Related
With the understanding that RC2 will be superseded by RLS1 very very shortly, I thought I would share my godmode "upgrade" experience from yesterday anyway:
For me, the elapsed time between booting into Amon Ra and finally getting a booted OS (let's define that as the earliest you can pull up the lock ring and get to a homsecreen, even if it is very laggy still) :
20 minutes grand total.
The total time before I could launch an app or actually use the phone in a meaningful way was more like 30 minutes.
Total time before the pain of initial lagginess no longer called attention to itself (ie, you could use the phone without the thought of "damn this is slow" intruding in your mind) : hours.
The long delays during the install process happen at times that are different from what I expected
Flashing the actual zip while in Amon Ra:
8 minutes total. Progress bar seems to hang on around the 50% mark (right under the "u" in Virus") for at least half the time, then the bar fills in to 100% suddenly, then a long wait at 100%, then back to the interactive Amon Ra interface.
At this point Rosie 3.0 carousel "non-landscape" people such as myself flash the appropriate mod ( I did the one with Rosie 3.0 widgets). Very brief ( a few seconds to navigate to your zip, a few seconds to flash).
What happens after you select "Reboot now" in Amon Ra?
First, the "white screen with black 'htc EVO 4G' text" (Note this is different from the "white screen with green 'htc' logo" you get later (and indeed any time Sense reloads, whether due to crashes, first boot, reloading after titanium activity etc)).
This lasted only 3 minutes.
Then the glowing green "SYNEAGY AOM" ( <-- not a typo, look carefully at boot animation ;> ) throbbing-synapse-loop boot animation.
This lasted 9 minutes. Sometimes the synapses throbbed very slowly.
Then finally a brief glimpse of lock ring on top of wallpaper. No shortcut icons visible. If you don't touch phone, the screen promptly goes to sleep. Which is fine. It could probably use a little quiet time at this point.
(If you just touch the power button but don't actually mess with lock ring it's amusing to watch what time it is. First it will be something like UTC time, totally off from your local time unless you're actually in England. Then a while later it will spontaneously change to local time, except in 24-hour format (eg 21:57) . Then finally it will revert to 12-hour format (eg 9:57). Takes several minutes.)
Finally I unlocked it and the first thing I was greeted with was a modal dialog saying "Process com.android.phone is not responding...Force Close / Wait". I chose wait and immediately was shown the "white screen with green 'htc' logo" for a good five minutes of totally non-interactive wait time.
I left the phone alone during this time and eventually it finished doing what it was doing and it fell back asleep. When I woke it up, I was placed directly in the Setup Wizard app. Interestingly, the first screen of the setup wizard has a 'back' button. Not feeling like signing in to anything just yet I hit 'back'. Again came the "white screen with green 'htc' logo", then a desktop with a dialog just saying "Loading" for yet another minute.
At last a real homsecreen appears (now with the familiar constellation of six icons, and, again, no clock/weather widget), the tips widget throws up a balloon with its first tip, and finally you can actually use the phone.
This would be around the 30 minute point since the flashing process started.
There are times during this initial break-in stage where it seems the phone is almost unresponsive. Touches may *begin* to get responded to after a five second lag or more. The response itself can take 5 seconds more to do something simple like simply redrawing a button with its highlight color after a button press, let alone performing the requested action.
That phone / wait dialog comes up a lot. For instance I just saw it again today when someone actually called me. I chose wait and then answered the call normally.)
Ominously, I also saw a dialog later concerning "android.process.media" which concerns me because the point of god mode is to change the way the filesystem works for basic I/O functions.
Still haven't ever signed in to my main google account yet. Seeing how far I can take this before I do. I suspect as soon as I sign in it will start downloading all my apps from the Market. Which force closed on me by the way when I was doing something totally unrelated (just poking around Spare Parts I believe it was).
Also the first time I tried all this the internet browser app simply did not work right out of the box. Force closed every time. (I restored app+data for just the browser app from my titanium backup I made (while running RC2 non god mode) prior to the install and got my browser back. That didn't give me warm and fuzzy feelings.)
Later I repeated the entire install procedure from scratch and did not experience market FC's or internet browser FC's. Not sure why the second time would be different.
Note I was not connected to AC power during any flashing or initial boot up.
For those playing along at home, you may be curious to know things like what kind of phone do I have, how did I prepare to flash, and what was the exact sequence of steps during wiping / flashing?
OG Evo HW 004, original SD card ( I believe that means 8 GB class 2), never toyed with any kind of partitioning. Previous ROMS have all worked fine with the SD card which has the usual folders full of pictures, nandroids, titanium, folders created by previous ROMs including Synergy, etc.
Latest radios, PRI, PRL, GPS works, 4G keys happy, never had any drama.
Before flashing God Mode I was already running Synergy RC2, and once I was ready to say good bye, I did a nandroid backup, then rebooted, connected to a PC and offloaded any new camera pictures, some recent nandroids and uploaded the ROM image ( I did check the md5) and the Rosie mod I intended to use (dkdude, not fdb) . Then ran titanium, backing up all user plus system apps, then finally did one last quadrant test (just under 1000), took a deep breath, and rebooted into Amon Ra 2.3 .
From there I did these wipes in this order:
rotation
battery
dalvik
cache
data
factory reset
Yes I realize many of these are redundant. Then, to be *really* redundant, I left wipe mode and went into flash zip mode and flashed calkulins format all tool. I believe this also wipes boot amongst other things.
So now at this stage the phone is fairly re-virginized. The only thing I haven't touched is the SD card which has the zips I want to flash.
Now I flash the actual synergy RC2 god mode zip (as described at the very top), then the rosie mod, getting no errors for either one, and then without further ado selected reboot now, which brings us back to the firstboot behavior chronicled above.
Edit: I did restore quadrant and got 1600 on my first run: make of that what you will.
[Reserved for updates on 4G experience, bluetooth, gapps, general usability etc...]
Quick update: I did successfully test 4G, WiFi, bluetooth, and GPS.
I finally signed in to Google and sure enough market downloaded all my apps. This may be a Synergy thing- Synergy also seems to remember things from previous installs despite the elaborate wiping regime described above, such as the password to my WiFi access point some search term history, maybe a few other settings.
Anyways, during the download and install of a moderately small number of market apps (I have like 15, all free) the phone was effectively unusable. Almost unresponsive. Finally a half hour after the install activity was no longer apparent, things seemed to settle down and the phone gradually seemed to become normal again.
Quadrant scores were originally as low as 1200 something. Then got it up in the 1400's, then finally i have seen several in a row in the mid-1500's. Again, for reference, I consistently got around 1000 with vanilla RC2 (and the same hardware gave me 1200 with CyanogenMod 7.1 RC1 for you AOSP fans out there).
And this is supposed to be an upgrade???
The party line is *once the phone has had time to settle in* things get a little faster in real world experience. I am in fact beginning to see the promised behavior now, 12 hours after install (including maybe 4 hours of heavy usage)
Certainly the improvements to the benchmark scores are immediate, but we can all agree actual 'driveability' is more important.
So far, I will say it's looking better with each passing hour.
As an example, the simple spinning carousel action (remember I'm doing the Rosie 3.0 carousel mod) under RC2-non-GM was clearly straining the limits of what the Evo could smoothly render. With god mode, it's clearly different, faster and smoother.
Here's the feeling I get: every time you do something for the *first time*, let's say the first time you launch a particular app, activate a certain part of the Rosie UI, get a new dialog box, there's a punishing lag. The *next time* you launch that app, or swipe that tab, or experience that same condition, it's faster. Indeed perhaps faster than it ever was in plain old RC2.
But the make-or-break thing will always be stability, or should I say predictability: days from now, if I still see a lot of Force Close's, or if I am still experiencing unexpected moments of slowness while it "learns" how to do something (and you know how Murphy's law works- it will always happen at just that moment where you can't afford to be surprised by a mysterious delay) - well, it may be back to regular Synergy. Hard to say. I'm a patient person. I intend to give this a good long audition.
When I Flashed the Alpha it took forever, but yes RC2+ was a very pleasant flash by comparison, just flash ROM - flash mount zip - flash carousel + widgets - flash unmount zip. then Im using link2sd and TB. Does anyone know of another a2sd gui that is good? want to prepare for RLS1
I had a similar experience giving rc2+ a try. It was borderline useless on my phone for whatever reasons. Went from rc2 to + after a nandroid backup and did a wipe of dalvik and cache. After about 6 hours of usage I said screw it and restored back to my nandroid backup which is blisteringly fast. The "seat test" on the phone wasn't great at all but the quadrant resulted in test results in the 1700-1800 range which is awesome. I too am on the stock class 2 card and I planned on buying a new card so maybe the results will be better with a new card?
TruthAEE said:
When I Flashed the Alpha it took forever, but yes RC2+ was a very pleasant flash by comparison, just flash ROM - flash mount zip - flash carousel + widgets - flash unmount zip. then Im using link2sd and TB. Does anyone know of another a2sd gui that is good? want to prepare for RLS1
Click to expand...
Click to collapse
The main Synergy thread is full of discussions on a2sd stuff.
Interesting that you flashed the rosie mod using the mount / unmount strategy. I chose to use a rosie mod that had specifically been re-written for godmode. I suppose you end up at the same place either way.
I wonder how it would run on a 32gb class 10.
Sent from my locked tight OG EVO using XDA Premium App
I have seen a lot of wildy varying reports on upgrading your SD card. When it works, it works. It's awesome. But there are also reports of even "class 10" cards that did not improve performance at all. Could come down to who the SD card manufacturer is.
If you tweak everything just right (note most people say to leave dalvik in internal memory regardless) with a swap partitioin, ext3 paritition, a2sd, then maybe one of the new custom kernels that have just come out, and maybe even apply the v6 super charger memory management trick, I bet this ROM could fly, benchmark or no benchmark.
Ran into a weird bug. I can copy ~50-60 MB from a removeable source (dock cardreader or USB port) at a respectable rate of 12 MB/s, after which the whole system bogs down and stops responding to input for 10-20 seconds. It then copies another 10 MB and stops responding again.
It keeps doing that and then usually crashes about halfway through.
Reproduced in multiple performance modes, and multiple file explorers (stock Explorer and Solid Explorer).
Ideas, or just another bug Asus needs to fix?
EDIT: From what I've gathered most people are having issues like this, like the system bogging down when updates are applied etc. Apparently it's due to a poor system I/O control
If you have root, you can try the SD Speed Increase app and set the cache to 2048. The SD cache is usually too small on stock roms.
Sent from my GT-I9100 using XDA
Thanks, gave it a try, but it didn't fix it. It improved system responsiveness but it still bugged out after 130MB.
Also, it's no the /sdcard filesystem I'm having trouble with, but the /removeable filesystems.
Honestly I'm clueless about sdcard speed.
I used to have 17-22mb write speed which I think is ok.
When I had about 2gb space left it went down to 5-10mb. I removed some files and speed went back to normal for quite long time. Now I have 5gb (32gb version) left and speed is 5-6mb. I'm like WTF!
Speed test is very irradic. It writes 15mb/s for a few seconds and then stops for some seconds and then speeds up. Average then gets really slow.
What tool/apps can I use to see if some process locks up write or what could be wrong?
All ideas appreciated. Can sdcard get fragmented like harddrives?
I'm stock rom 4.2.2 rooted.
Also tried ktoonez kernel but same result for sdcard speed.
Skickat från min Nexus 10 via Tapatalk 2
And the solution was lagfix on Google Play. Well known problem on Nexus 7. Apparently present on Nexus 10 too. Strange noone else seem to have this problem on their Nexus 10.
Skickat från min Nexus 10 via Tapatalk 2
All solid state storage bogs down after a time, it is similar to "fragmentation" on hard drives but in a different fashion. solid state storage is made up of cell's that store an electrical charge. SLC chips are either on or off and store 1 bit per cell. MLC flash chips have 4 levels, which gives the capability of storing 2 bits of information per cell. So double the storage in the same space. The problem is how the MLC memory is handled, you can just write a new value to a cell like you can with SLC type. When the memory cell is empty then yes it can be written to directly, but when it contains data the system must first read the data in a cell and store it in memory, then do an erase cycle on the cell, then write the new data to the cell that is a combination of the old data and new data. A lot more steps on MLC type. As memory cells get full you have to do these extra steps a lot more often because there are no empty cells left. This causes a large slowdown in write speed. What lagfix does is called "TRIM", it sends a command to try and consolidate the data in the cells so that all the half filled cells get brought together to a smaller amount of full cells. Then it uses all the newly empty cells (which are not truly empty yet) and does an erase cycle on all of them to remove the voltage charge. This creates more completely empty cells on the storage which allows for the system to do writes much faster since it doesnt have to do 2 extra steps each time until the cells all get dirty again.
In addition to this problem, many solid state controllers have problems when they get too full, jut as hard drives do when you fill them up completely. The chipset cant handle what it is trying to do with shifting around data very well so this creates a large slowdown as well when the storage is almost full. Not all chipsets have this problem, but most do.
Most chipsets have "garbage collection" routines in the background that when the system is idle for long enough will automatically do this TRIM stuff for you to get speed back up. But if you have no idle time then the system cant do this optimization and you run into more slowdowns.
TRIM isn't specific to MLC flash, actually; SLC has to be erased too. Initially all the bits are 1, and data is written by selectively changing individual bits to 0. Changing them back to 1 can only be done by erasing the whole block.
Technically, TRIM doesn't actually command the flash device to erase anything, it just informs the device that certain parts of its data are no longer needed. Typically the device will respond by erasing blocks in that area, but the specifics can vary from device to device.
Hehe this got really technical (which is interesting) but in the end I'm just happy it worked. Most curious why this isn't fixed either in kernel or rom. Because I honestly thought my internal memory was damaged and thought I needed a replacement. Shouldn't this really bad slowdown occur to everyone after a while?
(really love autocorrection sometime. Sdcard managed to be seward)
Skickat från min Nexus 10 via Tapatalk 2
Yes the slowdown does happen to everyone. Theoretically the problem should clear itself up from garbage collection built into the chipset. This lagfix app is really for those who want it fixed right away and not done over idle time in the background.
I don't think it fixes itself on my Nexus 10. Been slow speed and laggy as hell for days. And it should have been idle a lot during this time.
Skickat från min Nexus 10 via Tapatalk 2
I use CM12.1 on both my N7 2012 and N6 and it's incredibly slow on the N7. Clearing the cache does nothing, trim does nothing, F2FS /cache and /data does nothing and even the stock 5.1.1 image is slow.
I've read everything under the sun about poor NAND, not enough RAM, poor CPU, etc but none of them really make that much sense. I have hardly anything running EVER and I only have a few apps installed for opening documents an such. No Facebook or Email clients or anything that would be running in the background. The built in RAM manager tells me that I usually have over 50% of my RAM free and with such a small number of things running, my CPU usage is low, so I fail to see where the issue lies. I guess the NAND, but I also read articles about how that's kind of a load of bull as someone tested old 2012 N7s that had been heavily used and slow, as well as new ones and the R/W speeds were the same.
The main thing that bothers me about it is the fact that when I do a clean install of the 5.1.1 factory image or even CM12.1, it will be snappy for all of 10 minutes and then suddenly it becomes annoyingly slow. It's by no means unusable, but compared to my Nexus 6 every action feel like it takes 2-3 times a long. Even doing my pattern unlock feels sluggish.
I went back to KitKat tonight and it seems to run much better, but there are some things I've gotten so used to with Lollipop and Holo looks plain ugly now that I'd really rather not use KK. Does ANYBODY know of something I can do to speed it up even a little bit. This almost seems like a kernel related issue to me, seeing as how the N7 has been running off of an old kernel for most of it's life. It makes me wonder if there are some kernel-level things that might be done to help.
admiralspeedy said:
I use CM12.1 on both my N7 2012 and N6 and it's incredibly slow on the N7. Clearing the cache does nothing, trim does nothing, F2FS /cache and /data does nothing and even the stock 5.1.1 image is slow.
I've read everything under the sun about poor NAND, not enough RAM, poor CPU, etc but none of them really make that much sense. I have hardly anything running EVER and I only have a few apps installed for opening documents an such. No Facebook or Email clients or anything that would be running in the background. The built in RAM manager tells me that I usually have over 50% of my RAM free and with such a small number of things running, my CPU usage is low, so I fail to see where the issue lies. I guess the NAND, but I also read articles about how that's kind of a load of bull as someone tested old 2012 N7s that had been heavily used and slow, as well as new ones and the R/W speeds were the same.
The main thing that bothers me about it is the fact that when I do a clean install of the 5.1.1 factory image or even CM12.1, it will be snappy for all of 10 minutes and then suddenly it becomes annoyingly slow. It's by no means unusable, but compared to my Nexus 6 every action feel like it takes 2-3 times a long. Even doing my pattern unlock feels sluggish.
I went back to KitKat tonight and it seems to run much better, but there are some things I've gotten so used to with Lollipop and Holo looks plain ugly now that I'd really rather not use KK. Does ANYBODY know of something I can do to speed it up even a little bit. This almost seems like a kernel related issue to me, seeing as how the N7 has been running off of an old kernel for most of it's life. It makes me wonder if there are some kernel-level things that might be done to help.
Click to expand...
Click to collapse
Turn off journaling, use trimmer and try Minimal OS
XenonHD and BSZAospLP run fairly well on my N7. I've got the 32GB model, which purportedly has less memory slowdown issues than the original 16GB model, fwiw.
If your flash memory has bad blocks in it, that will slow down your device whenever it tries to read/write data. A full format of the /system /data and /cache partitions may help. I can't remember if there is a way to mark off bad sectors from being used. You'll have to research that. You may have to do a special kind of format to remove bad blocks from use.
Sent from my Nexus 7
GtrCraft said:
Turn off journaling, use trimmer and try Minimal OS
Click to expand...
Click to collapse
Well, disabling journaling did nothing and trimmer does nothing.
Dirty Unicorns with /data and /cache formatted to f2fs works perfectly with my n7 2012. I'd highly recommend it.
I assume you went from a full flash of the latest stock images, flashed latest twrp recovery, formatted f2fs for cache and data, flashed latest stable CM snapshot, and optionally installed the relevant open gapps as linked to on CM's wiki site?
Have you tried running this setup with no additional apps installed? Chrome isn't much better under this CM 12.1 installation than stock 5.1.1 for me, but everything else seems to run about as good as stock 4.4.4. One thing I do is reboot my 2012 N7 every time I put it on the charger
Chroma works fine on my N7.
admiralspeedy said:
Well, disabling journaling did nothing and trimmer does nothing.
Click to expand...
Click to collapse
Then you clearly did something wrong. Try with a custom rom like Minimal OS, Chroma or Ressurection. And with M kernel
What could I have done wrong? I flashed the file to disable journaling and I've always used trimmer... Disabling journaling literally did nothing.
im right there with you OP, my nexus 7 is ****. Doenst matter what rom, or what format (ext4 or f2fs). I slows to a crawl in a few mins of use, more often than not, takes forever to wake, and then will sometimes just go black before i can unlock, freezes constantly and requires reboots. I hate this piece of ****.
I've added
ro.config.low_ram=true
to the build.prop and I am running the Trimmer app once a day. There is still some lag from time to time, but at least it's useable.
Hi,
I haven't been in here a while. Mostly because I rarely use my 32Gb (2012) N7 anymore; it is simply too painful of an experience. Typically I will pick it up for web browsing, but after the browser or keyboard hangs for tens of seconds for the fifth time in ten minutes, I feel like chucking it against a wall.
Don't tell me I need to free up some space; it has 25 GB of free space in /data
Don't tell me I need f2fs; I'm running CM 12.1 (20151117) / 5.5.1 with /data and /cache formatted as f2fs
Code:
[email protected]:/ $ mount | grep f2
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,inline_dentry,active_logs=6 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,inline_dentry,active_logs=6 0 0
I've filled (to within a few 100 MB) the device and deleted all those files; no real improvement.
So anyway - since I haven't been keeping up, I'm wondering if anyone had been able to shine some more light on what seems to be progressive degradation of eMMC write performance with use (independent of choice of OS, kernel, fs types etc). I suppose this is some sort of wear-leveling/write amplification thing but I can't say for sure.
I really liked this tablet for the first 18 months I owned it; I'm not trolling anyone here. Note that I don't believe this is a situation with faulty hardware (it never crashes or spontaneously reboots - eventually it always comes out of it's hangs (but maybe not for 30-40 seconds). My device has just gotten progressively worse with time, to the point of unbearability.
Have there been any new developments or findings in the last several months?
I use Parrot Mod with Stock 5.1.1 on my N7 3G and I have acceptable performance on it. Ok, Chrome is not the fastest but much faster than before applying the Mod.
http://forum.xda-developers.com/showthread.php?t=3300416
bftb0 said:
Hi,
I haven't been in here a while. Mostly because I rarely use my 32Gb (2012) N7 anymore; it is simply too painful of an experience. Typically I will pick it up for web browsing, but after the browser or keyboard hangs for tens of seconds for the fifth time in ten minutes, I feel like chucking it against a wall.
Don't tell me I need to free up some space; it has 25 GB of free space in /data
Don't tell me I need f2fs; I'm running CM 12.1 (20151117) / 5.5.1 with /data and /cache formatted as f2fs
Code:
[email protected]:/ $ mount | grep f2
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,inline_dentry,active_logs=6 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,inline_dentry,active_logs=6 0 0
I've filled (to within a few 100 MB) the device and deleted all those files; no real improvement.
So anyway - since I haven't been keeping up, I'm wondering if anyone had been able to shine some more light on what seems to be progressive degradation of eMMC write performance with use (independent of choice of OS, kernel, fs types etc). I suppose this is some sort of wear-leveling/write amplification thing but I can't say for sure.
I really liked this tablet for the first 18 months I owned it; I'm not trolling anyone here. Note that I don't believe this is a situation with faulty hardware (it never crashes or spontaneously reboots - eventually it always comes out of it's hangs (but maybe not for 30-40 seconds). My device has just gotten progressively worse with time, to the point of unbearability.
Have there been any new developments or findings in the last several months?
Click to expand...
Click to collapse
Just install parrotmod and you'll notice the difference
I'm using N7 as a main device with Pure Nexus ROM + parrotmod and installed Facebook, messenger, facebook groups, asphalt 8 and about 60 other apps still works fine without lag!
Thanks for the quick feedback everyone.
I'll read through that entire thread and look at the github too.
Already I see I've got Kingston eMMC (manfid 0x000070) , ugh.
Does Trimmer accomplish the same thing as trim on boot, or is it possible to re-enable trim-on-boot on a Kingston device if not? (I just leave the tablet on, so boot time isn't a huge deal to me.)
PS for anyone interested I stumbled across an older version of JESD84 (.pdf)
Please, don't think too much about chips, trimming, file systems etc. Simply apply the Mod and be happy.
Your N7 then will be faster than before.
mausbock said:
Please, don't think too much about chips, trimming, file systems etc. Simply apply the Mod and be happy.
Your N7 then will be faster than before.
Click to expand...
Click to collapse
Performance optimization is always, always about details. In particular, tuning that benefits one type of workload usually makes another one worse.
If I'm sitting behind a full queue of I/O and the CPU is idling at 8% usage, tweaking the GPU or adding BT functionality isn't going to do me a whit of good.
But I'll give lines 58-74 of 01ParrotMod.sh a roll and see how it goes.
PS for anyone else reading this thread: the Trimmer app doesn't do anything on f2fs. (That app is basically a wrapper around a BusyBox version of fstrim; it dies without doing anything but the app doesn't record that in it's log.)
It's Your life. You can spend Your whole time in analyzing this old tablet and its firmware. You can also try dozens of custom roms or custom kernels, format partitions with f2fs etc. Mostly You will still have a laggy N7.
In past I also tried many things like wiping cache, limiting background processes and other tweaks in developer options.
Parrotgeek did a lot of research and many people like are happy with the result.
By the way, f2fs is auto trimming. There is no need to call fstrim manually or by script.
mausbock said:
It's Your life. You can spend Your whole time in analyzing this old tablet and its firmware.
Click to expand...
Click to collapse
You are probably right I suppose. I guess the downside of buying inexpensive commodity hardware is that it is designed for a 2-3 year life cycle, maybe less.
Makes me wonder how much usable life span I gave up by letting the tablet sit at idle condition instead of turning it off - all those slow but non-zero write cycles inexorably chewing away at MLC/TLC write endurance lifetime, and that in turn causing progressively higher write amplification & lower usability/performance.
I can understand that - compared to other types of appliances / equipment that people buy - that expectations of usable lifetime for computers has always been rather short. Mostly because a replacement would be dramatically better/faster/more capable than the older gear. (In contrast, nobody expects to replace their toaster oven every two years - they won't be getting dramatically better toast every few years)
On the other hand, this is a subtly worse situation: not only are the replacement products better, but the older product is actually getting worse with time. Imagine buying a car model with a top speed of 100 mph; but during each year of ownership it's top speed drops by 20mph. It is impossible to remain satisfied even at a fixed level of performance if that functionality is continuously eroding.
Kind of a new-age planned obsolescence I guess. Just keep buying!
@bftb0 I am still using the N7 as my daily driver. I am running trim every two days (it helps especially when there is a lot of write access on your tablet, e.g. installing new apps, etc.) and I have set the background task limit to 4. With these settings on MM I can live quite well. Even if there are from time to time some lags, but most of the time I do not even notice them ...
AndDiSa said:
@bftb0 I am still using the N7 as my daily driver. I am running trim every two days (it helps especially when there is a lot of write access on your tablet, e.g. installing new apps, etc.) and I have set the background task limit to 4. With these settings on MM I can live quite well. Even if there are from time to time some lags, but most of the time I do not even notice them ...
Click to expand...
Click to collapse
I'm using f2fs for /data and /cache, so explicit "fstrim" is not needed. Which flash memory chip do you have? I think that probably accounts for some of the differences in reports. (The "eMMC" flash memory usage model hides some details of wear leveling and even the basic memory cell type and ECC design within the chip itself - so chips from two vendors can perform similarly at the beginning of their lifespan, but quite differently towards the end as they start to engage in more page replacement activity - the methods they use to implement wear leveling are not mandated to be identical by the eMMC specification)
I have the 32 Gb model with the eMMC flash memory chip apparently mfg'ed by Kingston. (manfid 0x70)
I do have a 16GB version with MAG2GA (Samsung), rev. 0x05 (which should have even the TRIM bug ... 8-0)