Vivaldi freezing is also fixed! Wohoo!
After a few days of use in 10 II (Dual SIM) I would say that 4.1 was operating more smoothly. Battery life is significantly reduced, loosing 40% overnight and phone barely lasts 24hrs (before it would easily survive 2 days). The text prediction as other mentioned takes for ever and freezes the phone once you select a word from the proposed ones. When on WiFi most of the Android apps think that there’s no internet connection. When walking outside the house, the phone keeps looking for the WiFi instead of switching to mobile data.
After flashing I had to do several reboots to get things working and at least once the phone was stuck with green LED on and no way to light up the screen. Exchange didn’t sync until after serveral reboots.
1 Like
Hey guys,
I just confim the following aspects for Sony XA2:
→ Not for Sony XA2: Smoother experience with 4.2 and no battery drain as decribed above.
→ Yes, this problems occurs with my XA2 too.
→ Yes, so annoying! Also in my XA2!
→ No, installation went perfect. Only problem: download status bar got stuck after ~10%. The progress carried on in the background.
1 Like
Tried all steps, no updates found. But seemes problem was fixed, at least from last night till this moment everything is fine. Maybe it was somehow related with post_sfos-upgrade command.
I updated my X10II to 4.2, but the gui method failed repeatedly, the download didn’t even start. I ended up installing sfos-upgrade and using it. The download went ok, but RPM script segfaulted on two packages: sailfish-ca and popt, so I had to try it three times. In the end everyting went fine and device works smoothly 
Some notices:
- Android apps feel more responsive
- Android apps frames get rendered in correct order
- Vivaldi (by extension Chrome, Brave et. al.) don’t crash anymore after 30-ish seconds
- Predictive text works fine 98% of the time
- Lock screen media controls: prev/next/pause works, play (aka unpause) doesn’t, at least not with Deezer. Please see my commen of this answer: Status of allowed libraries in Harbour - together.jolla.com
- bluetooth keyboard still doesn’t work properly on android apps. layout is always english, shift key does nothing. SFOS side works fine.
- Bluetooth audio control buttons work for next/prev/pause, but not for play. See comment above. I’ll open a new bug report for this. Edit: Logitech keyboard media buttons don’t work, but JBL headphone buttons still work as before. No issue after all!
- Bluetooth button on top menu desyncs on reboot (Bluetooth is on, button says it’s off. I think this is a known issue… Existed in 4.1 too.)
- Triple camera works great!
- Strikethrough over SMS bubbles on XA2 Ultra is still there
- Edit: JBL bt headset works, except for calls. This was the case for SFOS 4.1, too. I’ll test it with XA2 Ultra on 4.2, too.
Overall it’s a great update, and no immediate regression popped up (except Whisperfish, and WLAN is untested, Bluetooth devices largely untested). Thanks again for great work!
1 Like
It’s still not possible to tick the checkbox in German trains (DB, WIFIonICE) captive portal.
EDIT: this was with 4.2.0.19. Seems to be fixed in 4.2.0.21 as reported by @jollajo
2 Likes
Hello I would welcome any advice before updating my XA2. Sailfish recommends removing the following packages before updating: harbour-storeman and commhistory-daemon
Removing harbour storeman would be no problem. However I cant remove commhistory daemon. When using pkcon remove commhistory-daemon the terminal replies: fatal error this command leads to system crash.
What should I do? Some previous updates already broke my system - I really do not have time to setup my whole system again.
I have found a new bug (XA2 plus). After having received an MMS, no WLAN connection in 4g for Android apps. Connection OK after using “restart network connections” utility.
Well, the source of information I was using did not clearly state any exceptions. The serial number seems to appear on Xperia X and some business customer products only, not on XA2, 10 or 10II. After learning this, I decided to remove the mention of the serial number from the notes.
3 Likes
Thanks for reporting. We should take another look at it to see what is causing the issue in this case.
1 Like
On an Xperia 10 II I experienced several cases of Battery drain with 4.2. that didn’t happen with 4.1. Today it was ofonod that ran at 100% CPU for hours. After an reboot everything is back to normal for now.
2 Likes
I am also experiencing frequent battery drain, ofonod eats up a core. Restarting data using Sailfish Utilities fixes it, until it occurs again.
1 Like
I just noticed the upcoming 4.2.0.21 update! Thank you so much! This in particular caught my eye:
- Routing phone call voice to Bluetooth headsets improved, also by being less pedantic about the ordering of speech codecs
I knew it would be something like this, because I had some Bluetooth devices that worked and others that didn’t but they would all expose the same capabilities! Can’t wait to test my JBL with it!
3 Likes
In the meantime users with cars BT systems that requires PIN to pair cannot make BT calls in car 
I’m early access subscriber and I don’t get the new update 4.2.0.21 
you won’t get it before the 13th ;-p
I don’t know what day is today…
2 Likes
I have a Ford Audio system, made by Sony, which requires a PIN code. Pairing goes fine, so does music playback. I used to be able to make calls before 4.2, but no more 
There’s no audio from the car speakers. That should be fixed in the upcoming 4.2.0.21 update. (This also applies to JBL TUNE750BTNC, which doesn’t have a PIN pairing.)
Or is your issue different?
My update from 4.1 to 4.2 failed with Sony Xperia 10 II 128GB Dual SIM with 1 SIM installed, no microSD card. I have a quite fresh install of Sailfish OS, only native and Android apps from stores. During the update process the phone rebooted and the progress bar got stuck at about 40% for 5h+. I powered the phone off and restarted it. Now it shows version 4.2.0.19 even though the update was not completely successful. I currently encounter problems with some Android apps (Signal is not opening chats, only the overview, WhatsApp is not able to access the camera) and also triple camera does not work. Have not tested much.
EDIT: After doing this in the terminal, everything seems to work fine.
$ devel-su
# ssu release 4.2.0.19
# version --dup
1 Like
I can’t seem to find the thread, but i guess here is a good place too:
For the first time in quite a long time (years) i’m having problems with Android apps’ network connectivity when switching between wifi and cellular.
7 Likes