FYI for WidgetLocker lovers..........the latest update has fixed the issues where the fingerprint scanner did not work on the WidgetLocker screen. The fingerprint scanner now unlocks and takes you right to your home screen. If you use the slider bar in WidgetLocker, it no longer takes you to the normal lock screen, but brings up the code unlock screen instead as the regular lock screen does. I have checked this multiple times on my phone on 4.1.83, GladiAtrix, and Cool Blue.
WidgetLocker Market Link
You do have to swipe the scanner a wee bit slower it appears, almost like Atrix was prior to 4.1.57 update, but other than that it works fine.
+1 Yea noticed that been using it again with no problems as well ^_^
Sent from my MB860 using XDA App
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
i just tried widgetlocker for the first time yesterday. It was nice and definitely modifiable (word?) but it slowed down my phone ever so slightly.
badnokia said:
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
Click to expand...
Click to collapse
It happens to me also.
Sent from my Chuck Norris powered PRO RED DXblurred Atrix
badnokia said:
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
Click to expand...
Click to collapse
When did you update? There was an update yesterday or the day before which did not address this particular issue. The update today wasn't there earlier because I check several times a day for Market updates out of boredom. It appeared this evening in the Market for me. Working great for me now.
Also, how fast are you swiping on the reader? You can't swipe as fast as when not using WidgetLocker.
blunted09 said:
i just tried widgetlocker for the first time yesterday. It was nice and definitely modifiable (word?) but it slowed down my phone ever so slightly.
Click to expand...
Click to collapse
When you say slowed down your phone..............in what way? I know it slows down unlocking slightly, but I notice no other slow downs once the phone is unlocked.
CaelanT said:
When did you update? There was an update yesterday or the day before which did not address this particular issue. The update today wasn't there earlier because I check several times a day for Market updates out of boredom. It appeared this evening in the Market for me. Working great for me now.
Also, how fast are you swiping on the reader? You can't swipe as fast as when not using WidgetLocker.
Click to expand...
Click to collapse
I updated this morning. I just checked the market again just now & no additional update was available; I'll check back again later. Re: swipe speed, I'd say I didn't change my speed at all. Again, that seemed to not be a problem for ~1/2 a day.
The only known issue right now is that Exchange can break things. I'm working on a method for rooted Exchange fingerprint scanning users to bypass this (the trick actually allows for some other things too so it's not as niche of a group as it sounds), but it requires manual XML changes right now and could mess up your system. When it's wrapped into an apk and ready for user testing I'll post somewhere in the Atrix section to let you guys know.
If you're not using Exchange (or a similar device admin that "Requires password") and having issues with it not working in cases that the Motorola lock screen would, then Settings > Report Bug and provide as much details as you can about when it's not working.
mine doesn't work at all anymore now. before, it would work about 50% of the time, now no response at all. i tried rebooting, clearing my lock screen settings and re-enabling fingerprinting, etc. no dice.
Sent from my MB860 using XDA App
dLo GSR said:
mine doesn't work at all anymore now. before, it would work about 50% of the time, now no response at all. i tried rebooting, clearing my lock screen settings and re-enabling fingerprinting, etc. no dice.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Same here. Mine was working, now it's completely unresponsive. Back to the stock lock screen.
I am one of the elusive Exchange users he mentioned though...
is anyone else having problems? i can't get it to work AT ALL. i've uninstalled, reinstalled, rebooted, gone through every setting in the settings menu... what gives?
dLo GSR said:
is anyone else having problems? i can't get it to work AT ALL. i've uninstalled, reinstalled, rebooted, gone through every setting in the settings menu... what gives?
Click to expand...
Click to collapse
Still not working consistently enough for me to continue using...bummer... I've been back to stock lock for awhile now & waiting for next update with fingers crossed.
ok i think i've narrowed it down.
if you set a FP profile, and use a PIN, then it will work. BUT if you are using the pattern unlock and the FP (which you can set by setting as pattern first, then FP with existing profile), it will not work.
dLo GSR said:
ok i think i've narrowed it down.
if you set a FP profile, and use a PIN, then it will work. BUT if you are using the pattern unlock and the FP (which you can set by setting as pattern first, then FP with existing profile), it will not work.
Click to expand...
Click to collapse
I use FP with pin, so maybe you have hit on something there, as I have no issues with it.
yup, confirmed it's true with the dev, and also that it's Motorola's fault.
"I did notice this in testing, however Motorola does not support the Fingerprint scanner with Pattern so I decided not to either. What you found is unintentional and may have issues on it's own (I haven't tried with the latest firmware, but I had played with that setup on the original firmware and found it unreliable. Setting a delay with the Fingerprint scanner (via sqlite) also caused weirdness).
With regard to WidgetLocker, there's some code in there to handle Motorola's pattern and some other code to handle Motorola's fingerprint scanner. I did try to get both to work, but in limited testing was unable to do so and since it's not officially supported by Motorola I decided not to pursue further. (I actually also thought they fixed the loophole you found in the later firmware so the only way of doing it was sqlite, but apparently I was wrong)"
Related
My Atrix's fingerprint sensor stopped working all of a sudden. Anybody experienced this?
Happend to me and restarting my phone seemed to be the trick
Sent from my MB860 using XDA Premium App
I have read about ppl having problems on the 83 FW thread. Are you on 57 or 83?
Same problem with mine today. Version 1.83
I've been on 1.8.3 for four days so far, and the fingerprint sensor seems to be working normally.
Perhaps you can go back and redo your fingerprint calibrations.
I'm on 4.1.57. Never rooted. I tried to re calibrate my finger prints and it the phone would not even sense it. bummer.
Same happens to me every so often. And restarting phone did fix it.
Sent from my MB860 using XDA App
Just happened to me for the first time ever. Just updated to 83 so i guess thats why.
I had the same thing happen to me today. Running .83. Rebooted the phone and it went back to normal
1.26 1.57 1.83 have the same problem.
Just config it again.
You guys tweaking your memory management?
Sent from my Motorola Olympus
If you happen to have your finger on the sensor when the phone is booting, the sensor gets confused and doesn't work.
Reboot and keep your finger off the sensor until the unlock screen and you should be fine.
fingerprint scanner going out for me once a day, reboot fixes it. for now i just shut it off. any permanent fixes or is it because of the latest 1.8 update?
Mine did the same thing after updating it to .83 and a reboot fixed it. One thing I noted was this happened whn the battery is below 20%. I initially thot it would come back after I a recharge, apparently I was wrong and had to restart. It is so annoying. Also, I am experiencing more battery drain after updating.
Sent from my MB860 using XDA App
I've had it refuse to see my finger from time to time, fewer times after each OTA update. I'm not happy about the freezes but this is the only phone with a finger reader, when it fails...pretend it is any other phone, use the passcode. I expect Moto to get this solved sooner rather than later because this is supposed to be a big feature for corporate sales and the attack on Blackberry's native security functions.
Whether it is a memory conflict (let's face it, Android apps are often ill-behaved and there's no one really doing qc testing on them) or an Atrix flaw...no choice but to wait either way.
Has anyone found a permanent fix for this? The Atrix is the first smartphone that my wife has owned and shes losing confidence in it. This is just one more thing that is on the list of problems shes had. My Atrix works fine, but her fingerprint reader stops reading once or twice per day and she has to reboot each time to get it working again.
I've had the same problem since 1.8.3--somebody suggested in another thread that it might be related to Titanium backup keeping settings from pre-update and trying to apply them?
I have to be honest that the fix suggestions were kind of over my head and I've just gone into settings and changed to a pattern instead of the fingerprint reader to avoid it.
My wifes Atrix keeps losing the fingerprint reader still. Maybe 2 times a day. Hers is not rooted. I took a closer look yesterday and looked at her running apps. She had a lot that were running and taking up a lot of memory. Could this be the problem? If she doest exit apps and just hits the home button will this cause the Atrix to use up its memory and lose the fingerprint function?
JohnnyDanger said:
My wifes Atrix keeps losing the fingerprint reader still. Maybe 2 times a day. Hers is not rooted. I took a closer look yesterday and looked at her running apps. She had a lot that were running and taking up a lot of memory. Could this be the problem? If she doest exit apps and just hits the home button will this cause the Atrix to use up its memory and lose the fingerprint function?
Click to expand...
Click to collapse
I have no idea if that could be related/the issue, but I guess it's worth a try, maybe install an app to auto-kill other apps. Something like advanced task killer, I used to use it (and it works well, no particular reason for uninstalling it) but now I just use juice defender and my battery life has increased a significant amount (I keep it on the default setting - using free version)
Every 2-3 days it happens and I have to reboot. When it fails, it doesn't scan your finger at all..
So I used to run /system/bin/sensorcalibutil_yamaha as root to get a more precise horizontal calibration (the option in setting seemed to do nothing). However after upgrading to GB it seems like this executable has been removed and the option is settings still didn't seem to solve my issue. Is there another alternative on a stock GB rom? Maybe they renamed the app?
Download GPS Status from the Market. When you open the app, go to settings. There is an option to calibrate compass. Worked great from mine. Mine is spot on now.
Is there really no longer a built-in calibration app in system settings? Mine worked fine although the phone had to be upside-down like many other people's while using it.
DroidApprentice said:
Is there really no longer a built-in calibration app in system settings? Mine worked fine although the phone had to be upside-down like many other people's while using it.
Click to expand...
Click to collapse
No the built-in Settings -> Display -> Horizontal Calibration still exists. My statement was that it never really worked for me and still doesn't. The only reliable way I had to calibrate was by running the aforementioned yamaha application while running as root.
I've tried the upside down trick and I still get jitters. For instance Words with Friends randomly shakes the tiles, even if my phone is sitting on a table. It's not so bad w/ GB as it was when I got the phone originally but I was able to solve it under Froyo with the yamaha tool and don't seem to have that option in GB :-(
machx0r said:
So I used to run /system/bin/sensorcalibutil_yamaha as root to get a more precise horizontal calibration (the option in setting seemed to do nothing). However after upgrading to GB it seems like this executable has been removed and the option is settings still didn't seem to solve my issue. Is there another alternative on a stock GB rom? Maybe they renamed the app?
Click to expand...
Click to collapse
machx0r said:
No the built-in Settings -> Display -> Horizontal Calibration still exists. My statement was that it never really worked for me and still doesn't. The only reliable way I had to calibrate was by running the aforementioned yamaha application while running as root.
I've tried the upside down trick and I still get jitters. For instance Words with Friends randomly shakes the tiles, even if my phone is sitting on a table. It's not so bad w/ GB as it was when I got the phone originally but I was able to solve it under Froyo with the yamaha tool and don't seem to have that option in GB :-(
Click to expand...
Click to collapse
offtohavasu said:
Download GPS Status from the Market. When you open the app, go to settings. There is an option to calibrate compass. Worked great from mine. Mine is spot on now.
Click to expand...
Click to collapse
Yeah, I used to use /system/bin/sensorcalibutil_yamaha as well, and it worked very well for increasing the speed/sensitivity of rotation, but seems to be gone in CM7 (Which is built upon AOSP GB 2.3.5). I brought it up in another topic & one of the devs (I forget who) said that there is no known fix right now.
I'll try offtohavasu's tip, but I'm not gonna hold my breath! I've used it before with no success, but I haven't tried it with CM7 yet. Cross your fingers that this is the fix we need!
EDIT: no luck. I tried both the "Compass calibration" (which I didn't expect would do anything for rotation speed/sensitivity, but I tried anyway) and "Calibrate Pitch and Roll," and neither one had any impact.
not working for me either.
My rotation lag is terrible as well, and the upside down / display calibration option has not fixed it. I thought it was just me as this popped up on the last two GB leaks for me. I would love to be able to rotate my phone properly again.
Hate to tease but if I had a computer I could probably whip up a possible fix if I had my computer:/
Sent from my Samsung Legen-wait for it-dary! 4g
This certainly seems to be somewhat hardware related (as in, variations in production quality). I had issues back on Eclair or one of the first froyo leaks, including the bacwards compass that initially lead me to the upside-down calibration discovery, but my rotation speed has been fine since sometime around the release of EC05.
But how long of a delay do we each define as lag? When I had issues, I actually had to shake the phone to get the rotation to register... now, it still hesitates for about a second, but I see that at as a check to make sure it was an actual rotation instead of an incidental, momentary tilt of the phone - I would be annoyed if my screen rotated every time the motion sensor detected the slightest movement
Edit: a full second is an exaggeration, I'm seeing more like half a second of hesitation... Just trying to remain accurate
2nd edit - damn swypos, lol
Sent from my SPH-D700 using XDA App
I'm on T-Mobile but I just got home and phoned up my co-worker who has the Verizon version. Says he noticed a slight improvement in overall touchscreen responsiveness. Biggest problem that he said was fixed was ghost touches (touching one portion of the screen caused a menu to pop up somewhere else for example) being completely gone. Idk, it's really starting to feel like a lot of these bugs should have gotten squashed in the product testing phase. Wonder if this is the same update as the mandatory one T-Mobile got way back. I wouldn't think so since the T-Mobile update did not fix touch screen issues for anyone.
Anybody notice the auto brightness isn't as dim anymore which is a good thing IMO.
slick_shoes said:
Anybody notice the auto brightness isn't as dim anymore which is a good thing IMO.
Click to expand...
Click to collapse
well that sucks because the lowest wasn't low enough for me.
Lock-N-Load said:
2. I do NOT see a difference in QC 2.0. I was about 8.94-9.0 volts draw on QC 2.0 before, and now I am at same. I call it as no change in QC 2.0 speed - so still not "true" QC 2.0.
Click to expand...
Click to collapse
Forgive me if I've misunderstood QC 2.0. But my understanding is it can charge at 9V or 12V. So just because it's still at 9V doesn't definitely mean that the phone isn't receiving more power, the amps could have also increased.
To provide 15W, for instance, you'd need 3A at 5V, 1.67A at 9V, and 1.33A at 12V.
It's possible to still get 9V from the charger, but draw more amps, for faster charging. Using something like Battery Monitor Widget, to monitor the current provided to the battery, would be a useful tool.
bobloadmire said:
well that sucks because the lowest wasn't low enough for me.
Click to expand...
Click to collapse
Try the paid version of Lux ... Can get the screen REAL dim!
G4'ed it!
After reading all of these posts, I'm really hoping for a similar update on T-Mobile coming soon. I'm glad this isn't just a placebo and an actual solution to a software problem that doesn't require getting my phone serviced.
SIdeloading apps problem???
UPDATE: Nevermind - issue not related to Verizon update... Had Twilight app kick on after sunset and that overlay app (reducing blue light) is what caused the touch issue. (Credit: brainwash1)
Enabled installing from "Unknown Sources" and installed an app yesterday no problem
I just did the Verizon system update and reboot, now on sideloading install I get the permissions list with CANCEL & INSTALL buttons at the bottom. Looks normal, but the INSTALL button doesn't respond to any tapping. Tried landscape mode also, just to move where the button was located on the screen, but no dice. CANCEL button works fine.
[Also, if there are many permissions, so I need to scroll, the INSTALL button starts as a NEXT button, then changes to INSTALL when done scrolling to bottom. Doesn't matter, neither NEXT not INSTALL buttons function]
Not sure what else would cause this. It seems like the Verizon system update broke something. Anyone else having new problem sideloading after the update???
Whats your carrier? I think the other guy is verizon. So am i, and i put no thanks
z500zag said:
Enabled installing from "Unknown Sources" and installed an app yesterday no problem
I just did the Verizon system update and reboot, now on sideloading install I get the permissions list with CANCEL & INSTALL buttons at the bottom. Looks normal, but the INSTALL button doesn't respond to any tapping. Tried landscape mode also, just to move where the button was located on the screen, but no dice. CANCEL button works fine.
[Also, if there are many permissions, so I need to scroll, the INSTALL button starts as a NEXT button, then changes to INSTALL when done scrolling to bottom. Doesn't matter, neither NEXT not INSTALL buttons function]
Not sure what else would cause this. It seems like the Verizon system update broke something. Anyone else having new problem sideloading after the update???
Click to expand...
Click to collapse
Do you have an app running that overlays something on the screen? I've had this in the past with a couple of different apps. Try turning off anything that's running.
Sent from my VS986 using Tapatalk
Ding ding ding!
brainwash1 said:
Do you have an app running that overlays something on the screen? I've had this in the past with a couple of different apps. Try turning off anything that's running.
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Twilight app kicked on after sunset, which is why I started having the problem. Paused it, and no more issue. Thanks!
Misterxtc said:
If you or anyone else don't want to be bothered by the OTA in fear of patching a exploit for root block LGDMSClient.apk with the debloater tool by @gatesjunior. If anyone downloaded it and do not want to install it just clear the cache from recovery mode. That should remove it from the phone.
EDIT: To enter recovery mode power down the phone and then hold the volume down and power buttons when powering back on.
Click to expand...
Click to collapse
Wiping the cache did nothing. It keeps popping up saying it is already downloaded and ready to install.
psycho_asylum said:
Wiping the cache did nothing. It keeps popping up saying it is already downloaded and ready to install.
Click to expand...
Click to collapse
OK, then the update isn't stored in the cache partition as other phones. It's a bit drastic but a factory data reset will do it. I ended up taking the update and then froze the updater. It did improve the touch response so I have no need for further updates. It updates the kernel because that is where the necessary changes are.
Misterxtc said:
OK, then the update isn't stored in the cache partition as other phones. It's a bit drastic but a factory data reset will do it. I ended up taking the update and then froze the updater. It did improve the touch response so I have no need for further updates. It updates the kernel because that is where the necessary changes are.
Click to expand...
Click to collapse
my touch response "seems" improved but I still get ghost touches..
I love pretty much every aspect of the phone, but the issues I have with the touchscreen are maddening at times, if I didn't see widespread reports of issues I would have Verizon replace the phone, but I am not sure it's worth the hassle..
lazarus2297 said:
my touch response "seems" improved but I still get ghost touches..
I love pretty much every aspect of the phone, but the issues I have with the touchscreen are maddening at times, if I didn't see widespread reports of issues I would have Verizon replace the phone, but I am not sure it's worth the hassle..
Click to expand...
Click to collapse
It might be worth replacing. I first had a black one that had the problem pretty bad. I returned the phone and went back to my S6 for a while but ended up picking up a blue one from Best Buy and this one works great. The touch wasn't that sensitive before the update but now it works really good. My battery is really good on the blue model too. Keep in mind I paid full retail for mine so when I returned the first one there was no restocking fee. I go to BestBuy just for that reason.
I was having some touch issues just as many are experiencing. Just today I installed the Google keyboard from the play store. I enabled the new keyboard and stopped using the LG keyboard. I have been using it this way for about an hour and I am much happier. I am hopeful this will take care of my issue. This is on a Verizon G4.
I took the update yesterday and threw my Verizon G4 on a Qi Wireless Charger last night and the bug where it has crashed in the AM is still there. Not sure about that.
Basically every time I wake up on a night of Qi Charging, the phone is crashed and freaks out.
Update:
My phone is now getting hot and doing the screen brightness bounce like it did out of the box. Going from 100 to 90 to 80 to 90 to 80 to 100 to 90.
bnick007 said:
I was having some touch issues just as many are experiencing. Just today I installed the Google keyboard from the play store. I enabled the new keyboard and stopped using the LG keyboard. I have been using it this way for about an hour and I am much happier. I am hopeful this will take care of my issue. This is on a Verizon G4.
Click to expand...
Click to collapse
I switched from the LG keyboard to the google keyboard day one so that was never a source of my issues.. Just today.. twice post update I have had ghost touches launch the app switcher icon while texting and caused me to switch apps on accident.. Doh.. It's frustrating to say the least.
Never had a problem with wireless charging besides it's slow.
No screen brightness fluctuations.
No ghosting on screen.
Sounds like there's an awful big batch of bad phones.
06stang said:
Never had a problem with wireless charging besides it's slow.
No screen brightness fluctuations.
No ghosting on screen.
Sounds like there's an awful big batch of bad phones.
Click to expand...
Click to collapse
There are definitely bad ones. I returned mine again a few hours ago because my outdoor pictures would come out either dark or overexposed real bad. I tried manual mode and auto and no matter what I did they were awful. So I'm back to my S6 again, it was fun while it lasted.
I am still new to the fingerprint reader so my old habit of swiping, which takes you to an pin pad. It says to Use fingerprint or enter pin, but about half the time it doesn't take the fingerprint. I'll either have to let it time out and get it on the main lockscreen or just enter the pin.
Actually the first day it was so bad that I didn't even think it was accepted on that pin screen. It wasnt until last night when I even saw it say "use fingerprint" but it works about half the time.
The fingerprint scanner works pretty reliably everywhere else so I don't think its a hardware issue. Just curious if others are having problems scanning on the pin screen.
Only time I have an issue is the first time Samsung Pay reads my print. 99% of the time, I have to put my finger on it again. Best way to solve your issue that I found is by unlocking your phone as follows:
Press and hold the home button with a finger that you have saved. When the phone unlocks, remove your finger. This way your finger is firmly on the reader. If it is still giving you issues, try making the fingerprint again in the settings.
I have big fat fingers lol. And I use my thumbs to unlock. In the fingerprint settings, I now have multiple fingers set to unlock the phone, that way, if I'm having maybe a problem hitting it right with one finger, I can get it with the other. I've got both hands covered. Multiple fingerprints to me is key. Also, when I was first learning to scan my prints, it took me a little while to get it right. For my thumbs, I'm pretty methodical... I start at the bottom left, lift up bottom middle, lift up, top left, lift up, etc... Basically let it scan a small quadrant of my thumb at a time. Seems to work really well. I have very few bad readings. Usually happens when my fingers have something on them, or the button has something on it, or my finger is laying too far sideways...
Sent from my SM-G935V using Tapatalk
No its not about reading my finger. I have multiple fingers setup (4).
I dont have an issue unlocking via fingerprint from the main lockscreen. The problem is when I try to swipe and it asks for a pin. Its this screen where it works half of the time. Its not that it isnt "matching" because when it works it will throw an error like "no match". But half the time it doesn't even recognize me trying to scan a finger.
I've been testing it more and more and it is a bug.
I understand what you're saying now. I haven't run into this problem yet. I do have some issues here and there, but it's not like an all the time situation.
Sent from my SM-G935V using Tapatalk
mwshows said:
I understand what you're saying now. I haven't run into this problem yet. I do have some issues here and there, but it's not like an all the time situation.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I just moved to the Note 5 and grabbed Marshmallow. I can say that the issue was specific to the S7E. Even on the same screen, it is responsive regardless of whether it was successful or failed, at least it prompts and responds.
On the PIN screen, it just would recognize a fingerprint input half the time.
Update
My Note 5 did it a few times today too. Aggrevating.
When you have a bunch of notifications, you select one to open, the pin screen comes up, and occasionally doesnt take fingerprints. Its like it's looking for ONLY the pin. Weird.
Im having this exact issue as well. So annoying to be not able to unlock via fingerprint at the PIN screen!!!!
Having exact same issue, and it pretty much makes the
fingerprint unlock method useless. I'm using a Galaxy S7 Edge, in Australia with an Australian carrier, so it's a safe bet the issue isn't isolated to Verizon (perhaps move the thread in the main s7e thread to get more attention?)
*The fingerprint works
100% time on the main lock screen, but whenever you tap a notification or swipe
to unlock, and you are presented with the PIN/Fingerprint or
Password/Fingerprint screen, the fingerprint unlock method rarely works. You
either have to enter the pin/password, or go back to the main lock screen and
use your fingerprint there to unlock the phone.
Seeing as multiple people have reported the issue, safe to say its not an isolated issue. I'm surprised more people haven't complained
about it, as it really defeats the purpose of fingerprint unlocking.
*Is there a way to raise the issue with Samsung so they can address it in a future update? Or does anyone know of a temporary fix?
To solve the problem you can have your home and work address saved as a safe place and the phone will not lock at those locations.
For me this helps to not use the fingerprint scanner all of the time. I also never have a problem with it anyways.
Sent from my SM-G935V using XDA-Developers mobile app
Good suggestion, thanks for that : )
I'm hoping Samsung acknowledge the issue and fix the problem soon. TBH, I'm surprised more people haven't encountered and complained about the issue. I noticed it within a day of getting the phone. Perhaps people don't bother with fingerprint unlock? Either way, fingers crossed an update comes soon.
I traded out for a Note 5 and its MM update is doing the exact same thing. I switched to a pattern backup and I think its working much better.
I am going to try that new Good Lock that updates the UI. Running good and will report if its still broken or if it fixes the fingerprint reader.
Did some testing of my own. Issue is not present with goodlock. Did you find the same mate?
player911 said:
IWhen you have a bunch of notifications, you select one to open, the pin screen comes up, and occasionally doesnt take fingerprints. Its like it's looking for ONLY the pin. Weird.
Click to expand...
Click to collapse
Same identical problem here. It worked only one time, after that it doesn't worked anymore.
Good Lock is a modified (perhaps the next gen?) TouchWiz silently released by Samsung that is still very much in its alpha/beta stages.
Info and download link: http://9to5google.com/2016/04/04/samsung-good-lock-update-bug-fixes/
Ironic that the fingerprint bug plagues touchwiz, but doesn't seem to be present in this new good lock system UI.
invision1 said:
Good Lock is a modified (perhaps the next gen?) TouchWiz silently released by Samsung that is still very much in its alpha/beta stages.
Info and download link: http://9to5google.com/2016/04/04/samsung-good-lock-update-bug-fixes/
Ironic that the fingerprint bug plagues touchwiz, but doesn't seem to be present in this new good lock system UI.
Click to expand...
Click to collapse
I will wait for more stable version, in the meantime I continue to keep this annoying bug. I just don't understand why if it is a bug, most people doesn't have this problem.
Sended from my Samsung Galaxy S7 Edge Gold Platinum
That's a really good question. It's am extremely annoying bug that I keep running into multiple times on a daily basis.
If anyone knows how to officially report bugs to samsung please share. I'm not going to hold my breath though. Seeing as I am on a carrier firmware, the update could take quite a while before I see it on my phone. That's assuming samsung even fix the bug in the ubranded firmwares.
Grr
Apparently yestrday a dutch user got a new update on his phone. I have an unbranded phone, i will wait for it. I keep you guys posted.
invision1 said:
That's a really good question. It's am extremely annoying bug that I keep running into multiple times on a daily basis.
If anyone knows how to officially report bugs to samsung please share. I'm not going to hold my breath though. Seeing as I am on a carrier firmware, the update could take quite a while before I see it on my phone. That's assuming samsung even fix the bug in the ubranded firmwares.
Grr
Click to expand...
Click to collapse
Could it be an hardware issue? Has anyone installed last Samsung's update? Maybe it solve this issue too.
I doubt it's a hardware issue. the fingerprint reader works fine, it's only on the screen described above is when it works inconsistently. And it doesn't happen on the good lock interface. All of this clearly points to a software bug, not a hardware issue
I haven't received any need update yet but if you do please post your results!
invision1 said:
I doubt it's a hardware issue. the fingerprint reader works fine, it's only on the screen described above is when it works inconsistently. And it doesn't happen on the good lock interface. All of this clearly points to a software bug, not a hardware issue
I haven't received any need update yet but if you do please post your results!
Click to expand...
Click to collapse
I didn't tried Good Lock yet, but i wonder why some users have this issue and others have not. Anyway when i will receive the update i'll let you know
When I first got the phone yesterday, unlocking the phone was crazy fast with the facial recognition. This morning, I got the latest software update, and now, it's basically unusable. Has anyone else experienced this?
JDM9499 said:
When I first got the phone yesterday, unlocking the phone was crazy fast with the facial recognition. This morning, I got the latest software update, and now, it's basically unusable. Has anyone else experienced this?
Click to expand...
Click to collapse
The update was to improve the security. You may need to resetup. They made it more sensitive so it can't be unlocked with a pic as easily
bossg4 said:
The update was to improve the security. You may need to resetup. They made it more sensitive so it can't be unlocked with a pic as easily
Click to expand...
Click to collapse
After the update, it was a night and day difference. I tried registering my face again multiple times, and it worked maybe 3-10 times. It was terrible. I just reset my device though after I registering another facial input, and it's back to how it was - super fast. I'll continue to monitor if it reverts back to being unusable.
It's horrible... I can't even open my phone half the time...Just came to XDA to see if I was the only one having this issue
Same issue. The first day I got my phone I was actually bragging to everyone how amazing and fast the face unlock was. After the update it sucks, to the point where I just can't use it. I did register my face again multiple times as well.
kuulhus said:
Same issue. The first day I got my phone I was actually bragging to everyone how amazing and fast the face unlock was. After the update it sucks, to the point where I just can't use it. I did register my face again multiple times as well.
Click to expand...
Click to collapse
It's back to be crap now. After I reset the phone, it was working great again, but now not so much. I even get a pop-up sometimes saying to clean the lens!! It's spotless!
The iris scanner now is what the facial recognition WAS before the update. So, I'll start using that until this is figured out and solved because at least facial recognition works with glasses on.
Try registering your face much closer , cover most of it but not 100%, leave a gap of 2 or 3 cm. Also have you tried turning on the "faster recognition" option?
eniorodriig said:
Try registering your face much closer , cover most of it but not 100%, leave a gap of 2 or 3 cm. Also have you tried turning on the "faster recognition" option?
Click to expand...
Click to collapse
Where's the faster recognition setting
No problems with mine whatsoever. Crossing fingers it'll stay that way.
JDM9499 said:
It's back to be crap now. After I reset the phone, it was working great again, but now not so much. I even get a pop-up sometimes saying to clean the lens!! It's spotless!
The iris scanner now is what the facial recognition WAS before the update. So, I'll start using that until this is figured out and solved because at least facial recognition works with glasses on.
Click to expand...
Click to collapse
Yup using the iris scanner as well now. Surprisingly faster than the first day which is weird, but still not as fast as face unlock . I wonder which takes more battery
laz45 said:
Where's the faster recognition setting
Click to expand...
Click to collapse
Settings -> Lock Screen and Security -> Face Recognition
You should be able to find the "Faster Recognition" option in there. I believe this came bundled with an update i received today, i cannot remember also having this option before. Take a look there and make sure the phone is up to date.
I believe there is improvement to be made here, hopefully once we start rooting this puppy , someone can come along and tweak a few settings.
eniorodriig said:
Settings -> Lock Screen and Security -> Face Recognition
You should be able to find the "Faster Recognition" option in there. I believe this came bundled with an update i received today, i cannot remember also having this option before. Take a look there and make sure the phone is up to date.
Click to expand...
Click to collapse
AT&T user here. Got the OTA update yesterday that made the facial recognition terrible and I don't have the "Faster Recognition" option.
EDIT: I should also mention that I have redone the facial setup multiple times since the update and it's still noticeably worse than before the update.
Mine got slower, but I cleared cache and redid the facial set up, seems to be better again (after TMobile update).
JDM9499 said:
When I first got the phone yesterday, unlocking the phone was crazy fast with the facial recognition. This morning, I got the latest software update, and now, it's basically unusable. Has anyone else experienced this?
Click to expand...
Click to collapse
I have noticed the same I can hardly use facial recognition after update was so fast before. Now using iris
Iris is significantly better, safer and faster.
how safe is the iris scanner - from a medical POV
when activating it - you get loads of disclaimers including one saying to always keep at least 8 inch between eyes and phone to prevent retina damage - i mean WTF!!!!!!
has anyone looked into this ****?
tim2london said:
how safe is the iris scanner - from a medical POV
when activating it - you get loads of disclaimers including one saying to always keep at least 8 inch between eyes and phone to prevent retina damage - i mean WTF!!!!!!
has anyone looked into this ****?
Click to expand...
Click to collapse
Yeah I saw the warning that scared me. I'm a delivery driver and drive around 350mi a day Monday- Friday can't have my eyes damaged. Plus just payed 4500 for lasic
I have had lasik also. I would not worry about it. All things have warnings like that... heck, even your basic computer screens have warnings.
Yeah since the Att update face recognition doesn't work at all for me, wellaybe 1 time out if 10. Annoying. I'm not bothered someone could use a photo of me to unlock. If my phone is ever out of my possession for that long, I'm disabling it remotely anyway
Yep, got my s8 last night, was showing my GF how incredible facial recognition was, THEN I applied the update. Doesn't work at all, the fingerprint scanner is in the worst possible place, and I wear glasses so the iris scanner won't work for me. I can't believe I'm starting to miss the fingerprint scanner on the S7.