Meine Wiki

Seite bearbeiten und [Speichern] drücken. Siehe syntax zur Wiki-Syntax. Bitte nur editieren, falls Sie das Dokument tatsächlich verbessern können. Zum Testen bitte erst in der Testumgebung üben.

Quick facts: The initial public rollout began on August 21, 2017 (build corresponding to API 26); the follow-up incremental system arrived December 5, 2017 (API 27). The codename for this pair is the "O" release. API 26 introduced core platform changes; API 27 added machine‑learning and low‑memory optimizations plus vendor modularization work that speeds rollouts on many devices.

Key technical highlights (practical impact): Notification channels (apps must register per‑channel settings so users can control importance and sound); picture‑in‑picture for video apps; an Autofill framework for password managers and form filling; adaptive icons requiring foreground/background layers for proper display; background execution limits that force long tasks into JobScheduler/WorkManager rather than persistent background services; Bluetooth 5 support and Wi‑Fi Aware (NAN); introduction of Project Treble to separate vendor code and accelerate firmware updates; API 27 adds a Neural Networks API for on‑device inference and a Go edition tuned for low‑RAM devices.

Concrete recommendations: For end users – verify "Build number" or "OS release" and the API level in Settings → About phone; keep the device on official updates and apply monthly security patches; enable a trusted password manager via the Autofill framework; turn off background location for nonessential apps and review per‑app notification channels to avoid unwanted alerts. For app teams – target API 26+ and implement notification channels, migrate background work to JobScheduler/WorkManager, adopt the Autofill API for credential handling, supply adaptive icons, and test on both API 26 and API 27 system images (use the NNAPI on API 27 where on‑device acceleration yields latency gains).

What Android Version Is Oreo? Android 8.0 &amp; 8.1 Overview

Upgrade devices to the latest security build for the 2017–2018 Google mobile-OS releases (API level 26 and API level 27) and, for apps, target API 26+ while implementing notification channels and background-execution limits to avoid delivery failures and unexpected service termination.

Public rollout dates: initial platform image published August 21, 2017 (API 26); follow-up maintenance release deployed December 5, 2017 (API 27). Key platform identifiers: API 26 = base release; API 27 = incremental feature and stability updates.

User-facing improvements: adaptive launcher icons (layered foreground/background assets, mipmap-anydpi-v26), notification channels and dots (mandatory channel creation for visible alerts), picture-in-picture mode for video apps (declare support in the manifest), Autofill Framework (system-level credential and form autofill via android:autofillHints), Wi‑Fi Aware (NAN) support, and tightened background execution/implicit-broadcast limits that reduce battery drain.

Developer checklist:

- Create and register NotificationChannel objects before posting notifications; handle varying importance levels and user-managed channel settings.

- Replace long-running background services with JobScheduler/WorkManager or convert to foreground services and call startForeground() within the required time window.

- Stop relying on implicit broadcasts that were limited; use explicit broadcasts, JobScheduler triggers, or ContentObservers where applicable.

- Provide adaptive icon assets and test launcher presentation across form factors.

- Test on emulator system images for API 26 and API 27 and on Project Treble-enabled devices to catch vendor-specific behavior.

Operational steps for device owners and admins: check Settings → System → About for build and patch level, enable automatic system updates where available, back up user data before major upgrades, and verify critical corporate apps against API 26/27 emulator images or physical test devices to confirm notification behavior and background-task reliability.

Version IDs &amp; Release Timeline

Set targetSdkVersion to 27 and validate behavior on API 26 and API 27 images; keep minSdkVersion at a level that matches your user base (commonly 21+) while using support libraries for backward compatibility.

API 26 reached stable release on 2017-08-21 (introduced notification channels, background execution limits, autofill framework and picture-in-picture). API 27 reached stable release on 2017-12-05 (added the Neural Networks API (NNAPI), android. If you have any issues with regards to where and how to use [[http://procurement.gov.ck/wordpress/?p=72498|1xbet download android]], you can make contact with us at the web-site. os.SharedMemory and several smaller API additions and fixes).

Developer previews for the line began on 2017-03-21, followed by public betas through spring/summer of 2017; the first stable build (API 26) rolled out in late August 2017, with the maintenance/feature refresh (API 27) finalized in December 2017.

Security updates were distributed monthly by Google during the active support window; OEM cadence varied (Pixel-class devices received monthly updates, many vendors moved to quarterly). Maintain an update policy that treats monthly patches as the baseline for flagship devices and quarterly for wider fleet management.

Practical checklist for developers and release managers: pin CI/emulator images to API 26 and API 27, add automated tests for background execution limits, notification channels and autofill flows, include NNAPI smoke tests if using on-device ML, and document any behavior changes tied to targetSdkVersion 27 in your release notes.

Zusammenfassung

Hinweis: Durch das Bearbeiten dieser Seite geben Sie Ihr Einverständnis, dass Ihr Inhalt unter der folgenden Lizenz veröffentlicht wird: CC Attribution-Share Alike 4.0 International