Yesterday I tried for the second time to send a file from my FP3 (3.3-t) to another FP3 (3.3-t) and I failed. I failed also already under 3.2-t.
Both devices are paired. Pairing itself does also still work.
What currently doesn’t work at all is establishing a proper connection which is then stable and usable. When I want to make a connection it comes up on both devices but then breaks in just three or four seconds. I can’t use it for anything. Especially I can’t send a file.
I remember this did work. Sending some pictures or whatever hasn’t been a problem a year ago.
When I try it with a Windows PC again pairing is successful and I can indeed make a connection which seems to be stable for more than just a few seconds. But I also can’t send a file, it fails in both directions, always. Why is this so complicated??
Does indeed nobody have this problem? So it’s mine alone?
Did indeed fail for me on 3.2-a15-20251025540112-community-FP3.
But did work again for me on 3.3-a15-20251213556761-community-FP3.
Or in other words (by the Business Insider from 2018) …
Yeah, thanks, but this article says only: “We’ll just have to wait and see.”
The German translation from Firefox is great: “Warum ist Bluetooth immer noch sauger?” Yes, why???
Interesting is, Bluetooth to other devices (headphones, speaker, sports watch) does mostly work in my environment, also over hours. But from /e/ device to /e/ device is works never. And to the PC I did also always fail. So the other device has indeed an impact.
The article says Bluetooth suffers from the 2.4 GHz frequency being crowded, but that isn’t the point. The point is that Bluetooth was always unreliable, is unreliable now, and (as a reasonable projection from its decades long history) will be unreliable in the future until it is gone.
Yes, OK, but as I said before: some connections do always work [1] and a connection between two /e/ devices does never work. There must be a substantial none-random reason. And because the breakdown happens indeed every single time in just three seconds it should also debugable, either on the one or on the other side.
Not that I depend on this. But Bluetooth has been one almost standard way for file exchange. When you now have a bigger file you can’t send per e-mail anymore you must indeed think about an alternative way. I did open a HTTP server for file exchange, the other side needs then just a browser to download the file.
[1] I do for instance complete firmware updates on a sports watch via Bluetooth - this connection is stable for 20min, never had any problem