yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Jon Lee:
I wouldn't recommend the use of that script on this newer rom.

I experimented briefly with an odexed build but it seemed to have a detrimental effect. The only way I could rationalize it was that it took longer to read the .odex from an ext4 partition, than it did to read the data from a F2FS partition (non odex). That wouldn't apply to non hybrid filesystem roms...
[Nook HD, HD+ Android Development] xflier:
Thanks for your reply! I ended up with odexed system app and data, which worked fine! Feel smoother.
[Nook HD, HD+ Android Development] twiztid_:
Two questions: Does anyone know a way to use a newer STOCK browser than 4.3's stock? Preferably Lollipops? I know the reason you can't just drop in 4.4.x/5.0 browser, the WebKit/WebView switch, but I was wondering if there was something newer (and more secure). I want/need bookmark sync, but chrome sucks.

And second, an EXTREMELY pie-in-the-sky idea, that I have almost no hope of being possible, but I figured it can't hurt to ask:

Is there any possibility of Frankenstein-ing the CM11 theme engine into this?

I see quite a few CM11 skins that are CM10/11 compatible, so I hope they're not too different. However, one of the skins I use on my CM11 phone won't even install.
[Nook HD, HD+ Android Development] Jon Lee:
The short answer is no, it can't be done (to both questions). Yes, I have tried (from a source standpoint).

That said, several aftermarket browsers do offer bookmarks sync... chrome, firefox, safari...etc.

As far as themes go, I use dustinb's themes, and they work quite well.

https://play.google.com/store/apps/developer?id=dustinb&hl=en
[Nook HD, HD+ Android Development] xflier:
I just find one issue that location service is not working. Google Map and other apps can't find my location. However, google+ could. Thanks for any advice!
[Nook HD, HD+ Android Development] twiztid_:
Thanks.

I figured it wasn't possible, but I found a "workaround" if anyone is interested.

Using HKThemeManager (Xposed Module), I think it let's you use newer CM themes, but definitely let's you use HKThemes. I'm using the Materia10 HK theme.

I'll look into using CM11 themes, and update this post. I think its a matter of the file location.

I can "manually install" skins, like anything else, but it doesn't really help or let me use the CM11 themes, so its no different than letting the .apk install itself.

1). Rename the .apk file to its package name, move it to the /data/app folder. Permissions: rw- r-- r--

2). Create a folder /data/data/PACKAGE.NAME, optionally a /lib subfolder.

3). Reboot.
[Nook HD, HD+ Android Development] mikey williams:
Just wanted to say thanks to Jon Lee for an excellent ROM. Have installed it on 2 Nook HD+s and they are both working beautifully. Best ever.

BTW, I reinstalled my apps with Titanium Backup and have had no problems.
[Nook HD, HD+ Android Development] PMikeP:
Yep. There was an update to TB that fixed my problem where it wouldn't restore data. Works fine now.
[Nook HD, HD+ Android Development] PMikeP:
Hi Jon:

I was wondering if you would keep tweaking.

I don't want to dissuade you, but this one didn't work for me. I get a message that the AOSP keyboard stopped. Even before that, I can't activate the system menu (the three dots on the bottom right of Home page). The "back" button doesn't work on mine. Which is strange if all you changed was wi-fi stuff.

Update: But

So maybe that's causing my keyboard problem. (Should I clear data on keyboard? Update: Cleared cache & data on keyboard. NC.)

Update 2: I did a Factory Reset and the keyboard still crashes.

I noticed that, on start up, the screen flickers as it seems to start in Expanded Mode and then reset to non-expanded. (Which I don't recall seeing the previous builds do.)

Sorry to be the bearer of bad news. I went back to the last one.

But looking forward to the next! :)

P.S. I did a dirty flash, which has worked fine with your previous ROMs. I will go back and try it later with a cache wipe. Update: NC.

(Out of curiosity, how long do these ROMs take to compile? I saw someone in the forum taking about it taking all night.)
[Nook HD, HD+ Android Development] Jon Lee:
That's a shame. I dirty flashed it and it works a treat for me. (So well, in fact, that it feels like the final version, lol). Did you include the md5? It's possible it could have been corrupted uploading/downloading (I noticed there were several hundred downloads of the last ROM, and maybe ten downloads of the md5 :D). Any confirmation either way?

This ROM is fairly quick to compile.. about four hours. It really depends on the ROM (with limited ram).

I'm not wiping it just yet, just that I don't think there's anything left to do (except play with FM and I doubt I'll get anywhere with that... Although, the Wi-Fi changes were along that line...)
[Nook HD, HD+ Android Development] mikey williams:
Just dirty flashed over the previous version (with md5 file) and in the half hour I've been using it there have been no problems st all. Cant say i notice any changes - it is as snappy as ever. But will investigate further.

Thanks for another super ROM.
[Nook HD, HD+ Android Development] Jon Lee:
OK, cool. Thanks. The keyboard change was for the stuck key highlight issue (which I haven't seen any more of/yet).
[Nook HD, HD+ Android Development] PMikeP:
===========

Update: Success! I wiped /system (but did NOT do a Factory Reset). That worked.

I notced that Google Play, Framework & Services are no longer installed. (When I first installed Jon's CM 10.2.1 Yellow kernel ROM, I did a complete wipe of everything, including media. The three were there initially when I installed Jon's ROM. (I did NOT install GAPPs.) I disabled them from the start and was happy to be Google free. Now I'm really Google free.

End of update.

==========

Well, I downloaded the ROM again and this time, I downloaded the MD5 sig too. I told TWRP to check it and it checked fine.

I did a Factory Reset and the first thing I get on the Welcome screen is "Unfortunately, the AOSP keyboard has stopped." (I noticed that Developer Options was enabled after my Reset. Did you enable it in the ROM? Or is something stuck on my end? Perhaps I need to wipe /system?)

Rats. I wish this would work for me because I've seen the stuck key highlight you're talking about and are fixing.

As I mentioned before, my screen jumps in and out of Expanded mode with this build. Does that give you any insight as to where the problem lays?

Perhaps this is one of those hardware specifics things? It''ll be interesting to see if someone else will report if they're having the same issue.

(Writing these posts is like a sounding board. Now that I've said it, I'll go try it with a /system wipe and report back later.)
[Nook HD, HD+ Android Development] FirePsych:
Dirty flashed 3-28 without a problem, but I haven't used. everything yet. No Fc's or weird behavior so far.

As with all builds, it bogs down the more I use it. Can't use too many apps, even if I back out if them with the back arrow. A reboot fixes that. Not a big deal, just an observation.

Any recommended settings through Settings>Performance?

Also, what's the best way to download through Mediafire?

I'm using Dolphin set to desktop and it usually takes 3 tries before I can input the Captcha phrase without it opening up an ad/window.
[Nook HD, HD+ Android Development] PMikeP:
As to Performance: I use Jon's stock settings for the CPU and IO. I vacillate on between 10% and default 18% for zRAM. I installed Kernel Tweaker and I've lowered the LMK settings.

As to downloading from Mediafire: I use Chrome. One click and it downloads. (Albeit it doesn't ask me where, like Dolphin allows.)
[Nook HD, HD+ Android Development] FirePsych:
[MENTION=5348266]PMikeP[/MENTION], thanks.

Update, keyboard error in landscape. Works ok in portrait.

For settings? Abyssplug, SIO?

I don't remember stock settings since I've changed them.

I had zRam at 26%. Might've been part of the problem with lagging.

I'm also using Greenify which may do more harm than good.
[Nook HD, HD+ Android Development] PMikeP:
On the keyboard errors - I almost exclusively use landscape. No problems since wiping /system and reflashing.

Yes, Abyssplug. IO is FIOPS. Since it's supposed to be optimized for Flash, I figured that was best.

I use Greenify too. I find that I get faster AnTuTu scores w/ auto hibernate disabled. But I leave it enabled for day to day use so that I can get impressive standby life like yours.
[Nook HD, HD+ Android Development] trenty12:
cant install gapps?

ok, so i temporarily went back to factory stock and have now just gone to do a fresh flash of this using version 20150322 and it has gone on ok, but I have now tried 3 different zips of gapps and although they seem to install correctly, i am still not able to see play store or anything?
[Nook HD, HD+ Android Development] twiztid_:
Have you checked your apps page? It should be listed as Play Store, and you should have Google Settings at minimum.

If its not in your apps list, you can try my gapps package: http://xdaforums.com/showthread.php?p=59271962&highlight=gapps#post59271962 Its the official CM10 gapps repacked into a minimal package that contains just the files for the play store and its framework.

What are you using to flash the gapps package?
[Nook HD, HD+ Android Development] Jon Lee:
I admit I normally keep auto-rotate off, so I actually had to check...

No problems here, so you might want to wipe cache or keyboard app data.
[Nook HD, HD+ Android Development] FirePsych:
Thanks Jon,

I always wipe dalvik and cache after flashing or restoring.

I'll try wiping keyboard data.
[Nook HD, HD+ Android Development] Jon Lee:
OMG! You would never guess what I have just accomplished!!

I haven't had time to play with it yet, but wow.
[Nook HD, HD+ Android Development] PMikeP:
Kind of a cool looking keyboard. I guess that's themeing?
[Nook HD, HD+ Android Development] Jon Lee:
Yeah, I thought about it and realized I should have used a yellow one as a matter of principal, but actually orange ("cobalt inferno"), is my favorite.
[Nook HD, HD+ Android Development] FirePsych:
Don't get me wrong 3-22 works great, and my Nook HD+ has never run better. I'm just chasing unicorns here, but...

restored my working nan of 3-22, flashed 3-28, wiped Dalvik-Cache and Cache through Wipe rather than the shortcut on the Install screen (TWRP), rebooted.

had the AOSP keyboard crash and lost functionality of my back button.

Wiped keyboard data.

Didn't help.

Went back to TWRP and wiped System. Went to reboot and go the No System message, so I reflashed 3-28, wiped Davlik-Cache and Cache and rebooted.

No Keyboard error!

But, a bunch of Google Play Services errors.

Went back to TWRP and flashed PA GAPPS Modular Mini 4.3.

Wiped Dalvik-Cache and Cache

Reboot.

Back where I started. AOSP keyboard error and no functioning back button.

I guess next steps are

TiBU Pro all my apps (or use Rom Toolbox Pro)

Do a full wipe, start from scratch and reflash 3-28

or

Download 3-28 and the MD5 with Chrome,make sure it's a good download, then flash, wipe System, Dalvik-Cache, Cache, boot, back to TWRP, flash GAPPS, wipe Dalvik-Cache/Cache, profit.

Meanwhile, setting IO to FIOPS and setting zRam back to 10% seems to have helped the lagging, but it'll take a few days without reboots to see if that's really the answer.

Again, no complaints here at all. Just welcoming the distraction from real work.
[Nook HD, HD+ Android Development] twiztid_:
Kind of odd seeing the comments about the keyboard giving errors... The first thing I did after installing this ROM, and gapps, was to replace the keyboard with the one from Lollipop and I've had no issues what so ever.

Silly question, but was /system/lib/libjni_latinime.so (and libjni_latinimegoogle.so maybe a mismatch version is causing the error?) updated as well as the apk?
[Nook HD, HD+ Android Development] PMikeP:
Similar problem here.

I went flying today without first checking the 328 ROM.

Turns out that two applications don't work with the 328 ROM. Nor can I re-install them. (I get the very helpful message "App not installed" when I try.)

They are blitzortung and a Bluetooth GPS app.

I was forced to restore back to 322 ROM while waiting for takeoff clearance. (Fortunately, there was a 20 minute delay for takeoff!)

Since getting back home, I've uninstalled the apps from 322 ROM and then wiped /system and flashed 328. Strangely, the "desktop" icons for the apps reappear upon flashing, and I cannot install the apps. Even Titanium gives me the message "App not installed."

I'm guessing it has something to do with lack of Google Play, Services, & Framework on this ROM? (Even tho both of my troublesome apps are free apps.) I really, really don't want to wipe data - takes a couple hours to put everything back in place. And I really, really don't want to install GAPPS . . . although I suppose I could disable them as soon as I install them, as I did with the first iteration of this ROM.

For now I'll have two backed up versions - a 322 ROM for flying. And a 328 ROM for daily driving.
[Nook HD, HD+ Android Development] PMikeP:
Some progress w/ 328

So, I enabled Google Play, Framework & Services in 322 and then dirty flashed 328. Doing that solved the problem with my two apps not surviving 328.

Unfortunately the keyboard is still not working for me in 328. But that might be because I have most of the services in the three Googles disabled. (Update: Or I wonder, since we're using a CM11 keyboard, if we need an updated version of the three services?)

My next plan is to do a clean install of 322 and then flash 328 on it before I start hacking away at services.
[Nook HD, HD+ Android Development] Jon Lee:
It hasn't really been explained, but the easiest way to do a full format, for a clean install, with twrp is convert to an opposite filesystem of the one you want and then go back to the one you want. That's what I do anyway, and I think it would save on these types of issues.

Just to compound things further, I ended up personally going with omnirom's keyboard. I think I like it the best.

I DID run into problems and had to do a full format though (yesterday)- instead of dirty flashing (internal builds). No issues since.

I also ended up making yet more changes to the touchscreen driver.

I've been testing those changes for four days now.

I seems I might have the touchscreen driver done now, so I can stop OCD'ing on it.

I think I will have to share that change eventually, but I'm slightly hesitant until everyone gets over having to format because of the keyboard changes.

;)
[Nook HD, HD+ Android Development] PMikeP:
Hi Jon:

Please don't take any of the keyboard issues personally. I, for one, am very appreciative of your efforts. (While I'm not glad you finally had the same problem, it's good that you saw it yourself. Any thoughts as to what's causing the problem? Like, another .db file, per http://xdaforums.com/showpost.php?p=59320312&postcount=212 ?)

Instead of taking 4 hours to format and install 328, I'll wait until you feel like releasing the final build. 'Course, if you want to PM me the link to the mediafile . . . ;)

And when you say to full format, we're talking /system & /data again, correct?
[Nook HD, HD+ Android Development] twiztid_:
have you tried deleting /system/lib/libjni_latinimegoogle.so if it exists?

To re-enable swipe/gesture typing, make a copy of libjni_latinime.so and rename the copy to libjni_latinimegoogle.so
[Nook HD, HD+ Android Development] PMikeP:
The latinimegoogle.so file doesn't exist in my running 323 build. And I don't use swipe, but I could try the renaming trick on 328.
[Nook HD, HD+ Android Development] Jon Lee:
Alright, here is kernel source with the latest touchscreen changes.

http://www.mediafire.com/download/i273dyrz1lyryoo/kernel-20150410.tar.gz

For convenience, here's an experimental test build that demonstrates those last touchscreen changes.

http://www.mediafire.com/download/k762kaz0t3uctzo/cm-10.2-20150410-UNOFFICIAL-ovation.zip

http://www.mediafire.com/download/as2ki75gcppucyp/cm-10.2-20150410-UNOFFICIAL-ovation.zip.md5sum
[Nook HD, HD+ Android Development] PMikeP:
Took about 3 hours, but I got it installed. I tried a dirty flash-no joy. So I did Jon's thorough format/wipe. That got me up and running. Then I had to install twtizid_'s modified GAPPS http://xdaforums.com/showpost.php?p=59271962&postcount=202 for my GPS Bluetooth & blitzortung to install.

I'm beginning to hack out bloat now.

Yea!
[Nook HD, HD+ Android Development] Jon Lee:
Do you use a GPS dongle? Because of post #250, I disabled the build option:

#BOARD_HAVE_FAKE_GPS := true

In this latest build.

I'm wondering if it made any difference?
[Nook HD, HD+ Android Development] PMikeP:
No, I don't use a dongle. I use a Tom-Tom GPS that xmitts BT. I use an app that picks it up. (http://downloader-apk.com/?id=btgps using mock location, w/ Location Service off.)

At first, BT wouldn't turn on with Wi-Fi enabled. So I disabled Wi-Fi and BT became active. Still, it took a long time before BT picked up the T-T for pairing. But once it did, I could run Wi-Fi again, although it took a couple of toggles before Wi-Fi scanned my router correctly.

Anyway, despite the iterating, GPS works fine.

P.S. The app Wi-Fi Analyzer doesn't work. I'm guessing it can't hook what it used to after you improved the wi-fi protocol. Not a problem - just noting it.
[Nook HD, HD+ Android Development] Jon Lee:
No. It's because I used TI/omapzoom jb source for hostapd, which allows for Wi-Fi direct connections (try it!), but broke Wi-Fi analyzer. I haven't ran a difference between TI and CM's source to know why exactly, I know WPA_supplicant and p2p_supplicant are different as well. I'll have to purchase a miracast dongle to further experiment with screen casting. Or if anyone can recommend any file beam transfer apps to use with Wi-Fi direct (I would like to beam files/pictures between phone and tab).
[Nook HD, HD+ Android Development] shdware:
You have a Roku 3? That will support Miracast.

Haven't experimented with Wifi-beam though.
[Nook HD, HD+ Android Development] PMikeP:
I have a Roku stick.

I have enabled Roku's direct wi-fi access (beta) in Roku Settings.

On a whim, I went into Wi-Fi on my Nook HD+ and tapped on Wi-Fi Direct.

Lo and behold, the Roku showed up and I could "invite" it.

I clicked and it "connected." Something popped up on the TV about displaying a video from my android. But the gas gauge only got about a third fill and nothing happened.

Obviously, I don't know what I'm doing. (I recall seeing something about enabling miracast on one of these ROMs once.)

But I thought I'd report it, FWIW.
[Nook HD, HD+ Android Development] Jon Lee:
It would be interesting to see the logcat messages...

I'm fairly sure I can get miracast working, at the very least as source.

Basically, though, I'll have to purchase a miracast dongle for testing.

(I know I used wifi-direct source without hdcp hooks. I might have to use the later source with hdcp hooks.)

Anyway, it's do-able.
[Nook HD, HD+ Android Development] Jon Lee:
Then go to settings-display-then Wireless display/enable, and see if it lists your device.
[Nook HD, HD+ Android Development] PMikeP:
I tried that at the time. There are two things going on in the Wireless display Setting.

First, when I tried it, it didn't show any devices available. (That was with the Roku connected.)

Now that I've tried it (and while toggling Wi-Fi on and off), it's "stuck," saying that No devices are available because Wi-Fi is off. Even tho Wh-Fi is on. (The On/Off switch is greyed out, but stuck at "on.")

Update: I noticed that Roku offers an app called Twonky, which supports beaming. It might be the ticket-but as before, my Wireless Display Setting is stuck at "off."
[Nook HD, HD+ Android Development] Jon Lee:
I think I may have found what I was looking for in order to fix that.

https://raw.githubusercontent.com/C...rameworks/base/core/res/res/values/config.xml

Namely,

<item>"wifi_p2p,13,1,0,-1,true"</item>

in networkAttributes...

Building a test build now with those changes.
[Nook HD, HD+ Android Development] DSoundso:
I'm getting random freezes and tablet reboots vor I habe to force it to. Mostly it happens while browsing vor readng pdfs. I doesn't happen instantly maybe 15-30 min into it.

What could that be? Wifi is in and I usw The 4.3 gapps with lollipop keyboard.
[Nook HD, HD+ Android Development] Jon Lee:
If you get a reboot, afterwords go into /proc and view last_kmsg, and then one could copy/paste that message here to help with debugging.

Not much to go on. Personally it sounds like your pdf viewer app, or a corrupted cache... dunno.

Also, what are your governor/IO settings?
[Nook HD, HD+ Android Development] Jon Lee:
I still don't know if it will see a display device, but the above did fix the wifi display on/off from "sticking".

(same kernel source as previous)

http://www.mediafire.com/download/6tlsdcdcsac997g/cm-10.2-20150414-UNOFFICIAL-ovation.zip

http://www.mediafire.com/download/8y26nz26ga1z3tv/cm-10.2-20150414-UNOFFICIAL-ovation.zip.md5sum
[Nook HD, HD+ Android Development] shdware:
I'll install today and test.
[Nook HD, HD+ Android Development] PMikeP:
I tried it and managed to get the Wireless Display toggle to stick again. (Took me longer this time. :) )

Here's what I did:

I did a Factory Reset.

I wiped /system. (Redundant with next step.)

I flashed this ROM.

I let it boot and set my local time zone. (Just in case a time difference messed up Wireless Display.)

Booted to Recovery.

I installed the stripped down version of GAPPS. (Do we needed a fuller version to make this work?)

I turned on Wi-Fi.

(But I didn't not enter any passwords just yet. So nothing connected, per se.)

I went to Wireless Display, which told me "To see devices, turn wireless display on."

I toggled the blue on/off and it toggled, but the "Search for displays" did not come alive.

(IIRC, it did come alive on the previous ROM when I was trying all this and told me "nothing found." But I didn't take notes like I did this time, so I could be wrong about this recollection.)

Moreover, even when the blue toggle says "ON" on the Wireless Display page, the text says "Off" when you go back to the Display page and look at the Wireless Display summation.

I toggled Wi-Fi on/off; I played with Direct Connect to the Roku. Somewhere in the process, I managed to freeze the Blue toggle again.

I also installed a media share apk that is supposed to work with Twonky on the Roku. No joy. (I toggled Roku's Beta screen mirror on and off. Same result as before when on - I get a gas gauge about loading a video (I don't know what video they're talking about) which stops at the one-third point.

I remember seeing a Nook HD+ owner in the forum talking about what he had to do to get miracast working. I'll look for it in the background.
[Nook HD, HD+ Android Development] Jon Lee:
I'm not positive but I think you have to connect through Wi-Fi direct in WiFi settings before checking for displays in wireless displays in display. I believe AOSP kept those two together but CM split them which makes it less intuitive.
[Nook HD, HD+ Android Development] PMikeP:
I tried that in my many iterations. I let it connect to my Wi-Fi router too. I wasn't able scan for wireless displays. I'll plan to do clean flash of your previous build later.
[Nook HD, HD+ Android Development] Jon Lee:
I'm in the process of building another build.

I reverted all Wi-Fi direct source to original and removed WiFi p2p device type from the overlay (like the s4 overlay has it).

This one should be ready to test tomorrow afternoon.

(PS. There should be no reason why you should have to revert back to the previous build unless this one has problems... besides Wi-Fi direct...)
[Nook HD, HD+ Android Development] PMikeP:
Okay, I'll wait. Tnx.
[Nook HD, HD+ Android Development] DSoundso:
I already made a fresh and clean install of your recently posted rom update from the 14th. So I'll see if the freeze still happens and am if so, I will post the kmsg stuff. Thanks for now.
[Nook HD, HD+ Android Development] PMikeP:
BTW, have you noticed that the Wi-Fi Region Code is stuck on Europe?