Hi.

I'm trying to configure aerc but on configuration page it crashes. Seems that Unix Server is not started. How can I solve it?

Regards,
Peter

I am fairly new to the Pine ecosystem and hope this is a good place to ask my question. Dose the PinePhone have a secondary processor that handles the real-time processing needs of a phone? I am seeing that the PinePhone has trouble receiving calls sometimes; is this a possible solution?

pinephone circuit board design, conductive parts

is there somewhere circuit board design for pinephone? in this case conductive parts, not the components placings. (although components placings for 1.2x could be useful).

i was thinking about that power surge issue. is it possible that power connections to the modem chip are too thin. this might be an issue to look at.

I'm strugging to get opensuse to complete a boot on my RockPro64.  I can only get as far as "EFI stub: Exiting boot services and installing virtual address map..."  it stalls there.  What am I doing wrong?

I was able to clone the project, change the color of the flashlight app and then build that and flash it to my PineTime sealed OTA. Looking to perhaps help look into the multi-swipe issue. I saw that the PineTime uses the CST816S, and I found where the driver for that is in the repo, but I am still trying to figure out what is happening in there... The medium article mentioned is no longer available.

I have limited experience with embedded devices, so any resources to point me in the right direction to understanding how swipes are registered with the CST816S are welcomed!

I'm using my RockPro64 as a NAS with open media vault. I'd like it to shutdown or standby at a particular time (this I can do with OMV) and then boot up again the next day at a particular time. 

How can I get the boot up to happen on schedule? I tried using WOL but the board wasn't responding to it. I also tried using OMV to put the system into standby and then trigger a reboot at a set time but nothing happened.

I've found that since there is still 3G service for now, my Pinephone running Mobian/Phosh will sometimes jump back and forth between 3G and 4G. Calling seems to be more reliable with 4G so I went into "Settings/Mobile/Network Mode" and changed that to "4G Only". A checkmark appears next to that, so then I tap the blue "Set" button and it changes and takes effect. However, that setting does not survive a reboot. The next time the phone is turned on the setting reverts to "2G, 3G, 4G (Preferred)".

Is this a bug or a feature, or am I missing something? Is there a way to retain this setting across reboots?

Hi Pinephone team,

Each Pinephone, the Pinephone UBPorts and Pinephone for Mobian editions over the months,

their batteries deplete really quickly and don't hold good charge, and I'm still using a backup Android for most things because of this.

I'm wondering if it's a hardware concern of power usage or it's about the software and how much energy it would take to run a laptop or desktop kernel with all the GUI and classic higher energy usage software on the smaller hardware .

Not sure! I'm only a user .

wellwishes,
food

Hi Mobian team,

I've been using Mobian as my daily driver on Pinephone and it's been working every day.

I'm noticing the battery degrades really quickly over time, and I'm wondering if there's anyone working on increasing the energy efficiency of the operating system

I know I can buy a new battery for not that much money, though I'm concerned about the long-term cost of having a pile of dead batteries whereas Apple and Google have no piles of dead batteries.

wellwishes,
food

Hello PINE friends,

as you may have heard, the Quartz64 has an eInk interface. This allows for high-speed (relatively speaking) operation of a 10.3 inch eInk panel. The controller for this is referred to as "EBC".

The problem, however, is that the downstream driver for this is... a GPL-2.0 licensed assembly dump. Yeah. Thankfully it comes with debug symbols though, so we're actually very lucky in that regard.

Here's where you can come in and help: we need to reverse engineer the driver struct by struct, function by function, allowing us to write an upstream-ready EBC driver. Not only will this allow us to run the driver on mainline kernels (or rather, at all, since it currently doesn't build even on the downstream kernel), but we can also then make it faster, as there seemingly are some math heavy functions.

For more information, check the wiki article on the matter, which includes links to the repositories and some further information. People have also reported good results from assembling the .S into a binary and then running Ghidra on it.

Thank you for your attention and your interest.