Greetangs bredren,

It used to be that

I know the PBP is not ideal for modeling but I use it to practice while I learn and to tinker with ideas when away from the desktop.  Recently an update to Manjaro moved to a new version of python and freecad would no longer work.  I solved the problem with this thread: https://forum.manjaro.org/t/rolling-back...sion/52985 and pyenv.  I am just kind of wondering if there is a more elegant solution to this.  I had thought I could roll back with pacman, but the linked thread says that manjaro considers python to be a system component, and I worried that a rollback may break something else.  BTW, the flatpak for freecad could not be installed, and IIRC the snap was also a dud.  I think they may not be maintained any longer, so I am glad I found any kind of solution at all.

On another note , freecad has a fork that sounds interesting: https://github.com/realthunder/FreeCAD_a...3/releases.  When I have a minute I will try the x86 AppImage, but I do not have confidence that it will work on the PBP.  Is it possible to recompile from source for something like this, or will I be throwing away my time? Thanks in advance.

Picked up an S20 Ultra battery case with 8,500 mAh battery. I've left my Pinephone Pro off the charger for two days straight without charging and it's still at 100% with battery case showing only 50% capacity. Combined the Pinephone Pro's battery 3,000 mAh battery with the extended battery case 8,500 mAh battery gives the Pinephone Pro a whopping 11,500 mAh charge to work with. I've used about 3 hours screen on time both days (6 hours screen time total) without seeing much drain at all, and this is with suspend completely disabled.

While the official Keyboard case does offer a similar solution with a 6,000 mAh battery, I decided having a keyboard in my face in public is not ideal.

The buttons line up perfectly with the case buttons, but has a half inch gap at the top between case and phone. Also be aware the thickness of the phone is doubled to almost the size of the keyboard case and does add a little extra weight but feels durable.

The case, however, offers no protection if your phone would to fall screen face down, so be aware of this as well.

I've had the charging case for 48h on Manjaro so reliability and lifespan of the case still hasn't been assessed, but for $25 I feel it's pretty low risk. The case takes about 6-8 hours to charge from zero but this fine for an overnight charge while sleeping --did this as soon as I got it. You do not need to take the phone out to charge case.

The Pinephone Pro in this case seems to only reliably work in Manjaro at the moment as Arch power management is still early and drains faster than the case can charge it, but this is a bug which should be worked out soon. Have not tried with Postmarket or Mobian. I've also not tested peripherals such as OTG cables / hubs in the USB C port but will report back once I've done so.

The battery can be toggled with the power button on the back and Manjaro will report immediately when charge is active. Turn it off if you wish to power the phone down as the constant charge causes the phone to boot again

Here is a link to the case if anyone is interested:
https://www.amazon.com/dp/B08ZN5416W/ref...UTF8&psc=1

Pictures below: - ignore 80% charge, was running Arch at the time.



 


Feel free to ask any questions I didn't address here and I'll do my best to answer them.

It looks like there are about 10 OS teams and several desktop teams working on software for each OS.  They are, of course, working toward making PPP a functional smart cell phone.  Success will depend upon the magnitude of the effort put in.

Are they volunteers?  I think not. Are they professional programmers?  I think so.

Is Pinephone paying for their time?  Are the OS and Desktop companies paying for their time?

One contributor to this site says "Donate to support your favorite OS team". What are the details of that?

Overall question is how is the PPP optimization effort being funded?

Any insights anyone?     tom kosvic

Made this bsp/sdk because the beta wich is on the site don't makes a image wich you can flash and boot from sd/emmc
and while mainline is cool a working bsp/sdk makes it more complete for me

I looked how raxda and firefly made their bsp/sdk and made a custom one for the Quartz64
used some scripts of them and adjusted so they work to build a image
Most sources are from rockchip and the just 2 or 3 comes from other sources (from firefly: rawimg script, qsetting and camera_engine_rkaiq package)
So i tried to keep it some kind rockchip original and those packages were not on the rockhcip site or other open places so if it is a problem i can remove them

The bsp/sdk builds a buildroot ,debian or yocto distro wich you can flash on a sd/emmc or rockchip images to do it the difficult way
the hardest part was to get the right revisions to make some packages work

The bsp/sdk has 2 kernel options kernel 4.19.19 or 5.10.66 from rockchip sources

the 4.19 is common used kernel for the rk3566/68 bsp/sdk kernel and it has
working hdmi,lan,usb,wifi,gpu and npu

* 4.19.219-2022-01-18

the 5.10 is a newer(experimental) one it is for the coming rk3588 and proberly for the newer android 12 rk3566/68 no confirmation but saw some info
working hdmi,lan,usb,gpu

* 5.10.66-2022-01-18

!! keep in mind 5.10 is way from stable npu crash no video but hdmi works !!!

pcie and bluetooth not tested
not included lcd,touchscreen (just broke one)

Uboot

just the latest from 2022-02-11

the distros have some simple usage and some test files are included like for the video ,gpu npu,wifi etc

Sure it it is far from perfect but at least it works to make a image

*** ADDED ***
Added buildconfigs for other pine boards with a rk356x  PineNote ,Quartz64-b and Soquartz
!!! DTS files not included only added a pinenote dts the soquartz and quartz64-b are just quartz64-a dts !!
so if you got a dts for dowmstream kernel bards you can add them

so instead of

quartz64-rk3566-buildroot-k4.mk
 you do
quartz64b-rk3566-buildroot-k4.mk        For building a Quartz64-B image
or
pinenote-rk3566-buildroot-k4.mk         For Building a Pinenote image
or
soquartz-rk3566-buildroot-k4.mk         For building a Soquartz image

and same for

quartz64-rk3566-raw-k4.mk

quartz64b-rk3566-raw-k4.mk        For building a Quartz64-B  SD-image
or
pinenote-rk3566-raw-k4.mk         For Building a Pinenote SD-image
or
soquartz-rk3566-raw-k4.mk         For building a Soquartz SD-image


*Needed*

Time
Ubuntu 18.04 or 20.04
at least 200+GB of free space (yeah it likes to grow maybey more)

*Building*

#Packages Needed on pc

sudo apt-get install repo git ssh make gcc libssl-dev liblz4-tool \
expect g++ patchelf chrpath gawk texinfo chrpath diffstat binfmt-support \
qemu-user-static live-build bison flex fakeroot cmake gcc-multilib g++-multilib \
unzip device-tree-compiler python-pip ncurses-dev python-pyelftools

*Download BSP*

#make bsp/sdk folder

mkdir Quartz64

#go to Quartz64 folder

cd Quartz64

# make .repo folder

mkdir .repo

#go to .repo folder

cd .repo

#download repo

git clone https://github.com/rockchip-linux/repo
or
git clone https://gerrit.googlesource.com/git-repo repo

#make repo executable

chmod a+rx repo/repo

#go back

cd ..

# Download repo manifest

.repo/repo/repo init -u https://github.com/Shaggy013/manifests -b master -m rk356x_linux_custom_v1.2.8_20220309.xml

# Dowload bsp/sdk

.repo/repo/repo sync --no-clone-bundle

***** trouble ****
if it gives trouble about github account
https://elinux.org/Buildroot_how_to_contribute
configure section
**** only by trouble ****

Now you see that your Quartz64 folder is full with new folders and files
your Download is finished

*Building*

There are 4 distros you can build Buildroot,Debian,Ubuntu and Yocto
You can choose to make the distro against the 4.19 or 5.10 kernel

First you choose wich kernel

#for 4.19

./build.sh quartz64-rk3566-buildroot-k4.mk

#or 5.10

./build.sh quartz64-rk3566-buildroot-k5.mk

For the first time you have to do it twice the first time can give a error

you see something like this

***** example ****
processing option: quartz64-rk3566-buildroot-k4.mk
link kernel to proper kernel-directory
renew kernel to proper kernel-directory
link kernel 4
link Debian to proper Debian-distro
renew Debian to proper Debian-Distro
link debian to bullseye or buster
link kernel 4
switching to board: /home/thc013/corner/Quartz64-release/device/rockchip/rk356x/quartz64-rk3566-buildroot-k4.mk

****** example ****

so now you bsp is set to the right options

You have multiple options but you have to make a uboot,kernel and recovery and a rootfs so the best start is just as a base for the later buiding of distros

# build all (uboot,kernel,recovery,rootfs"buildroot",rockchip image) / AKA BUILDROOT

./build.sh

**Info**
For the 4.19 kernel you get after a few minutes a blue screen where you have to give the right voltage for the io-domains
watch carefull some domains are not asked
the domain info comes from the schematic or the dts file

pmuio1-supply = <&vcc3v3_pmu>; not asked
pmuio2-supply = <&vcc_3v3>;
vccio1-supply = <&vccio_acodec>; 3,3
vccio2-supply = <&vcc_1v8>; not asked
vccio3-supply = <&vccio_sd>; 3,3
vccio4-supply = <&vcca1v8_pmu>;
vccio5-supply = <&vcc_3v3>;
vccio6-supply = <&vcc1v8_dvp>;
vccio7-supply = <&vcc_3v3>;
After that the buildroot will start the rest of the building
****

Depening on the speed of your pc it takes from a hour to ?
so after some coffee and some heat for the cold weather you get

Now it build a rockhip image DO NOT FLASH TO SD !!!!!!!!

Make buildroot image ok!
..../Quartz64/rockdev/pack/QUARTZ64-RK3566-BUILDROOT-K4-GPT-!DATE!-2137.img

Now it builds a rockhip image DO NOT FLASH TO SD !!!!!!!!

#change to the SD/EMMC IMAGE option

.#for 4.19

./build.sh quartz64-rk3566-raw-k4.mk

#or 5.10

./build.sh quartz64-rk3566-raw-k5.mk

#Build image

./build.sh rawimg

***Info ***
Make raw image ok!
..../Quartz64/rockdev/pack/QUARTZ64-RK3566-RAW-K4-GPT-!DATE!-2137.img

Now you can flash that image RAW to a sd or EMMC with your desired tool Etcher,dd etc

*****

Now you can build a Debian or a Yocto image

**** DEBIAN ******

#for 4.19

./build.sh quartz64-rk3566-buildroot-k4.mk

#or 5.10

./build.sh quartz64-rk3566-buildroot-k5.mk

!!
before building you have to install extra packages they differ from ubuntu and debian so you have to install or overwrite them first

sudo apt-get install binfmt-support qemu-user-static
sudo dpkg -i ubuntu-build-service/packages/*
sudo apt-get install -f


# build Debian rootfs

./build.sh debian

Now it build a rockhip image DO NOT FLASH TO SD !!!!!!!!

#change to the SD/EMMC IMAGE option

.#for 4.19

./build.sh quartz64-rk3566-raw-k4.mk

#or 5.10

./build.sh quartz64-rk3566-raw-k5.mk

#Build image

./build.sh rawimg

***Info ***
Make raw image ok!
..../Quartz64/rockdev/pack/QUARTZ64-RK3566-RAW-K4-GPT-!DATE!-2137.img

Now you can flash that image RAW to a sd or EMMC with your desired tool Etcher,dd etc

Same as rest /Quartz64/rockdev/pack/

**** Ubuntu ******

#for 4.19

./build.sh quartz64-rk3566-buildroot-k4.mk

#or 5.10

./build.sh quartz64-rk3566-buildroot-k5.mk

!!
before building you have to install extra packages they differ from ubuntu and debian so you have to install or overwrite them first

sudo apt-get install binfmt-support qemu-user-static
sudo dpkg -i ubuntu-build-service/packages/*
sudo apt-get install -f

# build Ubuntu rootfs

./build.sh ubuntu

*** This build option ask after a few minutes the keyboard and region settings ****

Now it build a rockhip image DO NOT FLASH TO SD !!!!!!!!

#change to the SD/EMMC IMAGE option

.#for 4.19

./build.sh quartz64-rk3566-raw-k4.mk

#or 5.10

./build.sh quartz64-rk3566-raw-k5.mk

#Build image

./build.sh rawimg

***Info ***
Make raw image ok!
..../Quartz64/rockdev/pack/QUARTZ64-RK3566-RAW-K4-GPT-!DATE!-2137.img

Now you can flash that image RAW to a sd or EMMC with your desired tool Etcher,dd etc

Same as rest /Quartz64/rockdev/pack/



***** YOCTO *****
!!! Yocto can take a time to build the toolchain has also clang etc included !!!

#for 4.19

./build.sh quartz64-rk3566-buildroot-k4.mk

#or 5.10

./build.sh quartz64-rk3566-buildroot-k5.mk

# build Debian rootfs

./build.sh yocto

Now it build a rockhip image DO NOT FLASH TO SD !!!!!!!!

#change to the SD/EMMC IMAGE option

.#for 4.19

./build.sh quartz64-rk3566-raw-k4.mk

#or 5.10

./build.sh quartz64-rk3566-raw-k5.mk

#Build image

./build.sh rawimg

***Info ***
Make raw image ok!
..../Quartz64/rockdev/pack/QUARTZ64-RK3566-RAW-K4-GPT-!DATE!-2137.img

Now you can flash that image RAW to a sd or EMMC with your desired tool Etcher,dd etc

Same as rest /Quartz64/rockdev/pack/

***** BUILD OPTIONS ****

Available options:

*.mk              -switch to specified board config
launch              -list current SDK boards and switch to specified board config
uboot              -build uboot
spl                -build spl
loader            -build loader
kernel            -build kernel"
modules            -build kernel modules
modules2          -build kernel modules to rockdev/pack/modules *added*
toolchain          -build toolchain
extboot            -build extlinux boot.img, boot from EFI partition
rootfs            -build default rootfs, currently build buildroot as default
buildroot          -build buildroot rootfs
ramboot            -build ramboot image
multi-npu_boot    -build boot image for multi-npu board
yocto              -build yocto rootfs
debian            -build debian 9 or 10 rootfs !! set in config !! !! only bullseye included
ubuntu            -build Ubuntu 20.04 rootfs !! set in config !! !! only focal included
pcba              -build pcba not tested
recovery          -build recovery
all                -build uboot, kernel, rootfs, recovery image
cleanall          -clean uboot, kernel, rootfs, recovery
firmware          -pack all the image we need to boot up system
updateimg          -pack update image not tested
rawimg            -pack raw image
otapackage        -pack ab update otapackage image (update_ota.img) not tested
sdpackage          -pack update sdcard package image (update_sdcard.img) not tested
save              -save images, patches, commands used to debug
allsave            -build all & firmware & updateimg & save
check              -check the environment of building
info              -see the current board building information
app/<pkg>          -build packages in the dir of app/*
external/<pkg>    -build packages in the dir of external/*

**** Examples ****

For if you made changes to uboot or the kernel
buildroot is another story

#u-boot

./build.sh uboot

#kernel

./build.sh kernel

#recovery

./build.sh recovery


***** Making modules from the kernel ****
it can be that you want to copy or have some kernel modules to copy to your image

./build.sh modules2

makes in the folder rockdev/pack/modules the kernel-modules

**********************************************************************************************************************

****** TESTS ******

the distros all contain a folder rockchip test with some simple demos and test even a benchmark

cd ~/rockchip_test

# some test options

./rockhip_test.sh

The npu video and gpu are most fun

********

ddr test :                  1 (memtester & stressapptest)
cpufreq test:              2 (cpufreq stresstest)
????flash stress test:          3
# not working # bluetooth test:      4 (bluetooth on&off test)
# not working # audio test:          5
recovery test:              6 (default wipe all)
suspend_resume test:        7 (suspend & resume)
wifi test:                  8
ethernet test:              9
auto reboot test:          10
ddr freq scaling test       11
#not working # npu test              12
npu2 test                  13 (rk356x or rk3588)
??? camera test                14 (use rkisp_demo)
video test                  15 (use gstreamer-wayland and app_demo)
gpu test                            16 (use glmark2)
# not working# chromium test          17 (chromium with video hardware acceleration)"
nand power lost test:       18

*****

************ Last Info ******

That is almost step for step i hope
it just started with a dts and boardconfig but got a little bigger
if i made any faults or i missed something please let me know
no debug program just plain doing diff,reading(there is a lot),copy paste and some simple adjustments to make it work for me
well it was something diffrent as making a custom limo os for the limo M1 360 from vodafone in 2009 (got first to root cdc_nand) gone glory
the sources and info you can all find them on google and github and gitlab

so no OFFICIAL ROCKCHIP or QUARTZ64 JUST !!CUSTOM!!


I will include download links with the images it compiles

and to make it work for another 3566 or 68 just make a boardconfig.mk in ?/Quartz64/device/rockchip/rk356x/
and make sure the defconfigs and dts are inthe right places
well at least it gets you on the way

SPECIAL THNX TO quartz64 chat , my free time ,a quartz64 too stay still alive ,ryzen 3700x+5700xt to keep me warm,20TB nas for the space,R.I.P sd (2),touchscreen,monitor and OPI4 (well the opi semi dead dont fuss with the fusb32 in uboot )


DOWNLOAD

# Buildroot 4.19
https://drive.google.com/file/d/1xdv4Tid...sp=sharing

# Yocto 4.19
https://drive.google.com/file/d/1sqNHhae...sp=sharing

# Debian Bullseye 4.19
https://drive.google.com/file/d/1GQV98SA...sp=sharing

*******

#Buildroot 5.10
https://drive.google.com/file/d/1_rK2d5t...sp=sharing

#Yocto 5.10
https://drive.google.com/file/d/1kRkdwrT...sp=sharing

#Debian Bullseye 5.10
https://drive.google.com/file/d/1kguM3XA...sp=sharing

Hello, I'm new to Pine boards and am not sure how I should/can do my installation. I've got a 128 gb ragepro USB stick that I want all my things saved too but I also have a 32 microSD sitting around. So i'm wondering if I should just flash my usb stick or flash my microSD and then just plug my usb in? If the answer is just flashing my USB how would I boot from my USB? 

Thank you for the help.

I'm currently on PostmarketOS with Phosh, and the battery indicator always says it is "charging", even when it's unplugged.  I believe this was also happening on the Manjaro ARM+Plasma Mobile image that shipped on the device, but I didn't check it out in detail.

`/sys/class/battery/status` always says "Charging" too, which I'm guessing is closer to the root cause, but `/sys/class/rk818-charger/status` does update correctly.

Is there a kernel module known to be incomplete here that I could look into?  I'm an experienced software engineer but have not had to dive into this sort of thing in the past, so a starting point would save me a lot of time 

This is probably worth a separate post, but the phone is consistently pretty warm when off the charger and drains the battery pretty quickly.  I'm hoping that maybe the "charging" indication is related; maybe it's not managing power as intended just because it thinks it's plugged in.  At any rate, seems worth getting the charging state to work before trying to work around it in power management.

Thanks!

Something that does not seem to be currently available, even for TS100, is heat set insert tips, especially for M3, M4, and M5 brass heat set inserts. I hate having to break out my old soldering station when I want to place inserts in a plastic part. Right now I am just using a cone tip for it, but it doesn't align the insert properly.

Almost everytime after running a 'sudo apt update' I get this error about flatpak:

** (appstreamcli:4670): WARNING **: 11:33:51.773: Found icon of unknown type 'unknown' in 'system/flatpak/flatpak/cc.nift.nsm/*', skipping it.

** (appstreamcli:4670): WARNING **: 11:33:51.773: Found icon of unknown type 'unknown' in 'system/flatpak/flatpak/cc.nift.nsm/*', skipping it.


Should I be worried?

I was looking at: https://wiki.pine64.org/wiki/PinePhone_P...er_Edition  and I saw that the adb tools could be used on the PPP developer edition.

I have my samsung android phone set with developer options open so I can delete google garbage etc.  I use adb tools to do the debloating.  I had no idea adb would run on the PPP.  I thought that they were specific to android.

Can/how do I activate developer mode on the Explorer edition?  I can't see any way to do that in settings as there is in android settings.  Is there a method to activate developer mode?

thanks,      tom kosvic