I also used sms backup and it's good. Signal has its own backup and restore process I used. Contacts I sync with my email (mailbox). Personally, I prefer to not just restore apps via a third party.
Roland
- 17 Sep
- Joined Jul 5, 2022
- Edited
Newby with GrapheneOS (But really living it) uses Garmin Forerunner 945 with connect on a playstore less profile. Only when making routes I use a second connect app on my seconden profile WITH sandboxed profile.
GrapheneOS version 2022070800 released: https://grapheneos.org/releases#2022070800.
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS version 2022070600 released: https://grapheneos.org/releases#2022070600.
See the linked release notes for a summary of the improvements over the previous release.
When i think the translation is finished I'll post it here for you to review it. It would be important to maintain it. We could use a dedicated channel in matrix for translators.
I don't have the time to keep it updated. It is important to keep it as close as possible to the original
For calendaring I use the SimpleMobileTools calendar. It will import/export ICS files. If you want to sync data with a server, then something like DAVx5 is required as well as an appropriate server (e.g. some webmail services support CalDAV, or setting up a CalDAV server yourself, though this would be too much for non-technical users).
I've never used a "wallet" app, as I just use Signal's "Note to Self" to retain important information.
Geometric weather is currently my choice but it'll depend on where your wheather data shall come from.
For car navigation, there is magic earth which is even better than google maps if osm data is vailable. For a general mal app, there's osmand which is more feature rich than organicmaps. Organic maps is great but for anyone serious about maps it's too limited - like any other map.
I have no idea about public transportation, but there's probably an app for that.- Edited
kokolem This is also true for work profiles.
Not in the same way user profiles do. By their very nature, user profiles provide totally different workspaces and GrapheneOS provides the option to put the entire profile at rest with an "End session" button. Encryption keys are protected by their lock method like you would expect. You don't get that flexibility with work profiles.
In fact, each user profile has its own Weaver slot on the secure element. Compared to stock OS, GrapheneOS raises the number of user profiles from 4 to 16. That's one of the ways (including the upcoming cross-profile notifications feature) GrapheneOS aims to make user profiles more convenient and the de facto choice for compartmentalization.
By design, work profiles are also made to allow communication between apps on the user profile and the nested work profile. That can't happen with apps on different user profiles (even the with the mutually consented IPC that takes place in a user profile) unless they use network (which can be revoked by the network permission, including localhost).
(Also to be clear, the app sandbox always applies whether you use work/user profiles or not. These profiles are not substitutes for the app sandbox.)
kokolem This is the only disadvantage of work profiles I see, although it's quite a big one.
Yeah, because the device manager app has ownership over the data of the work profile it manages, and not yourself, fundamentally. You're trusting a third-party app with considerable permissions over that data. Work profiles were designed with BYOD deployments (bring your own device) in mind.
For these reasons, we often recommend user profiles as the preferred way to create isolated workspaces. I hope I was able to give a satisfying enough answer to explain why.
External documentation to learn more about user/work profiles:
https://source.android.com/devices/tech/admin/multi-user
https://source.android.com/devices/tech/admin/managed-profiles- Edited
Battery Share
Starting from the 2022062200 release of GrapheneOS, a cool feature has been implemented - reverse wireless charging for devices supporting it. This includes Pixel 5, 6, and 6 Pro.
To turn on Battery Share:
1. Open your phone's Settings app.
2. Tap Battery and then Battery Share.
Tip: You can also add Battery Share to your Quick Settings.Battery Share turns off when your phone:
- Starts wireless charging, like when on a Pixel Stand.
- Doesn’t notice that it’s charging another device after 30 seconds.
- Knows the receiving device is fully charged.
- Reaches a high temperature.
- Senses power transmission isn’t going well due to poor placement, a thick case, or other issues.
- Turns on Battery Saver.