I have seen a few threads posted about random reboots and v3.1. However, my wife's Transformer will go into a cycle where it will reboot, then a minute later or less will reboot again, and keep this up for a while (not sure how long exactly).
Don't know if this is related to an incompatible app/setting or something with the OS (3.1). Is there anything I can check/do to try and prevent this?
**Edit......Forgot to mention device is unrooted running stock 3.1.
I'm facing the Sleep of Death on this TF. It was there even on Stock and is there on other ROM's also. My Transformer reboots when in sleep mode
Srikar_NBK said:
I'm facing the Sleep of Death on this TF. It was there even on Stock and is there on other ROM's also. My Transformer reboots when in sleep mode
Click to expand...
Click to collapse
Yep....pretty much the same problem as I'm trying to fix.
*Bump*
Sent from my PC36100 using XDA App
The workaround I posted here has worked thus far for me.
http://forum.xda-developers.com/showthread.php?t=1120185
Though I haven't tried it without root privilege
sassafras
Mine was rebooting like every 10 minutes, running 3.0.1 stock non-rooted. All I did was reset it to factory settings and the problem went away.
kovla said:
Mine was rebooting like every 10 minutes, running 3.0.1 stock non-rooted. All I did was reset it to factory settings and the problem went away.
Click to expand...
Click to collapse
Why are you running 3.0.1? Upgrade to Android 3.1. It's more stable and reliable.
kovla said:
Mine was rebooting like every 10 minutes, running 3.0.1 stock non-rooted. All I did was reset it to factory settings and the problem went away.
Click to expand...
Click to collapse
If I set it to factory is it going to take it back to 3.0? Or just change all the settings back?
factory reset won't rollback the firmware, it just clear all installed apps, caches and set everything to default
Related
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
pfoxdizzle said:
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Did you make any tweaks on the system before your update? I.e. rooted or custom rom system with changing build.prop, MinFree, or anything that basically you can only do after rooting?
No changes. Completely fresh and.un modified tablet
Sent from my MB860 using xda app-developers app
Honestly, I have gotten some and I'm fresh totally stock just got mine. However, I stopped connecting it to dock and uninstalled songza and MX player. Its a shot in the dark but lets see if any reboots, otherwise back to amazon.
pfoxdizzle said:
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I'm curious as to how much RAM your tablet is using after a cold boot in balanced or perf mode.
Mine stays between 579 and 654mb no matter what.
Haven't had a crash or a freeze since the first 3 days of ownership.
Well that's a lie...I had a lot of freezes and crashing with sygic and earlier editions of some browsers.
pfoxdizzle said:
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I thought it was just me. I've been playing The Bard's Tale on it and got the update the same night. I, too, have noticed random reboots where the game will freeze, and then 5 seconds later the tablet is rebooting. I honestly thought it was the game, but since you're saying it happens to you on Performance mode only, and that is exactly where I am as when I am playing the game, maybe it is performance mode and not hte game causing mine as well.
if that is the case, chalk me up for these random reboots as well.
pfoxdizzle said:
No changes. Completely fresh and.un modified tablet
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Mine was far from fresh, but only rooted, no other mods made.
pceasar said:
Honestly, I have gotten some and I'm fresh totally stock just got mine. However, I stopped connecting it to dock and uninstalled songza and MX player. Its a shot in the dark but lets see if any reboots, otherwise back to amazon.
Click to expand...
Click to collapse
I don't think that will help as 1) I have neither of those two apps, and 2) mine happened when I was not connected to a dock at all.
My tablet after JB update, has been getting freezes. Screen is black but lit and I have to reboot :\
Aria807 said:
My tablet after JB update, has been getting freezes. Screen is black but lit and I have to reboot :\
Click to expand...
Click to collapse
To fix this reboot and screen blank out, you guys need to reflash the full version of JB.
buhohitr said:
To fix this reboot and screen blank out, you guys need to reflash the full version of JB.
Click to expand...
Click to collapse
Might not be a bad idea. But a full install won't allow us to use root keeper methods, so we'd then have to wait for a new root method, right?
I'll deal with the idiosyncrasies until i can root JB and then "blob" my pad (I've been dying to say that, can't you tell?).
Sent from my rooted BIONIC running ICS 6.7.247 (!) via Tapatalk 2
johnlgalt said:
Might not be a bad idea. But a full install won't allow us to use root keeper methods, so we'd then have to wait for a new root method, right?
I'll deal with the idiosyncrasies until i can root JB and then "blob" my pad (I've been dying to say that, can't you tell?).
Sent from my rooted BIONIC running ICS 6.7.247 (!) via Tapatalk 2
Click to expand...
Click to collapse
To root a JB locked bootloader=NO, but for unlocked bootloader=YES. Another way to solve the reboot/screen issue and keep root is to downgrade to .30 (full version), root, then OTA root keeper to save root then let the JB OTA upgrade back to JB, then restore root.
buhohitr said:
To root a JB locked bootloader=NO, but for unlocked bootloader=YES. Another way to solve the reboot/screen issue and keep root is to downgrade to .30 (full version), root, then OTA root keeper to save root then let the JB OTA upgrade back to JB, then restore root.
Click to expand...
Click to collapse
That is exactly what I did. I'll test later this evening, but so far it has been a lot snappier *and* no random reboots.
But, I've also not run performance mode either.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
johnlgalt said:
That is exactly what I did. I'll test later this evening, but so far it has been a lot snappier *and* no random reboots.
But, I've also not run performance mode either.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
Click to expand...
Click to collapse
Also highly recommend to install browse2ram, make all your browsers(stock included), kick ass!!!
buhohitr said:
To root a JB locked bootloader=NO, but for unlocked bootloader=YES. Another way to solve the reboot/screen issue and keep root is to downgrade to .30 (full version), root, then OTA root keeper to save root then let the JB OTA upgrade back to JB, then restore root.
Click to expand...
Click to collapse
What's the point of doing this? I was already on .30 to begin with, ran Debugfs rooted .30 and OTA rootkeeper backed up, and I got the OTA update from JB a week later, which had the SOD issue. Why downgrade and upgrade?
Aria807 said:
What's the point of doing this? I was already on .30 to begin with, ran Debugfs rooted .30 and OTA rootkeeper backed up, and I got the OTA update from JB a week later, which had the SOD issue. Why downgrade and upgrade?
Click to expand...
Click to collapse
The point is it's going to solve your random reboot/blank screen issue. Most of people did exactly what you did included myself, but once you are on JB and experiencing reboot and blank screen, you need to reflash because the install did not done correctly some how. If you reflash a full version of JB, it will fixed the issue but then you don't have root, this is not a problem if you're unlocked. So if you still have locked bootloader, you need to downgrade with full version of .30 then re root. when you install a full version it automatically wipe for you so you don't need to wipe before downgrade. Once you have a fresh install of .30, now you can use OTA to upgrade to JB and keeping root.
Ah gotcha. Well in this case, I might as well just unlock my bootloader and flash [ROM][10/3][JB4.1.1] - Stock Root Odex / De-Odex - 10.4.4.16 Base since it's stock based minus bloatware?
Aria807 said:
Ah gotcha. Well in this case, I might as well just unlock my bootloader and flash [ROM][10/3][JB4.1.1] - Stock Root Odex / De-Odex - 10.4.4.16 Base since it's stock based minus bloatware?
Click to expand...
Click to collapse
Sure you could do that, but I'm waiting for Zeus Rom. This rom is amazing with I/O.
Actually, could the problem be the idle clock speed? I don't recall the TF700 having a 51mhz speed. I thought lowest multiplier was 102mhz. Perhaps that's why it is freezing/sod
I'm gonna raise my min clock speed at 102mhz and see if it freezes any more
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
buhohitr said:
To fix this reboot and screen blank out, you guys need to reflash the full version of JB.
Click to expand...
Click to collapse
Well, I had the same issue on ICS stock and custom rom and JB so I don't think this is anything to do with reflashing, but our old friend IO.
Like people have mentioned before ,change the number of background processes to 4.
My MAXX HD will randomly reboot. This can happen during heavy usage, or when my phone is just sitting in my pocket. It (was) non-rooted, a large amount of apps installed, and on 9.16.6. The phone started this reboot cycle about a month and a half ago.
I performed a factory reset, and it continued it's reboot cycle. The only apps that got installed were K9 mail and Touchdown.
Any ideas what could be happening?
First thing I'd try is fix permissions.
banesong said:
My MAXX HD will randomly reboot. This can happen during heavy usage, or when my phone is just sitting in my pocket. It (was) non-rooted, a large amount of apps installed, and on 9.16.6. The phone started this reboot cycle about a month and a half ago.
I performed a factory reset, and it continued it's reboot cycle. The only apps that got installed were K9 mail and Touchdown.
Any ideas what could be happening?
Click to expand...
Click to collapse
Uninstall the apps that you've installed since this has started. Then, start reinstalling until you get it to do the same thing. Then, stop using whichever app is causing.
RikRong said:
Uninstall the apps that you've installed since this has started. Then, start reinstalling until you get it to do the same thing. Then, stop using whichever app is causing.
Click to expand...
Click to collapse
That is the thing. I am at factory reset. It restarted prior to even installing a single app.
PhoneBill said:
First thing I'd try is fix permissions.
Click to expand...
Click to collapse
How does one do that?
banesong said:
That is the thing. I am at factory reset. It restarted prior to even installing a single app.
Click to expand...
Click to collapse
most people dont like to hear this fix, but in most cases the best way to fix these things for good is to flash it back to stock. a fdr just removes data and doesn't fix errors in the system.
if you are still on 9.16 and want to keep that, you will need to use the 1.21 utility.
---------- Post added at 09:15 AM ---------- Previous post was at 09:13 AM ----------
banesong said:
How does one do that?
Click to expand...
Click to collapse
pretty sure you need a custom recovery, i dont think stock can do it.
Well... flashing stock seems to have solved it; a full day with no reboots at this point. Updates took, too!
Thanks all.
I had the same issues, stock, rooted, did factory reset no app installed VZW tech replaced phone under warranty. Now I have phone I can't unlock and still trying to root. not much help just passing some info along
Does anyone have a problem with random "pauses" while using apps? It's totally not noticeable for applications that aren't continually running animations (ie: kindle, text scrolling) but becomes evident when doing thins such as:
- recording video (the "pause" will cause the recording to stop randomly for both continuous and time lapse)
- playing games (will cause the game to go to the pause screen)
- tasker programming (I think this is affected because tasker will randomly close itself without a FC dialog, profiles and tasks seem okay)
I turned on debugging to see if it was a dirty screen or anything, but the touch coordinates don't change at all when the "pause" happens. Anyone have an idea how I can fix this? It is rather crippling to the N5.
I am rooted and I have seen this problem on all roms (and I believe I noticed it on stock too...)
I use a ballistic case, if anyone else has had problems with it...
Thanks in advance!
Using N5 on Carbon + Franco kernel
I guess no one's ever had this problem before? =[
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
I've tried out a few roms (factory reseting and cache clearing between each one) to see if it was any one problem, but whether AOSP or CM based, I still have the problem =/
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!
Do you mean stock + unrooting? I think I remember having the problem back then, but I don't quite remember before I rooted...I'll try going back to stock w/ root first and see if it's still happening. Thanks!
Click to expand...
Click to collapse
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?
mistahseller said:
Yes follow the link in the general to go back to complete stock and that will eliminate anything and everything that could be an issue related to software.
For what it is worth, what method did you use to root?
Click to expand...
Click to collapse
I used the Chainfire's autoroot (http://forum.xda-developers.com/showthread.php?t=2507211) on Windows.
mistahseller said:
Have you tried factory reset? Fixes most problems. Could be Franco's kernel has a bug in the latest release.
Sent from The Deathstar
Click to expand...
Click to collapse
Bruce Lee said:
Have you tried going back to complete stock to see if that fixes the problem?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm, I think it worked. I haven't tested it out for lengthy periods of time but I haven't noticed any pausing anymore! =]
I followed the unroot instructions to return to stock. Although I didn't relock the bootloader.
Then I booted up stock and it seemed like it works fine.
I reinstalled CWM recovery through adb (same as I did the first time) and proceeded to reflash
It seems like the problem is gone now on custom ROM as well. Interestingly enough, if I nandroid restore my old backup, I do get the problem again.
Is there something different between reflashing stock part and wiping from factory/data reset + system partition format + wipe cache + wipe davalik?
Thanks for your help guys! I was sure before that it was hardware since I had the problem on stock w/ root, but thankfully it's not a hardware problem! =]
Anyone else?
Fully stock? Do a factory reset from stock recovery.. Should fix it. If you're on a custom rom, do a clean flash. (wiping everything except data)
- Sent from an IceCold Hammerhead!
Thx for the advice.
But was wondering if anyone else is getting them.
I'm trying a few things to fix it as I never had a reboot since I owned the phone in November last year, until 4.4.3
At the moment I'm trying an older radio, but it's hard to pin since my last try of using a 4.4.2 kernel kept me up for 35 hours before it happened again.
got an rma replacement.. still happening
meangreenie said:
got an rma replacement.. still happening
Click to expand...
Click to collapse
Did you restore a nandroid on it or anything?
rootSU said:
Did you restore a nandroid on it or anything?
Click to expand...
Click to collapse
no, is completely fresh
tried everything under the sun over the last month.. factory image installs, running safe mode, no apps installed, new Google account... ect ect
can't stop a soft reboot occurring every 2 or 3 days.. I use to have 'up times' of over a month on 4.4
meangreenie said:
no, is completely fresh
tried everything under the sun over the last month.. factory image installs, running safe mode, no apps installed, new Google account... ect ect
can't stop a soft reboot occurring every 2 or 3 days.. I use to have 'up times' of over a month on 4.4
Click to expand...
Click to collapse
Upgrade to 4.4.4 and see if it sorts out?? You get random reboots even when the phone is in safe mode?
vin4yak said:
Upgrade to 4.4.4 and see if it sorts out?? You get random reboots even when the phone is in safe mode?
Click to expand...
Click to collapse
I'm on 4.4.4.. op was posted when 4.4.3 was out.
I know it's weird, i was very surprised to see my new replacement do it too a little a while a go
.. shrugs
meangreenie said:
I'm on 4.4.4.. op was posted when 4.4.3 was out.
I know it's weird, i was very surprised to see my new replacement do it too a little a while a go
.. shrugs
Click to expand...
Click to collapse
Perform a factory reset and see if it sorts things out??
I'm assuming you're stock, unrooted??
still suffering from this
i have noticed that if location is not set to off, it's much better, where it can run for over a week at time
as soon as i turn location off, I'm lucky to get much over 30 hours before it soft reboots
going back to 4.4 it is completely stable as it always was
So anyone else having random restart issues no matter what firmware you are running?
I am having this issue even after updating the firmware (yes I managed to get it updated lol didn't realize need to do it in increments rather straight to the latest).
I found a work around sort of but it requires having my hotspot on and another device connected at all times to keep the phone from restarting randomly.
Has anyone else ran into this issue and have a fix? Could it be a battery optimization setting?
Thanks
i got it when i update the rog 5 to latest version so i factory reset it then worked well
messhary said:
i got it when i update the rog 5 to latest version so i factory reset it then worked well
Click to expand...
Click to collapse
Ok thank you for replying, I just finished backing up with Migrate and going to do a factory wipe and then restore all my apps. Hopefully that solves my issues.
I have the same problem for last two firmware updates, for each update I need to do a full factory reset in order to let it work again!