Related
Hiya, Yesterday I loaded Damage Control v2.08.1 and it's been running pretty smooth. Just in the past few minutes I've noticed the phone getting hot around the battery. I've never felt this phone get hot before. A few minutes later it cut off. I had to press the power button to get it to turn back on. Everything seems fairly normal now and it doesn't really feel hot anymore. Has anyone else experienced anything like this? Should I try a different ROM?
I think this is a random thing..ive had it happen a few times on diff roms etc..
-------------------------------------
Sent via the XDA Tapatalk App
The ROM is fine I use it.
maybe you should take it to sprint and say it is getting really hot. They will trade it in for a new one. In less your over clocking it then you should know why it is getting hot. But I believe it is a hardware error.
Thanks for the input. The main reason I posted is because I used stock 1.5 for 5 months before loading a custom ROM and never once felt the phone get hot.
As long as it's a common thing I'm alright using it that way.
I ran into a similar thing when signal was low. A workaround is to turn off wireless triangulation in the location menu. Also turning off "always on" helps a lot, I forget where this setting is. I was hitting 43c a day before these changes, now barely get over 30.
-------------------------------------
Sent via the XDA Tapatalk App
lineman78 said:
I ran into a similar thing when signal was low. A workaround is to turn off wireless triangulation in the location menu. Also turning off "always on" helps a lot, I forget where this setting is. I was hitting 43c a day before these changes, now barely get over 30.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
the always on setting is in location (it turns GPS off)
Line got really hot a couple weeks ago. At first I could not figure out why, but after looking at everything I realized it said I was roaming. O was in a location I was always at and never had s problem before. It said I had been roaming for 4 hours. Restarted the phone and the problem was fixed.
I know there might be a dozen threads about this, but its all gobbledygook and nobody seems to have a straight answer.
I just want to ask: What can we possibly do about Froyo draining our battery? Task manager auto-killers aren't working right now it seems.
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Task Managers??? Are you kidding me? My battery life has doubled since Froyo because I dont use task managers or auto killers. Use Fresh Rom, with set cpu with perflock off, change the screen off to 245/245. Most important part is condition your battery...Trust me, i thought it was stupid as well, but it works.
drmacinyasha said:
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Click to expand...
Click to collapse
haha thats funny and true so i like it. i am running froyo official and have noticed an increase in battery. but hey when you get near your computer plug your phone in when you get in your car plug your phone in.
Froyo Killed Your Parents??
Sorry To Hear About Your Parents
R.I.P.
theres not much else u can do..just wait for a fix
I have ota and its the worst batterie ever with out doing nothing not even a phone call it died under an hour i only have gps enable had 3g off 4g to app all close no auto killer
Htc Evil Phone
I have the same problem. I read reports that Facebook 1.3 will not release the partial wake lock. I took FB 1.3 off and the problem persisted.
Here is how to check if you have a problem with your partial wake lock:
goto settings > about phone > battery and compare the uptime and awake time. If they are the same or very very close you have a wake lock problem. A wake lock allows an app to prevent your phone from going to sleep, even if the screen is off. If these times match then an app is creating a wake lock and not releasing it, and therefore your phone never sleeps.
As I said removing FB 1.3 did not solve the problem, but I was able to prove it is a wake lock as using Advanced Task Killer to kill 21 tasks allowed my phone to actually sleep, as indicated by a corresponding difference in the two times. So now that I know this is an app doing it, I will try to narrow it down and figure out which and report back.
OK I just found it. It appears the LED Light widget also causes a partial wake lock. To alleviate you don't need to uninstall it, just remove the widget.
Which led light? From market or the one with 2.2?
Borg1982 said:
Which led light? From market or the one with 2.2?
Click to expand...
Click to collapse
The new "flashlight" app is not a widget...It's actually called LED Light, by picolyl.
I don't have a problem, for me is little better!!!! just buy a new battery that solve your problem
drmacinyasha said:
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Click to expand...
Click to collapse
Problem NOT solved. Or maybe 15 extra minutes.
Or don't use it at all, you'll save plenty of battery
Check to make sure that your Google Talk app is not automatically signing in. Go to apps - talk - settings. This is a typical battery drainer
totally forgot about google talk. have flashed a few ROMs back and forth, and now running a stock rooted ROM, I forgot to shut this one off...
use a custom rom, something without sense and try not to have a f***ton of widgets. im running cyanogen nightly and i get about 10 hours before i hit 20%-30% thats when i quit doing stuff and start trying to make the battery last. screen eats most of the battery so turn the brightness down.
my average 10 hours is 75-125 txts 30 + or - min of talk time and 3+ hours of internet (facebook)
oh, and about your parents... they are gone, there isnt an app or a rom that can fix that.
Indeed, the title of this thread is goofy. Froyo has literally killed my parents....... and has done a bad job for my battery life on my phone. Haha!
I guess an apostrophe would not have hurt after the word "parents" eh?
Doing a factory reset will fix your problem... I had the same problem when I updated.
Sent from my PC36100 using XDA App
opie2l said:
Doing a factory reset will fix your problem... I had the same problem when I updated.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm having similar issues with my OMJ 2.2 froyo rom. poor battery life, plus it seems laggy and unresponsive. i was much happier with OMJ's 2.1 rom
Anyone else having this problem. So far it's happened twice on me. I click the power button to lock the screen and then I come back to it a minute later and it's off. I try to turn it back on but it doesn't unless I remove and replace the battery.
I had this problem, even while running stock everything. The phone is very likely defective. I had to exchange it at the Sprint store.
I probably will do that if it happens more
Sent from my SPH-D700 using XDA App
Are you using SetCPU or anything like that? That happened to me one morning (because I set the minimum clock frequency too low: 100 MHz) and it wouldn't come back on save for a battery pull. I think the minimum safe frequency to prevent that from happening is around 400 MHz... but then there's no reason to have setCPU installed in the first place.
If that's not your case, then it's probably a defective phone, go and exchange it if that happens again.
Maybe related, maybe unrelated, but mine did the same thing after installing SetCPU and setting the profile to "OnDemand".
After actually reading the SetCPU info, it says on the Galaxy S phones the "OnDemand" will cause issues and you should use the "Conservative" setting to have it auto-scale the CPU to usage demand.
Swapped mine to that, and no issues since.
I've had this happen on occasion with an unresponsive program that is hogging the CPU. Mashing the power button repeatedly has little effect, so I just give it a few seconds, and try again. I don't think it has ever taken longer than 30 seconds to respond. Apps that can trigger this behavior include the AP News app, which is terribly-coded and even less responsive. Don't fault the device - it's just unresponsive software. As capable as the CPU and OS are, it's still possible to get a hangup like that.
So, I just went and checked my phone's battery usage and realized it has been awake all day. I'm not sure what's causing this, nor how to fix it. I tried glancing through the forums a bit but I'm pretty busy at the moment and didn't see anything, so I apologize for probably repeating a topic. Oh, I'm running MikG 3.0 with the Less Lionfish 1.4 kernel, Smartass governor and SIO I/O scheduler. Thanks for any help.
sounds like maybe a rogue app. did you restore any apps through Titanium Backup? did you recently download any new apps? How long have you been noticing it? do you have any data syncing in the backround that may be hung up?
app
I think alaman68 is correct. If you reboot your phone, does it happen again? If yes, check your running apps for rogue service. If not, you'll just need to to do trial and error.
Today was the first day I noticed it, and I check my battery usage rather often. I am constantly installing and uninstalling apps, but I don't have anything currently installed that I didn't have before when my phone was normal. I'll reboot my phone and see if it continues.
Brilliancy said:
Today was the first day I noticed it, and I check my battery usage rather often. I am constantly installing and uninstalling apps, but I don't have anything currently installed that I didn't have before when my phone was normal. I'll reboot my phone and see if it continues.
Click to expand...
Click to collapse
wipe the cache and delvik when you reboot
I rebooted it without wiping either cache and it has stopped for now. Should I do that anyways? Thanks for the help, by the way.
In terminal emulator, type dumpsys power.
It'll shoe you if any of your system level apps or sensors are causing it
Sent from my PC36100 using xda premium
Im having the same problem somehow. I thought it might b android Os that was high but that doesnt come up on battery use...
Cm7
Check to see if you have FriendStream removed, I know MikG will allow this through the tweaks. If it's not showing up in your list of apps, it'll lead to a sync problem that will literally keep your phone on constantly. The only way to fix is to wipe and flash again, then don't remove it. You can try to push it back in through ADB, but that didn't work on my phone. I reflashed, and now I'm consistently getting 19 hours with no tweaks applied. Just a heads up. Without FriendStream, you may see the sync icon in your top bar all the time.
I don't have the sync icon or anything, just the ones on the pic but still awake?
If i do clean flash then nandroid restore, will the problem fine back?
What else can b keeping it awake
I don't have friendstrm or any of those Facebook related apps
Nothing comes up on battery use, its simply always awake
cwbeasley said:
Check to see if you have FriendStream removed, I know MikG will allow this through the tweaks. If it's not showing up in your list of apps, it'll lead to a sync problem that will literally keep your phone on constantly. The only way to fix is to wipe and flash again, then don't remove it. You can try to push it back in through ADB, but that didn't work on my phone. I reflashed, and now I'm consistently getting 19 hours with no tweaks applied. Just a heads up. Without FriendStream, you may see the sync icon in your top bar all the time.
Click to expand...
Click to collapse
Will this happen even if you shut autosync off? One of the first things I do when flash a rom is remove friendstream, I never thought of a potential problem though.
Sent from my PC36100 using Tapatalk 2 Beta-4
I don't have any auto sync, and Google apps bakup is off
This will happen with auto sync off.
Sent from my SGH-T989 using xda premium
Download the 'better battery stats' application. It will show you what is causing the wake lock
Sent from my PC36100 using XDA
OK I d.l the app. But I'm having trouble finding what's keeping it on.
What option should I click on.
The first screen does say my phone has been awake for one extra minute compared to the screen on. But I can't find the option where it says what the app is.
Hellp
oscar996 said:
OK I d.l the app. But I'm having trouble finding what's keeping it on.
What option should I click on.
The first screen does say my phone has been awake for one extra minute compared to the screen on. But I can't find the option where it says what the app is.
Hellp
Click to expand...
Click to collapse
When you open the app the first line on top says other. Change it to partial wakelocks. Before checking your wakelocks unplug your phone and don't use it for a few hours.
Sent from my lair.
OK thanks. It ended up being a `audioOut`1which I have no idea what they r since they r not apps. Check them out.
I'm on aokp evo
Hey guys,
Sorry if this has been asked before, I did a search and didn't see anything.
A few weeks ago I noticed that my 2013 Flo was randomly powering down. I have noticed that this only occurs when the screen is shut down and it is allowed to go into deepsleep or hibernation as it will only occur after the screen has been off a few minutes. There is sometimes a series of four beeps after which the device powers down. If I turn on the screen after the beeps it comes up with the shutting down dialog as if I manually shut it down. I have tired to use various log recorders but all of them keep the system in wakelock and thus prevent this from happening.
I was wondering if anyone else has been having this issue, or know of any methods to debug this, and if it is a hardware issue thus meaning I should return my device or not.
Also: I am running PA 3.98 rather then stock but do not believe it to be caused by the rom.
There are some threads where people mention this happening because the "keep wi-fi on during sleep" setting not being checked as the root cause.
What's yours set to?
cowabunga said:
There are some threads where people mention this happening because the "keep wi-fi on during sleep" setting not being checked as the root cause.
What's yours set to?
Click to expand...
Click to collapse
It was set to never. Just put it on always. I'll see if that fixes it. Thanks
This just happened again so I dont think that fixed it.
Sorry for bumping this but it still is happening and I think I have tried everything. Does anyone know a way to fix this or should I try and swap my device for a new one and hope that works?
Swap it IMO
Sent from my HTC Sensation using xda app-developers app