the-modem-distro / pinephone_modem_sdk Goto Github PK

On Sailfish the GNSS worked very well on version 0.4.2 then after upgrade the firmware the GNSS not work anymore either v0.5.0

Sometimes the modem disappears partially. gnome-control-center will say "No wireless / QMI device found", ip a will still show a wwan0 device, but with no IP addresses or routing tables, and gnome-calls will state that there is no voice-capable modem detected.

This can happen after resuming from deep sleep, but sometimes also while the phone is awake. (I sometimes wake up finding the modem "broke" overnight, while the phone was charging and not going to deep sleep.)

The modem is still detected with lsusb in this state; no different from normal operation:

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 008: ID 2c7c:0125 Quectel Wireless Solutions Co., Ltd. EC25 LTE modem
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The only way to get the modem to work again, is by running adb shell reboot from the PinePhone. (adb reboot does not work.)

Attached are openqti.log and dmesg of both the modem and the PinePhone.

I can't see anything out of the ordinary. Do you have any suggestions of where I should look the next time this happens?

Hello Pine64 folks,
as you may be aware checkpoint research has found a high rated vulnerability in QMI:

An attacker can use such a vulnerability to inject malicious code into the modem from Android. This gives the attacker access to the user’s call history and SMS, as well as the ability to listen to the user’s conversations.

Android is already taking steps to mitigating it.

Keep up the great work,
Enrico Bonetti Vieno

P.S.: I'm hooked on your achievements with the pine-phone and pine64 open hardware, big fan here 👍 Thanks for your hard work!!

With the stock image you have the option AT+CMUT with switches 0 and 1 to mute the microphone. This workaround is used by Manjaro with this patch. Currently it seems not to be implemented as shown with this terminal output:

echo 'AT+PINE64ROCKS' | sudo atinout - /dev/ttyUSB2 -
[sudo] password for manjaro: 

OK
[manjaro@manjaro-arm ~]$ echo 'AT+CMUT=1' | sudo atinout - /dev/ttyUSB2 -

ERROR
[manjaro@manjaro-arm ~]$ echo 'AT+CMUT=0' | sudo atinout - /dev/ttyUSB2 -

ERROR

After flashing this firmware, the boot time of the modem is quite noticeably longer compare to stock. I guess it could be due to the hardcoded powersave cpufreq scaling governor. If this is the case it might be sensible to apply the cpufreq scaling governor settings after the modem is fully up.

(Actually is the application processor ever used in a CPU-bound way other than probably during booting?)

I'm trying the last release of this firmware, and it seems to be working well, mostly.

Outgoing calls and data work fine, but incoming calls do not have any effect on the phone. It doesn't ring; it doesn't wake up, and the other side just hears the dial tone until it goes to voicemail.

I have tried the ring-in AT command, but it gives ERROR as a reply:

AT+QURCCFG:"urcport","all"

ERROR

Compared to the proprietary firmware, the call volume is relatively low. In noisy environments, it's hard to understand the other side, even though the earpiece is at maximum volume.

I'm not sure if the modem firmware itself has some volume controls that could be tweaked, but I was able to improve the situation by setting ALSA's "DAC" output to 100% during calls, which defaults to 40% normally.

In order to automatically set this during calls, one must edit /usr/share/alsa/ucm2/PinePhone/VoiceCall.conf and modify the following line:

cset "name='DAC Playback Volume' 160"

It must be changed to:

cset "name='DAC Playback Volume' 100%"

Unfortunately, alsaucm reload doesn't seem to work, so the phone must be rebooted.

After changing this file, the call volume is a lot more bearable.

FLASHING.md says:

    Get required tools: you need adb and fastboot installed in your pinephone
    Debian/Ubuntu based distros: apt install android-tools

debian says:

Couldn't find any package whose name is "android-tools", but there are 3 packages which contain "android-tools" in their name:
  android-tools-adb android-tools-fastboot android-tools-mkbootimg 

do you mean android-tools-adb and android-tools-fastboot packages?

I think the same happens in ubuntu

Hello @Biktorgj

What is the minimal necessary recommended time for the open firmware modem to be initialized?
When using Plasma Mobile on Manjaro Arm, the ofonoctl.service failed to start using the standart ofonoctl.service.
I already altered the service to restart on failure by setting option "Restart=on-failure".
This makes the modem usable for telephony at least, by retrying to initialize the modem until it succeeds.
I found out on the other hand this will break the wwan part of the modem firmware.
When choosing a big enough sleep timer before starting ofonoctl this initializes modem/wwan properly, problem is I don't want to add a to big sleep timer.
Originally ofonoctl has a 15 second sleep timer before starting the real ofonoctl:

[Unit]
Description=Poweron-Modem
After=ofono.service

[Service]
Type=simple
ExecStartPre=/usr/bin/sleep 15
ExecStart=/usr/bin/ofonoctl online
Restart=on-failure

[Install]
WantedBy=default.target

Was original modem firmware quicker in initializing/starting up?

Hi, I am somewhat involved with Mobian, and wanted to ask, what we can incorporate, so that mobian works better with your firmware. Obviously we want still work with the default firmware, but if there are kernel patches, config changes etc that we can include that makes using your firmware easier without breaking the default firmware, we would be happy to do so.

Firmware version: 0.5.9
pinephone version: v1.2b
OS: alarm phosh
behavior:

Wifi constantly connects to hotspot and disconnects.

Thank you very much for you effort on this amazing project.

Could you please give the instruction in order to get logs from the modem?

it shows up and i even tried downgrading to 0.2.7 and then reinstalling plasma mobile but it only shows this

and this

and if i call the number the phone screen just turns on

it would be nice an official matrix channel for development discussions, which can be added to readme file

Hi,
I would like to help you build a better doc because, well I'm kinda confuse :P.
So in order to do that I would need a bit of support.
Is their a way to get in touch?

After flashing this (0.3.1) the Modem no longer powers up. The only logs I can find so far in dmesg -l err

[   24.063878] modem-power serial1-0: The modem didn't report powerup success in time
[   24.076755] modem-power serial1-0: power up failed

I've tried with the latest pinephone-fedora remix as well as the latest Mobian release.

lsusb:

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Trying to manually echo 1 > /sys/class/modem-power/modem-power/device/powered renders me this:

fedora-phone kernel: modem-power serial1-0: powering up
fedora-phone kernel: modem-power serial1-0: wakeup ok
fedora-phone kernel: usb 3-1: new high-speed USB device number 4 using ehci-platform
fedora-phone kernel: usb 3-1: New USB device found, idVendor=18d1, idProduct=d00d, bcdDevice= 1.00
fedora-phone kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
fedora-phone kernel: usb 3-1: Product: Android
fedora-phone kernel: usb 3-1: Manufacturer: Google
fedora-phone kernel: usb 3-1: SerialNumber: [REDACTED]
fedora-phone kernel: modem-power serial1-0: The modem didn't report powerup success in time
fedora-phone kernel: modem-power serial1-0: Forcibly cutting off power, data loss may occur.
fedora-phone kernel: modem-power serial1-0: power up failed
fedora-phone kernel: usb 3-1: USB disconnect, device number 4

But works if the modem put in 2G mode only (I didnt test other variants). In 4G mode mmcli returns "timeout was reached".

Hello,

I flashed the latest release (https://github.com/Biktorgj/pinephone_modem_sdk/releases/tag/0.2.3) this afternoon. It seems to works well.. Congratulations and thank you for this work. This is an important project.

However, I noticed the phone stays warm when plugged and the battery charges very slowly while the modem is on. I'm not sure whether the firmware is at fault here, but connecting to the modem using adb shell and running top shows that openqti constantly uses 60 to 100% of the modem's CPU.

Back to the stock firmware, I don't see this CPU usage in the modem.

Is this expected?
If no, how can I help / debug this? is there an easy way to install gdb or perf and attach to the process to see what's happening?

I'm using Mobian (up to date).

Using the latest 0.5.5 version of the firmware with the ADSP 004 I have very poor call quality.

Every few minutes during a call all sound drops, I can't hear the other side and they can't hear me. As well as that the other side thinks that I have poor reception as the quality isn't great.

This all occurs with good phone reception. I'm using pmOS Edge. From memory I think I saw the same issue with ADSP 003 as well.

I'm in the same situation as bcnaz - I need to have GNSS (GPS) enabled and the mobile should not try to make a GSM connection at the same time. Turning off "Mobile Network" (Phosh) shuts down the whole modem including the location receiving.

How to reproduce:

• run # mmcli -m any --location-status
• turn off Mobile Network
• run again # mmcli -m any --location-status

If it is not possible to turn off the GSM modem while keeping the location signal receiving running, at least a mode where GSM does not try to connect would help. It would also be a sympathetic step in terms of privacy.

Modem seems to work OK, but status bar always shows 3G as status. I'm in an LTE area, and the original firmware didn't exhibit this behavior?

It would be nice to be able to easily check which version of custom firmware is currently installed.

When running the flashall script while the modem is connected, it says the device or resource is busy on the first step:

kevin@pinephone:~/Downloads/modem-firmware$ echo -ne "AT+QFASTBOOT\r" > /dev/ttyUSB2
-bash: /dev/ttyUSB2: Apparaat of hulpbron is bezig

(My user is in the dialout group.)

Running it as root does work as expected.

As this is the only command that has to be run as root, I'd suggest changing it to:

sudo su -c 'echo -ne "AT+QFASTBOOT\r" > /dev/ttyUSB2'

That way, rebooting to fastboot should always work.

here's what worked for me on mobian:

# apt install picocom
# picocom --echo --omap ignlf /dev/ttyUSB2

exit the session with C-a, C-x

I upgraded this afternoon to 0.4.2 from 0.3.0, and upgraded my ADSP firmware as suggested. Since this update, I cannot make or receive phone calls. Data and SMS work flawlessly.

I am using Arch with all packages up to date.

Whenever I try to place a phone call, the call window appears for a split second and then disappears. The call is logged in the call log from gnome-calls, but nothing happens. The following extract from journalctl shows 2 attempted outgoing phone calls and an attempted incoming phone call.

Oct 06 15:53:41 danctnix ModemManager[3080]: <info>  [modem0/call2] user request to start call
Oct 06 15:53:41 danctnix ModemManager[3080]: <info>  [modem0/call2] call state changed: unknown -> dialing (outgoing-started)
Oct 06 15:53:41 danctnix gsd-media-keys[3331]: Unable to get default sink
Oct 06 15:53:41 danctnix gsd-media-keys[3331]: Unable to get default source
Oct 06 15:53:41 danctnix ModemManager[3080]: <warn>  [modem0/call2] couldn't start call: Couldn't create call: QMI protocol error (48): 'InvalidArgument'
Oct 06 15:53:41 danctnix ModemManager[3080]: <info>  [modem0/call2] call state changed: dialing -> terminated (unknown)
Oct 06 15:53:41 danctnix gnome-calls[3495]: Error starting outgoing call ModemManager call to `PHONENUMBER': GDBus.Error:org.freedesktop.libqmi.Error.Protocol.InvalidArgument: Couldn't create call: QMI protocol error (48): 'InvalidArgument'
Oct 06 15:53:41 danctnix gsd-media-keys[3331]: Unable to get default sink
Oct 06 15:53:41 danctnix gsd-media-keys[3331]: Unable to get default source
Oct 06 15:54:12 danctnix ModemManager[3080]: <info>  [modem0/call3] user request to start call
Oct 06 15:54:12 danctnix ModemManager[3080]: <info>  [modem0/call3] call state changed: unknown -> dialing (outgoing-started)
Oct 06 15:54:12 danctnix gsd-media-keys[3331]: Unable to get default sink
Oct 06 15:54:12 danctnix gsd-media-keys[3331]: Unable to get default source
Oct 06 15:54:12 danctnix ModemManager[3080]: <warn>  [modem0/call3] couldn't start call: Couldn't create call: QMI protocol error (48): 'InvalidArgument'
Oct 06 15:54:12 danctnix ModemManager[3080]: <info>  [modem0/call3] call state changed: dialing -> terminated (unknown)
Oct 06 15:54:12 danctnix gnome-calls[3495]: Error starting outgoing call ModemManager call to `PHONENUMBER': GDBus.Error:org.freedesktop.libqmi.Error.Protocol.InvalidArgument: Couldn't create call: QMI protocol error (48): 'InvalidArgument'
Oct 06 15:54:12 danctnix gsd-media-keys[3331]: Unable to get default sink
Oct 06 15:54:12 danctnix gsd-media-keys[3331]: Unable to get default source
Oct 06 15:54:27 danctnix ModemManager[3080]: <warn>  [modem0] network reject indication received
Oct 06 15:54:27 danctnix ModemManager[3080]: <warn>  [modem0]   service domain: cs
Oct 06 15:54:27 danctnix ModemManager[3080]: <warn>  [modem0]   radio interface: umts
Oct 06 15:54:27 danctnix ModemManager[3080]: <warn>  [modem0]   reject cause: network-failure

As of 0.5.1, AT+QGMR doesn't return what it used to, the more detailed version of AT+GMR, but instead the same response as AT+GETSWREV.
I believe this is a bug, but if it is not, then a documentation update would be needed.

After I installed the free modem package, postmarketos doesn't ring or show the caller application. In arch (also phosh) it works.
Before it was perfect in pmos.
The phone wakes up though.
Any pointers?
Thank you in advance!

Currently trying to work out this issue.
I'm reporting this in the issue tracker for good measure, so other people don't need to file a separate bug report on this.

Currently after a fresh reboot, with persistent ADB disabled, you are not able to switch ADB straight to on using the AT+ADBON command.

Current workaround is one of the following two:
1: Reboot the system after issueing the AT+ADBON command to switch on ADB at boot.
2: First issue AT+ADBOFF, causes a usb reset. Issue AT+ADBON after modem has come back online. This resets usb briefly again, but ADB should now be started.

Probably has something to do with OpenQTI not reading correct USB state or something like that. Have to investigate some more.

Progress can be tracked in here.

I see you have no LICENSE file for this project. The default is copyright.

I would suggest releasing the code under the GPL-3.0-or-later or AGPL-3.0-or-later license so that others are encouraged to contribute changes back to your project.

See error messages on last lines below. The modem is gone now, even after a reboot. How can I recover from this?

1. Checked version of ADSP firmware:

   $ mmcli -m any --command="AT+QGMR"
   response: 'EG25GGBR07A08M2G_01.001.01.001'
   

2. Upgraded to ADSP version 01.003.01.003:

   # cd /tmp
   # wget https://github.com/Biktorgj/quectel_eg25_recovery/raw/EG25GGBR07A08M2G_01.003.01.003/update/NON-HLOS.ubi
   # echo -ne "AT+QFASTBOOT\r" > /dev/ttyUSB2
   # fastboot flash modem NON-HLOS.ubi && fastboot reboot
   

3. Flashed the Biktorgj firmware:

   $ cd ~/src
   $ wget https://github.com/Biktorgj/pinephone_modem_sdk/releases/download/0.4.2/package.tar.gz
   $ mkdir firmware
   $ tar xzf package.tar.gz -C firmware
   $ cd firmware
   $ sudo ./flashall
   Sending AT+QFASTBOOT...
   FAILED (remote: 'unknown command')
   fastboot: error: Command failed
   Sending 'aboot' (486 KB)                           OKAY [  0.024s]
   Writing 'aboot'                                    OKAY [  0.209s]
   Finished. Total time: 0.244s
   Rebooting                                          OKAY [  0.018s]
   Finished. Total time: 0.068s
   < waiting for any device >
   OKAY [  0.002s]
   Finished. Total time: 0.003s
   Sending 'boot' (4566 KB)                           OKAY [  0.150s]
   Writing 'boot'                                     FAILED (Status read failed (No such device))
   fastboot: error: Command failed
   ./flashall: exit: line 11: Illegal number: Failed to flash main kernel
   

Seems I have no call audio after flash. Arch - no audio/no mic, Mobian audio works but mic does not. Was working until flash, is this firmware related?

I followed the instructions at https://github.com/Biktorgj/pinephone_modem_sdk/blob/honister/docs/RECOVERY.md and on stock the call audio works as expected. Seems 0.5.5 doesn't work right on PPP

I've been looking for a way to boot into the custom firmware without modifying the stock firmware.

Motivation

This would allow to:

• avoid the risk of potentially (soft) bricking the modem while flashing the custom lk
• tie the modem firmware version to the currently booted distribution, making it deterministic
• provide a nice unified way for users to use this firmware, that works accross distros. I would put the logic in eg25-manager (if that's fine with @a-wai et al.), which is widely used already among distros.
• have upgrading the modem firmware as easy as installing a new package and rebooting/restarting eg25-manager

Research

To my surprise, it seems that the kernel of the stock firmware was built with CONFIG_KEXEC.

/ # echo 0 > /proc/sys/kernel/dmesg_restrict 
/ # echo 0 > /proc/sys/kernel/kptr_restrict
/ # cat /proc/kallsyms | grep kexec
c0035c48 W compat_sys_kexec_load
c0035c48 W sys_kexec_file_load
c0035c48 W sys_kexec_load
c0a62c44 t setup_crash_kexec_post_notifiers
c0aa01e2 t __setup_str_setup_crash_kexec_post_notifiers
c0aa2b64 t __setup_setup_crash_kexec_post_notifiers
c0b357f4 b crash_kexec_post_notifiers

rw tmpfs mounts:

/ # mount
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (ro,relatime,bulk_read,chk_data_crc)
ubi1:modem on /firmware type ubifs (ro,relatime,bulk_read,chk_data_crc)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=64k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime)
tmpfs on /var/lib type tmpfs (rw,relatime)
/dev/ubi2_0 on /cache type ubifs (rw,relatime,bulk_read,chk_data_crc)
/dev/ubi2_0 on /data type ubifs (rw,relatime,bulk_read,chk_data_crc)
none on /sys/kernel/config type configfs (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)

> 70 MiB of RAM available in tmpfs:

/ # df -h
Filesystem                Size      Used Available Use% Mounted on
ubi0:rootfs              57.9M     51.7M      6.2M  89% /
ubi1:modem               41.1M     33.7M      7.4M  82% /firmware
tmpfs                    64.0K      4.0K     60.0K   6% /dev
tmpfs                    77.8M     28.0K     77.8M   0% /run
tmpfs                    77.8M    112.0K     77.7M   0% /var/volatile
tmpfs                    77.8M    112.0K     77.7M   0% /var/lib
/dev/ubi2_0              48.3M      1.1M     47.2M   2% /cache
/dev/ubi2_0              48.3M      1.1M     47.2M   2% /data

Concept

So I'm assuming it would work like this:

• automatize getting adb shell access via AT command
• do sanity checks via AT / adb shell (i.e. did we boot into the custom fw already?)
• adb push files to /var/lib tmpfs:
  • kexec static binary
  • new kernel
  • initramfs file
    • which contains all of the custom firmware userspace code
    • according to @Megous this should be doable in 200 KiB? Given that we have > 70 MiB in tmpfs, this seems feasible even if it is a lot bigger.
• shutdown running userspace services via adb shell
• use kexec to boot into custom kernel + initramfs
• wait until it is booted
• done, modem can be used now

A potential problem could be, that kexec boot itself takes a long time. Personally I think the advantages would be worth it, even if this means that it takes 20s or so extra after boot until the modem is fully functional. That's just a random guess, I didn't try this concept out yet.

Next steps

The next step to trying this out is, creating a minimal initramfs that allows communication via serial and building the userspace kexec program statically. To check whether kexec works at all, and to test how long this boot method takes. From there on, we could look into building this awesome firmware into such an initramfs and then potentially automate the whole setup and put it into eg25-manager.

I'll probably not continue investigating this any time soon due to other tasks, but I wanted to write the idea down. If somebody wants to evaluate if this is feasible, please go ahead.

Thoughts?

What do you think, does it sound feasible or am I overlooking something?

Is is possible there is some sort of watchdog or maybe a buffer problem with the AT command port? I was having persisitent USB reset drama, but the following command completely mitigated the problem:

# while true ; do echo ATI | atinout - /dev/EG25.AT - ; sleep 2 ; done

Simply listening to the output (eg):

# hd /dev/EG25.AT

was not enough, but the ATI in a loop (embarrassingly) works really well.

I can't connect to my mobile operator after the update (v0.4.2 > 0.5.1). Downgrade to 0.4.2 solves the problem.

HW: PinePhone v1.2b
OS: Manjaro/Phosh-dev - https://github.com/manjaro-pinephone/phosh-dev/releases/tag/202201030254

journald:

• restart eg25

  Jan 03 15:35:11 manjaro-arm systemd[1]: Stopping Quectel EG25 modem...
  Jan 03 15:35:11 manjaro-arm eg25manager[358]: dropping systemd sleep delay inhibitor
  Jan 03 15:35:11 manjaro-arm eg25manager[358]: Powering down the modem...
  Jan 03 15:35:12 manjaro-arm eg25manager[358]: Executed power-on/off sequence
  Jan 03 15:35:12 manjaro-arm eg25manager[358]: Executed power-off sequence
  Jan 03 15:35:18 manjaro-arm ModemManager[1545]: <info>  [modem0] simple connect started...
  Jan 03 15:35:18 manjaro-arm ModemManager[1545]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
  Jan 03 15:35:18 manjaro-arm ModemManager[1545]: <info>  [modem0] simple connect state (5/8): register
  Jan 03 15:35:42 manjaro-arm eg25manager[358]: Modem down, quitting...
  Jan 03 15:35:42 manjaro-arm systemd[1]: eg25-manager.service: Deactivated successfully.
  Jan 03 15:35:42 manjaro-arm systemd[1]: Stopped Quectel EG25 modem.
  Jan 03 15:35:42 manjaro-arm systemd[1]: Started Quectel EG25 modem.
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Opening config file: /usr/share/eg25-manager/pine64,pinephone-1.2.toml
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: STATUS is low, modem already powered
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: taking systemd sleep inhibitor
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager appeared on D-Bus
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: oFono vanished from D-Bus
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: inhibitor sleep fd is 21
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp.ProfileManager' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Simple' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Firmware' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Voice' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Time' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Adding new modem `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGMR
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Messaging' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Location' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Adding new modem with location capabilities `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Response: [0.5.1\r\n\r\nOK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QDAI?
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Got a different result than expected, changing value...
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Expected: [1,1,0,1,0,0,1,1]
                                                 Response: [OK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QDAI=1,1,0,1,0,0,1,1
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="risignaltype"
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Response: [+QCFG: "risignaltype","physical"\r\n\r\nOK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="ims"
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Response: [+QCFG: "ims",1,0\r\n\r\nOK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="apready"
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Response: [+QCFG: "apready",1,0,500\r\n\r\nOK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="urc/ri/ring"
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Response: [+QCFG: "urc/ri/ring","pulse",120,1000,5000,"off",1\r\n\r\nOK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="urc/ri/smsincoming"
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Response: [+QCFG: "urc/ri/smsincoming","pulse",120,1\r\n\r\nOK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="urc/ri/other"
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Response: [+QCFG: "urc/ri/other","off",1,1\r\n\r\nOK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="urc/delay"
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Response: [+QCFG: "urc/delay",0\r\n\r\nOK]
  Jan 03 15:35:42 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="urc/cache"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QCFG: "urc/cache",0\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="urc/ri/pin"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QCFG: "urc/ri/pin",uart_ri\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QURCCFG="urcport"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QURCCFG: "urcport","all"\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QSCLK=1
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSXTRA?
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QGPSXTRA: 1\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSCFG="gnssconfig"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QGPSCFG: "gnssconfig",4\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSCFG="odpcontrol"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QGPSCFG: "odpcontrol",0\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSCFG="dpoenable"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QGPSCFG: "dpoenable",1\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSCFG="gpsnmeatype"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QGPSCFG: "gpsnmeatype",31\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSCFG="glonassnmeatype"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QGPSCFG: "glonassnmeatype",7\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSCFG="galileonmeatype"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QGPSCFG: "galileonmeatype",0\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSCFG="beidounmeatype"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QGPSCFG: "beidounmeatype",0\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSCFG="autogps"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QGPSCFG: "autogps",0\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="fast/poweroff"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Got a different result than expected, changing value...
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Expected: [0]
                                                 Response: [OK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="fast/poweroff",0
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="sleepind/level"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QCFG: "sleepind/level",0\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="wakeupin/level"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [+QCFG: "wakeupin/level",0,0\r\n\r\nOK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="ApRstLevel"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Got a different result than expected, changing value...
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Expected: [1]
                                                 Response: [OK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="ApRstLevel",1
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="ModemRstLevel"
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Got a different result than expected, changing value...
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Expected: [1]
                                                 Response: [OK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QCFG="ModemRstLevel",1
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:35:43 manjaro-arm eg25manager[1614]: Executed soft sleep sequence
  Jan 03 15:36:13 manjaro-arm eg25manager[1614]: GNSS assistance upload started...
  Jan 03 15:36:13 manjaro-arm eg25manager[1614]: GNSS assistance upload step (1/9): fetching assistance data
  Jan 03 15:36:13 manjaro-arm eg25manager[1614]: Fetching GNSS assistance data from https://xtrapath4.izatcloud.net/xtra2.bin was successful
  Jan 03 15:36:13 manjaro-arm eg25manager[1614]: GNSS assistance upload step (2/9): disabling GNSS engine through ModemManager
  Jan 03 15:36:13 manjaro-arm eg25manager[1614]: GNSS assistance upload step (3/9): disabling GNSS engine through AT+QGPS
  Jan 03 15:36:13 manjaro-arm eg25manager[1614]: Executed soft wake sequence
  Jan 03 15:36:13 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPS?
  Jan 03 15:36:13 manjaro-arm eg25manager[1614]: Response: [+QGPS: 0\r\n\r\nOK]
  Jan 03 15:36:13 manjaro-arm eg25manager[1614]: Executed soft sleep sequence
  Jan 03 15:36:13 manjaro-arm eg25manager[1614]: GNSS assistance upload step (4/9): initiating upload
  Jan 03 15:36:14 manjaro-arm eg25manager[1614]: Executed soft wake sequence
  Jan 03 15:36:14 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QFDEL="RAM:*"
  Jan 03 15:36:14 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:36:14 manjaro-arm eg25manager[1614]: Executed soft sleep sequence
  Jan 03 15:36:14 manjaro-arm eg25manager[1614]: Initiate GNSS assistance data upload: "RAM:xtra2.bin",59555,10
  Jan 03 15:36:14 manjaro-arm eg25manager[1614]: Executed soft wake sequence
  Jan 03 15:36:14 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QFUPL="RAM:xtra2.bin",59555,10
  Jan 03 15:36:14 manjaro-arm eg25manager[1614]: Response: [CONNECT]
  Jan 03 15:36:14 manjaro-arm eg25manager[1614]: Modem ready for GNSS assistance data upload
  Jan 03 15:36:14 manjaro-arm eg25manager[1614]: GNSS assistance upload step (5/9): uploading assistance data
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Successfully uploaded 59555 bytes to the modem
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Response: [+QFUPL: 59555,31b8\r\n\r\nOK]
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Executed soft sleep sequence
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: GNSS assistance upload step (6/9): finishing upload
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Setting GNSS assistance UTC clock to: 0,"2022/01/03,14:36:20"
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Setting GNSS assistance file to: "RAM:xtra2.bin"
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Executed soft wake sequence
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSXTRATIME=0,"2022/01/03,14:36:20"
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Successfully sent command: AT+QGPSXTRADATA="RAM:xtra2.bin"
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Response: [OK]
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: Executed soft sleep sequence
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: GNSS assistance data upload finished
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: GNSS assistance upload step (7/9): re-enabling GNSS through ModemManager
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: GNSS assistance upload step (8/9): re-enabling GNSS through AT+QGPS
  Jan 03 15:36:20 manjaro-arm eg25manager[1614]: GNSS assistance upload step (9/9): finished
  Jan 03 15:36:21 manjaro-arm NetworkManager[387]: <warn>  [1641220581.4270] modem-broadband[ttyUSB2]: failed to connect modem: Network timeout
  Jan 03 15:36:21 manjaro-arm NetworkManager[387]: <info>  [1641220581.4274] device (ttyUSB2): state change: prepare -> failed (reason 'gsm-registration-timeout', sys-iface-state: 'managed')
  Jan 03 15:36:21 manjaro-arm NetworkManager[387]: <warn>  [1641220581.4408] device (ttyUSB2): Activation: failed for connection 'Default'
  Jan 03 15:36:21 manjaro-arm NetworkManager[387]: <info>  [1641220581.4444] device (ttyUSB2): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
  Jan 03 15:36:21 manjaro-arm NetworkManager[387]: <info>  [1641220581.4516] policy: auto-activating connection 'Default' (b5430712-fceb-442d-b693-313065df922f)
  Jan 03 15:36:21 manjaro-arm NetworkManager[387]: <info>  [1641220581.4588] device (ttyUSB2): Activation: starting connection 'Default' (b5430712-fceb-442d-b693-313065df922f)
  Jan 03 15:36:21 manjaro-arm NetworkManager[387]: <info>  [1641220581.4641] device (ttyUSB2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  Jan 03 15:36:21 manjaro-arm ModemManager[1545]: <info>  [modem0] simple connect started...
  Jan 03 15:36:21 manjaro-arm ModemManager[1545]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
  Jan 03 15:36:21 manjaro-arm ModemManager[1545]: <info>  [modem0] simple connect state (5/8): register
  Jan 03 15:36:36 manjaro-arm gsd-xsettings[722]: Failed to get current UI legacy scaling factor
  Jan 03 15:36:36 manjaro-arm gsd-xsettings[722]: Failed to get current UI legacy scaling factor
  Jan 03 15:36:36 manjaro-arm gsd-color[708]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
  Jan 03 15:37:22 manjaro-arm ModemManager[1545]: <info>  [modem0] simple connect started...
  Jan 03 15:37:22 manjaro-arm ModemManager[1545]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
  Jan 03 15:37:22 manjaro-arm ModemManager[1545]: <info>  [modem0] simple connect state (5/8): register
  

• restart MM

  Jan 03 15:37:51 manjaro-arm ModemManager[1545]: <info>  caught signal, shutting down...
  Jan 03 15:37:51 manjaro-arm ModemManager[1545]: <info>  [modem0] state changed (enabled -> disabling)
  Jan 03 15:37:51 manjaro-arm systemd[1]: Stopping Modem Manager...
  Jan 03 15:37:51 manjaro-arm ModemManager[1545]: <info>  [modem0] 3GPP registration state changed (idle -> unknown)
  Jan 03 15:37:51 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mm_vanished_cb() Modem Manager vanished
  Jan 03 15:37:51 manjaro-arm eg25manager[1614]: ModemManager vanished from D-Bus
  Jan 03 15:37:51 manjaro-arm NetworkManager[387]: <info>  [1641220671.4545] modem-manager: ModemManager no longer available
  Jan 03 15:37:51 manjaro-arm NetworkManager[387]: <info>  [1641220671.4550] device (ttyUSB2): state change: prepare -> unmanaged (reason 'removed', sys-iface-state: 'removed')
  Jan 03 15:37:51 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_NO_MANAGER
  Jan 03 15:37:51 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:mm_vanished_cb() Modem Manager vanished
  Jan 03 15:37:51 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:mm_vanished_cb() Modem Manager vanished
  Jan 03 15:37:51 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_NO_MANAGER
  Jan 03 15:37:51 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mm_vanished_cb() Modem Manager vanished
  Jan 03 15:37:51 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_NO_MANAGER
  Jan 03 15:37:51 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_NO_MANAGER
  Jan 03 15:37:51 manjaro-arm ModemManager[1545]: <info>  ModemManager is shut down
  Jan 03 15:37:51 manjaro-arm gsd-wwan[710]: file ../gnome-settings-daemon/plugins/wwan/gsd-wwan-manager.c: line 560 (object_removed_cb): should not be reached
  Jan 03 15:37:51 manjaro-arm dbus-daemon[357]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=0 pid=387 comm="/usr/bin/NetworkManager --no-daemon ") interface="org.freedesktop.ModemManager1.Modem.Simple" member="Disconnect" error name="(unset)" requested_reply="0" destination=":1.84" (uid=0 pid=1545 comm="/usr/bin/ModemManager --test-quick-suspend-resume ")
  Jan 03 15:37:51 manjaro-arm systemd[1]: ModemManager.service: Deactivated successfully.
  Jan 03 15:37:51 manjaro-arm systemd[1]: Stopped Modem Manager.
  Jan 03 15:37:51 manjaro-arm systemd[1]: ModemManager.service: Consumed 1.442s CPU time.
  Jan 03 15:37:51 manjaro-arm dbus-daemon[357]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=0 pid=387 comm="/usr/bin/NetworkManager --no-daemon ") interface="org.freedesktop.ModemManager1.Modem.Simple" member="Disconnect" error name="(unset)" requested_reply="0" destination=":1.84" (uid=0 pid=1545 comm="/usr/bin/ModemManager --test-quick-suspend-resume ")
  Jan 03 15:37:51 manjaro-arm NetworkManager[387]: <warn>  [1641220671.6256] modem-broadband[ttyUSB2]: failed to disconnect modem: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=0 pid=387 comm="/usr/bin/NetworkManager --no-daemon ") interface="org.freedesktop.ModemManager1.Modem.Simple" member="Disconnect" error name="(unset)" requested_reply="0" destination=":1.84" (uid=0 pid=1545 comm="/usr/bin/ModemManager --test-quick-suspend-resume ")                                                                                                                                                  
  Jan 03 15:37:51 manjaro-arm systemd[1]: Starting Modem Manager...
  Jan 03 15:37:51 manjaro-arm ModemManager[1635]: <info>  ModemManager (version 1.18.4) starting in system bus...
  Jan 03 15:37:51 manjaro-arm eg25manager[1614]: ModemManager appeared on D-Bus
  Jan 03 15:37:51 manjaro-arm systemd[1]: Started Modem Manager.
  Jan 03 15:37:51 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:mm_appeared_cb() Modem Manager appeared
  Jan 03 15:37:51 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:mm_appeared_cb() Modem Manager appeared
  Jan 03 15:37:52 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_MANAGER_FOUND
  Jan 03 15:37:52 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:cb_mm_manager_new() ModemManager found: :1.89
  Jan 03 15:37:52 manjaro-arm mmsdtng[1322]: Could not connect to modem
  Jan 03 15:37:52 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_NO_MODEM
  Jan 03 15:37:52 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_MANAGER_FOUND
  Jan 03 15:37:52 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:cb_mm_manager_new() ModemManager found: :1.89
  Jan 03 15:37:52 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_MANAGER_FOUND
  Jan 03 15:37:52 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_MANAGER_FOUND
  Jan 03 15:37:52 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:cb_mm_manager_new() ModemManager found: :1.89
  Jan 03 15:37:52 manjaro-arm vvmd[472]: vvmd[472]: Could not connect to modem
  Jan 03 15:37:52 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_NO_MODEM
  Jan 03 15:37:52 manjaro-arm mmsdtng[471]: Could not connect to modem
  Jan 03 15:37:52 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:cb_mm_manager_new() ModemManager found: :1.89
  Jan 03 15:37:52 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_NO_MODEM
  Jan 03 15:37:52 manjaro-arm vvmd[472]: Could not connect to modem
  Jan 03 15:37:52 manjaro-arm NetworkManager[387]: <info>  [1641220672.1239] modem-manager: ModemManager now available
  Jan 03 15:37:52 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_NO_MODEM
  Jan 03 15:37:53 manjaro-arm ModemManager[1635]: [/dev/cdc-wdm0] Opening device with flags 'version-info, proxy'...
  Jan 03 15:37:53 manjaro-arm ModemManager[1635]: [/dev/cdc-wdm0] created endpoint
  Jan 03 15:37:53 manjaro-arm ModemManager[1635]: cannot connect to proxy: Could not connect: Connection refused
  Jan 03 15:37:53 manjaro-arm ModemManager[1635]: spawning new qmi-proxy (try 1)...
  Jan 03 15:37:53 manjaro-arm ModemManager[1635]: [/dev/cdc-wdm0] Checking version info (45 retries)...
  Jan 03 15:37:54 manjaro-arm ModemManager[1635]: <info>  [base-manager] couldn't check support for device '/sys/devices/platform/soc/1c10000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1': not supported by any plugin
  Jan 03 15:37:55 manjaro-arm ModemManager[1635]: transaction 0x2 aborted, but message is not abortable
  Jan 03 15:37:56 manjaro-arm ModemManager[1635]: transaction 0x3 aborted, but message is not abortable
  Jan 03 15:37:57 manjaro-arm ModemManager[1635]: transaction 0x4 aborted, but message is not abortable
  Jan 03 15:37:58 manjaro-arm ModemManager[1635]: transaction 0x5 aborted, but message is not abortable
  Jan 03 15:37:59 manjaro-arm ModemManager[1635]: transaction 0x6 aborted, but message is not abortable
  Jan 03 15:38:00 manjaro-arm ModemManager[1635]: transaction 0x7 aborted, but message is not abortable
  Jan 03 15:38:01 manjaro-arm ModemManager[1635]: transaction 0x8 aborted, but message is not abortable
  Jan 03 15:38:02 manjaro-arm ModemManager[1635]: transaction 0x9 aborted, but message is not abortable
  Jan 03 15:38:03 manjaro-arm ModemManager[1635]: transaction 0xa aborted, but message is not abortable
  Jan 03 15:38:04 manjaro-arm ModemManager[1635]: transaction 0xb aborted, but message is not abortable
  Jan 03 15:38:05 manjaro-arm ModemManager[1635]: transaction 0xc aborted, but message is not abortable
  Jan 03 15:38:06 manjaro-arm ModemManager[1635]: transaction 0xd aborted, but message is not abortable
  Jan 03 15:38:07 manjaro-arm ModemManager[1635]: transaction 0xe aborted, but message is not abortable
  Jan 03 15:38:08 manjaro-arm ModemManager[1635]: transaction 0xf aborted, but message is not abortable
  Jan 03 15:38:09 manjaro-arm ModemManager[1635]: transaction 0x10 aborted, but message is not abortable
  Jan 03 15:38:10 manjaro-arm ModemManager[1635]: transaction 0x11 aborted, but message is not abortable
  Jan 03 15:38:11 manjaro-arm ModemManager[1635]: transaction 0x12 aborted, but message is not abortable
  Jan 03 15:38:12 manjaro-arm ModemManager[1635]: transaction 0x13 aborted, but message is not abortable
  Jan 03 15:38:13 manjaro-arm ModemManager[1635]: transaction 0x14 aborted, but message is not abortable
  Jan 03 15:38:14 manjaro-arm ModemManager[1635]: transaction 0x15 aborted, but message is not abortable
  Jan 03 15:38:15 manjaro-arm ModemManager[1635]: transaction 0x16 aborted, but message is not abortable
  Jan 03 15:38:16 manjaro-arm ModemManager[1635]: transaction 0x17 aborted, but message is not abortable
  Jan 03 15:38:17 manjaro-arm ModemManager[1635]: transaction 0x18 aborted, but message is not abortable
  Jan 03 15:38:18 manjaro-arm ModemManager[1635]: transaction 0x19 aborted, but message is not abortable
  Jan 03 15:38:19 manjaro-arm ModemManager[1635]: transaction 0x1a aborted, but message is not abortable
  Jan 03 15:38:20 manjaro-arm ModemManager[1635]: transaction 0x1b aborted, but message is not abortable
  Jan 03 15:38:21 manjaro-arm ModemManager[1635]: transaction 0x1c aborted, but message is not abortable
  Jan 03 15:38:22 manjaro-arm ModemManager[1635]: transaction 0x1d aborted, but message is not abortable
  Jan 03 15:38:23 manjaro-arm ModemManager[1635]: transaction 0x1e aborted, but message is not abortable
  Jan 03 15:38:24 manjaro-arm ModemManager[1635]: transaction 0x1f aborted, but message is not abortable
  Jan 03 15:38:25 manjaro-arm ModemManager[1635]: transaction 0x20 aborted, but message is not abortable
  Jan 03 15:38:26 manjaro-arm ModemManager[1635]: transaction 0x21 aborted, but message is not abortable
  Jan 03 15:38:27 manjaro-arm ModemManager[1635]: transaction 0x22 aborted, but message is not abortable
  Jan 03 15:38:28 manjaro-arm ModemManager[1635]: transaction 0x23 aborted, but message is not abortable
  Jan 03 15:38:29 manjaro-arm ModemManager[1635]: transaction 0x24 aborted, but message is not abortable
  Jan 03 15:38:30 manjaro-arm ModemManager[1635]: transaction 0x25 aborted, but message is not abortable
  Jan 03 15:38:31 manjaro-arm ModemManager[1635]: transaction 0x26 aborted, but message is not abortable
  Jan 03 15:38:32 manjaro-arm ModemManager[1635]: transaction 0x27 aborted, but message is not abortable
  Jan 03 15:38:33 manjaro-arm ModemManager[1635]: transaction 0x28 aborted, but message is not abortable
  Jan 03 15:38:34 manjaro-arm ModemManager[1635]: transaction 0x29 aborted, but message is not abortable
  Jan 03 15:38:35 manjaro-arm ModemManager[1635]: transaction 0x2a aborted, but message is not abortable
  Jan 03 15:38:36 manjaro-arm ModemManager[1635]: transaction 0x2b aborted, but message is not abortable
  Jan 03 15:38:37 manjaro-arm ModemManager[1635]: transaction 0x2c aborted, but message is not abortable
  Jan 03 15:38:38 manjaro-arm ModemManager[1635]: transaction 0x2d aborted, but message is not abortable
  Jan 03 15:38:39 manjaro-arm ModemManager[1635]: transaction 0x2e aborted, but message is not abortable
  Jan 03 15:38:39 manjaro-arm ModemManager[1635]: <info>  [device /sys/devices/platform/soc/1c1b000.usb/usb2/2-1] creating modem with plugin 'quectel' and '6' ports
  Jan 03 15:38:39 manjaro-arm ModemManager[1635]: <warn>  [plugin/quectel] could not grab port cdc-wdm0: Cannot add port 'usbmisc/cdc-wdm0', unhandled port type
  Jan 03 15:38:39 manjaro-arm ModemManager[1635]: <warn>  [plugin/quectel] could not grab port ttyUSB3: Cannot add port 'tty/ttyUSB3', unhandled port type
  Jan 03 15:38:39 manjaro-arm ModemManager[1635]: <info>  [base-manager] modem for device '/sys/devices/platform/soc/1c1b000.usb/usb2/2-1' successfully created
  Jan 03 15:38:40 manjaro-arm ModemManager[1635]: <info>  [modem0] state changed (unknown -> disabled)
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:cb_object_added() cb_object_added
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: New Object with Messaging feature found, Adding...
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_add_object() Not checking for a default Modem
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_add_object() Added device at: /org/freedesktop/ModemManager1/Modem/0
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_init_modem() mmsd_mm_init_modem
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:cb_object_added() cb_object_added
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: New Object with Messaging feature found, Adding...
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:cb_object_added() cb_object_added
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:cb_object_added() cb_object_added
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: New Object does not have Messaging feature, ignoring....
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_add_object() Not checking for a default Modem
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_add_object() Added device at: /org/freedesktop/ModemManager1/Modem/0
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_init_modem() vvmd_mm_init_modem
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_MODEM_FOUND
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_add_object() Not checking for a default Modem
  Jan 03 15:38:40 manjaro-arm vvmd[472]: New Object does not have Messaging feature, ignoring....
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_add_object() Added device at: /org/freedesktop/ModemManager1/Modem/0
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_add_object() Not checking for a default Modem
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_init_modem() mmsd_mm_init_modem
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_add_object() Added device at: /org/freedesktop/ModemManager1/Modem/0
  Jan 03 15:38:40 manjaro-arm NetworkManager[387]: <info>  [1641220720.2714] modem["ttyUSB2"]: modem state changed, 'disabled' --> 'enabling' (reason: user preference)
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_init_modem() vvmd_mm_init_modem
  Jan 03 15:38:40 manjaro-arm NetworkManager[387]: <info>  [1641220720.2780] manager: (ttyUSB2): new Broadband device (/org/freedesktop/NetworkManager/Devices/6)
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_MODEM_FOUND
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager object `/org/freedesktop/ModemManager1/Modem/0' added
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp.ProfileManager' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Firmware' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Voice' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Time' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: Adding new modem `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Messaging' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Location' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: Adding new modem with location capabilities `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm eg25manager[1614]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Simple' found on object `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm chatty[882]: Your SIM or Modem does not support modem manger's number! Please file a bug report
  Jan 03 15:38:40 manjaro-arm NetworkManager[387]: <info>  [1641220720.2883] device (ttyUSB2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
  Jan 03 15:38:40 manjaro-arm NetworkManager[387]: <info>  [1641220720.2988] device (ttyUSB2): modem state 'enabling'
  Jan 03 15:38:40 manjaro-arm NetworkManager[387]: <info>  [1641220720.3064] device (ttyUSB2): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
  Jan 03 15:38:40 manjaro-arm NetworkManager[387]: <info>  [1641220720.3158] policy: auto-activating connection 'Default' (b5430712-fceb-442d-b693-313065df922f)
  Jan 03 15:38:40 manjaro-arm NetworkManager[387]: <info>  [1641220720.3230] device (ttyUSB2): Activation: starting connection 'Default' (b5430712-fceb-442d-b693-313065df922f)
  Jan 03 15:38:40 manjaro-arm NetworkManager[387]: <info>  [1641220720.3247] device (ttyUSB2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  Jan 03 15:38:40 manjaro-arm gnome-calls[886]: New voice interface on existing origin with path `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm gnome-calls[886]: New voice interface on existing origin with path `/org/freedesktop/ModemManager1/Modem/0'
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/src/service.c:mms_service_set_country_code() Service Country Code set to CZ
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_connect_to_sms_wap() Watching for new SMS WAPs
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() Something May be wrong with the modem, checking....
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_STATE_DISABLED
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() Turning on Modem....
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/src/service.c:mms_service_set_country_code() Service Country Code set to CZ
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/src/service.c:vvm_service_set_country_code() Setting Service Country Code...
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/src/service.c:vvm_service_set_country_code() Setting Service Country Code...
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_modem_available() Attempting to autopopulate VVM carrier settings
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/src/service-providers.c:vvmd_service_providers_find_settings() mccmnc: 23003
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: Could not get modem number!
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_connect_to_sms_wap() Watching for new SMS WAPs
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_modem_available() Checking status of carrier subscription
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_check_subscription_status() Checking your carrier's VVM service
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/src/vvmutil.c:vvm_util_create_status_sms() VVM type: type_invalid
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: Unknown type of VVM service.
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() Something May be wrong with the modem, checking....
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() MM_MODEM_STATE_DISABLED
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() Turning on Modem....
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_connect_to_sms_wap() Watching for new SMS WAPs
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() Something May be wrong with the modem, checking....
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/src/service-providers.c:vvmd_service_providers_find_settings() mccmnc: 23003
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_STATE_DISABLED
  Jan 03 15:38:40 manjaro-arm vvmd[472]: Could not get modem number!
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() Turning on Modem....
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_connect_to_sms_wap() Watching for new SMS WAPs
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_modem_available() Checking status of carrier subscription
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_check_subscription_status() Checking your carrier's VVM service
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/src/vvmutil.c:vvm_util_create_status_sms() VVM type: type_invalid
  Jan 03 15:38:40 manjaro-arm vvmd[472]: Unknown type of VVM service.
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() Something May be wrong with the modem, checking....
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() MM_MODEM_STATE_DISABLED
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() Turning on Modem....
  Jan 03 15:38:40 manjaro-arm ModemManager[1635]: <info>  [modem0] state changed (disabled -> enabling)
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() Modem disabled
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_MODEM_DISABLED
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() Disabling Bearer Handler
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/src/service.c:mms_service_set_bearer_handler() service 0x556bf65b30 handler (nil)
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 3 New State: 5, Reason: 1
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() Something May be wrong with the modem, checking....
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_STATE_ENABLING
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() Modem disabled
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_MODEM_DISABLED
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() Disabling Bearer Handler
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/src/service.c:mms_service_set_bearer_handler() service 0x556bf65b30 handler (nil)
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() Modem disabled
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_MODEM_DISABLED
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() Disabling Bearer Handler
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/src/service.c:mms_service_set_bearer_handler() service 0x55791c5b30 handler (nil)
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 3 New State: 5, Reason: 1
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() Something May be wrong with the modem, checking....
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_STATE_ENABLING
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() Modem disabled
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_MODEM_DISABLED
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() Disabling Bearer Handler
  Jan 03 15:38:40 manjaro-arm mmsdtng[1322]: ../mmsd/src/service.c:mms_service_set_bearer_handler() service 0x55791c5b30 handler (nil)
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/src/service.c:handle_method_call_manager() At Get Services Method Call
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/src/service.c:handle_method_call_service() Retrieving all Messages...
  Jan 03 15:38:40 manjaro-arm mmsdtng[471]: ../mmsd/src/service.c:handle_method_call_service() No Messages!
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_MODEM_DISABLED
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_MODEM_DISABLED
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 3 New State: 5, Reason: 1
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() Something May be wrong with the modem, checking....
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() MM_MODEM_STATE_ENABLING
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_MODEM_DISABLED
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 3 New State: 5, Reason: 1
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() Something May be wrong with the modem, checking....
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() MM_MODEM_STATE_ENABLING
  Jan 03 15:38:40 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_MODEM_DISABLED
  Jan 03 15:38:40 manjaro-arm ModemManager[1635]: <info>  [modem0] simple connect started...
  Jan 03 15:38:40 manjaro-arm ModemManager[1635]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: Could not find settings: Operator ID '23003' not found in service provider database
  Jan 03 15:38:40 manjaro-arm vvmd[472]: vvmd[472]: Your VVM settings for are not in the database! Please file a merge request at https://gitlab.gnome.org/GNOME/mobile-broadband-provider-info so they can be added
  Jan 03 15:38:40 manjaro-arm vvmd[472]: Could not find settings: Operator ID '23003' not found in service provider database
  Jan 03 15:38:40 manjaro-arm vvmd[472]: Your VVM settings for are not in the database! Please file a merge request at https://gitlab.gnome.org/GNOME/mobile-broadband-provider-info so they can be added                                                                                                                                         
  Jan 03 15:38:41 manjaro-arm ModemManager[1635]: <info>  [modem0] power state updated: on
  Jan 03 15:38:41 manjaro-arm ModemManager[1635]: <info>  [modem0] 3GPP registration state changed (unknown -> idle)
  Jan 03 15:38:41 manjaro-arm ModemManager[1635]: <info>  [modem0] state changed (enabling -> enabled)
  Jan 03 15:38:41 manjaro-arm ModemManager[1635]: <info>  [modem0] simple connect state (5/8): register
  Jan 03 15:38:41 manjaro-arm NetworkManager[387]: <info>  [1641220721.6875] modem["ttyUSB2"]: modem state changed, 'enabling' --> 'enabled' (reason: user-requested)
  Jan 03 15:38:41 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 5 New State: 6, Reason: 1
  Jan 03 15:38:41 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 5 New State: 6, Reason: 1
  Jan 03 15:38:41 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 6
  Jan 03 15:38:41 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_READY
  Jan 03 15:38:41 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() Setting Bearer Handler
  Jan 03 15:38:41 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_get_all_sms() Searching for any new SMS WAPs...
  Jan 03 15:38:41 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 5 New State: 6, Reason: 1
  Jan 03 15:38:41 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 6
  Jan 03 15:38:41 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 6
  Jan 03 15:38:41 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() VVMD_MM_STATE_READY
  Jan 03 15:38:41 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
  Jan 03 15:38:41 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_mm_state() Setting Bearer Handler
  Jan 03 15:38:41 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
  Jan 03 15:38:41 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_get_all_sms() Searching for any new SMS WAPs...
  Jan 03 15:38:41 manjaro-arm mmsdtng[471]: ../mmsd/src/service.c:mms_service_set_bearer_handler() service 0x556bf65b30 handler 0x556bf09480
  Jan 03 15:38:41 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_get_all_sms() Searching for any new SMS WAPs...
  Jan 03 15:38:41 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 5 New State: 6, Reason: 1
  Jan 03 15:38:41 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 6
  Jan 03 15:38:41 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
  Jan 03 15:38:41 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
  Jan 03 15:38:41 manjaro-arm mmsdtng[1322]: ../mmsd/src/service.c:mms_service_set_bearer_handler() service 0x55791c5b30 handler 0x5579169480
  Jan 03 15:38:41 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_get_all_sms() Searching for any new SMS WAPs...
  Jan 03 15:38:42 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_get_all_sms() Adding timeout to vvmd_get_all_sms()
  Jan 03 15:38:42 manjaro-arm vvmd[472]: vvmd[472]: Modem is not ready to process any unsent/unreceived VVM messages.
  Jan 03 15:38:42 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_get_all_sms() Adding timeout to vvmd_get_all_sms()
  Jan 03 15:38:42 manjaro-arm vvmd[472]: Modem is not ready to process any unsent/unreceived VVM messages.
  Jan 03 15:38:43 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_messaging_list() Adding timeout to mmsd_get_all_sms()
  Jan 03 15:38:43 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_mm_get_messaging_list() Adding timeout to mmsd_get_all_sms()
  Jan 03 15:38:48 manjaro-arm mmsdtng[1322]: ../mmsd/plugins/modemmanager.c:mmsd_get_all_sms_timeout() Removing timeout to mmsd_get_all_sms()
  Jan 03 15:38:48 manjaro-arm mmsdtng[471]: ../mmsd/plugins/modemmanager.c:mmsd_get_all_sms_timeout() Removing timeout to mmsd_get_all_sms()
  Jan 03 15:38:48 manjaro-arm vvmd[472]: vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_get_all_sms_timeout() Removing timeout to vvmd_get_all_sms()
  Jan 03 15:38:48 manjaro-arm vvmd[472]: ../vvmd/plugins/modemmanager.c:vvmd_get_all_sms_timeout() Removing timeout to vvmd_get_all_sms()
  

• # nmcli d (v0.5.1)

  DEVICE         TYPE      STATE                 CONNECTION 
  wlan0          wifi      connected             myWiFi  
  ttyUSB2        gsm       connecting (prepare)  Default    
  p2p-dev-wlan0  wifi-p2p  disconnected          --         
  lo             loopback  unmanaged             --
  

• # nmcli d (v0.4.2)

  DEVICE         TYPE      STATE         CONNECTION 
  wlan0          wifi      connected     myWiFi  
  cdc-wdm0       gsm       connected     Default    
  p2p-dev-wlan0  wifi-p2p  disconnected  --         
  lo             loopback  unmanaged     --
  

The README states

Listen to AT Commands and blindly respond OK to everything not implemented (to make userspace happy)

Is there an overview somewhere which AT commands are fully/partially/not implemented? If not I think it would be helpful down the road to have a listing of that somewhere (maybe as a wiki entry?).

Possibly even with more detailed descriptions when a command might deviate from the original implementation, that way Quectel's AT command manual can still be used as a reference.

When I make a call for the first time after booting my Pinephone, it's 3G. I hear a regular ringback tone instead of the more boop sounding one. My friend called me back, and it was VoLTE, and then I made another call, and it was VoLTE.

Hello @Biktorgj,

On Manjaro ARM Phosh Developer image (updated daily) there's an issue of not having a dial-tone when placing a phone call.
I don't know if this issue is happening on other distro's as well, I suspect so because of this bug report [Callaudio Bug Report](https://gitlab.com/mobian1/callaudiod/-/issues/17) Firmware version which I was using is v0.42.
When restoring stock firmware the dial-tone appears on all placed phone calls again.
I tried this 3 times, to make sure it was no coincidence, but really a issue with the open firmware
What can I do to help you out in trying to figure out what might cause this issue

Greeings Jasper

I use PP as a home WiFi router i.e. at least ten hours a day.. (7x24 I wouldn't call it). With the 0.4.2 version I have not noticed any problems. 0.5.1 did not work at all, with 0.5.3 I have outages in hours. (At the moment I can not exclude the influence of the distribution - at the same time with the firmware I updated the system.)

Symptoms:

• Internet connection is lost (x SMS works)

• connection cannot be restored

  # nmcli c up Default 
  Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)
  
  # journalctl -xe NM_CONNECTION=8b8dd9a2-4612-4ba9-b578-97beb81bf656 + NM_DEVICE=cdc-wdm0
  Jan 26 12:08:33 manjaro-arm NetworkManager[388]: <warn>  [1643195313.3139] device (cdc-wdm0): Activation: failed for connection 'Default'
  Jan 26 12:08:33 manjaro-arm NetworkManager[388]: <info>  [1643195313.3171] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'ma>
  Jan 26 12:08:33 manjaro-arm NetworkManager[388]: <info>  [1643195313.3589] device (cdc-wdm0): Activation: starting connection 'Default' (8b8dd9a2-4612-4ba9-b578-97beb8>
  Jan 26 12:08:33 manjaro-arm NetworkManager[388]: <info>  [1643195313.3608] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'm>
  Jan 26 12:08:34 manjaro-arm NetworkManager[388]: <info>  [1643195314.4014] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed>
  Jan 26 12:08:34 manjaro-arm NetworkManager[388]: <info>  [1643195314.4091] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'manag>
  Jan 26 12:08:49 manjaro-arm NetworkManager[388]: <info>  [1643195329.3027] device (cdc-wdm0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-if>
  Jan 26 12:08:49 manjaro-arm NetworkManager[388]: <warn>  [1643195329.3150] device (cdc-wdm0): Activation: failed for connection 'Default'
  Jan 26 12:08:49 manjaro-arm NetworkManager[388]: <info>  [1643195329.3178] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'ma>
  Jan 26 12:11:37 manjaro-arm NetworkManager[388]: <info>  [1643195497.5397] device (cdc-wdm0): state change: disconnected -> unmanaged (reason 'removed', sys-iface-stat>
  Jan 26 12:11:59 manjaro-arm NetworkManager[388]: <info>  [1643195519.6419] manager: (cdc-wdm0): new Broadband device (/org/freedesktop/NetworkManager/Devices/6)
  Jan 26 12:11:59 manjaro-arm NetworkManager[388]: <info>  [1643195519.6455] device (cdc-wdm0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state>
  Jan 26 12:11:59 manjaro-arm NetworkManager[388]: <info>  [1643195519.6597] device (cdc-wdm0): modem state 'enabling'
  Jan 26 12:11:59 manjaro-arm NetworkManager[388]: <info>  [1643195519.6818] device (cdc-wdm0): state change: unavailable -> disconnected (reason 'none', sys-iface-state>
  Jan 26 12:13:08 manjaro-arm NetworkManager[388]: <info>  [1643195588.1492] device (cdc-wdm0): Activation: starting connection 'Default' (8b8dd9a2-4612-4ba9-b578-97beb8>
  Jan 26 12:13:08 manjaro-arm NetworkManager[388]: <info>  [1643195588.1512] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'm>
  Jan 26 12:13:09 manjaro-arm NetworkManager[388]: <info>  [1643195589.0195] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed>
  Jan 26 12:13:09 manjaro-arm NetworkManager[388]: <info>  [1643195589.0244] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'manag>
  Jan 26 12:13:24 manjaro-arm NetworkManager[388]: <info>  [1643195604.3052] device (cdc-wdm0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-if>
  Jan 26 12:13:24 manjaro-arm NetworkManager[388]: <warn>  [1643195604.3188] device (cdc-wdm0): Activation: failed for connection 'Default'
  Jan 26 12:13:24 manjaro-arm NetworkManager[388]: <info>  [1643195604.3219] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'ma>
  Jan 26 12:13:49 manjaro-arm NetworkManager[388]: <info>  [1643195629.3102] device (cdc-wdm0): Activation: starting connection 'Default' (8b8dd9a2-4612-4ba9-b578-97beb8>
  Jan 26 12:13:49 manjaro-arm NetworkManager[388]: <info>  [1643195629.3116] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'm>
  Jan 26 12:13:50 manjaro-arm NetworkManager[388]: <info>  [1643195630.0422] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed>
  Jan 26 12:13:50 manjaro-arm NetworkManager[388]: <info>  [1643195630.0476] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'manag>
  Jan 26 12:14:05 manjaro-arm NetworkManager[388]: <info>  [1643195645.3005] device (cdc-wdm0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-if>
  Jan 26 12:14:05 manjaro-arm NetworkManager[388]: <warn>  [1643195645.3129] device (cdc-wdm0): Activation: failed for connection 'Default'
  Jan 26 12:14:05 manjaro-arm NetworkManager[388]: <info>  [1643195645.3162] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'ma>
  Jan 26 12:14:05 manjaro-arm NetworkManager[388]: <info>  [1643195645.3784] device (cdc-wdm0): Activation: starting connection 'Default' (8b8dd9a2-4612-4ba9-b578-97beb8>
  Jan 26 12:14:05 manjaro-arm NetworkManager[388]: <info>  [1643195645.3806] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'm>
  Jan 26 12:14:06 manjaro-arm NetworkManager[388]: <info>  [1643195646.3268] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed>
  Jan 26 12:14:06 manjaro-arm NetworkManager[388]: <info>  [1643195646.3346] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'manag>
  Jan 26 12:14:21 manjaro-arm NetworkManager[388]: <info>  [1643195661.3035] device (cdc-wdm0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-if>
  Jan 26 12:14:21 manjaro-arm NetworkManager[388]: <warn>  [1643195661.3162] device (cdc-wdm0): Activation: failed for connection 'Default'
  Jan 26 12:14:21 manjaro-arm NetworkManager[388]: <info>  [1643195661.3194] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'ma>
  Jan 26 12:14:21 manjaro-arm NetworkManager[388]: <info>  [1643195661.3906] device (cdc-wdm0): Activation: starting connection 'Default' (8b8dd9a2-4612-4ba9-b578-97beb8>
  Jan 26 12:14:21 manjaro-arm NetworkManager[388]: <info>  [1643195661.3921] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'm>
  Jan 26 12:14:22 manjaro-arm NetworkManager[388]: <info>  [1643195662.3679] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed>
  Jan 26 12:14:22 manjaro-arm NetworkManager[388]: <info>  [1643195662.3803] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'manag>
  lines 65-103/103 (END)
  

Questions:

• Is there anything I should try before downgrading the firmware?
• I made some changes using AT commands while experimenting with GNSS. Are there any recommended values? (Can they be set in bulk?)
• The only way I can get to a working state is by restarting PP. (I tried restarting eg25-manager, ModemManager and NetworkManager 🥴) Is there a less drastic/more intelligent approach? 🙏

Seeing how this is not listed under 'Next steps' in the README, I figured I could submit it as a (humble) feature request. If for nothing else, you could shoot it down and let this issue serve as a warning to those following in my steps. :-)

As you have stated, the pinemodem does not need it, as audio is routed via i2s in that particular implementation. But those of us wanting to give this firmware a spin on other EG25-G implementations (plain USB), may not have that particular option.

Can I flash firmware ADSP 30.004.30.004 on 0.5.5?

[v@arcadia pinephone_modem_sdk]$ make kernel                                                                                    [5/4359]
mv /home/v/data/olimex/usb-glink/new_kernel_and_bootloader/pinephone_modem_sdk/yocto/build/conf/local.conf /home/v/data/olimex/usb-glink
/new_kernel_and_bootloader/pinephone_modem_sdk/yocto/build/conf/backup.conf                                                             
cp /home/v/data/olimex/usb-glink/new_kernel_and_bootloader/pinephone_modem_sdk/tools/config/poky/rootfs.conf /home/v/data/olimex/usb-gli
nk/new_kernel_and_bootloader/pinephone_modem_sdk/yocto/build/conf/local.conf                                                            
cd /home/v/data/olimex/usb-glink/new_kernel_and_bootloader/pinephone_modem_sdk/yocto && source /home/v/data/olimex/usb-glink/new_kernel_and_bootloader/pinephone_modem_sdk/yocto/oe-init-build-env && \
bitbake -c menuconfig virtual/kernel

### Shell environment set up for builds. ###

You can now run 'bitbake <target>' 

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'

Other commonly useful commands are:
 - 'devtool' and 'recipetool' handle common recipe tasks
 - 'bitbake-layers' handles common layer tasks
 - 'oe-pkgdata-util' handles common target package tasks
WARNING: Host distribution "arch" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    MACHINE=mdm9607 is invalid. Please set a valid MACHINE in your local.conf, environment or other configuration file.

is there a layer missing? maybe I missed something ...
any help is appreciated thanks

I downloaded this new release package, and extracted it's contents to study what was inside.
I'm using Manjaro ARM distro, so using Mobian kernel would not be right for my distribution.
If I'm correct the kernel is not included in the flash script provided in the installation package is it?
Do you really need the patched kernel for this modem firmware to work, or does stock kernel work as well for use with the standard sample rates?
Waiting for your reply.

Greetings Jasper

[Environment]
Hardware: PinePhone KDE CE with mainboard rev. 1.2b
OS: Manjaro ARM Phosh Beta 8
Software version: Modem Release 0.2.1 [Latest]
Provider used: Dutch cellular provider (Simpel)
Reproducibility rate: 100%

[Steps to reproduce]
Initial situation:
Latest Quectel stock modem with Simpel simcard inserted in PinePhone

1. Update the modem to @Biktorgj his released 0.2.1 firmware release following the exact instructions provided in the FLASHING docs.
2. After the fastboot reboot, the modem recovers perfectly and shows my network carrier "Simpel" next to the signal strength indicator.
3. Although the modem is recovered, telephony complains about no voice capable modem available so I've rebooted the complete system.
4. After reboot I'm able to place a call/answer a call using the Calls appliciation in Manjaro.
5. I placed a call to my wifes telephone and also called my PinePhone from my wifes telephone,

[Expected Result]
I would expect to hear a dial tone whenever I make a call to somebody.
When the other end answers the call I would expect them to hear me, and for me to hear them.
Whenever someone calls me and the phone rings, I pick up the call.
Now i would expect them to hear me, and for me to hear anything on the other end of the line.

[Actual Result]
Whenever i place the call to someone (in my case my wifes phone) I do not hear any dial tone in my earpiece, while my wifes telephone actually rings. Whenever I pick up the call, I'm not able to talk to the other end, and also am not able to hear anything from the other end. The call is initialized properly, as my phone shows the call timer counting, and also my wifes phone shows the call times counting.

Whenever I receive a call (also in my case my wifes phone), the phone rings properly and i'm able to answer this call. Again the call timers start counting on me and my wifes telephone, so I know the call is initialized. Although the call is initialized I'm not able to hear any audio from the other end, and the other end is not able to hear anything from my side.

[Severity]
High/Critical: Although everything else on the modem seems to work properly and the modem is in good shape, making proper calls is a important function of a modem. This is why I rate the severity high/critical.

If I can provide you with any more information, please let me know what information i can gather for you to triage the problem on this bug.

After having tried previous versions of this firmware successfully, I tried to flash 0.4.0 today, but the process failed at flashing the system partition (something about the device not existing, unfortunately I don't remember the exact error). MAYBE this happened because I had a systemd timer running that checks every minute the presence of /dev/ttyUSB2 and restarts eg25-manager if it's not there to bring the modem back up when it disappeared (happened a lot recently). Stupidly I forgot to disable the timer before flashing, so maybe this is related. Since then the modem is gone and I can't get it back. It still shows with lsusb, but other than that I can't get it back up. There is no /dev/ttyUSB2 and ModemManager complains that /dev/ttyUSB0 can't be handled. What I've tried so far:

• Flashing again: doesn't work. Fastboot is waiting for devices, nothing there apparently.

[the following steps according to this very helpful post]

• echo -ne "AT+QFASTBOOT\r" > /dev/ttyS2: nothing happens, no changes
• echo -ne "AT+ADBOFF\r" > /dev/ttyS2, echo -ne "AT+ADBON\r" > /dev/ttyS2 and echo -ne "AT+RESETUSB\r" > /dev/ttyS2: First time I tried it, /dev/ttyUSB2 showed up, but other than that nothing worked. The next times I tried it, not even that happened.
• Running this script from Mobian (I usually use Manjaro Phosh): The script doesn't work (anymore?) since the files it's trying to write to don't exist (/sys/class/gpio/gpio$n).
• Shorting the EDL pins and running qfirehose: After I finally managed to short the pins (had to solder a wire to one of them because I just couldn't get it to work otherwise) I ran ./qfirehose -f ./ from the recovery repo, but that didn't do anything. The command immediately finished without any output and nothing else happened.

Is there anything else I can try? Or something I misunderstood? It would be really nice to have a working modem again :D
Also thank you for this amazing work here!

Hello,
First of all a big thank you for your hard work providing us with an open source userspace for the pinephone modem.
I am facing some problems with r0.4.1, mobian, bookworm stable and 5.14 kernel

• Data disconnects and won't come back
• Modem disappears (but with 5.14 seems to be coming back after a while)
  Then everything is OK.
  I am aware that this could be also a modemmanager or networkmanager problem, but I need your expertise to assess that.
  All in all with 5.14 the whole system behavior seems to be better than with 5.13 but I have been testing this only for some hours until now. : )
  Let me know if you need any additional information.
  modem.txt
  openqti.log
  dmesg.txt

Hi.

Slightly off-topic issue, hope I can be forgiven.

I have been looking at options for desktop integrated (mobile) telephony for Linux. Purely "because we can" and because I thought it might be cool.

Hardwarewise, the pinemodem is a Quectel EG25-G modem. But it is my understanding that in the pinemodem case, call audio is routed via i2s, and not via a 'USB Audio Card' as the Quectel application note calls it. Is this correct, or just an issue of misinterpreting the available information?

So, bottom line, I wonder if a USB device which embeds the EG25-G:

1. can be set up for voice calling from a Linux desktop (given the right software and configuration)
2. will work with your SDK out of the box

I am also trying to figure out exactly what Quectel means by stating that VoLTE is optional for their solutions. Would you happen to have any insight here?

Other showstoppers to consider?

after excecuting

echo -ne "AT+ADBON\r" > /dev/ttyUSB2

device appears in adb devices but with

no permissions; see [http://developer.android.com/tools/device.html]

So the adb shell dont work. Any idea how to get into the modem?

I feel I need to go back to the stock firmware, can I just use fastboot like I did to flash yours? Or do I have to take the phone apart?

I didnt find how to make a feature request, so I write it here:

it would be great if the open firmware would support IMEI change.
The stock firmware can do it with the command: AT+EGMR=1,7,"wishedIMEI"

Hello @Biktorgj ,

You were hoping for some more user reports on modem usage on Ofono.
Today I flashed Plasma Mobile Development image, with 0.28 modem which was already running on my Phosh install.
To my surprise I found out the modem was in a broken state.
I then went back to the last known working modem (for me), which was 0.23.
I incrementally upgraded modem FW to 0.27, which broke the modem with ofono again.
Went back to version 0.26, which made it working again.
It seems the choice to only listen to service 0x1a works perfectly for Phosh related buids, but breaks everything for Ofono (Tested Plasma Mobile / Sailfish OS [Both Ofono])

Hi!
Thanks for your effort on this project!
I'd like to try this but I'm using Manjaro on my pinephone.
So my questions is what patches did you apply to the mobian kernel in order to work with this modem firmware?

Thanks in advance :)