If I have a mask on, swiping up immediately brings up the pass code screen. In this case immediately is <0.5 secs.
FWIW I have a new Apple Watch and have this issue. I just installed the update so I haven't tested the Watch authentication. If it can't detect a mask I'll have the same issue as before waiting for a number pad.
What exactly is the reason/rationale that it has to fail on facial recognition first before proceeding to use passcode?
C O U R A G E
Joke aside, it seems that Face ID was a tremendous technical effort so you could have instant access to your phone. Besides unlocking, there's no other serious application (memojis aside). The fingerprint reader was probably removed just to prop acceptance of Face ID. Also, Face ID is less secure. If you're detained or mugged, just looking at your phone will unlock it before you can react and look away.
IMO, the 3D scanner should be on the other side, enhancing your pictures with 3D depth.
By the "they can just use violence" logic, no computer is secure and we should throw them all into the ocean. Security can improve the intermediate cases- focusing solely on the worst case is unproductive.
As far as hypothetical situations go, I prefer this over them cutting off my finger.
More seriously, in a situation where I'm detained or mugged, there will be a lot of external factors which are pushing me to unlock my phone, be it via passcode or biometrics.
FWIW, "SOS mode" (holding the power and volume up buttons) will purge information needed for biometrics to work and mandate a PIN on both TouchID and FaceID devices.
That's what the LIDAR sensor on the latest phones is for. It only gets used in photos for the portrait-mode stuff, admittedly.
Portrait mode is Apple-speak for pseudo-depth-of-field, which is the effect that real cameras do that make the subject in focus but the background blurry.
It makes photos look way more professional.
Much easier to force someone to unlock the phone with their fingerprint than to force them to unlock with faceid if you have “Require attention” on.
You can’t physically force someone to look in a certain direction, but you definitely can force them to tap their finger on a surface.
Excuse me, but this is ridiculously easier than forcing someone to use their fingerprint; just wait until they are distracted, show them the phone and ask them "what is this?". It unlocks in less than a second with "Require Attention" activated. We prank each other this way when we forget our phones around the house.
* If you're concerned about someone who can see you typing, a biometric is better because they have far fewer chances to watch you — especially if you don't reboot outside of your home.
* If you're concerned about actual adoption, a biometric is better because you remove the constant frictional password entry cost which causes a large fraction of users to use short, easily-entered passwords.
* If you're concerned about someone who has enough access to construct a usable fingerprint / face facsimile but can't coerce you into providing a password or shoulder-surf it with a drone, a long password is better.
To better train the facial recognition system, perhaps.
If a mask is on the tip of my nose and loose fitting, it seems to work.
I always enable this when setting up an iPhone for a parent (or myself).
Personally, I'm getting the passcode prompt in less than 1 second.
When you refer to the Apple Watch being “less aggressive to re-lock,” you’re really overselling it. The Watch does not re-lock for the entire time it’s on your wrist after you first unlock it (which you can do with FaceID on your phone). I go weeks without typing a passcode on my Watch.
Apple reached phone perfection with the iPhone 4; they reached access perfection with touchID. Things have gotten worse since then.
FaceID is perfect.
FaceID works better when your hands are dirty or unavailable (e.g. you're wearing gloves), TouchID works better when your face is covered or your look changed slightly[0].
FaceID has been a strict downgrade for me, there are very few situations where FaceID works and TouchID wouldn't have, the reverse is a daily occurrence. And things would be even worse if I couldn't work from home, as TouchID works just fine with a mask.
[0] in bed without my glasses FaceID works 0% of the time, even resetting the entire thing and re-registering my face with and without glasses, it works all of 2 days before it stops recognising me without glasses.
1. hold the phone far enough away from my face for faceid to work, and
2. focus my eyes on the screen
so if I wake up in the middle of the night, I always have to use my passcode to unlock my phone.If you support just one with the other disabled, it is wasted hardware/space in a device with extremely limited size/cost budget. If you require both, you haven't fixed the usability issues.
The touchID on my new MacBook Pro is extremely useful. Trained on right index finger.
Also, these are not “extreme” or “dire” or even uncommon conditions - most of Northern Europe, Canada, and the north-eastern USA experience several months of such conditions every year.
FaceID has been quite good other than the masks issue. I just wish Apple would allow a grace period for rechecking auth.
I usually only replace phones when the battery starts going. But I'm thinking of getting the SE anyway, just in case it isn't available when this one (X) finally goes.
I bought a aftermarket headset lightning adapter. Wireless charging largely eliminated my complaints about charging. Fast charging with an 18w brick is great as well!
I only miss Touch ID when wearing a mask. Face ID is otherwise so much more reliable and fast.
Thank you, I tell people that I liked developing on that platform and the only reason I still don't is because XCode no longer supports it and I get critized like I'm a luddite.
It's a phone, you can't do a lot more on device other than add new sensors and new networking technology... it's like buying a new car because it has a 2021 instead of a 2020, it hasn't changed that much....
I still use an SE to control a few things around the house. Without a SIM, with the mobile radios and bluetooth disabled but wifi enabled, and with Apple's idiotic News app that nobody wants disabled, the battery lasts for 20 days. Peak iPhone.
In all fairness, I believe they require you to set a passcode on your watch if you use it for Apple Pay. And, honestly, especially right now--while I don't always use my watch to pay mostly because the Magsafe wallet makes pulling out a card very easy--it's pretty convenient.
Apple doesn't always succeed with picking the ideal middle point between too few and too many choices (most frequently, it's skewed towards the 'too few' side) however.
Also, it wouldn’t surprise me if significant percent of users actually checks their phone at least one in 15 minutes. This would mean that their phones would be at unlocked almost all the time.
- When Face Unlock is enabled the iPhone doesn't take 15 minutes to re-lock. That's what is being requested, not what we have. 15 minutes would be much longer than the status quo.
It such a shame that apple are good at removing useful features rather than just adding them.
This new Watch feature is great for people like me who are paranoid about punching in my passcode in front of a shop full of cameras and strangers, but it's a nice-to-have feature not a "required" feature as some of the above comments seem to complain it is.
My face unlock works fine with sunglasses. If it detects a mask could it fall back to judging the remainder more thoroughly?
Having used it for several weeks, this feature elegantly solves the issue.
Right you are, but for a different reason: Face masks entirely break Apple Pay. If you have an Apple Watch, lucky you, you can use the watch to pay instead. If you don’t? Well, tough luck.
Unlock with Watch apparently does not work with Apple Pay.
/e: Wasn’t aware of activating Pay using the code. Oops. :D
I might be misunderstanding you, and it’s far from ideal, but you can still use your passcode - I do it all the time.
I find Apple Pay so much easier to use with the Watch that I never can remember how to use it on the phone.
1. https://www.imore.com/sites/imore.com/files/styles/large/pub...
- This is an issue of Apple's own artificial creation.
- This doesn't even solve the issue.
So this all started because Face Unlock didn't work with masks, that's not Apple's fault. But what is entirely Apple's fault is that they break an option which resolves this only when Face Unlock is enabled: "Require Passcode."
When you disable Face Unlock you can set Require Passcode to e.g. 15 minutes/1 hr, and it largely mitigates the aggressiveness by which your iPhone re-locks itself while you're e.g. out grocery shopping in a mask and trying to use a shopping list. But when you enable Face Unlock this option is removed (forced to "Require Immediately").
So Apple enforces "Require Immediately" in Require Passcode, it blows up in their face, and then instead of backing down when masks broke Face Unlock, they instead over-engineer a solution where you have to buy an Apple Watch to work around it.
Their new work-around solution doubles down on exactly the same anti-choice problems discussed above because they forget to mention in this press release that you MUST enable a passcode on your Apple Watch to use this feature at all (and they're relying on the Apple Watch being less aggressive to re-lock than the iPhone).
If you jailbreak your iPhone you can just switch it from "Require Immediately" to e.g. 30 minutes and this mask issue is almost completely gone in one fell swoop. This Apple Watch fix only kinda works (e.g. lost connection to the watch = relock, Watch thinks it is off your wrist = relock, etc).