Install 9.0 on supported handsets: public rollout began on August 6, 2018 for Google’s Pixel line, with OEM rollouts spanning late 2018–2019. This build corresponds to API level 28; expect faster security patch delivery on devices with Project Treble support and check your manufacturer’s update schedule before proceeding.
Major technical changes include Adaptive Battery (ML-driven limits on background CPU and network use), gesture-based navigation (single-pill home and swipe gestures), Digital Wellbeing tools (app timers, dashboard, wind-down), strengthened privacy controls that block microphone/camera/sensor access for idle background apps, Private DNS (DNS-over-TLS) support and TLS 1.3 adoption, display cutout (notch) handling, multi-camera APIs for logical streams, HEIF image support to reduce photo sizes, and performance improvements in the runtime and JIT compiler.
Practical steps for end users: back up to cloud storage before updating; check Settings > System > System update for vendor packages; enable Adaptive Battery and Adaptive Brightness in Settings to gain immediate battery savings; turn on Private DNS and use a trusted provider such as dns.google or 1dot1dot1dot1.cloudflare-dns.com; activate Digital Wellbeing controls if available; audit mic and camera permissions for apps running in background.
For developers: target and compile against SDK 28 and test on the API 28 system image in emulator and on hardware; adapt UI to gesture navigation and display cutouts; migrate background work to WorkManager or foreground services to comply with background execution limits; adopt the BiometricPrompt API, multi-camera support and HEIF where appropriate; verify network stacks for TLS 1.3 and Private DNS compatibility and test behavior when microphone/camera access is revoked for background processes.
Android 9.0 (Pie): Version Basics
Upgrade devices to 9.0 (API level 28) to obtain gesture navigation, adaptive battery and brightness driven by on-device machine learning, stricter background privacy, and runtime performance improvements from the new ART JIT/profiling system.
- API level: 28.
- Public rollout began August 6, 2018.
- Key platform capabilities: gesture navigation model, multi-camera API (logical + physical camera support), HEIF image container support, VP9 Profile 2 HDR playback, Wi‑Fi RTT for indoor positioning, display-cutout (notch) support.
- Privacy and background limits: background processes are blocked from accessing camera, microphone and sensors; tighter restrictions on background network and location access for apps targeting API 28.
- Security and networking: platform adds support for modern cipher suites including TLS 1.3 support; improved sandboxing and media stack hardening.
- Runtime and storage: ART switched to a JIT + profile-guided compilation model to reduce install size and improve runtime performance; HEIF support reduces photo storage size compared with JPEG.
- User-facing additions: adaptive battery/brightness, app suggestions (App Actions), UI for digital wellbeing pilot programs and enhanced notification replies.
- Developer checklist:
- Set compileSdkVersion and targetSdkVersion to 28 and run full test matrix on API 28 images/emulators and representative devices.
- Handle gesture navigation: test edge-swipe gestures and use setSystemGestureExclusionRects(View) where appropriate to avoid accidental system gestures.
- Support display cutouts by opting into windowLayoutInDisplayCutoutMode and testing on tall aspect ratios and notched displays.
- Migrate authentication flows to BiometricPrompt API and update camera/microphone usage to respect background access restrictions.
- Use Camera2 multi-camera APIs for devices exposing logical camera devices; validate capture session behavior for simultaneous streams.
- Adopt ART profile-guided optimizations by generating baseline profiles where heavy code paths exist to improve startup and steady-state performance.
- Verify network security configuration and TLS compatibility with servers, and test HEIF image handling if the app reads/writes photos.
- Upgrade checklist for device owners:
- Back up data before applying the update; check OEM or carrier update schedules for your model.
- Confirm critical apps run on API 28 using Play Store reviews or vendor compatibility notes; update apps before major OS upgrade if possible.
- After updating: enable gesture navigation in system settings if preferred, allow Adaptive Battery to learn usage, and review app permissions for background access to sensors, camera and microphone.
- If encountering app issues, test by switching to classic navigation or contacting the app developer with logs and repro steps.
Official release date and build numbers
Flash build PPR1.180610.009 (API level 28) for the original stable public image – official availability date: 2018-08-06.
Core facts: initial public build identifier is PPR1.180610. Should you cherished this article along with you would like to obtain details regarding 1xbet ph download kindly pay a visit to our web site. 009; platform API is 28; the first source tag in the open-source tree is 9.0.0_r1 (published 2018-08-06). Factory images for Pixel-family devices used that PPR1 prefix for the August rollout.
How to interpret build IDs: the prefix (for example, PPR1) denotes the branch/release stream, the six-digit block (180610) encodes the upstream build date (YYMMDD → 2018-06-10), and the trailing number is the vendor build counter. Later monthly security updates retain the same pattern with different prefixes and date codes.
Verify builds on a device: open Settings → About phone → Build number and Security patch level, or from a host use adb shell getprop ro.build.id and adb shell getprop ro.build.fingerprint; for bootloader queries use fastboot getvar all. Cross-check those values against the factory-image archive on Google’s developer pages or the open-source tree tag list (start at 9.0.0_r1) before flashing or deploying.
