Pineport

Sixteen essays

Setup

Kernel

Bluetooth

Closing

Board index

PinePhone Pro

The RK3399S phone index: live hardware status, board references, and the pages that describe the active FreeBSD bring-up.

PinePhone Pro remains the active bench target. It is where the port already boots, builds confidence from hardware receipts, and proves the mobile stack before the same habits move to PineTab2.

Boot and access

● working

SD boot, EFI framebuffer console, serial after boot, and USB gadget networking are the stable base for phone-side work.

Display and input

● working

Framebuffer display, Sway on scfb, Goodix touch, GPIO power key, SARADC volume keys, and RGB LED control have hardware proof.

Wireless and audio

◐ partial

Native WiFi, Bluetooth attach, A2DP, RT5640 playback, and loudspeaker routing exist, but still need hardening and upstream-quality cleanup.

Phone hardware

◐ partial

USB-PD sink policy, EG25-G modem control, battery/charger policy, cameras, sensors, suspend, and long-run reliability remain open.

Reading Order

Start here when you want the phone-specific material without the tablet references mixed in.

/appendix/pinephone-pro-hardware Hardware reference Board-specific RK3399S phone manifest, separated from PineTab2 work. /appendix/components Component matrix PinePhone Pro component status, driver candidates, and follow-up targets. /appendix/pinephone-pro-schematic-map Schematic support map Board-level grouping by power, display, touch, audio, wireless, modem, sensors, and indicators. /essays/14-where-we-are Current status essay Narrative snapshot of what is working, partial, blocked, or deliberately deferred. /essays/15-whats-next Next work essay Roadmap for phone-side finishing work and PineTab2 phase boundaries. /appendix/hardware/#pinephone-pro-rk3399s Combined hardware manifest Cross-board lookup table when phone and tablet wiring need to be compared.

Appendix Entries

These are the PinePhone Pro pages currently registered in the site navigation. New phone-specific reference pages should be added here before they get mixed into shared appendices.

  1. PinePhone Pro hardware reference RK3399S phone manifest, separated from the PineTab2 tablet work.
  2. PinePhone Pro component support matrix Every chip, sensor, and on-SoC block on the RK3399S phone — with FreeBSD driver status, our-tree path, and upstream reference.
  3. PinePhone Pro schematic support map Board-level features from the public PinePhone Pro schematics, mapped to FreeBSD support status and work logs.

Current Rule Of Thumb

Keep turning phone subsystems from "proved once" into repeatable drivers with narrow, reviewable contracts. The highest-value work is still reliability: WiFi, modem policy, battery/charger state, audio routing, and long-run graphical stability.