yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Tom2112:
Thanks brusyev! That did the trick.
[Nook HD, HD+ Android Development] :
Already had it replaced with an upgrade to 32GB too :D

Now, time to see this ROM shine... finally.

Hope your not counting my older posts as the 1st... had a username change done.
[Nook HD, HD+ Android Development] mlovesu:
is it safe to install cm 10.2 with trim on sd card

i just got my nook hd+ from US. I wanted to know if it is safe to install cm 10.2 on sd card with trim enabled.
[Nook HD, HD+ Android Development] TeutonJon78:
I don't know if it works with the Nook. It's working with the ovation (HD+) builds. No reason it shoudln't work. It's just nice to not have to download a huge file each time you want to update. Plus, you can see the changelog right there and you can setup other zips to auto install as well (useful for reflashing the GAPPS so gmail doesn't get clobbered) and kernels.
[Nook HD, HD+ Android Development] starbright_:
Did I get it right? Forced Closes of Firefox are due to bad RAM?

I am suffered to. How could you know this is a hardware defect?
[Nook HD, HD+ Android Development] starbright_:
Have 2 questions to CM10.2 for our NOOK HD+

a) I would like to use Androids internal SIP function. But our version doesn't include a dialer. Can this be added?

b) On the other hand we have focal on our devices, but no camera to operate with. Does this make sense or are there features that as useful?
[Nook HD, HD+ Android Development] verygreen:
If it's only firefox (or any other, but single app) that's forcecloses, it's likely just a bad app.

On the other hand if all apps randomly crash and you have regular kerne lcrashes (you would see them as reboots in the middle of using a tablet), that might be pointing at a bad RAM.
[Nook HD, HD+ Android Development] sovanyio:
Is anyone having issues accessing the tab over adb in the 8/27 nightly? Tab shows that its in USB debugging but adb just doesn't see it.
[Nook HD, HD+ Android Development] monkey3ddd:
So I got the dreaded MAG2GA. i ran the "brick check" or whatever it is from the play store and it says everything is ok, even after a memory check. Problem is, my HD+ is super laggy. Would reverting back to 10.1 be helpful to me?
[Nook HD, HD+ Android Development] artesea:
The brick check is only useful if you are running the app on a Samsung Galaxy S2. The only purpose to using this app on a Nook is to get the make and firmware of the EMMC.

10.1 won't make a difference, unless you are willing to run with a kernel which allows trim to run, and then you have a risk of bricking the device.
[Nook HD, HD+ Android Development] Reed-Sternberg:
I get forcecloses in Hangouts (only in conversions when trying to type in chat mode, video calls come in just fine), I don't get many reboots (3-4 overall so far), and I had this issue in cm10.1 and KS's carbon rom (he uses your kernels I think). So is this my ram problem (since I have not seen anyone else complaining about this, and I don't think Google hangouts is badly coded either!)
[Nook HD, HD+ Android Development] :
To simplify it further: Nothing stopped the reboots.

Though, heavier app usage tended to trigger it faster, yet not always. It could still hit 10 minutes or an hour in from a good boot. Many times one a day with three a day possible too (testing more or less caused it to be lower). Probably other signs as well - though not 100% sure just yet.

If suspecting, It might be best to reinstall stock, factory restore, update to latest stock version (if not already). And test. Should go back to stock and factory restore anyway to take it in.

But... still testing this new one. Solid as a rock so far.
[Nook HD, HD+ Android Development] monkey3ddd:
Guess we now know why B&N were trying to dump these :)

Do we ave any recourse? Return or exchange?

right now I'm working on going back to rooted stock and Nova Launcher. Hopefully that will get me enough mileage until the new 10" Nexus is released.
[Nook HD, HD+ Android Development] pdx1138:
??

no lag issues here.

10.1 runs great on my HD+ (7/19 build)
[Nook HD, HD+ Android Development] Jack45:
Problems shared in this forum are not universal. The "dumping" relates to B&N overstock due to lack of demand, primarily because the device didn't originally support Google Play. The reduction in price is not related to lack of quality.

Regarding returning your HD+ or exchanging it, speak with the retailer you purchased it from. Different policies for different outlets.
[Nook HD, HD+ Android Development] freecity:
Intermittent - can't get past the lock screen

This ROM is generally running great and I'm getting few random reboots and no reboots to the Nook OS, but I am having a problem once or twice a day when waking up the tablet. When I press the power button the lock screen displays but when I swipe to unlock it goes back to a black screen. Pressing the power button again brings up the lock screen again. There seems to be no way to get past this besides powering off the tablet and rebooting.

Is anyone else having this problem?

How can I pull a logcat when this occurs? Would one pulled immediately the tablet is rebooted be of any use?
[Nook HD, HD+ Android Development] kmika:
have a 32G device with mbg4ga 8/27 nightly installed with fstrim kernel since fstrim the device fast and much more stable only rare reebots...
[Nook HD, HD+ Android Development] leapinlar:
It is your magnetic cover. Just open the cover twice to unlock it.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] razholio:
That depends. If you boot from the external SD card, and don't mount any partitions on the eMMC, then you'll be fine. However, you also won't benefit from the trim-enabled kernel as SD cards don't do trim.
[Nook HD, HD+ Android Development] monkey3ddd:
I was just kidding about the dumping, I know this market of e-readers is risky. Not sure what best buy will do if anything.
[Nook HD, HD+ Android Development] kmika:
running emmc version of course.
[Nook HD, HD+ Android Development] razholio:
of course. ;) There is a good chance you'll be ok with the TRIM-enabled kernel, though you do have an eMMC part that is confirmed vulnerable, and the current 'fix' in the trim-enabled kernel has not be verified on the nook. It's still possible that you could brick it. If you don't mind going through the warranty process, you could join the few of us who are currently testing this. I think there's at least one of us with a 16GB model currently testing.
[Nook HD, HD+ Android Development] RichMD:
The fault is only evident if you try to run FSTRIM with Android 4.3 - correct? If 4.3 isn't officially supported by the tablet manufacturer we would need to manufacture a different reason for the return - correct?
[Nook HD, HD+ Android Development] brusyev:
I noticed the same issue after installing magnetic cover on my Nook. Can this issue be fixed eventually?

---------- Post added at 01:26 AM ---------- Previous post was at 12:35 AM ----------

Do I need to run some commands to kick off trim optimization with this kernel? Or simply installing it is enough to enable it?
[Nook HD, HD+ Android Development] m509272:
Good install but feeling stupid. Have a 64GB sdcard in there. Does anything make use of it automatically e.g. Play Music, Maps, etc or do I need to put stuff in there by myself?
[Nook HD, HD+ Android Development] leapinlar:
You have to do it manually. If you want to use it automatically, use my SD swap zip from my HD/HD+ CWM thread linked in my signature. See item 4 there. But I am not exactly sure it works well on CM10.2. But it should.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] darkcurrent:
If I want maximum stability, would I be better off with CM10.1 or CM 10.2?

thanks
[Nook HD, HD+ Android Development] Azurael:
There have been reports of occasional soft reboots in 10.2. Funnily enough, I experienced those once or twice a day in 10.1 and haven't had any in with 10.2... It seems to be device specific as to what's mores stable but I'd call both 'daily drivers' for most!
[Nook HD, HD+ Android Development] starbright_:
How do you update? Manually, or with Buildin updater?

Is it really necessary to wipe cache/dalvik/fix permissions - as I guess the intention is, that this is running automatically (which doesn't right now, as it doesn't find the download path...)

Can this be fixed?

---------- Post added at 02:26 PM ---------- Previous post was at 02:21 PM ----------

Regarding delta upgrade:

Yes, have a NOOK HD+ as well. But the update itself seems not to work. I guess first of all due to wrong path (same issue with the Setting/About Tablet/Update Cyanogenmod).

Nevertheless it seems not to give me the chance to search for the correct path and reboot...

Again the question here - how can this changes, is Wipe of cache/dalvik/fix permission needed? Or can this be part of the update itself as (hand over parameters like also the name and location for the update.zip is handed over) ?

Many questions ...
[Nook HD, HD+ Android Development] Sherip:
Sadly I'm getting a lot of hard reboots. I leave my nook charging with its SD install of 8/22 CM 10.2 and when I come back its showing the CM 10.1 I have on emmc. When I reboot, it goes thru the lengthy process of rebuilding cache/dalvick. Tedious.

Sent from my HD+ Running CM 10.1 from emmc
[Nook HD, HD+ Android Development] TeutonJon78:
I've only updated using CyanDelta (using TWRP) and I've had no problems with paths or anything. CyanDelta stores the ROM in it's own directory and flashed it from there. I've had zero problems with it (other than gmail being removed and needing to flash gapps each time, but not CyanDelta's issue).

Is you're using CWM, maybe that's the culprit.
[Nook HD, HD+ Android Development] SCWells72:
I posted this in the help forum, but I realized I probably have a better chance of getting a lead on a solution here. I've been running CM10.2 on my HD+ but started running into issues that I felt may be related to CM10.2 not working with fix permissions properly, primarily FCs in apps that didn't FC previously, keyboard wonkiness, etc. I had a nandroid backup of CM10.1 and restored that. Everything went fine there, and the Play Store spent a good ten minutes updating all the apps that had moved on since I made that backup. About an hour later I went to turn on the HD+ and it didn't turn on. I tried all the standard solutions...press home and power a few times to wake it up, close and re-open the smart cover in case it's the smart cover issue with CM10.x, hold down power for ~10 seconds and then press power again to reboot the device, hold down power + home for 25 seconds to initiate a hard reset...none of which did a thing. Still just a blank, black screen.

My device reports an emmc of 0x000015 and MBG4GA and I have been using LagFix, so my guess is that I actually do have one of the bad emmcs and just happened to get away with it for several weeks, but eventually it caught up with me?! If that's the case, is there anything I can do at this point? If that's not the case, any thoughts on other things I might do to resurrect it? Should I try for an exchange with B&N Support?

Thanks in advance for any thoughts on the matter!
[Nook HD, HD+ Android Development] brusyev:
Once you flash the trim enabled kernel does it run trim automatically or do we need to run some kind of command?
[Nook HD, HD+ Android Development] cfli1688c1:
recently, i have notice that i have to press the power button a couple of time before the screen would startup. Has anyone notice this problem? I am on the 8/22 10.2 build. thanks.
[Nook HD, HD+ Android Development] Sherip:
After downloading from Amazon app store, when I elect to install the app, I'm now getting soft reboots. After that, if I restart the Amazon app store it prompts to install the app and succeeds.

This is new behavior on my 8–22 SD Cm 8.2.

Edit: BTW Amazon is offering a few "greatest hits" free apps today, including SwiftKey. Still trying to decide if I can get used to SwiftKey. I'm too accustomed to the Android keyboard I guess.

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] tebra:
Same for me on 8/29. But the hardware home button wake up thé screen directly.

Envoyé depuis mon Xperia S avec Tapatalk 4
[Nook HD, HD+ Android Development] razholio:
with 10.2 it will automagically use trim.
[Nook HD, HD+ Android Development] verygreen:
but it would onl do it who knows when once the load is low and you have plenty of battery.

You can force it with "vdc fstrim dotrim" command from adb shell.
[Nook HD, HD+ Android Development] verygreen:
After getting wind of some interesting hints I decided to give them a try and they seem to be somewhat working, though does not seem to be a huge difference, but I feel a general smoothness is improved.

So here's a binary 10.2 build for sdcard, give it a try if you are interested and please report back with your experience, and based on that we'll decide if it's worth importing this stuff into mainline.

cm-10.2-20130830-UNOFFICIAL-ovation-sdcard.zip
[Nook HD, HD+ Android Development] Stevethegreat:
I thought VG removed it for feat that it will brick the eMMc. Or has he kept it on just for the SD version?
[Nook HD, HD+ Android Development] starbright_:
How did you manage to install TWRP?

Goo Manager reports that the device is not supported.

Or did you use this method:

dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p3
[Nook HD, HD+ Android Development] verygreen:
No, sd version has trim disabled as well.

The only way to get trim is to flash that trim-enabled kernel referenced a few pages back and only for emmc installs.
[Nook HD, HD+ Android Development] Sherip:
I installed it and wiped both caches. This time I'm trying without SuperSu and will see how it goes. So far mostly seems fine. But I quickly had several crashes in Trebuchet, mostly when using the app drawer. I rebooted and haven't had another crash as yet. Also didn't soft boot as before when I tried installing from Amazon appstore.

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] razholio:
Brusyev (and myself and others) is using verygreen's trim-enabled kernel which must be flashed on top of recent 10.2 roms.
[Nook HD, HD+ Android Development] :
From what I can understand and find* about the emmc brickbug, when on a kernel that has trim enabled for the faulty samsung part/firmware (I'm guessing lagfix is in the same boat) it is important to not wipe/format as there would be a high possibility of bricking.

One of the two type of bricks would cause the device to not turn on.

I do not know if that is what happened.

*I know nothing about lagfix nor trim on Android so correct me if this is wrong, not quite right, or missing information.

QUOTE:

"Operations that are likely to cause damage when running an affected kernel:

Wiping in CWM (and likely any other custom recovery) (confirmed)

Restoring a Nandroid backup in CWM (wipes first)

Flashing another firmware in CWM (most flashes wipe first)

Wiping in stock 3e recovery (suspected, also wipes a partition)

Deleting large files when running an affected kernel (suspected but not confirmed)

If you have an affected kernel:

Flash a known good kernel using Odin/Heimdall immediately"

Information found in below links:

http://developer.samsung.com/forum/...axy-s-ii-and-note-official-ics-roms/77/152576

http://xdaforums.com/showthread.php?t=2091045
[Nook HD, HD+ Android Development] Stevethegreat:
Isn't that kind of dangerous though?

(I'm asking because I'm honestly thinking of experimenting with it, but a bricked Nook doesn't sound like a good idea)
[Nook HD, HD+ Android Development] verygreen:
It is possibly dangerous, but without testing there's no way to find out if the fix we have is effective or not.
[Nook HD, HD+ Android Development] williamlaw:
will this feature "Experimental layer sizing changes to improve general smoothness" on future cm rom ??
[Nook HD, HD+ Android Development] verygreen:
depends on how well this testing will go.
[Nook HD, HD+ Android Development] RoundSparrow:
I enjoy the HD+ so much that I'm using it for my app development... it's great to have Android 4.3. I'm using CynDelta to update every new release of 10.2..

Overall, even using all internal flash, I find this kernel isn't very stable with any kind of heavy writing activity. For example, I am working on an app that downloads images from cameras over WiFi... and my app runs as a service all the time. But it typically is only a few hours and I encounter random reboots. Other devices (such as Sero 7 Pro from wal-mart, running it's stock 4.2) don't have this problem...

On similar note, do you ROM developers run some kind of hard stress test? I mean can we write a Python program or something to really exercise the WiFi + disk writing... I imagine we can make this kernel reboot within a few minutes if we identify the pattern of activity that triggers it ;)

Is there any kind of setting to STOP the Linux kernel from automatically rebooting and instead present some diagnostic information of why my Android system just rebooted?

---------- Post added at 03:36 PM ---------- Previous post was at 03:14 PM ----------

the "notification area" topmost bar of Android - I think it's too small. on the stock Nook HD+ ROM it's much larger... perhaps too large...

But this CM 10.2 doesn't seem to take into account the size high DPI of the nook screen. For example, if I turn on the percentage display of battery, you really can't read it inside the circle. I also have repeat problems touching the notification bar and pulling it down.

Is there a setting I can change to increase this? I also suggest the default goes up at least 25%... how many pixels high is it now?

I don't have fat fingers ;)
[Nook HD, HD+ Android Development] SCWells72:
Can someone give me a pointer to the noemmc ROM so I can see if it at least lets me boot into my HD+ that appears to be bricked now? I'm likely going to pursue a warranty replacement, but I'd like to see if I can isolate what's going on a little more before taking that final step.
[Nook HD, HD+ Android Development] Sherip:
See the links in this post http://xdaforums.com/showthread.php?p=44810400

Hope it helps.
[Nook HD, HD+ Android Development] verygreen:
What's in /proc/last_kmsg after reboot?

Is your writing to sdcard (as opposed to emmc)? sdcard accessing hardware is very picky about your cards and tends to frequently timeout and die otherwise.

I run benchmarks from time to time that do bursts of activity ;)

Not easily, but the crash data is recorded in /proc/last_kmsg that you can access after reboot.
[Nook HD, HD+ Android Development] TeutonJon78:
Verygreen posted a version of it to install in original thread for 10.1. You could choose CWM or TWRP. I don't think it's an official release from TWRP.

On that note, verygreen, is it possible to get that port of TWRP official so that when new versions come out they build them, or does it require too much "hackyness" with the bootloader?
[Nook HD, HD+ Android Development] SCWells72:
Yup, that helped quite a bit! I've verified that it does boot from SD card into CWM but can't seem EMMC from there. I'll contact B&N about a replacement. Thanks!
[Nook HD, HD+ Android Development] brusyev:
How did you brick your Nook? I have the 16Gb version with faulty chip and currently running the trim enabled kernel on it....
[Nook HD, HD+ Android Development] RoundSparrow:
I do not have any sdcard in the device, I'm purely on emmc. /proc/last_kmsg doesn't exist (I tried to cat it from root adb shell)

Any chance during these troubleshooting Alpha days we can enable:

CONFIG_ANDROID_RAM_CONSOLE=y

CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y

CONFIG_APANIC=y

CONFIG_APANIC_PLABEL="oem_log"
[Nook HD, HD+ Android Development] verygreen:
/proc/last_kmsg would only exist right after you had this unexpected reboot.
[Nook HD, HD+ Android Development] verygreen:
Once booted there, do "dmesg | grep mmc1" from adb

if you see "110 timeout" then that's it.

If you see your emmc device listed, then likely you have a non-fatal corruption that I atill plan to do a test fix for adopted from KindleFireHD solution and will need testers ;)
[Nook HD, HD+ Android Development] verygreen:
I am not sure how to add an official port to TWRP, I just pull their repo in my tree and it builds, so there are no extra hacks needed (at least for Ovation, hummingbird is a different story with it's upside-down screen).
[Nook HD, HD+ Android Development] TeutonJon78:
At least according to the webpage, if you let them know you got it working for a device, they might add official builds for it: "If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later."

http://teamw.in/project/twrp2

On a side note, there 2.6.1.0 was released as well, with updates for 4.3 ROMs.
[Nook HD, HD+ Android Development] starbright_:
Thanks for activities reagrding TWRP.

With latest version (0830) I miss the toggling for brightness.

I setup the brightness Icon in the notificaton bar, so that (in case I dimmed it completly) can even blind touch that to make display readable again. In general the settup for this has been changed, but - is this selection of discrete brightness levels really disappeard or did I haven't found it?
[Nook HD, HD+ Android Development] SCWells72:
As far as I can tell, just by using it. I definitely flash ROMs frequently, and I was running LagFix occasionally, so I guess the former was putting my emmc in a bad state that trim is intended to fix, then the trim was what actually nuked it.

B&N has authorized a replacement that should arrive this week. I'm hoping it has a problem-free emmc chip in it this time. The accumulated lag makes the device unusable, and the fix for that kills it! Not a good combination...
[Nook HD, HD+ Android Development] razholio:
There is anecdotal evidence that data wipes between updates will eliminate the reboots.
[Nook HD, HD+ Android Development] Amirusownsu:
Alright...flashed the install, for some reason can't get into recovery, any tips? I long press power button and it either boots, or shows the logo then turns right back off.

Any help is appreciated.
[Nook HD, HD+ Android Development] Reed-Sternberg:
Well, I also started running the fstrim enabled kernel on my faulty 16G HD+. Will update you folks if I managed to brick it! ;)
[Nook HD, HD+ Android Development] Hashcode:
I saw that the commits needed to build hummingbird were merged in 2.6.1 so with the existing config, we should be able to pull the repo and do a straight build. Also we can put a separate twrp.fstab in /etc which overrides the default recovery.fstab.

I'll catch you on IRC and we can run some tests.
[Nook HD, HD+ Android Development] verygreen:
My anecdotal evidence suggests that there are no reboots, I've yet to see any, I always do dirty updates, never flush cache, reuse /cache between different versions and so on.
[Nook HD, HD+ Android Development] Amirusownsu:
I've had no reboots either, and it seems very stable. I forgot to install gapps when I flashed the update, and can't seem to get back into recovery, any tips?
[Nook HD, HD+ Android Development] jpisini:
Not seeing a huge difference. What should I notice?
[Nook HD, HD+ Android Development] Amirusownsu:
Able to get into CWM...

Installed apps etc in CWM, says it's succesful but when I boot back into android the apps are not there. Any advise?
[Nook HD, HD+ Android Development] leapinlar:
You mean gapps? What is it that you are expecting to be in android when you boot back? Generally the only gapps you see is Play Store.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] Amirusownsu:
I do not have play store, gmail, or any of the apk's that normally come with the gapps installs.
[Nook HD, HD+ Android Development] leapinlar:
Gmail does not come with gapps. What version of gapps did you flash?

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] Amirusownsu:
gapps-jb-20130813-signed