Thanks for sharing this @jabgoe. Of course, it’s a shame to hear that, but this is why we flagged the issue up, and we certainly hope it can be fixed so that you (and anyone else in this position) can then go ahead and make the upgrade.
3 Likes
@flypig well I’m worried about comments from @sledges:
Due to above reading [this comment](https://github.com/sonyxperiadev/bug_tracker/issues/684#issuecomment-809408332) it seems that it won't be possible to fix this for phone calls..
This issue has been fixed for loudspeaker but for the builtin… well could someone confirm this? Cause if this is for sure then I think 10 III is a nogo for a lot of people and could be that it will be pointless to even try to do anything with that phone and waste resources if this is not fixable.
3 Likes
The foundation for future development cant come from other peoples HW no matter how “open” this is. The issue above -and other- exemplify that.
At some point jolla needs to man up (read put money) and decide on a HW design that can be used both for phones and their automotive ventures. Needs to be as open as possible, replaceable, available, and not necessarily bleeding edge. After all working old > new and buggy.
HW is a problem for jolla since the beginning. For whatever reason they thought HW is the easy part. Well as it was proven it isn’t. You can fix SW but you can never fix HW if you don’t “own” it.
2 Likes
Is it possible to take the drivers from the commercial firmware, rather than the AOSP branch?
Every user of a 10 III is a paid up, licensed user of those drivers.
I don’t know the answer I’m afraid, but potentially not. For example, see here under “Risks”
1 Like
@flypig I dare to suggest that this is another reason to extend the voucher expiry date of the “buy one get one free promotion” to give us more time to decide which phone model to choose. I know this echo issue from a phone with Lineage OS that I set up recently for a relative of mine, and it is almost unbearable. If this thing turns out impossible to fix, the 10 III will be a no-go and the 10 II will become the only viable choice.
1 Like
@flypig yes, very nice you flagged that. i’d be much more unhappy if i had had to find this error myself … 
please keep up the information until this error is resolved …
considering the “known issues” section I’d say that Xperia 10 is the only vailable choice as it has the least amount of “known issues”.
Well I think that even if Jolla would OEM the handset there would be Qualcomm SoC blobs that could rise issues too where OEM has no clue how to fix them even if hardware is owned by vendor.
2 Likes
Thank you Flypig. Yes I have seen the link to the blog and I understand the choice and agree with it. Of course we hope it can be fixed after some time .
I gave My XA2, updated to Vanha Rauma, to my husband. He now has a similar problem, but reversed: when he makes a call, he hears the echo himself.
I don’t know if it has anything to do with it: he used a Gigaset with e-foundation for a while and he had the same problem: other people heard echos… Could it be an android thing? Anyway he’s back on Sailfish and it works for him.
1 Like
So what I get here is that stock firmware and AOSP use the the same acdb (audio calibration database) IDs that fixed former issues with echo cancellation on previous models where for some reason AOSP used different IDs.
For the Xperia 10 III however those IDs are equal so both firmwares use the same audio sinks provided by the SoC. Does this mean that in older devices (eg. 10 II) the SoC was actively supressing the callees echo but on 10 III some proprietary echo filter by Sony does the job instead (which is included in stock firmware but excluded from AOSP?).
Sorry, I am now reading that devices on lineageOS have the same problem like that one from the e-foundation. How do they solve it?
I wished a Jolla 2 was coming!
1 Like
But instead it has a tiny battery.
Anyway, while the aforementioned licence vouchers expire in just a few weeks, there’s clearly no intention of Jolla to extend them, meaning that we’re forced to make the following blind choice:
-
either get the X10 III with its echo issue that no one can tell if it’s fixable. I know this echo problem from Lineage OS and I can’t imagine having it on a newly purchased phone for 400 Euros that I will be using for important calls
-
or get the X10 II that doesn’t suffer from the echo issue, but still doesn’t have VoLTE and no one can tell if it is ever going to be supported on that model, meaning that if I choose the X10 II in order to avoid the possibly unfixable echo issue, I may soon end up with a device not really usable on any mobile network. I.e. 200 Euros (and the licence) just wasted.
A truly marvellous choice. And that while extending the voucher validity period wouldn’t impose ABSOLUTELY ANY BURDEN to Jolla, the only effect of it being giving us a few more months to consciously decide which phone model to get (and thus which phone model to assign the licence to) while they possibly manage to fix the echo issue or bring VoLTE to X10 II.
But no, they just won’t do it. Very disappointing.
1 Like
I believe Jolla have akready said they’ll implement VoLTE on the 10 II next once they have got it working on the 10 III. As for the echo issue, I’ve been using SFOS on my new 10 III for just over a week now and have made dozens of calls (the old fashioned way, I haven’t enabled VoLTE) and nobody has mentioned it. I’ve even called my own 10 III from another phone and didn’t notice it myself. I wonder if this issue depends on the exact Android version present before flashing? I upgraded to the very last Android 11 version before 12 and all seems fine to me.
4 Likes
About this echo cancellation issue… wouldn’t it only/mainly be relevant when you are using the speakerphone (as opposed to the earpiece)? Given that it is suuuper obnoxious to your environment and the person you are calling anyway, it basically not a real-world use-case outside that one meeting where the other equipment didn’t work.
Nah, it’s the standard use echo not being cancelled, cancellation works for speakerphone usage weirdly enough but not for basic usage
They actually said that they
which to me sounds too vague to rely on, as “aim” sounds more like an intention than any solid timeframe, and such “further testing” may turn into months or quarters, as it already happened in the past.
Nevermind, I don’t want to start any debate on this, I just can’t comprehend why they are so unwilling to make such small and friendly gestures to their faithful customers like extending the voucher expiry date so that one could make a fully conscious and risk-free choice a month or two later, being fully aware of if either the echo issue can be fixed on the X10 III or if/when VoLTE will come to the X10 II.
Recently I salvaged two phones by installing Lineage OS 18.1 on them and giving the phones to two of my relatives (one of them being my mother whose previous phone just broke). Both those phones have the echo issue, but each of them in a different way. One has the echo only in speakerphone mode (but the echo is totally unbearable, the caller just can’t stand it, mostly hearing himself, so the speakerphone mode is totally unusable but the normal mode is fully OK), and the other one has the echo problem while normally using the earpiece, and it is slightly less troublesome. None of those phones had any echo issues with their original stock Android firmwares, it is Lineage OS (i.e. AOSP) what introduced that problem. On the XDA forums, I’ve seen that there are some attempts to cancel the echo in those ROMs, but it’s mainly some tricks with side effects, like modifying the overall volume or mic sensitivity, or something like that.
Anyway, while such an issue is kind of bearable on old salvaged phones having been given new life with Lineage OS and provided to some elderly people whose expectations from a smartphone are quite basic, if the echo cancellation issue on the to be newly bought €400+ X10 III is anywhere near that of Lineage OS, for me it is a deal breaker.
Hence, I would really like to be given possibility of making a conscious choice, knowing if either the echo is fixable on the X10 III or if/when VoLTE will come to the X10 II.
So please Jolla, kindly extend my voucher’s expiration date by the time you are able to provide this basic information.
Just to confirm @Steve_Everett ’s experience, I have also used the 10iii (with VoLTE enabled) for two weeks now and I haven’t had this echo cancellation problem. YMMV, of course, but more data points may be helpful.
Well, I think Jolla’s timescales for delivery of features, releases, etc have always been known to be, how shall we say, somewhat ‘elastic’ - and I guess because they’ve never done a VoLTE implementation on SFOS before these timescales might be more ‘elastic’ than previous ones. Software development never tends to be plain sailing at the best of times. However, they do always seem to get there in the end so, personally, I’m sure we will get VoLTE on the Xperia 10 II at some point when it’s ready. Personally I am still hopeful that we might also get it on the XA2 as well (I have two of those phones as well as a new 10 III) but since nothing has been said about this model that may well be doubtful. Other threads have already discussed this point.
As for free promotions on products, these are always going to be time limited no matter which company is offering them. That’s just the nature of the beast. No company is going to continue to offer a free promotion for an indeterminate period of time just because a feature (VoLTE on 10 II) is not yet available on that product that one or more users are demanding. Unless there is some form of contractual commitment on Jolla’s part with regard to the ongoing provision of free licenses whilst certain functionality on certain models remains to be delivered (which is highly unlikely) then I think you’re out of luck.
And besides, whilst your hot button may be VoLTE, for others it may be different. My key missing requirement at the moment is modern two factor authentication for MS Exchange accounts as my work clients insist on this now. At present I cannot access some work email accounts on my Sailfish phone, so I have to dual carry which is a real ‘pocket pain’. We can’t all demand ongoing free licence provision until these features are delivered, can we?
Personally I’ve found the X10 III a good upgrade over the XA2 - it’s faster, the OLED screen is a huge improvement and SFOS runs much faster on it. I had thought the narrow form factor would make reading more difficult over the wider XA2, but it doesn’t as the screen resolution is much clearer and the text better defined. GPS also actually works on this model without fuss (Yay !! 
) which it never did on the XA2 to the extent it was usable in everyday life. I don’t do patches and I haven’t enabled VoLTE whilst its still in Beta - I try and keep things as stock as possible to minimise issues. The only new (for me) annoying issue I’ve found so far is apps being killed whilst in use. This is mainly the web browser (regularly) but does affect other apps (irregularly) as well - this never happened to me on the XA2. It still suffers from some of the long standing bugs seemingly affecting all SFOS phones (e.g. Android apps losing network connectivity, email sync failures, cloud services (Dropbox, Onedrive) not working, etc, etc), but overall I’m pleased I did upgrade to the X10 III. It’s the closest implementation so far towards being acceptable as a daily driver for me.
3 Likes
Oh, and as I have mentioned in another thread, the Android image on the X10 III seemingly no longer allows the use of my banking app (Santander) whereas it does on the XA2 with the same 4.4.0.64 release … strange.