yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] ST Dog:
Thanks. I missed that edit.

Didn't realize it was a unified fix for all 3 devices. I just skimmed past all the Acclaim talk

Great. As I read that the changes were accepted, so next official release will include support for all 3 devices.
[Nook HD, HD+ Android Development] digixmax:
Thanks for the follow-up reply & info.

On my HD+ running amaces' AOSP build 180212 it looks like the edited file wpa_supplicant.conf gets clobbered and replaced with new version without the hotspot ssid and password whenever the tablet gets rebooted or wifi gets turned off+on.
[Nook HD, HD+ Android Development] buggage:
This is exactly the same behavior I've been experiencing - haven't been able to use any of the workarounds.
[Nook HD, HD+ Android Development] digixmax:
I tried using both the text-editor built into FX file-explorer, then vi in terminal shell, neither made any difference. File permission is 660.

disable_scan_offload=1
driver_param=p2p_device=1
update_config=1
device_name=Android_b73d
manufacturer=BN
model_name=Nook HD+
model_number=Nook HD+
serial_number=3025230055714300
device_type=1-0050F204-1
config_methods=virtual_push_button physical_display keypad
p2p_ssid_postfix=-Android_b73d
persistent_reconnect=1
pmf=1
external_sim=1
tdls_external_control=1

network={
ssid="hoangmai"
psk="password"
key_mgmt=WPA-PSK
priority=1
}
[Nook HD, HD+ Android Development] fddm:
[MENTION=3511186]digixmax[/MENTION] [MENTION=4092344]buggage[/MENTION] I finally was able to reproduce, the problem is caused by gapps. Disable the following setting and the workaround will work again:

Settings -> Location -> Menu (3 vertical dots on top right) -> Scanning -> "Wi-Fi scanning"
[Nook HD, HD+ Android Development] digixmax:
Thanks for the solution.

With the Location WiFi Scanning disabled the wpa_supplicant.conf file stays intact across reboot and WiFi on/off -- but it seems that one now has to manually remove the existing file in order to get auto-reconnect with a different hot-spot.
[Nook HD, HD+ Android Development] nmyshkin:
Did you install/enable a location provider back end like the Mozilla app? This is needed with microG for location to work properly. There is also a flashable zip to enable Maps fully.
[Nook HD, HD+ Android Development] fanoush:
Yes. There are two, Mozilla na DejaVu, I enabled both, or just one, no difference.

Which one is that?

BTW, Google Maps installed from Play Store work but do not show my location. Also some apps showing maps via api work fine (but look a bit ugly, e.g. ISS onLive).

This issue is not about maps but about missing GPS location provider on device without GPS.
[Nook HD, HD+ Android Development] nmyshkin:
This is the flashable zip which helps out with the Maps api: https://github.com/microg/android_frameworks_mapsv1/wiki/Installation

I've never had much luck with Maps on any of my devices until I tried this older version: https://xdaforums.com/attachment.php?attachmentid=4384547&d=1515524005

It does everything I want and allows you to pre-cache map areas for offline use which will

not

expire, unlike with current versions. I found it to be a little reluctant with locating me at first. Check your permissions and try a few times. It generally kicks in.

I've never had a need for the GPS stuff, so don't have any ideas there.
[Nook HD, HD+ Android Development] flieswithhawks:
Thanks [MENTION=4473900]amaces[/MENTION] for continued support of the Nook. I am running the February test build on my Hummingbird and it's really great.:good:

Also, as another user mentioned previously, the power off bug seems to be solved for me as well.
[Nook HD, HD+ Android Development] digixmax:
After a year of using LNOS, based on the above quoted tip, I recently switched to AOSP (build 180212) and couldn't be happier with the tablet's responsiveness performance. My only wish-list item is a fix for the WiFi auto-reconnect (without having to resort to the [MENTION=3711980]fddm[/MENTION]'s work-around of editing wpa_supplicant.conf https://xdaforums.com/showpost.php?p=75698291&postcount=2394). I missed not having the reboot menu but it's no big deal.

With LNOS builds in the last 9 months, the tablet's responsiveness performance consistently degraded and became unusable about a week or two following a fresh install. The moment the tablet goes in use and its WiFi gets turned on there seems to be some background processes rushing into action and sucking a great chunk of cpu and/or ram memory resources for a good 3+ minutes before things settle down when the tablet starts to respond. Leaving the WiFi on while the tablet is in the sleep mode helps quite a bit with this bursty-congestion behavior but at the great expense of battery drain.
[Nook HD, HD+ Android Development] HarvHouHacker:
I know about the processes; it happens to me too. :crying:

The lock screen is probably the most cumbersome thing right now, as it directly involves LineageOS. I swipe up once, and the elements return, so I have to swipe several times to get it to show where I can input a password. I'm not so worried about battery drain, as most of the time it stays plugged in, and I don't seem to have WiFi problems very much.

[MENTION=3511186]digixmax[/MENTION], you could try to add swap. At least 1 gig will do ya. :good:
[Nook HD, HD+ Android Development] digixmax:
I ran into this problem of "swiping to bring up the login screen" whenever the tablet is plugged in for charging, with both LNOS and AOSP.
[Nook HD, HD+ Android Development] fanoush:
Looks like this is microG issue. After reflashing same aosp rom with gapps it no longer crashes and location works fine. so looks like real gapps contain location provider named "gps" even for devices without gps (or those apps run different code path with real gapps installed).
[Nook HD, HD+ Android Development] robotsondrugs:
For everyone having performance issues on LineageOS, I've found that disallowing Google Play Services from doing wi-fi scanning helps tremendously, at least on ovation. It was suggested to disable scanning in Settings -> Location but I would suggest also going into Privacy Guard and reigning in Google's apps. Settings -> Privacy -> Privacy Guard -> 3-dot menu -> Advanced. Google Play Services should show up in multiple categories. It's also worth tweaking other apps here to your liking while you're at it.
[Nook HD, HD+ Android Development] secretwolf98:
[MENTION=4473900]amaces[/MENTION]

I flashed cm 11, cm 12.1, and cm 13 on ovation, the boot animation is soo slow. Any solutions?
[Nook HD, HD+ Android Development] twiztid_:
Assuming you're not talking about the first boot taking a while longer, especially if you have things like GApps installed, and while I don't have hard data to back this up, but I FEEL like deleting the bootanimation.zip file shaves a few seconds off boot time. Plus I like the minimal "android" logo.

If I were to get as to the why behind it, with my no-knowledge of Androids inner workings, it would be that the boot animation has to finish before going to the home/lock screen. So using some random numbers for the sake of argument, if the boot animation is 5 seconds, and booting finishes in 11 seconds, that means you'd have to wait an "extra" 4 seconds to finish the 3rd loop of the animation. But again, this is all just conjecture.
[Nook HD, HD+ Android Development] secretwolf98:
I am not talking about the bootloader. I am talking about CID CM 13 face, and under. CM 14.1 haven't tried. But I know Lin14.1 works perfectly.
[Nook HD, HD+ Android Development] twiztid_:
Is this in reference to the wpa_supplicant.conf file "forgetting" our connection?

Because if so it's happening to me in UnlegacyAndroid, I don't have GApps installed (using MicroG + the "real" Play Store) and wifi scanning is off.

It only seems to happen when the tablet enters sleep(?) state, as turning off the screen and then back on shortly after keeps the connection going, but leaving it to idle off seems to make it happen more frequently.

The only thing that has worked for me is setting wifi to Always On, which eats up the battery real fast.
[Nook HD, HD+ Android Development] BultoPaco:
I'm running [MENTION=4473900]amaces[/MENTION] most recent AOSP Experimental release on hummingbird and, in general, it runs smooth and fast. I don't seem to have the problem with retaining WiFi connections - remembers home & work. I do have what may be a related issue. I recently started a trial for YouTube TV and have no problem connecting to the service on other Android devices. The hummingbird can't get past the checking location screen no matter what WiFi and location settings I try. I'm curious if anyone else has experienced something similar?

UPDATE: Installed GPS Emulator app to set my ACTUAL GPS location and YouTube TV works great!
[Nook HD, HD+ Android Development] HarvHouHacker:
I accidentally deleted the source for the Nook SDK! Since my Nook is running LineageOS, I wonder if I ever do need it again. Just in case, however, where can I find an existing source of the SDK?
[Nook HD, HD+ Android Development] jernyx:
Do you have Google Play Services or a non-Google equivalent installed?
[Nook HD, HD+ Android Development] BultoPaco:
I'm running Google Play Services .
[Nook HD, HD+ Android Development] Nemesis1278:
I have switched to asop from lineage and it has been running as smooth as can be for a while. lineage runs good at first but then becomes sluggish after some time. The "fixes" I tried only temporarily fixed the issues. Now on asop it is running great. I can enjoy my nook as a tablet. Thanks amaces for your hard work.
[Nook HD, HD+ Android Development] thyTwilightGoth:
I am wondering if it is possible to Port Android 8.0 to the nook hd
[Nook HD, HD+ Android Development] ST Dog:
Possible yes.

There are some hangups delaying it right now. It is discussed in a few threads.

Mainly some new libraries are needed but have not been released for distribution.
[Nook HD, HD+ Android Development] twiztid_:
Search the thread...

It's been asked a couple dozen times.

There's still a lot of work to do to get 8.0 to work with our hardware, and we already have a lot of the optimizations that Android Go uses.
[Nook HD, HD+ Android Development] sega dude:
Would it be possible to make one of the Ovation images a no-emmc image?
[Nook HD, HD+ Android Development] HarvHouHacker:
Any news on Lineage 15 based on Android Go?
[Nook HD, HD+ Android Development] rtarv321:
I have reinstalled lineage 2-14-2018, but can't get root. I have installed &rooted since jellybean,but now I think I'm am my own worst enemy. I have tried all that I remember.i I get a "error message 7" in TWRP. ANY IDEAS?
[Nook HD, HD+ Android Development] rtarv321:
I finally figured it out. Somehow I had formatted the data wrong. Working great so far
[Nook HD, HD+ Android Development] neutronjeff:
I also have installed 0214 [Ovation] using your latest TWRP 3.2.1 and am running fine.

Thanks!
[Nook HD, HD+ Android Development] rfrazier:
Hummingbird no longer builds (Lineage 14.1), unfortunately. Pehaps its race is run.

Best wishes,

Bob
[Nook HD, HD+ Android Development] secretwolf98:
So our nooks don't get anymore updates from [MENTION=4473900]amaces[/MENTION]?
[Nook HD, HD+ Android Development] Uldiniad:
Magisk 16.4
[Nook HD, HD+ Android Development] rfrazier:
I don't know. Although I know (barely) enough to build, I can't tell from the error file how much has to be changed to get it building again (or whether it is worth the effort to [MENTION=4473900]amaces[/MENTION] ).

Before yesterday, my last attempt at building was in March, and it built okay.

Best wishes,

Bob
[Nook HD, HD+ Android Development] rtarv321:
I thought that Amaces was involved in the "unlegacy android builds" now. That's what I changed to. They are updated monthly
[Nook HD, HD+ Android Development] amaces:
I've rebased manifests and everything else forked. Can you try repo sync & build again?

I certainly plan to keep updating N builds, but those Lineage repos are mostly in maintenance mode now. I'll work on new images this weekend. Otherwise, AOSP builds have been kept up-to-date via UA builds, which are on latest security patches.

About root, official Magisk should be a good option after the patches accepted a few months back. My personal SU addon should also work on Lineage, and personal AOSP builds, but not on UA builds. You can't use the official Lineage addon after we switched to 64-bit Binder IPC everywhere. At some point, I'll get around to updating the OP and FAQ.

I personally never built SD-only images, but will try to figure out how it was done years ago. Might take some time.

Sadly, we still don't have UM blobs that can be released publicly. The rest is definitely prepared for Oreo, but w/o new Gralloc and GLES libraries, nothing can go forward. When there's time and energy, I'll try to go back at debugging the issues with current blobs. There's a decent chance they might still be made to work, but will take significant effort.
[Nook HD, HD+ Android Development] rfrazier:
Sure. Many thanks. I've got both ovation and hummingbird, and will do a make clean first, so it will probably take overnight.

Best wishes,

Bob
[Nook HD, HD+ Android Development] rfrazier:
Both ovation and hummingbird built just fine, and more quickly than I expected. I've installed on hummingbird. All seems well, and it has the 5 June security update. Thanks again.

Best wishes,

Bob

PS About root. I built the images with su enabled and it works.

RLF
[Nook HD, HD+ Android Development] twiztid_:
This might be a dumb/silly question, but I'm guessing that it's not possible to make a build *without* the blobs, and then have users find and add them on their own?

Or if it is possible, then something you just don't want to deal with I would guess.
[Nook HD, HD+ Android Development] secretwolf98:
The blobs has to be in the github tree and compiled with the ROM. isn't possible for anyone else to add them.
[Nook HD, HD+ Android Development] ST Dog:
What's the issue?

Why would the OE not release them?

Just doesn't make sense.
[Nook HD, HD+ Android Development] Zippy Dufus:
Build success

Nice to see there is still interest in this device!

I successfully built a 06/25 Ovation ROM.

Thanks!
[Nook HD, HD+ Android Development] HarvHouHacker:
That's OK, [MENTION=4473900]amaces[/MENTION]. It's impressive that the Nook HD+ can support Nougat due to your efforts. I'll flash whatever will be the next LineageOS update when you've got it ready. :highfive:
[Nook HD, HD+ Android Development] secretwolf98:
Did you try the one from a week ago?
[Nook HD, HD+ Android Development] Nolfer:
Why can't the scheduler be changed?
[Nook HD, HD+ Android Development] myjess:
Is anyone working on android oreo 8.1 go rom for these?

Go works with lesser hardware apparently.

Thanks.
[Nook HD, HD+ Android Development] ST Dog:
Look a few posts back.

There's some stuff needed For 8.1 that hasn't been publicly released.

As for GO, also discussed earlier in this thread, the ROMs already use most of the optimizations (or similar) so GO won't be much different.
[Nook HD, HD+ Android Development] twiztid_:
Has anyone had these issues on the LNOS builds?

- Lineage Setup Wizard causes screen flickering and restarts tablet

- Pulldown "preview" works, but you cannot further pull down the panel

- Home (Circle) and Overview (Square) buttons do not work

These are happening to me on a fully wiped and fresh install of 180624.
[Nook HD, HD+ Android Development] BultoPaco:
I was running a clean install of the February LNOS build on a hummingbird and it has worked quite well. I dirty flashed the June build last night and it is less laggy than the previous build. I am not experiencing any of the issues you mention.
[Nook HD, HD+ Android Development] ipdev:
I have some issues, clean flashing the last few ua builds for ovation.

- The navigation buttons, home and recent stop responding. Using the power button to actually power off. Then turning it back on seemed to correct the problem, for awhile.

- Pulldown, sometimes has an extreme lag.

- Screen rotation, sometimes has an extreme lag or doesn't rotate until I select something on the screen.

I didn't see anyone mention these problems. I assumed it was my hardware, setup, some other app or configuration interfering, and I would try a few things when I had some time.

About 5 months ago, I installed ua on my Sister-in-law's ovation.

What can I say, normally when I ask her "How's your nook running?", I get "It's fine."

I checked with her this afternoon and she has had some issues also. Nav buttons, a random reboot here and there, and once-in-awhile she can not wake the device. She'll have to hold the power button for about 10-20 seconds and then the screen will flicker and go completely off. Then she can turn it back on and use it for days on end without issues.

I haven't tried the latest ua for ovation yet. I should have time tomorrow to start testing a few things to see if I can narrow it down.

Make sure it isn't hardware, setup, some other app or configuration interfering or simply a user related error.

I already cut a bunch out of this post, and it is still long. ;)

One last comment about the nav buttons, ovation is the only device I have that the button layout changes when you change the display size. It happened with the last los builds I ran also.

See attached screenshots.

ua on ovation and for comparison ua on flo
[Nook HD, HD+ Android Development] myjess:
Sideloaded a few packages already on my nook hd+, but seems to get stuck now saying installing and never completes. Any ideas without me resetting and going back to initual nougat?

I put the apks in /system/app via twrp. They are still apks after i rebooted, so haven't actually installed as far as I can tell.

Updates taking forever downloading also.

Thanks.
[Nook HD, HD+ Android Development] HarvHouHacker:
I've figured out something about the lockscreen: If you use a wallpaper that exceeds the resolution of the Nook HD+, everything is slow. I switched to one of the defaults, and now I can log in effortlessly. There's one workaround for you all. :good:
[Nook HD, HD+ Android Development] ShapeShifter499:
I recently got a Nook Tablet Acclaim in addition to my Nook HD. Does anyone know how I should repartition the Nook Acclaim to make the system partition bigger?

---------- Post added at 03:08 PM ---------- Previous post was at 02:36 PM ----------

Ok I've used this recovery build to repartition the device, was this alright or was there a more official way? https://xdaforums.com/nook-tablet/development/cm-14-1-nook-tablet-acclaim-16gb-model-t3499226

I'm also having a issue getting any acclaim builds booting, so far I've gotten to the boot animation with the arc and the circle that pans from right to left. I am only flashing the OS for now, no gapps or root extras. Am I doing something wrong?
[Nook HD, HD+ Android Development] secretwolf98:
Is it the 16GB model or the 8GB model? And what OS are you trying to use?
[Nook HD, HD+ Android Development] ShapeShifter499:
This was on a 16GB model. But I also have a 8GB model which I haven't attempted to boot anything other than the stock OS on. I would like to get some more recent Android OS running on both.

Right now on my 16GB I tried two amaces builds. lnos_acclaim-ota-NJH47F.180211.zip and lnos_acclaim-ota-NJH47F.180624.zip No luck, these two didn't boot past the boot animation.

I also installed the version 3.1.1 TWRP build by amaces
[Nook HD, HD+ Android Development] Zippy Dufus:
Mismatched partitioning?

I doubt that amace's builds will work on chrmhoffmann's updated partitioning.

I built from amace's repos (see my signature) to avoid repartitioning. However, I don't install gapps and only have a few apps installed on my Acclaim which I side-loaded using a Titanium backup APK from one of my other devices.

Formerly, I hacked chrmhoffmann's device tree to revert back to the original partitioning and while this resulted in a bootable build, WIFI would not work. Hence I went to amace's repos.
[Nook HD, HD+ Android Development] Nolfer:
I had the screen flickering problem too on that build, and it automatically rebooted the nook after flickering for some seconds and prevented me to go any further.

Clean install too. Had to restore a backup. I'm using f2fs in data and cache, maybe this is the problem? Also, the i/o scheduler cannot be changed (tablet freezes) and it's a pain in the ass, because bfq is the absolute worst, laggy and stuttery as hell. I'd give anything to just have a noop slammed in there

I think I will try the new experimental builds. I saw that on the 12 July amaces updated the box directories with new builds. Hopefully this time there will not be problems
[Nook HD, HD+ Android Development] ShapeShifter499:
How can I revert my partitioning?
[Nook HD, HD+ Android Development] twiztid_:
I have used F2FS in the past, but I'm not sure if I'm still on it.

Apparently Unlegacy Android builds might have a battery drain issue, since my tablet has died twice while sleeping. WiFi is set to not stay on, and I'm not using GApps either.

Edit: Yes, I am still using F2FS for Data/Cache. I wonder if that is causing some of the problems.

If I can't fix/work around the battery drain issue with Unlegacy, I might change them back to EXT4 and try LNOS again.

Edit 2: Back on EXT4, completely wiped all partitions, fresh install of the latest LNOS build (2018-07-13) and still running into all the issues I mentioned above.

AOSP builds are working fine (2018-07-11). Would prefer to use LNOS (Pulldown and Buttons not working) or UnLegacy (Battery/WiFi issue) if anyone has any ideas/workarounds.
[Nook HD, HD+ Android Development] secretwolf98:
Try [MENTION=4473900]amaces[/MENTION] yesterdays build. https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/304318477029
[Nook HD, HD+ Android Development] Zippy Dufus:
I've never repartitioned a disk on an Android device before, but I think that you want to investigate this:

Look her for amaces's partition sizes starting at line 50: https://github.com/Unlegacy-Android/android_device_bn_acclaim/blob/aosp-7.1/BoardConfig.mk

Carefully read and understand this post to see if you can manually repartition your Acclaim back to the original sizes as per above: https://xdaforums.com/showpost.php?p=22157605&postcount=25

I took a minute to download that special recovery image which does the repartitioning to the new sizes but was unable to mount it on my Linux desktop to see what is in it. There is probably a script which drives this and could be adapted to revert to the original partitions.

Good luck and sorry I cannot be of more help. :(

If someone with more knowledge could weigh in, this would be appreciated.
[Nook HD, HD+ Android Development] secretwolf98:
Hey, question...

I put stock back on my Nook HD+, and it lost space? How can I fix that? Same for my Nook HD. Thanks.
[Nook HD, HD+ Android Development] Zippy Dufus:
Sorry, I have no idea. Probably caused by discrepancies in partitioning.

To maintain my stellar record of building and flashing many ROMS on many Android devices and having NEVER bricked one, I have always shied away from tampering with partitioning! :angel:
[Nook HD, HD+ Android Development] secretwolf98:
The nooks can't be bricked, only soft bricked. Soft bricked is way easy to fix.
[Nook HD, HD+ Android Development] ifGeny:
Don't know where to ask this is better, so I'll try it here too.

Can someone explain why my Tablet is booting infinitely after I flashed lnos_acclaim-ota-NJH47F.180624.zip? A blue circle is moving on bracket infinitely and that's it. However with lnos_acclaim-ota-NJH47F.180713.zip, from experimental folder, my Tablet boots well. Is it safe to use this image?