[Q] CPU gets 100% after waking up on nook simple - Nook Touch General

Greetings.
I'm having a trouble with my nook simple touch since I installed nookmanager on it. everytime I put it to sleep (either pressing the power button or letting it to sleep automatically) it wakes up with 100% of CPU process. It causes to my nook to burn it charge very fast.
I haver already installed taskXP and killed every process that could be the problem but it remains on 100%. does anybody have this problem? any ideas about what it could be?

ghostpaladin said:
Greetings.
I'm having a trouble with my nook simple touch since I installed nookmanager on it. everytime I put it to sleep (either pressing the power button or letting it to sleep automatically) it wakes up with 100% of CPU process. It causes to my nook to burn it charge very fast.
I haver already installed taskXP and killed every process that could be the problem but it remains on 100%. does anybody have this problem? any ideas about what it could be?
Click to expand...
Click to collapse
900th post!
I've never had this problem, but I might know just how to fix it. This has helped my battery life a ton, and I'm pretty sure it will fix yours, too.
First, install the attached .apk (not mine). Launch the app, and tap Menu (on the status bar), and then tap "Settings". In the Settings screen, scroll down one page, and check the box labelled "Include deep sleep".
That's all there is to it - enjoy your non-mega-draining battery!

ИΘΘK¡€ said:
900th post!
I've never had this problem, but I might know just how to fix it. This has helped my battery life a ton, and I'm pretty sure it will fix yours, too.
First, install the attached .apk (not mine). Launch the app, and tap Menu (on the status bar), and then tap "Settings". In the Settings screen, scroll down one page, and check the box labelled "Include deep sleep".
That's all there is to it - enjoy your non-mega-draining battery!
P.S. Don't forget to click "Thanks!" :good:
Click to expand...
Click to collapse
thanks for the tip
It worked very well for my nook while is sleeping. It would be a good temporal patch. But the problem about the CPU at 100% still remains.
I was wondering if it could be the re launch app, just guessing. When I turn my nook on, the cpu process is normal (20% or below), the problem begins after putting it to sleep. Have anyone passed throw there?

ghostpaladin said:
thanks for the tip
It worked very well for my nook while is sleeping. It would be a good temporal patch. But the problem about the CPU at 100% still remains.
I was wondering if it could be the re launch app, just guessing. When I turn my nook on, the cpu process is normal (20% or below), the problem begins after putting it to sleep. Have anyone passed throw there?
Click to expand...
Click to collapse
Thank you for jogging my memory - you are actually correct, ReLaunch has been known to eat up CPU usage and battery life.
Try the .apk below - ADW Launcher is what I'm running currently, and I can testify that it takes up nearly 0% of my battery when idle.
Enjoy! :good:

There's a thread somewhere warning about putting the NST "to sleep" consuming a lot of battery power. Better to let it just go to sleep on its own (without the wireless on, of course). Mine sits around for weeks at a time with insignificant power drain. If you have the screensaver set to activate after 5 min it should be fine, 2 min if you must, but I find that interval a bit fussy.
I also use No-Frills CPU Manager to clock the device down to 300 MHz.

nmyshkin said:
There's a thread somewhere warning about putting the NST "to sleep" consuming a lot of battery power. Better to let it just go to sleep on its own (without the wireless on, of course). Mine sits around for weeks at a time with insignificant power drain. If you have the screensaver set to activate after 5 min it should be fine, 2 min if you must, but I find that interval a bit fussy.
I also use No-Frills CPU Manager to clock the device down to 300 MHz.
Click to expand...
Click to collapse
Yes, there is, but in the same thread, @Renate NST and I did a bit of testing and discovered that both methods of putting the Nook to sleep (letting it fall asleep and tapping the power button) actually take up precisely the same amount of battery. For the past few months, I have been putting my Noom to sleep whenever I want it to sleep, and it always wakes up with 0% lost.
What you mentioned is not his problem; I'm confident that ReLaunch is his problem. But thanks! :good:
EDIT - I found the thread. Here it is.

ИΘΘK¡€ said:
Yes, there is, but in the same thread, @Renate NST and I did a bit of testing and discovered that both methods of putting the Nook to sleep (letting it fall asleep and tapping the power button) actually take up precisely the same amount of battery. For the past few months, I have been putting my Noom to sleep whenever I want it to sleep, and it always wakes up with 0% lost.
What you mentioned is not his problem; I'm confident that ReLaunch is his problem. But thanks! :good:
EDIT - I found the thread. Here it is.
Click to expand...
Click to collapse
Hello there again.
I've already tried what you recommended without succeed. My nook still gets 100% CPU proccess after wakin up. no-frills CPU also gets at 1.0 Ghz no matter what configutation is applied.
I just remembered something while I was installing the 174 kernel on my nook. The most of sites tells to install this kernel with the “Apply update from .zip file” option, but I didn't do it that way (because the “choose zip from sdcard” option didn't appear there). Instead, I used the “install from .zip file” option. Is it relevant? Maybe by doing this I uninstalled something important on my nook.

ghostpaladin said:
Hello there again.
I've already tried what you recommended without succeed. My nook still gets 100% CPU proccess after wakin up. no-frills CPU also gets at 1.0 Ghz no matter what configutation is applied.
I just remembered something while I was installing the 174 kernel on my nook. The most of sites tells to install this kernel with the “Apply update from .zip file” option, but I didn't do it that way (because the “choose zip from sdcard” option didn't appear there). Instead, I used the “install from .zip file” option. Is it relevant? Maybe by doing this I uninstalled something important on my nook.
Click to expand...
Click to collapse
Aha! You never mentioned you had an OC kernel installed!
No, the different installation process shouldn't make any impact on this issue. However, the kernel itself is most likely the problem - hopefully you backed up your stock kernel before you flashed the modified one. OC kernels are notorious for eating up device batteries, which is why I'll never use one.
Try reflashing your backed-up stock kernel (by booting Noogie and replacing the uImage on the mounted drive with your backup) and then see how it goes.

ИΘΘK¡€ said:
Aha! You never mentioned you had an OC kernel installed!
No, the different installation process shouldn't make any impact on this issue. However, the kernel itself is most likely the problem - hopefully you backed up your stock kernel before you flashed the modified one. OC kernels are notorious for eating up device batteries, which is why I'll never use one.
Try reflashing your backed-up stock kernel (by booting Noogie and replacing the uImage on the mounted drive with your backup) and then see how it goes.
Click to expand...
Click to collapse
You were right!
Unfortunately, I didn't make a backup, but! I restored my nook to factory reset and that went very good. Then, I only reinstalled nookmanager without installing the modified kernel. Now I can put asleep my nook without waking up with the 100% of CPU process.
Thanks for all the help now I can read in my nook for long hours again.
Merry christmas!

ghostpaladin said:
You were right!
Unfortunately, I didn't make a backup, but! I restored my nook to factory reset and that went very good. Then, I only reinstalled nookmanager without installing the modified kernel. Now I can put asleep my nook without waking up with the 100% of CPU process.
Thanks for all the help now I can read in my nook for long hours again.
Merry christmas!
Click to expand...
Click to collapse
So glad you're all fixed up!
Be sure to post again if you have any more issues and/or need any assistance. :good:
Regards,
Nookie
P.S. Merry Christmas and happy New Year to you, too!

I have been lurking and joined XDA for this problem. I found clearing the Dalvik cache and the data cache made the 100% problem go away. it was reproducible after restoring, rooting, and overclocking.. it seemed to be related to removing stock apps that still had the dex files in the cache. Hopefully that helps someone else with tweaking the NST and seeing 100% CPU.

Related

[13.JAN] standby 60mA - 5 Tips that may help

hey
1.
just use system panel to kill "ALL" processes include system process
then its will be back to normal mA
[well its better then restarting the phone no ?]
2.
Forgetting to disable bt or gps in winmobile
can cause that too
3.
remove with titanium backup CSPeopleSyncService [ thx to fruchtfliege ]
dont like apps that cant be controlled and do what they like
4. same apps make drain more in standby i think cos its not really full standby
5. unmount sdcard when u gonna "put ur phone to sleep"
[this one should help a lot but in testing for 8 hours gonna try it on nites]
that doesn't always work, if you don't isolate the cause then the app will re-open itself at times.
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
fruchtfliege said:
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
Click to expand...
Click to collapse
Might be a nOOb question but how do you kill that CSPeopleSyncService process?
I've been suffering from this 6mA for a couple of minutes and going to 60mA thing. Rebooting 'might' work but I don't want to monitor the consumption every hour.
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative. Some builds have hot rebooting built-in, even easier.
Back in the game in less than 30 seconds, as opposed to the rather lengthy full reboot.
StephanV said:
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative. Some builds have hot rebooting built-in, even easier.
Back in the game in less than 30 seconds, as opposed to the rather lengthy full reboot.
Click to expand...
Click to collapse
LoL just downloaded it. It really says what it does. Click it and the device reboots without a single warning.
lukesan said:
Might be a nOOb question but how do you kill that CSPeopleSyncService process?
I've been suffering from this 6mA for a couple of minutes and going to 60mA thing. Rebooting 'might' work but I don't want to monitor the consumption every hour.
Click to expand...
Click to collapse
the best way is a taskkiller. i'm using systempanel light (included in mdj hd builds), where you can add programs and processes to ignore list. but as i said, changing sync to once a day fixed my problem with 60ma in standby completely! i don't know why
StephanV said:
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative.
Click to expand...
Click to collapse
lukesan said:
LoL just downloaded it. It really says what it does. Click it and the device reboots without a single warning.
Click to expand...
Click to collapse
I think he meant fast reboot. It just kills everything so it's as if you've just rebooted (sort of).
johncmolyneux said:
I think he meant fast reboot. It just kills everything so it's as if you've just rebooted (sort of).
Click to expand...
Click to collapse
No, I mean Quick Reboot. I'm still not convinced this battery drain is caused by certain processes, so Fast Reboot isn't an option imo.
StephanV said:
No, I mean Quick Reboot. I'm still not convinced this battery drain is caused by certain processes, so Fast Reboot isn't an option imo.
Click to expand...
Click to collapse
Fair enough. So you just mean reboot then. Ah well.
No, it's hot rebooting: basically only rebooting Android (it's a little more complex than that).
I used to do regular reboots but they take way longer.
im suffering from this in Desire HD build
wanna kill this permanently without quick reboot (since my ROM is not Deodex) completely.
disabling sync? its all "disabled"
You all might try a different SD card, had the 30ma bug, was 60. Changed micro SD card, re loaded android, now 3-7ma
Sent from my HTC Desire using XDA App
Just saying, I reboot using dev tools: bad behavior-> crash system server. Probably not the cleanest way to do it but it works.
fruchtfliege said:
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
Click to expand...
Click to collapse
Where did 'find' this information?
Without background sync enabled and facebook not even installed it can draw up to 60mA.
I'm not sure it's that single process causing the drain to be honest.
(Please don't take this the wrong way )
For me I think it is after I turn on WiFi and then back off again. It never goes back to 7ish mA. It stays at around 65mA as if WiFi was still on.
I'm using darkstone SuperRAM FroYo v1.5.
strange?
I just found something interesting while using autokiller.
In the processes (i had the high drain again) there was twice the 'android system' mentioned.
I killed one of those entries, and the drain went back to 6mA.
Of course, can't be sure enough so i rebooted the phone, played with it a little and after 10 minutes of standby, i checked again. 54mA.
Again, Autokiller > processes and twice the android system. Killed 1 of them and back to 7mA.
I can't say why this happens, because in older builds (MDJ 2.4 Froyo clean w/ it's own kernel i don't have that issue).
I am no DEV or programmer, but maybe it's something others could test as well? I've been playing with this and trying to find out why this happens ever since the hastarin 8.6 kernel was released and I noticed it only happens with later kernels and mostly on RAM builds.
Just my 2 cents (or local currency my 2 bani )
I found this on other post
DarkStone1337 said:
Lets see how many people will ignore this...
To fix high power drain / usage in standby (60mA or 70mA) disable 'Use wireless networks' in Settings>Location menu. You will now get 7mA or less constantly. I discovered this as the main culprit last night. Also works in other builds.
Click to expand...
Click to collapse
For whatever its worth: On MDJ Froyo HD 4.6 (and earlier builds) I can get 3-6mA in standby but anytime I change the Kernel or framework-res.apk and reboot, standby consumption goes up to around 55 mA all the time. Doesn't matter how many times I reboot.
I've been correcting this by rebooting to WM and recopying all the files in the android folder (CLRCAD.exe, Haret.exe, initrd.gz, rootfs.img, startup.txt, system.etx2, ts-calibration) except zImage (because I'm using a different Kernel than came with the build) and data.img. When I boot back to Android, back to 3-7 mA. I don't know why this works, but it consistantly does. At least for me.
another tip by darkstone:
turn off the "use Wireless" in the Locations Settings help to solve the problem if you are having high drain when you got data/wifi

Freeze after 10-20 seconds of operation on CM7 running on SD

Hello all,
Really new to the android game here and I have a problem with my nook. I looked around the forums and didn't see anything that was just like mine so I thought it wouldn't hurt to ask. I'll give you (whoever is willing to read this and give me some suggestions) as complete of a picture as I can.
I recently bought a refurb nook color. I put the latest stable build of CM7 on a 32gb class 4 sandisk card. Everything was working great. I tweaked the CPU settings (voltage too) and everything was running smooth as butter for the past two or three days. A few days ago I also upgraded the stock OS to 1.4.1.
This morning I woke up to a dead nook. I thought it was mostly charged before bed but I figured I had made a mistake. I plugged in, rebooted, got it to work for 10-20 seconds (VERY shaky performance) and then it froze up and I had to reset. It did this 3 or 4 times in a row until I gave up and booted into stock OS, which is working flawlessly. On the way home I was still having the same problems with the CM7 so I decided to take out the sd card and reinsert and that seemed to do the trick! I was able to use it for a good 1-2 hours and everything was flying. However, I went to plug it in and it froze up again. If I have it plugged in and when I drain the power (by holding the power button) it boots right back up, works for 10-20 seconds, then dies on me again. Stock OS is still working great, but I don't know what to do with CM7.
Was it messing with the CPU settings (though I reset all of them in my 20 second window at some point and that didn't help)? If it was the CPU settings, what are some suggestions for what I should set them to if I just start over? I know that not every chip is the same and thus not all of them will respond well to overclocking.
Was it my upgrade to 1.4.1 on the stock OS (why would that effect CM7)?
Is there any way to fix this? Should I just start wipe the card and start over? Any suggestions on what to or not to do next time?
Thanks in advance for your help!
If you are not using Nook Tweaks, download from market. Set minimum to 300 MHz and maximum to 1200mhz. Set scaling to "on demand". Leave or reset CPU voltage settings to the standard settings. Messing with the voltage settings will result in instability, especially if you do not know what you are doing. If there is a "set on boot" setting, enable it. Reboot.
Upgrading to 1.41 has no effect on the SD cm7 install.
hwong96 said:
If you are not using Nook Tweaks, download from market. Set minimum to 300 MHz and maximum to 1200mhz. Set scaling to "on demand". Leave or reset CPU voltage settings to the standard settings. Messing with the voltage settings will result in instability, especially if you do not know what you are doing. If there is a "set on boot" setting, enable it. Reboot.
Upgrading to 1.41 has no effect on the SD cm7 install.
Click to expand...
Click to collapse
Thanks, but I just tried this and it didn't work. I've been noticing that it's hanging most, if not all times, when giving superuser permission in the background, mostly to "autokiller memory optimizer" app. Can this be doing it?
EDIT: Never mind, still crashes/freezes even when no superuser permissions are being granted and with all of hwong96's suggestions in place. Any other suggestions? Thank you.
Uninstall that app and reboot. If system is stable after reboot you have your answer.

Questions about standby mode

I may have asked this before, but I'm not sure.
My A500 has a custom ROM on it, but its had this problem on multiple roms. I haven't tried on stock yet, but that's probably my next step. Anyways, here are my questions:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
When I first got it, I remember leaving my A500 in standby mode (it should automatically go into standby when you idle, right?) and being able to wake it by hitting the power button almost a day later. Now I can only do it for a few hours and then it won't come out of sleep. I'll have to turn it off by holding the power button down (even though there is no indication that it is turning off), then I can turn it on again. Sometimes my battery will be depleted, apparently indicating that it did not properly go into sleep mode?
chairhome said:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
Click to expand...
Click to collapse
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Moscow Desire said:
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
Click to expand...
Click to collapse
erica_renee said:
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Click to expand...
Click to collapse
Thanks to both of you. I needed reassurance that my tablet wasn't just messed up. I have a warranty on it and was thinking about getting it replaced and seeing how the new one behaved, but I'll try the suggestions. I'll probably try to reload my ROM after formatting and start with just the base apps and add one at a time as you suggested. If that doesn't work, I'll try a different kernel or ROM with a different kernel. I've already tried not using SetCPU to under/overclock, but that didn't work. Thanks again!
Another (relatively rare) issue is that the kernel you're using actually is flawed and fails to wake the GPU after it went to sleep (this may be a lot later than the device itself, depending on background services!). In this case using a different kernel will solve the issue (stock kernel is works).
EDIT: Posted at the same time... By all means try another kernel, this is a known evil with custom ones.
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
OK, before you take your tab back, personally, I wouldn't worry about it.
I have noticed, on some occassions, (yes, I do run stock rooted on occasion), that sometimes, the tab will get what we call the sleep of death. And usually, this may occur over a long period of time. Also, sometimes, I have to hit the pwr button several times, before it wakes.
+1 with the PP on overclocked kernels. This happens with the most recent ones.
Fortunately, System Tuner Pro, will increase MB voltages, so you don't get this.
If it does it again, and you are on stock, try to press the pwr button several times.
cool, thanks. I'll try this today.
chairhome said:
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
Click to expand...
Click to collapse
Mine has never worked on any rom with any configuration. Turning off wifi helps sometimes.

Questions & Thanks for: Dualboot Mirage CM7 / ICS CM9 Image for SDcard [5/4]

Last night I followed the steps on the following thread:
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [5/4] http://forum.xda-developers.com/showthread.php?t=1448186
I was amazed by how easy it was to do it and how nice both CM7 & CM9 worked. Unfortunately CM9 only comes ups in landscape mode at the home level, which is inconvenient, but not terrible and I would like to thank "racks11479" :victory::good: for such a nice a detailed job.
Now, since I'm new to this forum. I'm a bit confuse about a few things and if someone could help me I would really appreciate it. Sorry if some of these questions were asked before. I did search for answers but didn't find it.
1. I follow steps 1 to 8 and everything seems to work. I'm suppose to make all 11 updates?
2. If so, can I do all of them at the same time and then do the gapps?
3. Is this how the flashing are done? : "6-Now power on nook again and this time hold down the button to get to the boot menu and choose SD Boot --> uRecImg/uRecRam. 7-Choose to 'Install zip from SDcard --> Choose zip from SDcard --> Now choose, gapps-GB-20110828-signed-DualbootSD.zip. Once that's completed now choose, gapps-ICS-20111125-2-DualbootSD.zip" Obviusly using the specif zip in each update.
4. What does V6 SuperCharger does? Makes it faster?
5. Does any of these updates helps with the landscape/portrait issue in CM9?
Thanks in advance for the attention and please excuse me if I'm making dumb questions,but I'm no expert
Zue
Also where do I download the following Flashable zips: (there is no dowload link)
Update 5/4/12 Flashable zip for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL
Update 3/26/12 Flashable zip for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL / MIUI GB & ICS
Update 3/6/12 Flashable zip for Mirage CM7.2 / ICS CM9
Update 3/2/12 Flashable zip for Mirage CM7.2 / ICS CM9 / MIUI v2.2.24
ZueKary said:
Last night I followed the steps on the following thread:
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [5/4] http://forum.xda-developers.com/showthread.php?t=1448186
I was amazed by how easy it was to do it and how nice both CM7 & CM9 worked. Unfortunately CM9 only comes ups in landscape mode at the home level, which is inconvenient, but not terrible and I would like to thank "racks11479" :victory::good: for such a nice a detailed job.
Now, since I'm new to this forum. I'm a bit confuse about a few things and if someone could help me I would really appreciate it. Sorry if some of these questions were asked before. I did search for answers but didn't find it.
1. I follow steps 1 to 8 and everything seems to work. I'm suppose to make all 11 updates?
2. If so, can I do all of them at the same time and then do the gapps?
3. Is this how the flashing are done? : "6-Now power on nook again and this time hold down the button to get to the boot menu and choose SD Boot --> uRecImg/uRecRam. 7-Choose to 'Install zip from SDcard --> Choose zip from SDcard --> Now choose, gapps-GB-20110828-signed-DualbootSD.zip. Once that's completed now choose, gapps-ICS-20111125-2-DualbootSD.zip" Obviusly using the specif zip in each update.
4. What does V6 SuperCharger does? Makes it faster?
5. Does any of these updates helps with the landscape/portrait issue in CM9?
Thanks in advance for the attention and please excuse me if I'm making dumb questions,but I'm no expert
Zue
Click to expand...
Click to collapse
Been using Racks dual boot since a long time and definitely it's a good option for anyone who like to try both ICS and also use the more stable CM7.
SO concerning your questions:
1) No need to install all updates. Only the latest one will be fine
2-3) concerning flashing roms and gapps. Just remember this: for every Rom you flash (either the mirage[gb] or the ICS, then you must install corresponding gapps.every time you change Rom, you should do that
4) this script is Supposed to make system a bit faster, but with ICS ROM didn't work always much better and also sometimes creates boot problems. Personally I don't use it
Powered by my IceCold 8.3 DHD
RASTAVIPER said:
Been using Racks dual boot since a long time and definitely it's a good option for anyone who like to try both ICS and also use the more stable CM7.
SO concerning your questions:
1) No need to install all updates. Only the latest one will be fine
2-3) concerning flashing roms and gapps. Just remember this: for every Rom you flash (either the mirage[gb] or the ICS, then you must install corresponding gapps.every time you change Rom, you should do that
4) this script is Supposed to make system a bit faster, but with ICS ROM didn't work always much better and also sometimes creates boot problems. Personally I don't use it
Powered by my IceCold 8.3 DHD
Click to expand...
Click to collapse
Thanks a lot for answering my questions. I was really concern about applying all those updates specially because I can't see the folder sdcard folder in my laptop. I only c the partition with the Barnes and Noble folders. I think I'll just do all over again without botting BN while the card is in.
Also I found out where the updates are downloaded. It was a bit confusing because it don't have a corresponding name, just the date makes sense.
Are the gapps you talking about the 2 gapps that are flashed during the initial installation?
Thanks again
Zue:cyclops:
ZueKary said:
Thanks a lot for answering my questions. I was really concern about applying all those updates specially because I can't see the folder sdcard folder in my laptop. I only c the partition with the Barnes and Noble folders. I think I'll just do all over again without botting BN while the card is in.
Also I found out where the updates are downloaded. It was a bit confusing because it don't have a corresponding name, just the date makes sense.
Are the gapps you talking about the 2 gapps that are flashed during the initial installation?
Thanks again
Zue:cyclops:
Click to expand...
Click to collapse
Yes, you should install appropriate gapps after installing each rom.
Produced by NookColor at ICS AOKP 4.0.4
RASTAVIPER said:
Yes, you should install appropriate gapps after installing each rom.
Produced by NookColor at ICS AOKP 4.0.4
Click to expand...
Click to collapse
Thank you
Thanks (& battery drain issue)
Hi
Just to say this is fantastic OS update to the Nook - I'm a UK user and imported mine specifically with this ROM in mind. Really cool so far!
I do have a slight issue with battery use that's a niggling me. I took the basic Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL ROM (ie the last update on the thread) and had no trouble getting it on my SD card. It all boots and works beautifully with gapps etc.
BUT... running in CM9 I find that unless it's plugged in, battery is draining fast even when it's in 'sleep mode' - ie I usually do a quick click on the side button, or when the device is set to switch display off after 10 mins. A bit of an issue as after a full charge at midnight, in the morning it's about 65% already. Basically with no actually use the device is often dead and needs to charge again.
Am I doing something wrong?? I've spent a few days searching threads and the Nook forums generally before posting here. I'm using Juice Defender and attempting to find a good technical reason. I'm wondering it's a voltage problem between UK and US? Should be using an adapter or just a standard microUSB mobile (cell) phone charger?
Regardless - still want to say a HUGE THANKS to the developers of this particular ROM and the Nook forum users generally. I'm truly amazed at the dedication and effort that's going into this stuff - great bunch of technical know-how made available to beginners. Amazing.
pandachilli said:
Hi
Just to say this is fantastic OS update to the Nook - I'm a UK user and imported mine specifically with this ROM in mind. Really cool so far!
I do have a slight issue with battery use that's a niggling me. I took the basic Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL ROM (ie the last update on the thread) and had no trouble getting it on my SD card. It all boots and works beautifully with gapps etc.
BUT... running in CM9 I find that unless it's plugged in, battery is draining fast even when it's in 'sleep mode' - ie I usually do a quick click on the side button, or when the device is set to switch display off after 10 mins. A bit of an issue as after a full charge at midnight, in the morning it's about 65% already. Basically with no actually use the device is often dead and needs to charge again.
Am I doing something wrong?? I've spent a few days searching threads and the Nook forums generally before posting here. I'm using Juice Defender and attempting to find a good technical reason. I'm wondering it's a voltage problem between UK and US? Should be using an adapter or just a standard microUSB mobile (cell) phone charger?
Regardless - still want to say a HUGE THANKS to the developers of this particular ROM and the Nook forum users generally. I'm truly amazed at the dedication and effort that's going into this stuff - great bunch of technical know-how made available to beginners. Amazing.
Click to expand...
Click to collapse
I'm having the same problem with both CM7 and CM9 and while I love how everything works and looks. I'm sad to say I'm considering going back to stock, which is a real shame, but unless I keep it plugged in, the battery just drains at a dramatic speed. Turning the Wi-Fi off helps, but I use the internet a lot, so that is not an option
battery issues [PARTIAL FIXES]
ZueKary said:
I'm having the same problem with both CM7 and CM9 and while I love how everything works and looks. I'm sad to say I'm considering going back to stock, which is a real shame, but unless I keep it plugged in, the battery just drains at a dramatic speed. Turning the Wi-Fi off helps, but I use the internet a lot, so that is not an option
Click to expand...
Click to collapse
Zuekary
I'm not sure if this is any help to you (or anyone else??) but I've significantly reduced the battery drain in the last day or so by identifying and addressing a few issues (and basically using these forum search to 'thread title' to get a few more ideas).
NB: This does not constitute a perfect resolution, but has helped me regain use of the Nook, when I was beginning to wonder if I might have to sell it
1. BATTERY DRAIN whilst in 'sleep' mode: [PARTIAL FIX]
Upgraded to Juice defender to Pro. This enables: Turn off wifi when screen is off, schedule wifi usage off overnight.
Use Juice defender to dissallow certain apps web access.
Turn off Google Maps - I read this is a battery drain.
Disallow Google Calendar Syncing - yet another culprit apparently.
2. "Sleep of Death / SOD - Nook seems to randomly turn off completely [PARTIAL FIX]
When the Nook turns off and won't start press the power button for 5 seconds or so 3 times in a row, with a slight pause in between.
3. Perpetual Battery Drain [UNRESOLVED]
Return Nook to charge between uses
Reduce Screen brightness to 30%
4. Unsure of issues generally
Install Spare Parts+ and log battery killing apps
Thanks for the suggestion!
I'll try Juice defender.
As of now I'm going to Install just CM7.2 and see how that works:
http://forum.xda-developers.com/showthread.php?t=1000957
pandachilli said:
Zuekary
I'm not sure if this is any help to you (or anyone else??) but I've significantly reduced the battery drain in the last day or so by identifying and addressing a few issues (and basically using these forum search to 'thread title' to get a few more ideas).
NB: This does not constitute a perfect resolution, but has helped me regain use of the Nook, when I was beginning to wonder if I might have to sell it
1. BATTERY DRAIN whilst in 'sleep' mode: [PARTIAL FIX]
Upgraded to Juice defender to Pro. This enables: Turn off wifi when screen is off, schedule wifi usage off overnight.
Use Juice defender to dissallow certain apps web access.
Turn off Google Maps - I read this is a battery drain.
Disallow Google Calendar Syncing - yet another culprit apparently.
2. "Sleep of Death / SOD - Nook seems to randomly turn off completely [PARTIAL FIX]
When the Nook turns off and won't start press the power button for 5 seconds or so 3 times in a row, with a slight pause in between.
3. Perpetual Battery Drain [UNRESOLVED]
Return Nook to charge between uses
Reduce Screen brightness to 30%
4. Unsure of issues generally
Install Spare Parts+ and log battery killing apps
Click to expand...
Click to collapse
ZueKary said:
Thanks for the suggestion!
I'll try Juice defender.
As of now I'm going to Install just CM7.2 and see how that works:
http://forum.xda-developers.com/showthread.php?t=1000957
Click to expand...
Click to collapse
Interesting - if possible let us know how it goes. I'm keen to find a nice stable build, Cm7/CM9 seems like the "best of both" however, if I find out Cm7.2 has a healthier battery experience, I'm likely to switch, or prep an alternative sd just in case!
I'll update back here if I find anything more re: battery on ROM
There is no way to make CM9 to reach the fine battery consumption of CM7.
On the other hand it's not normal to have problems like drainage during sleep.
Install Betterbatterystats and check the Partial Wake locks for possible reasons that create the problem.
Produced by NookColor at ICS AOKP 4.0.4
ingdebso England
RASTAVIPER said:
There is no way to make CM9 to reach the fine battery consumption of CM7.
On the other hand it's not normal to have problems like drainage during sleep.
Install Betterbatterystats and check the Partial Wake locks for possible reasons that create the problem.
Produced by NookColor at ICS AOKP 4.0.4
Click to expand...
Click to collapse
Thanks Rastaviper - going to look into this further, meanwhile if possible can you recommend the most reliable / "vanilla" / commonly used CM7 ROM for SD cards?
I'm nervous about flashing the whole device and installing on the internal HD but still want something with good battery.... possible?
Thanks in advance!
For stable CM7, Mirage kang is the way to go.
Check here :
http://forum.xda-developers.com/showthread.php?t=1344873
Powered by my IceCold 8.6.1 DHD
RASTAVIPER said:
For stable CM7, Mirage kang is the way to go.
Check here :
http://forum.xda-developers.com/showthread.php?t=1344873
Powered by my IceCold 8.6.1 DHD
Click to expand...
Click to collapse
Wish you had posted that before. I installed 7.2 (stable) according to this link: http://taosaur.blogspot.com/2011/09/running-cyanogenmod-7-from-sd-nook.html which is suppose to be based on this post: http://forum.xda-developers.com/show....php?t=1000957 with a newer image file. I did this on Friday and so far everything works wonderfully. Battery life is excellent. I think even better that when I was using the Stock and I have NOT installed any kind of battery saving app.
The only problem I keep having, which I also had with the previous installation is the status bar disappearing randomly. I get an error message "the application statusbar (process com.android.systemui) has stopped unexpectedly)". The only suggestion I have found is to wipe the card which did wipe before installing this version using "EaseUS Partition Master 9.1.1". If you have any suggestion on how to fix that issue I would feel very happy with the performance I have.
Even a tip on how to reopen the status bar without rebooting will be greatly appreciated.
pandachilli said:
Thanks Rastaviper - going to look into this further, meanwhile if possible can you recommend the most reliable / "vanilla" / commonly used CM7 ROM for SD cards?
I'm nervous about flashing the whole device and installing on the internal HD but still want something with good battery.... possible?
Thanks in advance!
Click to expand...
Click to collapse
My current installation is wonderful with battery life. If I can get a fix for the "the application statusbar (process com.android.systemui) has stopped unexpectedly)" error. It will be the closest to perfection I have tested so far and I had tested 3 different installations so far plus I used the stock for nearly a year.
I found the following recommendation in the link posted by RASTAVIPER (thank you!). I'm giving it a try right now. Will report tomorrow how it is working after unchecking "disable full screen".
Recommendations:
1) Regarding the status/notification bar force close issues, I recommend unchecking the "disable full screen" option in the Tablet Tweaks to avoid the status bar crashes. This also improves the app behavior especially movies and games that need full screen.
Click to expand...
Click to collapse
So far working excellent, no status bar crash, battery is not draining any faster than expected, but enableling full screen is annoying in certain application including book readers, so installing the button savior is a must.
ZueKary said:
So far working excellent, no status bar crash, battery is not draining any faster than expected, but enableling full screen is annoying in certain application including book readers, so installing the button savior is a must.
Click to expand...
Click to collapse
Great news - thanks for feeding back.. so you're using "[ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards." ??
RE: battery - no drainage during sleep, random power off's etc?
Going to wipe my SD and start again this evening BUT...can't decide between your recommend ROM or RastsVipers's suggestion of "CM7, Mirage"
Confused.
I experience only 3 percent drain Max overnight. I recommend you use a Task Killer and clean your RAM and turn off the screen when you do not need it. Another handy tip is to use System App Remover and delete the phone.apk to stop battery drain due to cell standby..
satya-1998 said:
I experience only 3 percent drain Max overnight. I recommend you use a Task Killer and clean your RAM and turn off the screen when you do not need it. Another handy tip is to use System App Remover and delete the phone.apk to stop battery drain due to cell standby..
Click to expand...
Click to collapse
I like the handy tip of removing the phone.apk
Now can you tell me where is that thank you button? (Never mind. I found it )

Battery draining after root (NookManager - graphical rooter for 1.2.x and beyond)

Hello,
i was wondering if someone after rooting with the "NookManager - graphical rooter for 1.2.x and beyond" is experiencing a fast battery draining.
Unfortunately i'm a new user so i was not allowed to write in the dev section, so i'm starting a new thread.
In idle (screensaver) i lost 7% overnight.. before rooting, it was around 2% (daily).
My nook fw was 1.2.1, no extra apps installed (i also removed the amazon store) and wifi off.
I already cleared the davlik,
Setcpu says cpu set @ 300mhz and conservative governor (i removed the app after checking)
I deleted all the useless stock apps (like phone.apk, TelephonyProvider...) as suggested in some other posts,
I also tried installing deepsleep and installing the kernel 166 but without improvements...
My guess: is relunch fault (In the processes list seems to use a lot of cpu..), is someone experiencing the same with fw 1.2.1?
Can you suggest me a solution?
feed_back said:
i was wondering if someone after rooting with the "NookManager - graphical rooter for 1.2.x and beyond" is experiencing a fast battery draining.
Unfortunately i'm a new user so i was not allowed to write in the dev section, so i'm starting a new thread.
Click to expand...
Click to collapse
I run 1.2.1 rooted with NookManager with a setup very similar to yours (remove Amazon, B&N apps, no other apps installed except CoolReader and AardDict, and no wifi) and I have excellent battery life (1-2% drop per day, more if I read for extended periods with the Glowlight on. I charge my Nook about once a month, sometimes less). So if you're having battery issues, it's probably not related to NookManager.
I would try the following:
- Charge to 100%
- Reboot
- Use your Nook as you would normally, without connecting it to USB or to a charger. Continue using your Nook until the battery drains completely and will not power on.
- Charge your Nook to 100%
- Reboot
That should help the Nook find you min/max battery points and more accurately calibrate the battery indicator.
I use the same spec's and have no problem with battery. Nook is set to work in FastMode all the time. I just woke him up after a week and it's still working (86% battery).
- FW 1.2.1
- kernel v166
- NookManager
- B&N apk's blocked
- CPU scaling "conservative", 300-1000 MHz
- in NookTouch Mod Manager -> everything checked
1. Relaunch shows invalid CPU load values because it counts it's "load checker" as using CPU. When you don't use this function it's not using additional memory.
Try to connect via adb and check what's using the CPU, using 'top' .
2. My guess would be that you manually set your device to sleep.
If you do that 'settings.apk' starts automatically.
Set 'autosleep' on 2 min and let nook fall asleep without your action.
3. I use 'TaskXP' to kill all apk's right after booting (and before leaving my nook for a longer period of time).
After booting i see "calendar, settings, market, gmail and super manager" running.
One of them might be responsible.
4. One of your apk's may prevent the nook from sleeping. Check options in all suspicious apk's and look for "keep screen on while reading" or something similar.
5. Turn off 'logging' in all apk's
6. check your '/system/app' once again. NookManager may not remove all unnecesary apk's.
My folder contains :
- Accesories, AccountAndSync, AFfileDownload..., AirRuntime, ApplicationsProvider, Browser, Calendar, CalendarProvider, CertInstaller, Cryptoserver, DeviceRegistration, DownloadAdmin, DownloadProvider, DrmProvider, GlobalSearch ,Gmail , GmailProvider, GoogleApps, GoogleBackup..., GoogleCheckin, GoogleContacts, GooglePartnerS..., GoogleSettings, GoogleSubscribe, Gtalkservice, HTMLViewer, LatinIME, MarkerUpdater, MediaProvider, Oobe, PackageInstaller, QuickStartActivity, Settings, SettingsProvider, SysChecksum, UserDictionaryProvider, Vending

Categories

Resources