Just noticed this in termux using shizuku :
rish -c ip a
68: wondertap0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ieee802.11/radiotap {some MAC address}brd ff:ff:ff:ff:ff:ff
i searched for wondertap0 ans found this:
https://android.googlesource.com/kernel/common-modules/wonder/+/refs/heads/android14-6.1/wondertap.c
Which is mosltly gibberish to me.
Wonder apparently is a driver for Protocol-X which enables virtual WiFi devices !!!
And i had a bit of a time finding anything else about it. Actually, i found a total of 1 thing. The source code.
https://android.googlesource.com/kernel/common-modules/wonder/+/refs/heads/android17-6.18
noticing it is meant to contact another device, and is acting maybe as a server and tunnel. But it isn’t just a link. It creates its own 80211x device and broadcast frequency.
But, what the hell is it? What does it do, what’s it for, what triggers it, who owns the device created, and what is it sending, how is it broadcasting?
You must log in or # to comment.
I don’t get why anyone would downvote you. This is a very legitimate question.
It’s an interface between the standard kernel WiFi driver and a proprietary WiFi device.
what is the proprietary device?
Is it internal or a physical device and why is it created if i have no google anything ?
Probably the actual physical WiFi device for some phone or phones. I’d imagine it’s a compatibility layer so they can focus on the standard kernel driver or leverage that.
That’s the one where after you give away all your personal information, Google turns into an elephant
Google Wonder WiFi Virtual Soft-MAC Driver
wondertap.c is just one of several files for this kernel module, check out main.c and some of the other source files to get a better understanding of what it does.
Cancelled.
Sorry, that’s what it will be in 6 months.
I’m wondering too.
Some kind of specialized wifi connection. Google has implemented support in Android via that driver.
