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.
Related
I keep reading some mixed results. So questions are.
Did the lag fix work for you...
1. Yes my phone flies
2.didn't see a difference so uninstalled
3. Worked for a but got slow again so uninstalled.
4. Never had lag to begin with so haven't tried.
I finally installed one again and must say I see a difference in a few areas. One is the speedtest app, it used to take the test button like 6 seconds to pop up, now isntantly. Apps don't really open faster or anything, or browser either, but things just don't take forever to load, but will the fix do harm eventually is what I'm worried about..
1day after lag fix installed edit: OK so, the #3 started to show up, the market and speedtest app went back to normal load times ( still not bad maybe 6 seconds for market and same for speedtest) so I unistalled. Remember there's never been lag for me and since the 2 out of 3 apps I noticed it increase speeds in started going back to normal, I am fine with my gig back......
100 apps with 1.3 gb left... woohoo
I was going back and forth with different iterations of RayanZA's lag fix, and really do not see a noticeable difference once I reverted back to the original (tried one with ext4 support and it bombed on me, glad I had the nandroid backup done before I applied the lag fix).
Which version do you have?
EXT2 can be easily corrupted if it is uncleanly unmounted - during the phone crash, battery pull, etc. - I haven't seen the reports here that it is corrupted beyond the repair, but there were reports when people were running fsck on the ext2 partitions and there were errors.
EXT3/4 is a better choice, but again people are afraid that in the long run it will wear your internal sdcard beyond repair, since it is I/O heavy - well, I am not keeping this phone for more than 3 years, so I'd care less.
I do think Samsung went the lazy way with FAT32 variant, but I guess it was for the ease of use - you connect your phone to a windows PC, and there you have it as a flash drive.
lqaddict said:
I was going back and forth with different iterations of RayanZA's lag fix, and really do not see a noticeable difference once I reverted back to the original (tried one with ext4 support and it bombed on me, glad I had the nandroid backup done before I applied the lag fix).
Which version do you have?
EXT2 can be easily corrupted if it is uncleanly unmounted - during the phone crash, battery pull, etc. - I haven't seen the reports here that it is corrupted beyond the repair, but there were reports when people were running fsck on the ext2 partitions and there were errors.
EXT3/4 is a better choice, but again people are afraid that in the long run it will wear your internal sdcard beyond repair, since it is I/O heavy - well, I am not keeping this phone for more than 3 years, so I'd care less.
I do think Samsung went the lazy way with FAT32 variant, but I guess it was for the ease of use - you connect your phone to a windows PC, and there you have it as a flash drive.
Click to expand...
Click to collapse
What's fsck ?
1 or 3?
It is insanely fast, but I just applied it 10 minutes ago...
smashpunks said:
What's fsck ?
Click to expand...
Click to collapse
File system check utility in Linux. Wikipedia Entry
smashpunks said:
What's fsck ?
Click to expand...
Click to collapse
Linux utility stands for Flie System ChecK
Personally, I did the app-cache-to-NAND fix. I had done the OCLF but it took waaaaaaaaaaaaaay too long to boot up, and it broke google maps (froze every time and I had to battery pull). I noticed that with the OCLF, Quadrant scores were more than doubled, but the phone itself didn't feel much different. I guess I never noticed any lag or sluggishness, except during boot when the damned media scanner was wasting my time.
lqaddict said:
I do think Samsung went the lazy way with FAT32 variant, but I guess it was for the ease of use - you connect your phone to a windows PC, and there you have it as a flash drive.
Click to expand...
Click to collapse
You can do that with any Android phone, they all use FAT32 for the SD cards.
Samsung went with RFS due to the safety margin it supplies - journaling file systems are more resistant to corruption from being unmounted unexpectedly - and the fact that it's proprietary/closed source, and big companies LOVE closed source stuff.
I never noticed "Lag" to begin with, but with all the issues everyone else was having figured better safe then sorry yah know? I have done the OCLF and while I can't say I've seen any benefit, I can say i haven't noticed any Detrimental effects to the phone. So yah I have it installed no issues, beneficial or negative to speak of that I know of. lol
boystuff said:
I never noticed "Lag" to begin with, but with all the issues everyone else was having figured better safe then sorry yah know? I have done the OCLF and while I can't say I've seen any benefit, I can say i haven't noticed any Detrimental effects to the phone. So yah I have it installed no issues, beneficial or negative to speak of that I know of. lol
Click to expand...
Click to collapse
I think the term lag is wrong.
I never noticed lag, however reading on slow loading of downloads in the market or their messaging app taking forever to load, I had to try again.
I do notice in the market things load faster and also like I said in op the speedtest apps test button pops up instantly now. Also just noticed in twitter it also loads and refreshes instantly now. So it does speed up loading times, but as far as lag??? There was never lag to begin with. Its loading times of some apps, and this drastically speeds it up.
I got like 100 apps installed and 390 mb left for more apps after it took 1gb for the fix (ext2), so unless it starts acting funny I'm gonna keep this installed.
Never got lag, but it does help some apps load faster....
Yea, really did help! No issues with market, apps taking ages to load, and messaging is faster.
Sent from my SGH-T959 using XDA App
Made it faster
It definitely made my phone faster, although I never really had lag, just wanted it even faster, but ended up going back to stock as it was causing issues with a few games. If they could find a way to not make it a memory hog I would put it back on.
It did it yesterday using the market one. The phone was fast already and never really saw any lag. What I have noticed is the market is way faster too load and my games load faster as well, overall well worth it.
I am using CMYLXGO's NAND stock Desire HD build. Its great. However, I am having so many lag issues. I seem to be one of the few that is experiencing this with the build so i turn to some of you to see if you have had similar issues with your phones.
Problems:
1. when auto populating apps (like using installer, uninstaller, managing applications in the system tab) the phone will take forever to pull up all the apps , the screen will cut off (because the screen times out) and when I hit the home button or any button to cut the phone back on it stays black.
2. every action makes the cpu run high. adding a widget to the home screen (apps populating issue again), changing screens really fast and other assorted minor processed.
I have stopped auto sync
I do not use auto rotate any more
I do not have any rogue processes for the most part
I don't understand why I seem to have these lag issues. Everyone else talks about how fast and fluid the build is. I am under the impression that with the build NOT being run from the memory card NAND would add to speed. This is not happening for me. If anyone has any idea why this is happening. I am convinced it is something on my end but I don't know where to start. I am open to suggestions.
I have 2.15 radio, 16 gig class 2 memory card.
Hmmm, not sure but have you tried another ROM similar to see if it does the same? You can also go into MAGLDR and wipe dalvik cache. I used this ROM and all was good for me. I have sense been using this one which is also working very well.
http://forum.xda-developers.com/showthread.php?t=976384&page=1
every version of this build has been tried. That is the part that gets me. differnt kernels don't help either. i have even used SetCPU and overcloced to try and get through some of the lag. it works, but it is only when I play games not when I need to perform uninstall or widget selection for the home pages. I use SeePU which is ususally shows my cpu strain in the bright orange (for high use). most of my processes/actions raise the cpu use to high levels. I never really operate in a green (or low) usage level no matter what the action is. I would really like to capitalize on the speed NAND is supposed to offer.
Personally I would try something else (a totally different ROM) and see if you are still getting the same results, maybe even revert back to a windows mobile rom just to see if you are still getting the hang up. Last option would be to restore your phone to stock and start over, reinstall HSPL 2.08 new radio, etc...etc...
do you use an app killer?
XthelordinatorX said:
do you use an app killer?
Click to expand...
Click to collapse
yeah. but i did not at first. however, it is needed to stop some of the rogue processes. android.process.acore comes to mind.
I personally think this is one of the most stable builds around. I would rarely experience any lag, and if I did it would only last for seconds.
WorldWide60 said:
I personally think this is one of the most stable builds around. I would rarely experience any lag, and if I did it would only last for seconds.
Click to expand...
Click to collapse
Believe me, I know. Everything is working in his build. GPS, MMS, easy to install - the works. This is why i really want this to work properly so I can use it, without the hiccups, as my daily build. It has to be something with my phone but I can't figure out what it is yet....
On Cmylxgo's build, the first time I loaded it, I had the laggy and unresponsiveness you described for the same reasons. What I found is that rebooting the system to off/on a couple of times when I first loaded the build, addressed the first initial lag and unresponsiveness. After doing a couple of reboots, I found the build as smooth as everyone says it is. I am now trying the GL Core v11 kernel and it gives an extra 300 pts to the Quadrant Score and seems to be a bit quicker than the Rafpigna 1.8 kernel that comes with the build. Also, standby battery drain seems to be a bit better with the hourly peaks at half what I see with Rafpigna. If rebooting a couple of times doesn't do it for you, I know trying another build which may not have all the bells and whistles as Cmylxgo, but it is worth a try to see if it makes a difference. For me at least Cmylxgo's stock Desire (HD)2 build is much faster and smoother than any of the MDJ SD builds I was using.
Hello.
I've read various other topics about how not having too much ram is good, expected, and so on.
However, when I first got my n7, it would use perhaps about 50% of the RAM, without any apps. I could run a bunch of apps, and they'd be responsive, I could move between apps quickly and easily, and everything was smooth. I've tried multiple roms, and kernels, and everything was good.
Until lately. Suddenly, when I boot, apparently i'm using up 75-90% of the ram. I've manually added up the amount of ram being used, and found that the apps that were running in the background were only using about 128mb. Starting applications takes a while, scrolling is laggy, and switching apps can take up to 15 seconds at times.
I figured it was a kernel, so I switched back to a reliable kernel. Nope, everything was the same. Was it the rom? I've tried AOKP, Dirty AOKP, paranoid android, and a few others. Bootloader perhaps? I've switched between clockwork and TWRP. Cleared the caches. Tried changing the I/O governers, various schedulers. Still laggy, and still using up a lot of RAM.
Should I back up my data, and do a factory restore? Or am I just missing something that's staring me, ready to slap me in the face with it's obviousness?
Thanks in advance.
Depends on which apps are you running in background , like for ex Chameleon Launcher uses around 100mb of ram . Better go back to stock and see if the problem persists
Sent from my Nexus 7 using xda premium
Hi, so I've had my G2 D800 model for a while (about a year or two), and for the most part, it's been an excellent phone despite being 3 years old now. Never had any slowdown problems, and it's always performed well in games and in general.
But just recently, about a week ago, it just started lagging out and being very, very slow.
For example, if I'm watching a YT video through the app, if I rotate the screen, it takes maybe 5-8 seconds to actually rotate. Also, in a lot of circumstances where the keyboard has to pop up, it just freezes the app until the keyboard pops up maybe 10 seconds later.
It's also just laggier in general in most apps, scrolling through FB or Twitter freezes nearly every second when I'm scrolling. It's generally unresponsive and sometimes just freezes outright. It also acts this way on the homescreen, and in most everything else.
The most annoying part, however, is that sometimes the devices just doesn't turn on for sometimes up to 15 seconds after pushing the power button (and it usually just refuses to turn on when using my knock code).
The odd part, however, is that once it's actually in something like a game, it performs perfectly fine.
I've played a number of Cardboard games, as well as games like Nova 3, and it performs perfectly.
I've also ran multiple benchmarks (Geekbench, 3DMark, etc), and it scores around where it should.
Info about the device:
LG G2 D800
Stock Lollipop 5.0.2
Software Ver. D80030f
Kernel Ver. 3.4.0
Rooted
TWRP Recovery installed
XPosed Lollipop installed
G3 Tweaks installed, a number of tweaks applied
Everything else is stock (homescreen, etc)
What I've tried/checked:
Checked memory usage during "lag sessions", rarely dips below 300mb free
Changing minfree values through Rom Toolbox (tried every preset, as well as setting everything to the max to free as much as possible)
Rebooting (affects nothing)
Checked CPU speed with Rom Toolbox (is at max, and does achieve the max speed of 2265 MHz. Setting it to performance mode/setting the min speed to be 2265 MHz has no effect, but reduces battery time)
Changed default cache sizr (tried every preset from 128kb to 4096kb. With multiple benchmarks, the optimal value for r/w bounced between 512kb and 4096kb, currently on 4096)
Things I have not tried (that I am aware would possibly have an affect):
Changing anything in the kernel tweaks/build.prop
Completely wiping, reformatting, and reinstalling (I really would rather avoid this if possible, as it would take a while to get everything back to what it is now, and it was a pain to upgrade to Lollipop in the first place)
I am unaware of anything else I could try to fix it, which is why I'm here
So, does anyone know of any other solutions or things to try? This has made my phone very unreliable, even for phone calls and messages, which is a problem.
Thank you for your time and help!
Jtpetch said:
Hi, so I've had my G2 D800 model for a while (about a year or two), and for the most part, it's been an excellent phone despite being 3 years old now. Never had any slowdown problems, and it's always performed well in games and in general.
Click to expand...
Click to collapse
Hi,
First thing i need you to try out is this custom kernel : http://forum.xda-developers.com/lg-g2/development/lp-5-0-2-kernel-3-4-107-dorimanx-1-0-lg-t3102512
Then install greenify, and hibernate all the unnecessary apps.
This should solve the issue.
iubjaved said:
Hi,
First thing i need you to try out is this custom kernel : http://forum.xda-developers.com/lg-g2/development/lp-5-0-2-kernel-3-4-107-dorimanx-1-0-lg-t3102512
Then install greenify, and hibernate all the unnecessary apps.
This should solve the issue.
Click to expand...
Click to collapse
Thanks for the quick reply!
I'll try out greenify, though there aren't many unnecessary apps running (i uninstalled all the bloatware first thing, when I rooted).
And about the custom kernel, it's something I've never tried, so I have a couple questions.
Will it wipe my device, or break TWRP, root, or Xposed? (Sorry, didn't see the answer on that forum)
Will a TWRP backup I make be able to fully restore my device to it's current condition?
Is everything that is supported on my device be supported with that kernel? (Apps, etc. Don't know a whole lot about how kernels work, so I don't know)
Thank you!
Jtpetch said:
Thanks for the quick reply!
I'll try out greenify, though there aren't many unnecessary apps running (i uninstalled all the bloatware first thing, when I rooted).
And about the custom kernel, it's something I've never tried, so I have a couple questions.
Will it wipe my device, or break TWRP, root, or Xposed? (Sorry, didn't see the answer on that forum)
Will a TWRP backup I make be able to fully restore my device to it's current condition?
Is everything that is supported on my device be supported with that kernel? (Apps, etc. Don't know a whole lot about how kernels work, so I don't know)
Thank you!
Click to expand...
Click to collapse
Hi,
Even you uninstalled bloatware, the apps you use daily could be running in background and taking all those rams. So whenever you play a game or dont use a certain app, just go to greenify and hibernate. Since you have xposed installed, you can do more than that such as u can stop sync , etc.
About the kernel, it has a ram management settings and cron task.
Ram management dont need to be altered. It has some preset profile so if you seek performance, just choose performance or if u need battery , select battery profile etc.
Cron task is useful because it will do alot of things automatically. For example, it will release ram at certain amount of time from the apps , it will restart google play service since that could be an issue , etc.
All you need to do is take a nandroid backup just to be safe. Then download Dorimanx Ota from playstore and it will detect ur device and show u which version of kernel is available. Then download that, go to recovery, flash it, and you will see three app installed : Synapse -- will give you all the details of ur setup including cpu speed, temp etc for monitoring purposes
Dorimanx settings - this is the main settings of the kernel. You will see a P icon on top, tap it and choose your desired profile.
Color management : It is as the title says, just leave it be.
Then use your device, check your ram and report back. Hopefully it will resolve your issue.
Wow. Dorimanx did a lot more than I was expecting.
Downloaded the app, downloaded the kernel, flashed it no problem, went through and checked out synapse.
Went into the Dorimanx settings, and set it to the "Performance" profile.
Immediate improvement.
The whole phone seems a lot more snappy, and I switched back and forth between a 1080p60 YT video, facebook, and twitter with absolutely no problem.
Free memory when idle (no apps open) stays around 1gb; it used to be about 500mb before.
Tested a few games for the heck of it, and it actually seems to have improved game performance somehow. (It seems to have overclocked my CPU to 2.5ghz, though, so that makes sense.)
Temps stayed at around 58-60c while running a few Cardboard apps, so it seems fine.
Thanks for the help iubjaved! This has fixed my issue and then some! Ah, the wonders of the Android dev community.
Jtpetch said:
Wow. Dorimanx did a lot more than I was expecting.
Downloaded the app, downloaded the kernel, flashed it no problem, went through and checked out synapse.
Went into the Dorimanx settings, and set it to the "Performance" profile.
Immediate improvement.
The whole phone seems a lot more snappy, and I switched back and forth between a 1080p60 YT video, facebook, and twitter with absolutely no problem.
Free memory when idle (no apps open) stays around 1gb; it used to be about 500mb before.
Tested a few games for the heck of it, and it actually seems to have improved game performance somehow. (It seems to have overclocked my CPU to 2.5ghz, though, so that makes sense.)
Temps stayed at around 58-60c while running a few Cardboard apps, so it seems fine.
Thanks for the help iubjaved! This has fixed my issue and then some! Ah, the wonders of the Android dev community.
Click to expand...
Click to collapse
No worries, happy to help. I gave you advice based upon my experience using all those .
Feel free to post in XDA if you need any sort of help, you will find many that will give you insights and stuff to solve your issue.
GL :good:
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)