Related
I have searched the forum for an answer and can not find it anywhere so please bare with me if it has been answered previously, it's not easily found.
I have a rooted MyTouch running Cyanogen 4.0.4. I could have sworn in his previous releases, there was an option in the Dev Tools to keep the screen awake while it was plugged in to either USB or charging. Was I imagining this? If not, can someone please tell me where to do this because for the life of me, I can not find it again!
Thanks in advance!
Download Locale from the Android market. It's free and you'll be blown away by the features and ease of use. And it does exactly what you're asking. I don't know if this feature was in previous versions of Cyan's mods but I don't know who wouldn't love Locale!
*Personal tip for ya too, if you d/l locale and use it's other features, use the wifi positioning, not the GPS. The GPS positioning kills my phones battery because it checks your position every 10 minutes with GPS. Wifi is alot less power heavy on the battery. Go get the app and use it, then read my tip again...it'll make alot more sense!*
~*Apollo*~
*Locale, so you know, is location based profiles for sound, brightness, connections like wifi/bluetooth, vibrate, and ringer profiles, and also has power profiles for charging, or when the battery is below 20%, etc.*
yes there is an option. i am using it. it isnt in dev tools. it is in development option in your settings. the same place where you go to turn on usb debugging.
Sorry Slightly off topic but I was wondering if anyone knows of an app to turn the Screen off during a phone call?? I thought The app was "Spare parts" but it wasn't
Any ideas?
Thanks NguyenHuu! I knew I had seen it before and it was driving me nuts not being able to find it! Thanks again!!
Hey guys,
Just updated to the x10 after my samsung galaxy died on me, so far i am rather happy - except for the lack of root, but that will come.
I have noticed many complaints on the forum about battery life, and have experienced the same thing myself. From my experience, i think this looks like the same issue that was faced on a leak of 1.6 for the galaxy - it was referred to as the "No Sleep Bug".
TBH, the name says it all - for some reason, in many builds of android 1.6, phones were not sleeping correctly. There are many theories as to why, from cpu not being allowed to sleep, to permanent communication with google servers.
Despite all these different theories, one thing seemed to fix the problem - turning off all location services. Some people argue that a different carrier build, turning off just 'share with google' under location, turning off just AGPS etc. would fix it, but from my experience, the only real way to fix the issue was to turn off all GPS usage unless you need it. The once you have used it, reboot your phone.
This fix obviously sucks, and a new fix has recently been released by a veritable android-demigod around the Galaxy.
HERE IS A THREAD ABOUT NO SLEEP ON i7500 GALAXY;
(ok, some stupid rule says i can't post links - can a mod help me out?)
HERE IS THE FIX FOR THAT PARTICULAR BUG;
(ok, some stupid rule says i can't post links - can a mod help me out?)
LINKS ARE IN POST #5 - THANKS TO ONDOTEAM (would still be nice to get them in this original post though)
Now, from my experience, no sleep behave exactly the same way on the x10 as it does on the Galaxy;
1) I turn of all location services, and my battery life at least doubles.
2) After said turning off of services, 'spare parts' no longer says 100% running time under battery usage - in fact it can be as low as 10%.
These two factors are identical to my experience with Galaxy. SO; is there any way drakaz's fix can be applied to our X10's? It seems to me that the files he mods are standard Android system files, not sony/samsung specific.
Now i am no developer, so i dont know it this is possible - the first question that comes to mind for me is "do we need root access, or can this be done through developer tools using the android SDK?"
Can anyone help shed anymore light on this?
Seems to work for me. I disabled all location services. Spare Parts went down from 100% to 7.6%.
I'll just have to enable GPS when I need to use it..
Awesome! Glad to hear it has helped.
Let's keep testing this guys - if it does show up to be a big cause, then perhaps the devs around this place can help is figure out a patch for Drakas' mod to make it work with our x10's!
n3man said:
Awesome! Glad to hear it has helped.
Let's keep testing this guys - if it does show up to be a big cause, then perhaps the devs around this place can help is figure out a patch for Drakas' mod to make it work with our x10's!
Click to expand...
Click to collapse
Hello send me a PM with links, I will try to post it
http://androidforums.com/samsung-i7500/61168-no-sleep-has-nothing-do-anything.html
http://androidforums.com/samsung-i7500/78471-no-sleep-bug-fixed-drakaz.html
Links from n3man
No sleep is easy to fix, took me a while to figure it...
Turn your screen brightness from manual to auto, spare parts will now start showing proper running stats, no more 100% running.
The screen is a little dark in auto but it will cure the 100% running.
GPS and location services etc make no difference to my X10i, I am running the 1.6 version unbranded UK handset, the only thing to stop mine running 100% is to put the screen on Auto.
ronnyuk said:
No sleep is easy to fix, took me a while to figure it...
Turn your screen brightness from manual to auto, spare parts will now start showing proper running stats, no more 100% running.
The screen is a little dark in auto but it will cure the 100% running.
GPS and location services etc make no difference to my X10i, I am running the 1.6 version unbranded UK handset, the only thing to stop mine running 100% is to put the screen on Auto.
Click to expand...
Click to collapse
LOL... this is already going the way of the Galaxy thread!
My phone came out of the box with auto-brightness and i never changed that option, yet i still had no sleep.
Drakaz has done some fairly deep digging and is next to certain that it is an artefact of the geolocation bug discussed in the thread in which the problem was fixed.
I can't see "Spare Parts" in About Phone -> Battery Info
tuxStyle said:
I can't see "Spare Parts" in About Phone -> Battery Info
Click to expand...
Click to collapse
Me neither.. I was wondering about that myself!..
Although I'd half assumed that they were referring to the total "up-time" figure which you can see at the bottom of the "about phone"; "Status" screen.. But perhaps not.?
Spare Parts is a standalone Program ...
(i don't know for sure if it is in the market or downloadable as .apk from somewhere here in the forum ...)
Bax
im_iceman said:
Me neither.. I was wondering about that myself!..
Although I'd half assumed that they were referring to the total "up-time" figure which you can see at the bottom of the "about phone"; "Status" screen.. But perhaps not.?
Click to expand...
Click to collapse
You can download it here
Spare parts is indeed available from the market - it is a much more powerful tool for indicating battery usage than the regular android methods. The galaxy stared on 1.5 which had NO indicator of battery usage statistics at all, so we all learned about spare parts very fast.
Perhaps that is why no x10 users have realised about the potential no sleep bug; because so far only the android usage indicators have been used?...
Anyway, hopefully this can help us all understand the way our phones are working better together
n3man said:
Spare parts is indeed available from the market - it is a much more powerful tool for indicating battery usage than the regular android methods. The galaxy stared on 1.5 which had NO indicator of battery usage statistics at all, so we all learned about spare parts very fast.
Perhaps that is why no x10 users have realised about the potential no sleep bug; because so far only the android usage indicators have been used?...
Anyway, hopefully this can help us all understand the way our phones are working better together
Click to expand...
Click to collapse
14% it's mine value for running time, not 100%. By the way thats 30 minutes of 210 in total :S
I'm also experiencing "No sleep bug" after i used GPS. I use Battery Graph to plot my power consumption and after I use GPS, I can clearly see that power consumption is high even if i turn the phone in plane mode.
In addition SE widget, used to turn on/off GPS, seems to not work very well for me. So, to fix the bug, i manually disable GPS in parameter menu and restart my phone. After that power consumption is hardly null (20% in 8h with MP3 on almost all the time).
mimok said:
I'm also experiencing "No sleep bug" after i used GPS. I use Battery Graph to plot my power consumption and after I use GPS, I can clearly see that power consumption is high even if i turn the phone in plane mode.
In addition SE widget, used to turn on/off GPS, seems to not work very well for me. So, to fix the bug, i manually disable GPS in parameter menu and restart my phone. After that power consumption is hardly null (20% in 8h with MP3 on almost all the time).
Click to expand...
Click to collapse
Do you have 3G always on?
My phone has no trouble sleeping.
Gps hasn't really been an issue but I keep it off when not needed.
Here's my solid settings:
1) No auto sync
2) No moxier
3) Gps off
4) Restart after using wireless
As long as it's like this my phone lasts 2 days easily
ondoteam said:
Do you have 3G always on?
Click to expand...
Click to collapse
Yes, but I made a lot of test with and without 3G enabled and 3G seems not to be a problem for me. I think my problem comes from GPS.
ondoteam said:
Do you have 3G always on?
Click to expand...
Click to collapse
3G always on.
n3man said:
LOL... this is already going the way of the Galaxy thread!
My phone came out of the box with auto-brightness and i never changed that option, yet i still had no sleep.
Drakaz has done some fairly deep digging and is next to certain that it is an artefact of the geolocation bug discussed in the thread in which the problem was fixed.
Click to expand...
Click to collapse
I have been playing with mine for a month to work out what caused mine to not go into sleep, I keep GPS wifi etc on 24/7 but in spare parts I was running 100%, after numerous reinstalls and removing everything i chanced on turning on auto screen brightness, now when i unplug my x10 the running sits at the correct level.
No Geolocation bug here
I have this problem with 100% on and off. Sometimes when I check its under control (~10%), other times its at 100%. I have GPS off, no WiFi, auto brightness... don't know why it sometimes just gets stuck at 100% :/
I updated to CM 7.1 RC1 last week and I've noticed a few times where the device has locked up after "going to sleep". Essentially, if I leave it on the coffee table with WiFi on and let the screen turn itself off, it won't respond when I return to it 20-30 minutes later. I have to force reboot via the power button + nook button.
Just curious if anyone else has noticed it or if it's just me. If it's a common issue I'll escalate to the CM folks, if it looks like just me I'll start the long and tedious process of uninstalling apps one by one. =)
I have at least one every day. I figure its just a price I pay. Over all its the best rom I have used.
Sent from my NookColor using XDA Premium App
Only once have I had the issue you described. I leave WiFi on some of the times, but majority of the time I have it off when I am done using it. I know some people have mentioned using Tasker or something similar to turn WiFi off when screen goes off so that it can perhaps be prevented.
EDIT: I don't believe I can link yet on my account, but search General for the post "NC, CM7, Dalingrin OC kernel.. Sleep of Death" and start about post #6.
Thanks bio, that looks like the exact issue I'm experiencing.
For the next guy with this issue: Link to the thread biohazard mentioned
Installing Droid wall has fixed the problem for me and has doubled my battery life
Sent from my NookColor using XDA Premium App
mrkavanagh said:
Installing Droid wall has fixed the problem for me and has doubled my battery life
Click to expand...
Click to collapse
That's a pretty generic statement... what did you blacklist within Droid wall to increase battery life / fix the issue?
I'm facing random freezes when I open an application like tweetdeck or mercury and leave it updating from the internet. After some time, I'm not using it, it just stucks. To get it back to life I have to press for a few seconds the power button to shutdown it and then again to power it on. I have used different nightlies, voltages or governors but it is still here.
Now, I don't have freezes since yesterday that I really reduced the voltages but I'm not sure if my problem is solved.
configuration: 144 nightly 300-1100mhz xlv profile
not sure if anyone has told you that what you describes is called:
Sleep of death.
Felt to be possibly related to wifi being on all the time. In wifi settings, go to advanced change it wifi to off when screen off.
skylar.sutton said:
That's a pretty generic statement... what did you blacklist within Droid wall to increase battery life / fix the issue?
Click to expand...
Click to collapse
I'm sorry. I use the white list feature and only check mark the current application that I want to use and allow to access the internet. It keeps everything else from using background data.
For example right now I selected xda and updated rules.
Sent from my NookColor using XDA Premium App
Phatdawg said:
not sure if anyone has told you that what you describes is called:
Sleep of death.
Felt to be possibly related to wifi being on all the time. In wifi settings, go to advanced change it wifi to off when screen off.
Click to expand...
Click to collapse
It seems that I solved it reducing the voltages. When sod occurs a black screen appears right? I never had sod, only random freezes.
Sent from my Nook Color
Heyo bros so I'm experiencing what I'm afraid might be a problem:
I've been getting watchdog alerts regarding the "Base System" process. It notifies me that the CPU % at the time of the captures range from 40% to 60+%. Coincidence or not, it usually happens when I wake my phone from sleep- not when I unlock it, just when I press the power button. The moment the lock screen pops up, the phone's already vibrating and the watchdog notification is up in the status bar.
Battery life so far is:
9h 22m @ 74%; Phone Idle- 56% | Cell Standby- 22% | Display 17% (40m) | Android OS 3% | Voice calls- 3%
Who knows, maybe this^ looks normal. I just want to be sure.
I've heard talk of 'wakelocks' but I don't know exactly what they are, what might cause them, and how I can track them.
I'm currently running:
Atrix 4G (not 2, just for clarification)
CM7 xB^xN
Baseband reads: N_01.77.30P
Kernel version reads: 2.6.32.39-MB860-GB-Faux123-v0.2.1 [email protected] #14
Build number: GWK74
Totally honest, I don't know if that might be able to help diagnose the problem, but for what it's worth, I want to check two things:
1) I flashed Faux's enhanced stock CM7 kernel, and am pretty sure it took, but does that look to be the proper kernel version? I just want to be sure.
2) While I also flashed the "latest radio" in the CM7 xB^xN thread, I was certain there was an xx.97 radio (vs the x.77 radio that mine appears to currently have). Am I indeed on the latest radio version?
Would it hurt to reflash these two? Could either one, or maybe both, be the cause of this?
It also occurs to me: I've been using SetCPU and have ONE profile set up that forces my CPU to min/max 216/216 when the screen is off. Could that be causing it?
Thanks so much for any and all insight bros. Also, please let me know if there's any more info you might want to help diagnose what the dealio is.
Heyo guys,
I hate to bump this kinda soon, but this is definitely a problem.
It's getting to be that I don't even have to wake the phone up for the Base System to spike. I was woken up a couple times in the middle of the night by notifications saying it was really high.
You guys have any thoughts? I'd really like to get this resolved as CM7 is AWESOME.
Yes, you guessed it- I'm not anal about the fingerprint scanner or webtop. Just a stable and fully functional release.
Thanks for any help bros I really appreciate it.
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
AX-MA said:
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
Click to expand...
Click to collapse
Thanks for the insight bro. For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Looks like a couple of us are having problems then, though. We'd both really appreciate any info, advice, or help.
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
xyrovice said:
For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Click to expand...
Click to collapse
AX-MA said:
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
Click to expand...
Click to collapse
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
WiredPirate said:
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
Click to expand...
Click to collapse
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
xyrovice said:
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
Click to expand...
Click to collapse
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
WiredPirate said:
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
Click to expand...
Click to collapse
Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
Also, is there any reason CM7 would have the minfree set to a default that causes this?
Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Thanks so much for saying this bro. Who knows, this might be the problem.
PS: I just tried this and am going to see if it works. Post #13 is the one that would really sum up my reaction of successful.
Hopefully maybe this helps my other bros.
xyrovice said:
1Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
2Also, is there any reason CM7 would have the minfree set to a default that causes this?
3Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Click to expand...
Click to collapse
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
possible solutionary steps I've taken:
So Update:
I actually ended up checking out my (partial) Wakelocks with betterbatterystats, and I think I may have found a problem (diagnosed with alarmdump.txt from the Alarm Manager):
1) When I first flashed CM7 I thought, "Oh well why not really get comprehensive about keeping apps up to date" and I actually, for every single app, checked the "Automatically update" box in each one's market page. This led to a CATACLYSMIC wakelock that I'm now pretty sure could be the problem.
2)Google talk also seemed to be a little active with the screen off so I unticked the "sign me in auto..." box and made sure I signed out.
Lastly (not related to wakelocks), I checked on my TTS settings (see my last post about that).
Oh also LASTLY lastly I froze the modem fastdormancy manager in TiBU (kinda just for ****s and giggles). That said though, is the consensus on this that it's pretty harmless?
So, other bro who was having a problem, check and see if this might help you at all AYY
WiredPirate said:
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
Click to expand...
Click to collapse
Thanks for posting this. I checked ROM toolbox and it does indeed have the capability. That said, if my aforementioned possible solutions don't work, I'm turning here. Thanks for the info bro.
Watchdog is flagging the "base process" app because IT IS using over 60% of your CPU BUT it is using 60% of your CPU that is running at 216MHZ.
It's your screen off setcpu profile of 216/216, if you bump up the max to 456 the alert will go away. When you have it set as 216/216 Watchdog (I believe) thinks that is the actual max cpu speed and bases its percentages off of that. I got that warning before and after a bit of troubleshooting (actually tried several different things) found that was the problem.
I am not sure but if you "whitelist" a app in watchdog it might ignore it as well. However my alert level was set at 80% and it would still set it off, so I think the higher speed might just be better.
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
nando_pt said:
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
Click to expand...
Click to collapse
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
bigmatty said:
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
Click to expand...
Click to collapse
Thanks for the response anyway.
Is that thread about freezing? My Nexus is not freezing.
Hello! Yes, that is one of the threads Im talking about. I found it to hard to find people who posted with as good of detail as you did, so I had to "latch on" to the biggest group that was vocal about their problems. But mine manifests itsself almost always as sleep of death, and NOT reboot - just like yours. Here are some links:
Google: https://groups.google.com/a/googleproductforums.com/d/msg/mobile/-/GFnACv1nC0MJ
On of the XDA: http://forum.xda-developers.com/showthread.php?t=1998496&page=39
As I say on the Google thread:
My thoughts on the error:
1) The most logical explanation I've heard yet is the memory leak that B has been posting about
2) I think this memory leak/problem can manifest its self as crash, reboot, or sleep of death
Right now I am trying Stock 4.2.2, rooted, using KTmanta kernal. This is the second day Im on a non-stock kernal, too early to post any useful info.
Good luck on this,
bm
---------- Post added at 02:09 PM ---------- Previous post was at 02:05 PM ----------
say, quick question since you are in same boat as me - does your device's serial # start with R32C or R32D?
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
nando_pt said:
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
Click to expand...
Click to collapse
I agree that the inability of this device to reliably stay powered on is a deal breaker, at least in a work scenario.
I actually bought mine "just for games", but have been really concerned about trying to resolve this issue to verify its not a hardware issue and I miss my warranty period. I cant honestly say I think its a harware issue, so I am really trying to find a ROM/Kernal/settings combo that resolves this.
I have a lot of faith in the dev community for ROMs and kernels, but I think its absolutely scandalous and horrible that I have to click past a warning that says 'may void your warranty' to install softare on my device to make it perform AS IT SHOULD HAVE direct from Google.
If not for all these issues I would have NEVER gone custom recovery, root, and new kernel. Im glad this has forced me to do so because Ive loved finally having a justification for "risking" my expensive device, but again that learning experience is NOT what Google is taking $500 payments for here https://play.google.com/store/devices/details?id=nexus_10_32gb so Google should be SHAMED!
Thanks for the info on your serial number, that actually relieves a concern of mine that somehow the 'newer' units werent having this problem. Mine's a C.
bm
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
jamir5 said:
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
Click to expand...
Click to collapse
I hope it stays that way for you. It will take a few more days with the device to know for sure. If the problem comes back it'd be worth noting here for troubleshooting. :good:
I called back the seller, and they will do the return. Really bad situation...
i left my n10 in my house and its idle with 41% on battery i just got home and open the device it consume only 1% without random reboots. hope itll stay this way ill root this and install crom maybe nextweek.
So - now I am 2.5 days into testing 4.2.2 OS with a different kernel. And so far, NO sleep of death! AND I've been using the tablet a lot more than my "minimal use" in my other tests! This of course is the ultimate test - I'm posting/talking about it on the internet so certainly if its going to blow up in my face, now would be the time. But as of right now - it looks like the alternate kernal is better for my device than Google's...
I am using the KTmanta kernel.
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
neatchee said:
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
Click to expand...
Click to collapse
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/clock settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Oh, and the LED flashing does not mean the unit is actually on, you can test that by plugging in a charger before attempting a long (power on) press = if you get instant battery charge indicator your unit was actually off.
bigmatty said:
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/click settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Click to expand...
Click to collapse
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
neatchee said:
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
Click to expand...
Click to collapse
After my two months of trouble shooting I feel strongly that there are two main issues: memory leak and "something to do with power". Likely a software/driver/OS problem on the memory leak like the majority says. BUT - not everyone has the power problems. I think the power problems are hardware related.
Only a couple other users have talked about experiencing the power problems...
If I was going to place a bet, I'd say based on your description of symptoms you too have the power problem. Ask the others in threads you are following if they have the LED thing, I'm guessing they don't.
Rxnelson on these forms does. He's seen it on two physical units. For me, it didn't appear on my second physical unit.
Good luck!!
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Also please note the tip I shared about diagnosing if it's off or on via the charger I posted above, handy trick another user taught me.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
neatchee said:
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Click to expand...
Click to collapse
Not quite what it seems. If the unit was on, plugging in the charger would not instantly,w/out delay, display the powered off charging indicator.
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
neatchee said:
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
Click to expand...
Click to collapse
Yes dude, I understand. Just test what I am saying. When I saw my white gmail led flash, but then couldn't turn on I thought the exact same thing you typed. Then while discussing w/power users someone told me to try that. Next time it happened I tried it, was SHOCKED to see what happened, knew I had a problem (that was not just shell reboot.)
My tablet just started doing this as well. It's never done it before, it started about a week ago. What could be causing this? I just factory reset to see if it'll fix the problem. I'll report back in a few days to see if this fixes the issue.
Sent from my Nexus 10 using xda app-developers app