yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Darrian:
I'm not sure if this is a bug or not, but I noticed I can't move apps to the sdcard anymore. Unsure if this is a CM11 issue or if Google removed that feature from Kit-Kat.
[Nook HD, HD+ Android Development] leapinlar:
You said 'anymore'. Are you saying you could do that on an HD/HD+ version of CM previously? To my knowledge that feature has never been available on the HD/HD+.
[Nook HD, HD+ Android Development] Darrian:
LOL Well, that explains it then. No, I haven't ever done it on the HD+ before. I haven't done it since I was using my Nook Color. I haven't needed to, but now that I have been forced to downgrade to the 16GB model I thought it could be helpful, so I tried to do it and found that I can't. Oh, well.
[Nook HD, HD+ Android Development] rholm:
Except for LMT getting killed occasionally, I'm pretty happy with 06/06. It happening much less than some of the April and May builds.

Cheers,

Rich
[Nook HD, HD+ Android Development] LucaToo:
LMT killed only a couple of times and NO forced closures on 06/06 - both of which happened regularly on M6. After a dodgy couple of months my Nook is back..!
[Nook HD, HD+ Android Development] tebra:
New automatic nightly build for HD failed again.

See http://jenkins.cyanogenmod.com/view/All/job/android/71642/console

Build is aborted because of a timed out.

Look like the same problem as 2 weeks ago.
[Nook HD, HD+ Android Development] craigcharlie:
Hey, anybody have any idea yet how good battery life is on 4.4.3 or 4.4.2 vs CM10 versions? I was on CM10.1 before, and the battery life was awesome. It seems to drain faster since I moved to 4.4.2/4.4.3, but I haven't tested for direct comparisons.

I have ART enabled btw, which seems to make the tablet a lot snappier. It just seems like standby battery life has taken a hit though.

Also, is anybody running a custom kernel with the 4.4.3 builds?
[Nook HD, HD+ Android Development] Moxie3000:
I can at least corroborate the battery drain issue of CM11 vs. CM10.2. The culprit seems to be musb_autosuspend_wake_lock (per Better Battery Stats 1.16 B3), which kept my device awake for 18 hours. Deep sleep was only at 77%. So there's definitely a problem there.

Anyone else see this?
[Nook HD, HD+ Android Development] TheDannemand:
I must say I don't see this at all. For months now on different versions of CM11, my HD+ hardly uses any battery when idle -- even with WiFi left on and notifications running for both my wife's and my own accounts.

I don't have it quantified, but I am regularly surprised when picking it up after a couple days of little or no use and it's still at almost full battery.

Even with moderate use, it lasts pretty long. I'm particularly impressed that watching hours of Netflix on Chromecast (with the HD+ as controller) uses almost no battery. It cannot be completely idle, even with the actual streaming happening on the Chromecast.

But if my wife starts playing Eufloria (particularly outside with high brightness) that'll burn through the battery in a few hours.

I just updated from M6 to 2014-06-07 nightly the other day (clean install). Battery seems to be the same, but I need longer to verify that.
[Nook HD, HD+ Android Development] Moxie3000:
That's fantastic! I think I'll update from 05-17 to 06-07 over lunch, then.
[Nook HD, HD+ Android Development] extrem0:
My battery is the same as in cm10.2. It can idle for a month or more.
[Nook HD, HD+ Android Development] TheDannemand:
Of course YMMV, I should have included that. Make sure to get updated 4.4.3 Gapps with the latest nightlies.
[Nook HD, HD+ Android Development] Moxie3000:
I used cmupdate...so hrm... no issues bringing up the Play store or viewing email, though. If it starts acting up I'll flash the new gapps. Thanks for the heads up.
[Nook HD, HD+ Android Development] Blenky:
I take it that is if you do a full wipe. I always install new nightly over current version.
[Nook HD, HD+ Android Development] TheDannemand:
In this case mine was a full-wipe clean install because I came from a test of succulent's ROM, and before that M6. Since this was also the first 4.4.3 install on the HD+, I decided to do a factory reset and wiped /data-media (internal sdcard) /system and /bootdata.

But even when I just update a nightly, I always wipe /system and /bootdata (and of course /cache and dalvik), then flash the ROM and the latest Gapps again. It takes only a few minutes, and eliminates a host of potential issues.
[Nook HD, HD+ Android Development] Blenky:
But isn't that time consuming having to reinstall all apps and configuring everything? I have quite a few apps loaded and wouldn't want to reinstall them each time a do a nightly
[Nook HD, HD+ Android Development] leapinlar:
Never wipe /bootdata. It helps nothing and could cause a bad problem (bootloops).
[Nook HD, HD+ Android Development] TheDannemand:
It's an old habit from my days with Optimus V which didn't always flash cleanly over old data. I did accidentally reboot one time after wiping /bootdata. You only make that mistake once :D

Sound advice, though, in a thread like this. Thank you!

When doing a complete clean re-install (as this last time) it takes an hour or two: I let Google re-install all apps (except the ones from Amazon appstore) then use Titanium to restore app-data (for apps that need it).

But when updating the ROM or Gapps, it only takes a few minutes to wipe /system and flash ROM and Gapps again (see leapinlars warning about wiping /bootdata). All apps and data will remain in the /data partition. Any apps from the Play Store, which are updated with the new ROM or Gapps, will automatically be removed from /data on first boot.

Again, the purpose is just to eliminate any potential issues. Indeed, I have very few problems on any of my devices. Most of the problems I see reported here, I've never experienced.
[Nook HD, HD+ Android Development] leapinlar:
But /bootdata is not data. The name makes it sound like it is, but it is not. It is configuration information on the status of your last boot, not data (that is in /data). Wiping that configuration info just messes up the device.
[Nook HD, HD+ Android Development] Blenky:
When doing it this way do you have to install Gapps as well as new nightly? Also how do you wipe /system. I have always just installed a new nightly over the last - the only concession is to wipe the cache in recovery first.
[Nook HD, HD+ Android Development] TheDannemand:
Thank you. I never meant to say it is "user data", that's not why I wipe it before a clean install.

Some flash memory (controller or NAND) is known to occasionally produce bit errors when flashed without being erased first. As I mentioned, Optimus V (and other devices in that family) were known to have this issue. I like to wipe before flashing in order to eliminate that risk, however small.

Of course, wiping /system is by far the most important, since it not only reduces the risk of such bit errors when the actual ROM is flashed, but also cures any issues that may have accumulated from successive ROM and/or Gapps updates (from addon.d scripts or otherwise).

I believe /bootdata contents (BCB and BootCnt) get re-created every time a ROM is flashed, and that is why I wipe that as well. Certainly I've never had an issue the dozens of times I have done this (starting in early 2013). And my BCB and BootCnt files are intact, dated as of my last flash. As I mentioned, my Nook HD+ shows exemplary behavior in almost every way.

That said, my respect for your authority on all things Nook, and your efforts here helping countless Nook owners who got themselves in deep waters, is almost infinite. And that comes from the bottom of my heart. You are absolutely correct that the probability of being saved from a bit error by wiping bootdata is tiny, compared to the (high) likelihood that someone will accidentally reboot before flashing a new ROM -- and then come here and ask for help. That is why I fully acknowledged your warning in my last post. If you advise it, I am happy to edit my original post to include a link to this post (with your warning).
[Nook HD, HD+ Android Development] TheDannemand:
Oops, I overlooked this when I made my last post.

Yes, if you wipe /system, you need to flash both ROM and Gapps again. I don't update every day, only when a seemingly good version comes out. Then I'll grab TKruzze's latest PA Gapps and flash them both.

Edit: You wipe /system in Recovery just before flashing the new ROM and Gapps. I forget the exact menus, and they depend on whether you use CWM or TWRP. It's easy to find in both.
[Nook HD, HD+ Android Development] procter:
Does the fitbit device work with NOOK HD+ CM11? I tried to install this modded fitbit app from XDA, but it could not find the tracker. On the other hand the officially supported S3 worked fine with the un-modded app.
[Nook HD, HD+ Android Development] digixmax:
No, HD+ Bluetooth is not the Bluetooth Low-Energy variety used by Fitbit.
[Nook HD, HD+ Android Development] naveed.hasan:
Yes, it is. No one owns this issue on JIRA (CYAN-2494), but it is trivial to resolve so that BLE on the Nook HD+ works just fine.

https://jira.cyanogenmod.org/browse/CYAN-2494
[Nook HD, HD+ Android Development] bpaulien:
M7 available?

I understand they made a snapshot "M7" on the 9th, but that's when our ovation stopped building, so I was wondering, once it's up and building properly again, will an M7 be available? Or do we have to wait until next month for the M8 snapshot?
[Nook HD, HD+ Android Development] dealpapa1:
coming soon ;)
[Nook HD, HD+ Android Development] Blenky:
Thanks for the info. I'll bear that in mind for next update.
[Nook HD, HD+ Android Development] dealpapa1:
anybody try mokee before?

http://download.mokeedev.com/?device=hummingbird
[Nook HD, HD+ Android Development] Moxie3000:
Just a quick update on my battery issues for anyone else who might be seeing drain. It may not be the ROM; looks like YouTube was the culprit for me. I used BetterBatteryStats to find out that the YouTube process had been awake and running for over 2 hours (after 4 hours of Unplugged time). After I killed it, battery drain while idle resumed a respectable flat line on the graph. A Google search turns up a number links indicating this is a known issue and that there may be a fix coming in some future update. In the meanwhile, kill YouTube after you're done with it and/or use Greenify.
[Nook HD, HD+ Android Development] blautens:
That link is a little annoying for those of us that only speak English - the translated page blows.

But I checked out a few other sites about it and saw the video of it, and I don't see where it's anything special, other than slightly larger and squared off/boxed application icons, ala IOS. It's no MUI, that's for sure.It could be done via a theme to any version of Android.

Am I missing something?
[Nook HD, HD+ Android Development] pgrunwald:
Hi all, I have been running 3/23 nightly and I have lost track. Can I safely update to one of the June builds?
[Nook HD, HD+ Android Development] excalibar001:
I guess so. After a long break, made the jump to June 13th built. it is stable, no FCS and all my apps run fine. Installed the ROM and the latest 4.3.3 gapps. Got a process acore error after the first boot. Deleted account setting data and it went away. Another thing, tried to switch to ART to test it out but booted right back to Dalvik so ART may be broken. Other than that, things are running ok.
[Nook HD, HD+ Android Development] jck_w:
Any luck on the location settings in Google maps?
[Nook HD, HD+ Android Development] tebra:
Does not work on June 13
[Nook HD, HD+ Android Development] mr72:
I am using 6/13 with ART and it is working fine. FYI
[Nook HD, HD+ Android Development] excalibar001:
Were you on ART previously, before the upgrade? if so, then ART may be fine, and the problem lies somewhere else. I'm on dalvik and cannot switch my runtime on 0613. When trying to switch the runtime, I get a message, the tablet reboots but back right into dalvik again without the lengthy compilation of apps.
[Nook HD, HD+ Android Development] mr72:
Yes I have been using ART always on CM11. I wonder why yours won't switch.
[Nook HD, HD+ Android Development] webdroidmt:
Sounds like you're running Xposed module. :) If you are, it's not compatible with Art and will always reset back to Dalvik.

Mike T
[Nook HD, HD+ Android Development] excalibar001:
Yup. That must be the reason behind it. I installed it just a few days back to tweak GEL. I love Google launcher but it has limited config options. with xgel I have tweaked it to my liking.
[Nook HD, HD+ Android Development] pgrunwald:
Where is the setting to enable ART and Dalvik?
[Nook HD, HD+ Android Development] Tight Git:
Settings

Developer options

Select runtime
[Nook HD, HD+ Android Development] :
I don't see developer options
[Nook HD, HD+ Android Development] :
Please don't take offense now, but in that case, ART may not be for you in it's current form. While I use it myself (and so do others) it is still in an experimental phase, and can render your tablet unbootable, requiring some knowledge and/or googling skills to fix.
[Nook HD, HD+ Android Development] gale2000:
I can vouch for this. It took me much googling and many hours to get my Nook working again after switching to ART with an unsuccessful boot.
[Nook HD, HD+ Android Development] pgrunwald:
I had it before and forgot about the magic 7. I was running art before.
[Nook HD, HD+ Android Development] jbbandos:
Anyone has a June 05 or immediately before nightly? June 06 adds 4.4.3 stuff and breaks openvpn across all cyanogenmod devices, and I need it working...

Of course, the oldest nightly available at cyanogenmod downloads is June 07.
[Nook HD, HD+ Android Development] Jann F:
Is there even a dev still working on CM for our device?

I only see more and more things that need to be fixed :S

Will test nightlys and report issues, but it's pretty much frustrating if it isn't heard by anyone...
[Nook HD, HD+ Android Development] TheDannemand:
drmarble, spd_rcr and Zippy Dufus all seem to have affected it positively when the pipes got clogged building our nightlies due to some Nook specific issue.

And thanks a lot for that guys. It IS being noticed!
[Nook HD, HD+ Android Development] Mike The Menace:
Question: I've owned a Nook HD+ for some time now. Up until now I've been running the Stock / CM 10 Hybrid set-up where the cyanoboot menu would always present me with an option to boot into stock or CM 10. Following the directions in this thread, I originally attempted to just download the updated CWM zip and update the recovery and install the CM 11 zip, however I received errors every time. I tried installing from internal memory and SD but neither worked. So I took the microsd card I used for the initial install, re-formatted it and wrote the emmc-cwm-early3.1.img to the card which allowed me to boot into CWM, install the CM 11 zip and gapps. I removed the microsd card and rebooted and now I get no option to boot stock, the Nook automatically boots CM 11 but wont go past the initial CM 11 boot screen. What did I do wrong? Do I need to wipe the Nook completely and start over? Can you dual boot Stock and CM11? Any help is greatly appreciated!
[Nook HD, HD+ Android Development] PMikeP:
6/15 so far, so good

I said earlier in this forum that I would wait until the CM team incorporated 4.4.3 into the build before trying CM 11 again.

Well, I don't know how they got all 7454 changes incorporated in a month, but since they say it's now 4.4.3, I tried it yesterday.

I installed the 6/15 nightly. (And 4.4.3. micro gapp.) Heretofore, I've been running 10.2.1 stable with the fuzzy kernel.

It's only been a day but it seems faster and benchmarks a little faster. (Dalvik.) My aviation apps don't crash. The WiFi list doesn't seem to forget who's in range. Bluetooth works "better." (I use a Bluetooth app to pick up GPS from a Tom Tom. It usually took a reboot to get the app to talk to my aviation maps in 10.2.1.)

The screen still flickers when I'm charging the battery. I still think it's related to the animation of the battery "icon" text while charge. (I remember seeing something about the screen flicker here in this thread. Something to do with wall paper. I'm running a stock static CM wall paper. Nothing fancy. No scroll.)

No zRam or KSM in the Performance tweaks. (The author of zRam-settings says zRam is a thing of the past.)

I tried ART at first, before I installed my aviation apps and it worked fine. But since I didn't want to be experimenting in flight, I decided to play it safe and returned to Dalvik.
[Nook HD, HD+ Android Development] tebra:
About the screen flickering during charging, I thing it's a bug into the HD+ kernel. I have now a HD from 2 months and never had screen flickering with cm11
[Nook HD, HD+ Android Development] Mike The Menace:
So I decided to start from scratch and do a factory re-set on my Nook. I was able to boot into CWM off the initial emmc-cwm-early3.1 recovery img I wrote to a microsd card. I copied the cwm-recovery-ovaition-6, CM11 6/15 nightly and pa-gapps-mini and flashed them and successfully booted into CM11. My question is can I still boot into the stock Nook OS or did I wipe the Stock when I decided to flash CM11? If dual booting is still possible, can someone point me in the direction of the correct recovery and/or procedure? Thanks.
[Nook HD, HD+ Android Development] leapinlar:
This thread puts CM11 on internal memory replacing stock. If you want to dual boot you need to put stock back on it and CM11 on SD.

To put stock back go to my HD/HD+ linked in my signature and make a bootable CWM SD per item 1a. Use that to flash a plain stock zip from item 6 followed by a factory reset.

Go to this thread to install CM11 to SD. Then you can dual boot:

http://xdaforums.com/showthread.php?t=2583952
[Nook HD, HD+ Android Development] PMikeP:
On battery life

I've only had 6/15 nightly running for a day now. No night and day difference in battery life that I can tell. (It might be that CM 11 is slightly better, although I'm about to contradict my own statement.)

But I notice that, unlike my tweaked CM 10.2.1, where I could get something like 20% "Tablet idle," I only get a few percent now, with Google Play Services eating up battery.

One of the things I found is that the CM 11 cLock widget wants to query my location all the time. I don't know if the old CM 10.2.1 clock did that too. (I have "Locations" set to off, but that doesn't seem to stop Google gapp stuff from trying.)

Anyway, in addition to using the free app "Disable Service" to kill off a lot of Google Nlp location sniffing stuff, I found that you can also click on "Enable Privacy Guard" for the cLock app and then disallow it from requesting your location.

Suddenly "Tablet idle" has jumped back up into the tens of percent.

(I don't use the HD+ for email or messaging. Mostly just for web browsing and for moving map apps in an airplane. So, for example, Wi-Fi is off when the screen is off. So my tablet really is idle when the screen is off. My goal is to get "Tablet idle" to reflect that reality.)
[Nook HD, HD+ Android Development] LucaToo:
If you don't mind me asking - what app would that be - as it would be most useful on a 16-hour drive across Europe..?
[Nook HD, HD+ Android Development] PMikeP:
Bluetooth GPS tether client

It's called Bluetooth GPS.
[Nook HD, HD+ Android Development] pnkpig:
so if I have installed a CM11 nightly and now I want to update to a newer version, I need to reboot to recovery and flash the new nightly zip only, am I right?
[Nook HD, HD+ Android Development] digixmax:
Yes.
[Nook HD, HD+ Android Development] TheDannemand:
If you're using PA Gapps from the last month or so, then note that due to a bug in its addon.d script, you may need to flash Gapps again after updating the ROM. Should be fixed in the next PA Gapps update.

Not everybody is affected, see note from TKruzze (the Gapps dev):

http://xdaforums.com/showthread.php?p=53480881

I personally always wipe /system then flash both ROM and Gapps when I update, so haven't experienced this myself.
[Nook HD, HD+ Android Development] PMikeP:
This happened to me, although I didn't use the gapps removal tool. I had a small problem with my first install of CM 11 6/15 nightly. (I removed one too many apks and the Home button didn't work anymore.) So I reflashed the ROM after having gapp micro installed.

For some reason, Play wouldn't work after that. (I did the usual delete cache, delete data stuff. N/C.)

So I had to reflash gapp micro.

Now, it could be the script problem mentioned above. Or, it could be that I had integrated a newer version of Play Services into the system ROM via a feature of Link2SD. Or both.
[Nook HD, HD+ Android Development] PMikeP:
It's 4.4.4 now

I just flashed/updated to 6/21 nightly. It's reporting as version 4.4.4.

Everything seems to be running well.

I don't use VPN, but I saw someone else in this thread complaint that VPN was broken. I saw a line in the change log that it's been fixed.
[Nook HD, HD+ Android Development] jbbandos:
Thanks, I was the one posting the VPN issues, will check if it is really fixed now.

Edit: it is fixed now, thanks for the hint.
[Nook HD, HD+ Android Development] PMikeP:
Sleep of Death

I have had two occurrences now w/ the 6/21 build where I cannot wake up the HD+. It's as though none of the buttons work. Not even the Volume buttons. (I was listening to a podcast during one event.)

To be fair, I disabled cLock and a few more other services in the gapp stuff since the 615 nightly.

Anyone else having SOD issues with this build?
[Nook HD, HD+ Android Development] PMikeP:
Fuzzy kernel clogs up CM 4.4.4

I've been getting ghost touches since moving from CM 10.2.1 and the fuzzy kernel to CM 11 6/15. So I decided to try Succulent's fuzzy kernel for CM 11.

It didn't work. Wouldn't boot. (Well, wouldn't get past the boot loader. Never got the animation.) Worse, a simple restore of the /system partition didn't fix the problem. I had to do a full wipe and restore.

Since then, I set the touch sensitivity to Medium as a workaround under Accessibility.
[Nook HD, HD+ Android Development] rhyang:
Looks like a location fix is coming -

http://review.cyanogenmod.org/#/c/66314/
[Nook HD, HD+ Android Development] excalibar001:
Installed 0624. Location lock is working in Google maps. Everything works smooth so far. Will report if I see any problems .
[Nook HD, HD+ Android Development] rholm:
Very cool. Will try tonight. I'm on the first 4.4.3 build. Anyone know if the excessive process killing is fixed? BBS and LMT are constantly restarting on my HD+.

Cheers,

Rich
[Nook HD, HD+ Android Development] angelofmenoth:
That kernel was built in April from the look of things. Nothing after 6/1 is going to boot with that. Same goes for almost any KK rom and kernel after that point, not just here in HD+ land.

I'm running 6/21 now, and I'm not seeing any issues. Downloading 6/24 now, actually. The last few days have had some really stable, smooth builds.
[Nook HD, HD+ Android Development] rhyang:
Installed 6/24 last night. SOD this morning, could not wake the tablet, had to power-cycle. Also saw something like our old friend the systemui crash last night. Nightlies are like that :)
[Nook HD, HD+ Android Development] PMikeP:
I've been running 6/23 for two days now. No SOD's so far. I even switched to ART last night.

---------- Post added at 04:50 PM ---------- Previous post was at 04:44 PM ----------

Yeah, I think the CM devs are converging on a solution. We should be really thankful they do all this for free.
[Nook HD, HD+ Android Development] rholm:
06/24 has been solid all day for me. I will report if something happens.

Cheers,

Rich
[Nook HD, HD+ Android Development] JimJ2Mz:
Hm. What first?

It's been a while and I decided to make the jump back to CM (wow what a rom hopper lol).

I kind of forgot what goes first- install rom and enable ART right after or install rom + all your own apps and then enable ART?
[Nook HD, HD+ Android Development] Darrian:
Maybe this has been asked already, but is there any chance we'll get F2FS support?