| 00:13.31 | *** join/#maemo-ssu _xnt14 (~xnt14@xceleo.us) |
| 00:26.32 | *** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no) |
| 00:56.40 | *** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no) |
| 01:09.37 | *** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no) |
| 01:15.57 | *** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no) |
| 01:32.15 | *** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no) |
| 01:50.12 | *** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no) |
| 02:15.25 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 02:36.59 | *** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no) |
| 03:03.47 | *** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 03:49.42 | *** join/#maemo-ssu jon_y (~enforcer@swz-173-88.tm.net.my) |
| 05:20.03 | DocScrutinizer05 | anybody ready for fun with sftp? |
| 05:20.27 | DocScrutinizer05 | I have a rather strange bug in KDE |
| 05:20.43 | DocScrutinizer05 | (maybe not limited to KDE) |
| 05:21.20 | DocScrutinizer05 | you probably know ~/.ssh/id_dsa.pub |
| 05:22.02 | DocScrutinizer05 | AIUI it's just needed on targets, not on origin of a ssh/sftp connection |
| 05:22.14 | DocScrutinizer05 | even there it's called known_hosts |
| 05:23.15 | DocScrutinizer05 | so obviously there's nothing wrong with `mv id_dsa.pub id_dsa.pub-away` |
| 05:24.03 | DocScrutinizer05 | sftp://user@host:port still works great, in both konqueror and dolphin |
| 05:25.11 | DocScrutinizer05 | but!! only once, since then some sneaky magic created a new id_dsa.pub, alas a crippled truncated one, and next connection via sftp:// will fail due to that :-o |
| 05:26.50 | DocScrutinizer05 | plus each time you open a normal ssh connection it spamms that trunkated key for a greeting |
| 05:28.21 | DocScrutinizer05 | err, correction: |
| 05:28.33 | DocScrutinizer05 | even there it's called authorized_keys |
| 06:04.14 | *** join/#maemo-ssu Guest57704 (~rd@p57B4847F.dip0.t-ipconnect.de) |
| 07:08.22 | *** join/#maemo-ssu timo^ (~timo@unaffiliated/tiempjuuh) |
| 07:34.56 | *** join/#maemo-ssu amiconn (amiconn@rockbox/developer/amiconn) |
| 07:56.34 | *** join/#maemo-ssu fw190 (~fw190@user-188-33-151-143.play-internet.pl) |
| 07:56.57 | fw190 | DocScrutinizer05: I vanished yesterday as I was on my last legs |
| 07:57.02 | fw190 | all went well |
| 07:57.06 | fw190 | LXDE works ok |
| 07:57.58 | fw190 | I installed patterns-opensuse-lxde and it pulled everything as it should |
| 07:58.08 | fw190 | thanks for the tips yesterday |
| 08:00.24 | kerio | fw190: how's lxde? |
| 08:00.30 | kerio | and have you realized that it's worse than xfce? |
| 08:07.08 | fw190 | kerio: well it looks like lxde |
| 08:07.16 | fw190 | newver used xfce |
| 08:07.26 | kerio | to be fair, the latest xfce is somewhat bad |
| 08:07.29 | kerio | it used to be good |
| 08:07.44 | fw190 | everyone is saying that lxde is lighter |
| 08:07.51 | fw190 | so I stick to it |
| 08:08.00 | kerio | xfce used to be the "light" DE |
| 08:08.10 | kerio | then it became heavier |
| 08:08.14 | fw190 | but comparing with KDE I do not see much speed improvment |
| 08:08.23 | kerio | well, is KDE slow for you? |
| 08:08.27 | fw190 | no |
| 08:09.56 | kerio | :) |
| 08:10.33 | fw190 | I just have to find the settings which changes from one click to two |
| 08:10.43 | fw190 | although I'm starting to get used to it |
| 08:20.31 | fw190 | just found it |
| 08:20.34 | fw190 | have to say it |
| 08:20.44 | fw190 | this suse thingy looks better and better to me |
| 08:34.13 | *** join/#maemo-ssu CodenameStrike (~assassin@210.195.80.229) |
| 08:35.39 | *** join/#maemo-ssu CodenameStrike (~assassin@210.195.80.229) |
| 08:59.14 | *** join/#maemo-ssu NIN101 (~NIN@p5DD29167.dip0.t-ipconnect.de) |
| 09:04.45 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
| 09:06.26 | *** join/#maemo-ssu Pali (~pali@unaffiliated/pali) |
| 09:13.45 | freemangordon | merlin1991: http://talk.maemo.org/showthread.php?p=1274218#post1274218 |
| 09:14.21 | merlin1991 | freemangordon: I just saw it |
| 09:14.36 | freemangordon | you'd better disable ipv6 DNS until everyone is on CSSU :D:D:D |
| 09:14.57 | merlin1991 | ipv6 has been there all the time |
| 09:15.05 | merlin1991 | I wonder why it fails now |
| 09:15.10 | freemangordon | hmm, then it is your ISP |
| 09:15.22 | freemangordon | lemme try on my device |
| 09:18.42 | freemangordon | well, ping6 fails here as well, but I don't have problems with apt-get update |
| 09:19.48 | merlin1991 | odd, http://centralops.net/co/Ping.aspx for example works |
| 09:20.45 | freemangordon | merlin1991: in the meantime: |
| 09:20.46 | freemangordon | http://maemo.merlin1991.at/cssu/develdebs/gcc-4.7.2_fremantle_armel/scratchbox-toolchain-linaro-4.7-2012.09-fremantle-armv7a_1.0.17_i386.deb |
| 09:20.50 | *** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua) |
| 09:21.03 | *** join/#maemo-ssu CodenameStrike (~assassin@210.195.80.229) |
| 09:21.41 | merlin1991 | freemangordon: btw what do you get for ping6 ipv6.google.com on your device? |
| 09:21.56 | freemangordon | network unreachable |
| 09:22.41 | merlin1991 | also you have 384 dl of the mp so far :D |
| 09:22.49 | freemangordon | wow |
| 09:23.07 | int_ua | hey, I just got second N900 ^_^ |
| 09:23.19 | freemangordon | hmm, not good, i'd better not screw with pulseaudio :D:D:D |
| 09:23.25 | merlin1991 | int_ua: welcome to the club of madmen who own several n900s :D |
| 09:23.43 | int_ua | but haven't slept 28 hours) |
| 09:23.53 | int_ua | see you tomorrow :) |
| 09:24.01 | merlin1991 | have a nice sleep :) |
| 09:24.11 | int_ua | thanks :) |
| 09:24.14 | freemangordon | int_ua: night |
| 09:24.28 | merlin1991 | freemangordon: do we have dig on the device? |
| 09:24.43 | freemangordon | nslookup? |
| 09:24.53 | freemangordon | not sure for dig |
| 09:25.00 | merlin1991 | dang dig is so much better :P |
| 09:25.23 | merlin1991 | currently has no n900 nearby, all 4 of them are ~65 km away from him |
| 09:25.37 | *** join/#maemo-ssu arcean (~arcean@aaem131.neoplus.adsl.tpnet.pl) |
| 09:26.10 | merlin1991 | hm I could drop the ipv6 dns entry on maemo.merlin1991.at |
| 09:26.20 | merlin1991 | aka AAAA entry |
| 09:33.58 | freemangordon | merlin1991: need to reboot my PC |
| 09:34.18 | merlin1991 | ~lart rndc |
| 09:34.18 | infobot | installs PocketPC on rndc's PDA |
| 09:35.42 | *** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
| 09:37.44 | freemangordon | merlin1991: no idea, but that should be something with bind (or whatever DNS server you use) |
| 09:39.00 | merlin1991 | well I wonder why his/her n900 decided to query the dns for AAAA instead of A entries |
| 09:39.12 | merlin1991 | ah wait |
| 09:39.45 | merlin1991 | afaik I set up ipv6 dns entries on my side, but the guy who hosts the real dns servers had ipv6 disabled on his bind back then |
| 09:47.16 | kerio | freemangordon pls |
| 10:00.52 | *** join/#maemo-ssu dhbiker (~dhbiker@APN-122-88-230-gprs.simobil.net) |
| 10:27.39 | merlin1991 | gotta love my university, finally found my course which has a description page that is awesomely emtpy except an entry about some jabber chatroom, so I dl psi try to remember my jabber pw again, and finally logon, to find the chat room empty |
| 10:27.40 | merlin1991 | yay |
| 10:38.39 | kerio | yo merlin1991 |
| 10:38.45 | kerio | can we update connui-home-cellular pls |
| 10:39.24 | DocScrutinizer05 | yo dawg, heard you like info. So we put info about info into info of your course |
| 10:40.03 | merlin1991 | kerio: eh is there anyhting new on gitorious? |
| 10:40.15 | DocScrutinizer05 | yo dawg, heard you like chat... ;-P |
| 10:40.16 | kerio | merlin1991: the logging fix |
| 10:40.58 | DocScrutinizer05 | is it complete |
| 10:41.00 | DocScrutinizer05 | ß |
| 10:41.02 | DocScrutinizer05 | ? |
| 10:41.33 | merlin1991 | ah yeah http://gitorious.org/community-ssu/operator-name-cbs-widget/commit/ff96ce3653b9951158badc150cb4c62aec28b1fc |
| 10:41.49 | DocScrutinizer05 | still, is it *complete* now? |
| 10:42.06 | DocScrutinizer05 | has anybody finally *tested* that ? |
| 10:42.18 | kerio | tested what? |
| 10:42.22 | kerio | the whole thing or just that fix? |
| 10:43.14 | DocScrutinizer05 | takes a huge sip of his coffe, and breathes deep |
| 10:43.51 | DocScrutinizer05 | the fact that/if log files won't appear despite logging off, with random loglines in them |
| 10:44.35 | merlin1991 | kreio wanna play guinea pig? |
| 10:44.51 | merlin1991 | s/kreio/kerio/ |
| 10:44.59 | merlin1991 | should use tab instead of typing myself :P |
| 10:45.01 | kerio | sure, why not |
| 10:45.14 | merlin1991 | hits the reboot button |
| 10:46.07 | DocScrutinizer05 | merlin1991: btw I yesterday spotted something I'd frown on as a pretty evil flaw in maemo boot UX |
| 10:46.50 | DocScrutinizer05 | fsck gets started without *any* feedback to user about "prepare to watch your device acting_bricked" |
| 10:47.05 | kerio | DocScrutinizer05: to be fair it's ext3 fsck |
| 10:47.23 | kerio | it's journaled and stuff |
| 10:47.32 | DocScrutinizer05 | well, my fsck.ext3 takes quite some time here |
| 10:47.46 | DocScrutinizer05 | naw, fsck doesn't use journal |
| 10:48.15 | DocScrutinizer05 | once you need or want fsck, you forget about journal. |
| 10:48.25 | DocScrutinizer05 | journal is for not needing fsck at all |
| 10:48.46 | DocScrutinizer05 | basically&afaik |
| 10:49.05 | DocScrutinizer05 | anyway my fsck.ext3 here takes dozens of minutes |
| 10:49.10 | DocScrutinizer05 | on PC |
| 10:49.11 | kerio | tune2fses his mmcblk0p2 |
| 10:49.42 | merlin1991 | hm regarding fucked up course pages, http://ti.tuwien.ac.at/rts/teaching/courses/osue/ is the best so far timeout when trying to access it |
| 10:50.20 | merlin1991 | why the fuck can't they use the centralized information system, every single stupid course has a link to their "own" homepage that doesn't work most of the time |
| 10:50.59 | DocScrutinizer05 | yeah, down4me2 |
| 10:51.20 | DocScrutinizer05 | yo dawg... |
| 10:51.39 | merlin1991 | and the best thing about it, the semester begins tomorrow, and guess what, the course in question has a reservation for a room on monday |
| 10:52.04 | DocScrutinizer05 | errrwut? |
| 10:52.22 | DocScrutinizer05 | sounds like it's a sane thing |
| 10:52.32 | DocScrutinizer05 | surprisingly sane? |
| 10:52.33 | kerio | tomorrow my courses begin too ^_____^ |
| 10:53.00 | merlin1991 | kerio: what do you study? |
| 10:53.05 | kerio | math |
| 10:53.25 | merlin1991 | ah yeah /me forgot |
| 10:53.30 | DocScrutinizer05 | merlin1991: call the Prof on Sunday noon ;-P "Hey Prof, where's the room?" |
| 10:53.58 | DocScrutinizer05 | that explains some bits |
| 10:54.11 | merlin1991 | call the prog "sup dwag, I heard you like questions in questions, so what's up with the page and which room would it show?" :D |
| 10:54.17 | merlin1991 | s/prog/prof/ |
| 10:55.02 | DocScrutinizer05 | aaah, that makes more sense than prog ;-) |
| 10:56.45 | merlin1991 | oh ffs automake madness in my sb again |
| 10:57.48 | DocScrutinizer05 | merlin1991: less +/else /etc/event.d/rcS-late |
| 10:58.38 | DocScrutinizer05 | waddooyathink? Add some LP5523 machine pattern for notifier LED? |
| 11:00.49 | merlin1991 | hm what's the right way (tm) to edit symlinks in /etc/alternatives ? |
| 11:02.44 | DocScrutinizer05 | err |
| 11:03.03 | DocScrutinizer05 | usually postinst does that afaik |
| 11:03.24 | DocScrutinizer05 | prolly there's even a scriptie dedicated to that daunting task |
| 11:03.58 | merlin1991 | seems to be update-alternatives, but it keep claiming that there's no alternative for aclocal |
| 11:05.24 | kerio | replacing rcS-late will fuck up soooooooooo many things |
| 11:06.12 | DocScrutinizer05 | kerio: please elaborate |
| 11:06.34 | kerio | well, it's the place where a lot of system mods live |
| 11:06.48 | DocScrutinizer05 | that's what patch is meant for |
| 11:06.48 | kerio | people with weird swaps, people with strange partitioning... |
| 11:07.18 | DocScrutinizer05 | and if we don't have patch, we still can use sed to tweak whatever sits in /etc/event.d/rcS-late. |
| 11:07.26 | merlin1991 | kerio: http://cdnm.at/~christian/maemo/cssu/connui-home-cellular/ |
| 11:07.51 | DocScrutinizer05 | and if even that's not feasible or PC, we can wrap fsck.* by a wrapper taking care about proper user-notification |
| 11:08.15 | merlin1991 | srly why don't people ever use dpkg-divert on packaged scripts they edit? |
| 11:08.31 | kerio | merlin1991: because they don't know how dpkg works |
| 11:09.34 | merlin1991 | It's so stupid to go "uh I'm gonna edit this file here and don't think about anything but my immediate gain" |
| 11:09.36 | DocScrutinizer05 | why don't we just use proper md5sum checks to detect edited config/scrript files and do like all good updaters: install xyfile.new instead of overwriting xyfile unconditionally? |
| 11:09.53 | kerio | DocScrutinizer05: guess what, apt actually does that |
| 11:09.54 | kerio | it asks the user |
| 11:09.57 | kerio | (for config files) |
| 11:10.01 | kerio | (for modified config files) |
| 11:10.05 | DocScrutinizer05 | thought as much |
| 11:10.14 | merlin1991 | 2 reasons, firstly there is no such support for scripts in dpkg |
| 11:10.24 | merlin1991 | only for "configfiles" and stuff in /etc |
| 11:10.31 | kerio | "config file modified, install (N)ew, keep (O)ld, show (D)iff, ask (L)ater" |
| 11:10.33 | merlin1991 | and secondly, because ham! |
| 11:10.59 | DocScrutinizer05 | ~fsck HAM |
| 11:10.59 | infobot | e2fsck /dev/HAM : warning! filesystem contains dumbasses! |
| 11:11.00 | kerio | merlin1991: opername.log seems to not appear |
| 11:11.28 | DocScrutinizer05 | kerio: good |
| 11:11.46 | DocScrutinizer05 | now please also check if enabling logging will change that |
| 11:12.24 | DocScrutinizer05 | also check if that silly timestamp got fixed |
| 11:13.41 | merlin1991 | kerio: you got this fix aswell: http://www.gitorious.org/community-ssu/operator-name-cbs-widget/commit/95ca519c5b29dfb7a7692f19828781ddfcc29d63 |
| 11:13.46 | merlin1991 | DocScrutinizer05: which silly timestamp? |
| 11:13.53 | DocScrutinizer05 | merlin1991: no comment from your side about general nastiness to start fsck.* and let user stare at moving dots for 'hours'? |
| 11:14.13 | kerio | merlin1991: the timestamp in the connui logs is 01120930 |
| 11:14.17 | merlin1991 | eh no n900 so no chance to comment till later this evening |
| 11:14.20 | DocScrutinizer05 | merlin1991: the 19112 |
| 11:14.24 | DocScrutinizer05 | year |
| 11:15.09 | DocScrutinizer05 | merlin1991: (comment) mompls, I pastebin the rcs-late for you |
| 11:18.12 | merlin1991 | is about to fix the fsckd timestamp |
| 11:18.22 | merlin1991 | what's the timestamp log convention? |
| 11:18.28 | DocScrutinizer05 | http://maemo.cloud-7.de/maemo5/etc/events.d/rcS-late |
| 11:19.06 | merlin1991 | oh nice, autofsck |
| 11:19.16 | DocScrutinizer05 | yeah |
| 11:19.25 | DocScrutinizer05 | without any notification to user |
| 11:19.40 | DocScrutinizer05 | a bug in my book |
| 11:22.46 | merlin1991 | kerio: did you enable the log and check it? |
| 11:22.57 | kerio | no |
| 11:22.59 | merlin1991 | judging from the source the timestamp should have a format of xx.xx.xx xx:xx:xx |
| 11:23.42 | merlin1991 | though the order on the xx.xx.xx is day month year which imo should be the other way around :P |
| 11:25.09 | merlin1991 | so we have 3 things for next -testing already, openssl dbg strip, connui-home-cellular logfix + namefix and camera-ui updates |
| 11:27.15 | *** join/#maemo-ssu ZogG (~zoggrules@funtoo/user/ZogG) |
| 11:27.56 | merlin1991 | DocScrutinizer05/kerio please test something reagarding camera-ui, set the captured image preview to unlimited, take a pic and the delete it in the preview window |
| 11:28.07 | merlin1991 | do you get the viewfinder back or a black screen? |
| 11:28.55 | DocScrutinizer05 | "happy" that I still can test that ;-P |
| 11:30.19 | DocScrutinizer05 | though, first of all, WTF do I configure the review timing? |
| 11:30.59 | merlin1991 | there's a wrench symbol somewhere on the side of the screen iirc |
| 11:31.11 | merlin1991 | or it's one of the buttons on the bottom lef |
| 11:31.13 | merlin1991 | +t |
| 11:31.29 | DocScrutinizer05 | alas the menu under wrench has no fsckng setting for that |
| 11:31.44 | DocScrutinizer05 | got it |
| 11:31.52 | DocScrutinizer05 | 2nd left on bottom left |
| 11:32.56 | kerio | i get the viewfinder back |
| 11:33.55 | merlin1991 | good, then mag did compile that one |
| 11:37.26 | merlin1991 | so the new stuff in camera ui would be launcher support and proper cam directory code |
| 11:38.14 | DocScrutinizer05 | video is totally useless |
| 11:38.20 | DocScrutinizer05 | slow as molasses |
| 11:38.32 | DocScrutinizer05 | takes like 20s to start capture |
| 11:38.44 | merlin1991 | might be faster with the coming update |
| 11:38.45 | DocScrutinizer05 | but yes, viewfinder comes back |
| 11:39.06 | DocScrutinizer05 | autofocus distance is totally wrong 90% of the times |
| 11:39.43 | merlin1991 | well that's still the same as with the stock camera |
| 11:40.10 | DocScrutinizer05 | hitting play button in preview opens mediaplayer. Deleting video file there and then closing mp returns me to preview where I could delete *again* |
| 11:41.07 | DocScrutinizer05 | closing preview seems to freeze the whole system for several seconds, until viewfinder re-appears |
| 11:41.42 | merlin1991 | don't hate so much on our beloved cam :D |
| 11:45.07 | kerio | DocScrutinizer05: camera-ui in cssu-thumb is much, much faster :3 |
| 11:45.35 | DocScrutinizer05 | and the worse: it seems to ignore trigger button presses that are shorter than 0.5s |
| 11:45.57 | DocScrutinizer05 | obviously trackerd all the time hogs CPU like mad |
| 11:46.56 | DocScrutinizer05 | while it *should* *just* 'index' the _one_ media file that just got created/deleted, and then STFU again |
| 11:47.18 | DocScrutinizer05 | (unconfirmed by any means like htop etc!) |
| 11:47.33 | DocScrutinizer05 | (just cpu load widget constantly red) |
| 11:48.38 | DocScrutinizer05 | honestly tracked needs to get suspended during realtime stuff like camera usage |
| 11:50.36 | DocScrutinizer05 | when you short a rapid sequence, "rapid" like >1pic/s (if that's even possible), you for sure don't need any friggin trackerd hogging system resources for indexing that as well could be done later |
| 11:51.02 | DocScrutinizer05 | same when you return from preview to viewfinder |
| 11:51.40 | DocScrutinizer05 | as long as there's viewfinder visible, trackerd has to go hybernate mode |
| 11:52.32 | DocScrutinizer05 | may just store up dbus msgs about media files to examine, for later processing |
| 11:53.13 | DocScrutinizer05 | but to answer your question: yes, viewfinder comes back... eventually ;-P |
| 11:54.17 | DocScrutinizer05 | UX however is like with a 1880's camera XP |
| 11:55.08 | DocScrutinizer05 | "please don't move!" PFOOOOSH-FLASH <magnesia smoke goes up> |
| 11:55.42 | DocScrutinizer05 | "please stay! I'm just inserting another plate" |
| 12:02.03 | DocScrutinizer05 | on a "stock" PR1.3 (PK47 or sth, my t900 devel device), turnaround for the sequence >start video capture, stop video capture, review shows up, hit delete in preview, hit "ok", returns to viewfinder, start video capture< is like 5 times faster than on CSSU-T |
| 12:02.48 | DocScrutinizer05 | also reacts reliably on short trigger button push |
| 12:02.58 | DocScrutinizer05 | reliably and instantly |
| 12:03.19 | DocScrutinizer05 | not with 2s delay like nicocam/cssu-t |
| 12:03.59 | kerio | DocScrutinizer05: cache? |
| 12:04.09 | DocScrutinizer05 | honestly, this stuff isn't ready for prime time |
| 12:04.44 | kerio | it's pretty fast here, idk |
| 12:05.09 | kerio | ...actually you could try it too, you have a n900 with cssu-thumb installed |
| 12:06.23 | DocScrutinizer05 | I just tried on cssu-thumb by mistake, looked all the same like on cssu-t |
| 12:07.36 | kerio | DocScrutinizer05: is it updated? |
| 12:07.46 | kerio | nicocam was thumbified recently |
| 12:08.12 | DocScrutinizer05 | kerio: well, actually cssu-thumb is significantly faster than cssu-t, but still not as fast as stock |
| 12:09.10 | DocScrutinizer05 | esp invocation of preview and return to viewfinder after hitting "ok" for delete is still sluggish, compared to stock |
| 12:09.32 | DocScrutinizer05 | while reaction to trigger button is almost bearable |
| 12:09.45 | DocScrutinizer05 | both for starting and stopping capture |
| 12:12.36 | DocScrutinizer05 | but... could it be that charging is completely fsckdup in cssu-thumb? |
| 12:14.42 | kerio | D: |
| 12:14.46 | kerio | why would it be? |
| 12:14.52 | kerio | bme is the same |
| 12:15.33 | DocScrutinizer05 | somehow device been stuck at "USB mode: just charging" in sysmenu. When I click it, the selector AssRage/PCShit pops up. Selecting AssRage gives me another notifier "not possible, storage already in use" |
| 12:16.09 | DocScrutinizer05 | I plugged and unplugged USB 10 or 15 times before that, and it didn't even recognize |
| 12:16.29 | kerio | well, maybe the storage is in use |
| 12:16.34 | DocScrutinizer05 | NB all the above been with USB *detached* |
| 12:16.39 | kerio | haha |
| 12:16.39 | kerio | neat |
| 12:16.44 | kerio | ~n900-full-reset |
| 12:16.44 | infobot | methinks n900-full-reset is when the user presses the PWRON (power-on) button for 8 seconds and removes the battery in the next 8 seconds, the TPS65950 enters NO SUPPLY state instead of BACKUP state, even if a valid backup battery is present. In such a situation, the backup domain registers are also reset, along with the VRRTC domain registers. |
| 12:17.19 | kerio | well, ke-recv isn't thumby |
| 12:17.41 | DocScrutinizer05 | nah, now after that error-msg I quoted, it's back to normal. I inserted USB and it did "swooooosh" and notifier about charging came up |
| 12:18.18 | DocScrutinizer05 | I guess something severely fsckd up in recent KP, regarding fast charger detect |
| 12:18.23 | DocScrutinizer05 | and related stuff |
| 12:19.59 | DocScrutinizer05 | h-e-n had to get over quite some headache due to this abomination of "layering violations" when reading /sys/*/*/charger nukes PHY settings and thus messes up musb-hdrc driver state |
| 12:20.40 | DocScrutinizer05 | we had "some asshole is trying to probe for charger" klog in original h-e-n kernel. dunno what happened to it |
| 12:20.51 | kerio | hah |
| 12:20.56 | kerio | please, tell me that was the actual message |
| 12:21.04 | DocScrutinizer05 | yes |
| 12:21.08 | DocScrutinizer05 | verbatim |
| 12:21.10 | kerio | =D |
| 12:21.59 | DocScrutinizer05 | should've told a story to devels messing with it (/me glares at pali) |
| 12:22.27 | kerio | Pali: *glare* |
| 12:23.08 | DocScrutinizer05 | you MUST NOT probe for D+- short during musb-hdrc has 'allocated' USB to do meaningful stuff like ENUM or data transfer! |
| 12:23.11 | DocScrutinizer05 | ~2119 |
| 12:23.12 | infobot | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. |
| 12:23.31 | Pali | new kernel-power has patch which disable that sysfs node charger when host mode is active |
| 12:24.06 | DocScrutinizer05 | well, this probelm isn't hostmode specific |
| 12:24.17 | Pali | when musb go back to peripheral mode, then charger detection is enabled again |
| 12:24.19 | DocScrutinizer05 | welcome Pali :-) |
| 12:27.24 | DocScrutinizer05 | Pali: iirc musb-hdrc'.ko' initializes PHY as soon as somebody tries to do something over USB, like e.g. enable mass storage mode, or PC-Suite (or hostmode, yes). Any subsequent probing for D+- short nukes those PHY config settings and renders whole USB in an undefined defunct state |
| 12:28.02 | DocScrutinizer05 | no matter if done via /sys readout, or via direct call to related musc-hdrc function |
| 12:28.14 | DocScrutinizer05 | (aka kernel-internal) |
| 12:29.19 | DocScrutinizer05 | the even more funny stuff about that: PHY gets backed up via main bat even during real device powerdown |
| 12:29.49 | DocScrutinizer05 | so any such mess is relatively sticky, until musb-hdrc takes care to initialize it again the proper way |
| 12:30.30 | DocScrutinizer05 | and!!! there's NO way to really reliably reset PHY, unlike twl4030 |
| 12:31.08 | DocScrutinizer05 | only reliable reset is: remove main bat, short + and - battery contacts in device. wait 10 minutes (to be sure) |
| 12:31.49 | DocScrutinizer05 | if PHY is misconfigured, even flatbatrecover may fail |
| 12:32.10 | DocScrutinizer05 | since it depends on PHY detecting D+- short and signalling it to bq24150 |
| 12:32.13 | kerio | DocScrutinizer05: why do you need to short + and -? :o |
| 12:32.26 | DocScrutinizer05 | to discharge buffer capacitors |
| 12:32.48 | DocScrutinizer05 | there are quite some huge cubes on Vbat |
| 12:32.53 | DocScrutinizer05 | several 100 uF |
| 12:34.01 | kerio | DocScrutinizer05: does a working bupbat screw with this, too? |
| 12:34.18 | kerio | also, do i have a problem if my usb works? |
| 12:34.23 | DocScrutinizer05 | and there's no *reliable* way to discharge them in a short time, though trying power button during battery removed may help |
| 12:34.44 | DocScrutinizer05 | no, as long as your usb and charging works, no problem |
| 12:34.59 | kerio | hmm, does this also mean that in case of water damage, you're basically screwed? |
| 12:35.19 | kerio | if removing the battery still leaves quite a bit of charge |
| 12:35.32 | DocScrutinizer05 | if however charging doesn't kick in, or device thinks it's connected to PC while in fact it's connected to fastcharger or to nothing at all, odds are this is cause by PHY |
| 12:36.51 | DocScrutinizer05 | kerio: nope, since the reason for battery removal on water incidents is to stop electrolysis which means rapid discharge of buffer capacitors if they actually seen shorts by water |
| 12:37.27 | kerio | oh, so it basically solves itself |
| 12:37.28 | kerio | i see |
| 12:37.41 | DocScrutinizer05 | lemme put it this way: if water shorts your + and -, your capacitors are empty during few seconds |
| 12:38.24 | DocScrutinizer05 | for buffering PHY 1707 on a intact device however they may last for hours |
| 12:38.48 | kerio | got it |
| 12:38.56 | kerio | to reset PHY, i must dunk my device in water |
| 12:39.05 | DocScrutinizer05 | yeah, kinda |
| 12:40.27 | DocScrutinizer05 | (disclaimer: all the above is not verified on a normal scientific level, but rather just off top of my head without properly checking each detail) |
| 12:40.59 | DocScrutinizer05 | which *usually* is just good enough for any RL purpose ;-D |
| 12:41.20 | kerio | to be honest i don't remember the last time i connected my n900 to my pc when fremantle was booted |
| 12:41.30 | kerio | only backupmenu/bootmenu |
| 12:41.45 | DocScrutinizer05 | but don't call me out on it, when it turns out there is some incorrect or fuzzy bit in the whole story |
| 12:46.42 | DocScrutinizer05 | tbh I *think* I've seen similar lockups on USB with stock kernel |
| 12:47.16 | DocScrutinizer05 | there's a known race condition in kernel, with detecting Vbus vs detecting D+- short |
| 12:47.34 | DocScrutinizer05 | the window for that race might have grown in KP |
| 12:49.17 | DocScrutinizer05 | however so far on my daily iroN900 I'm used to an occasional USB charger detect miss, but that's just a simple ignore and gets fixed by un- and re-plugging fastcharger |
| 12:49.38 | kerio | yeah, i get that too |
| 12:49.38 | DocScrutinizer05 | this time, on cssu-thumb not even 15 rounds did fix it |
| 12:50.36 | kerio | anyway, going back to the nicocam thing |
| 12:50.50 | kerio | what's your installed version for camera-ui? |
| 12:50.56 | DocScrutinizer05 | i'm done with testing. Noting to add so far |
| 12:51.30 | DocScrutinizer05 | what could it be? latest T |
| 12:51.46 | kerio | 1.1.29.2+0cssu14+thumb0 then? |
| 12:52.12 | DocScrutinizer05 | as well as cssu-thumb as of when I installed thumb on that other device, a few weeks ago |
| 12:52.38 | kerio | i don't really remember *when* fmg thumbified camera-ui |
| 12:52.48 | DocScrutinizer05 | nfc, I have not even a ssh open to the thumb thingie |
| 12:52.58 | kerio | he also added maemo-invoker support |
| 12:53.06 | kerio | and optification |
| 12:53.08 | kerio | (i think) |
| 12:53.23 | DocScrutinizer05 | that might help a lot, with switching to and from mediaplayer |
| 12:53.30 | kerio | hm, he didn't optify it |
| 12:53.36 | kerio | but it's maemo-invokered |
| 12:54.16 | DocScrutinizer05 | anyway, have to get some glimpse of TheBigBlueBox aka RL |
| 12:54.30 | DocScrutinizer05 | o/ |
| 12:54.37 | kerio | watch out, it's dangerous out there |
| 12:54.42 | DocScrutinizer05 | yeah |
| 12:54.57 | DocScrutinizer05 | I watched Monk, I heard the music |
| 12:55.36 | DocScrutinizer05 | ...cause it's jungle out there, it's jungle out there! |
| 12:57.18 | DocScrutinizer05 | http://www.magistrix.de/lyrics/Randy Newman/Its-A-Jungle-Out-There-96950.html |
| 12:58.17 | DocScrutinizer05 | http://www.youtube.com/watch?v=HIW69IRODxM |
| 14:22.46 | Pali | DocScrutinizer05, freemangordon, seems that I found problem |
| 14:22.59 | freemangordon | Pali: where? |
| 14:23.04 | Pali | see log |
| 14:23.27 | Pali | problem is that stupid battery status area plugin cannot handle hal changeset |
| 14:23.58 | Pali | I changed all calls libhal_changeset_set_property_ to libhal_device_set_property_string |
| 14:24.17 | Pali | and then status area battery plugin show message "battery is low" |
| 14:27.15 | freemangordon | Pali: which log, there is a wall of text :) |
| 14:27.21 | freemangordon | btw why did you change that? |
| 14:27.42 | freemangordon | do you remember me REing the original bme-addon |
| 14:27.51 | Pali | freemangordon, find your name in log |
| 14:28.31 | Pali | freemangordon, I changed it now (only for testing, not in git yet), because statusbar battery plugin not worked |
| 14:29.09 | Pali | without this change statusbar battery plugin did not show me message "charger disconnected" and message "battery is low" |
| 14:29.32 | freemangordon | aah, i see |
| 14:30.08 | freemangordon | Pali: AFAIK bme status plugin waits for dbus calls, though I might be wrong |
| 14:30.18 | freemangordon | dbus signals even |
| 14:30.33 | Pali | I'm sending same dbus signals as bme/hald-addon-bme |
| 14:30.46 | freemangordon | hmm |
| 14:30.54 | freemangordon | does it work now? |
| 14:31.10 | Pali | seems that after I changed code to use libhal_device_set_property_string is working... |
| 14:31.14 | DocScrutinizer05 | Pali: nice :-) |
| 14:31.20 | Pali | now I'm waiting until battery will be empty :D |
| 14:31.21 | freemangordon | yeah, great |
| 14:31.25 | freemangordon | hehe |
| 14:32.26 | DocScrutinizer05 | we now just wanna know why the other stuff been used or if it really been used at all in original bme*, and why this doesn't work in your RE if it's actually different |
| 14:33.52 | Pali | freemangordon, in hald-addon-bme README.properties.gz is written that for information about "battery low" is need first to change battery.charge_level.capacity_state to "" and then to new real value |
| 14:33.53 | DocScrutinizer05 | I mean, there's probably a difference in semantics between libhal_device_set_property_string and libhal_changeset_set_property_ |
| 14:34.38 | freemangordon | DocScrutinizer05: I didn't do 100% RE replacement (as with VKB) |
| 14:34.48 | freemangordon | just basic sceleton |
| 14:34.48 | Pali | so we need to decide when to send this "signal" battery is empty |
| 14:34.56 | DocScrutinizer05 | aah, so that's been an educated guess |
| 14:35.15 | Pali | original hald-addon-bme sent it more times (you can see that phone show message battery is too low/empty more times...) |
| 14:35.19 | DocScrutinizer05 | well, near miss fair enough then |
| 14:35.59 | freemangordon | Pali: I think the signal is sent every time voltage goes onder the threshold |
| 14:36.09 | freemangordon | s/onder/bellow/ |
| 14:37.06 | DocScrutinizer05 | nah, it also has a gate timer, to stop too frequent msgs/signals |
| 14:37.14 | freemangordon | the other option is to send a signal on every percent down |
| 14:37.26 | freemangordon | (after we are in low zone) |
| 14:37.27 | Pali | DocScrutinizer05, now new hald-addon-bme sending empty state (which cause that dsme will turn device off) when EDV1 or EDVF flag in bq27200 is set |
| 14:37.36 | Pali | it is ok? |
| 14:37.58 | DocScrutinizer05 | edv1 iirc, yes |
| 14:38.21 | freemangordon | do we have enough charge for graceful shutdown? |
| 14:38.23 | DocScrutinizer05 | edv1 with some 90s delay, to give user a chance to close stuff |
| 14:38.29 | DocScrutinizer05 | edvf immediately |
| 14:39.07 | Pali | now both edv1 or edvf immedialety turn device off |
| 14:39.22 | freemangordon | DocScrutinizer05: what do you think about: <freemangordon> the other option is to send a signal on every percent down |
| 14:40.00 | freemangordon | sounds like the best option to me |
| 14:40.14 | Pali | and low state is when bq27200 report capacity below 15% |
| 14:40.30 | Pali | (7% is for edv1) |
| 14:40.47 | freemangordon | well, so we'll have 7 beeps before shutdown |
| 14:40.48 | Pali | low state = show notification |
| 14:40.54 | DocScrutinizer05 | so: when edv1 got hit for >15s, you send a warning "going to power down!" and start timer for next msg that does real teardown. On either exiry of that timer, or on edvf you send "I'm shutting down NOW!" and do that - unless meanwhile charging kicked in or voltage is above edv1 again |
| 14:41.51 | DocScrutinizer05 | freemangordon: I guess that's exactly what bme does |
| 14:41.59 | DocScrutinizer05 | (per 1%) |
| 14:42.14 | freemangordon | DocScrutinizer05: only charger should preven shutdown once "shutting down" message appears |
| 14:42.30 | freemangordon | DocScrutinizer05: yeah, that is what i think too |
| 14:42.44 | DocScrutinizer05 | nah, not really. Battery can recover pretty much from a brownout on heavy load |
| 14:43.07 | freemangordon | then no "shutting down" message :) |
| 14:43.55 | freemangordon | and TBH I think it is better to shutdown with a slightly more charge, than to run battery flast |
| 14:43.59 | DocScrutinizer05 | btw percentage of charge my be vastly unrelated to actual voltage of cell |
| 14:44.00 | freemangordon | *flat |
| 14:44.20 | DocScrutinizer05 | may* |
| 14:45.34 | freemangordon | hmm, how precise is remaining percenatge if the battery is not calibrated? |
| 14:45.37 | DocScrutinizer05 | I'll think about it during my brinnerunch |
| 14:45.54 | DocScrutinizer05 | freemangordon: might be totally off |
| 14:46.13 | freemangordon | I mean after a couple of discharge cycles |
| 14:46.40 | freemangordon | so bq has had a chance to measure at least something |
| 14:46.58 | DocScrutinizer05 | we had OM GTA02 shut down at ~60% real capacity remaining, due to bq27000 miscalibration and shutdown mechanism only looking for percent-charge rather than voltage |
| 14:48.13 | DocScrutinizer05 | basing shutdown on EDV1/EDVF is sane. Waiting for 0% count down to 0% for warnings isn't |
| 14:48.14 | freemangordon | I don't think it is a good idea to force calibration only in order to have correct shutdown |
| 14:48.39 | freemangordon | AIUI that is what Pali does |
| 14:48.39 | DocScrutinizer05 | I'll think about it during my brinnerunch |
| 14:48.50 | DocScrutinizer05 | o/ |
| 14:48.55 | freemangordon | ~brinnerunch |
| 14:49.06 | DocScrutinizer05 | dinner+brunch |
| 14:49.08 | kerio | i say we wait the 10 or so seconds on EDV1 so we can properly calibrate bq27200 |
| 14:49.45 | freemangordon | you mean auto-calibrate on first battery empty? |
| 14:50.04 | DocScrutinizer05 | I say we only warn on EDV1, and shut down on EDVF |
| 14:50.10 | Pali | if edv1 is set, then learning cycle is complete |
| 14:50.11 | freemangordon | agree |
| 14:50.26 | freemangordon | Pali: only if you have a full charge AFAIK |
| 14:50.37 | freemangordon | (at the start of discharge cycle) |
| 14:50.45 | kerio | Pali: hm? |
| 14:50.54 | Pali | yes |
| 14:50.56 | kerio | oh girhgt |
| 14:50.58 | kerio | *right |
| 14:51.20 | DocScrutinizer05 | even a short intermediate charging stops learning cycle |
| 14:51.30 | Pali | I mean that it is ok to turn device off (if learning cycle was active, then after edv1 is complete) |
| 14:51.46 | freemangordon | well, how is learning syscle activated? |
| 14:51.52 | freemangordon | *cycle |
| 14:52.26 | DocScrutinizer05 | EDVF = End of Discharge Voltage Final. we should take it as that |
| 14:52.33 | Pali | start charging when edv1 is set and stop charging when battery is charged |
| 14:52.39 | kerio | freemangordon: VDQ set |
| 14:52.52 | kerio | aka fully charge |
| 14:53.08 | Pali | then vdq is set and when edv1 is set again, cycle is complete |
| 14:53.29 | freemangordon | you mean there is no need SW to take care of it? |
| 14:53.45 | freemangordon | to set some bit or something? |
| 14:53.48 | kerio | no |
| 14:53.49 | DocScrutinizer05 | a valid learning cycle includes: charging to 100% -> VDQ:1. discharge without any intermediate charging or other extrema, until EDV1 is hit |
| 14:54.04 | kerio | it's just a bq27200 thing |
| 14:54.15 | freemangordon | and if learning cycle is interrupted, what happens with the calibration? |
| 14:54.23 | DocScrutinizer05 | untouched |
| 14:54.27 | freemangordon | great |
| 14:54.35 | freemangordon | I don't see any problem then |
| 14:54.36 | DocScrutinizer05 | VDQ:0 |
| 14:54.42 | DocScrutinizer05 | there |
| 14:54.46 | DocScrutinizer05 | 's no problem |
| 14:54.51 | kerio | the problem is that you need to wait a handful of seconds below EDV1 voltage |
| 14:54.57 | kerio | usually it's not doable with bme |
| 14:55.02 | DocScrutinizer05 | just we shouldn't shut down on EDV1 |
| 14:55.03 | freemangordon | kerio: no bme there |
| 14:55.06 | kerio | indeed |
| 14:55.08 | freemangordon | DocScrutinizer05: :nod: |
| 14:55.13 | freemangordon | Pali: ^^^ |
| 14:55.19 | DocScrutinizer05 | since that per definitionem wwastes 6% of bat capacity |
| 14:55.41 | kerio | shut down after 60-90s under EDV1 or when you reach EDVF |
| 14:56.06 | freemangordon | hmm , we'd better just ignore EDV1 |
| 14:56.11 | DocScrutinizer05 | that's what I said |
| 14:56.22 | freemangordon | and shutdown on EDVF |
| 14:56.23 | DocScrutinizer05 | no, not that :-) |
| 14:56.31 | kerio | DocScrutinizer05: we should hold enough charge to boot, though |
| 14:56.34 | DocScrutinizer05 | we start warnings at EDV1 |
| 14:56.36 | kerio | boot to ACT_DEAD at least |
| 14:56.48 | DocScrutinizer05 | kerio: that's granted |
| 14:56.54 | kerio | granted how? |
| 14:57.03 | kerio | how big is EDVF? |
| 14:57.07 | DocScrutinizer05 | edvf still allows device to boot |
| 14:57.11 | kerio | i see |
| 14:57.27 | DocScrutinizer05 | hw cutout threshold is waaay lower |
| 14:58.04 | DocScrutinizer05 | anyway, cya. I'm going hypoglycemic |
| 14:58.16 | kerio | eat some food |
| 14:58.18 | kerio | food is good! |
| 14:58.49 | kerio | http://youtu.be/g-uLTTT3BPc |
| 14:59.28 | freemangordon | Pali: so, AIUI -> start battery low beeps on N% (10-15), beep on every % down, ignore EDV1 and shutdown on EDVF |
| 14:59.42 | Pali | ok |
| 15:00.09 | freemangordon | BTW we may want to keep the current BME threshol for low warnings |
| 15:00.22 | freemangordon | or lower it just a bit (2-3 %) |
| 15:00.30 | DocScrutinizer05 | well, increase warning freequency to a timed schedule on EDV1 since bq27200 switches from ~6% to 0% on EDV1 anyway |
| 15:01.03 | freemangordon | aah, i see |
| 15:01.06 | DocScrutinizer05 | or maybe I recall wrong |
| 15:01.14 | DocScrutinizer05 | read DS please |
| 15:01.27 | freemangordon | yeah, batt low every 30 seconds should be ok |
| 15:01.28 | DocScrutinizer05 | or ~jr/bme |
| 15:01.47 | freemangordon | (once we are at EDV1) |
| 15:01.50 | DocScrutinizer05 | there are some nice logs, with comments |
| 15:02.13 | DocScrutinizer05 | ~jrtools |
| 15:02.13 | infobot | i heard jrtools is http://wiki.maemo.org/User:Joerg_rw/tools |
| 15:02.21 | DocScrutinizer05 | ../bme* |
| 15:02.21 | freemangordon | Pali: ^^^ |
| 15:02.56 | DocScrutinizer05 | http://wiki.maemo.org/User:Joerg_rw/jrbme/bme_discharge_learn_log |
| 15:03.28 | DocScrutinizer05 | http://wiki.maemo.org/User:Joerg_rw/jrbme/bme_chargefloat2_log et al |
| 15:03.32 | DocScrutinizer05 | study those |
| 15:03.45 | kerio | 30 seconds? ew |
| 15:03.54 | kerio | after i got the first warning, i *know* the battery is low |
| 15:08.44 | DocScrutinizer05 | http://people.openmoko.org/joerg/battery/batlog.txt.odf |
| 15:09.46 | DocScrutinizer05 | make as many as possible of those timing and level parameters configurable, via module parameters or whatever |
| 15:10.18 | DocScrutinizer05 | so kerio can set that warning frequency to once per day ;-D |
| 15:10.33 | kerio | omfg i liek configurations |
| 15:10.52 | DocScrutinizer05 | also timeout levels for those "90sec stable EDV1 " |
| 15:11.04 | DocScrutinizer05 | cyacyacyacya |
| 15:12.11 | kerio | Pali: eventually will you rewrite the statusmenu button to allow for detailed data from bq27k and to choose usb host mode? |
| 15:12.42 | Pali | kerio, MAG already started rewriting it |
| 15:13.15 | Pali | I have pending merge request for it, MAG wrote me that he merge it after he commit some changes... |
| 15:13.50 | kerio | :D |
| 15:14.15 | kerio | Pali: also, can you make your UI a bit more configurable so we can actually choose the usb speed and/or manually enumerate? |
| 15:14.37 | Pali | kerio, I have no time for it now... |
| 15:14.38 | DocScrutinizer05 | is there a way to detect user clicking away a one-line-notifier? |
| 15:14.54 | kerio | DocScrutinizer05: make it permanent :) |
| 15:15.01 | DocScrutinizer05 | nah!!! |
| 15:15.32 | DocScrutinizer05 | the idea is to open the permanent requester when user clicks on the bat-low warning |
| 15:16.00 | DocScrutinizer05 | in that requester you can say "don't warn for this low-power-event again" |
| 15:16.21 | merlin1991 | a click on notifier discards it |
| 15:16.24 | DocScrutinizer05 | or set period of warning to something more pleasant for you |
| 15:16.38 | DocScrutinizer05 | merlin1991: that's not what I asked |
| 15:16.46 | DocScrutinizer05 | I know that |
| 15:17.30 | merlin1991 | I'm saying to change that for 1 notifier would be a break of ui |
| 15:17.52 | DocScrutinizer05 | I didn't suggest to change that |
| 15:18.09 | kerio | just detect whether the user dismissed it or it was just timeout'd |
| 15:18.13 | DocScrutinizer05 | I asked "is it detectable that user did it (click it away)" |
| 15:18.18 | merlin1991 | <DocScrutinizer05> the idea is to open the permanent requester when user clicks on the bat-low warning |
| 15:18.32 | merlin1991 | thus you're suggesting to change the default behaviour even if not implemented in the notifier |
| 15:18.41 | merlin1991 | which is inconsistent to the rest of the ui |
| 15:19.17 | DocScrutinizer05 | hmm, i'll think about that. Maybe you got a pojnt, maybe I don't think it's a good point ;-) |
| 15:19.22 | DocScrutinizer05 | or maybe I do |
| 15:19.39 | kerio | we could just make it a bigass system notification |
| 15:19.46 | kerio | one of the ones in the middle, that you *have* to dismiss |
| 15:20.09 | DocScrutinizer05 | goes blackout |
| 15:20.10 | *** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua) |
| 15:29.29 | *** join/#maemo-ssu ZogG (~zoggrules@funtoo/user/ZogG) |
| 15:37.18 | *** join/#maemo-ssu arcean_ (~arcean@aaem131.neoplus.adsl.tpnet.pl) |
| 16:19.47 | DocScrutinizer51 | after dealing with pending blackout due to *my* charge reaching EDVF, I retought the notifier thingie and I guess merlin1991 is right. Anything related to powerflow-alarm config etc belongs to a requester popping up after clicking battery button in system menu |
| 16:20.27 | DocScrutinizer51 | s/flow/-low/ |
| 16:21.15 | kerio | DocScrutinizer51: actually, config belongs in Settings |
| 16:21.27 | kerio | the battery button in the system menu is for live stuff |
| 16:21.45 | DocScrutinizer51 | I however already wanna come up with another weird idea tweaking UI: the battery icon as such is BS for low battery |
| 16:22.10 | DocScrutinizer51 | kerio: exactly what I meant |
| 16:22.40 | DocScrutinizer51 | snoozing a bat-low-alarm *is* a live thing |
| 16:24.20 | DocScrutinizer51 | bat icon is utter crap for detecting change of 1 row of pixels from green to red. I suggest to change the iconset and animation |
| 16:26.42 | Pali | hald-addon-bme changes pushed to git on gitorious |
| 16:28.28 | kerio | D: |
| 16:28.30 | kerio | don't do this to me |
| 16:28.34 | kerio | i'm not at home tomorrow |
| 16:28.45 | kerio | i really want to try it, but i know i mustn't |
| 16:31.52 | Pali | see http://pastebin.com/mppAFAKd |
| 16:32.21 | Pali | EDVF was set when voltage was only 3021 |
| 16:32.28 | Pali | it is good idea to wait for EDVF? |
| 16:32.35 | Pali | DocScrutinizer51, see ^^^ |
| 16:33.37 | DocScrutinizer51 | according to bq27200 DS this is incorrect behaviour/voltage |
| 16:33.59 | kerio | D: |
| 16:38.02 | DocScrutinizer51 | EDV1 set at 3239mV in that log |
| 16:38.40 | DocScrutinizer51 | EDVF at 30nn mV is correect and sane |
| 16:39.43 | DocScrutinizer51 | device is meant to shut down immeidiately though gracefully at tripping EDVF |
| 16:41.15 | kerio | is "LOW" edvf? |
| 16:42.18 | DocScrutinizer51 | I guess |
| 16:42.28 | DocScrutinizer51 | not my version of script |
| 16:42.39 | *** join/#maemo-ssu timo^ (~timo@unaffiliated/tiempjuuh) |
| 16:42.40 | kerio | ~shadowjk |
| 16:42.44 | kerio | hrmpf |
| 16:42.57 | DocScrutinizer51 | hrmpf? |
| 16:43.09 | kerio | i thought i added that factoid |
| 16:43.33 | DocScrutinizer51 | you won't add a nick as factoid, will you? |
| 16:43.48 | kerio | of course |
| 16:43.50 | kerio | ~pali |
| 16:43.50 | infobot | i heard pali is http://atrey.karlin.mff.cuni.cz/~pali/ |
| 16:44.13 | *** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se) |
| 16:44.42 | DocScrutinizer51 | whatever it is you're after, maybe you find it next to |
| 16:44.51 | DocScrutinizer51 | ~jrtools |
| 16:44.52 | infobot | i guess jrtools is http://wiki.maemo.org/User:Joerg_rw/tools |
| 16:45.01 | kerio | i wanted the url to bq27200.sh |
| 16:45.25 | DocScrutinizer51 | ^^^^ |
| 16:45.39 | DocScrutinizer51 | ../jrbme/ |
| 16:45.46 | kerio | oic |
| 16:48.26 | DocScrutinizer51 | and of course at maemo.cloud-7.de |
| 16:49.22 | DocScrutinizer51 | maemo/patches'n'tools/ or sth like that |
| 16:49.43 | kerio | hehe, http://maemo.cloud-7.de/Aegis-kills-device.jpg |
| 17:16.18 | *** join/#maemo-ssu arcean_ (~arcean@aaem131.neoplus.adsl.tpnet.pl) |
| 17:38.47 | *** join/#maemo-ssu Guest57704 (~rd@p57B4847F.dip0.t-ipconnect.de) |
| 17:55.52 | *** join/#maemo-ssu timo^ (~timo@unaffiliated/tiempjuuh) |
| 18:02.09 | *** join/#maemo-ssu fw190 (~fw190@user-5-173-80-252.play-internet.pl) |
| 18:30.49 | *** join/#maemo-ssu timo^ (~timo@unaffiliated/tiempjuuh) |
| 19:03.35 | *** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 19:54.22 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 20:29.58 | *** join/#maemo-ssu M13 (~Miha@170.133-224-87.telenet.ru) |
| 21:09.21 | *** join/#maemo-ssu Guest57704 (~rd@p57B4847F.dip0.t-ipconnect.de) |
| 21:22.05 | *** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua) |
| 21:25.51 | SpacedOut | DocScrutinizer05: I missed getting in on the USB charging discussion. I've tracked down a problem where plugging into a wall charger works, but plugging into a computer usb port doesn't charge and the computer doesn't see the N900. musb_core.c struct musb_ctx holds hardware register values, it can get it into that state. |
| 21:29.27 | SpacedOut | `echo mem > /sys/power/state` is the most reliable way to get it into that state. If anyone is wanting to debug it I have a patch for compiling the USB drivers as modules which also fixes some concurrency problems in the charger detection routines, a whole bunch of debugging print messages. |
| 22:06.58 | *** join/#maemo-ssu arcean_ (~arcean@aaem131.neoplus.adsl.tpnet.pl) |
| 22:09.53 | DocScrutinizer51 | SpacedOut: we concluded during 18months of h-e-n development that musb-hdrc has to be monolithic. |
| 22:11.03 | SpacedOut | I'm fine with it being compiled in the kernel with the default configuration, but I have it working as module, and that is very handy if anyone is trying to do development or debugging on it. |
| 22:12.03 | SpacedOut | Which I was. |
| 22:12.14 | DocScrutinizer51 | and setting device to suspend-to-ram is kinda useless since it either wakes up again after 10s due to signal-level change message from cmt, or you block that and it won't even wake up on inbound call |
| 22:13.07 | SpacedOut | I was wanting to point out that some of the problems you were having with it detecting the usb port and charging sounded familiar with what I was debugging, depending on the specifics and it all gets pretty fuzzy trying to track down all the variables. |
| 22:13.40 | DocScrutinizer51 | or you have very secrit wisdom how to tell bb5 cmt to stop spamming unsol msgs |
| 22:14.12 | SpacedOut | I think suspend to ram is useless unless you are in offline mode, and that is exactly how I use it, not very often, but I want it near off, but not have to boot it up when I'm ready to use it again. |
| 22:15.01 | DocScrutinizer51 | yep, this works. speedevil done this |
| 22:15.26 | DocScrutinizer51 | sorry for terse answers |
| 22:15.27 | DocScrutinizer51 | N900 |
| 22:18.19 | SpacedOut | I didn't get the reference or what part works, the current suspend to ram works for me after my patches for one to let it work with a computer USB port after resuming. |
| 23:30.15 | int_ua | maemo.org down |
| 23:30.27 | int_ua | isup.me/maemo.org |
| 23:51.04 | int_ua | I've just installed CSSU-thumb and U-Boot disappeared, is that ok? |
| 23:52.12 | merlin1991 | it's to be expected |
| 23:52.17 | merlin1991 | cssu-thumb flashes a kernel |
| 23:52.43 | merlin1991 | but you can install the kerne-thumb (or how it's called) bootimg and install uboot again |
