It requires WiFi active monitor mode, which is a standard chipset feature. Nothing related to custom silicon, secure enclave, hardware acceleration or other such shenanigans being brought up in the current conversation, and nothing that most android phones wouldn't fully support.
No, OWL only appears to have specific driver requirements, namely that they expose to userspace functionality that any remotely modern WiFi chip should already have.
Yeah, I saw that. I'm pretty sure that's a statement more about the drivers than the underlying hardware. Open-source drivers often have more limited feature support than the underlying hardware. I doubt anyone is producing WiFi chips that cannot transmit arbitrary software-constructed WiFi frames, or capture and relay to software all the frames they hear, and ACK frames as needed while doing so. But it's very easy to imagine that some of those capabilities would not be publicly documented, or not enabled with the default firmware provided to end users. Those limitations that hinder Linux end-users tinkering with their machines don't necessarily apply to an OS vendor with a deep partnership with the relevant hardware vendors.
