# aosp

AOSP (Android Open Source Project) is the open-source documentation and source code for Android, a production-quality developer platform that can be customized and ported.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Accelerating development for massive Git repositories

DevFeed: [Accelerating development for massive Git repositories](<https://devfeed.tech/articles/accelerating-development-for-massive-git-repositories-138168.md>)

Original publisher: [Read original article](<https://developers.googleblog.com/accelerating-development-for-massive-git-repositories/>)

Author: The Android ABFS Team

Published: 2026-11-17T18:09:46.914988Z

Content type: article

Language: en

Sources: [Google Developers Blog](<https://devfeed.tech/sources/google-developers-blog.md>)

Topics: [aosp](<https://devfeed.tech/topics/aosp.md>), [Git](<https://devfeed.tech/topics/git.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Gerrit](<https://devfeed.tech/topics/gerrit.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [acceleration](<https://devfeed.tech/tags/acceleration.md>), [android](<https://devfeed.tech/tags/android.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cache](<https://devfeed.tech/tags/cache.md>), [content](<https://devfeed.tech/tags/content.md>), [development](<https://devfeed.tech/tags/development.md>), [file](<https://devfeed.tech/tags/file.md>), [filesystem](<https://devfeed.tech/tags/filesystem.md>), [git](<https://devfeed.tech/tags/git.md>), [google](<https://devfeed.tech/tags/google.md>), [open](<https://devfeed.tech/tags/open.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [service](<https://devfeed.tech/tags/service.md>), [source](<https://devfeed.tech/tags/source.md>)

### AI overview

ABFS speeds work on large Android repositories by mounting a virtual filesystem that fetches file contents on demand and shares cached build results. Its Linux kernel module, host daemons, and server use content hashes to store Git objects, workspace changes, and build outputs. CASFS exposes file metadata before downloading bytes; its tap utility records files a build reads or changes, and Ninja-go uses content-addressable caching for Ninja builds. The article reports that agents can mount Android release branches in under eight seconds, check out a tree in under ten seconds, and complete a full build in under ten minutes. These results are from runs on a 64-vCPU GCE VM with the ABFS server in the same cloud network. ABFS is open source; Android Soong/Ninja was its first target, with a Bazel proof of concept and other projects exploring compatibility.

### Source excerpt

Meet Another Build File Service (ABFS), Google's open-source content-addressable filesystem and build cache that cuts Android checkouts to <8s and builds to ~2m.

## Cuttlefish on Mac: Running Android's Virtual Device Framework Natively on Apple Silicon

DevFeed: [Cuttlefish on Mac: Running Android's Virtual Device Framework Natively on Apple Silicon](<https://devfeed.tech/articles/cuttlefish-on-mac-running-android-s-virtual-device-framework-natively-on-apple-silicon-134031.md>)

Original publisher: [Read original article](<https://engineering.fb.com/2026/11/13/android/cuttlefish-on-mac/>)

Author: Hadrien Zalek; Joe Knox; Alex Chong; Marcel Apfelbaum

Published: 2026-11-13T17:00:39Z

Content type: article

Language: en

Sources: [Engineering at Meta](<https://devfeed.tech/sources/engineering-at-meta.md>)

Topics: [macOS](<https://devfeed.tech/topics/macos.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Android](<https://devfeed.tech/topics/android.md>), [aosp](<https://devfeed.tech/topics/aosp.md>)

Tags: [3d](<https://devfeed.tech/tags/3d.md>), [android](<https://devfeed.tech/tags/android.md>), [apple](<https://devfeed.tech/tags/apple.md>), [apple-silicon](<https://devfeed.tech/tags/apple-silicon.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cuttlefish](<https://devfeed.tech/tags/cuttlefish.md>), [device](<https://devfeed.tech/tags/device.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [framework](<https://devfeed.tech/tags/framework.md>), [labs](<https://devfeed.tech/tags/labs.md>), [mac](<https://devfeed.tech/tags/mac.md>), [macos](<https://devfeed.tech/tags/macos.md>), [meta](<https://devfeed.tech/tags/meta.md>), [qemu](<https://devfeed.tech/tags/qemu.md>), [reality-labs](<https://devfeed.tech/tags/reality-labs.md>), [virtual](<https://devfeed.tech/tags/virtual.md>)

### AI overview

Meta ported Android's Cuttlefish virtual-device framework to run natively on Apple silicon Macs, enabling developers to use the same higher-fidelity virtual devices in local development and CI. The port revived Cuttlefish's QEMU backend and addressed three Linux-specific gaps: vhost-user components were made buildable on macOS, QEMU's Hypervisor.framework backend gained more memory-region tracking, and native display, build, and signing support were added. The Cocoa display supports BGRA rendering, pointer-to-touch input, and configurable geometry. Mac builds require a JIT entitlement, code signing, and notarization. The unified platform reduces the burden of maintaining Goldfish and Cuttlefish separately and supports capabilities including Bluetooth, Wi-Fi, cellular, 3D graphics, OTA testing, fastboot, and snapshots. Meta shares the work through its qemu-wearables fork and cuttlefish-wearables patch set, while exploring upstream contributions.

### Source excerpt

How Meta's Reality Labs brought Cuttlefish and its QEMU backend to macOS and Apple silicon. [...] Read More... The post Cuttlefish on Mac: Running Android's Virtual Device Framework Natively on Apple Silicon appeared first on Engineering at Meta.

## A banking malware sample led researchers to an Android bug that can loop-crash phones

DevFeed: [A banking malware sample led researchers to an Android bug that can loop-crash phones](<https://devfeed.tech/articles/a-banking-malware-sample-led-researchers-to-an-android-bug-that-can-loop-crash-phones-118742.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/11/05/ghostmap-android-bug-research/>)

Author: Mirko Zorz

Published: 2026-11-05T09:00:02Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [APK](<https://devfeed.tech/topics/apk.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [Malware](<https://devfeed.tech/topics/malware.md>), [Library](<https://devfeed.tech/topics/library.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [android](<https://devfeed.tech/tags/android.md>), [android-17](<https://devfeed.tech/tags/android-17.md>), [apk](<https://devfeed.tech/tags/apk.md>), [app](<https://devfeed.tech/tags/app.md>), [banking](<https://devfeed.tech/tags/banking.md>), [bitdefender](<https://devfeed.tech/tags/bitdefender.md>), [bug](<https://devfeed.tech/tags/bug.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [comes](<https://devfeed.tech/tags/comes.md>), [crash](<https://devfeed.tech/tags/crash.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [factory](<https://devfeed.tech/tags/factory.md>), [factory-reset](<https://devfeed.tech/tags/factory-reset.md>), [first](<https://devfeed.tech/tags/first.md>), [ghostmap](<https://devfeed.tech/tags/ghostmap.md>), [help](<https://devfeed.tech/tags/help.md>), [hot-stuff](<https://devfeed.tech/tags/hot-stuff.md>), [malware](<https://devfeed.tech/tags/malware.md>), [news](<https://devfeed.tech/tags/news.md>), [phones](<https://devfeed.tech/tags/phones.md>), [research](<https://devfeed.tech/tags/research.md>), [sample](<https://devfeed.tech/tags/sample.md>), [software](<https://devfeed.tech/tags/software.md>), [zimperium](<https://devfeed.tech/tags/zimperium.md>)

### AI overview

Bitdefender Labs traced GhostMap to a gap between two Android ZIP-handling libraries: an APK entry using an unsupported compression method can pass inconsistent checks, be mapped larger than the file, and trigger a SIGBUS on read. Depending on the malformed entry, installation can crash or a system process can repeatedly crash during reboot, leaving a Pixel 10 in a loop that may require a data-erasing factory reset. Bitdefender reproduced the issue on Android 10 through 17 in AOSP testing, including a Pixel 10 on Android 17 with the August 5, 2026 patch; it did not test other manufacturers. Google classified the report as outside the scope of a security fix and may consider it for a future version. Bitdefender reports no observed in-the-wild use, has no CVE, and does not establish whether app-store review would catch a malicious APK.

### Source excerpt

Bitdefender Labs researchers built an Android app that contains no executable code and requests no permissions, and installing it leaves a Pixel 10 in a crash loop that can take a factory reset to clear. The flaw, which Bitdefender calls GhostMap, comes from how Android reads the ZIP structure inside an APK. The app does not need to be opened. The team reproduced the loop on a Pixel 10 running Android 17 with the August ... More -> The post A banking malware sample led researchers to an Android bug that can loop-crash phones appeared first on Help Net Security.

## GrapheneOS, LineageOS, /e/OS and Others Are Now Officially Supported

DevFeed: [GrapheneOS, LineageOS, /e/OS and Others Are Now Officially Supported](<https://devfeed.tech/articles/grapheneos-lineageos-e-os-and-others-are-now-officially-supported-116251.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/android-apps-everywhere-even-without-google/>)

Author: Shai Almog

Published: 2026-11-04T00:00:00Z

Content type: release

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [LineageOS](<https://devfeed.tech/topics/lineageos.md>), [GrapheneOS](<https://devfeed.tech/topics/grapheneos.md>), [aosp](<https://devfeed.tech/topics/aosp.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [grapheneos](<https://devfeed.tech/tags/grapheneos.md>), [ios](<https://devfeed.tech/tags/ios.md>), [layer](<https://devfeed.tech/tags/layer.md>), [lineageos](<https://devfeed.tech/tags/lineageos.md>), [os](<https://devfeed.tech/tags/os.md>), [room](<https://devfeed.tech/tags/room.md>), [workmanager](<https://devfeed.tech/tags/workmanager.md>)

### AI overview

Codename One now officially supports GrapheneOS, LineageOS, CalyxOS, /e/OS and other AOSP builds with a single APK. At runtime it checks for Google Play Services; CI checks that the Android port does not call Play services, Play Core or Firebase without first checking. Push can use UnifiedPush with a VAPID public key build hint, without app-code or server changes. Play Billing remains unavailable without the Play Store. The Android compatibility layer can also build Android Studio projects for iOS, with support for Room (unsupported features fail at build time), WorkManager, location and sensors, services, notifications, Android Keystore APIs and document pickers. On iOS, background work timing is controlled by the system, most foreground services get only a short execution window, and save dialogs cannot report cancellation. Other stated limits include non-hardware-backed keystore keys, single-connection SQLite, no system content providers or broadcasts, and no reflection-based libraries.

### Source excerpt

GrapheneOS, LineageOS, CalyxOS and /e/OS are now officially supported, and the Android layer runs Room, WorkManager and document pickers on iOS.

## Inside Android Layoutlib: How View and Compose Previews Reach the Canvas

DevFeed: [Inside Android Layoutlib: How View and Compose Previews Reach the Canvas](<https://devfeed.tech/articles/inside-android-layoutlib-how-view-and-compose-previews-reach-the-canvas-113140.md>)

Original publisher: [Read original article](<https://proandroiddev.com/inside-android-layoutlib-view-compose-rendering-pipeline-dc5d7f8ac21c?source=rss----c72404660798---4>)

Author: Ravi Rawal

Published: 2026-11-02T14:47:44Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Android](<https://devfeed.tech/topics/android.md>), [aosp](<https://devfeed.tech/topics/aosp.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-framework](<https://devfeed.tech/tags/android-framework.md>), [android-open-source-project](<https://devfeed.tech/tags/android-open-source-project.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [canvas](<https://devfeed.tech/tags/canvas.md>), [compose](<https://devfeed.tech/tags/compose.md>), [device](<https://devfeed.tech/tags/device.md>), [drawing](<https://devfeed.tech/tags/drawing.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [framework](<https://devfeed.tech/tags/framework.md>), [image](<https://devfeed.tech/tags/image.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [inflation](<https://devfeed.tech/tags/inflation.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [layout](<https://devfeed.tech/tags/layout.md>), [layouts](<https://devfeed.tech/tags/layouts.md>), [view](<https://devfeed.tech/tags/view.md>)

### AI overview

Android Studio previews share Layoutlib's host rendering session, but Views and Compose keep different UI representations. For XML, Layoutlib inflates framework Views, resolves resources, then measures, lays out, and draws the hierarchy. For Compose, tooling invokes compiled composable code through a Compose host: a ComposeView sits in the View hierarchy, while Compose owns its internal layout tree. Layoutlib adapts selected framework behavior for desktop rendering; it does not boot Android or guarantee device behavior. A successful preview validates drawing under a selected configuration, not production data loading, lifecycle, window insets, platform services, or every device. The text recommends passing explicit UI state to presentation composables for representative previews, diagnosing failures at the construction, composition, or layout boundary, and using an emulator or device for OS-specific behavior.

### Source excerpt

Trace the rendering pipeline from XML inflation and compiled composables to measurement, drawing, and the final preview image and understand where Layoutlib's responsibilities end. Android Studio can render an XML layout or a Jetpack Compose screen without launching an emulator. The two types are rendered within the same preview window but are rendered differently, i.e. the rendering pipeline in the same way. When you have a view based layout, Android Studio will inflate your Android Viewshierarchy. When using compose, the compose tools will invokes the compiled composable code using the compose host. The Compose runtime will then build its own compose tree. Layoutlib connects these different UI models to a host-side rendering environment. It will not convert compose to views or emulate an entire Android device. That distinction explains the architecture behind Android previews, the role of classes such as Bridge and RenderSessionImpl . It also means that just because you successfully render your preview, it doesn't mean it will behave the same on a real device. The implementation can be found in the Layoutlib repo inside the Android Open Source Project's Layoutlib repository. You can look at the rendering bridge and compose tools source code to see how it all fits together. 1. What Layoutlib actually is Layoutlib is a part of the Android framework that has been adapted and ported to work outside of Android devices. It is used by Android Studio to render layouts. However, it is not a screenshot tool that parses XML and tries to mimic how Android widgets would look. It can instantiate Android framework views, resolve resources, perform layout measurement, and execute drawing operations through the adapted framework. This is important because a lot of how a layout looks is down to how the framework behavior. Text measurement, drawable rendering, padding, resource resolution, and parent-child layout rules all influence the resulting pixels. A renderer that merely appro

## You Can Reserve This Small-Factor, De-Googled Phone for $30

DevFeed: [You Can Reserve This Small-Factor, De-Googled Phone for $30](<https://devfeed.tech/articles/you-can-reserve-this-small-factor-de-googled-phone-for-30-93091.md>)

Original publisher: [Read original article](<https://feed.itsfoss.com/link/24361/17502193/brax-wink-pre-order>)

Author: Sourav Rudra

Published: 2026-10-21T17:12:00Z

Content type: news

Language: en

Sources: [It's FOSS](<https://devfeed.tech/sources/it-s-foss.md>)

Topics: [aosp](<https://devfeed.tech/topics/aosp.md>), [keyboard](<https://devfeed.tech/topics/keyboard.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Pinephone](<https://devfeed.tech/topics/pinephone.md>)

Tags: [5g](<https://devfeed.tech/tags/5g.md>), [android](<https://devfeed.tech/tags/android.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [apps](<https://devfeed.tech/tags/apps.md>), [banking](<https://devfeed.tech/tags/banking.md>), [based](<https://devfeed.tech/tags/based.md>), [batch](<https://devfeed.tech/tags/batch.md>), [big-tech](<https://devfeed.tech/tags/big-tech.md>), [bluetooth](<https://devfeed.tech/tags/bluetooth.md>), [bluetooth-5-4](<https://devfeed.tech/tags/bluetooth-5-4.md>), [camera](<https://devfeed.tech/tags/camera.md>), [device](<https://devfeed.tech/tags/device.md>), [display](<https://devfeed.tech/tags/display.md>), [encrypted](<https://devfeed.tech/tags/encrypted.md>), [esim](<https://devfeed.tech/tags/esim.md>), [gadgets](<https://devfeed.tech/tags/gadgets.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [include](<https://devfeed.tech/tags/include.md>), [keyboard](<https://devfeed.tech/tags/keyboard.md>), [news](<https://devfeed.tech/tags/news.md>), [phone](<https://devfeed.tech/tags/phone.md>), [wink](<https://devfeed.tech/tags/wink.md>)

### AI overview

The Brax Wink combines a 4-inch OLED touchscreen with a clip-on QWERTY keyboard and BraxOS, an Android-based system without Google services. Setup offers Omni, a fuller Android experience, or Zero, limited to encrypted communications and optional navigation. Most Android apps reportedly run, but apps requiring Google integrity services--including some banking apps--may not. A configurable hardware switch can disable selected radios and sensors; wipe triggers include restarts, extended powered-off periods, repeated failed unlocks, and a duress password. Brax promises updates through 2032 and says BraxOS can be built from source. Reservations start with a $30 refundable deposit toward $550, with the balance due around July 2027 and shipping planned for September; full-price $449 buyers are slated for July shipment. The article notes dates may change.

### Source excerpt

The Brax Wink is a 4-inch phone that runs BraxOS and has a keyboard that clips onto the back.

## Releasing Palm OS Archive, Developer Rediscovers Working Virus After 25 Years

DevFeed: [Releasing Palm OS Archive, Developer Rediscovers Working Virus After 25 Years](<https://devfeed.tech/articles/releasing-palm-os-archive-developer-rediscovers-working-virus-after-25-years-89780.md>)

Original publisher: [Read original article](<https://mobile.slashdot.org/story/26/10/18/002223/releasing-palm-os-archive-developer-rediscovers-working-virus-after-25-years>)

Author: EditorDavid

Published: 2026-10-18T14:34:00Z

Content type: news

Language: en

Sources: [Slashdot](<https://devfeed.tech/sources/slashdot.md>)

Topics: [Retrocomputing](<https://devfeed.tech/topics/retrocomputing.md>), [aosp](<https://devfeed.tech/topics/aosp.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [github](<https://devfeed.tech/tags/github.md>), [handheld](<https://devfeed.tech/tags/handheld.md>), [os](<https://devfeed.tech/tags/os.md>), [programming](<https://devfeed.tech/tags/programming.md>), [retrocomputing](<https://devfeed.tech/tags/retrocomputing.md>), [virus](<https://devfeed.tech/tags/virus.md>)

### AI overview

A Palm OS developer released a 1.5 GB archive of historical development resources, including SDKs, documentation, examples, and utilities. He also rediscovered source code for a self-replicating virus he developed and tested in 2001; its source code and binaries will remain private.

### Source excerpt

Long-time Slashdot reader ardiri remembers his days writing applications for the Palm OS. And he's now released approximately 1.5 GB of historical Palm OS development resources, "accumulated during the early days of handheld computing and preserved on hard drive backups for more than 25 years... to preserve the tools and knowledge that helped define an important era of personal computing." The collection includes historical SDKs, developer conference presentations, technical documentation, programming examples, limited source code, and development utilities. (ROM images, commercial applications, and simulator binaries have deliberately been excluded....) Making a broader collection of development resources available to the retrocomputing community, the archive is available at GitHub.com/ardiri/dev-palmos and is intended for historical preservation, education, and research, particularly as enthusiasts continue working to maintain, emulate, and revive the platform... Ardiri has also written an auto-biography and has started explored the engineering principles behind these systems in his books. And somewhere along the way, Ardiri rediscovered the original source code for "The Palm OS Virus That Never Was -- Lost for 25 Years, Found in 2026." Lurking on a CompactFlash card containing files dated June 2001, he found the self-replicating Palm OS virus that he'd developed and tested in June 2001, months before the planned PalmSource developer conference in San Jose. Named 'Virii,' the virus intercepted Palm OS system calls to progressively infect legitimate applications while preserving their original functionality. Infected applications could then spread between handheld devices through infrared beaming, potentially allowing an infection to propagate among hundreds of developers exchanging software at the conference. The virus also included a date-triggered payload designed to interfere with system time reporting between October 23 and 27, 2001, potentially causing erratic

## Can an AI copy itself? Inside Anthropic's 15-TV-box experiment

DevFeed: [Can an AI copy itself? Inside Anthropic's 15-TV-box experiment](<https://devfeed.tech/articles/can-an-ai-copy-itself-inside-anthropic-s-15-tv-box-experiment-87016.md>)

Original publisher: [Read original article](<https://blog.adafruit.com/2026/10/14/can-an-ai-copy-itself-inside-anthropics-15-tv-box-experiment/>)

Author: Anne Barela

Published: 2026-10-14T14:42:00Z

Content type: news

Language: en

Sources: [Adafruit Industries](<https://devfeed.tech/sources/adafruit-industries-makers-hackers-artists-designers-and-engineers.md>)

Topics: [aosp](<https://devfeed.tech/topics/aosp.md>), [anthropic](<https://devfeed.tech/topics/anthropic.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>), [robolectric](<https://devfeed.tech/topics/robolectric.md>), [World models](<https://devfeed.tech/topics/world-models.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [android](<https://devfeed.tech/tags/android.md>), [android-tv](<https://devfeed.tech/tags/android-tv.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [gemma4](<https://devfeed.tech/tags/gemma4.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [qwen3](<https://devfeed.tech/tags/qwen3.md>), [red-team](<https://devfeed.tech/tags/red-team.md>)

### AI overview

Anthropic Frontier Red Team research tested whether AI systems could replicate themselves across inexpensive Android TV boxes and other hardware. A model split across 15 boxes generated 0.39 tokens per second. Separate tests found that a smaller model could set up inference with inherited notes, while GLM-5.2 reached eight Android emulator nodes through an exposed debugging port. The research says the thresholds do not yet overlap: smaller models fit but are unreliable, and the model that completed the chain is too large for the devices.

### Source excerpt

Ashu Kumar, writing at The Agentic Stack, covers Anthropic Frontier Red Team research published October 12 on whether an AI system can replicate itself onto cheap hardware. The team split Gemma4-26B-A4B across 15 off-brand Android TV boxes, each about $55 with 4 GB of memory, and got 0.39 generated tokens per second. Slow for a [...]

## EuroBSDCon Trip Report - Federico Angelilli

DevFeed: [EuroBSDCon Trip Report - Federico Angelilli](<https://devfeed.tech/articles/eurobsdcon-trip-report-federico-angelilli-86286.md>)

Original publisher: [Read original article](<https://freebsdfoundation.org/blog/eurobsdcon-trip-report-federico-angelilli/>)

Author: Florine Kamdem

Published: 2026-10-13T17:44:12Z

Content type: article

Language: en

Sources: [FreeBSD Foundation](<https://devfeed.tech/sources/freebsd-foundation.md>)

Topics: [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [linux foundation](<https://devfeed.tech/topics/linux-foundation.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [development-kit](<https://devfeed.tech/tags/development-kit.md>), [event](<https://devfeed.tech/tags/event.md>), [freebsd](<https://devfeed.tech/tags/freebsd.md>), [google-summer-of-code](<https://devfeed.tech/tags/google-summer-of-code.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [practical](<https://devfeed.tech/tags/practical.md>), [trip-report](<https://devfeed.tech/tags/trip-report.md>)

### AI overview

A Google Summer of Code participant reports on presenting his FreeBSD live-patching work and attending EuroBSDCon. He recounts conference talks, discussions, tutorials, and feedback from other developers.

### Source excerpt

This year, I had the great opportunity to participate in the Google Summer of Code for the FreeBSD Project. After my proposal for "Live-patching for the FreeBSD kernel" was accepted, I worked for three months to make the first revision of the subsystem and associated tooling. My mentors, Bojan Novkovic and Mateusz Piotrowski, recommended that [...] The post EuroBSDCon Trip Report - Federico Angelilli first appeared on FreeBSD Foundation.

## Valve Quietly Open-Sources Its Android Compatibility Layer

DevFeed: [Valve Quietly Open-Sources Its Android Compatibility Layer](<https://devfeed.tech/articles/valve-quietly-open-sources-its-android-compatibility-layer-48042.md>)

Original publisher: [Read original article](<https://feed.itsfoss.com/link/24361/17465915/valve-lepton>)

Author: Sourav Rudra

Published: 2026-09-18T10:47:55Z

Content type: news

Language: en

Sources: [It's FOSS](<https://devfeed.tech/sources/it-s-foss.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [LineageOS](<https://devfeed.tech/topics/lineageos.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-open-source-project](<https://devfeed.tech/tags/android-open-source-project.md>), [aosp](<https://devfeed.tech/tags/aosp.md>), [app](<https://devfeed.tech/tags/app.md>), [arm](<https://devfeed.tech/tags/arm.md>), [client](<https://devfeed.tech/tags/client.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [container](<https://devfeed.tech/tags/container.md>), [developers](<https://devfeed.tech/tags/developers.md>), [filesystem](<https://devfeed.tech/tags/filesystem.md>), [game](<https://devfeed.tech/tags/game.md>), [games](<https://devfeed.tech/tags/games.md>), [gaming](<https://devfeed.tech/tags/gaming.md>), [gpl](<https://devfeed.tech/tags/gpl.md>), [layer](<https://devfeed.tech/tags/layer.md>), [lepton](<https://devfeed.tech/tags/lepton.md>), [news](<https://devfeed.tech/tags/news.md>), [steam](<https://devfeed.tech/tags/steam.md>), [steam-frame](<https://devfeed.tech/tags/steam-frame.md>), [valve](<https://devfeed.tech/tags/valve.md>), [vr](<https://devfeed.tech/tags/vr.md>)

### AI overview

Valve has open-sourced Lepton, the Android compatibility layer built for Steam Frame. It launches Android games inside Linux containers; the Steam client handles it for most users. The project targets developers bringing VR-focused Android games to Steam Frame, though the repository notes other possible uses. Its compat tool, which Steam invokes to launch games, uses the MIT license, while the Android root filesystem is GPL-3.0 because it incorporates outside projects. The image builds on AOSP, LineageOS, and Waydroid, with Boringdroid also listed among its components. Lepton is deliberately limited rather than general-purpose: apps share a user without isolation, games are intended to run in separate containers, and unneeded Android services are disabled at launch.

### Source excerpt

The Lepton project is aimed at game developers who want to bring VR-focused Android titles over to Steam Frame.

## The Thumb That Ran Ahead of the Finger: Anatomy of a Compose Slider Bug

DevFeed: [The Thumb That Ran Ahead of the Finger: Anatomy of a Compose Slider Bug](<https://devfeed.tech/articles/the-thumb-that-ran-ahead-of-the-finger-anatomy-of-a-compose-slider-bug-22952.md>)

Original publisher: [Read original article](<https://proandroiddev.com/the-thumb-that-ran-ahead-of-the-finger-anatomy-of-a-compose-slider-bug-ddec306251d0?source=rss----c72404660798---4>)

Author: Vitaliy Gribko

Published: 2026-09-14T04:19:34Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [code analysis](<https://devfeed.tech/topics/code-analysis.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [Design system](<https://devfeed.tech/topics/design-system.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [human review](<https://devfeed.tech/topics/human-review.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [aosp](<https://devfeed.tech/tags/aosp.md>), [bug](<https://devfeed.tech/tags/bug.md>), [compose](<https://devfeed.tech/tags/compose.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [design-system](<https://devfeed.tech/tags/design-system.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

A custom Compose range slider inherited mid-drag tick snapping from a View-based implementation. It kept the finger's raw position separate from the displayed snapped position, so the thumb jumped ahead; asynchronous settling could also cancel a new drag or let range thumbs cross. The fix draws from the raw position during dragging and snaps on release, synchronously for the range slider and with animation for the single-thumb slider. Removing duplicate snapped states, the snap helper, an animation class, and coroutine machinery cut more code than it added. A companion reset bug arose when a keyed `remember` created new state but `LaunchedEffect(Unit)` kept observing the old object; an AI reviewer identified the mismatch, and the effect was keyed to the reset signal. The article presents these as findings from this component and review, with the reported thumb-crossing race described as a reconstruction that was not reproduced on camera.

### Source excerpt

A bug report sat in the backlog for seven months. The fix took a day, deleted a third of the slider's logic, and was almost shipped with a second bug inside -- until a machine read my diff better than I did. This is the whole story: the ported behavior that never made sense, the race nobody reported, and why the best fixes remove code. The report The bug report was seven months old when it reached me. A QA engineer had filed it in December, with a screen recording and three steps: Open the people search filters. Grab the right-hand thumb of the age range slider. Drag it slowly to the left. The recording showed the problem in two seconds. The thumb does not follow the finger. It sprints ahead -- you are still crossing the gap between two ticks, and the thumb is already standing on the next one, waiting for you, like a dog that runs to the park while you are still tying your shoes. Expected: the thumb moves with the finger. Actual: it escapes. On a budget phone, on two Android versions, every time. Not a race condition, not a flake -- a perfectly deterministic lie, filmed in December, assigned to a fix-day in July. Seven months is not negligence. It is the natural half-life of a visual glitch filed as minor against a screen nobody dies on. The age filter works. You tap a tick, the value applies. Only the drag -- the one gesture the slider exists for -- feels wrong in a way that is hard to screenshot and easy to deprioritize. When the ticket finally landed on my desk, a colleague glanced at it and asked whether it had already been fixed once. It had not. But I understood his confusion later, when I opened the slider's source and found a comment that explained everything -- including why this bug felt so old. The comment that confessed The slider is not the framework's slider. Our design system ships its own Compose slider, forked from the AOSP Material one, because design needed three knobs the framework does not expose: a custom thumb radius, a custom track height, a differ

## I ported Kubernetes to the browser

DevFeed: [I ported Kubernetes to the browser](<https://devfeed.tech/articles/i-ported-kubernetes-to-the-browser-83249.md>)

Original publisher: [Read original article](<https://ngrok.com/blog/i-ported-kubernetes-to-the-browser>)

Author: Sam Rose

Published: 2026-06-30T00:00:00Z

Content type: article

Language: en

Sources: [\[ngrok news\]](<https://devfeed.tech/sources/ngrok-news.md>)

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [ai slop pull requests](<https://devfeed.tech/topics/ai-slop-pull-requests.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [slop](<https://devfeed.tech/tags/slop.md>)

### AI overview

The author describes webernetes, a partial TypeScript port of Kubernetes that runs simulated clusters in a browser for interactive teaching content. They explain how they used LLMs to port much of the code, then reviewed it and built extensive unit and integration tests comparing its behavior with real Kubernetes running on k3s. The article discusses common LLM porting errors and argues that code review and tests are both necessary for confidence in generated code.

### Source excerpt

Almost 100,000 lines of LLM-generated code in 2 months, and none of it is slop.

## The Android Developer's Journey into Hardware Observability

DevFeed: [The Android Developer's Journey into Hardware Observability](<https://devfeed.tech/articles/the-android-developer-s-journey-into-hardware-observability-47173.md>)

Original publisher: [Read original article](<https://interrupt.memfault.com/blog/aosp-observability>)

Author: Victor Lai

Published: 2025-02-28T00:00:00Z

Content type: article

Language: en

Sources: [Interrupt](<https://devfeed.tech/sources/interrupt.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [Android](<https://devfeed.tech/topics/android.md>), [Hardware](<https://devfeed.tech/topics/hardware.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-open-source-project](<https://devfeed.tech/tags/android-open-source-project.md>), [aosp](<https://devfeed.tech/tags/aosp.md>), [developer](<https://devfeed.tech/tags/developer.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [observability](<https://devfeed.tech/tags/observability.md>), [os](<https://devfeed.tech/tags/os.md>), [smartphones](<https://devfeed.tech/tags/smartphones.md>), [soc](<https://devfeed.tech/tags/soc.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

This article examines how observability tooling for AOSP-based Android hardware grows from a small number of devices to deployments of thousands. It describes the complexity of managing Android apps, native services, ODM customizations, hardware drivers, and limited OS source-code access.

### Source excerpt

In this article, I walk through how the growth of internal observability tooling for an AOSP device might look like, and the variety of pitfalls one might encounter as they scale from 1s to 10s to 1000s of Android devices in the field, based off my experience talking to AOSP developers and teams, and personally as an Android app developer working on AOSP hardware. Continue reading...

## #51 - My developer blogging journey so far

DevFeed: [#51 - My developer blogging journey so far](<https://devfeed.tech/articles/51-my-developer-blogging-journey-so-far-25697.md>)

Original publisher: [Read original article](<https://blog.shreyaspatil.dev/51-my-developer-blogging-journey-so-far/>)

Author: Shreyas Patil

Published: 2025-02-18T14:10:44Z

Content type: opinion

Language: en

Sources: [Shreyas Patil's Blog](<https://devfeed.tech/sources/shreyas-patil-s-blog.md>)

Topics: [Publishing](<https://devfeed.tech/topics/publishing.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [SDK](<https://devfeed.tech/topics/sdk.md>)

Tags: [2019](<https://devfeed.tech/tags/2019.md>), [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [article](<https://devfeed.tech/tags/article.md>), [better](<https://devfeed.tech/tags/better.md>), [blog](<https://devfeed.tech/tags/blog.md>), [blogging](<https://devfeed.tech/tags/blogging.md>), [blogs](<https://devfeed.tech/tags/blogs.md>), [building](<https://devfeed.tech/tags/building.md>), [career](<https://devfeed.tech/tags/career.md>), [code](<https://devfeed.tech/tags/code.md>), [content-creation](<https://devfeed.tech/tags/content-creation.md>), [contribute](<https://devfeed.tech/tags/contribute.md>), [contributed](<https://devfeed.tech/tags/contributed.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [journey](<https://devfeed.tech/tags/journey.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [personal](<https://devfeed.tech/tags/personal.md>), [sharing](<https://devfeed.tech/tags/sharing.md>), [technical-documentation](<https://devfeed.tech/tags/technical-documentation.md>), [technical-writing-1](<https://devfeed.tech/tags/technical-writing-1.md>), [writing](<https://devfeed.tech/tags/writing.md>)

### AI overview

In 2019, while building an Android app, the author needed pagination for Firebase Realtime Database, which FirebaseUI-Android did not then support. They developed a pagination API, first used it in their own app and GitHub project, then contributed it to the official SDK. Hoping it would help other developers, they wrote a Medium article, revised it in response to ProAndroidDev editors' suggestions, and published their first tech blog on April 8, 2019. The excerpt ends as they begin describing what happened after sharing the post, so it does not establish the rest of their blogging journey or career impact.

### Source excerpt

A personal account of my journey as a tech blogger, from my first post in 2019 to becoming a GDE. Insights on English barriers, criticism, and why sharing matters.

## The Starter kit for Android Platform Engineering

DevFeed: [The Starter kit for Android Platform Engineering](<https://devfeed.tech/articles/the-starter-kit-for-android-platform-engineering-28364.md>)

Original publisher: [Read original article](<https://siddroid.com/post/android/the-starter-kit-for-android-platform-engineering/>)

Author: Siddhesh Patil

Published: 2024-06-21T11:50:55Z

Content type: tutorial

Language: en

Sources: [Sid Patil - Android Engineer and Kotlin Advocate](<https://devfeed.tech/sources/sid-patil-android-engineer-and-kotlin-advocate.md>)

Topics: [aosp](<https://devfeed.tech/topics/aosp.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [Android](<https://devfeed.tech/topics/android.md>), [ide](<https://devfeed.tech/topics/ide.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Ubuntu](<https://devfeed.tech/topics/ubuntu.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-15](<https://devfeed.tech/tags/android-15.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [android-open-source-project](<https://devfeed.tech/tags/android-open-source-project.md>), [android-os-build](<https://devfeed.tech/tags/android-os-build.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [android-system-ui](<https://devfeed.tech/tags/android-system-ui.md>), [aosp](<https://devfeed.tech/tags/aosp.md>), [aosp-build](<https://devfeed.tech/tags/aosp-build.md>), [aosp-build-tools](<https://devfeed.tech/tags/aosp-build-tools.md>), [aosp-development](<https://devfeed.tech/tags/aosp-development.md>), [aosp-environment-setup](<https://devfeed.tech/tags/aosp-environment-setup.md>), [aosp-guide](<https://devfeed.tech/tags/aosp-guide.md>), [aosp-installation](<https://devfeed.tech/tags/aosp-installation.md>), [aosp-machine-configuration](<https://devfeed.tech/tags/aosp-machine-configuration.md>), [aosp-setup](<https://devfeed.tech/tags/aosp-setup.md>), [aosp-step-by-step](<https://devfeed.tech/tags/aosp-step-by-step.md>), [aosp-tutorial](<https://devfeed.tech/tags/aosp-tutorial.md>), [articles-by-sid-patil](<https://devfeed.tech/tags/articles-by-sid-patil.md>), [build-android-from-source](<https://devfeed.tech/tags/build-android-from-source.md>), [build-aosp](<https://devfeed.tech/tags/build-aosp.md>), [custom-android-build](<https://devfeed.tech/tags/custom-android-build.md>), [full-system-build-aosp](<https://devfeed.tech/tags/full-system-build-aosp.md>), [guide](<https://devfeed.tech/tags/guide.md>), [ide](<https://devfeed.tech/tags/ide.md>), [ide-configuration-for-aosp](<https://devfeed.tech/tags/ide-configuration-for-aosp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [linux](<https://devfeed.tech/tags/linux.md>), [machine-setup-for-aosp](<https://devfeed.tech/tags/machine-setup-for-aosp.md>), [md3](<https://devfeed.tech/tags/md3.md>), [monet](<https://devfeed.tech/tags/monet.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [system-ui-apk](<https://devfeed.tech/tags/system-ui-apk.md>), [tiramisu](<https://devfeed.tech/tags/tiramisu.md>), [ubuntu](<https://devfeed.tech/tags/ubuntu.md>)

### AI overview

A practical guide to Android platform engineering that covers setting up an Ubuntu machine, configuring development tools, building the Android Open Source Project, preparing test devices, and booting an Android system image.

### Source excerpt

Unlock the secrets of the Android Open Source Project (AOSP) with a comprehensive guide to Platform Engineering. This article covers everything from machine setup and IDE configuration to compiling a full Android system builds for Google Pixels.

## ML Kit Document Scanner in action

DevFeed: [ML Kit Document Scanner in action](<https://devfeed.tech/articles/ml-kit-document-scanner-in-action-25944.md>)

Original publisher: [Read original article](<https://medium.com/google-developer-experts/ml-kit-document-scanner-in-action-1c3a49ef5a33?source=rss-cbfc736ddcd3------2>)

Author: Julien Salvi

Published: 2024-04-15T09:53:27Z

Content type: tutorial

Language: en

Sources: [Julien Salvi](<https://devfeed.tech/sources/stories-by-julien-salvi-on-medium.md>)

Topics: [ML Kit](<https://devfeed.tech/topics/ml-kit.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [Library](<https://devfeed.tech/topics/library.md>), [Image](<https://devfeed.tech/topics/image.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>)

Tags: [aircall](<https://devfeed.tech/tags/aircall.md>), [android](<https://devfeed.tech/tags/android.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [api](<https://devfeed.tech/tags/api.md>), [flow](<https://devfeed.tech/tags/flow.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [ml-kit](<https://devfeed.tech/tags/ml-kit.md>), [ml-kit-android](<https://devfeed.tech/tags/ml-kit-android.md>), [scan](<https://devfeed.tech/tags/scan.md>), [scanner](<https://devfeed.tech/tags/scanner.md>)

### AI overview

ML Kit Document Scanner adds in-app document capture for Android through a scan flow delivered by Google Play Services, so the article says apps need no camera permission and gain about 300 KB in download size. It provides automatic capture, edge detection, rotation, and three editing modes: basic, filters, or ML image cleaning. Developers can set a page limit, allow gallery import, and choose PDF or JPEG output. The article describes integrating it into Aircall messaging: configure the scanner, launch it with an ActivityResultLauncher, retrieve the PDF cache path, and use FileProvider to expose the file URI for upload. Aircall built a proof of concept in a day and later released the feature for sending scanned documents as MMS. The library was still in beta; the author notes PDF-generation controls such as image compression as a desired improvement.

### Source excerpt

Recently, ML Kit released a new library to digitize physical documents directly from your Android application. ML Kit Document Scanner allows the users to easily scan documents with maximum controls and minimum code integration. During my time at Aircall, I took some time to explore and integrate the library to build an Android-exclusive feature for the messaging scope. Discovering the library ML Document Scanner is the newborn of the ML Kit family. It allows users to convert physical documents into digital formats. The library now brings this feature to any apps with many capabilities like applying filters, cleaning the image, removing shadows and many more. The entire scan flow is delivered by the Play Services so no camera permission is mandatory and the library size (~300KB download size increase) has a low impact in your app (the ML models are also managed by the Play Services). So let's dig into the what the library offers. The ML Kit Document Scanner offers key capabilities like a high-quality user interface that ensures consistency across Android applications. With automatic capture and document detection, the users can effortlessly scan documents, while accurate edge detection ensures optimal cropping results. Additionally, automatic rotation detection ensures that scanned documents are presented upright. For developers seeking customization options, the Document Scanner API offers flexibility. You can set a limit on the number of pages scanned and enable or disable the capability to import from the photo gallery. Moreover, there are 3 editing modes available: basic editing capabilities, editing with image filters or editing with ML-enabled image cleaning capabilities (erase stains, fingers...). You will find a complete overview of the library with the official documentation. ML Kit | Google for Developers Build with Document ScannerCrafting the feature It's now time to craft our new feature with ML Kit Document Scanner. Here, we want to give the ability to t

## Android Fragmentation state. Did Google fixed it?

DevFeed: [Android Fragmentation state. Did Google fixed it?](<https://devfeed.tech/articles/android-fragmentation-state-did-google-fixed-it-25962.md>)

Original publisher: [Read original article](<https://proandroiddev.com/android-fragmentation-state-0e7be1649e66?source=rss-7a0a233f88a2------2>)

Author: Kirill Rozov

Published: 2023-10-23T01:40:30Z

Content type: opinion

Language: en

Sources: [Kirill Rozov](<https://devfeed.tech/sources/stories-by-kirill-rozov-on-medium.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>), [aosp](<https://devfeed.tech/topics/aosp.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-11](<https://devfeed.tech/tags/android-11.md>), [android-13](<https://devfeed.tech/tags/android-13.md>), [development](<https://devfeed.tech/tags/development.md>), [fragmentation](<https://devfeed.tech/tags/fragmentation.md>), [google](<https://devfeed.tech/tags/google.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [programming](<https://devfeed.tech/tags/programming.md>), [treble](<https://devfeed.tech/tags/treble.md>)

### AI overview

The article argues that Android fragmentation has become less consequential as Google has moved more updates and features outside the full OS upgrade cycle. It describes vendor delays caused by adapting AOSP releases, chip drivers and manufacturer software, then traces Google's responses: Jetpack compatibility APIs let apps use newer features on older Android versions; Google Play Services distributes services and updates independently on most devices that include it, though the author notes vendors must meet Google's terms and devices without those services need alternatives; Project Treble separates Android from vendor implementation to speed upgrades; Project Mainline makes selected system components independently updateable; and SDK Extensions can expose newer APIs on older releases. The Photo Picker illustrates this shift: introduced in Android 13, the article says it was extended to Android 11+ with Mainline support and later to Android 4.4+ through Play Services. The author's opinion is that annual Android version upgrades matter less to users, while acknowledging continued differences among vendors and devices.

### Source excerpt

Android Fragmentation state. Did Google fix it?Image generated by Kandinsky 2.2 In Android 13 a new feature called Photo Picker appeared. It allows applications to access individual user photos and videos without giving them full access to the photo/video or the entire memory of the device. This is a good feature for limiting an application's access to a user's personal data. It was immediately announced that this feature would also work on Android 11 and newer (with support for Mainline updates), and later its support was added to all devices with Android 4.4 and above via Google Play Services. I immediately asked myself, why hasn't it been done before? And the answer is simple -- Android didn't allow to implement this, because Google was struggling with fragmentation and working on the possibility of an independent update of Android, it became a reality. In this article, I share my opinion about Android fragmentation. You will learn what it is, the reasons for its appearance, and why it is no longer so relevant. I'll also tell you about the ways Google did with this problem in the first 10 years of Android's existence and why device updates to newer versions of Android will not be as important as before. The article is my own opinion and it can be wrong, but I open to discuss it in commentsBrief History of Android OS To understand the problems that OS developers faced, we need to go back in time. The history of Android begins in 2004. Andy Rubin decided to develop an operating system for digital cameras, which were very popular at the time. However, due to funding problems and the pretty small market for digital cameras, the system was refocused on smartphones as a competitor to Symbian and Windows Mobile. In 2005, the company was acquired by Google. The Good Corporation decided to enter the mobile phone market by selling its OS to device manufacturers. In 2007, the Open Handset Alliance was created, and at the same time, Android was announced as an open-source mob

## What's new in Android 14 for developers

DevFeed: [What's new in Android 14 for developers](<https://devfeed.tech/articles/what-s-new-in-android-14-for-developers-25966.md>)

Original publisher: [Read original article](<https://proandroiddev.com/whats-new-in-android-14-1e5d7d8b3482?source=rss-7a0a233f88a2------2>)

Author: Kirill Rozov

Published: 2023-10-04T18:06:41Z

Content type: article

Language: en

Sources: [Kirill Rozov](<https://devfeed.tech/sources/stories-by-kirill-rozov-on-medium.md>)

Topics: [aosp](<https://devfeed.tech/topics/aosp.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-14](<https://devfeed.tech/tags/android-14.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [for-developers](<https://devfeed.tech/tags/for-developers.md>), [pixel8](<https://devfeed.tech/tags/pixel8.md>)

### AI overview

Android 14 tightens background execution and component rules while adding APIs for user-visible work and accessibility. Foreground services must declare a type and its associated permission; Google Play may require apps targeting API 34 to justify the type, and short services have a three-minute limit. Context-registered receivers must declare exported status, may not receive broadcasts while the app is cached, and can receive only one of repeated identical intents. Implicit intents reach exported components only, and mutable PendingIntents using implicit intents throw an exception. For longer user-started data transfers, JobScheduler adds user-initiated jobs that require network criteria and a notification, and are exempt from App Standby Bucket quotas, though the system may stop them. Other changes include partial photo and video access, non-linear font scaling, grammatical inflection, and custom predictive-back animations; the predictive-back preview animation still requires enabling in developer settings.

### Source excerpt

Android 14 is already here, so I took the documentation, experts' reviews, and other available resources to sort out all the important changes that will affect most application developers. Let's examine new restrictions on background mode, changes in Foreground Service, new restrictions on the work of Intent and BroadcastReceiver. In this release, we have many restrictions, but we've also got new features. Thanks for Mishaal Rahman for his articles about Android 14. I based the articles on them.Predictive Back Gesture in actionDemonstration of animation of using back navigation. Source Already in Android 13, we were warned that in the next version of Android, we should expect updates of the Back Gesture and Predictive Back Gesture with animation in the form of a preview screen where we will move. Animation for that preview is still not working. If you want it to work, you should activate it in the developer's settings. Demonstration of animation of using back navigation An example of your personal animation when doing the Back gesture Also, the ability to create personal transition animations inside the application was added. For that, a method handleOnBackProgressed() was added in OnBackPressedCallback. This method is called with the progress of the Back Gesture, as well as the handleOnBackPressed() and handleOnBackCancelled() methods, which are called at the end of the Back Gesture's animation and its cancellation, respectively. On the screen, you can see an example of implementing your custom animation using the Jetpack AppCompat 1.8.0 library. class MainActivity : AppCompatActivity() { override fun onCreate(savedInstanceState: Bundle?) { ... val box = findViewById<View>(R.id.box) val screenWidth = Resources.getSystem().displayMetrics.widthPixels val maxXShift = (screenWidth / 20) val callback = object : OnBackPressedCallback( enabled = true ) { override fun handleOnBackProgressed( backEvent: BackEvent ) { when (backEvent.swipeEdge) { BackEvent.EDGE_LEFT -> box.t

## Fixing Android's 3-minute screen recording limitation

DevFeed: [Fixing Android's 3-minute screen recording limitation](<https://devfeed.tech/articles/fixing-android-s-3-minute-screen-recording-limitation-22886.md>)

Original publisher: [Read original article](<https://maestro.dev/blog/fixing-androids-3-minute-screen-recording-limitation>)

Author: Leland Takamine

Published: 2023-08-24T07:00:00Z

Content type: tutorial

Language: en

Sources: [Mobile](<https://devfeed.tech/sources/mobile-dev-medium.md>)

Topics: [recording](<https://devfeed.tech/topics/recording.md>), [Android](<https://devfeed.tech/topics/android.md>), [adb](<https://devfeed.tech/topics/adb.md>), [aosp](<https://devfeed.tech/topics/aosp.md>)

Tags: [adb](<https://devfeed.tech/tags/adb.md>), [android](<https://devfeed.tech/tags/android.md>), [binary-rewriting](<https://devfeed.tech/tags/binary-rewriting.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [maestro](<https://devfeed.tech/tags/maestro.md>)

### AI overview

ADB's `screenrecord` stops after 180 seconds, which caused complaints from Maestro Cloud users. The article's excerpt compares several attempted alternatives: repeated recordings can be stitched but skip at the seams; rebuilding from AOSP requires separate dynamically linked binaries for Android versions; `scrcpy` avoids the limit but is harder to integrate; and a static binary is impractical because of AOSP's dynamic library dependencies. The chosen approach was binary rewriting: the duration limit is a hardcoded constant, and the team modified bytes in the compiled `screenrecord` binary to raise it. The excerpt says this met their requirements for longer, continuous recordings across Android versions and on emulators and physical devices, but cuts off during the explanation of how they located the bytes.

### Source excerpt

How we used binary rewriting to remove the 3-minute screen recording limitation on Maestro Cloud

## The Better WebViews Collection

DevFeed: [The Better WebViews Collection](<https://devfeed.tech/articles/the-better-webviews-collection-26011.md>)

Original publisher: [Read original article](<https://proandroiddev.com/the-better-webviews-collection-778c7bd709e6?source=rss-2ffcf6104135------2>)

Author: Stacy Devino

Published: 2023-05-09T14:04:27Z

Content type: tutorial

Language: en

Sources: [Stacy Devino](<https://devfeed.tech/sources/stories-by-stacy-devino-on-medium.md>)

Topics: [Front end](<https://devfeed.tech/topics/frontend.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Web](<https://devfeed.tech/topics/web.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [LocalStorage](<https://devfeed.tech/topics/localstorage.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [all](<https://devfeed.tech/tags/all.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-fire](<https://devfeed.tech/tags/amazon-fire.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [aosp](<https://devfeed.tech/tags/aosp.md>), [app](<https://devfeed.tech/tags/app.md>), [apps](<https://devfeed.tech/tags/apps.md>), [attention](<https://devfeed.tech/tags/attention.md>), [avoid](<https://devfeed.tech/tags/avoid.md>), [base](<https://devfeed.tech/tags/base.md>), [based](<https://devfeed.tech/tags/based.md>), [basic](<https://devfeed.tech/tags/basic.md>), [best](<https://devfeed.tech/tags/best.md>), [better](<https://devfeed.tech/tags/better.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cache](<https://devfeed.tech/tags/cache.md>), [can](<https://devfeed.tech/tags/can.md>), [collection](<https://devfeed.tech/tags/collection.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

The source recommends treating Android WebViews as a practical option while accounting for provider and device variation. It advises checking WebViewFeature support and permissions instead of relying on Android OS version, and using AndroidX WebKit compatibility APIs. For responsive layouts, it suggests TEXT_AUTOSIZING, loadWithOverviewMode, and useWideViewPort. It recommends disabling unneeded storage, JavaScript, and file access, enabling Safe Browsing where supported, and validating URLs before loadUrl; local assets can use WebViewAssetLoader. Performance guidance emphasizes optimizing web code and weighing cache modes. For testing, it describes System WebView Shell, Chrome DevTools inspection, and AndroidX tracing, with noted DevTools limitations. For web-to-app messaging it favors HTML5 MessageChannel with WebMessageCompat, subject to page-load and Android 6.0+ constraints. It also explains that WebView cookies manage sessions and may need saving and restoration to preserve login across app restarts.

### Source excerpt

The Better Android WebViews Collection WebViews are one of the most controversial subjects in the Community and unfortunately have been much maligned by developers. WebViews can be extremely useful and the best first implementation for a ton of situations from Login and Payments to User Support and Legal. Using WebViews, you can allocate your resources and attention to what your customers value most. WebView-primary apps even make up almost a third of all Apps on the Google Play Store. So, how do we make really good WebViews? Knowledge Drop 🧠💧 WebKit implementation varies ⏺ Non-Chromium-based (Non-GMS devices and some vendors) ⏺ Not all Play-Enabled devices have all features. Use isFeatureSupported and permission checks rather than @Targetan Android OS to be safe. ⏺ Customized Chromium Base (Samsung and Amazon Fire devices) There are 3 "Standard" WebViews available embedded as providers. ⏺ "Standalone" AOSP basic implementation and standard for 5.X-6.X ⏺ "Monochrome" public and AOSP-accessible unified Browser and WebView for 7.X-9.X ⏺ "Trichrome" which is a base Core Library, WebView, and Chrome browser all separated for 10.X -- Now (13.X) Use the modern WebViewCompat extensions with AndroidX Webkit / AndroidX Browser to avoid compatibility issues & version-based errors All WebView instances in your app will share the same Cache and Dom Storage, improving performance and memory usage Trust the Chromium Docs first over android.dev ⏺ WebView is now built and maintained by the Chrome team, so their documentation is going to be the most accurate and extensive WebView Settings for Success 🏆 "Make it look like Chrome" or "Why is Scaling broken?!?!?!" ReactJS, VueJS and similar front end frameworks rely on viewport and framing information in order to enable their dynamic sizing and styling features. By Default, what exists on Chrome is not what is enabled in the WebView and it requires some browser/web rendering knowledge to even figure out what is going wrong. Try these ou

## How we reduced our ANR by three times

DevFeed: [How we reduced our ANR by three times](<https://devfeed.tech/articles/how-we-reduced-our-anr-by-three-times-37402.md>)

Original publisher: [Read original article](<https://medium.com/okcredit/how-we-reduced-our-anr-by-three-times-d9ae0b41ad94?source=rss----40ea5327aac7---4>)

Author: Anjal Saneen

Published: 2022-05-24T05:19:21Z

Content type: article

Language: en

Sources: [OkCredit](<https://devfeed.tech/sources/okcredit-medium.md>)

Topics: [mobile-app-performance](<https://devfeed.tech/topics/mobile-app-performance.md>), [Android](<https://devfeed.tech/topics/android.md>), [app startup](<https://devfeed.tech/topics/app-startup.md>), [digital experience monitoring](<https://devfeed.tech/topics/digital-experience-monitoring.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [code analysis](<https://devfeed.tech/topics/code-analysis.md>), [locking](<https://devfeed.tech/topics/locking.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [anr](<https://devfeed.tech/tags/anr.md>), [background](<https://devfeed.tech/tags/background.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [google-i-o](<https://devfeed.tech/tags/google-i-o.md>), [input](<https://devfeed.tech/tags/input.md>), [mobile-app-performance](<https://devfeed.tech/tags/mobile-app-performance.md>), [okcredit](<https://devfeed.tech/tags/okcredit.md>), [performance](<https://devfeed.tech/tags/performance.md>), [production](<https://devfeed.tech/tags/production.md>), [source-code](<https://devfeed.tech/tags/source-code.md>), [stack](<https://devfeed.tech/tags/stack.md>), [startup](<https://devfeed.tech/tags/startup.md>), [what-is](<https://devfeed.tech/tags/what-is.md>)

### AI overview

The article links Android ANRs to stalled input handling, slow background startup, main-thread work, lock contention, SharedPreferences writes, and garbage-collection waits. It explains that ANRs are hard to diagnose in production: Play Console traces can be delayed, missing, or poorly grouped, while Firebase exposes exit traces only on Android 11+ and supports breadcrumbs. The authors use an ANR watchdog to capture main-thread stalls and recommend profiling cold startup, keeping heavy work off the main thread, and examining blocked-thread traces for locks. In their app, optimizing startup helped address background service and broadcast timeouts; they also moved SharedPreferences commits to a background thread and used LeakCanary to investigate memory issues. They report a 0.03% Play vitals ANR metric and continued difficulty resolving all cases. The opening separately claims a 60% ANR improvement and 70% cold-start improvement.

### Source excerpt

App not responding is one of the most frustrating experiences for users. The user is stuck with an app that is hung and must terminate it. It is ridiculously difficult to observe and fix ANR for the android app in production due to their indeterministic nature. After studying stack traces of ANR, we were able to improve ANR by 60%, as well as cold startup performance by 70%. We've also been featured on Google I/O and the Android developer's blog has covered our ANR case study. The goal of this blog post is to discuss our learnings about ANR, challenges around solving ANR, how we track ANRs, an analysis of the source code of ANR generation, and some interesting ANRs that we found and how we resolved them. What is ANR A certain period of time needs to be allowed for the Android system to process events. As soon as the processing times out, an ANR dialogue appears, allowing the user to choose to wait or terminate the application immediately. To discover ANR, Android implements a set of sophisticated mechanisms at the system level. ANR can be classified into various categories. According to the background/foreground of the App, each category has a different timeout. InputDispatching Timeout(5s): A major reason for this is that the button or input event does not respond within a specific period of time. On Android, the timeout is set at 5 seconds by default. Broadcast Timeout (10s): If the broadcast receiver fails to complete its processing within the specified time, the broadcast timeout message is reported (foreground timeout is 10 seconds, background timeout is 60 seconds). Service Timeout (20s): The service does not complete the processing within the specified timeframe (foreground timeout is 20 seconds, background timeout is 200 seconds). User experience is directly affected by ANR since it forces the user to stop using the application through an automated dialogue. However, in the background, this dialogue will not be shown to the user, instead, the app is silently

## Chasing Monet inside the Android framework

DevFeed: [Chasing Monet inside the Android framework](<https://devfeed.tech/articles/chasing-monet-inside-the-android-framework-28362.md>)

Original publisher: [Read original article](<https://siddroid.com/post/android/chasing-monet-inside-the-android-framework/>)

Author: Siddhesh Patil

Published: 2022-04-27T23:50:55Z

Content type: article

Language: en

Sources: [Sid Patil - Android Engineer and Kotlin Advocate](<https://devfeed.tech/sources/sid-patil-android-engineer-and-kotlin-advocate.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [material-you](<https://devfeed.tech/topics/material-you.md>), [Material Design](<https://devfeed.tech/topics/material-design.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [color](<https://devfeed.tech/topics/color.md>), [aosp](<https://devfeed.tech/topics/aosp.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-12](<https://devfeed.tech/tags/android-12.md>), [android-13](<https://devfeed.tech/tags/android-13.md>), [android-framework](<https://devfeed.tech/tags/android-framework.md>), [android-open-source-project](<https://devfeed.tech/tags/android-open-source-project.md>), [android-system-ui](<https://devfeed.tech/tags/android-system-ui.md>), [aosp](<https://devfeed.tech/tags/aosp.md>), [article](<https://devfeed.tech/tags/article.md>), [articles-by-sid-patil](<https://devfeed.tech/tags/articles-by-sid-patil.md>), [color](<https://devfeed.tech/tags/color.md>), [deep-dive](<https://devfeed.tech/tags/deep-dive.md>), [design](<https://devfeed.tech/tags/design.md>), [design-system](<https://devfeed.tech/tags/design-system.md>), [dynamic-colors-jetpack-compose](<https://devfeed.tech/tags/dynamic-colors-jetpack-compose.md>), [dynamic-theming](<https://devfeed.tech/tags/dynamic-theming.md>), [dynamic-theming-on-android](<https://devfeed.tech/tags/dynamic-theming-on-android.md>), [framework](<https://devfeed.tech/tags/framework.md>), [how-does-dynamic-theming-work-on-android](<https://devfeed.tech/tags/how-does-dynamic-theming-work-on-android.md>), [internals](<https://devfeed.tech/tags/internals.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [material-design](<https://devfeed.tech/tags/material-design.md>), [material-design-3](<https://devfeed.tech/tags/material-design-3.md>), [material-you](<https://devfeed.tech/tags/material-you.md>), [md3](<https://devfeed.tech/tags/md3.md>), [monet](<https://devfeed.tech/tags/monet.md>), [monet-in-aosp](<https://devfeed.tech/tags/monet-in-aosp.md>), [monet-theme-engine](<https://devfeed.tech/tags/monet-theme-engine.md>), [monet-theming](<https://devfeed.tech/tags/monet-theming.md>), [pixel](<https://devfeed.tech/tags/pixel.md>), [system-ui-apk](<https://devfeed.tech/tags/system-ui-apk.md>), [tiramisu](<https://devfeed.tech/tags/tiramisu.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

A technical deep dive into Monet, the Android framework changes behind Android 12/12L dynamic theming and Material You. It explains how System UI responds to wallpaper changes, extracts colors, generates tonal palettes, and refreshes the system context.

### Source excerpt

We deep dive into the internals of the Android framework, covering the System-UI to understand the changes introduced starting from Android 12/12L and above, code-named Monet. We will explore the new system-wide dynamic theming capabilities and take a look at how Monet fuels the Material You design.

## Gesture Navigation: Immersive Modes (IV)

DevFeed: [Gesture Navigation: Immersive Modes (IV)](<https://devfeed.tech/articles/gesture-navigation-immersive-modes-iv-24925.md>)

Original publisher: [Read original article](<https://medium.com/androiddevelopers/gesture-navigation-immersive-modes-43f2d37a925d?source=rss-9303277cb6db------2>)

Author: Chris Banes

Published: 2019-10-16T13:01:02Z

Content type: article

Language: en

Sources: [Chris Banes on Medium](<https://devfeed.tech/sources/chris-banes-on-medium.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [aosp](<https://devfeed.tech/topics/aosp.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-10](<https://devfeed.tech/tags/android-10.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [apps](<https://devfeed.tech/tags/apps.md>), [code](<https://devfeed.tech/tags/code.md>), [drawing](<https://devfeed.tech/tags/drawing.md>), [games](<https://devfeed.tech/tags/games.md>), [gesture-navigation](<https://devfeed.tech/tags/gesture-navigation.md>), [gestures](<https://devfeed.tech/tags/gestures.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [screen](<https://devfeed.tech/tags/screen.md>), [sticky](<https://devfeed.tech/tags/sticky.md>), [system](<https://devfeed.tech/tags/system.md>), [ux](<https://devfeed.tech/tags/ux.md>)

### AI overview

Android immersive mode hides system bars for fullscreen content; while hidden, Home and Back gestures are disabled until the user swipes an edge to reveal the bars. Non-sticky mode is suited to fullscreen video and photo viewers without precise edge swipes: on Android 10+, gesture exclusions remain limited to 200dp per edge whether bars are visible or hidden. Sticky mode suits drawing apps and games that need edge touch input. While its system bars are hidden, apps can exclude as much of the left and right edges as needed; when bars are visible, exclusions are ignored so users can navigate. The bottom home gesture zone remains mandatory and cannot be excluded, and may be the only way to reveal bars if both vertical edges are excluded. The excerpt says sticky mode returns to immersive mode a few seconds after the user reveals the bars.

### Source excerpt

Cover image by Virginia PoltrackGesture Navigation: immersive modes (IV) This is the fourth post in our series on Gesture Navigation. If you want to skip to another post, you can find them listed below: Gesture Navigation: Going edge-to-edge (I) Gesture Navigation: Handling visual overlaps (II) Gesture Navigation: Handling gesture conflicts (III) In this fourth post, we're going to cover what you can do if your app needs to draw across the entire screen, with the system bars hidden. Referring back to our flowchart from the previous post, we're going to cover the remaining two solutions on the right hand-side of the chart. You can find a printable PDF version of the complete flow chart here. The solutions here are to use the immersive mode which the Android platform offers apps. But what is immersive mode? What is immersive mode? Immersive mode is a way to render content fullscreen, hiding the system bars so they are not in the way. It additionally provides safety from accidental gestures/presses causing the user to leave the app, particularly useful for games. There are two types of immersive modes: Non-sticky (normal) immersive mode -- A user can exit immersive mode, by swiping in the system bars. Sticky immersive mode -- A user can temporarily exit immersive mode by swiping in the system bars. Immersive mode is automatically re-entered after a short time (few seconds). For both modes, there are two states: System bars hidden -- in this state the home and back gestures are disabled. The user must first swipe from an edge to bring in the system bars. System bars showing -- in this state the home and back gestures work as normal. Now that we've gone over the background on immersive mode, let's take a look at the two different modes in detail. Immersive mode: non-sticky As you might have seen from the flow chart, non-sticky immersive mode is ideal for UIs which need to be fullscreen, but do not require precise swiping gestures near the screen edges. Common examples includ

## Mobile Platform Convergence - Kevin Galligan

DevFeed: [Mobile Platform Convergence - Kevin Galligan](<https://devfeed.tech/articles/mobile-platform-convergence-kevin-galligan-38298.md>)

Original publisher: [Read original article](<https://touchlab.co/mobile-platform-convergence>)

Published: 2018-04-04T16:07:02Z

Content type: opinion

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Mobile](<https://devfeed.tech/topics/mobile.md>), [Android](<https://devfeed.tech/topics/android.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [aosp](<https://devfeed.tech/topics/aosp.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Java](<https://devfeed.tech/topics/java.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [aosp](<https://devfeed.tech/tags/aosp.md>), [code-sharing](<https://devfeed.tech/tags/code-sharing.md>), [featured](<https://devfeed.tech/tags/featured.md>), [ios](<https://devfeed.tech/tags/ios.md>), [java](<https://devfeed.tech/tags/java.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [platform](<https://devfeed.tech/tags/platform.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [thoughts](<https://devfeed.tech/tags/thoughts.md>)

### AI overview

The article argues that Android and iOS differ substantially in implementation but share similar architectural foundations, including Unix-like systems, files, threads, networking, and SQLite. It presents Doppl as an effort to share tested application architecture between the platforms by adapting selected AOSP code for iOS with J2objc.

### Source excerpt

Why your products feature set should be the same on Android and iOS should be obvious. However how apps are built for each are quite different.

[Next page](<https://devfeed.tech/topics/aosp.md?cursor=WyIyMDE4LTA0LTA0VDE2OjA3OjAyKzAwOjAwIiwgIjVlNjQ5OGU5LWQ4YWEtNDBkMC1iZGRiLTUwZjQ2NGNjYWE1ZCJd>)