Hello guys:
I've a strange behaviour of cpu. After a while, the Little CPU stuck at 1401 mhz like min frequency. It's not the same problem that stucks in max freq.
I don't know why it is. I have a theory .. when I connect the USB Type C adaptor to headphones or the USB cable to charge, after a while the cpu rises the low freq from 633 mhz to 1401 mhz and stucks here like the min freq.
Somebody with a similar issue or solution?
Thanks a lot!
is your phone FP sensor is FPC ?
they also have CPU stuck bug but only 4 Little CPU stuck.
it occasionally happen when use FP to wakeup from deepsleep or wakeup while Quick charging.
Just checked my little cores and they were stuck at 1401. Restarted the phone and they are back to 633 MHz, and now no matter what I try (unlocking several times with FP, from deep sleep and what not) I can't get them stuck at 1401 again. Could it be something else?
I got the FPC sensor, running September patch.
upcita said:
is your phone FP sensor is FPC ?
they also have CPU stuck bug but only 4 Little CPU stuck.
it occasionally happen when use FP to wakeup from deepsleep or wakeup while Quick charging.
Click to expand...
Click to collapse
Yeah.. when I disconnect the charger I have to reset because stucks at 1401.. what can I do?
prokaryotic cell said:
Just checked my little cores and they were stuck at 1401. Restarted the phone and they are back to 633 MHz, and now no matter what I try (unlocking several times with FP, from deep sleep and what not) I can't get them stuck at 1401 again. Could it be something else?
I got the FPC sensor, running September patch.
Click to expand...
Click to collapse
Please try when you disconnect your phone before charging or listen music with earphones with jack 3.5 mm adaptator. The CPU back to stucks at 1401.
MarianoGarcia84 said:
Please try when you disconnect your phone before charging or listen music with earphones with jack 3.5 mm adaptator. The CPU back to stucks at 1401.
Click to expand...
Click to collapse
I've charged and used the headphone adapter multiple times since the last reboot and my little cores still go all the way down to 633MHz.
I have only noticed this bug once and have not been able to reproduce it, it's very rare and inconsistent for me
I still have 1401Mhz stuck problem. Did anyone solve it?
do you resolve it after restart?
I do. something is triggering it at my device but I'm unable to understand what. It's not often I get it.
I don't use fingertip sensor.
geronimo_2 said:
do you resolve it after restart?
I do. something is triggering it at my device but I'm unable to understand what. It's not often I get it.
I don't use fingertip sensor.
Click to expand...
Click to collapse
I switched off smart lock and fingerprint, it has been 9 hours since last restart and no problem. O do agree with you, it's still unknown CPU freeze. I'll try to switch on smart lock, lets see what happens)
I got it twice in the past 2 days. Weird. I hadn't gotten it in weeks. I did enter battery saver mode yesterday, maybe that messed things up with the cpu. And I also installed rootless launcher which is what I think triggered it the first time
Well, today I received the Pie update. after install it, the 1401 MHz bug still continues. Anyone else ith this bug and the Pie didn´t fix it? It is weird, I wait for the Pie and I was thinking that it feixed the bug, but no!
nbaptista said:
Well, today I received the Pie update. after install it, the 1401 MHz bug still continues. Anyone else ith this bug and the Pie didn´t fix it? It is weird, I wait for the Pie and I was thinking that it feixed the bug, but no!
Click to expand...
Click to collapse
I'm facing this issue too. Updated to Pie today as well.
But is this software or hardware issue?
Same on Redmi 6
I have the same problem on a Redmi 6 at around 900 MHz according to GSam. It seems to appear after I have disconnected the charger. Not everytime.
Restarting the device does not reset the frequency. Stopping it and starting again after a minute or two does. Weird and annoying !
Related
Hey guys,
I just wondered if you guys have the same problem that you lose 1% battery every 2 minutes when you´re having your display on. I know it´s quite known that big screens suck the battery like a vampire but that´s just odd, because I don´t even have to do anything with the phone just staring at the activated display.
I´ve had these troubles from the beginning with FW 10G then updatet to 10H and did factory reset- nothing changed. I tried different brightness levels without any differences in battery consumption, which is totally uncommon. And the freaky thing is there is no difference whether I have airplanemod on, wifi turned off and so on. It is always the same... Although when the display is off there is as good as no consumption but really 1% battery per 2 minutes that´s just sick. I can´t believe it.
Now i wondered if this is normal or if I should turn it to the customers service to check it.
Please tell me if you explored the same things with your LG 4X HD
Well i found it odd too but if you would root the phone and install something like setcpu you would actually see
Min CPU Freq --------------- 1.5 GHz
Max CPU Freq -------------- 1.5 Ghz
Er yeah .... after saying that i think you know why its using the battery so fast. I rooted my brothers phone and changed the clockspeeds , but no matter how low i set the min freq on "no frills cpu control" it always shows on the toast message 750 Mhz or somewhere around that.
-Grift- said:
Well i found it odd too but if you would root the phone and install something like setcpu you would actually see
Min CPU Freq --------------- 1.5 GHz
Max CPU Freq -------------- 1.5 Ghz
Er yeah .... after saying that i think you know why its using the battery so fast. I rooted my brothers phone and changed the clockspeeds , but no matter how low i set the min freq on "no frills cpu control" it always shows on the toast message 750 Mhz or somewhere around that.
Click to expand...
Click to collapse
Well thank you... I´ve rooted it and thought it had something to do with apps running in the background but it didn´t help at all so I thought this can´t be, mine must be wrong somehow.
Especially because i haven´t heard anything in reviews or forums about this rapid battery drain. This is something I´m wondering most, how can a phone taking so much battery be rated so high It sucked 3% watching a 3 minute video on youtube...
I won´t think I´m going to be happy with this phone and the best is when I contacted customers service later today they told me to send it in because its not normal, but now that you said the cpu is set this high no matter what, I can just suggest they don´t know anything about their phones...
Bet the only reward I get sending it in is "all is fine our phone likes to suck your battery, so what? Just keep the display off"
Screen off "deep sleep" battery drain is quite bad too ..
-Grift- said:
Screen off "deep sleep" battery drain is quite bad too ..
Click to expand...
Click to collapse
For me. The battery says its fully charged after 1hr. But it actually takes 3-4hrs befire it reaches the absolute full capacity.
Battery lasts twice as long then...
Sent from my LG-P880 using xda app-developers app
The last days my girlfriend is complaining about battery drain in her i8190. I installed No-Frills CPU and it seems that the min CPU frequency is stuck at 1GHZ. Applying the 200MHz setting does nothing, when i restart the app i see that the min freq is 1ghz again. The phone is with stock rooted firmware (XXAMJ3).
Any ideas about this really annoying problem?
Flash framework in odin
send for I8190N CM11 using XDA Premium 4 mobile app
pang34 said:
Flash framework in odin
send for I8190N CM11 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your answer but i am a newbie fish i didn't understand that. What am i supposed to flash?
@volanis1980
Tell your girlfriend, she should reboot her phone with Wi-FI OFF. This will solve the problem
xXPR0T0TYPEXx said:
@volanis1980
Tell your girlfriend, she should reboot her phone with Wi-FI OFF. This will solve the problem
Click to expand...
Click to collapse
Unfortunately that didn't work! Any other ideas?
volanis1980 said:
Unfortunately that didn't work! Any other ideas?
Click to expand...
Click to collapse
Did you or your girlfriend change the CPU governor to performance? No-frills CPU control can change the CPU governor. Try it out
Or
Set the phone in airplane mode and reboot the phone if it still didn't work then please attach/send some screenshots from the battery statistics in settings > battery in this thread.
P.S : Download "CPU spy" from play store and check if only 1GHz is in use.
She hasn't change the cpu governor (was with ondemand). The trick with airplane mode didn't work either!
These are two screens from no frills and cpuz where you can see the problem. I checked yesterday the real battery performance, it didn't seem that bad. Was 100% to 35% in about 9 hours with 2 hours screen on time. But isn't that strange, the min freq bug?
volanis1980 said:
She hasn't change the cpu governor (was with ondemand). The trick with airplane mode didn't work either!
These are two screens from no frills and cpuz where you can see the problem. I checked yesterday the real battery performance, it didn't seem that bad. Was 100% to 35% in about 9 hours with 2 hours screen on time. But isn't that strange, the min freq bug?
Click to expand...
Click to collapse
that is an unnormal behaviour. I think it is app-related.
try THIS to see which apk´s wake your phone up.
I installed wakelock detector but i don't see something strange.
Really frustrating, i can't find any solution!
volanis1980 said:
I installed wakelock detector but i don't see something strange.
Really frustrating, i can't find any solution!
Click to expand...
Click to collapse
noLED 107x (a playing tool in my opinion)
Handcent 104x (stoneage)
... many wakelocks
btw who uses sms in this time ?
use threema and greenify noLED
m.
if you still have problem try to change govenor and i/o schedular then switch wifi off then reboot.
Hello, I'm using Titan Stock ROM and it was working quite OK, but I noticed that with high CPU usage during longer periods of time (Like when you are calling on Skype with both webcams on) after like 5 minutes (depending on ambient temperature) the CPU throtling kicks in and you can barely end the call because the whole GUI of Android gets completely unresponsive.
Quick questions:
- What is the maximum "safe temperature" for the CPU to not break? 60ºC is way too less.. as it gets easily to that temperatures.
Now in hope of getting this a bit fixed I recently installed the "Stellar Kernel". I set the CPU settings as recomended on its kernel page (Undervolted to Min Freq. 98MHz and Max Freq. to 1190MHz). Now its just a nightmare. It overheats even quicker.. and when it throttles you can just pray to do anything.. (I changed finally to Min Freq to 385MHz but that doesn't helps much).
And on the other hand thanks to the underclocking the phone doesn't wants to wake up during minutes.. which is quite unpractical when somebody is calling you.. you can hear the phone ringing but you cannot accept the call because the phone doesn't want's to wake up. But that got somehow fixed putting it back to the Min Freq. +300Mhz.
Just want to know if somebody knows about some magic setting which allows the phone to function properly during longer time.. as far as I'm aware 1190MHz is the original maximum Freq. of this phone so no overclicking is done here. So it looks that the only way to have it working somehow decently is to underclock the maximum frequency and leave the minimum frequency high enough to work properly. I don't really care about battery anymore, as I just need the phone to be functional, and as it is now it's just not. Any advices? Thanks for any reply.
You probably have a hardware problem
rhp07 said:
Hello, I'm using Titan Stock ROM and it was working quite OK, but I noticed that with high CPU usage during longer periods of time (Like when you are calling on Skype with both webcams on) after like 5 minutes (depending on ambient temperature) the CPU throtling kicks in and you can barely end the call because the whole GUI of Android gets completely unresponsive.
Quick questions:
- What is the maximum "safe temperature" for the CPU to not break? 60ºC is way too less.. as it gets easily to that temperatures.
Now in hope of getting this a bit fixed I recently installed the "Stellar Kernel". I set the CPU settings as recomended on its kernel page (Undervolted to Min Freq. 98MHz and Max Freq. to 1190MHz). Now its just a nightmare. It overheats even quicker.. and when it throttles you can just pray to do anything.. (I changed finally to Min Freq to 385MHz but that doesn't helps much).
And on the other hand thanks to the underclocking the phone doesn't wants to wake up during minutes.. which is quite unpractical when somebody is calling you.. you can hear the phone ringing but you cannot accept the call because the phone doesn't want's to wake up. But that got somehow fixed putting it back to the Min Freq. +300Mhz.
Just want to know if somebody knows about some magic setting which allows the phone to function properly during longer time.. as far as I'm aware 1190MHz is the original maximum Freq. of this phone so no overclicking is done here. So it looks that the only way to have it working somehow decently is to underclock the maximum frequency and leave the minimum frequency high enough to work properly. I don't really care about battery anymore, as I just need the phone to be functional, and as it is now it's just not. Any advices? Thanks for any reply.
Click to expand...
Click to collapse
acquire kernels and other que rooms have different governors Study on them and the Best That was enough pro you and your needs .
I think this will help you , give will take this need to manually change the clock all, the governor will operate according to its governor preferably .
Read
http://androidforums.com/threads/android-cpu-governors-explained.513426/
:good::good::good::good::good::good:
Thanks if helped :highfive:
EDIT 2: I made a backup for my phone's data through TWRP (Recovery) and then factory reset through TWRP (as my phone's factory reset button in the settings was not functioning). All was good as soon as it booted, took awhile, but it booted. I then restored the backup and bam. The problem was solved. It may have been a problem with the system, but the Logs had shown nothing and nothing would report the mass amount of CPU usage. So a simple factory reset was all I needed.
I'm not sure what I did to make my phone mad.
I'm currently Rooted and S-ON. I'm using ElementalX as my custom kernal and the OS is stock. It started happening when I received my phone back from a repair store as my charge port was short-circuited (overloaded the port). The System would respond incredibly slowly and die quickly (100% to 85% in less then 15 minutes). I went into CPU-Z and noticed that my CPU was at a constant 100% Usage running at 384 MHz. Now, my device runs at a constant 60%-100% at 2.04 GHz (Overclocked by 200 MHz). It does throttle between 1-2 GHz but never goes below 1 GHz for more than 3 seconds.
I checked every app I could and every app reported 100% CPU usage but that NO APP was recorded using CPU above 3% AT ALL.
A thing to note is that in order to (guessing) replace the charge port, they had to remove the bottom speaker. In this case, they destroyed the bottom speaker which does not work anymore. It only makes a *CLICK* sound every half-second. What's weird is that CPU usage increases by 30-50% when the device tries playing sound through the speakers. I'm pretty sure CPU usage increases when playing music to the speakers but not by that much? Anyway, I want to keep resetting the device as a last resort since I need to backup my photos and videos but I can't since the CPU is being hogged and can not turn on MTP.
Please help me!
EDIT 1: A quick check at CatLog makes me certain that the device is unable to "read mount points" when connected to a USB port. Any ideas?
did you check your govenor setting? make sure it is "ondemand" or something else, not "performance"
kyeljnk said:
did you check your govenor setting? make sure it is "ondemand" or something else, not "performance"
Click to expand...
Click to collapse
I tried putting it on Performance thinking that the extra juice will keep up but alas it completely froze my device, in some cases crashing it and causing it to restart. It is set to OnDemand right now.
thehumanslayer12 said:
I tried putting it on Performance thinking that the extra juice will keep up but alas it completely froze my device, in some cases crashing it and causing it to restart. It is set to OnDemand right now.
Click to expand...
Click to collapse
performance is just for bench marking, not good for daily use. Ondemand will raises your clock speed in heavy task, and lower it when not needed to save battery
You're talking to a tech geek too. Anyway, any ideas on how to find out what's using all that CPU?
I've given up.. I'm going to just back up the Data through TWRP and restore it later. Please delete/lock this thread.
Hello, I have noticed that whenever I remove the charger from the phone after a full charge, the CPU stays idle at 1.04 and 1.06 for big cores instead of 576 and 710. It is fixed after a reboot.
Can anyone else confirm and report back the bug?
10.2.2.26 official global rom.
MysteriousStranger said:
Hello, I have noticed that whenever I remove the charger from the phone after a full charge, the CPU stays idle at 1.04 and 1.06 for big cores instead of 576 and 710. It is fixed after a reboot.
Can anyone else confirm and report back the bug?
10.2.2.26 official global rom.
Click to expand...
Click to collapse
I can confirm that the bug appears ONLY when I use fingerprints for unlock. When I delete all fingerprints, it is gone. (and in addition, still present in 10.2.28 EEA)
MysteriousStranger said:
I can confirm that the bug appears ONLY when I use fingerprints for unlock. When I delete all fingerprints, it is gone. (and in addition, still present in 10.2.28 EEA)
Click to expand...
Click to collapse
This explains why I got better battery hours after I deleted fingerprints! Not that it was bad before, but now it's ridiculously good!
I don’t think this a bug, it probably must be this way in order to wake up screen just by putting the finger on the scanner.
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
kingbasescu said:
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
Click to expand...
Click to collapse
This summer when I started to get the pocket photos, before the .27 was released (yes I was among the ones that got it before it was redrawn) I deleted the fingerprints to get rid of the pocket activity due to the non-existing pocket mode. As .27/.28 came with pocket mode I started to use fingerprint again but discovered that face unlock that I had been using was far more convenient and suited me better despite the somewhat lower security rating. I don’t use Gpay, and do not keep top secret stuff on my phone so I’m happy being rid of the fingerprint sensor. The sensitive economic things are protected by pin-code anyway.
So it was not battery time that drove me to ditch the fingerprint sensor, that extra battery time just came as added value for me!
kingbasescu said:
Having fingerprints registered means that the fingerprint sensor is kept active so there'll be higher cpu usage(shouldn't persist minutes after the phone has been woken) and more battery consumption. Removing all fingerprints( i.e. deactivating the sensor) should give ~10% more battery life but I think having the sensor on at all times even with all its hiccups is more than worth it.
Click to expand...
Click to collapse
If you notice, the CPU frequency increase occurs randomly after a period of time, not as soon as you turn on the phone, which seems like a bug to me. In addition, the frequency does not settle down again, leading to less standby time available. So I don't really understand how an active fingerprint sensor affects the CPU frequency after a while, and not since the boot.
gerhard_wa said:
This explains why I got better battery hours after I deleted fingerprints! Not that it was bad before, but now it's ridiculously good!
I don’t think this a bug, it probably must be this way in order to wake up screen just by putting the finger on the scanner.
Click to expand...
Click to collapse
If that was the way to be, the frequency should be that high even right after booting.
MysteriousStranger said:
If that was the way to be, the frequency should be that high even right after booting.
Click to expand...
Click to collapse
No, that does not have to be true. I can think of some reasons why CPU speed can't slowdown in order to instantly start the scanner, like for example the more services and apps are started the more CPU power is needed to make the scanner snappy enough. So that may explain why right after boot the CPU may be able to enter a lower idle state. It is in fact true that if you turn off the fingerprint reader you will not have the higher speed at idle state at all, I tested this.
Perhaps there will be a new firmware with a somewhat slower response to the fingerprint scanner that allows the CPU to enter the lower idle state to save battery power. Who knows!
I noticed this as well right from the first firmware update I used (EEA). It's been fixed after upgrading to Android Q's beta modified by Xiaomi.eu, but I don't see much, if any, improvements in battery life, while also witnessing a giant storage performance regression. Hella disappointed.
gerhard_wa said:
No, that does not have to be true. I can think of some reasons why CPU speed can't slowdown in order to instantly start the scanner, like for example the more services and apps are started the more CPU power is needed to make the scanner snappy enough. So that may explain why right after boot the CPU may be able to enter a lower idle state. It is in fact true that if you turn off the fingerprint reader you will not have the higher speed at idle state at all, I tested this.
Perhaps there will be a new firmware with a somewhat slower response to the fingerprint scanner that allows the CPU to enter the lower idle state to save battery power. Who knows!
Click to expand...
Click to collapse
I get your point but the fact is that in never goes into these lower frequencies again, even after unlocking the phone and idling with screen on, which is strange. I don't get it, really. Plus, you are not able to see in real tilme what process is hooking up CPU resources, as you could normally do in older android versions by using an app.
Ok, if the frequency never locks in the high range again and the scanner starts just as snappy I guess you are right that it must be a bug.
Skickat från min MI 9 via Tapatalk
I disabled fingerprint auth, but I don't seen any improvements in battery life.
I notice it on mine as well right now, small cores sitting at 1036 MHz and big ones+super one at 1056 MHz. Can't really put my finger on what triggered it as I've been using the FP sensor all this time and I've checked many times and the cores were at normal clocks (576, 710 and 825). I killed all running apps but it still sat like that until I restarted... at least now I can understand why sometimes my overnight consumption goes from 1% up to 5% even though I always close/kill all apps.
kingbasescu said:
I notice it on mine as well right now, small cores sitting at 1036 MHz and big ones+super one at 1056 MHz. Can't really put my finger on what triggered it as I've been using the FP sensor all this time and I've checked many times and the cores were at normal clocks (576, 710 and 825). I killed all running apps but it still sat like that until I restarted... at least now I can understand why sometimes my overnight consumption goes from 1% up to 5% even though I always close/kill all apps.
Click to expand...
Click to collapse
Try rebooting your device and you will see what the actual idle frequencies should be, then monitor it for a day or two! Can't find what triggers it but It's bugged for sure.
apoklyps3 said:
I disabled fingerprint auth, but I don't seen any improvements in battery life.
Click to expand...
Click to collapse
Reboot your phone after disabling it, otherwise the frequencies stay the same