desktop: fix linking mobile and connecting after onboarding. Also fixes other cases when core controller changes in android/desktop. #6489
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change fixes the increase of MESSAGE_TIMEOUT from 15 to 300 seconds that was made to reduce Android battery consumption that resulted in desktop app being unresponsive for 5 minutes after the initial onboarding, until reception loop makes the new call with the updated controller - starting from v6.4.4
The original change was made to reduce Android battery consumption.
The root cause was that changing the controller (e.g., when DB is (re) encrypted) did not immediately call the new reception loop, so the call was pending for 5 minutes.
This was likely to affect other cases too.