I think you are overstating a lot of things.
Weāll see I suppose. No need to change whatās workingā¦.
I came here first time also do the European perspective 
Glad to hear that others are coming here from similar reasons. I got Xperia 10 III to play with the Sailfish before new phone arrives and I must say it is working exceptionally well. My only problem: especially with that phone model there is quite critical bug where phone loses all audio. This is under investigation what is root cause as not every 10 III has this bug and I am confident Jolla does everything in their power to make sure this doesnāt exist with the new phone. Other than that I have been very happy with the Sailfish itself. So welcome abroad!
2 Likes
Thanks for the confidence boost. Hope I can hold my nerve and not cancel the pre-order. There seems to be a few sizeable issues with the OS in both hardware and software functionality, which I am hoping 5.1 might sort out. I knew the jump would be a challenge, but like a few others who have left, a basic functioning phone is an expected starting point.
I think I have established most of the workarounds for the swap, Iāll see what the next few days on the forum do to solidify my decision. Thanks again 
3 Likes
I am very eagerly waiting the BeaconDB if that would make getting even raff location even inside the buildings or shortening the time needed for location lock. Do you have other sizeable issues in mind?
Only the basics for now, browser, Volte and Bluetooth through App services would be a good start 
Good questions for the next meeting, by the way, FAQ was mentioned above and relevant to my post here. Though for now I have no visibility, so Iām hoping it will deal with some of my concerns. 
1 Like
Well browser was obvious here But very easy to mitigate using preferred browser inside AAS. At least I havenāt yet had any occasions where I couldnāt choose to open link in android browser inside AAS. And it is published that BeaconDB should become available at 5.1 update, so soonish (I think they said something like march-april).
Volte is working already, if I understand it correctly? That basically means that when I call, my phone donāt drop to 2g/3g, right? And luckily the bluetooth for AAS side is also published already! But from that we need to give huge shout-out to the community as this was community finding!
Yes, but it depends on your provider. Thereās an overview of providers that work well and providers that donāt for the Xperia 10 II and III over here, and a similar overview for the C2 over here. Keep in mind that these are just users who decided to share their results, and many results are nearly four years old from a test way back when VoLTE support in Sailfish was first introduced. Probably many more providers work well now.
It isnāt, but itās coming.
Yes and no, the community came up with a useful hack, but Jolla took a different approach to make it work the way people would expect it to. But maybe the community hack pushed Jolla to prioritise their work on Bluetooth support for Android applications.
Sorry maybe my wording wasnāt perfect, meant exactly that is is published to become available soonish. Maybe āannouncedā would have been better english word.
I think this happened, but of course super glad that Jolla started to work with that and makes it easily available for wide masses!
I think Iāve dragged us off topic here sorry! But thanks to you and @CLMA31 I have some clarity.
My understanding from forum searches was pretty much as you have stated. I was going to query @CLMA31 as to when a work around was classed as a fix or whether I had missed something somewhere. Which was partly the reason for this topic and my argument to centralise J2 activity, but it was just a thought .
Thanks again both.
1 Like