UPDATE: I've since tested my Gear S2 on other Wifi networks and had better results.
So my conclusion is that the Gear S2 suffers *really badly* under adverse network conditions. In good network conditions it is fine, though OH SO SLOW to deploy and debug even the simplest applications (often multiple minutes to launch a debugging session). In bad network conditions, SDB is utterly dreadful. Not sure if the issue is at the SDB level, or at the transport layer, but the SDB connection just gets lost, and does not recover. You need to manually close the "dead connection", often restart the WiFi connection and then re-establish the SDB connection. On Thu, Dec 17, 2015 at 5:04 PM, Bob Summerwill <[email protected]> wrote: > I just wrote .. "How to deploy to Gear S2 smartwatch" for TizenExperts: > http://www.tizenexperts.com/2015/12/how-to-deploy-to-gear-s2-smartwatch/ > > If anybody knows where the "Wi-Fi debugging on Gear S2 is flakey as > anything" feedback can be usefully directed, that would be much appreciated! > > > -- > [email protected] > > -- [email protected]
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
