Investigate connectivity changes when entering/exiting sleep and doze
AndroidNetworkManager makes a connectivity check when it receives a broadcast associated with entering or exiting sleep or doze (ACTION_SCREEN_ON, ACTION_SCREEN_OFF or ACTION_DEVICE_IDLE_MODE_CHANGED). A second connectivity check is scheduled 1 minute after the broadcast, because we've sometimes seen connectivity changes shortly after entering or exiting sleep or doze.
We want to detect these delayed connectivity changes reliably, but we don't want to hold a wake lock for a full minute after every screen on/off event, and in any case that might just cause the connectivity changes to be deferred until we release the wake lock.
Investigate the circumstances under which these delayed connectivity changes happen (on various devices), find out whether our current approach detects them reliably (with and without Tor enabled), and if not, work out how to do so.