The iodéOS Premium subscription gives access to 2 simultaneous connections. I realized that in the case of multiuser configuration on my phone (in order to compartmentalize my different use cases), this implies that I have to connect the premium account for each user. In my use case (a general user + a “private” user and “work” user, each “user” being actually myself in different situations), only two of my local phone “user” can be connected to the premium (connecting a third one automatically disconnecting one of the other two).
Is it a desired functionality — i.e. “connect up to 2 iodé phones simultaneously” actually meaning to be “up to 2 connections” rather than “up to 2 physical phones”? Or is it a mere (undesirable?) side effect of how the connection limit is implemented (with no possibility to distinguish the situation “2 users from the same phone” from “2 different phones”)?
I believe you should see any changes to the iodé app (graphical user-level) are applied to the underlying iodé blocker (system level), so are effectively applied to all users on the device.
But, this is certainly confusing when dealing with the multiple “user-level” accounts scenario as apps from the other accounts won’t be shown to you, I need to get re-confirmation on how this can be accomplished. The intention is that you can have it on 2 separate devices so this may be an issue we haven’t yet sorted out correctly (I recall some discussion of it before with the team but am still a bit unclear as you may be seeing from my reply )
Oh, I see. Thank you for your answer. I checked, and indeed, configuring one app in the iodé blocker from the “top level” user gets its configuration “propagated” to the underlying user with no activated subscription for the app. So it somehow solves (partially) the problem.
But I would have never guessed that it is how this is working… I understand that the user “containerization” is probable difficult to deal with, but I hope there would be a better/cleaner solution. I do not know much concerning Android, but is there a way for an app to determine if it is at a “top level” user, or if it is a “secondary” user (inside a container/service?)? In that case, trying to register iodéOS app from a secondary user should at least open a warning explaining the issue. This wouldn’t solve anything, but at least give the right information at the right time.
The remaining problem is that different user may (and actually, are likely to) use different apps. So in the present situation, the only workarounds are 1) install all apps for the primary user, from where all are configured (simple, but need to duplicate many apps, and to have some back-and-forth configuration between users) 2) keep the primary user registered at all time, and use the “second device” login for the secondary users, only one at the time being able to be connected (not ideal neither, as it implies to connect/disconnect the secondary user at each configurations).
Of course, the only good solution would be to be able to have the iodéOS registered once and for all, for all users of a physical phone, but I do not know if it is feasible, technically speaking. If the app configurations can be somehow “propagated” from one user to another, can the registered status be also propagated in a similar way ?
Note: I hypothesized that this “container” view of multiple user in Android is correct, but I don’t really know how it is working. My observation was that 1) there is a clear distinction between the “top” (first) user and “secondary” user, as only the “top” user can have access to the “developer options”; and 2) when looking at the running services from developer options, each secondary user appear as separated services.
)