Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
I use https://github.com/nirajsanghvi/docker-gphotos-sync, which is a fork of Jake Wharton's Docker wrapper with an extra option baked in to prevent redownloading previously downloaded files. It relies on the gphotos-cdp tool which uses the Chrome Dev Protocol to headlessly browse the Google Photos site and download your photos one by one. The reason for this, assuming you store your photos in Google Photos, is it's one of the only ways to get your photos in their original quality and also retain EXIF information (Google Takeout loses the EXIF info).
A warning though, it can be quite finicky to setup, particularly with obtaining your account cookie for the first run. In the past it's taken me several attempts before success. However, once it's running it's pretty reliable with an occasional stall requiring a container restart (there's issues for this on the parent repos, but they were complicated problems to solve so they're still open, and occasionally needing to restart the container when the healthcheck fails once every couple of months hasn't been too bad).