S
seanld444

  • Mar 16, 2023
  • Joined Mar 7, 2023
  • I just discovered the Storage Scopes feature (thank you, Graphene team) and it fits exactly what I want to do with my non-FOSS apps that I unfortunately kind of just need.

    For the sake of keeping it unrepetitive, ~ means /storage/emulated/0 (or whatever Graphene's user home directory path is).

    I created the directory ~/ProprietarySandboxOfDoom which I gave Slack access to only. I assume the point of Storage Scopes is that it should now only be able to find files within that directory, or its internal directory. However, when I select a file to send to someone in Slack, it can send files from any directory under ~ which entirely defeats the purpose of limiting it to that one directory.

    Am I missing a step? I force-closed Slack and relaunched it, to see if the restricted storage access needed a relaunch to be applied. But it's still able to send files from any directory.

    Any ideas?

    • matchboxbananasynergy

      That's the source for the equalizer and camera apps respectively. You have to build them from source. And they're buried amongst the other 2.5k (?!?!) repositories on LineageOS's GitHub. But if you use the search bar, you can probably find the repositories for the apps you want.

    • You

      fight4freedom

      1. https://www.f-droid.org/en/packages/dummydomain.yetanothercallblocker/
      2. Every contacts app I've used has a way to export your contacts to a .vcf file, or import in from one. That may be what you want. Check your app's settings.
      3. Same thing here. I use QKSMS, and it has a section in the side bar to export them. But this one may be less standardized and intercompatible than the contacts. Other than that, I don't have a solid answer for this one. Sorry.
    • Blastoidea reading up, that sounds like it describes exactly this situation. Thanks. For some reason none of my search terms turned up with "pixel binning" when I was trying to figure this out on my own. Glad to know it's not intentionally handicapped.

    • I've noticed in the specs for the Pixel 7 Pro, the camera is supposedly 50 MP. When taking pictures with the GOS Camera, I'd get ~13 MP photos. Same with Open Camera. So then I figured maybe those didn't have the proper proprietary code to use the full capabilities of the camera, so I reluctantly enabled sandboxed Google Play and installed Google Camera. I was surprised when even that produced ~13 MP photos at "full" resolution.

      Is this me misunderstanding an important distinction between the described resolution, and the actual functional resolution of the hardware itself? Is there some setting or configuration I'm missing? Are there proprietary blobs that need to be bundled into the OS for any of the three to take max resolution photos?