starling-capture
starling-capture copied to clipboard
Cannot Connect to Internet When Establish Connections in Both WiFi to Canon Camera and Mobile Data
Move from https://github.com/numbersprotocol/mediant/issues/14
Android: 8.0.0 Mobile: Exodus 1 App version: 0.12.1 Capture type: image
Steps to reproduce (Dual Capture mode):
- Enable WiFi only i. And connect to the Canon camera WiFi access point.
- Go to Settings, i. Click Connect to Canon Camera ii. Enable Polling
- Go back to the main screen, i. Click Open CCAPI Live View ii. Enable Dual Capture
- Enable Mobile network (and keep WiFi enabled).
- Trigger Canon camera shot.
- See the pop-up messages in order:
i. Successfully uploaded media via Textile.
ii.
failed to connect to /52.90.13.186 (port 80) from /192.168.1.10 (port 40884) after 1...
Steps to reproduce (Camera Capture mode):
- Enable WiFi only i. And connect to the Canon camera WiFi access point.
- Go to Settings, i. Click Connect to Canon Camera ii. Enable Polling
- Enable Mobile network (and keep WiFi enabled).
- Trigger Canon camera shot.
- See the pop-up messages in order:
i. Successfully uploaded media via Textile.
ii.
failed to connect to /52.90.13.186 (port 80) from /192.168.1.10 (port 40884) after 1...
Steps to reproduce (Mobile Capture mode):
- Enable WiFi only i. And connect to the Canon camera WiFi access point.
- Go to Settings, i. Click Connect to Canon Camera ii. Enable Polling
- Enable Mobile network (and keep WiFi enabled).
- Trigger Mobile camera shot.
- See the pop-up messages in order:
i. Successfully uploaded media via Textile.
ii.
failed to connect to /52.90.13.186 (port 80) from /192.168.1.10 (port 40884) after 1...
This issue requires further study to change the default behavior of the Android networking policy. We need to set the transport type of CanonCameraControlApi connections to Wi-Fi manually. We should try to provide a custom socket factory from Android Network class to OkHttp client. Further details: https://github.com/square/okhttp/issues/3736
Reference:
This sprint (20.09.10) will focus on the survey of the solution of this issue. The implementation may come later.
@tammyyang If this issue is not that critical, we should postpone the implementation to the next milestone (beta6).