yashsingh1/xdaforums huggingface dataset:
[HTC One S] Sneakyghost:
Agreed. It most likely is fixable by a software-only fix. We had said that a few times.

Yet, there is some good hints (see my above post for example) that it might still be a combination of a hardware malfunction and a software problem.

Only after the 1.78 update came, most of the people began to report this.

Some where having it on 1.53 already, like me.

so, there seems to be at least different levels of severity. Now, a software change made the trigger level lower, more people have it.

Due to the nature of this 900MHz interference with the capacitive button electrodes (provided, this is the reason) it can be influenced/manipulated both by software and hardware. This would be:

- Software: changing the jitter tolerance in the button driver, meaning, adjusting the trigger level from a high sensitiveness to capacity changes to a lower sensitivity. A google Engineer called that a "bounce rate" which is used to distinguish valid finger proximity from electronic jitter on the mainboard. This jitter on the mainboard gets drastically increased by some 900MHz frequency. So, the bounce needs to be adjusted. The electronic jitter on a small assembly is normal and science has put a lot of effort into mechanisms to distinguish it from finger proximity. It is a tricky business and easy to fail on.

- Hardware: if there is anything in the hardware interfering with the reception/sender Antenna, the phone will try to compensate bad signal by increasing output wattage. This will immidiately stimulate stronger jitter on the assembly circuitry. Thus it will directly influence the button electrodes if the Antenna circuitry is close by the button circuitry. Which it is. SImply put.

I see this as an unlucky combination of a bad design (circuits too close together), failing hardware (e.g. Antenna cover not fitting tight enough), and a badly adjusted driver.

Note: this too is just an opinion and i am no engineer, i just did a lot of googling to find out about the specifics with capacitive button electrodes and microwave interference. So, while this theory might not be right at the end, i think it still holds some value. It is also the reason why people keep thinking it might also be something with their hardware. I had outlined this theory already at the beginning of the thread. I am unsure whether or not you read it all but there is some strong evidence pointing towards an unlucky hardware/software combination which can possibly be overcome by a sole software fix.
[HTC One S] martinl8:
I've just called to the HTC. They told me that they know about this problem and they told that people should report this problem straight to the HTC helpline. When you're calling you should have an IMEI number. More reports = faster update. Also they said that they don't read our reports documents on google so it's important to call them.
[HTC One S] DeGon:
Inspired by Martins post I just called the HTC customer service in Switzerland. Although there is a swiss contact number for their service desk I was sent to somebody somwhere (as it is in our globalized world). The woman, who was quite friendly, just noted all the necessary details like IMEI, Baseband, BuildNo.

At the end of the call she told me that HTC had already sent out an update which should fix this issue. I asked her when that should have happen. She told me that it was around 2 weeks ago (but she did not seem to sound so sure). She also said that it was first rolled out to users in Germany and because I had a branded version it could take a bit longer to reach my phone. She finally proposed I should maybe ask my local provider (Swisscom) when they plan to roll out the update for the branded versions....

bizarre... could any high ranking and responsible person from HTC make clear and true statements please?

:confused::confused::confused::confused:
[HTC One S] Badmiker:
Posted 30th May

So that's over 2 months worth of exactly the same response from HTC. (It's also a standard response to say "It's not our phone's fault; it's YOUR apps.")

Anyone who blindly believes what they are told by HTC is being, at best, naive IMHO.

I'm totally with SG here; it's fundamentally a hardware issue (hence why it varies between phones) which is exacerbated by over touchy software. I'm sure that a software tweak would solve it for 90% of faulty phones, but why would HTC do that if the same tweak reduces antenna power for unaffected phones?

Nor are HTC going admit to a to a hardware fault and having to go through the whole process of recalling some/all phones.

It makes much more sense to just quietly replace/repair any phones which people return to them. They even previously offered to repair my rooted phone 'out of good will' despite telling me that I had voided the warranty.
[HTC One S] Sneakyghost:
Well just to avoid misunderstandings: i am not 100% sure this is fundamentally a hardware issue. My opinion tends to this being mainly badly tweaked drivers for the capacitive buttons and a bad hardware makes that visible. Not vice versa.

I am very sure from what i have read that pretty much any and all phones/devices using capacitive buttons and placing electronically speaking strong other hardware beside it are prone to have this happening. The only way to avoid this is to fine tune what that google engineer called the "bounce rate".

If now the hardware leads to stronger emissions by whatever fault, this bad tuning becomes visible.

This and nothing other is my opinion.

Following this, the result would be a software-only fix.

Looking at the issue the other way around, a software fix would be a lot less likely.
[HTC One S] pierre.grand:
I reproduce HSM syndrom even in safe mode.

https://docs.google.com/open?id=0B8Azrm4XviE6LUFDNkhYakM2eXM

I'm in 2.21:

https://docs.google.com/open?id=0B8Azrm4XviE6aXBqUDFfX2VuSWc
[HTC One S] zoesdad70:
I emailed HTC UK and they offered to take my phone back for repair! Nice to see consistency here!
[HTC One S] opiswahn:
I'm finally also moving forward, HTC told me that they would replace my phone, but since it's vodaphone-branded i have to speak to my seller.

They made no fuzz and send me a repair/replace-form to fill out and send the phone in.

We'll see how that's going ;)
[HTC One S] DeGon:
Would you please all mark it as "Newsworthy Thread" on top of the page? I do think that HTC will only release an official statement, if somebody writes about it. So it's necessary to create a bit of a buzz.

Imagine this problem happened to an iPhone: Tech Blogs would write hundreds of posts about it. I haven's seen one post about this problem except forum posts.

So if you own a tech blog, why not writing about this?
[HTC One S] opiswahn:
Because the OneS is no iphone ;)

I think the OneS sold only a fragment of what the iphone was sold, so the number of people concerned is pretty small, if you look at the whole picture. I think if the problem was on the OneX, there would habe been a fix already, because the OneS seems to be the shadowed(and completly underestimated) evil twin of the OneX...
[HTC One S] pierre.grand:
I don't want to disappoint you, but I had twice this answer from HTC but when the phone arrived in their repair cente they didn't recognized the problem and just sent it back. :(

I hope that won't happen to you.
[HTC One S] opiswahn:
Uh, bummer...

Maybe i send them an USB-Stick with a video demonstrating it on my device ;)
[HTC One S] martinl8:
I sent my phone to the HTC yesterday. I could wait few days.. Now i know that they won't solve my problem. It's really anoying that so expensive hardware (for me) doesn't work properly.. OMG it must be a joke :/
[HTC One S] Lamyron:
Ok. Peoples a little review of my repair.

I sent it to arvato and waited 14 days (I think) and then I got it back..... Repaired!

And now I haven't any problems more. So I think it is an Hardware failure. They replaced a lot of stuff, why they should do that if is a software problem? I don't want to destroy any hopes but I think htc don't know what they should do.

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] martinl8:
What kind of stuff? Motherboard?
[HTC One S] Lamyron:
Read here please http://xdaforums.com/showpost.php?p=28247274&postcount=211

Mainboard is one of this ... yes
[HTC One S] Sneakyghost:
i have encouraged people to vote the thread up in the past but obviously XDA Team does not consider this newsworthy.

The media is not interested. I already checked a few options. I also moved away from that because we see that HTC is trying to get it done. I'd think that a mean move at the current stage. Don't think it will speed it up at all. Just makes it harder.

If its gonna last another 2 month i might reconsider the Media/Press option :D

---------- Post added at 10:07 PM ---------- Previous post was at 10:04 PM ----------

Thanks for checking back mate. I had your previous post cited here a few times. Your foto of the repair letter really told a long story back then.
[HTC One S] stupot123:
Hi All

I am looking for some advice I updated my first phone to 1.78 the first day I got it. after 10 days the phone went mad. after three weeks I went to carphonewarehouse and got a replacement. I decided not to update this phone still on 1.53. I have had the phone three weeks and the only issue is that the other day I switched on edge at the same time I had no bars and the phone rebooted itself, this happened twice. It has not happened since.

1 Should I stay with 1.53 and see how it goes and wait to see if there is a fix for this from HTC.

2 should I update to 1.78 and see what happens

3 Should I try and get HTC to change the phone.

Your advice would be welcome
[HTC One S] Beatnix1:
number One or switch directly to the newest Ruu. i had that Problem after Upgrade to 1.78

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] Sneakyghost:
:D if that was my phone i'd definetely avoid 1.78.

1: Go for 2.21, then, if Problems arise (home button issue),

2: sent phone in for replacement.

Also, the random reboots are another known bug of this phone. I don't remember if the current strategy from HTC is replacement or update, but i think it's the latter. If you tell them you suffer from random reboots they will probably suggest the latest RUU.
[HTC One S] corbie:
Safe mode didn't resolve problem, flickering is even worst than on normal mode. I noticed also last time that even touching cover edges my couse that. That's happens when internet is switched off.
[HTC One S] opiswahn:
Did anyone know about the Home-Button-Issue from the OneX?? http://xdaforums.com/showpost.php?p=29988320&postcount=1

If it's the same problem, has HTC finally found a cure for that curse??
[HTC One S] DeGon:
I think the issue about the X was the menu button, which is displayed as that stupid three point bar on the bottom of the screen, as you know it from the S too. Its fixed with the next update. You will be able to configure the task button as menu button (plus long press for the tasks). No solution for HSM in sight...
[HTC One S] opiswahn:
damnit, that would have been too good to be true ;)
[HTC One S] Sneakyghost:
The Wi-Fi issue of the HOX is very similar if we talk hardware problems. It stems from the back cover not fitting tight enough with the little metal springs of the bt/Wi-Fi antenna.

If we talk about the home button issue as an antenna problem it is actually the same. Not if it's a sole software problem of course.

Sent from my suffering HTC One S
[HTC One S] martinl8:
I think that it's a problem connected with motherboard or bad construction.. not software. The funniest is that HTC doesn't care about it too much.
[HTC One S] Phuturist:
I contacted HTC Netherlands again with the question if I should send in the phone as I was seeying more and more indications that this is a hardware problem. Here is a roughly translated reaction.

So HTC Netherlands seems to think that the RUU update fixes the home button issue. Although it does improve a lot it's not a 100% fix.
[HTC One S] will1987:
What do they say if you tell them that you have already applied the RUU and that it doesn't completely fix it?
[HTC One S] Phuturist:
I'm waiting for an answer, HTC Netherlands is usually pretty quick in their response so I'm guessing I'll have an answer on monday.
[HTC One S] Sneakyghost:
Yes i would recommend to stick with this Inquiry and insist to know what the fix actually is. That other dude a few pages back also quoted HTC with a statement, that the fix is already being rolled out in northern europe. That made me wonder already if they possibly think that the new RUU fixes this. If that is the case, we need to immediately get back to them again, everyone who updated, and tell them it is NOT fixing the issue. That is very important as HTC will otherwise consider this issue solved.

Also, we need to report to the Report sheet again if we see it with RUU 2.21.

NOTICE:

Zoesdad was very kind and changed the Report sheet to a Reporting Form, which can be accessed through the original reporting sheet and the old link. The original sheet is now Read Only to prevent further damage. I am very grateful for Zoesdad's help as i am not able to accomplish this. He deserves a few thanky clickys too now. :D

For now, if you want to report again or change your report, this is only possible by filing a new report, as the old ones can only be edited by Zoesdad or me. You can also contact me if you wish to have your report adjusted. I'd actually prefer this in favor of having a phone reported twice.
[HTC One S] jbolts:
used to have similar issue on nexus S

for those who missed my prior post I'd just like to inform you that there was a similar issue with the samsung nexus s and the touch buttons on that phone.

I was one of the few people that got the phone fixed and it was a hardware issue. Samsung replaced my screen, the buttons are part of the screen and they also replaced my speaker with one that was noticably not as loud as the original.

The nice staff from google (nexus s = flagship phone) kept telling us (yes us there were threads with over a thousand posts) that an ota update was coming and it dragged on for months and no ota update fixed the issue ... it did "help" a little for some phones but it never fixed the problem.

Different radios react differently and I'm not a computer engineer ... but these are very complex little devices and slight variations in resistance between all the doodads they cram into these things cause these problems to occur.

There was one person from north america who reported the problem vanishing while in europe and having swapped out the sim while he was there with one from a european provider.

One thing that was certain the problem occured when the 3g reception was spotty and went from 0 to 1 bar.... thats when the seerch button would fire on it's own(for most people it was the search button but for some it was the home) ....some phones were worse than others .... also when the data connection was disabled the problem disappeared.

Anyhow google pointed the problem at samsung... and samsung pointed to google... most people never got it fixed because they were wating for the promised update which never fixed the problem.

It was a very sad thing to have to expeerience and witness.

Btw ... samsung is the manufacturer of the screen and buttons on the one s .... and surprise surprise same problem... very sad indeed.

I feel your pain and my advice to you is to return your phones asap and dont take no for an answer.

There will be no ota update that will fix this problem... it will only mask it on some phones .... this is talking from past experience

And if anyone tells you to relax and that an ota update is coming i would point them out as being a troll and do not listen to them.

I really hope this helps with anyone who is experiencing this problem and dont listen to htc if they tell you its a software issue

There are probably not enough affected phones from them to really care and take the problem seriously.

I got a 3 year extended warranty from best buy here in canada this time around btw... anything happens I can walk in and they replace it on the spot. Not cheap but at least I know i will have a phone for 3 yrs as long as I dont lose it ...

Get your phone serviced or replaced.

Period.

just my 2 cents... (or several dollars! :) )

jbolts
[HTC One S] guigz2000:
Hello,

I've spent one week in a ****ty reception place in normandie,France, with my 2.21 flashed phone.

no issue at the moment.

Phone kept swapping gsm/3g without problem.

I even used it as a GPS along the 950km to get back home...not a single issue.

Battery is not bad and hotmail sync is fixed..

I just pray it stays that way..
[HTC One S] Sneakyghost:
jbolts,

what you are writing there sounds very sad. I am hoping very much that this is going to have a good end. The Nexus story is a bad one indeed- did you know that another Nexus brought me to the idea about the interference in the first place? Another user, who was/is following this thread dug out an old article about the volume slider on the Galaxy Nexus. It contained the same misbehaviour and also a link to a blog from some google engineer who explained what was happening. So, your Nexus story is now the third Phone i heard about in regards of this problem. It looks like a common problem with capacitive buttons. I had that feeling already when i researched the Technology. The way this works made me wonder why not more phones suffer from it and it also increased my respect for the engineers who work around this. Theoretically, every single phone using capacitive buttons could show this problem. It is a little wonder that not all do actually. It is "Borderline Technology". It borders the realm of the physically impossible. So, big achievement to have it working. On some phones.
[HTC One S] kcmx:
Hi Guys, I have been tracing this topic for some of the times. Just wondering, is any of you same as me still suffering from the touch button does not function after turned into sleep mode? (Well, even it could be not functioning from turning it on.) I am totally a layman for hardware/software. Almost want to kill myself it still not functioning after updated to Ruu 2.21!
[HTC One S] ExDr:
I submitted this issue to HTC support two days ago. Unfortunately turning off the data roaming sound does not help, though couple of days there was no bug - just coincidence I think.
[HTC One S] opiswahn:
I can confirm that turning off the sound doesn't work for me.

I submitted the problem a while ago, but no news till then...

The other problem is: If it's an hardware-issue and you RMA the phone, i think you can't be sure if you get a phone with an S4 back... they seem to be switching to the S3 globaly...

For me it seems i have to life with this bug.. or can someone confirm that flashing a custom rom(maybe with some different radio) fixes the problem???
[HTC One S] azzledazzle:
Mines in the repair centre because of the signal and this issue, What happens if they send me back a One S with the S3 chip ?

Will i be allowed to not accept it ? maybe end the contract ? After all I signed up for S4 version.
[HTC One S] Sneakyghost:
I'd at least try. Nothing wrong with making a solid point on that.

I wouldn't want to be f*** around with either.

I got a phone with a good boody, no chipping, but the Button is giving me headaches.

As of now, factory resetting the LeeDroid ROM seems to have eased it down a bit. Haven't seen it for a day or two now. But i doubt its gone judging by the past weeks experiences.

@HTC:

Guys, go do something about it! (just in case you have someone monitoring the Forums here...)
[HTC One S] zoesdad70:
My phone's in repair

I've suffered this problem every since I got the phone - I bought my phone outright so I'm really disappointed about this fault as it has really taken the shine of what seems a wonderful phone.

Dealing with HTC has been a frustrating experience as the HTC personnel didn't seem to read all the info I provided and then asked for this info in their reply. They also refused to take the call any further until I had obtained a replacement sim card.

My phone's with HTC being repaired since before the jubilee holiday. As I'd heard nothing, I emailed them and got back a message that they are 'waiting parts'. That's not a good sign, as if it is true, then this problem is a hardware fault and means we all need to return our phones.

Interesting to read of the S4/S3 variants of the phone. I'll be double checking mine when I get it back. Would they dare replace the phone with the lesser model?
[HTC One S] wrickwrackwruck:
I can't confirm EDGE only.

Just had the Problem again at home on wifi.

Managed to turn wifi off and had GPRS connection.

Home Screens kept going crazy
[HTC One S] D3LTA:
They can't replace it with a s3 chip, that isn't legally right... is it??
[HTC One S] Shandorkar:
sorry for my english.

I have this issue too, but the signal 2g is perfect!!! when i turned off connection (radio modul) this issue still had.
[HTC One S] Shandorkar:
please someone give me email and help me write grammatically text with this issue for HTC support. my english is bad, but i want to help to solve this issue. you can write me private message
[HTC One S] Sneakyghost:
I wrote this text to HTC, you may Copy/Paste it and alter it to your liking. My english is not perfect either but i think that doesn't matter:

Drop your Report on any of these adresses (there is more if you want to use any localized page, navigate to it from HTC Homepage):

Germany http://www.htc.com/de/contact/

US http://www.htc.com/us/support/email-support

RUS http://www.htc.com/ru/contact/
[HTC One S] zoesdad70:
The media are picking up on this now.

Just been reading The Register and they have an article on this problem as well as a couple of One X problems.

XDA won't let me paste the link as I'm too new around here, but head over to TheRegister dot com and the article is on the front page.

Hopefully many more in the media will pick up on this and act as a swift boot up the backside of HTC.
[HTC One S] Dublinguy:
I have the same problem and its really annoying. I've been in contact with HTC twice, the first time they "knew about the issue" and the second time "never came across it"

My provider (Meteor) in Ireland are a bit sceptical about replaceing the phone as they know nothing about the issue but I'm fighting them all the way on it as its "not fit for purpose". I think if enough people get onto their service provider it might come across a lot stronger from the Vodafone's or O2's as well as users.
[HTC One S] Sneakyghost:
Yeah definitely worth a try, although I haven't purchased mine from the carrier but off Ebay without a receipt, so there is no way for me to go that way unless I try to convince 1&1 to provide warranty by giving them the	IMEI. Bit of a hassle I think.
[HTC One S] Dublinguy:
Well its worth a try. But if people who have the issue with the screen taking "a fit" it might make HTC really do something about the problem.

I just about to copy and paste the letter from above to email HTC support, can I suggest that people do a google search for the problem and there are links to O2.ie forum regarding the same issue and if I may I'll add those links into the email and send it off. The more backing behind this the better.

I think it might be a good idea when you email HTC that you include Items such as IMEI No. Software Version, and other information that might be of some help to them. Just my 2c worth :-)
[HTC One S] opiswahn:
The problem is that the 'normal' callcenter worker hasn't the power to get that problem noticed in higher levels of hierachie.

To be notable there have to be a significant number of people(or people with a more 'heavy' voice ;) ), and it has to be sent to people who can decide if it's an issue worth fixing(eg. economical to fix)

So everybody report to your local HTC-dealer or get in contact with HTC directly and report your problem, not only once, bug them!
[HTC One S] Dublinguy:
Totally agree. I think the "Heavy Voice" would be the service providers, when customers start handing there handsets back as the phone is "Not fit for purpose"