Related
I'm currently running DamageControl 1.0 but have also tried AOSP 2.1 and DarchLegend 4.1 and cannot get my phone to pair the 'calls' part to my Pioneer car stereo. The music part pairs fine but not the phone. It worked perfectly on every version of 1.5 I ran.
Is there a way to push some 1.5 bluetooth files to a 2.1 rom?
I searched XDA and it appears that some folks with Eris phone using the latest leak are also experiencing this same thing, one guy specifically stated he had a Pioneer deck as well - coincidence? Could it be Pioneer?
Reading the rom specific threads it appears that most folks have working bluetooth so it may be my situation, hence the question, can I push some 1.5 files to 2.1 to get the phone to pair? If so, any help as to which ones?
ItsDon said:
I'm currently running DamageControl 1.0 but have also tried AOSP 2.1 and DarchLegend 4.1 and cannot get my phone to pair the 'calls' part to my Pioneer car stereo. The music part pairs fine but not the phone. It worked perfectly on every version of 1.5 I ran.
Is there a way to push some 1.5 bluetooth files to a 2.1 rom?
I searched XDA and it appears that some folks with Eris phone using the latest leak are also experiencing this same thing, one guy specifically stated he had a Pioneer deck as well - coincidence? Could it be Pioneer?
Reading the rom specific threads it appears that most folks have working bluetooth so it may be my situation, hence the question, can I push some 1.5 files to 2.1 to get the phone to pair? If so, any help as to which ones?
Click to expand...
Click to collapse
I am also running into this with all 2.1. I have a premier(pioneer) deck. Any luck finding a solution?
CharlyDigital said:
I am also running into this with all 2.1. I have a premier(pioneer) deck. Any luck finding a solution?
Click to expand...
Click to collapse
Nope. I tried everything possible but nothing got the phone and radio to pair. I just can't go back to 1.5 so I've resorted to using a BT earpiece until the official 2.1 is released. Hopefully it will have an updated Bluetooth.
If you come across something I'd love to be kept in the loop.
Truely sorry i cant be much help...but you might consider posting your question in damages thread, or pm him.
Cheers
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.
I know complaining about that is almost ridiculous but I thought there might maybe be a solution or at least an explanation for this problem. I tried to connect the Android HD2 to my BMW and it worked in the first place. Also Bluetooth Audio connection works which gives me the option to listen to my music while the phone still is in my pocket.
But when I try to make a call or answer a call (which is shown on the display) nothing happens. Is there any idea to fix that?
More info needed....like android build etc etc....
Sent from my HTC HD2 using XDA App
Sounds like your running a cm based rom. Download and apply one of the sense builds. try this one: http://forum.xda-developers.com/showthread.php?t=791835
I'm not using a Cyanogen ROM since I need to use HTC Sync as I'm using the phone for business. I'm using the new 3.2 FroyoStone ROM which is very fast and stable and stock.
Today I had a minute or two of hope when I was making a call from my car using bloototh. But after around three minutes of speaking to the other person I could only hear him while he was obviously not hearing anything from me.
I then tried to stop and start the bluetooth in the properties section of android again which caused a total system crash...
Until the problem is solved completely I will continue to write my expiriences, experiments and disappointments here even if nobody gives me any response to it.
I've had loads of problems with Darkstone 3.2, you can try a different build and see if that works...
Sent from my HTC HD2 T8585 using XDA App
Now I found a midtime solution. When using the buildby Mdeejay (FroYo HD v.3.6 / kernel:hastarin R7.2) the bluetooth handsfree device in my car works just perfectly. Unfortunately the DesireHD build doesn't support the camera yet and the disconnects are out to happen much more frequently than in the other builds.
I will try to run this build using the newer kernel V7.6 and see if the bluetooth device is then still working.
Pairing Problems with BMW iDrive (525d 2005)
Hi,
I've been having this issue with my BMW iDrive and HTC Desire HD, it keeps constantly connecting and disconnecting the bluetooth on HTC stock ROM and ARHD 6.3.1, but with the Custom ROM (CM7.1) I keep getting connection prompts and keep going around in loops without any success in pairing.
I have tried the suggestion from the forum topic below with regards to the audio.conf mod and see if it has any success. This failed.
forum cyanogenmod #entry85118
Push to /sdcard/ and then run in sh
cd /sdcard/
cp /system/etc/bluetooth/audio.conf /sdcard/audio.conf.bak
mount -o remount,rw /system
cat audio.conf.txt > /system/etc/bluetooth/audio.conf
mount -o remount,r /system
Then reboot.
/system/etc/bluetooth/audio.conf amended with the following parameters
# Configuration file for the audio service
[General]
Enable=
Disable=Headset,Gateway,Source,Control,Sink
# Do not require master role for incoming connections
Master=false
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
MaxConnections=3
BMW iDrive version 1-04-09-500 0 (BMW 525d E60 2005) Build July 2004
I've tried a few custom ROMs now without success, if the bluetooth itself could be patched up that would be nice, if I need to downgrade the bluetooth please let me know where to begin as I have only just begun tinkering with Rooting and Custom ROMs.
I'm now thinking I'll have to get the BMW iDrive software updated to see if this resolves my issue.
Regards
M
Bluetooth in car
Someone related to bluetooth to in the car, for those that don't have it an easy solution is Flexsmart X2. It works just fine, almost an alternative to their real thing, please check it out.
Jimmy4485 said:
Someone related to bluetooth to in the car, for those that don't have it an easy solution is Flexsmart X2. It works just fine, almost an alternative to their real thing, please check it out.
Click to expand...
Click to collapse
I don't like the idea of tuning into the radio to hear the phone call, I tried one of those MP3 things with mixed results.
I've found a much simpler solution, iPhone 3gs pairs/connects, syncs address book and works!!!
So clearly the Bluetooth is junked in HTC/Android phones, we tried a HTC Magic running an older Android version which had the same problem.
I'm back to the Stock HTC ROM until I find a solution for the existing phone or eligible to upgrade my contract.
Update iPhone 4 also works so that settles it, now need to get hold of someone with iPhone 4s for the sanity check.
HTC Desire HD now syncs/connects fine.
Had to also rename the blacklist.conf and auto_pairing.conf.
Stop and clear data for Bluetooth share service.
Initiated call from phone call successful after a few mins the address book was up on the idrive and was able to start the call from there.
Currently using ARHD 6.3.1 with recommended radio file.
Sent from my Desire HD using XDA App
arfie_don said:
HTC Desire HD now syncs/connects fine.
Had to also rename the blacklist.conf and auto_pairing.conf.
Stop and clear data for Bluetooth share service.
Initiated call from phone call successful after a few mins the address book was up on the idrive and was able to start the call from there.
Currently using ARHD 6.3.1 with recommended radio file.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I spoke too soon, lol. Back to square one.
Hi,
I've been trying to pair my Legend (updated to HTC Android 2.2) with Holux M-1200 bluetooth GPS receiver but without success, I kept getting "wrong PIN or passkey" error. The strange thing is that I can pair this same Holux M-1200 with Desire and Wildfire (both running HTC Android 2.2) without any problem. Does this means Legend's Android 2.2 is not the same as Desire and Wildfire?
I drive to the neighbor country quite often and since I don't have a data roaming plan and it usually take me a very long time (5~10 minutes) to get a gps location fix without data access.
Is there a work around to get this working? Or even better, is there a way to have a faster gps fix without using data (something like QuickGPS in HTC TD2 running WM?)?
Thanks in advance for any help.
Its better to contact htc customer care and report the issue.
There are many frustrating unsolved bluetooth issues with legend.
For me, its with my blaupunkt bluetooth audio in my car stereo.
It might pair, but many a times the audio isn't routed through the bluetooth even if its paired and connected.
lessirey said:
Its better to contact htc customer care and report the issue.
There are many frustrating unsolved bluetooth issues with legend.
For me, its with my blaupunkt bluetooth audio in my car stereo.
It might pair, but many a times the audio isn't routed through the bluetooth even if its paired and connected.
Click to expand...
Click to collapse
Thanks for your post, I shall report the issue to HTC Customer care.
ykkhern said:
Hi,
I've been trying to pair my Legend (updated to HTC Android 2.2) with Holux M-1200 bluetooth GPS receiver but without success, I kept getting "wrong PIN or passkey" error. The strange thing is that I can pair this same Holux M-1200 with Desire and Wildfire (both running HTC Android 2.2) without any problem. Does this means Legend's Android 2.2 is not the same as Desire and Wildfire?
I drive to the neighbor country quite often and since I don't have a data roaming plan and it usually take me a very long time (5~10 minutes) to get a gps location fix without data access.
Is there a work around to get this working? Or even better, is there a way to have a faster gps fix without using data (something like QuickGPS in HTC TD2 running WM?)?
Thanks in advance for any help.
Click to expand...
Click to collapse
hi, don't know if you ever got this sorted, but I had the exact same issues with a stock legend and a qstarz q818xt gpsr (and I believe the qstarz gpsrs use very similar hardware to the holux ones, if not exactly the same!)
I eventually found that by rooting (not trivial as I had to downgrade) and then flashing CM7 rom onto my legend I was able to get the device to pair easily, it appears to be an issue with the bluetooth stack in the stock rom.
Cheers,
Sam
insanimal said:
hi, don't know if you ever got this sorted, but I had the exact same issues with a stock legend and a qstarz q818xt gpsr (and I believe the qstarz gpsrs use very similar hardware to the holux ones, if not exactly the same!)
I eventually found that by rooting (not trivial as I had to downgrade) and then flashing CM7 rom onto my legend I was able to get the device to pair easily, it appears to be an issue with the bluetooth stack in the stock rom.
Cheers,
Sam
Click to expand...
Click to collapse
Hi Sam,
Thanks for the info. I've decided to stick with stock ROM as I still prefer Sense UI and some Sense's widgets. For the time being, well, just switch on the gps once in a couple of days, that helps......
Cheers,
YK
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