Related
Anyone else getting this error? After reading the two main errors seem to be faulty camera hardware and bar code scanning apps. I uninstalled my bar code scanner and the problem persists. There is a small dent next to my flash under the camera but this came with the phone and my camera worked for a while. Taking the battery out and putting it back in fixes the problem about half of the time, but only is good for one to two uses. I'm thinking of sending this in, but I'm waiting until the SGSII HD is out in case they offer to replace it with any phone. Wishful thinking, I know.
And here's the error:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
HJZS2K said:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
Click to expand...
Click to collapse
Stock ROM not rooted. No modifications what-so-ever.
8mileroad said:
Stock ROM not rooted. No modifications what-so-ever.
Click to expand...
Click to collapse
Try doing a factory reset. Sometimes an app installed on the phone might screw up with a hardware's function. For example, I've always use Screebl Pro on my phone to let it control how my screen turns off. I decided to try their new Beta version. A few days later, I cannot seem to manually turn off my screen by pressing the power button. Every time I press the power button, the screen will come back on on its own. I can try up to 4-5 times before it eventually goes off. I though my phone finally broke as I tried uninstalling and reinstalling apps, changing settings here and there to no luck. I finally realized about the beta Screebl I had installed, and decided to disable it. The moment I did that, the phone was back to normal, no weird things happening to it.
So try doing a factory reset first before sending it back.
Strangely enough uninstalling Reconage has seemed to fix this. Can anyone else confirm it breaks your camera? The comments don't say it does so it must be something with the Nitro.
I get it too on cm7 all the damn time. I can record 1 video then after I stop, it messes up and I have to reboot to record again.
Any more definitive answer on this issue? My wife's Nitro HD has started giving this error in the last few days and no amount of rebooting seems to be fixing it. She is stock plus a few apps. I uninstalled nearly everything that uses the camera, reboot the phone, and still have the problem.
Alternatively, is there a way to see what apps were installed/updated by date? The last photo she took was on 6/13, so if we can figure out what apps have been updated since then that might help us get to the bottom of the issue.
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju-rooted
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
2. Did OTA update with Bluetooth on and cannot switch off Bluetooth now with devices paired. Bluetooth switches back on automatically as soon as I try to switch it off. Correct me if this is a change in 4.2.1 or if this is indeed a bug.
Other complaints
1. apps on lockscreen widgets starting up randomly
2. 3 sec lag to start daydream and camera app
3. butter gone
4. laggy
luckily no random reboots and broken Bluetooth as others have reported on my device yet. I am not happy Google.
1. doesn't happen with me
2. can't test that (no bluetooth accessories)
Others:
1. lockscreen needs improvement (like clock widget auto resizing itself to full screen when swiping through screens)
2. my camera app starts in less than 2 seconds
3. 4.2 is a little heavier than 4.1.2 but still buttery compared to other high end phones
4. not on my phone
Something which happens to me when creating events on calendar... If i manually type in the end time of the event and the minutes are 59 (e.g. setting the end time to 22:59) when i press okay the time goes back one hour (e.g. 22:59 becomes 21:59). Anyone else?
I have none of the issues any of you have specified.
Sent from my Galaxy Nexus
I got the same Recent App bug, which I didn't notice before!
But overall it is running smoothly. Did you try factory reset or flashing stock image?
jam_27 said:
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
2. Did OTA update with Bluetooth on and cannot switch off Bluetooth now with devices paired. Bluetooth switches back on automatically as soon as I try to switch it off. Correct me if this is a change in 4.2.1 or if this is indeed a bug.
Other complaints
1. apps on lockscreen widgets starting up randomly
2. 3 sec lag to start daydream and camera app
3. butter gone
4. laggy
luckily no random reboots and broken Bluetooth as others have reported on my device yet. I am not happy Google.
Click to expand...
Click to collapse
* I listen to podcasts via Bluetooth car audio during my drive to and from work. Ever since 4.2, I get frequent Bluetooth disconnects while I am listening to audio. This never happened before 4.2. Unfortunately, 4.2.1 did not fix it.
* When third party apps such as Locale or Tasker turn WiFi on, it will not connect to any access points in range. However if I turn WiFi on via the WiFi settings, it connects immediately.
* Car mode is broken in 4.2 and 4.2.1. A "car home" app used to be able to invoke a mode where the home button would return you to the car app instead of the desktop. Now, the home button drops you to the desktop and crashes the launcher (Android's desktop process).
* Overall, much more lag and delays. Looks like 4.2.x is optimized for the Nexus 4 and its 2GB of RAM. 4.1.2 seemed perfect -- too bad we only had it for less than a month.
Well, my screen shuts off at random.. I can still press stuff, but it's totally black!! I have to put the battery and restart
bugs
I cannot use my BT headset, it disconnects when screen is off.
Camera is very very laggy.
Wipe phone and flash complete stock image!
I have none of these bugs! Bluetooth works like a charm.
Stock browser omnibox issue. When I open bookmarks and links from 3rd party appss, it's all good.
But when I try to type a search or url, the adress bar freezes and stays frozen on the screen. Rotate the screen and it becomes a black empty wasted space.
Is it a bug in in 4.2/4.2.1 or is it my phone?
Sent from my Galaxy Nexus using xda app-developers app
i find it takes a couple of swipes of the security pattern at times, screen doesnt always respond as quick if ive not used my phone for a few hours.
didnt happen on 4.1.2 , not a massive issue but i do notice it
FrankNS said:
Wipe phone and flash complete stock image!
I have none of these bugs! Bluetooth works like a charm.
Click to expand...
Click to collapse
Firstly, It sounds bit too much to do a complete wipe and re-flash or a factory reset for just a dot.dot update.
Also, I have been reading that for some wipe and re-flash did not fix the Bluetooth issue. Also, a just a factory reset after OTA hasn't worked for all.
Can we please have confirmation here that a the factory reset thingy works so that all of us having issues can give it a shot?
In case we should wipe and re-flash, can it be done in the following way?
1. full backup system (in my case using titanium backup)
2. factory reset
3. copy the relevant image , yakju 4.2 in my case, into memory and flash zip using cwm recovery (6.0.1.5 in my case). then flash 4.2.1 similarly.
4. restore root.
5. system data/apps restore
please let us know.
International Yakju here and I've get the most annoying out of the problems. Random soft restarts. I've done a soft reset and it didn't help. I'm getting really pissed at this. Thinking of rolling back to 4.1.x
I havent tested bluetooth but I have random errors, sometimes when phone is locked It vibrates, I unlock it and it is asking with wich program I want to open, I choose gmail and it attaches a bug report, a .txt file with 4mb and a screenshot tottaly black.
weird. 4.2.1 yakju
jam_27 said:
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju-rooted
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
2. Did OTA update with Bluetooth on and cannot switch off Bluetooth now with devices paired. Bluetooth switches back on automatically as soon as I try to switch it off. Correct me if this is a change in 4.2.1 or if this is indeed a bug.
Other complaints
1. apps on lockscreen widgets starting up randomly
2. 3 sec lag to start daydream and camera app
3. butter gone
4. laggy
luckily no random reboots and broken Bluetooth as others have reported on my device yet. I am not happy Google.
Click to expand...
Click to collapse
I agree with the 3rd and 4th points. Camera app is quite different from ISC 4.0 and Jelly Bean 4.1, both icons are rotating while the phone is rotated. However, Jelly Bean 4.2's icon, instead of rotating, they shift the position while the phone is put as horizontally. I hope these will be fixed in the near update.
jam_27 said:
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju-rooted
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
Click to expand...
Click to collapse
I got the same bug on both my galaxy nexus and nexus 7. For those who said that they don't have this bug, did you leave at least one app on and rotate the screen while having the recent apps menu open? Try again.
NexusDro said:
I got the same bug on both my galaxy nexus and nexus 7. For those who said that they don't have this bug, did you leave at least one app on and rotate the screen while having the recent apps menu open? Try again.
Click to expand...
Click to collapse
Just tryed that, no bug.
Can I turn off updates
OTA update to 4.2, totally stuffed my setup, flashed 4.2.1, no difference, have now flashed stock 4.1.2. to make the phone work as it should do.
Problem 1: The signal strength meter vanished on my car screen, no indication that bluetooth had connected.
Problem 2: The speaker, as I am sure we are all aware, is rubbish. I am using the pucker car mount and have a small speaker system set up and hooked into this so that I can hear warnings from CamerAlert. The phone connects over bluetooth but the CamerAlert warnings are directed out of the device speaker and go via the car mount to the speaker system - works a treat. With 4.2 this totally disappears and I get half a warning from the device speaker itself.
Having gone to 4.2 and back I can vouch for the fact that it is the update that is wrong.It will take me another day to get the 'phone back as I want it and I will then do a full backup. Thanks a bunch Google for, really professional update.
All I want now is for the 'phone to stop nagging me to update, anyone know how to turn off updates ??
my phone freeze after taking a picture today, so weird it didn't happen before and i need to pull out the battery in order to restart the device because the power button not give a respond.. so sad.. in 4.1.x everything is good.. for the first time on my gnex i need to pull out the battery twice today.. huh!!
Wow. I was very pissed of with the overall lagginess of 4.2/4.2.1 update, but I thought I might wait and hopefully Google will fix that. But then I noticed just how ofter the stock launcher crashes (leaks from RAM anyways). 5-10 times in an hour after using heavy apps like Chrome, Pocket, Facebook etc I press home button and I get and empty wallpaper. WTF? How is this even possible for a stock app?. And then there are things I've mentioned in other similar 4.2-reated threads like camera animation that lags and music widget that stops responding and keeps playing after headphones are unplugged...Gosh, that's the worst update (for me at least) ever. And now I noticed that recent apps bug. It does exist. Awesome.
So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.
After a few days of the update pestering me I decided to go for it.
Now there are 2 things that are very annoying.
The first, whenever the screen comes on, there is a slight delay in the watch face.
It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.
I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.
The second thing is that the watchface doesnt turn on when I receive texts anymore.
The vibrate function still works, but the screen won't light up.
Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.
Thanks
Make sure 'card previews' turned on from the android wear app, other wise your experience with the faces sounds buggy! A factory reset would help on that.
Factory reset doesnt work, this also happens to me since the update, looks like this is a firmware problem.
Damnit, I wish I didn't update.
Battery is also noticeably worse.
airjordan223 said:
So I was hesitant to proceed with the update since my 360 has been working so well and the battery life increased tremendously when I got my Note 5.
After a few days of the update pestering me I decided to go for it.
Now there are 2 things that are very annoying.
The first, whenever the screen comes on, there is a slight delay in the watch face.
It lights up with a black face and the hands are white, then it switches to whatever face I have and respected dials.
I'm not using facer or anything, just the stock moto Dials 2. This is very annoying and makes the watch seem slow.
The second thing is that the watchface doesnt turn on when I receive texts anymore.
The vibrate function still works, but the screen won't light up.
Is there a setting that changed making this the default? I would prefer the screen turn on when I receive texts.
Thanks
Click to expand...
Click to collapse
Same exact two issues here and I'm shocked I haven't seen more people complain about them. The first one is a nuisance but the second one completely devalues the purpose of the watch making it useless. Not seeing the text/email/etc... and only having a vibration on your wrist is pointless. I could keep my phone on vibrate in my pocket if I wanted to be notified of a new text/email without seeing the actual message. Please post a fix if one is found!
antknee2016 said:
Same exact two issues here and I'm shocked I haven't seen more people complain about them. The first one is a nuisance but the second one completely devalues the purpose of the watch making it useless. Not seeing the text/email/etc... and only having a vibration on your wrist is pointless. I could keep my phone on vibrate in my pocket if I wanted to be notified of a new text/email without seeing the actual message. Please post a fix if one is found!
Click to expand...
Click to collapse
Can you found a way to fix it?
Enviado desde mi SM-N920I mediante Tapatalk
The first issue is because the watch now comes on in ambient mode first. Even if you don't use ambient mode. It sucks. Luckily i use Watchmaker for my watch face so I went in and made all the parts (hands date etc...) to be visible in ambient mode.
I have noticed that if I wait a couple of seconds the notification does appear on my watch screen but it is after the vibrate, not immediate. I thought it wasn't showing up at first too. Still, I wish it was quicker as I look right away.
Sent from my SHIELD Tablet using Tapatalk
I went back to using Facer for my watchface and the delay is gone.
Also did they completely remove the restart option? Now it's just power off, and then press and hold the side button.
I'm experiencing both issues as you do on 6.0.1.
Also yes, reboot option is gone from update.
The renamed reset with "unpair from watch". Not gone, just to mess with us.
Sent from my SHIELD Tablet using Tapatalk
frenziedfemale said:
The renamed reset with "unpair from watch". Not gone, just to mess with us.
Click to expand...
Click to collapse
Reboot is not reset...
I've also noticed that theater mode does not work after the mm update (unrooted, ota). I usually set it to theater mode at night to avoid burn in and just because I don't want it on all night. Now, it looks like it's blacked out, but when I wake up, the charging screen is lit up. Anyone else getting this?
I have the exact same issue after the update. Theater mode will not keep the display off if the watch is being charged. Off the charger, it works as expected. Quite an annoying bug.
If I turn ON the theatre mod with double press the power button before I put the clock on the charging dock, after that screen continue charge with screen off.
For me it's work.
Can anyone try it?
Sent from my D6503 using XDA Free mobile app
Just tried that - doesn't work for me. Screen turns off but once I put it on the charger, it comes back on after a few seconds. I'm watching it and it's still on a few minutes later.
Same here. Screen always turns back on
I'm getting the first bug the OP mentioned havn't noticed the second one though.
However the first bug is annoying enough, hopefully there'll be a quick patch.
Little patience, update to Marshmallow is great.
Here's what I mean with screen off when charge:
So in the morning until you take it out of the dock and go to work.
Sent from my D6503 using XDA Free mobile app
still on 5.0.1
man i just boughjt it 2 days ago and battery sucks,now i am trying to update cause i heard batter improved,but i cant ,watch start download but take too long and then show me a message charger to update blah blah but phone is charger is over 90 percent i have reset phone and uninstalled app many times this is ridiculous now i know why motorola was giving away this pos when yopu buy the 64gb moto x pure edition arrrrgggg
Srandista said:
Reboot is not reset...
Click to expand...
Click to collapse
Sorry I read wrong...but wouldn't you just use the power off option and then turn back on to reboot?
Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.
1up1up said:
Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.
Click to expand...
Click to collapse
No issue here mate, still as fast as it was before on 8.0.0. Might wanna try another reboot to see if it fixes your issue. You could then always try a factory reset as well.
I just downloaded and reinstalled the 8.1 factory image. Went through and setup phone from today's backup and added fingerprints. While the phone was finishing downloading apps from backup, the fingerprint unlock was fast and normal as usual. After apps updated and restore finished, I restarted the phone. Immediately, the slow fingerprint unlock returned. I have very few apps and this wasn't an issue until after I applied the 8.1 OTA side load before the initial posting of this thread. Additional testing of the speed by pressing the power button then unlocking with fingerprint reader yields inconsistent unlock speeds. At this point, I do not want to say that maybe it's because of a particular app that is installed on the phone, but rather it's possibly a problem with 8.1.
Any thoughts?
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
I have this exactly
I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.
Yup. First thing I noticed was this delay between when the fingerprint is actually recognized (vibrate), until I actually get visual on the screen. Around a second or more
I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.
SOLIDFND said:
I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.
Click to expand...
Click to collapse
I too, am not a fan of the "Always On" display but can confirm that this does fix the problem. Thanks for sharing your finding.
sn0warmy said:
I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.
Click to expand...
Click to collapse
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...
I found hit super hit or miss. When I flashed my rma phone to dp2 it was slow to unlock. When I flashed 8.1 final it was fast again. I had to flash 8.1 final again but this time the phone was slow to unlock. I got my new device flashed 8.1 on and it is thankfully unlocking quickly. I wish you all luck
I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153
Today I also noticed a random "static pop" noise coming from the phone while Chrome browser was open. It was quite distinct and loud and happened twice.
SOLIDFND said:
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...
Click to expand...
Click to collapse
Same problem, gets fixed with always on display but if the screen is not on in between the seconds of pressing the power button and ambient display kicks in then the problem is still there. Also tried deleting the fingerprints and redoing the fingerprint initiation, but it did not help. The sensor registers the fingerprint by vibrating but screen gets on only after a second or more. sometimes though it is instantaneous. another problem for Google to fix I guess in next month update.
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same issue here since updated to 8.1
The fingerprint is recognized quickly (you fell the short vibration) but the screen turns on with a delay of about a second.
I have the same issue when I just press the Powerbutton - it also takes about a second until screen turns on.
Guys, I'm so disappointed with my Pixel 2 XL. Never had so many issues with a stock firmware phone.
Been running 8.1 through the beta for awhile now and haven't had any of these issues. Not sure if I'm just lucky or what but it's been humming along just fine. Just installed the 8.1 official over the 8.1 beta and haven't noticed anything as of yet. Will pay attention to see if I notice anything being slower.
I am also seeing the issue after updating to 8.1. It takes about 2 seconds for the screen to appear. AOD does make it faster but I can deal with it and hopefully google fixes it soon
I searched he'd the issue on google- obviously because I HAVE IT TOO. This is infuriating. This is major functionality. after 8.1 the finger print reader is slow AF. It feel like my old galaxy s4 that i just came away from when i would swipe to unlock it. How many times do we unlock these things a day? We just went from the fastest unlocking phone to the slowest. Why is this effed up? I'm pissed.
We have ppl whining about the freaking hamburger emoji having the cheese on the bottom and the wrong foam in the beer mug, meanwhile it takes forever to get into the phone to do anything much less get to the Emojis. How does BASIC functionality go BACKWARDS with an update?
What's even more infuriating is I can't go back to 8.0!!! Google doesn't allow it do they? I am coming to this phone off a Galaxy s4. One of the big benefits of the pixel family is the "fast updates."I saw someone argue that this isn't necessarily a plus sometimes these new Android versions slow a phone down, and it's done. Sometimes, like in this case, bugs are introduced. The very first update I took on this phone largely argues his point.
Another thing I'm noticing is the battery life seems to be dropping much faster. I'm wondering if it's the flash kernel 2.0 I installed though.
I will be filing a complaint on the link someone so kindly posted above (thank you), and I will be going into the chat option through the help menu on my phone to file a complaint there.
EDIT: it also seems like Google assistant isn't working now either. "Ok Google" brings her up. The mic registers my talking, but no results are displayed.
EDIT 2: I also forgot to mention that along with the slow unlock the swipe function on the finger print reader has been altered. Smiling up and down to toggle the notification drawer is very inconsistent and buggy. I have the finger print quick action app installed. I had a single tap set up to lock the screen. I had my finger print reader un/locking the phone and toggling the notification drawer. While the notification drawer has always been a little buggy, it was VERY functional and very acceptable. Something has changed on the reader so it is having a harder time differentiating between the different movements. Now it usually registers a swipe as a tap and the screen locks. I expected this to happen when I first downloaded the app on 8.0, but I was pleasantly surprised when everything worked through the sensor. Now I am very disappointed. The issue is NOT constant. It comes and goes. Idk why it does that. I'll be seeing if I can figure out why. I will NOT be activating the always on screen as a means to circumvent this issue. I don't want burn in. I've been concerned with that issue associated with always on before the pixel showed up.
jbarcus81 said:
I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153
Click to expand...
Click to collapse
I want to jump on board and file an issue too. What do I select the issue as?it's not a developer preview. Is it android system issue? Framework?
fearfighters said:
I have this exactly
Click to expand...
Click to collapse
-deleted
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same here
Hi all, I have the LE2127 T-Mobile version of the OP9 Pro, and recently I have been having a strange issue with it. I am using the stock firmware, locked bootloader, nothing significant changed on it, running OxygenOS 12 (LE2127_11_C.19).
Sometimes, when I wake the phone from sleep, one of two things will happen:
1. The fingerprint sensor will not light up properly, and will instead remain the same brightness as the rest of the screen and appear as a dull white circle.
2. The entire display will get set to maximum brightness, and remain that way until I reboot the phone.
Nothing really screams at me in logcat, and removing and re-enrolling the fingerprint doesn't seem to work either. I also have factory reset the phone, to no avail. The bug happens intermittently with no real way to reliably reproduce that I've found. The only way to get the screen back to normal and to make the fingerprint sensor work again is to reboot.
Any ideas?
My last time updating to the current A12 on TMO LE2127, I couldn't get the fingerprint sensor to work once I set it up in settings. I went back to 11.2.9.9. Fully rooted.
I'm too.
BCXB said:
Hi all, I have the LE2127 T-Mobile version of the OP9 Pro, and recently I have been having a strange issue with it. I am using the stock firmware, locked bootloader, nothing significant changed on it, running OxygenOS 12 (LE2127_11_C.19).
Sometimes, when I wake the phone from sleep, one of two things will happen:
1. The fingerprint sensor will not light up properly, and will instead remain the same brightness as the rest of the screen and appear as a dull white circle.
2. The entire display will get set to maximum brightness, and remain that way until I reboot the phone.
Nothing really screams at me in logcat, and removing and re-enrolling the fingerprint doesn't seem to work either. I also have factory reset the phone, to no avail. The bug happens intermittently with no real way to reliably reproduce that I've found. The only way to get the screen back to normal and to make the fingerprint sensor work again is to reboot.
Any ideas?
Click to expand...
Click to collapse
I'm too
No9p ✨ said:
I'm too.
I'm too
Click to expand...
Click to collapse
That's A12 for you, I suggest going back to 11.2.9.9 A11 and staying there for awhile. I hated A12. Latest is not always the greatest!
I've also been dealing with this issue. Talked to support and they said just to restart the phone when it happens. They are working on a fix