yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] verygreen:
The soft reboots linked to gps service are not affected by the emmc chips.
[Nook HD, HD+ Android Development] verygreen:
I guess the apps checks only for a very specific sublist of buggy chips and the list is not really updated. Perhaps it was targeted to a very specific device too.
[Nook HD, HD+ Android Development] Sherip:
I don't have GPS Satellites enabled in Location settings (might be helping prevent soft reboots)

HD+ with MAG2GA chip running CM 10.2 from SD card
[Nook HD, HD+ Android Development] artesea:
It was built for the Samsung Galaxy S2, and then adapted for the Samsung Galaxy 3. But it does get the EMMC info without the need to load terminal or type commands.
[Nook HD, HD+ Android Development] razholio:
the brickbug app was written for a subset of samsung devices. However, the list at the CM wikipage includes the MGA2GA (in the 16GB HD+, but not the MGB4GA (32GB). Is there some other reason you are suspicious of the MGB4GA or is it because it's a samsung, and you figure it's only a matter of time before there is enough evidence to include it in the list here:

http://wiki.cyanogenmod.org/w/EMMC_Bugs#MAG2GA_TRIM_bug
[Nook HD, HD+ Android Development] verygreen:
I helped to draft the list.

MGB4GA was not really seen in any other devices before, I think.

Judging by the patch in the N7 tree, I suspect the workaround would also be enabled by this chip (the only conditions for workaround are: manfid 0x15 and lowest bit in csd[64] set, no name check.
[Nook HD, HD+ Android Development] Azurael:
The brickbug app should be fairly accurate and has been kept up to date. Remember, it's specific chips in combination with a particular firmware revision which suffer from the brickbug. Most devices which are known to suffer from this have had kernel patches which load a new firmware on boot (although the change obviously isn't permanent.) I would hazard a guess that my N7 also has a 'safe' chip since I've been using LagFix on a regular basis since day 1 on that too...
[Nook HD, HD+ Android Development] razholio:
ah, that's critical info. thanks. I'll cease my use of lagfix, then. How does that workaround avoid the bug? does it avoid trimming under certain circumstances or does it avoid trim() altogether?

---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------

I'm assuming this is a 2012 N7? there are 2 other possibilities:

1. 4.2 got the firmware update in the kernel at some point, thus fixing the bug that way, or

2. you have been extremely lucky.

at least for some of the eMMC corruption bugs, the bug is triggered when the firmware is in a certain state and if you don't catch it in that state when issuing the trim(), then you don't see the bug. According to verygreen, the workaround in 4.3 for the N7 just checks the manfid, and not the firmware version or chip name, though this could just be out of an abundance of caution. better to degrade performance a bit and avoid bricking your customer's tabs...
[Nook HD, HD+ Android Development] verygreen:
The workaround uses "discard" command instead of "trim" command on affected parts. We don't know how effective that is, what we do know is there are no problem reports from N7 users that use same parts as us, but they also have a little bit older firmware (ours is version 6, theirs is 5. It is not impossible that 5->6 introduced the bricking bug too while version 5 jsut had a corruption issue).

The N7 tree patch has a very strange description that talks about adding a new feature instead of fixing any bugs, but I suspect that's just the usual smoke about real reasons, which does happen with Samsung originated patches in this area.
[Nook HD, HD+ Android Development] razholio:
very interesting. well, I've got fairly good access to warranty support as I live near a B&N store and I've got AMEX at my back so I'm willing to offer myself up as a test case for anything you need in this area. I'm also not thrilled about keeping a lag-prone tablet around.

will discard accomplish the same thing? I've got to return the 2013 N7 I have by tomorow or else I'll have to keep it. If the workaround using discard isn't going to take care of the crippling lag from eMMC fragmentation, then I might just keep it...
[Nook HD, HD+ Android Development] verygreen:
Discard should work the same.

Anyway, here's a build with workaround in and fstrim reenabled for those that have sandisk EMMCsor want to give it a shot regardless.

cm-10.2-20130822-UNOFFICIAL-ovation-emmc.zip

(come think of it, I should have just made a kernel only zip, but well, too late now, I'll probably be doing that in the future. Then it would be version-agnostic too)
[Nook HD, HD+ Android Development] bpaulien:
I was considering the same thing. I have the faulty chip, and was wondering... I live within 10 miles of at least 3 B&N stores that I can think of. Are you able to return it to a store and get a replacement right there? Or do you have to follow the process of sending it in, and waiting for a replacement to be shipped to you?

I just don't want to be receiving a refurbished unit, if I did have to do a warranty replacement.

Does anybody have any experience with this? Can you just walk into a B&N store with a bricked HD+ and say "it stopped working, can I get a replacement?" and walk out with a new unit?

If so, I may just play around with this and see what happens. If not, I'll be a little more careful. :)
[Nook HD, HD+ Android Development] verygreen:
YMMV, but when I fried NC usb port some time ago, I just demonstrated it not working at the local B&N store and they made a replacement right away.
[Nook HD, HD+ Android Development] bpaulien:
That's encouraging... I may make a couple phone calls to the stores around me and see what their policy is. If they allow walk in warranty replacements, I may just give it a try, and see if I can brick this bad boy! LOL. It would be an extra bonus if I got one that didn't have the defective part!
[Nook HD, HD+ Android Development] razholio:
even better. I hadn't really thought it through, and frankly, would be ok with sending it in. However, being able to replace it in-store is even better.
[Nook HD, HD+ Android Development] verygreen:
Yes, I was fine sending it in, but phone support insisted I go to the store so that they make sure it really does not work, and then the store decided that they will replace it right away.
[Nook HD, HD+ Android Development] razholio:
I'm gonna do this. I'm downloading now. I've got some SD shuffling to do as I just got a new card, a backup of my current 10.1 and then I'm off to 10.2 brickage-land. I kid, I kid... ;)

anything I need to be sure to do in order to expose the bug other than reboot every so often and verify it does actually boot?
[Nook HD, HD+ Android Development] verygreen:
run lagfix from time to time

or run "vdc fstrim dotrim" from terminal/adb shell from time to time - ths triggers the trim action.

Try formatting (not erasing, formatting) partitions on emmc (/system is already formatted, but not trimmed, though you might remount /system rw to trim it too)
[Nook HD, HD+ Android Development] razholio:
ok, sounds good. I actually use my tab quite a bit and don't wanna wipe data, but I can do cache for sure.

anyway I can talk you guys into making this a boot-time tuneable like maybe something in build.prop? then the crazies among us could follow the nightlies and manually enable trim(). you could call it something like 'brick.me.now.with.trim' or something...
[Nook HD, HD+ Android Development] bpaulien:
Just a quick note about intentionally bricking your device, in order to get a warranty replacement... I don't know if it matters to anybody if you get a new unit, or refurbished unit, but I called the 3 closest B&N stores to me, and they all told me the same story. If you take it in to the store, they will "try to troubleshoot" it, but if it needs to be replaced, you'll be able to get the replacement on the spot.

They all 3 also confirmed that you would receive a refurbished unit, not a new one, as the replacement. (The exception being if you JUST bought it -- probably within a couple weeks -- you might get a new replacement.) This isn't probably "news" to anybody, but just thought I'd confirm that the process seems pretty straight forward, as long as you don't expect a new unit as a replacement.

Now I just have to decide if I want a refurbished unit that possibly doesn't have the defective part for EMMC, or keep my current one. I guess since I bought it in January, it's over 8 months old. Probably a refurb wouldn't be any worse than the one I've got... :) And I can just keep bricking them until I get one with a better part. Hmmm. This could be fun!

Still thinking. I may end up doing this.
[Nook HD, HD+ Android Development] verygreen:
I'll make special kernel zip later that you would be able to flash over nightlies to enable trim but otherwise retain the rest of the nightly.
[Nook HD, HD+ Android Development] razholio:
that works too. thanks.
[Nook HD, HD+ Android Development] Sherip:
I wonder if BN does in-store swaps if you bought it elsewhere, eg Target or OfficeMax.

HD+ with MAG2GA chip running CM 10.2 from SD card
[Nook HD, HD+ Android Development] BenGman:
Same here, Nook HD+ 32GB,

SEM32G, 0x000045

purchased 27th July 2013 from BestBuy.

Using 10.1 Unofficial Carbon 7/23 though but keeping track of the 10.2 progress.
[Nook HD, HD+ Android Development] Azurael:
I just checked, it's not even Samsung eMMC :)
[Nook HD, HD+ Android Development] brusyev:
Are they asking for the receipt/proof of purchase?
[Nook HD, HD+ Android Development] verygreen:
That I don't remember. Perhaps someone who did a recent exchange can chime in.
[Nook HD, HD+ Android Development] rholm:
I was getting daily soft reboots until I disabled GPS. Shouldn't this be disabled by default? We don't have a GPS in our nook hd+.

Cheers,

Rich
[Nook HD, HD+ Android Development] leapinlar:
As long as you registered it with B&N, they don't care where you got it. They just check the serial number and see if it is registered to you and if it is not working and within the warranty period, they replace it. No receipt necessary.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] razholio:
Sorry, what's not a Samsung eMMC? Yours in your nook, or the one in the N7?
[Nook HD, HD+ Android Development] brusyev:
Got it. Thanks Leapinlar

---------- Post added at 07:52 AM ---------- Previous post was at 07:42 AM ----------

I am having strange issue with the latest nightly release (actually few recent releases now). Upon reboot my Nook gets stuck at the CM spalsh

screen (rotating circle). The only way I can boot in to OS is by clearing cache or davlik cache. Is this happening to any of you? What can be causing this?
[Nook HD, HD+ Android Development] Azurael:
In my 2012 N7 32GB... I guess all NHD+ contain Samsung eMMC. Still, at least mine is thought to be a bug-free part. We'll see, since I have TRIM re-enabled now. Since I lagfixed it, this CM10.2 build us the fastest thing I've run on it yet. Since switching to CFQ the UI lag is drastically reduced too. I'm not sure why since none of my other devices run best with CFQ!

The graphics performance in 4.3 is dramatically better than any 4.2 build was for me... UI transitions are generally smooth, Beach Buggy Blitz runs notably more smoothly and Candy Crush is every bit as slick as on the N7 or N10 now. This is pretty amazing progress compared to how awful the performance as a whole was in the early CM10.1 builds.
[Nook HD, HD+ Android Development] stephencwl:
Can we assume SanDisk emmc hd+ with this fstrim() reenabled ROM is safe?
[Nook HD, HD+ Android Development] sovanyio:
I get the boot hang too. Clearing just cache seems to do the trick... and forces us to sit through the "Android is Upgrading" screen whenever it happens :/
[Nook HD, HD+ Android Development] bpaulien:
Hey, just curious. I know you may not have had enough time to brick it yet, but was wondering how your "experiment" is going. I haven't had a chance to do anything with my HD+ yet, but since it's presumably easy enough to get a replacement, I think I'll do this, as soon as I get the time.

Keep us posted, I'm curious if you can get it to brick.
[Nook HD, HD+ Android Development] stevetrooper:
So no 8/22 Nightly for EMMC, something go wrong with the build last night?
[Nook HD, HD+ Android Development] SCWells72:
I installed it on mine as well and it's already helped tremendously to eliminate the lag that's built up over the past few days. Crossing my fingers for a brick-free future!
[Nook HD, HD+ Android Development] razholio:
Interesting. At least some 2012 N7's should have samsung parts or they wouldn't have released a samsung-specific fix. Not all HD+'s came with samsung flash. a few people on here have sandisk eMMC.

I'm glad you are seeing such performance improvements. I was very happy on the 7/19 10.1 build with the pure_performance mod. I can't say 10.2 is much better for me. it could be a bit, but it's hard to judge objectively. I haven't done much yet with it, but all my usual apps work just fine.

I just did a standard update from 10.1 -> 10.2 w/o wiping data. Is that what you did? I flashed the 10.2 firmware, then the 7/26 gapps, and then the 8/13 gapps, then wiped cache and dalvik cache. It hasn't given me any trouble so I figured I'm ok.

---------- Post added at 09:45 AM ---------- Previous post was at 09:41 AM ----------

sure. I just got it done last night so it hasn't had much time to brick itself. I've run lagfix once and rebooted, and I've moved some files around, updated via the play store and it is working well. I don't know that 10.2 is dramatically faster, perhaps a bit. I do notice, though, that eMMC I/O doesn't have the same lagging effect on the rest of the system. I was fooling around during the playstore update and it was more responsive than 10.1 would have been, and then I started a big upload in copy and moved over to download something in box and that also went well.

at the very least I'd say I/O performance is better in 10.2. I use 'deadline' as the I/O scheduler in both 10.1 and 10.2. the only mod I've done so far is to increase the screen DPI to 320.
[Nook HD, HD+ Android Development] verygreen:
There are no known problems with SanDisk parts.
[Nook HD, HD+ Android Development] razholio:
thanks for joining us. The higher the numbers, the more reliable the results. especially if their negative. How long do we have to run these w/o bricking/corruption before we feel confident that either the 32GB eMMC is bug free or the 'fix' is valid? I don't know, but I suspect it'll be a while...
[Nook HD, HD+ Android Development] rsanchez1:
I installed cm-10.2-20130821-NIGHTLY on my HD+ last night. This morning I had a weird problem with it. I use my HD+ as an alarm clock. When the alarm sounded this morning, I could not get the screen to turn on. It flickered on occasionally, giving me a glimpse of the lock screen, but promptly turned off again. I couldn't turn off my alarm without turning on the screen, so I had to force reboot my HD+.

Is this an issue with the 10.2 nightlies, or is there a way to fix this? Also, could it be a "feature" to prevent you from oversleeping? :laugh:
[Nook HD, HD+ Android Development] bpaulien:
Oh, really? I didn't realize there were 2 gapps files we needed to flash for 10.2. I was flashing the 8/13 gapps when I first used 10.2, before going back to 10.1. What's special about the 7/26 gapps?

That's good to hear. At least the I/O performance is good. I guess we'll also see if there's a difference between the 32G and 16G, since mine is the 16G version. Hopefully I'll get to this tonight, or sometime this weekend.
[Nook HD, HD+ Android Development] SCWells72:
For what it's worth, last night I (clean-)flashed the last official nightly CM10.1 build for the HD+ and the Kindle app didn't work there either. It looks like they updated it to 4.2.0 on August 14th or so and it seems to be causing issues on a number of devices. Is it possible that a slightly older official apk might work under our CM10.2 ROM until they resolve that? Does anyone have access to the previous version?

UPDATE: Unsurprisingly, the previous version (4.1.0.66) didn't work either. I imagine I could keep trying older and older versions, but the app works on both my phone (Galaxy S4) and iPad 3, so I have a workaround for it until the real issue has been resolved. Bummer, though...
[Nook HD, HD+ Android Development] brusyev:
Yep..this is a very annoying issue. Is this a result of improper flash or just a software bug?
[Nook HD, HD+ Android Development] Azurael:
I just dirty flashed from CarbonROM 10.1 followed by wiping contacts storage and clock app data, as I did going from 4.2 to 4.3 on all my other devices. No issues to report. I strongly recommend giving CFQ IO scheduler a go if you haven't already. The performance difference was quite staggering in my case.
[Nook HD, HD+ Android Development] brusyev:
Do you also set the CPU to on demand mode?
[Nook HD, HD+ Android Development] Reed-Sternberg:
Hangout force closes as soon as I enter one of my conversations. It's been the case in all nightlies so far. Anyone else has this issue? I had the same issue in 4.2.2 carbon ROM too.
[Nook HD, HD+ Android Development] rholm:
I've seen this... doesn't happen every time, but often.

Cheers,

Rich
[Nook HD, HD+ Android Development] brusyev:
It happens on every boot for me...Also the CM boot circle is shown to be distorted. Is there a way to disable the boot splash screen by modifying files?
[Nook HD, HD+ Android Development] foxorroxors:
Anyone got bladeslinger working. it fc when u meet/kill the first mob
[Nook HD, HD+ Android Development] digixmax:
I've been running 10.2 build dated 08/15 off SDcard, and twice in the last week I woke up the HD+ to find it operating in stock ROM!!! How that happened is a mystery, as the CM10.2 card was still fully in the slot intact and a reboot would bring up CM10.2.
[Nook HD, HD+ Android Development] Tom2112:
This happens every boot for me as well. I have to boot into recovery, clear the cache, and reboot. Then it goes through the updating process again and boots.
[Nook HD, HD+ Android Development] Azurael:
I'm using Hotplug. I don't think PowerHAL is working on this ROM. I found ondemand very laggy with its default settings (something like 95% load for scaling up as I recall) - presumably you'd only set it up like that if you were expecting PowerHAL to scale up the CPU in response to touch input. I found hotplug at its defaults gave better performance and a theoretical battery life increase (although that may be canceled out by the more responsive scaling...) so I didn't bother playing with the others. Remember to set IO IS BUSY to 1 as well, it's off by default with hotplug. I'm sure there's a battery life penalty for scaling in response to IO load but the awful performance of the eMMC in Android devices at the moment makes this a near necessity to maintain decent performance when loading apps or anything the involves heavy filesystem access but not necessarily high CPU load otherwise.
[Nook HD, HD+ Android Development] razholio:
Damn, dude, I think yer right about cfq. I'm very pleased with it so far. Have you had any stability issues?
[Nook HD, HD+ Android Development] monkey3ddd:
Was having issues in Chrome. Soft reboots, SwiftKey disappearing while typing. Grabbed the chrome beta and seems to have helped. Fyi.
[Nook HD, HD+ Android Development] brusyev:
I had several soft reboots on 08/20 but has been stable on 8/23....still testing it....
[Nook HD, HD+ Android Development] Azurael:
The TRIM-enabled 22nd build verygreen has proven stable for me set up as described. In fact it's been a good while since any of my devices suffered any form of instability. I never had soft reboots though, so I guess either it's a hardware quirk my NHD+ doesn't suffer or my usage model just doesn't trigger it.
[Nook HD, HD+ Android Development] Sherip:
I agree the new beta seems more stable. It also has a new feature for reducing bandwidth by compressing web page data routing them through Google's servers. I agreed to enable the feature until I realized it defeats Adaway. Then it took awhile to figure out how to turn it off again.

Sent from my BN NookHD+
[Nook HD, HD+ Android Development] Jack45:
FWIW, I haven't had an SD card mounted since my initial install of CM10.1 (now on 10.2 nightlies). Wonder what that "something" you refer to is.
[Nook HD, HD+ Android Development] leapinlar:
That happens when it does a spontaneous panic reboot, it boots directly to stock even if the SD is still inserted.
[Nook HD, HD+ Android Development] digixmax:
I am curious if it's possible to control/make "spontaneous panic" reboot to boot off SD?
[Nook HD, HD+ Android Development] leapinlar:
Yes, if you look at verygreen's SD thread he talks a lot about that since it was a problem with his early SD installs. He modified the kernel so that it would always boot to SD. But I think he removed that feature in his newer releases.
[Nook HD, HD+ Android Development] razholio:
I never saw instability with 10.1, either. This is a new phenomenon with 10.2, though it may be related to my ext4 SD card which is giving me issues, or my dirty upgrade.

---------- Post added at 11:43 AM ---------- Previous post was at 11:26 AM ----------

I reformatted my SD card to ext4 and it mounts, gets the fuse treatment and has 775 mode and root:sdcard_rw ownership just like the internal one. However, my apps throw write failures in any subdirectory on that card, and touch silently fails to create new files. Is there something I'm missing?
[Nook HD, HD+ Android Development] verygreen:
as promised before, here just kernel zips you can use with nightlies to reenable trim ioctl:

These are only for CM-10.2!

for ovation:

kernel-fstrim-ovation.zip

For hummingbird (also has 1.5GHz reenabled back):

kernel-fstrim-hummingbird.zip
[Nook HD, HD+ Android Development] YOUCANNOTDENY:
Disable "Wallpaper Quick Render" in Trebuchet Settings. This gave me many headaches before.

---------- Post added at 12:40 PM ---------- Previous post was at 11:56 AM ----------

Unfortunately, these links produce DNS errors. Can you fix them please?
[Nook HD, HD+ Android Development] verygreen:
indeed, should be fixed now
[Nook HD, HD+ Android Development] rushless:
Not yet seeing the value with 10.2 yet. More issues and still has the lag.

Thankful for a stable 10.1 :)
[Nook HD, HD+ Android Development] verygreen:
I am still waiting for your testing results on that game and a bunch of different kernels I made for you the other week.

Can you please dedicate some time to it?
[Nook HD, HD+ Android Development] :
Interesting. 10.2 is no more or less different than 10.1 for me. It feels so much the same that I wouldn't know if it smacked me in the face.
[Nook HD, HD+ Android Development] treubber:
For me the value is mainly in one feature. In 4.3 they modified the multiple user feature to include the ability to create a restricted profile. Since I will often let my kids play with the tablet, the restricted profile comes in very handy.
[Nook HD, HD+ Android Development] Odenknight:
Flash on 8-15-2013 release & Wifi analyzing apps

Question for anyone still running 8-15 release. Can you go to YouTube or bbc.co.uk and play any of the video's there? I went from the June update to 8-15, and was pleasantly surprised when I could play BBC video's and YouTube video's within Opera web browser, but was unable to after updating past 8-15. I'd like to get confirmation just to make sure that someone didn't lace my drinks with anything for that time period.

Also, I have read about an issue w/ wifi analyzers not updating when new hotspots appear. Is that something that can be fixed, but is just a low priority, or is there something we in the community can to to fix/work around it.

Thank you all for your help and knowledge.
[Nook HD, HD+ Android Development] bpaulien:
Mine is incredibly lagging to, in 10.2. I just tried installing it again the other day and I will probably go back to 10.1. Although I see the modified kernel was just made available, so maybe I'll check that out first. Then either back to 10.1,or maybe slimbean, it seems to work well.