Hello to everyone.

I want to assemble some kind of tablet powered by FreeBSD. The main electronic components of this tablet that I've bought or that I want to buy in the next future are the following :

1) soc = RockPro64 (Rockchip RK3399 hexa-core SoC) : already bought

2) this enclosure : (already bought)

https://ameridroid.com/products/pine64-p...eq=uniform

3) these batteries : https://www.ebay.com/itm/315203768497 ---> not yet bought

Since I want to create a "tablet" that will be powered by FreeBSD,I need an USB display that does NOT requires any driver to work and the size should fit with the enclosure at point 2 that I like ; because I'm not a programmer, I will be not able to make the porting of a driver from Linux to FreeBSD. I also would like to reuse the screen for different projects,so it is great if it can be powered and work only connecting the HDMI cable from the screen to the soc.

Can someone suggest to me one ? thanks.

I see this part is out of stock.  Will it be in stock again at some time?

I have two Pinebooks Pro on which the left hinge has broken free.  I assume that the Bottom Case is all I'll need to fix these. Or is it just the magnesium cover? (I don't need that)
Maybe the palm case is what I need. Is it possible to get two? @tllim I see there is a limit of one.

Hello to everyone.

I want to assemble some kind of tablet. The main electronic components of this tablet that I've bought or that I want to buy in the next future are the following :

1) soc = RockPro64 (Rockchip RK3399 hexa-core SoC) : already bought

2) this enclosure : (already bought)

https://ameridroid.com/products/pine64-p...eq=uniform

3) these batteries : https://www.ebay.com/itm/315203768497 ---> not yet bought

4) this display : https://www.waveshare.com/product/displa...onitor.htm (not yet bought)

Since I want to create a "tablet" that will be powered by FreeBSD,I need an USB display that does NOT requires any driver because I'm not a programmer. I will be not able to make the porting of a Linux driver to a FreeBSD.


1) I'm not sure if the display at point 4) is a good display for me because I don't understand if its size can match with the size of the enclosure at point 2.

2) I'm not sure if it can be powered by the USB port of the RockPro64 and it is ready to work

3) Eventually I want to reuse it for another device,so I don't want to be forced to use a special connector that will work only on the RockPro64 RK3399. I hope there isn't the needing to use a special connector / adapter that could even requires a driver.

That's all. If you think that the display suggested by me is not good,please explain to me why and suggest me another display that can work. Very thanks.

Hello Pine64 community,

I'm looking for a virtual number app to use on my phone, primarily for account verifications and potentially for small business purposes later on. Ideally, the app should be easy to use, have good privacy features, and if possible, offer a free trial or some bonus credits.

Has anyone here tried an app that they’d recommend? I'd really appreciate any advice or experiences you can share!

Thanks in advance for your help!

Hello,
I recently purchased a Pinecil to repair my headphones.

Before tackling the headphones, I practiced soldering jump wires to a proto board. While the soldering process itself was quick and neat, the desoldering proved to be quite a challenge. I spent an hour and a half trying to desolder a jump wire at 400°C, but I was unsuccessful. The solder just wouldn't adhere to the desoldering braid, and even when it did, it would immediately get stuck, preventing me from heating it enough to return to a liquid state.

Could my struggles with desoldering be due to using a 45-watt power supply? Would switching to a 65-watt supply make a difference?

I wasn't paying attention and accidentally installed Factory SailfishOS and overwrote the Tow Boot, I attempted to finish the installation and click the two prompts after clicking "whatever" part 1 and where it asked if I wanted to encrypt phone which I chose no then told me to Reboot after it was done processing. 

Now all it does when I power on is the green led just flickers a few times and that's it.

But when what I want to do is install Ubuntu Touch.

Do I need Tow Boot or uBoot

I just got a new main board of the PPP and replaced it from old broken one.
After replacement of the main board, my PPP only boots into AOSP android after displaying "Rockchip kernel" splash.
I tried with powering on with volume-down button, couldn't boot. With volume-up button, it goes into the android recovery mode,
I also tried with RE-button, but I got no response.

Is there any way to boot from MicroSD? 

Certainly I know you boot the phone and hold vol + until it turns blue, (I have towboot), but I accidentally let my battery die and got stuck in a boot loop, ordered an external battery charger, to help with getting a full charge.

I flashed one image via BalenaEtcher and a MicroSD reader and pressed vol -, but I get an error message.

Still if I try Vol + the phone just reboots and doesn't stayed on, so I can't flash the image to the card that way via BalenaEtcher

Earlier this year, there was an update to the Linux kernel that broke booting Rock64 from their eMMC and it was necessary to force using an older, working kernel version.  It's since been fixed, but in case there is again a need to boot with a kernel older than the latest, here's one way:



Drop a file in /etc/flash-kernel/ubootenv.d that forces the U-Boot environment variable fk_kvers to a working kernel version present in your /boot, then run flash-kernel to regenerate the U-Boot bootscript /boot/boot.scr





echo "env set fk_kvers 6.1.0-22-arm64" > /etc/flash-kernel/ubootenv.d/90-force-kernel-version &&

flash-kernel



When you want to stop forcing the kernel version, remove /etc/flash-kernel/ubootenv.d/90-force-kernel-version, run flash-kernel, and reboot



This works because flash-kernel rebuilds /boot/boot.scr from the template /etc/flash-kernel/bootscript/bootscr.uboot-generic, and this includes "@@UBOOT_ENV_EXTRA@@", which gets replaced by the contents of each of the files in /etc/flash-kernel/ubootenv.d/ and the boot script boots the referenced kernel