galaxy nexus crash randomly, battery remove is needed. - Samsung Galaxy Nexus

my galaxy nexus has a problem since a few months.. the phone get stuck and the screen go weird (sometimes totally black, or "noisy"), nothing works, not even the power button, i have to remove the battery to make it work again.
this has happened most of the times while downloading and installing something from goole play or while i get emails notifications and im doing something else in the phone. it does not reboot, like i said, just totally dies till i remove the battery and turn it on again.
now i updated to stock jellybean and i had the same issue. is not all the time like i said, just happens once in a while.. but i do not think is normal..
could it be a hardware issue?? i've been thinking that maybe it could be that the internal storage has some demaged sector and when android tries to write or read from that area make the phone crash.
is there any app for android to find and isolate demaged sectors??? what else could it be??

perhaps it's a hardware issue, probably with your cpu not being able to handle the load

rhed said:
perhaps it's a hardware issue, probably with your cpu not being able to handle the load
Click to expand...
Click to collapse
it seems, it is a common issue called "sleep of death", i wanna think it is a software issue, because users of the nexus 7 are experiencing this too..
but i cant find a solution for this.. everyone seems to know this issue but i have not find a solution..
it is not an app, im sure because this has happened in stock, after a factory reset without any app installed.. i've tried wipe cache also..
in other forum a guy said that could be that the device cant support low voltages and when the cpu go to its minimum frequency it shuts down.. that sounds kind of logical to me, because when the phone crash the battery usage is in its minimum (saw it in the battery statistics)..
i wanna try uncreasing the voltage a little but i cant do it in stock.. if anyone found the solution to this weird and annoying issue please help!!!

Use a uv-capable kernel, disable smartreflex, increase voltages for core, mpu and iva by 10 mV.

Related

[REQUEST] simple app: Help with overheat problem

Hello,
I need a simple app to help with an overheat problem on my EVO.
Let me recap the problem simply, when the phone gets too warm it will shut down and vibrate five times and then blink the green LED. The phone then cannot be turned back on until the battery has cooled down.
I have found a half solution, if my phone is in Airplane mode then it will not shut down even when it is warm. So, to avoid shutdown, I need a simple widget. The widget should be 2x1. On the left side, a simple battery temp monitor. On the right side, an airplane icon to let me know if the phone is in airplane mode or not.
What I need the app to do is to automatically switch the phone to airplane mode if the the phone gets above a user designated temperature. The only exception to the automatic airplane mode should be if the phone is in a current call. Seems like the phone will let me finish a call before shutting down due to heat. Hopefully the app can throw the phone into airplane mode immediately when the call ends. But if that exception is too difficult, the primary functionality would still be worth it.
This is my first app request, so I don't know if I'm being specific enough. I also know that other people can use this app. Hopefully someone out there can help us all out.
Thanks
There is an app called tasker that should be able to do that for you. At least untill someone can build an app for you.
Sent from my PC36100 using XDA App
Not sure what your doing to over heat the phone, but I would try to fix the problem instead of usong a work around. It sounds like you have an inefficient kernel or its too far ovrrclocked. I'm thinking continual use in this overheated state will cause unrepairable damage to your phone.
Just looked at Tasker, from what I can tell it does not have Temperature as an event.
And the problem cause is not my kernel, from what I can tell. I've tried a few different kernels on a couple different mods. I've tried underclocking and under volting. Nothing seems to help. From what I've read, I might have a faulty sensor.
I had a hell of a time with cm7 and the jit compiler. Poor battery life and running warm even when browsing the web. Not sure what your running but it may be as easy as tapping a checkbox.
siris420 said:
Not sure what your doing to over heat the phone, but I would try to fix the problem instead of usong a work around. It sounds like you have an inefficient kernel or its too far ovrrclocked. I'm thinking continual use in this overheated state will cause unrepairable damage to your phone.
Click to expand...
Click to collapse
It's a hardware cpu sensor calibration issue, according to Sprint tech Lokifish Mars. Search for my thread in Evo General.
I avoid shutdowns by keeping battery temp < 39°C.
mine overheated when i was charging and using hotspot/tether, somehow after i wiped my sd card and everything else and installed the rom again it never overheated again.
somehow the more apps get installed the more the chanse some of them be are gonna be running in the backgroung, who knows...
omenovi said:
mine overheated when i was charging and using hotspot/tether, somehow after i wiped my sd card and everything else and installed the rom again it never overheated again.
somehow the more apps get installed the more the chanse some of them be are gonna be running in the backgroung, who knows...
Click to expand...
Click to collapse
Some phones overheat and shutdown regardless of installed apps, rom, or kernel. My Evo consistently shutsdown at 39°C, even when running bare aosp w/zero apps installed.
It's only an issue for me when playing games, using the phone in high ambient temps, and flashing mods. Keeping the battery & cpu cool with a fan or ac vent is the only way I can flash mods or roms.
Elixir is a free app on the market, you can make customizable widgets (1x1 up to 4x1), one for temp, the other to toggle airplane mode.
I use it to monitor temp, battery, cpu freq, and cpu %, and to keep an eye on ram.
Works well.

Sleep of death

Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.
Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium
I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.
Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App
Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.
Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.
did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.
I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.
how often has the sod been happening? I think i got it yesterday, but not sure.
Do you use setcpu?
Sent from my SPH-D710 using Tapatalk
This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.

Constant reboots...

I've been having this problem for some time now and let me tell you, it is so god damn annoying.
For some reason at least once a day the phone just constantly reboots by itself in a loop until the battery is pulled out and put back in, then the next day it just does the same old thing.
I know for a fact it is not kernel related because I've tried Franco, AK, and Lean Kernel, all have the same issue.
I've also tried stock rom and Xylon rom.
I turned off SR and the problem is still there, no underclocking no undervolting, completely stock rom/kernel.
Does anyone know how I can fix this? Is this app related?
Any help would be appreciated.
Thanks
I can see how that would be very irritating. There are a lot of possibilities for the cause, but I think the first thing I would do is use Trickster app or equivalent to set my cpu frequency down to about 1000 MHz and see if that makes it stop rebooting for a few days. If so, then you might have a device that can't tolerate a normal level of heat. In that case I'd try to get it replaced, or just live with a lower maximum frequency. Or you could try turning up the voltage for 1200 MHz a little, maybe 10 mV, and see if that makes it stop.
If neither of those worked, I would start looking for a rogue app or leftover script from a previous installation. Try wiping /system as well as cache, dalvik, and factory reset next time you install a ROM.
I guess I figured out the problem.
This only happens if I restart the phone while it is connected to the charger.
Sent from my Galaxy Nexus using Tapatalk 2

Little cores running at 1440 all the time

Hey guys, need some help. I have an AT&T H810 rooted 10o. My little cores seem to be running full out at 1440mhz even though my governor is set to Interactive. This is causing it to heat up incredible, to 70c+, and is draining the battery quickly. It seems to have only started occurring in the last few days! I can run it in powersave governor which fixes it to 384mhz, and it fixes the problem, but I don't understand why it is running at full speed under interactive now. The big cores do NOT have this problem AT ALL.
I've removed any apps I installed during that time, cleared my phones cache, cleared the memory, I have tried running it in airplane mode, I've looked into what apps were running and it seems to be very few. Turned location off. I've tried freezing the play services because I have been getting a very intermittent force close. I have also tried to disable all xposed modules, and used avg to scan for any malware. Possibly init.d? Possibly the new xposed v79? I'm at a loss as to what is causing this!
Does anyone have any other ideas as to what could be happening?
There's always the good old factory reset if everything else fails.
Just asking the obvious but there is no offending wakelocks or anything that sticks out in the battery usage stats?
spartan268 said:
There's always the good old factory reset if everything else fails.
Just asking the obvious but there is no offending wakelocks or anything that sticks out in the battery usage stats?
Click to expand...
Click to collapse
Battery usage Android OS is highest at 33, followed by screen at 16%.
Wakelocks, I seem to have them under control with amplify, and I don't see any new ones.
Question about factory reset, I am not near a pc for the next few days, will it cause any problems with xposed or my rooted system image, and basically what can I expect with it? I came from a M8 where with custom recovery I was pretty fearless with being to wipe and refresh, can't do that here.
Noticed that disabling 2 of the little cores with kernel auditor really helps with the heat buildup of the phone with not much slowdown
elementalfusion said:
Noticed that disabling 2 of the little cores with kernel auditor really helps with the heat buildup of the phone with not much slowdown
Click to expand...
Click to collapse
Doesn't solve why it's running at full speed, but I'll keep that in mind.
question about factory reset, I am not near a pc for the next few days, will it cause any problems with xposed or my rooted system image, and basically what can I expect with it? I came from a M8 where with custom recovery I was pretty fearless with being to wipe and refresh, can't do that here.
Personally I never done a factory reset myself yet so i cannot comment.
For the most part it does look like you have something to work with seeing Android OS is taking up the most battery. The hard part is tracking down which process. I'm not the best at this so maybe someone else can chime in. Try taking a look at your currently running processes and see if there's anything odd
Well, after a few factory resets which did not affect xposed, I was able to resolve it to where the cores now return to 384mhz idle. It was something that was installed, and it took 3 or 4 resets after restoring my app backups, and I'm still not sure which app was the culprit. I'm possibly wondering if it was the Amplify module
Sorry for bumping this. I just suffered from this problem and it seems for me it was antutu. For some reasons it was running the background keeping the 4 small cores at 1,2-1,4 cuz constantly. I stopped it and now it's back to normal. Just wondering why it started itself in the first place.
Sent from my LG-H815 using XDA-Developers mobile app

CPU frequency sometimes lock on maximum frequency values

Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.
iFreeMan said:
Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.
Click to expand...
Click to collapse
i have samne problem on 8.8.16
Just uninstall CPU Z and accu battery problem solve
iFreeMan said:
Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.
Click to expand...
Click to collapse
I knew this problem about 2-3 weeks ago. When you charging, it go up top freqs too
That's why I want to use custom kernel. But sometimes ( much less than stock ) locked at top freqs so I think it is Miui system policy also.
You should try some kernel manager to solve temporary.
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
SunilSuni said:
Just uninstall CPU Z and accu battery problem solve
Click to expand...
Click to collapse
Problem will back soon on stock kernel
SunilSuni said:
Just uninstall CPU Z and accu battery problem solve
Click to expand...
Click to collapse
Actually bad solution, you know
Zanr Zij said:
I knew this problem about 2-3 weeks ago. When you charging, it go up top freqs too
That's why I want to use custom kernel. But sometimes ( much less than stock ) locked at top freqs so I think it is Miui system policy also.
You should try some kernel manager to solve temporary.
Click to expand...
Click to collapse
Aha, yes, you're right. Now I sorted our everything in my mind and seems it occurs after charging.
Do you think the same issue has all people with this smartphone? But just a lot of them doesn't look on that?
But I'd say it's critical bug to have locked frequencies. Why do you think it's like "miui system policy"?
I had many xiaomi devices, only here I faced with this issue. I thought may be my phone has manufacturing defects.. but seems the bug is general on our device.
What the miui version you have?
Ah, I didn't want to root my device.. I wanted to leave it as is, as stock and don't think about all this headache, but seems the time to unlock bootloader.. Because I haven't root, so, I'm not able to use any kernel managers to reset the frequencies/governors
iFreeMan said:
Actually bad solution, you know
Aha, yes, you're right. Now I sorted our everything in my mind and seems it occurs after charging.
Do you think the same issue has all people with this smartphone? But just a lot of them doesn't look on that?
But I'd say it's critical bug to have locked frequencies. Why do you think it's like "miui system policy"?
I had many xiaomi devices, only here I faced with this issue. I thought may be my phone has manufacturing defects.. but seems the bug is general on our device.
What the miui version you have?
Ah, I didn't want to root my device.. I wanted to leave it as is, as stock and don't think about all this headache, but seems the time to unlock bootloader.. Because I haven't root, so, I'm not able to use any kernel managers to reset the frequencies/governors
Click to expand...
Click to collapse
- I'm on Masik 2.5 with BlackBox kernel. If Kirks solve Dual app problem I will switch
- Miui system policy: I can not freeze/delete many system apps/modules after rooted. I also can not disable many Miui services/procsess ( by MyAndroidTools ). Miui also has performance mode for some purposes, can be auto activate in some cases
Does it drain battery faster? It can be caused by one of your user app. Try to remember when this started to happen, and traceback to the time you install/update apps during that period. Use MiXplorer and check the last installed app. There are apps that can triggered to mine cryptocurrency during charging, making your phone super hot and charge very slow. I am not saying it must be a malware, but it can be some apps that act similarly.
Try to boot to safe mode for several hours to check if it really caused by user app. Turn off your phone > Hold power to turn on > As soon as mi logo appear, quickly hold volume down until the phone finish booting (can be up to 30 seconds). You should see "safe mode" watermark at the bottom left corner, indicating all user app has been temporary disabled. Leave it for several hours to see if the battery still drain or the phone stay awake all the time (high cpu usage). To exit from safe mode, simply reboot.
I always found it is kind of a habit to blame MIUI for everything. I am not defending MIUI here, they bloat a lot. I also hate it and I am using RR now. But on several occassions when we troubleshoot, we found out it is one of the user app that cause the trouble, ads, or slow charging; not anything related to MIUI. Blaming MIUI won't solve the problem, only troubleshooting will lead us to the real culprit. In your case, it still can be caused by the MIUI itself. But until you troubleshoot it out, you won't know who is the real culprit.
For comparison, when still using MIUI 9.5.17.0 I can easily achieve 10+ hours SOT within 1,5 days (max is 14 hours). When switched to RR, affected by the wifi deep sleep drain, I rarely get 10 hours SOT anymore. Still in the process of troubleshooting the problem.
Zanr Zij said:
- I'm on Masik 2.5 with BlackBox kernel. If Kirks solve Dual app problem I will switch
- Miui system policy: I can not freeze/delete many system apps/modules after rooted. I also can not disable many Miui services/procsess ( by MyAndroidTools ). Miui also has performance mode for some purposes, can be auto activate in some cases
Click to expand...
Click to collapse
I don't mind to have additional applications.. But I don't like when my CPU works incorrect O_O
Desmanto said:
Does it drain battery faster? It can be caused by one of your user app. Try to remember when this started to happen, and traceback to the time you install/update apps during that period. Use MiXplorer and check the last installed app. There are apps that can triggered to mine cryptocurrency during charging, making your phone super hot and charge very slow. I am not saying it must be a malware, but it can be some apps that act similarly..
Click to expand...
Click to collapse
I've checked everything. It occurs after charging in most cases. I think that is the bug in governor. Yes, it drain battery a bit faster, but just a bit, I just calculated emergy consumption.
So, when my frequencies was locked, I just connected my phone via ADB to laptop and was looking at the "top" utility to see the load of CPU. And guess what? No load! Idle 796%. (all another 4% for top with refreshing each second and for CPU-Z ran on device).
Weird bug, actually...
I think I have unlock device and re-flash firmware via fastboot to over-write everything.. who knows where bug is hidden.
I've already done full reinstall system. wipe.. but it could occurs even during I read the book. Or just.. enable device, go to CPUZ, and frecuencies locked at max. Absolutely random event
iFreeMan said:
I've checked everything. It occurs after charging in most cases. I think that is the bug in governor. Yes, it drain battery a bit faster, but just a bit, I just calculated emergy consumption.
So, when my frequencies was locked, I just connected my phone via ADB to laptop and was looking at the "top" utility to see the load of CPU. And guess what? No load! Idle 796%. (all another 4% for top with refreshing each second and for CPU-Z ran on device).
Weird bug, actually...
I think I have unlock device and re-flash firmware via fastboot to over-write everything.. who knows where bug is hidden.
I've already done full reinstall system. wipe.. but it could occurs even during I read the book. Or just.. enable device, go to CPUZ, and frecuencies locked at max. Absolutely random event
Click to expand...
Click to collapse
Try not to install anything first after the wipe. Or just try the safe mode. As I said before, it might be caused by the same user app you installed after you wipe.
Desmanto said:
Try not to install anything first after the wipe. Or just try the safe mode. As I said before, it might be caused by the same user app you installed after you wipe.
Click to expand...
Click to collapse
That's could be.
I've unlocked bootloader and just flashed the last 8.8.16 with fastboot (just had thought about it could fix something, may be some thin deep bug).
But no, after I've installed the firmware with fastboot, I've started to install all my software from Google play. And guess what? I just see in cpuz and see the same - frequencies are locked on maximum values.
Strange .. I don't use something custom, or from unverified sources, just everything from google play.
Even without games (just PUBG). All another software just social. FB, messenger, Instagram, telegram, WhatsApp, Viber, and so on. And I even cannot to see what application could cause that. Don't want to root the device. After I've installed everything and rebooted device (to reset that bug with frequencies), now everything normal. Continue observation...
Just wanted to find someone who has the same issue and at least compare revisions, installed apps and so on...to try to find the trigger which causes this issue.
iFreeMan said:
That's could be.
I've unlocked bootloader and just flashed the last 8.8.16 with fastboot (just had thought about it could fix something, may be some thin deep bug).
But no, after I've installed the firmware with fastboot, I've started to install all my software from Google play. And guess what? I just see in cpuz and see the same - frequencies are locked on maximum values.
Strange .. I don't use something custom, or from unverified sources, just everything from google play.
Even without games (just PUBG). All another software just social. FB, messenger, Instagram, telegram, WhatsApp, Viber, and so on. And I even cannot to see what application could cause that. Don't want to root the device. After I've installed everything and rebooted device (to reset that bug with frequencies), now everything normal. Continue observation...
Just wanted to find someone who has the same issue and at least compare revisions, installed apps and so on...to try to find the trigger which causes this issue.
Click to expand...
Click to collapse
That's why I prefer the troubleshooting starting from small first, before going thru the whole ROM flashing. 80% of the time, it is caused by user app. A simple safe mode or factory reset will pointed out a very obvious clue immediately.
Not all playstore app are bug-free, we just don't know what happened in the next update of the app.
While you don't state it before, it can be mediaserver bug. It is caused by the mediascan which stucked at certain file/folder during the scan and keep eating CPU cycle forever. But I've never seen it goes thru almost full CPU load. The solution is to rearrange the files/folder in your internal storage or microsd (if you have it), clean up as needed. Sometimes, a simple restart resolve the issue, but not always.
I have Whatsapp. Some users in the kaskus has FB, IG, Telegram installed; I don't see much complaint from them regarding the CPU usage, except that the IG story are cropped/zoomed (16:9 to 18:9 ratio problem). You can only troubleshoot it step by step, by installing one app at a time. It is very lengthy process and tedious. But usually you can spot which app can be the potential culprit by looking at the battery usage of them. Example, you don't use viber at all, by it appears as one of the highest battery usage.
Desmanto said:
That's why I prefer the troubleshooting starting from small first, before going thru the whole ROM flashing. 80% of the time, it is caused by user app. A simple safe mode or factory reset will pointed out a very obvious clue immediately.
Not all playstore app are bug-free, we just don't know what happened in the next update of the app.
While you don't state it before, it can be mediaserver bug. It is caused by the mediascan which stucked at certain file/folder during the scan and keep eating CPU cycle forever. But I've never seen it goes thru almost full CPU load. The solution is to rearrange the files/folder in your internal storage or microsd (if you have it), clean up as needed. Sometimes, a simple restart resolve the issue, but not always.
I have Whatsapp. Some users in the kaskus has FB, IG, Telegram installed; I don't see much complaint from them regarding the CPU usage, except that the IG story are cropped/zoomed (16:9 to 18:9 ratio problem). You can only troubleshoot it step by step, by installing one app at a time. It is very lengthy process and tedious. But usually you can spot which app can be the potential culprit by looking at the battery usage of them. Example, you don't use viber at all, by it appears as one of the highest battery usage.
Click to expand...
Click to collapse
Yes, I understand that and understand why it would occurs and tried to investigate in this way, but...
I have equals application list which I had on previous device except...CPU-Z and AccuBattery (the AccuBattery for now is removed) because of I faced with this frequencies issues.
This morning it happened again. But I just.. woke up, saw on frequencies - everything OK. Then I just.. Instagram, Telegram, Facebook Messenger and Google Chrome and no more. Then I realized that the phone became a bit warm.. I saw on frequencies - it was locked again
As it happened, I've came to office, connected via ADB to laptop and made several screenshots from `top` utility and looked a bit into `adb logcat`. But nothing... IDLE ~798%. And then I've tried to go to all apps and do force stop for ALL apps. But nothing.
I just rebooted device again...
Please look on it.. https://drive.google.com/open?id=1yXjQQ4rsF3MURh1PF0DZ1Z_Gtgc4-m4_
Just concerning about.. there are a lot errors in logcat. But I understand that.. that's ok.
But 90% of logs flowing from system processes, not from apps. But there is nothing critical.. Nothing something what could flow unstoppable text and caused over-loading CPU.
I'm afraid that it could be manufacturing defects
I event tried to re-flash firmware with fastboot (I thought that byte-by-byte flasing into ROM memory could fix some random small issues). But after flashing with fastboot this CPU locking happening again.
Actually.. dunno what to do with that. The last thought to try any custom ROM (may be Lineage OS) with custom kernel and make sure that it is just bug in Xiaomi's ROM..
And I've posted about this bug on official MIUI forum and seems this bug happening with some people.
http://en.miui.com/thread-3620931-2-1.html
Talking about me. I've flashed Pixel Experience and for now everything good. Seems that's the bug in xiaomi firmware.
iFreeMan said:
And I've posted about this bug on official MIUI forum and seems this bug happening with some people.
http://en.miui.com/thread-3620931-2-1.html
Talking about me. I've flashed Pixel Experience and for now everything good. Seems that's the bug in xiaomi firmware.
Click to expand...
Click to collapse
Maybe that's the random issue with certain apps configuration with some users. Not all reporting the same. Seems to be related to thermal engine or CPU governor configuration. But I don't know where it goes wrong. At least you solved it now by flashing custom ROM.
Desmanto said:
Maybe that's the random issue with certain apps configuration with some users. Not all reporting the same. Seems to be related to thermal engine or CPU governor configuration. But I don't know where it goes wrong. At least you solved it now by flashing custom ROM.
Click to expand...
Click to collapse
I just used custom firmware just for check is that factory defect. But seems that's issue only with xiaomi's firmware.
Yes, I thought that could be governor likewise. But.. Don't think so, because this low-level things, I think, debugged and enhanced successfully by default. Seems some conflicts between system applications.
On custom ROM I haven't faced with this issue, so...
But this morning I've flashed again the global stable firmware (9.6.3.0), will see how it will going..
iFreeMan said:
But this morning I've flashed again the global stable firmware (9.6.3.0), will see how it will going..
Click to expand...
Click to collapse
Yes, I've got first lock on maximum frequencies.
So, after researches.. I could say that it's a bug in xiaomi firmware. Definitely.
I also have this problem on every MIUI rom, with stock or custom kernel. It happens randomly. I have tested in 9.6.19, 9.6.4.0, and betas 8.8.23 and 8.8.30.
If I flash any custom rom the problem desapears so it must be a problem of miui rom itself.
marc_alv said:
I also have this problem on every MIUI rom, with stock or custom kernel. It happens randomly. I have tested in 9.6.19, 9.6.4.0, and betas 8.8.23 and 8.8.30.
If I flash any custom rom the problem desapears so it must be a problem of miui rom itself.
Click to expand...
Click to collapse
I have no problem with Miui based custom Rom + custom kernel
Zanr Zij said:
I have no problem with Miui based custom Rom + custom kernel
Click to expand...
Click to collapse
Could you specify the rom and kernel, please?

Categories

Resources