yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] ieatabiscuit:
Ok, reflashed, checked numbers before flashing GApps, and after. Before I was actually running system at about 390MB, and after flashing a different GApps than i had before, I'm sitting closer to "normal" at about 450MB. Looks like the CM12 GApps from their page is a bit on the fat side. Needed something more slimmed (just the base for Google Play, that's all I really wanted on the tablet anyway.) As for the post about my phone using low RAM, I have a screen cap, but won't let me do attachments, pops up a window about not having more than 10 posts yet. System is using 182MB, Apps are using 366MB, and I have 1.2GB free. It's on a One (M8) with 5.0.1 on it. Maybe the ROM is reporting back wierd numbers, but you can see how that would make someone think 450-480 is high (more like 1/2 to 1/3 than it is 1/4, but still, it's crazy numbers).
[Nook HD, HD+ Android Development] robak1965:
I use the following pa-gapps (micro size works best IMHO on nooks):

http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html

Here's the pa-gapps comparison chart if anyone's interested:
[Nook HD, HD+ Android Development] king200:
You might want to look here for gapps too	[GAPPS][CM11][CM12][4.4.4][5.0.2][5.1] Delta Gapps With Modular Addons (All DPI) http://xdaforums.com/showpost.php?p=58047099&postcount=1
[Nook HD, HD+ Android Development] ieatabiscuit:
Haha, that actually IS the one I'm using now. Did the trick quite nicely for me too.
[Nook HD, HD+ Android Development] kdejong2012:
I'm on CM 10.1 (4.3.1) and want to make the switch to LP. It's my wife's Nook so it needs to be very stable or I hear about it A LOT. I tried KK builds but could tried a few builds but at the time they were not stable enough. I think it's time to try Amaces LP build since most people are saying latest build is very stable.

I wanted to confirm proper steps to update. I've downloaded TWRP, 0414 build, and gapps. I assume i should perform a factory reset / wipe clean to start fresh. Can I then install TWRP from current recovery or should I use flashify to insall TWRP? After TWRP, I need to install LP rom and gapps? Can someone confirm if this is correct? I dont plan to use SDCard install but rather install from EMMC. I've looked through Hashcodes's thread and this one and havent found the exact steps coming form 4.3.1 based rom. Apologies if I missed the details I'm looking for.
[Nook HD, HD+ Android Development] twiztid_:
You may want to try installing it to SD card first if ensuring stability is that important. Either way, after installing TWRP, be sure you make a back up.

I use lollipop exclusively, but there are still some apps that have issues with it. Its stable, as in it doesn't crash, but I have Disable HW Overlay turned on under Developer Options. Without it, the keyboard, and/or drawer cause flickering and reboots.

As for the steps, I literally just posted them this morning to someone else who claimed they couldn't find them.
[Nook HD, HD+ Android Development] kdejong2012:
I found your previous post which validated the steps I listed in my original post - so thanks . It's been a while since I installed rom on sd card so need to re-familiarize myself with that process again now. Will make sure to make backup before and after TWRP install. My wife mainly uses tablet for Kindle app, Facebook, and browser . I'll make sure to turn off HW Overlay. Thanks again.
[Nook HD, HD+ Android Development] g002ahe:
I have been trying to make this stable and have followed the advice of the above poster.

You have to disable HW overlays in the developer settings. This seems to fix all problems.

I have set up tasker to automate this as it reset every reboot

This info should probably be included in post #1 as it is critical.
[Nook HD, HD+ Android Development] TeutonJon78:
The TWRP images are in IMG format, so you need to use Flashify or put it into a flashable zip (just find a TWRP install flashable zip and replace the file in it with the new one). I think the new TWRP can flash IMG directly (might be wrong), but that doesn't help get it on.

---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------

Is Netflix working cleanly on this ROM yet, or is it still having trouble?
[Nook HD, HD+ Android Development] keshabbhattarai126:
VPN not working

Though this is not a must have feature for me but I like having this feature. I tried Pisphion, hola vpn, droid vpn but none of them worked properly. Some connected to server but internet access was not present and some simply could not connect.
[Nook HD, HD+ Android Development] hallanthony:
After the positive feedback for this build I thought I would give it a go, however I'm struggling to boot into recovery? Recovery is currently cwm, but have tried using flashify to install twrp instead but that's failing too. After reboot from flashify it still reports current recovery is cwm???

Any ideas? Cheers
[Nook HD, HD+ Android Development] keshabbhattarai126:
Once I flashed twrp image, no errors but still there was cwm, next boot took me to twrp. I flashed zip files.

I was able to boot cm12.1 . Perfectly fine. While rebooting to recovery surprisingly there was cwm insted of twrp. I was shocked. What was happening?? I don't know !! amused!!
[Nook HD, HD+ Android Development] g002ahe:
For those struggling with recovery why not create a bootable microsd with twrp plus the ROMs. Really quick and easy if you have a microsd handy.
[Nook HD, HD+ Android Development] amaces:
You'll like the incoming experimental build even better :)
[Nook HD, HD+ Android Development] twiztid_:
Damn you amaces! My montly bandwith cap can't take your awesomeness!! :D
[Nook HD, HD+ Android Development] vinceweis:
It is working great! You are on a roll with this.
[Nook HD, HD+ Android Development] amaces:
Just imagine my Box bandwidth :( God bless those gigabit SK people who download the whole folder every time ;)

We're getting close to the bottom of the bag of tricks though… I guess another jump will happen with the switch from memory carveouts to dynamic CMA, but that's not short term stuff.
[Nook HD, HD+ Android Development] lixxus:
Hi guys,

just wanted to report that i have updated to 14/7 and the flickering is still there on the hummingbird when "android upgrading"

after it finishes updating and completing boot it still flickers. However when i turn off the screen and back on it goes away.

It is also not there when i reboot. it only seems to be present when updating on the initial boot.
[Nook HD, HD+ Android Development] ieatabiscuit:
That's interesting, my hummingbird usually outperforms my ovation, since it has the lower res screen I assume it has an easier time with such similar hardware. I'll pop this into ye olde hummingbird right away, and see if I get the same thing. As for my Ovation, so far, I haven't tried the experimental, but the 7/14's been great so far.

Update: Tried a few newer ones with the hummingbird, worked like a dream. The ONLY thing I had found was that there was some bluetooth software left out of the kernel which was addressed by [MENTION=4473900]amaces[/MENTION] last night. Now we just wait a bit for the updates to come down from ovation to hummingbird, and it SHOULD be all gravy. If you haven't yet, try the 7/16 build, and if he's posted it yet, go for the newest possible. It's near perfect.
[Nook HD, HD+ Android Development] TBueno:
Care to elaborate on the improvements over 0714 build? Snappier performance maybe?
[Nook HD, HD+ Android Development] andtron:
Hi Amaces,

On your airend/android_kernel_bn_omap build, what revision are you currently using? The devices.xml lis on the box.com is g-3, and is no longer valid.

TIA.
[Nook HD, HD+ Android Development] amaces:
Have been rebasing my kernel changes into distinct features branches for a week now, which will make it easier for cherry-picking upstream. Anyway, finished yesterday, with the benefit of upgraded zRAM/zcache/frontswap, a newer F2FS backport, which also brought back the .101 kernel. Will move these builds into stable soon.

Just updated the repo list file, and I should probably update the manifest as well… There all on the cm-12 branch now ;)
[Nook HD, HD+ Android Development] asakurato:
For some reason, 07/07 and 14/07 build are lagging for me, previous builds were fine. Installed both with clearing cache, using latest twrp. Any suggestion?

Edit: Lagging got better, still there. Aaaaaaaand, flickering is goooone :D Especially in fb messenger :happy:

Edit2: Now that system has settled, most of the lag that I had in previous build is gone now :good:
[Nook HD, HD+ Android Development] amaces:
Uploading full ROMs just for a few updated kernel modules was getting ridiculous, so I spent some time setting up a kernel ZIPping script (boot.image, plus /system/lib/modules magic). These flashable kernels should work even with older ROMs, with the added benefit of not having to wait for the cache regeneration step. Modified a few kernel build optimization flags today, so test out the (small) flashable kernels in experimental. Beware that there are no ro.product.device asserts for now, so it won't stop you from flashing the wrong device kernel…

That's certainly odd, and I don't think it's the same underflow bug we've been wrestling with… Is it something that started recently, or has it been there since Hashcode's February build? Flickering before fully using the device has never happened on ovation, and hummingbird had a much easier job already, although I accept the possibility of different chipset binning. Most likely that's not the issue, and a good clean install, maybe even a simple cache plus Dalvik wipe, could fix it. Otherwise, you'll have to send log output.

More kernel tweaks to test beyond the latest ROM; see the info about flashable kernels above. P.S. There really shouldn't be any UI degradation between today's ROM/kernel, and the 07/06 build, but do post feedback if that continues to happen in your case.
[Nook HD, HD+ Android Development] extrem0:
Congratulations [MENTION=4473900]amaces[/MENTION]. I'm impressed in what you achieved in quite small period of time for "someone who considered didn't had the sufficient skills to do so" . You used to say that in hashcode's cm12 thread when you still hadn't created this one but already shared your builds with us. I know you gather contributions from others developers (including hashcode in kindle fire HD, besides his initial device tree which is already a huge contribution) also from users providing their logs. It appeared impossible to reach cm11 performance in cm12 builds but looks like you could do it. I'm wondering how our nooks would perform with a 3.4 kernel if we'll ever get it.

Anyway, thank you for your excellent work and for keep our nook up to date and stable!

Also, it's good to see how's your communication in this thread with us users. People use to ask more than developers are available to provide (like when people ask for changelogs or newer builds when devs doesn't have time to do so) and you always answer very politely and accurately. I've seen developers stopping sharing their works because of this. It's really nice to see this here.
[Nook HD, HD+ Android Development] andtron:
I totally agreed with extreme, you are the one almost single-handedly make this release the way it is now, and yet you kept giving credits back to the others.

I salute you for your hard works and tenacity, take a bow man, you deserve it.
[Nook HD, HD+ Android Development] belfastraven:
Ditto from me, too, amaces.

Also, I am running the latest kernel from experimental and the 7/16 rom on my HD. Everything is running well. I notice that on the last couple of builds the readahead buffer is back at 128--I seem to remember it being 256 before, and I did have it running (TricksterMod) at 512 with no problems, but didn't really see much difference, subjectively. If there is anything else you would like me to try tweaking, let me know.
[Nook HD, HD+ Android Development] ieatabiscuit:
I wanted to say thanks again also. I wish my two cents added more than it did, but this ROM has been fun to test. My wife hates it, because I stay up tinkering, but that's OK. So far the 7/16 build is great. I did notice that my daughters fitness band did not want to pair in Bluetooth, when it used to, but given the win with stability, I can't complain at all! We can save that little issue for later, when I am able to give note information than "my Bluetooth broke with xyz device".
[Nook HD, HD+ Android Development] Shermanballz:
Okay, I hope I've got an easy issue that gets me laughed out of here. I know there have been a couple people with Titanium issues.

Let me first say this ROM is sweet. So sweet that when I heard the flickering issues were resolved, I wiped everything and did a clean install. Now I have an issue

So here's the deal: cannot restore from Titanium (hangs. already troubleshooted using Titanium suggestions: no luck). Also many apps from Amazon will not install. Don't know for sure, but it seems to be apps that want to install to SD.

I actually had this issue crop up on a couple of CM11 based ROMs and on Hashcode's CM12 until I saw a post that helped me fix it:

http://xdaforums.com/showpost.php?p=59671558&postcount=607

It basically said to go to Settings --> Apps, hit the menu in the upper right, and change the Preferred Install Location. It worked. But I do not see that option anymore.

Has it been moved? Or is there another way to change it? Or do you think it even matters?
[Nook HD, HD+ Android Development] Zippy Dufus:
Perfect !

I just built 07/17 out of your kernel cm-12 repo:

Can confirm that the flicker is gone.

The reproducible reboot I got on a 07/14 build in the Calendar widget is gone.

Checked all my other use cases where there has been trouble in the past - no problems!

This snappy ROM is the best ever for this device!

Thank you!!
[Nook HD, HD+ Android Development] asakurato:
Device got more stable and less laggy after newest build in fact
[Nook HD, HD+ Android Development] twiztid_:
Anything exciting in the 0717 experimental build?

And is the kernel the same as the zip?
[Nook HD, HD+ Android Development] lixxus:
hi Amaces.

i have tried as you suggested even though i did the same before installing your 12.1 build. i did a complete clean reinstall and it still flickers when upgrading dialogue box boots. its not doing it now because as i explained once i turn off the screen and turn it back on . the flickering is gone. also when i reboot the problem is no longer there.

so the problem seems isolated to when i install a new build or upgrade for some reason.

also will the output log show anything ? if so how do i go about providing you that

many thanks
[Nook HD, HD+ Android Development] twiztid_:
Come for the Nook HD builds...

Stay for the snarky quips. :D

Thank you so much or all your work amaces, and a bit of humor too!
[Nook HD, HD+ Android Development] 9.3x72R:
^^^ This ^^^

A big thank you from me as well.
[Nook HD, HD+ Android Development] pastordl:
Installed the 6/17 kernel ran fine. Then updated to 6/17 rom another winner. Fantastic and no problems. Many thanks. [MENTION=4473900]amaces[/MENTION]

Noted that the kernel was different than the one in the ROM. Is there anything to test or try that might help you in any way.
[Nook HD, HD+ Android Development] Jon Lee:
Awesome job!

I do have an ulterior motive. A HWC with full writeback(WB) support is needed to enable the video component of screencasting. Our kernel dss already supports it. I believe Hashcode has a tree that has a HWC with WB support also.

https://github.com/SciAps/android-ti-omap4xxx/tree/phytec-ksp5012/hwc

BTW, There's some really good stuff here:

https://github.com/SciAps/android-ti-omap4xxx/commits/phytec-ksp5012

https://github.com/SciAps/android-frameworks-native/commits/phytec-ksp5012

Edit: Oops! Wong link.

https://github.com/trevd/android_hardware_ti_omap4xxx-archos/tree/master/hwc

(search for 'wb'...)

https://github.com/trevd/android_hardware_ti_omap4xxx-archos/blob/master/hwc/hwc.c
[Nook HD, HD+ Android Development] asakurato:
Don't know if it's YouTube or rom problem, but most of the time when I open video on YouTube, it crashes without any message, or it crashes when video just ended and I press back. It also crashes when I lock the screen while video is still opened
[Nook HD, HD+ Android Development] mattyyey:
MD5 check sums? installation problems....

Hi, I've been using this for ages and its great - even with the HW overlay bug (tasker was disabling it for me ;) ). I have not updated in a long while... I went to update yesterday, and I couldnt get it to install at all.

So first I updated recovery to twrp 2.8.7.1 from your box. I like it. :)

Previously I was on 20150414-0425 ovation. (SElinux permissive + 3.0.72+ kernel)

I did factory reset, went to install and it started and just hung on the words "patching system unconditionally" I left it 3ish hours since it was on charge anyway. No movement. I held the power button and rebooted recovery. Tried a second time, but only gave it 10 mins, same effect. powered off. Then this 3rd time I noticed it said it could mount /system in recovery. So I didnt try flashing again, I just formatted n restored my old rom. Worked. phew...

I then re-downloaded the file two times more and created a MD5 to check them, they were all 3 identical. It was: 4DC0E8E75B15BEBFCB2B99546B35A977 Is this correct for the 20150716-UNOFFICIAL-ovation?

I have tried a few things like installing an old rom and restoring different backups, and formatting system, my system is fine and works, but it needs reformatting each time I power off during installation. Understandable.

So I then read in the thread several people had tried this build in combo with the experimental kernel. 04/14 with the new kernel, installed fine, I wiped cache and dalvik for good measure, it wouldnt boot. Yes I know I could get a logcat for that but its not vital to my problem really as I still wanna update. I then booted into recovery, did a factory reset, and attempted to install the 07/16 rom again, thinking the new kernel and bootloader, might have fixed it... NOPE Still wouldnt even install past patching system. Can i get you recovery u log somehow maybe? something that saying more than literally patching system unconditionally...

My Md5 for the kernel-ovation is 282965969B39AE576FFFC78D1DD19627 that right?

I have just tried 0717 from the experimental folder now.... still patching system... :crying: I'll give it some time... md5: 545EA9F67A70532B53F0118824711B14 EDIT:10 mins later still on patching system unconditionally. Note all my installs are from the external sd.

Please can you check these checksums, or do you have any advice? No matter what seems to happen at least I can restore my nandroid.

cheers
[Nook HD, HD+ Android Development] bhuffman:
Failure connecting to wifi

[MENTION=4473900]amaces[/MENTION] - I can not connect to my wireless AP with this ROM. This has been a problem since I've started testing CM12 on the ovation (although it may have coincided with a change in APs). I know it works on other CM11 devices (kindle fire) and non-CM android devices.

The one thing that seems to be unique is that I am running the AP with the SSID hidden. I have been able to get the device to connect to an open AP with broadcast SSID. Is this is a known issue with CM12?

Logcat and /proc/kmsg attached.

Thanks,

Brian
[Nook HD, HD+ Android Development] ieatabiscuit:
How old is your sd card, or rather how much use has it seen in it's time. I had a similar issue that caused a lot more craziness when I actually did get something to boot, and it was literally ALL due to a worn out sd card. At the very least, it's worth a shot.
[Nook HD, HD+ Android Development] mattyyey:
Wow. Not a single sign the card was on the way out... its barely used, and is only about a year old. However using a 2gb card (my super old HTC hero gold card) it's installed. Thanks for the advice.
[Nook HD, HD+ Android Development] ieatabiscuit:
Same thing happened to me. Card was maybe a year or two old, but used for flashing a lot. No sign of it going, just saw weird things going on, and stumbled on the reason by mistake. I just wanted to pass on my experience there. Glad it helped.
[Nook HD, HD+ Android Development] amaces:
I definitely like this :) WB support in HWC would be nice (regardless of screen casting), but I'm most excited about making frameworks use the 1.1 API. I knew this stuff was floating around, and it's on Hashcode's agenda, together with DDK 1.12, and K3.4, but our current DDK 1.9 already supports API 1.1 I think, and the d-jb-mr1-release HWC has those patches. This might be the easiest path to test API 1.1, at least with my current understanding.

Yes, I noticed that YouTube would crash after playing a couple of videos with the July 14-16 HWC. While relatively harmless, I had planned to look into whether it's due to the many frameworks/av changes in the middle of the week, or our HWC stuff. YouTube on 07/17 seems stable though, so I can't tell for sure what the cause was (made HWC changes, but CM has been fixing stuff as well).

Flashing these ROMs in recovery should take a couple of minutes at most, so no point letting it run beyond that. P.S. Since you're doing clean installs, better format /data and /cache as F2FS, if you haven't already.

All your checksums are correct, so it's not a download issue. On a related note, I decided not to clutter the folders with md5sum files; it's been years since I had a bad download, and Box is pretty reliable. Otherwise, you don't need to reformat /system (or any partition) every time; CM's scripts construct a temporary image by merging the few file with backup support in addon.d (i.e., AdAway hosts, GApps) on top of the clean system.new.dat in the ZIPs, which is then flashed over /system, regardless of whatever else is there. Manually formatting /system is mainly for those backup scripts, although you could simply remove the whole addon.d folder.

[MENTION=6326205]ieatabiscuit[/MENTION] to the rescue :) I'll just add that this should really not happen with a decent SD card, even after thousands of flashes… That card was on its way out very early on.

I will look through the logs, but I do know that a hidden SSID is a good way to prevent my stock Nexus 5 to connect to certain signals. If security is your concern, I can assure you that the bad people can totally bypass the hidden part ;) CCMP, or even better, enterprise ciphers/key management, is as foolproof as can be…
[Nook HD, HD+ Android Development] bluecopper:
Hi guys. About to install 07/17. Which kernel is embedded in the rom?
[Nook HD, HD+ Android Development] ieatabiscuit:
3.0.101+ alchemy #6, the flashable kernel is 3.0.101+ alchemy #2
[Nook HD, HD+ Android Development] bluecopper:
OK thank. Which is the better performer?
[Nook HD, HD+ Android Development] ieatabiscuit:
I tried them both but didn't notice a huge difference. I think one is supposed to have more Bluetooth commits, but performance wise, I decided to stick with what came with the ROM on my ovation. The Bluetooth commits I need are for the hummingbird.
[Nook HD, HD+ Android Development] 3c57x9:
Awesome thread!

I must say I had my Ovation sitting in a drawer until I came across this thread. It's been transformed to a completely new device. Thanks a ton