serenrodgers
Absolutely, I second that. Very, very important for Vanadium to be the viable default.

I would add also that after 10 wrong pin codes attempts the device wipes itself, or delete the encryption key.

    • export + import blocked numbers
    • assign sim card preference per contact. then i could drop custom dialer and sms app
    • call back missed calls using the sim on which the call arrived

    Here is a simple one - color invert all the GOS icons to match dark mode, for example; Phone app - dark background, white handset, Camera app - dark background, white camera and etc.

    If it's a wishlist...

    • A kind of quick setup for User Profiles. My idea would be to use GrapheneOS somewhat similar to Qubes, regularly setting up new Profiles for very limited tasks and deleting them afterwards. This is already possible, but could be made easier. For example, there could be multiple default profile types you can select to automatically have the settings configured like this.
    • Another hurdle currently is that while you can install apps into new User Profiles from the Owner profile, this doesn't do much if you have a setup where you pretty much don't use the owner profile at all and don't actually have any apps installed in it.
    • In fantasy land, where you have unlimited capacity, I'd love for you to provide more apps in "Apps". In practice, Obtainium and Accrescent projects are looking quite promising and F-Droid seems to also head into a better direction, so it would probably be a waste.
    • Dark/black/more beautiful themes/UI for the keyboard, calculator, clock, maybe more
    • A very very basic GOS notes app that's there by default
    • Security Keys as MFA for User Profiles
    • A way to avoid being fingerprinted through your background (question: does this currently only affect the home background, or is the lock screen a problem as well?)
    • And finally, a more extensive wiki/way of sharing knowledge with further scope. I consider the GOS team as some of the most knowledgeable people (surprise) on many infosec questions. GOS as a tool for targetted people that need the safety it provides might benefit everyone a lot by sharing more knowledge. Something like an official Blog that now and then comments on current events or provides easily accessible insight into what's being worked on, might be good. Communication generally could, imo, be improved upon.

    I want to add that this is not in any way to be understood as criticism. Graphene is an incredible product and its achievments are the reason expectations are that big:) Also, maybe those things don't make sense, I'm not a dev, pls don't judge me too hard:D

    Well, here are another three wishes:

    1. Full eSIM support that does not require Google Play Services
    2. Not one more app added! Please : )
    3. Update "Messages" to the latest API
      • [deleted]

      AlanZ Update "Messages" to the latest API

      Its better to just include another SMS app or at least ask user to download one on the device setup screen

        [deleted]
        Oh, for sure, if they can ditch it altogether, I am all for it.

        As I understand it, a GOS keyboard is on the roadmap (or at least a consideration). If so, I'd like to request that a key feature from

        https://github.com/rkkr/simple-keyboard

        ...(not to be confused w the talented, Tibor Kaputa's offering of the same name) be used: cursor space swipe. Currently, the stock kb requires swiping of the cursor on-screen itself. This is cumbersome and often inaccurate whereas swiping along the space key left or right keeps fingers down by the keys and allows for precise cursor movement.

        This feature alone is a workflow game-changer given the nature of kb use. If anyone here hasn't tried this or another kb with said feature, I'm confident you'll agree.

        A huge aside: thank you, devs and team GOS for the best OS I've ever used regardless of platform. Every time I use my phone, I'm reminded of the all the fantastic accomplishments that have been made here. GOS is truly a diamond in the rough.

        My two controversional wishes are:

        • Sandboxed microG (same as as sandboxed Play Services). DivestOS now has an unprivileged microG implementation. I think this is a good compromise if you want to stay as far away from Google as possible, but have some apps that need FCM for notifications. You could then install microG (rather than full Play Services that include many components you don't want) in a second profile together with those apps. And whatever DivestOS has done, it doesn't need signature spoofing or privileged extensions unless I'm misunderstand something.
        • Support for more phones. I know there's almost no phones available that allow relocking the bootloader (I think Fairphone and Shiftphone are the only ones?), but 1. I feel bad buying a Google phone and thereby supporting that evil company, 2. Pixels are not available in most countries, 3. if Google one day decides to not allow unlocking Pixels anymore (credible given their recent trajectory towards locking down everything e.g. WEI) or stops making Pixels altogether (not impossible given their track record of abandoning every project) then GOS needs a plan B.
          • [deleted]

          • Edited

          Elk9877 Sandboxed microG

          MicroG is both poorly made and poorly maintained; so It just doesn't make sense to allow even an unprivileged implementation of It. MicroG was also caught logging user's Google account password to device logs.

          Elk9877 DivestOS now has an unprivileged microG implementation.

          I asked its developer and he himself doesn't recommend It.

          Elk9877 I know there's almost no phones available that allow relocking the bootloader (I think Fairphone and Shiftphone are the only ones?)

          Just Verified boot support or third-party Operating systems won't do. The device at least needs to have proper security implemented at the hardware/firmware level with proper IOMMU isolation, and much more to be even considered for GrapheneOS.

          [deleted] Like what app? QKSMS was the most popular one, and the developer mysteriously disappeared for years, came back and said he's gonna keep working on it, then he disappeared mysteriously again.

          Partisan SMS is a fork with bleh security, where, surprise surprise, the developer mysteriously has disappeared
          Simple SMS is pretty meh
          Silence is abandonware
          ... that's it for FOSS SMS apps really.

            A "clear all data on exit" for Vanadium would be nice to have. It'd be nice to get rid of the incognito widget icon.

              • [deleted]

              Conjure6589 A "clear all data on exit" for Vanadium would be nice to have.

              That's a known feature to be implemented down the road.

              • [deleted]

              wuseman That's because they have no incentive to work on their apps.

              An SMS app which is mostly open source but the premium features are proprietary (so other people can't just compile from source to use them) would be a better choice.

              5 days later

              As for my current wish list, I'd ask for

              1. Ability to quickly switch profiles based on the pin code I enter. Yes, I know that multiple profiles can have the same PIN, but, for instance, if the user enables this feature, the OS could make sure my profiles will have different PINs. Or present a list of users on the profile's lock screen (also as an optional feature that can be disabled). This would make user switching way faster than it currently is.

              2. Per-profile location spoofing. Currently only the main user can "emulate" location, and this affects all other profiles. It would be VERY helpful if each profile can have an option to simulate location separately (if not on a per-app basis, which, I presume, is much more difficult to implement). For example, banking, dating or evening taxi apps do not necessarily need to know even my approximate location, but some of them refuse to work if not granted access.

              3. Ability to change TTLs of data packets when WiFi hotspot mode is enabled. Some cellular operators charge extra if the user uses mobile internet in the hotspot mode (even for his own devices). This is detected by the increased TTL in data packets comparing to normal smartphone traffic. AFAIK currently this can be adjusted only by rooting the phone.

              4. Perhaps an out-of-box app for sharing files between profiles. I am using Primitive SFTPD and it works for me, but for newer users it may be difficult to set up, furthermore AFAIK ftp directories cannot be mounted on GrapheneOS as normal directories, so other apps cannot use them, unless they explicitly support SFTP.

              FWIW I am a software developer and I could dedicate some time to implementing at least simpler asks, if the team needs help, as I love Graphene and use it a lot. If any of the existing developers could provide some guidance as to how certain features are preferred to be implemented and some help navigating the existing code base.

              • de0u replied to this.

                traveller Ability to change TTLs of data packets when WiFi hotspot mode is enabled. Some cellular operators charge extra if the user uses mobile internet in the hotspot mode (even for his own devices). This is detected by the increased TTL in data packets comparing to normal smartphone traffic. AFAIK currently this can be adjusted only by rooting the phone.

                TTL mismatch is an easy way to detect tethering, but not the only way.

                https://discuss.grapheneos.org/d/5683-tethering-is-being-detected-by-t-mobile/22

                It would arguably be more productive to add an option to run hotspot client traffic through an existing VPN connection. I think there may be an open GitHub issue.

                SpiderUser That's been brought up before and isn't going to happen. The throttling enforced by the security chip would prevent anyone from brute forcing a random 6 digit pin in a reasonable amount of time unless they had an exploit for it.

                In the senerio that they had an exploit they could clone the storage before they run out of attempts and try again as many times as they want. It only introduces the possibility of permanent data loss without actually adding any security.