yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] mhunt13:
As for me, just habit to turn it off when not using it for a few hours, or turn it off at night. I re-charge my devices when they need it, not a fan of routinely plugging things in to charge all night. On the HD+, I've gotten used to just holding the power button for a few seconds until it shuts down. Not a big issue.

I'd be curious why yours boots when you do plug it in, my HD+ has never done that. If it's off and you plug it in , it will boot then -- but never had it boot when already on and I plug it in. ???
[Nook HD, HD+ Android Development] snoozer854:
I never knew about the holding of the power button until just yesterday.

I myself I don't use it every day, so I see no reason to leave it on all the time. Just like I don't leave my laptop on if I'm not going to be using it for awhile.
[Nook HD, HD+ Android Development] TBueno:
I'm also intrigued by that. And no, you're not the only one who doesn't shut it down, I'd even guess we're a majority.

Only explanation I could come up with is that being tablets and not phones, and not a novelty anymore (to most at least), the Nooks might be used only occasionally by some, thus the habit of shutting it down completely to avoid full battery drains.

Also, reports of this near-non-issue get old, especially considering there's a hardware workaround .
[Nook HD, HD+ Android Development] ieatabiscuit:
I meant when it's off and I plug it in. Like I said, I was just curious if others opinions.
[Nook HD, HD+ Android Development] snoozer854:
Who do I make a donation to?

I pretty much retired my Nook HD other then streaming music to my stereo, because I was having some battery issues with it that required me to stay close to an electrical outlet.

With CM 11 I could have tablet fully charged & be reading a book or whatever for a few minutes & all of sudden the battery level would drop to 20% & a message would pop up about plugging it in a few times it would actually shut down due to what it was sensing as a low battery.

When this happened I would plug it in & instantly the battery level would go back to where it should have been.

I was told by others that the battery must be getting bad & I couldn't locate a reasonable priced battery, so figured I have had it for 2 years I guess I will buy another tablet which I did.

Well the other day I decided to get the Nook out and put CM 12.1 on it just to be doing something, well lo & behold the battery issues are gone.

I now can go back to using it if I want to with out worrying about it shutting down due to the battery.

I just want to thank you for your work on 12.1 & was wondering who could send a donation to. It wouldn't be much I live on a fixed income, but I would like to show some support for your time.

Thank you

Mark

---------- Post added at 05:09 PM ---------- Previous post was at 04:59 PM ----------

I just recently found out about the holding of the power button.

I too was curious if it was a common problem. My wife has the same Nook HD with the same version of CM as I always had since I would update hers after I tested it on mine & hers has never had any shutting off issues. Which makes me happy, better mine then hers.

Guess you have to be careful what you ask around here it appears.

Started to remind me of the old question you used to always read "Should I turn my computer off or leave it on?"

I am just happy that CM 12.1 took care of a major issue I was having with my Nook & I can start using it more.
[Nook HD, HD+ Android Development] ieatabiscuit:
[MENTION=5300254]snoozer854[/MENTION], something that I learned whilst tinkering: The SD card can cause the following when it is getting towards the end of its life span.

Boot loops

Unbootable, even to recovery

Sporadic battery readings even after 24 hours of charging

Screen flashes suddenly, or screen becomes unresponsive

Crashing

Random rebooting

Not charging at all

If any of that is happening try things without the SD card. You can also put the card in a reader on your PC, and if it's giving grief you KNOW Windows will complain like a teenager. Linux won't complain, but will not mount it or format it. Apple will just self replicate a new vulnerability in the core OS lol.
[Nook HD, HD+ Android Development] mrcpu:
I'm running the 9-6 release, and everything is working great, except netflix. Netflix starts, and will usually play one episode of a show, but in the second one, the audio will continue playing but the video is frozen. Hit the back and play again, and it goes again. I uninstalled, wiped, reinstalled, keeps on happening. I usually cast to my chromecast, so it's not a really big deal, but it is something new.

Thanks for all your hard work.

J.
[Nook HD, HD+ Android Development] PainToad:
Probably being stupid, but where's the download link?

Edit: Found it.
[Nook HD, HD+ Android Development] ieatabiscuit:
Casting is a bit wonky, they talk about it in more detail a few pages back. I don't have all that new-fangled stuff, so I'm a bit useless there.
[Nook HD, HD+ Android Development] snoozer854:
Thank you for sharing that. I saved it for later in case I ever run into any weird problems or something.

Great tip.

Really liking CM 12.1, the Nook seems so much more snappy & no more battery issues. Great!

Think I might go grab everything I need for my Samsung tablet & put CM 12.1 on it to.

Man I did the craziest thing today, wasn't going to use my truck for several hours and I shut it off. LOL
[Nook HD, HD+ Android Development] TBueno:
Oh!, I hope you didn't have to endure the hassle of mechanically turning a key or pressing a button to achieve that... :D
[Nook HD, HD+ Android Development] amaces:
Bells and Whistles

The builds today are more special than usual, so you know, make a backup ;) Some of the more notable changes since early September:

Bumped toolchain and NDK to 4.9. After enough wrangling, both ROM and kernel are compiled with Linaro GCC, plus experimenting with Cortex-A9 optimized EABIs and SaberMOD.

All the kernel tweaks over the past ten days are now incorporated into the full builds. Quite a few tweaks to lowmemorykiller, binder, memory compaction, etc.

Added simple performance profiles under battery settings. They control the CPU governor, and can switch between interactive (default), performance, and powersave.

Nook HD/hummingbird is bumped to 1.5 GHz now, same as ovation. Despite the silicon being marked differently, it doesn't seem to create obvious issues. The current implementation is not very elegant, and can be reverted at the first sign of problems, so keep an eye on temperature, other warning signs.

These are the kind of stories that definitely add fuel to all this play development :) No worries about donations and whatnot; too many people have been involved over time to get us here. Then, I'd spend too much time second guessing all the ethical ramifications. Now, if lots of money were involved…

Although my device is spared, It's a common enough issue based on the informal poll a while ago (see attached). It's frustrating to work on it since whenever I tried, I couldn't find anything obvious and consistent in the kernel logs. I'm periodically looking into it, so we'll figure it out eventually. But yeah, it's a ridiculous bug to have, even if not a deal-breaker…

This issue started with the September 6th build, right? We've been fixing Netflix twice already, and I guess it was ripe to break again ;) Will look into it, but I may need some logcat output.
[Nook HD, HD+ Android Development] TBueno:
First impressions on ovation-0915 couldn't be better. Responsiveness and memory management are great as they've been for the last few builds/kernels, Newsstand and browsing performance seem slightly improved.

YouTube, Spotify, Deezer, Chrome, Firefox run better than never.

However, I've come accross the strangest bug: Netflix playback is "accelerated", resulting in choppy audio and video looking like mute cinema. I've cleared cache and rebooted, but it's still there. Wonder if anyone else has this problem.
[Nook HD, HD+ Android Development] mrcpu:
Nope, I have the opposite. Mebbe your netflix is stealing the frames mine isn't playing.
[Nook HD, HD+ Android Development] smileyint:
Hi ,

May I know where can i find the CM12.1 for hummingbird [2015-09-15]? Thanks in advance

Cheers,

BP
[Nook HD, HD+ Android Development] smileyint:
Finally Amaces posted the hummingbird version. Thank you for your hard work.
[Nook HD, HD+ Android Development] amaces:
Pretty odd since I don't see changes in the XML codec files, but can you guys try the attached media_codecs.xml? Unpack, replace the file in /system/etc, and reboot. Other Netflix issues may happen, but I want to check with a clean slate, and this is much easier than flashing a whole ROM.
[Nook HD, HD+ Android Development] snoozer854:
I am currently running the 12.1, 8-29-15 hummingbird version.

What is the best way to update it, in the past on CM 11 I would just flash it over what I already had installed & wiped the cache.

Should I just do it that way or wipe everything & start from scratch?

everything is working great, awesome battery life

Thanks

Mark
[Nook HD, HD+ Android Development] ieatabiscuit:
Update to the latest TWRP from amaces by flashing the zip as you would any other zip in the current running TWRP.

Reboot into newly flashed TWRP

Flash the new version of amaces' buttery goodness

???

Profit
[Nook HD, HD+ Android Development] asakurato:
At first, I had extreme lag and phantom touches with lates build, but after some time, I had less lag and no phantom touches. I guess it was Supersu problem.
[Nook HD, HD+ Android Development] snoozer854:
Thank you very much.

Really appreciate it.

Mark
[Nook HD, HD+ Android Development] dbrickg:
I was getting stuttering sound in Netflix, like a CD that was skipping. I've just now installed this media_codecs.xml in /system/etc and rebooted. Now Netflix says "Loading..." It's been doing that for 5 minutes. Guess I'll go move the original media_codecs.xml back into place and re-reboot....

OK, now I'm back to the original stuttering sound.

I should specify that the "Loading..." message I was getting with the new media_codecs.xml was happening when I tried to watch a movie. The Netflix app itself loaded just fine, but when I tried to play a movie, it would say "Loading..." forever
[Nook HD, HD+ Android Development] amaces:
This stuttering, is it new to the latest build, or it happened on 09/06 as well? I've updated the attachment (same post); can you try the new XML?
[Nook HD, HD+ Android Development] dbrickg:
I haven't tried playing any movies on Netflix on my Nook HD+ for quite some time, so I don't know if the stuttering is new or not. I'm downloading the new codecs file and will report as soon as it's installed and the nook is rebooted....

Well, at least it's no longer Loading... forever. But it *is* stuttering, just like the original. Sorry to be the bearer of bad news
[Nook HD, HD+ Android Development] TBueno:
It is new to this build. I fell back to ovation-0906 precisely because of Netflix, and it plays perfectly...
[Nook HD, HD+ Android Development] leswgnr:
It is new for ovation. 9/6 Netflix worked fine. 9/15 stutters for me also. Will try the additional zips shortly.

Speedup with stutter is probably a better description.... The additional zipped codec produced the same result as the one in 0915.
[Nook HD, HD+ Android Development] amaces:
I think I was attempting to fix an unlikely problem, and a supposedly harmless flag is creating audio thread priority issues with the software codecs Netflix uses. YouTube, other HW codec players, are fine, right? Anyway, I uploaded a quick build, then another experimental kernel. The ROM feels wonky as I haven't finished changing the toolchain and dependencies, but it should fix the Netflix issues.
[Nook HD, HD+ Android Development] dbrickg:
Thanks. I left my nook at home today, so it'll be awhile before I can test it.
[Nook HD, HD+ Android Development] leswgnr:
Other codec players were fine. I'll try the new build tonight and let you know.
[Nook HD, HD+ Android Development] amaces:
Oops, I may have built that image on a slightly off temp branch, so if Netflix doesn't even start playing, here's yet another XML to replace in etc…
[Nook HD, HD+ Android Development] ArcSmurf:
Finally updated to your latest build plus the new media codec xml file but Netflix is still stuttering on playback
[Nook HD, HD+ Android Development] amaces:
Rollback then… till we figure this out.
[Nook HD, HD+ Android Development] belfastraven:
Also happening ing to me on hummingbird, and not just Netflix--also v ideo on NYTimes and TWC.. wanted to let new rom settle for a while before reporting. I didn't see muchdeifference, aside from comments, in media_codec.xml, but noticed other files are included--perhaps a chage in one of those?
[Nook HD, HD+ Android Development] leswgnr:
Tested the 0916 build with the ovation kernel, both with and without the extra xml3 codec file. In both cases Netflix would only get to "loading".

Mxplayer had completely garbled sound.
[Nook HD, HD+ Android Development] dbrickg:
Thanks, amaces, ArcSmurf, belfastraven, and leswgnr. I'd just downloaded the 9/16 build, booted into recovery, and was backing up my last install, when I read your comments. So I let the backup finish and rebooted, downloaded the 9/6 build, and installed it. Netflix works just fine from there.

I'll stay there, I guess, till the next build.

Thanks again!
[Nook HD, HD+ Android Development] amaces:
The new experimental ROMs are fully rebuilt, so unless upstream CM introduced the bug, audio should be the same as on 09/06. Or, you can wait till the weekend builds.
[Nook HD, HD+ Android Development] belfastraven:
Perhaps bug was introduced upstream. Hummingbird (9/18) still has stuttering with streaming video. Streaming audio from radio app (WFMT) is fine, btw. ( not a problem for me--just trying to help test)
[Nook HD, HD+ Android Development] leswgnr:
I should have been more specific, MXPlayer had garbled sound while playing an mp4 video.
[Nook HD, HD+ Android Development] js290:
I didn't experience that problem with 20150906. But, with 20150917, video from Netflix, Hulu, and Youtube will initially play in double speed. Restarting the video usually fixes the playback speed problem. I see that 20150917 is no longer available for download, so there must have been other issues, too.
[Nook HD, HD+ Android Development] twiztid_:
Is there a way to delete the system related files in the data partition? With 9/17 I backed up and wiped my nook, starting fresh again and things feel a LOT more smooth than my old semi-dirty (I would wipe system and cache/dalvik partitions) install.

[Removed because, as so often happens, what is broken for days magically works within hours of posting.]
[Nook HD, HD+ Android Development] amaces:
Hopefully, the experimental builds today are stable/bug-free enough to move into the respective device folders (hummingbird soon™). Lots and lots of changes over these past couple of weeks, and I'm happy with the results. After people have a chance to test them, I'll describe the recent changes in more detail.
[Nook HD, HD+ Android Development] king200:
Somehow, I lost root cm-12.1-20150920-UNOFFICIAL-ovation.zip. I couldn't locate where in settings to enable. I flashed a supersu zip and seems to be working fine.

I also lost the ability to boot into recovery from the power menu.
[Nook HD, HD+ Android Development] amaces:
Enable Developer options, then Advanced reboot. The ROMs are normal user builds now, rather than userdebug like before, so a few options are hidden, but still there. I thought root would remain untouched, but I like SuperSU better anyway.
[Nook HD, HD+ Android Development] belfastraven:
As ovation poster noted,on hummingbird, root is lost and the setting to enable is gone from developer options. SELinux is enforcing, so boot to recovery from power menu for me. Video does seem to be working, however. :)
[Nook HD, HD+ Android Development] king200:
Developer options were and stayed enabled. I had to put the option on and then off. {ower off, boot into recovery, NOW WORKS! :)
[Nook HD, HD+ Android Development] amaces:
Grab the SuperSU (stable/2.46?) ZIP.
[Nook HD, HD+ Android Development] king200:
You might try this SuperSU-v2.49.zip https://app.box.com/s/dmbdta7krivxij75ev4yh0bfwtgo89yf

I think it is really beta SuperSU-v2.49.zip.
[Nook HD, HD+ Android Development] belfastraven:
Thanks--I 've got the 2.46, which is fine. I just wanted to let [MENTION=4473900]amaces[/MENTION] know that we had totally lost root and that it no longer showed up in developer options... and to warn others before they flash
[Nook HD, HD+ Android Development] amaces:
That was good to point out. In my mind, folks had already switched to SuperSU, and this change was supposed to be transparent.
[Nook HD, HD+ Android Development] belfastraven:
Wow--after rebooting a couple of times, I seem to be able to reboot to recoverry from power menu.. Yea!! Hope this lasts.

Am eagerly awaiting your writeup about changes. Could just rebuilding without debug be helping? :)
[Nook HD, HD+ Android Development] leswgnr:
So far so good for me, using 920 ovation and kernel. Video issues seem to be resolved, performance in general seems fine. Will keep testing and report any issues I find.
[Nook HD, HD+ Android Development] swaaye:
Has there been any progress on the strange VPN lack of connectivity issue?
[Nook HD, HD+ Android Development] js290:
The cmupdater script seems to be working on 20150920 while using your TWRP 2.8.7.4. Good work.
[Nook HD, HD+ Android Development] TBueno:
Ran ovation-0920 for a while, awesome work as usual! Video works, everything is smooth, and both boot to recovery and power off work for the first time in quite a while (as long as SuperSU is installed).

Only (very minor) issue I detected is a "Interf sist has stopped" dialog the first time I tap the task switcher button after a reboot.

I could not get root privilege though, and I've kind of hit a wall. Here's what I've tried:

* installed SuperSU 2.46 successfully, Greenify works in root mode, but other apps don't even detect there's SU, couldn't grant them access. Rebooted a few times and tried again

* "restored" SuperSU when shutting device down through TWRP recovery (a prompt shows up)

* reverted to 0906 and installed SuperSU before updating to 0920. SuperSU worked all right in 0906, authorized CMFM, Flashify, AirAudio successfully. Ticked persistence in SuperSU options and flashed 0920, back to previous situation

* reset and reinstalled SuperSU from within its advanced options

Here's what I haven't tried:

* full wipe (not sure it's worth the trouble right now)

* reinstate root through CWM (if there's any version compatible with AMaces latest builds)

* do something over ADB (I lack the tech knowledge)

So I'm back to the fantastic 0906 and stock SU and I'm fine with it, but still curious about root giving me a hard time in 0920. Could it be related to enforcing SELinux?
[Nook HD, HD+ Android Development] belfastraven:
[MENTION=3450613]TBueno[/MENTION],

did you flash the supersu zip in recovery? Just installing the app will not get root back. Flashing the zip worked for me on hummingbird
[Nook HD, HD+ Android Development] TBueno:
Yes, 2.46 zip through TWRP.

SuperSU has given me a hard time before in another device, I wonder what I'm doing wrong...
[Nook HD, HD+ Android Development] belfastraven:
Are you not getting propted to give root permission if you run flashify? Have you checked the settings on the supersu app? I notice that it can be set not to prmpt, e.g. and also to use cyanoigenmod permission, which might not be good in this case. Other than that I'm out of ideas right now.
[Nook HD, HD+ Android Development] TBueno:
Yes, I pretty much exhausted its settings, including reinstall. Thanks for the input anyway.
[Nook HD, HD+ Android Development] dbrickg:
Aha! Thanks to everyone for pointing out the loss of root with the built-in SU. I installed SuperSU before installing the 9/20 zip. Hopefully that'll all work out....

Well, that didn't seem to work at all. Restoring to backup of the 9/6 nightly....
[Nook HD, HD+ Android Development] ieatabiscuit:
Little thing I noticed, nothing serious in my opinion. I went to install V4A which requires SELinux to be permissive for the install. Upon simply using SELinux Mode Changer to put it into permissive, it rebooted into recovery without a hitch. I'm going to play with it more, and see if I can reproduce everything on demand both with permissive, and enforcing. It was late, so I didn't go back to enforcing to test, but plan to today. I'm curious if being able to reboot to recovery sticks or not, but wanted to post this before I forgot about the whole thing. Sorry about the half cocked information, but now I have a reminder to stare in my face lol.

Update: I can not make it reproduce. So I changed SELinux to permissive, reboot to recovery works, then changed back to enforcing, and reboot to recovery still works. Like I said, it's not like it's a serious issue, but curiosity is a beast. I don't think SELinux is what's effecting reboot to recovery, as [MENTION=4473900]amaces[/MENTION] has said before, but whatever is, is daft, confusing. Clearly it only seems to work when you offer it cookies, and it's picky about what flavor at the time of offering. Silly CM ROM, go home, you're drunk!
[Nook HD, HD+ Android Development] dbrickg:
I guess I don't understand how supersu works: when I installed it from the store, it offered to install itself by rebooting into recovery, which it apparently did. I mean, the phone rebooted into recovery, and when it came back up, supersu was the default su. For instance, when I run an app that needs root access, supersu pops up and asks if i want to grant that app root. But when I installed the 9/20 nightly and rebooted, nothing worked. There was an error message saying that there was no su installed. I restored to the 9/6 nightly, and that seems to be working. So, I don't know what to do at this point.
[Nook HD, HD+ Android Development] vinceweis:
I downloaded the one that is linked in post 1047, flashed it in recovery, and it has worked well since then.
[Nook HD, HD+ Android Development] TBueno:
That's almost exactly what happened to me, I just flashed it through recovery: it's fine in 0906, then it simply doesn't work in 0920.

I guess something has to be done for it to circumvent enforcing SELinux...
[Nook HD, HD+ Android Development] reflecx:
I second that, using this SuperSU works

Here's the link - https://app.box.com/s/dmbdta7krivxij75ev4yh0bfwtgo89yf
[Nook HD, HD+ Android Development] js290:
Just flashed 20150921, no built in su. SELinux enforcing so booting into recovery requires buttons. Video seems to work well like 20150920.
[Nook HD, HD+ Android Development] dbrickg:
Thanks, all, for the SuperSU suggestions. I'll try that next time I've got my Nook in hand.
[Nook HD, HD+ Android Development] ieatabiscuit:
I did a full wipe and reinstalled just to addressee what happens. Reboot to recovery worked with no issues at all. Did not change SELinux in any way, did not have to finesse anything at all. Clearly I have made it happy somehow.
[Nook HD, HD+ Android Development] camp8615:
Same here reboot to recovery working for me as well
[Nook HD, HD+ Android Development] belfastraven:
just want to be sure: Is latest hummgbird build the 9/20 in experimental? I notice ovation has a 9/21 in ovation folder. Also, where is latest ( wi SuperSU binary) TWRP?

thanks again, [MENTION=4473900]amaces[/MENTION].
[Nook HD, HD+ Android Development] amaces:
I had some issues compiling the equivalent 0921 hummingbird build yesterday, but it should be done in a couple of hours. What I call TWRP 2.8.7.4 has the updated su binary, but really, any recovery that can install current CM12.1 will be OK. Worst case scenario, SuperSU will take a few seconds to update it.