yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] amaces:
Yup, TWRP has brightness controls under Settings, and that way you can check that your panel is still responding properly.
[Nook HD, HD+ Android Development] js290:
Yeah, I think the acclaim maintainer rolled his own CM recovery with f2fs support. I've noticed on kfhd jem and ovation, only /data supports f2fs. When I change /cache to f2fs, CM will not boot; just sits there with the logo flashing.

Yeah, it's a mixed bag. Dlx was horribly unreliable. Evita and d2att always worked. I'm a bit hesitant to even flash TWRP 2.8.7.0 for my daily driver dlx. May be worth doing if the new nightlies also support f2fs.
[Nook HD, HD+ Android Development] prsa01:
brightness control works fine in twrp. I'm thinking i should revert to stock and move forward again. Let me know if there are other ideas.

Thanks
[Nook HD, HD+ Android Development] mhunt13:
I'm good now on 0615. Just checked /system space with TB, it says: System rom 693MB (220MB free).

I never checked system space while on 0622, behavior too erratic.

Thanks for all your hard work, and for helping all your 'followers' here!
[Nook HD, HD+ Android Development] amaces:
Noticed how? Had you followed the evolution of this ROM, or looked through my device-specific repos, you'd know that F2FS /cache (using it right now) has been supported starting with the very first CM12.1 builds. Otherwise, yes, if you install a ROM without the proper F2FS /cache support in fstab, it'll just sit at the boot animation forever.

No one says you should flash anything; the previous TWRP 2.8.5 & 2.8.6 recoveries work perfectly well for flashing ROMs. If you have /data & /cache already F2FS formatted, I think you might even be able to use verygreen's external SD CWM recovery. Again, you're mixing issues, and extrapolate from other device bugs before understanding why they happen. You have to wonder why does the same TWRP codebase have reliability issues on some platforms, but not on others… People submit ports to the few TWRP developers in the form of kernel and device trees, and these are used with the automated build system for the official recovery images. If active TWRP support disappears for a device (e.g., dev flakes out, or loses interest), the automated builds may continue on top of deprecated kernel branches, some initially meant for ICS/JB/KK.

We do not have an official TWRP recovery, and you can bet that our changes happen in tandem across the repos relevant to us. Hopefully you won't take this the wrong way, but if you're unsure about something, it's better to ask a simple specific question, rather than make a general claim. Other people looking for information might become even more confused when they stumble upon absolute statements…

Stock is perfectly fine, although if brightness control is your only reason, understanding why you're the only one having this issue is probably important. If your partitions are healthy, I cannot imagine that a full wipe won't fix it (stock would imply full wipe as well). Are you sure that you wiped /data, /cache, and Dalvik, plus /system before installing everything from scratch?

That all looks good; hopefully, your issues will disappear with the next builds.
[Nook HD, HD+ Android Development] twiztid_:
Hey [MENTION=4473900]amaces[/MENTION], do you recall a while back I had an issue with the browser loading the first page on load? net::ERR_NETWORK_CHANGED problem

After the clean install of 0622 it popped back up again, so I did some digging. Turns out its an issue with IPv6 in Lollipop (both 5.0 and 5.1), and disabling it is a workaround. Apparently setting a static IP disables IPv6, or possibly more accurately uses only IPv4, for the connection, which i ended up using and is why my issue went away shortly after I posted my problem.

I have no clue if you can do anything to fix it, but I figured I'd let you know about the workaround.
[Nook HD, HD+ Android Development] prsa01:
quote: originally posted by amaces

Stock is perfectly fine, although if brightness control is your only reason, understanding why you're the only one having this issue is probably important. If your partitions are healthy, I cannot imagine that a full wipe won't fix it (stock would imply full wipe as well). Are you sure that you wiped /data, /cache, and Dalvik, plus /system before installing everything from scratch?

Only reason i am considering going back to stock temporarilyis to try to reset whatever suddenly caused this. If i can get brightness working i would then move back to these roms.

I'm pretty sure i am getting a full wipe. The procedure i use, all within twrp:

"Factory reset" wipe

Advanced wipe, selest system and do wipe

(Note, at various times i have also run a repair on system)

Install 6/22 or 6/15 build

Install gapps (the one you provided the link for)

Wipe cache and dalvik

##restore data from backup

Reboot

I'll try the same process without the restore

One final piece of info, don't know if it is related. At some point i converted system to f2fs. I wrongly thought it could be. After having issues i later was going to change it back to ext, twrp already had it listed as ext, don't know if installing the build automatically converts it to ext.
[Nook HD, HD+ Android Development] twiztid_:
[MENTION=4433692]prsa01[/MENTION]: in wipe -> advanced, tick dalvik, data, cache, and system.

All the brightness adjustment options work on all my installs, so it sounds like you got some junk info that's surviving between installs and wipes. Changing the file system of /system, /cache, and /dalvik, and then changing it back, might be a good option if you can't do a full wipe/format, due to needing your user data.

[MENTION=4473900]amaces[/MENTION]: I'm not sure if its the new build, or my nook just being extra dusty, but the touch seems a bit more twitchy. If nothing was changed, just ignore this :p
[Nook HD, HD+ Android Development] amaces:
Thanks for the heads up, although I wouldn't put an equal sign between these issues. Here's what I know:

With a regular Linux (and other UNIX-like distributions), disabling DHCP or setting a static IPv4 address, does not interfere with the IPv6 router advertisements mechanisms, and you get at least a local-link address, if your LAN/routers have IPv6 support (even if WAN is IPv4-only). It's possible that Android does things very differently; look under Settings > About > Status, where all addresses should be listed, and if you see anything beyond your chosen IPv4 address, than your problem lies elsewhere.

From my own experience, when similar error messages happened in the past, I was actually on an IPv4-only network. Since May or so, I turned on full native IPv6 at home, after my ISP upgraded their termination boxes. I do not recall seeing the ERR_NETWORK_CHANGED for a few months, so with or without IPv6, it doesn't seem to have made a difference.

Now, Andrdoid 5.* (and CM12.*) does have issues with IPv6, as indicated by countless reports (such as this one), but they seem of a different nature, and I've been lucky enough to avoid them in my use cases. These kind of insidious bugs in the network stack, I'm more than happy to let AOSP and CM wrestle with ;)

Well, that's your problem… We had already established that your user settings in /data are broken or corrupted, so restoring them after all that clean install work yields the same behavior, unsurprisingly; there was no point delving into your mention of that accessibility service error, but clearly this is a purely software issue. You've already tested that the brightness control interface works properly in recovery, which is just another Android distribution, same as stock, just not broken like your current configuration in /data. F2FS has nothing to do with any of this.

Can you describe what kind of twitchy (e.g., phantom touches, less accuracy)? Also, HD+, right, and is it something specific to the 06/22 build?
[Nook HD, HD+ Android Development] twiztid_:
it shows an IPv6 address. But setting a manual address has eliminated the problem (though, the amazon app store has a similar issue, but that could just be the latest app update).

My ISP does not support ipv6, if that makes a difference. Not sure about my router settings but I haven't touched anything ipv6 related there. I'll poke around to serif disabling it there will also fix the issue.

An example would be when trying to long press a word on a webpage, instead of highlighting, the page jumps a bit and it takes a few tries yo get it to highlight.

This isnt specific to this build, it pops up every now and then, seemingly when I update, but that could just be me being more observant.

Sometimes I have touch issues and I can fix them by turning off the screen and wiping a cloth (or my hand lol), but this is a different prob all together.
[Nook HD, HD+ Android Development] windoge89:
[MENTION=4473900]amaces[/MENTION] thanks for your great work. Running the 6/22 build with no issues.
[Nook HD, HD+ Android Development] kdejong2012:
Does anyone have stability issues when the battery gets low (10-20%) with 5/30 build? When battery reaches 10-20% level, display starts to flicker to the point where tablet is unusable and needs to be rebooted. Typically, I just put on charger at this point. Just curious if others are having similar issues. This is my wife's tablet so it happens when she's using it and not easy to get logcat or any diagnostic info. I have not turned off HW overlays since everything else is working great.
[Nook HD, HD+ Android Development] prsa01:
================

[Quote Amaces:]

Well, that's your problem… We had already established that your user settings in /data are broken or corrupted, so restoring them after all that clean install work yields the same behavior, unsurprisingly; there was no point delving into your mention of that accessibility service error, but clearly this is a purely software issue. You've already tested that the brightness control interface works properly in recovery, which is just another Android distribution, same as stock, just not broken like your current configuration in /data. F2FS has nothing to do with any of this

===========

it wasn't quite as simple as just not restoring the data partition. I had done that multiple times as well. Part of this is my admittedly very limited android knowledge. If I reset everything and installed using my original gapps it would go thru the initial device setup including getting my google account info. Selecting the exising nook hd+ device would put me back with unworking brightness control. If i installed using the gapps you recommended it would not take me thru google account setup and if I tried to add an account the google account is not listed as an option. Under that scenario google play would crash. Brightness control does work in this scenario. What finally worked was installing my original gapps and telling setup that this was a new device.

On a side note I would like to know how to get the google account setup under the gapps you pointed me to or make play store work or whatever.

Thanks again for your patience workig with a relative Android newbie

Most importantly, now that I undid whatever i manahed to do to screw it up, I'm again loving these builds!!
[Nook HD, HD+ Android Development] amaces:
Then, indeed, your problem is unrelated to the other well-known IPv6 bugs, but rather to the basic 802.11 handshake/DHCP negotiation with your AP. Assuming that you have Wi-Fi set to always on, that delay suggests either very aggressive/short DHCP lease times, or some other more basic timing issue between the AP and your Nook. As long as you don't switch networks, a static IP is perfectly fine. As a side note, sounds like your router does have IPv6 enabled by default (like it should these days), so local-link, other type of LAN-only addresses are issued regardless of WAN/ISP capabilities.

Yeah, that behavior used to happen fairly often on CM11 and the early builds of CM12.0, and like you, I'd turn the screen off, wait a second, then turn it back on. Those issues seldom happen now, but I did commit this touchscreen change a couple of weeks back, which to me was an improvement (certainly in recovery where they deal with touch events differently). Not sure that we'll make any more changes to the touchscreen driver…

It's very odd that the Google account wizard didn't show up immediately after a fresh install; BaNkS is one of the better known GApps packagers, and his tends to be quality work. Since I haven't had to go through this process in a few months, I think you should continue with the package that's been working for you. In theory, it shouldn't make much difference, but for many practical reasons, some packages are a lot worse than others (PA clones went downhill fast, for example).

Anyway, it sounds like your broken configuration managed to get backed up in the cloud; truly starting from scratch was a sure way to fix it, alas time consuming and frustrating… More and more settings and app data are being stored on Google's servers nowadays, and with Android M, pretty much all configuration will be. So yeah, be wary of random apps requesting accessibility, administrative privileges; legit ones like Tasker, rootless Greenify, etc have a reason, but many don't. The silver lining is that you know what to do next time ;)
[Nook HD, HD+ Android Development] squall2131:
I've been lurking for a while and lost track of some of the latest messages in this thread, does the latest beta/experimental builds have working hardware acceleration for video? I mainly use my nook hd+ as a Kodi/netflix watching device, so i don't want to update from the 5/31 build until I know the media playing support is working correctly.

Many thanks for all your hard work!
[Nook HD, HD+ Android Development] ieatabiscuit:
Anyone know how well Bluetooth works with the ROMs latest and greatest? Specifically pairing a sixaxis controller? I ask because its common for CM ROMs to not work with it from what I've seen, but the latest CM nightly releases actually have worked with it quite well for a bit. It's a nice little setup with some emulators on my HD+.
[Nook HD, HD+ Android Development] windoge89:
I don't know about sixasis, but Bluetooth speakers work fine for me.
[Nook HD, HD+ Android Development] ieatabiscuit:
I'd bet nobody has, it seems that the lack of compatibility with CM ROMs in the past made it an abandoned hope, I can't even Google much information on it working now (which it does for those curious). I know it doesn't work on earlier releases of this ROM, might not now, is not really on any priority list I can imagine. It's a nice dream though look. Maybe as the kernel matures, it will fall into place. Gotta love [MENTION=4473900]amaces[/MENTION] with that dedication to the cause.
[Nook HD, HD+ Android Development] asakurato:
I noticed weird thing lately. When I leave my HD+ charging, sometimes I look at it and see green led and think it is charged, but when I open cover, it isn't fully charged and isn't charging anymore. If I replug the cable, led change to orange again and it starts charging again. Happened today when I left it overnight at 15% and woke up at 23 something. Again happened after it, now at 74% (same green led showing). Anyone had same thing? What can be causing it? I'm on 11/06 build.
[Nook HD, HD+ Android Development] sutty86:
What's the most stable build atm gents?

I use the tablet for reading,browsing and movies via MX player.

Any major difference with SOT etc

Currently on cm11
[Nook HD, HD+ Android Development] asakurato:
Just flash the latest build, the only major bug is flickering in landscape mode, but thats kernel related, not rom. Other way, its pretty much stable.
[Nook HD, HD+ Android Development] Shadowpain:
There is also a bug with hangouts/ skype calls . (audio is choppy or you can't hear anything )
[Nook HD, HD+ Android Development] squall2131:
Thanks for the reply kind stranger!
[Nook HD, HD+ Android Development] ieatabiscuit:
I had some weird charging issues once, it would say full, then a random charge level, then it said 1% for 3 days straight with no recharging. I discovered later that the micro SD card I was using had given up the ghost. Upon replacing it, the issue has never returned. I don't understand how, but I WAS able to reproduce it on a freshly opened nook HD+ with no mods to it. Upon removal of the faulty card, that nook also started to perform perfectly again. I then repackages the new nook and replaced it I n the closet as a spare if I kill my main one with tinkering.
[Nook HD, HD+ Android Development] Posty91:
Flashed wrong recovery

Hello,

i did a big mistake. I flashed twrp-2.8.6-hummingbird on my NOOK HD+. Now it doesn't boot anymore.

The case is that the device isn't completely turned off. The LCD is bright black.

When i hold the power button for a short time it will be completely dark.

Then i turn it on and after the nook logo appears for a short time the LCD is bright black again.

Has anybody a idea to fix this problem? I read that i need a bootable sd card with a revovery for cm11.

Would be great if anybody give me some instructions.
[Nook HD, HD+ Android Development] Shadowpain:
Check leapinlar's guide (section 1 ) on how to make a bootable sd with cwm recovery here

I think that's the only option.
[Nook HD, HD+ Android Development] Posty91:
There are a lot of files. Which one is the right one in my case?
[Nook HD, HD+ Android Development] twiztid_:
Read the ENTIRE section called 1. Clockworkmod (CWM) Recovery - READ THIS SECTION FIRST, IT HAS EVERYTHING YOU NEED TO GET STARTED!

Then I'm pretty sure the file you need is: NookHDplus-bootable-SD-TWRP-2.6-for-emmc-BOOTFILES-rev0-(09.15.13).rar

Follow the instructions, and that will give you a bootable MicroSD with TWRP. After you get it set up, copy the Ovation TWRP IMG file to the MicroSD, and reinstall it as soon as you can. It may take you a few boots for it to read from the MicroSD, but it should work eventually. Smaller cards tend to work better, my bootable is a 2gb, and try to avoid MicroSDHC (4+GB) if possible.
[Nook HD, HD+ Android Development] Posty91:
Yes thank you. Your instructions worked.
[Nook HD, HD+ Android Development] mikey williams:
I have had similar problems with brightness to psa01:

On my NookHD (16Gb) I have been running CM11 with no problems (other than a bit sluggish)

Having successfully run CM12 on my NookHD+ thought I would try it on the NookHD

Used flashify to change from Clockwork Mod to TWRP 2.8.7.0

Made Nandroid of current set up.

Then wiped in TWRP (system reset, and caches) and installed the 0622 hummingbird.

As soon an it started booting, the screen started flashing every second or so and continued flashing after completing the setting up - nothing else was flashed (no gapps)

The brightness setting did not change no matter where the slider was. After an hour or so it was still flashing regularly.

So back into twrp and restored CM11 which again worked with no brightness problems.

Retried the above with 0530 file but exactly the same result.

So back on CM11 but I liked the bit that I saw of CM12.

Odd!

psa01 says he has overcome the problem but I couldnt follow what he did.

Any advice please?
[Nook HD, HD+ Android Development] tebra:
I have this flashing screen bug on my hummingbird only directly after a reboot. But that bug stop by turning the screen off/on. So not a big bug form me
[Nook HD, HD+ Android Development] windoge89:
For me that happens when I reboot with maximum brightness sometimes
[Nook HD, HD+ Android Development] mikey williams:
Unfortunately I cannot control the brightness as the slider does not change it.
[Nook HD, HD+ Android Development] windoge89:
Even after turning the screen off and back on again? That usually fixes it for me
[Nook HD, HD+ Android Development] twiztid_:
Do a clean install (wipe /system, /data, /cache, and /dalvik), and when you install gApps, choose a new device. It seems something is being backed up with your files that is bugging brightness. Possibly try a new gApps package. Amaces suggests Bank's gApps, but I personally prefer something smaller, and switched to Slim gApps Zero package.
[Nook HD, HD+ Android Development] pcspecialistpdx:
Why not http://wiki.cyanogenmod.org/w/Google_Apps ?
[Nook HD, HD+ Android Development] tj2003:
I just did a fresh install install of Windows 7. Hooked my one Nook HD+ running the 06/07 build it loaded drivers and connected.

My other Nook HD+ is running 06/22 build. The minute I plug in usb it restarts but at the blue logo screen. I have tried different cords and usb ports. Anybody else have the same problem?
[Nook HD, HD+ Android Development] amaces:
Hangouts Dialer Fixed

Non-BT audio input (i.e., built-in mic, wired headset) is much improved. After some back and forth, it turns out that a few sampling rates were not synchronized across the different abstraction layers working on top of the kernel. Hashcode has pushed this: http://review.cyanogenmod.org/102058, and the builds from today incorporate it (ovation's build is up, hummingbird's in an hour or so).

As a side note, the benefits of switching to the new audio HAL should become a lot more apparent now. Even with brief testing, the quality of audio capture seems better than I remember in CM11, and these tablets may even be a viable speakerphone now.

Thus, no more holy trinity of major bugs, just a duality of broken screen casting and GFX underflows, although they probably add up to less than a full bug ;) Sadly, these two will persist for a while; Lollipop/CM12 does screen casting in a way not (yet) fully compatible with with our OMAP OMX, and the video system underflows might even last into K3.4… Either way, progress is being made.

With the exception of one experimental build (labeled DMABUF, in obsolete now), all other builds have had working HW accelerated video codecs.

The core Bluetooth stack works pretty well; it'll pair up with many devices, and many functions work well (foremost, A2DP high bandwidth unidirectional music streaming). Is the Sixaxis using an exotic BT profile? Either way, if it doesn't require some exotic HID support in kernel, and if you know that CM12.1 has fixed the userspace components, there's a good chance it'll work here as well.

On a completely different tangent, I'm glad to see that the thread has quite a bit of momentum, and enough good people willing to help (thanks, [MENTION=5720705]twiztid_[/MENTION] and the others), especially when it comes to addressing previously solved issues. This way, I can scale back my time here, and mainly focus on new bug reports, and more important, the work that remains to be done (Hashcode has awesome ideas about improving these devices).
[Nook HD, HD+ Android Development] techdudepro:
Has anyone else had any battery issues on the 6/22 hummingbird build? Because ever since I upgraded from the 6/15, battery life has been terrible. I barely used my Nook in the past 2 days, yet the battery keeps dying very quickly. Doesn't happen on the 6/15 build. I don't have GApps...

The first bar in the screenshot was from my nook being on overnight... the battery's never gone down more than 8% for me overnight.
[Nook HD, HD+ Android Development] panchokoster:
great! excellent news!

btw [MENTION=4473900]amaces[/MENTION], any chance to get the otg support back? http://xdaforums.com/showpost.php?p=42141795&postcount=491

regards
[Nook HD, HD+ Android Development] pastordl:
6/28 seems fine with only one quirky thing to mention. In Netflix the first 15-20 seconds of video has various green horizontal bars and no picture then straightens out and plays fine. Audio is good everywhere. Flickering still occurs in landscape mode but doesn't FC with either SwiftKey or hackers. No flicker with Zippy BT 500 keyboard in landscape.
[Nook HD, HD+ Android Development] wanderso:
Sad to say that the 6/28 build does not solve my Azio Bluetooth keyboard problems (no data comes through but it does pair) and my Plantronics PLT 1100 now can hear my Ovation on media playback, but no audio on a WiFi call. I did get TWRP 2.8.7 installed at least - thanks, Amaces!