Massive thanks to PulpZilla for letting me have his OP. I will now be able to take care of the updates a lot easier. Mate, this was a nice move. And even though the "Thanks" at the bottom say they where for me, they are still counted to your name. I did not get them from you
-=Introduction=-
This Thread serves as collection and information point for all Data regarding the HOME BUTTON / SCREEN ISSUE or as HTC sometimes likes to call it: HELICOPTERING GLITCH.
It also serves technical and factual discussion in order to maybe find ways to overcome or work around the issue.
For any and all discussion regarding civil, legal or other types of action against HTC we now have a new thread, named:
Operation Rolling Thunder
It is run by Gibarian. Please head over there for discussing actions and options. I would also like to encourage everyone to move discussions of "Buy or not to Buy" this phone over to that thread. So we can keep this clean for rather technical and news things. Apart from that, I would also like to express that i outspokenly support the campaigning as long as it stays civil and serves the sole purpose of raising public awareness and thus creates the necessary pressure on HTC. I would like you to support the current campaign there too to help our issue getting taken more serious. Up till now HTC has delivered nothing but empty promises.
Please refrain from stupid actions/posts/reviews.
Thank you.
Sneakyghost
-=Problem Description=-
Main Symptom:
The capacitive Home Touch Button sometimes likes to press itself. When in an app or the home screen without or with the finger near the home button it seems to get pressed a few quick times in succession without actually being touched.
Click to expand...
Click to collapse
Additionial symptoms:
- continuous/odd vibration
- multiple screenshots being saved to disk without the user interacting with the phone
- the virtual buttons appear locked/dead/without function [NOTICE] From Base 2.21 onwards, this can turn into the main symptom and the screen switching can disappear.
- long-press menues coming up randomly (On Stock JellyBean 3.16 this would be Google Now popping up all the time)
Click to expand...
Click to collapse
Occurrence and reproducibility:
Mainly related to GSM activity, rarely on WCDMA only setting. It seems to be related to low GSM signal (1 to 2 bars), switching between networks, calls coming in or building up, seldom wifi and 3g connections. The occurrence still seems rather random as it is hard to purposely reproduce the situation. The best chance to trigger the misbehaviour or malfunction is if signal coverage is low, 3G/HSDPA (or: WCDMA) is not available, try to build up a call or start a heavy data transmission on edge. A few people report the issue only after the first 2- 4 weeks of use.
Also noteworthy: it seems to hit phones in complete unaltered, stock state as well as heavy customized and unlocked phones.
Click to expand...
Click to collapse
-=Documentations and Discussions=-
Discussion on the Vodafone UK forums: http://forum.vodafone.co.uk/t5/HTC-One-Series/Home-screen-button-problem/td-p/1082393
Discussion on the O2 Germany Forum: http://forum.o2online.de/t5/Software-Firmware/HTC-One-S-Home-Knopf-Problem/td-p/259614
Discussion on the SwissCom Forum: http://supportcommunity.swisscom.ch...onie/HTC-One-S-Home-Knopf-Problem/td-p/121958 (NEW)
Discussion on the Android-Hilfe.de Forum: http://www.android-hilfe.de/htc-one...usgeloest-durch-bestimmte-netzfrequenzen.html
Discussion on the Handy-Faq.de Forum: http://www.handy-faq.de/forum/htc_one_s_forum/251792-display_springt_hin_her_home_ansicht.html
User contributed Video: http://www.youtube.com/watch?v=LOb1LuWA7N8
User Contributed Video: http://youtu.be/kvPOZsk9I_I
User contributed Video: http://www.youtube.com/watch?v=mEKwMkuisqE
Disassembly video, bottom Antenna, US Model: http://www.youtube.com/watch?v=b0jGY2N2h1U
Disassembly Video, complete EU Model: http://www.youtube.com/watch?v=1lBT15PgpYw
LeeDroid mention of HTC's own theory: http://forum.xda-developers.com/showpost.php?p=26819259&postcount=707
Related:
http://www.youtube.com/watch?v=B6xlZFcgPlo (similar issue on Galaxy Nexus) (Thanks to SageKing for pointing this out!)
https://plus.google.com/112413860260589530492/posts/1a4hY7VeqiG (Google Engineer talking about the Galaxy Nexus problem)
http://maps.mobileworldlive.com/ Site to see which operator uses what frequency in which country - cross check against Affected users Spreadsheet!
-=News Articles=- (please send in other articles if you find any as we will pass them on to HTC at some point):
http://www.geeky-gadgets.com/htc-one-s-touch-button-bug-makes-phone-go-crazy-26-06-2012/
http://www.phonearena.com/news/HTC-One-S-touch-button-bug-makes-the-phone-go-crazy-video_id31606/
http://www.chip.de/artikel/HTC-One_S-Handy-Test_55316948.html
http://www.chip.de/news/HTC-One-S-Probleme-HTC-bezieht-Stellung_57834622.html --> Chip cites HTC here, yet no source is given.
-=Attempted fixes=-
- Disabling GSM/EDGE completely (no calls in rural areas, Issue not fixed)
- Setting Accessibility → Touch & Hold delay to medium (reported ineffective by some users starting HERE
- Factory Reset (multiple users had tried this, was recommended by different support agents, did not help at all)
- different Radio (there had been different radios involved, but not all radios seem to be affected. Still needing evidence)
- Exhchange SIM Card. (has been done by several users, did not help at all)
- Root device, Unroot device, flash Custom, flash stock, unlock Bootloader, relock bootloader. (did not help at all)
- Removing bottom cover (Mobile Radio Antenna), cleaning spring contacts, examining hight (make sure contact is made) - Not fixed
- Setting Display illumination to Auto Brightness (did not help at all)
- Run CM9/CM10/MIUI/JB Builds. Did not change anything.
- New Radio 1.06s.50.02.27_2_10.08.50.04L (19th of July 2012) Betters it for most users considerably,did not help all Users
- New Radio 1.06es.50.02.31_10.09a.50.04L (21st of August 2012) Worsens the effects clearly for most users, did help some very few. Upgrade NOT recommended!
- New Radio 1.08es.50.02.21_10.09c.50.04L (14th of September 2012) Some users report failure and behavior similar to the 1.06es radio.
- New Radio 1.08ts.50.02.16_10.08e.50.04L (ca. November 2012) Similar to the 1.08es radio
- New Radio 1.09ts.50.02.04_10.08g.50.04L (ca. November 2012 Only my Test-Results available, which where just as bad as 1.08 based Radios.
- New Radio 1.11.50.05.28_10.27.50.08L (24th of December 2012) Worse than the 1.08 radios, but some users also reported a Fix
-=Working Fix(es)=-
none known
Update 4th July 2012: HTC begins to claim towards some users now, they were soon be rolling out a software fix. 4 weeks later, they still say the same.
Update 21st July 2012: HTC has not officially acknowledged the Issue, but allowed this Info from HTC Elevate moderator Jason Dunn to be shared: "A software based Fix is possible and being worked on. A release date is not available but it will come".
Update end of July 2012: HTC released a new RUU (RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe) with new Radio. Betters it for most users considerably Semi-FIX. Not good for all.
Update 30th August2012: HTC Released a new RUU (RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1 .06es.50.02.31_10.09a.50.04L_release_275655_signed .exe) This Firmware does not help most users but rather worsens the effects again. Upgrade of Radio not recommended!
Update 14th September 2012: HTC released a new OTA to Vodafone Customers going by the Name of 2.38, containing a new Radio 1.08es, which does not solve anything. Like the previous 2.31 WWE release, it seems to make matters worse again.The other carriers succedingly released their updates with either the 1.06es or the 1.08es radio. Only T-Mobile released a 1.08ts variant. None fixed the Issue.
Update 24th December 2012: HTC finally released JellyBean Firmware 3.16 to their customers. It became obvvious only hours later that it did not fix anything. I myself have a worse HBI problem than on 2.31. Plus, reception and Data-Switching got worse too.
-=Workarounds=-
- Disable Home Button: User Beatnix has found out how to disable the Home button completely. It can then be replaced by the App "Button Savior"Obsolete
- Recommended: Custom ROM allowing button remaps. Viper ROM with Venom Tweaks has given me almost a hassle free Experience during the past month due to its ability to map functions to the buttons that either do nothing or do not disturb too much.
- Recommended: After countless tests with all sorts of Radio/Wifi-Partition/Base Version Combinations it is very obvious that the 1.06s Radio from Base 2.21 is by far the best, least bugged Radio.
Note: A "Brick Downgrade[/UL]" might be required, if you are already on or above Firmware Version 1.78, as Radios can only be flashed on lower hboot versions. Here is a [URL="http://forum.xda-developers.com/showthread.php?t=1990043"]Tutorial
-=What Now?=-
If you are feeling like getting active i would like to invite you to join Gibarians Operation Rolling Thunder which is designed to make our Issue heard. We feel that we have been quietly waiting for a fix long enough and that waiting any longer will just make HTC believe that they do not need to take any further action, so Gibarian has designed a campaign to make the Issue more public and make it obvious to HTC that there is need for urgent action.
At the time of writing, some People have been waiting 6 month for a fix and had not gotten a replacement, nor any other compensation. They have just been left out in the dark with a nearly unusable phone. So, feel free to make yourself heard! Also, if you just have a story to tell, feel free to add it at Gibarian's Thread "Operation Rolling Thunder". You are warmly invited to share your sufferings there and also discuss recommendations for other (potential) buyers.
-= IMPORTANT: Report your device here if affected =-
PLEASE:
file a report with your vendor (most likely your carrier) and ask for repair/replacement
file a report with HTC. Ask for repair/replacement if your Vendor refuses.
This is very important, as this is the only means by which HTC can tell the severity of the issue!
Jason Dunn of HTC Elevate and Richard Willis of HTC Consumer Communications EMEA encourage everyone to report to HTC.
Please also report here: (For updating your Entry please contact Sneakyghost or Zoesdad70)
[UPDATE 11.10.2012]
Here is a new Report Sheet where everyone with a Serial xx26 and higher can report his FULL serial and Contact Details.
Personal Information: This Sheet can only be accessed by me (the Results page) and is only used to be forwarded to HTC. I kindly ask you to leave contact details for the sole purpose of possible further questions. Your data will remain with me and there will be no abuse.
Thank you.
LINK: http://goo.gl/5gAR8
What do we do that for? I am currently talking with another HTC Digital Consumer Communications Manager for the EMEA region and he is trying to find out about the new devices. If it is a lot of them, HTC wants to fix that in time. To be able to do so, they need to know as early as possible. So, your help is greatly appreciated and in the end, will help all. Thanks.
Click to expand...
Click to collapse
-=Statistical Data of affected users=-
Updated 7.01.2013
Total number of reports:
793
- Areas where this has been reported:
Portugal, Spain, France, Belgium, Netherlands, Great Britain, Ireland, Swiss, Germany, Austria, Denmark, Sweden, Poland, Estonia, Latvia, Czech Republic, Russia, Ukraine, United Arab Emirates, Israel, Malawi, Ethiopia, Niger, Iran, Malaysia, China, Vietnam.
Please pay attention to this! It is mainly northern Europe and Russia. Up till now four reports from the US.
- Serial - Numbers first digits that had been reported as affected:
FA28 (2x)
HT23 (183x)
HT24 (77x)
HT25 (18x)
HT26 (7x)
HT27 (3x)
MB22 (1x)
SH23 (149x)
SH24 (190x)
SH25 (27x)
SH26 (35x)
SH27 (1x)
SH28 (1x)
- Base Versions reported (Entries cleaned up, corrected Base Versions according to reported Radios. This assumes that all reporters used either RUU or OTA).
1.09 (2x)
1.11 (8x)
1.15 (1x) (odd Thailand version - never seen anywhere else)
1.47 (1x)
1.53 (16x)
1.70 (6x)
1.77 (40x)
1.78 (273x)
1.84 (5x)
2.15 (2x)
2.21 (10x)
2.31 (338x)
2.35 (3x)
2.38 (20x)
- Black device count:
577
- Grey device count:
185
- Baseband versions reported:
0.15.31501S.16_3_10.12.31501S.06L
0.15.31501S.19_10.12.31501S.06L
0.15.31501S.19_2_10.13.31501S.06L
0.16.31501S.17_10.23.31501S.10L
0.16.31501S.17_2_10.23.31501S.10L
0.16.31501S.19_2_10.23.31501S.10L
1.06s.50.02.27_2_10.08.50.04L
1.06es.50.02.31_10.09a.50.04L
1.08es.50.02.21_10.09c.50.04L
1.08ts.50.02.16_10.08e.50.04L
1.09es.50.02.07_2_10.09d.50.04L
16.11.20.02U_16.05.20.11_M2
16.12.20.02U_16.05.20.16_M2
16.13.20.02U_16.05.20.24_M
16.13.20.02U_16.05A.20.23_M
Concluding:
All the numbers peak at xx23 and xx24 serials. Base 1.78 and 2.31 are reported most often. My Guess: the March and April devices are worst combined with those two bases.
Source of these figures is the Google Spreadsheet, Anyone wanting to add can do so. Please feel welcome to put in your details via the Form linked in the top left Cell of that table, the top right cell of the table holds another spreadsheet-form for only the newer xx26 and up serials. It is designed so that it remains private because you can put in your contact details so that HTC can contact you. They are currently investigating the newer devices and might need your help.
-=END NOTICE=-
If you came here to find information you were helped hopefully. Please help other people with the same issue by raising your voice and add a report. Please include your Country, your first part of the Serial (“SH23”), Carrier Base, Baseband, Phone color etc. Best is to update the Spreadsheet directly.
Same problem here, although it hasn't happened in a while. I have the phone rooted but even before it was rooted it happened.
interesting. Since you've rooted and changed the ROM it hasn't happened?
Same one here.
I think it has something to do with the gsm-mode. When i'm in an area without HSDPA(only G-Mode, sometimes also in Edge) or when i manually switch the mode to 'only GSM', the switching appeares.
The strange thing is that this is not always the case.
I don't know if this is a hardware error or has something to do with the recent update. I can't compare this because my phone came back from RMA the day the Update was released. On my 'old' phone (before RMA) i never had that problem, but that was before the update.
*edit*: Still on Stock Rom.
Greets,
**Jürgen**
opiswahn said:
Same one here.
I think it has something to do with the gsm-mode. When i'm in an area without HSDPA(only G-Mode, sometimes also in Edge) or when i manually switch the mode to 'only GSM', the switching appeares.
The strange thing is that this is not always the case.
I don't know if this is a hardware error or has something to do with the recent update. I can't compare this because my phone came back from RMA the day the Update was released. On my 'old' phone (before RMA) i never had that problem, but that was before the update.
*edit*: Still on Stock Rom.
Greets,
**Jürgen**
Click to expand...
Click to collapse
funnily enough it seems to happen more when there's less light? also it still happened when i had WiFi on so i'm not exactly sure of the cause. Hopefully it is only a software glitch and something that can be fixed in custom ROMs!
Has someone fixed the problem with a custom rom? Or has that problem with a custom rom?
I'd like to know if i have to RMA ma phone again or if it's a simple software glitch...
after more testing it looks like you're right it seems to happen when the phone is searching for a GSM signal on edge?! really weird...must be others out there having the same issue?
Sure, that problem have more people. I have reported it to HTC this day. The problem is the Edge we think. It can be reproduced if you turn on Gsm.
I hope HTC make a update to solve the problem, but more people must report I think.
P. S. I'm on Trickdroid Rom, this happens on custom Rom to.
Gesendet von meinem HTC One S mit Tapatalk
PulpzillA said:
after more testing it looks like you're right it seems to happen when the phone is searching for a GSM signal on edge?! really weird...must be others out there having the same issue?
Click to expand...
Click to collapse
A whole bunch of people have this problem over on the UK Vodafone HTC One S forum
I have this problem whenever I try to press space, I end up hitting home. I noticed that if you slide your finger down from the screen onto the touch buttons, it registers as a button press. Whereas on my Desire S, if I was sliding my finger down (i.e. scrolling a list), even if I went past the screen and onto the touch buttons, it would still continue to scroll. Only if I let go of the screen and then touched the buttons again would it press. I'm pretty sure that's how it should be.
Lamyron said:
Sure, that problem have more people. I have reported it to HTC this day. The problem is the Edge we think. It can be reproduced if you turn on Gsm.
I hope HTC make a update to solve the problem, but more people must report I think.
P. S. I'm on Trickdroid Rom, this happens on custom Rom to.
Gesendet von meinem HTC One S mit Tapatalk
Click to expand...
Click to collapse
Did you wrote a Mail or did you call some support?
*Edit*
Ok, i just had a chat with a support-lady from HTC, she told me HTC knows of this problem and they are working on an update for this. But there is no release-date for this update.
*Edit2*
This doesn't seen to be a hardware problem, thats good news so far. Everyone who has this problem should report to HTC, to increase the pressure for the fix. This was a hint from the support-lady
I had same problem.
I gave my phone at warranty service, they checked it and approved the problem.
I managed to get the phone to seller and exchange to new one, but I know if I would repair it at service, they would replace back cover (had little chipping), battery and MOTHERBOARD.
So I suggest you to bring it to warranty (if the return period is over) and they should fix it...
PulpzillA said:
interesting. Since you've rooted and changed the ROM it hasn't happened?
Click to expand...
Click to collapse
Just to clarify. I have the phone rooted but still on the stock ROM. And yeah, it seems to happen when its not on 3g.
Here is a video of the problem:
http://www.youtube.com/watch?v=mEKwMkuisqE
Please post if you are concerned by the problem.
Conditions foir this issue to happen:
No wifi.
EDGE with low signal. numerous siwtch of the phone between 3G and EDGE.
then you shall reproduce the issue.
Thats exactly it. Just report to HTC to increase the awareness of this problem, so the fix comes out faster.
Really annoying now as the phone is barely usable on GSM signal! Gonna have to complain to HTC. This shouldn't happen whatsoever. It's a simple thing to test for?! Can't believe it wasn't picked up...
Don't know if its worth wiping and seeing what happens?
Sent from my HTC One S using xda premium
Guys, I turned off the data roaming sound in the network settings and havnt had this problem since. Though I.only turned it off last night but it hasn't happened since.
Sent from my HTC One S using XDA
Interesting! thanks for the tip. will try this out and see.
shoffobroff said:
Guys, I turned off the data roaming sound in the network settings and havnt had this problem since. Though I.only turned it off last night but it hasn't happened since.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Unfortunately that didn't work for me.
I sent mail to HTC support to inform them about problem.
They advise me to try new sim card.
I have new sim card now, but problem still exist
I'll send phone back tomorrow, but I think that next one will be affected by the same issue.
This has been getting worse for me. Seems to happen particularly when outside? Otherwise; exactly as described; when switching to and from Edge.
Neither Vodafone nor HTC UK are aware of the problem. HTC global suggested I hard reset. Currently awaiting next useful repair suggestion...
Related
The 2.32.651.2 OTA for the Sprint Hero is still rolling out, and so are some bug reports. I’m hearing and seeing a bit too many reports of things like serious lag, to the point of a battery pull, or problems with contacts since accepting the OTA than usual. According to Sprint, the only thing users should see is an updated Sprint Zone, but there are a couple other bug fixes. Hopefully these are just isolated incidents, as you would think they have the Hero software down pat by now.
In any case, be warned before you click accept. Of course if you’ve rooted your Hero, you have nothing to worry about, because you shouldn’t be accepting OTA updates. Get the update yet? Share your experience (and help out a fellow Hero user) in the forums
via:
http://androidgod.net/?p=2243
I downloaded the update and had zero change to my phone whatsoever. I assumed root was removed once I updated the phone so I went ahead and re-rooted it immediately after updating. There was no change in performance everything remains the same. It seems like the only thing that changed was the baseband version.
kaokollaa said:
The 2.32.651.2 OTA for the Sprint Hero is still rolling out, and so are some bug reports. I’m hearing and seeing a bit too many reports of things like serious lag, to the point of a battery pull, or problems with contacts since accepting the OTA than usual. According to Sprint, the only thing users should see is an updated Sprint Zone, but there are a couple other bug fixes. Hopefully these are just isolated incidents, as you would think they have the Hero software down pat by now.
In any case, be warned before you click accept. Of course if you’ve rooted your Hero, you have nothing to worry about, because you shouldn’t be accepting OTA updates. Get the update yet? Share your experience (and help out a fellow Hero user) in the forums
via:
http://androidgod.net/?p=2243
Click to expand...
Click to collapse
I'm running this right now and since Nfinite posted it and have had no probs at all.It is that update rooted
http://forum.xda-developers.com/showthread.php?t=849024
I tried it out for a whole DAY!! It was very laggy on my Hero. I even tried rooting, ading a2sd, switching over cache and adding a custom kernel... No Luck, still slow as sin. Way to go Sprint just gave me one more reason to follow what you want us to do and toss this phone for a new one. But Wait.. I'm smarter than that. I don't have to follow the Sprint Way. So I reflashed LiquidSense. Ahhhhh, That's better.
I only flashed the radio and it decreased my signal. Worst part is I was out in the sticks were I only got two bars afterwards only got none
Asadullah said:
I only flashed the radio and it decreased my signal. Worst part is I was out in the sticks were I only got two bars afterwards only got none
Click to expand...
Click to collapse
Yeah I'm Goin back to the prior radio
I'm having a lot of echo on the phone I don't know if its the radio or the rom I just started running the extremely blue cm6
Sent from my HERO200 using XDA App
lags might be sprint-zone ?
id been on .7 for awhile, did ota to .32 and did not notice any changes in radio (bars or echo or whatnot) nor any changes in lag (contacts or responsiveness)... i DO have those problems (radio due to not-near-tower and lag due to several-hundred-contacts) so i doubt that the 'reports' are common issues... of course i live in metro-socal so life is pretty good normally...
however, i DO believe that a lag (particularly on initial powerup) might be due to the sprint-zone app... i dont know if we had had it before, but now it actually seems to be slightly-intrusive and it DOES require a reasonable connection to dl the info and time to create the notification... i have had it (sprintzone) intrude/notify me twice since the weekend (my OTA update to .32)... i hope it stops - cuz it is not useful info (for me)... personally, id prolly uninstall it if i were into really-customizing my phone...
comparing stock-anything to custom-liquid-sense like the user up above is ridiculous tho... when id gone custom before, there were tweaks for overclocking and so-much-bloat-removal that the phone HAD to be faster...
just my 2-cents, h.
I want to return to stock on my tmobile branded HTC sensation 4G. I have flashed the radio, eng s off, and CSL recovery.
I am going to give them a shot at fixing my reception issues before I destroy the phone and buy something else.
Did you have reception problems before flashing your radio or after? I think you should be fine with having a rom since HTC released their bootloader if its a big deal and your really worried just flash a stock rom on that bad boy and call it a day. Just my 2 cents new to the site so hopefully a vet will chime in here for help
Though I've never returned to stock on my phone, you just need to download one of the TMOUS RUUs in this thread:
[ROM][11 May] Shipped Pyramid ROM Collection
There are two listed for TMOUS (there was only one when last I checked the thread), but it supposedly doesn't matter which one you pick according to one of the posts later on in the thread.
They're big old files, but just run the .EXE and it ought to walk you through every necessary step to proceed properly.
Good luck, and let us know how it goes!
Thank you very much for the great responses.
Yes I had reception problems on all 3 sensation 4g's I've had my hands on. It's terrible. Side by side, on the same tower, it gets far lower reception than my old Motorola Cliq (piece of slow crap.)
It's ridiculously low and drops calls. It's so unreliable at my house that I have to use WiFi calling and take a drop if I get more than 30' from my extremely good wireless router. meh. crap.
To the other gentleman, than you very much. I figured it included the radio, but I was unsure about the bootloader/recovery. I will start there and then figure out if there is anything else I need to fix before I send it in. I don't want any more BS from them. I'm sure they are just going to send it back and say "nothing is wrong".
They have said that it is comparable to reception on their other models. If this is the case, this will be the VERY last HTC phone I ever own, and our company has just gotten to the point that I can invest in things such as this for business. If we only get 2 at a time, every 6 months or so, That is $10,000 in lost business in the next ten years, provided they are only $500 phones.
chisleu said:
Thank you very much for the great responses.
Yes I had reception problems on all 3 sensation 4g's I've had my hands on. It's terrible. Side by side, on the same tower, it gets far lower reception than my old Motorola Cliq (piece of slow crap.)
It's ridiculously low and drops calls. It's so unreliable at my house that I have to use WiFi calling and take a drop if I get more than 30' from my extremely good wireless router. meh. crap.
To the other gentleman, than you very much. I figured it included the radio, but I was unsure about the bootloader/recovery. I will start there and then figure out if there is anything else I need to fix before I send it in. I don't want any more BS from them. I'm sure they are just going to send it back and say "nothing is wrong".
They have said that it is comparable to reception on their other models. If this is the case, this will be the VERY last HTC phone I ever own, and our company has just gotten to the point that I can invest in things such as this for business. If we only get 2 at a time, every 6 months or so, That is $10,000 in lost business in the next ten years, provided they are only $500 phones.
Click to expand...
Click to collapse
If I may be so bold as to make a suggestion and ask a few questions....
1. Have you tried reverting to stock and see if you still have the same problems with reception?
2. Are you aware that the Sensation suffers from the grip of death?
3. Have you noticed performance with reception after flashing a new ROM in comparison to stock?
I think I may have some insight to the real problem but need this info first.
mystikal87 said:
If I may be so bold as to make a suggestion and ask a few questions....
Click to expand...
Click to collapse
Best 3 Stooges voice: "Sauwtainly"
mystikal87 said:
1. Have you tried reverting to stock and see if you still have the same problems with reception?
Click to expand...
Click to collapse
Yes, They (3 different phones) had this problem from day 1. Purchased from different places, at different times.
mystikal87 said:
2. Are you aware that the Sensation suffers from the grip of death?
Click to expand...
Click to collapse
Yes, but this isn't to what I refer. Holding the phone in a weird way to make the radios D/C isn't my problem so much as the design that allows this to happen in the first place is my problem. If I set the phone down, I get more bars than if I hold it normally. If this is the difference between 2-3 and 1-2, I can get dropped calls. My wifi range (max performance on) is 1/10th of my tablet and 1/20th of my laptop.
Even without touching the phone, just setting it on a wood counter top, it has less reception than my Motorola Cliq or Mytouch 4g, even when on the same tower. The cliq's reception does not change if I pick it up.
It's a bad design. If it is what HTC considers acceptable, then their phones aren't acceptable to me. It's cool. I'm not really that pissed about it. I just won't buy another. There are options.
mystikal87 said:
3. Have you noticed performance with reception after flashing a new ROM in comparison to stock?
Click to expand...
Click to collapse
No, I've found no increase in reception with any change I've made. I've flashed 5 different radios other than stock with no changes in this department.
I have heard people have speed changes, but I was not tracking that so I can't really respond to that.
mystikal87 said:
I think I may have some insight to the real problem but need this info first.
Click to expand...
Click to collapse
Hope you have some help.
I've already tried a new back. It did nothing. There simply aren't enough towers in my area (all edge towers anyway) to support a phone with such poor reception. My Cliq had no issues with dropped calls in many of the areas I drive through, but this sensation just can't make it down my parents road without dropping.
The reason I ask is that I think that the Radio-Interface-Layer (RIL) files must be screwing with your radio. The RILs are like drivers for your radio. Different radios work with different RILs depending on your location. Long-in-short-version, Since the Sensation is fairly new, we are still exploring what works best and therefore your mileage may vary.
You may want to check this thread
And check out your RIL version. To check to see what RIL you have run getprop "gsm.version.ril-impl" in Terminal Emulator or adb shell and it will print out the RIL version.
T-Mo users should utilize HTC-RIL 2.2.0159HMQ if not running 2.3.4 ROMS
2.3.4 ROMS require HTC-RIL 2.2.0169HMQ. The matching radio versions are included in the thread posted above.
Hope this helps.
If that fails, tonight, TMOUS released an OTA update. See if you can get it through Settings-> About Phone -> HTC Software updates.
The changes for the T-Mo update can be found here
Hope this helps!
EDIT : I am assuming that you have a T-Mobile Sensation 4G and not an unbranded HTC Sensation and that you current location is in fact Myrtle Beach, SC. But then again, I hate assumptions and I really should have asked >.< **having a simpson 'doh' moment here**
Change your cid to all ones and flash the stock ruu.exe and send it back to tmobile.
Sent from my HTC Sensation Z710e using XDA Premium App
charlieb620 said:
Change your cid to all ones and flash the stock ruu.exe and send it back to tmobile.
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
I'm sending it to HTC, not tmobile.
I will play with the MILs right now (installing the tmo one)
I'm on stock RUU now, but it did not replace the PVT S-OFF and recovery crashes and requires a battery pull to reboot. It goes to a icon of a phone with a red triangle thingie on it.
EDIT: MIL's match.
EDIT: Texts from 10076200000 is tmobile related. WTF it does is WTF.
chisleu said:
I'm sending it to HTC, not tmobile.
I will play with the MILs right now (installing the tmo one)
I'm on stock RUU now, but it did not replace the PVT S-OFF and recovery crashes and requires a battery pull to reboot. It goes to a icon of a phone with a red triangle thingie on it.
EDIT: MIL's match.
EDIT: Texts from 10076200000 is tmobile related. WTF it does is WTF.
Click to expand...
Click to collapse
Could be trying to push the OTA update. Have you tried applying the OTA update?
iNFORMATION
I have personally reset my phone a couple of times using the tmo ruu and know that it sets your phone back to absolute stock, with no root and only being s-off. What this means is, if you wish to reroot then you are going to have to go back through the rooting process.
As far as the symbol that you are seeing when you try to do an ota update? The reason that you are seeing the phone with a red triangle is because your phone is being recognized as being rooted and once rooted htc will not allow an ota to your phone. You have to trick HTC into thinking that the phone is not rooted in order to get the ota, there is a thread in the forums for this. I do not remember which thread it is, however, I know that it works as I did it for all four of the HTC sensations that I own.
I just wondering as still haven't!
I never got 1.47, I'm still on 1.28. I'm not sure why.
My DS is an unbranded unlocked UK model.
We are certainly not the only people not to get 1.47.
At first I was glad that I did not get 1.47, but now I notice that (so far) only people with 1.47 seem to be getting the recent upgrade.
Least am not the only one! HTC support seems to think I would need to send my phone away for repair to have it updated!
podycust said:
Least am not the only one! HTC support seems to think I would need to send my phone away for repair to have it updated!
Click to expand...
Click to collapse
Seriously. All HTC seem to say is any update news will appear first on Twitter or Facebook, yet when anyone has questioned them on there they deny any knowledge of the update even with proof
The only thing they use social networking for is product spamming and corporate shindig promoting!!
Got a small update months ago which installed an updater, but never got 1.47. Still on 1.28. Unbranded, unrooted.
Interested to learn what HTC told you about returning it...
Yes I got those same updates months ago too! This is what they said after first saying 1.28 was the latest and then me saying I know about some with 1.47
Thank you for your reply regarding your Desire S.
The case there is an update available and you cannot receive it through 'OTA', the device may need to be sent for repair. then your device gets updated to the latest version.
Please confirm the following information in order to be able to book the device for repair:
From which address you wish the collection to happen
On which day you wish the collection to happen (please allow 48 hours’ notice)
The Serial Number of your device. (Serial Number can be found underneath the battery.) I will then book and confirm this via Email and provide further repair instructions:
We can arrange for UPS to collect your device from an address (Mainland UK only) that is convenient for you. UPS can collect on Monday through Friday from 1pm to 5pm. There is no UPS service on Weekends and Public Holidays.
Click to expand...
Click to collapse
Do have in your applications (settings> manage applications> all) an install called Updater version 2.3?
I think - not sure - that this is what was installed by the small update? Or is it for the Market? Terribly tempted to uninstall it and see what happens, eg if it updates again, but to 1.47. Or perhaps just try clear data.
Unfortunately to ignorant to know the risk if any...
Yes I and this what small update was it just updates the FOTA program which updates the phone firmware
podycust said:
Yes I and this what small update was it just updates the FOTA program which updates the phone firmware
Click to expand...
Click to collapse
Say again please?
yes it did install updater version 2.3. if you uninstall it you will be asked to install it again!
DON'T INSTALL 1.47!
Please! If you're looking to depress yourself, google "desire s late sms", look at the hundreds of pages of results, from users all over the world with the same problem.
You lucky ones who are still on 1.28 havent suffered the misery of the problem with 1.47 and the Desire S. Just imagine how much fun could be had, every time you're connected to a mobile data network (GPRS, 3G or HSDPA), knowing that there's a better than 50/50 chance all your 2G functions will stop working. Calls will go straight to voicemail, texts will fail to arrive for hours on end... And then randomly, you'll get a dozen messages at once, from people wondering why you've ignored them all afternoon...
Seriously, stick with 1.28 for now, wait for the next update.
We will need to have 1.47 before we can get 2.10!
fasty said:
I never got 1.47, I'm still on 1.28. I'm not sure why.
My DS is an unbranded unlocked UK model.
We are certainly not the only people not to get 1.47.
At first I was glad that I did not get 1.47, but now I notice that (so far) only people with 1.47 seem to be getting the recent upgrade.
Click to expand...
Click to collapse
can you use wireshark to analyze what the update sever's response is?
as when I've done that it replys {"time_msec":"1317992280856","stats_ok":true,"reason":"FOTACANCEL_NO_MATCH_RULE_FOR_CID","intent":[{"action":"android.server.checkin.FOTA_CANCEL"}]}
as mine is also an unbranded unlocked uk model
podycust said:
can you use wireshark to analyze what the update sever's response is?
as when I've done that it replys {"time_msec":"1317992280856","stats_ok":true,"reason":"FOTACANCEL_NO_MATCH_RULE_FOR_CID","intent":[{"action":"android.server.checkin.FOTA_CANCEL"}]}
as mine is also an unbranded unlocked uk model
Click to expand...
Click to collapse
I'd prefer not to install wireshark right now, but I'm certain that I would get the same response.
There are plenty of other people in the same situation. I'm guessing that HTC may have aborted deployment of 1.47 because they noticed that it caused so many issues.
I assume that the "no match rule for CID" simply means that there are no updates available for our particular software version at the moment.
I've just factory reset my DS in the hope of fixing another issue, and after doing so it politely updated the version of it's FOTA loader but nothing else new.
Starting deployment of the sense 3.0 version to a few users without any explanation seems a bit dumb of HTC unless they are simply beta testing.
I could understand them prioritising those who have already loaded 1.47 as clearly this is causing them the most issues. We just need to hope that they don't forget those if us who are still on 1.28
- Steve
had your phone been rooted before you get it?
helicopterpro said:
had your phone been rooted before you get it?
Click to expand...
Click to collapse
Nope, I don't think so. My phone was new, carrier unlocked "sim-free" version from an authorised HTC retailer in the UK. I was previously using an Orange SIM in it, although recently switched to Three. (Have tried to get update when connected to both)
Hello all.
I'm having some major problems with my Desire S - stock firmare v1.47, T-Mobile - and would be very thankful for any support and advice provided
I've had the phone since late August, and just over a month of having it, the phone completely died. T-Mobile replaced the mainboard, and returned it. Since receiving the repaired handset, text messages are delayed when coming through - sometimes upto an hour. Sent it off to T-Mobile again, and this time they've replaced the antenna. The same thing is happening.
While it was away the second time, I did some research and found lots of people claiming it's an issue with the 1.47 update on the Desire S.
The main reason for this thread is just to ask what my best options are from here. I'm ok S-OFFing and flashing another ROM, or downgrading if this is possible and will definitely resolve this issue; but as I'm a certified noob, I was wondering what advice you guys may have for me
Thanks,
DJM.
can't you just flash the 1.28 RUU?
Hi, thanks for the reply.
I used a T-Mobile 1.30 RUU, and S-OFF'd with revolutionary.
I *think* I might have cracked it - touch wood.
I'm amazed at android releasing updates which impede such basic functions though
great, hope you get it sorted
Thanks man
I'm getting texts through as they should at the moment, so fingers crossed it will stay that way.
I recommend that anyone with a Desire S, especially on T-Mobile UK, resists the urge to upload to 1.47
Gone fishing...
GROGG88 said:
Guys, there was another one of these reports about sudden catostrophic failure today:
CLICK HERE FOR THREAD
I think it's high time to get to the bottom of this! To ALL users who have been affected by one of these events, PLEASE post the following information and nothing more:
1. ROM
2. Kernel
3. Firmware
4. Radio
5. OC/UV settings (if applicable)
I'd like to track these stats and tally them up here in the OP to see if we can find a common culprit. I don't really suspect it's a ROM issue since there have been reports on multiple ROMs, but I don't want to rule that out...
-Thanks
Click to expand...
Click to collapse
Hi,
Yes,I have noticed this worrying trend...
One of the things to keep in mind when looking at responses to this kind of poll is to realize that we're looking at an adversely selected population of respondants.
Everyone who posts here about a failure is on XDA.
Everyone on XDA meddles with their phone.
So it's easy to conclude that meddling with your phone causes the phone to fail. (Or that ARHD causes the phone to fail because 90% of custom ROM users are running ARHD)
But that doesn't actually prove anything about the relationship between meddling with the phone and the phone failing because we're not including the 98% of Sensation users who run the stock ROM, don't even know you can replace it, and still have hardware failures.
In order for this poll to be worth any statstical value, we'd need to know what the general failure rate is among all Sensations, including the 98% that aren't rooted, s-offed, or anything else of that nature. (And I'd be willing to bet that someone here is good enough with Google to search out those stats. I guarentee HTC and the Carriers keep that information. It's just a matter of how public they make it.)
If the failure rate among people who flash custom ROMs, kernels, radios, etc is significantly higher than among the general population, then we can conclude that we're doing something risky.
If the failure rate on rooted phones is similar to the failure rate of the total population, then flash whatever you like with joy in your heart. You phone might die on you, but it would have died anyway. You're not the problem.
I would expect the rate of reported failures to be slightly higher on XDA than among the general population even if it's a general hardware fault. That's just because we're more likely to talk about a failed device than the average consumer who has a higher chance of just buying a new one and never talking about it.
Just looking to see if there's common ground between them...
Yes it would help to just narrow it down and try and deal with it unless we want the problem to spread. And now saying that I'm going off arhd to virtuous inquisition after reading previous posts
Sent from my HTC Sensation XE with Beats Audio using XDA
Here is another thread from last week, I think he was running Virtuous before it died on him, but not 100% sure.
http://forum.xda-developers.com/showthread.php?t=1624293
I agree with the failure rate statement, just seems like the folks posting these having been flashing for a while and seems a bit different than the "HELP, I JUST BRICKED MY PHONE" type of thread
Yes..I am not sure if this issue is just a hardware problem and it just happens it died...or if it's related to what we're flashing and modding. And yes...I had flashed ROM a few times before...including insertcoin GB, and ICS...and everything was working....
After I installed ARHD..it seemed fine too...it was running....until I made a phone call.. then it died. So was it just coincidence that it happened after I installed that ROM (include 4ext recovery, radio recommended for t-mobile)...or it's something related to the files we're flashing. I don't think it was from flashing incorrectly since everythig was running for a bit.
If it's just a hardware pb with HTC...then surely there's nothing we can do....but if something is up with the files we're flashing that's killing the phone...as there seem to be much more of these occurences lately with the new ICS roms....then maybe something is up and hopefully someone smart can pinpoint the pb.
Do any of the Devs know this is happening?
Radio recommended for T-Mobile USA in ARHD... I know there was something posted that was supposed to help T-Mobile USA phones be a bit faster in ARHD, is that what you flashed?
Just found this in ARHD:
HTC Sensation 4G (U.S. T-Mobile PG5810000 | T-MOB010) users can flash this for better signal and data speeds!
Wondering if this could cause the problem?
gustav30 said:
Radio recommended for T-Mobile USA in ARHD... I know there was something posted that was supposed to help T-Mobile USA phones be a bit faster in ARHD, is that what you flashed?
Just found this in ARHD:
HTC Sensation 4G (U.S. T-Mobile PG5810000 | T-MOB010) users can flash this for better signal and data speeds!
Wondering if this could cause the problem?
Click to expand...
Click to collapse
Yes, this is what I flashed as part of the update. But it doesn't explain why others have same pb?
Sent from my HTC Sensation 4G using XDA
newr said:
Yes, this is what I flashed as part of the update. But it doesn't explain why others have same pb?
Sent from my HTC Sensation 4G using XDA
Click to expand...
Click to collapse
Hi - I'm just wondering if there is something up with that particular update that is sometimes wreaking havoc with ICS roms for T-mobile USA users.
The reason I pointed it out is because its not a necessary update to install an ICS rom on the Sensation. We just need the latest firmware package and the Rom.
AFAIK, that update is only supposed to enable faster data in the U.S. Probably everyone else in the world outside of the USA, installing ARHD, skips over that update.
I guess it would help to know if the same type of failures are happening to people outside the U.S and who never installed that update.
I know the failure is not limited to just ARHD. So its possible though at one point someone went to the ARHD thread and installed that radio update with ARHD Rom, then jumped ship to say Virtuous and then had a phone failure, because that update is not part of the Rom itself.
This is just speculation - but trying to rule out possibilities.
Hmm..possibly...but I did read mail from someone that's not in U.S. who had dead phone similar to mine....so unless they installed that radio file...it should be ok?
gustav30 said:
Radio recommended for T-Mobile USA in ARHD... I know there was something posted that was supposed to help T-Mobile USA phones be a bit faster in ARHD, is that what you flashed?
Just found this in ARHD:
HTC Sensation 4G (U.S. T-Mobile PG5810000 | T-MOB010) users can flash this for better signal and data speeds!
Wondering if this could cause the problem?
Click to expand...
Click to collapse
That is not a radio. It is rcdata for the radio and the build.prop needs to edited to match. I don't know what the end result of a long term mismatch would be (I suspect nothing bad), but I have run both dish 2 and dish 3 settings with no long term issues on either...
newr said:
Yes, this is what I flashed as part of the update. But it doesn't explain why others have same pb?
Sent from my HTC Sensation 4G using XDA
Click to expand...
Click to collapse
I know you are one of the affected users. Please do me a favor and post the info specifically requested in the OP... I'm specifically interested in what kernels, and cpu settings the affected users were using!
i flashed that thing too when i was running a different rom then coindroid.. luckily im not one of the affected users...YET lol
This isn't looking so good... I hope the devs will figure this out before this thing catches on like wildfire... eek
I was about to get the Sensation...It seems i will have to think again!
I had installed AOKP and when I format data and sd card to factory reset my phone won't turn on anymore...I have warranty and service changed my motherboard...now I can not unlock bootloader anymore...
I should close this thread since it seems nobody can read the OP and follow directions...
I just think they're all dying now because it's been approx a year that the phone is out now? Maybe time is the killer! Afterall, I wouldn't think that the majority of users baby their phone... I've seen some people abuse the living crap out of their poor phone! Dents, scratches, marks everywhere. I'm not too surprised seeing this kind of issue after a year or so. Mine is slowly causing problems too (only prob at the moment is dust under screen and I don't like the microphone either...) and I baby this thing.
Man the same **** used to happen with the G2 and the myTouch4G, the emmc chip in the phone would just randomly give out after about 1 year. ****ing HTC phones, man.
i as using insert coin sense4 rom when mines stop turning on.........all i get is on and off vibrates