Related
Hey XDA friends,
I was testing my One today with some intense gaming and benchmarking. I noticed that Real Racing 3 was slowing down after some time of gaming. So I ran Antutu before and after my gaming session. My score before: 24567, my score after 20 minutes of Real Racing 3: 19945 !
Especially the GPU score was significantly lower in the second test. It seems that the One is throttling speed when reaching defined temperatures. There is a thermald.conf in /system/etc , but impossible for me to read out. A modified thermald.conf or a custom kernel should sort that out!
Sent from my HTC One using xda app-developers app
more2come said:
Hey XDA friends,
I was testing my One today with some intense gaming and benchmarking. I noticed that Real Racing 3 was slowing down after some time of gaming. So I ran Antutu before and after my gaming session. My score before: 24567, my score after 20 minutes of Real Racing 3: 19945 !
Especially the GPU score was significantly lower in the second test. It seems that the One is throttling speed when reaching defined temperatures. There is a thermald.conf in /system/etc , but impossible for me to read out. A modified thermald.conf or a custom kernel should sort that out!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Mh.. we had a guys that ran a lot of taiji basemark runs (loop) and had no problem with throttling. Maybe Taiji is gpu only and real racing 2 needs gpu and cpu a lot. A bit worrying though.
Thermal throttling really is a big problem for S4 Pro. So S600 has to suffer it also, although HTC made a very thin copper cover inside for reducing the heat.
shox22 said:
Mh.. we had a guys that ran a lot of taiji basemark runs (loop) and had no problem with throttling. Maybe Taiji is gpu only and real racing 2 needs gpu and cpu a lot. A bit worrying though.
Click to expand...
Click to collapse
GPU tests don't make a significant stress on the system. The thermal throttling happens mostly when both CPU and GPU reaching the limit.
That's too bad... :-/
My Nexus 4 really suffered from thermal throttling, too. But a custom kernel by Franco with lowered voltages and a newly written thermal handling routine sorted that out, the SoC didn't become too hot and didn't throttle at all!
Can someone try running Stability Test (cpu+gpu test) to see at what temperature is throtled?
Re: HTC Flagship 2013 - HTC One - Qualcomm® Snapdragon™ 600 - Mega Information Thread
May be an isolated issue and not with all devices?
more2come said:
Hey XDA friends,
I was testing my One today with some intense gaming and benchmarking. I noticed that Real Racing 3 was slowing down after some time of gaming. So I ran Antutu before and after my gaming session. My score before: 24567, my score after 20 minutes of Real Racing 3: 19945 !
Especially the GPU score was significantly lower in the second test. It seems that the One is throttling speed when reaching defined temperatures. There is a thermald.conf in /system/etc , but impossible for me to read out. A modified thermald.conf or a custom kernel should sort that out!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Sent from my Windows 8 device using Board Express
I can hardly believe that this is an isolated issue! I'm pretty sure that the S600 has the same temperature handling routines as the S4 Pro. The presence of a thermald.conf in /system/etc/ shows that there are defined parameters for SoC throttling to protect the device.
If you're willing to test that, just give Real Racing 3 a go for about 30 minutes and run Antutu directly afterwards. Or run stability test for longer periods of time.
If this is the case, you would have thought Qualcomm would have at least attempted to sort out the thermal issue as seen in some S4 Pro handsets!.
more2come said:
I can hardly believe that this is an isolated issue! I'm pretty sure that the S600 has the same temperature handling routines as the S4 Pro. The presence of a thermald.conf in /system/etc/ shows that there are defined parameters for SoC throttling to protect the device.
If you're willing to test that, just give Real Racing 3 a go for about 30 minutes and run Antutu directly afterwards. Or run stability test for longer periods of time.
Click to expand...
Click to collapse
I did what did you ask there is not really difference in Antutu result, before and after, both above 22K.
I played around 25 minutes of RR3
Sent from my HTC One using Tapatalk 2
@MrKaon
Are you on some custom ROM?
No m8 Stock
Sent from my HTC One using Tapatalk 2
MrKaon said:
No m8 Stock
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Thanks, that and your signature were very helpful! My stock firmware was from O2 Germany which is reportedly older than the most recent stock EU firmware. I flashed mike's Revolution ROM right now which has a newer firmware base and possibly a newer kernel. Thermal throttling doesn't happen on Revolution HD!
more2come said:
Thanks, that and your signature were very helpful! My stock firmware was from O2 Germany which is reportedly older than the most recent stock EU firmware. I flashed mike's Revolution ROM right now which has a newer firmware base and possibly a newer kernel. Thermal throttling doesn't happen on Revolution HD!
Click to expand...
Click to collapse
Well that's reckless and dangerous.
There is thermal throttling for a reason, and it's set very aggressively for a reason.
Hunt3r.j2 said:
Well that's reckless and dangerous.
There is thermal throttling for a reason, and it's set very aggressively for a reason.
Click to expand...
Click to collapse
Thermal throttling didnt steped in - but that doesnt mean that thermal throlltling isnt there. The change could come from the update to 1.28 (new driver for example). The same happened on the one x last year. There was an update that significantly reduced heat.
shox22 said:
Thermal throttling didnt steped in - but that doesnt mean that thermal throlltling isnt there. The change could come from the update to 1.28 (new driver for example). The same happened on the one x last year. There was an update that significantly reduced heat.
Click to expand...
Click to collapse
It gets a little less hot on the backside with the newer firmware base, I can confirm that.
it gets hot, it throttles. it's a safety measure. why do u complain?
so u want your phone to breach the heat threshold then the chip dies and then u're gonna say htc one sucks becoz components die?
shiningarmor said:
it gets hot, it throttles. it's a safety measure. why do u complain?
so u want your phone to breach the heat threshold then the chip dies and then u're gonna say htc one sucks becoz components die?
Click to expand...
Click to collapse
Of course it's a safety measure, but in my opinion a smartphone shouldn't throttle due to normal usage. If the circumstances are abnormal (very hot summer temperatures, for example), throttling is okay and I'd welcome that to protect my valuable HTC. But while playing a game?
But there's no further reason for me to complain, because the newest firmware runs cool enough without throttling.
so in the latest firmware its not throttling? can you add this info to your OP?
What is the latest firmware? Is there a published changelog and do I need to go back to stock to get at it?
Sent from my Tricked out HTC One via xda-developers application
Tetsumi06 said:
What is the latest firmware? Is there a published changelog and do I need to go back to stock to get at it?
Sent from my Tricked out HTC One via xda-developers application
Click to expand...
Click to collapse
latest should be 1.29
Please, after reading my post, don't blame me or suggest things like "mobile devices aren't meant to play or aren't meant to replace pc", I'm not looking for surrender, I'm looking for advices or proposals.
Several times I've noticed Thermal Throttling (from now TT ) effects on our device, because during high-resource-demanding apps, for example Real Racing 3 (but everyone can have his own high-resource-demanding app example), TT decreases cpu frequencies (maybe gpu too?) when it reaches a certain temperature, causing framerate drop. With cool-phone RR3 has superb framerate, but when phone becomes hot (after 6-7 minutes), there's a noticeable framerate drop caused by TT. You can notice this just by watching at asphalt flow under the car or how trees move in the environment.
This is normal, TT is normal and good beacuse it prevents high-temp damage, "but" I think that LG (or qualcomm or android) has implemented this function in a wrong way, not optimal. If this effect is so significant, it means that cpu frequencies cut is too much! I think it cuts in "half" cpu frequency, but it's a very conservative behaviuor, it's too much! If we consider another device, for example 4-cores clocked at 1,2 GHz, this device won't have 50 fps as G2 (in first minutes), maybe it will have 40 fps all the time, but it won't throttle down; G2 instead will throttle down and framerate will drop to 25 fps, which is not optimal, until it will cool (when stop playing, because it won't cool during playing). If these two devices were two cars, slower car would be the fastest because it will be constant and have best lap times.
First of all, there's a "normal" hardware problem that involves cooling and this problem can't be faced. But it's a software problem too, in the way TT is tuned; TT setting is what we shall deal with.
How can we achive this? There are several ideas:
1) Reading through forums I read about two possibile secret menu settings (3845#*802# ... 802 is phone model):
a) Thermal mitigation daemon off: this value should affect screen light dimming to lower temp, but it's not something that can slow down fps;
I tried it but my phone rebooted after 5 minutes playing and went into bootloop...
b) High temperature priority off: this value should affect TT temperature start treshold, for example increasing it from 60°C to 70°C, that is still a safe (internal) temp; I noticed a decreased TT effect, but it doesn't disappear. It simply happens after more time (for example after 10 minutes instead of 5). It's not a ultimate solution;
2a) Lowering max cpu freq to a value that prevents reaching TT treshold; but it depends also on environment temp, we should make too much tries; can someone say what max cpu freq to set? Obviously not to low... if 1.8 GHz it's good, if 1.4 GHz it will be better sell G2 and buy a less hardware performant nexus 4, but in real life better in performance than G2 because N4 can be less affected by TT;
2b) Lowering voltages, same as 2a), it's very difficult and we won't be sure to solve the problem;
3) There are several system files ( http://forum.xda-developers.com/showthread.php?t=2472318&page=43 ) that can be involved in TT tuning... Very difficult to achieve...
4) If TT can be tuned by kernel, a custom kernel with better TT tuning... hoping in a dev. (I think this would be the best solution).
What do you think about?
titomax82 said:
4) If TT can be tuned by kernel, a custom kernel with better TT tuning... hoping in a dev. (I think this would be the best solution).
What do you think about?
Click to expand...
Click to collapse
That you did not do your research? I am not sure where you are headed at, but check our this DEV for example.
http://forum.xda-developers.com/showthread.php?t=2725023
PAGOT said:
That you did not do your research? I am not sure where you are headed at, but check our this DEV for example.
http://forum.xda-developers.com/showthread.php?t=2725023
Click to expand...
Click to collapse
Do you mean this "Support Inteli CPU Temp control (by @faux123)" in "whats inside"? Is this what I'm looking for in 4)?
titomax82 said:
Do you mean this "Support Inteli CPU Temp control (by @faux123)" in "whats inside"? Is this what I'm looking for in 4)?
Click to expand...
Click to collapse
You have to test. But almost all custom kernels are pretty much tweakable to your loving. Anyway depends on which device and Android version you are. Check carefully that you are not with a brick in the end.
Sent from my LG-D802 using Tapatalk
PAGOT said:
You have to test. But almost all custom kernels are pretty much tweakable to your loving. Anyway depends on which device and Android version you are. Check carefully that you are not with a brick in the end.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I'm not expert in tweaking...
Well all I'm gonna say is I'm a huge gamer, I own multiple consoles and am into pc gaming and I've been doing some gaming on my g2 and here is a list of games I play gta 3/San Andreas, dungeon Hunter and I play psp games and most demanding of all I play dolphin emulator (GameCube games) and out of all the them the only one I can't play for more than 35 mins is dolphin because it's too cpu intensive(after 40mins fps goes down and at about an hour the phone might reboot itself it's happened before) and my phone is all stock(because dorimanx kk kernel is not completely stable yet)
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
Well all I'm gonna say is I'm a huge gamer, I own multiple consoles and am into pc gaming and I've been doing some gaming on my g2 and here is a list of games I play gta 3/San Andreas, dungeon Hunter and I play psp games and most demanding of all I play dolphin emulator (GameCube games) and out of all the them the only one I can't play for more than 35 mins is dolphin because it's too cpu intensive(after 40mins fps goes down and at about an hour the phone might reboot itself it's happened before) and my phone is all stock(because dorimanx kk kernel is not completely stable yet)
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
I tried 2 kernels:
1) Dorimanx 4.4: too much options to set... with default installation G2 is slower in antutu and in gaming...
2) Simple Kernel V5 (No Oc version): wonderful with default installation, phone becomes a little bit hotter than custom kernel, but no TT! Very Good! Also, I can revert "High Temperature Priority OFF" to its default setting (OFF): phone becomes slightly cooler and TT becomes barely noticeable. TT can be still considered solved, with temperature and battery benefits.
Update
All the changes I made were merged into CoCore-refresh kernel (3.0.31) and 3.0.101 by TeamCanjica, so they will hit 'mainstream' in some time when they release another build.
This thread is over
/Update
Hi,
I've been working on this kernel for some time with improving undervolting in mind. It's based on CoCore Refresh r10 by CoCafe and of course the credit goes to him where it's due.
Main changes:
- rewritten liveOPP internals.
It improved stability a lot - it now allows to use 300/500/700/900 MHz frequencies with no problem and it allows to undervolt low frequencies even more. Freqs >1GHz are now stable at varm=0x32 (at least on my phone), which also saves a lot of power.
Freqs <=400 MHz now use 0x12 (0.925V) voltage by default - It's the original voltage for 400MHz and you can go even lower when undervolting
- rewritten Mali booster algorithm.
It's far from perfect yet, but it eliminated instability due to the fact, that CoCafe's mali booster and "original" booster (switching between APE 50/100 OPP) were working independently and could cause a crash when the original algorithm switched to APE_50_OPP while mali boost was active. APE_50_OPP voltage is 1V by default (0x18), so when clock is boosted to i.e. 700MHz and it switched to 50 OPP, the result was 350MHz @ 1V, which mihgt be too low.
- allow to set APE and DDR OPP with liveOPP
echo apeopp=25/50/100 > arm_stepXX and echo ddropp=...
before the kernel would set ape/ddr opp to 100 for freqs above 400MHz
- allow changing ape_50_opp voltage
echo 0xXX > /sys/kernel/mali/mali_gpu_vape_50_opp
- make wlan/mmc boost tunables available through sysfs in /sys/kernel/performance/*
- Memory split changed to 2G/2G and switch highmem off - it's not needed with this split
- removed some unnecessary drivers and moved others to modules to reduce kernel size
- changed kernel compression to LZO
- 631MB available memory
- 7800ms kernel boot time
Download & install:
Mediafire
That's partition image - flash it with dd:
Code:
dd if=kernel.mk-r1-release.img of=/dev/block/mmcblk0p15
It's also good to create a symlink from /system/lib/modules to /lib/modules - it'll allow modules to autoload, enable modprobe to work and also you can use KoControl app to manage module loading.
Source:
GitHub
TODO:
- create a package for flashing with recovery and place modules (7MB) in /system/lib/modules instead of a ramdisk
- touchbooster has a bug that causes it to limit max freq to 1000MHz on boost.
- figure out how to enable setting of minimal cpu freq - now touchboost always resets it to 100MHz
- add interactive gov from Zwliew kernel
- create more power optimized, auto tuning 'foreground' governor (long story)
My voltage settings
(default kernel voltages are more conservative - set those from init scripts and test them for stability!):
100 - 0x0f
200 - 0x10
300 - 0x11
400 - 0x12
500 - 0x14
600 - 0x18
700 - 0x1d
800 - 0x24
900 - 0x28
1000 - 0x2f
1050..1250 - 0x32
Mali gpu voltage
Default voltage from CoCafe is way too high - idx0 vape could be just 1V since that's the voltage, when mali is running at 1/2 speed (200MHz by default).
My settings (for safety they are 3 steps higher than the lowest working voltage for given freq).
#0 - 0x17
#5 - 0x1c
#9 - 0x23
I don't overclock the gpu - my low index is set to 0 (200MHz), and hi (boosted) to 5(400MHz), which is the original mali freq. That gives mi 100MHz when working at half speed. I don't use any fancy UI effects, so it's enough - when not plaing a game, mali is only working at 100/200MHz and only boosts when loaded. Params:
boost_low idx=0
boost_low threshold=30
boost_delay 2000
boost_high idx=5
boost_high threshold=220
Default kernel settings are left unchanged - set those manually from init scripts.
I place the thread here because I'm not allowed to post in developer forums (<10 messages limit).
MK
Wow. Thanks for your work, mate!
Most people are using CM or CM/AOSP based ROMs nowadays, but there are only a few people (like me) who still use Jellybean. So, I'll try your kernel very soon and I'll post a review after using it.
You joined XDA on 2010 and yet, this is your first post. That just doesn't feel right.. Anyways, keep up the good work, mate. :good:
Good to see another kernel developer for our phone! I'm on stock rom now, I will try it out
Sami Kabir;5571pro. [B said:
Wow. Thanks for your work, mate! [/B]
Most people are using CM or CM/AOSP based ROMs nowadays, but there are only a few people (like me) who still use Jellybean. So, I'll try your kernel very soon and I'll post a review after( using it.
Click to expand...
Click to collapse
The code is on github and there's no problem with merging it with some cm kernel. When I'll try my with some 4.4 again (so far each one had something broken and didn't suit me), I'll probably do it
You joined XDA on 2010 and yet, this is your first post. That just doesn't feel right.. Anyways, keep up the good work, mate. :good:
Click to expand...
Click to collapse
To keep it short let just say that I'm not a sociable type of guy... but when I have something of value, I try to share...
One more thing (most probably know it, but for those who don't) - 99% of "user experience" depends on the settings of governor, mali and touch booster - if you screw this up, no kernel will work smoothly. I had this problem with my first vanilla jb - it sucked as hell(ondemand), but when I set sampling_down_factor to 3-4 suddenly it was very smooth. Default gov params aren't always the best. Thats one of the reasons I'll try to write a governor that tunes itself and adjusts itself to the app currently in foreground - but that's just an idea and it'll take me some time to refresh all the math needed for it...
Anyway - enjoy the kernel.
Hmm I really wanna test this kernel, but I'm currently on Vanir
I definitely gonna follow your thread, it's good to know Janice is still alive and kicking
Reinkaos said:
Hmm I really wanna test this kernel, but I'm currently on Vanir
I definitely gonna follow your thread, it's good to know Janice is still alive and kicking
Click to expand...
Click to collapse
You can always ask rom's devs to merge my changes - it's just a few commits.
And how is that rom working for you? At the time I was checking up 4.4 roms each one of them sucked in a different way. Carbon was the closest (in fact it was the only one acceptable) to being useful (feature- and ui-wise), but it had some process spinning in the background and It was draining my batt (it was unkillable because it was a part of lock screen I think - the bug was known, but no fix available at that time).
If it's similar to carbon I might give it a try...
mkaluza said:
You can always ask rom's devs to merge my changes - it's just a few commits.
And how is that rom working for you? At the time I was checking up 4.4 roms each one of them sucked in a different way. Carbon was the closest (in fact it was the only one acceptable) to being useful (feature- and ui-wise), but it had some process spinning in the background and It was draining my batt (it was unkillable because it was a part of lock screen I think - the bug was known, but no fix available at that time).
If it's similar to carbon I might give it a try...
Click to expand...
Click to collapse
Well I use to be a Carbon die-hard fan before, but since the dev have got himself another device, so I just had to change rom.
And then I try Vanir. Surprisingly it's pretty stable, and we have official support by the Vanir team too.
Feature-wise its just as good as Carbon, but I kinda miss the pie, since Vanir doesn't have it.
And I think Vanir have a bit more features than Carbon do.
Anyway can you go lower than those cpu voltage on your OP? Or is it really not stable?
Mine's 1000 is at 0x2c, 800 at 0x20, and that's the lowest I can go.
And thanks for the gpu voltage :good: , I actually use that value now :laugh:
aioreu the
Reinkaos said:
Well I use to be a Carbon die-hard fan before, but since the dev have got himself another device, so I just had to change rom.
Click to expand...
Click to collapse
It's a pity... but I understand that's only the S Advance branch of Carbon thats dead - the rom itself is being developed further?
And then I try Vanir. Surprisingly it's pretty stable, and we have official support by the Vanir team too.
Feature-wise its just as good as Carbon, but I kinda miss the pie, since Vanir doesn't have it.
And I think Vanir have a bit more features than Carbon do.
Click to expand...
Click to collapse
I didn't like the pie ;P But if you say it's ok, I'll give it a try when I'm in the mood to reinstall everything on the phone...
Anyway can you go lower than those cpu voltage on your OP? Or is it really not stable?
Mine's 1000 is at 0x2c, 800 at 0x20, and that's the lowest I can go.
Click to expand...
Click to collapse
Actually I didn't recheck those two and focused on lower freqs - these were the limits with older LiveOPP, but now I can go to 0x22 and 0x2c.
In fact, 0x24 and 0x2f are already undervolted values - original are 0x28 and 0x32. But every bit counts, especially on higher freqs.
Thanks for the tip
But what's more interesting - 900MHz works at 0x23 (didn't test that before - just took a voltage halfway between 800 and 1000)... there's something wrong with this ARM_100_OPP, but I don't know what yet... Will test the rest again later and post my results.
And thanks for the gpu voltage :good: , I actually use that value now :laugh:
Click to expand...
Click to collapse
Your welcome
When I have time, I'll try to write how to quickly check undervolting limits for both cpu and gpu.
Mk
mkaluza said:
It's a pity... but I understand that's only the S Advance branch of Carbon thats dead - the rom itself is being developed further?
Click to expand...
Click to collapse
Yes, only for our device. It's not really dead yet.
The dev has been kind enough compiling new one once in a while.
I didn't like the pie ;P But if you say it's ok, I'll give it a try when I'm in the mood to reinstall everything on the phone...
Click to expand...
Click to collapse
Yeah, I could understand that. Too much of a hassle. Got to reinstall everything back again.
But you know, I always do clean flash, even with nightlies. Imagine backing up, factory reset and restoring everything in every 3-4 days.
But now I get really used to it
Actually I didn't recheck those two and focused on lower freqs - these were the limits with older LiveOPP, but now I can go to 0x22 and 0x2c.
In fact, 0x24 and 0x2f are already undervolted values - original are 0x28 and 0x32. But every bit counts, especially on higher freqs.
Thanks for the tip
But what's more interesting - 900MHz works at 0x23 (didn't test that before - just took a voltage halfway between 800 and 1000)... there's something wrong with this ARM_100_OPP, but I don't know what yet... Will test the rest again later and post my results.
Click to expand...
Click to collapse
No problem man, thought that information would be useful to you.
Yeah, it would be really nice to go lower, especially on 1000 and 800.
I'm gonna test the rest, and later I would let you know the lowest working voltage that I can go.
And honestly, I have no idea about kernel stuffs :silly: The least that I can do is to play around with it
Your welcome
When I have time, I'll try to write how to quickly check undervolting limits for both cpu and gpu.
Mk
Click to expand...
Click to collapse
Yes, please do. I would really appreciate that :fingers-crossed:
Reinkaos said:
Yes, only for our device. It's not really dead yet.
The dev has been kind enough compiling new one once in a while.
Click to expand...
Click to collapse
He also left a repo with build scripts and manual, so I'll try to build the rom.
Yeah, I could understand that. Too much of a hassle. Got to reinstall everything back again.
But you know, I always do clean flash, even with nightlies. Imagine backing up, factory reset and restoring everything in every 3-4 days.
But now I get really used to it
Click to expand...
Click to collapse
That's hardcore ;P I have patience to do it 1-2 times a year
Yeah, it would be really nice to go lower, especially on 1000 and 800.
I'm gonna test the rest, and later I would let you know the lowest working voltage that I can go.
Click to expand...
Click to collapse
mine crashed at 1000MHz/0x2c - I'm on 0x2d now and it seems ok
And honestly, I have no idea about kernel stuffs :silly: The least that I can do is to play around with it
Click to expand...
Click to collapse
You could always learn It's fun, all the info is there to read for free... all it takes is will and time
Yes, please do. I would really appreciate that :fingers-crossed:
Click to expand...
Click to collapse
I still cant post links, so you need to go to my github (mkaluza), open the i9070_kernel_CoCore-E repo and go to wiki on the right - there is a page "Undervolting janice". Hope this helps.
Mk
mkaluza said:
He also left a repo with build scripts and manual, so I'll try to build the rom.
Click to expand...
Click to collapse
Well that's a good news :good:
That's hardcore ;P I have patience to do it 1-2 times a year
Click to expand...
Click to collapse
LOL yeah
mine crashed at 1000MHz/0x2c - I'm on 0x2d now and it seems ok
Click to expand...
Click to collapse
I'm not sure if mine is really stable, gonna test it with your guide on github
You could always learn It's fun, all the info is there to read for free... all it takes is will and time
Click to expand...
Click to collapse
Yeah, I am learning right now
I still cant post links, so you need to go to my github (mkaluza), open the i9070_kernel_CoCore-E repo and go to wiki on the right - there is a page "Undervolting janice". Hope this helps.
Mk
Click to expand...
Click to collapse
So there are scripts that will provide me with some infos when doing UV-ing
And I'm not familiar with registers though, I only do it via liveopp, but still I'll try this
Thanks for the guide
Anyway I got a question about gpu, lets say my mali low_boost is 400 and high_boost is 480,
does it use the two freq only or it use the other freq in between 400 and 480 too?
P.S. hey you could just spam in OT threads to get 10 posts
Reinkaos said:
I'm not sure if mine is really stable, gonna test it with your guide on github
Click to expand...
Click to collapse
If you don't get random reboots/crashes than it is - when following my guide, the resulting voltage should be stable, but it isn't always so... I'ts just a starting point that can save you some initial crashes or the other way around - if it doesn't pass freq_jump test, then it isn't stable for sure
Anyway I got a question about gpu, lets say my mali low_boost is 400 and high_boost is 480,
does it use the two freq only or it use the other freq in between 400 and 480 too?
Click to expand...
Click to collapse
Only those two - three actually - also 200MHz (that is low_boost/2), but with ape_50_opp voltage, not the one from dvfs_config. There's not much point in doing any smarter gov because gpu intensive apps usually load it at 100% no matter how much power it has - they just have more fps then.
.P.S. hey you could just spam in OT threads to get 10 posts
Click to expand...
Click to collapse
Yeah, maybe, but if those are the rules, then I try to respect them - because I respect the community. (not because I'm some kind of by-the-book guy ;P I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
mkaluza said:
I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
Click to expand...
Click to collapse
You like adrenaline, heh
PS: Sorry for OT
mkaluza said:
If you don't get random reboots/crashes than it is - when following my guide, the resulting voltage should be stable, but it isn't always so... I'ts just a starting point that can save you some initial crashes or the other way around - if it doesn't pass freq_jump test, then it isn't stable for sure
Click to expand...
Click to collapse
Hey, just letting you know, about opptop script, we don't have prcmu-qos folder in /debug. I thought maybe it have a different name, but I couldn't find ape_requirements and ddr_requirements. The others are working fine
Only those two - three actually - also 200MHz (that is low_boost/2), but with ape_50_opp voltage, not the one from dvfs_config. There's not much point in doing any smarter gov because gpu intensive apps usually load it at 100% no matter how much power it has - they just have more fps then.
Click to expand...
Click to collapse
Thanks for the infos :good:
Yeah, maybe, but if those are the rules, then I try to respect them - because I respect the community. (not because I'm some kind of by-the-book guy ;P I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
Click to expand...
Click to collapse
LOL, I'm curious though, what bike do yo own? Must be a real badass one
Force said:
You like adrenaline, heh
PS: Sorry for OT
Click to expand...
Click to collapse
I'ts more about freedom and versatility, but yeah sometimes I like to push it too
Reinkaos said:
Hey, just letting you know, about opptop script, we don't have prcmu-qos folder in /debug. I thought maybe it have a different name, but I couldn't find ape_requirements and ddr_requirements. The others are working fine
Click to expand...
Click to collapse
I forgot... this feature was written by me, so it's available only on my kernel for the moment. But it's not really that important - it was more for debugging purposes for me, now I left it as informative.
I'm trying to build Carbon rom for out phone since last night... when/if I'm done, I'll patch the kernel with my stuff and push it somewhere. What is your kernel version? I think that both carbon and vanir use the same, or at least similar one.
LOL, I'm curious though, what bike do yo own? Must be a real badass one
Click to expand...
Click to collapse
Not really I't an old BMW F650 - only 48 ponies (of which some might have already died of old age ;P). But in reality you can do most of the fun stuff with as little as 125cc Anything bigger is usefull for longer trips/highways/trips with passenger/etc... I mostly ride small country roads and light offroad, so I rarely go over 100km/h, so no badass machine is needed something like 350cc would be best I think. Actually - it's not the bike you ride, but how you ride it... and on narrow roads with many turns a bigger bike is event sometimes harder to ride...
mkaluza said:
I forgot... this feature was written by me, so it's available only on my kernel for the moment. But it's not really that important - it was more for debugging purposes for me, now I left it as informative.
I'm trying to build Carbon rom for out phone since last night... when/if I'm done, I'll patch the kernel with my stuff and push it somewhere. What is your kernel version? I think that both carbon and vanir use the same, or at least similar one.
Click to expand...
Click to collapse
Well ok then. Vanir got a 3.0.101 kernel. It's the same I think? I'll flash and test it when you're done, definitely.
Not really I't an old BMW F650 - only 48 ponies (of which some might have already died of old age ;P). But in reality you can do most of the fun stuff with as little as 125cc Anything bigger is usefull for longer trips/highways/trips with passenger/etc... I mostly ride small country roads and light offroad, so I rarely go over 100km/h, so no badass machine is needed something like 350cc would be best I think. Actually - it's not the bike you ride, but how you ride it... and on narrow roads with many turns a bigger bike is event sometimes harder to ride...
Click to expand...
Click to collapse
lol the biggest one I ever been on is about 130 cc. It's small, enough that you could squeeze through traffics
I don't know much about bike, but AFAIK those superbike need different kind of handling too.
Let's speak just about this kernel as for this is meant this thread
Please anyone tell me how to find the kernel link . I`m a noob at this part :silly: Thanks
pictorul20 said:
Please anyone tell me how to find the kernel link . I`m a noob at this part :silly: Thanks
Click to expand...
Click to collapse
Go here and see download link at top of page: https://github.com/mkaluza/i9070_kernel_CoCore-E
Download link : http://goo.gl/FvqPlg
Then check OP to see how to install it.
Force said:
Go here and see download link at top of page: https://github.com/mkaluza/i9070_kernel_CoCore-E
Download link : http://goo.gl/FvqPlg
Then check OP to see how to install it.
Click to expand...
Click to collapse
Many Thanks.
I intended to delete thermal engine to unlock the maximum performance of S810, but I didn't after a half day for thinking. Then I took a look at thermal-engine and do some optimize for it.
When I looked at the thermal-engine, I saw it use emmc_therm (temperature of emmc) sensor to do throttle, and the throttle start too soon, from 43°C, detail is two cores 6 and 7 will be hotplug (plug out, turn off), and big cluster will be limited to 1.2GHz at just 47.7°C (the battery temperature is just ~40-41°C). You can see more detail in below:
Temperature (/1000 to get the values in Celcius):
43000
47700
48900
50200
51400
52000
52600
53200
53600
54000
54500
55000
55500
55900
56300
56800
Action: cluster0+cluster1+hotplug_4+hotplug_5+hotplug_6+hotplug_7+gpu+s_backlight+battery+modem+s_cam_ltb_tim+s_cam+s_tel
1555200+1958400+0+0+1+1+630000000+255+2+0+100000+0+0
1555200+1248000+0+0+1+1+630000000+209+3+0+100000+0+0
1478400+864000+0+1+1+1+630000000+171+3+0+100000+0+0
1478400+384000+1+1+1+1+630000000+141+3+0+100000+0+0
1344000+384000+1+1+1+1+630000000+115+3+0+100000+0+0
1344000+384000+1+1+1+1+630000000+95+3+0+100000+0+0
1248000+384000+1+1+1+1+630000000+78+8+0+100000+0+0
1248000+384000+1+1+1+1+630000000+64+8+0+001800+0+0
960000+384000+1+1+1+1+630000000+52+9+0+001800+0+0
960000+384000+1+1+1+1+450000000+44+12+0+001800+0+0
864000+384000+1+1+1+1+450000000+44+12+0+001800+0+0
864000+384000+1+1+1+1+390000000+44+12+1+001800+0+0
768000+384000+1+1+1+1+390000000+44+12+1+001800+0+0
600000+384000+1+1+1+1+180000000+44+12+1+001800+0+0
460800+384000+1+1+1+1+180000000+44+12+1+001800+0+0
384000+384000+1+1+1+1+180000000+44+12+1+001800+5+0
EXPLAIN (from my knowledge, maybe it's not right at all)
cluster0: LITTLE (A53 cores) cluster clock limitation, value: hertz
cluster1: big (A57 cores) cluster clock limitation, value: hertz
hotplug_4-7: 1 to hotplug (disable) the core, 0 to do nothing.
gpu: GPU frequency, value: hertz (?)
s_backlight: the maximum brightness of screen, range: 255-0
modem: 1 to disable mobile data, 0 to do nothing.
the rest: IDK
I did a quick research and found that emmc can work from -25°C to +85C, so the limitation that Sony has set is too low (for me), just do a Geekbench and then the performance will come down clearly. Then I edit thermal-engine to increase the maximum performance of S810 but still keep my phone (IDK about yours just because we're not the same) in peace.
So why do I post here? Firstly, for those who wanna take the risk like me to unlock/get the true performance of our devices; secondly, maybe my knowledge is not right so I want you who have certain knowledge about this (EMMC, battery limitation; thermal, blah blah blah) correct me and help me and other users improve it.
I've done attached two files, one is original and the other is mine, hope you guys (who are sensei) will take a look on it to contribute for the community. For those who wanna use them, backup thermal-engine.conf first in /system/etc then copy the modify to the direction, correct name and permission and reboot.
UPDATE:
Thanks to @Envious_Data, his guide helped me to manage big cluster, now I can turn 4 big cores always on by make them becomes "non big cores", so now our phones are true octa cores. I was afraid that there're some issues that will appear such as heating, throttle (thermal manage won't work correct if it recognizes big cluster to be little cluster) so I made a test with Antutu Stress test and monitor CPU cores via Trepn Profiler, and amazing, thermel engine still works fine and my phone's temperature isn't different from old/original settings (just 1 big core on time and will be plugged in if need) so far (of course it should be hotter but not much). And I updated new thermal values too to improve some performance in camera. About battery life, I guess it would not go so far from stock settings because I saw the current discharge (mA) isn't higher (a lot).
Update 17/06: re-setting back to big cores for the best compatibility after enable all 4 big cores, so true octa cores is still there with big core setting is 1 (true).
Update 23/06: new thermal-engine to adapt with OC from SunKernel, it still works fine with stock or even any different maximum clock speed in kernel, why? Because I simply just remove "clusterX" action instead of edit it to match with the maximum clock.
INSTALL: download MODIFY files and rename to init.qcom.post_boot.sh and thermal-engine.conf (due to XDA's restriction so I have to change their type), put in /system/etc/, correct permission (644 rw-r--r--) and reboot.
UPDATING... (depend on you)
Now i try your file, my phone give 89k in antutu constantly
You tweaked it to 63°c max? Sounds not bad at all..
Gonna try as soon as I have some time!
Sent from my E6653 using XDA-Developers mobile app
Alessandro2553 said:
Now i try your file, my phone give 89k in antutu constantly
Click to expand...
Click to collapse
Try to do test continue to see the lost of performance, I just use Geekbench in my phone.
langeveld024 said:
You tweaked it to 63°c max? Sounds not bad at all..
Gonna try as soon as I have some time!
Click to expand...
Click to collapse
Actually you can see the emmc_0 and emmc_1 so the maximum is 68 Celcius and start throttle from 52.4 Celcius, at that temperature of emmc I still don't notice hot in my hand.
Sent from my E6683 using XDA Labs
@RyTekk
Interesting, but for my daily use Z5 is more than performant enough.
Why do you still want better performance ? For games ??
RyTekk said:
Try to do test continue to see the lost of performance, I just use Geekbench in my phone.
Actually you can see the emmc_0 and emmc_1 so the maximum is 68 Celcius and start throttle from 52.4 Celcius, at that temperature of emmc I still don't notice hot in my hand.
Sent from my E6683 using XDA Labs
Click to expand...
Click to collapse
And which model do you have?
nreuge said:
@RyTekk
Interesting, but for my daily use Z5 is more than performant enough.
Why do you still want better performance ? For games ??
Click to expand...
Click to collapse
I think we can also benefit from this when running heavy tasks like camera AR or 4K video.
I can feel phone slowing down after few minutes.
Sent from my E6653 using XDA-Developers mobile app
nreuge said:
@RyTekk
Interesting, but for my daily use Z5 is more than performant enough.
Why do you still want better performance ? For games ??
Click to expand...
Click to collapse
Because I got lost in performance so fast when just did install an app or play a single benchmark, I wanna unlock the highest as possible, Sony did limitation so much.
langeveld024 said:
And which model do you have?
Click to expand...
Click to collapse
E6683 dual sim variant as you see in my sign.
Sent from my E6683 using XDA Labs
Alessandro2553 said:
Now i try your file, my phone give 89k in antutu constantly
Click to expand...
Click to collapse
What kernel are you using? I've just got reboot when do Antutu bench, two times.
Androplus v30 with stock setting governor and clock speed
I have almost 84k on stock kernel. Nice
I've used this for some days now.
Was in Turkey last week (30°c) and all was fine.
In fact, performance seems much better.
I don't use benchmarks at all but I can feel multitasking is faster for a longer time and so for camera applications.
I'm now using it on 224 fw and Andro-kernel v31 and all seems good so far.
Thank you!
Sent from my E6653 using XDA-Developers mobile app
Any way to disable big cores permanently on latest firmware 32.2.a.0.224 z5 dual E6683
rajdeep312 said:
Any way to disable big cores permanently on latest firmware 32.2.a.0.224 z5 dual E6683
Click to expand...
Click to collapse
You mean thermal management for big cores?
Sent from my E6653 using XDA-Developers mobile app
langeveld024 said:
You mean thermal management for big cores?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
I want to stop big cores permanently i read somewhere big cores cause heat up device while playing games about 5 min my device burn my hand so want to reduce heat like my galaxy s7 exynos
rajdeep312 said:
I want to stop big cores permanently i read somewhere big cores cause heat up device while playing games about 5 min my device burn my hand so want to reduce heat like my galaxy s7 exynos
Click to expand...
Click to collapse
U can set it via sysfs path in init.d or su.d script, depending on what kernel u use (different paths)
Note that especially for heavy tasks u will notice performance drop when disabling these cores.
I disables two big cores and for light use it was okay but the camera app started to lag.
Sent from my E6653 using XDA-Developers mobile app
langeveld024 said:
U can set it via sysfs path in init.d or su.d script, depending on what kernel u use (different paths)
Note that especially for heavy tasks u will notice performance drop when disabling these cores.
I disables two big cores and for light use it was okay but the camera app started to lag.
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
Plz make file for me i am newbie 1. All big cores stopped and 2. Like u 2 big cores stopped
rajdeep312 said:
Plz make file for me i am newbie 1. All big cores stopped and 2. Like u 2 big cores stopped
Click to expand...
Click to collapse
I would, if I'd knew the exact sysfs path your installed kernel uses.
Are u running andro-kernel?
Sent from my E6653 using XDA-Developers mobile app
langeveld024 said:
I would, if I'd knew the exact sysfs path your installed kernel uses.
Are u running andro-kernel?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
Using this rootable kernel E6683 dual
http://forum.xda-developers.com/xperia-z5/development/32-2-0-224-ftf-rootable-kernel-t3391071
rajdeep312 said:
Using this rootable kernel E6683 dual
http://forum.xda-developers.com/xperia-z5/development/32-2-0-224-ftf-rootable-kernel-t3391071
Click to expand...
Click to collapse
Then most likely you're using core_ctl.
This thread is about minimizing thermal throttling (a.k.a wanting hotter phone, not cooler phone lol)
This is wrong thread to discuss this, head over to this thread:
http://forum.xda-developers.com/showthread.php?t=3376233
If using andro-kernel, I made a script for it, check here:
http://forum.xda-developers.com/showthread.php?t=3246100
Next time, give XDA search function a shot. It is such a nice feature, worth a try
Regards
rajdeep312 said:
Using this rootable kernel E6683 dual
http://forum.xda-developers.com/xperia-z5/development/32-2-0-224-ftf-rootable-kernel-t3391071
Click to expand...
Click to collapse
Sent from my E6653 using XDA-Developers mobile app
Thanks TS. Works pretty well so far for me (.224), and indeed the phone feels faster and more reactive under heavy load (noticed it after I finished recording a 10m 1080p60fps video). Good job
abandoned.
Can this apply on mi 11?
huycoixvb said:
Can this apply on mi 11?
Click to expand...
Click to collapse
Not exactly.
This chart is for the sd865.
Mi11 has a sd888, so the voltage levels will be different.
The basic idea is the same. But it requires testing and proofing.
Do you have source of konabess app? If possibility, send me pls :3
Thanks really useful
Great guide, this post definitely deserves more views. Got one question: if my goal frequency is (let's say) 660MHz, isn't it better to set ddr7 and ddr8 max values to 11? Would it squeeze out more performance at max load, in your opinion?
Keppo2911 said:
Great guide, this post definitely deserves more views. Got one question: if my goal frequency is (let's say) 660MHz, isn't it better to set ddr7 and ddr8 max values to 11? Would it squeeze out more performance at max load, in your opinion?
Click to expand...
Click to collapse
Not really. The ddr timings are not really set for balanced performance.
Trottling happens alot, so finding a balance give overall better performance than burst performance thatxthen gives lower results due tocthe time to cool being longer than the time to heat up.
I was able to get a higher antutu score than stock at 670, with timings between 4-9
But its all based on user preference and work loads. These settings work excellently well for me.
The big difference though is the voltage table. Less electricity going in creates less heat.
The ram timings are just a minor tweak to add a bit more to the clock. Its the voltage that really changed big time for me. Lower volts, less heat, longer time at high clocks.
Patrick Morgan said:
Not really. The ddr timings are not really set for balanced performance.
Trottling happens alot, so finding a balance give overall better performance than burst performance thatxthen gives lower results due tocthe time to cool being longer than the time to heat up.
I was able to get a higher antutu score than stock at 670, with timings between 4-9
But its all based on user preference and work loads. These settings work excellently well for me.
The big difference though is the voltage table. Less electricity going in creates less heat.
The ram timings are just a minor tweak to add a bit more to the clock. Its the voltage that really changed big time for me. Lower volts, less heat, longer time at high clocks.
Click to expand...
Click to collapse
Loud n' clear, thanks alot!
How can I edit Votages is volts table ?
Can l do this in xiaomi mi 10t pro?
yeh with any smartphone with snapdragon from 855. Just root and install konabess from GitHub and overclock and undervolt
Patrick Morgan said:
abandoned.
Click to expand...
Click to collapse
Hi Patrick, sorry to ask but you abandoned for some reason?
I have a OnePlus 9R (SNAP 870) and it's hot, I'm looking for an undervolt on it but I can't find anything, could you give me some direction?
Use this table from this post in this video.
Max freq on Poco F3 is 683Mhz you have to try if can be overclock higher but Undervolt is still possible as all phones.
I recommend new version 0.15 on two lower freq retention and min_svs or low svs on third and do like in this table so 670 voltage SVS_L2.
I don't think that Snapdragon 870 is good choice for gaming better is to buy 865 and overclock to 950Mhz or 1ghz giving snapdragon 888 performance with lower temps than 870 and 888.
If you do root try to underclock CPU to 865+ 3ghz or 2.9ghz to lower temps performance difference isn't noticable.
vinyimp said:
Hi Patrick, sorry to ask but you abandoned for some reason?
I have a OnePlus 9R (SNAP 870) and it's hot, I'm looking for an undervolt on it but I can't find anything, could you give me some direction?
Click to expand...
Click to collapse
things just update faster than I have time to test.
my charts became old, even the one Dr.Brown is using on his video, its quite old missing voltage steps and have not been tested on the newer versions of Konabess.
my original thread here took about 3 months of my time testing every possible setting to make sure other users didnt brick or toast their devices.
I took everything down when I seen alot of new rom updates, and konabess updates were causing bugs in the settings I had here for many users.
I didn't have time to retest everything and update my charts, I also had to deal with people stealing my charts and claiming the work for them selves. which I had to open youtube reports, contact google with proof of my work contact admins here and a few other sites too, etc all because some people didn't want to add a credit of where they found my charts.
so after a good week of emailing and chatting on the phone with google fraud control i decided to not continue posting my work, that may actually cause damage if used wrongly was too much work to deal with.
I'm still just too busy. my phone is stock android non rooted now because some apps I use can't be hidden.
so, I have no time to update this thread. I have no desire to leave the information for others to brick their devices.
the chart on dr.browns video is older than my most up to date chart, but still even that is months behind the current app and rom version changes.
my best advice is, if your phone works the way you want it, dont mess with any of the clock speeds. just undervolt some steps that are commonly used and test those.
too many people have tried to overclock their phones GPUs above 900 and lost functionality (permanently) or just hard bricked the phone (where an unbrick tool wont recover it.)
many will say its harmless, but its about usage. if you game alot and want to game alot, overclocking will create more heat, even if you undervolt. the result will be a paperweight.
those many people are not you, and not your phone. so anything can happen.
be mindful and careful of the settings you use. and install a temperature monitor for CPU and GPU.
going over 70'c will risk the loss of your unit.
Patrick Morgan said:
things just update faster than I have time to test.
my charts became old, even the one Dr.Brown is using on his video, its quite old missing voltage steps and have not been tested on the newer versions of Konabess.
my original thread here took about 3 months of my time testing every possible setting to make sure other users didnt brick or toast their devices.
I took everything down when I seen alot of new rom updates, and konabess updates were causing bugs in the settings I had here for many users.
I didn't have time to retest everything and update my charts, I also had to deal with people stealing my charts and claiming the work for them selves. which I had to open youtube reports, contact google with proof of my work contact admins here and a few other sites too, etc all because some people didn't want to add a credit of where they found my charts.
so after a good week of emailing and chatting on the phone with google fraud control i decided to not continue posting my work, that may actually cause damage if used wrongly was too much work to deal with.
I'm still just too busy. my phone is stock android non rooted now because some apps I use can't be hidden.
so, I have no time to update this thread. I have no desire to leave the information for others to brick their devices.
the chart on dr.browns video is older than my most up to date chart, but still even that is months behind the current app and rom version changes.
my best advice is, if your phone works the way you want it, dont mess with any of the clock speeds. just undervolt some steps that are commonly used and test those.
too many people have tried to overclock their phones GPUs above 900 and lost functionality (permanently) or just hard bricked the phone (where an unbrick tool wont recover it.)
many will say its harmless, but its about usage. if you game alot and want to game alot, overclocking will create more heat, even if you undervolt. the result will be a paperweight.
those many people are not you, and not your phone. so anything can happen.
be mindful and careful of the settings you use. and install a temperature monitor for CPU and GPU.
going over 70'c will risk the loss of your unit.
Click to expand...
Click to collapse
Perfect understood Patrick, it's a shame all this happened, unfortunately people don't give value/recognition to people who help for free!
I'll enjoy and tell you my experience, my 9R is on OOS 11.2.6.6 (Stock) and with Kernel Stock as well (since there isn't much customization yet)
They ended up recommending the Dr. Brown video and I decided to do some tests, if the person copies the Overclock that he does in that video (905MHz) the device will not start, it will be necessary to flash the previous boot.img
This happened to me and I was able to reverse the situation (probably because the KERNEL does not support such clocks that would even be unnecessary)
But on his channel there is a more recent video teaching how to Underclock and so I took the clock's as a base and started to make my fine adjustments
Clocks follow this pattern; 512 - 490 - 455 - 445 - 305 - 295 - 195
Voltages as per your chart; SVS_L2 - SVS_L1 _ SVS_L0 - SVS_L0 - LOW_SVS - LOW_SVS - LOW_SVS
And the BUS frequencies I left original, so I found SWEET SPOT, the device is much cooler, stable, in games despite the Underclock holding well (80 FPS+ with graphics at maximum)
Hopefully there will soon be some app/kernel that can undervolt the CPU too, maybe just remove -25mv/-50mv and do some testing as most of the heat comes from it.
I'm quite satisfied and I'm grateful to you because without your charts in Dr. Brown's video, wouldn't know how to do!
I wish you all the best, success!
vinyimp said:
Perfect understood Patrick, it's a shame all this happened, unfortunately people don't give value/recognition to people who help for free!
I'll enjoy and tell you my experience, my 9R is on OOS 11.2.6.6 (Stock) and with Kernel Stock as well (since there isn't much customization yet)
They ended up recommending the Dr. Brown video and I decided to do some tests, if the person copies the Overclock that he does in that video (905MHz) the device will not start, it will be necessary to flash the previous boot.img
This happened to me and I was able to reverse the situation (probably because the KERNEL does not support such clocks that would even be unnecessary)
But on his channel there is a more recent video teaching how to Underclock and so I took the clock's as a base and started to make my fine adjustments
Clocks follow this pattern; 512 - 490 - 455 - 445 - 305 - 295 - 195
Voltages as per your chart; SVS_L2 - SVS_L1 _ SVS_L0 - SVS_L0 - LOW_SVS - LOW_SVS - LOW_SVS
And the BUS frequencies I left original, so I found SWEET SPOT, the device is much cooler, stable, in games despite the Underclock holding well (80 FPS+ with graphics at maximum)
Hopefully there will soon be some app/kernel that can undervolt the CPU too, maybe just remove -25mv/-50mv and do some testing as most of the heat comes from it.
I'm quite satisfied and I'm grateful to you because without your charts in Dr. Brown's video, wouldn't know how to do!
I wish you all the best, success!
Click to expand...
Click to collapse
I recommend Overclocking by your self to higher freq.
This config from video don't boot on any sn865 devices even Apollo but I can overclock to 940 MHz stable.
I know that Poco F3 has lock freq to 683 MHz after that doesn't boot.
I think your UV is too high 512 can get as low as SVS_L1 or SVS_L0
astronomy2021 said:
I recommend Overclocking by your self to higher freq.
This config from video don't boot on any sn865 devices even Apollo but I can overclock to 940 MHz stable.
I know that Poco F3 has lock freq to 683 MHz after that doesn't boot.
I think your UV is too high 512 can get as low as SVS_L1 or SVS_L0
Click to expand...
Click to collapse
Unfortunately on the OnePlus 9R (all stock) any clock higher than the original (670 MHz) the system doesn't boot (I don't know why, maybe some ROM limitation or KERNEL doesn't support it)
I ended up Underclocking to have a cooler device and in fact it is cooler without loss of performance in normal use and holding up well in games at maximum graphics
No artifacts, crashing or instability
As for the voltage on 512, it could really go with SVS_L1 - it goes between SVS_L2 and L1 on Patrick's Chart (525 - 512 - 490 MHz) I intend to do a test soon, for now it's stable and in games it doesn't get too hot!
vinyimp said:
Unfortunately on the OnePlus 9R (all stock) any clock higher than the original (670 MHz) the system doesn't boot (I don't know why, maybe some ROM limitation or KERNEL doesn't support it)
I ended up Underclocking to have a cooler device and in fact it is cooler without loss of performance in normal use and holding up well in games at maximum graphics
No artifacts, crashing or instability
As for the voltage on 512, it could really go with SVS_L1 - it goes between SVS_L2 and L1 on Patrick's Chart (525 - 512 - 490 MHz) I intend to do a test soon, for now it's stable and in games it doesn't get too hot!
Click to expand...
Click to collapse
No it is lock by Qualcomm to that freq so of doesn't boot it like 855+/860.
That why I buy Mi 10T with 865 and can be overclock to even 2ghz by someone.
astronomy2021 said:
No it is lock by Qualcomm to that freq so of doesn't boot it like 855+/860.
That why I buy Mi 10T with 865 and can be overclock to even 2ghz by someone.
Click to expand...
Click to collapse
Understood, a custom KERNEL doesn't unlock this lock by Qualcomm?
I had a OnePlus 8 with 865, today I just miss it
vinyimp said:
Understood, a custom KERNEL doesn't unlock this lock by Qualcomm?
I had a OnePlus 8 with 865, today I just miss it
Click to expand...
Click to collapse
Maybe can by i case of 855+ was lock on all phones from manufacturer process.
But early builds of F3 has unlock freq but after that they are block that why buying 865 is better if you want performance for gaming or emulation like switch. I now play Zelda breath of the wild on my Mi 10 t and after 168days will be Overclocking to 940Mhz giving me performance of 888.