I’ve only had a complaint about it once. And back in the day, surely no phones had any echo cancellation and worked just fine, so i suppose it is perhaps not critical.
It used to be that speakerphone was always terrible… apart from the odd emergency conference phone, i only keep seeing terrible uses of it (like people walking around town etc).
It’s annoying to be forced to have speaker on and even then I get complaints. It doesn’t help much when people are saying ‘I don’t have this problem’. And I know I am not the only one with this. Sometimes when I have enough of it, I charge the N9 so I can use that for making calls over 2G/3G.
Yes, it is annoying. And yes, I do get complaints from people about the echo. A partial solution is to keep call volume <= 70% which limits echo to much less disturbing levels, but at the same time it obviously makes the earpiece volume lower than sometimes needed to hear the other party comfortably.
I’ve been using mobile phones since 1997 or so and I don’t remember that anyone ever complained about echo in any of them, except now the 10 III that numerous people do complain about this problem to me. So there’s clearly something unique to that effect that even old simple mobile phones didn’t have.
Today is that kind of day for me. I’m almost having enough of all the bugs and problems that the 10 III (with SFOS) is tossing at me.
Edit: Oh, I forgot. That freaking silence (no tone of any kind) when calling someone via VoLTE. This single thing alone makes me want to throw that damn thing against the nearest wall, multiple times a day.
Sorry for my late replay again 
It took some time, but i got carddav going from SailfishOS to my radicale server. For now i made an ugly patch to simply disable the redirects for the /.well-known/ directory on the server side. On the client side this 404 response is handled cleanly and a sync is done using the information available from the configuration.
For me this means that i think i finally have everything ready to switch to my X10iii 
, now i just hope there are no more nasty surprises 
.
@Kea thanks for sharing your experiences. It’s good to know they are (or can be) there, i’ll see if it impacts me when i can actually start using my X10iii.
Well … carddav had enough nasty surprises left . I had a working sync from my FP2 to my server and expected the X10iii to do the same. The backup/restore restored the account config, but after entering the password i got an error. I tweaked the server responses a bit more, and at some point that worked. The account was active but not synced yet.
When i started the sync the GUI asked for a wifi network to connect to (even though it already was connected to the right wifi network) and no request to the server is done.
I this point i decided to abandon carddav and manually transferred the contacts that were unique to the carddav address book.
I’m using rsync to sync my music collection from my server to my phone. On my FP2 the destination was the uSD card which was automatically indexed. On the X10iii i doni’t have that option since i need 2 SIM’s. I created a directory /home/defauluser/Music_rsync (/home/defaultuser/Music is used for music which isn’t rsync’ed) and the sync did it’s thing, but it doesn’t get indexed and doesn’t show up in the media player. What would be the best way to fix this?
Have to say the constant browser crashing is getting very tedious.
Hope to see this high up on the priority list for the next point release…
Yes. I actually never used the SF Browser. But I will happily try it once it is usable.
in the four years i have been using SFOS i have always used firefox, but since i finally got my 10iii working a few months back i have used the SFOS browser.
it was okay initially, but 4.5.18 seems to have made it extremely crash happy.
The I’ll be waiting for SFOS 5.0
Thank you.
I’ve fixed my rsync issue by moving files to /home/defaultuser/Documents/Music_rsync, this seems to be indexed and works as expected.
I just started experimenting with my VPN and it seems to behave different from how i’m used to with my FP2. My VPN is reachable over the internet with an IPv4 address and provides IPv4 and IPv6 access to my own network. IPv4 works(but not as expected) but IPv6 doesn’t work at all. This means IPv6 is still routed to the internet instead of to my VPN, which breaks all dual stack capable applications (which is most of them nowadays ).
IPv4 behaves strange in an other way: After setting up the VPN the default gateway is changed to the VPN, which is good. In order to keep the VPN itself working you need to route your VPN peer’s address to your internet connection, because otherwise this also gets routed into your VPN which obviously does not work. Problem is, this doesn’t happen. It also doesn’t configure the VPN provided DNS server. I worked around these with a script but of course that isn’t ideal.
Does someone know a fix for the complete sound system crash, that happens randomly (and silently) and can be only fixed with a reboot? I usually only detect it when someone calls and there is no sound. Very annoying.
Well you can do systemctl stop pulseaudio and then systemctl start pulsaudio, but that also doesn’t work sometimes and i have the feeling that if you tune the minfree values it happens less often. In /vendor/etc/init/init.lena.rc you edit the corresponding line to: write /sys/module/lowmemorykiller/parameters/minfree “65536,73728,90112,
131072,196608”
Okay, thanks, I’ll try.
I installed the app qcommand and put the commands separated by && in to be able to execute them faster
Doesn’t work. Says pulseaudio can’t be started/stopped manually, only by a component.
Also doesn’t help much.
pulseaudio works in userspace.
systemctl --user stop pulseaudio
If that’s the case then is that mean that pulseaudio is leaking memory or something else and low memory killer is just doing it’s job? Well if PA is not leaking, then it should be protected by lowmemkiller from being killer, and something else should be killed. But eve if it’s that case, then a workaround would be that lowmemkiller would just reload pulseaudio instead of killing it.
But these are just workarounds tbh.
I installed SailfishOS last week on an Xperia iii - I checked it with a minimal install and was pleasantly surprised to see ~ 33% battery after 2 days, so I guess 2.5 to 3 days.
This is about the same as my previous Sailfish phone, a Gemini X27 PDA, which I am replacing because it does not support 4G and my MSP (Vodafone UK) is actively shutting down 3G.
The only problem that I have found is that I cannot send SMS when the phone 4G (beta) is enabled - making and receiving calls and receiving SMS are fine.
My workaround is to disable 4G, send the SMS and enable 4G again.
The GPS works and I am running Pure Maps with the HERE map provider - I have not used it in anger.
The Android support is a nice to have as I now have microG, Kindle and the Vodafone app installed.
By the way, Sailfish was installed over the Android 11 that the phone came with, as there were no updates available over the air - it was not Android AOSP ( release number ended in .9? with tag release-keys?).
I have found no problems with doing that.