[Q] booty loops - EVO 4G General

So it seems that my phone might be reaching the end of line. Whenever the phone starts to get warm it starts boot looping.
A Few Examples:
Talk on the phone for 10-15 minutes, as soon as the screen comes on after i hang up, boot loops.
While streaming music for a while and turn the screen on and start using the browser, boot loops.
Tethering and doing anything with screen on, boot loops.
playing any game for a short time, boot loops.
hulu plus for a couple mins, boot loops.
In order to get it to stop I just pull the battery let it cool off for a couple minutes and let it boot up like normal. I have never had it reboot while the screen was off. It also happens in any rom/kernel combination I have used. It also happens with my stock battery and the Anker battery that I have. Any opinions? Tips?

Gm0n3y said:
So it seems that my phone might be reaching the end of line. Whenever the phone starts to get warm it starts boot looping.
It also happens in any rom/kernel combination I have used. It also happens with my stock battery and the Anker battery that I have. Any opinions? Tips?
Click to expand...
Click to collapse
What ROM/Kernel combinations you using for example?
What's your flashing process, you doing dirty or clean flashes? Also any apps recently d/l'd?
Any over/underclocking. Same for voltages?
How old are your batteries, both stock and anker?

Gm0n3y said:
So it seems that my phone might be reaching the end of line. Whenever the phone starts to get warm it starts boot looping.
A Few Examples:
Talk on the phone for 10-15 minutes, as soon as the screen comes on after i hang up, boot loops.
While streaming music for a while and turn the screen on and start using the browser, boot loops.
Tethering and doing anything with screen on, boot loops.
playing any game for a short time, boot loops.
hulu plus for a couple mins, boot loops.
In order to get it to stop I just pull the battery let it cool off for a couple minutes and let it boot up like normal. I have never had it reboot while the screen was off. It also happens in any rom/kernel combination I have used. It also happens with my stock battery and the Anker battery that I have. Any opinions? Tips?
Click to expand...
Click to collapse
I had the same problem.
The problem was CPU halting because of too low voltage.
Fixed it by overvoltaging at the max clock via Incredicontrol.

Oem battery is 2 years old. Anker is 2 months old. Currently running v8 of digital karma, underworld kernel with stock speeds and voltages. I have never messed with voltages on my phone but I was thinking the same thing about the cpu getting unstable and needing more juice. Just don't know how similar phone and pc cpus are...
Sent from my PC36100 using xda app-developers app

Gm0n3y said:
Oem battery is 2 years old. Anker is 2 months old. Currently running v8 of digital karma, underworld kernel with stock speeds and voltages. I have never messed with voltages on my phone but I was thinking the same thing about the cpu getting unstable and needing more juice. Just don't know how similar phone and pc cpus are...
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
If I'm not mistaken, Underworld is an undervolted kernel by default. My phone never responds well with Underworld kernels, despite which rom I try.
Try using a different kernel and see what happens. Of course, there IS the chance that your phone is reaching the end of its life. My phone is acting all wonky, too, but in much less severe annoyances.
______________________________
HTC Evo 4g

yeah underworld is undervolted. I upped the voltages to the stock setting outlined in the underworld thread.. Same problems. It happened on ics roms also with mason kernel and the prelude drew kernel. Contract with sprint is up in about 2 weeks ill just wait it out and stop tethering for coworkers, that should keep the heat down lol.

Might be am idea to check how many processes are running in the background too. I know Android is set to run better with ram being used but sometimes I think the system can get overloaded.
I forgot did you say the reboots happen with any scheduler, governor combo too?
An enviousOG

on ics roms it happened with wheatly and smartassv2, on sense smartassv2 and ondemand. I have also noticed that it never happens when the screen is off.. I stream music alot at work and say after 2-3 hours of streaming i turn on the screen BAM reboot. I pull the battery and place the phone and battery in front of a fan for 10-15 seconds and it boots up and runs like nothing had happened for another 2-3 hours or even the rest of the day.
edit: Also I made it reboot after 10 minutes of streaming extreme quality on spotify app. I was happy it played without skipping with the terrible 4g connection i get at work! LOL oh well 2 more weeks til upgrade.

Maybe try to increase the min values of both the cpu and if you can the voltages for the kernel, since it seems to be happening when trying to wake the phone. Might be an idea to try increasing all voltages as well

Gm0n3y said:
So it seems that my phone might be reaching the end of line. Whenever the phone starts to get warm it starts boot looping.
A Few Examples:
Talk on the phone for 10-15 minutes, as soon as the screen comes on after i hang up, boot loops.
While streaming music for a while and turn the screen on and start using the browser, boot loops.
Tethering and doing anything with screen on, boot loops.
playing any game for a short time, boot loops.
hulu plus for a couple mins, boot loops.
In order to get it to stop I just pull the battery let it cool off for a couple minutes and let it boot up like normal. I have never had it reboot while the screen was off. It also happens in any rom/kernel combination I have used. It also happens with my stock battery and the Anker battery that I have. Any opinions? Tips?
Click to expand...
Click to collapse
I would just wipe EVERYTHING. Make sure to do a nandroid backup, and wipe the crap out of that thing. Partition your SD card, triple wipe data, dalvik, and cache. Then re-flash your rom, or try another kernal.

Related

Simple Trick To Get 4-11ma In Standby

First, sorry for the new post on this, but I have not seen this mentioned. Didn't want it buried before it could help anyone.
I have used pretty much every android ROM out now, and for some strange reason they each have one constant.
ROMS which give 54-67ma on standby on first boot can be reset a couple of times until they reach the 4-11ma in standby point. Usually takes 1-3 resets.
Now, I'm not sure why this is all I know is it works. And yes, there is a huge amount of difference between 5+ and 50+ma.
I can surely confirm this
Hatefly said:
First, sorry for the new post on this, but I have not seen this mentioned. Didn't want it buried before it could help anyone.
I have used pretty much every android ROM out now, and for some strange reason they each have one constant.
ROMS which give 54-67ma on standby on first boot can be reset a couple of times until they reach the 4-11ma in standby point. Usually takes 1-3 resets.
Now, I'm not sure why this is all I know is it works. And yes, there is a huge amount of difference between 5+ and 50+ma.
Click to expand...
Click to collapse
This is most definitely true, might sound illogical or fake but I personally took battery logs when my drain was 58mA but could not find anything, I changed Kernels just to observe the same and I finally gave up but I accidentally had to reset my phone a few times as I forgot to put it on charge/freeze then after a few days I happened to see terrific battery improvement 5-8mA, I didn't know why but then I understood it was because of the resets..
Good to see I'm not going crazy. Like I said, I tried this with a bunch of different ROMS. All the same.
So if you are having bat problems. Try a few resets and see how that works for you before giving up on the ROM.
Oh, I might also mention I am not running any sort of set cpu app.
Check again
Hatefly said:
Good to see I'm not going crazy. Like I said, I tried this with a bunch of different ROMS. All the same.
So if you are having bat problems. Try a few resets and see how that works for you before giving up on the ROM.
Oh, I might also mention I am not running any sort of set cpu app.
Click to expand...
Click to collapse
Funny that just the both of us are populating this thread.. But yes I too do not use any Set CPU or Task Killers..
Currently on
Mattc Leo 1.8 with hastarins r7.6 with 5-7mA battery drain on Stand by (Wifi, GPS,Bluetooth off, data on(but disconnects sometimes))....
I can confirm this too.
Im a little new to Android on the HD2, running Mdeejay eVo Sense v. 2.3 rEVOlution 7.7 Hasteran at the moment.
Im finding the battery life on v2.3 less then on v.2.2 so I'll try a few resets & see if it improves, thanks.
Oh, is it really necessary to run SetCPU or a task killer?
Im forever closing tasks with task killer & the though of a task being auto closed when I turn the screen off is comforting, but is it best to just leave things to the kernal?
The most consistent way I have found to get 4-5ma on standby was to use exceller's android loader set autoboot android and 3 secs.
I can confirm this too.
I am trying dual boot (http://forum.xda-developers.com/showthread.php?t=723200) to boot into Android right away to see if that leads to more consistent standby battery drain. (this was mentioned on another thread.)
I have abandoned TaskKiller and AutoKiller, made no diff in battery drain for me.
I so still use SetCPU to slow the CPU when battery gets low.
Juno-First said:
Im a little new to Android on the HD2, running Mdeejay eVo Sense v. 2.3 rEVOlution 7.7 Hasteran at the moment.
Im finding the battery life on v2.3 less then on v.2.2 so I'll try a few resets & see if it improves, thanks.
Oh, is it really necessary to run SetCPU or a task killer?
Im forever closing tasks with task killer & the though of a task being auto closed when I turn the screen off is comforting, but is it best to just leave things to the kernal?
Click to expand...
Click to collapse
For better battery life, setCPU is a MUST! Creating different profiles to change the cpu clock is huge in conserving battery; especially, the the screen off profile.
Ditch ATK and download Watchdog instead.
even hastarin himself is using android without setcpu. with kernels 7.6, 7.7 I get same batt juice as with setcpu, BUT less stuttering in general, i.e. android runs more smoothly.
Honestly I have found that every ROM I have used set cpu was a detriment to battery life.
I'm still not 100% that even task killer is helpful in some cases. I think that on the other hand has to do more with how you use your phone and what apps than anything. Some people can prob get away with it.
SetCPU is pretty much pointless now with the latest kernels, only thing it's useful for is overclocking, but even without it I've not found anything that can't run. Even graphically intensive games like Reckless Racing run perfectly fine at stock CPU speeds.
I've just updated last night to ShubCraft 2.0 DropMode and I get 6ma in standby, my battery dropped 9 percent in 8 hours of standby while I slept, and after a full day of using my phone from about 9am to 6pm tonight (texting, calls, wifi use, 3G use, picture taking, playing a few games and listening to over an hour of music) my battery only just hit 50% at 6pm. This is without SetCPU.
What i've done is just swap out the micro sd card for another one. I had the stock 16gb and replaced it with an 8gb micro sd card and i'm getting fantastic results.
Without any type of task killers or Set Cpu, i'm constantly getting 3ma - 9ma stand by readings from Current Widget.
I also downloaded Juice Plotter from the Market ( what a fantastic app IMO ) and it tells you how much time you have left on your battery as well as a graph detailing the percentage of power battery has used.
I can go a day to a day and a half with out charging my phone. I am in complete Android Heaven.
NOTE: Keep in mind that when booting into Android, when you hit the Haret, make sure that the hard key light are on.
I also have the auto sync off to save battery as well.
To get the 4-11 mA, just make sure the keypad lights on the phone are on when booting haret.(pretty much, boot asap)
Sent from my HTC HD2 using XDA App
alantak said:
I can confirm this too.
I am trying dual boot (http://forum.xda-developers.com/showthread.php?t=723200) to boot into Android right away to see if that leads to more consistent standby battery drain. (this was mentioned on another thread.)
Click to expand...
Click to collapse
After several reboots this is holding true.
Before when I making sure the keypad lights were on before booting Android I would still occasionally get bad standby drain, so I think that is myth.
Exceller's auto boot app = no battery drain!!!
szfjcr said:
The most consistent way I have found to get 4-5ma on standby was to use exceller's android loader set autoboot android and 3 secs.
Click to expand...
Click to collapse
GOLD!!!! PURE GOLD!!! Been trying to preach this for days now! The battery drain is eliminated by booting Android before WM/Sense fully boots. Has nothing to do with keypad lights being on or off. Hence, use Exceller's auto boot app set to boot 3 secs and restart your phone and let it auto boot. Battery drain ELIMINATED!!!!!
secano said:
To get the 4-11 mA, just make sure the keypad lights on the phone are on when booting haret.(pretty much, boot asap)
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
See above comment.
anush.isaac said:
This is most definitely true, might sound illogical or fake but I personally took battery logs when my drain was 58mA but could not find anything, I changed Kernels just to observe the same and I finally gave up but I accidentally had to reset my phone a few times as I forgot to put it on charge/freeze then after a few days I happened to see terrific battery improvement 5-8mA, I didn't know why but then I understood it was because of the resets..
Click to expand...
Click to collapse
When you guys say do a few resets do you mean pull the battery or just use the off menu?
danielefeldt said:
When you guys say do a few resets do you mean pull the battery or just use the off menu?
Click to expand...
Click to collapse
Just do a hot reset if your android buid has that option, even better power off and and reboot from windows
I'm using bangster v1.5 with hasterin 7.7. I only get 2-3 ma standby.
Sent from my HTC HD2 using XDA App
For me the problem was the SD card. I formatted it with 4098 (or similar)block size, copied the Android build back over the top and bang from 115-170mA to 4-9mA on standby!!! WOW.

Epic shut down while charging? Missed alarm. Frozen rom1.1.0

So my epic is flashed with the frozen 1.1.0 rom with vision kernal and the keyboard type fix.
Yesterday I was playing with over clocking and it locked up. And a few hours later I had problems with force closes. I cleared cache and delvik cache and reloaded all three things again. She seemed to work fine. But when I missed my alarm clock for work it had shut down over night while charging? And After 3 short phone calls and 2 hours it dropped to 75% battery.
She seems to be working fine right now. I'm going to do a full charge and see what my battery looks like.
My big concern is the phone shutting of while charging.
Thanks,
Brandon
similar thing...
Mine spontaneously power cycles while sitting on the desk. Ive never had a missed alarm. But i think there is a buried bug somewhere that FC's google system and/or processes. Ive had to reflash mine and factory reset 3x. But to koNane's defense, it is YOU that chose to flash this! Remember the disclaimer? Sorry dude, don't stress, the ROM's keep getting better. You gotta admit! Its pretty [email protected] fast and clean. Download the app "Desk Clock". Ive never had any issues with it. Ever
I know thats the risk when doing roms. I never said I was blaming anyone.
I was just wondering if there was a known issue with it shutting off at all.
I could have been a fluke thing. I don't know.
I've had my phone shut down on me while charging with ACS SRF 1.1.0 as well. Genocide kernel 1.0. No over clock, no undervolt and minimum step set to 200.
It shuts down when charging. If I'm not charging I get spontaneous reboots every now and then.
I have never had the random reboot while unplugged. Just the 1 random shutoff while charging. So far it's been a great rom.
If you continue to have issues, Odin to full stock, format your SD card, redownload the ROM, re-CWM3, wipe 3x, reflash the ROM, then use the journal-enable zip in the development section. If you continue to have issues after that process, you most likely have a bad battery or charging circuit.
Thanks, I'm going to keep an eye on it. I have been charging it on and off all day today. No problems so far not a single force close from anything. If it does it again then I will do a clean install. I'm going to run some benchmark programs while it's charging to see what happens.
Well it looks like i'm going to Odin to full stock. She was locked up this morning this time. Front screen buttons were lit up and the blue full charge led was on.
And the blu led light and front screen buttons were still on after I unplugged it.
I had to pull the battery to reset.
If you get any more freezes or odd battery drain after the full stock, try the EB13 modem and either VisionKernel or Genocide.
Thanks, I know it's one of those trial and error things. But it's worth it.

[Q] AT&T S4 Battery Drain when Plugged and Charging extremely slow.

Hope someone can help me solve this issue.
The Setup
I recently went out of the country and before I left I unlocked my GS4 following from wonderhowto[dot]com
Arrived to my Carribean destination, bought a prepaid SIM, popped her in and everything worked great.
Problems started when I flew back into Miami. I removed my prepaid SIM and installed my old one, changed my APN name back
and rebooted the phone. Decided to plug it into my laptop (USB3.0) to get some extra juice before the next flight and I noticed that
the battery was actually going down and quite quickly too, about 1% every 3 minutes. The phone was also doing a lot of connecting and disconnecting from the laptop even though it was not being moved.
I use two batteries which I have an external charger for , so this didn't slow me down too much.
After a few days, I thought maybe by unlocking the phone I had left it in some "roaming" state where it was eating up battery looking for its signal, so I decided that I'd restore it to the nandroid backup ROM Manager created before I did the unlock procedure. OH NUGGETS!
Things got ugly , quick!. In the process of trying to restore got MD5 mismatch error, so I went back to 3 previous backups before all of which said either "MD5 mismatch" or unable to open .zip -None of them worked.
Thankfully I had saved a copy of the backup folder in clockworkmod to my PC and tried to load that, it started and then get to writing /data and said error writing data.
I rebooted. Bootloop.
After a few hours of attempts with KIES, and some well timed cold beer deliveries from my wife, I finally got the phone back to stock version.
Rooted it again, motochopper, And loaded GoldenEye Rom v 8.0 . Still slow to little or no charging.
Loaded PACMAN and noticed something that should be mentioned.
Pacman rom has its own little battery widget that sits in the top tray and shows the %. It glows green from bottom to top to show that it is charging. I noticed on every couple of cycles, the battery meter would flash red for a quick second before turning green and sweeping up.????
Went back to a backup of GoldenEye8.
The current status
The phone is currently plugged in to the stock charger (2A) and stock cable. It has charged up only about 3% in 20 minutes time. I have it in battery saving mode with wifi on , and EVERYTHING else turned off.
Battery info says:
Temp 87.3 F
Voltage 4033mV
Plugged True
Charging
Li-ion
Health:Good
Charge Type : AC
Battery use shows 62% of battery use coming from SCREEN (Yes I have auto-brightness set, and NO live wallpaper)
Anyone have some good input?
Maybe its a bad cord? Or bad USB port/connection on the phone it self...
Sent from my SGH-I337 using Tapatalk 4
62% screen usage is normal, I sometimes see over 70% with my brightness all the way up.
Make sure apps aren't keeping it from going idle and staying active.
Battery temp. seems a bit high. General causes of that are a faulty cable.
Download greenify and hibernate any apps that may be running unnoticeably in the background.
If your kernel allows fast charging (disables access to phone storage while fast charging is on) enable it while charging if you're not using the phone.
Play with CPU and GPU governors in your kernel to save battery life. I.E: I put my CPU governor on "powersave" while idle and not using the phone for anything extensive.
Sent from my SGH-I337 using XDA Premium HD app
mg2195 said:
Maybe its a bad cord? Or bad USB port/connection on the phone it self...
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Tried two other cords,but they just made it worse. They actually caused it to look like its charging but the battery level was going down.
Your second suggestion is probably right, but i'd like to exhaust my options first before having to restore and send to creator. I do find that with the stock cable and no external case on it stays plugged in well and doesn't make any "interrupted connection" noises.
With stock charger and cable and minimal functions running its charging about 1% every 4 minutes. ( Approx 6.5 hrs to full charge )
I feel like the hardware must be working in order to do that, and that the software is putting some kind of excessive strain on it. Possibly?
The battery use still shows, screen as the major contributor at 61% , so I switched from a really high resolution static background to a low res one. ( results to follow)
Downloading WanamLite now and going to try that out, also going to try performing the unlock procedure I did in reverse order and see what that does. Keep you posted. Open to suggestions.
Br4nd3n said:
62% screen usage is normal, I sometimes see over 70% with my brightness all the way up.
Make sure apps aren't keeping it from going idle and staying active.
Battery temp. seems a bit high. General causes of that are a faulty cable.
Download greenify and hibernate any apps that may be running unnoticeably in the background.
If your kernel allows fast charging (disables access to phone storage while fast charging is on) enable it while charging if you're not using the phone.
Play with CPU and GPU governors in your kernel to save battery life. I.E: I put my CPU governor on "powersave" while idle and not using the phone for anything extensive.
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the advise, I'm running greenify and its really only showing facebook and my sms app, I hibernated facebook anyways just to test it, but I know out of the box , on a car adapter this thing was charging 1%/min , maybe I have a bad ROM/Kernel mix?
prodigaltaurus said:
maybe I have a bad ROM/Kernel mix?
Click to expand...
Click to collapse
Doubt it, but maybe you can try going from touchwiz to aosp. Very much more lightweight, though you'll lose some s4 features. If it is faulty hardware/battery I'd just save yourself the trouble and swap it for a new one; or try another battery. I guess you can try doing a compete wipe and flashing a fresh ROM with a kernel you know will definitely run smooth with it.
Sent from my SGH-I337 using XDA Premium HD app
Br4nd3n said:
Doubt it, but maybe you can try going from touchwiz to aosp. Very much more lightweight, though you'll lose some s4 features. If it is faulty hardware/battery I'd just save yourself the trouble and swap it for a new one; or try another battery. I guess you can try doing a compete wipe and flashing a fresh ROM with a kernel you know will definitely run smooth with it.
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
Already tried the second battery, no luck. Any suggestion on the rom/kernel combo?
I use task650 with kt's kernel and it's excellent. Though it's all opinion, there is many great combinations. Some ROMs come packaged with their own kernel or a custom one.
Sent from my SGH-I337 using XDA Premium HD app
IMO: those temps are pretty normal.
Why you don't try a bone stock rom and see how it respond for a few hours, if the stock rom behaves the same, probably you will need to send it for warranty.

[Q] My Nexus did something strange... is it of any concern

I have been using TWRP and Beanstalk ROM for some time, and the current version installed has been there about two weeks with Hellscore kernel, never had any issues or problems, its been pretty flawless and I have been very happy with it. I also run a tool called AutoReboot, which automatically reboots the phone daily at 3:00am for a few months now. I never really had trouble with my phone previously, it just seemed like a way to keep things cleaned out on a regular basis.
So about 1am I threw my Nexus on the charger with about 30% battery and went to sleep, this morning I get up and grab my phone and am treated to the screen stuck on, the battery at 6%, and the nice Google logo with a open padlock at the bottom of the screen... Holding the power button for 10 seconds or so powered the device off, and then I was able to power up and boot normally and within a few hours the battery was full. Tried a manual reboot and everything went fine.
First question... I am wondering is if this is just a fluke and it can be ignored, or is it likely the beginning signs that it's time to start looking for a new device? The phone is about 15 months old and never given me any problems at all.
Second question... Is rebooting daily really needed, would doing it automatically weekly or so be better, or am I better off just to manually reboot when something acts up or feels "off"?
Personally, I'd just randomly reboot it when you need to and not use some app to do it. Of course I mess with my phone a lot so reboot frequently, lol
Sent from my Nexus 5 using XDA Free mobile app

VS995 random reboots

So, i had this random rebooting issue on stock oreo, after installing custom roms it went away for a while but now the issue is back again, My phone will randomly reboot as if my battery has just died(while plugged in or fully charged).. I can be playing games or just scrolling through my home screen and it will reboot without warning, then starts up like nothing happened.. any ideas on how to fix this?
texas7412 said:
So, i had this random rebooting issue on stock oreo, after installing custom roms it went away for a while but now the issue is back again, My phone will randomly reboot as if my battery has just died(while plugged in or fully charged).. I can be playing games or just scrolling through my home screen and it will reboot without warning, then starts up like nothing happened.. any ideas on how to fix this?
Click to expand...
Click to collapse
Hey Texas, I'm not sure how old your battery is. But if your battery is on the fritz it could be losing voltage in your phone will shut down. I think you'll normally get a bad battery warning but I'm not positive. I'm using Alpha Oreo 1.3.1 with MK 2000 version 2.2 kernel. And have not had any random reboot problems. On the contrary. It has been extremely stable and I'm getting extremely good battery life especially with greenify. Normally 24 to 27 hours on a full charge. With anywhere from 3 1/2 to 6 hours of screen time.

Categories

Resources