yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] amaces:
Wait, maybe I'm misunderstanding the issue, but the way it's supposed to work, volume events go to the current audio source. Whenever music, YouTube, etc are the foreground source (in the audio sense), the volume buttons control the Media volume slider. If nothing is playing, and you're on home screen or some other app, the buttons control notification volume and related settings.

Are you by any chance charging or connected to USB when powering off?
[Nook HD, HD+ Android Development] twiztid_:
On other builds of CM the volume on the home screen affects the speaker volume, unless your phone rings or has a notification recently. But either way, the volume for the speaker (or notification, or ringing) doesn't affect the keyboard (they still play), and had no effect in Hearthstone. I can try with a video in Youtube/MX Player, but I think the result is the same.

Going into the Music app and changing the volume DOES show the speaker volume icon, but keyboard is still at full volume. I can test this further tomorrow.
[Nook HD, HD+ Android Development] mhunt13:
That would actually make sense, it just not the way previous CM versions worked. My notifications for emails seem to be really loud, no matter where the sliders are set.

No, not connected at all. Just can't power it off with the power button. This immediate powering back up is consistent in both your builds. It's like the action for the power off menu is the same for 'power off' and 'reboot'. Both result in a reboot. (I know the Nook stays powered on when plugged in).
[Nook HD, HD+ Android Development] matthewsjl:
Is tablet encryption broken in these builds?

I try to encrypt and get a few seconds of the green android gear man - then a reboot.

Thanks,

John.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Android 5.1

When official nightlies will arrive, will they going to be 5.1.x or 5.0.x?? Any Idea.

And also excited about brand new type of theme engine.

Although this build is based on ART, switching back and forth between apps is quiet slow. Infact slower

than dalvik in kitkat and jellybean. Is it going to be improved later??

Is there any possibility of scrolling cards in overview be smother?? moto e can handle it quiet properly.

Nook hd (hummingbird) also should in my opinion.

Then there would be no complain about these rom.

-------------------------------------------------------------------------------------------------------------------------------

Also what is the status of Xposed framwork?? which modules are perfectly working on hummingbird??

Let me know.

Thanks.
[Nook HD, HD+ Android Development] twiztid_:
After further testing audio does work as intended, but with some exceptions:

1). Keyboard clicks ignore volume setting. This makes Lollipop unusable for me because I browse on my tablet at night, and the clicks are quite loud.

2). Volume buttons should change Sound volume by default, not Notification. This is the default behavior for previous versions of Android/CM, and combined with #1 are why I thought sound was broken.

3). Volume Adjustment Sounds option (Settings -> Sound -> Other sounds) does not function. Very minor.

Sorry for any confusion I caused, and thanks for the help.
[Nook HD, HD+ Android Development] Dread This Day:
...You could simply turn the "Sound on key press" option off in the keyboard settings. I don't know why anyone wants to hear that anyways.
[Nook HD, HD+ Android Development] twiztid_:
Because I like to hear if I missed pressing a key when I type, but the sound itself is broken as well (only registers every 3rd press when I start typing fast), so I might as well turn it off.

It also worked fine under hashcodes first two builds, so its not like its something that never worked.
[Nook HD, HD+ Android Development] Dread This Day:
But you're staring right at it? To each their own. Hummingbird seems to have a lot less issues than Ovation, the sound on key press is annoyingly perfect over here. It'll get sorted out soon I'm sure.
[Nook HD, HD+ Android Development] CweeperHugz:
I don't usually look at my keyboard too much. I guess I'm just that good at typing? I just turn auto correct and sound on keypress off because they annoy me, but I suppose some people like hearing it. Nonetheless, hopefully this fixes some audio issues I've been having. I haven't flashed it yet. I'll try when I get home.
[Nook HD, HD+ Android Development] MossyTC:
Has anyone tried [MENTION=4473900]amaces[/MENTION]' 15th March ovation build? [MENTION=4473900]amaces[/MENTION]' last post here was on the 14th, so there was no announcement here about that build.

FYI The latest hummingbird build was uploaded on the 18th.
[Nook HD, HD+ Android Development] MossyTC:
I've just seen that [MENTION=4473900]amaces[/MENTION] has posted since then and at least one poster has pointed out the 15th March build already. Don't know how I managed to miss that the first few times I read through those pages.
[Nook HD, HD+ Android Development] N!ghty:
just flashed it. seems good to go :good:
[Nook HD, HD+ Android Development] MossyTC:
Yes, I get this problem installing apks on a clean install of the March 15th build, ovation.

For some apps on clicking Install on the standard "installing from apk" install dialog, I got App Not Installed after about a second. This happened both for apps that were originally installed from Google Play Store and Amazon Appstore. Notably Amazon Appstore apps that would not install from Titanium Backup backups would also not install from Amazon Appstore (same problem).

For reference one of the apps is Aldiko.

What fixed it for me was changing the Preferred install location setting from Let the system decide to Internal device storage. Removeable SD card works too.

After installing the problematic apps I changed back to Let the system decide and reinstalled a couple of those apps. This time the install worked, the apps worked, but they disappeared after a reboot.

For anyone who needs to know the Preferred install location is in

Settings -> Apps -> Menu (3 vertical dots, top right)
[Nook HD, HD+ Android Development] KenNashua:
I got the same scrambled screen graphics on the omnirom-twrp-2.8.5-hummingbird after flashing it from flashify.
[Nook HD, HD+ Android Development] davidron:
My screen only freaked out when certain apps were running. I was able to eliminate the scrambled screen graphics by going into setup->developer options and disabling hardware overlays. After doing this, it might make things a little faster if you also force GPU rendering. But, disabling hardware overlays seems to have a significant negative impact on the Nook's performance.
[Nook HD, HD+ Android Development] amaces:
TWRP 2.8.6 Early Builds

TWRP 2.8.6.0 sources are out in their android-5.1 branch. Beyond a few bug fixes (notably, timezone selection, clock is finally correct!), it contains changes to the theme engine plumbing and build configuration, although those are not user-facing. Nothing major, but I uploaded new recovery builds for both ovation and hummingbird.

As usually, the Nook HD+ stuff is tested, the rest, not so much.

P.S. A new updated ovation ROM is in there as well, although didn't notice any performance changes yet.

Not sure what to tell you… You're the first with this problem after reverting to the original build configuration. Try the new 2.8.6 version.

---------- Post added at 01:33 PM ---------- Previous post was at 01:28 PM ----------

His problem was with the hummingbird recovery.
[Nook HD, HD+ Android Development] Zippy Dufus:
Hello [MENTION=4473900]amaces[/MENTION]

Have you added any new patches to your ovation build or is just capturing new upstream Cyanogenmod changes?

(I'm interested in the issue with Hangouts Dialer.)
[Nook HD, HD+ Android Development] belfastraven:
New build is fine for me on Hummingbird. Time is working once reset. thnx.

P.S. I am happy to test Hummingbird roms. I notice that there were several WIFI and bluetooth changes in the last nightly. I'm hoping , too, that if we get to 5.1 it will fix more memory issues.
[Nook HD, HD+ Android Development] w1ll1m:
I take it, the process is the same coming from CM11? Also on CWM v6.0.4.6.

How would i change the partition to F2FS?

Cheers
[Nook HD, HD+ Android Development] twiztid_:
The instructions are the same for CM11 and 12.

For F2FS you need the modified TWRP (Team Win Recovery Project) 2.7.1.0, it has its own topic here., but for F2FS get this version.

Converting your /data partition WILL wipe ALL your data, so back up your files.
[Nook HD, HD+ Android Development] amaces:
No new patched beyond the few kernel changes I mentioned earlier; I try to keep things as close as possible to CM12 upstream. My focus has been the video buffer underflows, which still happens occasionally. I had read about issues with Hangouts Dialer, but never really investigated. I use GVoice pretty much for everything, but I wouldn't rely on the mic in these Nooks. Anyway, I checked on the current build, and Hangouts crashes as soon as I try to place a call :( There could be many reasons, including CM12's audio routing, our device config, the recent kernel changes, etc. Is this a deal breaker issue for you?

Sure, I left a hummingbird build baking overnight. Should be ready and uploaded tomorrow morning.
[Nook HD, HD+ Android Development] Zippy Dufus:
It is not a deal breaker because I can just flash a Kitkat ROM. However, it is an important feature when I am travelling on vacation and business to avoid long distance charges.

I think that the fix is probably something simple but simple things can sometimes be hard to find. I noticed that the LP kernel's configuration is now significantly different from verygreen's Kitkat kernel and maybe something got lost in the transition.

Hangouts started out "functional" but with unintelligible sound but a recent Hangouts update seems to have broken it completely. Last time I checked, it is broken on my CM12 Nook Tablet as well.
[Nook HD, HD+ Android Development] belfastraven:
Am running amaces 3/26 hummingbird build. Everything is fine so far for me. Google maps still will not find location (it has never worked on cm12 on HD for me) although google earth does.

Maps used to work (find location) on Nook tablet, but now does not. I haven't investigated whether it was a map update or rom update that killed it there. On the HD, other apps , like accuweather, do find the location. My location services are set on battery saving, but I have tried various settings and that doesn't seem to make any difference. I'd be happy to look at source to see if I can find the problem but am not sure where to find it (or even if its available). Any ideas?
[Nook HD, HD+ Android Development] lukychmz:
Guys I need some help here, flashed cm12 and when starting up I cant get wifi to turn on. I removed the folder /data/misc/wifi and reflashed rom, removed it again restarted but nothing seems to work. Am I just missing something? :confused:
[Nook HD, HD+ Android Development] w1ll1m:
Have you got a link for the hummingbird? the link is for ovation.
[Nook HD, HD+ Android Development] mhunt13:
Did you flash an appropriate gapps, too. If not, there are likely missing google pieces.

Link to gapps can be found in first post, be sure to get latest 5.0.x version.
[Nook HD, HD+ Android Development] twiztid_:
Sorry about that.

From what i read, I think you grab the omnirom twrp from the link below, and flash with flashify. I can't say if it has F2FS or not though.

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww
[Nook HD, HD+ Android Development] mhunt13:
I used the TWRP files referenced in post #502 on page 51 of this thread. It supports f2fs for the data partition.

My path:

- complete TWRP backup

- reformat data as f2fs

- restore only data partition (got warning about restoring from ext4 backup, but appears that it worked)

- wipe cache/dalvik (maybe unnecessary)

- reboot system

No issues so far, seems slightly more responsive.
[Nook HD, HD+ Android Development] twiztid_:
You don't need gapps for WiFi.

You don't need gapps period, it just makes things easier, like using the appstore.
[Nook HD, HD+ Android Development] w1ll1m:
So flashed the latest builds of twrp, 2.8.6, and cm12, 26.3.15.

I have 2 main issues:

the brightness is not adjustable

the screen keeps flashing.

Will twrp automatically format to f2fs? Or do i have to do it manually? If so, how?

If there's nay fixes to my issues, that would be helpful. If not, well that's the price of testing.

thanks
[Nook HD, HD+ Android Development] belfastraven:
For me (hummingbird) brightness is adjustable. Have you checked display settings? Also, I often get flashing for the first five minutes or so after installing a rom. If I leave the device plugged in for five minutes without using it, the flashing will stop . I leave it plugged in since the flashing drains the battery a bit.

You need to format to f2fs "manually". In the 2.8.6 twrp recovery, you can do it through "wipe", then "advanced wipe" which gives you the chance to reformat and/or change file structure. You just want to do this for data. Make sure you have a backup of data. I was able to restore the backup once I data was reformatted.
[Nook HD, HD+ Android Development] w1ll1m:
Both issues seem to have resolved after a reboot. So that is a relief.

And it looks like the data was set to f2fs.

So the problems i had, were not problems at all.

Thanks for clarifying
[Nook HD, HD+ Android Development] lukychmz:
I think that was the problem, everything seems to be working great now, thank you :good:
[Nook HD, HD+ Android Development] rnaodm:
Tried to flash this rom on my hummingbird nook hd, it installed but while setting up, processes in the background repeatedly crashed to the point where I couldn't further the install, I wiped data/cache/dalvik installed a cm11 build via adb and now my tablet is trapped in a boot into recovery mode loop.

Never came across this problem, usually it would just boot and hang on a loop if the rom install failed. Anyone know how to fix this? Should I run one of those zips that uninstalls cwm? I'm hesitant to do that as if that doesn't work would I essentially end up with a brick?
[Nook HD, HD+ Android Development] leapinlar:
I don't know how you installed a CM build via ADB. Or do you mean you copied the zip file to the tablet with ADB? As far as I know there is no way to install a ROM via ADB.

In any case, the way to fix the device is to go to my HD/HD+ CWM thread linked in my signature and make a new CWM SD per item 1a there and use that to flash a plain stock zip from item 6. Follow that with a factory reset with CWM and your device should boot normally to stock and you can start over.
[Nook HD, HD+ Android Development] w1ll1m:
The latest build works splendidly. Will give it a good run over the weekend
[Nook HD, HD+ Android Development] rnaodm:
I used adb to transfer the file to the tablet, Thank you for your help I will do that.
[Nook HD, HD+ Android Development] spazmochad:
I would put my money on you having flashed the wrong GAPPS zip - I just did the same, downloading the gapps-lp version now, betting that was my mistake
[Nook HD, HD+ Android Development] Dread This Day:
[MENTION=4473900]amaces[/MENTION] are your builds set up for screen casting to Chromecast? Checking because it is not at all working for me no matter what I do or which version of Mirror Enabler I try.

Running your latest build.
[Nook HD, HD+ Android Development] amaces:
My builds differ from CM repos only in very minor respects, a few kernel patches, but nothing touching screen casting. Our device-specific repos haven't charged since February 17, so if it didn't work in [MENTION=4243514]Hashcode[/MENTION]'s last build, no hope with mine… I'm only now looking into the Hangouts issue, plus making a functional 5.1 ROM from the craziness that is staging/cm-12.1 ;) Just checked, and although the "Cast screen" tile show up, my Chromecast is not found. Did it ever work on CM11?
[Nook HD, HD+ Android Development] Dread This Day:
I had it work on CM11 after using the MirrorEnabler app. This is from the MirrorEnabler thread:

For those STILL having issues,

Check /system/lib/hw directory for the file "audio.r_submix.default.so".

If it doesn't exist, ask your device maintainer to add audio.r_submix.default to

the product_packages in the device.mk file. (You may not know what it means, but they will.)

EXAMPLE (Thanks, [MENTION=3900214]runandhide05[/MENTION]!):

http://review.teameos.org/#/c/389/

---------- Post added at 10:03 PM ---------- Previous post was at 09:11 PM ----------

My Chromecast is found, but every and any time I try to screen cast, my TV screen will go blank as my Nook is trying to cast, then a toast notification of "Screen casting has ended" and back to the Chromecast backdrop. Same as what I got on CM11 before using MirrorEnabler on it.
[Nook HD, HD+ Android Development] amaces:
That library is already added in common.mk (sourced by both ovation and hummingbird). The problem may be in audio_policy.conf, also common to both devices. I've added the extra configuration based on this information, and should have new builds later today. Unfortunately, they will be based on the currently unstable code in CM 12.1 staging, which have a couple of weird bugs.

Honestly, you don't need to wait for a full ROM. I'm assuming you could edit your /etc/audio_policy.conf as shown in this patch, then reboot.
[Nook HD, HD+ Android Development] Dread This Day:
Strange, maybe I'm doing something wrong but adding the patch gives me the same result. Not really a big deal, more of an added bonus feature. I'll try the new build and see if it works.
[Nook HD, HD+ Android Development] belfastraven:
amaces,

[QUOTE... Unfortunately, they will be based on the currently unstable code in CM 12.1 staging, which have a couple of weird bugs.

...[/QUOTE]

Since i really really really wanted to try a 5.1 rom, I downloaded your test Hummingbird rom. I tried to flash it first with Flashify and then by booting into recovery (TWRP 2.8.6.0)anad installing. . I got the installed successfully message but the rom stayed stuck in the boot animation. I left it there for 20 minutes.. No problem, I'm back on your previous build ,but wondered whether I needed to do something special to install... I'm happy to test.

I've found a few 5.1 gapps; do you have a preferred one?

Thanks again.
[Nook HD, HD+ Android Development] amaces:
Ha-ha, you found it early ;) Tomorrow morning, I was planning to post in more detail about the current compilation issues and new runtime bugs. Things work fairly well on the HD+, while hummingbird is completely untested, although both built from the same snapshot. Since [MENTION=2777334]TKruzze[/MENTION] quit, I've been using this GApps package: http://fitsnugly.euroskank.com/?rom=banks&device=gapps. Of course, you'd need a good wipe, maybe including /system (in case you have stubborn backup scripts).

If things still don't work, do let me know. Hopefully, it has nothing to do with my changes to support F2FS on /cache (ext4 should still work, at least it does here).
[Nook HD, HD+ Android Development] king200:
I'm reading that just a dirty data flash over 5.02 and system format is not going to work?

My data partition is already f2fs. Is reformatting cache partition to f2fs necessary? It's easy to do but I worry about restoring previous backups.
[Nook HD, HD+ Android Development] amaces:
Flashing over CM12 could work, although definitely install 5.1-based GApps. I was switching from a customized "stock" GApps to a minimal one, so wiping /system seemed like a good idea. Still, /data could be left untouched, but he had issues with a build that I cannot test, so full wipe is the first advice.

You don't need to reformat anything; the changes I made were to support F2FS /cache (in addition to /data). Someone needed it, but it shouldn't affect ext4 partitions.
[Nook HD, HD+ Android Development] belfastraven:
I'll give it a try later today and let you know.

I'll reformat cache f2fs and wipe cache ,dalvik cache, data and system.

OK! rom and gaps are now installed. (I k ow that flashify ust uses recovery but I can see better what is going on when I do it myself. Normally, with nightlies I use the cm update process, otherwise Flashify.

So far, "Sound" in Settings broken for me; it forces settings to close. The tablet IS playing sounds however, as far as I've tested it.Google chrome indeed won't run (gives the you may not have right version etc. message). I use this device mostly for emailo, web, reference apps (e.g. ibird or audubon mammals) and reading (through google and amazon). Everything else I've tested so far seems to be working, except for google maps, which I wasn't expecting to work.

Thanks again for all your work on this.
[Nook HD, HD+ Android Development] amaces:
By the way [MENTION=5672278]belfastraven[/MENTION], Flashify-ing the ROM just submits a script to the recovery, so results should be identical. The benefit with installing in recovery is that you have more time to see eventual warning/error messages, and definitely have more control over debug logs. Otherwise, changing /cache shouldn't be required, and is probably not the culprit (tested on ovation, boots with either F2FS, or ext4).
[Nook HD, HD+ Android Development] king200:
I did not have luck in with a flash over 5.0.2. I tried both cache/Ext4 and cache/f2fs. A complete wipe and the rom came up. I went back and restored just the data from the Nandroid and the rom did not come up.

If is the direction we are headed, I'll to a reinstall of apps and data and continue to play.
[Nook HD, HD+ Android Development] amaces:
You're talking about hummingbird, right? Does the boot animation at least come up?
[Nook HD, HD+ Android Development] king200:
Ovation. Yes the boot animation comes up.
[Nook HD, HD+ Android Development] amaces:
Odd, that's the one I fully tested, and currently running. The first boot does take a bit longer (maybe 10-15 minutes).
[Nook HD, HD+ Android Development] king200:
It came up fine with a clean install. I waited a long time and nothing except the boot animation when I tried the dirty flash.

I'll go back and give it ½ hour later and see what happens.
[Nook HD, HD+ Android Development] belfastraven:
amaces, that was the same for me on hummingbird. I initially just cleared cache and dalvik and got stuck on boot animation. After wiping data and system also, the system booted.
[Nook HD, HD+ Android Development] aoleary:
Hi Amaces.

I installed your ROM from 24.03 with TWRP 2.8.6, but it says its not rooted.

I tried reflashing SupserSU-2.4.6, but its still un-rooted.

Ideas?
[Nook HD, HD+ Android Development] toplist:
Try changing Root Access in Developer options to Apps Only. I had the same problem with amaces cm12.1 build and it solved the problem.
[Nook HD, HD+ Android Development] amaces:
I had the same issue on stock LMY47I hammerhead (but not LMY47D). TWRP will usually catch it, and prompt you just after pressing reboot. Either way, if SuperSU asks you to update the binary, choose the recovery method for now. Check the official thread for reports and solutions (not a deal breaker yet, but something they'll fix soon, I'm sure).
[Nook HD, HD+ Android Development] Dread This Day:
On [MENTION=4473900]amaces[/MENTION] 5.1 Hummingbird build, as you know, Chrome browser will not work. Restored a backup of Chrome from 5.0 build, same error. Tried Chrome Beta, it force closes. Tried Firefox, crashes every time I try to start it. Stock browser seems to work fine. Recent apps menu has a section at the top that is grayed out and says "Couldn't add widget". Everything else seems to be working alright.

Edit: This build is very finnicky. On one flash, touch to talk was enabled on boot. On another flash, both of these fresh, WiFi was nonexistent even after deleting the necessary files and rebooting. And finally, after some combination I cannot even remember, the recent apps menu glitch is gone. Have tried various fixes for Chrome browser, clearing it's data/cache, uninstalling updates to the play store, changing the build.prop build ID, to no avail.
[Nook HD, HD+ Android Development] aoleary:
Thx toplist.

That worked perfectly :)