v2 May 2nd update seems to only prolong the time before receiving the 'Service...' message, regardless of power-related option in settings. I reverted back to v1 a few days back and everything worked as it should...guess I'll revert back again.
Service stopped by device
If you look at all the forums this issue has been going for about 19 months with zero sign of resolution. The only response I ever got from the devs is that they're looking into it. I'm sorry but if it isn't resolved after 19 months you're not. My guess is that it's happening to onlyt a few people and as long as the majority of their users are fine they'll just ignore it.
The lack of input from the devs tells me they just don't care.
The lack of input from the devs tells me they just don't care.
@ALL
Thanks for your feedback and really sorry for the inconvenience this have caused and the late reply.
Usually this issue is related to the network environment, and power saving mode on device may cause this, too. Please check if you have set any power saving mode on your device. You may keep screen awake to avoid network being cut off.
Because we cannot reproduce your issue. So if you guys could offer us more details, such as what operation and factors will lead to this, we can figure out the cause and fix it more efficiently.
And we've fixed some bugs and some improvements are made since V2 was released. The latest version of AirDroid is 2.0.6. Would you please update AirDroid to the latest version and try if the issue still remains?
If yes, how long will this error message appear and more details?
Thanks for your feedback and really sorry for the inconvenience this have caused and the late reply.
Usually this issue is related to the network environment, and power saving mode on device may cause this, too. Please check if you have set any power saving mode on your device. You may keep screen awake to avoid network being cut off.
Because we cannot reproduce your issue. So if you guys could offer us more details, such as what operation and factors will lead to this, we can figure out the cause and fix it more efficiently.
And we've fixed some bugs and some improvements are made since V2 was released. The latest version of AirDroid is 2.0.6. Would you please update AirDroid to the latest version and try if the issue still remains?
If yes, how long will this error message appear and more details?