yashsingh1/xdaforums huggingface dataset:
[HTC One S] Sneakyghost:
Too early to have a decent idea about it actually. I only noticed 3 people coming back complaining right after the update on Android-Hilfe.de, which seemed a lot to me. Usually it takes some days for the first reports to turn up and for 2.21 it was only about at max 10 i'd guess. so i have the feeling that it might be worse again but the truth is: i have no idea. Its about time to check it.

I cannot flash it at the moment though because there is no update for 2.21 users yet.
[HTC One S] shoffobroff:
Has anyone installed the new ota update? I read on the verge that its software version is 2.31? I can't update till I flash my stock rom back on my phone.

Sent from a glitchy one s :(
[HTC One S] Shandorkar:
the problem persists!
[HTC One S] Phuturist:
Could you elaborate on this. Have you updated to the latest radio and if so from which radio did you come?
[HTC One S] Shandorkar:
new rom 2.31.401.5, radio 2.31_10.09
[HTC One S] Sneakyghost:
New OTA for 2.21 devices available

OK guys some smart dude on TrickDroid Thread found this http://xdaforums.com/showpost.php?p=30574398&postcount=4218

Obviously, the OTA for the 2.21 guys is out in the wild already. Just needs a CID Switch again.

But this also just the first region getting it and the other CID's will most likely follow soon. But if you have no patience you may switch cid right now and receive the update :D

[EDIT]

Or even better: http://fotadl.htc.com/OTA_Ville_U_I....21.401.10_release_275774cltf0sxl730g7fp1.zip

Props to Behold_This.

Cheers and happy flashing this OTA, 2.21 users! :D
[HTC One S] mattionline:
How to install this 2.31 OTA if you already installed the 2.21 RUU??
[HTC One S] pierre.grand:
I suppose you have to root...

I'm stuck in same situation :(
[HTC One S] Sneakyghost:
I knew someone would ask this :D

You see, this is a zip file. How are zips usually flashed? Yes. With recovery.

Go install CWM or TWRP and then flash it.

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] mattionline:
Forget it, I'm not going to root my device for a simple OTA :p

Default recovery isn't working, already tried it a few times...

I guess we'll have to wait for a RUU or an OTA for 2.21 ;)
[HTC One S] pierre.grand:
Since I'm suspecting HW fault for my handset I don't want to modify the phone and loose guaranty from HTC(even if guaranty for HTC is a concept...)

I don't know how RUU are published, does anyone has some infos about that?
[HTC One S] Sneakyghost:
Guys, you won't lose warranty if you use a RUU. If you don't believe me (I could be wrong after all) just phone HTC support. I'm slowly getting sick of all this fear. HTC wants you to shut up and stop complaining so they are HAPPY if you flash the update.

You know, I'm through a good hundred flashes by now and I bet you all I will still get warranty if I go back to sick and really insist. Even though I have already pissed of HTC elevate.

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] pierre.grand:
Don't get pissed off, my remark was about rooting and not RUU updates.

Getting the RUU 2.21 was an enormous improvement even if the phone still bugs.

I(and I suppose all others in this thread) recognise your big investment in helping people and getting this issue solved.

so thank you!
[HTC One S] Phuturist:
Have you flashed this OTA yourself already Sneakyghost? I thought I read somewhere that you can't just flash an OTA zip file and you need to trick your device into thinking it receives the OTA by performing a couple of different steps.

[Edit]

Yeah, this is the thread I had read:

http://xdaforums.com/showthread.php?p=27195248
[HTC One S] Sneakyghost:
Hahaha no i didn't.

And you know why? There's one reason only. When i posted the Radio Update on Android-Hilfe.de Thread, those quick dudes there had already discovered and flashed it. I didn't believe my eyes but before i came even to post that there is an update there where already reports of people having the home button issue with this radio.

The speed those responses came in shocked me. The guys must have had the issue right away after the flash. This was not normal with the other updates, so i thought i better wait a day.

Today there is reports on the radio thread, that people say they have better 2G signal.

So, better 2G here, Home button issue there. Go figure.

I bet you, HTC increased the signal out wattage again and that makes the device go nuts again. I fear they actually "unfixed" the home button issue.

So i will still hang on to the old radio for a bit and watch whats happening. I have no chance to go back if the radio is sh1t. so this time someone else can be the lab rat. Sorry.
[HTC One S] jahwol:
Bad news ... after 10 days the problems come back

Jahwol
[HTC One S] aardbeix15:
and still no solution for the home button issue. The reception seems to be beter in 2g and 3g mode. Still I'm able te reproduce the home button issue in 'gsm' and 'gsm/WCDMA' modus, only 'WCDMA' mode prevents the home screen from flipping.

HTC One S Android 4.0.4. Sense 4.1 update 2.3.1. stock, no-root, no-unlock.
[HTC One S] martinl8:
I've just got my One S from warranty repair. Now everything works fine and they didn't install new software or something. They replaced some parts but I don't know what does it mean:

Number: 80H01290-00

FRU-SUB ASSY, SAMSUNG, GENERIC COLOR, LCM

Samsung? I guess it's a touchscreen, but maybe i'm wrong.
[HTC One S] Badmiker:
It really sounds like the home button issue is basically a hardware problem.

Yes, changing the software can help, but but this doesnt seem to solve the problem. Correct me here if I'm wrong SG, but the only phones which have been permanently fixed have had physical bits replaced?

The only people saying it's

not

a hardware issue at all are HTC...

The same people who say that changing to GSM only fixes the problem.

IMHO there's enough evidence here to say that HTC have supplied

physically defective

handsets and are now trying to deny/cover up the problem. I cannot believe that, just when HTC need to be keeping customers and rebuilding their brand, they let cr@p like this go uncorrected and allow public threads like this one to continue. Last HTC for me; I doubt they'll be in business when my renewal comes round.
[HTC One S] zoesdad70:
I wonder if that's the whole screen assembly, complete with capacitance buttons.

FRU normally means Field Replaceable Unit
[HTC One S] opiswahn:
Some news from me, finally i had my phone replaced by Arvato. Not one of the new build-lines (>SH/HT25) as i asked, still an SH23, but the day is nearly over and i havn't got the problem so far. Even back at home where i had the problem constantly, nothing. Let's hope it'll stay that way. It came with 1.78 installed.

The only thing that i think might be different is thet the lower antenna cover is a little bit 'thinner'. On my old handset i noticed that the antenna cover was just a little above the rest of the body, now it's perfecty even.

Could just be a coincidence, but who knows. I'll keep you up to date.
[HTC One S] Sneakyghost:
SH26 serial is already in the report. SH25 also. HT25 was, but I lost the only one report when someone messed up the paper.

But all it tells us is: The issue lives in all versions.

Thanks for reporting back.

---------- Post added at 02:16 AM ---------- Previous post was at 02:09 AM ----------

it will be. The whole freakin thing is assembled on one piece of glass. Hard to just replace the panel. Watch the disassembly videos on YouTube.

Looks more and more like the hardware component is the part that needs the real fix, doesn't it?

I was hoping all the time that this might be overcome by a soft fix but I think badmiker has a serious point there. In the end, it's the hardware fix that seems to do the trick.

[EDIT]

Oh and by the way: on the "S3 for S4" thread is enough evidence now that we will definitely get an S3 replacement when stocks run out. Some people are already getting the S3 in returns.

Very bad. I don't want a hardware fix already for that reason.
[HTC One S] :
What's so bad about the S3 version?
[HTC One S] opiswahn:
Older processor, overclocked to 1.7 GHz to machtes the S4s power, but, due to overclocking and older architecture, it consumes more power and lacks some capabilities.

That makes it in any way inferior.

**Edit**

Sure, but it seems to occure less frequent in the 25/26 series. The focus seems to be on 23/24. That's why i requested a new phone from a new series. But, well, as long as it stays fixed i don't complain ;)
[HTC One S] aardbeix15:
Do it yourself hardware fix for the home button issue:

this morning with a potato peeler very carefully the lower antennacover 2mm lifted on the bottom and sides, very little. 3 sides so long, not on the long side 'top' in the back. Then lightly pushed back. Space seems slightly larger than before the operation.

Just 60 km ridden with "GSM only" and now my work with "GSM / WCDMA auto ', navigation, talks and chat on my drive. Before I had the hoem button issue sometimes on the road at my work it was very worse and the phone was unusable, for now still nothing..........

The problem is with me even after two months arise, perhaps when there has been some pressure on the antenna cover. It seems therefore a hardware issue that perhaps with a different cover or antenna layout can be permanently solved. No quality build HTC!

So entirely at your own risk but it works for me now tentatively.

If I have HBP again I let you know directly, but so far so good.
[HTC One S] Sneakyghost:
There was that guy here from Belgium who also took the cover off but i think he didn't get it back on properly anymore. I wonder if i should do that. I probably can't send my device in anyway. Haven't made up my mind yet though.
[HTC One S] aardbeix15:
so my luck I did not pull of the cover complete. As said I only lifted it for 2mm on 3 sides and then gently pushed it in a soft way back again.

Still not a sign anymore of de HBp on this workplace were it turned off constant the last time.
[HTC One S] mattionline:
That was me :p The repair center installed a new cover for free.

It didn't really fix the problem because it came back after a week or so.

It happens less frequent now so it's acceptable :)
[HTC One S] stupot123:
Hi All

I was on 1.53 for one month with no problems at all until I decided to update to 1.78 what a mistake.:( The first day after update the problem starts up again.

The 1.78 update has to be a part of it. Have to wait till the 2.31 update and if that does not help I will sent for repair.

Stu
[HTC One S] Phuturist:
Just when it started to look like a hardware problem ... :D
[HTC One S] Badmiker:
It is not so odd. The flicker fault has never been fixed by software, but 1.78 seems to make it worse on faulty devices.

SG's experiences flashing the phone is interesting: when the software is first installed everything is fine, but after a couple of weeks the phone fails. Reflashing the phone fixes it temporarily. It seems that the software learns how hard is it can work antennae/buttons, maybe 1.78 improves this process and when a faulty phone is working really hard, it starts to flicker.

Judging by the "Galaxy Nexus Volume problem is hardware related" thread, the problem is the shielding of the buttons. Maybe there's a bad connection to the button shielding on some phones?

I would love to see behind the lower cover (I dont have the tools or experience to take it off) I might have an idea what to look for, if anyone has any pictures?
[HTC One S] Sneakyghost:
Cool Idea, Badmiker.

I'd much rather think its an assumed micro-gap between Cover and Springs so the connection isn't good and in return the phone increases the output wattage. Thus also being a worse battery drainer than the other phones and having a flickering screen. My theory so far.

Why am i thinking this? Because i know the HD2 already had the issue with its wifi Springs and cover and most obviously now, the HOX with its wifi springs. I tend to think that HTC has a general engineering fault going on here. They should opt for a different connection technique. My opinion...
[HTC One S] Beatnix1:
http://www.youtube.com/watch?v=1lBT15PgpYw

http://www.youtube.com/watch?v=b0jGY2N2h1U

maybe this can help
[HTC One S] aardbeix15:
:( got it once again. But first I had it 100st of times a day and now once. My operation did improve it, not completely.
[HTC One S] Sneakyghost:
Cool find :)

Current video is really good, second one is already linked on OP.

Second one also shows the us model. It's slightly different.

I will add the first video to the OP as well soon. I think I might actually goo for a repair try myself sooner or later.

I hate no-one doing it. So I will. Not yet though. Too busy with viper one s currently.

Bitten by One S Viper...
[HTC One S] aardbeix15:
It occurred only once for me no, first I had it a dozen times a day when not set to WCDMA, after 1,5 day I can definitely say my self repair action was successful.
[HTC One S] Sneakyghost:
Now look at the report sheet, guys. The 2.31 Updates come flying in. That Radio is **** i tell you.

After the 2.21 Update it had been pretty quiet, hardly any reports.

I am nearly sure now the 2.31 base and radio are **** for the Home Button issue. I am not updating the Radio for sure. I am on latest base now with Viper One S but the radio will nicely be staying on the older one... :D
[HTC One S] guigz2000:
Damn....lucky french ota servers are slow to make 2.31 available....my phone has had no 3 button issue for 3 weeks with 2.21.....i'll stick to it...
[HTC One S] pierre.grand:
2.21 received in OTA

On this forum:

http://www.htc-hub.com/htc/actualites/htc-one-s-mise-a-jour-sense-4-1-disponible/comment-page-5/#comments

TaGuéli is saying that he received the 2.21 in OTA, he didn't use a RUU to have it.

Now he is not receiving 2.31

theory here:

Could it be possible that HTC have deployed 2.21 on phone that have reported Home button issue ?

Could it be possible that 2.31 is not planned to be deployed to these phones?

Is HTC aiming specific IMEI with OTA(didn't know it was possible)?
[HTC One S] Triton11:
I've been following the home button issue (on the HOS) topic in several threads in different forums (xda, android-hilfe.de, pocketpc.ch) for about two months now.

I first had the 1.78 base (stock) on my HOS. At the beginning everything was ok. Then after maybe two or three weeks the home button issue occured. It got worse so that it was almost unusable. Two weeks ago I decided to flash the 2.21 RUU. At the beginning, everthing was great, the home button issue seemed to be fixed. But today, it started again. The circumstances (area, way of use, ...) are the same, I haven't been in the holidays or something like this.

What I think about it: Unfortunately, the home button issue also occurs with the 2.21 base. What is strange about the whole thing is, that the phone works well for two or three weeks before it goes mad. Considering this fact, shouldn't it be possible to fix it with a software update? What I mean is that the home button issue seems to be a hardware problem, but might be fixed with software update owing to the fact that it properly worked for some time before it started flickering.
[HTC One S] jbolts:
Jus to remind Samsung Nexus S had the exact same issue and they never even admitted to the problem

The only ones that were really lucky were the ones who had a walk in Samsung service center and happened upon a good technician.

Neither Samsung nor Google ever truly admitted to the problem and everyone got the same runaround and nothing was ever really done about it.

When enough devices are not affected by a problem and it's not really worth there while to look into fixing it the bottom line is that they don't bother.

bolts

---------- Post added at 06:48 PM ---------- Previous post was at 06:38 PM ----------

The haptic buttons are indeed part of the screen

Thats how Samsung fixed my Nexus S with similar issue with search button

I'll say it again only a hardware repair will fix the problem 100%

bolts
[HTC One S] opiswahn:
well, after 3 days with the new phone and without any issue i got struck again today, in an area wehre i had no issues before. So the Problem isnt solved, just reduced... Now what? Grmph...

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] zoesdad70:
Is your phone still on 1.78 or did you get an upgrade to 2.21 or 2.31?
[HTC One S] opiswahn:
1.78. And its a Vodafone branded phone, so the Update will come some Time later... :(

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] Sneakyghost:
Not quite, but nearly :D

The OTA runs to specific IMEI Numbers and/or regions.

The 2.21 had been rolled out in northern Europe first according to HTC.

The 2.31 seems to be intended for all phones now, but is still rolling and they do it area-wise, so not all get it at the same time.

I suppose this serves two ideas: 1.) have control over the feeback rolling back in (too much if rolled out worldwide) and keep a chance to react if things go badly wrong, 2.) Server load. Save costs.

According to a Technicians statement i heard about, both 2.21 and 2.31 include a "fix" for the Home Button Issue.
[HTC One S] Laurence93:
I do hope the update comes soon; sending texts is a nightmare. I can happily use the phone for most tasks without a problem but soon as a text starts coming through it goes crazy, same with sending them.

@Sneakyghost - I suppose you don't know how long it could possibly take for the update to be finished rolling out, like 1 - 2 weeks or? (Unbranded phone - UK)
[HTC One S] zoesdad70:
My phone (1.78) is getting worse - I couldn't use it at all for over ten minutes this morning because of the homescreen problem. I finally managed to get in and switch off mobile data.

And this comes straight after the phone came back from HTC: Seems they did absolutely nothing to the phone except keep hold of it for a week and send it back to me with some cosmetic damage! They now tell me to sit tight and await Vodafone releasing the 2.31 update.
[HTC One S] shoffobroff:
My phone is officially unusable so I'm sending it back. They said they recognized the problem and to send it to them for repairs.

Id say for people to start sending their phones back. I'm sick of hearing HTC's bulls**t excuses about waiting for updates.
[HTC One S] Sneakyghost:
Well, HTC said 4-6 weeks, which are half finished.

I swapped CID yesterday and updated to the latest radio. Seems ok for now...

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] Phuturist:
Why swap CID and not just update from the available OTA zip file?

I'm on vacation right now but will probably update to radio 2.31 when I get home as well, would be nice to know how things evolve over time with the new 2.31 radio.
[HTC One S] opiswahn:
Seems to be the best thing to do. Even though my phone isn't 100% repaired, it's kinda acceptable now, i'm getting the issue max once per day and only for a very short period, and that in areas where i had it constantly before.

And since it came back with 1.78 installed(as it was before) it kinda proves that it must be a hardware-issue. They say they swapped the phone, but it's still a SH23 serial.

Now i feel the urge to install a custom ROM, but i'm afraid it will get worse after it ;);)
[HTC One S] zoesdad70:
I've been in contact with HTC over my phone and the fiasco of my last repair. I've been told that repair turnaround currently stands at 7-10 working days - Up to two full weeks! Where I live, the phone takes two days to get to them plus two days to get back, so I'd be looking at three weeks without my phone.
[HTC One S] Pulsik:
For those, who wanted to try 2.31, but were waiting for RUU: http://xdaforums.com/showpost.php?p=30902675&postcount=30

But as for me, I'm still on 2.21 and don't want to upgrade as it wont bring anything major and can only recreate the home button issue. As for now, it still didn't appeared on 2.21.
[HTC One S] aardbeix15:
just did a factory reset on 2.31 and I was able to reproduce the home button issue within an hour. No constant but it is still there.

This morning the support guy of HTC Netherlands confirmed a OTA was on it's way and that this would be a number higher then 2.31. No release-date known yet.
[HTC One S] Sneakyghost:
I've updated to 2.31 and the phone is absolutely fine so far.

And regarding "nothing major" I do disagree. It brings sense 4.1 and that makes the phone considerably smoother and is all in all a very nice upgrade.

But you can of course have that if you use venoms viper Rom and keep the old radio.

[EDIT]

Spoke too early. Just had another incident on the new radio and base.

Will see how this develops.
[HTC One S] TheEndHK:
I ran 2.21 RUU and flashed TD 7.0 rom since then I never have the home button issue again.
[HTC One S] zoesdad70:
How long ago did you flash the phone? My second handset was problem free for about three weeks before the problem started showing itself. This has gradually got worse over the last month. This morning, mobile data and wireless were switched off and still the phone buzzed and locked the buttons out!

When I spoke to HTC the other day, the HTC bod assumed that my phone was running 2.21. When I told him it was still on 1.78, he admitted that 2.21 only fixed the homescreen issue for 60-70% of phones and that he was going to ask me for some screenshots of info from the phone. Thereafter HTC have refused to help until I get an upgrade. I'm on Vodafone UK so I'm in for a bit of a wait. Their support is a joke, relying on customers to support each other rather than having any proper technicians involved. When you ask the vodafone staff for information, they either ignore you or give a generic 'we're investigating' answer. They've been investigating the homescreen issue for the last four months, haven't been able to replicate it and have their 'fingers crossed' (their words!) that the update fixes the problem. They cannot tell us if they've received the update code from HTC and so cannot tell us which version it is. Neither can they (or will they) tell us anything about their investigations.