**** BEGIN LOGGING AT Thu Jul 24 03:00:02 2014
Jul 24 06:45:34 <norayr> what was the name of tha package containing "don't panic" bootsplash animation?
Jul 24 12:58:59 <Tekk_> hm, now musikloud can't update
Jul 24 12:59:06 <Tekk_> along with cuteTube
Jul 24 15:36:53 <Snafu777> Has anyone managed to tunnel x11 over their n900 successfully?
Jul 24 15:38:55 <TTilus> i have, both ways, show remote app on n900 and n900 app on remote
Jul 24 15:39:31 <Snafu777> xauth required?
Jul 24 15:40:34 <TTilus> i simply did ssh -X otherhost whatnotapp
Jul 24 15:40:44 <Snafu777> hmm
Jul 24 15:41:04 <TTilus> i assume xauth is required
Jul 24 15:41:08 <TTilus> both ways
Jul 24 20:26:10 <sixwheeledbeast1> ~flatbatrecover
Jul 24 20:26:11 <infobot> Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber going off - in this case start over again with ~flatbatrecover. CAVEAT! Only works when ~rootfs is OK (no ~bootloop)!.
Jul 24 20:38:35 <sixwheeledbeast1> it seems with flat battery device (solid yellow) will charge without data pins shorted, however when device then boots it no longer charges but keeps trying to boot. 
Jul 24 21:23:56 <DocScrutinizer05> ((what the diff between deb http://repository.maemo.org/extras/ fremantle-1.3 free non-free and deb http://repository.maemo.org/extras/ fremantle free non-free would be)) there shouldn't be a difference, once it been a symlink
Jul 24 21:24:48 <DocScrutinizer05> (("don't panic" bootsplash)) see
Jul 24 21:24:52 <DocScrutinizer05> ~jrtools
Jul 24 21:24:52 <infobot> hmm... jrtools is http://wiki.maemo.org/User:Joerg_rw/tools
Jul 24 21:26:21 <DocScrutinizer05> sixwheeledbeast1: WELL, SORT OF CORRECT, YES
Jul 24 21:26:31 <DocScrutinizer05> oops capslock, sorry
Jul 24 21:28:23 <bencoh> DocScrutinizer05: hmm ?
Jul 24 21:28:40 <DocScrutinizer05> actually even autonimous charging tries to detect fastcharger D+- short, and then use 500mA instead 100mA for flatbatrecover. But ir will happily use 100mA when the short in datalines missing. Just the question is if it comes out of molasses with 100mA
Jul 24 21:29:03 <DocScrutinizer05> bencoh: hm? hmm???
Jul 24 21:30:02 <DocScrutinizer05> bencoh: maybe [2014-07-24 Thu 08:45:34] <norayr> what was the name of tha package containing "don't panic" bootsplash animation?
Jul 24 21:30:07 <sixwheeledbeast> Well I didn't leave it booting over and over too long to test.
Jul 24 21:31:50 <DocScrutinizer05> sixwheeledbeast: the problem is that 100mA won't suffice to powe rup the device during early boot. So a weak or worn battery will drop below lower threshold during the few seconds it needs to boot up to a state where software controls charging. And with missing D+. short even that sw control won't help
Jul 24 21:32:55 <DocScrutinizer05> steady yellow is hw autonomous aka emergency charging, not aided by software
Jul 24 21:34:12 <DocScrutinizer05> as soon as battery voltage trips the minimum voltage threshold needed by OMAP system to start and POR the CPU, it will boot and load NOLO, which in turn tries to handle charging by software
Jul 24 21:34:40 <DocScrutinizer05> and Nolo also switches steady yellow to pulsing yellow
Jul 24 21:34:51 <DocScrutinizer05> iirc
Jul 24 21:35:17 <DocScrutinizer05> now the system runs a CPU and a display, and that will eat more than 100mA
Jul 24 21:35:59 <sixwheeledbeast> :nod:
Jul 24 21:36:32 <DocScrutinizer05> a charger without D+- short is not supposed to be able to provide more than 100mA, so N900 will behave and continue leeching 100mA for battery charging while same time system DIScharges battery with maybe 200mA
Jul 24 21:37:17 <sixwheeledbeast> exactly what I was about to say
Jul 24 21:37:20 <sixwheeledbeast> :)
Jul 24 21:37:42 <bencoh> DocScrutinizer05: the hmming was for the fremantle-1.3 vs fremantle in extras :)
Jul 24 21:38:06 <DocScrutinizer05> aaah. well, that's pretty much bogus
Jul 24 21:38:22 <nox-> so it wont charge 500 mA even once booted?
Jul 24 21:38:39 <DocScrutinizer05> not when D+- short missing
Jul 24 21:38:52 <nox-> oh
Jul 24 21:38:56 <DocScrutinizer05> from a PC USB host it might, though
Jul 24 21:39:04 <nox-> aah
Jul 24 21:39:10 <nox-> thats what i was wondering
Jul 24 21:39:11 <DocScrutinizer05> after ENUM
Jul 24 21:39:32 <DocScrutinizer05> NOLO doesn't do proper ENUM afaik
Jul 24 21:39:39 <nox-> ok
Jul 24 21:39:46 <bencoh> DocScrutinizer05: so basically extras/ is fully replicated ? :]
Jul 24 21:39:47 <honestly> some laptops have a "power" usb socket
Jul 24 21:39:49 <DocScrutinizer05> you need working linux rootfs for that
Jul 24 21:39:51 <bencoh> twice the space
Jul 24 21:40:03 <honestly> that provides higher current and also works when the laptop is powered off
Jul 24 21:40:22 <honestly> no idea how nicely that plays with n900
Jul 24 21:40:36 <DocScrutinizer05> honestly: N900 doesn't care
Jul 24 21:41:27 <DocScrutinizer05> bencoh: yep, wasted space. Ask xes
Jul 24 21:41:53 <DocScrutinizer05> somebody did a wget copy during migrations, I guess
Jul 24 21:42:03 <bencoh> I think xes is still on vacation/away from a real keyboard
Jul 24 21:42:17 <bencoh> DocScrutinizer05: probably yeah
Jul 24 21:42:21 <DocScrutinizer05> as am I, starting this weekend
Jul 24 21:42:37 <bencoh> DocScrutinizer05: you on vacation ? wow ;)
Jul 24 21:42:42 <bencoh> enjoy ! :)
Jul 24 21:42:48 <DocScrutinizer05> yeah, vacation or die
Jul 24 21:44:14 <DocScrutinizer05> my health doesn't give me any choice
Jul 24 21:45:38 <honestly> I hope you will stay away from maemo for at least two weeks
Jul 24 21:46:54 <DocScrutinizer05> 2 weeks is exactly what I planned as minimum afk time
Jul 24 21:46:59 <DocScrutinizer05> :-)
Jul 24 21:47:11 <sixwheeledbeast> Wasn't the whole fremantle-1.3 thing suppose to be for some incompatiblity with fremantle-1.2?
Jul 24 21:47:37 <DocScrutinizer05> nope, 1.2 was incompatible with 1.1
Jul 24 21:47:42 <DocScrutinizer05> iirc
Jul 24 21:47:58 <DocScrutinizer05> 1.3 been established just in anticipation
Jul 24 21:49:47 <sixwheeledbeast> ah, I knew there was a reason
Jul 24 21:50:09 <sixwheeledbeast> so 1.3 is an exact copy of 1.2
Jul 24 21:50:25 <DocScrutinizer05> the story goes like: when we roll out new 1.X MP, we will ship new incompatible packages in repo for stuff that 1.(X-1) dvices may depend on. So we have a repo copy of 1.(X-1) for those who don't want to update, so they still can install packages that are compatible to their system
Jul 24 21:51:46 <DocScrutinizer05> on a second thought, that might have been 1.2->1.3
Jul 24 21:52:49 <DocScrutinizer05> for those who don't want to update to 1.3, there's fremantle-1.2 with all the old lib versions so they could install stuff from extras and the stuff doesn't pull in incompatible 1.3 versions of lins or whatever
Jul 24 21:53:19 <DocScrutinizer05> so devices not willing to upgrade to 1.3 need to use fremantle-1.2
Jul 24 21:53:49 <sixwheeledbeast> exactly, how I remember it.
Jul 24 21:54:13 <DocScrutinizer05> fremantle is meant to be "rolling release", while fremantle-1.3 is a symlink to fremantle for the time until a incompatible PR1.4 would get released
Jul 24 21:54:52 <sixwheeledbeast> ah, I see the reason for fremantle now.
Jul 24 21:54:55 <DocScrutinizer05> on release of PR1.4 the fremantle-1.3 would turn from a symlink into a copy
Jul 24 21:55:13 <DocScrutinizer05> static copy
Jul 24 21:55:20 <DocScrutinizer05> aka snapshot
Jul 24 21:56:01 <DocScrutinizer05> alas there never been a pr1.4, and somebody messed it up during migrations, turning fremantle-1.3 symlink into a copy
Jul 24 21:56:14 <DocScrutinizer05> then shit hit the fan
Jul 24 21:56:47 <sixwheeledbeast> Well I can't image anybody on <1.3 now
Jul 24 21:56:54 <DocScrutinizer05> xes did a compare between fremantle and fremanlte-1.3 afail
Jul 24 21:56:59 <DocScrutinizer05> afaik*
Jul 24 21:57:29 <DocScrutinizer05> anybody on <1.3 is irrelevant, since that would be fremantle-1.2
Jul 24 21:57:55 <DocScrutinizer05> and that *is* a snapshot of fremantle of 2011(?)
Jul 24 21:58:22 <DocScrutinizer05> we have a fremantle-1.2 afaik
Jul 24 21:58:35 <DocScrutinizer05> it's a copy, as it is supposed to be
Jul 24 21:59:09 <DocScrutinizer05> we're NOT supposed to have a fremantle-1.3 copy, particularly not one that's not in sync with fremantle
Jul 24 21:59:41 <DocScrutinizer05> alas reality looks different
Jul 24 22:00:01 <DocScrutinizer05> thanks to autobuilder madness
Jul 24 22:00:18 <sixwheeledbeast> hm
Jul 24 22:00:20 <DocScrutinizer05> ask xesw
Jul 24 22:00:23 <DocScrutinizer05> xesw
Jul 24 22:00:30 <DocScrutinizer05> damn it!
Jul 24 22:00:37 <sixwheeledbeast> xes maybe ;)
Jul 24 22:00:38 <DocScrutinizer05> xes, our sysop
Jul 24 22:01:22 <DocScrutinizer05> he did a comprehensive compare and analyzed what are the differences between fremantle-1.3 and fremantle
Jul 24 22:01:43 <DocScrutinizer05> somebody should use this info/data and re-unify those two repos
Jul 24 22:02:18 <DocScrutinizer05> (unless somebody already did and I missed it)
Jul 24 22:03:09 <DocScrutinizer05> we also got maemo5 ex-symlink to fremantle :-/
Jul 24 22:03:24 <DocScrutinizer05> same trouble
Jul 24 22:04:23 <DocScrutinizer05> migration created an incredible mess
Jul 24 22:04:56 <DocScrutinizer05> everything "worked" so nemein didn't care anymore, and of course Nokia didn't care at all
Jul 24 22:06:01 <sixwheeledbeast> :nod: I remember....
**** ENDING LOGGING AT Fri Jul 25 03:00:00 2014