Re: qtmoko v26 bluetooth headset
Jim Morris wrote: > > 4. With my preferred device the Motorola T505 handsfree device, it has > trouble connecting on > occasions. If connecting as a handsfree device, the devices buttons do not > accept or hangup a call, > and the incoming number is not detected. But it does seem to work, although > not in a usable way. > If I try to connect as a headset it does not seem to work at all. > After rebooting and unpairing and repairing with the motot505, it did in fact work, the button accepted the incoming call and hangup again when pressed again. I did see the incoming number being sent to the device in hcidump, but the device did not recognize it. When I powered off the bluetooth device and started it up again the bluetooth daemon died, when started again I failed to be able to connect getting authentication errors. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Well I have played with the BT operations on qtmoko and here are my results... 1. With a plantronics headset once paired, it will work if you tell it to connect as a headset, the buttons work, and audio is ok. However when the bluetooth headset is subsequently turned on or comes in range of the FR, it seems to connect briefly automatically then disconnect, and you have to go in and connect as headset again from the UI. If you connect as handsfree the buttons no longer work for hangup and accept calls. 2. The Bluetooth is very flaky, while testing I had it lock up on me, or the bluetooth UI just would not come up without a reboot. 3. With one of my handsfree devices (the VR3 car speakerphone) if I connect as handsfree device, it actually works very well, the buttons accept and reject calls, and the incoming number shows on the devices LCD. This is surprising as the qt implementation of the handsfree profile looks incomplete, but I may be looking in the wrong place. 4. With my preferred device the Motorola T505 handsfree device, it has trouble connecting on occasions. If connecting as a handsfree device, the devices buttons do not accept or hangup a call, and the incoming number is not detected. But it does seem to work, although not in a usable way. If I try to connect as a headset it does not seem to work at all. Conclusions are that the system needs to be made more sturdy (maybe upgrade to bluez4, which would be a lot of work). The Handsfree profile code needs to be looked at closely and made to work with more devices. We need to make it automatically connect to a preferred device when in range with the preferred profile (headset or handsfree), having to go to the UI to connect everytime is not very usable. However I am impressed with how far Radek has got with this so far, especially as he doesn't use BT much :) I'll see if I can fix some of these issues, time permitting. (Special thanks to Paul Fertser for helping me out on IRC last night, it really helped to get me started on this). Thanks Jim -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Hi Radek, Great job, I have been away from the FR for a while, but I am back to see if I can finally use it as a phone, and it looks like I may be able to now with this bluetooth stuff. Its nice to see that my qtpedometer (with car finder) still works, which is just as well as I have totally forgotten how to build apps for qtmoko ;) I have several bt headsets and handsfree devices, so this is what I have found so far My plantronics earpiece works great, automatically connects when it is on, and the button accepts and hangs up calls. My Motorola T505 handsfree device also works, but the button does not accept or hangup calls, ditto with the VR handsfree device I have. (This is a serious problem for me when in the car). My IOGear stereo headset connects via A2DP, and works with mplayer (although rather choppy), and only appears to be mono. I have an in-car builtin bluetooth, which I haven't tried yet, it has buttons on the steering wheel to accept and hangup calls. I'll do some research to see why the headset button works but the handsfree doesn't, unless someone can point me to the problem. Its amazing that you were able to integrate all this into qtmoko! The incoming call first is a bit of a problem but I can live with that for a while. Thanks Jim Radek Polak wrote: > On Thursday 16 September 2010 07:44:41 Jim Morris wrote: > >> I have not tried to make a GSM call yet using the headset, but was >> wondering how far the BT integration has gone? > > Once you connect to the headset (which looks is working for you) it should > work automatically. > > But there is problem with 2.6.29 kernel - you will have no sound until you > get > first incoming call. Then it should work good. > > Gabrys (who did all the hard work to make it working) said that with newer > kernels this problem is fixed. I am now testing qtmoko v27 with 2.6.34 kernel > but i have my headset at home, so i cant try right now. > >> 1. Should it work with a GSM call? If so what else has to be done to make >> it work? 2. Will the headset button answer an incoming call? > > Yes. For me also the button was working. But beware some headsets which do > not > work well with freerunner [1] - i have Jabra which is ok, but motorola does > not have sound. > >> 3. Do I have to manually connect everytime I want to use the headset? or >> will it automatically connect when in range (like my other cells phones). > > My jabra connects automatically to Freerunner when it's turned on. > >> 4. I notice in the tools there is a start gsm bt audio fix, what does that >> do? does it need to be done every time I start up the phone or connect to >> the BT headset? > > It's called automatically after connecting to the headset. I have it there > for > debugging purposes. > >> Thanks all for the great work, this looks very good at last, maybe after >> waiting several years, if the BT headset stuff works, I can start using my >> FR as a phone ;) (BT handsfree is a legal requirement here). > > I am not using headset for calls so i cant tell if it's daily use ready, but > it would be interesting to hear some experience... > >> I did contribute way back to the power monitoring for qtmoko and fixing >> some bugs in that code, and can contribute to making BT work seemlessly, >> if that is possible, but I need to know how far the current integration >> has gone, and if anyone is actually using BT for phone calls. > > You are already in the "hall of fame" [2] :) > >> I do not really need BT to work for the media players, or voice recording >> but it would be nice. > > It works in qtmoko too - if your headset supports it. You will have to select > something like "available services" from device context menu and then there > should appear "connect A2DP" button. It's bug that the button does not appear > automatically but then it should work. > > Regards > > Radek > > > [1] http://wiki.openmoko.org/wiki/List_of_bluetooth_headsets > [2] http://activationrecord.net/radekp/qtmoko/ > -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
On Thursday 16 September 2010 07:44:41 Jim Morris wrote: > I have not tried to make a GSM call yet using the headset, but was > wondering how far the BT integration has gone? Once you connect to the headset (which looks is working for you) it should work automatically. But there is problem with 2.6.29 kernel - you will have no sound until you get first incoming call. Then it should work good. Gabrys (who did all the hard work to make it working) said that with newer kernels this problem is fixed. I am now testing qtmoko v27 with 2.6.34 kernel but i have my headset at home, so i cant try right now. > 1. Should it work with a GSM call? If so what else has to be done to make > it work? 2. Will the headset button answer an incoming call? Yes. For me also the button was working. But beware some headsets which do not work well with freerunner [1] - i have Jabra which is ok, but motorola does not have sound. > 3. Do I have to manually connect everytime I want to use the headset? or > will it automatically connect when in range (like my other cells phones). My jabra connects automatically to Freerunner when it's turned on. > 4. I notice in the tools there is a start gsm bt audio fix, what does that > do? does it need to be done every time I start up the phone or connect to > the BT headset? It's called automatically after connecting to the headset. I have it there for debugging purposes. > Thanks all for the great work, this looks very good at last, maybe after > waiting several years, if the BT headset stuff works, I can start using my > FR as a phone ;) (BT handsfree is a legal requirement here). I am not using headset for calls so i cant tell if it's daily use ready, but it would be interesting to hear some experience... > I did contribute way back to the power monitoring for qtmoko and fixing > some bugs in that code, and can contribute to making BT work seemlessly, > if that is possible, but I need to know how far the current integration > has gone, and if anyone is actually using BT for phone calls. You are already in the "hall of fame" [2] :) > I do not really need BT to work for the media players, or voice recording > but it would be nice. It works in qtmoko too - if your headset supports it. You will have to select something like "available services" from device context menu and then there should appear "connect A2DP" button. It's bug that the button does not appear automatically but then it should work. Regards Radek [1] http://wiki.openmoko.org/wiki/List_of_bluetooth_headsets [2] http://activationrecord.net/radekp/qtmoko/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
2010-09...@00:02 Jim Morris > Jim Morris wrote: > > >> Also keep in mind that if you've got an ordinary (non-stereo, > >> non-A2DP) headset, it's not supposed to work with mplayer and > >> such. See [2] for the reference. > > > > Ok that makes sense, I do have another A2DP headset, I'll see if that works > > differently. > > Holy crap it worked! I paired with an a2dp headset and it asked to install > the bluez audio via apt, > then after a restart plays though the headset, Radek you are a genius ;) hey! how I can verify my bt device supports a2dp? :S -- ALFA21 IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Jim Morris wrote: > Jim Morris wrote: > >>> Also keep in mind that if you've got an ordinary (non-stereo, >>> non-A2DP) headset, it's not supposed to work with mplayer and >>> such. See [2] for the reference. >> Ok that makes sense, I do have another A2DP headset, I'll see if that works >> differently. > > Holy crap it worked! I paired with an a2dp headset and it asked to install > the bluez audio via apt, > then after a restart plays though the headset, Radek you are a genius ;) Actually all you guys that figured out the blue tooth stuff are geniuses, Radek gets special Kudos from me for getting it to work relatively seemlessly on qtmoko... Now can I get handsfree to work seemlessly? Still working on that. Sounds like it does though from Alfa21's comments. I have several handsfree devices to test it out on. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Jim Morris wrote: >> Also keep in mind that if you've got an ordinary (non-stereo, >> non-A2DP) headset, it's not supposed to work with mplayer and >> such. See [2] for the reference. > > Ok that makes sense, I do have another A2DP headset, I'll see if that works > differently. Holy crap it worked! I paired with an a2dp headset and it asked to install the bluez audio via apt, then after a restart plays though the headset, Radek you are a genius ;) -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Jim Morris writes: > Paul Fertser wrote: >> This [1] page and this guy might help. Also feel free to ping me or >> him on irc, we do know some bluetooth tricks :) > > Unfortunately frameworkd and the dbus stuff does not appear to be > relevant for qtmoko. Some dbus stuff (calls to org.bluez) is relevant :) > seems Radek got most of it working, but going into a shell and > typing stuff to connect and disconnect would probably make the > California Highway Patrol come down on you like a ton of bricks, > especially since texting while driving is illegal (although it > doesn't say typing shell commands is illegal ;) ROTFL -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
2010-09...@08:22 Christ van Willegen > > which is the default for most headsets. > But not for the car. It generates a PIN to use for that pairing. I was able to pair my FR with my toyota and during the process I entered my pin on the dialog showed by the FR. I also was able to pair my FR with a garmin navigator. have you tried both directions for the pairing process? eg: initiate the process on the car searching your FR or vice versa ? btw I'm able to access my phone-book and last dialed numbers and also get the battery and signal status of the FR on the paired device :) -- ALFA21 IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Thanks for the pointers Paul. Paul Fertser wrote: > This [1] page and this guy might help. Also feel free to ping me or > him on irc, we do know some bluetooth tricks :) Unfortunately frameworkd and the dbus stuff does not appear to be relevant for qtmoko. However those pointers did explain what the start gsm bt audio fix does which is hidden in the tools menu on qtmomo. I guess I can sniff around what you guys did for the other dists, and try to do the equivalent here, seems Radek got most of it working, but going into a shell and typing stuff to connect and disconnect would probably make the California Highway Patrol come down on you like a ton of bricks, especially since texting while driving is illegal (although it doesn't say typing shell commands is illegal ;) Anyway the main point is I need to integrate all this into the system so it all happens automatically, like on most other phones, otherwise it defeats the object of having a "handsfree device". Has this been automated on the other dists, or do people still need to setup everything manually? Does qtmoko use the same version of bluez as the other dists? Do those dists handle the buttons for answering and hanging up calls? If so I can probably port some of that over unless it all uses frameworkd and dbus commands. If nothing else I can use it as a pointer to how to do it. > > Also keep in mind that if you've got an ordinary (non-stereo, > non-A2DP) headset, it's not supposed to work with mplayer and > such. See [2] for the reference. Ok that makes sense, I do have another A2DP headset, I'll see if that works differently. Thanks Jim -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
On Thu, Sep 16, 2010 at 7:58 AM, Jim Morris wrote: > Christ van Willegen wrote: >> Is there support for pairing w/ a PIN? If I can only pair it with my > > When I paired with my headset, it asked for a PIN and there was a screen that > I was able to type in > which is the default for most headsets. But not for the car. It generates a PIN to use for that pairing. > When you pair with the car there should be two options to connect, "connect > headset" and "connect > handsfree unit", I got the PIN screen when I clicked the "connect handsfree > unit". Ok, let me see again and try to get this set up. I can probably check tonight. Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Jim Morris writes: > Anyway I tried to get my bluetooth headset to work, and I am not > sure exactly what needs to be done to make this work seemlessly. This [1] page and this guy might help. Also feel free to ping me or him on irc, we do know some bluetooth tricks :) Also keep in mind that if you've got an ordinary (non-stereo, non-A2DP) headset, it's not supposed to work with mplayer and such. See [2] for the reference. [1] http://wiki.openmoko.org/wiki/User_talk:Gabrys [2] http://piotr.gabryjeluk.pl/bluetooth-on-shr -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Christ van Willegen wrote: > > On a related note, I have a car with integrated BlueTooth support. > > Recently, I tried pairing my FR with it. At some time in that process, > the car displays a PIN that should be entered on the phone to complete > the pairing, but there is no PIN dialog showing on the FR. > > Is there support for pairing w/ a PIN? If I can only pair it with my When I paired with my headset, it asked for a PIN and there was a screen that I was able to type in which is the default for most headsets. When you pair with the car there should be two options to connect, "connect headset" and "connect handsfree unit", I got the PIN screen when I clicked the "connect handsfree unit". -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
On Thu, Sep 16, 2010 at 7:44 AM, Jim Morris wrote: > Anyway I tried to get my bluetooth headset to work, and I am not sure exactly > what needs to be done > to make this work seemlessly. On a related note, I have a car with integrated BlueTooth support. Recently, I tried pairing my FR with it. At some time in that process, the car displays a PIN that should be entered on the phone to complete the pairing, but there is no PIN dialog showing on the FR. Is there support for pairing w/ a PIN? If I can only pair it with my car to make phone calls, that's OK. I don't need the 'fancy' stuff like downloading my phone book into the car (and stuff like that). Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qtmoko v26 bluetooth headset
Hi, I upgraded to v26 of qtmoko and it looks pretty darn good! Wifi worked out of the box with wpa/psk which is an awesome feat! Anyway I tried to get my bluetooth headset to work, and I am not sure exactly what needs to be done to make this work seemlessly. I paired OK, I connected as handsfree, and the headset beeped. Clicking the headset button did not do anything, it should usually recall the last number or bringup the dialing screen. Neither of the media players (mplayer and the other one) played through the headset, and voice record did not record or playback through the headset either. I have not tried to make a GSM call yet using the headset, but was wondering how far the BT integration has gone? 1. Should it work with a GSM call? If so what else has to be done to make it work? 2. Will the headset button answer an incoming call? 3. Do I have to manually connect everytime I want to use the headset? or will it automatically connect when in range (like my other cells phones). 4. I notice in the tools there is a start gsm bt audio fix, what does that do? does it need to be done every time I start up the phone or connect to the BT headset? Thanks all for the great work, this looks very good at last, maybe after waiting several years, if the BT headset stuff works, I can start using my FR as a phone ;) (BT handsfree is a legal requirement here). I did contribute way back to the power monitoring for qtmoko and fixing some bugs in that code, and can contribute to making BT work seemlessly, if that is possible, but I need to know how far the current integration has gone, and if anyone is actually using BT for phone calls. I do not really need BT to work for the media players, or voice recording but it would be nice. Thanks -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community