Now that android Auto is added, what is the next best feature to port?

someone1223

In my opinion, please port adaptive charging and battery. This really helps out a lot on older pixel. Followed by Now playing. I think then this OS will be a serious contender even for normies.

I hope given we managed to make even android auto work these 2 should be relatively easy.

[deleted]

someone1223

I do appreciate what you and the other developers have done so far. Thanks

I vote for finishing projects before starting something new. Content blocking for Vanadium and Duress are two that I can recall. Perhaps there are others.

[deleted]

someone1223 we managed to make even android auto work

I misunderstood.

mmmm

I think the most important feature would be some kind of scope to prevent/limit/mitigate inter-app communication.

dc32f0cfe84def651e0e

mmmm Also: widevine fingerprinting mitigation.

DeletedUser28

mmmm

Yes, and specifically for Play Services. Most of my apps works fine, including notifications, without Play Services. Some lack the notifications if Play Services are not installed. The only option is to have a second profile with those naughty apps + Play Services. If it were possible to limit communication with (and detection of) Play Services to these few apps that would be even better.

jroddev

mmmm

Block Inter-App: This! I have some profiles that exist because I don't want the apps in them talking to other apps I have installed. If I could install an app that thinks its in isolation I could probably install in a more common profile and reduce my total number of profiles. Some kind of Intent blocking perhaps?
Prevent Background: The other reason I have these apps in a separate profile is that I want to guarantee they aren't running when not in the foreground (block services/daemon). Though I installed something the other day and got a "Let app always run in the background?" popup (deny), so maybe this is already implemented? I haven't seen it with any other apps but it would be good if someone could confirm.
More permission toggles. When I look at an app on Aurora Store it shows some apps with having 60+ permissions, some of which are ridiculous. They don't all appear in the permissions page. Maybe that's because the app hasn't requested them yet?
PWA sandboxing and always private browsing. The problem I have is that if I use private browsing then I need to re-login every time I launch the PWA. So I have disabled the 'always private' option and just launch incognito tabs whenever I am browsing direct in Vanadium. This has the problem that if I click on a link in another app then it is launch in a non-incognito tab.
The other problem with PWAs is that they are not sandboxed from each other. If I have 2 PWAs their cookies are in the same cookie jar.
If I'm in a Discord PWA and I click on a LinkedIn link it will direct me to a logged in LinkedIn page with credentials from my separate PWA.

Just a few thoughts

someone1223

[deleted] I do appreciate what you

when did it sound that I am a dev? This is awkward. I just wanted to start a discussion, sort of an idea pool

LazyT

How about basics like localization and reliable backup/restore?

other8026

Just to be clear, someone1223 is not a developer for GrapheneOS.

Based on other responses in this thread so far, I'm not sure if everyone was aware of that.

I also don't want to imply, nor do I think, that anyone intended this kind of confusion.

Sorry for the awkward post.

Moving on... It's true that Android Auto is a big feature for GrapheneOS. When I started using GrapheneOS, it looked like Android Auto was never going to happen. Very impressive what they can do!

As for other features that were mentioned here, I'm not sure if they're on the project's To Do list. There are other features that are coming soon, many of which I think a lot of people in our community will be excited about.

someone1223

other8026 Just to be clear, someone1223 is not a developer for GrapheneOS.

other8026 Based on other responses in this thread so far, I'm not sure if everyone was aware of that.

did I made it look like that?

Eirikr70

I think an operational backup system would be nice, but I leave it to the devs to establish the priorities.

RRZishe

someone1223 I don't think anyone thought that you are pretending to be a dev, he probably just wanted to make sure that no one mistakes you for one.

other8026

someone1223 Like I said, I just wanted to make it clear.

If you want to talk privately, I have a number of ways to contact me in my bio.

jefdgbd

I think easy data transfer from the stock os would be really useful for people new to custom roms.

someone1223

jefdgbd I don't think that is possible, as unlocking bootloader clears all data in phone.

RRZishe

someone1223 I think he means from a different physical phone, like via network or something.

[deleted]

There was a high demand for Android Auto among GrapheneOS users.

However, when it comes to adding new features, I think they only consider adding new features if they provide significant privacy/ security improvements for the operating system.

On a personal note, I am eager to see the App Communication scopes in GrapheneOS.

RRZishe

[deleted] same here

Trena

jroddev PWA sandboxing

That seems strange that this is not already a feature. I was under the impression that tabs were sandboxed from each other, one would assume that pwa’s would be as well.

DeletedUser28

jroddev The other problem with PWAs is that they are not sandboxed from each other. If I have 2 PWAs their cookies are in the same cookie jar.
If I'm in a Discord PWA and I click on a LinkedIn link it will direct me to a logged in LinkedIn page with credentials from my separate PWA.

I think this might work in Firefox. They separate third-party cookies.

treequell

jroddev PWA sandboxing and always private browsing. The problem I have is that if I use private browsing then I need to re-login every time I launch the PWA. So I have disabled the 'always private' option and just launch incognito tabs whenever I am browsing direct in Vanadium. This has the problem that if I click on a link in another app then it is launch in a non-incognito tab.
The other problem with PWAs is that they are not sandboxed from each other. If I have 2 PWAs their cookies are in the same cookie jar.
If I'm in a Discord PWA and I click on a LinkedIn link it will direct me to a logged in LinkedIn page with credentials from my separate PWA.

You misunderstand how sandboxing and cookies work in Vanadium and even in Android more generally. PWAs are sandboxed in the same way as any other website in Vanadium. You can disable third party cookies in Vanadium settings.

All that is happening here is that the webpage in Discord is redirecting you to LinkedIn because you clicked a link that opens a link in LinkedIn, the same as opening a link on a website.

Discord can't read the cookies for LinkedIn, and LinkedIn can't read the cookies for Discord, that's not how things work.