Hi,
i have/was having problems with tablet not waking up from sleep (lock) and also had a first known reboot out of the blue yesterday.
So, i first tried with cold boot, but didn't help.
Now i have factory reset the tablet, but the weird thing is that my boot animation is same as before, also the apk for google search > google now (which i was tried weeks ago) is still present. I had an impression that the factory reset - well, resets the tablet. But can someone please explain what does it actually, specially i need an answer on why the boot animation didn't go back to stock etc...
Why do a factory reset if thing are not like from factory
PS: still testing if it solved tablet wake up problems. Anyone figured out what is the cause and how to solve it?
how did you do the factory reset?
First time inside the cold boot menu (vold-down+power etc..), second time inside the OS (settings etc...)
So, it happened today again - couldn't wake the device from sleep. I did restore all my apps with titanium backup, so i still can't say what causes this, but i am very sad right now
Is there any way to look at some logs or something and to identify what makes tablet to not wake up from the sleep.
Next time I will try plugging it AC if it helps, but i doubt my problem is as described in some other thread.
Also, I would still like some answer on why the factory reset doesn't change the boot animation. I also noticed Elixir2 system widget app was still installed after the reset. Very strange. I can safely assume that build.prop was not overwritten, yes?
Thx
Related
Hello, This is my first post. I have the vanilla GTAB with the 2 updates that were automatically loaded last Dec. & Jan. I frequently get force closes. Today when I booted the gtab, I had it connected to my pc, but I clicked 'hide' at the activate usb prompt. Then the usual force close occured in Launcher pro. At the same tiime there was a prompt that said something like "which app to use for this action" 1) desktop or 2) launcher pro. Since I thought I already set this to Launcher pro, I selected Launcher pro, and (this is the important part, I think) I checked the box to make this the default action. I had done this before so I didn't give much thought to it.
Well, the device immediatel began looping between to 'force closes' that look similar: 1) The application LancherPro (process android.acore) has stopped unexpectedly. Pleas try again; and then the second half of the loop is 2) The process android.process.acore has stopped unexpectedly. Please try again.
Note that in #2 it doesn't refer to LauncherPro.
I rebooted the ddevice and it immediately goes into the same loop.
Is there any way out of this? I can't help thinking it is caused by making the failing app (Lpro) the default action. How do I get the prompt back? Or have I bricked this gtab?
I was able to activate usb support between loops, so I have backed up all my data to my pc (whew!), but I can't get the device to do anything on it's own, other than loop. I do not have a recovery file or any of the suggested clock??? utilies. This is a completely vanilla device. Therefore booting with recovery (power + vol +) just comes up and enters the same loop.
Sorry if this is long winded, but I want to hear any advice before I follow Viewsonic cust support's instructions to ship it to them for a hardware reset. TIA, -Jim
Try Fix Permission in the Recovery. I face this problem every now and then and could not find a better permanent solution . Its really painful at times. It usually happens when my Gtab awakes from a long sleep (like remaining in standby for overnight).
I just experienced the same problem the other day. It is my third time with all the loops and force close and android.process.etc.etc. Unfortunately the GTab with the stock OS has this troublesome issue. I followed the instructions to install clockworkmod (CM) restore to stock with the 3389 mods, and now when it happens I boot into CM and first try and clear the cash and if that dosen't fix the problem then I do the wipe data/ factory reset option which is a pain, but if you have backed up everything you are back up and running with everything restored in less than 15 minutes. Do a quick search and you will find the CM solution to get your tablet back.
Hope this helps! I think everyone who has this device has gone through it. I guess for the price what can you expect, $799 for a XOOM without flash or $350 for the Gtab with flash and some issues. There is always a trade off.
Thanks VERY MUCH for the replies. So minardml, it seems you have done the factory reset yourself. Is there instructions for this online? You took the back off the unit to do it? I will search for the CM solution. Also, kshwetabh, you are right it had been several days since I used the gtab. Could you explain how to "try fix permission in the recovery?"
newbieJim said:
Thanks VERY MUCH for the replies. So minardml, it seems you have done the factory reset yourself. Is there instructions for this online? You took the back off the unit to do it? I will search for the CM solution. Also, kshwetabh, you are right it had been several days since I used the gtab. Could you explain how to "try fix permission in the recovery?"
Click to expand...
Click to collapse
@newbieJim, before wiping cache or factory resetting try Fixing permission option. It always works for me.
1. Reboot system into Recovery (Shutdown. Press and hold Volume Up(+) button and press Power button.
2. Select "advanced" ( scroll the options using Volume up/down button). Press Home button when on "advanced" option
3. Select "Fix Permissions".
This will take a while (depending on the packages/apps installed). Note that you will not see any progress bar. Once complete simply reboot.
Hope this helps . I don't know how the system looses permissions but somehow it does.
-------------------------
kshwetabh
NexusOne [Cyanogen 7| Desire HD| MM Cyanogen 7| Looking for 720P mod]
GTab [Vegan latest]
http://kshwetabh.wordpress.com/
Sorry if I led you to think that I took the back off as I did not do that. The options that I was refering to are in the menu of clockworkmod. If you haven't found the fix I was talking about (installing CM) post again and when I get home later today I will see if I can find it. I think I may have bookmarked it on my laptop.
I just keep the home button prompt on. it seems to prevent 90% of FCs and also improved the screen lag i was getting.
it may be another step, but it's less of a pain the the ass in the end.
Once again thx to all. I will attemp recovery again, but I don't have high hopes because, as I said, the loop happens even in recovery (or safe) mode. IOW, I cannot get to any menu or screen.... Only the loop. I do not think I can install any new app., but I will try tomorrow when I return.
Cross posted
So of you followed my latest "journey", I had a perfectly funtiocnal phone, I screwed up the lockscreen font sending me into bootloop, I managed to eventually get an update zip that flashed the correct lockscreen font to the phone, and all is well. Except for one annoying thing
I noticed now when I press the power button to wake the phone, the bottom capacitive buttons will light up first, then the display will light up. There's a noticeable lag where there wasn't one before.
Thinking it might be my system, I took a nandroid backup, then factory reset the phone (Settings -> Privacy -> Factory Reset). When it was done reloading the factory restore, I tried turning the screen off and on, delay was still there. I restored my backup, phone was back to normal, but delay was still there.
Any ideas where this delay came from? I'm going to try flashing a few other backups I have and see of they all do it.
I noticed this too. I think it's Virgin Mobile's way of "fixing" the flickering screen problem... just don't let it power on until it's cooled down. Thus we get a slow-to-turn-on screen.
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.
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
Anyone else have an issue with unlocking the phone either by the power button or fingerprint scanner? My phone at times just sits there when i try to unlock it and will sometimes restart when i press the power button again when its frozen. Anyone else have that issue?
I have the s8+ from tmobile. I tried factory resseting and even updated to the new update. No luck. Any ideas?
Same, looks like a bug in the OS
Good!!! Better than getting a faulty device. Hopefully it can be fixed soon!
Mine froze and went to black screen after i downloaded and applied new theme. And when i press the home button i can feel the haptic feedback. I tried charging the phobe but there was no light too. I just perform a hard reset with the power + volume down keys.
You jinxed me... I read this thread but didn't bother clicking on it because I wasn't having the issue...
well... just did it. iris unlock, and then I got a reset and power button wasn't turning it on for a minute.
Hopefully it will be fixed
Yep
Hello, No issues on my S8+ from Tmobile.
Do you have a theme installed that maybe is causing the delay?
I learned from other posts from xda, when doing a factory reset, do NOT perform a backup and restore for apps. This causes some delays in response from the phone. Is better always to install fresh the apps from the app store and then just log in.
I also recommend enabling the developer options and disable all three animations to off. This will speed the phone response.
jdanielsantiago25 said:
Hello, No issues on my S8+ from Tmobile.
Do you have a theme installed that maybe is causing the delay?
I learned from other posts from xda, when doing a factory reset, do NOT perform a backup and restore for apps. This causes some delays in response from the phone. Is better always to install fresh the apps from the app store and then just log in.
I also recommend enabling the developer options and disable all three animations to off. This will speed the phone response.
Click to expand...
Click to collapse
No themes and installed the apps fresh on the second time. Has only happened twice since the reset so it improved. Now i just give it time if it freezes on me when unlocking so that it doesnt reboot.
I'm having an issues were using the messeges app makes my phone freeze