yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] corhsin:
How do you mean 'setting up?' I install the exp. CM and then boot into it. After next it shows the 02 MAC and endlessly moves the status bar. Is there something additional that should be completed? I played with wifi for quite a while before I decided to try it with GApps installed. This is my first time setting up an Android root, although I have done many routers->DD-WRT which is (at the basic level) the same thing.
[Nook HD, HD+ Android Development] lorddunlow:
I had to reboot once after flashing the ROM without Gapps to get WiFi to work. Then rebooted to recovery and flashed Gapps pico. The boot after that didn't seem to ever finish, so I powered off and rebooted. Then after about 15 minutes it booted and has been working wonderfully since.

I have another question for the devs - I'm guessing live wallpaper was removed in the CM 14 ROM for performance, right? Or are they supposed to work and something is wrong with my setup?
[Nook HD, HD+ Android Development] corhsin:
Yes as per my instructions I did reboot after recovery, OS, and GApps when I finally tried it with them. WiFi doesn't ever have a MAC let alone SSIDs listed.
[Nook HD, HD+ Android Development] belfastraven:
First re weird screen rotation: That is not a 'bug". If you run a 3.4 recovery, you will need to use it "upside down" i.e. turn the nook around. For the rom, the boot image animation will be upside down. In an AOSP build, Once you pick up the nook you will get the proper orientation, For cm roms, you need to go to setting, display, rotation, and make sure that 180 degrees is checked. I believe amaces did this to simplify building for two devices, ovation and hummingbird, and not having to maintain more than one set of parts of the display code. I think if you are a normal user and don't flash roms every day, ti shouldn't prove too annoying. I sympathize if this is bother. Right now its makes me dizzy, becuase I am flashing roms sometimes 3 times.day. :)

RE root, if you are running cm root is built in, the "trick" to enabling it is to go to develper options, find root (which will look llike it is enabled), disable it, and then reenable it. You should not flash another root manager. Seemingly, a file that needs to be there doesn't get written, although in developer options you are told that you have root. By disabling and enabling root (for apps, or apps & adb), that file is written and you will have root and will not have perform that action again, unless you wipe data.

If you are using an AOOSP rom, root should be build in also. To manage it you will need phhs superuser app from playstore.

---------- Post added at 03:11 PM ---------- Previous post was at 02:40 PM ----------

Sorry you are still having difficulty. No use weeping over wonky WiFI: if you are running a cm rom, to make sure that you have root. Go to developer options, and under root access, (it willn say it is on) set it to disabled, then immediately set it back to Apps and ADB. That will actually turn on root. For AOSP, it should be on without your doing anything.

While you are in developer options, turn on "terminal".

In the past, sometimes when people were coming from stock the rom the mac address would not be set up properly.

So,

If you have already tried rebooting (just turrnig the nook off and on again, NOT doing anything else,) and are still getting the 02 00 00 00 00 mac address, you can try going to terminal,

entering

su

to give yourself root there,

and running

/system/bin/fix-mac.sh

Which should fix the mac address problem.

I'm sorry, I can't remember which particular rom you are running. Could you remind me?

Keep in mind that the nougat/cm14 or 14.1 roms are "experimental". CM just started nightlies for 14.1 on a few devices.
[Nook HD, HD+ Android Development] corhsin:
The newest of new CM7.1.

insmod: failed to load /system/lib/modules/wl12xx_sdio.ko: Bad address

Failed to load kernel module using command /system/bin/insmod /system/lib/module

Calibration not complete. Removing half-baked nvs

chmod: /rom/devconf/wl1271-nsv.bin: No such file or directory

then back to ovation:/ # prompt.
[Nook HD, HD+ Android Development] belfastraven:
If that is what returned when you ran fix-mac.sh, you should "bug report" or I can do it for you. . [MENTION=4473900]amaces[/MENTION] should see the bug report.

We could try to set you up on an earlier rom and update to this one, but I honestly can't tell you which cm13 rom to use, right now, so it might b e more frustrating than waiting a little while.
[Nook HD, HD+ Android Development] corhsin:
Please do or point me to the correct site. I am willing to try a 13 install if I can get it going. Thank you.
[Nook HD, HD+ Android Development] rtarv321:
For what it's worth, I upgraded from kitkat to cm13 using the Aug 19th file in the Ovation folder. Installed with - 0- problems. I they upgraded to the latest cm in the experimental folder.
[Nook HD, HD+ Android Development] TRS_80:
Thanks! Ya, that's what I did for the screen, I also uncheck 0 degrees and lock screen rotation on. No biggie, it's just that I only noticed a couple of posts mentioned the problem, thought maybe something went wrong with my 3.4M install.

Yes! That fixed root on cm. I think I recall now, having to do that before, either on this device or another. Funny thing is, I was right there a couple of times before to check it, I just never disabled/re-abled. derp Anyways worked right away and I was able to flash TB update.zip in TRWP and everything looks OK.

Seems fluid, wifi / BT are working no problem. No wierdness thus far. Time to play and drain my battery :D Thanks for providing Nougat so quickly amaces!
[Nook HD, HD+ Android Development] belfastraven:
to bug report, go here: http://xdaforums.com/devdb/project/?id=12398#bugReporter

Someone has suggested that moving from kitkat to the latest cm rom in the ovation folder on Box worked. I don't know wehter that means from "stock": or not. You will need a gapps for Marshmallow , if you want gapps for cm13 . It might not be a bad idea to do a factory reset and install just the rom to make sure you have WiFi. If you do, you should be able to install the experimental rom and 7.1 gapps... Sorry this has been such a problem.
[Nook HD, HD+ Android Development] corhsin:
The bug report is filed. I believe this is a workaround? If so, can anyone assist? T. I. A.

Developer Response Mar 20th, 2016
While we moved fixmac insmod to init, calibrator still tries to use it for plt autocalibrate (first time NVS generation). We could stop using calibrator altogether for the MAC address update, but having calibrated NVS per device is probably more important. For now, I've replaced toybox with a prebuilt version where insmod does work with older kernels. This issue only affects people who have never installed one of my CM12.1 or MM ROMs (the actual NVS file lives in /rom, and survives across installs). If this is your case, and don't want to wait till the next builds, you can simply copy https://github.com/airend/android_device_bn_common/raw/mm-13/prebuilt/bin/toybox to /system/bin/toybox (making /system rw/adb remount needed). The proper fix would be to support the more modern module loading, which doesn't break toybox's insmod, but that backporting may, or may not be possible.
[Nook HD, HD+ Android Development] belfastraven:
I think I reported that bug initially for cm-13, but I am not sure the file that fixes it is still at the location specified in [MENTION=4473900]amaces[/MENTION] answer. I will try to locate it for you later if you can't flash the cm-13 rom that was mentioned as working and you hear back from the bug report. The link in the answer is to [MENTION=4473900]amaces[/MENTION] repository on github, but the way. you can look at the repository by going to github.com/airend/device_bn_common/prebuilts/bin -- your will see that there isn't a toybox in that folder now..:) which is why just clicking on the link wouldn't work...
[Nook HD, HD+ Android Development] sasmith-129:
I installed cm_ovation-ota-NDE63X.161109 from experimental along with openGapps pico (2016-11-11) with *no* installation issues. Nice job [MENTION=4473900]amaces[/MENTION] & team!

The biggest issue I've seen is that gesture typing doesn't work for me (AOSP keyboard) - bummer! I haven't tried any other keyboards yet.

Also, I've run across a few apps that won't start, most notably the gapps email client, but there are functional alternatives.

I upgraded to the latest (2016-11-18) openGapps but that made no difference.

Keep up the good work!
[Nook HD, HD+ Android Development] sega dude:
Are the ASOP ROMs rooted? Do I just need to install a superuser app?
[Nook HD, HD+ Android Development] mikeataol:
yes, they have the root binaries installed, but you need the phh superuser app from the play store for it to be functional.

https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en
[Nook HD, HD+ Android Development] ipdev:
There is an alternative manager available for phh's also, PunchUp's Superuser 2.0 Beta 9.

You can grab it from phh's superuser thread.

http://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394/page190

- This is the one I prefer to use if I am running phh's, not saying it's better, just another option. :)
[Nook HD, HD+ Android Development] Lanchon:
this might be interesting to users of this thread:

[Nook HD+] REPIT: enlarge /system and /data partitions without wiping your data

http://xdaforums.com/nook-hd/development/nook-hd-repit-enlarge-data-partitions-t3503615

thanks!
[Nook HD, HD+ Android Development] gascomm:
just got round to installing the latest cm experimental build. installed without issues but the video quality on YouTube, iPlayer, all 4 is very poor. no bluetooth or casting support either... back to trusty 12.1 I guess.
[Nook HD, HD+ Android Development] arh2o:
For Android Nougat, does the AOSP build or the CM build have better performance? I don't really care about features, just maximum speedy performance.
[Nook HD, HD+ Android Development] amaces:
In the latest CM14, I'm attempting to enable 180 degree rotation by default (all others are already permitted). Please report if this still doesn't work on a clean build.

The touchscreen/display/accelerometer configurations are still very different for the two devices. I mainly wanted to drop the abnormal panel orientation patches in frameworks; these three subsystems need to agree on factory panel mounting, and unfortunately ours is a bit odd.

Should be fully fixed in the current builds. The BusyBox insmod hack for the initial auto-calibration process was removed, and the additional kernel support for toybox insmod was fixed. All this would only happen if you never run the calibrator utility successfully.

That's a GApps feature, and it depends on your package installing Google's proprietary library (and AOSP keyboard app finding & loading it); Google keyboard works out of the box.
[Nook HD, HD+ Android Development] sasmith-129:
Thanks [MENTION=4473900]amaces[/MENTION], yes, the Google keyboard was the first alternative I tried and it works fine.

Unrelated, I dirty flashed the 11/23 experimental build and, after reboot, it complained about not having enough storage even though I have plenty. It doesn't seem to make a difference. Thanks!
[Nook HD, HD+ Android Development] belfastraven:
It's probably talking about storage space in the system partition. Look at "memory" in settings, rather than "storage". If it is actually reporting correctly, you might want to get rid of some wallpapers or any apps you don't use.
[Nook HD, HD+ Android Development] amaces:
It says system space, so data or SD card doesn't matter; look at df -h /system. Are you installing anything more than pico GApps? If this is CM14, it may be one of their recent “innovations”.
[Nook HD, HD+ Android Development] belfastraven:
I can confirm it is coming from cm14-- frameworks/base/services/core/java/com/adnroid/.server/storage/DeviceStorageMonitorService.java, where you will also find lots of other "helpful" checks and messages.

the string itself is listerd in

frameworks/base/core/res/res/values/.strings.xml

I'm not sure its working the way it is intended to though, since it seems that if that message comes up, the installer is supposed to come up so that you can uninstall things. ALso, it looks like the amount of storage should be logged to the event log, but they are also talking about memory--I'm confused.... When I saw the message in the previous post, I thought they were talking about space taken up by the running system --very confused i AM..................
[Nook HD, HD+ Android Development] corhsin:
[MENTION=5672278]belfastraven[/MENTION] or anyone else. Would you mind translating this? I hadn't heard of the calibrator utility. I appreciate the assistance.
[Nook HD, HD+ Android Development] amaces:
Basically, Wi-Fi should work now, even if you haven't installed any of the previous unofficial builds (since about CM12.1).
[Nook HD, HD+ Android Development] belfastraven:
[

I'll try: :) Probably you already know what Busybox is, bvut for philosophical/business reasons Android builds are switching to use Toybox. From the web:

"BusyBox is software that provides several stripped-down Unix tools in a single executable file. It runs in a variety of POSIX environments such as Linux, Android, and FreeBSD, although many of the tools it provides are designed to work with interfaces provided by the Linux kernel."

"Toybox is an implementation of some Linux command line utilities. ... The Toybox project was started in 2006, and became a BSD-licensed BusyBox alternative. Toybox is included with Android 6.0 "Marshmallow" and all later Android versions, and is also available for installation on certain other operating systems."

There have beren some problems for our devices in the switch:

The WiFi drivers are being built as seperate kernel modules, hence the need for the insmod command which had problems, initially. So at times various commands have moved from using busybox to toybox or module insertion has occured some other way.

If you were coming from stock, I am pretty sure that calibration in the way its being performed here had never been done, so the files that the calibrator was looking for didn't exist(or didn't exisat where they were expected to be). see here for a general description (not for our devices specifically).

http://linuxwireless.org/en/users/Drivers/wl12xx/calibrator/#wl12xx_Calibration

According to [MENTION=4473900]amaces[/MENTION], if I understand correctly, if you use one of the new builds in experimental, you should get wifi back.

I don't know whether this helped at all...
[Nook HD, HD+ Android Development] corhsin:
Respectfully I find that difficult to understand, or disagree, going from stock to Nov9 wifi will not function. If you already understand this, why not add, "Upgrading from stock requires a version prior to 14 to be installed for wifi to function correctly" to the OP?

I appreciate the translation. I was only one build back from Nov23. My guess is he is mistaken. I will try it and see what happens. Thank you.
[Nook HD, HD+ Android Development] brenyoka:
I am on a few month old MM build on Ovation and now I plan to upgrade to a new build. I noticed there is 1 MM and 1 Nougat build in the experimental folder, both dated as 11/23/2016. I noticed the MM actually came a bit after the Nougat. Does this mean the MM is recommended over the Nougat? But, if the Nougat is just as good and works reasonably well, which OpenGapps version should I flash: 7.0 or 7.1? Thanks a lot guys.
[Nook HD, HD+ Android Development] amaces:
Did you actually test the new build when I said it's fixed? You went and installed an experimental build; it's probably better to stick to what exists in the respective device folders, or stock if nothing else works.

As a side note, nobody knows what Goldilocks-level explanation is appropriate in each case… As per OP, these are and will likely remain development builds, despite all the efforts to push these devices forward.
[Nook HD, HD+ Android Development] sasmith-129:
FWIW, after a clean install of the ovation 11/23 experimental build, there were 262M free in /system. After installing Open Gapps PICO 7.1 (2016-11-24), there were only 118M free in /system. Also, of you press the notification, it presents a pop-up to remove apps and/or clean cache (IIRC).
[Nook HD, HD+ Android Development] belfastraven:
Well at least it is operating the way it is supposed to. Interestingly, I just built using [MENTION=4473900]amaces[/MENTION] manifest for cm-14 ( hummingbird) but with a different kernel and I am not getting the message, even though I have less space available in system than you do, at the moment.

Once again (I know I sound like a broken record here) , if you want more free space in system, you can use a .gapps-config file to remove not only gapps apps (e.g. do you really need exchange services which are installed even with pico gappsl) but also other system apps. If you look at all of the apps (i.e. when you go to settings, apps, and to the menu at that upper right corner, you can enable the display of system apps)you might see some you want to disable. I'm not sure those would appear in the "deinstallation" popup. This is only a short term fix, I know.

I'm curious about why I am not getting the message..
[Nook HD, HD+ Android Development] ShapeShifter499:
Ok so I cleared everything and clean installed the latest 11/26/16 CM build for Hummingbird and I cannot get the playstore to work, any ideas? I did use the 7.1 version of OpenGapps. The playstore will hang on a white screen and never load anything and I know my tablet gets internet as the browser can load the Google website.

---------- Post added at 09:07 AM ---------- Previous post was at 08:37 AM ----------

Update, clearing cache, reflashing the 7.1 opengapps package, then clearing the cache again seemed to get the playstore working.

---------- Post added at 09:33 AM ---------- Previous post was at 09:07 AM ----------

I have another issue. On my other Cyanogenmod devices the screen will dim then lock on idle but with these roms on Hummingbird it doesn't dim properly. Is this a bug? It's problem because there is a second or two where the device is dark but still unlocked.
[Nook HD, HD+ Android Development] sasmith-129:
[MENTION=4473900]amaces[/MENTION] - I noticed TWRP-3.0.2 is no longer in experimental and only 3.0.1 is under ovation.

I upgraded to 3.0.2 before switching to your CM Nougat builds.

Do you recommend ovation users stick with 3.0.1? Thanks.
[Nook HD, HD+ Android Development] ShapeShifter499:
[MENTION=4473900]amaces[/MENTION] I'm getting a "out of space" error trying to install F-Droid on the 11-26-16 build for Hummingbird. Any ideas? As you can see from the screenshot I uploaded to imgur, I have plenty of space.

http://imgur.com/a/dLgl4
[Nook HD, HD+ Android Development] Zippy Dufus:
Yup ... earlier in this thread, a couple 3.0.2 TWRP users got stuck in bootloops cycling back to TWRP. I helped a friend having the same issue with 3.0.2 on his Google "mako" Nexus 4 and had to install CWM Recovery to fix it. I then put TWRP 3.0.1 on it and it has been fine ever since. I am happily using 3.0.1 to flash my NookHD+ with Nougat.
[Nook HD, HD+ Android Development] sasmith-129:
I did not get the low space message with the 11-26 build even though /system was well under 150M.

Regardless, I reinstalled 11-26 with a stripped down .gapps-config and free space in /system was well over 160M.

Thanks!
[Nook HD, HD+ Android Development] belfastraven:
Could you tell me which build cm or aosp? And exactly what had you done before this happened? I just installed the 11/26 cm hummingbird build (dirty flashed), rebooted, installed the latest (11/25 as of the time I am writing) nano gapps (but removed some things with a .gapps-config file) rebooterd and then installed fdroid with no problem. I'm wondering if some space does not get cleared properly immediately after a rom installation... , but does after a reboot...
[Nook HD, HD+ Android Development] ShapeShifter499:
It's only a issue if you have FDroid installed to /system and then try to apply a update over it. I'm not sure why but when I removed FDroid from /system I could install it like a normal app. Doing that however removes the permission to allow FDroid to install apps without "unknown sources" toggled on.

EDIT: I had clean flashed CM 14 11/26/16 build onto my HD Hummingbird after clearing all the partitions (data, system, cache).
[Nook HD, HD+ Android Development] belfastraven:
Hmm.. I saw from their doc that they said that the best way to install the extension was from from a zip file--however the link did not lead to any such file. I thought maybe they were fixing something for Nougat... How did you get it back onto system after you had wiped system?
[Nook HD, HD+ Android Development] ShapeShifter499:
Their "privileged extension" does not work (yet?) for 5.1+ I just checked it recently. I got FDroid onto my system by moving the apk file to a folder specifically for FDroid under /system/priv-app/FDroid/ and moving it into that folder. chmod 755 on the folder and 644 on the apk. Doing this allows FDroid to install apps without "unknown sources" being toggled on, works on my other devices running CM 13, like my Moto X Pure. I also added a script to /system/addon.d so updates wouldn't remove FDroid.
[Nook HD, HD+ Android Development] lentm:
Does anyone have glitches when the screen rotates on CM13 11/25 build?

Never saw it on August build. hmm.
[Nook HD, HD+ Android Development] ShapeShifter499:
[MENTION=1389822]lentm[/MENTION] The 11/25 build is a update to CM 14. The rotation change appears to be down to what was easier to code and build for [MENTION=4473900]amaces[/MENTION]. It only affects the bootlogo, to fix after boot go to Settings > Display > Rotation settings and make sure "rotate lock screen" is toggled on and make sure '180 degrees" is checked.
[Nook HD, HD+ Android Development] lentm:
I thought I was talking about the graphic glitches, not the rotation issue.
[Nook HD, HD+ Android Development] ShapeShifter499:
OHHH uh.. so not related to rotation, sorry about that. I haven't seen any screen tearing or artifacts or the like. But I have had issues where I see "burn-in" of images that have been on the screen for a while but those clear up as I use the tablet.
[Nook HD, HD+ Android Development] acr123:
CM ovation 11/25 & 11/26

Both of these are no longer in the experimental folder. I notice there is ~ 18 MB size difference. Does anyone know what is the differences in these 2 versions.

thanks,

Al
[Nook HD, HD+ Android Development] belfastraven:
They are both now in the device (ovation in your case) folder. note that once has ota-M in the name, the other ota-N. M is a marshmallow build and N is a Nougat build, I believe.
[Nook HD, HD+ Android Development] acr123:
thanks for the info. That makes perfect sense - the M & N differences. Interesting that the N ( Nougat ) build is smaller.

Al
[Nook HD, HD+ Android Development] robak1965:
On hummingbird, it does not Only affect the boot logo. There are certain apps (like busybox), that when started flip the display upsidedown no matter what the toggles are set to. Setting the toggles does not fix the issue, but if you are like me, and want the nook button on the bottom when using, it's a minor nuisance. I can't speak for ovation. Also, the hummingbird recoveries here start up upsidedown, so i have gone to the twrp site latest build for hummingbird which have the correct orientation.
[Nook HD, HD+ Android Development] HMSVictorious:
It's there a recommended way to go from M to N? I'm running both a HD and a HD+ so would love to not have to set them up from scratch.

Many Thanks