According to top in terminal, pm-service is consistently using 30% CPU.
Anyone got any ideas what this service is, and if it's something I can disable or fix?
Or, any recommendations on potential fixes?
Ikbosh said:
According to top in terminal, pm-service is consistently using 30% CPU.
Anyone got any ideas what this service is, and if it's something I can disable or fix?
Or, any recommendations on potential fixes?
Click to expand...
Click to collapse
It should be a Power Management Service. Google it shows that LG phones have this program. On my phone, Smartisan M1L, there is no such process.
Hmm interesting, I'm running the experimental LineageOS version on my Xiaomi Mi Mix.
Do you think it could be dangerous to disable?
baohaojun said:
It should be a Power Management Service. Google it shows that LG phones have this program. On my phone, Smartisan M1L, there is no such process.
Click to expand...
Click to collapse
After further digging I discovered it's the "Peripheral Manager Service", I also found in Logcat that I have errors going constantly related to my fingerprint scanner.
Could these be related?
People talk in the thread for my ROM also about the NFC chip causing issues, so they disabled that completely by removing the /system/vendor/app and /system/lib files related to it.
I wonder if I can do the same for fingerprint?
Ikbosh said:
Hmm interesting, I'm running the experimental LineageOS version on my Xiaomi Mi Mix.
Do you think it could be dangerous to disable?
Click to expand...
Click to collapse
I have this same problem in the Mi Mix running RR. Did you managed to solve it?
bump! same issue, top process , battery drain
RR rom
Related
Yes, I've searched the internet and xda for an answer.
Yes, i do indeed know that xperia Z2 has an overheating problem with the camera and especially 4k recording.
But my problem is one of a kind!
It never occurs during the most heavy tasks, and yet it appears in the most simple ones.
I play asphalt 8 on high graphic while wifi is online and even when it is charging, i can feel the warmth but it NEVER shuts down.
But yet in other times i open my phone for a simple task like makimg a simple call, and it says that the device is shutting down due to high temperature.
Even though i have all apps killed, the phone temperature is cooled, it suddenly decides to shut down.
It also occurs as soon as i open the camera "normal pic, not eben 4k" and it instantly gives me that "shutting down due to high temp"
But it's not a big deal compared to my main problem that it shuts down at random low-tasks.
--------------
The solutions I've tried "please read before you suggest them again ":
- The problem first occured on LP 5.1.1
- I've downloaded and reflashed the official LP firmware. Problem still exists.
- I've downloaded and flashed the new official MM firmware, the problem still exists.
- I've had this problem before and after rooting my device, despite killing all the insignificant background processes using greenify
- I can "not" take it back to service center, because i do not have one in my country, and the local shop i bought it from would simply ignore that problem since it happens like 1-2 times per day at random occasions and i won't just keep messing with my mobile till it occurs, so he would deny the problem and blame it on "heavy usage".
Thank you in advance! :crying:
Don't have a solution but was wondering how old your device was? Have you used any temperature guage apps to see what's happening inside? Apps like https://play.google.com/store/apps/details?id=com.yanyan.cputemp - https://play.google.com/store/apps/details?id=com.cpuid.cpu_z - https://play.google.com/store/apps/details?id=info.kfsoft.android.MemoryIndicator the last one let's you have an overlay on screen to see what's happening as you use your phone. But from what you've described it sounds like a hardware fault with the sensor. There is a system app called "over heat control" maybe you could disable said app? BUT I don't know if this would stop your phone functioning all together... Maybe try recording your screen when you know this happens most to prove to shop what's happening? Best of luck!
Sent from my D6503 using XDA-Developers mobile app
Install kernel adiutor and change temp. controll to 80/85*C
EugenStanis said:
Install kernel adiutor and change temp. controll to 80/85*C
Click to expand...
Click to collapse
i have the same problem but by tablet is not rooted to do this is there a guide on how to root as the only ones i have found want to charge about £40 to do this
specs
Sony Z2 tablet
Android marshmallow 6.01
thanks in advance
EugenStanis said:
Install kernel adiutor and change temp. controll to 80/85*C
Click to expand...
Click to collapse
i have got mine routed now but cant seem to work out how to change the temp what section is it in please ?
@nickbaker66 cpu controo change default temp to 75 C
EugenStanis said:
@nickbaker66 cpu controo change default temp to 75 C
Click to expand...
Click to collapse
Thanks very much mate I'll have a tweak
---------- Post added at 07:31 PM ---------- Previous post was at 07:23 PM ----------
EugenStanis said:
@nickbaker66 cpu controo change default temp to 75 C
Click to expand...
Click to collapse
Hmm don't seem to have that on my version, it's the latest one from the play store
Cpu management ---> heat control
EugenStanis said:
Cpu management ---> heat control
Click to expand...
Click to collapse
I've had a look in kernel Adiutor and I definitely don't have that I've taken a few pics of the settings I have available or have I downloaded the wrong app ?
Thanks in advance
EugenStanis said:
@nickbaker66 cpu controo change default temp to 75 C
Click to expand...
Click to collapse
What kernel allows you to make these changes or what ROM can you make these changes
Thanks in advance
HEY FOLKS!
I'm currently running a cm13 nightly on my OPX but have been plagued with the infamous mobile radio active bug, which has crippled my battery life. After looking for fixes and talking to my developer friend, I have concluded that the only way to avoid this is to revert back to a KitKat ROM. (yes, I have tried the xposed module fix).
Does anyone know if a KitKat ROM has been made for the OPX?
Please help me out because I want good battery life back .
(I get an average of 4 hours SOT on Wi-Fi and about 2 hours SOT on LTE)
The primary culprits are google play services and fb messenger.
Thanks in advance
byrno said:
HEY FOLKS!
I'm currently running a cm13 nightly on my OPX but have been plagued with the infamous mobile radio active bug, which has crippled my battery life. After looking for fixes and talking to my developer friend, I have concluded that the only way to avoid this is to revert back to a KitKat ROM. (yes, I have tried the xposed module fix).
Does anyone know if a KitKat ROM has been made for the OPX?
Please help me out because I want good battery life back .
(I get an average of 4 hours SOT on Wi-Fi and about 2 hours SOT on LTE)
The primary culprits are google play services and fb messenger.
Thanks in advance
Click to expand...
Click to collapse
First of all it is highly difficult and probably impossible. Second, there is no point of it. It leaves device prone to various security vulnerabilities, leave on some optimization and doze. Some apps might not work in future because of end of support.
Google is not admitting google play service and mobile radio active bug, it continues from lollipop to marshmallow and most likely in nougat. It almost kills battery life in mobile data. Even if someone starts development, it would be huge pain with very little to gain.
saurabh40629 said:
First of all it is highly difficult and probably impossible. Second, there is no point of it. It leaves device prone to various security vulnerabilities, leave on some optimization and doze. Some apps might not work in future because of end of support.
Google is not admitting google play service and mobile radio active bug, it continues from lollipop to marshmallow and most likely in nougat. It almost kills battery life in mobile data. Even if someone starts development, it would be huge pain with very little to gain.
Click to expand...
Click to collapse
Bummer. Any advice about how to cope? Or should I sell up and get a phone that supports KitKat?
byrno said:
Bummer. Any advice about how to cope? Or should I sell up and get a phone that supports KitKat?
Click to expand...
Click to collapse
No kitkat for opx, since no sources were released. If you want a good phone that supports kitkat, buy a refurbished nexus 5, or lg g2.
As long as you turn mobile data off you wont be affected by the bug. Why not use something like leandroid to turn off mobile data after "x" time of the screen being off? It also has the ability to turn it on and off every x time if im not mistaken (so you get notifications). It is not ideal, but it is a good workaround probably (i dont use it because i only use mobile data ocasionally and turn it off after using it so im not affected)
byrno said:
Bummer. Any advice about how to cope? Or should I sell up and get a phone that supports KitKat?
Click to expand...
Click to collapse
In settings-security-apps with usage turn both off. Turn off all Google sync (except mail.) And I go a far as turning automatic update and such in play store settings. Haven't had an issues since. With messenger skip adding phone number and contacts.
migueldbr said:
As long as you turn mobile data off you wont be affected by the bug. Why not use something like leandroid to turn off mobile data after "x" time of the screen being off? It also has the ability to turn it on and off every x time if im not mistaken (so you get notifications). It is not ideal, but it is a good workaround probably (i dont use it because i only use mobile data ocasionally and turn it off after using it so im not affected)
Click to expand...
Click to collapse
That sounds like a good solution. Also found an app named "force doze" which disregards some of the senses and will allow you to doze straight away.
Thanks guys.
byrno said:
That sounds like a good solution. Also found an app named "force doze" which disregards some of the senses and will allow you to doze straight away.
Thanks guys.
Click to expand...
Click to collapse
force doze probably does not fix that bug. It also may introduce new bugs, i wouldnt advise to use that app yet. Use doze editor instead
Hello,
Does anybody recognize a wakelock called LocationManagerServiceEx ? It appeared in bbs but could not be detected by amplify (see pictures). How come? It kept my LG G5 awake all night long.
Thanks.
Edit: I found the following thread and will try the solution it offers:
http://forum.xda-developers.com/tmobile-lg-g5/help/battery-drain-t3427578
It didn't fix the problem.
I tried with both adb commands.
Any solution for it?
leranp said:
It didn't fix the problem.
I tried with both adb commands.
Any solution for it?
Click to expand...
Click to collapse
Yes, it didn't fix it. It still shows up. Did you find any other solution?
bonotheedge said:
Yes, it didn't fix it. It still shows up. Did you find any other solution?
Click to expand...
Click to collapse
No ?
same problem here on LS992 (Sprint variant for months) I have tried using the battery historian tool, but it isn't able to tell me what app is causing this wakelock.
:/
riggsandroid said:
same problem here on LS992 (Sprint variant for months) I have tried using the battery historian tool, but it isn't able to tell me what app is causing this wakelock.
:/
Click to expand...
Click to collapse
I am using Amplify to stop two services which you can see at the attached photos. As of few days, I do not see the mentioned above wakelock any longer.
bonotheedge said:
I am using Amplify to stop two services which you can see at the attached photos. As of few days, I do not see the mentioned above wakelock any longer.
Click to expand...
Click to collapse
And now with the photos...
bonotheedge said:
And now with the photos...
Click to expand...
Click to collapse
if i just run the pm hide com.qualcomm.location command isn't that equal to what you're doing? just with a lot more brute force.
I don't have root on LS992. Amplify isn't an option.
riggsandroid said:
if i just run the pm hide com.qualcomm.location command isn't that equal to what you're doing? just with a lot more brute force.
I don't have root on LS992. Amplify isn't an option.
Click to expand...
Click to collapse
I am not sure about it.
Turn it off in location settings. Izat. Better Iocation service with less power consumption.
Isnt that it?
sierrawhiskey said:
Turn it off in location settings. Izat. Better Iocation service with less power consumption.
Isnt that it?
Click to expand...
Click to collapse
It's off with the wakelock showing up. Even if I try turning it on and back off, wakelock persists. I'm letting battery die today and will run another historian thing on a bug report to see. It's been better today but no where near where it should be.
I have this same wakelock irritatingly preventing any deep sleep on the phone. It's not there all the time, but reliably, if I find my phone is burning through battery faster than my norm, betterbatterystats shows this wakelock is the culprit.
Another thread recommended blocking the com.qualcomm.location app, but this results in poor GPS reliability, cutting in and out, very similar to the 10A Tmobile GPS bug, which was fixed in 10D.
It's hard to tell which app is polling this service and not gracefully killing it when it is no longer needed.
riggsandroid said:
if i just run the pm hide com.qualcomm.location command isn't that equal to what you're doing? just with a lot more brute force.
I don't have root on LS992. Amplify isn't an option.
Click to expand...
Click to collapse
I have an unlocked RS988 G5 running Marshmallow 6.0.1 and it is not rooted (I don't really want to root). Kind of a noob question, but if the G5 RS988 can't be rooted, how can I even run BetterBatteryStats?
The phone has thermal issue and heats up even during normal tasks, I don't even game on the phone. Heating is more noticeable while using camera. Is there any fix for thermals(non-root method)?
No issues such that.
Could You provide us your device variant and miui version, please ?
Clear system cache.
Try disabling ARcore.
Abdullah.Csit said:
No issues such that.
Could You provide us your device variant and miui version, please ?
Click to expand...
Click to collapse
Rn note 10 12.0.1 IN
blackhawk said:
Clear system cache.
Try disabling ARcore.
Click to expand...
Click to collapse
How to disable ARcore?
suku.incognito said:
How to disable ARcore?
Click to expand...
Click to collapse
I use Package Disabler. Not sure if you can disable that one in apps. Going back to the factory load if it has been updated by Playstore though might be enough to get it to behave.
Otherwise use an ADB edit.
That is far from the only one that could be causing trouble but the camera issue is why I mentioned it. The cam draws a lot of current normally so there may be others that are the prime offenders; using the cam just tips it over the edge so to speak.
Google Play Services is one I keep disabled except when needed. Playstore too.
I have about 90 packages blocked. All power management is disabled.
Took a lot of trial and error to optimize my stock AT&T N10+. It was a hot running bandwidth hog, now it's a cool, fast running, very stable platform.
One of the big reasons I refuse to upgrade from Pie.
This is not the common problem of this phone.
We don't meet him with him.
First try factory reset.
If it doesn't help, do nothing more with your phone.
You would violate the quality guarantee.
Claim the phone.
Hello everybody!
Ever since I bought this phone (Pixel 6) the assistant has never worked. Considering this is a Google phone, one would assume it would work no issue but joke is firmly on me!
I have been researching and have seen mixed messages from many websites where some users have the issue, others no issue! I have seen some people say to reinstall the Google App (tried this, didn't work) and other people said to completely restore to factory which I don't want to considering the hassle of getting everything back in order.
Does anybody have anything else I might be able to try?
Thanks in advance
Jamesr1292 said:
Hello everybody!
Ever since I bought this phone (Pixel 6) the assistant has never worked. Considering this is a Google phone, one would assume it would work no issue but joke is firmly on me!
I have been researching and have seen mixed messages from many websites where some users have the issue, others no issue! I have seen some people say to reinstall the Google App (tried this, didn't work) and other people said to completely restore to factory which I don't want to considering the hassle of getting everything back in order.
Does anybody have anything else I might be able to try?
Thanks in advance
Click to expand...
Click to collapse
I have seen this happen with a different launcher installed. It happen with me using Nova launcher back in the beginning of using the P6. Nova fixed the issue a week after people complained.
vandyman said:
I have seen this happen with a different launcher installed. It happen with me using Nova launcher back in the beginning of using the P6. Nova fixed the issue a week after people complained.
Click to expand...
Click to collapse
I still use the Pixel launcher. It literally happens every time, it just shows "Cannot Reach Google" :/
Jamesr1292 said:
I still use the Pixel launcher. It literally happens every time, it just shows "Cannot Reach Google" :/
Click to expand...
Click to collapse
The only other thing that comes to mind.
Are you using an ad blocker?
vandyman said:
The only other thing that comes to mind.
Are you using an ad blocker?
Click to expand...
Click to collapse
Nope. If it counts, I am using the Brave Browser?
Jamesr1292 said:
Nope. If it counts, I am using the Brave Browser?
Click to expand...
Click to collapse
No the Browser should not block it.
But since you brought up the Brave Brower.
Did you disable Chrome?
I think the assist only works with Chrome. I am not a100% sure.
I am going to step aside and let someone else help. I really am just guessing at this topic.
vandyman said:
No the Browser should not block it.
But since you brought up the Brave Brower.
Did you disable Chrome?
I think the assist only works with Chrome. I am not a100% sure.
I am going to step aside and let someone else help. I really am just guessing at this topic.
Click to expand...
Click to collapse
I didn't disable it, I just never used it.
I did open it just now and tried to use the assistant with it and it didn't crash immediately. You might be on to something.
Maybe I am missing something though, if it was a browser based issue, why would that impact my ability to open say Spotify or "check the weather".
Maybe it's some other Google system/service I am after breaking?
Jamesr1292 said:
I didn't disable it, I just never used it.
I did open it just now and tried to use the assistant with it and it didn't crash immediately. You might be on to something.
Maybe I am missing something though, if it was a browser based issue, why would that impact my ability to open say Spotify or "check the weather".
Maybe it's some other Google system/service I am after breaking?
Click to expand...
Click to collapse
I use Duck Duck Go browser.
I have tried the Brave browser a few months back for a short time.
Side note; I use Brave browser on my pc, because edge gives me trouble with networking for my smarthome devices and nas.
I am also having this issue after rooting and modding a few things. Reverted the changes but I am still having the issue. Updating Google App and downloading Google Assistant doesn't seem to do the trick either. Anyone with some insight into the issue know what's going on?
quick update - I installed Alexa to see if that would work, and it too doesn't appear to like me
Starting to think its a service based issue instead of a particular app.
Anybody who has guidance please chime in
Are you completely stock, no custom rom, kernel, Magisk mods?
Alexa will increase your four letter vocabulary to a new level.
Do you have the assistant set to more than 1 language? For me having the assistant set to English and dutch causes it to constantly.
I figured out for me it was dozing google play services
so, update on this. Firstly, I only have it using the one language.
Secondly, I got an update yesterday for the google app from the playstore and it appears to have fixed whatever the problem was!