- Edited
Just solved the issue. There's a lot of permissions to play with to get Google Timeline and Google Find My Device to work. I consider the two questions in my original post solved (though there is a potential functionality bug described below that the devs might want to look into). Solution to question 2 in the original post:
Relevant settings:
- Under OS Sandboxed Google Play settings:
- Reroute location requests to OS is DISABLED
- Google location accuracy->improve location accuracy is on
- If there is a permission conflict a "potential issues" section will pop up with an explanation - Under Google Play Services app settings location permission is set to allow all the time and use precise location is enabled
- Under Google Play Services app settings nearby devices permission is set to allowed
- Under Google Maps app settings location permission is set to allowed all the time
- Open the Google Find My Device app, go to "Find My Device" settings and enable the service
- Open the Google Maps app, go to "Your Timeline" settings:
- Click the cloud icon to manage your timeline backups
- Click three dots then "Location & Privacy Settings" to enable BOTH location and timeline - Settings -> Location -> Location services and enable wi-fi and bluetooth scanning for more accuracy
-Allow background battery usage for Google Maps, Find My Device and Google Play services
An alternative is to enable "Reroute location requests" and disable Google Play services location permission (which the permission conflict alert described above will tell you about and the conflict is explained in the link below), but I found it to be much less reliable than the above set up. I got mostly "Can't reach device" errors with Google Find My Device. Maybe the devs should look into why their location request rerouting feature isn't working well with Google Find My Device. And are there any security advantages to using the Graphene OS location request rerouting feature over just giving Google permission?
Note changing some of these settings seems to disable your VPN. You may need to reenable your VPN after changing the settings to reestablish internet connectivity (assuming you used a VPN kill switch) before Google Timeline or Google Find My Device can find you.
I have not tested the above settings with Google Timeline yet as it takes time for data to be collected to verify it's working. I will update this post if I have any issues.
For more information about these settings, how they affect functionality and combinations you can use to prevent conflicts go here:
https://grapheneos.org/usage#sandboxed-google-play-configuration
If all else fails or you still don't want to use Google Services you can use Nulide's Find My Device app instead of Google which can be found on F-droid: https://f-droid.org/packages/de.nulide.findmydevice/
You can backup your location history to the app's public server (https://fmd.nulide.de/) and encrypt the backup with a password and user ID or use sms commands to get the location. It has much of the same functionality as Google Find My Device. Link to their privacy policy: https://fmd.nulide.de/ds.html