yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Uldiniad:
appreciate your help [MENTION=5672278]belfastraven[/MENTION]

will try your suggestions once I reboot my computer to Linux. :)
[Nook HD, HD+ Android Development] Uldiniad:
I got the twrp-recovery folder out of the bootable folder and it worked. thanks [MENTION=5672278]belfastraven[/MENTION]

Hopefully we won't have to do workarounds too often. I like it when it is as simple as repo sync and brunch :)

---------- Post added at 02:01 PM ---------- Previous post was at 01:44 PM ----------

actually, now that I am thinking about it. Will repo sync recreate the twrp-recovery folder? Because it will be a little bother to have to keep cutting the folder out every time I repo sync...
[Nook HD, HD+ Android Development] ajislav:
Hi [MENTION=5672278]belfastraven[/MENTION],

On my secondary device Samsung Galaxy S2 an issue resulting in negative battery percentage being shown cropped up on 20160815 build.

The issue was fixed here https://review.cyanogenmod.org/#/c/156807

I believe the original commit that broke it was either this https://review.cyanogenmod.org/#/c/155482 or this https://review.cyanogenmod.org/#/c/156415

Both of which modify this file

CyanogenMod/android_vendor_cm*/*charger/Android.mk

I am absolutely unsure if this is related to the issue diacussed, but the correlation seems good enough to mention it.
[Nook HD, HD+ Android Development] belfastraven:
Yes, it will. If you don't want to do that, you can put a file named "something".xml (Most people name it roomservice.xml) in the local_manifests directory under the .repo directory. It should contain

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

<manifest>

<remove-project name="android_bootable_recovery"/>

</manifest>

That will remove the twrp directory when you sync, the way things are configured right now. Please keep in mind that amaces is letting us use the build sources that he has developed and could change them in the future so that this would

1) not work

or 2) not be necessary.

---------- Post added at 07:35 PM ---------- Previous post was at 07:24 PM ----------

The initial commit indeed is what broke our build, since it (amoung other things) added a new cpp file which included a function which needed the /recovery/minui/graphics.cpp file to have been compiled--which we normally wouldn't do since will build TWRP recovery when we build. The fix, which should have fixed the reporting problem you mentioned, wouldn't fix our build problem though. Most builders who default to building the CM recovery wouldn't have had our issue. I didn't look at the code closely enough to see what reporting differences we will see on our nooks. Maybe I'll try building later and check it out :)
[Nook HD, HD+ Android Development] neonleon29:
I am using an early April version of AOSP. I wanted to try the latest version but am having difficulty dirty flashing it. I am also running Exposed with the ROM. I've tried the following with no success:

1) Go into TWRP and wipe cache and dalvik cache

2) Install latest AOSP

3) Rebooted without wiping anything.

This method kept getting me a message that google services no longer worked.

Then I tried:

1) Go into TWRP and wipe cache and dalvik cache.

2) Install latest AOSP and open GApps

3) Reboot without wiping anything

This method gave me a message that the setup wizard wouldn't work.

Anyone have any suggestions? Do I need to disable Exposed before trying to dirty flash the latest AOSP version? And should I reinstall GApps during the dirty flash? TIA.
[Nook HD, HD+ Android Development] flieswithhawks:
Have you tried re-installing latest Xposed zip file after you flash ROM&GApps?
[Nook HD, HD+ Android Development] neonleon29:
When I installed both ROM and GApps, I couldn't get past a message that kept popping up and saying the setup wizard won't work.

When I originally installed only the ROM, it took me to the home screen but every now and then I would get a pop up message saying googles services no longer work. I did not try reinstalling xposed at that time. Do you think that would fix the google services issue?
[Nook HD, HD+ Android Development] TBueno:
There's a workaround. Check out this post:

http://xdaforums.com/showthread.php?p=67365690
[Nook HD, HD+ Android Development] flieswithhawks:
I don't use GApps on this device so I'm of no further help regarding this. Sorry
[Nook HD, HD+ Android Development] neonleon29:
I finally got the June version of AOSP to work but ran into a problem with the quick setting tiles being nonexistent when pulled down from the status bar. I remember people mentioning this issue which is probably the reason I stayed at version 4/6 for so long. Is anyone using a more recent version of AOSP that doesn't have a problem with the quick setting tiles? I went back to my old standby of 4/6 for now.
[Nook HD, HD+ Android Development] mmnspeed:
Flashed the latest experimental build for ovation.Everything seems to be working fine .The issue with turning off the device has been solved.Also the device now turns on if you connect the charger in off state.Earlier it wouldn't charge in that state.Don't know what would have happened if the device had discharged fully on that build.
[Nook HD, HD+ Android Development] rtarv321:
I flashed the latest experimental version of Cm also. Everything was fine except that I lost root & could not get it back. I tried flashing supersu with TWRP & installing from play store. I finally ran recovery from TWRP. Unfortunately I'm back where I started. I can't figure out what I did wrong. Any ideas?
[Nook HD, HD+ Android Development] neonleon29:
These instructions were posted by mikeataol (post #1072) and helped another user gain root. Maybe it could work for you. Here is the post:

"to get root in CM versions you have to enable developer options (by tapping on the build number 7 times) and then in developer options , enable root for apps and adb

you might flip it on and off once and then go back and flip it again, that's a common problem in CM...."
[Nook HD, HD+ Android Development] rtarv321:
Thank you for your reply. Developer option has been set, also "root access is set for apps & add. I am familiar with this process, as these options were used with my install of the mm 6.0 dated 5-30-2016 & what I remember dating back to when I first rooted & installed kk 4.4 back a couple of years ago. What don't understand is root was fine on the 5/30 version. I flashed the June experimental version & lost root
[Nook HD, HD+ Android Development] acr123:
In developer option turn off root access then turn on root access for applications or applications & adb and you should have root again.

Good luck,

Al
[Nook HD, HD+ Android Development] ipdev:
Having install issues with cm_ovation-ota-MOB30Z.160819.

"Updater process ended with ERROR: 70"

(Tried on both my ovation, same result, normally run cm on one and aosp on the other.)

http://pastebin.com/gf3PXGmr

I can install aosp_ovation-ota-MOB30Z.160820 the exact same way without error on both.

Any ideas?
[Nook HD, HD+ Android Development] vinceweis:
Thank you very much for the update. I appreciate the effort that keeps this device fully functional for my uses. I flashed and then wiped cache and dalvic and everything works so far. Thanks again.
[Nook HD, HD+ Android Development] belfastraven:
Have you tried installing the rom without gapps? It looks like the rom installation itself is succeeding but the gapps installation is failing. Are you using the same gapps version in both cases (AOSP and CM?) I assume you are sideloading using a script of some sort, since I see that you back up the partitions first... If you are not installing Pico gapps you might want to try that....

see this from your log?.....

Insufficient storage space available in

System partition. You may want to use a

smaller Open GApps package or consider

removing some apps using gapps-config.

See:'/sideload/open_gapps_log.txt'

for complete details and information.

- Copying Log to /sideload

cp: can't create '/sideload/open_gapps_log.txt': Read-only file system

- NO changes were made to your device

I dirty flashed the cm version on my hummingbird, and the only issue I am seeing right now is that if I go into settings/about tablet/status , I get the "Unfortunately, the process com.android.phone has stopped" message, a problem that I am still looking into.

---------- Post added at 01:29 AM ---------- Previous post was at 01:18 AM ----------
[Nook HD, HD+ Android Development] flieswithhawks:
I parrot everything said here. On the newest testing everything runs well so far except the "power off bug" still occurs. Any solution for this?
[Nook HD, HD+ Android Development] ipdev:
[MENTION=5672278]belfastraven[/MENTION]

With aosp, I can complicate the install with su and xposed with no problems.

I have wiped, restored, reformatted, wiped and installed.

Between twrp and adb I'm not sure what else to try.

CM rom install works.

Installed with gapps, I get force close when first booted. (If gapps takes.)

I get force close every time I install gapps after initial boot. (Regardless what I wipe before or after.)

twrp-3.0.2-0-ovation

cm_ovation-ota-MOB30Z.160819

aosp_ovation-ota-MOB30Z.160820

open_gapps-arm-6.0-pico-20160813

open_gapps-arm-6.0-pico-20160817
[Nook HD, HD+ Android Development] mmnspeed:
Did you try a clean install?...I tried turning off the device a few times yesterday and it did turn off successfully..
[Nook HD, HD+ Android Development] flieswithhawks:
No I dirty flashed. I will try a clean one and report back. Thanks.
[Nook HD, HD+ Android Development] mmnspeed:
Please don't try it.My apologies for any inconvenience caused.Turns out you are right.The bug is still there.I tried it today.I can't understand how it seemed to work properly yesterday. It was the first thing I checked and offline charging.I must have been mistaken to believe that it was rectified.
[Nook HD, HD+ Android Development] belfastraven:
The AOSP rom takes up much less space in system, so it is not surprising that things would "fit" there and not with cm. I haven't yet tried doing a clean install of the cm rom, however, I was able to dirty flash the rom (i.e. flash the rom and not wipe/clear anything ) without any problem. Apparently the gapps needs more system space while it is installing-that's what the message I pointed out was telling you.

I am not running exposed, however, so don't know what happens if you flash over a rom with exposed installed. You might want to try restore system and data from a previous successful backup and then dirty flash the rom. If that works but you still want to do a clean install, try using a .gapps-config file to remove things you don't use, to make gapps smaller. (e.g. FaceDetect

FaceUnlock

ExchangeGoogle (unless you do use exchange services) , and do flash GAPPS immediately after the rom with no intervening steps.

Also, I would suggest doing this from TWRP on the HD+ so you can watch the output in real time--
[Nook HD, HD+ Android Development] flieswithhawks:
So I clean installed before reading your post and the tablet did power down correctly once and then afterwards it still has the bug and reboots itself. It was due for a clean flash anyways and at the least seems to run smoother than before.
[Nook HD, HD+ Android Development] droidseban:
I see that the latest build cm_ovation-ota-MOB30Z.160819 got moved to the main area from the experimental section. Compared to the previous build (...30J...), this one is bigger and seems to not leave enough room in system partition for gApps (I tried pico version). Power off bug remains. On the plus side, the latest one boots up about 5 seconds faster than the previous build. That's awesome! Thanks Amaces!

Since I couldn't install gApps, what I did is to flash the previous build with gApps and install all my apps. I then used ES file explorer to backup the APKs to external SD card, reflashed the latest, and side loaded the APKs. Not ideal, but works for now and the faster boot up makes it worthwhile for me.
[Nook HD, HD+ Android Development] snovvman:
Another option to trim the ROM: After flash, stay in TWRP, mount the /system partition and use File Manager to remove unneeded APKs, such as bundled IMEs. You can then try to flash GApps again.
[Nook HD, HD+ Android Development] neutronjeff:
I'd like to better understand this. Could you please be more specific what is removable?
[Nook HD, HD+ Android Development] belfastraven:
solving cm space issues with .gapps-config

If you are having trouble flashing gapps because of the size of the latest rom, you might want to check out this https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

Once you create the .gapps-config file, you can keep it around in the directory from which you normally install the gapps zip and it will not only prune unwanted apps from gapps but also from the rom itself, if you'd like , when you install gapps. The description referenced in the link gives examples of things that can be removed. You will get good logs of what has been done, too.

FWIW
[Nook HD, HD+ Android Development] droidseban:
Thank you to snovvman and belfastraven for the suggestions!

First I tried snovvman's suggestion and deleted a few things from /system/app from TWRP including camera, gello (browser), galaxy4 (music player), all the different live wallpapers (photoPhase, holobeam, etc). This made enough space to install pico gApps. It rebooted fine but had FC's after screen unlock.

For the second try, I tried the gapps config file method belfastraven suggested, which not only lets you trim stuff out of the gApps package, but also lets you uninstall some CM apps that is already installed. This worked very well.

I reflashed CM and gApps with the config file. I have attached the config file, in case anyone needs it. Put the config file in the sd card with our gApps (pico) zip file. Take a look at the contents since all those components will be excluded from your install.
[Nook HD, HD+ Android Development] snovvman:
Glad you got it sorted out. You do have to be judicious in what you remove, but it can save you when other options are not available. I do not run the CM ROM, but the next time I flash it, I'll build a list on what is safe to remove. The gapps config option sounds like a good one. Do remember to clear caches after flashing or removing apks.
[Nook HD, HD+ Android Development] twiztid_:
Have any fixes/workarounds been found for the top three (IMO) issues with these builds?

WiFi preventing deep sleep (rx_wake wakelock)

Use to go away for me, but seems to be annoyingly persistent using a clean install of 160819 (NookHD+).

No WiFi after you wake the device

Occasionally goes away on its own? Possibly resolved with clearing Cache/Dalvik?

Power/Home not waking device

This issue seems to resolve itself after a while/a few restarts. I believe this is related to something with the touch screen, when this happens plugging in the device will turn the screen on (with the Screen on when plugged/unplugged enabled), but touch screen is unresponsive/behaves oddly or is just really laggy.

Update:

It actually seems the screen MOSTLY works, once you get past the lock screen. Instead of unresponsive/oddly/laggy, I think the screen just has a "touch" on it somewhere, which is causing the behavior. However, the Power/Home buttons still don't work, I haven't tried the volume buttons.
[Nook HD, HD+ Android Development] ShapeShifter499:
So I just came across this issue with TWRP. Is there a more current build that contains the Adopted Storage fix? Right now I have TWRP 3.0.2 and it fails to read my Adopted Storage SD card. This is on a Nook HD Hummingbird.
[Nook HD, HD+ Android Development] belfastraven:
Could you tell me which rom you are running (AOSP or CM and the date) and from where you got the TWRP?

I've noticed that in the last couple of weeks there have been some fixes to the partition software on TWRP for adopted storage --the version has not changed, but perhaps a very recent build would help. I've just built and installed a new image today which is working for a rom install, wipes, etc. I don run with adopted storage, so I don't know whether it would fix your problem. Let me know if you want to try it.
[Nook HD, HD+ Android Development] mmnspeed:
Tried the latest nougat build in the experimental folder.Have been using it only for a short tme but it has already got me really excited.One thing I hated on the dvevice(due to hardware limitations) after material design has been revamped.Multitasking is smoother.Recent apps menu is snappier.Haven't tried looking for any gapps yet.I have already taken a backup.Take a backup and check it out. If I get the things I require working i might even ditch CM.:)
[Nook HD, HD+ Android Development] hemeboy:
Experimental Nougat build running very smoothly with Open Gapps pico version. No major problems so far.
[Nook HD, HD+ Android Development] ShapeShifter499:
I would like to try a newer build. I'm currently running Hummingbird Cyanogenmod build 05-30-2016 from this thread with TWRP 3.0.2-0 from the official TWRP website. I downloaded this TWRP months ago so of there was a change let me know.
[Nook HD, HD+ Android Development] belfastraven:
I have attached a zipped HUMMINGBIRD TWRP recovery image file--the image file was a bit too big to be allowed as an xda attachment. This is NOT the same thing as a flashable recovery zip. Unzip the file, and then you can use TWRP to flash the recovery.img file to the recovery partition.

this is the commit that I thought might solve your problem--it's from two weeks ago, and the TWRP from the official download page is a few months old, I think.

https://github.com/omnirom/android_bootable_recovery/commit/3126a113e7f45f54bb2475b1145a0467ae508308
[Nook HD, HD+ Android Development] belfastraven:
Noticed this re dex2oat from cm13 nightlies changelog

[MENTION=4473900]amaces[/MENTION],

http://review.cyanogenmod.org/#/c/122947/ --looks like a patch that fixed the dex2oat problem.

I am still pursuing setting up docker on my pc to try to build--there is a bug in the current docker release, but I'm almost there: If I use the repo you indicated before,

repo init -u git://github.com/airend/android.git -b marsh

will that repository work for cm as well as aosp?

thanks ( I think it will be a couple of more weeks before I can actually try to build)
[Nook HD, HD+ Android Development] amaces:
Great, based on that thread it fixes CM13 ART issues on a bunch of devices, including acclaim. Probably everything non-QCOM suffered from what they merged before (AOSP is not affected by this). I still don't understand how they could leave this broken for more than a month, when they broke it themselves. I guess I'll give CM13 another shot, now that they merged android-6.0.1_r3.

Right, that command will initialize the AOSP Marshmallow repositories; CM1[23], Lollipop would need appropriate -b arguments as described in post #2. Thus, we need four distinct manifest branches, although cm-12 and lolli are probably not in good shape right now. You definitely need dedicated folders for each ROM flavor, but you can change your mind later on to reinitialize from a different manifest. If disk space is a constraint, and you want to have both CM and AOSP checked out separately, repo --reference will attempt to avoid repository duplication, save bandwidth, etc.

Keep in mind that it'll have to be a fairly modern desktop (well ventilated, too). Another option is building remotely on cloud/virtual machines (e.g., AWS/EC2), although you probably need more than the free tier resources. It sounded like [MENTION=3651088]Zippy Dufus[/MENTION] went that route.
[Nook HD, HD+ Android Development] Zippy Dufus:
Yup, I have a bleeding-edge Fedora 23 x64 laptop running a Fedora 23 x64 virtual machine (VM) under the Linux-specific KVM virtualization software. For Windoze users, I would recommend using Oracle Virtualbox (it's free) with either an Ubuntu or Fedora guest. You will need about 90GB of disk space on VM. I run my VMs from external USB drives so I can run them from different machines.

I now have three VMs for Android (CM, OmniRom, and ASOP for this ROM).

Of course, using Fedora, I am often master of my own misery when the build doesn't work.

Speaking of misery, [MENTION=4473900]amaces[/MENTION], I still have not been successful building the ASOP version this ROM (haven't tried CM13 yet). It still fails at trying to link to the 3rd-party firmware libraries.

target Executable: pvrsrvinit (/home/android/out/target/product/ovation/obj/EXECUTABLES/pvrsrvinit_intermediates/LINKED/pvrsrvinit)

/home/android/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin/../lib/gcc/arm-linux-androideabi/4.9.x-google/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lsrv_init_SGX544_112

/home/android/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin/../lib/gcc/arm-linux-androideabi/4.9.x-google/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lsrv_um_SGX544_112

hardware/ti/omap4/pvrsrvinit/pvrsrvinit.c:8: error: undefined reference to 'SrvInit'

collect2: error: ld returned 1 exit status

build/core/executable_internal.mk:79: recipe for target '/home/android/out/target/product/ovation/obj/EXECUTABLES/pvrsrvinit_intermediates/LINKED/pvrsrvinit' failed

make: *** [/home/android/out/target/product/ovation/obj/EXECUTABLES/pvrsrvinit_intermediates/LINKED/pvrsrvinit] Error 1​

Are my build commands correct?

repo init -u git://github.com/airend/android.git -b marsh

repo sync --force-sync

source build/envsetup.sh

lunch aosp_ovation-userdebug

make otapackage​
[Nook HD, HD+ Android Development] amaces:
The commands look OK, although you only need --force-sync if regular sync doesn't work (repo will tell you what the problem repository is). Also, just to clarify again, repo init is needed only once (unless you switch manifests). The pvrsrvinit linkage problem happens sporadically after installclean, but always works after make clean. The proprietary blobs are checked out in vendor/ti. Are you using a custom Android EABI - i.e., what does arm-linux-androideabi-gcc -v say?

P.S. You can retry only this step with make pvrsrvinit. Also, the -jN flag can speed things up quite a bit.
[Nook HD, HD+ Android Development] belfastraven:
I have a Haswell i7-4770 cpu with 16G of memory. Unfortunately (well-for this purpose--I actually built it like this on purpose) it is an ITX system and uses the stock cooler, so ventilation probably would be an issue, although if [MENTION=3651088]Zippy Dufus[/MENTION] is building with a laptop, maybe, not. :) I will check out the AWS possibility.
[Nook HD, HD+ Android Development] andtron:
Hi amaces,

I tried out the aosp1208, and my nook just boot loop on the 'android ' animation.

Maybe my way of installing it was wrong:

(1) factory wipe,

(2) gapps

(3) supersu

Then reboot.
[Nook HD, HD+ Android Development] amaces:
No worries then; your setup is way better than mine, which means you'll finish builds much quicker, especially if you're SSD based. Once you have everything set up, your build will probably take 3-4 hours at first, and possibly even half an hour for re-builds with ccache. Overheating is not as much of an issue then.

This happens on ovation or hummingbird? Both are tested at this point, so it probably doesn't matter. Did any of the previous MM builds work for you? Your way looks OK; factory wipe should only be needed when switching from CM or Lollipop, but after that, I just install ROM, SU, and finally GApps. If you don't have anything important on internal storage, formatting data is worth trying (seems to have helped a couple of people on the thread).
[Nook HD, HD+ Android Development] Monfro:
AOSP 1208 is working ok on my Ovation.

When you open an app it works faster than Lollipop.

General memory management (switching between apps and using more apps at the same time) is the only thing that needs refined.

Other than that it can be used as a daily driver.
[Nook HD, HD+ Android Development] andtron:
Hi , amaces,

I was switching from lollipop, and my cm mm from your 1129 build was fine, other than the sd card support issue.

I am using ovation.

Thanks for taking the time to write.