XPost: comp.mobile.android   
   From: marion@facts.com   
      
   UPDATE:   
   Tested on Samsung Galaxy A32-5G, Android 13   
   Google Play services (com.google.android.gms)   
   Version: 23.33.16 (190400-560149061) (233316044)   
      
   Observed permissions and current settings:   
   1. Body sensors: Don't allow   
   2. Call logs: Don't allow   
   3. Cameras: Don't allow   
   4. Contacts: Don't allow   
   5. Microphone: Don't allow   
   6. Location: Off   
   7. Music and audio: Don't allow   
   8. Nearby devices: Don't allow   
   9. Notifications: Off   
   10. Phone: Don't allow   
   11. Photos and videos: Don't allow   
   12. Physical activity: Allow (grayed out, apparently required by system)   
   13. SMS: Don't allow   
      
   Privacy impact:   
   - With almost all optional permissions denied, Google Play services cannot   
     directly access contacts, microphone, camera, location, call logs,   
     media or most sensors.   
   - Oddly, the one exception is Physical activity, which is apparently   
     required by the OS & cannot be revoked without breaking core functions.   
      
   At this point, I'm unsure about potential functional impacts:   
   - Push notifications may fail for apps using Firebase Cloud Messaging.   
   - Location-based features in apps may be inaccurate or unavailable.   
   - Apps using Google sign-in or account sync may not work.   
   - Casting, Bluetooth pairing and nearby device discovery may fail.   
   - Some background services & battery optimizations may behave differently.   
   - Failures may be silent (e.g., apps may stop syncing perhaps).   
      
   Monitoring:   
   - TrackerControl can check com.google.android.gms for activity   
   - Anything else?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)