Hi,
I recently bought a Pixel Fold for the sole purpose of installing /e/os on it. I was surprised to see that there don’t seem to be a lot of people who’ve done this, as there are very few entries on this forum about this Phone lol. So far most things have gone off without a hitch though and the few things that irked me I’ve been able to work around somewhat.
One thing that hasn’t worked that does irk me is that even though one Google Account seems to have made it over the hurdle somehow, it’s specifically not the one I really need and I can’t seem to add any other ones. I always get that error of “Sorry…there was a problem communicating with Google servers.”.
I did some research and found out about this whole SafetyNet/Play Integrity thing and wonder if thats what’s causing it.
microg’s selftest completes successfully, yet YASNAC and all the other checkers give me a 7: NETWORK_ERROR.
My research led me to the assumption that this may be because its a community build and so I can’t lock the bootloader? But that can’t be where this ends, there HAS to be a workaround for all of this, right?
Like ih8sn or something, which my research has led me to, but I’m not sure if I should install that or not, like if thats safe to do or will fix the problem.
Maybe it’s because the /e/os version of microg is a little outdated? Looking up the versions on github revealed that there’s a new version out and the latest pre-release version mentions something about “fixing google logins”. I know I can’t just update manually, so maybe this is something to put into the next /e/os patch?
I don’t know and my research alone can only take me so far. This is a community after all, so I thought I’d ask about it here.
Thank you to whoever reads this and I hope you have a fantastic weekend!
Yes, I’m aware of that. We don’t need to get into my reasons as to why I’d like to add a google account over microg, the issue I’ve brought up is that it very much is a feature that the software supports and is failing midway. Even if I can’t add this google account, fine, I guess I can work around it in the browser for the few instances that I still need it while I’m unable to shake Google completely for the time being. There’s workarounds for most things that way and convenience is a gateway to leaving backdoors, it’s why I wanted to get away from stock OSes and install a privacy-focused one in the first place.
I failed to get into this much in the original post, i did mention it in the title, my healthcare provider has an app that crashes on startup and my research on why this is happening has linked back to microg and this safetynet/play integrity verification failing.
If there’s no fix to it, there’s no fix to it, but since, like I’ve mentioned in the original post, there’s very little documentation or posts otherwise mentioning the pixel fold, I wanted to make one here detailing my experiences and inquiring about a problem I’ve encountered. And if there’s one thing that I think is undeniable in all of this it’s that the version of microg that comes with the community build of /e/os is a bit outdated atm and since murena keeps control of microg updates by signing their own signature off on it, I can’t just update microg myself, at least this is what I’ve encountered as I’ve researched this.
Also, I don’t wanna be rude, but I’m not a big fan of this kind of rhetoric. I like to think that we all deep down want the same thing from tech, to work smoothly and in our best interests. There’s plenty of stupidity out in the world. I don’t think you need to make me feel dumb for asking questions, especially when I’m not just screaming my problems into the ether, demanding somebody come and fix it without giving much details or having tried to find a cause.
I don’t want to fight, just saying.
Micro-G versions tend to include bleeding edge. /e/OS makes testing here “almost impossible”. To try this I suggest you would need to start from a different base. It can always be said that /e/ “lags” a bit but I suggest that /e/ mostly considers “tested and stable” as the aim. [1]
Play Integrity is the modern test. At expert level these guys are even saying that Google are fighting the validation apps [2] on a daily basis. The keywords in attempting full Play Intergity compliance are keystore or TrickyStore.
There was some resistance to /e/ including in a15
Version 15
com.android.healthconnect.controller
One might use Settings > Search facility for Health Controller. Potentially you might try to get your app to “network”.
For instance you might have two health monitor apps on your device you can get to share data on device (I feel this was the aim of its inclusion). However the Google way would be to network this data back to their servers.
[1] Both your posts are interesting in enquiring about the general position. At any expert level one could always argue with my over simplified position. A more specific question about your particular Healthcare app may get a more useful response.
Unfortunately, its not that kind of app. It’s the german healthcare provider Barmer, and their app allows you to send in sick notices, book appointments, stuff like that. There’s no entry for the app inside the Health Connect Permission Manager and even if it would have an entry like that, it probably can’t due to crashing at startup.
I’ve also come across TrickyStore in my research, it’s linked to Magisk afaik, right? I didn’t find much information on being able to integrate Magisk alongside /e/os and I didn’t necessarily want to brick my new phone that early on as I’m still in the process of properly migrating everything and there’s not much documentation out there.
