[General Omni Discussion] Lanchon:
actually i think the maintainer of the fire or fire hd enabled trim ages ago in the official builds without any problems.

the fact that samsung lies has nothing to do with technical matters and is not evidence for or against safety. about a year ago i tried to argue with you that there are technical reasons to believe that nonsecure erase is safe. i laid out the bare-bones of a flash translation layer implementation, similar to what the eMMC firmware must be implementing, detailing the steps needed for each eMMC operation.

i did this to show you that there is a huge difference in complexity of secure and nonsecure erase implementations, enormous. in particular, i wanted to show you that 1)the implementation of nonsecure erase is a *strict subset* of the implementation of write. and if write doesn't brick, so shouldn't nonsecure erase. (btw secure erase is not a subset of write, and is much, much more complex.)

you never replied to that message, it was very long of course and i supposed you never read it.

now couple this with other facts such as:

2)no bricks ever reported on fixed samsung firmwares

3)fire (hd?) official CM using trim without problems

4)samsung *actually finding the bug* in their firmware (as evidenced by the bug being squashed in newer firmwares) and then choosing to disable only secure erase/trim/discard in their kernel fix, going against the gospel of the whole xda community that had disabled secure and nonsecure version to fix the problem before that.

5)samsung doing what appears to be a stopgap interim fix disabling both secure and nonsecure commands, then later reverting that fix (see note below)

6)samsung actually saying that only secure commands are affected (though yes, they are liars)

i, though not a CM maintainer and contrary to your belief, did research this matter enough to have a clue i think. and my clue was that it was worth a shot. very responsibly i started testing nonsecure erase (for first testers i only accepted shattered glass or lost IMEI phone) and in time found that nonsecure erase is totally safe for brickbug affected devices. many people just didnt mind the risk: with their devices so slow, they were ready to dump them in the trash anyway. and now they are happy again and don't need a new phone. you can add this to the list:

7)hundreds of people have been using my trim-enabled kernels for months on i9100 d710 n7000 and i777 without any issues.

note: i realize 5) is not documented anywhere so ill mention it here. we found that certain post-brickbug "sane" (fixed) eMMC firmwares where a)not changing their performance characteristics *at all* after trim (tested by androbench), and b)"trimming" in zero time instead of the usual couple of seconds these eMMCs typically take. it seems samsung did a stopgap "fix" disabling all (secure and nonsecure) erase/trim/discard commands in a few eMMCs before they actually found and fixed the real bug. one must assume they followed XDA's practice and disabled everything. when they later found the real bug, they finally output their fixed kernel and started producing fixed and capable eMMCs. unfortunately there is not way to trim that batch of eMMCs and those device owners are kinda screwed.

of course this is a short account and there are many other bugs than brickbug itself. right now i feel that only one bug remains to be properly tested before i push for the inclusion of trim in official kernels: MAG2GA TRIM bug. some devices (i think d710), very few apparently, have this chip. so far 2 showed up and none was tested. note that the stock nexus 7 2012 has this chip and trims with samsung's kernel fix for it and is totally safe. but the d710 devices have a different firmware version (newer than the N7 fw) so trim, though very likely to be safe, can't really be pushed wide open yet. (but i feel it's time to push for TRIM on other devices.)

i documented everything in cases someone is interested. google i9100 trim kernel and go from there, there are a bunch of threads. i'm not a lonely cowboy going around and enabling trim: i researched, organized and tested, and the result is success. i did this because no one else dared. i don't have these devices but some friends do, and i always thought this could be fixed. in retrospect i should have done this sooner. i understand you have emotional issues with the whole ugly brickbug saga you found yourself in the middle of at the time, and you just want no part of it now, but that's no reason to call anybody following a rational systematic approach to this issue clueless.

i'm surprised by the "pile of issues" you mention for the N7000. i though the 4210 family devices were basically identical. do you mean that the i9100 builds have the same issues? thanks!