Has anyone experienced random system ui force close after rooting? All I did was install adaway and used the chainfire workaround to get it working. It continuously force closes even after reboots. The only way to get out of it is to plug the phone in to a charger...weird I know.
I had the exact same thing happen. In my case it was MalwareBytes that was causing it. I plugged into the charger, got the homescreen and noticed malwarebytes crashed too, and wouldnt open. Uninstalled it, rebooted and no more System UI crash errors.
I had that issue come up while I was using Messenger. I have unlocked and rooted my phone. No other changes. I did use Titanium Backup to import an xml of my previous text messages. (Added later: the battery was probably close to 15% or less when this occurred.)
Have you tried uninstalling ad-away? I've done the exact same steps you describe with no issue.
Yes i have faced the same problem, i think it happens when the battery is low. Don't know if its root or EX kernel!
Had the same UI issue this morning. When I plugged the charger in, the UI force close issue immediately stopped. The battery was at 7% and when I unplugged it at 44% the issue is still gone.
I believe as well that Adaway is causing the issue. Before installing Adaway, the error did not appear. I reflashed the factory images and obviously the error went away.
A temporary solution suggested @blk_jack is to turn on power saver @ 15% auto
The issue was reported to Google. Everyone should star it so it gets more attention.
I thought I was alone, it happened shortly after I froze Pixel Launcher with Titanium Backup. I'm glad to know it wasn't the case and charging the phone resolved the issue.
Related
Hello android geniuses,
I have a weird problem with my infuse.
Earlier today I installed a new launcher app..... i was at 50 or 60 % battery.
Suddenly the launcher froze..... and when it woke back up 2 minutes later....my battery was down to 5% ...WTF
Afterwards...every time i plugged the USB in to charge it, it froze and rebooted.... but it DOES charge.
When I turn it on it boots perfectly fine....but it has to be unplugged.
If it is plugged in and I turn it on to boot....it reboots and goes back to the charging screen....
So weird.....
PS> The launcher (ligning launcher) has been uninstalled and my old launcher activated and running perfectly.
Thanks for any help
Any idea?
Edit .... I have used a battery calibration program to erase batrrystats.bin
Well, this issue has been address a couple times the last few weeks. Its a very weird situation that seems to be happening lately. So far i havent find a way to fix it, and to me this is a hardware issue. Something similar to what happens sometimes to certain iphones also. The solder contacts from certain ics(integraded circuits) will breakdown. And the phone will not work as it should because of that. If i find something, ill let you know...
Flash the device back to stock & perform a factory data reset.
Forenote, my N5 was running PSX v2 and Franco Kernel r13 flawlessly for weeks when this ramdomly happened.
Used my phone today just as I have for weeks on end with little to no issue until around 8 or 9 hours into my day the phone started to lag very badly. Redraws, stutter, unresponsiveness, you name it. I was surprised as this phone usually flies! So I cleared my recent apps and that seemed to help slightly, but it still was very slow. I used cache cleaner's built in ram cleaner to stop all running processes (which I never do) and it seemed like the issue was fixed. The system UI and launcher redrew and I was good to go.
Until I started to play some music in Play Music, a pop up constantly popped up that YouTube has stopped working. I didn't even use YouTube today! I tried to then open the YouTube app and it wouldn't open whatsoever. No animation no execution, just a dialog box reading, "Unfortunately, YouTube has stopped working." I went into app settings and cleared cache/data/and force stopped and the app still was misbehaving. I reinstalled the app via the play store and it still wouldn't open. The dialog box wouldn't stop popping up this whole time mind you.
I was thinking what the hell is wrong with my phone today!? Maybe a reboot would fix things. I tried rebooting and my phone got stuck at boot animation. I force shut off and rebooted into recovery, formatted cache and dalvik cache and rebooted. This time the boot animation actually froze.. I was like what the f***! I let it sit for a few minutes to see if anything would happen without any luck.
I force shut off again and now the phone won't even turn on. Not into bootloader, not normally, the thing won't even charge! So here I am with a dead phone and a $450 paperweight. I'm just so lost I have no idea what could've caused this really unusual sequence of events.
Any ideas? Thanks in advance.
A bad phone. Rma it
Was the phone hot when the weird things happened?
ctbear said:
Was the phone hot when the weird things happened?
Click to expand...
Click to collapse
Nothing seemed out of the ordinary temperature wise.. Although my phone has overheated and shut off before that was maybe 2-3 weeks ago..
Sent from my Galaxy Note 8.0
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 .
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.
Same problem after android 8.0 update
If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk
My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
wrong place sry
Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now
Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?
That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.
Got mine at release. November 16. Google won't replace it either. I have a one pixel brick
I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.
Hello there. I think my phone's been compromised. It's been acting up since my last OS update. I have a OnePlus 9 LE2115, currently running oxygen os 13.1.
I was searching through apps because something's draining my battery and i noticed that all of my apps are always running even tho I've turned them all off manually and turned off background data usages. I can't force stop on about 60 percent of my apps anymore.
Upon further inspection, i found a few system apps I've never seen before and cannot find any info on when googling.
App #1- Metis ( i cannot find any info on this at all or delete this app but i have disabled it but i don't think that did anything) when i googled 'Metis ui' this is something that caught my eye... (https://github.com/europeana/metis-ui/blob/develop/package-lock.json) i don't read code so I'm not sure what it even is but it's the only thing i saw that might be relevant to what's installed?
App#2- media:: 10065 ( it doesn't show up as an app normally, just when 'show system' apps on my apps list in settings.
App#3-i think it's from when i installed TikTok on my phone but have since deleted it, but as you can see the 'musically' file was found on my phone after TikTok app was deleted.
I'll attach screenshot of what I'm seeing... Idk what to do. Can you please help me with this?
I was in the same situation with my op9 after update to 13.1 The absolute only way I could achieve proper battery life and it was from a suggestion out of the oneplus community. Factory reset fixed everything. Now I'm getting 22-30 hours off charger and up to 7 hrs Sot. This will fix your issues as well. It stinks but is what has to be done.
Generally, the recommendation is to factory reset after OTA. Sometimes bugs pop up and factory reset fixes them. I have had a few myself lately. Anyways, if it still doesn't fix your issues, I recommend to use MSM Tool to revert back to factory firmware. It will take you back to OOS11. You can then OTA all the way upto latest one. Then do a factory reset and start using the phone.
You could first try to keep device plugged in and charging 30 min to an hour after it's completely full charging to optimize apps See if this works before having to reset device .
mattie_49 said:
You could first try to keep device plugged in and charging 30 min to an hour after it's completely full charging to optimize apps See if this works before having to reset device .
Click to expand...
Click to collapse
I've had it at a full charge and it will last a little longer but all my apps are still running in the background. And it takes so long for my fast charger to charge up my phone too. I was hoping i didn't have to factory reset but... I guess if it's the only thing that can be done for this. I've had to resort to fingerprint locking every app to see if would stop the problem. It didn't. Well, here goes nothing. Time to backup my data. I'll come back after my reset and update. Thank you for your help guys!
If you only started having these issues after updating to 13.1, then its best you do a factory reset. Its not uncommon for weird issues to happen such as battery drain. I once lost the ability to use 5G after an update and a factory reset fixed it. If you believe your phone might be compromised, well a factory reset will fix that too.