**** BEGIN LOGGING AT Mon Nov 09 02:59:56 2009
Nov 09 03:31:22 <rooly> so
Nov 09 03:31:31 <rooly> android gracefully handles push imap and push twitter
Nov 09 04:42:48 <slaxxer> got an interesting email  today
Nov 09 04:43:10 <ndnihil> some guy in nigeria wants to send you money?
Nov 09 04:45:37 <slaxxer> no but my neighbor  wont let that go    Haaaaa
Nov 09 04:46:32 <slaxxer> someone at armdslack  id interested in      the moko project
Nov 09 04:54:11 <ndnihil> they going to package up a filesystem for it?
Nov 09 05:42:13 <luke-jr> if a used Freerunner was bought in 2008, what generation is that?
Nov 09 06:13:25 <slaxxer> v5  prolly
Nov 09 06:13:51 <slaxxer> usa?
Nov 09 07:05:51 <PaulFertser> luke-jr: it's easy to tell exactly the revision if you have the device running.
Nov 09 07:05:58 <PaulFertser> luke-jr: just cat /proc/cpuinfo
Nov 09 07:06:28 <PaulFertser> Psi_: iirc yes
Nov 09 07:09:22 <luke-jr> PaulFertser: Freerunner lacks a keyboard. I'm not sure how practical it is to ask someone selling via ebay to run that.
Nov 09 07:09:55 <PaulFertser> luke-jr: perfectly is
Nov 09 07:10:29 <PaulFertser> luke-jr: if he bought it in the first place it's assumed he has some basic gnu/linux knowledge. It's easy to start a terminal and type a simple command, especially provided path completion is working.
Nov 09 07:10:42 <beer> morning
Nov 09 07:48:52 <Psi_> PaulFertser: thanks
Nov 09 07:50:45 <PaulFertser> Psi_: i can tell you the exact PN i used
Nov 09 07:51:41 <Psi_> its 10uf 10V
Nov 09 07:51:43 <Psi_> the one in there
Nov 09 07:51:45 <PaulFertser> X5R 20% 6.3В 0805 
Nov 09 07:51:49 <PaulFertser> 22uF
Nov 09 07:51:55 <PaulFertser> Is the one i changed it too.
Nov 09 07:52:06 <PaulFertser> s/too/to/
Nov 09 07:52:07 <apt> PaulFertser meant: Is the one i changed it to.
Nov 09 07:52:30 <Psi_>  ya, ive ordered a few sizes of 10uf to parallel with it. will see which one fits best
Nov 09 07:52:44 <PaulFertser> GRM21BR60J226M, murata
Nov 09 07:52:46 <Psi_> wanted to check 6.3V was fine, which it is
Nov 09 07:53:10 <PaulFertser> Psi_: i guess parallel mounting is even easier than replacing so it's a good choice :)
Nov 09 07:53:16 <Psi_> yeah
Nov 09 07:53:29 <Psi_> apparently the c1009 on gta01 is glued down really well
Nov 09 07:53:36 <Psi_> harder to get off than gta02
Nov 09 07:58:37 <PaulFertser> Psi_: yep. Have you actually tried? ;)
Nov 09 08:01:01 <Psi_> na, was just reading about it
Nov 09 11:54:59 <alabd> Does A7 have just a fix more than A6 ?
Nov 09 11:56:20 <Kamping_Kaiser> iirc the last two hardware fixes were buzz fix and gps fix.
Nov 09 11:57:17 <PaulFertser> Kamping_Kaiser: gps fix is not essential and doesn't work that way.
Nov 09 11:57:39 <PaulFertser> Kamping_Kaiser: but yes, A7 has special pads so you can add hardware capacitor to every SD line.
Nov 09 11:58:41 <Kamping_Kaiser> PaulFertser: 'work that way'?
Nov 09 11:59:27 <PaulFertser> Kamping_Kaiser: yes, the capacitors are not installed on a7 afaik because you can change drive strength in software with exactly the same outcome.
Nov 09 12:00:43 <Kamping_Kaiser> PaulFertser: hm, interesting to know. Wonder what hardware revision the FR with a cap is
Nov 09 12:01:02 <PaulFertser> Kamping_Kaiser: A6
Nov 09 12:01:22 <PaulFertser> Kamping_Kaiser: but only one cap is not enough, one needs caps on all the lines. Or to alter drive strength.
Nov 09 12:01:30 <Kamping_Kaiser> A02E
Nov 09 12:02:14 <Kamping_Kaiser> PaulFertser: weird. ok. guess the magic is being done in software (guess it also explains why the FR with no cap gets gps fix faster then the one with it)
Nov 09 12:03:06 <Kamping_Kaiser> thanks for the info
Nov 09 12:04:01 <PaulFertser> welcome
Nov 09 12:14:17 <PaulFertser> "A woman engineer is like a guinea pig - neither guinea nor pig". Do you agree?
Nov 09 12:15:40 <SpeedEvil> no.
Nov 09 12:18:49 <PaulFertser> SpeedEvil: neither do i.
Nov 09 12:19:46 <PaulFertser> SpeedEvil: but i'm yet to meet a single woman engineer. :(
Nov 09 12:20:16 <PaulFertser> I mean i've never met any, not that i'm interested in single engineers.
Nov 09 12:20:18 <PaulFertser> :)
Nov 09 14:54:53 <DocScrutinizer> A7 has 8 pairs of pads on base of uSD holder to place C there. PV preMP prototypes have 011100000 for populated Capacitors there (read left to right, when holding device USB connector facing upward)
Nov 09 14:55:37 <DocScrutinizer> s/0 / /
Nov 09 14:55:38 <apt> DocScrutinizer meant: A7 has 8 pairs of pads on base of uSD holder to place C there. PV preMP prototypes have 01110000 for populated Capacitors there (read left to right, when holding device USB connector facing upward)
Nov 09 14:57:48 <DocScrutinizer> ok, there's a 9th pair of unused pads at the outer left, horizontal orientation. Can't tell off top of my head what that might be
Nov 09 14:58:46 <lindi-> DocScrutinizer: i can reproduce the overheating bug with a usb-ethernet dongle
Nov 09 14:59:11 <DocScrutinizer> lindi-: please scratch the "over" part ;-)
Nov 09 15:00:59 <DocScrutinizer> lindi-: you seen my remarks wrt kernel should take action to shut down USB when /USB_OC trips?
Nov 09 15:02:31 <lindi-> DocScrutinizer: "should" as in "the code is there now"?
Nov 09 15:03:16 <DocScrutinizer> nah, "should" as in "it's mandatory, but we think it's not yet implemented"
Nov 09 15:04:03 <DocScrutinizer> PaulFertser: ^^^ any details / news?
Nov 09 15:04:19 <lindi-> DocScrutinizer: now I can add "buy http://www.dealextreme.com/details.dx/sku.2797" to steps to reproduce :)
Nov 09 15:04:53 <DocScrutinizer> nice. But who might be interested in doing that? ;-P
Nov 09 15:06:51 * DocScrutinizer wonders how the hell that tiny plastic toy can consume 2.5W without melting down to a blue blob
Nov 09 15:09:38 <lindi-> don't ask me :)
Nov 09 15:11:46 <lindi-> it seemed to have emptied the battery quite well too
Nov 09 15:11:48 <DocScrutinizer> lindi-: well, maybe L4901 is such a crappy Subaru choke (even probably), and if that choke eats >30% of the converter energy, that for sure would cause it to heat up (700mW!!)
Nov 09 15:12:23 <lindi-> i don't have the wall charger now with me so i need to do some voodoo to make the phone boot :P
Nov 09 15:13:44 <DocScrutinizer> lindi-: (suck bat) no surprise. The bat has ~4Wh. If you ask it to supply ~3W for converter input, you likely won't see a batlife of >1h
Nov 09 15:13:48 <lindi-> I should have used newer u-boot that lets me force 500 mA and turn the display off and wait in boot loader
Nov 09 15:17:58 <DocScrutinizer> lindi-: even NOR uBoot does charge at reasonable rate (though you need to keep it alive by occasionally pressing the AUX button). After 5min you should have enough capacity in bat to boot
Nov 09 15:18:58 <DocScrutinizer> (from arbitrary USB-charger that is. Not sure for USB-hosts)
Nov 09 15:36:19 <lindi-> DocScrutinizer: what's reasonable rate?
Nov 09 15:36:35 <lindi-> DocScrutinizer: and this is my laptop
Nov 09 15:37:55 <DocScrutinizer> lindi-: reasonable rate is "at least 100mA", which should suffice to recover a bat in max 10min
Nov 09 15:38:07 <lindi-> DocScrutinizer: 100 mA is not enough since the LCD backlight consumes more than that
Nov 09 15:38:23 <lindi-> (combined with cpu)
Nov 09 15:38:35 <DocScrutinizer> hmm, sorry seems my coffee didn't kick in today
Nov 09 15:39:02 <DocScrutinizer> of course you're right - though I can't tell if it's maybe 500mA or even 1000mA
Nov 09 15:39:35 <lindi-> DocScrutinizer: it's 100 mA only :(
Nov 09 15:39:55 <lindi-> DocScrutinizer: since I have not flashed u-boot with support for forcing 500 mA
Nov 09 15:40:04 <DocScrutinizer> so that's bad then (for NOR)
Nov 09 15:40:52 <DocScrutinizer> lindi-: you should fix that annoyance of yours, by replacing the Vsys-buffer C by 100uF
Nov 09 15:42:20 <lindi-> having "if [ $(energy) -lt 5 ]; then backlight 12; fi" in boot scripts might help :)
Nov 09 15:49:14 <lindi-> would be nice to know if the phone charges itself now that it is off :)
Nov 09 15:51:02 <DocScrutinizer> it didn't on my short test a few minutes ago
Nov 09 15:51:39 <DocScrutinizer> for obscure reasons uBoot decided to disable charging when I selected "power down"
Nov 09 15:53:25 <DocScrutinizer> the whole power management topic is so FUBAR due to all the senseless "fixes" for imaginary special cases... :-(
Nov 09 15:54:02 <lindi-> DocScrutinizer: "The following commands will add a boot menu entry that switches to fast charging and turns off the backlight: "
Nov 09 15:54:08 <lindi-> DocScrutinizer: -- http://wiki.openmoko.org/wiki/Bootloader_commands
Nov 09 15:54:35 <lindi-> DocScrutinizer: any idea if that works for freerunner?
Nov 09 15:54:43 <DocScrutinizer> another senseless fix for a bug introduced by another senseless fix
Nov 09 15:55:01 <DocScrutinizer> no idea, sorry
Nov 09 15:55:52 <lindi-> DocScrutinizer: i don't think turning backlight off is senseless
Nov 09 15:55:53 <DocScrutinizer> but I really wonder what's the use of turning off the backlight via a menu you only can read when backlight is turned on
Nov 09 15:56:20 <DocScrutinizer> pure nonsense
Nov 09 15:57:16 <lindi-> DocScrutinizer: you can hit aux six times :)
Nov 09 15:57:23 <lindi-> DocScrutinizer: no need to read anything on screen
Nov 09 15:58:52 <DocScrutinizer> uBoot should simply enable 100mA charge (i.e. set PMU to a sane state) and never revert that. Neither on "power down" nor any other occasion - except for detecting a even more powerfull charger source and pushing to 500 / 1000
Nov 09 15:59:42 <lindi-> DocScrutinizer: well those patches have been sent ages ago
Nov 09 16:00:23 <lindi-> DocScrutinizer: but since this is NOR i don't have them :P
Nov 09 16:00:53 <DocScrutinizer> yeah, current uBoot - on detecting weak bat - enteres a "no charge, blink AUX LED from (WEAK!!) bat" state which it never will leave :-/
Nov 09 16:01:31 <DocScrutinizer> isn't that GREAT?
Nov 09 16:01:51 <lindi-> depends on what current means, there's a set of patches waiting on mailing lists :)
Nov 09 16:06:06 <DocScrutinizer> ok, wasn't aware of that
Nov 09 16:06:22 <DocScrutinizer> last time I mentioned the issue, nobody cared
Nov 09 16:06:34 <DocScrutinizer> so I didn't as well
Nov 09 16:08:39 <DocScrutinizer> you see, EE finally managed to give semi-decent HW to community. If community decides to screw it up via SW, and then starts to whine about the "eeew so buggy HW" I just turn arounf and face other less annoying topics
Nov 09 16:11:48 <SpeedEvil> 99% of the community think electrons are how leaders get chosen though.
Nov 09 16:12:48 <lindi-> DocScrutinizer: well I always cared but did not know enough to modify boot loaders back then :)
Nov 09 16:14:15 <lindi-> DocScrutinizer: and then came Qi :)
Nov 09 16:14:39 <d1b> lindi-: you modify qi ?
Nov 09 16:15:12 <d1b> DocScrutinizer: what hardware?
Nov 09 16:15:24 <DocScrutinizer> d1b: huh?
Nov 09 16:15:30 <lindi-> d1b: well it does not have a menu at all so no chance to select "force 500 mA" in it :)
Nov 09 16:16:17 <DocScrutinizer> d1b: I thought we are talking FR here
Nov 09 16:16:54 <d1b> lindi-: :)
Nov 09 16:17:01 <d1b> DocScrutinizer: sorry i wasn't sure who you meant by ee 
Nov 09 16:17:24 <d1b> DocScrutinizer: last time i asked the stupid question of why can't it even  charge in suspend i was told the gsm module is stupid :)
Nov 09 16:17:34 <DocScrutinizer> EE is my TPE located (ex) colleagues and me
Nov 09 16:17:47 <d1b> ok.
Nov 09 16:17:51 <DocScrutinizer> Electronic Engineering
Nov 09 16:17:54 <d1b> AH.
Nov 09 16:17:56 <d1b> sure.
Nov 09 16:18:12 <d1b> the guys who make stuff :)
Nov 09 16:19:05 <d1b> lindi-: are you able to keep an freerunner at around 90% charge if it is charging via wall / usb host...
Nov 09 16:20:03 <DocScrutinizer> d1b: The question is nonsense, as it actually *is* charging during suspend, and the answer was complete random garbage
Nov 09 16:21:09 <DocScrutinizer> d1b: you bet *lindi* is ;-P
Nov 09 16:22:21 <DocScrutinizer> for the rest of us mortals, see Pauls&my "battery FAQ" in wiki
Nov 09 16:23:50 <DocScrutinizer> d1b: the PMU HW will keep the battery between ~75% and 100% without any SW interaction
Nov 09 16:25:39 <PaulFertser> DocScrutinizer: not yet, i think we can release the .31 and then think about the bugfixing. OTOH this particular problem seems to be requiring attention. Luckily we have it on trac already so we won't forget about it anyway.
Nov 09 16:27:00 <d1b> DocScrutinizer: oh really.
Nov 09 16:27:38 <DocScrutinizer> PaulFertser: if anybody cares he should do a test with defined load on USB-VBUS (e.g. a shunt), and actually confirm what's max output current, and which is the current when device starts to heat up
Nov 09 16:27:42 <d1b> ok ill see the issue maybe.
Nov 09 16:28:08 <PaulFertser> DocScrutinizer: i agree
Nov 09 16:28:19 <d1b>  / wiki thingy but like i charge my phone atm it gets pretty hot, replacing the current battery as this one only goes for <1 hour with wifi on
Nov 09 16:30:18 <slaxxer> i hope the nov 9 image is better that the nov 6  shr
Nov 09 16:30:26 <DocScrutinizer> d1b: SHR? check settings-power to read out battery temperature. What you call hot should be less than 60° anyway
Nov 09 16:30:30 <d1b> is it out ?
Nov 09 16:30:41 <slaxxer> oemerge
Nov 09 16:30:42 <d1b> DocScrutinizer: um probably less than 60 :)
Nov 09 16:30:51 <d1b> slaxxer: like an image right?
Nov 09 16:31:01 <DocScrutinizer> that's absolutely normal
Nov 09 16:31:05 <slaxxer> http://build.shr-project.org/tests/mrmoku/oemerge/images/om-gta02/?C=M;O=D
Nov 09 16:31:12 <d1b> slaxxer: oh.
Nov 09 16:31:26 <d1b> DocScrutinizer: what wifi +battery <1 hour ?
Nov 09 16:31:36 <DocScrutinizer> strange
Nov 09 16:31:45 <d1b> i think not!
Nov 09 16:31:52 * d1b hopes
Nov 09 16:33:12 <d1b> was the 6th of nov image anygood ?
Nov 09 16:33:15 <DocScrutinizer> d1b: check out the bq27k-detail script in my people folder
Nov 09 16:33:17 <d1b>  / anything new
Nov 09 16:33:24 <d1b> DocScrutinizer: url plz...
Nov 09 16:34:13 <DocScrutinizer> http://people.openmoko.org/joerg/battery/bq27k-detail
Nov 09 16:34:18 <slaxxer> well   nov 6   was cool  looking but    gsm was borked
Nov 09 16:34:19 <d1b> i need bash right?
Nov 09 16:34:25 <DocScrutinizer> yep
Nov 09 16:34:33 <d1b> slaxxer: as in..
Nov 09 16:34:45 <d1b> so besides gsm borked what was different.
Nov 09 16:35:23 <slaxxer> pengy boot splash    slider controlls for mic and volume
Nov 09 16:35:28 <d1b> ooooooooooo
Nov 09 16:35:32 <d1b> perty
Nov 09 16:36:11 <d1b> when is the next unstable release due... then
Nov 09 16:36:31 <DocScrutinizer> today! always is "today" :-P
Nov 09 16:36:39 <slaxxer> i hear very soon   but u know how that goes
Nov 09 16:37:26 <slaxxer> maybe it will be an updated "testing" image    buy i dought it
Nov 09 16:37:37 <slaxxer> *but
Nov 09 16:38:41 <d1b> DocScrutinizer: before or after you wake the guys who are trying to stupidly (like me!) use the device as a phone ;)
Nov 09 16:39:10 <slaxxer> it works as a phonee
Nov 09 16:39:32 <slaxxer> just not very well  yet
Nov 09 16:39:35 <d1b> if i had two sims cards one for the moko and one for another phone then yes!
Nov 09 16:39:49 <d1b> alsa / audio has always *sucked*
Nov 09 16:39:56 <slaxxer> why 2 sims?
Nov 09 16:40:04 <d1b> slaxxer: one to fail at a phone the other for a phone
Nov 09 16:40:13 <d1b> gprs and hacking is fine tho
Nov 09 16:40:20 <d1b> just not for the phone part.
Nov 09 16:40:21 <sicu> it's a multitasking object, mine also works nicely as a paperweight
Nov 09 16:40:28 <d1b> slaxxer: hehehehe
Nov 09 16:40:31 <d1b> erh sicu *
Nov 09 16:40:55 <slaxxer> tired of paper weight mode
Nov 09 16:41:22 <sicu> admittedly, said paperweight is also my daily phone ;)
Nov 09 16:41:33 <slaxxer> what hardwar was android developed on?
Nov 09 16:41:40 <slaxxer> &hardware
Nov 09 16:41:56 <slaxxer> the moko?
Nov 09 16:42:21 <slaxxer> i realize they are paid a google    but   DAMN
Nov 09 16:42:54 <sicu> heh, that would've made it an easier job to port it to the moko, don't you think ;p
Nov 09 16:43:14 <d1b> DocScrutinizer: where should i put the output ?
Nov 09 16:43:16 <DocScrutinizer> the moko?
Nov 09 16:43:36 <DocScrutinizer> d1b: which output? wher to put?
Nov 09 16:43:58 <DocScrutinizer> bq27k?
Nov 09 16:44:09 <slaxxer> booting
Nov 09 16:44:18 <d1b> yep
Nov 09 16:44:34 <DocScrutinizer> the devices are called Neo, not moko
Nov 09 16:44:48 <d1b> close enough :)
Nov 09 16:45:03 <d1b> DocScrutinizer: any ideas re my output tho
Nov 09 16:45:10 <slaxxer> ok freerunner
Nov 09 16:45:21 <DocScrutinizer> d1b: the output is meant to be read by you. if you think it should be scrutinized by me, use pastebin
Nov 09 16:45:44 <d1b> i did pastebin
Nov 09 16:45:52 <d1b> http://pastebin.com/m2cefde0b
Nov 09 16:46:20 <lindi-> DocScrutinizer: can I force 500 mA by poking directly some memory mapped device? ;)
Nov 09 16:50:21 <DocScrutinizer> d1b: your bat is 100% full, has 32°C, and is charging
Nov 09 16:50:56 <DocScrutinizer> d1b: max current FR has drawn is ~2A what seems excessively high to me
Nov 09 16:51:37 <DocScrutinizer> also capacity of cell is estimated as 886 mWh which seems rather odd
Nov 09 16:52:11 <DocScrutinizer> d1b: is that an old worn cell?
Nov 09 16:52:20 <slaxxer> now theres 4 sliders on the call screen,,, 2 to mute an 2 to adjust
Nov 09 16:52:33 <DocScrutinizer> yay
Nov 09 16:52:56 <DocScrutinizer> 2 for mute seems rather exaggerated
Nov 09 16:53:08 <slaxxer> speaker-mic
Nov 09 16:53:21 <slaxxer> 1 for each
Nov 09 16:53:42 <DocScrutinizer> quite reasonable usecase to mute earpiece while mic is open
Nov 09 16:53:45 <slaxxer> gsm working:)
Nov 09 16:53:47 <d1b> DocScrutinizer: tis old
Nov 09 16:54:03 <d1b> slaxxer: so is good ?
Nov 09 16:55:32 * alfatangoxt is away: ................
Nov 09 16:55:40 <DocScrutinizer> (2 mute) that's the result of sw developers coding along API rather than usability considerations and use cases :-P
Nov 09 16:55:55 <slaxxer> http://pastebin.com/m4c30d8b1
Nov 09 16:56:07 <slaxxer> d1b  seems so
Nov 09 16:56:42 <DocScrutinizer> lindi-: sure, you can poke each PMU register the way you like
Nov 09 16:56:44 <slaxxer> email     from the armdslack people
Nov 09 16:56:55 <Zeti> hello
Nov 09 16:57:16 <Zeti> what's the lowest energy setting for the openmoko, while still recieving phone calls?
Nov 09 16:57:19 <d1b> slaxxer: that guy is a bit silly ;)
Nov 09 16:57:22 <DocScrutinizer> lindi-: prolly via I2C interface
Nov 09 16:57:23 <Zeti> I just tried suspend and nothing
Nov 09 16:57:37 <DocScrutinizer> lindi-: no memmap though
Nov 09 16:58:02 <lindi-> DocScrutinizer: http://git.openmoko.org/?p=u-boot.git;a=commit;h=4ed6f14590c443f20c12b2f39ec0c14f0c41c0f8
Nov 09 16:58:17 <lindi-> Zeti: nothing?
Nov 09 16:58:18 <DocScrutinizer> Zeti: standby
Nov 09 16:58:43 <slaxxer> this shr also has the new logo  at suspend screen wake
Nov 09 16:58:49 <DocScrutinizer> which will yield 40..150h of GSM 
Nov 09 16:59:47 <Zeti> grml
Nov 09 16:59:52 <Zeti> couldn't connect to fso
Nov 09 16:59:55 <Zeti> -_-
Nov 09 17:00:44 <DocScrutinizer> lindi-: great
Nov 09 17:01:23 <DocScrutinizer> Zeti: huh? don't get ya
Nov 09 17:01:32 <Zeti> that explains my phone not taking calls
Nov 09 17:02:28 <DocScrutinizer> aaah, SHR settings "couldn't connect to dbus or frameworkd" or sth
Nov 09 17:02:56 * d1b looks at old nokia :)
Nov 09 17:03:34 <DocScrutinizer> thought you maybe talk about "http://freesmartphone.org  404" 
Nov 09 17:03:58 <DocScrutinizer> or "ssh: no route to host"
Nov 09 17:06:36 <DocScrutinizer> d1b: this seems not to suggest the bat is too old and worn:
Nov 09 17:06:39 <DocScrutinizer> 0x29 - 0x28:     2  CYCL Cycle Count Since Learning Cycle High-Low Byte  Cycles       R
Nov 09 17:06:41 <DocScrutinizer> 0x2B - 0x2A:   205  CYCT Cycle Count Total High - Low Byte               Cycles       R
Nov 09 17:06:46 <d1b> DocScrutinizer: oh?
Nov 09 17:06:54 <d1b> so... what is my issue then...
Nov 09 17:07:29 <DocScrutinizer> it rather suggests you had a learning cycle 2 charges ago, which might have failed for some reason
Nov 09 17:07:45 <d1b> DocScrutinizer: m...? can haz fix it?
Nov 09 17:08:17 <DocScrutinizer> d1b: bateries might get worn out due to storage while depleted. or have issue from fab
Nov 09 17:08:30 <d1b> right.
Nov 09 17:08:38 <d1b> so the battery is useless atm to me.
Nov 09 17:08:44 <d1b> i already ordered a new one.
Nov 09 17:09:43 <DocScrutinizer> d1b: I suggest you do another "learning cycle" which simply means you need to discharge it until voltage actually drops below 3.0V (that's not the whole pic, but sufficient to advice)
Nov 09 17:10:07 <d1b> DocScrutinizer: so i shouldn't have ordered a new battery...
Nov 09 17:10:20 <d1b> DocScrutinizer: um...
Nov 09 17:10:25 <d1b> well last time i was using it like that.
Nov 09 17:10:39 <d1b> well actually it has been on 0% recently or it reports to be
Nov 09 17:10:41 <DocScrutinizer> d1b: a spare bat never is a bad thing to have :-)
Nov 09 17:10:47 <d1b> i turn it on and it says 0%
Nov 09 17:10:49 <d1b> and im like...?
Nov 09 17:11:35 <PaulFertser> d1b: imo regular nokia battery is enough for most gta02 users.
Nov 09 17:11:50 <DocScrutinizer> d1b: this bat the log was from is charged 100%. If your device reports diferent on switching on, you got a sw problem
Nov 09 17:12:04 <d1b> DocScrutinizer: tis not a software issue
Nov 09 17:12:14 <d1b> it is a hardware / battery issue.
Nov 09 17:13:20 <DocScrutinizer> d1b: how could hw/bat know which app is querying the bq27k? my script reports the bq27k thinks bat is at 100%
Nov 09 17:13:43 <d1b> DocScrutinizer: turn phone on
Nov 09 17:13:44 <d1b> use.
Nov 09 17:13:45 <DocScrutinizer> so if your app reports different, what might be the cause? hw??
Nov 09 17:13:57 <d1b> come back later 0%. reboot .. try again.
Nov 09 17:14:17 <d1b> actually i haven't drained it completly i guess to the point where it don't boot.
Nov 09 17:14:20 <d1b> DocScrutinizer: no idea.
Nov 09 17:14:24 <d1b> im not the EE guy :)
Nov 09 17:14:45 <DocScrutinizer> that's why I tell you this is NOT a hw problem
Nov 09 17:14:58 <DocScrutinizer> at least not a batter-hw problem
Nov 09 17:14:59 <d1b> DocScrutinizer: this is a hardware problem
Nov 09 17:15:07 <d1b> :)
Nov 09 17:15:18 <DocScrutinizer> ahhh, says the non-EE guy
Nov 09 17:15:24 <d1b> DocScrutinizer: exactly :)
Nov 09 17:15:46 * d1b turns auto suspend off / auto dim off
Nov 09 17:15:48 <d1b> gps on
Nov 09 17:15:55 <d1b> ! + wifi lets see how long this lasts
Nov 09 17:16:09 <DocScrutinizer> d1b: I'm no astrologist, so I tell you it's related to stars constellation
Nov 09 17:16:29 <lindi-> DocScrutinizer: why don't you measure it yourself? :/
Nov 09 17:16:34 <lindi-> sorry, meant d1b
Nov 09 17:16:57 <d1b> mm?
Nov 09 17:19:06 <DocScrutinizer> d1b: we frequently see bq27k driver to fail readout the ColoumbCounter chib BQ27000 inside bat correctly. This results in illme opening a requester saying "your bat is low!!!"
Nov 09 17:19:34 <d1b> DocScrutinizer: debian also
Nov 09 17:19:43 <DocScrutinizer> ignore that
Nov 09 17:20:09 <d1b> 89% from 100% atm --> estimated 47minutes left 
Nov 09 17:20:45 <DocScrutinizer> so could you please do another bq27k-detail printout NOW
Nov 09 17:21:27 <d1b> ok
Nov 09 17:21:40 <DocScrutinizer> d1b: and, btw 89% != 0%
Nov 09 17:22:29 <d1b> DocScrutinizer: i know this :)
Nov 09 17:23:47 <DocScrutinizer> d1b: with full backlite, GPS and WLAN and GPRS constant traffic you could actually reach the reported ~2A load on batery, which means it's empty after <45min
Nov 09 17:24:15 <d1b> good
Nov 09 17:24:33 <d1b> ill wasnt that the point :)
Nov 09 17:26:36 <DocScrutinizer> yesyes, the point is bg27k-detail reports a capacity of bat of 862mWh
Nov 09 17:27:03 <d1b> which is wrong
Nov 09 17:27:13 <DocScrutinizer> which should be more like 4000mWh
Nov 09 17:27:28 <DocScrutinizer> for a good bat
Nov 09 17:27:31 <d1b> yes.
Nov 09 17:27:50 <DocScrutinizer> as long as BQ27000 is calibrated
Nov 09 17:28:23 <DocScrutinizer> it could get out of calib by faulty learning cycle
Nov 09 17:28:31 <d1b> oh.
Nov 09 17:29:28 <DocScrutinizer> that's why I suggested to deplete bat until voltage is below some reasonable lower limit, like 3V3
Nov 09 17:30:52 <DocScrutinizer> you shouldn't do this with a current of >1000mA though
Nov 09 17:31:11 <d1b> erh. how do i know what current im at...
Nov 09 17:31:22 <DocScrutinizer> as it's natural for a cell to yield less capacity on high load
Nov 09 17:31:43 <DocScrutinizer> use bq27-detail, or shrsettings-power
Nov 09 17:32:02 <d1b> so just let it go to 0 atm?
Nov 09 17:32:02 <d1b> ish
Nov 09 17:32:11 <d1b> by leaving it alone and letting it suspend etc.?
Nov 09 17:32:28 <DocScrutinizer> please rephrase
Nov 09 17:32:42 <d1b> how would you like me to attempt to dischart it
Nov 09 17:33:14 <DocScrutinizer> check current-now, or shrsettings-power "current" reading
Nov 09 17:33:32 <d1b> trying too :
Nov 09 17:33:32 <d1b> )
Nov 09 17:33:36 <DocScrutinizer> make sure it's not >1000mA
Nov 09 17:33:59 <DocScrutinizer> disable GPRS if needed, as it eats random high current
Nov 09 17:34:13 <DocScrutinizer> disable suspend and dim
Nov 09 17:34:15 <d1b> nothing is on atm. just the phone.
Nov 09 17:34:19 <DocScrutinizer> let bat deplete
Nov 09 17:34:22 <d1b> so don't suspend and don't dim ?
Nov 09 17:34:26 <d1b> ok.
Nov 09 17:36:40 <DocScrutinizer> when bat voltage reading reaches <3V3 (and you got 0% for quite some time by then) - Do a bq27k-detail log, then connect charger, do a 2. log, then let bat charge completely
Nov 09 17:37:22 <DocScrutinizer> do a 3. log
Nov 09 17:37:29 <DocScrutinizer> then come back
Nov 09 17:37:47 <lindi-> DocScrutinizer: now 'neo1973 neo1973 info' returns "fast_charge" and backlight is off :)
Nov 09 17:37:58 <lindi-> DocScrutinizer: I mean "neo1973 charger status"
Nov 09 17:38:10 <d1b> wow to many steps ill just let it drain wake it up after that via a nokia battery and get the info, then log after the finished charge
Nov 09 17:38:17 <d1b> should be the same :)
Nov 09 17:38:24 <d1b> just going to use the nokia battery to start it.
Nov 09 17:38:37 <d1b> DocScrutinizer: im going to have to kill fso tho no?
Nov 09 17:39:59 <DocScrutinizer> d1b: since quite some months fso shouldn't power down device when CC reading reaches 0%. If yours does, you got an outdated version and for sure a problem with your bat life
Nov 09 17:40:31 <d1b> i thought fso would power the device down to avoidthe issue
Nov 09 17:40:36 <d1b> of not being able to boot
Nov 09 17:41:21 <DocScrutinizer> that should be done by kernel interrupt triggered in PMU at a certain bat voltage
Nov 09 17:41:35 <d1b> ok
Nov 09 17:41:52 <DocScrutinizer> the scheme of reading out CC in bat prooved to be buggy
Nov 09 17:42:30 <DocScrutinizer> bbl
Nov 09 17:42:42 <d1b> ok
Nov 09 17:42:45 <d1b> ty
Nov 09 17:44:54 <d1b> fun rebooting it twice --> 0% left now
Nov 09 17:59:25 <DocScrutinizer> d1b: ty, doesn't matter
Nov 09 17:59:52 <DocScrutinizer> [2009-11-09 18:36:38] <DocScrutinizer> when bat voltage reading reaches <3V3 (and you got 0% for quite some time by then) - Do a bq27k-detail log, then connect charger, do a 2. log, then let bat charge completely
Nov 09 18:00:51 <DocScrutinizer> the 0% point is off when bq27000 had wrong learning cycle
Nov 09 18:01:20 <DocScrutinizer> wrong learning cycle == a premature stop of discharge
Nov 09 18:01:51 <DocScrutinizer> thus: PLEASE discharge until bat VOLTAGE is below 3.3 Volt
Nov 09 18:02:05 <d1b> DocScrutinizer: im not stopping
Nov 09 18:02:07 <d1b> :)
Nov 09 18:03:38 <DocScrutinizer> you'll be amazed how long your system can run from a bat with 0% left ;-)
Nov 09 18:04:01 <d1b> not really ;)
Nov 09 18:04:02 <d1b> heheheh
Nov 09 18:04:27 <d1b> i just wish i tried this before ordering the other battery
Nov 09 18:04:29 <d1b> :)
Nov 09 18:05:44 <DocScrutinizer> bbl
Nov 09 18:12:30 <d1b> ooo it turned off
Nov 09 18:12:46 <fredrin> some news about latest shr-unstable, got a version from sept, some things annoyes the hell out of me
Nov 09 18:13:23 <fredrin> like if i get a new sms, i need to close the sms app and then reload it again to see the new sms
Nov 09 18:13:34 <fredrin> takes 2 min if you got like 100 sms in the inbox
Nov 09 18:14:05 <d1b> fredrin: dont worry there is this other bug which deletes your smses
Nov 09 18:14:08 <d1b> ;)
Nov 09 18:14:12 <fredrin> sweet
Nov 09 18:16:51 <Zeti2>  * ERROR: Cannot satisfy the following dependencies for fsousaged:
Nov 09 18:16:52 <Zeti2>          *  libfso-glib0 (>= 0.2.1+gitr47+7608c8d98bb65bb5beca6621eb86920b71df1b
Nov 09 18:16:52 <Zeti2> c9) *
Nov 09 18:16:58 <Zeti2> can somebody translate this for me?
Nov 09 18:17:05 <Zeti2> or rather
Nov 09 18:17:13 <Zeti2> where do i get it if not from the official repo
Nov 09 18:20:21 <Zeti2> ok manual install does it
Nov 09 19:22:11 <Gabrys> I got this error 
Nov 09 19:22:18 <Gabrys> and managed to find this ipk
Nov 09 19:30:35 <CIA-53> freesmartphone.org: 03mickey 07cornucopia * r149bbca9cc4b 10/libfsobasics/ (fsobasics/utilities.vala tests/testutilities.vala): libfsobasics: rewrite removeTree() for systems that lack proper d_type reporting in readdir(2)
Nov 09 19:30:36 <CIA-53> freesmartphone.org: 03mickey 07cornucopia * r0f3bbcab77b6 10/fsogsmd/ (src/lib/sms.vala tests/testsms.vala): fsogsmd: testsms working again
Nov 09 19:30:37 <CIA-53> freesmartphone.org: 03mickey 07cornucopia * r89022de0d4ec 10/libfsobasics/ (fsobasics/utilities.vala tests/testutilities.vala): 
Nov 09 19:30:37 <CIA-53> freesmartphone.org: libfsobasics: add Utility.createBacktrace()
Nov 09 19:30:37 <CIA-53> freesmartphone.org: NOTE: function disabled until Vala 0.7.9 or (inofficial) 0.7.8.1 release
Nov 09 19:30:41 <CIA-53> freesmartphone.org: 03mickey 07cornucopia * r60a5eacce377 10/fsousaged/src/ (bin/main.vala plugins/dbus_service/plugin.vala): 
Nov 09 19:30:44 <CIA-53> freesmartphone.org: fsousaged: fix race condition that broke dbus system activation
Nov 09 19:30:46 <CIA-53> freesmartphone.org: NOTE: Do NOT use plain deferred initialization (Idle.add(do_more_init_stuff))
Nov 09 19:30:48 <CIA-53> freesmartphone.org: for plugins that are dbus system activated, since in that case, the dbus call
Nov 09 19:30:50 <CIA-53> freesmartphone.org: will be the first action inserted in the mainloop queue -- even
Nov 09 19:30:52 <CIA-53> freesmartphone.org: before your idle call, hence parts may not be initialized at that time.
Nov 09 20:16:48 <luke-jr> PaulFertser: "It's running Android at the present time. It is model number GTA02. Since I can't pull up an xterm, I can't check that file. "
Nov 09 20:16:50 <luke-jr> :/
Nov 09 21:02:32 <Kamping_Kaiser> luke-jr: surely they can pop the back off and look at the serial(s)
Nov 09 21:05:06 <luke-jr> Kamping_Kaiser: ?
Nov 09 21:05:51 <Kamping_Kaiser> luke-jr: wasn't the problem to do with finding out the model of the device? (i'm trying to remember from yesterday)
Nov 09 21:06:48 <luke-jr> yeah
Nov 09 21:12:22 <tomcatek> Anyone is using SHR unstable by mrmkou?
Nov 09 21:44:22 <slaxxer> tomcatek yes
Nov 09 21:47:28 <slaxxer> http://shr.bearstech.com/tests/mrmoku/oemerge/images/om-gta02/
Nov 09 21:47:51 <tomcatek> slaxxer: do You have an issue with suspending on demand
Nov 09 21:48:02 <tomcatek> slaxxer: or powering back the phone
Nov 09 21:48:22 <slaxxer> well it seems to not suspend automaticly
Nov 09 21:48:34 <slaxxer> i manual now
Nov 09 21:48:37 <tomcatek> it does for me
Nov 09 21:48:44 <slaxxer> in suspend
Nov 09 21:49:08 <tomcatek> when I'm pressing power button I don't get the casual menu with suspend option
Nov 09 21:49:25 <slaxxer> out ok
Nov 09 21:49:31 <slaxxer> i do
Nov 09 21:49:50 <slaxxer> same shutdown menu
Nov 09 21:50:04 <tomcatek> when I'm trying to power phone back i have to keep power button pressed for a while before any reaction
Nov 09 21:50:42 <slaxxer> u have uboot?
Nov 09 21:51:02 <slaxxer> Qi?
Nov 09 21:52:06 <slaxxer> i had issues with nov 6 .jffs2
Nov 09 21:52:11 <tomcatek> uboot
Nov 09 21:52:23 <slaxxer> nov 9   works for me
Nov 09 21:52:31 <tomcatek> but I ment powering from suspend
Nov 09 21:52:50 <slaxxer> not so far here
Nov 09 22:00:03 <slaxxer> power light on
Nov 09 22:01:27 <tomcatek> hm..
Nov 09 22:01:55 <tomcatek> frameworkd.log shows, that pressing power button is recognised normally
Nov 09 22:02:19 <tomcatek> but phone reasumes from suspend after 2-3 seconds
Nov 09 22:11:14 <Gabrys> is it hard to port the sliders-during-call to shr-unstable?
Nov 09 22:12:29 <Gabrys> I mean adjust audio-settings-during-call-sliders
Nov 09 22:18:00 <tomcatek> Gabrys: if You would done that, You would have few "fans" ;]
Nov 09 22:18:17 <Gabrys> "few" or "a few"
Nov 09 22:20:10 <tomcatek> life will show :P
Nov 09 22:24:19 <Gabrys> in fact I need this, automatic wifi (which is handled nicely with mofi if added as init script and resume.d file), better browser (which I'm going to write extending arora a bit), minimalistic mail client and IM application (which can be done in browser once there is good one)
Nov 09 22:24:58 <Gabrys> and then we can compete with Android 
Nov 09 22:26:13 <Gabrys> saving sent SMS-es would be nice too ;-)
Nov 10 00:57:54 <luke-jr> what is "Freerunner Basic"?
Nov 10 01:02:14 <slaxxer> where u see that at?
Nov 10 01:02:14 <max_posedon> huh?
Nov 10 01:07:21 <slaxxer> earth to luke
Nov 10 01:12:22 <luke-jr> slaxxer: don't wanna say? :/
Nov 10 01:13:56 <PaulFertser> luke-jr: nobody has an idea
Nov 10 01:14:17 <PaulFertser> luke-jr: probably that's just some way some distributors call FR with no accessories.
Nov 10 01:16:55 <luke-jr> does "Neo1973 Advanced" mean anything either?
Nov 10 01:18:47 <luke-jr> did the 1973 work well for its specs?
Nov 10 01:30:05 <PaulFertser> luke-jr: gta01==Nea1973
Nov 10 01:30:42 <PaulFertser> luke-jr: Advanced means that it's packaged with debug board, a screwdriver, guitar pick and a special case to carry all that stuff iirc.
Nov 10 01:54:51 <luke-jr> PaulFertser: guitar pick? srsly? wtf? :p
Nov 10 01:55:23 <PaulFertser> luke-jr: handy for disassembling
Nov 10 01:57:02 <luke-jr> lol
Nov 10 01:57:16 <luke-jr> so is it usable? or is it buggy like Freerunner once was?
Nov 10 01:57:41 <luke-jr> found one for sale, and the specs don't look *too* bad for my purpose
Nov 10 02:00:55 <PaulFertser> luke-jr: kinda usable
Nov 10 02:01:02 <PaulFertser> luke-jr: graphics is faster than on FR
Nov 10 02:01:13 <PaulFertser> luke-jr: MP models can actually be used as a phone.
Nov 10 02:01:26 <DocScrutinizer> luke-jr: gta01 aka Neo 1973 was pedecessor  (wtf aspell doesn't know this word :-/ )  of Freerunner, and it was a mere development version which for sure has some hw flaws
Nov 10 02:01:28 <luke-jr> MP?
Nov 10 02:01:32 <PaulFertser> luke-jr: battery lifetime is considerably worse
Nov 10 02:01:51 <luke-jr> DocScrutinizer: it's "predecessor"
Nov 10 02:02:02 <PaulFertser> DocScrutinizer: it's predecessor :)
Nov 10 02:02:04 <DocScrutinizer> arrrg
Nov 10 02:02:06 <luke-jr> DocScrutinizer: are the hw flaws documented for v4?
Nov 10 02:02:16 <PaulFertser> luke-jr: gta01v4?
Nov 10 02:02:20 <luke-jr> err Bv4
Nov 10 02:02:21 <PaulFertser> luke-jr: or gta01Bv4?
Nov 10 02:02:24 <DocScrutinizer> lol, yes n schematics
Nov 10 02:02:43 <luke-jr> DocScrutinizer: ?
Nov 10 02:02:58 <PaulFertser> luke-jr: all the flaws are there to see :)
Nov 10 02:03:25 <luke-jr> -.-
Nov 10 02:03:34 <luke-jr> so not documented as in "what effect it has"?
Nov 10 02:03:36 <DocScrutinizer> studying the schematics you'll find it has e.g. no way to reliably shutdown GSM
Nov 10 02:03:46 <DocScrutinizer> except removing bat :-P
Nov 10 02:04:16 <luke-jr> ok, that isn't a bug that affects real-world use afaik
Nov 10 02:04:25 <luke-jr> maybe battery life when you're on a plane
Nov 10 02:04:28 <PaulFertser> DocScrutinizer: btw, it's now obvious for me that pcf50606 won't allow to charge foreign batteries in a comfortable way ever :(
Nov 10 02:04:30 <DocScrutinizer> haha, depends
Nov 10 02:05:10 <DocScrutinizer> luke-jr: ^^ see PaulFertser for another flaw
Nov 10 02:05:11 <PaulFertser> DocScrutinizer: because charge current limit is the same as usb current limit basically, there's only one current sensor in there.
Nov 10 02:05:33 <luke-jr> O.o?
Nov 10 02:05:43 <DocScrutinizer> PaulFertser: well possibly the case, yes
Nov 10 02:05:56 <PaulFertser> DocScrutinizer: so even if one enables 200mA charge current, he probably needs to at least suspend the device so it'll be reasonable enough.
Nov 10 02:06:12 <DocScrutinizer> ack
Nov 10 02:06:12 <PaulFertser> Because charging with ~40mA is uber-slow :)
Nov 10 02:06:22 <luke-jr> anything that would stop my technically literate wife from using it to make/receive calls on a regular basis? :p
Nov 10 02:06:23 <DocScrutinizer> hehe
Nov 10 02:06:40 <PaulFertser> DocScrutinizer: so i'd recommend to just change 10k R to be ~70k to conform to bl-5c specs.
Nov 10 02:06:54 <DocScrutinizer> ack #2
Nov 10 02:06:57 <luke-jr> eg, provided I do the software bits
Nov 10 02:07:28 <PaulFertser> luke-jr: hm... it doesn't last long on battery.
Nov 10 02:07:31 <DocScrutinizer> luke-jr: nah, basically gta01 is a better device than gta02 :-P
Nov 10 02:07:52 <luke-jr> DocScrutinizer: ?!?!
Nov 10 02:08:10 <DocScrutinizer> e.g. it has *faster* graphics
Nov 10 02:08:18 <luke-jr> PaulFertser: as in, 5 minutes, 30 minutes, 2 hours?
Nov 10 02:09:09 <PaulFertser> luke-jr: 4 hours running with backlight on. ~30 hrs suspended.
Nov 10 02:09:18 <luke-jr> suspended can receive calls?
Nov 10 02:09:29 <PaulFertser> luke-jr: MP models yes
Nov 10 02:09:34 <luke-jr> wtf is MP?
Nov 10 02:09:38 <PaulFertser> luke-jr: mass production
Nov 10 02:09:39 <DocScrutinizer> sure, otherwise it would be called "off" XD
Nov 10 02:09:41 <PaulFertser> mass produced
Nov 10 02:09:52 <luke-jr> I see, which is anything advertised as "Neo1973 Advanced"? :)
Nov 10 02:10:06 <PaulFertser> I guess so
Nov 10 02:10:12 <DocScrutinizer> no, that's not related I guess
Nov 10 02:10:16 <luke-jr> DocScrutinizer: classical Linux "suspend" means off plus instant on
Nov 10 02:10:28 <PaulFertser> luke-jr: same here, it resumes on irq from gsm
Nov 10 02:10:45 <luke-jr> ah right, gsm is another CPU ;)
Nov 10 02:10:53 <DocScrutinizer> exactly
Nov 10 02:10:53 <PaulFertser> luke-jr: also gta01 lacks NOR so it can be put to a state where you can't boot it without debug board.
Nov 10 02:11:12 <luke-jr> PaulFertser: O.o
Nov 10 02:11:17 <DocScrutinizer> aka brick it
Nov 10 02:11:28 <luke-jr> I don't get the NOR connection
Nov 10 02:11:51 <DocScrutinizer> NOR is your "recovery BIOS"
Nov 10 02:11:54 <PaulFertser> luke-jr: gta02 has NOR that can't be written without tricks. Even if you hose your BL in NAND you can boot from BL from NOR.
Nov 10 02:12:07 <luke-jr> oh
Nov 10 02:12:19 <luke-jr> so basically it's an anti-brick backup
Nov 10 02:12:33 <luke-jr> not something that will be a problem in regular use :)
Nov 10 02:12:45 <DocScrutinizer> yep
Nov 10 02:13:03 <DocScrutinizer> for normal use differences are quite minimal
Nov 10 02:13:16 <DocScrutinizer> gta01 has no WiFi
Nov 10 02:13:50 <DocScrutinizer> and it has less storage builtin
Nov 10 02:14:55 <PaulFertser> luke-jr: and is a second-class citizen in the community because not many devs have it :-/
Nov 10 02:15:14 <DocScrutinizer> and it reliably *won't* boot with flat bat :-P
Nov 10 02:16:05 <luke-jr> DocScrutinizer: not even w/ dev board? <.<
Nov 10 02:16:06 <DocScrutinizer> which you'll achieve easily as Modem won't shut down
Nov 10 02:16:20 <DocScrutinizer> not even with debbo
Nov 10 02:16:25 <luke-jr> wtf
Nov 10 02:16:33 <luke-jr> perm brick unless it's kept on charger?
Nov 10 02:16:56 <PaulFertser> DocScrutinizer: i've just prepared a qi version for gta01 which enables fast charge unconditionally on init :D
Nov 10 02:17:05 <DocScrutinizer> nope you "just" need to take care not to deplete bat completely
Nov 10 02:17:22 <DocScrutinizer> or get an external charger
Nov 10 02:17:35 <luke-jr> seriously, there is no way to recover?
Nov 10 02:17:41 <PaulFertser> luke-jr: you can charge its battery with any dumb nokia charger or you can boot gta01 with any nokia bl-5c battery
Nov 10 02:17:47 <luke-jr> ah
Nov 10 02:17:54 <DocScrutinizer> PaulFertser: I think it will motoboat nevertheless
Nov 10 02:17:57 <PaulFertser> Though hot-swapping batteries on gta01 is prohibited.
Nov 10 02:18:15 <luke-jr> I think if it's flat, hot-swapping is not happening :p
Nov 10 02:18:28 <DocScrutinizer> ABSOLUTELY
Nov 10 02:18:32 <DocScrutinizer> prohibited
Nov 10 02:18:58 <PaulFertser> DocScrutinizer: well, folks who use gta01 daily (pyneo guys) usually can't boot fully with a flat bat but at least BL works, so if the fast charge is enabled they should be able to.
Nov 10 02:19:01 <DocScrutinizer> you NEVER remove bat from a powered device
Nov 10 02:19:10 <PaulFertser> Unless the device is not gta01
Nov 10 02:19:31 <DocScrutinizer> exactly
Nov 10 02:20:32 <DocScrutinizer> PaulFertser: I think Vsys brownout on gta01 will happen even before BL gets a chance to execute a single opcode
Nov 10 02:21:19 <DocScrutinizer> so a really depleted bat won't boot the device
Nov 10 02:21:41 <DocScrutinizer> thus it never will get charged again
Nov 10 02:21:57 <DocScrutinizer> if you're unlucky with PMU reg settings
Nov 10 02:22:45 <PaulFertser> DocScrutinizer: a really depleted indeed won't allow to boot but luckily in RL it's not usually the case.
Nov 10 02:22:47 <DocScrutinizer> that's the crux of "don't boot on flat bat" issue
Nov 10 02:23:21 <DocScrutinizer> everything else is "Kindergarden"
Nov 10 02:23:24 <DocScrutinizer> ;-D
Nov 10 02:25:13 <Snyfer> Hello guys, sorry if I interrupt you... I'm stuck with something, I'm trying a gentoo on my brand new freerunner, but at boot the kernel hangs at "Freeing init memory" right after mouting the rootfs... The kernel is not crashed, if I push the power button a message is printed saying that I did so, and if I wait enough (say 5minutes) a prompt arrive from nowhere
Nov 10 02:26:06 <Snyfer> I've seen some similar problem on the freerunner when googling for it, but none has the answer on how to fix, do you anything about it ?
Nov 10 02:28:43 <PaulFertser> Snyfer: looks like your init takes too long.
Nov 10 02:29:18 <PaulFertser> Snyfer: with default Qi config you do not get any messages from userland on LCD.
Nov 10 02:30:08 <Snyfer> PaulFertser: I've append loglevel=8
Nov 10 02:30:17 <Snyfer> I like seeing it booting
Nov 10 02:31:57 <PaulFertser> Snyfer: yes, so you see kernel messages
Nov 10 02:32:05 <PaulFertser> Snyfer: but not the messages from rc scripts
Nov 10 02:32:05 <Snyfer> yes I do
Nov 10 02:32:10 <Snyfer> ooh ok
Nov 10 02:32:47 <Snyfer> PaulFertser: is that documented on the wiki page ? I haven't red about it
Nov 10 02:33:05 <PaulFertser> Snyfer: probably console=tty0 should come first in the kernel arguments
Nov 10 02:33:14 <PaulFertser> Snyfer: i'm afraid it's not
Nov 10 02:33:32 <Snyfer> PaulFertser: ookayy, thank you i'm giving it a try
Nov 10 02:34:11 <Snyfer> PaulFertser: it seems you always have the answer... I'm stuck since hours with this thing :)
Nov 10 02:34:53 <PaulFertser> Snyfer: (always have the answer) if only that was true...
Nov 10 02:35:18 <Snyfer> at least for my own problems :)
Nov 10 02:35:21 <PaulFertser> I just seem to have lots of spare time to chat on irc and yet no time to do real things.
Nov 10 02:35:26 <Snyfer> and that's all I need ;)
Nov 10 02:35:49 <Snyfer> so get out, breath some fresh air
Nov 10 02:35:51 <PaulFertser> Snyfer: you're lucky i'm not asleep :)
Nov 10 02:36:01 <PaulFertser> 5:30am here
Nov 10 02:36:08 <Snyfer> what time is it at your place ?
Nov 10 02:36:27 <Snyfer> already awake or still awake ?
Nov 10 02:39:20 <PaulFertser> Snyfer: already. Got tired after coming home from work and fell asleep at 8pm :D
Nov 10 02:39:37 <Snyfer> wowo I see
Nov 10 02:40:05 <Snyfer> here it's 3:40am and i don't wanna go sleep till gentoo boots :)
Nov 10 02:40:41 <PaulFertser> Snyfer: you say a prompt arrives so it means it boots
Nov 10 02:41:20 <Snyfer> PaulFertser: ok I mean, till I don't see those wonderfull openrc line where it's written OK in green :)
Nov 10 02:42:59 <Snyfer> putting console=tty0 as the first parameter in append-GTA02 file didn't make it :(
Nov 10 02:43:13 <PaulFertser> Snyfer: sure
Nov 10 02:43:33 <PaulFertser> Snyfer: you need to recompile Qi i'm afraid. Or let me try to understand kernel docs about the console parameter
Nov 10 02:44:05 <Snyfer> PaulFertser: Don't worry I'll take a look at it
Nov 10 02:46:23 <PaulFertser> Snyfer: hm, console=tty0 comes first already...
Nov 10 02:46:31 <Snyfer> PaulFertser: erf :s
Nov 10 02:46:32 <PaulFertser> Snyfer: probably it should come last then :)
Nov 10 02:47:34 <Snyfer> according to this doc http://elibrary.fultus.com/technical/topic/com.fultus.linux.howtos/howtos/Remote-Serial-Console-HOWTO/configure-kernel.html the order doesn't really matter, there should not be to console referencing the same type of tty, for example one for a serial tty, one for a virtual one and one for a usb one
Nov 10 02:47:54 <slaxxer> PaulFerster  whats the news with gta02-core?
Nov 10 02:48:12 <PaulFertser> Snyfer: for kernel messages it doesn't matter. But only one device can become /dev/console after boot
Nov 10 02:49:06 <Snyfer> PaulFertser: ok, so you want me to try with console=tty0 ate the end of the parameters, right ?
Nov 10 02:49:17 <luke-jr> what is OpenMoko doing now that they've out with the crappy Wikireader?
Nov 10 02:49:41 <PaulFertser> Snyfer: i'm not sure it'll really help since console=tty0 is hardcoded in the parameters of Qi and comes first.
Nov 10 02:50:32 <Snyfer> PaulFertser: okay
Nov 10 02:50:57 <PaulFertser> Snyfer: http://forum.soft32.com/linux/kernel-messages-multiple-VGA-serial-consoles-ftopict440064.html
Nov 10 02:51:49 <PaulFertser> Snyfer: is it easy for you to recompile Qi?
Nov 10 02:52:34 <darmou> Wikireader, what a joke lol
Nov 10 02:52:57 <PaulFertser> darmou: somehow it sells and that's what matters
Nov 10 02:53:24 <darmou> PaulFertser: hopefully it will allow them to develop other products if there is money coming in
Nov 10 02:53:35 <Snyfer> PaulFertser: yep no problem I've cloned the repository
Nov 10 02:56:25 <PaulFertser> DocScrutinizer: http://lkml.org/lkml/2009/11/9/449
Nov 10 02:56:46 <PaulFertser> Slowly but steadily we push stuff upstream :)
**** ENDING LOGGING AT Tue Nov 10 02:59:57 2009