When I use the lock icon that appears on the lock screen when Smart Lock is engaged, it occasionally pops up an error message that the System UI has stopped. This problem persists even after I've done a factory reset (wiping the cache in recovery before and after). Toggling Smart Lock features off and on doesn't help.
Although the phone thinks the error is unfortunate, I'm not noticing any problems apart from the error message itself.
If it matters: I'm using the Google Now launcher, and my device and SD card are encrypted.
Same
Same thing here. Also using google now launcher, also have sd card, only difference is I'm not encrypted.
Yes I am seeing this one too sometimes. Had to do a battery pull to shut it down (last time), never had that issue before Lollipop
Related
My gnex was super stable since I got 4.0.2 (stock ICS, no changes whatsoever) except that it randomly crashed two days ago. I got "Android UI Stopped" message couple of times followed by lots of similar "stopped" messages refering to different system processes.
looks like two last posters in this thread had the same issue: http://forum.xda-developers.com/showthread.php?t=1383109&highlight=ui+stopped
It was exactly like this: http://www.youtube.com/watch?v=zeoo1Nx2T-o
I tried going into odin mode and starting fastboot. From there I deleted cache. I didn't want to go further and wipe all data and lose all camera files..
I wanted to gain access to internal storage and take backup of DCIM and other folders before wiping memory and going back to factory defaults from fastboot>recovery and was unable to do so.
Every time I went to fastboot or odin and connected GNex to the pc with usb I got could not install Android 1.0 and OMAP4440 drivers error message in windows 7.
What should I do?? Any suggestions? is it possible to get into internal storage if one only can access fastboot/odin?
(btw I tried to turn on gnex again after having it turned off the whole evening and it booted normally!! the only thing was that background wallpaper got reset. nothing else has changed.. dafuq?)
Hi,
I just recently rescued this cellphone which I believe had Darkside 3v7 rom on it. After flashing a couple of factory roms thru odin, i could finally get thru to the OS itself, not without a hassle of force closes. I already wiped everything in the factory recovery. MY first problem was just a black screen after boot with all the capacitive buttons lit, but you could use the upper menu bar (as in mounting the internal / external SD, etc.) I got past that now.
Right now I don't have an IMEI recognized, and i cannot open the market due to force close errors. I was going to use HC-kTool to recover the Imei.
Any suggestions would be appreciated!
Hello,
few days ago I've bought a Huawei Ascend P6, had rooted & updated it to 4.4. As i've tried out the functionality, i noticed the safe boot option and tried it out. (I was curios, because i don't knew this before.)
So, some seconds after the GUI is visible, the system shutdown. Sometimes it starts in the Lockscreen, sometimes in the Homescreen, mostly all of the reboots, the GUI is reloading.
Vibrations are working, but the touchscreen doesn't. As a result of the unremovable battery, i cant enforce a full normal shutdown.
Unfortunately. I haven't made a backup of the internal storage, so i would prefer a fix or a way i could backup the internal storage, before reinstalling.
Some advice, how i can fix that? I would be deeply grateful for some tips.
EDIT: After battery clearing & "normal" boot, same again.
Repost from Sprint forum area, since this main area is much more active...
I have some weirdness going on with my LS990, still running the original ZV4 with Xposed and TWRP. I've never had any problems, until now, with anything on this phone, it's been fantastic and that's why I leave it on Kit Kat.
Starting yesterday, whenever I try to open the stock File Manager, I get the following error dialog:
------------
Note
Cannot read files. File Manager will be closed. Please check Media Storage enable settings and try again.
OK <--button
------------
Sometimes the dialog is in the foreground and I can close it with OK, but File Manager never opens. Sometimes the dialog appears behind my launcher icons and everything is unresponsive until I kill the running process using my nav bar shortcut from G3 Tweaksbox.
Also, I was trying to take a screenshot to include with this post, but it gives an error (Cannot take screenshot. Try again.) when trying to save it, plus the notification just stays on "Saving Screenshot" and is unable to be swiped away. [UPDATE: Noticed the screenshots do get saved in the proper Pictures/Screenshots folder, but the notification remains "stuck"]
I have also noticed my gallery is now empty, yet I can still access all of my pics from third-party file managers. Plus, when I open the camera and take a picture, it doesn't show in the little Gallery bubble at the bottom of the screen - in fact, the bubble doesn't even work, but yet the picture is saved properly.
Has anyone seen behavior like this before? The only thing I have changed on the phone is flashing the new TWRP 3.0.0.0 yesterday, using the image feature in my previously installed TWRP 2.8.7.0. I've updated TWRP plenty of times and there has never been an issue, but one difference I did notice this time was it asked if I wanted to keep System read-only or the default swipe to make read-write, which is what I did since I have Xposed and it modifies the System anyways.
Hopefully someone out there has an idea how to fix this, I really don't want to start all over, at least not until Sprint releases MM for the G3. The strange thing is, everything else is working just fine. My phone is fully functional except for the quirks mentioned above, root is still there and Xposed is functioning properly. I did do a Safe Mode boot to see if I could eliminate any root apps, but the issues were still there even after a safe boot.
Try sd card write fix on the market just for kicks u mighta lost permissions to the ext sd try switching save point to internal and see if they save
Unfortunately, I'm not using a microSD card, everything is saved to the internal memory. I thought it might be something with permissions, was thinking about trying the "fix permissions" option in TWRP but I'm not sure if that would make things worse. I've already tried a cache and Dalvik wipe, but that didn't fix anything. Even in Safe Mode, nothing changes.
I've searched online and haven't seen anyone else with this issue, it's very strange. I wish Sprint would hurry up and drop the MM update so I would have the perfect excuse to flash back to stock.
After boot loop issue with my LG G4 in February. It was replaced by the repair station without firmware and now with the firmware and Lollipop 5.1 installed with no updates available for Marshmallow.
Now I have noticed that camera crashes when selfie mode is used or front facing camera. This maybe the beginning of things going wrong again....
Can anyone recommend a fix. Phone is not rooted. And I don't want to use the very unstable Android 6. I bought this phone u locked via Amazon and unfortunately don't want to return it to them as LG has changed the serial number.
Totally stuck between a rock and a hard place as can't be without a phone for another 2 weeks.
Sent from my PLK-L01 using Tapatalk
Look for the camera app in the apps manager - all apps and try to clear cache. Test.
if that does not work, try clear data option above.
Test again...
had a similar problem with another device because i twiddle a setting. and lost the camera. The above fixed it. I learnt not to twiddle that setting again.
Hi, I had this issue and none of the software workaround worked for me. The issue is related to a defective hardware part, the power switch (B0181RDMM6). I replaced this and it fixed the issue. When this part is defective, it can hinder the call screen (meaning that when you dial or receive a call, the screen will not turn on for about 10 seconds) and it can also make the camera useless (meaning that the user will receive an error message on boot and when trying to use the camera. the error message is "unfortunately camera has stopped working". This is because the camera cannot work when the flash is used as a flashlight. It seems that when this part is defect, the phone thinks that flashlight is always on.
you can easily find the part on amazon at amazon.ca/s?k=B0181RDMM6&ref=nb_sb_noss
Unfortunately camera has stopped working Android error
Method 1: Restart phone
Well, this is a very straightforward step that could easily fix the camera has stopped error on your smartphone.
Method 2: Clear cache and data of your Camera application
Most of the time, the application cache may cause this error. To fix it, simply follow these steps:
Go to Settings >> Apps (or application manager) >> Swipe to go to “All”
Now scroll down the list of apps, and tap on “Camera”
Tap “Clear Cache” & “Clear Data”
Now restart your smartphone
Open the camera app and check for the error.
Method 3: Formatting external microSD card
This method is applicable only if you save your photos on your external microSD card. Simply remove the SDcard and move all of files stored on it to your hard drive. Then insert the microSD card in your PC or Laptop’s SDcard slot and format it. To format it, right click on the microSD card drive after it appears on your PC, then select “Format”. Before formatting , you can also try checking for error by right clicking your SDcard and selecting “Properties” >> Tools >> Check