-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Zanetti wrote on 28/07/15 18:12:
...
The incoming call and the wifi password entry are handled through
the notification system. Seems like the Bluetooth case would be
just the same, no?
...
That incoming calls and wi-fi password entry are handled through the
notification system is a mistake. It means that without changing the
notification system itself, the incoming call dialog can't be
full-screen, or display the stored photo of the contact calling you[1];
that third-party VoIP apps, if they existed, couldn't do anything
equivalent to the incoming call dialog; that the wi-fi auth dialog
can't do anything to prevent you from submitting a password that can't
possibly be correct[2]; that the dialog is incapable of showing
connection progress, and instead just disappears only to reappear
seconds later if there was an error[3]; that even then, it doesn't
display an error message[4]; and that you can't connect to an
enterprise network without opening System Settings[5], because the
notification system can't show dialogs that contain multiple text
fields and/or certificate pickers.
Repeating this mistake with Bluetooth would result in similar problems
in validating PINs, displaying pairing progress, and presenting
pairing errors.
