UBports CE buggy and cellular issues

[wibble]

I have shelved my phone for a for a short while and while I came back to try a new UBports system image I am still without working cellular. What is the deal with this issue? Is it only occurring on UBports edition Pinephones? Neither I had Mobian on my phone and that had no cellular working whatsoever. Is there any news on this or updates because so far my Phone cant be used in this state as a daily driver.

This may be something network-specific since it seems to be working for others. Do you know what band your provider is using in your area, and that it's supported by the phone? What do you see if you run (on mobian):

Code:

mmcli -m 0

4G LTE, on my working android phone it uses this T-Mobile LTE APN. I ran the command and it shows that couldnt find the modem.

Update: I turned it off and turned it back on and ran the code this time I did get something. What exactly am I looking for. Does Mobian even have a screenshot feature?  It does show my phone number and other details such as :
state: enabled ,power state: o  ,Signal quality: 0 %

I ended up using the reset command mmcli -m 0 -r and running the command mmcli -m 0  with that resulting in error: couldn't find modem.  It then shows up when running 1 instead of 0 with the following command mmcli -m 1 

Resetting that once more ends up moving the number to 2.

The changing number is expected - use this to find the current number:

Code:

mmcli -L

You should see something like:
/org/freedesktop/ModemManager1/Modem/1 [QUALCOMM INCORPORATED] QUECTEL Mobile Broadband Module

I've never tried screenshots - for cli stuff I usually ssh in from a pc so I can copy that way.

The 'mmcli -m <modem_number>' command gives you an overview of the modem status. The aim was to try to narrow down the details of your problem like whether it could talk to your SIM, whether it registers with the network, doesn't have any signal etc. For example the Status section on mine shows:

Code:

  Status   |                    lock: sim-pin2
           |          unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
           |                   state: registered
           |             power state: on
           |             access tech: lte
           |          signal quality: 84% (recent)

Since you say it's showing your number it is almost certainly able to access your SIM. The previous command should have shown the dbus path to it - something like:
SIM      |            dbus path: /org/freedesktop/ModemManager1/SIM/3
Note the number on the end of the path, similar to the one for the modem. You can get more info on the sim using:

Code:

mmcli -i <modem_number>

My guess would be that t-mobile in your area is using one or other of bands 66 and 71 in your area, which I don't think the EG25-G in the PinePhone supports.You may be able to confirm this with another phone - there are apps for Android that will show details of the LTE connection including the band being used. I guess there are similar things for iPhone.