Hello,
I saw no recent posts on this but was wanting to check in.
Just curious if anyone else is having the problem with static and disconnecting of bluetooth on their device post ICS leak?
I have the original verision on yet and waiting on replacement headset and wanted to update .3 verision to see how that works.
My friend is still on stock 2.3 and having alot of range issues also was curious.
I think if that does work that may also help me to convert him to root lol
I'm on the ICS leak. I was using my bluetooth and the person on the other end said it sounded horrible, and said it sounded like it was really windy out. It wasn't, it was calm. I'm not sure if this is a BT earpeice problem, phone problem, ICS problem or what.
Range is not good. When I get out of my truck on a traffic stop and am at the violators car, with my phone in the truck, my BT beeps in my ear. I'm not really *that* far away from the phone.
RobsSXT said:
I'm on the ICS leak. I was using my bluetooth and the person on the other end said it sounded horrible, and said it sounded like it was really windy out. It wasn't, it was calm. I'm not sure if this is a BT earpeice problem, phone problem, ICS problem or what.
Range is not good. When I get out of my truck on a traffic stop and am at the violators car, with my phone in the truck, my BT beeps in my ear. I'm not really *that* far away from the phone.
Click to expand...
Click to collapse
My bluetooth is having the same issues. It disconnects for no reason and even with the phone in my pocket or sitting next to me in the car. One time this weekend I was talking to someone and in the middle of the conversation it just disconnected. After grabing my phone sitting less that 2 feet from me and putting it up to my ear, it reconnected itself. I have not tried the most recent leak and am on Energy's ICS leak ROM. Was hoping NRGZ would update his ROM to latest leak so I can try it and see if the probldem corrects itself or not.
I don't know about the ICS leak or even what the official will bring, but on stock 2.3.4 the range is pretty terrible.
It has been said quite often that the Amazes BT range is pretty bad. I actually agree. I can sometimes walk a few feet away and it dies out. Good thing I don't rely on BT much as anytime I do use it, I am close to my phone. I can see how it would bother others to where they can't use their phone with them close by.
I personally don't think any ROM will fix it, just believe it is unfortunately a phone issue.
Sent from my HTC_Amaze_4G using Tapatalk 2
Wrong section. Please keep all question/help related threads in the Q&A section. Thank You.
Thread Moved.
"if you choose not to decide, you still have made a choice" ~N.P. Rush
Brought to you courtesy of my Galaxy Note (i717), using XDA Premiero!
Same issue
Same here. When in my car using the amaze, the other end of the line claims that it sounds like I'm in a windstorm. Is the no fix to this yet?
Related
I have noticed that when I record video with the Thunderbolt that the picture quality is out of this world but the sound quality is terrible at best. I can barely hear my TV playing just 6 or 7 feet away from me. Anyone else have this problem?
I am running Infected ROM but have had this problem since it came out of the box.
Also, I was wondering, if I called VErizon support on this, could they tell that I had my phone rooted just by being on the phone with them?
This issue has been discussed on xda as well as a few other forums (htcs own community as well). I havent found an explanation or anything that fixes it unfortunately. I'm kinda upset about this since I'm constantly taking videos on my phone.
Sent from my ADR6400L using XDA App
sm0k3y-TB said:
I have noticed that when I record video with the Thunderbolt that the picture quality is out of this world but the sound quality is terrible at best. I can barely hear my TV playing just 6 or 7 feet away from me. Anyone else have this problem?
I am running Infected ROM but have had this problem since it came out of the box.
Also, I was wondering, if I called VErizon support on this, could they tell that I had my phone rooted just by being on the phone with them?
Click to expand...
Click to collapse
They don't know you're rooted. I exchanged my Moto droid 4 times, it was rooted each time. I often called them and they would just send me another. The buttons kept going bad on my phones. Bad luck I guess.
It uses the mic at the bottom of the phone (same one for phone calls) so make sure you're not covering that up. And it seems that unless whatever you're recording is close, you'll have issues. There was a post somewhere from someone who contacted HTC and was told it was due to the noise cancelling software
Well at least if its software related maybe it can be fixed in the first update. It's a shame to have such great video quality with such horrendous sound.
PJnc284 said:
It uses the mic at the bottom of the phone (same one for phone calls) so make sure you're not covering that up. And it seems that unless whatever you're recording is close, you'll have issues. There was a post somewhere from someone who contacted HTC and was told it was due to the noise cancelling software
Click to expand...
Click to collapse
ignore what I posted, I am tired and that was stupid lol.
hello, I am running the current public release at the time of this post(v1.1). I have a Jabra SP700 bluetooth FM speaker for my car. I am uncertain if this is a fault of the rom or the hardware of my bluetooth speaker. I am leaning more towards the bluetooth but I figured I would ask the community.
I play music through this to my car stereo. Frequently the bluetooth drops the audio connection at random times. The phone and speaker say the X2 is connected, but the audio ceases. Within a minute the sound will play through the phone speaker not the bluetooth. Then the bluetooth will say "disconnected" and begin searching to reconnect. My X2 will state the bluetooth is still connected. In order for me to get the phone connected, I need to power off the bluetooth then disable and reenable bluetooth on the X2.
I believe this has happened with previous versions, ive been using eclipse since it started. Although I cannot remember if it works correctly with the bluetooth bone stock.
I am leaning towards the bluetooth since the bluetooth is about 2 years old now...but I was wondering if anybody used a similar bluetooth piece and experienced similar issues. Thanks!!
Ok guys. Let's try this thread over.
Anyone want to help this gentleman? We're not going to argue or derail. If you can't help this guy, don't respond.
OP, search while you wait for an answer.
There is a known issue with the bluetooth function on 1.1
I had heard people saying that with the newest ((1.2rc3)) that the issue had been fixed.
I don't use bluetooth do I cannot confirm but that might be the issue
I didn't think that older BTdevices would become "obsolete" . I thought any newer phones that support bluetooth would encompass all older BTdevices not exclude them. I can see an older phone not connecting to newer bluetooth but not older bluetooth not connect to newer phone.
Nitro tweeted that the new eclipse final should be out tomorrow. Hr has known about the bluetooth bug for a while so I am sure it was a priority fix.
It is possible tho that there is something faulty with your bluetooth device. Have you tried contacting the manufacturers of it to see if that is a known problem with that device? They may be able to help troubleshoot it also.
Thanks ash. As usual you are helpful and nice the speaker is way out of warranty. Ive owned it for 2 years. The battery os startong to go too. I never doubted the compatibility of the speaker...just the performance. It has acted odd in the past. I did not notice an issue initially with the X2. Since it started acting up i was pretty sure it was the bluetooth just showing its age and starting to malfunction. Well at least i do not have to buy anothee speaker just yet
Sent from my DROID X2 using XDA App
Thanks
Even if it is out pf warranty they may be the type of company who is willing to repair or help with problems just to keep your loyalty to their products. Who knows you may be able to talk them into a rebate on new product or a coupon or something . Might be worth a shot. Just be site you tell them you promote the product to people you know and in forums you post in. I have been looking for either a wired or bluetooth speaker for my x2 and not sure what to go with. . I saw one in the VZW store I
that looked nice but $199 is a bit steep for a speaker for me lol
And it seems like any other speaker I find (wired or bluetooth) is labeled do I ipod /iphone etc... im thinking the wired would work okay((headphones jack type)) but am not willing to shell out the 50$ that ill only get back in store credit for opened electronic in a store I barely shop at lol. Im sure ill find something sometime and ur post introduced me to a different one to look into. Curious if new eclipse final will fix your problems. Good luck.
Its odd that it will work for a while and then cut off. Wonder if it may be the "receiver " in the device not working correctly. Maybe something wiggled loose. Might be worth taking it apart((if possible) and checking where things connect to each other it giving it a wipe down and clean it up. Maybe dirt is interfering with something inside due to its age.
Or IT'S ALL YOUR FAULT. YOU USED IT TO MUCH FOR WHAT IT WAS DESIGNED FOR AND IT IS DEAD NOW ...lol j/k...im sure something can be done to fix it if it isn't eclipse that is causing the problem. ..its just a matter of is it worth the time to fix or buy a new one..
It is all my fault!!!! Haha. Well that is an idea....maybe i will try. If i can make a suggestion, the droid roadster is pretty cool. Works well and is user friendly! I tested it for a while and liked it.
Sent from my DROID X2 using XDA App
I have a bluetooth earpiece that I use with my old Razr and it works fine with my DX2 so I don't think age has much to do with compatibility. Wear and tear probably plays more of a factor.
I do pair my DX2 with my Touchpad (WebOS, not when booted in CM7) and I can make calls great on the TP but because the default bluetooth.dun is missing from Eclipse I can send sms with my TP. Not an issue but something to consider if you are shopping and comparing specs to see if you nifty new devices will work with your phone. The devs pull out the blur and bloat because that is what we want but it can change how devices talk to each other.
I have a set of moto rokr hd headphones that I use all the time and I have had this exact same issue with eclipse. The phone still says it has a connection but no audio is playing through my headphones. The only way to correct the issue is to turn off the headphones and turn off bluetooth on the phone and restart them both. It will happen completely at random times. Sometimes I will use them for a couple hours before it hours, but sometimes only 15 min. Its def eclipse, I don't think moto headphones have a compatability issue with a moto phone
I think this is the right forum to post. Please move if not, sorry mods.
Is anyone using an ICS ROM on their i777 with a Subaru navigation system and has Bluetooth streaming working properly? More specifically, are there any 2010+ Subaru Outback w/ Navigation users using ICS and having Bluetooth streaming working correctly?
If so, what year/model is your car? And what ROM/kernel are you using?
Mine works flawlessly in GB, but in any ICS ROM, streaming will start for a couple ms, you'll hear a fragment of the song, then it will pause for a second. My logs are showing a buffer issue in the BT stack. Is anyone else having the same problem?
I might have some time to get to the bottom of it, but if someone else has it working I'd like to hear that too.
I have Subaru BT audio disconnect issues also.
The disconnects happened with deep sleep on ICS, Shostock2 and AOKP roms.
I have found that keeping the charge cord plugged in will prevent deep sleep and avoid the disconnect.
My thread on this from a few months back
http://forum.xda-developers.com/showthread.php?t=1609686
Someone else posted a thread yesterday that was moved to Q+A about the same issues.
He claimed to avoid BT disconnects on CM9.
Subaru and Audi owners are the biggest groups complaining, so their BT stuff must be a little different from most.
I am using Tasker on Shostock2 to avoid the issue as posted in my thread.
daverup said:
I have Subaru BT audio disconnect issues also.
The disconnects happened with deep sleep on ICS, Shostock2 and AOKP roms.
I have found that keeping the charge cord plugged in will prevent deep sleep and avoid the disconnect.
My thread on this from a few months back
http://forum.xda-developers.com/showthread.php?t=1609686
Someone else posted a thread yesterday that was moved to Q+A about the same issues.
He claimed to avoid BT disconnects on CM9.
Subaru and Audi owners are the biggest groups complaining, so their BT stuff must be a little different from most.
I am using Tasker on Shostock2 to avoid the issue as posted in my thread.
Click to expand...
Click to collapse
This is different than the disconnect issue. This is a constant stutter. Basically, you hit play, you hear a couple ms of your track, then silence, repeat ad nauseum. During this, you see the head unit and phone flip from PLAY to PAUSE repeatedly. logcat shows a buffer issue in the bluetooth stack.
If you pause, then hit play, and repeat that for a while, it sometimes begins to function normally for the remainder of the BT connection. But the issue is ALWAYS present when first starting to play from a fresh BT connection.
My Subaru HU is made by Kenwood. That's why I asked for other similar models/years, since I could at least then do some research on what model Nav unit was being installed and figure something out from there. Unfortunately I don't know about Audis or I'd try to help there too.
sjwaste said:
This is different than the disconnect issue. This is a constant stutter. Basically, you hit play, you hear a couple ms of your track, then silence, repeat ad nauseum. During this, you see the head unit and phone flip from PLAY to PAUSE repeatedly. logcat shows a buffer issue in the bluetooth stack.
If you pause, then hit play, and repeat that for a while, it sometimes begins to function normally for the remainder of the BT connection. But the issue is ALWAYS present when first starting to play from a fresh BT connection.
My Subaru HU is made by Kenwood. That's why I asked for other similar models/years, since I could at least then do some research on what model Nav unit was being installed and figure something out from there. Unfortunately I don't know about Audis or I'd try to help there too.
Click to expand...
Click to collapse
Ok, I think the Subaru radio CD on my car was made by Clarion.
Definitely problems with the BT software somewhere.
Good luck
daverup said:
Ok, I think the Subaru radio CD on my car was made by Clarion.
Definitely problems with the BT software somewhere.
Good luck
Click to expand...
Click to collapse
Thanks! What model/year is your car, just so I can exclude from trying to find working examples?
sjwaste said:
This is different than the disconnect issue. This is a constant stutter. Basically, you hit play, you hear a couple ms of your track, then silence, repeat ad nauseum. During this, you see the head unit and phone flip from PLAY to PAUSE repeatedly. logcat shows a buffer issue in the bluetooth stack.
If you pause, then hit play, and repeat that for a while, it sometimes begins to function normally for the remainder of the BT connection. But the issue is ALWAYS present when first starting to play from a fresh BT connection.
My Subaru HU is made by Kenwood. That's why I asked for other similar models/years, since I could at least then do some research on what model Nav unit was being installed and figure something out from there. Unfortunately I don't know about Audis or I'd try to help there too.
Click to expand...
Click to collapse
I have the same issue with the wifes' seinna. Thankfully I rarely drive it
T
tedkunich said:
I have the same issue with the wifes' seinna. Thankfully I rarely drive it
T
Click to expand...
Click to collapse
What year? And did you have that issue with a GB ROM, or only ICS?
I have the same bluetooth stutter issue with my 2011 Prius. I am running the stock ics rom. I would be very interested in hearing about an ics rom that does not have this problem.
sjwaste said:
What year? And did you have that issue with a GB ROM, or only ICS?
Click to expand...
Click to collapse
It is a '12 model. Been on AOKP since before getting it so I have no experience with GB and the toyota.
T
Sent from my Liberty using XDA App
sjwaste said:
Thanks! What model/year is your car, just so I can exclude from trying to find working examples?
Click to expand...
Click to collapse
2011 Impreza. No stutter, just deep sleep disconnects
PeterY125 said:
I have the same bluetooth stutter issue with my 2011 Prius. I am running the stock ics rom. I would be very interested in hearing about an ics rom that does not have this problem.
Click to expand...
Click to collapse
Seemed to work on seridipity 9 from mikeymike. It is missing the volume up/down for changing tracks, so it is a deal breaker for me. He did a great job of de-touchwizing it.
T
Sent from my Liberty using XDA App
My wife is running ShoStock2 3.0.4, and is experiencing dropped bluetooth connection on phone calls in her '12 Outback. I suspect it is due to the phone going into deep sleep, as she tried changing her screen timeout to keep the phone awake, and didn't get dropped calls. As with everyone else, waking the screen will re-establish the BT connection and the call will continue.
Prior to this issue coming up and digging into it, I didn't realize these phones would go into deep sleep while on a call, so that was an interesting piece of info for me.
Guess it's time for her to get tasker and learn how to use it.
Thanks for all the input/advice here on how to work around this guys!
DD
dandrumheller said:
My wife is running ShoStock2 3.0.4, and is experiencing dropped bluetooth connection on phone calls in her '12 Outback. I suspect it is due to the phone going into deep sleep, as she tried changing her screen timeout to keep the phone awake, and didn't get dropped calls. As with everyone else, waking the screen will re-establish the BT connection and the call will continue.
Prior to this issue coming up and digging into it, I didn't realize these phones would go into deep sleep while on a call, so that was an interesting piece of info for me.
Guess it's time for her to get tasker and learn how to use it.
Thanks for all the input/advice here on how to work around this guys!
DD
Click to expand...
Click to collapse
What would be so unique about the car side that would cause the phone to timeout? I ask because I routinely have hour+ long conference calls over BT (Jabra Cuiser 2) and have never had a BT dropout - dropped calls yes (it is ATT afterall) but never a BT dropout.
T
All I want to say is Subaru FTW! Love my 03 WRX
tedkunich said:
What would be so unique about the car side that would cause the phone to timeout? I ask because I routinely have hour+ long conference calls over BT (Jabra Cuiser 2) and have never had a BT dropout - dropped calls yes (it is ATT afterall) but never a BT dropout.
T
Click to expand...
Click to collapse
Wish I knew. Hers is the only vehicle we have access to with built in BT,.so I don't have a way to test it on other setups. I'm not 100 percent positive the problem appeared after the change to an ics ROM, but I do not recall it ever happening when she was on GB. I believe, but am not certain, that the phone call over in car audio via BT is handled through an a2dp media connection with the car, rather than a more typical BT mono phone headset type of connection. I'm admittedly very unfamiliar with the specifics of BT connection stuff, so I may be talking out of my a$$ here. I do know that I've had no issues at all with my el cheapo BT headset on various ics roms...
Sent from my SGH-I777 using Tapatalk 2
1.) Has anyone with the "Bluetooth Problem" rooted their phone and found that it fixed the BT issue.
2.) Did the first OTA cause the BT problem on the Amaze.
I bought my HTC Amaze in January 2012. I didn't have my access to my Plantronic headsets at the time. Before I was able to test the Bluetooth on my Amaze, the first OTA came out. I did the update and all was good. Then my headsets came in and I tried them all (3 total -Voyager Pro HD and Explorer.) The range with the Voyager and Explorer was about 1-2 Ft. I basically had to hold the handset next to the Bluetooth headset. The Explorer had a better reception, but both headsets were distorted with the sound of static and would drop connection with a mere turn of the head. After ICS I now get about 8-10 Ft. with lots of static at anything over 3 feet.
My HD2 running CyanogenMod 7 still gets 30 ft. line of sight. And 15-20 through doors and walls.... I guess I'm spoiled.
Thanks for any answers guys.
Nope. Mine works. I have a jawbone prime. No issues with connection.
Sent From My HTC Amaze 4G Via Someone's Room
Maybe there's an issue with your BT antenna? It could be something as similar to the wifi fix (where you add a small piece of aluminum foil to the back of your case where the antenna is).
I have spent alot of time on the T-mo forum in the last few months. For the most part there seems to be a BT issue with at least "some" of the phones. When I updated to ICS the BT did without question get better. Not great.. but marked improvement. The fact that ICS made it better, along with a few posters stating that their phones BT worked fine prior to the first OTA but went bad after the update, led me to believe that the problem may be software related ...ergo the first OTA. The other people that are having this problem also saw a difference when they too updated to ICS.
One update "allegedly" messed up BT on the phone (some anyway) and another made the BT problem better. Strange....
hasoon2000 and kered424 are you guys running stock ROMs? I haven't rooted a custom ROM up to this point because I wasn't sure if it would actually fix the problem. That is why I was seeking a confimation or denial that rooting the phone would fix the problem. My dilemma is returning the phone. I have not unlocked the phone...but I did do the "Leaked ICS." But that is off topic...
I've been running stock for the longest time, but recently switched to NRG's stock-look rom. I've never had an issue with bluetooth (gb, ics, or nrg). When I was running stock, I was rooted, but I doubt rooting will fix your problem.
kered424 said:
I've been running stock for the longest time, but recently switched to NRG's stock-look rom. I've never had an issue with bluetooth (gb, ics, or nrg). When I was running stock, I was rooted, but I doubt rooting will fix your problem.
Click to expand...
Click to collapse
Thanks for you reply kered424.
I guess what I am really looking for is someone that actually recognized they had the problem and notice a change when rooting a custom ROM onto the phone. I may not find that person here...most people here root without need. I'm all about rooting...I have an HD2 that I still root (my digitizer just went out.) I just do not want to go through the hassle of rooting only to find out that it was the hardware and not the software. I would not even post about this and root the phone...if it were not for the marked impovement when I updated to "Leaked ICS."
It leaves me going: "Hardware?..software?...hardware?...software?"
From your description, it sounds like hardware. Have you tried the aluminum foil trick? That's the only thing I can think of.
Solution to Amaze 4G Bluetooth Issues. Possibly.
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
You are right...I could not find anything showing a diagram or pic of where the antenna is/are located. Hopefully somone will provide you with something. Have tried emailing HTC and outright asking for a diagram?
BlackeyedBandit said:
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
Click to expand...
Click to collapse
Still Still No Adequate Solution to Amaze 4G Bluetooth Issues.
badgerdave said:
You are right...I could not find anything showing a diagram or pic of where the antenna is/are located. Hopefully somone will provide you with something. Have tried emailing HTC and outright asking for a diagram?
Click to expand...
Click to collapse
Me too. I asked them for a service manual as I am a PC technician to let me figure it out but just like Toshiba laptops. Not a chance.
Update: Unfortunately my Bluetooth antenna mod/fix seems to only have solved the connectivity issue indoors as my headset still cuts out every few seconds outside and drops calls like crazy. I feel as though we've all been suckered by HTC as they will neither let us exchange for a smartphone that works properly or provide a solution to those of us who purchased this factory defective off the shelf phone.
I will still continue my efforts to find a way to enhance the antenna but I will probably never buy anything from HTC again seeing as how they've chosen to not deal with and dodge this widespread problem. T-mobile is no longer selling the Amaze that was the Sales person's response when I told them they were selling a defective product today at one of their stores, However, on the T-mobile website they are giving them away for free with new contracts. Those poor unfortunates that take them up on that offer who know no better.
I am going to demand a refund from either T-mobile or HTC but I doubt I will get one.
The salesman at T-mobile said "Nothing beats a wired headset." jerk!
Again I am sorry for jumping the gun but I was certain I had made a significant breakthrough in solving the Bluetooth problem on the Amaze.
BlackeyedBandit: I once read that the very first OTA is what messed up the Bluetooth on the Amaze. Unfortunately I am unable to comfirm this, or deny it. When I purchased my Amaze in Janaury 2012 my BT devices were being shipped to me. Before these devices got to me, my Amaze prompted me to do an update. I did it. When my BT devices arrived none of them had a range of more than 1-3 Ft. without static and/or terminated BT connection. When the ICS update came out the range increased to about 8-10 Ft.
I want to revert back the ROM that was first released to see if in fact it is better. But....I don't want to go through all those changes to find out it doesn't work any better. My phone is still completely stock...because I want to be able to return it soon. I love the phone and only want the BT to work in a manner that I have become accustomed to with HTC products. And to get the video stereo sound quality fixed too.
This is my second HTC device. The first was the HD2. It was a nightmare with WinMo 6.5 on it. I returned that thing 5 times and never got one that worked right. I eventually...with the help of xda members and others, learned the art of rooting. Once I got that down and rooted Andriod onto it, I was in love. I thought that even with all it's faults, HTC made an awesome device. I just needed to figure out how to "tune it up."
So I believed that the Amaze would be super awesome and looked forward to getting it. I feel let down because BT is a must for me. I'm not sure I will buy another HTC product either. This is the second time I have been burned.
BlackeyedBandit said:
Me too. I asked them for a service manual as I am a PC technician to let me figure it out but just like Toshiba laptops. Not a chance.
Update: Unfortunately my Bluetooth antenna mod/fix seems to only have solved the connectivity issue indoors as my headset still cuts out every few seconds outside and drops calls like crazy. I feel as though we've all been suckered by HTC as they will neither let us exchange for a smartphone that works properly or provide a solution to those of us who purchased this factory defective off the shelf phone.
I will still continue my efforts to find a way to enhance the antenna but I will probably never buy anything from HTC again seeing as how they've chosen to not deal with and dodge this widespread problem. T-mobile is no longer selling the Amaze that was the Sales person's response when I told them they were selling a defective product today at one of their stores, However, on the T-mobile website they are giving them away for free with new contracts. Those poor unfortunates that take them up on that offer who know no better.
I am going to demand a refund from either T-mobile or HTC but I doubt I will get one.
The salesman at T-mobile said "Nothing beats a wired headset." jerk!
Again I am sorry for jumping the gun but I was certain I had made a significant breakthrough in solving the Bluetooth problem on the Amaze.
Click to expand...
Click to collapse
This Piece of S was offered as a replacement to FIVE HTC Sensations, followed by a Samsung Galaxy S Blaze?, followed by THREE HTC Amazes...all in 11 months. WiFi doesn't work right. Bluetooth is practically useless on the Amaze, and worse when combined with WiFi. I've used it with three different high-end Bluetooth devices (Plantronics (best-I forget the name), Samsung's best, and the Motorola Sliver Elite. All work find with friends' phones when I've tried to troubleshoot. I've used several WiFi routers, access points, repeaters,etc...still the signals fluctuate, the sound warbles, and the calls get disconnected.
I have LITERALLY spent 49:25 hours on the phone with T-Mobile, and 16:30 hours on the phone with HTC. There has been no resolution. T-Mobile...offered...me...the option (get this...) to pay MORE money and get a different phone. I've spent countless hours on websites (I'm a software developer and systems integrator, so I know my way around) and was unable to get anything working. I've had to hold the phone...in my hand...about 1-2ft from my Bluetooth devices to get them to work at all.
The device is FULL of known issues. Bluetooth & WiFi being the only ones about which I care.
I've also gone back to the T-Mobile store twice (which dialing 611 or the 800-number tells you not to do...but after the HTC Sensation, and then the HTC Amaze issues, I had to choice but to go to the face-to-face supervisors and beg for help.) The first supervisor left T-Mobile and the second one "Jodi" was INCREDIBLY rude to me.
T-Mobile's 611/800-number "customer service" has three times not documented anything - and I was on the phone for 1:30 hours/each.
notperse said:
This Piece of S was offered as a replacement to FIVE HTC Sensations, followed by a Samsung Galaxy S Blaze?, followed by THREE HTC Amazes...all in 11 months. WiFi doesn't work right. Bluetooth is practically useless on the Amaze, and worse when combined with WiFi. I've used it with three different high-end Bluetooth devices (Plantronics (best-I forget the name), Samsung's best, and the Motorola Sliver Elite. All work find with friends' phones when I've tried to troubleshoot. I've used several WiFi routers, access points, repeaters,etc...still the signals fluctuate, the sound warbles, and the calls get disconnected.
I have LITERALLY spent 49:25 hours on the phone with T-Mobile, and 16:30 hours on the phone with HTC. There has been no resolution. T-Mobile...offered...me...the option (get this...) to pay MORE money and get a different phone. I've spent countless hours on websites (I'm a software developer and systems integrator, so I know my way around) and was unable to get anything working. I've had to hold the phone...in my hand...about 1-2ft from my Bluetooth devices to get them to work at all.
The device is FULL of known issues. Bluetooth & WiFi being the only ones about which I care.
I've also gone back to the T-Mobile store twice (which dialing 611 or the 800-number tells you not to do...but after the HTC Sensation, and then the HTC Amaze issues, I had to choice but to go to the face-to-face supervisors and beg for help.) The first supervisor left T-Mobile and the second one "Jodi" was INCREDIBLY rude to me.
T-Mobile's 611/800-number "customer service" has three times not documented anything - and I was on the phone for 1:30 hours/each.
Click to expand...
Click to collapse
Bro I think you have been extremely unlucky with the amaze. Although it does have some issues (capacitative light bleed, camera flash bleed, lower battery life than one would like, and slow development) most of these have been overcome to a great extent. If you are using a case you will have WiFi issues and possibly Bluetooth (I had WiFi issues with cover on, no BT issues) but that's fixible with a silver cigarette foil (or gold as well Iguess) placed in the battery back cover right beside the camera hole in the cover.
BlackeyedBandit said:
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
Click to expand...
Click to collapse
I too have the bluetooth connectivity issues. The only reference I could find to an "aluminum foil fix" was actually wifi antenna related. However, the thumbnail image is in this post by darll, 15th November 2011: (Wifi signal affected by phone case) in the Amaze 4g General forum.
BT MAC addresss
hasoon2000 said:
Nope. Mine works. I have a jawbone prime. No issues with connection.
Sent From My HTC Amaze 4G Via Someone's Room
Click to expand...
Click to collapse
Where does the bluetooth get it's MAC address from? (the one under settings/ about/hardware info/ bluetooth address)
chevycowboyusa said:
Where does the bluetooth get it's MAC address from? (the one under settings/ about/hardware info/ bluetooth address)
Click to expand...
Click to collapse
I think it is on the chip, but I'm not certain. It could also be programmed into the part of the phone firmware that is not touched when flashing.
I also want to report that I've had no issues with BT connectivity, and I have connected with about 8 headsets / handsfree over the past year.
My Amaze can get into a problem state with the BT, where the phone does not acknowledge a change in BT from off to on or vice versa. When this happens the phone starts to overheat, and I have to power completely down, and then power on again - at which point it will show the actual BT status. I've been on NRG almost from the start, so I don't know if this is a hardware issue or a ROM issue. I haven't had it happen in a while - I'm now more careful about turning on the BT (the problem seemed to happen when I was accidentally hitting the switch twice). Since I know how to avoid it, I haven't pursued any fixes.
Have you tried replacing the back cover? That seems like the most probable fix.
bluetooth
bluetooth problems?!
Hi, I have a rooted and s-off amaze with nightmare rom. everything is working but bluetooth. I can turn it on and switch to visibility but the problem is it can not find any devices and also it can not be found by others. I flashed some kernels but it did not work. please if u know a kernel that fixes bluetooth i can try it. thanks
BT
artur-x said:
bluetooth problems?!
Hi, I have a rooted and s-off amaze with nightmare rom. everything is working but bluetooth. I can turn it on and switch to visibility but the problem is it can not find any devices and also it can not be found by others. I flashed some kernels but it did not work. please if u know a kernel that fixes bluetooth i can try it. thanks
Click to expand...
Click to collapse
This have anything to do with it?:
http://forum.xda-developers.com/showpost.php?p=54112028&postcount=6
Looking to see if anyone else has had BT issues in the past week-ish? I'll get some cutting out of the audio. It seems to happen no matter which app I'm streaming from or what device I'm streaming to. Also, I'm not sure if it is related but I've noticed some weirdness with my Fitbit Syncing too since roughly about the same time. (Some of the data is making it across to my phone because another app gives me credit for the steps taken but none of the info shows up in the Fitbit app and I can't get the time on the tracker to update. May 12th seems to be the last official sync.)
I responded to a post in the Tmo Oreo thread that I'm not really sure that it is related to the Oreo update. I did the update right when the OTA came out then went on a road trip. It didn't happen the first couple of days. I initially thought it was thermal cut out since I was driving a lot at the time and it was pretty hot out. But it still happened when I was driving at night when it was cooler. Then I was thinking it might be my car's BT but it's also happening as I sit here at my desk connected to a pair of BT headphones that were also reliable before my trip.
So it's looking like some sort of update did it but I'm at a loss as to which one so I thought I'd see if anyone else was having the same issues. Although, after a little looking around, I think the Fitbit stuff may just be Fitbit's issue.
CHH2 said:
Looking to see if anyone else has had BT issues in the past week-ish? I'll get some cutting out of the audio. It seems to happen no matter which app I'm streaming from or what device I'm streaming to. Also, I'm not sure if it is related but I've noticed some weirdness with my Fitbit Syncing too since roughly about the same time. (Some of the data is making it across to my phone because another app gives me credit for the steps taken but none of the info shows up in the Fitbit app and I can't get the time on the tracker to update. May 12th seems to be the last official sync.)
I responded to a post in the Tmo Oreo thread that I'm not really sure that it is related to the Oreo update. I did the update right when the OTA came out then went on a road trip. It didn't happen the first couple of days. I initially thought it was thermal cut out since I was driving a lot at the time and it was pretty hot out. But it still happened when I was driving at night when it was cooler. Then I was thinking it might be my car's BT but it's also happening as I sit here at my desk connected to a pair of BT headphones that were also reliable before my trip.
So it's looking like some sort of update did it but I'm at a loss as to which one so I thought I'd see if anyone else was having the same issues. Although, after a little looking around, I think the Fitbit stuff may just be Fitbit's issue.
Click to expand...
Click to collapse
This was one of the reasons the Oreo update was halted.
R800x_user said:
This was one of the reasons the Oreo update was halted.
Click to expand...
Click to collapse
As I said, this doesn't seem to be Oreo related. Just as oddly as it started, it has stopped. So it doesn't seem to be related to any visible front end update, OS or app. Looks like it is somewhere in a background update. (And I don't have any my apps set to auto update.)
FWIW, the only communication update that I can recollect at this point in time that is causing a ton of problems for mobile device users is the Bluetooth 5 that came out with Oreo 8.0. It is a bonifide mess. The version that came out with Oreo 8.1 was supposed to fix these issues, but I don't know that this actually happened. For the most part, manufacturer updates that are released for devices, such as BT Headphones, will try to incorporate a workaround or fixaround for the deficiencies in the underlying software, such as Bluetooth. But there is only so much that a manufacturer can do to circumvent the fundamental issues in an application such as Bluetooth. After all the promises and hype, the basic consensus is that Bluetooth 5 practical improvements are basically in range and some bandwidth. But it is also pretty well accepted, by now, that Bluetooth 5 is largely a mess right now, and not only for headphones, but pretty much about everything that you try to pair your phone to.