yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Zippy Dufus:
Build still not working

After some more commits, now it doesn't build at all.

ERROR: /home/android/packages/apps/Settings/src/com/android/settings/accessibility/ToggleAccessibilityServicePreferenceFragment.java:60: The import android.view.WindowManager.LayoutParams.PRIVATE_FLAG_HIDE_NON_SYSTEM_OVERLAY_WINDOWS cannot be resolved

ERROR: /home/android/packages/apps/Settings/src/com/android/settings/accessibility/ToggleAccessibilityServicePreferenceFragment.java:187: PRIVATE_FLAG_HIDE_NON_SYSTEM_OVERLAY_WINDOWS cannot be resolved to a variable

[ 88% 30190/34192] target arm C: libavcodec <= external/ffmpeg/libavcodec/aacadtsdec.c

[ 88% 30190/34192] target arm C: libavcodec <= external/ffmpeg/libavcodec/aaccoder.c

[ 88% 30190/34192] target arm C: libavcodec <= external/ffmpeg/libavcodec/aacdec.c

In file included from external/ffmpeg/libavcodec/aacdec.c:260:

external/ffmpeg/libavcodec/aacdec_template.c:3078:21: warning: passing 'const uint8_t *' (aka 'const unsigned char *') to parameter of type 'void *' discards qualifiers [-Wincompatible-pointer-types-discards-qualifiers]

AV_WL32(side, 2*AV_RL32(side));

^~~~

external/ffmpeg/libavcodec/../libavutil/intreadwrite.h:182:38: note: expanded from macro 'AV_WL32'

# define AV_WL32(p, v) AV_WN32(p, v)

^

external/ffmpeg/libavcodec/../libavutil/arm/intreadwrite.h:59:44: note: passing argument to parameter 'p' here

static av_always_inline void AV_WN32(void *p, uint32_t v)

^

1 warning generated.

[ 88% 30190/34192] Building with Jack: /home/android/out/target/common/obj/APPS/TeleService_intermediates/with-local/classes.dex

[ 88% 30190/34192] Building with Jack: /home/android/out/target/common/obj/APPS/SystemUI_intermediates/with-local/classes.dex

ninja: build stopped: subcommand failed.

make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1

make: Leaving directory '/home/android'​
[Nook HD, HD+ Android Development] belfastraven:
the only errors I see here are the two about PRIVATE_FLAG_HIDE_NON_SYSTEM_OVERLAY_WINDOWS and - it looks to me like the repository was updated on the 15th --

https://github.com/airend/android_frameworks_base/commit/5a7a7e96fe117f85c30724db858bacaa6760446d

which I would have thought would fix your issue. I just built and installed (with a different kernel/device branch-but that shouldn't matter with respect to this bug, I would think.) will no problem.

Did you resync just before you built? You were building the cm-14 branch. ? If so, perhaps try a clean build..​
[Nook HD, HD+ Android Development] Zippy Dufus:
I do a clean build:

Completely remove everything but .repo as well as another directory containing my build scripts from the build directory.

I don't have any special local manifest.

I did a straight build without my custom Linaro toolchain.

Up until the 09/15, it would build but not boot.

Oh!? See some more commits. Time to try again!

Thanks for your reply.
[Nook HD, HD+ Android Development] digixmax:
I am still having this issue with the 08/13 build, so I am curious whether others also have same issues and if so which launchers they are using.
[Nook HD, HD+ Android Development] vinceweis:
I had my wallpaper revert maybe twice. I just change it back and move on. I use Nova. I have tried trebuchet, Arrow, Google, and a couple others and always come quickly back to Nova. It just always seems the smoothest and quickest for me with plenty of customization options,
[Nook HD, HD+ Android Development] digixmax:
I too much prefer Nova Launcher over others, but I'm interested in finding out if the wallpaper revert issue is peculiar to Nova.
[Nook HD, HD+ Android Development] rtarv321:
I have used Nova for years. I too had the wallpaper problem up until the latest version. I am currently running lnos-ovation dated 8-14-2017 and have not experienced the wallpaper issue using Nova
[Nook HD, HD+ Android Development] dbrickg:
Using Nova here, too. I've never had the wallpaper issue. But I'm using a blank black wallpaper. I don't understand how that would affect the issue, but just putting it out there in case anybody else sees a connection
[Nook HD, HD+ Android Development] digixmax:
The freeze issue I am having with my HD+ running build 08/13 is getting worse in frequency and length.

FWIW - dmesg diagnostic following the last incident is posted at http://www.mediafire.com/file/981vykm6ybj40yy/dmesg-lnos0813-freeze.txt.
[Nook HD, HD+ Android Development] NE0HP:
If you’re looking for better alternative to Nova then I would recommend you to try [MENTION=7049589]deletescape[/MENTION] ‘s launcher app name “Lawnchair - Customizable Pixel Launcher” from this link https://xdaforums.com/android/apps-games/lawnchair-customizable-pixel-launcher-t3627137 It is in beta development but works perfectly fine. You can also try it out the latest Alfa version from this link [url]https://lawnchairmirror.duckdns.org[/URL] which is also works fine and dev is updating it almost on daily basis by adding more features!
[Nook HD, HD+ Android Development] yerman:
flashed aosp_ovation-ota-NKG47S.170811.zip and it is fabulous, this Nook has never been so smooth.

Superb, thankyou
[Nook HD, HD+ Android Development] Zippy Dufus:
FYI, I got my first bootable build since 07/22.

Thanks!
[Nook HD, HD+ Android Development] fuzzychicken:
EXACTLY same problem. Did you manage to address it?

I have just flashed the ROM and didn't install Gapps or SuperSU as it takes forever to boot.

Thanks in advance.
[Nook HD, HD+ Android Development] io7m:
I couldn't address the problem, unfortunately.

I ended up installing the AOSP build instead, and that seems to work correctly.
[Nook HD, HD+ Android Development] fuzzychicken:
Same here. Have been playing around with older versions of the ROM since yesterday. Same problem with each and everyone. Just installed AOSP and its working, except for wifi. Wifi doesn't stay connected

Which version of SuperSU did you install? The standard chainfire version leads to forever boot.

Thanks in advance.
[Nook HD, HD+ Android Development] twiztid_:
I'm not sure if this is for Android, or GApps, and I recall that in the past someone strongly discouraging doing this, but you you could try renaming (or deleting) system\privapp\SetupWizard.apk
[Nook HD, HD+ Android Development] Nemesis1278:
If you're using lineage I have noticed the wallpaper reverting back to the original. I think it may be due to the system.ui being put to deep sleep. I have also noticed with the accuweather app that it is unable to update because of deep sleep. I took it off of the system.ui and weather app and now my wallpaper seems to be stable and weather app is refreshing. I have Gapps installed and am actually using the google launcher along with most google apps since the lineage apps are out of date. I have turbo zram running and this with some mods to the init.d file seem to allow the system to run smooth with minimal lag. Hope this helps although I think I went off topic slightly.
[Nook HD, HD+ Android Development] digixmax:
How does one change the deep-sleep setting for system.ui or another app?

TIA.
[Nook HD, HD+ Android Development] xMandy:
[MENTION=4473900]amaces[/MENTION]

First thanks for your cool and impressive work to keep our nooks alive! :good:

Do you know when you'll find time to create/cook a new "nightly" for the hd+ with latest security patches and so on?

Btw, do you have plans to port it to v8 also? ;)

thx from munich,

xMandy
[Nook HD, HD+ Android Development] twiztid_:
Would you mind doing a quick write up on the changes you made and any steps involved in making them?

Thanks!
[Nook HD, HD+ Android Development] Nemesis1278:
To change the deep sleep settings you go to settings ->Battery-> then on the top right the three button and Battery Optimization->Select all apps.

Then choose the apps that you want to prevent from going to deep sleep and select to not optimize that app.

With Turbo zram once you set it, it will write a file to init.d folder. You can use root browser to go to the init.d folder also you will need root for this. Once root browser is open go to System->etc->init.d. There you will find a file named S01turbozram. Select the file and open it as a text. You can use RBtexteditor to edit the file. once open you should only need to edit the top four lines which will look like

swapoff /dev/block/zram1;

swapoff /dev/block/zram2;

swapoff /dev/block/zram3;

swapoff /dev/block/zram0;

change the swapoff to swapon and then restart. The system should run better afterwards. I believe you only really need to change is the one on zram0 but I change them all to be safe.

If you need to install turbozram. You can get it from here. https://xdaforums.com/showthread.php?t=2422040&page=65

There is also busybox that you will need to install.
[Nook HD, HD+ Android Development] rfrazier:
I just wanted to thank [MENTION=4473900]amaces[/MENTION] for providing source for the builds. Having decided that I wanted to have local builds for my 2 HD and 1 HD+ so that I could sign with my own keys, I had a go at it yesterday, and it all went smoothly.

I had to set up a completely different build tree than that I'm using for "official" lineageos builds as I don't know enough about git and the build trees to integrate them as much as possible, but that's no big deal.

It was a pleasant surprise to find that the self build had the latest security patches incorporated.

Best wishes,

Bob
[Nook HD, HD+ Android Development] MossyTC:
Official LineageOS has applied patches for the Krack Wifi vulnerability. Are there plans to include these patches?
[Nook HD, HD+ Android Development] twiztid_:
From what I understand, amaces' builds are "unofficially official".

There's a few issues/fixes/reasons that prevent(?) it from being an official/nightly build, but beyond that his code should include the patches included in LNOS.
[Nook HD, HD+ Android Development] MossyTC:
I should have thought to check the sources. There's a new "wpa_supplicant" repository on amaces' github page so he's obviously looking at it.
[Nook HD, HD+ Android Development] amaces:
KRACK, Oreo Plans, etc.

Definitely my goal, and these were the devices I first started porting to Oreo, but this release really strains the limits of our current kernel and vendor blobs. Fortunately, updated blobs have recently become available, yet legally it's not possible to incorporate them into public builds. I don't know when this will change, and given that it took years to get here, I need to continue working on the old DDK for Oreo. The second issue is about current Wi-Fi stack, which fails on Oreo; the new drivers that I prepared before summer do work, but then about a third of people here didn't like them.

If we're lucky and these two issues can be solved with current drivers, Oreo builds can happen sooner. Otherwise, it all depends on the ability to distribute the new DDK blobs.

These devices are severely RAM-limited at this point. All sorts of races happen between LMK, zRAM, and other memory management with increased memory pressure, which is a constant state after adding GApps... Oreo might slightly improve this management, but really we need better kernel, graphics DDK, and many other things where progress is slow.

New builds are uploaded in experimental. Unfortunately, Google has stopped updating 7.1.2 since August, but at least KRACK and possibly BlueBorne should be addressed in the latest AOSP builds. Lineage also includes these fixes, and more. At some point, I need to update the thread to highlight the Unlegacy-Android builds, which happen weekly, and tend to incorporate all security patches on AOSP.
[Nook HD, HD+ Android Development] rfrazier:
The local Hummingbird and Ovation lineage builds I did on 17 Oct. had the wpa_supplicant fixes.

I use a Hummingbird as a bedside clock and music player. It would be useful to keep it plugged into a charger, but set limits on when it charges (e.g., start charging when it falls below 40%, but stops charging when it reaches 80%). There is an app for this, but to get it to work with a device, one needs to know what file, if any, sets charging on and off (usually a switch between "1" and "0"). I've looked (and looked) but can't find the appropriate file. Any help would be appreciated.

Best wishes,

Bob

PS These devices (Ovation and Hummingbird) work better and reasonably well without GAPPS. The Hummingbird in front of me is using 529MB of 860MB total memory (61%).

RLF
[Nook HD, HD+ Android Development] nmyshkin:
FWIW, I have described here: https://xdaforums.com/nook-tablet/general/how-to-cm-11-8-gb-nook-tablet-bntv250a-t3667555

a method for accessing the PlayStore without GApps. My experimenting has been with the 8 GB Nook Tablet which has limited RAM as well as limited internal storage. I would expect that with the greater (albeit finite) resources of the HD/HD+ you could stop at step 11 with the sign-in to the PlayStore. This would allow you to purchase apps, if you chose, as well as access all the free ones.
[Nook HD, HD+ Android Development] dbrickg:
just downloaded and installed the lnos ovation 171021 zip. dirty flashed it over the last version, and everything booted and seems to be happy and shiny new. thanks much, amaces
[Nook HD, HD+ Android Development] ST Dog:
Can you expand in that or point me to something that does?

I don't recall the issues, but if it would give 2/3 the option for O, I'd think it worth switching. Maybe later work can improve them.

Hard to believe it's become such an issue. There are still a lot of devices sold with 1GB and less RAM.

Maybe Go would be helpful? Is AOSP or LOS looking at a Go version?

So your latest builds have the newest LOS patches?
[Nook HD, HD+ Android Development] ST Dog:
Did you verify that the fixes for Blue Born and KRACK are Incorporated?
[Nook HD, HD+ Android Development] dbrickg:
found amaces quote about including a fix for KRACK and possibly BlueBorn. see above. but he does say "possibly BlueBorn", so it's not totally clear whether those fixes are included or not. if you know of some way to check, i'll be happy to do it. just let me know, and i'll get back to the group.
[Nook HD, HD+ Android Development] ST Dog:
Only test I know of is this app. Accuracy is questionable base on what I've seen.

https://play.google.com/store/apps/details?id=com.armis.blueborne_detector&hl=en

It wasn't clear from amaces post if his code has the ASOP/LOS patches or not. The discussion of Google not updating muddies the water.

I think he was saying it does. Just looking for confirmation.
[Nook HD, HD+ Android Development] secretwolf98:
I know you are still working on Oreo, but could I try it? It's my dream to try it. Or could you show some pictures of Oreo for hummingbird / ovation? Thanks for your awesome work for keeping the Nook's alive :)
[Nook HD, HD+ Android Development] rfrazier:
I'm very new at self building, but my understanding of how things work with the nooks (and lineage devices in general) is that as much standard stuff is included from lineage and aosp as possible. Then necessary local changes are made. So, if the changes are general, they are automatically included. The patches for BlueBorne and Krack seem general. I checked the git logs for the Nook build tree and the patches are there. So, any recent build (after they were patched in aosp/lineage) will include them.

Best wishes,

Bob
[Nook HD, HD+ Android Development] ST Dog:
I still haven't figured out git or how to track the changes.

Maybe if I had a build environment setup up it would make sense, but trying to follow stuff online just doesn't make sense.

Wasn't clear how recent the patches were vs when synced.
[Nook HD, HD+ Android Development] ajislav:
This app has previously claimed my ovation as being vulnerable, but with the latest experimental build it claims it is not.

TLDR, BlueBorne fixed
[Nook HD, HD+ Android Development] dbrickg:
hmm, yeah, judging from the comments on that blueborne vulnerability scanner, the app is pretty useless. i actually installed it, then read the comments, and uninstalled it immediately
[Nook HD, HD+ Android Development] marscandybars:
Where is the link to ovation lineage ROM?
[Nook HD, HD+ Android Development] w1ll1m:
In the OP
[Nook HD, HD+ Android Development] king200:
Xposed v88.1 works with Ovation AOSP. Almost all of Gravity Box works. I found rom unstable and several applications crashed. IMHO, if you want many of the Xposed features, use Lineage rom.

This post is not meant to get reply but for information only.
[Nook HD, HD+ Android Development] secretwolf98:
LineageOS 14.1 is my daily driver on hummingbird.
[Nook HD, HD+ Android Development] neutronjeff:
I just loaded the 1021 Ovation LnOS build. Seems good.

Thanks [MENTION=4473900]amaces[/MENTION].
[Nook HD, HD+ Android Development] ST Dog:
You ever get a chance to look into Magisk the installer?

Would be nice to be able to use a few apps that fail due to SafetyNet.
[Nook HD, HD+ Android Development] theleagueofstream:
Is anyone else getting severe battery drain with screen-on time? (HD+)

I've been switching between builds, trying battery savers (Greenify, Amplify ,etc.), battery monitors, wakelock detectors, Privacy Guard limitations, disabling services, screen brightness, etc. and the drain is significant.

Is this just due to limitations of the hardware? I didn't have this issue on CM 10.1 (Upgraded last week.) I'm currently on a build from January. Is the experimental build worth a try?
[Nook HD, HD+ Android Development] nsfgp:
No Issue with battery drain. Use the 10/21 latest ROM in experimental. It works great.
[Nook HD, HD+ Android Development] theleagueofstream:
Is there a significant difference in performance? I've wiped and reinstalled ROMs (as far back as stock factory reset) and apps about ten times this week with no results and don't want to do it again with the same result.
[Nook HD, HD+ Android Development] ST Dog:
You really think we can remember 10 months ago with enough detail to compare?

Just dirty flash the Oct build and see for yourself, while you have the Jan build fresh in your mind.

Mind you there are many other fixes/changes along the way, but the 10.21 build seems reasonably. Maybe not quire as good as CM11, but still good.
[Nook HD, HD+ Android Development] theleagueofstream:
No, I am just looking for any kind of lead and I've figured the users here are more in tune with how the builds have improved over time.

I recently switched over from CM10.1 to LN14.1 and have been getting misreported battery (it worked fine previously) Specifically, it will drop 15-20% every 10 minutes or so, and stay at 1% for several hours.

What I've tried to fix the issue:

Draining to 0% and recharging to 100% (i.e. manual calibration listed on XDA)

Battery Calibration Apps

Flashing down to stock ROM, factory resetting, and re-flashing 14.1 (I read this could restore a battery file that has been affected by repeated flashing of ROMs.)

Flashing back down to CM10.1 and CM10.2 (also tried CM11 and CM12 builds)

Wiping DALVIK/Cache between each install

Battery Monitoring Apps (Rooted)

Battery saving/hibernation apps

Adjusting nearly every power consumption option (screen brightness, WiFi, etc.)

Anyone have any tips on where to look next? Is this just an issue with LN on HD+ in general? Thanks in advance for any help.
[Nook HD, HD+ Android Development] ST Dog:
I didn't​ use earlier builds of LN14, but I don't recall much discussion about battery issues, but search the thread for similar issues.

I haven't noticed that on my HD.

My wife's HD+ was having battery issues on CM11 so not a fair comparison (figure it's just getting old).

Did returning to CM10 or 11 show the same or did it revert back to old behavior?
[Nook HD, HD+ Android Development] theleagueofstream:
The behavior has been the same switching between any ROM of CM, LN, Stock/Factory Reset from the point that I first upgraded from CM10 to LN14 recommended here.

Right now, it's been at 1% for 7 hours or so with about 2 hours of screen-on time. I don't think it's a lack a capacity and it has to do with misreporting.
[Nook HD, HD+ Android Development] ST Dog:
Tbe fact that CM10 and stock show the same battery behavior makes me think it's hardware not software.
[Nook HD, HD+ Android Development] theleagueofstream:
I haven't tried recalibrating/draining on CM10 or stock, but I don't know if that would be pointless since I've attempted it three times on LN14 with no success. Also, I don't know if the process causes battery issues long-term. Right now, I'm looking to see if TWRP reports the same battery level as LN14. Last night, I was at 1% for 10 hours or so, including ~3 hours of video trying to discharge.
[Nook HD, HD+ Android Development] ST Dog:
Full return to stock should clear any issues from other ROMs, but you'd need to test to be sure.

I vaguely recall some discussion in the past. Maybe the CM12/13 threads?

As to draining, full brightness screen always on, playing video should drain pretty quick. Add wifi and bluetooth for good measure.
[Nook HD, HD+ Android Development] theleagueofstream:
Yeah I haven't had any luck messing with ROMs. I got a response here:

https://xdaforums.com/nook-hd/help/misreporting-battery-t3704597

from someone with a similar issue, but it didn't resolve the battery misreporting.

I feel I've exhausted every option that doesn't involve me trying to open the device and/or replace the battery, but it doesn't seem like the device is made for it.
[Nook HD, HD+ Android Development] ParadoxGBB:
Don't know if this helps, but I've actually replaced my mother in law's Nook HD (Hummingbird) battery and it was fairly straightforward, and I don't normally open up tablets. It was a bit awkward to close it up with everything aligned correctly, but it is doable. To get in, folks suggest you use, of all things, a guitar pick. I used this as a guide:

https://www.youtube.com/watch?time_continue=1&v=lb3l8ZOuMSg

A replacement with tools ran me about $20 on ebay. In my case, you really could tell that the battery was screwed up, it had expanded and was bowing out from the holding container.
[Nook HD, HD+ Android Development] ST Dog:
What battery? Where'd you get it?

How's it performing?

I've never had much luck with 3rd party batteries.
[Nook HD, HD+ Android Development] ParadoxGBB:
As luck would have it I was able to find the original listing in email. I lied, I got it from Amazon: https://www.amazon.com/dp/B00WNEBRDK/ref=cm_cr_ryp_prd_ttl_sol_0

If you have a huge aversion to 3rd party batteries, I do see "original" batteries listed on ebay (from the pictures they seem legit because they have the B&N logo on them). Some claim to be new. You're going to pay a few bucks premium, but it appears that there still is inventory out there. In my case, I was looking for a cheap, hackable upgrade from my acclaim since at the time builds on that were getting pretty slow and I was offered a free one from my mother in law which I knew I could rehabilitate. At the time it didn't hold a charge at all, maybe 30 seconds, tops, so I really didn't have anything to lose.

As for battery performance, I have it plugged in mostly all the time next to my bed and I rarely go on multiday trips with it --- but I suppose I get about 8-10 hours of internet surfing usage on it on very low display brightness, probably about 2-3 days on idle. For the price of the actual device I think it's decent. I've been happy enough that I scored another one for $35 on ebay that I got for my wife a year ago. I figure if I get a few years of usage from them it'd have been worth it. I'm still hoping I'll get lucky and it'll take Oreo one day.
[Nook HD, HD+ Android Development] ST Dog:
Thanks.

It's not a huge aversion. Just burned too many times. There are good ones but can be tough to find. And most of the reviews are useless, I don't care much what it does the day it's installed. I want to know about 2-6 months later.

And I trust the claimed OEM units even less. Usually fakes trying to get a premium price. There are well done counterfeits that are nearly impossible to tell aren't OEM until you see the performance/longevity.