yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] twiztid_:
I can't say for sure, and I can't speak for everyone, but my flickering issues are now only an annoyance. I don't have any more force restarts* with the latest build, and the flickering does stop for a bit after a few times, but I typically finish typing what I need to before it starts, and well before it starts again. I am very happy with the progress being made, thanks a ton!

* I did have two instances of flickering forcing a restart using F-Droid, but I updated the app and the problem went away.

Any improvements in particular? Speed/transition improvements hopefully? Or more functionality-wise?

One annoying "bug" I've had, when I close Browser via (X) on tab, sometimes it takes a tap or two due to my fat fingers lol, but a lot of times I end up tapping one (or more) time too many because the screen still shows Browser, but the tap(s) end up going through to the home screen and launch an app. It's a mild annoyance at worst, and has gotten SIGNIFICANTLY better in the past few builds that have had noticeable performance boosts. This would probably happen with other apps as well, but Browser is one that I end up closing in the app itself, rather than tapping Home or using the square button and swiping the app away.

You could try running Advanced Battery Calibrator.

My phone had a similar battery drain issue , and that fixed it. I did have to run it twice, the first time I didn't exactly follow the instructions the first time around (Charged, ran app, left plugged in for a few minutes, unplugged and turned on), so that may have been why. So let your battery drain until it says it's almost dead, run the app and let it power off, then charge to 100% before turning on.

I also wiped the /Cache and /Dalvik the second time around, powered on and booted directly into recovery, so if you don't mind doing that I'd suggest giving it a try as well.

Maybe it's because I just don't know a whole lot, but it seems odd to me you have some big gaps in your battery stats. I've only seen gaps when my device is off, but yours is showing WiFi as being on... but then again, your span shows 10 days with no charging time, which I've never seen, so...
[Nook HD, HD+ Android Development] mr72:
I often have to unplug/replug my cable to get it to light amber and actually charge. This is a very consistent issue across all CM builds I have run beginning with CM9, the first ROM I flashed the day I bought the HD+. It's only mildly annoying since it gives basically immediate feedback, so you just unplug/replug about three or four times and eventually it'll start charging.

The other mildly annoying but super consistent bug is on waking with the magnetic sensor, which about 75% of the time does not work the first time and you have to shut/open the case again to get it to do it. I'm now in the habit of just doing open-shut-open every time I open. Annoying but not a deal breaker.
[Nook HD, HD+ Android Development] amaces:
Testing Official TWRP Images

We're closer to official TWRP support; can everyone able to do so, test the two recovery images in the experimental folder (both ovation and hummingbird)? They're generated on the TWRP build servers, from the official CM12.1 bn/omap kernel (3.0.72), and the only bug I fear is non-responsive touchscreen. But no worries, these images should be safe otherwise, and you can easily return to mine if needed. Also, these images use the standard TWRP theme (since the new one is WIP/not yet merged), so you'll easily be able to discriminate between different 2.8.7.0 builds.

I though that was still in? I see now that USBHostSwitcher is commented out; no wonder the app is nowhere to be found. Still, can you describe what happens currently, when you attempt to use that functionality? If you're sure it's broken without the app, a bug report (here, or on the CM12.0 thread), would be a better way to organize this information.

You missed the part about only non-BT audio input being fixed… About BT keyboard input, I'll dig up mine to check if it still works.

Both in the long term (read months), but I'll do lower expectations for now, focus on the few issues needed for official support.

Yes, that has been my experience with Browser as well; pretty frustrating, given that other similarly-tabbed apps (e.g., Chrome) are a lot better. One thing that I noticed empirically is that the touchscreen is not uniformly responsive across all areas (at least my variant/batch). So, it's probably hardware shortcomings, plus subtle sizing differences in Browser's control widgets. Have you tried setting the display density to 260 (closer to actual PPI than the default 240)?
[Nook HD, HD+ Android Development] ieatabiscuit:
I'll be testing the Bluetooth with several things, I'll give feedback on what does/doesn't work. Just because I use things like a Pebble, and sixaxis, and my daughter has a fitness band and what not. My reasoning: I don't see anything on that in here, so why not? I would think it will work fine with everything, but we'll see tonight.
[Nook HD, HD+ Android Development] amaces:
Well, it can't work with every BT peripheral, just considering how the stack is designed; it's not a monolithic piece of software, and not even fancy vendor stock supports all profiles. Considering the small number of people using custom ROMs on these Nooks, plus the relatively niche community of Pebble users, etc, no reason to expect the Venn overlap to be significant…

Still, don't forget to verify that those semi-official recovery images work for you, if you're in a testing mood.
[Nook HD, HD+ Android Development] pastordl:
Tried the test TWRP 6/29 image. Installed in recovery fine, but gui unusable. Touch, tap, Double Tap, triple Tap, touch and hold, nothing. Had to press and hold power to restart. Used flashify to restore prior 2.8.7.0. Tried reinstalling test from flashify and no change. Like the theme in the prior ver better also.
[Nook HD, HD+ Android Development] amaces:
The GUI/buttons show up, but the touches register in wrong places, or not at all, right? I need some feedback about hummingbird as well, but yeah, I fear there may be a bug in our touchscreen driver, which is unearthed by recent changes with AOSP 5.1 and TWRP >=2.8.6. I fixed it by making trivial changes in TWRP (since that was easiest), but I'm pretty sure they won't accept hacky fixes upstream, just for the sake of our hardware.
[Nook HD, HD+ Android Development] twiztid_:
HUGE improvement.

I accurately hit the (X) and (+) buttons around 15 times with no mis-taps. Additionally, my typing accuracy has improved. I typed this twice and have not run into a major annoyance of mine, hitting the b/n keys instead of space. I was hesitant to post how good this change was without giving it a full day of testing, but the change was immediately noticeable in browser, and feels better all around, especially with long press to select smaller words.

If you can, and are interested in doing so, you have my vote for setting your builds to use 260 (or maybe even better, a "custom" PPI of 256) as default.

While I'm typing this, I've got an odd issue with skins. I installed a skin, euphoria dark, and my bars on the homesceen went from gradient to solid black. I disabled the skin, and even uninstalled (and wiped /cache and /dalvik), but its still solid. Any thoughts?
[Nook HD, HD+ Android Development] mhunt13:
Yes, had that same thing with 0622 build on my HD+. Each time I connected via USB to my laptop, the Nook would re-boot to blue screen. I had a couple of other issues with the 0622 build, so restored to 0615 backup. USB connects on 0615 as Media Device (MTP), transferring files works great. Also, other USB connection options are present.

Haven't tried the 0628 build yet.....
[Nook HD, HD+ Android Development] mikey williams:
Followed your advice - previously I had been wiping data,cache and dalvik but not system.

This time wiped system also and used the latest hummingbird version and success. No flashing (or rather a little but it stopped).

And as somebody else suggested turning the screen off and on enabled brightness adjustment.

Now happily restoring my apps. So far it all works beautifully. Well done amaces.

Thanks to everyone for patient help.
[Nook HD, HD+ Android Development] pastordl:
Correct with not at all.
[Nook HD, HD+ Android Development] mhunt13:
Just flashed the ovation Test 2.8.7 TWRP.

Flashed with Flashify, and it booted into recovery OK. Then I touched the 'Install' button -- but got the 'Factory Reset' screen. Tried 'Back' and 'Home' buttons multiple times but neither worked. Since I was stuck, just held the 'power' button until the Nook powered off. It appears the touch is way off, so you don't get what you touch ??

Booted back to CM, and re-flashed the original TWRP 2.8.7 -- with the new interface that is very nice!
[Nook HD, HD+ Android Development] belfastraven:
Re hummingbird test 2.8.7.0 TWRP. So far working fine for me. No touch problems. I haven't actually installed anything with it yet, but can boot and power off from recovery as well as boot into recovery from shutdown. Not as pretty as your version, however :)
[Nook HD, HD+ Android Development] tj2003:
The 06/28 build fixed the usb problem. So far it seems to be a good build.
[Nook HD, HD+ Android Development] TeutonJon78:
I"m getting the same issue -- green bars and lines in Netflix. However, it doesn't start working for me. After about 10 seconds it just quits out of the video and back to the Neflix menu.

HBO Go and Youtube both work correctly.

Otherwise, it's excellent -- seems way better than CM11.
[Nook HD, HD+ Android Development] pastordl:
Just tried again and now mine's not switching either. No force close though.
[Nook HD, HD+ Android Development] TeutonJon78:
It's not a force close -- the video just ends and the app goes back to the initial screen where you select your video.
[Nook HD, HD+ Android Development] panchokoster:
it seems to be working now, ... strange. I guess it was a faulty usb device.

but, you need the app to make it work. It can be found here http://nook.rootshell.ru/hd/USBHostSwitcher.apk. Otherwise it will not detect any device.
[Nook HD, HD+ Android Development] TeutonJon78:
Ok, I tried Netflix again to get a catlog, and this time, it did go to normal video after 10 seconds or so (which was the exact same video before that didn't work). Odd.

I've attached a catlog at debug level (not verbose) of the time of trying to play the netfix video. Lots of video and ducati issues.
[Nook HD, HD+ Android Development] pastordl:
Mine is back working again after 10+ seconds. Yep meant to say closes or shut down the video, brain stuck on fc. Wonder it the new Netflix mobile Web update was / is part of the problem.
[Nook HD, HD+ Android Development] ieatabiscuit:
I had an issue when running YouTube last night, got a lot of flashing static lines, then screen shut off, and flashed every couple seconds with static lines. Did forced shut down, then rebooted, and problem seems to be gone. Also, frequent SystemUI crashes, and tries to restart, then repeats until reboot. Again, after reboot, it clears up, and so far seems resolved on it's own. could be my download of the ROM, so going to check more before getting logs. Also, for Bluetooth, everything I have tested has worked fine. Sixaxis controller, keyboard, speaker, Pebble, Up24, and Subaru radio interface all work like a boss! Aside from the bugs that I really believe are from my DL of the ROM, this really seems solid. TWRP 2.8.7 has been working with no issues so far, and the reason I think it could be my DL is that I did not check MD5 as it was late, and I was lazy, and the install script in TWRP said successfull install, with code 0.20. Again, it was late, I was tired, so I have not looked into anything further yet. My issues seem pretty confined to my device from things I have read so far, so I'll look into things I have done first. Again [MENTION=4473900]amaces[/MENTION]: You rock, I'm loving this ROM on my HD+, and it is just the cure for the flashing itch I suffer from. Thank you!
[Nook HD, HD+ Android Development] js290:
Just flashed the test twrp using dd if=OFFICIAL_TEST_twrp-2.8.7.0-hummingbird.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery. I then tried rebooting into recovery, but now after the nook logo, it goes to a blank screen.

Power cycling doesn't try to boot ROM any more. I downloaded the file using the built in android browser. Anyway to get CM to boot again? Or, is this device officially bricked?
[Nook HD, HD+ Android Development] TeutonJon78:
If you look back a few posts, you can create a microSD recovery card and that should be able to get it back.

Why did you want to flash it via dd versus just using the built in way of using TWRP or Flashify? Seems much more error-prone.
[Nook HD, HD+ Android Development] js290:
Yeah, I remembered the microSD boot card for the initial CM install. I booted up with that, which went into the CWM recovery. It couldn't read the f2fs /cache partition, so it wasn't useful as a recovery. But, turns out, it didn't matter as cyanoboot loaded on the subsequent reboot. I flashed the unofficial twrp using dd, and it's all good again.

I then tried updating to 20150628 using the cmupdater, and ran into NIGHTLIES-581

Error executing udpater binary in zip '@/cache/recovery/block.map'
Error installing zip file '@/cache/recovery/block.map'

---------- Post added at 02:20 AM ---------- Previous post was at 01:58 AM ----------

I can also confirm the Netflix green video playback problem with 20150628-ovation. I downgraded to 20150622, and Netflix plays fine.
[Nook HD, HD+ Android Development] twiztid_:
That's probably why you ran into issues...

Hummingbird is for the Nook HD.

Ovation is for the Nook HD+.
[Nook HD, HD+ Android Development] Jon Lee:
It's good to have a bootable SD fastboot on hand (and setup). It saved me recently.

I had installed the 2.8.6(?) Recovery and it rebooted in the middle of a flash.

Would not boot back into recovery.

Had to use fastboot to flash my trusty 2.7.3 twrp, and then had to format all partitions- all were corrupt and could not be mounted.
[Nook HD, HD+ Android Development] js290:
Argh! Not sure how I missed that. Okay, will give it another shot later. :o
[Nook HD, HD+ Android Development] Tschumi:
The new recovery is stunning! Flashed it with flashify and had no problems flashing the latest nightly and adjusting the brightness.
[Nook HD, HD+ Android Development] Ferd Burfle:
I agree that the new TWRP performs better than the previous incarnations on my HD. Touch features are not as finicky.
[Nook HD, HD+ Android Development] amaces:
Recovery Info in the OP

After the recent reports blaming TWRP for soft-bricked devices, I've added a little section about rescuing a non-bootable system.

Can't say for sure as I haven't used Netflix in a long while, but my impression was that it uses DRM more aggressively than other apps. If the issues are somehow due to our Widevine library blobs being out of date, try the ovation ROM in experimental. It has the most recent binaries from https://github.com/TheMuppets/proprietary_vendor_oppo/tree/cm-12.1/msm8974-common. Otherwise, our kernel/video system hasn't changed since the end of May, and CM12 is as recent as can be.

Yes, occasionally the Ducati/M3 coprocessor stops working properly, and anything needing HW-accelerated video (e.g., YouTube, PBS Video ) will fail. Reboot usually fixes it, or power off for a few seconds, then restart.
[Nook HD, HD+ Android Development] asakurato:
Just flashed new TWRP along with newest build. I must say that this new recovery is most responsive TWRP I have ever seen! And UI is awesome, made for tablet.
[Nook HD, HD+ Android Development] TeutonJon78:
Someone a few posts back stated it worked fine on the 6-22 build, so maybe it's more of a general CM12 bug then.
[Nook HD, HD+ Android Development] pastordl:
Wow CM12.1 & Xposed update on the same day. Both running great. Somebody pinch me in case it's a dream. Thanks Amaces.
[Nook HD, HD+ Android Development] TeutonJon78:
Tried out the 7-02 experimental and it mostly fixed Netflix. Sometimes it just works correctly. The other time it had a blip of bad video, then some seconds of distorted liney video (but real color and not green tinted) and then it would work correctly.

So, it seems the Widevine library updates are needed.
[Nook HD, HD+ Android Development] amaces:
Thanks, could you continue testing it for a bit longer (after a few suspend/resume cycles, etc), and possibly collect logcats when the issues happen? If Netflix made changes to how it chooses codecs/sets decoding parameters, the fix is usually more complicated than just updating the proprietary blobs, but maybe we're lucky this time.
[Nook HD, HD+ Android Development] TeutonJon78:
So, I still had one video come up green a few times. But most of the time it works. There are few instances of it working, then going to the real color distorted and then working again. I was able to get two logs of that.

Let me know if you want more logs. As Netflix is an important use for this tablet, I'll be leaving the 7-2 build on anyway, since it works most of the time.
[Nook HD, HD+ Android Development] chili81:
Failing to "Turning Wi-Fi on..."

EDIT - False alarm - I was using a wrong gapps. Using the one from the CM12 wiki page worked.

I just tried the this for the first time and it looks so sweet - so smooth so nice!!! I can't get wifi to work though... I tried with both the experimental 7/2 build and the 6/28 build.

I used: EMMC CWM based recovery v6.0.4.6

Wiped data/factory reset

Wiped cache

Install the CM12 zip

Install the gapps from the cyanogenmod 12.1 page (gapps-lpmr1-20150607-signed.zip)

It boots up, does the 'optimizing apps' step, then during setup, it gets stuck on the "Turning Wi-Fi on..." step. I can skip that and and the system comes up and seems to be working well (so well! I must have!) but if I go and try to enable wifi, still no luck.

I saw a previous post with this issue that involved SELinux and a boot.img - but I didn't understand what that meant and if it was related to my situation at all. I did check in settings and SELinux is 'Permissive', if that matters.

Could it be related to CWM - do I have to use TWRP?

EDIT: I also tried wiping dalvik specifically from the advanced menu of CWM - no luck.
[Nook HD, HD+ Android Development] mhunt13:
Don't think TWRP is required, CWM flashing should work.

Your steps look good, though I would add wiping /system, too before you flash. There may be some leftover wi-fi bits in there causing your issues.
[Nook HD, HD+ Android Development] js290:
The gapps from the CM wiki are gapps-5.1-2015-06-02-15-19.zip and most recently gapps-5.1-2015-07-03-13-41.zip. I've seen on less capable devices (like acclaim) not capable of loading google play services in any useful way. But, ovation has always worked.
[Nook HD, HD+ Android Development] chili81:
Good eye [MENTION=6141348]js290[/MENTION]! I don't know wtf I got that gapps... I updated my Moto X the other day and somehow ended up with that file - I even checked md5's... who knows wtf I did. But ANYWAY - I got the right one from the wiki page and BOOM - wifi works!

Much obliged!
[Nook HD, HD+ Android Development] amaces:
Yup, that July 2nd build is (mostly) only different with regards to five DRM proprietary libraries, and should be as stable as the other ones. Just want to make sure the new blobs are not placebo before sending pull request upstream. Either way, they don't seem to cause any harm, so I'll be keeping these updated libraries in my local tree for all future builds.

Looking through your logs, I don't see many critical errors, and thankfully nothing in Ducati. For the "blip" case, the audio XRUNs are a bit worrying, and I wonder if they have anything to do with switching the output sampling rate to 48000 from 44100 (in order to fix audio input). Any issues with sound in Netflix, either during errors, or regular playback? The other errors common to both logs are related to the choice of decoders in Netflix. In the past, it tried to use the software decoder because of its strong preference for Adaptive Playback, but that was fixed, and it should definitely switch to the HW-accelerated decoder. Whether in CM or Netflix, something must have changed with that logic, because it seems to take a while for the HW fallback to happen now. Maybe that's why those initial artifacts happen? It's not a simple problem, but I understand playback is OK once it sorts itself out, correct?

P.S. I wonder if this change in frameworks/av has anything to do with the audio underruns. There will be another experimental build in a few hours.
[Nook HD, HD+ Android Development] jt61:
problems with 6/28 and 7/02 ovation builds

have successfully used the 5/30 and 6/15 builds on my nook HD+ (ovation)

tried 6/28 and experimental 7/02 builds, but both of them suffer crashes with a dialog that pops up saying:

"Unfortunately, System UI has stopped"

in both cases, reverted to 6/15 build

any ideas/suggestions? would logs of some sort be helpful?

thx...
[Nook HD, HD+ Android Development] amaces:
Xposed, by any chance? Either way, can you wipe /cache and Dalvik, wait for the optimization step, then maybe reboot once more if it still happens?
[Nook HD, HD+ Android Development] pastordl:
Ditto on mine video and sound wise. Sound never flickered. Video is much better and green lines etc much short. only once in several videos has it crashed back to the Netflix launcher.
[Nook HD, HD+ Android Development] webdroidmt:
Re: Netflix green screen and/or distorted video on start of movie

Looks like CM has changed the media_codecs_ffmpeg.xml in /system/etc on builds after 20150622 on our device. I'm thinking that this interferes with the already patched media_codecs.xml for adaptive playback that we have from @stargo. I believe this might explain why the playback starts out glitched but snaps back after some seconds, instead of just not playing at all. Which is what happened on LP 5.02 before we got this patch.

I would think that applying the @stargo patch to media_codecs_ffmpeg.xml, similar to what's already been done with media_codecs.xml, should fix the issue. As end users, we can currently fix the issue by simply editing the media_codecs_ffmpeg.xml file. See below.

Look under the <!-- ffmpeg video codecs --> heading for the h264 decoder info you need to change.

This is what the current media_codecs_ffmpeg.xml has for the h264 decoder:

<MediaCodec name="OMX.ffmpeg.h264.decoder" type="video/avc">

<Limit name="size" min="2x2" max="2048x2048" />

<Limit name="alignment" value="2x2" />

<Feature name="adaptive-playback" />

</MediaCodec>

This is what it should look like after editing ie; deleting the line shown above in red.

<MediaCodec name="OMX.ffmpeg.h264.decoder" type="video/avc">

<Limit name="size" min="2x2" max="2048x2048" />

<Limit name="alignment" value="2x2" />

</MediaCodec>

This can probably be edited directly on your device with a root explorer but I copied the file to my PC and edited it with Notepad++. I then pushed it back to /system/etc, making sure to change permissions to 644. Reboot and you're good to go.

It's a very simple and quick fix, takes a couple of minutes but hopefully, @amaces will be able to patch this up.

Because of the nice size screen, I use this device solely for media, so Netflix is important for me. :D

EDIT: Btw, maybe someone can make a zip containing the edited xml file for those that may not be comfortable doing this themselves. I would have done it but I'm having some issues with my dropbox.

Mike T
[Nook HD, HD+ Android Development] jt61:
I'm assuming this was a response to my (jt61) post about probs with 6/28 and 7/02 builds on ovation...

I don't know what Xposed is, so I'm guessing I'm not using it

tried 7/02 again with this recipe:

1. reboot into recovery

2. wipe cache

3. wipe Dalvik

4. install 7/02

5. reboot

6. see System UI crash dialog

7. repeat steps 1-3

8. reboot

9. see System UI crash dialog

10. repeat steps 1-3

11. install 6/15

12. reboot

13. no System UI crash dialog