We've really been wanting to get it working better for our customers, but honestly your summary is true. Carriers aren't supporting hooks to reliably to get the information. I personally haven't seen a 3GPP command in the data sheets I have to get the info either. If that changes I'd be the first to bring it back but until then it's kind of a dead field. IMHO
On Sat, Jul 28, 2018 at 2:42 PM, Aleksander Morgado < aleksan...@aleksander.es> wrote: > Hey Dan, Ben & all, > > The SubscriptionState property was originally thought to expose the > state of the subscription with the operator. It has been implemented > only in the Altair LTE plugin, and the current implementation is based > on two main things: > * Verizon-specific logic that allows knowing the subscription state > based on the PCO info. > * Registration check errors, e.g. to say that the SIM is > unprovisioned when the registration fails. > > I'm not sure any of the previous two things are very robust. The > Verizon-specific parsing will only work for Verizon, and the > registration check errors may be caused by multiple different root > causes. To me it looks like the Altair LTE plugin is trying to do more > than it's supposed to do. It would be much better if we exposed the > raw PCO info received, and let upper layers process that if needed > with operator-specific logic. > > What do you all think? > Should we deprecate the SubscriptionState property? > Should we expose the raw PCO info? > > -- > Aleksander > https://aleksander.es > _______________________________________________ > ModemManager-devel mailing list > ModemManager-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel >
_______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
