> On 14 April 2017 at 23:15 Aleksander Morgado wrote:
>
> On Fri, Apr 14, 2017 at 4:57 PM, Colin Helliwell
>
> wrote:
>
> > Might have hung this off the wrong thread, but it's along the same lines.
> > I've just noticed that whilst
Might have hung this off the wrong thread, but it's along the same lines.
I've just noticed that whilst the mmcli status now decodes the operator, the
--sim status doesn't:
# mmcli -m 0
...
3GPP | imei: '358606050452806'
| enabled locks: 'none'
|
On 01/04/17 06:01, Dan Williams wrote:
> On Sat, 2017-03-25 at 21:39 +0100, Aleksander Morgado wrote:
>> The method doing the operator name normalization takes as input the
>> current configured modem charset. If this is UCS2, we will now just
>> assume this is a hint: the string may or may not
On Sat, 2017-03-25 at 21:39 +0100, Aleksander Morgado wrote:
> The method doing the operator name normalization takes as input the
> current configured modem charset. If this is UCS2, we will now just
> assume this is a hint: the string may or may not come in hex/UCS2.
>
> This logic makes the
The method doing the operator name normalization takes as input the
current configured modem charset. If this is UCS2, we will now just
assume this is a hint: the string may or may not come in hex/UCS2.
This logic makes the custom operator name loading in Huawei unneeded,
if the modem is