Hi everyone, I'm putting my ANSI PineBook Pro up for sale.

• Perfect working condition
  
• Excellent cosmetic condition
  
• Only lightly used
  
• Fresh install of Manjaro Mate
  
• Clean
  
• The only thing missing is the power adapter. (The adapter was DoA but USB-C charging works fine.)
  
• Asking $200 which includes UPS shipping
  
• PayPal
  
• Prefer to ship US only
  

I'm about to order the PineBuds Pro.
I am missing the following information:

1. Which OSes are out there yet?
2. Which OS is preinstalled?
3. How do I flash OSes?
3. How do I check which OS is installed and which version?

Can somebody help? Thank you!

I have 2 PBPs that I sometimes do a lot of compiling with.

One is from 2020.  I never used all 6 CPUs when compiling, or if I did, I throttled the two faster CPUs: due to the problem of using more power than the power supply can supply.

The other is from 2023 (or was it 2022?) and has the improved charging circuit.  I used this one the same way, because, if I use all 6 CPUs unthrottled, it will overheat and reboot.  For some reason, I thought this was just a shortcoming of this SOC.

But recently I did some short runs using full power on the 2023 model (not getting it hot enough to reboot), and I accidentally used the same configuration on the 2020 model.  I found out that, except for the expected battery depletion, the 2020 one never overheats and reboots.

Does anyone else have a newer one that overheats like this?  Or have I been dealing with a flaky PBP all along?

Since I got my pinephone early last year, any attempt at installing packages from discover has resulted in an error message popup saying "<pkgname>;<version>;aarch64,extrra: could not find or read package" when browsing to the application profile page.

All packages are also listed as 0b.

Sometimes images don't load.

Is there something I need to do, or should I be using a different OS?

I am currently using Pinephone "convergence edition" with manjaro beta 15.

Thanks.

I'm at my wits end, hopefully someone here can help me. So I purchased a Pinebook Pro some time ago, it's generally been a faithful machine, and satisfied my desire to move from x86_64 to aarch64 in the laptop realm. I've thus far resisted the urge to roll my own Linux install on the thing, instead faithfully sticking with the Manjaro that was installed when I got it, save for updates here and there. Needless to say, the thing is still very stock, only having accumulated whatever updates Manjaro has pushed for it, along with some of my own tools for retro console programming and a few other supporting utilities.

The problem plaguing me is being able to also use this laptop as a desktop by plugging in a monitor. The hardware itself does not contain a standard video port of any kind, which seems to be par for the course with laptops these days, so can't really fault Pine for following this awful trend. However, where things fall apart is trying to use any sort of USB dongle or dock which purports to expose video through the USB-C port.

I tried a few dongles that work with my work-assigned Macbook Pro, also over USB-C, thinking that would be fine, but no dice. Got to reading and apparently there are multiple standards for how to do this thing, and a lack of transparency by vendors, so it's a crapshoot getting a device that actually works. So I decided to avoid this whole mess and went straight to the source, I purchased the official Pinebook Pro Docking Deck, thinking this would be the end of my misery. Surely the dock sold by the vendors of the laptop would be plug-and-play, right? Wrong. I've had no luck, even with the vendor supported device, getting anything resembling video output from this thing. I can get all the other parts of the dock to play nicely, such as the USB ports, SD card slot, and audio port. The only thing that I can't get to work is the one thing I bought it for: external video.

Does anyone have any pointers, ideas, anything at all? Forum posts I've read here have unfortunately been largely unhelpful as they're either targeting some third-party component (which I've already accepted aren't going to work) or they're full of advice like "Did you try turning the symmetrical-by-design USB-C connector 180 degrees" which, given USB-C is supposed to work both ways, seems like a non-starter. I've also tried to install the "linux-pinebookpro" package in Manjaro that a few threads I've read suggested, that package isn't even found in the stock repos on Manjaro (again I haven't royally changed the base install, just kept up with updates on the same install that the device shipped to me with.)

Anywho, to summarize, does anyone know how to go about getting HDMI (or VGA!) video out of a Pinebook Pro when plugged into the first-party standard Pinebook Pro Docking Dock? I can accept third-party devices not working, but the fact that I can't even trust the first party one has me honestly a bit irked. This is really the only thing that for what feels like two years now has prevented me from finally taking this computer on as my daily driver, I can only use it through the built-in screen despite ordering what should be the absolute correct device for the job.

Let me know if a dmesg trace or any system information is needed, I've built several Linux systems up from scratch on a few different architectures, so I have a pretty good idea of where to look for symptoms of a problem.

Hi there,

I'm new here, and I've some background on Linux, Debian in particular, but I'm not a programmer but I still dare to try something special. I would like to know how the Pinebook Pro compares to the Pinetab2 in general use ? what is/are working/not working ?

Thanks all and wish you a great day !

Is there an easy way to encrypt the home directory on any of the pinephone linux distros? And is there a way to disable using USB to access files?

I love the Pinecil, but the wire I use to connect it to my [big] power supply is so large that it frequently pops out of the power connector.  How are the rest of you managing to get enough power to the Pinecil without having it disconnect all the time?

Thanks!

Jon

Hi folks.

I'm afraid to say that I've been finding owning a PPP a... cr*ppy experience.

I had expected to receive a device that, whilst the software was incomplete, at least had the basics covered - reliable booting, diagnostic ports, etc.

Well, I got lucky, and when I bought it (I think it was about a year ago) I managed to get it to work eventually after muddling my way through the assorted guides out there. I'd boot mobian, and then basically nothing was finished (fair enough, its a dev phone).

I didnt have time to play with it then (I planned to have a look at camera stuff), and it crashed on suspend so it got thrown in the "expensive paperweight" bucket.

Move on 12 months... I got some time to play, and I'd clearly forgotten / suppressed the trauma (at least my wallet had)...

After about 8 or nine attempts at getting it to power up, I managed, and... it still booted.

I thought to myself "I'll just update this debian device, and maybe it will install all that lovely fixed software and nice new toys" - I am used to Debian being reliable in this regard.

Irrationally, then, I executed

apt update
apt upgrade

And it worked!

Although a little red flag there - it now produced a deb12, not mobian boot splash...

whatever - how bad can it be?

apt dist-upgrade

oh dear... now it doesn't boot anymore...

No worry, I thought - its an open device, with OSS on it, and of course with everything being open, the instructions to fix it will be concise and easy to follow.

Nope.

I mean, this is tragic.

There is *not one* place I can find that *really* details how a PPP boots. I did find a couple of pages, but nothing on them was any use.

I mean, what, literally, is supposed to happen? theres a $£%£$^ huge LCD on the thing, but no, it just sits there blankly, or if I'm lucky, the one LED on it might change colour or it might buzz a bit.

but WHERE is any of this documented? what does the 4 buzzes mean when it occasionally does that? why does the LED go blue in some modes?

seriously - android and fastboot is better documented.

I build small devices for a living, and have worked on getting ARM devices booted for years, but this takes the cake into a whole new dimension. I'd have been utterly embarrased both personally and professionally to have released such a pile of junk.

-10 out of 10. Pathetic.

This is almost as insanely dumb as my RockPro64, which comes FROM THE FACTORY with the serial port running at 1.5Mbaud. Who the h*** wants that, ever? utterly useless, unexpected, and I had to spend AGES hunting through my serial adapters until I found one that would tolerate such a stupid speed.

WHY?

This is OPEN HARDWARE AND SOFTWARE. There is literally no excuse for this.

Any hardware on sale should come with:
1) A list of instructions on how to FULLY RESTORE IT TO FACTORY SETTINGS
2) All specs, for all versions
3) A guide that INCLUDES METHODS TO IDENTIFY  *ALL VARIANTS* of the phone - "purchased before XYth of XXX" is not good enough. I have no idea when mine was purchased at this point.
4) A bootloader that either speaks serial 8n115200 and/or (preferably) also can display status on screen / interact enough with the user to perform a self test or indiate why it's sulking.


So. Now what?

I have a useless Pine Phone Pro, that I was once enthusiatic about getting to use, that does nothing but bootloop and try to kill its battery now.

There are no instructions on restoring the phone to any sort of factory settings.

I've tried following this guide on installing tow boot, https://tow-boot.org/devices/pine64-pinephonePro.html

it doesn't actually give a link to the file it refers to, but I'm guessing its the spi-installer.img located in here:

https://github.com/Tow-Boot/Tow-Boot/rel...006.tar.xz

I've tried following this on the pine64 site:
https://wiki.pine64.org/wiki/PinePhone_P...emporarily

it SEEMS like I have the version where pressing vol_down makes it do er... something? but all it does is turn the LED blue.

this isnt documented AFAICT. Is it meant to go blue? I read that the *screen* is supposed to go blue, but that isn't happening either.

This is over a year later now - what is the excuse? EVERY SINGLE issue above should have been solved at release, and *certainly* should have been by now.

Does anybody ACTUALLY know how to make my expensive brick into a phone again?

I found that it was easy to download and install Manjaro images to my SD card using Etcher. However, after fighting Manjaro XFCE I have been pleasantly surprised by changing to Manjaro Mate. Using XFCE I tried to upgrade without success. The package manager was impossible. I tried to download/install Libre Office without success. After trying to download/install Abiword I then tried to use the terminal and the command "sudo pacman -Sy abiword". Everything appeared to work. However, When I rebooted the SD card was corrupted and the system locked up. So I reformatted the SD card and installed the Mate version of Manjaro. What a difference. The layout was more like what I was used to from working with my Raspberry Pi's. Icons on the taskbar were handy and made sense. I was able to install Libre Office without any difficulty. The download/install was slow but I could easily follow everything by watching the Package Manager screen. My Pinebook Pro is sooo much fun using Manjaro Mate.