yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] chrone:
It's not google's fault,

It's the nand chip's characteristic. Your mile may vary.

Mine was only slowed down to 5Mbps sequential write speed coming from 7Mbps.

It's a characteristic of the eMMC chip itself, even the most advanced and expensive nand chip inside the eMMC will have slow down sequential and random write performance. Current smartphone didn't implement controller to do garbage collection in order to reduce this slow down like it is on SSD. Hope someday it will.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Jar3112:
About this, how to check the actual read-ahead set in the phone? Do I have to search for it in build.prop?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] DriftGT:
What I need to do to increase my performance? What I need to delete que you explain to me?

A have now 2GB free and my androbech is:

Sequencial Read: 23.98MB

Sequencial Write: 1.63MB

Random Read: 8.75MB

Random Write: 0.13MB

This is to low, V3U00M I want to kill you dammit.

Give me some tips pls
[Samsung Galaxy Nexus] Jar3112:
Have a look,with some search you would have found it! :D

http://xdaforums.com/showthread.php?t=2029246

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chrone:
Just out of curiosity, how about to delete files to get 4GB free available storage and reboot. Will it increase your sw and rw performance?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] DriftGT:
I flash 4.2.1 again and now I have the normal speed
[Samsung Galaxy Nexus] KaiZ51:
But did you actually fill up the memory again to test if the problem has been permanently resolved?
[Samsung Galaxy Nexus] Sytheii:
interesting.
[Samsung Galaxy Nexus] chrone:
He doesn't have to. It will slow down in time since he just reset to factory. If he happens to have V3U00M eMMC chip, the slow down will be quite big.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] DriftGT:
Right. I dont want to fill it. If I do that I think my phone will became slow again.

I hope Google solve the problem quickly :( this is very annoying.

The speed is too dam low :(
[Samsung Galaxy Nexus] klau1:
Does the problem of Write Amplification apply to all devices?

I accidentally filled up my Galaxy Note 10.1 with garbage and deleted it.

Now I have 21.17GB free out of 25.87GB

How can I prevent Write Amplification in Android without wiping everything?

I don't know what the original results were but here is the current:
[Samsung Galaxy Nexus] chrone:
It is known that all nand chipsets have write amplification and slow down on sw and rw performance at some level. Each type of chipset is vary.

As per anandtech's article, leaving a 25% free space will help maintain the performance consistency. I always left 4gb free space on my gnex and the slow down only down to 5mbps sw from 7mbps. My eMMC chip is VYL00M rev.0x25. While others who have V3U00M chip are having slow down sw down to 1mbps.

Your benchmark is way much better than gnex at it's optimal. No worries then. :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] skoolkaholic:
I have same promblem here,

V3U00M

8/12

random write :

< 6 GB = 0.51 MB/s

< 2 GB = 0.21 MB/s

< 720 MB = 0.11 MB/s

after delete some files, androBench take long time to finish

random write become 0.07 MB/s

I'll try flash 4.2.1, hope the speed will be normal again :(
[Samsung Galaxy Nexus] chrone:
Ouch, that gotta hurt. :P

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] markop90:
Tried discard mount option?
[Samsung Galaxy Nexus] skoolkaholic:
haven't do that. will it make any difference ?

I've flash my phone to 4.2.1 stock rom.

and still got around 0.58 MB.
[Samsung Galaxy Nexus] chrone:
It will maintain the drop sw and rw write performance as minimum as possible since it avoids keeping deleted files marked as deleted and delete instantly, hence no garbage collection, stable subsytem storage input output and less cpu cycle usage.

But be careful, affected brick bug eMMC chip is not recommended doing this method. Check your eMMC nand chipset first. The safe chipset currently is the VYL00M rev. 0x25.

Don't forget to fill all your available space with dummy data and delete the dummy afterward.

Normal sw is around 7mbps, and rw is around 0.25mbps.

Hope this helps. :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] skoolkaholic:
mine :

V3U00M

8/12

Revision : 0xD

I dont think I'll do that if there is a chance of brick. since i got this phone only 3 weeks ago.

I think I'll live with this speed and make sure doesnt fill up too much on storage.

hope next update will resolve it soon
[Samsung Galaxy Nexus] Jar3112:
If you download the brick bug test app from play store you can check whether you have it or not, but I'm pretty sure you shouldn't have.

If the app tells that you are brick bug free then use this method, will work perfectly.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ph4zrd:
This chip is exactly the type affected by the slowdown problems.

It doesn't have the brick bug and many users (including me) applied the workaround successfully.

Guide/Workaround

Google Code Issue
[Samsung Galaxy Nexus] rnjsgurwn96:
Here are my results. I have 6GBs left. Using stock yakju 4.2.1 with franco kernel and fsync on. I don't get why the write speeds show up so high.. I haven't done any tweaks
[Samsung Galaxy Nexus] Jar3112:
Fsync must obviously be off. Check it better

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chrone:
and here's nexus 4 16gb storage performance with 5gb available on the left and 1gb available on the right.

the slow down still dropped like a free fall. hehe *ouch :(

Sent from my Nexus 4
[Samsung Galaxy Nexus] markop90:
Here in Italy nexus 4 won't arrive...damn :'(

Inviato dal mio Xteam Smartpad 810c con Tapatalk 2
[Samsung Galaxy Nexus] chrone:
i tested with the nexus 4 16gb nearly full on my post above. the dropped performance is there. :(

sw from 10 MBps to 4 MBps

rw from 1 MBps to 0.39 MBps

did a reboot and the performance is getting better.

sw from 4 MBps to 9.89 MBps

rw from 0.39 MBps to 0.51 MBps
[Samsung Galaxy Nexus] lesp4ul:
Even thou i feel no prob with my previous setup, it is no harm to test the script i think. I also tweak some kernel setting too. After some tries, finally i chose this setup:

i9250 yakju, V3U00M

Space about 5.2GB

Discard ON (init.d)

Paranoid Android 2.9b999 (4.2.1)

Modded Trinity Kernel by Dax

Stock freq, no UV, cfq/interactive, fsync ON, read ahead 896.

Small RW increase with 1024 read ahead buffer, but sacrifices some SW.

The result before applying script, buffer 1024 as kernel default.

Plase correct me if my setup is wrong :)

EDIT: i noticed a huge startup time decrease. Usually Startup Manager reported about 57-59 seconds, few moments ago it reported 47 seconds. So i try again now with my stopwatch and YES i can confirm it. :thumbup:
[Samsung Galaxy Nexus] chrone:
Nice setup there! :D

Sent from my Nexus 4
[Samsung Galaxy Nexus] lesp4ul:
Thanks to you for sharing :)
[Samsung Galaxy Nexus] AuxLV:
I've compiled fstrim for Android and packaged it inside APK with nice GUI. You can find LagFix tool here. It is much better then backing up and formatting /data. And A LOT faster too!
[Samsung Galaxy Nexus] chrone:
whoa thanks for this! i've reached my thanks limit just now. lol.

will sure try this later. awesome! :)

it works! #1 post updated.

Before and after filling up the storage (coming from 5GB and filling it up to 1.2GB space available):

SW from 10 MBps to 4 MBps ~ 60% loss

RW from 1 MBps to 0.39 MBps ~ 61% loss

Did a reboot and the performance is getting better (1.2GB space available, deleted some files left with 2.2GB space available but the performance is more less the same):

SW from 4 MBps to 9.89 MBps ~ 147% gain

RW from 0.39 MBps to 0.51 MBps ~ 31% gain

Using the fstrim app (LagFix for Nexus 7 and HTC One X) and reboot (2.2GB space available):

SW from 9.89 MBps to 9.9 MBps ~ 0.1% gain

RW from 0.51 MBps to 1.07 MBps ~ 110% gain
[Samsung Galaxy Nexus] lesp4ul:
Re: Galaxy Nexus Storage Performance Over Time & TRIM

Wow that is one big write results, badass!!! Mine never reached 0.6 for RW haha.
[Samsung Galaxy Nexus] chrone:
haha yeah it is, one of the main reason why i jumped to nexus 4 bandwagon. :D
[Samsung Galaxy Nexus] tiny4579:
Re: Galaxy Nexus Storage Performance Over Time & TRIM

We're still out of stock for nexus 4. I'm jealous of your io performance.
[Samsung Galaxy Nexus] TheMysteriousOne:
Am about to buy a GNex. Can someone tell me what I should look out for to make sure I don't get a phone with performance issues?
[Samsung Galaxy Nexus] markop90:
R: Galaxy Nexus Storage Performance Over Time & TRIM

Random write grew up from 0.3 to 0.5 with your app!!! Thanks!!
[Samsung Galaxy Nexus] chrone:
sweet!! did you use the discard with fstrim too like les4paul? a killer combination for storage performance consistency. :)
[Samsung Galaxy Nexus] markop90:
R: Galaxy Nexus Storage Performance Over Time & TRIM

Yep :)
[Samsung Galaxy Nexus] AuxLV:
Glad to hear it!
[Samsung Galaxy Nexus] ph4zrd:
AW: Galaxy Nexus Storage Performance Over Time & TRIM

You can't tell if it is one with the affected chip until you get the issues or check with an app (e.g. brickbug check) :/
[Samsung Galaxy Nexus] alexflash:
On my tab 7.7 with Paranoid 2.50 (Android 4.1.2):

fstrim: FSTRIM: Operation not supported on transport endpoint.

both for /data and /cache

Why do I get this error?

P.S. Sorry, my post must be in another thread )
[Samsung Galaxy Nexus] chrone:
Re: Galaxy Nexus Storage Performance Over Time & TRIM

I really have no idea why, whether the emmc didn't support it or your kernel. Let's ask AuxLV. :)

Sent from my Nexus 4
[Samsung Galaxy Nexus] ph4zrd:
Possibly because it is disabled in the kernel as the 7.7 is known to have the eMMC brick bug ;)

[Notice] Tab 7.7 Contains Brick Bug Vulnerability - Check for yourself with new app!
[Samsung Galaxy Nexus] backfromthestorm:
Here is a flashable zip to trim /data and /cache if anyone would like it.

Flash like any other zip from recovery.

Check recovery log in sd for details on bytes trimmed.

I dont see any point whatsoever in trimming /system

https://www.dropbox.com/s/y5o4omqhapulf2b/Trimmer_Backfromthestorm.zip

Only tested on my One X. Shouldnt be any different on a Nexus though. Feedback would be great from testers..

Edit - Heres an updated version - should work on roms without busybox installed.

https://www.dropbox.com/s/6ctn90ra3x8p0y1/Fstrimmer_CWM.zip
[Samsung Galaxy Nexus] chrone:
Re: Galaxy Nexus Storage Performance Over Time & TRIM

Aha, that's more likely. :thumbup:

Thanks dude! :)

care to add fstrim on /system too? apps logging, database works related, apps install-uninstall-reinstall is happening on the /system i believe, so it needs to be fstrimmed too. :D

Sent from my Nexus 4
[Samsung Galaxy Nexus] nitrogen618:
Re: Galaxy Nexus Storage Performance Over Time & TRIM

What setting do you guys benchmark with? I use the all button and I get totally different results..
[Samsung Galaxy Nexus] chrone:
i chose all on androbench. the slow down only appear if you have utilized all of your storage. i do fill in my storage with tv serials, watch it, delete it, and fill it up again and again. thus having fstrim on my phone does improve the storage subsystem performance back to normal. :)
[Samsung Galaxy Nexus] KaiZ51:
Re: Galaxy Nexus Storage Performance Over Time & TRIM

I haven't really been following this thread but... Have you guys found a solution to the problem yet?

I saw your post with the zip file so maybe yes... I don't know what Fstrim is so does it have any negative symptoms by flashing your zip? How do I undo it in case I want to?

Also I've currently got the discard script running at boot, should I disable that if I flash your zip?
[Samsung Galaxy Nexus] chrone:
Re: Galaxy Nexus Storage Performance Over Time & TRIM

Or you could use the lagfix (fstrim) on Google play as posted on the first post. :)

I've checked the script and it is fine. Only do the fstrim command to /data and /cache and afterward write the recovery log onto your sdcard, that's all. You could google what fstrim does to your storage, but as for me, it only does the garbage collection of your "marked as deleted" files in your storage, hence less input/output and more consistent performance as in new drive.

Sent from my Nexus 4
[Samsung Galaxy Nexus] Jar3112:
R: Galaxy Nexus Storage Performance Over Time & TRIM

Also free on xda

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] backfromthestorm:
System trim - https://www.dropbox.com/s/91site2hr3...im_sys_CWM.zip

Data trim - https://www.dropbox.com/s/053a73xczn...r_data_CWM.zip

As requested, fstrim zip to trim data, cache AND system from recovery in first zip.

I would recommend just trimming data and cache, as system isnt written to on a continual basis during normal use of rom, so even if it required trimming it wouldnt be noticable. Plus of course its trimmed when its formatted when roms are flashed.

Again, check amount trimmed in recovery.log on sd.

This is the same as the lagfix app, only its for running through recovery, so you dont need to reboot afterwoods like when youve used the app, and you can use it after transfering large files, flashing many mods etc when youre already in recovery. Just another way of fixing the same problem.
[Samsung Galaxy Nexus] chrone:
Re: Nexus Storage Performance Over Time & TRIM

Thanks, dude! Will update the first post once back on PC. :thumbup:

update:

i found the links above were invalid, so here's to quote from backfromthestrom original thread:

http://xdaforums.com/showpost.php?p=37034130&postcount=27

Sent from my Nexus 4
[Samsung Galaxy Nexus] backfromthestorm:
Dropbox is a pain in the ass.

System - https://www.dropbox.com/s/91site2hr31kuf3/Fstrim_sys_CWM.zip

Data - https://www.dropbox.com/s/053a73xcznmxv60/Fstrimmer_data_CWM.zip
[Samsung Galaxy Nexus] xaueious:
Any idea why this doesn't work well on VYL00M?

My Androbench is showing random write at 0.24 MB/s.
[Samsung Galaxy Nexus] markop90:
R: Nexus Storage Performance Over Time & TRIM

/system partition is read only, so apps cannot write in it (unless you have root and the app is intended to modify system related components, like theming, deodexing and whatsoever)...databases, log streams and so on are written in /data partition
[Samsung Galaxy Nexus] chrone:
Re: Nexus Storage Performance Over Time & TRIM

It's the normal random write speed for vyl00m.

It's flashed from CWM recovery so mounting system with write access is kind of easy once the bootloader is unlocked.

How about system apps that came preinstalled, it will also gain improvement. I always fstrim system, data, and cache, and my phone is as snappy as it was out of the box, kudos for the lagfix app. Hehe

Sent from my Nexus 4
[Samsung Galaxy Nexus] landwomble:
Re: Nexus Storage Performance Over Time & TRIM

Holy crap. This is awesome. Been plagued with lag on my one x throughout its life and this just fixed it! Been on multiple roms and they all eventually go laggy, probably due to lots of pics stored on my sd card. This worked like a charm. Thanks! Been poking for the last year for a fix!
[Samsung Galaxy Nexus] chrone:
glad it helps. kudos to AuxLV and backfromthestorm. :)
[Samsung Galaxy Nexus] backfromthestorm:
What did you use? The zip or app?
[Samsung Galaxy Nexus] chrone:
one more question before i flash, will removing the /tmp uninstall your fstrim package?

Update:

it worked using your cwm fstrim on system, data, and cache on nexus 4.

but i could not find any log on /sdcard :D
[Samsung Galaxy Nexus] backfromthestorm:
/tmp from where?

I wouldn't remove anything, just flash it as any other zip. I've made it so it should work on unrooted roms but not tested it on those.

You can always see what's going on by looking in recovery.log

Oh I see what you mean... it doesn't install anything! Nothing gets installed, all it does is run fstrim from recovery, it just uses tmp/ as a place to run fstrim from for twenty seconds, then it's gone..
[Samsung Galaxy Nexus] chrone:
oh i see, it runs on the ramdisk. lol. :D

i found the log. it seems on android 4.2.1 the /sdcard is on /data/media. i have to move it to /sdcard to see it listed in es file explorer or windows explorer. great i guess it works! :)

tested on 1.74gb space available:

SW: 10MBps

RW: 0.73MBps

almost near to stock performance, just lacking a bit on the RW section. well done! :)
[Samsung Galaxy Nexus] backfromthestorm:
Ok, If your theres no log on sdcard, ill need to know where the recovery log is on the nexus. Have a look in cache/recovery/ there should be a log in there.

Edit - your on 4.2 then, thatll be why. Glad you found it.

Now check the log to see if it worked. Hopefully it did. If it didn't, it'll just have to be for the one x for now.
[Samsung Galaxy Nexus] CADude:
Re: Nexus Storage Performance Over Time & TRIM

OK I ran the Lagfix app yesterday and I definitely notice that my animations are smoother and the keypresses are more responsive.
[Samsung Galaxy Nexus] chrone:
here's my log. care to look at it?

nice to hear that! :)
[Samsung Galaxy Nexus] backfromthestorm:
about to run program [/tmp/fstrim] with 3 args

trimming cache

565686272 Bytes was trimmed

about to run program [/tmp/sleep] with 2 args

trimming dataabout to run program [/tmp/fstrim] with 3 args

1210425344 Bytes was trimmed

about to run program [/tmp/sleep] with 2 args

about to run program [/tmp/fstrim] with 3 args

242970624 Bytes was trimmed

Success!
[Samsung Galaxy Nexus] chrone:
Re: Nexus Storage Performance Over Time & TRIM

Great! the about to run text is lagging behind. Lol

Sent from my Nexus 4
[Samsung Galaxy Nexus] backfromthestorm:
Yeah doesnt matter. Only the log. That's what the sleep is for. You can change it to sleep 10 if you like, give it time to write, but it's bad enough waiting 15 seconds lol.

It's only a pointer as to weather the fstrim is working and it is.

Excellent.
[Samsung Galaxy Nexus] chrone:
much appreciated for your work, dude! :)
[Samsung Galaxy Nexus] landwomble:
Re: Nexus Storage Performance Over Time & TRIM

App. System gets flashed with new rom quite frequently...
[Samsung Galaxy Nexus] chrone:
after reading some posting on the lagfix app, i have a new thought on the notorious samsung emmc brickbug, and how come trim or fstrim prolong our nand chipset lifespan. so without further ado:

the eMMC brick bug on samsung devices might be related with its own ssd department too. more info about this firmware bug in anandtech site here.

me myself often wonder how come almost all review sites told us to trim in order to prolong the nand chipset lifespan and improve performance. i think i finally found a link to confirm that trim/fstrim does improve nand chipset lifespan by reducing the write amplification.

without trim: storage is nearly full (used, free, and mark as deleted block), and you need to write a bunch of new files which exceed the free available block, the system must do this cycle: read the mark as deleted blocks, erase the mark as deleted blocks, modify the free available block, and write the new files.

with trim: storage is nearly full (used, trully free available), and you need to write a bunch of new files, the system just do this cycle: write the new files, hence less write amplification, longer lifespan and much faster write performance. :D

the trim command and secure erase are somehow very well explained in this write amplification article on wikipedia here.

resources:

http://www.anandtech.com/show/6503/second-update-on-samsung-ssd-840840-pro-failures

http://www.anandtech.com/show/6489/playing-with-op

http://en.wikipedia.org/wiki/Write_amplification

http://en.wikipedia.org/wiki/TRIM

http://en.wikipedia.org/wiki/TRIM#SD.2FMMC

http://en.wikipedia.org/wiki/Solid-state_drive

https://patrick-nagel.net/blog/archives/337
[Samsung Galaxy Nexus] Garridon:
Re: Nexus Storage Performance Over Time & TRIM

You have no idea how much this made my nexus 7 faster. It kept freezing while on the browser and in quadrant it took a good two minutes to get past the I/o test. Now it blazes through everything!
[Samsung Galaxy Nexus] ph4zrd:
In fact, Samsung f***ed up their SSDs wear leveling / TRIM code quite often.

For information about the brick bug on Samsungs phones, I recomment reading the following articles:

http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/

http://xdaforums.com/showthread.php?t=1644364

There were two bugs in the eMMC firmware produced by Samsung:

1) When using secure erase on chips with the "super brick bug" aka fw rev 0x12 or 0x19, the firmware screws up the internal data structures so that the chip locks up every time the affected blocks are read. The issue with 840 series SSDs sounds very similar to that. Samsung worked around it by disabling secure erase in the kernel code for these chips.

2) The "patched" firmware 0x25 had another bug, inserting 32KB of zeros in the storage sometimes. This was resolved by a kernel patch which modifies the eMMC firmware on every boot.

I think the eMMC slow down issues with V3U00M can be called the next bug in this series :D
[Samsung Galaxy Nexus] nihalot:
Can anyone post the results they got with their galaxy nexus?

My results are not even close to the op's results even with fstrim
[Samsung Galaxy Nexus] chrone:
Re: Nexus Storage Performance Over Time & TRIM

First post attachment was from galaxy nexus:

SW: 7MBps

RW: 0.25MBps

I updated the first post so it's easier to diff which one is Galaxy Nexus and which one is Nexus 4. Sorry for the confusion. :D

Sent from my Nexus 4
[Samsung Galaxy Nexus] mfbgeo:
Galaxy Nexus, Stock Rom, franco nightly 358, encrypted
[Samsung Galaxy Nexus] adlx.xda:
Re: Nexus Storage Performance Over Time & TRIM

Galaxy Nexus, stock 4.2.1,with Faux 25b5, IO scheduler SIO, 512 read ahead. To be honest, I'm quite impressed by the results, far far more than previous comment!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] markop90:
R: Nexus Storage Performance Over Time & TRIM

Encrypted partition, as I've understood, cannot be trimmed, and your results are really low!

---------- Post added at 03:22 PM ---------- Previous post was at 03:21 PM ----------

Fsync is off in your kernel...enable it and redo the benchmark
[Samsung Galaxy Nexus] adlx.xda:
I've got Dynamic File Sync [ON] (during previous Benchmark also). Is it what you mean?
[Samsung Galaxy Nexus] chrone:
whoa a dynamic fsync? how does it work? a really cool feature to have! :)

seems encrypted storage slows down the write performance like a lot, lack built-in encryption encoder/decoder chipset on the eMMC perhaps?
[Samsung Galaxy Nexus] adlx.xda:
I don't have much info about how it works.

It says: "while screen is on, file sync is temporarily deferred. when screen is off, a flush is called to synchronize all outstanding writes"

<6>[20293.781646] dyn_fsync_active_store: dyanamic fsync disabled

<6>[20297.140747] dyn_fsync_active_store: dynamic fsync enabled

# cd /sys/kernel/dyn_fsync

# ls -al

-rw-rw-rw- root root 4096 2013-01-24 16:40 Dyn_fsync_active

-r--r--r-- root root 4096 2013-01-24 16:40 Dyn_fsync_earlysuspend

-r--r--r-- root root 4096 2013-01-24 16:40 Dyn_fsync_version

# grep . *

Dyn_fsync_active:1

Dyn_fsync_earlysuspend:early suspend active: 1

Dyn_fsync_version:version: 1

btw, kernel is 3.0.60-tuna-faux123-jb-025+ #198 (beta5)
[Samsung Galaxy Nexus] mfbgeo:
Well ok, that may be the reason why LagFix is not working on my devide...

So I'll have to reflash stock again...

kind of liked the encryption in case of losing the device :/
[Samsung Galaxy Nexus] jericho7:
This application changed my life, or the life of my GN at least. I was ready to give up on my device after multiple ROMs and tweaks, I was beginning to think something in the hardware had failed. Now it's running better than ever
[Samsung Galaxy Nexus] Jar3112:
R: Nexus Storage Performance Over Time & TRIM

This app works great! Only one thing..

If I put a script in init.d folder running the trim command at every boot will this work as well?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] AuxLV:
Should work. Test it (:
[Samsung Galaxy Nexus] Jar3112:
R: Nexus Storage Performance Over Time & TRIM

Uhm, got an output saying "fstrim was not found".. :confused:

Sent from my Galaxy Nexus