yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] amaces:
I don't think that's it; media_codecs_ffmpeg.xml was never device-specific, but only a copy of frameworks/av/media/libstagefright/data/media_codecs_ffmpeg.xml. The only thing changed recently is that we don't have to actively copy that file, as it happens automatically now. Otherwise, stargo's patch is still in media_codecs.xml as before, but CM's logic may have been tweaked by this: http://review.cyanogenmod.org/#/c/100014.

Bottomline, we should implement eventual fixes in media_codecs.xml; did that change in media_codecs_ffmpeg.xml actually fix your issue?

Yup ;) It sounds like broken configuration in /data, which happened to many people after mid June… If you had an (untouched) backup of /data from before 06/15, you could attempt restoring that over a fully clean install. Barring that, I'm afraid you need a full wipe (including system), plus app reinstallation.
[Nook HD, HD+ Android Development] webdroidmt:
Regardless of where the eventual fixes are implemented, I thought my post was pretty clear that editing media_codecs_ffmpeg. xml fixed the issue. Why do you think I took the time to outline how to do it? ;)

Anyway, I'm on the 20150702 build and my Netflix is working perfectly with this edit. So, for those who want to get rid of the green screen/distortion issue, give it a try.

Mike T
[Nook HD, HD+ Android Development] amaces:
Thanks for the clarification. To reiterate, media_codecs_ffmpeg.xml is controlled upstream, so I cannot modify it in these builds (well, I shouldn't). [MENTION=2773890]TeutonJon78[/MENTION] & [MENTION=4122820]pastordl[/MENTION], could you implement [MENTION=4393788]webdroidmt[/MENTION]'s change (nuke line 95), and see if it fully solves your issues?
[Nook HD, HD+ Android Development] bluecopper:
Did play store break for anyone after installing 0628? I'm just having the need to install and try a new keyboard as I keep getting screen flicker when I use then keyboard normally or when I turn screen landscape. Most happens in landscape mode and causes the tablet to restart. I did notice on few occasions that I got Google play service has stopped message when the tablet restarts.
[Nook HD, HD+ Android Development] pastordl:
Made the change to the xml file, rebooted, ran Netflix, tried three separate videos, all instant on and no problems. THANKS [MENTION=4393788]webdroidmt[/MENTION] and [MENTION=4473900]amaces[/MENTION].

Edit: tried YouTube ok on 720p but video dies on 1080p. Livable but seems like fixing one thing and breaking another. Guessing H263 is for 720 and the H264 for 1080.
[Nook HD, HD+ Android Development] 9.3x72R:
Update via CWM

Remarkable! Was running cm11 latest nightly, original install via [MENTION=3654172]verygreen[/MENTION] on emmc. System/data/cache wipe, installed the 7/02 and pico gapps zips from sdcard via CWM, expecting I don't quite know what - and there it is. Restored a bunch of apps vua TiBu, now debloating. Looks very promising so far. Approx 18400 antutu.
[Nook HD, HD+ Android Development] twiztid_:
I'd suggest switching to TWRP, not that there's anything wrong with CWM.

Once you get use to it, you'll be spoiled by the touch controls and wonder how you ever got by using the volume rocker to select entries. :P TWRP also supports a few advanced, if somewhat obscure, features like being able to restore individual partitions (/Data for example), choosing the file system for your partitions (causes a full wipe of that partition! be warned), and some others that escape me. Plus it's currently developed and updated.
[Nook HD, HD+ Android Development] js290:
Using cmupdater from 20150622 to 20150704 still get:

E:Error executing updater binary in zip '@/cache/recovery/block.map'
E:Error installing zip file '@/cache/recovery/block.map'

Manual install worked fine.

20150704 still has green video playback for the 3 Netflix videos I tested.
[Nook HD, HD+ Android Development] webdroidmt:
Deleting that line should actually be transparent, since this device has had adaptive playback for h264 omitted in codecs since Feb of this year. At that time [MENTION=4243514]Hashcode[/MENTION] determined that adaptive playback would cause problems with Netflix on this device, IOW it wouldn't play. LOL

Basically, deleting it should return our device to a state prior to CM introducing the newer ffmpeg.xml codec in current builds. I say basically, because you never know what might possibly be affected. :)

With that said, I just played 5 straight YouTube vids in 1080p without issue. Granted, it wasn't extensive testing ie; a minute or two on four of them. But I did let one play 'til the end (9 min 37 sec) and it was fine. Don't know if this makes a difference but because I use this strictly for video and music, ( Netflix, HBO GO, YouTube, MX Player) I keep hw overlays permanently disabled.

Mike T
[Nook HD, HD+ Android Development] jt61:
can you (or anyone) point me to the best instructions on how to make that switch? this is for HD+ (ovation)

thx...

---------- Post added at 12:40 PM ---------- Previous post was at 12:31 PM ----------

ok, I did a full wipe and re-install of the 7/02 build and gapps-5.1-arm-2015-05-03-16-32-37

booted up fine, and went through the wifi setup and Google login, but it seems to be hung in re-installation of apps - left it going overnight, and Play -> My apps show the list of apps to be installed with all the progress bars sweeping left to right and one showing "Installing"

suggestions?
[Nook HD, HD+ Android Development] jt61:
never mind - wiped and re-installed again and all went fine - all apps re-installed as expected

haven't tested everything, but seems extremely good - very responsive, VLC works, etc.
[Nook HD, HD+ Android Development] pastordl:
Read webdroidmt's comment and it got me thinking, cleared YouTube data, started YouTube, signed in and it works great. Tried several videos with no problems. So the. Xml edit works fine for both. I didn't Disable HW overlays either. [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] twiztid_:
Grab the TWRP image from the Hummingbird (HD) or Ovation (HD+) folder here, and copy it to your device.

Then install Flashify from the Play store, and run it. On the main screen, select Recovery image, browse to your TWRP file, and go.

You should now have TWRP as your recovery.

When I'm doing an upgrade (between new versions of the same ROM), I wipe /System, /Cache, and Dalvik, then install the ROM + gApps (this MAY not be needed with a persistant gApps, but I haven't tested yet).

But when I change ROMs, or need a bigger wipe (because something went wrong), I wipe /Data as well which will clear your APPS but leave your personal files (files in /SDCard). Be warned however, changing the /Data filesystem (EXT4/F2FS) will wipe ALL of the data partition including your personal files. That one tripped me up a few times.

I'm not sure what the cause of the issue is, but I've had the same thing (on a smaller scale) happen before. Cancel the download(s), close Play Store, clearing Play Store app data, and trying again has worked for me.
[Nook HD, HD+ Android Development] js290:
Just tried to edit on the 20150704 build, but /system is mounted ro. Is your /system mounted rw?
[Nook HD, HD+ Android Development] amaces:
So, as you noticed, I couldn't make sense of frameworks/av/media/libstagefright/data/media_codecs_ffmpeg.xml being changed with respect to adaptive playback. That's the file we used to copy before this cleanup. Well, looks like the FFmpeg XML lives in external/stagefright-plugins/data now, and the unwanted feature flags were added in http://review.cyanogenmod.org/101788.

As you mentioned, our HW decoder doesn't really do adaptive playback like Netflix wants, but works fine otherwise. One option is to extend stargo's quick fix for media_codecs_google_video.xml by dumping the whole media_codecs_ffmpeg.xml (minus adaptive-playback flags) rather than including the CM copy, maintained upstream. There must be a better way though; it wasn't pretty before (our XML was already slightly out of sync with Google's copy), it'd be downright ugly now.

I don't know enough about XML grammar and precedence, but let's try another approach; [MENTION=4122820]pastordl[/MENTION], and anyone else willing to change /system files, can you replace media_codecs.xml with the one in the attached ZIP? The other files (media_codecs_ffmpeg.xml & media_codecs_google_video.xml) should be reverted to their original versions, also included in the attachment. To clarify, this is not for flashing in recovery; just repplace the files in /system/etc, reboot, and test Netflix.

P.S. Whether enabled or disabled, HW overlays should not interfere with video playback.
[Nook HD, HD+ Android Development] TeutonJon78:
Commenting out that line fixed Netflix for me. No other changes., HW overlays always enabled. So, it seems that something around those few CM changes seems to be what hosed up Netflix for sure.

Sorry, I probably won't be able to play with the other changes, as it isn't my tablet and the owner really needs it to working without too much delay.
[Nook HD, HD+ Android Development] Zippy Dufus:
Re: Hangouts Dialer Fixed

I just built 07/05 with your g-3.0 kernel repo and can confirm that Hangouts Dialer works.

Thank you!
[Nook HD, HD+ Android Development] pastordl:
Tried the three .xml video files neither netflix nor youtube would play videos. Youtube eventually came up with message "can't play video at this time". Netflix just kept showing the circling arrow. Reverted to the two original and one modified both running. This was on 7/2 exp. Am in process of updating to 7/4. Will edit this post with results. [MENTION=4473900]amaces[/MENTION]

Edit: 7/4 same problem as 7/2. Copied modified ffmpeg.xml runs fine. Will keep the webdroidmt's moded file just in case for now. Thanks for all your hard work.
[Nook HD, HD+ Android Development] amaces:
Thanks for confirming, [MENTION=4122820]pastordl[/MENTION]; after more reading, I realized that duplicates are really bad in XML, and that attempt at overriding previously included variables yields a completely broken media_codecs.xml. Eh, back to learning; will probably use the brute force approach we have for Google decoders, at least till something better comes up.

So, no reason to break your configuration again; just use [MENTION=4393788]webdroidmt[/MENTION]'s approach till next set of builds.
[Nook HD, HD+ Android Development] webdroidmt:
Just tried the codecs you uploaded on the 20150704 build and Netflix just hangs on the loading screen. Btw, I read through the media_codecs and it didn't look all that ugly. LOL

I just wish I knew more about deciphering xml, so I could be of more help.

Mike T

---------- Post added at 06:13 PM ---------- Previous post was at 06:07 PM ----------

I know you're a tenacious guy, I'm confident that you'll eventually figure it out. :) I'll clue you in if I discover something useful.

Thanks,

Mike T

---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------

I'm on the 20140704 build, it produced the same results as 20150702.

Mike T
[Nook HD, HD+ Android Development] jt61:
cool - however, Flashify says I don't have root access, even though I did the "hit build number 7 times to turn on developer options" thing, and root is turned on for apps and ADB

is there something else I need to do?
[Nook HD, HD+ Android Development] twiztid_:
I don't know if it's a bug, or "safety feature", but disable root and then set it back to Apps or Apps/ADB. You may need to restart, but I don't think so.
[Nook HD, HD+ Android Development] jt61:
20150702 ovation report

quick report on 20150702 experimental build on ovation after full wipe and install

* seems more responsive than other recent builds

* VLC works fine on 720p mp4

* have experienced several (2-3) spontaneous reboots, each of which triggered a full "optimizing apps" cycle (rebooting manually doesn't)

* seems to require pressing power button twice to wake up

* still experiencing the "battery appears to drop suddenly from 70-80% to 1%, but when plugged back in, jumps right back to where it was" issue

---------- Post added at 04:23 AM ---------- Previous post was at 04:17 AM ----------

wow - that's somewhat less than obvious

thx - that worked - didn't have to reboot

and you're right, TWRP is nice!
[Nook HD, HD+ Android Development] twiztid_:
You may want to try the instructions in the last section here to reset your battery statistics.

Yup, really weird, and mildly annoying... but it only has to be done once (per complete wipe), and something I end up getting out of the way early on (when I'm turning on Advanced Reboot), so I can understand it not being a top priority. Glad you got it working, enjoy all your fancy recovery touching! :D
[Nook HD, HD+ Android Development] windoge89:
Not quite on topic, but how do I install twrp on a nook HD with cwm already on it? Do I just flash it over cwm?
[Nook HD, HD+ Android Development] tebra:
CWM can't flash .img files. You have to install flashify to do that.
[Nook HD, HD+ Android Development] 9.3x72R:
TWRP, charging

Per [MENTION=5720705]twiztid_[/MENTION] I replaced CWM 6.0.4.6 with TWRP 2.8.7 using flashify from the running ROM, and confirm this works a treat. Use the "Nook" button as usual to invoke boot to recovery by means of switch control. I have just noticed (and sorry if this is old news, I am fairly new to this device but could not find it as having been discussed elsewhere) that the HD+ does not (or at least, does not any longer) charge when powered off? Wouldn't even bother to mention this except I only have noticed since the upgrade. Charges fine when booted to recovery. This is associated with battery recalibration mentioned earlier in the thread.
[Nook HD, HD+ Android Development] belfastraven:
7/06 hummingbird

is running fine on my HD. i normally use it mostly for reading/reference but have tried netflix , youtube, and twc tv app and they are all running well. I flashed using flashify with the latest test TWRP 2.8.7.0, btw. Thanks again, amaces, for the HD builds.
[Nook HD, HD+ Android Development] amaces:
Yep, the blunt approach here was used to fix Netflix; I didn't test it directly, so thanks for the confirmation.
[Nook HD, HD+ Android Development] webdroidmt:
Can also confirm Netflix and all my other video stuff working properly on 20150706 ovation build. Nice work!

Mike T
[Nook HD, HD+ Android Development] pastordl:
Great work [MENTION=4473900]amaces[/MENTION]. 7/6 Works and runs great, Netflix and Youtube with no hiccups. Glad to be at least a little help.
[Nook HD, HD+ Android Development] nimaim:
Thanks for all the work guys ... also confirm YouTube and Netflix working well.
[Nook HD, HD+ Android Development] TBueno:
Moved from 0530 to 0706-ovation. Haven't really noticed any difference in performance, though task switcher might be a little snappier. It's good to have telephony back, and, guess what?, artifacts are gone from Chrome. :D

Setting DPI to 260 brings some noticeable improvement for me, that's one good tip.

With audio capture trouble out of the way, the only remaining serious problem is flickering, since screen casting is more of a feature request.

Thank you AMaces once more.
[Nook HD, HD+ Android Development] dk1keith:
Everything running great here on 07/06 ovation..

awesome work
[Nook HD, HD+ Android Development] 9.3x72R:
BT, OTG

7/06 build: external device notes:

Bluetooth: I have a cheap BT mouse (Tecknet BM306) that is recognized as "Bluetooth 3.0 mouse" but generates the message "Pairing rejected by Bluetooth 3.0 mouse". Mouse pairs fine with phone (4.4.4, xt1080m) and laptop (RH6.6, lenovo). Verbatim 97537 folding keyboard that pairs, including PIN entry, but is not recognized as an input device (keyboard also pairs with my phone and functions, will not reliably be discovered by nor pair with laptop). Bluetooth tethering to the phone seems to work, although the connection stops occasionally requiring a re-pair. I'll attempt to investigate further, just reporting some observations here.

OTG: Have not gotten this to work at all yet. Using [MENTION=3654172]verygreen[/MENTION] host switching app (his UI design is a thing of beauty, IMO), a variety of cables and devices. As yet no joy.
[Nook HD, HD+ Android Development] amaces:
Official TWRP: Second Batch

Another batch of official TWRP images are in experimental; I tested ovation, but would like to make sure hummingbird is OK too. Once I get a couple of confirmations, we should be good to go on twrp.me.

Yeah, I think Chrome was overly sensitive to the low-ram flags, which I reverted here for now.

[MENTION=4563594]panchokoster[/MENTION] might know more about this; at least I don't recall anyone else mentioning USB OTG (see http://xdaforums.com/showpost.php?p=61617524&postcount=447).
[Nook HD, HD+ Android Development] games906:
I got a quick question- why does my tablet die faster when its powered all the way down than it does when its on but the screen is off? If I leave it on with the screen off (battery saver on) it'll last for days on end. But if I turn it off one night it'll go down at least 50% when I turn it back on
[Nook HD, HD+ Android Development] TeutonJon78:
That sounds...not possible. When you turn it back on does it go back through the whole boot sequence? I know some people have had problems where when they shut the tablet down it turns itself back on, which could burn lots of battery.

I've also had that problem in phones when the battery starts to swell and the device won't stay off.
[Nook HD, HD+ Android Development] belfastraven:
The hummingbird TWRP in experimental looks like the last test version, right? i.e. it doesn't have your nice interface. Assuming that is the case. It is working well for me. Occasionally I have to double tap or hold an icon a bit longer, but normally, the touch is very responsive. Also, I notice when I power down from recovery, the machine actually stays off, which is new for me.
[Nook HD, HD+ Android Development] twiztid_:
[MENTION=4473900]amaces[/MENTION] Could you check that the theme engine files are up to date, and there that aren't some fixes not merged in yet?

Tried a few themes, all of them having an issue: popup windows, like when long pressing on links, have black text on black background. A few skins have mentioned this is a CM12 issue, and needs to have the ROM updated with the updated/fixed engine.

The issue persists even after uninstalling the skin and going back to the default. And I think it might be related to another skin issue, where the status and navigation bars are solid black after I used a skin, and will not go back to semi transparent gradient. Actually, it seems it's an issue with Nova Launcher... The Black text on black(ish) background in Browser seems to be default though. Oh well.

Thanks a million :)
[Nook HD, HD+ Android Development] pastordl:
Tried the "official" TWRP 2.8.7.0 Ovation, works okay but some double taps required. Still like the 2.8.7 custom theme better. Reverted to it. Like the custom button at the bottom to return directly home after backup.
[Nook HD, HD+ Android Development] games906:
No because I'm able to turn it back on when I shut it down. I never heard of 40% being burned in a turn off/on.
[Nook HD, HD+ Android Development] TeutonJon78:
Of, for sure (unless the battery has REALLY gone to hell). I was thinking more that you turn it off, and at some point it turned it back on. I've seen other old batteries that read with a good level, then after a reboot read way lower (especially after going into recovery). Does the battery graph show any skips or too fast drops if you leave it on?
[Nook HD, HD+ Android Development] games906:
It's a little wierd- if I were to charge it to a 100%, WiFi and Bluetooth off, battery saver on, it would probably last for a month.
[Nook HD, HD+ Android Development] TeutonJon78:
Large drops like that often relate to battery health (on one of my old batteries it would go slowly from 100 to like 60, then suddenly be at 15). Did you get the tablet at launch and/or (dis)charge it often since you got it? I'm not really sure of any good way to check battery health other than a few apps that show statistics, but those are really that informative over than temp and charge.

If you charge it up to full, and then power it off, does it still start up with a huge drop?
[Nook HD, HD+ Android Development] twiztid_:
To easily see battery stats, go Settings -> Performance -> swipe from left edge in (or enable tabbed view) -> Battery. It will tell you the mV, %age, and temp.

If your battery is dropping quickly, or the "bottom" half gets used VERY quickly, read 2 or so pages back for my instructions on the battery stats app. It seems to be an issue when you update the ROM, that some battery data isn't fully wiped so you get incorrect info.
[Nook HD, HD+ Android Development] granny smith:
[MENTION=5619946]games906[/MENTION] - I had to replace the battery in my HD. I would charge it 100% and then the battery level would drain normally from about 100 - 70% and then it would all of a sudden drop to 40%. If I reset my HD, sometimes the battery level would stay the same at 40% or actually go back up, but it would inevitably drop real fast. My battery also started to bulge at the end of its life. Changing the battery is not hard, but (at least on the HD) the little clip that holds the battery connector is VERY fragile. I broke the clip just trying to take out the old battery! And I thought I was being careful. Anyway, buy a B&N brand battery off of ebay if you can because the connector on their battery is ever so slightly different from third party batteries and will still clip and hold into the a broken battery connector - along with some hot glue to keep it in place : ) I hope you don't have to replace your battery, but if you do I hope this information helps.
[Nook HD, HD+ Android Development] ieatabiscuit:
I had the battery on mine do this also. After looking into replacing it, I found it to be difficult to find a replacement for ovation. I busted out my unopened ovation (got 3 for dirt cheap one day), and upon booting to my SD card, the new tablet started acting exactly the same way. After reinstalling EVERYTHING (yes, recovery, and all) from scratch on the first ovation with a shiny new SD card, the issue has been gone, I am using the first one now to type this, battery runs like new! It runs along with the format not clearing battery data, and the information getting conflicted. Try a NEW SD card, and start from bare metal. I'd bet this will fix more issues than you may think. Especially since SD cards are not known for having the best life span/reliability. Starting from bare metal is important though. You don't know what can be screwed up by flashing with a potentially dying media, just using it with even a new device can make strange terrible things happen.
[Nook HD, HD+ Android Development] TBueno:
I can't seem to find performance settings for 0706-ovation... am I missing something?
[Nook HD, HD+ Android Development] twiztid_:
Apparently not :/ It seems it was either removed from 5.x or was a custom menu on my phone's ROM (Carbon). My mistake.
[Nook HD, HD+ Android Development] TeutonJon78:
That seems most likely -- I've never seen any AOSP-based ROM has any swiping actions to the side in settings.
[Nook HD, HD+ Android Development] ajislav:
Moved (or removed)

http://review.cyanogenmod.org/#/c/101804/