yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] jpisini:
Unfortunately the nook does have issues of you let the battery die this is a hardware issue no known work around. Try not to let it run out. Wish I had better information got you.
[Nook HD, HD+ Android Development] leapinlar:
That image is a corrupt connect_charge.ppz file in /bootdata. It is supposed to be a picture that says "connect your charger". It obviously thinks your charger is not attached. Try going to /bootdata and deleting that file to get rid of the corrupt picture. And try disconnecting and reconnecting the cable.

To get the correct image back you must flash a stock zip from my HD/HD+ CWM thread linked in my signature (item 6). But since you have CM11 and CWM v6045 or newer installed on internal memory, you must use a bootable CWM from my thread to flash it. And of course you lose CM11.

An alternative is to download the plain stock zip and extract the file from the zip and copy it to /bootdata. It is in /system/media there.
[Nook HD, HD+ Android Development] dougsdir:
no problem, so is this a general fault on any rom or just this CM11 rom?

I might consider switching roms if its just cm11

---------- Post added at 04:09 PM ---------- Previous post was at 04:06 PM ----------

thanks i'll give that a go!
[Nook HD, HD+ Android Development] pdx1138:
Ya, I had a HUGE scare when a version of HBO GO drained the battery all the way while in sleep.

It was the better part of 4 hours charging before the Nook HD+ would even turn on after being

fully drained like that.
[Nook HD, HD+ Android Development] RocketOptics:
It looks like it is being worked on. I've been following this

http://review.cyanogenmod.org/#/c/63806/
[Nook HD, HD+ Android Development] dougsdir:
I tried to copy the connect_charge.ppz to /bootdata using es file explorer but it says access denied. I am rooted as i have a hosts editor which requires root and that works.

Do i need to do something else?
[Nook HD, HD+ Android Development] digixmax:
Check Settings->#Superuser to see if ES File Explorer is listed as having super-user permission "allowed".
[Nook HD, HD+ Android Development] TheDannemand:
And make sure to enable Root Explorer under Tools in ES File Explorer.
[Nook HD, HD+ Android Development] erm1001:
Make sure enable root in ES explore and enable r/w

---------- Post added at 08:25 PM ---------- Previous post was at 08:22 PM ----------

Look like they fixed it http://review.cyanogenmod.org/#/c/64114/
[Nook HD, HD+ Android Development] TheDannemand:
That was in the old days. The last many versions of ES have a new UI where you just select Root Explorer ON or OFF under Tools.
[Nook HD, HD+ Android Development] Korgy:
Just as a an FYI, a good alternative to ES is Root Explorer.
[Nook HD, HD+ Android Development] RocketOptics:
Nice! and it looks like it's slated for the next nightly.

http://changelog.bbqdroid.org/#/ovation/next
[Nook HD, HD+ Android Development] digixmax:
Even with the latest version, you might still need to set the partition of interest to be mounted RW -- e.g., by default /system is RO.
[Nook HD, HD+ Android Development] TheDannemand:
Your post prompted me to look for that setting (which I remember clearly in Settings in the old ES) and it took awhile before I accidentally tapped Root Explorer (not the toggle, but the words) and saw it. I guess I haven't needed to edit System since I updated to the new version.

Thank you. I stand corrected!
[Nook HD, HD+ Android Development] Darrian:
I prefer Root Explorer over any other, but I'm not sure why anybody would need either file manager solely for this task when the built in CM file manager has root access and is also pretty fantastic.
[Nook HD, HD+ Android Development] leapinlar:
And the free Root Browser Lite.
[Nook HD, HD+ Android Development] Sherip:
I've been running the unofficial 1/18 version from sd card since it became available without issues. Suddenly I'm not able to use it at all. I think the issue may have been caused by an app getting auto updated but no idea which one. What happens is, it loops with an error something like "Unfortnately com.android.systemui has Stopped". It alternates the green leaf wallpaper (not my usual wallpaper), an absent (black) wallpaper, and the error message in rapid repeated succession. I never see the unlock mechanisms. I see my desktop icons but can't use them. I tried clearing caches but no change. I also tried reflashing the unofficial sd zip and gapps. I suspect clearing data might work but of course would rather not.

Sent from HD+ Running Rooted Stock 2.2
[Nook HD, HD+ Android Development] erm1001:
Installed 5-17. Seem to be working no more system.ui crash.
[Nook HD, HD+ Android Development] rholm:
Are background processes still being killed? LMT on my nook was constantly having to restart. I am back on 03/27/2014 and it's pretty stable. Only issue is I lose wifi passwords on each restart.

Cheers,

Rich
[Nook HD, HD+ Android Development] Hashcode:
This happens sometimes when rolling back to an older CM without wiping.

The only "fix" I've been able to use reliably is to tibu backup apps only, do the wipe and then restore.
[Nook HD, HD+ Android Development] mr72:
I tried that one, bootlooped for me. Back to the 5/12.
[Nook HD, HD+ Android Development] rholm:
I didn't rollback. I restored a backup. I might wipe and try a fresh install of a new nightly. What is the experience with the new nightlies?

Cheers,

Rich
[Nook HD, HD+ Android Development] spd_rcr:
I see a lot of people posting about boot-loop issues with roms that I've similarly installed without issue. I'd be curious to know how many of these actually happen with a real clean install and having checked the MD5 sum prior to installing ? Is it even supposed to be ok to dirty flash a rom if you've converted to art ?

A big thank-you to whomever is responsible for http://changelog.bbqdroid.org/#/ovation/next

Seems a great way to see quickly what's been changed in each nightly and deciding if it's something I want to upgrade to/flash.

fwiw, it might be handy to add a link to http://goo.im/devs/BaNkS/GApps/4.4.2 in the instructions. I always use the latest GApps-Minimal. Seems pointless to install some outdated version of GApps cluttered with crap (like the camera app) that we really aren't going to use on the Nook.
[Nook HD, HD+ Android Development] hallanthony:
Same thing's just happened to me :(, but like you didn't see which apps updated to know what app caused this trouble

And also like you just tried reflashing the unofficial zip and same error, also would prefer not to clear data - anyone else any idea what app could have caused the issue?
[Nook HD, HD+ Android Development] hallanthony:
So found out my recently updated apps, Amazon for Tables, Facebook, Juice SSH, Sky+ and Weather & Clock Widget

But unable to uninstall any of them as that just causes reboots :(
[Nook HD, HD+ Android Development] RocketOptics:
Been using 5/17 for over a day. No more crashes as well. 5/17 Nightly seems solid.

Left it over night, and notification bar was fine in the morning. It survives Candy Crush, Chrome, Newstand.

I had gone back to 4/8 nightly because of the notification bar issue. Now HW acceleration is also working in MX Player on this 5/17 nightly.

BTW, I wiped SYSTEM, DATA, and CACHE/DALVIK when I went back to 4/8. But only wiped CACHE/DALVIK when going from 4/8 to 5/17. Also using pa_gapps-stock-4.4.2-20140513-signed.zip
[Nook HD, HD+ Android Development] myherbalsurf:
Great Build!

I just updated my tablet to emmc 4.4 and am using the 5/17 build without ART and the software is great. Sure, I am having a few hiccups here and there with force closes, but, for the most part, the release is working great!

I just wanted to say thanks to everyone involved! You are doing a wonderful job and I appreciate it a ton!

Keep up the great work and thanks for keeping this device alive and well!
[Nook HD, HD+ Android Development] Darrian:
I am also happy to report the notification crash bug seems to be squashed, but now now RDIO will not open. It hasn't had an update and it was previously working fine, and no other app is giving me any trouble, so it has to be something with the ROM, possibly a by-product of recent bug fixes. Noticed it yesterday on 5/17, it's still doing it today on 5/18.
[Nook HD, HD+ Android Development] rholm:
I did a factory wipe and installed 05/18. Used TB to restore my apps and I don't think my nook has ever been this smooth and stable. Time will tell, of course, but right now I am very happy. Kudos to all that make this ROM happen.

Cheers,

Rich
[Nook HD, HD+ Android Development] Sherip:
I tried to rebuild the sd and reinstall my apps and ended up with the same issue, couldn't boot. Now trying to use Bokbokan's sd install and having issues there too.

Sent from HD+ Running Rooted Stock 2.2
[Nook HD, HD+ Android Development] digixmax:
You might want to try the CM11 SD build process described at http://xdaforums.com/showpost.php?p=49007593&postcount=84.
[Nook HD, HD+ Android Development] Sherip:
I resolved my issue on all my cards. A recent update to Flipboard was causing all the trouble. While booted to internal memory I mounted the data partition of each card and deleted the app. Also deleted the flipboard cache file. Then booted the card(s) and quickly started the play store to remove auto-updating from Flipboard. For the cards based on verygreen's unofficial cm 11, I also had to reapply my wallpaper (which had switched itself to green leaf). Haven't tried the latest Flipboard under Dalvik, only with ART.

This odyssey isn't over yet because I forgot a password (zinio) and their password reset doesn't work. My attempt to reset the password on the new cards has caused the original install with the original authenticated password to quit working. :(

Also, I did use the previous version of Flipboard a lot and I don't have a recent backup.

Edit: The previous version was still there. When I touched the Flipboard icon it was restored!

Sent from HD+ MAG2GA CM 11 from SD
[Nook HD, HD+ Android Development] hallanthony:
Thanks for the info, can't remember if Flipboard was updated recently - it didn't appear in my recently updated list, but I'll see if I can firstly work out how to remove an app, cheers Tony
[Nook HD, HD+ Android Development] jbbandos:
In have a strange issue with 5/17 and 5/18 with xposed. I was with M6 before, but just flashed this weekend 5/17 and now 5/18, to see if the notification bug is fixed. It apparently is, the nook no longer hangs when I pull down the notifications, but I still get some reboots from time to time.

However, that isn't the issue. The problem I have is with exposed, both the previous and the just released version. I can download modules, but the install button never shows up. On other devices this doesn't happen, and it didn't happen with M&, but on the nook, it happens with both 5/17 and 5/18, there is only a download button for modules, and I see in the notifications that the modules are downloaded, but I never get an install button.

Anyone else seen this?
[Nook HD, HD+ Android Development] ejstubbs:
That sounds very promising. Are locations services working? Last info I could find said they were still broken.
[Nook HD, HD+ Android Development] Sherip:
Here's some steps based on what I did while booted to emmc (where I have rooted stock):

Open ES File Explorer and activate root access and make hidden files viwable.

Browse to /data/local

Open Terminal Emulator. Execute the following commands:

su

mount -rw -t ext4 /dev/block/mmcblk1p3 /data/local/tmp

Then in ES File Explorer:

Browse to /data/local/tmp/app

View such that files are sorted by date

Select and delete the recent flipboard file

Browse to /data/local/tmp/dalvik-cache

Select and delete the recent flipboard file

In Terminal

umount /data/local/tmp

exit

exit

Shut down. Restart. sdcard should boot without error.

Sent from HD+ MAG2GA CM 11 from SD
[Nook HD, HD+ Android Development] hallanthony:
Thanks for the suggestion, I'm not running from an SD card, direct on emmc so I presume it will be a little different?

Must admit with the error re-showing straight after I dismiss the message it's a struggle to run any apps, let alone switch between them
[Nook HD, HD+ Android Development] Sherip:
You'll need to either use adb or make a bootable SD card. You probably won't need any mount commands, e.g., with the cm11 SD install in this thread you can access internal data from \int-data in a root browser like es file explorer.

Sent from HD+ MAG2GA CM 11 from SD
[Nook HD, HD+ Android Development] hallanthony:
Just to conclude my story, after starting to create a bootable SD card I saw your other thread and it clicked that I was also using the Art runtime (must admit it did cross my mind last night to try switching back) so I thought hmmm, lets try switching back and eventually after managing to switch back I now have a working system :good:
[Nook HD, HD+ Android Development] rholm:
I am not seeing this. I use Xposed, but still version 2.5.1. Did you upgrade to 2.6? I read in the XHFW thread that some are having problems with KitKat and 2.6.

I did a clean install of 05/18/2014 and my tablet hasn't run this well in a long time.

Cheers,

Rich
[Nook HD, HD+ Android Development] Sherip:
Glad you got it working. I couldn't get into settings when I had the problem. But I'm glad I can keep ART because it feels a lot more responsive on my SD installs.

Sent from HD+ MAG2GA CM 11 from SD
[Nook HD, HD+ Android Development] rhyang:
So far so good with 5/17. I'd had to reboot after the initial flash with some previous builds, but it seemed to work right off the bat with this one.

Obligatory disclaimer: Make sure to do a backup first though.
[Nook HD, HD+ Android Development] hallanthony:
Must admit last night after getting things back running I did feel that things were being a little sluggish - so perhaps I may try un-installing Flipboard and going back to ART just to see, thanks again for getting me going, well at least in the right direction :good:
[Nook HD, HD+ Android Development] huntz:
I'm coming from the stable (for me) M4.

Now I'm running for a couple of days cm-11-20140518-NIGHTLY-ovation.zip, with 5-15_GApps_Minimal_4.4.2_signed.zip.

The notification bug is fixed and all is working fine (except the Wifi Analyzer, no networks detected - btw I can live without it :p ). I'm not using ART.

Following the MD5 of the files I'm using:

c36b771ce86328a2551e77d9d776fde1 5-15_GApps_Minimal_4.4.2_signed.zip

f4f25853128c15bcf88c3d0f069a16f2 cm-11-20140518-NIGHTLY-ovation.zip
[Nook HD, HD+ Android Development] tebra:
I guess that location in Google maps doesn't work. It never worked for me on my HD and HD+
[Nook HD, HD+ Android Development] manojm:
Flashed 518 nightly on m6 a couple of days ago. Only problem I have seen is the battery drain is much faster than before! I am not using anything like ART, ADB etc
[Nook HD, HD+ Android Development] huntz:
The device has no GPS module, so it's getting the location from the Wi-Fi network name...

Usually I get the location on Google maps...
[Nook HD, HD+ Android Development] tebra:
I know that, but I don't get any location even with WiFi connection
[Nook HD, HD+ Android Development] Manwthgun:
Great write up and most things work great. But, I do have a few questions. Using USB Host it works fine on spinning drives but, not 3 flash drives I have. Any ideas?
[Nook HD, HD+ Android Development] jck_w:
I'm running the stable cm-11-20140518-NIGHTLY-ovation.zip as well however with the 5-16-pt2_GApps_Minimal_4.4.2_signed.zip gapps as I was unable to download the 15th before it got taken down. No location for me ?.

If yours works can you upload your 15th gapps?

Thanks
[Nook HD, HD+ Android Development] Blenky:
Has it ever worked?
[Nook HD, HD+ Android Development] clockworx:
Regarding Location Services, I found that it works on a clean install of CM11 nightly + Mini Modular PA Gapps, UNTIL I accept the suggestion to update to the latest google play services. Since I usually accept updates off the bat, it took me a while to figure out the issue. Apparently Hangouts doesn't want to work without the update, though, so I either lose Location or lose Hangouts.
[Nook HD, HD+ Android Development] tebra:
Yes with CM10.2 but I don't remember working with CM11
[Nook HD, HD+ Android Development] Manwthgun:
Still working on this but, an update. I have some older flash drive dell, SimpleTech, DiskGo!. They work though much smaller. When I connect my Patriot Tab CM 11 picks it up it asks me to view files in File Explorer. But, it never mounts the drive. Could it be a generic mass storage driver not assigning to the device? It is formatted NTFS but, I have tested other drives with different partitions including NTFS and they mount fine.
[Nook HD, HD+ Android Development] jbbandos:
Hi,

I finally tracked down the problem to a corrupt xprivacy database. Xprivacy was blocking xposed framework... :(
[Nook HD, HD+ Android Development] LucaToo:
I get no location now either. Used to work - not sure when it stopped.
[Nook HD, HD+ Android Development] rholm:
How are you guys checking for a location? I'll do the same test. Maps seems to know where I am.

Cheers,

Rich
[Nook HD, HD+ Android Development] digixmax:
I mostly use Maps -- hitting the location icon would yield "Waiting for Location ..." then nothing.
[Nook HD, HD+ Android Development] tebra:
Exactly my problem on Google maps
[Nook HD, HD+ Android Development] rholm:
I have the exact problem. When I open maps, it takes me to my home and that's it. I can move around, but no finding my current location. I think this used to work.

Cheers,

Rich
[Nook HD, HD+ Android Development] Darrian:
So, um, yeah. Apparently RDIO crashing was caused by Xposed, not the ROM. That's fixed now, too. Yay!
[Nook HD, HD+ Android Development] tebra:
Thank you for this information about location bug linked to google play services.

But PA Gapps page wright this:

So we can't prevent upgrade of google play services. Maybe the one push to Nook HD/HD+ has a bug with location service.
[Nook HD, HD+ Android Development] huntz:
5-15_GApps_Minimal_4.4.2_signed.zip uploaded here: https://app.box.com/s/mwob2w26xvdoacznsv6i

If sometimes you see "Waiting for Location ...", try to disable and re-enable the Location switch in the Settings.

Good luck!
[Nook HD, HD+ Android Development] NishantM:
Location has magically started working now. I am on M6, and didn't do anything to fix it.

Google Maps location is still working when it wants, i.e randomly. But other apps like Beautiful Weather widget etc which was not showing geolocation is now properly detecting it.

Edit: Spoke too soon. Stopped working after a reboot. Seems like a minor issue.
[Nook HD, HD+ Android Development] tebra:
Hi [MENTION=3654172]verygreen[/MENTION]

Did you know that last auto build of CM11 for HD+ and HD failed?

No now build after 2014-05-21
[Nook HD, HD+ Android Development] spd_rcr:
Looks like a floodgate worth of commits waiting to happen as well.

Who is responsible for all the work on the nightly Ovation/Nook HD+ builds ? I feel like I ought to be buying them a beer or two at the least for all their work making the HD+ a killer functional tablet (vs. the stock ROM that made me just want to kill the tablet).
[Nook HD, HD+ Android Development] Darrian:
Maybe I'm late to the party, but I was just messing around with 5/18 (I got some weird error saying I had a UID mismatch and needed to wipe my data partition, so I did and now I'm setting it all up again) and I found there are a lot more options in the theme chooser now. Nice. I wonder how long that's been there.
[Nook HD, HD+ Android Development] Zippy Dufus:
Bad patch!

This patch is the problem: http://review.cyanogenmod.org/#/c/64558/1/tools/releasetools/ota_from_target_files,unified

I manually reverted it and now my build completed. (Unless someone slipped in a different fix while I was building.)
[Nook HD, HD+ Android Development] seattlecard:
Howdy folks - I am preparing to install CM11 on my stock HD+ ...

I checked and I do have the MAG2GA bad emmc chip.

Is it safe for me to roll with CM11 given TRIM is enabled? I've already lost one HD+ (sent back to BN), don't want to lose another. I
[Nook HD, HD+ Android Development] spd_rcr:
First I've heard about the MAG2GA.

Assuming this is what you're referring to, http://wiki.cyanogenmod.org/w/EMMC_Bugs#MAG2GA_TRIM_bug , it says not to use CM 10.2 Rom's prior to August 2013. I think we're well past that.

I checked my own device and it shows MAG2GA, rev.06, from 08/2012 and I haven't had any bricking of my device running 10.1, 10.2, or 11 nightly builds, but maybe I've just been lucky so far.
[Nook HD, HD+ Android Development] tebra:
I don't know how to do that, but somebody must inform CM team that this patch broke Nook HD/HD+ auto build.
[Nook HD, HD+ Android Development] tebra:
Here is the log of the last build bot in CM http://jenkins.cyanogenmod.com/view/All/job/android/70171/console

The build is aborted because of a "time out" during the "Package OTA" operation.
[Nook HD, HD+ Android Development] Zippy Dufus:
Yup, this is the same place where my build hanged.

And thanks for the link! Now I know where to go compare my logs to.
[Nook HD, HD+ Android Development] huntz:
Here you can read all you need to know:

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

Rev. 06 usually is a good chip, so no brick risks. From some months, anyway, the kernel on CM is patched to do trim safely with any MAG2GA chip.

Read the previous link for more details.
[Nook HD, HD+ Android Development] drmarble:
Fix build hangup

I wrote a patch (actually 2 but I abandoned the first thanks to Ethan Chen making a much more elegant solution possible) to fix the recent building problems. Just apply:

http://review.cyanogenmod.org/#/c/64788/ in device/bn/common

and Ethan Chen's patch:

http://review.cyanogenmod.org/#/c/64780 in build.

This fixes the build hangup when calling imgdiff (it doesn't call it anymore).

I hope these are merged soon so the nighllies can begin again.
[Nook HD, HD+ Android Development] tebra:
Thank you.

Will it be applied also to HD (hummingbird) builds?
[Nook HD, HD+ Android Development] drmarble:
Yes, this patch will also fix the hummingbird builds. Our devices share the bn/common directory and the build failure.

I hope it gets merged in soon. The wheels of cm turn in mysterious ways. It could be in an hour, it could be days.
[Nook HD, HD+ Android Development] Zippy Dufus:
Don't get too excited.

My cm-11.0-20140527-UNOFFICIAL-ovation.zip is not a banner build:

When not in use, the ratio of deep sleep:396Mhz is a bad 60:40. So the power drains quickly (5% in 4 hrs)

Somehow, it appears that the CPU governor was changed to Interactive from Ondemand. Don't know why.

Maybe related to the #2, I had a series of force-quits on the android.systemmui (if I remember correctly) which made it difficult to shutdow because it kept overlaying the poweroff panel.

At least the AnTuTu benchmark (13563) was one of my best ever.

I'm looking forward to the fixes being promoted so I can do a normal build without my manual intervention. I see more changes buffered up.
[Nook HD, HD+ Android Development] extrem0:
Was it a clean or dirty install?
[Nook HD, HD+ Android Development] Zippy Dufus:
Nice try ... but no cigar!

I thought the fix was promoted but my 06/29 build hung up at the same place. I'm pretty sure I saw it in this list before I started my build.

No worries. I'm patient and can work around it. Thanks for the fix!

I always do dirty flash unless it is a major jump in revision or version.

However, the good news is that I did another cm-11.0-20140528-UNOFFICIAL-ovation.zip "intervention build" (with my manually-reverted source file) and although it started with the 60:40 Deep Sleep:396 ratio, it has since settled back to a more reasonable 95%+ deep sleep level when idle. I haven't had any force-quits either.

I've noticed that it often takes a day or so for newly-installed ROMs to "settle down".
[Nook HD, HD+ Android Development] FirePsych:
Anyone found WiFi to be really slow on the May builds?

With my phone and Nook HD+ next to each other on the same network, I get about 1.5mbps down on my Nook and 40mbps down on my phone.

That was on the 5/22 build. I restored a 5/5 nandroid and had the same speeds.