madmaxoft / deskemes Goto Github PK

Some Android devices don't support port reversing (HTC Desire Z with Cyanogen). For those, it would be better if the DesktopClient asked the AndroidApp to connect to specific IP addresses via wifi.

Allow a USB connection by using ADB reverse-port-forwarding, and a special intent in the Android app.

Sometimes the app doesn't detect socket closure, which results in the app running in busy-loop (select - got 1 socket - read 0 bytes - repeat) and at the same time the app won't connect to the remote peer because it's still blacklisted.

The connection needs TLS encryption. The encryption is already documented, we need to add it to the Android app, the desktop client and the Lua tests.

The wizard should first show devices that have already been discovered. If the user selects "My device is not in the list", they should be taken through the steps to connect the device - via USB, TCP or Bluetooth.

Perhaps the device list should be a regular dialog that stays in the background / attached to the wizard, and any new device that connects while the wizard is running should be highlighted.

When in the New Device Wizard, after selecting a device that is not paired, the "waiting for secure connection" progress page is shown. If the device starts TLS at this point, it is auto-accepted without pairing and the wizard is stuck on the progress page. The device is shown in the main window and the wizard can be cancelled.

To replicate this issue, simply use a random PubID for a device.