We are again a CWM supported device. Update ROM mgr.
Ian
sent from other side of that
Ian
sent from other side of that
Anyone have any suggestions on how to get deep sleep? I have never been able to get it with the last two updates. I have tried with and without the wife sod fix.
Sent from my NookColor using xda premium
Sent from my NookColor using xda premium
Well its good that lg has confirmed ics of the optimus black..... in 3rd Quarter
Better late then never,they say
Better late then never,they say
M
Typo. Don't you mean wife sob fix? ;-)
Latest nighlies are too big for sd card
The latest nightlies do not fit on the SD Image that Samiam posted. Does anyone have a solution???
The latest nightlies do not fit on the SD Image that Samiam posted. Does anyone have a solution???
Sam is trying to make an enlarged installer image so that folks won't have that trouble in the future. In the meantime, a temporary solution is to remove some large video files from the zip.
Open the zip with your file manager and go to /system/media/video. There you will find six mp4 files there that are a total of 10MB. Delete them. That will make the zip small enough to fit.
Sent from my Nook Color running ICS and Tapatalk
someone had mentioned easeus partition master. the "home" version is free (you can get it from their site, which really just links to download.com)
i started with a fresh sd card (nothing installed on it), flashed it with the SD image, ejected it, pluged it back it, saw it as "boot". ran easeus and resized it to 203.4mb (its based on the sector size). ran the changes, ejected, plugged back in (for good measure) and then tossed the latest and gapps. put the sd card in my nook, installed, booted into recovery, installed gapps, booted into cm9, changed some settings, installed titanium and updated my apps. all is back to where i was before. i tried "deep sleep" on the 1/27 and it somewhat works, i checked the history in cpuspy and it did it for 19 seconds... but hasnt since. have wifi on during sleep to never...
if anyone has a dumbies step-by-step guide for how to change out the wifi driver with the one that does not sod and allows cm9 to sleep, please post it, i had seen previous posts from ppl saying that worked, but i am unsure for exactly how to do that.
thanks
The modified wifi driver does help with SOD but does nothing with the deep sleep issue.
I posted a zip file that adds the wifi module, the bootanimation rotation fix and the market telephony fix. Place it in your boot partition and boot to the SD recovery. It will install automatically. Look here:
http://forum.xda-developers.com/showthread.php?p=21869655
I've been trying to do this, but I keep getting a Error Code: 4 Disk Error I/O Errror. Not sure how to fix it. I've google'd it a few times but can't find a solution.
I just learned something about ics. I thought I would share it with the group. With CM7, when you wanted to change between installed keyboards, you just long pressed on the page and "input method" popped up. That does not work with ics. If you are using a keyboard and you want to change to another installed one, you drag open the notification area and "select input method" is there. Just select it and choose the keyboard you want.
Sent from my Nook Color running ICS and Tapatalk
Sent from my Nook Color running ICS and Tapatalk
Anyone else having Facebook FC everytime? Idk if its just me or what, but Facebook is not working at all.
Sent from my NookColor using Tapatalk
Sent from my NookColor using Tapatalk
It's fine here. Try clearing data and logging back in.
Sent from my NookColor using xda premium
i used to do that for my wife everytime she used it... its trying to access the gps like it did in cm7; there is a free fake gps in the market that will make it happy. i dont know what its called explicitly.
---------- Post added at 04:15 PM ---------- Previous post was at 04:13 PM ----------
did you try deleting all 4 partitions prior to resizing?
its like starting over from scratch
you might need to load ubuntu (livecd) and completely wipe all partition data from the sd card prior to starting
WARNING backup all your data from the SD CM9 nook install first.
freezing while using browser
i just rooted and installed cm9 on the 27th, using the build from the same day.
everything is going great, except for the two times i have opened the browser.
the nook just freezes, no response at all.
i can't do a battery pull like i can on a phone, what to do? i've had to let it sit and drain the battery overnight.
is there another way to reboot the nook when something like this happens? or is letting the battery drain the only way?
is the browser freezing for others or is it just me? will one of the newer builds from the 28th or 29th fix this issue, or should i just use another browser other than stock?
thanks for any and all help
i just rooted and installed cm9 on the 27th, using the build from the same day.
everything is going great, except for the two times i have opened the browser.
the nook just freezes, no response at all.
i can't do a battery pull like i can on a phone, what to do? i've had to let it sit and drain the battery overnight.
is there another way to reboot the nook when something like this happens? or is letting the battery drain the only way?
is the browser freezing for others or is it just me? will one of the newer builds from the 28th or 29th fix this issue, or should i just use another browser other than stock?
thanks for any and all help
Hi all,
Just a noob question: Is there anyway to set the default landscape mode to be upside down? I use my nook with a B&N Cover, and every time I need to rotate the nook again to turn the screen orientation match with the position of the nook in the cover.
Just a noob question: Is there anyway to set the default landscape mode to be upside down? I use my nook with a B&N Cover, and every time I need to rotate the nook again to turn the screen orientation match with the position of the nook in the cover.
I learned another new trick for SD installations of CM9. Before I tell you what it is, I need to explain some things. It has to do with dalvik cache.
Dalvik cache is an area on your nook that helps the operating system open and run applications. The system copies information from the application's apk package and puts it in the dalvik cache for its own use when opening and running that application. It speeds up the system by having it available. The dalvik cache is not in a single location like many believe. It is actually in two locations. The cache for most of your system applications is located in the cache partition of emmc under /cache/dalvik-cache. The cache for all your installed applications are stored in the data partition under /data/dalvik-cache. The operating system keeps track of these and when a new application is installed or a system application changes (like when flashing a new nightly), the system updates the dalvik cache files. It does this when it boots. You may have noticed that sometimes CM7 took longer to boot than other times. And now with CM9 you may see a message that says "Optimizing Applications" as part of the boot. It is updating the dalvik cache. Often it is recommended that you wipe dalvik cache when you install a new nightly. This is to force creation of all new fresh cache files when it boots.
Normally this works all seamlessly and smoothly. But the introduction of SD installs has caused a wrinkle. When Verygreen created the script to make it possible to run a ROM off of an SD, he had it create new partitions on the SD. It has /boot, /system, /data and /sdcard (for media). The new ROM shares the /cache on emmc with the ROM on emmc. That is the problem. Each time either the emmc ROM or the SD ROM boots, the system looks at the dalvik cache on /cache and updates it if necessary. Sometimes the systems are fighting each other. When emmc boots, it sees cache files that don't match its system files, so it overwrites them so they do match. It then runs fine. The next time the SD ROM boots, it does the same thing. This is not a problem of things not running properly, because they do. The problem is the boot time for each system. Each time you switch between the systems, the cache is rebuilt.
There is a solution that works for CM9. You can add a setting in CM9 that tells it to write ALL of its dalvik cache files to /data. That way it is not sharing the cache with another ROM. Boot times are dramatically reduced.
Just add this line to local.prop in /data on the CM9 install.
dalvik.vm.dexopt-data-only=1
If you do not have a local.prop file on your system, create it with a text editor and put this line in it. Be sure to change the permissions of the file as I explained a few posts back.
This works whether CM9 is on emmc or SD, but is not necessary unless you are running one system on emmc and one on SD.
I have been running mine this way for a couple of days. I have noticed no difference in performance and boot times are significantly reduced.
EDIT: This works for CM7 also. I have my CM7 on emmc set to use all /data and my CM9 on SD set to use all /data. No dalvik cache files are written to /cache at all. There is no chance of tangling the files at all.
Dalvik cache is an area on your nook that helps the operating system open and run applications. The system copies information from the application's apk package and puts it in the dalvik cache for its own use when opening and running that application. It speeds up the system by having it available. The dalvik cache is not in a single location like many believe. It is actually in two locations. The cache for most of your system applications is located in the cache partition of emmc under /cache/dalvik-cache. The cache for all your installed applications are stored in the data partition under /data/dalvik-cache. The operating system keeps track of these and when a new application is installed or a system application changes (like when flashing a new nightly), the system updates the dalvik cache files. It does this when it boots. You may have noticed that sometimes CM7 took longer to boot than other times. And now with CM9 you may see a message that says "Optimizing Applications" as part of the boot. It is updating the dalvik cache. Often it is recommended that you wipe dalvik cache when you install a new nightly. This is to force creation of all new fresh cache files when it boots.
Normally this works all seamlessly and smoothly. But the introduction of SD installs has caused a wrinkle. When Verygreen created the script to make it possible to run a ROM off of an SD, he had it create new partitions on the SD. It has /boot, /system, /data and /sdcard (for media). The new ROM shares the /cache on emmc with the ROM on emmc. That is the problem. Each time either the emmc ROM or the SD ROM boots, the system looks at the dalvik cache on /cache and updates it if necessary. Sometimes the systems are fighting each other. When emmc boots, it sees cache files that don't match its system files, so it overwrites them so they do match. It then runs fine. The next time the SD ROM boots, it does the same thing. This is not a problem of things not running properly, because they do. The problem is the boot time for each system. Each time you switch between the systems, the cache is rebuilt.
There is a solution that works for CM9. You can add a setting in CM9 that tells it to write ALL of its dalvik cache files to /data. That way it is not sharing the cache with another ROM. Boot times are dramatically reduced.
Just add this line to local.prop in /data on the CM9 install.
dalvik.vm.dexopt-data-only=1
If you do not have a local.prop file on your system, create it with a text editor and put this line in it. Be sure to change the permissions of the file as I explained a few posts back.
This works whether CM9 is on emmc or SD, but is not necessary unless you are running one system on emmc and one on SD.
I have been running mine this way for a couple of days. I have noticed no difference in performance and boot times are significantly reduced.
EDIT: This works for CM7 also. I have my CM7 on emmc set to use all /data and my CM9 on SD set to use all /data. No dalvik cache files are written to /cache at all. There is no chance of tangling the files at all.
Last edited:
I havent had any issues but if your having those old pains,just switch to friendcaster, I like its ui on ics and its a bit more customizable, GPS tether would get wonkey and start fc'ing itself after a bit, at least it did for me.
Ian
sent from other side of that
Last edited:
Did you try holding the power button until it shutdown that is what I have done in the past when I had freezes? Try Dolphin HD browser.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone