yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] TBueno:
Great work

April CM Ovation builds have been very stable and smooth.

With a ROM as polished as this, we tend to pay more attention to details and small annoyances. So the "AudioFX has stopped" dialog - which dates back to CM11 at least - started getting on my nerves. It is completely unrelated to AMaces work (even the One Plus One has it!), and I even considered switching to AOSP just to get rid of it, but there's a workaround: disabling the AudioFX app altogether. I used Quarantine, and it worked flawlessly after a reboot. AudioFX is now shown as just another pre-installed disabled app under Settings>Apps. All "equalizer" options within music apps vanished, clean and painless. Could not reproduce the "AudioFX has stopped" dialog so far, and nothing else seems broken.

The downside is loosing the ability to tame audio to your liking, making this a not good alternative to audiophiles since 3rd party equalizers don't work in android 5+. In my brief testing, music sounded pretty good through bluetooth phones, although rock drums and guitars came out a bit shakey through speakers.

Wifi stability has been great for me with April builds, at least as good as CM 11 and 12. Plus: shutting it down through power button makes it actually stay off. Reboot to recovery works as it should too.

The only strange behaviour I've noticed in latest builds is asking for bluetooth pairing as if it was the first time I connected the device every time I use my headset (Sol Republic).

Once again, thank you very much AMaces. :good:
[Nook HD, HD+ Android Development] J.parkerrrr:
Does anyone have a flashable zip for amaces' kernel?
[Nook HD, HD+ Android Development] sepehr@teh:
I installed AOSP & TWRP & gapps Nano . Everything is ok . Now I want to install more apps . Can I use opengapps full package ( Aroma ) .

I have to use it in twrp environment? And I might get error message ( error no 70 ) ?

Is it selective ? To select which one to install ?
[Nook HD, HD+ Android Development] Tight Git:
You can only install one Gapps package as far as I am aware, so now just download the apps you require from the play store.
[Nook HD, HD+ Android Development] BultoPaco:
Interesting observation for install of the 0407 CM build. After reading TBUENO's post (a few posts back), I loaded the 0407 CM build on both devices -- ovation and hummingbird. I confirmed that turning the ovation off through the power button really does result in full shut down. However that is not the case with the hummingbird. It still just reboots when you select Power Off from the power button. Not a big deal to me but I usually don't notice any differences between the two devices.
[Nook HD, HD+ Android Development] leswgnr:
My Ovation still powers back on after shutdown, and has pretty consistently thru most of these CM builds
[Nook HD, HD+ Android Development] BultoPaco:
I agree with you about the historical consistency of the power button behavior. Never the less, my ovation really does completely shut down when Power Off is selected in the current build. Are you using a custom theme on your ovation?
[Nook HD, HD+ Android Development] mikeataol:
My Ovation also reboots on PowerDown, with or without advanced reboot settings checked in developer options. I'm using just the default theme, tried disabling System Profiles, didn't make a difference.
[Nook HD, HD+ Android Development] leswgnr:
NO, just the CM default. I have read where it makes a difference if it's charging or not, and a few other conditions, but none of the states seemed to make a difference on my Nook, and it really is such a small item for me that pursuing it in any great length wasn't worth it.
[Nook HD, HD+ Android Development] x86demon:
I've faced with same power off problem with my ovation (CM13 build 0401).
[Nook HD, HD+ Android Development] TBueno:
Mine used to reboot under 0401 build too, but 0407 powers it off properly.
[Nook HD, HD+ Android Development] ieatabiscuit:
I usually disable the built in CM AudioFX by default anyway, and V4A (last I checked, which I plan to again in a little while since I have not played with my ovation in a bit) works well on this ROM. Now I have to choose if I want to play in AOSP Land, or CMville... decisions decisions...
[Nook HD, HD+ Android Development] ieatabiscuit:
I must say the 0407 CM Ovation build is a beautiful work of art so far! I reboot from trying to shut down, but I personally never turn it off anyway. Animations are smooth, boot time is low, no hangs on reboot (like my phone's ROM does), my BT keyboard plays nicely with it, and I am currently using V4A with it and have AudioFX disabled with pleasing results.
[Nook HD, HD+ Android Development] TBueno:
Would you mind sharing some details? Like which version and installation method have worked for you?

p.s. yes, CM-0407 is makes Ovation shine...
[Nook HD, HD+ Android Development] ieatabiscuit:
Would you believe stock latest official release installed via the app from their website? No joke, it installed with no issues. I will put a screen shot up later if you want.
[Nook HD, HD+ Android Development] sasmith-129:
FWIW, here is my observation regarding power-off behavior over the last several builds (maybe/probably even longer).

I have the lock screen enabled on my ovation (Nook HD+). It seems like Power-Off (almost?) always works when I hold the power button and then select "Power Off" *iff* the tablet is locked. If my ovation is *not* locked when I try to Power-Off, then it seems to be hit or miss (favoring reboot).

It could be my imagination as I intentionally reboot nearly daily and tend to leave the tablet charging overnight. However, when I do try to power off, this seems to do the trick for me.

I just thought I'd pass this along in case someone else wants to try to replicate it.
[Nook HD, HD+ Android Development] TBueno:
Thanks for the info, couldn't be easier.

Installed it just now, it really works and there's a lot to play with.

Wish I'd known about this a few years ago...
[Nook HD, HD+ Android Development] ieatabiscuit:
Oh yes, and watching a movie with it is amazing, small, but amazing.
[Nook HD, HD+ Android Development] sepehr@teh:
Which ver of AOSP is stable ? And which gapps rather than Nano I can use ?
[Nook HD, HD+ Android Development] ieatabiscuit:
If it is in the folder for the specific hardware then it's deemed stable. As for gapps, I use pico on my ovation, I don't like all the excess taking up my precious resources that can be spent elsewhere. Nano is best if you want that extra functionality, and you can then install what's missing yourself. To tell what can fit look at the free space in /system in twrp, and go for what will fit there. Unfortunately mm gapps is a fat little bundle, not much fits so the leftover is usually put into /data by the user manually; hence nano, or in a minimalistic case like mine: pico. Also, I would use the latest releases, using them is similar to eating large amounts of bacon slathered in cheddar cheese.

---------- Post added at 08:39 AM ---------- Previous post was at 08:29 AM ----------

Update to battery experiment: since my reset using factory recovery, then reflashing from the ground up, I have had no issues to mention. I have tried several ROMs, and spent several days with this to see if the issue persisted. So, if anyone flashes and runs into weird battery activity, it is most definitely NOT the ROM its self. For new ppl with the issue, no reason to clutter forums with questions and pointed fingers about a ROM causing sudden battery death. Just pm me and I'll help you. I've beaten the subject near to death, and have tried all that can be tried even on the hardware side of the issue.
[Nook HD, HD+ Android Development] sepehr@teh:
Just installed " aosp_ovation-ota-MHC19Q.160406" + twrp 3.0.1.0 + gap nano . I started using , seems OK.

.

Now I want to install Nook app , but it says "your device is not compatible" . How can I install ?

BR
[Nook HD, HD+ Android Development] ieatabiscuit:
Side load it. It's been discussed in here so a quick search should do the trick. If not this thread then the cm12.1 thread that this one branched from.
[Nook HD, HD+ Android Development] TBueno:
For the record: that line by me you quoted was about Viper audio, which previously required BusyBox etc. to be installed, completely unrelated to the Nook app.
[Nook HD, HD+ Android Development] ieatabiscuit:
Yeah... about that... I'm not allowed to respond to things from my phone at 6am anymore. I still have not figured out how/why it put you in there as a quote when I went to respond to the Nook app question. As for busybox, the ROM has it installed already, I think 1.22, you can update to 1.24, but why, it works right?
[Nook HD, HD+ Android Development] TBueno:
I can't say, I'm not familiar with BusyBox to be honest. It is mentioned in the Play Store version of Viper, which I couldn't get to install, but the .apk available at the developer's site can be simply sideloaded, as you pointed out.

BTW, if anyone else is interested, it can be found here: vipersaudio.com/blog/?page_id=48. It works (and sounds) great, and integrates seamlessly with CM13.
[Nook HD, HD+ Android Development] mikeataol:
Hi, Can you say under what conditions AudioFX fails? . I've been running a while and haven't seen it yet, granted I don't do audiophilic things very often, but is it worth the effort to go to the ViperAudio? Thanks
[Nook HD, HD+ Android Development] TBueno:
The easiest way to reproduce it in my use case was skipping through a few songs in Deezer. It usually takes just 3 to get a "Audiofx has stopped" dialog. Even if I didn't skip any tracks, it would typically appear after a few minutes. Spotify and other music apps triggered it too, just not so fast.

In CM 12 or 13, it was just a dialog that disrupted my interaction with the tablet, an imperfection. Music itself wasn't even affected as far as I could notice. In other ROMs or devices, it can get ugly, and it's one of the oldest cyanogen bugs I've come accross, even affecting the OnePlus One.

If you don't see that dialog and sound is good enough, I don't see a reason to disable it or install Viper. AudioFX is good enough and the interface is quite pretty. As the saying goes, if it ain't broke, don't fix it...
[Nook HD, HD+ Android Development] pchc_lx:
can confirm I wasn't able to play large video files in MXplayer with an NTFS formatted microSD card. formatting as EXFAT fixed it.

running pretty well, one minor bug is when attempting to SHUT DOWN- the tablet will often times restart / start back up again on it's own.

will also sometimes have a difficult time waking up from sleep, using either HOME or POWER buttons. will immediately fall back asleep and can be hard to get the device to unlock and wake up. however this also happened on previous ROMs with me, so could be something wrong with my device or etc.
[Nook HD, HD+ Android Development] ipdev:
Update about the nook.apk (running cm - ovation)

NOOK_Read_eBooks_Magazines_4.1.1.12 (build 545) was the newest that would install and run.

(Newer builds would not install or get force close errors.)

After setting up my account, and using 41112 for a few days, I gave updating a chance.

I jumped to NOOK_4.5.0.59 (build 651) Had to do the "welcome to you nook" (Swipe left / right ect.)

Since 45059 was working... (Of course & after a reboot) I installed NOOK_4.5.2.50 (build 667 - Current version.)

No problems with it. Been using 45250 for the last 2 days.

Currently running :

twrp-3.0.2-0-ovation -- cm_ovation-ota-MHC19Q.160407 -- open_gapps-arm-6.0-pico-20160407 -- BusyBox-v1.24.1-Stericson -- BETA-SuperSU-v2.67-20160121175247 (I didn't realize that I installed an old version of su. Will be updating to 271.) -- Nova Launcher_4.3-beta4
[Nook HD, HD+ Android Development] ieatabiscuit:
It's a well known bug when using a cover that has the magnet in it to wake the device. The magnet feature tries to override the lockscreen setting, and the two just don't play well together. If you disable the magnet sensor by either removing the magnet, or via xposed, or if you just turn off the lock screen so it wakes directly to the desktop, it becomes much less of an issue. Also, to get it to come on with none of these fixes, simply reclose, and open the cover. In short, you just have to finesse it a bit. It's not your hardware though, nor is it any specific ROM. Just wonky design flaw.
[Nook HD, HD+ Android Development] danj88:
Running cm_ovation-ota-MHC19Q.160407.zip

(I used TWRP 3.0.1.0 to install after wiping)

Problems:

- After reboot, WiFi won't turn on unless you swipe down on the status bar and click the WiFi icon, even with the WiFi network already saved.

- Youtube 720p 60FPS won't work (sound works - but no video)

- Videos in browser (Chrome) play fine, but when you choose full screen there's static all over the screen and the original video is in the middle surrounded by the static.

These problems were not present in cm 12.1 [2015-12-18]
[Nook HD, HD+ Android Development] pchc_lx:
wow this is a revelation- thank you! flashed xposed and installed a module to sort this. it's probably placebo but the whole device seems to be working a little better now :p
[Nook HD, HD+ Android Development] :
Wow, so I've had the dreaded force reboot issue forever with this tablet and all verygreen's cyanogenmod versions including the official ones - which verygreen said somewhere around here that he couldn't fix it (or words similar).

Your aosp March 14 2016 version has had no force reboots up to 550 hours and continuing! Before, it would only get up to the 300s max, then a force reboot.

A search for reboot shows no one mentioning this in your thread.

Thank you for building and making it available. Glad I tried it.
[Nook HD, HD+ Android Development] ipdev:
Glad I never ran into that problem. ?

(Current uptime 22 hours 40 minutes. - Ran an update that required a reboot last night.)
[Nook HD, HD+ Android Development] sepehr@teh:
I'm using AOSP , last ver. Works well . I'm using SuperU for root. It's OK now :

1. For having root access , this software have be installed on device ? Or I can remove it ?

2. If answer is yes , I have to let it to update or not ? Note that updated version can't root the device . Update might make it not working ! So it would be let to update ?
[Nook HD, HD+ Android Development] ieatabiscuit:
FOr installing root, you have to flash a .zip to make it work. If you are not rooted, you can't install the updated root via .apk because the process requires root to do it. I suggest removing the installed SuperSu.apk, and get the latest .zip file and flash it via TWRP, then if it updates itself from the GP store, all will be fine.
[Nook HD, HD+ Android Development] sepehr@teh:
AOSP : Could not download files. Says : Unfortunately browser stopped working.

This problem forced me to install Firefox!

Anyone faced this ?
[Nook HD, HD+ Android Development] xflier:
Grant permission in settings for browser, issue should be gone
[Nook HD, HD+ Android Development] neonleon29:
I'm currently using AOSP with Xposed installed. If I dirty flash a newer AOSP version, will my Gravity Box settings remain or will I have to set up everything again from scratch?
[Nook HD, HD+ Android Development] ipdev:
Found this in a different thread. Haven't used it yet to restore my settings.

I did install and made a backup.

http://xdaforums.com/showthread.php?p=66322922
[Nook HD, HD+ Android Development] sepehr@teh:
AOSP installed +TWRP : On clock when clicking on world icon this message appears " Unfortunately, Clock has stopped"

Any solution?
[Nook HD, HD+ Android Development] ieatabiscuit:
Try Google's version, they are usually more updated than the AOSP versions. The keyboard for example behaves better with the Google version than the AOSP one.
[Nook HD, HD+ Android Development] sepehr@teh:
You mean I have to update them ? Or download new clock, keyboard . . . from play store ?
[Nook HD, HD+ Android Development] ieatabiscuit:
You have to download new ones. The ones that come stock are usually not as well maintained, that's why they sometimes give grief. Just search "google" in the play store, and it will list all their more updated versions of the stock apps. The Goole versions are also usually identical anyway, no no real learning curve.
[Nook HD, HD+ Android Development] sepehr@teh:
Great. I downloaded some of them. But what about old version. I tried to uninstall, but they could be disabled .

Disabling those apps , might damage the system ?

Or make it slow & heavy ?
[Nook HD, HD+ Android Development] ieatabiscuit:
I disable, or even uninstall the old ones with no bad side effects. I usually just use something like Titanium to freeze them anymore though. If I uninstall them, they will be back with the next update, but once disabled, they stay that way unless you clean flash.
[Nook HD, HD+ Android Development] MrPresident:
EDIT: can anone explain why i get a message at the top of my terminal saying:

/system/bin/sh: /system/etc/mkshrc[10]: getprop: not found

also. i cant use getprop or setprop commands.

im guessing this is my fault?

EDIT: this is on the AOSP version.
[Nook HD, HD+ Android Development] TRS_80:
Love the ROM!!! Thank you amaces for yet again extending the life of these tabs.

Sorry if I missed it in the thread, but has anyone found a better kernel ( or settings) for battery? When I was running KK using Bexus, I was getting days and days( I think 2 weeks was my best) on standby, now only a couple. Don't need the performance so much as battery savings.
[Nook HD, HD+ Android Development] ieatabiscuit:
I don't seem to have that issue personally. Do you have anything running in the background? Do you have any apps that do not close properly? Most social media apps (*cough*Facebook*cough,cough*) will murder a battery on most devices.
[Nook HD, HD+ Android Development] TRS_80:
Nah man, I dont' run anything like that on it. Reading, light surfing, email etc. The top 2 draining apps according to Avast are @ <1%, weather and google. I did find a regional wifi setting? Corrected that, we'll see what it does. How many days do you get with what usage?

Is anyone working on a MM Bexus like kernel?

Thx
[Nook HD, HD+ Android Development] ieatabiscuit:
I haven't seen any kernel development aside from the custom tweaking that was poured into this ROM to make it what it is. As for my tablet, under lite usage like that, I could use it for at minimum a week. After I got the sudden battery drop from random high percentage to 1% nonsense handled, I have seen it last well over a week or so. Thought it would have been dead, opened the cover, and it was still at 40% or so. I don't get that frequently though, as I tend to burn the battery down with apps like the Fallout 4 companion app, and whatever else pops in my head. I've even used it to power a 1TB external usb HDD (mostly to see if it would though, and it did).
[Nook HD, HD+ Android Development] TRS_80:
Hmmm...I guess I'll spend some more time going through running apps and processes. Only other explanation is my batt is dying :(
[Nook HD, HD+ Android Development] ieatabiscuit:
That is possible, but with as easy as these are to take apart, the battery is easily testable with a multimeter. Also, I have found that when mine acts up, it's time to reflash back to full stock, and do a full factory reset from the stock recovery. Then reflash back to what you want to use. Sometimes the partitions that handle the hardware info, which includes the battery metering and charging drivers can get messed up after it's been flashed several times. Just an idea to try. I've beaten the battery theories to death here, so there will be instructions in more detail in previous threads made by me.
[Nook HD, HD+ Android Development] MrPresident:
"find /system -name getprop" didnt produce any results.

"ls -l /system/bin" confirmed there was no getprop or setprop symlinks to "/system/bin/toolbox", which i goggle said was supposed to contain getprop & setprop. other symlinks to toolbox were present.

http://pastebin.com/ZJLAchLt

so i copied the symlinks "/system/bin/getprop" & "/system/bin/setprop" from my phone and pasted them to "system/bin/" on nook.

And, voila, no more error message at top of terminal, and I can use the commands in the shell now.

I'll attach the getprop and setprop files in case anyone else has same problem.

I'd appreciate if someone could explain why they were missing in the first place? From what I read it might be cause of some problem with toybox on marshmallow? Toolbox must have had the correct getprop/setprop commands included in it anyway, even though they weren't symlinked anywhere, right? becuase, the files I copied over are just symlinks themselves?? (but then why does a link have to be 156Kb?, "ls -l /system/bin" showed them to be symlinks to toolbox anyway).

3rd edit: oh yeah, forgot to mention that i dont know what i'm doing. so i wouldnt follow my advice even if i needed it.
[Nook HD, HD+ Android Development] smileyint:
Hi Amaces,

I had installed the latest cm for hummingbird cm_hummingbird-ota-MOB30D.160422 that you posted.

I noticed the settings and connectivity on the second pulldown from the status bar is not working. Is there any setting to toggle for that?

Thanks in adv.
[Nook HD, HD+ Android Development] belfastraven:
I'm not sure what you mean by "second pulldown", but I had a problem with pulling down the settings/getting notifications when I initially dirty flashed. I went into recovery and wiped cache and dalvik, and that problem seems to have been resolved for me (also hummingbird). You might want to try that.

I am still getting some fatal errors which are throwing off tombstones--I'm still investigating those, but they do not prevent me from using the nook.
[Nook HD, HD+ Android Development] belfastraven:
tombstones/fatal errors

[MENTION=4473900]amaces[/MENTION]

logs and tombstones from hummingbird 4/22 cm build. The logs/tombstones are from after a reboot after wiping cache and dalvik. (see above)

Sorry--there doesn't seem to be any way to include these in a bug report.
[Nook HD, HD+ Android Development] smileyint:
Hi Belfastraven,

The problem is pulling down the settings you mentioned. I had clean flashed including wiping dalvik and cache directly after the installation. I did one after you mentioned but still no go on the pull down settings. Right now, i just dragged out the settings to the homepage for easy access. Thanks.

Maybe it will be ok for Amaces next release. Thanks for his hard work.
[Nook HD, HD+ Android Development] dbrickg:
Just dirty flashed the ovation cm13 20160422 nightly. Seems to be working just fine so far. No problems that I've noticed.
[Nook HD, HD+ Android Development] BultoPaco:
Yep, seems like everything is OK on my Ovation. I'll try Hummingbird tomorrow and see what difference there are between devices.
[Nook HD, HD+ Android Development] mikeataol:
I clean flashed this ovation 160422 version, and there is fer sure something up with notifications and the quick settings.

I'm not seeing any notifications, and the quick settings tiles are missing.

Tried several things, applying a downloaded theme, cleared cache and dalvik, looked at all the permissions, and I'm seeing no notifications and no quick tiles.

It's still a good rom, has good chromecast connectivity (except for casting the screen) , all the apps that are supposed to see a chromecast do. This isnt the case with most CM13 roms.

Thanks for the work on it...
[Nook HD, HD+ Android Development] mikeataol:
OMG. I must be dreaming....

I installed the AOSP version and its the first CM13 ROM that supports native screen casting to ChromeCast.

I only installed it to compare against the CM13 version and its issue with notification and quick settings, but, very glad I did.

Thank you very much!
[Nook HD, HD+ Android Development] TBueno:
Great news! Let's hope the upcoming CM builds learn that trick too.