What you describe is essentially how Touch ID works on newer iPhones, just with your fingerprint as the simple passcode. On a fresh boot, you have to put in your full passphrase, and every 48 hours after that. After you put in your passphrase, fingerprint unlock is available until either you turn the phone off, 48 hours passes, or fingerprint authentication fails five times in a row.
Unfortunately, the 48 hours thing isn't configurable, so it's not quite perfect, but it's pretty decent.
Certainly for me, it has immensely improved the security of my phone. In situations where I don't trust the fingerprint authentication (e.g. crossing an international border), I can just shut the phone off. Otherwise, it provides "good enough" security. Yes, there are potential attacks on the system, by copying my fingerprints and replicating it, but the five-attempt limit and the 48-hour timeout are good enough. For me, it's a vast improvement over what came before, when I had a passcode of 0000 just to satisfy some apps that wouldn't offer certain features unless a passcode was set.
There are some improvements I'd like to see. The timeout should be customizable. I'd like to be able to set up a "duress fingerprint" which immediately disables fingerprint authentication, as an easier alternative to turning off the phone. But overall it seems like a good blend of security and usability.
Coercion codes would certainly be a great next step for Apple to implement, not just with fingerprints but with actual pass phrases/PINs as well. Ideally a coercion code system would allow a couple of different levels of response depending on a user's needs and the situation they faced. For example, one simple PIN/finger print could just revert the system to needing the full passphrase, while another (or a longer passphrase for that matter) could cause the machine to activate pre-scripted actions, wipe itself, or even simulate a malfunction.
For what it's worth you can actually already do a limited version of this under iOS if you jailbreak. Touch ID can handle up to five separate fingerprints, and in vanilla iOS AFAIK any successful read is the same as any other in terms of system action. Interestingly however, internally Apple actually registers a separate system event for each different finger. Either writing your own tool or using a tweak like Activator, you can thus set different fingers to trigger different actions, including shutting down/rebooting the device (which in turn activates a long pass phrase) or running a script (which allows alerts, photos, erasure, boot looping, or potentially even something proximate to bricking via messing with nvram).
I'm actually quite curious what, if anything, Apple plans to do with Touch ID in the future because they've clearly left themselves some flexibility in the underlying system that I don't think they're presently using anywhere in iOS. Maybe they're more leaning towards features like "select a different payment system with a different finger" or "unlock and launch straight into a favorite app with different fingers", or even some form of multiuser access based on different finger prints, but if Apple decided to start implementing features against rubber-hose cryptanalysis in iOS 10 it'd genuinely be pretty exciting. I'm not aware of any mainstream consumer electronics even attempting anything like that yet, though if anyone has some existing/historical examples I'd really love to read about them.
I like your idea of the duress fingerprint since the police can demand that you supply a fingerprint to unlock a device (but can't demand a passphrase). If you use the wrong one then "Oops, I was so stressed out I forgot which fingerprint to use".
I really think it's unlikely that law enforcement will ever take an interest in my phone, yet I still like knowing that my data is my data.
There are cases where a judge can force you to supply a password.
I personally just don't use the tip of my thumb, so unless you knew that I would just try it 5 times and lock out touch id.
I would like to be able to shut down the phone when the risk of attacks/theft/loss is high, knowing that a high-entropy password protects it, but without having to enter it all the day.
I have fingerprint set up to unlock the screen - but at least once a day ill have to enter the passphrase and it wont accept fingerprint. It says something like "for additional security, please enter your passphrase" instead of "finger moved too fast" or whatever
Every reboot you have to use the passphrase to unlock the phone the first time.
I dont see any options for configuring the time period when it asks for the passphrase again though.
Sadly, it's not straightforward to make a remote reboot-phone button that's usable by the general public.
[0] IIRC, calling halt(8) from the shell didn't work, either.
It's only a poor choice if there's anything worth securing on the phone, and most people think that there's not, he destroyed his personal phone while leaving this phone intact.
In any case, most people unlock their phone dozens of times a day, perhaps hundreds of times a day (for some). So expecting users to use a secure passphrase as an unlock code is unreasonable. It seems that it would be better to have a 2 stage system -- if the phone hasn't been unlocked with the passcode in X hours (user configurable), then it has to be unlocked with the secure passphrase -- even if someone knows the passcode the phone can't be unlocked with it after that timer expires. And on reboot, only the passphrase should be accepted.
So someone that unlocks their phone frequently can use a simple passcode, but once the phone has been out of their possession for a few hours, only the passphrase can unlock it.