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
Related
can some one recomend me some volts settings and gpu setting.. after i put on the overclocking kernel my galaxy is getting hot... know i got litening rom and still getting hot... i need some setting?? the battery drain fast..???
everything is not easy there r plenty of posts on ov/oc tweaks search or find in general section....
rocky23 said:
everything is not easy there r plenty of posts on ov/oc tweaks search or find in general section....
Click to expand...
Click to collapse
OP - ^^ this. Good advice. Start with stock voltages & gradually decrease until you get to the lowest possible whilst remaining stable. As Rocky has said, there's no shortcuts (apart from the the posts on this subject on here), it's trial & error.
And the other thing, don't expect to see massive increases in battery life with undervolting. Yes, you'll get some increase over the life of a whole charge, but it won't double your battery life or anything like that. So far as the heat issue is concerned, of course your phone is going to get hot if you overclock.
The phone is only made to go to 1200mhz out of the box. If you want to overclock, heat is something you're going to have to learn to live with; tho undervolting might reduce the heat produced by overclocking a little bit.
Overclocking is the same as undervolting in that some CPU's can handle more or less than others. Your phone might be able to handle 1600mhz just fine whereas the CPU in mine might only be able to handle 1400mhz. Same with undervolting, stable values for me might cause your phone to crash.
adding to the above you could also check this thread:
http://forum.xda-developers.com/showthread.php?t=1572538
made by ArchenzeEL
Its an EXCELLENT thread to start with as there is quite some information as well as sample values for you to play with. Keep in mind that those values might not work with you but you can experiment a bit in order to find the values most suited to your phone.
Also i think you should take a look in this thread
http://forum.xda-developers.com/showthread.php?t=1369817
its a LONG LONG read but it will help you in the end understand how overclocking/undervolting works in general...
I have the the international version of S3, i9300. I don't think quad core is that much of an advantage for basic operations, was thinking if disabling the other two cores would help in power saving?
Im on CM10.1 with siyah kernel 1.91 by the way.
yes
It definitely would, but there are better ways to save battery on your phone that offers more battery life with almost unnoticeable difference in performance.
If you haven't already I would recommend using Greenify, Betterbatterystats, underclock CPU slightly - check out the General thread for more information and tips.
Oh and if you're sorta a geek like me, you could try Perseus kernel and tweaking the settings for it; it has a lot of options which I'm sure will be useful in conserving power, which is what you seem like you want to do.
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.
Hello folks!
This thread is intended for sharing, please be kind. Any suggestions would be appreciated
A few days ago I was tired of having my Mi3 running on stock global dev MIUI 8, it was inefficient system with really bad memory management. On my experience, the MIUI tend to run out of memory. In some case, after a few hours of usage the system cannot reclaim the occupied RAM, thus making the system lags a lot and generate excessive heat!
Yes, MIUI is a feature-rich ROM, and the Mi ecosystem is a pretty mature ecosystem. However, those all greatness needs a lot of power to run on our 3 year old device. After a few research I decided to switch to CM13 ROM.
With efficiency in mind, I do my research and tinkering with my device to get the best setup possible without losing performance. The results are AMAZING! I can use my phone for a whole day without recharge in the mid day. All of this with huge improvement on performance, Real Racing 3 highest graphic setting without any noticeable lag! CPU and battery temperature are now significantly lower (43-47C idle / light tasks, 55-57C heavy gaming). Now that I've found the best setup, I want to share it with you folks! Here we go:
Mi3W 64GB
CM13 ROM snapshot build
CM kernel (automatically flashed while flashing CM13 zip through TWRP)
Screen resolution changed to 720x1280 use this guide
Modded interactive CPU governor (see screenshot below)
Undervolt (see screenshot below, this one really helps reduce CPU working temperature)
Noop I/O scheduler
Reduce aggresiveness of LMK (see screenshot below)
Thats all folks, hope this guide will get our Mi3 having another year of flagship-grade experience! Cheers! :highfive:
How did u undervolt
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
Yes, it depends on the kernel used. Some kernel support undervolting while others don't. You need to flash kernel that support undervolt.
solazz said:
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
Click to expand...
Click to collapse
While testing CPU voltage value, don't tick "apply on boot" option until you find the most stable voltage without causing system reboot or crashes. Every CPU has different limit on how far you can undervolt, but you can use the values on my screenshot as guidance (Snapdragon 801 / MSM8974-AB only)
Wow!! Thanks a lot bro. I'll fiddle now with my phone.
miui8polska，i cant root it .can you give me a supersu.zip?
Sent from my MI 4LTE using XDA Labs
Random reboot after setting undervolt just likes yours
z1d4n21 said:
Random reboot after setting undervolt just likes yours
Click to expand...
Click to collapse
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
rxl.noir said:
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
Click to expand...
Click to collapse
Ok thanks i will test it later
Hey there, android enthusiasts!
Hopefully this post will gather many experienced users and solve these problems and doubts once and for all.
I've searched pretty much everywhere on google and the usual material showed up, copied and pasted around the web.
So I'm posting here, hoping that developers and hackers come and share their precious knowledge, producing new material that will put light in this often misunderstood field.
1) What does vfs_cache_pressure do? How does it interact with RAM and Swappiness?
2) What happens when I have Z-Ram enabled and Swappiness set at 0?
3) Are the init.d tweaks by franco's developers team still good for Nougat and Oreo? I understand these guys know what they do and put a good amount of effort in finding the best settings, however maybe they were wrong, or they intended to engineer them for a different kind of usage (I'm thinking about the perennial debate between Performance, Balanced, and Multitasking).
The VM tweak sets Swappiness at 0. Is this stupid if I have z-ram on because that z-ram will never be used?
4) That also tweaks vfs_cache_pressure at 100. Why not using lower values of vfs_cache_pressure like 50, or even 30 or 10? These all raise perceived performance and overall fluidity, at the expense of real performance. Even though this seems counterintuitive, one only needs to try these settings to be convinced of their value in overall fluidity and smoothness (to know more about that, see Tales from Responsivenessland by Rudd-o, and also Imoseyon's Sysctl tweaking for faster, longer lasting Android)
5) What about dirty_ratio and dirty_background_ratio? Why values of 20 and 5 respectively? What happens if we set them at, say, 90 and 55? How do they interact with swappiness and vfs_cache_pressure? I remember reading somewhere that setting them high would delay writes and save battery, but at what price?
6) How do dirty_background_ratio, dirty_ratio, swappiness and vfs_cache_pressure all interact with low memory killer values?
7) Not related: What does the Arch Power option do, exactly? Why is it good/bad for x or y?
8) What is RQ Affinity and how should I set it and why?
No one?
I've been looking for answers to some of these same questions. I know Google is my friend but when i search for what feels like forever and only find more questions, it gets frustrating. So like the OP said.....NO ONE?
Shameless bumb, we need answers
Nolfer said:
Shameless bumb, we need answers
Click to expand...
Click to collapse
Sorry for the necro.. but in May 2019 I wrote this and this on Telegra.ph in this subject, hope it still helps and you are still interested.