We have moved to a new Sailfish OS Forum. Please start new discussions there.

Sending files from PC to Jolla by Bluetooth is extension dependent [answered]

asked 2014-09-03 12:35:07 +0300

cocof2001 gravatar image

updated 2014-10-05 23:34:41 +0300

I have a simple text file (test.txt) on my PC. This file I am able to transfer to my Jolla. If I change the extension to .pem (.random), when I try to send the file to Jolla I get "The request could not be honored". I want to know if this is a bug or a limitation. If this is a limitation is there an explanation?

UPDATE: I have created a Feature Request for full Bluetooth file transfer support here: https://together.jolla.com/question/57789/full-bluetooth-file-transfer-support/

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by cocof2001
close date 2014-09-25 11:54:45.636540


1 Answer

Sort by » oldest newest most voted

answered 2014-09-25 11:06:06 +0300

hmallat gravatar image


it's a limitation of the current implementation. File extension is used to check if there's an application on the phone that can handle the incoming file (unfortunately sending the file mime type of the file in a header is not mandatory for OBEX transfers). This is needed for two reasons:

  • to be able to open the file from the transfer list with a suitable application
  • Bluetooth qualification requires that unsupported files are rejected automatically; of the file types mentioned in BT specs we don't currently support receiving calendar or message files.

So, unfortunately you need to use other means like scp to transfer files for which there isn't any application that can receive them.

edit flag offensive delete publish link more



Thanks for an answer, but ...

"unfortunately sending the file mime type of the file in a header is not mandatory for OBEX transfers" -- yes -- fortunatelly, because as it is now I have to rename rejected file (usually some *.deb) to something binary like *.png to transfer it back and forth between PC an Jolla.

I have feeling that sometimes developers want to dumb users by letting phone handle everything. Back in "the old days" you can throw anything through bluetooth and was transferred with no questions. There is still "FILE TRANSFER PROFILE" present in BT standard. Why not use this for transferring files? Once file is transferred user can launch & choose what to do with file.

I really wish Jolla wouldn't limit usefullness of Bluetooth as some other vendors does. BT specs can be found here: https://www.bluetooth.org/en-us/specification/adopted-specifications

/rant off

sponka ( 2014-09-25 15:33:55 +0300 )edit

Re Obex-FTP, it's not officially supported on the device because we didn't qualify it. Qualification of BT profiles costs time and money. If there is enough demand, it might be included in a future update. Please make a feature request.

And as mentioned BT SIG qualification for Obex push requires that unsupported content is rejected, regardless of whether we want to let everything through or not.

hmallat ( 2014-09-25 15:54:46 +0300 )edit

that does not explain why it is not possible to transfer files with the extensions .ogg .flac .aac and .ac3 that could be handled with mediaplayer...

lpr ( 2014-09-26 19:47:26 +0300 )edit

lpr: Mediaplayer should be registered as a handler for audio/ogg (and other types) but is not, I'll file a bug for that. Thanks for noticing the issue.

hmallat ( 2014-09-29 09:52:35 +0300 )edit

Which configuration file needs to be modified, to force bluetooth to accept files regardless of the "type"?

Maybe this is somewhere in the bluetooth specification, but is is such an idiotic limitation, that an override must be available to the user. I have not bought an iToy but Jolla.

ortylp ( 2014-10-03 22:06:15 +0300 )edit

Question tools



Asked: 2014-09-03 12:35:07 +0300

Seen: 715 times

Last updated: Oct 05 '14