I have installed the app Google Health Connect, but it wont start because it needs an encrypted phone. I use Xperia 10 II dual sim. But according to my settings my phone is already encrypted. I guess there is something with the communication between Sailfish and Android apps informing about encruption, that is wrong here.
Is there anything else I need to do to get Google Health Connect working?
Should it be possible for Android apps to properly identify that the phone is encrypted, or is this not implemented altogether?
There are plenty of Android roms for X10II - why bother with Sailfish OS in that usecase of yours?!
Sailfish is for humans, who seek to be google-free.
I have zero experience with Gooogle Healt Connect, but as you are trying to use it inside AAS container, app don’t have any information from native phone side. Meaning it can’t check weather phone truly is encrypted or not. For example android apps can’t really check if bootloader is locked or not in the native side. This would need to be faked inside the AAS container. I haven’t before heard about this kind of requirement from app, so might not be so high priority.
Just to check, do you have MicroG setup and have you allowed all possible things there?
Thank you for a kind and productive and useful reply. I have activated MicroG, but I don’t know about other settings, besides just allowing it to run. I am not a developer, so I might not have access to other settings. But it seems logical as you say, that an Android app can not get that information from the system from within it’s container.
As for now I cannot make use of that app anyway, since the Polar H10 heart sensor is not supported. It uses Bluetooth LE. I am just testing many things at the moment, to see what works and what doesn’t.
Bluetooth support for AAS should be coming with next releases, so that might be solved with that.
I don’t remember if there is instruction somewhere, but if you launch app from app drawer named “MicroG Settings” you will see additional google services you can allow. For example “Google device registration”, “Cloud messaging” etc. If I were you, I would go all of them through and see if that helps in this case. Also the first “Self-Check” gives you option to allow various things, you can try to check every box and see if that has any help.
I just also noticed that if you go to the phone settings → Apps → MicroG Settings → App permissions → There is permission “Body sensors”, which I haven’t allowed for example. Maybe that can be allowed too?
That sound very promising! I will await the next release and see how it goes.
I think I have the wrong version or phone for that (Xperia 10 II), because I do not have such an app, and I can also not find it on Jolla Store or Aurora. I only have one setting and that is to turn MicroG on or off. Maybe the MicroG Settings app is something that will be included in the next release. I just have to wait and see.
No, I had not! Thank you for showing me how to do it. Now it is done, a lot of the permissions activated. Still same problem with Health not seeing that the phone is encrypted and Polar not getting access to the H10 through the Bluetooth LE. I will just wait and see what the next upgrade brings. At least now, I have the MicroG set up properly.