I love the fact that this phone is still getting security updates btw. But after the November security update TOS317M the camera and flashlight stopped working. Still running stock haven't rooted or put TWRP. Has anyone else experienced this?
Edit: Taking out the battery fixed it
dennis212 said:
I love the fact that this phone is still getting security updates btw. But after the November security update TOS317M the camera and flashlight stopped working. Still running stock haven't rooted or put TWRP. Has anyone else experienced this?
Edit: Taking out the battery fixed it
Click to expand...
Click to collapse
My camera is working but since the update it has changed the storage location with no option to change it
Related
As the title states lately I have been having fingerprint issues. Setting up fingerprint to unlock my phone works perfectly with the phone itself. When it's comes to apps Chase, Cinemark , TMobile setting up fingerprint verification goes through correctly. Now opening the apps and using my fingerprint to verify does not unlock the app. Apps just keep telling me to put my assigned fingerprint in again. Anyone noticing issues lately? Is there any way to troubleshoot this? I have reflashed the OTA (8.1 Oreo - March update) multiple times- no change.
Running stock 8.1 Oreo March update
Any other suggestions?
LubbocksFall said:
As the title states lately I have been having fingerprint issues. Setting up fingerprint to unlock my phone works perfectly with the phone itself. When it's comes to apps Chase, Cinemark , TMobile setting up fingerprint verification goes through correctly. Now opening the apps and using my fingerprint to verify does not unlock the app. Apps just keep telling me to put my assigned fingerprint in again. Anyone noticing issues lately? Is there any way to troubleshoot this? I have reflashed the OTA (8.1 Oreo - March update) multiple times- no change.
Running stock 8.1 Oreo March update
Any other suggestions?
Click to expand...
Click to collapse
I have not had any issues with apps that rely on / give the option of fingerprint authentication. I also have Chase installed and I just tested it and it works fine. I also have Amex, Bank of America, alarm.com, ADT Pulse and fingerprint access seems to be working fine on all of them. I am also running stock 8.1 Oreo / March update- but I am unlocked and rooted with Magisk. One suggestion based on some Fingerprint related struggles I had recently (when TWRP couldn't decrypt and I had to remove Fingerprint/pattern security during the update process and then add back after updating/rooting)....I found that some apps that had already had Fingerprint access enabled, didn't behave well when Fingerprints were removed then added back on the phone. The best workaround I found in those cases was to uninstall the app completely, fully setup Fingerprint security on the phone, then install the apps again. This definitely was the case with Amex, Chase, and Bank of America. Just something to try...good luck.
So using the OTA multiple times via fastboot wouldn't have cleared the apps?
LubbocksFall said:
So using the OTA multiple times via fastboot wouldn't have cleared the apps?
Click to expand...
Click to collapse
Sideloading or taking the OTA natively doesn't typically wipe app data in my experience. Flashing the factory image (without removing the -w) would wipe your data (and most everything else)...but that creates alot of work in setting up your phone again. I found uninstalling the troublesome apps, setting up fingerprint security/pattern, then reinstalling and setting up the apps relying on fingerprints worked the best for me - but the situations are a bit different as my troubles always were related to adding new fingerprints to the phone and apps that had the "old" fingerprint information already....for me - uninstalling / reinstalling the apps solved my issue.. YMMV
My camera encountered a fatal error after Android Pie update but I'm still able to use Snapchat. I'm using a brand new Pixel 2 Xl and right after I updated to Pie yesterday I haven't been able to connect to my stock camera. Has anyone else been experiencing this?
Aerro47 said:
My camera encountered a fatal error after Android Pie update but I'm still able to use Snapchat. I'm using a brand new Pixel 2 Xl and right after I updated to Pie yesterday I haven't been able to connect to my stock camera. Has anyone else been experiencing this?
Click to expand...
Click to collapse
Try clearing data/cache
Then force stop
Then reboot phone
What he said in the post above. Had the same issue on DP4. It fixed it. Reboot after you clear.
I had the same issue. I didn't think about clearing the camera app cache. I flashed the factory stock 9.0 image, and the problem disappeared.
I've done all of the above I cleared cache and data with a restart I also updated OTA if that wasn't mentioned. I've also done a factory reset with Android Pie and still getting the crash prompt.
Aerro47 said:
I've done all of the above I cleared cache and data with a restart I also updated OTA if that wasn't mentioned. I've also done a factory reset with Android Pie and still getting the crash prompt.
Click to expand...
Click to collapse
Not cool
Sounds like a hardware issue now.
I have this issue also and no fix with it, it's hardware, at least on mine, I have try a couple things, wiping, deleting, flashing, restoring, even downgrade to Oreo and still freezing and rebooting when try to open the app and camera.
This start to happen when I update to September update.
I contacted Google support and the most rare question it was; What was the camera app version I have?ñ mine is 5.3 I said, so then he/she told me that is going to send me a replacement.
I am thinking that they know what this issue is and probably there's no fix for it with the software, only change the camera or whatever is the problem with the board.
Here are some screenshots:
OG Pixel XL 32GB on Project Fi, rooted with Magisk 17.1, previously on Android Pie 9.0.0 August security update.
Just sideloaded to September security update via the usual method. Upon booting, fingerprint sign-in was disabled, and in "Settings," it appeared that my fingerprints had been cleared. Tried enrolling fingerprints via "Pixel Imprint," but while it registers reads properly, enrollment fails at the last step with the message "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger." No luck with other fingers. Gestures (notification shade pulldown) still works. Tried flashing back to August update, but same issue persisted.
Anyone else have this issue, or know of a solution? Thanks!
davidrqli said:
OG Pixel XL 32GB on Project Fi, rooted with Magisk 17.1, previously on Android Pie 9.0.0 August security update.
Just sideloaded to September security update via the usual method. Upon booting, fingerprint sign-in was disabled, and in "Settings," it appeared that my fingerprints had been cleared. Tried enrolling fingerprints via "Pixel Imprint," but while it registers reads properly, enrollment fails at the last step with the message "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger." No luck with other fingers. Gestures (notification shade pulldown) still works. Tried flashing back to August update, but same issue persisted.
Anyone else have this issue, or know of a solution? Thanks!
Click to expand...
Click to collapse
I didn't not have that issue this upgrade or any others. The only time I have lost Fingerprints is when I have had to disable security when TWRP is unable to decrypt. But that was not the case for September update. You might try disabling security completely. Rebooting. Then reenabling security and Pixel Imprint. Maybe something didn't get cleared all the way when your Pixel Imprint got disabled or partially cleared...
sb1893 said:
I didn't not have that issue this upgrade or any others. The only time I have lost Fingerprints is when I have had to disable security when TWRP is unable to decrypt. But that was not the case for September update. You might try disabling security completely. Rebooting. Then reenabling security and Pixel Imprint. Maybe something didn't get cleared all the way when your Pixel Imprint got disabled or partially cleared...
Click to expand...
Click to collapse
Thanks for the tip. Just tried this and no dice, however. Have never had any issues with any previous updates, including with Oreo when a lot of other people were having fingerprint reader problems.
davidrqli said:
Thanks for the tip. Just tried this and no dice, however. Have never had any issues with any previous updates, including with Oreo when a lot of other people were having fingerprint reader problems.
Click to expand...
Click to collapse
Any progress on this? Were you able to get it working?
sb1893 said:
Any progress on this? Were you able to get it working?
Click to expand...
Click to collapse
Nope, still the exact same. Issues also persist in Safe Mode.
Had this issue with DP4. Had to do a factory reset. Sorry.
jaytv said:
Had this issue with DP4. Had to do a factory reset. Sorry.
Click to expand...
Click to collapse
Gotcha... thanks. Not in a position to do a factory reset now, but maybe in a week or so when I'm back from a trip. Anyone else have any luck fixing this without a factory reset?
Update: Did a full factory reset, which fixed the problem. Not an ideal situation, but at least it worked.
davidrqli said:
Update: Did a full factory reset, which fixed the problem. Not an ideal situation, but at least it worked.
Click to expand...
Click to collapse
Glad you got it sorted. That normally does the trick but it does suck if you don't have everything backed up.
Is there anyone experiencing this? I have re-flashed again and its the same. Only why i can get it stable is to install an update from apk mirror and then unistall the update in applications. Unfortunately when my phone reboots it happens again and have to do the same thing over and over.
It seems to be issue with gesture controls. I seen some had this issue with Decembers update. By reverting back to buying control fixes it temporary. Anyone know how to fix this or will I have to wait for an update?
After the June update, I can't tap notifications that used to lead me to the message.
Anyone know a fix?
Just tested now with a what's app message and a txt and rcs app working for me
This is what happens regardless of the notification
I just re flashed the update and checked before I rooted, it was fine before I rooted.
Why would root affect reading my notifications?
vibrantliker said:
I just re flashed the update and checked before I rooted, it was fine before I rooted.
Why would root affect reading my notifications?
Click to expand...
Click to collapse
I have no clue sorry I don't root at all I think you might have that delayed notifications bug that I saw get reported on here but I have no clue
Edit to ad I hadn't watched your video before the reply have you tried a clean fresh install see of that fixes it
vibrantliker said:
I just re flashed the update and checked before I rooted, it was fine before I rooted.
Why would root affect reading my notifications?
Click to expand...
Click to collapse
I had the same issue and it turned out being a custom font magisk module. I updated the zip for June firmware and it works fine now.