i use MiniCM7 v5
my phone isnt really fast although i oc'ed to 710mhz. so i want to ask u which are the best performance settings (in settings-cyanogenmod).
vmheap, dithering on/off, cache on sd, ... and every option which is available
thx for reply
i've set my cache size to 3072 cause that personally gives me best readings, but I don't know if that's a general thing or dependant on the sd card you're using.
my VM heap is at 24M cause that's prolly more than enough memory for any app i have installed to run properly
clock speed is a personal thing, so best to fidle around with that and see what u like
higher speeds = faster, but more battery drain
lower speeds = slower but less battery drain
Related
Dj steve said the rom was over 3000 quadrant I only get 1750 what did I do wrong
Sent from my Dell Streak using Tapatalk
There are a lot of factors that make up that high of score. I could be wrong, but any additional apps that are installed slow down the score. Background apps running, type of installation, speed of internal SD card, speed of CPU. I am sure that there are other tweaks that will come down the road, or maybe not (a Developer has to keep some secrets to himself). I myself get anywhere from 2000-2500 on average. Keep in mind that the base install of Dell's 1.6 only gets about 800, so anything over that is a bonus. You are getting double that of a new Streak out of the box. As more Roms come out, the better and faster you can customize it to your liking.
1. Install setcpu app
2. overclock to 1.26ghz
3. change from on demand to performance
4. Turn off wifi, blutooth and 3G radio
5. Uninstall any apps you don't use
6. set your LCD density to 240
7. free up as much memory as possible by shutting down memory hogs like gmail and browser
8. don't clear cache.
Do all of these things and you will be humming at 2500+ in no time. I gaurantee you that steve got 3000 on a base system with absolutely nothing running and has a quick processor... all processors are not created equal. Some are fast and some are average
Which Rom offers the best battery life??
Villain , Coderom , KPE or KPH ????
U have to try what suits u best depends on ur usage , KPH is working good for me.
CODE ROM - IMO.
I have an explanation - a2sd - just one more battery safer, because more data on sd - less CPU using.
Why needs aps on the sd card less cpu?
number of calls to the phone is reduced, due to the speed of the memory card.
So, less calls to the phone - less battery we use.
And, on my expirence, i advised to use SetCPU and Autostarts, to control you cellphone processor and control your apps
Profiles of SetCPU i gives in near topic - here post.
KPH is giving me excellent battery life... my ace last almost 36 hours now with constant sync of 3 mails.
Without data connections, it lasted me a bit more than 3 days
Running build 11 of team hacksungs cm9 ics port. My current governor is on demand with a minimum of 400 and maximum of 1000. There are numerous memory settings in the cm9 settings such as how many background processes run. I wouldn't call myself a power user but I do use my phone for apps and internet throughout the day.
Sent from my SCH-I500 using XDA
I use sio and glitch/smartassv2.
There is never really a "best" selection for these types of setups. They are relevant to how you want your phone to operate. Some choose for performance versus battery. You have to pick what is most important to you but the question may be better phrased if you have stability issues.
I run AOPK ROM but I have always chose performance governor with min and max set to 1200MHz. For memory, the Droidstyle guide I believe references keeping 100mb free.
That combination has worked good enough to prevent lag/delay but provide additional response time for my phone. Battery is decent with moderate use but watch the battery temp. The stock battery is only 1500mA so that is one of the limiting factors.
So, using extweaks I see that theres a zram setting thats default is off. I have a couple questions about it. To my understanding, enabling it adds more usable ram for the android system, but it uses cpu to compress it right? So does this mean that it uses more battery life as well? or by adding more ram, will it save battery life because its not having to reorganize system resources all the time. I don't quite understand how it works.
someone enlighten me. My main question is, does it negatively or positively impact battery performance.
thanks
I don't know much about how it works, but I can tell you when I tried to use it it slowed down my system. No positive effects noticed.
aspen1135 said:
So, using extweaks I see that theres a zram setting thats default is off. I have a couple questions about it. To my understanding, enabling it adds more usable ram for the android system, but it uses cpu to compress it right? So does this mean that it uses more battery life as well? or by adding more ram, will it save battery life because its not having to reorganize system resources all the time. I don't quite understand how it works.
someone enlighten me. My main question is, does it negatively or positively impact battery performance.
thanks
Click to expand...
Click to collapse
More cpu work load = more battery drain , so yes theoretically zram will decrease your battery life but i don't have numbers to prove it . Also your kernel must support zram to use it . I haven't seen a huge performance increase or the like enabling it but multitasking seems more smooth or so it feels to me .
leap before you think
Our device isn't considered to be powerful anymore. It's became an complete underdog. Thanks to Android's flexibility, you can force to make your phone pretty much fly with several tweaks.
1. Delete as much bloatware as possible.
This is regarded as an easiest, noobiest option to improve your phone's performance. Many OEM apps stays hibernated in the RAM, thus limiting free RAM available to the user and sometimes even stressing NAND too much. In the end, it's the best to keep your phone as clean and deleting useless apps on the fly.
2. Don't install too much apps into NAND memory
Benchmarks shown, that our phone's NAND chip is considered to be rather slow. Since many apps access small amounts of random data pretty much constantly, it's better to have less apps installed on your phone.
3. Avoid using app killers
This is a placebo effect, since Android's memory management is inferior to what app killers are doing. Many apps stays in such state, where they are ready to be launched almost instantly. App killers, however, pretty much screw all the mandatory functions and stresses the phone even more than before. Launcher redraws are rather common occasion when app killer is being used.
4. Use custom kernel
Custom kernels often offer more features and are more optimized to make the use of available hardware. OEMs never seem to mess around with kernels much, since they want to have their product as stable as possible. Devs, however, mess around with kernels and extract almost double the real-time performance.
5. Never fill up your storage completely
The more data is available on the storage, the harder is getting to find it. Since data is laid randomly, it searches for the information location. When there are too much data, it gets harder to find the data needed. Often slower cards, like Class 2 or Class 4, are considered to be the better choice, since those cards are much faster at writing and reading marginal data randomly.
6. Select the I/O scheduler, CPU governor wisely
These things manipulate with the main hardware. The better optimized the governors are, the better the phone will run and won't drain the battery as much. Though keep in mind, that many governors have their own drawbacks.
sioplus is one of the better I/O schedulers. It allows access to random data pretty quickly, which ensures smooth and snappy performance in the system.
ondemand is the most common and is the stapple and the base of many custom governors available today. It's method is pretty simple - whenever phone registers a touch input, it automatically raises the CPU speed to the max. In retrospect, it should give great performance, but it usually suffers from poor response.
7. Play around with Dalvik VM settings
My optimized settings (feel free to use them):
dalvik.vm.heapstartsize=6m (size when first launched)
dalvik.vm.heapgrowthlimit=64m (limit of standard app)
dalvik.vm.heapsize=192m (heap for large app)
These settings pretty much controls our multitasking. Each phone has it's own specified settings, so it could run better.
Lowering these settings could majorly improve performance, but it could slow down around, when there too much heavy apps running in the background.
Raising these settings could improve multitasking, since less CPU power is required to extract certain data to the RAM. Scrolling a heavy webpage, for instance - raising these settings could improve scrolling smoothness and loading times, since there isn't a need to clean the heapsize as frequently as it was before.
More suggestions are coming later. If you found this article useful, please leave THANKS!
Good day.