Related
I had this on 4.4.2 but 4.4.3 fixed it. I'm on 4.4.4 now and have been since it came out, but all of a sudden last week, mm-qcamera-daemon came back and I'm not alone.
With L just around the corner, I doubt there will be any fix for this from Google, so what's the best way of finding out which app is keeping this service alive?
P.S. I have neither Skype, Instagram, nor Snapchat installed - and never have done - so it's not them.
Did you have a camera app running in the background? ie. minimized it without swiping it away.
Nah, nothing like that. I'll even get it when I boot my phone, open no apps at all, and charge to 100% before unplugging from the charger - this action seems to be the cause of the daemon, like some of the other users on that issue report are saying. Never mind, I guess I'll just wait it out until L.
I have never had this problem on my nexus 5 until today (I bought the Nexus 5 on day one)!
This process is draining all my battery!!
The only app I installed in the past week is "Google Opinion Rewards" which was installed 6 hours ago.
Please help if you find a solution
UPDATE 1: I just noticed, via CPU-Z, that all 4 cores are continuously active at high frequency and the phone is overheating
UPDATE 2: Problem is still there even after removing "Google Opinion Rewards"
Just reflash the stock firmware and see if it continues.
Best thing to do with any issue that a solution can't be found for easily. ?
skttrbrain said:
Nah, nothing like that. I'll even get it when I boot my phone, open no apps at all, and charge to 100% before unplugging from the charger - this action seems to be the cause of the daemon, like some of the other users on that issue report are saying. Never mind, I guess I'll just wait it out until L.
Click to expand...
Click to collapse
the camera daemon is supposed to appear. its not supposed to stay around, draining battery. especially at 100%, you will see it, as the phone uses it a little bit, and you havent used the phone at all. it will show up. the question is, if you dont use the camera at all, and it appears in your battery stats, after a full cycle of use, how much battery does it take? chances are that by the end of your battery cycle, it wont even be in your battery stats.
simms22 said:
the camera daemon is supposed to appear. its not supposed to stay around, draining battery. especially at 100%, you will see it, as the phone uses it a little bit, and you havent used the phone at all. it will show up. the question is, if you dont use the camera at all, and it appears in your battery stats, after a full cycle of use, how much battery does it take? chances are that by the end of your battery cycle, it wont even be in your battery stats.
Click to expand...
Click to collapse
I actually fixed it now by flashing the system image and restoring all my apps via Titanium Backup, but I swear I'd never even open Camera for it to occur, and I don't have any third party camera apps. It would constantly be active without opening any camera apps at all.
edit- also Google have restated that they're looking into this bug and have marked it urgent, so anyone else getting it - don't panic too much, it's most likely not a problem you've caused.
I suspect the Hangouts/Hangouts dialer. I updated the app few days ago (no other installs), today was the first time that I got this issue (got my Nexus in February). Also first time since updating I used the camera, followed by battery drain/ daemon/ "failed to connect camera" etc.
I think its because of android wear
With android wear u can access the camera, hence u will be seeing the camera drain for sure. i unpaired my watch for few days and i didnt have this problem till now
I had this problema today morning, my android version is 4.4.4, In my case I used yesterday the camera to attach a photo inside the facebook messenger, maybe this buggy app make this mess in my case.
I reboot and waiting for the results
Same here
Everything was ok from 4.4.2 till 4.4.4. But suddenly week ago discovered mm-qcamera-daemon issue, tried many things without success. I am using phone in safe mode (facepalm).
Waiting official Android L or fix from google.
I got the same issue now!
Started today, what the hell?
Some apps will keep the camera wakelocks going. Freeze anything that can possibly use the camera and see what happens.
Or just clean flash stock, and see if its OK. If so... Install a handful of apps per day.... Then if it goes nuts you know it's an app you've just installed.
https://code.google.com/p/android/issues/detail?id=70755#c171
I think i had this fixed. Ihave a rooted nexus 5 stock rom. Installed greenify, pirchased the donate version and had the camera app greenified. No more mm-qcamera-daemon showing up on my battery stats. No more "cannot connect to camera" issues. (So far it's been 2days without it.
camera block app
i see this issue occurs when i use skype or any camera related app in my grand 2 4.4.2 / only way i keep the issue at bay is use camera block app.. which i keep it turned on when i am not really using the camera.
this seem to keep this daemon under control and not drain my battery .
Since I read about a lot of problems with the Lollipop-Update on the Edge I - for the time being - do not want to update. My Problem:
I forgot to switch off the automatic update function on my Edge and now it downloaded the Lollipop-update. I marked the "install later" - option but now it constantly reminds me when I switch it on after some time at idle and the Update-notification cannot be cleared in the status-bar.
Question: does anybody know how to get rid of this ? My Edge is NOT rooted (nor will I), I just wish to have it like it is with KitKat since it is my main work-tool and I have NO SECOND to spend to fiddle around with problems after an update. It works perfect for me as it is ..........................
This worked for me. Still running kit Kat without prompting to update.
http://forum.xda-developers.com/note-4-att/general/guide-disable-knox-ota-updates-apps-root-t2976315
troed said:
Since I read about a lot of problems with the Lollipop-Update on the Edge I - for the time being - do not want to update. My Problem:
I forgot to switch off the automatic update function on my Edge and now it downloaded the Lollipop-update. I marked the "install later" - option but now it constantly reminds me when I switch it on after some time at idle and the Update-notification cannot be cleared in the status-bar.
Question: does anybody know how to get rid of this ? My Edge is NOT rooted (nor will I), I just wish to have it like it is with KitKat since it is my main work-tool and I have NO SECOND to spend to fiddle around with problems after an update. It works perfect for me as it is ..........................
Click to expand...
Click to collapse
Take these people's "issues " with a grain of salt. 99.9% of people's issues are users error. Period. Update is running absolutely awesome. Battery is the same as it was on kk, it's smoother, looks better, and just overall improved. End of story.
Can second that. Most issues like overheating, battery drain turned out to be due to the system indexing the files, and running all sorts of stuff in the background. All got sorted out by itself in a day or so.
Anyway, you might try clearing the cache from recovery.
Else, only option I know of is what has been posted above already.
- I prefer the 'recent apps' layout of EMUI 4.1 over 5.0. Just my personal preference. Wish there was a way to choose the style like BlackBerry does for their Android phones.
- Ever since I upgraded, I noticed the phone hasn't been running as smooth as before. Experience odd lag here and there.
- When I receive a message such as a text message, it doesn't scroll the message in the status bar anymore. I use to like reading my messages scroll in the status bar. Is this an option I'm just not seeing?
- I receive two persistent notifications on my lock screen that no matter how many times I clear, they keep coming back: BBM (Connected) and Cisco Jabber (Available.) Any suggestions on how I can remove these?
- Can I revert back to 4.1?
- Why still no double tap to wake?
- I like the pull down notification panel better now. Never really liked the split pull down.
Did you upgrade officially through the settings app/Hicare? Or was it another method?
I ask because I've yet to see anyone who's upgraded officially say they're experiencing lag, all I'm seeing is that EMUI 5 is actually smoother.
vyper4 said:
Did you upgrade officially through the settings app/Hicare? Or was it another method?
I ask because I've yet to see anyone who's upgraded officially say they're experiencing lag, all I'm seeing is that EMUI 5 is actually smoother.
Click to expand...
Click to collapse
I have seen no lag at all. 5.0 seems snappier.
peneoark said:
I have seen no lag at all. 5.0 seems snappier.
Click to expand...
Click to collapse
That's why I'm wondering why OP says he's experiencing lag.
Well, for the BBM connected icon, you can go into BBM settings and turn it off.
It's used to keep the app "alive" and keep receiving notifications, since BBM doesn't use standard google play services for push.
Also, if your phone runs out of ram, it will shut off apps like BBM to use that ram, but I've found with 3+ gbs of ram, it's never shut down on me.
Not sure if jabber will have the same setting, but it should. Presumably for the same reasons.
I upgraded thru settings. Well maybe i have too much going on. Going to clean up a few things and do a restart.
vyper4 said:
Did you upgrade officially through the settings app/Hicare? Or was it another method?
I ask because I've yet to see anyone who's upgraded officially say they're experiencing lag, all I'm seeing is that EMUI 5 is actually smoother.
Click to expand...
Click to collapse
The lag maybe because of the remnant left behind from EMUI 4 or marshmallow. That is why I advocate factory reset after major update. We moved from MM to Nougat, it might seem much from the changes but it is significant enough to warrant change from 6 to 7.
Thanks! I'll try that
SolarisSixth said:
Well, for the BBM connected icon, you can go into BBM settings and turn it off.
It's used to keep the app "alive" and keep receiving notifications, since BBM doesn't use standard google play services for push.
Also, if your phone runs out of ram, it will shut off apps like BBM to use that ram, but I've found with 3+ gbs of ram, it's never shut down on me.
Not sure if jabber will have the same setting, but it should. Presumably for the same reasons.
Click to expand...
Click to collapse
Since we've been talking about Pie in at least four different threads, I thought I'd create a single one to address, list and possibly fix all the issues that are being experienced with the gradual release of Android 9 on Nokia 7 Plus. Mods: I'm assuming this is helpful, but if you think this thread is redundant feel free to delete it.
IMPORTANT: Before you do anything or think something is broken, make sure you restart the phone twice once you've installed the update. If issues are still there, you might go for a hard reset which is always helpful for creating a clean system environment.
In any case, you're welcome to add to this list and help others find solutions. This is what I found so far:
Battery draining
Most users noticed a decrease in SOT, for some this is even 2-3 hours less than on Oreo. While it might be peculiar to Pie itself, it is worth noticing that the new Adaptive Battery feature takes some time to adjust according to how you use your phone and learn what apps to handle and how. You should also check that no app permissions have changed since the update, or that no unwanted processes are misbehaving because of it (see below).
@trveller72 points out a neat trick: deactivating the automatic Battery Saver (Settings > Battery > Battery Saver > UNCHECK "Turn on automatically") seems to extend battery life a lot.
Heating issues
Regardless of the SOT, these should not be there. I experienced the thing myself and in deep October no phone should burn into one's pocket, whether idle or when doing some light browsing. If you're having heating issues, this is most likely related to processes misbehaving and abusing your CPU when they shouldn't (either because of an application bug, or because of something gone wrong after the update). In this case you should launch the ADB command
Code:
adb shell top
which returns the CPU usage of your phone (make sure, of course, the phone is connected to your computer and has USB debugging enabled). This might give you an idea of anything strange going on and allow you to act accordingly. Or you could go for a hard reset like I did, which is a nice overkill solution and grants that you carry over no unwanted issues from Oreo - and it also recovered some SOT for me.
No adaptive brightness fade effect
I experienced this myself: the screen goes from 0 to 100 brightness in a millisecond and you're blinded forever, never to see your loved ones' faces again. This might possibly be an issue with the personal settings brought over from Oreo. In my case, I solved it to a degree by playing with the bar a bit, and it was solved completely with a hard reset. I think the fade effect is a bit faster in Pie anyway, so there is a degree of difference you should not worry about.
App notifications not disappearing
Notifications for some apps tend not to disappear when you swipe over them. For instance, this is true with the "HDR processing" progress bar of the PixelCamera mod (or better yet, in some versions of it). No fix for now, you just have to force quit the app and hope it is made compatible soon.
UI and Animation glitches
As with all first releases, this one is not perfect yet. I've personally encountered some animation glitches with the reception of nested notifications (especially in the lock screen), non-standard DPI settings, app-switch animations, volume control when writing on your keyboard, and minor stuff of the sort. While most of these are system-related and will have to be fixed in next releases, for in-app glitches make sure they are correctly updated and compatible with Pie; you could also try deleting cache/data, uninstalling and reinstalling them.
In particular, some report an issue where the bottom part of the touchscreen stops working after prolonged inactivity, regardless of the navbar settings. @k3dar7 suggests using XDA Navigation Gestures (no root).
Digital Wellbeing
Yes, this is not compatible with Nokia 7 Plus yet, despite it being in DP4 (iirc), the feature is still unavailable although installed on the phone and already collecting data, and can be enabled by subscribing to the beta program (thank you @divvykev). Downloading it as an app from Play Store won't be possible, but @Redcap56 kindly points out that a working version is available for download at APKMirror.
"Non-issues"
(i.e. things you're probably complaining about but are actually feature-dependant)
- The new gesture-based navigation is not available. It's there, but you have to turn it on under Settings > System > Gestures > Swipe up on Home button
- Mobile data is always active even when on a Wi-Fi. Yes, unlike before it is, but you can turn this feature off in Developer Settings.
- There is a maximum number of possible notification icons before the dreaded "etc. dot" appears. Nothing that can be done, unfortunately. This was decided by Google regardless of not all phones having a notch.
- File Manager is gone. And FilesGo is now there, like the child you never wanted. And most likely you never wanted it because it doesn't allow you to browse folders. The old file manager can still be accessed through the Download app or in System > Storage > Files. If you can't see the internal memory, make sure the option is ticked in the three-dot dropdown menu.
Digital Wellbeing does work!
Installing from apkmirror worked for me: apk/google-inc/digital-wellbeing (I am still not allowed to post url)
Redcap56 said:
Installing from apkmirror worked for me: apk/google-inc/digital-wellbeing (I am still not allowed to post url)
Click to expand...
Click to collapse
Thanks for the heads-up, it works indeed.
By the way, before getting the APKMirror version I had just found out that Digital Wellbeing is actually installed on the phone, just inactive.
https://drive.google.com/file/d/1vYzZE5zB3LNLAckAUlRMkWoXPMjkD42M/view?usp=sharing
When I updated it with the APKMirror one it could show me statistics from all the past day, which means two things: one, it's already collecting data and it's creepy. Two, it's in a working state as it was in DP, so shall we expect that it becomes activated with the next OTA? (or when marketing-wise it's no longer important to make it Pixel-exclusive?)
If I search on internet, Digital Wellbeing is only available on beta version for Pixel phones on Android Pie only.
I think, when the beta is finished, we have all access to this functionality
Wellbeing is available. I found it be looking for the app in the store but found that it was installed. Signed up for the beta and hey presto....there it is. Can't see it being of any use to man or beast but hey ho.
Am on Pie stable btw.
divvykev said:
Wellbeing is available. I found it be looking for the app in the store but found that it was installed. Signed up for the beta and hey presto....there it is. Can't see it being of any use to man or beast but hey ho.
Am on Pie stable btw.
Click to expand...
Click to collapse
Thank you.
I checked yesterday and was saying that you need a Pixel phone to install it. Today I just had to join the beta program and voilla!
divvykev said:
Wellbeing is available. I found it be looking for the app in the store but found that it was installed. Signed up for the beta and hey presto....there it is. Can't see it being of any use to man or beast but hey ho.
Am on Pie stable btw.
Click to expand...
Click to collapse
Thank you, I don't find it useful either but this is good information indeed! Post updated.
I don't see any difference between latest beta and this so called stable one, all the issues persists.
Phone heating is really pain in the a$$, especially while charging (most of the time, not always though). I have seen "Temp High, Stop Charging" notification 3 times in a row now.
I have some issues with displaying apps since Pie. For example, when I'm playing music with Youtube Music and Maps has a picture-in-picture overlay the YouTube music app will flicker heavily and the album art won't be visible anymore.
Same for the normal YouTube app and SwiftKey.
Anyone else experiences this?
PiotrekV said:
I have some issues with displaying apps since Pie. For example, when I'm playing music with Youtube Music and Maps has a picture-in-picture overlay the YouTube music app will flicker heavily and the album art won't be visible anymore.
Same for the normal YouTube app and SwiftKey.
Anyone else experiences this?
Click to expand...
Click to collapse
In Snapchat messages, the screen can flicker so much it's unusable. It's usually cause by putting the cursor before an already typed word.
shailendra1993 said:
I don't see any difference between latest beta and this so called stable one, all the issues persists.
Phone heating is really pain in the a$$, especially while charging (most of the time, not always though). I have seen "Temp High, Stop Charging" notification 3 times in a row now.
Click to expand...
Click to collapse
High temperature while charging is very, very bad. If you can't solve this, I'd suggest you go back to Oreo before the battery is ruined.
In any case: did you update directly from DP? Did you check for strange processes via ADB? If you haven't done it, a hard reset can be very helpful as well.
PiotrekV said:
I have some issues with displaying apps since Pie. For example, when I'm playing music with Youtube Music and Maps has a picture-in-picture overlay the YouTube music app will flicker heavily and the album art won't be visible anymore.
Same for the normal YouTube app and SwiftKey.
Anyone else experiences this?
Click to expand...
Click to collapse
RancidPenguins said:
In Snapchat messages, the screen can flicker so much it's unusable. It's usually cause by putting the cursor before an already typed word.
Click to expand...
Click to collapse
Not with the same apps, but I experience this as well. Only advice I can give is to try what you can for single apps (i.e. clear cache/data, uninstall, reinstall) but you probably did that already. If it isn't solved this way, only the next OTA (and/or the next app update) will solve it.
But yeah, this is definitely a thing. I have heavy flicker in some setup wizards for Google apps (most notably Lens) and the volume control will flicker at all times if shown while typing on the keyboard.
valexbast said:
High temperature while charging is very, very bad. If you can't solve this, I'd suggest you go back to Oreo before the battery is ruined.
In any case: did you update directly from DP? Did you check for strange processes via ADB? If you haven't done it, a hard reset can be very helpful as well.
Click to expand...
Click to collapse
Yes, updated directly from DP. I have done factory reset, Hard reset is necessary?
shailendra1993 said:
Yes, updated directly from DP. I have done factory reset, Hard reset is necessary?
Click to expand...
Click to collapse
Actually that should suffice AFAIK. If I were you, I'd try downgrading to a stable Oreo and updating from there. I'm really not sure about it, but probably some bad code is brought over from the beta? But that temperature is definitely not normal, especially if you already did a factory reset.
valexbast said:
Actually that should suffice AFAIK. If I were you, I'd try downgrading to a stable Oreo and updating from there. I'm really not sure about it, but probably some bad code is brought over from the beta? But that temperature is definitely not normal, especially if you already did a factory reset.
Click to expand...
Click to collapse
Maybe some app is behaving inapppropriately. I have done Hard Reset and will see if the problem still persists, else I will degrade.
shailendra1993 said:
Maybe some app is behaving inapppropriately. I have done Hard Reset and will see if the problem still persists, else I will degrade.
Click to expand...
Click to collapse
Not sure if you did that already, but the adb command I wrote in the first post can be useful to check that. Good luck anyway!
The stable pie update is a full rom, not an incremental update, so it doesn't matter from which version you are upgrading, after a reset, no trace of the old operating system remains
I might be wrong but I think the issue with the screen on time not lasting as long as it did in oreo in one of the updates they decreased the speed the battery charges or the curve it charges at, I can't remember where it was mentioned but there were issues and they said it will be addressed in pie, this could be related to the battery getting hot while charging as mentioned by @valexbast .I personally haven't had this issue with screen on time being less but I use my old Samsung charger 2Amp 5V most of the time.
I am having (albiet minor) bugs when adjusting the display density and font size both to their smallest. The lock screen pin entry sticks to the left side of the screen, and notifications & quick settings change themselves randomly to the wrong density and back again. Nokia support refuses to acknowledge these bugs exist but I have seen a few people around the web with similar issues. I did not have any of these issues on DP4 which is interesting!
occasionallyhavingeyes said:
I am having (albiet minor) bugs when adjusting the display density and font size both to their smallest. The lock screen pin entry sticks to the left side of the screen, and notifications & quick settings change themselves randomly to the wrong density and back again. Nokia support refuses to acknowledge these bugs exist but I have seen a few people around the web with similar issues. I did not have any of these issues on DP4 which is interesting!
Click to expand...
Click to collapse
While helpful, I noticed that Nokia support is often instructed to "pacify" the user and assure them everything is normal. But I guess they're taking notes. I haven't tried changing display/font size but the bugs you describe should be easy enough to fix in the next update.
I don't think any of this is app-related anyway, even when we're talking notifications from certain apps. So here's to waiting.
Edit: by the way, I'm a long-time lurker and only newish user so I'm really not a veteran, but hey... welcome to XDA!
Hi all, I'm a very unhappy bunny right now, bought the P20 last year on Vodafone UK. All was fab, loved it. I received an OTA pie update and now many of my apps aggressively closer in the background if they're off focus. Particularity hard for browser pages with a login. The app reloads and I have to log in, again, and again. It has rendered it effectively unable to multi task. (Much like me really). Even as I type this I'm afraid of losing the screen as I received WhatsApp messages. What am I doing wrong? It must be met since I can find no other instances of my problem anywhere.
Cheers
Mark
Anyone able to offer any advice here?
have the same problem. Multitasking on 8.1 worked like a charm, now with pie it sometimes closes my Spotify even if there are 2gigs of ram available
Same problem here, haven't found any solution to this problem yet
I changed the App-Starts to manuell and back to automatic and it seams to work for now...
That's simple. You can control your app activity simply by using Battery Optimizer and set permissions from automatic to manual. Also in System Settings type "ignore battery optimization" you will see a list of apps that are allowed to be ignored while the phone falls asleep or being optimized and you can add more apps if you need to and allow them to be ignored.
hwandroid said:
That's simple. You can control your app activity simply by using Battery Optimizer and set permissions from automatic to manual. Also in System Settings type "ignore battery optimization" you will see a list of apps that are allowed to be ignored while the phone falls asleep or being optimized and you can add more apps if you need to and allow them to be ignored.
Click to expand...
Click to collapse
It works for a few hours than the systems ignors my stettings and kills the background apps again. In 8.1 everything worked fine
PuzzleFoco said:
It works for a few hours than the systems ignors my stettings and kills the background apps again. In 8.1 everything worked fine
Click to expand...
Click to collapse
Might be a bug, needs to check. I'm still waiting for EMUI9 on my device.
hwandroid said:
Might be a bug, needs to check. I'm still waiting for EMUI9 on my device.
Click to expand...
Click to collapse
I'm think about rolling back to 8.1
Rolled back to 8.1 everythings fine now. Hopefully Huawei will fix this problem with pie
Well to tell you the truth guys I just have received an update to EMUI 9 and I don't face any issues at all, I have apps which I need to be running in the background and as I stated before I just moved the badges in App launch section from Automatic to Manual and it's all ok as on EMUI 8.