I am hoping for some guidance on how to best address disabling the multi-user functionality altogether so that a guest user/session cannot be initiated. Quick Internet search indicates it's as simple as merely editing the build.prop file in /system as below:

Multi Users

fw.max_users=1
fw.show_multiuserui=0
fw.show_hidden_users=0
fw.power_user_switcher=0

My conundrum is how to best access the build.prop file. The tried and trued suggestions don't seem to apply to GrapheneOS build.

Any nudge in the right direction is greatly appreciated.

Thanks in advance.

    coffee-black Hello, as far as I am aware, the guest session function has to be explicitely enabled in the settings of the owner profile, which means that it is not possible to activate a guest session unless the setting is turned on.

        stupidcreature
        You are 100% correct. I am wanting to remove the ability to toggle it on and off. This phone is being utilized by my son and we are trying our best to lock it down as much as possible. The Achilles heel of all the various parental control app packages on the market today is that all an end user has to do to bypass is simply fire up a guest session and they are off to the races with a clean profile with no apps installed, including the parental controls, proxies, and filtered dns settings. One way folks have addressed this in the android world is to set max users to 1 and bury the options in settings. This is achieved by manipulating/adjusting the build.prop file as illustrated in my original post.

            coffee-black

            there's a very simple answer to this, don't give your son access to the owner profile. Set up a secondary profile just for him and he won't be able to set up new guest profiles.

                I was going to test that out in the AM. I was suspecting you could still fire up a guest regardless. If it is indeed an owner only function we are golden. I genuinely appreciate the response.

                gk7ncklxlts99w1
                I gave this a quick run this morning and it does appear to do the trick. I also ran a adb fix-up that eliminates the user icon from the app drawer pull-down thus reducing the temptation to look around. But per your suggestion, having my son's account as a user and me as the owner does indeed eliminate the guest user option.

                Thanks again gk7ncklxlts99w1 for the nudge!

                • de0u replied to this.

                    coffee-black Note that if the device reboots (or the battery runs flat) the owner must unlock the device before a secondary profile can be used.

                        de0u

                        We saw that when testing out various scenarios this AM. While not ideal for 100% of the time it is more than acceptable 99.999% of the time. He should not be needing to reboot for any 'unforeseen' reasons. In the event he runs the battery dead and gets caught having to have a parent to login this will hopefully prove to be a good motivator to manage his usage as well as his power. Two things as a new user he currently contends with.