So back to the Galaxy Alpha-known problem after updating to 5.0.2 (may occur earlier):
Symptoms sometimes hang before rebooting which also hangs. (This much is lost rank)
Frequency: can be manifested periodically from once a week to once a day.
Workaround: turn off unlocking fingerprint
Now proven reasons, to be exact, that does not help, and checked up on my machine:
Problem married board - I replaced the basic service fee to the new - the symptoms were.
Problem Fingerprint Module - I replaced the fingerprint service - Problem remained.
Problem to be updated. - I have frequently different update 5.0.2 with a full reset and wipe. - Problem remained.
Problem in registering more than one print (2-3 imprint) - now is a new scanner and registered one print - hang 2 per day 15% charge for 16 hours (at least at the same I use to 18 hours 40% ostaettsa) saved wireless charging  in auto output and not in this case.
Interesting facts about problemme:
Entering knox via fingerprint (one member) does not freeze. Perhaps because periodically rather than continuously sitting in knox, and because of this it does not manifest itself. But the fact is that when you use to unlock the screen print - hangs apparatus using to enter knox not Wisnu. Perhaps you need razyasnit that podvisanie is not in the moment of release, while using all sorts of other applications, for example calls the camera, etc.
4.4.4 The second point on this crash was seen once every 3 months and on 5.0.2 I unlock when activated by fingerprint hangs on average once every 2 days.
Deadlock: Materinka scanner replaced - that is in fact a new phone .... - means no hardware Problem. Software updated not once - it means not software.
Conclusion: The mean initial miscalculation, engineering or something - but then why there are those who use the scanner to unlock 5.0.2 and it all ok ???? !!!
Sorry for my translation.
Hi all,
I just bought an LG V10 yesterday, and the fingerprint scanner was working absolutely fine, but after a restart it just stopped working. Whenever I went to the fingerprint scanner settings it would say that "there is a problem on the fingerprint scanner" and instruct me to restart, but no number of restarts helped.
I've tried googling it, doing a factory & settings reset and even an alcohol swab, it seems nothing worked. After upgrading to Marshmallow, still nothing.
I'm using the Verizon version incase that's relevant.
You got a bad phone. Happens. Exchange it at Verizon, being a day old it won't be an issue.
Hi,
I have problem with fingerprint reader on my elephone p9000. I am using latest softer version and i have this problem from the begining.
So when i try to add new fingerprint it recognize my finger every fifth time, and after i set my fingerprint and lock phone it recognize and unlock phone first few time, and after that i seems like he forget fingerprint and i cannot use it.
Is this system or hardware problem?
After update i factory reset my phone but this does not help.
I find youtube video with the same problem
If you have any sugestion please.
I have the same problem too. I think you need to press the finger well for getting a good result.
I hope that this problem have a solution.
Sent from my P9000 using Tapatalk
I had loads of problems with the fingerprint sensor.. I was scanning itself (no finger on the sensor, vibrates and returns "too many attempts), working only when the screen is on, not working at all, working 1/10 times I tried, etc...
My problems were all software related (some were registering technique related). It's really not possible that two phones that you have ordered had the same problem.
I have managed to fix mine by combining Resurrection Remix and DarkSense Kernel 1.2.0, now it works 100% of the time. (1.1.0 rendered the fingerprint sensor useless). XPosed and ROM Toolbox seemed to break the fingerprint sensor as well.
I know it might sound silly, but try a different fingerprint registering technique. What I do is I lightly touch the sensor with the centre of my fingertip for the first time, lift the finger up, rotate it by ~5 degrees and lightly touch it again. Do that until most of the finger tip is registered. I'm only saying this because I've seen people touching and "smearing" the fingerprint sensor, expecting it to work. Imagine it's a camera, give it pictures of your fingerprint.
I don't know if this is useful, but after a few months of trial-and-error I've managed to find what was wrong with mine.
I just installed the AEROM V5 and now it works about 90% of the time, which is more than my Nexus 5X did.
Hi,
I've read this thread and disabled battery optimisation for "com.samsung.android.biometrics.app.setting"* on my Note 10+ and Tab S6 (Wifi).
On both devices the fingerprint scanner is faster :good:
... and it seems to fix recurrent unlock problems with my Tab S6 too
* on some devices it's named "com.samsung.android.biometric"
Important:
it's not known yet if this might have any negative side effects (as battery drain or burning out the fingerprint sensor).
I also did it. But it doesn't make the fingerprint scanner faultless...
Hi, am I the only one having a problem with the fingerprint reader after upgrading to Android 10? ?
I have probably tried everything. Factory reset and clear cache partiotion do not help. The problem returns randomly. The reader stops working, and when I try to get to the settings I have the message: "Finger print sensor calibration needed " or "finger print sensor doesn't respond, try to reboot your device . If the problem persists, contact support "
I checked everywhere and there is no such thing as calibrating the fingerprint reader. Technical support also couldn't help me with the problem, they only recommended to send the tablet for service. ?
The problem has never appeared before the update so I bet that the problem is new software.
Any advice what else I could try?
The reader, when it starts to work, works much better than before the update, unfortunately more and more often it does not work at all.
The strangest thing is that sometimes it starts working after a regular restart. I have no idea what to think about it.
Something similar... It sometimes works like a charm. It sometimes stops working, but no message and no way to use it in order to activate the tab. In that case I have to use an alternative method to. I suppose a fix could be released after this update to Android 10...
solved
Hi there,
I've solved this issue. I have tab s6 4-5 month and I couldn't even register the fingerprint. today I tried again and I found out that you have to touch the scanner very gently, do not press firmly. so I could register 3 fingerprints and it is working. even with unlocking if you press harder it won't work you have to touch slightly and it is working. still it is not reliable as other scanners but it works. i'm providing the video, you can see when I touch gently it is working, but If I press harder it won't register.
h t t p s://drive.google.com/file/d/1BegH3jbh3QxAuwLqSY8fdiHFbZ0MU2Zc/view?usp=sharing
Wazzup.
Over at the Pixel 6 Pro fair, we have quite the number of people having problems with random reboots. We are trying to narrow it in - Android12? Pixel 6? Software? Hardware?
So - anyone here with the same set of problems? Or does the Pixel 6 not have that kind of issue?
For reference: https://forum.xda-developers.com/t/random-reboots.4353231/
I have gotten several random reboots as well. 256gb seafoam pixel 6. In particular, I was using "Frep" automation app (unrooted, used pc to start server) to do repetitive image searches in a game. Also the phone was sitting on a wireless charger while doing this. I noticed my phone felt pretty warm, wonder if it could be overheating?
Could be a naughty 3rd party app. Have you tried safe mode?
I posted this here:
P6 Bluetooth Problems
My p6 will see most some of my Bluetooth devices (laptop, tablet, TV, earbuds) . It pairs with the earbuds, but everything else it will try and pair, usually does not. If and when hen it does pair, that pairing is dropped dropped within 5 secs...
forum.xda-developers.com
My random reboots (or crashes that forced me to reboot) almost entirely stem from the wifi+bluetooth implementation. I found a sure-fire way to crash it during setup. Without word vomiting here, connecting the P6 with and to other devices has proved more difficult than any previous Pixel (for me).
mruno said:
Could be a naughty 3rd party app. Have you tried safe mode?
Click to expand...
Click to collapse
Not yet. It's also hard to "force" it (the reboots, I am not able to replicate it manually). Yesterday it just randomly happened whilst the phone laid idle next to me, thrice at the morning, about one time through late afternoon, then one time evening. I just notice the screen lighting up, then the Google logo comes, meaning the phone restarted.
I'm also pretty sure that Bluetooth/Wifi settings differed when the reboots happened, ergo at some times bluetooth was on, then when it rebooted, bluetooth was off. At no time when the reboots happened had I a bluetooth device connected. WiFi was online though, all the time.
What all the reboots have in commong though (at least the ones where I am concerned), is that the phone is just laying next to me, or somewhere, being in idle - doing as far as I know, nothing. It never happened when I used the phone or put it under load, so my P6 never "crapped" out under me. That's why I am not that concerned about this as of now, but it's certainly a nuisance to unlock the phone every time with my darn pin.
(Concerning 3rd party app) - I'd say that's unlikely. I copied my files over from my Pixel 4 XL and have not yet added one singular other app to my P6 Pro, so it should have gone naughty before my transfer over.
Hi! I experienced a big crash on the pixel 6. When I was configuring telegram, the app crashed and then the screen got black. After a minute it rebooted to the Google logo with a loading bar underneath. It was blocked in that state, but I could reboot it with volume up + power button.
I was pretty scared as the usual button down + power button didn't do anything lol
12 (SD1A.210817.036) on my pixel 6, occurred randomly when opening camera app. Happend 7-10 times.
dirtyissa62 said:
12 (SD1A.210817.036) on my pixel 6, occurred randomly when opening camera app. Happend 7-10 times.
Click to expand...
Click to collapse
Odd. I never had a problem whilst using the phone, my phone only rebooted when laying idle (even though today I had no reboots at all, alas I didn't use the phone much, maybe 2h SoT without any heavy lifting).
Something in android 12 is bugging around, maybe we have to open support tickets.
dirtyissa62 said:
Something in android 12 is bugging around, maybe we have to open support tickets.
Click to expand...
Click to collapse
I just talked for a while with a Google rep and he said that they are not aware of any reboot problems, no people over at Google Forums have reported such a thing. "We do not monitor Reddit or XDA" - so he said he opened a support ticket to the responsible team and they would look into it, he also asked that I / we report/feedback this under -> Settings -> Tips & Support -> Feedback.
We also talked about a lens flare problem, that at least the Pixel 6 Pro has. If you shot some photos where the sun is directly shining into the camera, you might want to re-check them. Most of mine have either some sort of big circular green dot in them, or a big beam of light like in a phone with a very bad HDR processing. It seems to be some sort of software glitch, he also reported that.
So hopefully those things can get fixed.
This was the follow-up email:
Thank you for contacting Google support.
This email is regarding the chat conversation we had earlier today, I'm sorry we weren't able to complete it. Hence I wanted to follow up via email to ensure all your queries have been answered.
Please re-launch the camera app and check if the issue is fixed.
Please be assured our developer team is working on this to fix it as soon as possible. We would really appreciate your kind understanding as we work on this to fix it for you.
If there is anything apart from this that needs clarification, please feel free to reply back to this email. I'll be more than happy to assist you.
Thanks!
Nova
The Google Support Team
I'm having similar restarts while phone is sitting on a table doing nothing. Tried a factory reset and was fine until overnight on charge and it happened again.
Also have had a few times where wifi has stopped working for some reason. Not sure if related.
Not had any reboots but quiet a few app crashes in especially FB will be scrolling away and bang just closes also Amazon app ,
Well that was interesting.. When it rebooted that time, it gave me an error screen saying it could not load and may be corrupt. I had two options, try again and factory reset. Try again got me back running, but I'm wondering do I got as defective device now.. or if it's software related.
So after a lot of messing around, I think I have narrowed down what may be causing my reboots. It only seems to happen when I am using "Frep" to play macros on a game while charging my phone.. the phone gets pretty hot, and reboots when I tap the screen or try to swipe home or recent apps. Maybe its overheating, or maybe its "Frep" playing naughty.. but Frep did work perfectly fine on my old $200 used Nord N10 5g. Will update if it reboots while not doing this.
no reboots or crashes so far, not doing any gaming - but using phone for email, surfing, whatsapp etc and also a work profile for MS outlook and teams.
I have/had similar issues with my Pixel 6 (128GB - europe unlocked).
I was transferring old data via cable from my old (Xiaomi Mi A1) to the Pixel 6. This resulted in sluggish performance, crashes every 15 minutes. The crashes would randomly occur and behave mostly like this:
Try to unlock phone with fingerprint sensor
Fingerprint sensor lights up, nothing happens, no haptic response
Swiping up to the PIN entry. Enter PIN and hit enter. Nothing happens. Now freeze.
Screen turns black and it takes phone to reboot on average ~7minutes
Factory Reset; Installed apps manually (standard messaging apps, no games etc), better performance, problem persists
Factory reset; boot into safemode. It now took way longer to provoke the issue. But it still happened.
After this I contacted the customer service and they will provide me with a replacement. But now after a night of idle, the phone was working for 3-4 hours without any issue at all with most of my apps installed. It just now went into a random reboot (could only notice because it asked for PIN because of the reboot). But not the 8 minute blank black screen type of reboot.
I am really unsure what is the issue at hand here. But have to say that experience is less than ideal.
Mine just happened last night, not charging or running anything 3rd party apps (all from App Store). I tried to use the camera after eating dinner and noticed that double clicking power button doesn't open the camera anymore. After unlocking the phone it appears that the phone has restarted.
Is anyone running Private DNS on their system like Adguard DNS or NextDNS? I did some searching and people reported some private DNS were causing Android to crash. It was suppose to be fixed in previous Android versions but it could be back again.
I haven't noticed any random reboots (and the lock screen will require a pin to be entered after reboot and says this on the screen, so you should know the phone rebooted). I've had the P6 since the official release date. In fact, I haven't restarted the phone in days.
I run a wide variety of apps. Some from the Play store and some sideloaded. I think that any reboot issues are probably app related. Remember that A12 is very new and the are surely still some compatibility issues that app developers haven't found/fixed yet.