Best User profile strategy for privacy

mmobder

oci3o It also helps by disabling all permissions for the app

enable before using the app and then disable after each use? WoW, not my level of endangerment.

mmobder

Again, with all those complications (non-working Alarms etc) and UX inconveniences, it looks like the optimal for most (including me) could be owner without Google Play Services, Private Space with Play services (including Auto, but w/o network) for banking/etc apps keeping it at rest when needed.
I anyway manually disable background use and background data for foreground-only user-installed apps. Though I acknowledge it's closer to the edge of "paranoid")
I haven't understood yet in full if Work profile can also be a valid option for 3rd "scope" (dunno if it will be deprecated soon, is it really the "isolation", etc).

Because for me, creating 3rd profile just for Android Auto without a strong reasoning is beyond understanding.

harp

mmobder non-working Alarms etc

What do you mean by 'non-working Alarms'? Alarm-clock? Works flawless in secondary profiles. Notifications pushed from owner to 2nd profile? Works fine: If allowed, owner-notifications are pushed to 2nd profile. Only in some rare cases there's the issue of getting notifications twice, e.g. SMS- and call-notifications: If calls and SMS are allowed in 2nd profile you'll get their notifications directly within this profile, if pushing notifications from owner is allowed, you'll also get these notifications pushed from owner.

Or what else do you mean?

mmobder

harp Alarm-clock? Works flawless in secondary profiles

I don't think so, Alarms don't go off in non-owner in BFU state that is relatively frequent because of nightly reboots (either scheduled or upgrades), so one have to figure out to set Alarms primarily in Owner for them to work reliably without thinking of reboots.
https://discuss.grapheneos.org/d/4027-alarm-clock-is-silent-bfu/12

I've heard of custom sounds not working in some cases either with owner, but haven't checked if that's (still) valid/fixed etc as I don't care - I don't use custom sounds anyway.

mmobder

harp Notifications pushed from owner to 2nd profile?

I'm sorry, I have no idea where you pulled it from - can't find anything relevant in my msg.

harp

mmobder Alarms don't go off in non-owner in BFU state that is relatively frequent because of nightly reboots

Ok, in BFU, I could'nt imagine that someone would expect that. When the device reboots to BFU, the 2nd profile will be killed by/like "end session" of course, the profile is completely turned of. You have to imagine it as if each user profile were a seperate device. So if the 2nd profile session has ended, the "device" (the 2nd profile) is completely turned of. Its the same as if the whole physical device is turned off: in that case you won't get any alarm, if set in owner or anywhere else.

mmobder I'm sorry, I have no idea where you pulled it from - can't find anything relevant in my msg.

I couldn't too. I was just thinking about what you might mean apart from the alarm clock function.

So of course, in that case you either have to take care the device won't reboot before the alarm or you need to set it in owner (and maybe also in the 2nd profile). I think that's not a big deal.

There are some much more annoying restrictions in secondary profiles, e.g. that there's absolutely no way to use hotspot/tethering via Bluetooth in secondary profiles and after a reboot the mobile data background usage setting of every app is set back to enabled. The need to change to owner for en-/disabling mobile data is also not comfortable, but you can deal with it.

There are further restrictions in comfort but these are much less annoying than the ones mentioned before.

mmobder

harp Ok, in BFU, I could'nt imagine that someone would expect that.

You've probably missed " so one have to figure out to set Alarms primarily in Owner for them to work reliably without thinking of reboots" in my relatively short answer.
What you say doesn't make Alarms UX less inconvenient, as someone who is using non-owner as primary has to keep alarms in owner.

mmobder

harp There are some much more annoying restrictions in secondary profiles, e.g. that there's absolutely no way to use hotspot/tethering via Bluetooth in secondary profiles

yep, I try to keep those aspects here https://discuss.grapheneos.org/d/16754-pls-help-to-collect-inputs-only-that-influence-users-scheme-setup-in-a15/26

mmobder

harp and after a reboot the mobile data background usage setting of every app is set back to enabled. The need to change to owner for en-/disabling mobile data is also not comfortable, but you can deal with it.

wow, haven't noticed it, will check as I try to keep those disabled for front-only apps, thank you!
was it discussed somewhere as search returns adjacent but not exactly this issue?

harp

mmobder You've probably missed " so one have to figure out..."

No, I definitely got that. I was just explaining, why I didn't think of someone could expect setting alarms in 2nd profiles will be triggered in BFU state after a reboot - cause I wasn't aware you could mean this BFU-situation. Before my question you just wrote about "like expectedly failing alarms in non-owner". So just reading that, I couldn't imagine what alarm should fail in non-owner because it doesn't. An alarm set in non-owner won't be triggered in owner or BFU state but that's not a "fail" in non-owner. That's why I clarified how 2nd profiles work and a 2nd profile's ended session is like a turned off device.

mmobder What you say doesn't make Alarms UX less inconvenient, as someone who is using non-owner as primary has to keep alarms in owner.

Yes, I'm also aware of that inconvenience, just wanted to say there are other inconvenient issues, but not such a big deal but others much more annoying.

And again: my initial question was caused by wondering what you meant. After your clarification I wanted not only explain why I couldn't think of it myself but also explain for those who weren't aware of that yet, why this 2nd profile behavior is inherent in it's function.

newbie24689

For those of us who do not need to receive night time calls, would a better approach to avoiding nighttime updates and reboots be to set airplane mode at night?
For years this was not an issue with me 'til recently, when I awoke to find my updated phone in owner and my user alarm having failed to sound - this despite that automatic reboot had been disabled in owner settings.
Given the importance of getting those morning alarms, I'm starting to think that counting on an automatic restart of owner after updating is not best!?

harp

newbie24689 For those of us who do not need to receive night time calls, would a better approach to avoiding nighttime updates and reboots be to set airplane mode at night?

There are much more approaches if you want avoid nighttime updates and/or reboots caused by this: you can just disable the automatic reboot after update function. The update will be loaded but only a notification triggered to reboot manually. Or you can just turn of wifi and mobile data, so no updates will be even loaded but you can still receive calls and SMS.

« Previous Page