Related
OK so I downloaded & installed the latest OTA update (RV23RC03; 1.057) with the power mode choices, and it has completely destroyed my touch screen response! I previously had ZERO problem with this- every key press registered on both the original ROM and the 1st update. Since the latest update, everything takes 2 or 3 presses, sometimes VERY firmly, many times still without registering. This totally sux
Is anyone else having this issue? I should note that I do have a matte screen protector on; this previously caused NO problems.
Is there an easy reasonably safe way to revert back to the 1st update (RV07RC06; 1.029)? A link and/or instructions appreciated. Thanks.
Acer, are you out there? This exact issue occurred with my A510 on its 1st update, after which it became nearly unusable for me. Since it was < 30 days I was able to return it. No such luck this time. Why are these updates doing this? It's driving me nuts!
No issues with touch on update. It seems to be running better actually.
Try to completely reset thru recovery with wipe data maybe.
More specific instructions
Itchiee said:
No issues with touch on update. It seems to be running better actually.
Try to completely reset thru recovery with wipe data maybe.
Click to expand...
Click to collapse
That's so amazing. I went from no problem at all, to I can hardly use this any more; only thing that changed was the update.
Can you please be specific about how to reset through recovery. (Step-by-step if possible) and how to wipe data.
Thanks.
You can reset data thru settings/privacy but you will lose everything and start fresh.
I'll check on the other method later on for you.
Also turn up touch sensitivity in settings/display if you haven't...
Edit - it appears that the stock recovery doesnt have those options.
You can still reset by inside ICS like above, or...
Factory Reset:
WARNING: reset will start immediately
Volume button (one dot) and Power button, once buzzes release power button and then toggle the rotation switch on and off a few times
Yes of course, I have set screen sensitivity to high. I think I'd rather go back to 1st update, rather than wipe everything (I do have a backup but it's still a hassle). I can't believe no one else is having this problem.
Any idea how to revert to last update?
Someone in a german android forum mentioned that it help on his device after the update to set the sensitivity to the lowest setting and then back to middle or high.
I tried playing with sensitivity settings, turning on/off,resetting and no luck.
I actually found the ROM from before the update on this website and flashed it as update.zip with vol +power. It worked, I now have 1.029 back and touch screen works perfectly. I'm sorry to lose power management but i think I'll stay where I am . Don't ask me about a Jellybean update; I'll want it but after this I'll be afraid to try it. If anyone has an explanation for this i'd love to hear it.
Hi dear community!
Got a problem with the power button of my a510. Sometimes when the device is in standby and I want to switch it on by pressing the power button nothing happens and rest totally unresponsive. I have to push it like 10-20 times and even connect the charger to get reaction. Once the device is switched on the power button works normal. I suppose its some kind of freezing of the device in standby mode that blocks the power button. Is it a common problem and what can I do? Thanks in advance for advise!
First thing I would try is to reboot it (press power button for a few second and let it shut down, then restart it). If this is not helping I would hardreset it (reset hole left to power/usb-connector).
And if not this is making it better make a factory reset (from the settings). Keep in mind that you will loose all data and have to start from scratch with your tablet.
Thanks! One question though, do the hardreset from the hole left to power/usb-connector do the same thing as factory reset from the settings - loosing all the data?
ozonbg said:
Thanks! One question though, do the hardreset from the hole left to power/usb-connector do the same thing as factory reset from the settings - loosing all the data?
Click to expand...
Click to collapse
Nope. The pinhole reset thingee is similar to the reset button on a CPU. It simply hard reboots the system (supposedly used when the device freezes, since we can't "pull the battery" like what we do with phones).
Reading through your OP though, I actually recommend sending the tablet back to the shop. I don't have that, nor have I heard of that issue.
I don't have this problem, you'd better send it to service.
I think I found the problem wnen seeing the log from the device. It's a freezing situation. The device become unresponsive and that's why the power button doesnt work when pressed. After second long press it reboots the device. So the button works.
In one of those freezings console says: Unsafe JavaScript attenmp to access frame with URL.. So I disabled java in the stock browser and will keep reading log for further freezes.
hi i was getting that issue.
a factory reset stopped it but recently it came back.
im overseas for 2 months asking acer the immeditaely said to return device for repair.
have to wait now.
Also jist the other day i got three freezes screen went pink completely.
once it went yellow.
i would sugest talk to acer as i know mine now is def faulty after the screen issue.
Hi,
so I realized that a couple of days after buying the thing I disabled some of the apps that comes with it in order to save some RAM, but maybe disabling them causes other apps to misbehave. And thats why sometimes device freezes compleatly. Now I'm checking this theory. Sorry for my English.
What did you use to disable them?
From settings - > apps, then choose a system app and there is a option to disable it.
Another thing. So I'm playing a lot and when some game suddenly stop responding I force closing it. Even this game is already closed after like 10-15min. the device freezes and only rebooting it saves the situation.
ozonbg said:
Hi,
so I realized that a couple of days after buying the thing I disabled some of the apps that comes with it in order to save some RAM, but maybe disabling them causes other apps to misbehave. And thats why sometimes device freezes compleatly. Now I'm checking this theory. Sorry for my English.
Click to expand...
Click to collapse
I disabled alot of stock apps as well. My tab is running fine though. You can maybe list down what you've disabled and I'll confirm if they're disabled on mine too?
Couple of days observation lead me to the conclusion that the freezing is due to unresponding processes left in the memory most likely a high demanding 3d games such Dead trigger, Asphalt 7 or Dark knight.
Edit:
It might be a bad freezing flash player mostly used through stock browser.
i tried this way too..but it freezes also when it's fresh from a hard reset
i don't know if it's an app issue...or whatever.
but i just got a new a510 as replacement of my old one that kept freezing...and also this replacement keeps freezing
i didn0t disable any native app...nor installed any new app. just got it...and freezes the same.
When watching flash video in stock browser and when exit watching, the browser sometimes freezes and needs to be force closed to function again. When left whitout force closing it eventually after some time causes general freeze. That's happening also when a game crashes and left in memory that way. Needs to force close everything that crashes. For example when watching HD Cams in Earthcam.com often browser crashes when closing it or when I play Tower Defense game crashes a lot. Afterwards the whole system freezes.
That's my assumption as above all monitoring I've done.
Let's hope Acer will have fix in Jelly Bean update.
in the newer firmwares are freezes still found? i noticed that all my italian friends stuck with 1044 experience them...maybe later ones solve it?
There is no new firmware, but will be most likely.
there are lots of ota after 1.044 ww.
germany is at 1.099 stock....
i'd like to hear something from who uses it ...
As of last night my tab 2 (p3100) has been playing up, have it running a pac rom, not updated in a while but all was working fine. Now when I do get it on, it lags a lot on home screen, can only really access anything for about 30 seconds before its practically unusable. When I try to power off or reboot it begins the process but ends up freezing, only way I can get it properly off it to plug it in to charge and then hold power for ages. Then getting it on again takes ages. Only thing I recall doing prior to these issues was installing the peel remote earlier that day, maybe just a coincidence but after that it all went wrong. I've just tried a factory reset and data wipe, seemed to initially solve the problem but after a few mins back to the same issues, any ideas?
edingal said:
As of last night my tab 2 (p3100) has been playing up, have it running a pac rom, not updated in a while but all was working fine. Now when I do get it on, it lags a lot on home screen, can only really access anything for about 30 seconds before its practically unusable. When I try to power off or reboot it begins the process but ends up freezing, only way I can get it properly off it to plug it in to charge and then hold power for ages. Then getting it on again takes ages. Only thing I recall doing prior to these issues was installing the peel remote earlier that day, maybe just a coincidence but after that it all went wrong. I've just tried a factory reset and data wipe, seemed to initially solve the problem but after a few mins back to the same issues, any ideas?
Click to expand...
Click to collapse
Try flashing another ROM, like CM 10.2 or one of the stock-based ROMs. Make sure to wipe data, system and cache before flashing. If the issue still persists, try restoring a backup that you know worked.
Will give that a go, thanks.
Hey,
yesterday i faced a problem i didn't knew of yet. As i mentioned sometimes, i came from an One M7 2 weeks ago as it didn't work the way it should - camera useless and awful battery life. I rooted the M7, had problems with it and so on - just how it is with a rooted phone + custom roms.
However, due to the DRM i didn't root my Z3 yet. Yesterday i took it out my pocket, thought it was a bit warm.. nevermind. It worked. 30 minutes later i pulled it out again, still warm, and screen wouldn't turn on. I reset it (power and vol+ for those who didn't know), tried to boot again.. well, it took several minutes and finally showed me the attached error message. The system performance was really, really low. Everything stuttered, i couldn't even enter my pin. A few forced reboots later i could finally enter my pin and get into my system only to notice that my data partition wasn't doing fine. I had to set language and so on in the initial setup process, apps kept force-closing in seconds. My own apps were still on the device, however when i tried to open WhatsApp there was no data there, i should have gone through the registration process. The phone froze after seconds each time. I tried to enter the fastboot menu (is it called that way?) while booting to just do a factory reset, didn't find the button combination. So finally, after i found home without navigation from no man's land (sure, why doesn't it happen at home anyway..), i managed to boot it, get through settings and initiate a factory reset. Of course, all the apps were deleted then and i could install all apps like LightFlow again. Had to re-enter all the settings i did in those kind of apps, it was kind of annoying.
So, my questions: Why the hell did this happen to my Z3? Not rooted, didn't even think of it. There wasn't a day on the One M7 without flashing anything and it never happened. It wouldn't have been as bad as it was on the Z3, as i HAD root, could have wiped data in TWRP in a matter of seconds and also had backups of my data, which i of course didn't have for my unrooted Z3.
Is it likely to happen again? Can any app do this on a non-rooted phone? I read a bit about the error, that it would be caused by some apps, but not in the extent as it happened on my phone. Most of the times it would just be an annoying error message.
I got a thing in always getting a defective unit, so i hope it isn't happening again on the Z3
Maybe the internal flash is corrupted/failing. I had a similar issue with my HTC One X I went to nap one day and half hour later it shut down, it restarted but boot looped. Eventually it showed no data partition as being mounted and completely died. They replaced the motherboard.
Better contact Sony, maybe you need a replacement.
Mh, actually that's the least thing i want to do.. I'd have to wait for at least 2 weeks to get it back and chances are that they won't do a thing or damage it (bad experiences with my former Razr i). It works just fine after the factory reset, no errors yet. If it should happen again, i'd of course send it in for repair but i think, until then i will use it normally, with more caution and backups of course.
Probably the cleanest solution HERE
Hello! I have a stock Android Lollipop 5.0.1 Nexus 5 and for the past week or so I have been experiencing a weird issue.
The device randomly crashes. By "crashes" I mean the screen goes black, but the backlight is still on (it's a lighted black). I can push the power button and it will turn completely black (locked) and if I push it once more it turns lighted black again.
To get the device back into usable state I have to keep the power button pressed until the phone resets. Sometimes I keep it pushed for a full minute and nothing happens, sometimes 10 seconds are enough. Sometimes it will go through the "Google" logo and then stay in the lighted black state until I finally manage to reboot it again. Sometimes it crashes again right after it boots up.
It's weird because a lot of the times it's ok throughout the day and then when I go out in the evening, I take it out of the pocket and I see it crashed. Sometimes it crashes while I actually use it.
Last night it started doing something else: instead of lighted black, the screen is filled with static noise. It doesn't move or anything, it's a still image. Today, when a crash like that occurred, the screen glitched first (random lines on the screen, some parts got moved, really weird). I will get some photos if it happens again.
The problem is that I can't identify what's causing it. There is no particular app or action that I do / use that triggers this. It also doesn't seem to be movement-based, as it sometimes happens while it's sitting still on a table.
I updated to 5.0.1 about a day before this started happening, but I'm still not sure if it's software or hardware-based.
I tried a factory reset and booting into safe mode, none of these helped. I will only consider flashing a custom ROM as a final resort, because I'm not sure if it voids the warranty.
PS: the device is still under warranty, but I'm away for the holidays and will be until the beginning of the next year. And I'd like to have a usable device, especially while I'll be on the road.
Smith_S9 said:
Hello! I have a stock Android Lollipop 5.0.1 Nexus 5 and for the past week or so I have been experiencing a weird issue.
The device randomly crashes. By "crashes" I mean the screen goes black, but the backlight is still on (it's a lighted black). I can push the power button and it will turn completely black (locked) and if I push it once more it turns lighted black again.
To get the device back into usable state I have to keep the power button pressed until the phone resets. Sometimes I keep it pushed for a full minute and nothing happens, sometimes 10 seconds are enough. Sometimes it will go through the "Google" logo and then stay in the lighted black state until I finally manage to reboot it again. Sometimes it crashes again right after it boots up.
It's weird because a lot of the times it's ok throughout the day and then when I go out in the evening, I take it out of the pocket and I see it crashed. Sometimes it crashes while I actually use it.
Last night it started doing something else: instead of lighted black, the screen is filled with static noise. It doesn't move or anything, it's a still image. Today, when a crash like that occurred, the screen glitched first (random lines on the screen, some parts got moved, really weird). I will get some photos if it happens again.
The problem is that I can't identify what's causing it. There is no particular app or action that I do / use that triggers this. It also doesn't seem to be movement-based, as it sometimes happens while it's sitting still on a table.
I updated to 5.0.1 about a day before this started happening, but I'm still not sure if it's software or hardware-based.
I tried a factory reset and booting into safe mode, none of these helped. I will only consider flashing a custom ROM as a final resort, because I'm not sure if it voids the warranty.
PS: the device is still under warranty, but I'm away for the holidays and will be until the beginning of the next year. And I'd like to have a usable device, especially while I'll be on the road.
Click to expand...
Click to collapse
I have none of your issues, try booting the device in safe mode and see if the problems still occure. It must be a or multiple downloaded apps that are causing your issues. Or try a data factory reset and restore/download your apps one by one amd try to identify the culpritt.
gee2012 said:
I have none of your issues, try booting the device in safe mode and see if the problems still occure. It must be a or multiple downloaded apps that are causing your issues. Or try a data factory reset and restore/download your apps one by one amd try to identify the culpritt.
Click to expand...
Click to collapse
I said in the post that I tried both of those things. The crash occurred seconds after booting in safe mode and factory reset did not help either.
Smith_S9 said:
I said in the post that I tried both of those things. The crash occurred seconds after booting in safe mode and factory reset did not help either.
Click to expand...
Click to collapse
Flashing the 5.0.1 factory image in fastboot should fix your issues. Or try flashing system.img first, maybe thats enough.
Same issues with my Nexus 5
gee2012 said:
Flashing the 5.0.1 factory image in fastboot should fix your issues. Or try flashing system.img first, maybe thats enough.
Click to expand...
Click to collapse
I am experiencing SAME exactly issues in my N5 with 5.01 and 5.1 . EXACTLY... you are not alone
Seems a software problem (third party app ?) , started in 5.01 and now is in 5.1 , of course system and boot images where flashed with fastboot, so no solution using
Stock, Rooted, using Nova Launcher - Smartwatch 2 - Google Cardboard - Chromecast and many apps.
But started ..if memory helps .. after installing Cardboard 3D apps.
reimer1 said:
I am experiencing SAME exactly issues in my N5 with 5.01 and 5.1 . EXACTLY... you are not alone
Seems a software problem (third party app ?) , started in 5.01 and now is in 5.1 , of course system and boot images where flashed with fastboot, so no solution using
Stock, Rooted, using Nova Launcher - Smartwatch 2 - Google Cardboard - Chromecast and many apps.
But started ..if memory helps .. after installing Cardboard 3D apps.
Click to expand...
Click to collapse
My phone had an issue with the screen. I went to the LG service and they replaced the screen entirely, so that's that.
again and again...
i'm in the same case... I don't have any clues or solutions, i'm just wainting like a dumb... I don't know what to do, i always have to make the thing with the power button and the lower sound button to make it show the boot screen, but it glitch after few seconds... PLS HALP