**** BEGIN LOGGING AT Sat May 29 02:59:57 2010 May 29 03:04:58 qtmoko May 29 03:05:21 android May 29 03:05:53 shr if u are a hacker May 29 03:06:42 slackware has even improved May 29 04:09:16 slaxxer: thanks May 29 04:09:38 the first two have properly working sms and phone calls? May 29 05:02:00 does shr no longer use .state files? May 29 05:04:26 undrwater: yes May 29 05:04:54 undrwater: they know use another format in /etc/freesmartphone/... that is directly parseable by some FSO2 part that loads them. May 29 05:16:01 PaulFertser: max audio at the slider is still a bit low for me outside...is it recommended to mess with those settings? -> /etc/freesmartphone/whatever? May 29 05:20:49 undrwater: if you think you fully understand the diagram (with control names) at http://wiki.openmoko.org/wiki/Neo1973_Audio_Subsystem , then yes, feel free to modify the values as you see fit. But beware, quite possibly your device has extra useless caps in the earpiece path, so they might be the main factor limiting the volume. May 29 05:21:32 gotta love useless caps ;) May 29 05:21:32 undrwater: an interesting option would be to use external headphones (but the same gta02-integrated mic) for gsm calls. May 29 05:22:02 actually, the shipped headphones are working quite well for me :) May 29 05:22:09 that was a surprise recently May 29 05:22:21 I shorted several of them, it required some tiny soldering after opening the main can (i needed to do that anyway for the bass fix). May 29 05:22:32 (shorted useless caps i mean) May 29 05:23:32 do you have any intention to re-write the bluetooth headset page? May 29 05:24:22 undrwater: which one? I care about "Manually using Bluetooth" page the most. May 29 05:24:59 that one May 29 05:25:03 undrwater: it'd be nice to have somebody test bluetooth headsets (for gsm) with the current SHR-u, so that the page can be updated with the actual info. May 29 05:25:14 i'd love to! May 29 05:25:33 undrwater: do you have any particular suggestions for that page? May 29 05:25:35 i have 3 i can test May 29 05:25:55 last time i looked at it it wasn't up to date? May 29 05:25:59 let me check again May 29 05:27:14 "you will need a fixed statefile for bluetooth"...but shr not using statefiles? May 29 05:28:37 undrwater: yes, i think this can be removed/amended. But it would be nice to have someone test with shr-u first. May 29 05:29:52 as-is? how to replace the mdbus command? May 29 05:30:30 undrwater: you can use good old mdbus or the new cool mdbus2 the same way. May 29 05:30:52 undrwater: dbus-send would also work May 29 05:31:51 hmmm....i remember trying and getting an error...but i'll do that and post to ML May 29 05:32:40 undrwater: an error where? May 29 05:33:32 after one of the mdbus commands...even with mdbus2 or dbus-send...i don't remember as it was about a month ago May 29 05:34:22 undrwater: hm, strange May 29 05:35:20 maybe...can't be very helpful if you don't know what happened ;) May 29 05:46:17 undrwater: so are you going to try it right atm? May 29 05:47:05 i can't...playing with .32 kernel...screwed things up ;) May 29 05:47:26 if i fix quickly, i'll try May 29 05:47:37 otherwise i'll try later and post results in ML May 29 05:48:36 undrwater: ok, nice plan :) May 29 05:52:36 is anyone who has the ability actually working on any kind of "normal" bt headset functionality? May 29 05:55:43 undrwater: not atm. But i think it works in qtmoko May 29 06:02:20 interesting...not sure about that May 29 06:03:14 if i use a .32 kernel, will that be a problem with anything in those instructions? May 29 06:05:42 PaulFertser: there is no "/usr/share/openmoko/scenarios/" directory May 29 06:05:59 so where would gsmbluetooth.state go? May 29 06:06:43 undrwater: nowhere, as i've already told you shr-u has all the necessary files and stores them in another place. May 29 06:07:35 ahh...okie... May 29 06:20:19 mdbus2 -s org.bluez $BTADAPTER/dev_00_0A_9B_78_14_02 org.bl May 29 06:20:19 uez.Headset.Connect May 29 06:20:19 [ERR]: Unknown object path /dev_00_0A_9B_78_14_02 for org.bluez May 29 06:21:45 PaulFertser: ^ May 29 06:22:45 undrwater: check available pathes with mdbus2's introspection facilities "mdbus2 -s org.bluez" May 29 06:24:11 undrwater: have you really paired the headset beforehand? May 29 06:24:22 yes May 29 06:24:33 simple-agent requested the pin May 29 06:24:59 added address to /etc/freesmartphone/opreferences/conf/phone/default.yaml May 29 06:25:15 Oh May 29 06:25:18 don't know if that makes it "really", though May 29 06:25:22 [ERR]: Unknown object path /dev_00_0A_9B_78_14_02 for org.bluez !!! May 29 06:25:29 undrwater: you forgot to set $BTADAPTER May 29 06:25:42 where would that be done? May 29 06:25:56 i tried hci0/dev_... May 29 06:27:12 [ERR]: The name org.bluez was not provided by any .service files May 29 06:27:19 oops... May 29 06:27:30 was off May 29 06:28:09 /org/bluez/811/hci0/dev_00_0A_9B_78_14_02 May 29 06:28:38 undrwater: the page has that earlier in http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#How_to_use_bluez4_dbus_API May 29 06:31:21 ok...did that...still same message May 29 06:32:04 undrwater: if you set BTADAPTER, the message can't be the same. May 29 06:32:43 mdbus2 -s org.bluez $BTADAPTER/dev_00_0A_9B_78_14_02 org.bluez.Headset.Connect May 29 06:32:43 Unknown option --help' May 29 06:32:43 Run 'mdbus2 --help' to see a full list of available command line options. May 29 06:33:14 undrwater: run the command that sets BTADAPTER part by part to see why it gets you a wrong result. May 29 06:33:26 ok May 29 06:34:37 It used to work for me, not sure what might have changed. May 29 06:34:39 sorry...what are the different parts of that command? May 29 06:35:00 i have a hard time understanding where one ends and the other starts :( May 29 06:35:37 undrwater: dbus-send ... is one part, then it uses a pipe (|) to pass it to tail, then it uses a pipe to pass it to sed. May 29 06:35:40 3 parts overall. May 29 06:37:59 dbus-send --system --dest=org.bluez --print-reply / org.bluez.Manager.DefaultAdapter May 29 06:37:59 method return sender=:1.24 -> dest=:1.32 reply_serial=2 May 29 06:37:59 object path "/org/bluez/811/hci0" May 29 06:38:22 should i pastebin? or is this OK? May 29 06:39:01 undrwater: ok May 29 06:39:31 echo $BTADAPTER May 29 06:39:31 /org/bluez/811/hci0 May 29 06:39:42 looks like it's set, no May 29 06:39:43 ? May 29 06:40:29 undrwater: yes, looks perfectly correct May 29 06:41:42 soooo: mdbus2 org.bluez $BTADAPTER/dev_00_0A_9B_78_14_02 org.bluez.Headset.Connect May 29 06:41:42 [ERR]: Unknown object path /org/bluez/811/hci0/dev_00_0A_9B_78_14_02 for org.bluez May 29 06:42:20 looks different May 29 06:42:21 undrwater: you miss -s May 29 06:42:39 same result May 29 06:42:53 undrwater: then try introspection to see what's there May 29 06:43:24 / May 29 06:43:24 /org May 29 06:43:24 /org/bluez May 29 06:43:24 /org/bluez/811 May 29 06:43:24 /org/bluez/811/any May 29 06:43:25 /org/bluez/811/hci0 May 29 06:43:25 /org/bluez/811/hci0/dev_00_0A_9B_78_14_02 May 29 06:43:26 /org/bluez/test May 29 06:43:50 it's there :P May 29 06:44:18 Damn strange May 29 06:45:01 i have to quit soon...any other ideas? May 29 06:45:22 undrwater: probably there's some tiny difference between invocations, you can try to find it... Or whatever. No idea, sounds too strange. May 29 06:46:03 okay...i'll post to ML with what i've done so far and see if anyone has a clue May 29 06:46:08 thanks! May 29 06:46:09 I.e. you can try manual way: mdbus2 -s org.bluez /org/bluez/811/hci0/dev_00_0A_9B_78_14_02 May 29 06:46:16 ok May 29 06:46:45 unknown object path May 29 06:47:23 dbus-send? May 29 06:48:29 undrwater: yes, you can try that May 29 06:48:57 ok...no error May 29 06:49:04 dbus-send org.bluez org.bluez.811.hci0.dev_00_0A_9B_78_14_02 May 29 06:50:44 how to do the "connect" thing? May 29 06:51:48 undrwater: dbus-send has very different syntax, you need to look it up in the previous sections May 29 06:54:48 dbus-send --system --dest=org.bluez --print-reply $BTADAPTER/dev_00_0A_9B_78_14_02 org.bluez.Headset.Connect May 29 06:54:48 method return sender=:1.24 -> dest=:1.42 reply_serial=2 May 29 06:55:16 undrwater: looks ok May 29 06:55:27 yep...but no sound May 29 06:55:43 undrwater: you might want to check the framework log May 29 06:55:46 etc. May 29 06:56:10 undrwater: i'm sorry but probably debugging this issue requires more involvment/knowledge. Especially given ophoned is still somewhat broken. May 29 06:57:38 Ok...well..thanks for trying with me :) May 29 06:57:40 night! May 29 06:57:41 undrwater: thanks you for trying anyway, that's one step forward, and every step counts :) May 29 06:57:47 undrwater: good night :) May 29 06:59:47 undrwater: i now confirm there's some problem with mdbus2 May 29 06:59:53 And it looks like a regression indeed. May 29 09:19:57 is there a command line (maybe dbus call) to de-/activate the screenlock in shr-u from console? May 29 13:31:13 does the display of the freerunner feel all rubbery or did the earlier owner put some protective foil on it? May 29 13:42:16 quitte: it's a resistive TS, not capacitive May 29 18:17:36 where do i set my provider specific sms central in shr-u? i cant find it in the wiki May 29 19:22:40 if i have problems sending and receiving sms with shr-u what log is the best starting place to look at? at the moment there are quite a bunch of different fso logs at /var/log :) May 29 20:27:44 hi May 29 20:28:02 is mtest in u-boot supposed to have false-positives? May 29 20:38:45 What does mtest do? May 29 20:39:13 write/read different memory patterns May 29 20:39:59 to RAM? May 29 20:40:32 yeah May 29 20:41:11 paying a bit more attention to its output, seems it isn't reliable unless you specify the address range May 29 20:41:36 (it seems to test some read-only zones too) May 29 21:08:06 it seems my external card reader is a pos. how can i get the freerunner to act as a card reader for its internal micro sd card? May 29 21:10:25 oh wrong channel **** ENDING LOGGING AT Sun May 30 02:59:56 2010