yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] verygreen:
No, there's not much useful development in the queue, I think and 8/15 for sdcard already has fstrim disabled.
[Nook HD, HD+ Android Development] Aporus:
Thank You! I made Sdcard and can boot to it. What next step? How can I see about my partitions?
[Nook HD, HD+ Android Development] verygreen:
so when you adb shell in and do

"dmesg | grep mmc1", what do you see?

Is /dev/block/platform/omap/omap_hsmmc.1/by-name dir empty? Can you mount devices from there?
[Nook HD, HD+ Android Development] Aporus:
Mmm.. Cant to connect device :( I see "NookHD+" in Windows Device Manager, try to change the driver (take it here )and see massage "No driver"
[Nook HD, HD+ Android Development] verygreen:
Well, you probably need to install some sort of a driver.

I don't use Windows myself, but there's what looks to be a guide for Windows users at http://xdaforums.com/showthread.php?t=2336088
[Nook HD, HD+ Android Development] Sherip:
I found you can set it for a fixed location in settings. Updates weather regularly for me after doing that.

Sent from my Nook HD+ running CM 10.2 from SD card
[Nook HD, HD+ Android Development] starbright_:
Question: After updating via CM-Updater - do in need to wipe cache or dalvik?

[MENTION=3654172]verygreen[/MENTION]: as this might be of interest for others too, can you update the first post with this info? (that will be read by all users)
[Nook HD, HD+ Android Development] RottenEntrailz:
Since I updated to 10.2, when I try to update with CM-Updater it reboots to recovery and I have to point it to the zip file.

Before that it would know where the zip was and start.

Sent from my Nook HD CM10.2 4.3
[Nook HD, HD+ Android Development] cfli1688c1:
are we safe with the 8/15 rom? the one with FSTRIM disabled

thx
[Nook HD, HD+ Android Development] TeutonJon78:
Depends on if your running it from SD card.

From SD: 8/15 or newer (or 10.1)

From emmc: 8/17 or newer (or 10.1)
[Nook HD, HD+ Android Development] cfli1688c1:
this is for CM 10.2 8/15 build, and on the sd card (its only available on sd card ... )
[Nook HD, HD+ Android Development] SCWells72:
I'm pretty sure the 8/15 build is the last one that had fstrim enabled even though that was the same day that the change to disable it was checked in.

UPDATE: Looks like others have provided more accurate information.
[Nook HD, HD+ Android Development] stevetrooper:
8/20 still not working with geolocation, but setting a location continues to work.
[Nook HD, HD+ Android Development] cfli1688c1:
whats the difference between these updates?

-	cm-10.1-20130819-UNOFFICIAL-ovation-noemmc.zip

-	cm-10.1-20130816-UNOFFICIAL-ovation-sdcard.zip

one has noemmc and one has sdcard

thanks.
[Nook HD, HD+ Android Development] Sherip:
The one labelled sdcard uses the cache partition on internal storage whereas the noemmc would not. There may be other differences like whether or not it tries to read the serial number and such, or mount the emulated sdcard of internal storage.

Sent from my Nook HD+ running CM 10.2 from SD card
[Nook HD, HD+ Android Development] verygreen:
cm-10.1-20130819-UNOFFICIAL-ovation-noemmc.zip is intended for people who bricked their emmc and want to use their nook anyway because for whatever reason doing a warranty replacement is not feasible.

It does not try to access emmc at all, so is fully sdcard-contained, including cache and everything like that. HDMI will not work in that version because the keys for that are obtained from emmc too.
[Nook HD, HD+ Android Development] bxlegend:
ADB only works in recovery for me. Anyone else have this issue?
[Nook HD, HD+ Android Development] Sherip:
You need to have USB debugging enabled in developer options. If you don't have developer options you need to tap the build number in about tablet repeatedly (about 8 times) to enable developer options. There's also an option for root access (mine says Apps and ADB).

Sent from my Nook HD+ running CM 10.2 from SD card
[Nook HD, HD+ Android Development] bxlegend:
Already have all of that enabled.
[Nook HD, HD+ Android Development] Sherip:
Also, did not work for me without the latest version of adb, and the first time I used it I had to confirm from a popup on the nook that I allowed the connection. Probably different than connecting to recovery. Hope it helps. Which OS are you using? Mine is Win 8

Sent from my Nook HD+ running CM 10.2 from SD card
[Nook HD, HD+ Android Development] starbright_:
So, should this mean no cache or dalvik clear is necessary?
[Nook HD, HD+ Android Development] bxlegend:
Whatever it is that needs to be done I already did it. Been using adb and custom ROMs since the MyTouch 3G was released. I use Linux primarily and Windows only when necessary and it doesn't work on either OS. Come think of it, I don't think it has worked on any of Verygreen builds.
[Nook HD, HD+ Android Development] dbrickg:
LIkewise on mine. And Kindle still doesn't work at all, just throws an error saying "Unfortunately Amazon Kindle has stopped"
[Nook HD, HD+ Android Development] Crazy Chuckster:
I reverted back to CM 10.1 8/13 build and I can now tether to my photon via Bluetooth (still only in 3G mode) but this nook refuses to see my photon as an access point with WiFi tether on.

Also when resetting all data/factorty wipe in CWM in order to change to 10.1 or back it still leaves folders and images in the os.
[Nook HD, HD+ Android Development] razholio:
I'm also almost exclusively linux and I've never had any trouble connecting ADB to atrix, atrix2, xperia ion and LGOG. However, the nook HD+ has been a problem. I just figured I needed to add some udev magic...
[Nook HD, HD+ Android Development] verygreen:
This sounds like old sdk.

They did change the protocol a bit when going to 4.2, and now the ssl handshake is a requirement. all older sdk adbs only report "device offline".
[Nook HD, HD+ Android Development] bxlegend:
Yeah I mucked around with UDEV for a minute thinking it was an issue with my 51-android file but I had no luck.

I think you missed the context of my post. I have many devices in my home running various versions of CM. So whenever Google releases a new version of Android, I update the SDK. Just to be more clear, ADB shows no device while I am booted into CM. I only get device status while I'm in recovery.
[Nook HD, HD+ Android Development] RoundSparrow:
Even with today's update, the 10.2 isn't working with geolocation for me. I did a complete format and load on upgrade to 10.2....

sl4a python fails to get location, google maps,Car2Go, weather apps, etc. This was working with the 10.1 before the changeover to 10.2 nightly. I'm talking WiFi location/Google...
[Nook HD, HD+ Android Development] verygreen:
A small poll, esp. if you have Nook HD that's not 8G or HD+ that's not 16G. (Trying to see if there's any variability in emmc chips used and also find out what chips are used in devices of other sizes).

Can you please do these commands (in adb shell or terminal, does not matter if you run off sdcard or emmc):

cd /sys/class/block/mmcblk0/device
cat name
cat manfid

Please report the value printed after "cat name" and value printed after "cat manfid" if it's differet from what was posted in posts before your.

On My Nook HD+ 16G I get: name MAG2GA and manfix 0x000015 - which is a known faulty Samsung EMMC part.

On my Nook HD 8G I get: name 008G92 manfid 0x000011 - which is a 8G Toshiba part that has no known problems.

Thanks.
[Nook HD, HD+ Android Development] Depardieu:
So is the bricking only localized to build 8/15? Or to be completely safe should one just go back to 10.1?

Thanks for any info!
[Nook HD, HD+ Android Development] dbrickg:
Likewise: my Nook HD+ 32GB, has MAG2GA and 0x000015
[Nook HD, HD+ Android Development] Nuor60:
nook hd+ 32G

MBG4GA

0x000015
[Nook HD, HD+ Android Development] jpisini:
I use an Ubuntu based system with webupd8`s android tools no issues using adb.
[Nook HD, HD+ Android Development] hyun5suk:
HD+ 32G CM10.1 8/12

MBG4GA

0x000015
[Nook HD, HD+ Android Development] bpaulien:
My 16G HD+ has the same part as yours.

I guess I should stick with 10.1 for now.
[Nook HD, HD+ Android Development] verygreen:
to all builds before 8/15 and 8/15 nightly (but sdcard 8/15 is ok).

CM 10.1 is not affected as long as you do not run the lagfix app.
[Nook HD, HD+ Android Development] Eric Karz:
Nook+ 16 G

MAG2GA

0x000015

stock/unrooted / cm10.2- 815 on SD 64 sdcard
[Nook HD, HD+ Android Development] Depardieu:
Thanks, I have 8/17, so I guess I should be ok, thanks for the reply! Definitely put me at ease.

*Additional Info*

NOOK HD+ 16GB - CM10.2 8/17 emmc

MBG4GA

0x000015
[Nook HD, HD+ Android Development] Fornowagain:
hd+ 32G

MBG4GA

0x000015

CM10.2 8/17 emmc
[Nook HD, HD+ Android Development] scabbard1:
HD + 16 gb name MAG2GA and manfix 0x000015
[Nook HD, HD+ Android Development] :
HD+ 16G: MAG2GA, 0x000015
[Nook HD, HD+ Android Development] rholm:
My HD+ 32G matches yours.

Cheers,

Rich
[Nook HD, HD+ Android Development] bxlegend:
Nook HD+ 16G

MAG2GA

0x000015
[Nook HD, HD+ Android Development] Nucking Futs!:
HD+ 32GB:

SEM32G

0x000045

0820 build

Haven't used it long enough to notice any issues yet.
[Nook HD, HD+ Android Development] Reed-Sternberg:
Nook HD+ 16g

MAG2GA

0x000015
[Nook HD, HD+ Android Development] YOUCANNOTDENY:
My Nook HD+ 16GB uses a SanDisk chip, and had no problems on both the 08/15 and 08/19 builds.

SEM16G

0x000045
[Nook HD, HD+ Android Development] leapinlar:
My 32 GB HD+ says

SEM32G and 0x000045.

Edit: My 16GB HD is 016G4A and 0x000011 and my 8GB HD is M8G2FB and 0x000015 and my 16Gb HD+ matches yours.
[Nook HD, HD+ Android Development] SCWells72:
My 32G HD+ reports 0x000015 and MBG4GA.
[Nook HD, HD+ Android Development] verygreen:
You guys are lucky, there are no known sandisk issues on any device.
[Nook HD, HD+ Android Development] Nucking Futs!:
Nice! FWIW, I purchased mine 4-5 weeks ago.
[Nook HD, HD+ Android Development] stevetrooper:
Mine matches this. Nook HD+ 32
[Nook HD, HD+ Android Development] RageAgain:
My Nook HD+ 16GB is the same...
[Nook HD, HD+ Android Development] MadMikeSS:
I have the same with my 16gb HD+. I've been running 10.2 since it started coming out in the nightlies, should I not be at this point? I don't use lagfix app I've been reading about. I also have 8/20 installed as of this afternoon and haven't run into any significant issues with cm yet on at least 3 different 10.2 nightly roms.
[Nook HD, HD+ Android Development] Darrian:
Amazon Kindle is crashing on startup (everybody seems to know about this) and so is Plex (haven't seen anybody else talk about this one yet). Other than that it's looking pretty stable. I'm wondering if these apps that are crashing simply need to be updated for Android 4.3.
[Nook HD, HD+ Android Development] oogsaggie:
HD+ 16 gb MAG2GA and manfix 0x000015

So one can assume that the Sandisk chips were "late production"?
[Nook HD, HD+ Android Development] Sherip:
I had recently set up adb on Windows, and just now I set it up on a ubuntu chroot I have running on an x86 Chromebook.

All I needed was platform-tools from the sdk and a ~/.android/adb_usb.ini file containing a line with 0x2080 in it. You only need the ini file for usb, to use adb wirelessly you just need to adb connect nooksaddress:port (and have network adb enabled on the nook. For both usb and wireless you have to answer a popup on the nook to allow the connection.

The current adb executable is dated 7/29/2013

---------- Post added 21st August 2013 at 12:03 AM ---------- Previous post was 20th August 2013 at 11:55 PM ----------

Mine is the same.
[Nook HD, HD+ Android Development] webdroidmt:
Originally Posted by verygreen

On My Nook HD+ 16G I get: name MAG2GA and manfix 0x000015 - which is a known faulty Samsung EMMC part.

Ah, seems I am also lucky enough to have the same faulty part on my HD+ 16GB. :laugh: Actually, looks like there are quite a few with this part.

Mike T
[Nook HD, HD+ Android Development] Crazy Chuckster:
Another MAG2GA - 0x000015 16GB Nook HD+ here.
[Nook HD, HD+ Android Development] stumark:
Nook hd+ 32G<br />

MBG4GA<br />

0x000015<br />

Forgive me, I'm struggling to keep up - is CM10.1 completely safe? What is the issue with CM10.2 and the Samsung chip?
[Nook HD, HD+ Android Development] guythnick:
HD+ 16G: MAG2GA, 0x000015

Can you post the source that shows this is faulty hardware?
[Nook HD, HD+ Android Development] Aporus:
Do it and see

Is it?
[Nook HD, HD+ Android Development] starbright_:
Listed as a known bug at post #1. We are all suffered from this. Best is keep patience.

---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------

Has someone testet this?

is this CM Updater work NOOK HD+ as well?
[Nook HD, HD+ Android Development] spartan4585:
It was crashing on the last official 10.1 dated 8/13 also. I had to revert back to the first official one dated 8/9 which worked for me. I did not try the other versions in between. I am waiting for this to get resolved before going to 10.2
[Nook HD, HD+ Android Development] jpisini:
MAG2GA and manfix 0x000015

Nook HD+ 16gb

---is there anyway to make sure we don't get bit?
[Nook HD, HD+ Android Development] Jack45:
From OP:

Important! if you still run 8/15 nightly or earlier, I advise you to upgrade to a newer one or to downgrade to cm-10.1 right away while we fight emmc bricking firmware bug.
[Nook HD, HD+ Android Development] stephencwl:
Nook HD+ 32G

Name: SEM32G

Id: 0x000045
[Nook HD, HD+ Android Development] move_over:
Same here Nook HD+ 32GB
[Nook HD, HD+ Android Development] rkeller62:
2 NookHD+ 16GB models one with bad Samsung emmc and one with SEM16G Sandisk emmc.

Luckily didn't brick the one with bad emmc as I used to run lagfix on 10.1 and have been on the 8/15 nightly of 10.2 until just now.
[Nook HD, HD+ Android Development] verygreen:
Your EMMC and partition layout is intact. what you need is to probably figure out which ones are damaged and repopulate them.

Flash full stock 2.1.0 zip from item #6 of this post, this should help you: http://xdaforums.com/showthread.php?t=2062613

Once done and all is fine you can install CM again.
[Nook HD, HD+ Android Development] rushless:
I am probabky sticking with 10.1, since Flash is not as friendly with 10.2. It still works, but not with as many sites and some sites "work" but with issues. Besides, I still have not seen concensus that the lag issue is fixed or mitigated with 10.2. The only issue I have is the lag.

Staying in my bunker for now, especially based on the recent 10.2 issues.
[Nook HD, HD+ Android Development] O.a.T.:
Same on my Nook HD 8G.
[Nook HD, HD+ Android Development] razholio:
I've got a HD+ 32G with MBG4GA and mafid: 0x000015

I'm on 10.1 and have run lagfix about 20x w/o issue.

FWIW, brickbug says my eMMC chip is bug free. Can anyone confirm?
[Nook HD, HD+ Android Development] RageAgain:
I have used all of the 10.2 nightlies since they became available, so I guess that I have been lucky considering the memory I have. Even so, other than spontaneous reboots and crashes I haven't had many issues that weren't 4.3 related, and the new 10.2 20130820 seems to be working fine. Since they took the suspect code out of the nightlies after 08/15 I am not concerned that there will be any major issues. The new nightly works pretty good as far as I am concerned.
[Nook HD, HD+ Android Development] spartan4585:
is the kindle app working with latest build or is that still broken?
[Nook HD, HD+ Android Development] TeutonJon78:
Nook HD+ 32GB

name: SEM32G

manfid: 0x000045

10.2, 8/17, emmc

I won the emmc lottery. Bought during the Father's Day sale (that is still ongoing).
[Nook HD, HD+ Android Development] Jack45:
Not working with cm-10.2-20130821-NIGHTLY-ovation.zip .
[Nook HD, HD+ Android Development] digixmax:
http://wiki.cyanogenmod.org/w/EMMC_Bugs#MAG2GA_TRIM_bug
[Nook HD, HD+ Android Development] razholio:
it looks like those of us with the 32GB samsung module (MBG4GA) are safe (so far):

http://wiki.cyanogenmod.org/w/EMMC_Bugs
[Nook HD, HD+ Android Development] SCWells72:
Yeah, that's what I have, and I also noticed earlier that it looks safe. So any idea what the plan might be to start taking advantage of fstrim again for those who can while not risking those who can't? Should we just drop back to either CM10.1 or the 8/15 build, or is there something else in the works?
[Nook HD, HD+ Android Development] razholio:
The two options I see are:

1. use lagfix now to manually (or schedule) fstrim calls to /data and /cache

2. wait for a brickbug-safe implementation to make it into CM10.2

they are working on #2 right now and a solution is known so it shouldn't be too long. Because it takes so long for the lag effects of eMMC fragmentation to be felt, manually running lagfix every few days is perfectly acceptable to me. for now.
[Nook HD, HD+ Android Development] stegg:
I'll answer even if I have a 16G HD+ because my results are different:

name SEM16G

manfid 0x000045
[Nook HD, HD+ Android Development] bxlegend:
It works over network but I need it to work with USB which it just does not do.
[Nook HD, HD+ Android Development] hooah212002:
Under what circumstances is it OK to run the lagfix app without the (well documented) chance of bricking the device (short of waiting for the actual fix)?

Not at all with any CM 10.1?

CM 10.2 build 8/16 and later?

I ask because I can deal with all the rest of the bugs (reboots, wonky screen rotation), but the lag makes me want to return this thing.
[Nook HD, HD+ Android Development] helousn:
On My Nook HD+ 16G I get: name MAG2GA and manfix 0x000015
[Nook HD, HD+ Android Development] SCWells72:
Agreed, but lagfix only works when the trim operation is enabled in the kernel/filesystem, and it's not in 10.2 after the 8/15 build. That was what I meant about going back to CM10.1 or CM10.2 from 8/15...you'd also have to use lagfix (which is fine with me).
[Nook HD, HD+ Android Development] razholio:
your only safe option is to wait for the fix to be committed to 10.2 in the near future.

---------- Post added at 03:39 PM ---------- Previous post was at 03:35 PM ----------

are you certain that's the case? 4.2 and earlier was not supposed to have fstrim support. It turned out that trim() was present in the kernel, but not actually called by any code. I understood that in 4.3, the implementation is not to call it with every sync() or fsync(), but to run it only under certain conditions like charged above a certain percent and system being quiescent. I don't know if this was userspace or kernel, but with this functionality disabled, the actual trim() system call would still be available. lagfix includes a fstrim executable for android that calls trim() on specific mountpoints.
[Nook HD, HD+ Android Development] verygreen:
safe to run lagfix on 10.2 post 8/15 because it's a noop there

Only safe to run lagfix on 10.1 if you have EMMC from sandisk or Toshiba (ie not Samsung (manfid 0x15))
[Nook HD, HD+ Android Development] SCWells72:
Yup. Try to run lagfix on any build after 8/15 and it actually tells you itself that the feature isn't enabled and disables its own functionality. My understanding is that they actually disabled the ioctl to support the trim operation in the kernel filesystem module. Here's the exact message that lagfix gives on post-8/15 builds:
[Nook HD, HD+ Android Development] Sherip:
Wouldn't those without Samsung EMMCs (not me) be safe with the unofficial EMMC 8-20 build that reenables trim support?

Sent from my Nook HD+ running CM 10.2 from SD card
[Nook HD, HD+ Android Development] verygreen:
I don't know.

We are not really sure if that patch is really applicable to our devices in the same way it is applicable to original Nexus 7.

Nexus 7 has a bit earlier firmware and for all I know the newer firmware fixed the original bug and introduced something even more horrible.

So it needs a lot of testing on one hand, but I cannot ask anybody to really test it because that would be askign people to try potentially bricking code again.

Also there are some a bit different samsung parts, as we learned, how succeptible are those we don't know too, and if there are any bugs in them, as we have not seen those parts in other devices so far, I think.
[Nook HD, HD+ Android Development] m771401:
Nook HD+ 32GB CM-EMMC 8/19

MBG4GA

0x000015

06

11/2012

I recently RMA'd mine and they sent a whole new one in retail packaging.
[Nook HD, HD+ Android Development] verygreen:
NEw sdcard binary drop (matching upcoming nightly too): cm-10.2-20130822-UNOFFICIAL-ovation-sdcard.zip

Not too much user visible changes here, other than hardware buttons in settings are now matching what we have.

A work around for missing location was discovered - just turn wifi off, then back on.

Also it was noticed that the "Recent app" button does not work reliably (and it must be an upstream problem), I think when yo turn the screen off and then back on, it comes to it's senses.
[Nook HD, HD+ Android Development] dmullens:
Thanks for keeping the SD version up to date. I assume the SD version can't update from the manual update so we need to wait for these drops...
[Nook HD, HD+ Android Development] verygreen:
I am not really sure what you mean, shows "Today 11:33" for me
[Nook HD, HD+ Android Development] dmullens:
Yea...sorry about that. After it posted the timestamp changed and was correct. Very odd. Not sure what happened. Didn't know if one of the updates somehow threw the time off. I edited my message hoping that it didn't confuse anyone. Guess I didn't get it quick enough ;)
[Nook HD, HD+ Android Development] Sherip:
My uptime before updating was more than 5 1/2 days.

Sent from my Nook HD+ running CM 10.2 from SD card
[Nook HD, HD+ Android Development] alexisprz:
# cat name

MBG4GA

# cat manfid

0x000015

Nook hd+ 32gb

No problems running any files you've uploaded or nightlies for emmc
[Nook HD, HD+ Android Development] artesea:
The soft reboots we've been seeing. Are these linked to the EMMC chips? Could suggest why some people haven't been getting them if they have different hardware.
[Nook HD, HD+ Android Development] dmullens:
I'm running off the SD card and I've noticed them. I have the bad chip too.
[Nook HD, HD+ Android Development] foxorroxors:
using emmc 10.2 for a few hours now doesnt seem to be any less stable than 10.1, happy nooker here =) (32gb)
[Nook HD, HD+ Android Development] Azurael:
That'd be why mine hasn't bricked despite repeated use of LagFix since I've owned it... Is there a current build of 10.2 with TRIM enabled?
[Nook HD, HD+ Android Development] SCWells72:
Same here. Mine is already starting to lag again. I'd prefer to move forward if possible, but worst case scenario I may go back to CM10.1 until there's a more recent 10.2 build that enables it for emmc that does support it safely.
[Nook HD, HD+ Android Development] MadMikeSS:
So I installed this same app, I have mag2ga chip and this app says no to brick bug.
[Nook HD, HD+ Android Development] kliu888:
Are there other ways to fix the lag if I prefer not to use apps like LagFix? Would doing a Nandroid backup/restore do it? Or would it just write the fragmentations back?
[Nook HD, HD+ Android Development] razholio:
you da man! I didn't realize (until reading verygreen's post about the noop in trim() ) that they had disabled fstrim in a different way from 10.1. I just ASSumed that they would have made 10.2 behave like 10.1 if for no other reason than to let those of us lagfixers still have our lagfix. :(

oh well, thanks for setting me straight. guess I'm just fine with 10.1 for now...
[Nook HD, HD+ Android Development] Sherip:
I've not seen many soft reboots running any of the SD 10.2 updates. I'm not sure if uptime is reset by a soft reboot, need to check just after one to be sure.

FWIW I'm still flashing SuperSu 1.51 whenever I flash an update.

There was a recent Chrome update via the play store, and I had stability issues with it, so I processed the option to remove updates for chrome. It was suddenly vanishing while I was using it, and putting me on the desktop.

Geolocation works for weather widget with the latest update (at least after disconnecting and reconnecting).

I've noticed my email count notification gets overstated by 1. When I have one new message, it reports 2, etc.

Sent from my Nook HD+ running CM 10.2 from SD card