In order for SyncbackPro/SE to find SyncBack Touch, SyncBack Touch is broadcasting a simple message on the local network to identify itself. SyncBackPro/SE picks up this message and figures out on which IP/Port SyncBack Touch is listening and then tries to connect to it.
The problem is that on some Android chipsets if the device is sleeping (screen is off), even if you have set your WiFi to be always ON, this broadcast message is not being transmitted so SyncbackPro/SE cannot receive it. If SyncBack Touch is running, it will still be running even the device enters sleep mode, it's just that the WiFi driver discards the broadcast packets.
In your case I would suggest using a static IP for your device when connected to that particular network and then use that IP when you configure SyncBack Touch in SyncBackPro. Keep in mind though that SyncBack Touch is a standard application and it may get shutdown by the device if doing nothing and sitting idle in the background for long periods of time.
Thanks,
Kostas
The problem is that on some Android chipsets if the device is sleeping (screen is off), even if you have set your WiFi to be always ON, this broadcast message is not being transmitted so SyncbackPro/SE cannot receive it. If SyncBack Touch is running, it will still be running even the device enters sleep mode, it's just that the WiFi driver discards the broadcast packets.
In your case I would suggest using a static IP for your device when connected to that particular network and then use that IP when you configure SyncBack Touch in SyncBackPro. Keep in mind though that SyncBack Touch is a standard application and it may get shutdown by the device if doing nothing and sitting idle in the background for long periods of time.
Thanks,
Kostas
![2BrightSparks [2bs]](http://www.2brightsparks.com/bb/images/smilies/2bs.gif)