Related
Hello everyone,
I rooted my phone in early september and put cyanogen 5 on it. I loved the new features but the speed wasn't very good so I switched to biffmod. That's when the problems started to happen. My battery life significantly decreased, I could barely keep it running for 4 hours. When I would open apps like google maps it would turn off instantly, but the phone and text messages worked flawlessly and I loved the speed so I didn't really mind. In the last few weeks it got worse. After a phone call the phone would turn off. I decided to reflash but it stayed the same. Now the phone lasts about 1 minute after unplugging from 100% charge. Anyone knows what could be causing this? or how to fix it?
EDIT : I'm using Biffmod 2.1 with 245 CPU minumum frequency and 556 maximum and DangerSPL.
is this happening on other roms or just biffmod??
Cyanogen 5 was working fine, only hapenned since I switched to Biffmod. (Which is using cyanogen 6)
do a nandroid (plug the phone in for this so it keeps power). then try another rom i say. we can then narrow down whether it is a rom issue or a battery issue. as far as i know no rom should give your battery a lifespan of 1 minute. make sure you have wiped your battery stats too. not sure if this will change anything but you never know.
Looks like a battery wipe fixed the problem. It got past the 1 minute mark! In fact I didn't even know that RA's recovery had that feature. Thanks!
no problem man. i figured it may have been something like that. if the stats dont match then it thinks the battery is low on power when it isnt.
False alarm, it did get better but it shut down after 30min of idle with wifi on.
ok. try a different rom to see if that helps or try draining the battery completely. keep turning your g1 on until it wont turn on any longer. then try charging it from there.
how long have you had the phone by the way?
I got the phone 1 year ago. I'm trying to drain the battery right now. I'll try switching rom after this. Do you have a recomendation? I'm on ebi1 radio.
not sure myself mate. i went for cyanogen, then went to superE as it suited my needs and aint changed since
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.
so this has happened twice now. When my phone is asleep (screen off) i go to wake it and the buttons light up but the screen won't turn on. I have trackpad wake enabled, but also tried the regular unlock button and no dice. If I do a battery pull everything works again. Do you all think this could be a rogue app? Is my screen potentially dying?
This has happened to me a couple times also. I believe it is software related but I do not know exactly what is going on. Maybe someone else can chime in? What ROM are you running? Im on Royal Ginger 2.1.
I am also on RG 2.1
are you using any profiles in setcpu to overclock/undervolt your phone? if so, try raising your min mhz
clarknick27 said:
are you using any profiles in setcpu to overclock/undervolt your phone? if so, try raising your min mhz
Click to expand...
Click to collapse
I am not using setcpu. I am running RG straight out of the box besides turning off screen animations and screen off to sleep mode. The second time that my phone behaved weirdly was when i was plugged into the standard charger that came with the MT4G. I don't remember if I was plugged in the first time it happened. Maybe there is something suspect there?
Debating about whether to install CM7, but there have been a few problems with it. I'm having a tough time finding the current state of the following issues:
1. Sleep of Death - Nook goes to sleep and doesn't wake up, forcing a reboot. There seems to be some debate over whether this is solved. One of the threads indicates that it's not a problem if you turn wifi off with the screen. Can anyone confirm?
2. Battery drain - Battery drains at 2%-3% per hour in sleep mode. I believe this is resolved. Can anyone confirm?
3. Premature Battery Death - Battery dies at various points over 0%. There seem to be various utilities for resetting battery stats, etc., but I can't figure out whether or not this is resolved.
4. Screen stays on when plugged in - Forced to hit the screen off button when plugging in the Nook. I've seen recent complaints about this one, so I'm assuming it's not resolved.
I did go through the threads and am confused about whether these issues still exist, so I figured I would try the Q&A section. If someone with CM7 wouldn't mind jumping in, that would be great. Thanks!
1. Maybe, I'm a lucky one but I haven't had problem with SoD regardless wifi on or off. I've been using nb100 and up, and now at 138
2. Using 138, i got 2-3% drop overnight, about 8 or 10 hours. With 120, zero dropped
3. Not experienced yet since I never let it down to sub-5
4. Mine seems act the opposite way: screen off, plug in to charge, screen automatically on, have to press power button to put screen off again.
1. I haven't seen this in recent nightlies.
2. Fixed; NC now deep sleeps when unplugged, even with WiFi on.
3. Fixed as far as I know.
4. Mine acts like yours and votinh's both; these are not mutually exclusive. If you plug in while on, the screen eventually dims instead of going off. If you plug in while off, the device turns on, sometimes just the backlight. I'd call this one minor, especially in relation to the other issues.
511pf said:
Debating about whether to install CM7, but there have been a few problems with it. I'm having a tough time finding the current state of the following issues:
1. Sleep of Death - Nook goes to sleep and doesn't wake up, forcing a reboot. There seems to be some debate over whether this is solved. One of the threads indicates that it's not a problem if you turn wifi off with the screen. Can anyone confirm?
2. Battery drain - Battery drains at 2%-3% per hour in sleep mode. I believe this is resolved. Can anyone confirm?
3. Premature Battery Death - Battery dies at various points over 0%. There seem to be various utilities for resetting battery stats, etc., but I can't figure out whether or not this is resolved.
4. Screen stays on when plugged in - Forced to hit the screen off button when plugging in the Nook. I've seen recent complaints about this one, so I'm assuming it's not resolved.
I did go through the threads and am confused about whether these issues still exist, so I figured I would try the Q&A section. If someone with CM7 wouldn't mind jumping in, that would be great. Thanks!
Click to expand...
Click to collapse
1) I get SOD about once a day regardless of how I have it set up. It does happen less with wifi on sleep only but at work I need to push data, so my wifi is on all the time and...it's an issue, not terrible but annoying none the less.
2) Battery drain, I get about 36 hours if I use it lightly, but I tend to charge it nightly because I can't take a chance of heavy use at work and loosing it.
3) PDB, never had this problem.
4) The screen turns off by just hitting the screen off button. This isn't a big a deal actually, since you gotta plug the thing in, another button isn't a big deal. I have katecca screen lock and off in my bar at the bottom, so it's easy to turn off. I also have the nook power off widget but I haven't used it much.
That's great. Thanks a lot for the responses. Really helpful.
I have only had it CM7 on my nook for one day, so im not sure about the battery issue. But i know i put it down around 10pm last night with less then half a battery and i got home from work around 3pm and it had about 25% batt left.
Besides that sometimes when i plug it in it stays lit up. but thats a "meh who cares" to me at least.
Running 7.1.0 RC1 with Dal's OC, On Demand, with lowered Voltage on the steps
1) I've only had one SOD ever (knock on wood), it seems to be mostly cleared up
2) Battery drain has not been a problem for me. On .29 it was more only 1%/hr for battery drain.
3) I haven't experienced early battery death at all
4) It isn't a big deal, especially if you charge with the provided outlet adapter for quick charge. Don't see this preventing you from installing CM7.
If these stats are correct from ASI (I'm hoping they are, they sound right), I'm at 76% after 3 days, 19 hours uptime, and 7 hours of it without sleep.
I say go for it. Even if it is off SD (mines on emmc) it is still a much better experience than stock/rooted. I doubt anything will make me change from CM7, unless ICS becomes a viable option in the future.
Just a follow up on this. I installed CM7 and have not had a Sleep of Death, have normal battery drain comparable to stock rooted, and have not had premature battery death. The screen does come on when I plug the Nook in, but like everyone mentioned, I just turn it off and it's no big deal.
So far, my wifi actually reconnects more reliably than on stock rooted 1.1. I'm overclocked to 1200 Mhz, with no voltage or other adjustments.
Following up again - I get a SOD or a reboot about every five times I turn off the screen in CM7. I tried to use Tasker to turn wifi off with the screen, which has solved the problem for some people but this made no difference at all. I was running a nightly from late July and updated to another from late August (173?) but the problem hasn't gone away. I may try Stock 1.2 rooted.
511pf said:
Following up again - I get a SOD or a reboot about every five times I turn off the screen in CM7. I tried to use Tasker to turn wifi off with the screen, which has solved the problem for some people but this made no difference at all. I was running a nightly from late July and updated to another from late August (173?) but the problem hasn't gone away. I may try Stock 1.2 rooted.
Click to expand...
Click to collapse
I had no SODs from almost a week with n165; I upgraded to n171, got an SOD first time I put it down for a while, so I reflashed n165 and I'm sticking with it until I hear of something I need.
WiFi always on.
As always, YMMV.
Sent from my NookColor using XDA Premium App
Just a little update:
Since using nb169, I got a few SoD, did update again to nb173, still got hit occasionally.
I never have this kind of issue before but lately.
The changes I made
a. Played around with ADW Launcher setting (especially Desktop Animation)
b. Recently installed Simi Clock and updated some apps (such Nook app)
c. Recently having 8GB uSD card plugged in.
For some reason, I don't think a. and b. causing problem but c.
can you run cm7 with the 1.2 or 1.3 updates from b&n? im on a autonooter 1.1 and have been wanting to move up to something better especially if i can have flash finally.
miss_october said:
can you run cm7 with the 1.2 or 1.3 updates from b&n? im on a autonooter 1.1 and have been wanting to move up to something better especially if i can have flash finally.
Click to expand...
Click to collapse
CM7 is custom Gingerbread-based ROM, it has nothing to do with stock ROM and there is absolutely no relationship between the two (except they are both Android OS)
votinh said:
CM7 is custom Gingerbread-based ROM, it has nothing to do with stock ROM and there is absolutely no relationship between the two (except they are both Android OS)
Click to expand...
Click to collapse
thanks for the response
One last (I think) follow up. I installed stock rooted 1.2 thinking it CM7 causing me problems over the last month. Turns out I had the same problem on CM7.
I read my Nook before I go to sleep, so it's often dark in the room. I turn the brightness WAY down. The problem ended up being the Adjbrightness "Lock brightness so other applications can't change" setting. It has something to do with screen dimming when turning off the screen. This setting being on was causing frequent reboots both on CM7 and stock rooted 1.2. I ended up going to ScreenFilter instead, and the problem has completely gone away at least so far.
511pf said:
Debating about whether to install CM7, but there have been a few problems with it. I'm having a tough time finding the current state of the following issues:
1. Sleep of Death - Nook goes to sleep and doesn't wake up, forcing a reboot. There seems to be some debate over whether this is solved. One of the threads indicates that it's not a problem if you turn wifi off with the screen. Can anyone confirm?
2. Battery drain - Battery drains at 2%-3% per hour in sleep mode. I believe this is resolved. Can anyone confirm?
3. Premature Battery Death - Battery dies at various points over 0%. There seem to be various utilities for resetting battery stats, etc., but I can't figure out whether or not this is resolved.
4. Screen stays on when plugged in - Forced to hit the screen off button when plugging in the Nook. I've seen recent complaints about this one, so I'm assuming it's not resolved.
I did go through the threads and am confused about whether these issues still exist, so I figured I would try the Q&A section. If someone with CM7 wouldn't mind jumping in, that would be great. Thanks!
Click to expand...
Click to collapse
I try to stay up to date with the latest nightlies.
1) This is not completely solved. It's rare now (I think it was issues with WiFi), but it has still happened to me recently.
2) Battery drain was fixed with kernels that support Deep Sleep correctly. Not any 7.0.x builds, only 7.1.x+ (RC1) and nightlies have fixed kernel. So this shouldn't be an issue (unless you have a rogue app that is keeping the CPU active, which would prevent Deep Sleep. The "CPU Spy" app will let you see if this is working correctly).
3) This is better, but still a problem. My Nook Color will just switch off at 4% battery now. It use to switch off when I was a lot higher. It's not supposed to do that. It's supposed to gracefully shutdown when low. I have several iOS and Apple devices, so I'm use to things shutting down correctly when low. My Nook Color always just randomly powers off.
4) This isn't a big deal. The screen comes on when charging, but you can turn it off if you want. It stays dim, and the Nook Color charges fine. Dalingrin (the kernel developer guy) said leaving the screen on was a fix to some nasty crash.
#3 is the biggest issue to me, as I've been in the middle of something when my Nook Color randomly powered off. Clearing battery stats, rebooting, etc - none of that makes it perfect.
#1 use to be the biggest problem, but it's very rare for me now.
#2 has been fixed, and #4 doesn't bother me.
stolenmoment said:
I had no SODs from almost a week with n165; I upgraded to n171, got an SOD first time I put it down for a while, so I reflashed n165 ...
Click to expand...
Click to collapse
I misspoke; n165 SOD's on me too, so I conclude that I dl'd 165 and didn't flash it; I reflashed n161 and have been stable since.
I keep WiFi on for email and podcast updates.
I've always got an 8G uSD card in.
Sent from my NookColor using XDA Premium App
So it was on the afternoon, 40°C outside, I took a nap and left my s7 edge charging as usual (it was inside my house and had my curtains down, so the sun wasn't aiming at the phone), 2 hours later I woke up and the phone was hot as hell, it was burning my hand, the weird thing is that it was on something like a safe mode (widgets dissapeared, could't pull down notification bar and after some seconds it kept rebooting) I could not turn off the phone without it rebooting, so I went to recovery mode (temp was 44°C), wiped cache and dalvik and rebooted, also put my phone on a fan to try to cool it down. When it restarted it was again in that weird mode and after 2 minutes it went back to normal mode, but a lot of settings had restored to its defaults (wifi passwords deleted, keyboard on default mode, widgets still not there, notification asking me about if I wanted notifications to show on lockscreen...). What could it be? I've disabled fast charging just in case, I don't want it to happen again
fanfzero said:
So it was on the afternoon, 40°C outside, I took a nap and left my s7 edge charging as usual (it was inside my house and had my curtains down, so the sun wasn't aiming at the phone), 2 hours later I woke up and the phone was hot as hell, it was burning my hand, the weird thing is that it was on something like a safe mode (widgets dissapeared, could't pull down notification bar and after some seconds it kept rebooting) I could not turn off the phone without it rebooting, so I went to recovery mode (temp was 44°C), wiped cache and dalvik and rebooted, also put my phone on a fan to try to cool it down. When it restarted it was again in that weird mode and after 2 minutes it went back to normal mode, but a lot of settings had restored to its defaults (wifi passwords deleted, keyboard on default mode, widgets still not there, notification asking me about if I wanted notifications to show on lockscreen...). What could it be? I've disabled fast charging just in case, I don't want it to happen again
Click to expand...
Click to collapse
Which ROM are you on? Are you using the charger cable and brick that came with your phone?
RVR said:
Which ROM are you on? Are you using the charger cable and brick that came with your phone?
Click to expand...
Click to collapse
Stock rom from 2018 with moro kernel, not the original cable, but have been using it for over a year
fanfzero said:
Stock rom from 2018 with moro kernel, not the original cable, but have been using it for over a year
Click to expand...
Click to collapse
Which governor and min-max frequencies are you using? Have you used overvolt options?
RVR said:
Which governor and min-max frequencies are you using? Have you used overvolt options?
Click to expand...
Click to collapse
Stock governors, no, just undervolting, but it had been stable for a week or so, when I entered mtweaks everything had been restored to its defaults
So today it happened again, but this time looks like it corrupted my /data partition, system got restored to its defaults without me touching anything (fingerprint was still registered and apps were still installed), most of the apps give me force close and the ones on the system partition (whatsapp, instagram...) boot but is like if its data had been wiped