Sailfish 3 - Sailfish X Bug Fixes [answered]
asked 2018-08-25 16:56:12 +0300
Hi, I have read through many of the Sailfish X / Xperia bug threads on here, including what seems like the main one as it's a wiki and quite comprehensive: https://together.jolla.com/question/171437/what-bugs-does-sailfish-x-have/ (with some reasonably fundamental bugs still on there).
Has there been any official communication on whether the imminent Sailfish 3 will be addressing any of these items? I'm so close to biting the bullet, setting sail and joining the sailfish club by getting an X and buying SailfishX but am a bit put off by some of the issues listed, for example no speakerphone? Tiny available internal disk space? Roaming issues + mobile settings getting lost?
It's also hard to tell from that thread, how many people have the particular issues, how many are rogue problems unique to one individual / device and how many are widespread. Is there any resource to monitor the bugs and how prevalent they are? It would be great if there was a list bugs along with a list of users that experience those bugs - a bit like you can see on Github with something like a thumbs up on a particular bug.
Apologies if this shouldn't be a new thread I just felt it would be good to get answers as to whether any bugs listed were being / have been addressed in the new Sailfish 3 release.
usually this list is part of the release notes
pawel ( 2018-08-25 17:30:28 +0300 )We don't get notified or told what is or what isn't going to be fixed, this is akin to "how long is a bit of string", the truth is, no one knows except those in the driving seats at JollaHQ. You might catch utterance of "we will address that in the next OS update" but it does not guarantee that it will. In my opinion, if you are heavily reliant on many aspects of a mobile device, then perhaps to hang back for a while longer until things improve.....but when might they improve?, no one knows, just like we don't know when SFOS3 will actually be rolled out, there are rumours and roughly said times, but those of us who have been here from the start, know that "it will be ready in xxx" can be taken largely with a pinch of salt and you maybe waiting months more. If you are keen, then just do it and strap in for the journey, you can always sell it if you don't like it, there is always someone willing to 'give it shot'. Personally, I have 2 x Jolla1 to kill before I even consider getting anything else.
Spam Hunter ( 2018-08-25 18:01:41 +0300 )You can get an idea from the number of upvotes that the bug thread has. For what it's worth, here's my data point: on my Sailfish X I had no roaming problems (except when trying to do actually impossible things like using the dual-SIM in a country with no 2G network), I never lost mobile settings, and I can connect my Bluetooth headset but I get some audio artifacts/interference if wifi is active. The internal space isn't too small; I have 45GB in the main partition (5122 w/ 64GB) and I'm currently using 15.
Federico ( 2018-08-25 23:23:39 +0300 )Speaker phone is fixed.
rfa ( 2018-08-27 01:13:02 +0300 )Regarding the roaming issues :
the latest version of
ofono(the system deamon that handles cell network connection) available in the current 2.2.0.9 verions of Sailfish X has immensly progressed since the original release. It's much more stable nowadays.on the very rare case a problem arises, usually switching the airplane mode on and off solves it. (I haven't needed to restart the connection daemons anymore). Back in the beginning, you used to need to reboot the phone.
DrYak ( 2018-08-27 18:39:40 +0300 )Regardin the space :
it's sadly a "feature" of how android is setup. Tons of partitions reserved for everything.
On a 32G Xperia, you have ~7.5G for a "recovery" system (basically the base android system in factory state), and a 20G partition for user data (basically, everything you have installed over the base system in a kind of overlay) - so you can "factory reset" the phone simply by erasing the user data partition. All the remaining ~4G are lost to various system partition (drivers and firmware).
Sailfish X uses the "user data" partition to store everything, and the "recovery" partition to store a compressed backup of the factory state. (This time, the "factory reset" menu option on sailfish' recovery telnet works by restoring from the compressed backup).
This sadly means that only 20G out of 32 is available to Xperia.
Now three things :
- The dual SIM, as pointed above by federico , has 64G of flash, so even factoring in all the space lost you have a 'whole' 45 GB left this time.
- Like I just said the Sailfish recovery methods relies on compressed backup. These take only about 650mb. By tweaking the partition scheme (there are tutorials here on TJC), you can claim almost ~7GB of space from the backup to Sailfish X. (Note though that this prevents you from installing Android back. You'd need to restore the exact partition scheme that Android wants before restoring Android back. Also to not touch any other partition !!!)
- The Xperia X support SDHC and SDXC cards, you can safely put a 128GB one (though Sailfish X still uses an oldish kernel with known bugs with some cards. Transcend's seem to work, tough). Out of the box Sailfish can store its camera storage there (though out of the box Sailfish X doesn't have an exFAT license, you'd need to reformat the card to ext4 or f2fs), most of the native application can be pointed to store their data there two (e.g.: downloading all Europe maps for the OSM Scout server).
DrYak ( 2018-08-27 18:43:18 +0300 )If you like to live dangerously, you could even add space from the SD card to the LVM pool and have your "/home" LVM partition spill over the card. But then your phone will stop working properly if the SD card becomes unavailable (e.g.: you accidentally eject the card tray).
(I would advise against it. If you do, at least get a card that does ECC like industrial models or the consumer cards from Transcend, and backup OFTEN)
DrYak ( 2018-08-27 18:47:04 +0300 )