I understand your understanding of this. But C2 doesn’t have the same VoLTE config. Maybe even none if there are no VoLTE packages. That’s written in the Release Notes. We all hope that’ll change soon.
@ hschmitt: I do appreciate your findings!
If I’m wrong (which I hope I am) I’m sorry for snarky comment.
So when I get it niw right, the C2 has a complete other mobile network stack as the prior SFOs versions?
I’m not an expert but from what I read here is that VoLTE part is very different. So they might changed other parts (even config) as well.
I read it, but I wanted to share my findings. And I guess I could fix it if I knew the files - and by the way it is not about VoLTE. VoLTE is the phoning part.
Oh, so I was just smartassing then as himmi let me know (thx for that btw). Harry, I’m really sorry!
Note to myself: I should not reply in the bad mood.
With your knowledge you should be in C2 VoLTE testing group.
C2 does not support mobile data in AppSupport yet. Therefore, you cannot fix it.
Wifi is also not working with Andoid apps after wifi-network change. I have to disable>enable Wifi and then stop>start AppSupport.
Actually mobile data works e.g. WhatsApp works without a problem. It is just that AppSupport does not find a matching APN and therefore signals “No mobile data connection”. I thought there is a github repo to contribute. I found https://github.com/sailfishos-mirror/mobile-broadband-provider-info, but that is for the sailfishos part I guess.
I find it highly unlikely that AAS has to “find its own APN config”.
You should trust @jovirkku or provide reasoning - now you did neither and it’s just noise.
For me, all the ‘please be quiet, this can’t work’ feel much more like noise than people sharing actual technical details of the problem
I’m asking them to prove it is not just technical mumbo-jumbo; because it sure sounds a lot like it.
Maybe Idid not write it clear enough:
I can receive and send WhatsApp messages with my C2 on mobile connection without wifi. Is this prove enough?
But you can proof it yourself on an older sailfishos version. Just remove the APN config for your sim card from the file /system/etc/apns-conf.xml and you will see that most of android apps say that they don’t have internet connection on mobile while native still have.
But I have to admit that it sounds really strange.
This sounds a lot like the issue that has plagued Xperia 10 III users for months, if not for years ([4.6.0.13] Xperia 10 III: Android apps mobile data connectivity - worse then ever). If the issue appeared, mobile data was not available to any Android apps, except Whatsapp.
So it seems the same issue is permanently present in the current state of SFOS 5.0.
You could look into how opengapps script rebuilds the system.img of android, just skip downloading/extracting gapps and its apks, you just need the mounting/extracting insert your modified apn.xml here, then squash to get an .img in the end with your modifications
Edit: one example of the script Sony 10 III - Dual SIM (arm64) | Sailfish OS 4.6 | Android 11 | Open GApps pico installation script · GitHub
Just comment out the install_opengapps step, rest can be easily modified to inject your own versions of files into the extracted system.img before it gets squashed back
Edit2: what you see in /opt/appsupport/rootfs is that system.img mounted, if you kill appsupport files there disappear, so you need to make changes to the img before starting appsupport
Hmm, could it be that @hschmitt got his mobile connection working by copying a working apns-conf.xml to the /system/etc directory?
That sounds a lot less hassle (=risky) than manipulating the system.img
And is easier to undo just before Jolla releases a new SailfishOS version with an official fix of this problem.
The script makes a backup copy of the original system.img in its workdirectory, you can always do it manually too just in case, but if you want to modify system part of appsupport rebuilding the img is the way to go (and you can also always follow the clean reinstall of appsupport guide to download it again from scratch, worst you can get is appsupport not starting and going into bootloop, just replace system.img with the backup and you’re good)
Looks like android has broken dns resolving, I can open http://35.180.139.74 in android firefox just fine on mobile data, so whatsapp is just using a list of IP addresses to communicate and skips domain names
edit: and here’s a pastebin of a minimally changed opengapps script that skips the whole gapps and just adds your own /home/defaultuser/apns-conf.xml into the system.img, modify lines 93 and 94 as needed set -eWORKDIR=/home/.appsupport_systemimg_patchTMPWORKDIR="$WORKDIR/tmp" - Pastebin.com
You seem to be right. Although Internet connections over mobile data on the Jolla C2 do not work for Android apps, WhatsApp makes an exception.
The problem is that AppSupport isn’t aware of the network connection. There’s a component that injects the mobile data state in, and it’s quite a big job to migrate that to support the C2 as it has a very different hardware interface for that. Any app that asks Android if there’s a network connection when on mobile data will be told that there isn’t one and so refuse to work. But Whatsapp doesn’t bother asking - it just tries to connect to things and as there is really network available then it works. DNS would also be broken, but it’s another symptom rather than the cause of the problem.
The migration is ongoing, but as I said it’s a substantial amount of work so is taking some time.