yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] steven676:
Again, the problem with this comes if you have a smaller /data partition (1 GB /data eMMC installs, or some SD card layouts) and a lot of apps -- you'll run out of room in /data/dalvik-cache. We're therefore probably going to continue steering users away from ART until we repartition.

Someone's already pushing this feature as http://review.cyanogenmod.org/56515 and http://review.cyanogenmod.org/56516 (they also have a patch set for switching between an emulated /data/media and a real SD card for primary external storage).

You can also reduce the number of rows of icons on screen. I haven't had time to look at why this is happening yet -- presumably the launcher is miscalculating how much space it actually has to draw icons.
[Nook Color Android Development] nismopc:
volpo222 - your settings change worked, but it's still not perfect. Some of the lettering still sits below the viewable screen.

steven676 - I noticed that the iamafanof's kitkat rom came with a alternate launcher then realized that rom has the same issue. I'll assume he added the alternate launcher with his build because of this same issue.

For the nightly builds, I downloaded NOVA launcher and everything works perfectly. No issues with over sized icons or hidden font, etc. Appears the Trebuchet launcher default that comes with the kitkat rom settings are not correct for Nook color screen dimension.
[Nook Color Android Development] deadbot1:
enabled ART on mine last night...used the Nook app and some Facecrack. can't say either way if its better or worse...instant app startup...but longer time to load in data(book art or the book itself when starting) Facebook also instant loads, but then seems to wait a sec before displaying anything.

Thanks to all the Devs. Love having a device that I can still get use out of after all this time. This ones still not in a dump or sitting unused in a drawer. :good::highfive:
[Nook Color Android Development] Nushio:
I've also started using CM11, after recovering my Nook from my Mom (She's since upgraded to a Nexus 7, so I'm back with my ol' Nookie :3 )

I've installed Nova Launcher, but noticed that this build doesn't seem to have a transparent Nav Bar. Is it because its disabled on "low end" devices?
[Nook Color Android Development] volpo222:
Something is up with Trebuchet in the 02/07 update. My desktop was reset and now only 5 icons across. I guess this is to get everything lined up in landscape mode. How can I get back to six across (or can I) ?

Thanks,

V

More: Trying to remove an icon from the desktop is a bit more difficult. The little red 'x' seems to have been shrunk down to a pixel in the top left of the screen. The icon still does turn red though. - Just noticed that this is only happening in landscape mode.
[Nook Color Android Development] ibilln:
woohoo

Some time btw 2/5 and 2/7 the wifi-would-not-reconnect-after-sleep issue was fixed! Thanks!
[Nook Color Android Development] bigbob23:
+1!
[Nook Color Android Development] samcoinc:
The touch response of the screen for me is 100% better. I used to find myself touching the screen 10+ times. (Compared to 10.1)
[Nook Color Android Development] newbtrigger69:
kcin launcher is WAY better than nova. promise. got all that and more. mine as well regress to a very stable jellybean build and use kcin launcher along with a kernel that provides overclocking. makes it look like kitkat. transparent nav bar and all. to change its settings, long touch on homescreen. lmk wut u think :)
[Nook Color Android Development] micl9:
Last 2 nighties (2/8&2/9) fail to auto install via cm updater, signature verification failed. Anyone else?
[Nook Color Android Development] rampart51:
Could someone please point me to the change log for the nightlies?

Something has really changed in the last few updates. Suddenly it has become very laggy. I have not updated since 2/2. Installed 2/9 this morning.
[Nook Color Android Development] Arbelzapf:
http://review.cyanogenmod.org/#/q/status:merged,n,z

I don't know if there's a better way to track the changes between individual nightlies
[Nook Color Android Development] rampart51:
Thanks....the one I remember didn't look like that but this will do!
[Nook Color Android Development] volpo222:
Perhaps you meant this one: http://changelog.bbqdroid.org/#/encore/next

V
[Nook Color Android Development] viskon:
The TWRP EMMC recovery worked for me.

Can this be added to the OP , please ? I spent quite some time trying to find the right recovery, so this might be helpful to others like me.
[Nook Color Android Development] steven676:
Coming changes which might affect app compatibility

As discussed over in the dev thread, I've landed a change to only report hardware we actually have on the Nook Color in CM, which should be part of nightlies starting February 10. While this change brings us into compliance with the Android Compatibility Definition on this front, and not lying about supported hardware is probably a good idea regardless of what standards documents say, there is a possibility that some useful apps will no longer be installable on the Nook Color because of this.

Some background: back in the old days, it was necessary to do this because the CDD (written with phones in mind) required all devices to have things like a camera, microphone and GPS, and apps were written to blindly assume that they were present. Since 2.3, though, this hardware is no longer required from all Android-compatible devices, and apps are no longer supposed to assume their presence without declaring a need for them. With the proliferation of non-phone Android devices since the release of Android 4.0 (wifi-only tablets, TV set-top boxes, ovens, ...), it should no longer be necessary to lie about hardware present in order to get apps to install and run.

That said, a large majority of Android devices in the wild still do include things like a GPS and compass, so there are likely still applications out there which either blindly assume their presence or assert a need for them despite being perfectly usable without. Hopefully, there aren't any "important" apps in that set, but we're willing to consider backing out this change if the impact on app compatibility turns out to be too significant. If you find that an app you've previously installed on your device is now reported as "Not compatible with your device" by the Play Store after this change, please report it here, but also get in touch with its maintainers -- if the app can use a hardware feature, but does not require it, it should be declared as android:required="false" in the app's AndroidManifest.xml file.
[Nook Color Android Development] volpo222:
Just installed the m3 version. Thanks for restoring 6 across icons.
[Nook Color Android Development] b30sam:
maybe this

http://www.cmxlog.com/11/encore/
[Nook Color Android Development] rampart51:
No but I LIKE THIS ONE BEST! Thanks!
[Nook Color Android Development] pastordl:
Netflix back working with 2-10 Nightlies

Whatever changed with the CM 11 2-10 Nightly got Netflix back working with the script workaround. Thanks guys for all your hard work.
[Nook Color Android Development] GAPY427:
CWM

How do you install the newer version of CWM? When I try to update it with ROM Manager, it says that the device is not supported.
[Nook Color Android Development] leapinlar:
don't use rom manager. Use cmupdater in settings.
[Nook Color Android Development] halrulez:
I keep getting a Status error 7 anyone know how to fix this?
[Nook Color Android Development] pastordl:
Sounds like wrong recovery version

If you are trying to install via CWM, are you using ver 6.0.4.7. Anything before 6.0.3.6 will not work.

Go to eyeballer's post follow his link, thank him, download and enjoy installing CM11.

http://xdaforums.com/showpost.php?p=49915965&postcount=34
[Nook Color Android Development] halrulez:
Thank you
[Nook Color Android Development] pastordl:
Trying CM11 as main os.

Including system apps have 240 on 5gig data partition, running on emmc. Smooth and fast clocked at 1100mhz. Great video quality on YouTube, Netflix, Crackle and MX Player (using "Disable HW overlays" in Developer Options) . Very, very, very happy. Thank you to all who got it running on Nook Color. Can't wait to see what's next. The new partition scheme sounds awesome. Maximizing the use of the on board memory.

Thanks again
[Nook Color Android Development] pastordl:
Is there a way to disable HW overlays past a reboot?

Have found through research that disabling HW overlays in Developer Options eliminates the video flicker problem in CM11 videos. The problem is that after any reboot you have to go in to Developer Options and click the box again to watch flicker free video. If some smart cookie could figure this out I, and others, would be very grateful.
[Nook Color Android Development] viskon:
I find my NC runs better (more responsive, less stutter) on 800MHz.
[Nook Color Android Development] steven676:
Kernel security bug -- update strongly recommended

A security bug in the core kernel (CVE-2013-6282) allows users to read and write arbitrary kernel memory on machines with ARMv6k and ARMv7 CPUs -- including the Nook Color -- and is therefore exploitable for privilege escalation (root) by a local attacker on any device with those CPUs.

The kernel in nightly builds starting February 19 contains a patch for this bug. The CVE entry notes that this bug has been exploited in the wild since October, so it's strongly recommended that you upgrade to a nightly from February 19 or later as soon as possible. (I apologize for this -- this is the sort of thing that I should have picked up much, much earlier than I actually did.)

Fixed kernels for CM10.1 stable and CM10.2 stable are available on the respective threads. See my post on the dev thread for more information.
[Nook Color Android Development] volpo222:
Hi,

Anybody else have trouble with the 02/19 nightly? After upgrading to it (SD install) my NC is stuck on the bootloader 'Loading' page.

Thanks,

V

Later: Re-installed 02/18 and it booted up as usual.
[Nook Color Android Development] dmcdonnell:
Yes. Same issue. Going to re-install 02/18.
[Nook Color Android Development] peramikic:
Ditto
[Nook Color Android Development] bigbob23:
I'm installing it now (and there seems to be no way to interrupt TWRP). No biggie, but I wish I had checked here first!
[Nook Color Android Development] Homer_S_xda:
Same here on 2/19. Updated kernel issue?

Anyone using apps from Amazon? I have issues with icons disappearing after flashing a new nightly.

Homer
[Nook Color Android Development] steven676:
Sigh. https://github.com/CyanogenMod/andr...mmit/3693f33557bb3b9731eff9379a2ab78ea309b078 is causing the boot failure -- reverted.

I'm completely at a loss here, since (1) this only changes the compiler optimization options; (2) the exact same change works fine on the 3.0.8 kernel used for the 10.2.1 release; and (3) this exact same code builds fine with this change if you change a couple of other things in the kernel config as well. This almost certainly has to be a gcc bug, but I have no time to look into this now, and we need the security fix ASAP, so ... revert now, revisit later.
[Nook Color Android Development] drmarble:
The current build doesn't boot. Don't blame Steven676. I tried reverting his kernel change and the build still doesn't boot. Something else changed in some other part of cyanogenmod. We can hope that it breaks other devices and someone else fixes it.

Again, it isn't the fault of Steven676's kernel changes. We need that change as do all devices using older kernels. It doesn't boot even without those changes.

OK, Steven676 has posted a fix. It was this patch. It caused problems with eliminating optimizing for size. So, builds should be working again.
[Nook Color Android Development] FUSHA:
Where I can download ClockworkMod 6.0.3.6 or newer for Nook Color?
[Nook Color Android Development] Mr-Glass:
Eyeballer posted these earlier in the thread... http://xdaforums.com/showpost.php?p=49898894&postcount=18
[Nook Color Android Development] FUSHA:
Thanks a lot
[Nook Color Android Development] volpo222:
If anyone is wondering, just installed 02/20. Smooth sailing once again.
[Nook Color Android Development] aperezdc:
It seems that the author has abandoned the review requests. Would it be possible to have at least the patch for vold applied into the repository? I think people who would use this feature do not mind having to type a couple of commands to enable it. Compared to the Settings option, the vold patch is small enough as to not be a problem to have it around.
[Nook Color Android Development] sqs1shu:
navigation buttons

Does anybody have the problem where navigation buttons showing in daydream mode? After a couple of days or so (my nook color main usage is alarm clock), the buttons are not visible in daydream mode or not. Using the power button to turn screen off and on, buttons reappear.
[Nook Color Android Development] uranium:
I agree with aperezdc. I would love for this feature to swap storage so I might or might not have to include a sd card for full functionality. Is there any other way to swap the internal and sd card storage in kitkat for our nook color? thanks!
[Nook Color Android Development] FUSHA:
Rom is not loading.Nook has reboot and loads to the recovery.

Recovery for CM11, and installed Cyanoboot as bootloader.

Help me please.

Sorry for my English.
[Nook Color Android Development] pastordl:
Are you using CWM 6.0.4.7 or TWRP 2.6.3.0 for recovery? If not download either here.

http://xdaforums.com/showthread.php?t=2653483
[Nook Color Android Development] FUSHA:
Thanks for link.My problem was in a wiping of /rom partition.
[Nook Color Android Development] leapinlar:
I don't think you should be wiping the /rom partition. It will make your device useless.
[Nook Color Android Development] FUSHA:
I solved the problem by using the zip for /rom restore.
[Nook Color Android Development] vtecduck:
Do I need a specific GApps to work? I downloaded the most current, but I can not set up gmail and the is no play store.
[Nook Color Android Development] pastordl:
Go to this link:

http://xdaforums.com/showthread.php?t=2653483

Look for where can I get: Gapps

Go there and select tbe gapps for CM11 20140105. Just used it for a friend and it has both.

Same Gapps that post 2 sends you to.
[Nook Color Android Development] viskon:
Have to say that the 2/25 nightly is running the best for me so far. Very fast and responsive.
[Nook Color Android Development] vtecduck:
Tried that, still no go. Loaded fine, but no way to enter gmail info or play store. Wiped everything and fresh install of rom and gapps. I am on emmc and have it set to the 5 and 1 gb partitions.
[Nook Color Android Development] pastordl:
I have the same 5g data. Did you do a factory reset / wipe cache after installing the rom and gapps.
[Nook Color Android Development] vtecduck:
That worked, thank you. I know I wiped cache after flashing, but I think i forgot to factory reset.
[Nook Color Android Development] hliew88:
*bump*

I'm holding back on upgrading to CM11 from CM10.2 because this feature is missing. I have an older nook with 1GB data/5GB media. My microSD card is tiny, only for backing up /data between ROMs, so having the internal/external swapped has really helped me store all my data since CM10.1 (mainly music synced with Google Play).

I could repartition to 5GB data/1GB media, but I'm pretty sure Google Play Music will not cache to /data as it is not even an option now, unlike on other devices. Besides, I cannot seem to flash an older TWRP with the older updater binaries to make the repartitioning scripts work.

Is there any way to make it work, even if it's some script that we must configure to run on every boot? Thanks!
[Nook Color Android Development] pastordl:
I believe that the re-partition zips need CWM to work. You can get them here. I have used both the 5.5.0.4 & 6.0.1.2 and they both worked fine with the re-partition zips.
[Nook Color Android Development] hliew88:
Thanks, I ended up upgrading to CM11 before seeing your reply (oops), and it turns out Google Play Music is happy with the files it had downloaded previously to emmc (no idea why), so my data storage is still working out. I may repartition 2GB data/4GB media, unless the comprehensive repartitioning scheme discussed last month comes through :D?

Otherwise, 3/2 nightly is running very smoothly, and managing memory slightly better than CM10.2 1/19 nightly despite not having zram (will this be added?). I had 1 SOD today, but I cannot reproduce it, nor did I get to capture a kmesg/dmesg.

I still have Seeder running on it... does this still do anything in KitKat?

Absolutely amazing how this old tablet can run KitKat... I've used mine so much that my battery can't make it beyond 4 hours of continuous use anymore! Thanks!
[Nook Color Android Development] douginoz:
Can;t find anything saying this should or should't work but I've tried using the device encryption in settings but all I get is an Android graphic that sits there for hours (I literally left it for 2 hours first time then 24 hours the 2nd time). Pushing the U button returns back to the normal screen. It appears that the menu in settings is there and you can supposedly go through the warning screens and start performing the encryption, but nothing actually happens.

Is this going to be working in the future?
[Nook Color Android Development] frankusb:
A logcat would probably catch what's going wrong. Probably vold is not happy about something. Can you post a logcat that contains you attempting to enable encryption? You can probably catch it in the first minute after enabling.

Frank
[Nook Color Android Development] douginoz:
Done. But there's absolutely no mention in the logcat of me even attempting to enable encryption. I tried it several times - walked through the Settings/Security/Encryption - enabling process, entered my PIN, started encryption, got the graphic of an android gearmesh figure. Sat there staring at it for a minute, pushed the U button, went back into Catlog, checked logs, repeated a couple of times. It really doesn't do anything at all from what I see.

I think its safe to say that anyone with a NC can safely try the same thing without fear that its going to crash or start an hour-long encryption. It appears that there's no code being executed at all.
[Nook Color Android Development] SGH-i200:
Settings/Security/Encryption

If I remember right some of the devs said this feature wasn't implemented on any nook color build at all. I did a quick search but couldn't find that statement. Maybe ask the devs over at the "[DEV] CM11 Work-In-Progress" thread?
[Nook Color Android Development] douginoz:
Clearly the only reason full-device encryption is not working on ANY custom ROMs is intentional sabotage.

No, I'm not joking. I've looked at this issue for years and without boring anyone with details, that really is Occam's Razor.
[Nook Color Android Development] bowguy:
http://xkcd.com/538/
[Nook Color Android Development] skwalas:
Err, just to clarify, the thanks was for Bowguy. Tinfoil types always amuse me.
[Nook Color Android Development] leapinlar:
It is possible to remove a thanks if you put one up in error.
[Nook Color Android Development] cyonsinn:
I've dealt with low volume on all cm versions throughout the years but this versions killing me. Has anyone else found a way to increase headphone jack volume yet?
[Nook Color Android Development] pastordl:
Check at link below under volume

http://xdaforums.com/showthread.php?t=2653483
[Nook Color Android Development] douginoz:
I don't know, but I've done a "Thanks\" to bowguy to try to offset the accidental thanks you did to me.

Of course, my tinfoil hat will one day be proven to be fully warranted and you'll be ahead of the pack when everyone wants to thank me then....

:D
[Nook Color Android Development] steven676:
Test kernel and initramfs for memory management changes

Here's a new kernel (and accompanying initramfs and kernel modules) for everyone to test out. The changes are all in support of enabling both Kernel Samepage Merging (KSM) and swap-to-zRAM by default; the goal is to have more memory available for things you care about, hopefully without too much impact on performance and battery life. (See the dev thread for details.)

Things to look out for when testing:

Do you notice less memory pressure (killed background apps and launcher restarts are some possible effects of memory pressure, though there are others)?

Do you see increased lag, and if so, how much? (Swapping pages back into memory takes time, so using swap can introduce additional lag. If there's lots of it, particularly while interacting with a foreground process, that suggests we need to tune the swap parameters, or abandon use of swap if we're not seeing enough benefit elsewhere.)

How is battery life affected? (I expect KSM, in particular, to be a net negative for battery life, but it'd be nice to get a baseline value so that we know whether any potential measures to reduce the impact are effective.)

Please also report any crashes or instability which show up after installing the new kernel.

Instructions: flash the attached ZIP file over a recent CM11 nightly from recovery. Note that if you want to uninstall this, you need to restore the original kernel (/boot/uImage), initramfs (/boot/uRamdisk), and kernel modules (contents of /system/lib/modules). (You may find it simpler to reflash your original ROM.)

Source code: kernel, wl12xx wifi modules. The initramfs is the one from the 20140309 CM11 nightly modified to enable KSM and swap to zRAM on boot.

EDIT: -gae36e35 replaced with -g833e8df; now with 100% more boot testing! Also, replaced the update-binary in the ZIP package with the one from CM 11.0-M3 for encore, which should fix install problems with some recoveries.
[Nook Color Android Development] :
Anyone else having problems installing this modified kernel? I am using the latest TWRP and getting an error message stating installation failed.
[Nook Color Android Development] bowguy:
Mine installed to SD but will not boot. Never gets to boot animation. I am not set up to get messages right now.
[Nook Color Android Development] dmcdonnell:
[MENTION=4631259]bowguy[/MENTION] and [MENTION=2683470]dcsoimpossible98[/MENTION], which cm11 nightly are you using?

[MENTION=4353291]steven676[/MENTION] states " The initramfs is the one from the 20140309 CM11 nightly modified to enable KSM and swap to zRAM on boot. "
[Nook Color Android Development] bowguy:
The 20140309 nightly. I downloaded/installed it first then the kernel
[Nook Color Android Development] andtron:
I did a new repo from steven server and did a clean rebuilt, same as bowguy, the boot screen goes totally blank.

And I am not even using steven's test kernel.
[Nook Color Android Development] :
I'm operating on the 20140303 nightly. Should I try updating to the one from the 9th before trying this kernel?
[Nook Color Android Development] hliew88:
I can confirm that the updater binary included in this zip is too old for the latest TWRP. Probably requires CWM instead.

I've been using KSM for forever, so I wouldn't be able to comment on that, but with the CM11 nightlies without zram, I can confirm a slight battery improvement over Jelly Bean w/ zram enabled. It seems to last about an extra half hour (4.75 hrs vs. 4.25 hrs) under continuous usage. I also use sleep motion tracking at night, so it doesn't go into deep sleep, and it uses about 11% battery over 6 hours as opposed to ~15%.

That said, KitKat's memory improvements w/o zram are less noticeable for me compared to Jelly Bean w/ zram, besides slightly better app launching speed... I'd prefer to have zram over battery life any day though.
[Nook Color Android Development] frankusb:
FWIW, KSM was tested on CM7 and found to impact battery life so was backed out.

Frank