Open 5hahryar opened 2 years ago
Yeah. Good point. I'll try to fix this
These are the ways that I've tried and failed:
In my PR i chose the 1. approach. I'm not publishing to google play atm, so luckily I don't need to care about googles rules.
Ning already has a custom mDNS system (because the android buildin system is slow and unreliable). There seem to be some bugs in parsing the DNS-Records resulting in some response data not being understood by Ning.
looks like it cannot be done because sending these kinds of packets needs root access.
If I would require root access, reading from /proc/arp
would also be possible
Option 4 founds interesting. I have never heard of SNMP, so I might look into that
Vendor detection has lately (during the past couple weeks?) stopped working for me on Android 10.
Even with the targetSdk set to 29 this doesn't work on Android 13 Looks like SNMP isn't enabled by default on most devices, so that must not be what Fing is relying on (which Fing does still work on Android 13)
I found this library which replacing the attempt to read /proc/net/arp with this and then changing index 3 to 4 when mapping gets it working for Android 13 as long as you continue to target sdk 29
Hello, because of the new restrictions on android for accessing the ARP table and ip commands, the mac address and vendor detection do not work any more. Is there any way to fix this issue? I've noticed some apps have found a way to work around this.