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
[\[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
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
Reddit
From the Android community on Reddit: What if Android let you install desktop apps through the Play Store?
Explore this post and more from the Android community
The only eink device running Android 17?
The Musnap Neo 2 ships with Android 14 userspace, but its hardware boundary is an Android 12-era GKI 5.10.233 kernel with vendor policy level 31. It is also rootable out of the box and that made it an interesting AOSP target: instead of touching stock partitions, I keep the stock kernel/vendor stack and boot replacement generic-arm64
The hardware is a 6-inch 1448×1072 e‑ink panel. Its display path is not exposed through a generic Android display interface, so the project captures physical-display composition from SurfaceFlinger, converts it into the panel’s evidenced 16-level grayscale input domain, and submits an owned buffer through the device-specific vendor e‑ink engine.
That proprietary lower layer still handles panel conversion, waveform selection, and panel transport. It is the reason this is an integration project rather than “flash a GSI and call it done.”
Across the tested AOSP branches: Android 14, Android 15, Android 16, and Android 17 / API 37, the same presentation path has worked: SurfaceFlinger composition reaches the vendor e‑ink engine, Android UI is visible and usable on the physical panel, and repeated refreshes are accepted without recorded lower-engine rejections in the tested diagnostics.
The frontlight path is also working at a narrow, testable level: calibrated cool-only and warm-only midpoint requests, plus explicit zero/off, completed without Android-side write failure. There is persistence and sleep/wake replay now, and lift cover to wake works, but I haven't integrated it with the native brightness control yet instead I have a simple controller apk with some config settings right now.
I can’t distribute a flashable image because it needs proprietary libraries, waveform resources, and calibration data though. The AOSP-side code and build logic are publishable; the device-specific runtime pieces have to come from the owner’s own stock firmware. Not sure if there is interest in the presentation-adapter itself as these eink panels are ubiquitous across the industry.
E: https://github.com/eink-fan/eink-aosp-lab
https://preview.redd.it/7c7mh13ehdih1.jpg?width=960&format=pjpg&auto=webp&s=75ab18befd0eb43f96a7dcd0dbd6a3621cf9e413
https://redd.it/1vjtmtc
@reddit_android
The Musnap Neo 2 ships with Android 14 userspace, but its hardware boundary is an Android 12-era GKI 5.10.233 kernel with vendor policy level 31. It is also rootable out of the box and that made it an interesting AOSP target: instead of touching stock partitions, I keep the stock kernel/vendor stack and boot replacement generic-arm64
/system images as temporary DSUs.The hardware is a 6-inch 1448×1072 e‑ink panel. Its display path is not exposed through a generic Android display interface, so the project captures physical-display composition from SurfaceFlinger, converts it into the panel’s evidenced 16-level grayscale input domain, and submits an owned buffer through the device-specific vendor e‑ink engine.
That proprietary lower layer still handles panel conversion, waveform selection, and panel transport. It is the reason this is an integration project rather than “flash a GSI and call it done.”
Across the tested AOSP branches: Android 14, Android 15, Android 16, and Android 17 / API 37, the same presentation path has worked: SurfaceFlinger composition reaches the vendor e‑ink engine, Android UI is visible and usable on the physical panel, and repeated refreshes are accepted without recorded lower-engine rejections in the tested diagnostics.
The frontlight path is also working at a narrow, testable level: calibrated cool-only and warm-only midpoint requests, plus explicit zero/off, completed without Android-side write failure. There is persistence and sleep/wake replay now, and lift cover to wake works, but I haven't integrated it with the native brightness control yet instead I have a simple controller apk with some config settings right now.
I can’t distribute a flashable image because it needs proprietary libraries, waveform resources, and calibration data though. The AOSP-side code and build logic are publishable; the device-specific runtime pieces have to come from the owner’s own stock firmware. Not sure if there is interest in the presentation-adapter itself as these eink panels are ubiquitous across the industry.
E: https://github.com/eink-fan/eink-aosp-lab
https://preview.redd.it/7c7mh13ehdih1.jpg?width=960&format=pjpg&auto=webp&s=75ab18befd0eb43f96a7dcd0dbd6a3621cf9e413
https://redd.it/1vjtmtc
@reddit_android
GitHub
GitHub - eink-fan/eink-aosp-lab: A small, device-neutral reference repository for experimenting with an e-ink presentation policy…
A small, device-neutral reference repository for experimenting with an e-ink presentation policy on Android-derived systems. - eink-fan/eink-aosp-lab
Got Root on my S22 Ultra! Ported CVE-2026-43499 exploit (Android 15)
Hey everyone,
I just published a port of the CVE-2026-43499 exploit for the Samsung Galaxy S22 Ultra (codename: `b0q` / SM-S908W). The exploit successfully establishes an arbitrary read/write primitive, switches SELinux to permissive, and spawns a root helper daemon, giving you full root access.
**Status:** This vulnerability is **currently UNPATCHED** by Samsung and works on the absolute latest firmware available!
🔗 **Repo Link:** https://github.com/sarabpal-dev/IonStack-S22U
**Currently Supported Target:**
* **Device:** Samsung Galaxy S22 Ultra (SM-S908W)
* **Android:** 15 / SDK 35
* **Firmware:** `AP3A.240905.015.A2.S908WVLS8FYG7`
* **Kernel:** 5.10.226-android12-9-30958166-abS908WVLS8FYG7
* **Architecture:** aarch64
\### ⚠️ Reliability & Kernel Panic Warning
Because the exploit relies on a race condition and precise timing, it can be somewhat unreliable and may trigger a kernel panic on bad runs.
**Tips for success:** For the highest success rate, **reboot your device** before running it to ensure a clean heap state. Close all background apps, keep the screen unlocked, and do not touch the phone while the exploit is running so background tasks don't disturb the timing.
\### 🛠️ Porting to other firmwares / Generating `target.h`
The offsets in the repo are specific to the firmware version listed above. If you are on a different build, you need to generate your own `target.h` file by extracting kernel symbols and offsets from your specific kernel binary.
Here is how to do it:
1. **Extract the uncompressed kernel binary (`Image`)** from your device's `boot.img`.
2. Follow the step-by-step instructions in the `target_generator` directory to install dependencies, compile the `kallsyms` extractor, and run the generator script.
👉 **[Full step-by-step instructions for the target generator can be found here\](https://github.com/sarabpal-dev/IonStack-S22U/blob/main/target_generator/README.md)**
Once you generate your `target.h`, place it in `src/targets/<YOUR_FIRMWARE_VERSION>/target.h` and compile using `make PROJECT=<YOUR_FIRMWARE_VERSION>`.
\### 🚀 How to Deploy and Run
Once compiled, push the binaries to your device:
```bash
adb push build/S908WVLS8FYG7/bin/cve-2026-43499 /data/local/tmp/cve-2026-43499
adb push build/S908WVLS8FYG7/bin/cve-2026-43499-root /data/local/tmp/cve-2026-43499-root
adb push build/S908WVLS8FYG7/bin/cve-exp32 /data/local/tmp/cve-exp32
adb shell chmod 755 /data/local/tmp/cve-2026-43499 /data/local/tmp/cve-2026-43499-root /data/local/tmp/cve-exp32
```
Execute the exploit stage to start the root daemon (it will automatically retry up to 16 times if it fails):
```bash
adb shell "LD_PRELOAD=/data/local/tmp/cve-2026-43499 sh"
```
Once successful, pop an interactive root shell:
```bash
adb shell "/data/local/tmp/cve-2026-43499-root"
```
\### 🤝 Contributions & Pull Requests
I'd love to make this exploit more stable. If you have ideas to improve reliability, optimize the futex choreography, **Pull Requests are highly appreciated and welcome!**
Check out the repo for the full source code, build instructions, and technical details on the porting changes from the v6.6 kernel to the v5.10 kernel. Technically it should work on all firmware and all varients of s22 family need to put just target.h. Please dont ask for port to other devices its impossible without having real device on hand other devices can check Root-My-Galaxy repo
https://redd.it/1vjndfi
@reddit_android
Hey everyone,
I just published a port of the CVE-2026-43499 exploit for the Samsung Galaxy S22 Ultra (codename: `b0q` / SM-S908W). The exploit successfully establishes an arbitrary read/write primitive, switches SELinux to permissive, and spawns a root helper daemon, giving you full root access.
**Status:** This vulnerability is **currently UNPATCHED** by Samsung and works on the absolute latest firmware available!
🔗 **Repo Link:** https://github.com/sarabpal-dev/IonStack-S22U
**Currently Supported Target:**
* **Device:** Samsung Galaxy S22 Ultra (SM-S908W)
* **Android:** 15 / SDK 35
* **Firmware:** `AP3A.240905.015.A2.S908WVLS8FYG7`
* **Kernel:** 5.10.226-android12-9-30958166-abS908WVLS8FYG7
* **Architecture:** aarch64
\### ⚠️ Reliability & Kernel Panic Warning
Because the exploit relies on a race condition and precise timing, it can be somewhat unreliable and may trigger a kernel panic on bad runs.
**Tips for success:** For the highest success rate, **reboot your device** before running it to ensure a clean heap state. Close all background apps, keep the screen unlocked, and do not touch the phone while the exploit is running so background tasks don't disturb the timing.
\### 🛠️ Porting to other firmwares / Generating `target.h`
The offsets in the repo are specific to the firmware version listed above. If you are on a different build, you need to generate your own `target.h` file by extracting kernel symbols and offsets from your specific kernel binary.
Here is how to do it:
1. **Extract the uncompressed kernel binary (`Image`)** from your device's `boot.img`.
2. Follow the step-by-step instructions in the `target_generator` directory to install dependencies, compile the `kallsyms` extractor, and run the generator script.
👉 **[Full step-by-step instructions for the target generator can be found here\](https://github.com/sarabpal-dev/IonStack-S22U/blob/main/target_generator/README.md)**
Once you generate your `target.h`, place it in `src/targets/<YOUR_FIRMWARE_VERSION>/target.h` and compile using `make PROJECT=<YOUR_FIRMWARE_VERSION>`.
\### 🚀 How to Deploy and Run
Once compiled, push the binaries to your device:
```bash
adb push build/S908WVLS8FYG7/bin/cve-2026-43499 /data/local/tmp/cve-2026-43499
adb push build/S908WVLS8FYG7/bin/cve-2026-43499-root /data/local/tmp/cve-2026-43499-root
adb push build/S908WVLS8FYG7/bin/cve-exp32 /data/local/tmp/cve-exp32
adb shell chmod 755 /data/local/tmp/cve-2026-43499 /data/local/tmp/cve-2026-43499-root /data/local/tmp/cve-exp32
```
Execute the exploit stage to start the root daemon (it will automatically retry up to 16 times if it fails):
```bash
adb shell "LD_PRELOAD=/data/local/tmp/cve-2026-43499 sh"
```
Once successful, pop an interactive root shell:
```bash
adb shell "/data/local/tmp/cve-2026-43499-root"
```
\### 🤝 Contributions & Pull Requests
I'd love to make this exploit more stable. If you have ideas to improve reliability, optimize the futex choreography, **Pull Requests are highly appreciated and welcome!**
Check out the repo for the full source code, build instructions, and technical details on the porting changes from the v6.6 kernel to the v5.10 kernel. Technically it should work on all firmware and all varients of s22 family need to put just target.h. Please dont ask for port to other devices its impossible without having real device on hand other devices can check Root-My-Galaxy repo
https://redd.it/1vjndfi
@reddit_android
GitHub
GitHub - sarabpal-dev/IonStack-S22U: CVE-2026-43499 full exploit chain for Samsung Galaxy S22 Ultra (Android 5.10 kernel)
CVE-2026-43499 full exploit chain for Samsung Galaxy S22 Ultra (Android 5.10 kernel) - sarabpal-dev/IonStack-S22U
NL Tech - Don't make this $2,100 mistake! Galaxy Z Fold8 Ultra review!
https://www.youtube.com/watch?v=r97jqMkPG6s
https://redd.it/1vkau9z
@reddit_android
https://www.youtube.com/watch?v=r97jqMkPG6s
https://redd.it/1vkau9z
@reddit_android
YouTube
Don't make this $2,100 mistake! Galaxy Z Fold8 Ultra review!
Written version here!
https://nasilemaktech.com/samsung-galaxy-z-fold8-ultra-review
Where to buy Galaxy Z Fold8 (wide boi)? (Affiliate links)
Amazon: https://amzn.to/44MACEO
Lazada: https://invl.me/clnnzl8
Shopee: https://invl.me/clnnzl1
Where to buy Galaxy…
https://nasilemaktech.com/samsung-galaxy-z-fold8-ultra-review
Where to buy Galaxy Z Fold8 (wide boi)? (Affiliate links)
Amazon: https://amzn.to/44MACEO
Lazada: https://invl.me/clnnzl8
Shopee: https://invl.me/clnnzl1
Where to buy Galaxy…
Daily Superthread (Aug 10 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/1vkivsk
@reddit_android
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/1vkivsk
@reddit_android
Reddit
r/Android
Android news, reviews, tips, and discussions about rooting, tutorials, and apps. General discussion about devices is welcome. Please direct technical support, upgrade questions, buy/sell, app recommendations, and carrier-related issues to other subreddits.
Google Pixel 11 Pro XL Geekbench 7 result offers early look at Tensor G6 performance - Notebookcheck News
https://www.notebookcheck.net/Google-Pixel-11-Pro-XL-Geekbench-7-result-offers-early-look-at-Tensor-G6-performance.1364515.0.html
https://redd.it/1vkmz4e
@reddit_android
https://www.notebookcheck.net/Google-Pixel-11-Pro-XL-Geekbench-7-result-offers-early-look-at-Tensor-G6-performance.1364515.0.html
https://redd.it/1vkmz4e
@reddit_android
Notebookcheck
Google Pixel 11 Pro XL Geekbench 7 result offers early look at Tensor G6 performance
A fresh Pixel 11 Pro XL Geekbench 7 listing offers an early look at Tensor G6 CPU performance. The new Google SoC comes with an unusual seven-core configuration, which, in turn, affects multi-core performance.
Google Play Store starts distributing third-party Android app stores – here’s how it works [Gallery]
https://9to5google.com/2026/08/10/google-play-store-third-party-android-app-stores-launch/
https://redd.it/1vksty7
@reddit_android
https://9to5google.com/2026/08/10/google-play-store-third-party-android-app-stores-launch/
https://redd.it/1vksty7
@reddit_android
9to5Google
Google Play Store starts distributing third-party Android app stores – here's how it works [Gallery]
Google has opened the floodgates, with third-party app stores on Android now showing up in the Play Store in the US.
Samsung Galaxy Z Fold 8 Ultra Review: What Happens When Samsung Stops Playing It Safe
https://www.androidheadlines.com/samsung-galaxy-z-fold-8-ultra-review
https://redd.it/1vkyijv
@reddit_android
https://www.androidheadlines.com/samsung-galaxy-z-fold-8-ultra-review
https://redd.it/1vkyijv
@reddit_android
Android Headlines
I Spent A Week With The Galaxy Z Fold 8 Ultra, Here's What Samsung Got Right (And Wrong)
It took Samsung seven generations to finally launch an 'Ultra' foldable. But is the Galaxy Z Fold 8 Ultra actually 'Ultra'? By Samsung's definition, it
Exclusive: First images show Fairphone 6+ in Cobalt Blue
https://www.newmobile.com/Fairphone-Gen-6-Plus
https://redd.it/1vl0iob
@reddit_android
https://www.newmobile.com/Fairphone-Gen-6-Plus
https://redd.it/1vl0iob
@reddit_android
NewMobile
Exclusive: First images show Fairphone 6+ in Cobalt Blue
Exclusive: First images of Fairphone Gen. 6+ in Cobalt Blue. Design remains same, RAM grows to 12GB. View photos here.
Another YouTube auto-play bug/feature (not sure which)
https://www.androidauthority.com/youtube-autoplay-bug-or-feature-3696192/
https://redd.it/1vl4lcp
@reddit_android
https://www.androidauthority.com/youtube-autoplay-bug-or-feature-3696192/
https://redd.it/1vl4lcp
@reddit_android
Android Authority
YouTube's new autoplay behavior is already triggering thousands of users
YouTube is testing users' patience again with videos that autoplay the instant the app opens in a change no one asked for.
ANROID BEAM RETURNS!
Hey everyone,
I missed Android Beam after Google removed it, so I built a simple app that brings the same idea back.
ANRO-BEAM lets you send files between two Android phones just by holding them back to back / tapping them together.
No internet, no cloud, no account needed.
You can download it here:
https://s9723651-debug.github.io/anrobeam/
It’s still early, so I’d really appreciate any feedback or bug reports.
Thanks!
https://redd.it/1vl19ef
@reddit_android
Hey everyone,
I missed Android Beam after Google removed it, so I built a simple app that brings the same idea back.
ANRO-BEAM lets you send files between two Android phones just by holding them back to back / tapping them together.
No internet, no cloud, no account needed.
You can download it here:
https://s9723651-debug.github.io/anrobeam/
It’s still early, so I’d really appreciate any feedback or bug reports.
Thanks!
https://redd.it/1vl19ef
@reddit_android
USBIPBeta: Free, Open-Source USB/IP Server for Android (VirtualHere Alternative)
Hey everyone! 👋
If you've ever wanted to connect and share USB peripherals (like gaming steering wheels, pedals, and controllers) from an Android device to a Windows client over your local network, I built something that might help.
Introducing **USBIPBeta**—a lightweight client application and custom kernel driver suite designed to bridge Android hosts and Windows PCs using the USB/IP protocol.
# 🚀 What It Does
* **Peripheral Redirection:** Share physical USB devices attached to an Android device over your local network.
* **Sim Racing & Gaming Focus:** Great for plugging hardware like a Logitech G29 directly into an Android setup and routing it smoothly to a client machine.
* **Cross-Platform Bridge:** Consists of an Android APK host component and a Windows client executable/driver suite.
# 💻 Open Source & 100% Free
This project is completely free and open-source, and it always will be! If you want to check out the code, inspect the setup, or download the beta release, you can find everything here:
🔗 **GitHub Repository:**[https://github.com/hellfurian1228/USBIPBeta](https://github.com/hellfurian1228/USBIPBeta)
*Note: While the app is and will always remain 100% free to use, if you find it helpful and want to buy me a coffee, you can find an optional donation link over on the GitHub repo!*
https://redd.it/1vl0u2o
@reddit_android
Hey everyone! 👋
If you've ever wanted to connect and share USB peripherals (like gaming steering wheels, pedals, and controllers) from an Android device to a Windows client over your local network, I built something that might help.
Introducing **USBIPBeta**—a lightweight client application and custom kernel driver suite designed to bridge Android hosts and Windows PCs using the USB/IP protocol.
# 🚀 What It Does
* **Peripheral Redirection:** Share physical USB devices attached to an Android device over your local network.
* **Sim Racing & Gaming Focus:** Great for plugging hardware like a Logitech G29 directly into an Android setup and routing it smoothly to a client machine.
* **Cross-Platform Bridge:** Consists of an Android APK host component and a Windows client executable/driver suite.
# 💻 Open Source & 100% Free
This project is completely free and open-source, and it always will be! If you want to check out the code, inspect the setup, or download the beta release, you can find everything here:
🔗 **GitHub Repository:**[https://github.com/hellfurian1228/USBIPBeta](https://github.com/hellfurian1228/USBIPBeta)
*Note: While the app is and will always remain 100% free to use, if you find it helpful and want to buy me a coffee, you can find an optional donation link over on the GitHub repo!*
https://redd.it/1vl0u2o
@reddit_android
GitHub
GitHub - hellfurian1228/USBIPBeta
Contribute to hellfurian1228/USBIPBeta development by creating an account on GitHub.
Google Play Now Takes Venmo Payments | You can use Venmo to pay for Android app purchases and subscriptions.
https://www.engadget.com/2232988/google-play-venmo/#Echobox=1786363509
https://redd.it/1vlaucy
@reddit_android
https://www.engadget.com/2232988/google-play-venmo/#Echobox=1786363509
https://redd.it/1vlaucy
@reddit_android
Engadget
Google Play now takes Venmo payments - Engadget
You can now use your Venmo balance or linked accounts for Google Play purchases.
Feedback Looking for feedback on my app – send WhatsApp messages without saving contacts
Hey everyone!
I launched a small Android app a few months ago and recently started working on it again. Before adding new features, I'd like to get some feedback from other Android users and see if there are things I should improve, change, or fix.
# What does the app do?
The app makes it easier to start a WhatsApp conversation with a phone number without having to save the number as a contact first.
For example, if you need to send a WhatsApp message to a delivery driver, a customer, a seller, or someone you probably won't contact again, you can simply enter their phone number and open the conversation directly in WhatsApp.
The idea is to make this process a little faster and avoid filling your contact list with temporary numbers.
# Why did I make it?
I found myself frequently needing to send WhatsApp messages to numbers that I didn't want to save as contacts. I wanted something simple that would make this process more convenient.
But more importantly, I've noticed that many people who aren't very familiar with smartphones struggle with this process. They often have trouble entering the country code, area code, and phone number correctly before they can start a conversation on WhatsApp.
I wanted to make this process simpler and more accessible, especially for people who aren't very comfortable with smartphones.
# I'd love your feedback
I'm particularly interested in hearing about:
Is the app useful to you?
Is the process intuitive?
Is there anything confusing or annoying about the UI?
Are there features you think would make it more useful?
Did you encounter any bugs or unexpected behavior?
Is there anything you'd change about the app?
I'm still working on it, so I'll be following the comments and answering questions here. Any honest feedback — positive or negative — is welcome.
If you'd like to try it, it's available on Google Play:
https://play.google.com/store/apps/details?id=com.chamarnozap.app
Thanks for taking the time to check it out! ⚙️
https://redd.it/1vkyqzd
@reddit_android
Hey everyone!
I launched a small Android app a few months ago and recently started working on it again. Before adding new features, I'd like to get some feedback from other Android users and see if there are things I should improve, change, or fix.
# What does the app do?
The app makes it easier to start a WhatsApp conversation with a phone number without having to save the number as a contact first.
For example, if you need to send a WhatsApp message to a delivery driver, a customer, a seller, or someone you probably won't contact again, you can simply enter their phone number and open the conversation directly in WhatsApp.
The idea is to make this process a little faster and avoid filling your contact list with temporary numbers.
# Why did I make it?
I found myself frequently needing to send WhatsApp messages to numbers that I didn't want to save as contacts. I wanted something simple that would make this process more convenient.
But more importantly, I've noticed that many people who aren't very familiar with smartphones struggle with this process. They often have trouble entering the country code, area code, and phone number correctly before they can start a conversation on WhatsApp.
I wanted to make this process simpler and more accessible, especially for people who aren't very comfortable with smartphones.
# I'd love your feedback
I'm particularly interested in hearing about:
Is the app useful to you?
Is the process intuitive?
Is there anything confusing or annoying about the UI?
Are there features you think would make it more useful?
Did you encounter any bugs or unexpected behavior?
Is there anything you'd change about the app?
I'm still working on it, so I'll be following the comments and answering questions here. Any honest feedback — positive or negative — is welcome.
If you'd like to try it, it's available on Google Play:
https://play.google.com/store/apps/details?id=com.chamarnozap.app
Thanks for taking the time to check it out! ⚙️
https://redd.it/1vkyqzd
@reddit_android
Google Play
WhatsCall without contact - Apps on Google Play
Send messages without saving the contact. Fast, simple, private.
Daily Superthread (Aug 11 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/1vlfh3a
@reddit_android
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/1vlfh3a
@reddit_android
Reddit
r/Android
Android news, reviews, tips, and discussions about rooting, tutorials, and apps. General discussion about devices is welcome. Please direct technical support, upgrade questions, buy/sell, app recommendations, and carrier-related issues to other subreddits.
Samsung’s Hearing Aid Feature on Galaxy Buds Cleared by FDA
https://news.samsung.com/global/samsungs-hearing-aid-feature-on-galaxy-buds-cleared-by-fda
https://redd.it/1vlhnuk
@reddit_android
https://news.samsung.com/global/samsungs-hearing-aid-feature-on-galaxy-buds-cleared-by-fda
https://redd.it/1vlhnuk
@reddit_android
Samsung Global Newsroom
Samsung’s Hearing Aid Feature on Galaxy Buds Cleared by FDA - Samsung Global Newsroom
Company brings accessible, over-the-counter hearing aid directly to Galaxy Buds
Xperia 1 sales are "growing significantly" in Europe
https://www.itmedia.co.jp/mobile/articles/2608/10/news015.html](https://www.itmedia.co.jp/mobile/articles/2608/10/news015.html
https://redd.it/1vljy73
@reddit_android
https://www.itmedia.co.jp/mobile/articles/2608/10/news015.html](https://www.itmedia.co.jp/mobile/articles/2608/10/news015.html
https://redd.it/1vljy73
@reddit_android
ITmedia Mobile
ソニーに聞く「Xperia 1 VIII」の裏側 デザイン刷新や20万円超えの理由、物議を醸したAIカメラ新機能の真相（1/2 ページ）
ソニーはフラグシップスマートフォン「Xperia 1 VIII」の開発背景や特徴について説明した。デザイン刷新や望遠カメラの進化に加えミリ波対応や新機能の意図を明かした。高価格化にもかかわらずファンに支持される独自の価値提案を強調した。
Inside Swiff: An Interview with NaviVani on Bringing Flash Games Back to Android
https://gardinerbryant.com/inside-swiff-an-interview-with-navivani/
https://redd.it/1vlf0y0
@reddit_android
https://gardinerbryant.com/inside-swiff-an-interview-with-navivani/
https://redd.it/1vlf0y0
@reddit_android
The Bryant Review
Inside Swiff: An Interview with NaviVani on Bringing Flash Games Back to Android
From childhood memories to the RG Rotate, the developer behind Swiff explains why the lost games of the early web still matter.
DeX Inner Tester allows your Galaxy foldable to run Samsung DeX locally without a monitor
https://www.androidauthority.com/samsung-dex-local-android-app-3697211/
https://redd.it/1vlsafi
@reddit_android
https://www.androidauthority.com/samsung-dex-local-android-app-3697211/
https://redd.it/1vlsafi
@reddit_android
Android Authority
This clever app lets you use Samsung DeX locally on your Galaxy Z Fold
A developer has built an app that lets users access Samsung DeX’s functionality directly on their phone without needing a monitor.
Review revelation: Xiaomi is also cutting costs on a specific smartphone component
https://www.notebookcheck.net/Review-revelation-Xiaomi-is-also-cutting-costs-on-a-specific-smartphone-component.1363567.0.html
https://redd.it/1vls8mk
@reddit_android
https://www.notebookcheck.net/Review-revelation-Xiaomi-is-also-cutting-costs-on-a-specific-smartphone-component.1363567.0.html
https://redd.it/1vls8mk
@reddit_android
Notebookcheck
Review revelation: Xiaomi is also cutting costs on a specific smartphone component
Our Xiaomi 17T review evaluates the smartphone based on hard facts: chip performance, camera quality, battery life, and build quality. We’ll show whether the device can compete with true flagship models despite its price—including all its strengths and weaknesses.