title: Android M permission revocation - protecting a service with a "dangerous" permission
body: <p>I have app A which exposes a service through an AIDL and app B which binds to and invokes methods on that service. App A defines a custom permission with "dangerous" protectionLevel which is used to guard the service and is claimed by app B.</p>
  
  <p>Does Android M provide the user the ability to revoke custom dangerous permissions via settings or does this apply to only stock dangerous permissions?</p>
  
  <p>If custom dangerous permissions are revocable, what would happen if the user revoked the custom dangerous permission from App B while App B was bound to App A? Would Android immediately kill the binding resulting in App B receiving an onServiceDisconnected callback, or is the dangerous permission only enforced when the binding initially occurs?</p>