Thanks!
Just having a few days holiday to play with the sources again...
If you meant the MMC_CAP_ERASE flag, cm's kernel never have this flag enabled. I think the revert you meant would be adding the flag to those two files. I'm not sure if all faulty chips have been included but using the custom recovery would be eMMC brick safe.
I'll try and see if fstrim works again. Thanks.
Edit: Just checked, the cm kernel source already has similar codes inside block.c.
Hi Daniel,
Appreciate your reply. Thanks.
In my ICS kernel, for extra safety, I have both:
1. Removed ref to mmc cap erase : https://github.com/UpInTheAir/P681...mit/dfc97a2ed8c9f6b886de1cced2e35a2fd1cdeb91
and
2. Samsung patch implemented : https://github.com/UpInTheAir/P681...mit/f9d69ae2246571f4cd80337711953acab2d63092
I know this prevents the fstrim app from working. Not sure if the removal of mmc cap erase alone prevents the fstrim app working, but I know the patch definitely does (like it's supposed to do).
EDIT: Found this, maybe this is what you're referring to ??
https://github.com/CyanogenMod/android_kernel_samsung_smdk4210/commit/cb9622bef4174f63bbb8e91099dddd50e5db94b0 BUT, I don't see it in the JB branch......
Sent from my GT-I9500 using XDA Premium 4 mobile app
Last edited: