I am interested in getting an OS built for Raspberry Pi 4 to run on a RockPro64.

https://github.com/Start9Labs/embassy-os

How does one begin that process? What steps are involved? Is there a "how to convert raspberry pi to rockpro64" guide somewhere?

Thanks!

I am angry at pine64 for still using paypal as the only option to pay, even with a creditcard.
I wanted to buy something that was only available on your general website and not the eu one, it forced me to use paypal and create an account.
Which i did. then it cancelled my payment because paypal wanted me to upload my ID card.
What is this for nonesense!
I tried for hours to close my paypal account.

Edit: i removed the i will never buy again part from the message, as soon as i can pay with just creditcard i would be happy to buy again. i was just angry paypal made the whole experience even worse than before! Its like they mis use the power that they are being given by people having to use them with creditcard payments.
Its so malicious!

Hello
My pinecill got burnt. I tried to fix it, me and other two electonicians, with no success. Will post a photo tomorrow.
It didn't work even 2 months
Buying again a new one is not an option for me, as for 25$ i paid another 25$ shipping and other 60$ customs.
Does anyone selling one from Europe?

Hi,


The Pine64 phones already support convergence. This is another way for convergence.
Some of you, maybe already familiar with Samsung DEX which used to support Linux.
Unlike Samsung,  we  make a Linux  distribution that runs on top of any
Android installation. Here is a clip of Linux desktop running on Motorola G100
which packs a powerful Snapdragon 870 CPU.

https://www.youtube.com/watch?v=PG5cKL9bnzY


Regards
Vasant

I am trying to do a Yocto build (kirkstone) for the sopine-a64 module using the SOPine Baseboard.

I have followed steps in the meta-pine64 repo here: https://github.com/alistair23/meta-pine64

The only exception is that I have specified the kirkstone branch where possible. I have also added console=tty0 to enable HDMI output.

Build Configuration:
BB_VERSION          = "2.0.0"
BUILD_SYS           = "x86_64-linux"
NATIVELSBSTRING     = "universal"
TARGET_SYS          = "aarch64-poky-linux"
MACHINE             = "sopine-a64"
DISTRO              = "poky"
DISTRO_VERSION      = "4.0.1"
TUNE_FEATURES       = "aarch64"
TARGET_FPU          = ""
meta
meta-poky
meta-yocto-bsp      = "kirkstone:4aeda14352a9fa9dd5ba50cf940a2b514fd1ac3c"
meta-oe
meta-python
meta-multimedia     = "kirkstone:fcc7d7eae82be4c180f2e8fa3db90a8ab3be07b7"
meta-arm-toolchain
meta-arm
meta-arm-bsp        = "kirkstone:a8cb33d5139e30b4a643da9a277487299c0e658f"
meta-pine64         = "master:96b5e55c25912c8bd80fbf0e537bf0d3519989ec"
meta-python2        = "kirkstone:f02882e2aa9279ca7becca8d0cedbffe88b5a253"


When I boot the resulting image (core-image-base), I see uboot text, then yocto splash screen. However, almost immediately the HDMI looses connection, but the board remains powered (LEDs on).

Has the kirkstone yocto build been verified with the meta-pine64 layer?

Hi,

some time ago, somewhere in the internet, I found a way to check the pinephone's hardware revision using the terminal.
I searched and searched, but I'm not able to find this anymore.

Does somebody have a clue how that can be done? I have two pinephones and I know, that one is revision 1.2a and one is 1.2b. I reinstalled OSes, had covers removed and played around.
I'd like to know again, which is which.

Thanks for your help!

Another community working mostly outside of the Pine64 forums is Maemo-Leste.  They take the very mature Maemo OS of the Nokia N900 and upgrade it with Deuvian(no systemd) to modern standards as well as adding apps from the rich Maemo mobile app repos.

I like the developed and alt flagship phone deployed UI much better than Phosh, has anyone else booted up an SD of Maemo-Leste for a test drive for function or for nostalgia?

https://talk.maemo.org/showthread.php?p=...ost1574282

Hello!

I find out quite good workaround for MMS if you have separate APN for Data and MMS.

If you wan't to find out more about this original issue see here:
https://gitlab.com/kop316/mmsd/-/issues/5
https://gitlab.freedesktop.org/NetworkMa...issues/958

So there is option in elogind that it will do something right before and/ord after suspending and this is what I am now using.

Firs you need to create bash script and for me this works:

I wanted to report a malfunction of the screen after 3 years of use.

White horizontal trace, a few centimeters long and one millimeter thick. Can only be seen in dark images. Faint blue artifacts above and below the line, and to the left. Does not prevent colors from being displayed, but the screen cannot display dark colors in this area.

I guess there is not much to do.

After an upgrade, I came back and the phone was dead. I've tried several of the troubleshooting techniques on the Wiki, but the device is completely unresponsive. Even plugged in and with a new SD Card. 
I tested the battery and there is a ~3.0V charge. Documentation says 3.3V is needed, but I'm not sure why the device is complete dead. 

Please help. Thank you.