Back in the day, when you had a computer with slow CPU, minimum RAM or small hard drive, people made "tiny" or frugal Linux distros
that gave you a full-ish Linux but left out bloated software like KDE that ran slowly.

Is there such a frugal or tiny Linux distro for the Pinephone or Pinephone Pro that strips away resource-hogging software that
slows things down unnecessarily?

Hi,
Does either the Pinephone or Pinephone Pro offer conventional OpenGL support, or are they limited to OpenGL ES?
And is there any hardware acceleration?
Thanks.

I broke stuff.
Booted from JumpDrive, saw what looked like two partitions (I guess they're actually separate emmc drives?) exposed (apart from the SD card), in frenzy formatted the first one to vfat, flashed system to the second partition with dd.
Pinephone doesn't start. I guess the first partition is a boot partition and I broke it. I can't find files that should go onto the first partition in order to fix it.
What should I do?

Just wanted to  add some information  for those that are looking to  delve into the  phone lapdock  realm.   As many have asked about  does it work for PinePhone Pro.  and had many mixed reports of  usb-c docks  work and not work and Nexdock and Uperfect lapdock owners asking does it work and seeing it mostly not work  etc...  

the following is the current state i have working....  noting that things are fluid with rolling distro's so  it may break for a while in the future.... but usually it only gets better....

I am using the DanctNix  arch plasma for pinephone pro  then updated to the latest... 
data from  information panel on plasma:

Operating System: Arch Linux ARM
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.17.6-1-danctnix
OS-Type: 64
Processor: 4 × ARM Cortex-A53, 2 × ARM Cortex-A72
Memory: 3.8 GiB


for the lapdock i am using the Uperfect X lapdock  its practically the nexdock 360 minus one usbc port. the cables that came with the lapdock are from ugreen.

and the biggest thing is that cable orientation matters....  so once i  got the cables at each end in an orientation that worked. i added a simple dab of nail polish.  as to reduce future setup frustrations...

I also tried a Satechi brand short cable and it worked as well but only when the satechi logo is facing "out/towards the user"...

also i found that if things were not looking right after plugging in the cables  pressing the power button quickly to lock the phone, then entering back in via the login screen  usually fixed things....   for the most part i did not have to play with screen display settings just let plasma work it out..

like all things on the pinephone pro  its beta... 

I will update this post with images soon   also  this setup works even when the Pine Keyboard is attached to the PPP...   but power drain is still a thing so until charging works better   it appears  even if plugged int  still drains down ever slowly 10-20% per hour whilst using it.....

Attached Files

Thumbnail(s)
           

Gday ... First post on forum ... I note that the Pinebook Pro 14 inch laptop is currently out of stock but will be available late June 2022. Is it possible to pre order?

Last time I was using my PP intensively was August of 2021. At that time, I wanted to get the PP to mostly be suspended, but every 10 min or so, wake up and check for notifications (emails, Matrix messages, Signals, etc.). I did manage to get it to do that (and so finally got a comfortable day's battery life out of it [EDIT 2022/05/25 while still getting notifications in a timely manner]), but you'll see that it is a labor intensive hack to implement. Here's my thread on that: https://forum.pine64.org/showthread.php?tid=14564

I've been waiting for a better-implementation of this functionality to come around. Has it? Does tow-boot do this now? I see good things, but the forum posts and docs don't specifically address this question.

So, what's the verdict? Does Mobian on the PP now periodically wake up to check for notifications? (It already did this for texts, via CRUST. I'm looking for general functionality; not just texts but emails and all other messages)

Thank you!

Hello everyone. I have a problem with making backup through dd.
Example:
Through PINE installer on windows i installed some image of Linux on SD card.
Then on linux machine through dd command (dd if=/dev/mmcblk0p conv=sync bs=64K | gzip ~/image.img.gz) i made image of this SD card.
Then i copied (gunzip -c ~/image.img.gz |dd of=/dev/mmcblk0o conv=sync bs=64K) image from my file to SD card.
And this doesn't work, system is not loading. 
Gparted cant read what kind of FS using partitions after making copy on SD card.
Has anyone encountered this?

I have not been here in awhile, but still very interested in all things Pine. Sorry if my questions are redundant.
Has the Pinebook Pro advanced to the point where it could be considered end-user ready for someone who uses only Linux (Mint, Ubuntu) in daily life? (I am not an advanced Linux user)
I see the trackpad works better

Has the problem with the hinges been fixed?

Any ideas on when/if  Pinetab will be ready/available? Is it still a viable project?

So went back from Phosh Manjaro to Manjaro-Plasma and kept getting package errors trying to run updates in the gui, ran the following from terminal and voila...now time to test things and see if there were any improvements to battery life and/or calls/MMS

Hi All,

Apologies for the simple questions, but I want to confirm a few things before we design this module into our system.

1. We are effectively using no analog signals (i.e, HDMI, Headphones, Microphone) in this design. On the baseboard we are designing I am planning to leave these pins floating. Is that okay to do?

2. I am powering the device through a DC wall wart. There is no battery in the design. For the pins that connect to the battery port of the PMIC, can I leave these open?

3. Should I power the COM from the DCIN ports, USBVBUS ports, or both? I noticed on the baseboard you design that these signals have a population option to be connected together.

4.How should the PWR_ON signal for the PMIC be used? Should it be pulled up or down to turn the device on? Or is it only edge triggered?