Related
I recently went from the original leaked froyo rom to super clean 2.9. Ever since I flashed that rom I have had the sleep of death. When I say that my phone has the sleep of death that is Everytime my phone goes to sleep. I have tried many things...I have tried using odin and flashing back to the original and them putting 2.9 and even going to 2.9.1. I have also went as far as not even installing titanium period. I eventually gave up and tried installing DarkRevenge v3 and am having the same results. I guess my only option is to go back to stock non-froyo. I have read that it is a froyo issue, but can't understand why I never had a problem with the original froyo leak. I honestly believe that I had the same kernel every time. I believe that I first had the froyo leak with DL09 then upgraded to the EB01. Let me add that each upgrade I never used voodoo, nor have I ever used voodoo...to my knowledge. I also went into wifi settings and changed the sleep policy to the plugged in option in hopes of saving battery life and thought it might be what was causing the issue, but it is not after switching back and having the same results.
If anybody has any ideas it would greatly be appreciated. I have tried wiping everything and flashing all roms according to instructions to a "T". If my SOD problem with just once or twice a day it would be tolerable, but every time has got to be a pain, especially since I have to take the phone out of the case and do a battery pull. Of course my battery life sucks, but that is acceptable. I am hoping that someone can help me with this issue before I go back to stock. I really like SC 2.9 and DarkRevenge v3 these roms are sooooo awesome. There again I am scared when I go back to stock I will still get the SOD...I hope not.
Thanks,
Leroy \oo/
Having the EXACT same issue ... any success?
I had to go back to a non froyo rom. I went with dl05 super dark with voodoo5 kernel. It runs great with no sod and awsome battery life with no froyo though. I might do some experimenting this weekend and I will let you know if I find any solutions.
Sent from my SCH-I500 using Tapatalk
I installed the Nameless v4 yesterday and v4.1 today.
On the Froyo roms my battery pull on idol was -2 to -10ma [i use battery monitor widget]
Now on the GB i am getting -100 to -275.
Is anyone else experiencing this kind of draw?
[I do understand that the GB is a wip]
I can't speak on the new build, but I was running the 4.0 build and my battery ran down so quickly that I thought I left my gps running with a connection. I also was having quite a lot of issues with the rom, so I thought it was a fluke. I'm on 4.1 and it's been running much better, so hopefully the battery drain isn't as great.
Definitely sounds like you've got a runaway process or wake-lock occurring somewhere. Have a look around the processes and see if something's keeping the CPU running hard. Also run a dumpsys power from adb and see if something's keeping it from sleeping.
Im getting quite the opposite here. It's been almost a day and after moderate use I have a little over 50%. It's amazing because I would be getting half of that on a full charge in froyo.
Looks like it may have been the Widget itself.
But i am not sure, if i closed the running application of Battery Monitor it dropped down to -1 or -2 but then ten mins later its back up to -300.
The other possibility is when i kill the app the widget gets no information and defaults to a low number.
Thank you everyone for your input. I will keep on testing to find my battery killer.
I also may try uninstalling K-9 mail and reverting to the stock Mail client
It being on stock kernel and a lot of debugging features being enabled will do that to your battery.
Sent from my SCH-I500 using XDA App
A lot of people have reported poor battery life with K-9, FWIW, though the K-9 devs say there isn't an issue. I haven't used it myself so I can't really say... you could try this though:
https://market.android.com/details?id=org.r3pek.k9datakiller&feature=also_installed
4.1 drained my battery from 100% to 10% in about 4 hours today. But then I plugged in and rebooted and I had 40%, so I would imagine a battery stats wipe is needed on my phone.
My home button does not work as well, so I am going to re-install again and see if it fixes these issues.
Anyone else had the home button issue?
Edit: The re install fix the home button/lock screen issue. Will report back on the battery tomorrow.
Weird, my battery is AMAZING on Nameless. After 11 hours with using Screeble, with moderate use, I'm at 50%.
xwhofarted said:
I installed the Nameless v4 yesterday and v4.1 today.
On the Froyo roms my battery pull on idol was -2 to -10ma [i use battery monitor widget]
Now on the GB i am getting -100 to -275.
Is anyone else experiencing this kind of draw?
[I do understand that the GB is a wip]
Click to expand...
Click to collapse
I tried Nameless 4.0 and it used less than 20% during the first 6 hours.
Whenever I flash a new rom, it uses more power at first and less and less as you use the phone. Some people insist that you do not have to kill the apps especially on Gingerbread.
zas311 said:
Some people insist that you do not have to kill the apps especially on Gingerbread.
Click to expand...
Click to collapse
Assuming you're talking about task killers, "some people" = Google. With the exception of apps like Watchdog (which just notifies you of apps using excessive CPU, like >50%), task killers hurt more than they help -- they're all effectively scams.
Google's serious techy explanation:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.
An excellent, understandable article from Lifehacker:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
I thought I read somewhere (either the EC09 Leak thread on the Nameless v4 thread) that auto-rotate is causing 50% cpu for this EC09 leak, would that have something to do with battery drain?
http://forum.xda-developers.com/showthread.php?t=1131213&page=15
Thanks
saw the one about auto rotate and turned it off, then i was in the -50 to -100
But that is still bad coming from froyo`s -2 to -10
So i went back to Com Rom and will be awaiting the best Devs on XDA to crack the Leak and make some fantastic ROMS, just like they did with Froyo!
Keep up the good work!
xwhofarted said:
saw the one about auto rotate and turned it off, then i was in the -50 to -100
But that is still bad coming from froyo`s -2 to -10
So i went back to Com Rom and will be awaiting the best Devs on XDA to crack the Leak and make some fantastic ROMS, just like they did with Froyo!
Keep up the good work!
Click to expand...
Click to collapse
I suggest disabling auto rotate, rebooting, and then never turning auto rotate on again. (even toggling on/off can get the events/0 process stuck at high cpu usage) Once I did this, the full bloated GB leak is spanking Froyo battery life.
This more than makes up for the poor contacts scrolling for this guy.
Also full bloated GB leak appears to be much safer for you SD card than other versions of the leak.
Scrappy1 said:
I suggest disabling auto rotate, rebooting, and then never turning auto rotate on again. (even toggling on/off can get the events/0 process stuck at high cpu usage) Once I did this, the full bloated GB leak is spanking Froyo battery life.
This more than makes up for the poor contacts scrolling for this guy.
Also full bloated GB leak appears to be much safer for you SD card than other versions of the leak.
Click to expand...
Click to collapse
This. My battery life (and signal dBm) has been MUCH better even at work, which is notoriously hard on the battery due to being so well insulated.
I've had ZERO issues with the SD card so far, and it's a huge mystery what exactly is causing that. I ODIN'd the leak an hour after it was posted, then the NamelessV4 rom, then the NamelessV4.1 and haven't had a single issue. There needs to be a better process of defining it, and I'd be willing to bet it has something to do with the recovery the person used when it was flashed.
sarkozy said:
I've had ZERO issues with the SD card so far, and it's a huge mystery what exactly is causing that. I ODIN'd the leak an hour after it was posted, then the NamelessV4 rom, then the NamelessV4.1 and haven't had a single issue. There needs to be a better process of defining it, and I'd be willing to bet it has something to do with the recovery the person used when it was flashed.
Click to expand...
Click to collapse
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
xwhofarted said:
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
Click to expand...
Click to collapse
That's definitely what I'd be leaning towards. I also took the added (though not really needed) step of using the GB root exploit app, and confirming all was well before ever flashing CWM3.xx in ODIN, then going onto the nameless ROMs. I've actually tried to re-create the problem since I stuck in a spare 4GB card waiting for it to happen, but nothing so far.
Everything is so new, it's really all speculation for the time being. I personally don't think it's the ROM or the leak causing the problem, although it's obviously a factor. There are so many different combinations of recoveries being used (as if all of us read directions in full) and ROMs were flashed in different sequences that it's impossible to nail it down.
Aside from disabling auto rotate, I've had no complaints about the leak or ROM. I ran CM7 forever on my Eris before getting this Fascinate, and while I like it, it's a pain to deal with the missing functionality at times.
xwhofarted said:
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
Click to expand...
Click to collapse
I went from stock odin to nameless and my card was eaten alive...I followed the steps exactly as listed not missing one thing. So it has nothing to do with flashing from another rom
detox07 said:
I went from stock odin to nameless and my card was eaten alive...I followed the steps exactly as listed not missing one thing. So it has nothing to do with flashing from another rom
Click to expand...
Click to collapse
So, immediately upon flashing the sd card was corrupted?
It'd be nice if there was more cooperation among everyone to figure out the common problem. It seems like for all the trouble reports, there are as many or more of us with no issues. I can't see anything in logs that would tip off a problem, so it needs to be someone who has the issue.
I'm still leaning towards it being a recovery issue. It's odd that some people are saying the files still appear on the sd when viewed through the CWM interface.
Sent from my SCH-I500 using Tapatalk
Man, that would be awful if the CWM we were told to use is what is killing the SD cards, and a diffr version would have worked :O
I used the CWM linked in the nameless thread and no issue so far, but only 2 days so far.
So i have a verizon fascinate and am currently running cm7. (first tried the stable release but niw a nightly). Im eeally liking cm, but since i got it my battery life is garbage. Basically the drain seems to come from either the android os sercice or cell standby. Whenever i leave my phone inactive for a while, when i wake it up the battery has dropped a lot and tge phone is very warm. I have been modding this phone for a while, but im no android programmer. Purely based on the forum searchi. G ive done on the issue, it seemsblike cm7 has an issue with my modem or radio.
Extra info: my 3g/2g signals seem fine (always 0% time without signal). Wifi connectivity seems fine. Im also running glitch's kernal altho the problem has persisted with and without it (i did do a kernel cleaning first). I used the "go from anything to jb vanilla" guide cuz i was having issues switching to mtd at first (sry dont have a link rite now but it was on xda) . I get occassional force closes, but not really a problem. When i did a titanium back up, the very first time i flashed cm7 i Did restore system settings, but i did not do that every time since then. Ive done a fresh flash of the stable mod around 3 times trying different stuff, but this one is niggtly as i said, and each has had this issue.
If looked around a lot, and wgile this seems common, no one has posted a consistent solution or explanation to the problem, so thats what im looking for.
Sent from my SCH-I500 using XDA App
Hellomello13 said:
So i have a verizon fascinate and am currently running cm7. (first tried the stable release but niw a nightly). Im eeally liking cm, but since i got it my battery life is garbage. Basically the drain seems to come from either the android os sercice or cell standby. Whenever i leave my phone inactive for a while, when i wake it up the battery has dropped a lot and tge phone is very warm. I have been modding this phone for a while, but im no android programmer. Purely based on the forum searchi. G ive done on the issue, it seemsblike cm7 has an issue with my modem or radio.
Extra info: my 3g/2g signals seem fine (always 0% time without signal). Wifi connectivity seems fine. Im also running glitch's kernal altho the problem has persisted with and without it (i did do a kernel cleaning first). I used the "go from anything to jb vanilla" guide cuz i was having issues switching to mtd at first (sry dont have a link rite now but it was on xda) . I get occassional force closes, but not really a problem. When i did a titanium back up, the very first time i flashed cm7 i Did restore system settings, but i did not do that every time since then. Ive done a fresh flash of the stable mod around 3 times trying different stuff, but this one is niggtly as i said, and each has had this issue.
If looked around a lot, and wgile this seems common, no one has posted a consistent solution or explanation to the problem, so thats what im looking for.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You could flash jt's vanilla gb rom. That has good battery life.
Sent from my SCH-I500 using XDA App
Plus do you have an overclock?
Sent from my SCH-I500 using XDA App
I have had the standby battery drain on every CM7 version and Kernel tried so far including 7.1 stable,7.0 nightlies,JT's Vanilla,and PoolParty. It's even worse if I shut phone down and don't plug in. It will drop 50 to 75% overnight with phone not on?
Has done it with undervolting,overclocking,and voltage control not even installed. This is first time I have seen others having similiar issues.
I think this is a known issue for all MTD roms on the fascinate, if I'm not mistaken.
Sent from my SCH-I500 using xda premium
TheBDub said:
I think this is a known issue for all MTD roms on the fascinate, if I'm not mistaken.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I lose only 5% to 10% overnight on CM7 never really notice how much on MIUI cause I never ran it long enough. I guess every phone would behave differently for MTD's or maybe you have an app or mulitple ones that refreshes frequently(Fancy Widget comes to mind).
Well that really sucks, because i do enjoy cm7. But this also means if i go back to a touchwiz configuration like stock dl09 i shouldnt have these issues right?
But before that, has anyone who had these issues tried anything (ie kernels or maybe standby mode power conservation setting, etc... ) that have at least noticeably improved your battery life? Right now mines pretty unbearable (im talking 8hrs while on but totally inactive), but if i can get it up a little i might b able to manage.
Sent from my SCH-I500 using XDA App
I am also experiencing poor battery life. I just flashed 7.1.0 yesterday and absolutely love it. Was using com rom for a few months, but a friend said to try out cwm 7. I used to get about 6 - 8 hours of Pandora while at work and today I only got about 4 before my phone shut off. I'm going to try completely killing battery and charge with phone off tonight an see if it's any better tomorrow.
Any other suggestions? I'm not a noob when it comes to custom roms and flashing (I used to flash the **** out of my G1) but there may have been something I over looked when switching to cwm7. I wiped everything a few times before flashing including battery stats and dalvic.
My battery life is actually really good. Running latest nighty, undervolted -75 across the board,stock kernel, and no overclocking.
Just can't figure why I lose 50-75% of battery overnight when phone is shut down and not charging?
I have the same issue with CM7.1, turning phone of at 80% battery at night to find it at 25% at morning
Is there knows solution?
I'm not sure if other X2's do this, but my battery runs fine. I get a solid 10 hours of hard use out of it.
But lately I noticed that if I simply reboot I get another 20%-50% out of it. Yesterday, it was down to around 30%, restarted, went back up to 80% and drained normally the rest of the night.
Is this normal? Is there a fix or something I can do? I wish I could just get the most out of the battery without having to restart.
I'm just running rooted 2.3.4. I do the whole drain it to 0% once a month thing & fully charge.
--
P.S. I'm not making this up. Lol.
2.3.4 is the problem. There is a battery bug in the software where it reports less battery power than you have. Then, when you reboot, it might shoot up 5% to 10%.
Many custom ROMs have a fix in it. Not sure what the fix is or if you can apply it to the stock ROM.
Eclipse 2.0.x has the fix, but it also requires updating to the unofficial 2.3.5 OTA upgrade.
CM7 is based on 2.3.4 kernel and seems to have the issue resolved as well.
I see. Well, thank you for your help. Sorry if this is a repeated topic.
I just got started in the whole root/flashing "scene" so I'll have to see what I can do about CM7 now.
For those that want to stay on the stock rom, the fix is here.
Thanks, I'll try this out later.
I could use it too but the download link is dead. Thanks
Tried using new file from updated link but it would not work. Hung up at installing. Had to pull battery to restart phone. Any ideas?? Thanks
Probably something wrong with Peppermint's script. I have the original one from my phone. You can give it a try if you want.
http://www.mediafire.com/?a52x45m3dou19us
Thanks. It installed OK this time. I'll be checking to see if it makes a difference. Thanks again for the help.
You're welcome. Hope it works for you.
xtel said:
I see. Well, thank you for your help. Sorry if this is a repeated topic.
I just got started in the whole root/flashing "scene" so I'll have to see what I can do about CM7 now.
Click to expand...
Click to collapse
I bought my mother an x2, rooted and flashed CM7, she gets around 15 hours on the stock battery.
You will notice a huge change in performance, battery and more while you flash any ROM... Good luck, just follow the tutorials here in the forum.
SMILE It's Not Illegal Yet
Hey can anyone help with my battery prob? I got the extended battery from verizon I wiped battery stats after draining it fully and recharging fully twice. I'm running eclipse 1.3, speedy v7, and the cdma unthrottle mods. For some reason my phone eats this battery faster than my stock battery.
Sent from my DROID X2 using Xparent Cyan Tapatalk
Hi guys,
Not sure what could be the issue. I'm quite a veteran when it comes to troubleshooting these phones and flashing, etc. I've been a power user since the S1 and S2.
I flashed CM9 a few weeks ago, one of the stables and it was all running fine. One day I picked up the phone after charging overnight and it was really hot, the battery drained in about an hour or so, the whole time it was extremely hot.
I flashed a few other CM roms, which didn't fix much, tried full wipes and everything.
I've now gone back to an original samsung rom which I flashed via odin. This seems to have fixed the overheating issue, however, my battery barely lasts more than 3 hours on full charge and this is with absolutely minimal use (few phone calls).
WiFI is also extremely unstable. It takes a while to connect to any network, and when it does, it'll drop after a few minutes. I've tried different networks.
Scanning for WIFI networks works fine, so does this rule out a faulty WIFI chip?
I'm thinking the battery drain may be related to the WIFI card.
I've also tried a new battery.
Any suggestions, or is the phone fried?
A number of posts saying the same .
after charging overnight and it was really hot, the battery drained in about an hour or so, the whole time it was extremely hot.
jje
au_stevo said:
Hi guys,
Not sure what could be the issue. I'm quite a veteran when it comes to troubleshooting these phones and flashing, etc. I've been a power user since the S1 and S2.
I flashed CM9 a few weeks ago, one of the stables and it was all running fine. One day I picked up the phone after charging overnight and it was really hot, the battery drained in about an hour or so, the whole time it was extremely hot.
I flashed a few other CM roms, which didn't fix much, tried full wipes and everything.
I've now gone back to an original samsung rom which I flashed via odin. This seems to have fixed the overheating issue, however, my battery barely lasts more than 3 hours on full charge and this is with absolutely minimal use (few phone calls).
WiFI is also extremely unstable. It takes a while to connect to any network, and when it does, it'll drop after a few minutes. I've tried different networks.
Scanning for WIFI networks works fine, so does this rule out a faulty WIFI chip?
I'm thinking the battery drain may be related to the WIFI card.
I've also tried a new battery.
Any suggestions, or is the phone fried?
Click to expand...
Click to collapse
No, to get up your hopes, the phone isn't dead, yet.
Try flahsing a ROM, other than CM. I have the same problem, with AOSP, that's why I stick to sammy based ROMs, AOSP is made for the device, but Google only tunes it up to their standards, when it has something to do with their Nexus devices.
I'd say: Try a different ROM, don't overclock it. If that doesn't work, flash stock and then try it. One of the two should work, though!
I've gone back to a stock Samsung 4.0.1 rom. Flahed using odin, yet still the same issue with battery life and WIFI.
I've heard somewhere that flashing CM9 can cause WIFI issues, and there's a specific flash procedure to get it working normal again?
au_stevo said:
I've gone back to a stock Samsung 4.0.1 rom. Flahed using odin, yet still the same issue with battery life and WIFI.
I've heard somewhere that flashing CM9 can cause WIFI issues, and there's a specific flash procedure to get it working normal again?
Click to expand...
Click to collapse
There is no 4.0.1 for the S3. I'm just sayin'.
Sent from my GT-I9300 using xda premium
My bad, I mean whichever came with the phone.