Originally Posted by Sneakyghost

Gsm is edge

Feel the Viper!

Aha! Thanks for clarifying. In that case, I just need to work out why I can't establish a data connection when I force GSM/Edge only mode. I do get a full signal for calling, but that's all. I wish I had checked this before updating the software.

Originally Posted by craigspc

Aha! Thanks for clarifying. In that case, I just need to work out why I can't establish a data connection when I force GSM/Edge only mode. I do get a full signal for calling, but that's all. I wish I had checked this before updating the software.

That is odd. I don't quite have an idea why that happens. Did you try a reflash and RUU the phone in between (in case you run a custom ROM)?

Feel the Viper!

Originally Posted by gibarian

Very long week for me too, so I haven't really had time to make any progress. Will work on it this weekend if I don't get caught up by something else, and hopefully everything will be set up by next week.

I will definitely consider what you said. I still believe that a separate thread will help keep things "tidy". Cross-referencing with this thread will of course be done.

Anyway, the key to success will lie in the willingness of people who share this issue to report it properly at different places, like for example review websites. Some material for thought: CNETs review of the One S has 4 stars (editors review) and 3.5 stars (average of 24 user reviews). Now imagine 415 users (people having reported the issue on the spreadsheet) posting a 1-star review on the website. The phone ends up with 1 star from users for good. Of course, every user will send a nice mail to HTC and invite them to go read their reviews. Multiply this by a vast number of review websites... and you get a pretty nice idea of the plan. If they don't do anything then, we go on: carriers, press, bloggers... Keeping HTC in loop every step of the way will also show our determination.

I believe if we play our cards well, we should get somewhere...

Will keep you updated over the weekend.

Allright that's fine with me then. I suggest keep your thread in the same sub-forum (Q&A) to have accessibility centered (search subforum for the home button issue brings up both threads, else it would need a search on the One S Top level forum which brings up too many results.

I strongly suggest to post as many links to sites for reviews and ratings as possible as there might be a lot of users who have little time like me and can't afford the research time. Underlying thought: not making it easy for the lazy but reducing barriers so people will not feel intimidated by your request to help downrating the phone ( i think you are intending this anyway, just seems important to me).

Look at it from this perspective and it will make quite clear that you will have to do good, structured preparation, a lot. But it will draw more people and be a lot more effective.

Always keep your thoughts public and transparent, keep everything fair and reasonable. Don't put us and xda in a bad light to reduce the risk that involved parties will just put it off as "whining from some spoiled brats". No unfair trickery. Motivate your readers to also act on an adult and educated level.

Originally Posted by Sneakyghost

That is odd. I don't quite have an idea why that happens. Did you try a reflash and RUU the phone in between (in case you run a custom ROM)?

Feel the Viper!

No, it's a retail bought phone that has been updated via OTA only.

I realise that there are other factors to consider with this phone, but...

1) I have homescreen bug
2) I install 2.31 update via OTA
3) The problem is gone
4) the only thing that doesn't work on the phone is GSM Only data connection (which people suggest I use to recreate the fault).
5) All connection types work fine in GSM/WCDMA auto mode.

Is that really just chance? Is there any possible way that there's something different between the OTA and manually flashing firmwares and RUU's? I have been unable to recreate the problem since the update. Even the paper test doesn't cause problems.

Vodafone UK today released their OTA update. Details are:

• Kernal Version: 3.0.8-01585-g9a884e3
• Baseband version: 1.08es.50.02.21_10.09c.50.04L
• Build Number: 2.38.161.6 CL97613 release keys
• Browser version: WebKit/534.30
• Android Version: 4.0.4
• HTC Sense Version: 4.1
• HTC SDK API level: 4.23
• HTC Extension version: HTCExtension_403_1_GA_20

Would you be surpised to hear that I've had two instances of the homescreen problem since I updated? No? Me neither!
Both instances were a lot less severe than before the update, but I only updated less than four hours ago and I've mostly been on WiFi.

Interesting... other baseband (1.08 instead of 1.06) and other Build(2.38 instead of 2.31)... Is that just the Carrier's modifikation to the 2.31 or is it another update from HTC >2.31???

*Edit* Upie, i can update too but i'm to scared it'll make things worse... Has someone tried it yet??

We need the hboot version and I need the cid that is currently getting the update please.
If the hboot is still 1.14.0002 I will swap cid and run the ota because with equal hboot I could go back to 2.21.
I want the files radio.img and boot.img on my phone at least to see if it makes a difference.

Feel the Viper!

How do i get what cid i have on a virgin device?

Originally Posted by Sneakyghost

We need the hboot version and I need the cid that is currently getting the update please.
If the hboot is still 1.14.0002 I will swap cid and run the ota because with equal hboot I could go back to 2.21.
I want the files radio.img and boot.img on my phone at least to see if it makes a difference.

Feel the Viper!

HBoot is still 1.14.0002
My CID is VODAP001.
Remember my phone is a Vodafone UK branded phone.

The update also comes with added bloat from Vodafone (joyn version 2.9.46 and EA Games).

EDIT: I downloaded an app called CID Getter from the Play Store in order to get the CID.

Originally Posted by zoesdad70

Would you be surpised to hear that I've had two instances of the homescreen problem since I updated? No? Me neither!
Both instances were a lot less severe than before the update, but I only updated less than four hours ago and I've mostly been on WiFi.

Would have been to good to be true... Seems to be then a derivation of the 2.31 OTA...