Paul, Could you have a look on this bug? Before connman/connman-gnome upgrade, the feature should work.

It was suggested that the problem here may be related to the SIM card in use which wasn't recognized by ofono and therefore had an empty APN in the ofono gprs settings. However, after updating the gprs settings (create-internet-context) to include the APN, username, and password which can now authenticate and obtain an IP address, connman still does not show the 3G connection.

However, after bringing up the interface, either manually or via connman detecting the usb0 interface coming up, connman then lists two wired ethernet interfaces, both via "test-connman services" and the connman-gnome interface.

This suggests to me that connman is not collecting the contexts from ofono correctly.

Is there an upstream bug with connman? Does connman have a 3G utility or does it need to be written?

(In reply to comment #3)
> Is there an upstream bug with connman? Does connman have a 3G utility or
> does it need to be written?

There are some 3G upstream bugs. Somebody who works on connman could take a look.

Hello,

Judging by Connman 1.9 release notes, there is still no 3G utility or deeper integration with ofono.

Development and testing of this issue is not possible for the moment in Romania, as there is no hardware available with 3G support. Only FRI2 hardware would be a possible platform to use for, but the FRI2 that we have here don't have the 3G module present.

Until Connman can support this upstream, this will be a future, please watch connman for updates.  Also, please include pointers to any upstream bugs

Jukka's input:

Hi Cristian,

this looks like ofono issue to me. ConnMan does not really "configure"
3G connections, that is oFono issue. oFono presents the 3G network connection to ConnMan which creates then a service that the user can connect to.
ConnMan handles the 3G technology i.e., it can enable/disable 3G radio but the 3G technology creation is done by oFono and it informs ConnMan about new radio technology if such is found.

There was some 3G issues earlier and this bug seems to be from that time. Currently if one has decently new oFono and ConnMan, the 3G network should come up automatically and ConnMan should be able to connect to it. Of course oFono is critical element here, it should know about the modem, the pin should be input etc but that is not really part that ConnMan can handle.

Cheers,
Jukka

Hi Alex,
Can you please test if the issues is now solved?

Thanks,
Cristian

Added ofono-tests to image.
ofono test list-modems doesn't return anything.

Also, following the documentation from https://www.yoctoproject.org/download/intel-atom-e640t-fish-river-island-2 it seems that the FRI2 that we are working on doesn't have /dev/ttyACM3 but only /dev/ttyACM0.

lsmod does present an entry for cdc_amc module but this isn't used.

Also, still no presence of 3G in connman-properties.

If anyone has ideas on this, I will gladly apply them.

No hardware to test on. Bug is idling.

Hi,

Any update on this ?

Cheers,
Ionut C

This might be fixed by the improved connman-ui that can be used when sato will move to gtk+3.

I'd like to close this or alternatively get a better description of the issue.

As mentioned earlier: Connman does not configure cellular connectivity in any way, and it's not meant to. So the title of the bug does not describe a bug, it's a statement of fact.

Our connection management UI could have a feature like that (using e.g. ofono APIs) but I'm not so sure it should... APN settings really should be there out-of-the-box and things should Just Work.

If there are bugs like a specific 3G modem (that  is supported by ofono) not actually working in yocto, please file bugs.

I'm closing this.

A) In the typical case APN settings should be provisioned
B) Satos current goal is to be a good testing environment for graphics features: adding new features like 3G settings UI doesn't really fit