I received my PBP around a week ago and the keyboard doesn't work. I contacted support that night, while they said they would send me a new keyboard, they havn't said anything since, not even how long it might take to ship the part, nor what the status of the part is. Is this normal? Is there something going on I'm unaware of that would induce a delay in getting this sort of information? As-is, the device is unusable and is making me quite sad.

Good evening,
i'm one of the guys that has preordered the pinephone PMOS-Edition very early, because i was really eager to get a working linux phone.
And yeah, i received my pinephone, was very happy, until i noticed that the screen was not working as intended.
   

The did work, but had many problems with the image on it. I tried many things like flashing manjaro, in hope it world be the os, but no.
So then i did contact the Pine64 support. Didn't receive a message back for 9 days. Then i became worried and did, what i didn't want to do at all, opening a paypal case just to be on the safe side and get things going. After that i finally got a message back from the support telling me to please try to adjust the cables in the phone. So i did, and nothing changed.

After some conversation i was offered to get a replacement screen, which they sent out to me. While it was shipping my paypal case time was running out, but i didn't worry about that anymore. I would have a replacement screen, so no worries for me.

And indeed, i did receive my screen six days ago. I immediately started replacing it, and indeed, it worked. The problem here was, the touchscreen did not. So i tried reinserting the cables and looking for broken cables in the screen. I didn't find anything. What i tried then was connecting the old screen, and yeah, while the image was broken, the touchscreen worked. So in that case i can be sure it's a problem with the new screen, not with the phone itself.

I'm quite puzzled how it can be that i received two non-working devices in a row. After all i did not notice anyone else having problems with the quality of their phone here on the forums, maybe i just didn't look enough.

But i wonder how that could happen. Additionally i'm a bit disappointed in the support. I know, it's not like Pine64 is a multi-million dollar company with a giant support section. But i had to wait 10 days and a paypal case for an answer. While the case was running i got my answers rather quickly, now after it ran out and i have those two partially broken screens i don't get any answers anymore. Still waiting for one.

Did anyone else have a similar experience, am i just in an unlucky position to be here?

Greetings
Janik

Hi, 9 days ago I opened an ticket on Pine64's desk.zoho. No one has answered me yet.

How long does Pine usually take to respond?

Just wanted to let everyone know that after installing Fedora 32 Workstation the upgrade to Fedora 33 Workstation went off without a hitch.

Gnome is version 3.38.

Memory usage in Fedora 32 hovered around 1.2G. In Fedora 33, memory usage hovers around 980M. The desktop is snappier and animations are smoother. CPU usage seems to be lower as well. Videos and Youtube run fine. I haven't tested anything above default settings for video playback, yet. I have lots of testing and playing to find all the changes.

Fedora 33 adds better support all around for Pine64 hardware. I didn't get a chance to really test Fedora 32 that much but it was a solid experience. I have it installed on emmc.

Fedora Magazine Article

In my opinion, Pinebook Pro went from tinker toy to a serious daily driver for me with Fedora. It really is solid. Software installation is a breeze with gnome store and RPMFusion is a nice equivalent to AUR. Also, dnf package manager is great. The documentation is superb for learning and getting things done as quickly and easily as possible.

This is my first experience with this distro and I'm really enjoying it.

So I just got my Pinebook Pro ANSI in and right off the bat I found I was having trouble connecting to Wi-Fi under Manjaro. It refused to connect, and kept asking for the password again and again.

I then remembered I had 802.11r Fast Transition enabled across my APs (under OpenWRT). When I disabled it on one of them, my Pinebook was able to connect. Turning it back on kicks it off the network.

Is this a known issue? I haven't experienced an issue with any of my other wireless devices. I'd like to keep it enabled if at all possible. A lot of people in my home make use of Wi-Fi calling, and FT helps with dropouts.

Thanks!

[27/10/2020]
Stay tuned to this thread for up-to-date details regarding the shipping progress of Manjaro CE.
Everything is on track and getting ready for shipment. I should have more details this week.

[30/10/2020]
We're somewhat ahead of schedule as first PinePhones shipped via DHL have already started arriving to their new owners.
Those of you who received DHL shipping notices earlier this week - check the status, your units may have already shipped.

For those of you in the Europe: PinePhones destined for European countries will arrive at the warehouse in Poland soon.
However, end-user delivery times may be affected by COVID19 restrictions - this remains to be seen.

[04/11/2020]
There is a constant and steady shipping stream and no major issues have been encountered so far.
Shipments for Europe are expected to start Thursday - 5 November - and continue over the coming weekend. You should expect to see shipping notifications soon.

[09/11/2020] It has come to our attention that some Manjaro PinePhones have shipped with postmarketOS - please see this thread for details.

I have recently installed a fresh copy of Manjaro using the manjaro-arm-flasher, but when I try to boot the machine it shows a red light on the left status indicator, then I have to wait for a few moments, hold the power button for a couple of seconds and then it gets started with running the OS and showing a green light.

Why is that and how can I fix that so it would start itself directly after the first time I push the start button?

Thanks!

Hi, this is my first thread, I'm new to PINE64 and need help with a Pinebook Pro.

So... My PBP has elementary OS installed on its internal disk, but after not charging for a while (I guess, it can be some other cause), initramfs stops detecting the eMMC... It says something like "UUID=xxx not found dropping to shell", and in the busybox terminal I found out that there's just no mmcblk2 detected! In /sys/block/ there's only mmcblk1 - my SD card! But the eMMC is definitely not dead, because the PBP still can find the bootloader from eMMC.

So what happens inside my PBP so initramfs can't detect it, but the firmware does??? And the problem just dissappears when charging for a while again?


And sorry if this question is stupid and it's on the first page of some documentation and was answered ~90 times on this forum and it would get 1000 downvotes on stackoverflow.

I have a Dell TB16 dock at work and thought of a use case for it with my Pinephone, but since the Thunderbolt connection is normally used for powering a laptop and replacing a 130W, 19.5V power supply, I'm hesitant to plug it into my phone. This means the phone would have to negotiate the dock down to a supported voltage (if the dock hardware allows it) or reject charging at all.

Is there any realistic chance that this would damage the phone, or should it be fine?

Hello community any advice for Phone Rings cant PickUP/Talk or engage call?  Txt message works I am running ubuntu touch internet work as well just no go on the phone function???