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"
Related
Okay it all started when I updated my original Samsung Galaxy S i9000 running Eclair to Froyo I9000XXJP3 using Samsung Kies. Since then its been really slow and very laggy. I ran around Google for a bit and found some clues about doing a factory reset just after updating to Froyo. To do this I would like to download all apps that can be installed onto and SD card to my SD card so I dont have to re-install all the 111 apps I have after factory reset. It would be pretty cool if someone told me how to backup my contacts, ALL of my settings, my email, basically EVERYTHING on my phone that I would have added on myself after I started using it. Of course I am guessing that the default Samsung Apps that came with the phone and are still available on Froyo will still be available after the factory reset.
My next problem. While someone on these forums tell me how to backup ALL of my data (apps, contacts, media, etc........) onto an SD card before factory resetting I decided I will try to root my phone and apply OneClickLagFix V2.2+. So I used an Windows app called SuperOneClick to root my phone, successfully. After this I installed OneClickLagFix, gave it permission. Then I installed the OneClickLagFix V2.2+, also successfully. After this I tested my phone with Quadrant Benchmark and I got a score of 1956 (which is amazing because I had got 915 before I had applied the LagFix). This is all amazing, but I realised that my battery is draining really fast, because usually if I don't use my phone in the night while sleeping for approx.6-8 hours it drains little to nothing of the battery, but after applying the lag fix I left it on at night (with full battery) while sleeping and when I woke up it had only half of its battery left, so I am guessing OneClickLagFix V2.2+ drains my battery while trying to speed up my phone which is really not helpful (which is why I would like to try to factory reset as a means of speeding up my phone without draining battery).
The third thing, still related to the topic of battery power and speeding up Froyo. I realised that even after applying the OneClickLagFix V2.2+ and gaining a Quadrant mark of 1956, my Galaxy S still did not have the iPhone style smoothness I would expect from the powerful 1Ghz processor in the phone, so please dose anyone have any ways of basically speeding up the phone (with iPhone style smoothness) and not draining battery.
My next thing is not a problem, it's just for fun. I heard that the Galaxy S's CPU can be overclocked to 1.2GHz and 1.6GHz. Could someone post a guide that explained in detail what I have to do to overclock my Galaxy S because I am quite new to hacking my phone and things like that.
So my questions so far:
How to speed up my Froyo phone (make it very fast and smooth like the iOS) without draining too much battery?
How to backup EVERYTHING (like all my downloaded apps, contacts, SMS, etc..) before factory resetting?
How to overclock CPU to 1.2GHz and 1.6GHz?
Hi, I'm still running 2.1 Eclair but maybe i can help a bit. I very much doubt that its OneClickLagFix draining your battery, ive been running it for over 6 months without any problems and so have thousands of others but you could try looking through the OneClickLagFix thread just in case
http://forum.xda-developers.com/showthread.php?t=784691&highlight=oneclicklagfix
Next thing, are you running a task manager or process killer? they can drain the battery while they kill a process and it starts again and gets killed again and starts agai...... you get the idea
I use AutoKiller Memory manager from the market. This works with the built in android process killer and just tweaks it to work better. I find the moderate preset setting to be good but others have suggested going further so you may need to experiment on that.
Also are you sure you didnt install another 'rogue' app? some apps are known to stop the phone from going into sleep mode and that would also cause battery loss at night.
As for backing your things up, AppBrain from the market will take care of your apps if you make an account with them and use your Google log in. It will remember which were installed and put them back when you are ready, I dont think it will save 'in game' data like saves and such though. I cant help with contacts, messages and the rest, sorry.
Lastly, to overclock it you will need to be rooted (as you said you are) and use an app called SetCPU from the market. But be warned, firstly it is guaranteed to cost more battery power overclocking it and the phone will get hotter in use. It will however speed things up a little IF it doesnt blow up LOL. The opposite would be to underclock and save power but then it would run slower and you don't seem to be aiming for that
Good Luck
Thanks!
Thanks for the help, I used App Brain to sync apps and also backed up my apps using Titanium Backup to my SD card, which also backed up the app data. Also, I backed up my contacts by pressing the menu button on the contacts screen and exporting. To backup my messages I used SMSBackup. It all worked well.
I will look into the battery matter, yes, I am using Advanced Task Killer but after reading your response I did not re install it after the factory reset. I will definitely try AutoKiller Memory manager and look into the battery matter further if it doesnt change things.
I tried SetCPU but it only lets me move the sliders upto 1GHz, not higher. Any help is appreciated. And also I just want to try the 1.2GHz, because I am guessing 1.6GHz will REALLY push things past the limit and might mess things up. If things mess up with 1.2GHz I will put it back to 1GHz, and if you had not told me I wouldnt have known about the heating problem, thanks .
How does overclocking work anyway?
Similar issues like whoosh with my phone too.
Pre froyo (no root no lagfix) - app drawer page transition smoothness superb. No lag or stutter in transitions.
Post froyo (pre root and lagfix) - stuttery app drawer page transitions.
Root and voodoo lagfix have not fixed that problem.
- Quadrant ~1500
- formatted internal sd card.
- factory reset post froyo install.
- formatted ext sd card.
- ext sd card sandisk class 4 16gb.
Any solutions to above issues would be greatly appreciated as i would assume would also assist op with their issues.
Cheers
Sent from my GT-I9000 using XDA App
Hey, erm, I thought the Galaxy S has 512MB of RAM but the RAM manager is 300 and something MB of RAM. Maybe thats why it is so slow, because i would expect iPhone-style smoothness from a 1GHz Processor and 512MB of RAM, but looks like it has a cap on. Is there anyway we can fully uncap the RAM usage, so all the 512MB is used? that would be helpful
problems fixed
I used the power of my rooted phone to titanium backup (pro recommended) and then backed up all apps with user data. I factory reset my phone which speeded everything up A BIT. then i discovered Darky's ROM 5.5 (maybe higher by the time some read this post) and installed that following the CLEAN guide written very well (video too) on his forum (CLEAN recommended to upgrade from normal galaxy s firmware to darky's ROM then EASY guide for upgrading from past versions of Darky's ROM).
After following the guide, everything booted up perfectly (amazing gingerbread experience, it feels and looks a lot like it, just missing vibration from gingerbread keyboard and some gingerbread icons, also if darky reads this, maybe you should integrate the new Nexus wallpaper in, but its not that hard to install it yourself either so its fine).
I set the phone up, redownloaded Titanium Backup and it took about half an hour to restore all my apps (with all data). Also note that before I had installed Darky's ROM 5.5 it had taken me 1 and a half hours to restore apps using Titanium Backup so you can see how significantly fast Darky's ROM is. It is amazing!
Well done!
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk
Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.
angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!
angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.
I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.
queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!
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.
My nook is booting up fine, but once it gets to the android interface after a couple seconds or minutes, it just freezes and I can't do anything until I reboot. Has anyone else had any similar issues like this?
If this is a repost, I'm sorry just point me in the right direction as I could not find anything.
Edit: This may be linked to beautiful widgets? I have reflashed CM7 twice now, seems to be linked to that.
Yep, BW will do exactly that. Fancy Widgets is a decent alternative for a large clock widget
I've been having a similar problem after I rerooted and installed phiremod. I can rarely even boot up and have a functional tablet. It almost instantly freezes and must be reboot only to do it again.
reeeaaally pissing me off.
---------- Post added at 05:24 PM ---------- Previous post was at 05:10 PM ----------
after about 10 reboots I was able get it running long enough to uninstall beautiful widgets and after another reboot it seems to have solved the problem. Its a bummer though cause it a good app.
I had the same problems with Beautiful Widgets and the BeWeather widgets. I've read Fancy Widgets work and I'm currently using HD Widgets since it has a 4x4 widget and hasn't given me any problems.
Sent from my PG86100 using xda premium
I'm having a freezing problem, with pure, clean CM7. I can use the Nook for 1-10 minutes, browsing the web, and then it hard freezes. Then if I reboot it, it typically gets stuck in a CM7 bootloop the next 1-2 times I reboot it. Then eventually it will boot successfully again.
I tried switching to running CM7 from the SD card, didn't seem to change anything.
(I definitely do not have Beautiful Widgets, or anything else, installed. I even checked in Manage Applications--none found.)
mondegreen said:
I'm having a freezing problem, with pure, clean CM7. I can use the Nook for 1-10 minutes, browsing the web, and then it hard freezes. Then if I reboot it, it typically gets stuck in a CM7 bootloop the next 1-2 times I reboot it. Then eventually it will boot successfully again.
I tried switching to running CM7 from the SD card, didn't seem to change anything.
(I definitely do not have Beautiful Widgets, or anything else, installed. I even checked in Manage Applications--none found.)
Click to expand...
Click to collapse
Are you overclocked? And I assume since you mention SD card, you normally run from the internal storage? And is this a hard freeze while you're using it, or some time later while the screen is off?
1. Not overclocked. Completely pure, just-installed, CM7 with no changes to default settings. No GApps even.
2. I had the same problem when running from internal. Switched to the SD card to see if that would change anything--it didn't'.
3. Hard freeze occurs while using it.
Thanks!
I also had major freezing w/7.1. I flashed the last nightly (11/16/11) and gaaps.
http://download.cyanogenmod.com/?device=encore
Although freezing might happen once in awhile, it's rare now. I only use one widget (wifi signal). Everything else is pretty much default. No overclocking, live wallpaper, themes, etc.
I've downloaded about 20 apps so far.
Yep, it is caused by beautiful Widgets. I had the same thing happen and I posted on their development forums. I was able to get the startup logs and send them to the developer. Then the response was he could not figure out the bug. The logs clear showed a problem when trying to load the bw, but the bug may have been down deeper the operation system.
Not sure. But bummed none the less.....
Sent from my NookColor using Xparent Green Tapatalk
I was having a similar issue. However I didn't have Beautiful Widgets installed. I solved this by going to the Cyanogen CPU settings. I set minimum to 800mhz, max to 1200mhz and the profile to performance. I also checked the SET ON BOOT (can't recall the exact wording.) After a reboot, I haven't experienced any freezing. Hope this helps you guys.
Thanks.
I will give that a try with a beautiful widget on my home screen. then I will report back on my findings.
Update: nope that did not fix the problem for beautiful Widgets. I made your changes, rebooted, added a super clock widget to my home screen, rebooted, it froze. Thanks for the idea, though.
Sent from my DROID2 using Xparent Green Tapatalk
I've been following this thread as I have been experiencing the same thing, I ridded the nook of BW and it hasn't helped the freezing upon boot issue, even knocked up the min setting to 800. I've reflashed a million times. This came out of no where.
Edit: its getting really annoying. This thing isn't even useful. Never occurs with the ics preview. Only with any cm rom.
Sent from my PG06100 using xda premium
Sorry to hear that. The only time I have really experienced freezing, it was always because of some application. Is there some application that you always install that could be causing the issue. I know at one point it seemed like a certain version of flash would freeze mine, even if it was just installed not being used. Are you using the most recent stable build of cm7?
for now I have switched to ics on my nook, just for fun, I wanted to be able to make my own nightlies so I set that up . Will have to try a beautiful widget on there once I make a backup.
Sent from my DROID2 using Xparent Green Tapatalk
same issue here , mine freezes after an hour of use, ... i have nightly 10252011 with the oc kernel . i just change the cpu setting and will report back if this solves the problem , if not then i guess i will try the stable cm7.
---------- Post added at 04:10 PM ---------- Previous post was at 03:30 PM ----------
carlosraf20 said:
same issue here , mine freezes after an hour of use, ... i have nightly 10252011 with the oc kernel . i just change the cpu setting and will report back if this solves the problem , if not then i guess i will try the stable cm7.
Click to expand...
Click to collapse
reporting back still freezes , i will install cm-7.1.0-encore-signed.zip stable tonight and see what happens, what oc kernel to go with stable cm?
So for what it's worth currently beautiful Widgets seem to work on nook color ICS without freezing it up. But ICS is still in it's infancy.
By the way are you running off an sd card or Emmc? Running off an sd card is not nearly as good and that can cause a lot of freezing. Just throwing that out there.
Sent from my NookColor CM9 pre-alpha using Xparent Green Tapatalk
Thanks for all the replies guys, I found out it was nook tweaks causing the issue. Removed it, and it's been running fine ever since. I'm on Kang cm7
Sent from my PG06100 using xda premium
peanjr said:
Thanks for all the replies guys, I found out it was nook tweaks causing the issue. Removed it, and it's been running fine ever since. I'm on Kang cm7
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
how do u find out it was nook tweaks that was causing this?
Because it always ran just fine, until I installed nook tweaks checked "set on boot" for the cpu settings. I didn't change them, just ticked it. After that, anytime i rebooted, it was a fight to keep it on. So i removed the last thing i put on there, nook tweaks. Its not froze one time and I've rebooted it a whole since then. I reinstalled it but never opened the cpu settings, just edit the audio stuff, no freezes. Kinda wierd.
Sent from my PG06100 using xda premium
I just install cm 7.1 stable and change the kernel to daligrin 603011 and still having freezing issues . I don't want to do it ,but i guess i will have to do a complete wipe and then install cm 7.1 fresh.
Nook Color freezing issues
I too have having freezing issues.
Symptoms: I'll be using my Nook Color with no issues when it suddenly just locks up. No error of any sort on the screen. Screen does not black out. It just locks up. I think everytime it has happened has been after I've transferred several MB (over 5 at least) of data over Wi-Fi.
I'm running CM7.2.0 RC0 KANG build from 11/30/2011 from eMMC.
I'm overclocking to 1200 with the Min CPU set to 800 and the governor set to Performance. I also tried Max CPU at 1100 but that didn't make a difference. I'd had Min CPU at 300 but moved to 800 based on a suggestion found here. Setting the Governor to Ondemand didn't make a difference either.
I do have Nook Tweaks installed but have changed nothing from the defaults and nothing is set to start up at boot time. (I use it to get to USB Host Mode.)
With this build I haven't had any screens of death like I was getting on CM7.1. Just the freeze-ups.
Anyone else seeing a pattern with Wi-Fi?
I've never installed Beautiful Widgets.
Hello Community!!
I am seeing a problem with my Revo, and I'm putting it out here because you guys are good at finding answers.
I am running Gingervolt 1.3 with the blitzkreig kernel installed. I have previously tried Hicks' little ICS responsiveness script.
Here is my problem. Most days after little to moderate use, Phone/text, I have to reboot my phone by either soft reboot (power button) or a hard reboot (battery pull) because nothing at all is responding. By nothing I mean, touch the screen..nothing, open a program...nothing...etc.
It is a slow degrade sometimes where (and my wife has mentioned it using my phone) that the touch screen is really really laggy and non responsive, especially when using a keyboard or even trying to play angry birds.
I have done a full wipe including data, cache, dalvik. I have formatted my internal and removable SD card, I have not used previous backups, instead resorted to downloading programs and installing from scratch.
This is a very frustrating issue. If it was a computer I'd say either the processor was overworking, or the ram was used up. But since we don't use program killers in GB I'm kind of at a loss. And I'm tired of having to wipe my phone every few days just so I have meh performance (and no, I'm not hating on the phone, or the rom or any of the developers, nor do I have any interest in changing phones,etc)
I'm just looking for suggestions/solutions etc. I'm sure I missed something in my troubleshooting steps.
Thanks in advance for those who read through this and try to give a hand. I appreciate it.
Wow. Since you've already gone to extreme measures, I'm at a loss. My suggestion would be to freeze the apps you do install to look for a culprit there. Or, don't install any and see how the phone performs.
I restored a nandroid prior to Google's 10ยข apps promo and my phone is back in fine form. It was lagging badly before that. I was rebooting daily. Now I go for days and the phone's solid.
Sent from my VS910 4G using Tapatalk
I was experiencing similar issues about a week after updating to blitzkrieg 1.0. I restored from backup and it's been stable since. I just installed 2.0 today, so I'm curious to see if it'll have the same effect.
Sent from my VS910 4G using xda premium
I can't say yet whether or not 2.0 has added to or taken away from the response type issues. I did have to do a couple of battery pulls yesterday just to get firefox to do anything. I'm going to uninstall that one. I may, just for S&G's do one more factory wipe and put all the tweaks and mods in place before downloading anything but the most essential programs. I did this phone, but the unresponsiveness sometimes can be a real pain.
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
revo_65 said:
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Currently I have it at 1.7, before when it was really bad, the oc wasn't sticking and I was at 1024, so not overclocked much. I am sure its an app that is causing the problem, but I'm not sure what.
I've never had this type of issue using Blietzkreig or any of the other tweaks so I'd guess you're right in thinking it's an app. Since you've pretty much tried everything else I would say maybe try going back to complete stock then rooting again? That just seems like what I would try if I had tried everything else and nothing worked.
And yeah you definitely don't want to overclock too much because it could definitely damage the hardware of your phone since it's not meant to run at that level. But you said you had it at 1.0ghz so it doesn't seem like that is the problem unless the damage was cause when running at 1.7ghz. I had mine at 1.9 and didn't see any issues except my phone randomly started to vibrate for a while then just restart. It did that twice when i first flashed everything but it seems fine now. I brought it down to 1.0ghz just cuz i'm not really using it now and I don't want it causing any problems with the hardware.
Thanks for the Feedback everyone. I am not sure what the issue is/was/going to be. I think Firefox was a big part of it and I have since removed it. But I am still getting random freezes, almost like the deep sleep while the screen is on. Oh well, maybe I do need to go back to complete stock.