Partial connection between android and windows.

[whyvy-code]

I am only able to send files from android to windows, but not the opposite way. It shows partial connection. I have checked for VPN. Tried with vpn disabled as well as enabled, didn't work. Also tried hotspot.
Though it works perfectly between two android phones.

[TwistedC0de]

I had a similar issue even with VPN disabled, see #148 .

You can install app called Turmux and run "ifconfig" command to see all the interfaces.
Then compare that with Warpinator logs to see which interface it's using.
If it is using a left over VPN interface like "tun0" then it might be a match for #148 .

[whyvy-code]

I got this. Though I don't fully understand. But it seems there is some issue with my phone. While using apps like Warpinator ( I also tried LocalSend), it is able to send files but is unable to receive them.
In the logs it mentions inability to share certificate, after which the connection fails.
I have another phone and it works fine in that, even though I use the same vpn and dns service in both, plus connected to the same wifi.

[whyvy-code]

Could you provide the modified app, where in you altered the java file?

[TwistedC0de]

I don't think you have the same issue as me (no extra interface like "tun0"), so my patch probably won't work for you.
Maybe provide the Warpinator log here and see if @slowscript takes a look.

[whyvy-code]

I am attaching the debug log. The error shows "Couldn't establish duplex".

[TwistedC0de]

Did you check the firewall on your desktop? Would need to check both in-bound and out-bound.

[whyvy-code]

Yes. I tried with firewall disabled and enabled. Didn't work.

I have another phone which works with the laptop, but doesn't work with this phone. Seems like phone has some issue.

[slowscript]

Thanks for the log. Couldn't establish duplex means that the PC does not see the phone or that it does not connect back.
However, I got an idea what could be a problem. Looks like I have at some point moved around which parts of code run asynchronously during announcement of the service and ended up in a situation where cleanup of old announcement and the new announcement run at the same time.
Please try the attached APK, it is signed with the same keys as regular releases and should install cleanly. Alternatively you can build it yourself from master.

warpinator-release.zip

[whyvy-code]

Thank you. I will give it a try.

[whyvy-code]

Well, it didn't work. The same issue as well.

When I tried sending a file from my phone to another phone, it failed and displayed "Failed to open file for writing. " in the receiving phone.

Anyway, thanks for your effort. I will see if I can do it myself.

[whyvy-code]

Also, at times, it shows the below error.

[slowscript]

The "unregistering failed" message is unimportant and should not show up in release versions, I only added it for debugging.

Does the Lenovo device see your phone and does not connect or does it not show up at all? Have you tried manual connection?

There might also be an issue on the other side. If you're using warpinator-windows, you can start it by opening the Terminal (or cmd) in the folder where it is installed and running .\Warpinator.exe -d, which (after closing the program) will write logs into your AppData\Local\Warpinator\latest.log. Winpinator is probably also somehow able to produce logs, although I'm not that familiar with it.

Now there is also a new Android version 1.8.3, where I have tweaked some keep-alive values, that could have caused some issues with connections breaking, although I'm not sure if this is your case.

[whyvy-code]

Both devices see each other. The first time I tried, it worked. But every subsequent try failed. It only showed half duplex on both devices, both sending.

[slowscript]

Thanks for the reply. So if I understand correctly, both devices show half duplex at the exact same time? Waiting for duplex means there is a one-way connection, through which the device asks the other if it is also waiting for duplex. If both devices are in this state, it should immediately switch to Connected.
If each device shows Waiting for duplex at a different time (e.g. one times out and fails before the other device can connect), that means that this could be fixed by increasing the timeout (currently 5 sec). If you see the Windows device in this state, tap the reconnect button on its device page on the Android app (or vice versa) to make them attempt to connect at the same time.
I will also note that the log that you sent does not show the Windows device connecting, there would be messages like (device name) is waiting for duplex... if it was. Ideally I would need logs from both devices that correspond to the same connection attempt.

[slowscript]

@whyvy-code I have discovered a bug in release builds that seems to cause what you are describing (only one device connects at a time). I have posted a build that should fix it here: #149 (comment) . Could you test if it resolves your problem?