X000X
Exactly - replacement for a work profile. Please, read my comment again incl. your quote :)

    14 days later

    Oggyo what is the definition of "work profile" isn't a work profile any profile but the owner profile?

      fid02 Thank you but I'm on Android 15. Got it even updated recently, the wizard was mentioning Private Space and even when opening the menu from the wizard itself, it's not there. Build BP1A.250305.019.

      Very few sub reddit are talking about it. And of course not many pages on google search... But a journalist wrote about crashing issues with private space, I guess that's the reason why this partial removal.

        cybermattic https://www.reddit.com/r/pixel_phones/comments/1g4id3b/anyone_not_seeing_private_spaces/#:~:text=Here%20is%20the%20answer.,device%2C%20you%20lose%20the%20feature.

        Why are you citing yourself?

        cybermattic https://www.reddit.com/r/GooglePixel/comments/1g5ejq1/cant_find_private_space_in_a15/

        Random Redditors not being able to find Private Space isn't proof that Private Space is being discontinued or even partially removed.

        cybermattic Very few sub reddit are talking about it. And of course not many pages on google search...

        So can you share any authoritative sources that say this is happening?

        cybermattic I guess that's the reason why this partial removal.

        So far I see zero evidence of this happening. Android 15 QPR2 was released earlier this month and GrapheneOS's release based on QPR2 was released shortly after. I still see Private Space even on a phone that has been factory reset yesterday.

          other8026 What is the benefit for me to lie about meaningless such thing? Explain to me please.
          I'm citing myself to highlight the silence on this issue. Google Support itself acknowledged it. But eh oh, believe what you want.
          I'm not saying they are discontinuing it, you read what you want to read, I say they are not enabling it on all devices even if on Android 15, and I don't know the reason why.

            cybermattic What is the benefit for me to lie about meaningless such thing?

            Maybe I missed the part of the thread where somebody suggested lying. Can you point it out?

            cybermattic I'm citing myself to highlight the silence on this issue. Google Support itself acknowledged it.

            Even if one person working for Google (or working for a Google contractor) said that, that doesn't make it true, because people sometimes make mistakes (and it's even possible that the Google support person said something that was misinterpreted). Generally if "the Pixel engineering team" decides to add or remove a feature, Google announces this publicly (including on the Android developer web site) and it's covered widely in the press.

            cybermattic I'm not saying they are discontinuing it, you read what you want to read, I say they are not enabling it on all devices even if on Android 15, and I don't know the reason why.

            But earlier in this thread this text occurs, apparently posted by your account:

            cybermattic The Pixel engineering team decided to remove the Private Space feature. As of now, no Pixel device using Android 14 and higher supports it, you reinstall your device, you lose the feature.

            It is difficult for me to understand how to read "decided to remove the Private Space feature" and "no Pixel device using Android 14 and higher supports it" as meaning "not enabling it on all devices".

            cybermattic But eh oh, believe what you want.

            It seems multiple possibilities are being discussed:

            1. "No Pixel device using Android 14 and higher supports it" (seems very incorrect!)
            2. Google is "not enabling it on all devices" (seems as if user testimony supporting this is quite thin at best!)
            3. A Google support person told you something that is incorrect (this happens!)
            4. A Google support person told you something that was misinterpreted

            If what one Google support person says seems much more trustworthy than other possible sources, perhaps (as suggested on February 4 de0u) it might be good to ask a second Google support person whether "The Pixel engineering team decided to remove the Private Space feature" is or isn't accurate.

            cybermattic What is the benefit for me to lie about meaningless such thing? Explain to me please.

            I'm not accusing you of lying, but as a moderator for this forum, I kind of have to follow up when a community member is saying something that doesn't seem to be correct.

            This is what you said in your first post about this:

            cybermattic The Pixel engineering team decided to remove the Private Space feature.

            It appears that you were saying that this applies to all devices, not just some of them...

            Also, note the post you were responding to (lordiont) about an issue lordiont was having with Private Space. As far as I can tell, you were hypothesizing that the errors they were getting were somehow related to Private Space being "removed." I could be interpreting it wrong, though. I'm just guessing based on what was being responded to and what you said followed by "Maybe related?"

            Since lordiont had GrapheneOS on their phone at the time (I assume this because they said they have "Sandboxed Google Play" installed, which is a GrapheneOS thing), it wouldn't be Google that would be "removing" Private Space from phones for some unknown reason, it would be GrapheneOS, which I don't believe is happening.

            cybermattic I'm not saying they are discontinuing it, you read what you want to read, I say they are not enabling it on all devices even if on Android 15, and I don't know the reason why.

            That's not what you said originally, but if that's the case, then I would also be curious as to why this is happening. My best guess is Private Space not showing up for some people is a result of a bug.

            cybermattic Google Support itself acknowledged it.

            cybermattic they are not enabling it on all devices even if on Android 15, and I don't know the reason why.

            Maybe the support person was confused? I don't know much about other OSes, but I gather that other OSes may not support the feature yet? I believe it has something to do with them needing to add support for Private Space into their launchers, but I could be mistaken. If I'm correct, maybe they were confused and were talking about other devices, not Pixels?

              other8026 The support person might have been confused, yet that's what is happening to few people using Pixel and the right Android versions. But, I still have this device with me, some screenshots are worth more than long talks.
              menu
              build number

              • de0u replied to this.

                cybermattic But, I still have this device with me, some screenshots are worth more than long talks.

                Those screenshots appear consistent with what would be visible in a secondary user profile (as opposed to the owner profile).

                  de0u I know what you mean. I'm in the owner profile, no user profile.

                  According to google's private space documentation I should be able to take any app currently installed and install it in my private space: https://support.google.com/android/answer/15341885?hl=en (See the section "Install an app in private space"). This doesn't seem to be possible on GrapheneOS though, or at least it doesn't work thew way they suggest in that article. What is the recommended way to install existing apps in the private space? Or is this not possible?

                  EDIT: For posterity I've copied the relevant portion of the article below. The "touch and hold an app" part is the part that doesn't seem to work. This article is linked at the bottom of the private space settings menu.

                  Install an app in private space

                  You can install apps in private space, when it’s unlocked.

                  In “All Apps:”
                  Touch and hold an app.
                  Tap Install app in Private space.
                  To complete the installation, follow instructions on the installer app.
                  The new instance of the app is installed. The previous instance isn’t copied or modified.

                  de0u I found the issue just now! It turns out you must have less than 4 users on the device to be allowed using Private Space. From this documentation, I just assumed, I quote "You can’t use private space when: Your device has more than 4 users or profiles." I guess the guest is counted as one even if not used. Or it's "more than or equal 4". I delete 1 user, rebooted and "Private Space" was there!

                    cybermattic I found the issue just now! It turns out you must have less than 4 users on the device to be allowed using Private Space.

                    Woah! That is quite a finding.

                    In fact, I encourage you to file this as a bug on the GrapheneOS issue tracker. I suspect the four-user limit is an accidental (mistaken) inheritance from upstream, based on: https://grapheneos.org/features#more-user-profiles

                    If you don't have a GitHub account and would like me to file the issue on your behalf, let me know. If you do file, be sure to reference this discussion thread (suggested link: https://discuss.grapheneos.org/d/16670/216).

                      de0u No it's all good on GOS. I was experiencing this on stock android not GOS. I mentioned it here a few weeks ago just because I was believing Private Space wasn't stable. Otherwise when using GOS with the same device it was working just fine, even with more than 4 users.

                      • de0u replied to this.

                        cybermattic No it's all good on GOS. I was experiencing this on stock android not GOS.

                        Oh, I see. Private Space is a profile, so if a device is "full" in terms of the number of profiles it would make sense that it wouldn't allow creation of Private Space.