[Android Software/Hacking General [Developers Only]] Lanchon:
Please read Post #2 for background info.

Post #3 discusses safety.

Post #4 lists affected devices and the status of their CyanogenMod ports.

Post #5 details the work needed to support a new device.

This is a work in progress. Please subscribe to this thread to keep up to date. More to follow soon.

Currently Supported Devices

Galaxy S II International (i9100)

Galaxy S II AT&T (i777)

Galaxy S II Epic 4G Touch (d710)

Galaxy Galaxy Note (n7000)

In Short

Brickbug fix by independent developers killed TRIM. Because of this, all devices -affected or not- running 'safe' custom roms end up slowing to a crawl with enough usage.

Samsung's later fix does not inhibit TRIM, but it is widely believed that their fix is incomplete and inadequate. I beg to differ and believe Sammy's fix could well be adequate, and I have good reasons for it. They are summarized in Post #3.

Which Devices Are Known To Be Affected?

Please refer to Post #4.

What To Do?

Make CyanogenMod builds for affected models where the indie fix is replaced with sammy's fix.

CLEARLY LABEL THEM AS DANGEROUS.

Is That Enough?

No, you need to actually invoke fstrim somehow. Android 4.3 and later automatically does so daily when left overnight to charge. You can invoke fstrim manually from a root shell, or just use this app instead. Also, there are scripts you can flash to fstrim on boot.

Are The Builds Safe?

It depends. Not all devices of a particular model known to be affected by brickbug carry the bug. If your device is brickbug-free, then yes, it is safe. You have been running crippled custom roms for ages now and you definitely want these builds to restore the speed and responsiveness of your device.

If your device is affected by brickbug, then it could be safe or not. I suspect yes, but testing is needed. Please refer to Post #3. You are strongly advised NOT TO TRY THESE BUILDS or else your phone could very well die forever. You have been warned.

How Do I Know If My Device Is Affected?

Use this app. Root is requested but not needed for this test. WARNING: Do not trust its verdict! Instead use the reported eMMC model name and the firmware revision (fwrev) to look up your eMMC in this table. Of particular concern is the TRIM bug supposedly present only in MAG2GA eMMCs.

How Do We Test Safety?

I hope some volunteer with an affected device and a partially cracked screen may show up. Also, I have a working Galaxy S2 i9100 display (dead mobo); if someone has an affected fully cracked S2 to donate, that could work. I live in Argentina, but I have friends in the US that come and go.

How Do We Test Performance?

Use Androbench. Make sure you have plenty of free space in your internal memory. Run it on your standard CM before switching to trim-enabled CM. Take a screenshot? Switch, trim the file systems, and rerun.

My Device Is Affected. My Device Is Too Slow. Is There An Alternative For Me To Restore Performance Now? I Do Not Want To Wait For This Project

Yes there is. But involves trade-offs. I will write about it soon.

XDA:DevDB Information

BrickbugAftermath, Tool/Utility for all devices (see above for details)

Contributors

Lanchon

Version Information

Status: Beta

Created 2014-07-21

Last Updated 2014-09-13