Yeah, just realized it’s not there on Xperia 10 II and III. Checking if this a bug or expected…
It’s a bit bigger effort to adapt to all devices as there are differences in adaptation level.
1 Like
Google wallet works??? It doesn’t require some weird safetynet sh*t plus device attestation etc, afaik even graphene with their locked bootloader can’t manage this???
1 Like
Yep, it now boots, I have it open on the phone right now. Can’t add CC-s because device doesn’t meet security requirements, but it’s still good to go for collecting and displaying various loyalty passes, airline tickets, and whatnot.
I can probably retire my web app launcher now, although that worked fairly seamlessly as well.
3 Likes
Not there on the 10 v either …
i really hope that the networking fix comes to 10 III soon, as that feature is literally the only thing i care about in AAS 13. AAS is a pretty bad experience on the 10III currently for daily driving.
I’ve had my share of AAS mobile data malfunctions over the past years releases, but it’s never been this bad, not even when I was roaming in the US.
My main problem was pretty much always AAS OOM-crashing, and then not able to recover ofono-related stuff on AAS restart. You’d always have to also carefully restart ofono before etc. garbage.
Now this recent discovery about apkd-bridge-hw which also seems to setup ofono for AAS makes me think it was at fault all along, but I never got to test it before 5.0.0.73 came along.
Every couple hours feels like something is continously pulling the rug from under ofono and AAS can’t recover well from it. You were in the US, right? Was there any other open 
you posted any logs or previous findings in @teleshoes?
Can’t you use the native BarWal app for those? I’ve yet to come across something I couldn’t add and it loads almost instantly.
1 Like
So where it actually is? As I can’t spot it on Xperia 10 V, either. Not much devices (with AppSupport 13 update) left to choose from, right? Zero, if I count it correctly 
The AAS “treat mobile data as wlan” -option is currently available only on Jolla C2. And that is on purpose, due to some differences in the hardware adaptation layer.
And currently not sure if that will be introduced to other devices in the future or not. After all it is more of a workaroud, and getting the connectivity detection working properly would be the preferred end goal.
8 Likes
the networking issues are not fixed by stopping or restarting apkd-bridge-hw. mobile networking in AAS is much worse since ~5.0.
edit: yes, this is on T-Mobile USA. it was not the case on aliendalvik (4 or 8) on X, XA2, 10II, 10III, definitely up to SFOS 4.4. i dont think it was the case for AAS11 on 10III on SFOS 4.5, either. i think it started somewhere between 4.6 and 5.0.
please please PLEASE bring that networking fix to 10III. AAS is so bad without it, and fixing the ipv6 and routing issues seems like the windmill that jolla will tilt at forever. the wifi fix seems to have just about no drawbacks; unlike android, we can do our own throttling on mobile internet since sailfish users own their devices.
4 Likes
That’s ‘a little bit’ disappointing considering the persistent connectivity problems in AAS on the 10 III and V.
2 Likes
The update installed smoothly upon my 10V. I appreciate the hard work and the great progress.
I do have some information to report. I do not believe it is the same thing as Teleshoes reported on the T-Mobile USA network, but maybe someone more understanding of the technology can connect dots.
I installed the update. I have struggled with the Flight Mode airplane icon in the upper-righthand part of the screen where normally the cellular signal strength indicator is. I know how to get rid of it after a reboot, but I am lazy about that most days.
As a result, I wasn’t immediately aware that the signal strength post-update to 5.0.0.73 was dramatically weaker than prior.
Cellular phone conversations sounded great to me, but consistent reports from other participants was that I sounded like I was underwater.
I ran CellMon and noted that the two RSSI values used to be high percentages, but now the Network Registration number is very low, while Network Monitor remained high.
My son also has a 10V and has not yet updated his phone. With both phones side -by-side, he gets 4/5 bars, I get 1/5 bars. In CellMon, I verified that the upload and download frequencies utilized are the same on both phones.
I have done many things on the 10V to troubleshoot, but I am traveling tomorrow for work and really wanted my phone healthy again. In an act of desperation and to be thorough to report here, I moved my SIM card back to my 10iii.
I took screen snapshots of CellMon where the 10iii is currently located. 72% and 71% while in 5.0.0.72.
I then upgraded it to .73 and that upgrade also went smoothly. However, the same phone, 30 minutes later now shows 10% and 74%.
I noted in the .73 description that in Bug fixes section > oFono > “Network signal strength reporting fixed”
I theorized that perhaps the Network Signal Strength numbers weren’t accurate before, but now they are accurate. I could live with that as an answer, but the call quality has markedly decreased commensurate with the new Network Signal Strength numbers.
I have travelled by automobile for over an hour, passing through multiple cell/mobile towers on expressways (i.e. towers all along the road…pretty much ideal line of sight and proximity) and I never get above one bar of signal strength indicated on the car’s dash as reported via the BlueTooth connection between 10V and the car. Consistently, the other party on the phone call reports the terrible connection, as well.
I hope this helps someone. Cheers.
3 Likes
What is that you call ‘the great progress’ on the 10 V? I must’ve overlooked something. Did it make the camera or fingerprint sensor work, or at least fixed the Bluebinder problem? Or maybe the speakers now play also the right channel rather than twice the left one? Or maybe power consumption dropped from twice the 10 III (which was already very high) to something more usable? Does the microphone now work out of the box, and the headphone jack? Or actually none of the above? Please advice.
2 Likes
Update went well on my Xperia 10 II but Duolingo could not log in anymore (other Android apps are working well or better than before). I tried to reinstall the microG but with no luck. Is it something to do with the fact that I had microG installed during the update?
Edit: Found another app that needs Google play services and doesn’t work anymore.
Update was smooth on Xperia 10 III. One thing I noticed is that Aurora Store installs the update of android apps automatically with the new SFOS version, but not sure if this is related to the AAS layer or Aurora itself. At least I didn’t change anything in Aurora or AAS settings - before the SFOS update I always explicitly needed to tap update and then needed to accept the installation after download was complete. Also not sure if this behaviour is good or bad… But for new installations of apps I still need to confirm the installation after downloading.
Nevertheless with F-Droid nothing changed, I still have to confirm the installation of updates as well as for new apps.
1 Like
Xperia III here - after the update , i get double less mA currents (no sailfish-qmu 23% constant run anymore). kudos!!! battery now lasts twice longer (feeling is it could be even better but now happy user!) cheeeeers!!!
7 Likes
I too got a Xperia 10 II and updated with microG installed, and I haven’t had any issues with signing into Duolingo (or, staying signed in, precisely). The app keeps working for me.
You haven’t by any chance accidentally unactivated “Allow running microG services” from Settings - Android AppSupport? I did once or twice, and immediately had issues with some Android apps.
I concur to that - empirical observation and feeling that battery discharges slower over the last few days.
I can’t quantify - BatteryBuddy shows an instant drain of 120-150mA for longer /more often.