Freeze after 10-20 seconds of operation on CM7 running on SD - Nook Color Q&A, Help & Troubleshooting

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.

Related

Random HD2 Freezes!

Hi guys. I've been running the Android Stock Desire build from Cotulla for a few months now. Every once in a while I'd get a freeze, but then a battery in, and out would fix the problem (usually within the first try. sometimes I need to do this a few times, but no more than 5 times)
However, since last Friday my phone has been crashing like crazy! Constant crashes at random stages, and even reboots. Removing the battery also didnt guarantee a fix. I think I may have tried it about a hundred times, and Android just crashed at a random point in time during every boot. Eventually it booted, but since then it has crashed again! I figured that perhaps I should try a newer build.
I've decided to try out this build: [08.MAR.2011][CWM]TyphooN CyanogenMod 7 RC2 v2.5.4[2.3.3][A2SD/RAM][rafpigna OC 1.8]. Since I already have radio 2.15.50.14, these are the steps I've taken:
- Flash Task29 (ShaDrac version).
- Flash MAGLDR 1.13
- Flash ClockworkMod Recovery v1.3 135M System
- Flash CM7
Now, even during the various stages before flashing the CM7 rom, I would get freezes during the MAGLDR 1.13 bootscreen, or recovery won't load and I'll get stuck on the GOGOGO screen. Also, copying the zip file over in the MAGLDR mass storage mode won't work, and causes a freeze when I start the copy. Reset, or Battery removal seems to get me to the next step again.
Eventually I've flashed CM7, but now it freezes at the setup stage.
I'm starting to think maybe its not the various Android builds that I'm trying, but perhaps the problem lies somewhere else on the phone? Any ideas? Is my radio perhaps not the best one for the phone (even though its the latest)?
Any help will be much appreciated.
Regards,
XA83
Shameless bump (hope I'm not breaking any rules!)
I realize this post should have probably been under the CM7 thread as well, but I don't have access to that yet due to my low post count...
Could be:
*Wrong CWM Size, check in the rom thread for information
*leftover data, task 29 and reinstall everything
*Corrupted data on SD card, try booting without sd card to see if this is the case.
Thanks for the reply.
I've removed both the SD card and the SIM card. Phone seems to work flawlessly. Boots CM7 without a hitch. Next step I've added the SD card back, and formatted the card from the CM7 settings page. Still perfect.
I've tried it about 5 times now and every time the SIM card is not present, the phone works like a dream. Every time I put the SIM card in, CM7 crashes within the first few seconds of showing the home screen.
Finally, some progress!! Thanks again for the assistance. However, what dis this mean? Could this be related to the actual SIM card I'm using, or does it have to do with the part where it initiates the network connection and possibly the 3g connection?
*Also, just for information, I believe that I do have the correct CMW size. The build indicates "Flash ClockworkMod Recovery v1.3 135M System" which is the one I've flashed.
maybe reflash back to winmo then do evrything all overagain to android
I doubt it's an issue with the phone and its initiating with the sim card. Just replace the sim card
the SAGA continues
Hi Guys,
So since my last posts I have actually managed to get the phone running Typhoon's CM7 and its been working great... for a while.
I'm currently on version 3.0.4 and I still get:
1) Freezes,
2) Reboots,
3) SOD,
4) This happened today: phone cuts mid-phone call and makes a loud buzzing noise until I pull the battery.
I'm thinking more towards hardware problem at the moment, but please let me know what you think, and what I can do to debug the sitaution. Is there perhaps a hardware monitoring app that I can install that logs the whole system every 1 minute that I'll be able to pick something up.
I was also thinking maybe the phone overheats. As explained in my original post, whenever a crash or reboot occurs, it would sometimes not restart the first time round after pulling the battery out and putting it back in. Sometimes I get crashes even during the MAGLDR stage with "fatal hit" and strange things like that. Or even when I boot into CWM sometimes.
Now, to test this overheating, I've experimented with placing my phone in the fridge for 5 minutes after a crash. Thusfar I've done this 3 times, and every time I get a clean boot when I put the cold battery back in and then the phone functions perfectly for a while.
So, overheating, or do I perhaps need another radio? I'm out of ideas.
Any help will be much appreciated. The problem now is that I'm so used to android that I wont be able to go back to winmo or even blackberry
Regards,
XA83
it happens to my phone, and did on my previous HD2.
I've tried every build, task 29, every radio...new sd card....everything.
matt
Are there any apps we can run to test battery temp, cpu temp, cpu voltage or anything like that? I'm pretty effecient at debugging PC hardware issues, but when it comes to my phone I feel like I'm back in the stoneage!
Please help
I have tried over and over and over and over on this kind of issue.
most if the time was some unfinished coppied file which can;t runs properly on roms.
Try to asks ROM developer.
- SD partition : how many partititons?
- SD partitions : what kind of partitions, is it using etc 2/3/4, does it comes with swap etc?
- Installation method : does it needs to clear phone ROM with cwr ? what is the size?
HD2 usually I will go for 400M size
- config.txt settings for SD/NAND.
A proper guide could helps you on in the installations
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Possible solution, Thanks mate,
I changed the CPU speed to 1036 Mhz from stock 998 Mhz speeds and haven't had a Freeze yet,
before that The touch screen would freeze occasionaly when there was a lot of activity like in games such as fruit ninja ....
a Lower CPU speed such as 806 Mhz also seemed to do the trick ...
I don't understand why the Freezes would occur at stock speeds ...
I'll have to give it a few days though ...
Touchscreen Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Update:
Tried that with Interactive Governer, it still freezes on odd occasions, and the battery temp shows 33-36 Degrees Celcius on load when running games ...
i'm beginning to think the freeze is temperature related, as it never freezes while it's cool ...
I'm going to try running it with Smartass governer and see if it makes any difference ...
regards.
Yeah, there's been alot of HD2 owners who've had high-temp related freezes, one guy even went as far as to dissassemble his phone, re-bond the cpu to his mainboard, and add a home-made heat sync to prevent further overheating (successfully)
I just figured changing the cpu freq or governor might reduce cpu load, or increase efficiency, resulting in less overheating. But I feel pretty confident in saying that you guys' freezes are very likely coming from heat. It was even a problem in stock WinMo roms
Sent from my HTC HD2 using XDA App
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Touchscreen Freezes
Dylan Wilson said:
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Click to expand...
Click to collapse
Thats wierd, I'd have thought that such a High Temp as 44 Degrees C would cause more freezes ....
regards.
i'm getting freezes from cyanogenmod android too. i recently restored my ROM to the original 2.13 and believed to have all previous settings related to android deleted.
freezing
i realy didnt undrestand what the exactly means of freeze, my phone freeze after change rom ,i can't use "TyphooN CyanogenMod " becuz my phone freeze at the android logo and it didnt any animation to boot !!!
i have hspl8 , radio 2.15.50 ,Recovery_130M_system_4M_cache[v3.0.2.4],mgldr 13.
i install windows then install android but it steel frezz, i can install just HyperDroid-GBX rom !!
it this problem fix with cpu temp ??
i get it in Refrigerator still feee !!
Temperature
Hi guys. It's definitely the overheating causing all the freezes. I've now succesfully "fixed" my phone 11/11 times by placing it in the freezer and then it works flawlessly for at least a day.
I'll try setCPU to try and lower the CPU frequency from stock and prevent heat issues.
However, ideally I'd like to return the phone to the manufacturer as a defective one! Only problem - how do you convince the 'genius' tech guy that the phone overheats. Last thing I want is to send the phone in, and only get it back after a few months with some response that they found nothing wrong.
Hence, I'm still looking for some sort of app to prove in a way that the overheating is causing crashes... At least in that case they may be more likely to issue a replacement immediately. Any ideas yet?
Regards,
XA83
Just a follow up:
My phone has been sent back to HTC. After a long wait, tech support said they replaced the hardware components - I'm assuming the phone mainboard.
I've reflashed CM7 since, and it hasn't crashed a single time!
Verdict: Random freezes was caused by hardware problems on the phone, and the crashes was most likely due to overheating of the components.
Regards,
XA83

had a problem (possible solution for all)

ok, so I learned the hard way to NEVER over overclock your tablet as in, Do not overclock it to something higher then it can handle, even if you have a kernel that can do it. I was messing with an overclocking program and put the setting on performance. at that point, my transformer froze up and rebooted. every time it turned on, it would say cpu master granted superuser permission and then freeze up within about 3 seconds of unlocking the screen however, I noticed that it checked for the SD card first and mounted it so, thinking quickly as I didn't want to sustain damage to the processor of the transformer, once it turned on and I unlocked it, I promptly removed and reinserted the sd card, pressed the app list, removed then reinserted sd card, found CPU master in the app list, removed and reinserted, then dragged it over to delete. After one reboot, it was all back to normal
I hope this can help others who broke their tablets with OCing too much
Maybe better advice would be to test your tegra's capabilities first before setting SetCPU or other overclocking app to apply settings on boot?
sent from a device using an app
Glad you learned your lesson
Dyskmaster said:
ok, so I learned the hard way to NEVER over overclock your tablet as in, Do not overclock it to something higher then it can handle, even if you have a kernel that can do it. I was messing with an overclocking program and put the setting on performance. at that point, my transformer froze up and rebooted. every time it turned on, it would say cpu master granted superuser permission and then freeze up within about 3 seconds of unlocking the screen however, I noticed that it checked for the SD card first and mounted it so, thinking quickly as I didn't want to sustain damage to the processor of the transformer, once it turned on and I unlocked it, I promptly removed and reinserted the sd card, pressed the app list, removed then reinserted sd card, found CPU master in the app list, removed and reinserted, then dragged it over to delete. After one reboot, it was all back to normal
I hope this can help others who broke their tablets with OCing too much
Click to expand...
Click to collapse
I had the same problem with mine,but like spuniun said,you need to test the capabilities of the cpu first,do a stress test with "Tap Benchmark" or "Setcpu" to find out what it can handle,then set it.I was running mine @ 160000GHZ and it went into a boot loop,i reset it and changed it to 140000GHZ and it hasnt givin me a problem since.
Diablo67 said:
I had the same problem with mine,but like spuniun said,you need to test the capabilities of the cpu first,do a stress test with "Tap Benchmark" or "Setcpu" to find out what it can handle,then set it.I was running mine @ 160000GHZ and it went into a boot loop,i reset it and changed it to 140000GHZ and it hasnt givin me a problem since.
Click to expand...
Click to collapse
Im running at 140000 now and it is still flying! UI lag is only apparent when I set a live wallpaper but I usually don't do that.
Sent from my SGH-i917 using XDA Windows Phone 7 App

[Q] Random lock ups freeze

I keep getting random lockups, at least more than once a day, and sometimes several reboots in a row.
It appears that i can happen almost any time, whether it be at a lock screen, while titanium is asking for root, or opening twitter or facebook, even the gmail app. It simply freezes, and requires me to long press the off button and reboot.
Unfortunately, i can't get adb via usb to work on the nook, so i can't get a reliable logcat.
Is this common? I have had two nook devices so far, tranferred the rom over through nandroid and have had lock ups on both, I am flashing regular cm7 nightlies now (emmc), but it occured using phiremod too.
Help?
I never had one, maybe I'm lucky
Have you tried fixing permissions in clockwork?
Sent from my LG Optimus V using Tapatalk
I am having the same problem. I loaded CM7 to my emmc yesterday and I have had it freeze on me a couple of times now. All have been random. I do have performance set to 1.1 and on demand gov set.
So I can just go to ROM manager to fix permissions? Hopefully that works.
EDIT**
Did not work. Was fine, then I uninstalled market updates, connected to wifi, opened the old market, searched for flash and it froze up. Any ideas?
EDIT 2**
uninstalled beautiful widgets (read that somewhere), so far no lockups (fingers crossed).
i had mine lock-up twice last night
i was in dolphinHD and i had just installed swype beta
i have only had 1 time that it has locked up before then in the last 1-2 months that i have had it.
im blaming swype, since i havent had the problem in the past
perhaps not your problem, if you dont have it installed.
I get lockups pretty regularly. It's irritating. Not sure what the cause is. I thought overclocking had something to do with it but everyone else is overclocked and this problem doesn't seem to be common.
How low do you have the voltage settings in tweaks? Having a voltage just barely too low for your CPU can cause a lot of weirdness. Also, it could be any one of the stepping voltage settings, not necessarily either the min/max frequency.
Folks, playing with the voltage settings in nook tweeks is not for the average user. These settings can really bork your nook. That's why you get a warning when you open those settings.
That being said, I have been running cm7 on eMMC for months and have never had a lockup. I am overclocked to 1200 mHz but have left the voltages alone.(cm7.1 nightly 160).
If you are running on eMMC,try fix permissions first. If that does not help, start looking at the apps you are running to determine if one of them might be the problem. Several people have reported issues running beautiful widgets. There are other apps that can cause issues. If you have good backups of all your apps, try removing apps one at a time. In the process, you might learn something about your system.
Worst case, reinstall cm7, wipe data, cache, and dalvic cache. Start over with a clean system and add your apps (apps only, not apps+data) one at a time. This will ensure that a possibly currupt data set was not causing the issue.
The key to a fast, well functioning nook is to start slowly and ensure each change works well before moving on to the next step.
While it's true I have more time than most to play (retired), my nook can run circles around most competitors but only because I took the time to set it up right the first time and I am not afraid to wipe everything and start over.
Sent from my NookColor using Tapatalk
I fixed permissions some time ago, seemed to help a bit, but i still get the odd lock up or two. I am running Swype and Beautiful widgets(anyone know a good alternative?)
I had been getting irritated by these these random locks up for a while. It seems that uninstalling beautiful widgets fixed the problem for me. I thought it might be that BW was trying to access the GPS, but it still locked up after disabling geo location in BW.
liam.lah said:
I fixed permissions some time ago, seemed to help a bit, but i still get the odd lock up or two. I am running Swype and Beautiful widgets(anyone know a good alternative?)
Click to expand...
Click to collapse
In case you're still interested, BeWeather is a great substitute for BW and FlexT9 in place of Swype.
Also, I had issues with lockups no matter my overclocking and formatting the eMMC and possibly reseating the SD card fixed it.

Nook Color Sudden Shut Down CyanogenMod 10.1

Recently I upgraded my Nook Color from CyanogenMod 7.2 to CyanogenMod 10.1 stable. After that, somehow, it kept shutting down every half a minute or so when in use and when left alone. I did not touch the battery, the CPU is clocked at 300 MHz to 1.1 GHz, screen set to 16 bit mode, GPU untouched. Has anyone else had this problem and is there a way to fix it? Thanks in advance.
Ethan_Kok said:
Recently I upgraded my Nook Color from CyanogenMod 7.2 to CyanogenMod 10.1 stable. After that, somehow, it kept shutting down every half a minute or so when in use and when left alone. I did not touch the battery, the CPU is clocked at 300 MHz to 1.1 GHz, screen set to 16 bit mode, GPU untouched. Has anyone else had this problem and is there a way to fix it? Thanks in advance.
Click to expand...
Click to collapse
I upgraded to the latest stable CM10.1.2 release and have started getting random sleep of deaths (SD install). I've had them while plugged in, not plugged in, with screensaver on, with screensaver off (thought maybe keeping it active would help prevent)... I can't seem to find a pattern. I've tried every nightly since and am still seeing it. I tried rolling back to the first stable release, still there. I'm going to try rolling back from 1100 MHz to 1000, then 800, to see if that helps at all.
I'm a total newb to debugging this thing, but I'm happy to try and pull any logs to post if someone can point me in the right direction (I've looked around before on how to do this but get confused easily). Also, I'd be willing to try a clean install, but don't want to go through the hassle of reinstalling everything again. If there is a quick way to backup programs, I'm all ears.
The good news is, it runs great when it's up. Quite smooth. Pretty awesome stuff.
I believe Titanium Backup should back everything up.....
I have downgraded to CyanogenMod 7.2 as I am very exasperated with this issue, the short battery life and lagginess that the upgrade has brought.

[Q] CPU gets 100% after waking up on nook simple

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.

Categories

Resources