ndk VS AndroidStudioBenchmark

Android folks are thinking about using WASM for NDK, with compilation to native code on the PlayStore.

https://github.com/android/ndk/issues/1771

We have looked into what work would be required to support Rust in the NDK, but even if we did it (which is not certain!) it's a lot of work. Today, we're mainly investing in the lower-level work (compiler changes for some of the complexity around linkage on android, etc.). Feel free to follow along / make suggestions here: https://github.com/android/ndk/issues/1742

If it used to work then you probably just need to reinstall(/recompile) it with something like pip3 install ocrmypdf --force. Most likely issue happens because some library it links against had a major upgrade, which caused the mentioned symbol to disappear (could also be a variant of https://github.com/android/ndk/issues/1614, but seems unlikely)

I have an M1. I compile Android apps in Android Studio a lot. For a small Android app without many bells and whistles M1 compiles fast (even faster than my Ubuntu laptop). However some Android apps I compile have some C/C++ code compiled with the NDK and accessed via JNI - and which now have to compile on an ARM chip - and that is a rigmarole currently ( https://github.com/android/ndk/issues/1299 ) to the extent that I am just sticking with Ubuntu on x86-64 until ARM is fully supported in Android Studio full release (not some alpha/canary version).

Also, I have never used the MacOS Active Trader Pro app, but I downloaded it to my M1 and it did not work, and online old Macbook users say it works and people with M1s say it has problems on M1.

So my experience is look to see what apps support M1 and ARM. I can tell you that Rosetta does not work for everything.

Apps were not working, and I put Rosetta in, and now some apps work and some don't. So this is another thing to look into.

> The new architecture also doesn't make much difference. Stuff just works, though homebrew needs to be told it's not on Intel anymore (terraform breaks weirdly if you don't do this). There seem to be plenty of M1 versions for your generic coder stuff.

I bought an MBP with M1 recently. The main reason was to run video conferencing software, which so far it has done well at. That it is a powerful machine yet small and lightweight was a plus for it as well - its easy portability.

I bought it for some secondary reasons, but those have not panned out yet. In mid-February I tried to compile a program with the release version of Android Studio, the project had NDK (C language) components. Even with Rosetta it was not working ( https://github.com/android/ndk/issues/1299 ). Google said they had M1 support coming down in Android Studio canary version and other fixes coming out as well in the future. I'm not in a rush, but it compiles on my Ubuntu box and on Intel-based Macs, but not M1 out of the box yet (not without having to fiddle around to do it any how).

For my Android projects that were fully Java/Kotlin based, the M1 did compile fast though.

Also, Fidelity said they have an application called Active Trader Pro that works on Macs. It's not something I ever used, or that I would probably use regularly, but I decided to check it out. It would not work for me either, and support forums made mention of difficulties it has on M1.

One thing I haven't tried yet is loading Unity 3d and futzing around with it, hopefully when I have the time to do that it will be working.

Still happy with my purchase as it's working for my primary need, and more Android Studio support seems to be coming, and it is not a big rush to me. It's probably good that Apple is pulling software into a world where it supports ARM (kind of weird Android code primarily targets ARM devices, yet has trouble compiling on ARM devices). I had heard about how fast things compile on it, but it was even faster than I expected. So all in all I like it, and hopefully more software will be supported as time goes on.

> And ARM compatibility issues not really helping

There were two things I wanted to try on my MBP w/ M1 - compiling an Android app that has some C code, and also to run Fidelity's Active Trader Pro program (not that I would use it that actively). I also installed the Rosetta stuff it prompted for.

The Active Trader Pro program would not run.

In Android Studio, the production version can not compile with CMake as it can on Intel-based Macs yet ( https://github.com/android/ndk/issues/1299 ). They say there is stuff in the beta/alpha/canary branches where it is working, but I am not in a rush and will wait for that to make its way into production.

> It’s good, fast

Yes, I did see the speed, especially with a normal Kotlin/Java Android Studio compile, on 16GB RAM.

Could you open an issue at github.com/termux/termux-packages? Miiight be a variant of https://github.com/android/ndk/issues/1614, but we haven't seen that for golang packages before

NDK development is not supported, but my understanding is that everything else is good to go.

I saw and tried hp zbook fury 17 g7 by myself, with i7 10750H, 64ram, 1tb ssd nvme, 1tb grafics. It stays cool and quiet doing cpu stress test for 10 min. Starting to be hearable to ears only when gpu added to test. It the same in action as thinkpad p17, but much cooler and quieter. I am now choosing between zbook and dell xps 17. I dont know why, but the same specs xps is 1.5x faster then mob workstations in my test: https://github.com/yozhik/AndroidStudioBenchmark/blob/master/README.md

I think you can send your own results to the author and they will be included in the sheet. Here is the link to the repo: https://github.com/yozhik/AndroidStudioBenchmark

Hi! I'm android developer and I want to help software developers choose the fastest machine for work. To do this I have prepeared a big test project to test Android Studio real life performance. Here is the repository with code and step-by-step guide: https://github.com/yozhik/AndroidStudioBenchmark/blob/master/README.md It has already more than 30 results and would be cool if someone could also add more new results. Thanks.