Mi5 is supposed to be underclocked at 1.8 ghz right but according to the droid info app it shows 1.3 ghz
Clock speed 1363mhz-1363mhz
Hi,
Snapdragon 820 SoC works with lutte.Big architecture.
In facts your mi5's SoC has 4 cores : 2little and 2big.
Little is well suited for light tasks as it is very power efficient and low power consuming.
On the other end, big is much power hungry but more powerful.
What xiaomi "forgot" to mention is that mi5's little core isn't clock at 1,8GHz (you guessed it : it's big's clock) but at 1,3GHz.
So don't wrorry everything is normal ^^'
Just check cores 3 and 4 They should be at 1,8GHz where cores 1 and 2 are sitting at 1,3GHz which is normal.
You should try CPU-Z
It shows all 4 cores and corresponding clock speeds.
2nd: your phone might be in power save mode. Switch to "balanced" to gain more clock speed.
Related
Hello all !
I was bored in school today so I've written a governor concept idea for quad cores. I'm not a dev AT ALL (for now at least, i'm studying many different stuff, hardware / code related too).
I have no idea if this is possible or if this is clever but I wanted to share it anway. If it gives idea to a developer, that's totally worth it, otherwise, well... I had fun doing it
It's called Progressive.
Progressive
The name of the governor says all. The idea behind it is to be «*progressive*». It means it doesn't unleash the full power when it's not needed. It goes progressively higher in freq with more cores. This should make the phone cooler and the battery better. The delay (3 sec ) is just a number, not sure this is really nice. Also, I'm not sure how the S4 handles temperature.
Max freq 1.5 Ghz
Min freq 384 Mhz
Screen off
=> 384-918 Mhz // not too low frequency to avoid reboot
Screen on without touching since 3 sec // always check after 3 seconds for changing the state
=> 384-1134 Mhz only one core online
Screen on touched
=> 594-1134 Mhz two cores online // bump the min_freq to avoid keyboard lag and to add a bit of butter
Screen on touched with a medium load of task // not sure how quantify this
=> 594 Mhz – 1.5Ghz two cores online
Screen on touched with a high load of task // i.e. Games
=> 702 Mhz – 1.5 Mhz four cores online // max power
We also need a thermal protection to avoid any damage, this should do the trick
If the temp is >= 80°C
=> Two cores online max_freq 1134 Mhz until it reaches 70 °C // not sure about the temp, this can be adjusted
If the temps is >=70°C
=> Let 4 cores being possibly online but lower the max_freq to 1134 Mhz
Click to expand...
Click to collapse
What do you guys think ? Is this even possible ? Good, bad idea ?
I hope you enjoy reading it as much as I enjoyed to writte it
doesn't it do this already?
Fissurez said:
doesn't it do this already?
Click to expand...
Click to collapse
I'm not sure how the ondemand governor on nexus 4 works. So I can't really answer, it's really a noob idea that poped into my head today
you pretty much described interactive with mpdecision enabled.
not exactly, but quite.
3 seconds is way too long for the CPU to ramp up (just a matter of tweaking, though). you'd get more lag than you save battery.
mpdecision ramps the cpu to its maximum frequency as soon as a touch input is detected (normally only 2 cores until a certain threshold is reached), so yours should save a bit of power during smaller workloads.
also, if the touch input is released, it clocks the active cores down to 1.02 GHz for a bit before disabling them when not needed.
after all, it seems like a more conservative interactive governor with active mpdecision. could be nice for saving battery while retaining good performance.
it could be a viable choice for those who go for battery life over performance. :good:
Nuu~ said:
you pretty much described interactive with mpdecision enabled.
not exactly, but quite.
3 seconds is way too long for the CPU to ramp up (just a matter of tweaking, though). you'd get more lag than you save battery.
mpdecision ramps the cpu to its maximum frequency as soon as a touch input is detected (normally only 2 cores until a certain threshold is reached), so yours should save a bit of power during smaller workloads.
also, if the touch input is released, it clocks the active cores down to 1.02 GHz for a bit before disabling them when not needed.
after all, it seems like a more conservative interactive governor with active mpdecision. could be nice for saving battery while retaining good performance
Click to expand...
Click to collapse
Thank you Sir, I understand better how mpdecision works now
Glad to see i'm not completely stupid lol
i know that soc is an 8026 but how many core and which gpu are in that snapdragon on GWR? Because somesay that it have 2 core and adreno 220 and someone else say that it's a normal quadcore with adreno 305
You might want to check this thread:
http://forum.xda-developers.com/g-watch-r/orig-development/kernel-intersectravens-kernel-t2957728
It has all 4 cores, with max speed of 1.2GHz (I think?)
It comes with only 1 core enabled out of the box on the default kernel, but it's possible to enable all 4. The problem is of course battery life, and it makes a huge difference when you enable all 4 and start playing with the watch.
It also gets quite (uncomfortably) warm for example during the initial synchronization (when all the apps are installed/compiled by ART).
A good compromise is 2 cores limited to 800MHz, which is what I'm running right now (a default setting on the kernel I linked in recent versions) and I cannot complain. I think it now actually drains less power than stock (some optimizations were added) and it is a lot more responsive. There's no need for more power anyway.
I can't use my vr gear for more that 10 minutes before the overheating message appears on the phone.
Has anyone found a fix for this?
I wouldn't do the cooling fan mod on the gear, too much hassle.
On my note 4 I undervolt and set the cpu governor to 1100mhz max. I believe the VR is more dependent on GPU than CPU so undervolt and limiting the cpu speed keeps it cooler.
jedisurfer said:
On my note 4 I undervolt and set the cpu governor to 1100mhz max. I believe the VR is more dependent on GPU than CPU so undervolt and limiting the cpu speed keeps it cooler.
Click to expand...
Click to collapse
Do you mind sharing your voltage and clock settings?
How much additional time you achieve with your setup?
Thanks!
Rayan said:
Do you mind sharing your voltage and clock settings?
How much additional time you achieve with your setup?
Thanks!
Click to expand...
Click to collapse
I can run it pretty much indefinitely I think, at least an hour. I usually stop every 30 min because my eyes get strained.
I have emotion kernel 21, running rapture rom using synapse to undervolt and underclock. I have the 805 variant so there is core 0, 1, 2, 3. Under hotplug I also disable core 3. It runs perfectly fine and does not jitter even with the cpu set that low and core 3 offline(the 4th core since it starts at core 0)
I run -100mv through all the speed steps (that's the most it will let me undervolt global if I want to go lower I have to manual set it for each speed)
268mhz - 600mv
300mhz - 605mv
345 - 610
422 - 615
499 - 625
576 - 635
652 - 645mv
729 - 655mv
etc each step I usually go up 10mv
1113 - 705mv
1190 - 715
1267 - 725mv
1344 - 745mv
my pvsX
qcom speed2-pvs13-bin-v1 I believe I got lucky with a high pvs13 your undervolts will vary. So please go slowly and don't try -100mv right away. I'd go -20, -40, -60 etc to test stability first. I also run it without the back cover just because I hate my chips heating up too much.
jedisurfer said:
I can run it pretty much indefinitely I think, at least an hour. I usually stop every 30 min because my eyes get strained.
I have emotion kernel 21, running rapture rom using synapse to undervolt and underclock. I have the 805 variant so there is core 0, 1, 2, 3. Under hotplug I also disable core 3. It runs perfectly fine and does not jitter even with the cpu set that low and core 3 offline(the 4th core since it starts at core 0)
I run -100mv through all the speed steps (that's the most it will let me undervolt global if I want to go lower I have to manual set it for each speed)
268mhz - 600mv
300mhz - 605mv
345 - 610
422 - 615
499 - 625
576 - 635
652 - 645mv
729 - 655mv
etc each step I usually go up 10mv
1113 - 705mv
1190 - 715
1267 - 725mv
1344 - 745mv
my pvsX
qcom speed2-pvs13-bin-v1 I believe I got lucky with a high pvs13 your undervolts will vary. So please go slowly and don't try -100mv right away. I'd go -20, -40, -60 etc to test stability first. I also run it without the back cover just because I hate my chips heating up too much.
Click to expand...
Click to collapse
Funny I just did the same thing to my a10 7870k rig. Lowered vcore and over clocked gpu. Runs much better those a10s don't need 1.45 volts lol. I'm not sure if I could do that to my s6 tho as I'm nervous to root because of jump program.
Sent from my SM-G920T using Tapatalk
Does any have experience with editing the available CPU frequencies? I want to go to a lower frequency than 1113 GHz. So, the opposite of overclocking. From what I understand, it requires either editing the kernel or getting an entirely different one - which I am not capable of doing myself.
As it bugs me (and probably you) how fast the battery drains on Mi 6x, I looked in the CPU settings.
As it looks:
CPU 0 to 3 run on a minimum frequency of 633 GHz each.
CPU 4 to 7 run on a minimum frequency of a whopping 1113 GHz each.
When I put the phone into standby, it continues to run on 1113 GHz on 4 cores. So, is it surprising that Mi 6x drains battery? No. (In addition to a massive screen that requires extra battery, in addition to a smaller battery... very smart engineering here) Imagine you'd put your laptop into standby and it would continue to work with half its processor speed. Not acceptable.
daokris said:
Does any have experience with editing the available CPU frequencies? I want to go to a lower frequency than 1113 GHz. So, the opposite of overclocking. From what I understand, it requires either editing the kernel or getting an entirely different one - which I am not capable of doing myself.
As it bugs me (and probably you) how fast the battery drains on Mi 6x, I looked in the CPU settings.
As it looks:
CPU 0 to 3 run on a minimum frequency of 633 GHz each.
CPU 4 to 7 run on a minimum frequency of a whopping 1113 GHz each.
When I put the phone into standby, it continues to run on 1113 GHz on 4 cores. So, is it surprising that Mi 6x drains battery? No. (In addition to a massive screen that requires extra battery, in addition to a smaller battery... very smart engineering here) Imagine you'd put your laptop into standby and it would continue to work with half its processor speed. Not acceptable.
Click to expand...
Click to collapse
Hello. It is normal for the processor to operate at its normal frequency while the phone is idle. There are plenty of processes in the background. If you have root rights, then you can download an application like (l speed) through this application, I put my battery my processor and the data in the background that allows me a loss of only 1% over a period from 10 am
If I'm not mistaken, your processor cores should go into deep sleep state when you turn your screen off. If they stay on 633/1113 then something is probably keeping the phone awake and battery is going to suck.
Download Dev Check to see how long the cores stay on certain frequencies. If you leave your screen off for most of the time, then most of the graph should show "Deep Sleep" instead of any other frequency.
Most of your know about this problem. People complaining about phone heating, phone shuts down in the middle of gaming, heating while gaming with 90hz in all forums. But no one come up with the solution and Some even told us to send the phone to get serviced [yeah, but even then the service center will say that it is motherboard fault, which is the costliest replacement of all around 25k INR]
[NOTE: I want this to be heard by ASUS to release software update. If you are a moderator of any Asus forum or who could contact ASUS dev, share this thread with them]
First and foremost we have to understand what is causing the problem. And everyone who is facing the problem knows Its the Temperature causing the shutdown. But ASUS never implemented any Warnings to to the UI, instead they give active cooler to 256+ GB version, while leaving 128 GB owners stranded. I faced the shut down problem when updating to A10 around a year back.
Every time when I game outdoor on warm condition (around 30 degrees) and After few months of updates, it started to shut down very frequently. So I switched back and forth to custom ROMs and even to stock A9s.
Faced the worst embarrassment "Gaming phone shuts down in front of cousins who were playing in budget phone"
Finally my Gaming phone become a phone which cant game anymore.
Finding the real Problem:
After researching about android thermals and I even tried to stop the shutdown from happening to my device. But I failed and my device successfully shuts down when there is a chance.
I switched to custom rom and installed GCAM. On taking few photos, my phone died. After restarting and enabling the CPU overlay which shown the temperature and clock speed of CPU. Opened GCAM and took some photos the temperature rose from 40-65 degrees in an instant and it died and I noted all the CPU cores are ran at max clockspeed.
So, I switched back to stock rom, used Armoury crate to limit and limited the CPU clock speed of GCAM, Again same result phone died (like the custom rom Armoury crate displayed the max clock speed of 2.96 Ghz, though the app was being set to use lower clock of 1.92 Ghz)
After using and failing to limit CPU clock using kernels, It was conclusive that the temperature is not causing the issue, "NO_THROTTLING" of CPU does.
During heavy load on CPU like gaming or benchmarking, all CPU cores will run at high clock speed, which increases the temperature of CPU. To counterfeit this, the system applies slightly lower max clock speed to all its cores, makes the CPU to run at slightly lower clock speed. As the temperature increases the max clock speed will get reduced till it can no longer produces heat (auto cooldown) on doing work. Same applies for GPU. This is called throttling.
What will happen, when throttling doesn't happen? All CPU and GPU cores run at max speed which increase the temperature, when there is nothing to stop the rising temperature. The temperature rises further [A10's thermal management kicks in] and shuts the device.
During charging, the CPU temperature will be higher due to battery dissipating the heat, so when there is even slight load on CPU (background activities like downloading) rapid rise in temperature even for few milliseconds kills device.
Maybe none of the testing devices have this problem & none of the developer devices have this problem, but this problem does exist and I'm asking ASUS to release the patch for devices which lacks controlling CPU clock speed via Armoury create, and fix the device which doesn't throttle (thermal engine)
-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-
Temporary Solution: Manually down clock the CPU and GPU
After so many failed attempt to apply lower clock to CPU, I found the location where the max clock speed file was located.
[I modified the file and put together in tasker (paid app to automate things) found my CPU finally throttled again]
I shared the values taken from asus thermal management applied those values and uploaded it.
Be careful, This might brick your device if used improperly, if that happens you might need to flash raw image so backup anything important. Don't point me the finger afterwards. If you are okay with that lets proceed.
We Need root access and root browser. If you have root access open any root browser and Extract the attached zip file
It has two folders and some files. CPU Reading folder has all the CPU max clock speed you can use to apply lower clock.
the folder contains 9 digit number like 295241178
First 3 number denotes max clock speed of Prime core i.e., 2.96Ghz
Next 3 numbers denotes max clock speed of Big core i.e., 2.4Ghz
Last 3 number denotes max clock speed of little core i.e., 1.78Ghz
for GPU First 3 number is the MHz of max clock (6750 is 675 MHz)
Select the clock speed you need
(lower number = lower clock speed = low performance = less heating
Higher number = high clock speed = better performance = more heating)
CPU has 9 different clock speed littleBigPrime combos
Gpu has 5 different combos
Applying clock speed
Replace the CPU file cpu_max_freq to the folder /sys/module/msm_performance/parameters
Replace the Gpu file max_gpuclk value to the folder /sys/devices/platform/soc/2c00000.qcom,kgsl-3d0/kgsl/kgsl-3d0
Replace those files and see if your device shuts down on gaming, if it does choose the lower value and repeat the process.
Everything should work properly now. It might not be great solution but it will prevent shutdown.
-x-x--x-x-x--x-x--x-x-x-x--x-x--x-x-x-x--x-x-x-x-x--x-x-x-x-x-x-x-x--x-x-x-x-x-x--x-x-x-x-x--x-x-x-x-x-
Im creating an app to solve this, which is in progress. Will update once everything is done.
por favor, preciso deste aplicatirvo!
venkatesh321 said:
Im creating an app to solve this, which is in progress. Will update once everything is done.
Click to expand...
Click to collapse
Are you done making the app, cuz i really need it rn
its power ic related issue. throttling app is reducing the performance