Sabaev

`Clock.getDefault()` isn’t configurable; add platform-aware selection & override hooks

5

**Component(s):** `sdk`, `common`, `bootstrap` **Environment:** Cross-platform (JVM & Android) ## Summary `Clock.getDefault()` effectively hardwires `System.nanoTime()`. On Android this ignores deep sleep, leading to incorrect elapsed-time semantics for features like timeouts...

`backgroundInactivityTimeout` miscounts on Android due to a clock that pauses in deep sleep

1

# 1) `backgroundInactivityTimeout` miscounts on Android due to a clock that pauses in deep sleep **Component(s):** `android-agent`, `android`, `SessionManager`, `SessionConfig` **Environment:** Android (device enters Doze / deep sleep) ## Summary...

AttributeMap does not respect last-value-wins semantics for duplicate keys (SpanBuilder.setAttribute vs Attributes.builder)

2

**Describe the bug** According to the OpenTelemetry specification: - Attribute keys are **strings** https://opentelemetry.io/docs/specs/otel/common/#attribute > “The attribute key MUST be a non-null and non-empty string… Keys that differ in casing...