Related
My g1 started shutting off randomly. I'm not sure what the problem is. Anyone else have this problem before? Thanks.
I'm on SuperD 1.6 with darkstar theme and sterricsons lockscreen
Amon_Ra recovery
BFS and locksreen sleep hangs some times. I installed the same thing this morning and havn't had one yet.
I would say re-partition, wipe all, flash. make sure you back everything you want up. good luck!
I was thinking my battery needs to be calibrated? It's weird it just started happening...
I drain my battery until the phone dies then charge it when it's off. The LED turns green in under an hour. Something has to be wrong here right?
hmm, have you tried a new battery then? and I read you want to drain it to about 20-30% not all the way, this way it lasts longer. But I would say try someone else's battery or buy a new one
have you re partitioned wiped everything and flashed?
I don't want to buy a new battery if I don't need it. Money is tight! I have wiped everything though but haven't re-partitioned.
I let it drain and wiped everything today. Let it charge while off and it hasn't shut off. I'll have to see if the calibration was off or something..
ToeKnee! said:
My g1 started shutting off randomly. I'm not sure what the problem is. Anyone else have this problem before? Thanks.
I'm on SuperD 1.6 with darkstar theme and sterricsons lockscreen
Amon_Ra recovery
Click to expand...
Click to collapse
Mine did it to me before and then it just shut off and died.
Mine (actually, an ADP1, not a G1) was doing the same thing. I returned it to the vendor. I wasn't running anything fancy, it did it on both the factory 1.0 build and after I upgraded to 1.6.
When my phone is sitting idle (screen off) it will randomly decide to power itself off. Has anyone else noticed this? Any ideas on what could be causing it?
The Balvenie said:
When my phone is sitting idle (screen off) it will randomly decide to power itself off. Has anyone else noticed this? Any ideas on what could be causing it?
Click to expand...
Click to collapse
you mean randomly power itself ON, right?
if that is the case, it's normal, it just mean it woke up to connect to the internet, to get updates of news, emails, or whatever it was scheduled to pick up
nope. i mean it randomly turns itself off. this topic is being discussed over on the att captivate galaxy forum section.
interesting, so it's going from stanby mode, to complete OFF... nope never seen that happen to my i9000 model
yep totally powered off... completely sucks... looks like there are a bunch of ppl that have this issue with the captivate on att. $10 says its some lame piece of software that att puts on your phone that's causing the problem.
it's possible, i've read here a few users having crazy power issues (battery draining very fast) with their SGS i9000, but after wiping it out clean, to start anew, then the power problem is gone away.
so yes, a software could cause something weird like that.
Factory reset and so far so good
Hey guys,
I use a Galaxy S here in Hong Kong and I had the same random shut down issue constantly happen when my screen went off...
I tried everything, check temperature of cpu, etc. etc. and nothing worked, it just got worse and worse.
I even changed the battery to use the spare one that came with this. Still problematic.
Used SET CPU to limit the cpu to 400mhz, still problems.
Finally I did a factory reset and so far so good.
I only have the original system installed with the Remember the Milk app installed.
24 hours, no problems.
Installed AppBrain app.
Then I installed 3G WatchDog
12 hours, no problem.
Then I installed Paperdroid
12 hours, so far no problems at all.
If I run into an issue I'll post it here. But I think it definitely was a software issue.
Update - it randomly shut down on me
Alright guys, it shut down on my randomly today in the afternoon......
I dont know if it's the re-charging that screwed it up?
Because after my factory reset, last night was the first time i charged it....
Hmmm
This happened to me too - two days in a row until noon it would shut down two or three times - i uninstalled SetCpu and for now (24 hours) it hasn't happened again. I am not sure if it was the one responsible but it started happening after i installed two programs and i uninstalled them after it started happening. I uninstalled Visual Task Switcher first but on the next day it turned off again, then i unsinstalled SetCpu and it hasn't happened again - maybe some wrong profile settings but i didn't feel like experimenting
I had this issue once too in about 40 days.
I was reading an sms and then i turned into standby and put it in my pocket. Later, maybe 40 minutes i came home and my phone was completely off. I do not remember if i had to take out the battery before to get it on again.
I was wondering why it happened. Maybe it was caused by an app i had opened. Battery still was at 40%.
But since it only occured once in 40 days i doesn´t bother me.
Interesting you mention this as it just happened to me today for the first time. I took it out of my pocket and wtf? The phone was off. Very strange... Using the i9000 on the stock Eclair rom.
Should send back for warranty
Sent from my GT-I9000 using XDA App
software clash?
Well the phone suddenly switched off for me, but this time I turned off APPBRAIN and so far so good.
In fact, I came across an app called NoLED and since it kind of keeps ht phone on, while I have it on my desk, I'm able to be notified of stuff and so far with that, the phone hasnt' shut off.
I'm still experimenting with what works, but try turning off AppBrain and see if you still have the random shut off issue....
i use app brain all the time to keep my apps in sync
not the cause of the problem, that's for sure
my phone can last a whole day even with app brain running
OP, do you have MSN Talk installed on your phone? I have this same problem, seems to happen more when I am running MSN talk in a low signal area.
«try a new sim card. «Could be faulty. «i am on my 3rd phone and all of them had this same problem. «i bought a new sim card 4 days ago, and hasnt happened since. «but then again, this problem usually happens to me once every 3rd-5th day anyways, so i dont know if i am in the clear yet.
Me too, shutdown everyday
Hi guys
After upgrade OS to I9000ZSJG4, Phone random shutdown everyday.
Yep still shuts down
Tried keeping AppBrain off, still shuts down.
Used NoLED so the screen kind of stays on, still shuts off..
So far shut off on me after 40 hrs... this is really stupid.
I am this close to taking it back, but I genuinely think it's a software issue than a hardware issue...sigh
Anyone have any luck figuring this out?
Same problem no solution yet
Hi
I too have the same problem, haven't found any solution yet.
The temperature etc is all good, there is no pattern in shutdown issues.
I have tried factory reset and no new application, it still shut down while using in built browser.
I had the same thing happen to me while skiing in Whistler last weekend. It died twice. I attributed it to the cold. I normally use a 3000mah battery up there, but left it back the house that day. Afterwards while charging in the car and even charging it at home it died prematurely again. It was the eBay aftermarket variety 1500mah knock off. I have since changed back to the Samsung OEM battery. I haven't had an issue with it since. My assumption is that the knock offs in my case cannot handle the heat cycles of charging and then the cold as well as the original. Or they have a limited lifespan, well below OEM specs. I am now only using the 3000mah battery on the weekends to hedge my bet on the quality of manufacture, as it seems to be from the same factory as the 1500.
I've been trying hard to avoid the Epic update, since my phone was working great. I was getting almost 20 hours battery before being asked to charge, using about 30 minutes phone calls, 1 hour "display on" time, bluetooth/wifi off, GPS only when needed.
The nagging update available message would always pop up, and I'd always tell it to install later.
Somehow, I must have accidentally selected update while getting out of the car today, since I saw the phone installing firmware and then reboot.
After the reboot, my Sprint Hotspot stopped working. Now when I activate it, it turns my 3G radio off. Prior to this, I could activate (and use) Sprint Wifi tethering even though I am not specifically subscribed to it. Now, it still "activates" but shuts down my data connection.
Even worse, when I try to activate 4G, it just hangs the phone. I tried factory resetting, which did not solve the problem. Still no more 4G. Also, I noticed my battery getting really hot, and the smell of smoke inside the case. The battery went from 50% to 9% within a minute!! I don't have any explanation on how the update caused this.....
This update fried my phone! I'm going to try the Odin method back to DG27. If that doesn't work, the phone is going back!
DO NOT UPDATE if you can avoid it!!
that sucks
I'm having a really really hard time believing the ota update had anything to do with anything you described.
Sent from my SPH-D700 using Tapatalk
styckx said:
I'm having a really really hard time believing the ota update had anything to do with anything you described.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Me too, but I don't know what else could have caused it. Just tried Odin, still can't get 4G to work.
I don't think there's much else I can try. The phone just hangs when I enable 4G. Tried factory reset, Odin back to DG27. No luck.
Any ideas?
Dont listen to this guy -- you want the DI07 update on your phone. It has vital improvements to the radio and kernel. It doesn't break 4G or ruin battery life.
it has happened to many of us,including me..i also started a thread in the development forum..i talked to a service rep and they instructed me to do a msl reset,which required a msl code the give and no luck..this happened to me last week.since then i swapped my phone for another unit an was weary of updaing again,but i did and everything works fine now.im guessing a bad batch of phones or bad dowload/install of update ota.return it for another
Sent from my SPH-D700 using XDA App
Before the update, I was getting about 14-15 hours of battery with my average daily use. After the update I'm swapping batteries every 6 or 7 hours. I started tracking power consumption a few days ago with Spare Parts. I flashed back to stock with odin, and installed the DI07 update. The only apps I installed were Battery Indicator Pro and Spare Parts. I noticed right away that the running time was always close to 100%. That means that the phone is not sleeping. Under "Partial Wake usage", Android System is running almost the same amount of time the phone is powered on. It's not spiking the CPU, but running just enough to create a partial wakelock. This behavior is consistent on every boot. Normally, Android System should only keep the system awake about 3 or 4 minutes per hour of uptime at most. I think they botched something in the update.
Tonight I reverted back to DG27 and the problem is now non-existent. I only have one Epic to test, so I'm curious to see if anyone else gets different results. If it's just my Epic, then I will be returning it for another.
Anyone feel like experimenting?
I'm going on 18 hours now since I reverted back to DG27 and I'm still on the same battery. I would be on my third battery right now if I was still running DI07. I don't think I'm gonna be updating till Sprint releases another fix. Other than Media Hub and the loss of battery life, I noticed no changes while running DI07.
Sent from my SPH-D700 using Tapatalk
I'm getting over 18hrs since update. It maybe just like the HTC phone when you flash the rom the battery life goes down for the first few full charges then after that it's fine. Maybe I'm just lucky because I'm not having all the drama you guys and others are having.
infamousjax said:
Dont listen to this guy -- you want the DI07 update on your phone. It has vital improvements to the radio and kernel. It doesn't break 4G or ruin battery life.
Click to expand...
Click to collapse
Any why should we listen to you? Can you describe your source of knowing how this update has "vital improvements" to the radio and kernal? What are the nature of these improvements?
Thanks
-Everyone
Not sure what the particular improvements are... but check your phone info and you will see that the baseband was changed, which means a new radio was implemented. Also, in the release notes it specified that there were some "Qualcomm Updates", and since Qualcomm engineers the radio in our phones, it doesn't take much brain capacity to put 2 and 2 together.
I've updated and have experienced none of these problems. (As I suspect is true of most of the people here.)
infamousjax said:
Dont listen to this guy -- you want the DI07 update on your phone. It has vital improvements to the radio and kernel. It doesn't break 4G or ruin battery life.
Click to expand...
Click to collapse
It ABSOLUTELY ruins battery life. If it doesn't ruin your battery life specifically, then your one lucky sun of gun. It cut my battery life in half. I used to be able to go to 11pm and never even get a battery warning! Now, my phone completely shuts down by late afternoon while I'm still at work. DI07 is a horrible update. I don't know what Samsung/Sprint did, but my screen is dimmer, battery life took a major dump, and the phone does not seem any faster, actually slower if anything. My phone also seems to be hot all the time, even after it's supposedly been asleep for hours. With DG27 it was always felt cool when pulling it out of my holster and not hot like it is now.
Testing...testing
After running DG27 for almost 24 hours with great results, I decided to give the DI07 update another shot. But first I made a Nandroid backup in CWM before I accepted the update. After about two hours on DI07, it was clear the phone was not sleeping again when the screen was off.
So now I'm gonna try another experiment. I've done a system restore from my Nandroid backup to DG27. Except that the Baseband(radio) is still DI07 because Nandroid doesn't touch the radio. I'm thinking that this will tell us if the new radio is the culprit, or if they just botched something in the DI07 ROM.
Dev's, let me know if I'm off base here. I will report as soon as I have any relevant results.
compujock said:
It ABSOLUTELY ruins battery life. If it doesn't ruin your battery life specifically, then your one lucky sun of gun. It cut my battery life in half. I used to be able to go to 11pm and never even get a battery warning! Now, my phone completely shuts down by late afternoon while I'm still at work. DI07 is a horrible update. I don't know what Samsung/Sprint did, but my screen is dimmer, battery life took a major dump, and the phone does not seem any faster, actually slower if anything. My phone also seems to be hot all the time, even after it's supposedly been asleep for hours. With DG27 it was always felt cool when pulling it out of my holster and not hot like it is now.
Click to expand...
Click to collapse
Heres what will help:
Run the root script, delete all sprint bloatware, and keep track of all the services running on your phone. I'm getting 20 hours of battery with heavy usage on the DI07 update.
Also, try the bump charging method which has helped me a lot. Turn the phone on, let it fully charge, unplug, let it fully charge, turn back on.. rinse and repeat. It helps.
The update is not what is causing bad battery life. The screen dimming is part of the auto-brightness setting and/or power saving setting which should be helping the battery more than killing it.
Get System Panel/spare parts or any kind of task manager to MONITOR (not kill) processes running on your phone.
Here's a post from another forum, so I'm not the only person with a dead 4G radio. I believe it was temporally related to the update, but reverting back to DG27 didn't fix it.
Link: http://forum.androidcentral.com/sprint-epic-4g/36985-4g-doesnt-work-after-di07-update.html
"I have been out of town in a non-4G area since applying the DI07 update. Got home earlier today and just went to turn on 4G and it no longer is working!!
When I enable 4G (through the pull-down or the settings menu) now it just says "On..." and then "Unknown..."
Anyone else that has applied the update and lives in a 4G area seeing similar behavior?? I am currently backing up me SMS messages so I can do a hard-reset to see if that will fix it."
infamousjax said:
Heres what will help:
Run the root script, delete all sprint bloatware, and keep track of all the services running on your phone. I'm getting 20 hours of battery with heavy usage on the DI07 update.
Also, try the bump charging method which has helped me a lot. Turn the phone on, let it fully charge, unplug, let it fully charge, turn back on.. rinse and repeat. It helps.
The update is not what is causing bad battery life. The screen dimming is part of the auto-brightness setting and/or power saving setting which should be helping the battery more than killing it.
Get System Panel/spare parts or any kind of task manager to MONITOR (not kill) processes running on your phone.
Click to expand...
Click to collapse
Infamous,
These are all good suggestions for basic power management under normal circumstances, but for some reason this update has introduced an issue that causes the Android System process to prevent the phone from sleeping. Why it's not affecting everyone I don't know. Some people had to take their phones back to the Sprint store after the update because they got so hot and would not cool down unless turned off.
Anyway, if you are getting 20 hours on heavy use, you obviously don't have the bug. But to anyone who thinks they might, you can check using Spare Parts.
First, if you've just rebooted, turn the screen off and let it sit for a few minuets. Open Spare Parts and click Battery history. By default it displays 'Other usage'. If your 'Running' percentage is 100% or close to it, and your 'Screen on' percentage is anything other than your 'Running' percentage, then your phone is not sleeping when the screen is off.
Next change the top tab from 'Other usage' to 'Partial wake usage'. This will show you what is preventing it from sleeping. You can click on whatever is at the top of the list to see its partial wake time. If it's 'Android System', the partial wake time should not be any more than about 1 minute per hour of system uptime. For example, if your phone has only been on for 10 minuets, and 'Android System' has a partial wake time of 2 minutes, you have a problem.
Found more info here.
http://forum.androidcentral.com/sprint-epic-4g/37034-those-batt-issues-after-upgrade.html
This is great info, according to Spare Parts and your info, I have a severe problem. I have just killed DRM
The update went through automatically Sat night, battery has dived at least
50%. Reboot at that time.
Battery History
Total in all Time Since Reboot (2 days)
Running 30.5% 99.7
Screen On 16.7 18.3
I see the problem, don't know if DRM dead will fix, is there anything else I can do?
I am rooted (or at least I was, I stayed stock and added Wireless Tether, it is broken). So not happy there either.
I will charge and check this tomorrow to see what changes or if there are any other suggestions.
Thetwo apps running none stop are I! Agent Service in Android System and GTalkService in Goggle, using over 10 mb ram
Other usage is still almost 100%, Screen time has gone down, but Wifi On is same as Running and I have it turned off every which way I can find as with nothing showing on top bar.
Partial Wakelock: Andoid System is on 113 hrs of25 since boot.
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, 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.