yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] digixmax:
See https://xdaforums.com/showpost.php?p=71372105&postcount=1719.
[Nook HD, HD+ Android Development] e.mote:
>Following the update to the LN newest build ovation-ota-NOF26W.170226 my HD+ started to have intermittent but frequent problem connecting to WiFi

I recall having this problem with the Jan build, but not the Feb build. It is more sluggish coming out of sleep. Display rotation takes about half a minute to work. It does respond faster once you start tapping on some apps.

I just ran across a different bug with the Feb build. Hangouts SMS crashes when you start typing; dialing VoIP w/ GV works.

These were on clean installs, and are the same on 3 Nooks (they have identical software config, based on the same backup.)
[Nook HD, HD+ Android Development] ieatabiscuit:
I recently switched to the latest lnos myself. I like it better than my usual AOSP preference even! I've seen the issue with wifi connectivity, but not on my own router. I think that's something that can be worked out with router settings, though it can be annoying. I would look specifically into what channel you broadcast on in relation to other networks near you. As for being sluggish, mine's running great, not a problem in the world. Hangouts may be acting up because Hangouts is in a constant state of change though. I gave up on that app a year ago when the word of them dropping SMS support first appeared, so I can't really vouch for that one. I DID notice that the more robust your GApps is, the slower my HD+ ran. I've got mine down to just barely enough to get the play store, and used something like Titanium Backup to freeze everything that I didn't want/use to free up resources for the things that I did use. While I'm not sure if it's needed or not, I also disable anything related to telephone, or mobile data with no ill effects. Maybe [MENTION=5672278]belfastraven[/MENTION], or [MENTION=4473900]amaces[/MENTION] can elaborate there.
[Nook HD, HD+ Android Development] twiztid_:
I've run into Wifi issues before, and I would personally recommend this app to help solving channel issues. One of my neighbors has an almost overpowering Wifi signal and will cause interference if we're on the same channel. And keep in mind that your microwave could cause troubles with dropping too, for us Channel 6 seems to be the same frequency as the microwave, so if Wifi is on Ch6 it will drop signal when the microwave is on.

I had a similar issue with the first LNOS build, it worked fine but would be fairly sluggish after waking particularly while wifi was re-connecting, gmail was fetching mail, and AdAway was looking for updates all at the same time. After installing the second build over the first, all the problems went away.

Maybe try doing a re-install ontop of the current build if it's giving you problems, not sure why it would work but I don't see how it could really hurt either. Overall, I'd say my Nook is running better than it ever has.
[Nook HD, HD+ Android Development] ieatabiscuit:
That is the very same app I use actually. My router is even able to switch itself among a small range of channels its self once set up for it too. Getting it juuuuust right will also help with your range as well.
[Nook HD, HD+ Android Development] digixmax:
Having now lived with the WiFi slow connect issue for about a month, I have found that, after manually turning on WiFi following the device coming out of sleep, if I put the Nook back to sleep and quickly turn it back on then WiFi would connect right up. It's a bit of hassle, especially there is now one extra gesture to bring up lock-screen pattern-lock.
[Nook HD, HD+ Android Development] CalculonsTalent:
I know this is a crazy request but is anyone working on SD-only (noEMMC) builds for these versions? I recently suffered an emmc failure and there are a bunch of us out there that would greatly appreciate it.

Thanks!
[Nook HD, HD+ Android Development] nsfgp:
Thanks Amaces and all for these great ROM and tips, etc.

Just want to report that for one main TV streaming app I use. Somehow it thinks Mock location is turned on and won't run => this is the same for all the AOSP/LN/CM 14.1 builds I have tried for my HD+. 13.0 builds works fine.

I also use Amaces's builds on my Nook Tablet (Acclaim) ... and the same app works fine on 14.1 builds.

Am I the only one getting this??

Thanks!!
[Nook HD, HD+ Android Development] drmarble:
New aosp experimental builds: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3480156918

Looks like another stab at updated wifi drivers and a 3.4 kernel. Not certain, though.

Actually looks like 3.0.101.
[Nook HD, HD+ Android Development] ntice:
I attempted to install lnos_ovation-ota-NOF26W.170226.zip using twrp-3.0.1-0, but when booting it just shows the LineageOS line/circle animation forever (at least 30 minutes before I gave up).

The install did print a couple of "unknown command" error messages, although it still completed. Is that normal or a bad sign? Should I have used CWM instead?

Thanks!
[Nook HD, HD+ Android Development] neutronjeff:
Twrp works fine. Did you use the twrp amaces posted?
[Nook HD, HD+ Android Development] ntice:
Yes, I used sdcard-reco-ovation.img
[Nook HD, HD+ Android Development] digixmax:
Was your install a dirty-flash upgrade from a previous version of LN, or was it a clean new install coming from CM or from stock ROM?

If upgrade from previous version of LN, beware that unlike previous versions of CM in which the boot animation stops running after the system boot completes and the apps' "re-optimization" begins, the boot animation now runs until the whole system + app update process is completed. So, if you have a lot of apps installed, don't panic as the first reboot after the upgrade flash will take a long, long time.
[Nook HD, HD+ Android Development] ntice:
Clean install from stock.
[Nook HD, HD+ Android Development] NE0HP:
To do clean install.

If you're able to boot your device in to TWRP then,

Download new official TWRP 3.1.0-0 from this link https://dl.twrp.me/ovation/ and put it in to SD card. Flash this new TWRP over your existing TWRP as an internal recovery.

Reboot your device to new TWRP

In TWRP, Go to wipe --> Advance wipe ---> select everything except Extrnal SD card --> wipe. Go back to Main menu of TWRP, Select Install, Select ROM, Swipe to Flash ROM, Select Gapps, swipe to flash Gapps, wipe dalvik/cache and reboot the device.

And Be patience first boot will take time! That's it.
[Nook HD, HD+ Android Development] ntice:
That worked! Thanks! This time there were no error messages during the OS install (and the install took longer to complete, which was encouraging).

When booting after install, it took 5 minutes to get past the line/circle animation.

By the way, I had a really hard time entering TWRP. First, I didn't know what button to use (I figured the "n" key - nope, it's a volume key). And then, it only worked 10% of the time. It seemed to be timing critical - you couldn't press it too soon or too late. Or maybe my volume key is busted. Whatever, it was frustrating.

Thanks again!

---------- Post added at 02:44 AM ---------- Previous post was at 02:43 AM ----------

Question about these releases: My tablet has the Samsung eMMC with the buggy TRIM. That issue was addressed in the kernel a long time ago, right? There's no risk of bricking my device?

Alternatively, is there an android app that will disable TRIM?
[Nook HD, HD+ Android Development] belfastraven:
I have not had the problem becuase I don't do much streaming, but I have seen that many other people on various devices have, with several different apps. (Some were trying to stream NFL games and were REALLY UPSET)

There used to be the ability in developer apps to enable/disable mock locations. Now, apparently, if the mock location setting has ever been enabled (It was by default for a while on the HD's) , you are given only the ability to set the application. If if it is set to nothing or none, some badly coded apps don't recognize the fact that it is not being used.

There used to be a build.prop setting for mock locations being off.

ro.allow.mock.location=0

that doesn't appearanymore on my nook HD. I just added it to my build.prop. It doesn't cause any problems for me, but I have no way of checking if it fixes your issue.

I wonder whether that's what the app is checking. Which app is it? Have you checked to see if any one else is having trouble with it; looking at playstore or other reviews for example. I am puzzled that it works on the tablet builds and not on the HD builds. On your tablet, in developer options, what do you see about mock locations? Is it the same as what you see on your HD?
[Nook HD, HD+ Android Development] aa84:
error e1001 unable to format cache

I tried to test aosp_hummingbird-ota-N2G47J.170404.zip, but I kept getting error e1001 unable to format cache. Updated twrp to 3.1.0 https://dl.twrp.me/hummingbird/ and the error went away, but it doesnt boot - stuck at cyanaboot logo, no adb. Went back down to 3.20 build, small wifi issue but after toggling it goes away.
[Nook HD, HD+ Android Development] nsfgp:
Bingo. I think I found what might be wrong.

In default.prop -> ro.allow.mock.location=1

Now why would it came in like that?? The developer intended to do that may be??

I tried added the line with value 0 to /system/build.prop but does not work.

Is there an easy way to change it to 0 in default.prop?? I believe the boot partition needs to be changed .... no idea how to do that.

If Ameacs is listening .... can you please make mock location off in your next version if possible??

I am using the LNOS_170226 build.

Thanks!!!!
[Nook HD, HD+ Android Development] belfastraven:
First--you do need to recognize that the problem is probably with your app: The property "allow mock location" is actually "deprecated" and probably the app developer hasn't caught up with the code yet. I just made and installed a build with it set as 0 in the default prop ; the system still let me install and use a gps emulator, so it doesn't seem to actually do anything, but perhaps that is what your app is checking. (I believe that the app should now be checking for mock locations set to nothing or none, rather then checking for the allow_mock_location property)

I just wanted to make sure that on your nook tablet, where your app is working, you see the ro.allow_mock_location=0 in the /default.prop file, so we are pretty sure that is the problem. If that is the case, I can build a rom for you to test.
[Nook HD, HD+ Android Development] nsfgp:
Thanks a lot and I agree it is mostly due to the app. It is not the best app to begin with. It is the KTSF app by Syncback inc. Almost unusable in earlier versions. It is an app for a local TV channel.

On my Acclaim that is working ok with the App ... I am currently running drmarble's new LN rom (https://xdaforums.com/showpost.php?p=71741945&postcount=57).

And yes I just checked on it ... in default.prop the ro.allow.mock.location is there and set to 0.

So it is likely that crappy app is checking for that entries.

Is there a way I can do a temporary override to make it 0 again on my Ovation to test if it will fix the issue for now with the app.

Thanks for helping.
[Nook HD, HD+ Android Development] belfastraven:
If you have root, you should be able to edit the /default.prop file. The nook won't currently keep the edited setting across reboots, but you might be able to test your app right after you do it. Let us know.
[Nook HD, HD+ Android Development] nsfgp:
Changed /default.prop entry from 1 to 0. Fire up the app but no go. Stupid app still saying mock location is turned on.

In Dev. Option the Mock location App is showing nothing.

No big deal. At least I have the Acclaim to use for now until they fix that app.

Thanks again.
[Nook HD, HD+ Android Development] belfastraven:
Yes, since you gave me the name of the app, I tried it too (using the rom I built with default.prop=0), figuring that if it had worked it would tell me I was in the wrong location, but I got the same message. I think using the Acclaim build that works is a fine idea :) Who knows, with all the complaints about there code in the reviews, we may be seeing a bad error message with the real problem being something else entirely :)
[Nook HD, HD+ Android Development] nsfgp:
Thanks for trying!!! Appreciate the help and tips.

That KTSF app is crap I know. Hope they fix it soon.
[Nook HD, HD+ Android Development] johnnyspork:
Ovation Marshmallow Lineage OTG Issue

Hey, seems like VeryGreen's baked-in host switcher works fine to enable USB OTG (host mode), but the only device I want to use isn't compatible! It's a GameStop branded generic Xbox 360 controller made by "Perfomance Designed Products," aka PDP. It worked fine on the latest Pacman ROM (Kitkat), but I need to be at Lollipop or above for some of my apps. The error I get when checking it out in TPUSBMount is "device v0e6f p0401 is not supported." The idVendor is 0e6f and the idProduct is 0401. If anyone could point me to a way to fix this, I'd certainly appreciate it. Is it possible it just needs a keymapper file added in system/usr/keylayout? Thanks for everyone's hard work on these builds, and I look forward to finding a workable solution. If there's a way I can get my own keymappings manually and make a .kl file, I'd be open to doing that and sharing my results here so others can use them or they can be included in future builds. I just need someone to point me in the right direction, since I'm not sure if it's an issue with the controller config, a low-level driver, or the key layout.
[Nook HD, HD+ Android Development] mmnspeed:
Started using greenify with the lineage os builds by amaces.Trust me,the tablet performance is amazing after this.Turns out I may have had a lot going on in the background on a device with just 1Gb ram.
[Nook HD, HD+ Android Development] sacto7:
Installed MM a couple of times. Problem with gapps stock in not enough memory; tried mini & still not enough memory. Used the computer to check "storage" & deleted some stuff like a version of CM 11 & some other stuff.

Tried pico & then got "setup problem" & cannot get MM running as could not bypass the "setup problem".

Popped the sdcard out & put MM & mini gapps & reinstalled MM but mini gapps had "not enough memory", error 70. BUT did a reboot & got up & running with Google access which was the main thing. Guess gapps got partially installed.

Now, the TWRP had a "wipe" selection which I did; but should I have done an advanced wipe? I looked like I did enough wipe........

BTW, it may be just a MM problem with using MTP as it looks like it has to be "reset" when one had powered off as the MTP doesn't work when powering on again. The couple of things being used on my Ovation looks to be running quicker.
[Nook HD, HD+ Android Development] belfastraven:
Build questions

Using [MENTION=4473900]amaces[/MENTION] repository ( with -b cm13), trying for a cm13 build.

if I breakfast or lunch, I get "dependencies file not found, bailing out" It looks to me like the bn hummingbird and common code is in the vendor directory: Is there something else I need to do so that it is found? I tried to build anyway using "lunch cm_hummingbird-debug", then mka, because I wasn't sure that the error message was "valid" ;). The build stopped with the following errors:

gcc: error: unrecognized command line option ‘-fdiagnostics-color’

make[3]: *** [scripts/basic/fixdep] Error 1

make[2]: *** [scripts_basic] Error 2

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/home/mlp/cmbuild/kernel/bn/omap'

make: *** [/home/mlp/cmbuild/out/target/product/hummingbird/obj/KERNEL_OBJ/usr] Error 2

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

host C++: libc++_static_32 <= external/libcxx/src/future.cpp

make: *** wait: No child processes. Stop.

#### make failed to build some targets (15:41 (mm:ss)) ####

the other warning messages I am getting seem to all be about integer/unsigned integer comparisons..

Building on Ubuntu 14.04

Any help would be appreciated...I have tried to look at all the build messages on this thread as well as elsewhere on the internet am am now very very confused, as this type of environment is new for me.

Building on Ubuntu 14.04....
[Nook HD, HD+ Android Development] prsa01:
Amazed at how usable this is already!

I stayed on 12.1 until things seemed to have stabalized somewhat. Did the process others have used:

Reset device

Full wipe

Install MM (CM)

Install open gapps (in my case nano)

Install supersu

Device walked thru setup fine and I was able to install my apps. Most things work close to as well as 12.1. Amazing that it is this far so quickly. I occasionally notice some slowdowns that seem memory management related but a restart takes care of that. It even took care of a nagging app/keyboard issue I still had in 12.1 but had learned to work around.

Much thanks for all of your work!
[Nook HD, HD+ Android Development] amaces:
Not enough “memory” refers to insufficient storage space in the /system partition. CM is much larger than AOSP, and not even sure mini GApps work with the latter. The nano package is probably the sweet spot given that it contains support for all Google features that you can install afterwards in /data, and it should still fit into the CM13 /system.

Yes, you did for the first install, but once you boot into the new system, /data becomes dirty. OpenGApps require a clean install the first time, and every time you have to fix things.

Whatever you did, you'll have to redo it properly, on a clean install, with the appropriate GApps package (nano or pico). When everything installs properly, there should be no setup or permission issues.

Not aware of MTP issues, but I'm also not using it often. Anyone who does, and encountered these bugs, should chime in.

You mean -b cm-13, right? That unrecognized option (-fdiagnostics-color) would be a problem with GCC 4.8, but we use 4.9 for everything (including kernel). Can you try re-syncing and make sure there are no errors? I checked the CM13 manifest, and it looks fine, but maybe I'm missing something.

P.S. The warning about bailing out during breakfast/brunch happens because I took out cm.dependencies; our upstream device trees stop at cm-12.1, and we don't need a local manifest since I include everything in the main one.

There will be a million warnings, so no worries about those.
[Nook HD, HD+ Android Development] amaces:
Actually, it dawned on me that the host compiler could also be the culprit. Sure enough, looking at the log more carefully, the error happens at a host binary target, which means that CM13 expects GCC 4.9 or higher on the Ubuntu host.

Usually, you worry about the cross-compilation toolchain (i.e., the one generating ARM binaries that actually end up on the tablet). The host stuff is usually easy to keep updated, but in this case, Ubuntu LTS must have decided to stick with the more stable toolchain (at the time). What does gcc -v say?

If it's indeed 4.8, you can either update the host GCC, or use a more modern distribution to make the colorized output in CM happy. Still, I'm a bit confused since I thought CM12 would detect and disable this feature with GCC 4.8, but maybe CM13 gave up on that.
[Nook HD, HD+ Android Development] belfastraven:
I too came to the conclusion that the problem was here(my brain hurst..)-when I first got the message I tried to update GCC but was told I had the latest version. 4.8 does come with Ubuntu 14.04--I looked around on-line and found a way to install and use alternate versions should they be required. I now have 4.9 (and 4.9 GCC ++) installed successfully built. I used

lunch cm_hummingbird-userdebug

then make bacon -j16

Second builds(after make installclean) only take about 5 minutes, initial builds take about 1.3 hours, I think.

I ran with the cover off of the machine, just in case.

I'll probably make clean, repo sync etc. tomorrow, and then build and install the rom. Thanks for your help.

I haven't installed on nook yet. That will be tomorrow's project:)
[Nook HD, HD+ Android Development] belfastraven:
Build Success and successful installation of rom

I built, using [MENTION=4473900]amaces[/MENTION] repository with no local changes, and successfully installed hummingbird this morning. Soooo happy!. BTW, On my system a clean "make" with -J16 takes about 50 minutes. I have Ubuntu 14.04 installed on an external SSD (256)connected via USB3., Haswell 17-4770s, 16G memory.

Re "doze". With the 12/13 rom, over 5 days, the nook HD was "deep sleeping" 69% of the time. I think that may have been because it is syncing various apps even when I am not using it. Except when I was updating the rom, it ran cool, too, about 24.5 degrees C.

I'll see what things look like after letting this rom sit for a few hours. Thanks again, [MENTION=4473900]amaces[/MENTION].
[Nook HD, HD+ Android Development] amaces:
Regarding Ubuntu, you might as well use 15.10, since most of it will become the next 16.04 LTS, and has much newer libraries and toolchain.

Glad everything was straightforward; you're your own man now ;) Also, your setup is almost an order of magnitude faster than mine; I can't help feel a bit envious, since my clobbered CM builds can take up to eight hours. Eh, it's OK as long as I don't break things before leaving stuff to build overnight.

I think we solved the overheating issues for now, and even if hummingbird is overclocked, it'll finish tasks quickly then ramp down to 396 MHz.
[Nook HD, HD+ Android Development] belfastraven:
OK, my New Years project willl be to update my Linux distribution ...

To make up for my speedy build ability, we suffer from pretty mediocre download speeds here, even though we have the fastest speed available to us, so it takes as long, or longer, to do a repo sync after an init as it does to build:).

I was just indicating the times of my build with my equipment so that others who might want to try might have some idea how long it would take on their own setups. I set up the build system on an external drive so that I could attempt to build on my spouses better ventilated and faster machine .

One thing that I noticed after installing my build; I can no longer change permissions of files on the internal or external sdcards--this must be some kind of policy change in cm.

I was going to try to build again tomorrow. I am totally NOT my own "man" --if I were not using your repository I couldn't build anything, I am positive. This way I get to look at source code and get some idea of how things are put together. I often feel like I am playing "adventure" --"You are in a twisty maze of passages, all alike" , which was my first computer game ;)
[Nook HD, HD+ Android Development] js290:
cm13.0-20151213-UNOFFICIAL-ovation seems to drop wifi after about 30 minutes of being connected. I'm attaching logcat and bugreport.
[Nook HD, HD+ Android Development] belfastraven:
build issues on ubuntu 5.10

[MENTION=4473900]amaces[/MENTION], build stops with the following message:

make: *** No rule to make target .../android/system/out/target/product/hummingbird/obj/STATIC_LIBRARIES/liblz4-static_intermediates/export_includes', needed by .../android/system/out/target/product/hummingbird/obj/EXECUTABLES/updater_intermediates/import_includes'. Stop.

web research seems to show this as a problem with the linkage of liblz and other static libraries and suggests a patch --

http://xdaforums.com/galaxy-alpha/orig-development/sources-cyanogenmod-12-0-t3053173/page8

which I probably applied in the wrong place since it didn't help.:(

Any ideas?
[Nook HD, HD+ Android Development] amaces:
It's probably due to TWRP; the MM branch is supposed to compile on CM12 as well, and some leftover dependencies remain. Anyway, I pushed a fix, so repo sync bootable/recovery-twrp and re-build (no need to re-sync everything).