How do we know if we have the faulty emmc?

[Nolfer]

Hi there, noticed that you have the same eMMC as me, was wondering if anything new has been found or if you have had any issues? Am still on 10.1.3 CM but am feeling the some lag now so tempted to upgrade to the latest 10.2.... Thanks

I didn't have any issues when I used the 10.2 trim kernel.
if you have my chip you should be clear and should definitely do the upgrade to 10.2 and flash the trim kernel. However, remember that you do so at your own risk blah blah blah. (you should be all right) :silly: :silly:
You can also check the bug status of the various chips in the wiki page http://wiki.cyanogenmod.org/w/EMMC_Bugsmod
you can safely assume that my nook and yours should be brick free:highfive:

 

[twe69]

I didn't have any issues when I used the 10.2 trim kernel.
if you have my chip you should be clear and should definitely do the upgrade to 10.2 and flash the trim kernel. However, remember that you do so at your own risk blah blah blah. (you should be all right) :silly: :silly:
You can also check the bug status of the various chips in the wiki page http://wiki.cyanogenmod.org/w/EMMC_Bugsmod
you can safely assume that my nook and yours should be brick free:highfive:

Cool, did a bit more reading and seemed fine, so am glad you replied too!

I was thinking of the Carbon Rom on Android 4.3 though.

 

[Jann F]

Jann F,

I have the same module as you. Do you have anything new to report? Are you still using TRIM? Is all OK with you Nook?

I'm running CM 10.1.3 and had lag. Leapinlar suggested in another thread to format 'data and mediadata' thru CWM. I did this and it fixed my lag however, I had to re-register with CM, and allow play store to reinstall some apps and manually reinstall other apps w/Apps Back-up and Restore. While i am happy with the results, this is not something i wish to do on a regular basis.

So, do you recommend using TRIM while staying away from the SECURE ERASE command?

Thanks,
josim

I still use the TRIM Kernel with CM10.2 and had some random reboots (1 per week), but I don't think it has something to do with TRIM.

 

[Nolfer]

Cool, did a bit more reading and seemed fine, so am glad you replied too!

I was thinking of the Carbon Rom on Android 4.3 though.

I think I will get back to 4.3 too. 442 is still unstable for daily use IMHO. I'll do that with my arc s too.

 

[oboefiend]

I think I will get back to 4.3 too. 442 is still unstable for daily use IMHO. I'll do that with my arc too.

Which 4.4.2 ROM are you using? I'm running succulent's build and its very stable, more so than CM 10.2 IMO. I haven't had a single reboot in the 2 weeks I've been using it.

 

[Nolfer]

Which 4.4.2 ROM are you using? I'm running succulent's build and its very stable, more so than CM 10.2 IMO. I haven't had a single reboot in the 2 weeks I've been using it.

I'm not talking about random reboots. I'm talking about general performance. Audio from the jack is aweful, google search lags, some fc, general sporadic lag, battery life, some bugs. I'm using the the same, installed via internal storage, but I feel like getting back to the most stable one for these motives. Is trim enabled in the 4.3 carbon?

 

[oboefiend]

I'm not talking about random reboots. I'm talking about general performance. Audio from the jack is aweful, google search lags, some fc, general sporadic lag, battery life, some bugs. I'm using the the same, installed via internal storage, but I feel like getting back to the most stable one for these motives. Is trim enabled in the 4.3 carbon?

That's strange...this has been the most stable ROM I've found for the HD+ and I haven't had any of the issues you described. Anyway, I believe TRIM is disabled in the 4.3 Carbon build.

 

[Nolfer]

That's strange...this has been the most stable ROM I've found for the HD+ and I haven't had any of the issues you described. Anyway, I believe TRIM is disabled in the 4.3 Carbon build.

Hehehehe... I present you here the final solution: The work linked here contains touchscreen fix and trim enabling (I tested it when I was running the old 10.2 and they both worked)

http://forum.xda-developers.com/showthread.php?t=2562499

No need to thank me... No need at all...

 

[oboefiend]

Hehehehe... I present you here the final solution: The work linked here contains touchscreen fix and trim enabling (I tested it when I was running the old 10.2 and they both worked)

http://forum.xda-developers.com/showthread.php?t=2562499

No need to thank me... No need at all...

Looks like Succulent already merged this with his build of CM11.

 

[Nolfer]

Looks like Succulent already merged this with his build of CM11.

I'm sorry are you talking about carbon rom? Because I've been on the carbon thread right now and he only mentions the possibility to flash a trim kernel.

Anyway I kinda need help, I funked up. This is not exactly on topic but I think this is a stupid problem. went to my nook Cwm recovery and factory resetted, formatted system cache and data, and when I selected install zip from sdcard the recovery couldn't find the sd anywhere. It was like sdcard/0, and then after this 0 directory there was another 0 directory similar to the other one, like every flash of new roms left its android skeleton structure and the new ones installed theirs inside that. In all of this I couldn't find the sd card with the new rom files that I just transferred via USB before doing the format. It's like it has a simulated sd card, and cannot read the real one. Any help?

 

[oboefiend]

I'm sorry are you talking about carbon rom? Because I've been on the carbon thread right now and he only mentions the possibility to flash a trim kernel.

Anyway I kinda need help, I funked up. This is not exactly on topic but I think this is a stupid problem. went to my nook Cwm recovery and factory resetted, formatted system cache and data, and when I selected install zip from sdcard the recovery couldn't find the sd anywhere. It was like sdcard/0, and then after this 0 directory there was another 0 directory similar to the other one, like every flash of new roms left its android skeleton structure and the new ones installed theirs inside that. In all of this I couldn't find the sd card with the new rom files that I just transferred via USB before doing the format. It's like it has a simulated sd card, and cannot read the real one. Any help?

I'll pm you; I don't want to hijack the thread.

 

[Nolfer]

Looks like Succulent already merged this with his build of CM11.

I'm sorry are you talking about carbon rom? Because I've been on the carbon thread right now and he only mentions the possibility to flash a trim kernel.

Anyway I kinda need help, I funked up. This is not exactly on topic but I think this is a stupid problem. went to my nook Cwm recovery and factory resetted, formatted system cache and data, and when I selected install zip from sdcard the recovery couldn't find the sd anywhere. It was like sdcard/0, and then after this 0 directory there was another 0 directory similar to the other one, like every flash of new roms left its android skeleton structure and the new ones installed theirs inside that. In all of this I couldn't find the sd card with the new rom files that I just transferred via USB before doing the format. It's like it has a simulated sd card, and cannot read the real one. Any help?