Related
Hey everyone, there is an overclocking app in the market, anyone care to give it a try?
Edit: So I downloaded it lol. Here are some screenshots. BTW, is there anyway I can verify that the cpu freq is actually being adjusted?
*Just for fun I ran neocore to see if it would raise my FPS. lol.
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
For example, atrackdog would take me at least 20-30 seconds to load my full app list (184 apps)
After installing overclock, it loaded in under 5 seconds.
i'll run other programs, and post my results.
I ran droidgear (game gear emulator) before and after, and I can honestly say it was faster (not a placebo affect).
-Before: droidgear would take over 4 minutes just to get to the menu screen
-After: i was actually able to load a game in under 1 and a half minutes, I even let it sit to run the demo, and it is the fastest ive ever seen an emulator run on this device (compared to NesEmu, and GB emu)
It would probably actually be playable if tweaks were made to the application codebase, and android Open GL stack.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
well, i was too, and then i downloaded it and said "aahh, what the hell, if i break mine, ill just take my wifes haha..." probably not the best of plans but i installed it anyway
sooo i havnt burnt up my phone yet, but here is my issue with the app, does the app only work untill you reboot your phone?
because when i reboot my phone, it goes back to the default speed according to the app
also, my phone tends to hang up (stuck on the apps screen, no buttons work, screen wont rotate, power button wont shut screen off) when using the 528MHz
so far, i havnt found a reason to pay a dollar for it, but ill keep testing
[UPDATE]
resolution for all below tests is 320 x 480
i tried neocore like posted above, using the mid level setting, and i actually did raise my fps from
DEFAULT CPU (248 MHz): 20.5 (with sound off)
384 MHz: 25.0! (with sound off)
DEFAULT CPU (248 MHz): 14.5 (with sound on)
384 MHz: 20.8 (with sound on)
still havnt gotten the fast speed to work yet, but im still trying to figure that out, on another note, sweeter home does seem to load a little faster
[UPDATE]
Incase you didnt see my sig, im not running on a ADP1 phone, so that might by why the fastest setting doesnt work for me, but so far 384MHz is making a noticeable difference with NEOCORE and SWEETER HOME
andonnguyen said:
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
Click to expand...
Click to collapse
i use snap photo, which used to take FOREVER to load up on my g1 using the camera button, its significantly faster using the 384MHz setting, good observation
Ok, so so far here is a list of things ive noticed (using 384MHz vs 248MHz):
-FPS in NEOCORE increased on adverage 5 to 6 fps
-Sweeter Home doesnt lag NEARLY as much as it used to (ALOT less force closes)
-Snap Photo doesnt take a month to load using the camera button
-G1 Wakes up properly which was a issue my g1 (and others on this forum) had
-Even though the app says it will "kill" the battery, using 384MHz during normal use of the phone isnt "killing" my battery, however, doom (while runs better (even with sound on)) seems to be dropping my battery level faster, but the game is running faster, which is the trade off id expect when running these apps together
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
speoples20 said:
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
Click to expand...
Click to collapse
all of our battery life sucks unless you have the extended battery, im not getting THAT big of a battery drain according to the system monitor app, and it DOES make a difference on g1's that have lag issues (running tons of apps like i do)
in other threads, people have complained about the g1 not waking up quickly sometimes, ive yet to have that issue since ive clocked mine up to the 384MHz setting
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
The program installs a script on your sd card called ocx_tmp.sh and adjusts it that way, it'll write to /system as -rw (from what I've discussed with someone) would probably cause instability.
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Try it before and after setting the cpu freq in overclock and you'll see what I mean =)
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
andonnguyen said:
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
Click to expand...
Click to collapse
im not as familiar with clocking/overclocking so i wasnt sure if i was clocking it to 384, overclocking it to 384, or what, so what would be the proper thing to put in my sig? lol because according to my first quote, true overclocking wouldnt be untill i went beyond 528, so from the view of my first quote, im not OVERclocking, im clocking, wheras your saying im overclocked
andonnguyen said:
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Click to expand...
Click to collapse
so is it infact the program thats changing the cpu freq or is it the phone? if its the program, is this to avoid overworking the cpu without the demand?
andonnguyen said:
.
The program will reset the cpu freq back down to 384mHz after the phone sleeps.
Click to expand...
Click to collapse
by sleep do you mean turning the screen off using the power button? because i saw no change in my cpu freq when doing so using your commands
ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
dont know, but i found this over at the android community:
Technical Features
Supports WCDMA/HSUPA and EGPRS networks
Multimedia Broadcasting Multicast Service (MBMS)
Integrated ARM11™ applications processor and ARM9™ modem
QDSP4000™ and QDSP5000™ high-performance digital signal processors (DSP)
528 MHz ARM11 Jazelle™ Java® hardware acceleration
Support for BREW® and Java applications
Qcamera™: Up to 6.0 megapixel digital images
Qtv™: Playback up to 30 fps VGA
Qcamcorder™: Record up to 24 fps QVGA
Up to 4 million triangles per second, and 133 million depth-tested, textured 3D pixels per second fill rate
gpsOne® position-location assisted-GPS (A-GPS) solution
Support for third-party operating systems
Digital audio support for MP3, aacPlus™ and Enhanced aacPlus
Integrated Mobile Digital Display Interface (MDDI), Bluetooth® 1.2 baseband processor and Wi-Fi® support
maybe that info will help? if not sorry
I remember reading somewhere by someone that it runs at 384 by default, and I think the post above confirms that...
ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
gui fluidity is definitely increased, and sluggishness between app switches and when the translucent app drawer opens up is gone. i like it, but to the average person there probably is no need to do it.
keep in mind this is also not overclocking the cpu, it's clocking it to its default spec. as it is an embedded arm, it is designed to run hot, so i guarantee you are in no danger of hurting your phone.
also, do not listen to people that claim there could be no gain from overclocking, just because the bus speed is slower than the cpu speed does NOT mean there will be no improvement in system performance. if that were the case, there'd be no use for 4ghz desktop processors.
cache still runs full speed, and common execution paths stay in cache meaning no prefetch from system memory, meaning BIG improvement in many cases. (that's why cache exists.)
damnoregonian said:
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
gui fluidity and responsiveness is greatly improved. sluggishness if app switching and the translucent app drawer are completely gone.
for many i imagine this means there isn't really any reason to clock the cpu up to its stock speed, but to each their own.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
Click to expand...
Click to collapse
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Holy crap. Used this @528MHz with Haykuro's version 4.5 apps to sd ROM and the osk works SO MUCH BETTER!!!! Also I got 25.6 fps on neocore... very smooth
wootroot said:
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Click to expand...
Click to collapse
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
A modded version of JF's ROM would ROM.
I DO notice the sluggishness and it bugs the heck out of me. (I switched from a WING with a 200MHz CPU, and although it IS faster than the wing, it doesn't seem significantly faster and seems to much slower when I open up the camera...
damnoregonian said:
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
Click to expand...
Click to collapse
that involved eh?
thanks for this post though, now i understand more about the idle loop and why the cpu freq resets with each reboot
maybe someone can take this stuff further like he said, that kind of stuff would be worth the dollar, imo more than a dollar
well... i don't mind providing basic procedure and source, i just don't want to get dragged into level 1 support of the procedure.
i'll go ahead and package up some source, prebuilt boot images based on JF's RC33 (which is what i run) and a basic procedure.
Ever since I flashed the 213 leak, battery life has been a bit disappointing. To help things along, I downloaded SetCPU (haven't used it since my good ole OG Droid) and let it autodetect settings. To my surprise the governor was set to 'interactive' instead of hotplug like it was on stock GB.
My understanding is that hotplug allows the phone to disable unneeded cores during periods of low utilization, while interactive does not (although both cores can be disabled when the phone is sleeping). Do you think switching to hotplug from interactive will improve battery life?
My battery life is much better since switching, but I also disabled 4G (on WiFi most of the time) and added screen off and low battery profiles (600mhz and 800mhz max respectively) which muddy the waters a bit. I thought I would mention it on here for those of you who feel the same, it might be an easy way to improve battery life on the leak.
That's interesting. I've been using the .213 leak and my battery life has been quite good. I haven't noticed any particular drop in battery life, and I keep 4G on all the time. If I don't use my phone much, it's not uncommon for me to have 60% left at the end of the day.
Do you use anything like SetCPU? I am wondering whether I can confirm that the default governor of the leak does not shut off one of the CPUs when it is idle. If nobody can confirm I'll get around to checking it myself this weekend :laugh:
Sorry, I haven't messed with my cpu settings.
I've received Nexus 6 from FlipKart, Its great but two major concerns:
1. Screen is very yellow (warm color) and on reducing brightness it becomes magenta. When compared to any other phone including Nexus 5, its extremely yellow. Tried couple of apps, none of them do a good job of fixing the yellows. Did anyone find a good app/setting to calibrate this screen right?
2. Battery life is pathetic: From 100% to 10% in half day. SOT is barely 3 - 3.5 hours (Greenified Facebook, Encryption off), no gaming, where as my friend gets 5hours. Sometimes phone hangs and switches off. When I switch on, it looses 15% battery. It has only been charged 2-3 times (only got it 2 days ago). Does it get better with time? or Am I having a faulty battery?
Update: forgot to mention my phone shuts down at 28% battery. And it didn't boot at all. I realized battery was zero. Is this calibration issue? Or bad battery
Flash elementalx, you'll be able to change color values and battery life is great
1. You can change your RGB using any kernel with support to it. Almost every single kernel have support to RGB LCD KCAL. Use a app such as Trickster to modify the RGB once you flashed a kernel of your choosing.
2. Battery life is subjective to how you use your device. Just because someone was able to achieve 5 hours+ SOT doesn't mean you will either because there are way too many factors that play into effect such as: cellular signal strength, wakelocks, apps installed, etc. If you want to maximize your battery life, look into underclocking the CPU/GPU frequency and flash a custom kernel (e.g. Franco) that removes mpdecision. Mpdecision is a huge battery drain and the frequencies that it selects is completely random and unnecessary in my opinion.
http://forum.xda-developers.com/showpost.php?p=57808725&postcount=7 my battery life with Franco pre-r1.
I agree that mpdecision really does drain battery a lot. I have mine OVERCLOCKED to 2.88 ghz with sensei kernel and intelliplug. And I am still getting way better battery life than stock. Just flash this kernel with intelliplug and there goes your battery issues. And you can also adjust your screen colors.
rmx36 said:
I agree that mpdecision really does drain battery a lot. I have mine OVERCLOCKED to 2.88 ghz with sensei kernel and intelliplug. And I am still getting way better battery life than stock. Just flash this kernel with intelliplug and there goes your battery issues. And you can also adjust your screen colors.
Click to expand...
Click to collapse
For more elaboration on mpdecision,
All Qualcomm based phones have Qualcomm prorprietary userspace binary called "mpdecision" aka m(ake)p(oor)decision. Instead of letting the kernel itself to decide what frequencies and how many cores to run, this "mpdecsion" binary polls the kernel run queue statistics and decides for the whole system the "optimal" frequency and the "optimal" number of cores to use. The concept is fine, except the decision making is done in userspace and it's 100% closed source so there's no way to tweak it and there's a latency (because all userspace binaries needs to "poll" the kernel for the latest information which is slightly delayed). - faux123
Click to expand...
Click to collapse
In other words, mpdecision makes your phone sit at 1.5GHz for doing the most simplest tasks, even composing a email it'll bring your frequency to be at 1.5GHz.
Download CPU Spy and use your phone, then look at CPU Spy and you'll see how much time is spent in that frequency. Then flash another kernel that does not use mpdecision then you'll see the difference, the phone sits at frequencies that makes sense for the load that is on the device.
The alternative solutions would be, Franco's Hotplugging Algorithm or intelliplug by Faux.
Battery life is very subjective.
I am still 100% stock, encrypted, auto brightness and get over 6 hours SOT every charge. Mainly WiFi, some LTE. No gaming.
I will root and switch to another kernel when I have time and see the difference. I would expect more battery.
However if you are only at 2.5 hours SOT on a full charge, I wouldn't expect it to double just by changing kernels.
JasonJoel said:
Battery life is very subjective.
I am still 100% stock, encrypted, auto brightness and get over 6 hours SOT every charge. Mainly WiFi, some LTE. No gaming.
I will root and switch to another kernel when I have time and see the difference. I would expect more battery.
However if you are only at 2.5 hours SOT on a full charge, I wouldn't expect it to double just by changing kernels.
Click to expand...
Click to collapse
Thats so impossible. I've switched to 2G only but i run on Wifi all time and yet 1 day standby and 3.5hrs SOT.
zephiK said:
1. You can change your RGB using any kernel with support to it. Almost every single kernel have support to RGB LCD KCAL. Use a app such as Trickster to modify the RGB once you flashed a kernel of your choosing.
2. Battery life is subjective to how you use your device. Just because someone was able to achieve 5 hours+ SOT doesn't mean you will either because there are way too many factors that play into effect such as: cellular signal strength, wakelocks, apps installed, etc. If you want to maximize your battery life, look into underclocking the CPU/GPU frequency and flash a custom kernel (e.g. Franco) that removes mpdecision. Mpdecision is a huge battery drain and the frequencies that it selects is completely random and unnecessary in my opinion.
http://forum.xda-developers.com/showpost.php?p=57808725&postcount=7 my battery life with Franco pre-r1.
Click to expand...
Click to collapse
Impressive! I'm trying ElementalX kernel right now. Is it safe to switch-off MP-decision on that using trickster or shall I go with franco blind folded.
taranfx said:
Thats so impossible. I've switched to 2G only but i run on Wifi all time and yet 1 day standby and 3.5hrs SOT.
Click to expand...
Click to collapse
Well, not impossible as it has been that way on my phone since day 1.
But i agree that it is really odd how some people are getting 3 hours and others getting 6.
I had the opposite on my Note 4 though. Everyone got 6 and I got 4. So who knows?
taranfx said:
Impressive! I'm trying ElementalX kernel right now. Is it safe to switch-off MP-decision on that using trickster or shall I go with franco blind folded.
Click to expand...
Click to collapse
You only want to disable MPDecision if theres a alternative. For Franco, mpdecision is 100% removed so you don't need to disable anything.
I don't know ElementalX so I can't say, ask in their thread. If you use Franco, everything is done for you and you don't need to do anything on your part.
My battery life with LK is pretty good as well! I was able to tether for 10 hours straight and still had 22% left after sleeping ~8 hours.
I'm totally a rookie for modify the kernel, but i wish to get better battery life for my nexus 6. So i read often that changing the CPU Maximal/Minimum Frequency - for example for the franco.kernel or Lean Kernel or other kernel - almost everybody get a better battery life and no wake locks. At the moment i use the nexus 6 stock with no custom software, but the battery life isn't very good.
My questions now: How can i setting the right CPU Maximal/Minimum Frequency for the franco.kernel or Lean Kernel or other Custom Kernel? Are there specific apps? And the most important question: Which are the right numbers to set for the CPU Frequency?
Thanks. :good:
Erdiou said:
I'm totally a rookie for modify the kernel, but i wish to get better battery life for my nexus 6. So i read often that changing the CPU Maximal/Minimum Frequency - for example for the franco.kernel or Lean Kernel or other kernel - almost everybody get a better battery life and no wake locks. At the moment i use the nexus 6 stock with no custom software, but the battery life isn't very good.
My questions now: How can i setting the right CPU Maximal/Minimum Frequency for the franco.kernel or Lean Kernel or other Custom Kernel? Are there specific apps? And the most important question: Which are the right numbers to set for the CPU Frequency?
Thanks. :good:
Click to expand...
Click to collapse
first off, questions go into the q&a/help threads, not general. and there are many cpu control apps to use, some free, some paid. thats the way for you to setup your cpu anyways you feel like. and there is no such thing as the right numbers, you need to find the right numbets for your use. me, i overclock to 3033mhz, and still see 5.5-6.5 hours of sot.
Thank you!
You shouldn't necessarily change the minimum and maximum frequencies because they won't necessarily save you battery.
When you look at the mex frequency of 2650 MHz, that's how many clock cycles there are per second. 2,650,000.
Every task you do on your phone will complete within an amount of clock cycles. Let's make some things up to illustrate this. Let's pretend that it takes Facebook app 5,000, 000 clock cycles to open. That means it would take nearly 2 seconds. If you set your Mac CPU frequency to half of stock, that app is going to take twice the time to open. The question is, will running running at 1267 MHz for 4 seconds use less energy than 2650 MHz for 2 seconds?
Looking at the voltage table for elementalx, the stock voltages are 890mV and 1110mV so it seems to me that since the voltage for half the max frequency is a lot higher than half the voltage of max frequency, running a task for twice as long would use more energy than max.
Surely, there will be tasks that take significantly fewer cycles than max frequency, so in those instances it may seem a bit more balanced, but its one of those things you're going to have to just try for yourself. Some people seem to get better battery though personally I'm not tempted.
Thank you, too! Now i understand.
Should I flash only the Lean Kernel or franco.Kernel and then look again at the battery life? Is this enough to get a better battery life on my device?
Erdiou said:
Thank you, too! Now i understand.
Should I flash only the Lean Kernel or franco.Kernel and then look again at the battery life? Is this enough to get a better battery life on my device?
Click to expand...
Click to collapse
no. kernels generally wont give you better battery life, but they can help you. battery life is dependent on how you use your device, how you set up your device, what apps you installed and use, your brightness, and the quality of your phone/data connection. and much more other things that weigh in less then these on nattery life.
some apps you install can be badly written, and take lots of battery, even though you rarely use. dropping brightness can increase your battery life. i keep my brightness below 15% usually. if i raise it to 35-40%, ill see a whole hour less screen on time.
Hey, was just wondering what settings you all have under Kernel Auditor in order to ensure 5 hours+ SOT. I personally have a dual core setup and have the other two cores kick in when the load gets to 90%, but this seems sort of sluggish now and I only get about 3.5-4 hours SOT and I don't play any games; just simple browsing and productivity. Others manage to get up to 5-6 hours SOT and I wonder how, I have NEVER been able to get this much. Standby is great though, 10 hours overnight and I lose only 3% battery. I am running on Pure Nexus Project ROM and latest Hells Core Kernel.
thats about the regular time I get outa mine. If I had to guess a lot of these 5+ hours are from watching videos or something that doesn't involve touching the screen. I've been using HC kernel with just zen decision on max performance settings and gpu on performance governor (since it idles 27mhz anyway might as well ramp up to full 600mhz for touches) for smoothness.
I have it setup that all my cores are on all the time, no hotplugging. ondemand/deadline, mpdecision disabled, fsync disabled. and I get 5+ hours sot every single day. no, I do not watch videos. but I do keep my brightness all the way down.
Hey, where do you go to disable fsync
aroy97 said:
Hey, where do you go to disable fsync
Click to expand...
Click to collapse
it has to be an option in the kernel that youre using, at least the kernel has to expose it so that you can disable it. if its not xposed in general, then you cant disable it. im using despair kernel.
Try undervolting. Unless you severely under clock your cores you won't really see battery life improvement.
I keep my max CPU speed at 2803mhz. You might think "oh well if you're running higher frequencies then more battery drain". Not exactly. The difference between 2649mhz and 2803mhz will be negligible in terms of battery life so I'm seeing a slight performance increase with no significant battery loss. For example, on 2649mhz after a full day of normal usage I'd have about 49% battery life. On 2803mhz I'd have about 43%. I got a good performance increase and a more snappier device in terms of loading web pages, apps, opening documents etc so that extra 6% I lost doesn't matter to me, because its not significantly impacting me, I barely notice most of the time.
So yeah, the same goes for lowering CPU speeds to unless you significantly lower them. Putting max CPU speed to something like 2572mhz, you wouldn't even notice e the difference in battery. Now lowering it to like 1958mhz, or 2188mhz and you'll see a difference because at that point your severely under clocking.
You could also be draining your battery by hotplugging. That's why some people like Zen and MP Decision to keep all cores online when screen is on. If you use your device often, its better to have all cores running. If you don't and its kept in your pocket for hours at a time, hotplugging is the way to go.
Try under volting too. I do. Global Under Volt of -60.
TransportedMan said:
Try undervolting. Unless you severely under clock your cores you won't really see battery life improvement.
I keep my max CPU speed at 2803mhz. You might think "oh well if you're running higher frequencies then more battery drain". Not exactly. The difference between 2649mhz and 2803mhz will be negligible in terms of battery life so I'm seeing a slight performance increase with no significant battery loss. For example, on 2649mhz after a full day of normal usage I'd have about 49% battery life. On 2803mhz I'd have about 43%. I got a good performance increase and a more snappier device in terms of loading web pages, apps, opening documents etc so that extra 6% I lost doesn't matter to me, because its not significantly impacting me, I barely notice most of the time.
So yeah, the same goes for lowering CPU speeds to unless you significantly lower them. Putting max CPU speed to something like 2572mhz, you wouldn't even notice e the difference in battery. Now lowering it to like 1958mhz, or 2188mhz and you'll see a difference because at that point your severely under clocking.
You could also be draining your battery by hotplugging. That's why some people like Zen and MP Decision to keep all cores online when screen is on. If you use your device often, its better to have all cores running. If you don't and its kept in your pocket for hours at a time, hotplugging is the way to go.
Try under volting too. I do. Global Under Volt of -60.
Click to expand...
Click to collapse
undervolting doesnt really save you battery, but it does reduce heat. and hotplugging or having all your cores on doesnt really factor in when you dont use your device that much. as, if you have all your cores on or hotplugging, your phone should be in deep sleep anyways. it does make a difference when your phone is awake. i get much better battery life when all my cores are on all the time.
Should there be a sticky of suggested settings of differing requirements of speed, battery life, etc?
ronaldheld said:
Should there be a sticky of suggested settings of differing requirements of speed, battery life, etc?
Click to expand...
Click to collapse
honestly, I don't think so. as the settings/setup used is always dependent on how you actually use the device. and many people have different opinions on how it should be set up.