What bugs does Sailfish X have?

Thanks, that's much better. For number 10. what is the workaround you mention? Recompiling the kernel?

About no. 9: "reported and apparently fixed upstream already" - do you have a source for this information?

The volume in both the earpiece and the speaker, isn't really high. This is an important issue. What is the status? See: https://together.jolla.com/question/169291/xperia-x-speakerphone-volume-too-low/

I have an issue where the screen, directly after awakening with a power button press, is totally unresponsive, so you either way for it to time out and re-sleep, or hit the power button twice (to dismiss the awakened screen and then wake it again) in order to be able to swipe the phone on.

I also find the keyboard in Android a little buggy, sometimes touching a text field will bring up the keyboard, but then it automatically disappears after a second.

I also cannot get google maps to utilise the GPS data, I can see with sailfish apps that the GPS is locked in and working, and yet gmaps does not show a location.

you mean speaker? indeed!

But few times i used handsfree coorspondent complainded so much about echo it had to be switched off. In my case handsfree works but sound quality is so poor that it can't be used. It was in quiet room with phone on a steady wood table at about 50 cm. Anyway realy like to use sailfish X.

It sets the region based on what mobile network (not what country of SIM you have) it is connected to. This is set upon boot.

i also have the same audio issues.

Do you have doubletap-to-wake enabled?

It seems that will sometimes behave so that lockscreen is shown but you cannot swipe left or right to enter the lock code. Short press to powerbutton to shut display and retrying works after that.

Withlut doubletap enabled, I never have this problem.

Yes I have enabled double tap. Thanks, that must be it!

Double tap doesn't work fine, if you've actived it, this is the cause of this issue

The GPS works ok for me on HereWeGo and Sportstracker.

Turn by turn directions on HereWeGo work well, however since text to voice isn't available there are no Street names included in the turn by turn directions.

GPS on google maps works fine here, using it daily when driving.

I just went on a trip with my car and getting any valid gps location at all was a real pain (I used HereWeGo). I also had a problem with Sailfinder (the Sailfish tinder app) often getting a completely wrong location for me, which may or may not be related to that. Jolla always claims to have a fix (gps icon not blinking, but being solid), but it seems to be almost completely broken for me... maybe someone has a suggestion how I can reliably check if the phone has a correct gps fix...

I used Waze each day ... And I din't get any problem with GPS position ...

Unbelievable that i am the only person that consistenly has issues with SFOS GOS integration when it comes to Android Apps, for Example maps.me just doesnt work!

I did confirm that Here actually works (just dont trust my GPS data with them, neither with Google or Waze, which places all those off the menue for me); i am looking at an open streets map implementation.

Is this still the case? So of the 32gb on the X you can only use 2.5gb? I'm confused by this one!

I really want to move to sailfish and would love an Xperia X (or XA2 if all set) to install it on but I'm constantly put off hearing these issues. The trouble is; 1) It's not easy to get hold of an Xperia X any more in the UK that you can be confident it is unlockable 2) It's then not easy to ensure the DRM keys are backed up and to restore them to return the X if there are so many bugs that I think the phone is unusable as my main phone.

@mr_xperia :

Note :

• here the situation is slightly different than what we have discussed in your thread.
• it's still the "only 20GiB partition" problem
• that partition is split using LVM into a / (a.k.a root) partition, and a /home.
• android stuff goes into /home/.android/data/ so it's not relevant here (and these apps tend to be huge)
• some native apps can put stuff into / (mostly into /usr/share)
• for some reason, some of the native apps that @objectful has been using put way to much shit in there. (<- that's not normal behaviour to begin with )
• also for some reason, said apps don't have a nice user interface to move the shit to the SD card ( <- that's a big UX issue for the app, file an issue to the devs.)

There's a possible manuall fix to circumvent :

• Put symlinks that divert whatever directory gets too full toward the SD card.
• e.g.: Stellarium (that's the biggest example I could come up with) puts 80MB worth of star maps in /usr/share/stellarium.
• move Stellarium: mv /usr/share/stellarium /run/media/nemo/MyData/
• make a symlink : ln -s /run/media/nemo/MyData/stellarium /usr/share/
• problem solved.

It's not a problem for the Jolla 1 because :

• Sailfish X on Xperia X uses LVM to statically split the available 20GiB into 2GiB root and 18GiB users' home.
• Jolla 1 use a feature of the BTRFS that grow dynamically sub-trees inside the same partition space. the ~14GiB space remaining for data is spread over the @ (root) and @home subvolumes of the BTRFS partition as need arise.
• This comes with its own set of problem if the partition runs out of 1GiB chunks for BTRFS to allocate OR runs out of 256MiB chunks to use for metadata. (The dreaded enospc error message) This is saddly highly likely on a tiny partition like the 13GiB of Jolla 1.
• But even that can somewhat be alleviated by better following official BTRFS recommendations

The end result is that way too many people got burned by the peculiarities of BTRFS (weird space management in 'chunks', very unusual recovery strategies - one of the rules of BTRFS is that you NEVER actually try to repair a filesystem, you only run fsck as a last resort when EVERYTHING else has failed).

And Jolla saddly decided to step aside from it, so since the Jolla Tablet and Jolla C you have space that is statically split using LVM, and EXT4 partition of fixed size.

The 2GiB root limit on Sailfish X stems from that, but shouldn't be a big issue under normal circumstances (the largest app I have is 80MiB, I barely exceed 200MiB of installed app data).

And is perfectly circumventable until Jolla comes with a better solution.

(Use du -s -c /usr/share/* | sort -n to get a list of space consumers)

Forgot to add regarding the symlink trick :

this works WAY BETTER if the SD card is formatted with a non-stupid file system.

Use something unix-y, at best : BTRFS, F2FS or EXT4.

So that anything that you moved app needs in the original EXT4/BTRFS partition in /usr/share/{app} , such as access rights, extended attributes, advanced access control, etc. keeps working once moved to your EXT4/BTRFS/F2FS SD card.

Forget about FAT32 and exFAT, they are b0rked by design

(For FATnn-family, that is partially excusable : it's an evolution of an extremely ancient file system that dates back from the dark ages of 16bit home computers, and that was about what you could do with the limited ressources.

But exFAT ? Why, gods, why did Microsoft need to inflict us this crap ? Specially when there was already UDF as a partition format used by nearly everyone, and specially geared toward less writing (one variant of it was even used on CD-R and DVD-R, things that can only be burned and never overwritten !), but no Microsoft desperately needed to come up with a new shit...

...oh, yeah. I know. A broken attempt at money grab by using patents. I hate you, Microsoft)

After years of maturing: The rootfs is still too small! ...

Behaving the other way round for me - when listening to music over a BT headset, a phone call will not be routed to the headset, although the music stops. The only way for me to take the call is to switch on the loudspeaker. Using 3.0.0.8 on Xperia X. Now upgrading to 3.0.1.11, will see if that helps.