Database Users

Possible Battery Problem

So i have a Samsung Nexus S and im having problems ith my battery/charge.
I have recently installed a new Rom [CM-7.1.0 RC1] http://download.cyanogenmod.com/get/update-cm-7.1.0-RC1-NS-signed.zip
And noticed when i woke up this morning that my phone was off [ok thats strange] so i got up tried turning it on , i did fire up [thank god] BUT hen it came to the homescreen it started to run uber slugish, and the battery bar was RED [wtf] then it just did the shutdown procedure.
So i plugged in the charger thinking it was flat and tried fireing it up again, it did the same thing, i have an app called ''Battery Monitor'' where it shows all battery info in my notification pull down, the battery is now charging on my laptop but not actually charging its just keeping my phone alive.
This is what it says,
1% On USB for 3m ETA n/a
1%, 275mA, 3625mV, 30.0C
Im just about to order a new battery, but if anyone has had similar problems please let me know as this is rather frustrating

Could be cm7. I just read about a Guy who's screen kept waking up in the middle of the night on the new cm7 RC. You could try flashing another rom or even go back to stock and see of that fixes the problem.
Sent from my Nexus S using XDA Premium App

Kindatired said:
Could be cm7. I just read about a Guy who's screen kept waking up in the middle of the night on the new cm7 RC. You could try flashing another rom or even go back to stock and see of that fixes the problem.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thanks for the reply, soon as i seen the problem i reflashed to a stable nightly [115] and the problem persists i might try deleting battery stats in recovery but would this have any bad effects ?

This is strange....for me all ok
Inviato dal mio Nexus S usando Tapatalk

I fixe the problem, i did a reboot [lol] i had done this multipe times, to no aviele but its fine now..

Working SoD fix from Dalingrin (re-post from rootzwiki)

Sorry if this is already posted around here somewhere, but I found this yesterday and was surprised that I hadn't seen anything here about it:
http://rootzwiki.com/topic/8853-working-sod-fix-from-dalingrin/
I installed the new kernel on both of my TouchPads last night, cleared both caches and fixed permissions, and set my lower CPU speed to 192MHz (from 384MHz to help prevent SoDs previously). I wasn't using SoftLocker, so I can't comment on that.
I haven't had a single SoD yet, and I left one of the TouchPads unplugged overnight to see what the battery drain looked like with the new kernel. I'm pretty sure it drained <1% overnight, and CPU Spy shows that all that time was spent in Deep Sleep.
Obviously this isn't a long-term evaluation, but initial results look promising.
UPDATE: Some folks have reported that applying this kernel breaks sound for them. I know it's happened to some people on alpha 1 and others on alpha 2.1, and I also know it hasn't happened to others (myself included). There's quite a bit of discussion about this on the linked thread, so if it happens to you, please refer to the existing information there.

Just flashed this clearing cache, dalvik and fixing persmission.
No SoD yet but NO SOUND.
I have no sound on my touchpad.
cleaned everything and flashed the fix again but no luck.

Silenus21 said:
Just flashed this clearing cache, dalvik and fixing persmission.
No SoD yet but NO SOUND.
I have no sound on my touchpad.
cleaned everything and flashed the fix again but no luck.
Click to expand...
Click to collapse
I think that may have happened to some other folks on the rootzwiki thread. Read down a bit and see what they say. I believe some of them reflashed CM7 with the new kernel (toward the end of the thread) and that fixed the issue. Worst-case scenario, someone has uploaded a recovery zip with the original kernel so you can roll back.
For what it's worth, neither of my TouchPads lost sound, so it's definitely possible to apply this without that happening.

SCWells72 said:
Sorry if this is already posted around here somewhere, but I found this yesterday and was surprised that I hadn't seen anything here about it:
http://rootzwiki.com/topic/8853-working-sod-fix-from-dalingrin/
I installed the new kernel on both of my TouchPads last night, cleared both caches and fixed permissions, and set my lower CPU speed to 192MHz (from 384MHz to help prevent SoDs previously). I wasn't using SoftLocker, so I can't comment on that.
I haven't had a single SoD yet, and I left one of the TouchPads unplugged overnight to see what the battery drain looked like with the new kernel. I'm pretty sure it drained <1% overnight, and CPU Spy shows that all that time was spent in Deep Sleep.
Obviously this isn't a long-term evaluation, but initial results look promising.
Click to expand...
Click to collapse
I don't think it's been mentioned much because it isn't a common issue anymore, i've never had sod on my touchpad and a lot of people claimed alpha 2 fixed the issue.
Sent from my HP Touchpad using Tapatalk

Alpha 2 definitely didn't fix the SoD issue (otherwise why would Dalingrin have kept working on it?). I think most folks used some combination of SoftLocker and cranking up the minimum clock speed to avoid it, both of which have significant impact on battery life. Hopefully this kernel (or some subsequent iteration if this one doesn't fully address it) will give stability and good battery life, particularly when the device isn't being used.

I've had the SoD on both a1 and a2. Flashed this fix. No SoD yet. Sound is still there too.
Sent from my ERIS using XDA App

according to the rootzwiki thread the fix is not allowing WIFI to go to sleep mode. This was the cause of most SODs.
You'll find in this fix that your WIFI will not turn off during sleep even if you set it to do so.

so after i installed the update it don´t save my "overclock"
i set up 1512 mhz but after reboot it´s gone and back at 1200
any idea for this?

Im not sure if Im the only one. But since Alpha 2 I have yet to see SOD, was there anyone else who saw SOD vanish completely with Alpha 2?

I had one sod with alpha 1 then none with alpha 2. I haven't installed any apps or changed CPU settings it just has never happened to me.
Sent from my HTC Desire HD using Tapatalk

synapses11 said:
Im not sure if Im the only one. But since Alpha 2 I have yet to see SOD, was there anyone else who saw SOD vanish completely with Alpha 2?
Click to expand...
Click to collapse
Not a single SOD here, but i skipped alpha 1.

After playing with it for a while, no SoD, but now I'm having wifi issues. Won't stay connected. Did a restore back. Now no wifi issues, but as soon as it goes to sleep, it wont wake up. Uggh. Can't wait till this gets stable. Getting bored of webos.
Lolento said:
according to the rootzwiki thread the fix is not allowing WIFI to go to sleep mode. This was the cause of most SODs.
You'll find in this fix that your WIFI will not turn off during sleep even if you set it to do so.
Click to expand...
Click to collapse
Sent from my ERIS using XDA App

mouseym said:
Not a single SOD here, but i skipped alpha 1.
Click to expand...
Click to collapse
I get Sod all the time. I put my cpu to 648mhz and it still does it. I even put it up to 1500 min 1700max and it did it. I'll edit this post to see if flashing works. Im charging my touchpad at the moment.
EDIT: flashed. So far no SOD but its a little too soon to tell. We'll see what a few hours does.
Sent from my DROID X2 using xda premium
EDIT: I seem to have all functionality and I have not SODed yet. Looks good so far
Sent from my HP Touchpad using xda premium

mouseym said:
Not a single SOD here, but i skipped alpha 1.
Click to expand...
Click to collapse
Same here, i started on Alpha 2.1
i think the problem is alpha 1 related
im guessing a clean wipe will fix the problem...

I had sod from hell.. I just kept it on the touch stone to keep it awake in between.
This fix worked though. Whole day without death
Sent from my HTC Glacier using Tapatalk

Try No-Frills from Market. He's on here too. No SoD for me. It has some feature that prevents it.

Alpha 2.1 was already out by the time I got my touchpad, only had 2 SOD on it prior to installing this patch and none since. Currently I am using No Frills CPU with 192 min and 1512 max I think. Running great and no other issues to speak of. Sound is working fine and this has not impacted my battery life at all, may even be better.

Op should be updated to state that this kernel breaks sound on alpha1. Make sure you are on alpha2 before flashing.I posted both a revert and a repackaged alpha2 with the fix already applied in the thread on rootz.
Sent from my Sensation using XDA App

cpittman said:
Op should be updated to state that this kernel breaks sound on alpha1. Make sure you are on alpha2 before flashing.I posted both a revert and a repackaged alpha2 with the fix already applied in the thread on rootz.
Sent from my Sensation using XDA App
Click to expand...
Click to collapse
I just updated my original post in this thread with a disclaimer about the sound issue. I think it's also affected some alpha 2/2.1 folks, so basically I'm just making sure folks know about it and know to consult the original thread for information about how to resolve it.

Ya I'm not sure what the common thread is with no sound then. I only experienced it in relation to alpha1.
Sent from my Sensation using XDA App

Galaxy Note randomly shuts down

Since i upgraded to ICS my note randomly shuts itself down to the point I have to longpress the on/Off button tot boot It up again.. there's no sign of low battery after rebooting ...
Very annoying if you're counting on your alarm clock in the morning to get to work in time
I recently flashed stunner 5.0 and am very pleased with this rom.. I dunno if it's stunner-related or not..
Anyone else experiencing this?
Sent from my fabulous GT-N7000 using xda premium

User error, start fresh from gb.
Sent from my GT-N7000 using xda premium

I completely restarted from stock GB before rooting again / flashing ics.. did it twice already .. so I don't think it'll work if I try it a third time...

Nicosch said:
Since i upgraded to ICS my note randomly shuts itself down to the point I have to longpress the on/Off button tot boot It up again.. there's no sign of low battery after rebooting ...
Very annoying if you're counting on your alarm clock in the morning to get to work in time
I recently flashed stunner 5.0 and am very pleased with this rom.. I dunno if it's stunner-related or not..
Anyone else experiencing this?
Sent from my fabulous GT-N7000 using xda premium
Click to expand...
Click to collapse
Sounds like an SOD. It is very common with ICS Roms and currently there isn't really a proper fix for it. Essentially, your phone is still on, but its screen won't come back on until you reboot/pull battery. Look up SOD or screen of death or some other combination to search for tips on how to improve its reliability

Flash basband lp6 that will fix your sods

Yeah its weird prior to lp5/6 release I had nothing but sod. But with new ics leak I haven't had any sod with stock or custom roms and I think majority of the community hasn't had many if any like the old leaks.
Which apps are you installing? Are you restoring backup data from titanium backup or similar.
Sent from my GT-N7000 using xda premium

Yep.. restoring like 170 apps using titanium backup ... including user data ... could that be the cause?
Sent from my GT-N7000 using xda premium

brockyneo said:
Flash basband lp6 that will fix your sods
Click to expand...
Click to collapse
Baseband = modem ? Right.. ?
Any idea where to get only LP6 modem ?
I suppose I have to flash it using mobile Odin?
Thnx in advance ..
Sent from my GT-N7000 using xda premium

Nicosch said:
Baseband = modem ? Right.. ?
Any idea where to get only LP6 modem ?
I suppose I have to flash it using mobile Odin?
Thnx in advance ..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Here you go mate flash via cwm http://www.mediafire.com/?zuicr1120j54vx9
Do wipes too before just to be on safe side

the restoring apps could be the issue also. Remember that stunner rom, has alot of built in root apps that cover setting up the cpu and such. If the modem doesnt fix it I would suggest starting over fresh with your apps, and seeing if your problem goes away.

Flashed modem.. and my note seems to have survived the night ..
If I get a sod today .. I'll restart from stock later this evening, and manually restore my apps and/or userdata..
Thnx for the advice
Sent from my GT-N7000 using xda premium

One hour and fifteen minute later and had my first sod on LP6..
Sent from my GT-N7000 using xda premium

Seems like CPU governors like setcpu and 2nd core combined with energy saving apps tend to mess things up.. removed them all and flashed baseband radio LP6..
Now running a few hours without SOD's..
Keeping my fingers crossed
Sent from my GT-N7000 using xda premium

i would reccomend Stunner 0.5
just for its power saving options you can control 3g data and Wifi at any time to be turned off automaticly so it saves battery though ROM is quite kind with power, anyway install it clean and then just with any CPU managing application set the settings of CPU to 1400 MAX - 200 MIN and ONDEMAND so it doesn't run constantly on full power and then add a profile for Screen Off and set it to 200 MAX- 200 MIN aply at boot of course checked good luck

I've had SoD's and reboots on imilka's CM9v2 and Stunner 5 beta so when Stunner released 1.4.19 I started completely fresh. I reflashed the LP1 repack with wipe, did another full wipe in CWMR before flashing Stunner 1.4.19, flashed the LP6 modem and did another full wipe. I've been using it for about 20 hours, 14 hours since my last manual reboot and I haven't had a problem yet.

Just flashed the new Stunner 1.4.19 this morning over my existing 5.0 version..
And have not had one SOD since..
Let's hope it stays that way..

I think ics is to early in this stage to restore apps with userdata. Im not talking about xda app, slacker or things of that nature. But restoring things like setcpu, rootexplorer and other root apps could lead into problems. Unless you are very strict about backups.
Happy you got your problem situated.

Hey guys, lucky I found this thread.
I followed this guide as literally as I could: http://forum.xda-developers.com/showthread.php?t=1763151
But as far as I can tell I am, too, getting a screen of death every now and then. For example, I went to bed last night and left my phone with 70% battery, this morning, 8 hours later, I found it with 22%. When I checked the battery graph (I would post a SS but I cant use the stylus for that and dont know any apps for the job ATM) I found a "gap" between 70% and 22%, its like nothing was there. So Im tempted to believe that it is, in fact, a SoD.
I've read the experiences of this previous user but I cant really figure out what it is im supposed to do to fix my note. I am using CM9 (latest nightly) and would like to continue doing so, is there a way for me to fix the SoD without changing roms?? I am not a m4d h4xx0r on this subjet, but I manage and I can follow a clearly laid out guide as good as anyone.
I would hate to waste your time, so if you could please be extra clear when explaining whatever procedure I must follow it would be awesome.
If anyone could help me out on this subject you would have my humble thanks!

Galaxy Note 2 shuts off
The issue exists on the Galaxy Note 2 as well and has nothing to do with software.
The problem is hardware related. The phone is flawed and shuts off on it's own under various conditions, all hardware related. Take a look at this video: http://www.youtube.com/watch?v=SjLn2yikYnI
Also, take a look at this site I built that goes in to more detail regarding the issue: www.GalaxyNote2ShutsOff.com
One look at that short video and I am sure there will be some light bulbs going off. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.

swaldrop said:
The issue exists on the Galaxy Note 2 as well and has nothing to do with software.
The problem is hardware related. The phone is flawed and shuts off on it's own under various conditions, all hardware related. Take a look at this video: http://www.youtube.com/watch?v=SjLn2yikYnI
Also, take a look at this site I built that goes in to more detail regarding the issue: www.GalaxyNote2ShutsOff.com
One look at that short video and I am sure there will be some light bulbs going off. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.
Click to expand...
Click to collapse
Well Thank you for REVIVING THREADS that are LIGHTYEARS away from now.........revive it? Really? Every thread that says shut down?
<<<The CRACKS on my NOTE shows how often it KISSES the FLOOR>>>

[Q] NC will not do anything

This is my first nook. I did some trading to get it. It had cm9 on it when I got it but it a tad laggy so I put mirages cm7 on it using from manager. It has been running great ever since and today I put it on the counter(battery was around 60%) I took it to my room a little later to charge since I have to work tonight but before I plugged it in I tried to wake it up but the screen would not come on. It will not do anything at all. Never owning one I have no idea how to diagnose it.
Sent from my Galaxy Nexus using xda premium

Welcome to the Sleep of Death - I have this happen occasionally too.
Hold the power button for ~10 secs, the screen will get noticeably darker when it actually turns off. Let go and press for another ~8 secs to cause it to reboot - you'll get that distinctive flash from the back-light.
I find this happens more often when I leave the wifi on and it goes to sleep, so I'm pretty obsessive about turning that off before sleeping the nook.
What ROM are you running? Stock CM7 or Phiremod / Mirage / etc.?

HumanXv2 said:
This is my first nook. I did some trading to get it. It had cm9 on it when I got it but it a tad laggy so I put mirages cm7 on it using from manager. It has been running great ever since and today I put it on the counter(battery was around 60%) I took it to my room a little later to charge since I have to work tonight but before I plugged it in I tried to wake it up but the screen would not come on. It will not do anything at all. Never owning one I have no idea how to diagnose it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That was probably Sleep of Death (SOD). Read about it in my tips thread in my signature link.
Sent from my Nook Color running ICS and Tapatalk

Worked like a charm, thanks a lot. I'm running mirage now and sometimes back to miui. Debating on going back to cm9.
Sent from my Galaxy Nexus using xda premium

[Q] Cannot wake up device from sleep

So I've had this problem for some time maybe a couple of weeks.
The problem is that I sometimes cannot wake up my device after setting it down for sometime. For example if I go to sleep get up the next morning and then screen will not turn on. I have to hold power button down for multiple seconds and press it multiple times. Also one recent occurrence of this there was massive battery use. See attached photo.
If anyone knows why this is occurring or knows any remedies that would be appreciated.
Using PA 2.54
Franco Kernel
I can provide more information if needed. Just ask.
Thanks
Sent from my Nexus 7 using xda app-developers app

I was having serious issues with my 16gb. Very hard to turn on, sometimes hold power for 10 seconds, sometimes 30, sometimes 5.. all over the place. And it only started after I believe the 4.2 update.
Also, it was draining battery while off. Charge it overnight, leave it off the entire time, come back 8 hours later. Turn it on and only have 50% battery.
Sometimes the charging animation would lock up while off as well. And if the device was turned off, and you plug it in to charge, it turns on. It shouldn't.
I think I've narrowed it down to the bootloader. My bootloader was at 4.13, and Flashing the 4.2.1 and 4.1.2 factory images didn't help.
Last night I finally fixed it. I ran the 4.1.1 factory image. Which put the 3.34 bootloader back in place. This wipes the device. So I flashed the recovery back and then reflashed Paranoid Android 2.99B6. All is good now, it turns on like it should, doesnt come on when plugged in, etc.
Meanwhile a new 32gb I have I can flash the 4.2.1 factory image, and I have no issues with that one.
Which bootloader are you on?

Hmm. That seems to be the exact same issue I have!
I just checked my bootloader and I have 3.41. But I never went up to 4.2. I stayed at 4.1.2 with PA 2.54.
Hmm. Maybe I'll try what you tried!
Sent from my Nexus 7 using xda app-developers app

kazemitsui said:
Hmm. That seems to be the exact same issue I have!
I just checked my bootloader and I have 3.41. But I never went up to 4.2. I stayed at 4.1.2 with PA 2.54.
Hmm. Maybe I'll try what you tried!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You can flash the 4.1.3 bootloader from JB 4.2 and use it with 4.1.2. I am, and it works perfectly and I never have a problem booting or bringing it out of sleep mode.

I think it was just your Franco kernel. Kernels are typically the cause.
I'm running PAb6 and no problems.
Sent from my Nexus 7 using XDA Premium HD app

player911 said:
I think it was just your Franco kernel. Kernels are typically the cause.
I'm running PAb6 and no problems.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Hi, which kernel are you using? I just changed my bootloader back to 3.34 and my kernel to motley. See if that helps.
Thanks for the tips.
Sent from my Nexus 7 using xda app-developers app
----------------------------------------------------------------------------------
seems after flashing a new kernel to motley the problem still occurs...
I think ill factory reset. reinstall PA gapps and everything... see what happens.

anyone else have any insights into this... flashing a new kernel and it still occurs

Sometimes you have to set you're minimum cpu frequency above 200 using one of the various cpu or kernel tuners
Sent from my HTC One X using xda app-developers app

Just had this similar problem. I drained the battery to about 11% on wednesday night, so i shut it off and charged it to 100% on that very same night. Turned it on on friday night (It should have been turned OFF all this while) and it wont start. After the help of the AC charger, it came back on and found out the batt was at 0%. Which should not be the case even if the tablet was accidentally switched on because theres no way it can drain from 100% to 0% in just 2 days. And everytime i leave it plugged into AC it suddenly turns on and shuts down due to low power. Am using TWN ROM V1 (Android 4.2.1) with M-Kernel A17 kernel if that has anything to do with it.

So I think I have it figured out that if I set my wife policy to keep awake always no problems, but if it is set to keep awake only during charging, I will have problems
I will try it out on a higher cpu setting with semi awake
Sent from my Nexus 7 using xda app-developers app

Just wiped the device and flashed CleanROM 3.0 on it and NOTHING else (No extra scripts, custom kernels, radios..etc) and it seems to have been stabilized. Although the battery drained pretty quick while i was using it last night, but I was installing apps and setting up stuff on the nexus so its not a very accurate benchmark. Will continue to monitor.

Hmm, I see. Well that's great that you solved it
It seems after switching my minimum cpu to 200. It still froze when I was trying to wake it up this morning
Maybe a full wipe is needed...
Sent from my Nexus 7 using xda app-developers app

Yes you should have done a full wipe like I did. All still seems to be good on my side. Looks like for my case it was M-Kernel a17 causing the problem. I doubt such a thing would happen due to a faulty bootloader.

So I did a full wipe of my tablet and instead installed PA 2.99 b6, flashed correct gapps, then flashed the beats audio v3b2 and the same thing occurs.
im using franco kernel v30 no OC just gpu oc to 446.
my tab if i leave it unplugged and set wifi policy to keep wifi on during sleep only when plugged in I get this problem that I cannot fix... which is the tablet freezes or something and i cannot turn the screen back on until i hold the power button, Then turn it back on. Also on a side note for the first time this morning, the back of my tab was hot, which never occurred when i was on PA 2.54
Any insights on this issue anyone?

full wipe and flash a ROM that comes with the stock kernel. I did that with CleanROM 3.0 and its still working fine to this day. Will probably try flashing franco or M-kernel again when I have the time. But for now it seems that a custom kernel might be the issue here.

cr0wnest said:
full wipe and flash a ROM that comes with the stock kernel. I did that with CleanROM 3.0 and its still working fine to this day. Will probably try flashing franco or M-kernel again when I have the time. But for now it seems that a custom kernel might be the issue here.
Click to expand...
Click to collapse
Thanks for all your replies. It seems to have fixed it after updating my ROM im really not sure what happened with PA 2.54 but with PA 2.99b6/8 it has not freezed at all, but then again the min cpu freq i have is at 340 heh...