I have a sprint LG g2.
Just recently the process Sensors.qcom started using cpu all the time and is murdering my battery life.
I am unrooted using stock everything.
What is Sensors.qcom and how can I stop it from eating my battery?
Sent from my LG-LS980 using Tapatalk
xNotta said:
I have a sprint LG g2.
Just recently the process Sensors.qcom started using cpu all the time and is murdering my battery life.
I am unrooted using stock everything.
What is Sensors.qcom and how can I stop it from eating my battery?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I'm having this problem also.
What is sensors.qcom?
same here but on the nexus 5 since the latest update
I toggled all of my sensors and rebooted a few times and the next day the process was gone.
Haven't seen it since. Doesn't even show in battery usage anymore.
I read something about apps that don't shut down the sensor after it finished using it and the still in use sensor was why that process was running.
But I'm not sure if that is even close to what is happening.
Try seeing if it's running around time of startup, if it is, find out which downloaded apps auto start and disable or uninstall them and reboot again.
Sent from my Sprint LG G2 (LS980) using Tapatalk.
just had this issue myself, anyone else had it and managed to fix it??
My phone is 3 days old and noticed my batterylife wasn't as good today, it came down to Sensors.qcom.
Can anyone else tell me there experience?
I also have a nexus 7, I was seeing the same issue with it.
So I found sensors. Qcom in system/bin, then changed its name to sensors.qcom.bak.
I lost my accelerometer, but things seem to be fine.
This is the problem with our G2s. Certain apps are keeping the accelerometer in use after the app has closed, a definite Google issue.
Sent from my Nexus 7 using XDA Premium 4 mobile app
markdexter said:
I also have a nexus 7, I was seeing the same issue with it.
So I found sensors. Qcom in system/bin, then changed its name to sensors.qcom.bak.
I lost my accelerometer, but things seem to be fine.
This is the problem with our G2s. Certain apps are keeping the accelerometer in use after the app has closed, a definite Google issue.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well need to find those bloody apps then. I have GiONEE Elife E7 with same battery drain issue with sensor.qcom
I had such a problem for a long time. But then I used the application "Ccleaner for Android 2.0" (or later) and delete this process. It was in the section "Delete at your discretion". I have LG G2 sprint unlocked by a European operator with root. All my sensors (accelerometer) work very well. sensors.qcom stay in system/bin
Related
I got pretty bad battery life today.
Usually I make it through a day with moderate use.
Today though, it was really bad thanks to "tcmd".
Thats all the info the battery usage page gives me.
55% and 2h:40m CPU time !!
What is that process? First time I see that problem.
My display time was just 55 mins today.
I am rooted on 57.
In terminal, "ps" gives me mot_tcmd /system/bin/tcmd
Anyone seen that before? What is that?
Thx
Me too! I used to use one battery charge per day and all of a sudden my battery is dead. Batter shows tcmd using 40%... I thought it may be related to the 1.8.3 update I applied over the weekend. The internet says tcmd is total commander app which I dont have unless its bunded with another app. I dont see it in the task manger either. Any info would be great. Thanks!
Mark
Sent from my MB860 using XDA App
I had this problem once also. But it was before the update that I just did. Wasn't able to pinpoint what it is though.
Sent from my MB860 using XDA App
My battery was dead in under 5 hours this morning. I restarted the phone and recharged and it seems fine now. I dont see tcmd in the battery list either. Ill see what happens in the morn.
Mark.
Sent from my MB860 using XDA App
TCMD is draining my battery fast. Running at between 34 and 40%
Would like to know what it is.
Are you all using Gingerblur 3.1? I flashed Kenn's new update and my battery life was total crap today. I dunno if it's related or not...
Sent from my MB860 using XDA Premium App
Im running stock 8.3 no root. After I simply restarted my phone I havent had the issue resurface again. Weird fluke I guess. My guess is that process must connect or do something over the wireless network and att may have been having issues with whatever that service is causing the service on our phones to use up all the battery while retrying. That theory but who knows.
Sent from my MB860 using XDA App
markh7999 said:
Im running stock 8.3 no root. After I simply restarted my phone I havent had the issue resurface again. Weird fluke I guess. My guess is that process must connect or do something over the wireless network and att may have been having issues with whatever that service is causing the service on our phones to use up all the battery while retrying. That theory but who knows.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
i used max 7h for 1 changed of battery . the baatery of atrixis very bad or processer run so fast ????
Today i want to work and put the device in a drawer. never touched it during the whole shift but one phone call. during a five hour period 30% of the battery was wasted. bbs showed audioout_2 wakelock took place for 5 hours. screen time was 30 minutes. I haven't kept any screen shots from bbs but i did capture on system battery usage.
what could have caused it?
Sent from my Nexus 4 using xda app-developers app
I'm having the same issue here
, couldn't find the sollution yet..
Sent from my Nexus 4 using xda app-developers app
weird. ain't nobody here aware of this?
Sent from my Nexus 4 using xda app-developers app
op, perhaps a little enlightenment on your setup(rom/kernel) would yield helpful information from someone running similar setup
good luck
Sent from my Nexus 4 using xda premium
QUIETLYloud said:
op, perhaps a little enlightenment on your setup(rom/kernel) would yield helpful information from someone running similar setup
good luck
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
STOCK EVERYTHING .
not even rooted or bootloader unlocked. An out of the box Nexus 4 16GB (301k),.
Perhaps there's a corrupted media file somewhere in the storage system.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Perhaps there's a corrupted media file somewhere in the storage system.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have no media files on my storage, all my music is via GOOGLE PLAY.
(the wakelock is not caused by google play because since I booted the phone I have not listened to any music)
There seems to be a fix for the problem, haven`t used it myself though. Link http://forum.xda-developers.com/showthread.php?t=2050252. Its a init.d script at boot and you need root.
I wish to avoid rooting my device. when I bought the nexus I wanted to have a vanilla Google experience.
Also I don't wanna void my warranty.
michel9501 said:
I wish to avoid rooting my device. when I bought the nexus I wanted to have a vanilla Google experience.
Also I don't wanna void my warranty.
Click to expand...
Click to collapse
Not rooting a Nexus is like forbidding the Pope to pray But to each his own.
Yeah I know, I think I'll root if i hear reports that rooted devices can receive official google updates
michel9501 said:
Yeah I know, I think I'll root if i hear reports that rooted devices can receive official google updates
Click to expand...
Click to collapse
Look here for flashing OTA`s when rooted http://forum.xda-developers.com/showthread.php?t=2145848.
and what of the audio out 2 wakelock? I'm still getting high wakelock times because of it
Sent from my Nexus 4 using xda app-developers app
I remember one time, I left a game without closing the game. 5 hours later my battery dipped and I tried to figure out why. I realized that the game was still running in the background and drained a good 30% of my battery because of the mediaserver. I know it was still actice cuz when I hit recent it picked up exactly where I left off with no lag jumping back into it.
I'm guessing the game isn't coded to freeze in the background when you leave it. I could be wrong, but this is one possibility I think.
I'm on PA, with the matrix kernel. The game is called PAD in case anyone wants more info. I say, just be sure to exit games or generally certain apps when you finish playing them.
This only happened once and since then never again since I started closing that particular app correctly. Also, I don't mess with any music volume booster mods. Just get some noise isolating earbuds/headphones. The volume booster mods definitely killed battery much quicker than it was worth with my first nexus 4
I close everything and still got 1.5h of AudioOut_2 and AudioOut_3 wakelock overnight . 20% battery drain overnight. normally my battery drains 5-6% overnight.
up
Maybe there is a corrupt file on your phone, it doesn't have to be music, could also be a ringtone or a video.
considering you don't want to root I would consider factory reset then reinstall 1 app at a time until you find the culprit. I know it's time consuming but it's either that or keep your charger handy
Sent from my Nexus 4 using xda premium
Strangely, my phone stopped responding to knock on to wake the screen. When you pressed the hardware power button to wake the screen would immediately close. It would take about 10-15 tries to unlock the screen in that split second before it closed. To troubleshoot I flashed back to factory and I still had the same issue after the phone was allowed to sleep just a few minutes. I took the OTA, same problem.
I was ready to box it up and swap out, but decided to try one other thing. I went to the screen off effect and changed it to Simple. Everything worked fine after that. I switched it back to retro tv and it would take many more tries to wake the screen. apparently its some kind of software bug. Thought I'd pass the info on to anyone else having similar issues.
Apparently root apps that play with system files trigger the bug too, like greenify. So the bug isn't tied to one screen effect, just switching to another fixes it until you play with system files via flashing or root apps. Hopefully it's something they fix in the next update.
It seems if you flash or change any system files, it reverts back to the retro tv effect and the issue repeats until change to another transition.
So the knock on feature is supposed to be more reliable if I do this?
in_dmand said:
So the knock on feature is supposed to be more reliable if I do this?
Click to expand...
Click to collapse
If you are suffering from the same software bug, it works. If you flash a mod or do anything that does a "updating android" on reboot, it reverts back to the default screen effect and the knock on becomes unreliable. After a deep sleep you can't wake it with a knock most of the time. Strange but saved me a trip verizon hell for a swap.
Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!
in_dmand said:
Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!
Click to expand...
Click to collapse
Glad it helped man. I restored my recovery,reflashed stock and took the ota before i found the bug. lol Works as advertised now.
Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app
dpaul01 said:
Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
Make sure the sensor area to the right of the FF camera is clean. If you have a screen protector over it, you might want to pull it off and clean the area really good. If that sensor is blocked or not working, it will do the same thing whether or not you change the screen off settings. Could be a bad sensor and you may need to swap it out.
Tried cleaning it, no luck. Seems like its hw related. Off to vzw I go.
Sent from my GT-N5110 using xda app-developers app
Can confirm this. Disabling retro worked originally, but after rooting and Greenify it's back.
Do I have to flash to stock to fix now? Or will Greenify uninstall do the trick?
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 08:28 AM ---------- Previous post was at 08:10 AM ----------
Well, I tested it myself. Uninstalling Greenify does indeed fix the knock-on issue.
A shame, as I really liked that app. Boo Verizon/LG. Boo.....
Damn! I was wrong.
Still having this bug, but only from deep sleep.
Incredibly annoying, but I really don't want to Re flash. Any ideas.
I'm dying here....
Sent from my VS980 4G using XDA Premium 4 mobile app
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Flashed back to stock myself and the problem continued. I returned the phone for a new one yesterday (14 days) and for the moment I'm going to keep this one stock until the issue fleshes itself out.
Sent from my GT-N5110 using xda app-developers app
timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nothing seems to fully resolve this. Super annoyed I ever installed Greenify. Ugh.
I'm within my 14 days (I got it on Monday), but I purchased from letstalk (the $26 price mistake deal that lasted a few minutes). Does anybody know if I can just walk into Verizon to switch it out, or do I have to do the mail back, wait 5 days with no phone thing?
thanks
I've only replaced the phones I directly received from Verizon in person. Call Verizon and tell them you needed to swap a phone under the 14 days. They can look at your account and tell you if you can just swap it in person or if you need to return through the reseller.
Sent from my VS980 4G using XDA Premium 4 mobile app
I've used greenify for two weeks without this issue ever happening.. maybe I'll freeze it now lol
Sent from my VS980 4G using Tapatalk 4
Maybe it was when we removed the Chinese SU. Secret payload to punish us. Lol
Sent from my VS980 4G using XDA Premium 4 mobile app
wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4
timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In theory, Greenify may break such a feature like Knock-on, but its always recoverable. Simply de-greenify the app and manually launch it to restore everything to normal.
Please avoid greenifying any app with background functionality.
PS: Greenify actually never touch any system files.
jayochs said:
wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
No, that was just humor.
Been noticing some high usage from instagram sometimes after using it. Seems Google knows about it. 4.4.3 coming? It states nexus 5 but says also on other devices.
http://www.androidauthority.com/nexus-5-camera-bug-fix-353852/
Sent from my GT-P3110 using Tapatalk
mymeatb18 said:
Been noticing some high usage from instagram sometimes after using it. Seems Google knows about it. 4.4.3 coming? It states nexus 5 but says also on other devices.
http://www.androidauthority.com/nexus-5-camera-bug-fix-353852/
Sent from my GT-P3110 using Tapatalk
Click to expand...
Click to collapse
greenify!
hey.
it's not instagram for me, but I think it's snapchat / camera (or camera permission in general)
When I look at App Ops X (an app for controlling permissions), I see that the camera app/snapchat app are running the camera always. In this app, it'll usually give a time at which a permission was accessed (e.g. 50 minutes ago) or it'll say "Running" to indicate it's using it currently.
For me, it's always been at "Running" status (the camera permission for snapchat/camera) even though I greenified snapchat.
I hope that this issue is related to the issue nexus 5 users are experiencing and that the 4.4.3 fix will apply to this as well..
Well judging by the article its the same issue. I don't use snap chat so I wouldnt know. But yeah definitely a pain.
Sent from my Nexus 4 using Tapatalk
mymeatb18 said:
Well judging by the article its the same issue. I don't use snap chat so I wouldnt know. But yeah definitely a pain.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Ever since around January, I had a battery issue where the battery capacity of my nexus 4 just dropped. I hope that this camera issue was the cause of that.
However, 4.4.2 was released on Dec 9 and I must have updated around then as well.. So there is an unexplained period gap from Dec 10 - Jan 2 of why my battery was functioning normally then..
Skyfall007 said:
greenify!
Click to expand...
Click to collapse
I have it greenified since a few days ago and although it does work to some extent it doesn't work all the time. I saw it stayed on for 1hr even with greenify
Sent from my Nexus 4 using Tapatalk
joecop said:
Ever since around January, I had a battery issue where the battery capacity of my nexus 4 just dropped. I hope that this camera issue was the cause of that.
However, 4.4.2 was released on Dec 9 and I must have updated around then as well.. So there is an unexplained period gap from Dec 10 - Jan 2 of why my battery was functioning normally then..
Click to expand...
Click to collapse
Its linked to apps that use the camera not the camera itself
Sent from my Nexus 4 using Tapatalk
Happened to me as well. Finally found the culprit (Instagram). Uninstalled. No more battery drain, camera daemon bug and can't connect to camera errors.
Sent from my Nexus 5 using Tapatalk
If you have root access, I'd suggest Dow loading Greenify from the Play Store. It hibernates the apps so that it doesn't use as much battery life.
Sent from my Nexus 4 using xda app-developers app
You should try SD Maid app from Play Store and freeze Instagram unless you use it, and don't have to uninstall it. Or just simply kill the process from SD Maid.
Hi,
A couple of days ago I updated my S5 to G900FXXU1ANE2 with Kies 3 from my PC.
I've noticed worse battery life, but I guess its too early to judge so I'll give it a week or so and a few more cycles.
However, I have noticed that during ALL games the battery gets ridiculously hot. I've never had this on any previous firmware updates. If its related to the flash/firmware then I am tempted to go back as it never used to get hot and battery life was a couple of days.
I know there will be some stock answers advising me to do a factory reset, but I'd really rather not.
Cheers,
GG
Same here..my screen gets very hot since update
Sent from my SM-G900F using XDA Premium 4 mobile app
I had strange battery life, too.
"Multimedia" drained my battery and phone became hot!
It seems that there is a scan of every media on SD after update..
Today I have another problem: http://forum.xda-developers.com/showthread.php?t=2737673
EDIT: Multimedia started again draining my battery.. I can't believe it..!!!
Noticed my battery life isn't as good after the update either. Not noticed any difference heat wise though.
Sent from my iPad using Tapatalk
Kill the bluetooth test process, it causes a damned large amount of wakelocks.... that helped a lot for me.
Also NFC despite being turned off, it was causing some wakelocks for me.
drakester09 said:
Kill the bluetooth test process, it causes a damned large amount of wakelocks.... that helped a lot for me.
Also NFC despite being turned off, it was causing some wakelocks for me.
Click to expand...
Click to collapse
Whats the bluetooth test process? I can only see 'bluetooth share' running and it only let's me stop the process not disable.
Sent from my SM-G900F using Tapatalk
simacca said:
Whats the bluetooth test process? I can only see 'bluetooth share' running and it only let's me stop the process not disable.
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Change to the All tab in the Application Manager and scroll, it should be below bluetooth share and it will have Force Stop enabled.
Got it. The only thing is that it will restart after every reboot because you can't disable it. I switch my phone off at night. Will force stop and see if it improves my battery life though.
Sent from my SM-G900F using Tapatalk
Heres to hoping that Samsung release another update to resolve this.
Its a shame coz on the previous firmware the battery life was awesome.
GG
adie1234 said:
Same here..my screen gets very hot since update
Sent from my SM-G900F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i noticed this too..