• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM+Kernel] MiRaGe - Custom CM7.2 for Nook Color - 07272013

Search This thread

mang0

Senior Member
Jan 12, 2012
536
174
San Diego
Wasn't able to get the latest version of YouTube working either, even with clearing the cache/data. Just keeps showing the "touch to retry" screen when attempting to play a video.

Went back to the 2.3.4 version apk, but that one doesn't have my subscriptions! So sad. Any fixes found yet? :)
 

unibroker

Senior Member
May 17, 2011
111
22
Wasn't able to get the latest version of YouTube working either, even with clearing the cache/data. Just keeps showing the "touch to retry" screen when attempting to play a video.

Went back to the 2.3.4 version apk, but that one doesn't have my subscriptions! So sad. Any fixes found yet? :)

I don't watch YouTube on my Nook but just downloaded the 10/31 app this morning to see if I could help. I got the "Try again..." the first time but before I tried again I entered the YouTube's menu button and tapped the "HD" choice. It then played without issue.
 
  • Like
Reactions: gsutton

stevedat

Senior Member
Dec 12, 2013
553
77
Hochiminh
MiRaGe CM7.2 2012 supporting KCM?

Can anyone guide me where i can find MiRaGe CM7.2 2012 supporting KCM?
My Nook Color's screen is unresponsive, i need that rom to use USB keyboard Cover.
Thanks
 

JohnVo

Senior Member
Jan 13, 2014
63
12
Melbourne
Realme 6 Pro
No need to spam mate.
The only way to use USB keyboard is to use Nook Tweak app. You can google it.
Turn on USB host mode, it should work.

Anyway, I noticed an issue with wallpaper i.e I can't change wallpaper using ADW.launcher or Gallery or File Manager and sometimes the wallpaper is minimised in left corner. I could get back to normal by closing home screen but still, that bug is a bit frustrating.
 

owim

Senior Member
Jun 6, 2011
114
17
Europe
Hello everyone,

I've been using Mirage CM 7.2 (from 2012) for ages. In 2012. I also tried CM 10 (20121211-nightly) and it was incredibly slow. Everything was dragging. Since then there was CM 10.2.1 in 2013-11-02 which I didn't try. Regarding CM 11 I heard it's even slowlier.

What would you suggest me? To reinstall latest CM 7.2 from 2014. or try CM 10.2.1 (or one of the close working alternatives)? I hope CM 10 from 2013. is faster than CM 10 from 2012.

I'm using email, YT, TapaTalk, just the usual stuff, few simple apps. But CM 10 from 2012. was even extremely slow on screen rotation.

Thanks a lot, folks! :)
 

unibroker

Senior Member
May 17, 2011
111
22
My current build is 07272013. I was building CM10 but finally just tired of the lag in everything and returned to CM7.2.

Hello everyone,

I've been using Mirage CM 7.2 (from 2012) for ages. In 2012. I also tried CM 10 (20121211-nightly) and it was incredibly slow. Everything was dragging. Since then there was CM 10.2.1 in 2013-11-02 which I didn't try. Regarding CM 11 I heard it's even slowlier.

What would you suggest me? To reinstall latest CM 7.2 from 2014. or try CM 10.2.1 (or one of the close working alternatives)? I hope CM 10 from 2013. is faster than CM 10 from 2012.

I'm using email, YT, TapaTalk, just the usual stuff, few simple apps. But CM 10 from 2012. was even extremely slow on screen rotation.

Thanks a lot, folks! :)
 

owim

Senior Member
Jun 6, 2011
114
17
Europe
My current build is 07272013. I was building CM10 but finally just tired of the lag in everything and returned to CM7.2.
Thanks, I guess that what I'd do. I also read your other comments here on XDA to people asking pretty much the same question (CM 7 vs. CM 10 vs. CM 11). Your build 07272013 is obviously the latest (as written in this thread name)?

However, there is one more thing: When running CM 7 you're on Gingerbread Android version, which is pretty old, and most of developers ask for Android 4 or higher for newer apps. CM 10 is Jelly Bean and opens more doors. :cool: To name one, Greenify won't work on CM 7.2. List is getting longer.

Furthermore, would so many people develop CM 10 and even CM 11 for years, there are so many post here on it -- if it was lagging and being obviously slower? :confused:

I'm currently on CWM Recovery ver. 3.2.0.1 installed on eMMC (not SD card install). Should I upgrade to newer CWM ver or newer TWRP if I want to try CM 10.2.1? On the other hand, I guess that current CWM 3.2.0.1 is ok for this latest Mirage CM 7.2 build?

Finally, what is the latest YouTube app I can use on latest Mirage CM 7.2 with no problems (HD included)? For years I've been using YT app ver 2.3.4. which is really very old and would gladly switch to a newer one if possible.

Furthermore, are there any more (Google) apps which should not be updated, since they might not work (like YT)? For instance, can I upgrade Gmail app to the latest one? Also using the old one from gapps. Maps?

This is the ver. I use for years:
sP2AGv7.png


Thanks a lot and sorry for a longer post full of Qs! ;)
 
Last edited:

stevedat

Senior Member
Dec 12, 2013
553
77
Hochiminh
I see no big deal with Cm 10. I gave my NC to my counsin and he is using it quite good with CM 10. Cm 7.2 is good but there is apps you cannot install to run on it, not fully supported.
 

owim

Senior Member
Jun 6, 2011
114
17
Europe
Hello,

In 2016. which NC ROM is most cost/benefit to install?

This is a perfect question for someone who was willing to try numerous NC builds. I'm not lazy, but there are hundreds of pages on different NC ROMs and their versions. So far, I used only Mirage 7.2, famous for stability and fluidity (as possible on 2010. HW). But, since it's Gingerbread, it doesn't support newer apps. Long ago, I briefly tried CM10 from 2012. and it was pretty slow. I guess things have changed so far. ;)

I've been reading other DEV ROM threads, for instance this ROM was evaluated by users as fast as Mirage 7.2: [ROM] MROM-Encore [4.2.2][LINARO][CM10.1] build:20131003

There are different builds of modified CM10 (up to stable 10.2), and also lots of only nightly builds of CM11. There is even CM13 (Android M), developing as we speak! I don't have enough time to try all these builds, so I kindly ask someone how actually tried them or even worked on them to share a small digest: what's worth of trying and working with today on a daily basis?. Maybe a small comparison.

Are certain versions of CM10 or CM11 close to fluid, everyday use? Which offer same responsiveness (or maybe just a bit slower) but with new options (mostly: possibility of running Android 4+ apps). If yes, which version in particular is worth trying?

Finally, I'm currently on CWM Recovery ver. 3.2.0.1 installed on eMMC (not SD card install). With this ver. I can flash CM 7.2 and CM 10. How about CM11 -- do I need newer CWM Recovery?

I'm really thankful for any hint. Cheers! :)
 

tekweezle

Senior Member
Jun 20, 2012
747
110
Sad thing is that this is probably the only rom that works on the now ancient Nook Color. I tried a jellybean rom a few years ago and battery life and lag were too much.

Sent from my LGL41C using Tapatalk
 

genekellyjr

Member
Aug 4, 2013
11
8
I tried CM 7.2 (Mirage), CM9 (nightly build was only that I could find), CM10 (Schizoid), and CM10.2.

Only CM 7.2 was fluid. There's some hiccups but it works. The on screen keys are annoying and small, but it's def a miracle they're there at all.

I was not able to try CM11 as the latest TWRP & CWM recovery builds posted (http://forum.xda-developers.com/noo...-0-5-1-unofficial-t3000062/page2#post67733949) are lost with their link. The CM11 page said "faster than CM7" and Kitkat could - but I was not able to confirm. If anyone has access to a newer TWRP/CWM than the one posted by eyeballer, lemme know.

To get my Google Account activated on CM7.2 I had to use a device-specific password. It said wrong PW otherwise, even though it was def right.

Edit: Looks like Gingerbread is too old at this point. The Playstore had major issues and many apps refused to connect at all - despite installing. I managed to get to CM11 which is faster than the others (CM9/10) but not as fluid as CM7.2.
 
Last edited:
D

Deleted member 4861160

Guest
I tried CM 7.2 (Mirage), CM9 (nightly build was only that I could find), CM10 (Schizoid), and CM10.2.

Only CM 7.2 was fluid. There's some hiccups but it works. The on screen keys are annoying and small, but it's def a miracle they're there at all.

I was not able to try CM11 as the latest TWRP & CWM recovery builds posted (http://forum.xda-developers.com/noo...-0-5-1-unofficial-t3000062/page2#post67733949) are lost with their link. The CM11 page said "faster than CM7" and Kitkat could - but I was not able to confirm. If anyone has access to a newer TWRP/CWM than the one posted by eyeballer, lemme know.

To get my Google Account activated on CM7.2 I had to use a device-specific password. It said wrong PW otherwise, even though it was def right.

Edit: Looks like Gingerbread is too old at this point. The Playstore had major issues and many apps refused to connect at all - despite installing. I managed to get to CM11 which is faster than the others (CM9/10) but not as fluid as CM7.2.

I have tried KitKat on this tablet and found it unbearably slow with gapps. Actually, practically all roms other than this one are extremely slow with gapps installed. If you dont install gapps then you can probably run any of them pretty decently. At the end of the day, I ended up coming to Mirage after trying the official cm-7.2.0-encore release and I can say that the performance seems much improved/smoother on this ROM... but it might be placebo. I'm enjoying it so far! App support is scarce because it's gingerbread, but it's better than having a completely unusable tablet in my opinion.
 

zagzag99

Senior Member
Nov 3, 2008
1,500
1,468
Google Nexus 4
Google Nexus 5
I have tried KitKat on this tablet and found it unbearably slow with gapps. Actually, practically all roms other than this one are extremely slow with gapps installed. If you dont install gapps then you can probably run any of them pretty decently. At the end of the day, I ended up coming to Mirage after trying the official cm-7.2.0-encore release and I can say that the performance seems much improved/smoother on this ROM... but it might be placebo. I'm enjoying it so far! App support is scarce because it's gingerbread, but it's better than having a completely unusable tablet in my opinion.

If not gapps, how do you install apps? Side loading?

I have a nook at the drawer, and if I can get it to run some browser and play YouTube it could be useable again.
 
Last edited:
D

Deleted member 4861160

Guest
If not gapps, how do you install apps? Side loading?

I have a nook at the drawer, and if I can get it to run some browser and play YouTube it could be useable again.
Exactly, you would have to sideload them. You can try for yourself to see if it works for you. CM10 is not terrible with gapps but as soon as you start installing stuff it goes bad in my experience. Honestly, I just settled for Mirage because it seems to be more optimized for the Nook than the official CM 7.2.0 release.

I did not try sideloading youtube on CM10 (it's been a while) but I can tell you that the app completely does not work on GingerBread. However, I did manage to get Youtube playing on Naked Browser (because Opera Mini wasn't working for me in that regard for some reason). The video runs pretty smooth and doesn't drop many frames but the quality definitely leaves things to be desired. However, I would assume playing videos off of an SD Card or EMMC would work well (but have not tested this), if you're interested in that.

The main use I have been able to give this tablet is emulators on Gingerbread. Not a whole lot is still compatible with this extremely old version but I much prefer the smoothness of it on this tablet than the more recent versions of CM that were released for this device.

Let me know what you end up doing and progress!
 

zagzag99

Senior Member
Nov 3, 2008
1,500
1,468
Google Nexus 4
Google Nexus 5
Exactly, you would have to sideload them. You can try for yourself to see if it works for you. CM10 is not terrible with gapps but as soon as you start installing stuff it goes bad in my experience. Honestly, I just settled for Mirage because it seems to be more optimized for the Nook than the official CM 7.2.0 release.

I did not try sideloading youtube on CM10 (it's been a while) but I can tell you that the app completely does not work on GingerBread. However, I did manage to get Youtube playing on Naked Browser (because Opera Mini wasn't working for me in that regard for some reason). The video runs pretty smooth and doesn't drop many frames but the quality definitely leaves things to be desired. However, I would assume playing videos off of an SD Card or EMMC would work well (but have not tcested this), if you're interested in that.

The main use I have been able to give this tablet is emulators on Gingerbread. Not a whole lot is still compatible with this extremely old version but I much prefer the smoothness of it on this tablet than the more recent versions of CM that were released for this device.

Let me know what you end up doing and progress!

I've tried flashing mirage, seems like it causes a reboot twrp while flashing and then just fail to start.

I found on my nook's SD a copy of cm11 nightly 15/08 and I am trying to make the tablet work without gapps. To see if it's reasonably useable
 
D

Deleted member 4861160

Guest
I've tried flashing mirage, seems like it causes a reboot twrp while flashing and then just fail to start.

I found on my nook's SD a copy of cm11 nightly 15/08 and I am trying to make the tablet work without gapps. To see if it's reasonably useable

That’s weird. I flashed Mirage with TWRP and had no issues with it. Did you follow eyeballer’s guide?

As for CM11, I remember there was something about installing a Snapshot released before installing the last nightly or else it wouldn’t install. Not sure if it was for cm11 or CM10, but that might be worth looking into if you’re not able to flash it first time around.
 

zagzag99

Senior Member
Nov 3, 2008
1,500
1,468
Google Nexus 4
Google Nexus 5
That’s weird. I flashed Mirage with TWRP and had no issues with it. Did you follow eyeballer’s guide?

As for CM11, I remember there was something about installing a Snapshot released before installing the last nightly or else it wouldn’t install. Not sure if it was for cm11 or CM10, but that might be worth looking into if you’re not able to flash it first time around.

I got mirage to flash, apparently I had to downgrade to twrp 2.3 (I was on 2.8, for cm11).

It's working snappier on the nook, but very limited in what it can do.
Seems like the integrated browser is capable of playing YouTube site. Just warnings about certificate authenticity. And not being able to do secured connections.

I'll see if this would get it out of the drawer and be used for something.

Edit: it's un-useable. Nothing can really work on it.
In the process of tinkering with it I got it reset to stock - a big mistake as I do not have the proper files now to hack it out of stock.
And it can't register as stock anymore, my guess the back end BN site not operational any more.
So this is now officially a tech junk, which I need to properly bring for electric recycling.
Sad moment.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 205
    miragebanner.jpg


    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.

    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://forum.xda-developers.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://forum.xda-developers.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://forum.xda-developers.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://forum.xda-developers.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://forum.xda-developers.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://forum.xda-developers.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://forum.xda-developers.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.
    Downloads:
    - 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.
    enocre2shots.jpg


    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.
    28
    MiRaGe 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!
    27
    MiRaGe 06232012

    I have uploaded the 06232012 build of MiRaGe after syncing with the latest changes in CM repo. Please check the OP for the download links, changes, and also the credits. Enjoy!
    19
    This 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
    Any desire to tinker with CM9/AOKP builds? I know you build for personal use, but have you thought about starting an ics rom? Or are you waiting until the 3.0 kernel is fully functional? Your cm7 builds are super solid, just wondering what's holding you back from moving towards ics..

    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.