| 00:01.30 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 00:01.32 | *** join/#maemo 21WAAGJXD (kraft@gateway/shell/blinkenshell.org/x-euujdogozoufxbbq) |
| 00:01.45 | *** join/#maemo cpt_nemo_ (cpt_nemo@rfc1459.de) |
| 00:02.02 | *** join/#maemo ab (~ab@vda.li) |
| 00:02.02 | *** join/#maemo ab (~ab@pdpc/supporter/professional/ab) |
| 00:02.02 | *** join/#maemo wnd (~wnd@katei.fi) |
| 00:02.14 | *** join/#maemo atk (~Arch-TK@ircpuzzles/staff/Arch-TK) |
| 00:21.38 | *** join/#maemo infobot (ibot@rikers.org) |
| 00:21.38 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~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 | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 00:22.19 | *** join/#maemo hurrian (~textual@unaffiliated/rikanee) |
| 02:58.23 | *** join/#maemo spiiroin (~spiiroin@178-55-100-134.bb.dnainternet.fi) |
| 02:59.46 | *** join/#maemo pagurus (~user@p508374D7.dip0.t-ipconnect.de) |
| 05:16.09 | *** join/#maemo spiiroin (~spiiroin@2001:998:2a:dead:54b1:76c1:38c1:8838) |
| 06:50.01 | *** join/#maemo wnd_ (~wnd@katei.fi) |
| 06:50.17 | *** join/#maemo eMHa_ (~mh@p200300738E289000267703FFFE6CC360.dip0.t-ipconnect.de) |
| 06:50.33 | *** join/#maemo geaaru__ (~geaaru@host23-170-dynamic.9-87-r.retail.telecomitalia.it) |
| 06:50.36 | *** join/#maemo spiiroin (~spiiroin@2001:998:2a:dead:54b1:76c1:38c1:8838) |
| 06:50.39 | *** join/#maemo kraft (kraft@gateway/shell/blinkenshell.org/x-aqilmqiwoukiphvz) |
| 06:51.43 | *** join/#maemo zgrepc (sid43445@ircpuzzles/2015/april-fools/sixth/zgrep) |
| 06:54.46 | *** join/#maemo pagurus (~user@p508374D7.dip0.t-ipconnect.de) |
| 07:09.00 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 07:43.58 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 08:04.30 | *** part/#maemo L29Ah (~L29Ah@31.173.83.147) |
| 08:32.19 | *** join/#maemo oniongarlic (~milang@tori.tal.org) |
| 08:37.43 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 08:38.57 | jonwil | hi |
| 08:51.28 | enyc_ | meow |
| 08:59.46 | *** join/#maemo L29Ah (~L29Ah@31.173.83.147) |
| 09:10.19 | *** join/#maemo spiiroin (~spiiroin@178-55-100-134.bb.dnainternet.fi) |
| 09:14.21 | *** join/#maemo APic (apic@apic.name) |
| 09:59.01 | *** join/#maemo eMHa_ (~mh@81.26.162.98) |
| 10:00.25 | *** join/#maemo Vajb (~Vajb@85-76-98-118-nat.elisa-mobile.fi) |
| 10:20.40 | *** part/#maemo L29Ah (~L29Ah@31.173.83.147) |
| 11:03.30 | *** join/#maemo L29Ah_ (~L29Ah@31.173.83.147) |
| 11:08.09 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 11:08.57 | *** part/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 11:09.08 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 11:10.40 | Wikiwide | Darn... LEDs, again, do not work. Anybody remembers how I got out of it before? Both keyboard LEDs and RGB notification LED. |
| 11:13.30 | KotCzarny | swap screen? cable? |
| 11:13.51 | Wikiwide | And, excessive breaklines in email may have been generated by sender (Turnitin), not by Modest. Though, it doesn't negate the problem with scrolling very long draft in Modest. |
| 11:15.00 | Wikiwide | KotCzarny: keyboard backlight too, not just notification light. And, it was somehow resolved before, without changing the hardware. |
| 11:16.07 | Wikiwide | Either it is come-and-go problem, or it is file damage from all these out-of-control shutdowns (aka dying battery?) |
| 11:17.52 | Wikiwide | /me curses again lack of GUI for password management in MicroB; surely, there has to be a better way than python2.7-ing firefox_decrypt.py ? |
| 11:19.41 | Wikiwide | Actually, if I understood python better, it might have been possible to rewrite the py file to work with python2.5, and save the trouble of installing python2.7? |
| 11:22.31 | Wikiwide | I am quite irritable. But at least, "only" 97% of rootfs are full, even after installing python2.7 . So, pdf reader and other things should work. |
| 11:27.30 | *** part/#maemo L29Ah_ (~L29Ah@31.173.83.147) |
| 11:41.18 | *** join/#maemo L29Ah_ (~L29Ah@31.173.83.147) |
| 11:42.33 | *** join/#maemo sunshavi (~user@190.234.106.138) |
| 12:13.17 | sicelo | what password management? |
| 12:15.30 | sicelo | anyway, if you mean v/iewng saved passwords, just open 'chrome://passwordmgr/content/passwordManager.xul' the same as you would in FF |
| 12:16.22 | Wikiwide | Hmm, thank you! Will see if it can be bookmarked. Or added to desktop as a shortcut. |
| 12:18.44 | Wikiwide | Only, I have 5 passwords saved, and chrome://passwordmgr/content/passwordManager.xul says that no, there aren't any passwords saved in MicroB |
| 12:19.49 | *** join/#maemo hurrian (~textual@unaffiliated/rikanee) |
| 12:20.00 | *** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr) |
| 12:20.16 | Wikiwide | /me wonders how exactly I managed to tell MicroB to break the database. .. So that MicroB probably doesn't recognise it anymore (while firefox_decrypt.py does recognise it) |
| 12:27.21 | *** join/#maemo oniongarlic (~milang@tori.tal.org) |
| 12:27.47 | Wikiwide | Whatever is /dev/.udev/failed/ ... |
| 12:32.33 | DocScrutinizer05 | Wikiwide: LP5523 chip gets fsckdup by fcam |
| 12:32.37 | DocScrutinizer05 | remove battery |
| 12:34.43 | Wikiwide | No fcam here. Battery gets replaced regularly (since charging port not working). Does the battery need to be out of device for a long time (as in, forget time and date) ? |
| 12:35.12 | DocScrutinizer05 | at least for a maybe 30s |
| 12:35.46 | DocScrutinizer05 | a powercycle *should* reset LP5523 too, but... something is strange about that |
| 12:36.02 | DocScrutinizer05 | also check mce |
| 12:36.29 | DocScrutinizer05 | it might have encountered problems, for whatever reason |
| 12:37.00 | Wikiwide | Okay. Will do that. Hoping it works. Because it looks like I highlight all possible problems; if something can go wrong, it does (at some point in time). |
| 12:37.36 | DocScrutinizer05 | murphy's law ;-D |
| 12:39.03 | DocScrutinizer05 | stop mce; sleep 5; start mce |
| 12:39.18 | DocScrutinizer05 | watch syslog |
| 12:41.29 | Wikiwide | Okay, where is syslog?.. |
| 12:43.04 | Wikiwide | Sysklogd? |
| 12:48.15 | DocScrutinizer05 | ooh, you don't have it installed? then yes, apt-get install syslogd (and/or ksyslogd), somesuch |
| 12:48.22 | DocScrutinizer05 | sysklogd |
| 12:48.45 | DocScrutinizer05 | sysklogd is only for kernel messages which you also could read using dmesg |
| 12:49.12 | DocScrutinizer05 | http://wiki.maemo.org/Phone_control#Activate_LEDs |
| 12:49.16 | DocScrutinizer05 | try that |
| 12:49.44 | DocScrutinizer05 | with mce running |
| 12:52.38 | *** join/#maemo Vajb (~Vajb@85-76-55-20-nat.elisa-mobile.fi) |
| 12:54.43 | DocScrutinizer05 | when you installed syslog (and rebooted), you do "less /var/log/syslog" |
| 12:54.59 | DocScrutinizer05 | Wikiwide: ^^^ |
| 13:33.58 | *** join/#maemo drcode (~drcode@5.28.134.3) |
| 13:35.32 | *** join/#maemo florian (~fuchs@x4d0941ce.dyn.telefonica.de) |
| 13:46.15 | *** join/#maemo sunshavi (~user@190.234.106.138) |
| 14:12.39 | DocScrutinizer05 | ((Does the battery need to be out of device for a long time)) remove battery, press power button. should reliably and drastically reduce the time battery needs to be out |
| 14:13.54 | DocScrutinizer05 | ((time and date)) unrelated, the time&date is kept in TWL4030 with a dedicated backup battery coin cell |
| 14:13.59 | DocScrutinizer05 | ~bupbat |
| 14:13.59 | infobot | rumour has it, bupbat is use the capacitive type, LiIon are breaking during 12 months, or http://www.digikey.de/product-detail/de/PAS414HR-VG1/587-2157-1-ND/1959153, or https://hbe-shop.de/Art-2112777-TAIYO-YUDEN-PAS414HR-VA5R-KONDENSATOR006F-33V-STAKED-COIN, or http://talk.maemo.org/showthread.php?t=90864 |
| 14:15.14 | DocScrutinizer05 | the bupbat isn't connected and thus unrelated to LP5523 LED controller |
| 14:18.00 | DocScrutinizer05 | the involved systems are (without any special ordering): main battery, I2C, LP5523, flatflexcable, MCE (plus the mce-*.so libs), dbus |
| 14:20.03 | DocScrutinizer05 | (/usr/lib/mce/modules/libled.so) |
| 14:48.32 | buZz | DocScrutinizer05 servicing the world again \o |
| 14:48.36 | buZz | !tip DocScrutinizer05 10 maemocoins |
| 14:48.56 | DocScrutinizer05 | :-) |
| 14:49.14 | DocScrutinizer05 | still trying to recover from total health breakdown |
| 14:50.14 | DocScrutinizer05 | just fixing a nasty age old bug that - via sneaky paths - crept in again: sed -i -E 's/\x05\x00\x00\x00\x05\x00\x00\x00\x00\x00\x00\x00/\x05\x00\x00\x00\x05\x00\x00\x00\x05\x00\x00\x00/' /usr/lib/mce/modules/libfilter-brightness-als.so |
| 14:50.54 | DocScrutinizer05 | http://talk.maemo.org/showthread.php?p=1388368 |
| 14:51.38 | DocScrutinizer05 | allegedly CSSU MCE is fixed, but if that's true then for unclear reasons I'm not able to install CSSU mce on my device |
| 14:56.42 | DocScrutinizer05 | when you got CSSU installed, could you please paste in here the output of ` od -A x -tx1 /usr/lib/mce/modules/libfilter-brightness-als.so|grep '0086a0' ` |
| 14:57.35 | DocScrutinizer05 | and please md5sum /usr/lib/mce/modules/libfilter-brightness-als.so as well |
| 14:57.47 | *** join/#maemo hurrian (~textual@unaffiliated/rikanee) |
| 14:58.17 | buZz | DocScrutinizer05: stay healthy man |
| 14:58.22 | buZz | dont invest too much brain while still weak |
| 14:58.23 | DocScrutinizer05 | stay? hehe |
| 15:05.15 | *** part/#maemo L29Ah_ (~L29Ah@31.173.83.147) |
| 15:06.09 | DocScrutinizer05 | buZz: do you have CSSU MCE? |
| 15:06.44 | buZz | MCE? |
| 15:06.54 | *** join/#maemo hurrian (~textual@unaffiliated/rikanee) |
| 15:07.14 | buZz | oh is that the mediaplayer? |
| 15:07.16 | DocScrutinizer05 | <PROTECTED> |
| 15:07.24 | DocScrutinizer05 | ~mce |
| 15:07.25 | infobot | [mce] http://wiki.maemo.org/Free_Maemo#MCE |
| 15:07.40 | buZz | MCE is responsible of handling display control (active/dim/blank), activity monitoring (keys, buttons), keyboard backlight, ambient light sensor (ALS), LEDs and device mode control. In addition, MCE is responsible for providing interface to proximity, accelometer and vibra devices. |
| 15:07.45 | buZz | ah |
| 15:07.48 | buZz | not sure, i did install CSSU stuff |
| 15:08.35 | buZz | is the CSSU one the one that segfaults on --version ? :D |
| 15:08.39 | buZz | 1.8.127 |
| 15:08.52 | buZz | oh also on --help :D lol |
| 15:09.22 | kerio | lol |
| 15:09.27 | bencoh | is cssu-mce available in -stable/-testing nowadays? |
| 15:09.48 | DocScrutinizer05 | could you please do f= /usr/lib/mce/modules/libfilter-brightness-als.so; ls -l $f; md5sum $f; od -A x -tx1 $f|grep '0086a0' |
| 15:11.01 | DocScrutinizer05 | I have doubts free MCE is in CSSU, or it lacks my bugfix |
| 15:11.37 | buZz | 3fb...a9e is the md5 of that file |
| 15:11.43 | buZz | dno what rest of command does |
| 15:11.52 | buZz | no 0086 in it |
| 15:12.33 | DocScrutinizer05 | wow, doesn't match *any* of my various versions here |
| 15:12.38 | buZz | :) |
| 15:12.50 | buZz | maybe its the CSSU-NSA additions |
| 15:13.38 | DocScrutinizer05 | http://paste.ubuntu.com/24784295 |
| 15:14.15 | DocScrutinizer05 | thinks his system is thoroughly fuxored |
| 15:14.42 | buZz | i have 1.8.127.5+0m5 |
| 15:14.55 | buZz | from maemo.merlin1991.at |
| 15:14.56 | DocScrutinizer05 | hmmmm |
| 15:15.06 | buZz | thats the nsa, right? |
| 15:15.13 | DocScrutinizer05 | right ;-P |
| 15:15.17 | buZz | ^_^ |
| 15:15.45 | DocScrutinizer05 | could you please run od -A x -tx1 /usr/lib/mce/modules/libfilter-brightness-als.so|grep '0086a0' |
| 15:16.30 | DocScrutinizer05 | wait, that's prolly nonsense |
| 15:16.46 | DocScrutinizer05 | the byte offset would have changed in freeMCE |
| 15:17.08 | buZz | od doesnt have -A |
| 15:17.15 | DocScrutinizer05 | ~messybox |
| 15:17.15 | infobot | messy... err busybox is meant for lean scripting. Regarding all the missing options and immanent limitations (see su, passwd, nice, ps, diff as used by mc...) it's not really the interactive shell of choice. A lot of people hate busybox because a lot of system integrators don't understand the difference between busybox and a decent user interactive shell plus unix utils |
| 15:17.23 | buZz | i dont care :P |
| 15:17.43 | buZz | i'm not replacing shell just to check for a hexdump :P |
| 15:18.21 | DocScrutinizer05 | neither do I |
| 15:18.30 | DocScrutinizer05 | I simply run bash manually |
| 15:18.36 | buZz | :) |
| 15:18.41 | DocScrutinizer05 | and I adjust my path |
| 15:18.48 | bencoh | od isn't part of the shell |
| 15:18.54 | DocScrutinizer05 | o.O |
| 15:19.13 | buZz | 'not found' |
| 15:19.15 | buZz | :P |
| 15:19.27 | buZz | DocScrutinizer05: this is getting close to my limit of 'check a file for me' |
| 15:19.35 | buZz | its different, just be happy :P |
| 15:20.52 | DocScrutinizer05 | nevermind, if it's freeMCE then the bytes at offset 0x000086a0 are meaningless anyway |
| 15:21.25 | DocScrutinizer05 | IroN900:~# busybox od -help |
| 15:21.26 | DocScrutinizer05 | od: invalid option -- p |
| 15:21.28 | DocScrutinizer05 | BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) multi-call binary |
| 15:21.29 | DocScrutinizer05 | Usage: od [-aBbcDdeFfHhIiLlOovXx] [FILE] |
| 15:21.36 | DocScrutinizer05 | bencoh: ^^^ |
| 15:21.47 | buZz | hehe, doesnt even have -A |
| 15:21.49 | buZz | lol |
| 15:21.58 | buZz | oh, lol |
| 15:21.59 | buZz | ^_^ |
| 15:28.15 | bencoh | DocScrutinizer05: it still isn't part of the shell perse |
| 15:28.34 | DocScrutinizer05 | err. I never claimed that, whatever it means |
| 15:29.21 | DocScrutinizer05 | ~dict perse |
| 15:30.04 | DocScrutinizer05 | od *is* part of busybox |
| 15:30.41 | bencoh | DocScrutinizer05: http://www.dictionary.com/browse/per-se |
| 15:30.53 | DocScrutinizer05 | oh per se |
| 15:30.56 | *** part/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 15:31.11 | bencoh | busybox ships with its own version of od |
| 15:31.24 | bencoh | using bash instead wont change the fact that you're using busybox-provided od |
| 15:31.28 | DocScrutinizer05 | well, isn't that what I just said? |
| 15:31.40 | bencoh | anyway |
| 15:32.05 | DocScrutinizer05 | [2017-06-05 Mon 17:18:41] <DocScrutinizer05> and I adjust my path |
| 15:33.04 | DocScrutinizer05 | /usr/bin/gnu/od |
| 15:33.06 | DocScrutinizer05 | IroN900:~# echo $PATH |
| 15:33.07 | DocScrutinizer05 | /usr/local/sbin:/usr/local/bin:/usr/sbin/gnu:/usr/sbin:/usr/bin/gnu:/usr/bin:/sbin:/bin:/usr/bin/X11 |
| 15:33.32 | DocScrutinizer05 | missed first line IroN900:~# which od |
| 15:34.34 | DocScrutinizer05 | not interested in this pointless fighting |
| 15:40.02 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 15:40.33 | DocScrutinizer05 | particularly since I got other problems: http://paste.ubuntu.com/24784525 *puke* |
| 15:44.55 | DocScrutinizer05 | tbh od oughta get killed with fire from all POSIX (is it even POSIX?) and get replaced by e.g. hexdump |
| 15:45.26 | DocScrutinizer05 | octal dump, computer pleozaen |
| 15:46.54 | DocScrutinizer05 | not like the usual hexdump had a comprehensive set of options either |
| 15:47.45 | *** join/#maemo L29Ah_ (~L29Ah_@31.173.83.147) |
| 15:49.56 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:58.53 | DocScrutinizer05 | buZz: you could check the result instead of checking the binary creating results: get a bright flashlight, place it to the ALS (upper left corner in landscape) for as long as it takes to dim the screen and shut off kbd backlight (with brighness set at 4 bars, won't ever happen at 5 bars. a 15s should suffice in this case), then without removing flashlight lock the screen with sliding lockswitch, check the brightness of beathing indicator |
| 15:58.54 | DocScrutinizer05 | light - is it normal brightness or very very dim (which is the bug I fixed) |
| 15:59.18 | buZz | what problem of -mine- is that analyzing? |
| 15:59.29 | DocScrutinizer05 | dim indicator light |
| 15:59.37 | buZz | i dont have that problem |
| 15:59.45 | DocScrutinizer05 | are you sure? |
| 15:59.52 | buZz | does that matter? :D |
| 16:00.01 | DocScrutinizer05 | does maemo matter? |
| 16:00.18 | buZz | i do 3-4 weeks on a charge, light can be dim all it wants |
| 16:00.30 | DocScrutinizer05 | now THAT is too much for my brain and mind |
| 16:00.37 | buZz | <3 |
| 16:01.15 | DocScrutinizer05 | trying to fix a bug (or check if that bug is already fixed in CSSU) and reply in here is "fuck off, doen't matter" |
| 16:01.48 | freemangordon | DocScrutinizer05: iirc the bug is not fixed |
| 16:01.56 | DocScrutinizer05 | :nod: |
| 16:02.46 | freemangordon | DocScrutinizer05: please, find the relevant file on https://github.com/community-ssu/mce, fix it and give it back to me, I'll make the appropriate commit and release |
| 16:03.12 | DocScrutinizer05 | http://talk.maemo.org/showthread.php?p=1388368 |
| 16:03.43 | freemangordon | ok, thanks |
| 16:03.43 | DocScrutinizer05 | the 00 must ne a 05 |
| 16:03.46 | freemangordon | ok |
| 16:05.01 | DocScrutinizer05 | http://mg.pov.lt/maemo-ssu-irclog/%23maemo-ssu.2013-11-23.log.html#t2013-11-23T06:20:48 |
| 16:05.07 | DocScrutinizer05 | better more detailed |
| 16:05.09 | freemangordon | DocScrutinizer05: which line is that? https://github.com/community-ssu/mce/blob/master/modules/filter-brightness-als.h#L82 ? |
| 16:06.32 | freemangordon | DocScrutinizer05: https://github.com/community-ssu/mce/blob/master/modules/filter-brightness-als.h#L184 ? |
| 16:06.55 | DocScrutinizer05 | yup, looks correct |
| 16:07.17 | freemangordon | ok, will fix it, though not today |
| 16:08.11 | DocScrutinizer05 | :-) |
| 16:08.47 | freemangordon | I am waiting for guests to come home, so... :) |
| 16:08.57 | DocScrutinizer05 | with >100lux (https://github.com/community-ssu/mce/blob/master/modules/filter-brightness-als.h#L180) the brightness switches to 0, and it switches back to 5 on <64lux |
| 16:11.19 | DocScrutinizer05 | or is it >1000lux? |
| 16:11.33 | DocScrutinizer05 | NFC, anyway the patch works |
| 16:12.43 | DocScrutinizer05 | aah wait, the tupels are defining a threshold incl hysteresis, not a range |
| 16:15.26 | DocScrutinizer05 | so (assuming a }, { 3, 5, 0, 0, 0, 0 } line) we would run LED at 0 up to 64lux, at 5 up to 1000lux, and at 0 over 1000lux. dimming down again, we would switch back to 5 at 100lux and to 3 at 32lux |
| 16:17.10 | DocScrutinizer05 | each tuple defines the thresholds for downward and upword, for one ","-border in { 5, 5, 0, 0, 0, 0 } |
| 16:18.36 | DocScrutinizer05 | since we got two valif such tuples, we need *3* meaningful brightness levels in that { 5, 5, 0, 0, 0, 0 } |
| 16:21.12 | DocScrutinizer05 | so (assuming a }, { 3, 5, 0, 0, 0, 0 } line) we would run LED at **3** up to 64lux, at 5 up to 1000lux, and at 0 over 1000lux. dimming down again, we would switch back to 5 at 100lux and to 3 at 32lux |
| 16:21.31 | DocScrutinizer05 | (sorry for the typo) |
| 16:55.41 | *** join/#maemo drcode (~drcode@5.28.134.3) |
| 17:04.50 | *** join/#maemo eMHa_ (~mh@p200300738E289000267703FFFE6CC360.dip0.t-ipconnect.de) |
| 17:09.31 | *** join/#maemo tomislav (d4c841f3@gateway/web/freenode/ip.212.200.65.243) |
| 17:09.48 | tomislav | Why my ip was banned from talk on Maemo |
| 17:10.13 | tomislav | What did I do wrong |
| 17:10.17 | tomislav | ? |
| 17:13.47 | KotCzarny | nothing, just overzealous spam list and you are probably using dynamic ip |
| 17:14.45 | KotCzarny | pah. |
| 17:46.57 | *** join/#maemo ff__ (~ff_@dzi140.neoplus.adsl.tpnet.pl) |
| 17:47.20 | ff__ | wikiwide, from root try, rmmod leds_lp5523 |
| 17:47.20 | ff__ | modprobe leds_lp5523 |
| 17:48.37 | ff__ | and then this: cat /sys/class/i2c-adapter/i2c-2/2-0032/selftest should blink all leds and print OK in command line |
| 17:49.41 | *** join/#maemo drcode (~drcode@5.28.134.3) |
| 17:49.42 | *** join/#maemo cyteen (~cyteen@cyteen42.plus.com) |
| 18:03.09 | DocScrutinizer05 | you won't see such blinking |
| 18:03.24 | DocScrutinizer05 | it's way too short to usually get noticed |
| 18:05.04 | DocScrutinizer05 | ooh, I stand corrected, after testing it |
| 18:09.46 | DocScrutinizer05 | nice way to check for operational hardwate with minimal software involvement |
| 18:10.01 | DocScrutinizer05 | hardware* |
| 18:10.27 | DocScrutinizer05 | selftest is a LP5523-internal hw function |
| 18:11.00 | DocScrutinizer05 | ff__: nice catch |
| 18:11.25 | ff__ | yes, it should gives some additional information if something doesn't work |
| 18:12.34 | DocScrutinizer05 | yep, the chip checks if each of the LEDs draws correct current at correct voltage |
| 18:13.30 | DocScrutinizer05 | so it can detect all hw defects except a LED simply not emitting photons when operating |
| 18:13.58 | DocScrutinizer05 | don't know if that's even possible for a LED die |
| 18:16.40 | ff__ | by the way, is it possible indicate autofocus & whitebalance during record through gstreamer? |
| 18:16.59 | DocScrutinizer05 | no idea |
| 18:17.32 | DocScrutinizer05 | I _think_ both are managed by a blob shared lib |
| 18:18.15 | DocScrutinizer05 | maybe I'm mistaken and the lib isn't a blob |
| 18:19.00 | DocScrutinizer05 | or it has a documented API at least, where you can get that info from |
| 18:20.10 | DocScrutinizer05 | camera-ui2 aka nicocam has a focum length indicator, so the v4l2 stuff must provide it |
| 18:20.21 | DocScrutinizer05 | focus* |
| 18:22.04 | ff__ | yes, focus adjusting is done |
| 18:22.54 | DocScrutinizer05 | https://www.linuxtv.org/downloads/legacy/video4linux/API/V4L2_API/spec-single/v4l2.html maybe helps. No idea whatsoever about whitebal |
| 18:24.20 | ff__ | v4l2src has GstColorBalance |
| 18:24.53 | ff__ | but don't know how to use it |
| 18:27.27 | DocScrutinizer05 | needs at least 2 (prolly dimensionless) ints, I'd guess |
| 18:29.15 | *** join/#maemo pagurus (~user@p508374D7.dip0.t-ipconnect.de) |
| 18:29.30 | DocScrutinizer05 | how whitebalance works internally is a mystery to me. It's less mysterious when the picture has all colors so you could adjust to maje a median or average or whatever fit a neutral point. But what when you shoot a tree format-filling? all just green, what's the whitebalance with that? |
| 18:30.52 | DocScrutinizer05 | s/maje/make/ |
| 18:32.21 | ff__ | it adds some error probably, camerabin in gstreamer does the job, but not in v4l2src |
| 18:33.02 | ff__ | *but not with v4l2src |
| 18:33.25 | DocScrutinizer05 | and that's exactly the sekrit knowledge camera manufs (also the one of N900 camera) add to their product in form of closed blob binaries aka libs which are never getting disclosed since they are company asset algorithms |
| 18:34.49 | DocScrutinizer05 | recent cryPhone camera advertised by apple as "the best camera ever" or somesuch - all of that is in those libs, none in the mere hardware |
| 18:35.40 | DocScrutinizer05 | Sony compactcam ultrafast autofocus: software |
| 18:37.26 | ff__ | fluid lens are fun :) |
| 18:37.42 | DocScrutinizer05 | hehe yes, but not exactly high quality |
| 18:38.16 | DocScrutinizer05 | neither suitable for decent aperture size |
| 18:38.34 | ff__ | and how speed performace with it? |
| 18:39.07 | DocScrutinizer05 | hm? I think that's their main advantage - mere speed |
| 18:39.19 | DocScrutinizer05 | plus no mechanics at all |
| 18:39.53 | DocScrutinizer05 | apply more voltage, make drop mor special |
| 18:40.02 | DocScrutinizer05 | works in milliseconds |
| 18:40.15 | DocScrutinizer05 | damn!! |
| 18:40.34 | DocScrutinizer05 | apply more voltage, make drop more spherical |
| 18:40.58 | ff__ | I didn't know that liquid lens has pretty poor quality |
| 18:41.13 | DocScrutinizer05 | it's a sperical lens |
| 18:41.28 | DocScrutinizer05 | of max a few millimeters diameter |
| 18:41.38 | DocScrutinizer05 | prolly more like 1 or 2 mm |
| 18:42.10 | DocScrutinizer05 | for a spherical lens it's maybe perfect |
| 18:42.59 | DocScrutinizer05 | but high class multi-lens setups use surprisingly complex lens shapes |
| 18:43.56 | DocScrutinizer05 | to reduce color aberration etc |
| 18:46.11 | *** join/#maemo Cor-Ai (~cor-ai@c-423572d5.06-922-7570702.cust.bredbandsbolaget.se) |
| 18:51.00 | *** join/#maemo spiiroin_ (~spiiroin@188-67-71-20.bb.dnainternet.fi) |
| 18:57.03 | DocScrutinizer05 | wow, seems they increased that stuff in scale quite a lot: http://www.varioptic.com/ |
| 18:58.29 | DocScrutinizer05 | http://www.varioptic.com/technology/liquid-lens-autofocus-af/ tha basics |
| 18:58.42 | *** join/#maemo pagurus (~user@p508374D7.dip0.t-ipconnect.de) |
| 19:01.03 | *** join/#maemo ginggs (~quassel@2a05:d018:c1e:8d00:c473:4128:ae2d:2c36) |
| 19:04.22 | DocScrutinizer05 | s/color/chromatic/ |
| 19:05.11 | DocScrutinizer05 | https://en.wikipedia.org/wiki/Chromatic_aberration |
| 19:06.15 | DocScrutinizer05 | maybe they meanwhile can use a spherical liquid lens in combination with a complex aspheric glass lens setup |
| 19:08.16 | DocScrutinizer05 | https://en.wikipedia.org/wiki/Aspheric_lens |
| 19:10.27 | DocScrutinizer05 | https://en.wikipedia.org/wiki/Aspheric_lens#/media/File:Mobile_phone_camera_lens_module,_3D_X-ray_microscopy_(30033111412).jpg ;-D |
| 19:21.41 | DocScrutinizer05 | https://en.wikipedia.org/wiki/Chromatic_aberration#/media/File:Lens6b-en.svg achromatic doublet - can't be done that way with a liquid lens for the convex part since the concave part needs matching properties |
| 19:26.24 | ff__ | so that's not for professional use, maybe for some action use |
| 19:27.11 | ff__ | have we uart or spi interface somwhere inside n900? |
| 19:29.05 | ff__ | second e-ink screen would be helpful, like that one http://waveshare.com/wiki/4.3inch_e-Paper_UART_Module |
| 19:56.04 | DocScrutinizer05 | UART yes. SPI too but not available to users |
| 19:56.20 | DocScrutinizer05 | UART though is on testpoints: console |
| 19:57.03 | DocScrutinizer05 | maybe you want hackerbus? ;-) |
| 19:57.10 | DocScrutinizer05 | ~neo900 hb |
| 19:57.15 | DocScrutinizer05 | ~#neo900 hb |
| 19:57.15 | infobot | well, #neo900 hb is http://neo900.org/stuff/papers/hb.pdf and http://talk.maemo.org/showthread.php?p=1461954 |
| 20:00.08 | ff__ | yes, read this for now http://wiki.maemo.org/N900_Hardware_Hacking |
| 20:01.09 | ff__ | connect this e-ink to n900 (while it has exposed UART) seems to possible |
| 20:01.37 | ff__ | *seems to be possible |
| 20:07.17 | DocScrutinizer05 | yes, possible |
| 20:07.43 | DocScrutinizer05 | you need more than just UART though: power, and power control |
| 20:08.17 | DocScrutinizer05 | and levelshifter for UART |
| 20:09.44 | ff__ | you are right |
| 20:10.17 | ff__ | how to talk through this UART? |
| 20:10.37 | DocScrutinizer05 | err, prolly just use /dev/tty0 or somesuch |
| 20:14.07 | ff__ | ok, J2000 connectors under battery and /dev/ttyS0 |
| 20:20.04 | DocScrutinizer05 | without warranties, but yes :-) |
| 20:21.24 | DocScrutinizer05 | the voltage level is still a mystery, but I'd recommend assuming 1V8 |
| 20:22.06 | DocScrutinizer05 | as that's the level expected according to all datasheets and other docs available |
| 20:22.52 | DocScrutinizer05 | see my latest edit >> Pin number: AH8, name: etk_d15/sdti_txd3 (serial data out, system trace messages); power domain: vdds 1.8V [1] voltage level actually seen is a miracle<< |
| 20:24.08 | DocScrutinizer05 | you might want to ask a kernel hacker ( freemangordon?) for details about etk_d15/sdti_txd3 |
| 20:26.05 | DocScrutinizer05 | maybe he could even completely falsify what I found out regarding that stuff |
| 20:26.28 | DocScrutinizer05 | tbh it makes no sense to me |
| 20:34.04 | DocScrutinizer05 | http://wstaw.org/m/2017/06/05/plasma-desktopr22054.png looks like AH7 but that makes no sense at all, and probably it's AH8. Then there's also http://wstaw.org/m/2017/06/05/plasma-desktopL22054.png which must be OVP and thus irrelevant, and http://wstaw.org/m/2017/06/05/plasma-desktopw22054.png which probably is some phantom current via a number of nearby pads, so a secondary false positive |
| 20:34.58 | DocScrutinizer05 | (the original is in the [1] reference of above quote) |
| 20:35.32 | DocScrutinizer05 | in http://wiki.maemo.org/N900_Hardware_Hacking |
| 20:48.23 | ff__ | make screenshot, convert it to gray4 (2bpp), add 800x120 pixels and send it to the module (need sniff what EPSCOMM.exe sends first, some init etc) |
| 20:51.20 | ff__ | I think for white / black on n900 it should be nice visible on this 2bpp e-ink, but for colourful, more gradient, that gray4 is too small |
| 20:51.20 | ff__ | need convert few screenshots |
| 20:53.32 | *** join/#maemo HRH_H_Crab (~crab@kowloontong.dim-sum.org) |
| 20:54.41 | *** join/#maemo Wikiwide (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 21:16.11 | DocScrutinizer05 | that should be easy. but honestly I think e-ink paper is better used in independent mode rather than mirroring mode, on N900 |
| 21:17.30 | DocScrutinizer05 | the qurstion actually is: what are the planned usecases |
| 21:18.59 | DocScrutinizer05 | I'd run a separate x11 server for e-ink display, and have that "screenshot" as an app within a "window" |
| 21:20.18 | DocScrutinizer05 | you don't have a digitizer on that e-ink display, to operate anything. So you need to resort to the original display anyway for anything meaningful interactive |
| 21:23.16 | DocScrutinizer05 | for e.g. a ebook reader you could configure the reader to show next page (or scroll) via vol+/- for example, and have the text displayed in "mirror display to e.ink" app on e-ink paper (could refresh automatically when the primary display gets refreshed). Then you shut down the primary display by simply setting backlight to 0 and maybe even blank it |
| 21:24.12 | DocScrutinizer05 | you can't "just lock the screen" since by definition that stops all running processes from updating their window content - to save energy |
| 21:24.55 | DocScrutinizer05 | any app that doesn't obey this rule wouldn't qualify for maemo-extras in testing |
| 21:25.47 | DocScrutinizer05 | you need a launcher that can start apps on display:1.0 - the e-ink display |
| 21:26.20 | DocScrutinizer05 | this way you could for example have a clock on e-.ink |
| 21:27.05 | DocScrutinizer05 | maemo-notifier could get tweaked to use both displays concurrently |
| 21:29.58 | ff__ | don't know how use x11 server with UART |
| 21:30.33 | DocScrutinizer05 | err well, it's a question how to implement the framebuffer, no? |
| 21:31.03 | ff__ | essential is what you sed, what are the planned usecases |
| 21:35.53 | ff__ | as reader text from pdf, doc, it's simple script that will be read block of text from ebook and send it to e-ink each time + /- vol pressed |
| 21:37.02 | DocScrutinizer05 | maybe an inspiration, though aiui the e-ink display can do better than only ascii art: https://linux.die.net/man/3/aa_render |
| 21:37.38 | DocScrutinizer05 | anyway you see people implemented framebuffers even on ascii-only displays |
| 21:37.57 | DocScrutinizer05 | shouldn't be hard to implement a framebuffer talking to UART |
| 21:38.30 | DocScrutinizer05 | >>This function does the trick of converting the emulated framebuffer into high quality ASCII-art<< |
| 21:48.27 | DocScrutinizer05 | ((simple script)) yes, for that you should look into printing (lpr et al) |
| 21:49.47 | DocScrutinizer05 | cups etc exist for maemo, and a UART/serial ascii-only printer is easy to configure in cups |
| 21:50.17 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 22:05.14 | *** part/#maemo L29Ah_ (~L29Ah_@31.173.83.147) |
| 22:05.37 | *** join/#maemo L29Ah_ (~L29Ah_@31.173.83.147) |
| 22:08.12 | *** join/#maemo oniongarlic (~milang@tori.tal.org) |
| 22:20.43 | *** join/#maemo cyteen (~cyteen@cyteen42.plus.com) |
| 22:29.55 | *** join/#maemo HRH_H_Crab (~crab@kowloontong.dim-sum.org) |
.jpg){kind=link}
