Develop Bugs

Phone keeps resetting randomly

Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.

okay, i'm not a dumbass (maybe). Phone keeps resetting on its own randomly still but less frequently after I overclocked.

How is your battery condition? Like how old is it? Do you have and tweaks (kobridge or phakker scripts)
Cpusleep app? And you said it happens on a few ROMs, I would say it maybe a battery or hardware issue. Also, do you check the MD5 sums before you flash the different ROMs?
Sent from my SPH-D710 using XDA

Battery condition is good, I actually have two oem batteries that I use daily and swap them when one dies.
I'm not running any tweaks currently, but when I flashed the roms recently its been through a nandroid backup of my previous working rom. But I'll try a clean install without a backup and see if that works. Thanks
Sent from my SPH-D710 using xda premium

Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium

Subiegsr said:
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Are you using a stock battery charger? Is the charging cable damaged or loose? I had an issue with an after market charger making my phone freeze up before.
Not to my knowladge, but it never hurts to check it. I use md5sum app.
Sent from my SPH-D710 using XDA

Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!

What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2

Subiegsr said:
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
Click to expand...
Click to collapse
No problem, just wanna find out the root cause of the reboots.
Sent from my SPH-D710 using XDA
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
cp320703 said:
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You may be right on the money with that. It could be causing script confliction. Between the ROM and the CPU app. But I do know that cpu app scripts will override the ROMs cpu scripts, but not all the time.
Sent from my SPH-D710 using XDA

Subiegsr said:
Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
Click to expand...
Click to collapse
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app

FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA

g_ding84 said:
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I have 3 OEM and 4 extended they all do the same thing.
Sent from my SPH-D710 using xda app-developers app

You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817

tysonrj said:
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
Click to expand...
Click to collapse
Thank you very much. I didnt know this was an issue with the phone.

FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Does it reboot in download mode? If not..I would odin to stock and go from there see if that fixes things.

Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).

Subiegsr said:
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Click to expand...
Click to collapse
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.

milky1112 said:
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
Click to expand...
Click to collapse
Thanks man. It started doing it today and I took out the SD card and it hasn't done it since. So maybe it was the SD card this whole time?
Hopefully it is.
Sent from my SPH-D710 using xda premium

[Q] Battery Issue, Never go below 100%

Alright, As the title says I'm having a battery issue. I just bought the phone used, unlocked it, Flashed CM 10.1, and ever since changing ROMs the battery hasn`t gone down below 100%. I've let the battery go flat, wipe Battery_stats.bin. Issue remains un resolved. I also tried to recalibrate using an app, still no improvement. Any ideas on how it can be fixed? Anyone out there having same/similar problems?
EDIT: Also, I`m rooted & have CWM installed.

let me get this straight
your battery is always full?

Try With Change Your Kernel. But Must Match with Recomendation ROM Kernel.
Sent from my ST15i using xda premium

raymuy said:
let me get this straight
your battery is always full?
Click to expand...
Click to collapse
So it claims to be, But isn't, I wish it was an eternal battery! That'd be awesome
SigitCGumilars said:
Try With Change Your Kernel. But Must Match with Recomendation ROM Kernel.
Sent from my ST15i using xda premium
Click to expand...
Click to collapse
Alright, Is there a thread or tutorial i could follow? Thanks for the help!

LGOG acting very strange

My phone is acting very weird ever since I've flashed evolutionmods kernel. My battery dropped off about 50% instantly, and is now very hot all the time and will not charge above 44%. At one point i took it off the charger, but the charging animation continued till i rebooted the phone. Its also not getting any service anymore, I get data, but no voice reception. I have since restored to the stock kernel but all my issues remain. I've never experienced anything like this, what the hell is going on?
Sent from my Nexus 7 using XDA Premium HD app

I noticed the heat issue and the charging issue, when I charged it the percentage would go down until I rebooted it and it still did it every once in a while until I rebooted it. I did a full wipe and reflashed Lifeless then flashed Joker's kernel and did the ##72786# and everything has been fine.

You guys need to post this in his kernel thread. Also ill have him revert the charging patches but ill have to look at his github to see what's causing the other issues. You guys should try to get logcats or even better kmesg logs.
Sent from my LG-LS970 using xda app-developers app

jokersax11 said:
You guys need to post this in his kernel thread. Also ill have him revert the charging patches but ill have to look at his github to see what's causing the other issues. You guys should try to get logcats or even better kmesg logs.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Good looking out guys, i have totally different source built up from any of the last kernels you all have flashed.
I have been running it for about 2 days now and its very nice.i get a little heat but that when running a bunch of benchmarks.

jokersax11 said:
You guys need to post this in his kernel thread. Also ill have him revert the charging patches but ill have to look at his github to see what's causing the other issues. You guys should try to get logcats or even better kmesg logs.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I wouldve posted there but as i said in my post i have since flashed back to the stock kernel and its still doing it occasionally. So i think its a device issue rather than a kernel issue, just coincidental that it started when i flashed evolutionmods kernel.
Sent from my LG-LS970 using Tapatalk 2

random reboots with cm10 nightlys

anyone possibly have a solution to the random reboots issue with these nightlys? also having a lot of trouble with bluetooth devices not connecting automatically. I have to go into the settings and connect manually. pretty annoying.
any help is greatly appreciated!!!

Good grief wrong thread
Sent from my SGH-I747 using xda app-developers app

For the reboots, are you on the jb bootloader? As for Bluetooth, try turning your bt device on, then turning on bt fir the phone

It's called nightly for a reason. They're unstable builds that gradually progress. If you can't handle the bugs, stick with the stable build.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta

lilmeanz said:
Good grief wrong thread
its really annoying that people like you always post this dog **** rather than offer up a link to where this thread should go. how about a little less holiness and bit more constructiveness.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
mrhaley30705 said:
For the reboots, are you on the jb bootloader? As for Bluetooth, try turning your bt device on, then turning on bt fir the phone
Click to expand...
Click to collapse
no special bootloader. cm10.1. no special kernel either. whatever comes with the build is what im using. the bt used to work fine then this started happening.
Domoo said:
It's called nightly for a reason. They're unstable builds that gradually progress. If you can't handle the bugs, stick with the stable build.
i get that these are unstable..... how come then was it working just fine at one point then it all went to **** after updating with one of the rc's and/or nightlys? if they are supposed to get progressively better then how do you explain this??
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse

Nobody said that they get progressively better. They progress as they add new features or tweaks that tend to break other things. Fixing one problem may cause another to show up. If every build was to improve the rom, it would be stable in a month, but that's not how it works.
The bluetooth issue has been beat to death in the i747 cyanogenmod development thread. All you can do is wait till they fix the issue. Just flash back to a build with the bt working and follow the development thread. I'm sorry if this comes out in the wrong way.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta

Phantom touches. Never had them before

My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?

littleromeo said:
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
Click to expand...
Click to collapse
I had the same experience the other day. Currently running
Latest version of Clean Rom with ElementalX kernel. After I was finally able to reboot, all was well.
Sent from my Nexus 7 using Tapatalk

dantegl36 said:
I had the same experience the other day. Currently running
Latest version of Clean Rom with ElementalX kernel. After I was finally able to reboot, all was well.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm running stock+xposed.
Testing with multi touch app seemed to have made it worse for me, even prevented me shutting it down. Hope it doesn't come back.

littleromeo said:
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
Click to expand...
Click to collapse
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app

Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If an RMA is not an option, try Abel's solution. It boils down to bad hardware and no quality control. I had to RMA my first one for the exact same reason. Second one is fine.
If you do some googling, you will see that thousands of people have had this problem. Any definitive word from Google or Asus? You wish. They will never admit they made a mistake.
littleromeo said:
I'm running stock+xposed.
Testing with multi touch app seemed to have made it worse for me, even prevented me shutting it down. Hope it doesn't come back.
Click to expand...
Click to collapse

Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, will do if it starts again.
Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Aerowinder said:
If an RMA is not an option, try Abel's solution. It boils down to bad hardware and no quality control. I had to RMA my first one for the exact same reason. Second one is fine.
If you do some googling, you will see that thousands of people have had this problem. Any definitive word from Google or Asus? You wish. They will never admit they made a mistake.
Click to expand...
Click to collapse
Yes I read about them but this is weird cause a reboot solved the problem.

Had this issue start yesterday. Running Sinless 3.2.2 on stock kernel. I've noticed it only start since installing Xposed but that could be coincidence. Reboot fixed it but woke up to it again today...
Sent from my Nexus 7 using xda app-developers app

mister2quick said:
Had this issue start yesterday. Running Sinless 3.2.2 on stock kernel. I've noticed it only start since installing Xposed but that could be coincidence. Reboot fixed it but woke up to it again today...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The one I had (before I sent it back to Google), would only do it after it had been started for a while. Reboot would make it go away for a while, but it always came back.
Not related to Xposed.