yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] i9000usersa:
No, but then again, I don't really want to. I want my apps to update in the background, so that when I turn it on it's ready to go, and have push notifications. That is how the stock ROM works, right? If I'm completely honest, I don't need it that much, but it is bothering me because it tells me that the tablet is not functioning like it is supposed to. If there is a fix I would like to know. If there isn't may be my post can help the devs to fix it.
[Nook HD, HD+ Android Development] recnamoruen:
Any chance you could upload that somewhere, I can't seem to get them to build

properly.
[Nook HD, HD+ Android Development] ajislav:
I will try, but I am offline now so Monday at earliest. Maybe in the meantime you could post your build errors and somebody might be able to help you..

BTW for me, the most difficult part was getting the repositories right: I overlooked the fact that hardware_ti_omap4 is sourced from amaces (airend) not from LNOS.

In addition I had to remove one overlay file, but that was all...
[Nook HD, HD+ Android Development] ejstubbs:
Root for AOSP Marshmallow

OK, so I've had to give up on the CM Marshmallow ROM because there doesn't seem to be any solution to the choppy audio problem.

So I've been trying AOSP today. Woohoo, the audio is OK. Boohoo, there doesn't appear to be any way to get root. Reading elsewhere on this thread suggested that simply installing PHH's SuperSU from the Play Store would do it. Not for me it didn't.

I tried rebooting and got a notification that the SU binary is out of date. How do I update it, given that (AIUI) it's baked in to the ROM?
[Nook HD, HD+ Android Development] digixmax:
Have you tried looking for "Root" in "Developer Options"? See https://xdaforums.com/showpost.php?p=70471533&postcount=1542.
[Nook HD, HD+ Android Development] recnamoruen:
I've been using a virtual machine to build, I get around 25% and it runs out of memory. I would have to change the java settings, and I'm not really sure about how to go about it.
[Nook HD, HD+ Android Development] belfastraven:
I may be getting confused about versions, but I don't think that root was built into the marshmallow roms, only the Nougat roms. You may indeed need to install a superuser binary into the AOSP marshmallow rom. I hope someone else jumps in here... or you may one to try a Nougat AOSP build.....
[Nook HD, HD+ Android Development] neutronjeff:
Quote:

correct! after each flash you need to resize with TWRP (IF... THE ROM HAS A FLASHING SCRIPT IS FAULTY).

but for reasons too long to explain here, i recommend this sequence instead:

wipe /system, flash rom, resize system with TWRP button, flash gapps.

-------------------------------------------

After running the two repit scripts, I cant get the lnos_ovation-ota-NMF26Q.170104 to flash. using twrp 3.0.2.

I wiped /system as recommended and get the same error messages.

I get:

E1001: Failed to update system image.

E: unknown comand [log]

E: unknown comand [log]

Updater process ended with ERROR: 7

Error installing zip file...

What am I doing wrong? Not sure what to try now.
[Nook HD, HD+ Android Development] NE0HP:
I think E: unknown command [log] error is due to official TWRP 3.0.2.0. Try using latest 3.0.3.0 TWRP(Ovation) from experimental folder to flash LNOS rom and you will not get that error.

And E1001: Failed to update system image error might be due to corrupt LNOS downloaded file so I suggest you to download LNOS Ovation ROM again and do clean install.
[Nook HD, HD+ Android Development] neutronjeff:
Hey, thanks. Fresh download worked fine.
[Nook HD, HD+ Android Development] Tonto87:
I had the same problem with CM11 or CM12 (I can't quite remember) - it would slow down to be unusable. But with this ROM it (so far) doesn't seem to slow down at all.
[Nook HD, HD+ Android Development] ejstubbs:
Unfortunately I've not yet managed to get a reliably usable version of Marshmallow or Nougat installed (see my earlier post about the choppy audio issue with CM13, still unresolved). As a result, I've not been able to confirm whether or not either version is less prone to slowdowns.

However, I have found this app on the play store which does appear to run fstrim on demand on MM. So if I do end up seeing lag, I may be able to do something about it - which is reassuring :)
[Nook HD, HD+ Android Development] ejstubbs:
I looked for it, but it wasn't there!

Thanks for that guidance. I have now successfully installed CM14, which has root, and doesn't have the audio playback problem. I may have to experiment with AOSP Marshmallow again soon, though: one app that I use quite a lot doesn't seem to like Nougat. I have got Chainfire's SU binary ready to install when I do that.

One thing I wasn't so keen on about AOSP was the apparent lack of a reboot option on the power menu. Is it a configuration option somewhere in Settings?
[Nook HD, HD+ Android Development] belfastraven:
That is actually a feature of CM/Lineage; it is not available in the current AOSP roms here. You can reboot/reboot recovery through the terminal or through apps which are available on the play store..
[Nook HD, HD+ Android Development] ejstubbs:
So I now gather. I've heard that Google are opposed to it, and that Sony submitted a patch to fix it as a "bug" but Google won't have it. Oh well.

I have now had another go at CM13 and this time it seems to be much less prone to the audio problem. It does still occur very occasionally, but most of the time it's fine. So now I seem have the choice of CM Marshmallow or Nougat. Hmm, decisions, decisions...
[Nook HD, HD+ Android Development] ajislav:
Have you tried decreasing the number of threads the build command "make" uses using the -j command, see e.g. here http://elinux.org/Android_Build_System#Speeding_up_the_build

See PM for my LNOS13.1 build
[Nook HD, HD+ Android Development] neutronjeff:
Are you playing music from a SD card, from emmc, or over wi-fi from another source? Format is MP3s..?
[Nook HD, HD+ Android Development] ejstubbs:
MP3s from the SD card, MP4 videos from internal storage.

Nougat (CM14) doesn't seem to exhibit the problem. Marshmallow (CM13) does - though it seems to happen less frequently now I've done a 'clean' install. But it does still happen, and it's annoying!
[Nook HD, HD+ Android Development] recnamoruen:
Yeah, I tried setting the thread to 1 and even gave it most of my system memory. Issue still occurs.
[Nook HD, HD+ Android Development] jernyx:
First, huge thanks to amaces for his builds and to everyone else who contributed. I've been using the experimental LNOS ovation build and his TWRP build and they've been working very well. My Nook has been greatly improved by your work.

I don't want to be that person impatiently asking "when will we have this build" but I noticed that ovation was initially included in the list of devices getting an official one, but hasn't been mentioned elsewhere on the LNOS site except for a couple commits on Gerritt. It makes sense that it would be a lower priority, and I was just curious if an official build was still planned? Either way, the current build is working fine and many thanks again for all the work you've done which has greatly improved this device over the stock rom.
[Nook HD, HD+ Android Development] Goggles2114:
I don't really want to sound like I'm rushing the folks doing actual work here but any word on new hummingbird builds? Possibly including not having the whole screen flip issue? That one really does bug me since several APS (reddit. Aldiko, and others) do not allow reorientation.
[Nook HD, HD+ Android Development] neonleon29:
I am currently on AOSP MM. The way I got root was by using SuperSu in system mode. The link was originally posted by Denooker. Here is the link: https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

As for the power menu, I installed exposed and then a module called APM+. Another module to customize AOSP would be Gravity Box.
[Nook HD, HD+ Android Development] ejstubbs:
Thanks. I have the SuperSU 2.46 zip but the versions in that link look much more recent.

I don't like xposed so I'll live with the power menu as is.
[Nook HD, HD+ Android Development] Anatinae:
Any chance of getting HDMI adapter working again with LineageOS? I'm running the 20160222 build of CM13, the last I believe that worked with HDMI.
[Nook HD, HD+ Android Development] kind of android newbie:
Shutdown Problem?

Noticed shutdown problem with Amaces's NFM26Q Ovation Lineage OS (Jan 4 2017) build after fresh install. Nook HD+ will reboot automatically after shutdown. Is this also a problem with the associated ASOP build? Is there a fix I could implement?
[Nook HD, HD+ Android Development] mikeataol:
I believe that the shutdown (and it reboots), , and choosing reboot (and it reboots to recovery in error) is common across all the current roms....
[Nook HD, HD+ Android Development] ieatabiscuit:
Yes it did do it on AOSP. I personally like it though, is just a poorly labeled APM for me because I don't turn mine off.
[Nook HD, HD+ Android Development] neutronjeff:
This has been a "problem" for a while. If you continue to hold the power button beyond when the soft menu appears, it will actually shut down.
[Nook HD, HD+ Android Development] joefidler:
Thanks

Well thanks for nothing! Had just convinced the wife it was time to replace my aging NookHD, went onto XDA to find a way to wipe it and found this thread. In a "flash" the old Nook is fast, stable and shiny new (Jan 4 Hummingbird Lineage NMF26Q build). The high battery drain due to keeping the WiFi on all the time so it does not loose its SSID is a nuisance, but it looks like the Nook will be keeper for a while longer. Cheers and thanks to all involved for your work on this. ;)
[Nook HD, HD+ Android Development] lip008:
I dug out the HD+ after a few years of it collecting dust. After a long time charging it was a flash from the past seeing Slimbean. Came here to be shocked at all the development as the device lives on. I'm gonna give it a flashing of something, but I'm a bit confused. I'm used to finding the build on the main page from the OP for other devices. Here it looks like the files are hosted on Uni of Notre Dame. Which if the case is fine....but I'm not sure what to grab. Hummingbird.....Ovation...Acclaim? Appreciate any recommendations.
[Nook HD, HD+ Android Development] mikeataol:
Acclaim=original Nook Tablet 7"

Hummingbird=Nook HD

Ovation=Nook HD+

the AOSP versions are leaner meaner, less themed than CM based, but I prefer them.
[Nook HD, HD+ Android Development] lip008:
Excellent! Thanks!
[Nook HD, HD+ Android Development] neutronjeff:
I've been looking, but I don't see any performance settings. Am I missing them somewhere?
[Nook HD, HD+ Android Development] mikeataol:
what device? what rom?

I usually install kernel adiutor (root) if the rom needs say clocking up....
[Nook HD, HD+ Android Development] neutronjeff:
Sorry, right, Ovation on LnOS.
[Nook HD, HD+ Android Development] pyoungworth:
What settings do you use on kernel adiutor?
[Nook HD, HD+ Android Development] andrerz:
I have both Hummingbird and Ovation devices to test with and am keen to get stuck in the source code to see if I can fix some of the more obvious bugs in the Nook builds. But after several days stuck here, I need help because.....

AMACES Hummingbird CM14 and AOSP branches do not appear to be buildable anymore. Can someone confirm?

I'm running builduntuvm in virtual box on Windows 10 with 6.7Gb memory made available, updated and prepared as per Harry Youd's and other LineageOS build blogs/guides.

I can repo init and sync all AMACES branches successfully and build a CM13 rom. However CM14/AOSP builds fails in the same place.

I dont know enough to trace where the problem is, maybe this helps

In file included from hardware/ti/omap4/libtiutils/DebugUtils.cpp:17:

In file included from hardware/ti/omap4/libtiutils/DebugUtils.h:21:

In file included from system/core/include/utils/threads.h:35:

In file included from system/core/include/utils/Thread.h:31:

system/core/include/utils/RefBase.h:20:10: fatal error: 'atomic' file not found

#include <atomic>

^

1 error generated.
[Nook HD, HD+ Android Development] belfastraven:
It seems that somehow that line

#include <atomic> may have gotten corrupted. The repositories, both [MENTION=4473900]amaces[/MENTION] and the lineageos version indeed say that, whereas the earlier repositories e.g. cm-13/marshmallow say

#include <cutils/atomic.h>

The atomic.h file is indeed there, at system/core/include/cutils/atomic.h.

so if you just edit that Refbase.h file with the mistaken #include in it to say

#include <cutils/atomic.h>

you should be able to build. I will see what we can do to get the repository fixed.
[Nook HD, HD+ Android Development] andrerz:
I had already tried that, but just throws more errrors earlier.

There are several files in the working tree (also cm13) with #include <atomic> e.g. In bionic/libc/include/stdatomic.h , there is a comment that "We have a usuable C++ atomic; use it instead", so I'm thinking it might be a make file or path error.
[Nook HD, HD+ Android Development] belfastraven:
Yes--I ater looked further and found that that change was legitimate and had been made about 10 months ago in the AOSP repository. (I don't do much cpp programming--obviously---) Amacves thought it might be a toolchain error, but I thought the error was thrown from the compilation of a cpp program using one of the standard toolchains, so it puzzled me because I had just built myself earlier in the day, with no problems. I was compiling on linux with ubuntu xenial. Some research on the web shows that the particuar error of not finding atomic is often caused by the cpp compiler not being configured properly--that is, it is missing the cpxx11 configuration. You can look up c++11 (or cxx11) and android on the web and get info about this. If this is a cross-compiler cpp problem, I am curious as to why you are getting it and I'm not. I will try a clean build today.

I wonder whether this has happened to anyone else?
[Nook HD, HD+ Android Development] belfastraven:
I just compiled lineagos 14.1 using the amaces standard repositories.

Here is the compilation line from the build output at which your build seemed to fail.

[ 83% 28420/34147] target thumb C++: libtiutils <= hardware/ti/omap4/libtiutils/DebugUtils.cpp

Are you seeing that same

"target thumb c++: " at that point in your build?
[Nook HD, HD+ Android Development] belfastraven:
That long first "paragraph" after FAILED: is telling you which build command failed, then, after that showing you the particular error that caused it to fail...

I can see from your build output that this is not a "clean" build. Have you ever done a clean build for nougat/lineage14.1.? I mean, when you first built for 14 after the builds, did you ever do a make clean and clear ccache? If you haven't done that, I would definitely try to do that. I know that the build system and ccache are supposed to be smart enough to know that code and flags have changed but problems have been known to occur in the past. Also, at the beginning of your build output after the variable definitions, you will see what tools and which flags are being used for various parts of the compilations. I've zipped up the output of my successful build from "scratch" and attached it here. Since you are running an ubuntu emulator, I think you should see the same tools being used, unless perhaps you have your own version of Clang installed and the build is using it instead of the prebuilt...

I know this must be frustrating.
[Nook HD, HD+ Android Development] andrerz:
Thanks for the help. I had already tried make clean, make clobber, and ccache -C -z, even wiped .repo and started again, all to no avail.

I am in the process of building a new vm, this time looking carefully about the toolchain I install. Its not easy as all the expert/easy guides are subtly different in what/what not to install, and as a Linux newbie it doesnt look as uninstall is even an option. Even Harry Youd's (of Lineage fame) guides are missing simple basic steps like create the build directory.

Indeed after spending my life writing embedded software and windows packages, Linux/ubuntu feels as if I'm stepping back 25 years in time!! Not found even a decent file manager....

Giving it a rest for a couple of days after the last 7 days intense learning curve. :(

Will update in a couple of days. Many thanks for now.
[Nook HD, HD+ Android Development] ajislav:
I was able to resolve the choppy audio on MM builds by applying this fix.

In order to build, I had to revert this. Seems amaces has been trying lately to update the LineageOS/android_hardware_ti_omap4 (see his recent activity here, presumably to bring it on par with his custom repo which his manifests use. I take it as a good sign, that the custom repo will possibly no longer be needed in the future ( <speculation>i.e. that our devices could become official??</speculation>)

If anyone is still on MM and is interested for an uptodate CM/LNOS ovation build, just PM me.
[Nook HD, HD+ Android Development] belfastraven:
Just FYI, There are new AOSP and Lineage Ovation and Hummingbird builds from today ( 2/26) in the Experimental folder from the link in the OP....
[Nook HD, HD+ Android Development] vinceweis:
Thank you and [MENTION=4473900]amaces[/MENTION] for the updates. Already installed and greatly appreciate keeping my ovation up to date. I love this tablet. With these updates, it does almost everything I need.
[Nook HD, HD+ Android Development] NE0HP:
New build for Ovation and Hummingbird is up

New build for Ovation and Hummingbird is up in experimental folder. I've dirty flashed new build Inos_ovation-ota-NOF26W.170226.zip over Inos_ovation-ota-NMF26Q.170104.zip and it just works fine. Once again Thank you [MENTION=4473900]amaces[/MENTION] for all your hard work. And yes good to see beautiful LineageOS boot animations in new build and so as updated security patch to 5th Feb'2017. One more cool thing is, I guess LineageOS updates under About Tablet is looks live now and we might able to download new build once it's available to download much like official LineageOS build OTA updates. And only thing I see missing is File Manager and so as much awaited root access. I'm sure [MENTION=4473900]amaces[/MENTION] will definitely bring back File Manager in his next build updates and hope to see this UNOFFICIAL build convert in to OFFICIAL soon and then we can able to flash suaddon zip as well.
[Nook HD, HD+ Android Development] pyoungworth:
Is there a change log for what is in the new experimental updates? Thanks for all the hard work you guys put in to this.
[Nook HD, HD+ Android Development] digixmax:
I've have not flashed the new LN build, but in the 0104 build the root-access enable setting can be found in Developer options.
[Nook HD, HD+ Android Development] NE0HP:
Yes, it was there under developer options but even if we enable(Apps & ADB) root under developer option, it's not working while enable the same on File Manager or in fact to any other file manager that support root access!
[Nook HD, HD+ Android Development] digixmax:
See https://xdaforums.com/showpost.php?p=70471533&postcount=1542.
[Nook HD, HD+ Android Development] NE0HP:
Thank you. Yes, It worked. :good:
[Nook HD, HD+ Android Development] mmnspeed:
New build looks good.I had some issue while first bootup where I couldn't login to my Google account and had to by pass that.Rest,it is working fine without any issues.Thank you Amaces.
[Nook HD, HD+ Android Development] i9000usersa:
I'm having trouble booting the latest build on hummingbird. It wouldn't get past the lineage boot animation. I left it on the charger all night and didn't boot. I used twrp 3.0.3 and did full wipe. Can anyone please help me out?
[Nook HD, HD+ Android Development] rpadula:
also having issues on boot

did a dirty flash and then a full system wipe, both ways didn't boot.
[Nook HD, HD+ Android Development] belfastraven:
Which hummingbird build--AOSP or Lineage?. What were you running before? Before doing anything else, assuming that you have powered off the device, I'd power it up and see if it will boot now. It shouldn't take more than 20 minutes, I think, even with everything wiped. If not, If I know which build you are using, I can test it for you. Is it possible your download was somehow corrupt?
[Nook HD, HD+ Android Development] dbrickg:
Just now installing on my nook hd+ ... waiting for it to boot ...

... and it looks good!
[Nook HD, HD+ Android Development] belfastraven:
Hummingbird issues:

There do seem to be issues with the new hummingbird builds. AOSP and Lineage--I will try to get logs and report to [MENTION=4473900]amaces[/MENTION]. You might want to hold off installing for a bit...
[Nook HD, HD+ Android Development] mikeataol:
Just an FYI , I installed the AOSP accaim with no booting issues.

still having the shutdown-restart issues, and video seems to struggle sometimes, but it boots and runs.
[Nook HD, HD+ Android Development] rpadula:
i was able to update to do a clean aosp install with the experimental twrp on my hummingbird.

wiped and tried to boot Lnos, but now my recovery stops with Error 7 and can't mount partitions.
[Nook HD, HD+ Android Development] mikey williams:
I have done the following :

aosp ovation 17.01.4 Clean instal. pico gapps

Worked OK but often very sluggish.

Then yesterday :

TWRP 3.0.1.3

aosp ovation 17.02.26 Dirty flash. pico gapps

I find it much snappier.

Two programs - Google keep and Alexa stopped working. but uninstalling and reinstalling solved the problem.

well done and thanks to amaces.
[Nook HD, HD+ Android Development] neutronjeff:
Question, did you use the REPIT tool on your Ovation?
[Nook HD, HD+ Android Development] belfastraven:
I too have been able to install AOSP after a factory reset. Trying to install Lineage definitely will cause problems. Sometimes I have had to try a few times to boot the machine into recovery. When are you getting the 07 error code? I was able to do various mounts and wipes once I was in recovery, and then I was able to install and boot AOSP.
[Nook HD, HD+ Android Development] rpadula:
anytime i try to flash a rom it returns Error 7 and/or System partiton mount error.

happened with LnOS, old MM CM, i'm trying to find a recovery now that mount the partitons correctly and flash AOSP again.
[Nook HD, HD+ Android Development] mikey williams:
No
[Nook HD, HD+ Android Development] belfastraven:
There is a new LNOS rom up in experimental now. It will boot and run fine. There are also new reocveries, but I think before trying a different recovery installation, to a factory reset AND wipe system, then try to install the new rom. I think the old LNOS rom somehow corrupted system. If you still have problems, then do flash the new hummingbird recovery image.

---------- Post added at 11:19 PM ---------- Previous post was at 10:40 PM ----------

There was a problem with the earlier Lineage rom. If you tried to install it and had problems, I would do a factory reset AND wipe system before reinstalling the new rom. (either Lineage or AOSP).
[Nook HD, HD+ Android Development] rpadula:
i've done a system wipe, went back to recovery 3.0.1 but still, sometimes system mounts but cache don't.

can't wipe ART/Dalvik,

actually, cache partition shows as 0 Mb, i don't remember if this is right...

i have to travel now hope to get some sleep and figure this out.

anyone remembers how to get hummingbird back to stock?
[Nook HD, HD+ Android Development] digixmax:
See #6 of https://xdaforums.com/showthread.php?t=2062613.