Little bit of thermal throttling compared to other Strix boxes like Framework, but I do like that I could always take this setup on the go or repurpose these into individual dev machines if needed.
Hey folks,
There have been a few solutions over the years for distributing Android apps before they are ready for a major store like the Play Store. This includes Testflight, Firebase App Distribution, Microsoft App Center, and even the Play Store itself with its additions for Alpha and Beta testing. But a lot of these have either shut down or take quite a bit of setup to get up and running. We created Drebin451 as an alternative to all these. On the free tier, you get 1 GB of storage for your APKs, and you can share links to others and they can get notified of updates to your app.
And the whole stack (app and backend) is open source. https://github.com/Commit451/Drebin451
Feel free to give it a try, I have been using it to distribute and test my apps with friends and family for the past month and its made my workflows a lot easier to deal with. With the impending doom of Google making it much harder to sideload apps, we will work to keep the flow with Drebin451 easy and simple as much as we can.
tl;dr ARM Android build-tools binaries here: https://github.com/Commit451/android-arm-build-tools
Hey folks! Some months ago, I was trying to set up my Raspberry Pi to be a CI/build server for my Android projects. I realized that Google for whatever reason does not ship ARM binaries for their Android build-tools. I found a project https://github.com/termux/android-build-tools which defines how you can pull down and manually build with cmake and other tools. But, it does not provide "out of the box" binaries that you can use for ARM devices.
So, the project here will scan for new tags each day and build the latest build-tools for ARM whenever Google updates/releases the AOSP source and the project finds a corresponding tag that it can build.
Let me know if you run into any issues! I have only had the chance to test this on the Raspberry Pi and have not yet tried it on a Chromebook, Ampere, etc, so please comment if you find any issues with those.
Was driving me crazy when testing mine out, every single FX type will output to Phones, just as you'd expect, but the DELAY FX specifically only applies to OUTPUT and not PHONES. Threw me off and I thought I had a defective unit until I put my headphones on OUTPUT and realized that DELAY was processing correctly there, just not on PHONES. Would be a good one to fix!