yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] amaces:
Good point, although moving the first-time calibration functionality from ROM to recovery seems fraught with other issues. People change recoveries, or may attempt to dd the eMMC partition images directly (say, from verygreen's external SD recovery). Also, we need to find a permanent/longterm solution given that SELinux Enforcing will trickle to recovery as well. TWRP is already tightening up the noose: https://github.com/omnirom/android_bootable_recovery/commit/eb32b1ff00878e7b01453450fcd04ecb9fcbba52.

No biggie though, we can continue with Permissive for a while longer, as I did with today's builds.
[Nook HD, HD+ Android Development] bluecopper:
Thank you. What i ended up doing earlier this evening was flashing the previous test boot img and then reflashed the 0615
[Nook HD, HD+ Android Development] belfastraven:
I've updated to the 6/22 hummingbird build from the 6/15 with the Enforcing boot image.. In order to do so, I had to get into recovery with power key-nook key combination--the reboot into recovery from the power off menu and/or from flashify would not work. Everything running fine. Maps location is working I am not running GApps. I found that after the basic roms started including play store, I didn't need GApps anymore. It seems that if an app needs a later version of a google process, it will ask you to download it,btw.

Glad we might be getting nightlies "soon".

Thanks again
[Nook HD, HD+ Android Development] dully79:
Couple of quick questions as search was unfruitful.

Does this contain CM theme engine and does it work fully?

Is this possible to be installed onto sdcard?

Is there a list of what does and doesn't work?

Regards.
[Nook HD, HD+ Android Development] amaces:
TWRP 2.8.7 Early Builds

Now that TWRP 2.8.7.0 is officially released, I figured it's time for some updates. The changelog doesn't have many goodies for us (unless you're one of the very rare folks who use encryption on these devices). Beyond what's included in the official changelog, I have a couple of updates of my own:

The recovery is now built on the same 3.0.101 kernel sources in my g-3.0 branch, the same currently used for the ROM. This change should make almost zero difference in normal use.

For the past month or so, I've been using [MENTION=2719389]z31s1g[/MENTION]'s wonderful landscape theme on my ovation. Since I believe it'll become the TWRP default in the near future, I compiled the 2.8.7 recoveries with this more modern theme built-in, but I can reverse this change based on popular feedback.

Because we're talking about recovery, and I can only test for HD+, hummingbird's new TWRP lives in experimental until enough people confirm that it works properly.

Wait, CM ROMs haven't had any trace of Google proprietary apps (e.g., Play Store or Services) in years now. You mean that you had installed a GApps package at some point in the past, and its backup script in addon.d made them linger across upgrades, right? If you wipe /system with a factory reset, there should be zero trace of Google services, and only the few AOSP counterparts.

Since the ROM side is pretty much upstream CM12.1, you get the full benefit of that theming engine. I'm pretty sure that it works, although I avoid using any custom theme on this already underpowered device. About SD card install, do you mean moving apps to external storage, or actually running the ROM off a micro SD? The former is possible, while the latter is currently not supported (eMMC-only images; to my knowledge, last micro SD ones are in verygreen's CM11 thread). Finally, this is not a stable ROM, and the assumption is that you'll have read Hashcode's initial CM12.0 thread, as well as at least the few initial posts in this one. That's enough information to give you a good idea what to expect.
[Nook HD, HD+ Android Development] prsa01:
6/22 build crashes my keyboards

On my ovation device all of the keyboards crash with "unfortunately ... has stopped responding". This is with hackers, aosp, & swiftkey. This is with or without hw overlays disabled and in lightning browser attempting to login to gmail.

I know this same config worked fine without disabling hw overlays on the 6/15 build.

For feedback pur[oses only. Not a complaint. I can go back to 6/15 easy enough but if there is anything else you would like me to try, let me know.

I did flash in TWRP, then wiped cache & dalvik, which is what i have done on all other updates. As always, thanks much for your work on this!
[Nook HD, HD+ Android Development] belfastraven:
New recovery seems to work fine on hummingbird, but I haven't tested every possible branch, of course. I do see a new theme, by the way, but it is still portrait orientation on hummingbird, which is fine with me.

Actually, that is why I was a bit surprised . All other google apps had disappeared (I didn't check running processes), and I thought I had wiped system as well as doing a factory reset (I was expected to have to reflash GApps). Play Store was the only carry over-no gmail, google, I had only noticed this in June...but I am probably forgetting something I did or didn't do...
[Nook HD, HD+ Android Development] amaces:
With that consistent behavior across different keyboards, my guess is that something got corrupted during the upgrade (maybe during the app optimization step?). Do you have enough (5-10 MB at least) free space in /system? I had the same update path as you, and nothing like that happens here. Maybe force another cache rebuild (by wiping Dalvik/cache again), and if that doesn't work, a full wipe/clean install would be my next guess. Filesystem corruption does happen occasionally; never happened to me, but this is the second report that I recall about unexplainable issues after an update.

Awesome, if the display and touchscreen work like before with the new hummingbird TWRP, the rest is most likely OK as well; moving it out of experimental. The theme is supposed to remain in portrait mode on that device. When you have a chance, could you attach a few screen captures (TWRP can do it apparently, or maybe just regular pictures)? I'm curious how well does the new theme work in portrait mode on the HD.
[Nook HD, HD+ Android Development] belfastraven:
I'vew attached a zip file with a few screen captures. The only difference I've noticed in operation is that I only need to touch an icon once, i.e. I don't have to "double tap" it , which I think is an improvement. The power + volume down does work in TWRP to get the screen captures, but I found that I needed to write to my external SDCARD for the capture to be available to me after system boot. If there is anything specific you'd like me to capture, let me know.
[Nook HD, HD+ Android Development] amaces:
Thank you for taking the time to capture these; looks great on hummingbird, too. I'm glad the touchscreen behaves like it's supposed to now (double tap wasn't right).
[Nook HD, HD+ Android Development] bluecopper:
Just flashed the new twrp and 0622. Loving the response from the new twrp. The intermitent need to double tap was annoying.
[Nook HD, HD+ Android Development] mhunt13:
Update reports --

Updated to TWRP 2.8.7 -- HD+

Flashed the new recovery img with Flashify.

Really like the new theme and blue colors. Looks clean and sleek. Have used the backup, restore, install & wipe functions. All appear to work well!! Thank you amaces!

Updated to 0622 Rom -- HD+

Wiped System, cache & dalvik, and flashed the 0622 Rom (with the new TWRP).

First boot completed, and then got 'Unfortunately, the System UI has stopped.' That recovered, but it keeps happening every few minutes. Then I noticed similar problem as prsa01 posted above -- 'Unfortunately, Hackers keyboard has stopped.' This happens each time you need the keyboard to type... I've rebooted several times, it's consistent. Also wiped cache & dalvik again, still these messages persist. Not sure what's happening, perhaps I got a corrupt download. I will re-download and try again tomorrow. Never had these issues with any other update...

Not big deal, can restore a backup of 0615 which worked great. Just reporting in case others see similar messages.....

Thank you, amaces!!!
[Nook HD, HD+ Android Development] bluecopper:
So after flashing i attempted to download an app from the playstore. The screen went to sleep and then it would wake up. Eventually it restarted on its own. Doing something on the laptop for a while, turned around to notice the table restarting on its own again. Just wipe cache and dalvik and gonna see if it persists. Anyone else having the problem. Will do a full wipe if nothing has changed
[Nook HD, HD+ Android Development] starbright_:
Just want to to give my feedback, that due to some unknown reason Titanium Backup is still not working here (can't get root, although it works in terminal). But TB is working in other CM12 for other devices, so this seems not CM12 specific.

Together with the Wifi problems (I reported earlier that after a while it will not reconnect automatically) I decided to go back to CM11. Although I did a clean install, I am the only one suffered from this. Mh.

Sorry, but currently I need that device a lot and I think the alpha state at initial post is correct. I just want to say thank you and encourage you to go on! I am sure, I will come back later this year.
[Nook HD, HD+ Android Development] js290:
Any chance of building Cyanogen Recovery with f2fs support? TWRP has a lot of problems applying cm12.1 nightly updates reliably.
[Nook HD, HD+ Android Development] bluecopper:
Last night after still having issue with restarts, i wiped cache, dalvik and system, reflashed 0622 and gapps and the abrupt restarts stopped. I used to have issues where it would restart when using facebook app or facebook messenger. The screen would flicker then go blank for a few then restarts. Will see if i get that behaviour during the next few days
[Nook HD, HD+ Android Development] steavis00:
22 June - ROM

I haven't updated TWRP yet (just to see the difference), but the 22 June rev works really well for responsiveness. Thank you again.
[Nook HD, HD+ Android Development] pastordl:
Been running 6/22 and new TWRP. Both running great, still can't use SwiftKey or hackers keyboard in landscape. Bluetooth works with my Memorex speaker and Zippy BT 500 keyboard. The Zippy does work in portrait and landscape without flashing problems. The new TWRP is smooth and single touch on everything I've tried. Thanks for the awesome work. :good:::highfive:
[Nook HD, HD+ Android Development] twiztid_:
I did a clean install of 0622 and its running SO smoothly on my HD+.

I've had minor flickering, but it is considerably improved from the previous version, which was significantly better than before. I'm using the stock keyboard with stock browser (still don't like the symbol layout in 5.1, but haven't changed it yet), very few changes to the default settings so far.

Thank you so much amaces! :D:D:D
[Nook HD, HD+ Android Development] mr72:
No, I am saying across many different phones and tablets an incorrect "Insufficient Storage Space Available" error comes up from time to time, and this bug was introduced in KitKat. But I haven't experienced this problem on this particular tablet until CM12.1.
[Nook HD, HD+ Android Development] amaces:
All great advice; [MENTION=2804040]mr72[/MENTION], df might reveal the problem, but also try looking at the raw partition sizes: cat /proc/partitions and fdisk -l /dev/block/mmcblk0 (in Terminal, although adb will make it easier to copy/paste that output). A (correct) previous CM11 installation implies that your partitions should be OK, but even if eMMC is completely messed up, it can easily be rescued (assuming the hardware is not broken, that is).

Yeah, that problem will probably take a while to figure out :( After looking around, I'm thinking that it must be our current kernel, audio/video HAL, plus userspace configuration, and intuitively, the issues with the Dialer, screen casting and recording probably have a common culprit. If I understand correctly, the audio HAL was changed to used DMIC, rather than the old analog stuff. Based on [MENTION=4243514]Hashcode[/MENTION]'s comment here, he had looked at this, and if he hasn't figured it out, well…

About different kernel configurations, ours is very finicky; any change that might get us 5-10% improvements results in a non-bootable image, or breaks the frame buffer somehow. For example, SLUB (the default memory allocator since K2.6) will not work (likely, TI's bug, based on other resports), disabling CGROUP_MEM_RES_CTLR, ditto. So yeah, our best bet is a newer kernel; I spent a lot of time merging recent tuna changes and 3.0.101, and that kernel barely boots. K3.4 with the new ION library doesn't even give me an adb shell. I should probably open a separate thread specifically for these kernel experiments, but not before some mild success.
[Nook HD, HD+ Android Development] twiztid_:
Has anyone else had a problem with the keyboard recently? Its been crashing fairly regularly for me.

I even went back to a 5.0 keyboard, which hasn't crashed on me on 4.3/4.4/5.0, but I don't think its helped.

Also is there a way to change the key layout (mostly for the long-press symbols) of the 5.1 keyboard?

On 5.0 the asdf row has "@#$%&*-+_", and on 5.1 its "@#$%&-+().
[Nook HD, HD+ Android Development] Monfro:
Galaxy Nexus has 3.0.101 kernel, and I remember I have read that also the experimental 3.4 kernel was working well.

They were also trying to update GPU drivers.

Maybe we can start from their trees, since Galaxy Nexus probably is the Omap device with most support?
[Nook HD, HD+ Android Development] mr72:
I have never run stock os on this tablet. Installed cm9 or 10 the day I got it. Any way, here's df output. And I'm running cwm.

Root@ovation:/ # df

Filesystem Size Used Free Blksize

/dev 388.6M 36.0K 388.6M 4096

/sys/fs/cgroup 388.6M 0.0K 388.6M 4096

/mnt/asec 388.6M 0.0K 388.6M 4096

/mnt/obb 388.6M 0.0K 388.6M 4096

/system 661.4M 451.9M 209.5M 4096

/data 12.7G 12.0G 685.7M 4096

/cache 456.7M 7.8M 448.9M 4096

/rom 47.2M 12.5K 47.2M 512

/bootdata 47.2M 13.5K 47.2M 512

/mnt/shell/emulated 12.7G 12.0G 685.7M 4096

/mnt/media_rw/sdcard1 29.7G 23.6G 6.1G 16384

/storage/sdcard1 29.7G 23.6G 6.1G 16384
[Nook HD, HD+ Android Development] andtron:
Hi amaces (or other builders),

After the reinit to 12.1 , do you need to do a clean (what is the command) especially after you just built the 12.0?

I asked because I am getting the compile error:

Symlink: /home/xxxx/android/system/out/target/product/ovation/recovery/root/sbin/fsck.exfat -> mount.exfat

external/libselinux/src/android.c:837: error: undefined reference to 'SHA_hash'

collect2: error: ld returned 1 exit status

Edited: never mind I found the solution, just move the previous $OUT/.../Ovation to anther folder (like ovation0) and then rebuild.
[Nook HD, HD+ Android Development] kia75:
What Google apps does everybody use?

I downloaded the latest build and Google apps from Here using the 5/3/15 and initial setup keeps crashing. Should I try the 3\24\15 build? Especially since 5\3\15 is still a month away?
[Nook HD, HD+ Android Development] Zippy Dufus:
building the boot.img?

Builders,

I'm following option B on this page in attempt to build the boot.img but the only image file that I get is ramdisk.img.

Basically, I run mka bootimage instead of brunch.

However, lots of intermediary files are created so it appears that I'm missing a step which puts them all together.

Any ideas?

My goal is to rapidly iterate for debugging and tweaking the kernel, i.e. the Hangouts issue.
[Nook HD, HD+ Android Development] Ferd Burfle:
I updated from 4/4 to 4/8 and have no issues. I just wiped the cache and flashed the new build.
[Nook HD, HD+ Android Development] mr72:
BTW, I installed TWRP in place of CWM and then did a wipe formatting /data, which it did with F2FS. Before that I noticed that in /data was a directory called 'Android' that included its own /data with lots of stale content that looks like it was held over from some previous installation like CM11. Dunno how that got there.

Anyway, after the wipe and then reinstalling the same apps that were there before I now have 9G or so free.

I'm glad I got it fixed but I still wish I knew how it got in this state.
[Nook HD, HD+ Android Development] asakurato:
Rotation setting on landscape isn't working, as soon as I change to landscape, it immediately changes to portrait

Sent from my C6603
[Nook HD, HD+ Android Development] MossyTC:
I'm using gapps-lpmr1-20150503-signed.zip without problems. Note that this was uploaded on 4\3\15, so the file name must be a typo.
[Nook HD, HD+ Android Development] twiztid_:
20150503 = Year Day Month I would imagine.
[Nook HD, HD+ Android Development] MossyTC:
[MENTION=5720705]twiztid_[/MENTION]

Nope, the date format on the other files on that page are all YYYYMMDD and are uploaded on the same date as specified in the filename.

It's a typo.

---------- Post added at 09:34 AM ---------- Previous post was at 09:22 AM ----------

If you're using git, git log --oneline should show the commit messages (including those from merged code), which could be used as a changelog.
[Nook HD, HD+ Android Development] amaces:
That's what I started a few weeks back. The problem is that our kernel tree is already heavily customized, and trying to merge tuna (GNexus) or bowser (KFire) kernels results in hundreds of conflicts, which are not easy to sort out. First, I spend a few afternoons merging Ziyann's 3.0.101, and was excited when I had finally build an image. Alas, the frame buffer/touch panel/surfaceflinger fails to start, although I can get an adb shell, and kmesg/logcat helped fix some errors. After giving up on that, I stumbled upon faZevoLv's kernel, so next I spent another couple of days merging his bowser kernel tree. Given that it's based on Hashcode's work, I assumed this one would be a easier to work with, but once again the KFire base is still very different than ours. I did manage to resolve all conflicts, and even boot an image, but still got stuck with broken surfaceflinger. Anyway, I will post my experiments with these on a separate kernel thread at the next opportunity.

Glad you solved your problem; this shouldn't (and normally doesn't) happen. It may have stemmed from how different recoveries handle wiping, which is different than formatting (for some partitions, at least). If you have the time, and for your peace of mind, you could start with a totally empty slate, by reformatting the whole eMMC.

It's usually a good idea to do a mka installclean. That (plus ccache) will still allow faster compilation than a total mka clean/clobber.

That's what I've been doing, but make sure you run mka bootimage/recoveryimage/bacon only after you initialized you device with breakfast or lunch, or after a brunch complete build.

[MENTION=2915683]BaNkS[/MENTION] GApps here are another good option.

We're talking about hundreds of different repositories, and it sounded like you were looking for an easy encompassing indicator of the last thing included. Thus, with next builds, I will append an UTC timestamp for build start, so you can then check your favorite log sources.
[Nook HD, HD+ Android Development] lmacmil:
The link in the first post doesn't work for me. I get a "webpage not available" error message.

Update: issue related to accessing the link on my Nook, works fine on my PC.
[Nook HD, HD+ Android Development] MossyTC:
[MENTION=4473900]amaces[/MENTION] Ok, thanks for that.
[Nook HD, HD+ Android Development] belfastraven:
Thanks for the 4/14 hummingbird build, amaces

Seems to be working very well on both 16G and 8G nook hd. I don't use hangouts, though, so haven't tested that.
[Nook HD, HD+ Android Development] aoleary:
In CM12, I cannot get Titanium Backup to restore all my apps in one go.

I think this is more of a superuser issue, however..

Does anyone else see this issue? How did you get around it...
[Nook HD, HD+ Android Development] shdware:
The last build works very well. It eliminated the reboots and flickering completely.

I tested Netflix, Hulu+ and a few other apps. No crashes. Microsoft Office worked okay - no crashing.

I did take a performance hit coming from 4.4: Antutu benchmark went from 21500 to 18400. I think the issue is primarily with the video drivers as it doesn't look nearly as smooth on the desktop and on websites when scrolling and zooming.

Anyways, I'm pleased. This is stable enough to be a daily driver.

Can the keyboard sounds be made adjustable? I can't mute it or turn the volume down on those.
[Nook HD, HD+ Android Development] mhunt13:
Well, I did re-download the 0622 build this morning, checked MD5 and is same as yours.

Tried your suggestion.......wiped everything, flashed 0622 rom and Gapps --- then restored only the data partition (from full 0615 backup). Wiped cache and dalvik again, just to be sure. Then re-booted and waited for system/ART to finish. Alas, it didn't seem to help. Still the UI stops, and also Hacker's keyboard stops. No luck with that.... yet thanks for the help.

Have restored full 0615 backup, all is well again.
[Nook HD, HD+ Android Development] prsa01:
suddenly no brightness control

Hope i am missing something obvious. First off, Amaces was right about my issues with the 6/22 build. It seemed to be tied to not having space in system. Not sure why that was, don't really have much on tablet, but have moved on from that.

I cuurently do not have brightness control. Have done multiple full wipes in TWRP followed by reflashes of both the 6/15 and 6/22 builds. Have explicitly wiped system, data, cache and dalvik multiple times. Gone back and re-setup the device from scratch multiple times. None of that seems to get my brightness control back. All else seems to work properly. This is after everything working fine on multiple builds until i tried to go to 6/22 the first time.

Anyway, just looking for anything else to try. I am far from an android expert and don't know if I'm missing an obvious step.

Thanks much!!
[Nook HD, HD+ Android Development] mhunt13:
This is like stating the obvious -- so please excuse me if you've done all the touches to get the brightness bar to show up.

Go -> Settings -> Display & Lights -- then at the top, underneath 'Screen' it should say 'Brightness level'. You actually have to touch 'Brightness level' and then the slider bar will appear at top/center of your screen. Hope it works..... :)
[Nook HD, HD+ Android Development] amaces:
About filling /system, are you using a PA GApps clone (those are deprecated, and certainly lack proper maintenance these days)? That partition is read-only during normal operation, and the stock ROM leaves ample space in there. About brightness control, unless you broke your device somehow, it's a very odd issue. Android simply writes values (0 to 255) to a sysfs interface, and the kernel does the rest. Maybe you corrupted your boot partition, although that get re-writen with every update. Are you stuck at some extreme value (very dim, or very bright), or just something intermediate that you chose before?

Next step is clean install… You could wait till next week for the next set of builds, and see if that fixes your issues. I'm assuming you checked free space in /system (see [MENTION=4433692]prsa01[/MENTION]'s post above).
[Nook HD, HD+ Android Development] amaces:
That looks like a minimal GApps package, which should still leave close to a 100 MB of free space in /system. You have something else that's filing that partition, and it must have backup support if it keeps getting carried over with new installs… If you don't mind a clean install, make sure to wipe /system after factory reset (which only cleans /data, /cache, and Dalvik stuff), then reinstall ZIP, GApps, and whatever else you may need. I've been recommending the package here: http://fitsnugly.euroskank.com/?rom=banks&device=gapps.
[Nook HD, HD+ Android Development] prsa01:
To be clear, the system part size was only an issue until the first time i wiped system. Hasn't been an issue since then. I'll try the different gapps you linked.

Oh, i should have pointed out that when in twrp, etc brightness is normal/brighter. Not sure if twrp or anything else has brightness controls i could test with.