I don't think this topic has been discussed before (I did do a search before posting a new one). If it has, please remove it and redirect me to the correct thread, thanks!
So, here is my problem: I have a HTC Sensation 4G phone and I was trying to pair it to my car (Chevrolet Orlando 2012) using bluetooth. The car told me to do a search on the phone and once it has found it, enter the code provided. So I did all that and it seemed to worked out fine. It said the pairing was successful and it was ready for use. Then, things started to get a bit weird. Every now and then, and I am talking like every 10 to 15 seconds or so, the bluetooth will automatically turn off (unpair itself) and then 10 to 15 seconds later, it will pair itself again. While it is unpaired, it will switch over to the OnStar Handsfree Calling Service. Does anyone have any idea why this is happening? My brother has an iPhone 4S, and my mom has the LG Optimus, and they both worked fine, no disruptions at all.
Does anyone have any idea what the problem could be?
have you installed any custom rom?
matt95 said:
have you installed any custom rom?
Click to expand...
Click to collapse
Thank you for the reply, but no, I haven't installed any custom roms before since I don't even know how. I am currently running on Android 2.3.4 and HTC Sense 3.0, software number 1.45.666.5
I have contacted GM about it and they are saying that it's a problem with a lot of phones and they are working with the manufactures to rectify the problem. They have no time frame nor are they very willing to contact you if they solve the software problems. My husband just got a 2012 Toyota Yaris and his HTC Sensation 4G works perfectly! My brand new Chevy Cruize does the same exact things that yours does. Please post if you find out anything more, and I will do the same.
Related
Hey Guys, i'm hoping you can help me.
I have searched this forum and couldnt find anyone that has the same bug as me. I apologize in advance if there is a thread already that discusses this.
I have a Ford Mondeo Titanium X 58plate. Bluetooth syncs up and sends/receives calls great, however When I try to hang up the call it crashes. Is anyone having the same problem?
I upgraded my o2 HTC phone to the latest 1.66 rom and I still get the same problem. Any help would be appreciated.
I too have the same issue. I have a Mondeo Zetec and suffer from the same issue. After hanging up, the phone continually tries to connect and disconnect and the only way to stop it is to turn off bluetooth completely. I logged the problem with HTC and they were trying working on the problem howver I havent heard anything from them for 3 weeks. Im considering changing the bluetooth stack on the phone but arent sure how and with which stack.
I heard that changing the stack to the Microsoft default causes other issues. Let me know if you get a response from HTC regarding a fix. I dont even bother connecting the phone to the car anymore because it just crashes everytime i get a call, its so frustrating.
This is the response I got from HTC:
We can never guarantee that our products will be compatible with car kits or bluetooth headsets.
There are different ROM versions of Windows Mobile 6.5.
It might be that this product is not 100% compatible with this specific car kit.
When it comes to upgrades and updates then you will have to contact O2 for them to provide the upgrades for you.
Best regards,
Jozefine M
HTC
Probably a generic answer to everyone.
Same issue/possible fix
I have a Titanium X sport exactly the same issue.
I was told a couple of days ago if you switch off Data connection in Wireless controls in Settings it helps and I have tested a few times and this does seem to work.
I have not had an opertunity to test thoroughly and would be interested to here if it helps you
Okay.. I know. This is my first post, but don't use that to determine the validity of the information.
I've been on here for months, just didn't have anything useful to contribute until now.
Switched from rooted Gingerbread MT3G to G2x - was pretty excited till the bluetooth issues set in.
Didn't have the random reboots like everyone else. I think that happened once in my pocket... not thing to write home about there. This damn bluetooth was killing me though. Like a bad toothache badly in need of a root canal. Every time I picked up the phone I was reminded how beautiful but flawed this is.
So my search began. Poured over LG forums, T-Mobile and Google searches, compiling information. It became clear that this didn't seem like a hardware issue. The crappy Andriod 2.2 shipped with the phone was the issue. To me it seemed like this wasn't fully tested before shipping. Has sold tens of thousands of these phones and were largely unaware of the issue - the techs were surprised when the reports came in - mainly from US based customers on T-Mobile. In my quest I stumbled across an app that reported to fix a similar issue on a few other phones and gave it a shot, and it worked. So real simple here you go:
1. Root your phone, if you haven't already done so. I did with a heavy heart. Was waiting to do so but this issue was driving me nuts.. I used these scripts to Mac and Linux (I'm a unix guy):
http://forum.xda-developers.com/showthread.php?t=1048309
2. Download, from the market, and run, the following app:
>>>> Bluetooth Fix Repair <<<<
That's it!!
Here's what I did to test:
a. Left headset on, power cycled phone
b. Left phone on, power cycled headset
c. Out of range disconnect on head set, then moved back in range - successfully placed call.
d. Received call from a fresh connect, force range disconnect, then reconnect - successfully received call.
e. Disconnected headset from phone menu, then reconnected, placed call successfully.
f. Left headset and phone on for hours, multiple disconnect/reconnect - successfully placed calls.
I'm using a Blueant Q1, with the Blueant app from the market - BTW.
All seems to be well so far.. Give it a shot
fix the a2dp on gb and i'll give you your first donation.
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
donbeth said:
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
Click to expand...
Click to collapse
My battery life is fine. Lasts the whole day and then some. Check the running apps and kill the unnecessary tmobile apps and anything else that you don't need. Another way to save battery is to drop the data rate down to 2G. Settings --> Wireless & Networks ---> Mobile Nets --> Use 2G. I know, defeats purpose of having 4g, but it works fine for email and IM.
Bluetooth issue:
Bluetooth disconnects and doesn't reconnect. Only way to resolve is to power cycle phone. Sometimes it would indicate that it was connected where it wasn't. Multiple folks have the same issue. Doesn't seem to matter whether it's a headset or car bluetooth.. same issue.
crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
Wish I had the time to get into the ROMs. Don't know how you guys do it..
Returned the original G2x today and got another. Well, bluetooth is jacked on this one also. You know, I shouldn't have to be messing with this damn thing I paid $300 for. It should work.. The right thing for T-Mobile to do is recall the G2x and replace it the new dual core nexus for affected users. This phone is a piece of shyte.
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
jlevy73 said:
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
Click to expand...
Click to collapse
I have a Blueant Q2 that collects dust because it is useless trying reconnect it every time it disconnects (far too often) while I'm driving, what's the point? Bluetooth is a fail on the G2X.
So the damn bt issue is still not resolved.
Sent from my Sensation using xda premium
ICS fixes the BT issue... but how? And can it be done for previous versions too?
I have tried the ICS CM9 and it seems to fix this BT issue. Not sure how it happens. Can one of the developers comment and maybe implement the fix in their ROM as well?
crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
It works in the SK ICS builds.
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
mansa_noob said:
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
Click to expand...
Click to collapse
Wow you dug up deep for this. I believe this is the time we didn't have a2dp on cm roms
Sent from my LG-P999 using xda premium
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
SovereignKnight said:
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
Click to expand...
Click to collapse
check the irl too?
No haven't done that. Not sure how you mess with the irl. I know it has something to do with baseband. But I don't think it has anything to do with Bluetooth?
Hello all!
I am a noob on here so if this has been asked or brought up before please forgive me. I couldn't find any info on this issue. After installing 2.3.4 on my sensation (I am running stock out of the box) I notice when I connect the phone to wifi and use wifi calling that when I use the speaker phone on my phone, the person on the other end can no longer hear me. The person just says hello over and over and totally cuts off the mic on my phone. When I enter it back to the regular headset, it continues to be cut off. When I try troubleshooting the issue I connected to the t mobile network it works just fine. Only when I use the wifi calling feature does this happen. Does this happen to anyone else? Is this a known bug? I did a battery pull and this did not fix the problem. Any suggestion or feed back would be much appreciated. Thank you everyone!
Not one person is having this issue? Can anyone help out there? At least let me know if it is a known issue. I know the speaker phone is terrible but I'm only trying to find out if there is a fix for this.
Thanks!
HTC Sensation Speakerphone does not work on WIFI
I am having the same issue. Speakerphone does not work over Wifi. Person on the other end cannot hear me and I often cannot hear them. When I am not using Wifi, speakerphone works fine. Version 2.3.4 seemed to improve speakerphone volume, but it still does not work over Wifi. I contacted HTC tech support and they said while they were unaware of the problem, but it is possible that it exists. They said they would investigate. We will see. Not sure whether the HTC Amaze has the same problem.
I had the same issue till I S-offed and flashed a new ROM. I think it's something with TMO's factory ROM they have the speaker function turned way down and my first Sensation would do just what urs is.
Rec: Unlock (S-off) and flash a new ROM (I personally am running CoreDroid 2.4)
I'm on ARHD 3.6.2 and non speaker phone works ok, but on speaker I've been told its hard to hear.
I am also having a same issue. I've opened up a ticket with t-mobile. T-mobile techs are looking into this issue. Yesterday I went to the store from which I purchased my sensations and showed them the issue. We tested the issue with other HTC android devices but only sensation is having this Issue.
I noticed this problem a couple months ago, and am surprised there hasn't been a software update to fix it. In the meantime, I just shut off wifi if I expect to make a phone call using the speaker phone, which is somewhat annoying.
Hi everyone, I hope I am not wasting your time with this question but I have just gone out and bought a Q2 Blueant headset and I have a HTC desire HD, on the side of the box it says it works with android and the guy at the shop said it works great..........the thing is if I say phone commands it says this phone is not supported, I have installed Vlingo and it does not pick up on my voice unless i speak into the phone and it just does not want to use the headset even though in the box the headset comes with says to use Vlingo with it!!! I don't get it!!
I have made sure the voicedialer.apk works and it does but not through the headset either, is there something I am missing? its driving me up the wall!!
Cheers for any help everyone.
If anyone can help at all it would be awesome, the people at vlingo are just emailing me what info they have on their site even though I asked them not to do that.....probably why they are doing it and blueant still won't get back to me. Someone else has to have tried to use Bluetooth.....
Sent from my Desire HD using XDA App
Have you downloaded the blueant app? I have the Q1 and the T1 and they both work without issue. Also are you on a custom rom?
Thanks for the reply,
Yeah I have tried 2 custom roms now android revolution and core droid, I just want the headset to do more than answer and decline calls, I want full hands free feature with this thing, I have already gotten a $350 fine for using my phone so I bought the q2 which says it does all this and then when I say phone commands into the headset it just says this phone is not supported, I have gone through all the settings I can think of and nothing!
If there is a Rom you know of that will work perfect then Ill install that, I don't care what rom I am using I just want to be able to do my work while driving and any email I send to blueant or vlingo gets me nowhere.
EDIT: Yeah I downloaded the blueant app, it has done nothing for me unfortunately
v0lley said:
Thanks for the reply,
Yeah I have tried 2 custom roms now android revolution and core droid, I just want the headset to do more than answer and decline calls, I want full hands free feature with this thing, I have already gotten a $350 fine for using my phone so I bought the q2 which says it does all this and then when I say phone commands into the headset it just says this phone is not supported, I have gone through all the settings I can think of and nothing!
If there is a Rom you know of that will work perfect then Ill install that, I don't care what rom I am using I just want to be able to do my work while driving and any email I send to blueant or vlingo gets me nowhere.
EDIT: Yeah I downloaded the blueant app, it has done nothing for me unfortunately
Click to expand...
Click to collapse
Not real sure to be honest. I use it only for phone calls. I don't even have it read texts as that can be trouble causing. One of the main issues that when the screen is locked nothing will work till it is unlocked. What you are wanting may not be possible at the present time. Ill test a few things out on my end and see what I can find. But no promises
Cheers mate,
Ill be interested to know if yours works.
I did just get this email from Vlingo also.
"Hello
Thank you for contacting Vlingo Customer Support.
Our most recent 3.5 patch seems to have corrupted Vlingo's Bluetooth compatibility. We are currently investigating this matter and work to reproduce the issue you have reported to us. I regret that I am unable to provide you with a concise solution to resolve this matter at this time. Nonetheless, please be aware that our QA engineers are aware of the problem and will be testing to identify the issue. We hope to resolve the problem in a timely manner. If we are able to repair the issue, we will deploy the fix in a future version release.
We appreciate you brining this issue to our attention and apologize that our recent 3.5 build has caused issues with Bluetooth. Please let us know if you have any questions or concerns.
Best regards,"
But why my headset says my phone is not supported I still don't know.
One of the biggest issues I have found is the lock screen. Once locked it doesn't allow any commands untilled unlocked.
That wont bother me too much, when im in the car its connected to USB and it will be unlocked most of the time.
i have a headset that i want to pair with my Charge, but for some reason when i try to pair it, it keeps telling me that the device returned a code that was incorrect,
first off the headset has no method of input, and second the phone never asked for a code, ive searched everywhere and cant find answers just people with the same issue that just decide to give up and get a new headset.
the Issue was there since EE4 (the version my phone had when i purchased it at the VZ store)
I now have EP4 with tweakstock, tried it with stock rom and still same issue
I know that the 2.1 should automatically exchange the codes is there a way to manually put in the code to the charge?
the head set works fine on a flip phone my brother uses, and im not sure if this is specific to the droid charge, or if this is Android in general as i dont have any way to test it.
any suggestions other than "buy a new one" would be great
oh come on! anyone?
See if another, newer headset has the same problem. If it happens again, it's the phone's bluetooth. If it pairs successfully then it's just an incompatible headset.
Really, there's no other way of testing. Just because one headset works with one phone, doesn't mean it'll work with another, but this isn't a common problem since Bluetooth headsets are mostly universal.
Sent from my SCH-I510 using xda premium