Related
Ok I'm kinda new to the whole overclocking thing and I was wondering what are the best settings to use if I wanted to(for instance) save more of my battery. I've done quite a bit of searching but I wanted to make sure that the voltage settings aren't different on different ROMS or phones. I'm on Zeus V3 for the record. Any help would be greatly appreciated! Thanks for your time.
Stable settings definitely vary from phone to phone unfortunately, even if they are the same device. So basically its trial and error, no matter what anybody suggests. Generally, the more you can undervolt and stay stable, the better battery life you will have. You're just going to have to experiment a bit, and just make sure you don't save any settings as boot settings until you know they are stable. I know there is a guide to overclocking somewhere on the forums, I just hate searching on my phone.
Quick tips, start with only moderate undervolting, and crank them down gradually until your phone is at the limit of stable to maximize battery life. Use the 'stability test' app in the market to test for stability. Also, running other benchmarks, such as neocore or quadrant, without freezing is a good test.
Hope I helped!
PS, I've come to the realization that it all doesn't make THAT huge of a difference, and if you switch roms anywhere as frequently as me, its a waste of time. Not to discourage you, just my two cents. If you like to pick a rom and stick with it, then definitely play with it.
*edit* Got on my computer and found the guide for you:
http://forum.xda-developers.com/showthread.php?t=1036020
Obviously, since the guide is based on a captivate, the values you will end up with will be different, but he explains the process of fine tuning very well. Enjoy!
Sent from my SGH-I997 using xda premium
what i do with all my ROMs is put it from 100 mhz (min) - 1600 mhz (max)
and put the governor to "ondemand"
i usually get about 18 hours on battery life a day.
give it a shot doesnt hurt to test it out cause you could always charge your battery haha
This thread shows the results of some benchmarks of the Android OS (using a Nexus S) where certain parameters affecting performance have been isolated to the greatest extent and then compared statistically.
Background
I teach mathematics, and also used to be a professional sound engineer.
Some of my work on measuring battery drain was published on the XDA portal here however since then further studies were conducted, revealing critical flaws in my original test setup.
Although I believe some of my finding may be generalised to other devices, please bear in mind that my device is a Nexus S, and has its own peculiarities. I have attempted to edit out findings which I believe may be specific to the Nexus S, but I have linked to the original thread in case you wish to go exploring further results, or get an overview of my methodologies, which are usually in the second post.
Please feel free to post or PM with any queries, and I am more than happy to help if you want to apply my techniques to your own device.
Results
Over my time here in XDA I've built up a few studies on the Nexus S.
Here are the links. There are summaries in each thread in the first and second (and sometimes third) posts of the main findings, but I've done some very quick and minimal overviews here also.
ICS ROM Benchmarks: this thread
-Freely available benchmark programs were used to determine which ROMs had the best performance. Among the top six were an AOSP ROM with some CM9 parts, MIUI, and Stock, all within about 1% of each other. My conclusion was that the gingerbread tweaks we all knew and loved didn't improve performance with ICS, and in some cases, enthusiastic young developers were throwing together incompatible tweaks that hurt performance.
Battery Drain Benchmarks: this thread
#1 - With screen on, the slowest processor step saves the most power (duh... )
#2 - Regardless of your choice of governor, even with extreme undervolting, you are not going to be able to increase your battery life by more than 2%. (Click here for explanation.)
For the instability introduced by UV, it seems a 2% increase in battery life isn't really worth it! REMEMBER rebooting uses so much power, a single one would more than undo any savings made by UV.
Also, undervolting seems to cause more reboots when the battery is running low. This makes sense, as the battery runs low it loses some of its voltage (which shouldn't be confused with remaining power capacity).
#4 - This is one point that everyone ought to know, but I'm including because many people seem to believe in myths: if the screen is off, and the CPU is not active, neither deep idle nor UV will have any impact on battery life.
#6 - If you have an amoled display, black saves a great deal of power. After that, red. If you have a black and red theme, this is saving you power!
#9 - For amoled displays, Kernels higher FPS mods will cause the screen to drain about more power. For instance, on the Nexus S, 65 fps drained 10% more power than 56 fps. Also, 50 fps saved about 7% power compared to 56 fps.
#11 - If you've got no reception, you might as well be in airplane mode, because searching for reception also eats battery.
#12 - If your phone can't handle OC (or UV for that matter) it's because components in general are built to cost, which means factoring in tolerances, and every chip is made as cheaply as possible within the specified tolerances. Outside of those tolerances, whether your chip can cope or not is unfortunately down to the whether you got lucky with the individual device that dropped off the manufacturing line.
ARM document on A8 fault tolerance: http://infocenter.arm.com/help/index.../Babhjhag.html
In fact I measured how UV in particular can cause errors, and saw in action the A8 using MORE power to correct the errors.
CPU Governors and I/O Schedulers: this thread
-Interestingly, CFQ generally performs very well, and deadline. Most custom kernel developers in the Nexus S section recommend a version of deadline that has been tweaked for flash storage. In one of my unpublished benchmarks deadline performed slightly better than CFQ.
Does SuperCharging work?: this thread
-This was just a short study to find out if this script is suitable for the Nexus S, but it turned out it had no effect, positive or negative. This script was probably more use on devices that had less memory. One benefit that remains is to 'bulletproof' the launcher.
Kernel Memory Allocators: this thread
-This is another short study for kernel developers to show that SLUB performs best.
This is my first Android phone (2nd device overall), I love it, it was my free upgrade option from AT&T, on number 2, the first, I completely bricked trying to upgrade to GB stock..... After I got the taste of flashing ROM's, thanks to TRusselo and his ninja skill, I find myself oriented towards the leaner ones because of memory issues, I run V6 Supercharger , SlimICS :victory:, with JRummy's ROM Toolbox Pro :good: (gotta support the kicka$$ apps), TB, blah blah blah.
My major complaint is that my Cap runs hot, I have OS Monitor on it because I got tired of not knowing the threshold. It bothers me that my phone gets over 110 degrees Fahrenheit , I've even had a brief history of random reboots I attribute to heat when I ran the ICSSGS 4.0.3 ROM (Awesome stuff, but once I bit into Slim, it was over). Is there a way to manage the heat or get a case for the phone that helps to manage the temperature? Or am I S.O.L unless I keep a frozen gel pack nearby?
BTW, first post, I surf the posts often and since I didn't see any questions about overheating for this particular Samsung model thought I'd give this a shot
My gets hot to I think it has to do with the kernel
Sent from my SGH-I897 using xda app-developers app
Mine runs really hot too, mine gf has a cappy and they run the same everything most of the time, but mine is the only one that gets stupid hot. Would love it to be fixed but I think its probably a manufacturing issue. Problem is it wears on the battery. 10-20 of use and you will burn your ear if you want to talk on the phone . The metal back certainly doesn't help either.
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
takeoutttt said:
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
Click to expand...
Click to collapse
I have the max set at 1Ghz, min 600Mhz, Performance, SIO, I'm sure the fact that the temperature outside being over 100 F doesn't help at al. I have overclocked it before and it started smoldering, not literally, just felt like it.
I've literally taken damp cloth's and set them underneath the phone on occasion to see if that will help, it definitely does, so does setting the gel ice pack under it, so I have found ways around it. I would probably only trade this phone for one of the S3's, but this phone has definitely earned the top place among my favorite devices all time. It's just as tough as a Blackberry, and easier to use than an iPhone.
That's why LOL, 600MHz minimum and 1000MHz max, with performance gov, that keeps it at max clock all the time XD take that off OMG...
b-eock said:
That's why LOL, 600MHz minimum and 1000MHz max, with performance gov, that keeps it at max clock all the time XD take that off OMG...
Click to expand...
Click to collapse
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
takeoutttt said:
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
Click to expand...
Click to collapse
I have never knowingly oc my phone, it would get hot on GB even before I rooted and went to cm. 10-20 mins of web browsing brings my temps up to about 41 C (106 f) I am pretty new to this, where to I check my clock settings?
I'm running helly bean nightly s
I have switched batteries with my gf cappy so I'm pretty sure its not a battery issue
Maybe a bad/defective battery is the cause of the problem since there is no overclockin...???
Sent from my SAMSUNG-SGH-I777 using xda premium
master2828 said:
I have never knowingly oc my phone, it would get hot on GB even before I rooted and went to cm. 10-20 mins of web browsing brings my temps up to about 41 C (106 f) I am pretty new to this, where to I check my clock settings?
I'm running helly bean nightly s
I have switched batteries with my gf cappy so I'm pretty sure its not a battery issue
Click to expand...
Click to collapse
With a metal back of cappy, it will easily heat up because it conducts heat in the metal. Based on my experience it is cause by the user usage depending on how high is the voltage/clock require of each app used to maintain it's smoothness and reached it's maximum clock. You can see your usage at Settings>Battery.
You can use CPU Spy or Voltage Control to see your OC and adjust it. You can check also in Settings> Performance >Processor.
---------- Post added at 02:36 AM ---------- Previous post was at 02:28 AM ----------
brttwilliams said:
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
Click to expand...
Click to collapse
Yeah, you'll learn in time, just try to search and read throughout the forums. I suggest that you lower your min to 100/200 and max to 1000/1200,
use smartassv2 and sio governor. This settings saves me some battery and to extent that still smooth, slick and good ui/gaming/app performance.
If you're on DEVIL KERNEL, go to recovery>devil>governor profile> tick SMOOTH.
brttwilliams said:
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
Click to expand...
Click to collapse
Wasn't doggin' you dude, Just letting you know that could be the cause of your problem. Awhile ago I might have flamed you, I have matured and get that not everyone reads (not this situation), and I have to get used to that. People make mistakes, I know I do even if I wanna act like I don't. I am just helping around here now since I have gotten as much knowledge as the some of the users that joined XDA and other hacking forums in the beginning because I was always searching to find out ways to do it on my own, asking for help with stuff that no one talked about. So I am glad that I was able to help you in a way, sorta.
b-eock said:
Wasn't doggin' you dude, Just letting you know that could be the cause of your problem. Awhile ago I might have flamed you, I have matured and get that not everyone reads (not this situation), and I have to get used to that. People make mistakes, I know I do even if I wanna act like I don't. I am just helping around here now since I have gotten as much knowledge as the some of the users that joined XDA and other hacking forums in the beginning because I was always searching to find out ways to do it on my own, asking for help with stuff that no one talked about. So I am glad that I was able to help you in a way, sorta.
Click to expand...
Click to collapse
Thank you both, b and takeout.... I know neither of you were doggin me, b-eock. I've been one of the behind the scenes types but I've seen a few of your posts, I know you know what you're talking about, I definitely appreciate the guidance. Truth be told, I know I'm still a nub here, but I know my way well enough, after you break something a few times, its only natural to pick up a few tricks along the way.
Yeah you'll learn something here just have the patience, experiment, test things out yourself to conclude and rather soon it'll be your hobby reading
And also help others out too.
Sent from my SGH-I897 using xda premium
my gets hot sometimes too. im on helly bean latest 08/08/12 version, also battery gets sucked down quick, barely get 8 hrs and i do virtually nothing. ics cm9 was great on battery.
VashTS said:
my gets hot sometimes too. im on helly bean latest 08/08/12 version, also battery gets sucked down quick, barely get 8 hrs and i do virtually nothing. ics cm9 was great on battery.
Click to expand...
Click to collapse
I know my battery is going quick on the SlimBean 2.0 ROM, but the heat issue still happens, I have noticed with my OS monitoring tool that it gets hotter if you have programs running constantly in background using up high CPU %. I was able to isolate a few of the programs as things I could remove, overall it does still run hot, but it's not as bad.
I use the free version of the OS Monitor on Play Store, you can set it to run under root and to autostart when the device is turned on.
Picked up an 1800 mah battery and my batty life is great! Going to bed with 40ish percent left
Haha, well let me know where you snagged that from
Sent from my SGH-I897 using xda premium
try Smartassv2 gov and change your min from 600 to 100, then note the temps, or run a log of them.
typically my phone runs about 35° C (95° F) and that is with an otterbox commuter case on the phone. When the gps is on in the car, I use a vent mount to keep it at 40° or less, and never have to take the case off.
I read that higher temps, example 45°, really shorten battery life, and you wiil only get 200 charge cycles instead of 500 from the battery.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
brttwilliams said:
Haha, well let me know where you snagged that from
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Amazon, was a great purchase, got an oem battery, there is a huge thread in the accessories section about the 1800 mah epic 4G battery that fits in the cappy
Hi
A friend of mine is endlessly complaining about the bad battery life on his stock nexus 5, the phone is off the charger at 7am and is all but dead at 4pm
Being a nice guy and all, I want to help him out by offering to install a ROM that optimises battery life.
Can anyone suggest a good rom for the task ?
If such a rom exists and battery life can be extended to 15 to 17hrs I might jump ship from my LG G3
None
roms have absolutely nothing to do with battery.
battery is determined by your personal use, your personal setup, apps installed, and very much the quality of your phone/data connection. there are other things that'll influence battery life slightly as well, but these are the main things that determine your battery life.
Turn off auto and set the screen brightness display to 15%!
galaxys said:
Turn off auto and set the screen brightness display to 15%!
Click to expand...
Click to collapse
Autobrightness isn't too bad if your ROM allows you to change the values/levels
Also, "Lux Autobrightness" is useless for saving battery on an LCD screen since the backlight is still the same brightness. on AMOLED (aka not the Nexus 5) it would help, however.
simms22 said:
roms have absolutely nothing to do with battery.
battery is determined by your personal use, your personal setup, apps installed, and very much the quality of your phone/data connection. there are other things that'll influence battery life slightly as well, but these are the main things that determine your battery life.
Click to expand...
Click to collapse
so we shouldn't expect any battery improvements when Android L is released ?
ipguy said:
so we shouldn't expect any battery improvements when Android L is released ?
Click to expand...
Click to collapse
its possible, a small amount. but that would be from new code that makes something more efficient. but, i personally, dont expect much difference in battery life.
simms22 said:
its possible, a small amount. but that would be from new code that makes something more efficient. but, i personally, dont expect much difference in battery life.
Click to expand...
Click to collapse
not sure I agree with you, project volta looks like a concerted effort from Google to do exactly that.
Funny. I always use Auto-brightness and get 4 hours SoT at least twice a week. Other times, I get a little over 3 hours or below.
The best battery life for me is with elementalx 1.05 kernel with a stock rom. 2 days stand by and at least 5 hours sot is the usual verdict.
But i think the problem here is how your friend uses his phone
Different ROMs do have different battery usage. Even with the same kernel. He could stick on stock with elementalx aosp kernel. Then mess around with trickster mod to suck out the most use. Only use the high power goveners when needed. Then switch back to low power for general use. Honestly, had my n5 for a month. Also had a n4 before. The n5 battery isnt much better. Biggest downside. Just doing nothing its fine, but if I play some games on the train it dies in no time.
Some ideas
Vanir
Slim
Purity
Cm11
Vanir with elementalx was good for me battery wise. But after a certain nightly I was getting alot of heat and battery drain. Im now using sabermod carbon with elementalx.
Turn Location off. It has the biggest Impact in Battery life time.
"Best" ROM.
There is no such thing as a best ROM. The question itself is ambiguous. "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are you running on your Nexus 5 thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded. You will likely be able to read about this in the ROM threads. ROMs do not impact battery life. The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
Also, please note that as above, "best" is still subjective. What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life. Let's get this cleared up. Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life". This is actually wrong. Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning. The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings. This is what we refer to as out-of-the-box settings. The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance. The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
rootSU said:
"Best" ROM.
There is no such thing as a best ROM. The question itself is ambiguous. "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are you running on your Nexus 5 thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded. You will likely be able to read about this in the ROM threads. ROMs do not impact battery life. The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
Also, please note that as above, "best" is still subjective. What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life. Let's get this cleared up. Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life". This is actually wrong. Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning. The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings. This is what we refer to as out-of-the-box settings. The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance. The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
Click to expand...
Click to collapse
with this guy
I used about every rom and kernel.... And my battery life for me, with my lean setup and usage was always 24 hoursish total and usually over 6 hours screen time on all of them.
So no one will ever convince me that different kernels and especially different roms affect battery life any more than in the smallest ways. Definitely not enough difference to base a choice on solely.
?
rootSU said:
"Best" ROM.
There is no such thing as a best ROM. The question itself is ambiguous. "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are you running on your Nexus 5 thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded. You will likely be able to read about this in the ROM threads. ROMs do not impact battery life. The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
Also, please note that as above, "best" is still subjective. What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life. Let's get this cleared up. Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life". This is actually wrong. Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning. The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings. This is what we refer to as out-of-the-box settings. The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance. The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
Click to expand...
Click to collapse
Well said. I hope you don't mind but I've linked your well written response in a Reddit post. Users there argue daily over which ROM or kernel is best for battery life despite my best efforts.
bblzd said:
Well said. I hope you don't mind but I've linked your well written response in a Reddit post. Users there argue daily over which ROM or kernel is best for battery life despite my best efforts.
Click to expand...
Click to collapse
You can lead a horse to water.... Etc... Etc. ?
bblzd said:
Well said. I hope you don't mind but I've linked your well written response in a Reddit post. Users there argue daily over which ROM or kernel is best for battery life despite my best efforts.
Click to expand...
Click to collapse
Not at all. I'm just copying and pasting it wherever needed now.
Sent from my Nexus 5 using Tapatalk
ipguy said:
not sure I agree with you, project volta looks like a concerted effort from Google to do exactly that.
Click to expand...
Click to collapse
we will see.
This thread is intended to have power users post their best configurations so as to guide the rookies in optimizing their MXPs once they get unlocked and rooted. It's also intended to compare the best setups for battery, performance, gaming, multitasking, etc.
My main interest is in battery life, although lately I've been on the XDA Labs app like crazy and it's hurting my drain.
Constructive criticism welcome on how to improve the below records!
ROM: Stock MM Canadian
Kernel: Ultra Kernel R3
Governor: Smartmax
Frequencies: 200 big, 800 little
Xposed Framework modules: Force Fast Scroll, Lucky Patcher, GravityBox (duh!), Use USB For Marshmallow, Xposed GEL Settings
Best SOT: 8 hours
Best Drain (100% to 0%): 120 hours
Other miscellaneous tweaks: Shake Flashlight as a system app instead of double-chop (works great, just don't let go)
Launcher: Still figuring that out...but Nova and DarkLauncher are worthy contenders right at the moment
Voice Assist/Google Now on long-press Home: Disabled thanks to @pijes. Settings > Apps > Gear icon > Default Apps > Voice and Assist > None
Post below, power users! What's your best setup so far?
Bro, I would like you use Greenify and DS Battery saver
As you have xposed framework installed you can use boost mode in greenify and also
DS Battery saver also has a module so activate them and then choose slumberer and phew see your battery stats
Coming to launcher, right now Arrow launcher is good and smooth and I prefer that
Thank you!
ashwath230 said:
Bro, I would like you use Greenify and DS Battery saver
As you have xposed framework installed you can use boost mode in greenify and also
DS Battery saver also has a module so activate them and then choose slumberer and phew see your battery stats
Coming to launcher, right now Arrow launcher is good and smooth and I prefer that
Thank you!
Click to expand...
Click to collapse
Cool man thanks. I'll try the Greenify and DS you recommend. I've seen Greenify a lot around XDA. I'm excited to try it.
Tesla rom(seems faster/smoother then stock/anyother rom) plus Squid kernel. Governor is set to Lionfish and I/O scheduler is set to Row with 512kb readahead. Minimum frequency for the Big cluster is 800mhz and 499mhz for the little cluster. NFC and location disabled. Best battery life I ever got was with stock with the same kernel/settings configuration, had 9 hrs SOT and nearly 24 hrs overall.
xtremeed2705 said:
Tesla rom(seems faster/smoother then stock/anyother rom) plus Squid kernel. Governor is set to Lionfish and I/O scheduler is set to Row with 512kb readahead. Minimum frequency for the Big cluster is 800mhz and 499mhz for the little cluster. NFC and location disabled. Best battery life I ever got was with stock with the same kernel/settings configuration, had 9 hrs SOT and nearly 24 hrs overall.
Click to expand...
Click to collapse
What do you mean nearly 24 hours overall - how long before you had to recharge?
I need to learn more about I/O scheduling. I've changed to Row and 512 as you recommend but where will I see the difference? When I connect to my PC? When apps access internal storage?
I've changed my governor back to lionfish. Smartmax wasn't doing it for me. 200 big 800 little. I'll look into that Tesla ROM too.
I was hoping this thread was gonna be more popular. I hope some people have gotten use out of it so far! Grow little thread, grow!
It would be awesome to see more growth in this thread! It would enable prospective buyers to talk to current owners, and figure out what they might want before they sink money into the device!
*cough*cough*
Which is exactly what I was hoping to do! Does anyone know if sweep to wake/sleep is possible with the Moto X Play? It's honestly one of the most useful features I've ever seen from rooting et al.
I'll post my setup. Been using it this way for like 2 weeks so I feel it's stable.
I'm currently running this:
Unlocked BL obviously
Stock Canada firmware (MPD24.65-18)
Rooted
Xposed Framework installed
Squid Kernel r14b
I have gravity box installed and that's really it as far as tweaks and stuff.
Averaging 5 or 6 hours SOT down to about 25% or 30%. Really depends on what I do and what network I use. Performance is great too.
I'm gonna mess around with some of this stuff tonight and see what I can do with it.
Sent from my XT1563 using Tapatalk
I'm trying the interactive governor in Squids kernel, some of the stuttering issues have disappeared. Like when I clear all recents in the task switcher screen or scrolling big web pages.
Sent from my XT1563 using Tapatalk
Marshmalux. Rooted. Xposed. Greenify. Powernap. Amplify.
Getting sot around 5.5 hours for my usage. Happy with that squid kernel latest r15. Lionfish on both cores
Sent from my XT1563 using Tapatalk
JohnHorus said:
It would be awesome to see more growth in this thread! It would enable prospective buyers to talk to current owners, and figure out what they might want before they sink money into the device!
*cough*cough*
Which is exactly what I was hoping to do! Does anyone know if sweep to wake/sleep is possible with the Moto X Play? It's honestly one of the most useful features I've ever seen from rooting et al.
Click to expand...
Click to collapse
Hey hey. Thanks for posting!
I'm sure sweep to wake is possible on the phone in some way, likely through a combination of rooting and Xposed modules. I know that GravityBox has a double tap on status bar to sleep feature.
One of the nicest features of the X Play is the Moto Display. It's nice to have the phone screen come.on showing notifications without fully waking the phone. Check out the Moto Display app on the Play Store. It's a totally sexy feature.
I'd say this phone is absolutely worth it for the battery alone. I personally feel the camera to be laggy especially with focus, so consider that if you're a shutterbug. I am very hopeful that software updates will being out the power of the camera but it doesn't have optical image stabilization so blir happens more frequently, at least for me. That could be my shake fingers though.
Feel free to ask any further questions!
brian10161 said:
I'm trying the interactive governor in Squids kernel, some of the stuttering issues have disappeared. Like when I clear all recents in the task switcher screen or scrolling big web pages.
Sent from my XT1563 using Tapatalk
Click to expand...
Click to collapse
Good stuff. Interactive does appear to handle web pages better. I did a Wikipedia search for The Simpsons and got a huge page. I flicked down to scroll it all at once and then Chrome froze. Hahahaba. Same with Lionfish though. Maybe I'm getting greedy thinking this phone is as powerful as my PC.
Lionfish was giving me great SOT results. Like I mentored in the OP: 8 HOURS! Was so happy to see that. Blew the socks off my Nrxus 4. I average between 6.5 and 8 usually, but WhatsApp and XDA Labs are hurting those scores now.
I haven't had to Greenify any apps yet - I only hsvr geeky ones installed anyway so they never keep the phone awake.
Gopinath15 said:
Marshmalux. Rooted. Xposed. Greenify. Powernap. Amplify.
Getting sot around 5.5 hours for my usage. Happy with that squid kernel latest r15. Lionfish on both cores
Sent from my XT1563 using Tapatalk
Click to expand...
Click to collapse
I think @squid2 deserves a lot of credit for extending the X Play even further. His kernel and work on TWRP make the X Play even more attractive than it is out of the box.
I prefer Ultra kernel personally because I believe the dev for that (@technoander) takes the latest releases of squid's and adds features to them. I may be mistaken but that's my impression. I'll try to clarify and report back. I should do a direct comparison of Ultra and squid's latest to be as objective as is possible with a subjective test. Hahaha.
I guess I should specify a bit further - sweep/tap2wake is really only effectively useful when the phone supports some kind of low-power state for the touchscreen, otherwise the screen has to remain on in order to use it.
I'm sure sweep2sleep would be possible, but if there's no low-power state for the screen, it wouldn't really matter for me in the end. Moto display sounds like exactly what I'm talking about, though I don't know if it includes any low power mode for the touch features, as well as the display.
I'm gonna look into this a bit more, and see if I can dig up any info. It would be a hardware feature, designed-in, so it definitely should be discoverable. I figure if I can find out all the information for one of the people who have written kernels for the phone, they shouldn't have a problem emulating the feature. It's popular enough, and with the low-power state, shouldn't be too complex to implement.
JohnHorus said:
I guess I should specify a bit further - sweep/tap2wake is really only effectively useful when the phone supports some kind of low-power state for the touchscreen, otherwise the screen has to remain on in order to use it.
I'm sure sweep2sleep would be possible, but if there's no low-power state for the screen, it wouldn't really matter for me in the end. Moto display sounds like exactly what I'm talking about, though I don't know if it includes any low power mode for the touch features, as well as the display.
I'm gonna look into this a bit more, and see if I can dig up any info. It would be a hardware feature, designed-in, so it definitely should be discoverable. I figure if I can find out all the information for one of the people who have written kernels for the phone, they shouldn't have a problem emulating the feature. It's popular enough, and with the low-power state, shouldn't be too complex to implement.
Click to expand...
Click to collapse
Cool - definitely report back - it would be nice to know if this is embedded in the hardware somewhere. I hope it is, unlike optical.image stabilization. Damn!
XxMikeMasterxX said:
What do you mean nearly 24 hours overall - how long before you had to recharge?
I need to learn more about I/O scheduling. I've changed to Row and 512 as you recommend but where will I see the difference? When I connect to my PC? When apps access internal storage?
I've changed my governor back to lionfish. Smartmax wasn't doing it for me. 200 big 800 little. I'll look into that Tesla ROM too.
I was hoping this thread was gonna be more popular. I hope some people have gotten use out of it so far! Grow little thread, grow!
Click to expand...
Click to collapse
Yes nearly 24 hrs before I had to recharge. As for Row you should notice it with both situations. I use it because of other phones I had before people were saying it was one of the better I/O schedulers.
Actually I have a picture of when I got it. Was nearly 23 hrs not 24 but still.
Hey developer,the banking apps I have does run after flashing a custom rom.Is there any workaround for this?.have to reflash stock after trying any custom rom.Its a pain in the as*.
xtremeed2705 said:
Yes nearly 24 hrs before I had to recharge. As for Row you should notice it with both situations. I use it because of other phones I had before people were saying it was one of the better I/O schedulers.
Actually I have a picture of when I got it. Was nearly 23 hrs not 24 but still.
Click to expand...
Click to collapse
Row is essentially the best scheduler. Benchmarking is weird, because by design it's an optimized test case and not a use case. Use cases will always be variable, but generally with a smartphone writes aren't too latency-sensitive. That's why Read Over Write generally works the best once your phone is settled, because reading is most of what it does. Doesn't write too often.
There are lots of custom governors, not so many custom schedulers, and lots of suggestions, but generally stock *IS* best, and if you don't understand it, you should not change it. Governors are fun to play with but even they can cause issues if poorly coded. Changing governors will give you a huge impact on battery, but also a relative impact on performance. It all depends on the use context. You'll rarely get much battery life without a performance hit unless you custom-tune settings for your own use context.
As for read-ahead, that value is iconic of exactly what I'm talking about. It is the "chunks" of data that your OS reads in one go. So if it needs 2k, or 2m, it reads a different number of chunks, but each chunk will be the size set by I/O read-ahead. Google likes 512 best. I've been told by the dev for the EX Kernel that internal Motorola devs like 128 best. Benchmarks like the biggest value possible, because they present the OS a massive pile of data and ask it to read it all as fast as possible. In that context, a large chunk size saves time. In most contexts, you read more than you need half the time. So a low value like 128 saves battery and memory.
---------- Post added at 09:10 AM ---------- Previous post was at 09:08 AM ----------
kiran91 said:
Hey developer,the banking apps I have does run after flashing a custom rom.Is there any workaround for this?.have to reflash stock after trying any custom rom.Its a pain in the as*.
Click to expand...
Click to collapse
Android pay does this too, it's a "security" feature built-in by the devs to stop hacking. Not really necessary, but then neither are smartphones, so you take what you can get I guess. No ROM developer can work around this for you. The app is detecting any modification whatsoever. Even root may cause it.
xtremeed2705 said:
Yes nearly 24 hrs before I had to recharge. As for Row you should notice it with both situations. I use it because of other phones I had before people were saying it was one of the better I/O schedulers.
Actually I have a picture of when I got it. Was nearly 23 hrs not 24 but still.
Click to expand...
Click to collapse
Badass dude. 9 hours SOT is wicked.
I'm finding the phone app drains the battery like crazy. Is this to be expected?
Hey @JohnHorus - thanks for your informative post. I'm currently trying Row 128 and will report back but I doubt I'll see any real-world difference in use. Memory and battery are two soft spots for me so I'm hopeful 128 will maintain solid performance.
Looking forward to reading about others' setups!
XxMikeMasterxX said:
Badass dude. 9 hours SOT is wicked.
I'm finding the phone app drains the battery like crazy. Is this to be expected?
Click to expand...
Click to collapse
Yeah in my experience it drains the battery more then doing other things for some reason. As you can see in my 9 hrs picture I only used the phone for like 2 minutes lol.