yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] digixmax:
ES File Explorer & ROM Responsiveness Performance

After years of using ES File Explorer I removed it and switched to another simpler but less intrusive file-manager app, FX File Explorer. Surprisingly my HD+ running LN14.1 (build 10/21) seems significantly more responsive, app installation or update also completes a lot faster.
[Nook HD, HD+ Android Development] theleagueofstream:
I've considered doing this just for the sake of seeing it's a bad connection, but apparently it requires double-sided tape to re-secure the battery?.

I'm hesitant, like ST Dog, to rip out a battery in exchange for a third-party product with only day-one reviews. My battery is currently manageable, but I've gone from charging it about once a week to every day and I feel I'm reducing its lifespan. This is a device that I depend heavily on for work and personal use so it's been a bit stressful trying to make a decision.

Thanks for the heads up.
[Nook HD, HD+ Android Development] ST Dog:
Yes, double sided tape. You can get a roll at a department store.

You may want some fresh tape for the bezel too. The old stuff might not be great after you remove the bezel.

Mine won't last more than a few hours of use now. But I'm usually able to plug in when it gets low.
[Nook HD, HD+ Android Development] rfrazier:
Unfortunately, hummingbird fails to build. The problem, I think, has to do with a new KeyHandler API (used in CMParts). Also unfortunately, I don't know how to fix it, so I thought that I would just pass it along.

Best wishes,

Bob
[Nook HD, HD+ Android Development] rs899:
He is using the date format that most of the developed world other than the US uses....you need to travel more.....
[Nook HD, HD+ Android Development] KnowledgeBroker:
Yes, I get the difference in formats.. It was intentionally a joke. I don't care where you live, it isn't typical to get 10 months.. Hence the sarcasm. But, yes, in the US it would literally be read as 10 months from now. And yes, if you want English speaking people to reply, English is required ;)

If you mean my blue tooth adapter- yes, it works with every other device I've used.. It pairs, but then it isn't find within the app. Just got my parents to buy 2 lg stylo phones for Xmas (cheap at Walmart), and it works perfectly.

I'm starting to wonder if cm12.xx has Bluetooth issues since my phone also does the same (and also on cm12)

That's why I'm looking for feedback about Bluetooth with this ROM.

I'll be able to give feedback shortly, after updating to the twrp mentioned earlier, I just successfully flashed it.. And it did have a boot animation. The 1/3/16 build.
[Nook HD, HD+ Android Development] herges:
External SD Card shows as corrupted

Hi All,

I've installed the cm_hummingbird-ota-MMB29M.160103 on my 8GB Nook HD. Great work and thank you everybody - involved it runs really smoothly!

However I've got a 32GB SanDisk external SDCard which is detected fine. I then get the choice to format it as "Use as internal storage" or "Use as portable storage". If I select internal the format starts but at 60% I get a message as follows:

"This SanDisk SD card appears to be slow.

You can continue, but apps moved to this location may stutter and data transfers may take a long time.

Consider using a faster SanDisk SD Card for better performance."

After clicking OK I get the menu to move data to new storage. I select "Move now" and the Move which then force closes settings with "Unfortunately, Settings has stopped."

If I select "Move later" the SanDisk SD card is then shown as Corrupted in storage.

Any idea what's causing this or has anyone successfully used this Marshmallow feature?

I've got two of these cards "SanDisk Ultra 32GB MicroSDHC I" and both show the same behaviour.

Many thanks,

herges
[Nook HD, HD+ Android Development] asakurato:
Didn't do anything unusual, just flashed without wiping anything, just after flashing Jan 03 build.
[Nook HD, HD+ Android Development] belfastraven:
Are you trying to get the marshmallow boot animation? The attached works for me on Hummingbird, so if it works for you it might be too small, but if you want to try

just copy the attached bootanimation.zip file to /system/media/bootanimation.zip on your device and change its permissions to 644 (rw-r--r--). You need to rename your old bootanimation first, of course.

I found that the one listed as 800 did not work for me on hummingbird--it looked "squashed". The only difference I could see on this one was that dimensions were slightly different in the desc file and the pngs--, but this one works fine.
[Nook HD, HD+ Android Development] acr123:
The problem why I did not get a boot animation is that since I was using a theme with my launcher it appears that the bootanimation used is not in system/media but located in data/system/theme. When I put the marshmallow 800p file and also your bootanimations.zip file it WORKED. I guess location for the file is very important and specific to what you are using. Hopefully this info will help others. Also, were you able to get any of the landscape boot animations to work?? The marshmallow1080p landscape did NOT work for me. These would look much nicer since I usually have my nook in this position.

Al

---------- Post added at 07:57 PM ---------- Previous post was at 07:08 PM ----------

I was able to get the marshmallow 720p landscape animations to work by manually putting the bootanimation.zip into the correct location instead of flashing through recovery.

Does anybody know how to change the desc file so that the animation could be larger for the Nook HD+ where the screen resolution is screen is 1920 x 1280

Thanks,

Al
[Nook HD, HD+ Android Development] belfastraven:
You can edit the desc file and change the first two numbers, but I think you'd need to use a landscape bootanimation file. Normally, the a device is supposed to be smart enough to present the PNG files with the numbers in the desc file, but it doesn't work on all devices, in which case the numbers in the desc file would need to match the pixel width and height numbers of the png files. Not sure about our nooks.. I don't believe you can hurt anything by trying--it's just that the animation won't work.
[Nook HD, HD+ Android Development] belfastraven:
Build problems and deprecation of BusyBox

Additional info.tried to build cm13 hummingbird this morning and am now stuck here: [MENTION=4473900]amaces[/MENTION],

build/core/static_java_library.mk:125: recipe for target '....../android/system/out/target/common/obj/JAVA_LIBRARIES/com.android.emailcommon_intermediates/src/R.stamp' failed

make: *** [....../android/system/out/target/common/obj/JAVA_LIBRARIES/com.android.emailcommon_intermediates/src/R.stamp] Segmentation fault (core dumped)

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

build/core/package_internal.mk:276: recipe for target '......./android/system/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk' failed

make: *** [......./android/system/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] Segmentation fault (core dumped)

make: *** Deleting file '......./android/system/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk'

Added:2016/01/08: After trying many things, re syncing , updating installed software, etc. running a make clean and then make bacon worked. I'd still like to understand what was stomping on the memory before...

Did not know whether you had seen this re busybox:

http://review.cyanogenmod.org/#/c/119819/

Also noticed that Screencast has showed up in last couple of my builds. It's not working--but I haven't figured out why, yet.

thnx
[Nook HD, HD+ Android Development] ST Dog:
That's the order of precedence working as it should.

If a file is in the first location it's used. If not, it looks in the next location, down to the last one, system/media. If none found it uses a infernal default. (Not sure what the search path is on MM/CM13)

You theme uses a custom animation install on /data (because it's writable and /system often isn't).

You can delete the theme installed file, and it will go look in the other locations.

Or, replace the custom one as you did. Problem there is, if you use another theme, or reinstall that one, the animation will be overwritten. If in /system it won't be and you just delete the theme animation to get the other one

Common thing in the *nix world. (Remember Android has Linux underneath)
[Nook HD, HD+ Android Development] acr123:
I'm not sure I understand exactly what you are saying. When I put the bootanimation.zip file into the primary location it did not work. If there is some sort of hierarchy as to what the priority, for the different location are, it would be useful to know. If you could you list them so I can try what "system" location would work wince I would like to not have the bootanimation.zip overwritten..

Thanks,

Al
[Nook HD, HD+ Android Development] KyJelly69:
I have read 10 pages of this thread and have not found any download links. There is one in the op of the 12.1 thread. Is this where the marshmallow rom is?
[Nook HD, HD+ Android Development] vinceweis:
Yes, they are all in the same place. The files have either lp or mm somewhere in the file name.
[Nook HD, HD+ Android Development] sasmith-129:
Yes, that's it. Under the appropriate device folder and named aosp_<device>-MM* (or something similar to that).
[Nook HD, HD+ Android Development] belfastraven:
Yes-- in Hummingbird folder for nook hd and Ovation for hd+. There is also a new TWRP 2.8.7.5 which you should flash first. Be aware that there is still one lollipop rom in the folder, and two MMs/cm13 if you are moving from cm12.x/Lollipop

you should do a factory reset and flash the rom, gapps (opengapps.org gapps work) and superSU ,if you want it (2.52 works), one right after the other before you reboot. The cm rom does come rooted.

I always do a nandroid backup before I flash major changes, just in case :)
[Nook HD, HD+ Android Development] ST Dog:
Yes, a hierarchy (path search order). It checks /data/local first, if not found then /system/media, before giving up and using a built-in default.

Those are the two I know of, but more could be added or be changed by the developers.

often in *nix, programs check 3 or 4 places for a configuration file.

User home directory

Local machine directory

System config directory

Application directory
[Nook HD, HD+ Android Development] KyJelly69:
Flashed twrp. Rebooted back to recovery. Factory reset. Flashing rom and it is taking forever. This normal?
[Nook HD, HD+ Android Development] brenyoka:
What is the difference between the AOSP and CM builds? Will flash this weekend so just curious which one would be better overall. Thanks.
[Nook HD, HD+ Android Development] belfastraven:
The actual flashing shouldn't take longer but the first boot will take considerably more time than if you had just installed a ROM with the same major version that you had...
[Nook HD, HD+ Android Development] KyJelly69:
Stuck on "patching system image unconditionally"
[Nook HD, HD+ Android Development] belfastraven:
That shouldn't happen.

As long as you have a backup of previous system, try wiping system, then flashing rom,gapps, whatever again.

Also, are you sure that your download of the rom finished correctly?
[Nook HD, HD+ Android Development] belfastraven:
I just rebuilt hummingbird successfully . I see that in the last few hours there were changes to [MENTION=4473900]amaces[/MENTION] repository. I did see the change you mentioned in the lineage repository which was made a couple of days ago. I haven't had time yet to check through all of the changes, but you might just want to try building again.

FWIW
[Nook HD, HD+ Android Development] rfrazier:
Many thanks. I will.

Best wishes,

Bob
[Nook HD, HD+ Android Development] ParadoxGBB:
Last post from me with regard to batteries --- but my wife and myself just got back from a weekend trip that might provide some data that isn't a one day review.

My wife has a referbished nook I got on ebay with what I assume is the original battery inside (not really interested in opening it up unless there's a problem). She had it on all weekend, on medium low brightness, with wifi off, and used it to read 4-5 hours total off and on, without plugging it in, until we were back home in two days. She was at about 13%.

I had mine on standby the entire time, never turned wifi off, always have my brightness on very low (I almost always use it before going to sleep at night) but just ended up using my phone instead rather than using the Wifi at the place we were using since everyone there was using the WiFi. When I got home and plugged it in next to my nightstand I was surprised to see that it was still at 91%, so very little idle drain. I usually don't keeep it unplugged and idle for that long --- usually I end up turning it off when I go for a trip, so I was largely guessing before when I thought 2-3 days idle.

Obviously everyone has their own preferences and preconceptions here, but unless you consider a Nook HD a collector's device, I don't quite understand why anyone would be too overprotective for a device that's less than $35 in the market today. That's not to say I don't love, use, or rely on my Nook (I do!), but at some point when it's not working for me as well as I know it should, I'm willing to roll the dice a bit to extend its lifetime, and if that goes sideways, then I don't feel like I just voided a warranty on an iPhone X or whatever. In my case it worked out pretty well and so I'd still recommend it for anyone who wants better battery performance.

As for the tape, I think I ended up re-using the tape that was already in there to hold the battery and that worked fine, but it was a while ago and as you can tell my memory kind of sucks.
[Nook HD, HD+ Android Development] rfrazier:
I got a HD+ in 2013 (I believe) and a couple of HDs in 2014. All refurbished. (I use the HD+ for reading PDFs and the like in my office and one HD for a bedside radio alarm. The other HD isn't used much these days.) The batteries on them have lasted better than I expected. Yesterday I "woke up" a HD that had been idling for a week. It reported that it had 72 days of battery left. A bit optimistic, but .... It doesn't have GAPPS. WIFI and BT were off.

An aside. Hummingbird builds again.

Best wishes,

Bob
[Nook HD, HD+ Android Development] secretwolf98:
There are problems with the hummingbird ROMs. I can never find a suitable ROM to stay on. I have a full 32 GB SD Card full of hummingbird ROMs to install. I don't know why I don't delete some, but it isn't bothering me. So, what I am trying to get at, do you have any suggestions that would work for video games, no battery drain fast or false battery percentage, no lag, right side up screen, or what you think that will work for my use? I also use ROOT, but not much. Themes are ok, but I don't use them a lot like a lot of people. I had a Nook HD for 5 or 6 years. I won it from my Library. I didn't have to do anything for it all I had to do was, put in my name on a piece of paper and put it in a box (Score! That's how I started Android).
[Nook HD, HD+ Android Development] rfrazier:
I'm afraid that don't have much advice, especially since we have different use cases. I have zero experience with video games, although my guess is that the HD tablet is underpowered for them. I don't have any experience with roms for HD/HD+ other than CM/Lineage.

Best wishes,

Bob
[Nook HD, HD+ Android Development] ST Dog:
I used the last CM11 build for years (as did my wife on her HD and HD+). It was getting laggy, probably from Google updates.

A fresh install likely would have fixed that.

I decided LN14 was with trying and I can always revert. It's fine other than the upsidedown screen in certain apps (most support rotation). Not as fast as CM11 was fresh, but faster than it was when I changed.
[Nook HD, HD+ Android Development] secretwolf98:
I've use CM 11 before. And when I decide to play video games, I start at 100% and about 15 minutes later it says 1% of battery. I plug it in, it says 40% of battery. I also noticed that if I don't use the Nook, the battery dies on me. I just want to find a good ROM for my Nook and call it good. For gapps, I always use opengapps.org, ARM | 4.4 | pico.
[Nook HD, HD+ Android Development] ST Dog:
Never had that issue.
[Nook HD, HD+ Android Development] secretwolf98:
Strange. What build are you using? I used my LineageOS 11 and CM 11 8-15-2016.
[Nook HD, HD+ Android Development] nmyshkin:
It may be an actual battery issue, but we had that same issue with my husband's HD running CM 12.1 (I don't think the OS matters).

There are a number of posts about the problem. A "consensus" fix is to reflash stock, do a factory reset (so, yes, you have to revert to stock completely,

including

stock recovery), boot into stock and let it sit for awhile (15 min?). If you have a B&N account you can sign in, etc. If not, then just let the tablet sit idle, then shut it down.

Now flash your new ROM, but first check your SD card. Be sure it is properly prepared. The popular opinion is that repeated flashing messes up the battery regulator/stats reporting, etc., in some way. Returning to stock for awhile resets all of that. As to the card, we found that I had inadvertently prepared a bad card in an attempt to run down the problem. My "bad" card was set to 0x0b instead of 0x0c and that seemed to cause yet another odd issue: not booting completely unless plugged in.

The short of it is that returning to stock, doing a factory reset, and carefully preparing a new SD card fixed all the weird issues, including the sudden battery drop that disappears when the tablet is plugged in for a bit (not to mention needing to be plugged in to boot!).
[Nook HD, HD+ Android Development] secretwolf98:
I guess I could ask for new Nook HD for Christmas. My first Nook HD, didn't have any battery problems.
[Nook HD, HD+ Android Development] ST Dog:
I'll have to check which CM11 build I was using. Probably one of the last official nightlies.

I used the Nov 2014 SD install for a long tine before moving to EMMC. Just not sure when I made the change now.

Didn't update it much as what I had worked great so no need for a newer build. But I may have grabbed the last official build when CM was killed.
[Nook HD, HD+ Android Development] nmyshkin:
You could. After tearing out much hair over the battery/booting behavior I described above I bought my husband another HD from ebay. But in the end, the procedure I described fixed the problems with the original HD, so now the "new" one sits in a box in a drawer, to be charged occasionally and held against the inevitable day when the original gives up the ghost. We don't judge it as a "loss" exactly, but I could have saved the $40.
[Nook HD, HD+ Android Development] secretwolf98:
Stock don't last long either with the battery.

---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------

I will be releasing another build of my LineageOS 11 build later today or tomorrow. https://xdaforums.com/nook-hd/development/rom-lineageos-11-t3665351
[Nook HD, HD+ Android Development] ST Dog:
Looks like I had 20160111 nightly and pa_gapps 4.4.4 from 20150308. I've got both micro and nano so not sure which I installed. Oh, I used twrp-2.8.7.0.

But the combination was great until a few months ago when it got really laggy which was probably due to Google updates.

---------- Post added at 11:24 PM ---------- Previous post was at 11:22 PM ----------

Still don't get what you've changed from CM11 to make that. But I doubt I'll go back to KK with 14.1 working so well.
[Nook HD, HD+ Android Development] secretwolf98:
Update the apps and update the security patch.
[Nook HD, HD+ Android Development] secretwolf98:
I am thinking about stopping development for the Nook HD...

I just attempted SlimKat, 2 times and both times were a fail. I don't what's going on. :confused:
[Nook HD, HD+ Android Development] :
I've temporarily seen this with a different device and it continues to work properly most of the time. If its a problem or happens too often, then yes trying different things to get the battery stats back on track would be the first step.

If nothing works then the correct thing wasn't tried or its a physical problem.

You could also just keep it plugged in and use it as a picture frame or media device in the kitchen or who knows what. Keeping it plugged in doesn't hurt the battery - I should know, mine has been plugged in nearly 24/7 for years now and when I actually unplug it, the battery has no noticeable difference in usage.
[Nook HD, HD+ Android Development] ST Dog:
Not a clue. Never used SlimKat.
[Nook HD, HD+ Android Development] ieatabiscuit:
I've seen a bad or worn out SD card cause the battery to act totally nuts on a spanking NEW fresh opened plastic sealed ovation. Removal of said SD card eliminated the battery confusion and reinstallation caused it to return on demand. Also, I had the inevitable battery failure once, and could not find a proper replacement for a reasonable price. I simply desoldered the original batteries from the controller and replaced them with 2 LIS1558ERPC batteries. They go to a Sony Experia Z3, and offer just a tiny bit more total capacity, and otherwise perfect performance. They are slightly thicker than stock, and noticeably smaller in length and width. The thickness does not effect the screen, or case in any way, I still have to use adhesive to hold it in place actually. For those that like to tinker, it's an easy project, but do be careful, they are live batteries, and can shock you if you get careless. NOTE: The tabs on the Experia batteries will not match perfectly with the tabs on the Ovation controller PCB, you will have to run some wire to accommodate this. Other than that, it's a very simple 1 to 1 swap. Don't bother with clipping the thick metal pads off the battery, as they are spot welded to them. Instead, heat them up, they are only soldered to the PCB, but LOOK like they are fixed more permanently. I've found 3M adhesive spray works to replace the front trim, and to hold the battery in place better than double sided tape also. One thing to note, do NOT peel up anything from the backing of the screen, they are grounding points, and will cause havoc. Just remove the screws, pop the back off, and the battery will be stuck to that back plate. For those of you not willing, or wanting to go that in depth with things, I wish you luck. I personally can't keep my fingers out of my electronics, so there's your reason for why i had gone to that length for an old tablet that has become a niche project purely for us hobbyists.
[Nook HD, HD+ Android Development] drmarble:
Homebuilding LineageOS 14.1

Those of you who have tried building airend's lineageos 14.1 have noticed that it hasn't worked for the last week or so. That is because the LineageOS repositories uptated to match AOSP r36. I have submitted two pull requests that fix the build. One consists of three commit to the default android manifest. The other is a change to frameworks/base. With these changes it builds, flashes and runs just fine.

You can find these pull requests on github: airend/android and airend/frameworks/base.

You can also find them on my github account: drmarble/android (-b r36), and frameworks/base-1 (-b kCaller). The -b designates the branch containing the updates to the cm-14 branch.

I hope/expect that Andrei Măceș will commit these to his trees so that LineageOS-14.1 builds can continue.

I am working on LineageOS-15.1 but am not making sufficient progress. OMAP kernels and device trees get harder and harder to update the each new android version.
[Nook HD, HD+ Android Development] drmarble:
Well, you can ignore my post above. airend pushed his fixes to the manifest and other repositories. It now builds just fine after a repo sync. His changes are better than mine as he really understands all the changes he has made to the lineageos code tree for the ovation. I just know enough to fix errors. It is working great again.
[Nook HD, HD+ Android Development] rfrazier:
Thanks to both.

Best wishes,

Bob