Did you have success with that eventually? I tried doing that a few years ago and gave up entirely, convinced myself that it was an impossible task and that the thought that I could was a misunderstanding of how Bluetooth works.

I ended up with device listed as "paired" while the process have clearly failed (with a message :) ). And while incoming files were detected, request for save never followed. I've transferred file using MTP over USB, but in that case it interrupted on every action (like changing directory) requiring to re-enter "file transfer mode" on the phone.

Dang, congrats. My phone's usb port was damaged at the time and I couldn't maintain usb connection long enough to get file transfer working. Think I tried ssh'ing into my phone after that and was immediately in over my head. Tried emailing the file to myself but my email provider wasn't letting me open it on that grounds that it thought it was a virus (was an apk file). I don't even remember how I ended up getting it working.

And as I think about it, I think I did get to the same spot as you, with the device 'paired' but not really. My theory now is that bluetooth works on a controller/client relationship, and that both your laptop and phone are trying to be controller and are thus incompatible with each other, while things like headphones would be clients. Would love to know if someone more familiar with bluetooth could correct me.

Eureka: I forgot about ADB! Next time I'll just "adb pull". But that's only convenient if you know exact path. And have dev mode working.

To this day I end up using `python -m http.server` (sometimes sending myself a url) to send files over wifi rather than try to wrangle bluetooth.