As you installed over the original Android: do you also have the problems with echo cancellation at high volume or is that the solution to the problem?
I basically did the same, phone came with stock android (11 according to specs, i didn’t verify) and installed SFOS. I do have the echo issue.
@Sturton what problem did you have with sending the SMS? In my case the GUI kept displaying “Sending …” while in reality the SMS has been delivered.
I had the same “Sending …” experience, but the message was never received.
Sending MSP Vodafone UK, receiving MSP Three - turning off 4G Beta meant that the sent message was received.
@pa4wdh : I hadn’t noticed the echo until I turned up the volume, but it is there, but not enough to prevent me understanding the conversation.
I usually use the phone on speaker and that seemed better.
I agree that the echo isn’t so bad that it disturbs phone calls, but it’s noticeable.
The SMS was send over 4G in my case, and if i recall correctly the messages application immediately crashed when i pressed the send button. When i re-started the messages application i saw the status “Sending …”. The recipient of the SMS called me and that was my confirmation the message has actually been send 
.
Even though I’m fairly happy with my X10iii i wouldn’t expect such basic issues in a supported software release on a supported device.
This happened on my Xperia 10 III after an unnecessarily long uptime (~25 days). I just didn’t have a particular reason to reboot… It didn’t occur to me to restart Pulseaudio, so i guess that would’ve done the trick. But i rebooted, and i’m waiting for the next time to it to happen, so i can get a better picture what might trigger it.
Jolla does recommend to reboot Sailfish-phones once a week to avoid problems. Maybe i should too, but who knows, that could’ve happen within a week anyway.
I can only wish for 25 days uptime. Sound breaks for me sometimes 2-3 times a day (restarting pulseaudio sometimes works, but not nearly every time) and in addition Bluetooth stops enabling and have to restart again for it.
I only loose the sound after GPS was enabled. Bluetooth is always broken after a reboot. My workaround is to go to settings, enable bluetooth go back to settings and restart bluetooth from Sailfish Utilities and it is working.
1 Like
Jolla does recommend to reboot Sailfish-phones once a week to avoid problems. Maybe i should too, but who knows, that could’ve happen within a week anyway.
This can be observed on Android-Smartphones im my Family too, at least a Smartphone is a mobile Computer with a grown OS which have the same Problems like on Desktop. So reboot once a week is good.
1 Like
I can only wish for 25 days uptime.
Maybe it helps to flash the latest Sailfish-Version to it, some of my Friend have helped this on similar Problems.
1 Like
Thanks for the BT tip, might help. Mine is usually working after restart, but sometimes it isn’t. I’ll try the Sailfish Utilities.
I’m always on latest.
Just out of interest, do you have a link to Jollas reboot advice?
I was about to ask the very same question. I’ve never seen Jolla stating anything like that.
I did. Not really sure but I think it was @jovirkku stating it in a post.
Anyway, it is common sense. All handheld/desktop OS’s needs reboot now and then.
Well… Uptimes of my Blackberry Passport were literally months. There were absolutely no reasons to reboot it unless there was an OS update or something like that. It was a rock solid OS.
Heck, even my Windows 7 (yeah, I’m still on 7) laptop gets a reboot once every couple of months, usually when Norton asks for it due to some update that needs reboot.
So a recommendation to reboot an OS weekly is quite exceptional to me.
2 Likes
I’ve also never heard of the requirement of a periodic reboot. I’ve been using sailfish devices since the first jolla phone (2014?) and the only time they got a reboot was when i was too late to charge the battery .
I’ve been using my X10iii for 1,5 week now, and i’d like to share some experiences:
The good:
- I like the (lack) of thickness, it’s much thinner than my FP2 and that’s very noticeable with carrying it with me
- I sometimes use OSM Scout with offline maps, the performance of map rendering is way better than my FP2
- The audio output of the 3.5mm jack is higher than my FP2, high enough to use it with the line-in of my car stereo, so i can use my phone to play music
- Calender reminders are working as expected
- It does IPv6 on mobile data connections
The bad:
- I’ve had issues with phone calls and SMS messages (see previous posts)
- Once i had no keypad on the lock screen, giving me no way to unlock it
The battery life has been a mixed experience for me. I had one day with high use (1,5 hours of navigation with OSM Scout, 1,5 hour of mp3 playback) and with that use the battery lasted 2 days, which i think is quite good. On the other hand, the days after that i barely used the phone and it also lasted 2 days, which is not so good.
For now i’ve set the mobile network to “2G only”, this had a huge effect: Phone calls and SMS work as expected and battery life has almost doubled. Since i don’t use data on a regular basis i have no requirement for higher speed data connections. I also noticed the same thing with my FP2: My reason to buy a new phone was because it’s battery barely lasted a day, but now it’s on 2G only it even lasts 5 or 6 days. Actually, looking back to when the problems with my FP2 started, that’s when 3G was shut down (so only 2G and 4G remain). I’m not sure if it’s related, but the timing suggests it might be.
Reboots of SFOS tend to fix some things while at the same time often make some other things (which worked fine prior to reboot) work worse / misbehave.
For example, let’s say that I need to reboot the phone in order to fix the sudden “total lack of audio” issue or contact pictures no longer showing up in background during calls. OK, the reboot does indeed fix it. But at the same time, media player and the Gallery application, which weren’t causing problems before reboot, now tend to freeze after every couple of media file playbacks. So I reboot again. Media playback starts working fine again, but now web browser crashes noticebaly more often than previously, or the fingerprint sensor freezes / becomes unresponsive much more often. And so on.
I don’t know what it depends on, but it is so. That’s why, if most things seem to work fine, I try to avoid rebooting the device for as long as I can.
2 Likes
Yes.
See 3 (How to keep your Sailfish device in good shape), point 4:
Restart the device every now and then (for instance, once a week). Some unnecessary data may pile up in the main memory (RAM) over time. A reboot removes it.
Now you have.
Exactly.
Also reading the manual helps. 
2 Likes
For me this is an excuse for bad software and not common sense. I have my phone and my laptop running forcweeks without a reboot and didn’t experience problems which require a reboot.
This advice sounds like it’s coming from IT Crowds tech support or from an old Microsoft Windows forum…
2 Likes
Yes, device that was used as sound recorder. You can probably get years of uptime if you just leave the phone plugged in to a charger and leave it alone. Even in maemo times with proper linux drivers and hundreds of devs at nokia N900 would slow down with normal (active) usage after few days, just search tmo forums, people were writing scripts to restart problematic services during the night to keep the uptime going
2 Likes