yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] bowguy:
Dual boot with cm-13

Dual boot works fine on the Nook. Install cm-11 or lower on the SD card as usual. Install cm-13 on emmc. When you boot into cm-13 it will ask you to configure the SD card. Pick the option for portable storage and it will still dual boot. An added advantage on cm-13 is it sees all the SD card partitions and files instead of just the boot partition as in previous versions
[Nook Color Android Development] loneBoat:
I'd be interested in a ROM if you're willing to upload it!
[Nook Color Android Development] XxAmyJo87xX:
I'm willing to try..pretty please
[Nook Color Android Development] drmarble:
I am glad that there is interest. I am currently too sick to trust posting a rom but will put one up soon.

There are a few improvements since I last described it. It now backs up and restores your gapps. You do need to overwrite your old cm-11 gapps on the first install. It correctly mounts the data partition.

You will need the larger system partition described here: http://xdaforums.com/showpost.php?p=54401912&postcount=4177 along with his flashable zips.

I am currently trying to get f2fs working. When I do, I will post new flashable repartition and format zips.
[Nook Color Android Development] drmarble:
cm-13 rom available:

As promised, here is a flashable rom:

http://d-h.st/lAkX

I recommend reading the last cople of pages of the cm-11 development thread where I discuss some of the limitations of this rom.

You sill need a larger than standard (450M) system partition so use the link provided in my previous post to flash the 1GB system 4.5GB data 1GB media. You will then need to format those partitions with vfat or ext4 as appropriate. You can also do the partitioning by hand as was discussed in the cm-11.0 thread. Start reading here: http://xdaforums.com/showthread.php?t=1370873&page=417 and continue for a few pages. As I remember the update binary in those zips required an earlier cwm version. You can always do the repartitioning by hand with adb shell in recovery.

Note, you will lose all data stored on the internal sdcard. Marshmallow insists on encrypting the data-media partition. Make backups. Store them off the tablet. After formatting, you can restore those cwm backups and get your /data back. Your personal files are up to you.

You can install the open gapps nano gapps. I don't recommend using any larger gapps. These apps really slow down the device. The fewer applications running the better.

If I was healthier I would probably make some repartition and reformat zips with a current update binary. I think I made some back when but cannot locate them now. I expect to get better soon. Never eat bad peanut butter with a broken seal.
[Nook Color Android Development] hliew88:
Thank you so much for this!!! I repartitioned to a 1GB /system and 5.5GB /data (leaving /media to <8MB since it's useless in Marshmallow) and then clean installed this ROM with pico gapps. It has been running pretty smoothly but definitely slightly slower than KitKat (except with app launches because of ART vs. Dalvik).

A couple notes:

1) The built-in File Manager does not have the option to request root. Is this because SELinux is disabled?

2) I noticed your patches removed the Noto fonts, leaving lots of "tofu boxes" around non-English characters. Was this to save space in /system, and can it be added back?

3) I seem to be getting best performance (especially with YouTube) at max 1200MHz CPU clock and the Deadline scheduler (128kb read-ahead). I/O speed feels like the bottleneck... would f2fs give tangible improvement?

4) None of the fancy display stuff (LiveDisplay, inversion) work which is to be expected. Could it ever be supported by our poor old GPU?
[Nook Color Android Development] bowguy:
1) Titanium Backup has the same issue.

2) I added back the fonts and it adds 20MB (10%) to the build so it is doable.
[Nook Color Android Development] drmarble:
Glad things are working for you.

I have finished the f2fs work. It is running fine for me. You can use the f2fs device and kernel trees. I don't think I had to change anything else. I don't notice any improved performance, it is still slow. Maybe a little less. No major change in quadrant scores. We just spend all our time being I/O limited (according to toybox top). I have made a cwm that supports f2fs and an f2fs compatible twrp 3.0 that will backup/restore twrp and change file system types. It just crashes on flashing a rom. I used the twrp to backup and restore my data partition. I don't like reinstalling. I view having to re-login to the play store as a sign of failure. I will get these posted someday. I should also post a document on repartitioning and reformatting. Maybe I can make some flashable zips for that. I think I found my old data/media and format flashable zips. I will leave using twrp to restore the data partition to those who care to look up how it is done. There are some good tutorials elsewhere on xda.

I don't include the noto fonts because adding that 20mb to the zip prevented me from sideloading it. I hate having to upload the roms to the devices.

I should add it back for the zips that I post. I just dumped them for space. Actually, my zips have been getting smaller. The CM code base has been tightened up. Maybe I can include it in sideloadable zips.

I doubt we will get any of that fancy display stuff working. I have been trying to backport the new graphic drivers from the Motorola 360 watch. It uses a 3.10 omap3660 kernel. I haven't had any luck yet. I am just happy that I can watch a youtube video.

I will keep working on making this better. If I try real hard, I might be able to get this official again. There are just a couple of tough build patches. Making the sound libraries and ti omap3 hardware branches into prebuilts shouldn't be too hard. Getting it non-permissive will be a problem. I managed to boot up an selinux enforcing rom but it was mostly just errors in the logcat. There is a lot of niggling, boring work to get enforcing right.

I am glad that someone else is using this rom. Sometimes I feel like I am just building into a vacuum.
[Nook Color Android Development] lev777:
I would be happy to try the partitioning zip & flashing the rom if you get them all and the updated CWM/TWRP posted. :good:
[Nook Color Android Development] j8048188:
Is this ROM supported for booting from the SD card or just EMMC?

Thanks for all the hard work. As I don't have the time right now to build, I'll try the flashable version you posted.

I might have to get a build environment running again...
[Nook Color Android Development] bowguy:
I believe the marshmallow security requirements force the SD card to be encrypted so no booting from there.
[Nook Color Android Development] drmarble:
That is correct. Maybe somebody can figure out a way around it. There might be something you can do with fstab and init.

It really just runs on emmc.

I need to post a more current buid. I keep my github reasonably current so home builders should be in good shape.

I am glad that there is still any interest in this. This device is so dated. I am just amazed that cm-13/marshmallow runs on it at all.
[Nook Color Android Development] bowguy:
Are the f2fs-b branches ready for testing?
[Nook Color Android Development] drmarble:
yes. F2fs works fine. It is a bit of a pain to get things formatted for f2fs. The roms work just fine with ext4 partitions too, You would need my unreleased f2fs compatible cwm recovery to use ft2fs. The conventional cwm works just fine for ext4 intalls.

I tried enabling gello. It is just too large. It's size is decreasing so it may fit eventually.
[Nook Color Android Development] genekellyjr:
I ain't experienced enough to figure out how to install this well now, but I'm damn excited to install it eventually!

Just got CM11 working and it's not bad. CM13 should be fun - I picked up an Amazon Fire recently and got CM12 on it but can't go past that. But this old thing can haha!

Edit: Is ART involved in CM13? I tried it in CM11 and it was laggy (the opposite of what pre-compiled should do).
[Nook Color Android Development] SGH-i200:
I'm interested in a current build zip! :)
[Nook Color Android Development] UnstoppableDrew:
I've been meaning to resurrect my old NC, so I'd love a current build zip too. I put some version of CM on it, don't remember what, but it was never quite right. Ran excruciatingly slow, and would just freeze periodically.
[Nook Color Android Development] fattire:
Well jeesh... cm-14.0 is out... what's everyone waiting for?!!! :)
[Nook Color Android Development] drmarble:
I have 14.1 booting. It has trouble with gapps. It is slow. Maybe not quite as slow as cm-13.0.

I will post further details later.
[Nook Color Android Development] drmarble:
I have 14.1 booting. Gapps works now too (open_gapps made a big update which made it smaller and now play services don't crash)

Here is the screenshot to prove it:

[

It has f2fs support (but it isn't mandatory). I doubt it will fit in a standard sized system partition. Mine is 1GB. I still stripped some fonts to make it loadable by adb push.

It is still slow. It feels a bit faster than cm-13.0 but the benchmarks are a little lower. I think the interface just gives one the impression of quickness. It still spends all its time swapping in the background. The fewer apps installed the better.

I will upload a rom Including one with full fonts and cm features that I will NOT have tested. I will also upload the files needed for f2fs capable cwm and a buggy TWRP.

I will also upload my trees to github and try to make a build document.
[Nook Color Android Development] fattire:
I love everything about this post.
[Nook Color Android Development] lorddunlow:
Damn. Fine work. I haven't used my Nook Color in forever and just thought I'd pop over here to see if there was any active development. Never expected to see a Nougat rom in the making. Wow. You guys are the best.

I may have to pull my Nook out and play with this. (I'd have to remember what weird partitions I have set up on it and try to repartition it back to something that can accommodate this.)
[Nook Color Android Development] just_magikkal:
Why the jump to 13? xD personally my favorite version of android thus far is 5.1, so if anyone would be willing to go for building a CM12 for encore I'd love that. I'm no java expert though, bit of a noob to it actually xD
[Nook Color Android Development] Der_Neger:
Hi,

very nice to see that you are still playing around the nook color.

Would be nice if you upload a rom so we could play with it a bit ;)

Nougat on a device this old is something special.

Best wishes
[Nook Color Android Development] rfoster2009:
I'm wondering what will happen now that Cyanogen, Inc. has practically killed CM. Will our NCs see LineageOS perhaps? Who knows?
[Nook Color Android Development] just_magikkal:
I'm not actually familiar with LineageOS. Will research that :D

Are there any other active developments for upgrading the NC to a Marshmallow equivalent?
[Nook Color Android Development] rfoster2009:
Not that I am aware of. The fact things got as far as they did is really amazing.
[Nook Color Android Development] bowguy:
Lineage builds

Hey fattire

Could you post your basic build instructions somewhere?

My link goes to cm and obviously doesn't work. Looking for dependencies, inits, etc. listed in your handy guide

There is a bash shell in win 10 now and for fun I was going to try it instead of virtual box.

Step one would be lineage 11.
[Nook Color Android Development] fattire:
Unfortunately, they didn't restore the wiki in the way I would have liked (via mediawiki) but I do have a back up from Xmas Eve (the night before they removed the original wiki). Here's a cobbled-together version of the encore build page.

Cheers!
[Nook Color Android Development] fattire:
Amazing. Just amazing. OMAP3 4eva!

ft
[Nook Color Android Development] bowguy:
It works!

Thanks for all your hard work. I have a dual boot setup, 14.1 on emmc and cm11 on the SD card. My plan is to sideload titanium backup to emmc, then I can load any app I want from the SD. No need for gapps.
[Nook Color Android Development] Arbelzapf:
Incredible. I need to see this for myself. If only I could find my trusty old nook right now.
[Nook Color Android Development] drmarble:
updated lineageos-14.1 rom

LineageOS upgraded to 7.1.2 so Encore does too. Still waiting on source for 7.2. Here's an updated rom, lineage-14.1-0414_1953-DrM-encore-udb.zip:

https://www.androidfilehost.com/?fid=673368273298947780

md5sum: 0dd4f5f2f347d41dd6f6e746311ba748

I am glad folks like this rom. On the LineageOS statistics page we are now up to 2 (two) installations for Encore. That is a doubling in just 1 week. Back in the 7.1 to 11.0 days Encore was one of CM's most popular devices. I guess it is a bit slow by modern standards. The years have not been kind to this device. Still, glad that folks are enjoying it.

I have been in conversation with a person on irc trying to port LineageOS-14.1 to the Nook Simple Touch. I guess slow matters less when you have an e-ink display.
[Nook Color Android Development] KittenSauce:
The latest version of LineageOS (7.1.2) runs surprisingly well! That is, if I don't install GApps. Otherwise, it's just a buggy mess, heh. Since I can't use the Play Store without maintaining an implausible amount of patience, I sideload APKs. However, this is a little difficult, considering I can not connect to a WiFi network! The moment I try turning WiFi on, it instantly turns itself off. I'm rooted with the latest SuperSU beta - could this be the issue? Sorry if I posted this in the wrong place; any help would be appreciated.

Oh, I almost forgot to mention, I've repartitioned to increase the /system partition to 1.1Gb. Thanks!
[Nook Color Android Development] drmarble:
I am glad you like it. I agree that it is stinking slow if you install gapps. You shouldn't need to root this rom with anything. I built it rooted. I don't think that SuperSU would cause wifi problems but it might. You could try reflashing without reinstalling SuperSU. Unistalling the SuperSU app might work, I don't remember if it has a component outside of the system partition. I think that reflashing and maybe ininstalling will erase it all. You might have to format system from cwm and then flash. That would definitely remove all traces of SuperSU if it does something sneaky with the backup_tool function. I don't think that would affect wifi, but it might.

I have no trouble with wifi. I can turn it on and off and reconnect to different access points. Maybe you could get a logcat and I could look for clues. Be careful posting logcat because they can contain personal information. Mine never seem to but I guess some apps can be somewhat revealing.

Again, I am glad it is working for you. I'll go check my wifi more on the latest feb 14 build.

Thanks for posting.
[Nook Color Android Development] KittenSauce:
I installed SuperSU because CWM was bugging out, and telling me to "fix superuser". Of course, installing SuperSU didn't really shut it up, but I decided to leave it anyway. It's kind of late in my timezone, so tomorrow I'll try formating /system and the bunch, then reflashing the ROM without SuperSU. If that doesn't work, I'll post a logcat (I'll try to remove any personal information). Custom kernels on my Nexus 5 used to require a Wi-Fi fix with Android Nougat, but that's since been fixed, and I haven't flashed any custom kernels on my Nook. Maybe I dropped it at some point, and the Wi-Fi connection got jostled?
[Nook Color Android Development] KittenSauce:
I don't believe SuperSU was the problem, as after formatting /system, wiping data, cache, and dalvik cache, and reflashing the ROM without SuperSU, I still can't get WiFi to work. Here's my logcat.

My exact steps were booting the device, setting it up, moving some icons around, opening Settings, and trying to turn WiFi on twice. It looks like it can't find the drivers. WiFi worked fine on CM11; I guess the source code was changed?
[Nook Color Android Development] drmarble:
That message from CWM about rooting is a bug. It has been around for a while but it is wrong. The rom is rooted.

I recall that I had to do some odd magic to get wifi working. I thought I had it all happening automatically in the rom but it is possible to do it using adb. If you continue to have wifi problems I will try to remember just what I did and post the solution. It has to do with wifi initialization, sym links, read only file systems and other charming things. Luckily, it only has to be done once and persists through rom updates. I hope it was just SuperSU causing the problems.

Best of luck.
[Nook Color Android Development] KittenSauce:
Apparently, all I needed to do was reboot. Heh! The ROM is working fine now (though I'm having a few issues with auto-rotation; not too important). Thank you for porting Nougat to the Nook Color!
[Nook Color Android Development] drmarble:
Glad it's working now. I didn't want to have to rewrite that wifi initialization script/makefile.
[Nook Color Android Development] bowguy:
I can't get the browser to interact. I know it is working by opening two tabs and switching back and forth.

Also titanium backup doesn't get root permission. Tried all the possible settings.

Other than that it runs pretty well. Better than CM11.

Thanks
[Nook Color Android Development] Arbelzapf:
Got it running today as well. Amazing.

Wifi worked after a reboot, but I don't have a working browser either.
[Nook Color Android Development] drmarble:
I can confirm that the browser doesn't work. It was working on earlier versions. I wonder how I broke it. I expect I broke webview somehow. Or, perhaps it is trying to use something from gapps. Maybe some third party browser will work such as FireFox.

Rebooting if usually needed to get it to work well. It alsow takes an hour or so to get all its initialization done. Sometimes it needs a reboot after a few days of use. It doesn't seem to properly dismiss app from memory after you close them. Even holding the back arrow button to kill an app and removing it from the recents display doesn't always kill it. I use:

adb shell toybox top

to look at what is running. You will see lots of io wait because of our limited ram. Google thinks 1Gb is low ram these days.

I'm glad that you folks are trying it out. I've been thinking about building a gingerbread 7.2.4 version. Encore was down right speedy with that rom, and that old kernel had great standby life. Building it would be a challange. I would have to downgrade lots of build tools (java, python, gcc).
[Nook Color Android Development] Tschumi:
I would definitely be interested in a 7.2 version. Nougat on Nook Color is an amazing feat, but I remember the glory days of Gingerbread.
[Nook Color Android Development] xam247:
Going to test this out today but I would also be interested in an older but stable and quick version. It's been a while since I had any desire to pick up my NC because everything ran so slow.
[Nook Color Android Development] bowguy:
I have tried several browsers none seem to be working. I will try a logcat to see if I can find anything but it looks like webkit might be the issue.

I do a lot of browser displays using SVG which gingerbread didn't support.

Do you have a version of roomservice.xml that would build? I think I have most of your repositories but I don't get very far in building.

Thanks!
[Nook Color Android Development] drmarble:
I managed to get the browser to work by updating the webview.apk to google's from 7.1.2. I will try to attach a zip file to a later post. Otherwise, it is lurking in external/chromium/webview/prebuilts/arm/webview.apk. It is still slow as molasses but it does load web pages eventually. The LineageOS folks are working on a new webview based browser, Jelly. It will replace the stock browser. It is a small footprint browser for non-qcom devices like ours. It still needs some more work but it should help us when it is released.

I have no problems with bulding frameworks. I use a few of my own repos and have three patches to /build that need to be applied. Again, I will post those soon. Right now I have some awful illness that is making me tired and stupid all the time. I am sure I would mis-post anything now.

I will put a working build up soon.
[Nook Color Android Development] bowguy:
Is there anyway to post that apk? I would like to test a few small footprint browsers but I can't find it in the file structure.

Thanks
[Nook Color Android Development] jrk190:
I just picked a nook color from Goodwill for a few bucks, ready to play around with roms on it
[Nook Color Android Development] jrk190:
I'd honestly wait and try to build On when it's released, with the Android Go stuff is super fast apparently.
[Nook Color Android Development] ShapeShifter499:
[MENTION=4190710]drmarble[/MENTION] I haven't followed this thread or any of the Nook Color stuff. I landed here after buying a Nook Color as apart of a "ShopGoodwill" auction, wanted the E-ink Kindle but it also included 3 other devices so I ended up with a Nook Color.

Couple of questions before I install anything, but I am interested in installing LineageOS 14.1:

Has zram been enabled or have you tried enabling it? Might help with tight ram constraints.

Is there a way to boot right off the SD card? I have a Nook HD (hummingbird) that I know has this feature.
[Nook Color Android Development] robross0606:
I would love to get hold of a flashable zip or at least an SD Card image for this. I want to special-purpose my old NOOK and it needs to run an app which requires Android 5.0 or greater. It may not be a daily driver, but this would probably fit the bill.

How can I get hold of this ROM? :D
[Nook Color Android Development] robross0606:
Nevermind, I just found the LineageOS post and flashed that. It boots up and runs, but some apps continuously crash (Trebuchet, Settings, etc.) and I have yet to be able to successfully enable Wifi.
[Nook Color Android Development] robross0606:
After a couple factory resets I finally got it to stop crashing and Wifi to work. Awesome stuff! Which Gapps is best to flash on this ROM?
[Nook Color Android Development] bowguy:
Use the smallest gapps (Nano?) possible. Unfortunately adding gapps will seriously degrade performance. Sorry