Skip to content

Video: Apple flubs its first demo of Face ID during iPhone X keynote

2017 September 13
by RSS Feed

The headlining new feature of iPhone X is its depth-sensing facial recognition feature afforded by a new TrueDepth camera system hidden in that notch.

But Apple flubbed its first demo of the technology during yesterday’s keynote at the Steve Jobs Theater, putting its software engineering chief Craig Federighi, who was demoing the future, in an awkward situation.

Here’s that moment.

People who have taken a closer look at the footage observed that it wasn’t probably Federighi’s fault because he picked up a phone that appeared to had just been restarted. As you know, for security reasons, after an iPhone is restarted the system always requires that you punch in a passcode before Touch ID or Face ID is enabled.

Most of the reviews I’ve seen online praise Face ID, noting that it “just works” but we’ll have to wait until iPhone X arrives before we stress-test the feature under various conditions to see how well it really works.

Apple says the chance of someone unlocking iPhone X with their face is one in a million. By contrast, the odds of someone having a. fingerprint similar enough to yours to crack Touch ID are about 1 in 50,000.

Face ID takes advantage of the new depth-sensing camera that shoots 30,000 invisible dots onto your face, which are detected by an infrared camera that builds your unique facial map, using artificial intelligence to verify it’s you.

Your facial map is stored encrypted and safely walled off from the rest of the system inside the Secure Enclave portion of the A11 Bionic chip, like Touch ID.

A new flood illuminator sensor kicks into action in low-light situation, using invisible infrared light to help identify your face in darkness. Apple even asked Hollywood special-effects specialists to help it secure Face ID.

They’ve created some very realistic recreations of human faces that Apple says couldn’t bypass Face ID. According to the company, if you do have an evil twin you should use passcode security instead.

Source link:

Leave a Reply

Note: You may use basic HTML in your comments. Your email address will not be published.

Subscribe to this comment feed via RSS