Related
Please tell my which is best software that stops applications to run automatically at startup
tell me the application which works
no one is using any app. to stop unnecessary start up of tasks
try autostarts its very good
Sent from my GT-I9000 using Tapatalk
Ditto on Autostarts. Also, Autokiller Memory Optimzer works really well, it doesn't kill tasks itself, it tweaks the Android function thar does it to work better.
auto killer mem optimizer workd well for me.but now i simply don use any of those batt saving app,mem apps etc i jus kill apps in inbuilt task killer...iam using my phone to the peek cause at the end ill b getting a 2ghz dual core by selling sgs.......cant stick to old things lol........cheeerz
tarunagg said:
Please tell my which is best software that stops applications to run automatically at startup
tell me the application which works
Click to expand...
Click to collapse
... what?
Do any of you even understand how Android works?
so mind sharing ur exp wiv us on how it works???
manosv said:
try autostarts its very good
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
+1 Autostarts. It amazes me what runs on the phone after start-up, after you switch states or update apps. The perfect cure for batt draining nonsense
rocky23 said:
so mind sharing ur exp wiv us on how it works???
Click to expand...
Click to collapse
Google it. Android is Linux based. Its memory management is not the same as Windows. I'd explain further, but you're the 4,753,857,195 person to ask.
I spent 10s and googled it for you. Here's a quick link that explains it in simple terms.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Basically having applications in RAM is a GOOD thing. Constantly killing them is likely to WORSEN PERFORMANCE AND BATTERY LIFE.
Shanakin said:
I spent 10s and googled it for you. Here's a quick link that explains it in simple terms.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Basically having applications in RAM is a GOOD thing. Constantly killing them is likely to WORSEN PERFORMANCE AND BATTERY LIFE.
Click to expand...
Click to collapse
That's right. On the other hand - permitting almost every app to load at startup isn't the best approach, as you will soon run out of memory - therefore using apps like autostart makes sense imho. But constantly killing everything isn't the right approach either. Android removes "old" apps automatically.
Bottom line:
- just letting those apps load at startup, which you use on regular basis, is fine
- using a "ram tweaker", auto-kill app, etc. is not
Kind regards,
ww
webwude said:
That's right. On the other hand - permitting almost every app to load at startup isn't the best approach, as you will soon run out of memory - therefore using apps like autostart makes sense imho. But constantly killing everything isn't the right approach either. Android removes "old" apps automatically.
Bottom line:
- just letting those apps load at startup, which you use on regular basis, is fine
- using a "ram tweaker", auto-kill app, etc. is not
Kind regards,
ww
Click to expand...
Click to collapse
And when you run out of memory, Android will free memory by automatically killing cached (unused) apps. Therefore, I don't see the point of stopping apps from running at start--unless they're actually doing something in the background and not letting your phone sleep.
RAM tweaks (or memory management), on the other hand, is the only thing I use. I adjust OOM settings to adjust which apps Android closes to free memory, as well as how much free RAM Android should keep open in various situations.
upichie said:
And when you run out of memory, Android will free memory by automatically killing cached (unused) apps. Therefore, I don't see the point of stopping apps from running at start--unless they're actually doing something in the background and not letting your phone sleep.
RAM tweaks (or memory management), on the other hand, is the only thing I use. I adjust OOM settings to adjust which apps Android closes to free memory, as well as how much free RAM Android should keep open in various situations.
Click to expand...
Click to collapse
Well actually I don't see the point that an app, that I hardly use once per month should be loaded everytime I start the phone or change my internet connection. Also more apps at startup increase the time when the phone is available...
But on the other hand, you are certainly right, after a while, only the latest apps are still in background / memory. What I have recognized nevertheless: if you use a lot of apps with push functionality and load on startup, the phone runs out of memory...
Kind regards,
ww
hi guys,Does Quasar kernel support swap?and how to enable it?
i tried to enable it but failed
and i'm thinking about there's a lot of free space that i never used in /data and /system,so why don't we use those useless space to swap for more ram?
or we can use ZRAM?and how to use it?
we have 512 mb memory, for what you want swap?
actually the ram we can use only have less than 300mb
hmm partitionning SDC should do the job, isn't it ? do "ext" partitions have something to do with that ?
I think there's no reason to use swap, but dxdiag32's idea is not bad... internal memory is quicker than sd...
Regards.
Nah, it doesn't support it.
I did some tests with ZRAM and ZCache back in the LG P500 days and it didn't seem to help with anything so I usually disable Swap support now.
Anyway, you can always mount a tmpfs partition to some applications to boost their I/O operations if that's what you're looking for.
Huexxx said:
I think there's no reason to use swap, but dxdiag32's idea is not bad... internal memory is quicker than sd...
Click to expand...
Click to collapse
Depends on the microSD card's class. A class 10 is faster than internal memory.
In fact, it's a shame they dropped the yaffs2 filesystem as in non-sequential I/O operations it's the best one.
Class10 is faster? At least internal memory will be less energy hungry... won't be?
Huexxx said:
Class10 is faster? At least internal memory will be less energy hungry... won't be?
Click to expand...
Click to collapse
Yes, class 10 (>= 10 mb/s write speed) is faster than internal memory.
This is why moving app, data and dalvik to microSD when you have such microSD provides a good boost on I/O operations. There's many folks using the combo CM + S2E + MicroSD Class 10.
As for battery, it's a good question but I bet it should be the same. I/O stuff isn't heavy.
most of us now is using C4 sdcard,at least in China is .so i wanna give us some more performance.my free space in /data partition keep more than 800MB for a long time,and i think more ram can provide us more stable phone.
Beware that RAM works differently for Android devices.
Whereas free RAM in Windows is arguably better than occupied RAM, this is not so for Android. In Android, having RAM allocated is good which is also behind the reason of why we shouldn't use task killers. That being said, we don't really need more than 512 MB of RAM for a heapsize of 32 MB and proper OOM groupings and adj values! Even with an aggressive usage, it's unlikely you'll manage to trigger an OOM (out of memory) throughout your day.
Here's an oldie but goldie article regarding this:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
ok got it , thanks knzo
knzo said:
we shouldn't use task killers.
Click to expand...
Click to collapse
I understand the theory but because of my own experience I do not agree in 100% with You. My previous smartphone was Samsung Spica ( not much RAM ). I used to use my favourite IGO for navigation. It was impossible to succesfully launch IGO if I have not used task killer before.
Without task killer IGO just started and vanished within seconds.
pabgar said:
I understand the theory but because of my own experience I do not agree in 100% with You. My previous smartphone was Samsung Spica ( not much RAM ). I used to use my favourite IGO for navigation. It was impossible to succesfully launch IGO if I have not used task killer before.
Without task killer IGO just started and vanished within seconds.
Click to expand...
Click to collapse
That's because IGO triggered an OOM event and the ROM you had instead of doing an intelligent swipe and killing applications based on certain heuristics, was killing the process responsible for the OOM instead (IGO). It's a flag in sysctl called: OOM kill allocating task.
So in that case, it was just a lousy ROM/kernel. Or perhaps in Spica (old kernel, old android version) there wasn't this setting and the phone always killed the application that made the phone run out of memory. This explains why it vanished after a bit.
Either way I stand correct, there's no need for task killers in a device with >= 256 MB of RAM or properly configured.
knzo said:
That's because IGO triggered an OOM event and the ROM you had instead of doing an intelligent swipe and killing applications based on certain heuristics, was killing the process responsible for the OOM instead (IGO). It's a flag in sysctl called: OOM kill allocating task.
So in that case, it was just a lousy ROM/kernel. Or perhaps in Spica (old kernel, old android version) there wasn't this setting and the phone always killed the application that made the phone run out of memory. This explains why it vanished after a bit.
Either way I stand correct, there's no need for task killers in a device with >= 256 MB of RAM or properly configured.
Click to expand...
Click to collapse
Agreed. I still have my old Galaxy Apollo, with 256 MB ram it goes perfectly as it should. In fact, on a careful observation i 've noticed that if we use taskkiller at autokill level at let's say 30 minutes autokill, it will technicall consume 4 CPU cycles in an hour for each app (two for killing, and two when applications like gmail/facebook etc. starts automatically again).. but without taskkiller they may have stay idle, and not used any CPU cycle at all for as many hours as phone is idle. And for battery purpose, it is the CPU cycle that drain, not the used memory !
in my opinion,we only need to kill the apps that use internet in background to save battery.such as Google Maps,once i used it,its services stay in background and after 3 hours i didn't use phone do anything,battery drain 3%,and if i kill it,no battery drain after all
Google Maps and DRM service process sometimes cause battery drains indeed.
knzo said:
Google Maps and DRM service process sometimes cause battery drains indeed.
Click to expand...
Click to collapse
i deleted DRM service,and seems it's no harm to system
Lol but do you know what is it function ?
Sent from my LG-P970 using xda premium
I've seen drm using a lot of CPU as well from time to time. What is it used for and how would you go about removing it?
dxdiag32 said:
i deleted DRM service,and seems it's no harm to system
Click to expand...
Click to collapse
Sent from my LG-P970 using XDA App
masterthor said:
I've seen drm using a lot of CPU as well from time to time. What is it used for and how would you go about removing it?
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
You can use Titanium https://market.android.com/details?id=com.keramidas.TitaniumBackup
-Go to Backup/Restore tab
-Find by DRM Protected Content Storage
-Click and select Freeze
Now the app is Freeze and the system don't see more!
Hi there XDA,
I've been using the custom rom DjangoManouche for some time now, and it's great! But while installing i'm usually guessing the settings. If someone can clarify it, it would be great!
Note that these settings are asked of you while you install DjangoManouch custom rom.
1. Available Kernels.
When installing the KoB kernel, you can chose between several options. NoOC or OC, with or without RamHack. I know that OC stands for over clocking, but what does the RamHack do (28 / 32 mb)?
2. Dynamic Fsync (active / inactive)
I found this explanation: http://forum.xda-developers.com/showthread.php?p=33381928
If i understand this correctly it means that you have a small lag when ending calls. But when your system crashed you won't lose data.
3. Frandom Optimazations (active / inactive)
I can find no information about this on the internet..
4. Zram (active 96/128mb or inactive)
I found this explanation: http://forum.xda-developers.com/showthread.php?t=2077072
If i understand this correctly it means that ZRAM is handy for devices with not a lot of RAM. But the LG 02x has 1gb of RAM(?). Wich raises the question what good does it do?
5. RAM Management (stock RAM values / Supercharger Free Ram values / SuperCharger Balanced Ram values)
I found this explanation: http://www.technorms.com/10319/boost-performance-android-phone-supercharger
Wich explains that supercharger script boost your phones performance. But doesn't explain what the difference is between 'Free Ram values' and 'Balanced Ram values'.
6. CRT Effect (enabled / disabled)
Is this the awesome animation that shows when you power on / off your phone?
7. Fast Dormancy (enabled / disabled)
I found this explanation: http://androidforums.com/samsung-galaxy-s2-international/674208-fast-dormancy-in-nutshell.html
In short you want to enable it if your provider supports it, correct?
8. Cronjobs (active / inactive)
I can find some javascript related information, but not connected to Android. So i'm in the dark here.
As last i want to add that I'm posting these questions here because flooding the original thread with these questions is just creating noise And i'm sure there are a lot of other people with the same questions.
Thanks in advanced!
Dynamic sync is better disabled.....when enabled and issues of reboot....has a risk of data corruption.
ZRAM....96 is better....makes apps open faster......one correction-O2X has 512 and not 1GB.
Balanced RAM or free RAM.....old timers from GB will know....so maybe Carbs did not feel to state it again
Kernel ....OC is better but for rh....I prefer no ramhack
Frandom....I chose not to activate....did not find a big difference in perf
Fast dormancy.....better disabled for battery
Ramhack....is hacking and in simple words stealing what is normally for the system.....for faster performance.....but can be lagging or missing some features ....higher RH can lead to issues in Camera or other apps....so I prefer the minimum of rh and less RAM consuming background apps
I hope you can read the threads which you have posted but on experience ....I have posted what I have tested and used over quite some time on this device.
Thanks for the understanding
EDIT: forgot the cron job.....this is something Carbs first started in the O2X long back to free RAM periodically......everyday at a specified time,,,,cron script will run and clear.but you need to activate it by giving permissions
To be exact, Optimus 2x only has 384 Mb of RAM available to use for Android and apps, because 128Mb of that 512 is dedicated to the GPU. This is why many developers embed RAM hacks, because that is not much.
Since I've been using DMX I've experienced that with supercharger off, I'm always suffering from very little free memory, but many people claims (mainly Carburano), that supercharger eats much CPU even when the screen is off, that's why he doesn't suggest to use it.
LilProphet said:
To be exact, Optimus 2x only has 384 Mb of RAM available to use for Android and apps, because 128Mb of that 512 is dedicated to the GPU. This is why many developers embed RAM hacks, because that is not much.
Since I've been using DMX I've experienced that with supercharger off, I'm always suffering from very little free memory, but many people claims (mainly Carburano), that supercharger eats much CPU even when the screen is off, that's why he doesn't suggest to use it.
Click to expand...
Click to collapse
for the first part....you are absolutely right my friend.
in android.....extra or too much RAM is wasted RAM.....so generally speaking we dont need too much too....like in WIN
but, less RAM can be leading to lags and screen freezes
Ramhack can be leading to some unpleasant things sometimes.....too much of RH can also make a few apps, system apps to FC....so I always prefer to have no RH and use apps like greenify or minfree manager.....I agree with the DEV as the testings and general usage over time will show the correct results......some of us users might not see that....
SREEPRAJAY said:
Dynamic sync is better disabled.....when enabled and issues of reboot....has a risk of data corruption.
ZRAM....96 is better....makes apps open faster......one correction-O2X has 512 and not 1GB.
Balanced RAM or free RAM.....old timers from GB will know....so maybe Carbs did not feel to state it again
Kernel ....OC is better but for rh....I prefer no ramhack
Frandom....I chose not to activate....did not find a big difference in perf
Fast dormancy.....better disabled for battery
Ramhack....is hacking and in simple words stealing what is normally for the system.....for faster performance.....but can be lagging or missing some features ....higher RH can lead to issues in Camera or other apps....so I prefer the minimum of rh and less RAM consuming background apps
I hope you can read the threads which you have posted but on experience ....I have posted what I have tested and used over quite some time on this device.
Thanks for the understanding
EDIT: forgot the cron job.....this is something Carbs first started in the O2X long back to free RAM periodically......everyday at a specified time,,,,cron script will run and clear.but you need to activate it by giving permissions
Click to expand...
Click to collapse
Thanks for your reply!
It seems that cronjobs are actually really useful! But how do i give it permissions? Usually SU ask to give you permissions when the proces starts. (For example when you open Titanium Backup). But i can't manually add permissions.
LilProphet said:
To be exact, Optimus 2x only has 384 Mb of RAM available to use for Android and apps, because 128Mb of that 512 is dedicated to the GPU. This is why many developers embed RAM hacks, because that is not much.
Since I've been using DMX I've experienced that with supercharger off, I'm always suffering from very little free memory, but many people claims (mainly Carburano), that supercharger eats much CPU even when the screen is off, that's why he doesn't suggest to use it.
Click to expand...
Click to collapse
Thanks for your reply! So it means that your device is faster, but also drains your battery faster when screens is of?
SREEPRAJAY said:
for the first part....you are absolutely right my friend.
in android.....extra or too much RAM is wasted RAM.....so generally speaking we dont need too much too....like in WIN
but, less RAM can be leading to lags and screen freezes
Ramhack can be leading to some unpleasant things sometimes.....too much of RH can also make a few apps, system apps to FC....so I always prefer to have no RH and use apps like greenify or minfree manager.....I agree with the DEV as the testings and general usage over time will show the correct results......some of us users might not see that....
Click to expand...
Click to collapse
Thanks for your reply! Let;s see what Greenify can do!
I'm gonna install the new DMX 1.6.1 in a few minutes with these settings:
1. KoB Kernel with no ramhack
2. Dynamic Fsync inactive
3. Frandom Optimazations inactive
4. Zram 96mb
5. Ram Management with Supercharger Free Ram values
6. CRT Effect enabled
7. Fast dormancy disabled (For better battery life)
8. Cronjobs active
Has anyone experienced differences in performance between 'Supercharger Free Ram values' and 'SuperCharger Balanced Ram values'?
len.asdf said:
Has anyone experienced differences in performance between 'Supercharger Free Ram values' and 'SuperCharger Balanced Ram values'?
Click to expand...
Click to collapse
Not much, only the amount of free ram is more, but it doesn't effect the smoothness much imo. I had heavy lags with stock ram values on DM1.6 unfortunately, so I would have suggested you to use supercharger too. I hope you will be pleased with the settings you chose.
Sent from my LG-P990 using xda premium
LilProphet said:
Not much, only the amount of free ram is more, but it doesn't effect the smoothness much imo. I had heavy lags with stock ram values on DM1.6 unfortunately, so I would have suggested you to use supercharger too. I hope you will be pleased with the settings you chose.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Thanks for your reply! And we will find out today how smooth it goes
I've used my phone now for 2 days with these installation settings:
1. KoB Kernel with no ramhack
2. Dynamic Fsync inactive
3. Frandom Optimazations inactive
4. Zram 96mb
5. Ram Management with Supercharger Free Ram values
6. CRT Effect enabled
7. Fast dormancy disabled (For better battery life)
8. Cronjobs active
But it's far from smooth. I'm installing Greenify now to see if it changes anything..
If you Supercharged rom lag should happen. Which version are you using?
Sent from DjangoManouche!
carburano said:
If you Supercharged rom lag should happen. Which version are you using?
Sent from DjangoManouche!
Click to expand...
Click to collapse
Using DjangoManouceX 1.6.1A (the latest i believe).
But most of the lag happens when switching between apps or starting one. When an app is running, it's usually smooth.
len.asdf said:
Using DjangoManouceX 1.6.1A (the latest i believe).
But most of the lag happens when switching between apps or starting one. When an app is running, it's usually smooth.
Click to expand...
Click to collapse
Install 1.6.1 without supercharged and apply script for more free ram.
In my opinion for kernel use 1.7 KoB OC 32MB Ramhack.
mpoumpis said:
Install 1.6.1 without supercharged and apply script for more free ram.
In my opinion for kernel use 1.7 KoB OC 32MB Ramhack.
Click to expand...
Click to collapse
I will try this out on my next install! I prefere to use a install for several days so i can test it out better.
And after installing Greenify things got a lot smoother! That app is just black magic
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
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....