Related
after waiting impatiently for the arrival of your op2 , many are disappointed with the low battery standby....specially if you are using LTE.
issues :
1) even having such a large battery, getting poor battery life.
2) even if the phone is idle, battery drains :crying:
so after having it for almost 2 weeks, i have learned most of the cpu tuner and battery saving apps wont work with op2, its not because of software, basically snapdragon 810's big little architecture is new and apps in the market are not compatible with this octacore new chipset.
and because of very less manufacturers are using this SOC as we now know why... and they were right... it heats up a lot!!! so app developers have not concentrated an specific app for this SOC.
so after lots of mix and matches, finally have come up with a stable solution as follows :
a) your phone should be rooted.
b) install 3c cpu manager from playstore.
c) open minimum 6 apps in background maximum the better.
( remember if no apps are running in background then cpu manager will show only maximum 1.555 ghz. max frequency and 384 mhz low frequency single setup only and big little architecture dual setup wont be shown ie: 810 has 4 cores running @ 1.555 ghz max and other 4 cores @ 1.76 ghz max. and both setups at 384 mhz minimum. )
d) open cpu manager, there should be 2 different setups, if not then open more apps in background, simply change the governor to ON-DEMAND, from interactive and set it on and reboot, as i have noticed with interactive governor even during standby, processor does not stays idle at lower frequencies.
after changing the governor, i have noticed that during standby cpu frequencies are in idle or at the lowest. which highly improvises the battery standby life and haven't noticed any performance degradation.
you can even limit the higher cores frequencies from 1.76 ghz to 1.55 ghz... improving up-to some limit of over heating issues and better standby time.
these are just the findings i discovered with my phone, so don't blame me if anything goes wrong, do it at your own risk.
buntybauva said:
after waiting impatiently for the arrival of your op2 , many are disappointed with the low battery standby....specially if you are using LTE.
issues :
1) even having such a large battery, getting poor battery life.
2) even if the phone is idle, battery drains :crying:
so after having it for almost 2 weeks, i have learned most of the cpu tuner and battery saving apps wont work with op2, its not because of software, basically snapdragon 810's big little architecture is new and apps in the market are not compatible with this octacore new chipset.
and because of very less manufacturers are using this SOC as we now know why... and they were right... it heats up a lot!!! so app developers have not concentrated an specific app for this SOC.
so after lots of mix and matches, finally have come up with a stable solution as follows :
a) your phone should be rooted.
b) install 3c cpu manager from playstore.
c) open minimum 6 apps in background maximum the better.
( remember if no apps are running in background then cpu manager will show only maximum 1.555 ghz. max frequency and 384 mhz low frequency single setup only and big little architecture dual setup wont be shown ie: 810 has 4 cores running @ 1.555 ghz max and other 4 cores @ 1.76 ghz max. and both setups at 384 mhz minimum. )
d) open cpu manager, there should be 2 different setups, if not then open more apps in background, simply change the governor to ON-DEMAND, from interactive and set it on and reboot, as i have noticed with interactive governor even during standby, processor does not stays idle at lower frequencies.
after changing the governor, i have noticed that during standby cpu frequencies are in idle or at the lowest. which highly improvises the battery standby life and haven't noticed any performance degradation.
you can even limit the higher cores frequencies from 1.76 ghz to 1.55 ghz... improving up-to some limit of over heating issues and better standby time.
these are just the findings i discovered with my phone, so don't blame me if anything goes wrong, do it at your own risk.
Click to expand...
Click to collapse
This has nothing to do with apps, just poor drivers on the kernel side, scheduler isn't properly coded for this SoC, and the fact that there is no dynamic hotplugging options available without causing the phone to reboot under certain circumstances doesn't benefit us any. Check out some of the custom kernels, as they may increase your idle battery life, on my own kernel I saw .5% drain per hour max. For reference I saw about 20 hours idle and sitting at 89% on my kernel.
DespairFactor said:
This has nothing to do with apps, just poor drivers on the kernel side, scheduler isn't properly coded for this SoC, and the fact that there is no dynamic hotplugging options available without causing the phone to reboot under certain circumstances doesn't benefit us any. Check out some of the custom kernels, as they may increase your idle battery life, on my own kernel I saw .5% drain per hour max. For reference I saw about 20 hours idle and sitting at 89% on my kernel.
Click to expand...
Click to collapse
i really appreciate your findings with the kernel, but my post is intended for people like me who does not wants to mess up with a stock kernel, so that future OTA updates can be patched without much hassle.
as you see, oxygen os is quite new and incomplete when compared with other's have to offer. so i expect lots of future updates immediately by the OP to improve and stabilize the OS.
I am giving snapdragon battery guru a try, it's for Qualcomm processors. But I'm not very experienced in this stuff. I think it has helped but if someone with more experience wants to give it a try. Maybe they can shed some new light on this subject.
This is the result with on-demand governor settings when phone is idle. with stock kernel and stock frequencies.
Ondemand has always been my fvorite for all past phones. in op2 however it always reverts back to original after interactive. the best battery saver for any phone is swithching to 4.4.2. Azimg batteru life. unfortunately notpossble with op2
buntybauva said:
i really appreciate your findings with the kernel, but my post is intended for people like me who does not wants to mess up with a stock kernel, so that future OTA updates can be patched without much hassle.
as you see, oxygen os is quite new and incomplete when compared with other's have to offer. so i expect lots of future updates immediately by the OP to improve and stabilize the OS.
Click to expand...
Click to collapse
Being rooted alone will prevent OTA updates. You have to flash the full stock ROM when there's an update anyway which would overwrite the kernel.
I've looked everywhere and can't find a root nor any threads can someone help me out
Just rooted mine with http://kingroot.net
It's just root, no recovery or bootloader so far, but after deleting bloatware and installing Sense 7, it's a perfect and snappy phablet ☺☺☺
I unlocked my bootliader on my Fierce XL 5045n, now what?
I just noticed a "allow BootLoader to be unlocked" option in developer options. Still can't get root though. But that should definitely help getting a custom recovery done. I still can't get root, tried numerous times, apk and with Windows. I'm stock lollipop 5.1.1 and have the box checked to allow bootloader to be unlocked in developer options but still nothing. Any ideas?
LazMike, did you try Kingroot?
nyttliv7 said:
LazMike, did you try Kingroot?
Click to expand...
Click to collapse
Yes, I did, thanks, didn't work at first but a newer version did the trick but some apps are denied permission from Kinguser even though I grant it and it shows they are granted, it also made my phone super laggy. Cant wait for a recovery and some custom ROMs.
That's weird? My phone got even snappier... But I deleted quite a bunch of apps though. My ram is showing like 1gb free most of the time. I'm using greenify, maybe that helps as well? But of course, it will be great when the real development starts for this phone ☺
LazMike said:
Yes, I did, thanks, didn't work at first but a newer version did the trick but some apps are denied permission from Kinguser even though I grant it and it shows they are granted, it also made my phone super laggy. Cant wait for a recovery and some custom ROMs.
Click to expand...
Click to collapse
What version did you use?
I think it's the newest. 4.5.2, a older version wouldn't work, I keep getting permission denied for certain apps, even though they are granted and shows they are as well. I also keep losing root and Kingo has to redo it.
Ok so here's some tips for people who wanna root:
>-Download Kingroot 4.6.0 and use that to root. It may take a few tries but it'll root
>-In general settings, turn off smart authorization so it won't constantly ask for permissions that you already granted
>-If you want your Fierce XL to be faster and less battery consuming, download Kernel Auditor from the Play Store. When it's installed, grant root permission for it, go to the menu, tap where it says "CPU", and where it says " CPU Governor", click on it. It should have an option that says "powersave". Click on that one and you're good to go
>REMINDER: You need to root first to do all of this
psycho_deth6 said:
Ok so here's some tips for people who wanna root:
>-Download Kingroot 4.6.0 and use that to root. It may take a few tries but it'll root
>-In general settings, turn off smart authorization so it won't constantly ask for permissions that you already granted
>-If you want your Fierce XL to be faster and less battery consuming, download Kernel Auditor from the Play Store. When it's installed, grant root permission for it, go to the menu, tap where it says "CPU", and where it says " CPU Governor", click on it. It should have an option that says "powersave". Click on that one and you're good to go
>REMINDER: You need to root first to do all of this
Click to expand...
Click to collapse
It's of course a matter of personal taste and needs, but I don't agree with the choice of Powersave Governor. I use 3C toolbox Pro to change OOM settings to a level were most services "dies" after a set time of non use, which gives a bit snappier experience and less pressure on battery. Of course you need to be careful with OOM (ram) to not "kill" to fast, loosing more multitasking power.
My battery got better and better, and now after a week of heavy use from 100% down to 5%, it lasts from 8 to 14 hours, depending on usage. Fairly good for a midrange phone.
And I do prefer the built in Cpu Governor (interactive). It's a good balance between snappiness and battery. Powersave on the other hand, will obviously save battery, but for sure also make the system slower. But as I said before, it's all up to the user and his needs and expectations.
"Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).
Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above."
nyttliv7 said:
It's of course a matter of personal taste and needs, but I don't agree with the choice of Powersave Governor. I use 3C toolbox Pro to change OOM settings to a level were most services "dies" after a set time of non use, which gives a bit snappier experience and less pressure on battery. Of course you need to be careful with OOM (ram) to not "kill" to fast, loosing more multitasking power.
My battery got better and better, and now after a week of heavy use from 100% down to 5%, it lasts from 8 to 14 hours, depending on usage. Fairly good for a midrange phone.
And I do prefer the built in Cpu Governor (interactive). It's a good balance between snappiness and battery. Powersave on the other hand, will obviously save battery, but for sure also make the system slower. But as I said before, it's all up to the user and his needs and expectations.
"Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).
Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above."
Click to expand...
Click to collapse
You're kinda right, powersave does kinda suck sometimes. I wish they had the "Conservative" governor. That works for me
Anyways, this phone has all we need to become a perfect one, as soon as we get our custom recovery ☺
I'm searching through alcatel and MSM8909 forums to see who's behind their recoveries ☺☺☺
DO NOT TRY TO INSTALL XPOSED
YOU WILL BRICK YOUR PHONES
Sent from my 5054N using Tapatalk
yea kingroot is being a pain I have 1 GB internet speed i can download anything fast except this stupid 15.3mb file when i finally got done realized it was the chinese version now have to wait another hour hope it works though
Is anyone familiar with the built in recovery mode? What limitations does it have?
I'm not sure, but if the following similarities are enough, then maybe this thread can help us experimenting?
Fierce xl:
Qualcomm MSM8909 Snapdragon 210
Quad-core 1.1 GHz Cortex-A7
Adreno 304
PIXI 3 (5) 4g:
Qualcomm MSM8909
Quad-core 1.1 GHz
Pixi 3 (5.5) LTE:
Qualcomm MSM8909 Snapdragon 200
Quad-core, 1.1 GHz Cortex A7
Adreno 304
http://forum.xda-developers.com/showthread.php?t=3193624
Can someone upload the stock dialer apk and odex for this phone?
Sent from my 5054N using Tapatalk
Remove kingroot entirely so my xl is stock again can anyone help me
I'm trying to remove the kingroot root entirely from my phone everything I get or send a picture message it does not download and open or send ever since the I ingrown was installed also emojis worked at first but no long show up please help with removal of all kingroot settings apps and return to store bought settings
mamirie2015 said:
I'm trying to remove the kingroot root entirely from my phone everything I get or send a picture message it does not download and open or send ever since the I ingrown was installed also emojis worked at first but no long show up please help with removal of all kingroot settings apps and return to store bought settings
Click to expand...
Click to collapse
were you using the newest version of kingroot? I've had none of these issues
AesopRock127 said:
were you using the newest version of kingroot? I've had none of these issues
Click to expand...
Click to collapse
As far as I know I was but I unrooted my phone but still can't download incoming pix or see emojis the emojis keyboard is there just don't show them
i just installed remix os 3.0.207 64 bit version and my laptop cpu fan is spinning at maximum speed and it is so noisy. its spin normal when i boot on windows 10, it's spinning on max speed on remix os only.
i also cant turn off the remix os, keep stuck at shutdown screen and i must force shutdown by holding the power button. please help.
my hardware :
asus rog gl552vx
core i7 6700hq
16GB ram
Nvidia GTX 950m GDDR5 4GB
i recommend to not use remix on some hardware
it does not have all the fail safe on some hardware
and it can result in thermal damage.
it could be remix does not have the driver for your computer thermal sensor
and this can explain the fan speed...
tailslol said:
i recommend to not use remix on some hardware
it does not have all the fail safe on some hardware
and it can result in thermal damage.
it could be remix does not have the driver for your computer thermal sensor
and this can explain the fan speed...
Click to expand...
Click to collapse
too bad then... i really love remix os.... especially the multitasking ability... the only problem is the fan speed and cant shutdown... hope they update the driver....
Mathvediz said:
too bad then... i really love remix os.... especially the multitasking ability... the only problem is the fan speed and cant shutdown... hope they update the driver....
Click to expand...
Click to collapse
just cap the max cpu speed
HypoTurtle said:
just cap the max cpu speed
Click to expand...
Click to collapse
how to cap it?
Mathvediz said:
how to cap it?
Click to expand...
Click to collapse
Any cpu tuner on the playstore should work fine. But maybe try kernel auditor
HypoTurtle said:
Any cpu tuner on the playstore should work fine. But maybe try kernel auditor
Click to expand...
Click to collapse
i will not in your case.
those apps are made mostly for arm.
and in the case of x86 this can result in thermal damage in your device.
i can just say we decline all responsibility in case of damage...
tailslol said:
i will not in your case.
those apps are made mostly for arm.
and in the case of x86 this can result in thermal damage in your device.
i can just say we decline all responsibility in case of damage...
Click to expand...
Click to collapse
All those apps are doing is controlling the kernel via the files in /sys [and /proc] arm/x86 has very little to do with it. The [/proc and] /sys systems are I believe pretty similar between x86 linux and arm linux.
Alternatively you can locate where the max clock rate is listed/read from and alter it yourself, but this won't persist a reboot.
As an example in my case:
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq shows the clockspeed
running echo 1 > /sys/devices/system/cpu/intel_pstate/no_turbo disables my cpu's turbo maxing the clockspeed at 800000Hz
HypoTurtle said:
All those apps are doing is controlling the kernel via the files in /sys and /proc arm/x86 has very little to do with it. The /proc and /sys systems are I believe pretty similar between x86 linux and arm linux.
Alternatively you can locate where the max clock rate is listed/read from and alter it yourself, but this won't persist a reboot.
Click to expand...
Click to collapse
the differences is:
android is mostly set up with passive cooled arm device.
x86 need active cooling.
if you reduce the cooling of your device to much
overheat will happens.
simple and logic.
android can sometime not include all the fail safe x86 use,
this is why some devices have been damaged by remix.
tailslol said:
the differences is:
android is mostly set up with passive cooled arm device.
x86 need active cooling.
if you reduce the cooling of your device to much
overheat will happens.
simple and logic.
android can sometime not include all the fail safe x86 use,
this is why some devices have been damaged by remix.
Click to expand...
Click to collapse
I see what you mean.
Though the issue seems to be the cpu running at max [likely due to temp. sense data not being read/delivered as you said]; but OP has stated the fans are running - if they weren't it would be a greater issue [and I don't recall suggesting to turn them off].
So I'd still say it's worth capping the CPU which should help with the fan noise due to the generated heat. If just changing the governor doesn't seem to be doing much. [performance gov. for example will keep cpu as high as possible]
I'm running a passively cooled core M so no fan but without disabling turbo the cpu stays at ~max [2.0GHz] and is noticeably warm.
HypoTurtle said:
I see what you mean.
Though the issue seems to be the cpu running at max [likely due to temp. sense data not being read/delivered as you said]; but OP has stated the fans are running - if they weren't it would be a greater issue [and I don't recall suggesting to turn them off].
So I'd still say it's worth capping the CPU which should help with the fan noise due to the generated heat. If just changing the governor doesn't seem to be doing much. [performance gov. for example will keep cpu as high as possible]
I'm running a passively cooled core M so no fan but without disabling turbo the cpu stays at ~max [2.0GHz] and is noticeably warm.
Click to expand...
Click to collapse
i've tried to cap the core speed with kernel auditor but the fan keep spinning at maximum speed. i didn't feel any heat from my device. kernel auditor can read the cpu temp, it ranging from 40-45C. i think remix doesn't has the driver to control the fan speed for my device. maybe sixth generation processor with ddr4 ram are not supported yet.
Mathvediz said:
i've tried to cap the core speed with kernel auditor but the fan keep spinning at maximum speed. i didn't feel any heat from my device. kernel auditor can read the cpu temp, it ranging from 40-45C. i think remix doesn't has the driver to control the fan speed for my device. maybe sixth generation processor with ddr4 ram are not supported yet.
Click to expand...
Click to collapse
yes as i said the thermal sensor is not seen by remix.
so it default by 100% fan speed.
you will need something to control directly the fan speed.
but you will have to take care you will have no fail safe if your computer is starting to overheat.
you should try android x86 to see if you have same issues with it.
some computer are just not meant to be used on android.
Mathvediz said:
i've tried to cap the core speed with kernel auditor but the fan keep spinning at maximum speed. i didn't feel any heat from my device. kernel auditor can read the cpu temp, it ranging from 40-45C. i think remix doesn't has the driver to control the fan speed for my device. maybe sixth generation processor with ddr4 ram are not supported yet.
Click to expand...
Click to collapse
As @tailslol said be careful if the heat becomes an issue. But after a spot of google-ing there is a linux bug where fans stick at 100% and 'resetting' them seems to fix it.
Code:
for i in /sys/class/thermal/cooling_device* ; do
type=`cat $i/type`
if [ "$type" = "Fan" ] ; then
echo 0 > $i/cur_state
fi
running the above flicks the fans off, they should power back up as needed after that. Test running that via termux # but make sure it doesn't create a thermal issue
HypoTurtle said:
As @tailslol said be careful if the heat becomes an issue. But after a spot of google-ing there is a linux bug where fans stick at 100% and 'resetting' them seems to fix it.
running the above flicks the fans off, they should power back up as needed after that. Test running that via termux # but make sure it doesn't create a thermal issue
Click to expand...
Click to collapse
I've tried to run the code in termux but nothing happen. i try to install remix 32 bit and everything goes normal, but remix 32 bit has slow performance, limited compatibility on some apps and can only read 3 GB of ram.
Mathvediz said:
I've tried to run the code in termux but nothing happen. i try to install remix 32 bit and everything goes normal, but remix 32 bit has slow performance, limited compatibility on some apps and can only read 3 GB of ram.
Click to expand...
Click to collapse
it was worth a try at least - kind a surpised on your experience with 32bit - any specifics regarding apps?
Device - Samsung Galaxy S4
ROM - Resurrection Remix 6.0.1_r72 (https://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-resurrection-lollipop-v5-5-5-t3195202)
Kernel - Alucard kernel repacked from https://forum.xda-developers.com/ga...p/jdcteam-optimized-cyanogenmod-14-0-t3479888
Rooted
There are no problems with software but I've put it here anyway as the instructions suggest.
My problem is the following - I've been playing with undervolting to make my battery last longer and in order to test the stability I've ran StabilityTest.
The voltages seems to be stable but I've noticed a big problem with throttling once I get into 1V domain.
The cores behave totally separately as if on a different board instead inside the same processor.
The first thing is that on idle 3 out of 4 cores will report 32-35C but the last core shows 0.
The second thing happens under a full load - The first core gets super hot very fast (up to 70 when it begins to throttle) the cores 2&3 are around 40-50C and the last core is still stubbornly locked on 0 even though it's under a full load!
It seems obvious to me that the temperature is not reported correctly but I don't know what to do about it.
Is this about thermal sensor being moved out of place or broken? Or something else?
Any advice is welcome.
A great way to reduce heat generated on the xperia 1 iii/5 iii also gain bit more battery life.
There was a debate on why the snapdragon 888 heats up and the 2 reasons most told was ''Samsung's manufacturing process'' and that the "GPU was overclocked to 800+ Mhz to excel in benchmark"
I reduced the GPU freq to 491 Mhz, I had top temp 45 Celsius, before it went past 50 Celsius . So in the end reduced a bit of CPU and GPU and got good battery life and way less hot.
First root phone.
Then install
3c cpu manager - Android Apps on Google Play
Enjoy millions of the latest Android apps, games, music, movies, TV, books, magazines & more. Anytime, anywhere, across your devices.
play.google.com
Any settings from this application is temporary, as you restart the phone the frequency are back to default, only change maximum freq nothing else don't change the governors.
My settings:
CPU 1: Max freq = 998 Mhz
CPU 2: Max Freq = 1.2 Mhz
CPU 3: Max Freq = 1.3 Mhz
GPU : Max Freq = 419 Mhz
Try and post the experience and if any improvement (Mention with region model numbers)
:-Since rooted might want to try call recording , great app. Since native sony doesn't support call recording in many regions.
Releases · chenxiaolong/BCR
A Basic Call Recorder for rooted Android devices. Contribute to chenxiaolong/BCR development by creating an account on GitHub.
github.com
Tried your settings but after reboot it doesn't stick it reverts back to original settings
Mangtas_666 said:
Tried your settings but after reboot it doesn't stick it reverts back to original settings
Click to expand...
Click to collapse
Yes it wont stick, untill you flash modified kernel it doesn't stick but if you dont reboot it wont go. Also after setting the frequency, wait for the phone to sleep once then temperature stays to a max and for me the battery life increased, without any performance degrade.
Yeah the issue is there is no modified kernel out there for our device. Kirisakura kernel does not fully support our xperia 1 iii. Sony haven't released their source code.
Try the application and if you dont like to keep the application you can remove it, still it keeps the frequency you set, till you restart the device. Main for heating up in phone is the GPU, as per what i learned, reducing its frequency itself , reduced heat a lot. Try and let know your SOT and heat temperature avg.
Yeah i have EXkernel manager it indeed lessen the heat specially when gaming.
Kirisakura kernel supports our device now..