This is the one I use on my Nook Color:
https://play.google.com/store/apps/details?id=com.wemobs.android.lcdresolution
"LCD Resolution (Root)"
[ROM+Kernel] MiRaGe - Custom CM7.2 for Nook Color - 07272013
- Thread starter mrg666
- Start date
This is the one I use on my Nook Color:
https://play.google.com/store/apps/details?id=com.wemobs.android.lcdresolution
"LCD Resolution (Root)"
Hi, I just read through upon the recommendation that somewhere in this thread or in the rom settings itself it was possible to get the interface I was asking about in this thread here. Probably I missed it, but mostly the closest thing to an answer of what I wanted was in regard to theming the buttons in the system tray\notification bar. Not exactly what I'm looking for.
What I want is something like the way ICS handles the clock and notification bar at the top of the screen with a bar at the bottom of the screen with soft buttons to replace the missing ones we need on the NookColor. Is this at all possible in the Gingerbread version of Android without resorting to using a different launcher? I'm fond of Espier Launcher HD and would prefer not to have to give it up to get this.
While I'm definitely no programmer I am willing to try editing and mucking around with XML files to get it to work if people will point me in the right direction.
Also is it possible to use UOT kitchen for this rom? If so are there any *.uot files I can use to build off of and (hopefully) not make too much of a mess by using?
Thanks for all the hard work you put in here on this Rom and the IHO rom. (I have an Optimus V too, so I am already somewhat aware of your work from that.)
--bornagainpenguin
What I want is something like the way ICS handles the clock and notification bar at the top of the screen with a bar at the bottom of the screen with soft buttons to replace the missing ones we need on the NookColor. Is this at all possible in the Gingerbread version of Android without resorting to using a different launcher? I'm fond of Espier Launcher HD and would prefer not to have to give it up to get this.
While I'm definitely no programmer I am willing to try editing and mucking around with XML files to get it to work if people will point me in the right direction.
Also is it possible to use UOT kitchen for this rom? If so are there any *.uot files I can use to build off of and (hopefully) not make too much of a mess by using?
Thanks for all the hard work you put in here on this Rom and the IHO rom. (I have an Optimus V too, so I am already somewhat aware of your work from that.)
--bornagainpenguin
Regarding the statusbar on top and soft buttons at the bottom, you can move the statusbar to the top without soft buttons and using a soft-button app like button savior put the soft buttons at the bottom.
I finally got tired of optimizing bloated and unoptimized framework-res.apk and SystemUI.apk with every build and gave up with UOT kitchen some time ago. Instead of UOT, you can simply try replacing the icons in the framework-res.apk and SystemUI.apk yourself for starters. There are many guides around the forums about how to do this properly. Or, ultimately, you can start building from the source with the icons mods as I do here. I try to avoid modding the source code since I want to keep the ROM as close to CM as possible but you can do that as well. IMHO, the best way to theme is using the CM theme engine. Check this thread, it will give you a good head start on how to make themes for the built-in theme engine in CM which is much better than using UOT Kitchen.
Thanks for the response.
I looked into Button Savior a bit earlier but I didn't see a way to make it look native. Basically what I want is a bar on the bottom like there is now with the buttons but the clock up at the top with the notifications. I was under the impression that Button Savior just floats on the screen, not acts as a bar on the bottom (or wherever you set it to appear).
Thanks for the info on how to theme things, I guess I'm used to the way the roms on the Optimus work, which practically require use of UOT Kitchen. I'll start working my way into the threads you suggested and see if I can figure it out.
Sent from my NookColor using Tapatalk
I looked into Button Savior a bit earlier but I didn't see a way to make it look native. Basically what I want is a bar on the bottom like there is now with the buttons but the clock up at the top with the notifications. I was under the impression that Button Savior just floats on the screen, not acts as a bar on the bottom (or wherever you set it to appear).
Thanks for the info on how to theme things, I guess I'm used to the way the roms on the Optimus work, which practically require use of UOT Kitchen. I'll start working my way into the threads you suggested and see if I can figure it out.
Sent from my NookColor using Tapatalk
Screen unresponsive after install
I recently installed this ROM and while it started off working excellently, it since has become unresponsive to touch input. I already tried restoring and flashing different roms, but nothing works. Can anyone help me out? Thanks!
I recently installed this ROM and while it started off working excellently, it since has become unresponsive to touch input. I already tried restoring and flashing different roms, but nothing works. Can anyone help me out? Thanks!
"I recently installed this ROM and while it started off working excellently, it since has become unresponsive to touch input. I already tried restoring and flashing different roms, but nothing works. Can anyone help me out? Thanks!"
I don't believe it's a ROM problem as I've had the same thing happen running older CM versions also. I've always used the app "Nook Screen Recalibrate". It seems to help sometimes, other times a reboot with a cache/dalvik wipe helps. Then again sometimes a reload of the ROM cures it.
I don't believe it's a ROM problem as I've had the same thing happen running older CM versions also. I've always used the app "Nook Screen Recalibrate". It seems to help sometimes, other times a reboot with a cache/dalvik wipe helps. Then again sometimes a reload of the ROM cures it.
Just wanted to say...
Best ROM to date I've used (and I've used quite a few). Performance is at the top for a NC, and compatibility is pretty darn good.
The few items I have on the laundry list are:
1. Some items in the market (namely GameLoft and EA) show as not being compatible with this device.
2. We still have the FC on rare occasion on the status bar. I've seen the status bar disappear (no FC) with no hope of returning on SplashTop (even with the volume up set as the status bar toggle).
Overall though, just stopping in to say excellent ROM. Stability, compatibility, and performance in gaming has yet to be topped.
Best ROM to date I've used (and I've used quite a few). Performance is at the top for a NC, and compatibility is pretty darn good.
The few items I have on the laundry list are:
1. Some items in the market (namely GameLoft and EA) show as not being compatible with this device.
2. We still have the FC on rare occasion on the status bar. I've seen the status bar disappear (no FC) with no hope of returning on SplashTop (even with the volume up set as the status bar toggle).
Overall though, just stopping in to say excellent ROM. Stability, compatibility, and performance in gaming has yet to be topped.
Thank you for the comments.
Regarding incompatibility of some apps in the Market, this a problem with custom ROMs in most devices. I am not sure how to handle this because to make the ROM compatible with those apps we might be creating other incompatibilities. Some of the apps are locked to certain carriers besides the hardware requirements. But there are probably very few such apps.
Regarding the statusbar FC, there is a note in the OP. Please check under the heading "Recommended options".
Last edited:
1. Yeah, I'm not 100% positive how they filter - IMIED or LCD density? I think 160 is standard for LCD density, however.
2. I had read that, but don't like to turn off disable full screen because of the fact that my daughter likes to open every app on the Nook and hit the home button after each one (nice way to quickly make your Nook drag).
3. This one relates to 2, but with Button Savior, although it's a great app, the Nook's precision is not so great when touching the screen. That said, because Button Savior's fly out button is so small, it ends up screwing with other elements when you try to hit it (not to mention activating other menus it overlaps).
Overall, the issues with the status bar are far enough between where it's just a minor irritation deal. I'm sure forcing OpenGL/Hardware accelerated applications into a smaller space than originally intended is no small ordeal.
A note about the status bar: I also have had it disappear on me but have discovered a fool-proof way of getting it back: after acknowledging the fc, DON'T TOUCH THE SCREEN. It has never failed to come back for me within a few seconds.
Sounds crazy right? I hypothesize that the touch response may screw up the app restart. Why? I dunno, but it works for me, without fail, every time.
Sounds crazy right? I hypothesize that the touch response may screw up the app restart. Why? I dunno, but it works for me, without fail, every time.
that's worked for me on this ROM as well. Back on stock CM7 I had to use the statusbar restarter app when the statusbar fc'd and have been keeping it around unused just in case.
Thanks for the comments. Please thank/donate to CM developers. I am just building for myself and sharing here.
As written in the OP, I highly recommend unchecking the "disable full screen" option in the Tablet Tweaks to avoid the status bar crashes. Button Savior developer greatly improved the app lately. When I enable autohide feature in Button Savior, it does not occupy any space on the screen. I just use the short swipe option at the right edge of the screen and bring the soft buttons when needed. Since I keep the soft buttons on the status bar, Button Savior is only used when an app goes to full screen mode.
Since there are no important changes in the CM repo, I have not built this weekend.
As written in the OP, I highly recommend unchecking the "disable full screen" option in the Tablet Tweaks to avoid the status bar crashes. Button Savior developer greatly improved the app lately. When I enable autohide feature in Button Savior, it does not occupy any space on the screen. I just use the short swipe option at the right edge of the screen and bring the soft buttons when needed. Since I keep the soft buttons on the status bar, Button Savior is only used when an app goes to full screen mode.
Since there are no important changes in the CM repo, I have not built this weekend.
I'm using that disable fullscreen option and like it a lot for games. The status bar crashes don't happen often (maybe once a week) and it recovers itself within seconds. Maybe I'm just lucky though.
I've just updated to the latest version and it's working wonderfully as usual. One quick question, regarding the first recommended option from the OP:
Recommended options:
1) Nook Color with its large kernel with many features consumes the RAM rapidly and low memory becomes an issue where V6 Supercharger becomes useful.
Here is how I install, it takes only one minute.
My question is should I run this everytime an update is done or it does remember those settings from previous versions? (I only choose to wipe dalvik's cache from ROM Manager)
TIA!
Recommended options:
1) Nook Color with its large kernel with many features consumes the RAM rapidly and low memory becomes an issue where V6 Supercharger becomes useful.
Here is how I install, it takes only one minute.
My question is should I run this everytime an update is done or it does remember those settings from previous versions? (I only choose to wipe dalvik's cache from ROM Manager)
TIA!
If you are just upgrading the rom without doing a clean install, V6 stays intact.
Actually, the V6 script needs to be ran after updating. If you are using the one of the later updates, when you run the script after flashing an update over a previously supercharged ROM, the v6 will recognize the new flash (through overwritten symlinks) and ask you if you want to "re-supercharge" your previous settings as saved on the sdcard.
I don't think that update 8 has that part of the script, although I could be wrong. I think one of the major advantages of running the later updates and rc's is the expanded explanations of how well the script is working (although it can take a REAL long time to run).
If you want the latest updates, you can get it through Botbrew, or just as easily through zep's posts.We only added cm7 support by request, so people could always have the latest upgrade on their device. Downloading the script manually is no harder, I know.
Update 8 does not need to be rerun after updating the ROM. I don't recommend the later versions of Supercharger. The additional features do not add any noticeable benefit. Supercharger update 8 is sufficient for helping with the low memory of NC. I would avoid excessive complexity of the later versions.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
205
I have been building/compiling my Nook Color's ROM from the CM repo. Besides the geek satisfaction, I build for removing some extras and customize for performance. This thread is for sharing what I build for myself with the community. Here is MiRaGe.
Please thank/donate to CM project, especially the lead Nook Color developers, dalingrin, fattire, and keyodi.
Thanks to Nick N, unibroker, Tool Belt, k8108, christoophat, deboyz1014 for their generous donations.
Special thanks to nissanskylinebam for the banner.
Changelog:
CyanogenMod 7 changes are here.
My changes on the nook kernel are here.
Downloads:Code:[B]Updates:[/B] [U]07/27/2013:[/U] - Android security fix 8219321 (CYAN-1602) to Bluebox security bug merged - Updated ADW Launcher [U]05/13/2013:[/U] - Optimized kernel configuration by removing unused features - Removed debugfs for security improvement - Switched to performance optimization - Updated boot animation [U]03/28/2013:[/U] - Synced with CM repo - updated kernel with the 03282013 build - removed ro.pm.awake_on_usb enforcement from build.prop [U]03/10/2013:[/U] - Synced with CM repo - updated ADW Launcher - updated kernel with the 03082013 build [U]03/08/2013:[/U] - New kernel update package: -- cryptography library optimizations (sha1, crc32, aes) -- use get_random_int() to fix entropy depleting [U]11/10/2012:[/U] - Updated ADW Launcher [U]09/30/2012:[/U] - Synced with CM - Updated Cyanoboot [U]07/30/2012:[/U] - Reverted the KSM support in the kernel and dalvik-vm [U]07/27/2012:[/U] - Modify Running ProcessView as ics in Settings - Fixing a crash when doing lock profiling in dalvik vm - Basic [URL="http://review.cyanogenmod.com/#/c/12174/"]KSM Support in dalvik vm[/URL]. This is complementary to the KSM feature added into the kernel build. - Customizable kill app via back key timeout. - updated the kernel -- added [URL="http://www.linux-kvm.org/page/KSM"]KSM[/URL] support. See [URL="http://xdaforums.com/showpost.php?p=29460098&postcount=1595"]this post[/URL] for a patch that will initiate the KSM service. -- removed several debug configs [U]07/12/2012:[/U] - New build, synced with CM - ICS menu icons - default to hardware EGL libraries of SGX530 instead of using generic android EGL libraries (thanks to leolawliet) - new kernel with the following changes -- use optimized strnlen, strncpy, and crc32 functions in ARM (thanks to faux123) -- disable several DEBUG settings in kernel config [U]07/05/2012:[/U] - New build, synced with CM - ICS icons for settings.apk and power widget - new kernel with the following changes -- BFS 4.04 scheduler added to kernel -- updates to ashmem, lowmemorykiller, and interactive governor -- updates to rcutiny and core scheduler components [U]06/23/2012:[/U] - New 06232012 build, synced with CM [U]06/08/2012:[/U] - New build, synced with CM - Backported many bug/security fixes from 2.6.32.59 kernel for block layer, file system, networking, bluetooth, ARM architecture, and sound. See my github link above for details. [U]05/27/2012:[/U] - New build, synced with CM - Backported the staging android drivers from kernel 2.6.38.8 - added a fix for uptime overflow in the kernel after a recent report - added a modified Cyanbread_light theme to replace the orange highlights with cyan/blue that matches with the recent Google Play apps. The source code of Cyanbread_light is [URL="http://www.mediafire.com/?f2deqwh59p355r8"]here[/URL]. [U]05/18/2012:[/U] - New build, synced with CM - Integrated the 05112012 build of encore kernel and included Dalingrin's flicker fix by default since many users downloaded it. All of the kernel downloads below include the fix. - Replaced the bluetooth icon on statusbar with a new one - Tagged CM7.2 RC2 [U]05/11/2012:[/U] - The final build of the newly updated kernel is ready with a long list of changes (see the link above). You can download from the link below. The kernel is compiled with gcc-4.6 for better performance. - There is an important bug fix for busybox in the CM repo. You can patch your ROM with [URL="http://www.mediafire.com/?ee54355codge3xg"]this file[/URL] in the recovery. [U]05/09/2012:[/U] - Synced with CM - Updated the kernel source with B&N 1.4.2 update which brought updated touch screen and accelerometer drivers - Added Simple I/O scheduler as default and removed BFQ scheduler in the kernel. - Synced the binary/proprietary blobs in CM repo with B&N 1.4.2 update. - Removed the 16-bit framebuffer support since 32-bit performance is very good - Reverted the 68kHz pixel clock to default 48kHz. There is an optional kernel in the download section with Dalingrin's flicker fix included. - Reverted edge responsiveness workaround since it was not effective and causing more insensitivity at the touchscreen corners - Reduced the ROM size by ~5MB [U]05/05/2012:[/U] - Synced with CM - Replaced the lock screen clock font with the ICS clock font. [U]04/16/2012:[/U] - Synced with CM - integrated the OOM optimizations, see [URL="http://xdaforums.com/showpost.php?p=24930815&postcount=1004"]this post[/URL] for details - removed the V6 Supercharger recommendation [U]04/07/2012:[/U] - Synced with CM - transparent notification background [U]03/30/2012:[/U] - Updated [URL="http://xdaforums.com/showthread.php?t=1526119"]Cyanoboot[/URL] with 03/28/2012. Thanks to tonsofquestions and fattire - Synced with CM [U]03/23/2012:[/U] - Added [URL="http://xdaforums.com/showthread.php?t=1526119"]Cyanoboot[/URL] (thanks to fattire) - Synced with CM [U]03/04/2012:[/U] - CM 7.2 RC0 -> RC1 - Synced with CM [U]03/01/2012:[/U] - Synced with CM [U]02/25/2012:[/U] - Synced with CM - Replaced the soft button, battery, WiFi, smiley icons with ICS style icons in GB color. - Tested the ICS kernel with CM7.2. There were many problems. See [URL="http://xdaforums.com/showpost.php?p=22971427&postcount=710"]this[/URL] post for details. [U]02/17/2012:[/U] - Synced with CM [U]02/10/2012:[/U] - Synced with CM [U]02/01/2012:[/U] - Synced with CM to include the FC fix with rotation. No Statusbar FC on boot anymore. I had tested this fix earlier and it was not preventing the statusbar FC. Now works, I missed something apparently. - Built an optional ROM with the full language set. If you don't need any other language than English(US) and Spanish, smaller ROM is recommended. [U]01/26/2012:[/U] - Synced with CM to include the rotation animation fix. Thanks to kalltkaffe for this brilliant fix. - Please upgrade to this build if you are on 01232012 build. No other rotation fix is necessary. We are using unchanged CM7 kernel again without the backported CM9 rotation fix. - For the ones who want to go back to an earlier build, I had given the links to 01132012 build in [URL="http://xdaforums.com/showpost.php?p=21763348&postcount=459"]this post[/URL]. [U]01/23/2012:[/U] - Synced with CM [U]01/13/2012:[/U] - Synced with CM [U]01/10/2012:[/U] - Synced with CM [U]12/12/2011:[/U] - Synced with CM - Switched to modular kernel (see the previous update below), includes the SOD patch, and compiled with linaro 4.5-2011-10 toolchain. [U]12/05/2011:[/U] - Based on Dalingrin's encore kernel, built a modular kernel by configuring the uncommonly used features (they are still available) as kernel modules. There seems to be about 20% increase in the free RAM (available to the apps and cache) after first boot on my nook. If you want to try, here is [URL="http://www.mediafire.com/?6ii07g7bgh2273f"]the link[/URL]. See [URL="http://xdaforums.com/showpost.php?p=20048066&postcount=139"]this post[/URL] for more details [U]12/01/2011:[/U] - Synced with CM [U]11/28/2011:[/U] - Synced with CM - Dalingrin's kernel with SOD patch included in the build with recompiled kernels using linaro 4.5-2011.10 toolchain since the feedback was positive. The optional files are still downloadable for the ones who want to use them with other builds. - Updated Superuser.apk to 3.0.7. Market was constantly showing this update. [U]11/24/2011:[/U] - Included [URL="http://forum.cyanogenmod.com/topic/32316-sleep-of-death-debugging/page__view__findpost__p__266644"]dalingrin's SOD fix[/URL] in the kernel build. [U]11/20/2011:[/U] - CM sync - Added a flashable zip with Dalingrin's Encore kernel recompiled with Linaro 4.5-2011.10 toolchain. [U]11/18/2011:[/U] - Synced with CM - Reverted my signal icon fix to include [URL="https://github.com/CyanogenMod/android_frameworks_base/commit/72bd1410dfecbb061d7168af688579fd8da8b935"]Dalingrin's commit[/URL]. - Added back CMStats [U]11/16/2011:[/U] Well, everyone is talking about ICS code release but there is another news that [URL="https://github.com/CyanogenMod/android_vendor_cyanogen/commit/9eb9d741524dd596798821dedad43ee68207b955"]CM switched to 7.2.0-RC0[/URL] recently which came with a large number changes. I will not go through all those but you can check them [URL="https://github.com/CyanogenMod/android_frameworks_base/commits/gingerbread"]here[/URL]. I have also updated Roboto font with the improved version in the Android 4.0.1 source release. [U]11/13/2011:[/U] - Synced with CM - Resolved persistent signal bar problem in the status bar. The source of the problem is [URL="https://github.com/CyanogenMod/android_frameworks_base/commit/2ce85e989e66da91dc3c082fbe9bdf030fbd20f5"]this commit[/URL], removed the commit before compiling the code. - Updated Superuser.apk and su binary - Removed extra themes, - Removed CMwallpaper, - Removed large ring tones, - Removed and decompiled CMUpdateNotify - Removed development app, - Removed all languages except [U][B]English(US) and Spanish[/B][/U] - Removed ROM Manager, latest version is available in the Market. - Replaced the system font with the Roboto font from ICS - The optional status bar transparency theme as a flashable zip, please see the screenshot to decide if you want it.
- ROM with only English(US) and Spanish languages - 07272013 build: MD5sum: 1fb04c4134b76798c930300d54d3f197
- International ROM with full language set - 07272013 build: MD5sum: a8c940244c9d3f68a4699133a1d51c57
- Latest (05/16/2013) kernel update package. MD5sum: 945e7bd31a3553debea6e7d1543d8c4c (please see this post about turning off WiFi )
Installation:
- Just follow Eyeballer's guide.
- If you are installing MiRaGe for the first time or upgrading after a long time, complete wipe is recommended.
- When upgrading from a recent MiRaGe build, do wipe cache/dalvik-cache only.
- If you do a clean wipe, you will need to flash gapps again. You can find it here or here.
Recommendations:
1) Regarding the status/notification bar force close issues, I recommend unchecking the "disable full screen" option in the Tablet Tweaks to avoid the status bar crashes. This also improves the app behavior especially movies and games that need full screen. To bring the soft buttons back in the full screen mode, I recommend Button Savior (available in the Market). If you had tried this app before, Button Savior developer greatly improved the app lately. When I enable autohide feature in Button Savior, it does not occupy any space on the screen. I just use the short swipe option at the right edge of the screen and bring the soft buttons when needed. Since I keep the soft buttons on the status bar, Button Savior is only used when an app goes to full screen mode. You can even remove the soft buttons from the status bar completely if you prefer an uncluttered status bar.
2) If WiFi is not starting automatically on reboot, please see the fix in this post.
Screenshots:
Using ICS Launcher icons by kovdev. The clock widget is Sense Analog Clock.
Disclaimer: I don't accept any responsibility for any kind of damage or loss. If you are going to report problems, please make sure that there are no mods or themes applied to the system. Also, SD installations are not supported since many problems are related to the performance of particular SD card. Only EMMC installation is recommended and supported. Before reporting any problem please try reflashing after a clean wipe.28MiRaGe 11102012
I have updated the ADW Launcher with the latest version which is working much better than the previous version. With only this change, I have bumped the build number to 11102012. This will probably be the final version of MiRaGe for Nook Color based on CM7 since the development has reached to saturation since some time. There isn't much left to do here. I am planning to base the future builds on CM10.
Enjoy!19This is an effort to reduce the way to get Mirage-Kang on the eMMC of a Nook Color to it's bare essentials. It will then introduce what some call "must have" refinements and hopefully give a glimpse into the enormous potential of our beloved NC. This is just a compilation, you have a lot of thanks to click before you click mine. If you would prefer to install to an SD card first you"ll want to take a look at verygreen's thread.
First:
1) Use Win32DiskImager to write the 1gb_clockwork-3.2.0.1-eyeballer.zip image to the boot SD hereafter referred to as the CWM card.
2) Download encore_CM72-MiRaGe-11102012.zip and write it to the CWM card.
3) Download gapps-gb-20110828-signed.zip and write it to the CWM card.
4) Boot into the ClockworkMod Recovery.
5) Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and the n button to select.
6) Optional: Select backup and restore to create a backup of current installation of the Barnes & Noble Nook Color. Standard Caution: If you don't do a backup you won't have a backup. Excuse me, I'm gonna go do a backup,
7) Select the option to Wipe data/factory reset.
8) Then select the option to Wipe cache partition.
9) Select Install zip from sdcard.
10) Select Choose zip from sdcard.
11) Select the encore_CM72-MiRaGe-********.zip.
12) Install the Google Apps by performing steps 9 - 11 again and choosing the gapps-gb-20110828-signed.zip.
13) Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, (I use the power button as a back button), and select the Reboot system now option.
14) Last thing before you hit reboot, pop out the CMW card and put your storage card in.
The Barnes & Noble Nook Color should now boot into CyanogenMod. (It seems to take longer that first boot, don't sweat it.)
Reference:
eyeballer's thread
mr72's thread
mrg666's thread
___________________________________________________________________
Some Settings to Consider:
Settings, CyanogenMod Settings, Performance Settings:
check Use 16bit transparency
Settings, CyanogenMod Settings, Performance Settings:
uncheck Enable surface dithering
Settings, CyanogenMod Settings, Performance Settings, Compcache RAM Usage:
disabled
Nook Tweaks, CPU Setting, Clock settings:
300, 600, 800, 1000, 1200, check set at boot
Nook Tweaks, CPU Setting, Voltage Settings:
.925, 1.05, 1.2, 1.275, 1.325, check set at boot
Reboot
___________________________________________________________________
When you want to update...
You shouldn't need to redo gapps or delete Dalvik cache.
You'll notice that during the initial CyanobootMod there is an instruction to hold down the "n" for boot options. Since you're rebooting anyway why not hold down the "n" key and use the volume key to choose the eMMC recovery option. See? It looks just like CWM except slight wording changes. We want to make use of this and at the same time make SD Card swapping a thing of the past. All you should have to do is surf over to mrg666's thread and grab his latest from the OP. At this point I like to move it from the download folder to the temp folder but you could leave it in the download folder if you like. Reboot to CWM recovery option, wipe cache, select the appropriate folder and load the update ROM from it, reboot new ROM. If you where setting at your desk at work when you did this you may now go get a 'Born to Hack' tat during lunch and grin sheepishly the rest of the day.
After that first boot I like to go to settings/about tablet to make sure it "took" then reboot just because I'm a geek that way.
The above is the last Mirage-Kang update for CM7 don't forget to find a post of mrg666's and thank him.
___________________________________________________________________
Qapla' Y'all!15
I thought about joining the other developers. But if I leave CM7 there will be nobody left behind to cover the base. If you look at the changelog and user feedback, I did more than just building from the CM repo in the recent months. GB is not new and shiny like ICS anymore but I still enjoyed optimizing the CM7 build and overhauling the encore kernel. Plus I am also building for LG Optimus V. I simply didn't have time left for ICS. There is a little more work I want to complete for the encore kernel. I can try to help with ICS after that.I just don't like leaving incomplete stuff behind.
