On Thu, Jul 20, 2017 at 7:01 PM, Tim Small wrote:
> On 20/07/17 17:26, Aleksander Morgado wrote:
>> The AT+CSIM= command there timed out (it took longer than we expected
>> it to take, a pity that these logs don't have timestamp), and then we
>> issued ATE0, and we got the
On 20/07/17 17:26, Aleksander Morgado wrote:
> The AT+CSIM= command there timed out (it took longer than we expected
> it to take, a pity that these logs don't have timestamp), and then we
> issued ATE0, and we got the response of the previous AT+CSIM command
> back there. For this one maybe we
On Thu, Jul 20, 2017 at 5:42 PM, Tim Small wrote:
> On 20/07/17 09:09, Carlo Lobrano wrote:
>>
>>> I think that the commands which mm issue causes it to close and reopen
>>> the SIM and this takes longer than mm is giving it. How should I work
>>> around this?
>>
>> This modem
On Thu, Jul 20, 2017 at 2:04 PM, Piotr Figiel wrote:
> Hi Ben,
> I stumbled on similar issues when dealing with modem restarts on 1.6.
> This was briefly discussed here:
> https://lists.freedesktop.org/archives/modemmanager-devel/2017-June/005016.html
> In that case patch I
On Thu, Jul 20, 2017 at 11:15 AM, Ben Chan wrote:
> On Thu, Jul 20, 2017 at 1:42 AM, Ben Chan wrote:
>> Looking into it a bit more, the periodic signal update doesn't seem to
>> cause the issue. But it seems like the primary port is closed and then
>>
On 20/07/17 09:09, Carlo Lobrano wrote:
>
>> I think that the commands which mm issue causes it to close and reopen
>> the SIM and this takes longer than mm is giving it. How should I work
>> around this?
>
> This modem has an unsolicited signal (QSS) that shows the presence and
> status of the
Hi Ben,
I stumbled on similar issues when dealing with modem restarts on 1.6.
This was briefly discussed here:
https://lists.freedesktop.org/archives/modemmanager-devel/2017-June/005016.html
In that case patch I sent in last message fixed the issue with modem
reappearing though the underlying
Hi Tim,
> I think that the commands which mm issue causes it to close and reopen
> the SIM and this takes longer than mm is giving it. How should I work
> around this?
This modem has an unsolicited signal (QSS) that shows the presence and
status of the SIM.
According to this signal, it seems
Hi Kelvin,
2017-07-19 14:51 GMT+02:00 Kelvin :
> Hi
>
>> According to logs shared by Kelvin, the modem seems to be properly
>> replying
>
>
> Thanks, yes QMI commands seem to be working now but it fails to register on
> a network.
>
> I've tried a SIM card for a different
Hi Aleksander,
I'm looking into an issue with MMBroadbandBearer::cid_selection_3gpp:
Looking for best CID...
(ttyUSB3) device open count is 2 (open)
(ttyUSB3): --> 'ATX4'
(ttyUSB3): --> 'AT'
(ttyUSB3): --> 'AT+CGDCONT?'
loading signal quality...
(ttyUSB3) device open count is 3 (open)
10 matches
Mail list logo