When you code #android #apps, there is no need to get the #sdk binaries from google. They come with a proprietary license that you would need to accept.
But the #sdk source code is #floss.
You can build the whole #sdk on your own with #docker, using ready recipes:
1. Clone the repo from https://gitlab.com/android-rebuilds/auto
2. go into the desired sdk folder
3. check the few .sh files if everything is set up according to your needs
4. run "make" and relax
@Billie, I remember upgrading to Debian Sid simply because it has the SDK in the repo
Yes that is true, but most of the time it is a little bit outdated. For a long time, it was stuck at api level 23 (#android 6), now it luckily is at least 28 (#android 9).
I now compiled the sdk api level 29 from source (#android 10).
This was kind of an experiment, I am lucky that I can compile the sdk on my own, so that I do not need to rely on any binaries.
@resist1984, I used Anbox which was a pain to set up and get running, but it was fully libre and yo can find a ASOP image to use with it. It’s basically a container for Android so it’s much easier on resources than the emulator embedded in Android Studio, but it is alpha quality at best and cannot run all apps. I used it only for a course at school and the mainline Linux mobile (e.g. Librem 5 or PinePhone) community uses it sometimes too.
Maybe @Billie@social.tchncs.deI will have more options for you.
@huy_ngo @cnx I must come clean with my use for an AOS emulator: it's not dev work, but actually to sandbox untrusted apps from others. E.g. I wouldn't trust my bank not to monitor my location & other details, so an emulator gives control over inputs. OTOH, I should say that this fails with banking apps that somehow detect that they are running on a VM.
