mounting Jolla from Linux computers
asked 2015-12-25 19:41:29 +0200
This post is a wiki. Anyone with karma >75 is welcome to improve it.
File handling is severely hampered since the 2.0.0.10 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!
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 libpthread-2.9.so[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 +0200 )editI 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 2.0.0.10)
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 2.0.0.10. How to proceed? I'm a newbee, no clue, no idea ...
dietmar ( 2015-12-26 00:50:59 +0200 )editI 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 2.0.0.10)
Hans ( 2015-12-26 11:47:56 +0200 )editThis 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 2.0.0.10 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 +0200 )editI just tried it in kde4 and it works as it should. I get 3 options.
abc123 ( 2015-12-27 00:36:16 +0200 )edit1. 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:/