Open mochaaP opened 1 year ago
I believe sending is mostly working but it doesn't work with Android and NearDrop for some reason - will have to figure out why :)
hello any updates on this?
Hi, I haven't started working on this yet. I'll have a look once I have some time :)
Did a bit of work on this but now I'm a bit stuck. Android seems to be understanding all the messages until the file payload is actually sent - and then throws an error in logcat.
Read an unencrypted and invalid frame when we expected an encrypted one, discarding. Protocol message contained an invalid tag (zero).
I'll keep digging and post updates when I have something to share :)
I believe sending to Android is working now. Please let me know if you come across anything weird!
Should also update README for this change.
Updated. Not sure if this works with NS on Windows but it would be great if someone could let me know :)
I tried sending with qnearbyshare-send
to "Nearby Share" on windows and it works but the file name is just random numbers.
If I try it the other way around, nearby share says that connection failed.
I tried sending with
qnearbyshare-send
to "Nearby Share" on windows and it works but the file name is just random numbers. If I try it the other way around, nearby share says that connection failed.
Can reproduce on my side with Nearby Share for Windows 1.0.1184.0
Sending files from Windows works, though.
Guess I'll do some digging - anyone know if NearDrop does the same thing?
All good so far (send/recv to Android/Windows), it's just Nearby Share for Windows reporting the wrong filename when receiving from QNearbyShare.
Hi @vicr123 , thanks a lot for this project. I am using Arch Linux and I have successfully transferred from Android and received by the QNearbyShare. However when I try to send from QNearbyShare the scan returns no targets:
[mcako@myarch]$ qnearbyshare-send test.pdf
:: Scanning for devices...
No targets found.
I was wandering if you can give some pointers of how I could debug this. I am thinking if this might be a Permissions/iptables issue. Any input will be appreciated!
Hey, they used to have a button in the Google Files app that would open Nearby Share in receive mode, but it looks like they've moved it somewhere and I can't find where they've moved it.
If you can find it though, you'll need to open Nearby Share in receive mode before QNearbyShare can find it.
This is very unfortunate. They have completely rearranged the settings for nearby share on my Samsung S20. It's now merged with quick share and for now i can't find any solution to open nearby share in receive mode. Do you have any plans to make qnearbyshare work with pop up notification like it does when sharing with another android phone?
I'd love to make that work but I probably need some help with someone who's more familiar than BLE than I am
This seems to also be reported at grishka/NearDrop#150
Neither working for me: I can send files from my Pixel 8 to my Macbook M1, but I can't the other way around. It can't find my phone although quickshare visibility is set to everybody. Weird:
Neither working for me: I can send files from my Pixel 8 to my Macbook M1, but I can't the other way around. It can't find my phone although quickshare visibility is set to everybody. Weird:
try opening activity com.google.android.gms.nearby.sharing.ReceiveSurfaceActivity
on your phone. I recommend using Activity Launcher from the play store and setting a shortcut for it on your home screen.
See https://github.com/grishka/NearDrop/commit/8f0eccd7b62b380cdff045ef53fe40f087e50e9d for a reference implementation.