This is false and a meme that continues to stall progress. Hardening the BT stack means that accidentally crappy or adversarial devices cannot use a buggy BT stack to pop a device, from kernel mode remotely.

This is a hugely welcome change. The threat model from a app using the NDK is much different than having a drive by wireless attack.

Defense in depth and put focus on protocols and parsing, the rest of our stacks will come in time.

The meme that stalls progress is the myth of the perfect C developer.

> Sadly the Android team, while taking this safety steps, it keeps using unsafe C userspace for NDK APIs.

You phrase this as a negative but it's overwhelmingly a positive. Imagine how difficult it'd be to write an app using the NDK in Rust if the NDK had been C++ instead. The C ABI remains by far the most portable & common target. Everything can call it.

It is a bit hard to talk about safety when everything one has to play is an API that allows for all the usual stuff that C is known to cause.

Everything can call it, and everyone has to redo the safety work.