yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] ImeBob:
Thanks, I was thinking of that, but would have never thought of the stock recovery reset. After it booted still would not charge, but on a whim I pluged the charger multipel times and it charged. Next day didn't want to turn on, but I booted from the sd and installed twrp and Feb 22 rom reverted back to no charge same as before. I read that doing a "hard reset" after stock would rebuild the partitions, but it would not turn on at all with a stock version of the rom on the sd card. With the 08 rom on the sd it booted and I formated everything installing twrp, rom and gapps. Everthing is back to normal charging and booting. It would be an understatment to say I am baffled. I guess for now I am stuck on the 08 rom. When the genius of amaces solves the shutdown I will try adb.

Bob
[Nook HD, HD+ Android Development] highlandsun:
If anyone is interested, I managed to get OpenCL 1.1 drivers working on this. I used libPVROCL.so and liboclcompiler.so from a Samsung build (which also uses SGX544). There are a couple simple tricks and one less obvious to get it to work, all in /system/vendor/lib:

copy the 2 new libraries into /system/vendor/lib

symlink from libIMGegl_SGX544_112.so to libIMGegl.so

symlink from libusc_SGX544_112.so to libusc.so

The tricky part - libPVROCL.so wants libsrv_um.so, but this particular libPVROCL.so was built with debug options, and it wants to reference a PVRSRVDebugPrintf() function which doesn't exist in our libsrv_um_SGX544_112.so file. I got around that by writing a dummy wrapper:

debug.c

void PVRSRVDebugPrintf(unsigned level, const char *file, unsigned line, const char *format, ...){}

Compile this with arm-linux-gnueabihf-gcc, link against libsrv_um_SGX544_112.so into a new shared library libsrv_um.so:

arm-linux-gnueabihf-gcc -c -fPIC debug.c
arm-linux-gnueabihf-ld -shared -o libsrv_um.so debug.o libsrv_um_SGX544_112.so

Also, liboclcompiler.so needs /system/lib/libstlport.so which I also grabbed from another Android image.

That's it.

... for the impatient, just make /system writable and then extract this tarball there. It has the libraries and the symlinks already set.

... the performance is nothing great here.
[Nook HD, HD+ Android Development] justwondering:
Hi , I seem to be having a issue with the latest hummingbird release of the rom , whenever I close the system down / power off , it never closes down , it just reboots each time..

Any way to fix this problem ?
[Nook HD, HD+ Android Development] acr123:
Try and close down from recovery & see if that helps
[Nook HD, HD+ Android Development] belfastraven:
Using the same benchmark, running twice, I've gotten 4.72 and 4.79 on hummingbird.

It may be wishful thinking on my part, but Chrome_dev does seem a little bit "zippier". Do you happen to know what other apps are built using openCL now?
[Nook HD, HD+ Android Development] highlandsun:
There are very few at the moment. My interest is in building a Monero miner. Currently we have an OpenCL miner for AMD GPUs https://github.com/hyc/wolf-xmr-miner which I've been hacking on in my spare time. Getting this to work on OMAP4 was really just out of curiosity, my real target is ARMv8 devices (I have a Geekbox and Ugoos UT4, both RK3368 chips with 8xCortex-A53 in them. Also have a Pine64 on the way, Allwinner 4xCortex-A53.).

Looking thru that benchmark's database, it seems there's very few devices with OpenCL enabled at all. TI certainly didn't help on this score, by omitting the OpenCL libraries from the multitude of devices that used their OMAP4 chips. It took me several days to find a set of libraries that would actually work.
[Nook HD, HD+ Android Development] uberchoc:
Sleep of Death

Hi all. Again, thank you for all your help. So, I've done some reading here and there and come to know that what I'm experiencing is called the Sleep of Death, which, it turns out, isn't uncommon to Android devices. Also, it seems to be device-specific and not necessarily brand-specific, so two people could have the same device with essentially similar parameters, and one would suffer from the SoD while the other wouldn't.

So, problem half solved. It could boil down to a number of factors, but I've done some eliminating and I think it's a Wi-Fi problem. While some have advocated modifying the kernel to fix this, others say to flash a custom Wi-Fi module alongside your kernel. Please, can someone help me look into this? I tried an app to prevent it from going to deep sleep but even that didn't always work.

I would return the tablet but it turns out the window has closed. Besides, I live too far away from the U.S. to fret *that* much over a $60 tablet. Anyhow, I like it so much I'm considering ordering for another!

(Sleep of Death is such a badass name, BTW.)
[Nook HD, HD+ Android Development] belfastraven:
If you think it may be wifi, have you tried running with WiFi off for a day? What made you think that it was wifi? Are you using bluetooth, btw?

Also, does it do this when it is plugged into power?

Does it happen if you are in recovery?

We didn't really see much of help in the logs before, I think.

Perhaps others can come up with more questions/suggestions for you, too.

I always wondered if "Sleep of Death" came from Shakespeare's Hamlet-- "

For in that sleep of death, what dreams may come,

When we have shuffled off this mortal coil,

Must give us pause"

After all our devices do "dream" :)
[Nook HD, HD+ Android Development] theoneandonlybrooks:
I was trying to do this, but Barnes and Noble won't let me download books to my pc to try. I did do this with a pdf though to no avail. It reads the pdf fine, but that's it.

---------- Post added at 09:20 PM ---------- Previous post was at 09:19 PM ----------

Sorry it's been a busy few days. I work for the Illinois Senate, have a side business and two kids, and all of them got busy at the same time. I put the 29T rom onto my sd card, I'm going to try to flash it, start from scratch, and go from there.
[Nook HD, HD+ Android Development] ibr4him:
Just installed this ROM, so far looks good and everything seems to work, just a couple questions:

- any major known issues?

- is it stable for use a daily driver?

- I can't close screen with power buttons, nor can I use it turn on, bug or?

Thanks!
[Nook HD, HD+ Android Development] uberchoc:
Yes, I have. Wi-Fi off, Wi-Fi on. I might be dreaming it, but I think it occurs less often

when Wi-Fi is off, and set to always keep on during sleep; more recently though, I've set

it to never keep on during sleep, and I'm monitoring to see what difference it makes.

As regards bluetooth, I hardly ever use it.

Sometimes, when I pull up the app switcher, it sort of "crashes" and takes me to the lock

screen. I wonder if that is a related issue.

Yes, it happens even when plugged into power.

I've never been able to get it to happen whilst in recovery. I've tried. Safe to say it

never happens in recovery.

Aha, yes, regarding the logs, whenever it happens, I pull up Syslog and take a log, and

around the time it happens, the logcat always shows a message about an input event using

the wrong clock source.

I would hope others come up with more questions/suggestions for me; yes please. I wonder

in fact how it is that I seem to be the only one in this community affected by this

phenomenon. It makes me wonder if I'm doing something wrong. I just might have to revert

to stock, kernel and all, once more, and start from scratch--use it like so for a few

days, see what happens.

Ooh, thank you for this Shakespeare reference. Sadly, I only ever read him as a kid;

abridged compilations. (THE HORROR.) My mum though, she quotes him like she knew him. Just

the other day, I was stalling about some decision, and she hit me with "There is a tide in

the affairs of men. ..."
[Nook HD, HD+ Android Development] theoneandonlybrooks:
I did a factory restore, flashed 29T, booted and then installed an existing copy of the nook app from my sd card. It works great! However, I forgot and didn't flash gapps. The play store is on there though. Should I just download stuff or start over and remember to flash gapps? Am I missing some functionality if I don't flash gapps?
[Nook HD, HD+ Android Development] theoneandonlybrooks:
I started over again and installed pico gapps. Nook is again working great. So what could've changed?
[Nook HD, HD+ Android Development] belfastraven:
Lots of things actually, since the CyanogenMod rom is contantly changing (not only by our builder) :). Just to be clear, are you now running the 1/29 cm13 build with a recent pico gapps?
[Nook HD, HD+ Android Development] theoneandonlybrooks:
​

Yes. Open gapps Pico for arm 6.0

I think I downloaded the gapps a couple weeks ago.

I'm going to do a backup of this version so I can easily go back after trying the next version. If I have to choose between nook and Google play I will take nook. Hopefully in a future version I don't have to choose.

Should I run a logcat to see what's different?
[Nook HD, HD+ Android Development] belfastraven:
N:)o need, right now. In my logcat , the app doesn't seem to be able to find a particular java component. If I side load something as [MENTION=3418019]bobshaw[/MENTION] suggested and perform the actions he advised, I can read my document. If I try to buy something, the app quits. I will test on new builds and let you know as soon as things are back to working.
[Nook HD, HD+ Android Development] theoneandonlybrooks:
I was able to use nook as a pdf reader on the newer builds, but could never get past the setting up profile part when trying to do something else.

Did you send the tombstones to amaces or should I try to reinstall 2-22 and do it?
[Nook HD, HD+ Android Development] dxxvi:
Smoother, lighter than CM12?

To all people who already used AOSP/CM13 on the nook hd+, do you think it's smoother, lighter than CM12?
[Nook HD, HD+ Android Development] acr123:
I find CM13 more responsive than 12. Not sure what you mean by lighter. Only minor annoyance is unable to power off from menu ( Nook reboots) and need to go to TWRP and power off.
[Nook HD, HD+ Android Development] BultoPaco:
You shouldn't need to go to recovery to power off. Try holding the power button in until the power menu disappears and the screen is blank -- should be completely shut down. Works on both my ovation and hummingbird.
[Nook HD, HD+ Android Development] acr123:
Thanks. Worked perfectly
[Nook HD, HD+ Android Development] sasmith-129:
I certainly prefer CM13 over CM12 (which I used daily for over 6 months last year) on my ovation/Nook HD+.

The 02/22 CM13 build seems to be the smoothest yet and application performance seems better than ever.

Amazing work by [MENTION=4473900]amaces[/MENTION]!
[Nook HD, HD+ Android Development] dxxvi:
Could anybody please tell me the link to download?
[Nook HD, HD+ Android Development] BultoPaco:
As noted in the first post of this thread, [MENTION=4473900]amaces[/MENTION] has a link to the CM12 & CM13 files in the first post of his CM12 thread.
[Nook HD, HD+ Android Development] acr123:
download links also on page 1 of this thread.
[Nook HD, HD+ Android Development] dxxvi:
For most of the times after a reboot, my nook HD+ doesn't recognize the SD card. This didn't happen to me with cm12. Don't know if it's a software or hardware issue. When it happens, I turn off the tablet, take the sd card out, clean it, put it in, turn on the device and hope I can see it (but most of the time it doesn't work).

Yesterday, when the sd card can be seen, ES File Explorer v3 cannot write anything to it, but I could create a directory with adb shell and upload file to the sd card with adb push.

One more issue: my cm13 doesn't have root even though after I installed SuperSU 2.65 in twrp 3.0.0.0.

Does anybody know how to solve the issues that I have?

Thanks.
[Nook HD, HD+ Android Development] DerNetzreporter:
The ES File Explorer Problem seems to be an error of v3. On my Asus Zenfone 2 I have the same problem. Other file explorer dont have this problem.

I have root access, I used this file: UPDATE-SuperSU-v2.46.zip

But I have an "old" problem. The right side of the display is "jumping" up and down when I hold a finger on it. For version 10.1 (I guess) there was a hotfix for this problem. Is there such a solution for cm_ovation-ota-MMB29U.160222 ?

Which version of xposed framework is working with this build?
[Nook HD, HD+ Android Development] neutronjeff:
Not sure what to say. My ovation with a fresh clean install of the Feb22 build is seeing my SD fine. Also, I am able to grant ES File explorer root browser permission with the built in Root setting. I'm also on [MENTION=4473900]amaces[/MENTION] TWRP 3.0.
[Nook HD, HD+ Android Development] DerNetzreporter:
any infos which xposed version works?
[Nook HD, HD+ Android Development] Monfro:
New AOSP build appeared in experimental folder...my Ovation was waiting this new ROM since 3+4 February...It is flashing addicted :)

Thank you Amaces!!
[Nook HD, HD+ Android Development] DE-Nooker:
SuperSU won't root any device if it is not rooted (before). CM doesn't really need SuperSU, as it already has a SuperSU "light" pre-installed. The "not rooted" problem is a known one on some devices running CM. Just go to Developers Setting, disable root access and enable again with preferred settings.
[Nook HD, HD+ Android Development] Zippy Dufus:
Build error

Hello [MENTION=4473900]amaces[/MENTION] / home builders,

So I haven't built this ROM for over a week ;) and now I run into the following problems:

The build terminated looking for a command called mvn. I deternined that I needed to install a package called maven on my Fedora23 build virtual machine.

Maven complained about not having the $JAVA_HOME set up - fixed.

The build terminated with the error below.

I'm not sure if the problems are related.

This is a straight build so I am not doing anything funky with different toolchains, etc.

Any ideas?

30 warnings and 1 error generated.

build/core/binary.mk:828: recipe for target '/home/android/out/target/product/ovation/obj/STATIC_LIBRARIES/libtoybox_intermediates/lib/args.o' failed

make: *** [/home/android/out/target/product/ovation/obj/STATIC_LIBRARIES/libtoybox_intermediates/lib/args.o] Error 1

make: *** Waiting for unfinished jobs....

In file included from external/toybox/lib/dirtree.c:6:

In file included from external/toybox/toys.h:31:

bionic/libc/include/string.h:119:14: error: conflicting types for 'basename'

extern char* basename(const char*) __RENAME(__gnu_basename) __nonnull((1));

^

external/toybox/lib/portability.h:171:7: note: previous declaration is here

char *basename(char *path);

​
[Nook HD, HD+ Android Development] Monfro:
+60MB of ram available

Smoothness improved

No bugs introduced

This is a great update for Marshmallow AOSP rom
[Nook HD, HD+ Android Development] sasmith-129:
One issue i just discovered on CM13 02-22 is that HDMI output no longer seems to work. Bummer!

I last used HDMI output (successfully) at the end of January so that would have been one of the January builds, 01-10, 01-17, 01-24, or 01-27. Sorry I'm not sure which build I was on then.
[Nook HD, HD+ Android Development] belfastraven:
I too had to install the maven package in order to build Ubuntu, 16.04, but have successfully built just now. If you haven't re-inited the repo , I suggest you do that. The mismatch in definitions should have nothing to do with maven, but rather with mismatches in versions of various code, or something in the compile instructions, I think.

This is actually the code in my string.h

#if defined(__USE_GNU) && !defined(basename)

/*

* glibc has a basename in <string.h> that's different to the POSIX one in <libgen.h>.

* It doesn't modify its argument, and in C++ it's const-correct.

*/

#if defined(__cplusplus)

extern "C++" char* basename(char*) __RENAME(__gnu_basename) __nonnull((1));

extern "C++" const char* basename(const char*) __RENAME(__gnu_basename) __nonnull((1));

#else

extern char* basename(const char*) __RENAME(__gnu_basename) __nonnull((1));

#endif

#endif

Amaces has made lots of changes to his github in the last week,, so it's probably a good idea to re-init.
[Nook HD, HD+ Android Development] fddm:
Just want to say thanks to amaces, I've been running the aosp 160204 build and it's incredible. No issues with hardware overlays or random rebooting and app compatibility is very near cm11. Very easily the best rom ever released for the Nook HD+.
[Nook HD, HD+ Android Development] Zippy Dufus:
Thanks for the response.

One clarifying question, when you say "re-inited the repo", do you simply mean execute "repo init" or deleting the .repo directory and downloading everything again?
[Nook HD, HD+ Android Development] belfastraven:
I normally just repo init and then sync without deleting. Be aware when I built earlier today, cm13, I had no problem compiling but no WiFi either :). I just synced and built again, and will test: I couldn't tell whether anything important has changed. I don't want to bother amaces with this right now, but I'll let you know whether I have WiFi or not. At least, you can make sure you can compile again.
[Nook HD, HD+ Android Development] Khord:
When I try to full-screen videos in chrome, it doesn't fully expand and has a bunch of color noise around the blank areas. Anyone know if there is a fix for this?
[Nook HD, HD+ Android Development] Zippy Dufus:
I finally got a successful build - 03/12 - but wifi is still broken.

I wonder if it is the same problem that the Nook Tablet is having?

At least I am happy that my build environment is OK.
[Nook HD, HD+ Android Development] belfastraven:
Based on the error message I get I think we have different or, at least, additional issues. There were changes made in the wifi code in the repository a few days ago.. Remember, amaces had indicated that the repository would be in good shape for building when he built, so if you don't want to keep trying, wait until there is a new CM13 build from him.
[Nook HD, HD+ Android Development] neutronjeff:
Does [MENTION=4473900]amaces[/MENTION] ASOP require SuperSU? If so, wich one should be used? Thanks.
[Nook HD, HD+ Android Development] ieatabiscuit:
Yes, you will have to flash super su for the AOSP builds. I ran into issues flashing the latest, after flashing an older version, it updated from the play store flawlessly for me.
[Nook HD, HD+ Android Development] belfastraven:
If you re-init and sync now (I re-init because I know that lots of changes, unforks, etc are happening in the repository and I want to make sure I have the correct default xml) you will have wifi. amaces already has the fix in for the toybox issue, as well as other wifi changes. I'm sure things are still changing, but if you are anxious to try, you will at least have WiFi now.
[Nook HD, HD+ Android Development] Zippy Dufus:
Do you know if this is a problem with my local repo/environment or a general problem with the remote repos?

I was getting other errors so I added the --force-sync and -j1. So now I am down to the errors shown below.

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

repo sync -j1 --force-sync

...

Fetching project CyanogenMod/android_packages_wallpapers_PhaseBeam

Fetching project CyanogenModerror: cannot lock ref 'refs/tags/android-6.0.1_r22': unable to resolve reference refs/tags/android-6.0.1_r22: Invalid argument

From https://android.googlesource.com/platform/prebuilts/maven_repo/android

! [new tag] android-6.0.1_r22 -> android-6.0.1_r22 (unable to update local ref)

error: cannot lock ref 'refs/tags/android-6.0.1_r22': unable to resolve reference refs/tags/android-6.0.1_r22: Invalid argument

From https://android.googlesource.com/platform/prebuilts/maven_repo/android

! [new tag] android-6.0.1_r22 -> android-6.0.1_r22 (unable to update local ref)

error: Cannot fetch platform/prebuilts/maven_repo/android

error: Exited sync due to fetch errors

/android_packages_providers_CalendarProvider

Fetching project CyanogenMod/android_libcore

Fetching project CyanogenMod/android_packages_providers_UserDictionaryProvider

...

​
[Nook HD, HD+ Android Development] belfastraven:
I just now synced again with no problem --didn't re-init or anything. I'd try syncing again now--perhaps there was a problem on github earlier, or perhaps amaces was working on something. It's hard for me to tell, and since I can't replicate your issue ,I'm not sure how else to advise you. If you wait until amaces builds again, and then re-init the repo and resync and you still get errors, you can be pretty sure it's something in your build environment :). From looking around on the web, it seems the error has something to do with a mismatched branch name or a git permission problem. Funny that's it's the "maven" stuff again.

When you "inited" did you get the normal message back? I know that 6.01_r22 is a new branch... If all else fails, you could delete your current environment and re-init. I takes much longer for me to do an initial sync/download than it does to build.. so I do it very rarely.
[Nook HD, HD+ Android Development] belfastraven:
New 3/14 cm build runs well on hummingbird

Has any one else noticed the handy "apps started on boot" section under "memory" in settings> It seems to give information on how apps use various services, also.

Nook app is unfortunately still not working, but is throwing off more error messages now, so perhaps we can figure out if there is anything we can change on our side. (see lines starting near 3330--tombstone appears to be from a different issue)
[Nook HD, HD+ Android Development] :
Thanks amaces. i can confirm that pico gapps now work on aosp.
[Nook HD, HD+ Android Development] Zippy Dufus:
Thanks for the help.

It is looking like my environment needs an "enema" (delete .repo and download everything).

Another complicating factor is that, while I build on a virtual machine, this is the first attempt to build on new computer that I cobbled together and still shaking the bugs out. At one point, I left two such VMs building at the same time over night and I think that it got hot and rebooted. I've damaged VM filesystems with abrupt halts before. :cowboy:
[Nook HD, HD+ Android Development] belfastraven:
Um...yes if your build process was in progress when you tried to sync, some of your files may very well have been locked and inaccessible...

Although we should be able to ask one another anything here, I agree with amaces that it's important not to confuse others who may be seeing these interchanges. We wouldn't want other new builders to become even more confused... :)
[Nook HD, HD+ Android Development] king200:
New 3/14 cm build runs well on Ovation

I flashed the build with Open Gapps Nano and did no wipe. No problem.
[Nook HD, HD+ Android Development] acr123:
Did you have a somewhat earlier version to comment on any differences.

Thanks,

Al
[Nook HD, HD+ Android Development] mdonahuerib:
Hi,

Nook app seems to work flawlessly on the last AOSP build (on Ovation). Except for Nook video content, which fails to play. On the other hand, Google Play Movies works perfects (unlike on the last CM13 build I tried (next-to-latest build). On CM13 I had to fall back to an older Nook APK I had lying around.
[Nook HD, HD+ Android Development] extrem0:
Barnes and Noble shutted down their video service. They're only working with ebooks now.

Source: http://www.androidpolice.com/2016/0...s-but-will-continue-selling-ebooks-in-the-us/
[Nook HD, HD+ Android Development] belfastraven:
which version of the APK is working?
[Nook HD, HD+ Android Development] mdonahuerib:
You can try 3.5.3.5 from July 2015 (may work, can't remember) but versions from September 2014 work for sure (on Ovation). The UI is less fancy but for reading books it's just fine. Comics have improved in the last couple of versions (using the full screen as they do on the stock Nook HD ROM).

Good luck! I really recommend the AOSP build - it's the first time I try one but I'm sold. Far more available memory = much more responsive. The only issue I have is touch screen sensitivity (or lack thereof), but I've had that on every non-stock build since the beginning.