**** BEGIN LOGGING AT Tue Jan 26 02:59:56 2010
Jan 26 03:05:42 <buluca> hi, did you experience any trouble trying to make Qi boot from a large (namely 8 GB) sdhc card?
Jan 26 03:08:37 <buluca> here it boots from nand, apparently just skipping the sdhc
Jan 26 06:37:48 <mohan43u> hcitool cc "${BDADDR}" while giving this command to connect.. it connects and drops immediately..
Jan 26 06:38:07 <mohan43u> I'm not able to give hcitool auth "${BDADDR}"
Jan 26 06:38:15 <mohan43u> can somebody help me?
Jan 26 06:38:36 <mohan43u> debian(testing)
Jan 26 07:58:47 <PaulFer``> I've recently learned that to cope with relativity effects GPS clocks are actually pre-skewed. :-O
Jan 26 12:54:40 <Weiss> DocScrutinizer: results of my hwclock test: it reset to "Sat Jan 1 2000" after about 15 minutes without battery
Jan 26 12:55:02 <PaulFer``> Weiss: +1 to the battery dead then
Jan 26 12:55:12 <Weiss> GTA02A6 (no fixes), drm-tracking kernel etc
Jan 26 12:55:23 <Weiss> what's the issue being debugged?
Jan 26 12:55:30 <PaulFer``> DocScrutinizer: the misterious fault of the batteries :)
Jan 26 12:55:50 <DocScrutinizer> Weiss: thanks
Jan 26 12:56:22 <Weiss> hw clock backup battery or something?
Jan 26 12:56:26 <PaulFer``> Weiss: yes
Jan 26 12:56:31 <PaulFer``> Exactly
Jan 26 12:56:36 <DocScrutinizer> please everybody with a FR: can you do the following test: check hw clock settings with command "hwclock" in terminal. (make sure it's not like 01.01.1970 or sth, a reasonable time would be fine). Then power down device and remove battery for 5 minutes. Reinsert battery, boot up to a state without internet connectivity and without using GPS, and check again with "hwclock". Then report here if time is roundabout the same it was before 
Jan 26 12:56:37 <DocScrutinizer> battery removal, or if it's been reset by that procedure
Jan 26 12:56:46 <DocScrutinizer> PS re "please everybody": while you fremove your bat, you have 5 minutes to copy the datecode under the battery. Please post this datecode together with your result of "time reset" / "time kept correct"
Jan 26 12:57:13 <Weiss> ah, I didn't read the datecode..
Jan 26 12:57:21 <DocScrutinizer> Thanks a lot. This will help us building better devices (if we ever get to do such enterprise)
Jan 26 12:58:06 <Weiss> is it a hardware problem, or something like the kernel not twiddling the right registers to charge the battery properly?
Jan 26 12:59:17 <DocScrutinizer> Weiss: the 1mio dollar question ;-P
Jan 26 12:59:24 <Weiss> ah..
Jan 26 13:04:28 <PaulFer``> Weiss: i think i checked and i was sure the register was set properly.
Jan 26 13:04:47 <PaulFer``> win 18
Jan 26 13:21:48 <pespin> PaulFer``, I remember my phone beign set to 1 Jan 2000 some days ago too :)
Jan 26 13:22:10 <PaulFer``> pespin: unfortunately, that's not a surprise
Jan 26 13:22:45 <djj> 20090317 and... time kept :o
Jan 26 13:23:58 <PaulFer``> djj: sure you waited for 5 minutes without the main battery and usb plugged?
Jan 26 13:28:53 <djj> PaulFer``: yes, i'm sure of it
Jan 26 13:29:12 <PaulFer``> djj: lucky you. Interesting. DocScrutinizer ^^^
Jan 26 13:31:26 <DocScrutinizer> please everybody reporting: feel free to update topic. thanks
Jan 26 13:32:48 <DocScrutinizer> djj: you don't have internet (so time is set via NTP), GPS enabled, or registered with GSM and time set via GSM time broadcast?
Jan 26 13:33:09 <DocScrutinizer> PS re "please everybody": while you fremove your bat, you have 5 minutes to copy the datecode under the battery. Please post this datecode together with your result of "time reset" / "time kept correct"
Jan 26 13:33:44 <DocScrutinizer> aah sorry, missed the beginning of line
Jan 26 13:34:38 <h4v> 20080725 time kept
Jan 26 13:35:08 <djj> DocScrutinizer: yeah, no ntp or gps and it hadn't registered with gsm yet :)
Jan 26 13:35:44 <DocScrutinizer> djj: h4v: many thanks :-)
Jan 26 13:40:09 <meuh> 20091025 time reset
Jan 26 13:40:43 <PaulFer``> meuh: 1025? That late in the run?
Jan 26 13:41:04 <meuh> ordered in january 2010 :)
Jan 26 13:41:09 <PaulFer``> Kewl
Jan 26 13:41:13 <DocScrutinizer> A7?
Jan 26 13:41:29 <meuh> A7, yes
Jan 26 13:44:52 <Weiss> DocScrutinizer: my date code (time loss already added to the totals): 20080925
Jan 26 13:45:39 <DocScrutinizer> thnx
Jan 26 13:45:52 <meuh> Hardware        : GTA02
Jan 26 13:45:52 <meuh> Revision        : 0360
Jan 26 13:45:52 <meuh> Serial          : 0000000000000000
Jan 26 13:46:19 <DocScrutinizer> lol
Jan 26 13:52:39 <meuh> lol ? that's the only piece of information i'm currently able to retrieve (newbie inside)
Jan 26 13:53:24 <DocScrutinizer> lol on the ser#, not on your post. thanks for sharing :-)
Jan 26 13:54:06 <meuh> ok ;) i hope my IMEI is not set to the same value
Jan 26 13:54:25 <DocScrutinizer> hehehe we that one too, long ago
Jan 26 13:54:51 <pespin> DocScrutinizer, will you still doing the poll this afternoon? I'm a bit busy right now ;)
Jan 26 13:55:05 <DocScrutinizer> sure pespin 
Jan 26 13:55:21 <pespin> ok, hope I'll remember :)
Jan 26 13:55:41 <DocScrutinizer> I'll repost the call every once in a while
Jan 26 13:58:55 <Q-Master> DocScrutinizer: 20080901 and time kept.
Jan 26 13:59:21 <DocScrutinizer> please everybody reporting: feel free to update topic. thanks
Jan 26 14:01:02 <DocScrutinizer> on a second thought, maybe it's better the chanops do that (or any other user acustomed to doing it, so the topic doesn't deteriorate)
Jan 26 14:01:38 <Q-Master> DocScrutinizer: you should do it yourself then. 8)
Jan 26 14:01:41 <DocScrutinizer> howdy raster
Jan 26 14:01:56 <raster> DocScrutinizer:  DOCZZZZ!
Jan 26 14:02:14 <SpeedEvil> raster: are you aware of any similar fuzzy-keyboard work to work with hwkeybs?
Jan 26 14:02:37 <JaMa> ahh loosers are still winning a bit :)
Jan 26 14:02:45 <raster> SpeedEvil: none, actually, but the same principle can work i'd guess
Jan 26 14:02:46 <DocScrutinizer> SpeedEvil: thinking N900 ;-P
Jan 26 14:03:13 <SpeedEvil> Possibly, yes. 
Jan 26 14:03:28 <SpeedEvil> Though in priciple you could even jam it into - say - screen
Jan 26 14:05:49 <DocScrutinizer> please everybody with a FR: can you do the following test: check hw clock settings with command "hwclock" in terminal. (make sure it's not like 01.01.1970 or sth, a reasonable time would be fine). Then power down device and remove battery for 5 minutes. Reinsert battery, boot up to a state without internet connectivity and without using GPS, without registering to GSM (remove SIM if no PIN set) and check again with "hwclock". Then report 
Jan 26 14:05:51 <DocScrutinizer> here if time is roundabout the same it was before battery removal, or if it's been reset by that procedure. while you remove your bat, you have 5 minutes to copy the datecode under the battery. Please post this datecode together with your result of "time reset" / "time kept correct".  Thanks a lot. This will help us building better devices (if we ever get to do such enterprise)
Jan 26 14:08:10 <djp_> anyone have issues installing the latest shr-unstable? i past choosing the language and the illume shr profile, but then after selecting next on the first run screen, it loads the desktop, lots of little black menu boxes appear at the bottom (normally shows 3, currently showing 10) and the fr can't seem to connect to my mobile network...
Jan 26 14:10:45 <DocScrutinizer> djp_: known issue. Devels are working on it. Use a older version
Jan 26 14:11:38 <djp_> DocScrutinizer: ah, thanks not just me then. :)
Jan 26 14:14:02 <JaMa> djp_: connect to gsm should work
Jan 26 14:14:42 <JaMa> djp_: and those 10 buttons are better to ignore untill we switch to illume2 (AFAIK nobody is working on 10 buttons..)
Jan 26 14:15:11 <DocScrutinizer> raster: listen ^^
Jan 26 14:15:52 <JaMa> it's probably some changed logic in theme.. not e fault as such
Jan 26 14:16:14 <DocScrutinizer> ooh
Jan 26 14:17:01 <DocScrutinizer> whoooopy, >200 users
Jan 26 14:17:15 <JaMa> but I mean that theme wasn't changed.. just now it behaves a bit different (maybe something wasn't specified right from the start)
Jan 26 14:18:38 <djp_> JaMa: tried using settings option but received an application error...
Jan 26 14:18:52 <djp_> DocScrutinizer: should i revert to an older kernel image also?
Jan 26 14:19:24 <playya_> DocScrutinizer, actually no. minus your accounts minus ChanServ =199 :)
Jan 26 14:19:56 <DocScrutinizer> yeah spaetz left after a second
Jan 26 14:20:26 <playya_> let's spank him when he's back :)
Jan 26 14:22:04 <DocScrutinizer> djp_: always use the kernel and modules matching the rootfs date, as a rule of thumb
Jan 26 14:27:33 <dos1> DocScrutinizer: GTA02A5 - 20080621 - time reset
Jan 26 14:29:28 <djp_> DocScrutinizer: thanks
Jan 26 14:31:26 <gena2x> had discarge in <5 seconds, DATECODE 20080821
Jan 26 14:43:52 <matze|> DocScrutinizer: DATECODE: 20080925 - time reset
Jan 26 15:19:56 <ZaPPaS> DocScrutinizer: GTA02A6 (Buzz-fix) - 20080707 - time reset
Jan 26 15:33:19 <lindi-> DocScrutinizer: are you logging the timecodes somewhere too?
Jan 26 15:33:53 <DocScrutinizer> lindi-: not really. just trying to find a pattern. obviously there isn't any
Jan 26 15:36:55 <octavsly> DocScrutinizer: datacode 20080725
Jan 26 15:36:55 <octavsly> DocScrutinizer: time before reset: Tue Jan 26 15:25:03 2010  0.000000 seconds
Jan 26 15:36:55 <octavsly> DocScrutinizer: time after reset: Sat Jan  1 00:04:09 2000  0.000000 seconds
Jan 26 15:44:18 <djp_> what are these files... shr-full-eglibc-ipk--20091119-om-gta02.rootfs.jffs2? are these just older versions of full-om-gta02.jffs2?
Jan 26 15:46:45 <djp_> reason i ask, is because i've used full-om-gta02.jffs2 in the old-images directory and seem to have a pretty old version of shr-unstable now
Jan 26 15:52:01 <Heinervdm> full-om-gta02.jffs2 is just a link to the latest image in that directory
Jan 26 15:52:50 <Heinervdm> djp_: in my opinon one should download only the proper named images, then you will always know the exact version
Jan 26 15:54:38 <djp_> Heinervdm: thanks... i need an older image as unfortunately the latest one has issues...
Jan 26 15:55:21 <djp_> Heinervdm: i just didn't know whether the -eglibc-ipk-... files were older versions or not...
Jan 26 16:11:14 <DocScrutinizer> please everybody with a FR: can you do the following test: check hw clock settings with command "hwclock" in terminal. (make sure it's not like 01.01.1970 or sth, a reasonable time would be fine). Then power down device and remove battery for 5 minutes. Reinsert battery, boot up to a state without internet connectivity and without using GPS, without registering to GSM (remove SIM if no PIN set) and check again with "hwclock". Then report 
Jan 26 16:11:16 <DocScrutinizer> here if time is roundabout the same it was before battery removal, or if it's been reset by that procedure. while you remove your bat, you have 5 minutes to copy the datecode under the battery. Please post this datecode together with your result of "time reset" / "time kept correct".  Thanks a lot. This will help us building better devices (if we ever get to do such enterprise)
Jan 26 16:36:25 <jl_gene> DocScrutinizer: 20080621 time reset
Jan 26 16:39:06 <DocScrutinizer> jl_gene: thanks
Jan 26 16:39:58 <lindi-> topic is so long that it gets truncated here
Jan 26 16:42:03 <DocScrutinizer> lindi-: oops
Jan 26 16:42:13 <DocScrutinizer> which client?
Jan 26 16:42:17 <lindi-> irssi
Jan 26 16:42:32 <DocScrutinizer> :-/
Jan 26 16:42:33 <lindi-> i'm betting its the server that truncates it though
Jan 26 16:42:41 <DocScrutinizer> nope
Jan 26 16:42:49 <DocScrutinizer> everything fine here
Jan 26 16:43:23 <DocScrutinizer> so if tthat's not *your* server truncating it...
Jan 26 16:43:53 <lindi-> DocScrutinizer: can you change it once so that tcpdump can see it?
Jan 26 16:44:03 <DocScrutinizer> sure
Jan 26 16:44:46 <lindi-> hmm, now away, will check the dump later
Jan 26 16:45:18 <DocScrutinizer> ok now it's truncated here as well, after "tp://build.shr-project.org/shr-testing/images/om-gta02/ | time lost:10 kept:3 (#13:jl_gene;#12:octavsly) E“
Jan 26 16:46:03 <DocScrutinizer> lindi-: where is your truncation cutting in?
Jan 26 16:46:50 <DocScrutinizer> seems I remember I actually seen different topic maxlen on the different servers
Jan 26 16:53:01 <Heinervdm> DocScrutinizer: for me it's truncated there:  | time lost:10 kept:3 (#13:jl_gene;#12:oct
Jan 26 16:54:05 <DocScrutinizer> oh well, seems I seen that before. Freenode bug. just never mind
Jan 26 16:54:55 <DocScrutinizer> though unconfirmed - for the bug
Jan 26 16:56:33 * DocScrutinizer wonders if the 8chars truncation diff and the 8 "|" pipechars in topic are mere incidence
Jan 26 16:57:10 <SpeedEvil> the /topic #foo is counted in the 512 chars IIRC
Jan 26 16:57:23 <SpeedEvil> However it's done
Jan 26 16:59:04 <DocScrutinizer> well, truncation or not - could someone please take over updating the topic on reports coming in? Need some off time
Jan 26 18:59:16 <DocScrutinizer> Weiss: ping
Jan 26 19:18:07 <DocScrutinizer> please everybody with a FR: can you do the following test: check hw clock settings with command "hwclock" in terminal. (make sure it's not like 01.01.1970 or sth, a reasonable time would be fine). Then power down device and remove battery for 5 minutes. Reinsert battery, boot up to a state without internet connectivity and without using GPS, without registering to GSM (remove SIM if no PIN set) and check again with "hwclock". Then report 
Jan 26 19:18:09 <DocScrutinizer> here if time is roundabout the same it was before battery removal, or if it's been reset by that procedure. while you remove your bat, you have 5 minutes to copy the datecode under the battery. Please post this datecode together with your result of "time reset" / "time kept correct".  Thanks a lot. This will help us building better devices (if we ever get to do such enterprise)
Jan 26 19:21:18 <ndnihil> what happens after the 5 minutes?
Jan 26 19:21:34 <SpeedEvil> It explodes.
Jan 26 19:22:56 <ndnihil> I was afraid of that
Jan 26 19:34:24 <ThibG> it didn't explode, is it fine, still?
Jan 26 19:50:44 <ThibG> DocScrutinizer, Date Code: 20090317 ; time... perfectly correct? something must have been wrong
Jan 26 19:52:48 <wer-ist-roger> hej everyone
Jan 26 19:53:37 <wer-ist-roger> does anybody know hot to connect the latest qtmoko with a SIP-Server. I configured the client but it just won't register
Jan 26 20:17:09 <Heinervdm> DocScrutinizer: 20081016: time reset
Jan 26 20:20:58 <dos1> ThibG: looks like your Freerunner is just too young :P
Jan 26 20:21:33 <ThibG> when I say "perfectly correct", I mean, it's perfectly correct, it hasn't stopped when I've removed the battery
Jan 26 20:23:02 <dos1> ThibG: dunno exactly how it's done in FR, but some devices just have backup battery to keep clock running
Jan 26 21:09:59 <samgee> DocScrutinizer, date code 20080821, time reset (to 2000-01-01)
Jan 26 21:38:13 * tim_abell is opkg upgrading shr-t...
Jan 26 22:05:27 <uzi18> hi all
Jan 26 22:05:48 <uzi18> anyone know where to find c1767 on FR ?
Jan 26 22:06:07 <uzi18> need to know also if it is the same dimmensions as buzzfix
Jan 26 23:10:32 <PaulFer``> uzi18: there's a BOM
Jan 26 23:11:00 <PaulFer``> uzi18: fyi "size C" is ok for the buzzfix
Jan 26 23:12:19 <uzi18> thx
Jan 26 23:12:20 <PaulFer``> uzi18: and also there's a searchable version of pcb layout, courtesy lindi-.
Jan 26 23:12:35 <uzi18> i want to mod A5 -> A6 in this case
Jan 26 23:12:37 <PaulFer``> uzi18: you'll find everything at http://people.openmoko.org/joerg/schematics/GTA02/
Jan 26 23:12:50 <uzi18> thx
Jan 26 23:13:13 <DocScrutinizer> yoh
Jan 26 23:13:38 <PaulFer``> uzi18: one guy's already did a5->a6 mod but i do not remember who. I remember there's not quite much space for the cap inside, probably he used some lower capacity 1206 or something, not the same as for the buzzfix, but i'm not sure.
Jan 26 23:13:43 <uzi18> PaulFer``: and what kind of parts needed to mod gsm to dont eat current/
Jan 26 23:14:11 <DocScrutinizer> #1024 fix
Jan 26 23:14:19 <uzi18> yes
Jan 26 23:14:25 <DocScrutinizer> it's on wiki / ml
Jan 26 23:14:46 <PaulFer``> uzi18: any decent ceramic 0805 capacitor 22uF 6V iirc
Jan 26 23:14:59 <DocScrutinizer> yap
Jan 26 23:15:10 <uzi18> and buzzfix is 100u ?
Jan 26 23:15:29 <PaulFer``> uzi18: 100u is ok for a buzzfix.
Jan 26 23:15:59 <uzi18> nice to hear :) maybe today will order some parts from farnell
Jan 26 23:16:36 <PaulFer``> uzi18: check the space inside, where you plan to add the Vsupply a5->a6 cap.
Jan 26 23:16:49 <uzi18> PaulFer``: any other fixes i could do on my a5 ?
Jan 26 23:16:57 <PaulFer``> uzi18: the bassfix
Jan 26 23:17:02 <uzi18> hmm
Jan 26 23:17:10 <PaulFer``> uzi18: i did it on 4 devices so far
Jan 26 23:17:23 <uzi18> PaulFer``: and need to remove minijack  ?
Jan 26 23:17:51 <PaulFer``> uzi18: no
Jan 26 23:18:22 <PaulFer``> uzi18: GTA02_bass_fix
Jan 26 23:18:24 <uzi18> have found couple of fixes on same problem but dont remember now
Jan 26 23:18:26 <PaulFer``> on the wiki
Jan 26 23:18:40 <uzi18> ok will check
Jan 26 23:18:50 <DocScrutinizer> my firstborn ;-)
Jan 26 23:18:53 <PaulFer``> uzi18: hm, one more thing.
Jan 26 23:18:58 <uzi18> ?
Jan 26 23:19:32 <PaulFer``> uzi18: check that r3004 and r3005 are actually 0R and not 1uF capacitors. If those are caps -- short them.
Jan 26 23:19:40 <DocScrutinizer> short the 0R capacitors
Jan 26 23:20:21 <DocScrutinizer> the idiot bastard son 
Jan 26 23:20:29 <DocScrutinizer> (FZ)
Jan 26 23:21:53 <Psi> 0R capacitors?
Jan 26 23:21:58 <uzi18> ;)
Jan 26 23:22:10 <DocScrutinizer> SIC!
Jan 26 23:22:11 <uzi18> PaulFer``: this was some filter?
Jan 26 23:22:32 <DocScrutinizer> this was brain cancer
Jan 26 23:22:34 <PaulFer``> uzi18: this was some stupidity, just a burst of insanity
Jan 26 23:24:02 <PaulFer``> uzi18: btw, if you're really cool you should consider fixing buzz for the wired headset. This is nothing anybody done before.
Jan 26 23:24:32 <PaulFer``> uzi18: R4408 should be split into two series R's and a buzzfix 100uF connected to the middle point.
Jan 26 23:25:02 * uzi18 looking into shecmes
Jan 26 23:25:23 <uzi18> schemes
Jan 26 23:25:25 <uzi18> :P
Jan 26 23:25:27 <PaulFer``> uzi18: most probably to do that you'll need to route 2 wires outside the can, but you need to properly shield them and probably add ferrite bead.
Jan 26 23:25:33 <PaulFer``> anyway, gotta sleep.
Jan 26 23:25:44 <uzi18> ok thank you !
Jan 26 23:25:47 <uzi18> good night
Jan 26 23:25:52 <PaulFer``> I'm sure DocScrutinizer is able to tell all this and more better than me :)
Jan 26 23:26:01 <PaulFer``> Have a nice evening :)
Jan 26 23:26:14 <uzi18> i'm going asleep to
Jan 26 23:26:16 <uzi18> too
Jan 26 23:26:23 <DocScrutinizer> nightinight PaulFer`` 
Jan 26 23:26:34 <PaulFer``> DocScrutinizer: see you tomorrow Doc :)
Jan 26 23:26:45 <Psi> nite PaulFer
Jan 26 23:27:06 <PaulFer``> Good night, everybody :)
**** ENDING LOGGING AT Wed Jan 27 02:59:57 2010