yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] TBueno:
I've been running the 05-10 build for a couple of days on my HD+ and I'm impressed!

Flashed over CM11-m12 without any issues

Everything is working as it should (except for Deezer, which is mute)

It is more stable than stock, CM10 and CM11: only one reboot so far, after some flickering in Firefox while charging. Browsing OK when not charging

Using gooogle keyboard without major issues, HW overlays always on

CM11's irritating and well-known SystemUI crashes are gone (top and bottom bars used to disappear, throw me back to lock screen)

Notification and quick settings shades are "unified" in the center and very stable, big improvement from CM11

No lock screen issues, it actually works far better than CM11's

Video and audio streaming work, so does bluetooth and Wifi

Battery charging, estimates and monitoring all flawless (including red/green LED), battery life seems improved since CM11

Performance feels similar to CM11, only task switcher and Newsstand feel slightly slower. But task switcher wasn't exactly snappy in CM11-M12 either. Lollipop's fancy graphics and the HD+'s sheer resolution are to blame probably

Chromecast works for audio now, it didn't under CM11, had to use AirAudio

Smart lock is working, although geolocation is finicky on this device. BTW, Maps couldn't determine current location under CM11 either, this ROM is not to blame

Had a couple of "memory kickouts" on heavy apps, but it handled them quite elegantly: just sent me back to home screen without any error messages or systemUI fuzziness. Guess it's to be expected with that little RAM. In CM11, these events usually led to sudden reboots

None of CM11's touchscreen freakouts so far, screen rotation is faster

The only really strange issue I've run into is speakers becoming completely mute (no music, notifications, alarms etc). Once it was right after using bluetooth phones, but reconnecting and disconnecting them did the trick. The second time didn't involve the headset, and it needed a soft reboot.

From what I've been reading, most of the bugs being reported in this thread are not specific to this ROM.

It's a bit early to be sure, but in my experience this is the best software ever available to the HD+, especially stability-wise.

Thank you AMaces for all the work.
[Nook HD, HD+ Android Development] twiztid_:
Just to confirm, the experimental build you're talking about is the HD+ 5-23 build, right?
[Nook HD, HD+ Android Development] amaces:
You must be one of the lucky folks hardware-wise, if no flickering/reboots with Google keyboard ;) Maybe it's a different panel, better CPU/GPU binning, who knows, but glad it's working well. I'm mostly building on [MENTION=4243514]Hashcode[/MENTION]'s already solid foundation, and yeah, we're making progress, albeit slowly… At any rate, about the issues not discussed as much here, Wi-Fi based location was fixed in CM11, then another Play Services update broke the interface again, and to my knowledge, it never worked in CM12. The touchscreen is definitely better behaved compared to CM11, although it must be the updated kernel, since I only rarely need to suspend/resume now to fix fantom touches. By the way, I'm pretty pleased with the recent progress with zram and memory management, so test out the ovation build in the experimental folder. I'm still tuning some of the settings, but these work pretty well already:

echo 1 > /sys/kernel/mm/ksm/deferred_timer
echo 100 > /sys/kernel/mm/ksm/pages_to_scan
echo 500 > /sys/kernel/mm/ksm/sleep_millisecs

echo 1 > /sys/kernel/mm/ksm/run

echo 70 > /proc/sys/vm/swappiness

Yup, the hummingbird build (same codebase) followed after testing that ovation actually boots, thus the date difference. I tend to remove unneeded experimental builds quickly.

P.S. I've been working on making LiveDisplay potentially useful on these Nooks. It's nowhere near being done (new cmhw glue code has to be written, plus proper color calibration kernel support), but gamma control already works in the experimental boot-gamma-ovation.img (HD+ only, of course, and I think it'll work on top of the 5/23 build). The sysfs node is at /sys/devices/platform/omapdss/manager0/gamma; default is disabled (echo 0 > …), 5 or 6 replicates normal calibration, although be prepared for panel resume lags with anything other than zero. Also, Trickster MOD now becomes aware of the gamma interface, and can control it.
[Nook HD, HD+ Android Development] KevHD+:
Google maps location has been working for me as long as I use a version of maps no later than 9.1.2.
[Nook HD, HD+ Android Development] bk_xda80:
Ugrade from CM10.2.1-ovation?

I am having issues with Playstore and very laggy performance. Can I upgrade from 10.2.1 to the latest without losing files and settings? How (do I need to backup and restore, or just install the upgrade and all will be well)?
[Nook HD, HD+ Android Development] dk1keith:
Best Rom I've Used

Just wanted to say thanks for a Great Rom. I only use my HD+ for light everyday use so most of the issues some heavy users have experienced aren't an issue for me. Please keep up the great work, and again thanks much.
[Nook HD, HD+ Android Development] tebra:
Thank you, I confirm that location works with Google maps 9.1.2
[Nook HD, HD+ Android Development] TBueno:
A full nandroid backup is a no-brainer.

I can attest firsthand that upgrading from CM11 works without any issues (CWM 6.0.4.6 recovery), I'd give it a try from CM10 if I were you, it saves a lot of time and the trouble of setting everything up again.
[Nook HD, HD+ Android Development] evaporic:
Has anybody been able to run Disney Toybox https://help.disney.com/articles/en_US/FAQ/About-Disney-Infinity-Toy-Box-2-0#Android on this ROM?
[Nook HD, HD+ Android Development] TBueno:
It happened to me too. The first words of phrases would get cut. I realized there's actually a delay in voice detection.

So my workaround is: after triggering voice search, wait for the "listening..." prompt to appear and then about three seconds. Everything you say then will be properly captured.
[Nook HD, HD+ Android Development] starbright_:
Any idea, why with 0510 Wifi doesn't reconnect automatically after some days? After some days enabling WiFi is not enough, I have to press Connect button as well.
[Nook HD, HD+ Android Development] Ferd Burfle:
I have not seen that problem on my Nook HD or HD+. I connect to several WiFi networks daily, and all have automatically connected as expected.
[Nook HD, HD+ Android Development] myjess:
Toying with idea of upgrading to lollipop, but I have voice search and play issues on my HD+. Every now and again I get a message saying one or the other has stopped. I think I have a later version HD+.

Reverting to stock at the moment to see if I still have issues.
[Nook HD, HD+ Android Development] tebra:
Same conclusions for me with last experimental build for hummingbird without ksm. No app crash and no reboot and a little more faster.
[Nook HD, HD+ Android Development] pastordl:
Been running the Ovation 5/24 exp for a few days now and can say it is smooth and faster. This is with the suggested tweaks. Can watch 1080p video with no problems. Do get some screen flicker in landscape while editing this post. No flicker in portrait. The changes are doing well IMO. Thanks Amaces. :good::highfive:
[Nook HD, HD+ Android Development] ahriad:
What tweaks? I'm on 5/24 and i cant open more than one tab in dolphin browser, and even SwiftKey crushed a lot, also when I run a music player in background it close because of low memory. And what makes things more strange I didn't install Google services at all instead I use Amazon app store.
[Nook HD, HD+ Android Development] pastordl:
These tweaks listed back when 5/24 was released on 5/24.

Here

By the way I did this while in Dolphin and using SwiftKey and 187mb free. Check what you have running in the background sucking up memory. Freeze/disable those you don't use.
[Nook HD, HD+ Android Development] TBueno:
Spoke too soon while thinking I'd been spared from the AOSP/Google keyboard bug: when annotating a book in the Kindle app, it happened: blank unresponsive screen, had to force a reboot. A weird bug indeed.

Swiftkey seems more resilient, but flickers helplessly in landscape mode (as does Google's). Running the 0510 build for the HD+.

I wonder if other tablets running CM 12.1 have the same issue...
[Nook HD, HD+ Android Development] amaces:
Properly synced builds will follow later this afternoon, with even larger zRAM (192 MB) and increased swappiness (70) included; no need for custom scripts unless you want to customize these values. The changes are uploaded to my forked GitHub repos, and pretty much only make sense with LZ4-backed zRAM & zcache.

No idea about this, but looking through their requirements, I see xhdpi (Retina, or better), whereas our screens are only hdpi.

Weird indeed, since I've actually used this in the past, and it worked fairly well in the early days of CM12. Let's hope it's coming from CM repos, and not from Google's proprietary stuff.

If that total includes swap, it would make sense with the 64->192 MB increase in zRAM size. Beyond critical memory happening much less often, I'd like the device to feel more usable, stop killing so many recents, ideally keep a few Chrome tabs and the keyboard in foreground ;)

Today's builds will have all those experimental tweaks built in; if it still happens, try a clean install, if you haven't done that in a while.

It's not so much a CM12 bug, but rather due to our kernel; we've been dealing with this since the early days of CM12, and there are many reports/posts about it. It frustrates me to no end, and it's one of the main reasons I started building my images. Any 1080p OMAP44xx device using our kernel and the current TI SGX DDK would probably suffer from the buffer underflow bugs, but there aren't many such devices. That's why making the unified 3.4+ kernel work for us would be great progress, alas that may never happen.

About SwiftKey, it used to be my go to keyboard till the current 5.3 version; now it triggers the same problems as the Google keyboard, so I reverted to Hacker's Keyboard, although I kind of hate looking at it ;)
[Nook HD, HD+ Android Development] mhunt13:
[MENTION=4473900]amaces[/MENTION] - Thanks so much for all your work to keep our devices usable!

I have been using your 5/10 build on HD+ since you made it. I also use Hacker's Keyboard, think I've gotten use to it LOL. The best part is no screen flickering, no reboots, and it seems pretty snappy. I like it so well, haven't thought much about changing it. I will try one of your newer builds at some point .... but I have a backup of 5/10!
[Nook HD, HD+ Android Development] TBueno:
That's one precious tip! Thanks a lot! Using a one-version-old Swiftkey is a small price to pay for reclaiming stability! (that slide-out settings menu feels clumsy anyway, although the new default theme looks cool)

Hacker's Keyboard is not bad at all (very settings rich), but Swiftkey is surely sleeker. The last version suitable to landscape use in the HD+ is available here, and I've managed to unlink it permanently from Play Store using this method. The re-signed version does Swiftkey Cloud and all, and I don't have to worry about hitting "update all" in Play Store.

Just a quick confirmation: is RAM compression enabled by default in 12.1-20150523-UNOFFICIAL-ovation?
[Nook HD, HD+ Android Development] amaces:
Lots of changes under the hood this past week; new builds are up now.

The May 23rd build does contain much of the improvements enabled, but I deem today's build stable enough to live in its own folder. Now, we've had a small chunk of memory compressed in zRAM since Hashcode's early builds, but it was backed by an older, slower compressor (LZO). After I merged the revamped zRAM, zcache, etc, we could switch to LZ4, and since compression is significantly faster, a lot more memory can be feasibly swapped to zRAM (up to 25% now). Increasing the swampiness forces this swap to actually be used, so we can gain almost 100 MB extra RAM, or about 13% of the previous total memory. At the end of the day, I go by subjective feeling, and definitely like my device better now.
[Nook HD, HD+ Android Development] evaporic:
Quote:

Originally Posted by evaporic

Has anybody been able to run Disney Toybox https://help.disney.com/articles/en_...ox-2-0#Android on this ROM?

AMACES:

No idea about this, but looking through their requirements, I see xhdpi (Retina, or better), whereas our screens are only hdpi.

Thank you taking the time to respond :)

How do I check if a device is xhdpi vs hdpi. I guess the reason I am confused is that the app runs on my lenovo tab 2 A10-70 but it force closes on the nook.

I compared the display specs and they seem similar: (1920x1280) 256ppi

http://www.phonearena.com/phones/compare/Lenovo-TAB-2-A10-70,Barnes---Noble-NOOK-HD/phones/9273,7512
[Nook HD, HD+ Android Development] tebra:
[MENTION=4473900]amaces[/MENTION] could you post the md5som of the last hummingbird build. When I tried to flash it TWRP reboot. Thanks again for your support for this device
[Nook HD, HD+ Android Development] amaces:
Here's how they define the different DPI classes: http://developer.android.com/guide/practices/screens_support.html#range. If it runs on the Tab 2, that means they don't really enforce the xhdpi requirement, and the HD+ should be more than OK display-wise. My guess was wrong; it must be something else that crashes the app. Does the A10-70 also have CM12.1, or a Lenovo stock ROM? Also, if you can capture logs during crash (primarily logcat), might be able to debug.

It's 6805f3bde7ba19a6e89b956d46486442 for hummingbird; hopefully it's not a bad build.
[Nook HD, HD+ Android Development] prsa01:
what a GREAT build!

I've used every 12.1 build. Initially had to disable hw overlays on each one to make them usable. Between this ñewest buuild and switching to hacker's keyboard it is close to perfect. Not much difference now between this and my nexus 7 '13 with significantly less processor and memory. It even seems cooler and battery life seems better (ok, maybe some imagination on my part).

Back to being one of my favorite devices

Thank you so much

Ovation 20150530 on hd+
[Nook HD, HD+ Android Development] TBueno:
:good:

First impressions on 0530-ovation couldn't be better. Seems as stable as 0510 but slightly faster in window transitions and multitasker, and also Newsstand and Play Music. Browsing in CM's and Chrome is quite smooth, Deezer now works.

Can't tell yet if RAM compression is helping out, launcher redraws are still quite frequent, but not a big hassle.

I guess the HD+ wasn't actually built for speed, but with these latest builds and Hacker's or Swiftkey 5.2, it is finally a reliable tablet.

These ROMs have breathed new life into our devices, for which I thank you again!
[Nook HD, HD+ Android Development] sincewhen:
Notification bar problem

When I pull down the notification bar and then press the volumn up/ down button, the screen start !@#$%^&*().

Not a big problem, but hope you can fix it soon ;)
[Nook HD, HD+ Android Development] tebra:
It was just a bad download. Everything is fine now with last build for hummingbird. Thanks
[Nook HD, HD+ Android Development] TBueno:
Doesn't happen on 0530-ovation here, just tested in both portrait and landscape.

I take back what I said about the marginal performance improvement: it is actually considerable (from 0510). Everything is running quite better.

Those who watch a lot of movies and might be hesitating to install this should know that full hardware decoding is working beautifully in VLC. :good:

Also, I tried to set Browser as a lock screen in 0510 but it wouldn't actually launch. This has been solved in 0530 as well.
[Nook HD, HD+ Android Development] N0he:
Where do i find 0530? It's not where the others are :o
[Nook HD, HD+ Android Development] mhunt13:
Click the ovation folder, the 5/30 build is in there. (the 5/10 folder date is likely creation date...)
[Nook HD, HD+ Android Development] twiztid_:
510 is the older stable build. Both 510 and 530 are in the respective folders for Ovation and Hummingbird.
[Nook HD, HD+ Android Development] pastordl:
5/30 is awesome smooth as silk, stable, no Disable h/w overlays, and typed this with 5.2 version of SwiftKey w/o any problems. Thanks Amaces, great job. Hopefully this gets us closer to becoming "official".
[Nook HD, HD+ Android Development] nimaim:
I just dusted off the ol HD+ due to all the very positive feedback and I have to say this ROM is running beautifully. Just set it up with the 5/30 ROM, gapps here, nova launcher, hacker's keyboard, and no flickering of any kind whatsoever and both Netflix and Plex playing all media flawlessly. The responsiveness is very acceptable (obviously slower and bit more sluggish than CM 9/10 due to very old hardware so that's understandable). I was close to selling this thing but I have to say I will probably keep it now as a portable media player so I don't have to use my phone. Thanks again amaces ... can't believe this guy is running 5.1.1. :good: Will test drive it some more ...
[Nook HD, HD+ Android Development] Zippy Dufus:
What's the latest manifest to pick up all your new goodies?

My 05/17 build with your patches applied to verygreen's kernel is not the best build that I have had. I've seen more flickering and other unusual things than in my previous builds.

Also, any news on the Hangouts Dialer issue?

As always, thanks for your great work!
[Nook HD, HD+ Android Development] king200:
The Hangouts dialer works ok on my Ovation.

The 05/17 is working best for me. Actually, I can't believe how wonderfully my HD+ is working.
[Nook HD, HD+ Android Development] Zippy Dufus:
Thanks for the info!

Dialer is still broken in my build so I will try the build in this thread.

I wonder if I got different firmware or something? Perhaps this is related to different variations of the hardware?

Below is my local manifest.

Investigating ...

<?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>
[Nook HD, HD+ Android Development] king200:
If it makes a difference:

u0_a106@ovation:/ $ su

root@ovation:/ # cd /sys/class/block/mmcblk0/device

root@ovation:/sys/class/block/mmcblk0/device # cat name

MBG4GA

root@ovation:/sys/class/block/mmcblk0/device # cat manfid

0x000015

root@ovation:/sys/class/block/mmcblk0/device # cut -b 19,20 cid

06

root@ovation:/sys/class/block/mmcblk0/device # cat date

10/2012
[Nook HD, HD+ Android Development] qwert940:
Does 5/30 fix the flickering problem on hummingbird? Anyone?
[Nook HD, HD+ Android Development] tebra:
Never had flickering problem on hummingbird here.

Only on reboot sometimes but lock/unlock fix that

---------- Post added at 02:04 PM ---------- Previous post was at 01:20 PM ----------

Hi Amaces,

still wish to see the kernel patch for wiimote.

Please have a look at this other kernel patch to use Nook as a usb keyboard: https://github.com/pelya/android-keyboard-gadget

If I understand it good we also need a K3.1 at minimum :(
[Nook HD, HD+ Android Development] belfastraven:
With 5/30 build , on hummingbird, on both my nook hd's, the machines just "die" for no apparent reason. This seems to happen only while they are not plugged in, even with battery reporting close to full charge. When plugged in, they will reboot. Is this a return of the famous "sleep of death"? I tried disabling ksm; it makes no difference. This is the first time in any of [MENTION=4473900]amaces[/MENTION] builds this has happened. Has anyone else seen this? I'll try to investigate further.

Re flickering: my 16G which came with grey externals will flicker only when apps are being updated after rom upgrade but will stop after being plugged in for a few minutes. The 8 G with white externals never flickers.
[Nook HD, HD+ Android Development] hajkan:
Where is that folder? This is the only one I see on CMod website oad: cm-11-20150524-NIGHTLY-ovation.zip
[Nook HD, HD+ Android Development] keshabbhattarai126:
It's here.. Read the thread properly..specially first 2/3 post by OP.

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww
[Nook HD, HD+ Android Development] hajkan:
Thank you for the links. Exactly what I was looking for.
[Nook HD, HD+ Android Development] drmarble:
Amaces:

You don't have to be concerned about the number of changes you made to the cm code for ovation/hummingbird. While it would be unreasonable to put them all on gerrit the device maintainers (Hashcode and Verygreen) can push them straight to the source tree. They can pull your changes from your github and push them en-masse to the cyanogenmod tree. You are correct that these changes need substantial testing before getting pushed.

I will be testing out your changes on my personal cm-11.0 build. I had good luck with Hashcode's 12.0 kernel. It improved performance. I expect more improvements from yours and will post the results of my testing. Thanks for you work on these devices.
[Nook HD, HD+ Android Development] Zippy Dufus:
Thanks for the local manifest! I'll be building soon. I've been using your 05/30 build all day and it is working great! In fact, I've been doing carefully controlled Antutu benchmarks and will compare it to my linaro build with your experimental kernel and patches. I'll post the results ... unless they are embarrassing! ;)

Sadly, I confirmed that Hangouts Dialer still isn't working for me with amaces's 05/30 build. [MENTION=4493588]king200[/MENTION], you must be the luckiest NookHD user alive! :)
[Nook HD, HD+ Android Development] amaces:
That is definitely not good… Even if it's an isolated case, we need to debug; sounds like ADB will no respond at all. Can you pull something like /proc/last_kmsg right after this happens? What about the contents of the /data/dontpanic folder, possibly recent stuff in /data/tombstones? Once we have some sort of pointer, I can start sending you test boot images till it's fixed.

Very true, [MENTION=4190710]drmarble[/MENTION], although I fear that my changes are starting to run counter the current philosophy. It looked like swap use was not encouraged, with swappiness reduced all the way down to ten. So, Android's MM and LMK were trusted way more than the normal Linux processes. I thought the same (and still sort of hang onto that), but in practical use, a large, heavily swapped zRAM just feels better, even with the inherent slowdowns.

At any rate, I do hope these changes will be useful with KitKat, where buffer underflows hopefully happen far less often.

Benchmarks will surely be disappointing; even after disabling the currently mildly-tuned KSM, the system is definitely busier compressing/decompressing large chunks of LZ4 memory. I was afraid battery will take too much of a hit, but so far so good. Regarding Dialer, same conclusion as before, lots of work with little payoff, especially compared to something like a better kernel. P.S. I'm still debating whether my old patches actually make enough of a difference, so they're not included in the main g-3.0 branch yet, but you can find them properly committed in d-3.0, for easy cherry-picking. Those old files, although pretty much the same, were raw patches without proper attribution, so they're obsolete now.
[Nook HD, HD+ Android Development] king200:
"Sadly, I confirmed that Hangouts Dialer still isn't working for me with amaces's 05/30 build. [MENTION=4493588]king200[/MENTION], you must be the luckiest NookHD user alive!"

The dialer works...meaning it dials the other phone, which rings and can be answered. There is no communication other phone cannot hear me or me here them. That's with microphone and wired headset.

I got a fast error message that said indicated that the camera wasn't working properly? I have no idea of what that's about.