Heya,
Just addressing some of your points to hopefully alleviate questions or problems.
Switching between the profiles is quite a hassle, and I'm unsure if I will put up with that for long term. Although it is a bit like having 3 phones without the need to carry 3 bricks around. What is most annoying with switching profiles is the fact that the fingerprint works really shitty. It's slow, and I most of the time need 3-4 attempts to get it working. And what is really the worst, that after each failed attempt, it immediately asks for the PIN code to enter, instead of just letting you try again. Compared to my previous Huawei, the experience is really like day and night. The Huawei was fast and reliable, while the Pixel (or is it Graphene OS?) is really bad.
The fingerprint reader isn’t tremendous on the Pixel 7/Pro, but its sensitivity can be increased by increasing the screen sensitivity in the settings:
Settings -> Display -> Increase touch sensitivity
Charging is slow, and battery life is sort of similar, if not slightly worse with the new phone. And you would have thought that over time they improve.
The Pixel 7 Pro limits the charging wattage to 23W, in contrast to the Huawei P30 Pro’s 40W.
One other glitch is swiping horizontally. While most apps are kinda ok, Wechat is particularly bad. Sometimes I really can't swipe left/right, and most of the time I need to do it very carefully, swiping absolutely horizontal (90°), from an precise point or it won't work. Again, I'm not sure whether that is a hardware issue, Graphene OS or the app.
If it varies per-app, it is likely that it’s a bug with the app itself. I’m not experiencing any issues on my Pixel 7 regarding this.
One thing that is also a bit annoying, is the lack of shared memory to access certain photos/files from one profile to the other. I use Session with "Note to Self", but it is kinda cumbersome to do. Yet I understand the necessity and benefit of having separate data silos.
This is by design. Are you certain that your use case necessitates the use of multiple profiles? What are you attempting to separate? I only ask this as it would be a shame if the annoyance you’re experiencing with the lack of convenience outweighs the benefit you’re getting from it. The profiles feature is able to separate apps and prevent them from enumerating any other apps outside of its own profile as well as having its own separate storage. Is this benefit a factor in your decision? For some people’s purposes with regards to daily usage, it’s totally okay to just put most things in one profile and be done with it. For those who are, for example, concerned about Google Services sharing the same space as their usual apps or who want apps that have optional dependencies on it (like Signal using websockets for notifications unless Google Services is present, in which case they will use this for notification delivery), they can separate the apps, and any apps not in the same profile as GSF will not be able to rely on their features should they be able to do so. They can also ‘end’ profile sessions to put the apps and data at rest if needed.
The (Google) camera app sometimes acts up and doesn't take photos, despite me pressing multiple times. There's a big lag, or so much that I miss the best snap-shot. I should try a bit more the stock camera app, but I do like the additional functionality of the Google cam app. While the photos are pretty good, missing out on some snapshots makes it again a bit of a mixed experience.
A number of users have noted experiencing long processing times from previously shot photos when using Google Camera, especially with Portrait mode. Is this a mode you use?
Option to display the content of incoming SMS in the notification bubble. When receiving verification codes, it is always required to open the Messaging app and switching back, while in most cases all you need is a code and could continue straight ahead
Is this in regards to separate profiles? On the owner profile, this is the default behavior. On non-owner profiles, the app must be accessed instead.
Bitwarden filling in in Vanadium doesn't work (initially it did, but then suddenly stopped, although Bitwarden has all the permissions)
This is a bug with the Bitwarden app. Bitwarden, like some other password manager apps, hardcodes the browser package IDs for which it enables autofill. Vanadium recently changed its app id to app.vanadium.browser, from org.chromium.chrome. As a result, Bitwarden needs to add Vanadium to its list. A pull request exists for this exact problem, it just needs to be merged: https://github.com/bitwarden/mobile/pull/2199
Looks like it was approved recently.
Casting the screen to my TV doesn't work at all (previously it also did work in some apps, but somehow that stopped working too)
More info may be needed. Which apps are you attempting to cast with?
Not being able to add a background (withoug the image being totally distorted) is a bit annoying, as it would help to separate the different profiles a bit
This is an upstream AOSP bug.
https://github.com/GrapheneOS/os-issue-tracker/issues/1461
It will need to be fixed by the AOSP team.
Sometimes my phone seems to be like frozen for a few seconds and busy with something. Didn't experience that with my Huawei
Hard to say whether or not this is a GrapheneOS issue, an AOSP issue, or a hardware issue as of current. Do you know if this occurs on stock Android on this device, also?
Having to swipe down twice to switch the user is also one swipe to many, as this is a very regular task. Some simple short-cut/gesture would be very welcome
When getting a notification from a different profile, it takes up to 3 tabs to get to the "Go to profile" shortcut. Why can't I just tab on the notification itself?
These behaviours are how profiles are currently implemented. More features for making the profiles easier to switch to and from are planned, but it requires developer work, resources, and for community members to step up to help make such things happen.
Having to swipe down twice to adjust the brightness (instead of a single swipe) is a minor nuissance as well. Especially since I have the feeling that the screen is a bit on the dark side in general (compared to my old Huawei). And I also got the impression the image is a bit on the yellow side and not as "white" as my previous one.
Getting the camera open quickly is also less comfortable than previously, as the double pressing of the button is not ideal. Although that might also have to do with the case I am using. But the software solution to swipe up from the lower right corner on my Huawei was very simple and fast(er).
I'm also missing the few shortcuts on the locked screen for recording a note, the calculator, the timer and the torch when swiping up on the locked screen. That feature was very practical on my old phone
These are all default behaviours of the AOSP, on which GrapheneOS is currently based. Huawei is a massive corporation with plenty of resources and developers to add such features to their own distribution of Android and maintain them. Unfortunately, GrapheneOS doesn’t have such resources readily available. This isn’t to say that it could not potentially develop comparable features in the future, but it would need resources and dev work that cannot afford to be wasted. It also requires community members to step up and help with the project.
Hope this helps