Mishaal Rahman's banner
Mishaal Rahman's profile picture

Mishaal Rahman

@MishaalRahman72,822 subscribers

Community engagement for Android @ Google

Shorts

This app uses AirDrop to send files from your Android phone to your Macbook! Yes, it actually uses AirDrop. That means you don't have to install ANYTHING on your Mac to send files from your Android phone! Here's a video of a Galaxy Z Flip 5 AirDropping a file to a Macbook running macOS Ventura 13.5.1. (Thanks to u/FragmentedChicken for testing this app for me and sharing the video!) A few months ago, Twitter user @Linus13499209 brought an app called WarpShare to my attention. WarpShare is an app made by the developers of MoKee, an AOSP-based custom ROM that was popular in China. Since MoKee wasn't as popular outside of China, it seems the existence of their WarpShare app slipped under the radar. I was skeptical about whether it would work at all. Grishka, the developer of NearDrop, an open source port of Google's Nearby Share to macOS, told me that they were under the assumption that AirDrop requires the use of AWDL (Apple Wireless Direct Link, Apple's proprietary WiFi-based protocol) to communicate both ways. However, it seems that AWDL is only required for your Android phone to be discoverable by your Mac (ie. to send files from your Mac to your Android phone) but not the other way around. Because of this, though, WarpShare only supports sending files from Android to Mac but not vice versa. Your Mac also needs to have AirDrop discoverability set to "everyone" for this to work, as "contacts-only" requires Apple-signed certificates. Plus, it also doesn't support sending files from Android to iPhones or iPads, even when "everyone" mode is enabled. Still, if you find other Android --> Mac file sharing options to be lackluster, give WarpShare a try! The fact that it works at all is incredible, which is why I'm sharing this news here. If you want to download WarpShare on your Android device, you'll need to compile the app from its source code. If you're a Patron/X subscriber, however, I will share my compiled APK with you. WarpShare source code:

This app uses AirDrop to send files from your Android phone to your Macbook! Yes, it actually uses AirDrop. That means you don't have to install ANYTHING on your Mac to send files from your Android phone! Here's a video of a Galaxy Z Flip 5 AirDropping a file to a Macbook running macOS Ventura 13.5.1. (Thanks to u/FragmentedChicken for testing this app for me and sharing the video!) A few months ago, Twitter user @Linus13499209 brought an app called WarpShare to my attention. WarpShare is an app made by the developers of MoKee, an AOSP-based custom ROM that was popular in China. Since MoKee wasn't as popular outside of China, it seems the existence of their WarpShare app slipped under the radar. I was skeptical about whether it would work at all. Grishka, the developer of NearDrop, an open source port of Google's Nearby Share to macOS, told me that they were under the assumption that AirDrop requires the use of AWDL (Apple Wireless Direct Link, Apple's proprietary WiFi-based protocol) to communicate both ways. However, it seems that AWDL is only required for your Android phone to be discoverable by your Mac (ie. to send files from your Mac to your Android phone) but not the other way around. Because of this, though, WarpShare only supports sending files from Android to Mac but not vice versa. Your Mac also needs to have AirDrop discoverability set to "everyone" for this to work, as "contacts-only" requires Apple-signed certificates. Plus, it also doesn't support sending files from Android to iPhones or iPads, even when "everyone" mode is enabled. Still, if you find other Android --> Mac file sharing options to be lackluster, give WarpShare a try! The fact that it works at all is incredible, which is why I'm sharing this news here. If you want to download WarpShare on your Android device, you'll need to compile the app from its source code. If you're a Patron/X subscriber, however, I will share my compiled APK with you. WarpShare source code:

1,290,540 просмотров

🐤 Android Canary 2608 is now available with an exciting new customization feature to test: a Quick Settings layout editor! Here's a quick look at what it can do 🧵 (As usual, Canary is highly experimental and not recommended for daily use!)

🐤 Android Canary 2608 is now available with an exciting new customization feature to test: a Quick Settings layout editor! Here's a quick look at what it can do 🧵 (As usual, Canary is highly experimental and not recommended for daily use!)

51,644 просмотров

📲 In the Android 17 QPR1 Beta, the taskbar now shows your most recently opened apps at the end (up to 2 on foldables) instead of "predicted" apps. This should make multitasking faster and more consistent, in my opinion. But what do y'all think of this change? 🤔

📲 In the Android 17 QPR1 Beta, the taskbar now shows your most recently opened apps at the end (up to 2 on foldables) instead of "predicted" apps. This should make multitasking faster and more consistent, in my opinion. But what do y'all think of this change? 🤔

26,263 просмотров

Google just shared its first official look at the Pixel 10!

Google just shared its first official look at the Pixel 10!

50,885 просмотров

The latest loophole that third-party file manager apps were using to get access to files and folders under /Android/data and /Android/obb has been patched. As part of Android 11's Scoped Storage restrictions, apps that use the Storage Access Framework (SAF) to launch the documents picker are not supposed to be able to get access to files and folders under the /Android/data or /Android/obb directories. However, third-party file managers figured out that if they set the initial directory when launching the documents picker to either /Android/data or /Android/obb, the documents picker lets the user grant the app full access to directories. This loophole was patched in Android 13, but then another loophole was discovered that got around this. Since Android 13 only blocked apps from setting /Android/data or /Android/obb as the initial directory when launching the documents picker, it was quickly discovered that you could set the initial directory to one of the subdirectories under /Android/data or /Android/obb, thus the user could grant access to individual subdirectories one-by-one. However, this latest loophole was patched with a recent Google Play System Update. The latest version of the DocumentsUI app, the Project Mainline module that comprises the documents picker, now restricts the initial location for the ACTION_OPEN_DOCUMENT/_TREE intent so that apps cannot request the initial location to be one of /Android/data, /Android/sandbox, /Android/obb, or one of their subdirectories. If the DocumentsUI app (AKA 'Files' app) on your device is on version 14-10492947 (version code 340916000), then this loophole is patched.

The latest loophole that third-party file manager apps were using to get access to files and folders under /Android/data and /Android/obb has been patched. As part of Android 11's Scoped Storage restrictions, apps that use the Storage Access Framework (SAF) to launch the documents picker are not supposed to be able to get access to files and folders under the /Android/data or /Android/obb directories. However, third-party file managers figured out that if they set the initial directory when launching the documents picker to either /Android/data or /Android/obb, the documents picker lets the user grant the app full access to directories. This loophole was patched in Android 13, but then another loophole was discovered that got around this. Since Android 13 only blocked apps from setting /Android/data or /Android/obb as the initial directory when launching the documents picker, it was quickly discovered that you could set the initial directory to one of the subdirectories under /Android/data or /Android/obb, thus the user could grant access to individual subdirectories one-by-one. However, this latest loophole was patched with a recent Google Play System Update. The latest version of the DocumentsUI app, the Project Mainline module that comprises the documents picker, now restricts the initial location for the ACTION_OPEN_DOCUMENT/_TREE intent so that apps cannot request the initial location to be one of /Android/data, /Android/sandbox, /Android/obb, or one of their subdirectories. If the DocumentsUI app (AKA 'Files' app) on your device is on version 14-10492947 (version code 340916000), then this loophole is patched.

17,040 просмотров

Videos

Больше нет контента для загрузки