Database Develop

nexus one out of ram?

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

ok so i could use some help... please...

alright it is with great pain that i am writing this, but i really need some help here. for months i've read the forums, searched for answers, asked little individual questions, IMed with people directly for help... and i'm still having trouble.
i rooted my T-Mobile G1 all the way back when cupcake first came out. everything was great. life was grand. everything ruled. i was a happy android fanboy, talking friends into switching to android, talking crap about iphones... the works... but slowly things started getting slower and slower and slower...
the obvious thing was to wipe and reflash. i was constantly just updating to newer cyanogen roms at that point without wiping. so i wiped to the newest cyanogen at the time (can't remember at this point, but just picture it was like a couple months after cupcake). so things were good again for a little bit, but then it started slowing down again, getting FC's, etc. so a friend recommended i switch to superD... i did, and again, everything was great for a while. i consistently upgraded superD roms (sometimes wiping in between sometimes not). eventually i got to the point where i was on the most recent superD release. it lasted about a day before things started slowing down. examples include when i hit home to exit an application and go to the home screen, the whole screen would either turn black or just show my wallpaper for a good 5 seconds before my home screen would appear, or opening the browser would take like 10 seconds. lots of slow down.
so with the help of a friend i decided to completely wipe and reformat/repartition my sd card. i bought titanium backup but i didn't even bother with it, i said to myself, look, you barely use any of the stuff you have right now, how about just start fresh and reinstall things as you need them manually. so i formatted, repartitioned (using amon Ra's recovery, using the menu option that helps you do it automatically). i made sure i had the most recent radio and spl (this was just a couple months ago), and reflashed the most recent superD (i think its 1.11 if i remember correctly)... again, maybe one day of good performance before everything slowed down. this was also about the time when my battery life started becoming an issue. i'm not exaggerating when i say i couldn't make it home without breaking under 20% battery by the end of the day... and i really don't use my phone THAT much. i'd say i'm a little above average on my usage. i'll get into my widgets and apps in a second, but i really don't use that much stuff...
SO... continuing my story (thanks for sticking with me if you're still reading...). when cyanogens 2.1 for the g1 rom came out (5.0.8d/s) i decided it was time for a change. i reformatted AGAIN, repartioned AGAIN, and flashed 5.0.8. basically, i've got the same story going on. slowdowns, poor battery life, etc.
so here i am with my cyanogen 5.0.8 flashed g1. let me tell you about apps and widgets and stuff. right now i have a regular wallpaper (not live), 14 icons between my 5 screens and just the google search and power management widgets. i used to have calwidget, the genie widget (both news and weather), and the setcpu widgets too, but i decided to take them off to see if it would help with performance. zero help. apps that i either know for sure are always running or i think may have some impact are twidroyd, newsrob, craigsnotif (craigslist notifier), and dealdroid. i don't think any other apps are running and/or do automatic updates for content and stuff like that.
i also use cachemate (purchased) regularly to clear my caches. apps2sd is enabled.
i'm not sure what other information you'd need to help me out, but just let me know and i'll try to give you more details.
right now, i've got slow down like almost all the time. things are constantly pausing, slowing down. i feel like i'm back on my t-mobile mda with winmo5 haha. and forget about it with the battery. i left the house with 90% battery this morning. i went to the gym. went home. picked up lunch. came to work. its been like 4 hours. i currently have 19% battery. all i've done is make 2 phone calls, about a dozen text messages and i've sent 2 tweets (about my battery problem haha). i also used google maps once to look up a number. my wifi and gps is off.
so there we go. really guys, please please please. help me out if you can. any help would be appreciated. i'm so sick of this. and i'm stuck in contract until july 2011. so i'm not getting a new phone any time soon. i gotta figure this thing out.
i really appreciate your help.
thanks.
Dave

OH... and PS... forgot to mention that I just got a new battery this week thinking maybe the battery was just getting old and bad. obviously, no such luck.

I had the same issues till I flashed a SuperD, then everything was fine. I just recently flashed the Froyo from Cyanogen and its like it fixed everything and I'm on a brand new device (knock on wood)!
How old is your G1? Do we know if there are issues with the first run out of the factory? Is that even an issue?

i got the g1 last july. so it was already out for a while at that point. it was new from a store though. i suppose there could be something actually wrong with the phone itself, but i don't know. i was thinking of trying the cyanogen froyo but because its not a stable release yet i figured it would be just this bad or worse...

I promise cm5.0.8 has wonderful battery life when no custom apps are installed and not on any network..
so the question is what is your phone doing, and ought it be doing what it is doing.
There are some nice built in tools for this
Applications->running services
And
Applications -> manage applications (check out the filter in the menu from that screen)
You may be surprised by the apps the think they need to constantly have a service running for some painful trivial job the android API has better interfaces for.. if in addition to that you don't need the app uninstall it.
Otherwise experiment with comp cache and lock launcher in memory.

another example, as i was reading this i was on the phone and i just finished the call and hung up, and i was previously in text messages, it took 12 seconds for my text messages to come up. thats just insane...
as for running services:
- GTalkService <--- I use GTalk all the time
- GenieRefresh Service (Restarting) <--- weird considering I disabled this widget, although I'd LIKE to have it back
- Maps FriendsAppWidgetUpdater (Restarting) <--- never used this in my life
- NewsRob UnreadWidgetProvidor (Restarting) <--- never used the widget before (as a matter of fact, you have to pay to use the widget and i have the free version... weird)
-Twidroyd Background Service <--- understandable, I use this constantly
- AKNotepad Snaptic Update (Restarting) <---- umm... I use this all the time but I don't know why a notepad program would need an updater service running... interesting...
- Swype <---- gotta have that
- CM Updater (Restarting) <--- Don't really think that needs to be on all the time. Can easily manually refresh that...
So that's it. I didn't realize this was included now. Very cool. On older roms I had to use task managers which don't seem to really work. I'm going to stop everything except twidroyd, gtalk and swype right now and see how that does... at the bottom it says Avail: 3.2MB+0.00B in 0 ... Other: 55MB in 4 ... While typing that the Maps FriendsAppWidget just popped back up... I'm gonna see if theres a setting...
In the meantime, does any of this give you any ideas? thank you so much for the advice. Also what does (Restarting) mean?

ezterry said:
Otherwise experiment with comp cache and lock launcher in memory.
Click to expand...
Click to collapse
oh and i have compcache not checked and launcher in memory IS checked... i just tried turning on the compcache option... lets see how that goes...

ok so...
now that i know about those things that were running, i stopped all the ones i don't need, and also went into the apps to see if there was any options for turning off automatic updates, background syncing, etc etc for those things... i'm gonna charge my phone while getting ready to go out and then we'll see how it goes throughout the evening. lets see if i make it home with more than 20% battery left (i'll be gone for like 5 hours). if so then we're on to something here still i find it weird that i can't have a few widgets loaded. but whatever, i'll take a smoothly running phone that lasts all day and i just have to click on icons to get to stuff any day... thanks for the help, i'll let you know how its going tomorrow.

the next day
ok so i tried the compcache and keep launcher in memory options last night, messing with both settings. i found that every possible combination became very unstable other than the one i already had (which was compcache off and launcher in memory on). after trying to shut excessive running services like i mentioned yesterday, and also restarting the phone and then shutting them again, i got NO difference in performance OR battery life...
so back to square one... any ideas guys?
thanks so much for any help you can give me. i really really appreciate it.

polarbearmc said:
ok so i tried the compcache and keep launcher in memory options last night, messing with both settings. i found that every possible combination became very unstable other than the one i already had (which was compcache off and launcher in memory on). after trying to shut excessive running services like i mentioned yesterday, and also restarting the phone and then shutting them again, i got NO difference in performance OR battery life...
Click to expand...
Click to collapse
Um... The compcache instability scares me a bit
Compcache has had issues (maybe still does) where the first time you enable it the phone crashes.. but then works fine with Compcache on reboot. Otherwise it really ought no make the phone unstable. (it may or may not speed things up depending on how memory is being used.. usually however it allows 12MB of memory that is rarely used to be compressed, allowing a little more active memory to be utilized) You may want to look into wiping dalvik-cache both on the internal memory and SD card:
Enter console and run (this will restart the phone)
Code:
rm -rf /data/dalvik-cache/*
rm -rf /cache/dalvik-cache/*
rm -rf /sd-ext/dalvik-cache/*
reboot
if you get an error about no files found thats not an issue; but other errors may indicate a problem.
This may help system stability (with or without compcache) .. but won't do anything about the battery life (nor speed unless something was seriously wrong)
-------------------
Unfortunately you will either need to erase all your apps and just run stock CM5 [maybe slowly restore your apps you really need] -- OR -- be very patient and debug whatever application(s) are causing issues on your phone (and maybe complain to the dev for failing to read/understand google's documentation on how to write android applications.. not that some of the google apps haven't quite figured that out until recently)
Thus again the main question is what is running on your phone.. The places I mentioned before allow you to see the services (most of which usually restart if you run the related application again) but not strictly all the details to look for.
Example 1 An widget service is likely holding onto memory starving timer services (those not listed) and swapping out other services (phone/launcher making everything feel slow) At the same time the widget is not very active usually and may not connect to the internet at all; thus may not reduce battery life.
Example 2 An IM client on the other hand may requires a service to keep TCP/IP connections alive, and if not coded properly may be very persistent and cause a slow continual stream of data from your phone requiring a large amount of power to keep the phone on 2G/Edge.
Example 3 A Task killer an kill tasks that re-spawn, or kill a task in use if it doesn't know better causing things to behave in strange ways.. so can killing services/applications from the setting screens btw.. but at least that is a one off by user decision not a automatic operation in the background. Tasks when re-spawned may require more data from the internet thus more power to 2G/Edge
User: Then the one that causes me the most problems: A user that keeps the phone in his/her pocket rather than surfing the web, checking XDA, or continuously checking the battery level is using the device less thus will have longer battery life. (careful to not fall into this trap)
Other Ideas:
SetCPU: set the sleep CPU low in profiles (sleep for me is 245/160)[/*]
Verify End action: Settings->End Button Behavior->Go to sleep[/*]
Set longer periods between polls in applications that poll the net (example twitter every 10 or 20mins.. not 5)[/*]
Larger net transfers on wifi if available (example tell newsrob to sync on wifi only) wifi drains the battery faster than idle, but is much cheaper if larger amounts of data are involved.[/*]
As you can see many things will impact the system. You will need to find the ones eating your battery
Another helpful screen for debugging this may be Settings->Spare Parts->Battery History and Settings->Spare Parts->Usage Statistics
I get between 4h and 12h batter life under semi-normal conditions. 4h = surfing 3g + tappatalk + games.. 12h check email/tweat if i get one.. otherwise stays in my pocket. I've seen my test phone hang out for days on a 2g network without data. (so you can always set your apn type to mms if you just need it to be a phone for many hours.. mms keeps mms support btw)
Ebuddy (and most other MSN/AIM/ect chat clients is frequently one of the biggest problems on my phone.. so if I need more battery those are the first to go.. and whomever it is can poke me on gtalk/txt/or wait
Good luck in your search.. Took me a while to make cm5 work as long as cm4.. most of it was mis-behaving apps that I either know to shut off when I need longer battery life.. or have found replacements for.. or avoid widget functionality if the widget was misconfigured. (

Just a few questions about task killers!

Ok I noticed that most the Task killers arent really for froyo and they state that in the market before you download them; "Froyo doesnt allow devs to kill other apps" or something in that nature. So when ever you use a task killer the apps reappear right back all over again lol. The task management built inside doesnt really do anything phone still lags when all the apps are opening in the backgroud. I tried autokiller but it always just makes your phone super HOT when u crank up the settings and it just drains mad battery. What is the best way to keep my hero running cm6 stable free and smooth. Ive tried everything, I got kernels, setcpu and all the good stuff phone is mad fast, im just trying to figure out how to keep these random apps just having a tea party in the background without me knowing and what method should i take? thanks

From purely personal observation I just don't see that they offer any real benefit. I've tried a couple of them and they really seem to interfere more than help. Just earlier today I was reading about Taskiller, tried it, and immediately felt the phone was lagging and hesitating...if ever so little. I uninstalled it after 1/2 hour and the phone felt much zippier to me.
I'm running CM6 with 9/7 nightly and Darcs #14 kernel. LOVE how well my phone runs now

[Q] need help with multiple issues

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!

Cm7 and random freezing

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"