The only solution is to reset the device
I see these funny âgarbageâ-artefacts also occur sometime, but with native Apps and without Android App Support even running.
I have the same problem. On mobile data, most android apps cannot connect to the internet. Only Signal seems to be able to connect. I am also on the KPN network.
Also pinging 8.8.8.8 from the sailfish terminal on mobile data does not seem to work. Only ipv6 seems to work.
Since this update (on my Jolla 2026), some (but not all) android apps wonât have internet (at least in 4G).
I tried disabling / enabling Android Support, activating / deactivating plane modeâŚ
I tried to access Android Settings (by clicking 5 times on android version), every time I try to open Network&Internet settings, the app crashes.
Iâm on Sosh network in France (I see now Iâm not alone to have this issue)
I just had my first real crash on Sailfish after getting this update. I was listening to Spotify via AAS, and everything worked fine for about 10 to 15 minutes. Then, when I went to change track, there was suddenly no audio. The app also complained that there seemed to be some connection issues, yet the track was downloaded and should have been playable offline. I thought maybe the issue was with my Bluetooth earpieces, so I opened the native Qasar Pro app, and when I tried to play music via that app, it crashed. A couple of seconds later, my whole screen went black. A couple more seconds later, I could turn the screen on again and noticed that AAS had been turned off. Music then worked again in native apps.
So for me itâs in France and Sosh, I have same issue, I may have an IPv6 also
It should work if you change it to ipv4.
Sounds a lot like the problem I had, and still have with 5.2.0.18. Perhaps the workaround I found can help you too:
I donât know how I check if Iâm V4 or V6 on mobile connexion. I did switch from âMixteâ (there is âMixteâ,âIPv6â, âIPâ) to âIPâ but it wonât fix the issue
Looks like the network switching issues with wireguard and 4G/5G/Wifi works now. Will keep an eye of it over the next days.
But I have issues with Bluetooth and playing music. connecting my headphones via BT and within 15-30 seconds, I start get crackles and weird stuff happening in the music (and no, I donât listen to noise
) - itâs the same regardless of native apps or android apps. I have not tested with Bluetooth to my car yet. Reconnecting the headphones somehow helps - it plays flawlessly in native and android apps, but then other android appâs like Garmin Connect can not see itâs devices it usually connects to and reports Bluetooth is turned off, so I guess there might be some interference with that SFOS BT Stack/Android Bluetooth integration?!
Itâs not a big thing - as I rarely listens to music on my cellphone⌠unless Iâm in my car.
Your workaround works for me ! I set it to âdualâ, launched dbus-send command and now I have internet on my android apps⌠Thanks, it seems itâs the same issue.
What do you mean by resetting the device in this case? Can you check if sailfish-fpd process is running?
I had to do that dbus-send command, otherwise the whole mobile connection was down after I tried to change something in the sim data acces point settings.
AAS mobile internet still doesnt work, but I could at least restore the mobile data connction for native apps.
No more MMS for me and Android apps canât access to internet anymore.
Is it possible to downgrade ?
![]()
Same issue here (Bouygyes Telecom) : no more MMS and internet is down for Android apps.
MĂŞme problème pour moi (je suis chez Bouygues), plus de MMS et mes apps Android nâont plus accès Ă Internet.
I had same issue with mobile roaming but âtreat mobile data as wifi connectionâ toggle ON in AndroidAppSupport setting solved that one.
At least three reports of unexpected reboots/crashes, bit worrying, keep us posted if this repeats
Second: [Release notes] Finlayson 5.2.0.18 - Jolla Phone first - #54 by J4ZZ
Third: [Release notes] Finlayson 5.2.0.18 - Jolla Phone first - #85 by Apostle
This option is already activate.
Try restarting your phone.
Unfortunately no logs or pstore from those.