yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Mac Hosehead:
I am using 1511 on hummingbird and I see all the issues belfastraven has mentioned except for the home button behavior.

-MH
[Nook HD, HD+ Android Development] Minshter:
I am having similar issues others have been discussing, albeit on my Ovation.

For some reason on the 11/08 build, & installing the Open Gapps Nano you provided, I only got 2 force close messages related to play store service, etc. After that it was fine.

With the 11/15 build though, using either your previous Open Gapps Nano, or a newer one directly from them, nothing but a series of force close / apps stopped messages, all related to google stuff (play store service, news & weather, set up wizard).

Eventually it crashes and reboots, only to repeat.

This was all on clean installs as well. Went through the process four times, even checking my partitions for errors (just in case).

I did one further try, manually installing the google base apk's from apkmirror, making sure all the permissions were turned on. Google play store would still close. Trying to add an account would force close (app stopped message) for google services. Rebooting at that point would turn it into the issue mention above; a stream of app close / app stopped for google related things.

For now I've done like you advised in the OP, side-loading apps that don't rely on the play store base. I do look forward though to being able to use play store services since lots of things look for it.

Thanks so much for all your work on this. MM is damn speedy.
[Nook HD, HD+ Android Development] belfastraven:
AS I noted a couple of posts ago, I was having a lot of trouble with the 10/15 hummingbird, once gapps were installed. I have found a solution for myself--perhaps it will work for others. I had been wiping system, data, cache, and dalvik

then installing the rom, wiping cache and dalvik, rebooting, going back to recovery, installing gapps, etc.

I finally tried wiping cache, dalvik, system, but FORMATTING data--which does wipe data/media. I then flashed the romm ,11/15 nano gapps, and 2.52 SuperSU. I did not wipe cache or dalvik-just rebooted. The setup wizard actually ran for me--in its new form it will even ask if you want to recover apps from google backup--I let it do that ,and all of the apps I tried so far, except for the Kindle app, are working.

I'm wondering whether there was something left in data that was screwing things up before.

Location IS working,

And Newstand is fine--

Kindle app still won't work--I have seen some reports of this on other marshmallow devices and am trying to look into it more.

this feels MUCH better;), [MENTION=4473900]amaces[/MENTION]
[Nook HD, HD+ Android Development] leswgnr:
Thanks belfastraven. I've been trying every wipe and install order multiple times to get this all done...the format worked like a champ. I could always get past the setup and other fcs thru various other methods, but none of the installs with gapps worked right, yet all of the ones without it were fine.

Look forward to testing it out now. Kudos amaces.
[Nook HD, HD+ Android Development] Zippy Dufus:
Almost ...

Hello again [MENTION=4473900]amaces[/MENTION],

I twice tried to build but was unsuccessful:

Fixed up my script as per your advice.

First attempted to build against my existing repo which indeed had a mishmash of projects because I have build many other Cyanogen ROMs on it.

Deleted the repo and re-downloaded the git projects required by your manifest during my second attempt.

Both attempts resulted in the same error during the kernel build. It appears that it attempts to link in the incorrect version of decompress_unxz.c which calls memset while your kernel version initializes memory directly. Otherwise, the build almost finished.

Any ideas?

And my apologies for being a pest.

AS arch/arm/boot/compressed/ashldi3.o

LD arch/arm/boot/compressed/vmlinux

arch/arm/boot/compressed/decompress.o: In function `memzero':

/home/android/out/target/product/ovation/obj/KERNEL_OBJ/../../../../../../kernel/bn/omap/arch/arm/boot/compressed/../../../../lib/decompress_unxz.c:197: undefined reference to `memset'

/home/android/out/target/product/ovation/obj/KERNEL_OBJ/../../../../../../kernel/bn/omap/arch/arm/boot/compressed/../../../../lib/decompress_unxz.c:197: undefined reference to `memset'

/home/android/out/target/product/ovation/obj/KERNEL_OBJ/../../../../../../kernel/bn/omap/arch/arm/boot/compressed/../../../../lib/decompress_unxz.c:198: undefined reference to `memset'

/home/android/out/target/product/ovation/obj/KERNEL_OBJ/../../../../../../kernel/bn/omap/arch/arm/boot/compressed/../../../../lib/decompress_unxz.c:197: undefined reference to `memset'

/home/android/out/target/product/ovation/obj/KERNEL_OBJ/../../../../../../kernel/bn/omap/arch/arm/boot/compressed/../../../../lib/decompress_unxz.c:197: undefined reference to `memset'

/home/android/kernel/bn/omap/arch/arm/boot/compressed/Makefile:159: recipe for target 'arch/arm/boot/compressed/vmlinux' failed

make[4]: *** [arch/arm/boot/compressed/vmlinux] Error 1

/home/android/kernel/bn/omap/arch/arm/boot/Makefile:54: recipe for target 'arch/arm/boot/compressed/vmlinux' failed

make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2

/home/android/kernel/bn/omap/arch/arm/Makefile:280: recipe for target 'zImage' failed

make[2]: *** [zImage] Error 2

Makefile:134: recipe for target 'sub-make' failed

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory '/home/android/kernel/bn/omap'

build/core/tasks/kernel.mk:169: recipe for target 'TARGET_KERNEL_BINARIES' failed

make: *** [TARGET_KERNEL_BINARIES] Error 2

[0;31m#### make failed to build some targets (26:06 (mm:ss)) ####[00m
​

[android@localhost ~]$ find ./ -name decompress_unxz.c

./kernel/bn/omap/lib/decompress_unxz.c

./external/busybox/archival/libarchive/decompress_unxz.c

​
[Nook HD, HD+ Android Development] Minshter:
This sorted out my issues with Gapps as well. Greatly appreciate you sharing this info.
[Nook HD, HD+ Android Development] king200:
With my Ovation, I wiped system/data/cache/dalvik and just installed system. Newsstand was only app I installed. Contrary to your experience, Newsstand did not run.
[Nook HD, HD+ Android Development] belfastraven:
I'm not sure what you mean when you said that you just installed system. I've not had a particular problem running newstand no matter how I installed gapps, but my point was that google apps and services ran much better for me after I FORMATTED rather than WIPED data. At least in the TWRP 7.8.7.4 from [MENTION=4473900]amaces[/MENTION] that I am running, formatting will clear the internal SDCARD, wiping doesn't do that.

Newsstand needs some google services and google play services to run. I am not sure if I am understanding you correctly, but am just trying to help.
[Nook HD, HD+ Android Development] king200:
Just system is wiping everything and installing the rom, Gapps, and Supersu

Everything in my system runs fine with no problems with the Gapps.

I have reformatted the partitions with the previous build, where Newsstand did not run either, but this time I just wiped. I'll reformat and try once more.

Newsstand_3.4.5-2015091713_minAPI14(nodpi)
[Nook HD, HD+ Android Development] belfastraven:
I see that on google play store, the newsstand version was updated on 10/21.(they don't give a version number) I am running 3.4.5 same as you, but installed from the play store. What is happening when you run newsstand? Do you have a logcat? I know how frustrating this is when you want to read something and can't--I've gotten the amazon kindle app (which doesn't even need gapps stuff) to completely work just once :)
[Nook HD, HD+ Android Development] king200:
I did all that I know. Each partition was reformatted. The 0115 build, open_gapps-arm-6.0-nano-20151115.zip, and SuperSu 2.52. I went through the setup and then went to Playstore and installed Newsstand. It failed as usual. Sometimes it signs in and I get the screen to select a header but as soon as I touch the screen, goes black and crashes. I tried Kindle app and it also crashes. It looks like it's working but, again, it then just fails. Something will the Newsstand or Kindle app that will make them work.

For information, Gapps open_gapps-arm-6.0-nano-20151120.zip, does not work. The setup wizard crashes. Removing Setup Wizard in TWRP the System services crashes and changing all the permissions to on, does not solve the problem. NOT USABLE!
[Nook HD, HD+ Android Development] belfastraven:
I have pages of errors from the kindle app in my logcat--and not always the same ones. I think besides memory management issues on our devices right now, there seem to be "handshake" issues with the amazon servers and also seems that the app is "spamming" logcat.. I've attached part of a logcat for your amusement. I just tried again to run newsstand, and it is fine for me. Maybe someone else on ovation can try? Perhaps the fact that the app has to write a lot more pixels /screen is exacerbating problems on ovation.

If you don't have a convenient way to look at your logs, I recommend the Syslog app from the play store. It will write the logs to a directory on your internal sdcard and send them to you, also, via various means.
[Nook HD, HD+ Android Development] Zippy Dufus:
Still building ...

Hi [MENTION=4473900]amaces[/MENTION],

I'm still having issues trying to build the ROM.

My build stops here:

Export includes file: system/core/libmincrypt/Android.mk -- /home/android/out/target/product/ovation/obj/STATIC_LIBRARIES/libmincrypt_intermediates/export_includes

Export includes file: external/e2fsprogs/lib/blkid/Android.mk -- /home/android/out/target/product/ovation/obj/STATIC_LIBRARIES/libext2_blkid_intermediates/export_includes

make: *** No rule to make target '/home/android/out/target/product/ovation/obj/STATIC_LIBRARIES/libext2_uuid_intermediates/export_includes', needed by '/home/android/out/target/product/ovation/obj/EXECUTABLES/init_intermediates/import_includes'. Stop.
​

And I think there is a mistake (or a repo has changed) in default.xml line 420.

<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" name="Christopher83/arm-cortex-linux-gnueabihf-linaro_4.9" remote="github" revision="master" groups="pdk,linux,arm" />

<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" name="Christopher83/arm-cortex_a9-linux-gnueabihf-linaro_4.9" remote="github" revision="master" groups="pdk,linux,arm" />
​

Meanwhile, I'm patiently watching your repos and trying to build when I see changes. I'm sure that you must have your hands full trying to stabilize this.

Again, thanks for your great work!
[Nook HD, HD+ Android Development] amaces:
Try force syncing now. There was a small typo in the toolchain repo name, and I had to fork vold and e2fsprogs to push my local changes. Anyway, I'll add more details tomorrow, but it should hopefully build now.
[Nook HD, HD+ Android Development] Zippy Dufus:
Closer ...

Stopped here:

target thumb C: pvrsrvinit <= hardware/ti/omap4/pvrsrvinit/pvrsrvinit.c

hardware/ti/omap4/pvrsrvinit/pvrsrvinit.c: In function 'main':

hardware/ti/omap4/pvrsrvinit/pvrsrvinit.c:5:14: warning: unused parameter 'argc' [-Wunused-parameter]

int main(int argc, char **argv)

^

hardware/ti/omap4/pvrsrvinit/pvrsrvinit.c:5:27: warning: unused parameter 'argv' [-Wunused-parameter]

int main(int argc, char **argv)

^

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

#### make failed to build some targets (03:55:03 (hh:mm:ss)) ####

real	256m34.648s

user	169m15.869s

sys	35m38.529s
​

Question, is this related to the binary firmware? I included TheMuppets repo for your CM12 build. Where does this build pull in the firmware?

Again, no hurries and thanks for your last reply!
[Nook HD, HD+ Android Development] amaces:
Good, because I was about to switch to all caps asking if you did the first GApps install on a clean slate… Once again, the correct flashing procedure is:

Normal one-step factory reset (no need for system or data format)

Install ROM, GApps, SU, etc, sequentially (just add all ZIPs to the list)

After the first boot, /data becomes "dirty". GApps discriminates between a clean and a dirty system, and has different install strategies. The first-time install has to be on a clean system for permissions, other binaries to be integrated properly. Once the system and Google setup are complete (i.e., after the first boot finishes), you can do the the dirty install without problems. Since AOSP doesn't have addon.d/backup support, and every ROM flash wipes /system, you need to always flash GApps (and SU) after every update. At some point, backup support may be ported to the AOSP ROMs, and things will become simpler.

At any rate, by formatting /data, you achieved the same clean slate, while also losing all the eMMC/sdcard content, so very much overkill.

I'll reiterate that OpenGApps were fixed two weeks ago, as described in post #3, as long as you follow the proper first-time installation procedure above.

Can't find the exact reason why Kindle was killed in the attached log. Can you attach the relevant /data/tombstones/tombstone_0x? There should be a lot more information in there. Maybe it's trying again to load at a fixed address, a stupid bug that verygreen addressed years ago (on KitKat though). I'm still hoping Amazon hasn't properly updated it's suite of apps for MM; I for one moved my EPUB library to Google Books a long time ago.

Not aware of ART/fatal memory allocation errors; if you mean YouTube, that's an OpenGL configuration issue. Either way, I don't see any other tombstones on my system, so do attach logs where you see these.

It'll be a while before we're switching to Enforcing again; the MM sepolicies are tighter, and harder for me to figure out at this point.

Once again, you don't need any extra local manifests, unless you forked your own code, or absolutely need to replace parts of the toolchain. The goal with the manifests at https://github.com/airend/android was to have everything included upon repo init & sync, and that means updated proprietary blobs as well. As of now, I forked TheMuppets repo for some firmware/DRM updates, and the SGX/PVR blobs were switched to slightly updated binaries (now in vendor/ti). Of course, the build system is kept in sync with these changes.

At any rate, I do hope you're not reusing any part of that script… nightmare fuel that one. You only need repo init, sync, lunch, and make, as emphasized a couple of posts back. I'm forced to use a slightly different but exactly equivalent setup; small errors can happen, so do let me know when things break, provided that: a) repo sync was successful, and b) you're using the normal AOSP/CM build procedure.
[Nook HD, HD+ Android Development] Minshter:
Based on your reply, I think you are misunderstanding what is being pointed out.

We had all done, repeatedly, the method you describe to install it properly, hoping to avoid the error messages. IE: Normal one-step factory reset, install Rom, GApps, SU, etc.

Yet we all kept having the error issues related to GApps, though our messages might vary to some degree. We even tried variations on the standard installation method to see if it would make a difference, to no avail.

It wasn't until belfastraven's suggestion of formatting data that it began to work, and it did so immediately. For us this method was necessary, not overkill.

Though you say formatting data gets you the same clean state as wiping data, I don't think this is correct. If it was, it wouldn't explain how formatting was the only method to repair our issue.

As far as I can tell, only 3 of us have written about this specific situation & had to use formatting to resolve it. Even though our number is small, I hope this post makes it more clear it's not a case of "you didn't follow the instructions properly", & might lead you to consider updating the OP to instruct future users should they find themselves in this difficult, albeit rare, situation. Or maybe just a link directly to belfastraven's post since it hits the main steps needed.
[Nook HD, HD+ Android Development] michisteiner:
BTW: The ANRs i mentioned are primarily ANRs from background jobs (i changed the setting in developper's tools) but i've seen also the front-app hang once or twice. Greenifying some apps though seemed to have improved the situation. So not complaining too much about it :)
[Nook HD, HD+ Android Development] theoneandonlybrooks:
I have a backup from 29t but it fails to restore during the last step. So my only option there would be to just flash the older version and start over. Is it possible to flash the older one over the newer one?
[Nook HD, HD+ Android Development] belfastraven:
Yes it is possible, I just did that but the nook app is still failing in the same manner (quiting at setting up profile...). I didn't want tot ell you to go ahead without trying it.. I think it very likely that something has changed on the B&N server side--

BTW, what error were you getting when you tried to restore your backup, and how had you backed-up/restored the system. I have been using TWRP 3.0.0-0.
[Nook HD, HD+ Android Development] ieatabiscuit:
I believe I have found the magic trick to tending to that after a lot of poking and what not on my ovation. It's tedious, but so far has worked for me 100% of the time. You need to reflash to stock ROM, AND recovery (have a rescue SD card ready). After you have FULL stock back, reboot to it's recovery (it's a very basic and small screen that simply asks if you want to factory reset). Do the factory reset from that recovery, as it repairs partitions where the reset from within the ROM won't because they are often being used. Once this is done, reflash the recovery/ROM of your choosing, and you should be good for a while. It seems that at times the partition that has the battery information gets mucked up, and after repeatedly reflashing ROMs this can restore it. As for the flashing light that won't allow it to charge... you pretty much just have to play with it to get it to charge so you can do this to get the proper behavior back. If the light is not orange then it IS NOT charging, so if it's flashing, leaving it overnight is wasting your time.
[Nook HD, HD+ Android Development] theoneandonlybrooks:
It's failing to restore data. I'm using the previous TWRP version 2.8.something. I don't have it with me to check exact number, but it's the older one a lot of people are using. I could try upgrading to 3.0 and try the restore.

Also, Play movies are still failing to play or download for me from the app. Same error, failure to fetch license. I think you can see that in the log maybe as well.
[Nook HD, HD+ Android Development] belfastraven:
I checked on the file from this statement in one of your logcats.

Could not read /data/mediadrm/IDM1013/ay64.dat2:

It there on both of my nooks, including the one on which I reflashed the 1/29 rom.

It makes me think that there is something not quite right with your data partition . Perhaps the restore of data did partially succeed. If you want to get back to the 2/22 rom, it might be best to make sure you have a backup of apps that are not available in the play store, and then to flash the 3.0.0-0 recovery, use the recovery to do a factory reset, then flash the rom , then opengapps, without wiping anything in between or after the flash, and rebooting. It means you need to set everything up again, but at worst you can go to the play store and choose all of your apps from there to download and install at one time and put back the nook app (which still won't work--as I have indicated) .

I try the nook app a couple of times a day, btw, just to see if something has changed on the server side so that it works again... and will of course let you know when/if it begins to work.
[Nook HD, HD+ Android Development] bobshaw:
Nook app

I was able to get the side loaded nook app to work by doing the following.

1.install the app

2. Sideload a book into the my documents folder.

3. Use the app as guest or whatever (don't setup profile) and open up your book pretend to read ...

4. Close the app and swipe it away maybe reboot too

5. Reopen app and login with profile - mine crashed after credit card screen

6. Reopened app again and I was logged in

I've deleted mine twice now and was able to get it to work.

Cheers

PS realized what thread this is in and apologize for straying off topic. Please move me

---------- Post added at 04:29 AM ---------- Previous post was at 04:16 AM ----------

Pps Amazing work on this ROM. Haven't flashed anything in a couple years and was pleasantly surprised the life this ROM breathed into my tablet. Thank you for all you do
[Nook HD, HD+ Android Development] belfastraven:
Thanks for this info--I mentioning [MENTION=7223311]theoneandonlybrooks[/MENTION] who is the one having the problem. What rom are you running on? Are you using the 2/22?

---------- Post added at 04:29 AM ---------- Previous post was at 04:16 AM ----------

[/COLOR]

Pps Amazing work on this ROM. Haven't flashed anything in a couple years and was pleasantly surprised the life this ROM breathed into my tablet. Thank you for all you do[/QUOTE]
[Nook HD, HD+ Android Development] theoneandonlybrooks:
I'm on the 2-22 CM rom, and it has restored fine from a backup. It's the earlier 29T rom that fails to restore. As a note, similar to what someone else proposed, I can open a pdf with Nook and it works fine, but if I tried to back up it hangs in the same spot. I will try closer to his recommendation tonight and see if it works.
[Nook HD, HD+ Android Development] aoleary:
Is it OK to dirty flash the CM13 builds?
[Nook HD, HD+ Android Development] bobshaw:
I am running 2-22 and I guess I'm confused on the question ( blame it on jet lag) I thought the issue was getting the nook app to login? But now I see this stuff about backing up... We should move elsewhere for this I believe.
[Nook HD, HD+ Android Development] lavero.burgos:
I found a bug in the 2-08 build. The keyboard acts weird sometimes. Like if I type any letter or even the space bar it would type 'o' or I want to delete (backspace) it would do nothing or type more 'o'. If I remove the app I was using the keyboard with from recent apps and open it again, keyboard then works properly again.

Enviado desde mi ghost mediante Tapatalk
[Nook HD, HD+ Android Development] mmnspeed:
Is there any way to use some other recent apps menu other than the cards menu of android 6.0?It is the only thing that I find a bit annoying in this otherwise perfect ROM.I tried switchr, but turns out the developer hasn 't been able to make it work with lollipop and versions after that.
[Nook HD, HD+ Android Development] acr123:
swiftly switch is I think an upgrade to switchr that you may want to try.