I did an update tonight (2021 Jun 23) and the chatty app stopped working.
Code:
$chatty
$chatty: symbol lookup error: chatty: undefined symbol: _ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protobuf5ArenaE
I had to downgrade these packages to make it work again.
Code:
boost-libs-1.76.0-1 to boost-libs-1.75.0-3
evolution-data-server-3.40.2-2 to evolution-data-server-3.40.0-2
libphonenumber-8.12.25-1 to libphonenumber-8.12.21
protobuf-3.17.3-1 to protobuf-3.15.8-1-
I am not sure where to report this issue, but this post did help me.
EDIT:
As of 2021 Jun 24 this is no longer an issue with the update of chatty to chatty 0.3.1-2
I'm an "enthusiast" grade user and need some advice. I'm running the latest Beta edition of Manjaro ARM with Phosh and I need to install a Whatsapp client on it. Has anyone here done this successfully? Any pointers or better would be greatly appreciated. TIA.
Since writing I found this, but the commands aren't suitable for Arch Linux. Can someone please help me with the appropriate commands for installation, if it's possible? Many thanks.
Hi,
Truth: I am in deep, way over my head. If another forum is better suited for help questions, please let me know.
Admiring the mission, and needing to to better understand linux, I purchased several products in hopes to dive into learning linux for work. My PBP has been a great tool but I am having issues with my phone. When it first arrived I was able to use phone, text, and wifi. A had a few issues the first day. phone service would blink out and back in, power/battery indicator not correct (or the phone would randomly turn off), and it would occasionally freeze and a restart would be necessary. I started getting error messages about modem and the phone wifi and data stopped working and occasionally the sim is not recognized. I tried updates the same issues occurred. I thought maybe some of the issues could have been from bad sim adaptor and put the phone away until I could get a new one. I picked up a new adaptor today and installed sim into phone. The phone service seems to be working better but not data. My big issue now is my pin is not working and the reset button does not reset. The phone will also power down/turn off when showing a full charge. Any advice or direction would be greatly appreciated.
recap:
1. modem/data and service issues
2. freezing and random turnoff
3. login (pin) reset not working
My name is Leonardo and working together with my brother Marco we wrote a very rudimentary Compass app for the Pinephone with Python. To our knowledge, there is no such app available to date. Check the screenshot at the bottom.
We have tested the app in Phosh (Manjaro, Mobian and postmarketOS) and Plasma Mobile (Manjaro). For the moment it only works with "old" (a.k.a. pre-beta edition) Pinephones, which have the original magnetometer chip LIS3MDL. If it is not found, it will just display randomly generated values.
Currently the app is a proof of concept and not intended for daily-driving. That being said, you can get it and try it from
For best results, follow the suggestion in the Readme about changing the Sampling Frequency of the magnetometer. Take also into consideration the issue of calibration. We will try to come up with a tool to automatize these tweaks in the future.
We hope the app can be useful to some people. We intend to improve it over time, and of course, we are open to constructive criticism and contributions! Keep in mind though, that this is our first open source project, so please be kind.
Enjoy!
Changelog:
v0.3.1
* Preliminary support for the AF8133J magnetometer (Pinephone Beta edition). Needs custom kernel driver and patches.
* Advertise the app to Phosh as adaptive.
v0.3
* Complete project refactoring:
- Installation now handled by meson build system
* Complete GUI overhaul in GTK3 with:
- Magnetic field readings now shown under the compass card.
- Settings window with graphical calibration tool
- Dark/light theme switch
- About window
v0.2
* Automatic changing of the sampling frequency
* Calibration tool
* Major code refactoring
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 ?
Currently based on this docummentation I'm switching to unstable and doing full upgrade. At least something is being done few times per day there
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):
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 |
--------------------------------
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.
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.
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
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.
![[Image: screenshot.png]](https://gitlab.com/lgtrombetta/pinephone-compass/-/raw/main/data/screenshot.png)
