Reconnect Loop because of skipping backOff logic

currentDelay would stay 0 if error occurs in connect() method,
resulting in busy-loop on network failures.

Fix by always calling scheduleReconnect() which contains backoff logic.
This commit is contained in:
lambdaupb 2015-10-23 18:27:50 +02:00
parent cf7c72c14f
commit 788eddc31e
1 changed files with 3 additions and 5 deletions

View File

@ -377,11 +377,9 @@ public class McsService extends Service implements Handler.Callback {
sslSocket.close();
} catch (Exception ignored) {
}
if (currentDelay == 0) {
sendBroadcast(new Intent("org.microg.gms.gcm.RECONNECT"), "org.microg.gms.STATUS_BROADCAST");
} else {
scheduleReconnect(this);
}
scheduleReconnect(this);
alarmManager.cancel(heartbeatIntent);
if (wakeLock != null) {
wakeLock.release();