• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Random Reboot

Buggy firmware usually, occasionally a rogue app. What device you got, make, model and Android version? Have you checked for manufacturer updates and/or fixes?
 
Buggy firmware usually, occasionally a rogue app. What device you got, make, model and Android version? Have you checked for manufacturer updates and/or fixes?
I see the word "buggy" as very general. Could you be a bit more specific?
Sgh-t599n
4.4.4 Carbon Rom
 
Reboots can be caused by low-level problems in the particular version of Android that was built for the device. It's crashing completely and is rebooting, basically the equivalent of a Windows BSOD, or Linux or OS X kernel panic. Can be an actual problem with the hardware causes restarts as well, usually quality issues with cheapo Chinese devices.

"Carbon ROM" is not the original Samsung firmware for this phone, it's a custom third-party ROM, so I guess there's bugs or other stability issues with it, or something was wrong with the way you installed it.

FYI: When CyanogemMod was first ported to the Oppo Find 7, that was rather prone to reboots, but eventually the devs were able to fix those problems, probably using information from bug reports and telemetry.
 
Last edited:
I see the word "buggy" as very general. Could you be a bit more specific?
Sgh-t599n
4.4.4 Carbon Rom
Not sure how you expect specific answers without telling the whole story.

And even then, it's impossible.

Do you have a rogue app?

Did you check the md5 checksum of the rom before installing? Was it a good download before you installed?

Did you follow the rom installation instructions?

Did you clean flash or dirty flash?

Did you clear cache and Dalvik?

Does the rom have a recovery dependency? Are you using the right recovery?

When did it start relative to your rom install?

If it was OK before, did you attempt a nandroid recovery?
 
On the hardware side, I had a Galaxy Trend that rebooted several times a day and the culprit turned out to be a faulty power button!!
 
Back
Top Bottom