P
PixtTraveler

  • Joined Aug 7, 2023
  • Graffiti7675 I mistakenly referred to you in my post, but I meant the other poster that asked about the open-source app ( @notahuman ) -- my bad!

    de0u As for adding to github, I don't think that the aforementioned issue is the right one, since that's mainly talking about Google Play Services mirroring behavior with Google Services Framework and not about secondary profiles; so it would be better raised as a new issue. Also, I don't have a github account at the moment! :)

    But even before posting to Github, it would be good to confirm or deny if this is actually a GrapheneOS issue -- it may actually be an upstream bug in the Android code, in which case there is no "issue" with GrapheneOS at all. The only way to confirm this is for someone with the stock OS to try this on a secondary profile. Anyone in the community?

  • de0u

    Hi, I'm not sure how to make the reproduction of steps more clear, apart from the clarification I made in my follow-up post (which led @Graffiti7675 to think I was talking about going inside a particular app). I can put them all together here:

    to replicate this behavior:

    • start a secondary user session
    • Go to phone's System Settings, i.e. the gear icon for the OS, not a settings section from within an app
    • then go to the Apps section (third from the top within system settings)
    • then "See all XX apps", then pick any app (could be third-party installed, OS-installed app, etc), or more than one app as you would like
    • go to the data usage section of the select app's system settings and toggle "Background data" to off
    • end the secondary user session
    • restart the device
    • after reboot, enter the owner profile, and then enter the secondary user profile again
    • go to the apps you had disabled "Background data" for, and you find that the toggle will be back to on

    As for the motivation for turning off background data for an app, I'm just describing a feature of Android that has been available for several years now. The reasons a user may want to disable background data are varied, but mostly to conserve data charges and increase battery life. One can find a number of articles describing this feature online (e.g. Tom's Guide, Android Authority, among others).

    As I mentioned above, this may be a general upstream issue of Android for secondary profiles -- I simply don't have another Pixel with stock OS to check whether it is a bug upstream or unique to GrapheneOS.

    • de0u replied to this.
    • notahuman My original description may not have been clear. In my list of steps, the second step entails the following:

      • Go to phone's System Settings, i.e. the gear icon for the OS, not a settings section from within an app
      • then go to the Apps section (third from the top within system settings)
      • then "See all XX apps", then pick any app

      As @Graffiti7675 mentions, the issue is with any app, which includes both open and closed-source apps, and also includes GrapheneOS pre-installed apps too.

    • Hi,

      While disabling background data for an app works perfectly in the Owner profile, in secondary profiles this does not work as expected. Any app that you disable background data for is automatically granted the ability again upon restarting the device.

      You can replicate it as follows:

      • start a secondary user session
      • go to any app under Settings / Apps / see all apps
      • go to the data usage section of the app and toggle "Background data" to off
      • end the secondary user session
      • restart the device
      • enter the secondary user again
      • go to the app and the "Background data" toggle will be back to on

      I have the latest version 2024071600 installed and tested this on a variety of apps with the same result. I don't have stock OS Pixel to test to check if this is also an upstream problem.

    • Unfortunately, it seems Android has made it difficult to do this after Android v9 without the device being rooted. See post here on StackExchange.

      However, if anyone else has figured it out, would be happy to hear!

    • other8026

      I am able to type in a couple of different languages, though Greek is not one of them unfortunately! But I did happen to notice that not all languages are supported in the default spell checker when I had been playing with settings versus Gboard.

      In the v2023123000, the release notes say "add new implementation of multi-locale spell checking support", but it still looks like the same list of languages as before on my phone at least. Looking further back in time, it looks like the last time any mention of languages for the keyboard was from March 2022, v2022032715 release notes: "GrapheneOS Keyboard: enable spellchecking for Czech and Dutch languages".

      This may be a low priority for the developers, as they are probably capturing a good chunk of users with the languages offered. If they are working on adding languages, I would also imagine more widely spoken languages would take precedence (e.g. hindi?).

      The reality is that the AOSP keyboard isn't the greatest unfortunately, as I guess Google stopped adding features on it after making Gboard the standard keyboard.

    • temp_user1999
      In the case of Gboard, by default it only comes with English spellcheck. In order to use foreign languages, you need to have network access enabled, switch to the particular language you would like to use, and then Gboard will download the dictionary of that language in the background. It should be pretty quick on a normal internet connection. If you afterwards disable the network connection, it will still work. Of course, if there are updates to the spell checker, it will not get updated without internet access (I'm not sure how often, if ever, dictionaries are updated by Gboard).

      other8026
      In the case of the GrapheneOS stock keyboard, I don't think Greek is a supported language for spell check, regardless of the latest GrapheneOS release (2023103100, which is what I have installed). If you go to Settings \ System \ Keyboard \ Spell Checker, and select "Languages", Greek doesn't show up as a language when you have the system "Spell Checker" selected as the Default spell checker. On this latest Android v14 release of 2023103100, only the following languages appear on the list in my phone:
      English US, English UK, French, German, Italian, Spanish Russian, Portuguese, Dutch, Czech
      @other8026 does your phone show any other languages after the latest update?

      • PixtTraveler
        update
        I tried various suggestions above, though none worked. After several reboots, eventually the issue seems to have just resolved itself. OS not updated at all.

      • This problem exists for me on a Pixel 6 with the latest build.

        I found another post about swiping problems, but this current post actually directly describes my problem as well.

        For me this started today (27 Oct), and just started randomly, not having rebooted, and my OS was already updated a couple of days ago to the latest build (2023102300). Rebooting did not solve anything. Swipe up doesn't work to get to the home screen. Swipe down to get all the way down is "difficult", and swiping notifications off is almost impossible. There is considerable lag, especially when typing.

        As for differentiation between Owner and secondary profiles, this seems to be the same for me across profiles. Marila's suggestion of deactivating Wifi before changing profile didn't have any effect for me.

        I have noticed that upon rebooting (owner profile), once, at the very beginning swiping up worked again for a short while, and then stopped working again.

        I also note that upon rebooting, I am getting the system notification about optimizing some apps after update (2 out of 2, or 3 out of 3), even though the system was updated days ago.

        • I'm having similar issues as of today (27 Oct). This problem just started randomly, not having rebooted, and my OS was already updated a couple of days ago to the latest build (2023102300). I tried rebooting to no avail. Swipe up doesn't work to get to the home screen. Swipe down to get all the way down is "difficult", and swiping notifications off is almost impossible.

          This applies on both Owner and secondary profiles

        • Hb1hf this is helpful! Has this behavior ever reappeared for you?

          For me, it seems to just kick off randomly, about once a day or every two days, I'll see the green light flashing constantly, will invariably see the Settings App as the requester. Once I end the profile session, and go back in after, it won't start asking for location again (until the next day, or whatever it is that is triggering it).

          • treequell

            I do not actively use Wi-Fi Direct. I see that Wi-Fi Direct exists in my phone (under "Network preferences"), but I have never actually tried to use it. I don't think there is a way to turn if off? Also, with regard to Wi-Fi Direct, in Sandboxed Google Play settings, I have "Device visibility" set to off.

          • itsjpb Thanks for confirming @itsjpb , I appreciate it!

            I guess there's nothing to be done for now then, until Google addresses it

          • treequell

            I can confirm that I am not using Google for location requests -- "Reroute location requests to the OS" is ON.

          • Hi,

            I notice every now and then the green location indicator coming constantly when I'm not doing anything. Upon going into the Privacy Dashboard, I see it is the system "Settings app" asking for the location.

            When I say "constantly" I mean, every few minutes (e.g. 14x per hour). Note that I am NOT inside the Settings app when these location requests are taking place. If I reboot the phone, then the constant location requests stop (for at least a period, until the next time it starts happening again).

            For the record, when I see the recent location requests, none of the installed or system apps show the location access at the times of the Settings app requesting it. And while I do have Sandboxed Google Play installed, I have denied that location access.

            My question is -- could some other app, that does have location permission (be it system or installed app) causing the request to get routed via the Settings app? My main concern is whether some third-party app is somehow circumventing the location access restriction.

            For reference, I have a Pixel 6 running the latest stable release v2023080800.

          • treequell

            Hi, I don't have access to a Pixel w/o GrapheneOS -- can you confirm that this is an AOSP problem?

            • Hi there,

              When you select and copy/cut text, the text gets places in a little "pop-up editor bubble", which you can click to edit the copied text before using/sharing it. This is a pretty useful feature I find. I don't know what this feature is called, but this is what it looks like for clarity:
              image
              [EDIT: I though I could include an an image here but it won't show up; however, upon further searching I discovered the actual name of this feature "clipboard editor overlay", and can see an image of it on XDA Developers: https://www.xda-developers.com/android-13-beta-1-clipboard-editor-overlay/ ]

              This works in GrapheneOS exactly as it does in the stock OS, at least with the Owner profile.

              The problem I is that, at least for me, secondary profiles lack this "pop-up editor" functionality.

              To test whether this could be from some customizations, I created a brand new secondary user profile that is completely fresh and empty -- no changes to any settings, no app installations, no customizations. Upon copying text, the "pop-up editor" will not appear.

              Has anyone else experienced this? Is there a workaround?

              (For reference, I have a Pixel 6 running the latest OS as of this post, v2023080800)

              Thanks for any help!

              • GrapheneOS DoctorGo v6ak de0u
                Hi all, I was able to pin down the problematic element, and I thought I would post it here for the sake of reference since it had already been discussed here and couldn't find it elsewhere, rather than open a new posting.

                Subsequent to my last post ( PixtTraveler ), I updated the OS to 13/TQA.230805.001/2023080800.
                I needed to do a factory reset for another reason, so it was an opportune time to discover where this problem was coming from. (FYI I did the reset via the phone Reset Options "Erase all data (factory reset)"). The problem of course was not there after the factory reset.

                Upon changing various settings, I came across the element that for me seems to have been causing the issue -- ImsService.

                The SIM lock boot-loop problem begins if you make changes to the locations permissions of ImsService, with either:

                • you disable "precise location" for its location permission
                • you disallow the location permission for ImsService completely

                In either of those scenarios, I am able to replicate the problem. And then re-enabling ImsService's location permissions, the problem goes away completely.

                I hope this helps others in case their problem was caused by the same issue, so as to avoid any potential factory reset!