yashsingh1/xdaforums huggingface dataset:
[HTC One S] corbie:
I have the same, happen even on wifi. Sometimes in the moment when text message is sending, or i reciving messages. Still waiting for any good news about working fix. Anyone else try that fix with cleaning connectors and bendings pins under bottom covers?
[HTC One S] Sneakyghost:
Yes i find that normal. My impression is, that the Problem itself is radio interference but that the severity of the issue is determined by a hardware fault.

I think this because: a.) some people had software and hardware patches applied and b.) it makes absolute sense to think that with a bad antenna connection the phone increases emission power and thus the interference is much worse. [Speculation]

---------- Post added at 02:22 PM ---------- Previous post was at 02:20 PM ----------

This is also quite normal. Sending a Text happens with GSM at all times as far as i know. So whenever you send a text, the phone will try to build up a GSM connection, no matter if there's wifi or not. The worst moments are always when the connection builds up. That initial burst of data is usually send with a higher power output ( if i remember correctly).

---------- Post added at 02:24 PM ---------- Previous post was at 02:22 PM ----------

Oh how lovely! That is absolutely fantastic news! It is a very clear statement admitting that the problem is known and being worked on. We didn't have a real quote like this before. So it actually IS good news don't you think?
[HTC One S] opiswahn:
Don't know...

At least it is a clear statement, if you take the words seriously. If that all is true then:

1) HTC knows about this and it's been considered a problem worth fixing

2) It's a problem which can be fixed through software patching, so no hardware replacement is nessessary

3) It won't be long for the fix to arrive.

On the other hand... the mail seems to be some sort of default text they write to every customer on every problem, and the last time i asked(per chat, about 3 or 4 weeks back) the HTC-Lady toled me mostly exact the same thing...

So i don't realy know if the information is of any realy value to us... But still i keep the hopes up ;)
[HTC One S] Sneakyghost:
I don't write a full new letter to each client asking me the same. I pick a template and insert the relevant, altered information. So i think it is normal your letter sounds pretty much default and standard. Important is that bit where Support says the Problem is known. Up till know, most reports from people dealing with support where like: " the say they have no idea whats going on!". There where one or two where the agents knew already that there is an issue but that was not much and we didn't get a real text quote here. I find that very nice now actually.
[HTC One S] Burn-pl:
Hi Guys,

I have received a call yesterday from HTC tech support manager who called with regards to my case. She admitted that they cannot help me with my German T-Mobile branded phone in Poland. She said that I should contact German support with my case. I said that it is totally unacceptable as this breaches European warranty rules. I asked for their headquarter details and got UK address:

HTC Europe Co., Ltd.

Wellington Street

Slough

Berkshire

SL1 1YP

United Kingdom

I am going to escalate my case to their European headquarter and express my big disappointment with Polish support line and their way of handling my issue. I think that all of us affected by this problem should do the same as it is obvious that the 1st line support is not even HTC but rather 3rd party outsourcing company acting on-behalf of HTC.

What is also very interesting, the Polish tech support claims that my warranty is void due to custom firmware installed on my phone. When I stated that it is not that easy to judge without diagnostics in their repair center whether the issue is related to software or not, she said it doesn't matter. So ether way, the htcdev.com site disclaimer is wrong or the 1st support doesn't have specialist knowledge. She just said, well we don't have any clue about htcdev.com website - this seems to be the same as described in the post here http://xdaforums.com/showthread.php?t=1716709

I will keep you posted.
[HTC One S] shoffobroff:
I've sent HTC a support ticket giving a detailed description of the problem, and I linked to the YouTube vid of the problem and this thread and guess what I got back? Try turn the phone off and on again and see if the issue is still there.

:-/

I'm gunna reply and try go into more detail.
[HTC One S] Sneakyghost:
@Burn-pl:

Yes very good my friend. Go escalate the Issue.

I received a call on my mailbox today from HTC Support, they wanted to know why i left bad feedback for the Chat support lady.

They will call again tomorrow and i will tell them that the feedback wasn't for Katarszyna (she was polite and helpful) but for the no answer in 4 weeks thing and for the no information for no user on what the status is.

I will also let HTC know that i will soon go write Emails to all tech related newspapers i know of and ask if they could write Articles on the issues of the One Series please.

I am very happy that there was a statement today that they work on the issue but i am still very frustrated too.
[HTC One S] Burn-pl:
Hi Sneakyghost,

Katarzyna is Polish name - I really believe that HTC support is based in Poland and operated by 3rd party company on behalf of HTC.

I think that we should contact the media and advertise the way how this is handled. Lets try together to contact Engadget, the Verge, Gizmodo, etc...

EDIT:

Maybe our official post on HTC facebook page will change something...
[HTC One S] Sneakyghost:
Not yet mate. They are working on it. Think they still need some time.

And regarding the outsourcing mate: it is very normal to do that. My wife is from Dakar, she used to work in callcenters there for european companies. They speak french over there and serve the whole french speaking world.

There is loads of call centers in poland. They have contracts with loads of companies. Could be that Katarszyna is working for HTC today and for Samsung tomorrow. That is normal and nothing to blame HTC for.

I set myself a timeframe of another two or three weeks. I think by July 20th, around the time when i get my wages, i expect a fix or else i will go buy another phone, although i am REALLY broke as i already had to buy another one because my last two HD2's got smashed...
[HTC One S] Burn-pl:
Hi

I do not blame HTC for using the outsourcing companies. I used to work for Vaio support therefore I know from the inside how the 1st line support works and what are the internal rules. There is a hope for us but the case needs to go to 2nd or 3rd line support.
[HTC One S] Sneakyghost:
Ah ok i didn't know that :D

Thanks for sharing. Looks like you know which way to go then right? :-)

Would you be OK with waiting some 2 weeks more? Give them some time and in parallel try to escalate the issue to their Europe headquarters?

I am so unsure where to go at the moment. I think it might be good to give HTC some time and not get all hysterical but on the other hand these phones are really needed for work by some guys. They aren't just toys. So, for some, HTC really needs to hurry up. So i don't really know. Guess i'll wait for the call from the complaints line tomorrow and see what they have to say.
[HTC One S] Burn-pl:
I would not believe that they work on the solution until we have clear information from their 2nd or 3rd line support. The HTC answers posted above are just simple templates used for difficult customers nothing more. Unless we have clear confirmation that the case is escalated to their engineers we are left alone...
[HTC One S] Sneakyghost:
Are you quite sure about this?
[HTC One S] MRKikas:
I got an response from HTC today, resuming, said that they already are fixing the issue and very soon we are going to receive an update to solve this.

I think this is kind of official now and i will wait some time to see if the problem is solved or not. I really hope that is related to software and not hardware:confused:
[HTC One S] rrrah:
@MRKikas:

If they told that an update will be soon than it is great and we have hope that they do something.

110 people reported, btw
[HTC One S] Burn-pl:
Hi Mate,

I cannot be 100% sure because they may have different rules. However, from my previous experience I can say that whenever case was escalated to the 3rd level support there was some kind of official timeframe when the exact answer will be provided.

What is inconsistent from my point of view - some customers get answer "we are working on the solution' some of us gets "we are not aware about this problem".
[HTC One S] shoffobroff:
Is anyone with a custom ROM having the touch button problems??

It's really cracking me up!
[HTC One S] Sneakyghost:
Of course. I have it on LeeDroid, some German on handy-faq.de reported it for CM9 also
[HTC One S] ExDr:
Unfortunately there is the same issue on customs. I have not tried CM yet but I dont think there is a difference. If only we can flash the 1.53... But with update hboot has been updated as well, and can not be downgraded without s-off.
[HTC One S] Sneakyghost:
I was under the impression, that if you boot the One S from an external recovery.img into recovery, you can flash an older radio because the S-OFF restrictions don't apply then.

I cannot try that at the moment but i would be happy if someone could.

There is a guide here: http://xdaforums.com/showthread.php?t=1684477

If anyone is willing to flash the old Radio from the 1.47 RUU i'd appreciate this.

1.53 contains Radio: 0.15.31501S.19_10.12.31501S.06L --> this has been reported as affected too.

1.47 contains Radio: 0.15.31501S.13_3_10.08.31501S.04L --> this has NOT been reported as affected, yet i don't think anyone is still running that old RUU. So it's only a tiny chance. We also don't know whether or not the Radio has an impact on this at all.

[EDIT]

I quickly checked on the Radios and there seem to be no downloads for the older ones available.

However, i found that extracting it from the RUU can easily be done by launching the RUU, then locating its TEMP directory (For me: TEMP\{3C108E88-EDEB-4A76-B7D0-85C8F6288D38}\) and there find the "rom.zip". From that, you can extract the "radio.img".

Go and download a zip-flashable Radio here: http://ville.giev.de/?page_id=42 then just drop the "radio.img" you just extracted from the RUU into that zip (replace the original in it) and then go ahead flashing that like described in the linked guide above.

The RUU's are here: http://www.filefactory.com/f/cf061f69b5bf7878/

Attention: i have no experience in creating flashable zips. I have no idea if this works. I couldn't test it. Also, i don't know what negative side effects an old radio has with a new ROM. So: you do that on your own responsibility if you chose to help.
[HTC One S] ExDr:
I have tried only RUU 1.53 several times - always with error 155. I have found it was because of new hboot. I am not sure flashing old radio with new hboot does not brick device. It needs to be carefully considered...
[HTC One S] Sneakyghost:
true. but then again, people have been doing it already. it is supposed to work if you look at the radio thread.

[EDIT]

I read all the thread and obviously, it might be difficult to downgrade if on latest hboot/RUU. Haven't quite understood that.
[HTC One S] Pulsik:
Hello,

as you are discussing this bug in 1.53 radio.

I've bought phone few days ago. It's a SH23 phone.

My software number:

1.53.401.2 (this is radio, right?).

And i also have this bug with crazy buttons because of a bad signal.

Now i'm thinking what to do. Go to a shop and ask to change this phone or wait till official announcement?
[HTC One S] ExDr:
Some interesting facts from 4pda.ru mate. 1) Issue started on 1.53, then has continued on 1.78. 2) He had opportunity to compare two devices at the same time and in the same conditions. His device showed the bug, his friend device did not. It made him sure the issue was hardware-based. Now he is waiting for repaired device.
[HTC One S] Sneakyghost:
Well think of what i keep saying: if the interference is only occurring when the signal coverage is low, it might only happen when the phone increases the output power to reach the tower.

So, what could make the phone increase the output power beyond the critical limit? Right. A bad antenna cover for example. Or a lose wire. Or bend metal connector springs.

And what could make the phone go past the critical limit? Didn't we have bad reception for many phones in the first Software? And guess what HTC did to make these phones have better signal? Correct. They might have increased the general output wattage.

I am nearly sure they made the buttons play up by attempting to fix the bad reception.

And since not everyone had bad reception, it might be that the antenna is bad on some of the phones.

and since that is hardware, i totally agree. It could partly be hardware.

Did you read that one statement from Lamyron (He posted a picture from HTCs answer letter!)? It said: replaced Antenna Cover for assembly gap.

Do you know what an assembly gap is? well my english is not perfect but i understand it is a Gap from bad assembly technology.

It could very well be a badly adjusted assembly line that didn't assemble the phones body and cover right.

My theory by now goes like this: when the first batch of phones with bad reception was returned, they either didn't identify the cause of the problem and raised the output wattage as a fix, or they actually did identify the "assembly gap" already back then but thought it would go unnoticed with only a very few phones displaying the touch button issue. This would read: bad, expensive manufacturing error, trying the cheap fix first, then having the mess and needing to do more replacements and a lot of angry customers.

Negative thinking? Yes indeed. I will still wait till around 20th as i said before but then my good will is drained.

By the way: if that theory is partly or fully correct, we would have a similar manufacturing disaster as with the One X which had identical wifi antenna problems (guess what made me have this idea in the first place).
[HTC One S] wrickwrackwruck:
I opted out. Too much trouble with HTC.

Not sure about getting the Galaxy S3, Galaxy Nexus or iPhone 4s though.

I know iOS is much less powerfull but at least it always works in combination with its hardware. unlike HTC One S...
[HTC One S] Sneakyghost:
That, my friend is an arguable statement. I wonder if iOS really always does its job. Had heard to many bad stories.
[HTC One S] shoffobroff:
Ive used iOS for a long time, up to 4.2.3, and no way would I ever go back.

As soon as android bites it doesn't leave go :D
[HTC One S] TheEndHK:
I also have the Home button issuse, always happen on LeeDroid V2.1 and TrickDroid V5.0 ...

Please make a workaround mod for custom rom to exchange the position of home button and menu button. This is not a fix but should be much better because I won't fly to the home screen directly, it is very annoy.
[HTC One S] Sneakyghost:
Old Radios for One S

Hello all,

i have now created flashable zip files for each Radio, partly also taken from that Site i linked to earlier.

You can grab the 2 US and 3 EU Radios here: http://d-h.st/users/sneakyghost

Please someone test this for us. Especially with the oldest Radio, would be cool if that could still be flashed via fastboot booting a recovery :D

UPDATE:

Just found on Handy-FAQ.de that user Beatnix has tested Radio 0.16.31501S.16_2_10.22.31501S.10L, which is the Radio from the 1.84 US ROM. He says he has no Issue anymore but he only flashed it today. He successfully flashed the Tmo US RUU 1.84 on his phone, now he runs a Custom ROM with the US Radio. All good for him.

---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------

Hi and thanks for reporting. May i ask you to fill out the Reporting sheet? i see you have a hong kong flag. Are you using 900/1800 MHz GSM over there?

Would be nice to get some data from you.

Ask for a workaround in some ROM Dev thread. Maybe those guys are at the Button remapping already. LeeDroid has a few things remapped. Maybe you ask there. Also, i had the other two buttons going nuts too. It is definitely not only the home button.

Update 2:

i thought i'd let you guys know that i just bought another One S for 300 bucks because i want to test some things and my HD2 is totally unusable now. So i'll be here with some stories about Radios and such soon. :-D
[HTC One S] TheEndHK:
Yup, I'm in HK and my One S(S4) is an Europe model. Give me a couple of days to check out the problem before I report but I think it mainly happens with 2G/Edge when the signal is bad. Mosts of my time are on custom rom EU1.78 and that ver of raido comes with.

For the frequency part, my carrier:

2G/Edge:900mhz & 1800mhz

3G/H: 900mhz & 2100mhz

LTE: 1800mhz & 2600mhz

My carrier currently used some of 2G 900mhz for 3G/H and some of 1800mhz 2G for LTE because they believe there are very less 2G users now.

LeeDroid is now too busy with his real life so I think he has no time, I'll check out dev threads.
[HTC One S] Sneakyghost:
Now that is a decent report. Thanks. I'd think that with your carrier using mostly 900Mhz, there must be many many more having that Problem in Hong Kong, unless coverage is really good everywhere and the phone doesn't need to increase output power.
[HTC One S] rrrah:
@ Sneakyghost

I really hope that results of radio test will be great. I will try to test it in a few days, when I will have time
[HTC One S] Sneakyghost:
Yeah me too. There is just one problem here: my new One S comes with a later Serial (SH25) and does not show the button problem.

So, i need to wait until that comes up first. Then i will flash the TmoUS Radio. Then i will wait until the problem comes back or declare the Radio a good fix at some point.

If the Problem comes back i might still check on the oldest Radio, which was never reported. That has seriously bad reception though and would be a rather painful fix.

[EDIT]

For booting into Recovery and flashing a Radio, an unlocked Bootloader is required and also that the Recovery which shall be booted into is installed too, so the process would look like this:

1: HTC-Dev unlock phone

2: Goto: bootloader/fastboot, then connect to USB, launch CMD, change to directory where fastboot is (have the recovery there too), type: "fastboot flash CWM5831_Touch_ville.img"

3: then type "fastboot boot CWM5831_Touch_ville.img". That will launch the Recovery from external image and S-ON doesn't apply.

4: in CWM, flash your radio

Note: the zip needs to be copied over to SD from a running Android as the Mount in CWM does not currently work!
[HTC One S] rrrah:
thnx for tutorial) will try to find a laptop with Windows, cuz I have Mac Os X now

[UPDATE]

will try to do everything tonight

How do you think, will US radio work with my EU One S using Ukrainian operator?
[HTC One S] Sneakyghost:
Yes definitely. I have done a fair bit of sifting through XDA and there is various people that tried it and there is no problem to flash a TmoUS to a EU phone. All phones and Radios are identical and interchangable, apparently the only difference is release dates. The WWE and EU Radios are usually a tad newer than TmoUS and thus flashing the TmoUS Radio just means you go back one version. The VilleC2 (S3 SoC) has different radios. Those are not compatible.

I have bad news: i run hboot 1.13.000 and i cannot downgrade the radio. No matter what i try, the flash seems to go about successfully but the Baseband just remains the same.

Until now, there is no solution i think. All people that have upgraded to RUU or OTA 1.78 will probably not be able to downgrade.

It could still be a fault with recovery though, as it also cannot flash boot.img's so it could be that flashing with TWRP recovery could be more successfull. I am a bit tired now and will maybe try tomorrow or so.
[HTC One S] ExDr:
That is what I've been speaking about...

Watching closely your new 1S :D

New facts increasingly incline me to idea of rejection of separate devices
[HTC One S] Sneakyghost:
I'm through two Rom's and all the unlocking, cid changing and rooting this device can have already, but the buttons behave very nice.

Since it has a higher serial number and the hboot date says 20th of April (first reported touch button issues where around that time too) it could be that this device has already problems corrected. Although that'd normally be too early unless HTC became aware off the problems already before the public did and was really quick in fixing it. I don't believe so. I'll just have to wait like everyone else cuz we all know it might take up to 4 weeks to develop. Arghhhhh! *God bless the patient ones*

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] rrrah:
my radio now is 1.78, but will probably try to downgrade it in the morning
[HTC One S] Sneakyghost:
Good luck! Hope you succeed.

I have had plenty of time watch my wife's one s go nuts today and my newer one sit beside it and be fine. Odd impression. I'm sure mine will play up too eventually but for now, this looks bizarre...

sent from the tip of my finger
[HTC One S] opiswahn:
We should get this thread sticky btw.

This is an issue concerning enough people...

*edit* Maybe there should be a separate category for identified (and confirmed) problems with phones... so people wouldn't have long to search if they have issues...
[HTC One S] Sneakyghost:
Do you think so? I was wondering too but I also thought that HTC might deliver an update soon to fix this *fingers crossed*

It wouldn't be necessary then.

I could well imagine that the newer devices aren't even affected.

sent from the tip of my finger
[HTC One S] opiswahn:
That would be nice, but i'd like an official statement from HTC for that. I kinda don't care if they fix it in hardware or software, as long as they fix it. But that's the thing i'm not really sure about. Maybe there will be a fix in another service release at some point, but i think the total numbers of complaining customers is to little for them to make a dedicated hot-fix.

The 'we are working hard on a fix'-statement is pretty old now, and by now i think they want to sit it out.

At some point people will stop to complain because they are sick of it, changed to another phone or got a (hopefully working)replacement from their carrier.

I believe it will be much cheaper for HTC to just ignore the issue and wait until it'll resolve itself, 'course there are not the big numbers complaining (or the missing pressure from carriers or media).

*edit* I think there are much more people with the problem, nut they are either not reporting because they are to lazy, think they are alone, or the problem courses to rare to them(because of good signal area)
[HTC One S] rrrah:
still no luck with downgrading.

HTC did not give any fixes so we have the right to make this thread sticky
[HTC One S] Sneakyghost:
Yeah man that's what I'm afraid of. If the total number of affected devices is too small, the costs for developing a fix are higher than the costs from loss of customers and public image damage. That's why I'm after that list so much and why I'm trying to reach as many as possible because that's the only way to get HTC to work on it: having enough phones affected.

The alternative would be to kick off a big fuss on the media, yet again, the issue is not big enough for a big story.

sent from the tip of my finger
[HTC One S] masca88:
maybe you can downgrade flashing before a rom like leedroid and then the old radio..