Database Info

Finally bought a G Tablet

Well I picked this up at Sears today for $380 with a mail i rebate for the docking station. I tried to update the firmware and kept getting a failure, talked to tech support and changed some settings. The update still failed and tech support suggested charging for 24 hours, they claim this will help. I have used the G Tab with stock software and it seems really fast. I won't download any apps until the software is updated, supposedly this update will fix some major bugs. I think I'm going to like this tablet once the someware is updated.
Regards!
Ed

Two suggestions:
1- Charge it (in that, I agree with customer service)
2- Update the stock firmware as soon as it's charge (not a mod, just a newer stock update). The reason why is that there are bugs in the original firmware where the system may freeze, which you want to avoid.
3- Wipe your user data. It really helps with a lot of user issues, like force closes.

Well I turned on my tablet tonight and it was ready to install the update and did it successfully. I can see the difference in performance already. I'm happy so far and how do you wipe the user data? Also another question about a game called bejeweled. I tried to download and the site was asking which device I was using to confirm compatability....viewsonic wasn't listed so I could not download so now what do I do?
Thanks!
Ed

Settings -- Security. I would recommend it, before you start installing apps - if you already have installed apps, then no harm no foul.

OTA update to Andriod 2.3.5 bug

Hi guys,
It seems that after receiving the new OTA update I ran into some issues.
My problem is that after installing the update my phone started to occasionally refuse to unlock the screen after pressing the power button.
If I connect the charger the screen unlocks but otherwise I have no option to unlock it.
I did a Factory restore (of course I lost every bit of apps I had installed - even tough I had the Backup settings activated-) and it seems that I'm seeing the same problem a few times a day.
Has anyone encountered this issue?
The phone is bought from Vodafone and original software installed.
Haven't rooted or S-off it.
Thanks

if ur phone is s-on and have same issue like s-off phones thats actually good news..seems that HTC messed up something...maybe is good advice for u to give phone to repair service if is s-on and see what thay can say about that.

I actually had that bug BEFORE the update, but not after. Instead of that, HTC Locations stopped working after the update and still is refusing to start even after factory resets and reinstall.
I have tried to contact HTC through their website to ask wheter something can be done about the issue, but the "Email Us" form doesn't seem to be sending anything after pressing submit and the "Chat with Us" form just shows blank white... I tried them on IE, FF and on my phone but they all show the same kind of behaviour.
It's really beginning to get irritating...

Clearly a software issue if it really happened after the OTA.
Wiping your Cache, Dalvik-cache partitions along with your Data (Factory Reset) should be able to refresh your phone as a "brand-new" one. That is if you can.
Stock recovery has an option to wipe Data and Cache.
If these still doesn't work, shove it to HTC's arses.,
Just kidding..
Send it for repair or maybe show it first to them.

some more bug.
-> live wallpaper sometime hang.

Starting yesterday I disabled the new feature "Trace keyboard" and since then the phone unlocked everytime.
Has anyone else kept this option activated and working ok?

2.3.5 OTA suxxxxs
Hi All,
I got OTA 2.3.5 Sense 3.0 on last Friday.
Since I have the screen problem = after a call sometimes I cannot unlock the screen with power button. If connect to the charger it's unlock and after the
power button works again. My phone is S-ON, fully original.
And I have 2 friends, they have Desire S and got this update too,
and after it the problem appear on their phones too.
So I think something wrong with new OTA update.
And I also notice the TTS Service, don't work too, it's always
halted.
(I made a factory reset and my friends too, but we have this problem too)
Any idea?
Everybody "got" this bug with OTA?
Bye,
Istvan from Hungary.

Wait for fix from HTC. They messed up something.
~Swaypovano sa Desire S BRE!~

I was finally able to get in touch with HTC regarding the Locations bug. The service agent said that he has never heard of such a problem before. His advice was that I should try the factory reset once more without the SIM card and without logging in to my Google account. I did that but the Locations still won't work. Only advice after this was to send my phone in for service... I'm really not happy with sending it in just to get an app (that was broken by their own update) to work again. I'm also pretty sure there was something wrong with the update to begin with considering all the new bugs being surfaced all the time.
This is really frustrating...
Would the people that have updated please tell wheter their Locations works perfectly? And if so, where are you from?

Bmw_m6 said:
Hi All,
I got OTA 2.3.5 Sense 3.0 on last Friday.
Since I have the screen problem = after a call sometimes I cannot unlock the screen with power button. If connect to the charger it's unlock and after the
power button works again. My phone is S-ON, fully original.
And I have 2 friends, they have Desire S and got this update too,
and after it the problem appear on their phones too.
So I think something wrong with new OTA update.
And I also notice the TTS Service, don't work too, it's always
halted.
(I made a factory reset and my friends too, but we have this problem too)
Any idea?
Everybody "got" this bug with OTA?
Bye,
Istvan from Hungary.
Click to expand...
Click to collapse
Try to disable the "Trace keyboard" feature. I did that and it seems that for the last ~18 hours I didn't encountered the unlock bug once.

Trace keyboard...
My "Trace keyboard" was off and the problem also present.
I tried to switch on, it hasn't any effect to the problem.
I hope the HTC will soon cede to this OTA full with bugs...
But as I known them, they not soo fast.....

Since the OTA update my Desire S crashes about once a day, and after it reboots it tells me it has recoverd from an error and asks me if i want to send the report to HTC. Seeing as how it reboots without any problems, and it works perfectly except the crash once a day, i suspect it has something to do with the flashing to 2.3.5.
Should i try a factory reset, or could there be another solution (seeing as how i really want to avoid a factory reset).
Oh and I have not rooted or S-OFF'ed my DS before the OTA update, so it's totally stock (as it has been since I got it)

I was able to fix the bug with Locations not starting up by changing my phone's language to English, then starting Locations, then changing the language back to Finnish again and voilá, it worked. One less problem for me.
I think that the Locations bug is limited to Nordic language versions (or even only to Finnish versions).

Hello
After update i have also the issue with the screen impossible to re-activate by power button after call is ended.
howto reproduce the issue: it happens only when screen is locked by security lock (PIN) and I receive a call. I pick up the call, screen is automatically turned off during call. After the call is finished, I'm unable to get the screen active again by pressing the power button!
Only working workaround is to attach phone to charger or connect to USB. Then the screen is activated and I can unlock it by PIN and working normally...
I need to have security lock enabled to be able to sync corporate email ( this is the security policy enforced by corporate Exchange server).
Ferro
Sent from my HTC Desire S using XDA App

This new OTA update looks more like a beta testing for many users still haven't got it and those who got it are complaining about bugs.
Some are affected by power button bug and others experience difficulties unlocking their phones.
What makes the situation even more strange is HTC not announcing the update.
Sent from my HTC Desire S

hamedunix said:
This new OTA update looks more like a beta testing for many users still haven't got it and those who got it are complaining about bugs.
Some are affected by power button bug and others experience difficulties unlocking their phones.
What makes the situation even more strange is HTC not announcing the update.
Click to expand...
Click to collapse
I'm sure you're right. HTC must have got a whole load of their people committed on new phones, others working on the recent security issues, so updates to our DS must be fairly low-priority. It smacks of the way that Microsoft beta-tested new OSes (perhaps still do) - Deploy many different public beta versions, don't bother actually reading the feedback but just simply measure how many complaints come in on each version. Finally, make official the version that got the fewest complaints.
I wouldn't be surprised if it goes quiet again for a week or so now.

The reply from HTC regarding the power bug:
Thank you very much for your cooperation and please be informed that we will get into this issue and we will try to determine what could cause these problems and what can be the solution. Please be patient with us because the investigation process itself it may take between 2 weeks and 4 weeks.
Have a nice day!
Disappointing

Hello,
After investigating further on my issue about "unable to resume screen by power button after call is finished" I described in my previous post I found it is most probably not related to OTA update but to HW problem...
I found my Proximity sensor is possibly dead. How the phone behaves (regarding screen on/off) during making or pick-up the phone is non standard. I also tried several android apps that are checking all sensors available on the phone and I see activity from all sensors except Proximity .
Talked also with HTC support... I'm going to sent my DS to HTC service center
Wish all getting the OTA update to enjoy it - I will certainly do so after I get my phone is repaired.
cheers
Ferro.

Pressing the power button during call or afterwards should light up the display.
At least that's what happened with the previous software version.
I'm still convinced HTC messed something in the update.

I have the exact same issue.
Has there been any work arounds how to fix this problem.
Mine's is on O2, never been rooted. Just stock.
If all fail looks like I will have to wipe phone and start again

TF300T acting funny after latest rom upgrade (stock unrooted), by Asus

Hi all,
Has anyone experience some strange quirks after the latest upgrade by Asus.
I'm on 10.4.2, I think that's the version but I am going to include a screenshot of the system page.
So far the main issues are that the live wallpapers are being hidden behind a black background, but they are running. They show up immediately after boot but then get covered up.
The other more important issue is that I am having trouble installing app via manual apk install. And yes, have the setting check to allow for installing from sdcard.
However, I am working around it by: It seems if I attempt to quickly run the installation of the apk immediately after booting it works, if I wait until the system is totally up it won't.
I've considered that I have a virus, but not sure how to check for that.
I also looked at any apps that have anything to do with wallpapers or installation and I can't find anything. I really hate to do a factory reset, especially if the latest upgrade introduced those issues.
Again, I am not rooted and running stock of course.
Thanks!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Rob

If you are serious about considering the virus theory then you can download "Avast! Mobile Security" from the play store and run a virus scan though there

either, "A" virus "B" something went screwy with the upgrade some file got corrupted

How do I fix strange behavior after 7.1.1 OTA update?

I have a Pixel and recently received the 7.1.1 OTA update. This morning my phone restarted and failed to boot properly. It does boot, and I get to the home screen where all apps seem to be functional. But there are several problems, including 1) I can't turn on cellular data, 2) the home button and the task switcher button do not work. Also, when I press the back, home or task switcher buttons, I get vibration feedback which is not how I had the phone set. Another odd thing is that when I check settings, it shows that the phone is on Android version 7.1 It is as if the phone tried to revert back to 7.1, but did not do so fully. Another anomaly is that when I got to the Play Store, all my apps appear as if they are not updated, even though I just installed available updates yesterday.
When I go to System Update, it shows a 261.9 MB update available to download. I assume that's 7.1.1 OTA update. I could try downloading and re-installing it, but before doing so, I wanted to see if anyone thinks that could cause more problems. Or, does anyone have another suggested step I could take. I would like to avoid a factory reset, if possible. Hopefully, there's another simple, quick solution.

Most likely it is easily fixable by just flashing the full stock 7.1.1 image from Google. Unfortunately it will wipe your device, but it is basically a surefire way to fix whatever went wrong.

It sounds like what happened is the OTA failed somewhere, bad download etc. As the pixel has the dual partitions if an OTA fails it will revert back to the last known working system. As @renegadeone8 mentioned, flashing the full 7.1.1 zip should cure your issues. You will have to unlock the bootloader to do so. (No a bad idea anyway imho Incase you have errors)
No harm in trying the OTA again. If it fails you won't be any further behind than you are now.

I'm having very similar issues, I also have no notifications and cannot pull down the full drop down menu or turn my data back on.

Thanks, k.s.deviate. I wish I had read your response earlier. It probably would have been good for me to at least try re-installing 7.1.1 again. However, I read from users on a different forum that they had experienced odd behavior very similar to what I experienced. In their case they didn't realize, at first, that the problem was associated with the 7.1.1 update. So, they re-installed it. Unfortunately, they had the same problems re-occur. For them the only solution was a factory reset and then not downloading 7.1.1 again.
That's what I've done. Everything is working great now. Android shows the 7.1.1 update available. Based on your assessment, I'm partially tempted to try installing it again. However, if it does end up with problems again, like it did the first time, I don't feel like I have the time to go through the whole factory re-install process again. So, I'm just going to stick with 7.1 for now and wait until either 1) I feel I have more time or 2) Google releases another update (7.1.2 ?) that might fix this problem. Thanks, again, though for your feedback.

exactly same here, so bad download could be ruled out. Also I've seen discussion on reddit and google forum, but unfortunely no solution was presented

Question Reflash OS without data wipe? Not rooted

Hi all,
It's been a while since I've really done anything outside of business as usual with my Pixel phones. I haven't needed to root since my Nexus 6P days and every nexus previous to that. So for the most part, all my Pixels, I've been on stock OS and generally fine bc I got out of the custom ROM scene. Starting with my Pixel 5, I stopped unlocking the bootloader as well. Now on the 7 Pro and I am curious if there's a way to reflash the stock OS without data loss given all the progress that's been made in the community as well as the availability of the Pixel Repair Tool directly from Google. This latest March 2023 update has been a little funky and I've had some weird glitches going on. I don't want to go through the whole process of setting the phone up completely again given I have several apps for work that are annoying to set back up. Are there any options or am I stuck just waiting until April to see if the next update straightens it out?
I did search the forums before asking and honestly without reading through 100's of pages of posts, I couldn't find anything related to locked bootloader. I do have the Google unlocked phone from the Google store though so I have the ability to unlock, just chose not to at the beginning.
Thanks!

You should be able to just use Google's Android Flash Tool, and uncheck the wipe option (YMMV). Although if you have glitches a clean flash with the tool seems best.

jrg67 said:
Hi all,
It's been a while since I've really done anything outside of business as usual with my Pixel phones. I haven't needed to root since my Nexus 6P days and every nexus previous to that. So for the most part, all my Pixels, I've been on stock OS and generally fine bc I got out of the custom ROM scene. Starting with my Pixel 5, I stopped unlocking the bootloader as well. Now on the 7 Pro and I am curious if there's a way to reflash the stock OS without data loss given all the progress that's been made in the community as well as the availability of the Pixel Repair Tool directly from Google. This latest March 2023 update has been a little funky and I've had some weird glitches going on. I don't want to go through the whole process of setting the phone up completely again given I have several apps for work that are annoying to set back up. Are there any options or am I stuck just waiting until April to see if the next update straightens it out?
I did search the forums before asking and honestly without reading through 100's of pages of posts, I couldn't find anything related to locked bootloader. I do have the Google unlocked phone from the Google store though so I have the ability to unlock, just chose not to at the beginning.
Thanks!
Click to expand...
Click to collapse
If you reinstall the factory system image, all you will accomplish is adding a bit more wear to the flash memory it is stored on.

jrg67 said:
Hi all,
It's been a while since I've really done anything outside of business as usual with my Pixel phones. I haven't needed to root since my Nexus 6P days and every nexus previous to that. So for the most part, all my Pixels, I've been on stock OS and generally fine bc I got out of the custom ROM scene. Starting with my Pixel 5, I stopped unlocking the bootloader as well. Now on the 7 Pro and I am curious if there's a way to reflash the stock OS without data loss given all the progress that's been made in the community as well as the availability of the Pixel Repair Tool directly from Google. This latest March 2023 update has been a little funky and I've had some weird glitches going on. I don't want to go through the whole process of setting the phone up completely again given I have several apps for work that are annoying to set back up. Are there any options or am I stuck just waiting until April to see if the next update straightens it out?
I did search the forums before asking and honestly without reading through 100's of pages of posts, I couldn't find anything related to locked bootloader. I do have the Google unlocked phone from the Google store though so I have the ability to unlock, just chose not to at the beginning.
Thanks!
Click to expand...
Click to collapse
You can sideload the full OTA with a locked bootloader but I don't think it will help your situation.

I'm wondering if reinstalling the OS would help because it seems like something got corrupted but not enough to make a huge difference. Just some slow animations, having to gesture back 2 times in the Google messages app to exit (first swipe on conversation list just reloads that screen and second swipe actually exits), I don't know, just some other minor little annoyances that I can't fully remember at this point. Wasn't doing any of this prior to this update. I have to think it's not my data on the phone given the nature of these little glitches.

I think all those in this thread may be forgetting that in order to unlock the bootloader, one is required to wipe the device right after -- which goes against the title "without wipe"...
Even if OP was able to just flash the system partition or use Android Flash Tool, OP would need to have an unlocked bootloader. Although, what I know about Android Flash Tool is that, as long as "OEM unlocking" is ticked, it can automatically unlock the bootloader, but I can't confirm it requires the wipe (but since that's SOP, i imagine it's still required).
You don't need to be rooted to flash partitions, but the ability to flash means you'd have to wipe.
Sideloading OTA does not require OEM unlocking, unlocked bootloader, or root; for what it's worth -- dunno if OTA does anything like a Full Factory flash-all that dirty flashes over all (other than internalsd and app) partitions and therefore having a better chance at resetting/re-initializing what's needed to stabilize glitches or bugs....