PINE64 - User contributions [en]

PinePhone Pro/IMX258 Camera Debugging

2022-07-02T23:07:58Z

Memleek: explain better how one figures out what function is responsible for frame completion notification

{{Under construction}}

== Background ==

The Pinephone Pro's rear camera is a Sony IMX258. The camera driver is present upstream, and at least [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro Manjaro's kernel] (downstream of Megi's) enables the driver. The camera does not seem to work; this page catalogs work on figuring out why.

== Initial status ==

What do we see in dmesg?

<pre>
imx258 1-001a: supply vana not found, using dummy regulator
imx258 1-001a: supply vdig not found, using dummy regulator
</pre>

This tells us the kernel loads the driver, which is something.

Are these errors bad/fatal? Inspecting the [https://github.com/megous/linux/blob/orange-pi-5.17/drivers/media/i2c/imx258.c source] shows us that these supplies are defined in the <code>imx258_supply_names</code> array, and <code>imx258_probe</code> calls <code>devm_regulator_bulk_get</code> to set them up.
<code>imx258_probe</code> checks the return code from <code>devm_regulator_bulk_get</code>, emitting a fatal "Failed to get supplies" message if the return code is negative (indicating failure). Since we don't see this message (or any others from the driver), it looks like it loads successfully!

=== How can we test the camera? ===

==== Megapixels ====

[https://gitlab.com/postmarketOS/megapixels Megapixels] requires a per-device file to configure cameras. This one isn't complete (most of its numbers are complete nonsense), but it should let us see what happens when Megapixels tries to access the camera:
<code>pine64,pinephone-pro.ini</code>:
<pre>
[device]
make=PINE64
model=PinePhone Pro

[rear]
driver=imx258
media-driver=rkisp1
capture-width=4208
capture-height=3118
capture-rate=60
capture-fmt=GRBG10P
preview-width=1280
preview-height=960
preview-rate=60
#preview-fmt=BGGR8
capture-fmt=GRBG10P
rotate=90
mirrored=true
focallength=2.6
cropfactor=12.7
fnumber=2.8
flash-display=true
</pre>

This segfaulted Megapixels for me. After patching some trivial segfaults, I get fatal GTK4 issues and other tangential problems. Let's try something else.

==== Manually setting up a camera pipeline ====

We can roughly follow [https://www.kernel.org/doc/html/latest/admin-guide/media/rkisp1.html this guide]. Doing so gives us the following commands:
<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=800,height=600,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--verbose"
</pre>

Careful readers will note that this is setting the camera up with a low resolution compared to what the sensor can do. For some reason I can't get the rkisp1 node to configure its sink pad with the maximum resolution of the sensor (4208x3118). Instead, it sets itself to 4032x3024. This mismatch is forbidden and causes v4l2 to give us EPIPE when we try to enable the stream. Using the lower resolution gets us further--the last command (which attempts to save a single frame of video) gives output like this:
<pre>
VIDIOC_QUERYCAP: ok
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
</pre>

But then it just hangs there indefinitely.

Running under strace, we see the program stuck in an ioctl:
<pre>
ioctl(3, VIDIOC_DQBUF, {type=V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE
</pre>

[https://www.kernel.org/doc/html/v4.13/media/uapi/v4l/vidioc-qbuf.html VIDIOC_DQBUF] corresponds to dequeuing a buffer once it has been filled with an image by the v4l2 device. Apparently, the device never gives us back a captured frame.

=== Now what? ===

==== Does i2c work at all? ====

The camera driver uses i2c; we can see the camera [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts#L890-L914 in the .dts] to determine that it's on i2c bus 1, address 0x1a.

The imx258 is controlled over i2c, and sends image data over MIPI. The first step is to see if the i2c control is working.

Looking back at the driver, it seems we should see errors in dmesg if i2c communication fails. The driver checks the chip id in its probe function, which uses i2c, so we can conclude that i2c gets set up properly initially. Does it keep working?

==== Does i2c keep working? (FTrace) ====

We can see if other functions that use i2c produce errors--for example, when we run our <code>"v4l2-ctl" ... "--stream-mmap"</code> command, we expect that <code>imx258_start_streaming</code> will get called, and this function also writes a load of registers over i2c.

Build and install a kernel with CONFIG_FTRACE (not hard, but outside the scope of this write-up) and enable function graph tracing:
<pre>
$ sudo su
# cd /sys/kernel/debug/tracing
# echo function_graph > current_tracer
# cat available_filter_functions | grep -E 'rkisp|imx258|v4l2' | awk '{print $1}' > set_graph_function
# echo 'vm_map_pages,__iommu_map,iommu_map_sg_atomic,rk_iommu_map,__alloc_pages,dma_alloc_attrs,dma_mmap_attrs,__vm_map_pages,vb2_mmap,clk_e,able,schedule_timeout,clk_disable,regmap_write,schedule,__i2c_tra,sfer,i2c_tra,sfer_buffer_flags,dma_free_attrs' | tr , '\n' > set_graph_notrace
# tee trace_pipe > ~/function-trace.log
</pre>

Now, in another terminal session, run the <code>"v4l2-ctl" ... "--stream-mmap"</code> command again. We end up with a bunch (but hopefully not *too* much) of output in our first terminal and the <code>~/function-trace.log</code> file.

A quick grep shows that <code>imx258_start_streaming</code> is indeed called, so '''i2c is working properly'''.

=== If i2c works, what doesn't? ===

Our program that asks for a video frame is still hung! We ask the camera to start streaming frames, it presumably does, but the v4l2 stack never tells us a frame has finished. Doing some digging in the v4l2 stack (and the rkisp1 driver), we find out that rkisp1 is notified about frame status via interrupts. We figure this out by manually backtracking through the code to see when <code>vb2_buffer_done</code>, the function in the vb2 API to call when a frame is finished, would be called. In the rkisp1 code, <code>vb2_buffer_done</code> is only called from <code>rkisp1_handle_buffer</code> which is only called from <code>rkisp1_capture_isr</code>, which (for the PPP's rk3399 SoC) is only called from <code>rkisp1_isr</code>, which is an interrupt handler. We know that it's an interrupt handler from the name (<code>_isr</code>), but also because it gets passed (indirectly) to <code>devm_request_irq</code> by way of being the <code>.isr</code> field of <code>rk3399_isp_isrs</code>.

Perhaps the hardware is never actually emitting the interrupt that signals a frame being finished. Indeed, grepping our FTrace log shows that <code>rkisp1_isr</code> is never called. A quick look at <code>/proc/interrupts</code> shows that '''the only interrupt associated with the isp has never triggered''' (0 count on every CPU):
<pre>
# head -n1 /proc/interrupts; grep isp /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
57: 0 0 0 0 0 0 GICv3 75 Level ff914000.iommu, rkisp1
</pre>

=== <code>rkisp1</code> debugfs info ===

The <code>rkisp1</code> driver keeps some [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/drivers/media/platform/rockchip/rkisp1/rkisp1-common.h#L335-L363 error/debug counters] in debugfs, which can be viewed at <code>/sys/kernel/debug/ff910000.isp0</code>.

Sadly, the only one of these that comes up nonzero is <code>sp_stop_timeout</code> ("upon stream stop, the capture waits 1 second for the isr to stop the stream. This param is incremented in case of timeout"). I observe it to increment once per time I terminate the <code>"v4l2-ctl" ... "--stream-mmap"</code> command. This tells us what we already know: interrupts are not firing, but it also tells us that we aren't hitting any other errors that rkisp1 knows about.

== Next steps ==

Where do we go from here? I don't know--something may be wrong with the way the .dts specifies interrupts, some kind of firmware/GIC (the rk3399's interrupt controller) configuration issue, or something else. It would be good to try to determine:

* Whether the MIPI lines actually show traffic, if someone has a logic analyzer and a dissected PPP.
* Whether the DMA of frames to memory actually happens, regardless of (lack of) emission of the interrupt that tells us when said DMA finishes a frame.
* Whether the regulator messages we see during boot are actually significant. I don't know enough about the Linux regulator framework to say whether these being not-found means power is not correctly supplied, or if Linux just isn't being properly informed of the power supply requirements for precise tracking/power-saving when the camera is off.

== Megi saves the day ==

<pre>
[I] <megi> you might be interested in this https://megous.com/dl/tmp/0ae6ba03a17a3d53.png
[I] <megi> https://megous.com/git/linux/tag/?h=orange-pi-5.18-20220521-1759
</pre>

Turns out, the .dts had the wrong ISP connected to the sensor! This is fixed in [https://github.com/megous/linux/commit/9afd884f8b36121fb6097e77b6d35fe46ab48ad9 this commit], which is included in kernel version 5.18 or newer.

With a sufficiently new kernel, the following should produce an image (<code>frame.jpg</code>):

<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"imx258 1-001a":0 [fmt:SGRBG10_1X10/1048x780]'
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":2 [fmt:YUYV8_2X8/1048x780 crop:(0,0)/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:YUYV8_2X8/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--stream-to=frame.raw"

ffmpeg -y -s:v 1048x780 -pix_fmt yuv422p -i frame.raw frame.jpg
</pre>

Similarly, you can take a photo from the front camera with the following:

<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" "'m00_f_ov8858 1-0036':0 [fmt:SBGGR10_1X10/1632x1224]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'m00_f_ov8858 1-0036':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" "'rkisp1_isp':0 [fmt:SBGGR10_1X10/1632x1224 crop:(0,0)/1632x1224]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" "'rkisp1_isp':2 [fmt:YUYV8_2X8/1632x1224 crop:(0,0)/1632x1224]"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1632,height=1224,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" "'rkisp1_resizer_selfpath':0 [fmt:YUYV8_2X8/1632x1224 crop:(0,0)/1632x1224]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" "'rkisp1_resizer_selfpath':1 [fmt:YUYV8_2X8/1632x1224]"

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1632,height=1224,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--stream-to=frame.raw"

ffmpeg -y -s:v 1632x1224 -pix_fmt yuv422p -i frame.raw frame.jpg
</pre>

In some cases, the isp exposes 2 devices nodes, and the nodes have separate topologies with a different sensor attached to each. In this situation, you may need to reference the isp using the correct device node for the commands to work.

=== What's left? ===

* libcamera and megapixels still don't work. Megapixels appears to need support for debayering YUYV, and both appear to be configuring the rkisp1 pipeline wrong.
* The images captured are pretty green and seem to have two pixels of garbage at their bottom edge. rkisp1 supports auto white-balance (AWB) using the params/stats pads, and libcamera has some smarts that may hook these up properly. In the meantime, raw images can be postprocessed to improve white balance and exposure.

== Useful links ==

* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf Pinephone Pro Schematic]
* [https://blog.krybot.com/a?ID=01650-cea27a80-a1ab-4da1-9cb5-3945be91e3e1 Background on the GIC]
* [https://elinux.org/images/9/94/ISP-presentation.pdf Background on the rkisp1 ISP]

PinePhone Pro Software State

2022-05-21T20:37:32Z

Memleek: update rear camera status

Presently the PinePhone Pro Explorer Edition is aimed at '''Linux developers with an extensive knowledge of embedded systems and/or experience with mobile Linux'''. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile operating systems, in more general, to reach a higher degree of maturity.

Bear in mind that the software for these smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

The following table lists the feature functionality status of the unaltered pre-installed factory image of the current shipping batch and as comparison an up-to-date reference image (no responsibility is accepted for the accuracy of this information, the list is provided and updated by the community). If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the [[Main Page#Community and Support|community chat]] '''before buying the device''':

* Discord: ''#pinephone'' under https://discord.gg/pine64
* IRC: ''#pinephone'' on ''irc.pine64.org''. Note: please consider Matrix, Discord or Telegram due to the volatile nature of IRC
* Matrix: https://app.element.io/#/room/#pinephone:matrix.org
* Telegram: https://t.me/pinephone

{{Hint|The software is '''written by the community''', any contributions towards the community projects are greatly appreciated! Please see "[[How to Contribute]]" to learn about how to contribute to the software projects and "[[Where to Report Bugs]]" to learn about where to report bugs.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="min-width: 260px;" | Component
! scope="col" style="width: 120px;" | Status (factory)¹
! scope="col" style="width: 120px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="3" | Bootloader
| <code>U-Boot</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop (cause is known and currently being worked on);[[PinePhone_Pro#The battery is fully drained|Workaround]] Occasionally the eMMC fails to initialize[https://gitlab.com/postmarketOS/pmaports/-/issues/1424 Report]
|-
| <code>SPI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Unfinished
| SPI memory is currently empty in the Explorer Edition batch, a corrupted installation on the eMMC has a higher boot priority than a fresh microSD card installation, leading to a involved recovery procedure[https://tow-boot.org/ Planned]
|-
| <code>Boot GUI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Currently there is no graphical boot selection implemented[https://tow-boot.org/ Possibly planned]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]
|-
| <code>Suspend</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | Experimental
| '''Without suspend the phone will drain very fast!''' Suspend only available in specific more recent images[https://www.pine64.org/2022/03/15/march-update-introducing-the-quartzpro64/ News] Audio is often higher pitched after waking up from suspend due to a bug[https://github.com/dreemurrs-embedded/Pine64-Arch/issues/381 Report]
|-
| <code>Updates</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]; Pacman database lock preventing updates[https://wiki.archlinux.org/title/pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error Solution]; Keyring bug[Solution is to run "pinephonepro-post-install" script as root]
|-
! scope="row" rowspan="5" | Modem
| <code>General</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| The modem crashes frequently[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; Some carriers blocking specific TANs in their network[[PinePhone Carrier Support]]; '''Note:''' Proprietary firmware
|-
| <code>Phone</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The modem crashes frequently, which can lead to missed calls[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; bad call audio quality[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/249 Report];
|-
| <code>SMS</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/203 Report]; Some bugs
|-
| <code>MMS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Under certain circumstances it is difficult to wake up the screen[Citation]
|-
| <code>Touch</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | WIP
| Camera works with DTS fix; userspace still needs to do some catching up (see [[PinePhone Pro/IMX258 Camera Debugging|debugging article]])
|-
| <code>Front camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver not implemented yet (a staging driver exists for this sensor using the Intel Atom ISP framework (drivers/staging/media/atomisp/i2c/ov8858.c), but it needs to be ported and cleaned up); camera not operational
|-
| <code>Camera flash</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| (tested on Manjaro; at <code>/sys/class/leds/white:flash</code>)
|
|-
| <code>WiFi</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| WiFi is expected to work. Some remaining tasks, such as "monitor mode". '''Note:''' Proprietary firmware
|-
| <code>Bluetooth</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire Info] '''Note:''' Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| aGPS to be implemented[Citation]; long loading times to get a GPS fix[Citation]; No preinstalled application[Citation]
|-
| <code>Sensors</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| "3 Axis Magnetometer" (<code>lis3mdl</code>): Not present in hardware (it's an alternative chip to <code>af8133j</code> due to component shortages) 
"Geo Magnetic Sensor" (<code>af8133j</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-001c/iio:device1</code>) 
"Accelerometer / Gyroscope" (<code>mpu6500</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-0068/iio:device2</code>) 
"Ambient light / Proximity" (<code>stk3311</code>): Not working (tested on Manjaro 5.17.6-2 kernel; IRQ issues)
<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">stk3311 dmesg excerpt</div>
<div class="mw-collapsible-content"><pre>
[ 9.406478] genirq: Failed to request resources for stk3310_event (irq 99) on irqchip rockchip_gpio_irq
[ 9.407380] stk3310 3-0048: request irq 99 failed
[ 9.408360] stk3310: probe of 3-0048 failed with error -5
</pre></div>
</div>
|-
| <code>Vibration motor</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Buttons</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="5" | Accessory compatibility, spare parts
| <code>Keyboard Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | WIP and critical hardware issue
| The keyboard add-on compatibility is work-in-progress. '''Hardware issue: USB-C port of the phone must not be used while the current keyboard revision is connected'''[[PinePhone_(Pro)_Keyboard#Safety|Warning]]; Top row symbols not implemented as designed[Citation]; Keyboard hot-plugging not supported[Citation]; Battery state not exposed in the pre-flashed operating system state[Citation]; general driver bugs[Citation]
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software functionality and a driver is currently missing[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Spare parts</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not available yet
| Spare parts currently not available yet in the store.[https://pine64.com/product-category/smartphone-spare-parts/ Store]
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Software rendering only
| Waydroid is an Android container used to run Android applications. Currently can only be started using software rendering due to a bug[https://github.com/waydroid/waydroid/issues/291 Report][https://gitlab.freedesktop.org/mesa/mesa/-/issues/5928 Report]
|-
|}

¹ Status of the features at the time of the last factory installation without updates

² Status of the features with an up-to-date reference image

PinePhone Pro/IMX258 Camera Debugging

2022-05-21T20:34:37Z

Memleek: mention some caveats

== Background ==

The Pinephone Pro's rear camera is a Sony IMX258. The camera driver is present upstream, and at least [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro Manjaro's kernel] (downstream of Megi's) enables the driver. The camera does not seem to work; this page catalogs work on figuring out why.

== Initial status ==

What do we see in dmesg?

<pre>
imx258 1-001a: supply vana not found, using dummy regulator
imx258 1-001a: supply vdig not found, using dummy regulator
</pre>

This tells us the kernel loads the driver, which is something.

Are these errors bad/fatal? Inspecting the [https://github.com/megous/linux/blob/orange-pi-5.17/drivers/media/i2c/imx258.c source] shows us that these supplies are defined in the <code>imx258_supply_names</code> array, and <code>imx258_probe</code> calls <code>devm_regulator_bulk_get</code> to set them up.
<code>imx258_probe</code> checks the return code from <code>devm_regulator_bulk_get</code>, emitting a fatal "Failed to get supplies" message if the return code is negative (indicating failure). Since we don't see this message (or any others from the driver), it looks like it loads successfully!

=== How can we test the camera? ===

==== Megapixels ====

[https://gitlab.com/postmarketOS/megapixels Megapixels] requires a per-device file to configure cameras. This one isn't complete (most of its numbers are complete nonsense), but it should let us see what happens when Megapixels tries to access the camera:
<code>pine64,pinephone-pro.ini</code>:
<pre>
[device]
make=PINE64
model=PinePhone Pro

[rear]
driver=imx258
media-driver=rkisp1
capture-width=4208
capture-height=3118
capture-rate=60
capture-fmt=GRBG10P
preview-width=1280
preview-height=960
preview-rate=60
#preview-fmt=BGGR8
capture-fmt=GRBG10P
rotate=90
mirrored=true
focallength=2.6
cropfactor=12.7
fnumber=2.8
flash-display=true
</pre>

This segfaulted Megapixels for me. After patching some trivial segfaults, I get fatal GTK4 issues and other tangential problems. Let's try something else.

==== Manually setting up a camera pipeline ====

We can roughly follow [https://www.kernel.org/doc/html/latest/admin-guide/media/rkisp1.html this guide]. Doing so gives us the following commands:
<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=800,height=600,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--verbose"
</pre>

Careful readers will note that this is setting the camera up with a low resolution compared to what the sensor can do. For some reason I can't get the rkisp1 node to configure its sink pad with the maximum resolution of the sensor (4208x3118). Instead, it sets itself to 4032x3024. This mismatch is forbidden and causes v4l2 to give us EPIPE when we try to enable the stream. Using the lower resolution gets us further--the last command (which attempts to save a single frame of video) gives output like this:
<pre>
VIDIOC_QUERYCAP: ok
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
</pre>

But then it just hangs there indefinitely.

Running under strace, we see the program stuck in an ioctl:
<pre>
ioctl(3, VIDIOC_DQBUF, {type=V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE
</pre>

[https://www.kernel.org/doc/html/v4.13/media/uapi/v4l/vidioc-qbuf.html VIDIOC_DQBUF] corresponds to dequeuing a buffer once it has been filled with an image by the v4l2 device. Apparently, the device never gives us back a captured frame.

=== Now what? ===

==== Does i2c work at all? ====

The camera driver uses i2c; we can see the camera [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts#L890-L914 in the .dts] to determine that it's on i2c bus 1, address 0x1a.

The imx258 is controlled over i2c, and sends image data over MIPI. The first step is to see if the i2c control is working.

Looking back at the driver, it seems we should see errors in dmesg if i2c communication fails. The driver checks the chip id in its probe function, which uses i2c, so we can conclude that i2c gets set up properly initially. Does it keep working?

==== Does i2c keep working? (FTrace) ====

We can see if other functions that use i2c produce errors--for example, when we run our <code>"v4l2-ctl" ... "--stream-mmap"</code> command, we expect that <code>imx258_start_streaming</code> will get called, and this function also writes a load of registers over i2c.

Build and install a kernel with CONFIG_FTRACE (not hard, but outside the scope of this write-up) and enable function graph tracing:
<pre>
$ sudo su
# cd /sys/kernel/debug/tracing
# echo function_graph > current_tracer
# cat available_filter_functions | grep -E 'rkisp|imx258|v4l2' | awk '{print $1}' > set_graph_function
# echo 'vm_map_pages,__iommu_map,iommu_map_sg_atomic,rk_iommu_map,__alloc_pages,dma_alloc_attrs,dma_mmap_attrs,__vm_map_pages,vb2_mmap,clk_e,able,schedule_timeout,clk_disable,regmap_write,schedule,__i2c_tra,sfer,i2c_tra,sfer_buffer_flags,dma_free_attrs' | tr , '\n' > set_graph_notrace
# tee trace_pipe > ~/function-trace.log
</pre>

Now, in another terminal session, run the <code>"v4l2-ctl" ... "--stream-mmap"</code> command again. We end up with a bunch (but hopefully not *too* much) of output in our first terminal and the <code>~/function-trace.log</code> file.

A quick grep shows that <code>imx258_start_streaming</code> is indeed called, so '''i2c is working properly'''.

=== If i2c works, what doesn't? ===

Our program that asks for a video frame is still hung! We ask the camera to start streaming frames, it presumably does, but the v4l2 stack never tells us a frame has finished. Doing some digging in the v4l2 stack (and the rkisp1 driver), we find out that rkisp1 is notified about frame status via interrupts.

Perhaps the hardware is never actually emitting the interrupt that signals a frame being finished. Indeed, grepping our FTrace log shows that <code>rkisp1_isr</code> is never called. A quick look at <code>/proc/interrupts</code> shows that '''the only interrupt associated with the isp has never triggered''' (0 count on every CPU):
<pre>
# head -n1 /proc/interrupts; grep isp /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
57: 0 0 0 0 0 0 GICv3 75 Level ff914000.iommu, rkisp1
</pre>

=== <code>rkisp1</code> debugfs info ===

The <code>rkisp1</code> driver keeps some [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/drivers/media/platform/rockchip/rkisp1/rkisp1-common.h#L335-L363 error/debug counters] in debugfs, which can be viewed at <code>/sys/kernel/debug/ff910000.isp0</code>.

Sadly, the only one of these that comes up nonzero is <code>sp_stop_timeout</code> ("upon stream stop, the capture waits 1 second for the isr to stop the stream. This param is incremented in case of timeout"). I observe it to increment once per time I terminate the <code>"v4l2-ctl" ... "--stream-mmap"</code> command. This tells us what we already know: interrupts are not firing, but it also tells us that we aren't hitting any other errors that rkisp1 knows about.

== Next steps ==

Where do we go from here? I don't know--something may be wrong with the way the .dts specifies interrupts, some kind of firmware/GIC (the rk3399's interrupt controller) configuration issue, or something else. It would be good to try to determine:

* Whether the MIPI lines actually show traffic, if someone has a logic analyzer and a dissected PPP.
* Whether the DMA of frames to memory actually happens, regardless of (lack of) emission of the interrupt that tells us when said DMA finishes a frame.
* Whether the regulator messages we see during boot are actually significant. I don't know enough about the Linux regulator framework to say whether these being not-found means power is not correctly supplied, or if Linux just isn't being properly informed of the power supply requirements for precise tracking/power-saving when the camera is off.

== Megi saves the day ==

<pre>
[I] <megi> you might be interested in this https://megous.com/dl/tmp/0ae6ba03a17a3d53.png
[I] <megi> https://megous.com/git/linux/tag/?h=orange-pi-5.18-20220521-1759
</pre>

Turns out, the .dts had the wrong ISP connected to the sensor!

Apply [https://github.com/megous/linux/commit/9afd884f8b36121fb6097e77b6d35fe46ab48ad9 this commit] ([https://github.com/megous/linux/commit/9afd884f8b36121fb6097e77b6d35fe46ab48ad9.patch patch]) to your kernel tree, rebuild, and reinstall. Now, the following should produce an image (<code>frame.jpg</code>):

<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"imx258 1-001a":0 [fmt:SGRBG10_1X10/1048x780]'
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":2 [fmt:YUYV8_2X8/1048x780 crop:(0,0)/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:YUYV8_2X8/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--stream-to=frame.raw"

ffmpeg -y -s:v 1048x780 -pix_fmt yuv422p -i frame.raw frame.jpg
</pre>

=== What's left? ===

* libcamera and megapixels still don't work. Megapixels appears to need support for debayering YUYV, and both appear to be configuring the rkisp1 pipeline wrong.
* The images captured are pretty green and seem to have two pixels of garbage at their bottom edge. rkisp1 supports auto white-balance (AWB) using the params/stats pads, and libcamera has some smarts that may hook these up properly. In the meantime, raw images can be postprocessed to improve white balance and exposure.

== Useful links ==

* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf Pinephone Pro Schematic]
* [https://blog.krybot.com/a?ID=01650-cea27a80-a1ab-4da1-9cb5-3945be91e3e1 Background on the GIC]
* [https://elinux.org/images/9/94/ISP-presentation.pdf Background on the rkisp1 ISP]

PinePhone Pro/IMX258 Camera Debugging

2022-05-21T20:30:13Z

Memleek: fix command typo

== Background ==

The Pinephone Pro's rear camera is a Sony IMX258. The camera driver is present upstream, and at least [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro Manjaro's kernel] (downstream of Megi's) enables the driver. The camera does not seem to work; this page catalogs work on figuring out why.

== Initial status ==

What do we see in dmesg?

<pre>
imx258 1-001a: supply vana not found, using dummy regulator
imx258 1-001a: supply vdig not found, using dummy regulator
</pre>

This tells us the kernel loads the driver, which is something.

Are these errors bad/fatal? Inspecting the [https://github.com/megous/linux/blob/orange-pi-5.17/drivers/media/i2c/imx258.c source] shows us that these supplies are defined in the <code>imx258_supply_names</code> array, and <code>imx258_probe</code> calls <code>devm_regulator_bulk_get</code> to set them up.
<code>imx258_probe</code> checks the return code from <code>devm_regulator_bulk_get</code>, emitting a fatal "Failed to get supplies" message if the return code is negative (indicating failure). Since we don't see this message (or any others from the driver), it looks like it loads successfully!

=== How can we test the camera? ===

==== Megapixels ====

[https://gitlab.com/postmarketOS/megapixels Megapixels] requires a per-device file to configure cameras. This one isn't complete (most of its numbers are complete nonsense), but it should let us see what happens when Megapixels tries to access the camera:
<code>pine64,pinephone-pro.ini</code>:
<pre>
[device]
make=PINE64
model=PinePhone Pro

[rear]
driver=imx258
media-driver=rkisp1
capture-width=4208
capture-height=3118
capture-rate=60
capture-fmt=GRBG10P
preview-width=1280
preview-height=960
preview-rate=60
#preview-fmt=BGGR8
capture-fmt=GRBG10P
rotate=90
mirrored=true
focallength=2.6
cropfactor=12.7
fnumber=2.8
flash-display=true
</pre>

This segfaulted Megapixels for me. After patching some trivial segfaults, I get fatal GTK4 issues and other tangential problems. Let's try something else.

==== Manually setting up a camera pipeline ====

We can roughly follow [https://www.kernel.org/doc/html/latest/admin-guide/media/rkisp1.html this guide]. Doing so gives us the following commands:
<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=800,height=600,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--verbose"
</pre>

Careful readers will note that this is setting the camera up with a low resolution compared to what the sensor can do. For some reason I can't get the rkisp1 node to configure its sink pad with the maximum resolution of the sensor (4208x3118). Instead, it sets itself to 4032x3024. This mismatch is forbidden and causes v4l2 to give us EPIPE when we try to enable the stream. Using the lower resolution gets us further--the last command (which attempts to save a single frame of video) gives output like this:
<pre>
VIDIOC_QUERYCAP: ok
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
</pre>

But then it just hangs there indefinitely.

Running under strace, we see the program stuck in an ioctl:
<pre>
ioctl(3, VIDIOC_DQBUF, {type=V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE
</pre>

[https://www.kernel.org/doc/html/v4.13/media/uapi/v4l/vidioc-qbuf.html VIDIOC_DQBUF] corresponds to dequeuing a buffer once it has been filled with an image by the v4l2 device. Apparently, the device never gives us back a captured frame.

=== Now what? ===

==== Does i2c work at all? ====

The camera driver uses i2c; we can see the camera [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts#L890-L914 in the .dts] to determine that it's on i2c bus 1, address 0x1a.

The imx258 is controlled over i2c, and sends image data over MIPI. The first step is to see if the i2c control is working.

Looking back at the driver, it seems we should see errors in dmesg if i2c communication fails. The driver checks the chip id in its probe function, which uses i2c, so we can conclude that i2c gets set up properly initially. Does it keep working?

==== Does i2c keep working? (FTrace) ====

We can see if other functions that use i2c produce errors--for example, when we run our <code>"v4l2-ctl" ... "--stream-mmap"</code> command, we expect that <code>imx258_start_streaming</code> will get called, and this function also writes a load of registers over i2c.

Build and install a kernel with CONFIG_FTRACE (not hard, but outside the scope of this write-up) and enable function graph tracing:
<pre>
$ sudo su
# cd /sys/kernel/debug/tracing
# echo function_graph > current_tracer
# cat available_filter_functions | grep -E 'rkisp|imx258|v4l2' | awk '{print $1}' > set_graph_function
# echo 'vm_map_pages,__iommu_map,iommu_map_sg_atomic,rk_iommu_map,__alloc_pages,dma_alloc_attrs,dma_mmap_attrs,__vm_map_pages,vb2_mmap,clk_e,able,schedule_timeout,clk_disable,regmap_write,schedule,__i2c_tra,sfer,i2c_tra,sfer_buffer_flags,dma_free_attrs' | tr , '\n' > set_graph_notrace
# tee trace_pipe > ~/function-trace.log
</pre>

Now, in another terminal session, run the <code>"v4l2-ctl" ... "--stream-mmap"</code> command again. We end up with a bunch (but hopefully not *too* much) of output in our first terminal and the <code>~/function-trace.log</code> file.

A quick grep shows that <code>imx258_start_streaming</code> is indeed called, so '''i2c is working properly'''.

=== If i2c works, what doesn't? ===

Our program that asks for a video frame is still hung! We ask the camera to start streaming frames, it presumably does, but the v4l2 stack never tells us a frame has finished. Doing some digging in the v4l2 stack (and the rkisp1 driver), we find out that rkisp1 is notified about frame status via interrupts.

Perhaps the hardware is never actually emitting the interrupt that signals a frame being finished. Indeed, grepping our FTrace log shows that <code>rkisp1_isr</code> is never called. A quick look at <code>/proc/interrupts</code> shows that '''the only interrupt associated with the isp has never triggered''' (0 count on every CPU):
<pre>
# head -n1 /proc/interrupts; grep isp /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
57: 0 0 0 0 0 0 GICv3 75 Level ff914000.iommu, rkisp1
</pre>

=== <code>rkisp1</code> debugfs info ===

The <code>rkisp1</code> driver keeps some [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/drivers/media/platform/rockchip/rkisp1/rkisp1-common.h#L335-L363 error/debug counters] in debugfs, which can be viewed at <code>/sys/kernel/debug/ff910000.isp0</code>.

Sadly, the only one of these that comes up nonzero is <code>sp_stop_timeout</code> ("upon stream stop, the capture waits 1 second for the isr to stop the stream. This param is incremented in case of timeout"). I observe it to increment once per time I terminate the <code>"v4l2-ctl" ... "--stream-mmap"</code> command. This tells us what we already know: interrupts are not firing, but it also tells us that we aren't hitting any other errors that rkisp1 knows about.

== Next steps ==

Where do we go from here? I don't know--something may be wrong with the way the .dts specifies interrupts, some kind of firmware/GIC (the rk3399's interrupt controller) configuration issue, or something else. It would be good to try to determine:

* Whether the MIPI lines actually show traffic, if someone has a logic analyzer and a dissected PPP.
* Whether the DMA of frames to memory actually happens, regardless of (lack of) emission of the interrupt that tells us when said DMA finishes a frame.
* Whether the regulator messages we see during boot are actually significant. I don't know enough about the Linux regulator framework to say whether these being not-found means power is not correctly supplied, or if Linux just isn't being properly informed of the power supply requirements for precise tracking/power-saving when the camera is off.

== Megi saves the day ==

<pre>
[I] <megi> you might be interested in this https://megous.com/dl/tmp/0ae6ba03a17a3d53.png
[I] <megi> https://megous.com/git/linux/tag/?h=orange-pi-5.18-20220521-1759
</pre>

Turns out, the .dts had the wrong ISP connected to the sensor!

Apply [https://github.com/megous/linux/commit/9afd884f8b36121fb6097e77b6d35fe46ab48ad9 this commit] ([https://github.com/megous/linux/commit/9afd884f8b36121fb6097e77b6d35fe46ab48ad9.patch patch]) to your kernel tree, rebuild, and reinstall. Now, the following should produce an image (<code>frame.jpg</code>):

<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"imx258 1-001a":0 [fmt:SGRBG10_1X10/1048x780]'
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":2 [fmt:YUYV8_2X8/1048x780 crop:(0,0)/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:YUYV8_2X8/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--stream-to=frame.raw"

ffmpeg -y -s:v 1048x780 -pix_fmt yuv422p -i frame.raw frame.jpg
</pre>

=== What's left? ===

libcamera and megapixels still don't work. Megapixels appears to need support for debayering YUYV, and both appear to be configuring the rkisp1 pipeline wrong.

== Useful links ==

* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf Pinephone Pro Schematic]
* [https://blog.krybot.com/a?ID=01650-cea27a80-a1ab-4da1-9cb5-3945be91e3e1 Background on the GIC]
* [https://elinux.org/images/9/94/ISP-presentation.pdf Background on the rkisp1 ISP]

PinePhone Pro/IMX258 Camera Debugging

2022-05-21T20:27:16Z

Memleek: Add fix from Megi!

== Background ==

The Pinephone Pro's rear camera is a Sony IMX258. The camera driver is present upstream, and at least [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro Manjaro's kernel] (downstream of Megi's) enables the driver. The camera does not seem to work; this page catalogs work on figuring out why.

== Initial status ==

What do we see in dmesg?

<pre>
imx258 1-001a: supply vana not found, using dummy regulator
imx258 1-001a: supply vdig not found, using dummy regulator
</pre>

This tells us the kernel loads the driver, which is something.

Are these errors bad/fatal? Inspecting the [https://github.com/megous/linux/blob/orange-pi-5.17/drivers/media/i2c/imx258.c source] shows us that these supplies are defined in the <code>imx258_supply_names</code> array, and <code>imx258_probe</code> calls <code>devm_regulator_bulk_get</code> to set them up.
<code>imx258_probe</code> checks the return code from <code>devm_regulator_bulk_get</code>, emitting a fatal "Failed to get supplies" message if the return code is negative (indicating failure). Since we don't see this message (or any others from the driver), it looks like it loads successfully!

=== How can we test the camera? ===

==== Megapixels ====

[https://gitlab.com/postmarketOS/megapixels Megapixels] requires a per-device file to configure cameras. This one isn't complete (most of its numbers are complete nonsense), but it should let us see what happens when Megapixels tries to access the camera:
<code>pine64,pinephone-pro.ini</code>:
<pre>
[device]
make=PINE64
model=PinePhone Pro

[rear]
driver=imx258
media-driver=rkisp1
capture-width=4208
capture-height=3118
capture-rate=60
capture-fmt=GRBG10P
preview-width=1280
preview-height=960
preview-rate=60
#preview-fmt=BGGR8
capture-fmt=GRBG10P
rotate=90
mirrored=true
focallength=2.6
cropfactor=12.7
fnumber=2.8
flash-display=true
</pre>

This segfaulted Megapixels for me. After patching some trivial segfaults, I get fatal GTK4 issues and other tangential problems. Let's try something else.

==== Manually setting up a camera pipeline ====

We can roughly follow [https://www.kernel.org/doc/html/latest/admin-guide/media/rkisp1.html this guide]. Doing so gives us the following commands:
<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=800,height=600,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--verbose"
</pre>

Careful readers will note that this is setting the camera up with a low resolution compared to what the sensor can do. For some reason I can't get the rkisp1 node to configure its sink pad with the maximum resolution of the sensor (4208x3118). Instead, it sets itself to 4032x3024. This mismatch is forbidden and causes v4l2 to give us EPIPE when we try to enable the stream. Using the lower resolution gets us further--the last command (which attempts to save a single frame of video) gives output like this:
<pre>
VIDIOC_QUERYCAP: ok
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
</pre>

But then it just hangs there indefinitely.

Running under strace, we see the program stuck in an ioctl:
<pre>
ioctl(3, VIDIOC_DQBUF, {type=V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE
</pre>

[https://www.kernel.org/doc/html/v4.13/media/uapi/v4l/vidioc-qbuf.html VIDIOC_DQBUF] corresponds to dequeuing a buffer once it has been filled with an image by the v4l2 device. Apparently, the device never gives us back a captured frame.

=== Now what? ===

==== Does i2c work at all? ====

The camera driver uses i2c; we can see the camera [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts#L890-L914 in the .dts] to determine that it's on i2c bus 1, address 0x1a.

The imx258 is controlled over i2c, and sends image data over MIPI. The first step is to see if the i2c control is working.

Looking back at the driver, it seems we should see errors in dmesg if i2c communication fails. The driver checks the chip id in its probe function, which uses i2c, so we can conclude that i2c gets set up properly initially. Does it keep working?

==== Does i2c keep working? (FTrace) ====

We can see if other functions that use i2c produce errors--for example, when we run our <code>"v4l2-ctl" ... "--stream-mmap"</code> command, we expect that <code>imx258_start_streaming</code> will get called, and this function also writes a load of registers over i2c.

Build and install a kernel with CONFIG_FTRACE (not hard, but outside the scope of this write-up) and enable function graph tracing:
<pre>
$ sudo su
# cd /sys/kernel/debug/tracing
# echo function_graph > current_tracer
# cat available_filter_functions | grep -E 'rkisp|imx258|v4l2' | awk '{print $1}' > set_graph_function
# echo 'vm_map_pages,__iommu_map,iommu_map_sg_atomic,rk_iommu_map,__alloc_pages,dma_alloc_attrs,dma_mmap_attrs,__vm_map_pages,vb2_mmap,clk_e,able,schedule_timeout,clk_disable,regmap_write,schedule,__i2c_tra,sfer,i2c_tra,sfer_buffer_flags,dma_free_attrs' | tr , '\n' > set_graph_notrace
# tee trace_pipe > ~/function-trace.log
</pre>

Now, in another terminal session, run the <code>"v4l2-ctl" ... "--stream-mmap"</code> command again. We end up with a bunch (but hopefully not *too* much) of output in our first terminal and the <code>~/function-trace.log</code> file.

A quick grep shows that <code>imx258_start_streaming</code> is indeed called, so '''i2c is working properly'''.

=== If i2c works, what doesn't? ===

Our program that asks for a video frame is still hung! We ask the camera to start streaming frames, it presumably does, but the v4l2 stack never tells us a frame has finished. Doing some digging in the v4l2 stack (and the rkisp1 driver), we find out that rkisp1 is notified about frame status via interrupts.

Perhaps the hardware is never actually emitting the interrupt that signals a frame being finished. Indeed, grepping our FTrace log shows that <code>rkisp1_isr</code> is never called. A quick look at <code>/proc/interrupts</code> shows that '''the only interrupt associated with the isp has never triggered''' (0 count on every CPU):
<pre>
# head -n1 /proc/interrupts; grep isp /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
57: 0 0 0 0 0 0 GICv3 75 Level ff914000.iommu, rkisp1
</pre>

=== <code>rkisp1</code> debugfs info ===

The <code>rkisp1</code> driver keeps some [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/drivers/media/platform/rockchip/rkisp1/rkisp1-common.h#L335-L363 error/debug counters] in debugfs, which can be viewed at <code>/sys/kernel/debug/ff910000.isp0</code>.

Sadly, the only one of these that comes up nonzero is <code>sp_stop_timeout</code> ("upon stream stop, the capture waits 1 second for the isr to stop the stream. This param is incremented in case of timeout"). I observe it to increment once per time I terminate the <code>"v4l2-ctl" ... "--stream-mmap"</code> command. This tells us what we already know: interrupts are not firing, but it also tells us that we aren't hitting any other errors that rkisp1 knows about.

== Next steps ==

Where do we go from here? I don't know--something may be wrong with the way the .dts specifies interrupts, some kind of firmware/GIC (the rk3399's interrupt controller) configuration issue, or something else. It would be good to try to determine:

* Whether the MIPI lines actually show traffic, if someone has a logic analyzer and a dissected PPP.
* Whether the DMA of frames to memory actually happens, regardless of (lack of) emission of the interrupt that tells us when said DMA finishes a frame.
* Whether the regulator messages we see during boot are actually significant. I don't know enough about the Linux regulator framework to say whether these being not-found means power is not correctly supplied, or if Linux just isn't being properly informed of the power supply requirements for precise tracking/power-saving when the camera is off.

== Megi saves the day ==

<pre>
[I] <megi> you might be interested in this https://megous.com/dl/tmp/0ae6ba03a17a3d53.png
[I] <megi> https://megous.com/git/linux/tag/?h=orange-pi-5.18-20220521-1759
</pre>

Turns out, the .dts had the wrong ISP connected to the sensor!

Apply [https://github.com/megous/linux/commit/9afd884f8b36121fb6097e77b6d35fe46ab48ad9 this commit] ([https://github.com/megous/linux/commit/9afd884f8b36121fb6097e77b6d35fe46ab48ad9.patch patch]) to your kernel tree, rebuild, and reinstall. Now, the following should produce an image (<code>frame.jpg</code>):

<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"imx258 1-001a":0 [fmt:SGRBG10_1X10/1048x780]'
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":2 [fmt:YUYV8_2X8/1048x780 crop:(0,0)/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:YUYV8_2X8/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--stream-file=frame.raw"

ffmpeg -y -s:v 1048x780 -pix_fmt yuv422p -i frame.raw frame.jpg
</pre>

=== What's left? ===

libcamera and megapixels still don't work. Megapixels appears to need support for debayering YUYV, and both appear to be configuring the rkisp1 pipeline wrong.

== Useful links ==

* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf Pinephone Pro Schematic]
* [https://blog.krybot.com/a?ID=01650-cea27a80-a1ab-4da1-9cb5-3945be91e3e1 Background on the GIC]
* [https://elinux.org/images/9/94/ISP-presentation.pdf Background on the rkisp1 ISP]

PinePhone Pro Software State

2022-05-19T19:25:43Z

Memleek: link imx258 debugging article

Presently the PinePhone Pro Explorer Edition is aimed at '''Linux developers with an extensive knowledge of embedded systems and/or experience with mobile Linux'''. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile operating systems, in more general, to reach a higher degree of maturity.

Bear in mind that the software for these smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

The following table lists the feature functionality status of the unaltered pre-installed factory image of the current shipping batch and as comparison an up-to-date reference image (no responsibility is accepted for the accuracy of this information, the list is provided and updated by the community). If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the [[Main Page#Community and Support|community chat]] '''before buying the device''':

* Discord: ''#pinephone'' under https://discord.gg/pine64
* IRC: ''#pinephone'' on ''irc.pine64.org''. Note: please consider Matrix, Discord or Telegram due to the volatile nature of IRC
* Matrix: https://app.element.io/#/room/#pinephone:matrix.org
* Telegram: https://t.me/pinephone

{{Hint|The software is '''written by the community''', any contributions towards the community projects are greatly appreciated! Please see "[[How to Contribute]]" to learn about how to contribute to the software projects and "[[Where to Report Bugs]]" to learn about where to report bugs.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="min-width: 260px;" | Component
! scope="col" style="width: 120px;" | Status (factory)¹
! scope="col" style="width: 120px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="3" | Bootloader
| <code>U-Boot</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop (cause is known and currently being worked on);[[PinePhone_Pro#The battery is fully drained|Workaround]] Occasionally the eMMC fails to initialize[https://gitlab.com/postmarketOS/pmaports/-/issues/1424 Report]
|-
| <code>SPI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Unfinished
| SPI memory is currently empty in the Explorer Edition batch, a corrupted installation on the eMMC has a higher boot priority than a fresh microSD card installation, leading to a involved recovery procedure[https://tow-boot.org/ Planned]
|-
| <code>Boot GUI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Currently there is no graphical boot selection implemented[https://tow-boot.org/ Possibly planned]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]
|-
| <code>Suspend</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | Experimental
| '''Without suspend the phone will drain very fast!''' Suspend only available in specific more recent images[https://www.pine64.org/2022/03/15/march-update-introducing-the-quartzpro64/ News] Audio is often higher pitched after waking up from suspend due to a bug[https://github.com/dreemurrs-embedded/Pine64-Arch/issues/381 Report]
|-
| <code>Updates</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]; Pacman database lock preventing updates[https://wiki.archlinux.org/title/pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error Solution]; Keyring bug[Solution is to run "pinephonepro-post-install" script as root]
|-
! scope="row" rowspan="5" | Modem
| <code>General</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| The modem crashes frequently[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; Some carriers blocking specific TANs in their network[[PinePhone Carrier Support]]; '''Note:''' Proprietary firmware
|-
| <code>Phone</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The modem crashes frequently, which can lead to missed calls[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; bad call audio quality[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/249 Report];
|-
| <code>SMS</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/203 Report]; Some bugs
|-
| <code>MMS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Under certain circumstances it is difficult to wake up the screen[Citation]
|-
| <code>Touch</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver exists (drivers/media/i2c/imx258.c) but camera does not seem to capture frames (see [[PinePhone Pro/IMX258 Camera Debugging|debugging article]])
|-
| <code>Front camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver not implemented yet (a staging driver exists for this sensor using the Intel Atom ISP framework (drivers/staging/media/atomisp/i2c/ov8858.c), but it needs to be ported and cleaned up); camera not operational
|-
| <code>Camera flash</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| (tested on Manjaro; at <code>/sys/class/leds/white:flash</code>)
|
|-
| <code>WiFi</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| WiFi is expected to work. Some remaining tasks, such as "monitor mode". '''Note:''' Proprietary firmware
|-
| <code>Bluetooth</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire Info] '''Note:''' Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| aGPS to be implemented[Citation]; long loading times to get a GPS fix[Citation]; No preinstalled application[Citation]
|-
| <code>Sensors</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| "3 Axis Magnetometer" (<code>lis3mdl</code>): Not present in hardware (it's an alternative chip to <code>af8133j</code> due to component shortages) 
"Geo Magnetic Sensor" (<code>af8133j</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-001c/iio:device1</code>) 
"Accelerometer / Gyroscope" (<code>mpu6500</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-0068/iio:device2</code>) 
"Ambient light / Proximity" (<code>stk3311</code>): Not working (tested on Manjaro 5.17.6-2 kernel; IRQ issues)
<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">stk3311 dmesg excerpt</div>
<div class="mw-collapsible-content"><pre>
[ 9.406478] genirq: Failed to request resources for stk3310_event (irq 99) on irqchip rockchip_gpio_irq
[ 9.407380] stk3310 3-0048: request irq 99 failed
[ 9.408360] stk3310: probe of 3-0048 failed with error -5
</pre></div>
</div>
|-
| <code>Vibration motor</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Buttons</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="5" | Accessory compatibility, spare parts
| <code>Keyboard Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | WIP and critical hardware issue
| The keyboard add-on compatibility is work-in-progress. '''Hardware issue: USB-C port of the phone must not be used while the current keyboard revision is connected'''[[PinePhone_(Pro)_Keyboard#Safety|Warning]]; Top row symbols not implemented as designed[Citation]; Keyboard hot-plugging not supported[Citation]; Battery state not exposed in the pre-flashed operating system state[Citation]; general driver bugs[Citation]
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software functionality and a driver is currently missing[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Spare parts</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not available yet
| Spare parts currently not available yet in the store.[https://pine64.com/product-category/smartphone-spare-parts/ Store]
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Software rendering only
| Waydroid is an Android container used to run Android applications. Currently can only be started using software rendering due to a bug[https://github.com/waydroid/waydroid/issues/291 Report][https://gitlab.freedesktop.org/mesa/mesa/-/issues/5928 Report]
|-
|}

¹ Status of the features at the time of the last factory installation without updates

² Status of the features with an up-to-date reference image

PinePhone Pro/IMX258 Camera Debugging

2022-05-19T16:25:45Z

Memleek: More debugging, add some links

== Background ==

The Pinephone Pro's rear camera is a Sony IMX258. The camera driver is present upstream, and at least [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro Manjaro's kernel] (downstream of Megi's) enables the driver. The camera does not seem to work; this page catalogs work on figuring out why.

== Initial status ==

What do we see in dmesg?

<pre>
imx258 1-001a: supply vana not found, using dummy regulator
imx258 1-001a: supply vdig not found, using dummy regulator
</pre>

This tells us the kernel loads the driver, which is something.

Are these errors bad/fatal? Inspecting the [https://github.com/megous/linux/blob/orange-pi-5.17/drivers/media/i2c/imx258.c source] shows us that these supplies are defined in the <code>imx258_supply_names</code> array, and <code>imx258_probe</code> calls <code>devm_regulator_bulk_get</code> to set them up.
<code>imx258_probe</code> checks the return code from <code>devm_regulator_bulk_get</code>, emitting a fatal "Failed to get supplies" message if the return code is negative (indicating failure). Since we don't see this message (or any others from the driver), it looks like it loads successfully!

=== How can we test the camera? ===

==== Megapixels ====

[https://gitlab.com/postmarketOS/megapixels Megapixels] requires a per-device file to configure cameras. This one isn't complete (most of its numbers are complete nonsense), but it should let us see what happens when Megapixels tries to access the camera:
<code>pine64,pinephone-pro.ini</code>:
<pre>
[device]
make=PINE64
model=PinePhone Pro

[rear]
driver=imx258
media-driver=rkisp1
capture-width=4208
capture-height=3118
capture-rate=60
capture-fmt=GRBG10P
preview-width=1280
preview-height=960
preview-rate=60
#preview-fmt=BGGR8
capture-fmt=GRBG10P
rotate=90
mirrored=true
focallength=2.6
cropfactor=12.7
fnumber=2.8
flash-display=true
</pre>

This segfaulted Megapixels for me. After patching some trivial segfaults, I get fatal GTK4 issues and other tangential problems. Let's try something else.

==== Manually setting up a camera pipeline ====

We can roughly follow [https://www.kernel.org/doc/html/latest/admin-guide/media/rkisp1.html this guide]. Doing so gives us the following commands:
<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=800,height=600,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--verbose"
</pre>

Careful readers will note that this is setting the camera up with a low resolution compared to what the sensor can do. For some reason I can't get the rkisp1 node to configure its sink pad with the maximum resolution of the sensor (4208x3118). Instead, it sets itself to 4032x3024. This mismatch is forbidden and causes v4l2 to give us EPIPE when we try to enable the stream. Using the lower resolution gets us further--the last command (which attempts to save a single frame of video) gives output like this:
<pre>
VIDIOC_QUERYCAP: ok
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
</pre>

But then it just hangs there indefinitely.

Running under strace, we see the program stuck in an ioctl:
<pre>
ioctl(3, VIDIOC_DQBUF, {type=V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE
</pre>

[https://www.kernel.org/doc/html/v4.13/media/uapi/v4l/vidioc-qbuf.html VIDIOC_DQBUF] corresponds to dequeuing a buffer once it has been filled with an image by the v4l2 device. Apparently, the device never gives us back a captured frame.

=== Now what? ===

==== Does i2c work at all? ====

The camera driver uses i2c; we can see the camera [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts#L890-L914 in the .dts] to determine that it's on i2c bus 1, address 0x1a.

The imx258 is controlled over i2c, and sends image data over MIPI. The first step is to see if the i2c control is working.

Looking back at the driver, it seems we should see errors in dmesg if i2c communication fails. The driver checks the chip id in its probe function, which uses i2c, so we can conclude that i2c gets set up properly initially. Does it keep working?

==== Does i2c keep working? (FTrace) ====

We can see if other functions that use i2c produce errors--for example, when we run our <code>"v4l2-ctl" ... "--stream-mmap"</code> command, we expect that <code>imx258_start_streaming</code> will get called, and this function also writes a load of registers over i2c.

Build and install a kernel with CONFIG_FTRACE (not hard, but outside the scope of this write-up) and enable function graph tracing:
<pre>
$ sudo su
# cd /sys/kernel/debug/tracing
# echo function_graph > current_tracer
# cat available_filter_functions | grep -E 'rkisp|imx258|v4l2' | awk '{print $1}' > set_graph_function
# echo 'vm_map_pages,__iommu_map,iommu_map_sg_atomic,rk_iommu_map,__alloc_pages,dma_alloc_attrs,dma_mmap_attrs,__vm_map_pages,vb2_mmap,clk_e,able,schedule_timeout,clk_disable,regmap_write,schedule,__i2c_tra,sfer,i2c_tra,sfer_buffer_flags,dma_free_attrs' | tr , '\n' > set_graph_notrace
# tee trace_pipe > ~/function-trace.log
</pre>

Now, in another terminal session, run the <code>"v4l2-ctl" ... "--stream-mmap"</code> command again. We end up with a bunch (but hopefully not *too* much) of output in our first terminal and the <code>~/function-trace.log</code> file.

A quick grep shows that <code>imx258_start_streaming</code> is indeed called, so '''i2c is working properly'''.

=== If i2c works, what doesn't? ===

Our program that asks for a video frame is still hung! We ask the camera to start streaming frames, it presumably does, but the v4l2 stack never tells us a frame has finished. Doing some digging in the v4l2 stack (and the rkisp1 driver), we find out that rkisp1 is notified about frame status via interrupts.

Perhaps the hardware is never actually emitting the interrupt that signals a frame being finished. Indeed, grepping our FTrace log shows that <code>rkisp1_isr</code> is never called. A quick look at <code>/proc/interrupts</code> shows that '''the only interrupt associated with the isp has never triggered''' (0 count on every CPU):
<pre>
# head -n1 /proc/interrupts; grep isp /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
57: 0 0 0 0 0 0 GICv3 75 Level ff914000.iommu, rkisp1
</pre>

=== <code>rkisp1</code> debugfs info ===

The <code>rkisp1</code> driver keeps some [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/drivers/media/platform/rockchip/rkisp1/rkisp1-common.h#L335-L363 error/debug counters] in debugfs, which can be viewed at <code>/sys/kernel/debug/ff910000.isp0</code>.

Sadly, the only one of these that comes up nonzero is <code>sp_stop_timeout</code> ("upon stream stop, the capture waits 1 second for the isr to stop the stream. This param is incremented in case of timeout"). I observe it to increment once per time I terminate the <code>"v4l2-ctl" ... "--stream-mmap"</code> command. This tells us what we already know: interrupts are not firing, but it also tells us that we aren't hitting any other errors that rkisp1 knows about.

== Next steps ==

Where do we go from here? I don't know--something may be wrong with the way the .dts specifies interrupts, some kind of firmware/GIC (the rk3399's interrupt controller) configuration issue, or something else. It would be good to try to determine:

* Whether the MIPI lines actually show traffic, if someone has a logic analyzer and a dissected PPP.
* Whether the DMA of frames to memory actually happens, regardless of (lack of) emission of the interrupt that tells us when said DMA finishes a frame.
* Whether the regulator messages we see during boot are actually significant. I don't know enough about the Linux regulator framework to say whether these being not-found means power is not correctly supplied, or if Linux just isn't being properly informed of the power supply requirements for precise tracking/power-saving when the camera is off.

== Useful links ==

* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf Pinephone Pro Schematic]
* [https://blog.krybot.com/a?ID=01650-cea27a80-a1ab-4da1-9cb5-3945be91e3e1 Background on the GIC]
* [https://elinux.org/images/9/94/ISP-presentation.pdf Background on the rkisp1 ISP]

PinePhone Pro Software State

2022-05-19T15:26:22Z

Memleek: Note that lis3mdl is not present on devices (thanks @dsimic on the pinephone matrix channel for info)

Presently the PinePhone Pro Explorer Edition is aimed at '''Linux developers with an extensive knowledge of embedded systems and/or experience with mobile Linux'''. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile operating systems, in more general, to reach a higher degree of maturity.

Bear in mind that the software for these smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

The following table lists the feature functionality status of the unaltered pre-installed factory image of the current shipping batch and as comparison an up-to-date reference image (no responsibility is accepted for the accuracy of this information, the list is provided and updated by the community). If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the [[Main Page#Community and Support|community chat]] '''before buying the device''':

* Discord: ''#pinephone'' under https://discord.gg/pine64
* IRC: ''#pinephone'' on ''irc.pine64.org''. Note: please consider Matrix, Discord or Telegram due to the volatile nature of IRC
* Matrix: https://app.element.io/#/room/#pinephone:matrix.org
* Telegram: https://t.me/pinephone

{{Hint|The software is '''written by the community''', any contributions towards the community projects are greatly appreciated! Please see "[[How to Contribute]]" to learn about how to contribute to the software projects and "[[Where to Report Bugs]]" to learn about where to report bugs.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="min-width: 260px;" | Component
! scope="col" style="width: 120px;" | Status (factory)¹
! scope="col" style="width: 120px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="3" | Bootloader
| <code>U-Boot</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop (cause is known and currently being worked on);[[PinePhone_Pro#The battery is fully drained|Workaround]] Occasionally the eMMC fails to initialize[https://gitlab.com/postmarketOS/pmaports/-/issues/1424 Report]
|-
| <code>SPI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Unfinished
| SPI memory is currently empty in the Explorer Edition batch, a corrupted installation on the eMMC has a higher boot priority than a fresh microSD card installation, leading to a involved recovery procedure[https://tow-boot.org/ Planned]
|-
| <code>Boot GUI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Currently there is no graphical boot selection implemented[https://tow-boot.org/ Possibly planned]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]
|-
| <code>Suspend</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | Experimental
| '''Without suspend the phone will drain very fast!''' Suspend only available in specific more recent images[https://www.pine64.org/2022/03/15/march-update-introducing-the-quartzpro64/ News] Audio is often higher pitched after waking up from suspend due to a bug[https://github.com/dreemurrs-embedded/Pine64-Arch/issues/381 Report]
|-
| <code>Updates</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]; Pacman database lock preventing updates[https://wiki.archlinux.org/title/pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error Solution]; Keyring bug[Solution is to run "pinephonepro-post-install" script as root]
|-
! scope="row" rowspan="5" | Modem
| <code>General</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| The modem crashes frequently[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; Some carriers blocking specific TANs in their network[[PinePhone Carrier Support]]; '''Note:''' Proprietary firmware
|-
| <code>Phone</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The modem crashes frequently, which can lead to missed calls[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; bad call audio quality[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/249 Report];
|-
| <code>SMS</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/203 Report]; Some bugs
|-
| <code>MMS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Under certain circumstances it is difficult to wake up the screen[Citation]
|-
| <code>Touch</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver exists (drivers/media/i2c/imx258.c) but camera does not seem to capture frames
|-
| <code>Front camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver not implemented yet (a staging driver exists for this sensor using the Intel Atom ISP framework (drivers/staging/media/atomisp/i2c/ov8858.c), but it needs to be ported and cleaned up); camera not operational
|-
| <code>Camera flash</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| (tested on Manjaro; at <code>/sys/class/leds/white:flash</code>)
|
|-
| <code>WiFi</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| WiFi is expected to work. Some remaining tasks, such as "monitor mode". '''Note:''' Proprietary firmware
|-
| <code>Bluetooth</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire Info] '''Note:''' Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| aGPS to be implemented[Citation]; long loading times to get a GPS fix[Citation]; No preinstalled application[Citation]
|-
| <code>Sensors</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| "3 Axis Magnetometer" (<code>lis3mdl</code>): Not present in hardware (it's an alternative chip to <code>af8133j</code> due to component shortages) 
"Geo Magnetic Sensor" (<code>af8133j</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-001c/iio:device1</code>) 
"Accelerometer / Gyroscope" (<code>mpu6500</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-0068/iio:device2</code>) 
"Ambient light / Proximity" (<code>stk3311</code>): Not working (tested on Manjaro 5.17.6-2 kernel; IRQ issues)
<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">stk3311 dmesg excerpt</div>
<div class="mw-collapsible-content"><pre>
[ 9.406478] genirq: Failed to request resources for stk3310_event (irq 99) on irqchip rockchip_gpio_irq
[ 9.407380] stk3310 3-0048: request irq 99 failed
[ 9.408360] stk3310: probe of 3-0048 failed with error -5
</pre></div>
</div>
|-
| <code>Vibration motor</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Buttons</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="5" | Accessory compatibility, spare parts
| <code>Keyboard Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | WIP and critical hardware issue
| The keyboard add-on compatibility is work-in-progress. '''Hardware issue: USB-C port of the phone must not be used while the current keyboard revision is connected'''[[PinePhone_(Pro)_Keyboard#Safety|Warning]]; Top row symbols not implemented as designed[Citation]; Keyboard hot-plugging not supported[Citation]; Battery state not exposed in the pre-flashed operating system state[Citation]; general driver bugs[Citation]
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software functionality and a driver is currently missing[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Spare parts</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not available yet
| Spare parts currently not available yet in the store.[https://pine64.com/product-category/smartphone-spare-parts/ Store]
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Software rendering only
| Waydroid is an Android container used to run Android applications. Currently can only be started using software rendering due to a bug[https://github.com/waydroid/waydroid/issues/291 Report][https://gitlab.freedesktop.org/mesa/mesa/-/issues/5928 Report]
|-
|}

¹ Status of the features at the time of the last factory installation without updates

² Status of the features with an up-to-date reference image

PinePhone Pro

2022-05-19T15:23:43Z

Memleek: Add link to software state article

[[File:Pinephone_double.png|400px|thumb|right|Rendering of the PinePhone Pro]]

The '''PinePhone Pro''' is PINE64's flagship smartphone announced on October 15, 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC, which is a specialized version of the RK3399 made specifically for the PinePhone Pro.

== Introduction ==

The PinePhone Pro is PINE64’s second smartphone and a successor to the original PinePhone. It does not, however, replace the original PinePhone. It should also not be considered a second generation PinePhone; it is a higher-end device, with much better specs, aimed at those who wish to daily-drive a open system stack. Achieving this goal will, however, take time as the software and overall smartphone software ecosystem needs to mature.

More information about the PinePhone Pro can be found on the device [https://www.pine64.org/pinephonepro/ main page].

=== State of the software ===
([[PinePhone Pro Software State|view separately]])

{{:PinePhone Pro Software State}}

=== Editions and revisions ===
Similarly to the original PinePhone, various PinePhone Pro editions are planned, the first of which is the Developer Edition (aimed at developers, as the name entails) followed by the Explorer Edition, which is aimed at early adopters.

* [[PinePhone Pro Developer Edition]]
* [[PinePhone Pro Explorer Edition]]

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this Wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== First time setup ==
[[File:Pinephone_warning.png|320px|thumb|right|A protection foil isolates the battery for the shipping.]]

When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge or boot until it is removed and the battery is connected again.

{{Info|To remove the sticker after unboxing the phone: Carefully remove the back panel using the notch in the corner of the back cover without overbending it. Then remove the battery. Peel off the clear plastic sticker below it, which isolates the charging contacts and reinsert the battery.}}

The PinePhone's SIM slot only accepts a micro-SIM, please do not insert a nano-SIM without an adapter and make sure that the nano-SIM does not get released from its adapter. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot.

{{Info|Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them!}}

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the micro-SIM in the lower slot.]]

An adapter from a nano to a micro-SIM might be included under tape in the camera notch of the phone's packaging. Some nano-SIMs will not fit firmly into that adapter that comes with the PinePhone and if the included adapter is used without a well-fitting nano-SIM, the contact pins might get damaged. In that case it is highly recommended to acquire a better fitting adapter.

== Software ==

The software section explains how to install the available software releases for the PinePhone Pro to the internal eMMC or a microSD card, how to boot them and how to solve common booting issues.

=== Software releases ===

The [[PinePhone Pro Software Releases]] page has a complete list of currently supported phone-optimized operating system images that work with the PinePhone Pro.

{{Info|Images of the regular PinePhone are not compatible with the PinePhone Pro.}}

=== Boot order ===

The RK3399S processor in the PinePhone Pro searches for the bootloader (such as ''U-Boot'') in the following order:

# SPI flash
# eMMC (the internal memory)
# MicroSD card

The bootloader uses its own boot order for loading the kernel and other core operating system components at boot, which for example may result in the boot loader residing on the eMMC loading and booting the kernel from a microSD card.

The SPI flash and the eMMC chip can be bypassed during boot by temporarily disabling them at the hardware level using the following method, which can be used in cases such as having corrupted installation on the SPI flash or the eMMC:

* On the '''Explorer Edition''' hold the ''RE'' button underneath the cover for a few seconds, while powering on the device.

* On the '''Developer Edition''', which was an earlier revision intended for developers only, the SPI and the eMMC can be bypassed by shorting the bypass test points while booting. The process is explained in the article [[PinePhone Pro Developer Edition#Nuking the factory AOSP installation|PinePhone Pro Developer Edition]]. Please join the community chat for any questions regarding the process.

The bypass disables the SPI and the eMMC while being applied and the PinePhone Pro will try to boot from the next available boot medium, which is the microSD card. Note: When holding the ''RE'' button (or when shorting the contact points in case of the ''Developer Edition'') for a longer time at boot the operating system will not initialize the SPI and eMMC and it will not be possible to write to these storage mediums until the next reboot.

{{Info|The bootloader (such as ''U-Boot'') resides in the free space in front of the first partition. Wiping the bootloader from the eMMC to make the PinePhone Pro boot from microSD card can be done using <code>sudo dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=400 conv=fsync</code>. Formatting the drive or deleting the partition table is not sufficient to wipe the bootloader.}}

See [[RK3399 boot sequence]] for details regarding the boot sequence.

=== Installation instructions ===

The software releases can be installed (the process is being referred to as ''flashing'') to the eMMC or to an microSD card.

==== Flashing to microSD card ====
To install an image to the microSD card:

# Download a compatible image from [[PinePhone Pro Software Releases]]
# Extract the compressed image
# Write the image to your microSD card using your favorite method, examples:
#* Using ''dd'': On the device you're flashing the microSD card from, find the correct device under <code>lsblk</code> and then flash the image to the microSD card using <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>. Make sure the target is the whole microSD card and not its first partition (''sdc1'' or ''mmcblk0p1'' are wrong!).
#* Using ''bmaptool'': Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device: Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 GB file.
#* Using ''a graphical tool'': A graphical tool such as Gnome Disks under Linux or Etcher under Windows may also be used.
# Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore, see [[:File:Pinephone_slots.png|here]].
# Power on the PinePhone Pro. If there is an '''existing bootloader on the eMMC''' already you need to bypass or wipe the bootloader on the eMMC as explained in the section [[PinePhone Pro#Boot order|Boot order]].

==== Flashing to the eMMC ====
Flashing to the eMMC can be done by booting an operating system from the microSD (see the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]) and by writing to the eMMC directly from there:

# Boot an operating system [[PinePhone Pro#Flashing to microSD card|from the microSD card]]. If there is already a bootloader on the eMMC installed see the section [[PinePhone Pro#Boot order|Boot order]] to bypass it
# Download or copy the desired image to the microSD card as file
# Check if the eMMC appears under <code>lsblk</code>. If it doesn't appear in the output of the command, the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot
# Extract the image
# Flash the extracted image using <code>sudo dd if='''IMAGE.img''' of=/dev/mmcblk2 bs=1M status=progress conv=fsync</code>
# Reboot the PinePhone Pro

=== Troubleshooting ===

If the PinePhone Pro is not booting (either booting incompletely into a boot splash or tty or if the PinePhone Pro is showing no signs of life) this will typically have the following two reasons:

==== The battery is fully drained ====
The bootloader ''U-Boot'' is currently booting into a boot loop if the battery is fully drained. In that case it is not possible to charge the phone. The battery can be charged by interrupting the boot loop by booting the PinePhone Pro into ''Maskrom mode'' or by charging the battery externally. To boot the PinePhone Pro into ''Maskrom mode'':

* Remove any microSD card from the phone and keep it removed for the below procedure
* Remove the battery, any USB cable and any serial cable
* Reinsert the battery
* Hold the ''RE'' button underneath the back cover of your ''Explorer Edition'' (or short the bypass contact points on the ''Developer Edition'')
* Connect the phone to an USB port of a computer, while still holding the button for some time
* Check if the phone in Maskrom mode appears in the output of the terminal command <code>lsusb</code> on the computer, the expected ''VID:PID'' of the device is ''2207:330c'' (under ''Windows'' this can be checked using the ''Device Manager'' and checking the VID and PID of an appearing ''Unknown device'')
* Let the phone charge for at least two hours

{{Info|If the device doesn't appear under ''lsusb'' please try again with a different known good USB-C cable and make sure that there is no microSD card in the phone inserted.}}

The device should now be able to boot from the boot medium again. If that is not the case the installation got corrupted, as explained below.

==== The installation is corrupted ====
The PinePhone Pro won't be able to boot if the installation on the SPI flash, the eMMC or the microSD card got corrupted. To boot a working operating system:

* Prepare a microSD card as explained in the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]
* Remove any USB-C cable or device or add-on case from the PinePhone Pro
* Make sure the device is powered off by shortly removing the battery for a second
* Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore.
* Power on the device while bypassing the SPI and eMMC as explained under [[PinePhone Pro#Boot order|Boot order]]

The device should now boot from the microSD card. If the phone does not boot from the microSD card the microSD card was flashed with an incompatible image or the battery got drained as explained above.

=== Bootloaders ===
The following section contains notes regarding compatible bootloaders with the PinePhone Pro.

==== U-Boot ====
The pre-installed operating system on the PinePhone Pro Explorer Edition is using ''U-Boot'' as default bootloader.

==== Tow-Boot ====
There are plans to possibly ship the PinePhone Pro with ''Tow-Boot'' pre-installed to the SPI flash in a future batch, which is an opinionated distribution of ''U-Boot'' and brings numerous advantages over stock ''U-Boot'', such as the possibility to choose from booting the eMMC or microSD card using the volume buttons during boot, as well as a ''USB Mass Storage mode'', where the device can be written to by connecting the device to a computer via USB.

The user can flash Tow-Boot to the PinePhone Pro using the [https://tow-boot.org/devices/pine64-pinephonePro.html instructions on the Tow-Boot website].

==== levinboot ====
The levinboot bootloader is another upcoming option for the PinePhone Pro. The project repository can be found [https://gitlab.com/DeltaGem/levinboot/-/tree/master/ here].

== Privacy switch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Picture of the privacy switches]]

The PinePhone features six switches that can be used to configure its hardware. They are numbered 1-6, with switch 1 located nearest to the modem. Their "on" position is toward the top of the phone.

{| class="wikitable"
|-
! Number
! Name
! Description
|-
| 1
| Modem
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART¹ mode.
|}

¹ Note: The baud rate may be 1500000 instead of 115200.

== Specifications ==

* '''Dimensions:''' 160.8 x 76.6 x 11.1mm
* '''Weight:''' Approx. 220g
* '''SIM Card:''' Micro-SIM
* '''Display:'''
** '''Size:''' 6 inches (151mm) diagonal
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz
* '''RAM:''' 4GB LPDDR4 @ 800MHz
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''Back [[#Camera|Camera]]:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash
* '''Front Camera:''' 8MP, OmniVision OV8858 front-facing camera
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|Modem]]:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN & Bluetooth:''' Wi-Fi 802.11AC, hotspot capable + Bluetooth V5.0
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|Battery]]:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| LCD
| Himax HX8394 compatible
|-
| Rear camera
| IMX258
|-
| Front camera
| OV8858
|-
| Camera flash
| AW3641EDNR
|-
| WiFi + Bluetooth
| [https://www.azurewave.com/img/wireless-modules/AW_CM256SM_DS_Rev15_CYW.pdf AzureWave AW-CM256SM]
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| 3 Axis Magnetometer
| [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL]
|-
| Geo Magnetic Sensor
| [http://www.voltafield.com/products01.html Voltafield AF8133J]
|-
| Ambient light / Proximity
| STK3311-A
|-
| Accelerometer / Gyroscope
| [https://invensense.tdk.com/products/motion-tracking/6-axis/mpu-6500/ TDK MPU-6500]
|-
| Vibration motor
|
|-
| Notification LED
| LED0603RGB
|-
| Audio Codec
| ALC5616 and ALC5640
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
|
|-
| Battery fuel gauge
| [https://rockchip.fr/RK818%20datasheet%20V1.0.pdf RK818]
|}

== Datasheets, schematics and certifications ==

* PinePhone Pro mainboard schematic:
** [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf PinePhone Pro mainboard Explorer Edition Released Schematic ver 1.0 20211127]
** [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-top.pdf PinePhone Pro mainboard Explorer Edition component top placement ver 1.0 20211127]
** [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-bottom.pdf PinePhone Pro mainboard Explorer Edition component bottom placement ver 1.0 20211127]

* PinePhone Pro USB-C small board schematic:
** TBD

* Certifications:
** [https://files.pine64.org/doc/cert/PinePhone%20Pro%20FCC%20Certificate-S21101902805001.pdf PinePhone Pro FCC Certificate]
** [https://files.pine64.org/doc/cert/PinePhonePro%20SAR%20Evaluation%20Report-S21101902806001.pdf PinePhone Pro SAR Evaluation Report]
** [https://files.pine64.org/doc/cert/PinePhone%20Pro%20CE%20RED%20Certificate-S21101902802-R1.pdf PinePhone Pro CE RED Certificate]
** [https://files.pine64.org/doc/cert/PinePhonePro%20RoHS%20Test%20Report.pdf PinePhone Pro ROHS Test Report]

== Factory Test Build for Hardware Checking ==

* Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by support team. This is NOT a general release build.
* DD image (for 8GB microSD Card or larger)
** [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 214e063c8205c1a98d44b2015a21bb5d
*** File Size: 722MB

* Download the build, extract the image and dd it to a 8 GB or larger microSD card, takes out the PinePhone Pro Explorer Edition then insert it into microSD slot (upper slot).
* Insert battery, press RE button (bypass SPI and eMMC boot) while plug in USB-C power. After 3 seconds release RE button.
* When power up, below battery icon screen show up and press power key for two second, the Rockchip logo screen shows up.

[[File:PPP_Abdroid_Test_Utility-1.jpg|300px]][[File:PPP_Abdroid_Test_Utility-2.jpg|300px]]

* Wait for home screen, double tap on the test app icon (mark red circuit) and this will bring up the factory test screen. Please note that SD test is disable due to this is a SD boot build.
* After running particular test function, please snapshot test result and pass back to support team
** Note: Please slot in functional Sim card when perform SIM test
** Note: When perform GPS test, the first result may fail and please ignore this false message.
** Note: For light sensing test, please have touch light shine to PinePhone Pro when perform test.

[[File:PPP_Abdroid_Test_Utility-4.jpg|300px]][[File:PPP_Abdroid_Test_Utility-5.jpg|538px]]

== Using Factory Test Build for Battery charging ==

* Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by support team. This is NOT a general release build.
* DD image (for 8GB microSD Card or larger)
** [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 214e063c8205c1a98d44b2015a21bb5d
*** File Size: 722MB

* Download the build, extract the image and dd it to a 8 GB or larger microSD card, takes out the PinePhone Pro Explorer Edition then insert it into microSD slot (upper slot).
* Insert battery, press RE button (bypass SPI and eMMC boot) while plug in USB-C power. After 3 seconds release RE button.
* When power up, below battery icon screen show up and battery will start charging.
* The battery icon display for few seconds and then LCD panel turn off while charging. To check charging status, just quick press power button (about 0.5 second) and battery icon will display progress.

[[File:PPP_Abdroid_Test_Utility-1.jpg|300px]]

== Press ==

For an overview about media of the PinePhone Pro you can use for the news, blogs, or similar see [[PinePhone Press]].

== External links ==
* [https://www.pine64.org/pinephonepro/ Product Page]
* [https://www.youtube.com/watch?v=wP2-6Z74W44 Announcement video]
* [https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blog post] with the announcement

[[Category:PinePhone Pro]][[Category:Rockchip RK3399]]

PinePhone Pro/IMX258 Camera Debugging

2022-05-19T04:00:48Z

Memleek:

== Background ==

The Pinephone Pro's rear camera is a Sony IMX258. The camera driver is present upstream, and at least [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro Manjaro's kernel] (downstream of Megi's) enables the driver. The camera does not seem to work; this page catalogs work on figuring out why.

== Initial status ==

What do we see in dmesg?

<pre>
imx258 1-001a: supply vana not found, using dummy regulator
imx258 1-001a: supply vdig not found, using dummy regulator
</pre>

This tells us the kernel loads the driver, which is something.

Are these errors bad/fatal? Inspecting the [https://github.com/megous/linux/blob/orange-pi-5.17/drivers/media/i2c/imx258.c source] shows us that these supplies are defined in the <code>imx258_supply_names</code> array, and <code>imx258_probe</code> calls <code>devm_regulator_bulk_get</code> to set them up.
<code>imx258_probe</code> checks the return code from <code>devm_regulator_bulk_get</code>, emitting a fatal "Failed to get supplies" message if the return code is negative (indicating failure). Since we don't see this message (or any others from the driver), it looks like it loads successfully!

=== How can we test the camera? ===

==== Megapixels ====

[https://gitlab.com/postmarketOS/megapixels Megapixels] requires a per-device file to configure cameras. This one isn't complete (most of its numbers are complete nonsense), but it should let us see what happens when Megapixels tries to access the camera:
<code>pine64,pinephone-pro.ini</code>:
<pre>
[device]
make=PINE64
model=PinePhone Pro

[rear]
driver=imx258
media-driver=rkisp1
capture-width=4208
capture-height=3118
capture-rate=60
capture-fmt=GRBG10P
preview-width=1280
preview-height=960
preview-rate=60
#preview-fmt=BGGR8
capture-fmt=GRBG10P
rotate=90
mirrored=true
focallength=2.6
cropfactor=12.7
fnumber=2.8
flash-display=true
</pre>

This segfaulted Megapixels for me. After patching some trivial segfaults, I get fatal GTK4 issues and other tangential problems. Let's try something else.

==== Manually setting up a camera pipeline ====

We can roughly follow [https://www.kernel.org/doc/html/latest/admin-guide/media/rkisp1.html this guide]. Doing so gives us the following commands:
<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=800,height=600,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--verbose"
</pre>

Careful readers will note that this is setting the camera up with a low resolution compared to what the sensor can do. For some reason I can't get the rkisp1 node to configure its sink pad with the maximum resolution of the sensor (4208x3118). Instead, it sets itself to 4032x3024. This mismatch is forbidden and causes v4l2 to give us EPIPE when we try to enable the stream. Using the lower resolution gets us further--the last command (which attempts to save a single frame of video) gives output like this:
<pre>
VIDIOC_QUERYCAP: ok
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
</pre>

But then it just hangs there indefinitely.

Running under strace, we see the program stuck in an ioctl:
<pre>
ioctl(3, VIDIOC_DQBUF, {type=V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE
</pre>

[https://www.kernel.org/doc/html/v4.13/media/uapi/v4l/vidioc-qbuf.html VIDIOC_DQBUF] corresponds to dequeuing a buffer once it has been filled with an image by the v4l2 device. Apparently, the device never gives us back a captured frame.

=== Now what? ===

==== Does i2c work at all? ====

The camera driver uses i2c; we can see the camera [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts#L890-L914 in the .dts] to determine that it's on i2c bus 1, address 0x1a.

The imx258 is controlled over i2c, and sends image data over MIPI. The first step is to see if the i2c control is working.

Looking back at the driver, it seems we should see errors in dmesg if i2c communication fails. The driver checks the chip id in its probe function, which uses i2c, so we can conclude that i2c gets set up properly initially. Does it keep working?

==== Does i2c keep working? (FTrace) ====

We can see if other functions that use i2c produce errors--for example, when we run our <code>"v4l2-ctl" ... "--stream-mmap"</code> command, we expect that <code>imx258_start_streaming</code> will get called, and this function also writes a load of registers over i2c.

Build and install a kernel with CONFIG_FTRACE (not hard, but outside the scope of this write-up) and enable function graph tracing:
<pre>
$ sudo su
# cd /sys/kernel/debug/tracing
# echo function_graph > current_tracer
# cat available_filter_functions | grep -E 'rkisp|imx258|v4l2' | awk '{print $1}' > set_graph_function
# echo 'vm_map_pages,__iommu_map,iommu_map_sg_atomic,rk_iommu_map,__alloc_pages,dma_alloc_attrs,dma_mmap_attrs,__vm_map_pages,vb2_mmap,clk_e,able,schedule_timeout,clk_disable,regmap_write,schedule,__i2c_tra,sfer,i2c_tra,sfer_buffer_flags,dma_free_attrs' | tr , '\n' > set_graph_notrace
# tee trace_pipe > ~/function-trace.log
</pre>

Now, in another terminal session, run the <code>"v4l2-ctl" ... "--stream-mmap"</code> command again. We end up with a bunch (but hopefully not *too* much) of output in our first terminal and the <code>~/function-trace.log</code> file.

A quick grep shows that <code>imx258_start_streaming</code> is indeed called, so '''i2c is working properly'''.

=== If i2c works, what doesn't? ===

Our program that asks for a video frame is still hung! We ask the camera to start streaming frames, it presumably does, but the v4l2 stack never tells us a frame has finished. Doing some digging in the v4l2 stack (and the rkisp1 driver), we find out that rkisp1 is notified about frame status via interrupts.

Perhaps the hardware is never actually emitting the interrupt that signals a frame being finished. Indeed, grepping our FTrace log shows that <code>rkisp1_isr</code> is never called. A quick look at <code>/proc/interrupts</code> shows that '''the only interrupt associated with the isp has never triggered''' (0 count on every CPU):
<pre>
# head -n1 /proc/interrupts; grep isp /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
57: 0 0 0 0 0 0 GICv3 75 Level ff914000.iommu, rkisp1
</pre>

== Next steps ==

Where do we go from here? I don't know--something may be wrong with the way the .dts specifies interrupts, some kind of firmware/GIC (the rk3399's interrupt controller) configuration issue, or something else. It would be good to try to determine:

* Whether the MIPI lines actually show traffic, if someone has a logic analyzer and a dissected PPP.
* Whether the DMA of frames to memory actually happens, regardless of (lack of) emission of the interrupt that tells us when said DMA finishes a frame.
* Whether the regulator messages we see during boot are actually significant. I don't know enough about the Linux regulator framework to say whether these being not-found means power is not correctly supplied, or if Linux just isn't being properly informed of the power supply requirements for precise tracking/power-saving when the camera is off.

PinePhone Pro/IMX258 Camera Debugging

2022-05-19T03:47:54Z

Memleek:

== Background ==

The Pinephone Pro's rear camera is a Sony IMX258. The camera driver is present upstream, and at least [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro Manjaro's kernel] (downstream of Megi's) enables the driver. The camera does not seem to work; this page catalogs work on figuring out why.

== Initial status ==

What do we see in dmesg?

<pre>
imx258 1-001a: supply vana not found, using dummy regulator
imx258 1-001a: supply vdig not found, using dummy regulator
</pre>

This tells us the kernel loads the driver, which is something.

Are these errors bad/fatal? Inspecting the [https://github.com/megous/linux/blob/orange-pi-5.17/drivers/media/i2c/imx258.c source] shows us that these supplies are defined in the <code>imx258_supply_names</code> array, and <code>imx258_probe</code> calls <code>devm_regulator_bulk_get</code> to set up these supplies.
<code>imx258_probe</code> checks the return code from <code>devm_regulator_bulk_get</code>, and produces a fatal "Failed to get supplies" message if the return code is negative (indicating failure). Since we don't see this message (or any others from the driver), it looks like it loads successfully!

=== How can we test the camera? ===

==== Megapixels ====

[https://gitlab.com/postmarketOS/megapixels Megapixels] requires a per-device file to configure cameras. This one isn't complete (most of its numbers are complete nonsense), but it should let us see what happens when Megapixels tries to access the camera:
<code>pine64,pinephone-pro.ini</code>:
<pre>
[device]
make=PINE64
model=PinePhone Pro

[rear]
driver=imx258
media-driver=rkisp1
capture-width=4208
capture-height=3118
capture-rate=60
capture-fmt=GRBG10P
preview-width=1280
preview-height=960
preview-rate=60
#preview-fmt=BGGR8
capture-fmt=GRBG10P
rotate=90
mirrored=true
focallength=2.6
cropfactor=12.7
fnumber=2.8
flash-display=true
</pre>

This segfaulted Megapixels for me. After patching some trivial segfaults, I get fatal GTK4 issues and other tangential problems. Let's try something else.

==== Manually setting up a camera pipeline ====

We can roughly follow [https://www.kernel.org/doc/html/latest/admin-guide/media/rkisp1.html this guide]. Doing so gives us the following commands:
<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=800,height=600,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--verbose"
</pre>

Careful readers will note that this is setting the camera up with a low resolution compared to what the sensor can do. For some reason I can't get the rkisp1 node to configure its sink pad with the maximum resolution of the sensor (4208x3118). Instead, it sets itself to 4032x3024. This mismatch is forbidden and causes v4l2 to give us EPIPE when we try to enable the stream. Using the lower resolution gets us further--the last command (which attempts to save a single frame of video) gives output like this:
<pre>
VIDIOC_QUERYCAP: ok
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
</pre>

But then it just hangs there indefinitely.

Running under strace, we see the program stuck in an ioctl:
<pre>
ioctl(3, VIDIOC_DQBUF, {type=V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE
</pre>

[https://www.kernel.org/doc/html/v4.13/media/uapi/v4l/vidioc-qbuf.html VIDIOC_DQBUF] corresponds to dequeuing a buffer once it has been filled with an image by the v4l2 device. Apparently, the device never gives us back a captured frame.

=== Now what? ===

==== Does i2c work at all? ====

The camera driver uses i2c; we can see the camera [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts#L890-L914 in the .dts] to determine that it's on i2c bus 1, address 0x1a.

The imx258 is controlled over i2c, and sends image data over MIPI DSI. The first step is to see if the i2c control is working.

Looking back at the driver, it seems we should see errors in dmesg if i2c communication fails. The driver checks the chip id in its probe function, which uses i2c, so we can conclude that i2c gets set up properly initially. Does it keep working?

==== Does i2c keep working? (FTrace) ====

We can see if other functions that use i2c produce errors--for example, when we run our <code>"v4l2-ctl" ... "--stream-mmap"</code> command, we expect that <code>imx258_start_streaming</code> will get called, and this function also writes a load of registers over i2c.

Build and install a kernel with CONFIG_FTRACE (not hard, but outside the scope of this write-up) and enable function graph tracing:
<pre>
$ sudo su
# cd /sys/kernel/debug/tracing
# echo function_graph > current_tracer
# cat available_filter_functions | grep -E 'rkisp|imx258|v4l2' | awk '{print $1}' > set_graph_function
# echo 'vm_map_pages,__iommu_map,iommu_map_sg_atomic,rk_iommu_map,__alloc_pages,dma_alloc_attrs,dma_mmap_attrs,__vm_map_pages,vb2_mmap,clk_e,able,schedule_timeout,clk_disable,regmap_write,schedule,__i2c_tra,sfer,i2c_tra,sfer_buffer_flags,dma_free_attrs' | tr , '\n' > set_graph_notrace
# tee trace_pipe > ~/function-trace.log
</pre>

Now, in another terminal session, run the <code>"v4l2-ctl" ... "--stream-mmap"</code> command again. We end up with a bunch (but hopefully not *too* much) of output in our first terminal and the <code>~/function-trace.log</code> file.

A quick grep shows that <code>imx258_start_streaming</code> is indeed called, so '''i2c is working properly'''.

=== If i2c works, what doesn't? ===

Our program that asks for a video frame is still hung! We ask the camera to start streaming frames, it presumably does, but the v4l2 stack never tells us a frame has finished. Doing some digging in the v4l2 stack (and the rkisp1 driver), we find out that rkisp1 is notified about frame status via interrupts.

Perhaps the hardware is never actually emitting the interrupt that signals a frame being finished. Indeed, grepping our FTrace log shows that <code>rkisp1_isr</code> is never called. A quick look at <code>/proc/interrupts</code> shows that '''the only interrupt associated with the isp has never triggered''' (0 count on every CPU):
<pre>
# head -n1 /proc/interrupts; grep isp /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
57: 0 0 0 0 0 0 GICv3 75 Level ff914000.iommu, rkisp1
</pre>

== Next steps ==

Where do we go from here? I don't know--something may be wrong with the way the .dts specifies interrupts, some kind of firmware/GIC (the rk3399's interrupt controller) configuration issue, or something else. It would be good to try to determine:

* Whether the MIPI lines actually show traffic, if someone has a logic analyzer and a dissected PPP.
* Whether the DMA of frames to memory actually happens, regardless of (lack of) emission of the interrupt that tells us when said DMA finishes a frame.
* Whether the regulator messages we see during boot are actually significant. I don't know enough about the Linux regulator framework to say whether these being not-found means power is not correctly supplied, or if Linux just isn't being properly informed of the power supply requirements for precise tracking/power-saving when the camera is off.

PinePhone Pro/IMX258 Camera Debugging

2022-05-19T03:47:15Z

Memleek: Log what I've tried so far

== Background ==

The Pinephone Pro's rear camera is a Sony IMX258. The camera driver is present upstream, and at least [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro Manjaro's kernel] (downstream of Megi's) enables the driver. The camera does not seem to work; this page catalogs work on figuring out why.

== Initial status ==

What do we see in dmesg?

<pre>
imx258 1-001a: supply vana not found, using dummy regulator
imx258 1-001a: supply vdig not found, using dummy regulator
</pre>

This tells us the kernel loads the driver, which is something.

Are these errors bad/fatal? Inspecting the [https://github.com/megous/linux/blob/orange-pi-5.17/drivers/media/i2c/imx258.c source] shows us that these supplies are defined in the <code>imx258_supply_names</code> array, and <code>imx258_probe</code> calls <code>devm_regulator_bulk_get</code> to set up these supplies.
<code>imx258_probe</code> checks the return code from <code>devm_regulator_bulk_get</code>, and produces a fatal "Failed to get supplies" message if the return code is negative (indicating failure). Since we don't see this message (or any others from the driver), it looks like it loads successfully!

=== How can we test the camera? ===

==== Megapixels ====

[https://gitlab.com/postmarketOS/megapixels Megapixels] requires a per-device file to configure cameras. This one isn't complete (most of its numbers are complete nonsense), but it should let us see what happens when Megapixels tries to access the camera:
<code>pine64,pinephone-pro.ini</code>:
<pre>
[device]
make=PINE64
model=PinePhone Pro

[rear]
driver=imx258
media-driver=rkisp1
capture-width=4208
capture-height=3118
capture-rate=60
capture-fmt=GRBG10P
preview-width=1280
preview-height=960
preview-rate=60
#preview-fmt=BGGR8
capture-fmt=GRBG10P
rotate=90
mirrored=true
focallength=2.6
cropfactor=12.7
fnumber=2.8
flash-display=true
</pre>

This segfaulted Megapixels for me. After patching some trivial segfaults, I get fatal GTK4 issues and other tangential problems. Let's try something else.

==== Manually setting up a camera pipeline ====

We can roughly follow [https://www.kernel.org/doc/html/latest/admin-guide/media/rkisp1.html this guide]. Doing so gives us the following commands:
<pre>
"media-ctl" "-d" "platform:rkisp1" "-r"
"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "-l" "'rkisp1_isp':2 -> 'rkisp1_resizer_selfpath':0 [1]"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_isp":0 [fmt:SGRBG10_1X10/1048x780]'
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=1048,height=780,"
"media-ctl" "-d" "platform:rkisp1" "--set-v4l2" '"rkisp1_resizer_selfpath":0 [fmt:SGRBG10_1X10/1048x780 crop:(0,0)/1048x780]'

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "-v" "width=800,height=600,pixelformat=422P"
"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--verbose"
</pre>

Careful readers will note that this is setting the camera up with a low resolution compared to what the sensor can do. For some reason I can't get the rkisp1 node to configure its sink pad with the maximum resolution of the sensor (4208x3118). Instead, it sets itself to 4032x3024. This mismatch is forbidden and causes v4l2 to give us EPIPE when we try to enable the stream. Using the lower resolution gets us further--the last command (which attempts to save a single frame of video) gives output like this:
<pre>
VIDIOC_QUERYCAP: ok
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
</pre>

But then it just hangs there indefinitely.

Running under strace, we see the program stuck in an ioctl:
<pre>
ioctl(3, VIDIOC_DQBUF, {type=V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE
</pre>

[https://www.kernel.org/doc/html/v4.13/media/uapi/v4l/vidioc-qbuf.html VIDIOC_DQBUF] corresponds to dequeuing a buffer once it has been filled with an image by the v4l2 device. Apparently, the device never gives us back a captured frame.

=== Now what? ===

==== Does i2c work at all? ====

The camera driver uses i2c; we can see the camera [https://github.com/megous/linux/blob/c5af9f4f874a66b65c73c450b79f6a86b1b46332/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts#L890-L914 in the .dts] to determine that it's on i2c bus 1, address 0x1a.

The imx258 is controlled over i2c, and sends image data over MIPI DSI. The first step is to see if the i2c control is working.

Looking back at the driver, it seems we should see errors in dmesg if i2c communication fails. The driver checks the chip id in its probe function, which uses i2c, so we can conclude that i2c gets set up properly initially. Does it keep working?

==== Does i2c keep working? (FTrace) ====

We can see if other functions that use i2c produce errors--for example, when we run our <code>"v4l2-ctl" ... "--stream-mmap"</code> command, we expect that <code>imx258_start_streaming</code> will get called, and this function also writes a load of registers over i2c.

Build and install a kernel with CONFIG_FTRACE (not hard, but outside the scope of this write-up) and enable function graph tracing:
<pre>
$ sudo su
# cd /sys/kernel/debug/tracing
# echo function_graph > current_tracer
# cat available_filter_functions | grep -E 'rkisp|imx258|v4l2' | awk '{print $1}' > set_graph_function
# echo 'vm_map_pages,__iommu_map,iommu_map_sg_atomic,rk_iommu_map,__alloc_pages,dma_alloc_attrs,dma_mmap_attrs,__vm_map_pages,vb2_mmap,clk_e,able,schedule_timeout,clk_disable,regmap_write,schedule,__i2c_tra,sfer,i2c_tra,sfer_buffer_flags,dma_free_attrs' | tr , '\n' > set_graph_notrace
# tee trace_pipe > ~/function-trace.log
</pre>

Now, in another terminal session, run the <code>"v4l2-ctl" ... "--stream-mmap"</code> command again. We end up with a bunch (but hopefully not *too* much) of output in our first terminal and the <code>~/function-trace.log</code> file.

A quick grep shows that imx258_start_streaming is indeed called, so '''i2c is working properly'''.

=== If i2c works, what doesn't? ===

Our program that asks for a video frame is still hung! We ask the camera to start streaming frames, it presumably does, but the v4l2 stack never tells us a frame has finished. Doing some digging in the v4l2 stack (and the rkisp1 driver), we find out that rkisp1 is notified about frame status via interrupts.

Perhaps the hardware is never actually emitting the interrupt that signals a frame being finished. Indeed, grepping our FTrace log shows that <code>rkisp1_isr</code> is never called. A quick look at <code>/proc/interrupts</code> shows that '''the only interrupt associated with the isp has never triggered''' (0 count on every CPU):
<pre>
# head -n1 /proc/interrupts; grep isp /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
57: 0 0 0 0 0 0 GICv3 75 Level ff914000.iommu, rkisp1
</pre>

== Next steps ==

Where do we go from here? I don't know--something may be wrong with the way the .dts specifies interrupts, some kind of firmware/GIC (the rk3399's interrupt controller) configuration issue, or something else. It would be good to try to determine:

* Whether the MIPI lines actually show traffic, if someone has a logic analyzer and a dissected PPP.
* Whether the DMA of frames to memory actually happens, regardless of (lack of) emission of the interrupt that tells us when said DMA finishes a frame.
* Whether the regulator messages we see during boot are actually significant. I don't know enough about the Linux regulator framework to say whether these being not-found means power is not correctly supplied, or if Linux just isn't being properly informed of the power supply requirements for precise tracking/power-saving when the camera is off.

PinePhone Pro Software State

2022-05-18T19:43:05Z

Memleek:

Presently the PinePhone Pro Explorer Edition is aimed at '''Linux developers with an extensive knowledge of embedded systems and/or experience with mobile Linux'''. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile operating systems, in more general, to reach a higher degree of maturity.

Bear in mind that the software for these smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

The following table lists the feature functionality status of the unaltered pre-installed factory image of the current shipping batch and as comparison an up-to-date reference image (no responsibility is accepted for the accuracy of this information, the list is provided and updated by the community). If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the [[Main Page#Community and Support|community chat]] '''before buying the device''':

* Discord: ''#pinephone'' under https://discord.gg/pine64
* IRC: ''#pinephone'' on ''irc.pine64.org''. Note: please consider Matrix, Discord or Telegram due to the volatile nature of IRC
* Matrix: https://app.element.io/#/room/#pinephone:matrix.org
* Telegram: https://t.me/pinephone

{{Hint|The software is '''written by the community''', any contributions towards the community projects are greatly appreciated! Please see "[[How to Contribute]]" to learn about how to contribute to the software projects and "[[Where to Report Bugs]]" to learn about where to report bugs.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="min-width: 260px;" | Component
! scope="col" style="width: 120px;" | Status (factory)¹
! scope="col" style="width: 120px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="3" | Bootloader
| <code>U-Boot</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop (cause is known and currently being worked on);[[PinePhone_Pro#The battery is fully drained|Workaround]] Occasionally the eMMC fails to initialize[https://gitlab.com/postmarketOS/pmaports/-/issues/1424 Report]
|-
| <code>SPI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Unfinished
| SPI memory is currently empty in the Explorer Edition batch, a corrupted installation on the eMMC has a higher boot priority than a fresh microSD card installation, leading to a involved recovery procedure[https://tow-boot.org/ Planned]
|-
| <code>Boot GUI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Currently there is no graphical boot selection implemented[https://tow-boot.org/ Possibly planned]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]
|-
| <code>Suspend</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | Experimental
| '''Without suspend the phone will drain very fast!''' Suspend only available in specific more recent images[https://www.pine64.org/2022/03/15/march-update-introducing-the-quartzpro64/ News] Audio is often higher pitched after waking up from suspend due to a bug[https://github.com/dreemurrs-embedded/Pine64-Arch/issues/381 Report]
|-
| <code>Updates</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]; Pacman database lock preventing updates[https://wiki.archlinux.org/title/pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error Solution]; Keyring bug[Solution is to run "pinephonepro-post-install" script as root]
|-
! scope="row" rowspan="5" | Modem
| <code>General</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| The modem crashes frequently[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; Some carriers blocking specific TANs in their network[[PinePhone Carrier Support]]; '''Note:''' Proprietary firmware
|-
| <code>Phone</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The modem crashes frequently, which can lead to missed calls[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; bad call audio quality[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/249 Report];
|-
| <code>SMS</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/203 Report]; Some bugs
|-
| <code>MMS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Under certain circumstances it is difficult to wake up the screen[Citation]
|-
| <code>Touch</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver exists (drivers/media/i2c/imx258.c) but camera does not seem to capture frames
|-
| <code>Front camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver not implemented yet (a staging driver exists for this sensor using the Intel Atom ISP framework (drivers/staging/media/atomisp/i2c/ov8858.c), but it needs to be ported and cleaned up); camera not operational
|-
| <code>Camera flash</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| (tested on Manjaro; at <code>/sys/class/leds/white:flash</code>)
|
|-
| <code>WiFi</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| WiFi is expected to work. Some remaining tasks, such as "monitor mode". '''Note:''' Proprietary firmware
|-
| <code>Bluetooth</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire Info] '''Note:''' Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| aGPS to be implemented[Citation]; long loading times to get a GPS fix[Citation]; No preinstalled application[Citation]
|-
| <code>Sensors</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| "3 Axis Magnetometer" (<code>lis3mdl</code>): Not working (tested on Manjaro 5.17.6-2 kernel; not present in devicetree bindings; does not show up on i2c bus 4 as expected with <code># i2cdetect 4</code>... may have a conflict for i2c-4 addr 0x1c with <code>af8133j</code>) 
"Geo Magnetic Sensor" (<code>af8133j</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-001c/iio:device1</code>) 
"Accelerometer / Gyroscope" (<code>mpu6500</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-0068/iio:device2</code>) 
"Ambient light / Proximity" (<code>stk3311</code>): Not working (tested on Manjaro 5.17.6-2 kernel; IRQ issues)
<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">stk3311 dmesg excerpt</div>
<div class="mw-collapsible-content"><pre>
[ 9.406478] genirq: Failed to request resources for stk3310_event (irq 99) on irqchip rockchip_gpio_irq
[ 9.407380] stk3310 3-0048: request irq 99 failed
[ 9.408360] stk3310: probe of 3-0048 failed with error -5
</pre></div>
</div>
|-
| <code>Vibration motor</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Buttons</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="5" | Accessory compatibility, spare parts
| <code>Keyboard Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | WIP and critical hardware issue
| The keyboard add-on compatibility is work-in-progress. '''Hardware issue: USB-C port of the phone must not be used while the current keyboard revision is connected'''[[PinePhone_(Pro)_Keyboard#Safety|Warning]]; Top row symbols not implemented as designed[Citation]; Keyboard hot-plugging not supported[Citation]; Battery state not exposed in the pre-flashed operating system state[Citation]; general driver bugs[Citation]
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software functionality and a driver is currently missing[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Spare parts</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not available yet
| Spare parts currently not available yet in the store.[https://pine64.com/product-category/smartphone-spare-parts/ Store]
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Software rendering only
| Waydroid is an Android container used to run Android applications. Currently can only be started using software rendering due to a bug[https://github.com/waydroid/waydroid/issues/291 Report][https://gitlab.freedesktop.org/mesa/mesa/-/issues/5928 Report]
|-
|}

¹ Status of the features at the time of the last factory installation without updates

² Status of the features with an up-to-date reference image

PinePhone Pro Software State

2022-05-18T19:42:29Z

Memleek: Update flash status to Working and sensors summary to WIP

Presently the PinePhone Pro Explorer Edition is aimed at '''Linux developers with an extensive knowledge of embedded systems and/or experience with mobile Linux'''. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile operating systems, in more general, to reach a higher degree of maturity.

Bear in mind that the software for these smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

The following table lists the feature functionality status of the unaltered pre-installed factory image of the current shipping batch and as comparison an up-to-date reference image (no responsibility is accepted for the accuracy of this information, the list is provided and updated by the community). If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the [[Main Page#Community and Support|community chat]] '''before buying the device''':

* Discord: ''#pinephone'' under https://discord.gg/pine64
* IRC: ''#pinephone'' on ''irc.pine64.org''. Note: please consider Matrix, Discord or Telegram due to the volatile nature of IRC
* Matrix: https://app.element.io/#/room/#pinephone:matrix.org
* Telegram: https://t.me/pinephone

{{Hint|The software is '''written by the community''', any contributions towards the community projects are greatly appreciated! Please see "[[How to Contribute]]" to learn about how to contribute to the software projects and "[[Where to Report Bugs]]" to learn about where to report bugs.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="min-width: 260px;" | Component
! scope="col" style="width: 120px;" | Status (factory)¹
! scope="col" style="width: 120px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="3" | Bootloader
| <code>U-Boot</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop (cause is known and currently being worked on);[[PinePhone_Pro#The battery is fully drained|Workaround]] Occasionally the eMMC fails to initialize[https://gitlab.com/postmarketOS/pmaports/-/issues/1424 Report]
|-
| <code>SPI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Unfinished
| SPI memory is currently empty in the Explorer Edition batch, a corrupted installation on the eMMC has a higher boot priority than a fresh microSD card installation, leading to a involved recovery procedure[https://tow-boot.org/ Planned]
|-
| <code>Boot GUI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Currently there is no graphical boot selection implemented[https://tow-boot.org/ Possibly planned]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]
|-
| <code>Suspend</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | Experimental
| '''Without suspend the phone will drain very fast!''' Suspend only available in specific more recent images[https://www.pine64.org/2022/03/15/march-update-introducing-the-quartzpro64/ News] Audio is often higher pitched after waking up from suspend due to a bug[https://github.com/dreemurrs-embedded/Pine64-Arch/issues/381 Report]
|-
| <code>Updates</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]; Pacman database lock preventing updates[https://wiki.archlinux.org/title/pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error Solution]; Keyring bug[Solution is to run "pinephonepro-post-install" script as root]
|-
! scope="row" rowspan="5" | Modem
| <code>General</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| The modem crashes frequently[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; Some carriers blocking specific TANs in their network[[PinePhone Carrier Support]]; '''Note:''' Proprietary firmware
|-
| <code>Phone</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The modem crashes frequently, which can lead to missed calls[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; bad call audio quality[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/249 Report];
|-
| <code>SMS</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/203 Report]; Some bugs
|-
| <code>MMS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Under certain circumstances it is difficult to wake up the screen[Citation]
|-
| <code>Touch</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver exists (drivers/media/i2c/imx258.c) but camera does not seem to capture frames
|-
| <code>Front camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver not implemented yet (a staging driver exists for this sensor using the Intel Atom ISP framework (drivers/staging/media/atomisp/i2c/ov8858.c), but it needs to be ported and cleaned up); camera not operational
|-
| <code>Camera flash</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working (tested on Manjaro; at <code>/sys/class/leds/white:flash</code>)
|
|-
| <code>WiFi</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| WiFi is expected to work. Some remaining tasks, such as "monitor mode". '''Note:''' Proprietary firmware
|-
| <code>Bluetooth</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire Info] '''Note:''' Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| aGPS to be implemented[Citation]; long loading times to get a GPS fix[Citation]; No preinstalled application[Citation]
|-
| <code>Sensors</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| "3 Axis Magnetometer" (<code>lis3mdl</code>): Not working (tested on Manjaro 5.17.6-2 kernel; not present in devicetree bindings; does not show up on i2c bus 4 as expected with <code># i2cdetect 4</code>... may have a conflict for i2c-4 addr 0x1c with <code>af8133j</code>) 
"Geo Magnetic Sensor" (<code>af8133j</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-001c/iio:device1</code>) 
"Accelerometer / Gyroscope" (<code>mpu6500</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-0068/iio:device2</code>) 
"Ambient light / Proximity" (<code>stk3311</code>): Not working (tested on Manjaro 5.17.6-2 kernel; IRQ issues)
<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">stk3311 dmesg excerpt</div>
<div class="mw-collapsible-content"><pre>
[ 9.406478] genirq: Failed to request resources for stk3310_event (irq 99) on irqchip rockchip_gpio_irq
[ 9.407380] stk3310 3-0048: request irq 99 failed
[ 9.408360] stk3310: probe of 3-0048 failed with error -5
</pre></div>
</div>
|-
| <code>Vibration motor</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Buttons</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="5" | Accessory compatibility, spare parts
| <code>Keyboard Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | WIP and critical hardware issue
| The keyboard add-on compatibility is work-in-progress. '''Hardware issue: USB-C port of the phone must not be used while the current keyboard revision is connected'''[[PinePhone_(Pro)_Keyboard#Safety|Warning]]; Top row symbols not implemented as designed[Citation]; Keyboard hot-plugging not supported[Citation]; Battery state not exposed in the pre-flashed operating system state[Citation]; general driver bugs[Citation]
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software functionality and a driver is currently missing[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Spare parts</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not available yet
| Spare parts currently not available yet in the store.[https://pine64.com/product-category/smartphone-spare-parts/ Store]
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Software rendering only
| Waydroid is an Android container used to run Android applications. Currently can only be started using software rendering due to a bug[https://github.com/waydroid/waydroid/issues/291 Report][https://gitlab.freedesktop.org/mesa/mesa/-/issues/5928 Report]
|-
|}

¹ Status of the features at the time of the last factory installation without updates

² Status of the features with an up-to-date reference image

PinePhone Pro Software State

2022-05-18T19:40:09Z

Memleek: Update sensors status based on own research

Presently the PinePhone Pro Explorer Edition is aimed at '''Linux developers with an extensive knowledge of embedded systems and/or experience with mobile Linux'''. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile operating systems, in more general, to reach a higher degree of maturity.

Bear in mind that the software for these smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

The following table lists the feature functionality status of the unaltered pre-installed factory image of the current shipping batch and as comparison an up-to-date reference image (no responsibility is accepted for the accuracy of this information, the list is provided and updated by the community). If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the [[Main Page#Community and Support|community chat]] '''before buying the device''':

* Discord: ''#pinephone'' under https://discord.gg/pine64
* IRC: ''#pinephone'' on ''irc.pine64.org''. Note: please consider Matrix, Discord or Telegram due to the volatile nature of IRC
* Matrix: https://app.element.io/#/room/#pinephone:matrix.org
* Telegram: https://t.me/pinephone

{{Hint|The software is '''written by the community''', any contributions towards the community projects are greatly appreciated! Please see "[[How to Contribute]]" to learn about how to contribute to the software projects and "[[Where to Report Bugs]]" to learn about where to report bugs.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="min-width: 260px;" | Component
! scope="col" style="width: 120px;" | Status (factory)¹
! scope="col" style="width: 120px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="3" | Bootloader
| <code>U-Boot</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop (cause is known and currently being worked on);[[PinePhone_Pro#The battery is fully drained|Workaround]] Occasionally the eMMC fails to initialize[https://gitlab.com/postmarketOS/pmaports/-/issues/1424 Report]
|-
| <code>SPI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Unfinished
| SPI memory is currently empty in the Explorer Edition batch, a corrupted installation on the eMMC has a higher boot priority than a fresh microSD card installation, leading to a involved recovery procedure[https://tow-boot.org/ Planned]
|-
| <code>Boot GUI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Currently there is no graphical boot selection implemented[https://tow-boot.org/ Possibly planned]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]
|-
| <code>Suspend</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | Experimental
| '''Without suspend the phone will drain very fast!''' Suspend only available in specific more recent images[https://www.pine64.org/2022/03/15/march-update-introducing-the-quartzpro64/ News] Audio is often higher pitched after waking up from suspend due to a bug[https://github.com/dreemurrs-embedded/Pine64-Arch/issues/381 Report]
|-
| <code>Updates</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]; Pacman database lock preventing updates[https://wiki.archlinux.org/title/pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error Solution]; Keyring bug[Solution is to run "pinephonepro-post-install" script as root]
|-
! scope="row" rowspan="5" | Modem
| <code>General</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| The modem crashes frequently[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; Some carriers blocking specific TANs in their network[[PinePhone Carrier Support]]; '''Note:''' Proprietary firmware
|-
| <code>Phone</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The modem crashes frequently, which can lead to missed calls[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; bad call audio quality[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/249 Report];
|-
| <code>SMS</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/203 Report]; Some bugs
|-
| <code>MMS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Under certain circumstances it is difficult to wake up the screen[Citation]
|-
| <code>Touch</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver exists (drivers/media/i2c/imx258.c) but camera does not seem to capture frames
|-
| <code>Front camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver not implemented yet (a staging driver exists for this sensor using the Intel Atom ISP framework (drivers/staging/media/atomisp/i2c/ov8858.c), but it needs to be ported and cleaned up); camera not operational
|-
| <code>Camera flash</code>
| colspan="2" style="background:lightgray; text-align:center;" | Untested
|
|-
| <code>WiFi</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| WiFi is expected to work. Some remaining tasks, such as "monitor mode". '''Note:''' Proprietary firmware
|-
| <code>Bluetooth</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire Info] '''Note:''' Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| aGPS to be implemented[Citation]; long loading times to get a GPS fix[Citation]; No preinstalled application[Citation]
|-
| <code>Sensors</code>
| colspan="2" style="background:lightgray; text-align:center;" | Untested
| "3 Axis Magnetometer" (<code>lis3mdl</code>): Not working (tested on Manjaro 5.17.6-2 kernel; not present in devicetree bindings; does not show up on i2c bus 4 as expected with <code># i2cdetect 4</code>... may have a conflict for i2c-4 addr 0x1c with <code>af8133j</code>) 
"Geo Magnetic Sensor" (<code>af8133j</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-001c/iio:device1</code>) 
"Accelerometer / Gyroscope" (<code>mpu6500</code>): Working (tested on Manjaro, at <code>/sys/bus/i2c/devices/4-0068/iio:device2</code>) 
"Ambient light / Proximity" (<code>stk3311</code>): Not working (tested on Manjaro 5.17.6-2 kernel; IRQ issues)
<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">stk3311 dmesg excerpt</div>
<div class="mw-collapsible-content"><pre>
[ 9.406478] genirq: Failed to request resources for stk3310_event (irq 99) on irqchip rockchip_gpio_irq
[ 9.407380] stk3310 3-0048: request irq 99 failed
[ 9.408360] stk3310: probe of 3-0048 failed with error -5
</pre></div>
</div>
|-
| <code>Vibration motor</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Buttons</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="5" | Accessory compatibility, spare parts
| <code>Keyboard Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | WIP and critical hardware issue
| The keyboard add-on compatibility is work-in-progress. '''Hardware issue: USB-C port of the phone must not be used while the current keyboard revision is connected'''[[PinePhone_(Pro)_Keyboard#Safety|Warning]]; Top row symbols not implemented as designed[Citation]; Keyboard hot-plugging not supported[Citation]; Battery state not exposed in the pre-flashed operating system state[Citation]; general driver bugs[Citation]
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software functionality and a driver is currently missing[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Spare parts</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not available yet
| Spare parts currently not available yet in the store.[https://pine64.com/product-category/smartphone-spare-parts/ Store]
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Software rendering only
| Waydroid is an Android container used to run Android applications. Currently can only be started using software rendering due to a bug[https://github.com/waydroid/waydroid/issues/291 Report][https://gitlab.freedesktop.org/mesa/mesa/-/issues/5928 Report]
|-
|}

¹ Status of the features at the time of the last factory installation without updates

² Status of the features with an up-to-date reference image

PinePhone Pro Software State

2022-05-14T16:10:10Z

Memleek: Clarify front camera status

Presently the PinePhone Pro Explorer Edition is aimed at '''Linux developers with an extensive knowledge of embedded systems and/or experience with mobile Linux'''. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile operating systems, in more general, to reach a higher degree of maturity.

Bear in mind that the software for these smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

The following table lists the feature functionality status of the unaltered pre-installed factory image of the current shipping batch and as comparison an up-to-date reference image (no responsibility is accepted for the accuracy of this information, the list is provided and updated by the community). If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the [[Main Page#Community and Support|community chat]] '''before buying the device''':

* Discord: ''#pinephone'' under https://discord.gg/pine64
* IRC: ''#pinephone'' on ''irc.pine64.org''. Note: please consider Matrix, Discord or Telegram due to the volatile nature of IRC
* Matrix: https://app.element.io/#/room/#pinephone:matrix.org
* Telegram: https://t.me/pinephone

{{Hint|The software is '''written by the community''', any contributions towards the community projects are greatly appreciated! Please see "[[How to Contribute]]" to learn about how to contribute to the software projects and "[[Where to Report Bugs]]" to learn about where to report bugs.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="min-width: 260px;" | Component
! scope="col" style="width: 120px;" | Status (factory)¹
! scope="col" style="width: 120px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="3" | Bootloader
| <code>U-Boot</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop (cause is known and currently being worked on);[[PinePhone_Pro#The battery is fully drained|Workaround]] Occasionally the eMMC fails to initialize[https://gitlab.com/postmarketOS/pmaports/-/issues/1424 Report]
|-
| <code>SPI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Unfinished
| SPI memory is currently empty in the Explorer Edition batch, a corrupted installation on the eMMC has a higher boot priority than a fresh microSD card installation, leading to a involved recovery procedure[https://tow-boot.org/ Planned]
|-
| <code>Boot GUI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Currently there is no graphical boot selection implemented[https://tow-boot.org/ Possibly planned]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]
|-
| <code>Suspend</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | Experimental
| '''Without suspend the phone will drain very fast!''' Suspend only available in specific more recent images[https://www.pine64.org/2022/03/15/march-update-introducing-the-quartzpro64/ News] Audio is often higher pitched after waking up from suspend due to a bug[Citation]
|-
| <code>Updates</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]; Pacman database lock preventing updates[https://wiki.archlinux.org/title/pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error Solution]; Keyring bug[Solution is to run "pinephonepro-post-install" script as root]
|-
! scope="row" rowspan="5" | Modem
| <code>General</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| The modem crashes frequently[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; Some carriers blocking specific TANs in their network[[PinePhone Carrier Support]]; '''Note:''' Proprietary firmware
|-
| <code>Phone</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The modem crashes frequently, which can lead to missed calls[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; bad call audio quality[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/249 Report];
|-
| <code>SMS</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/203 Report]; Some bugs
|-
| <code>MMS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Under certain circumstances it is difficult to wake up the screen[Citation]
|-
| <code>Touch</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver exists (drivers/media/i2c/imx258.c) but camera does not seem to capture frames
|-
| <code>Front camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver not implemented yet (a staging driver exists for this sensor using the Intel Atom ISP framework (drivers/staging/media/atomisp/i2c/ov8858.c), but it needs to be ported and cleaned up); camera not operational
|-
| <code>Camera flash</code>
| colspan="2" style="background:lightgray; text-align:center;" | Untested
|
|-
| <code>WiFi</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| WiFi is expected to work. Some remaining tasks, such as "monitor mode". '''Note:''' Proprietary firmware
|-
| <code>Bluetooth</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire Info] '''Note:''' Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| aGPS to be implemented[Citation]; long loading times to get a GPS fix[Citation]; No preinstalled application[Citation]
|-
| <code>Sensors</code>
| colspan="2" style="background:lightgray; text-align:center;" | Untested
| Status of "3 Axis Magnetometer" [Citation], "Geo Magnetic Sensor" [Citation], "Ambient light / Proximity" [Citation], "Accelerometer / Gyroscope" [Citation] is Untested.
|-
| <code>Vibration motor</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:lightgray; text-align:center;" | Untested
|
|-
| <code>Buttons</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="5" | Accessory compatibility, spare parts
| <code>Keyboard Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | WIP and critical hardware issue
| The keyboard add-on compatibility is work-in-progress. '''Hardware issue: USB-C port of the phone must not be used while the current keyboard revision is connected'''[[PinePhone_(Pro)_Keyboard#Safety|Warning]]; Top row symbols not implemented as designed[Citation]; Keyboard hot-plugging not supported[Citation]; Battery state not exposed in the pre-flashed operating system state[Citation]; general driver bugs[Citation]
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software functionality and a driver is currently missing[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Spare parts</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not available yet
| Spare parts currently not available yet in the store.[https://pine64.com/product-category/smartphone-spare-parts/ Store]
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Software rendering only
| Waydroid is an Android container used to run Android applications. Currently can only be started using software rendering due to a bug[https://github.com/waydroid/waydroid/issues/291 Report][https://gitlab.freedesktop.org/mesa/mesa/-/issues/5928 Report]
|-
|}

¹ Status of the features at the time of the last factory installation without updates

² Status of the features with an up-to-date reference image

PinePhone Pro Software State

2022-05-14T15:47:08Z

Memleek: Update camera status to clarify that an IMX258 driver is in mainline but the rear camera still doesn't workr

Presently the PinePhone Pro Explorer Edition is aimed at '''Linux developers with an extensive knowledge of embedded systems and/or experience with mobile Linux'''. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile operating systems, in more general, to reach a higher degree of maturity.

Bear in mind that the software for these smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

The following table lists the feature functionality status of the unaltered pre-installed factory image of the current shipping batch and as comparison an up-to-date reference image (no responsibility is accepted for the accuracy of this information, the list is provided and updated by the community). If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the [[Main Page#Community and Support|community chat]] '''before buying the device''':

* Discord: ''#pinephone'' under https://discord.gg/pine64
* IRC: ''#pinephone'' on ''irc.pine64.org''. Note: please consider Matrix, Discord or Telegram due to the volatile nature of IRC
* Matrix: https://app.element.io/#/room/#pinephone:matrix.org
* Telegram: https://t.me/pinephone

{{Hint|The software is '''written by the community''', any contributions towards the community projects are greatly appreciated! Please see "[[How to Contribute]]" to learn about how to contribute to the software projects and "[[Where to Report Bugs]]" to learn about where to report bugs.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="min-width: 260px;" | Component
! scope="col" style="width: 120px;" | Status (factory)¹
! scope="col" style="width: 120px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="3" | Bootloader
| <code>U-Boot</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop (cause is known and currently being worked on);[[PinePhone_Pro#The battery is fully drained|Workaround]] Occasionally the eMMC fails to initialize[https://gitlab.com/postmarketOS/pmaports/-/issues/1424 Report]
|-
| <code>SPI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Unfinished
| SPI memory is currently empty in the Explorer Edition batch, a corrupted installation on the eMMC has a higher boot priority than a fresh microSD card installation, leading to a involved recovery procedure[https://tow-boot.org/ Planned]
|-
| <code>Boot GUI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Currently there is no graphical boot selection implemented[https://tow-boot.org/ Possibly planned]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]
|-
| <code>Suspend</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | Experimental
| '''Without suspend the phone will drain very fast!''' Suspend only available in specific more recent images[https://www.pine64.org/2022/03/15/march-update-introducing-the-quartzpro64/ News] Audio is often higher pitched after waking up from suspend due to a bug[Citation]
|-
| <code>Updates</code>
| style="background:lightcoral; text-align:center;" | Critical bugs
| style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]; Pacman database lock preventing updates[https://wiki.archlinux.org/title/pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error Solution]; Keyring bug[Solution is to run "pinephonepro-post-install" script as root]
|-
! scope="row" rowspan="5" | Modem
| <code>General</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| The modem crashes frequently[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; Some carriers blocking specific TANs in their network[[PinePhone Carrier Support]]; '''Note:''' Proprietary firmware
|-
| <code>Phone</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The modem crashes frequently, which can lead to missed calls[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/147 Report][https://gitlab.com/mobian1/devices/eg25-manager/-/issues/15 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; bad call audio quality[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/249 Report];
|-
| <code>SMS</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/203 Report]; Some bugs
|-
| <code>MMS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Under certain circumstances it is difficult to wake up the screen[Citation]
|-
| <code>Touch</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver exists (drivers/media/i2c/imx258.c) but camera does not seem to capture frames
|-
| <code>Front camera</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not working
| Driver (OV8858) not implemented yet, camera not operational
|-
| <code>Camera flash</code>
| colspan="2" style="background:lightgray; text-align:center;" | Untested
|
|-
| <code>WiFi</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| WiFi is expected to work. Some remaining tasks, such as "monitor mode". '''Note:''' Proprietary firmware
|-
| <code>Bluetooth</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire Info] '''Note:''' Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| aGPS to be implemented[Citation]; long loading times to get a GPS fix[Citation]; No preinstalled application[Citation]
|-
| <code>Sensors</code>
| colspan="2" style="background:lightgray; text-align:center;" | Untested
| Status of "3 Axis Magnetometer" [Citation], "Geo Magnetic Sensor" [Citation], "Ambient light / Proximity" [Citation], "Accelerometer / Gyroscope" [Citation] is Untested.
|-
| <code>Vibration motor</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:lightgray; text-align:center;" | Untested
|
|-
| <code>Buttons</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="5" | Accessory compatibility, spare parts
| <code>Keyboard Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | WIP and critical hardware issue
| The keyboard add-on compatibility is work-in-progress. '''Hardware issue: USB-C port of the phone must not be used while the current keyboard revision is connected'''[[PinePhone_(Pro)_Keyboard#Safety|Warning]]; Top row symbols not implemented as designed[Citation]; Keyboard hot-plugging not supported[Citation]; Battery state not exposed in the pre-flashed operating system state[Citation]; general driver bugs[Citation]
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software functionality and a driver is currently missing[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Spare parts</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not available yet
| Spare parts currently not available yet in the store.[https://pine64.com/product-category/smartphone-spare-parts/ Store]
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Software rendering only
| Waydroid is an Android container used to run Android applications. Currently can only be started using software rendering due to a bug[https://github.com/waydroid/waydroid/issues/291 Report][https://gitlab.freedesktop.org/mesa/mesa/-/issues/5928 Report]
|-
|}

¹ Status of the features at the time of the last factory installation without updates

² Status of the features with an up-to-date reference image

PinePhone FAQ

2021-02-10T17:25:45Z

Memleek: /* I want a replacement battery, which one should I buy? */ Clarify battery compatibility.

A list of frequently asked question.

== Hardware ==

=== Revisions ===
==== What are Community Editions? ====
Community Editions of the PinePhone are special versions which comes preinstalled with the operating system of the partner project and features the logo of this project on the back panel. The Community Edition is intended to help partner projects developing these systems: "Community editions are meant to bring exposure to partner-projects operating systems and communities, as well as help finance ongoing development.", [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ source].

==== Is the Community Edition the latest revision? ====
Yes, they are! The Community Edition PinePhones are the latest versions of the PinePhone, featuring the mainboard numbers 1.2 through 1.2b and branded back covers. The only difference between each Community Edition is the inclusion of crucial bug fixes, with the last issue being fixed with the 1.2b motherboard shipping with the Manjaro CE PinePhones. Aside from the back cover, the only other difference is that starting with the postmarketOS edition PinePhone, a convergence package option was released that adds another gigabyte of ram to the phone and a 32GB eMMC instead of a 16GB eMMC. Convergence packages also included a dock for plugging in USB peripherals and connecting to a HDMI monitor, however you can purchase a generic USB-C dock to use with a 2GB PinePhone. The predecessor to the Convergence Edition PinePhones was the Braveheart Edition intended for developers to bring up the platform, which had the version number 1.1. For more details about the topic see [[PinePhone#Hardware Revisions]].

There is currently no plans for further hardware changes beyond the mainboard 1.2b which shipped with the Manjaro CE.

==== Will there be other Community Editions? ====
Five Community Editions have been announced: [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ UBports], [https://www.pine64.org/2020/06/15/june-update-postmarketos-ce-pinephone-shipping-pine64-cluster/ postmarketOS], [https://www.pine64.org/2020/08/31/pinephone-manjaro-community-edition/ Manjaro], [https://www.pine64.org/2020/12/01/kde-community-edition-is-now-available/ KDE], and [https://www.pine64.org/2021/01/17/mobian-community-edition/ Mobian]. At this time no further Community Editions are expected. Pine64 is intending to transition to the release of retail units with partners.

==== In simple terms, what are the differences between Braveheart and the new Community Edition? ====
The Braveheart PinePhone was the first public revision of the PinePhone which was intended solely for developers and Linux enthusiasts. The Ubports Community Edition was the next revision of the PinePhone with an updated mainboard based on feedback from the Braveheart Edition, see [[PinePhone#Hardware Revisions]]. All current revisions of the PinePhone continue to be intended for developers and enthusiasts, however Pine64 will be starting to offer partnered retail units of the PinePhone in 2021 which will have a better warranty and technical support (keep in mind even then it is not intended for a broader audience at this time, as the software still needs work and the hardware does not hold up well to modern consumer standards).

==== Will there be a newer revision after the Community Editions? ====
It is highly unlikely (unless major issues are found in the latest revision). Starting with the Ubports Community Edition the PinePhone has gotten CE and FCC certifications, repeating the certification process due to changes in the hardware design is very expensive, so the Community Edition(s) are viewed as the final revision besides critical fixes.

The Community Edition PinePhones (and parts for them) will be produced and sold for at least 5 years. There are ideas for a newer PinePhone with updated hardware, however this is multiple years away and there is no solid plan for it yet (3-5 years).

==== Will there be hardware differences between the Community Editions? ====

Besides the varied back covers, starting with the launch of the PostmarketOS CE there has been the release of a convergence package option for the PinePhone which includes more ram and storage, and a included dock for convenience. There has also been multiple hardware changes starting with the Ubports CE (mainboard 1.2) and ending with the Manjaro CE (mainboard 1.2b). There is currently no plans for future hardware changes for a few years.

==== How powerful is the PinePhone's hardware? ====

The PinePhone is about on par with a Raspberry Pi 3 in terms of CPU power, however going by GFLOPS it has half the GPU power. The Pi 3's Videocore IV does 24 GFLOPS, and the Mali 400 MP2 on the PinePhone only 10.8.

Despite this, using software rendering the PinePhone is capable of smoothly rendering at 1080p resolution or higher. However, with a fully GPU-accelerated mobile environment you should expect a more sluggish experience outputting to such resolutions. Unfortunately the Mali 400 MP2 (a 2008 arm mobile GPU) simply isn't intended to push 1080p resolution. With that said, the VPU of the PinePhone has been shown to handle smooth H.264 1440p30 video playback using Cedrus and gstreamer as documented [https://xnux.eu/log/#001 here]. Further, the PinePhone should be more than capable of a smooth phone experience when used in conjunction with well optimized software that makes use of its hardware features. It is also more than capable of running many light games (including 3D ones such as Supertuxkart), and retro gaming. Expect further speed improvements over time as the drivers are improved, and in the meanwhile you can look into slightly [[overclocking]] the device (at your own risk).

=== Sound ===
=== Modem ===

==== The modem isn't working ====

In order to use the modem and WiFi/Bluetooth, you need to ensure the battery is inside the device and has a sufficient charge. Even when supplying the phone with enough power, the modem and WiFi chip will not work without a connected battery. Further, double check that you have no put the SD card into the sim card slot, or vice versa.

==== Does the PinePhone only wakeup from sleep for calls and texts? ====

Yes. Unless the PinePhone is configured to wakeup every few minutes from deep sleep in crust (At the cost of battery life. However, in the future there may be other solutions), then there is not any way to get any notifications for applications. The modem on the PinePhone will wake the device for incoming calls and texts however, and the real time clock is also capable of waking the device for alarms.

=== Battery ===

==== The battery is stuck inside the phone ====

The battery can be stuck in the phone if the screws of the frame are overtightened.

If your battery is stuck inside the PinePhone, grab a screw driver and completely unscrew all the screws of the midframe. Then pull out the battery (you may have to fully take off the midframe in some cases to get it out). And then rescrew the midframe, but only tighten the screws to the point where they are just barely tight to hold. This should allow you to remove the battery easily.

==== The battery is discharging while the phone is powered off (Braveheart Edition) ====

The issue is not present on the Community Edition. Due to a hardware bug, after poweroff, the phone still consumes 20–30mA which drains the battery in 3-4 days. A manual procedure to fix the hardware bug is described [https://xnux.eu/devices/pp-pmic-fix.jpg here].

=== Kill Switches ===
==== What are the kill switches doing? ====

{| class="wikitable"
|-
! Number
! Name
! Explanation
! Description
|-
| 1
| Modem
| Pulls Q1501 gate up (FET killing modem power)
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| Pulls up CHIP_EN
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| Breaks microphone bias voltage from the SoC
| "On" enables audio input from on-board microphones (not 3.5mm jack), "off" disables it.
|-
| 4
| Rear camera
| Pulls up PWDN on OV5640
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| Pulls up PWDN on GC2145
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| Pulls up IN2 on analog switch BCT4717ETB
| "On" enables audio input and output via the 3.5mm audio jack, "off" switches the jack to hardware UART mode.
|}

=== Memory ===

==== What's the speed difference between the eMMC and SD cards? ====
Maximum transfer speed of the eMMC is around 85 MB/s, while SD cards are limited to approximately 23 MB/s (even with faster cards).

=== GPS ===

==== GPS doesn't work ====

Like almost all smartphones, the PinePhone GPS antenna is small and can only get a first fix unassisted if the GPS signal is very strong. To make first fix faster and more reliable, phones download assistance data either from the phone network or from the internet. The GPS in the PinePhone modem supports the internet based assistance method, as detailed in the modem documentation, but this isn't yet supported out of the box by any of the distros. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] to show that it can work.

Until AGPS support makes its way into the distros you'll have to make some manual changes - see for example [https://wiki.mobian-project.org/doku.php?id=location Mobian wiki]

===== Broken hardware? =====

One or two people have reported no signal from any satellites, whether using the AGPS proof of concept script or not. This suggests a problem with the antenna, as even without AGPS it is normal for the system to detect the presence of a signal from satellites, even when it's too weak to get a first fix.

== Software ==

=== Installation ===

==== How can I install an operating system on the SD card / eMMC? ====

See [[PinePhone Installation Instructions]].

=== Updating ===

Read the [[PinePhone Updating Instructions]].

=== Booting ===

==== What's the boot order for SD cards and eMMC? ====

The PinePhone will automatically boot from microSD if a bootable card is inserted. If no (bootable) microSD is found, it will boot from eMMC.

==== How can I select different OSes at boot? ====

There is a project by Danct12 which allows the user to select different OSes at boot, the software is currently work-in-progress: https://github.com/dreemurrs-embedded/Pineloader.

==== I turned on my Manjaro CE PinePhone. The red LED and screen backlight are briefly lit, then both are not and it will not boot. ====

This can be the result of at least one situation:

# The eMMC installation became corrupt or otherwise unbootable
# An SD card is present but not bootable (consider [[PinePhone#Detailed usage instructions]])

If there is an installation of Manjaro on both the eMMC & an SD card, the SD card will always boot first on the device. Try taking the SD card out and booting the installation that is on the eMMC. If the problem persists, it is likely there is an issue with both installations and you will need to reinstall your distribution. You may also want to check with your distribution's maintainers if boot issues are a common problem in a recent update.

==== I did not install an update in Ubuntu Touch and I'm stuck on the Pine64 logo after rebooting. ====

# Use a USB A-C cable to plug your phone into your PC
# Hold the PinePhone's power button for 4 seconds or more to power it off.
# Wait 5 seconds
# Hold the Volume Up and Power buttons on the PinePhone to boot into recovery. You should see the LED light red, then yellow, then green. The "Installing update" screen will appear, but a progress bar to indicate update progress will not. Ignore the "Installing update" part.
# Your PC may automatically mount the PinePhone's partitions. If it does, Safely Remove or Eject all of them.
# Open a terminal on your PC. Type <code>telnet 172.16.42.1</code>
# You should receive the text 'Welcome to Rescue SD Shell!'
# In the new Rescue SD shell, type <code>umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync</code>
# Once this command pipeline finishes, type <code>sync && reboot -f</code>

Your PinePhone should reboot into Ubuntu Touch. Now head to Settings -> Updates and install the new update!

If these steps did not solve your issue, please create a new thread here on the Pine64 forums, note what the problem looks like, then say that you've tried these steps already.

This is caused by corruption on the userdata partition. Normally this should be fixed by 'e2fsck' in the initramfs, however an error in image creation means that that version of e2fsck is unable to correct corruption. This has been fixed in all new PinePhone updates, so if you update from the factory image to any other image available to the PinePhone now, you will not experience this issue any longer.

==== I turned on my PinePhone running Ubuntu Touch. The red LED is lit and it will not boot. ====
# Hold the power button until the light turns off
# Hold the power button until the light turns on

You may need to repeat these steps more than once.

This is caused by u-boot apparently trying to use the eMMC before it is ready. We are not entirely sure why this occurs yet.

==== Can I install a different OS on my Community Edition? ====

Yes! While all of the Community Edition Pinephones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see [[PinePhone Installation Instructions]] and [[PinePhone Software Releases]] on how to install them.

=== Other ===

==== How can I enable SSH? ====

In Ubuntu Touch you can run "sudo start ssh" to get a one-time start, or edit /etc/init/ssh.override and remove the manual line to make it auto-start.

In other distributions you may have to install ssh through its package manager and then proceed to use its init system to enable it. For Manjaro, Arch, and Mobian you can use "systemctl enable" and "systemctl start" command to enable and start ssh.

==== What works, what doesn't? ====

For Ubuntu Touch see https://gitlab.com/ubports/community-ports/pinephone#what-works-what-doesnt.

Other distributions will have different levels of functionality. Please refer to the release page of your chosen distribution for further information.

==== I can't connect to a 2.4Ghz Wi-Fi network in Ubuntu Touch. ====

Reboot your device by holding the power button until the "Power" dialog appears, then pressing "Restart".

If that does not fix the issue, note that all the following conditions must be met to use WiFi on the PinePhone:

# The plastic tab between the battery and the device's battery contacts has been removed
# The battery is installed
# The WiFi killswitch, #2, on the rear of the device is switched "ON"

Wi-Fi in the PinePhone only seems stable after a warm reboot like this.

==== What's the status of Android for the PinePhone? ====

Currently, there isn't any major push to get Android running well on the PinePhone. The developer Icenowy did get a Android image to run and partly work, it was however slow and buggy, with major functions not working. A solution for running some of your android apps may be found in Anbox as of now. Anbox is currently not included in Ubuntu Touch. In other distributions your millage may vary on what applications will run and how well.

==== Why are my apps loading slower than on my Android phone? ====

Android has multiple techniques in place to speed up launching applications after the first launch, such as the "Dalvik cache".

Using a alternative filesystem such as F2FS on the eMMC (which is considerably faster than running software on the SD card) may help improve performance slightly. Over time you can expect further optimizations and improvements in various distributions that will help speed up the PinePhone.

=== SMS ===

==== The phone does not receive SMS ====

Sometimes incoming SMS messages are not being received, but outgoing ones, phone calls and data are working fine. One potential cause could be SMS messages that linger in the modem's queue (10 or more of them). This queue appears to be persistent across reboots and also re-imaging the OS.

On Mobian and Manjaro, the ModemManager does all of the communications with the 3G modem including phone calls, cellular data, GPS and SMS. This may not be the case with other PinePhone OSes.

You can access the ModemManager using the mmcli command.

'''Mobian:'''

<pre>$ sudo mmcli -m 0 --messaging-list-sms
Found 10 SMS messages:
/org/freedesktop/ModemManager1/SMS/0 (received)</pre>

'''Manjaro:'''

<pre>$ sudo mmcli -m 3 --messaging-list-sms
/org/freedesktop/ModemManager1/SMS/77 (received)</pre>

For Mobian, delete all of the messages like this:

<code>$ sudo mmcli -m 0 --messaging-delete-sms=1</code> (Repeat with 1 through 10 to delete all of the messages)

For Manjaro, delete all of the messages like this:

<code>$ sudo mmcli -m 3 --messaging-delete-sms=77</code> (Repeat with all listed messages)

Note that the "-m 0" or "-m 3" refers to modem 0 or 3 (the only one in a PinePhone). For more help on the messaging related actions available in mmcli you can check the help with <code>mmcli --help-messaging.</code> This article is also helpful in learning: https://electronproton.com/mmcli-command-examples/. For your particular configuration, you may need to try different "-m #" combinations, e.g., "-m 2" or "-m 4." "-m 0" is not always the default.

It should also be noted that recent releases of Mobian and postmarketOS now include a userspace daemon called [https://gitlab.com/mobian1/devices/eg25-manager eg25-manager], which helps manage the modem and ensure proper operation.

== Shipping ==
=== I did not receive an order confirmation ===
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get a order confirmation email.

=== When does the phone ship? ===
For up-to-date information when the phone's shipping date is estimated, see the edits in this forum post: https://forum.pine64.org/showthread.php?tid=9942.

=== It is shipping day but I did not receive a shipping notification ===
For shipments with DHL the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.

=== When does my phone ship if I order now? ===
Orders made after Friday, 22nd May 2020 are shipped after the first bulk of pre-orders has been shipped. The exact date is not known yet due to various reasons, it may be a few weeks after the first bulk shipped. [https://forum.pine64.org/showthread.php?tid=9942 The forum] will be edited with updated information and you will receive a shipping notification when the device was shipped.

=== What about import taxes? ===
Import taxes have to be payed by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.

== Accessories ==

=== Protection ===
==== Which screen protector should i use? ====

Protecting your screen is important, especially for devices like the PinePhone that doesn't have access to the newest glass technology.
The Braveheart and Community Editions of the PinePhone comes with a plastic film screen protector installed, and Pine64 sells a tempered glass screen protector [https://pine64.com/product/pinephone-tempered-glass-screen-protector/ in their store].

You can also buy a third party screen protector, as the screen protectors for the iPhone 11 Pro Max/XS Max fit the PinePhone pretty well based on [https://forum.pine64.org/showthread.php?tid=8458&pid=65409#pid65409 this] forum post.

=== Batteries ===
==== I want a replacement battery, which one should I buy? ====

Replacement batteries for US customers are available in the store.

Currently the PinePhone battery is known to be compatible with replacement batteries for the Samsung J700. Specifically, models "EB-BJ700BBC" and "EB-BJ700BBE" are compatible with all PinePhone models, and "EB-BJ700CBE" is compatible with Community Editions [https://www.reddit.com/r/PINE64official/comments/kcof97/pinephone_replacement_battery_found_and_tested/gfrx4p2/?utm_source=reddit&utm_medium=web2x&context=3 after UBPorts] (due to plastic tabs on its bottom which only the newer phones [https://forum.pine64.org/showthread.php?tid=11901 have tolerance for]).

=== External hardware ===

==== Will Pine64 sell other addons made for the PinePhone? ====

Yes, currently there is a keyboard case [https://forum.pine64.org/showthread.php?tid=8537&pid=55396#pid55396 with similarities to the Psion 5] which includes an internal battery, and a [https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/ Qi wireless charging] add-on planned, both of which Pine64 intends to directly sell. There is the potential for future add-ons such as a game pad, however that is currently just an idea and not in any way planned.

==== Which 3rd party hardware can connect to my PinePhone? ====

See [[PinePhone Hardware Accessory Compatibility]].

[[Category:PinePhone]]