Sometimes we feel that our nexus 7 us getting slower.Here are some tips to speed it up again!!
1 Free Up Some Space
Many people report that the Nexus 7 slows down as it fills up. When the 16GB Nexus 7 gets to about 3GB of storage space left, it begins to slow down.so freeing some space helps a lot.
2 Disable Currents Background Sync & Other Background Apps
Google Currents syncing is a notorious cause of lag on the Nexus 7. If your Nexus 7 is too slow or isn’t responding to touch events properly, open the Currents app, go into its Settings screen, and disable the Syncing option. This will prevent Google Currents from constantly downloading and writing data in the background.You may also want to disable background-syncing in other apps, or set them to sync infrequently — similar problems could be caused by other apps downloading and writing data in the background.
3 Delete Multiple User Accounts
If you have multiple user accounts set up on your Nexus 7, you may want to disable them. When you have multiple user accounts set up, apps on other user accounts are syncing data in the background — so if you have three user accounts, three different Gmail accounts will be syncing in the background at once. It’s no surprise that this can slow things down on the Nexus 7′s older hardware.
4 Android 4.2.2
If u ever upgraded to android 4.2.2 and felt there is some lag and found no other way 2 fix it dont hesitate to downgrade to 4.1.2 (I have done this as 4.1.2 feels a lot more faster than 4.2.2 for me.)
5-Run TRIM (LagFix or ForeverGone)
Due to a bug with the driver for the Nexus 7′s internal Samsung NAND storage, Android on the Nexus 7 was not properly issuing TRIM commands to clear unused sectors. This caused write speeds to slow down dramatically. This was fixed in Android 4.1.2, and Android should now properly be issuing TRIM commands to the internal storage.
However, this update does nothing to fix existing sectors that should have been TRIMMed in the past, but were not. To do this yourself, you can try the LagFix app from Google Play AND this will will fix the problem.Link-
https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix
6 My personal best recomendation
Use the AVG Memory & Cache Cleaner app. link- https://play.google.com/store/apps/details?id=com.avg.cleaner
After clearing the cache with this app my nexus 7 runs like new .Also try Advanced Task Killer, might help a bit.link- https://play.google.com/store/apps/details?id=com.rechild.advancedtaskkiller
Please press the thanks button :good: if this helped you!
6 - don't use too many widgets, they run in the background and can slow down your tablet too
Sent from XDA app
Task killers are pretty debatable. Android is designed in a way that means task killers can actually decrease battery life and slow the device down in some situations.
Sent from my Nexus 7 using XDA Premium HD app
The first few are common-sense solutions that demonstrably work on most devices.
The task manager and memory cache suggestions are snake oil and should be avoided. There is almost no evidence that demonstrates that any of these apps actually improve performance, and there's a lot that suggests they actually impede both performance and battery life. A task killer/memory cleaner sweeps through the system, looks for things not running in the foreground, and kills them. Sounds simple enough, right?
That is, until you realize that these programs can't prevent the apps they just killed from being triggered, and often cannot distinguish between benign apps that have legitimate background services and programs you don't want running. It then unloads them from memory (because free RAM is always good, right? Wrong), which generally results in I/O thrashing as the system tries to reload the killed applications and sees them killed again. And that ties up I/O operations, which have never been the Nexus 7's strong point.
And mind you, starting an activity is one of the most memory-intensive processes in Android, whereas keeping an app in a dormant state has significantly less impact on the system. Multitasking works better to boot, and battery life is better because the system doesn't have to waste resources regenerating resources over and over and over again.
As of this writing, the only real "performance boosting" apps I have seen are Lagfix and Greenify, because they go in at the system level (requiring root access) and actually make the right changes. Greenify temporarily "freezes" an app similar to the Disable option (or Titanium Backup) until it's in use, but unlike a task killer, it also shuts down any self-triggers an app might have to avoid thrashing. If you open the app, Greenify defrosts the app immediately for a minimal performance hit, then freezes it again after you haven't used it for a while.
Lagfix is an implementation of fstrim, which helps keep the internal memory running more smoothly. It's particularly useful on the Nexus 7 owing to the generally poor I/O performance of the internal NAND flash.
1) Install custom ROM
2) Install custom kernel
3) Overclock your CPU
4) Change CPU Governor to performance
5) Change Tegra 3 CPU Quiet Governor to Userspace
6) Setup ZRAM
7) ???
8) Profit
Username invalid said:
1) Install custom ROM
2) Install custom kernel
3) Overclock your CPU
4) Change CPU Governor to performance
5) Change Tegra 3 CPU Quiet Governor to Userspace
6) Setup ZRAM
7) ???
8) Profit
Click to expand...
Click to collapse
9) Come on XDA and complain about battery life.
Sent from my Nexus 7 using Tapatalk HD
veeman said:
9) Come on XDA and complain about battery life.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
The more energy efficient ROM, kernel and undervolting would compensate for the higher clock speed voltage.
Username invalid said:
The more energy efficient ROM, kernel and undervolting would compensate for the higher clock speed voltage.
Click to expand...
Click to collapse
And the one step that users who would do 9) always mess up will invariably muck things up/they'll have bad sync settings and moot the whole process.
veeman said:
9) Come on XDA and complain about battery life.
Click to expand...
Click to collapse
Yep. Performance governor? Derp. This whole thread is derp.
Try many different ROMs with many different kernels, find the best match, and be happy with it
On another note, keep away from Gapps. They are a real issue, take about 50 mb on my phone, an the first thing I nuked after rooting. Beleive me, my HTC Sense forgot bein laggy after that. This implies to most devices. Every ROM that I have used, has been devoid of Gapps.
Use F2FS ported to nexus 7 by legolas
Sent from my Nexus 7 using Tapatalk
Another tip: apps may open faster with row io scheduler (prioritized read speed) in custom kernel.
Sent from my iPhone using Tapatalk
Amisuta said:
Another tip: apps may open faster with row io scheduler (prioritized read speed) in custom kernel.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
which rom will you choose for better performance
omni or slimkat
nat510 said:
which rom will you choose for better performance
omni or slimkat
Click to expand...
Click to collapse
I haven't used omni or the normal slimkat before, but I've used the all-f2fs version, which works great.
nat510 said:
which rom will you choose for better performance
omni or slimkat
Click to expand...
Click to collapse
Omni worked much better for me. Also benchmarks are much much higher.
Sent from my Nexus 7 using Tapatalk
467) isn't there 45 000 000 other threads just like this?
Thank you :good:
Good tips.
I personally use ROW and performance governor with no overclocking and my tab runs super smooth.
Thanks.
Although Android 4.3 solved the issue with NAND Trimming.
T-Keith said:
Omni worked much better for me. Also benchmarks are much much higher.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Year, Omni is awesome
Related
You don’t need to change your ROM to get the best from your 2x, just a rooted stock ROM and a couple of apps that will change things dramatically. One thing I’ve noticed on the 2x is its memory management is too lenient and gets consumed quickly by background tasks etc. In no time I was down to 40-30Mb free memory and then my phone would run like a dog resulting in a reboot as the only solution.
Installing task and app killers are not the way, as they’ll only give you a short respite before the apps and background tasks you killed relaunch.
However, there is a solution.
1)Root your phone using SuperOneClick (piece of cake, instruction already on this forum)
2)Install “AutoKiller Memory Optimizer” by AndRS Studio free from the market
Optional
3) Install “Watchdog Task Manager” by Zolmut LLC (There’s a free or Paid version) I paid!
4) Install “Root App Remover” by Best of Best Android app
AutoKiller is not a task killer/manager it reconfigures Androids inbuilt memory manager to kill or suppress memory usage by applications and tasks. I now always have about 140-170MB free RAM at all times regardless of what I’m doing (but I do close my apps with the back button rather than click home)
AutoKiller Memory Optimizer Settings
I’ve used the ‘Extreme’ settings to ensure I have around 150MB free, and this makes a huge difference in everything I do with the phone.
----------Optional things you may want to consider-----------
Watchdog
Yeah, I know this is a task killer but Watchdog is different from other task mangers as it monitors CPU usage rather than free RAM, 3D Gallery for example is a CPU hog on my 2X, so I configured it to be killed if it consumes more than 30% CPU whilst running in the background, you’d be surprised what saps your battery!
Root App Remover
Uninstall the tosh supplied on the ROM, I removed the following, AndroidBackup (I use Titanium Backup), CarHome, F-Secure_Mobile_Security, SNS (If you’re not using the built in Facebook and Twitter app).
I also use LauncherPro with Beautiful Widgets to give my phone an almost HTC Sense look and feel and uninstalled LG Home using Root App Remover afterwards.
Hope it makes a difference for you, it did for me, vote if you like
What do you think having 140-170MB RAM free at all times actually does?
Guess what? Nothing.
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
We want to see some bench marks.
Thanks for sharing! My phone does become much more responsive
Sent from my LG-P990 using XDA App
I tried the app too and i can say that it works, I also did some of the advanced tweaks.
phone seems more responsive now.
Yes, me too. It's more responsive now. Also when I open app manager, the app list is a lot faster.I know it's more related to file read/write but still it's nice to finally able to browse with less waiting time.
Sent from my LG-P990 using XDA App
thx
good one and simple, thx
cann someone please post some benchmarks?
Here are some screenshots, tested with AnTuTu Benchmark
The first one is v10c stock, some apps like f-secure, carapp etc frozen, second one is with using autokiller memory with preset extreme, third one is to compare, this was while using cm7.1 rc
now we'll see if autokiller works stable ^^
edit: realized that with cm7 something seemed to be wrong with the sd-card, so don't forget to compare the single-scores
spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'm sure Rusty knows what he is talking about. Thing is, this talk about "the more free ram the better" has been repeated so many times, and at the end of the day, it seems to be more about user preference.
The default LG ROM seems to allow tasks to run in the background until it reaches around 50MB free RAM, then it starts to close tasks one by one. For multi-taskers like me, this is fine, I love how I can switch between facebook, tweetdeck, miren browser, google+, gmail, and messaging without seeing the apps reload.
For some, they'd want to open a task, close it, and move on to another without looking back. I guess that is where the 100MB of RAM is good for.
If you guys will be looking at benchmarks, I can guarantee that you will have higher scores with RAM optimizers. As benchmarks do not test multitasking, they simply check the performance of your phone at that point in time. (Which is also why some modders pump up their CPU freq to insane values before doing their bench then posting it.)
I have nothing against AKMO, and I find it very effective for Froyo builds. But I would recommend that each user try it out themselves. It's not a "1 fix for all" thing.
spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
kiljacken said:
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
Click to expand...
Click to collapse
Does O2X already support swap space in EXT? (Or are your referring to VM heap?)
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
akyp said:
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
Click to expand...
Click to collapse
Yeah, FR19 is one of the more stable ROMs out there. Try full wipe then reflash maybe.
After flashing a rom onto my LG P990 it works flawlessly-everything is nuttery smooth, fast and reliable but after some uptime and few days of using it suddenly starts to lag. It really pisses me off since P990 is quite powerfull when it comes to specs but my friends Galaxy S somehow maintains it's performance.
So the question is how to make sure that my phone will not reduce it's performance so drastically over time?
I'm runnig latest Temasek's KANG and ETaNa's latest beta kernel with 1,4GHz OC.
Do you have alot of apps installed?
Try to see how much RAM usage you have on boot and after it starts to drop performance.
Yeah I read somewhere that there is a memory leak problem with the o2x...restart your phone once in 3 days..things should be fine
Rebooting doesn't help. If it did I would assume that it's simply because an app/apps is causing the drop and then I would try to find it. I do have a lot of apps on my phone but most of them shouldn't be running by themselves in the backgroud (mostly games and such).
I have same problem (on ICS ROMs). After flash, everything is fast, after few days....I have to wait for call for 30 sec....horrible...
I have noticed that problem witch made me a flashaholic .. you could begin with deleting facebook app, messenger and google plus (drainers) then dl rom manager and set in on hard gaming , worked ok for me
Sent from my LG-P990 using xda app-developers app
Also I have a major USB issue. Almost always after turning off storage mode the phone just hangs and I have to remove the battery to restart it. Sometimes it even reboots by itself while transfering files.
Memory leak... If this problem annoys you flash a stock froyo rom or cm based rom..
Have been using CM7 for probably 12 months, but the performance in the last few weeks seems to have got much worse....
i think it could be a baseband issue...I am ...during the verification of the existing problem ...
Since rebooting and installing the tweakaio.zip with lagfree patch for my kernel everything seems better. Not freshly-flashed good but much better.
I don't have any problems with my O2X. It runs buttery-smooth even after two weeks without rebooting. However, the internal IO does get pretty slow after a while. It's nothing too dramatic though.
Heres my recommendation;
Latest Temasek ROM & Kernel
Use the built-in ramhack (this really helps alot!)
Using TitaniumBackup, freeze un-needed apps or uninstall them (be careful with this, make backups. This is mainly meant for system apps that you don't need, i.e. Car Home so they won't fill up your RAM unnecessarily)
Using Autorun Manager just prevent most apps from auto-starting themselves.
Optional; let a task manager kill apps for you periodically. I always read that it's not good to use task managers but I never seem to have any problems with them. I've got 200MB RAM free all the time, even after several days of usage. To prevent killing specific apps just add them to the ignore list of your task manager.
You could also use the lagfree + dalvik cache fix by tonyp and adjust the LMK values.
This setup is working perfectly fine for me, just try it out yourself.
Edit: I also have to note that I don't have many apps installed. Just the things that I really need such as AlarmDroid, the XDA Premium App (!), PimpMyCpu, etc.
xExabyte said:
I don't have any problems with my O2X. It runs buttery-smooth even after two weeks without rebooting. However, the internal IO does get pretty slow after a while. It's nothing too dramatic though.
Heres my recommendation;
Latest Temasek ROM & Kernel
Use the built-in ramhack (this really helps alot!)
Using TitaniumBackup, freeze un-needed apps or uninstall them (be careful with this, make backups. This is mainly meant for system apps that you don't need, i.e. Car Home so they won't fill up your RAM unnecessarily)
Using Autorun Manager just prevent most apps from auto-starting themselves.
Optional; let a task manager kill apps for you periodically. I always read that it's not good to use task managers but I never seem to have any problems with them. I've got 200MB RAM free all the time, even after several days of usage. To prevent killing specific apps just add them to the ignore list of your task manager.
You could also use the lagfree + dalvik cache fix by tonyp and adjust the LMK values.
This setup is working perfectly fine for me, just try it out yourself.
Click to expand...
Click to collapse
good call.
lately ive been using etana kernel with the oall mighty temaseks rom, but the music for eg gets clipped when i open other apps start wifi/bt while playing
xilw3r said:
good call.
lately ive been using etana kernel with the oall mighty temaseks rom, but the music for eg gets clipped when i open other apps start wifi/bt while playing
Click to expand...
Click to collapse
I never listen to music on my phone so I can't help you out with that. Try a different kernel?
I am wondering if we have a task manager/process explorer app for Nexus 4? Currently I am using AirDroid v2 that includes a task manager, but I am looking for one with more options.
I travel a lot & would like to kill as much unwanted applications running in the background as possible to conserve battery.
There is no more need to use task killer to manage android systems any more. You will be doing more harm than good, in fact there is no good in killing tssks manually.
Sent from my SAMSUNG-SGH-I747 using xda premium
Point noted.
But when I use Airdroid task manager, I see a process when the corresponding app is not running the background.
To mention a few; Cut the rope free, stocks & Hill climb racing.
Few system process like picasa uploader, chrome etc.
As you said andoird may optimize most of them, but I would like some control when running thin on battery.
mohan_168 said:
I am wondering if we have a task manager/process explorer app for Nexus 4? Currently I am using AirDroid v2 that includes a task manager, but I am looking for one with more options.
I travel a lot & would like to kill as much unwanted applications running in the background as possible to conserve battery.
Click to expand...
Click to collapse
use greenify https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en to hibernate any persisting apps/processes (except system). apps relaunch when you open them.
Killing apps and then having to reload them actually uses more battery than them being dormant in the background and already loaded when called upon. The problem is when you have misbehaving apps that stay in the foreground eating up cpu, instead of going dormant into the background. And this does happen. I use an app called Watchdog that alerts me when this happens. It allows you to kill the app when this happens. It also allows you to whitelist and blacklist apps and processes.
Sent from my Nexus 4 using Tapatalk 4 Beta
main phone setting, apps, running.. default task/process manager. in the top right will be an option to show cached process as well.
simms22 said:
main phone setting, apps, running.. default task/process manager. in the top right will be an option to show cached process as well.
Click to expand...
Click to collapse
We all know that is there. The op mentioned wanting more options, mainly monitoring and kill options.
Sent from my Nexus 4 using Tapatalk 4 Beta
mohan_168 said:
I am wondering if we have a task manager/process explorer app for Nexus 4? Currently I am using AirDroid v2 that includes a task manager, but I am looking for one with more options.
I travel a lot & would like to kill as much unwanted applications running in the background as possible to conserve battery.
Click to expand...
Click to collapse
fernandezhjr said:
We all know that is there. The op mentioned wanting more options, mainly monitoring and kill options.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
fast reboot(free), but the paid version i like better https://play.google.com/store/apps/details?id=com.greatbytes.fastreboot&hl=en
rayiskon, I will try greenify & let you know how that helps.
fernandezhjr, I agree restarting app is not an optimal way, but I require to squeeze battery to atleast make phone calls when I am away from charging options.
simms22, fast reboot looks promising. I'll try the free one for now and take it from there.
It's kind of already been said, but I want to clarify as much as possible.
Apps running dormant in the background (using RAM) use no more power than if it weren't running. This is because all of the memory you have is being refreshed all the time, the controller has no idea whether there is actually data there, it still refreshes the entire space of memory.
Apps running "dormant" but using CPU do use more power than if it weren't running. I assume OP is wanting some sort of monitoring app that shows which apps are using CPU, in which case is fine. If OP is wanting to kill all apps that he isn't using at the time to conserve battery, then he would actually be doing the opposite of what he wants, as it requires to CPU to spin back up to restart it later. Again, the difference here is RAM vs CPU, one doesn't use battery (or rather, uses the same amount of battery, no matter how much of it is being utilized), and one can use more or less battery depending on how much it's used.
Johmama said:
It's kind of already been said, but I want to clarify as much as possible.
Apps running dormant in the background (using RAM) use no more power than if it weren't running. This is because all of the memory you have is being refreshed all the time, the controller has no idea whether there is actually data there, it still refreshes the entire space of memory.
Apps running "dormant" but using CPU do use more power than if it weren't running. I assume OP is wanting some sort of monitoring app that shows which apps are using CPU, in which case is fine. If OP is wanting to kill all apps that he isn't using at the time to conserve battery, then he would actually be doing the opposite of what he wants, as it requires to CPU to spin back up to restart it later. Again, the difference here is RAM vs CPU, one doesn't use battery (or rather, uses the same amount of battery, no matter how much of it is being utilized), and one can use more or less battery depending on how much it's used.
Click to expand...
Click to collapse
Thanks for the detailed explanation. I understand killing process, shutting down cached process or apps & later restarting them is only going to fire up the CPU usage which completely defeats the purpose of conserving battery.
Though not a daily ask, at times I am stuck in situation where a phone call or SMS is all I need to keep me going.
Hello,
I'm looking for a good ICS ROM with much RAM memory free.
I know there are many good ones like RocketRom, but the RAM is priority for me, as I use a lot off apps and I don't want them to get killed every time I exit them.
The ROM may be stock based (best) or even some other type.
Do You know some You could recommend?
PS. They don't have to be fast as hell.
Admin please don't close this thread.
try bulletproofing them and freezing/removing unwanted apps.
Also try to set autostarts off for apps you only want to run on request as well as proper exiting them to prevent running ram.
granted its android that should optimize ram usage which is why amount of free ram shouldnt impact, but yet it does.
maybe you have set dont keep activities to on development settings if so, disable it. lol.
Other tweaking can be done with minfree and oom levels to lower values, stock however they are pretty low.
last random thing I can come up with is less memory footprint apps. Alternatives for ones you are using. Lol. Goodluck!
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
try bulletproofing them and freezing/removing unwanted apps.
Also try to set autostarts off for apps you only want to run on request as well as proper exiting them to prevent running ram.
granted its android that should optimize ram usage which is why amount of free ram shouldnt impact, but yet it does.
maybe you have set dont keep activities to on development settings if so, disable it. lol.
Other tweaking can be done with minfree and oom levels to lower values, stock however they are pretty low.
last random thing I can come up with is less memory footprint apps. Alternatives for ones you are using. Lol. Goodluck!
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I have used about 170 apps on my SGS2, now I've reduced them to about 120. I have also deleted some system apps, but the problem is android OS.
Killing apps is disabled for 100%, it's just due to 70MB memory free. The launcher is killing almost every time I turn on some other app (build.prop edit didn't stop it from closing).
Android just uses too much RAM. Fresh ROM uses 400+ MB, that's so much.
That's why I'm looking for some ROM that uses max.300MB. Are there any?
I wish I could have ROM from my xpiera x10, which used max 120MB hehe
jakuburban said:
Hello,
I'm looking for a good ICS ROM with much RAM memory free.
I know there are many good ones like RocketRom, but the RAM is priority for me, as I use a lot off apps and I don't want them to get killed every time I exit them.
The ROM may be stock based (best) or even some other type.
Do You know some You could recommend?
PS. They don't have to be fast as hell.
Admin please don't close this thread.
Click to expand...
Click to collapse
These type of threads are not allowed....as the best is up to the individual to figure out, what is best for me, may not be best for you....
Okay guys,
with the introduction of 4.4 kitkat, Google decided to include ART as an optional second runtime that can be enabled through developer options. Naturally when promised faster app launch times, people will turn it on. ART is not stable however and so problems will be occur. For this reason, in hopes to prevent kernel developers, rom developers, and android developers from having their thread hijacked, I am making a thread dedicated to runtimes here. DO NOT POST ABOUT THIS TO DEVELOPERS ON THEIR THREADS, bugs when you are running ART are not their fault.
What is Dalvik?
Dalvik is the process virtual machine (VM) in Google's Android operating system. It is the software that runs the apps on Android devices. Dalvik is thus an integral part of Android, which is typically used on mobile devices such as mobile phones and tablet computers as well as more recently on embedded devices such as smart TVs and media streamers. Programs are commonly written in Java and compiled to bytecode. They are then converted from Java Virtual Machine-compatible .class files to Dalvik-compatible .dex (Dalvik Executable) files before installation on a device. The compact Dalvik Executable format is designed to be suitable for systems that are constrained in terms of memory and processor speed. Dalvik is open-source software.
Dalvik is named after an Icelandic city.
(source)
Okay so what is ART?
ART is a project Google has been working on for reportedly for 2 years. The goal of ART was to produce a faster runtime that wouldn't suffer from the problems Dalvik suffers. Android Kit Kat 4.4 is the first operating system with ART included in developers options although it is unclear just how recent this version is.
ART stands for Android RunTime
(source)
Great, Whats the Difference Then?
The main difference between ART and Dalvik is when they compile app code. Dalvik operates under a JIT (Just In Time) compilation method which means that when developers make their apps, they partially compile their code into bytecode which is interpreted by the java virtual machine. Dalvik converts bytecode to machinecode as the app runs to increase performance (bytecode execution is slower than machinecode execution). ART differs from Dalvik by performing this compilation of bytecode to machine code at installation of the app and saves this to the phones storage (not ram).
(source)
So Why Use ART?
Using ART instead of Dalvik allows the system to use much less resources during runtime. When apps are running, interpretation of bytecode is not ongoing, this can reduce CPU load and RAM usage. The resulting effect is faster app startup times (reportedly almost twice as fast) and better in app performance.
It should be noted that performance boosts will only really improve for the java components of apps. Apps like games which rely on the NDK or other languages will receive more incremental experience boosts.
(source)
Why Shouldn't I Use ART
Well first and foremost, Google's documentation of ART suggests not using ART because it can cause app instabilities and an unstable android implementation all together. It is still largely in development and it is unknown just how recent the version included in the current kit kat build is. Google is introducing it to the development community but really doesn't intend users to use it as a daily runtime.
Also since ART precompiles and saves that precompiled code upon installation of apps, it takes up more storage. The increase is about 10-20% of the code in the application. Remember the majority of apps usually comprises media files such as images, videos, sounds... so those components will be unaffected. For example, the Google+ apk is about 28Mb yet the code is only comprise of 7Mb. The increase in storage size is nominal, but worth noting.
Also the first start up after enabling ART can take up to 10 minutes due to this compilation occurring. Installation of apps will also take slightly longer but with hardware on the Nexus 5 you are unlikely to even notice.
ART also can cause issues with app backup and restoration.
(source) (source)
Custom Roms and ART
As developers start building Kit Kat roms from source they will have to decide if they would like to include ART in their builds. Google has created a flag to include ART in addition to Dalvik. This is a simple implementation, but if threads keep getting hijacked by discussions of ART and bugs, I wouldn't be surprised if developers choose to exclude ART from their builds.
ART also cannot function with deodexed apps. The odex files are necessary for bytecode to machine code compilation. Flashing a deodexed ROM or gaps with ART enabled will produce force closes and crashes to the point the UI won't be functional.
Also initial setup between Roms will take longer with ART since performing a factory reset as well as clearing caches will clear the stored precompiled code that ART saves. Dalvik will always be enabled at start up, so switching to ART will require a reboot and a wait for set up.
(source)
In my synopsis of ART and Dalvik I may have made a mistake or two or not explained something properly. If you spot a mistake or would like clarification, simply post and I will modify the OP.
Please, please, please send people to this thread if they are asking about runtimes in a developers thread. Having had my kernel thread hijacked by unrelated issues that are outside of my control, I understand the pain.
ART breaks Titanium Backup, just fyi
Sent from my Nexus 5 using Tapatalk
And quadrant and whatsapp
afazel said:
ART breaks Titanium Backup, just fyi
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
added to OP
I will not be posting a complete list of apps broken by ART, it would take way too much time and this is likely to change as the developers get to update their code to be optimized on 4.4. You are welcome to post any issues, but its pretty much ART can break a lot of apps.
I find app compatibility remarkably high. I have over 60 apps installed and the only ones that aren't working is titanium backup and greenify.
Everything else works even games like asphalt 8 and pvz2.
dwang said:
I find app compatibility remarkably high. I have over 60 apps installed and the only ones that aren't working is titanium backup and greenify.
Everything else works even games like asphalt 8 and pvz2.
Click to expand...
Click to collapse
Games generally are not coded in Java (usually NDK or something else) and so they will be effected much less by ART than other apps.
I thought that the play store felt noticeably faster when using ART when I was installing a bunch of apps last night.
Titanium backup and whatsapp instability are huge deal breakers for me, unfortunately.
Sent from my Nexus 5 using XDA Premium 4 mobile app
dwang said:
I find app compatibility remarkably high. I have over 60 apps installed and the only ones that aren't working is titanium backup and greenify.
Everything else works even games like asphalt 8 and pvz2.
Click to expand...
Click to collapse
greenify seems to be working fine for me with ART. What problems are you experiencing?
agalvin13 said:
greenify seems to be working fine for me with ART. What problems are you experiencing?
Click to expand...
Click to collapse
Perhaps a reinstall on ART would fix the problem?
Hi,
I know this may sound really stupid but.. can you guys write down some of your most used Apps that are written in Java? Do you notice any performance improvement?
Also, does ART affect overall android experience (original apps, launcher).
I am no developer and I don't know much about computer languages (so please don't throw rocks at me for those questions) but I like to tweak my phone to see what seems to be the best for my phone.
Does ART affect battery life?
Sent from my Nexus 5 using Tapatalk
MrBelter said:
And quadrant and whatsapp
Click to expand...
Click to collapse
Quadrant is working just fine for me.
busab said:
Does ART affect battery life?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It theoretically will and could. I haven't noticed a markable increase in battery life so far though. One would have to perform some test but scrolling and apps loading seems more fluid imo. I am leaving it on.
busab said:
Does ART affect battery life?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Not sure, tomorrow I'll see and report back.
It's not like the new Holy Grail to me, performance wise...
busab said:
Does ART affect battery life?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Theoretically, yes since it attempts to decrease cpu load and ram usage at runtime, it should theoretically give you some better battery life. But battery life is hard to gauge, so don't expect any definitive results on that anytime soon.
miHah said:
I know this may sound really stupid but.. can you guys write down some of your most used Apps that are written in Java? Do you notice any performance improvement?
Also, does ART affect overall android experience (original apps, launcher).
I am no developer and I don't know much about computer languages (so please don't throw rocks at me for those questions) but I like to tweak my phone to see what seems to be the best for my phone.
Click to expand...
Click to collapse
Pretty much all apps that are regular run of the mill apps will be coded in Java. It is just intensive programs like games are generally coded using the NDK, but all other apps in large will be in java (the vast majority).
When you say original apps, I assume you mean system apps like the GE Launcher, or settings app. These are all coded in java so yes they will get improvements too.
EDIT: if you want what is best for your phone, stick with dalvic, it's more stable.
Something I noticed with the Nexus 4 (Dalvik, obviously) is that if you have a lot of apps (10+ maybe?) open, the recent apps will take a slight delay to show up. It isn't lag, but it even appears with the Nexus 5. If you switch to ART, the recent apps will show up immediately, no matter what. I'd say that alone would be worth it to switch to ART, it makes everyday use feel notably smoother.
aletto said:
Something I noticed with the Nexus 4 (Dalvik, obviously) is that if you have a lot of apps (10+ maybe?) open, the recent apps will take a slight delay to show up. It isn't lag, but it even appears with the Nexus 5. If you switch to ART, the recent apps will show up immediately, no matter what. I'd say that alone would be worth it to switch to ART, it makes everyday use feel notably smoother.
Click to expand...
Click to collapse
I agree - the bad part is that it breaks tibu and whatsapp. Why can't devs be a bit more on their toes when an update comes ?
Been running ART for a full day now, and aside from TB, I've had no issues. Greenify works fine, and I don't use Whatsap, so hopefully by the time custom ROMs that support ART come out, TB will be updated to fix this issue. If not, oh well. I'll stick with it for now seeing as how much better some notoriously slow and crappy apps are running. Maybe it's just a placebo, but I've never seen the Facebook app load so quick and scroll so smoothly as it does now.