wow, i'll take that as a yes
I'm wondering if anyone knows what nightly build works with Volume+? Thanks again...
The newer kernel helps with SOD but does not eliminate them all. I have found that adding the patched wifi module eliminates even more. So I use both together. You only need to use the module if you are still suffering SODs with the new kernel.
Actually you can. There is a modified CWM recovery (version 3.0.2.8) that can be used with SD installs. It has been modified to read and write to the partitions on the SD. BUT IT CANNOT BE USED TO FLASH NIGHTLIES!! It can flash other install files like the fix boot animation zip, etc., BUT NOT NIGHTLIES. If you try to flash a nightly, it will flash it to emmc, so don't try. However, it can be used to backup and restore your whole SD install (/boot, /system, /data and /cache). It puts the backup files on your SD under clockworkmod/backup. This is what I use it for. You can use it to wipe your SD partitions (/system and /data). And you can clear dalvik-cache and cache. But note, the SD install uses the cache partition on emmc and shares it with emmc so clearing it for SD clears emmc cache too. Never wipe /boot, you will lose the verygreen script and this CWM you just put on your system.so just to get this straight, if i am running cm9 off of my sdcard, can i install clockwork mod recovery and run it off the sdcard? if so, how? right now, i only have the uRecovery
That version does not work with the current nightly build. It asks me to alter the Music Effects properties but there isn't one. I don't know what happen to it. The first nightly had it. But anything after that I don't see the settings...
Actually you can. There is a modified CWM recovery (version 3.0.2.8) that can be used with SD installs.......
BTW, that script that I posted earlier for modifying build.prop on the fly does not work with the Verygreen recovery on SD installs, but it works with the modified CWM recovery I just posted.
I don't think it has any effect on router issues. It was only modified to cut down on SODs. And it's not new. It was modified in October 2011.Does this new wifi module fix the problem with some routers where they have to be in 802.11g only for the NC to connect? My Nook connects fine to my DIR-655 with CM7, but I have to switch it to G-only with CM9.
No. It has been speculated that the problem is caused by the new kernel and library files that were created when opengl was introduced on or around the end of January. If you want it smaller try going for an older nightly. I think the devs have this on their list to fix.The keyboard and a few apps, particularly Opera Mobile, are HUGE on the screen...any way to adjust this back down? I've tried playing around with LCD density but to no avail...
I don't think it has any effect on router issues. It was only modified to cut down on SODs. And it's not new. It was modified in October 2011.
Just skip that step by closing and reopening the app and it will still work
This is in the Volume + app correct. The Nook Tweaks app doesn't work with ics. I just reinstalled Volume + and cleared the app data and it worked fine for meI get a forceclose every time I try to alter the volume sorry This doesn't work.
only thing that bugs me about this is the laggy screen rotation...
This is in the Volume + app correct. The Nook Tweaks app doesn't work with ics. I just reinstalled Volume + and cleared the app data and it worked fine for me
update-encore-20120218-tnp.zip
samiam303's latest nightly plus:
telephony fix
wifi SOD fix
bootani fix
enhanced hosts file
sysctl.conf tweaks
fix_permissions bin
I thought the wifi SOD fix was incorporated into the 109 kernel, which is included in the nightlies.
there have been mixed comments on this; some saying that it was incorporated, and others saying they still use the fix...if its not necessary anymore, i'll take it out of the next one...samiam330, can you weigh in on this?
There was an update to the kernel that was supposed to help with the SOD issue, but the flashable SOD fix uses a different method to try and fix them. Some people have reported that there's still a benefit to flashing that even with the new kernel, and I haven't heard anyone report any issues related to it, so I'd say there's no harm in including it.there have been mixed comments on this; some saying that it was incorporated, and others saying they still use the fix...if its not necessary anymore, i'll take it out of the next one...samiam330, can you weigh in on this?
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
I'm sorry, but the poster who comes into a ROM build post for the Nook Color in the Nook Color development section of XDA and says they have dumped it for a Fire because the Fire is faster (duh it has a dual core processor and was released a year later than the Color), is the troll.
Mods you can remove this whole string of off-topic posts started by the troll.