Does undervolting really save battery life? - Samsung Galaxy W I8150

Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet

TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
What part of "you won't save more than 2%" you didn't understand?

ilusi0n_ said:
What part of "you won't save more than 2%" you didn't understand?
Click to expand...
Click to collapse
Well, i don't really understand WHY it doesn't save more than 2% of the battery life. Afaik, EXUV does reduce heat and improve battery life by miles. But that's what I thought. In reality which is this, im not rly sure why that even with EXUV, it still cant save more than 2% of the battery life.
Sent from my S800 China Phone

TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
I'm not technically expert with things like this but I have read an article/ blog before that undervolting may damage a phone since it was designed to work with that specific voltage. So, I actually didn't do that even UC or OC. Just saying.....

Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)

r25txe said:
Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)
Click to expand...
Click to collapse
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/samsung-kernel-msm7x30/commit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware

sir mordred said:
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/sa...mmit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware
Click to expand...
Click to collapse
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.

So to sum all this up. We just have to leave the CPU & voltage tables alone since it damages hardware?
Via the Internet

It's not that you have to, but that chip designer recommends it.

r25txe said:
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.
Click to expand...
Click to collapse
That was also the POST that I'm referring to that I've read :good:

Related

[Q] Safe Overclocking speed

How fast can I overclock my chip to in my Rhod100 safely?
I'm using OCT I.5
CPUs are all different from on another. A "safe" speed for one person may not be for another. Best bet is to experiment by trying the next increment up, and test to see if there is any instability, SOD, etc. If everything looks okay, try the next increment up.
Some people on the overclocking thread seem to be having good luck at the lower-700s, with dynamic OC'ing turned off. I have mine set for the default 652 MHz setting (but with dynamic OC'ing off) just to be on the safe side.
You do not increase voltage, so overclocking to any value should be safe. In the worst case you just hang the device, but a softreset fixes this. I found the 710Mhz frequency to be 100% reliable.
Thanks Guys. Been a big help
i dunno, depends on software and rom. i personally do 768 no dynamic, all settings 0 at 1000ms on energy cookie 23138 sep 14. no reset needed for a month or so. and when it did it was user error lol.
but u just gotta play with it. expect to reset a few times. and id keep all settings on 0 at 1000 ms. just me.
Jackos said:
You do not increase voltage, so overclocking to any value should be safe. In the worst case you just hang the device, but a softreset fixes this. I found the 710Mhz frequency to be 100% reliable.
Click to expand...
Click to collapse
710 is the most reliable ive seen from public opinion
I did a bit of research and found out the chip is capable of 850mhz.
I've got mine running at 806.4 and seems to be runnning fine. I switched the stepping off. Feels awesome.
uncleswoop said:
i dunno, depends on software and rom. i personally do 768 no dynamic, all settings 0 at 1000ms on energy cookie 23138 sep 14. no reset needed for a month or so. and when it did it was user error lol.
but u just gotta play with it. expect to reset a few times. and id keep all settings on 0 at 1000 ms. just me.
Click to expand...
Click to collapse
How can no reset be needed for a month if your rom version is only 3 days old?
enahs_ said:
How can no reset be needed for a month if your rom version is only 3 days old?
Click to expand...
Click to collapse
i lol'd
enahs_ said:
How can no reset be needed for a month if your rom version is only 3 days old?
Click to expand...
Click to collapse
i meant from reset needed from sod's or other issues.
energy has been my rom of choice for quite some time. every version has been fully compatible for me with oct. thats what i meant to say
Can someone link to the overclocking software? I'd like to give it a try.
How about battery life and temperature? Does overclocking to 710 reduce battery life and increase the phone's operating temperature? If so, by how much?
gromky said:
Can someone link to the overclocking software? I'd like to give it a try.
How about battery life and temperature? Does overclocking to 710 reduce battery life and increase the phone's operating temperature? If so, by how much?
Click to expand...
Click to collapse
There Are 2 Overclocking Apps You Can Find Them
Here http://forum.xda-developers.com/showthread.php?t=725290
&
Here http://forum.xda-developers.com/showthread.php?t=698374
Does overclocking the phone kill your battery? I already only get two days of battery life.
Yes, I noticed decreased battery life with 710Mhz OC.
gromky said:
Does overclocking the phone kill your battery? I already only get two days of battery life.
Click to expand...
Click to collapse
I get three days with NRG ROM, but I have pretty light use. However with OC it is no worse than before.
Also using Energy ROM, have experimented overclocking at 650 MHz, and now 710 MHz for the past few days (based on suggestions in this tread, actually!). Haven't noticed a significant reduction in battery life. I get around 2 days also. 2 days has been pretty typical on the Rhodium for me, with the stock ROM and Energy, and moderate usage. Most comments on the main overclocking thread seem to indicate that battery life is not greatly reduced. Just anecdotal comments, of course. Don't think anyone has done any halfway scientific testing.
~8mA more during sleep
~40mA more during stress
That's why you don't notice a big difference during "normal usage". Try not to use the device for some days (I know it's hard ;D) with overclocking and without so you will notice the difference. Like I said in another thread: We do not measure the battery life while using the device - because this isn't measurable and doesn't give any reliable results.
It's like the percent battery driver - any clever person should notice that this cannot be described as precise.
Im using 787MHz dynamic oc with no problem at all. It doesnt seem to affect battery life either, but then again Im not using Sense.
Jackos said:
~8mA more during sleep
~40mA more during stress
That's why you don't notice a big difference during "normal usage". Try not to use the device for some days (I know it's hard ;D) with overclocking and without so you will notice the difference. Like I said in another thread: We do not measure the battery life while using the device - because this isn't measurable and doesn't give any reliable results.
It's like the percent battery driver - any clever person should notice that this cannot be described as precise.
Click to expand...
Click to collapse
I'm not exactly sure what point you are making. My observation is that with or without OC, the length of time my phone can be used before recharging is approximately the same, i.e., I don't detect any decrease in battery discharge.
Since my usage patterns are the same for both cases, this variable drops from the equation.
So, you need to run the program every time the phone boots? Or does the program remember its settings?

Feelings about undervolting.

How does everyone feel? I've always assumed that it forces better battery life but I've noticed a lot of people do. I've done it till now just because I figured it has to help since every kernel I've used on any phone is under volted. Do you think it helps? Any kind of proof is welcome but so are opinions.
Sent from my Galaxy Nexus using XDA App
I'm on board with a modest under volt, but when you drop the voltages to the point that the phone is no longer 100% stable any minuscule battery savings would be undone by the forced reboot.
GN's cpu uses a power management technology called smartreflex which dynamically changes voltages used by different frequencies. The values that are set with setcpu and similiar apps are only the maximum voltages that smartreflex is allowed to use. The actual voltages may be well below the nominal ones.
Personally I never noticed any significant improvements. It's hard to tell how much but it is definitely not worth going really low. Right now I am using leankernel which is undervolted slightly by default.
codesplice said:
I'm on board with a modest under volt, but when you drop the voltages to the point that the phone is no longer 100% stable any minuscule battery savings would be undone by the forced reboot.
Click to expand...
Click to collapse
This.
Apps may stop working randomly or the phone may have random reboots if you mess with the wrong speed.
Honestly speaking, just go to setting...
1. then data and limit background data of certain unimportant apps
2. developer options > background process limit. Set it to like at most 3.
These ways are much safer and will boost your battery life.
Thanks. Right now I have a decently aggressive but stable UV but I'm gonna up them another 50mv just to be safe and do that. Thanks for the suggestion I didn't know I could do that. I'd hit thanks if I wasn't on a phone...
MilkPudding said:
This.
Apps may stop working randomly or the phone may have random reboots if you mess with the wrong speed.
Honestly speaking, just go to setting...
1. then data and limit background data of certain unimportant apps
2. developer options > background process limit. Set it to like at most 3.
These ways are much safer and will boost your battery life.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using XDA App

[Q] Overclock

Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Deshabilitado said:
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Click to expand...
Click to collapse
I cover this in the guide I wrote in general (which has been pushed down quite a ways) but anyways here goes another version.
Overclocking varies from device to device, even of the same model. Variances in tolerance is on a per chip basis, as long as they pass within a certain range they are sent out for production in devices. Overclocking in general is within means of the chip's abilities, if it isn't, you'll know it. Generally speaking, 1.4 GHz is perfectly fine on our devices. 1.5 GHz is also usually ok, but is the upper end of what the Tegra2 can usually tolerate. Few an go past 1.58 GHz, my old G2x's tegra2 could hit 1.7 GHz,but that's well beyond "normal" range.
Overclocking a device is the same as overclocking a PC, you need to be careful with it. Don't just ramp it to 65% overclock and expect it to run fine. Every chip is different. Do it in steps, and test each step before moving on. Test it in normal usage, test it in heavy usage, gaming, etc.
An overclocked device will certainly run hotter then normal, it's running faster, drawing more power, and that creates a hotter running core, no way around it. Keeping in mind there is no airflow in these things, that makes the biggest enemy to CPUs even more dangerous.Does it run so hot that it can shorten component life? Sure it can. Will you still have the device when it happens? I doubt it. Likely, we'll be on Tegra5 before it even begins to show signs of stress.
One of the nice things, though, is our CPUs range so much in speed according to load that just because your Max is 1.5 GHz, it doesn't always run there. Most times, it won't even be in the overclocked speeds. Does it run faster? Sure does. Benchmarks will raise nicely, and games that maybe got choppy before will smooth out, movies that couldn't play well will be fluid, the heavens will align, mankind will discover world peace and I'll win the lottery.
All that being said, I don't usually overclock, in fact I tend to underclock a little to 800MHz. Its usually sufficient to do normal tablet stuff, and I adjust the speed according to what I require. If my movie is lagging, I'll bump it up until it smooths out. Same for a game if it needs it.
In the end, its all personal choice, really. Just because you CAN overclock, doesn't mean you NEED to. IMO a well tuned governor will give as good a result as overclocking in normal usage, and a good I/O Scheduler will also help alot, without adding anymore heat or stress to your device.
TL;DNR:
Overclocking is fun. It causes more heat. It likely won't explode within the time you own it. Or your children. Your battery will suck.
thanks pio for the answer, thats what i needed to read, cuz usually when u talk about OC its like "yeah dude, OC its "tha greeeeeat doi it dude" or something like "dont do it!!! u will decrease your tablet life" and yes, i know that devices are way to diferent even if they are the same model, and also im agree with u, governors and I/O works better than OC but we dont have many for our device, i miss the smartass v2 governor,or the brazzilianwax too, but well, hope someone can port it for us someday.

Ktoon's KT747 2/8/13 Kernel vs Task650's 2/10/13 Kernel

What are your guys' opinions on the performance of these two kernels? From what I've gathered it seems like KToon's kernel is meant for overclocking, but then what would one use task's for?
Task's recent update to his kernel makes me want to try it because I've been using KToon's kernel with the ktoonservative governer and row scheduler UV'ed a little bit but unlocked to 2.1GHz and have been having some pretty bad battery life in mu opinion, do you think switching to task's kernel would be better on the battery?
Well what do you guys think?
Fun Fact for the day. Versus threads get shut down in no time here on XDA.
P.S- Why wouldn't you just try it first before making a thread about it? Kernels take about 3 seconds to flash. Also. No one can tell you that you will get better battery life on one or the other considering all of the variables. We are all in different locations, use different apps, have different settings, and we all use our devices differently. You need to try them both out and see which one works better for YOUR device.
Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.
berryman13 said:
Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.
Click to expand...
Click to collapse
I'm not giving you are hard time. I'm just telling you the facts here. If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Which no one can tell you one is better than the other for. Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.
I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
gilo123 said:
I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.
task650 said:
If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.
Click to expand...
Click to collapse
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
gilo123 said:
Ithey're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.
berryman13 said:
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Click to expand...
Click to collapse
He cannot answer this question honestly. He doesn't have your device. You're not understanding. He can have the best battery life possible on my kernel but if you use it, you could have the worst battery life possible. IT'S DEVICE DEPENDENT. Will you please just do yourself a favor and take 3 seconds, flash the kernel, and see. You say you've tried them both, but you are also asking about playing games and what not with them? You would know if you had tried them dude. Same goes for the governors & schedulers. You would also know that if you had actually tried them both. I need to ask you this. Why won't you just try them and see for yourself. Are you really the type of person to flash what people tell you to your expensive device?
Look dude. I'm only trying to help you here. I'm not quite sure why you wouldn't just take my advice here. I have quite a bit of experience with this stuff and I'm trying to help you get the best experience possible. But it seems as though you think that personal opinions of others are whats best for your device when in all reality they are not. Real life testing is what will prove to be best for your device. Trust me.
berryman13 said:
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.
Click to expand...
Click to collapse
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Comprehensive list. I like it. Now I gotta figure out which gov I'm gonna use when I flash the underwear kernel.
Thanks everybody for their input, if anyone else has anything to say then please go for it!
Wiping cache + dalvik and flashing underwear kernel then fixing permissions and rebooting and gonna take a look around performance control to see whats up.
task650 said:
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.
Click to expand...
Click to collapse
Ohh Thnx man. While you're here any suggestions as to how I go about fixing/finding out which apps are responsible? Also,any combinations/settings you might recommend trying with your kernel,despite the phone dependent variables and what not. Thnx )
Running the underwear kernel today, changes frequencies min and max to the farthest it can go. Will report back with my results.
Sent from my SGH-I747 using xda app-developers app
Sorry man, but no need to report back here as it has already been stated that each User's experience will differ upon usage, apps, personal habits, planet alignment,... Boils down to a flash and see type thing.
Thread Closed
Here is some info on Governor and I/O schedulers. Obviously it isn't going to include Ktoonservative or ROW but you get the idea.

Overclocking of LG G4

Hi everybody,
I want to know if we can overclock our Snapdragon 808 to 2GHz (ARM A72 cores) with a modified kernel.
Also, If somebody is going to work on this challenge.
Thanks!!
Androsesp said:
Hi everybody,
I want to know if we can overclock our Snapdragon 808 to 2GHz (ARM A72 cores) with a modified kernel.
Also, If somebody is going to work on this challenge.
Thanks!!
Click to expand...
Click to collapse
A57 cluster, probably yes. I'm also working on a kernel, but I intensely dislike Overclocking because it isn't all that useful. The key to performance is with optimisation, not with raw power. So I'm most likely not going to include it, sorry.
What about underclocking and/or undervolting?
I think performance is good enough as it is, but would like to get better battery life.
I would like to be able to undervolt in order to relieve the bugging high temp warning. This phone rarely uses max performance. So, overclocking is not really a priority. Maybe a custom hotplug.
Crappy cpu. No point messing with it.
Sent from my A0001
GUGUITOMTG4 said:
I would like to be able to undervolt in order to relieve the bugging high temp warning. This phone rarely uses max performance. So, overclocking is not really a priority. Maybe a custom hotplug.
Click to expand...
Click to collapse
Hotplugging has been dropped not long ago. You'd basically need to reinvent it. Plus it costs more power than it would save
And what about undervolting to prevent excessive heat, @mythos234?
yea i guess undervolting is the only benefit here coz 2 ghz wont be hard to achieve but getting that overheating msg sooner aint worth it...
next thing u know is accessory back plates with mini fans to keep the phone cool...
seriously tho what good is the extra power for ? the phone is already fast with the correct setup (not that i saw any lag when it was stock)
anyone knows how to see the cpu binning in this phone?
oile said:
And what about undervolting to prevent excessive heat, @mythos234?
Click to expand...
Click to collapse
Excessive Heat?
mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
A number of people have gotten over-temperature messages, sometimes with the phones even shutting down.
This has been reported with using navigation, I believe, and I know people have reported it when shooting video. High screen brightness is likely a contributor. But there are examples of the phones running too warm.
Personally, I'd be more interested in cooler running, and longer battery life, rather than increased peak performance. So underclocking, if anything.
Well, the overclocking is not necessary, but is an opportunity to know the limits of the chipset. Moreover, with it we could know if we can make undervolting to our phones and make it more battery efficient with an underclocking kernel, when we need it.
RedOCtobyr said:
A number of people have gotten over-temperature messages, sometimes with the phones even shutting down.
This has been reported with using navigation, I believe, and I know people have reported it when shooting video. High screen brightness is likely a contributor. But there are examples of the phones running too warm.
Personally, I'd be more interested in cooler running, and longer battery life, rather than increased peak performance. So underclocking, if anything.
Click to expand...
Click to collapse
Happens to me too when gaming. The problem I observe is that Indeed, it is not excessive heat. But LG thinks otherwise.
You can actually underclock using Kernel Auditor and disable cores. Unless you meant Undervolting.
mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
Wanna check out periscope and comment back ? Atleast I know that app will push the phone to its limits.
Sent from my LG-H818 using XDA Free mobile app
Currently using Kernel Adiutor to disable both A57 cores and the phone screen does not heat up like before... Battery life has improved from what i saw yersterday. Continuing testing today. Only problem i have is the damn phone will enable one of the A57 cores after a while which i dont like. I need my settings to stick.
Any Kernel Dev know which files are causing this? Tab 3 had something like this but a couple of files changed solved the non sticking settings on cpu.
Overclocking/underclocking sure but just disabling cores would work for most.
Sent from my LG-H815 using Tapatalk
mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
lol, you're funny.
marcadam said:
lol, you're funny.
Click to expand...
Click to collapse
I haven't had any popups or heat related reboots, so I was wondering what the matter is here.
On every phone I see complaints over heat so I wondered if something is to it here or if it's the usual. And if there are overheating warnings and shutdowns, then there might be indeed something in the bush.
Try charging your phone in the car whilst using google maps to get to an important meeting, and then take a call just for good measure............and boom, there you have your own little meltdown.
marcadam said:
Try charging your phone in the car whilst using google maps to get to an important meeting, and then take a call just for good measure............and boom, there you have your own little meltdown.
Click to expand...
Click to collapse
That happens on every phone I ever had though. It's advised to not use a device while charging at all, so if you stress it to 120% while charging, of course it heats up..
@mythos234 is a pleasure to have you here (speaking as xiaomi mi2s owner too xD)
What Temps do you reach using cpu intensive apps?

Categories

Resources