Guys my Nook is freezing sometimes.
I have to shut down manually with the power button .
I am running right now nightlies 102 with OC 18/06.
But I had this problem and with Phiremod test Rom.
I have install the rom to my internal emmc.
any suggestion?
Isolate the machine..by this run without the OC kernel..or try running a different version of cm..many time on my machine with the nightly updates it does also freeze..I always to back to one that does not freeze..remember you are flashing test builds and they must be treated as such. Also..what speeds are you using...are you running setcpu with at boot option on..which you should not do. It WILL lock up..have you deleted any of the .apk files? Did you clear the cache and dalvic?
life64x said:
Isolate the machine..by this run without the OC kernel..or try running a different version of cm..many time on my machine with the nightly updates it does also freeze..I always to back to one that does not freeze..remember you are flashing test builds and they must be treated as such. Also..what speeds are you using...are you running setcpu with at boot option on..which you should not do. It WILL lock up..have you deleted any of the .apk files? Did you clear the cache and dalvic?
Click to expand...
Click to collapse
I will try to clear the cashe adn dalvin. No I dont use setcpu I know that it will crach with the preinstalled performance settings.
Try a complete flash with a differently nightly..what I mean is wipe all 3 (dalvic, data and cache and try just to boot) some times the nightlife are not very friendly... Build 110 comes to mind...it froze up..had to do a complete restore..frankly...I am getting tired of always flashing theses...my favorite is build 64 with the 1.3 sped kernel. For me this was running just right. I am going to flash 112 later tonight and I want to write a guide to which apks to remove safely for new flashers..I been meaning to write one for awhile..
life64x said:
Try a complete flash with a differently nightly..what I mean is wipe all 3 (dalvic, data and cache and try just to boot) some times the nightlife are not very friendly... Build 110 comes to mind...it froze up..had to do a complete restore..frankly...I am getting tired of always flashing theses...my favorite is build 64 with the 1.3 sped kernel. For me this was running just right. I am going to flash 112 later tonight and I want to write a guide to which apks to remove safely for new flashers..I been meaning to write one for awhile..
Click to expand...
Click to collapse
maybe I will try a new build tonight.
I will report back.
cool......
searius said:
Guys my Nook is freezing sometimes.
I have to shut down manually with the power button .
I am running right now nightlies 102 with OC 18/06.
But I had this problem and with Phiremod test Rom.
I have install the rom to my internal emmc.
any suggestion?
Click to expand...
Click to collapse
Try the new CM7.1 RC release. I always do a clean install whenever i have freezing issues or i feel that nook is running slow.
http://download.cyanogenmod.com/?type=RC&device=encore
To many freezes,
Oh how dare you mock me so.
Power off again.
sounds like SOD...
SOD: http://forum.xda-developers.com/show....php?t=1108964
I have put nightlies 112 now.
For the moment I had not any freeze only one time SOD.
But I have not use too much the Nook those days. I have exams
It doesn't look like Sleep of Death. My NC is not sleeping. Just when I'm in some application (for example, Angry Birds) it becomes extraordinary slow.
I exit the application and it is slow in launcher screen. Looks like frozen, then after several seconds it starts reacting on previous gestures. Then long delay again. Have to power off or reboot Nook.
I saw it yesterday for first time. My Nook was turned off for ~2 weeks. Then I turned it on and updated some apps in market. I noticed Netflix app was in memory. I don't think it loaded automatically at start up before.
I have CM7.0.2 stable, with normal kernel at 925MHz. I installed more than 100 apps, maybe one of them is the reason. It happens quite often, maybe once in half an hour. It can also happen in market during update. Nook is unusable right now.
But my friend has CM7.0.3 and he didn't install that many, I believe he has the same problem.
Will try to wipe stuff and to prevent unnecessary apps from starting with autostarts. Will see how it goes.
With that many apps...make sure you clean out the cache frequently...there are a few apps that do that free on the market....when got got my first android device...a evo I would load everything I could under the sun and delete and installed like crazy....now I have a few trusty apps and I clean out my cache everyday....browsing along will fill up the cache like crazy...
searius said:
I have put nightlies 112 now.
For the moment I had not any freeze only one time SOD.
But I have not use too much the Nook those days. I have exams
Click to expand...
Click to collapse
Glad to see you up and running.....
life64x said:
With that many apps...make sure you clean out the cache frequently...there are a few apps that do that free on the market....when got got my first android device...a evo I would load everything I could under the sun and delete and installed like crazy....now I have a few trusty apps and I clean out my cache everyday....browsing along will fill up the cache like crazy...
Click to expand...
Click to collapse
The only reason to do this kind of nonsense is if you need more space in /data, which is unlikely a problem on the Nook Color.
khaytsus said:
The only reason to do this kind of nonsense is if you need more space in /data, which is unlikely a problem on the Nook Color.
Click to expand...
Click to collapse
I have to disagree...I use firefox on the nook and after a few hours of surfing..it will slow down dramatically...clear my data cache and speed goes up...Also...the more apps loaded the more processess and services runningcin the background which results in overall slowdown...I really don't know why you call it nonesense when it is simple math..the more you have and use the more it is caches and or memory is gutted down with more crap running on it in the background and or swapping in and from cache.
I wiped cache partition and Dalvik cache using CWM recovery. NC looks better now. Didn't freeze so far, but I need to test more.
Thanks
PS. I rarely use browser. It froze while playing some game, or immediately after exiting game, in Zeam launcher.
micksh said:
I wiped cache partition and Dalvik cache using CWM recovery. NC looks better now. Didn't freeze so far, but I need to test more.
Thanks
PS. I rarely use browser. It froze while playing some game, or immediately after exiting game, in Zeam launcher.
Click to expand...
Click to collapse
I don't do the dalvic cache...I am talking about the general cache...currently using 'cache cleaner' from marketplace and works like a charm.
my nook has been freezing a lot lately too. randomly. it doesn't slow down or anything, it just freezes and I have to hard reboot. at least 3 times a day. I am on nightly 116, this has been happening since beta 3.1. using 6/18 kernel. overclocked to 1175.
sometimes it will even freeze right after the bootanimation as soon as it gets to the main screen. Any ideas on what I can do? I have changed the kernel from conservative to ondemand and that didn't help. I lowered the overclock from 1200 to 1175 and that didn't help.
edit: as I was typing this it froze while clicking on the dropbox app. I restarted and it froze as soon as it got to the homescreen. also just cleaned the cache. freed up a lot of memory but it didn't help.
Slow clock down to stock..or flash another build...also just use cm for over clocking if you are using setcpu..uninstall it..I don't know if you are. Try interactive...if still freezing..with setcpu..yes..reinstall..basically try different combos...when you find one that is stable...backup and use that as your daily driver and then experiment with different build.
I cleaned program cache too, with Android Assistant. I guess it's the same. Nook froze badly today. Played Angry Birds, froze completely. Pressed "n" button, exited to launcher, but could not do much in it. Only long-press power button helped.
The thing is it worked well two weeks ago. Then I didn't use it, then I downloaded few free apps from Amazon and ran out of space on eMMC. Then I moved some apps to microSD (I don't think I moved Angry Birds but it looks like it is on SD for some reasons). And my microSD has bad random access times. Can this be the reason?
People in this thread http://forum.xda-developers.com/showthread.php?t=1005633 reported problems when booting OS from slow cards. It probably applies to apps on SD too. I bought Sandisk card now, but it will take time to deliver.
Related
So since the first froyo leak I have been installing a bunch of differant roms just to get a taste of them all. From evil, king, rodriguezstyle, MoDaCo etc. I always wiped in between installs too. But as of lately I noticed my phone stuttering a lot. Becoming unresponsive and getting as low as 40ram free. I even went to a task manager and cancelled everything just to see if I would get my usual 240-260mb ram back but instead I would get a total of 90-130 after killing everything. Its so odd! I am on the new frf83 on stock launcher. Is there anything I can do to reclaim my old reliable phone? Wiping over and over didn't do it for me. Also, my n1 internal memory fluctuates a lot too but I'm not sure if its related. I have received a few low memory messeges.
Shameless bump! Just hoping the right people see this and respond.
If you have any memory available(even 10mb) then it would not stutter, sounds like your CPU is under heavy use.
Th3heretic said:
If you have any memory available(even 10mb) then it would not stutter, sounds like your CPU is under heavy use.
Click to expand...
Click to collapse
Even when I remove all background processes using a task manager I end up with a lot less then what I have available at boot up. Usually 140mb! I'm running pershoots latest kernel @ 1.1ghz. I'm also on the newest setcpu.
Foorgot to mention, browser feels a bit beta and I crash the browser about 5 times a day. Wifi works great and occasionally disconnects for some reason. Phone also rebooted on me but that's super rare. Is there anything I can wipe besides the 2 wipe options in recovery?
sheek360 said:
Foorgot to mention, browser feels a bit beta and I crash the browser about 5 times a day. Wifi works great and occasionally disconnects for some reason. Phone also rebooted on me but that's super rare. Is there anything I can wipe besides the 2 wipe options in recovery?
Click to expand...
Click to collapse
somewhere in between updating FRF50 to 72 to 83, I started having very slow performance despite free RAM.. I bit the bullet and wiped the phone and started over, installed everything back.. all is well and with FRF85B the phone is rocking again
pakraider said:
somewhere in between updating FRF50 to 72 to 83, I started having very slow performance despite free RAM.. I bit the bullet and wiped the phone and started over, installed everything back.. all is well and with FRF85B the phone is rocking again
Click to expand...
Click to collapse
I'm on frf83. Where is frf85b?
I also wiped before frf83
sheek360 said:
I'm on frf83. Where is frf85b?
I also wiped before frf83
Click to expand...
Click to collapse
http://android.clients.google.com/packages/passion/signed-passion-FRF85B-from-FRF83.f62ffd2b.zip
sheek360 said:
I'm on frf83. Where is frf85b?
I also wiped before frf83
Click to expand...
Click to collapse
I can just install via recovery on my rooted n1? Should I wipe?
my nexus has always been this way, even on 2.1. on fresh boot the full RAM is shown. then after a few days it goes down slowly. but if you kill all apps, you never reclaim all that RAM back. only a reboot brings it back. obviously over time background processes are slowly accumulating, ones that you cant see with any task manager. however my phone has never gone into critical slow down from this, meaning it ALWAYS can still keep around 100 mb free by killing stuff, even with this memory leak.
also, the browser in froyo has been updated so that it caches web pages now a lot more. so when you check the browser in system panel, it will show that its using sometimes 75mb of RAM. this isnt a memory leak, it is just caching pages now so that A) it doesnt have to refresh from the network, and B) so when you hit back button it doesnt always have to reload from the network.
this is an issue logged on the google forums, and some employees replied back that they made this change in froyo. check out the response.
http://code.google.com/p/android/issues/detail?id=2171
Anyone heard of an issue where apps in internal storage just start fc'ing then are essentially deleted? I am running cm6 rc2 which I flashed about 6 weeks ago. I haven't had too many issues outside of the bugginess of the ads launcher which I replaced with launcher pro. This afternoon, I try to start up dogcatcher and it immediately force closes, I tried to access the podcast I was looking for through music mod and that fails as well. I thought I might need to reboot, but when I get back into the system two more apps fail as well as the original failed apps not working. Curious, I look in my application list and the apps are mostly gone except for a few apps that show the generic market app icon, which I take to mean corrupted apps. I was able to go into titanium and restore some of the apps to work again, but I have had a pop up stating mytracks has stopped working, but I haven't even started mytracks since the reboot. I guess what I am worried about is If my phone's internal storage is failing? Is it even possible? Any suggestions?
Sent from my Nexus One using XDA App
I had the same thing happen, everytime I rebooted more apps would become corrupt, I was worried that my internal storage was failing, so I wiped everything and started again from scratch, and haven't had a problem since.
When you say start from scratch are you talking about reflashing cm6? I had been holding out since I have been reading about a lot of issues with the 6 stable version.
I formatted the phone, deleting cache and dalvic cache, and then reinstalled. I was using CM6 at the time so reflashed it, did everything by the book to be sure and it has been smooth sailing since.
Only time I have ever had this issue, on the N1 or G1 was after flashing a ROM and not wiping. Sometimes I could get away with it, sometimes not. Wipe and reflash is what I would do.
Hey Thanks guys.
I went ahead and wiped everything and started fresh with cm6 stable.
I am not sure what was going on . I had done a complete wipe and install from stock to rc2 and it worked great for 4-5 weeks. The only thing I could think of was possibly an issue with K-9 mail. One of things I saw happen fairly regularly (3-4 times a week) after rc2 was installed was that K-9 would suddenly just fc. That in and of itself wasn't too weird, but every time it would fc I would get a low space notification right after, where I kew I had 40-50 mbs of space free. Memory leak or something? Dunno.
All weirdness aside, so far CM6 stable is running great...
I've seen this happen when my the /cache filesystem was full. ('App not installed' , FCs etc). Run a 'df' command in a shell to check.
Clearing the cache would be a temporary solution. Moving the /cache to the sd card using DarkTremor Apps2SD is a permanent solution.
I currently have 178 apps.
i was doing my 5k run with my recently updated hero and about a mile into the run pandora radio started skipping and then stopped. when i looked at my phone it was rebooting. i have task manager and killed all the apps before i started and unchecked jogtracker and pandora so i could use them. it didnt last long. the phones screen froze and dimmed then crashed until it finally restarted. is there a reason for the crash. seems to me like a memory problem. i have a two gig card with one pt. five left on it. and the internal memory is at 91mb. it always worked before i rooted and installed cm6. the phone in general is way faster and more responsive since i put cm6 on it but for some reason the two apps running together arent working. thanks for any help
Try removing the task manger reboot into recovery and wipe Dev/ cache and try it then might work good luck
Root-Hack-Mod-Always™
I've tried running with and without various task managers and always wind up uninstalling and reminding myself that I should know better.
I seriously don't think Froyo and these mods need a task killer. If anything, they seem to cludge things up. My phone was running beautifully for two weeks and earlier today I thought I'd try out a different task killer. Mistake. I uninstalled it after 1/2 hour because it just made the phone feel funky.
Try running without for a couple weeks....
jwhistler said:
I've tried running with and without various task managers and always wind up uninstalling and reminding myself that I should know better.
I seriously don't think Froyo and these mods need a task killer. If anything, they seem to cludge things up. My phone was running beautifully for two weeks and earlier today I thought I'd try out a different task killer. Mistake. I uninstalled it after 1/2 hour because it just made the phone feel funky.
Try running without for a couple weeks....
Click to expand...
Click to collapse
+1, CM6 does not need a task killer/manager. The best method is to download AutoKiller (which lets you alter Android's internal memory manager, much more effective than task killers) and change the settings to Strict or Aggressive. Also, two of the biggest problems that create soft reboots that you describe is (a) the VM heap size being too small and (b) CPU speeds being too high. So, steps to take:
1) Uninstall task killer
2) Install AutoKiller and change settings to Aggressive
3) Change SetCPU/Overclock Widget settings to 691 max/595 min with screen on, 480 max/245 min screen off
4) Change VM Heap size (in Cyanogenmod Settings) to 24 MB and reboot
The only other possibility I can think of would be kernel instability. If you flash Decand3nce's #14 Stable kernel found here it is far more stable than the stock kernel and (IMHO) has much better performance than the stock kernel.
These steps should rectify any memory and/or CPU overconsumption problems you are having that could cause the reboots (as well as make your phone much faster, smoother, and more stable). If these steps don't fix it, it most likely is a problem with one of the apps themselves.
Good luck!
thanks for the help.
also on the restart i got this message Sorry the applicating spring updater (process com.sprint.ce.updater) has stopped unexpectedly. please try again. force close. this is probably the cause of all the problems thanks
the changes u pointed out seemed to have fixed the phone so far. thanks so much for the great instructions. u da man.
i noticed a couple times a day the phone reboots. should i back off of some of the settings.
kevinr12345 said:
i noticed a couple times a day the phone reboots. should i back off of some of the settings.
Click to expand...
Click to collapse
Yup, lower the max cpu.
Froyo Hero to the rescue
what is the VM Heap size for what does it change. mine is at 16 right now.
clutch_08 said:
what is the VM Heap size for what does it change. mine is at 16 right now.
Click to expand...
Click to collapse
Its the amount of memory each application can take up maximum. You tend to get smoother running stops with higher vms; I set mine to 24.
Froyo Hero to the rescue
Just bought a NC. Installed CM7 and everything seemed to be fine. Now the NC is locking up after less than a minute of use. I rebooted into CWM and wiped cache and dalvik but its still locking up. I checked to make sure it wasn't overclocked... nope... still locking up.
Any ideas?
I'm running the latest nightly....
Not my first time around CM7. I've got a Droid INC that's been running CM since 6.0 and I'm on the latest nightly with it.
Locking up as in it just quits responding? Of you have to fc?
Are you installing to emmc or sd? If the latter, what card do you have?
Completely locks up and I have to hold the power button. Its installed to emmc. I've got a sandisk 2gb in there which I've swapped.
I reloaded the nightly with a cache and dalvik wipe. When that didn't help I did a reload with a full data/factory reset. I'm still getting lockups though not quite as frequent.
Is bad hardware an option?
Always a possibility.
Was it new or refurbished?
Did you use out as stock before you flashed it with cm7?
Can you reinstall 1.2 stock, if it reinstalls ok, does it lock up also?
Brand new. Ran it for 5 minutes before slapping cm7 on it. I was thinking about putting 1.2 back on it and see what I get.
Well, I think I've figured it out. I had setup a Beautiful Widgets clock on my home. This last wipe and reload I didn't reinstall it.I haven't had a single hang. I tried installing BW again and setting up a clock widget. Within 5 minutes it hung. It was right back where I started locking up every couple minutes. I then uninstalled BW. No more lockups...
Weird......
menos08642 said:
Well, I think I've figured it out. I had setup a Beautiful Widgets clock on my home. This last wipe and reload I didn't reinstall it.I haven't had a single hang. I tried installing BW again and setting up a clock widget. Within 5 minutes it hung. It was right back where I started locking up every couple minutes. I then uninstalled BW. No more lockups...
Weird......
Click to expand...
Click to collapse
Yeah it's a common problem. It's Badly coded app.
Sent from my LG Optimus V using Tapatalk
think i am using fancy widgets, if you want something similar, that to date, i havent had a problem with - other than it uses clock cycles for something that you would think wouldnt take anything (showing the clock!?)
Yeah.. I installed fancy widgets. So far no problems. Don't know what the problem with BW is.
I am using BW on my nook as I type this at work..no problems at all.
Sent from my NookColor using Tapatalk
What build are you running? Are you on a nightly or the RC?
I'm running cm7.1 stable, running off emmc, and every now and then my beautiful NC just locks up, I have it OC to 1.2ghz, I did a search and only end up with results from older nightly threads. Is this a common issue or just me?
PS... I have reflashed and cleared, data,cache, etc..
Thanks
Sent from my NookColor using XDA
Have you always had the issue or did it start recently? I would look at uninstalling any new apps you downloaded prior to the issue starting. There is a good chance you might find a bad app to be your problem.
It wasnt happening before, I tried cm9 with opengl, after I reverted back to cm7(fresh install not nandroid) it started happening, the apps I am running were the same apps I was running before trying cm9(and the freezing problem wasn't happening)
Sent from my HTC Sensation 4G using XDA
Since you are going for a clean install anyway and there is no issue with the CM7 install script did you try the factory reset option or was it just the caches that you cleared? Have you confirmed that you have a good download of the CM7 zip?
Also you might want to try flashing your latest nandroid and make sure that is still running the same as when you created it. If so and you still want to install fresh try it coming off of that one instead of from CM9.
JP
I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.
511pf said:
I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.
Click to expand...
Click to collapse
I do have beautiful widgets installed, let me remove it and see if it helps
Sent from my HTC Sensation 4G using XDA
So did removing BW resolve the random freeze? My wife's NC is doing the exact same thing and she has BW too. But I just installed CM7 on hers last night so not sure if BW is the culprit or not yet.
I've been running CM 7.2.0 RC1 from SD card about a month now, and I've experienced a number of freezes. On April 5, I had two freezes within a few hours, and I started keeping track of the freezes, hoping a pattern would emerge.
From April 5 through April 17, there were a total of eight freezes. I don't know what the uptime was when the first freeze occurred on April 5, but all subsequent freezes occurred with less than two days uptime. During those 13 days, uptime got above two days on two occasions; both times a "Sleep of Death" occurred before uptime reached three days.
Was there a pattern? Yes! Every single freeze occurred while I was using Opera Mobile browser, and browsing these forums at forum.xda-developers.com.
On April 18 I started using Dolphin to browse the xda forums, and there has not been a single freeze so far. (I still use Opera Mobile for other browsing.) Uptime had reached five days when I voluntarily rebooted this morning.
I realize this may not be relevant to the rest of the discussion in this thread, which seems to deal with CM 7.1. Then again, maybe it is. This seemed the logical place to report the observation.
Update: Opera Mobile has updated to version 12.00.ADR-1204201824 on April 25. I'll revert to using Opera Mobile on the xda forums, to see if it still freezes.
My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.
threebeers said:
My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.
Click to expand...
Click to collapse
You really don't gain much and lose a lot by running apps installed to sd. Since everything is automatically on 'sd' with an sd install, those that say they are installed to phone are really still on sd (in /data, which is also on sd). The only reason to install apps to sdcard is if you have so many installed that you have no more room in /data. And with sd installs, usually the /data is made of a generous size. Installing apps to sd slows your system since it has more system overhead to work through.
I know it sounds confusing, but with sd installs, installing to phone means installed to /data which is a partition of your sd. If it says installed to sd, it means it is installed to sdcard, which is another partition of your sd. So no matter where you tell it, it is all on sd and /data is faster because of less system overhead.
For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!
pink401k said:
For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!
Click to expand...
Click to collapse
Came to post the same thing. My nook color will run max OC 1200 but often it will freeze for no reason. After many attempts of uninstalling the many different apps I thought were causing it I started moving the OC lower in small increments and running for a long as possible without a freeze. Finally got down to 975 and haven't had a freeze in days.
Kinda disappointed though since someone got it at 1600 and most run at 1200 and all I can get is less than 1000. I'm probably moving to a Asus Transformer Infinity soon anyways though.
It has been known since the early days of Dalingrin's overclocking kernels that many of the NC's have issues with anything above 1100 MHz and undervolting can create a great deal of instability.
My recommendations are to try 1100 MHz max... and lower voltage .05 mV at each step. I personally never have issues with these settings...
You can then try lowering voltage .05 mV at a time until you start having issues... then increase it back to the last one you had no issues with.
I just leave mine at 1100 and .05 mV lower than the reported "Stock Voltage"