Database Users

Bluetooth not working right with Pioneer and Android

I've been using Androind on my HTD for +/- the past month or so, and have yet to have stable bluetooth operation through my Pioneer AVH-3200BT which is enabled for BT phone calls (NOT A2DP). I've been through several builds, and currently am using shu8i's latest shubCRAFT 1.4d (23.08.2010 build). I'm got HPSL3 and Radio 2.12.
I get a lot of forced close app errors with trying to establish BT connection. Sometimes I get further, like the Pioneer can usually pick up my contact list after a few tries... But the worst happens when I try to make a phone call. The system hangs, the sound goes dead, the Pioneer cancels the call, and the HTC HD2 usually crashes back to the home screen. From then, I usually dont have any sound for anything until I reboot the HD2.
In WM6.5 Bluetooth works fine with the Pioneer.
Can anyone help me out with this? I'd be willing to pull some logs / demos / or get more vital information if I knew where to look. I'll be the geinea pig!
Thanks in advance

I'll add plantronics voyager 815 to list. maybe a list of working headsets might help if anyone has one.

my Jabra T3030 doesn't work either. It works great with A2DP and it even rings when i get a call. but it hangs the device if i try to answer and there's no audio in calls.
I tried every build possible

I cannot get my Bluetooth wireless headset to work also ,it works on phone calls but on media ,no sound is transferred ,Ian using Mattc 1.6b with sonyericsson headset ,that works more than perfect on windows
Sent from my HTC HD2 using XDA App

saabguy123 said:
I've been using Androind on my HTD for +/- the past month or so, and have yet to have stable bluetooth operation through my Pioneer AVH-3200BT which is enabled for BT phone calls (NOT A2DP). I've been through several builds, and currently am using shu8i's latest shubCRAFT 1.4d (23.08.2010 build). I'm got HPSL3 and Radio 2.12.
I get a lot of forced close app errors with trying to establish BT connection. Sometimes I get further, like the Pioneer can usually pick up my contact list after a few tries... But the worst happens when I try to make a phone call. The system hangs, the sound goes dead, the Pioneer cancels the call, and the HTC HD2 usually crashes back to the home screen. From then, I usually dont have any sound for anything until I reboot the HD2.
In WM6.5 Bluetooth works fine with the Pioneer.
Can anyone help me out with this? I'd be willing to pull some logs / demos / or get more vital information if I knew where to look. I'll be the geinea pig!
Thanks in advance
Click to expand...
Click to collapse
I got similar problem with my Motorola Headset too, it just keep hanging with the dialer, without bluetooth one, the dialer works flawlessly. Mine is Shubcraft

I think I figured it out... I set the pioneer to accept connections with pin 1234 instead of 0000 and it seems to be working alright now.
Sent from my HTC HD2 using XDA App

precsmo said:
I got similar problem with my Motorola Headset too, it just keep hanging with the dialer, without bluetooth one, the dialer works flawlessly. Mine is Shubcraft
Click to expand...
Click to collapse
I'm also having troubles with my Sony Ericsson MW600. I did get it going with I think ShubCraft 1.4b but now on 1.5 it won't have it...
It pairs fine, works fine with Media - AVRCP controls working, etc.
But the phone app just doesn't like it. I've tried to switch BT on and off whilst in call and most of the time get a force close on the phone app.
My libbluetooth.so files are dated 04/08/2010. Does anyone have later dated .so files I can try? Or earlier ones for that matter!?
Thanks all.

wheeliemonster said:
My libbluetooth.so files are dated 04/08/2010. Does anyone have later dated .so files I can try? Or earlier ones for that matter!?
Thanks all.
Click to expand...
Click to collapse
I've changed libbluetooth.so for this one:
http://code.google.com/p/androidobex/downloads/detail?name=libbluetooth.so
it work's but the hd2 ask for the bluetooth pass every time that connects.

magnus48 said:
I've changed libbluetooth.so for this one:
http://code.google.com/p/androidobex/downloads/detail?name=libbluetooth.so
it work's but the hd2 ask for the bluetooth pass every time that connects.
Click to expand...
Click to collapse
I can't even get the bluetooth radio to turn on using this file...
Not having bluetooth headset is the most frustrating thing. Well its a close second to nearly every android build claiming to have bt working in the OP but it doesn't work!!

bhilgeman said:
I can't even get the bluetooth radio to turn on using this file...
Not having bluetooth headset is the most frustrating thing. Well its a close second to nearly every android build claiming to have bt working in the OP but it doesn't work!!
Click to expand...
Click to collapse
I've tried changing the libbluetooth, libbluetoothd and libbluedroid files time and again with Shubi's build and nothing works.
I had some success today though. I'm currently using Shubi's build but with the michyprima r10 kernel.
I was trying a different kernel earlier - the huanyu OC kernel from here:
http://forum.xda-developers.com/showthread.php?t=777921
This got my BT headset working for calls and A2CP/AVRCP...
PLEASE NOTE: This kernel is in beta still, read the thread!
Unfortunately, it proved to be a little unstable for me, so I've had to go back to michyprima's kernel.
But it does seem that the problem lies in the kernel, rather than the bluetooth libraries.

bhilgeman said:
I can't even get the bluetooth radio to turn on using this file...
Not having bluetooth headset is the most frustrating thing. Well its a close second to nearly every android build claiming to have bt working in the OP but it doesn't work!!
Click to expand...
Click to collapse
A reboot is required after overwriting libbluetooth.so file
With some old android distributions I cant turno on the bluetooth radio, but it was a kernel matter. Maybe updating the kernel solves the problem.
Now I use FroyoStonev2 with this [kernel][.32.9](BFS+BFQ+AXI+OC+UV) build on 09.09.2010(version 0.2)
But every time that reboot the hd2 need to pair with the freehands.
Every time that reconnect it needs to reenter the code.

[Q] Froyo w/sense 1.7. Bluetooth flakey

So far I'm pretty happy with Froyo on my phone. I've got the barebones WM for droid rom, radio version 2.12.50.02_2and a FAT32 SD card I freshly formatted prior to installation.
It's great, save for the fact that my plantronics discovery 975 headset doesn't seem to play nicely with Froyo. It pairs just fine, but I don't get any audio and the phone app seems to lockup when I attempt to answer a call while paired. This is via either the button on the handset or the headset.
I know Android for HD2 is still in dev, so I"m willing to accept this is just a problem with no fix. However, if there is a bug out there I can fix to get my headset working, I would love to know about it.
Any help would be appreciated.

Mccm v.1.5 works nicely with my SE headset. It's the only android without sense build where Bluetooth is functional with my headset. Have tried them all.
If you're into sense, Froyostone build has Bluetooth perfectly functional.
Sent from my HTC Desire using Tapatalk

That's what I'm told, but...
....the MattC Froyo Sense is a slightly moded version of the stone, if understand the txt doc that comes with it.
I'll try the straight stone installation and let you know how it goes. In the meantime, if anyone has a suggestion as to why this would be flakey, I'm really curious what the issue is.

[Q] Bluetooth issues with Froyo

So I flashed to a froyo ROM over the weekend and have found someone posted a fix for the gps issues, but I'm having BT issues as well. Has anyone else experienced this: I can pair certain BT accessories but not others, and even when paired the devices cannot connect without multiple connection requests.
My specific issue is that I have motorola rockr bt earbuds, and a Jabra car kit, and they both pair with the phone (after a few trys) but neither will automatically connect to the phone once they're turned on. With the earbuds I have to manually try to connect 6 or 7 times in a row before they'll connect, and even then they may only connect with the phone audio only. This wasn't an issue with the stock ROM so I'm assuming its the bt radio library for Froyo thats the problem?
I'm not new to development, but I'm kinda new to development on Android. I've been trying to learn more about the radios and how they're configured within the OS but I haven't found a lot of good documentation on it. I'd be happy to work this out for myself and post any improved radio to the forum but it would be helpful if someone could send me a link to some learning material? If someone has an improved Epic Froyo BT radio to flash that would be helpful as well

yes bluetooth issues as well, but different in that only when i turn bluetooth on it foreclose's. the bluetooth is otherwise not affeceted. only on the initial start up.

I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!

Delta1Fox said:
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Click to expand...
Click to collapse
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.

revjtanton said:
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
Click to expand...
Click to collapse
I noticed that too with the stock 2.1. However, Bluetooth voice dialing is a feature built into 2.2. I've read that some people having it work great, but other's like myself, are not having it work at all. Oh well. I'll live for now. Hopefully if it isn't fixed beforehand then it'll be fixed with the "official" release. LOL.

now that you mention it, i had this problem too doing some bluetooth file transfers between my buddy and I's phones last night. it struggled to connect multiple times but after the first successful transfer it seemed to stop having problems for a little. I'm moving back to 2.1 until we get some non-beta custom roms for froyo because i use bluetooth and gps everyday. just out of curiosity though, for those who are having problems, which rom and modem are you using?

I put the DI18 modern on there and that has seemed to fix the gps more or less. I think I'm going to go back as well. Maybe I didn't flush data enough times but layar can't find the camera, neither can the bar code scanner...it's close, but Froyo just isn't ready for the Epic yet.
Sent from my SPH-D700 using XDA App

Still having Bluetooth problems with official Froyo release on Epic 4G
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...

I am using the new official Froyo release from Samsung/Sprint. having the same buggy issues I had with the old leaked version.

donkeysauce said:
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
Click to expand...
Click to collapse
I can confirm these issues still exist in the official release.

I'm having the same problem, but when I use bluetooth in my car, it insists on transmitting sounds to my car's bluetooth, even when I repeatedly uncheck Use for media audio. I don't have an option in my car to disable A2DP. My only complaint with Eclair, other than speed (I'm using Bonsai4All, and previously, Syndicate) was that I was running out of space for software (was using EpicExperience). Sometimes, bluetooth won't connect at all, necessitating a phone reboot, or going into airplane moe and then back out. So I'm gathering that this is across the board, regardless of Froyo build? Syndicate didn't work at all with my car.

Is There Any Fix for the Bluetooth Voice Dialing Crash Issue?

I've never seen a dedicated thread on this but I've seen people make off-hand comments about this issue from time to time. I think it started happening in Tytung R9 and higher kernels.
I am using a BlueAnt T1 Bluetooth headset. It pairs just fine and I can use it generally without any issue.
The problem comes when I use voice dialing to initialize a call from the Bluetooth headset. It connects to the phone and I get the normal Android "Speak now...." I speak my command "Call <person> on <service>...." It states the command back like normal and then _as soon as_ it switches to the phone app (eg, com.android.phone process) it locks up the phone and the only way to recover is to pull the battery.
If, instead, I go to the phone app, find the person, and call them that way (even with Bluetooth paired) it _always_ works without any problems. This isn't a long-term solution for me because I need to use voice dialing when I'm in my car.
Now that GPS looks to be fixed and CLK data over PPP is much more stable, this Bluetooth issue is the last thing standing between me and treating the HD2 as my full-time native Android phone (currently I tinker on the HD2 but use my Nexus One as my daily driver).
I've tried multiple different ROMs, from HyperDroid-CM7, HyperDroid-GBX, Typhoon CM7, and Nexus-HD2-Gingerbread. They all have the same issue though Nexus-HD2 appears to be worse than the others (that is, the problem happens more often there).
I've used the infamous audio.conf update as well as the various no-wonk and libaudio patches and none of them help this issue.
Anyone else experienced this and have any feedback on how you overcame it?

I have the same kind of problem and tried a lot of different ROMs - not help.
I tried Blueant ST3, Motorola t305.
Phone book copied to blueant very well, but voice dial has same simptoms like yours - even if phone does't hang sound goes away from phone permanently(needs reboot). Is there any other ROM which works well with bluetooth hadsfree?
Any one?
P.S. Looks like it is real problem, but non of developers pay attention to it - they just don't have handsfree maybe

Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...

clio94 said:
Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...
Click to expand...
Click to collapse
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....

This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).

svet-am said:
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....
Click to expand...
Click to collapse
I think it is not the kernel, same kernel will crash in CM7 but no in CM6. I think the problem is related to the libaudio.so and other libs in system/lib.

robrob777 said:
This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).
Click to expand...
Click to collapse
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"

svet-am said:
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"
Click to expand...
Click to collapse
I'm using it as my daily driver (CM6), I came back just bc of the calling issues in Gingerbread.
the build that I'm using has not been updated since Jan 7, however I applied around 10+ patches and now it works as good as the new builds.

I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.

robrob777 said:
I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.
Click to expand...
Click to collapse
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.

i just verified the problem exists in MIUI as well. I tested MIUI since it's allegedly a "clean room" type of build environment.

svet-am said:
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.
Click to expand...
Click to collapse
Yes, I tested successfully in a Froyo based ROM.
I went back for a moment to CM7 and tested...sound couldn't return to the phone after calling with BT, also during the call I was not able to switch to speaker phone like I do in the froyo based ROM.

Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.

zcdg said:
Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.
Click to expand...
Click to collapse
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.

svet-am said:
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.
Click to expand...
Click to collapse
Yes you are right. It is just what Tytung said(i asked in his thread). Probably he meant GB for HD2....Soon or later they will figure it out i think...
For now will use Froyo 1.9G....

tytung said:
I don't have any Bluetooth headset.
AFAIK, some people have the sound issues, e.g. causing the phone app FC, since using Gingerbread 2.3.4.
But it doesn't affect all people, I don't know why.
No solution so far. To use Gingerbread 2.3.3 instead if you are one of them.
Click to expand...
Click to collapse
I finally found Tytung's exact quote as to why he won't look into the issue. It can be seen in context over here: http://forum.xda-developers.com/showthread.php?t=905060&page=524#
So, it might not be Froyo that's the fix but rather older versions of Gingerbread as well.

i have found a workaround fix for this bug.I tried it in tytung`s v2.9 rom and in dorimanx cm7 light rom with driztee v2 libaudio file.For bt voice commands i am using cyberon voice commander because google app doesnt support yet greek language
i connect my bt headset (motorola h300) and then i use super bt mono froyo free app https://market.android.com/details?id=com.steven.supermonofroyofree&feature=search_result to send audio to bt headset.
After pushing the bt headset button cyberon voice starts and i can give the command i want.After giving the command, audio goes back to the phone (you will hear a beep from phone speaker).The weird thing is that the audio is in extremely low level for hearing music but when you receive a call it is in normal level.
If i close super bt mono froyo app,audio returns to phone in normal level.
But if i accidentally (after i close the app) push the button for voice bt command,audio will disappear.
If the app is on and you receive a call,all audio will go again to bt headset and to return it to phone speaker after end call, i push bt headset,cyberon voice starts and i dont give any comand.After cyberon ends,audio goes back to phone with low level for media hearing.
Sure this isnt the perfect solution,but the important thing for me is that with this way,audio is not go away and i can give bt voice commands.
Also i tried bt mono app http://forum.xda-developers.com/showthread.php?t=950472 and it have a little different behaviour.I cant start from bt headset cyberon voice comander,but only from the phone and after giving a command,audio returns to bt headset if you have enable the setting "restart after call".So i think it maybe be helpful to people who want to have audio all time in a bt carkit.

Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.

zcdg said:
Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.
Click to expand...
Click to collapse
thanks for that follow-up and testing. I was wondering if whether or not it might be a "fault" in the VoiceDialer.apk or even in the Phone.apk. I have been using my Nexus One for daily stuff. I might try replacing VoiceDialer and/or Phone.apk in a newer ROM (eg AOSP 2.3.5 or so) with the old version and see if it works.

Ive wondered about this as it is to me the last issue I have with my HD2. Here is a search link for some entries in Tytungs rom & kernal thread...
http://forum.xda-developers.com/search.php?searchid=86308155
Also here is a comment from the man himself...
http://forum.xda-developers.com/showpost.php?p=15996942&postcount=5953
and here is a post in reply that talks about the same issue being replicated using Bluetooth...
http://forum.xda-developers.com/showpost.php?p=15997234&postcount=5956
Some more chat about the sound issues...
http://forum.xda-developers.com/showpost.php?p=16113973&postcount=6045
Another thread with logcats on it...
http://forum.xda-developers.com/showthread.php?t=1060486

[Q] Bluetooth update for Jaguar DHD

Hi,
I´m using the Jaguar DHD Image on my HD2 WM6.5 for a long time.
It works very well.
The only problem that I have is that sometimes I get a connection with my Bluetooth devicese and somtimes not. Then I have to switch blutooth off an on a sveral times.
Is it possible fix this problem?

Bluetooth update for Jaguar DHD
This post is just 1 day old and 144 clicks.
I think there are more people who have the same problem.
Is it posible to contact Jaguaralani direct?
My build is an SD Build WM 6.5
Kernel 2.32.15_r9-gd0fb339
tytung
Build No 1.83.415.4 JaguaralaniDHD-ARA
It would be nice to get some help.
Thanks

Tar_zan said:
This post is just 1 day old and 144 clicks.
I think there are more people who have the same problem.
Is it posible to contact Jaguaralani direct?
My build is an SD Build WM 6.5
Kernel 2.32.15_r9-gd0fb339
tytung
Build No 1.83.415.4 JaguaralaniDHD-ARA
It would be nice to get some help.
Thanks
Click to expand...
Click to collapse
Try a different build. Bluetooth is worrking well on every rom i have tried, both nand and sd builds.

Bluetooth update for Jaguar DHD
Hello evilbarcode,
bluetooth is working on my device ,too.
But the "autodetect" is not working stable.
Sometimes it connects automaticly sometimes you have to start bluetooh several times or push the connect bottom a few times.
So on other builds there is no problem, you switch bluetooth on...and the devices are conected.

Tar_zan said:
Hello evilbarcode,
bluetooth is working on my device ,too.
But the "autodetect" is not working stable.
Sometimes it connects automaticly sometimes you have to start bluetooh several times or push the connect bottom a few times.
So on other builds there is no problem, you switch bluetooth on...and the devices are conected.
Click to expand...
Click to collapse
Yes, that is correct. I've recently installed a sense 3.5 nand build, but when I first put android on my hd2 (about 2 months ago) I used sd builds and I am pretty sure my bluetooth devices connected straight away (after I had connected them the first time). If your keen to stay on sd builds try this one. It was the first sd build I used, an older version but still good. Should be much better now though.
Cheers,
Evil.

Bluetooth update for Jaguar DHD
Thank you for that link.
That build looks good.
Last week I tryed the EVO HD2 V6 (Nexus) Build.
I like it, but there are some bugs.
But mr evil is working on V7.
But I also like my JaguarDHD (Desire HD) Build. It works almost perfect for me for about one year. Onyl this little Bluetooth thing is disturbing.
I don´t know anything about creating builds, but perhaps it is possible to create an update file with the bluetooth part of one of the other builds?

Bluetooth update for Jaguar DHD
Does no one have an idea how to do that?