yashsingh1/xdaforums huggingface dataset:
[HTC One S] erosman:
samsung here i come then :((

so i think this is it, samsung it will be, to bad i really loved the one s, hopefully someone will port the htc sense fully working on the s2
[HTC One S] erosman:
when the issue ocurs

guys when doeas the actual issue occurs, when you activate your mobile data and the signal is low or also when the mobile data is deactivated and the signal is low on gsm, can someone explain when is really hapening please, thank you
[HTC One S] odl:
mobile data doesn't have to be activated - I have this issue when I'm on wi-fi as well. it happens usually when phone is switching to gsm frequency or between gsm cell towers.
[HTC One S] ip3fix:
Before JB: could happen at any moment, using WiFi or Edge. Or even none of them at times, the only condition being "having low signal".

With JB: until now, only happened when using Edge but, as I said before, it only occurred once since I updated...
[HTC One S] erosman:
htc`s reply to my e-mail

Thank you for contacting HTC regarding a HTC One S.

My name is Rob and I am a Technical Support Agent for the HTC Written Team.

I understand you would like to purchase a HTC One S though you are wary about the issue with it helicoptering.

I would like to reassure you that this issue has been resolved and the update was released many months back to resolve this. To check if your future phone had it simply check the software version. When version 2.38 or 2.31 (depending on branding or not) or higher your phone will have the fix applied to it.

In regards to Jelly bean it has started its release to the One S just after Christmas so this should also be a welcome surprise if you get the phone.
[HTC One S] syzkk:
most people believe its radio related but I also see there are people suggest its hboot version related, as flashing official RUU also update the hboot and since 2.31 some people claim helicoptering has been reduced. would be interesting to see if someone can prove it.
[HTC One S] diggerbucket:
Lack of understanding from HTC, the update from months ago did not fix it.

It "might" be fixed in Jelly Bean which was released at Christmas, it's definitely better on my phone at least.
[HTC One S] Rampage:
Been runnig the virtuous Rom long and never had helicoptering.

Gesendet von meinem HTC One S mit Tapatalk 2
[HTC One S] zulmaslet:
Well I received my phone back this Monday from repairs, again with a new screen. At the moment still no coptering but still to early to say ofcourse. I've installed the JB update already. Keep you posted
[HTC One S] kajukas:
thinking about buying this phone (with S4), but really afraid of this bug, how to know if it will appear or not..
[HTC One S] erosman:
same dilema

i have the same dilema like yours but i think i will be getting the one x instead, is a bit bigger but at least it is working properly, if you get the one s buy the grey one as the black one`s paint is chipping of at the top of the phone, so another problem with this phone :(
[HTC One S] flex420:
what country you are living in and how long did it take to get yours back?

have to send mine in i guess -.-
[HTC One S] zulmaslet:
I'm from Belgium, here it takes +/- 10 days but it depends for me it was 1 week. They come and get it at home and if you're from Belgium they repair it in the Netherlands at dynafix. Atm its still holding strong but don't want to say it to loud :) since its basically 1 week I received it back. Greetz
[HTC One S] RichJo86:
Just as you guys experienced, my helicoptering bug changed into the Google Now bug. Great job HTC!

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] erosman:
new mail from htc about jb update

Thank you for providing me with the additional details to enable me to resolve your inquiry.

It’s always our aim to ensure that our customers’ issues are resolved first time and I’m sorry that this has not happened in your case.

It people have received Jelly bean and still haven't received the fix from us this can be one of two reasons. One is that there phones might be branded to a network. When HTC releases a update it will go to all unbranded models and networks. When it goes to the networks they have there time to review the update and make any changes they wish, they also control the release of the update. This can be very inconvenient for some so I may recommend getting a unbranded model for yourself if you do buy one. The other reasons is they may have received the update but not installed correctly, of which they would then need to contact us directly to help further. This could result in a repair to get the ROM flashed.

The issue appears in the default ROM that came with the phone. It conflicting with the signal on the phone as caused the phone screens to do its own tasks switching between screens. The stronger the signal the worst it got.

There was a work around for this that was the following:

- Like your making a call.

- *#*#4636#*#*

- Phone information.

- Change from WCDMA to GSM.

This however is not used anymore as the update has been released by HTC.
[HTC One S] Dublinguy:
So am I to understand that people are still having the same problem even after getting there phone rebuilt and updated with Jellybean 4.1.1?
[HTC One S] Laurence93:
Yup, mines off for it's 3rd repair by 'a senior engineer' tomorrow. (After being updated, then sent back again to be rebuilt + updated)

Fingers crossed it comes back working this time.
[HTC One S] Sneakyghost:
Bullsh!t.

No hboot dependency. Common people. At least read post one before jumping in here. I didn't work my A off for nothing.

There's no freaking way to reduce or remove the issue if the phone has it with a certain severity.

The critical severity to make it unfixable can't be told up front, you only notice when repairing and/or updating it.

So the only thing you can do is:

- update, if not fixed:

- repair, if not fixed:

- repair, if not fixed:

- repair, if not fixed:

- complain and press for a replacement, hope you get a new phone and not a fourth and fifth repair...

The level of frustration this is causing is unimaginable.

sent from a phone
[HTC One S] Sneakyghost:
Correct :D

As expected, nothing has changed.

Lol. Updated and rebuild by a senior engineer. Hahaha. Makes me laugh.

The best Agent this year was... Mrs Katarzsyna from Poland!

Congratulations! You have been promoted to Senior Engineer since you have pissed off most people this year! Keep the pace up, lady!
[HTC One S] Dublinguy:
It makes you wonder how much it costs for HTC to courier a phone from the owner to the repair center...to have it "repaired" (so far battery replaced 3 times, screen replaced 3 times, rear case twice, ear price and holder?? plus labour) and couriered back, not once but 3 times, and the major incontinence of the whole issue....I'd love to know the total cost of my repair as against just replacing the god damn thing? And myself being a happy HTC customer...NOT!!!
[HTC One S] zoesdad70:
I wondered that too: The cheapest UPS option was used, but even somust have cost a pretty penny. My One S went for "repair" four times and then went back a fifth time to be replaced. The cynic in me makes me wonder just how much Regenersis charge HTC for each repair; their incompetence means they have a licence to print money!
[HTC One S] :
Guys I just read that after jb it no more helicopters it opens Google now ! So have you tried disabling google now ? I think it will result in something else
[HTC One S] RichJo86:
Probably just opening Google Search. To test I disabled Google Now and set the phone to GSM/WCDMA.

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] Phantom Pt. II:
This is odd. I think I've seen this issue on my sisters Galaxy S
[HTC One S] Rapier:
Almost 2 weeks passed with my new One S, time in which I've tried to learn the differences.

Now I can say my phone is indeed built for Tmo DE in December even if I bought it from RO.

I never faced till now any "home button issue", being it with or without wifi or mobile data turned on or off. Neither on the stock ROM, nor on the updated JB. Since I'm on hboot higher than 1.09 (1.14.002), I flashed a custom ROM based on official release (Ville + by Zarboz). I've been in areas with poor signal (we have such shielded area in my office building) and I've played alot with the phone to see if I get any issues. I had 1 or 2 bars on GPRS and I didn't noticed any strange behavior all this time (hope I won't have it from now on also, fingers crossed)

Don't know if they were changing something in the latest built phones or it's just due to my carrier frequency or other reason, but till now everything is perfect

Sent from nowhere over the air...
[HTC One S] Sneakyghost:
As I wrote many a time here: phones from June 2012 onwards have modified hardware. I even have separate reporting sheets for both in the OP.
[HTC One S] Sneakyghost:
I would have thought that odd too but I learned a while ago, that this was first observed on the galaxy nexus. Then on the galaxy s...

The nature of the issue makes it very likely that any phone with capacitive buttons can theoretically have it...
[HTC One S] yz250il:
3.16 OTA Helicoptering

Hey, about 2 months ago i updated to the 2.31 update, since then i had no problems with the home button helicoptering(was rubbing CM10 and ViperS 1.21).

2 days ago i got the 3.16 OTA and already two times i got the helicoptering .

just an update.
[HTC One S] flex420:
my phone has serial number starting with SH26..... but i got the helicoptering since i have switched from O2-DE too T-Mobile.de even worse. The JB update reduced it a bit, but in some locations, its even MORE helicoptering then before. With " Edge " and full reception its very bad, not only with no / real bad reception as it was before....

so i guess i have to send it off wich i will do the next days .... im from germany, how long does it normally take to get your phone back from Arvato?

greets and happy new year

edit:

what do i have to mind when i send it in? wipe the phone complete?`- do i have to relock the bootloader and install the original recovery?
[HTC One S] majkyke:
It is therefore of chances when I buy HTC One S made ​​later than Jun 2012

I will have no error "Helicoptering"

Remove this error?

Thanks.
[HTC One S] :
May not have ! don't be sure , chances are still 50% , I never had this bug. And I really feel bad for those who have it , its such a nice phone , one x users prefer one s ,quite a many do , benchmarks on jellybean have left one x far behind .
[HTC One S] Sneakyghost:
Never 50%, much less. Never so many. I have only 15 reports from the newer devices. That is NOTHING really!
[HTC One S] thanito:
Happy new year mate!

Well, I had an SH26 device and the update just made the helicoptering a Google Now bug, but the frequency has become really low compared to the helicoptering issue. but after the miainboard replacement my device has a MB238 serial or something, just my $0.02
[HTC One S] flex420:
ya same here. i will send it in, as soon as somebody can tell me if i should relock the bootloader or not :D
[HTC One S] Sneakyghost:
Relock, run RUU, leave it empty, don't set it up.

That'll be ok. I sent it in like that. Probably they don't even care if it's unlocked or not...

sent from my phone
[HTC One S] Laurence93:
Most helpful conversation ever. Guessing i'll find out in a few days what's actually been done then.
[HTC One S] Sneakyghost:
Lil' update from my JellyBean doings:

Tested JB Roms and stock OTA on all sorts of Hboot/Radio/Extra Partitions combinations. Thanks to the Brick Downgrade Tut (took me 2 weeks to overcome my fear and brick the darn thing) i could finally manage to go back down to 1.06 hboot again and flash all sorts of things to the phone.

The result out of this is: The Home Button Issue or Helicoptering is mostly as bad as ever and doesn't go away in the slightest.

I can thus confirm what others have been writing, plus underlay it with some solid cross-testing. Neither Radio nor System do any helpful thing to resolve the issue on stronger affected phones. However, for some it did help. It is still worth a try.

What i did notice too (to my absolute dismay) was a heavily tweaked GSM/EDGE connection behaviour. At low signal the Data Connection drops much earlier. When the Signal goes towards zero, the drop threshold is much higher too, so it will drop the phone connection earlier than it used too. This effectively means: even less areas where i can actually use my phone.

Currently i am trying TrickDroid 9 and am also having severe data-switching issues, from Wifi to Mobile Data takes a while to pick up, allthough showing already connected. SOmetimes it takes a minute or more to actually transmit any Byte, so many apps report a Network-Problem. From mobile Data back to wifi seems a little better but its not good either.

This might be due to TrickDroid but i actually doubt it as TrickDroid is very close to stock. There arent't many mods in there.

I am once again disappointed, although i did expect this.
[HTC One S] zulmaslet:
Little status update : I received my phone back around 2 weeks ago and atm ( fingers crossed ) I had no more coptering / or something else. Only prob I had these 2 weeks is that my SIM card for some reason wasn't visible anymore for my phone ( happened 2 times ) so I needed to pull it out and put it in again. Dunno if this is a new issue or if they did something wrong. But I'll keep you guys further informed if it comes worse or if it goes away. Otherwise of to the next repair.

Greetz
[HTC One S] Flemmard:
Hi,

Just to make you know, i updated to latest RUU (JB) of Ville, for me it fixed the issue .. :)

Hope this helps !

Don't know if it's radio, hboot etc .. but it does it :)
[HTC One S] dev997:
I'd really like to give it a try .. can you please guide me to which RUU you are talking about ? its for EU Ville right ?

Also I'm on a custom rom , so do I need to follow any additional steps before flashing RUU.. sorry for the dumb question.:good:
[HTC One S] Sneakyghost:
You have to run the latest RUU for your phone (2.31 for WWE for example) and then check for the OTA. There is no JB RUU available currently.

The only branded phones that already got the update too are O2 Germany as of now, at least that's the only one I've seen HTC post about on Facebook.

If your phone has a wrong CID for the ruu you chose, it will simply not run but throw an error. So it's not dangerous.

Before you can run a ruu, relock the phone with "fastboot oem lock".

Sometimes, a RUU won't run if it finds a custom recovery, so it makes sense to flash the stock recovery before the relock.

sent from a phone
[HTC One S] flex420:
Worte htc. Waiting for the answer. Hope they will offen a Service at. arvato soon. Sick of that Bug..
[HTC One S] Sneakyghost:
Hi Flemmard,

honored to see you here in my little playground. Have heard your name mentioned a few times. You work with the Virtuous Team, right?

Well, let me state this as a response to your positive:

- Stock JB with all elements flashed (OTA) does not resolve the bug, changes its behaviour a little, mainly pulling up Gnow all the time as that has been set to long press home (same action call as on all ICS ROM's before which where based off 2.21 or higher), but being less persistent, always returning to normal by itself, which was sweet. The Occurence rate was raised drastically again though compared to the ultra low 2.21 based stuff. 2.31 firmware was already worse again on my device.

- Modified JB stuff: i tried all sorts of combinations from low hboot with high everything to just low everything with just selected few partitions updated like radio, adsp, wcnss, system etc. I am switching around pretty much everything at the moment and the results are utterly frustrating to say the least.

The second worst result i am currently having with the US radio flashed and the EU wcnss and adsp partitions (Wifi or Extra Partitions). The "baddest" result ever is with the 0.15 Radio from EU 1.47 base. It is killing me. I cant use the phone whatsoever, it keeps rocking the screens fast and doesnt stop...

Now back to some decent radio. Think the 2.21 Radio still does the best job... [EDIT] Yes it does. Medium reception but hardly any Seizures this morning on a 70k ride through different coverage areas. Perfect.
[HTC One S] flex420:
thanks for your testing and sharing with us. ever considered to change your mobile operator? i had o2-DE and the bug was gone with update 2.35? (4.0.4). when i switched to tmob-DE, things got worse. Wondering if Eplus-DE would help or Vodafone. As soon as HTC answers my mail and offer a service, ill sell this phone to a friend and getting a nexus 4 i guess ... :(
[HTC One S] Sneakyghost:
OP updated!

Thanks. I am on O2 and mightily p*ssed off with their really ever worsening service (been with them since they came up as Viag Interkom in the late 90's) and the never increasing coverage, so i am quite short of changing to a "D-Net" based carrier, most likely 1&1, which offers full flats for a good price. That network will then be the Vodafone Network.

Op has been updated.

Maybe for a long while. As i posted a few days ago already: I don't see much point in continuing.

Most obvious tendency out of the current report sheet: Firmware 2.31 is the most reported. IT SUCKS! :D

Furthermore: Black devices now clearly outrun the grey devices. I figured that the Blackies had been sold a lot more than the greys too.

Furthermore: There is no JellyBean report! Not one! BUT: i know a few people with the Home Button Bug and they can't update the sheet themselves.

PLEASE EVERYONE ON JB:

If you still have the problem, contact either me or Zoesdad70 on PM and let us Edit your Entry manually so that the sheet reflects the state of Jelly Bean too!. If we don't do that, only new users with JellyBean will enter the sheet and then the comparison between the bases is deemed to be useless.
[HTC One S] flex420:
1&1 is Vodafone. But ye, might help. For me is did not. I'm on Congstar ( t-mob ) with Jellybean OTA - Rooted and Customrecovery - sh26 Serialnumber, black device. Have the bug, but its now the google now bug ... :D you can add me to the list!
[HTC One S] Laurence93:
Just got the phone back once again, it's been about 30 minutes and no helicoptering - Improvement from last time they gave it back anyway.

IMEI has changed, SH24 serial still.
[HTC One S] frdn:
anyone has updated to jelly bean?? any luck?
[HTC One S] Sneakyghost:
Some did, yes. I mostly heard about it on the German forum android-hilfe.de.

sent from a phone
[HTC One S] flex420:
have the jelly bean OTA installed, no luck ... will send the phone in tomorrow, all i need is the original recovery, where to get this? we have no RUU from the JB update yet :(

any ideas?

i cant use the 2.31? RUU because it has the lower hboot ....

Edit : just extracted the ota zip :) worked
[HTC One S] flex420:
How long did it take to get your Phone back?
[HTC One S] guigz2000:
Hello...

I updated to jb in France (a small month ago)

I only got the gnow screen once,but I haven't been traveling a lot...

Seems quite well for me as was 2.21. For the moment..

Only drawback is the touch screen and buttons feels less responsive..
[HTC One S] Laurence93:
it usually takes just under a week, however this time it took just over a week due to me sending the phone off a day before new years. Once HTC received the phone it was fixed and sent back next day, it was just UPS who took their time.

On a side note: Still no sign of any helicoptering, so it seems the new motherboard has fixed it - cant say for sure though until I go somewhere with lower signal. However usually once on 'G' it would go crazy, now it happily switches back and forth 'G' - '3G' - 'H'
[HTC One S] captaineasychord:
Just a quick update from me, I've had my phone back from it's third repair for about three weeks now, and (touch wood) no sign of the helicoptering returning, and it's been well tested in places where it used to go crazy. So, fingers crossed, it's sorted, maybe HTC have finally worked out a fix! Loving jelly bean too!
[HTC One S] flex420:
hope the german supplier arvato will be that fast too ... they told me in the mail that it would normaly take 5 - 10 days after they got the phone. will send it off tomorrow morning.
[HTC One S] Sneakyghost:
It took 10 working days for me including one weekend, making it 12...

sent from a phone
[HTC One S] copas2:
stock JB

After using stock JB for a while now, helicoptering still exists at really low signal level while doing mobile networking (2G). By the way, touch-screen seems to be less sensitive.
[HTC One S] flex420:
awwww snap. i dont even know how i can live 5 days without a phone :D all old phones that i have wont take my microsim from the ones ... :D
[HTC One S] Sneakyghost:
Get your provider to send out a new SIM - it comes in a cut-out plastic frame, which then can be used as adaptor. I have done it that way.

Another method is to find some old SIM you ain't using anymore and cut out a shape for your micro-SIM with a (very) sharp carpet knife or similar. Not such a big deal to be honest...

Some funny sad news....

Just had a guy here with a new VW Passat for some tuning stuff to do and he showed off his brand spanky new One XL. guess what he said

.....

Don't we just know that all too well?

Oh my god... next one...
[HTC One S] hbbug:
...tried this too, did not work for me as you cannot disable the home button completely without causing errors in the Viper ROM (I couldnt start Venom Tweaks afterwards). If somebody has a better solution using Viper ROM pls let me know ;)
[HTC One S] odl:
you can try to remove line "key 102 HOME VIRTUAL" from cy8c-touchkey.kl and projector-keypad.kl files (you can find it them \system\usr\keylayout\ ). you can do it directly from mobile (some root explorer needed), or modify that files within zip file with ROM before flashing. I don't use viper, so I can't tell that it will not mess venom tweaks, but you can try it ;)

best would be to disable reading home button at kernel/driver level, but I'm still looking for some hint what I have to modify in cy8c driver source (im not familiar with C++). So far I managed to change home button function to "reset" keypad driver, so I don't have to switch the screen off/on to get remaining two keys back after issue occurs anymore. however during strong HOME button "spam time" sometimes I have to press other keys two-three times to have reaction - that's why it is not perfect solution yet.
[HTC One S] Sneakyghost:
For me, the Home Button Issue began to call the Long-Press option rather than the Short-Press option after Firmware 2.21.

So, in Viper/Venom-Tweaks app, i would simply disable the long press home (section "Buttons") and that would do the trick.

Currently i am Beta-Testing the new Viper 2.0, which has been rebased to the latest JellyBean Firmware 3.16. I also use the respective Radio and Extra Partitions and so far, i have not had the Home Button Issue, whereas i DID have it when on stock JellyBean OTA.

I have to say that i did the Brick Downgrade and am now running a low hboot (which has no influence on the Home Button behavior) plus everything else on the newest level.

And regarding the Workaround: Beatnix figured out that method way back when 1.78 was current. It was also meant for Stock RUU only and didn't quite work on custom Firmware i believe. I have not tracked that Workaround throughout the later bases. So i cannot really comment on that. If Beatnix happens to show up here again, he could maybe comment on that. I will try to reach out to him on the other Forum where i first met him.