Hi there.
Recently I have bought new monitor with the resolution 2560x1440. And it blinks with red color (flickering is very short) every now and then, not very often, once every few minutes. It's really annoying. When I set resolution 1920x1080 it works fine.

I use Ubuntu 18.04.2 with LXDE.

Is there any solution to solve that problem?

Is it normal, that the modem (wifi and SIM) isn't working when  booting with removed batterie ??

Default Debien installed, Mrfixit, touchpad, and Winevine updates done.

Sound works fine UNTIL I hook up a bluetooth Pioneer Ironman headphone. It connects just fine, shows as the output but it wont work. Netflix in Chromium stays buffering and the headphones stop working, cant even turn them off. I turn off bluetooth on the PBP and the headset and netflix start working just fine. Connect back to the headphones and it locks back up.

Has anyone experienced this and if so, is there a solution?

Thanks,

Michael

SOLD. THANK YOU.
---------------

I have a January-delivered ANSI Pinebook Pro that I am not using (work keeps me busy). It will ship in the original box, with the power supply.

Your price is $200 plus actual shipping to a US address (Fedex only).  PM me if interested.

Cheers.

I have following problem: My Pinebook Pro with the default OS never charge to 100%. So, when it is connected with the 5v charger, when I put the mouse on battery icon, the maximal percentage what I can see is 93% ("Laptop battery charging (93.0%)"). Do someone know if this is a hardware or software problem? And are there another people who have similar problem?

Hi All

My PBP stopped powering on recently whenever the SD card was not in it with an OS to boot from. no reaction to power button at all, short press, long press or anything.

I took the back off, re-seated the eMMC card and tried again - no luck. checked all cables, no damage at all.

I tried the reset and recovery buttons - no reaction.

Now, I cannot power it on even with SD card in - both off and on charger.

Have anyone encountered something like this before ?

Thanks in advance.

Connected USB type C to DP device: it works in mirror mode.

Manjaro XFCE only displays one video output: "default"

Hello,

I want to update my installation of u-boot. (I already asked some questions in the Manjaro Forum because its their u-boot update which asks to be dd'ed to a target, but I am left with some open questions.) Where exactly does u-boot reside when using a standard Linux like in this case Manjaro, installed to the eMMC? When I want to update u-boot, do I simply need to write it to the eMMC device or do mmcblkXboot0 and mmcblkXboot1 play any role in the booting process of Linux on the Pinebook? The information in https://wiki.pine64.org/index.php/Pinebook_Pro does not answer my questions and the documentation of u-boot is somewhat inaccessible even for someone who works with Linux for a living.

Yours
Stefan

It would be really simple.  After the preorder, you see that there are, say, 65% 128GB and 35% 64GB orders and assemble two batches.  When first assembling the units, you just put in the appropriate size module.

It would serve as market research.  Let your customers tell you what they want.  There's a good chance it would make this laptop even more popular.

As it is, it's annoying: Instead of +$20 for +64GB it's +$55 and you end up with a spare part you don't need.  The value proposition is less than half as good.

What people want out of the PBP is not necessarily a fixed $200 price point, it's the value for money.

So it appears there's a problem when upgrading from older kernels to something around 5.5 or later.  The symptom is that when you boot the new kernel, the screen is very dim, possibly appearing completely black.
The problem seems to be that with the older kernels, screen brightness was on a 8-bit 0-to-255 scale, and the newer kernels use a 12-bit 0-to-4095 scale.  So the reasonably bright "224" (for example) brightness that you had with the old kernel becomes a rather dim "224" with the new kernel.

It seems that this issue occurs with a few different distributions' kernel packages.  I'm not sure if any distributions have any fixes (maybe a transition script) built into their kernel packages.

My current thinking is that the best approach (for individual users) is to verify that your Fn-F1 and Fn-F2 are working for adjusting your screen brightness before upgrading the kernel.  Then when you boot your new kernel and you can't read the screen you can use them to turn up the backlight.  I neglected to do this.

A hackish approach could be to poke at the files in /sys/class/backlight/edp-backlight/ (you could do this via SSH if you can't adjust brightness via the keyboard/trackpad/screen)