location: Location Manager wakelock cleanup
Location Providers are now responsible for their own wakelocks and scheduling. Also fixed a deadlock in LocationManagerService in the code for releasing wakelocks after client notifications have been received. The fix is to use the Receiver object and mWakeLock for synchronization instead of the global mLock lock. Signed-off-by: Mike Lockwood <lockwood@android.com>
This commit is contained in:
@@ -231,20 +231,4 @@ public class LocationProviderProxy {
|
||||
Log.e(TAG, "removeListener failed", e);
|
||||
}
|
||||
}
|
||||
|
||||
public void wakeLockAcquired() {
|
||||
try {
|
||||
mProvider.wakeLockAcquired();
|
||||
} catch (RemoteException e) {
|
||||
Log.e(TAG, "wakeLockAcquired failed", e);
|
||||
}
|
||||
}
|
||||
|
||||
public void wakeLockReleased() {
|
||||
try {
|
||||
mProvider.wakeLockReleased();
|
||||
} catch (RemoteException e) {
|
||||
Log.e(TAG, "wakeLockReleased failed", e);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user