yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] YevOmega:
Thanks a lot. I got 4896 on Quadrant and 13444 on Antutu running Pinguy's ROM version 2.4.3. Those are the best of two Antutu and Quadrant runs.
[Nook HD, HD+ Android Development] infra_red_dude:
One reason I jumped back to CM11 was that succulent May/July builds have TRIM disabled.
[Nook HD, HD+ Android Development] mmoalem:
Thanks. Any idea which nightly is the most stable at the moment?
[Nook HD, HD+ Android Development] infra_red_dude:
I jumped straight on to M9, never tried anything else of late.
[Nook HD, HD+ Android Development] Black6spdZ:
any work on getting f2fs working for nooks? I've switched my Nexus 7 and Note 3 over and its a very noticeable difference
[Nook HD, HD+ Android Development] rhyang:
I agree, f2fs is great on my 2012 Nexus 7 and my new Moto G LTE. I've managed to compile TWRP with f2fs support, but to make the whole thing work the kernel needs to have f2fs patches applied. See the "yellow kernel" thread for more details. It's something I am considering doing, but it's kind of more work than I want to bite off right now. Maybe after the summer .. I just took up fly-fishing as a hobby :)
[Nook HD, HD+ Android Development] Eric Karz:
Thank you
[Nook HD, HD+ Android Development] metropolitans:
I'm on M9 as well. It is fast and stable. I got an Antutu mark of 14026 with it, just after installation and before I put most of my apps back, and that's the first time I got anything over 14000 on the HD+.

I was actually on one of the nightlies -- I think it was 8/15 -- and I started experiencing problems with boot loops and slowness. It was actually the very first time since I started with CM11 nightlies back in January that I had any significant issues. I don't know if it was that particular nightly that was the culprit or whether my system had just gotten so junked up after installing an average 1-2 nightlies a week over 7 months. So I decided to do a fresh install with M9 after cleaning everything out in CWM and now everything works great. I'm done with nightlies now and won't install anything new until M10 or a final is released.

Also ... an update on a problem I had with a glitchy touchscreen caused by a third--party generic charger -- I installed verygreen's Nook Charger Control, and it fixed the issue about 95%. I can now use the HD+ when using the generic charger at the same time. Moreover, the app also does as advertised -- it will greatly accelerate charging from the USB port of your PC. So, thanks to verygreen for another great contribution to Nook users!
[Nook HD, HD+ Android Development] cwmoser:
What is M9?

I'm back after a long siesta from this forum.

Just figured out how to upgrade my Nook HD+ from JB to KK

using the nightlies.

I note a mention of "M9" -- what is M9?

Thanks

Carl
[Nook HD, HD+ Android Development] lmacmil:
From the Cyanogenmod website:

Right now, CyanogenMod consists of four parallel and active major versions: CyanogenMod 10 (Android 4.1), 10.1 (Android 4.2), 10.2 (Android 4.3) and 11 (Android 4.4). *The variants of the firmware are split into categories, such as: Stable, Release Candidate, M-series and Nightlies. The Stable version, as suggested by the title, is the tried and tested variant of the firmware proven to be mostly bug free and suitable for daily use. The latest stable version is available for an assortment of the officially supported devices. A Release Candidate (RC) build may not be the final version, but a variant that has no fatal flaws or bugs, on the stabilization stages to become the final product that is the Stable variant. M-series releases behave similar to the RCs, but are considered ‘stable’ for our users. *Lastly we have the Nightlies, which are as volatile as a firmware can get. These releases keep coming at an interval of a day or two and if you do end up trying one of these, do not be alarmed if your device goes cuckoo on you. These ROMs are largely untested, and as advised by CyanogenMod, not meant for use for an average user. These releases, are meant to test untested waters that may or may not break your phone.
[Nook HD, HD+ Android Development] vtdat:
Hi all,

I am using cm11 nightly. But I didn't see tethering&portable hotspots function. How can I get it to share internet connection via Bluetooth

Thanks
[Nook HD, HD+ Android Development] Black6spdZ:
yea it would be nice to possibly have a little OC ability baked in a new CM11 kernel as well.. if the fish stop biting for a bit lets try to crack it
[Nook HD, HD+ Android Development] mr72:
What approximate date was the M9 taken? Wondering if I can safely dirty flash it from my current nightly.
[Nook HD, HD+ Android Development] js365:
M9 had been posted on 8/4. http://download.cyanogenmod.com/?device=ovation&type=snapshot
[Nook HD, HD+ Android Development] mr72:
Yeah, thanks for mentioning that. However, I think the M snapshots are lagging weeks at least behind the nightlies, right? So if it was posted on 8/4 then it is likely equivalent to an early-mid July nightly, right?

Jumping off the nightly train and getting on the M train might require too much patience for me. Perhaps laziness will substitute for patience and I can keep from upgrading the nightly before M10 comes out.
[Nook HD, HD+ Android Development] cwmoser:
Post #1868t by Imacmil was a very informative description of the different types of distributions.

I have been following the Nightlies and find them - so far - to be very workable. Not too enthusastic

about dropping to an "old" piece of code because of how well the latest versions work.

Carl
[Nook HD, HD+ Android Development] metropolitans:
M9 includes changes up to July 27th.

Personally, I would not dirty flash M9 over a nightly more recent than that. I learned that the hard way. When I had instability with the 8/15 build, I tried installing a build from early August and it was even worse ... continuous boot loops and I could not even get into CM11. I was able to boot into CWM and reinstall 8/15 just so I could get back into CM11 to make a few manual and Titanium backups.

Then I downloaded M9 and installed that after first using CWM to clean everything out and start fresh. I think it paid off. The problems I had with the 8/15 build could have been entirely due to lots of residual crud having accumulated after having installed roughly 40+ nightlies on my HD+ since early January. The reason I decided to use M9 instead of a more recent nightly is because I was on a late July build right before I had installed 8/15 and remembered it was very stable.

So my recommendation is to do an M9 on a fresh install. M9 is so far along that you may never need to install another update or will at least be able to keep them to a bare minimum. Therefore, you may never need to fresh install again ... at least until someone makes Android L available for the HD+ and you are tempted to start the process all over again. ;)
[Nook HD, HD+ Android Development] snoozer854:
I want to do a fresh install to clean things up after installing who knows how many nightlies since 10.1 came out.

What is the best way of doing this. I am currently using CM 11 newest nightly & CMW Thank you
[Nook HD, HD+ Android Development] leapinlar:
Boot to CWM, do a factory reset and install the new rom and gapps.
[Nook HD, HD+ Android Development] hemeboy:
can't add new user

When I try to add a new user account with the latest build i get the error "Unfortunately, settings has stopped". I did not have this problem with earlier builds.
[Nook HD, HD+ Android Development] bmwh0r3:
I updated to the latest nightly as of yesterday and now my nook HD is stuck on the cm bootlogo. I can't get into recovery. Tried rebooting and all the typical. Did I get a bad download or something?
[Nook HD, HD+ Android Development] O.a.T.:
I too have been unable to successfully install builds based on the latest CMs for my Nook HD for about the last month. I have been able to completely shutdown (hold power for ~20 seconds) and then get into recovery (hold power and nook button simultaneously then releasing Nook button after a few seconds) to restore a nandroid I had. Getting into recovery and either restoring a nandroid or installing an older ROM is probably key for getting your Nook HD back in working order.

Anyone else have any experience with installing later CMs for the Nook HD?

Know that's probably not much help. Good luck.
[Nook HD, HD+ Android Development] Tight Git:
Running 20140820 without any problems (previous version was about mid July)
[Nook HD, HD+ Android Development] bmwh0r3:
I got into recovery wiped dalvik and cache... Now stuck on android is upgrading.... Starting apps I can't win lol

20140821 is what I have installed and having issue.
[Nook HD, HD+ Android Development] bornagainpenguin:
This is highly speculative, so please don't shoot!

Is it possible the screwing around Google has been doing with the SD Cards has broken something? I ask because I enter bootloops that matches the descriptions above when I put in my SD card on the latest Milestone (M9) and no such issues when I remove it and wipe the cache. No idea why this would be the case as this same card was fine when using the earlier CM 10.1 and is detected as having no issues when checked on my Macbook. I am going to wipe it and try seeing if that fxes anything, I just wanted to mention it as a possible source or contributor to issues. My card is an Sandisc 32GB microsSD card.

UPDATE:

Copying my files to the Macbook, repartitioning and formatting the MicroSD card when placed back in the Nook HD+ and my files copied back to the MicroSD card seems to have stopped the issue for me. No idea why this would be the case but there you have it. Maybe someone who knows more can tell me why this voodo worked for me, all I know is that it did in fact work for me. No guarantee it wil work for others but what have you got to lose?
[Nook HD, HD+ Android Development] bmwh0r3:
I just can't get it to boot right... What do I format to clean install from scratch?
[Nook HD, HD+ Android Development] bmwh0r3:
Fixed :)

Mounted everything and formated it all. Then on another device downloaded gapps and cm11 nightly 20140818 and put them on the SD card. Inserted it, flashed them. Updated to current nightly once booted up with no issue.
[Nook HD, HD+ Android Development] Sherip:
Thanks for the update! I was still running the January SD card build which I had continued to prefer even after trying various other SD card options. I've loaded the new build on a freshly reformatted card, and so far all is well.
[Nook HD, HD+ Android Development] lordsilencer:
Just a stupid question. I am now using 10.2.1 stable build and want to upgrade to cm11 m9 build. What is the proper way to do the upgrade? Is it just go to the CyanogenMod updates options in settings > About tablet and then install the m9 build I downloaded? Do I need to update gapps or other component as well?
[Nook HD, HD+ Android Development] cwmoser:
I just installed Kit Kat on my Nook HD+. Stated like you with CM 10.2 Jelly Bean installed.

Had a hard time installing KK and finally found the reason was that the CWM recovery was

incompatible with KK. You need first to install CWM v 6046 recovery -- then its smooth as silk.

To install KitKat on the Nook HD+, you need these three files:

1- NookHDplus-CWM-6046-for-internal-memory-rev0-(07-13-14).zip

Scroll to bottom of this page:

http://xdaforums.com/showpost.php?p=42406126&postcount=7

2- pa_gapps-modular-micro-4.4.2-20140426a-signed.zip from:

http://xdaforums.com/showthread.php?t=2397942

(PA=Paranoid Android)

3- a KitKat nightly image from:

http://download.cyanogenmod.com/?device=ovation
[Nook HD, HD+ Android Development] cookie1003:
hi can anyone help ?

ive installed kitkat & had it running fine apart from the odd hitch, ive updated to the latest safe updates (non nightly's) & everything has been fine then the other night it seemed to do a small update on its own & from then on i can't get into my settings. every time i click on any of the setting buttons including wifi the screen goes blank for a second or 2 then back to the home screen.

any ideas anyone ?

thanks
[Nook HD, HD+ Android Development] leapinlar:
The update on its own was probably one of your installed apps being updated by Play Store. I would suggest you boot to CWM and factory reset and be careful which apps you reinstall. I'm sure it is one of them causing the issue.
[Nook HD, HD+ Android Development] JustSkilled:
Milestone #9, a sort of stable build within the nightlies
[Nook HD, HD+ Android Development] tuffluck:
I'm confused. Coming from 10.2. Do we install the recovery zip YOU suggested or the one from the OP? And can I just put the recovery zip, m9 snapshot and gapps on my Nook external memory and boot into recovery and flash that way? Or do I have to go back to installing through the sdcard like I did for 10.2?
[Nook HD, HD+ Android Development] leapinlar:
Use the versions from the referenced dummies guide. They are easier to install than the ones from the OP. Then just install the M9 and PAgapps. You may or may not need to wipe first. Some get by without wiping and others run into trouble.
[Nook HD, HD+ Android Development] digixmax:
No need to go through the SD-based recovery method.

Just use your current recovery to flash the new recovery zip file linked in the OP (i.e., "ovation recovery image (CWM)" for HD+, "hummingbird recovery image (CWM)" for HD),

then reboot into the new recovery

and use it to flash CM11 and Gapps -- see http://xdaforums.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171 for more info/pointers.
[Nook HD, HD+ Android Development] tuffluck:
Thanks guys. How do I restart recovery?

---------- Post added at 06:25 AM ---------- Previous post was at 06:02 AM ----------

Never mind, I figured it out. Thanks fellas!
[Nook HD, HD+ Android Development] tuffluck:
I actually went by the OP instructions and didn't have to wipe. It worked just fine for me.
[Nook HD, HD+ Android Development] digixmax:
M builds now supplant the "stable" builds -- see http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m6-release.
[Nook HD, HD+ Android Development] Darrian:
I didn't find the M9 to be that great, though it was loads better than M8. The lastest nightlies seem to be pretty fantastic though. Very stable and quite fast, plus a few new features.
[Nook HD, HD+ Android Development] tuffluck:
Which nightlie? I just went to 0831 from m9. It's fine stability wise, but I don't recognize any new features?
[Nook HD, HD+ Android Development] cwmoser:
I too think the nightlies are very usable.

Can't really say I found anything wrong or quirky with them.

Currently running with the 0831 nightly.

Anyone note any "issues" with the nightlies?

Carl
[Nook HD, HD+ Android Development] leapinlar:
The issue with the nightlies is they are highly experimental and just because one nightly works fine, it does not guarantee the next nightly will. That nightly may have a new bug introduced that day that makes it unstable. It will eventually get fixed in subsequent nightlies, but you never know. Whereas the M snapshots have been purged of bugs before they are released
[Nook HD, HD+ Android Development] tuffluck:
Interesting. I haven't seen any issues yet with the 0831 nightlie, but should I go back to the more stable m9?
[Nook HD, HD+ Android Development] leapinlar:
No, I was just pointing out the risks of using nightlies. If 8/31 is working nicely for you, by all means keep it.
[Nook HD, HD+ Android Development] eeter:
screen sensitivity

Is there an app for screen sensitivity for CM11? My Nook HD+ screen does'nt react often. I cannot open links easily and I have to tap on the screen repeatedly

I know thwr wis a kernel for CM10.2 but cannot be used for CM11
[Nook HD, HD+ Android Development] Darrian:
I'm still on 8/29, but 8/26 ran just as well for me. So far I've noticed the ability to set the clock position and soft reboot added to the reboot menu.
[Nook HD, HD+ Android Development] wellersl:
Some people see it. Some people don't. You and I see it. It's so bad on mine, I keep going back to 10.2.1 Stable. Setting the governor to Performance helps a lot. But my HD+ isn't stable enough to run that way for long and reboots.
[Nook HD, HD+ Android Development] cwmoser:
I have CM11 on my Nook HD+ and use this app to adjust touch sensitivity:

NookTouchScreenSensitivityAdjuster-4.apk

Works great.

Download link is in this thread:

http://xdaforums.com/showthread.php?t=2347003&page=8
[Nook HD, HD+ Android Development] Jann F:
Have you set any app-ops restrictions or popup notifications?

Had issues with this on M9 on my i9100, on my ovation everything works fine.

Also, try to avoid overlays like FB chatheads and the download manager, they also tend to let my ovation reboot.

OTG-enabling app is also there: http://nook.rootshell.ru/hd/
[Nook HD, HD+ Android Development] wellersl:
No, I have not. Is that meant as a recommendation or a do-not-do?
[Nook HD, HD+ Android Development] Jann F:
Just a recommendation.

Would be great if you could collect some logcats and last_kmsg's in /proc during and after a reboot.

Because filling in a bugreport in Jira would be more effective ^^
[Nook HD, HD+ Android Development] wellersl:
I'll see what I can do. Perhaps ironically, I really only use it anymore for Kindle books (known to cause reboots) and web-surfing (I've never found any joy in Android browsers).
[Nook HD, HD+ Android Development] :
I use the kindle app often and never had a reboot from it. They did a patch right when I first started using it a several months ago that fixed that or something. Can't remember now, but it shouldn't be a problem.
[Nook HD, HD+ Android Development] wellersl:
Supports my theory that we're seeing subtle differences in hardware if not all out differences in hardware revisions.
[Nook HD, HD+ Android Development] spd_rcr:
Just noticed the OP updated the sdcard build Aug.17th.

Anything different or advantageous vs. just continuing with the usual nightly builds from the CM repository ?
[Nook HD, HD+ Android Development] leapinlar:
It is just a nightly or M snapshot modified for sdcard, so I would say no.
[Nook HD, HD+ Android Development] spd_rcr:
That's too bad. I was hoping there was possibly a new kernel or some hardware specific patches. CM11 certainly runs so much better than the stock B&N firmwareit's hard to really fault any glitches it does have, but it still seems to choke & crash out of games that require a more active network connection. Might be asking too much of the budget e-reader.
[Nook HD, HD+ Android Development] lath19:
I never really had a stable tablet dating back to 10.2. Always had issues with force close, slow, lag, restarts, etc. Same thing happened on 11 with official releases and nighties. Full wipe and clean install never helped which made the device near useless.

I was about to give up on using the tablet but decided to do 1 more factory reset and a clean install of m9. What an amazing difference. It feels like a completely different tablet. I have no idea why one build would make such a huge difference but I'm stoked that it did.
[Nook HD, HD+ Android Development] cwmoser:
I had a similar experience with my Nook HD+. My first experience with flashing it I put on JB - slow, quirky, touch sensitivity was not good.

Now I am on the Kit Kat Nighties (currently 8/31) and like you I find my Nook running like its a "completely different tablet".

One thing I learned when I flashed KK ... at first KK ran slow and I found that certain "news" apps seemed to hog the tablet.

I had a lot of them and apparently they were constantly downloading news stories. I got rid of the ones that I thought were suspect

and kept the ones that seemed to behave. KK is so good, I highly recommend it for Nook HD+ owners.

Carl
[Nook HD, HD+ Android Development] wellersl:
How long did it take and/or how long has it been?

---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------

Which ones, please?

I use the Genie.apk and AZCentral.apk. Both are kind of ... meh. Genie won't re-size in KK. Or it didn't the last time I was on KK.
[Nook HD, HD+ Android Development] Arbelzapf:
Hello everyone,

After using my trusty Nook Color for what feels like an eternity, I decided to do an upgrade and got a used HD+, which I received yesterday.

It came with CM10.2.1, so the upgrade to CM11 was very easy. Now, after using it for a day, I think I'm going to have to ask for some tips on how to get around the frequent issues I'm experiencing.

I read back ~10 pages and it seems to be pretty hit-or-miss and I could not find much information on how to get a stable build. M9 and a current nightly both give me loads of problems:

- Apps force closing

- freezes, forcing me to reset the device

- reboots

- graphical glitches/artifacts

- flashing of a black screen (this only happened when charging until now)

M9 seems to me more force-closey, while my 0903 nightly seems to be more rebooty. Are there any known settings that help stability? Or settings that are known to cause issues? When it works, this device is incredible.

I will gladly grab logs/dmesgs/kmesgs of future issues, but right now, I would like to get the obvious stuff (that I might have missed) out of the way. ;)
[Nook HD, HD+ Android Development] huntz:
I'm currently using a nightly and all is working nicely for me.

I can suggest to do a factory reset before flashing CM11. I know, you have to reconfigure all your stuff, but is a necessary pain to get a stable device.

Good luck :)
[Nook HD, HD+ Android Development] Arbelzapf:
Oh, yes I did that, of course. I wouldn't bother you guys if I was running around dirty-flashing different versions of Android :angel:

I can get a seemingly reproducable reboot when trying to connect to Facebook with the (LinkedIn) Pulse app.

It's happened 3 times in a row now:

http://pastebin.com/Ag0D23Am

EDIT:

I am going to assume this is related to this post?:

The app is creating a webview overlay with the facebook login.
[Nook HD, HD+ Android Development] Arya99:
Thanks, I went to install this earlier but someone said it would not work with cm11. It made a huge difference when I was on cm10.
[Nook HD, HD+ Android Development] cwmoser:
Hmmm. I installed it on my CM11 (nightly) and it did not break anything.

Perhaps its not working but my touch sensitivity with CM11 is great.

I do remember touch with CM10 was poor and running this helped immensely.

Carl
[Nook HD, HD+ Android Development] Jann F:
Try to get a logcat while doing it. Also grab the last_ksmg and upload it here. I will open an issue in the following days in Jira with all logcat and kernelringbuffer logs collected.

Please quote me in the post with the logs or do [MENTION=4437688]Jann F[/MENTION]
[Nook HD, HD+ Android Development] Arbelzapf:
The kmesg is in my previous post:

http://pastebin.com/Ag0D23Am

I'm struggling to set up adb for the Nook HD+ right now, so I couldn't get a log that way (I assumed that would be the preferred way to log something that reboots the device)

Anyway, I did a recording using the logcat reader app, but I believe it cuts off before it gets to the interesting part.

Maybe it's still useful:

http://pastebin.com/KG75fu7s
[Nook HD, HD+ Android Development] Jann F:
You could also try to use the terminal to log to a file.

$: su
#: logcat -f /sdcard/logcat.txt

same for kernel logs

$: su
#: cat /proc/kmsg | /sdcard/kmsg.txt

if last_kmsg doesn't show useful stuff.
[Nook HD, HD+ Android Development] Arbelzapf:
I tried that. Maybe it's just using a different log level, but the log came out significantly longer.

Hope it's useful

http://pastebin.com/YeETX8CN
[Nook HD, HD+ Android Development] leapinlar:
Since you upgraded, did you wipe as part of the installation? Did you update gapps?
[Nook HD, HD+ Android Development] Arbelzapf:
I have done multiple clean installs since I got the device. It should definitely be clean by now. And I did both when I upgraded to cm11.
[Nook HD, HD+ Android Development] leapinlar:
Did you go to mounts and storage and format 'data and datamedia'? That is a true wipe.