Constant reboots... - Samsung Galaxy Nexus

I've been having this problem for some time now and let me tell you, it is so god damn annoying.
For some reason at least once a day the phone just constantly reboots by itself in a loop until the battery is pulled out and put back in, then the next day it just does the same old thing.
I know for a fact it is not kernel related because I've tried Franco, AK, and Lean Kernel, all have the same issue.
I've also tried stock rom and Xylon rom.
I turned off SR and the problem is still there, no underclocking no undervolting, completely stock rom/kernel.
Does anyone know how I can fix this? Is this app related?
Any help would be appreciated.
Thanks

I can see how that would be very irritating. There are a lot of possibilities for the cause, but I think the first thing I would do is use Trickster app or equivalent to set my cpu frequency down to about 1000 MHz and see if that makes it stop rebooting for a few days. If so, then you might have a device that can't tolerate a normal level of heat. In that case I'd try to get it replaced, or just live with a lower maximum frequency. Or you could try turning up the voltage for 1200 MHz a little, maybe 10 mV, and see if that makes it stop.
If neither of those worked, I would start looking for a rogue app or leftover script from a previous installation. Try wiping /system as well as cache, dalvik, and factory reset next time you install a ROM.

I guess I figured out the problem.
This only happens if I restart the phone while it is connected to the charger.
Sent from my Galaxy Nexus using Tapatalk 2

Related

Sleep of death

Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.
Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium
I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.
Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App
Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.
Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.
did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.
I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.
how often has the sod been happening? I think i got it yesterday, but not sure.
Do you use setcpu?
Sent from my SPH-D710 using Tapatalk
This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.

Data Disconnects after sleep?

I have an issue with any custom ROM's I've tried, when the phone sleeps my cell radio turns off and I cant receive phone calls, sms's and the like.. The service comes back after a minute of having the screen on, but its a real hassle. I dont have this issue with either of the stock roms, both 4.0.1 and 4.0.2 but anything custom causes me issues.. I wipe data, cache and dalvik and take care not to install any apps and the issue still arises.. I noticed there are a few other people having similar issues, but unlike them I do not have to reboot to get my cell radio working and its not just data, I have also tried the gamut of radio's but I am hesitant to flash radios constantly since my understanding is flashing them has a greater risk to brick your phone should something happen. Does anyone know anything I could try? I dont understand how custom roms all do this but a stock one wont..
set minimum CPU frequency to 700 mhz.
also try other radios (UGLA4 works very well)... flashing a radio won't brick your phone as long as its for your phone.. which in this case, just dont flash I515 radios (verizon)
what rom? kernel?
yannisthegreek has a thread about this; not uncommon by the sounds of it.
Purely conjecture on my part, but I think it's a power issue, i.e. your phone isn't supplying the radio with enough power to kick start it from sleep. Basing this on the fact that a particular kernel (Fugo IIRC?) or upping your min freq to 700 seems to fix the issue. I've yet to experience this however.
I'm going to try setting it to 700mhz right now, I've flashed CM9, Modaco, Codename Android, Revolution, used the Kernel that was provided with those ROMS and Franco's and Trinity, I have also tried every radio as well with the same results.. it does make sense the way mudferret explained it and also explains why it will start up after my phones out of sleep mode and running faster, the weird thing is that this just happened one day, my phone was fine running a custom rom and Franco's kernel and then one day I notice that I had calls going right to voice mail..
So glad I found this thread. I've been dealing with the same issue. People tell me when they try to call they get a fast busy signal. If I wake my phone for about a minute everything works again. I am going to try Fugo IIRC? kernel and see what that does.
Looks like setting my kernel to 700mhz did the trick.. using Franco Kernel and Modaco custom rom, this was driving me nuts.. I'm a happy camper now, thanks for the help guys..
flindil said:
Looks like setting my kernel to 700mhz did the trick.. using Franco Kernel and Modaco custom rom, this was driving me nuts.. I'm a happy camper now, thanks for the help guys..
Click to expand...
Click to collapse
Glad to see it up and running. I never had this problem but I always had my minimum frequency set to 700 MHz because I think I heard franco say something about it helps battery blah blah blah... it was a while back but I don't remember the full details
Yeah, I read that he said the difference on battery use was negligible.. that could have been why custom ROMS and kernels were working for me previously.
Sent from my Galaxy Nexus using xda premium
I don't believe that setting min freq to 700mhz solves anything that relates to ril.
If you were talking about voltages, that would be another story...
bk201doesntexist said:
I don't believe that setting min freq to 700mhz solves anything that relates to ril.
If you were talking about voltages, that would be another story...
Click to expand...
Click to collapse
What's the voltage differential between the 350 and 700 slots, if any?
Edit: I ask because I can't see my voltages on my current kernel
Have same problem post 4.0.4 update
I started seeing this too after a manual 4.0.4 update to my GSM Nexus. The phone is still stock (and was prior to the flash) with ClockWorkMod the only thing added. Still troubleshooting.
----------------------------------------------------
UPDATE: Noticed that this does not happen while phone is being charged. I've tried playing around with a CPU speed program, but I haven't yet figured out if the settings are taking properly.

[Q] Sleep mode/ screen off problems

Okay does any one have this same problem or am i just doing something wrong?
Every time i let my kindle sit with the screen off after about 30 minutes or so, and I assume it keeps going and getting stuck in sleep mode but the only way for me to get it turned back on is to do the whole power button for 20 seconds and then reboot. Am I not being patient enough with it or is there some trick to getting the screen back on that i haven't found yet? Because I've tried multiple different things and there isn't a disable sleep mode option in my rom just the option to extend the time, even though its pretty much useless. But can anyone help me with this?
what rom are you on?
Right now I'm on Hell Fire 1.1 but last week i was running CM9 Reloaded and it did the same exact thing.
I was going to give a long speech about how people need to READ before installing any new roms but considering the Hellfire thread doesn't list what works and what doesn't, I guess it's not entirely your fault
It's called "sleep of death" (SOD). Some ICS roms have problems with it and some don't. The same could be said about certain individual devices. You could boost your minimum CPU usage to 600Mhz or more, or try a different rom. Though, it should be noted that changing your CPU settings will affect battery life.
okay that makes sense i had no idea that most of the new roms have problems with it. but I'll probably try to up the min cpu usage i suppose the difference between 600 MHz and 300 MHz isn't going to be a true killer for the amount i use it but which rom or roms would you recommend? That don't have this problem I'd really like to try barebones but every time i try to flash it my Kindle goes crazy so i gave up on trying with it.

galaxy nexus crash randomly, battery remove is needed.

my galaxy nexus has a problem since a few months.. the phone get stuck and the screen go weird (sometimes totally black, or "noisy"), nothing works, not even the power button, i have to remove the battery to make it work again.
this has happened most of the times while downloading and installing something from goole play or while i get emails notifications and im doing something else in the phone. it does not reboot, like i said, just totally dies till i remove the battery and turn it on again.
now i updated to stock jellybean and i had the same issue. is not all the time like i said, just happens once in a while.. but i do not think is normal..
could it be a hardware issue?? i've been thinking that maybe it could be that the internal storage has some demaged sector and when android tries to write or read from that area make the phone crash.
is there any app for android to find and isolate demaged sectors??? what else could it be??
perhaps it's a hardware issue, probably with your cpu not being able to handle the load
rhed said:
perhaps it's a hardware issue, probably with your cpu not being able to handle the load
Click to expand...
Click to collapse
it seems, it is a common issue called "sleep of death", i wanna think it is a software issue, because users of the nexus 7 are experiencing this too..
but i cant find a solution for this.. everyone seems to know this issue but i have not find a solution..
it is not an app, im sure because this has happened in stock, after a factory reset without any app installed.. i've tried wipe cache also..
in other forum a guy said that could be that the device cant support low voltages and when the cpu go to its minimum frequency it shuts down.. that sounds kind of logical to me, because when the phone crash the battery usage is in its minimum (saw it in the battery statistics)..
i wanna try uncreasing the voltage a little but i cant do it in stock.. if anyone found the solution to this weird and annoying issue please help!!!
Use a uv-capable kernel, disable smartreflex, increase voltages for core, mpu and iva by 10 mV.

Little cores running at 1440 all the time

Hey guys, need some help. I have an AT&T H810 rooted 10o. My little cores seem to be running full out at 1440mhz even though my governor is set to Interactive. This is causing it to heat up incredible, to 70c+, and is draining the battery quickly. It seems to have only started occurring in the last few days! I can run it in powersave governor which fixes it to 384mhz, and it fixes the problem, but I don't understand why it is running at full speed under interactive now. The big cores do NOT have this problem AT ALL.
I've removed any apps I installed during that time, cleared my phones cache, cleared the memory, I have tried running it in airplane mode, I've looked into what apps were running and it seems to be very few. Turned location off. I've tried freezing the play services because I have been getting a very intermittent force close. I have also tried to disable all xposed modules, and used avg to scan for any malware. Possibly init.d? Possibly the new xposed v79? I'm at a loss as to what is causing this!
Does anyone have any other ideas as to what could be happening?
There's always the good old factory reset if everything else fails.
Just asking the obvious but there is no offending wakelocks or anything that sticks out in the battery usage stats?
spartan268 said:
There's always the good old factory reset if everything else fails.
Just asking the obvious but there is no offending wakelocks or anything that sticks out in the battery usage stats?
Click to expand...
Click to collapse
Battery usage Android OS is highest at 33, followed by screen at 16%.
Wakelocks, I seem to have them under control with amplify, and I don't see any new ones.
Question about factory reset, I am not near a pc for the next few days, will it cause any problems with xposed or my rooted system image, and basically what can I expect with it? I came from a M8 where with custom recovery I was pretty fearless with being to wipe and refresh, can't do that here.
Noticed that disabling 2 of the little cores with kernel auditor really helps with the heat buildup of the phone with not much slowdown
elementalfusion said:
Noticed that disabling 2 of the little cores with kernel auditor really helps with the heat buildup of the phone with not much slowdown
Click to expand...
Click to collapse
Doesn't solve why it's running at full speed, but I'll keep that in mind.
question about factory reset, I am not near a pc for the next few days, will it cause any problems with xposed or my rooted system image, and basically what can I expect with it? I came from a M8 where with custom recovery I was pretty fearless with being to wipe and refresh, can't do that here.
Personally I never done a factory reset myself yet so i cannot comment.
For the most part it does look like you have something to work with seeing Android OS is taking up the most battery. The hard part is tracking down which process. I'm not the best at this so maybe someone else can chime in. Try taking a look at your currently running processes and see if there's anything odd
Well, after a few factory resets which did not affect xposed, I was able to resolve it to where the cores now return to 384mhz idle. It was something that was installed, and it took 3 or 4 resets after restoring my app backups, and I'm still not sure which app was the culprit. I'm possibly wondering if it was the Amplify module
Sorry for bumping this. I just suffered from this problem and it seems for me it was antutu. For some reasons it was running the background keeping the 4 small cores at 1,2-1,4 cuz constantly. I stopped it and now it's back to normal. Just wondering why it started itself in the first place.
Sent from my LG-H815 using XDA-Developers mobile app

Categories

Resources