When I plug into PPP's USB-C port a storage device (microSD card via USB-C adapter), it's not detected at all (under ArchLinux + Phosh or SXMO).  journalctl -f   does not react when pluggin/unplugging the external storage.  The LED on the microSD-to-USB-C adapter blinks briefly when plugging in, so some power flows there.  Also, my PPP is connected to the keyboard case while testing the above.  Anyone had any luck using external storage via PPP's USB-C port?

Due to https://gitlab.com/postmarketOS/pmaports/-/issues/1645 my phone and keyboard case both discharged to the point of shutting off while I was out on the run for barely a regular day's length. Afterward I ran into some really annoying apparent keyboard case charger bug, where if it's beyond a certain level of discharged, even if it's plugged into a powerful charger it will lead to the phone inside to discharge further because it somehow can't manage to charge itself and the phone properly at that point, at least not in combination. Now I know the charger is adequate, because I ran the phone non-stop on this for durations like a week or more with the phone staying on high charge and the keyboard case also never turning off with the phone actually busy as a hotspot, so the charger obviously can and WILL provide enough power to charge and supply both items at least if the phone isn't on max cpu usage.

So I was hitting above bug where the phone would still discharge in idle even though charged through the keyboard case (and a connected charger!). Last time that happened I eventually gave up on this weirdness and just charged the phone and the case both separately and only then combined them again. This time, a kernel dev was in the PinePhone matrix chat so I thought why not try to collect some useful info first. This of course prolonged this bugged state.

And then, during this, the case just went dead. My only guess is that not only did it mess up bad enough to somehow no longer charge the phone or even provide enough for its idle power, but maybe at the same time also discharged itself further despite being plugged into an up-to-small-laptop 60W rated charger??? This would be pretty disastrous because now it won't even charge again, seemingly, it just doesn't seem to react to anything anymore. It's not getting warm, the phone isn't automatically booting when pressed into the case once it gets its charging connection, it's just acting like a dead weight basically.

What is going on? Also this seems like a pretty severe firmware or charger bug if it actually managed to discharge itself to dangerous levels under these kind of ridiculous circumstances (I mean, the charger was both proven to support it fine in the past and has a ridiculously overspec'ed max rating too, and was non-stop plugged in during this).

I would prefer to not just dump this entire case into the trash and maybe never buy one again since this and other issues have been pretty rampant for me, but I'm not sure what my other options are. Sadly I don't possess any electronics tinkering tools or knowledge. Any ideas?

I read everything I found, but I don't understand if there's something wrong or not.

- I tried different chargers, but none charges the PP or the keyboard while connected to the PP Keyboard (using the Keyboards USB-C port)
- When the PP is connected to the PP keyboard, the PPs battery drains even faster instead of getting charged
- I have to charge the PP and the PP keyboard seperatly (separated of course)
- PP keyboard never seems to be fully charged
- If I connect the fully charged PP to the keyboard, the battery capacity is about 30%, when switching on the (theoreticaly fully charged) keyboard battery it's about 60% max.
- Sometimes the Pinephone indicates, that it gets charged by the keyboard, but the battery percentage decreases, even when the PP is not in use (How is that possible?)

Can someone explain that to me?

Currently I have to seperate the PP from the keyboard twice a day to charge it. That is no solution. What can I do to charge the keyboard correctly (chargers should be fine)?
Is there any way to tell if the keyboard is charging at all? Or does that indicate any hardware problem?

Does anybody else have those problems?

Thanks!

EDIT:
 

After having a call all of the audio sinks disappeared (pactl list sinks only outputs a dummy sink) and they don't come back after rebooting (tried 5 times so far). I tried both pipewire and pulseaudio both don't show any sinks. So i assume that it's a driver issue. I also found this gitlab issue for Mobian (i run Mobian bookworm) which contains pretty much the issue i'm having with the difference that a reboot does not solve it.

In dmesg i found the following which seems to be related although i didn't look into dmesg before this problem appeared
(rt5640 is the driver for the ALC5640 I2S audio interface if i'm not mistaken)

I have developped several web applications using node.js/PHP on server side and classic HTML/JS/CSS on client side (https://www.alsatux.com/Pinephone), still in dev, currently using them on local desktop and phone.
But i still got annoying problems. Here is one of them...
My URL entry is https://mobian/app/ with a self signed certificate. I added of course "mobian" to "localhost" in /etc/hosts...
With no external connection, epiphany returns "Errror resolving "mobian" : name or service not known". But as soon as i connect to the internet, this error message disapears and i can't access to all of my webapps. So it seems that epiphany don't loot at /etc/hosts first, according to /etc/nsswitch.conf.
I made the same test with Firefox : with ou without external connection, firefox has no problem at all to access to the apps !

So is there any way to ask epiphany to follow the nsswitch.conf policy when no external connection is available ?

hi,
I managed to flash maemo on to card and boot fine. However there appears to be no way of using broswer/calls/sms. Can someone please tell me how to set this up on pinephone?

Edit: Found a report here from someone with the same issue and apparently it's because of a bug in libspdlog1 so I''l just have to wait for a fix. Thanks to anyone who read this

I've installed Nheko via apt on a fairly fresh Mobian install. When I tap the launcher the phone just shows a blue triangle-pattern background and nothing else (except the usual black bars at the top and bottom). Should it be working? Am I missing some dependency?

Pine64 announced first details on a forthcoming Risc V SBC https://www.pine64.org/2022/07/28/july-u...l-evolved/

Features

• StarFive JH7110 (4 SiFive FU740 1.5GHz cores)
  
• Imagination Technologies BXE-2-32 GPU
  
• 4 or 8GB memory
  
• 2x Gb ethernet ports
  
• 1 x USB 3.0, 2 x USB 2.0
  
• GPIOs
  

• There is a GPU but the CPU is probably too slow for daily desktop usage.
  
• 2 ethernet ports but no wifi. That rules out a router unless one adds external wifi.
  

Hi,

I successfully implemented a solution for having an "after power loss" feature on my rockpro64.
I use an esp8266 with a relay shield, connected to the rpi connector.  5V is provided through the rpi connector as soon as the 12v DC plug provides power
3.3v pin is connected to a GPIO of the esp8266. The pin is to 0v if the RockPro64 is off.
If the rockpro64 is off  the esp8266 detect that the 3.3v pin is down and it turn on the relay for 1s.

I use esphome to configure my esp8266.

Today one of my pogo pins melted while connecting an PPP with an empty battery to the keyboard:



This is a weird thing and if this happens to you, here are some pictures on how you might fix this:

1.) remove all screws on the backcover, including the one behind the white sticker:



2.) Gently remove the whole back cover:




3.) Clean the PCB contacts with alcohol or some special "Kontakt" cleaner:



4.) Take a replacement pin (or clean the burnt one) and try to model a new surface with some glue and bring it in place (its terrible work when you have big hands):



5.) Wait 24h until the glue is really dry (I know, they say it takes seconds to dry, but thats not true), then clean the pogo pin from any glue with a thin file or sandpaper:

......Picture coming in 24h........