yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] TBueno:
My subjective results:

Ovation-1011 brings no visible permormance improvements over 1004, although RAM seems to strecth a bit further. Everything runs as it should and it's very stable.

Ovation-1012 seems to be built for speed, it's probably the best performance the HD+ has seen in a while. I haven't tested it for video as thoroughly as others in this thread, but Netflix and YouTube worked. HOWEVER, Chrome went blank a couple of times for a few seconds before showing the page I was on again, and Firefox had the device (hard) reboot on me in the middle of a casual browsing session.

That sudden reboot reminded me of CM10/11 days, and it's the single reason I don't miss them a bit. Chrome "fainting" and recoverying were probably almost-reboots, so I'm guessing 1012 is the one with "possible stability issues". I'd trade that marginal speed improvement for better stability any day, so I'm back in 1011 for now.

In short: both run well and have good memory management (home screen can survive longer browsing sessions than 1004 without reloading), 1012 has the edge on speed but makes the HD+ less reliable.

[edit] 1011 gave me a very sudden (soft) reboot too when trying to open a site in Firefox from a link in Feedly... so both build seem to have some stability issues
[Nook HD, HD+ Android Development] neutronjeff:
Which launcher are folks testing with? (Trebuchet, Google Now, Apex...?)
[Nook HD, HD+ Android Development] zenlifexxa:
[MENTION=4473900]amaces[/MENTION] 10/11 build (hummingbird) worked like a charm. No more accelerated" video playback in my HD.

Many thanks!
[Nook HD, HD+ Android Development] Mac Hosehead:
I tried both hummingbird 1011 and 1012. 1011 seemed nice but it didn't want to sleep. Other than that I didn't have any stability problems. I am now running 1012.
[Nook HD, HD+ Android Development] amaces:
Yup, I got to test it last night, and sadly, screen casting is still half broken. Will keep looking for a solution, I guess.

It's called Ambient Display in settings, and it's supposed to wake the screen in response to notifications, sensor inputs (e.g., picking up the device), etc. So yeah, much more useful on a phone. There was a request, so I enabled the capability, as I was curious myself. If it automatically enabled on your device, you can turn it off (same as with Live Display) although your lack of keyguard might have disabled it.
[Nook HD, HD+ Android Development] MossyTC:
Give me a way of identifying the relevant repos or a list of repos to include or exclude and I'll change the script accordingly.

The timestamp doesn't need to be part of the filename, you can just publish it here in this thread, maybe in the OP?
[Nook HD, HD+ Android Development] amaces:
OK, I needed a semi-automatic way tied to when I repo sync, so I made myself an alias repostamp='date -u >> ../Box/repostamp.txt && reposync', which keeps appending UTC timestamps to repostamp.txt in that Box folder. I will only append relevant syncs, before starting actual builds, and this way you have sort of an incremental log. Also, I started making a list of the repos that we actually use (see repolist.txt). As of now, it's only our device-specific code, but all will be included as I parse the main manifest.
[Nook HD, HD+ Android Development] famewolf:
Where is the "proper gapps" for this rom?
[Nook HD, HD+ Android Development] illyfilly:
i did all the steps, but i get a constant Google Play Services error and can't do anything at all.

I tried to search the thread and nonthing has come up.

Installed the latets Gapps from here: http://d-h.st/users/dhacker29/?fld_id=27426#files

and used the gapps-lpmr1-20150503-signed.zip file.

is my problem with google play services crashing a gapps problem or something else?

thanks guys for a great ROM
[Nook HD, HD+ Android Development] vinceweis:
I kept having the same problem, but I was mostly dirty flashing over an older version. I finally did a complete wipe and reinstall of everything and the problem went away. I assume it was something left over from the previous rom.
[Nook HD, HD+ Android Development] king200:
Clear data and cache from play services, google services framework, playstore, and delete your google account. Reboot and you'll be asked for an account and start over. If that doesn't work, do an advanced wipe of /sysetm and reflash the rom and a different gapps.

I've been lucky with gapps http://fitsnugly.euroskank.com/?rom=banks&device=gapps
[Nook HD, HD+ Android Development] andtron:
Thanks, king.

Before your link to euroskand, I tired many many different gapp of 5.1. And this one works, no need to wipe the data partition.
[Nook HD, HD+ Android Development] hyun5suk:
I have installed cm12.1-20150502 to my hummingbird.

It seems to be ok till now.

Battary guage is ok, sound is ok, and recharge is ok.

It looks good.

I am very thanks for your great effort.

Thank you again.
[Nook HD, HD+ Android Development] tj2003:
I installed the ovation 5/2/2015 build . I have attached the log when trying to use chromecast. Still the same audio and no picture. Firestick picture no sound.
[Nook HD, HD+ Android Development] Jon Lee:
Looks like the major issue is that a permission needs to be added to the launcher3 AndroidManifest.xml.

I haven't looked at cm12 lollipop's source...

https://android.googlesource.com/pl...her3/+/kitkat-mr2-release/AndroidManifest.xml

<permission
android:name="com.android.launcher3.permission.RECEIVE_LAUNCH_BROADCASTS"
android:protectionLevel="signature"
/>

As far as the firestick goes., try this...

adb shell setprop media.wfd.use-pcm-audio true

https://android.googlesource.com/pl...+/e7bd24af08ef0722fb124a550662bcec48c56f86^!/

Also, this patch needs to be implemented, I think.

https://android.googlesource.com/platform/frameworks/av/+/3a0ef0d^!/
[Nook HD, HD+ Android Development] techdudepro:
Do you know if the Blend Boosted mod will work with this 12.1 build? http://xdaforums.com/showthread.php?t=2603767

And THANK YOU SO MUCH FOR ALL OF YOUR AMAZING, HARD WORK!!!
[Nook HD, HD+ Android Development] king200:
I'm not sure exactly what is being tested. I just used the Chromecast stick and Chromecast app on HD+ and Netflix cast video and sound w/o problem.

Which app are you trying to cast?
[Nook HD, HD+ Android Development] tj2003:
I know it works correctly if you cast from Chrome or from Google play movies using the cast from inside the app. When you try to use the chromecast app to cast you do not see anything from the tablet on tv whether using Mx Player or just seeing home screen no video is being cast.
[Nook HD, HD+ Android Development] extrem0:
He's talking about screen cast (mirroring). It works in cm11 but not in cm12 yet.
[Nook HD, HD+ Android Development] king200:
I read the reviews in Google Play regarding Allcast and judging from that I think this is a CM 12 problem and not unique to this rom.
[Nook HD, HD+ Android Development] MossyTC:
ChangeLog Apr 14th -> May 5th

Attached are the commit comments from all the repositories between the Apr 14th build and the May 5th build. As I don't have an exact time for the May 5th build some commit logs maybe erroneously included/excluded. Some of the repositories included may not be relevant to hummingbird/ovation.

[MENTION=4473900]amaces[/MENTION] The script now takes repostamp and repolist as input. If there is a manifest or other file that lists the relevant repos (or has information from which I can determine the relevant repositories) then please point me at it.
[Nook HD, HD+ Android Development] aoleary:
Hi Amaces.

Can we use replacement lockscreens on this ROM?

I cant seem to change the standard lockscreen.

Thx
[Nook HD, HD+ Android Development] starbright_:
What are the missing features/problems with the current CM12.1 ?

Is it stable enough to be used with WLAN, bluetooth?

What about power consumption?

Will it become official next?
[Nook HD, HD+ Android Development] aoleary:
It is very stable.

The main issue is with screen casting, but has very little bugs in it. It is prefectly usable day to day
[Nook HD, HD+ Android Development] asakurato:
I haven't flashed any kernel separately in a while. I hadn't any stuttering in 10/04 rom nor in game, neither in videos.
[Nook HD, HD+ Android Development] pastordl:
[MENTION=4473900]amaces[/MENTION] updated xposed and 10/12 running now? Will try 10/11 in a day or so. So far running fine.
[Nook HD, HD+ Android Development] MossyTC:
The battery drain may be fixed upstream soon.

Edit: Never mind, I was reading the wrong thread.
[Nook HD, HD+ Android Development] brenyoka:
using 12/10 ovation build after a clean install, and video stutters for me as well. Both in youtube and in videos I watched in the latest vlc player.
[Nook HD, HD+ Android Development] amaces:
So, not so blind testing anymore, given the feedback and discussion so far ;) No point delaying another experimental batch (10/13, also won't trigger re-optimization). About the differences between earlier builds:

Kernels were the same, i.e., the ones posted last week. That means optimized for speed, with most of the bells and whistles that a 4.9.4 toolchain allows.

The 10/11 ROMs were also full of optimization flags, same as the past couple of weekly build sets. Basically, 10/04 with the latest experimental kernel should feel the same.

The 10/12 builds rolled back the aggressive ROM-side optimization flags, after I feared stability issues, and what I perceived as memory “twitchiness”. Those may have been flukes.

Now, I still didn't expect that going back to the normal CM (read mildly-optimized) build flags would break things, so I decided that maybe the bleeding-edge Android EABI was too much. Thus, in the 10/13 builds, I'm going back to the better tested (yet still optimized) Linaro toolchain (both ARM & Android EABI). The optimization flags are similar to 10/11 (-O3, Graphite, alignment & neon tweaks, etc), with some cleanup and additions.

I did test optimize for size flags in both kernel and ROM; more is not necessarily better, and one goal was better memory use. Alas, the kernel seems way buggier with -Os, but it may be worth pursuing optimize for size for user space. I did modify the kernel Makefile to cascade everything based on setting CC_OPTIMIZE_FOR_SIZE, so people can do more testing with one simple configuration change. As of now, I only know that aggressive optimization brings back acceptable 1080p playback in YouTube after all the upstream changes (60 fps is still MIA, I think).

Probably because you had the latest experimental kernel on top of 10/04 ;)

Huh, that's opposite from my experience, expectations based on what I wrote above, and other reports… 10/11 should be the faster, smoother build, albeit with some stability issues. Either way, see if 10/13 is a good compromise.

I think 10/13 will have fixed that. Assuming you have 5-10 GBs of free SD card space, do keep a good snapshot of your /data (compression helps).

So, it was Xposed after all ;) BTW, that's due to changes in actual upstream AOSP, so CM is blameless this time.

Wait, how does this affect us? Unless I'm reading it wrong, these are fixes in the init scripts for a completely different device. Remember our debate about changelogs, and the issue of filtering out irrelevant repositories?
[Nook HD, HD+ Android Development] asakurato:
Stuttering is fixed, thanks. Also, I usually have at least 5gb free on internal sd.
[Nook HD, HD+ Android Development] jaiong:
On cm11, apps full.

can this move apps to sd?
[Nook HD, HD+ Android Development] games906:
Soooo I ran into something big this morning...it seems I've lost root. I was using es file explorer (root functions) and it said root operation failed. I went to see if root was checked in developer options...but it wasn't there. I then proceeded to the Super Su app to hopefully reinstall it but it wouldn't allow me to. Any thoughts? It's a flashed the October 12th build over a the November 6th one. I've been too lazy to charge the nook hd+ because of how complicated the charging process is but its charged now.
[Nook HD, HD+ Android Development] TBueno:
All of us who didn't use SuperSU did, it's been extensively discussed just a few pages back. Flash it through recovery.

Now that's intriguing.
[Nook HD, HD+ Android Development] games906:
Thanks- guess I didn't go back enough pages
[Nook HD, HD+ Android Development] dbrickg:
Hmm, yes, "intriguing"! What do you mean by complicated?
[Nook HD, HD+ Android Development] games906:
So when the nook hd+ completely dies, you have to plug it up (like any device). But when you do, the indicator has to stay orange. It'll light up green, flicker between green and orange, then stay orange. Usually it'll do that, but then it will turn off, causing the process require repetition. If you're lucky it'll flicker to orange and stay orange until it's charged enough for the backlight on the HD+ to turn on. Once that's on, the indicator will turn green again. I have to plug and unplug the pin over and over until its orange- then it'll charge. If you unplug AND try to turn it on before it has enough juice to turn on fully, you have to restart the whole process.
[Nook HD, HD+ Android Development] dbrickg:
Wow! That is complicated. Glad you got it recharged finally. I guess I'd never realized how complicated it was, but I'd never let the nook discharge completely. Oh, wait, I take that back. My wife's nook fairly often discharges completely, but I've never had any difficulty just plugging it in. It always recharges without any flickering lights or plugging and unplugging. I wonder if there's some hardware problem with your nook. Has anybody else encountered that complicated charging problem?
[Nook HD, HD+ Android Development] belfastraven:
[MENTION=4473900]amaces[/MENTION], I have uploaded 2 screenshots comprising the memory states listing from Process stats from developer options on my HD, showing about 24 hours on the hummingbird 10/13 in the experimental folder. It seems pretty smooth to me, no in-app lag or video problems with my normal use (NYTimes, Google Newstand, GMail, Chrome_dev, Amazon Kindle, and a few other reference or data logging apps) . It seems to manage memory better than the 10/11. I 'll check again after 48 hours....
[Nook HD, HD+ Android Development] belfastraven:
24 hr statistics after 48 hours...
[Nook HD, HD+ Android Development] sutty86:
Still can't install new ROMs once installed through cwm I get Google issues ( aosp) tried flashing stock open gapps and now get insufficient storage space in cwm
[Nook HD, HD+ Android Development] Scorchgid:
I used your version same result. Do I need an internal recovery to installs this correctly, I am currently using a recovery from the SD card.

I will trying waiting for the next version.
[Nook HD, HD+ Android Development] Shermanballz:
Using experimental: lots of installed apps (mostly games for my kids), but I mostly use Reddit Now and browser. Always had issues loading animated gifs, but now even still images have issues. Overall seems less responsive than before. Will try the other version given time. Thanks again!
[Nook HD, HD+ Android Development] dkuku:
hi - I have problems to setup the device to have screen on all the time.

Tried to use options: keep screen on while charging and also keep screen on while adb debugging but it always turns off n matter what I set.

Can someone confirm that this problem exist on all devices ?
[Nook HD, HD+ Android Development] sutty86:
Tried installing twrp over cwm and it says it can't be done something like this device needs ovation,but my device is ovation HD+
[Nook HD, HD+ Android Development] twiztid_:
Nook HD+ = Ovation.

Nook HD = Hummingbird.

You need to use something like Flashify to flash TWRP from within a ROM, or possibly a bootable TWRP or ROM? Check Verygreens post for a bootable stock/CM ROM.
[Nook HD, HD+ Android Development] jt61:
yeah, I deal with that - esp. when shutdown isn't working (e.g. plugging in or unplugging triggers a boot)

it also doesn't help that I'm still dealing with a battery issue I've mentioned here before, where it'll go along nicely for a while, battery capacity dropping at a reasonable rate, and then all of a sudden crashes to 1% from wherever it is (70% or whatever)

I tried one of those "battery recalibration" apps, but it didn't seem to help - battery certainly may be shot, but sure seems like more of a battery management system issue
[Nook HD, HD+ Android Development] ieatabiscuit:
Try things with the SD card out. It is very finicky about that, and is known to cause battery issues, and charging issues. It's a sign that a card may be starting to fall, and our devices being so finicky tend to over exaggerate things.
[Nook HD, HD+ Android Development] games906:
I haven't used an SD card in a long time (a few months)
[Nook HD, HD+ Android Development] ieatabiscuit:
Might be a worn out charging cable pin, or a dirty one.
[Nook HD, HD+ Android Development] amaces:
That shouldn't happen on any recent build, especially the last experimental ones. I'm using Sync for reddit a lot; here's typical GIF rendering in that app: https://goo.gl/photos/q1fj5tJjDkNXSjgs7. Maybe something in background is sapping your resources? You could try a clean install.

That means your current recovery doesn't report the device properly; I package everything with device asserts exactly because people were installing raw images onto the wrong device… Still, you can bypass that if you extract the raw recovery.img inside the package. As long as you have some sort of OS running (recovery is just a stripped down one), you have at least a couple of options now.

The easiest, as [MENTION=5720705]twiztid_[/MENTION] pointed out, is using Flashify with the recovery.img. Don't tell Flashify to download the official TWRP image. The packaging of CM12.1 nightlies changed in mid August, and official TWRP doesn't support the new scheme yet, but my customized recoveries are OK (if tagged 2.8.7.3 or higher).

If you don't have some sort of rooted Android installed, thus no Flashify, you can operate directly in the current recovery. Basically, adb push the new recovery.img, then dd if=<path to recovery image> of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery, inside adb shell (the procedure described in the OP).

P.S. Unless I'm taking crazy pills, the 10/18 builds are definitely improved.
[Nook HD, HD+ Android Development] sutty86:
Both of you thank you for your replies, the tablet us defiantly ovation, I cannot download anything on the tablet as the keyboard forces closes, just literally get bombarded with force closes aosp here and Google errors, I have tries different builds BTW .

Builds flash fine just can't get any Google apps to work,I've flashed open gapps , nano,pico,stock, full etc tried other gapps too...

So I don't think there is a way to flash using flashify and im useless with adb!!!
[Nook HD, HD+ Android Development] snoozer854:
The 10/18 build is working great on my Nook HD seems a lot more responsive, videos work great no stuttering, web browsing, playing a few games (not much for playing games) & all ereader apps including Audible are just a humming along.

Battery life seems pretty good too.

Thank you for renewing my tablet so I can get it off the shelf & use it again.
[Nook HD, HD+ Android Development] twiztid_:
Have you done a complete wipe of your cache, dalvik, system, and data partitions, then install a CM11/stock ROM?

Alternatively, you could try formatting cache/dalvik/system, installing a ROM, and doing a factory reset.

You could also try using a different keyboard, I can't vouch for the apps themselves, but I can for the site:

https://f-droid.org/repository/browse/?fdfilter=Keyboard&fdid=org.pocketworkstation.pckeyboard

https://f-droid.org/repository/browse/?fdfilter=Keyboard&fdid=com.menny.android.anysoftkeyboard

I could upload the Flashify apk for you, I've gone through the struggle of repeatedly closing a crashed app to muddle through something.
[Nook HD, HD+ Android Development] pastordl:
Tried 10/18 booted up fine. Tried various items great till I tried to sync with Goodsync over wifi it would not connect with the pc end of the sync. Reverted to 10/13 and all runs fine.
[Nook HD, HD+ Android Development] belfastraven:
Everything is running fine for me on hummingbird. I initially had some trouble with airdroid syncing with the pc, but am able to synch now. I switched to using https , but am not sure that is what fixed the problem. I initially got an error message that the browser on PC (Chrome beta) could not connect due to problems with unknown proxy settings. Looking at the cm changelogs I noted a network fix but don't know whether it had anything to do with this. For me, this is the best rom so far on 5.1.

thnx [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] sephiroth2k:
Running the 10/18 build now, works very well so far. I was running CM11 for a while, and upon flashing CM12.1 I noticed something strange: the UI, and some apps such as Xodo are much smoother on 12.1, while others (Dragonvale) much smoother on CM11. This doesn't bother me much since Dragonvale is for my wife and Xodo is for my textbooks, but does anyone know what might have caused this regression?
[Nook HD, HD+ Android Development] samteex:
I use Nook HD+. I use 10/18 everything seem to be fine. I rooted it with supersu and it went well. I use twrp to install nano-gapp, that also work fine. However, I try to use twrp to install open_gapps-arm-5.1-stock-20151018.zip, it won't installed.

In 10/15 the netflix stream run very fast, but in 10/18 it run normal. Other thing, I cannot mount usb thumb drive (Fat32). I would like to mount usb thumb drive (Fat32 and if possible also NTFS )

Can I do that?

Also, I try to use BT earphone (a cheap one) which can be paired with my phone, Nook cannot find it.

I thank you for your work, it is great:good::good::good::good:. (Please pardon my English)
[Nook HD, HD+ Android Development] w1ll1m:
Flashed the 18/10 build on my hummingbird, and after it loaded up, I lost root.

Tried rebooting back into recovery but it just reboots.

How did I lose both root and recovery from a simple flash?
[Nook HD, HD+ Android Development] sasmith-129:
Video issue with 10.18

I had a recurring audio glitch running Dead Trigger 2 with the 10.12 build on ovation (audio began stuttering after an indeterminate amount of time in the game).

I dirty flashed to 10.18 and discovered that video wasn't rendered properly running Temple Run 2 (objects are rendered in the wrong places on the screen making the game impossible to play). I tweaked some developer settings (HW overlays, GPU rendering, etc.) but the problem persisted.

To be sure, I did a full wipe/clean install of 10.18 but the video problem in Temple Run 2 was still there. I dirty flashed back to 10.12 (even though I understood this to be ill-advised) and Temple Run 2 plays fine (and, of course, the audio glitch still exists in Dead Trigger 2 but it is resolved restarting the game).

Has anyone else experienced video rendering issues with 10.18 on ovation?
[Nook HD, HD+ Android Development] belfastraven:
You need to be running SuperSU for root. if you were not running it previously, you need to flash the zip file from recovery. You should still be able to get to recovery by holding the power and nook keys simultaneously for 4 seconds or so when powering up the nook. Once you are again rooted with SuperSU (I believe the zip is here https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip) you will be able to reboot to recovery from the power menu.
[Nook HD, HD+ Android Development] js290:
Any idea why Live Display doesn't work? I've seen on other devices that Live Display needs GPS or cell signal to function properly.
[Nook HD, HD+ Android Development] s0c4:
USB host switcher does not work

Updated my Nook HD (hummingbird) from 2015-08-29 to 2015-10-18, done cache and Dalvik wipe. What an improvement in speed and smoothness! No issues with video and battery life here. This entire project gave new life to my Nook HD; thank you all, especially amaces.

But USB host switching for OTG is no longer working in hummingbird-2015-10-18. Gets error message:

"USB ID control file not found"

That worked with 2015-08-29. Is there some file missing now in 2015-10-18?