Actually I was wrong about mobile data - it is working, but apps can’t detect it (which results in Firefox refusing to load pages, but others do work).
There is another problem - at some point AAS stops starting at all (usually after several days) and only a phone restart fixes it. Didn’t investigate that yet.
So things not working are:
mobile data detection
camera can’t encode photos and videos to save them
playing videos (this is probably the same issue as the previous)
the AAS crash at some point
I have a hunch that the coming upgrade of AAS to Android 13 might fix some issues, since this port is based on 13.
You use the AAS of 10IV/V? Than it should be already AAS based on Android 13.
The crash of AAS happens quite a lot on my 10ii also and thats the reason why I didn’t update my C2 to last update. I think that problem has nothing to do with the port.
The problem you describe with the not-detection of the mobile connection was there, when the C2 was launched, too. Now they fixed it - but yes, that doesnt help with the connection for the 5IV/1IV.
@bundyo Do you have AAS configured to automatically start with the system? If so, could you please test it with that option disabled, i.e. reboot the device and only then manually start AAS with WiFi turned off and mobile data enabled beforehand? Then, when AAS is launched, give it some time, like 1 minute or so, to “settle down”, and only then launch Firefox or some other Android app to test if it sees mobile data? I would be very grateful if you could test it this way on the 1 IV or 5 IV.
The 10 V AAS tends to not discover mobile data if it is launched at some too early stage, and sometimes also if WiFi is turned on simultaneously, or if an Android app requesting web access is launched too quickly after the AAS was started… Thanks a lot in advance!
Do you give it some time to ‘settle’ after it starts? Both on 10 V and 10 III if I try to use Internet too quickly after starting AAS (e.g. try to open a website in Firefox without waiting some 20-30 seconds) then quite often it doesn’t see mobile data at all and only device restart fixes it…
I’m asking those questions because I’m actually hesitating whether not to cancel the purchase of the 1 IV before delivery (and payment upon receipt), as it seems to be affected with too many problems for such an expensive device… On the other hand, there’s nothing else to choose for SFOS that wouldn’t have issues…
It works well enough (got AAS from my 10 V) except the camera does not (which it also doesn’t on the 10 V so maybe that is related and just an AAS issue).
If the camera worked in AAS so I could scan QRs and pay with my banking app I would use this phone as my daily driver instead of the 10 III, it is so very nice besides that since the 10 III is getting really slow¹.
Rinigus really did a solid thing by building on LineageOS and Jolla should just make AAS officially available for ports that have shown to work well with it. Then the community can pick up some of the work and make it better.
¹) for Android apps since they’re getting bigger and slower
But how about mobile data? Does it work in AAS on the 1 IV? Can you use Internet in Android apps (e.g. Firefox) via your mobile network’s Internet connection, or only via WiFi? @bundyo wrote earlier that only WiFi works for him in AAS because it doesn’t detect mobile data connection…..
Rinigus did a marvellous job indeed, proving that there is a solid and stable base for SFOS and it doesn’t have to be dependent on those freaking buggy Sony blobs. We all should think about rewarding him for his continued support (first Tama and now this).
Anyway, I don’t really understand why Jolla, at least as a secondary option, keeps ignoring LOS as such a solid base for SFOS. I’m not sure if I follow that story that legal reasons prevent distribution of such blobs because Jolla doesn’t (re-)distribute (or in any other way directly provide/include/whatever) Sony blobs, either. They only post a link to Sony developer portal where those blobs are offered and where the user has to accept the EULA himself, and it is up to the user to find, download, extract and flash those blobs, entirely on his own. So why can’t they make a SFOS version for which it is entirely up to the user and his very own responsibility to find, download, extract, flash (and whatever else) LOS blobs is entirely beyond me.
Uh, that’s bad… Since Rinigus doesn’t use AAS, chances are poor that it might get fixed…
Have you checked in Android settings whether Network & Internet / Mobile network / Mobile data transmission switch is enabled? If I switch it off on 10 III or V, AAS stops seeing mobile data…
(to open full Android settings tap on Android version five times on SFOS Settings / Android AppSupport page)
On a different note, it looks that Waydroid has recently been made working on LOS 21, so maybe at least that would soon allow using Android apps with mobile data… Maybe @vlagged will be able to make it work on Nagara…?
… and that’s exactly what I don’t understand, because Jolla doesn’t (re-)distribute those blobs in any way. They only tell the user to go to Sony developer portal and download them himself, at the user’s own responsibility etc. (prior to download the user must accept Sony’s EULA, and so on). So I fail to comprehend why they couldn’t tell the user to grab the same way some LOS base instead. They wouldn’t need to distribute it or take any other responsibility for it, either.
That’s exactly what I was talking about. The base, the blobs. I was replying to someone saying that Jolla can’t use LOS base rather than Sony AOSP for legal reasons not allowing them to distribute it. IMO, Jolla does not distribute it in any way. With Sony blobs, they’re NOT part of SFOS distribution or flashable image, it is you, the user, who needs to go yourself to Sony website, accept Sony EULA, download them, and flash them. So the legal relationship when it comes to the Android base and Sony blobsis between you and Sony. Therefore, I can’t see any legal involvement of Jolla in the process of you downloading and flashing to your own phone those (or any other if you would wish so) blobs (or whole Android base, eg. via Xperia Companion) yourself. So why would it be any different with LOS as base and LOS blobs, at least with the models with the already existing, ready to use and download officially released LOS ports (that Jolla wouldn’t have to get in any way involved into building them themselves), is beyond me. Jolla wouldn’t distribute them in any way, either. Tough I might be wrong, because I am not a lawyer, just some common sense reasoning.
Are Sony SW binaries working and legally allowed for LOS? If not, then Jolla should rewrite their code to target LOS instead, which is a rather big change. I guess if you browse the community meeting logs, you may find an answer - it has been discussed on more than one occasion.
