yashsingh1/xdaforums huggingface dataset:
[HTC One S] Sneakyghost:
Hey Raynk,

cool that you are getting back to us here. I really hope you find someone to lend you an affected phone.

How about trying that on a healthy device? Wouldn't that be interesting too? I mean, if you could make a healthy device freak out, that would already prove quite something. It would mean that this device is already susceptible to this problem even if build properly and good.

What do you think?

If there is any other Italians with an affected phone near Raynk please contact him!

Thanks,

Sneaky
[HTC One S] guigz2000:
Hello...

Some news from my 2.21 phone...

I do not have the big home button problem anymore...no more neverending vibrations with helicopter view...

BUT,i wouldn't say problem is totally gone:

Sometime i get kicked out from an app or the touch buttons become irresponsive.This kind of issue is not very frequent.

Now,the phone is not perfect ,but it is definitely not that a bad phone...
[HTC One S] Sneakyghost:
Yeah mate the issue hasn't gone. You're quite right there. It's hiding behind different symptoms now. I have locked buttons all day for instance. I was hoping to add a new description to the op the next days because the issue is still present but different with the new bases.

Feel the Viper! :D
[HTC One S] :
Guys try this install battery drainer from play store and let you battery go empty . At 2% battery level it will switch off automatically but it can be switched on back then again run battery drainer ,on 0% it will last upto 5 mins then go blank will not power on . Then press the power button for 10 seconds and charge ,switch it on . Please tell if it gives some good results

---------- Post added at 09:40 AM ---------- Previous post was at 09:33 AM ----------

As when you will try powering on (10 seconds power button press ) while the battery is totally dead . It will suck all power from the board . It might fix it . I never had this issue my phone is now 1 week old , and signal keeps switching from 4G to 2G . And I am mostly on 2g (edge) . I have USA tmo one s s4 . Ht24x . But the base 0.16.31501S.16_2_10.22.31501S.10L is different from bases reported
[HTC One S] craigspc:
Just to keep everyone posted. My friends' One S is still fine since the 2.31 update. Must be nearly a week now without any problems.
[HTC One S] aardbeix15:
ok, report from my side.

Last wednesday I recieved my HTC Netherlands. They replaced my screen as a fix for the home button issue I was suffering so much. Luckly they listent to me and the software was not change (no factory reset, update, nothing).

For the last week now I have the phone 90% of the time in 'gsm'-only modus and try to leaf WiFi off. Before the operation the home button was going mad then. Now I leave the screen on en drive for an hour and nothing happens.

But... now after a week I'm again in a office, very rural, and I just saw the home button issue. But now different. I was much more polite, not very heavily and the touch buttons still worked after this happens. It is so much more less that I can live with it for the moment.

For me it makes clear it is a design flaw of the HTC One S but different devices have different hardware variations...
[HTC One S] gibarian:
Thanks for the update. Good news for him, I hope it stays that way.

I am running 2.31, and the issue persists. EDGE= havoc for me, screen dance & button lock

I am starting to lean towards an assembly flaw or component weakness...

Had similar experience with my Transformer Prime tablet, I exchanged it 5 (!) times during 2 weeks. In the end, I would open the box in the shop next to the vendor and check with him. Two devices had visible flaws right away: screen not attached properly or vibration unit loose (rattling sound when vibrating). The components themselves were fine, but the assembly line fu**ed up. The vendor couldn't believe it. They send an entire batch batch to the factory without opening the rest. In the end, I got a proper unit, happy ever since...

Point is: Maybe (just maybe) the hardware & software are fine, but due to tiny assembly errors, trouble appears on various models with different hardware after a while. It's just a theory, and I hope I'm wrong: I still pray for a software fix...
[HTC One S] :
Sneakyghost do think it will work ???
[HTC One S] opiswahn:
Little update from me too, 3 days since the 2.38 OTA and still no issue.

Maybe this is a combination of different solutions. The Phone i have now was sent to me as a swap device, preinstalled 1.78. But on this phone, the issue was way less than on my old handset. Still reproducable, but not so extreme. So, after the 2.38 OTA no issue at all(yet...)

Maybe they have done something with the antenna and the OTA did the rest... The only difference i noticed was that the bottom antenna cover was a little bit 'lower' than on my old phone. Could be coincidence, could be the solution.

I'll wait and see what happens (or not ;) )
[HTC One S] gibarian:
I find that very interesting...
[HTC One S] :
It could be a visual illusion or something. I dnt think HTC will change the hardware. As it would only make loss of them
[HTC One S] zoesdad70:
After I got the 2.38 update from Vodafone UK, I had several instances of the homescreen problem. However, the effects were very much reduced compared to before the update. Whereas before my screen would rapidly change between the homescreen and overview, after the update it took about a second to switch.

On Saturday afternoon I bit the bullet and did a factory data reset. Since then I've had one very minor instance of the problem where the phone buzzed and locked the buttons.

Today has been problem free (so far) and I've been trying hard to reproduce the problem by visiting previous blackspots and keeping WiFi switched off.

Has anyone else tried a reset?
[HTC One S] opiswahn:
Not yet, i'm waiting with this until(if) the issue reappears, or i feel like using a custom rom ;)
[HTC One S] decmk:
After reading first post i didn't find answer is ville c2 is affected with problem?
[HTC One S] gibarian:
Might wanna check out SneakyGhost's spreadsheet HERE

Your answer is in there. Bad news I'm afraid...
[HTC One S] Will972:
Maybe someone will take care of this note .. i got this amazing issue .. and since 3 days i got WCMDA by default.. and i ain't got the issue anymore . And when i try GSM/WVMDA auto , the issue come again.. the signal on WCDMA is not so bad . I got 3G and oyher things .. think the problem is related with GSM configuration .. i'm not expert on that .. i just make a test ..

For info i'm on the last viper's rom

My hboot is 1.13 and radio is 0.16 ..
[HTC One S] Raynk:
1) I have no devices, neither affected nor healthy, so the problem is still the same :confused:

2) I think it would be better to test an affected device first, so i could isolate the frequency range and output power required to trigger the issue. After that, i could try on a healthy one. Testing a healthy device first would probably lead to this question: "i'm unable to trigger the home button issue because the device is healthy, or because i'm not using the correct frequency / power?".
[HTC One S] gibarian:
Thanks for sharing mate but (lol) you might want to read this thread's first post...

Anyway, you're right: it is mostly noticeable on EDGE (GSM).

We are a little bit ahead of you here ;) Just read along :)
[HTC One S] Sneakyghost:
not much time, am at work. Only one quick thought: I have had several li-ion batteries killed instantly by running them down, so I began researching the technology and found out that these batteries always die very quickly when running them dry. So I think going your way can come at a very high price and even though it might be a good idea I would much rather grab my Torx screw driver, open the device and unplug the batteries for a few minutes.

I doubt that this will do more than give you a few days piece until the problem builds up again.

Yet your suggestion does contain an interesting thought which I need to think through still. Thanks for your contribution. Be sure that you inspired me with a new idea :)
[HTC One S] Sneakyghost:
Of course. Very often. At least once every three days for a while. It does help for a short period. It's not comparable to the idea of making the board lose all juice though.

Feel the Viper! :D
[HTC One S] Sneakyghost:
Gibarian meant you should check the spreadsheet. We discovered at least 20 reports that most likely came from the S3 VilleC2. Bad news...

Feel the Viper! :D
[HTC One S] Raynk:
Location diantnam

Hi,

this afternoon (at about 17.00) i received a call from Germany. Considering that i live in Italy, when i saw the caller id my reaction was "WTF? :eek: ". It was a call from HTC support, and they asked me about the issue that i had reported to the htc chat help desk, about one week ago. Now, i told him about the home button issue, the guy said they are aware of the problem and that an update was recently released to fix it... and that they're waiting for users feedbacks... I suppose he was talking about the 2.31 update, released almost 1 month ago (22/08/2012)... because i can't see any other update available on the htc website !
[HTC One S] Tecardo:
I wont recommend doing the powertrick. As it won't help solve the problem for ever. Also can and will damage battery

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] gibarian:
I second that. Lithium batteries should never be drained completely, it's very bad for them.

It's not like former Ni-Cd batteries where drains were sometimes needed because of the memory effect. With current batteries, one should always keep at least a little power in them.

Btw, I managed "save" a battery once by "shocking" it, as in giving it 2-3 times the required power for a very short period of time (1 sec). But it doesn't always work. Kind of a last resort... Of course, you'd need to get it out first, and have a proper adjustable power supply. Anyway, just don't do it :)
[HTC One S] DeGon:
Just installed the OTA Update provided by my carrier Swisscom. Before installing, I went to the basement in my house to check if the issue was still there. There's a spot where the phone switches to Edge. And of course it flickered as usual (see video I made some months ago: http://www.youtube.com/watch?v=xKkXW41T2zE&feature=youtube_gdata_player). After the OTA update it worked without problems. The phone switched to Edge but without any flickering. So I can confirm that the update helped in my case (until now).

Rgds
[HTC One S] gibarian:
Good news for you :) What version?

You might want to check again and confirm after a week or so... This bug tends to be tenacious and come back. I hope not though, for your sake...
[HTC One S] DeGon:
Software No. 2.36.166.6

Baseband is 1.06es.50.02.31_10.09a.50.04L

BuildNo: 2.38.166.6 CL97613 release-keys
[HTC One S] Sneakyghost:
Odd version. Too bad it's so late here, would love to look into it now.

Seems like a provider adjusted 2.31 derivative. Radio is from the previous 2.31 version if I see that right.

Feel the Viper! :D
[HTC One S] guigz2000:
Is someone in France?i do not get the ota...i flashed the 2.21 ruu...
[HTC One S] Sneakyghost:
Check your cid. Maybe yours is not on that list for the ota...

The ota can be had by either changing to a cid known to get it (HTC__001) or by running the complete RUU, which is in my dropbox. Look at my signature. RUU is easier I'm sure.

Feel the Viper! :D
[HTC One S] :
Thanks sneaky for warning me . I only drained my battery once for nothing . I will not do it again
[HTC One S] Sneakyghost:
At this time i'd much much rather open the case and unplug the battery. Even though this is not good either as assembly afterwards will nearly certainly cause you other issues. I am rather sure the other options are the best ones for now.

On the other hand: draining the board from all current might be worth a thought. But i think Tecardo and Raynk can answer this better as they are int he electronics business.
[HTC One S] fabioaalves:
the new vodafone Ota 2.38.161 is working for me

the new vodafone Ota, the 2.38.161 with radio 1.08es.50.02.21_10.09c.50.04L is promising good things!

i am in a phase of hard tests but it is holding on! :) and good ! not even 1 problem with home button

had to quit TrickDroid v8.0.0 , its ok for now

at least i finally have a new radio without changing CID :)

will report later in the week
[HTC One S] mugenx5:
Hi

my One S is now since 4 weeks in repair because of the Home Button issue.

Today i called the hotline of my provider (Swisscom) and ask about my phone.

They told me, that the replacement of the ONE S is delayed because off the Home Button thing.

The problem is well known at my provider and there are many customers waiting for a replacement.

Markus
[HTC One S] zoesdad70:
I got the Vodafone update last Friday and had an instance of the homescreen problem within 10 minutes of applying the update. After a frustrating 24 hours with the problem, I did a Factory reset. The result was that the problem disappeared!

Yesterday however I started having problems connecting to WiFi which I remember having before; this appeared as a precursor to the homescreen problem appearing on my replacement phone.

Today I've had a few instances of the homescreen problem, one of which happened when I was on a call. This is something that's never happened to me before.

One other thing of interest - I have camera upload switched on with DropBox and I was having a clearout today. There were a boatload of screenshots taken by the homescreen issue some of which were of the unlock screen! I hadn't realised the homescreen problem was kicking in at this stage.
[HTC One S] Sneakyghost:
@Zoesdad70

would you be willing to root your device and dump the radio.img by using a "dd" command and adb-shell?

If not you, maybe someone else might want to do it? I really want to try but i nearly bricked my device when swithcing to VODAP CID and not getting the update. I think the OTA process uses other means to determine if the update can be had. It must be checking the build.prop or something like that too because i was on RUU 2.31 and couldn't have it, then i tried 2.21 and couldn't get it either. But i want to try the radio and i have hopes that i can flash it because 2.38 has the same hboot as 2.21 and 2.31. So signatures should match.

-- Post duplicate from the other home button thread--

After having had two terrible days with my device nearly bricked from trying to find a fix for this horrible issue i can now report being back online.

Plus, i have used MiniTool Partition Wizard to zero out the SD Partition on the phone and then re-run the RUU 2.31 and then installed viper again and after that, the phone acts a lot more snappy and the Home Button Issue has pretty much changed to "Locked Capacitive Button" issue with hardly any occurrences of the actual home screen switching.

This behavior is known as the newer symptoms beginning with Base 2.21 and being stronger on 2.31 and 2.38. So, it's not fixed at all but way harder to notice. :D

Might goof some into believing they had a fix there. Just mentioning ;)

People, if you ever have difficulties on the One S with the SD not mounting properly after messing too much, i can only recommend doing a thorough wipe with nulling all bits using some tool like the above. I knew i had to go this route because i had similar experiences on the HD2 already. This is sometimes truly doing wonders. Fragmented data leftovers on the SD partition does not go well with an Android system for some odd reason. Doing that once in a while together with a Factory Reset and a RUU this keeps the device being a nice toy.

It doesn't fix the Home Button issue though. Just maybe a helpful tip for all the messies out there.
[HTC One S] sirward:
I'm here again with some more news about our One S. We received the phone back a couple of days ago from Dynafix for a second repair. Now they replaced the display module and since the phone is back we did not have encountered the problem again.

This evening we are leaving the city to visit some family in "EDGE valley" so that will be the big test to check if a screen module replacement really is a fix for the touch button issue over here.

Dynafix also encountered the problem in the repaircenter (running the latest software they installed on a previous repair!) they mentioned on the repairsheet. They did not see the flickering but did notice the "touchscreen did not work" (I assume they mean the touch buttons themselves).

So for now it looks we finally have a working phone again.. Ofcourse I will keep an eye on this thread and will update you guys if more troubles occur. For now I think your best bet is to send the device a couple of times for a repair, via HTC themselves, and hope for a display module replacement.
[HTC One S] greenvik:
Question ..

Hi everyone.

Firstly,I wanna say that I am sorry for all of you who are having the home button problem.I know how irritating is to have a phone problem so I am sorry that some of you have encountered that.

Having said that,let me move to my question.

I was planning to buy the One S few months ago,but I found out about this problem so I went for the HTC One V just for the summer,thinking that the problem on the One S will be fixed by then.

However,I decided to check once more before I buy the phone next week and I found out that the problem is still there.So now,I have a question to all of you,@Sneakyghost especially since he seems like the most informed about this problem.

What I want to ask is if EVERY HTC One S has the home button problem,or is it half of them,or just a small number ?!?

In other words,I really like the phone and I plan on buying it(I'd go for the One X but it has way more issues than the One S and I kinda like the S more),so I am asking if it is worth the risk or not ..

Btw,I am from Macedonia which is South-East Europe(in case the region has something to do with the problem).

Thank you in advance :) .
[HTC One S] geostar1:
Currently working around this issue running the Paranoid Android ROM with the hardware buttons disabled and ICS/JB Software buttons enabled.
[HTC One S] zoesdad70:
@Sneaky: Sorry, I really don't want to root my phone plus I've got to send it off AGAIN to HTC,

HTC wouldn't take my phone for repair until I got the update from Vodafone. As soon as I'd applied it, I got the homescreen problem. So I notified them of this. Today I got a reply from them advising me that the technical team "seem to think this is now a hardware related problem, and will carry out the necessary repair." Only seem to think? Grrrr.

This will be the third time I've sent my phone in and each time it has been away for two weeks. Slow or what?

So, anyone reading this who is considering buying an HTC phone - Think long and hard. The phones are wonderful if you get a good one. I haven't had a good one and have found out the hard way that their customer service sucks. I've been a One S owner for five months now and for all of that time I've had a phone that worked without fault for around 3 weeks of that time.
[HTC One S] gibarian:
Oy oy oy...

On a more positive note: Congratulations on your 2.000th post :) :highfive:
[HTC One S] Sneakyghost:
Haha oh was it... Never noticed. Too bad my thanks haven't risen to a full thousand yet or else I'd have had a perfect 50% ratio lol...

Feel The Viper! :D
[HTC One S] markeemark:
There's a contribution ha, keep going
[HTC One S] Sneakyghost:
Did anyone come across the 1.08es Vodafone Radio btw? I really want to test that.

Couldn't someone dump it for me?
[HTC One S] .TanTien:
I have not exaclty the same issue but if I have my finger over the homebutton it keeps clicking home. Thats really annoying.

Im running a villec2 with trickdroid 1 and gsm.
[HTC One S] Alex24_24:
Hi all!

same issue here. Does the Beatnix1 solution work? Is it possible to flash that zip without unlocking the bootloader?

I have stock rom and I'd like to preserve the warranty...

Thanks!
[HTC One S] Sneakyghost:
Yeah this is a known thing on Torxx's and he_stheone64's work. It has absolutely nothing to do with the Home button issue. It is fixed on the new ViperOneS OTA and for TrickDroid you have to talk to Torxx as he is aware and knows the reason for that now.

In any case, it does NOT belong here.
[HTC One S] Sneakyghost:
Thing is, Beatnix has experimented a lot with it and says it works but i never actually got around to test that. I feel a little blush creeping up my cheeks admitting to that but i simply had too many other things to check, test and research at the time.

To answer your last question: Since this messes quite deep down in the System it will more than likely not work without unlock, Root, custom Recovery. The fix has to be flashed through recovery anyway, which is not possible with the stock recovery. Without unlock, you'd already fail before you booted your device.

But i doubt that an unlock takes away your warranty. HTC did explicitly exclude unlocked devices from Warranty, however, you should be aware that a big company has to go that step to be on the safe side. It says nothing about how they deal with it in reality. They are still free to use common sense as that is not explicitly excluded in their terms and conditions.

Their way of dealing with it has mostly been this: if they get a rooted device and find obvious signs of physical damage (drop marks, water, heat, anything of that sort) they will refuse warranty. If they get the same unlocked device without any visible sh1t that hints towards you being rough on it, just messed up software, they will just reflash stock stuff and see if it fixes your issues and send it back. Hardly ever will they ask money for that.

I have been told to base decisions on what experience tells us and not upon fears and doubts.

Experience says unlocking your bootloader does not lead to loss of warranty in 99% of all cases. Physical damage caused by user cases excluded.
[HTC One S] .TanTien:
Okey, thanks.

Is there a Viper ROM for the villec2 devices?
[HTC One S] Sneakyghost:
Nope, my friend. Regrettably, there isn't. However, some people tried to talk the Venom Team in porting the Sensations latest viper to the ville C2 as that was based off the Ville C2 RUU if i understood that right and bringing it back to the VilleC2 should be possible. The only problem is, that it has not yet gotten the Sense 4.1 and Android 4.0.4 update. So it could be that the guys wait until there is a better base. Or maybe they can't be arsed at all. At this time the VilleC2 has a rather bad position. It might change once the Ville dies out. Production on the S4 has stopped since a while already and the S3 is pretty much overtaking it in numbers by now i think. So development might eventually increase too. But on the other hand if i where a dev i wouldn't want to waste my money on a 2010 chip based phone...
[HTC One S] Bomberkun:
I'm crazy with this problem. Now I just unlock, put the bootloader and root, and I'm ready to try other radio, the one I have now is RADIO-0.16.31501S.17-2 how I can change it, is safe?

Thanks ;)
[HTC One S] Sneakyghost:
In my signature is a link to my public DropBox folder. There is Radio.zips in there as well as RUU's.

If your hboot is below 1.13 (go to bootloader to check) you can use the zip's. Just unlock your device and flash TWRP Recovery (at the moment works better than CWM). Once you got the Recovery, copy the Radio you want to the SD Card and flash it with Recovery.

If your hboot is 1.13 or higher, you can only update your Radio by running a full RUU. In my DropBox are all HTC generic RUU's and the ones from TmoUS. For the RUU's you do not need to unlock or anything. Just connect the Phone to PC and double click the RUU.exe.
[HTC One S] Bomberkun:
Yep HBOOT-1-13-000 :(

The RUU change the entire system? It would be this: 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

Is it possible then upgrade to 4.0.4, and keep ROOT?

Thanks, I'm pretty lost :silly: