Database Users

Random Power Offs and Reboots?

My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.

yep
+1
Not very often but very annoying if you use your phone as alarm clock.

I honestly haven't experienced either with my SGS. I can sympathise though as my Milestone used to do both way too often (hence swapping for the SGS).

It hasn't happened to me.. It might be running a software or hardware watchdog to reboot automatically when the system panics. Ensure you are using a stock rom, otherwise, it may even be faulty hardware

Would happen several times a day on my Motorola Milestone so I sent it back and got the SGS. Totally rock solid. Only time it reboots is when I want it to. Maybe you have a rogue app?

you guys have any changes to the CPU speed whatsoever, task killers and all? i once used SetCPU and it sort of sent me into a random spree of reboots and such.
i remember rebooting, scanning 10gb of media, auto-reboot... repeat 4 times. lol.

Well it hasnt happened since yesterday. I will flash to froyo today just in case it was software related
Sent from my GT-I9000 using XDA App

dakine said:
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
Click to expand...
Click to collapse
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned

AllGamer said:
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
Click to expand...
Click to collapse
Link would be helpful, because I can't find that topic.

WOW, old thread that got dug up, for me it was just a software issue. I flashed many roms since and haven't had it happen again. I never reset my battery stats but I think clockwork mod recovery has an option to do that so most of the custom roms make that easy.

I also had random reboots and power-offs, on average once every 2 weeks, running on stock-firmware JF3. Problems did not go away when I manually upgraded to JM2. Problems stopped when I upgraded to Froyo...

Problem with internet connectivity on Aria.

Hey all,
I've got this odd problem with my Aria running Cyanogen 7.1 with Drowing's kernel.
Consistently throughout the day while moving from place to place where I either have Wifi, strong 3g connections, or both, that I will lose internet connectivity until I reboot which will restore both internet and sync/facebook capabilities. At first I attributed the problem to Juice Defender messing with wifi and 3g disabling so I uninstalled it. After today though, I realize the problem must be something else because the exact same thing happened.
I have yet to try doing a data wipe and re-installing 7.1, but I will if it could fix the problem.

There have been many reported data issues (in the kernel's thread and the nightlies' thread) with the later builds of CM7 using that kernel.

You should be able to simply flash the CM7 ROM on top of your current installation, without wiping anything, which will revert you back to the default kernel. It's not clear why but when the Android version number bumped up to 2.3.7, DC's kernel has caused data problems for some people. You shouldn't need to wipe any data to correct the problem, but you will have to stop using the kernel -- at least until someone figures out why it's happening.

Gratitude for the replies.
I was getting that paranoid Windows itch that something was just not feeling right so I wiped everything and re-installed 7.1. Surprisingly without the kernel I haven't had any issues with the internet problem described above and the phone is actually performing better than ever. I am interested in finding out exactly why that happens, but I can live without it.
Thanks again guys!

tebuddy said:
I am interested in finding out exactly why that happens
Click to expand...
Click to collapse
The developer is as well.

I'm still having this issue with the stock kernel. Does anyone know which was the last nightly that didn't suffer from this?

ThePettyTyrant said:
I'm still having this issue with the stock kernel. Does anyone know which was the last nightly that didn't suffer from this?
Click to expand...
Click to collapse
I have not had any data issues with any nightly using the stock kernel. You could re-flashing your current one (or later if possible).

I found that any 3rd party apps that control Wifi (Scanners and such) tend to permanently disable/make me unable to connect until I reboot.

Theonew said:
I have not had any data issues with any nightly using the stock kernel. You could re-flashing your current one (or later if possible).
Click to expand...
Click to collapse
I've been running the latest nightlies during this time but I haven't reformatted in probably 2 months.
I went into my router and gave the Aria a reserved DHCP address 4 days ago. Since then the data hasn't dropped out a single time. Maybe dhcp is part of the problem?

[Q] Can reboots be caused by location?

I'm have troubles with my HD2 randomly rebooting itself for apparently no reason. Initially I had a barebone CM7 ROM, and it seemed to reboot much more frequently when I came home from university. As soon as I got home for this break, sure enough, it began rebooting again. I then switched to a CM10 ROM, thinking it was just the previous ROM messing up, yet the problem persisted.
If it's not a ROM causing it, what could it be? It's really annoying having the phone shut off randomly while I'm doing something, and I'm worried it'll end up worse just because of how frequently it reboots.

overheating? failing touch screen? dodgy battery? failing hardware? faulty/fake copy SD card? old/wearing out sim card? some app that doesnt play nice on the hd2?
they can all cause reboots on multiple roms, along with another half a dozen reasons, i'm sure.

If the phone did reboot from any of those, it still wouldn't explain why it doesn't happen when I'm at school. I'm not exaggerating; once I go back (about ~126 miles away from home), it never reboots like this. At this point, you may be thinking, "Why not just wait to go back?" I have only two semesters left, and I want to get this fixed prior to me moving back here.
But nonetheless:
overheating?
Click to expand...
Click to collapse
I've held my phone in front of an AC to test if it's overheating, and it still rebooted. I had the back cover off and the air blowing into the battery.
failing touch screen?
Click to expand...
Click to collapse
My 'End' button is failing, but my touch screen seems to work just fine. Is there a way I can test if it's the touch screen causing the reboots?
dodgy battery?
Click to expand...
Click to collapse
I have two batteries, one original and a new from Amazon. Reboots occur using either of those.
failing hardware?
Click to expand...
Click to collapse
Quite possible, it's an old phone, but I feel that it would reboot regardless of where I'm at if this was the case.
old/wearing out sim card?
Click to expand...
Click to collapse
Same as above.
some app that doesnt play nice on the hd2?
Click to expand...
Click to collapse
I thought this was the case at first as well, but I uninstalled all my apps on the barebone CM7 ROM, and reboots still occurred. Even after doing a fresh install of this CM10 ROM, the phone rebooted before I even began installing apps to it.
Are there any files that don't get changed by flashing a new ROM? I was thinking that it could possibly be the modem I have flashed to my phone, but I wasn't sure if flashing a new ROM automatically changes the modem as well. Can I get some insight on this?

By modem do you mean the radio? It's unlikely to be the radio itself, however it could be something like the phone struggling to switch between 2g and 3g,,try it with the phone in only 2g mode,, perhaps you have a faulty cell tower in your area,,unlikely but not unknown.

Yeah, sorry about the terminology haha. But thank you, I'll try that and report back!

So disabling the 3G didn't change anything, but I noticed a drop in the frequency of reboots when I disable my wifi. Could some of my router settings be messing with the phone? I tried deleting the network on the phone and re-adding it, but the reboots remained consistent.

adobrakic said:
So disabling the 3G didn't change anything, but I noticed a drop in the frequency of reboots when I disable my wifi. Could some of my router settings be messing with the phone? I tried deleting the network on the phone and re-adding it, but the reboots remained consistent.
Click to expand...
Click to collapse
still sounds like hardware really, as suggested.
does it reboot even with the phone in airplane mode?

But the phone doesn't reboot when I'm in the city where my university is located, only when I come back home. That doesn't really lead me to believe that it's the hardware.

I have the same problem with the
[1.Dec.2012][All in One] EvoHD2v10 ICS 4.0.4-full HWA "Fastest ICS ever"
it reboots more than 3x a week!!!!!!!

For me, it can literally get up to 10 reboots per day, when I'm in this particular city. It gets very aggravating, and I'm worried about the stress it's putting on the hardware by constantly booting back up.
Anyway, I decided to say **** it and start from scratch. I don't think it's a hardware problem, so I decided to go back to the beginning. I formatted and re-partitioned my SD card for Native SD-compatibility. I flashed Xylo's 4.1.2 PA ROM. Now it's time to use it like I would normally.
If anyone is experiencing the same problem as me, or reads this in the future with the same issue, I'll try to keep the post up-to-date with what stopped the reboots for me.

dont forget to clear out your sd card, , leftovers from previous roms can cause issues. Easiest way is to flash teh new rom, then immediately in CWM do a wipe data/factory reset, as this clears out both fat32 and ext folders.

AW: [Q] Can reboots be caused by location?
I had the same problem with my fathers HD2. I installed clK before and it rebooted the last time quite often.
So I reinstalled everything. I started installing the official HTC WinMo 6.5 Rom.
Then I've done Task29 and installed MagLdr and then a Radio which Supports 576 MB Ram. (I think it was 2.15.xx) , repartitioned it for BlueOrange Mix Rom 1.2 (The best I ever installed so far) and flashed it in CWM.
So the HD2 is running since 150 Hours without any Problems.
P.S.: Task29, MagLdr, Radio Installation and Repartition has been done in HD2 All in one Toolkit.
Greetings by Myself5 and I hope I could help you.
Sent from my GT-I9100 using xda premium

[FIX!]Bad Factory Images - Fix Reboots and Bootloops

I've been really interested in finding the cause of these reboots and bootloops that are affecting many people. Right out of the box, the tablet does 2 updates and somewhere things go south. The tablet starts rebooting at random intervals which can lead to further errors and bootloops.
Knowing a thing about Nexii devices, several people now have working tabs. The trick is reflashing the stock image or a CM rom.
My conclusion is that a big batch must have been flashed with a bad stock image. It takes a little know-how to manually reflash stock, but there are 1-Clicker PC apps that make it easier.
Anyone wanna write a little batch file that JUST automates reflashing stock image?
Also for those with rebooting or bootlooping N7s, just factory wiping isn't the fix because the files you are restoring are bad. People are wiping over and over with no better results.
Hope this info helps and I'll try to elaborate with some steps and links. The information is on XDA already, probably to some effect of such a title like "Stock Images".
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

Perhaps you can compare the checksums for all the files in the bad /system against the good /system using some scripts?

An interesting project, and more than Google/ASUS are (apparently) doing for us.
I'll help in any way I can...

I have no problems believing Google will patch this soon, but in the mean time people have rebooting Nexus 7s and eventually it will go into a bootloop which requires a wipe to fix.
If someone could make a quick little PC script to grab the stock and automate the fastboot flash commands. Just a temporarily permanent solution until Google patches it.
The problem is most people using stock probably don't realize it is rebooting. Mine would reboot when idle and I'd never know unless I checked uptime. So people are grabbing their tabs and finding it off because it rebooted, corrupted, bootloops, and runs till the battery dies.
Anyone using straight stock should check their uptime status in Settings. If your Uptime looks low, it is probably rebooting in the night or when idle. If you do nothing, you risk losing your data.
Its best to backup your data files, wipe, flash a stock image, and restore your data.
Sent from my Nexus 7 using XDA Premium 4 mobile app

If you are talking about the random reboots, for most people, that isn't about corrupted images. I thought you were talking about some bootloop problem.
Corrupted user data from those random reboots is a possibility which maybe is what you are saying, but that will only get fixed if you fix the random reboots, which I don't believe are caused by corrupted factory images for most people.
Anyway if it really is about bad factory images, one should be able to compare good and bad and isolate the differences.
If the differences can't be located then it puts to doubt whether the theory is correct or whether one isn't looking in the right places.

sfhub said:
If you are talking about the random reboots, for most people, that isn't about corrupted images. I thought you were talking about some bootloop problem.
Corrupted user data from those random reboots is a possibility which maybe is what you are saying, but that will only get fixed if you fix the random reboots, which I don't believe are caused by corrupted factory images for most people.
Anyway if it really is about bad factory images, one should be able to compare good and bad and isolate the differences.
If the differences can't be located then it puts to doubt whether the theory is correct or whether one isn't looking in the right places.
Click to expand...
Click to collapse
That's exactly what I'm saying. Bad images = reboots = bootloops = wipes = loss of data.
When it reboots 6 times a day, corrupted userdata is going to happen eventually.
I don't really care about "why" as much as just helping people find a solution to fix it while Google makes with a fix. The ONLY thing that fixes the reboot issue is to reflash the stock image. I'm just sharing my findings. This is what I did and with my suggestions, several others are finding success at fixing the reboots.
This fixes the reboots. Which fixes the random bootloops.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Put it this way, I've reflashed stock images from google published tgz file many times and never gotten rid of random reboots. They eventually come back if I use Chrome. If I don't use Chrome the reboots go away. This is for MY usage pattern. Chrome may not be a trigger for everyone and likely isn't even the root cause, however I have flashed the stock images and still get random reboots.
In over 3 weeks of folks experiencing random reboots, I doubt I am the only person to have flashed the stock images and still have been able to reproduce random reboots.
Personally I like to investigate and understand why something fixes a problem. I like to understand why some procedure would fix for one person but not the next.

I would suggest flashing a CM rom. Test. Then flash back to stock. Test.
Somewhere, something gets fixed.
I also found Next Browser. Its based off Android Browser and much faster with great swipe options. I have been using both simultaneously though without fail... but chrome is going to be uninstalled here soon. Unless you need Chrome for specific purposes, its much slower then others.
Sent from my Nexus 7 using XDA Premium 4 mobile app

FWIW running cm10.2 nightlies and only reboots are those I intentionally do to load up a new nightly. CM's so much better than stock.
Sent from my Nexus 7 using Tapatalk 4

It's unlikely that the stock factory image is the cause of random reboots.
I've flash cm10.2 nightly on mine and it still reboots every 20 minutes whenever WIFI is turned on.

wweeii said:
It's unlikely that the stock factory image is the cause of random reboots.
I've flash cm10.2 nightly on mine and it still reboots every 20 minutes whenever WIFI is turned on.
Click to expand...
Click to collapse
Hold off for the JSS15Q update which may improve your situations...granted its for the multitouch fix but they are reporting it may fix bootlooping, albeit sacrificing custom ROMs and root temporarily. All current ROMs use the (buggy) JSS15J firmware base so when Q hits it may be the fix needed. On another note I doubt it's bad factory images, I've only had 1 random reboot in the 10 days I've had my Nexus 7. That, granted, was a bootloop which I had to factory reset for but it hasn't happened again (touch wood.)

Yeah, this hopefully all disappears after today.
If you use stock and keep track of your uptime, you might notice your N7 is rebooting quite often. I never noticed it until I found the reboot thread, and checked. It said the uptime was like 5hrs but was on all day and night (I was working). I checked again in the morning and it had a 2 hr uptime. This went on for a while. I never actually caught it reboot. It would champ through games and hours of use with no problems, then reboot when idle.
The bootloop you had was probably from the reboot issue. It reboots frequent enough and shuts down during cleanup and corrupts user data.
I've been running CM and no reboot issues/bootloops at all. So whatever it is, it is with the stock rom. Thankfully this patch is sooner then later and hopefully fixes the Multitouch AND the reboots. I think the bootloops are the result of the resets.

player911 said:
Yeah, this hopefully all disappears after today.
If you use stock and keep track of your uptime, you might notice your N7 is rebooting quite often. I never noticed it until I found the reboot thread, and checked. It said the uptime was like 5hrs but was on all day and night (I was working). I checked again in the morning and it had a 2 hr uptime. This went on for a while. I never actually caught it reboot. It would champ through games and hours of use with no problems, then reboot when idle.
The bootloop you had was probably from the reboot issue. It reboots frequent enough and shuts down during cleanup and corrupts user data.
I've been running CM and no reboot issues/bootloops at all. So whatever it is, it is with the stock rom. Thankfully this patch is sooner then later and hopefully fixes the Multitouch AND the reboots. I think the bootloops are the result of the resets.
Click to expand...
Click to collapse
Surprisingly no, I used Reboot Logger and there were no random reboots after I did the factory reset, the uptime was continuous, since the bootloop and factory wipe no reboots were logged (that was 5 days ago).

Reboots, can't call, no sound!

My nexus 6p has worked fine for months however I woke up yesterday morning to find it would not play a video on YouTube. Continuing to use it I noticed the following symptoms:
Wont play videos of any kind (youtube, Facebook etc)
Speakers do not work at all
phone hangs and will not connect during incoming or outgoing calls. The call may connect after several minutes of the screen hanging on the blue calling screen however speakers don't work anyway.
Phone restarts itself randomly
I have tried a hard reset from recovery, wiped cache, booted to safe mode etc with no change.
The phone is bone stock and has not been rooted.
Any suggestions?

At this point I'd try rooting and just flashing stock ROM, don't install anything and see where it goes. If it survives, then maybe it was a rogue app, but that's a lot for an app to do - so it could be a hardware issue.

Same problem here.
teh roxxorz said:
At this point I'd try rooting and just flashing stock ROM, don't install anything and see where it goes. If it survives, then maybe it was a rogue app, but that's a lot for an app to do - so it could be a hardware issue.
Click to expand...
Click to collapse
I've got the same problem, but it happens only on stock, when I've got Chroma installed, everything is fine. One time it happened under Chroma. I don't know what causes it. Reinstalling factory images or even 7.0 doesn't help. Custom kernels didn't bring any improvement either.
Maybe there are some music drivers or something.

Yakksiek said:
I've got the same problem, but it happens only on stock, when I've got Chroma installed, everything is fine. One time it happened under Chroma. I don't know what causes it. Reinstalling factory images or even 7.0 doesn't help. Custom kernels didn't bring any improvement either.
Maybe there are some music drivers or something.
Click to expand...
Click to collapse
It could be a driver thing. Didn't look like a device issue, as it'd be constant. I would go back to stock and note when it happens and then flash a custom ROM and repeat the steps, to perform a controlled test. While doing so, take logcats so Beans / others can review them.

Gone to the service becuase even on a custom ROM I couldn't get any sound. They said that it was a hardware problem (I don't agree but we will see).