Would GOS ever allow phenotype DB editing for advanced users?

eggy

I realize this is a long shot, but it feels pretty crappy to me how we all pay for a pixel phone, but are not able to use any of the pixel exclusive software features. As I understand, GMS maintains a sqlite DB of phone feature flags in the phenotype.db that affects Google app functionality. I imagine it can tell that GOS is not a Google-certified OS and, as such, does not enable any of the phenotype flags for pixel exclusive features. As GOS provides a way to install GMS, I wonder if it could provide some way for advanced users to opt-in to be able to edit the phenotype.db? As it stands now, this file gets installed into a directory which requires root to access. I'd prefer not to root my phone and am wondering if the GOS devs would allow for some way (I don't know how) for phenotype editing without root?

DeletedUser29

eggy it feels pretty crappy to me how we all pay for a pixel phone, but are not able to use any of the pixel exclusive software features.

I don't know what features you're talking about but -- making an (un)educated guess -- it sounds like those probably rely on code specific to Google's own version Android. GrapheneOS is based and built from AOSP directly and most likely doesn't have that code.

eggy As it stands now, this file gets installed into a directory which requires root to access. I'd prefer not to root my phone and am wondering if the GOS devs would allow for some way (I don't know how) for phenotype editing without root?

As for this, I doubt it. Root and GrapheneOS aren't compatible since it compromises the security.

But essentially I think you're looking at this the wrong way. You're not (or shouldn't be) buying a Pixel for Googles software gimmicks -- you're buying a Pixel for its hardware so that you can get the GrapheneOS software features.

pratyush

eggy

NO, we can not deal with the maintenance burden caused by the user modified gms flags.

other8026

I don't speak for the developers and I'm not involved in decision making in any way, so keep this in mind...

I doubt they would support this. Android intentionally makes it so users cannot access private storage for apps. If GrapheneOS permits messing with app-private storage for one app, then why not another or another? I feel like it cannot even be considered. That's just my opinion.

I feel like it's not a good idea from the project's perspective. A feature like this would only benefit a small number of GrapheneOS users. It also has nothing to do with privacy or security so it's not something that the project would normally work on.

Again (and yes, I'm repeating myself to make it very clear), these are just my personal thoughts.