Michael Rogers: > On 02/02/15 18:13, Hans-Christoph Steiner wrote: >> Michael Rogers: >>> Yup, this uses wifi direct to discover peers and Bluetooth or >>> ordinary wifi to connect to them. No user confirmation is >>> required for discovery or connection, unlike using Bluetooth or >>> wifi direct alone. >>> >>> I think I have a solution for connecting via wifi direct instead >>> of ordinary wifi, again without user confirmation, but I won't be >>> able to test it till tomorrow. > > Unfortunately neither of the solutions I had in mind worked. It's > possible to bind a socket to the link-local address used for service > discovery, but other devices can't connect to that socket. Possibly > the interface is configured to reject everything except service > discovery packets, or possibly the other device's routing table > doesn't send the connection over the link-local interface. > > The other approach I had in mind was to create a legacy mode AP via > WifiP2pManager.createGroup(). The AP is created successfully, with a > second link-local IPv6 address and a site-local IPv4 address > (192.168.x.x), but the existence of the AP seems to interfere with > service discovery. I need to investigate this further. > >>> jmdns could be useful for APIs 14-15, which support wifi direct >>> but not the service discovery stuff. We might be able to get >>> jmdns working over the wifi direct interface, which uses a >>> link-local IPv6 address. > >> I don't know if you are looking to support android-10/2.3.3, but >> that might be possible using jmdns. As far as I understand it, >> WiFi-Direct creates a real WiFi-AP, so the devices that attach to >> that do not need to have any specific WiFi-Direct support, they >> just need to be able to find and connect to a WiFi-AP. That is >> definitely something you can do automatically in android-10/2.3.3. > > Yup, older peers can connect to the AP, but in order to discover it > via jmdns I think both peers would have to be connected to an ordinary AP. > > Supporting older devices would be nice, but since this is just a side > project I'll be content if it works on Android 16+, which covers about > 85% of devices that connect to Google Play.
If Google Play devices are your target market, that's fine. But consider that most Chinese Android devices are not Play devices. And there are still new android-10 devices being made, those can cost as little as US$40. My guess is that if you look at Android around the world, non-Play devices are edging towards a majority, and of those non-Play devices, android-10 is quite common. But I think no one really has that data. .hc -- PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81 https://pgp.mit.edu/pks/lookup?op=vindex&search=0x9F0FE587374BBE81 _______________________________________________ Guardian-dev mailing list Post: [email protected] List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To Unsubscribe Send email to: [email protected] Or visit: https://lists.mayfirst.org/mailman/options/guardian-dev/archive%40mail-archive.com You are subscribed as: [email protected]
