nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug i found a workaround for my relay disco errors. i #logcatted and i kept seeing javaIO eof exceptions immediately after start. i do not know what triggered this but after seeing a few other errors relating to google tracking, etc.. i decided to try the fdroid release.

🎇🐡 it works.

so, apparently graphene only works with the fdroid version.. even though it almost works, something is causing cascade exception.

i will miss the translations, but this is nice i can connect again, this was driving me nuts 😂

Reply to this note

Please Login to reply.

Discussion

google play services maybe?

yes even though i run sandboxed google play services, somethings messed up. after seeing the logs i decided ewwww anyway. except for translate, thats gonna be tough to get used to.. may be worth debugging amethyst sandbox incompatibility for that. but the rest, eww.

Just checked my own logs. Can confirm, errors all over the place with sandboxed Google Play.

zapstore version works on GrapheneOS

there are two flavors of amethyst, the play one and the fdroid (degoogled) one.. does zapstore have both?

Isn't it pointless to server google play version from zapstore? If you need google play version, you have google services and thus google play store itself.

well, my new question is, do you have to install play version using Google play store and then it works? Unsure ... Obtainium gives you the choice which flavor of apk.

I didn't meant that exactly, however I often encounter issues with applications that expect GMS to be present. When they are fed something non-standard (like sandboxed version or MicroG), such applications behave poorly.

right, I'm realizing that now.. 🏴‍☠️