THtharen·Oct 14, 2026Submission
AOSP Source Releases Are So Late Developers Disassemble Libraries to Report Bugs
510 points · Open discussionandroid
ndk
Mobile & Desktop2015–2026
android / ndk
ndk
The Android Native Development Kit
6Distinct people
10Mentions
0Explicit recommenders
2.3KGitHub stars
What to know before exploring
What it is
The Android Native Development Kit
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year10 dated mentions
Observed mentions: 2015-12-21 22:03:33 UTC to 2026-10-14 06:18:01 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
10 sourcesAndroid folks are thinking about using WASM for NDK, with compilation to native code on the PlayStore.
https://github.com/android/ndk/issues/1771
In CheerpJ 3.0: a JVM replacement in HTML5 and WASM to run Java on modern browsersI 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
Read the rest
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.
(Side point - my work laptop is not an M1 and was force updated to 11.6.2 a few months ago. Now when the screen is unused for a few minutes and the computer sleeps or hibernates or whatever, I can't log back in any more half the time and have to shut down and reboot)
> 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 two months ago. 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
Read the rest
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.
In Linux Developer Laptops: Dell's Precision 5500 series reigns supreme (2019)No need for that.
https://github.com/android/ndk/wiki/Changelog-r18
https://fuchsia.dev/
In GCC drops its copyright-assignment requirementI am suggesting that, because as I mentioned it looks understaffed from the outside, either that or there isn't that much willingness to spend resources on improving it beyond "good enough".
Given that you mentioned, that there were actually so many LLVM engineers around, I thought they could give them an hand. :)
Regarding the clang regressations:
https://github.com/android/ndk/issues/742
https://github.com/android/ndk/issues/721
There are way less than I remembered though, sorry for the confusion.
In LLVM 9.0ndk-gdb / ndk-gdb.py seem to be broken in this release:
https://github.com/android-ndk/ndk/issues/2
https://github.com/android-ndk/ndk/issues/3
In Android NDK r11 releasedWhy is that? The linked-to changelog seems to make the process clear.
"""
We’ve moved our bug tracker to GitHub: https://github.com/android-ndk/ndk/issues
"""
In Android NDK: GCC is now deprecated, everyone should be switching to Clang