Hi, in the screenshot you can see an app or program running called 10219.
I've googled far and wide but so far i have not found an answer. By the end of the day this is the cause of a very fast battery drainage for my S6. I'm at an end wit this issue. Anyone have any ideas?
ikbendewalrus said:
Hi, in the screenshot you can see an app or program running called 10219.
I've googled far and wide but so far i have not found an answer. By the end of the day this is the cause of a very fast battery drainage for my S6. I'm at an end wit this issue. Anyone have any ideas?
Click to expand...
Click to collapse
Ask This Issue in S6 Device Forum's Q/A Section
http://forum.xda-developers.com/galaxy-s6/help ..So That Your Device Users itself Can Help you For This Issue..
Related
I have flashed so many custom ROMs and find the dailer mostly drains much battery. the dailer includes phone and dailer storage is always top 2 battery user in the battery statistic.
in fact, I just make a little calls during the whole day, less than 10 minutes.
who can help me?
allen oddest said:
I have flashed so many custom ROMs and find the dailer mostly drains much battery. the dailer includes phone and dailer storage is always top 2 battery user in the battery statistic.
in fact, I just make a little calls during the whole day, less than 10 minutes.
who can help me?
Click to expand...
Click to collapse
You're right, this has been identified before and is mentioned in other threads within this forum, unfortunately no solution has yet been found yet as far as I'm aware.
The dialer is always kept in memory. The app doesn't get killed. Maybe this is the reason.
Sent from my HTC Desire S using XDA Premium App
ben_pyett said:
You're right, this has been identified before and is mentioned in other threads within this forum, unfortunately no solution has yet been found yet as far as I'm aware.
Click to expand...
Click to collapse
I have tried to remove the stock dailer app(htcdialer.app in system/app) and replace with third-part dailer app such as smartdailer. It works well, but the entire dailer still drains so much battery life.
I have no idea.
Didn't want to open a new thread since a found this one, wanted to reactivate it maybe someone had found a solution.
After some hours of google, xda and other forum i didn't find a solution.
Many users mentioned that this issue appeared after the 2.3 Android update.
Even after switching off all the 3 features connected to the proximity sensor the Dialer is still there.
Hopeing for a solution from a brilliant mind here.
Tryed on Runny, Virtuos, Endymion....on all the same issue.
Thanks
cpx07 said:
Didn't want to open a new thread since a found this one, wanted to reactivate it maybe someone had found a solution.
After some hours of google, xda and other forum i didn't find a solution.
Many users mentioned that this issue appeared after the 2.3 Android update.
Even after switching off all the 3 features connected to the proximity sensor the Dialer is still there.
Hopeing for a solution from a brilliant mind here.
Tryed on Runny, Virtuos, Endymion....on all the same issue.
Thanks
Click to expand...
Click to collapse
Tried cyanogenmod? I don't get problems with the dialer, but then again I don't use it very often
Sent from my Desire S using xda premium
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
koszor said:
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
Click to expand...
Click to collapse
It only happens for some people and the reason behind it is unknown. For some it is a major issue, and for others it's never existed. Only way to get it to (maybe only temporarily) go away is to reboot. Not much you can do about it, but some have said it's better if camera apps are changed to user apps rather than leaving them as system apps.
Lethargy said:
It only happens for some people and the reason behind it is unknown. For some it is a major issue, and for others it's never existed. Only way to get it to (maybe only temporarily) go away is to reboot. Not much you can do about it, but some have said it's better if camera apps are changed to user apps rather than leaving them as system apps.
Click to expand...
Click to collapse
Interesting, do you think running a custom ROM or a different kernel will help... or hope and pray Android L fixes it?
koszor said:
Interesting, do you think running a custom ROM or a different kernel will help... or hope and pray Android L fixes it?
Click to expand...
Click to collapse
I doubt it, it might be a hardware driver issue, nobody knows what the real cause is. Personally I don't have this issue, I don't think another ROM or kernel will change anything much, although it's worth a shot if the drain applies to you.
It gives me a good reason to change ROMs.. haha. Ill give it some time and see what happens thanks for the quick reply so early in the morning!
koszor said:
It gives me a good reason to change ROMs.. haha. Ill give it some time and see what happens thanks for the quick reply so early in the morning!
Click to expand...
Click to collapse
Depends where you are in the world.. 10:46pm here in Australia. :angel:
But yeah, I have no idea if another ROM would fix the issue in any way. If it helps a little it's more likely because it's a clean flash, not because of the ROM itself, but who knows. Kernel won't affect this at all.
well, the camera daemon is normal to show up, especially when you use the camera or apps that use the camera. and its normal for it to take a larger % of battery than the camera app itself. what you havent really done is actually describe your problem. as far as i know, you dont have an issue, at least until you describe it. again, its normal for the camera daemon to appeae. now please, describe your actual problem. screenies?
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
what's not normal is if it continues to drain battery, which i havent seen personally in a while, nor read any real complaints on it in a long time.
koszor said:
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
Click to expand...
Click to collapse
I've heard it only happens now when you leave the offending app that uses the camera (snapchat, skype, etc) running in the background. I can't confirm though as I've never had the issue even before the update.
simms22 said:
well, the camera daemon is normal to show up, especially when you use the camera or apps that use the camera. and its normal for it to take a larger % of battery than the camera app itself. what you havent really done is actually describe your problem. as far as i know, you dont have an issue, at least until you describe it. again, its normal for the camera daemon to appeae. now please, describe your actual problem. screenies?
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
what's not normal is if it continues to drain battery, which i havent seen personally in a while, nor read any real complaints on it in a long time.
Click to expand...
Click to collapse
I can confirm I have the continual drain, unfortunately this was the other day and since then I have rebooted and charged my phone. I'm glad its only once in a while but from what I researched it should have been fixed in 4.4.4.
More info is available in the link I posted in the 1st post including screenshots and even links to XDA. The problem I have experienced a few times so far on 4.4.4 is identical to the link in OP.
bblzd said:
I've heard it only happens now when you leave the offending app that uses the camera (snapchat, skype, etc) running in the background. I can't confirm though as I've never had the issue even before the update.
Click to expand...
Click to collapse
Its gotta be snapchat, it used to lock up and soft boot my nexus 4 from a 'bug' or something like that ><
oh well, ill just have to keep an eye out for it.. I will try CM for a month or so and post my results back tho!
koszor said:
I can confirm I have the continual drain, unfortunately this was the other day and since then I have rebooted and charged my phone. I'm glad its only once in a while but from what I researched it should have been fixed in 4.4.4.
More info is available in the link I posted in the 1st post including screenshots and even links to XDA. The problem I have experienced a few times so far on 4.4.4 is identical to the link in OP.
Click to expand...
Click to collapse
do you have any apps that use the camera? and i mean any, there are many. if you used that app, and iy continued running in the background, the the camera daemon would also run in tbe background. if it is the old camera daemon issue that youre experiencing, then it would happen every time the camera is used, not occasionally. if its only once in a while, something else is causing your issue. i had the issue before, every single time i used the camera, not occasionally.
Hi All
I know there are a lot of older threads based around the gpsd battery drain issue, and I apoligise if I'm repeating the discussion, but I could not find a solution to the issue I'm having. I am not an android developer, but I have some experience in C and Java etc. I have messed around with the android sdk but only really for interest's sake.
The last two weeks I've been having an issue with battery drain on my Galaxy S6. I know other people in my area have been having the same issue, on the same mobile network as me. My dad also has an S6, and a friend of mine has the Galaxy S4 and we are all experiencing the same issue. I'm trying to understand this problem, as the networks are not being cooperative about this.
Connecting my device to adb and looking at logcat, i see the following two lines repeated like mad (319 times in the last 10 minutes)
05-17 19:26:56.737: D/wrapperGPS(2975): SendOemGpsMeasurePosition, len(437)
05-17 19:26:56.737: D/wrapperGPS(2975): SendOemGpsMeasurePosition: loc_info
Click to expand...
Click to collapse
Please let me know what i can do to stop this, or find the app that is causing this?
If you guys need more info just ask.
FrostyWolf359 said:
Hi All
I know there are a lot of older threads based around the gpsd battery drain issue, and I apoligise if I'm repeating the discussion, but I could not find a solution to the issue I'm having. I am not an android developer, but I have some experience in C and Java etc. I have messed around with the android sdk but only really for interest's sake.
The last two weeks I've been having an issue with battery drain on my Galaxy S6. I know other people in my area have been having the same issue, on the same mobile network as me. My dad also has an S6, and a friend of mine has the Galaxy S4 and we are all experiencing the same issue. I'm trying to understand this problem, as the networks are not being cooperative about this.
Connecting my device to adb and looking at logcat, i see the following two lines repeated like mad (319 times in the last 10 minutes)
Please let me know what i can do to stop this, or find the app that is causing this?
If you guys need more info just ask.
Click to expand...
Click to collapse
I have the sameee problem, I tried with 5 different countries and the GPSD is always there
Hi, in the screenshot you can see an app or program running called 10219.
I've googled far and wide but so far i have not found an answer. By the end of the day this is the cause of a very fast battery drainage for my S6. I'm at an end wit this issue. Anyone have any ideas?
I can't directly help you, but just incase someone else can piece our two experiences together:
I've got a wakelock that held my phone for 4mins yesterday (far more than most other single wakelocks). It was called "10103", with the full name "lemon". That 'app' just reminded me of it, with a similar name format
Never heard of something like that. I suggest you backup everything you need and perform a factory reset to see if it fixes the problem.
Sent from my SM-G920F using XDA-Developers mobile app
https://www.dropbox.com/s/dxerck6wu4l475m/20161207_203959.mp4?dl=0
Hello everyone,
Just asking for some help here; I couldn't find any cases like mine online. (Although, tbh, I'm not sure how to describe it, let alone search for it)
But it is a reproducible issue that occurs. It isn't always there but for certain images/screens, it is always present. The video is one example.
I am on stock everything; I haven't really touched the phone much since I just recently acquired it.
What would be causing this issue and is there a way to fix it??
Thanks in advance for the help.
P.S. I've posted this question on the Q&A thread and I don't mean to spam or anything. Just making sure I reach out to everyone.
I have the exact same issue.. While playing games it happens a lot.
Also whenever green color is onscreen it happens.
I have searched a lot on Google and basically the query is not understandable for google and it shows me irrelevant results.
Nitish Joshi said:
I have the exact same issue.. While playing games it happens a lot.
Also whenever green color is onscreen it happens.
I have searched a lot on Google and basically the query is not understandable for google and it shows me irrelevant results.
Click to expand...
Click to collapse
tell me about it...can't even search for it properly because queries like 'horizontal lines flickering' shows me search results a totally different issue
Mine also happen the same thing. Suspected software issues because only certain picture reproduce this issue. But a friend I found in facebook said he replace the screen to fix this. Starting to happen on 6.0.1 approx. 1 month before getting nougat custom rom. Never tried to reflash stock rom yet.
goyagoyago said:
https://www.dropbox.com/s/dxerck6wu4l475m/20161207_203959.mp4?dl=0
Hello everyone,
Just asking for some help here; I couldn't find any cases like mine online. (Although, tbh, I'm not sure how to describe it, let alone search for it)
But it is a reproducible issue that occurs. It isn't always there but for certain images/screens, it is always present. The video is one example.
I am on stock everything; I haven't really touched the phone much since I just recently acquired it.
What would be causing this issue and is there a way to fix it??
Thanks in advance for the help.
P.S. I've posted this question on the Q&A thread and I don't mean to spam or anything. Just making sure I reach out to everyone.
Click to expand...
Click to collapse
Try flashing cos13.x through fastboot.
goyagoyago said:
tell me about it...can't even search for it properly because queries like 'horizontal lines flickering' shows me search results a totally different issue
Click to expand...
Click to collapse
Have you fix yours?
I Still have the issue
awandroid89 said:
Mine also happen the same thing. Suspected software issues because only certain picture reproduce this issue. But a friend I found in facebook said he replace the screen to fix this. Starting to happen on 6.0.1 approx. 1 month before getting nougat custom rom. Never tried to reflash stock rom yet.
Click to expand...
Click to collapse
Hey, finally is the problem fixed for you ? And what was the solution? I am on Android 6.0.1 & was thinking about downgrading to 5.1.1
Let me know your thoughts. Thanks!