yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Blenky:
No not working.
[Nook HD, HD+ Android Development] vertycall:
Just created account to say thanks for your amazing work, Hascode !

My Nook HD+ is running nice and smooth. Much better than all previous CM 11 builds I've tried.

Had to use TWRP 8.2.3 for ovation than did a clean install and for these 24h of use it seems great. No hard reboots, no screen flashes, plays HD content smoothly without lags or shutters. Wifi - stable.

The only problem I found was with superSU not working , but after installing it from recovery all seems fine.
[Nook HD, HD+ Android Development] Hashcode:
Added Google Maps location issue to Bug Reporter.
[Nook HD, HD+ Android Development] Dread This Day:
I see some more Hummingbird success. Now I'm wondering if my internal is corrupted or something of the sort. But, I'm not sure how that would be as I went back to stock BN, then back to CM to flash this. The recovery I'm using is the newest/only available for Hummingbird so I'm not sure how that could be the issue. Beyond missing out on the material goodness, it is the curiosity that is killing me. If there is anything I can do [MENTION=4243514]Hashcode[/MENTION] to help with figuring out why some of us Hummingbird people can't boot CM12 I'd be more than glad to help. Anything.
[Nook HD, HD+ Android Development] neutronjeff:
Just curious, where did you get TWRP 2.8.3 for Ovation?
[Nook HD, HD+ Android Development] tebra:
Still have screen flickering on hummingbird after a few reboot but that bug disappears after device going to sleep.
[Nook HD, HD+ Android Development] TeutonJon78:
This was a problem in CM11 as well, so it's not necessarily new.
[Nook HD, HD+ Android Development] tebra:
The location bug was fixed around CM11 M8
[Nook HD, HD+ Android Development] allrockedout:
Cant Download

The download is super slow and fails, anyway you can post another download link. thanks
[Nook HD, HD+ Android Development] Darrian:
I ended up using my computer, Firefox, and a download manager (downthemall) to nab it
[Nook HD, HD+ Android Development] vertycall:
I found one here on Dev-Host - d-h.st/GE0s . I must warn you - some people reported problems with while wiping / formatting , so use it on your own risk.

For me it seems to work just fine, but probably it is a good idea to wait for another official link here in OP
[Nook HD, HD+ Android Development] :
It would appear that its slow until its fast. The speed varies. If its too slow try at a different time.
[Nook HD, HD+ Android Development] SCWells72:
Installed this on my HD+ and it seems to work very well. Any thoughts on optimal setup of governors for this ROM for a good balance of performance and battery life?
[Nook HD, HD+ Android Development] malikfaraj96:
Is there no one else experiencing the hummingbird crash at boot?
[Nook HD, HD+ Android Development] Dread This Day:
Yes, seems only about 50% of the people whom flash Hummingbird get to enjoy it. The other half, it crashes. We're still waiting patiently on a reason/fix. I tried everything I could find/think of, nothing worked. So I/we wait.
[Nook HD, HD+ Android Development] keshabbhattarai126:
I am experiencing too. I am done with this. Now I wont flash these early builds until new TWRP recovery is released.
[Nook HD, HD+ Android Development] tebra:
Are you certain that it crash at first boot? Because my hummingbird takes 10 min for the first boot and the Cm boot logo flickering like hell during that time.
[Nook HD, HD+ Android Development] Dread This Day:
I can't speak for anyone else, but I left mine for a very long time, around 15 minutes. And yes, it was crashing.

I tried again. flashed, it tried to boot for 15 minutes, then went to recovery.

All without me touching it. Hopefully soon it will be fixed. It booting itself into recovery hopefully gives a clue.
[Nook HD, HD+ Android Development] malikfaraj96:
What recovery are you using?
[Nook HD, HD+ Android Development] tebra:
Cwm 6.0.4.6 on internal memory
[Nook HD, HD+ Android Development] dbrickg:
Assuming this is similar to other lollipop releases, they include their own su app, which, by default is turned off. Go to Settings / Developer options / Root access, and set it to something other than "disabled". Or, you can do what you did, install superSU from recovery :)

Edit: this option does NOT work on the Nook HD+... or, at least, I couldn't make it work
[Nook HD, HD+ Android Development] Zippy Dufus:
Build issue

Hello,

I'm trying to build this ROM again and now I am having issues with a seemingly missing omap4_ion.h header file.

My first attempt to build this was successful but now it is not building.

Are the repos up-to-date? Configuration changing? (This file appears to be present.)

CC arch/arm/mach-omap2/omap-iommu.o
CC arch/arm/mach-omap2/i2c.o
CC arch/arm/mach-omap2/board-acclaim.o
[COLOR="Red"][32mtarget thumb C++:[0m v8_tools_gyp_v8_base_gyp <= external/chromium_org/v8/src/code-stubs.cc
/home/android/kernel/bn/omap/arch/arm/mach-omap2/board-acclaim.c:63:23: fatal error: omap4_ion.h: No such file or directory
#include "omap4_ion.h"
^
compilation terminated.
/home/android/kernel/bn/omap/scripts/Makefile.build:305: recipe for target 'arch/arm/mach-omap2/board-acclaim.o' failed
[/COLOR]make[3]: *** [arch/arm/mach-omap2/board-acclaim.o] Error 1
/home/android/kernel/bn/omap/Makefile:945: recipe for target 'arch/arm/mach-omap2' failed
make[2]: *** [arch/arm/mach-omap2] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/android/kernel/bn/omap'
build/core/tasks/kernel.mk:209: recipe for target 'TARGET_KERNEL_BINARIES' failed
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....

[android@localhost ~]$ find ./ -name omap4_ion.h -exec ls -l {} \;
-rw-rw-r--. 1 android android 3034 Jan 15 14:57 [COLOR="Green"]./kernel/bn/omap/arch/arm/mach-omap2/include/mach/omap4_ion.h[/COLOR]
[Nook HD, HD+ Android Development] drmarble:
This problem was introduced by this commit: http://review.cyanogenmod.org/#/c/82838/

I have made a comment about it on gerrit. Meanwhile you can revert it.

Try something like:

cd build
git reset --hard 16fc650a31c35490c26aeb702886788f579214b6
croot

This will change the build directory to its state before that commit was merged.

We probably need to modify our BoardConfig.mk file. Or have someone fix that commit. It looks like it may have been merged inadvertently.
[Nook HD, HD+ Android Development] detonation:
Flashed this last night on my HD+ and everything seems to be working pretty well.

Here's the steps I took coming from 10.2.1

1. Flashed TWRP 2.7.1.0. Not sure if this was necessary but I was on an older version and I needing to update to flash CM11 when I tried it a while back.

2. Rebooted back into recovery, wiped Data/Cache/Dalvik

3. Flashed ROM

4. Flashed Gapps

5. Rebooted

6. Waited (and waited and waited). The OP says first boot takes about 7-8 mins but mine was closer to 15 mins before I got the setup screen

Note that this was all done from the internal storage, I did not have an SD card in the nook even.
[Nook HD, HD+ Android Development] hallanthony:
Flashed my HD+ tonight and all seemed to work like a treat so thanks to hashcode!

Updated from CM11 with CWM 6.0.4.6

Wiped data

Installed ROMs

Wiped cache/dalvik

Rebooted and waited about 10 mins
[Nook HD, HD+ Android Development] drmarble:
Zippy Dufus and other home builders:

There is another solution to building you can now just cherrypick a commit that reverts just that change. This should work for a while until changes to build make the reversion no longer work.

The commit is: http://review.cyanogenmod.org/#/c/85601/

An easy way to cherrypick in cm is the repopick command from your croot (base) directory type

repopick 85601

It makes the change right then and there.

This has to be done every time you repo sync.

I am still looking at how to fix our build. I don't know why we are picking up board-acclaim.c . We should be using board-ovation.c .

I have been looking at changes others have made to fix their compiling with this change. None of the fixes work for us.
[Nook HD, HD+ Android Development] dbrickg:
Just installed on my Nook HD+. No big problems. Booted after a couple of minutes. Or, at least, booted to the "Updating Apps" screen. Which went on for half an hour or so. The usual thing for ART (vs Dalvik). Haven't played with it much yet, but looks generally good. The only thing I've noticed so far is that the Google calendar, in Agenda view, acts like ti's starting, and then just crashes, returning me to the home screen.
[Nook HD, HD+ Android Development] vertycall:
Short update on my 3d day of using ovation with cm12 - got a few random reboots and some screen flashing occasionally. The reboots occurred during heavy wifi transfer and watching HD video. Battery seems to drain more quickly, but hope future kernel release will fix that. Overall - I am more than satisfied with lollipop on this hardware. If the op needs some sort of help with logs or something else - let us know. Thanks again for your precious work, Hashcode!

[MENTION=4490141]dbrickg[/MENTION]

Regarding SU - figured out later that this option is part of dev settings as you wrote, but decided to leave it off for now with SU enabled from recovery install. Maybe when flashing upcoming versions will try to use the stock ON/OFF option.
[Nook HD, HD+ Android Development] KevHD+:
Location on maps version 9.1.2 works.
[Nook HD, HD+ Android Development] tebra:
I have Google maps 9.3.0 on my nook HD and location don't works
[Nook HD, HD+ Android Development] evaporic:
Is Netflix working correctly now?
[Nook HD, HD+ Android Development] dbrickg:
Just tried, and it's still loading after a minute or two, so I guess it's not working :(

---------- Post added at 12:41 PM ---------- Previous post was at 12:18 PM ----------

Well, looks like that option does not work on the nook hd+, sigh....
[Nook HD, HD+ Android Development] Zippy Dufus:
Build still borked

Hello again,

I'm still having difficulties building. Below are the relevant snippets from my build log:

My build script copied the original makefile just prior to calling brunch.

There was an issue with making some dtbs library but the build still trundled on.

The build ultimately failed near the end.

Other notes:

I'm interested in trying the repopick command if it doesn't update my local git repo. However, my Fedora 21 build VM doesn't seem to have this command. Investigating.

As per #1, any hacking that I do is with local patches prior to calling brunch. However, this build was a straight build without any code modifications except for the copying of the makefile.

I haven't ruled out that I am master of my own misery.

...
...
[COLOR="Green"]+ cp -f /home/android/bin/NookHD+.ovation/CM12.Linaro-patches/kernel.mk.before /home/android/build/core/tasks/kernel.mk[/COLOR]
+ set +x
...
...
AS arch/arm/boot/compressed/lib1funcs.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
make[1]: Leaving directory '/home/android/kernel/bn/omap'
make -C kernel/bn/omap O=/home/android/out/target/product/ovation/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/android/prebuilts/misc/linux-x86/ccache/ccache /home/android/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-" dtbs
make[1]: Entering directory '/home/android/kernel/bn/omap'
[COLOR="Red"]make[2]: *** No rule to make target 'dtbs'. Stop.
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/android/kernel/bn/omap'
build/core/tasks/kernel.mk:168: recipe for target 'TARGET_KERNEL_BINARIES' failed[/COLOR]
make: [TARGET_KERNEL_BINARIES] Error 2 (ignored)
make -C kernel/bn/omap O=/home/android/out/target/product/ovation/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/android/prebuilts/misc/linux-x86/ccache/ccache /home/android/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-" modules
...
...
[32mtarget Executable:[0m showmap (/home/android/out/target/product/ovation/obj/EXECUTABLES/showmap_intermediates/LINKED/showmap)
[36mInstall: /home/android/out/target/product/ovation/system/xbin/taskstats[0m
[32mtarget Executable:[0m vim (/home/android/out/target/product/ovation/obj/EXECUTABLES/vim_intermediates/LINKED/vim)
[33mCopy:[0m /home/android/out/target/product/ovation/system/lib/libion.so
[COLOR="Red"]acp: cannot create '/home/android/out/target/product/ovation/system/lib/libion.so': No such file or directory
build/core/Makefile:46: recipe for target '/home/android/out/target/product/ovation/system/lib/libion.so' failed
make: *** [/home/android/out/target/product/ovation/system/lib/libion.so] Error 1
make: *** Waiting for unfinished jobs....
[/COLOR]
real	217m13.058s
user	322m2.133s
sys	63m44.759s
[Nook HD, HD+ Android Development] :
It looks like the dtbs line was recently changed a bit. You may want to do something about that :)

- -$(MAKE) $(MAKE_FLAGS) -C $(KERNEL_SRC) O=$(KERNEL_OUT) ARCH=$(TARGET_ARCH) $(ARM_CROSS_COMPILE) dtbs

+ -$(MAKE) $(MAKE_FLAGS) -C $(KERNEL_SRC) O=$(KERNEL_OUT) ARCH=$(KERNEL_ARCH) $(KERNEL_CROSS_COMPILE) dtbs

https://github.com/CyanogenMod/android_build/commit/97ce0744766db922c216a3ef4b48226f069ad66e
[Nook HD, HD+ Android Development] Dread This Day:
Ugh, still can't even get hummingbird to boot. The Netflix glitch is an easy fix, if you'd read the known bugs. Use an older version of Netflix, as posted.
[Nook HD, HD+ Android Development] drmarble:
I don't think the dtbs error is important. It tells you that it is ignoring that error. I don't think it is required for a flashable build.

The libion problem is real. The change I described earlier causes us to buld board-acclaim.c rather than board-ovation.c

I don't know why. Reverting that change fixes the build. Folks who are much better at programming than I am are working on that.

My builds complete now but the build won't boot. I get egl and surfaceflinger errors. My last working build is from the 13th.
[Nook HD, HD+ Android Development] juasjuas:
Lollipop in HD is completely amazing! Have it for a few days and I am super happy about it :D

Battery life and general performance is best I have ever tried, also comparing it with nexus 5 :) :o :D ;) :p :good: :highfive: :fingers-crossed: :laugh: :victory:
[Nook HD, HD+ Android Development] vertycall:
[MENTION=4201688]evaporic[/MENTION]: Cant say anything about Netflix for now since I can not get my VPN to work with android 5.0 correctly. It gets connected but does not change my IP address hence I am rejected by the netflix server since I am out of US.

Almost sure it is not a problem of the device/firmware but probably an issue of PIA - the vpn provider. Anyway if someone has encounter a similar problem and found a solution , pls share :)

Btw tested also bluetooth tethering - works fine. Also installed antutu to check the video and overall performance - got 18250 which is slightly better than CM11 if my memory serves me well.
[Nook HD, HD+ Android Development] extrem0:
I might be mistaken but I think I read somewhere that Netflix is starting to block using either your device timezone or location.
[Nook HD, HD+ Android Development] :
I'm not sure how its any different. You should have libion.so as its a proprietary file. You probably could just manually copy the file into the /out dir and may encounter another error during kernel.mk that's not related to libion.so when using the new code.

https://github.com/Hashcode/proprietary_vendor_bn/tree/cm-12.0/hd-common/proprietary/lib

Thus, if reverting the changes fixes the build then it looks to be possibly the same reason - as in quite a few of the changes in kernel.mk make it less static hence the ifeq else's. Which means something along the line of the train is on the wrong track.

Correct me if I'm wrong.
[Nook HD, HD+ Android Development] Dread This Day:
How many times must it be said. Check the bug reports, in the comments for Netflix bug is a link to an older .apk of Netflix that will work. Problem solved.
[Nook HD, HD+ Android Development] drmarble:
You are right, there is a libion.so file in the proprietary files. It is even on the muppets.

I have been getting an error involving libion.c which is called by board-acclaim.c which we shouldn't be using. This error is fixed by reverting that build change. Somewhere in that mass of if defs and elses it messes up our build. I can build fine for tenderloin and flo. I think I will define some of those new kernel variables that should default to useful values.
[Nook HD, HD+ Android Development] evaporic:
So none of the apps worked but this combo worked. :)
[Nook HD, HD+ Android Development] andtron:
Yup, lay the nook on the floor, toe on the home button, right middle finger on the power button, left index finger on one of the volume buttons, then press at the same time until the bootloader icon show up. You can let go the buttons now, lol.
[Nook HD, HD+ Android Development] xu2006:
Updated EMMC TWRP 2.8.3.0 builds for Ovation/Hummingbird

[Coming up with install instructions and a flashable .zip to update the emmc recovery. For now, you *should* be able to install CM12 w/ your current recovery -- MAKE A BACKUP FIRST]

where is donwload flashable.zip？

EMMC TWRP SDcard img？

I‘m ver 2.5.0！

Can you help me? Thanks!
[Nook HD, HD+ Android Development] MarkMcCoskey:
New build Notification?

Will we receive a notification when a new build is available?

Will is show up under Settings > About tablet > CyanogenMod updates?

Thanks!
[Nook HD, HD+ Android Development] leapinlar:
No. As the title of the thread says UNOFFICIAL. You must always check the link in this thread.
[Nook HD, HD+ Android Development] drmarble:
We can build again. David Hacker made a patch that fixes out builds. It hasn't been merged yet so you will have to add it. The patch can be found at: http://review.cyanogenmod.org/#/c/85896/

You can apply the patch by changing to the build directory and entering:

git fetch http://review.cyanogenmod.org/CyanogenMod/android_build refs/changes/96/85896/1 && git cherry-pick FETCH_HEAD

Or, you can use repopick (whose source is found in the very useful file build/envsetup.sh which you have to run to set up your build environment) and simply type:

repopick 85896

Once this patch is merged you will no longer need to cherry pick it. Building will just work until they break it again.

Enjoy.
[Nook HD, HD+ Android Development] drmarble:
http://review.cyanogenmod.org/#/c/85896/ has been merged so home builders are back in business.

brunch ovation should produce a working .zip file.
[Nook HD, HD+ Android Development] graysooner:
Oops. Mistake.
[Nook HD, HD+ Android Development] amaces:
Thanks, [MENTION=4190710]drmarble[/MENTION]. Do you know roughly when official nightlies will start?
[Nook HD, HD+ Android Development] drmarble:
Two weeks.

(Standard answer; it never changes, always 2 weeks. This is the official CM answer.)

Every time someone asks for a cyanogenmod release schedule another puppy dies.
[Nook HD, HD+ Android Development] ST Dog:
Not before an OFFICIAL build exists. This is still unofficial.

Sent with XDA free app
[Nook HD, HD+ Android Development] twiztid_:
Is it possible for us to get another build before official? :D

I read that theme support was added in the 20150115 sources, but the current build is from the 11th. So far, I'm loving lolipop, but not a fan of the keyboards colors.

Thanks to everyone who had a hand in this! You rock!
[Nook HD, HD+ Android Development] Zippy Dufus:
libion.so ?

Hello,

Any DIY builders know what has changed with the libion.so?

Before the upstream refactoring of the build configuration, my automated build process simply copied libion.so to $BUILDROOT/vendor/bn/hd-common/proprietary/lib by running a modified version of $BUILDROOT/device/bn/ovation/extract-files.sh. (It is modified to pull these files out of a CM11 ROM instead of using ADB.)

Now the build requires this file in $BUILDROOT/out/target/product/ovation/system/lib.

So I added a hackish couple of lines just prior to calling brunch to:

Remove some broken link in $BUILDROOT/out/target/product/ovation/system/lib/libion.so

Copy this shared library to $BUILDROOT/out/target/product/ovation/system/lib/libion.so

Problem is that my build now aborts midway through and I have to repeat above steps manually before resuming. Annoying.

Any ideas?

BTW, the other problem with the makefile is fixed.

== Edit ==

The build process (now?) appears to build an object called $BUILDROOT/out/target/product/ovation/system/lib/libion_ti.so and then creates a broken link for libion.so. The path of this link is /system/lib/libion.so. Noted that it is missing a complete path or ".././". This looks like a boo boo.

== Edit #2 ==

Resolved. Apparently libion.sh is now built in CM12 but is still enabled in /device/bn/ovation/proprietary-files.txt.

Solution - comment out line 28

# For DRM key unpacking
bin/wvdrm_test_client
bin/install_wv_keybox
[COLOR="Green"]#lib/libion.so[/COLOR]
[Nook HD, HD+ Android Development] skyhawk21:
Help!

Installed this and looks like its working so far. Issue is on nook hd+ ovation latest build I cannot connect to wifi networks with wpa2 authentication. It keeps trying but wont connect?

How can I fix this?

Went to this latest unoffical build straight from stock os 2.2.1 (android ICS 4.04)

Used CWM from sdcard to install zips from sdcard to nook internal, did data/cache/factory reset then rebooted and re-fixed root.

I can connect to open networks without authentication.

Thanks for the help, dedication and support!

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

Ignore last message! Got it working by turning wifi completely off for couple of seconds and back on and now it connects!

AWESOME! This is my first taste of lolipop!

---------- Post added at 06:00 AM ---------- Previous post was at 05:19 AM ----------

Once again I wanted to thank Hashcode.

You do not know how much better the Nook HD+ is with your cm12 lollipop build compared to ice cream sandwich 4.04.

Everything is snappier, web browsing with built in cm browser actually works on heavy loaded graphical sites and scrolls smoothly. Quadrant scored almost 4000, Calendar agenda mode worked for me, no crashes or reboots yet and Ive been benching it and loading many apps into memory. Androbench gave me better scores for sequential write and the other write mode. I do hope trim is enabled so it will stay this fast!

Antutu just pushed out 18047 and thats using the latest version. Have not tweaked or messed with anything yet and I am blown away how much better this is even though its an alpha build!

Screen does flicker when it goes to sleep mode while turning off. Other than that no issues. Youtube worked awesome and allows me to select 1080p mode for video quality.

Google movies does not work which sucks, wonder if a way around that so they still load to chromecast? have not tried chromecast functionality yet but hoping it works. Showed my wife and kids even, how better it makes the nook HD+.

HELL I think its working better with the older hardware and devices internal than the nexus 9 new hardware with lollipop!

This breathed life into my Nook HD+! I was sick of after months of installing stuff the built in storage slowed to a crawl because of no trim in ICS 4.04. web and wifi working fast at N speeds.

THANK YOU!

Forward your build and my notes to the CM team and tell them to find a nook hd+ ovation to test out with your hard work! I bet you then they will be so impressed they will make real unofficial or official nightlys!
[Nook HD, HD+ Android Development] kangi26:
I have minor bug that I'm seeing. When I flashed to the current build, I did a dalvik clear, installed the ROM and gaaps. The alarm would go off but it would only click. I tested a few times and could never get the alarm to produce any audio. I set multiple different tones, volumes etc. No good. So I did a full wipe and a clean install. The alarm did start to work, but this morning I was feeling a bit lazy and hit snooze........... Oh crap...... No audio again. Makes for an interesting start to the day

EDIT: And disregard, cause it works now :)