yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] jdjohn:
Seems like a solid start. Battery life has been good...better than CM11, but YMMV. Bluetooth works. I haven't noticed the landscape notification pulldown flicker/reboot bug, but I'm usually in portrait mode.

BUT, am I the only one having the Gesture Typing issue...or am I the only one that uses that feature? ;) I didn't see any previous comments upon searching the thread, but that feature isn't working for me. I've found and enabled the appropriate options in the keyboard settings, but when I try to drag and type...nothing. Single strokes work fine, but no tracing/swyping/gesture typing works.
[Nook HD, HD+ Android Development] patstar5:
I flashed it but I can't get root to work, I download super su and it fails to update the binary
[Nook HD, HD+ Android Development] come2learn:
I have dirty upgraded from CM11 to CM12, and everything seem normal but:

1. Chrome browser often shutdown without any reason (I have to uninstall and used default browser, and it works fine ?!);

2. I couldn't use Titanium backup
[Nook HD, HD+ Android Development] twiztid_:
I dropped Chrome completely. The stock browser is MUCH more stable and faster.

If you need syncing, grab the 4.4.x PA GApps and extract the GApps/bksync/app/ChromeBookmarksSyncAdapter.apk and put it in your /system/app folder then reboot. After that go Settings -> Accounts -> your Google account, and tick the Bookmarks box. You'll get an error if your sync requires a passphrase, but you can just disable encrypt your data from your account options or desktop.
[Nook HD, HD+ Android Development] leswgnr:
Try this. It worked for me.
[Nook HD, HD+ Android Development] patstar5:
OK, I'll try that. Also when I power off, it tries to turn off and then restarts. I had to boot into recovery and power down from there
[Nook HD, HD+ Android Development] hendersj:
That gets my vote (for what it's worth) as well. I've been running one of your 10.2 releases off the sdcard in my HD+ for some time now, and came back today to see what was new. I was thinking of the CM11 sdcard install, but if there were a CM12 release to test with, I'd be inclined to try that instead.
[Nook HD, HD+ Android Development] atlind01:
thanks, I had the same issue and the solution works for me as well.
[Nook HD, HD+ Android Development] leswgnr:
Issue log

Please up vote the issue in the bug report log and leave a comment for Hashcode and everyone else. Last bug in the list, page 3.

Glad it worked.
[Nook HD, HD+ Android Development] Tonto87:
Okay. I tried fstrim but I get permission denied. I've also tried the app LagFix Free which used to work, but does not in the latest 17/2 build.
[Nook HD, HD+ Android Development] Dread This Day:
For fstrim, did you first type

su

then hit enter, to get root, then enter your commands?
[Nook HD, HD+ Android Development] Tonto87:
Oops, no I didn't, but it does work after that. Thanks!

But the LagFix Free app still doesn't work. It says: "error: only position independent executables (PIE) are supported."

That's after it asks, and I permit root access.
[Nook HD, HD+ Android Development] amaces:
That's because of LP SELinux changes; binaries need to be recompiled/linked with PIE flags, discarding support for older Android versions (at least API level 16 needed, I think). AdAway used to have similar issues with its webserver/tcpdump executables, but some good soul recompiled it for LP. Maybe the LagFix dev will implement these changes, but honestly, doesn't really matter when command line is more efficient (in this case).
[Nook HD, HD+ Android Development] Zippy Dufus:
Ovation proprietary.txt ?

Hello,

Question, is the proprietary text file in the Cyanogen repository correct?

I built a ROM and the WIFI didn't work. I unpacked the latest cm-12-20150217-UNOFFICIAL-ovation.zip and noticed some files in a different location. See the diff (patch) and file listing below. So next I used an ADB shell to move the files to their correct location which made the WIFI work after a reboot.

--- proprietary-files.txt	2015-03-08 21:24:48.390924764 -0400

--- proprietary-files.txt	2015-03-08 21:24:48.390924764 -0400

+++ proprietary-files.txt.fixed	2015-03-08 22:09:02.744823620 -0400

@@ -25,13 +25,14 @@

# Firmware

vendor/firmware/smc_pa.ift

vendor/firmware/ducati-m3.bin

-vendor/firmware/TIInit_7.6.15.bts

-vendor/firmware/ini_files/RFMD_D_E5.ini

-vendor/firmware/ini_files/TQS_S_2.6.ini

-vendor/firmware/ini_files/RFMD_S_3.5.ini

-vendor/firmware/ini_files/TQS_D_1.0.ini

-vendor/firmware/ini_files/TQS_D_1.7.ini

-vendor/firmware/ini_files/TQS_S_2.5.ini

+etc/firmware/TIInit_7.6.15.bts

+etc/firmware/ti-connectivity/ini_files/RFMD_D_E5.ini

+etc/firmware/ti-connectivity/ini_files/TQS_S_2.6.ini

+etc/firmware/ti-connectivity/ini_files/RFMD_S_3.5.ini

+etc/firmware/ti-connectivity/ini_files/TQS_D_1.0.ini

+etc/firmware/ti-connectivity/ini_files/TQS_D_1.7.ini

+etc/firmware/ti-connectivity/ini_files/TQS_S_2.5.ini

# Widevine DRM

Mounted ROM's filesystem:

$ pwd

/run/media/android/57f8f4bc-abf4-655f-bf67-946fc0f9f25b/etc/firmware/ti-connectivity/ini_files

$ ls -l

total 84

-rw-r--r--. 1 root root 13290 Feb 17 02:29 RFMD_D_E5.ini

-rw-r--r--. 1 root root 10101 Feb 17 02:29 RFMD_S_3.5.ini

-rw-r--r--. 1 root root 13289 Feb 17 02:29 TQS_D_1.0.ini

-rw-r--r--. 1 root root 13289 Feb 17 02:29 TQS_D_1.7.ini

-rw-r--r--. 1 root root 10101 Feb 17 02:29 TQS_S_2.5.ini

-rw-r--r--. 1 root root 10101 Feb 17 02:29 TQS_S_2.6.ini

$ pwd

/run/media/android/57f8f4bc-abf4-655f-bf67-946fc0f9f25b/etc/firmware

$ ls -l

total 20

drwxr-xr-x. 3 root 2000 4096 Feb 17 02:29 ti-connectivity

-rw-r--r--. 1 root root 15807 Feb 17 02:29 TIInit_7.6.15.bts

== // ==

On a related note, has anybody tried to build with the Jan 15 Barns&Noble update firmware? I tried but the ROM did not boot. Considering the issues above, I'll have to go back and review that I extracted and positioned the firmware files correctly.

Lastly, what I am trying to do is to see if I can find a reason why Hangouts Dialer doesn't work. Alas, either a recent upstream Cyanogenmod update or a Hangouts Dialer update has now totally broken it.
[Nook HD, HD+ Android Development] amaces:
Just to add to [MENTION=4190710]drmarble[/MENTION]'s good advice, here's my .repo/local_manifests/ovation.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_bn_ovation" path="device/bn/ovation" remote="github" />
<project name="CyanogenMod/android_device_bn_common" path="device/bn/common" remote="github" />
<project name="CyanogenMod/android_kernel_bn_omap" path="kernel/bn/omap" remote="github" />
<project name="TheMuppets/proprietary_vendor_bn" path="vendor/bn" remote="github" />
</manifest>

A repo sync will basically take care of everything for you, and allow you to skip the archaic "Extract proprietary blobs" step in the build guides.
[Nook HD, HD+ Android Development] N0he:
What is the cleanest way to install? Just wipe data/cache/dalvik, get the right recovery and flash this + gapps?
[Nook HD, HD+ Android Development] Dread This Day:
Yes sir.
[Nook HD, HD+ Android Development] N0he:
Seems like I have done it right then.

What browser work well for you guys on the HD+? Chrome, Firefox, Next Browser all crash for me. I also get flickering as soon as the keyboard pops up on Chrome. The stock browser has some security issues right?

Also, when my HD+ is turned off while charging, it turns itself on immidiately.
[Nook HD, HD+ Android Development] Dread This Day:
Disable "HW Overlays" in developer mode to fix flickering.

I'm on the HD and it doesn't stay off while charging either, not really an issue, though.
[Nook HD, HD+ Android Development] N0he:
Disabling HW makes animations less smooth though.

Since I habe the habit of turning off my devices at night, which is also the time for them to charge, it is an issue to me at least
[Nook HD, HD+ Android Development] Dread This Day:
Little tidbit for you, your devices do not have to be turned off to charge. :)
[Nook HD, HD+ Android Development] N0he:
I don't turn them off to charge, I just happen to turn them off and charge them at the same time, which is at night
[Nook HD, HD+ Android Development] Dread This Day:
No fix for it, so if it's a deal breaker, I hope you have a back up.
[Nook HD, HD+ Android Development] N0he:
Not a dealbreaker, but I wonder if it is actually fixable
[Nook HD, HD+ Android Development] Dread This Day:
I would say it is fixable, but the devs would probably worry about things like that after this is more stable.
[Nook HD, HD+ Android Development] ST Dog:
My HD turn on regardless of the ROM, even STOCK.

Plug in and it turns on.

Last post in this thread says all NOOK tablets do this.

http://xdaforums.com/showthread.php?t=2141031
[Nook HD, HD+ Android Development] TheDannemand:
Yes, it was always like like that on my HD+ as well (well, my wife's) since the first time we charged it on stock ROM.
[Nook HD, HD+ Android Development] tebra:
Hi all,

is it possible to have a TWRP with F2FS support for HD (hummingbird)?

I like to try that with this CM12 rom
[Nook HD, HD+ Android Development] aoleary:
I have seen this before on other CM11 ROMs for my mobile phone, so I think it is a general CM11 issue.

Not all, but some do have this issue.
[Nook HD, HD+ Android Development] ST Dog:
I can't speak to your phones, but in this case it's a NOOK issue.

All androids based NOOKs have done this. The NOOK Color, the NOOK Tablet, the HD, and the HD+.

I don't know about the earlier NOOKs or the current devices. The GlowLight probably does turn on while the Galaxy Tab variants likely behave like other Galaxy Tab devices.
[Nook HD, HD+ Android Development] CweeperHugz:
I do believe the Galaxy Tab Nook tablets are just running stock Touchwiz with this special Nook app included. I actually have the app installed on my Nook HD right now. Anyways, that would make them just Galaxy Tab devices. Nothing special, really. Too bad they have a lower resolution than the Nook HD/HD+. That's something I saw that upset me a bit.

I'm done talking about that for now. I'm kinda waiting for an update build to the ROM that fixes the audio in calls and stuff. But besides that, the ROM was working really smoothly for me. It actually almost felt more stable than CM11, to be honest. But I decided to flash back to CM11 so that I can be in Skype and Hangouts calls. I heard that this might be because of Google Now, but I don't feel like getting rid of all my apps again to flash it again just test it out. I'll try the next build that is available. Thanks to all the devs working together on this. I hope we can see a stable build or official nightlies sometime soon. :D
[Nook HD, HD+ Android Development] ST Dog:
What I've seen it looks like the HD/HD+ launcher is being used. I haven't played with one in person yet to see what else they kept.

If it's as easily modified as the HD/HD+ I could trade the resolution (at least on the 7") for the other improved specs.

But I've not had time to explore that either.

Still hoping for an SD card install from [MENTION=3654172]verygreen[/MENTION]

I'll be home in a few weeks and I'll start serious looking into building one myself.

(I don't have my normally computer with me, and have bandwidth/data restrictions as well)
[Nook HD, HD+ Android Development] CweeperHugz:
I hope to see an SD card install soon then, so i don't have to clear everything. I've factory reset this thing at least five times messing with the CM12 ROM. I had a lot of app data on it too. Luckily, the eMMC storage "sdcard0" doesn't get cleared with a reset. I'd be really sad if I lost all my pictures and downloads.
[Nook HD, HD+ Android Development] dermk4:
Thank you Hashcode. Have enjoyed and benefited from your great work back in my Moto days :)

Cheers
[Nook HD, HD+ Android Development] ST Dog:
As always, regular backups are important. And Certainly a point backup prior to anything invasive, like flashing a ROM.

One thing I really like about SD card install is the ease of such a backup. Pop the card in a reader and make a full disk image.

No dealing with partitions or recovery. Just write the image to a card and put it in the device. Exactly what you had before.

SD card gets lost or damaged? No issues getting back to you last backup.

Device gets damaged? No problem, just put the SD card in a replacement.

Now, If I could make a full backup of the eMMC the same way it's be great. But even then, you have to worry about getting the device to a point that you can access the eMMC to restore.
[Nook HD, HD+ Android Development] amaces:
A Few Updates…

Disabling HW overlays definitely degrades the UI on ovation, so I caved, and setup a build environment, trying to recompile the 3.0 kernel with different patches. In the process, I generated a new CM12 build, assorted boot images, and an updated TWRP 2.8.5 here: https://notredame.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww.

Now, those dreaded DISPC underflows are mostly gone (not really my credit, probably mostly due to CM12 improvements), except when using the Goggle/AOSP keyboard with the Chrome browser or the search bar. The new build is quite fluid with HW overlays on, so in order to avoid the underflows and inevitable reboots, I switched to Keyboard for Excel, which is surprisingly usable on this tablet. Hacker's Keyboard, and MultiLing derivatives also work without visual glitches, but many modern ones (e.g., Fleksy, Minuum, etc) don't.

The kernel for the CM12 build in that Box folder is completely unchanged, but if you feel like testing random patches, the boot-fifo.img has a few DSS2 changes that seem to delay the reboots after repeated display0 disable/enable events (see patches/series for what's applied). Obviously, most of the heavy lifting for our devices has already been done by [MENTION=4243514]Hashcode[/MENTION], [MENTION=3654172]verygreen[/MENTION], etc, so kudos to them!
[Nook HD, HD+ Android Development] Dread This Day:
Wish we had you on the Hummingbird side, Lol. If you get bored and feel like compiling a Hummingbird build, I wouldn't be mad at you. :P. Good job on the Ovation front though. Luckily, Hummingbird doesn't suffer the underflow issue.
[Nook HD, HD+ Android Development] amaces:
I was thinking about that, especially that the task is much easier now. The main issue is that I wouldn't be able to test for hummingbird (especially, the recovery part), and there were reports about driver problems early on. Still, if my understanding about manifests and multiple device builds is correct, a hummingbird build and recovery should be ready in a few hours :) Will keep you posted.
[Nook HD, HD+ Android Development] Dread This Day:
I'd test anything for you. :) Also, if you're compiling from the same source as Hashcode and very green, we should be fine on the screen drivers as those were added. But, yeah, I'll test anything. :D thanks for the effort!
[Nook HD, HD+ Android Development] amaces:
Well, it took longer than expected, but hummingbird is fully baked and uploaded now (same folder). After getting a chance to test it out, do you want to let people know if it's safe to install on their devices? The corresponding recovery image should support F2FS, same as for ovation.
[Nook HD, HD+ Android Development] Dread This Day:
She boots nice and proper. I dirty flashed over Hashcodes last build, and no issues so far. I will test HEAVILY tomorrow. I did not mess with TWRP, hopefully tomorrow. Thank you very much keeping me and the others up to date, I really appreciate it. And again everyone, THIS BUILD IS SAFE TO FLASH!
[Nook HD, HD+ Android Development] king200:
I want to make sure I'm headed in the right direction. Things are a bit different with the HD/HD+ Emmc install. The recovery "omnirom-twrp-2.8.5-ovation.img" is for an SDcard version or can it be installed in with adb?

Is, "cm-12-20150312-UNOFFICIAL-ovation.zip" ok to flash into a f2fs data partition? fsfs/Cache?
[Nook HD, HD+ Android Development] amaces:
All the files in that folder are for EMMC installs. If you have a working installation, you can flash recovery (or boot) images with Flashify. Now, TWRP 2.8.4 introduced direct flashing of these images in recovery, but that's probably a Catch-22 situation :) I'm sure adb can also rewrite your current recovery once you have full control of the system, although I don't recall taking that route.

Both ROM and recovery are compiled with the same kernel sources, which support F2FS, but [MENTION=4243514]Hashcode[/MENTION]'s fstab will only mount /data as F2FS (his reasoning here). That being said, formatting (only) /data as F2FS is sufficient, and definitely recommended.
[Nook HD, HD+ Android Development] belfastraven:
Thanks especially for the TWRP recovery; I seem to be very "button pushing" challenged. I flashed both recovery and cm-12 rom with flashify. Things seem to be speedier than with 2/17 Rom. I know that several memory issues were fixed in the past month--and some other functions were enabled (e.g. battery saver and live display) .

Question: Does anyone have a build environment running under windows 10 tech preview? I haven't been able to get any kind of virtual machine going...
[Nook HD, HD+ Android Development] Dread This Day:
Absolutely zero glitches so far on Hummingbird build. TWRP seems to be working 100% also, made a full backup. Seems a bit snappier than hash codes last build. Will be pushing it today to see how it will hold up. Thank you again [MENTION=4473900]amaces[/MENTION] !
[Nook HD, HD+ Android Development] Goggles2114:
Echoping zero problems on hummingbird. Dislike having to sign up for a Mega account since I don't trust them but eh.

Thoughts:

Wish closed worked. Wish there was a dark theme. Why the blazes did the keyboard have to change layouts? Tired of aim and mulkluk constantly closing out (they did this on cyanogenmod's 10 and 11vtoo so nothing special there.)

Where's this 'play YouTube in background' option I've heard about?

Feels snappy but could be placibo effect in place.
[Nook HD, HD+ Android Development] Zippy Dufus:
Applying the patches?

A couple questions about your series file:

Are all of the patches required for best results or only those which are not commented out?

Is that the correct order shown below of applying the patches?

DSIsync.patch

#FIFOsize.patch

#FIFOsize+calc.patch

FIFOoptimization.patch

FIFOthreshold+burst.patch

And thanks so much for your efforts!
[Nook HD, HD+ Android Development] amaces:
The uncommented patches, in that order, were used for ovation-boot-fifo.img. Basically, patches is a copy of the quilt folder I created in kernel/bn/omap. Based on what I found online, I tried different strategies to avoid triggering lines 4098-4168 in drivers/video/omap2/dss/dispc.c, thus the assorted pieces of code. The first one (DSIsync.patch) is pretty benign, but a good idea nonetheless. Next one removes video/omap2/dss/fifothreshold.c and corresponding plumbing (those come from tuna apparently, and were reverted several times in AOSP), and finally adding in a tweaked version of https://gitorious.org/linux-omap-dss2/linux/commit/1cc6c7c. As a side note, looks like Tomi Valkeinen was the TI guy working on the video subsystem, at least through kernels 3.0-7.

Generally, these are improvements that happened just after 3.0, but our kernel has bits and pieces from from all sorts of sources, so it's hard to apply TI commits. Maybe the cobbled state of 3.0 is the result of all the tuna-inspired patches; either way, it's painful to make any sort of improvements to the video drivers, and I completely understand why [MENTION=4243514]Hashcode[/MENTION] has been working on a 3.4 kernel.
[Nook HD, HD+ Android Development] Dread This Day:
You're referring to Hash codes build, I'm referring to [MENTION=4473900]amaces[/MENTION] build a few posts back. :)

[MENTION=4473900]amaces[/MENTION], any kernel testing you want done for Hummingbird? ;)
[Nook HD, HD+ Android Development] amaces:
I think this is it for a while; either that, or I have to get more bourbon ;) It's awesome that hummingbird works without glitches, probably due to having to drive almost 50% fewer pixels. Once LP 5.1 -> CM 12.1 is out of staging (hopefully, this weekend), I'll try to update these builds. Crossing my fingers that 5.1 will make the ovation issues even less noticeable.

---------- Post added at 06:21 PM ---------- Previous post was at 06:06 PM ----------

If you mean the ovation recovery, that may not be your fault… I also noticed weirdness with touch sensitivity, and I think it was due to a couple of leftover options (RECOVERY_TOUCHSCREEN_SWAP_XY/RECOVERY_TOUCHSCREEN_FLIP_Y) in BoardConfig.mk. I took them out, recompiled, and re-uploaded omnirom-twrp-2.8.5-ovation.img.

Does Live Display work for you? I was excited for Lux/Twilight/CF.lumen-like functionality, but I think that feature require color calibration in the kernel, which we don't have or ever will.
[Nook HD, HD+ Android Development] Dread This Day:
The hummingbird recovery touch was also a little strange, I didn't think much of it until I saw this, though. Still works, the important part.
[Nook HD, HD+ Android Development] ST Dog:
I gave up on stock keyboards completely. I prefer to always have the number on a separate row, symbols where I expect them, modifier keys and arrow key. Selecting for copy/cut/paste is so much easier with shift and arrow keys.
[Nook HD, HD+ Android Development] amaces:
I was wondering about that; didn't see the same custom touchscreen flags, and assumed it's all good. There are however other (unusual) flags, so I took everything non-essential out, and re-uploaded omnirom-twrp-2.8.5-hummingbird.img. Let's see if it works any better.
[Nook HD, HD+ Android Development] CweeperHugz:
i tried dirty flashing [MENTION=4473900]amaces[/MENTION] hummingbird build over cm11, and i got a black screen of death trying to boot. luckily the twrp recovery works just fine, and it was able to back up my data, unlike other recoveries i've used. i was wondering if i needed to do a wipe/factory reset first, or if this was just some random bug.
[Nook HD, HD+ Android Development] Dread This Day:
Nooooooooo sir, the graphics are all distorted, cannot make out ANYTHING. Lol. Pressing the screen obviously makes menu changes, but it's useless. I'll just reflash the first build. Lol.

---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------

Wipe EVERYTHING and flash, report results. :)
[Nook HD, HD+ Android Development] amaces:
Oops, restored back to first version. If you feel like testing some more, I have a fresh recovery for you: bad-hummingbird.img.
[Nook HD, HD+ Android Development] Dread This Day:
I'm always up for testing, uno momento.

---------- Post added at 07:28 PM ---------- Previous post was at 07:16 PM ----------

Same results, graphics glitched out insanely.
[Nook HD, HD+ Android Development] amaces:
One last try (still bad-hummingbird.img)? Also, would you be able to attach a picture of how it looks like?
[Nook HD, HD+ Android Development] CweeperHugz:
it worked. i guess that i shoulda tried that in the first place. it only makes sense now, obviously.
[Nook HD, HD+ Android Development] belfastraven:
[

Does Live Display work for you? I was excited for Lux/Twilight/CF.lumen-like functionality, but I think that feature require color calibration in the kernel, which we don't have or ever will.[/QUOTE]

Nope, doesn't work here or on the Nook Tablet (on official CM12 nightlies) . I had some hope initially because I remembered some kind of White Balance apk available on the HD when I first bought it... I believe someone found that the app just edited a couple of files in a /sys/devices/platform/omapdss directory... Certainly not critical.
[Nook HD, HD+ Android Development] Dread This Day:
No problem.

http://imgur.com/QY86SnR

http://imgur.com/IH8vRiP
[Nook HD, HD+ Android Development] amaces:
Whoa, that's insane. There was an option supposedly preventing "slanted" graphics, but that's a world of difference... Anyway, re-enabled it.
[Nook HD, HD+ Android Development] Dread This Day:
It is pretty nuts. Lol. Have you seen anything on github about getting our move to external SD working by any chance? And do you have another recovery with the enabled graphics option for me to test?