**** BEGIN LOGGING AT Tue Apr 06 02:59:56 2010 Apr 06 05:32:25 moin Apr 06 08:54:26 hello Apr 06 08:54:44 I'm using SHR-u and I tried to use my BT headset with no luck Apr 06 08:55:06 I used this howto http://wiki.openmoko.org/wiki/SHR_User_Manual#GSM_with_bluetooth_headset Apr 06 08:55:20 first of all emtooth seems broken, so I paired manually Apr 06 08:56:16 additionally I needed to launch blutoothd manually Apr 06 08:56:54 then if I add "bt-headset-*" lines to /etc/freesmartphone/opreferences/conf/phone/default.yaml after restarting frameworkd it either doesn't register to GSM network or does, but when calling or receiving a call, there's no GUI and no phone ring Apr 06 08:57:08 any hints on this? Apr 06 09:03:49 Gabrys: those lines in default.yaml shouldn't affect gsm registration or gui at all. Apr 06 09:04:00 Gabrys: tried to look at the log? No tracebacks there? Apr 06 09:04:32 Gabrys: https://wiki.openmoko.org/wiki/Manually_using_Bluetooth#Once_Again.2C_Bluetooth_Headset_on_Freerunner Apr 06 09:05:27 PaulFertser: I try different "formats" of those lines, using true instead of 1 and similar things Apr 06 09:06:02 PaulFertser: if use exactly those from wiki, GSM is registered but BT is not playing nicely :-( Apr 06 09:06:12 I get sound in phone instead Apr 06 09:06:53 I'll the manual method Apr 06 09:07:05 Gabrys: i've tested (and mostly written) the instructions in "Manually using bluetooth" myself. Apr 06 09:08:23 Gabrys: if you restart the whole phone, do not forget to make sure bluetooth is powered on and bluetoothd is started. Prefarrably before starting frameworkd. Apr 06 09:08:59 PaulFertser: yes I need to manually start bluetooth, and then I restart frameworkd, I have no idea why I miss /etc/init.d/bluetooth script Apr 06 09:13:24 PaulFertser: /usr/share/openmoko/scenarios/ is not a valid dir anymore Apr 06 09:14:58 also the http://dl.getdropbox.com/u/453116/gsmbluetooth.state is 404 Apr 06 09:15:14 but I have (I hope) right file in /usr/share/shr/scenarii/gsmbluetooth.state Apr 06 09:39:53 neither bluez4 nor task-base-bluetooth provide /etc/init.d/bluetooth file Apr 06 09:39:56 where to get it? Apr 06 09:55:46 PaulFertser: here's my frameworkd.log output when receiving a call: http://pastebin.com/8W9qkvXS Apr 06 09:56:05 and I have bluetooth connected, paired and everything :( Apr 06 09:58:11 PaulFertser: so it seems BTHeadsetIsConnected() returns false Apr 06 12:18:35 PaulFertser, Gabrys: the guide is out of date - bluetooth has changed drasticly - I think fso is now handling it all so the files are no longer neccessary Apr 06 12:19:00 BillK: I hoped so, but it doesn't work either way Apr 06 12:19:05 BillK: what exactly do you mean? Apr 06 12:19:54 e.g., reserving bluetooth via fsoraw is all thats neccesary to use bt these days - no init scripts Apr 06 12:20:14 BillK: so what's the proper way to use BT headset? Apr 06 12:20:33 BillK: are you talking about "SHR manual"? I'm concerned only about the "manual way" described on the other page. Apr 06 12:22:16 http://pastebin.com/Q5d2VkP5 - script to use mplayer to play music to a motorola s9 hbt headset Apr 06 12:22:52 I realise gsm is different, but the changes probably mean that the old approach is no longer valid Apr 06 12:24:37 I care about using bt with gsm Apr 06 12:26:37 using with mplayer and co is probably much easier, as can be configured in alsa/pulseaudio quite easily Apr 06 12:28:09 also the guide mentions ophonekitd - thats not even running on my phone - probably not even used any more. Apr 06 12:28:16 yes Apr 06 17:37:10 hi Apr 06 17:45:34 do you have any more news on bluetooth headsets? Apr 06 17:50:09 Gabrys: I think that radekp use his bluetooth headsets with qtmoko Apr 06 17:50:42 rafa: bt headset as a gsm receiver doesn't work in qtmoko Apr 06 17:51:01 and radekp suggested to first try to configure it in SHR, so we could "port" it to qtmoko somehow Apr 06 17:51:39 probably using bt as normal audio output (not gsm) is much easier and may work on qtmoko as well ;-) Apr 06 17:53:23 Gabrys: I have no idea about bluetooth headsets as gsm receiver. I thought that bluetooth headsets were for just audio Apr 06 17:53:37 well I mean for audio Apr 06 17:53:45 so I guess that radekp use it for audio only Apr 06 17:53:46 but for placing and receiving calls ;-) Apr 06 17:53:59 not as a GSM modem ;-) Apr 06 17:55:40 Gabrys: is not it possible just to have auto answer feature? I mean, if you do not want to answer the call you can perhaps press mute? Apr 06 17:55:43 rafa: and technically it is possible as described for "some" version of some distribution for FR here: http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#Once_Again.2C_Bluetooth_Headset_on_Freerunner Apr 06 17:56:13 rafa: I don't know, I want audio first :-) Apr 06 17:56:35 yeah, step by step ;) Apr 06 17:56:47 shit, it's so easy on, say, Nokia Apr 06 17:57:03 I want BT headset to f.... work on FR :D Apr 06 17:58:05 so frustrating Apr 06 17:58:20 if I have a bunch of commands to run in order to make it work Apr 06 17:58:27 I could do a kind of launcher Apr 06 17:58:30 or something Apr 06 17:58:44 but I can't get it working in any way Apr 06 17:58:55 even trying manual way Apr 06 18:03:04 the worst thing I don't know why it /should/ work Apr 06 18:03:09 s/why/how/ Apr 06 18:03:09 Gabrys meant: the worst thing I don't know how it /should/ work Apr 06 18:16:46 Gabrys: probably something was changed an FSO and support was broken. Apr 06 18:17:11 Gabrys: if you want to know for sure, well, read the log first, if it doesn't help, read the source, add debugging statements etc... Apr 06 18:17:22 I guess so, I want every possible hint :-) Apr 06 18:17:25 to get started Apr 06 18:17:43 so far I try to dig in Python sources of framework Apr 06 18:18:00 Gabrys: i'm sorry but i have no better advice. The problem is that end-users never really were interested. They were talking about how fso lacks the feature, but after it was actually added it received very little testing. Apr 06 18:18:06 So the developers got demotivated. Apr 06 18:18:29 The guy who actually implemented the feature never received a single patch concerning it. Apr 06 18:18:40 but do we have any docs Apr 06 18:18:44 on how it actually works Apr 06 18:18:52 Gabrys: i can explain the idea Apr 06 18:19:10 PaulFertser: I'd be grateful Apr 06 18:19:18 Gabrys: the high-level idea is that to get gsm sound on your BT headset the following method is used: Apr 06 18:19:51 Gabrys: gsm call is established the usual way, the GSM modem inputs/outputs sound via analog lines to the wolfson codec, that's the usual thing. Apr 06 18:21:47 PaulFertser: and how it is routed to BT, I guess it never really goes into kernel or bluez Apr 06 18:21:48 Gabrys: to actually use bluetooth: 1. bluetoothd should be given special command to "turn on and activate the headset" 2. the wolfson codec should be configured to route audio to the second audio interface (that is connected directly to bluetooth chip). 3 the wolfson codec should receive proper parameters for the second audio interface Apr 06 18:22:56 2. is taken care by loading the state file (and unfortunately the trick mentioned on the wiki is still needed, it's a kernel bug) 3. is taken care by FSO that uses some alsa API to set 8000 mono for hw:0.1 device (or something like that) Apr 06 18:23:48 Gabrys: this method of using bluetooth headsets is called "SCO over PCM" because it's SCO frames flowing to/from headset and it's "PCM" interface of the bluetooth chip directly connected to the wolfson codec. Apr 06 18:24:11 hmm Apr 06 18:24:37 one quick question, can we get GSM audio in/out routed to alsa/pulseaudio/whatever-in-software Apr 06 18:24:55 like here http://www.opkg.org/package_200.html Apr 06 18:24:57 Gabrys: yes, with proper "statefile" Apr 06 18:24:57 in principle at least Apr 06 18:25:14 this way we could simplify the magic a bit Apr 06 18:25:22 Gabrys: but later routing it to BT is tricky :) Apr 06 18:25:30 to route the audio to ALSA so we can hear it Apr 06 18:25:32 easy to debug Apr 06 18:25:46 and then from ALSA to BT, which is quite well documented Apr 06 18:25:54 Gabrys: you want to get bi-directional operation, then it means you want SCO, "SCO over HCI". Apr 06 18:26:13 Gabrys: with that you get a surprise, you need to modify EEPROM key in bluetooth chip to activate SCO over HCI Apr 06 18:26:44 and why can't we use ALSA in between? Apr 06 18:27:08 Gabrys: you can, but to actually use SCO over HCI you need to tweak that EEPROM setting. Apr 06 18:27:16 hm Apr 06 18:27:32 Gabrys: i did that (only tried playing an mp3 over SCO) Apr 06 18:27:44 aaah, I see Apr 06 18:27:50 SCO over PCM is "easy" Apr 06 18:28:03 Exactly. You just do one bluetoothd dbus call to activate it. Apr 06 18:28:03 but SCO over HCI (means ALSA -> BT) is "hard" Apr 06 18:28:22 and how about the GSM -> ALSA part? Apr 06 18:28:35 is it quite easy? Apr 06 18:28:58 Gabrys: if you get the right state file. I remember folks had difficulties crafting one, not sure why. Apr 06 18:29:10 Gabrys: have you seen "Neo1973_Audio_Subsystem" wiki page? Apr 06 18:29:13 and what's exactly the state file? Apr 06 18:29:47 and the audio subsystem is the same between gta01 and gta02? Apr 06 18:30:03 Gabrys: that page is mostly gta02-only anyway :) Apr 06 18:30:16 Gabrys: the wolfson chip is the same. The kernel driver is a bit different. Apr 06 18:30:26 Gabrys: anyway, the "pretty" diagram is for gta02. Apr 06 18:31:29 I regret we don't have everything going through sw somehow Apr 06 18:31:30 ;-) Apr 06 18:31:34 Heh Apr 06 18:31:47 it may not be simpler at first, but it would be easier to debug and test :-) Apr 06 18:31:56 as you can always easily dump things from sw Apr 06 18:32:11 Gabrys: if you're really serious about doing SCO over HCI, i'll share the details, they're not secret, but not really documented in a sane way anywhere either. Apr 06 18:32:24 Gabrys: but first of all, try SCO over PCM Apr 06 18:32:48 PaulFertser: ok, I just tried "everything" documented to get it working Apr 06 18:32:56 Gabrys: try to understand why the BluetoothIsConnected (or something) is failing. Apr 06 18:33:11 yeah, I wanted to test this as well :-) Apr 06 18:34:15 Gabrys: in fact if you know python at least somewhat (i've never learned it but i can understand fso sources) it would be nice if you made bluetooth work. Apr 06 18:34:30 well, I'm a python coder, kind of ;-) Apr 06 18:35:05 the code lacks some in-code documentation though ;-) Apr 06 18:35:47 Gabrys: come on, even if i can understand it ;) Apr 06 18:36:49 what about this note: Apr 06 18:36:50 using Bluetooth headset with GSM NOTE none of this works with GTA02. Neo mode has disappeared, and none of the state files are GTA02 compatible. Apr 06 18:37:07 Gabrys: some old note from whereever, ignore Apr 06 18:37:12 ok Apr 06 18:37:19 Gabrys: there's no "modes" at all in gta02 driver. Apr 06 18:39:18 my understanding of state files right is now they are states of ALSA settings Apr 06 18:39:31 and ALSA can set internal switches of codec Apr 06 18:39:37 that controls routing of sound Apr 06 18:39:55 Exactly Apr 06 18:40:04 so we can using ALSA switch snd chip to route sound from GSM to BT Apr 06 18:40:44 so in fact, I can set them all with alsamixer instead using state files? Apr 06 18:40:49 Gabrys: my notion is that the statefile is all right. Apr 06 18:40:57 Gabrys: many people tried it and it was ok. Apr 06 18:41:19 Gabrys: of course, alsamixer will work as well. Just do not forget fso likes to load different scenarious every now and then. Apr 06 18:41:29 sure Apr 06 18:41:45 Gabrys: and about the dirty trick (near the end of "manually using" page) needed due to kernel bug. Apr 06 18:42:33 what's the trick? I can't find it Apr 06 18:42:43 the disable_esco? Apr 06 18:42:47 No Apr 06 18:43:09 The next one :))) Apr 06 18:43:20 I see Apr 06 18:43:23 amixer ... Apr 06 18:43:27 amixer sset "Capture Left Mixer" "Analogue Mix Right" amixer sset "Capture Left Mixer" "Analogue Mix Left" Apr 06 18:43:39 how do I load the state file manually? Apr 06 18:44:43 Gabrys: alsactl restore Apr 06 18:45:30 Gabrys: and the bluetoothd call is org.bluez.Headset Play() iirc Apr 06 18:45:38 OK, I'm going to put in a wiki page, what I'm going to test Apr 06 18:45:42 and how Apr 06 18:46:25 I really think there's some misunderstanding between fso and bluetoothd right now. FSO should "sense" automatically that bluetoothd is up and headset is there, there's fso code for that. Apr 06 18:47:48 well, the problem is bluetoothd is not up Apr 06 18:47:54 because is now handled differently Apr 06 18:47:59 it's not a deamon anymore Apr 06 18:49:27 Gabrys: can't be. It was a daemon and it is still a daemon. Apr 06 18:51:11 what I want to do is omit frameworkd completely Apr 06 18:51:13 just for test Apr 06 18:53:31 Gabrys: how will you initiate gsm call? With socat+AT commands? Apr 06 18:53:39 I would call :-) Apr 06 18:53:47 for this frameworkd work :D Apr 06 18:54:09 I'll let frameworkd set statefile and then load my own Apr 06 18:55:13 Gabrys: have you forgotten about part 3? Apr 06 18:55:24 Gabrys: to set bluetooth IIS to 8000 rate etc. Apr 06 18:55:32 Gabrys: check out the relevant code in FSO. Apr 06 18:55:36 right Apr 06 18:55:45 what happens if we don't set this right? Apr 06 18:56:04 do we have no sound or some "wrong" sound Apr 06 18:56:05 No idea, probably they're already sane by default, probably not. Apr 06 18:56:29 I do not remember details of PCM interface. Probably you'll get "wrong" sound. Apr 06 18:56:42 this would work :-) Apr 06 18:56:52 I mean, this says something Apr 06 18:58:06 PaulFertser: please take a look at this: http://wiki.openmoko.org/wiki/User_talk:Gabrys Apr 06 18:59:08 Gabrys: bluetoothd dbus call is missing Apr 06 18:59:42 what does it do? Apr 06 19:00:06 Gabrys: "activates" bluetooth chip and the headset so they start exchange SCO frames. Apr 06 19:00:21 ah, this may be really needed :-) Apr 06 19:00:32 and I forgot about mentioning /etc/bluetooth/audio.conf config Apr 06 19:00:43 Gabrys: code to configure rate etc is really trivial Apr 06 19:01:16 Gabrys: the setting in audio.conf will affect only ability to issue that Play() dbus call. bluetoothd will stubbornly refuse to obey until its enabled. Apr 06 19:02:40 ok, could you point me to the rate setting code? :> Apr 06 19:03:43 Gabrys: http://git.freesmartphone.org/?p=framework.git;a=blob;f=framework/subsystems/ophoned/headset.py;h=80f5517b426026c934ea17a9c95a4e3502a40d25;hb=HEAD Apr 06 19:03:47 Gabrys: startpcm Apr 06 19:03:50 blablabla Apr 06 19:03:53 grep is your friend Apr 06 19:03:56 :) Apr 06 19:05:28 but I think it's for ALSA<->BT thing Apr 06 19:05:38 I mean if you later don't use the device IN CODE Apr 06 19:05:48 it would have no result I guess Apr 06 19:06:02 PaulFertser: or am I wrong Apr 06 19:06:23 Gabrys: alsa is used to configure bluetooth IIS even despite it's not connected to cpu. Apr 06 19:06:36 ok Apr 06 19:07:56 Gabrys: have you seen this: http://git.freesmartphone.org/?p=framework.git;a=history;f=framework/subsystems/ophoned/headset.py;h=80f5517b426026c934ea17a9c95a4e3502a40d25;hb=HEAD Apr 06 19:07:56 setting the rate is before the dbus call or after? Apr 06 19:08:02 Gabrys: doesn't matter Apr 06 19:08:37 Gabrys: i guess it works for Felix, probably you want to contact him Apr 06 19:09:09 Gabrys: or you're not running recent enough code. What's the date of your fso version? Apr 06 19:09:18 FSO I don't know Apr 06 19:09:25 I have shr-u from yesterday Apr 06 19:09:28 or even today Apr 06 19:11:17 how do I verify the settings for hw0:1 are oK? Apr 06 19:11:46 Gabrys: hm, no idea. I wouldn't bother. Just reapply with a simply python snippet if you're not sure. Apr 06 19:12:28 PaulFertser: OK, please take a look now Apr 06 19:13:42 Gabrys: looks good Apr 06 19:14:08 PaulFertser: you probably meant alsactl restore < statefile Apr 06 19:14:28 Gabrys: i'm sure you can figure out the correct syntax Apr 06 19:14:36 Gabrys: iirc it didn't require redirection Apr 06 19:15:22 ok, so I need now proper state file and dbus call Apr 06 19:15:26 and probably I can test :-) Apr 06 19:15:48 Gabrys: for dbus calls you'll find plenty of info on the same bluetooth page, it says enough about bluez4 api Apr 06 19:16:02 And i'm sure shr has the proper state file preinstalled. Apr 06 19:16:16 I guess so :-) Apr 06 19:17:43 org.bluez.audio.Headset Apr 06 19:18:25 Do not neglect the dbus introspection ;) Apr 06 19:19:20 I guess this would work Apr 06 19:19:20 mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_00_13_17_78_7B_A3 org.bluez.Headset.Play Apr 06 19:19:22 ;) Apr 06 19:21:06 Gabrys: omg, where did you read that "pidof bluetoothd"? Apr 06 19:21:17 Gabrys: i thought i corrected it everywhere, as it no longer works Apr 06 19:21:20 what's wrong with this? :> Apr 06 19:21:28 it used to work for Connecting though :D Apr 06 19:21:51 bluetooth guys changed their minds and this hack no longer applies Apr 06 19:21:56 Where did you read that? Apr 06 19:22:11 http://wiki.openmoko.org/wiki/SHR_User_Manual#Re-Connecting_the_headset Apr 06 19:22:20 Fuck Apr 06 19:22:29 I've told the guys to not copy-paste stuff! Apr 06 19:22:33 :( Apr 06 19:23:01 Gabrys: it would probably be nice if you removed all the stuff copied from the "Manually using bluetooth" page and linked it instead. Apr 06 19:23:33 on the SHR_User_Manual or on my page? Apr 06 19:23:41 Gabrys: on SHR_User_Manual Apr 06 19:23:49 I do not give a shit about your page ;) Apr 06 19:24:02 nice :D Apr 06 19:26:29 I don't know why Apr 06 19:26:39 but the "new" way works the same as the pidof way Apr 06 19:27:08 Gabrys: i'm sure pidof way broke starting from some bluez revision. Apr 06 19:27:49 PaulFertser: how does one connect/reconnect now? Apr 06 19:28:08 this is the only bit left in shr manual Apr 06 19:28:10 vanous123: $BTADAPTER Apr 06 19:28:25 vanous123: ah, so you removed most of the copied stuff. Thanks :D Apr 06 19:28:34 i did already before Apr 06 19:33:30 vanous123: please do not think i'm "dissing" your work on the manual Apr 06 19:34:46 PaulFertser: no, i understand Apr 06 19:35:02 this is why i removed all that Apr 06 19:35:17 i had to edit a lot of other peoples additions Apr 06 19:35:27 removed all related to theid desktops Apr 06 19:35:34 and leave fr related stuff only Apr 06 19:35:47 while the wiki keeps the relations... Apr 06 19:36:33 PaulFertser: for pairing, i am recommending emtooth in the manual Apr 06 19:36:51 vanous123: emtooth is broken now Apr 06 19:37:18 Gabrys: is it? Apr 06 19:37:27 yeap, I tested yesterday Apr 06 19:37:36 Gabrys: changes in bluez? Apr 06 19:38:10 it discovers no devices, prints lots or error (I guess) messages to stdout/stderr and segfaults when clicking on Stop discovery Apr 06 19:39:34 testing or unstable? Apr 06 19:39:36 unstable Apr 06 19:41:37 ok Apr 06 19:43:04 I upgraded testing to unstable because of GUI bug of not being able to move volume sliders left ;-) Apr 06 19:43:11 Gabrys: seems like one has to run bluetoothd manually Apr 06 19:43:18 then it works Apr 06 19:43:48 i have a feeling i read something about it Apr 06 19:43:50 I tried that, but still no luck, but maybe I miss-did something Apr 06 19:44:16 bluetoothd missing init script, not sure if by intention or a mistake Apr 06 19:45:25 I also noted that Apr 06 19:46:40 (11:39:53) Gabrys: neither bluez4 nor task-base-bluetooth provide /etc/init.d/bluetooth file Apr 06 19:46:41 ;-) Apr 06 19:49:53 PaulFertser: could I ask to make a final look on testing procedure at http://wiki.openmoko.org/wiki/User_talk:Gabrys Apr 06 19:57:11 I get some noise! Apr 06 19:57:24 but nothing more :( Apr 06 19:57:35 additionally frameworkd mutes sound Apr 06 20:11:34 maybe it's even ok Apr 06 20:11:47 'cause it mutes internal speaker Apr 06 20:16:19 Gabrys: noise but no signal? Apr 06 20:16:27 Gabrys: either that means wrong wolfson routing Apr 06 20:16:43 when I set up bt I hear 4 (?) clicks Apr 06 20:16:43 Gabrys: or your headset is the same as the one i tested :| Apr 06 20:16:56 and then noise Apr 06 20:17:01 ok, I'll check another one Apr 06 20:17:26 Gabrys: i'm not sure hciconfig will be able to do anything before bluetoothd is started, so change the order Apr 06 20:17:41 ah, ok Apr 06 20:17:44 it seems to work Apr 06 20:17:49 though Apr 06 20:18:17 Gabrys: because it's up by default :) Apr 06 20:18:23 Gabrys: are you sure your alsactl command is ok? Apr 06 20:18:57 Gabrys: it should be "alsactl -f restore Apr 06 20:20:33 ok, fixing this Apr 06 20:20:54 interesting thing is Apr 06 20:21:01 I have now two connections Apr 06 20:21:05 one SCO and one ACL Apr 06 20:21:14 root@om-gta02 ~ $ hcitool con Apr 06 20:21:14 Connections: Apr 06 20:21:14 < SCO 00:13:17:78:7B:A3 handle 45 state 1 lm SLAVE Apr 06 20:21:14 < ACL 00:13:17:78:7B:A3 handle 42 state 1 lm MASTER Apr 06 20:21:15 That's good Apr 06 20:21:42 Btw, you should hear some "beep" after your issue Play() and yes, SCO connection appears. Apr 06 20:22:32 ha! Apr 06 20:22:44 I hear myself in the middle of the script Apr 06 20:22:52 for about 1/4 of second Apr 06 20:23:03 Heh, interesting Apr 06 20:23:13 probably before python set_pcm.py is run Apr 06 20:23:14 In the middles of what script? Apr 06 20:23:23 I'll check one by one Apr 06 20:23:37 I have alsactl, amixers, python set_pcm and dbus thing Apr 06 20:23:50 so I'll check this commands one by one Apr 06 20:24:06 Gabrys: probably you should keep set_pcm running, as it might set some inappropriate defaults when connection is "closed". Apr 06 20:24:22 hmm Apr 06 20:24:26 ok, I'll check that :-) Apr 06 20:30:02 I got it working now! Apr 06 20:30:06 cool man :D Apr 06 20:30:23 PaulFertser: thanks for your great help in sorting this thing out Apr 06 20:30:38 Gabrys: :))) Apr 06 20:32:20 so basically I'm moving python thing to the end Apr 06 20:32:28 and make sleep(999) at the end of it Apr 06 20:32:45 so it breaks only after Ctrl-C Apr 06 20:32:48 heh droogies Apr 06 20:37:59 Gabrys: now the only thing left is to find why FSO doesn't do it on itself ;) Apr 06 20:38:04 yeap Apr 06 20:38:15 and qtmoko too please :) Apr 06 20:38:18 Gabrys: i guess if you sum up all the steps they might be beneficial to some tinkerers. Apr 06 20:38:51 radek_: i think you can compare now known to work Gabrys's instructions to what qtmoko does ;) Apr 06 20:39:50 PaulFertser: yes, i found this discussion really usefull - got it copy pasted in my mail :) Apr 06 20:47:39 ok guys, thank you for your help Apr 06 20:47:52 I've cleaned the page Apr 06 20:48:05 http://wiki.openmoko.org/wiki/User_talk:Gabrys it should more useful now Apr 06 20:48:15 feel free to move it to more proper place Apr 06 20:48:32 I need to get some sleep, I'll work on this tomorrow :-) Apr 06 20:50:53 Gabrys: thanks for your persistence! Apr 06 20:51:30 np, I'm solving problem for myself Apr 06 20:51:54 I find sound quality in BT is much better than in internal headset Apr 06 20:52:00 s/headset/handset/ Apr 06 20:52:01 Gabrys meant: I find sound quality in BT is much better than in internal handset Apr 06 20:52:21 including the echo bug Apr 06 20:52:27 ok, see you guys Apr 07 02:44:12 watsup **** ENDING LOGGING AT Wed Apr 07 02:59:57 2010