Related
Hi everyone.
I wonder if there's a way to underclock the device to save energy (which seems to be a rare good )
I already tried different tools like "Hack Master" or "XScalar" or "Battery [...]". They all managed to display the CPU-Speed but weren't able to change it.
I even tried to get some information about the Qualcomm Chip it uses to see if there is a document with the needed commands but I was only able to find a white paper describing the main feature.
But as the core is arm11 compatible I think there must be a way to change the clockspeed. Any ideas?
i have looked for a while too, but didn't find anything but this feature would be really neat, I used it on my Orbit and I could double battery life time.
Only TI OMAP CPU supports (under or) overclocking. Orbis comes with TI OMAP 850 200 MHz CPU, same as Diamond predecessor HTC Elf.. it works with Battery Status to dynamically over or underclock the CPU, but not the Qualcomm MSM7201A 528 MHz found in Diamond
UUUU you read my mind.
Hey everyone,
I seem to be having an issue with the battery temperature sensor. It will always say 30 Celsius even if I can feel the heat of the battery through the case. Is this a known issue with the tabs? Using sensor test, I can see that a temperature sensor works and is constantly updating, showing temps from 30C to 40C. I'm running stock rooted EC02 with KhasMek Voodoo Plus OC 1.4Ghz.
Thanks for your help.
xz124 said:
Hey everyone,
I seem to be having an issue with the battery temperature sensor. It will always say 30 Celsius even if I can feel the heat of the battery through the case. Is this a known issue with the tabs? Using sensor test, I can see that a temperature sensor works and is constantly updating, showing temps from 30C to 40C. I'm running stock rooted EC02 with KhasMek Voodoo Plus OC 1.4Ghz.
Thanks for your help.
Click to expand...
Click to collapse
There are 2 main reasons for a constant temperature:
1- A third-party battery is used which have its temperature sensor removed, you will usually see 0.1 variations, like 30.0 and 30.1 at all times. or more often 25.0 and 25.1 (not sure why though).
2- the ROM or kernel is broken with regards to providing temperature to battery apps. Battery apps get temperature from Android OS using well documented API, which have not changed since the very beginning of Android. See here for more information about the API: http://developer.android.com/reference/android/os/BatteryManager.html
Unfortunately it seems to affect a few ROMs now-a-days.
EDIT: Are you using a S3 with CM-based or OMNI (AOSP-based) ROMs?
We all know about the emmc bug that has affected our note 4, as I saw on the "Fix'd" thread someone solved their emmc brick by baking the motherboard, like people did when their PS3s were failing to reball the GPU.
So this means that at least some instances of the bug, if not most, are caused by the emmc being desoldered by the heat of the CPU, which is soldered on the same side of the PCB, right under it (Samsung ePOP technology). As an introduction to my possible "solution" to it I want to say this: I recently bought the Note 4, after I broke something on my Note 3's mobo. A big difference between the two that I observed is that on my N3 i could undervolt about 25-30 mV lower than the stock values and that was it,more and it would reboot, I forgot the pvs bin no. , but it was a either 3 or 4, the good ones. Well, on my N4 after I checked my pvs bin ( pvs10 ), I put the PVS10 voltage table on the phone , and that was -65 mV compared to stock, after that I undervolted -25 mV more and everything is perfect : No deep sleep problems, no audio problems with screen off (While also using V4A), 85K Antutu Score and CPU Throttling Test is showing a very big improvement on the heat dissipation: it now underclocks more easily (2.64-2.45-2.22-2.0 but it mostly stays at 2.45 and from time to time going to 2.22-2.0 for a few seconds), using stock values it was dropping to 1.72 after 2 seconds on the test then going up to 2.0 for a few moments then back to 1.72 and mostly staying there. I want to add here that the Sub-Ghz voltages can be undervolted even more to the values of the pvs15 table without any problems.
So , my "solution", not really a solution but more like future proofing the health of the ePOP package (S805 AP with RAM and EMMC soldered right on top of it) is to :
1. Check your pvs bin.
2. Apply specific voltage table values in KA/Synapse .
3.Undervolt -25 more and test for stability, and if your phone can handle it, undervolt even more, to the maximum possible ( sillicon lottery ).
P.S: If you are more experienced user and have H/W capabillities, you can also add what I did to my Note 3: I opened the phone, removed the pink heatpad it had, and in place of it I put a decent amount of Arctic MX-2, added a very thin aluminium heatsink (from car ECU) , then a blop on the heatsink, one on the CPU and voila! In the cpu throttling app the phone was sustaining 2.57 Ghz for like 2-3 minutes , then underclocking a bit and then back to 2.57 Ghz; idling at around 30 C even hitting 27 C, and when normal using going around 40-42 . Sadly while doing test (i had a few attempts before getting the perfect amount of Paste ) I broke the headphone band, then when replacing that I broke the MIC and Speaker little gold legs on the USB pcb, and then just sold the display and batteries and bought our beloved Note 4, which is a really nice upgrade!
EDIT : h t t p : / / w w w . myfixguide . c o m /manual/samsung-galaxy-note-4-disassembly/ it shows here the said package , they only mention "3GB RAM chip and Qualcomm APQ8084 enclosed chip", but as I read the technology combines RAM and MLC (the internal memory) on the same chip.
Hi bro, do we need custom kernel to do that, just the undervolt thing ?
i'm wondering whether emmc can be upgraded to a faster one, which will then make the phone way snappier?
Here is a 100% hardware fix for this issue that anyone can do with no tools or special equipment.
It really works. Give it a try. ?
https://youtu.be/jLPHWtb0StI
Moto Z2 Force is a blazing fast smartphone. This out of any doubt.
Fore sure it is the fastest phone I've ever worked on.
On the shelf a lot of phones seem to be fast, BUT when you install over 200 apps on them and you are using 7 home screens full of widgets (ehm...) things become "a bit" different...
Not this time: over 200 apps installed didn't change it's fantastic speed. It's like working on an iPhone.. BUT this *is* doing something too! :laugh:
What's more interesting is that... it can be even faster too!!!
Many smartphones can be sligtly overclocked because of heating and battery life needs that lead manufacturer to lock frequencies to lower values respect of SoC capabilities. BUT usually root isn't enough to have overclock access, since higher frequencies need a modified kernel to be unlocked..
But Moto Z2 Force is not "one of many" smartphones...
Motorola confirmed my first impression I had on my old Griffin (Moto Z): they are making smartphone for "geeks"!
Moto Z2 force is using an 8 core Snapdragon 835 using "big-LITTLE" architecture:
- 4 high performance Kyro 280 cores clocked between 345 and 2361 MHz (big)
- 4 low power Kyro (???) cores clocked between 672 and 1900 MHz (LITTLE)
(frequencies adopted on EU unbranded XT1789-06... on different markets/versions they could differ...)
Obviously, low power cores work most on screen off conditions and during light tasks, while high performance ones enter the game when more performances are required as we have already seen on many similar architectures...
What's particularly interesting is that 2361 MHz is NOT the higher frequency of Kyro 280 and 672 MHz is NOT the lower frequency low power Kyro can work before going to deep sleep condition...
In fact big cores can work up to 2457 MHz (in a single step) and LITTLE ones down to 300 MHz (with 300, 364, 441, 518, 595 MHz intermediate steps available!)
What's is even more interesting is that simply by having root and a (great!) app called Kernel Adiutor - available on Play Store too - we can go to change (temporary or permanently) these values to overclock and/or underclock our system, eventually having better performances and/or better battery lifes...
I'm testing this and results are confirmed (by Kernel Adiutor statistics too...) and interesting: Z2 Force is not a device prone to overheat (like was my old Griffin instead... ) and so it seems to work with no issues at all @2457 MHz with interesting Geekbench 4 results as attached (please note that results are taken with all my 200 apps still installed & working... on lighter conditions they could be quite better too...).
In any case they are better than any Android Device recorded to date in Geekbench 4 charts... expecially for Multi-Core results...!! :highfive:
Underclock LITTLE cores from 672 MHz to lower values could (and I underline could...) improve battery life expecially during screen off conditions, BUT there are considerations to be taken:
- lower frequencies involves more time out of "deep sleep" condition too...
- on many devices adopting very low frequencies often lead to slow (or difficulties in...) "screen back on" operations
BUT there are MANY frequencies to eventually test so... games are open!!!
In any case, Motorola again! :good:
Feedbacks and eventual Geekbench4 / Antutu results on different clock settings are the welcome...
This is with the pantheon Kernel, prior to poking it.
https://browser.geekbench.com/v4/cpu/4880631
I'm doing some little tune up experiments with frequencies and these are some first results:
- lowering lower working frequency of LITTLE cores up to 345 MHz (from 672 MHz) seems to create no issues or delays on powering on screen even using fingerprint sensor...
On the other hand I'm still not so sure of eventual power saving benefits (my Z2 setup is already very good during screen off time with an average consumption of about 1,5%/hr... so eventual differences are minimal)
- I've to doublecheck it (more confirms needed...) but I'm quite sure big cores are clocked at faster frequency (2.45 GHz) during boot up, then (when exactly?) lowered to a max frequency of 2.36 GHz... this seems to me simptom of a very well tuned up system...
Does somebody have voltages/frequencies tables for our phone?
enetec said:
I'm doing some little tune up experiments with frequencies and these are some first results:
- lowering lower working frequency of LITTLE cores up to 345 MHz (from 672 MHz) seems to create no issues or delays on powering on screen even using fingerprint sensor...
On the other hand I'm still not so sure of eventual power saving benefits (my Z2 setup is already very good during screen off time with an average consumption of about 1,5%/hr... so eventual differences are minimal)
- I've to doublecheck it (more confirms needed...) but I'm quite sure big cores are clocked at faster frequency (2.45 GHz) during boot up, then (when exactly?) lowered to a max frequency of 2.36 GHz... this seems to me simptom of a very well tuned up system...
Does somebody have voltages/frequencies tables for our phone?
Click to expand...
Click to collapse
They're in the kernel. I tried to do normal edits to lower and increase, but it did something weird and just parked them at 30mhz after compile...
Edit: https://github.com/Uzephi/kernel_nash/blob/upstream/arch/arm/boot/dts/qcom/msm8998-v2.dtsi
There is the link to the file that controls the frequencies for each bin of our phone
Uzephi said:
They're in the kernel. I tried to do normal edits to lower and increase, but it did something weird and just parked them at 30mhz after compile...
Edit: https://github.com/Uzephi/kernel_nash/blob/upstream/arch/arm/boot/dts/qcom/msm8998-v2.dtsi
There is the link to the file that controls the frequencies for each bin of our phone
Click to expand...
Click to collapse
Very complex!
I will take a deep look at this as soon as I would have a bit of time...
enetec said:
Very complex!
I will take a deep look at this as soon as I would have a bit of time...
Click to expand...
Click to collapse
Essentially, little CPU has one speed bin and frequencies available from 300-1900 and big CPU has 4 speed bins with frequencies from 300-2592. Top end changes depending on your bin. I.E. silicon lottery. Speed bin 0 can step higher than bin 3
Edit: to find speed bin, it's usually in proc/kmesg or proc/last_kmesg. Needs root to read
Uzephi said:
Essentially, little CPU has one speed bin and frequencies available from 300-1900 and big CPU has 4 speed bins with frequencies from 300-2592. Top end changes depending on your bin. I.E. silicon lottery. Speed bin 0 can step higher than bin 3
Click to expand...
Click to collapse
Yes, on my own device max available speed is 2457 MHz... but my doubt is, how a single device (using same software) would choose between different bins?
Anyway is voltage the complexity I was referring to... at first look It seems not using a fixed one for a single frequency as on my old LG G2 but a range... I've to look better at it...
Some first interesting results from tests have been achieved...
I will post a more detailed report in one day or two...
enetec said:
Yes, on my own device max available speed is 2457 MHz... but my doubt is, how a single device (using same software) would choose between different bins?
Anyway is voltage the complexity I was referring to... at first look It seems not using a fixed one for a single frequency as on my old LG G2 but a range... I've to look better at it...
Click to expand...
Click to collapse
It's quite simple. At boot the kernel reads all "devices" on the computer (our case, the phone) and runs checks at low level on the hardware for software revisions, serial numbers, Mac addresses and guess what? The speed bin embedded in the chip. It then runs a cmdline for the system to read the results to access the devices and use the kernel correctly. This is how I manipulated the system to read the bootloader as locked. On my kernel, go to developer options and you will see you can toggle bootloader unlocking. This is because the cmdline tells the system we are still locked.
Uzephi said:
It's quite simple. At boot the kernel reads all "devices" on the computer (our case, the phone) and runs checks at low level on the hardware for software revisions, serial numbers, Mac addresses and guess what? The speed bin embedded in the chip. It then runs a cmdline for the system to read the results to access the devices and use the kernel correctly. This is how I manipulated the system to read the bootloader as locked. On my kernel, go to developer options and you will see you can toggle bootloader unlocking. This is because the cmdline tells the system we are still locked.
Click to expand...
Click to collapse
Nice!
Anyway I saw official documentation of SD835 speaks about 2.45 GHz as max frequency... so other speed bins are for special/overclocked lots probably...
enetec said:
Nice!
Anyway I saw official documentation of SD835 speaks about 2.45 GHz as max frequency... so other speed bins are for special/overclocked lots probably...
Click to expand...
Click to collapse
Cherry-picking a commit by Flar2 on his Pixel 2 kernel that enables the 2.5Ghz on all bins. Hopefully it works.
Uzephi said:
Cherry-picking a commit by Flar2 on his Pixel 2 kernel that enables the 2.5Ghz on all bins. Hopefully it works.
Click to expand...
Click to collapse
Have you found (during you searches...) where is the routine which changes max frequency from 2.45 GHz to 2.36 GHz after boot?
enetec said:
Have you found (during you searches...) where is the routine which changes max frequency from 2.45 GHz to 2.36 GHz after boot?
Click to expand...
Click to collapse
Those are both different bins. Maybe it loads one then the other? In any event all bins will be 2.5 if this works. Building now
Edit: checking my device, I don't go down to 2.36, max on mine is 2.45
Uzephi said:
Those are both different bins. Maybe it loads one then the other? In any event all bins will be 2.5 if this works. Building now
Click to expand...
Click to collapse
Uhm... I'm not so sure this is bin related, since max frequency (2.45 GHz) still remains usable, but no more used after boot (it can be re-enabled by Kernel Adiutor anyway)... this is more a simple setting IMHO...
enetec said:
Uhm... I'm not so sure this is bin related, since max frequency (2.45 GHz) still remains usable, but no more used after boot (it can be re-enabled by Kernel Adiutor anyway)... this is more a simple setting IMHO...
Click to expand...
Click to collapse
That's your bin which is set at boot... My bin gives me 2.45 by default... I am not rooted and haven't made changes. See attached screenshot
Built and works... See screenshot. All I did was change kernel. No other settings done. Next it to try UV
Uzephi said:
That's your bin which is set at boot... My bin gives me 2.45 by default... I am not rooted and haven't made changes. See attached screenshot
Click to expand...
Click to collapse
Nope. Your app reports only min & max available frequencies but not the used ones... In fact, if you look at your screenshot, min frequency is reported to be 300 MHz for all CPUs, BUT if you look at your frequencies at the screenshot moment, they are respectively 672 MHz for LITTLE & 345 MHz for big cores, that are the really used as min frequencies as stock.
If you install Kernel Adiutor all will be clearer for you... it reports all this in better way...
Uzephi said:
Built and works... See screenshot. All I did was change kernel. No other settings done. Next it to try UV
Click to expand...
Click to collapse
It works for sure... because probably new frequencies are still not used... see my previous post.
Try it out then ?
Edit: be sure to flash twrp boot image, then kernel then root. SU and Magisk lose root when flashing our kernels right now and will pull backup kernel from backup boot image
Edit 2: if you also look at my "after" screen, the CPU was pegged at 2.0 and 2.5 respectively due to just booting up and loading assets.
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