Obex file transfer unsupported

Internet Download Manager. Advanced SystemCare Free. VLC Media Player. MacX YouTube Downloader. Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger. Talking Tom Cat. Clash of Clans. Subway Surfers. TubeMate 3. Google Play. Canon ink cartridge. Still, IMO Jolla should stop filtering for supported file types when receiving via BT file transfer in SailfishOS per default or offer a setting to disable this filter.

The current behavior "Oops, uploading did not work! Wow, 5 years since the original question and still Jolla has their fingers wedged firmly up their arses - no wonder people get fed up and leave. Such a simple function, yet this bunch can't seem to get it together, "Couldn't hold a piss up in a brewery! Still not able to send or receive any i. Even worse is that SailfishOS does not mention the real reason which is "unsupported file type" , but displays exactly the same error message which occurs when there is a Bluetooth connection error "Oops, uploading did not work!

Hence it is impossible for the user to distinguish an unsupported file type error from a real Bluetooth connection error. Please ultimately fix the file type limitations by allowing any file type to be transferred via Bluetooth. But I regularly forget and this is really awkward for a Smart phone! I cannot agree more, honestly how can something as basic as bluetooth file share is a bug or limitation on sailfish, I am so disappointed. I do hope it is the priority of any future update for crying out loud!!!

Yet Sailfish rocks, best os ever, and after all the little bug fixes in your numerous updates I can't even begin to imagine how beautiful it would be A partial fix for this issue was delivered in update 2.

We know that it is still not possible to share all file types but most of them , including. However, it is possible to share json and log files, for instance, by adding the extension. Investigations are carried on. Hopefully this issue can be fixed completely. Thanks for the official statement. I'm actually wandering why the filetype is an issue at all So the file is not getting analyzed This sounds as if a clear, rather political choice should be made by Jolla as the technical aspects have been sufficiently discussed between these three options:.

This has been implemented in 2. You are right but IMO it's not fully implemented yet since you are still unable to send multiple files at once and still not all file types are supported e. Also this bluetooth file sharing additionaly should be included into the relevant native apps e.

Maybe close this question and write new ones for specific features like those you mentioned then? Or tag it as partially implemented or something. I don't think sharing. What other file types are not supported? The answer and solution are already here in this very TJC thread! See my comment to the original question for an explanation and the link there for a solution. Thanks olf.

But after "downgrading" to XA2 I just forgot to apply that. In fact looking some time ago into the BT stack implementation it was clear that only OPP is implemented, while file transfer is not, because it needs all the things mentioned in the answers API, integrated APP etc.

I was even thinking I would find some time to write the server part, but not likely before next year. If someone is willing to share burden let me know. ObjectPath path ,. This takes the path of the transfer Session object and removes it. Remove all the session's transfers. Remove the session itself. This doesn't complete the transfer; code to mock up activating and. The test. The filters parameter is a map of filters to be applied to the results.

Returns a tuple containing the path for a new Transfer D-Bus object. Transfer object. Create a new temporary file to transfer to. Emit a behind-the-scenes signal that a new transfer has been created. It is emitted by the PullAll method, and is intended to be. The path is of the new Transfer object, and the filters are as provided to.

The transfer filename is the full path and filename of a newly. The test driver should then call UpdateStatus on the Transfer object each.