yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] secretwolf98:
Do you have a hummingbird home build of LineageOS 14.1 or LineageOS 15.1? If you get LineageOS 15.1 built (well, hummingbird), could I test it? I might be getting Ovation soon.
[Nook HD, HD+ Android Development] ze7zez:
Thank you for the idea for the future.

Could you expand or explain it in other words, because I do not understand the meaning of the sentence.

I would like to know why to be careful. Will the batteries be electrocuted? Do they weld PCBs after connection?
[Nook HD, HD+ Android Development] ieatabiscuit:
The batteries will be about 50% charged. On the tabs that the battery has, there will be some pads spot welded on, they are about 1mm thick, and they look like they are a permanent part of the PCB. They are not a permanent part of the PCB, they are only attached with solder on the under side. Heat them up with a soldering iron and they come right off the PCB so you have a nice thick contact you can solder to the ovations PCB. There's a more detailed walk-through with pictures on xda that I can link later after I find it.

Update: This is the xda thread on the ovations battery, part number, and some pics of the battery mood I mentioned. The batteries used in the pictures are hard to find in the us, for me anyway, but the party number I mentioned do the job nicely.

https://xdaforums.com/nook-hd/accessories/hd-battery-part-t2940558
[Nook HD, HD+ Android Development] ST Dog:
Any progress or updates you care to share?

I think I mentioned before builds with the new WiFi drivers would be better than no builds.

Last few monthly patches have references several 7.1 fixes.

My understanding is Lineage is updating as well.

A new build with the latest patches would be nice.

I'm also curious about the Unlegacy stuff, but would probably miss a lot from CM/LN. Is there a good thread or other source for info in it and status/updates?
[Nook HD, HD+ Android Development] secretwolf98:
This? https://builds.unlegacy-android.org/aosp-7.1/hummingbird/
[Nook HD, HD+ Android Development] ze7zez:
Yes, there are.

https://www.unlegacy-android.org/projects/unlegacy-android

https://github.com/Unlegacy-Android

---------- Post added at 13:24 ---------- Previous post was at 12:45 ----------

I have not read your first post carefully.

I have Nook HD (hummingbird), which has one battery.

Nook HD Battery Replacement
[Nook HD, HD+ Android Development] ST Dog:
That's just a folder with builds.

Nothing about festures or status.

---------- Post added at 08:10 AM ---------- Previous post was at 08:06 AM ----------

So where are all the dev and user comments on the ROM on hummingbird or ovation?

Like what we have here for LN14.1.
[Nook HD, HD+ Android Development] ze7zez:
Do not be lazy, just type omap in the search bar https://github.com/Unlegacy-Android
[Nook HD, HD+ Android Development] secretwolf98:
These?

https://github.com/airend/android/tree/cm-14

https://github.com/airend/android_device_bn_hummingbird
[Nook HD, HD+ Android Development] ST Dog:
That is a source repository. There are no discussion threads. I've looked through it several times. I see some comments on changes scattered through the repo, but no discussions. And nothing regarding 8.0/8.1 in the Nook repos.

Also nothing from users about unlegacy on the HD/HD+. What works. What doesn't. Allbtge sorts of stuff in this and ithe CM threads here on XDA.
[Nook HD, HD+ Android Development] ieatabiscuit:
I looked into the hummingbird battery, but only briefly. I had ordered one with a broken screen so that I could use it's casing and battery to repair the one my daughter mutilated. It's also MUCH easier to find a replacement for the hummingbird than ovation in my experience, though that was a couple years ago. Mainly you just have to match the numbers with a battery from another device that is more mainstream, and then do some solder work. If you're not that experienced at the soldering, and with handling a live current then I would strongly advice not to try this yourself. It could end with damaged hardware, possible fire, and most likely a painful tingling in the fingers, and money/time wasted. For a 4000 mAh battery, or something in that range, should you still want to go ahead with the mod, try looking up the batteries from some of the zenfones, or some of the other phones known to have beefy batteries. going a bit over on the capacity (mAh) just gives you longer life (I went over it by 200 mAh so I get maybe an extra couple minutes of hard usage, nothing serious though). You want to keep the same voltage, and what not though, going over on anything other than the capacity can fry hardware.
[Nook HD, HD+ Android Development] theleagueofstream:
Yeah, some indication of the changes between builds would be useful.

I haven't checked this in a while, but I pretty much gave up on the battery and just charge it daily.
[Nook HD, HD+ Android Development] Nemesis1278:
Well on battery I usually get a couple of days if not on heavy use. When using heavily it will go down to about a day possibly charging at the end of the day. I do notice that the reading of the battery percentage is a bit off, but I try to ignore it as long as I can.

I have also been to tweak turbo zram settings to the most optimal for good speed from tablet. I also Disabled an app running from lineage which helped a little with speed.

I disabled the app trebuchet. After that the system performed slightly faster.

I am currently adjusting swappiness in turbo zram to find an optimal setting for that. Right now I'm using swappiness 80. Might try 75 or 60. 80 is down from 100 and seems to perform better.

I am currently using lineage on ovation.
[Nook HD, HD+ Android Development] fddm:
I'm somehow not experiencing the WiFi corruption issue on AOSP Nougat anymore. I think I connected the main network and then connected to another. Now it autoconnects to the main network every boot. I don't mess with it now that it's working, too scared it will break. In AOSP Marshmallow you have to view available connections from the drop down for it to connect, so this is awesome.
[Nook HD, HD+ Android Development] lmacmil:
Does the HD+ really run OK on Marshmallow and/or Nougat with just 1 GB RAM? I gave my mother (91 years old) an HD+ running CM 10.1.2 a few years ago. It seems to have slowed down (although it could be because I'm used to my Galaxy Tab S2) and was thinking of upgrading it to MM or Nougat. Will either of these ROMs provide a performance improvement or is this old tablet just beyond the point where the OS can make a difference. FWIW, she uses it mainly to play Hearts and Texas Hold-em (via apps, not online) and occasional Gmail so pretty light usage.
[Nook HD, HD+ Android Development] fddm:
Marshmallow and Nougat do run very nicely, especially for a relatively slow dual core device with an HD screen and 1gb of ram. Not fast like a new device, but still very responsive. The main reason to update is for stability, IMO. Stock firmware and old custom ROMs have random reboots that were very annoying. Old custom ROMs also had graphics problems, random app crashes, all kinds of persistent weirdness.

I suggest testing out both Lineage Nougat and AOSP Marshmallow, and see what works best for you. I have less experience with the recent Lineage builds, but I'm pretty sure it has only minor issues.

In my opinion, AOSP Marshmallow is the most reliable option. You just have to remember to check that system apps have the permissions they need if you are having issues after install(like Storage so the browser can download files). Replacing some of the built-in apps is also good, like the browser and file manager. Only real bug is you have to view available networks before WiFi will connect, but it is very minor.
[Nook HD, HD+ Android Development] ST Dog:
My KK install got really sluggish over time.

I think it's more the newer Google apps than the OS. You could try mico G and seeing if it helps.

Of course a clean flash and setup, with full wipe, may help.
[Nook HD, HD+ Android Development] lmacmil:
Thanks. Since I don't have easy access to my mother's Nook (she's 900 miles away), I think I'll just buy another one, set it up and swap them next time I see her. She can probably get by with pico or nano Gapps and I'll just add Gmail and Chrome.
[Nook HD, HD+ Android Development] fddm:
Microg is nice, I do use it on my nooks, but I'm not sure you'd want it in this case. You'd have to setup fdroid with only the microg repo and teach the recipient how to use it. And when it breaks, the fix might take some time to come out, not sure how you'd teach someone how to handle that. The other thing is that Google Play Services is actually pretty well behaved, you won't reclaim much replacing it alone. Replacing the Play Store would probably do better, but then you lose licensing, IAP, app data downloads, etc.
[Nook HD, HD+ Android Development] kaew158:
Did anyone try this Nougat 7.1 for Nook HD ? Ang Bug?

Nougat for Nook HD

Dropbox

Nougat for Nook HD Plus

Dropbox
[Nook HD, HD+ Android Development] mikeataol:
That's a year old build, not what you probably want

The latest stable builds are here:

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3220985318

I prefer the LNOS over the AOSP on Nook HD+

Yes, there are a few minor bugs still, I believe kernel related, the most glaring is that shutdown usually works as a reboot
[Nook HD, HD+ Android Development] kaew158:
Nothing on this page.

Please give me new link.
[Nook HD, HD+ Android Development] digixmax:
That link works (except for occasional site-maintenance episodes). If you access it from a tablet then you need to select the "request desktop site" option in your browser.
[Nook HD, HD+ Android Development] oblivions:
Hello!

I followed the steps in the post nookhdplusandroid7 and ended up after rebooting in a loop showing the nook-sign, following the cyanoboot-screen and after a while the twrp-logo. Then after some time the tablet shows randomly one of these three screens, ending up stuck in the twrp-after 3-4 times.

The installation of cm and gapps is always said to be successfull accept in the end of the installation of cm its written:

(...) mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata at /data: No such device

unmount of / data failed; no such volume

Patching system unconditionally ...

E: unknown command (log)

E: " " "

script succeeded: result was (1.000000)

Install from sdcard complete

Does that mean anything or is the installation just successful?

Does anyone here maybe have an idea how to solve that problem or what could be the reason?

I would be very very grateful!
[Nook HD, HD+ Android Development] secretwolf98:
I had same problem with my very first Nook HD. Found out it was 100% bricked.
[Nook HD, HD+ Android Development] digixmax:
If the Nook only boots straight to recovery, it's likely that its /bootdata partition's files need to be reset/restored; this can be done by flashing the flashable_fix_bootdata-ovation.zip for the HD+ (or flashable_fix_bootdata-hummingbird.zip for the HD) available at http://www.mediafire.com/folder/6a4rivb8kkdfu/Nook_HD+.

In your case it's more likely that the Nook's emmc might be bricked, in which case you can try running the CM11 ROM build specially made for bricked/no-emmc available at https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
[Nook HD, HD+ Android Development] wally333:
I just installed the latest LNOS (oct 2017) build over top one of the ones from April 2017 and its working great! Good enough that I've ordered a replacement battery for it. Works great with all the video apps for the services linked to our U-verse account except for the AT&T app (which doesn't work on most things I've tried). Chromcast works great too in the apps that support it.

I just added a new access point out by the garage/pool and roaming works (although there is a pause and buffering when the AP switches). For roaming you need to enable developer options, then find the option under the section marked "Debugging" find "Always allow Wi-Fi Roam Scans", and enable it. I forgot if a reboot was require for it to become active.

Battery life seems pretty good considering the original battery could barely watch a 2 hr movie before I wiped the stock firmware for LNOS back in April.

Most annoying bug is the lack of Power Off, as he said, you can choose it but it just reboots :( which means a dead battery next time and really slow startup when my wife forgets to put it on the charger.

Kudos to all involved the development and debugging of LNOS on the NOOK HD+, we were ready to trash it last April for the weak battery and most of the updated video apps no longer supporting the old Android 4.x it came with. Well worth buying a new battery, as its a very nice display for watching movies now with Nougat.
[Nook HD, HD+ Android Development] lmacmil:
Can LineageOS 14.1 be dirty flashed over CM 14.1 or does it require a clean flash?
[Nook HD, HD+ Android Development] digixmax:
I think a clean flash is best (especially as I recall some of LN14.1 updates themselves entail a clean flash), but you can always first try dirty-flash and see if there is any issue.
[Nook HD, HD+ Android Development] nmyshkin:
I agree it is a big annoyance. I can't pretend to know anything about ROM construction but this feature has been on the fritz since CM 12 and it seems like a pretty basic thing (again, my ignorance showing). I've tried shutting down via ADB and it still reboots. Fortunately my husband is the one with the HD and he has been well-trained to hold in the power button until the screen goes black.

The problem also exists with Nook Tablet ROMs past CM 13, with the exception of

one

AOSP 7.0 ROM. Seems like a good opportunity to compare another ROM in the same series and maybe finally exterminate this bug?

Not to say I am not grateful for these ROMs which, on the whole, are a fantastic achievement.
[Nook HD, HD+ Android Development] kaew158:
Please give me link a Gapps for aosp_hummingbird-ota-NKG47S.171021. I got error when use open_gapps-arm-7.1-pico-20171225.zip

I always turn nook hd off use twrp recovery (power off).
[Nook HD, HD+ Android Development] lmacmil:
Is this just a LineageOS problem or do all AOSP ROMs have the same issue?
[Nook HD, HD+ Android Development] ST Dog:
Just hold the power button till it turns off, about 10 seconds.

Just remember, if you plug it in it will turn on.
[Nook HD, HD+ Android Development] HarvHouHacker:
@amaces - I'm attempting your Lineage OS build. Some things I tried:

Factory reset and cleared all data, then flashed the lnos_ovation-ota-NJH47F.171021.zip package. During the setup wizard, I couldn't get past the Location Settings without the screen flashing and forcing me to do a hard power off.

Rebooted into recovery, factory reset and cleared all data, then flashed cm_ovation-ota-MOB31K.161125.zip before flashing Lineage. Same issue.

Tried again, this time flashing an even older CyanogenMod package (10.2.1) before flashing the newer CM and then Lineage. Still the same issue.
[Nook HD, HD+ Android Development] ST Dog:
Weird. I flash the Oct build w/o issue.

Wasvon an old CM11 build. Wiped everything except user data.

Latest TWRP, flashed LN and gapps.

No issues with first boot, setup, or restori g apps.
[Nook HD, HD+ Android Development] HarvHouHacker:
I fixed my own problem. I think it has something to do with the graphics. I'm using Lineage OS 14.1, build date August 3 2017, but I plan on flashing the latest build. If anyone else is experiencing the same issue, here's what I did:

During the initial setup, BEFORE advancing to Location Settings page, swipe your finger from the top of the screen. You will be able to pull down the settings menu.

Access Developer Mode: Tap "About Tablet", then tap "Build number". You may or may not see a message, but after ten or twelve taps you should have enabled it. Tap the back arrow once and tap "Developer options". NOTE: If you are not able to see "Developer options", pull down the drop-down menu by swiping from the top again. Plug your Nook into a computer, and you should see the "USB debugging connected" message appear. Tap it to go into the developer settings.

Scroll down to the "Hardware accelerated rendering" section and check "Disable HW overlays" so that it is on.

This fixed my problem, and I was able to see the Home screen perfectly, without the display flickering or going to black. Huzzah! :victory:

UPDATE: I flashed the upda te. Hesitated on boot, but did not flicker. I rechecked the "Disable HW overlays" option just to be safe.
[Nook HD, HD+ Android Development] HarvHouHacker:
Is there some way to expand memory on the Nook HD+? Mine has 840 MB and the OS is using almost half that amount. For instance, any way to partition swap on the SD or in internal storage?
[Nook HD, HD+ Android Development] fddm:
Sure, both can be done. Just be aware of the performance impact if swapped data is requested and the shortened life of your SD/emmc from extra writes. Chances are if you feel you need swap for your desired workload, the Nook HD is probably not the device for you. I've tested ~140 kids games so far, and I think I've only had one fail due to limited memory.
[Nook HD, HD+ Android Development] HarvHouHacker:
Regardless, I'd still like to try. Some things I want to resolve:

I know the Nook HD+ should have 1 GB of memory, but only 840 MB is displayed in Lineage OS. How do I override this value to show the absolute maximum amount my Nook has or can take?

I once had some 2000 apps installed, and the Nook suffered due to memory loss. I realize that I can't expand the physical memory, so I'm looking at swap for an alternative. I'd prefer this swap partition on my SD card. How can I do this?

CPU load also seems to be a problem. Again, I can't upgrade the hardware without getting a new tablet, so I'm looking to keep the processor optimized. Any suggestions?
[Nook HD, HD+ Android Development] mikeataol:
not possible. There is a "carve-out" of memory for the video subsystem
[Nook HD, HD+ Android Development] ST Dog:
The kernel reserves memory which is not reported to the system. The Linux kernel has done this for over 20 years.

After booting you can check the kernel log to see how much, but I don't know of any other way to get it.
[Nook HD, HD+ Android Development] HarvHouHacker:
I just installed Swapper & Tools to create a swap file. Does anybody know whether this is a good app? :fingers-crossed:

---------- Post added at 08:37 PM ---------- Previous post was at 08:01 PM ----------

Well, it should show the exact amount, for those of us who want to know. Even if the reserved memory can't be modified without screwing up Lineage OS, it can at least be compensated for by clearing or reducing memory of other processes. Being uninformed of what's going on in the background... well, that's a lot like Windows! :eek:
[Nook HD, HD+ Android Development] ST Dog:
Like I said, over 20yrs. The same argument was made then.

Feel free to get on the Linux kernel mailing list and convince Linus to change it.

BTW, it not hidden. It is clearly reported in the kernel messages. You just chose to ignore that information.

So maybe you can convince the Android developers at Google to pull that from the log and report the unusable RAM somewhere.
[Nook HD, HD+ Android Development] HarvHouHacker:
I think I may have made myself unclear. Not everyone is as geeky (Eh, Smart! I meant smart. :p) as we are. People who want to know how much memory there is won't automatically look in the kernel log; they'll look in Settings > Memory and assume that 840 MB (or whatever amount of memory it tells them) is all there is on the Nook HD+. Period. No exceptions. They won't even bother to Google it.

Pulling the memory report from the log isn't a bad idea, if it coincides with the idea is that the OS, despite relying on the kernel, may choose to collect its own information to better integrate with the hardware. Thus, in the Memory section, we can see a colored (perhaps dark gray) section of the bar where it is described as "Reserved memory" or "System memory". Just a thought.

However, this doesn't help with my first issue in post #2243, so I'm just going to drop the issue. The other two are still open to suggestion.
[Nook HD, HD+ Android Development] ST Dog:
BTW, the stock OS from B&N, and every other android manufacturer reports the same way.

My 2GB phone says 1.8GB.

Not sure why you think it's suddenly a big deal now for and old device like the Nook HD/HD+.

You can try a swap file, but it won't help much. And using an external SD card will aggravate more than help.

---------- Post added at 10:32 PM ---------- Previous post was at 10:06 PM ----------

Are you asking about RAM for running apps or storage space for installing apps?

that's a lot of apps and more than most devices can handle well. Certainly more than you can use on a regular basis.

A 100 or so user apps (not counting system apps) is all most ever use.

I wouldn't want 2000 apps on a current 128GB flagship phone nevermind an old tablet.

Install fewer apps. Remove ones that load the CPU with background tasks.

Don't use google services, they are resource hogs. Use alternative ways to access the Play store , or alternate app sources that don't need Google.

(I'll probably be changing to something other than gapps on my Hummingbird before long. Current Google services are just too much for it)
[Nook HD, HD+ Android Development] mikeataol:
I load a start up manager , something like ES Task Manager, and disable all the extraneous things that run at system boot, and/or connectivity change...
[Nook HD, HD+ Android Development] nmyshkin:
FWIW, I've done a detailed "how-to" for going GApp-less, but still being able to access the PlayStore and run the apps that depend on Google Framework Services. The instructions are directed to the 8 GB Nook Tablet, but are general enough to apply to any device. I would think that with the greater resources of the HD/HD+ you could still run the actual PlayStore app, but there is an alternative given as well.

https://xdaforums.com/nook-tablet/general/how-to-cm-11-8-gb-nook-tablet-bntv250a-t3667555

(about half-way down where it says "The General Process")
[Nook HD, HD+ Android Development] ST Dog:
Yea, I was being lazy and not linking.

But I was thinking of your thread and MicroG.
[Nook HD, HD+ Android Development] nmyshkin:
Yes, that's right. I use microG for the basic Google requirements. Only two small apps instead of all the MBs of Google stuff. And then you add just what you want after that. Certainly for the 8 GB Nook Tablet it's the difference between "forever on CM 11" and "runs Lineage 14.1". Even if they didn't occupy lots of internal storage (and they do), once they get fired up all the background GApps stuff kills the 8 GB NT with anything beyond CM 11.
[Nook HD, HD+ Android Development] asakurato:
Have been trying this all day, but I can't get root to work on aosp/lnos 14.1. Flashed both supersu and magisk (both fail at boot image stage). Flashed both su addons. I think they do nothing on aosp (I'm most likely wrong). On lnos, they enable root in developer settings, but root still doesn't work. This is on Ovation.
[Nook HD, HD+ Android Development] ST Dog:
The systemless stuff generally doesn't work due to the odd 2 stage boot on these tablets. It's mentioned w/r/t Magisk earlier in the thread.

But amaces last LN builds have included root. If not flash the lineage addon (linked in the 3rd post)