| 00:10.07 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 00:18.06 | *** join/#maemo infobot (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
| 00:18.06 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog http://maemo.cloud-7.de/irclogs/freenode/_maemo/latest.log.html | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 00:18.07 | *** mode/#maemo [+v infobot] by ChanServ |
| 00:49.17 | *** join/#maemo hurrian (~hurrian@unaffiliated/rikanee) |
| 01:01.52 | *** join/#maemo hurrian (~hurrian@unaffiliated/rikanee) |
| 01:07.02 | *** join/#maemo hurrian_ (~hurrian@unaffiliated/rikanee) |
| 01:13.26 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 01:13.33 | *** join/#maemo hurrian (~hurrian@unaffiliated/rikanee) |
| 01:14.45 | Wikiwide | And now PDF reader is stuck. It has document X open, I click in File Manager for document Y to open, and PDF manager continues to display document X, not perturbed in the least. |
| 01:16.25 | Wikiwide | PDF reader can go all-black for a while, so it does hear something from File Manager - it's not File Manager's fault. |
| 01:17.05 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 01:19.12 | Wikiwide | And IRC is jumpy - on cellular Internet! At this rate, I will advocate for wooden buses with built-in Ethernet Internet - not that I know of any mobile phones with Ethernet built-in |
| 01:20.39 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 01:50.53 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 01:53.06 | Wikiwide | And barcode readers don't read barcode from my phone's display. I have already done 200% or so zoom, set brightness to 5/5, the barcode occupies at least quarter of display - half of width and half of height... |
| 01:53.51 | Wikiwide | They are probably designed to work with AMOLED display, with super-transparent Gorilla/sapphire glass :-/ |
| 01:54.48 | Wikiwide | At this rate, I would want to have a e-ink display for documents, barcodes and static images - low-power and I think that e-ink should be as readable as paper. |
| 02:31.13 | Maxdamantus | got an e-ink device yesterday (Kobo) |
| 02:31.22 | Maxdamantus | display seems quite nice. |
| 02:32.13 | Maxdamantus | wants to see if he can get a usable terminal running on it at some point. |
| 03:11.10 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 03:56.18 | *** join/#maemo pagurus` (~user@i59F7A7E3.versanet.de) |
| 05:20.05 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 05:20.55 | Wikiwide | Maxdamantus: Sounds neat :-) |
| 06:21.40 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 06:27.15 | *** join/#maemo Elleo (~Elleo@mikeasoft.com) |
| 06:27.15 | *** join/#maemo Elleo (~Elleo@libre.fm/hacker/elleo) |
| 07:45.14 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 07:50.09 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 07:50.48 | *** part/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 08:03.56 | KotCzarny | maxd: what soc? |
| 08:04.25 | KotCzarny | as for terminal, you would have your own app, so refreshes wont drive it dead ;) |
| 08:04.33 | KotCzarny | *write your own app |
| 08:13.25 | *** join/#maemo sicelo (~sicelo@41.84.244.160) |
| 08:21.43 | Maxdamantus | Do modern e-ink displays have lifetime issues? |
| 08:22.09 | Maxdamantus | I imagine the main reason for having to write some special screen update mechanism is just to avoid ghosting. |
| 08:23.25 | Maxdamantus | as for continuous updates, I've noticed the included web browser supports canvas .. was able to run http://maxdamantus.github.io/recplay/ on it. |
| 08:23.26 | KotCzarny | they are physical medium |
| 08:23.47 | Maxdamantus | So is everything. |
| 08:23.50 | KotCzarny | so i would assume they do, although it was more about refresh rate |
| 08:23.51 | Maxdamantus | including LCD. |
| 08:23.55 | KotCzarny | imagine running dmesg on it |
| 08:23.57 | KotCzarny | ;) |
| 08:30.49 | *** join/#maemo sicelo__ (~sicelo@41.84.239.199) |
| 08:37.40 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 09:17.18 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 09:44.12 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 10:19.38 | *** join/#maemo Kabouik (~kabouik@2a01cb008023010094ce3e4639dff0fa.ipv6.abo.wanadoo.fr) |
| 11:50.10 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 12:08.45 | *** join/#maemo Cor-Ai (~cor-ai@h-190-192.A400.priv.bahnhof.se) |
| 12:42.06 | *** join/#maemo remarc (~remarc@194.153.119.2) |
| 12:44.41 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 13:12.40 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 13:57.59 | DocScrutinizer05 | KotCzarny: on what? e-ink? X-D |
| 13:59.03 | DocScrutinizer05 | there's even 2-color e-ink paper now. Black&red. I guess other colors exist as well |
| 14:00.24 | DocScrutinizer05 | the "A4" size display allegedly (according to the fuzzy dadashit) takes up to 40 seconds for one full erase&scan |
| 14:01.26 | DocScrutinizer05 | yep, forty. aka 2/3 of a minute |
| 14:08.40 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 14:30.50 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 15:18.50 | *** part/#maemo rah (rah@verain.settrans.net) |
| 15:40.01 | KotCzarny | well, 16 level grayscale 1024x768 takes ~1s for full update |
| 15:40.08 | KotCzarny | with reset |
| 15:41.01 | KotCzarny | and color eink is just color filter applied on particular subpixels |
| 15:41.46 | KotCzarny | so color is tripling horizontal resolution in terms of pixels to refresh |
| 15:56.10 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 16:40.43 | *** join/#maemo i336 (~i336@121.216.113.211) |
| 17:46.10 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 18:13.40 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 18:41.10 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 18:44.59 | *** join/#maemo Oksana_ (~Wikiwide@124-169-0-52.dyn.iinet.net.au) |
| 18:45.23 | *** join/#maemo Oksana_ (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 19:52.21 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 20:38.43 | *** join/#maemo jrayhawk (~jrayhawk@unaffiliated/jrayhawk) |
| 21:44.10 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 22:10.18 | *** join/#maemo spiiroin (~spiiroin@81-197-33-31.elisa-laajakaista.fi) |
| 22:17.40 | *** join/#maemo saidinesh5 (~quassel@minad.de) |
| 22:31.37 | Maxdamantus | I don't think the resolution is going to have an effect on how long it takes to update. |
| 22:32.08 | Maxdamantus | unless something about the pixel density makes low-latency refreshes harder. |
| 22:33.42 | Maxdamantus | I would expect a terminal to update fairly quickly (resulting in ghosting) if it knows that it's scrolling through many lines of text, and when it stops scrolling, it should do a full redraw. |
| 22:34.07 | Maxdamantus | but I don't think a full redraw takes 1s on my kobo. |
| 22:34.41 | Maxdamantus | iirc takes probably less than 0.5s, but don't want to test that atm since I'm trying to get Xorg working |
| 22:39.53 | Maxdamantus | btw, rationale for resolution not having an effect on how long it takes to update: two e-ink devices should update in the same amount of time as one e-ink device, and two e-ink devices obviously have twice the number of pixels as one e-ink device. |
| 22:40.47 | Maxdamantus | so if more resolution means more time, you've just got some vertical scaling issue (eg, need more CPU power), not some issue inherent to e-ink technology. |
| 23:02.44 | *** join/#maemo xmn (~xmn@user-0cdft2n.cable.mindspring.com) |
| 23:04.46 | Maxdamantus | Decent demonstration of changes in update frequency: https://youtu.be/6pw-oCItgx8?t=356 |
| 23:12.10 | *** join/#maemo saidinesh5 (~quassel@minad.de) |