Galaxy Nexus unusable once again (low i/o) - Samsung Galaxy Nexus

So my phone went from being an unusable, laggy, crashing, ****ty phone in a matter of 30 seconds.
I'll explain more.
I had previously posted a thread about my Nexus' low i/o scores, and since it wasn't rooted, we concluded that the best way (and maybe only way) to fix it was by doing a factory reset. It fixed the problem, but I lost all my stuff, and it was a hassle.
Now it's back. Why? Because I thought the phone could handle having less than 3GB of free space. Boy was I wrong. That 1.6GB video I copied to my phone pushed it over the edge of ****ty i/o performance, never to return without a factory reset. I freed up 6GB+ of space, cleared all caches, even restored from a backup in cwm. The phone still suffers from painfully slow benchmarks (only i/o), and stutters at the simplest tasks.
What can I do? I have to reset again? This is not my vision of a well designed OS with such a flaw.

shao3m said:
So my phone went from being an unusable, laggy, crashing, ****ty phone in a matter of 30 seconds.
I'll explain more.
I had previously posted a thread about my Nexus' low i/o scores, and since it wasn't rooted, we concluded that the best way (and maybe only way) to fix it was by doing a factory reset. It fixed the problem, but I lost all my stuff, and it was a hassle.
Now it's back. Why? Because I thought the phone could handle having less than 3GB of free space. Boy was I wrong. That 1.6GB video I copied to my phone pushed it over the edge of ****ty i/o performance, never to return without a factory reset. I freed up 6GB+ of space, cleared all caches, even restored from a backup in cwm. The phone still suffers from painfully slow benchmarks (only i/o), and stutters at the simplest tasks.
What can I do? I have to reset again? This is not my vision of a well designed OS with such a flaw.
Click to expand...
Click to collapse
It's a problem with the memory chip i guess, my phone runs like a champ, filled the storage to the brim once and it's still pretty fast.

I recommend you go on the Play Store and download a paid app called Seeder.
This app is NOT a placebo effect. It does work.
If you don't want to pay, type in Seeder v1.4 XDA, and you'll be able to get it for free (not pirating, dev posted it up for free on this site. So zip it. Thanks. ^_^)
Why is the developer doing this? I dunno. But the benefit of the play store version is updates. Which is what I recommend.
Let me know how it goes. Made my nexus faster is all I can say.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^

Seeder
Just installed Seeder per the recommendation above
...Woah

I don't think Seeder will fix this - worth a try though (the dev states itself it does not have this effect on Android 4+).
I had the same problem (rooted) and only was able fix this issue by completely resetting my device. Very annoying indeed...
I don't know why it occured and thought it was too much playing with different ROMs. Once I found a ROM I'm really happy with and used for months without "playing" with other ROMs (liquidsmooth) it was all great but one day this i/o issue occured again out of nowhere. Only way to fix it -> reset.
I too would be really interested in knowing why this happens and how to avoid it...

why reccomend seeder for this?it's a unrelated thing,and doesn't fix any OP problems.

It helps stop lag. Which makes the phone feel faster. So yes it is related. And it does work on android 4.1.2 for me very well.
I'm clocked at 2xx-729 and have zero lags.
And yes I did factory reset recently and it didnt really help besides giving me faster boots. Seeder helped me ALOT. It may increase the io but it does make it faster since it reduces lag.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^

I'm just going to leave this here since it will actually help with the io problems instead of some entropy generator.
http://forum.xda-developers.com/showthread.php?t=2104326
Sent from my Galaxy Nexus using Tapatalk 2

geoffcorey said:
I'm just going to leave this here since it will actually help with the io problems instead of some entropy generator.
http://forum.xda-developers.com/showthread.php?t=2104326
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
:good: THIS. I believe this will, more or less, solve your problem without having to do factory reset

geoffcorey said:
I'm just going to leave this here since it will actually help with the io problems instead of some entropy generator.
http://forum.xda-developers.com/showthread.php?t=2104326
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
YES! This definately helped with my lags! :good:
After 1 month of using my phone, it started to lag again. So I tried Seeder first, which - as expected - didn't solve the problem (I will leave it activated though and observe it).
But using LagFix is now like having a new phone (or at least a fresh install ) and everything is hyperfast again! Thanks for the hint! Really great tool! (Though I would be more happy to not to have to use these kind of tools...)

Related

a simple way to get rid of lag (most of it)

hi everyone, i'm no expert on phone, so don't kill me if i sound stupid
been using my galaxy S for about 4 months now. and yes it does lag compare to the iphone, or other HTC phones. so i been trying to find out, what's going on? why is my top end phone lagging? here's what i found:
1) when does it start to lag badly?
i installed system panel which gives me a nice list of active and inactive apps, and how much free ram i have left. the phone ALWAYS starts to lag like crazy when ram gets below 60mb. this is a problem - samsung is not giving us enough free ram to play with as once we run a few apps (market, internet especially), we're reaching the 60mb point already. when the phone gets to the 60mb mark it tries to manage the apps by closing some less important ones. but it lags BADLY while doing so.
what's gonna happen is the phone gonna get into this never ending cycle of closing apps and laggin as it's stuck in around the 50mb-60mb mark.
i can solve this by going to system panel and closing all inactive apps. then the ram is gonna go back to around 140mb. however after opening a few apps, once again it goes back to below 60mb and the lag starts again.
2) autokiller
guys been saying autokiller is great and they go with the aggressive settings. i tried it and it made the phone worse. why? because instead of killing apps at the 60mb mark it starts killing apps even sooner! that's wasting battery, wasting free ram, and making the phone even slower. we don't have enough free ram to begin with, so we should make max use of it. here's how i do it:
1) root the phone. install autokiller from the market.
2) instead of using high aggressive settings, use the LOWEST settings. i use advanced mode and then enter all values to 8mb only.
now it is awesome!! the phone never lags until you get it down to around the 20mb mark. you now have around 40mb of extra ram to use (of course autokiller does use some ram but no big deal). the lag starts much latter. u may not think 40mb is a lot but it is in practice!
if you dont believe me, you can try it. it may or may not work for u, but it's definitely working for me. of course, once the ram falls below 20mb, it may be a good idea to close some inactive apps yourself, LOL
but really, samsung should give us at least 100mb more free ram, i can't believe i even have to do this!
Well you point one issue that lag happens, but almost every custom kernel/Rom use memory tweak that Make you around 40MB more to start with.
And yes autokiller don't work good.
The program in the phone is the best to use.
The main lag issue is the filesystem.
Even these can be fixed with many different kernel/Rom.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 341MB Ram
i don't disagree with what you're saying. but a few things to add:
1) i have not applied lag fix myself but i have a friend who has. i dont feel his phone is much quicker than mine in reality. also, his phone crashed after a few weeks and he had to do a hard reset. what we REALLY need is more ram. if we have lots of ram, who cares about the file system? we don't even need any swap from the file system. just let everything stays in ram where it is the quickest.
2) i'm not using any custom roms. if custom roms give me extra 40mb, and then i adjust the auto killer setting to low, that gives me 80mb extra to play with. great.
autokiller DOES work good i feel if you're doing what i'm saying. maybe u have already tried what i'm doing, i don't know, but if you have not, then i highly recommend you to try it.
like i said i'm no expert on this, but autokiller is so easy to install and adjust, and that i feel anyone here can use it
maybe flashing custom firmware is easy to do, i haven't tried it, but it sounds complicated to do for me, and i don't want really big changes on my phone, i want it to be extremely stable and safe as i use it a lot for business. i don't really want to risk any data or risk reinstalling stuff.
so maybe i sound uneducated but like i said i suggest everyone to try this method if they're newbies and don't wanna do too much
I can confirm that setting autokiller to low settings makes the phone feel faster than on high settings, I tried that some time ago.
But lag will still be present.
As mentioned by the poster this is a low risk, low skill method of improving the phone and is easy to do for all.
For all others I recommend the JFS lagfix. It is by far the lagfreest experience out there!
i have a buddy with a moto milestone and his phone lags just the same as ours. his phone has even less free ram than ours and so his is constantly lagging. sometimes he can't even take a phone call while listening to music becoz his phone only has like 50mb of free ram after starting up. so, just a point of reference - our galaxy is crippled with just not enough free ram, i heard stories of nexus one having 200+ free ram after startup and that's why they dont lag like us, so at the end of the day we're fighting a losing batter becoz samsung didn't give us a good enough phone
Mycorrhiza said:
I can confirm that setting autokiller to low settings makes the phone feel faster than on high settings, I tried that some time ago.
But lag will still be present.
As mentioned by the poster this is a low risk, low skill method of improving the phone and is easy to do for all.
For all others I recommend the JFS lagfix. It is by far the lagfreest experience out there!
Click to expand...
Click to collapse
thank u and i may try the jfs fix, but i'm just worried about something happening to the phone becoz of what happened to my buddy who lost all his data (i can't remember which lag fix he used though), i always have this thinking that if the lag fix are 100% safe, then why aren't samsung doing it? samsung are paying tons of money to the programmers i'm sure and you would think they know how to do it too? but they choose not to, and there must be a good reason why.
You have a very good point supraman123! I realized it was the memory management that made the phone go crazy around the 60MB mark (you'll see the kswapd0 process go crazy), but never realized Autokiller could help us lower that mark. I hope this works, would be one of the best and easiest fixes for the SGS.
supraman123 said:
thank u and i may try the jfs fix, but i'm just worried about something happening to the phone becoz of what happened to my buddy who lost all his data (i can't remember which lag fix he used though), i always have this thinking that if the lag fix are 100% safe, then why aren't samsung doing it? samsung are paying tons of money to the programmers i'm sure and you would think they know how to do it too? but they choose not to, and there must be a good reason why.
Click to expand...
Click to collapse
If we know the amount of time and money Samsung spend on developing RFS...
So wait, the phone is faster if the minfree is set higher than default, and the phone is faster if the minfree is set lower than default... holy ****!
I applaud Samsung for figuring out the one setting that makes the phone suck and use that as default. Way to go, Sammy, way to go.
I know what u are talking about. I think it was an ext4 fix. All other lag fixes I know of don't share that problem.
Also with root there are many ways to secure your data prior to installing a lag fix.
Sent from my GT-I9000 using XDA App
Mycorrhiza said:
I know what u are talking about. I think it was an ext4 fix. All other lag fixes I know of don't share that problem.
Also with root there are many ways to secure your data prior to installing a lag fix.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
hi, thank u, can u tell me how to secure the data? or u have any good links to show me? thanks
jjwa said:
You have a very good point supraman123! I realized it was the memory management that made the phone go crazy around the 60MB mark (you'll see the kswapd0 process go crazy), but never realized Autokiller could help us lower that mark. I hope this works, would be one of the best and easiest fixes for the SGS.
Click to expand...
Click to collapse
i hope it will work good for u also
xmonkee said:
So wait, the phone is faster if the minfree is set higher than default, and the phone is faster if the minfree is set lower than default... holy ****!
I applaud Samsung for figuring out the one setting that makes the phone suck and use that as default. Way to go, Sammy, way to go.
Click to expand...
Click to collapse
i'm quite disappointed at the ram issue also. coming from a n97 mini which seriously lacks ram, i was hoping by going for a high end phone like the galaxy, i aint gonna have to worry about ram and closing apps manually all day, however in reality the Galaxy aint much better than the n97 at multi tasking. of course, it's far better than the n97 at everything else.
I totally agree with OP on this one!
But Autokiller is not the only app that can fix the lag.
One Click Lag Fix 2.0 can root your SGS (Eclair only), lagfix it (with EXT2) and it can even do some additional tweaks like minfree (same as the Autokiller app) and fix the Scheduler.
With minfree Samsung put these values in "/sys/module/lowmemorykiller/parameters/minfree":
"2048,4096,5120,5632,6144,7172"
But best is:
Aggressive: "1536,2048,4096,21000,23000,25000"
or
Strict: "1536,2048,4096,15360,17920,20480" - I prefer this one
btw when you've a lot of ram free the ram is mostly used to cache file system reads ^.^
this explains that a little
Im using the 341MB of free ram so that gives me an instant 40MB ontop of the stock kernel, never seen the phone had less than 60mb free with this kernel, with my usage it doesnt even go under 95mb free.
I am also running one of those kernels that gives extra RAM. And I have all my partitions Ext4 lagfixed. But my phone still seems quite slow at times. My RAM was above 80MB free at that time though, so probably not related to any minfree/Autokiller thing at all. Which means there are way more causes to get rid of I guess.
I don`t know how you guys have problems with the lag, I use the stock samsung JPO, not even deodexed with zankinz 23 kernel and NO-RFS all ext4 lagfix and the phone is running perfectly, no lag whatsoever, the RAM is somewhere near 220 mb free after reboot. After deodexing and optimizing the apk`s the phone should run even better. I was determined to change my SGS with a Desire HD, but now I`m really thinking of keeping it.

Autokiller memory optimizer.

Hi i found an app called auto killer memory which ive been running for a while. this app has worked wonders for my wilderbeast, its on fire. so ive been tampering alot with things but this seems to have stabalised my phone loads. presets i set to lost, enabled advance mode,apply at boot,ticked all system tweaks and of course when promted enabled super user. my phone is now running sweet and battery has improved too. i dont know if this makes any sense but i have noticed a difference. whoop whoop. am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Ok I've ammended my settings within this app after doing some research And in memory values I'm now running at 6/10/16/100/120/160 to keep my phone running snappppppy. To explain the values in brief...... if free memory goes below 160mb my phone starts to kill empty apps etc etc as free memory goes below next value the phone starts to kill corresponding apps. Kind of makes sense to me now. Ok I know my settings makes the phone kill more frequently but its damn snappy now,and it can lower the oom settings by long pressing the app in processes section you wish to lower and choosing lower oom. Lowering the oom basically gives the app less chance of being killed.
Personally I haven't had a low memory situation since I rooted and installed cm7, the app your talking about I have installed after reading one of your other posts about it, I presume that it would work the same way as juwes after setting the low memory values, I don't use those settings with it though as I have juwes script installed, the other tweaks seem fine but again I think I had some of them covered from editing my build.prop (still have work to do on that though) and a few other little things, I can't knock this app though as it does seem to have made my battery last a bit longer since installing yesterday, I'd personally rather change the settings myself than have yet another app doing it for me but until I figure which setting seems to be helping my battery out I'll keep it installed.
A couple of other apps which might help you keep it smooth,
Autostarts- I swear by this app its one of my best buys from the market, why use a task killer when you can just stop the app starting in the first place??
Fast reboot pro- after time apps hold memory which they don't really need, hit this and it'll quickly reboot everything (unless you tell it to leave something alone) freeing up spare ram.
Sent from my HTC Wildfire using xda premium
Cheers for info,really happy with this app at the moment.by the sounds of things its doing similar job to other script mods,which I can't get working cos of s - off issue. Posted this for s on users benefit. Hope it helps others.
Edit my settings. Read 1st post.
sent from my wilderbeast/buzz
The only problems I see with having higher settings are if it closes something you use regular it'll be slower to open that app, I'd rather keep them set low and have apps open quickly.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
The only problems I see with having higher settings are if it closes something you use regular it'll be slower to open that app, I'd rather keep them set low and have apps open quickly.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
I agree but this app lets you temporary lower the oom level for apps,so I just lower oom on most important. Long click on process or service and to lower.
sent from my wilderbeast/buzz
Does it?..........I didn't spot that nice find!!
Sent from my HTC Wildfire using xda premium
Yep,long click app in service or process then choose to lower oom.it resets if you reboot so get your settings desired then leave by pressing home button.
sent from my wilderbeast:buzz
whats up with these settings for the pages? what do these settings change?
atm i have these settings:
2560
4096
25600
30720
40960
gozzaa said:
whats up with these settings for the pages? what do these settings change?
atm i have these settings:
2560
4096
25600
30720
40960
Click to expand...
Click to collapse
Change the view from pages to mb and these are the values when it will start killing processes etc. Ie. When your memory gets to the amount your phone starts freeing up starting with the highest setting (empty apps)
Its all explained above,just that you have the pages view instead of mbs.
Quote " its healthy to have enemies, it means you've stood up for something you believe in "
ahh the pagesettings are the same as the MB ones?
i thought its two different things
thanks for the explanation!
btw. do you still use the same settings?
Yes to this day I still use this app even though I'm now s-off with the settings I posted,I will just double check and ammend if needed on 1st post.
" once its gone,its GONE."
slymobi said:
am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Click to expand...
Click to collapse
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
zephyri-xr said:
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
Click to expand...
Click to collapse
i tried supercharger and juuwes but had issues which i think were specific to me but one of the issues was bootlooping from supercharger as well as other things. im not saying one is better than the other but as you and myself had issues with one of the mods then its an alternative for others to use. i prefer this as you get to control the settings and mods yourself from the app. also this is available for s-on whilst the others i believe need s-off.
zephyri-xr said:
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
Click to expand...
Click to collapse
I got a boot loop from supercharger. I had to wipe my phone and start again from an RUU as all my previous backups became corrupted. Nightmare. TBH in the few days that it did work, i saw/felt no difference.
Using CM_7.1.0.1 probably wouldnt advise to use the supercharge, CM_7 minfree values are set to a pretty good level to keep things in order i think
slymobi said:
Hi i found an app called auto killer memory which ive been running for a while. this app has worked wonders for my wilderbeast, its on fire. so ive been tampering alot with things but this seems to have stabalised my phone loads. presets i set to lost, enabled advance mode,apply at boot,ticked all system tweaks and of course when promted enabled super user. my phone is now running sweet and battery has improved too. i dont know if this makes any sense but i have noticed a difference. whoop whoop. am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Ok I've ammended my settings within this app after doing some research And in memory values I'm now running at 6/10/16/100/120/160 to keep my phone running snappppppy. To explain the values in brief...... if free memory goes below 160mb my phone starts to kill empty apps etc etc as free memory goes below next value the phone starts to kill corresponding apps. Kind of makes sense to me now. Ok I know my settings makes the phone kill more frequently but its damn snappy now,and it can lower the oom settings by long pressing the app in processes section you wish to lower and choosing lower oom. Lowering the oom basically gives the app less chance of being killed.
Click to expand...
Click to collapse
I have tried supercharge script and does make phone smooth. Also Ive use ram manager new app and that too made phone smooth. But this app (Pro) is so far great. I tried out your settings for now to see if it suits me and had the app for an hour and the phone is very snappy and smooth (which is most important to me). I hope there is a slight battery improvement that many have said on the net but will test more and will leave feed back. A big thx m8!
no probs mate, like i said i have tried the lot and this one for me is really good and you get to be the controller lol.the only drawback i have noticed is that it takes a little longer for the phone to boot after a reboot but !!!!! im ok with that.
LMFAO looks like I didn't pay enough attention... I've used a lot of tweaks already to make my Willy faster, more snappy and stable but to be honest nothing gave it such a boost like that
BTW: are you still using the settings of the op?
Holy crap, I've read that really often here and elsewhere but it's the first it applies to myself: feels like a new phone
eventcom said:
LMFAO looks like I didn't pay enough attention... I've used a lot of tweaks already to make my Willy faster, more snappy and stable but to be honest nothing gave it such a boost like that
BTW: are you still using the settings of the op?
Holy crap, I've read that really often here and elsewhere but it's the first it applies to myself: feels like a new phone
Click to expand...
Click to collapse
I use aggressive setting mostly, all advanced tweaks except sdcard boost one as this bumps read ahead up to 2048, just my preference you might prefer 2048.
Say oooh la la
slymobi said:
I use aggressive setting mostly, all advanced tweaks except sdcard boost one as this bumps read ahead up to 2048, just my preference you might prefer 2048
Click to expand...
Click to collapse
I see. I just have to sort things out now. Regarding the SD card read - I have it already done by sdbooster (@2048) - I'm at a point where I should make a documentation to stay on track and to avoid double tweaks lol.
I'm also very interested into scratch's build.prop lol (guess that would help to drop even more tweaks). Thx again - I've not forgotten about your tip re. AMO - just shifted it too far lol.

[Q] Abduction Help?

I'm currently using the Abbduction v1.81 ROM with my Dinc and its been acting weird lately. Help?
-random restarts.
-boot screen sometimes goes Portal and infinite loops itself.
-random force closes (although better than my previous ROM)
-battery isn't nearly as good as i was told.
Did you wipe all data before flashing?
Firstly, I love the thread title.
Secondly, Abduction is based on AOKP, right? In my own usage, I have seen those same symptoms (particularly the reboots and batter life) when running straight AOKP; even as recently as M4. My phone seems to like Evervolv a LOT better, so I keep coming back to it.
graymonkey44 said:
Did you wipe all data before flashing?
Click to expand...
Click to collapse
yessir. i followed all the steps that were listed in the instructions. this is not my first ROM btw. i forgot to mention that i think..
Try a different recovery or use a superwipe script. Sometimes recoveries don't wipe things correctly leading to unexpected behavior. Also, the space on your phone could be getting clogged by the number of apps you have, which often results in random reboots. To prevent this, you can try moving apps to the SD card or just downloading fewer of them.
I disagree on the wiping having issues. There was a post by a lewd cm member on this a while back. How much space used or left on /data/data? HTC made the brilliant move of limiting /data/data to 150mb which doesn't get reported anywhere in the os. That is a possible cause of the force closes if the free space there is low. As far as reboots did you tweak voltages or overclock?
Sent from my Galaxy Nexus using Tapatalk
http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
tiny4579 said:
I disagree on the wiping having issues. There was a post by a lewd cm member on this a while back. How much space used or left on /data/data? HTC made the brilliant move of limiting /data/data to 150mb which doesn't get reported anywhere in the os. That is a possible cause of the force closes if the free space there is low. As far as reboots did you tweak voltages or overclock?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
i did undervolt is when i started using Abduction, but before then i havent done anything but overclock it by a little bit. using the ROM control that came with AOKP.
tiny4579 said:
I disagree on the wiping having issues. There was a post by a lewd cm member on this a while back. How much space used or left on /data/data? HTC made the brilliant move of limiting /data/data to 150mb which doesn't get reported anywhere in the os. That is a possible cause of the force closes if the free space there is low. As far as reboots did you tweak voltages or overclock?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Ughhh I mean lead.
How much did you over clock, OP?
If its 1113 MHz or less it should be fine. Try without overclock and see if you have the same issues.
Sent from my Galaxy Nexus using Tapatalk

improve gnex performance?

i have a feeling this phone is starting to show its age. it seems whenever i install more than 100 apps on this phone it just becomes laggy as hell. to the point where right now the keyboard doesn't even open until 10 seconds later and phone constantly make weird noises when using tune in radio or youtube. the phone is also so slow that it can't even run temple run 2 or any of the games that came out recently. im using xylon rom with trinity kernel for those wondering. i honestly cannot use this phone anymore without having to do a factory reset every month just to stop the lag.
this could be a sign that its time to get a new phone but for now is there anyway to improve performance at all? i already am using the fastest trinity kernel and i have tried multiple roms and all of them seems to lag after hitting 100 apps mark which is ridiculous.
Have you made sure that the phone is not running out of memory as that is what usually causes the slow problems...I too have a 100+ apps and little or no lag. Try a different kernel and Rom maybe u could also tweak the processor speeds and stuff to get your desired performance...
If I helped hit thx
«««««««CYANOGENMOD 10.1 and FRANCO KERNEL»»»»»»»»»
Flash stock factory ROM and do a full wipe.
If you want later then flash custom ROM which is "STABLE".
Then make sure you have enough free memory on your Nexus's internal memory to avoid the lags.
You actually can't improve your Nexus's performance any other way, tweaks speed up very much..
I have over 60 apps installed (usually apps that I need) and some games..
I have 1.4 GB free memory on My Nexus and I use some cleaner apps to get more free space and I don't have any lags..
I use stock ROM that I've modified and stock default kernel..
The hardware slows primarily because of software (apps). Once the hardware fails, it fails.
Check and reign in the number and frequency of apps that sync, update and or check in.
Are you syncing an email client and or keeping them on the device rather than say the Exchange server?
Sent from my Galaxy Nexus using xda premium
kudoboi said:
i have a feeling this phone is starting to show its age. it seems whenever i install more than 100 apps on this phone it just becomes laggy as hell. to the point where right now the keyboard doesn't even open until 10 seconds later and phone constantly make weird noises when using tune in radio or youtube. the phone is also so slow that it can't even run temple run 2 or any of the games that came out recently. im using xylon rom with trinity kernel for those wondering. i honestly cannot use this phone anymore without having to do a factory reset every month just to stop the lag.
this could be a sign that its time to get a new phone but for now is there anyway to improve performance at all? i already am using the fastest trinity kernel and i have tried multiple roms and all of them seems to lag after hitting 100 apps mark which is ridiculous.
Click to expand...
Click to collapse
I have 276 apps on my Nexus and (perceived) performance is better than ever using XENON HD Stable-4.0 and the Franco kernel r364. For the latest update of the ROM, I decided to risk a dirty flash. I seem to have gotten away with it. Performance "feels" excellent, whatever that is worth. My last factory reset was about 2 months ago.
The ROM and kernel have a variety of performance tweaks. I wish there was a way to benchmark performance in a controlled fashion. I hate feeling and perception in the performance department.
On the new ROM, WiFI performance is now solidly pegged at my account's limit of 30 MBs. It was all over the map before, although I realize that many factors affect the Speed Test app.
The "seeder" app helped a lot for my device in reducing lag. The overall community is sharply divided about the effectiveness of the seeder: YMMV. Its worth trying, though. I've been using it for about 6 weeks. Other than the Google Play Store updates, I don't have lag any more. Before the seeder, I felt like you -- the phone was almost unusable.
Regarding the device feeling dated, this ROM supports the expanded desktop and the pie. Wow, the phone feels new again. No kidding.
smtom said:
The hardware slows primarily because of software (apps). Once the hardware fails, it fails.
Check and reign in the number and frequency of apps that sync, update and or check in.
Are you syncing an email client and or keeping them on the device rather than say the Exchange server?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I also observed that the apps that run sync/update/check in were slowing down the phone. Check for apps that have daemons associated with them. Decide whether its worth having.

Task killers

Experts always say that you don't need a task killer because of the way android handles memory. But here's my experience.
I used to have an early smartphone running android 2.3 and it would sometimes run as slow as molasses. An installed task killer would then show very little amounts of available ram. Clicking on the task killer would increase the available ram and the phone would become fast again.
Now I use a fast Nexus 7 with android 4.3 and there are occasions when the touchscreen would seem to freeze for a few seconds and then return to normal. I know that there is debate on the cause for this. But I'm starting to suspect that this may be caused by something using memory in the background so less is available to the running app. That is because if I reboot the touchscreen becomes responsive again. If so this might be something a selective task killer could help by freeing up ram. Especially if it could be run from within any running app. It would be less tedious than rebooting.
What do the experts think?
My opinion
Not that I am any expert, but the fact that the problem occurs across many different ROM's and kernels (and doesn't occur on other devices running the same versions of android) makes me think it is likely more hardware related than software related. Therefore, killing tasks wouldn't be likely to help.
drewmey said:
Not that I am any expert, but the fact that the problem occurs across many different ROM's and kernels (and doesn't occur on other devices running the same versions of android) makes me think it is likely more hardware related than software related. Therefore, killing tasks wouldn't be likely to help.
Click to expand...
Click to collapse
Thanks.
Hope you're wrong....
Anderson2 said:
Thanks.
Hope you're wrong....
Click to expand...
Click to collapse
No,he isn't wrong.This tablet has some touchscreen issues,although KitKat fixed most of them.Task killers are really useless here,because even if you are running a high-end game you will still have ~500 MB free.
Android is generally very good at memory management. You might be experiencing momentary garbage collection as it reclaims unused memory, but it shouldn't happen too often on the 2013 N7. Two gigs of RAM is a lot to fill up.
On some tablets with less memory, a "soft reboot" app like this can help by closing apps, then reopening what's required. This can help on a slower Android device before starting a game or other memory-intensive app (edit: I meant app, not device), but again, your N7 has a lot of memory and shouldn't need this. Try a startup manager and/or Greenify to keep unnecessary things from launching automatically. You could also try wiping cache, system and userdata, then reflashing your ROM (don't forget to make backups first!).
Thank you all. I appreciate the sage advice. I'm still on 4.3. Maybe I should go ahead and accept the ota update to kitkat.
I would. Let me add one more thing: the way Android works, running a task killer makes the CPU work a little more, which in turn uses up a little more of the battery's charge, so running one repeatedly (and some can run at regularly scheduled times) just reduces battery life. So with something like an N7 with lots of RAM that rarely gets filled, the best general practice is to let Android do its thing.
Pandae said:
I would. Let me add one more thing: the way Android works, running a task killer makes the CPU work a little more, which in turn uses up a little more of the battery's charge, so running one repeatedly (and some can run at regularly scheduled times) just reduces battery life. So with something like an N7 with lots of RAM that rarely gets filled, the best general practice is to let Android do its thing.
Click to expand...
Click to collapse
Thank you again.
Should I also stop using lagfix?
Anderson2 said:
Thank you again.
Should I also stop using lagfix?
Click to expand...
Click to collapse
I was unfamiliar with this app, but after reading what it does, I see it's wholly unnecessary for either N7 generation and most newer Android devices. Android 4.3 introduced TRIM support (equivalent of Linux fstrim), so you don't need this app at all.
Anderson2 said:
Thank you again.
Should I also stop using lagfix?
Click to expand...
Click to collapse
If the 4.4.2 update doesn't solve the issue, RMA if at all possible.
Anderson2 said:
Thank you again.
Should I also stop using lagfix?
Click to expand...
Click to collapse
You can keep using Lagfix if you want but Trim is working in 4.3 and above. That said... I have Lagfix also and on the rare occasion I use it there's not much for it to do because TRIM has been taken care of already. If I remember right the kernel (ElementalX) I use runs it in a script also. I would go ahead and update to 4.4.2, the firmware update might just solve your problem and there was also a noticeable increase in performance with the update to kitkat.
wantabe said:
You can keep using Lagfix if you want but Trim is working in 4.3 and above. That said... I have Lagfix also and on the rare occasion I use it there's not much for it to do because TRIM has been taken care of already. If I remember right the kernel (ElementalX) I use runs it in a script also. I would go ahead and update to 4.4.2, the firmware update might just solve your problem and there was also a noticeable increase in performance with the update to kitkat.
Click to expand...
Click to collapse
Thank you. I knew about trim being now included but like you use lagfix once a week anyway. Will move to 4.4.2.

Categories

Resources