Android app start times out when restarting appsupport

Bug Reports
#1

REPRODUCIBILITY: 75% (often)
OSVERSION: 4.5.0.21
HARDWARE: Sony Xperia 10 III - xqbt52 - xqbt52 - 1.0.1.22 - aarch64
UI LANGUAGE: Deutsch (user: de_DE, os: de_DE.utf8)
REGRESSION: not specified

DESCRIPTION:

This is an inconvinience that may cause people to restart their phones.

PRECONDITIONS:

STEPS TO REPRODUCE:

1.stop appsupport
2. Start it
3. Immediatly open an android app

EXPECTED RESULTS:

The app starts after appsupport started

ACTUAL RESULTS:

First start of app fails. Subsequent start works

MODIFICATIONS:

  • Patchmanager: no
  • OpenRepos: yes
  • Chum: yes
  • Other: none specified

ADDITIONAL INFORMATION:

Device Owner User: defaultuser
Home Encryption: enabled

the initial version of this bug report was created using Bugger 0.9.10+git1
2 Likes
#2

To be honest I observed this behaviour on all Sailfish versions I had, beginning with 3.2 - and I consider it absolutely understandable that it takes it time to start the container.

2 Likes
#3

The start time is fine. The problem is that the behavior is misleading and one might think that the container is not coming up… What is happening sometimes as well…

shouldn’t be too hard to increase the timeout or have a special notification if the container just started

2 Likes
#4

I see this most of the time too (for those few cases i have had AppSupport turned off, that is).
If the app timeout was another 50% or so it would have worked robustly for me.

1 Like