[runningcode]

📜 Description

Removes the enablePerformanceV2 option and its io.sentry.performance-v2.enable manifest key. Performance V2 is now always on.

With the flag gone, the v1 code paths can't run anymore, so this also deletes them:

• ActivityFramesTracker, the v1 slow/frozen frames tracker built on androidx FrameMetricsAggregator. It already no-oped whenever V2 was on. SpanFrameMetricsCollector is now always registered and records frame measurements per span.
• The ActivityFramesTracker parameter on ActivityLifecycleIntegration's public constructor, PerformanceAndroidEventProcessor and the AndroidOptionsInitializer plumbing.
• The SentryAndroidOptions parameter on AppStartMetrics.getAppStartTimeSpanWithFallback, which only read the flag.
• The ProGuard keep rule for FrameMetricsAggregator.

App starts are always measured from process start on API 24+. Below API 24 they still fall back to SDK init time, like before.

💡 Motivation and Context

The flag has defaulted to true for a long time, and we don't expect anyone to turn it off. Dropping it in the 9.0 major removes a configuration surface and about 1,200 lines of v1 code and tests.

GitHub code search found no use of ActivityFramesTracker, getAppStartTimeSpanWithFallback or the flag in the hybrid SDKs.

• resolves: Drop enablePerformanceV2 flag #5472
• resolves: JAVA-527

💚 How did you test it?

• Removed the tests that only covered the v1 path or the deleted tracker.
• Added a test that SpanFrameMetricsCollector is registered by default.
• Reworked foreground standalone app start measurement uses foreground fallback time span, which relied on V2 being off. It now uses an app start span longer than the one-minute cap, so the foreground fallback to SDK init time is still covered.
• if app is launched in background, appStartTimeSpanWithFallback returns an empty span only passed through the v1 path. It created an activity, and since then an activity created after a background launch starts a new warm start. V1 ignored that restarted span. The test now checks the background launch without an activity, and the next test already covers the warm start.
• Merged the two AutomaticSpansTest frames UI tests (V2 on and off) into one.
• Ran the affected sentry-android-core unit tests locally.

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

Update the Android docs in sentry-docs: tracing/instrumentation/perf-v2.mdx still shows how to enable the option, and features/index.mdx and automatic-instrumentation.mdx link to it.

🤖 Generated with Claude Code

[linear-code]

JAVA-527

[github-actions]

🚨 Detected changes in high risk code 🚨

High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:

• sentry-android-core/src/main/java/io/sentry/android/core/InternalSentrySdk.java

[github-actions]

🚨 Detected changes in high risk code 🚨

High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:

• sentry-android-core/src/main/java/io/sentry/android/core/InternalSentrySdk.java

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.62.0 (1)	release

⚙️ sentry-android Build Distribution Settings