Testing with the staging release
Perhaps the backup now button on the firmware loader popup should be disabled if the user is not signed in to Google. I was not signed into google when I selected the backup now. I was presented the backup popup, selected backup and the operation silently failed.
I would suggest that the "Backup Now" button be enabled, but that a check is done to verify that the user is signed into google before continuing. If the user is not signed into google, then an error dialog presented to tell the user that they need to sign into google before attempting a backup.
I'd further suggest that the same behavior be implemented for the straight backup/restore operation, too. I realize that the backup dialog does say that you need to sign into google, but disabling the buttons is not that great. I think warning them when they try to initiate the backup is a better mechanism.
Testing with the staging release
Perhaps the backup now button on the firmware loader popup should be disabled if the user is not signed in to Google. I was not signed into google when I selected the backup now. I was presented the backup popup, selected backup and the operation silently failed.
I would suggest that the "Backup Now" button be enabled, but that a check is done to verify that the user is signed into google before continuing. If the user is not signed into google, then an error dialog presented to tell the user that they need to sign into google before attempting a backup.
I'd further suggest that the same behavior be implemented for the straight backup/restore operation, too. I realize that the backup dialog does say that you need to sign into google, but disabling the buttons is not that great. I think warning them when they try to initiate the backup is a better mechanism.