Hi, I have a couple of HD2's ready for use within the business I work for.
These HD2's were purchased as replacements for older HD2's that had been used and were getting tempramental and old.
I have recieved the new HD2's and heres my problem:
The touch screen seems to decide when, and IF it works. The first time I EVER got it out of the box, unwrapped it etc the touch didn't work.
After a couple of restarts the touch works, then after a bit it will then decide not to work.
This happens constantly, it will work, then wont work, then work, then wont work.
When it works it is fine, just like the HD2 should be, it just seems to be like a moody teenager who decides when and if it want's to work.
Any one know what could cause this? Why it is happening and why it works and then doesn't?
Thanks !
the touch has always been a weak point of this phone, and your issue doesn't sound all that uncommon.
if they still have older version, rom then you should certainly update that.
if there's any warranty you should definitely go that route immediately,, because you almost certainly aren't gonna fix it.
Hi mate
Yes I have updated the ROM's which went from 1.4 (ish) to the current ROM listed on the HTC website. That seemed to fix it, but then I realised the phone was in a good mood, and 10 minutes later it started its hissy fit again.
And about warranty I don't know as I didn't buy them, we may have to attempt to send them back but thats gonna take weeks, as it took weeks for them to arrive. And we need them out and about tbh.
Do you have any idea what the cause is?
Hardware/Software?
Thanks !
sorry no clue why, and I'd say it's most likely hardware,,, a failing digitizer by the sound.
Sounds like the common digitizer issue, just had same with my personal TMOUS HD2.
Our local supplier said he had units 100% new but old that had failed in the box, reckons digi ribbon bonding to digi is bad on both solder & socket types.
From 20+ HD2 handsets we have running in our company I would conclude similar myself.
My personal handset has had extremely light & sympathetic use & hardly minimal use of end key but it still failed.
Hardware durability of digi/micro USB port & mainboard thermal control/BGA solder quality is very poor to be polite ...
Related
Having read a lot of posts... both potentially apropos and perhaps diverse... from this August company of Ameo sages and mages, I have been moved to write to you to ask if there is something you can advise with respect to WM6 on our Ameo.
We have two such similar devices, both in T-Moble livery... with the nice leather book binding and the peculiarly useful pen pointer.
One arrived well-used with HTC Windoze mobile 2.21.405.2 on it, and the accompanying larger sized HTC home module, apparently of that period.
The other arrived practically new and boxed, with Windoze Mobile 2.35.110.4 on it, and the HTC Home characteristically implemented in the task bar area.
Being housebound disabled, the Tom Tom which came with it is virtually useles to me as well... so if anyone is desperately seeking one then we might arrange something.
The new unit came in and came up from cold. Not having a method whereby you can stop the branding process, as we do on our XDAIIs units, we were forced to permit that to continue... which was our first surprise. However that seems to bring in some benefits... in the shape of Opera and Tru-Flo... as well as a bit of T-Mobile dross too.
The HTC unit functions pretty well as far as I can see, and takes more or less everything you can give it to try. And it also starts on keyboard contact too.
The T-Mobile does not, and also needs to be re-set fairly often.
Too often for my money.
The HTC unit is unlocked as far as I know. The T-Mobile is awaiting a Pay-As-You-Go Card from me, and the use of the unlock code, which was obtained for us by the person who sold it to us.
The real tell for us (as mere users rather than mavens) was oddly enough, not with a performance tool kit or with any kind of enhancer, but with Hidden Expedition Titanic... of all things.
It works fine on HTC, but appears to glitch on the sound on the T-Mobile, and then hangs. Other similar softwares appear to do the same immediately after install, and then sometimes seem to operate as they should after a re-set. Astraware Solitaire WE and Robo, to name but two.
Going on from there, we got hold of Syberia. As big a test as you might want for this type of device I thought. That works pretty well again on the HTC, but inexplicably stalls on the T-Mobile far too frequently... necessitating a re-set. It is my impression that it does so if run from a previously closed session involving more or less any other task or purpose but can sometimes function adequately from a warm boot. (There are occasions with this unit when I'd like to implement the old MSDOS computer users saw... and give it a warm boot... AND also a HOT Wellie.)
Again, it is only my impression, but it seems that if I run Pocket Mechanic Ram Reclaimer on this unit, and then run Syberia, we seem to get a longer run without a freeze... sometimes to where I have to close in the normal course of events.
The same sort of thing... system hangs... happens now I have tried it... in Word. Especially when using Transcriber.
I have to say that I had perhaps unreasonably high hopes of that, having had a Toshiba Portege Tablet for a while now also, and having been quite surprised at how good the Tablet version of Windoze is at handwriting recognition on that. Most unlike Microshaft...
Then I thought that problems we had (and still do occasionally, albeit not requiring a re-set however) with the Tosh might be similar on the Ameo.
On the Tosh, as it arrived, we found the startup to be inundated with little Toshiba software modules... many of which were uneccessary. We improved boot times no end by taking a lot of them out... although live processing sometimes still has slow periods.
Notwithstanding however I tried to look at the Ameo in the same way.
In the startup there are around a half dozen files, aside from the obvious... Magic Button and X-Scalar that are there due to my efforts. And there seems to be little or no information as to what these are, or what they actually do... or more importantly... if they can be safely left out.
I've no doubt, from my reading here, that a simple answer from you all would be to install the unlocker and the forthcoming cooked ROM.
End of problem... perhaps.
However I tend to be a little more conservative (or timid perhaps?) with this concept... also noting those poor folks who have "bricked" their units too.
We have had excellent service from our XDAIIs units over the years, and they have been good companions when we needed them, as well as just phones. They are still operating with WM2002SE and still most software that I "find" seems to work on them... including the Ameo-Glitching Hidden Expedition Titanic I might add.
This week the chap next-door-but-one also got an Ameo... having seen ours and liked it.
His came out of the box with WM5 on it... possibly old stock?
However it set me thinking again and this has finally moved me to ask the assembled wise old Ameo-ers... if perhaps we would be as well reverting our new Ameo to WM5 too... for the time being at least... or if we might be better employed seeking something like the HTC version on our HTC unit?
Or perhaps some other solution presents itself to you from my description?
I'd like to get the new unit starting from keyboard connect also, if anyone has the fix.
The HTC unit came with a restore CD with WM5 on it... and not the HTC version which is presently installed on it's ROM. So I cannot just mirror it to the new unit.
There must be a concensus surely?
The units are manufactured similarly, by the same processes, and using basically the same internals.
We need a windoze version for these which settles down and does what it is supposed to with most of the software that is available.
At the present moment I have "ancient-egyptian" XDAIIs, which seriously outperform at least one new Ameo... in most respects... and that can't be right.
QF
Ameo
XDAIIs
HP Jornada 720
Atari Portfolio
Cliff Notes version? In 5 sentences or less, what are you asking?
Cliff Notes?? Who he??
I want the second to run as well as the first... and I'd like to know why it doesn't.
QF
techntrek said:
Cliff Notes version? In 5 sentences or less, what are you asking?
Click to expand...
Click to collapse
quinbus_flestrin said:
Cliff Notes?? Who he??
I want the second to run as well as the first... and I'd like to know why it doesn't.
QF
Click to expand...
Click to collapse
Hi
I feel you have lots of time to write on here. therefore you must have time to read about these threads before you try to mirror anything. If you do not understand fully you may brick your ameo.
To unlock the CID: http://forum.xda-developers.com/showthread.php?t=315831
Read the above thread fully
upgrade the radio: http://forum.xda-developers.com/showthread.php?t=372904&highlight=radio
Upgrade to AP3 DUAL Rom: http://forum.xda-developers.com/showthread.php?t=346221
Both of your devices need to be unlocked if you want to upgrade another rom other than original ones. If you do not understand clearly please do not do any changes and read everything about athena.
Good luck
Microshaft Windoze,that's great.
Anyone else with a Parrot MK6000 having problems making and receiving a call while connected to the kit? Mine works great on stereo A2DP but when trying to make a call the voice cuts out after a second or two and then a few seconds later disconnects, probably because the person on the other end can't hear me and hangs up. At first I thought it was the phone and got a replacement but no joy. A similar thing happened with my Omnia last year and I got rid of the phone because of it thinking the phone was at fault but now I don't think so. Kit works fine with other phones but not Windows Mobile even though the phones I am having problems with are listed as completely compatible and tested on Parrots website. My software version on the kit is 1.03a which is their newest. Any ideas? Still waiting on a reply two days later from Parrot. Seems kind of screwy to have to worry whether and accessory like this will even work with your expensive phone. I thought that was why they came up with standards. These things aren't cheap or easy to install.
Try a Firmware update to the Parrot MK6000. Also ask them a way of configuring your HTC to work correctly. If they say that is full compatible, that's because they tested, and if they tested they know the definitions inputed in the phone.
I've a MK6100 and it works fine, not exactly the same... but yeah try the firmware upgrade
None to try
I've already got the most recent firmware. Parrots testing is crap. When I first got the thing within a day, I knew that I needed a firmware update on their upgradeable "ahem" unit. Software upgradeable was even plastered all over the box. The unit that came in that box had the 1.0 software and guess what. Faulty testing. They had to replace it with a unit that had the current software because they made a mistake in testing and updating would not work on the 1.0 units. That was over a year ago and there is still no firmware updates. They knew they had a problem with WinMo phones even then and now they are saying compatible? Onl good thing that happened then was I was in Detroit and drove my big truck right up to the door of their headquarters. One of their lab guys was forced to reinstall the unit that had been installed just two days earlier. You would think they would never want to have to do something like that again. So anyways, I have a call and and email into them to let them know I have a problem and no response. Hopefully someone else who thinking of buying one of these units see's this post and takes the warning stay away, at least if you have a smart phone because these people aren't going to support you. (At least not unless you embarrass them by pullling up to their front door in a 75 foot truck )
Techitrucker said:
(...)(At least not unless you embarrass them by pullling up to their front door in a 75 foot truck )
Click to expand...
Click to collapse
Yeap, that's also a good way of making them do what they promise... And to claim warranties...
Stay away from Parrot bluetooth
I have two parrot handsfree units, CK3200LS in my car, CK3100 in my wifes.
They have caused nothing but trouble for my WM phones (Tilt and now TP2)
I can't get the TP2 to pair with the CK3100. I'm waiting for parrot to respond to my help request. Their support info is worthless. The instructions refer to settings which don't exist and password format which is unusable (/"1234/" ?).
When the WM phones successfully pair, there is a re-occuring problem in both Parrot units where there appears to be an incoming call (it doesn't show a caller ID - just 'CALL') but the call cannot be answered. If you press the green button to answer, the unit locks up. You can't "disconnect" with the red button. The only thing you can do, is turn the car off, wait for the unit to turn off, and then turn the car back on to reset. Sometimes my Tilt would get locked up from the call and need to be soft-reset as well.
I had the unit working successfully with non-WM phones for some time, so it was no longer under warranty. When it started with the WM phones I took it to the installer. He was aware of the problem, but had no idea how to deal with it as the problem is so transient.
Bottom line - stay away from Parrot if you have a WM phone.
sblevine
have you try Jetware? I think it may solve alot of your problems
Used Jetware in the past and it caused more problems than it solved. After paying and exhorbitant amount of money for a setup, should not be needing to spend another $15 bucks and installing new software on the phone anyways. The answer I received from Parrot is that even though their website specifically says that the TP2 is a supported phone they are not aware of that and it is not. Real organization there. They also said they will no longer be supporting the MK6000 with software updates not that they supported it much to begin with. They are more than happy to try and find a workaround which I will try but not holding my breath. This will be the last Parrot product I will purchase. The MK6000 is less than 2 years old and is a hard install. It is unimaginable that a company should stop supporting such a product in such a short period of time. The vehicle you need to rip apart to install this thing will more than likely be in financing three times as long. Thoroughly unacceptable.
I had some issues with the TP2 on my carkit too. I discovered that issue was with the ROM on my TP2. Because the carkit downloads the contacts, TP2 just blocks somehow, The response of the phone was slow, I could not accept calls... Then I have installed 6.5 beta version of rom for TP2 and it has sloved the issue. Maybe you could just try installing "official ROM" 6.5.
I am glad you have written this all down. I have an MK6000 in my car now, and while I have some issues between it and my (soon to be old) Tilt, I can make calls, have full conversations and listen to music. I just have to put up with weirdness after I hang up the call and check to ensure my phone isn't suddenly in silent mode when I turn the car off.
I would like to know, what else is out there as far as installed hands-free kits that will work with WM phones? I've got a Tilt 2 coming to me this week (yay!) so I really don't want more problems!!
-Chuck
so is the parrot mk6000 worth it, i need a bluetooth car kit and it has the basic functions i need
also is this a good price or is it available cheaper from another place , the site i saw it at i think was mynewgps.co.uk
Many thanks
Hey guys,
I do got some issues with the WIFI reception on my gtab. The signal is always very low and weak. I tried every rom, even did an NVFlash to go stock but that didnt help either. I did put carbon stickers on the whole device though, can that have any impact? Are there more people with this problem and if so have you got stickers on the device? Please let me know, thanks in adance!!
Peace!
After submitting this post my connection dropped which it also does more often.
Anyone has a clue?
3sade,
I actually had this same problem about 2 weeks ago. I would be directly over my WiFi AP and had a weak signal (2bars) no matter what ROM I used. I called up GTab support (310) 228-4000 and opened a RMA with them. Despite what's I've read in other posts, support was very nice and willing to help for me. They will tell you that you'll have to remove the carbon stick from the device and restore it to the stock ROM. That part sucks but when I got my gtab back (14 business day wait), it is in better working condition then when I sent it to them (the screen is more responsive, seems less sluggish with the stock ROM).
I don't know if this is what you were hoping to hear, but I thought I would pass it along.
I'm sorry to reply to an old thread but I've just recieved a hannspad sn10t1 which I believe has similar if not the same hardware as the GTab. I'm having the same issue with wifi connection, if I actually touch it to the router then I might get 3 bars! I definately cant leave the room and still be connected.
Have I got a faulty unit or is there a software or settings fix? By the sound of this its a hardware fault but I'd rather try and find a fix first.
htc-rocks said:
I'm sorry to reply to an old thread but I've just recieved a hannspad sn10t1 which I believe has similar if not the same hardware as the GTab. I'm having the same issue with wifi connection, if I actually touch it to the router then I might get 3 bars! I definately cant leave the room and still be connected.
Have I got a faulty unit or is there a software or settings fix? By the sound of this its a hardware fault but I'd rather try and find a fix first.
Click to expand...
Click to collapse
Most definitely a hardware issue. It sound like your antenna is not even connected at all. I would contact the manufacture for a RMA. If not crack it open and find the antenna
I just bought the Tab from a buddy of mine the other day. I started with the G Harmony ROM but couldn't get my slingbox or Qloud player to work.
I changed to Vegan last night and while everything seems to work great now, my sound is having 2 major issues.
1. I get a constant crackle and hissing from the speakers. I know this is partially a known issue as I've found some older posts, but nothing recent.
2. In Youtube/Slingbox, if the audio is working, it will only go for about a minute before stopping all together.
If anyone has any clues, or if my device is shot, I'd love the feedback.
I can't help you resolve your existing issues.
But I can say I've been running Calkulins rom with Clemsyn's version 9 kernel and Youtube and Slingbox work without any issues. No crackling from the speakers either.
I think the device is fine, just software issues.
I'll update the kern, hope it works
I've had the same exact issue ever since I got my GTablet. I've tried nearly every ROM and a few kernels, but nothing worked. NOTHING.
So, just about 30 minutes ago I requested an RMA through Viewsonic. It was super easy, but it will be about 3 weeks before I get mine repaired or replaced.
I never found a solution, and tried every suggestion I could find. The problem is so rare that I don't know if the devs have even had a chance to determine what the problem is. I eventually gave in because no sound is downright annoying.
Again, though, the RMA process has thus far been very smooth. I'll keep you posted as the process unfolds.
I updated to the Clem 9 and it worked for a little while. Two nights ago it did it again... I'm almost positive its a hardware speaker issue. When I plug headphones in it stops. After it happens the sound usually drops. Headphones seem to still work.
My main issue is that I got it off someone of crags list. The kid generally wasn't a shady character although I'm sure he had the issue.
Will Viewsonic give me the email if I don't have a receipt?
Sent from my VEGAn-TAB-v1.0.0b5.1.1 using Tapatalk
ViewSonic did NOT ask me for a copy of my receipt, just where/when I bought it (so I'd have a good "story") but they're not trying to hassle you, that's for sure. I think that because the device is less than 1 year old and has a 1 year warranty they already know that all devices are still under warranty.
Give 'em a call if it bugs you (as it likely does). You'll lose your device for a few weeks, and you have to pay for shipping & handling (cost me $25 at FedEx, paid for their packaging though). But having a fully-functioning tablet is worth the wait.
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