Adding my vote with a concrete, fully tested case:
I'm running Ubuntu Touch on a Volla Phone Plinius, with Android apps through Waydroid/LineageOS (no Google components at all, Aurora Store as the app source). On this setup, Proton Mail works flawlessly, while the Lumo app crashes at startup with the "check that Google Play is enabled" message.
This inconsistency within Proton's own ecosystem is what surprises me most: the privacy argument that makes me choose Proton over Google's offerings is exactly the reason I can't use Lumo natively. Users of GrapheneOS and CalyxOS report the same behavior.
The web app at lumo.proton.me works well as a workaround, but a native app without Play Services dependency — or even just an official APK/F-Droid release of the current build minus the Play Services check — would be enough.
The irony is easy to point out: I'm literally chatting with Lumo right now, but only through a browser, because its own Android app refuses to run on my de-Googled device.
Max Mirat
Adding my vote with a concrete, fully tested case:
I'm running Ubuntu Touch on a Volla Phone Plinius, with Android apps through Waydroid/LineageOS (no Google components at all, Aurora Store as the app source). On this setup, Proton Mail works flawlessly, while the Lumo app crashes at startup with the "check that Google Play is enabled" message.
This inconsistency within Proton's own ecosystem is what surprises me most: the privacy argument that makes me choose Proton over Google's offerings is exactly the reason I can't use Lumo natively. Users of GrapheneOS and CalyxOS report the same behavior.
The web app at lumo.proton.me works well as a workaround, but a native app without Play Services dependency — or even just an official APK/F-Droid release of the current build minus the Play Services check — would be enough.
The irony is easy to point out: I'm literally chatting with Lumo right now, but only through a browser, because its own Android app refuses to run on my de-Googled device.