Android - Reddit
1.41K subscribers
17 photos
2 videos
35.1K links
Stay up-to-date with everything Android!
Content directly fetched from the subreddit just for you.

Powered by : @r_channels
Download Telegram
verification:** We have seen some bad actors begin to distribute malicious, unofficial versions of the Android OS that secretly compromise device integrity. To combat this, we are introducing Android OS verification in Android 17. Launching initially on Pixel devices, this feature helps you verify that your device is running an official, widely distributed build.
* **Enabling Certificate Transparency (CT) by default:** CT is now enabled by default for apps targeting Android 17, enhancing network security by ensuring all TLS certificates are publicly logged. 
* **Blocking cross-profile loopback traffic:** Cross-profile loopback traffic is no longer permitted by default, increasing network isolation and security between personal and enterprise work profiles.
* **Post-Quantum Cryptography (PQC):** The advent of quantum computing puts the current public-key cryptography we've relied on for decades at risk, potentially compromising everything from bank transfers to trade secrets. To prepare for the quantum computing era, we're introducing a comprehensive architectural upgrade to the Android operating system, starting in Android 17.  We’re integrating the [NIST Post-Quantum Cryptography (PQC)](https://blog.google/security/security-for-the-quantum-era-implementing-post-quantum-cryptography-in-android/) standards deep into the platform, establishing a new, quantum-resistant chain of trust that secures the platform continuously from the moment the OS powers on to when apps are executed.

# 📸 Improvements to your Android media experience

*tl;dr Android 17 levels up your multimedia experience by letting you easily record reaction videos without a green screen, decoupling your Assistant and media volumes for independent control, putting a stop to unexpected background audio, and delivering color-coded Live Updates alongside advanced Bluetooth, camera, and hearing device enhancements.*

**Screen Reactions**

In Android 17, we’re making it easier to record yourself and your screen at the same time with Screen Reactions. Available first on Pixel, this feature shows your face in a floating overlay on top of the screen. Android automatically puts the overlay at the bottom and cuts out the background so you don’t need a green screen, but you can move or resize the camera view and change the background color before or during a recording. Use this feature to make a reaction video, record a tutorial, or give feedback on a new app or document!

https://reddit.com/link/1u7l1cw/video/pdevsbhnko7h1/player

 

In addition, we’ve revamped the screen recording experience to add a floating toolbar that provides easier access to recording controls and capture settings. When you’re done recording, you can immediately view, edit, delete, or share your video.

**Dedicated Assistant volume stream**

Android 17 introduces a dedicated volume stream for Assistant apps. This change decouples Assistant audio from the standard media stream, allowing users to control both volumes independently. This enables scenarios like muting media playback while maintaining audibility for Assistant responses, and vice-versa.

**Background audio hardening**

Beginning in Android 17, apps cannot play audio, steal audio focus, or change the volume unless they are visible or have a foreground service. These restrictions on [background audio interactions](https://developer.android.com/about/versions/17/changes/bg-audio) reduce unintentional buggy experiences and ensure that these actions are started intentionally by the user.

**Enhancements to Live Update notifications**

Live updates provide a summary of important updates so users can track progress without opening the app. The system promotes Live Update notifications so they appear more prominently in the notification drawer, on the lock screen, and on the status bar. 

With Android 17, we’re introducing a metric style template designed specifically for health and fitness apps, timers, and travel apps. In addition, developers can use the new Semantic Coloring API to visually convey state changes, providing highly
glanceable, color-coded notifications.

**Other enhancements:**

* **Granular audio routing for hearing devices:** Users with hearing devices can [now independently manage](https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.it%2Fandroid-17-beta-3-a-new-multitasking-experience-redesigned-v0-6op2fpnl2grg1.png%3Fwidth%3D1080%26crop%3Dsmart%26auto%3Dwebp%26s%3D082745f23988500c117e753f50e07bd2ef8dee4d) where specific system sounds are played in Android 17. You can choose to route notifications, ringtones, and alarms to either a connected hearing aid or the device’s built-in speaker. This helps you avoid unwanted interruptions directly in your ears while maintaining a Bluetooth connection for hearing aid management apps.
* **Autonomous re-pairing for Bluetooth bond losses:** Android 17 introduces autonomous re-pairing, a system-level enhancement designed to automatically resolve Bluetooth bond loss. This occurs when two previously paired devices lose their cryptographic security keys, resulting in the devices no longer being able to securely authenticate and communicate with one another. The system now re-establishes lost bonds in the background without requiring the user to manually navigate to Settings to unpair and re-pair their peripheral.
* **Vendor-defined camera extensions:** Android 17 adds support for Vendor-defined camera extensions, allowing hardware partners to provide Android apps access to camera features like ‘Super Resolution’ or cutting-edge AI-driven enhancements.
* **Support for the RAW14 image format:** Android 17 introduces support for the RAW14 image format, the de-facto industry standard for high-end digital photography.
* **VVC support:** Android 17 adds platform support for the Versatile Video Coding (VVC) standard. This feature will be coming to devices with hardware decode support and capable drivers.

# 🤝 Making your apps and devices work better together

*tl;dr Android 17 seamlessly bridges your ecosystem by introducing the Continue On feature for effortless app handoffs between devices, unifying widget experiences to bring your favorite tools directly to Auto and Wear OS, and streamlining the pairing process for medical and fitness devices with new CompanionDeviceManager profiles.*

**Unifying the widgets experience across platforms**

Android 17 marks a shift towards a single, Compose-based development model for all widgets. By unifying the experience across mobile, cars, and Wear OS, developers can soon scale UI components across the ecosystem with a familiar workflow. The goal is to minimize the effort needed by developers to bring their widgets to more surfaces.

https://reddit.com/link/1u7l1cw/video/haep717hko7h1/player

Additionally, Android 17 introduces new platform functionality to make widgets work better on Auto. The update adds support for widgets on cars, allowing you to see the things that matter to you at a glance, even while actively navigating. For example, you can add a shortcut to your favorite contacts, a one-tap garage door opener, a weather overview and more. Widgets will be available to users of Android Auto later this year and to cars with Google built-in later on.

**Hand off your tasks with Continue On**

[Continue On](https://developer.android.com/develop/better-together/continue-on) is a new feature available in Android 17 that enables users to start an app on one device and then transition to another device in their Android ecosystem, continuing the journey they started. It’s designed to work bidirectionally, meaning that any supported Android device can both send and receive app activities, though, at launch, Continue On will first support mobile-to-tablet transitions. In the tablet taskbar, users will see a suggestion for the most recently opened app from their mobile device.

https://reddit.com/link/1u7l1cw/video/doxh917pko7h1/player

**Updates for companion device apps**

Android 17 introduces two new profiles to the CompanionDeviceManager API to simplify device distinction and permission handling. These include the medical device profile and the fitness
tracker profile. Furthermore, the system now offers a unified dialog for device association and nearby permission requests, reducing the number of dialogs you’ll see.

# ⚡ Optimizations to make your apps & device run better

With Android 17, we’ve made a number of improvements to optimize memory use, improve rendering performance, and enhance battery life. These include:

* **App memory limits:** Android 17 introduces app memory limits that are based on the device's total RAM. These limits are set conservatively to establish system baselines, targeting extreme memory leaks and other outliers before they trigger system-wide instability resulting in UI stuttering, higher battery drain, and apps being killed.
* **Lock-free MessageQueue:** Android 17 introduces a lock-free MessageQueue to reduce UI jank while massively speeding up high-contention scenarios. In our internal testing, we’ve seen 4% fewer missed frames across all apps, 7.7% fewer missed frames in System UI and Launcher interactions, and a 9.1% reduction in app startup times at the 95th percentile.
* **Generational Garbage Collector (GC):** The Android Runtime is introducing more frequent, less intensive young-generation collections in its garbage collector, improving memory management and performance. This is not just available on Android 17 but is also coming to past releases with a Google Play System Update.
* **Reduce wakelocks with listener support for allow-while-idle alarms:** Last year, we launched the [excessive wake lock metric in Android Vitals](https://android-developers.googleblog.com/2025/11/raising-bar-on-battery-performance.html), making it easier for developers to optimize their app's wake lock behavior. Excessive wake locks are a significant contributor to battery drain, so developers are encouraged to reduce them as much as possible. In Android 17, we’ve introduced a new API that helps reduce the power consumption of apps that rely on continuous wakelocks to perform periodic tasks, such as messaging apps maintaining a connection or medical devices monitoring health data.
* **Improved wireless ADB:** Android 17 introduces [ADB WiFi 2.0](https://www.youtube.com/watch?v=_CR44gRhad4), a significant overhaul of the wireless ADB stack to improve stability, reliability, and ease of use. The system now automatically monitors the network state and re-enables itself when a trusted network is detected, identifies trusted networks using a combination of SSID and BSSID, and is better tailored to monitor network changes on all platforms. We’ll have more details to share soon on the Android Studio side of things!
* **Constrained satellite networks:** Android 17 implements optimizations to enable apps to function effectively over low-bandwidth satellite networks.

# 🧒 Expanding Android Parental Controls to all devices

Launched [last year](https://blog.google/products-and-platforms/platforms/android/android-16-december/) on Pixel, Android Parental Controls make it easier for parents to manage their child’s screen time and to find balance between having fun online and offline. Now with Android 17, we’re expanding Android Parental Controls to all Android devices.

These parental controls are located directly within Android Settings and provide a single, convenient home for both built-in device controls and [Google Family Link](http://families.google/familylink/). These controls are protected by an easy-to-set PIN and allow you to:

* Set the amount of screen time your child can spend on a device each day.
* Create downtime schedules to automatically lock the device at night.
* Set app store filters for Google Play to manage the highest content rating you want your child to be able to download.
* Control app usage by limiting time spent on specific apps, or blocking apps entirely.

https://preview.redd.it/8e0tdq09ko7h1.png?width=1920&format=png&auto=webp&s=1fce1a9644465231160ad1170250e8b5f5927537

Android Parental Controls also provide a direct path to easily set up Google Family Link in the Family Link app on a parent’s phone, which offers additional features
like [School Time](https://blog.google/technology/families/family-link-updates-february-2025/), Google Play app purchase approvals, location alerts, and more.

# 🧘 Other quality-of-life improvements

And lastly, here are some smaller quality-of-life changes we’re introducing in this release:

* **Separate Wi-Fi and Mobile Data toggles:** With Android 17, we’ve split the “Internet” tile [into two separate tiles](https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.it%2Fandroid-17-beta-3-a-new-multitasking-experience-redesigned-v0-ojyys7fc2grg1.png%3Fwidth%3D1080%26crop%3Dsmart%26auto%3Dwebp%26s%3D3ff753ef1ee49de6c26dee2ebca6951946ac4754), one for controlling Wi-Fi and another for controlling Mobile Data. Consistent with the Quick Settings behavior we introduced with Material 3 Expressive, both tiles have two different touch points. Tapping the icon toggles the respective radio, while tapping the label opens the full Internet Panel. This change reduces the number of taps needed to toggle Wi-Fi and Mobile Data while still retaining access to the full Internet Panel!
* **Scheduled clock change notifications**: We’ve added a new feature in Android 17 that sends you a notification when your clock performs a scheduled change, for example when daylight saving time ends. You can [enable this feature](https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.it%2Fandroid-17-beta-3-a-new-multitasking-experience-redesigned-v0-1o08wbki2grg1.png%3Fwidth%3D1080%26crop%3Dsmart%26auto%3Dwebp%26s%3Dd6455b27d583b861de252c0e365b198505b1d109) under “Date & time” settings.
* **Restoring default keyboard visibility after rotation:** Beginning with Android 17, when the keyboard is on screen and you rotate the screen, the keyboard won’t be made visible unless the app explicitly requests it.

# 🪲 Bug fixes and security patches

Please refer to the [Android Security Bulletin](https://source.android.com/docs/security/bulletin/android-17) for details on the security vulnerabilities addressed with this platform release.

\----

There are plenty of other changes in Android 17, especially for developers! For example, Android 17 expands the capabilities of AppFunctions, introduces an EyeDropper API, makes the aspect ratio of images in the Photo Picker more customizable, and much more. To learn more about everything new for developers in this release, visit [developer.android.com](https://developer.android.com/about/versions/17/features).

Also, don’t forget that select advanced devices will be getting [Gemini Intelligence](https://www.reddit.com/r/Android/comments/1tb83gy/making_android_smarter_and_more_proactive_with/) features later this summer. In addition, we’re introducing [Android Halo](https://blog.google/products-and-platforms/platforms/android/android-halo/) in a future Android 17 release to give you at-a-glance visibility into what your agent is working on at any given time.  Lastly, be sure to check out our latest [Android Drop](https://www.reddit.com/r/Android/comments/1tuyxcv/june_android_drop_brings_new_safety_and/) to learn about what new features are coming to all Android devices, not just those running Android 17!

https://redd.it/1u7l1cw
@reddit_android
Daily Superthread (Jun 17 2026) - Your daily thread for questions, device recommendations and general discussions!

Note 1. You can search for previous daily threads.

Note 2. Join our IRC and Telegram chat-rooms! Please see our wiki for instructions.

Please post your questions here. Feel free to use this thread for general questions/discussion as well.

https://redd.it/1u8879s
@reddit_android
Paul Dunlop (Android Onboarding/Settings Product Lead) details Android Switch improvements in Android 17, including direct migration of signed-in Google accounts between iOS and Android, cross-platform app data migration APIs, seamless eSIM transfers, & more
https://www.threads.com/@pauldunlop/post/DZr4isfjanp

https://redd.it/1u8c7g4
@reddit_android
Building Computer Vision apps for Android in 2026: Has the bottleneck shifted from AI models to mobile engineering?

I've been reading case studies and following discussions around Android apps that use Computer Vision for OCR, object detection, image segmentation, quality inspection, and video analytics.

A few years ago, most conversations focused on model accuracy and training. But now it seems like the bigger challenges are:

Running models efficiently on-device with TensorFlow Lite or MediaPipe.
Balancing latency, battery usage, and model size.
Handling fragmented Android hardware and varying NPUs.
Building reliable pipelines for image/video processing in production.
Deciding when to use on-device inference vs cloud inference.

Interestingly, many successful products seem to rely as much on strong mobile engineering and UX as on the AI model itself.

I'm curious if other Android developers feel the same way.

For people who have built or worked on Computer Vision apps:

What has been the hardest problem for you?
Has model development become easier while deployment remains the real challenge?
Which frameworks or approaches have worked best in production?

Would love to hear real-world experiences and lessons learned.

https://redd.it/1u89w3l
@reddit_android
[DEV] I built an Android app that runs Whisper Base Q8 fully offline, handling long audio chunking on devices down to 2GB RAM. No data leaves your phone.

Hey everyone,

https://preview.redd.it/8614i1pfht7h1.jpg?width=1080&format=pjpg&auto=webp&s=cd314472f90beecc17b4cbe432af47ae6f4469e0

As an Android developer, I’ve always been frustrated by how speech-to-text apps rely heavily on cloud APIs, compromising privacy and requiring active internet connections. I wanted to build a solution that runs **100% locally on the device**.

However, running heavy models like OpenAI's Whisper and Silero VAD locally on budget Android hardware comes with massive memory bottlenecks and unexpected crashes.

To fix this, I built **Transcribe Offline**. Instead of defaulting to Whisper Tiny (which has terrible accuracy), I managed to optimize **Whisper Base Q8** to run smoothly even on **2GB RAM devices** using a few engineering workarounds:

* **Semantic Chunking via Silero VAD:** Instead of blindly cutting audio into fixed time slots (which cuts through words and ruins the context), the app uses local Silero VAD to detect natural human speech boundaries. I added a **negative 200ms offset** to ensure the start of sentences is never chopped off.
* **Flat Memory Footprint:** Audio chunks are processed sequentially and instantly cleared from memory, meaning the app handles a 2-hour recording with the same flat memory usage as a 2-minute clip. No Out-Of-Memory (OOM) crashes.
* **Native C++ Performance:** Core engines are compiled via Android NDK/JNI to leverage hardware acceleration and keep the main UI thread completely fluid.

The app is completely private, requires zero permissions other than reading your local files, and outputs clean text or standard `.srt` subtitles with precise timestamps.

If you are interested in the engineering details, I wrote a quick deep dive on Medium about how I overcame the memory and text-cutting limitations: 🔗[Read the Engineering Deep Dive on Medium](https://medium.com/@creazyheart92/how-i-optimized-on-device-ai-audio-transcription-for-low-end-android-devices-down-to-2gb-ram-49f1a3847337)

The app is live on the Play Store, and I would absolutely love your honest feedback, feature requests, or any questions about the on-device pipeline!

👉[**Get Transcribe Offline on Google Play**](https://play.google.com/store/apps/details?id=egyption.developer.transcribe)

https://redd.it/1u861fk
@reddit_android
I trained a neural network on my Android phone using Pydroid 3 — S-tier, 92% win rate, no servers

I wanted to see if my Android phone could train a real neural network. No cloud, no GPU, no TensorFlow — just Pydroid 3 and pure Python.

**The result:** A Q-learning neural network that reached S-tier in a fighting game and beat scientific algorithms.

**What it does:**

\- ⚔️ Fighting game: 81.2% win rate against 9 different bots (including Minimax)

\- ✊ Rock-Paper-Scissors: 92% against Exp3 and UCB1 (algorithms from research papers)

\- 🎭 Mafia (social game): 40% win rate (2x better than random)

**How it works:**

\- Pure Python lists and loops — no NumPy

\- Manual backpropagation (\~200 lines)

\- Replay Buffer (500 examples)

\- \~75 parameters, model size < 5 KB (JSON)

\- 10,000+ training battles on a phone

**Performance on Android:**

\- 500 fights: \~10 seconds

\- 5,000 RPS rounds: \~30 seconds

\- All trained locally in Pydroid 3

**Why this matters:**

You don't need a gaming PC or cloud GPU to experiment with neural networks. An Android phone is enough to train a working AI that beats algorithms from scientific papers.

Happy to answer questions about training on mobile!

GitHub in comments.

https://redd.it/1u8stc9
@reddit_android
Daily Superthread (Jun 18 2026) - Your daily thread for questions, device recommendations and general discussions!

Note 1. You can search for previous daily threads.

Note 2. Join our IRC and Telegram chat-rooms! Please see our wiki for instructions.

Please post your questions here. Feel free to use this thread for general questions/discussion as well.

https://redd.it/1u94brj
@reddit_android