I have performed several searches on this subject. I have asked several times. It seems either nobody knows the answer, nobody cares to answer, or else my question is so simple it comes across as a newbie question.
Anyway, here I go again.
A couple of months ago I replaced my EVO's ROM with RUU SuperSonic EvO 3.70.651.1 OTA - Stock - Sense. This was supposedly a rooted version of the last (pre 2.3) OTA.
Everything worked fine.
I then decided to update my radios because newer is always better
At first, everything seemed to work fine, but after a while I discovered my Bluetooth earpieces kept dis-connecting. I have two earpieces, both the same model (Original Jawbone). What happens is I'll be in a call, and all of a sudden the earpiece will disconnect. The only way to reconnect is to go into settings on my phone, turn off Bluetooth, turn it back on, and reconnect.
The current issue started with BOTH earpieces at the same time, after I flashed my phone's radios.
It is obviously software related. I am wondering if I can simply flash whichever piece of software that controls the Bluetooth radio, and if not, where can I find all the EVO radio versions so I can flash each one until Ifind one that works?
Or is it likely that I will need to flash the ROM to fix this issue?
Thanks.
I don't have an answer, but can confirm that I have a similar problem with my HTC Desire (CDMA) & Motorola H17txt headset. The only difference is, I haven't flashed anything (although rooted & S-OFF). I'm on my 4th headset, all with the same random disconnect of the earpiece. The first 3 turned out to be cheap Chinese knockoffs of the real thing, so I finally purchased directly from Motorola, same problem and a little worse.
I've searched everywhere online, and found others with similar issues, albeit in much older dead threads, but never any solutions offered. I'm convinced the problem is in the phone as you stated. I'll be interested to see if any solutions surface here on XDA-Dev.
US Cellular HTC Desire Stock ROM
Rooted, S-Off
Related
Hello everyone,
I have the latest AT&T 6.1 ROM, downloaded from the HTC site for the Tilt. Here's a couple of problems that I have, that I can't get search results for.
1. VERY often, when a person calls me and I answer, I can't hear anyone on the other end! The same results when I make an outbound call as well. The device says that I'm connected to the other party, but I can't hear that.
2. When I AM actively connected, VERY often my bluetooth headset will just DECIDE to disconnect! Now, the DEVICE is still connected, but I have to either quickly put it to my ear to not miss what the other party is saying, or, I've noticed that if I push the multifunction button on the earpiece (Jawbone), it will reconnect.
Any help with these two issues would be appreciated. This has ONLY begun since I've installed the newest AT&T 6.1 ROM, which is supposed to be for the Tilt... which I have.
I'm REALLY frustrated...
Maybe try the original 6.0 rom and see if it still happens. If it does, and your phone is under a year, I would definitely send your phone in for warranty.
Jason
i have 3 words for you,
1-radio
2-radio
3-radio..................
try changing your radio and see if the problem persists, but i smell a radio problem behind all of this
maiahsdad said:
Hello everyone,
I have the latest AT&T 6.1 ROM, downloaded from the HTC site for the Tilt. Here's a couple of problems that I have, that I can't get search results for.
1. VERY often, when a person calls me and I answer, I can't hear anyone on the other end! The same results when I make an outbound call as well. The device says that I'm connected to the other party, but I can't hear that.
2. When I AM actively connected, VERY often my bluetooth headset will just DECIDE to disconnect! Now, the DEVICE is still connected, but I have to either quickly put it to my ear to not miss what the other party is saying, or, I've noticed that if I push the multifunction button on the earpiece (Jawbone), it will reconnect.
Any help with these two issues would be appreciated. This has ONLY begun since I've installed the newest AT&T 6.1 ROM, which is supposed to be for the Tilt... which I have.
I'm REALLY frustrated...
Click to expand...
Click to collapse
did you do a hard reset? if not try that and see if that helps
Without a doubt an issue with your radio version. I had the same issues when I switched from WM6 to 6.1 - turned out my radio only worked w/ version 6 and caused my phone to only work half of the time.
SilverVenom said:
Without a doubt an issue with your radio version. I had the same issues when I switched from WM6 to 6.1 - turned out my radio only worked w/ version 6 and caused my phone to only work half of the time.
Click to expand...
Click to collapse
You are Switching from a 6.0 to 6.1...it probably is a radio issue...just go to the ultimate radio thread in my signature and download a 6.1 radio and try it....it will only take a few seconds
the stock wm6.1 at&t rom that he loaded comes with a functional radio made for that rom so unless he flashed a radio that is for wm6 after he updated then yes its the radio
looks like Radio problem.. but if you install the ATT official rom you have allready one for 6.1 windows.. Like already say MSD24200
but try one from here:
http://forum.xda-developers.com/showthread.php?t=393182
i prefer the 1.65.24.36 NIKI Radio
you must select one of 1.65.xx.xx or 1.70.xx.xx
Comm Manager?
b16b said:
looks like Radio problem.. but if you install the ATT official rom you have allready one for 6.1 windows.. Like already say MSD24200
but try one from here:
http://forum.xda-developers.com/showthread.php?t=393182
i prefer the 1.65.24.36 NIKI Radio
you must select one of 1.65.xx.xx or 1.70.xx.xx
Click to expand...
Click to collapse
Bob,
I using the eOS 4.888 ROM on AT&T and I have the "silent call" issue too. It seems to have come up only in the past month or so. I'm on my 4th radio, currently a Polaris 1.59.42.23. The Polaris Radio seems to make the problem less frequent, but it is still there. My first though was this is an AT&T issue but there is a thread in the Kaiser General section about this, and posts in the Ultimate Radio thread that indicate the issue is occurring outside of the AT&T network as well.
The issue has been blamed on radios, ROM, and bluetooth, but in my experience with it, I'm thinking it might be Comm Manager related, but I don't know enough to know how the Comm Manager interacts with the radio/ROM to really be helpful.
I do know that the person who figures out the answer to this problem will make quite a few folks on this board very happy!!
Jim
Same Issue
I am having the same issue. I have the official 6.1 ROM from HTC on the att tilt. I flashed it on a friday and did not notice issues with not hearing the person on the other end when connected until a few days later. I looked at the ultimate radio thread according to that, I have the correct radio for my rom version:
ROM version: 3.57.502.2 WWE
ROM date: 07/17/08
Radio version: 1.65.21.18
Protocol version: 25.88.40.05H
Could it still be a radio issue? Or something else?
jpcrailjr said:
Bob,
I using the eOS 4.888 ROM on AT&T and I have the "silent call" issue too. It seems to have come up only in the past month or so. I'm on my 4th radio, currently a Polaris 1.59.42.23. The Polaris Radio seems to make the problem less frequent, but it is still there. My first though was this is an AT&T issue but there is a thread in the Kaiser General section about this, and posts in the Ultimate Radio thread that indicate the issue is occurring outside of the AT&T network as well.
The issue has been blamed on radios, ROM, and bluetooth, but in my experience with it, I'm thinking it might be Comm Manager related, but I don't know enough to know how the Comm Manager interacts with the radio/ROM to really be helpful.
I do know that the person who figures out the answer to this problem will make quite a few folks on this board very happy!!
Jim
Click to expand...
Click to collapse
It is not Comm mgr related as I have tried several to no avail, Also several 6.1 roms and several radios . No luck.
Hopefully a mod can combine this thread with this one http://forum.xda-developers.com/showthread.php?t=438457 so we can all work on this together.
Can't hear other party......
Did anyone find a solution to this yet? I have flashed all the compatable rabios with the tilt running the official wm6.1 from htc. And I am still making and receiving calls with not being able to hear the other party(as well as them not being able to hear me).
The main function of the tilt is a PHONE!
Hard reset after flash maybe?
kaisernewb said:
Did anyone find a solution to this yet? I have flashed all the compatable rabios with the tilt running the official wm6.1 from htc. And I am still making and receiving calls with not being able to hear the other party(as well as them not being able to hear me).
The main function of the tilt is a PHONE!
Click to expand...
Click to collapse
It has to do with 6.1 . We are trying to pool all our information on one thread
http://forum.xda-developers.com/showthread.php?t=438457
Nika has reflashed to a 6.0 rom, and that appears to have eliminated the problem.
Again, if a Mod could merge these threads, we could all work togther on this.
Thanks.
kaisernewb said:
Did anyone find a solution to this yet? I have flashed all the compatable rabios with the tilt running the official wm6.1 from htc. And I am still making and receiving calls with not being able to hear the other party(as well as them not being able to hear me).
The main function of the tilt is a PHONE!
Click to expand...
Click to collapse
If it is not radio, then it is a connection issue with your USB port. I had this happen to me and frustrated the heck out of me until I discovered that the tether that is inside the USB port on the device was loose, as if it was cracked. I must have done that while jabbing the stylus in it without using my glasses to soft reset. I discovered the issue by accident when the phone was plugged to be charged and i received a phone call. every time i wiggled the phone the conversation sound would get muted or interrupted. I ended up returning the Tilt to AT&T as a defective device and got a refurbished one that works. Test it and let us know.
We switched from T-Mobile to ATT and got 2 Inspire 4g's and one Infuse.
Now my wife is hating her Inspire because she says the call quality is terrible. She can barely understand the person she is talking to, and if she turns the volume up it gets worse and worse.
She does not think it is the ATT network because it happens no matter where she is, and is not sudden or sporadic. She says it is every call all the time.
Any ideas before we take the 2 Inspires back?
You have a couple of options. The first would be to divorce her. (Just kidding.) The call quality is good on these phones. It is possible that you may have received a defective unit. The second option would be to exchange the phone for another and check the quality on the second unit, which is what I would recommend you try. It should not be happening on every call. There is nothing you could really try until you root your phone and test different fixes, but you should not need anything right now on a phone you have not changed yet.
I am in agreeance with the above poster, it sounds like you may have a defective handset, in all likelihood you should be able to exchange it, sooner than later and see if it works better. The other issue could be your area just has horrendous service for AT&T as that can happen as well.
Thanks guys, I agree we need to exchange it sooner than later, I am just worried because both Inspires we have have the same issue. I dont think it is the service because my Infuse is fine, and we have an iPhone 3gs that is fine in the same areas.
If both Inspires have the same issue it is possible they may have come from a bad batch. It is known to have very good call quality, and on certain roms you just have to apply a patch to fix sound issues. Normally, HTC build quality surpasses Samsung build quality. It may be worth it to go to a different store and try an exchange there to see how that goes. If your Infuse is working well, so should the Inspires.
Wolf_2 said:
If both Inspires have the same issue it is possible they may have come from a bad batch. It is known to have very good call quality, and on certain roms you just have to apply a patch to fix sound issues. Normally, HTC build quality surpasses Samsung build quality. It may be worth it to go to a different store and try an exchange there to see how that goes. If your Infuse is working well, so should the Inspires.
Click to expand...
Click to collapse
Well just because my son really likes his Inspire I went ahead and rooted his and installed the Android Revolution HD ROM. Here is what I tested/noticed:
With the downgraded ROM that is installed during the Rooting process the problem remains, and I was unable to use wifi. It would connect to the wifi, but could not browse the internet.
Once I installed Android Revolution HD I could connect and wifi was fine, but the phone signal was weak. So I installed the linked radio from the first page of the ROM and it went back to a strong signal, but not really any different than stock.
I am convinced that the issue is the radio, not the physical device, so I think I just need to find the right one.
If you are using the M2 radio that is recommended for the AR rom, then you should already have the correct Ril files that match that radio because they are included in the rom. The downgrade rom that is used during rooting needs to have a newer radio flashed in order to get it working. If you are getting any kind of tinny audio quality then there is a patch in the first post that fixes sound quality issues that a lot of people get. These patches are used for most of the European based DHD roms.
sgrant said:
Well just because my son really likes his Inspire I went ahead and rooted his and installed the Android Revolution HD ROM. Here is what I tested/noticed:
With the downgraded ROM that is installed during the Rooting process the problem remains, and I was unable to use wifi. It would connect to the wifi, but could not browse the internet.
Once I installed Android Revolution HD I could connect and wifi was fine, but the phone signal was weak. So I installed the linked radio from the first page of the ROM and it went back to a strong signal, but not really any different than stock.
I am convinced that the issue is the radio, not the physical device, so I think I just need to find the right one.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1106324
I have owned many AT&T phones, and the Inspire has one of the best sounding calls I have ever had. I would agree that it is probably a bad batch of phones, or something damaged the phones when they were shipped to the store. I have rooted/M2 Radio, and am running LeeDrOiD. This is by far the best phone I have owned. I am sorry that your wife is having issues, but i would definately try exchanging it for another Inspire before giving up.
i have no problems with call quality except for speaker
when i put phone on speaker the other end could never hear me
i would suggest putting ur sons phone back to stock, and taking them both to ATT and reproduce the issue for one of the reps and say see listen the phone sounds like total crap please fix this and have them replace both phones. do not leave the store until both of ur phones are working correctly
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.
I have a Verizon htc trophy. On monday I tried to activate bluetooth for the first time in a few weeks or so. I turn the status to on, it searches, doesn't find anything and then kicks back to status off. I've tried this with 4 or 5 different bluetooth devices.
I've scoured the internet and this forum with every search term I could think of with no luck or even mention of a similar problem.
Notes:
I updated to mango beta through the windows phone developer portal when it was made available. I'm pretty sure I was able to use bluetooth at some point with that os, but can't be sure. I updated to the newly available leaked 7720 last night hoping it would fix the bluetooth issue, but it still persists.
No other problems with the phone, and I haven't dropped it or anything. I do however use it to track my runs, and enough sweat has gotten into it to start to change the water damage stickers.
Wich devices did u want to connect?
This phone can´t connect with other phones, just with a few bluetooth-car-kits
and somethig like that!
I've now tried with a laptop, desktop, a cheapy noisehush bluetooth headset, a motorola s9-hd and also a motorola s10... Pretty sure all of which I have been able to connect with before (certain on the s9-hd and noisehush headset).
Any thoughts? This is a pretty limiting problem, especially since my state has banned the use of cellphones while driving.
I'm pretty close to opening the thing up and seeing if one of the Bluetooth antenna wires has popped off its connection maybe.
Anybody want to take a final stab at this question before I tear into my phone?
hi,
I have exact the same issue with my HD2. I have 7720 running. With 7392 it worked fine.
regards Coolity
It's possible there is an HTC driver needed to access the Bluetooth radio on the Trophy that is not on the Beta or RTM but would be on the final Mango roll-out ROM for this phone. All I can suggest is try to load the leaked VZW Trophy Mango ROM (but you can't unlock since it wipes the phone) or wait for VZW to roll out Mango for this phone.
Thanks for the responses. I have installed this version of Mango:
http://forum.xda-developers.com/showthread.php?t=1254384
which I'm pretty sure is as final as it gets. I did notice one thing, however. The firmware version seen here is 2305.13.20198.6 something, mine is 2305.13.20104.605.
Maybe this is the reason? All other revision numbers are the same, including the OS version in that picture.
This just in....
I also don't have regular fm radio. It's stuck loading (on 4 minutes now) with no moving forward.
Anybody else having these problems? Tried FM radio with the HTC shipped earbuds and it is still stuck on loading. The bluetooth is still experiencing the same problems.
I've tried to use the leaked htc verizon rom again but am not able to re-flash using the same steps as before.
I opened up the phone and looked around and it appeared that everything looked ok. no burn/oxidation marks anywhere.
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.