As title says.
I am cooling my phone with custom cooler and chipset drain like 1500-1600 mAh for like seconds and throttle instantly 1200 mAh/hour before cpu temperature doesn't even goes up like 40°C than drains between 900 mAh to 1200 mAh. I cooled chipset like 30°C for testing and nothing changed. That lead me that this isn't cpu temperature thing. But i don't exactly understand the point.
I can't sustain cpu frequency 2.84 ghz no matter how much i cool it.
I believe gaming phones that using same chipset drain more than that because of their sustainable performance drastically more than our phone even if ı cool my phone better than theirs.
In franco kernel manager there are some settings for cpu behavior but none of them helped.
I wonder is there any possibility that unlock that power drain limit -even if there is in first place- that kernel level. I want to squeeze our chipset's full potential
just curious, why do you need that performance?
i am using emulator thats why.
[Bounty) TPD App Throttling Disablement
I'll Personally donate $50 to anyone that comes up with a easy solution to disable the app throttling. I'm well aware that some Developers can exclude the TPD commit, but it seems like devs aren't too keen on doing that. I also realize that...
forum.xda-developers.com
Orwennes said:
[Bounty) TPD App Throttling Disablement
I'll Personally donate $50 to anyone that comes up with a easy solution to disable the app throttling. I'm well aware that some Developers can exclude the TPD commit, but it seems like devs aren't too keen on doing that. I also realize that...
forum.xda-developers.com
Click to expand...
Click to collapse
This isn't related with my question.
noobzayt said:
This isn't related with my question.
Click to expand...
Click to collapse
Isn't it?
samwhiteUK said:
Isn't it?
Click to expand...
Click to collapse
Isn't that obvious that i am not talking about app specific throttling but power limit throttle like laptop cpus.
noobzayt said:
Isn't that obvious that i am not talking about app specific throttling but power limit throttle like laptop cpus.
Click to expand...
Click to collapse
How do you know which the phone is doing?
samwhiteUK said:
How do you know which the phone is doing?
Click to expand...
Click to collapse
Because chipset constantly behaves like i mentioned regardless which app is running. So i know this thing isn't related with app spesific.
noobzayt said:
i am using emulator thats why.
Click to expand...
Click to collapse
maybe yours phone overheating? [Bounty) TPD App Throttling Disablement works for me perfect, even on hard encoding tasks, just keeping my phone cool
Related
Is it possible, and how?
yes how to overclock more than that, it seems stuck on 1267mhz
yansen78 said:
yes how to overclock more than that, it seems stuck on 1267mhz
Click to expand...
Click to collapse
infexis said:
Is it possible, and how?
Click to expand...
Click to collapse
seriously.. kids you don't want to do that, Overclocking makes heat, heat makes phone melt!
Phone arent cooling geniuses
doable yes
advisable no
ab i think you need to add vales int he kernel then add the values to the setcpu.txt
just add
, 1300000 to the end of setcpu.txt and whatever u want above that
it has to be enabled in the kernel for it to work in setcpu or anything, it has been tested by Richardtrip and unfortunately it didn't work out -- don't think there is any point just yet anyway.
StrongOneX said:
seriously.. kids you don't want to do that, Overclocking makes heat, heat makes phone melt!
Phone arent cooling geniuses
Click to expand...
Click to collapse
maybe he live on nort pole,& have extrime cooling
yes how to overclock more than that, it seems stuck on 1267mhz
Click to expand...
Click to collapse
Is it possible, and how?
Click to expand...
Click to collapse
seriously.. kids you don't want to do that, Overclocking makes heat, heat makes phone melt!
Phone arent cooling geniuses
Click to expand...
Click to collapse
CPU seems to stay cool enough. Its the battery that causes the most heat on the desire. Just push the voltage a little bit more then try to hit 1.4ghz. Yes its going to be a massive drian on the battery, but it would be fun for people that wants to beat everyone's benchmarking scores I don't recommend useing the overvolt for too long tho.
-------------------------------------
Sent via the XDA Tapatalk App
I get having it be higher than necessary to avoid bugs... but the 153mhz CORE slot can go to 90mV down from 8-900. That's 1/10th of the original voltage. Why would Google/Samsung ship it using so much more than what it needs?
Hungry Man said:
I get having it be higher than necessary to avoid bugs... but the 153mhz CORE slot can go to 90mV down from 8-900. That's 1/10th of the original voltage. Why would Google/Samsung ship it using so much more than what it needs?
Click to expand...
Click to collapse
Those are MAX voltages...and I call hogwash on the 90mV, unless you are disabling smart reflex. Then I would want to see some actual proof.
Lower than 70mV is unstable. I didn't disable smartreflex, but even if I do it makes no difference. Maybe someone else can share their lowest voltage for this. I'm sure I'm undervolting it as it becomes quite unstable if I input 60mV, so obviously something's happening.
Yes, they're max voltages, but even with SR it doesn't go below 886 or something.
I find that tough to swallow. Did you actually verify the voltage with a kernel log?
What's the easiest way to do that? I'd like to confirm it myself. Like I said, I know it's doing something because at 50-60mV there are instant issues.
Hungry Man said:
What's the easiest way to do that? I'd like to confirm it myself. Like I said, I know it's doing something because at 50-60mV there are instant issues.
Click to expand...
Click to collapse
If memory serves, dmesg will log it.
Yikes. A lot of output and no 'grep'. Give me a minute.
Hungry Man said:
Lower than 70mV is unstable. I didn't disable smartreflex, but even if I do it makes no difference. Maybe someone else can share their lowest voltage for this. I'm sure I'm undervolting it as it becomes quite unstable if I input 60mV, so obviously something's happening.
Yes, they're max voltages, but even with SR it doesn't go below 886 or something.
Click to expand...
Click to collapse
You have to disable smart reflex for your voltage settings to work. It isn't going down to 90mv. Disable smart reflex and then set that, I doubt your phone will run.
Voltage Nominal=75000, Calib=75---, margin=38000
Seems to be the most relevant. And yeah, I've got it at 75 right now.
And I've disabled SR as well, it doesn't change anything. And the voltage settings definitely do work witohut disabling it as, like I said, going too far down will cause a crash. So obviously it's doing something.
Have you guys tried undervolting that far?
And I'm doing this with franco kernel updater. The widget is showing the Core voltage to be 75.
Hungry Man said:
Voltage Nominal=75000, Calib=75---, margin=38000
Seems to be the most relevant. And yeah, I've got it at 75 right now.
And I've disabled SR as well, it doesn't change anything. And the voltage settings definitely do work witohut disabling it as, like I said, going too far down will cause a crash. So obviously it's doing something.
Have you guys tried undervolting that far?
And I'm doing this with franco kernel updater. The widget is showing the Core voltage to be 75.
Click to expand...
Click to collapse
thats 900mV and 750mV. and there is a large variation between individual devices. some can handle much less and some cant handle a tiny bit less. but undervolting too much will end up using more battery to achieve what it needs to achieve from working longer/harder to get there. 90mV without or even with smart relex will cause your phone to freeze then reboot.
but undervolting too much will end up using more battery to achieve what it needs to achieve from working longer/harder to get there
Click to expand...
Click to collapse
Why? I know that underclocking would do this - the time to finish a task at a lower clockspeed is longer.
I don't see how lowering the mV can possibly increase battery usage.
90mV without or even with smart relex will cause your phone to freeze then reboot.
Click to expand...
Click to collapse
But mine isn't freezing until I put it at 60-70,V.
thats 900mV and 750mV
Click to expand...
Click to collapse
Not according to the app.
Hopefully this attached a screenshot.
Hungry Man said:
Hopefully this attached a screenshot.
Click to expand...
Click to collapse
no, you are right. i didnt see that you mentioned core. after looking at the original post i see the core now. anyways, at that low a voltage it will operate, but wont be fully functional.
---------- Post added at 11:11 PM ---------- Previous post was at 10:53 PM ----------
anyways, i dont know what that app is reporting, but franco kernel can only be set to a minimum of 830mV. looks like a mistake or a bug in his app. im gonna email him.. https://bitbucket.org/franciscofran...e9aa9b26/arch/arm/mach-omap2/voltage.h#cl-184
It seems functional... I mean, clearly the GPU is working (and at that voltage according to the app) because the screen is on/ not artifacting.
Is it just incorrectly reporting it? Is there another way to confirm it? Dmesg was not clear.
Hungry Man said:
It seems functional... I mean, clearly the GPU is working (and at that voltage according to the app) because the screen is on/ not artifacting.
Click to expand...
Click to collapse
check the link out that i just posted. franco kernel can only be set to a minimum of 830mV, the app is reporting wrong. its setting, but not actually setting https://bitbucket.org/franciscofran...e9aa9b26/arch/arm/mach-omap2/voltage.h#cl-184
So what is it actually setting it to? Because if I set it *too* low it still does give me errors... so how can it be both?
Hungry Man said:
So what is it actually setting it to? Because if I set it *too* low it still does give me errors... so how can it be both?
Click to expand...
Click to collapse
i think it gets set to 830. i let francisco know, we'll see what he says.
Alright. It's just weird. Because if anything under 830 is setting it to 830, and 830 is stable (because 95 shows stable) than how would 830 be unstable when the UI shows it as 40.
I mean, 90mV is kinda insane. It would definitely make sense if it were more like 830. It's just confusing.
Hopefully francisco can explain.
simms22 said:
check the link out that i just posted. franco kernel can only be set to a minimum of 830mV, the app is reporting wrong. its setting, but not actually setting https://bitbucket.org/franciscofran...e9aa9b26/arch/arm/mach-omap2/voltage.h#cl-184
Click to expand...
Click to collapse
Hmm, then why does setting an absurd voltage like 200mV cause an instant reboot while I can set it to 830mV and it runs fine?
Sent from my Galaxy Nexus using Tapatalk 2
Yeah I can set it to 830mV and it runes fine. No issues until I drop to 60mV. I haven't reached a limit for any of them.
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
tpike1296 said:
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
Click to expand...
Click to collapse
Depends on the kernel too. Some phones will be better to support higher speeds than others.
tpike1296 said:
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
Click to expand...
Click to collapse
I've gone up to 2106MHz with @ktoonsez kernel using the default voltages, I was also able to undervolt too.
Edit, some differences in the manufacturing causes each phone to be different. What works with one phone might not work with another. My point: some phones can't be over clocked passed a certain point. My E4GT couldn't go pass 1.5GHz no matter what I did.
Second edit: why do you want / feel the need to overclock this phone?
Aaron Swartz, Rest in Pixels.
jamcar said:
I've gone up to 2106MHz with @ktoonsez kernel using the default voltages, I was also able to undervolt too.
Edit, some differences in the manufacturing causes each phone to be different. What works with one phone might not work with another. My point: some phones can't be over clocked passed a certain point. My E4GT couldn't go pass 1.5GHz no matter what I did.
Second edit: why do you want / feel the need to overclock this phone?
Aaron Swartz, Rest in Pixels.
Click to expand...
Click to collapse
I haven't felt the need, currently running BMS kernel-asswax gov. Superb battery life.
Sent from my hybrid GalaxyS3
joeyhdownsouth said:
I haven't felt the need, currently running BMS kernel-asswax gov. Superb battery life.
Sent from my hybrid GalaxyS3
Click to expand...
Click to collapse
I haven't either, with this phone, other than to do a benchmark and to say I could. I'm just wondering why the OP feels the needs.
Aaron Swartz, Rest in Pixels.
tpike1296 said:
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
Click to expand...
Click to collapse
You could try raising your voltages alittle
Sent from my SPH-L710 using xda premium
If you are in TW, search ziggy's in Google.
infected with the unspeakable
Yeah, I suggest you look up "CPU binning" and see what you have as not all processors can handle the same things, and you can seriously damage your phone by overclocking too high or something similar.
jamcar said:
I've gone up to 2106MHz with @ktoonsez kernel using the default voltages, I was also able to undervolt too.
Edit, some differences in the manufacturing causes each phone to be different. What works with one phone might not work with another. My point: some phones can't be over clocked passed a certain point. My E4GT couldn't go pass 1.5GHz no matter what I did.
Second edit: why do you want / feel the need to overclock this phone?
Aaron Swartz, Rest in Pixels.
Click to expand...
Click to collapse
The only real reason I wanted to overclock was to say that I could (and do some benchmarks). Curiosity, mainly. I've since realized that even going to 1728Mhz has proven fairly useless except if I want to reduce battery life, or get a *tiny* boost when emulating the N64. Thank you for the explanation of why it most likely wouldn't work. Seems I always get devices that don't really like overclocking, as my HTC EVO 4G didn't seem to like more than a tiny boost, either.
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:
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?