I've gotten so used to running multiple operating systems on my PBP (via SD cards) that I've gotten to the point of "needing" to run two simultaneously.

Oh well, maybe I'll get to the point where I'm running one in a virtual machine.

TLDR: if your pinebook pro audio sounds crappy, try:

Hey guys, still enjoying my PBP and having a blast with a few different distros.

Manjaro is still by far the best; I certainly wish there was a decent Ubuntu option. What is your favorite Ubuntu distro for PBP? - I even liked the close-to-Ubuntu Armbian.....

But for THIS question:

I got my PBP two weeks ago, so its one of the more recent deliveries... I've been told in other posts to update my touchpad firmware. However, since my PBP is a recent delivery do I still need to do this? Or... how do I check to see if my touchpad is on the most current firmware?

And, is this an upgrade that people have a lot of issues with? The touchpad *IS* the weakest point of this laptop, however with taps as opposed to clicks I have learned it enough that it isn't REALLY in my way. It sucks a little bit, but... I can get around the desktop using it.

I live in terminal alot so.... and/or I can always just use an external. However, if doing the update will help it be a little smoother - without much risk or downside; I think I am capable of doing the update.

I can search the wiki, but if you know where the info is about it, too that would be helpful.

Thanks for any details - I just wonder since mine is so new, maybe its already updated. THANKS.

I used a rockpro64 to turn an old apple G4 cube into a home server.  I posted all the information needed for others to make it too.

https://www.thingiverse.com/thing:4603374

Attached Files

Thumbnail(s)
   

Sorry if this is a FAQ; I searched and didn't see anything. Just got my first PinePhone and while charging after the first boot I noticed that sometimes if the cable is bumped (such as by picking up the phone while it's charging) I'll here the connect/disconnect notifications chatter a few times.  This doesn't always happen -- oddly enough, if I gently flex the end of the cable to test how much play it has it usually doesn't chatter -- but it does continue to occur randomly, a bit more often than I would like.

Is this normal?  There does seem to be a good deal more play than with other USB-C phones I've compared against.  Is there a special charging setup (e.g., a charging stand that fits especially well) or handling technique  needed to avoid damage?

I m interested in Linux watch. I cam across the TicWatch Pro 2020. Posting here is a bit off-topic, but what makes a Pine64 device a Pine64 device? Does it need an Allwinner A64 processor?


I compaired the specifications of the PinePhone, the PineTime and the TicWatch Pro:


The PinePhone uses an Allwinner A64 processor, which has four Cortex-A53 cores clocked at 1.152GHz and a Mali-400 MP2 GPU. Its frame and case cover is made of plastic. It contains a 5 megapixel back camera and a 2 megapixel front camera and a USB-C port with USB 2.0 that supports DisplayPort alt-mode


PineTime Smartwatch

• Display: IPS capacitive touchscreen, 1.3 inches (240 x 240 resolution)
  
• Communication: Bluetooth 5 Low Energy.
  
• Sensors: Accelerometer and Heart Rate Sensor.
  
• Battery: LiPo 170-180 mAh.
  
• CPU: 64MHz ARM Cortex-M4F.
  
• SoC: NORDIC Semiconductor nRF52832 (or nRF52840)
  

• Processor: Qualcomm Snapdragon Wear 2100
  
• Display: 1.39 inches AMOLED with 400x400 pixels resolution Gorilla Glass 3
  
• Operating system: Google Wear OS
  
• RAM: 1GB
  
• Storage: 4GB internal storage
  
• Bands: 22mm leather/silicone hybrid
  
• Connectivity: Bluetooth 4.2 LE, 801.11 b/g/n WiFi, GPS/Galileo/GLONASS/Beidou, NFC
  
• Sensors: Accelerometer, Heart Rate Sensor, Gyro Sensor, Geomagnetic Sensor, Ambient Light Sensor
  
• Rugged ratings: IP68 dust/water resistant rating and MIL-STD 810G shock resistance
  
• Battery: 415 mAh non-removable
  
• Dimensions: 45 x 45 x 12.6mm and 222 grams
  
• Colors: Shadow Black and Liquid Metal Silver
  

This is a bonus. Using the previous post:

https://forum.pine64.org/showthread.php?tid=11567

A 32M sized micro SD card image should be sufficient to extract a full copy of SPI NOR flash contents. I performed the following successfully using a 64M sized image to extract a full copy of SPI NOR flash from u-boot prompt with micro SD card inserted:

For my fellow klutzes, here's a DIY Bumper Case idea, using furniture bumpers: https://imgur.com/gallery/5xtZ3x6

Hello again!

Administrative: I apologize in advance for posting the actual instructions offsite as I have yet to figure out how to format headings using bbcode. If I ever figure it out or it becomes possible I will bring the content back over here. The instructions may be found at the link at the end of this post.

This process allows you to program/erase the Pinebook Pro (PBP) SPI NOR flash (flash) using u-boot on a micro SD card. 

• The user is still required to remove the back cover to turn the eMMC switch off and the UART switch on.
  
• The user is also required to connect to the PBP over USB serial UART from a host machine (Rock64 with keyboard and monitor for example).
  
• You cannot use this process to recover from writing bad images to the flash though, you would still have to short the pins on the flash to boot from SD card again in this instance.
  

• The SPI flash is not automatically detected. I am not a u-boot expert yet but I assume it is because an alias for 'spi0 = $spi1' is missing from the device tree. And I additionally assume this is because rk3399-pinebook-pro-u-boot.dtsi does not #include rk3399-pinebook-pro.dts. I tested this theory by temporarily adding the alias to rk3399-pinebook-pro.dts and the SPI was detected (should have also tested by adding the #include to rk3399-pinebook-pro-u-boot.dtsi).
  
• CONFIG_ENV_OFFSET is set too low. CONFIG_ENV_OFFSET is automatically set to 0x140000. uboot.itb is written to 0x60000 and its current size is 949936 (928K) bytes which overlaps with 0x140000. If you want to safely saveenv you will need to set CONFIG_ENV_OFFSET to 0x150000. You could also place it at the end of SPI ((16M bytes - 1 byte) - 32K bytes).
  

No matter what I do, I can't connect to wifi. I replaced the built-in Manjaro KDE Plasma with Manjaro Xfce. I'm using the wifi menu widget on the task bar to select my router, entered the correct password a million times, and it just pauses a great while trying to connect and then asks me to enter a password again. Does it every time. 

This is the only device in my house that has this problem. I've used Wifi on my Pinephone, my android, and like 4 other computers, and my family has other devices with working internet. I've tried reconnecting to internet on a few of these devices and it worked. My new Pinebook Pro is the only device that refuses to connect to internet. 

This has been happening for a full week now. I haven't even been able to use it effectively without internet. Without internet, it's extra space being used up in my house that I don't need if it won't work. (i bought a table for it)

Pretty frustrated, to be honest, because I'm pretty sure my 30 day warranty expired by now.

To top it all off, can't reinstall the operating system it came with, (or any operating system made for it, for that matter), because the micro sd card reader isn't reading my micro sd card. So unless I can fix wifi, I'm basically screwed.

Though a separate issue, it would be nice to have the micro sd card reader working again, too. Not sure if that will ever happen, either?

I'm a developer who ports my software to a lot of operating systems, including windows, mac, linux, freebsd, and I would like to get netbsd or openbsd working on my pinebook pro since my other machines are being used for other things at the moment and can't have their os replaced easily right now without being a big sacrifice.

Any help is appreciated, like you have no idea!
Samuel