Repository navigation
fix(android): Time a warm relaunch within 1 minute from its own activity - #6687
Merged
Merged
Conversation
runningcode
requested review from
markushi and
romtsn
and removed request for
a team
November 19, 2026 16:59
Contributor
PR risk: mediumFor commit Main concerns: data sent to Sentry, reach, host performance. This label is a hint for reviewers, not an approval. |
📲 Install BuildsAndroid
|
Since #4999, destroying the last activity marks the next launch as warm but keeps the process-start anchor unless the process is older than a minute. A quick relaunch was therefore timed from process start: standalone mode re-sent the cold interval as a second warm App Start, and the relaunched screen's TTID spanned the whole session. Refs JAVA-503 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
runningcode
force-pushed
the
no/fix-warm-relaunch-app-start-anchor
branch
from
November 19, 2026 18:26
f2d06bb to
65fd006
Compare
4 of 9 tasks
romtsn
reviewed
Nov 20, 2026
romtsn
approved these changes
Nov 20, 2026
romtsn
left a comment
Contributor
There was a problem hiding this comment.
One comment, but can be done in a follow-up, unblocking
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📜 Description
Here's the bug: You start the app, click home then relaunch the app with "Don't keep activities" on.
The second launch is a warm start since the activity was killed but not the process.
The problem is that it uses the process start time instead of a new anchor. This means the warm start is super long (since the process was started) instead of when the activity was launched. This affects TTID and TTFD metrics that include warm starts.
💡 Motivation and Context
Apparently this existed since #4999 (8.32.0),
onActivityDestroyedmarks the next launch as warm but leaves the process-start anchor in place, andonActivityCreatedresets it only after 1 minute. So a relaunch within 60s was timed from process start:💚 How did you test it?
My clanker easily reproduced this on an emulator:
App Startapp_start_warm1684ms, same start time as the cold oneui.loadTTIDapp_start_warm📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Make standalone app start tracing the default on
9.x.x(JAVA-503).🤖 Generated with Claude Code