Related
Can someone please check how well the fingerprint scanner works? Is it better than the s5 fingerprint scanner that was a piece of crap?!?!
I set it up and already stopped using it. Failed too many times and I couldn't get private mode to work which is the only reason why I wanted the fingerprint.
2swizzle said:
Can someone please check how while the fingerprint scanner works? Is it better than the s5 fingerprint scanner that was a piece of crap?!?!
Click to expand...
Click to collapse
I have read somewhere that the fingerprint scanner is the same as the s5, so no it's not any better.
I just started using it. Seems fine so far. I'll report back tomorrow after I've spent more time with it.
Works fine. :good:
Works fine with me. 8 out of 10 times I don't need to re-swipe. I like it.
Sent from my SM-N900T using XDA Free mobile app
Found out that my fingerprint private mode and s health crashing is due to xposed. Pretty much ducks considering you basically have to choose what you want most
knarfies said:
Found out that my fingerprint private mode and s health crashing is due to xposed. Pretty much ducks considering you basically have to choose what you want most
Click to expand...
Click to collapse
Is Xposed the pesky app doing that? I just installed Xposed and YouTube Adaway, after I did that the S Health app stopped working.
works great. this is now my go to. i'm quite surprised how well it worked. maybe it was how i registered my prints. who knows.
devynbf said:
Is Xposed the pesky app doing that? I just installed Xposed and YouTube Adaway, after I did that the S Health app stopped working.
Click to expand...
Click to collapse
Yeah, was pretty upset that I can't use the hrm with xposed or private mode. I tried the whole changing the build prop ro.securestorage trick but it caused nova launcher to crash until I changed it back. Smh.
I would use the fingerprint scanner but when I'm excited, my hands get sweaty. Hands have been sweaty for the past 6 hours or so messing around with this beast lol.
Gotta wait till I calm down :b.
re: xposed framework & wanam
devynbf said:
Is Xposed the pesky app doing that? I just installed Xposed and YouTube Adaway, after I did that the S Health app stopped working.
Click to expand...
Click to collapse
I uninstalled xposed framework and wanam because I noticed that if they are
active it makes the screen scrolling in most any app and launcher scrolling
from home screen to home screen after a while the scrolling gets stuck for a
few seconds intermittently. (like a slight delay where the phone feels like it locked up)...
The phone never done that before installing xposed framework and wanam.
Sweet!! I hated the s5 scanner and love my iphone 6 plus scanner. I'm selling my iphone to get the note 4 and would be upset to lose the ability to unlock my phone using the scanner. Got to keep these chicks out of my phone lol lol
Misterjunky said:
I uninstalled xposed framework and wanam because I noticed that if they are
active it makes the screen scrolling in most any app and launcher scrolling
from home screen to home screen after a while the scrolling gets stuck for a
few seconds intermittently. (like a slight delay where the phone feels like it locked up)...
The phone never done that before installing xposed framework and wanam.
Click to expand...
Click to collapse
I had the samething happened to me. I didn't think of uninstalling xposed. I had to odin back 2 twice because removing root and doing the factory reset just made the phone rebooting. Everything ran great until i installed xposed. Its ruuning great now without xposed app. Don't want to mess with it anymore.
Misterjunky said:
I uninstalled xposed framework and wanam because I noticed that if they are
active it makes the screen scrolling in most any app and launcher scrolling
from home screen to home screen after a while the scrolling gets stuck for a
few seconds intermittently. (like a slight delay where the phone feels like it locked up)...
The phone never done that before installing xposed framework and wanam.
Click to expand...
Click to collapse
I've noticed this too. You think its just something that can be fixed with updates to xposed? to calibrate it to work smoother with the note 4?
Been using it since I got my unit and it works perfectly every time unless I swipe across it sideways or something weird like that. Also on the subject of xposed I loaded it onto the phone and had nothing but issues and massive slow downs, once I removed it the phone went back to normal. So I guess xposed just isn't ready yet.
I like it and I have no problem.
You get 10 times to record it, so I swipe it straight, sideways, that way, this way, etc
It work for me!
RiffyDivine said:
Been using it since I got my unit and it works perfectly every time unless I swipe across it sideways or something weird like that. Also on the subject of xposed I loaded it onto the phone and had nothing but issues and massive slow downs, once I removed it the phone went back to normal. So I guess xposed just isn't ready yet.
Click to expand...
Click to collapse
it slowed the phone down and froze as well on mine but i noticed that it had to do something with gaining root access. Like installing aftermarket apps took forever as the installation process just hung when on wifi. (dont ask me but i noticed the wifi would reconnect and the the app installed). After a while though, (app settings started actually working) the device was snappy. Not sure if the system needed to settle or what but everything seems to be working fine. The only thing not working for me is the private mode. Without private mode, i have no use for the fingerprint and with the spigen neo hybrid, i cant get it to actually register my heart rate so unless i take the case off i wont be using that either i suppose.
knarfies said:
it slowed the phone down and froze as well on mine but i noticed that it had to do something with gaining root access. Like installing aftermarket apps took forever as the installation process just hung when on wifi. (dont ask me but i noticed the wifi would reconnect and the the app installed). After a while though, (app settings started actually working) the device was snappy. Not sure if the system needed to settle or what but everything seems to be working fine. The only thing not working for me is the private mode. Without private mode, i have no use for the fingerprint and with the spigen neo hybrid, i cant get it to actually register my heart rate so unless i take the case off i wont be using that either i suppose.
Click to expand...
Click to collapse
I just assumed xposed just wasn't ready for the note 4 yet. I got a lot of weird issues the moment I put it on and it was like pulling teeth to remove it because I came to depend on a lot of stuff it did. But I am sure it will get an update and be working again. It was just weird to see how crappy the system got all of a sudden, I had 4 photos on my phone and not linked to dropbox or drive but when I tried to open the gallery it would hang for 2 minutes before displaying the four images. I think we maybe expecting to much from a phone that isn't "out" yet (or was today the launch date)
RiffyDivine said:
I just assumed xposed just wasn't ready for the note 4 yet. I got a lot of weird issues the moment I put it on and it was like pulling teeth to remove it because I came to depend on a lot of stuff it did. But I am sure it will get an update and be working again. It was just weird to see how crappy the system got all of a sudden, I had 4 photos on my phone and not linked to dropbox or drive but when I tried to open the gallery it would hang for 2 minutes before displaying the four images. I think we maybe expecting to much from a phone that isn't "out" yet (or was today the launch date)
Click to expand...
Click to collapse
i didn't have that issue but i did notice hangs in and out of numerous apps. to be honest, i haven't noticed it anymore though. It felt as though something was going on in the background and now that its done, it seems to have smoothed out. i wish i had the same experience with the fingerprint scanner though. I noticed when swiping down with my pointing finger, that it registers pretty well but when we hold our device... we typically use our thumbs and i couldn't get my thumb to unlock the phone as well as my pointing finger.
Ever since upgrading to Lollipop 5.1 on my Moto X (2013), I get the message: "vnd.android.nfc://ext/motorola.com:xring", every time that the screen unlocks with the Motorola NFC Skip. Is there a way to prevent the message from showing?
Thanks
Pat
I get that message as well, the Skip doesn't really work consistently for me anymore though. Maybe the first day I set it up it kind of worked, now it doesn't do a damn thing. Anyone on 5.1 with 2013 able to get it to work reliably? I may do a factory reset if so.
If i remember correctly, Motorola posted that skip wont work anymore with 5.1
Called them up to get suggestions.
I uninstalled and reinstalled the Skip app on the play store. Then I re-added the Skip to NFC security settings. Seems to be working reliably now.
ohmimpotence said:
Called them up to get suggestions.
I uninstalled and reinstalled the Skip app on the play store. Then I re-added the Skip to NFC security settings. Seems to be working reliably now.
Click to expand...
Click to collapse
Does it still give the message or is it gone now?
Still gives the message if I do it with the screen on. From the lock screen it doesn't seem to. I haven't tested if it's still working today because I'd have to remove like the 4 trusted locations I have for my home but even with trusted location on, my phone will lock itself after not using it for a certain amount of time and I'm not using on body detection. When it did that this morning, I was not able to unlock it using the Skip.
ohmimpotence said:
Still gives the message if I do it with the screen on. From the lock screen it doesn't seem to. I haven't tested if it's still working today because I'd have to remove like the 4 trusted locations I have for my home but even with trusted location on, my phone will lock itself after not using it for a certain amount of time and I'm not using on body detection. When it did that this morning, I was not able to unlock it using the Skip.
Click to expand...
Click to collapse
I think that it has to do with SmartLock locks up the phone after 4 hours of inactivity.
The weird thing is it doesn't unlock with the Skip if it's locked due to inactivity.
Anyone ever get any satisfaction here? I just got the 5.1 update for me Verizon moto x, it's made my NFC ring practically unbearable. It unlocks the phone fine, but then it continually scans my ring and pops up every time the ring moves out of range and back in range of the NFC reader.
Sent from my XT1060 using XDA Free mobile app
I sometimes get the warning, no face detected, regardless of the light I am in. It once suggested I restart if I get this problem. Is it just my device?
ekerbuddyeker said:
I sometimes get the warning, no face detected, regardless of the light I am in. It once suggested I restart if I get this problem. Is it just my device?
Click to expand...
Click to collapse
I'm leaving this here to assist others. From a search: Turns out it is from a conflict with WhatsApp. If you have this problem, remove the permission for WhatsApp to access the camera, then return it when it next asks. It fixed it.
Update. It's not WhatsApp. Still having intermittent issues. Anyone have ideas?
Same here. Yesterday out of 20 tries it worked once. I am close to say that their implementation of face unlock is utterly crap. It works badly most the time, no matter what lighting situation my face is in.
EDIT: After I wrote this I tried it again, same problem: "No face detected".....
I let the phone sit at the same position and didnt move, rebooted and it worked. This must be some kind of bug.
I think it's related to a 3rd party app
Agreed, I have no problems.
ekerbuddyeker said:
I think it's related to a 3rd party app
Click to expand...
Click to collapse
hmm, the questions is what app? I have installed quite a bunch....
I don't have much problem with it, as long as it's decent light.
Sent from my SM-N950U using Tapatalk
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
fredphoesh said:
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
Click to expand...
Click to collapse
they broke ok google about a year ago, very sad.
SOLUTION!
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
fredphoesh said:
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
Click to expand...
Click to collapse
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
I had this problem, disabled Bixby, works properly now.
Sent from my SM-N950U using Tapatalk
Liface said:
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
Click to expand...
Click to collapse
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Mine get borked every time I toggle between power saving modes. I like to use Extreme power saver for overnight and Medium mode at work.
Medium mode straight up breaks OK Google. Not sure if this is by design or a bug, but it just will not hear me.
Coming out of either mode (and extreme is the worst) and neither "Hi Bixby" or "OK Google" work until I do another full reboot. Sometimes I have to reboot then go back into Google voice setting to switch the option back on manually. If I try to do this before the reboot the option is greyed out and I can't move it. Sometimes just the reboot is enough.
It's random as hell and extremely annoying. I have submitted the bug to Samsung via the feature in the Samsung Members app, but that was over two weeks ago and has seen no response.
Interesting post. My wife's OK Google voice doesn't work but mine does. Both USA T MO version. With works I'm referring to having the Google widget on home screen and saying the sentence OK Google. Mine responds and hers doesn't. With screen ON.
Sent from my SM-N950U using Tapatalk
fredphoesh said:
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Click to expand...
Click to collapse
That's not it, I rarely use battery saving mode and this happens 100% of the time.
Ok google for me just does not work.
Anyone get a fix for this?
"Ok Google" works when screen is on, but if I say it while the screen is off, it makes the noise and I get edge lighting indicating it's listening, however it doesn't respond and when I manually turn on the screen assistant is open saying "can't reach Google at the moment."
Power saving mode is off, tried disabling Bixby, clearing cache, nothing.
Hellothere37 said:
clearing cache, nothing.
Click to expand...
Click to collapse
so clearing cache of Google app and rebooting did not help at all?
bizarre, that fixed it for me...
I have a UK version.
I'd phone Samsung!
I'm frustrated too because I can't figure out how to use it while in power saving mode. I thought I added it correctly in the optimized battery usage apps (disabled google, ok google enrollment and voice assitant there). I can't see it as an option to select under unmonitored apps. Any idea what I'm missing?
Thanks for any help
This is strange to hear. Mine has worked flawlessly, as good as my pixel XL. Screen off and locked or not. I say ok Google, phone unlocks, and then I ask it whatever. Only thing ive done is disabled bixby by way of BK disabler.
Sent from my SM-N950U using Tapatalk
May be coincidental but I have not the slightest problem, and yeah, I uninstalled the Bixter. One thing I have read somewhere or other is that the OK Goog command is also subject to the level you set for Bix. In other words with sensitivity turned down for Bix it's also turned down for Goog. I never tested that one but might be worth looking at...
gingi999 said:
they broke ok google about a year ago, very sad.
Click to expand...
Click to collapse
So two things I wanted to mention the first one was my old phone case actually covered one of the microphone holes. Meaning the cut-out wasn't there so I used a drill and made a hole and it fixed part of the problem.
I have to be honest with you the Note 8 solved all the OK Google problems that I was having the past. For example the lockscreen didn't used to work and it works now I mean it was really a piece of trash with my Galaxy S7 Edge and now I can't imagine living without it.
Having problems like the first post where google assistant/ok google is non responsive all around. I've noticed that if I clear cache and data it falls back to just "ok google" and it work all the time. If I activate the google assitant with ok google it fails immediately. Who can fix this?
Ever since the update to Oreo I've been constantly having this issue and it's extremely irritating and can't figure out how to stop it from happening. Basically at least once a day now, sometimes more than once it refuses to use the fingerprint scanner and wants me to enter my password or now my PIN since I switched to the less secure pin just to make it less of a pain everytime this happens and I just want it to go back to working properly so I can have the password again, does anyone know how to fix this issue? It's an unlocked note 8 and it's not rooted or anything, just a stock phone.
It's probably because you're phone has restarted and requires a pin after a restart before it'll use biometrics - It's a problem on Oreo, it's basically just a completely cr*p update that's broken so many things.
Samsung as usual, don't seem to give a stuff!
Nope, it's not a restart that's causing it, that's an entirely different message, especially since the phone's encrypted so the phone won't even start up on a reboot till the encryption password is entered. This is just a it randomly won't accept the fingerprint to unlock, I've turned the phone off then turned it right back on to unlock it and this has happened, 100% certain it had nothing to do with rebooting.
I've read some people saying they had an app that force locked the phone and that causes this and removing it fixed the problem, but I don't have any app that does that.
I have an unlocked note 8 too, I only use iris validation (finger print does not reliably work for me because of my eczema), the only time i have ever encountered this was when the phone went to lock screen while trying to access bio-metric validation (banking app, only ever happened once, i disabled fingerprint after due to unreliability relating to eczema as previously mentioned)
Maybe not the same issue but fingerprint unlock never works for me reliably. I get that message when my fingerprint can't be recognized. I have working hands so often my fingers get knicked, scratched, etc or even just wet causing my fingerprint not register. If I reregister fingerprint with out a perfect fingerprint, after my fingers heal, can't be recognized again. Happened on my Note 5 as well so I stopped using fingerprint to unlock.
Don't think that's the issue for me, I never have any issues with the fingerprint reader normally, it always works great when it actually lets me use it.