he made a decision and told us the reasons. why should he waste the time to create separated issues ?
… which would be then marked as duplicates 
5 Likes
I have an Xperia 10 II running FREE SFOS, I can’t report any real problems so far. However, I do not have a SIM inserted and also as its the free version, no Android Support.
@triantares, I would certainly make good use of your other voucher if it is still available?
It could be that all these problems are caused by the Android compatibility layer? From what I’ve seen in the forum, those that report these bugs have Android apps installed (such as myself), whereas the ones that say that aren’t experiencing any of these issues tend not to use Android compatibility or have the free version of SFOS. In any case, this would be even more problematic, paying for a product which causes issues to the operating system. Or it might not be related to Android compatibility at all, I’m not that knowledgeable about the inside parts of SFOS.
3 Likes
I’m not angry at all, I’m sorry if I gave that impression and I’m certainly not leaving (if I can find my Pinephone again, that is 
)
I know a few of the solutions and actually found a few myself but typing in ofono related commands in a terminal while driving a car or navigating a ship isn’t an optimal situation in any way.
@diegoc says it exactly as it is. The Xperia10 is my daily phone (as previously my Jollas were) and I need it permanently available for my job.
I would like to compromise as @diegoc does but I cannot, I can’t be talking to my customers and suddenly lose my connection or continually apologize for the bad quality voice connection. Losing a GPS connection while navigating busy intersections is already bad enough.
I’m not reporting bugs as such … I’m explaining why I think these issues should not have been there when offering SFOS for the Xperia10, especially considering that they’re not new.
I’m in fact criticizing the decision to offer SFOS in that fashion and expect (paying) users to jump through these hoops to have a phone that is below par in functionality when compared to other OSes.
- Bad choices can be considered as bugs/issues too and need being named specifically to get seen to.
If I can make your day doing that, feel free to DM me and we’ll see on how to get that done. At least you know beforehand, what you’re getting into. 
2 Likes
Neither of the linked threads were bug reports, but this is a duplicate all the same.
I am perfectly content with Sailfish OS on my Xperia 10 II, it works basically the same as it ever has (i have had all previous Xperias, Jolla C and the first one). I don’t navigate a lot, but from what i have used, it works decent too. My primary headphones are Bluetooth - i have to reconnect them once every other week or so, that’s about it. I fail to care about battery when it is well over one day, just make a habit of recharging - draining the battery fully only hurts it anyway.
This is not to say there isn’t room for improvement- but unless we are concrete about it, how can we expect anything to happen?
You seem to use Xperia 10 II and Xperia 10 interchangeably, which is it?
It still only reads like “i have these bugs, and i don’t like it”, as those other threads, rather than any more substantial reasoning. Nothing about feasibility or frequency either…
Nah. While i use it sparingly, i have it on all the time.
These guess-rumours tends to grow legs, so please either substantiate or provide reasoning.
1 Like
I’m not quite sure what you’re trying to achieve here with your posts.
I’m trying to explain why I think this is hurting SFOS and you’re just on about how this doesn’t affect you or that I’m not concrete enough. Where IMO I am concrete in that I’m not looking to address individual bugs but find the offer damaging to the SFOS reputation, which should never have happened.
If you’d looked at other stuff I’ve posted i.e https://forum.sailfishos.org/t/android-gps-resolution-extremely-slow you could’ve seen that I did share experiences and offer work arounds here on the forums recently … but alas had to conclude it wasn’t to be for my daily use and simply shared that.
If it makes you feel any better: I’m still swiping left\right and pulling up/down on the interface to no avail on LineageOs … until I realize: "Oh yeah there’s these 3 lumpy icons at the bottom of the screen. Gahhh! 
"
Read the topic header!
1 Like
It remains a valid question. The name of the phone is Xperia 10 II, Xperia 10 is an older model with a different adaptation and different known bugs. Blame Sony for picking a very confusing naming scheme for their phones, but if you don’t use Sony’s names, it only ends up being even more confusing.
Edit just to add a few other similar names: the Xperia 10 II is an upgrade to the Xperia 10, which is a completely different device from the Xperia X10 released twelve years ago, which is different from the Xperia X10 Mini, which is different from the Xperia X10 Mini Pro, which again is different from the Xperia Mini Pro. First there was the X10, then the X, then the 10, and then they started iterating on the 10. Though, to be fair, naming products in a confusing way tends to be a problem with many companies, and not just for phones.
2 Likes
@triantares Could you share which Android apps you used on Sailfish?
diegoc raises an important topic which seems to crop up in this kind of “frustration” topics where nothing hardly ever works 
Maybe we do need to check how substansive this issue really is. There must be some popular Android apps that mess up the AppSupport system. We might discover a pattern with certain apps.
I only have Whatsapp, Signal, Firefox and DDG browser and have no issues on my XA2. No MicroG or GPlay or other rubbish either
1 Like
Same here, minus the firefox as I’ve got DDG-browser.
I only have “gpsinfo” from the jolla-store and “k9mail”, “magic-earth” and “pure-maps” as android apps.
I personally doubt this is Android apps related … but more hardware access (proprietary blobs) related.
Like the speakers/micro feedback on the phone is definitely not related to Android in any way.
Again, I’m NOT frustrated in any way as I test and troubleshoot lots of linux related stuff on lots of different hardware … and know what to expect.
My gripe was that IMO this FSOS version for the xperia10 II (dual sim) can barely be called Beta-test level and shouldn’t be sold yet … at least not without warning.
My mistake was in thinking that this would be reliable enough for my daily phone.
2 Likes
If I get it right, the real Android apps are Whatsapp, Signal, DDG browser, K9mail and Magic Earth.
Doesn’t sound too dangerous 
Sorry for calling it a frustration topic, that was incorrect.
It is a post of a malfunctioning phone.
Besides Android apps, there might be other factors, like what release was the device on before flashing and which Sony software revision got flashed. There might be combinations that give more problems than others.
I know it’s not the place nor helpful, but I did the same with my Xperia Plus. I am on MicroG lineageOS version since SFOS 4.0, and I have to say is a better living. Still too many missing feature (to me).
It’s not even that … it’s a post about a failed publicity or marketing strategy.
If it had not been a Jolla-shop sale but i.e a donation request things would’ve been very different, in expectations and liabilities.
Taking into consideration what reports have already been made and continue to come in:
It was simply too early to release this Xperia10 II version as a commercial product. 
Anyway, thank you for trying to help and clearly the forum is a user2user thing but I have no other way to flog the decision-makers at Jolla (beside clamouring for a refund, which I wont) .
3 Likes
As someone not experiencing any of the issues mentioned above I’m actually quite happy they released it. It has been my best SFOS device so far and I had virtually all of them.
8 Likes
I just hope that the reason why 4.4 is taking so long to be released is because they’re making a rock solid, bug free version of SFOS. The issues mentioned above are more and more tempting me to click the ‘Flash Android’ button. Especially because I switched from BB Q10 to Xperia 10 II SFOS because the Blackberry failed me in an important emergency (why would I carry a phone that could leave me stranded when I need communication the most?). The same has happened with SFOS twice, but I still have the hope that the new version will turn a so-far relatively unreliable phone into a phone I can trust. Hope doesn’t last forever, though, and if Jolla is such a small team, they may need help from outside. Maybe opening the project up in the same way Ubuntu did with UTouch could create an actual OPEN alternative to iOS and Android.
3 Likes
Rest assured: there will be new bugs. BUT … I share your hope that the most annoying bugs like loss of mobile connection (both, for voice calls and for data) will be resolved (at least to a large extend)
However, SFOS 4.3 already did resolve many tiny little annoyances I had so I still believe in progress
3 Likes
My first post here after acquiring an Xperia 10 II.
I wouldn’t consider Sailfish as “unusable” on the device, but that depends which features you need for your day to day.
But I have a few frustrations of my own, the most annoying one being my device just will not switch to landscape. It doesn’t work in native Sailfish apps, like camera, video playback or photo gallery and it doesn’t switch in Android apps like VLC playe. even if I force it to in the settings.
The other issues are minor, like the app draw is unresponsive for about 3 seconds when it is pulled up and sometimes stops half way up the screen.
Is there a fix or workaround for the orientation issue at least?
I guess display orientation mode is set to “dynamic”? See settings → display → orientation. Just to exclude the obvious. Because changing orientation works fine on my 10 ii. In the menue you can also fix the orientation either way, i.e. landscape or portrait.
I hope the same. Sometimes hopes come true qickly. After I updated my X 10 II to 4.3.0.15 yesterday for example android apps have access to wifi without problems.
As far as I’m aware orientation is set to “Dynamic”.
But I decided to run the CSDtool tonight and my accelerometer keeps displaying a “Fail” result when doing the test.
Maybe the sensor is poopzenfartzenshitzen (as they say in German…I think) 
Maybe a silly question, but you haven’t locked orientation in the pulley, habe you?