yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Tschumi:
Tried the latest 5.1 for ovation. I had to wipe and start a fresh install (dirty over the 5.0.1 didn't work).

I think it works better than the previous build, a bit more fluid. no major bugs so far.
[Nook HD, HD+ Android Development] amaces:
LP 5.1 Update, Promising News on the Kernel Front (3.4)

As people quickly discovered, I uploaded early CM12.1 builds for both hummingbird and ovation. They live in the "LP5.1|CM12.1: Chrome broken, other assorted bugs!!!" folder for now, and are rougher than usual as the name implies. Since there is at least one successful report for each device flavor, I will leave them up till better ones happen.

It's been more or less possible to build staging/cm-12.1 for a week, yet bionic is still broken for our devices, and all Cortex-A9 based ones. I uploaded this fix, my very first Gerrit commit ;) and it shouldn't be long till a hassle-free build is possible (anyone can repopick 92634 till then).

For now, it seems that wiping /data is needed, and even then one major bug remains: Chrome and a few other browsers report missing functionality, and crash. This may be related to the SSL changes in CM12 vs AOSP, but either way, should be sorted soon, definitely by the time staging graduates to regular cm-12.1. Other than that, minor annoyances abound: installing local APKs appears to fail with an error message, despite them being installed actually, some UI strings overflow/overlap, etc.

You can keep an eye on what's being merged/fixed here, plus upcoming commits to cherry pick here. By the way, [MENTION=5720705]twiztid_[/MENTION], since we're already making all these changes, I've added F2FS support for /cache (ext4 still works, of course). These commits (92658 & 92659) will probably not be merged anytime soon, but they're available to repopick.

About the few longstanding bugs that remain, notably screen casting, and the Hangouts Dialer crash, I think progress can be made, but haven't been able to pinpoint the exact cause. I've added what appeared to be missing configuration for screen Chromecast-ing, but that may not be enough.

Tha Hangouts bug is even more problematic, since we do seem to have all the right pieces. I'm hoping it's somehow due to CM12, and not to our audio or kernel config. After the split into common plus device-specific kernel config, it's harder to compare to CM11 configs, but I think all the relevant symbols are still there. The actual kernel code for sound is definitely the same, so I'm thinking that this common XML, or the files in here are responsible.

Finally, the most exciting news for me is that [MENTION=4243514]Hashcode[/MENTION] is making progress with the 3.4 kernel. I've been trying intermittently to build it, and while the kernel portion compiles, all the extra stuff in hardware/ti/omap4 does not. I knew it has to do with the ION headers, and then I stumbled upon this open commit. Hopefully a kernel can be build now, then there's the whole pesky business of booting it… Still, it must be close, especially that we don't have to worry about camera support in TIs proprietary binaries. If we can make these devices flicker free, avoid those dreaded underflows, and generally run as well as grouper on current stock, I'll be happy.
[Nook HD, HD+ Android Development] Dread This Day:
Ohh, also, screen casting on the 5.1 build is closer than before but still broken. It will say it's screen casting, TV screen will go black, and that's it. No "screen casting to xxxxxx has ended" error. All in all not a bad build. Seems snappier overall. Also seems to handle memory a bit better. I've noticed that lollipop on our devices likes to kill background services, Facebook messenger is a big one. That happens less in this build. Thank you [MENTION=4473900]amaces[/MENTION] .
[Nook HD, HD+ Android Development] Tschumi:
regarding backrground apps, anyone knows the best performance settings in order to keep an app running in the background? I use mantano reader a lot and it always seem to unload, even when I open a pic in quickpic.
[Nook HD, HD+ Android Development] amaces:
You could turn on KSM, and increase the size of the zRAM disk, if you can live with the occasional sluggishness. I have this in my /data/local/userinit.sh:

#!/system/bin/sh

echo 100 > /sys/kernel/mm/ksm/pages_to_scan
echo 500 > /sys/kernel/mm/ksm/sleep_millisecs
echo 1 > /sys/kernel/mm/ksm/run

swapoff /dev/block/zram0
#umount /dev/block/zram0
echo 1 > /sys/block/zram0/reset
echo $((128*1024*1024)) > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0

It should be snappier even at this point, just based on the generic changes in AOSP's memory management. Still, more optimizations happen in our device configs, which were last tuned for LP 5.0/CM12.0. About screen casting, that kind of progress may be indicative of issues with the underlying audio/video plumbing :( It's even possible that the Hangouts issues and Chromecast are connected. Haven't invested enough time on this, as I keep hoping a 3.4 kernel will fix a bunch of things. As of now, based on that open commit and a few other changes, I can finally compile a 3.4 boot.img, alas it needs the new ION libraries in the ROM. We'll see if it boots at all.
[Nook HD, HD+ Android Development] webdroidmt:
Kudos for your contributions with LP and up-to-date TWRP on these devices. You seem to have come out of nowhere LOL and made excellent progress, thanks for that! :)

Like you, I'm most excited at the prospect of a 3.4 kernel. As for LP, I was on each 5.0 version and I did try your latest 5.1 version but decided to go back to 4.4.4 for now. I really like the LP experience but although 5.1 felt "tighter" all around for me as opposed to 5.0.2, my 4.4.4 build of Liquidsmooth has just been super stable for me on the Nook HD+.

Aside from some of the known minor annoyances with LP, the big one for me has been the Nook rebooting instead of shutting down when selecting power off. Many times it will take at least 3 times to shut down, unless I just hard power off by long holding the power button. I'm not sure if it's related to a memory issue, or a kernel panic but that's another reason why I'm looking forward to the possibility of a 3.4 kernel.

Anyway, I'll be back to LP when it matures a little more on this device and thanks again for sharing your work.

Mike T
[Nook HD, HD+ Android Development] twiztid_:
I did notice, thank you so much, and I quickly installed it as soon as I had some time.

I wasn't able to play around with it too much, but I'm really appreciative, and excited to give it more testing as soon as I can!

I did notice the flickering is worse (pulldown menu) than your latest 5.0, but disabling h/w overlays quickly fixed it.

Thank you so much for adding that, and thank you (and everyone who has worked on this) more for all your hard work. I cannot thank all of you enough.
[Nook HD, HD+ Android Development] Frenchdroid:
Apologies - but could someone lend a hand please

I tried but failed at reading this thread each day, so I'm wondering if I can go ahead and put this on my wifes Nook HD+ (she has been running 10.1.3 which has just stopped working and can't be restored in recovery). Her Nook is mainly used for web browsing via Chrome, and that's about it really aside from the occasional streaming via Chromecast.

So, with this CM12, could someone tell me if the rom on the front page is best or has one of you whizzkids modified it ? And is there a recommended recovery I should use too ?

Thanks very much in advance
[Nook HD, HD+ Android Development] twiztid_:
You can try the builds here: http://xdaforums.com/nook-hd/development/rom-unofficial-cm12-0-nookhd-lp-5-0-x-t2993613/post59400283

You may have to disable the Hardware Overlays in developer options (Settings -> About Tablet -> tap Build Number) and possibly install an alternate keyboard like what is linked in the post to avoid flickering with the keyboard/chrome. But honestly, I really like the stock browser and does support bookmark sync (you may have to search for the 4.4.4/5.0 bookmark sync adapter).
[Nook HD, HD+ Android Development] Frenchdroid:
Thanks for the advice Twitzid - I may install it on my Nook too.
[Nook HD, HD+ Android Development] keshabbhattarai126:
[MENTION=4473900]amaces[/MENTION] Could you show me the link for your latest hummingbird build based on 5.1.

And also the flashing method.
[Nook HD, HD+ Android Development] aoleary:
Read two posts above you own post...
[Nook HD, HD+ Android Development] amaces:
Well, you're in luck as I generated new CM12.1 builds last night. Chrome, other third-party browsers are OK now, and since these builds approach the stability of CM12.0, I moved them to the respective device folders in here (thanks, [MENTION=4956374]theKramer[/MENTION]).
[Nook HD, HD+ Android Development] belfastraven:
4/01 12.1 rom seems even more responsive! (on Hummingbird)

"sounds" in settings still forces settings to stop, however.
[Nook HD, HD+ Android Development] Dread This Day:
Can confirm, on Hummingbird selecting sound settings causes a force close in settings. But, Chrome works, and so far, light testing, seems decent.
[Nook HD, HD+ Android Development] king200:
Sounds FC with Ovation as well.

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

I thought I looked well and I could not find the Shortcut for SuperSu. That could be that I dirty flashed over 5.0.2.

In any event, I flashed the SuperSu.zip and got the shortcut in the App drawer.
[Nook HD, HD+ Android Development] norm883:
So F2FS can be utilized on cache and data?

norm883
[Nook HD, HD+ Android Development] vinceweis:
Maybe I just never paid attention before, but after installing this on ovation and it goes through the Android is upgrading, it says Android powered by Microsoft with their logo in front. What is Microsoft's part in this? (I happen to be a Microsoft fan)
[Nook HD, HD+ Android Development] Dread This Day:
Nothing more than an April Fools joke.
[Nook HD, HD+ Android Development] vinceweis:
Funny. Thanks. It got me.
[Nook HD, HD+ Android Development] norm883:
Microsoft

Microsoft is reportedly taking part in a $70 million investment round in CyanogenMod, an Android ROM creator that is one of the most popular alternative versions of Android.

Could this be a first?

norm883
[Nook HD, HD+ Android Development] Dread This Day:
No. Just a joke. http://www.androidpolice.com/2015/0...uilds-are-powered-by-microsoft-for-april-1st/
[Nook HD, HD+ Android Development] twiztid_:
Yes. You can flash the TWRP builds in amaces shared folder to format /data and /cache to F2FS, but bear in mind CHANGING THE FILESYSTEM WILL WIPE EVERYTHING IN THE PARTITION!
[Nook HD, HD+ Android Development] aoleary:
Installed Amaces's 12.1 last night. Definitely seems a bit snappier.

Havent done any extensive testing yet though...
[Nook HD, HD+ Android Development] asakurato:
Also installed amace's latest 12.1 build. This build also have heavy flickering problems as many previous builds and as a result, it rebooted. But after that reboot, it no longer have the flickering when pulling down notifications in landscape mod :fingers-crossed: Now I'll test FB messenger(the app in which I had the most flickers).

P.S. That windows logo on app drawer icon :laugh:
[Nook HD, HD+ Android Development] keshabbhattarai126:
I am thinking of flashing amaces cm12.1 but one thing is striking in my head. Is it true that disabling Hardware Overlays might affect 3D games ?? or not???
[Nook HD, HD+ Android Development] asakurato:
You may not need to disable Hardware Overlays at all, as there is no flickering (I need further testing).

Noob question: How do I flash twrp recovery .img file without android sdk and such?

Tapping sounds in settings results in FC.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Use Flashify to flash that image file

https://play.google.com/store/apps/details?id=com.cgollner.flashify
[Nook HD, HD+ Android Development] aoleary:
Searching for the term "Hardware Overlays" in the search for this thread seems to suggest that its not a good idea. See post #609.
[Nook HD, HD+ Android Development] asakurato:
Ok, the flickers are less, but still present if FB messenger. Previously, when I just used it alone(with chat head), it was flickering and rebooting. But now, when on home screen, chat heads work fine, but if I open any other apps, flickering starts again.
[Nook HD, HD+ Android Development] norm883:
TWRP

Anyone know why TWRP would not see my Micro SD card in recovery to flash zip?

Used the newest TWRP with Flashify.

norm883
[Nook HD, HD+ Android Development] belfastraven:
Did you boot the tablet with the sdcard in it? It may not work if you insert the card after you have booted.... Someone has reported that problem before on Nook Tablet forum, I think.
[Nook HD, HD+ Android Development] aoleary:
I had this issue before. I didnt do anything special. I think after a reboot or two it finally recognised it.
[Nook HD, HD+ Android Development] norm883:
Omni Twrp, FYI

OK I reformatted the Micro SD to exFAT. Then loaded my zip files etc. onto it.

Once in the Omni TWRP recovery you need to touch the top line to switch between internal and external card and touch then the bubble to open Micro SD.

Was on same ROM prior but no F2FS.

Reformatted cache and data to F2FS. Then installed the 04/01/15 ROM zip and SU.

Loaded well takes a long time to boot with blue android guy!

Once running many apps need updating.

Thank you for your hard work.

norm883
[Nook HD, HD+ Android Development] Tschumi:
I am using the 1/4 image for ovation. So far I think it's one of the most fluid roms I've tried.

Also the crashing when installing apps outside the Play Store bug seems fixed.
[Nook HD, HD+ Android Development] twiztid_:
Keyboard flickering, force crashing and reboots vs. minor animation slowdowns? Not a hard choice in my book.

Yes, fixing the root problem will be the best, but until then disabling Hardware Overlays isn't all that bad.
[Nook HD, HD+ Android Development] arh2o:
Lol Amaces 4/1 build has a Microsoft logo as the drawer launcher. Fail, it was a Cyanogenmod joke for april fools haha
[Nook HD, HD+ Android Development] twiztid_:
Is there a way to increase the sensitivity/reduce the length you need to swipe down to pull the menu down completely?

If I swipe from the very top edge, it only shows one (Cast screen) and a half (Airplane mode, Auto-rotate, Location) rows of icons. I have to swipe down to show the Notifications, then swipe down from the very top again to show icons.
[Nook HD, HD+ Android Development] amaces:
So, CM12.1 graduated from staging a few days ago, but it'll probably be weeks before things stabilize. Compared to their initial assessment of a very easy transition, with official nightlies within a week of LP5.1 release, the reality hasn't been quite as smooth. Because they ended up rebasing a lot of the previous CM12 code, in theory at least, this version should be cleaner.

About the previous Chrome/Firefox/Opera bug, turns out that it wasn't really CM12.1's fault, but rather due to how we fixed bionic/stpcpy on Cortex-A9. Apparently, all these browsers make use of the non-standard bcopy, which had been discarded in the process.

Settings > Sounds FCing happens on ovation as well, and given that volume still works fine, I'm hoping this one is a minor bug introduced during the bumpy transition. Haven't seen any fixes merged, or upcoming.

I think actual 3D-accelerated surfaces don't use the same compositor, so hardware overlays shouldn't affect those games.

I was happy to discover that writing directly (e.g., dd) to /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery works equally well, when you've run out of options (plus, /dev/block/platform/omap/omap_hsmmc.1/by-name/boot for kernel flashing).

Yeah, even after reading a couple of articles about it that day, it only dawned on me when I flashed the build. Good fun, all in all ;)

Could be wrong, but I thought encryption was broken as far back as CM11. We do have support for it in fstab and recovery, so not sure what the root cause is. Still, it's probably not a good idea on these tablets, performance-wise.

The screen flickering bug has been discussed many times here (search for GFX/buffer underflows), and there isn't a trivial fix. It's been my initial impetus for these builds, and am hopeful that the next generation kernel and binaries will finally get rid of them.

On the 3.4 kernel note, we're still not there. I spent many hours trying to boot it on ovation. Although the whole kernel/ION/PVR finally compiles, I end up in a boot loop no matter what I do. Now, [MENTION=4243514]Hashcode[/MENTION] is still working on it, but his testing happens on OMAP4430 I think, while we have 4470s. There are a gazillion build options that could be the culprit, and I played forensics with diffconfig to no avail, so I'm giving it a break for a bit.

I guess things were happening faster than I was willing to wait… It took a long time for the Nook HD+ to grow on me, but once it did, making it run well has been a fun project so far. Hopefully, the excitement lasts at least till official nightlies start again. Otherwise, sharing is quasi-free ;)
[Nook HD, HD+ Android Development] derproblembaer:
Thank you. I like your builds very much.

Can you make a CM12 build with F2FS support? It would ease the process of switching between CM12 and 12.1.
[Nook HD, HD+ Android Development] Zippy Dufus:
Do you have any more patches outside of the HD+ device and kernel repos that you can share?

Your last batch are working great and your post here is my cue to do a new build.

And many thanks for all your efforts!
[Nook HD, HD+ Android Development] asakurato:
Yes sound works fine, but the thing is that i can't disable keyboard sound, which irritates me :D Waiting for 3.4 kernel, hope it will fix flickering.
[Nook HD, HD+ Android Development] twiztid_:
[MENTION=4473900]amaces[/MENTION] already did this, and made a post about it.

You can download his version, which he seems to be keeping updated, from pretty much all of the Most Thanked - Recent pane on the right in this thread.

[MENTION=4473900]amaces[/MENTION], sorry to bother you again with a request (its really your fault for being so awesome :p), but is there any way you could fix the TWRP problem that it doesn't have unzip support? If not, no big deal, I'm sure it will get fixed with the next version. Apparently its a common issue with the latest version, I'm hoping its just a matter of a lib not being included as its being compiled.

http://xdaforums.com/showpost.php?p=59888907&postcount=8

Thanks a million times over.
[Nook HD, HD+ Android Development] derproblembaer:
The switch for keyboard sounds is not in the sound settings. Look under "Language & Input" instead.

Really? His CM12 build does not boot on my device using F2FS for /data and /cache while CM12.1 does.
[Nook HD, HD+ Android Development] twiztid_:
Whoops, you're right. I thought amaces latest 12.0 had the f2fs as well, but his post that mentioned adding f2fs was just about 12.1. Sorry about that.
[Nook HD, HD+ Android Development] amaces:
So far, lots of git stashes, but can't say that anything that I tried lately makes a noticeable improvement. While trying to merge some of [MENTION=3654172]verygreen[/MENTION]'s CM11 defconfigs into the new common/variant framework, I played with these symbols:

# Extra/test symbols
CONFIG_CRYPTO_AES_ARM=y
CONFIG_CRYPTO_AES_ARM_BS=y
CONFIG_CRYPTO_SHA1_ARM=y
CONFIG_CRYPTO_SHA1_ARM_NEON=y
CONFIG_DMA_SHARED_BUFFER=y
#CONFIG_FB_OMAP2_NUM_FBS=1
CONFIG_SYNC=y
CONFIG_SW_SYNC=y
#CONFIG_F2FS_CHECK_FS=y
#CONFIG_OMAP4_DPLL_CASCADING=y
#CONFIG_TWL4030_POWER=y
#CONFIG_MMC_OMAP=y
#CONFIG_SLUB=y
#CONFIG_FIQ_GLUE=y

Basically, I have this block appended to android_omap4_defconfig (commented symbols resulted in aborted builds or boot loops). What I thought might make a real difference was replacing SLAB with SLUB, alas the old 3.0.31 kernel is pretty different from current 3.0.72.

Interesting, wasn't aware of the missing binaries. I wonder if it's due to changes with TWRP's handling of static binaries. What I did notice is that compiling TWRP with 5.1 repos results in weird touchscreen issues right now. As a temporary fix, I put back the 2.8.5 recoveries in their respective folders.

Officially, F2FS is only supported on /data, but I added it for /cache as well starting with CM12.1. The older CM12.0 builds won't know what to with F2FS /cache, and unfortunately, those end-of-March ROMs are the last.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Its unofficial build, I know all things don't go perfectly fine within short period of time.

None of the screen recording apps work. I tried Rec, AZ Screen Recorder and SCR Screen recorder in cm12 and cm12.1

It worked fine on cm11.
[Nook HD, HD+ Android Development] Monfro:
Amaces new Ovation build dated 04.04.2015 works really well here.

Thank you for all the great work you are doing for this device and this community!!
[Nook HD, HD+ Android Development] andtron:
I finally got my own build to compile successfully but sadly the wifi is not working, any builder here has any experience on how to fix it?

TIA
[Nook HD, HD+ Android Development] Zippy Dufus:
My guess is that you may have missed including the proprietary firmware. Check the file size of your ROM. I built one last night and it is:

228771704 Apr 3 17:31 cm-12-20150403-UNOFFICIAL-ovation.zip​

If yours is megabytes smaller, then this is your problem.

Also, the excerpt from my build script to set up the local manifest is below. Note TheMuppets repo is where I get the firmware.

# Set up local manifest

rm -f $CROOT/.repo/local_manifest.xml

echo '<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="CyanogenMod/android_device_bn_ovation" path="device/bn/ovation" remote="github" />

<project name="CyanogenMod/android_device_bn_common" path="device/bn/common" remote="github" />

<project name="CyanogenMod/android_kernel_bn_omap" path="kernel/bn/omap" remote="github" />

<project name="TheMuppets/proprietary_vendor_bn" path="vendor/bn" remote="github" />

</manifest>' > $CROOT/.repo/local_manifest.xml​
[Nook HD, HD+ Android Development] tebra:
I installed CM12.1 build 20150404 on my hummingbird without wiping data partition and everything works fine. Thanks for the hard work
[Nook HD, HD+ Android Development] andtron:
Thanks Zippy.

I tried that and still having no lucks, the wifi just won't (or trying to) start.
[Nook HD, HD+ Android Development] tj2003:
Screen casting on the CM12.1 build is partially working. On chromecast I get sound but the screen just goes black.

My FireTv stick gives me a picture but sound stays on the Nook HD+.
[Nook HD, HD+ Android Development] asakurato:
Latest build fixed ui overlays in notification area :good:

Sent from my C6603
[Nook HD, HD+ Android Development] Dread This Day:
[MENTION=4473900]amaces[/MENTION] have you seen anything about moving apps to SD? Still broken, when I try it says there isn't enough space to. Folder Mount helps, but not enough.

Edit: that error was on all builds prior to the April 4th 5.1 build. On the April 4th 5.1 build, when I hit move to SD card, sometimes literally nothing happens. Other times, it gives me the error.
[Nook HD, HD+ Android Development] agantai:
found it
[Nook HD, HD+ Android Development] robak1965:
Are you able to save/write anything to the external sd, or it is it just moving apps to sd that's not working?

If you can't write anything to ext sd then sounds like your platform.xml is not set for it. I would take a look at it. You can try SDfix app or edit it yourself.

1. Using a root-enabled file manager, navigate to /system/etc/permissions

2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.

3. Add an additional group definition for this permission: <group gid=”media_rw” />

4. Save the changes to the file.

5. Reboot
[Nook HD, HD+ Android Development] Dread This Day:
I can write to external SD, just can't move apps to it. Thank you for the reply though.
[Nook HD, HD+ Android Development] keshabbhattarai126:
Is this right way to install twrp and cm12.1??

https://www.youtube.com/watch?v=UgdRdcmDH58