-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quick Share support? #140
Comments
From my testing, Nearby Share devices only appear in Samsung Quick Share only after Nearby Share is removed (after a GMS update or a remote config flag?). Tested on S21+/S23 with both NearDrop on Mac and the official app on Windows: they were only showing up in Nearby Share yesterday. Got the update that removed Nearby Share today, now they're showing up in the Samsung app. Also, this update breaks receiving files from NearDrop on Samsung devices since the Receive files screen is gone (not sure about non-Samsung devices). |
That's a thing now?! |
On Samsung devices, Edit: It doesn't completely remove Nearby Share, it merges Nearby Share with Samsung's own file sharing tool. |
+1 After updating Nearby Share to Quick Share on my Pixel 8 Pro, my Macbook Pro with Neardrop doesn't show up in the phone's share menu. |
IT WORKS |
It doesn't work with samsung galaxy s23 since the merge, I did not have access to google's nearby share any more only Quick Share |
Same here thing here on a Galaxy S23. |
Im on s21 Ultra and it works for me, are you guys on newest quickshare version? |
Yeah, it says I'm on the latest versions: Quick share: 13.6.11.7 |
The only thing that matters in relation to NearDrop is whether the network protocol is different. Or, at least backwards compatible enough (those version numbers in all packets are there for a reason, after all). And no, I'm not renaming it to QuickDrop :P |
hi @grishka, So using the QuickShare option to no avail, even with other device (non samsung) using google nearby share. When using another android phone and enabling nearby share discovery, it triggers the google's services pop-up to open the old nearby share. Using the old nearby share on the samsung s23 (without using the direct share button that has disappeared) allow you to see your mac, but it fails to show a pop-up on the macos side. Moreover, it ended up with multiple time showing duplicated computer (for a same and single mac, with the same and single near drop launched). Both Xiaomi android 12 and Samsung S23 android 14 now fail to connect to neardrop app, they have changed something on both side, and google nearby share is not actually compatible with Samsung quickshare (even if in the settings of the latter, there is written your samsung account for samsung, your google account for google sharing) as it is not showing android devices on the quickshare menu, and other device sharing with a quickshare enabled device default to google's services. What a mess they have done, it basically means everyone keeps its own tech, but under a single name and a single logo. |
NearDrop doesn't implement the "device nearby is sharing" popup. Although I suppose I could add it? I reverse engineered that part. It relies on BLE. I can't send the required broadcasts from macOS because of its limited APIs, but there's nothing to prevent me from receiving them.
You had one fucking job, Google... |
I mean, when I choose a file to share with my computer, the pop-up to accept the transfer is not showing any more on macOS, nor the device actually findable from QuickShare. Actually the device is findable from the old Nearby Share Menu on Samsung, And Nearby Share menu on the Xiaomi, but the pop-up to accept the transfer is not showing any more on macOS. |
Does it just show up as loading and then fails with a timeout? |
On macOS side, nothing, and on android side timeout Enregistrement.de.l.ecran.2024-02-04.a.23.41.06.mp4Screen_Recording_20240204_234306_Google.Play.services.mp4 |
Works perfectly for me, using Samsung S24 Ultra with: |
On the Galaxy Z Flip3 I'm using, it doesn't work with 'Quick Share', but it does work with 'Nearby Share'. As you can see in the video below, if I try it on 'Quick Share' it says 'Fail' and I don't even get any notification on my MacBook Pro (Sonoma 14.3), whereas on 'Nearby Share' it works very well. I also moved all the videos below via 'NearDrop' and 'Nearby Share'. ** Note ** If you're not sure if 'Quick Share' and 'Nearby Share' are integrated on your Samsung Galaxy device, check to see if the icons are the same as mine, or long press on 'Quick Share' in the quick panel and a modal will come up telling you they are integrated. Quick Share Verison: 13.6.11.7 Screen_Recording_20240205_224035_Google.Play.services.mp4Screen_Recording_20240205_223540_Quick.Share.mp4 |
But you can see your mac on the device list if QuicShare ? Because mine is not to be found. As of today @grishka something happened, nearby share seams to work back again with S23, there is something strange going server side I think. |
Yes, I can see my MacBook even if I use Quick Share. I want to see what happens using XCode, but it's a bit difficult because I don't know how to develop macOS and iOS. |
@grishka 'Nearby Share is not available on this device.' |
Unfortunately Google has also removed the "Receive" page from the Files app, so you can't use it to make your phone visible for receiving from NearDrop |
Google dropped the Receive thing from the Files app. What do we do now? :/ |
Oops. Make an intent shortcut like it says in readme then. Unless they removed that activity as well. |
They started to remove that activity in gms |
That's extremely unfortunate. But then maybe they added some new way to enable the MDNS service that doesn't involve sending impossible BLE advertisements. This needs further research. |
I am unable to send files via 'NearDrop' anymore because 'Nearby Share' has been completely removed and merged into 'Quick Share' with using google Files app, I am using google Pixel 8 pro now not working at all we don't have any Receive Button so how we fixed? |
@grishka I think at the moment the best solution is to keep the old Google Files app apk, installation takes a few seconds and then open and use It. another solution is we can just clean the storage and cache whenever mac to sends Android file share. screen-20240209-163954.1.1.mp4Screen.Recording.2024-02-09.at.4.39.03.PM.movit is not appropriate for the long term but is Ok for now. |
@mitesh77 Which version should we install to get the receive tab back? |
This doesn't work, unfortunately (I have a Galaxy S23 Ultra). I downgraded to the January 22, 2024 version of Google Files, which still has the Nearby Share tab…but when I click "Receive," it says "Nearby sharing isn't available on this device." I can use Quick Share on the Samsung phone to send files to the Mac, but when I select a file > Share > NearDrop > NearDrop's share screen opens, it never detects my Samsung phone. |
Maybe the following works for some of you as well (as a workaround): In the Google Play Store, navigate to Google Files and then select "Uninstall". This will not remove Google Files but it will uninstall all updates to it. Afterwards, I got the Nearby receive tab again. Furthermore, you can disable automatic updates for that package, until hopefully a new solution is found. |
@stanleylhs |
This won't work for any Samsung users, who don't have Google Files installed by default. I uninstalled from the Play Store and it removed it completely. As noted in my prior comment, even installing an older version with Nearby Share doesn't work because the framework on Samsung phones has been removed. |
I can confirm that on my S23+ after February update and Nearby Share removal - Quick Share can send files to NearDrop. So probably Quick Share use same protocol for non Samsung devices under the hood as Nearby Share. |
After the update on my s22 Nearby Share also disappeared and when I'm trying to share something with Quick Share the app doesn't see my Mac despite turning on Bluetooth and connection to the same wifi network. Same situation, but it works with Flip 3 but it is searching for the device for a really long time |
Got a temporary workaround which involves uninstalling the updates for Google Play Services and Quick Share from phone's settings. This works for me atleast for now. |
I change my phone Galaxy Z Filp3 to Pixel 6 Pro. Everything is work. My Pixel 6 Pro still alive |
It's working again after yesterday's update of apps in GP
|
It seems like they brought back nearby share in the latest files update. |
This also works for me on my S21 Ultra |
Sending (to macOS) works for most of us. It's receiving (from macOS to Android) that is seemingly broken. |
As I already said before, the problem with macOS -> Android is that to become discoverable, Android expects BLE advertisements that are impossible to send using any macOS APIs I tried, both public and private. The "service data" field in particular can't be specified, but Android requires it to be present and its value to match a hardcoded prefix. If someone smarter than me would find a way to do it, I'll be more than happy to add it to the app. Or, if someone finds an alternative I may have overlooked while looking through a decompiled Google Services apk. That "open Google Files" thing is just a gross workaround for being unable to send that BLE advertisement. |
Samsung s23 Ultra. Nearby Share is removed for now and Quick share doesn't see Macbook. |
I have a Samsung Note 10+, and my 2020 M1 Macbook Air doesn't show up under Quick Share's "Share to devices nearby" section. Nearby Share + NearDrop was working flawlessly up until yesterday. How would I go about uninstalling Quick Share from the updates as a temporary workaround? |
@makerjeff check it once |
Updated to QuickShare on Pixel 8 today. Neardrop seems to work fine from Android -> macOS as usual. I didn't know the reverse was possible before, so never tried it. Wonder if any thoughts about renaming NearDrop to QuickDrop to match the brand change. |
No, I'm not Google. I don't change my mind on things 5 times a year for no good reason. |
lol fair |
Doesn't work anymore for me: Mac is found but transfer fails. |
Most problems seem to be with Samsung devices but I don't have a Samsung device that still receives updates to test this ¯\_(ツ)_/¯ Still works with my Pixel 4a. |
If it doesn't work on Samsung devices, check the (If Your One UI version is 6.1 or Your Phone is Galaxy S24 Ultra, this probably won't work at all, so if you can't find |
There's no Nearby Share, it was completely removed in the latest update, no
way to enable either in Settings. It's gone.
…On Tue, 27 Feb 2024, 01:08 김도훈, ***@***.***> wrote:
@AndreiRegiani <https://github.com/AndreiRegiani>
If it doesn't work on Samsung devices, check the Share Modal and make
sure there is a Nearby Share button. If it does, try to tap the Nearby
Share button instead of 'Quick Share' - if it doesn't work, I don't know.
—
Reply to this email directly, view it on GitHub
<#140 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALGJVKXIIU2FY4YL7GXKYLYVVL4BAVCNFSM6AAAAABCVOSC3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRVG42TCMZWGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
THANKKKS THIS IS WOK FOR ME |
Pixel 8. Just upgraded to Sonoma and got the most recent NearDrop (I had the pre-Sonoma one installed). It worked the first time I used it, but after that didn't detect my mac. For what it's worth, the first time I tried (the time it worked), I think my mac was broadcasting both the pre-Sonoma and Sonoma versions of NearDrop, since I saw two devices show up in QuickShare. |
Hello
Does NearDrop work with the new nearby share implementation, aka Quick Share?
My experiments show that no :(
For the uninitiated, Google is joining forces with Samsung and introducing alternative in the form of Quick Share. It's rolling out now to supported devices.
My test was trying to share a photo from the Samsung S23 to the MacBook with neardrop v 2.0.2
It works with nearby share, but choosing new unified Quick Share — it doesn't detect MacBook
I'm curious how this new application works from the inside and whether it will be possible to implement these protocols here
The text was updated successfully, but these errors were encountered: