I recently installed the OTA update via the rootsafe method posted by whitslack (Root-safe* stock OTA 1.47.651.1 *incremental* update w/ radio+WiMAX) and I have noticed that there is still significant touch input lag when testing in the multitouch visualizer 2 app.
I remember reading in various threads, albeit with mixed opinions, that the touch input lag was gone with this update. I'm wondering if anyone can confirm this or if it was just people getting a little too excited for their own good, cause I'm not seeing it with this modified version of the update.
It's been reduced but it's still there for me. Stock unrooted with ota.
Related
This may be a known issue but my wife's (non-rooted, completely stock) A500 has been getting a 4.0 OTA notification since yesterday. It says it's invalid, after downloading it, so I ASSUME it's not actually for this device but is that the case? If it is for the A500, do I need to do a factory reset to get it to update?
Thanks, and Merry Christmas!
What version is it running currently? 7.014.02
I have not seen anything since the 7.014.01/02 releases a few days back.
It would be nice to see Acer taking the lead on releases but I will believe it when it happens. The. 02 release did have a new to me update screen when it installed....
Wowsher
I think I know what one of the issues is- This must have been some really old stock (bestbuy.com) because it's running 3.0.1 and the kernal version is 26.36.3-00001-g9b3ce2b. Is it possible that it's somehow "skipping" the OTA updates in the correct order (or maybe they aren't available OTA anymore?) and thus giving me the "invalid" message?
yep would not surprise me at all... you should be able to download from a thread in the rom area a thread by vache has links to almost all of them.
You should probably change the thread title if you can.
Wowsher
There have been others with similar issues.Seems like acer did not and is not pushing the updates to some devices.
I would first call acer if you. Not likely to help but would atleast let them know they have issue.
For a right now fix.
Get iconiaroot. Root tablet.
Get acer recovery installer. Install custom recovery.
Look on forums for a stock 3.1 or 3.2 rom.
You can get a ore rooted rom if you wish but would kill all updates in future.
There are lots of information in the dev forums on step by step instructions and downloads.
Be careful fallow instructions.
Good luck.
The 4.0.xxxx update, is an update for UI. It should come in 2 notifications for stock tablets.
The first, is a preparatory update. The second, is the actual update.
Note, if you have a rooted tab, as some people can tell, it is not advisable to take any OTA update from acer.
In the forum, if you want to take the update, there is a thread which has rooted versions of these updates.
Alright, so I'm quite cautious before I proceed with the update but I've been hearing mixed results with the 2.3.5 update. I pretty much have the update ready to go in the ext SD card.
I was wondering since my phone is fairly new and stock, have the problems experienced by users who updated to 2.3.5 (such as null IMEI and touch screen issues) only affected those who have rooted and are running different roms? or could it affect me if I do an update to 2.3.5?
As for null IMEI, what significant impact would it have on my phone?
I'm really keen to go on Gingerbread as there doesn't seem to be any OTA updates to 2.3.5 here in NZ...
Current Android Version: U8800 V100R001C00B136
Cheers
I have been upgrading from stock 2.2 and did not have any problems at all. All went smooth and everything is working as it should. I am using 2.3 beta 1 update, because it has unlocked bootloader, otherwise it is preety much the same as final 2.3 release.
oh, do the problems people experience persist in beta 1? or over the official one?
Like I said, I did not have any problems with it and I had stock phone just like you (no costum rom, no costum partition). I know people have reported many problems with these updates but it works for me. If someone has different experience please post it and write in what state your phone was before update ( costum rom, partition, etc...)!
when I got my brand-new phone from the store, it was 2.2 but rooted (!) and no g-apps.
The update to 2.3 was no problem and everything works fine.
no root any more, but I don´t need it anyways.
Wurstwa55er said:
when I got my brand-new phone from the store, it was 2.2 but rooted (!) and no g-apps.
The update to 2.3 was no problem and everything works fine.
no root any more, but I don´t need it anyways.
Click to expand...
Click to collapse
did you update to the beta builds or the 'original' build? I guess I won't have to back up if its only a rare minority experiencing these faults.
Stephen289 said:
I was wondering since my phone is fairly new and stock, have the problems experienced by users who updated to 2.3.5 (such as null IMEI and touch screen issues) only affected those who have rooted and are running different roms? or could it affect me if I do an update to 2.3.5?
Click to expand...
Click to collapse
I have a U8800Pro so I can't offer you an answer as to whether you should upgrade, but all I can say is:
If your phone is rooted, use http://forum.xda-developers.com/showthread.php?t=1325036 to back up your IMEI. It's worth it anyway, even if you don't plan to upgrade
From what I've read, touchscreen issues seem to be occuring for those with Atmel screens (and there's a report of an Atmel screen going bad on its own anyway), not those with Synaptics ones. This is what I've gleaned by reading U8800 threads; again, I have a U8800Pro (which all come with Synaptics screens). You can use the tool Elixir from the Market or dial #*#2846579#*#* and navigate through the menus to find out what touchscreen you have
Was wondering if anyone has seen the update come thru if they installed one of the ICS Leaks - I rooted mine via blackthund3r's method and it works great but I wanted to compare to official version.
So I woke up this morning and have a notification for an OTA system update? Apparently, it's version D80120g. Doing some quick searching doesn't reveal much other than that it came out a few weeks ago. That in itself is surprising since I'm on XDA daily and hadn't previously seen any mention of this update. Anyway... has anyone taken this update? What has changed? Will I still be able to root after taking the update?
So, if you look at Asus's website, they have released firmware TW_V12.14.1.9 and in the changelog it mentions that "the first boot time after upgrading to Android 5.0" will take 5 mins. So I think that release is Android 5.0. It was released on April 2, 2015 so maybe we can hope to receive an OTA update for WW_V12.14.1.9 sometime within the coming week? I sure hope so!!
do not update if important sound in the headphones, disappeared after updating bass.
Before getting root solution, it's not recommended to update it yet.
OTA released since 12PM CEST, i can confirm that the version of Lollipop is the 5.0.1 WW_V12.14.1.9 which is 779MB in size.
No problem since I updated my tablet except one notification telling me that one application is requesting a newer version of Google Play Services...
Did you have root on tablet before you upgraded the new firmware and if so did you still have root afterwards?
Pirranha said:
Did you have root on tablet before you upgraded the new firmware and if so did you still have root afterwards?
Click to expand...
Click to collapse
Nop, no root...
Update breaks root. Zenroot failed.
psurut said:
Update breaks root. Zenroot failed.
Click to expand...
Click to collapse
Moreover, you can't apply OTA if you have root AND SD patch applied. Tried to install OTA, but no dice (stumped on platform.xml which was modified).
Thinktank: can you pre-root the ROM and install?
Hi, I've made an OTA update yesterday from .31 rooted version to Lollipop and I've lost root as I've expected. Beside it, tablet is unusable - still cycling messages 'Unfortunately IndexService has stopped' and 'Unfortunately ContextProvider has stopped' . I have to do super-fast double click on these messages and then I have about 0,1 seconds to click some other item before the cycling messages appear again! With this annoying double-clicking process, I've been able to reach "settings" app and make another user account - cycling messages are gone, but when I want to use Chrome, message 'Unfortunately Chrome has stopped' appears and other browser don't work too (Dolphin, Asus Browser, Chrome Beta...).
I've made the factory reset, but messages 'Unfortunately IndexService has stopped' and 'Unfortunately ContextProvider has stopped' still appear and I can't even to pass welcome guide!!!
Tablet is now useless, downgrade doesn't work.
Looks like Asus pulled the Lollipop update for the ME572C from their site.
I checked both the U.S. and Taiwan support sites (www.asus.com/us/Tablets/ASUS_MeMO_Pad_7_ME572C/HelpDesk_Download/ and www.asus.com/tw/Tablets/ASUS_MeMO_Pad_7_ME572C/HelpDesk_Download/). The Lollipop 5.0.1 WW_V12.14.1.9 build that came out in early April 2015 is nowhere to be found.
I hope Asus is going back to fix reported issues and...hopefully...go straight to 5.1 or 5.1.1 with the next update soon.
I checked also and noticed it was pulled after only being posted for a brief time. That is odd. I actually haven't had any issues with mine since updating to the lollipop build and actually have noticed a remarkable inprovement in my tablet since the last update. Of course, I did have to sacrifice my root to go to lollipop, but I was only using root to delete alot of the bloatware since the stock KitKat was slow and stuttered alot when new. It's not like we have an unlocked bootloader to flash custom roms with, so as long as they can make the stock firmware fast and smooth, I'm content to use it. Although, wouldn't it be cool if they pulled it and were gonna release the next update as a 64 bit version to take advantage of the 64 bit processor?