yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] mattyyey:
I was formatting them with f2fs after the first couple of failure. I know that install don't take 3 hrs m8 lol I just went out n forgot about it. Normally I'd wait no more than a 10 mins.

I'm glad the md5sums are good. However the reason I asked for them, is because I had 2 versions of kernel-ovation that were different sizes. That was due to wifi dropping on my tablet as I moved the router when cleaning tho.

I was suprised that it was the sdcard... as said not used alot, however in retrospect I do have folder mount with Spotify mapped to external. Which is one of the main uses of my tablet. Ive had no transfer faults or it randomly mounting... seemed fine other than not installig... I find it even more crazy that my years old gold card worked lmfao.

Anyway thanks everyone for your help. So far 0717 n experimental kernel seems very fluid and responsive, not an hw overlay bug in sight. Hehe hehe thanks again
[Nook HD, HD+ Android Development] bluecopper:
So I flashed the rom doing a wipe of dal, cache and system. Left it optimizing apps and when I came back some time after the tablet had restarted and was stuck at the mascot. Powered of and turned on, but it restarted again shorty after it got home screen. Did the fash again this time with gapps and it went thru normally.

Did the 2nd wipe fix something, or did gapps? I have flashed rooms on my phone before without gapps with no such problem.
[Nook HD, HD+ Android Development] kliu888:
Offline charging & Magnetic cover issues

This ROM works much better than CM 11. Huge thanks to dev. I have two questions:

1) Is offline charging supported? It's not working for me.

2) Screen lock doesn't seem to work with magnetic cover. I have to unlock it twice - when I open the cover and enter pin to unlock, it will immediately turn screen off & lock itself again. I have to turn it back on & unlock. The 2nd unlock works. This doesn't happen every time but frequently enough to be frustrating. If I don't use any lock then magnetic cover works fine. Or, if I don't use magnetic cover then unlock works fine.

Is anyone having these issues?

Thank you very much.
[Nook HD, HD+ Android Development] twiztid_:
Both of those are long standing CyanogenMod issues
[Nook HD, HD+ Android Development] kliu888:
I see. Hope they get fixed eventually. For now, I am disabling system lock & use an app from play store to lock the tablet. Not the best solution but works.

Thank you.
[Nook HD, HD+ Android Development] ieatabiscuit:
I haven't seen this happen on mine, and I flash the poor thing for sport. It is possible that the first time you just didn't hold your mouth right. I usually give mine a cheesy grin when flashing, works well for me :D Seriously though, it sounds like it could just be some random thing. Especially since it didn't happen after the next wipe.
[Nook HD, HD+ Android Development] bluecopper:
lol ok i need to remember the smile. Been working on project for school so haven't done much testing. One problem i will test is the one i noticed before i flashed. I was having issues using popcorn time. I got an error trying to watch an episode of Beauty and the Beast, something about enabling HW Accelaration. Then it would attempt to play the video but couldnt. Looked all choppy and pixelated
[Nook HD, HD+ Android Development] js290:
Hard shutdown while watching Netflix

With battery greater than 75%, I'm getting hard shutdowns when using Netflix. This has happened on cm11 as well as the last couple of cm12.1 builds, most recently the 201507016-ovation build. I'm attaching a couple of adb bugreports and logcats. The device powers right back up without problems. Seems like an issue with Netflix.

In the process of downloading 20150717-ovation now.
[Nook HD, HD+ Android Development] windoge89:
Could anyone tell me what I have to do to install twrp over my existing CWM installation? Is it worth it?
[Nook HD, HD+ Android Development] amaces:
The 07/20 builds contain the necessary overlay changes to un-hide that setting; beyond that, I don't know whether it'll still solve your other problem.
[Nook HD, HD+ Android Development] ieatabiscuit:
Flashify is what I used, since then I have not missed cwm a bit. Mostly because of the touchscreen feature, flashing more than one zip at a time, and you can update twrp within twrp once you download the update. I would have to say it is worth it, and you would enjoy the more in depth control over your installation with it.
[Nook HD, HD+ Android Development] Shermanballz:
Wow, thanks dude! I'm gonna check it out right now!

EDIT: Totally fixed the problem! You rock!
[Nook HD, HD+ Android Development] BEZMan:
I am having exactly the same problem. It seems like the unit all of a sudden goes to 1% battery and shutdown immediately. It is especially obvious whne using Netflix or YouTube.

I am going to try the 10.2.1 (Stable) on that forum to see if this is an issue with my Nook or a software issue. Stock ROM seems fine though.

If anybody has any clue what is happening that'd be awesome!

Thanks
[Nook HD, HD+ Android Development] extrem0:
It looks like you both have damaged battery. Try reducing brightness and see if it'll still shutdown or try watching while charging.

I remember similar behavior in HTC sensation. Many users reported that phone would shutdown when taking pictures with led Flash on. Replacing battery fixed it.
[Nook HD, HD+ Android Development] jaydeedid:
HDMI muted

I have the same issues. My tablet is my only source for movies and HDMI is very important. Aside from having no sound with HDMI, I'm loving this ROM.
[Nook HD, HD+ Android Development] BEZMan:
That may be unfortunately the case, so I have decided to return it. The guy I bought it from was nice enough to take it back. I am buying another one on Craigslist and we'll see!

Thanks
[Nook HD, HD+ Android Development] mattyyey:
hay just wanted to report back, My tablets all setup, themed and all my apps setup. Using the ovation 0720 build now and the experimental kernel. Its smooth, not got as clogged up with all my apps (did a bit on much older versions without Greenify). Oh and good news, xposed for 5.1 works well with this too. Thanks [MENTION=6326205]ieatabiscuit[/MENTION] for your help and extra big thanks to [MENTION=4473900]amaces[/MENTION] for this awesome rom and all the work you've put into it. (to mention just a few)
[Nook HD, HD+ Android Development] ieatabiscuit:
I'm just trying to not be a troll, and help when I can. If I helped you, you're welcome. Just adding my two cents when I can.
[Nook HD, HD+ Android Development] enochpc:
First I want to give amaces big thanks for his latest build, much more usable on my ovation, makes me think I can go a bit longer before I replace it. Lag is almost gone and runs great. Looking for some help tho. I have gone through the thread and all the suggestions, but still having issues with root. I have set root to apps only in developer options, I have flashed supersu, I have installed busybox from the play store. I have installed supersu from the play store trying to get it to work that way. I have turned on shell in developer options, turned off and on adb, tons of reboots. I tried setting supersu to ignore cm settings about root. Nothing works. Does anyone have a suggestion on what I can try to get work? Thanks in advance.
[Nook HD, HD+ Android Development] amaces:
Quick update about block schedulers: after testing FIOPS, ROW, BFQ, and SIO, it really seems that read-over-write is the best strategy for our zRAM, plus old eMMC tech. So ROW will remain the default, as it's been for the past couple of builds. It may be that local/per subsystem schedulers could work better (e.g., FIOPS for MUSB/OTG only), but that's for future testing.

Based on your logs, you installed Netflix from the Amazon app store, correct? Netflix is one of the things I don't use, but it's possible that the interaction with the Amazon installer plumbing causes issues, or that Amazon serves an outdated version. Maybe the Play Store version works better, or you could manually install it from here: http://www.apkmirror.com/apk/netflix-inc/netflix/.

Like [MENTION=4482904]extrem0[/MENTION] said, I'm hoping it was the battery hardware, although I'm confused about stock behaving differently. Did you reinstall stock and check again? The chipset heats up quite a bit while flashing ROMs, and some battery controllers may give erroneous readings with extreme conditions or internal chemistries.

HDMI audio has been on my mind, and it did come up while we were fixing the audio HAL for Hangouts Dialer. I have a couple of ideas, but you'll have to do all the testing as I don't have the adaptor cable, unfortunately. It'll happen over the next few days.

Can you expand on the exact behavior when you attempt to get root access, and before reboots? Since it should be much less complicated, I'd go back to basics. First, you don't need another busybox installation with CM ROMs, and although I prefer SuperSU, the builtin root binaries are good enough for testing. So, uninstall SuperSU, your other busybox distribution, whatever else you threw in there, then format /system only (mainly to get rid of SuperSU's backup scripts, etc), and reinstall ROM, GApps, Xposed maybe, but nothing else. Finally, turn on builtin root access, and test your apps. If everything goes well, reinstall SuperSU, should you like that root manager better.
[Nook HD, HD+ Android Development] enochpc:
When I get home I will try a reinstall per your instructions. When I started I worked my way up. First I set the developer options to app only right after install, when that didn't work I tried flashing supersu from recovery and spiraled out from there. I only have a few non-system apps installed, titanium backup was the first thing I tried root with, after messing with it for awhile I added chrome and a few other non-root apps just so I could use the thing for what I usual use it for. I will strip it back to nothing and try that and see if I can figure out what I am missing, I am sure it's something simple. Thanks for your help.
[Nook HD, HD+ Android Development] BEZMan:
I did try the stock again and it dies on me so definitely a hardware issue I think - the new unit I have seems solid!

Thanks
[Nook HD, HD+ Android Development] twiztid_:
In Developer Options, set Root access to Disabled, then change it to Apps only or Apps and ADB.

You have to set it to Disabled first for whatever reason, then set it to what you want.
[Nook HD, HD+ Android Development] pastordl:
From Amaces

I've got an HDMI adapter. Will watch for update and give it a try.
[Nook HD, HD+ Android Development] lostnick:
Hi amaces

Please update TIInit_7.6.15.bts in Your bulds to current versiion (from https://github.com/TheMuppets/propr...proprietary/vendor/firmware/TIInit_7.6.15.bts or https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_7.6.15.bts)

Without this firmware BLE does not work at ovation.
[Nook HD, HD+ Android Development] asakurato:
Wow, that performance in 20/07 build :good: Youtube is fast again, zero crashes and overall speed improved too, i think it's even better that before. Thanks a lot!

P.S. What is twrp-2.8.7.X-ovation in ovation folder? Is it just flashable zip version of img file?
[Nook HD, HD+ Android Development] amaces:
Ovation test build in experimental with one possible HDMI audio fix; [MENTION=4048645]sasmith-129[/MENTION] & [MENTION=6838526]jaydeedid[/MENTION], I'm not sure if you're on HD+ too, but hummingbird will finish in a couple of hours.

Why, thank you for asking… Did you stop to maybe check if it's already on your device, say in /system/etc/firmware/? Also, AIDA64 says that Bluetooth LE is supported on these devices…

It's an up-to-date recovery ZIP, which basically, keeps up with TWRP developments, new theme, my kernel changes, etc. I'm slowly phasing out raw images, since these ZIPs (i.e., kernel & recovery) have device asserts now, to stop people from flashing the wrong flavor again ;) Everyone else can simply extract the boot or recovery images therein, should they need them.
[Nook HD, HD+ Android Development] enochpc:
I will give this a shot before I wipe everything. I know I didn't do this so maybe this is the missing step.
[Nook HD, HD+ Android Development] twiztid_:
You wont need to do it between updates, as long as you don't wipe /data.

But when you do wipe /data, you lose all your ROM settings, including the ones for root.
[Nook HD, HD+ Android Development] jaydeedid:
It's honestly the only downside I've found to this ROM, so a big kudos for your efforts. I'll check back in a few days. Thanks again.
[Nook HD, HD+ Android Development] amaces:
You can check now ;) See #645.
[Nook HD, HD+ Android Development] js290:
Weird. I installed via Play Store. Don't have Amazon installed. I'll buy the other theory about a bad battery. I'll connect the power cable and see how it behaves. Thanks again for your feedback.
[Nook HD, HD+ Android Development] Silly_String:
Thank You Amaces!!

I have been pretty annoyed lately with this tablet and problems I was having with other time but it has been running smooth and fast all thanks to your effort. I actually ordered another tablet but decided to return it and keep using my HD+.
[Nook HD, HD+ Android Development] lostnick:
TIInit_7.6.15.bts exist in /system/etc/firmware/, BLE enabled, but does not really work with included version.

All needed modifications described in https://jira.cyanogenmod.org/browse/CYAN-2494 and Hashcode push them upstream, but only to cm-11 branch.

See https://github.com/TheMuppets/proprietary_vendor_bn/commit/9e9386abaa73d33d619a52295b51ec1e685332e1

PS. Tested with TI SensorTag.

Work with verygreen cm-11 SD build with suggested modifications and with Your cm-12.1 when I manually replace /system/etc/firmware/TIInit_7.6.15.bts with suggested version.

PPS. Maybe will be better to push this changes into upstream cyanogenmod repo, but I don't know how to do it.
[Nook HD, HD+ Android Development] amaces:
So, in Archer's words, phrasing ;) Had you specifically emphasized that the CM11 blob is more up-to-date than CM12.0/1, it would've been included already, in yesterday's builds. It's done now in my local vendor repo and fork, and I submitted a pull request for the cm-12.1 branch.

Just for clarification, TheMuppets is not upstream CM, and they do things in the standard GitHub way (i.e., pull requests). Either way, you've already fixed it in you current installation, and the next set of builds will have the BLE firmware incorporated.
[Nook HD, HD+ Android Development] Velines:
Is there any way to enable LagFix or fstrim with this build?
[Nook HD, HD+ Android Development] enochpc:
Just a follow up, had to do a clean wipe flash and use the trick of setting root to disabled and then back to apps, but I now have working root. Thanks everyone for all your help.
[Nook HD, HD+ Android Development] jaydeedid:
I tested the 7/21 build today and my HDMI audio works. The screen is still inverted but that's not a problem for me. Thank you. :good:
[Nook HD, HD+ Android Development] pastordl:
Tried [MENTION=4048645]sasmith-129[/MENTION] volume settings still no sound. Again in any video app the sound bar drops to 0 and stays there. If I am not in a video app the volume bar is normal and adjustable. Not going to cry over it but was hoping.
[Nook HD, HD+ Android Development] N0he:
I've had the same problem with battery jumping to 1% a couple of months before, but that problem just disappeared after flashing an update. Don't know which build it was, and why the problem disappeared, but it might not be a hardware problem? Also, I don't use Netflix.
[Nook HD, HD+ Android Development] amaces:
The kernel has the FITRIM ioctl, but you're probably trying to use it on a filesystem that doesn't support it… Check fstrim /system (ext4), just for kicks (obviously, not needed there). F2FS TRIM support was only added in K3.18 I think, and our backport covers features up to 3.16/3.17… Still, it shouldn't make much difference since both /data and /cache have discard and background_gc=on mount options. But yeah, converting /data & /cache back to ext4 will fix LagFix ;)

I'm gonna chalk it up as solved, at least the audio issue. For the video inversion, I need to look into a different HAL, and that may happen eventually.

Your issue now may be the other HDMI endpoint. Sound bar dropping to zero implies some sort of audio signaling over the HDMI connection, which is a different issue than the AudioFlinger stuff we just fixed.

Yep, that's an issue with the decoding process before the raw audio stream is sent over HDMI. It may be that the software decoders don't have good Dolby AC-3 support, or that software decoding of those stream can't keep up, producing audio underruns.
[Nook HD, HD+ Android Development] Velines:
Right, it wasn't ext4, thanks for the heads up. Now LagFix complains that it needs a PIC binary, but I'll rely on the mount options. Of course, in fstrim works in terminal. Thanks again :)
[Nook HD, HD+ Android Development] ieatabiscuit:
I keep saying it: Dem SD cards be runnin' crazy! Sometimes a good reformat and reflash can fix the issue, other times it's that SD card giving up the ghost. They get used quite a bit in the ROM flashing business, and just like an SSD, the smaller ones have less variety of area to write to, and thus degrade faster. The quality of the card can do it too, I also try to have the class of the card be at minimum class 4, though most of mine are class 10, or better. It makes all kinds of weird things happen when it's going bad. Anything from battery reading being off, to not booting while the card is in the nook, to more common things like read/write errors (which can do anything from corrupt a flashed ROM to causing all kinds of lag, long boot times, or worse). Anyway, just wanted to restate my case, as it has saved some people some issues, and I nearly scrapped a perfectly good ovation due to this when I didn't know any better.
[Nook HD, HD+ Android Development] excalibar001:
Thank you [MENTION=4473900]amaces[/MENTION] for your excellent work on this tablet and sharing it with us. Your solution to audio over HDMI, is it native to this tablet or applicable across cm12.1?

I am using cm12.1 on my other Samsung tablet and it has the same issues with audio over HDMI. I wanted to know if I could share your solution with the developers over the Note 10.1 thread?
[Nook HD, HD+ Android Development] amaces:
The issue was not so much device-specific, but it had to do with the HAL that we're using. If your Samsung tablet is using a HAL comparable to what we have in https://github.com/airend/android_device_bn_common/tree/cm-12/audio, then look for something like AUDIO_DEVICE_API_VERSION_*; it may be that you have to restrict it to a lower version, to prevent AudioFlinger from using features that don't work.
[Nook HD, HD+ Android Development] neonleon29:
It's been awhile since I visited this thread. Has screen casting been fixed? If not, is it even possible? It works on the Kit Kat Rom I'm using but I think I read somewhere that it might not be compatible with Lollipop.
[Nook HD, HD+ Android Development] asakurato:
And now I'm having yet another problem with playing videos :( When I try to stream with MX Player, my nook just hangs, only hard reboot helps :(

Edit: I think I fixed hanging with Selinix mode changer app, as I rwmembwred Ib had same problem with my phone.
[Nook HD, HD+ Android Development] amaces:
The video component is still MIA, but audio works. It's a tough problem, but we haven't given up.

It's already under SELinux Permissive… Anyway, you know how it works; a vague statement, with no logs or concrete information, will seldom be fixed…
[Nook HD, HD+ Android Development] asakurato:
I mean I switched to enforcing and hanging stopped. Also I havent made any logs because I wanted to see if changing mode would help. I shoulnt posted that here I guess :D
[Nook HD, HD+ Android Development] pastordl:
7/23 running fine

Not sure what changes were made but everything seems to be fine.

Back to the HDMI output, I understand my no audio problem is a different issue, so I took a log cat and have attached it below. [MENTION=4473900]amaces[/MENTION] if you or some other tech wunderkind could check it out to try to figure out the problem. I did plug and unplug the HDMI twice. If anyone does try thanks in advance.
[Nook HD, HD+ Android Development] andtron:
I used the default, which is Permissive, and I never have streaming issues with the MX Player.
[Nook HD, HD+ Android Development] williamlaw:
where to download latest rom ?

thanks
[Nook HD, HD+ Android Development] twiztid_:
Read the first page
[Nook HD, HD+ Android Development] amaces:
SELinux Enforcing

Starting with the builds today, Enforcing is default, and the initial WLAN calibration (in fix-mac.sh) has been changed to avoid remounting/writing to /system. The new location for the NVS BIN is /rom/devconf/wl1271-nvs.bin, symlinked to /system/etc/firmware/ti-connectivity/.

Now, the changes that I made to sepolicy, init.rc scripts, etc, are invasive enough that I'm not sure they'll like them upstream, but running under SELinux Enforcing was the last stumbling block before Hashcode was going to turn on official nightlies. Overall, there are advantages to the /rom location beyond not having to edit /system; the initial calibration should happen once per devices, not every time you flash a new ZIP, and it won't conflict with other ROMs, should you decide to switch them.

The only notable change with the 07/23 builds was the new BLE firmware that [MENTION=476189]lostnick[/MENTION] pointed out.

Anyway, I will keep your volume bar problem in mind; it may be CEC miscommunication between endpoints, due to conflicting implementations.
[Nook HD, HD+ Android Development] belfastraven:
7/26 running fine on Hummingbird for all of my usual apps. Thanks again.
[Nook HD, HD+ Android Development] amaces:
It says Enforcing in Settings, right? Also, Wi-Fi, BT, all good?
[Nook HD, HD+ Android Development] belfastraven:
Yup--SELinux Enforcing, Wi-Fi fine. I'm trying to figure out how to test Blue-tooth pairing. HD definitely sees my computer, but doesn't seem to want to pair. However, this is a new motherboard and I've never tried to pair anything with it before, and it's running Windows 10, etc. etc. So it might take me a little while to figure this out. :) I'll let you know if there's a problem.

OK -- have got nook hd paired to phone (verizon droid maxx) and pc.
[Nook HD, HD+ Android Development] SteveCoops:
Hi all,

Anyone seen on their HD the screen flickering? The screen flashes off every second or so.... and the brightness controls don't work?

Cheers,

Steve
[Nook HD, HD+ Android Development] belfastraven:
Many of our HDS seem to flash when installing a new rom, the normal fix is to turn-off the screen and turn it back on. Have you tried that?
[Nook HD, HD+ Android Development] 3c57x9:
Dirty flashed 7/26 on ovation, it's working really well. It seems smoother and quicker than 7/23. Thank you for your hard work amaces.
[Nook HD, HD+ Android Development] js290:
I just updated to 20150726 as well. Auto update still fails in TWRP complaining about the [MENTION=338331]block[/MENTION].map. Also, I don't seem to be able to boot into recovery with 20150726. I've tried with both adb reboot recovery as well as the power button reboot menu. Otherwise, it seems to work well as did 20150723.
[Nook HD, HD+ Android Development] andtron:
Hi js,

You could try pressing the n-power-vol (r) buttons (I.e 3 buttons at the same time) for at least 12 seconds, then it will boot into the recovery.
[Nook HD, HD+ Android Development] js290:
Yep, that works, but you should only have to perform that on power up. The reboot into recovery via adb or menu should also work as well. Thanks for the tip, BTW.
[Nook HD, HD+ Android Development] twiztid_:
Same here.

Question, did you restore apps/settings from Google? I did and I'm wondering if it's possible an old setting is causing it.
[Nook HD, HD+ Android Development] tebra:
Hi all,

Thank you Amaces for the 7/26 build. Installed on my hummingbird. Confirm selinux enforcing and WiFi working. Also confirm no reboot to recovery from power menu button