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..
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)"
After weeks of trying to work out why my browsing experience was awful using mobile Internet I finally found something that really works for me.
Drum roll........ Turn my device upside down
Basically don't touch the end with the USB port and my data lock ups basically disappear.
Anyone else's phone the same? Probably not.
meangreenie said:
After weeks of trying to work out why my browsing experience was awful using mobile Internet I finally found something that really works for me.
Drum roll........ Turn my device upside down
Basically don't touch the end with the USB port and my data lock ups basically disappear.
Anyone else's phone the same? Probably not.
Click to expand...
Click to collapse
Nope can't say that I have had this problem
Sent from my Nexus 4 using Tapatalk 2
What's a 'data lockup'?
Oh well, guess I got a duffer. But at least it works now:cyclops:
I have largely very few issues while using the Netgear PVT3000 with my Windows 8 laptop but have severe lag/pauses/drop outs with the Note 3. I also tried the Note 3 yesterday with a 2013 Samsung TV and things were better but still very laggy and with drop outs. In both cases things get better after a few minutes of the connection but eventually collapse. The common factor here is the note 3 and perhaps using miracast as opposed to Intel Widi protocol. All of this has been done within very close range and full bars being reported so signal strength isn't the issue. As there are no options to play with it kind of works or doesn't work - in this case it doesn't.
Wondered if anyone else has had more luck or has some suggestion because this is stopping me from becoming much less reliant on my laptop.
airwater9 said:
I have largely very few issues while using the Netgear PVT3000 with my Windows 8 laptop but have severe lag/pauses/drop outs with the Note 3. I also tried the Note 3 yesterday with a 2013 Samsung TV and things were better but still very laggy and with drop outs. In both cases things get better after a few minutes of the connection but eventually collapse. The common factor here is the note 3 and perhaps using miracast as opposed to Intel Widi protocol. All of this has been done within very close range and full bars being reported so signal strength isn't the issue. As there are no options to play with it kind of works or doesn't work - in this case it doesn't.
Wondered if anyone else has had more luck or has some suggestion because this is stopping me from becoming much less reliant on my laptop.
Click to expand...
Click to collapse
Ask another way: Has anyone had good success with wireless display and if so with which receiver?
I tried them with multiple at work and it does work but there is atleast a 1 second delay
Sent from my SM-N9005 using XDA Premium 4 mobile app
which firmware are you using?
Since you guys at least seem to have it working maybe you could help me...
I can't get screen mirroring to work.
The PVT acts like it is going to connect but then it freezes on "Connecting to the wireless display device..." even though my phone says the connection is good.
It shipped to me with 2.4.26 already on it and I am having a hard time getting any other firmware to load. It seems to always fail.
Netgear support is being pretty useless on it since Note 3 isn't officially supported but it did the same thing with my GF's Note II.
bds369 said:
Since you guys at least seem to have it working maybe you could help me...
I can't get screen mirroring to work.
The PVT acts like it is going to connect but then it freezes on "Connecting to the wireless display device..." even though my phone says the connection is good.
It shipped to me with 2.4.26 already on it and I am having a hard time getting any other firmware to load. It seems to always fail.
Netgear support is being pretty useless on it since Note 3 isn't officially supported but it did the same thing with my GF's Note II.
Click to expand...
Click to collapse
There isn't much that should stop some kind of connection being established one the dongle has had a minute to boot - the obvious one is to disable the power saving option on the note 3.
I'm very disappointed and surprised more people aren't doing widi mirroring and reporting issues with it.
airwater9 said:
There isn't much that should stop some kind of connection being established one the dongle has had a minute to boot - the obvious one is to disable the power saving option on the note 3.
I'm very disappointed and surprised more people aren't doing widi mirroring and reporting issues with it.
Click to expand...
Click to collapse
I agree. Would really like to know what firmware is working for anyone with Note 3. I thought there may be a custom version floating around. Which version are you guys on?
My latest update from Netgear is they want to do a hardware RMA. I'm not entirely convinced that it is hardware but there's no other posts about this that I can find.
I tried every firmware on their site and got the same result with Note 2 and 3.
https://www.dropbox.com/s/h7onknmps7dn10i/2014-01-22 19.44.51.jpg
My thought was maybe the firmware wasn't working with Android 4.3
bds369 said:
I agree. Would really like to know what firmware is working for anyone with Note 3. I thought there may be a custom version floating around. Which version are you guys on?
My latest update from Netgear is they want to do a hardware RMA. I'm not entirely convinced that it is hardware but there's no other posts about this that I can find.
I tried every firmware on their site and got the same result with Note 2 and 3.
https://www.dropbox.com/s/h7onknmps7dn10i/2014-01-22 19.44.51.jpg
My thought was maybe the firmware wasn't working with Android 4.3
Click to expand...
Click to collapse
RMA will be pointless, I've got two pvt3000s - both with the same issue with the galaxy note 3.
Got onto Netgear who advised me to try different firmwares and I went for v2.4.3 and found that it eliminated all of the drop out and most of the timing issues (except for youtube which lags 2-3 seconds behind what is happening on the phone but as the sound and video are sync'd, it's not really a problem).
airwater9 said:
Got onto Netgear who advised me to try different firmwares and I went for v2.4.3 and found that it eliminated all of the drop out and most of the timing issues (except for youtube which lags 2-3 seconds behind what is happening on the phone but as the sound and video are sync'd, it's not really a problem).
Click to expand...
Click to collapse
Are you on a completely stock ROM or a custom? I cannot get it to connect. Always freezes.
I'm on stock. Is your power saving turned off?
airwater9 said:
I'm on stock. Is your power saving turned off?
Click to expand...
Click to collapse
Yes power saving is turned off.
I was on a mostly stock rooted rom. Now I even went back to unrooted stock rom. Obviously my Knox is tripped but everything else is bone stock. It still won't connect. Going to scour xda today too see if there's some patch for mirrorcast for if you have ever rooted
hi to all how any one that has the same setup will help me understand i will try and keep it short first im using samsung note 4 running 6.0.1 now
ok so here goes i use my gear 2 together with my note 4 as a trusted device you know like every time the gear 2 is close the device must stay unlocked but it does not stay unlocked and there is no Bluetooth disconnecting anything like this i look at that so battery is full the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage but i connect it now and its fine but after a wile (don't know the exact time here ) but say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on and there was nothing like it disconnecting it is as if the phone on its own make sure that it asks the finger print every now and again say like i leave it overnight the next morning first fingerprint then you can use the phone i hate this it kind of bugs me if the steal the phone and the range is to big the device will lock any way why lock when the gear 2 it near the phone any help please
honestly, i stopped reading after few seconds.
have you ever heard about punctuation? - you know, the thing that looks like dots and commas, makes reading much easier.
244 characters in 1 sentence.
wow dude, looks like you dont wanna get helped.
biebie29 said:
...say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on...
Click to expand...
Click to collapse
From the Google Smart Lock support page (https://support.google.com/nexus/answer/6093922):
"Note: When you don't use your phone for 4 hours, and after you reboot your phone, you'll need to manually unlock it with your PIN, pattern or password"
It's a security feature.
EDIT: ...and, wow, yes, that was some run-on sentence!
Is there a root app to disable it or not
biebie29 said:
Hi to all. How any one that has the same setup will help me understand. I will try and keep it short. First, i'm using samsung note 4 running 6.0.1 now.
Ok, so here goes:
I use my gear 2 together with my note 4 as a trusted device. You know like every time the gear 2 is close, the device must stay unlocked. But it does not stay unlocked and there is no Bluetooth disconnecting, anything like this. I looked at that. Battery is full, the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage.
I connect it now and its fine, but after a while (don't know the exact time here ), say after 3 hours of no use, i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near. The gear 2 is still on and there was nothing like disconnecting. As if the phone on its own make sure that it asks the finger print every now and again.
For example, i leave it overnight the next morning first fingerprint then you can use the phone.I hate this. It kind of bugs me if they steal the phone and the range is to big, the device will lock any way. Why lock when he gear 2 it near the phone? Any help please.
Click to expand...
Click to collapse
Fixed that for you
I really had to break that down to make it readable for me. But as others said, it's an Android feature. Afaik there is no way of disabling that all together. There might be some xposed module i haven't heard of, but with my moto360 i couldn't get it to work the way you'd want. Sorry mate
Kinsman-UK said:
It's a security feature
Click to expand...
Click to collapse
As the programmers use to says: Its a feature, not a bug
Some people are just plain jerks, and I wish XDA would take these "grammar police" trolls a bit more seriously and penalize them.
Perhaps OP is using a translator, or is from another country, or is young. That should not matter to any of us and we should offer our help regardless of whether he/she includes proper punctuation or not. I'm sure the effort he/she put into typing it was much greater than that of the ridiculous responses some of you gave.
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
biebie29 said:
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
Click to expand...
Click to collapse
The Note 4 is problematic all around, but 6.0.1 is a problem for every device that has it. It is the reason I left my Nexus 6P, and my Nexus 6. I have a Xiaomi Mi Max, also on 6.0.1 and it has the same major flaws I experienced on all devices running 6.0.1. The problems I speak of are the WiFi and Data stop working briefly while browsing the web, or downloading something. However, I believe this is an issue related to the security patches related to Qualcomm devices on 6.0.1. It seems like an overall radio problem.