after an update few days ago. I've restarted a phone and now I get screen locker broken message on screen, and attaching a monitor and keyboard I'm able to login to shell.

journalctl error messages shows me some some coredump errors with qt5 conflicts and glibc. And I find it a bit too hard to find any information on this as this is so complicated based on that where I should exactly ask about it freenode channel is gone but even there they just claim it's all about KDE plasmamobile being just GUI and some other distro specific issues its not their issue.

Then which forum/communication channel is about this ?

I find manjaro itself being heavily bearable distro.


Thing is that GUI updater is often broken and I did my updates via

pacman -Suy

I had similar broken kde plasma locker issue in slackware-current which was solved with

slackpkg install-new

now this phone is unusable and I'm having very hard time about these manjaro/arch specific things as I'm not an user of these distros even for computers.

My guess would be just to distrohop in some fashion.

But maybe someone had this issue and solved this ?

Hi,
I tried to install Manjaro on the eMMC on my PBP but didn't know that using the "erase" option to make a new partition table would leave the system broken.  To get the machine to turn on, I have to disable the eMMC with the hardware switch so that it will boot off the SD card.  I want to try the installation on the eMMC again, but after booting from SD card (flashed with the Manjaro xfce image from the manjaro site) with the eMMC switch off and then turning the eMMC switch back on, I still can't access the drive.  I tried running (as root):

------------------------------------
Quectel EG25-G hardware connection
------------------------------------


Studying page 15 of Pinephone's mainboard schematic for the modem

https://files.pine64.org/doc/PinePhone/P...ematic.pdf

we can see that we have a chip with 144 contacts where half of them are actually connected. Physically half of them are SMD pins around the chip and the rest are balls under the chip.

Most of the connected pins are electrical grounding while the rest are voltage power, data lines, sychronisation lines and antennae.

------------
Pins
------------

14-17 -----> go to the SIM

35, 47, 49 -----> are the antennae

---------------------------------
2 -----> BB-AP-READY |
4 -----> BB-DISABLE | -----> are controlling the power state of the modem and are driven by the eg25-manager
20 -----> BB-RESET |
21 -----> BB-PWRKEY |
--------------------------------

7 -----> is output power

57-60 -----> are battery power

71 -----> is the battery power for the USB

115 -----> is the test button

8, 9, 19, 22, 36, 46, 48, 50-54, 56, 72, 85-112 -----> are ground

24-27 -----> are the PCM audio interface

62 -----> is the ringing indicator

64-68 -----> is the UART interface

69, 70 -----> are the USB (+),(-) differential lines
--------------------------------

We further see that the PCM, UART and the AP_READY,DTR signals pass through TXB0104YZT chips which are DC voltage converters but without using the inverting technique.

The communication with the A64 SoC is achieved by connecting the

1) power control lines
2) UART
3) USB
4) PCM

to GPIO contacts of the A64 which can be easily accessed by the kernel for reading and writing operations.

The audio data for calls are transferred by connecting the PCM contacts of the modem to the GPIO contacts of the A64 and the processing is done by the sound module in the SoC which is interfaced by ALSA.

--------------------------
A64 GPIO pins
--------------------------

The datasheet for A64 is here

https://files.pine64.org/doc/datasheet/p...t_V1.1.pdf

As we can see in 4.2 (page 23), the GPIO pins are divided in categories with different capabilities denoted in the following way

PB0 - 9 -----> 10 pins
PC0 -16 -----> 17 pins
PD0 - 24 -----> 25 pins
PE0 -17 -----> 18 pins
PF0 - 6 -----> 7 pins
PG0 -13 -----> 14 pins
PH0 -11 -----> 12 pins
PL0 -12 -----> 13 pins

Total: 116 pins

------------------------------------
Operating Modes
------------------------------------

1) Normal Operation

a) Idle: Software is active. The module has registered on the network, and it is
ready to send and receive data.

b) Talk/Data: Network connection is ongoing. In this mode, the power consumption is
decided by network setting and data transfer rate.
--------------------
2) Minimum Functionality

Mode AT+CFUN=0 can set the module to a minimum functionality mode without removing
the power supply. In this case, both RF function and (U)SIM card will be invalid.
--------------------
3) Airplane Mode

AT+CFUN=4 or W_DISABLE# pin can set the module to enter airplane mode. In this
case, RF function will be invalid.
--------------------
4) Sleep Mode

The current consumption of the module will be reduced to the minimal level. During
this mode, the module can still receive paging message, SMS, voice call and
TCP/UDP data from the network normally.
--------------------
5) Power Down

Mode The power management unit shuts down the power supply. Software goes inactive.
The serial interface is not accessible. Operating voltage (connected to VBAT_RF and
VBAT_BB) remains applied.

You can easily switch between modes 1,2,3 by

`echo at+cfun=1,0 | sudo atinout - /dev/EG25.AT -`
`echo at+cfun=0,0 | sudo atinout - /dev/EG25.AT -`
`echo at+cfun=4,0 | sudo atinout - /dev/EG25.AT -`

mode 5 can be achieved with

`echo at+qpwd=1| sudo atinout - /dev/EG25.AT -`


------------------------------------
eg25-manager
------------------------------------

The source code of the manager can be found here

https://gitlab.com/mobian1/devices/eg25-manager

Studying the directory tree we can see 3 directories.

1) "data", contains configurations files in ".toml" format which are installed in `/usr/share/eg25-manager`

2) "src", contains the source code

3) "udev", contains standard udev rules for the modem

The "src" directory contains two types of files, the ".c" source code and the ".h" header files for the respective ".c" files.

We can see the following files

1) at.c/.h - renders the AT commands defined in the ".toml" configurations files

2) gpio.c/.h - for the communication with the GPIO interface of the A64

3) manager.c/.h - the eg25-manager

4) mm-iface.c/.h -  for the communication with distributions using the ModemManager service

5) ofono-iface.c/.h - for the communication with distributions using the ofono service

6) suspend.c/.h - provides the ability to suspend the modem to sleep

7) toml.c/.h - for processing the ".toml" cofiguration files

8) udev.c/.h - for processing the udev rules

------------------------------------
How it works
------------------------------------

The main sequence of the code starts in "manager.c" at

`int main(int argc, char *argv[])`

1) it initialises some data structures,
2) reads the configuration files,
3) initialises the gpio chips (1c20800.pinctrl & 1f02c00.pinctrl)
4) takes actions on the modem (power on/off, suspend, wake, sleep) by sending and reading signals to and from the modem pins

2 -----> BB-AP-READY
4 -----> BB-DISABLE
20 -----> BB-RESET
21 -----> BB-PWRKEY

As we can see in the "gpio.c" code those signals are send easily via the "gpiod" library by calling functions like

`gpiod_line_set_value(manager->gpio_out[GPIO_OUT_PWRKEY], 1);`

You can find more information on the "gpiod" library here

https://www.ics.com/blog/gpio-programmin...od-library

Attached Files

  Quectel_EG25-G_Hardware_Design_V1.4-edit.pdf (Size: 947.14 KB / Downloads: 669)

Hi!
I'm having problem to run GNSS receiver with RockPro64.
I'm using Quectel EC-25EU with 0.8dBI antenna. The card is connected via USB2.0 cable and LTE hat.
When I use short (10cm) USB cable the time to first fix (TTFF) is very high (around 2 minutes). I tested different cables with different placement of modem relative to rockpro64. I also tested modem with notebook when rockpro64 is running next to. There is strong correlation between TTFF and distance to rockpro64.
I do not know what is source of noise however I see on PCB that there are mounts for metal shielding. I tried to find shop where it can be bought but without success. Please let me know if there is something that can be used to shield.
I would be grateful for any tips to decrease noise level. I'm already using ferrite beads on usb cable. It is hard to tell if there is any difference in TTFF as is is not stable.

I am interested in developing software to contribute to the PinePhone project. Since Manjaro is the official distribution for PinePhone, I think it makes the most sense to start here. Does anyone have any suggestions about a good place to start that would be the most useful to the project?

A bit of background, I do not work in technology but I have been programming as a hobby for about 5 years.  I like to get into the weeds more than your average programming hobbiest, so I'm not shy about learning things like kernal or driver development (even though this would be new territory for me).  I'm mainly interested in seeing where contribution is needed the most in the medium/long term.  This would also be my first time contributing to an open source project, so apologies if this isn't the best approach to take.

Anyone know if there is a fix coming soon for the broken inbound SMS issue using the default chat app on Mobian? I tested it last week and it still was happening with the latest updates. Inbound used to work months ago just fine. I was using it a lot.

Pinebook Pro with ANSI (US) keyboard from the most recent batch. I received it in May and played with it for about a week but it's been sitting in a drawer ever since and deserves a better home. Like new condition, ships in original box with original charger.

215 shipped, payment via paypal

It seems to come back to this every few months or so: Just when I feel like my Mobian is getting great battery life, and is responsive 90% of the time I would get an update after which the phone rings after a long sleep and I cannot answer it no matter how I press the "answer" indicater.  At this point, the phone will either continue ringing and would also start vibrating/buzzing as if obssessed. I would have to press the power button for a long time for it to shut down.   Another scenerio (after another update) is that after the phone sleeps and a call comes in, I could pick up, but there's no sound. This time when i checked in the setting, it had gone to "Dummy Output" for the output, and nothing for the input.  Again, I would have to reboot.

Am i the only one in this cycle? I am still with 5.10. Am confused as to exactly what software I'm suppose to be using. what is phosh? what is wayland? what is flatpak? (these are all secret questions i feel i'm too dumb to ask

(skip to last edit to see solution, leaving all steps to make searching for solution easier)
I finally received my new 3/32 upgrade board for my pinephone.
I read the wiki and watched the video, and did the board swap.
It looks like it was not flashed with a bootloader at the factory?
Instead I see a LED flash from the back of the board when I insert the USB and then I lsusb I get

Quote:hmm, right, I can measure 416mA when wlan0 is up, and 505 mA when down, and 380mA when the driver is unloaded