Two profiles: a "naked" Owner profile and my personal profile.
The "naked" profile offers some additional security and benefits:
1. "Emergency Mode" I have minimum services running to use the device as an operational phone with texting when I'm not using my personal profile.
2. Security. It gives me an additional layer of security because I enter a Password to access the phone (Owner profile), and when I switch to my user profile, I have another Password to open the profile. I also setup Fingerprint access to the user profile that is not present on the Owner profile.
3. Warrant Required. If stopped by the police and my personal profile is open and its biometric enabled, I hold the power button then select "End Session," and the phone reverts to the "naked" owner profile, which has nothing of interest. If the police demand to see the contents of my phone, however unlikely, they'd have to get a warrant for my password since the knowledge is in my head whereas a fingerprint can be used without a warrant. I supposed I could also restart the phone, but leaving it on and ending my user profile session is good enough.
4. Battery Life. The battery life should be outstanding as there's next to nothing running on the phone. I'm currently doing an experiment to see how long the phone will last.
In the Owner profile ("naked profile"), I only have the base apps that come with GrapheneOS, and I disabled many of them:
- Disabled Apps in the "naked" profile: Apps, Auditor, Calculator, Camera, Contacts, Gallery, PDF Viewer, Vanadium
- Running Apps in the "naked" profile: Clock, Files, Messaging, Phone, and Settings
PROFILE ISSUE: SMS
The ONLY issue I've run into with a user profile is how AOSP treats SMS messaging between the profiles. Basically, ALL SMS is transferred through the owner profile to the current user profile (when enabled). Here's some bad news:
- SMS only transfers from the Owner profile to the User profile through the Messaging app, which must be enabled and default for both profiles in order for the user profile to receive SMS.
- SMS messages are treated as a normal notification, not an SMS notification. I know this because, in the user profile, I set a special notification in the Messaging app, but the Default Notification sound, Pixie Dust, sounds instead for every SMS I receive.
What's in my user profile? Why everything else! I initialized Google Play Store services, but did not log in, so apps could use Firebase Cloud Messaging (FCM) for push messages because myParish and the Toyota app require these in order to run.