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.
Hi everyone,
I just flashed ARHD 7.0.2 on my Desire HD last night and I'm experiencing the following problem:
The CPU remains at 99-100% all the time, the battery drains excessively fast and the phone gets really hot.
Using "Watchdog Lite", I detected that when the CPU does not stay at 100% (after a battery-pull), the "Phone" process uses 0,0% of CPU.
However, for some reason, after a while it will jump up to 80-90% and stay there, causing the CPU to go berserk.
I suppose the heat-issue comes from the fact that the cpu works all the time at 100%.
The battery drain issue comes also from the CPU.
However, I do not know why the Phone process would suddenly go crazy and use that much cpu - and keeps doing it until the battery is dead.
I'm thinking it is because the ARHD 7.0.2 ROM is actually a stock Sensation XL base and thusly requires another RIL than the one that was on it before that.
Before flashing another RIL or radio I would like it very much if somebody could confirm that the fact that the Phone process goes crazy like that could very well be linked to the fact that the RIL and Radio don't match.
It seems obvious, but I don't know enough of the inner workings to verify this, so therefor: this thread
Thanks in advance to all!
sstm
The RIL should be pretty standard between HTC devices so that shouldn't cause any issues. Did you do a full wipe before the install?
Hello TransientMotion,
Yes I did a full wipe, I even cleared the battery stats for good measure.
I even formatted my SD-card to make sure nothing remained from some app somewhere.
The phone is as if I'd have bought it fresh out of the store with ARHD 7.0.2 on it (and rooted of course)
It's just weird to see that the "Phone" process is using this much cpu, even when on Airplane mode.
Thanks for you reply,
sstm
It may be worth trying out an earlier version of the rom just to see what happens. I used 6..3.1 before I switched over to ICS and never had any major problems with it. If that works fine then try newer versions until you get glitches again or it works without the drain
Hey,
I just found out that it is Llama (kebabApp 'location aware' application) who is causing the problem.
Whenever I leave an area and then re-enter it, the CPU goes berserk and stays that way as if some loop can never be interrupted.
I didn't have this problem on ARHD 6.3.1, but I didn't have the same Llama configuration on it either so I tried the Llama config on ARHD 6.3.1 and it did the exact same thing: cpu 100% and slowness all over.
So conclusion: Llama config is the culprit.
Anyways, thanks for you help TransientMotion.
sstm
I even broke my phone with App Ops trying to figure it out, disabling wake permissions for most apps which caused FC's and even reboots. I have since restored all permissions but I still get FC's whenever I leave an app or switch out of it. Not sure if it's really crashing, but I get a FC message every time. So much so that Substratum turned off its theming for Files because it "crashed" after every screenshot was successfully uploaded to this post. Btw I just removed CrossBreed Lite and it seems to have helped. So far no reboots doing the same stuff that caused reboots! Not sure why it caused problems though. I used it for a few days with no issues.
Anyway, back to my battery woes. 30-40% kernel system usage. Why is this happening? Even Snapchat which is abusing wake locks is nothing compared to kernel system.
I'm running the latest build of AIM 8.1 with EX Kernel. I have just visited the other thread about tweaking governer values to optimize battery life so I'll report back with results although I doubt that's relevant to my battery drain.
I've Googled quite a bit on the subject and it seems that each case is different. Usually caused by a certain bug, although a lot of people say it's "normal" which I strongly disagree with.
Update: optimizing the CPU has definitely made an improvement, but the kernel battery drain still exists.
Could it really be pick up to wake and wifi search behind the drain? Isn't this phone supposed to have a sensor hub that allegedly allows for all sensors to constantly be on while using minimal power? I never noticed this drain on any other phone with both of these features on.
Anyway, I disabled pick up to wake and I'll start trying to remember to turn off wifi when not in use.
I think you're trying too hard and running a bunch of stuff. The kernal usage looks about right. I wouldn't run Gsam and BBS at the same time. They can fight each other. What makes you think there's a problem? Nothing jumps out at me.
Sent from my [device_name] using XDA-Developers Legacy app
I also can't see anything out of the ordinary, except this one picture where it shows the phone being active while dozing. I don't know how to understand that because I don't use that app, maybe I'm reading it wrong. What does Android's built-in battery monitor show? Is it dozing properly while screen is off? What is your average SOT? Is your mobile signal strong? I'm also using AIM 8.1+EX combination with satisfying results. Is your radio up to date?
maybe Wakelock Detektor or Greenify can help you.
And if you currently have things crashing all the time, start with a factory reset. Much easier to diagnose the cause when the apps aren't doing random stuff.
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?