How do you figure they are not supporting it?
Yes I know it is a bummer that not fixed yet. Bit they did say that they are working on a resolution.
Because of the timing they may just roll that fix or develop the fix for the update instead to Android 4.0
Would be more time consuming and more resources to develop a fix for two different versions.
theartiszan wrote: How do you figure they are not supporting it?Yes I know it is a bummer that not fixed yet. Bit they did say that they are working on a resolution.Because of the timing they may just roll that fix or develop the fix for the update instead to Android 4.0Would be more time consuming and more resources to develop a fix for two different versions.
IF it is a software problem, then I suspect that the coding between OS versions would be similar, if not the same. In this instance, I say work on the patch and incorporate it into the future OS update.
The device is approaching 6 months old. My faith in any major OS updates is slim.
In any event, no firm commitment seems to have been released for either resolution, other than "we are working on it". I'm sure both HTC and TMO are devoting more resources to the latest and greatest release vs updating/correcting an existing device.
Honestly, I am surprised the problem made it into a final product.
Software or hardware, the problem had to be known about pretty quickly. That means that someone has been "working on it" for 6 months.
TMO won't do anything for me as far as a swap to a different device is concerned without (1) paying full activation price or (2) a contract extension, so that pretty much tells me where I stand. They don't seem to care, because the customer will either (1) put up with it or (2) buy another phone and remain a customer or (3) move to another carrier (which triggers early termination charges).
Compared to my history of mobile phones, yes, the Amaze is the worst. None of my last three handsets had all these issues: bluetooth range practically nil, general radio reception poor inside buildings, repeating text messages, and buggy wi-fi connectivity. These are all basic functions on mobile phones -- none of these should be an issue.
All these issues should have prevented the phone from being shipped at all. Based on my experience I will never buy an HTC model phone again.
The other problems I am not having at all. Again not saying that they don't exist just mine has no trouble and seems like most don't.
Just I am only having problems with the bluetooth is all.
And HTC did comment that they will be releasing a major update to the phone of android 4.0.3 and Sense 3.6.
If you are having problems with signal I would suggest calling HTC. You may have a problem with the back cover. That is where the antenna for signal is.
I agree, just had the talk with tmobile have been only 19 days still no budge, no release date for ics.
I agree with otheres development is cheaper if only on one version that is 4.0 instead of poor gingerbread and ics.
same 4 same text messaging and bad bluetooth, battery life is a joke. bloatware everywhere. I said F'em and rooted and unlocked running a kind of ics rom works great, no bluetooth issues or multi text. still have all functions as stock but no bloatware either. XDA_DEVELOPER.COM ROCKS and if and when ics comes out you can relock and run stock ruu and update with no issues.
So if I have an issue with the back cover, I call HTC or T-Mobile? I thought T-Mobile provided warranty coverage during the first year?
This has gone from annoyance to show-stopper. I asked a few co-workers to rate my phone calls from my truck using Bluetooth, and they all said "not great" to "terrible". Same problem with two different earpieces plus a Motorola bluetooth speakerphone.
The problem is T-mobile don't have back covers.
So if you need one you need to call HTC.
HTC is aware of a range problem though.
If Bluetooth is within 2 feet and having the problem that would not be the software and should get back cover.
But if only further away that is the software which a update from HTC will fix when they release it.
People running custom software don't have the problem like the previous poster said.
I also have had the same connectivity problem (intermittent disconnects and choppy audio) between my Amaze and four different handsfree devices; ALL of which connect without any problem whatsoever with my Desire and Nokia handsets. I had a warranty replacement unit sent to me within the 14 day initial period and the problem persisted with the new unit so I sent it back. It is not a range issue as the phone and handsfree are less than 3 feet apart at all times.
I am not at all convinced that any promised software fix would ever resolve the problem. I think it is more hardware / firmware related that results in a timing mismatch between hardware elements. During the manufacturing process it woouldn't surprise me that HTC tried a cheaper chipset or bluetooth module that just doesn't fly. That means only a physical replacement of the chipset with one that works would resolve the problem. That, obviously, means factory recall. That, obviously from the posts contained in this series, is something that will never happen without a more vocal initiative from the customer.
Based on the demonstrated, "We don't really care," attitude projected by T-Mobile towards it's customer on this well-knowns and persistent and unresolved complaint, I don't think anything short of a class action lawsuit would be enough to get them to react.
Grounds for the lawsuit would be not just failure to provide the features promised but also danger and legal rammifications posed to customers where handsfree functionality is required by law in certain jurisdictions.
I suppose going directly to class action lawsuit is a bit extreme. A more immediate venue is the Better Business Bureau.
T-Mobile is clearly being non-responsive to a clearly defective product in the Amaze. Doesn't matter that HTC is the manufacturer. T-Mobile has it's name plastered on the display. Don't they certify the quality of the handsets they distribute through their stores?
I went to a T-Mobile shop today to check whether the HTC One has a Bluetooth issue. It works perfectly. I want a trade-in option to upgrade to the HTC One. The Amaze is a defective product. I noticed that the Amaze is no longer sold in T-Mobile shops. Wonder why. I suspect it's not only because new phones come out every six months.
I encourage all of you Amaze owners with a similar defect to ask for the same. I bought my Amaze 2 months ago.
I really hope T-Mobile monitors these posts because calling customer care is a futile exercise on this issue.
It is already been well stated and documented that this is a known issue with the device.
The known issue is with the software of the phone not working properly.
If you try bluetooth stereo which uses the same hardware works fine. Just software is not connecting right for standard audio.
I too have this issue, or rather did have the problem I should say.
But anyway it was working great when it came out, then the wifi calling update came out and started having the problem.
I have since installed the leaked ICS update that has been floating around and has been working better.
It is fixable just need to wait for the update.
It is time to see results.....http://www.facebook.com/HtcAmazeOnlinePetition
My stereo Plantronics handsfree headset gives me a stereo hi-fi chopped audio experience. T-Mobile is being ineffective at dealing with one of their major suppliers to resolve this problem.
Curious. Just went to the HTC site to update sync software and the HTC Amaze is not even listed in the selection of phone models. Should I assume that they and T-Mobile have given up on supporting and resolving this long-known Bluetooth issue?
I did the same thing a while back....I accidentally went to the eu site. here you go:http://www.htc.com/us/smartphones/?carrier=tmobile
So, is HTC EVER going to resolve this Bluetooth issue?
"theartiszan" must be a T-Mobile employee. They are clearly NOT supporting and resolving this issue.
Retrieving data ...