Android 17 QPR1 Pricing and AOSP Source Status

Official API, source, and pricing boundary checked:

Verified pricing boundary

No new API fee or paid Android 17 QPR1 SKU

Google published API level 37.1 as an Android framework surface. Its official QPR1 and API-diff documentation does not introduce a per-call charge, SDK price, platform subscription, credit pack, or metered service. The buyer impact is compatibility and testing work, not a new Google invoice line.

New API fee

None announced

Framework version

API 37.1

API diff

84 additions · 233 changes

Matching QPR1 AOSP source

Not published at check time

What Google published

Google's final API 37-to-37.1 change report records a 0.52% framework difference: 84 additions, 233 changes, and no removals. It adds the android.hardware.hid package and updates areas including input, Health Connect, media, telecom, the embedded photo picker, and HTTP request timing.

The QPR1 release notes say the API surface reached Platform Stability and can be incorporated into apps. That makes 37.1 a real public developer surface rather than a UI-only Pixel feature drop.

What Google had not published

At the September 18 check, Google's public manifest refs exposed the Android 17 base release but no matching Android 17 QPR1 release branch. Google separately states that, effective in 2026, source is published to AOSP in Q2 and Q4. A September QPR can therefore ship to Pixel before the next scheduled AOSP source drop.

GrapheneOS described this as the first Android release since 3.x to add developer APIs without a simultaneous AOSP release. That historical comparison belongs to GrapheneOS; Google has not confirmed it. “Pixel-only” should also be read as launch availability, not a claim of permanent exclusivity.

Licensing and price are separate from source timing

AOSP uses OSI-approved open-source licenses, with Apache 2.0 preferred for most Android software and GPLv2 applying to Linux kernel code. The missing QPR1 source drop changes what OEMs and alternative operating systems can build today; it does not create a paid API 37.1 license or convert the Android SDK into a metered service.

AI Pricing Guru therefore keeps the canonical pricing dataset and public API unchanged. Those feeds track billable AI model endpoints, and Android 17 QPR1 has no model identifier, token price, or hosted inference route.

The real cost: compatibility work

  • Track the full SDK version rather than treating every Android 17 device as equivalent.
  • Test critical flows on both a QPR1 Pixel and a non-37.1 Android 17 device.
  • Use runtime capability checks and keep fallbacks for user-critical paths.
  • Measure device coverage before making a 37.1-only capability a hard dependency.
  • Recheck public AOSP refs during Google's Q4 publishing window.

Labs inclusion decision

Android API 37.1 is an operating-system capability surface, not a callable AI model. It cannot enter the current 49-task model leaderboard. Labs records an explicit scope and availability blocker until there is a reproducible cross-device app test with pinned Pixel and AOSP-derived builds, version and feature checks, traces, failure grading, engineering time, and device coverage.

Read the launch analysis for the API changes, portability consequences, and developer checklist.

Frequently asked questions

Does Android 17 QPR1 API 37.1 have a new API fee?

No new per-call fee, SDK charge, platform subscription, or API 37.1 rate card was announced. This is an Android framework release and source-availability change, not a hosted paid API.

Is Android 17 QPR1 open source in AOSP?

The Android 17 base release is in AOSP, but Google had not published a matching QPR1 source branch when checked on September 18, 2026. Google says its 2026 AOSP source drops occur in Q2 and Q4.

Are API 37.1 features available on every Android 17 device?

No. The public 37-to-37.1 API diff exists and Pixel received QPR1 first, but an Android 17 major-version check alone does not prove that a device implements the 37.1 surface.

Why is Android 17 QPR1 not in the AI pricing API?

The pricing API tracks billable AI model endpoints. Android API 37.1 is an operating-system framework surface with no model ID or usage rate, so adding a zero-dollar model row would misclassify it.

What cost does the AOSP delay create?

The immediate cost is engineering time: Pixel and non-Pixel testing, full SDK-version guards, runtime capability checks, fallback paths, and delayed adoption for OEM or alternative-OS builds.

Official sources and maintenance

Checked against Google's QPR1 release notes, API 37.1 diff, public manifest refs, 2026 source schedule, and AOSP licensing. Sources are checked daily for a QPR1 source release, price boundary change, or corrected availability statement.