First, let me explain what has happened. I have had my pinephone (not pro, this one https://pine64.com/product/pinephone-bet...e-package/) for almost a year. Most of that time I haven't used it. About 3 weeks ago, I brought it back out of storage because I wanted to play around with it again. It still had the manjaro kde-plasma default install on it. Took an upgrade to get it actually functional, but no big deal (although it was rather clunky and laggy, but its a pinephone).

About a week ago, it crashed, and I tried to reboot it (I think it was the same screen that I'll mention below, but I can't remember for sure). However, the phone would not reboot. The led would come on (i.e. a mixture of green/yellow/red, and depending on the angle you're can isolate each color of the led), the screen never turned on, and I never got the vibrate that has accompanied the phone when it turns on. I messed with it for a couple hours, decided I needed to get off of the garbage factory install, and planned to install a new os.

Two days ago, I tried it again, just to see what would happen. . . and it turned on. So I'm thinking, oh, it was never a problem to begin with. However, yesterday morning I try to turn it on and . . . it doesn't turn on. I fought with it most of the day yesterday and couldn't turn it on. Spend several hours on the irc chat with no results (trying to install manjaro phosh, but the phone wouldn't boot at all). So I gave up and went to work out.

When I came back last night I COULD TURN ON MY PHONE AGAIN. In fact, I was actually able to install manjaro phosh. I couldn't make calls or send texts like I could with the factory install, but I had to mess with the settings on the factory install to get calls, texts, and data working too. However, after about a half hour or so the phone crashed (i.e. the screen mentioned earlier). The screen turned mostly white but had these very thin, fine black vertical lines. I tried to turn the phone off and back on again, but it won't turn on. I haven't been able to get the phone turned on since, but I'm sure it'll work here shortly. . .

Here is what I've tried, both through my efforts and the irc:

1) I have a pinephone (not pro) https://pine64.com/product/pinephone-bet...e-package/
2) I've tried charging it through my computer and a 5v/2.4 amp charger (this charger has been working in the past, but maybe something happened?)
3) I've installed a new distribution (manjaro phosh https://github.com/manjaro-pinephone/pho...a24.img.xz is the image I installed)
4) I've begun to take the phone apart to look for loose connections. I did think to use a multimeter on the battery. The battery is outputing 3.63 volts (says its rated for 3.8) so maybe the battery is dead? But if that were the case, then why won't the phone boot up when connected to the wall without the battery?
5) when I plug the battery in and check the contacts opposing the battery on the phone, I'm still getting 3.63 volts on the battery. It does indeed appear to me that when plugged in the phone does not charge at all, but I have absolutely no clue why.
6) I have created an SSD with pine64-pinephone-charging.img.xz. Apparnetly, this image isn't for booting, but only for allowing your phone to charge. The led is supposed to turn red when the battery is under 5%, yellow when its >5% but <%50, and green when >%50. However, when I put the charging image sd card in and then plug the phone to a charger (I have used several different chargers and my computer, none of them works) in the led does not come on. I cannot get the led to come on by pushing the power button (when the charging sd card is inserted). The led will come on (as described above) when I take out the charging image sd card and either try to power on or plug into a charger.

What am I missing? The fact that the phone will work after sitting idle for an unspecified time (but not all the time, because I let it sit overnight) tells me that there's some issue with it, but it potentially remains functional. I have not seen any loose connections from taking it apart, but I could be missing something (if someone would have a better idea of where to check). I'm going to do another visual inspection tonight when I get home from work.

Anyway, thank you for any help that anyone has to give. I'm at a loss at the moment. Sorry if I'm too detailed here, but since the problem seems nebulous I figure no fact can be determined to be irrelevant at this point.

Hello. I receive the following error while trying to update software in Manjaro using Add/Remove Software:

Invalid or corrupted database (PGP signature)
Failed to synchronize databases

If anyone is able to advise I’d be grateful. I’m pretty inexperienced when it comes to Linux.

I'm trying to install Debian on the emmc. I've tried building an image from the firmware and partition images here https://deb.debian.org/debian/dists/bull...rd-images/ and here https://d-i.debian.org/daily-images/arm6...rd-images/.

In both cases no network interfaces are detected at all and it appears wifi drivers are missing, meaning I can't complete the install.

Is it expected that those images don't contain the driver? (I thought the netboot spin included non-free?). What is the best way of getting that driver? Is there another image I should be using?

Have the Pine team thought about designing a doorbell camera that can store images in the not-cloud?  Ring et al seem like horrible, privacy destroying options.  A device that is fully under the owner's control would be amazing!

Out of the box, when Manjaro is started, updates and software installs all fail because there are four missing  (outdated) GPG keys.  

I have seen several posts by other users who are understandably frustrated with this, and give up.  Finding and installing the keys from .zst files is just possible for three of them, though very UNdesirable for security reasons.  The fourth key is impossible to find, effectively making this Manjaro useless for most people.

Example;
------------------------------------
Apply transaction ? [y/N] y
Resolving dependencies...
Checking inter-conflicts...
Checking keyring...                                                                                      [1/1]
Downloading required keys...
Error: key "084A7FC0035B1D49" could not be looked up remotely
Error: required key missing from keyring
Error: Failed to commit transaction

-------------------------------------

HOWEVER, there is a simple solution which solves this!  $ sudo systemctl start pacman-init ...

--------------------------------
$ sudo systemctl start pacman-init
[sudo] password:


$ sudo pacman -Syu tor
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Some packages should be upgraded first...
resolving dependencies...
looking for conflicting packages...

Packages (1) manjaro-keyring-20220514-2

Total Installed Size:  0.71 MiB
Net Upgrade Size:      0.63 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                    [####################################] 100%
(1/1) checking package integrity                                  [####################################] 100%
(1/1) loading package files                                        [####################################] 100%
(1/1) checking for file conflicts                                  [####################################] 100%
(1/1) checking available disk space                                [####################################] 100%
:: Processing package changes...
(1/1) upgrading manjaro-keyring                                    [####################################] 100%
==> Appending keys from manjaro.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signed 1 keys.
==> Importing owner trust values...
==> Updating trust database...
gpg: next trustdb check due at 2022-09-22
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

:: Starting full system upgrade...
:: Replace kwayland-server with extra/kwin? [Y/n]

------------------------------------------

Once updated, Manjaro is actually a quite slick and useful OS, and EVERYTHING JUST WORKS on the Pinebook Pro.

For those unaccustomed to the Aarch Linux command line oddities, here is a CLI "cheat sheet" for you;

https://dpaste.com/BRSGKX59U

This will save you a good deal of time.

My carrier is T-Mobile USA. On 2022-08-08 (six days ago) I stopped receiving texts, though I did not realize it until 2022-08-12 (yesterday).
During that time, texts I sent were received, and phone calls worked, both incoming and outgoing.
I am certain that I did not change anything (software, firmware, etc.) around the time SMS Receive stopped working.

Today I tried several things to solve the problem, but the one that finally worked was switching ADSP firmware to 30.006.30.006.
After that, I received missing texts.

Pine and the distro makers have unfortunately "jumped the shark"
by trying to offer phones that might someday be competitive with Android/iOS i.e.
fast, responsive, good for gaming, amazing camera etc.

But this is not really what a Linux user wants. A Linux user wants different things from
the majority of users.
He wants:
1. to tinker first and foremost, configuring the phone in novel ways, starting with a functional phone not one with broken software;
2. to achieve privacy, and feel assured his data won't be exfiltrated to "the cloud", and use apps like Signal for Internet calling;
3. to write code for the phone, maybe write code on the phone itself.

But to gain adoption by Linux users the phone has to be able to
1. make calls reliably,
2. do SMS reliabily
3. and charge normally.

These 3 things should have been the top priority of Pine and the distro makers, but seem to have not been.

The distro makers apparently want to provide a nearly identical
experience and feature set to mainstream phone OSes (why?), and they have
loaded their GUIs down with bloated/slow software, rather than writing lean and fast
code using the bare bones approach e.g. with Xlib alone.

It is no big surprise that phones feel slow when they are using
KDE plasma or Python apps.

Pine for its part has failed to provide the basic hardware setup of a phone that:
A. charges normally without having to ever take out the battery;
B. has an EEPROM to store calibration data. They don't perform camera calibration at the factory
like ever other phone maker does, which means the camera
will never be calibrated because that can't be done at home.

In short, the Pine phones are a misfire, not conceived with the customers' needs in mind,
with bad distros brought by organizations not committed to the task and instead
committed to the wrong goals.

I just received my new pinebook pro in 08/2022. After installing the ARM Manjaro Gnome desktop OS to eMMC booting from Manjaro SD card, the PBP started with the new OS. After a couple of system starts, the PBP booted showing the u-boot screen, then showed a blinking cursor in the upper left corner and just stopped with a green-orange-blinking power LED. This has not changed since then. The following paragraphs describe my attempts to fix the problem.

I tried booting from SD card (the same card that worked before) but it doesn't work anymore. I tried different Linux distros to create a bootable SD card using Balena Etcher, e.g. Manjaro Gnome/xfce/KDE and Armbian (new and older versions).

After that, I opened the back cover to check the eMMC switch (no. 24 regarding the PBP wiki). But the new PBP does not have the switch as described. There is another switch (turned by 90 degrees to the original one) which is covered/sealed by a transparent material. I compared the switch to my other PBP (2020 model) and it looks different in my new PBP.

Using a USB eMMC adapter, I flashed several Manjaro and Armbian linux distros on the eMMC and inserted it back into the PBP. My PBP does not boot anymore: not with the eMMC and not with a bootable SD card.

When I insert the eMMC of my old PBP, the PBP boots to an older Manjaro KDE plasma. Keeping the old eMMC in the PBP, I tried to boot from SD card to flash a newer distro to the old eMMC. But it did not work. The PBP only starts from the old eMMC and not from any inserted bootable SD card. The problem with the old eMMC is that wifi is not working (not showing any networks). I do not dare flashing the old eMMC using the USB eMMC adapter...

Is it possible that the new eMMC has a failure and how can I check?

I read a lot of threads in the forum, on reddit and other web sources but all described steps and tips did not work for me. Is there a better way to flash a linux distro with u-boot etc. to eMMC? I also read that it is possible to boot the PBP without eMMC. That does not work with my PBP. Has this changed with the new model? I highly appreciate any tips and hints on how to proceed with my new PBP.

fresh install on danctnix's phosh Arch image everything works as normal except none chatty notifications.

I have extended the feedbackd config to sound on missed as well as new sms and IM these work as inconsistently.

if the screen is locked and no existing (dino-im in this case) notifications have sounded then the sms sound plays (the screen doesn't turn on)

if I am in different app screen on no sound is played notification is displayed.

if a voice/video call comes through on the app no sound is played regardless of state, visual notification is displayed.

have tested incoming call event with fbcli and chatty both work (chatty also turns on screen).
below is a capture of the dbus event it appears to invoke incoming-call sound but no audio ring is played the screen doesn't turn on.

any ideas where I should look next ?

signal time=1660509632.125137 sender=org.freedesktop.DBus -> destination=:1.90 serial=2 path=/org/freedesktop/DBus;
  string "Dino"
  uint32 0
  string ""
  string "SENDERADDRESS"
  string "Incoming call"
  array [
      string "default"
      string "Open conversation"
      string "reject"
      string "Reject"
      string "accept"
      string "Accept"
  ]
  array [
      dict entry(
        string "sound-name"
        variant            string "phone-incoming-call"
      )
      dict entry(
        string "urgency"
        variant            byte 2
      )
      dict entry(
        string "image-path"
        variant            string "call-start-symbolic"
      )
      dict entry(
        string "desktop-entry"
        variant            string "im.dino.Dino"
      )
  ]
  int32 0

Hi,
What is the status of being able to make reliable calls on the PP and PPpro?
By reliable I mean:
- Calls go through
- Calls are not disconnected for no reason
- Audio levels are fine (sending and receiving).
- Both parties can hear each other.
Thanks.