Google Messages rolling out long-press menu redesign with precise copying
https://9to5google.com/2026/08/06/google-messages-menu-redesign/

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

Google is working on Android Quick Settings lock screen changes, requiring unlock for Wi-Fi, Bluetooth, Mobile Data, and Airplane Mode
https://www.androidauthority.com/android-quick-settings-lock-screen-change-apk-teardown-3695702/

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

Google is working on a new feature to let users customize which notification icons are shown in the status bar on Pixel phones
https://www.androidauthority.com/android-customize-notification-icons-status-bar-apk-teardown-3695810/

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

Samsung is working on a smartwatch that doesn't run Wear OS [RTOS]
https://www.sammobile.com/news/samsung-smartwatch-no-wear-os-under-development/

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

Exclusive: Official Samsung Galaxy S26 FE Images Show All Three Color Variants
https://www.androidheadlines.com/samsung-galaxy-s26-fe

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

Nothing Phone (4a) Pro Teardown
https://nothing.community/d/60225-phone-4a-pro-teardown

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

Samsung Display's new Foldable OLED combines reinforced titanium technology, a high-resolution design, and next-generation organic materials
https://global.samsungdisplay.com/31479

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

Exclusive: Motorola Edge 70 Neo, Revealing Four Colors and 200MP Camera Branding
https://www.macobserver.com/news/exclusive-motorola-edge-70-neo-leaked/

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

Google Wallet adds supervised balances for kids and teens, no bank account required
https://9to5google.com/2026/08/06/google-wallet-supervised-balances-kids-and-teens-no-bank-account-required/

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

Daily Superthread (Aug 08 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/1viu7a7
@reddit_android

Saturday APPreciation thread (Aug 08 2026) - Your weekly app recommendation/request thread!

Note 1. You can search for previous [weekly Saturday threads\](https://www.reddit.com/r/Android/search/?q=Saturday+APPreciation+thread&type=posts&sort=new)

Note 2. You can also search for previous [daily threads\](https://www.reddit.com/r/Android/search/?q=daily+superthread&include\_over\_18=on&restrict\_sr=on&t=all&sort=new).

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

This weekly Saturday thread is for:
* App promotion,
* App praise/sharing

If you are a developer, you may promote your own app ONLY under the bolded, distinguished moderator comment. Users: if you think someone is trying to bypass this rule by promoting their app in the general thread, click the report button so we can take a look!

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

Samsung Galaxy Z Flip8 Review: The Flip Rolls On - MrMobile
https://www.youtube.com/watch?v=HoVsWE1_JUk

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

The Old Guard vs. The Luxury Powerhouse: Xperia 1 VIII vs. Honor Magic 6 RSR Camera Shootout - LL Techview
https://www.youtube.com/watch?v=aw7h8SWCWdQ

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

Daily Superthread (Aug 09 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/1vjo3t6
@reddit_android

Sunday Rant/Rage (Aug 09 2026) - Your weekly complaint thread!

Note 1. You can search for previous weekly Sunday threads

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

This weekly Sunday thread is for you to let off some steam and speak out about whatever complaint you might have about:

Your device.

Your carrier.

Your device's manufacturer.

An app

Any other company



Rules

1) Please do not target any individuals or try to name/shame any individual. If you hate Google/Samsung/OnePlus etc. for one thing that is fine, but do not be rude to an individual app developer.

2) If you have a suggestion to solve another user's issue, please leave a comment but be sure it's constructive! We do not want any flame-wars.

3) Be respectful of other's opinions. Even if you feel that somebody is "wrong" you don't have to go out of your way to prove them wrong. Disagree politely, and move on.

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

Everybody's binning: MediaTek and Qualcomm both quietly cut GPU cores for cheaper flagships
https://www.notebookcheck.net/Everybody-s-binning-MediaTek-and-Qualcomm-both-quietly-cut-GPU-cores-for-cheaper-flagships.1363949.0.html

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

What if Android let you install desktop apps through the Play Store?

# What if Android let you install desktop apps through the Play Store?

Disclaimer & Sourcing: This post presents a purely hypothetical user experience concept. The visual assets, button frames, and store templates were smashed together from Play Store screenshots and public Android UI layout references found via Google Images. All template elements belong to their respective copyright owners. These graphics have been modified solely for non-commercial, illustrative purposes to map out a feature concept. I am not affiliated with Google or Android.

Every year phones get more powerful, and every year desktop modes get a little better. Yet, for some incredibly strange reason, the moment I plug my phone into a monitor, I am still mostly running mobile software stretched across a 27-inch screen. It's less “my phone became a computer” and more “my phone app has been enlarged against its will.”

Am I hating on other Android modes? Possibly. Am I an Android systems engineer? Absolutely not, but since when has that ever stopped anybody?

The fact remains that putting many mobile apps on a desktop-sized display exposes layouts and limitations that they were never designed for. And though desktop Linux applications can already be made to run on Android, the current routes often involve developer settings, terminal commands, unfamiliar package managers, or third-party environments. That is perfectly acceptable for enthusiasts who are familiar with Linux tooling and approximately nobody else.

In other words, normal people are largely limited to mobile interfaces, mobile browser behaviour, and whichever desktop-sized layouts individual developers decided they wanted to support.

So, in my extensive qualifications as Someone Who Finds This Annoying (TM), I propose Android SkyView: a consumer-facing Android feature that makes desktop Linux applications installable and manageable through the Google Play Store.

\[View Play Store Mockup\](https://i.imgur.com/pptZDGe.png/img)

Did I make that name up? Yes, but trust me, there were worse options on the table.

Mobile, as shown in the image, would install the standard Android application. Desktop would install the SkyView-compatible desktop build. Hybrid would install both and choose the appropriate experience based on the screen and input setup.

But that's the visible product. The less glamorous question is what Android would need underneath it.

# What Happens Under the Hood

Because Android already uses the Linux kernel and now includes virtualisation infrastructure through AVF, Google has much of the low-level foundation needed to build a managed desktop Linux environment. The missing piece is a consumer-facing application and distribution model.

It would use one Android-managed Linux environment built on AVF rather than packaging an entire guest operating system for every application, because good lord, storage cannot handle that. Desktop applications could then be sandboxed within that shared guest while reusing its common libraries and base system, although Google would need to define the packaging, permissions, and isolation model.

Conceptually, that would include a lightweight Linux guest managed by Android, shared GTK/Qt and system libraries, and individual Play Store apps installed as comparatively thin layers above them.

And because of compatibility issues:

SkyView would prioritise native ARM64 Linux builds, potentially distributed through a Google-defined package format or adapted from existing formats such as Flatpak.
SkyView could optionally provide x86-to-ARM binary translation for legacy applications. Because translation would add performance and power overhead, Android could limit demanding translated workloads to validated devices or recommend docked, powered operation. Native ARM64 builds would remain the goal, though. I don't think anybody wants their battery gone in an hour.

# Battery, Thermals, and Storage

Battery life is very important too, and since desktop software is

What if Android let you install desktop apps through the Play Store?

# What if Android let you install desktop apps through the Play Store?

***Disclaimer & Sourcing:*** *This post presents a purely hypothetical user experience concept. The visual assets, button frames, and store templates were smashed together from Play Store screenshots and public Android UI layout references found via Google Images. All template elements belong to their respective copyright owners. These graphics have been modified solely for non-commercial, illustrative purposes to map out a feature concept. I am not affiliated with Google or Android.*

Every year phones get more powerful, and every year desktop modes get a little better. Yet, for some incredibly strange reason, the moment I plug my phone into a monitor, I am still mostly running mobile software stretched across a 27-inch screen. It's less “my phone became a computer” and more “my phone app has been enlarged against its will.”

Am I hating on other Android modes? Possibly. Am I an Android systems engineer? Absolutely not, but since when has that ever stopped anybody?

The fact remains that putting many mobile apps on a desktop-sized display exposes layouts and limitations that they were never designed for. And though desktop Linux applications can already be made to run on Android, the current routes often involve developer settings, terminal commands, unfamiliar package managers, or third-party environments. That is perfectly acceptable for enthusiasts who are familiar with Linux tooling and approximately nobody else.

In other words, normal people are largely limited to mobile interfaces, mobile browser behaviour, and whichever desktop-sized layouts individual developers decided they wanted to support.

So, in my extensive qualifications as Someone Who Finds This Annoying (TM), I propose **Android SkyView**: a consumer-facing Android feature that makes desktop Linux applications installable and manageable through the Google Play Store.

[\[View Play Store Mockup\]](https://i.imgur.com/pptZDGe.png[/img])

Did I make that name up? Yes, but trust me, there were worse options on the table.

Mobile, as shown in the image, would install the standard Android application. Desktop would install the SkyView-compatible desktop build. Hybrid would install both and choose the appropriate experience based on the screen and input setup.

But that's the visible product. The less glamorous question is what Android would need underneath it.

# What Happens Under the Hood

Because Android already uses the Linux kernel and now includes virtualisation infrastructure through AVF, Google has much of the low-level foundation needed to build a managed desktop Linux environment. The missing piece is a consumer-facing application and distribution model.

It would use one Android-managed Linux environment built on AVF rather than packaging an entire guest operating system for every application, because good lord, storage cannot handle that. Desktop applications could then be sandboxed within that shared guest while reusing its common libraries and base system, although Google would need to define the packaging, permissions, and isolation model.

Conceptually, that would include a lightweight Linux guest managed by Android, shared GTK/Qt and system libraries, and individual Play Store apps installed as comparatively thin layers above them.

And because of compatibility issues:

* SkyView would prioritise native ARM64 Linux builds, potentially distributed through a Google-defined package format or adapted from existing formats such as Flatpak.
* SkyView could optionally provide x86-to-ARM binary translation for legacy applications. Because translation would add performance and power overhead, Android could limit demanding translated workloads to validated devices or recommend docked, powered operation. Native ARM64 builds would remain the goal, though. I don't think anybody wants their battery gone in an hour.

# Battery, Thermals, and Storage

Battery life is very important too, and since desktop software is

heavy as it is, SkyView would introduce a sort of intelligent state hibernation. When docked or connected to power, SkyView could allow supported apps greater CPU, memory, and GPU access within Android’s thermal and resource limits. When undocked, inactive Linux environments could be suspended or hibernated to reduce background usage so the battery isn't eviscerated into nothingness.

[\[View hibernation and background reduction\]](https://i.imgur.com/B1PZdFX.png[/img])

Storage permissions would also be a headache since Android loves sandboxing and Linux loves an open file system. Google would need a secure file-broker layer that exposes user-approved Android folders to SkyView applications through the Storage Access Framework or a successor API. Otherwise, users would download a PDF in the desktop browser and spend the next hour questioning where it went, much as I question life at three in the morning.

# User Experience

The biggest thing about all of this is that it would be basically seamless. Users should barely need to know that Linux is doing its own thing under the hood. That, frankly, is how it should be.

Desktop packages would still need to be published, signed, updated, and supported by their developers or trusted distributors, however. Google Play would apply compatibility checks, permission declarations, security scanning, and update management just as it does for Android apps. SkyView should not quietly scrape random Linux repositories and hope nobody uploads a virus wearing a LibreOffice moustache.

The Play Store would also recognise whether the device supports SkyView based on device eligibility and provide installation options accordingly.

[\[View SkyView inaccessible mockup\]](https://i.imgur.com/kZ7DMJ6.png[/img])

[\[View SkyView accessible mockup\]](https://i.imgur.com/VgjKc3W.png[/img])

In Hybrid mode (both APK and Linux), Android could provide shared file access, account handoff, and synchronisation APIs. Apps that support a shared profile could switch cleanly between their Android and desktop versions, while unsupported apps would retain separate settings.

**Illustrative Hardware Tiers** (Google and manufacturers would determine eligibility using performance validation):

* For devices that do not meet Google’s validated performance and virtualisation requirements, the consumer SkyView feature would remain unavailable.
* For mid-range devices, it would be a somewhat limited standard environment running basically one or at most a few desktop apps at the same time.
* For flagship/higher-end devices, SkyView would, if hardware supports it, present the full, unfettered version with the multi-window desktop and most heavy workstation apps available.

(Again, this is illustrative. Some devices have 6GB of RAM and could handle all of SkyView wonderfully, and devices like tablets shouldn't need to be docked for access to this feature. Google and manufacturers can determine what their devices support themselves.)

Additionally, Linux apps designed for touch could also run while undocked on supported devices. Lower-level experimental tooling could remain available in development builds, but unsupported consumer devices would not receive SkyView through the Play Store.

SkyView could apply Material You styling to Android-managed window chrome and offer optional GTK/Qt integration packages for applications that support them. In touchscreen mode, the system could enlarge its own title bars, taskbar controls, window handles, and launcher elements, while developers could opt into a touch-friendly desktop profile inside their applications. The platform should style what it owns and leave application interfaces alone. No app should break because Android wanted one of its buttons to be a different colour.

Desktop Linux applications commonly target Wayland or X11-based environments, while Android uses its own graphics and window-management stack. SkyView would therefore need a low-latency display, input, clipboard, audio, and window-integration layer so applications feel native rather than like a remote

desktop session running at twelve frames per second.

And that is Android SkyView! It's not supposed to be a replacement for Windows workstations or gaming PCs, but a way to make desktop apps more accessible without requiring their owners to become part-time Linux administrators. Ain't nobody got time for that.

A lot of the baseline is already there--the missing step is turning that capability into something ordinary people can use without requiring users to understand virtualisation, package managers, or terminal commands.

But would you use this? More importantly, which part would collapse first under real-world engineering constraints?

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