**** BEGIN LOGGING AT Mon Jun 05 03:00:03 2017 Jun 05 08:38:57 hi Jun 05 08:51:28 meow Jun 05 11:10:40 Darn... LEDs, again, do not work. Anybody remembers how I got out of it before? Both keyboard LEDs and RGB notification LED. Jun 05 11:13:30 swap screen? cable? Jun 05 11:13:52 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. Jun 05 11:15:00 KotCzarny: keyboard backlight too, not just notification light. And, it was somehow resolved before, without changing the hardware. Jun 05 11:16:07 Either it is come-and-go problem, or it is file damage from all these out-of-control shutdowns (aka dying battery?) Jun 05 11:17:52 /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 ? Jun 05 11:19:41 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? Jun 05 11:22:31 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. Jun 05 12:13:17 what password management? Jun 05 12:15:30 anyway, if you mean v/iewng saved passwords, just open 'chrome://passwordmgr/content/passwordManager.xul' the same as you would in FF Jun 05 12:16:22 Hmm, thank you! Will see if it can be bookmarked. Or added to desktop as a shortcut. Jun 05 12:18:44 Only, I have 5 passwords saved, and chrome://passwordmgr/content/passwordManager.xul says that no, there aren't any passwords saved in MicroB Jun 05 12:20:16 /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) Jun 05 12:27:47 Whatever is /dev/.udev/failed/ ... Jun 05 12:32:33 Wikiwide: LP5523 chip gets fsckdup by fcam Jun 05 12:32:37 remove battery Jun 05 12:34:43 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) ? Jun 05 12:35:12 at least for a maybe 30s Jun 05 12:35:46 a powercycle *should* reset LP5523 too, but... something is strange about that Jun 05 12:36:02 also check mce Jun 05 12:36:29 it might have encountered problems, for whatever reason Jun 05 12:37:00 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). Jun 05 12:37:36 murphy's law ;-D Jun 05 12:39:03 stop mce; sleep 5; start mce Jun 05 12:39:18 watch syslog Jun 05 12:41:29 Okay, where is syslog?.. Jun 05 12:43:05 Sysklogd? Jun 05 12:48:15 ooh, you don't have it installed? then yes, apt-get install syslogd (and/or ksyslogd), somesuch Jun 05 12:48:22 sysklogd Jun 05 12:48:45 sysklogd is only for kernel messages which you also could read using dmesg Jun 05 12:49:12 http://wiki.maemo.org/Phone_control#Activate_LEDs Jun 05 12:49:16 try that Jun 05 12:49:44 with mce running Jun 05 12:54:43 when you installed syslog (and rebooted), you do "less /var/log/syslog" Jun 05 12:54:59 Wikiwide: ^^^ Jun 05 14:12:39 ((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 Jun 05 14:13:54 ((time and date)) unrelated, the time&date is kept in TWL4030 with a dedicated backup battery coin cell Jun 05 14:13:59 ~bupbat Jun 05 14:13:59 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 Jun 05 14:15:14 the bupbat isn't connected and thus unrelated to LP5523 LED controller Jun 05 14:18:00 the involved systems are (without any special ordering): main battery, I2C, LP5523, flatflexcable, MCE (plus the mce-*.so libs), dbus Jun 05 14:20:03 (/usr/lib/mce/modules/libled.so) Jun 05 14:48:32 DocScrutinizer05 servicing the world again \o Jun 05 14:48:36 !tip DocScrutinizer05 10 maemocoins Jun 05 14:48:56 :-) Jun 05 14:49:14 still trying to recover from total health breakdown Jun 05 14:50:14 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 Jun 05 14:50:54 http://talk.maemo.org/showthread.php?p=1388368 Jun 05 14:51:38 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 Jun 05 14:56:42 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' ` Jun 05 14:57:35 and please md5sum /usr/lib/mce/modules/libfilter-brightness-als.so as well Jun 05 14:58:17 DocScrutinizer05: stay healthy man Jun 05 14:58:22 dont invest too much brain while still weak Jun 05 14:58:23 stay? hehe Jun 05 15:06:09 buZz: do you have CSSU MCE? Jun 05 15:06:44 MCE? Jun 05 15:07:14 oh is that the mediaplayer? Jun 05 15:07:16 /sbin/mce Jun 05 15:07:24 ~mce Jun 05 15:07:25 [mce] http://wiki.maemo.org/Free_Maemo#MCE Jun 05 15:07:40 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. Jun 05 15:07:45 ah Jun 05 15:07:48 not sure, i did install CSSU stuff Jun 05 15:08:35 is the CSSU one the one that segfaults on --version ? :D Jun 05 15:08:39 1.8.127 Jun 05 15:08:52 oh also on --help :D lol Jun 05 15:09:22 lol Jun 05 15:09:27 is cssu-mce available in -stable/-testing nowadays? Jun 05 15:09:48 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' Jun 05 15:11:01 I have doubts free MCE is in CSSU, or it lacks my bugfix Jun 05 15:11:37 3fb...a9e is the md5 of that file Jun 05 15:11:43 dno what rest of command does Jun 05 15:11:52 no 0086 in it Jun 05 15:12:33 wow, doesn't match *any* of my various versions here Jun 05 15:12:38 :) Jun 05 15:12:50 maybe its the CSSU-NSA additions Jun 05 15:13:38 http://paste.ubuntu.com/24784295 Jun 05 15:14:15 * DocScrutinizer05 thinks his system is thoroughly fuxored Jun 05 15:14:42 i have 1.8.127.5+0m5 Jun 05 15:14:55 from maemo.merlin1991.at Jun 05 15:14:56 hmmmm Jun 05 15:15:06 thats the nsa, right? Jun 05 15:15:13 right ;-P Jun 05 15:15:17 ^_^ Jun 05 15:15:45 could you please run od -A x -tx1 /usr/lib/mce/modules/libfilter-brightness-als.so|grep '0086a0' Jun 05 15:16:30 wait, that's prolly nonsense Jun 05 15:16:46 the byte offset would have changed in freeMCE Jun 05 15:17:08 od doesnt have -A Jun 05 15:17:15 ~messybox Jun 05 15:17:16 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 Jun 05 15:17:23 i dont care :P Jun 05 15:17:43 i'm not replacing shell just to check for a hexdump :P Jun 05 15:18:21 neither do I Jun 05 15:18:30 I simply run bash manually Jun 05 15:18:36 :) Jun 05 15:18:41 and I adjust my path Jun 05 15:18:48 od isn't part of the shell Jun 05 15:18:54 o.O Jun 05 15:19:13 'not found' Jun 05 15:19:15 :P Jun 05 15:19:27 DocScrutinizer05: this is getting close to my limit of 'check a file for me' Jun 05 15:19:35 its different, just be happy :P Jun 05 15:20:52 nevermind, if it's freeMCE then the bytes at offset 0x000086a0 are meaningless anyway Jun 05 15:21:25 IroN900:~# busybox od -help Jun 05 15:21:26 od: invalid option -- p Jun 05 15:21:28 BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) multi-call binary Jun 05 15:21:29 Usage: od [-aBbcDdeFfHhIiLlOovXx] [FILE] Jun 05 15:21:36 bencoh: ^^^ Jun 05 15:21:47 hehe, doesnt even have -A Jun 05 15:21:49 lol Jun 05 15:21:58 oh, lol Jun 05 15:21:59 ^_^ Jun 05 15:28:15 DocScrutinizer05: it still isn't part of the shell perse Jun 05 15:28:34 err. I never claimed that, whatever it means Jun 05 15:29:21 ~dict perse Jun 05 15:29:23 could not find definition for perse Jun 05 15:30:04 od *is* part of busybox Jun 05 15:30:40 DocScrutinizer05: http://www.dictionary.com/browse/per-se Jun 05 15:30:53 oh per se Jun 05 15:31:11 busybox ships with its own version of od Jun 05 15:31:24 using bash instead wont change the fact that you're using busybox-provided od Jun 05 15:31:28 well, isn't that what I just said? Jun 05 15:31:40 anyway Jun 05 15:32:05 [2017-06-05 Mon 17:18:41] and I adjust my path Jun 05 15:33:04 /usr/bin/gnu/od Jun 05 15:33:05 IroN900:~# echo $PATH Jun 05 15:33:07 /usr/local/sbin:/usr/local/bin:/usr/sbin/gnu:/usr/sbin:/usr/bin/gnu:/usr/bin:/sbin:/bin:/usr/bin/X11 Jun 05 15:33:32 missed first line IroN900:~# which od Jun 05 15:34:34 not interested in this pointless fighting Jun 05 15:40:33 particularly since I got other problems: http://paste.ubuntu.com/24784525 *puke* Jun 05 15:44:55 tbh od oughta get killed with fire from all POSIX (is it even POSIX?) and get replaced by e.g. hexdump Jun 05 15:45:26 octal dump, computer pleozaen Jun 05 15:46:54 not like the usual hexdump had a comprehensive set of options either Jun 05 15:58:53 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 Jun 05 15:58:54 light - is it normal brightness or very very dim (which is the bug I fixed) Jun 05 15:59:18 what problem of -mine- is that analyzing? Jun 05 15:59:29 dim indicator light Jun 05 15:59:37 i dont have that problem Jun 05 15:59:45 are you sure? Jun 05 15:59:52 does that matter? :D Jun 05 16:00:01 does maemo matter? Jun 05 16:00:18 i do 3-4 weeks on a charge, light can be dim all it wants Jun 05 16:00:30 now THAT is too much for my brain and mind Jun 05 16:00:37 <3 Jun 05 16:01:15 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" Jun 05 16:01:48 DocScrutinizer05: iirc the bug is not fixed Jun 05 16:01:56 :nod: Jun 05 16:02:46 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 Jun 05 16:03:12 http://talk.maemo.org/showthread.php?p=1388368 Jun 05 16:03:43 ok, thanks Jun 05 16:03:43 the 00 must ne a 05 Jun 05 16:03:46 ok Jun 05 16:05:01 http://mg.pov.lt/maemo-ssu-irclog/%23maemo-ssu.2013-11-23.log.html#t2013-11-23T06:20:48 Jun 05 16:05:07 better more detailed Jun 05 16:05:09 DocScrutinizer05: which line is that? https://github.com/community-ssu/mce/blob/master/modules/filter-brightness-als.h#L82 ? Jun 05 16:06:32 DocScrutinizer05: https://github.com/community-ssu/mce/blob/master/modules/filter-brightness-als.h#L184 ? Jun 05 16:06:55 yup, looks correct Jun 05 16:07:17 ok, will fix it, though not today Jun 05 16:08:11 :-) Jun 05 16:08:47 I am waiting for guests to come home, so... :) Jun 05 16:08:57 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 Jun 05 16:11:19 or is it >1000lux? Jun 05 16:11:33 NFC, anyway the patch works Jun 05 16:12:43 aah wait, the tupels are defining a threshold incl hysteresis, not a range Jun 05 16:15:26 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 Jun 05 16:17:10 each tuple defines the thresholds for downward and upword, for one ","-border in { 5, 5, 0, 0, 0, 0 } Jun 05 16:18:36 since we got two valif such tuples, we need *3* meaningful brightness levels in that { 5, 5, 0, 0, 0, 0 } Jun 05 16:21:12 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 Jun 05 16:21:31 (sorry for the typo) Jun 05 17:09:48 Why my ip was banned from talk on Maemo Jun 05 17:10:13 What did I do wrong Jun 05 17:10:16 ? Jun 05 17:13:47 nothing, just overzealous spam list and you are probably using dynamic ip Jun 05 17:14:45 pah. Jun 05 17:47:20 wikiwide, from root try, rmmod leds_lp5523 Jun 05 17:47:20 modprobe leds_lp5523 Jun 05 17:48:37 and then this: cat /sys/class/i2c-adapter/i2c-2/2-0032/selftest should blink all leds and print OK in command line Jun 05 18:03:09 you won't see such blinking Jun 05 18:03:24 it's way too short to usually get noticed Jun 05 18:05:04 ooh, I stand corrected, after testing it Jun 05 18:09:46 nice way to check for operational hardwate with minimal software involvement Jun 05 18:10:01 hardware* Jun 05 18:10:26 selftest is a LP5523-internal hw function Jun 05 18:11:00 ff__: nice catch Jun 05 18:11:25 yes, it should gives some additional information if something doesn't work Jun 05 18:12:34 yep, the chip checks if each of the LEDs draws correct current at correct voltage Jun 05 18:13:30 so it can detect all hw defects except a LED simply not emitting photons when operating Jun 05 18:13:58 don't know if that's even possible for a LED die Jun 05 18:16:40 by the way, is it possible indicate autofocus & whitebalance during record through gstreamer? Jun 05 18:16:59 no idea Jun 05 18:17:32 I _think_ both are managed by a blob shared lib Jun 05 18:18:15 maybe I'm mistaken and the lib isn't a blob Jun 05 18:19:00 or it has a documented API at least, where you can get that info from Jun 05 18:20:10 camera-ui2 aka nicocam has a focum length indicator, so the v4l2 stuff must provide it Jun 05 18:20:21 focus* Jun 05 18:22:04 yes, focus adjusting is done Jun 05 18:22:54 https://www.linuxtv.org/downloads/legacy/video4linux/API/V4L2_API/spec-single/v4l2.html maybe helps. No idea whatsoever about whitebal Jun 05 18:24:20 v4l2src has GstColorBalance Jun 05 18:24:53 but don't know how to use it Jun 05 18:27:28 needs at least 2 (prolly dimensionless) ints, I'd guess Jun 05 18:29:30 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? Jun 05 18:30:52 s/maje/make/ Jun 05 18:30:53 DocScrutinizer05 meant: how whitebalance works internally is a mystery to me. It's less mysterious when the picture has all colors so you could adjust to make a median or average or whatever fit a neutral point. But what when you shoot a tree format-filling? all just green, what... Jun 05 18:32:21 it adds some error probably, camerabin in gstreamer does the job, but not in v4l2src Jun 05 18:33:02 *but not with v4l2src Jun 05 18:33:25 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 Jun 05 18:34:49 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 Jun 05 18:35:40 Sony compactcam ultrafast autofocus: software Jun 05 18:37:26 fluid lens are fun :) Jun 05 18:37:42 hehe yes, but not exactly high quality Jun 05 18:38:11 neither suitable for decent aperture size Jun 05 18:38:34 and how speed performace with it? Jun 05 18:39:07 hm? I think that's their main advantage - mere speed Jun 05 18:39:19 plus no mechanics at all Jun 05 18:39:53 apply more voltage, make drop mor special Jun 05 18:40:02 works in milliseconds Jun 05 18:40:15 damn!! Jun 05 18:40:34 apply more voltage, make drop more spherical Jun 05 18:40:58 I didn't know that liquid lens has pretty poor quality Jun 05 18:41:13 it's a sperical lens Jun 05 18:41:28 of max a few millimeters diameter Jun 05 18:41:38 prolly more like 1 or 2 mm Jun 05 18:42:10 for a spherical lens it's maybe perfect Jun 05 18:42:59 but high class multi-lens setups use surprisingly complex lens shapes Jun 05 18:43:56 to reduce color aberration etc Jun 05 18:57:03 wow, seems they increased that stuff in scale quite a lot: http://www.varioptic.com/ Jun 05 18:58:29 http://www.varioptic.com/technology/liquid-lens-autofocus-af/ tha basics Jun 05 19:04:23 s/color/chromatic/ Jun 05 19:05:11 https://en.wikipedia.org/wiki/Chromatic_aberration Jun 05 19:06:15 maybe they meanwhile can use a spherical liquid lens in combination with a complex aspheric glass lens setup Jun 05 19:08:15 https://en.wikipedia.org/wiki/Aspheric_lens Jun 05 19:10:28 https://en.wikipedia.org/wiki/Aspheric_lens#/media/File:Mobile_phone_camera_lens_module,_3D_X-ray_microscopy_(30033111412).jpg ;-D Jun 05 19:21:41 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 Jun 05 19:26:24 so that's not for professional use, maybe for some action use Jun 05 19:27:11 have we uart or spi interface somwhere inside n900? Jun 05 19:29:05 second e-ink screen would be helpful, like that one http://waveshare.com/wiki/4.3inch_e-Paper_UART_Module Jun 05 19:56:04 UART yes. SPI too but not available to users Jun 05 19:56:20 UART though is on testpoints: console Jun 05 19:57:03 maybe you want hackerbus? ;-) Jun 05 19:57:10 ~neo900 hb Jun 05 19:57:15 ~#neo900 hb Jun 05 19:57:15 well, #neo900 hb is http://neo900.org/stuff/papers/hb.pdf and http://talk.maemo.org/showthread.php?p=1461954 Jun 05 20:00:08 yes, read this for now http://wiki.maemo.org/N900_Hardware_Hacking Jun 05 20:01:09 connect this e-ink to n900 (while it has exposed UART) seems to possible Jun 05 20:01:37 *seems to be possible Jun 05 20:07:17 yes, possible Jun 05 20:07:43 you need more than just UART though: power, and power control Jun 05 20:08:17 and levelshifter for UART Jun 05 20:09:44 you are right Jun 05 20:10:17 how to talk through this UART? Jun 05 20:10:37 err, prolly just use /dev/tty0 or somesuch Jun 05 20:14:07 ok, J2000 connectors under battery and /dev/ttyS0 Jun 05 20:20:04 without warranties, but yes :-) Jun 05 20:21:24 the voltage level is still a mystery, but I'd recommend assuming 1V8 Jun 05 20:22:06 as that's the level expected according to all datasheets and other docs available Jun 05 20:22:52 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<< Jun 05 20:24:08 you might want to ask a kernel hacker ( freemangordon?) for details about etk_d15/sdti_txd3 Jun 05 20:26:05 maybe he could even completely falsify what I found out regarding that stuff Jun 05 20:26:28 tbh it makes no sense to me Jun 05 20:34:04 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 Jun 05 20:34:58 (the original is in the [1] reference of above quote) Jun 05 20:35:32 in http://wiki.maemo.org/N900_Hardware_Hacking Jun 05 20:48:23 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) Jun 05 20:51:20 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 Jun 05 20:51:20 need convert few screenshots Jun 05 21:16:11 that should be easy. but honestly I think e-ink paper is better used in independent mode rather than mirroring mode, on N900 Jun 05 21:17:29 the qurstion actually is: what are the planned usecases Jun 05 21:18:59 I'd run a separate x11 server for e-ink display, and have that "screenshot" as an app within a "window" Jun 05 21:20:18 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 Jun 05 21:23:16 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 Jun 05 21:24:12 you can't "just lock the screen" since by definition that stops all running processes from updating their window content - to save energy Jun 05 21:24:55 any app that doesn't obey this rule wouldn't qualify for maemo-extras in testing Jun 05 21:25:47 you need a launcher that can start apps on display:1.0 - the e-ink display Jun 05 21:26:20 this way you could for example have a clock on e-.ink Jun 05 21:27:05 maemo-notifier could get tweaked to use both displays concurrently Jun 05 21:29:58 don't know how use x11 server with UART Jun 05 21:30:33 err well, it's a question how to implement the framebuffer, no? Jun 05 21:31:03 essential is what you sed, what are the planned usecases Jun 05 21:35:53 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 Jun 05 21:37:02 maybe an inspiration, though aiui the e-ink display can do better than only ascii art: https://linux.die.net/man/3/aa_render Jun 05 21:37:38 anyway you see people implemented framebuffers even on ascii-only displays Jun 05 21:37:57 shouldn't be hard to implement a framebuffer talking to UART Jun 05 21:38:30 >>This function does the trick of converting the emulated framebuffer into high quality ASCII-art<< Jun 05 21:48:27 ((simple script)) yes, for that you should look into printing (lpr et al) Jun 05 21:49:47 cups etc exist for maemo, and a UART/serial ascii-only printer is easy to configure in cups Jun 06 01:30:16 DocScrutinizer : Thank you, keeping device battery-less for about 30s resolved the LEDs problem. And, I don't know what's up with battery coin cell, but it forgot time&date (as I expected it would; usually, I speed-swap batteries, to keep it from forgetting temporal location) Jun 06 01:30:58 it's dead Jun 06 01:31:06 they're virtually all dead by now afaik Jun 06 01:31:25 replaceable with a soldering iron tho Jun 06 01:31:28 yep, you'll have to replace it with one of those capacitors Jun 06 01:31:47 (why weren't these capacitors in the first place?) Jun 06 01:32:10 because they can't hold for long Jun 06 01:32:27 having a few orders of magnitude less energy in them Jun 06 01:33:25 and no one would have expected n900 to be the last successful gnu/linux device by nokia being preserved by a bunch of fans this long Jun 06 01:33:57 the RTC can draw off the main battery even when powered off right? Jun 06 01:34:03 yes Jun 06 01:34:06 a tiny bit Jun 06 01:36:15 the bupbat dies after ~12 monts usually Jun 06 01:36:23 ~bupbat Jun 06 01:36:24 from memory, 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 Jun 06 01:36:26 :D Jun 06 01:36:54 mine was visibly leaked like a coin battery Jun 06 01:37:09 yeah, some even leak Jun 06 01:37:42 either they were a complete crap product, or Nokia and OM soldered them too hot Jun 06 01:38:07 I don't think there was any reasonable use case where someone would take the battery/leave it flat for 6 months and still expect alarms to work Jun 06 01:39:02 it's just been best common practice to use LiMg(?) cell for that Jun 06 01:39:52 or maybe LiSOCl2 battery if they're available in the tiny coin form factor Jun 06 01:40:16 I've got a powermac G5 that still functions with its original PRAM battery about 15 years on... Jun 06 01:40:28 when it turned out those are crap, everybody moved to supercaps like ^^^ PAS414HR. Then flat phones with non-removable main battery became fashion and nobody needed any bupbat anymore Jun 06 01:41:36 s/supercaps like ^^^ PAS414HR/Polyacene supercaps/ Jun 06 01:41:37 DocScrutinizer05 meant: when it turned out those are crap, everybody moved to Polyacene supercaps. Then flat phones with non-removable main battery became fashion and nobody needed any bupbat anymore Jun 06 01:45:42 Given that my ALS is obscured with a paper sticker (will take another year for it to wear off), I would need a really bright flashlight to get through to the light sensor. Would it make sense, at some time in distant future, to make all these brightness values user-editable (like LED patterns), instead of hard-coded? Or would it be too slow, ineffi Jun 06 01:45:42 cient, unreliable? Jun 06 01:47:29 removing a paper sticker is easier than fixing it in software Jun 06 01:48:23 Yes, I know. But even when I set brightness at 1/5, and ASL thinks it to be night, I still find the display to be too bright at times (especially when it is night) Jun 06 01:48:53 Oksana: try baby oil? Jun 06 01:49:13 that's the "gentle" way to dissolve stickers, just takes som time Jun 06 01:49:18 afair there's a lower limit on the brightness level Jun 06 01:49:52 not sure if it's a hardware-bound limitation Jun 06 01:50:17 maybe the brightness range exposed to user is coarser than actual pwm settings range Jun 06 01:52:08 Yes, brightness level exposed to user in Settings is coarse. Actual brightness is based on both ASL (ambient brightness) and user setting? Jun 06 01:52:10 * L29Ah_ doesn't remember himself using n900 in actual darkness with accommodated eyes Jun 06 01:59:43 Forbidden Jun 06 01:59:43 You don't have permission to access / on this server. Jun 06 01:59:52 wiki.maemo.org is being a bitch again Jun 06 02:04:10 the range of influence of asl on the brightness is way too narrow Jun 06 02:05:18 as for me it should be max(1,asl * user brightness setting) Jun 06 02:05:57 and shut off the backlight completely when asl shows values over 10klux or so Jun 06 02:12:21 Okay... In darkness, have minimum brightness (1), in normal light get brighter together with ambient, in too bright light switch off the backlight (because transreflective?) Jun 06 02:38:28 L29Ah_: it already does the latter Jun 06 02:39:36 the minimum is "1" in /sys/class/backlight/acx565akm/brightness Jun 06 02:40:01 and SpeedEvil considered it too bright Jun 06 02:43:41 the problem with brightness setting is probably it's a mere PWM power percentage setting (in milliWatt, or % ontime vs offtime with 400Hz PWM) while physiological brightness is logarithmic - you need to half the power to sense any difference in brightness Jun 06 02:44:18 so: 256, 128, 64, 32, 16, 8, 4, 2, 1 Jun 06 02:44:40 5 steps are basically OK Jun 06 02:45:47 for a 8bit linear value Jun 06 02:46:15 it's the missing steps between 1 and 0 that hurts, I guess Jun 06 02:48:01 btw it's Ambient Light Sensor Jun 06 02:48:15 ALS Jun 06 02:48:52 /sys/class/i2c-adapter/i2c-2/2-0029/lux Jun 06 02:51:27 fun factoid re backlight: there are TWO ways to control it: acx565akm/brightness, plus a GPIO or even PWM (I didn't check details) from CPU itself Jun 06 02:51:49 I also never tried to use the second one Jun 06 02:52:20 no idea what for the Nokia EEs implemented it Jun 06 02:52:43 05:43:42] the problem with brightness setting is probably it's a mere PWM power percentage setting (in milliWatt, or % ontime vs offtime with 400Hz PWM) while physiological brightness is logarithmic - you need to half the power to sense any difference in brightness Jun 06 02:52:44 physiological brightness is irrelevant when we're comparing it against illuminance provided by asl Jun 06 02:52:59 als Jun 06 02:53:09 who compares what? Jun 06 02:53:29 05:38:29] L29Ah_: it already does the latter Jun 06 02:53:29 no, i see it is able to set much lower brightness when it's about to shut the display off completely due to lock timeout Jun 06 02:54:09 o.O what? Jun 06 02:54:19 sorry you lost me Jun 06 02:54:29 or prolly I lost you Jun 06 02:55:07 the latter == shut off the backlight completely when asl shows values over 10klux or so Jun 06 02:55:44 oh nvm disregard the timeout thing Jun 06 02:55:53 it actually does that on the lowest brightness setting Jun 06 02:56:15 but it is bad you must adjust the brightness settings to the ambient light manually Jun 06 02:56:16 does what? Jun 06 02:56:34 I don't get a word of what you say Jun 06 02:56:38 comes to the brightness level that is used a second before the screen lock timeout Jun 06 02:58:15 although it's 7, not 1 Jun 06 02:58:23 also 0 = 1 on my n900 Jun 06 02:58:26 and the lowest is 2 Jun 06 02:58:57 er, nope Jun 06 02:59:03 damn timeout Jun 06 02:59:26 okay, the lowest is 1, but it is never set by the brightness control logic **** ENDING LOGGING AT Tue Jun 06 03:00:02 2017