Manjaro ARM Beta13 with Phosh (PinePhone)

ARM Releases
, ,
1

Manjaro ARM Beta13 of Phosh for PinePhone!

The Manjaro ARM project is proud to announce our thirteenth BETA release for the PinePhone running Phosh!

This image is running the 5.13 kernel from Megi, which is designed for the PinePhone.

Features:

  • Firefox uses a dedicated configuration and plays videos on Youtube pretty well
  • Camera app with access to back and front camera, including autofocus
  • Auto-Rotate function and manual rotate
  • Welcome wizard for easy setup of the device
  • We have now a working Torch in the quick-access-menu
  • Prime phone functions working, including resume from deep-sleep and free speaking
  • Recording of audio works
  • Most applications got added to scale-to-fit
  • Haptic feedback functions are given
  • Optimized keyboard layout for terminal
  • Maps working with geolocate
  • Volume buttons working
  • Sensors fully functional
  • Easy access to Bluetooth, Wlan, Rotate and Mobile functions via quick settings
  • Default branch is arm-stable. This can be changed by editing /etc/pacman-mirrors.conf
  • usage of callaudiod for better audio experience with calls
  • This image uses a Crust enabled uboot

Changes since Beta12

  • Pipewire got updated to 0.3.33
  • Most of the Gnome packages got updated to 40.4
  • We updated modemmanager to 1.18-rc1
  • NetworkManager is now at 1.24.0
  • siglo is now at 0.8.8
  • We use now upstream uboot 2021.07 with needed patches
  • More fixes to eg25-manager. There is also now a script to auto-restart the modem as needed.
  • Kernel is now at 5.13.12
  • Mesa got updated to 21.1.6
  • Phosh got updated to 0.12.1. Use the drop-down box to display also non-adaptive apps!
  • We additionally added some backports in regard of how we use the torch power management.
  • Calls is now a Gnome project. Therefore we adjusted to those changes. Due some issues with phosh 0.13 we have first to fix an issue before we can update to newer versions.
  • Some additional fixes to Squeekboard
  • regular package updates

A detailed list of package changes can be found here.

Currently broken:

  • GPS may not work as it should

Notice about firmware

Modemmanager was upgraded to 1.18rc1, and there are changes to how call notifications from the modem are handled on the Pinephone. As a result, some receiving calls may be missed. SMS/text messages are not affected by this. Alternative Firmware 0.3.1 seems not to be affected by this, however we are now working on a solution also for stock firmware. Before you change your firmware you may want to read this articel about Pinephone Modem Stack. Also the upcoming Beta15 might have needed fixes for the stock firmware.

Known issues

  • You may loose the modem often. If that is the case call systemctl edit --full ModemManager and then edit --test-quick-suspend-resume to become --test-no-suspend-resume
  • it may take longer to wake up from deep-sleep mode when a call is incoming. Most of the time that call will vibrate only.
  • after a deep sleep (more than 30 mins nothing happening on the phone) the phone might wake up due to an incoming call, but won’t ring. You only will get notified with a missed call, when the caller hangs up. You may want to flash Biktorgj’s Firmware 0.3.1 or later.
  • UI becomes unresponsive after a while.
  • Doing a recording may result in noisy audio savings
  • Lots of apps are still missing or are not mobile friendly yet.

Download:

Device Phosh
PinePhone Beta13
PinePhone Nightly

About the device:
PinePhone:
Perhaps you’re in a line of work where security is a must, or a hard-core Linux enthusiast, or perhaps you’ve just got enough of Android and iOS and you’re ready for something else – the PinePhone may be the next Phone for you. Powered by the same Quad-Core ARM Cortex A53 64-Bit SOC used in our popular PINE A64 Single Board Computer, the PinePhone runs mainline Linux as well as anything else you’ll get it to run.

The purpose of the PinePhone isn’t only to deliver a functioning Linux phone to end-users, but also to actively create a market for such a device, as well as to support existing and well established Linux-on-Phone projects. All major Linux Phone-oriented projects, as well as other FOSS OS’, are represented on the PinePhone and developers work together on our platform to bring support this this community driven device.

Order

Pinephones Beta Edition are still on stock. Visit the Pine64 Store

How to install:

Download the image/xz file from the download location. Verify that the download completed successfully.

After that, install Etcher (sudo pacman -S etcher if on Manjaro) and burn the to an SD card (8 GB or larger).

The PinePhone should recognize the SD card as a bootable device and boot from it.

The premade users are:
User: manjaro
Password: 123456

User: root
password: root

Donate!

Please consider supporting Manjaro ARM directly via Patreon, Ko-Fi or Open Collective.
You can also donate to our upstream, which is Arch Linux ARM.

Bugtracker

If you face issues with this editon, please open a new issue on our bug-tracker

Development Changelog

We will list our progress to Beta14 here

  • Beta13 (2021-08-23) Download
    • based on stable branch
  • Dev (2021-08-28) Download
    • based on unstable branch
    • pipewire got updated to 0.3.34
    • bluez is now at 5.61
    • firefox got renewed to 91.0.2
    • mesa is now at 21.2.1
    • we now use ngl as OpenGL render. This will make usage of MegaPixels faster
7 Likes
2

Just flashed the new beta from scratch (without updating previous version). Unfortunately, incoming calls are missed here in the same way as after recent update on Beta12. Without a possibility to answer calls, a phone is not a phone :frowning:

3

Is it necessary to flash the new beta in order to update, or just pacman -Syu?

4

Updating should be fine.

1 Like
5

after trying to update and with pacman -Syu or even pacman -Syyuu I got “no updates available”. Then I check my version with cat /etc/manjaro-arm-version and I got “pinephone - phosh - beta12. Can I do something else in order to update from beta 12 to beta 13? Or is it because it is still on phosh 12, then it outputs “beta12”, because I just check and I got all packages updated to this beta13 release, and as stated phosh 13 was not rolled yet " Due some issues with phosh 0.13 we have first to fix an [issue ]”.

6

The /etc/manjaro-arm-version just indicates what image you flashed to the device.

If you run an update, and it says “nothing to do”, that means you are already up to date. That’s how a rolling release works.

The Beta images are just snapshots of the installed packages at the time the image was created.

So if you flashed Beta 12 and have run all your updates, then you are on the same package versions as Beta 13.

7

Thanks for the explanation!

8

the same problem :face_with_raised_eyebrow:

9

All images I test for incoming and outgoing calls thru D1 network of German Telekom. Also SMS texting works for me. Depending on the carrier, there might be some issues. Maybe update the modem firmware.

10

According to comments in the bugtracker, this problem is reproduced only on the original modem firmware. But still I don’t want to update the firmware because it is a one-way ticket as I understood - there is no way to downgrade it back if something goes wrong. Or am I wrong? Unfortunately, Pine64 doesn’t ship to my country, so in case of bricking the device I’ll have to use mail forwarding service for ordering the new one and it will take up to 3 months, with a possibility of missing/stealing/damaging it on some stage.
Anyway, phone calls worked stably on the previous beta (but there were occasional missing SMS). Now SMS texting works ideally, but there are no incoming calls. If it would be possible to combine SMS algorithm from the current version with calls algorithm from the previous one…

11

It is recommended to update the modem firmware. Note that the Manjaro editions shipped with the latest firmware.

Find out if you need to upgrade your firmware

If you check the modem log with journalctl (-k = --dmesg, -g = --grep, ArchWiki, man page):

$ journalctl -k -g modem

and this warning shows:

[...] modem-power serial1-0: Your modem has an outdated firmware. Latest know version is EG25GGBR07A08M2G_01.002.07. Consider updating.

You can do that easily by flashing the factory test image. During the tests also the latest firmware will be flashed. Based on the Phone release you will find the Factory Images here. And here the Flashing guideline, if you want to do it manually.

Getting your current firmware version use: sudo mmcli -m any --command='AT+QGMR'

Before you begin

Please, take a minute to get a copy of the stock firmware here, and carefully read the README. If you don’t know understand what it says, or don’t know how to recover the firmware in case something goes wrong, avoid touching your modem!

Other sources:

1 Like
12

I was not able to update the firmware from the factory test image, so I tryed the other way manually. But I got this error:
git clone GitHub - Biktorgj/quectel_eg25_recovery at EG25GGBR07A08M2G_01.002.07
Clone in ‘EG25GGBR07A08M2G_01.002.07’ in corso…
fatal: repository ‘GitHub - Biktorgj/quectel_eg25_recovery at EG25GGBR07A08M2G_01.002.07’ non trovato

13

I can send/receive calls and send SMS text, but three days after starting service with Mint Mobile, I haven’t been able to receive and texts! (It was fine the first three days 12Aug21-14Aug21).

My modem firmware seems fine (per instructions above) and the OS is updated to beta13 (originally beta 12). I tried Mobian/Phosh (17May21 version) because the the wiki indicates that SMS texts work with it, but I have the same behavior with that distro.

Could I get some hints on where to look to begin to debug this?

14

A firmware in this case for the modem is a complete OS. Most current shipped Pinephones come with EG25GGBR07A08M2G_01.002.07. However a newer version called EG25GGBR07A08M2G_01.003.01.003. Both firmwares are more or less designed for the EG25 general usage and provided by Quectel. So based on the version shipped with earlier Pinephones and current ones, software might behave different. Beside software, also the latest hardware revisions have improvements. So a Manjaro Edition and a Beta Edition might be from the same 1.2 series, but the Beta might have slight hardware improvements than the older Manjaro batch.

The Pinephone as it is now is clearly a developer device and NOT recommended for the normal user!!!

You can tinker, you can use it and you have to be willing to experiment. I’m sure there will be a time of the Linux phone and then you can use it also as a daily driver. The hardware and software is also not the only ones here. The ISP or network carrier also plays a big role. If some things don’t work, change the carrier. Most use prepaid options to test if the network is good for the Pinephone or not. So look it up before you blame us with network issues: Carrier list.

Again, the EG25 Modem is not designed to be be put into a phone. It is more used in industrial devices or navigation systems. That is why the pine64 community is creating an alternative firmware especially designed for the Pinephone. It will give you lower heat, as the CPUs are not so high clocked up, longer battery life and other benefits, however, it is still a work in progress. So you have to be willing to adjust, to learn and follow up our developments.

And if you have an issue with our software, please report your issue in rich details.

1 Like
15

So I just checked my Manjaro Edition pinephone. It gives me that:

Welcome to Manjaro-ARM
~~Website: https://manjaro.org
~~Forum:   https://forum.manjaro.org/c/arm
~~Matrix:  #manjaro-arm-public:matrix.org
[manjaro@manjaro-arm ~]$ sudo mmcli -m any --command='AT+QGMR'
[sudo] password for manjaro: 
response: 'EG25GGBR07A08M2G_01.001.01.001'

A line like this you won’t find, as we no longer use modem-power driver by Megi:

modem-power serial1-0: Your modem has an outdated firmware. Latest know version is EG25GGBR07A08M2G_01.002.07. Consider updating.

This means the phone I’ve here has an older firmware for the modem.

An older PostmarketOS Pinephone I already had updated to

response: ‘EG25GGBR07A08M2G_01.002.01.002’

So both modems behave slightly differently based on the used firmware. So it is recommended to dump the current used firmware before updating to a newer one.

If the version number is 01.001.01.001 (EG25GGBR07A08M2G_01.001.01.001) it is recommended to update the firmware to version 01.002.01.002 (EG25GGBR07A08M2G_01.002.01.002) due to various bug fixes.

To check which PP model Hardware Revision you have you can do a: cat /proc/device-tree/model. 1.1 is the Braveheart and 1.2 is a Community or Beta PinePhone. However Community editions have subversions like 1.2, 1.2a, 1.2b. Those might have additional hardware fixes.

Also I’ve to correct myself: Booting a factory test image will automatically flash the ANX7688 chip, which has nothing to do with the modem firmware. However, seems newer Factory Test Images now are able to flash the modem as mentioned here.

16

Seems we hijack this thread to be a discussion about modem firmware :grinning_face_with_smiling_eyes:

Even with the 002 firmware, it’s more or less buggy. so, none of the firmwares are totally stable.

17

Here is one reason why you should update to 01.002 at least:

Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="fast/poweroff"
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Response: [ERROR]

The 01.001 version doesn’t support that new feature, as it was added in 01.002 firmware.

Here a short snippet of the log for eg25-manager:

[manjaro@manjaro-arm ~]$ journalctl -b | grep eg25
Aug 29 11:48:49 manjaro-arm systemd[1]: /usr/lib/systemd/system/eg25-manager.service:15: Unknown key name 'ProtectedKernelModules' in section 'Service', ignoring.
Aug 29 11:48:49 manjaro-arm systemd[1]: /usr/lib/systemd/system/eg25-manager.service:20: Failed to parse /proc/ protection mode, ignoring: true
Aug 29 11:48:49 manjaro-arm systemd[1]: /usr/lib/systemd/system/eg25-manager.service:21: Unknown key name 'ProtectDevices' in section 'Service', ignoring.
Aug 29 11:48:49 manjaro-arm systemd[1]: /usr/lib/systemd/system/eg25-manager.service:26: Unknown key name 'ProtectKernelLog' in section 'Service', ignoring.
Aug 29 11:48:54 manjaro-arm eg25manager[3830]: Opening config file: /usr/share/eg25-manager/pine64,pinephone-1.2.toml
Aug 29 11:48:54 manjaro-arm eg25manager[3830]: Starting modem...
Aug 29 11:48:55 manjaro-arm eg25manager[3830]: Executed power-on/off sequence
Aug 29 11:48:55 manjaro-arm eg25manager[3830]: taking systemd sleep inhibitor
Aug 29 11:48:55 manjaro-arm dbus-daemon[3827]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.7' (uid=0 pid=3830 comm="/usr/bin/eg25manager ")
Aug 29 11:48:55 manjaro-arm eg25manager[3830]: oFono vanished from D-Bus
Aug 29 11:48:55 manjaro-arm eg25manager[3830]: inhibitor sleep fd is 21
Aug 29 11:48:58 manjaro-arm eg25manager[3830]: ModemManager appeared on D-Bus
Aug 29 11:49:05 manjaro-arm eg25manager[3830]: Response: [RDY]
Aug 29 11:49:05 manjaro-arm eg25manager[3830]: taking systemd sleep inhibitor (blocking)
Aug 29 11:49:05 manjaro-arm eg25manager[3830]: inhibitor block fd is 22
Aug 29 11:49:05 manjaro-arm eg25manager[3830]: Response: [+CFUN: 1]
Aug 29 11:49:06 manjaro-arm eg25manager[3830]: Response: [+CPIN: READY
Aug 29 11:49:08 manjaro-arm eg25manager[3830]: Response: [+QIND: SMS DONE]
Aug 29 11:49:08 manjaro-arm eg25manager[3830]: Response: [+QIND: PB DONE]
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager object `/org/freedesktop/ModemManager1/Modem/0' added
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp.ProfileManager' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Firmware' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Time' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Voice' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Adding new modem `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Sending command: AT+QGMR
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Messaging' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Signal' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Location' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Adding new modem with location capabilities `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: ModemManager interface `org.freedesktop.ModemManager1.Modem.Simple' found on object `/org/freedesktop/ModemManager1/Modem/0'
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Response: [EG25GGBR07A08M2G_01.001.01.001
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Sending command: AT+QDAI?
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Response: [+QDAI: 1,1,0,1,0,0,1,1
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="risignaltype"
Aug 29 11:49:15 manjaro-arm eg25manager[3830]: Response: [+QCFG: "risignaltype","physical"
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="ims"
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Response: [+QCFG: "ims",1,1
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="apready"
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Response: [+QCFG: "apready",1,0,500
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="urc/ri/ring"
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Response: [+QCFG: "urc/ri/ring","pulse",120,1000,5000,"off",1
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="urc/ri/smsincoming"
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Response: [+QCFG: "urc/ri/smsincoming","pulse",120,1
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="urc/ri/other"
Aug 29 11:49:16 manjaro-arm eg25manager[3830]: Response: [+QCFG: "urc/ri/other","off",1,1
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="urc/delay"
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Response: [+QCFG: "urc/delay",0
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="urc/cache"
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Response: [+QCFG: "urc/cache",0
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="urc/ri/pin"
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Response: [+QCFG: "urc/ri/pin",uart_ri
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Sending command: AT+QURCCFG="urcport"
Aug 29 11:49:17 manjaro-arm eg25manager[3830]: Response: [+QURCCFG: "urcport","all"
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Sending command: AT+QSCLK=1
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Response: [OK]
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Sending command: AT+QGPSXTRA?
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Response: [+QGPSXTRA: 1
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Sending command: AT+QGPSCFG="gnssconfig"
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Response: [+QGPSCFG: "gnssconfig",4
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Sending command: AT+QGPSCFG="odpcontrol"
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Response: [+QGPSCFG: "odpcontrol",0
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Sending command: AT+QGPSCFG="dpoenable"
Aug 29 11:49:18 manjaro-arm eg25manager[3830]: Response: [+QGPSCFG: "dpoenable",1
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Sending command: AT+QGPSCFG="gpsnmeatype"
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Response: [+QGPSCFG: "gpsnmeatype",31
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Sending command: AT+QGPSCFG="glonassnmeatype"
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Response: [+QGPSCFG: "glonassnmeatype",7
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Sending command: AT+QGPSCFG="galileonmeatype"
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Response: [+QGPSCFG: "galileonmeatype",0
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Sending command: AT+QGPSCFG="beidounmeatype"
Aug 29 11:49:19 manjaro-arm eg25manager[3830]: Response: [+QGPSCFG: "beidounmeatype",0
Aug 29 11:49:20 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:20 manjaro-arm eg25manager[3830]: Sending command: AT+QGPSCFG="autogps"
Aug 29 11:49:20 manjaro-arm eg25manager[3830]: Response: [+QGPSCFG: "autogps",0
Aug 29 11:49:20 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:20 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="fast/poweroff"
Aug 29 11:49:20 manjaro-arm eg25manager[3830]: Response: [ERROR]
Aug 29 11:49:20 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:20 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="fast/poweroff"
Aug 29 11:49:21 manjaro-arm eg25manager[3830]: Response: [ERROR]
Aug 29 11:49:21 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:21 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="fast/poweroff"
Aug 29 11:49:21 manjaro-arm eg25manager[3830]: Response: [ERROR]
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="fast/poweroff"
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Response: [ERROR]
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Command QCFG retried 4 times, aborting...
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="sleepind/level"
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Response: [+QCFG: "sleepind/level",0
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="wakeupin/level"
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Response: [+QCFG: "wakeupin/level",0
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Got a different result than expected, changing value...
Aug 29 11:49:22 manjaro-arm eg25manager[3830]: Expected: [0,0]
Aug 29 11:49:23 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:23 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="wakeupin/level",0,0
Aug 29 11:49:23 manjaro-arm eg25manager[3830]: Response: [ERROR]
Aug 29 11:49:23 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:23 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="wakeupin/level",0,0
Aug 29 11:49:23 manjaro-arm eg25manager[3830]: Response: [ERROR]
Aug 29 11:49:24 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:24 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="wakeupin/level",0,0
Aug 29 11:49:24 manjaro-arm eg25manager[3830]: GNSS assistance upload started...
Aug 29 11:49:24 manjaro-arm eg25manager[3830]: GNSS assistance upload step (1/9): disabling GNSS engine through ModemManager
Aug 29 11:49:24 manjaro-arm eg25manager[3830]: GNSS assistance upload step (2/9): disabling GNSS engine through AT+QGPS
Aug 29 11:49:24 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:24 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="wakeupin/level",0,0
Aug 29 11:49:24 manjaro-arm eg25manager[3830]: Response: [ERROR
Aug 29 11:49:25 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:25 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="wakeupin/level",0,0
Aug 29 11:49:25 manjaro-arm eg25manager[3830]: Response: [ERROR]
Aug 29 11:49:25 manjaro-arm eg25manager[3830]: Command QCFG retried 4 times, aborting...
Aug 29 11:49:25 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:25 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="ApRstLevel"
Aug 29 11:49:25 manjaro-arm eg25manager[3830]: Response: [+QCFG: "ApRstLevel",1
Aug 29 11:49:25 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:25 manjaro-arm eg25manager[3830]: Sending command: AT+QCFG="ModemRstLevel"
Aug 29 11:49:25 manjaro-arm eg25manager[3830]: Response: [+QCFG: "ModemRstLevel",1
Aug 29 11:49:26 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:26 manjaro-arm eg25manager[3830]: Sending command: AT+QGPS?
Aug 29 11:49:26 manjaro-arm eg25manager[3830]: Response: [+QGPS: 0
Aug 29 11:49:26 manjaro-arm eg25manager[3830]: Executed soft sleep sequence
Aug 29 11:49:26 manjaro-arm eg25manager[3830]: GNSS assistance upload step (3/9): fetching assistance data
Aug 29 11:49:26 manjaro-arm eg25manager[3830]: GNSS assistance data contains 0 bytes,check network connection.
Aug 29 11:49:26 manjaro-arm eg25manager[3830]: Rescheduling upload because of failure in 30s
Aug 29 11:49:56 manjaro-arm eg25manager[3830]: GNSS assistance upload started...
Aug 29 11:49:56 manjaro-arm eg25manager[3830]: GNSS assistance upload step (1/9): disabling GNSS engine through ModemManager
Aug 29 11:49:56 manjaro-arm eg25manager[3830]: GNSS assistance upload step (2/9): disabling GNSS engine through AT+QGPS
Aug 29 11:49:56 manjaro-arm eg25manager[3830]: Executed soft wake sequence
Aug 29 11:49:56 manjaro-arm eg25manager[3830]: Sending command: AT+QGPS?
Aug 29 11:49:56 manjaro-arm eg25manager[3830]: Response: [+QGPS: 0
18

My PinePhone CE Manjaro /w Phosh (Convergence) was updated to beta13.

So here are my findings so far:

  1. I have noticed something really weird- while in the middle of a call, the call get disconnected and my phone no longer show any sign of reception (reception bar on the top left side of the screen is empty),
    Even waiting on it to come back yielded no results, after a device restart the reception signal is back - but once again I call the guy back, we continue our conversation and randomly the same happens again.

  2. second issue is audio quality on calls, the person on the other side of the call was saying that my voice is not clear and the audio is pretty “weak”.

any clue?

19

I have a similar problem, did you put your sim card on an android device with the “chat function” under sms activaed? I ask that because I did it, and today a friend sent an sms, my sim card was on the pinephone, but I received the sms on my android without any simcard, obvioulsy it arrived because the android was connect to the internet with “chat function” on.

20

Yes, that was discussed on the arch arm chat a few months ago, and they also recommend stay with 01.002, by your previous post I thought there was something now. From my experience who has a lower than 01.002 firmware version, updating from pine64 wiki is super easy. I disagree with you that it is experimental and cannot be used as daily driver, I am not an expert but an enthusiast and have been using the device everyday for the last 4months, and manjaro phosh for the last month, and everything I need works fine and is getting better with time, like wine. Thanks for the great work.