Android is OS agnostic, barring the NDK - I don't think it's too far fetched to see ChromeOS and Android be ported to Fuchsia in due time.
Android is highly coupled to Linux, and this is visible at various places in the SDK such as: https://developer.android.com/reference/android/system/Os?hl...
But even just behaviorally it doesn't pretend to be OS agnostic at all. Setting thread priorities isn't even abstracted, it's just "uses the Linux values for this" https://developer.android.com/reference/android/os/Process#s...
That doesn't prevent building an abstraction layer and plopping Android onto a different kernel, of course. After all that's what Microsoft did with WSL.
That is POSIX, nothing to do with Linux.
As Android engineer since 2013, I'll say this is patently untrue. It is really difficult to get Android to work on non Linux OS's without virtualization.
It compiles slower, doesn't produce machine code of the same quality and requires a separate semantic model for heap management, the reason why recently they had a blog post about having to redesign it.
EDIT: Exactly for my experience with those languages and what went wrong with their adoption is why I will never use anything that isn't a platform language on production code. Either it comes with the platform SDK or no bother.
In Kotlin's case that is Android, as long as Google doesn't do one of their reboots and decides to focus on ChromeOS or Fuchsia instead.