I just got my Pinebook Pro and I noticed the keyboard issues others have already identified, but also that the bottom row of letters feel "crunchy". Noticeably louder click, with a click/crunch feel.
Anyone else getting this? Not sure this is a defect or just need time to bed in.

To be clear, it does not feel like grit/dirt is in there. It also doesn't (yet) seem to prevent the keys being recognized as pressed.

(I also had a scratched screen, but I've submitted a support ticket on that one).

Not feeling quite as excited as I was at first. Software/firmware problems I can deal with, but hardware is much less fun.

The Powerbook Pro has a 64-bit architecture.
I see the default Debian and the Mate OS are 32-bit.
Is there no 64-bit Linux OS available?

After installing ayufans patched mainline kernel (I want panfrost) onto his minimal buster and bionic builds, I cannot boot past a certain point.  Here's what I see on serial console before it dies:

[   47.917722] Run /init as init process
Loading, please wait...
[   48.897918] tmpfs: Unknown parameter 'size'
mount: mounting tmpfs on /run failed: Invalid argument
starting version 237
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Warning: fsck not present, so skipping root file system
[   99.500975] EXT4-fs (mmcblk1p7): mounted filesystem with writeback data mode. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
mount: mounting /run on /root/run failed: Invalid argument
[  104.987855] random: crng init done
[  106.115332] tmpfs: Unknown parameter 'mode'
[  106.119090] systemd[1]: Failed to mount tmpfs at /dev/shm: Invalid argument
[  106.143006] tmpfs: Unknown parameter 'mode'
[  106.145440] systemd[1]: Failed to mount tmpfs at /run: Invalid argument
[  106.169253] tmpfs: Unknown parameter 'mode'
[  106.172654] systemd[1]: Failed to mount tmpfs at /run/lock: Invalid argument
[  106.204518] tmpfs: Unknown parameter 'mode'
[  106.207772] systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: Invalid argument
[  106.257404] systemd[1]: Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or directory
[.[0;1;31m!!!!!!.[0m] Failed to mount API filesystems, freezing.
[  106.312466] systemd[1]: Freezing execution.


So it looks like we can't mount root with ayufans mainline.  Has anyone managed to get this working?

In the past my personal experience with 'tuning' consumer device antennas with AM cb radios, and radio phones VHF & UHF mostly involved trimming the antenna to a precise length,  though sometimes this is altered by reflectivity ie near-by objects affect the SWR.

  ( But those were all external antennas,  so much simpler to 'tune' I am sure.)


  By the scale,   I am pretty certain the smaller antenna as one inside a cell phone case is very sensitive to precise length for transmitting efficiently. 
   BUT Also,   the inter-action with the other components within such a small area,  can likely cause different lengths for this inter-action rather than just a calculated length.
 After precise adjustment,    any movement of the said antenna within the enclosure will cause changes to the antenna performance.

Since this phone is so easily serviced by the 'end user'  They should be warned to NOT disturb the internal antenna.
 
The smaller the antenna the more critical and sensitive the tuning.

This was posted as an announcement, but for visibility I'm also posting it as a normal thread...


Just a few moments ago as of writing this announcement, MrFixit released a new update (v1.4) to the default OS install. It does not bring kernel upgrades, but it does add a test for an important issue which was discovered yesterday:

On some number of PBP systems (not all), the boot directory contains files belonging to the Sality class of Windows malware. It likely has been caused by one or more flashing/test stations at the factory which are infected by this malware. These files take the form of one or more .exe or .pif files with cryptic names, as well as an autoexec.inf file.

IT DOES NOT POSE ANY DANGER TO YOUR PINEBOOK PRO. Again, it is Windows malware, and can't run on Linux (especially ARM Linux!). However, in the interest of complete safety, MrFixit has pushed an update which includes a small script which tests for unexpected files in this boot partition and asks you if you wish to delete them. This script will only run once upon update, as the malware files can not reappear. The script is available here, if you wish to inspect it or run it on your own.

The factory will be notified of this issue, and hopefully it will not recur in the future.

On the blog you already said that you thought of two covers, one in rigid plastic and one in silicone/rubber (I don't remember exactly).
My question is if one of these two covers (the rigid?) also covers the screen.
Sometimes my phone falls on the floor or comes into contact with sharp objects such as keys or similar, so I like that the case covers the phone as wide as possible, which makes it more sturdy to impacts and protects it from scratches (like booklet cover for example).
Is it in your plans to provide a case of this type?



Another idea could be a dockstation to keep the phone up and to be able to charge and provide at the same time more input like usb/hdmi/ethernet... (since probably the pinephone will  be used also as a portable pc!)

If I wanted to exaggerate, the complete case I was asking for at the beginning could also offer these additional ports, working as a stand and providing the possibility to charge the phone at the same time, can you call it "cover-station"... but this is only my fantasy

Hi all,
I got my PBP + nvme adapter last week.
I has been trying to move the rootfs to the SSD.

I tried this tutorial without luck: https://forum.frank-mankel.org/topic/208...vme-platte

Basically, after edit the bootfile (extlinux.conf) to point to the SSD instead to the emmc the PBP refuse to boot.
I have to boot from the SD modify the boot file (emmc) to be able to boot again from the eMMC.

I would like to know if somebody has any suggestions/solutions.

Thank you.

Will the pinephone get a warranty of some kind? It seems the pinebook pro mentions a "30 day" warranty?

First off Noob as in, I haven't touched a Linux based machine in a very, very long time and my skills are RUSTY so go easy on me.

I'm trying to install VSCode on my new Pinebook Pro with the hopes of using it for light front-end dev work. I downloaded the Debian version of the package. When I initiate the install I get this error...


"error wrong architecture amd64 run dpkg --add-architecture to add it and update afterwards"

I've done some digging but many of the solutions are 2 and 3 years old and nothing that specifically speaks to the error listed.

What steps should I take to install the amd64 and update as suggested?

Any help is appreciated.

Thanks