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

User reports - Sailfish X

asked 2017-10-11 20:49:06 +0300

h.berd gravatar image

updated 2017-12-18 00:21:26 +0300

Please share your overall experience in this thread. I would love to hear how much you like or dislike Sailfish X.

For Example:

How is the performance in general. Is there a significant difference to Jolla C?

How is your experience with bluetooth connection still in beta?

How much time is needed to flash the phone?

Is the camera working fast? Can you post some pictures to let us see the quality ?

Many thanks in advance and all the best!

edit retag flag offensive close delete

Comments

6

Sample pictures from the camera would indeed be nice!

TomC ( 2017-10-11 21:32:23 +0300 )edit
11

...

How is the performance in general. Is there a significant difference to Jolla C?

Not very much to feel, but the scrolling is smoother

How is your experience with bluetooth connection still in beta?

BT seems fine

How much time is needed to flash the phone?

I needed about 30 min., but I think it is way too hard for many users. If nobody comes up with flashed phones, this will not get an successor. It is complicated, too much different steps...

Is the camera working fast? Can you post some pictures to let us see the quality ?

Is working, faster and the results are better than in Jolla1 or JollaC

poddl ( 2017-10-13 00:48:50 +0300 )edit
43

Something that nobody mentioned yet...

The colour notification LED is back!!!!

Giacomo Di Giacomo ( 2017-10-13 15:25:17 +0300 )edit
9

Yay! I love the colour notification LED :)

Beethoven ( 2017-10-13 16:30:22 +0300 )edit
11

Unbelievable, how simple things, like colour notification LED, can make people so happy. And how these simple things widely ignored in industry.

nlsn ( 2017-10-16 13:19:16 +0300 )edit

48 Answers

Sort by » oldest newest most voted
3

answered 2017-10-17 15:30:53 +0300

Freddo gravatar image

updated 2017-10-17 15:34:30 +0300

Sailfish X is my first experience with Sailfish, and I'm very pleased. The performance is great compared to the N9 I've used until now, which isn't really that surprising since the N9 is 6 years old.

No issues with bluetooth, I could connect it to my Streamer Pro just fine (which in turn send audio to my hearing aids).

Flashing the phone took quite a bit longer than I expected. Maybe 3 hours?

I'm very content with the camera, a noticeable step up from the N9!

My only complaint, really, is that the Android version of HERE WeGo won't work on it. Also didn't like any of the music players available for Jolla, so I'm using the Android version of foobar2000 mobile.

Oh yeah, I also had to format my new 128GB microSDXC card to FAT32 to get it to work. Neither the default exFAT or ext3 would work.

edit flag offensive delete publish link more

Comments

I like the music pplayer 'Muuzik' Here we go is working here. I installed f-droid from their website, then the yalp store, then HereWeGo....

poddl ( 2017-10-17 17:08:27 +0300 )edit
1

Did you try QuasarMX?

Giacomo Di Giacomo ( 2017-10-17 17:10:41 +0300 )edit
1

I have Here WeGo working on Sailfish X. Have you tried to install Google Play Services and setting GPS on from settings (I mean not the battery saving version, I mean the High Precition mode) ?

lumen ( 2017-10-17 18:28:06 +0300 )edit
1

Thanks all, tried it again and now I got HERE WeGo. Not sure why it didn't work the first time.

Gonna try QuasarMX some more, but first impressions are good. Thanks for the suggestion!

Freddo ( 2017-10-18 08:05:48 +0300 )edit
7

answered 2017-10-17 16:59:52 +0300

elaurin gravatar image

So far Sailfish X has been great! This is my first foray into Sailfish, coming from Android and BB10 before that. I love the smooth UI. Android apps work really well (better than they did on BB10). Startup boot is amazingly fast. The performance, in general is fantastic. It feels fast and fluid, more so than Android.

Flashing could have taken as little as 30 mins. It took me about an hour, but I missed two steps and had to repeat a few things. The dual instructions between Sony and Jolla get a little confusing. Overall, flashing was no harder than rooting Android and flashing custom ROM’s, but I think it would be too difficult for an average user, who is not comfortable with command line. The current setup process would probably deter every day users looking for a pick-up-and-go phone. I think that same crowd would otherwise really like Sailfish X.

Bluetooth works great. It is a bit slow to detect nearby devices (20-30 seconds – I’m impatient), but it pairs without a problem. There is an occasional hiccup (gap in playback) when playing music over Bluetooth to one of my devices, which gets annoying after a while. I haven’t determined if it’s the particular speaker/radio or the phone.

The camera works well. I love the easy access to manual controls! Fantastic! I haven’t used it much yet, but it felt fast and responsive. The Sony camera is really good (my experience from Android), so I’m expecting pictures from the Sailfish X will turn out really well.

So far my only issues are with the Media tracker (won’t detect all artist id3 tags) and MMS settings (resets every time the phone is turned off). It looks like there are solutions, but they require going into developer mode. That’s on my to-do list, but a few GUI settings or permanent fixes would be preferable. Despite these, everything does work.

Overall, I’m very happy with the switch to Jolla. Great job!

edit flag offensive delete publish link more

Comments

3

Android is peace of crap, had to use it since my j1 got old. There is no intuitive navigation through menus, refreshing emails does not work properly and many more. I go for Sailfish this evening if i have time to install :) so welcome to Sailfish, its awesome!

NuklearFart ( 2017-10-17 17:20:27 +0300 )edit

Description is quite accurate. Bluetooth has worked with everything, but connection is slower to establish than with Jolla1. I thought first that it did not work. Video playback is the only complaint sofar. It is not completely smooth (from SD), maybe the old buffer problem upstream?

I had MMS problems with Jolla1 too.

mj ( 2017-10-30 09:53:44 +0300 )edit

also bluetooth hickups on my end. It feels like some buffer problem and only happens with some bluetooth devices. My plantronics headset works without hickups for example, JBL Flip 3 has problems after some minutes of playback.

mosen ( 2017-11-02 18:16:45 +0300 )edit
7

answered 2017-10-17 18:25:19 +0300

lumen gravatar image

updated 2017-10-18 18:08:46 +0300

I'll need to to say a few things about the camera. I remember reading from Jollas pages that the paid version of the camera software will be more advanced. Well, for now, it is not the case...

I used the Android version of the Xperia X for about 3 months and now comparing to Sailfish experience about the same device.

  • Sharpness Somewhat there, but you need to have luck that the camera focuses correctly. It's not so sharp as Android version either. I read somewhere that Sailfish camera is not exploiting full resolution of the sensor. Here are my findings: Android - 3366x5984 px = 20Mpx, contrasty sharp pictures and video with quite good colour reproduction Sailfish - 2988x5312 px = ~16Mpx, less contrast, often blurry pictures and video, inconsistent colour results

  • Focusing Errr.. what focusing... I wouldn't like to use word horrible, but I can't come up with something better either. Camera seems to focus erratically "just somewhere". Focusing into any darker areas is a no go. You can't focus to something well-lit either if there are even brighter objects anywhere in the scene, because i.e. a face becomes dark if there is sky somewhere behind. You can forget also macro photos which worked very well with Android version. Tapping on screen to focus doesn't yield good results. Eventhough I've tried it few times, it seems that I get blurry results anyway. If someone has better results with focusing, let me know.

  • Colours A mixture of daylight and luminaires makes this camera go hay-wire. You get weird results of greenish and yellowish tones where you don't expect them. Android version controlled them well. When in even lighting conditions, it gives you decent results, I think. Atleast better than that Jolla 1 did.

  • General usage of camera Oh.. sorry I haven't had time to see if GPS coordinates appear to photos. Atleast Android version did them. Here is one pretty annoying thing. When clicking to take a photo, the camera has quite a lag before photo is taken. People have time to move around before captured. This happens especially with Whatsapp. EDIT: Happens only with Whatsapp Feels that I need to have camera pointed for many seconds stabilized, because everything feels blurry, shaky and there is this annoying time of black screen and you don't know what you're gonna get...

  • Video I haven't read it from anywhere, but I'm pretty sure Android version had image stabilization in the camera. If it was so, then with Sailfish that is gone. I'm not expecting Jolla to get that working anytime soon either...

  • Editing Android version had quite nice adjustment tools which I miss a bit. Sailfish has only lightness and contrast, you don't really do much with them.

Hope this helps somebody to decide whether to convert to Sailfish or not. I have to say that I was hopeful to get a little bit better performance now that there's new imaging chip made by the market leader... Jolla, please put some effort to this. The camera is under-performing in a huge way.

edit flag offensive delete publish link more

Comments

I didn't take extensive camera tests, but I cannot see the lag you are talking about whan taking a picture. On the contrary, I was surprised of the extremely fast reponse of the camera to the shutter button, the fastest I have ever seen even on digital cameras.

Giacomo Di Giacomo ( 2017-10-18 11:17:17 +0300 )edit
2

thanks Giacomo, I think youre right, it's only Whatsapp where the lag is, not with the camera app by Jolla! I'll update that above.

lumen ( 2017-10-18 12:30:47 +0300 )edit
1

answered 2017-10-18 11:00:40 +0300

mrtrm gravatar image
  • Trying to reach from my linux box through ssh gives me error: ssh: connect to host 192.xxx.xxx.xx port 22: Connection refused - worked well in my C-ified Aquafish
  • Bluetooth audio connection with JBL speaker and Cambridge audio speaker stutters easily (when browsing the web for instance) - worked well in my C-ified Aquafish
  • Tethering my mobile network to my laptop doesn't work (I need that when working in places where there's no Wifi) - worked well in my C-ified Aquafish
  • Miss the double tap to wake up the screen.
edit flag offensive delete publish link more

Comments

..

Trying to reach from my linux box through ssh gives me error: ssh: connect to host 192.xxx.xxx.xx port 22: Connection refused - worked well in my C-ified Aquafish

Is working here. On connection start make sure you're display is on.

Bluetooth audio connection with JBL speaker and Cambridge audio speaker stutters easily (when browsing the web for instance) - worked well in my C-ified Aquafish

Same here

Tethering my mobile network to my laptop doesn't work (I need that when working in places where there's no Wifi) - worked well in my C-ified Aquafish

solution for tethering

Miss the double tap to wake up the screen.

Serach the forum, there is a solution for it.

poddl ( 2017-10-18 12:39:24 +0300 )edit
1

@poddl: thx a lot! 3 of 4 of my major issues solved!

mrtrm ( 2017-10-19 10:19:36 +0300 )edit

works very well for me. i had to set a fixed address, the password and then i could login as nemo. just like with my jolla 1 before. to get to the device with the kde file manager dolphin i had to delete the host key first that had appeared in my known_hosts. then sftp access in the file manager worked, too.

jabgoe ( 2017-10-20 16:01:39 +0300 )edit
3

answered 2017-10-19 08:49:15 +0300

revers gravatar image

How is the performance? I think its good. Everything goes smooth.

How is your experience with bluetooth connection still in beta? Not yet tested!

How much time is needed to flash the phone? For me it took about 10 hours. I had to watch some youtube vids because the explanation provided from Jolla and Sony is rather poor. Unlocking the bootloader was tricky and took me quite some time to understand. The flashing part was rather quick.

Is the camera working fast? Can you post some pictures to let us see the quality ? Not yet tested.

I have still some other problems: I cant make the SD card to be mounted or recognized. I cant even format it with my Experia. The card itself seems ok. I put it into the computer and works fine.

Any ideas?

The other thing bothering me is the hint when i start the phone because of unlocking the bootloader.

edit flag offensive delete publish link more

Comments

1

Try formatting the SD card to FAT32 on your computer. Worked for my 64GB SanDisk card. There are some more questions on TJC about other SD issues too.

Kao ( 2017-10-19 08:56:48 +0300 )edit

Unfortuntely it doesnt work. Maybe the SD -Card is broken. Have to try another card.

revers ( 2017-10-20 18:40:17 +0300 )edit

You can try ext4 before. See my experiance.

Filip K. ( 2017-10-22 17:13:19 +0300 )edit

@Filip Thx for the info. may try it next time. i used a sd card from an android tablet and it worked. restored the files from my Jolla 1 o Sony. Worked fine!

revers ( 2017-10-23 08:44:42 +0300 )edit
2

answered 2017-10-19 09:51:54 +0300

Hedexed gravatar image

updated 2017-10-21 11:40:12 +0300

The letter 'æ' is missing from the keyboard; will be an issue for Norwegian users. The other special characters used in Norway are present though ('ø', 'å')

Edit: 'æ' is available if selecting Norsk keyboard layout; thanks silta for the tip

Android-integration: Spotify - 'pause' and 'next song' -buttons are missing on lock screen; only song name and 'previous song' -button is displayed.

The phone is much cooler (as in temperature) than when running with the stock Android OS :)

edit flag offensive delete publish link more

Comments

Oh, was just about to purchase today, but living without æ is currently a deal breaker for me. Any hopes that this can be fixed soon? :)

StorOddnoga ( 2017-10-19 13:26:19 +0300 )edit
4

Go to settings > Text input > Keyboards, check Norsk, go back to Text input, tap Active keyboard on the top, choose Norsk, tap Active layout on bottom, choose Norsk, done.

You can find æ in the second row on the right side.

silta ( 2017-10-19 17:58:47 +0300 )edit
3

answered 2017-10-20 15:32:19 +0300

jabgoe gravatar image

updated 2017-10-20 16:52:42 +0300

i wish i had read the instructions about backing up the dpm keys before unlocking the boot loader ... :(

flashing with linux was a little difficult since updating my xperia's android didn't succeed in reaching the necessary version. as a result the flash script failed to complete. i managed to find a workaround with infos from the previous instruction of the community version (http://talk.maemo.org/showthread.php?p=1536613#post1536613). so the process of flashing took about 3 hours.

restoring the backup (from my old jolla 1) was a litte disappointing. messages, accounts and such were restored ok but i would have expected a backup-restore procedure also to backup and restore my applications. this didn't happen.

i cursed the bluetooth implementation of sailfishX until i remembered the concept of pairing my headset first ... now it works.

google maps from the android store is a sufficient substitute for the here maps.

i'm missing a (functioning) native telegram client.

after about one week i can say that everything works great. the screen is fast, connectivity (phone, net) is good. i'm missing the double tap. battery life is astonishingly good. didn't test tethering and other bluetooth devices than my headset, though.

for my personal use case everything is very well and a great improvement from my jolla 1.

it would be better, still, with fm-radio ... :)

edit flag offensive delete publish link more

Comments

I didn't save Android DRM keys before flashing, as I have no DRM-protected content and do not use Google Play Store (just Yalp Store for a small number of apps, like online banking). I assumed SailfishX would come with its own keys if required.

Anyway, apparently to save DRM keys you need to be root, to be root you need to unlock the bootloader, to unlock it you need to save TA partition, to save it you need to be root...

Did I miss something?

objectifnul ( 2017-10-20 21:31:46 +0300 )edit
1

@jabgoe if you will need backup your openrepos apps in the future use storeman https://openrepos.net/content/osetr/storeman

atlochowski ( 2017-10-21 11:58:36 +0300 )edit
1

@objectifnul: Yes!

"DRM keys" is a misnomer, they are really "Secure Boot certificates for TEE applications". And these applications for Sony's TEE (Trusted Execution Environment) are residing together with the "DRM keys" on the "TA (Trusted Applications) partitions".

The TA-partitions are erased, while unlocking a modern Sony Android smartphone.

Without them, Sony will not provide warranty.

So creating a backup of the TA-partitions is only good for enabling one to restore a Sony phone to a state, where warranty is applicable (in case you need that)!

How to achieve that is described here: https://together.jolla.com/question/168711/xperia-x-backup-ta-partition-before-unlocking-bootloader/

olf ( 2017-10-26 00:49:41 +0300 )edit
3

answered 2017-10-20 16:26:50 +0300

objectifnul gravatar image

Why did SailfishX drop the BTRFS file system? Technical or legal reasons?

edit flag offensive delete publish link more

Comments

bad experience from J1 I guess

pmelas ( 2017-10-20 23:07:26 +0300 )edit

@pmelas Well maybe BTRFS raised some issues with J1. However, I experienced some issues with SailfishX' current file system too: try to open any file explorer (filebrowser, filetug, cargodock, filecase) in 'root' mode using Schturman's hacks (in openrepos), and you'll probably see that in most cases you can't access /root unless you wait for 'some' time (not too short, not too long) before re-opening your favorite explorer in root mode after you've closed failed instance(s). The 'new' file system has an unpredictable behavior in some circumstances.

objectifnul ( 2017-10-21 01:41:17 +0300 )edit
2

answered 2017-10-21 17:02:43 +0300

Mack_ gravatar image

When you turn of your phone and restart, do you have a text: "your device has been ulocked and cant be trusted"

edit flag offensive delete publish link more

Comments

1

Yes, that is because of the unlocked bootloader. But don't worry, it is just a cosmetic issue. See here: https://together.jolla.com/question/169012/sailfish-x-startup-your-device-has-been-unlocked-and-cant-be-trusted/

Kao ( 2017-10-21 17:23:30 +0300 )edit
2

answered 2017-10-21 19:39:13 +0300

dysko gravatar image

is it only me or we are missing 16GB of space? Device has 32 GB but i am seeing only 16.

edit flag offensive delete publish link more

Comments

2

It is not just you, seems like this is a general issue. Unfortunately no solution yet. See here: https://together.jolla.com/question/168968/xperia-x-internal-storage/

Kao ( 2017-10-21 20:19:40 +0300 )edit

now that you mention it. the same problem with my xperia.

jabgoe ( 2017-10-23 17:09:16 +0300 )edit
Login/Signup to Answer

Question tools

Follow
24 followers

Stats

Asked: 2017-10-11 20:49:06 +0300

Seen: 23,490 times

Last updated: Jan 08 '18