yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] verygreen:
Hm, this one is a crash in wifi driver, either mmc controller or the wifi controller wedged up so badly that the kernel was not able to even get a dump from firmware.

And in trying to shut it down there was apparently a bug in that codepath (I imagine nobody tests uncommon error paths).

This could have been influenced by parallel sdcard io that we do know is not exactly super reliable on our hardware.

Likely there is nothing I can do about it in the short term.
[Nook HD, HD+ Android Development] :
nvm... :)

I just did a clean install this morning with only two apps installed and barely any setting changes. None thus far but it can take some time sometimes.

no SD, just normal use.

WiFi it could be here too perhaps? Dont know anything about this stuff.
[Nook HD, HD+ Android Development] verygreen:
If it keeps booting into twrp, that likely means the bootloader cannot find some essential part somewhere (did you erase /boootdata content by any chance?)

Cannot mount /boot message, I do not think I have seen, since the system is not supposed to mount /boot as it's not a filesystem.

The /bootdata warning is actually harmless because there's no /bootdata dir somehow. Can you use adb?

boot into twrp, do adb shell and there

mkdir /bootdata
mount /dev/block/mmcblk0p6 /bootdata
ls /bootdata

Also worst comes to worst you should be able to flash stock 2.1.0, boot that then reflash back to cm
[Nook HD, HD+ Android Development] gomavs123:
Gapps crashing (update applied)

hello guys, I have been using the emmc with no problems, but starting from a week ago, gapps started to crash on me with no reason, every time. When I click on the app, it crashes right away with no warnings. When I restart the device, it comes up with "unfortunately, gapps... has stopped" message. I even tried applying the gapps and updated the emmc to the most recent version as well.

Any help will be appreciated! thanks.
[Nook HD, HD+ Android Development] xdatoast:
Thanks again for this fabulous rom.

One question : is there a way to check for and install the nightly updates thru the settings? When I check for updates, it says there aren't any?

Thans
[Nook HD, HD+ Android Development] verygreen:
This only works for official CM ROMs. I am still waiting a response from CM HQ on inclusion of our devices into mainline.
[Nook HD, HD+ Android Development] verygreen:
New twrp recovery image for installation to emmc: twrp-recovery-ovation-4.zip

Updated to twrp 2.6.0.0. (Seems to results in a bit less of UI lag)

No more nagging /bootdata error messages when installing roms.

Applied touchscreen sensitivity adjustment.
[Nook HD, HD+ Android Development] jamus28:
Is there a danger to flashing the recovery image from inside an internal recovery? eg emmc cwm to twrp? Will it overwrite on reboot fine?
[Nook HD, HD+ Android Development] verygreen:
works well for me.
[Nook HD, HD+ Android Development] Óðinsdagr:
Only issue I've had on other devices going from CWM to TWRP is loss of previous backup compatibility
[Nook HD, HD+ Android Development] Wolfkmann:
Is there a touch version of cwm for our nook hd+?

Sent from where ever I currently am.
[Nook HD, HD+ Android Development] monkey3ddd:
Kudos man, love twrp, repped if I can.. I love this tab, thx to the awesome work of the devs.
[Nook HD, HD+ Android Development] rushless:
Very,

Is there a patch or "simple" way to move the navigation bar buttons over to the left, rather than the middle?

Also, can anybody recommend a short cut app so I can set up icons to quickly launch both the triple tap zoom function and full screen mode? Drop 7 needs the triple tap or tiny window and would be nice to quickly trigger full screen mode. I had a third party full screen app, but it seemed to be too intrusive.

Added: I was tempted to try Carbon, but all the extra stuff seems likely to have extra issues. I still do not understand how it could be faster/smoother if using the same kernel. Seems the real bottle neck is the 1080p resolution more than anything else, so lag would be a some level of a factor, regardless of rom.
[Nook HD, HD+ Android Development] stephencwl:
Just enable "Expanded Desktop" and you can easily trigger the full screen mode using the power button.
[Nook HD, HD+ Android Development] king200:
You can use Nandroid Manager in order to use either the TWRP or CWM backups.

https://play.google.com/store/search?q=nandroid+manager
[Nook HD, HD+ Android Development] gomavs123:
i would like to bump my question.. I am still at a loss as to how to solve this issue- any place to look for and/or advice will be appreciated! Thanks.
[Nook HD, HD+ Android Development] leapinlar:
You bumped this question. I did not try to answer because I did not understand the question. What gapps app are you talking about? Play Store? Or something else? As far as I know there is no gapps app.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] infra_red_dude:
A big thank you to verygreen for the ROM! I installed the 7/6 version. However the About Tablet says its 7/5 version. I assume that's a typo?
[Nook HD, HD+ Android Development] verygreen:
The final build was 20 minutes before 7/6 my time, but the build system assumes GMT as the base.
[Nook HD, HD+ Android Development] benengyj:
The only thing I erased was via the "Erase Dalvik/Cache" button in TWRP after updating.

Currently ADB isn't detecting the device either.

Thanks for your help!

EDIT: Ok...tried clearing /data and it didn't help but it's now working after reinstalling 2.1.0 and then reinstalling CM. Thanks everyone!
[Nook HD, HD+ Android Development] stephencwl:
Great to hear that.
[Nook HD, HD+ Android Development] bpaulien:
I've been using the carbon ROM for the last couple weeks and am considering coming back to CM10.1. I think you are right about all the features making it a little less stable. I don't really like the PIE launcher because it interferes with normal swiping around on the screen, pulling up random apps as you are trying to get something done. I like the concept of HALO but its implementation seems a bit flakey, and I disabled it. I do like how easy it is to change the DPI of the device on carbon, but I can do that in CM10.1 with a little extra effort.

All things considered, I think CM10.1 is a better choice for me right now.

EDIT: rebooting now to flash the new version of CM10.1 :)
[Nook HD, HD+ Android Development] gomavs123:
Oh can I not bump my own question? Sorry if that wasn't allowed.

As for my issue, it is simply the play store app- it was working fine up until a week ago, then every time I try to start it, it crashes (not even a crashed message). When I restart the device, it shows up with a message that the program has stopped working. I tried updating as well to the most recent version, but it didn't help.
[Nook HD, HD+ Android Development] al mon:
On 7/6, random reboots frequently after waking the device. On reboot, the device freezes on the cm logo. Hit power, and vit continues to the UI but with a error saying system UI crashed.
[Nook HD, HD+ Android Development] gharlane00:
Clear cache and data for the playstore and google play services apps.
[Nook HD, HD+ Android Development] gomavs123:
I would think that this reply was in response to my question? (If not, I wanted to reply since it seemed to be relevant to my question). I have actually tried clearing cache and data for all of it like said here, since it was suggested in an earlier thread, but to no avail.
[Nook HD, HD+ Android Development] leapinlar:
It is allowed to bump your own question. I was explaining why I did not respond before. I assume that is why others did not respond, they did not understand the question.

Like the other poster said, you need to clear out the data stored in Play Store and goggle framework. It is probably corrupted. Go to settings, applications, and all, then clear cache and data for those two apps.

EDIT: If you already tried that, you must go to CWM and do a factory reset. That should fix it. You will lose all installed apps though.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] Óðinsdagr:
Was unaware of this app, thanks for the heads up
[Nook HD, HD+ Android Development] gomavs123:
Thanks for the help, and sorry about the confusion!

I was hoping there was a way to avoid the factory reset, but I guess I will have no other choice at this point. Thanks for the help!
[Nook HD, HD+ Android Development] verygreen:
Please capture /proc/last_kmsg after the crash, also logcat after systemUI crash.
[Nook HD, HD+ Android Development] jfenton57:
Stumped

Every time I try and write the BOOT image to any one of 4 different micro SD cards on my Windo9ws 7 machine, once it says it is successfully written to the card, I can no longer access the card on my computer to put the other zip files on it. Each time, my computer wants me to format the card?

Suggestions?
[Nook HD, HD+ Android Development] verygreen:
Did you try to follow this excellent guide to the letter? Make sure you are unzipping the image before writing and you are writing to entire device, not to just one partition.
[Nook HD, HD+ Android Development] jfenton57:
Yes.

Download ovation (7-6) to my pc. Unzip the file.

Using the Win32 disk manager (as administrator) I write the BOOT file as an image file to the SD card (I simply select the H drive as that is what Win32 disk manager offers.

It only takes 10 seconds to write it (this seems kinda short?) and instantly, the SD card / H drive disappears from "my computer" in Windows explorer and no matter how many times I remove and reinsert, reboot the computer., etc. each time I am advised that I need to format the drive and there is no way to look at it's contents, add any files, etc.

If I am writing to what Win32diskmager shows as the "H" drive, am I by default writing to the "entire drive"?

The message states that the drive does not contain a recognized file system.

Patient, but frustrated that I can't figure this one out.
[Nook HD, HD+ Android Development] verygreen:
This is totally not like what the instructions tells you to do.

You do not need to unpack the cm10.1.zip file at all.

You need to write cwm image to the sdcard, so I would advise you to reread the guide.
[Nook HD, HD+ Android Development] jfenton57:
Will go back and read it again. I even made notes but maybe I am brain cramping.

I shall report back.

---------- Post added at 09:23 PM ---------- Previous post was at 09:22 PM ----------

Following this to a "T"

From the thread which you cited...

"Make bootable SD card

. Download the correct files for the Nook you have. Files specific to the HD+ are named 'ovation'. Files specific to the HD are named 'hummingbird'.

. Unzip boot image file; it'll uncompress to a 4GB image file.

. Install & run Win32DiskImager. Use it to write the 4GB image to SD card. Wait until done. (Mac OS X users refer to http://xdaforums.com/showpost.php?p=43335741 for a media imaging tool.)
[Nook HD, HD+ Android Development] leapinlar:
You are unzipping and burning the wrong file with win32diskimager. He says unzip the boot image file (that means the NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).zip), not the ovation (7-6) zip.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] jfenton57:
Aaaaah.......interesting because the CWM file I downloaded from the thread is a 6+ GB file. The ovation file is just over 4.

I will re-download the CWM file and see if that works.

---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------

Actually, the CWM file in your thread downloads the following file...and it extracts to over 6GB

cwm-recovery-ovation-2

I have an HD+...not an HD

Note: I also have just tried to write the TWRP recovery and the same thing happens. Takes 3 seconds to write it and the moment it is completed the card dissapears from the windows directory and reinserting it calls it to be formatted.

I have tried this both on my Windows 7 desktop and my Windows 7 laptop.

I am probably screwing something up nut for the life of me, I can't figure out what.
[Nook HD, HD+ Android Development] leapinlar:
That is still the wrong files to be burning to SD. Burn the one I told you to burn. (And what is CWQM?)

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] jfenton57:
I will be humble and assume I am royally misunderstanding :)

I would happily burn the exact file you noted...but where do I find it? The link in the native emmc thread doesn't point to it but rather the CWM 2 zip file I noted.

---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------

Did a search and found that exact file in another thread.

Will try this again and update.

Thanks for your patience!
[Nook HD, HD+ Android Development] verygreen:
you can also try the file noted in the OP: http://nook.rootshell.ru/hd/emmc-cwm-early2.1.img.gz
[Nook HD, HD+ Android Development] leapinlar:
That referenced thread you were quoting had a link to that file. It told you to download and use it.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] jfenton57:
OK...this time it worked. This could save some others some grief perhaps if the original emmc installation thread by evergreen were updated to point to the 5/13 issue of the CWM file rather than the one it is currently pointing to?
[Nook HD, HD+ Android Development] leapinlar:
He did point you to the Dummies guide which has clearer instructions.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] verygreen:
New binary snapshot: cm-10.1-20130708-UNOFFICIAL-ovation-emmc.zip

This time there are no changes from me, but upstream CM merged ntfs and exFat support which seems to be a popular feature.
[Nook HD, HD+ Android Development] e.mote:
[MENTION=3654172]verygreen[/MENTION]

Since TWRP automatically checks for MD5 if an MD5 sig file is present for zips to be installed, can you start including MD5 sigs for the downloads? Corrupted zips seem to be a common problem next to SD booting, and having TWRP rejecting bad zips would help minimize bad installs.

BTW, I appreciate the breakneck pace of release. Everybody is (should be) happy. Hope you take some time off and enjoy the summer.
[Nook HD, HD+ Android Development] stephencwl:
Great to hear that! However, I just ordered an 32 GB card instead of 64GB just because of the previous FAT limitations.
[Nook HD, HD+ Android Development] verygreen:
well, bummer. The 3rd party zips were available for a while, though.

Here's hope wherever you bought it from has a liberal return policy.
[Nook HD, HD+ Android Development] williamlaw:
since tried 07/07 version, pull down notification menu and swipe in app drawer (between app and widget) with lag.

less lag in 07/08 version ??

thanks
[Nook HD, HD+ Android Development] stephencwl:
Thanks for the feedback. I know those zips exist but really hesitate to flash and mess up.

BTW, just pop in an 64 GB exFAT (from my phone) into 0708 and it works really well in our HD+ now. Gonna leave that 64 GB card in my sweet HD+ for super full HD movies though.
[Nook HD, HD+ Android Development] Rycon33:
I didn't noticed it before on previous nightlies so I am not sure it is suppose to be normal in CM, but the "charged" LED indicator is still in RED
[Nook HD, HD+ Android Development] jfenton57:
Not Running Smoothly?

Finally got this loaded on my 32 GB+. Not as smooth as I had expected run wise and no matter the browser, the internet is a bit unsmoothbin scrolling as are all the other programs.

Suggestions?
[Nook HD, HD+ Android Development] samomamo:
Change the DPI to 320 or 480 it will me smmoth. And go to developers settings and turn off all the animations.
[Nook HD, HD+ Android Development] BigMacca:
I've not played with the DPI settings yet, how does increasing the reported DPI improve performance?

Cheers

Macca
[Nook HD, HD+ Android Development] ilal2ielli:
It's like changing the resolution of a computer monitor. Less pixels to push, better performance.
[Nook HD, HD+ Android Development] Ogre6473:
But the DPI is currently at 240. Wouldn't raising it to improve performance be counter intuitive?
[Nook HD, HD+ Android Development] SCWells72:
I've also been struggling with the lag in both this ROM and the Carbon ROM. First off, let me say that raising the DPI does seem to help with smoothness of the UI, but at least for me, 320 DPI turns on the phone UI with no two-column view in Gmail, the launcher dock locked into portrait bottom (right side in landscape), etc. I found that 280 DPI is a good balance between a tablet UI and a smooth experience. So far I haven't run into any issues from that density, but it's possible there will be some fallout since it's non-standard.

I'm still hopeful for a kernel that can be overclocked to 1.7GHz in a reliable and stable fashion, but perhaps there's a good reason that won't ever come. I know that level of OC on the Touchpad makes a world of difference in silky smoothness with JB ROMs. Obviously the HD+ is pushing way more pixels than the Touchpad, but it also has significantly better hardware to do so...

I'll be interested to know others' tactics for getting the smoothest experience from the JB ROMs. I'm really wanting to make this a full replacement for my iPad 3, and aside from two apps that aren't working quite right yet (the Game Informer digital magazine app and Marvel Unlimited), the only thing holding me back is the lag that frustrates me after any length of use. Don't get me wrong, I TOTALLY applaud verygreen and killersloth for their amazing and selfless work on these(!!!), but obviously I'm not the only one struggling to achieve a smooth experience based on the content of these two threads.
[Nook HD, HD+ Android Development] Ogre6473:
First we need tweaks for stability. I have mine locked at 1.5 GHz right now because it is slow to adjust the clock when you need the speed. Also, being locked at that speed is giving me at least one forced reboot a day.
[Nook HD, HD+ Android Development] ilal2ielli:
That is something I cannot explain. Resolution and DPI seem to work differently in Android than it does in Windows.

Someone more knowledgeable than me may be able to clarify.

This link explains it a little though: http://www.androidtablets.net/forum/android-tablet-usage-tips-tricks/9444-lcd-density-explained.html

Although when I calculate the DPIs from that formula it still supports the opposite notion of higher DPI equalling more pixels.
[Nook HD, HD+ Android Development] Rycon33:
For some reason, my Google photos doesn't seem to sync with gallery app. Even though autosync is already enabled at sytem settings. Any suggestion on how can I resolve this is appreciated. TIA

Tapatalked from my bricked TX
[Nook HD, HD+ Android Development] verygreen:
Overclocking CPU does not make any sort of difference on gfx performance. Even overclocking GPU mostly does not (see my other post on this).

We seem to be bus bandwidth constrained there mostly, sadly L3 does not really want to run at 466Mhz stably enough to even finish booting.
[Nook HD, HD+ Android Development] rushless:
Compared to stock 2.1, CM 10.1 is FAR better, but still the lag exists. An example is when using Tapatalk. When activating the app, it can be over 15 seconds before you can navigate in the app. A gray bar with Tapatalk shows on top and that is it during the 15 or so seconds. It is better when in the app, but the lag is obvious. This is the first Android device I have had that does this. Seems nothing to do with DPI and something else going on (or not) that causes the lag. Dolphin is the same as other apps.

Again, the thing is when playing games there is not lag and this includes emulators or other games that use virtual controls. A good example is Zen Pinball. Play GREAT on the HD+ and no lag. The positive though is stock 2.1 not only has the same lag, but also has a LOT of stutter as well (in part due to the near constant library syncing).

Seems CM 10.1 itself is not the issue, since the exact same lag exsists with Nook stock 2.1. Game stutter goes away, but lag in the OS remains.
[Nook HD, HD+ Android Development] SCWells72:
Interesting. So I tried to do a little diagnosis over the weekend basically using CPU Memory Monitor (basically top as an app) and noticed two processes that were really chewing up CPU when things got sluggish, Media Server and Chrome. After googling the former a bit, I did two things to try to address it: 1) removed my Sandisk class 10 32GB uSD card; 2) deleted some directories that contained large numbers of files, in particular stuff left around by Gameloft games. As far as the latter, I did a little test and switched all of my browsing duties to the Browser app and noticed a significant decrease in lag and choppiness. That could very well be coincidental, or perhaps Chrome is doing something more CPU/GPU intensive than the other browser(s). Any thoughts on that?

Also, aside from monitoring apps while lag is actually occurring, any other thoughts on how I can contribute to this diagnostic process? I'm very happy to do so, but I don't want to spin my wheels or cause anyone to chase down red herrings because I'm looking at the wrong thing.
[Nook HD, HD+ Android Development] Jack45:
One of the selling points of this device is the sharpness of the display. I've left it as is and simply turned off all animations. Speed demon? No, but fine nonetheless.
[Nook HD, HD+ Android Development] Jd6J0r:
Wow, thanks! What a difference this makes. Feedly's tiny text is readable. And so is the tiny text in Android Settings menus.

I used Root Explorer to manually edit /system/build.prop (first change the mount to r/w) and changed this line (in the last section in the file, in about the middle of that section):

ro.sf.lcd_density=240

to

ro.sf.lcd_density=280

Then saved, exited and rebooted.

You can use the free ES File Explorer or, probably, CM's built-in file manager :)

https://play.google.com/store/apps/...id.pop&feature=nav_result#?t=W251bGwsMSwyLDNd

I also changed the Screen Text size in Settings -> Display -> Text Size from Enormous to Large (translating from Spanish here, so it may be slightly different words).

Verygreen: Please consider making 280 the default in your ROMs. It makes the HD+ a lot more readable, in my opinon.
[Nook HD, HD+ Android Development] bpaulien:
Hmmm.. I don't know if I've noticed that on TapaTalk... Although I'm using TapaTalk HD, so maybe that behaves differently than the other version? It's pretty quick getting in, and picking a forum I want to read on my HD+.

I set my DPI to 320, and am still trying to get used to it, and see if I think it's worth it. Things are easier to read, so that's a good thing, I guess. I'll keep it for a little longer, and see if it grows on me.
[Nook HD, HD+ Android Development] leapinlar:
Actually it is better to make the change to /data so it survives a flash of a new ROM.

Create a text file and name it local.prop. Copy it to /data. Add this text line to it:

qemu.sf.lcd_density=280

Then save it and reboot. It will override whatever is set in build.prop. That way when you flash a new CM10.1 ROM, it stays at 280.

But I personally like 320 since it matches my Galaxy Tab and makes more things in Play Store compatible than 280.

Sent from my Nook HD+ running CM10.1 on New SD
[Nook HD, HD+ Android Development] SCWells72:
First, there's an app called BuildProp Editor in the store that vastly simplifies changes like this.

As far as the default, I think that verygreen is staying with the standards for different device types which are 240, 320, etc., to keep things like the market working properly out-of-the-box.

Oh, and you can change icon size in Nova. At 280 dpi, I found that 85-90% looked great.