**** BEGIN LOGGING AT Tue Mar 02 02:59:58 2010
Mar 02 08:45:06 <naquan> hi everyone, I installed shr-testing 20100125 on my SD card and shr-today create a double lock: I must slide the button twice to unlock my phone. I tried reinstalling shr-today but it's still there, please help.
Mar 02 08:51:50 <JaMa> naquan: remove shr-today
Mar 02 08:52:29 <JaMa> naquan: afaik that lock screen is provided by phoneuid, so if you installed shr-today too, then you have 2 lock screens.
Mar 02 08:56:30 <naquan> JaMa: thank you
Mar 02 09:18:00 <naquan> JaMa: I removed Xsession.d/80phoneui and install shr-today, it works fine. The default phoneui lock screen has error on GSM network status.
Mar 02 09:19:06 <JaMa> naquan: really strange solution indeed.. you did it exactly the oposite way I suggested..
Mar 02 09:21:11 <PaulFertser> LOL
Mar 02 09:21:24 <naquan> JaMa: :)
Mar 02 09:25:01 <DocScrutinizer> moin paul
Mar 02 09:27:24 <PaulFertser> DocScrutinizer: morning Joerg :)
Mar 02 10:02:01 <alabd> hello ,  how to know if fr is paired with another device or not ?
Mar 02 10:45:49 <Psi> does gta02 have the same bug as gta01 where if you suspend the phone while on charge it eventually runs totally flat
Mar 02 10:46:51 <Psi> in shr, i should say
Mar 02 10:47:08 <PaulFertser> Psi: no
Mar 02 10:47:17 <Psi> ok
Mar 02 10:47:29 <PaulFertser> Psi: do you have an idea how that might happen?
Mar 02 10:48:07 <Psi> it seems to last longer than normal, so i think it is charging, just not enough to keep the bat topped up
Mar 02 10:48:11 <PaulFertser> Psi: i see this scenario: you suspend the phone, it charges the battery until full, then stops charging, the battery starts discharging slowly but steadily until flat. But it should take a lot of time since only gsm is powered directly by the bettery.
Mar 02 10:49:01 <Psi> my phone bat was at around 60% (dont know exactly, just from what the icon looked like) after around 24h suspended on charge
Mar 02 10:49:13 <Psi> it was fully charged at the start
Mar 02 10:49:49 <Psi> phone would never last 24hours suspended if it wasnt on charge
Mar 02 10:49:58 <Psi> would probably last 12 or so
Mar 02 10:50:16 <Psi> although, ive not done a test to check that for a while
Mar 02 10:50:58 <Psi> does the phone need to wake up to turn charge back on? or should it happen automatically
Mar 02 10:51:23 <Psi> it may have something to do with what i said a few months back, that gta01 never seems to stop charging, charge icon is always on
Mar 02 10:51:39 <Psi> i remember you thought that was wrong, and it should dissapear once the bat was full
Mar 02 10:52:58 <PaulFertser> Psi: hm
Mar 02 10:53:34 <PaulFertser> DocScrutinizer: do you have an idea? I thought 500mA is pretty much enough to run gta01 from usb. What's weird here is that it flats the battery even suspended...
Mar 02 10:54:45 <DocScrutinizer> sounds weird
Mar 02 10:54:59 <DocScrutinizer> lemme scan backscroll
Mar 02 10:58:10 <valos> alabd: paired with another device ? do you sppeak about bluetooth devices ?
Mar 02 10:58:11 <DocScrutinizer> I think it's a) not really suspended and hogs power, or b) PMU is configured incorrectly
Mar 02 10:58:46 <Psi> ok
Mar 02 10:58:49 <PaulFertser> DocScrutinizer: in my testing suspended gta01 really charged the battery.
Mar 02 10:58:55 <DocScrutinizer> Psi: usually PMU chip should restart charge when battery is some 70% down
Mar 02 10:59:07 <PaulFertser> DocScrutinizer: not the case for pcf50606 i'm afraid.
Mar 02 10:59:07 <Psi> its possible i didnt wait long enough
Mar 02 10:59:21 <DocScrutinizer> PaulFertser: ouch!!
Mar 02 10:59:38 <PaulFertser> DocScrutinizer: yeah, i think i tried hard to find the feature but looks like it's not there.
Mar 02 10:59:40 <Psi> so phone needs to wake up every so often to check?
Mar 02 11:00:49 <Psi> im pondering getting a n900
Mar 02 11:01:03 <Psi> anyone else in here got one?
Mar 02 11:01:06 <PaulFertser> Basically, yes. But in RL you'll rarely leave the phone for so long plugged in continuesly. It should be 120 hours straight to drain the battery with only GSM.
Mar 02 11:01:20 <Psi> true
Mar 02 11:02:01 <DocScrutinizer> yep, your figure of only 12h in suspend doesn't sound correct
Mar 02 11:02:18 <Psi> ok, its been a while since i did that test, ill do another one
Mar 02 11:04:19 <alabd> valos: yeah
Mar 02 11:05:08 <valos> alabd: if you use SHR-unstable, you can use mdbus2 command line utility
Mar 02 11:05:24 <alabd> valos: testing
Mar 02 11:10:26 <valos> alabd_: under shr-testing, there is mickeydbus package
Mar 02 11:10:58 <Psi> is there anywhere in proc i can pickup if there is a call in progress?
Mar 02 11:11:09 <Psi> or /sys or anywhere really
Mar 02 11:12:31 <valos> alabd_: opkg install mickeydbus
Mar 02 11:12:36 <valos> alabd_: mdbus -s org.bluez /org/bluez/1536/hci0  org.bluez.Adapter.ListDevices
Mar 02 11:16:18 <alabd_> valos: wait
Mar 02 11:16:33 <valos> alabd_: I wait
Mar 02 11:20:51 <alabd_> valos: http://pastebin.com/7NtL2WXN
Mar 02 11:21:56 <valos> alabd_: ok, try just :  mdbus -s org.bluez
Mar 02 11:24:52 <alabd_> valos: http://pastebin.com/R2sq5hXy
Mar 02 11:25:22 <valos> alabd_: mdbus -s org.bluez /org/bluez/1478/hci0  org.bluez.Adapter.ListDevices
Mar 02 11:26:08 <valos> alabd_: mdbus -s org.bluez  /org/bluez/1478/hci0/dev_00_1F_E1_C0_FE_12 org.bluez.Device.GetProperties
Mar 02 11:27:21 <alabd_> valos:  what is that command for ?
Mar 02 11:27:49 <valos> alabd_: the last one?
Mar 02 11:28:03 <valos> alabd_: to get device properties ?
Mar 02 11:28:22 <alabd_> how to know if fr is paired with laptop ?
Mar 02 11:29:00 <alabd_> valos: Paired': True,
Mar 02 11:29:00 <alabd_>     'Trusted': False,
Mar 02 11:29:22 <valos> alabd_: in device properties, you will see the laptop name in field name
Mar 02 11:29:57 <alabd_> yes
Mar 02 11:30:02 <alabd_> how to make it trusted
Mar 02 11:30:10 <valos> alabd_: and next look at paired and trusted
Mar 02 11:30:39 <valos> alabd_: you can use simple-agent or emtooth
Mar 02 11:31:14 <valos> alabd_: http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#Pairing_2
Mar 02 11:31:18 <alabd_> emtooth can not make it trusted choice is not accessable
Mar 02 11:31:21 <PaulFertser> I' not 
Mar 02 11:31:27 <PaulFertser> I'm not sure it must be trusted to work.
Mar 02 11:31:58 <valos> alabd_: http://code.google.com/p/emtooth/ but I don't know if it works under shr-testing
Mar 02 11:32:09 <alabd_> am afraid at all what should be done except pairig 
Mar 02 11:32:21 <alabd_> emtooth worked but 
Mar 02 11:32:35 <alabd_> can not make it trusted choice is not accessable
Mar 02 11:34:02 <alabd_> maybe reading wiki should make sense 
Mar 02 11:36:02 <alabd_> is this step required for shr-testing ?
Mar 02 11:36:12 <alabd_> http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#State_file
Mar 02 11:37:26 <alabd_> PaulFertser:  valos it is trusted now with emtooth
Mar 02 11:37:47 <PaulFertser> alabd_: no, you've already has the right statfile.
Mar 02 11:37:57 <alabd_> ok thanks 
Mar 02 11:38:45 <alabd_> how about   Rules file   PaulFertser
Mar 02 11:39:02 <PaulFertser> alabd_: you need to alter that according to the wiki.
Mar 02 11:39:35 <alabd_> ok
Mar 02 11:42:55 <pabs3> is there a way to power off the GSM chip in the FSO configuration file? I don't have a SIM card at the moment so I want it off at all times
Mar 02 11:48:38 <PaulFertser> pabs3: just do not start phoneui or anything that requests GSM.
Mar 02 11:52:12 <pabs3> looks like I should also disable /etc/X11/Xsession.d/80phoneuid
Mar 02 11:56:50 <PaulFertser> pabs3: yes
Mar 02 11:56:54 <PaulFertser> pabs3: that's what i meant :)
Mar 02 11:57:01 <pabs3> killing phoneuid and its wrapper doesn't seem to have helped, turning off GSM in shr-settings and then suspending, shr-settings says GSM is still on after resume
Mar 02 11:58:00 <alabd_> PaulFertser:  after altering according wiki for rules file this occurred http://pastebin.com/apnqis3Q
Mar 02 11:59:01 <PaulFertser> alabd_: you'd better restart after doing all the changes.
Mar 02 11:59:17 <alabd_> PaulFertser: yes restated
Mar 02 12:02:12 <naught101_> $ /usr/bin/tzselect
Mar 02 12:02:14 <naught101_> -sh: /usr/bin/tzselect: not found
Mar 02 12:02:15 <naught101_> wtf?
Mar 02 12:02:25 <naught101_> it's there
Mar 02 12:04:36 <naught101_> ah, because it's got a bash shebang?
Mar 02 12:04:41 <naught101_> instead of sh?
Mar 02 12:05:04 <alabd_> PaulFertser:  but it was ok before editing
Mar 02 12:05:37 <naught101_> yep...
Mar 02 12:07:23 <PaulFertser> alabd_: it's hard to tell why's that...
Mar 02 12:08:27 <alabd_> PaulFertser: is it ok ? http://pastebin.com/7f5m2wdQ 
Mar 02 12:09:23 <PaulFertser> alabd_: looks like
Mar 02 12:13:24 <alabd_> PaulFertser:  but it seems humble done it wrong would you give your /etc/freesmartphone/oevents/rules.yaml
Mar 02 12:13:42 <PaulFertser> alabd_: have you actually tried calling?
Mar 02 12:14:08 <alabd_> PaulFertser: calling
Mar 02 12:14:38 <PaulFertser> alabd_: is BT resource enabled/requested?
Mar 02 12:15:30 <alabd_> PaulFertser:  humble say maybe /etc/freesmartphone/oevents/rules.yaml edited wrongly
Mar 02 12:24:12 <alabd_> /etc/freesmartphone/oevents/rules.yaml  is required where to get it ?
Mar 02 13:08:57 <alabd_> has anyone used PC as BT headset ?
Mar 02 13:15:23 <alabd_> PaulFertser:  after doing mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage \
Mar 02 13:15:23 <alabd_> org.freesmartphone.Usage.SetResourcePolicy Bluetooth enabled
Mar 02 13:15:48 <alabd_> and also backing up rules file to default one 
Mar 02 13:15:54 <alabd_> the same error
Mar 02 13:16:33 <alabd_> http://pastebin.com/apnqis3Q
Mar 02 13:16:51 <alabd_> PaulFertser:  of course with altering wiki also 
Mar 02 13:17:05 <PaulFertser> alabd_: you're doing something wrong. I'm not sure how and what but you're altering rules when in fact you have some problems with bluetooth configuration and the like...
Mar 02 13:17:12 <PaulFertser> alabd_: i've no idea how to help.
Mar 02 13:18:04 <alabd_> am doing the same as here http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#Rules_file PaulFertser
Mar 02 13:18:10 <alabd_> and reboot
Mar 02 13:18:48 <PaulFertser> alabd_: i thought all the recent shr versions already come with proper rules file.
Mar 02 13:19:32 <alabd_> don't they come ?
Mar 02 13:19:47 <alabd_> PaulFertser:  defaul was ok PaulFertser
Mar 02 13:20:08 <PaulFertser> alabd_: so? Have you actually modified the config file to set address of your "headset" like described on the wiki?
Mar 02 13:20:10 <alabd_> after editing as wiki said there is problem
Mar 02 13:21:37 <alabd_> PaulFertser:  in wiki is written You should replace the entire section from Call -> Audio Scenario Handling (Which is shown) to (but not including) while: PowerStatus() with the following:
Mar 02 13:22:03 <alabd_> what does " (but not including) "  mean ?
Mar 02 13:23:13 <DocScrutinizer> alabd_: please don't crosspost to several channels in parallel. Chances are people ignore you, rather than getting better, more, quiqer answers
Mar 02 13:23:38 <alabd_> docscrutinizer are you sure ?
Mar 02 13:25:47 <alabd_> PaulFertser: so humble changed http://tinyurl.com/yjf256d to http://pastebin.com/0mnNC8Ta  is that done truly 
Mar 02 13:26:26 <PaulFertser> alabd_: i've already told you, that most probably the rules file is already ok, no need to change anything.
Mar 02 13:26:39 <PaulFertser> alabd_: please read the wiki section about using headsets in its full, carefully.
Mar 02 13:28:32 <alabd_> am going a head with wiki , wiki has said edit rules file but you say no why ?
Mar 02 13:35:08 <PaulFertser> alabd_: "If you're using SHR unstable, you already has a correct state file and rules.yaml, so you can skip to the pairing section." !!!
Mar 02 13:35:21 <PaulFertser> alabd_: it was written half a year ago!
Mar 02 13:36:36 <alabd_> PaulFertser: so humble copied http://tinyurl.com/yjf256d we should see result
Mar 02 13:42:37 <alabd_> PaulFertser: even with http://tinyurl.com/yjf256d not worked ; the one from git  
Mar 02 13:42:42 <alabd_> gives the same error
Mar 02 13:45:32 <alabd_> (Method "GetProperties" with signature "" on interface "org.bluez.Device" doesn't exist
Mar 02 13:45:33 <alabd_> )
Mar 02 13:46:51 <BlackBishop> you broke it !
Mar 02 13:57:08 <alabd_> mrmoku: do you know where to get  /etc/freesmartphone/oevents/rules.yaml of shr-testing ?
Mar 02 16:35:31 <PBeck> hi
Mar 02 17:04:07 <alabd> good day all ,  where to get  /etc/freesmartphone/oevents/rules.yaml of shr-testing ?
Mar 02 17:14:40 <DocScrutinizer> alabd: please note PaulFertser talked about rules-yaml of UNSTABLE
Mar 02 17:16:17 <DocScrutinizer> btw you seem to ask this question several times today, both channels. And you got a couple of pointers
Mar 02 17:20:00 <alabd> docscrutinizer yes noted , but default file on shr-testing is removed and humble need one 
Mar 02 17:22:16 <DocScrutinizer> alabd: so what's the point in getting a testing yaml rules and then edit them, while unstable yaml rules are ok without editing, like PaulFertser said?
Mar 02 17:23:12 <alabd> docscrutinizer  of course the point is  after changing rules file and using new one there is a problem 
Mar 02 17:23:38 <alabd> http://pastebin.com/apnqis3Q
Mar 02 17:23:47 <DocScrutinizer> well, maybe your problem isn't with rules at all then?
Mar 02 17:24:04 <alabd> it occurred after replacing it
Mar 02 17:24:25 <DocScrutinizer> I seem to remember you said it occured after editing it
Mar 02 17:28:22 <DocScrutinizer> anyway it seems build.shr-project and git.shr-project are down. So I can't help ATM
Mar 02 19:21:19 <radekp> any ideas about the bluetooth hands free? I have it connected and i think the connection is ok. I can use the button on headset to start/stop call and the blue light on headset indicates that something is happening. But i have no sound..
Mar 02 19:22:16 <radekp> i also tried activate the bluetooth.state from command line
Mar 02 19:22:30 <radekp> is there something else what has to be done?
Mar 02 19:22:49 <radekp> i also tried this program http://opensource.wolfsonmicro.com/~gg/bluetooth-pcm/bluetooth_pcm.c
Mar 02 19:23:31 <PaulFertser> radekp: yes
Mar 02 19:23:48 <PaulFertser> radekp: i'm a bit shy to ask that but have you actually read the relevant page on the wiki?
Mar 02 19:24:15 <radekp> yes, but it seems FSO related
Mar 02 19:24:28 <PaulFertser> radekp: unfortunately, just loading the state file is not enough, you also need to tweek a particular knob in a particular way (known bug). And also yes, you need to use something like the program you mention.
Mar 02 19:24:32 <radekp> and the links to http://handheldshell.com/ do not work anymore :(
Mar 02 19:26:03 <PaulFertser> radekp: that particular wiki page has some fso-specific info, yes. But also it mentions the "magic knob".
Mar 02 19:27:26 <radekp> hmm i think i will try it on SHR first
Mar 02 19:28:38 <radekp> PaulFertser: can you point me out to that "magic knob", please :)
Mar 02 19:33:38 <PaulFertser> amixer sset "Capture Left Mixer" "Analogue Mix Right"
Mar 02 19:33:38 <PaulFertser> amixer sset "Capture Left Mixer" "Analogue Mix Left"
Mar 02 19:33:40 <PaulFertser> radekp: ^
Mar 02 19:37:05 <radekp> PaulFertser: thanks, i'll try on fso now
Mar 02 19:37:37 <PaulFertser> radekp: yes, to make sure your headset works in principle
Mar 02 20:17:36 <UndrWater> is there a cache created by opkg?  I had put the navit feed in my opkg, done the update, installed navit...then realized that shr's navit works differently...removed the navit conf, updated again, but opkg is still trying to find the navit from the navit feed...
Mar 02 22:01:10 <radekp> any idea how to add more package feeds to SHR?
Mar 02 22:04:03 <radekp> PaulFertser: well i havent figured A2DP in SHR, i wonder how anyone can make it working, i think i am giving up :(
Mar 02 22:05:44 <PaulFertser> radekp: what?
Mar 02 22:05:56 <PaulFertser> radekp: a2dp in shr is exactly the same as on any GNU/Linux distro,
Mar 02 22:06:03 <PaulFertser> radekp: absolutely no difference
Mar 02 22:06:21 <PaulFertser> radekp: just pair and add bluetooth device to alsa config.
Mar 02 22:06:33 <radekp> i did it
Mar 02 22:06:44 <PaulFertser> radekp: and what was the result when you tried mplayer?
Mar 02 22:06:44 <radekp> but mplayer says: Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_bluetooth.so
Mar 02 22:07:09 <PaulFertser> radekp: shr guys will tell you the package that should contain that.
Mar 02 22:07:28 <PaulFertser> JaMa: ping
Mar 02 22:09:26 <radekp> i found this ticket http://docs.openmoko.org/trac/ticket/1674
Mar 02 22:10:03 <radekp> it should be in bluez-utils-alsa
Mar 02 22:19:25 <radekp> oki, seems i have figured it out
Mar 02 22:19:27 <radekp> opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/libasound-module-bluez_4.35-r1.1_armv4t.ipk
Mar 02 22:19:46 <radekp> but it took me 2 hours...
Mar 02 22:22:16 <PaulFertser> radekp: libasound-module-bluez
Mar 02 22:22:43 <PaulFertser> radekp: hm, i thought this particular package is in shr distro already, you're discouraged to use angstrom repo.
Mar 02 22:23:01 <PaulFertser> radekp: btw, i've found that by simply looking at http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/bluez/bluez4.inc
Mar 02 22:23:07 <PaulFertser> (found package name)
Mar 02 22:23:24 * radekp is too used to debian...
Mar 02 22:24:11 <PaulFertser> radekp: hm, wiki has the info in fact: http://wiki.openmoko.org/wiki/A2DP#1.1_Check_installed_packages_.28Bluez4.29
Mar 02 22:25:16 <radekp> hmm i should read more carefully
Mar 02 23:15:08 <radekp> PaulFertser: now it seems that A2DP is working, but i get no sound again
Mar 02 23:15:23 <radekp> but mplayer seems to be using bluetooth device
Mar 03 00:26:27 <JaMa> PaulFertser: pong
Mar 03 00:28:14 * JaMa off again
Mar 03 01:30:10 <Psi> DocScrutinizer51: wow, you're right, gta01 suspend time has definitly improved, 15h suspended at still at 60%
Mar 03 02:28:45 <brolin_empey> Windows 7 says "USB device not recognized" when I connect my North American GTA02A6.  I get this same message when my FR is running U-Boot from NOR, U-Boot from NAND, or QtMoko v14 from NAND.  What is this a symptom of?
Mar 03 02:29:55 <brolin_empey> It used to work until a few days ago, but something unknown changed and now I cannot get it working again.
Mar 03 02:30:59 <brolin_empey> I have shut down QtMoko, unplugged USB from the FR, removed the battery, reinstalled the battery, and booted again, but the results are the same.
Mar 03 02:33:02 <brolin_empey> I thought it was a hardware problem with the USB connector, but I disassembled my FR to check:  the USB connector looks OK, other than maybe pin 4 (ID).  Is pin 4 on the FR USB connector supposed to contact pin 4 on the USB plug?  It does not appear to contact.
Mar 03 02:33:58 <brolin_empey> "FR USB connector" = USB socket/receptacle.
Mar 03 02:35:26 <brolin_empey> Do I have to use a digital multimeter to check the continuity between the pins in the USB socket and the connection between the USB socket and the PCB?  Or am I (hopefully) missing a software problem?
Mar 03 02:37:37 <brolin_empey> sysfs says the FR is in USB device mode both logically and electrically, but I still get the "USB device not recognized" message on Windows 7.
Mar 03 02:39:07 <brolin_empey> On Ubuntu, Linux detects a new full-speed USB device but does not detect the FR specifically.  lsusb shows no devices connected.
Mar 03 02:39:48 <brolin_empey> What am I missing? :/
**** ENDING LOGGING AT Wed Mar 03 02:59:58 2010