I have noticed a very fast (probably 3-5x normal speed, where listening is impossible) playback when using Podbird with downloaded podcast episodes. I don't have any other local media to try this with but I was able to watch YouTube videos at normal speed. Has anyone else seen this behavior (in Podbird specifically or more generally with local media)?

Just threw together a few renders of the logo in different colors for fun. I also made a little image for on the back of the phone. Figured I would share them.


  transparent-pine-64-logo5.jpg (Size: 74.16 KB / Downloads: 545)

  transparent-pine-64-logo3.jpg (Size: 73.94 KB / Downloads: 558)

  transparent-pine-64-logo4.jpg (Size: 73.27 KB / Downloads: 522)

  transparent-pine-64-logo2.jpg (Size: 73.19 KB / Downloads: 519)

Anyone having an issue with the keyboard when booting off of SD card slot for Kali?

I got Kali to work fine but the issue I have is when I type semi fast the curser jumps and really starts messing up.  I'm trying to figure out which keyboard selection might be best in the settings as the default system ones do not seem to work.  I switched to 101 keys and 105 keys for PC but still getting it.

Any luck with anyone else?



thanks!

SBC:    Rockpro64 v2.1 4Gb
OS:    Official Debian Release (un-bootable)

So I decided to try the Official Debian release on my RockPro64
and the installation went fine but would not [re]boot after the
installation.

Any ideas, recommendations, suggestions?

TIA,
/Faradn

~ Rockpro64 ~ Odrooid C4 ~ Odroid N2 ~ Odroid XU4 ~ Pi 3B ~

Noting that regardless of what OS is tried, my PBP seems to lock up after a while running...Except the original Debian install. 
I'm trying several OS'es via SD card....
Is it the unit itself or is there some sort of change I need to make??
Thanks for your help :-)

One of the things Solaris & AIX have for safe patching & upgrades, are alternate boot environments. AIX solves this by having an OS boot mirror device that can be detached and made bootable as a backout plan. Solaris 11 does this through a mostly automated procedure with ZFS snapshots & file system clones, using the "beadm" command. The intent is to allow easier restoration of service without having to perform a full restore. (Either from backups, if you have them. Or re-install.) Simply reboot to the previous OS image.

At home, with Linux, I've done 3 different methods for backing out changes & updates. First method applies here, using a second OS partition for the backout plan. This is what I will describe for the Pinebook Pro, with Manjaro on eMMC. This can work for other Linux distros, but I will not be describing them at present.

It's a bit more clumsy on the Pinebook Pro right now, as we can't use Grub menus to select the prior OS in case of complete failure. If the default OS is completely un-bootable, then you have to boot and use a SD card to perform the change back.

To start, you need to re-partition your eMMC to something like below. If this is beyond your skill set, then it's likely the rest would be too.

part 1 - /boot
part 2 - / (root 1, about 15GB)
part 3 - / (root 2, same size as root 1)
part 4 - /comm (common for rest of the space)

What you call the "/comm" is up to you. I normally use the host name. Basically you should put your home directory, and other things that should be common for both OS images in a separate partition.

I will assume you have the root file system on partition 2 booting fine under Manjaro.

Manjaro uses the file system label in the U-Boot configuration file. So, we use a different file system label for the second root OS. Here we make a second file system, with different label, mount it and copy it.

I had recently seen the video by megi tweeted by pine64 of the pinephone displaying on a monitor, but there was no mention of the phone having a hardware mod.
https://twitter.com/thepine64/status/127...7726109696

Later I discovered on the wiki page that there was a hardware quirk that was discovered after the production of the CE version.
https://wiki.pine64.org/index.php?title=PinePhone_v1.2

A workaround is to desolder to switches.
https://wiki.pine64.org/index.php?title=...ONN_is_off
https://xnux.eu/devices/pine64-pinephone.html

But apparently this causes another issue when using a USB-C hub: "SD card reader not enumerating on PP with removed VCONN switches"
https://wiki.pine64.org/index.php/PinePh...patibility

So I have a couple of questions. I ordered my pinephone on may 21 with DHL shipping. I have not yet received DHL notification e-mail.
Do the shipped pinephones all have this hardware quirk?
Should I cancel my order and wait for a new pinephone revision?
Will there even be another revision?

I would really like to know, because I was really looking forward to this feature and cannot afford to buy more than one pinephone.

I've discovered quite a few ways that don't work...

Starting with the 0.10.12 ayufan arm64 builds, things work sanely, with the exception of deep sleep and sound.

Using the pbp-tools repo (thanks, those scripts are awesome!), I was able to build an updated 5.7 mainline kernel from the Manjaro git repos, which gives support for just about everything.  The postinstall script fixes sound, not that I really care too much about sound these days.

What I can't quite figure out the details for is the deep sleep mode.  It's not critical - I can live without it, but I'd like to have it working if possible, because that's the last step before it's "totally working."  The s2idle sleep mode works fine, but the deep mode doesn't.

I understand this is related to a lack of the binary bsp blobs in the bootloader regions, which on these images seems to be a 4MB partition starting at the standard 32kb offset.  I just don't quite understand where to find the BSP blobs, or how to arrange them in this 4MB region.

Is this documented anywhere?  I've found plenty of references to what to do, but not any specific steps of "You grab these blobs, arrange them this way, and it solves the problem."

Hello every one.

I would like to take a screenshot of my Pinephone UB port Edition (UBports 20200608-18105) from my cumputer (Kubuntu 18.04).

Is someone know how to do it?

With my android devices, I can do this with "Monitor" wich is included in Android Studio.

Anyway, thank you for reading, and have a nice day.

Let me know if anyone is willing to sell their pinephone the UBports edition is preferred. I will only send money through PayPal.

Found one