Open lwcorp opened 5 years ago
Hi,
FakeWifiConnection won't fake the device if that's what you're asking. It can pass some other network (ethernet, 3g ...) as a wifi network, but if the device is not on that network then it won't work.
But it is on that network. Does that change things? I didn't mean to fake the device, just to allow getting access into the real device.
Not sure i understand what you're trying to do. If the device is there on wifi the app should just work, you don't need FakeWifiConnection.
I emulate Android-X86 inside VirtualBox, so Android-x86 thinks there's no Wi-Fi. But I want to connect to devices like ChromeCast and iRobot through apps that expect to find these devices inside the Wi-Fi which those apps are supposed to be used in.
Ok, should work then.
Do you mean I should install FakeWifiConnection, use the SSID of the real network and then suddenly the VM will find devices?
Here's the current situation (a neverending looped search):
SSID shouldn't matter. If it doesn't work check what the app is doing. Specifically how it scans for device, could be using wifi-specific calls that FakeWifiConnection doesn't emulate yet.
The iRobot HOME app provides remote control over your WiFi connected iRobot device.
When installing the app for the first time, you can't complete the installation unless it finds your device in your WiFi.
Should FakeWiFiConnection be able to trick it to connect anyway? Assuming, of course, I shall define the real SSID to which the device is connected.