Would cpu rk3576 be suited for running a phone? My information is that the cpu rk3576 is able to run
on free software except from a ram training blob. Thank you.

I noticed mesa updated on my pinetab2, so i tried it out.

both mpv and browsers got a HUGE speed boost, with almost perfect video playback.

I would further recommend

Debian 13 / xfce with Daniel Thompon's ancient 5.7 kernel and updated touchpad firmware (too long ago that I remember the details).

Under xfce -> settings -> mouse and touchpad, I checkmarked "tap touchpad to click". Tap to click works with one finger taps, only. For 2 or 3 finger clicks, I need to press the touchpad.

On other computers running Debian / xfce, I can tap with two and three fingers as well.

What about you? Does it work for you on the Pinebook Pro and I just need to dig deeper?

Hello,
I just flashed postmarketOS onto my PinePhone Pro, and everything seems to be functioning well, except the OS can't detect the battery. There's no battery indicator in the top-right corner of the screen, and the settings menu shows 0% under Energy. I installed the PowerSupply app, but all the fields are displaying "N/A." I've checked to ensure the battery is properly seated and that the phone turns on when unplugged. I can't find any information about this issue. Has anyone else experienced this or know what might be causing it?

I'm still working full-time on my educational bare metal OS project for the PinePhone.  Zig has been a great match for this project, and with a sprinkling of arm assembly, the OS is now booting in 800ms!  Who needs modern hardware   

Anyway, I'm almost at the point where I can add some basic Apps, and then I'll have to think about distribution to a couple of colleagues for testing.

First I need to ensure my OS can only boot on the PinePhone v1.2b, since that is the only device I have for development.  Does anyone know if there there is a version string somewhere within the hardware?

The other unknown is U-Boot.  It seems to do a lot of the hardware configuration before it reaches my kernel code, and I am a little concerned that people might be running different versions from me (U-Boot 2020.07).  Currently I'm running from SD card, but maybe the boot process/chain is different once I figure out how to install my kernal onto the eMMC?

Do we know how many v1.2b devices were sold? and how long they will stay in production?  Since that obviously limits the scope of my project.  The device I have is continually out-of-stock, maybe already discontinued?  And the expensive model is currently $270, which is a bit of a worry when I see android 14 phones going for 79eur.  Are the PinePhones still selling?

Anyway, whatever becomes of this project, I wanted to thank the community for their support over the past 2 years.  It's a shame I didnt discover the PP sooner!  I was hoping to add LORA and Keyboard case support next, but just discovered they are no longer available

Just thought if anyone was thinking/trying to use a rock64 to control their 3d printers with Klipper / Mainsail over serial, that this might help
I did this with four rock64 v3 and got everyone working exactly like my pis, controlling 2 Prusa MK3S each.
I am not a Linux user, I managed to piece this together for the first one and the other 3 went smoothly following this.
Some of these steps may be redundant or unnecessary, but the result is that it works.

Base Setup:

Wipe SD card with SD Card Formatter
Download and use Armbian Imager to image SD
select board and OS
I used OS Minimal 25.5.1 bookworm

sudo apt update && sudo apt upgrade
sudo apt-get install git -y
sudo apt install network-manager
sudo reboot

Set up wifi dongle: (you may need specific firmware for brand if not Linux native. Mine was, I used a Ralink dongle)

nmcli device wifi list
nmcli dev wifi connect "Your_WiFi_SSID" password "Your_WiFi_Password"
nmcli device status
sudo reboot


Setup Mailsail and klipper, just follow prompts to install 1-3 or follow a guide for Kiauh:

cd ~ && git clone https://github.com/dw-0/kiauh.git
./kiauh/kiauh.sh
(install 1, 2, and 3)
sudo reboot
sudo apt update && sudo apt upgrade


Reduced bootup time for no Lan connection from 2min to 10 sec:

find / -name "systemd-networkd-wait-online.service"
(This should be the location, but confirm with the find)
sudo nano /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service

(add text under [Service])
TimeoutStartSec=10

(At this point you could run klipper over a usb to the printer
Mailsail/klipper web GUI is whatever IP the rock64 or wifi dongle grabs
It will be at the top of the screen when you ssh/login)

Tx/Rx setup on UART2/tty2:

sudo apt update && sudo apt upgrade

1.Overlays
sudo armbian-config
system>kernel>boot01
(added text to boot/armbianEvn.txt under overlay)
overlays=rk3328-uart1 rk3328-uart2 rk3328-uart3

2.Kernel
sudo armbian-config
system>kernel>ker001 - alt kernel
updated to the newest rock kernel

3.disabled console
sudo systemctl mask serial-getty@ttyS2

4. Added users to dialout group
sudo usermod -a -G dialout <username>
(confirm user is in dialout group)
groups

5. echo test with jumper if you want(jump the UART2 Tx and Rx pins(8,10) together with a wire, no ground needed)
sudo apt install picocom
sudo picocom -b 115200 -r -l /dev/ttyS2

Type anything, if writing appears port is working
ctrl a then ctrl x to exit

In your printer.config file under the MCU you will use
serial: /dev/ttyS2


Happy Printing!!!

Hi there!

Looks like L2000 gave out on my ROCKPro64:

   

The labeling says 3R3, which leads me to believe this is a 3.3uH inductor. There are three more inductors on the board with a label of 3R3, one in the same size and quite close (can be seen in the photo) and two more closer to the CPU, between the CPU and the PCIe port, which are smaller (3x3mm if I'd have to guess).

The schematics for the 2.1 board revision (mine has Rckpro64 V2.1 2018-07-02 printed on it) only show two 3.3uH inductors and if I'm reading the label correctly ("IND_3x3"), those would be the inductors between the CPU and the PCIe port.

By cross-referencing the V2.0 silk screen with the V2.1 schematic (risky, I know), I identified the damaged part as being L2000, behind the VCC5V0_SYS regulator. That seems plausible and fits my symptoms of random kernel panics (as far as I can tell, the CPUs power is derived from VCC5V0_SYS at some point).

However, the V2.1 schematic lists L2000 (and L2001) as 4.7uH inductors, while my board seems to have 3.3uH inductors in that place.

Is that a manufacturing error or is that a mistake in the schematics or did I do a mistake when identifying the problematic part?

I'm also looking for a replacement, and assuming that 3.3uH is correct, I'd think that MPL-SE4030-3R3 would be a good fit. If it should in fact be a 4.7uH, the MPL-SE4030-4R7 should fit the bill. At least those parts fulfill the current rating (3.3A) and the resistance (0.04Ohm) from the schematics.

Thanks for any insights,
jssfr

P.S.: I do not know what damaged that inductor in that way. I cannot imagine physical force alone, I suspect it got overloaded at some point, but I don't know with what. AFAICT, *that* 5V rail does not power the USB, so it can't be any USB peripherials. I do have some connected to the Pi header, but none of which should draw more than a few dozen milliamperes.

A pinephone pro having adequate software support in terms of hardware performance which iphone or android phone would the pinephone pro compare to?
Thank you.

In a blog it says pinephone pro was discontinued due to low sales. Since daily use level was never reached for the pinephone pro's software it is difficult to say if the pinephone pro could have gotten a market share. For free software people the pinephone pro would probably have been a best option buy.
Why did the pinephone pro never get proper software support? Was it too difficult technically to get the software ready? Could the software have been made had money been plenty? Thanks.

I have a Rock64 V3 I'm trying to use Klipper/MailSail on to replace a Pi w2 Zero, which has been running my coreXY printer over serial.
I can't seem to figure out the serial connection. I have gotten the Rock64 to run the printer with no problem over USB.

I'm not a strong Linux user, but I managed to make it to the very end here, but I can't get this last part to work.
I feel I'm either missing the correct terms in overlays/ the correct kerral header/ or some permissions or conflict.

I'm trying to use UART2, which are the same pins as the pi w2 zero. 6,8,10
I think I have the serial console disable. I ran:
sudo systemctl mask serial-getty@ttyS2
and see nothing on tty2 now when I run ls /dev/ttyS*

I added to armbianEvn.txt