Ask / Submit

mounting Jolla from Linux computers

asked 2015-12-25 19:41:29 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2017-01-30 11:28:50 +0300

jiit gravatar image

File handling is severely hampered since the update. Linux seems to be unable to view or store files on the Jolla, just transferring to the computer's local hard disk is possible. Tested with Linux Mint 17.3 and Fedora 23. The phone is mounted using MTP nowadays, after this update. It used to me mounted via gphoto2: back in those times file handling posed no problem, images in the Jolla internal memory could be viewed and saved, also to and from the SD card.

Windows XP fails as well. Windows 7 and 10 seem to have no problem with correctly mounting the phone's file system.

To me it looks like something went wrong in the way the phone is mounted (the way it is recognized by Linux computers).

What can I do to solve this issue? How can I change the protocol used for mounting the device, or the way the phone is giving info to the OS to be recognized and mounted?

Thanks for all info

best regards and merry Christmas!

edit retag flag offensive close delete


my brand new Saimaa2.0.0.10 has the same issue: When the sd card is inserted it most times (!) fails to connect to Linux (Fedora 10).

dmesg tells:

usb 1-5: USB disconnect, address 27

usb 1-5: new high speed USB device using ehci_hcd and address 28

usb 1-5: configuration #1 chosen from 1 choice

usb 1-5: New USB device found, idVendor=2931, idProduct=0a05

usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

usb 1-5: Product: Sailfish

usb 1-5: Manufacturer: Jolla

usb 1-5: SerialNumber: DU3C601030

usb 1-5: USB disconnect, address 28

gvfsd-gphoto2[5996]: segfault at c ip 00bf9a00 sp bfc44e84 error 4 in[bf2000+16000]

usb 1-5: new high speed USB device using ehci_hcd and address 29

usb 1-5: configuration #1 chosen from 1 choice

usb 1-5: New USB device found, idVendor=2931, idProduct=0a05

usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

usb 1-5: Product: Sailfish

usb 1-5: Manufacturer: Jolla

usb 1-5: SerialNumber: DU3C601030

Segfault - is that a cute pet?!? Using the Jolla w/o memory card most times works.

My first impressions of my very first Jolla phone are depressing, devastating. No hidden WiFi, no USB connect, no usable RSS-Reader, no proper access to the memory card, Better care of the one half that matters than for the "other half" gimmicks. Really an immature nonsmart-phone.

dietmar ( 2015-12-26 00:34:23 +0300 )edit

I correct myself: The 25th attempt WORKED! All Jolla memory is available via USB mount. This means it is feasible, the Sailfish methods are right (in principle).

There is light at the horizon:

What I found:

If you have the phone in normal mode it is unlikely to connect via Linux USB mount.

It is LIKELY TO WORK when the phone is in DEVELOPER mode.

It always shows as a camera (same in Ubuntu and WinXP).

This provided my old Fedora 10 Cambridge can sometimes transfer files to the phone memory as well as to the sd card in the phone.

Whatever it means: It shows there is some adjustment necessary in the phone / Sailfish (here: Seimaa

Further findings:

Ubuntu 14.10

can show the presence of Jolla when the Jolla is in Dev.-mode. It did not give access and shows a lot of error messages (anyone interested in details?) Ther is nothing recognised when Jolla is not in dev.-mode. The icons even disappear when I switch off dev.-mode on the phone while connected.

Windows XP

on my old machine shows eactly the same behaviour like U14.10 except it does not reveal messages about issues.

So it is clearly a bug in Sailfish How to proceed? I'm a newbee, no clue, no idea ...

dietmar ( 2015-12-26 00:50:59 +0300 )edit

I use Fedora 23 and doesn't have any problem with Jolla. I just put the phone in PC connection mode and then i have to wait a few minutes to see the phone in the file manager (shows sd card and internal memory). I can even synchronise my music with Banshee and Rhythmbox player via MTP.(Sailfish

Hans ( 2015-12-26 11:47:56 +0300 )edit

This is clearly dependent on the OS that tries to mount. It does not depend on the hardware on the connected machine. It seems not to depend on Wayland/X/Gnome stuff. Let me show:

  • My laptop (older HP) with Fedora 22 does refuse to connect to Jolla like WinXP and U14.10.

  • The same laptop running U15.10 connects to Jolla Sailfish with ease (not using dev.-mode)!

The problem showing in dmesg is stating the same on all machines:

"usbfs: proces nnnn (pool /or/ events) did not claim interface 0 before use"

So it is clearly a Sailfish configuration issue.

As said before :

quote: "To me it looks like something went wrong in the way the phone is mounted (the way it is recognized by Linux computers)."

This is the point.

dietmar ( 2015-12-26 12:23:34 +0300 )edit

I just tried it in kde4 and it works as it should. I get 3 options.
1. download to gwenview (import using camera:/ ) i guess it's the same as gphoto2.
2. open with filemanager uses camera:/ and let's me open and browse files but not write anything (camera:/Jolla%2520Sailfish%2520(ID2)@usb:005,010/).
3. open with filemanager uses mtp:/ this one let me do anything i can read and write browse just as i want (mtp:/Sailfish/Mass storage/).
If you ask me it sounds like your device doesn't mount properly and you use the camera:/ instead of mtp:/

abc123 ( 2015-12-27 00:36:16 +0300 )edit

6 Answers

Sort by » oldest newest most voted

answered 2015-12-25 19:45:31 +0300

updated 2015-12-25 19:47:04 +0300

You could try SFTP instead of MTP. Here's a how-to:

Or if SFTP doesn't suit your needs, try mounting your Jolla via SSHFS. Here's some instructions:

edit flag offensive delete publish link more



@jollailija Totally forgot that SSHFS thing... Thanks for the hint :-)

ced117 ( 2015-12-26 00:41:37 +0300 )edit

The samba build on openrepos work flawlessly too.

But I've given up some month ago, on both Jolla and Sailfish. It's a burning platform. Never looking back on it one second. Just walked in to see how people are desperate to get basic things working.

dietmar is SO right about his impressions on his Jolla, its just too much crap to overcome. If Jolla would have fixed the most important things while they had time instead of going even worse with 2.0 I just might have cared, but its way too late.

Larswad ( 2015-12-28 15:14:02 +0300 )edit

@Larswad I've had my Jolla for about half a year, and I have no idea why people are complaining :P Of course it isn't the most polished thing and it misses some basic stuff, but still.
Meanwhile my fruitPad fails to sync and the only option to fix it is to perform a factory reset (and iTunes seems to be really keen on doing it). Seems like both sides of the coin have their own problems.

jollailija ( 2015-12-28 18:52:03 +0300 )edit

@jollailja: Well, I (had) mine for nearly two years and the road was all just bumps and dead ends. In contrast to what everyone claims, this is not really a true Linux device with all that flexibility and extensibility. It's a homemade distribution with some lipgloss attached to it. It lacks so much stuff and carries so much irritating bugs and usability problems that it's not worth being called user friendly. It was a relief when my screen cracked. I had already ordered my Nexus. For Linux I stick to PC until something ACTUALLY community driven turns up. SFOS and its ecosystem is still way too immature and dysfunctional, not to say the bunch of promises (lies) told by the company. I can understand well enough why Dillon ditched the boat. I am not going to give you the list, if you don't see the overwhelming amount of missing or buggy stuff you simply have no idea what can be expected from a mobile OS today. And no, I'm not a droid nor iPhone fan, I simply see where this is going. For me, the "unlike" slogan became exactly what it should mean.

Larswad ( 2015-12-29 00:57:00 +0300 )edit

I'll just leave this here for you :)

jollailija ( 2015-12-29 11:54:50 +0300 )edit

answered 2017-01-24 22:12:08 +0300

Georg gravatar image

I'm running Linux Mint 18.1 by now; problem solved! Already starting from 18.0 everything worked as expected: Jolla is mounted using mtp when connecting via the PC mode (not fully reliable, though), so otherwise I'm using the developper mode and sftp (or the secure copy scp -p command, for preserving file modification info). Thanks for all your suggestions and the interesting discussions! Cheers, Georg.

edit flag offensive delete publish link more


@Georg thank for reporting cool that it works for you. that's good news.
Just for understanding, does it mean that with mint 18.1 you didn't have to do something and it worked then? Or one of suggestion above made the trick?
thanks in advance for the precision.

cemoi71 ( 2017-01-24 23:34:25 +0300 )edit

@DaveRo cool that you report it. maybe it is more as answer than a comment to be considered.
By the way too have this right problem. but i think that is changeable. I remember that i tinkered to have the possibility for having my 64gb sdcards to format in ext4, et should change something for being able to have better access on mtp.
But i did so much experimented with, and didn't tried different right schemas.
i've just changed the ownership, but not the right (possible to be done too)...
You may have a look here, and i'll be glad for feedback, more informations, or updates.

cemoi71 ( 2017-01-25 14:12:28 +0300 )edit

@cemoi71 OK - I made it an answer

I also formatted 64GB sdcard card ext4 on my SUSE box (didn't know at the time that Jolla could fornat it) and couldn't access it. I can't remember exactly what I did to fix it - probably hit it with chowns and chmods - so I can't offer any definite answers about that. Sorry.

DaveRo ( 2017-01-26 10:43:58 +0300 )edit

answered 2017-01-25 00:53:33 +0300

DaveRo gravatar image

FWIW my Jolla C mounts OK on OpenSuSE Leap 42 & MTP - and has done since I got it. I can't always copy/paste between the windows (have to resort to sftp for multiple/some file types) but mounting and viewing is fine.

edit flag offensive delete publish link more


i like to see with which panel of system it would be easy to use it... :-) Many thx

cemoi71 ( 2017-01-27 17:21:12 +0300 )edit

answered 2017-01-17 16:14:31 +0300

deloptes gravatar image

Have a look into this workaround and let me know if it works for you.

edit flag offensive delete publish link more

answered 2017-01-17 17:13:34 +0300

cemoi71 gravatar image

i have an ubuntu based desktop os (14.04 lts) and installed the tools gmtp and/or mtpfs from the native Software-Center. and it still works now.
Please try to find and install them.
I made a report here, that is a little bit unclear, but i've still in mind that it was solve by just installing one of both or the boths.
I'll try to find some time to investigate and make it more clear.

edit flag offensive delete publish link more


jmtpfs did it for me on debian jessie. I guess it would work the same way in ubuntu as well, because ubuntu is based on debian

I still have to work on automated (or better to say system or ui driven) approach.

deloptes ( 2017-01-17 17:49:24 +0300 )edit

i didn't need to work on further configuration or setup after i installed those which i mentioned above.
It mount it automatically when i bound the device to the computer...
i can't tell you if i tried the jmtpfs, i don't remember those which i tried and didn't work for me.
Seems that gmtp and mtpfs are available in the debian repos.did you tried to test it?

cemoi71 ( 2017-01-18 12:35:23 +0300 )edit

Thanks for the information, so I'll look into how ubuntu does it. Perhaps it is related to my desktop then.

deloptes ( 2017-01-18 12:53:22 +0300 )edit

I hope that it rocks then

cemoi71 ( 2017-01-20 12:07:06 +0300 )edit

answered 2017-01-22 14:05:48 +0300

tapio gravatar image

see my post on

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2015-12-25 19:41:29 +0300

Seen: 2,052 times

Last updated: Jan 24 '17