POST A COMMENT

46 Comments

Back to Article

  • GuniGuGu - Monday, July 29, 2013 - link

    This was a great find in your N7 review.. I'm really curious how this affects performance. I sold my n10 already, but I will say it was even slower than my n7 (2012) in certain operations. Reply
  • Brian Klug - Monday, July 29, 2013 - link

    The Nexus 10 I had started slowing down as well. I wiped it, but I think if I had let it get this OTA I would've seen performance improve as a result, since I filled that device with videos and deleted them to add more quite often (great for watching stuff on a plane).

    -Brian
    Reply
  • jt122333221 - Monday, July 29, 2013 - link

    Now you are making me NOT want to sell mine. I picked up the new N7 for portability (I had the old one and used it much more than my N10) and was planning to sell mine to pick up the cost of the new one. Reply
  • Flunk - Monday, July 29, 2013 - link

    They also seem to have done something to improve graphics acceleration in chrome and in the launcher even more. That's my first perception upon installing the update on my Nexus 10. It really feels like a high-end device now. Reply
  • MadMan007 - Tuesday, July 30, 2013 - link

    I felt like Chrome was much faster loading pages over WiFi on my Nexus 4 immediately after getting the update as well, especially in a spot where my WiFi signal is very weak (outside at home.) Reply
  • darwinosx - Tuesday, July 30, 2013 - link

    Get an iPad 4 then. GPU is four times faster, much better color and contrast, build quality, service and support, LTE capable. Reply
  • djebel - Wednesday, July 31, 2013 - link

    moo cow. MOO! Reply
  • MrPhilo - Monday, August 05, 2013 - link

    Only a dumb ass would say iPad 4 GPU is 4x faster. Reply
  • Ikefu - Monday, July 29, 2013 - link

    I'm very curious to try this on my galaxy nexus. I've done a lot of adding and deleting datasheets and cad drawings to it and its started to slow down considerably in the last 6 months. Have any recommendations for a benchmark to run before and after the upgrade to 4.3 to test for improvement? Reply
  • geemaan - Tuesday, July 30, 2013 - link

    I checked the logcat and there's no sign of fstrim. Reply
  • DuckSoup87 - Tuesday, July 30, 2013 - link

    I can confirm that after three days running 4.3 on my Galaxy Nexus there's no sign of fstrim in the logcat. Probably I just didn't met the conditions required for starting it. Reply
  • geemaan - Tuesday, July 30, 2013 - link

    I charge my gnex in the dock every night so fstrim should've been run by now. I extracted /system/bin/vold and it does contain the fstrim and FITRIM references. Reply
  • DuckSoup87 - Tuesday, July 30, 2013 - link

    The fstrim command itself however is not there. I wonder if this new scheduled fstrim functionality calls directly fstrim, or if it re-implements it with system calls. If the former is true then I don't see how it is supposed to work on a gnex that lacks the fstrim executable... Reply
  • geemaan - Wednesday, July 31, 2013 - link

    vold has fstrim functionality built in. Reply
  • geemaan - Thursday, August 01, 2013 - link

    Well, now I know why fstrim is not invoked: because of the daydream (clock) that is running while the phone is charging in the dock. This night I connected the charger directly to the phone and this morning I found the fstrim references in logcat. Reply
  • tipoo - Monday, July 29, 2013 - link

    I wonder if this will be any different from what lagfix already does, apart from being automatic. Lagfix just runs fstrim on pre 4.3, should have the same effect I guess. Its interesting android never had it before, what about other mobile operating systems? Some sure seem to keep their feet longer. Reply
  • arthur449 - Tuesday, July 30, 2013 - link

    Thanks for the pointer. I'm stuck on 4.1.2 and lagfix allows me to use TRIM on my internal storage without creating yet another reason to be upset that I'm stuck on 4.1.2. Reply
  • Zingam - Tuesday, July 30, 2013 - link

    Amazing! How is this possible at all? I wonder who is designing these technologies and why is this not available by default? Why so many computer technologies are release only half finished? It would be like a car that cannot turn left and the designer: "Go on, will patch it up, when you need to steer." Reply
  • dishayu - Tuesday, July 30, 2013 - link

    Because hindsight is always 20/20. Reply
  • piroroadkill - Tuesday, July 30, 2013 - link

    Not really, this was just poor design. It's not like TRIM is somehow a new command, only just discovered, or something. Reply
  • Zingam - Thursday, August 01, 2013 - link

    In this case this is just a scruffy job. It is an obvious deficiency. Reply
  • dishayu - Tuesday, July 30, 2013 - link

    Sweet. That's something to look forward to in the 4.3 update. Should address the issue of devices slowing down after a few months. Reply
  • evilspoons - Tuesday, July 30, 2013 - link

    My 16 GB Nexus 7, picked up on launch day last year, was slowly getting more and more frustrating to use. It hadn't hit the point many people had described in terms of complete unusability, but it certainly was worse than when I had first taken it out of the box... now, two days after updating to 4.3, the thing is as fast as it ever was.

    I'm sort of confused why they hadn't added this to the operating system ages ago, but it's great to see it here now, and it's great to see the huge improvements!
    Reply
  • hyperspacey - Tuesday, July 30, 2013 - link

    TRIM support was ostensibly added to Nexus 7 versions of Android back in 4.1.2, and while it made a difference, performance is still very much sub-optimal. The 4.3 update isn't going to change your current Nexus 7's performance. Reply
  • Death666Angel - Tuesday, July 30, 2013 - link

    All I read about that was that it was added, but never activated/used. So 4.3 is changing that a lot. And all the people commenting seem to have a different feeling about that as well. :) Reply
  • vnangia - Tuesday, July 30, 2013 - link

    The vast majority of comments and Brian's testing above say the exact opposite: that the 4.3 update does indeed convert an unusably slow tablet into an extremely fast one. A D6A also says, it's likely that fstrim as a command was included in the code for 4.1.2, but it wasn't active. I don't think the criteria for activation (80%+, hour-plus deadtime) is aggressive enough and I would rather it attempt an fstrim on upgrade - like Android says, "Upgrading apps ..." - but that it's active rather than just present is a good step in the right direction. Reply
  • thomase - Tuesday, July 30, 2013 - link

    I'm not sure this is entirely accurate.

    If you look at a pre-4.3 nexus device (perhaps 4.1.2 through 4.2.2), you'll notice that the writeable filesystems (i.e. /data and /cache) are mounted with the "discard" option. This means that the storage is trimmed after EVERY file delete operation. This prevents performance degradation over the long term, but the trade-off is that trimming on-the-fly can effect responsiveness.

    4.3 no longer mounts filesystems with "discard" and instead runs TRIM on a schedule when the device is not being used. This has the benefit of preventing performance degradation over the long term, as well as not impacting responsiveness when the device is in use.

    I suppose you could still run into temporary problems with this strategy if you were to fill up the entire filesystem with files followed by deleting them, all within a 24 hour period, before the storage has a chance to be trimmed. However, this is an unlikely scenario.
    Reply
  • max1001 - Tuesday, July 30, 2013 - link

    ......
    Way to generalize. For people who has the 8 gb version and never did a reset, this would make a huge difference. 4.3 also brings better 2D Ui performance.
    Reply
  • Wolfpup - Tuesday, July 30, 2013 - link

    Wow, this is awesome! Does iOS do TRIM? Windows Phone? I never thought much about it in the context of these mobile devices with their terrible flash.

    I still haven't gotten the 4.3 update on my Nexus 7.

    (Oh, and I still prefer 10" tablets, though 7" might make for a great phone...)
    Reply
  • Sunburn74 - Tuesday, July 30, 2013 - link

    Go to apps, and find the google services framework service. stop the service and wipe the data. Go back to about this tablet and try to upgrade (it should read last upgrade sometime in 1969). It may take 2 or 3 tries but eventually you will upgrade Reply
  • steven75 - Thursday, August 01, 2013 - link

    I don't know if they do TRIM specifically, but they definitely don't have the same sort of slow down problems the N7 had. I routine fill up iOS devices to the limit and don't have any kind of slow down at all. Reply
  • Peterwww - Tuesday, July 30, 2013 - link

    finally! that's single most annoying issue with Android in my case, and something Windows Phone actually got right from the start Reply
  • tedr108 - Tuesday, July 30, 2013 - link

    Hey, Google, give us a utility (app) or widget allowing us to run the trimmer whenever we wish. Reply
  • max1001 - Tuesday, July 30, 2013 - link

    just install lagfix. Reply
  • max1001 - Tuesday, July 30, 2013 - link

    From what I understand, the native eMMC controller must support fstrim command. Only devices with support eMMC would get automatic trim. Reply
  • darwinosx - Tuesday, July 30, 2013 - link

    So ANY Android device not running 4.3.3 has this issue... Reply
  • MrCommunistGen - Tuesday, July 30, 2013 - link

    Sounds like a good step in the right direction. Explains a lot of anecdotal observations about devices slowing with age.

    Does anyone know where or how to find out which eMMC controllers are found in a device and more importantly which controllers support TRIM? I think it'd be unfortunate if lots of recent devices don't support TRIM. Could be scandalous.
    @ Brian Klug: TRIM-gate?
    Reply
  • Syran - Wednesday, July 31, 2013 - link

    My wife was just complaining about how her Droid Razr was running really slow, and it never occurred to me (while it should have) to wonder about trim on the phones. Makes sense as to why they would slow down over time. Reply
  • Jmaxku - Wednesday, July 31, 2013 - link

    My Galaxy S4 GPe is now continually experiencing lag after being used for about a day. Rebooting my phone fixes the issue, but it's incredibly annoying. My home screen suffers from the most lag—kind of has a ghosting effect when I scroll. Other elements—e.g. keyboard—seem to work better, but not as well as they should. I don't know if this is unique to my phone or some sort of software screw up. Anyone else experiencing this issue? I can’t help but think it’s related to the slow storage I/O performance described in this article. My Galaxy Nexus and Nexus 10 never had this problem. Reply
  • JoeKing - Wednesday, July 31, 2013 - link

    I updated my Gnex last night and I have to say I'm absolutely loving 4.3. I had been experiencing horrible lag and slowdown with my gnex and after the update its almost running like new again. Not only that, but I'm noting an improvement on battery life as well. Reply
  • steven75 - Thursday, August 01, 2013 - link

    Great that Google fixed this.

    I can't imagine having the N7 for an entire year before this major problem was resolved though. I guess it's another case of getting what you pay for.
    Reply
  • Charlie Bing - Thursday, August 01, 2013 - link

    FINALLY! Reply
  • DeniZz - Friday, August 02, 2013 - link

    "Android 4.3 Fixes First-Gen Nexus 7 Slowdown Issue", "Google Android 4.3 to the Rescue for Old & Laggy Nexus 7", "Android 4.3 may breathe new life in your bogged down Nexus 7", blah-blah-blah... First of all, why just Nexus 7? Buggy eMMC V3U00M is in many devices - HTC One X, SGS3, my Galaxy Nexus and maybe in others. Another question, why we should be very happy with our buggy devices after 4.3 update? TRIM doesn't help get rid of lags and slowdowns, when there's less than 3 GB free memory. With less than 1GB of free space available my GNex slow as hell, and TRIMing and DISCARDing doesn't help at all. And what a strange schedule for automatic "idle maintenance"? When should I charge my phone and let it idle for maintenance start? I've charged it every night for a week, and it never started "idle maintenance", because I haven't seen any trims in logcat and any speed improvements in androbench. And is there any way to force that fstrim process manually without root and lagfix app in 4.3?
    I don't think that "quietly added TRIM support" in 4.3 is cure-all for devices with eMMC V3U00M.
    Reply
  • BC2009 - Thursday, August 15, 2013 - link

    I'm confused.... is Android implementing TRIM for solid state storage that does not otherwise support it or is Android just now supporting TRIM when it is implemented on the solid state storage?

    I didn't think that TRIM was something that had to run in the background. Is the background process just cleaning up all the stuff that accumulated before Android 4.3 was installed on the device?

    Did I simply misunderstand how TRIM was implemented normally?
    Reply
  • Badelhas - Wednesday, November 20, 2013 - link

    Should we do a full wipe when upgrading or we gain performance over time when we do a OTA upgrade? Reply
  • Chromejob - Sunday, March 23, 2014 - link

    Having upgraded my 2012 N7 16gb to 4.3 I found immediate improvement (well who wouldn't if you did a fresh wipe), but after a while, it slowed down again.

    A colleague recommended I run logcat against "fstrim" or even just "trim." If ordinarily finds nothing:

    platform-tools]$ adb logcat -d -b main -b system -b events |grep trim

    After running lagfix (yeah, I know I shouldn't have to, but I found it DOES immediate good to my N7's response, irregardless of available RAM), I find the following:

    [dspaldin@dspaldin platform-tools]$ adb logcat -d -b main -b system -b events |grep trim
    I/EsApplication( 5056): Trimming memory (onTrimMemory 20)
    I/EsApplication( 5056): Trimming memory (onTrimMemory 5)
    I/EsApplication( 5056): Trimming memory (onTrimMemory 20)
    I/EsApplication( 5056): Trimming memory (onTrimMemory 80)

    I'm not sure that fstrim is working properly even in the current version, 4.4.2. Pity, the Nexus 7 '12 shouldn't have become obsolete so soon.
    Reply

Log in

Don't have an account? Sign up now