I've been facing non responsive screen with my OnePlus 5T. The screen touch stops responding and only volume keys and power button are responsive.
Sometimes a reboot fixes the trouble but other times I have to dirty flash the stock Oxygen OS 10.0.0 zip file in TWRP recovery using OTG and mouse, to bring back the touch function to normal.
What should I do to permanently solve this trouble?
This has been a frequent problem as posted by many users here.
https://forum.xda-developers.com/oneplus-5t/help/touch-screen-5t-randomly-stops-t3888017
Well, this problem is 100% a hardware one and it is caused by the fluid of the screen digitizer. One possible cause (apart from manufacturing flaw) is the prolonged heat that is encapsulated inside the phone. That's why most people with thick protective cases and protective plastic screen film had the issue appear as soon as 4 months of usage.
You can easily prove my theory: the next time it happens again leave the phone in the fridge (not freezer) for around 10 minutes, without restarting or doing anything to it. Then see by yourself if your touchscreen has come back to normal.
The most permanent solution is to replace the AMOLED screen and use a case that is as thin as possible. Other people had success by flashing a different custom kernel (probably one that lowered the Snapdragon's power consumption) but even then some reported that it reappeared after a few months. But I think that the screen's digitzer fluid has been permanently damaged by the heat over the years of use.
So to sum up:
1. Change screen for a new one
2. Use the thinnest possible case for the phone
3. (my recommendation) Flash a slightly underclocked/undervolted kernel alongside a stock-android based custom ROM
The third step is just a precaution to prevent it from happening again.
Hope I helped to clarify the issue
BlackRazor97 said:
Well, this problem is 100% a hardware one and it is caused by the fluid of the screen digitizer. One possible cause (apart from manufacturing flaw) is the prolonged heat that is encapsulated inside the phone. That's why most people with thick protective cases and protective plastic screen film had the issue appear as soon as 4 months of usage.
You can easily prove my theory: the next time it happens again leave the phone in the fridge (not freezer) for around 10 minutes, without restarting or doing anything to it. Then see by yourself if your touchscreen has come back to normal.
The most permanent solution is to replace the AMOLED screen and use a case that is as thin as possible. Other people had success by flashing a different custom kernel (probably one that lowered the Snapdragon's power consumption) but even then some reported that it reappeared after a few months. But I think that the screen's digitzer fluid has been permanently damaged by the heat over the years of use.
So to sum up:
1. Change screen for a new one
2. Use the thinnest possible case for the phone
Click to expand...
Click to collapse
Thanks for replying @BlackRazor97. Few minutes ago, I faced this trouble again.
My screen froze and I rebooted once. The screen wasn't responding. I gave a second reboot. It started functioning again. While it was booting, I came here and went through your post. I just went through your post. Getting the screen replaced is probably going to be an expensive affair. I would rather buy a new phone but still want to continue with this one without getting any hardware replaced.
I'll surely try the fridge trick the next time it happens.
BlackRazor97 said:
3. (my recommendation) Flash a slightly underclocked/undervolted kernel alongside a stock-android based custom ROM
The third step is just a precaution to prevent it from happening again.
Hope I helped to clarify the issue
Click to expand...
Click to collapse
I have never done underclocking/undervolting before. Wouldn't it make the phone slow? Can you please suggest any reliable slightly underclocked/undervolted kernel for stock oxygen os 10.0.0 as that's the one I'm currently on. Flashing a new ROM, restoring my apps will take a long time.
archz2 said:
I have never done underclocking/undervolting before. Wouldn't it make the phone slow? Can you please suggest any reliable slightly underclocked/undervolted kernel for stock oxygen os 10.0.0 as that's the one I'm currently on. Flashing a new ROM, restoring my apps will take a long time.
Click to expand...
Click to collapse
I have only used FrancoKernel myself but since it's not available for Android 10, I recommend you to flash blu_spark r209 stable kernel for Android 10. It should work fine for stock Android 10 OOS.
https://forum.xda-developers.com/oneplus-5/oneplus-5--5t-cross-device-development/kernel-t3651933
And then by using the FKM (Franko Kernel Manager) under "battery tips" you can underclock the CPU. You don't need to underclock it too much; set it to 2Ghz (instead of 2.45Ghz) for the big cluster and 1.2Ghz for the little cluster. You will see no big difference in performance and your battery life will improve too !
Always do a backup of your stock kernel, just in case something happens.
Please let me know if it helped resolve your issue.
BlackRazor97 said:
I have only used FrancoKernel myself but since it's not available for Android 10, I recommend you to flash blu_spark r209 stable kernel for Android 10. It should work fine for stock Android 10 OOS.
https://forum.xda-developers.com/oneplus-5/oneplus-5--5t-cross-device-development/kernel-t3651933
And then by using the FKM (Franko Kernel Manager) under "battery tips" you can underclock the CPU. You don't need to underclock it too much; set it to 2Ghz (instead of 2.45Ghz) for the big cluster and 1.2Ghz for the little cluster. You will see no big difference in performance and your battery life will improve too !
Always do a backup of your stock kernel, just in case something happens.
Please let me know if it helped resolve your issue.
Click to expand...
Click to collapse
I'm quite frustrated now. I'll try flashing the blu spark and do settings with Franco Kernel Manager.
Anyway, my experience with the refrigerator trick today.
First time it worked. The other time when screen issue came up, I rebooted my phone twice, hoping to solve the problem, but it didn't happen. Then I put it in the fridge. After ten minutes, I took it out the screen wasn't responding. I rebooted it. The screen started working.
Sent from my ONEPLUS A5010 using Tapatalk
@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A5010 using Tapatalk
archz2 said:
@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?View attachment 5128013
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Yes exactly. Let the minimums as it is and lower the maximum frequencies. FKM received a big overhaul update in version 4.0, which apparently I haven't used. The menus are different but the functionality must be the same. Also don't forget to enable blu_spark blu_active governor.
Let me know if the fix is a permanent solution for you.
BlackRazor97 said:
Yes exactly. Let the minimums as it is and lower the maximum frequencies. FKM received a big overhaul update in version 4.0, which apparently I haven't used. The menus are different but the functionality must be the same. Also don't forget to enable blu_spark blu_active governor.
Let me know if the fix is a permanent solution for you.
Click to expand...
Click to collapse
Okay. Thanks. I've done it. So far so good. I have set frequencies to 1248MHz, 2112MHz. These I selected from the options pop-up. There's no way to type frequencies manually. One small query. When I do any changes in franco kernel, I don't have to reboot to apply those changes. Or should I ?
archz2 said:
@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?
Click to expand...
Click to collapse
Actually there is a battery tips tab.
And if you are interested, you can check the Lazy kernel
They say it's good.
archz2 said:
Okay. Thanks. I've done it. So far so good. I have set frequencies to 1248MHz, 2112MHz. These I selected from the options pop-up. There's no way to type frequencies manually. One small query. When I do any changes in franco kernel, I don't have to reboot to apply those changes. Or should I ?
Click to expand...
Click to collapse
Nice! Yes, I think you don't need to reboot for the settings to apply. You can check with another app like CPUZ to check if clocks go above 2112MHz. But I think you should be fine.
As for the Lazy Kernel, I don't know if it's compatible with stock Android 10 OOS. But here we don't go for the performance but we target stability and low thermals to resolve the screen issue.
BlackRazor97 said:
Nice! Yes, I think you don't need to reboot for the settings to apply. You can check with another app like CPUZ to check if clocks go above 2112MHz. But I think you should be fine.
As for the Lazy Kernel, I don't know if it's compatible with stock Android 10 OOS. But here we don't go for the performance but we target stability and low thermals to resolve the screen issue.
Click to expand...
Click to collapse
Yah there is lazy kernel for stock OOS .
Those who flashed it has high recommendations and showed low ram usage .
Before flashing lazy kernel it was 700 mb free ram usage .
After flashing lazy kernel , attached screenshot.
Rom- derpfest
I haven't flashed it yet , I will when I get time
...........
@BlackRazor97
Okay. Almost a week went by. I faced non-responsive screens in last 3-4 days but the issue got resolved by tapping mindlessly on the screen when it was locked and frequent screen unlocks. Yesterday came the issue where I rebooted the phone multiple times to make the screen respond. Today the issue also came, half an hour ago and frequent reboots didn't solve the issue. I rebooted in recovery and wiped the cache and dalvic. Then I started my phone. It responded fine. I went to Franco Kernel Manager. To my surprise, the frequencies were switched back to 2361 MHz for Big Cluster and 1824 or 1900 MHz (can't remember which one) for the Little Cluster. Now I've changed them back to 2112 MHz and 1248 MHz
How did these frequencies got back to higher number without me every touching the Kernel Manager? I didn't install any app, nothing in these days.
archz2 said:
@BlackRazor97
Okay. Almost a week went by. I faced non-responsive screens in last 3-4 days but the issue got resolved by tapping mindlessly on the screen when it was locked and frequent screen unlocks. Yesterday came the issue where I rebooted the phone multiple times to make the screen respond. Today the issue also came, half an hour ago and frequent reboots didn't solve the issue. I rebooted in recovery and wiped the cache and dalvic. Then I started my phone. It responded fine. I went to Franco Kernel Manager. To my surprise, the frequencies were switched back to 2361 MHz for Big Cluster and 1824 or 1900 MHz (can't remember which one) for the Little Cluster. Now I've changed them back to 2112 MHz and 1248 MHz
How did these frequencies got back to higher number without me every touching the Kernel Manager? I didn't install any app, nothing in these days.
Click to expand...
Click to collapse
Did you set it to set on boot my friend?
When I enable the CPU governor blu_active, I get the notification "set on boot:true", that's it. I didn't toggle any other setting. I just restarted, the frequencies are back to 2361 MHz. Is there some other place where I should set on boot ?
View attachment 5132257
archz2 said:
When I enable the CPU governor blu_active, I get the notification "set on boot:true", that's it. I didn't toggle any other setting. I just restarted, the frequencies are back to 2361 MHz. Is there some other place where I should set on boot ?
Click to expand...
Click to collapse
Do one thing this time.
Under clock both your CPU AND GPU.
Under battery life tips, check under clock both.
And click on the settings icon just near to it and set it on boot.
Check this for some days and tell me
This
rohithksaj said:
Do one thing this time.
Under clock both your CPU AND GPU.
Under battery life tips, check under clock both.
And click on the settings icon just near to it and set it on boot.
Check this for some days and tell me
Click to expand...
Click to collapse
Thanks. I've done it. I'll keep you posted.
The situation became worse after underclocking. Had to reboot twice to get the screen working. I went back to the old settings.
archz2 said:
The situation became worse after underclocking. Had to reboot twice to get the screen working. I went back to the old settings.
Click to expand...
Click to collapse
DO NOT use the automatic underclock button. This also lowers the voltage to the point it becomes unstable and we don't want this to happen. Use the typical 2112 MHz and 1248 MHz (big and little cluster accordingly).
Unfortunately, it seems that the "set on boot:true" flag is bugged. So every time you shutdown your phone, you have to re-configure to the frequencies. Let me know if you have found any better solution to keep the settings.
Related
I have a S4 mini running custom carbon kk unofficial 4.4.3 as it comes with the settings to set CPU's and governors but the phone keeps changing the min to around 1400 but the max stays at 1700.i don't notice until my battery is draining really fast or gets hot. anyone kno a fix to this?
matizkool said:
I have a S4 mini running custom carbon kk unofficial 4.4.3 as it comes with the settings to set CPU's and governors but the phone keeps changing the min to around 1400 but the max stays at 1700.i don't notice until my battery is draining really fast or gets hot. anyone kno a fix to this?
Click to expand...
Click to collapse
Which governor is it using to set a min of 1400? Ever likely it gets hot and eats power! I use f4k's kernel, and the 'Performance Control' app to look at and alter stuff - you don't say what you use or have tried.
There is a Carbon 4.4.4 available with f4ktion 1.5 kernel - might be an idea to flash that and the problem might go away!
xbin said:
Which governor is it using to set a min of 1400? Ever likely it gets hot and eats power! I use f4k's kernel, and the 'Performance Control' app to look at and alter stuff - you don't say what you use or have tried.
There is a Carbon 4.4.4 available with f4ktion 1.5 kernel - might be an idea to flash that and the problem might go away!
Click to expand...
Click to collapse
It's on every governor this happens but I use Wheatley. I would manually set it to around the 300s but in a couple of hours it would auto set at 1400 on its on. This causes my battery to drain my kernel version is 3.4.91 f4ktion 1.4.5 eur lte
matizkool said:
It's on every governor this happens but I use Wheatley. I would manually set it to around the 300s but in a couple of hours it would auto set at 1400 on its on. This causes my battery to drain
Click to expand...
Click to collapse
Strangely enough I've settled with Wheatley too! but it spends most of its time at 162 when not in deep sleep (a bit like me!). This really needs posting in the Carbon thread so I would post a few more things here to help or comment on stuff to get to 10 posts and then ask in there. I can't think what could be causing that behaviour, if it was me it would be bye bye 4.4.3 and hello 4.4.4
xbin said:
Strangely enough I've settled with Wheatley too! but it spends most of its time at 162 when not in deep sleep (a bit like me!). This really needs posting in the Carbon thread so I would post a few more things here to help or comment on stuff to get to 10 posts and then ask in there. I can't think what could be causing that behaviour, if it was me it would be bye bye 4.4.3 and hello 4.4.4
Click to expand...
Click to collapse
Yeah i flashed to 4.4.4 thanks though
Never mind above still happens even though I flashed 4.4.4
matizkool said:
Never mind above still happens even though I flashed 4.4.4
Click to expand...
Click to collapse
Does the actual minimum change rather than it simply running continually at 1400+ and if so which governor does it change to if any!
I read somewhere in the Carbon thread someone was having similar problems so they flashed the kernel twice, one directly after the other; seems something wasn't getting written correctly the first time but was the second, and the problem went away. Worth a go...
xbin said:
Does the actual minimum change rather than it simply running continually at 1400+ and if so which governor does it change to if any!
I read somewhere in the Carbon thread someone was having similar problems so they flashed the kernel twice, one directly after the other; seems something wasn't getting written correctly the first time but was the second, and the problem went away. Worth a go...
Click to expand...
Click to collapse
I found this : Q: CPU/GPU frequency doesn't stick?
A: If your frequency settings don’t stick, it's because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel feature that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues.
Is this a fix?
matizkool said:
I found this : Q: CPU/GPU frequency doesn't stick?
A: If your frequency settings don’t stick, it's because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel feature that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues.
Is this a fix?
Click to expand...
Click to collapse
It could help. Trickster is good. However, this suggests that there is something else causing or forcing the frequency setting to be changed. The question is what? and I've no idea:crying:
Haha I found the problem it was either this battery saver app or I changed to scheduler to anything besides row
matizkool said:
Haha I found the problem it was either this battery saver app or I changed to scheduler to anything besides row
Click to expand...
Click to collapse
Thats good. It was probably the battery saver because they usually do the opposite!
I got really annoying problem here...is anyone check this or never encounter the problem i faced...it seems i cant get the most out of my mi max when needed...when playing games and watch 1080p video, small core stuck at 1017mhz and big cores stuck at 1190mhz..ive change it several times but nothing happened...because of this i got stuttering when playing video and games....ive check the temp throttle, and dissable all of it...but the problem still persist...ive test it with miui globerom and mm rr....same problem with both rom...
how can i get small cores to min 400mhz, max 1401mhz and big cores 400mhz, max 1804mhz when i needed it...
Here some sample image when im playing games and watching 1080p video.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And also my big and small cores setting...i dont fiddle with anything on it..
As much as I see your cores do reach peek clock frequencies I also see a lot of bad configured tunables in interactive governor setup you are using especially timer rates.
Don't have much time now to explain or adjust it me by later today. & I don't know from where you got your config as it have CPU frequencies that are not supported by S65x SoC's so plenty of problems there to start with.
Zola III said:
As much as I see your cores do reach peek clock frequencies I also see a lot of bad configured tunables in interactive governor setup you are using especially timer rates.
Don't have much time now to explain or adjust it me by later today. & I don't know from where you got your config as it have CPU frequencies that are not supported by S65x SoC's so plenty of problems there to start with.
Click to expand...
Click to collapse
It reaches peak at normal usage from time to time but when playing games oland watching videos, the cores stuck at 1017mhz for small cores and 1190mhz for big cores...small cores max have 1401mhz and big got 1804mhz...so there s a difference in performance when in trottle down like that...ive ask some other users....but they also have the same config as mine...this is the stock config for globerom and ive never change it....
If you can give a screenshots of your config, i would be glad to test it if it work on my device...
Sorry the first 2 pictures doesn't show clearly...
Why dont just stay with stock settings? The little cores are configure really bad
donalberto17 said:
Why dont just stay with stock settings? The little cores are configure really bad
Click to expand...
Click to collapse
I dont know what stock setting config are...this is the setting i got when flashing the rom....so probably its the roms fault?...or maybe some mode causing this....if i flash the rom again, maybe it will be fixed...?
Can i get any example setting for me to fix it...
Put;
Above high speed delay
40000 900000:60000
Go high speed load
90
Min sample time
20000
Boost pulse durilation
40000
Hi speed freq
900000
Target loads
90 600000:95 900000:97 1100000:97
(delate other entries in target loads)
Timer slack 40000
For the big cluster do it like this:
Above high speed delay
40000 1382400:60000
Go high speed load
90
Min sample time
20000
Boost pulse durilation
40000
Hi speed freq
1382400
Target loads
90 1382400:97
Timer slack 40000
Should be much more snapper, balanced, power aware with a good performance.
Don't charge anything else & in a couple of days tell me how you feel about it.
Have to add that used Interactive is rather old & doesn't have some tunables.
Best regards.
And one more thing...is it advisable to use L speed to improve the cpu load....or might it interfere with the manual setting...
martin132014 said:
And one more thing...is it advisable to use L speed to improve the cpu load....or might it interfere with the manual setting...
Click to expand...
Click to collapse
My advice is that you don't use anything that you can not check in code what exactly it's doing. L speed shifted away from using scripts long ago so I don't recommend using it.
Edit:
You can try HEBF if you wish it still uses scripts.
http://forum.xda-developers.com/and...ebf-tweaking-battery-saver-optimizer-t3401341
Zola III said:
My advice is that you don't use anything that you can not check in code what exactly it's doing. L speed shifted away from using scripts long ago so I don't recommend using it.
Click to expand...
Click to collapse
Thanks...ive used your setting, and test it to the extent of my phone....the performance is great...but unfortunately, it still the same...the cores will gradually tuned down automatically to 1190 big and 1017 small, max value....even everything i do, it will stay in that state...and also, one of the big cores will offline for no reasons...so i just have to operate my phone with 5 cores online only for any big resources app....in the end, stuttering will appear...
Ive also checked that i cant change the governor either...it stuck at interactive....this things occur if the battery and cpu heats up to 38-40°....at 40°, all cores is lock away from any setting...ive tried to diactivate all the temperature throttle...but its the same...no effect...still lock....then if the rom is the culprit, then ive used RR rom and Miui GlobeRom...2 of a different Rom all together...still persist this problem...so im stuck to dont know what to do rather than flash unmodified stock rom and see whats happened...
martin132014 said:
Thanks...ive used your setting, and test it to the extent of my phone....the performance is great...but unfortunately, it still the same...the cores will gradually tuned down automatically to 1190 big and 1017 small, max value....even everything i do, it will stay in that state...and also, one of the big cores will offline for no reasons...so i just have to operate my phone with 5 cores online only for any big resources app....in the end, stuttering will appear...
Ive also checked that i cant change the governor either...it stuck at interactive....this things occur if the battery and cpu heats up to 38-40°....at 40°, all cores is lock away from any setting...ive tried to diactivate all the temperature throttle...but its the same...no effect...still lock....then if the rom is the culprit, then ive used RR rom and Miui GlobeRom...2 of a different Rom all together...still persist this problem...so im stuck to dont know what to do rather than flash unmodified stock rom and see whats happened...
Click to expand...
Click to collapse
First of all all monitoring apps aren't real-time secondly they some times have the problem with displaying correct informations for 2,3,4th cores on the big cluster (I don't know why) falls displaying how they don't work but believe me they do. Tried to do a bit of monitoring my self & depending of game & or video player the cpu utilisation varies but little cores do meet their max frequency when needed & big ones do stay around 1200MHz when used but if you ask me that is perfectly normal & desired actually if it whose otherwise you would got thermal throttling. So this doesn't have to do anything with thermals nor CPU governor, it's probably imposed by the cpu ctr driver. I don't know where you got idea how any of this is crucial for either gaming or (good forgive) video playback; for GPU its crucial that one of CPU clusters (or with hot plug at least one core) scale along as it determines the RAM frequency, on the other hand video decoding (for supported formats) it's done on a DSP so it's desirable to CPU's actually stay as much as they can on active idle frequencies (periodically syncing system tasks) if you use unsupported video compression or for some other case choose to use software video decoder then CPU's jump to full frequency as they get utilised.
Zola III said:
First of all all monitoring apps aren't real-time secondly they some times have the problem with displaying correct informations for 2,3,4th cores on the big cluster (I don't know why) falls displaying how they don't work but believe me they do. Tried to do a bit of monitoring my self & depending of game & or video player the cpu utilisation varies but little cores do meet their max frequency when needed & big ones do stay around 1200MHz when used but if you ask me that is perfectly normal & desired actually if it whose otherwise you would got thermal throttling. So this doesn't have to do anything with thermals nor CPU governor, it's probably imposed by the cpu ctr driver. I don't know where you got idea how any of this is crucial for either gaming or (good forgive) video playback; for GPU its crucial that one of CPU clusters (or with hot plug at least one core) scale along as it determines the RAM frequency, on the other hand video decoding (for supported formats) it's done on a DSP so it's desirable to CPU's actually stay as much as they can on active idle frequencies (periodically syncing system tasks) if you use unsupported video compression or for some other case choose to use software video decoder then CPU's jump to full frequency as they get utilised.
Click to expand...
Click to collapse
For monitoring real time cores, i go to development option and select Show cpu usage option....that i think doesn't lie....the problem im facing is that why doest the cores doesn't stick to selected frequency....ive never seen it do that on other phone before...even when the phone heats or overclock...theres always for us to change it manually if we want to..so for my case, its not like that...it persistently selected what it want...
The problem im facing is in fact a video playback...Hevc x265 1080p 24fps.....so if your aware, hevc is a new encoder for video playback with lower size but better quality...but to run it, it needed more processing power...ive tried with same format but with 720p only...it runs flawlessly...so i assume 1080p will do the same....but in this case...its not....yes the video only support software decoding...and i used mx player for it...since it support it, ive set it to run at max performance....to run all cores to play video...
Ive run the video at 34° battery and cpu...small cores run max clock...and also 2 big cores run max 1800mhz....the video runs smoothly...until the temp reaches 37° the big cores start to slow down to 1600mhz....then after a while 39° 1190mhz....then the video start stuttering badly until in unwatchable....
So this behavior of big+small cores is for me kinda unnatural or is it, it supposed to be acting like that...i dont know...this is the first cluster core phone i ever used...so if it supposed to be acting like that, then are we getting the most out of the phone performance if it always dumb down like that...
Monitoring does lie (check by running Volumark bench when it happens) & that temperature/frequency down scaling is not normal behaviour.
I do know what H265 is (& even how it works) I also know both hardware (QC) and software (Google) libs on firmware are broken for it (surprisingly Vp9 just works fine). I still think how H265 full profile FHD culd be a little to much for a CPU alone.
Zola III said:
Monitoring does lie (check by running Volumark bench when it happens) & that temperature/frequency down scaling is not normal behaviour.
I do know what H265 is (& even how it works) I also know both hardware (QC) and software (Google) libs on firmware are broken for it (surprisingly Vp9 just works fine). I still think how H265 full profile FHD culd be a little to much for a CPU alone.
Click to expand...
Click to collapse
That's why im scratching my head all this time...ok ill do some research more and post if anything new or if im able to solve it...thanks for the knowledge...
Just for curiosity...i ran Volumark at cool temp 32° and all cores run well....got 72 at Volumark.
But i run again with temp 38° and my cores, like i said earlier, big cores max at 1200mhz and the other one offline...got 39 at Volumark.
martin132014 said:
Just for curiosity...i ran Volumark at cool temp 32° and all cores run well....got 72 at Volumark.
But i run again with temp 38° and my cores, like i said earlier, big cores max at 1200mhz and the other one offline...got 39 at Volumark.
Click to expand...
Click to collapse
As I told you that isn't normal behaviour. I would re flash firmware or better yet if you have a full backup in recovery if I whose you.
This is my logcat...if someone have some free time or care to help me solve my problem, care to take a look...
Im hoping someone could provide me an answer for me to fix my problem im having...i dont think i can live with a phone that behave like this...
Im not able to read it and hoping someone can...just post it here.
I take this log out from kernel audiutor...so i hope thats ok..
https://drive.google.com/folderview?id=0B5jpDdyf-VE_bC13T0lValF2d1U
Uffff. Log didn't show much at least not reasonable to me. There are cuple of IO denials at the end. Did look last cuple of pages. It's really hard to get to the bottom of this, actually impossible regarding how much potential problematic things you are using, from xposed framework to the fact that you are on beta MiUI relase to the fact you used various tuning apps that changed the behaviour. Sorry but I cant really help you. If this persist after flashing full official stable firmware freshly then try to catch the fresh logcat right afterwards down frequency cpu happens along with screanshots, post it hire and fail the official bug report at MiUI forums (with a screanshots & logcat attached).
Best regards.
https://drive.google.com/folderview?id=0B5jpDdyf-VE_bC13T0lValF2d1U
Well, i did a fresh install but using latest Official dev Rom, did not touch nothing or change anything on the rom after install...just install couple of apps and do the test....but unfortunately, the problem still there....
Here are the fresh log cat, if your wanna take a look and feedback...this is the last time i think...i will try to contact post it on Miui forum as well.
This morning my Pixel C felt slow and sluggish.
Rebooted and removed recently installed apps but no difference.
Installed a CPU monitoring app and see that the CPU stays at 204Mhz even under load.
Any ideas before I try a full wipe?
Full reset seems to have fixed though notice cpu maxes at 1326
This right?
I'm not sure most CPU monitors know what to do with the X1, I know CPU-Z doesn't recognize it beyond a general "Nvidia Tegra" chip. What app are you using?
I switched from AOSP for acbit but yesterday had the same issue. Tablet felt slow and sluggish.
CPU monitor app showed CPU not scaling.
Went back to stock Oreo and still "feels" slow.
Geekbench4 says single core 926 and multi 2561
This is wrong?
My Pixel C performance is strange still the OREO update. I know this going to sound weird but when in splitscreen, the app on the left in landscape or on the top in portrait is lagging a lot. Scrolling, page swiping, etc.. takes a distinct longer time than expected. The app in the other half of the screen is acting normally.
Could this be related to the same issue?
With the pixel C now discontinued, Google is unlikely to fix a bug, especially if nobody reports it.. Bit of a worry, what to do?
I'm facing this issue as well. Already wiped cache and did factory reset, with no results.
It's now a very fancy digital picture frame.
There is no such problem. I used the first available monitoring program (cpufloat) and the CPU frequency change is shown adequately.
https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat
Vartom said:
There is no such problem. I used the first available monitoring program (cpufloat) and the CPU frequency change is shown adequately.
https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat
Click to expand...
Click to collapse
Thanks - in that case, the issue is less obvious to spot but I have definitely noted a lag in split screen mode refreshing the app on the left (yes, I know how strange it sounds..).
In addition, there have been quite a few report of the new January patch release affecting Pixel (phones) users. I can't help thinking our Pixel C issue with the last update and these new issues are too much of a coincidence..
I am hoping Jan patch might fix my Pixel C issue...
L
laurentbon said:
Thanks - in that case, the issue is less obvious to spot but I have definitely noted a lag in split screen mode refreshing the app on the left (yes, I know how strange it sounds..).
In addition, there have been quite a few report of the new January patch release affecting Pixel (phones) users. I can't help thinking our Pixel C issue with the last update and these new issues are too much of a coincidence..
I am hoping Jan patch might fix my Pixel C issue...
L
Click to expand...
Click to collapse
At the moment I'm using the kernel I've modified, and I have no problem with scrolling on the left side of the screen in split screen mode.
you can try it.
Install Kernel Auditor and deselect CPU Multi-core power saving option in CPU tab, that was on for some reason.
MrPhilo said:
Install Kernel Auditor and deselect CPU Multi-core power saving option in CPU tab, that was on for some reason.
Click to expand...
Click to collapse
For what? if the frequency control and so works normally
Just updated January-ota and nothing has been solved... What can we do to make google solve it. The bug with the navbar continues and the split-screen is impossible to use
I started a thread when I noticed this bugs
https://forum.xda-developers.com/pixel-c/help/bugs-android-8-1-t3718156
AlfreGarcia98 said:
Just updated January-ota and nothing has been solved... What can we do to make google solve it. The bug with the navbar continues and the split-screen is impossible to use
I started a thread when I noticed this bugs
https://forum.xda-developers.com/pixel-c/help/bugs-android-8-1-t3718156
Click to expand...
Click to collapse
https://issuetracker.google.com/issues?q=componentid:190923+ Click "Create Issue" Report the bugs in detail how to replicate etc Someone from the dev team should get back to you
liam_davenport said:
https://issuetracker.google.com/issues?q=componentid:190923+ Click "Create Issue" Report the bugs in detail how to replicate etc Someone from the dev team should get back to you
Click to expand...
Click to collapse
I dont know why, but the blue buttons are unclickable for me, so I cant create the issue.
Bringing back from dead.
So if you use Kernel Auditor to turn off some of the cores when this is occurring, the clock speed goes up for the primary core. It's as if they set a total limit, then divide by total core count. When battery charge is above 67%, you get the full max speed. No reboot or anything, just charge it up and you unlock the speed again. I suspect the Oreo kernels have bad throttling algorithm for this CPU.
My Pixel C was lagging quite bad when the battery fell below 67% using stock 8.1 (locked bootloader, everything untouched). I tried reflashing the factory images, but the problem stuck around. I rooted (magisk 18.1) and installed Kernel Adiutor. The problem was obvious, the CPU would heavily throttle (under 67% battery) depending on the amount of core active (with 4 cores, they would all run at ~200 mhz, with 2 cores, about 700 mhz and with 1 core about 1100 mhz). It wasn't so terribly laggy with 1 core running at 1100 mhz, but it was still pretty slow.
To try and troubleshoot the problem I then installed LineageOS 15.1 and followmsi's kernel (https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591). To my surprise the problem remained, despite the custom ROM and custom kernel. I think there is something wrong with the 8.1 oreo kernel and the Pixel C (see google forum post here: https://productforums.google.com/forum/#!msg/nexus/x7izNIUIHeI/VO4n9l_DCAAJ ). So I tried a second solution. This time I did the following:
1. Flashed TWRP: twrp-3.2.3-0-dragon.img
2. Flashed in TWRP: Followmsi's unoffical lineageOS 16.0: lineage-16.0-20190206-UNOFFICIAL-dragon.zip
3. Flashed in TWRP: (same session, before booting into LineageOS): OpenGAPPS Arm64 Pico package: open_gapps-arm64-9.0-pico-20190302.zip (m
4. Flashed in TWRP: (same session, before booting into LineageOS): Followmsi's Android 9 custom kernel: tegra-3.18_kernel_pie_dragon_v190205_unicorn-xceed-followmsi.zip
And voila, back to full speed. In fact the tablet seems to run better than ever. After some testing I installed Magisk 18.1 (for root and to pass safetynet), and everything is running great. The CPU's now appear to be managed properly by the 9.0 kernel. I'd recommend anyone experiencing this problem to go ahead with what I outlined above. Alternatively, if you're not comfortable with custom roms, you can install the last Android 7.1 build (ryu-n2g48c-factory-0bc0ee15.zip - guide here: https://mmikowski.github.io/pixelc-revert-nougat/).
Hope this helps.
So just today, I realized I was under clocking my phone's CPU at 1920 mHz instead of the base clock speed of 2150 mHz which basically meant I was limiting its performance. Realizing this, I called myself an idiot and was also excited to see my benchmarks at base clock since its 165K using antutu when under clocked. So I changed my clock speed back to 2150 mHz and started benchmarking. All was going well until around 80% of the benchmark when the screen just instantly turned off and the notification light dimly lit up, no warnings, just instant. I can't interact with my phone until I forced restart it. I under clocked my phone again if it still has the same issue but benchmarking worked out just fine. Any idea why this happened and is there any fix? I really want to know my benchmarks at 2150 mHz ;-;
Ps: idk how to call website admins but please tell them to fix their website for PCs, can't even login since text boxes are missing, can't make a new thread since title input text box is missing when making new thread. Everything is fine on phone tho.
ZeeSmilez said:
So just today, I realized I was under clocking my phone's CPU at 1920 mHz instead of the base clock speed of 2150 mHz which basically meant I was limiting its performance. Realizing this, I called myself an idiot and was also excited to see my benchmarks at base clock since its 165K using antutu when under clocked. So I changed my clock speed back to 2150 mHz and started benchmarking. All was going well until around 80% of the benchmark when the screen just instantly turned off and the notification light dimly lit up, no warnings, just instant. I can't interact with my phone until I forced restart it. I under clocked my phone again if it still has the same issue but benchmarking worked out just fine. Any idea why this happened and is there any fix? I really want to know my benchmarks at 2150 mHz ;-;
Ps: idk how to call website admins but please tell them to fix their website for PCs, can't even login since text boxes are missing, can't make a new thread since title input text box is missing when making new thread. Everything is fine on phone tho.
Click to expand...
Click to collapse
Its kernel panic
JV Spartacus said:
Its kernel panic
Click to expand...
Click to collapse
Kernel panic? How can i fix it?
ZeeSmilez said:
Kernel panic? How can i fix it?
Click to expand...
Click to collapse
Reboot should fix it .If not install boot.img from the custom rom file u have installed or use custom kernel if u like
JV Spartacus said:
Reboot should fix it .If not install boot.img from the custom rom file u have installed or use custom kernel if u like
Click to expand...
Click to collapse
Im using nameless kernel. I now just remember having this same problem before and rebooting doesn't work, and i also remember that this problem is the reason why i underclocked my phone. The only thing that caused a kernel panic so far is antutu, probably geekbench too but i can't properly remember.
ZeeSmilez said:
Im using nameless kernel. I now just remember having this same problem before and rebooting doesn't work, and i also remember that this problem is the reason why i underclocked my phone. The only thing that caused a kernel panic so far is antutu, probably geekbench too but i can't properly remember.
Click to expand...
Click to collapse
If the phone temperature gets high it shuts itself to protect the device
JV Spartacus said:
If the phone temperature gets high it shuts itself to protect the device
Click to expand...
Click to collapse
Phone doesn't get really hot when benchmarking though
Hello,
I've been having a terrible problem ever since I tried the ArrowOS Android 12 ROM. I noticed that my phone was notably less smooth when scrolling and it had an ever so slight delay to touch that was infuriating, it's not really that visible but it makes the phone feel very sluggish. Scrolling/flinging would result in a lot of stuttering as well.
I poked around and inspected the kernel, and it seems like there's something wrong with the values for the CPU since the maximum the CPU will go to is 2750 on the fastest core instead of 3.2 and 2250 on the big cores (the LITTLE cores are at 1.8ghz max as intended). Now of course this still shouldn't mean the phone should lag as a snapdragon 870 even at those speeds is plenty fast for things like reddit and youtube and such, but I think this might be related to my problem with the smoothness of the UI.
I've since tried going back to official LineageOS 18.1 but the CPU was still stuck to the lower values and the UI was still not smooth. I've tried going back to the latest global fastboot ROM as well but even on full stock, when installing the fastboot rom through Miflash and doing everything clean, the CPU is stuck at these lower values and the smoothness is affected.
What exactly is wrong with my phone? I also tried a few different kernels and none of them were able to go back to the default SD870 settings. The kernel manager shows the maximum values in the dropdown but if I choose to set them as the maximum CPU frequency, they just revert back as soon as the screen refreshes. Setting the scheduler to performance just sticks the frequency to 2750/2250/1800 at all times, it just won't go to 3200/2500/1800 at all.
Is there any way this can be remedied? Has anyone ever experienced this with a phone? I tried goggling it and found nothing...
Thanks for any answers!
companyja said:
Hello,
I've been having a terrible problem ever since I tried the ArrowOS Android 12 ROM. I noticed that my phone was notably less smooth when scrolling and it had an ever so slight delay to touch that was infuriating, it's not really that visible but it makes the phone feel very sluggish. Scrolling/flinging would result in a lot of stuttering as well.
I poked around and inspected the kernel, and it seems like there's something wrong with the values for the CPU since the maximum the CPU will go to is 2750 on the fastest core instead of 3.2 and 2250 on the big cores (the LITTLE cores are at 1.8ghz max as intended). Now of course this still shouldn't mean the phone should lag as a snapdragon 870 even at those speeds is plenty fast for things like reddit and youtube and such, but I think this might be related to my problem with the smoothness of the UI.
I've since tried going back to official LineageOS 18.1 but the CPU was still stuck to the lower values and the UI was still not smooth. I've tried going back to the latest global fastboot ROM as well but even on full stock, when installing the fastboot rom through Miflash and doing everything clean, the CPU is stuck at these lower values and the smoothness is affected.
What exactly is wrong with my phone? I also tried a few different kernels and none of them were able to go back to the default SD870 settings. The kernel manager shows the maximum values in the dropdown but if I choose to set them as the maximum CPU frequency, they just revert back as soon as the screen refreshes. Setting the scheduler to performance just sticks the frequency to 2750/2250/1800 at all times, it just won't go to 3200/2500/1800 at all.
Is there any way this can be remedied? Has anyone ever experienced this with a phone? I tried goggling it and found nothing...
Thanks for any answers!
Click to expand...
Click to collapse
the freqs that you report are normal. Most of the roms that i have tried do not go above 2750. They are underclocked a lil. So no issues with your device
m0lly. said:
the freqs that you report are normal. Most of the roms that i have tried do not go above 2750. They are underclocked a lil. So no issues with your device
Click to expand...
Click to collapse
I understand that default kernels might want to underclock a little but I am literally unable to change these settings and my UI is not smooth at all so I am having a problem, I don't want to unlock the frequencies just for benchmarks or whatever. I am unable to change these frequencies even on the stock global ROM on a fresh fastboot install, I don't think that's normal?
companyja said:
I understand that default kernels might want to underclock a little but I am literally unable to change these settings and my UI is not smooth at all so I am having a problem, I don't want to unlock the frequencies just for benchmarks or whatever. I am unable to change these frequencies even on the stock global ROM on a fresh fastboot install, I don't think that's normal?
Click to expand...
Click to collapse
that happened with me too. Simple fix was to flash china fastboot *pls do not lock the bootloader on china* just flash and see. The freqs came back to normal for me and switching between freqs works. btw take it easy it'll def be back to normal, try this out^^^
m0lly. said:
that happened with me too. Simple fix was to flash china fastboot *pls do not lock the bootloader on china* just flash and see. The freqs came back to normal for me and switching between freqs works. btw take it easy it'll def be back to normal, try this out^^^
Click to expand...
Click to collapse
I actually just started downloading the Chinese rom to try this...thanks for the heads up now I feel a bit more confident in this stupid idea just to be sure I am downloading the Redmi K40 fastboot rom from here - I can't find the development ROM for alioth otherwise; am I doing it wrong?
companyja said:
I actually just started downloading the developer rom to try this...thanks for the heads up now I feel a bit more confident in this stupid idea just to be sure I am downloading the Redmi K40 fastboot rom from here - that is the latest development ROM for alioth, right?
Click to expand...
Click to collapse
yep looks good just don't lock it
Will this reproduce when flashing anything else than china fastboot rom? Or is it some particular ROMs that will bottle CPU freqs? Sound serious if true, can we actually confirm any of this?
I can confirm that the latest chinese ROM also has these same frequencies. The only time I was able to get the proper CPU values out of my CPU and a smooth experience is when booting a copy of 15.2.1.0 - it's not related to any app since I tried multiple apps to display CPU info, and when using the CPU throttling test, only 12.5.1.0 allows the CPU to get up to 3.2/2.5.
I tried installing LOS over 12.5.1 but it still locks to 2750/2250. Flashing over 12.5.1.0 firmware onto the LOS install also does nothing. I tried putting the 12.5.4.0 kernel (boot.img) over the 12.5.1.0 ROM to see if the kernel alone makes the difference, but aside not being able to use the network with the 12.5.4.0 kernel, the speeds are still unlocked on 12.5.1.0 with the 12.5.4.0 boot.img. It's smelling awfully like Xiaomi locked down the performance of the SD870 to increase battery life/reduce temperatures at some point between 12.5.1.0 and 12.5.4.0 (I haven't tried 12.5.2.0 yet). I remember LineageOS not having this problem when I switched to Arrow in early novermber but Arrow had it out the gate (but I decided to stick with it to try Android 12 out).
Barring some strange inconcievable problem with my device alone it seems awfully like something Apple would do backhandedly, restricting your CPU through the software just-cause. It doesn't seem like it's a kernel or a firmware change but something deeper, as flashing over both from other versions do not change this behavior - it's locked down on some level that doesn't seem as easy to unlock. I don't want to be alarming but I am at a loss right now and I'll probably use 12.5.1.0 till I can find a more sensible solution. I might try installing an old version of LineageOS later to see whether it locks the speeds down, and to try and see which version triggers the newer values.
companyja said:
I can confirm that the latest chinese ROM also has these same frequencies. The only time I was able to get the proper CPU values out of my CPU and a smooth experience is when booting a copy of 15.2.1.0 - it's not related to any app since I tried multiple apps to display CPU info, and when using the CPU throttling test, only 12.5.1.0 allows the CPU to get up to 3.2/2.5.
I tried installing LOS over 12.5.1 but it still locks to 2750/2250. Flashing over 12.5.1.0 firmware onto the LOS install also does nothing. I tried putting the 12.5.4.0 kernel (boot.img) over the 12.5.1.0 ROM to see if the kernel alone makes the difference, but aside not being able to use the network with the 12.5.4.0 kernel, the speeds are still unlocked on 12.5.1.0 with the 12.5.4.0 boot.img. It's smelling awfully like Xiaomi locked down the performance of the SD870 to increase battery life/reduce temperatures at some point between 12.5.1.0 and 12.5.4.0 (I haven't tried 12.5.2.0 yet). I remember LineageOS not having this problem when I switched to Arrow in early novermber but Arrow had it out the gate (but I decided to stick with it to try Android 12 out).
Barring some strange inconcievable problem with my device alone it seems awfully like something Apple would do backhandedly, restricting your CPU through the software just-cause. It doesn't seem like it's a kernel or a firmware change but something deeper, as flashing over both from other versions do not change this behavior - it's locked down on some level that doesn't seem as easy to unlock. I don't want to be alarming but I am at a loss right now and I'll probably use 12.5.1.0 till I can find a more sensible solution. I might try installing an old version of LineageOS later to see whether it locks the speeds down, and to try and see which version triggers the newer values.
Click to expand...
Click to collapse
brah those are the freqs on all roms 2750 is super normal
btw china flash was only to fix switching between freqs if they were stuck
I'm really happy that it's normal however for me it's causing stuttering which is obviously a problem. And either way being fine with your device being arbitrarily locked down is absolutely bizarre to me but maybe that's just me
the change that you're talkin abt from 3.2 to 2750 was always the case with custom roms iirc
companyja said:
I'm really happy that it's normal however for me it's causing stuttering which is obviously a problem. And either way being fine with your device being arbitrarily locked down is absolutely bizarre to me but maybe that's just me
Click to expand...
Click to collapse
stuttering happens on my end too but thats dynamic refresh rate and other things btw stutter happens even on stock meme
I'm really not sure what your specific issues are but I think I was pretty clear in my first post that the device was working smoothly till I switched to Arrow OS with Android 12, and it works smoothly on stock 12.5.1.0 for me. I'm sure a lot of ROMs stutter a lot (I haven't installed a custom ROM yet that doesn't allow you to force the refresh rate to 60/90/120 anyway) but this wasn't the case with roms such as LineageOS for me before but it seems to be now; sadly the earliest build I can download is 13/11, I wish I saved some of the old builds I had
companyja said:
I'm really not sure what your specific issues are but I think I was pretty clear in my first post that the device was working smoothly till I switched to Arrow OS with Android 12, and it works smoothly on stock 12.5.1.0 for me. I'm sure a lot of ROMs stutter a lot (I haven't installed a custom ROM yet that doesn't allow you to force the refresh rate to 60/90/120 anyway) but this wasn't the case with roms such as LineageOS for me before but it seems to be now; sadly the earliest build I can download is 13/11, I wish I saved some of the old builds I had
Click to expand...
Click to collapse
so you still have max freqs on 12.5.1.0?
Yes 12.5.1.0 has the stock frequencies; 12.5.4.0 has locked down frequencies. Haven't tried 12.5.2.0 (this is all Global ROMs)
companyja said:
Yes 12.5.1.0 has the stock frequencies; 12.5.4.0 has locked down frequencies. Haven't tried 12.5.2.0 (this is all Global ROMs)
Click to expand...
Click to collapse
i will try flashin 12.5.1.0 and see
After updating I can confirm 12.5.2.0 is the last known good version with the default maximum clocks. The ROM runs super smoothly and it's a joy to use, if only you could disable dynamic refresh on MIUI...
I've tried two other roms but they both had the new values. I really don't know why there is no option to boost the clocks manually via a kernel manager/different kernel, but even aside from the advertised clocks and all that this has really affected the smoothness of my F3; does anyone have an up-to-date AOSP ROM that has normal clocks? You can check with a kernel manager/downlod CPU Throttling Test and see the maximum clocks you get as soon as you press start.
companyja said:
After updating I can confirm 12.5.2.0 is the last known good version with the default maximum clocks. The ROM runs super smoothly and it's a joy to use, if only you could disable dynamic refresh on MIUI...
I've tried two other roms but they both had the new values. I really don't know why there is no option to boost the clocks manually via a kernel manager/different kernel, but even aside from the advertised clocks and all that this has really affected the smoothness of my F3; does anyone have an up-to-date AOSP ROM that has normal clocks? You can check with a kernel manager/downlod CPU Throttling Test and see the maximum clocks you get as soon as you press start.
Click to expand...
Click to collapse
can confirm 12.5.1.0 *tried the indian one* max freqs on all cores btw there are some thermals that do you help you get max freqs on cpu and dynamic clocks on gpu you'll have to check tg for that
I also had this issue with arrow 12 and a bunch of other AOSP roms (with terrible antutu and geekbench results), but it's OK with latest version of xiaomi.eu (12.5.18.0.RKHCNXM)
Here is the antutu results. in arrow it was around 602000!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
companyja said:
Hello,
I've been having a terrible problem ever since I tried the ArrowOS Android 12 ROM. I noticed that my phone was notably less smooth when scrolling and it had an ever so slight delay to touch that was infuriating, it's not really that visible but it makes the phone feel very sluggish. Scrolling/flinging would result in a lot of stuttering as well.
I poked around and inspected the kernel, and it seems like there's something wrong with the values for the CPU since the maximum the CPU will go to is 2750 on the fastest core instead of 3.2 and 2250 on the big cores (the LITTLE cores are at 1.8ghz max as intended). Now of course this still shouldn't mean the phone should lag as a snapdragon 870 even at those speeds is plenty fast for things like reddit and youtube and such, but I think this might be related to my problem with the smoothness of the UI.
I've since tried going back to official LineageOS 18.1 but the CPU was still stuck to the lower values and the UI was still not smooth. I've tried going back to the latest global fastboot ROM as well but even on full stock, when installing the fastboot rom through Miflash and doing everything clean, the CPU is stuck at these lower values and the smoothness is affected.
What exactly is wrong with my phone? I also tried a few different kernels and none of them were able to go back to the default SD870 settings. The kernel manager shows the maximum values in the dropdown but if I choose to set them as the maximum CPU frequency, they just revert back as soon as the screen refreshes. Setting the scheduler to performance just sticks the frequency to 2750/2250/1800 at all times, it just won't go to 3200/2500/1800 at all.
Is there any way this can be remedied? Has anyone ever experienced this with a phone? I tried goggling it and found nothing...
Thanks for any answers!
Click to expand...
Click to collapse
Is that correct?