PINE64 - User contributions [en]

PinePhone Hardware Accessory Compatibility

2020-11-03T03:49:41Z

E1337: using hint box for the "call to action" note

List of devices that have been tried on the PinePhone, and the results.

== Protection ==
=== Screen protector ===
The official screen protector can be found in the Pine64 store under [https://pine64.com/product/pinephone-tempered-glass-screen-protector/?v=0446c16e2e66 PinePhone Tempered Glass Screen Protector].

Most screen protectors for the iPhone 11 Pro Max and the iPhone XS Max fit the PinePhone (if the top notch is not obscured by a black foil or similar).

=== Case ===
The Pine store got official cases:

* [https://pine64.com/?product=pinephone-hard-protective-case&v=0446c16e2e66 PinePhone Hard Protective Case]
* [https://pine64.com/?product=pinephone-soft-tpu-protective-case-reduce-digital-gap-donation-program&v=0446c16e2e66 PinePhone Soft TPU Protective Case - "Reduce Digital Gap" Donation Program]

Tight-fit cases of other phones can't be alienated for the PinePhone due as most times the proportions and/or camera notch won't fit. The phone can however also be used with "phone sleeves", such as those from fitBAG. The sleeve from fitBAG for the Xiaomi Redmi Note 8 Pro is fitting the PinePhone very tightly.

== Peripheral equipment ==
=== Hubs ===
USB hubs do not require a custom driver and are therefore expected to be compatible with the PinePhone, as long as they are within the specification. On revisions the PinePhone mainboard revisions v1.1 and v1.2 the VCONN fix is required, on v1.2a and later the USB hub should work out of the box, see [[PinePhone#Hardware revisions]].

=== Bluetooth devices ===
In general, Bluetooth should be working. However, due to the audio setup on the PinePhone being complicated due to the dynamic rerouting needed for phone calls, Bluetooth-based audio might still be in a finicky state no matter the exact headphones or speakers used. {{Hint|''Note:'' for people who have new info on the PinePhone's general Bluetooth audio state e.g. from own tests, feel free to update this text.}}
{| class="wikitable sortable"
!Name || Product info || Hardware ID || Result || Tested OS || Notes
|-
| Test || Test || Test || Test || Test || Test
|-
|}



[[Category:PinePhone]]

PinePhone Hardware Accessory Compatibility

2020-11-03T03:37:59Z

E1337: another really minor grammar improvement

List of devices that have been tried on the PinePhone, and the results.

== Protection ==
=== Screen protector ===
The official screen protector can be found in the Pine64 store under [https://pine64.com/product/pinephone-tempered-glass-screen-protector/?v=0446c16e2e66 PinePhone Tempered Glass Screen Protector].

Most screen protectors for the iPhone 11 Pro Max and the iPhone XS Max fit the PinePhone (if the top notch is not obscured by a black foil or similar).

=== Case ===
The Pine store got official cases:

* [https://pine64.com/?product=pinephone-hard-protective-case&v=0446c16e2e66 PinePhone Hard Protective Case]
* [https://pine64.com/?product=pinephone-soft-tpu-protective-case-reduce-digital-gap-donation-program&v=0446c16e2e66 PinePhone Soft TPU Protective Case - "Reduce Digital Gap" Donation Program]

Tight-fit cases of other phones can't be alienated for the PinePhone due as most times the proportions and/or camera notch won't fit. The phone can however also be used with "phone sleeves", such as those from fitBAG. The sleeve from fitBAG for the Xiaomi Redmi Note 8 Pro is fitting the PinePhone very tightly.

== Peripheral equipment ==
=== Hubs ===
USB hubs do not require a custom driver and are therefore expected to be compatible with the PinePhone, as long as they are within the specification. On revisions the PinePhone mainboard revisions v1.1 and v1.2 the VCONN fix is required, on v1.2a and later the USB hub should work out of the box, see [[PinePhone#Hardware revisions]].

=== Bluetooth devices ===
In general, Bluetooth should be working. However, due to the audio setup on the PinePhone being complicated due to the dynamic rerouting needed for phone calls, Bluetooth-based audio might still be in a finicky state no matter the exact headphones or speakers used. (''Note:'' for people who have new info on this e.g. from own tests, feel free to update this text.)
{| class="wikitable sortable"
!Name || Product info || Hardware ID || Result || Tested OS || Notes
|-
| Test || Test || Test || Test || Test || Test
|-
|}



[[Category:PinePhone]]

PinePhone Hardware Accessory Compatibility

2020-11-03T03:37:13Z

E1337: minor grammar typo fix

List of devices that have been tried on the PinePhone, and the results.

== Protection ==
=== Screen protector ===
The official screen protector can be found in the Pine64 store under [https://pine64.com/product/pinephone-tempered-glass-screen-protector/?v=0446c16e2e66 PinePhone Tempered Glass Screen Protector].

Most screen protectors for the iPhone 11 Pro Max and the iPhone XS Max fit the PinePhone (if the top notch is not obscured by a black foil or similar).

=== Case ===
The Pine store got official cases:

* [https://pine64.com/?product=pinephone-hard-protective-case&v=0446c16e2e66 PinePhone Hard Protective Case]
* [https://pine64.com/?product=pinephone-soft-tpu-protective-case-reduce-digital-gap-donation-program&v=0446c16e2e66 PinePhone Soft TPU Protective Case - "Reduce Digital Gap" Donation Program]

Tight-fit cases of other phones can't be alienated for the PinePhone due as most times the proportions and/or camera notch won't fit. The phone can however also be used with "phone sleeves", such as those from fitBAG. The sleeve from fitBAG for the Xiaomi Redmi Note 8 Pro is fitting the PinePhone very tightly.

== Peripheral equipment ==
=== Hubs ===
USB hubs do not require a custom driver and are therefore expected to be compatible with the PinePhone, as long as they are within the specification. On revisions the PinePhone mainboard revisions v1.1 and v1.2 the VCONN fix is required, on v1.2a and later the USB hub should work out of the box, see [[PinePhone#Hardware revisions]].

=== Bluetooth devices ===
In general, Bluetooth should be working. However, due to the audio setup on the PinePhone being complicated by the dynamic rerouting needed for phone calls, Bluetooth-based audio might still be in a finicky state no matter the exact headphones or speakers used. (''Note:'' for people who have new info on this e.g. from own tests, feel free to update this text.)
{| class="wikitable sortable"
!Name || Product info || Hardware ID || Result || Tested OS || Notes
|-
| Test || Test || Test || Test || Test || Test
|-
|}



[[Category:PinePhone]]

PinePhone Hardware Accessory Compatibility

2020-11-03T03:36:40Z

E1337: Add note on bluetooth audio

List of devices that have been tried on the PinePhone, and the results.

== Protection ==
=== Screen protector ===
The official screen protector can be found in the Pine64 store under [https://pine64.com/product/pinephone-tempered-glass-screen-protector/?v=0446c16e2e66 PinePhone Tempered Glass Screen Protector].

Most screen protectors for the iPhone 11 Pro Max and the iPhone XS Max fit the PinePhone (if the top notch is not obscured by a black foil or similar).

=== Case ===
The Pine store got official cases:

* [https://pine64.com/?product=pinephone-hard-protective-case&v=0446c16e2e66 PinePhone Hard Protective Case]
* [https://pine64.com/?product=pinephone-soft-tpu-protective-case-reduce-digital-gap-donation-program&v=0446c16e2e66 PinePhone Soft TPU Protective Case - "Reduce Digital Gap" Donation Program]

Tight-fit cases of other phones can't be alienated for the PinePhone due as most times the proportions and/or camera notch won't fit. The phone can however also be used with "phone sleeves", such as those from fitBAG. The sleeve from fitBAG for the Xiaomi Redmi Note 8 Pro is fitting the PinePhone very tightly.

== Peripheral equipment ==
=== Hubs ===
USB hubs do not require a custom driver and are therefore expected to be compatible with the PinePhone, as long as they are within the specification. On revisions the PinePhone mainboard revisions v1.1 and v1.2 the VCONN fix is required, on v1.2a and later the USB hub should work out of the box, see [[PinePhone#Hardware revisions]].

=== Bluetooth devices ===
In general, Bluetooth should be working. However, due to the audio setup on the PinePhone being complicated by the dynamic rerouting needed for phone calls, Bluetooth-based audio might still be in a finicky state no matter on the exact headphones or speakers used. (''Note:'' for people who have new info on this e.g. from own tests, feel free to update this text.)
{| class="wikitable sortable"
!Name || Product info || Hardware ID || Result || Tested OS || Notes
|-
| Test || Test || Test || Test || Test || Test
|-
|}



[[Category:PinePhone]]

PinePhone Hardware Accessory Compatibility

2020-11-03T01:28:39Z

E1337: Adding a note encouraging people to fill in missing data

List of devices that have been tried on the PinePhone, and the results.

== Protection ==

=== Screen protector ===

The official screen protector can be found in the Pine64 store under [https://pine64.com/product/pinephone-tempered-glass-screen-protector/?v=0446c16e2e66 PinePhone Tempered Glass Screen Protector].

Most screen protectors for the iPhone 11 Pro Max and the iPhone XS Max fit the PinePhone (if the top notch is not obscured by a black foil or similar).

=== Case ===

The Pine store got official cases:

* [https://pine64.com/?product=pinephone-hard-protective-case&v=0446c16e2e66 PinePhone Hard Protective Case]
* [https://pine64.com/?product=pinephone-soft-tpu-protective-case-reduce-digital-gap-donation-program&v=0446c16e2e66 PinePhone Soft TPU Protective Case - "Reduce Digital Gap" Donation Program]

Tight-fit cases of other phones can't be alienated for the PinePhone due as most times the proportions and/or camera notch won't fit. The phone can however also be used with "phone sleeves", such as those from fitBAG. The sleeve from fitBAG for the Xiaomi Redmi Note 8 Pro is fitting the PinePhone very tightly.

== Peripheral equipment ==
'''Note: if you tested any of the listed entries with an "Unknown" in any column, please feel encouraged to fill it in.''' (Even if you aren't the original tester who originally added the row!)

{| class="wikitable sortable"

!Type || Make/Model || Connected via || Hardware IDs || Result || Tested OS || Tested PinePhone HW (1.2, 1.2a, ...) || Notes
|-
|USB-C Hub || [https://www.aliexpress.com/item/32954358411.html AliExpress 5-1 USB-C Hub] || USB-C || 05e3:0626 hub || PD not working, rest not working yet ||UBPorts/pmOS || Unknown || HDMI, GBit eth, 2xUSB-3, USB-C PD [http://www.sympato.ch/~dryak/files/usbc-dock.jpg image]
|-
|Bluetooth Keyboard || Unknown(? maybe this entry should be removed) || Bluetooth || -- || No pairing via ui, but functional via terminal || pmOS || Unknown || [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Bluetooth Instructions]
|-
|USB-C Hub || [https://www.tsbohemia.cz/umax-u-connect-type-c-multiport-h7_d350000.html UMAX U-Connect Type-C Multiport H7] || USB-C || - || USB-A ports, PD, HDMI works, SD card reader not enumerating on PP with removed VCONN switches (may need VCONN) || Arch Linux || Unknown || HDMI, 3xUSB-3, USB-C PD, SD reader
|-
|USB-C Soundcard || [https://store.google.com/?srp=/product/usb_c_headphone_adapter Google Pixel USB-C to 3.5mm adapter] || USB-C || 18d1:5029 || Works, recognized as usb soundcard, but only if a cable is plugged in || pmOS || Unknown ||
|-
|-
|USB-C Hub || [https://www.anker.com/products/variant/powerexpand--7in1-usbc-pd-ethernet-hub/A83520A1 Anker PowerExpand+ 7-in-1 USB-C PD Ethernet Hub] || USB-C || -- || USB Ports and HDMI Port work, can charge while using this device (needs VCONN HW mod) || [https://wiki.mobian-project.org/doku.php?id=mods Mobian] || Unknown || HDMI, USB3, Ethernet, PD-USBC, SD Card, Micro SD Card
|-
|USB-C Hub || [https://www.dell.com/support/article/en-us/sln296829/how-to-use-and-troubleshoot-dell-docking-station-wd15?lang=en Dell WD-15 Docking station] || USB-C || 0424:2807 || USB Ports and charging works. Audio sinks and DP status changes are detected (needs VCONN HW mod and ANX firmware) || pmOS || Unknown || HDMI, VGA and DP might work after a kernel update. ANX firmware is needed for charging after VCONN mod.
|-
|USB-C Hub || [https://www.microsoft.com/en-us/mobile/accessory/hd-500/specifications Microsoft HD-500 Dock] || USB-C || -- || USB Hub, Display Out, and Power Delivery all works. (needs VCONN HW mod and ANX firmware) || [https://wiki.mobian-project.org/doku.php?id=mods Mobian] || Unknown ||
|-
|USB-C Hub || [https://support.hp.com/us-en/product/hp-elite-x3-lap-dock/12088822/document/c05320203 HP Elite x3 LapDock] || USB-C || -- || Dock display, keyboard/trackpad, and Power Delivery all works. (needs VCONN HW mod and ANX firmware) || [https://wiki.mobian-project.org/doku.php?id=mods Mobian] || Unknown || Haven't tested micro-HDMI port or the internal USB-C hub.
|-
|USB-C Hub || [https://www.kjell.com/se/produkter/dator/mac-tillbehor/plexgear-multiadapter-for-usb-c-med-7-anslutningar-p62099 Plexgear 7-port multi adapter with PD and SD-card reader] || USB-C || USB-hub: 0bda:5411 (RTS5411); Ethernet: 0bda:8153 (RTL8153); SD-card reader: 05e3:0749; Audio: 0c76:161f; 2109:0102; 0c76:161f || Everything seems to work. PD, 3x USB 2.0 ports, ethernet, HDMI, SD-card, audio. || Arch Linux || 1.2 with VCONN mod (CC switches removed) ||
|-
|}

[[Category:PinePhone]]

PinePhone Hardware Accessory Compatibility

2020-11-03T01:26:06Z

E1337: Just clearing the table because it's imperfect won't improve it, so I restored the table. I added a hw column to encourage people to fill it. I cleaned up type + model columns so people fill it in properly. Hopefully this will actually improve things in the future

List of devices that have been tried on the PinePhone, and the results.

== Protection ==

=== Screen protector ===

The official screen protector can be found in the Pine64 store under [https://pine64.com/product/pinephone-tempered-glass-screen-protector/?v=0446c16e2e66 PinePhone Tempered Glass Screen Protector].

Most screen protectors for the iPhone 11 Pro Max and the iPhone XS Max fit the PinePhone (if the top notch is not obscured by a black foil or similar).

=== Case ===

The Pine store got official cases:

* [https://pine64.com/?product=pinephone-hard-protective-case&v=0446c16e2e66 PinePhone Hard Protective Case]
* [https://pine64.com/?product=pinephone-soft-tpu-protective-case-reduce-digital-gap-donation-program&v=0446c16e2e66 PinePhone Soft TPU Protective Case - "Reduce Digital Gap" Donation Program]

Tight-fit cases of other phones can't be alienated for the PinePhone due as most times the proportions and/or camera notch won't fit. The phone can however also be used with "phone sleeves", such as those from fitBAG. The sleeve from fitBAG for the Xiaomi Redmi Note 8 Pro is fitting the PinePhone very tightly.

== Peripheral equipment ==

{| class="wikitable sortable"

!Type || Make/Model || Connected via || Hardware IDs || Result || Tested OS || Tested PinePhone HW (1.2, 1.2a, ...) || Notes
|-
|USB-C Hub || [https://www.aliexpress.com/item/32954358411.html AliExpress 5-1 USB-C Hub] || USB-C || 05e3:0626 hub || PD not working, rest not working yet ||UBPorts/pmOS || Unknown || HDMI, GBit eth, 2xUSB-3, USB-C PD [http://www.sympato.ch/~dryak/files/usbc-dock.jpg image]
|-
|Bluetooth Keyboard || Unknown(? maybe this entry should be removed) || Bluetooth || -- || No pairing via ui, but functional via terminal || pmOS || Unknown || [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Bluetooth Instructions]
|-
|USB-C Hub || [https://www.tsbohemia.cz/umax-u-connect-type-c-multiport-h7_d350000.html UMAX U-Connect Type-C Multiport H7] || USB-C || - || USB-A ports, PD, HDMI works, SD card reader not enumerating on PP with removed VCONN switches (may need VCONN) || Arch Linux || Unknown || HDMI, 3xUSB-3, USB-C PD, SD reader
|-
|USB-C Soundcard || [https://store.google.com/?srp=/product/usb_c_headphone_adapter Google Pixel USB-C to 3.5mm adapter] || USB-C || 18d1:5029 || Works, recognized as usb soundcard, but only if a cable is plugged in || pmOS || Unknown ||
|-
|-
|USB-C Hub || [https://www.anker.com/products/variant/powerexpand--7in1-usbc-pd-ethernet-hub/A83520A1 Anker PowerExpand+ 7-in-1 USB-C PD Ethernet Hub] || USB-C || -- || USB Ports and HDMI Port work, can charge while using this device (needs VCONN HW mod) || [https://wiki.mobian-project.org/doku.php?id=mods Mobian] || Unknown || HDMI, USB3, Ethernet, PD-USBC, SD Card, Micro SD Card
|-
|USB-C Hub || [https://www.dell.com/support/article/en-us/sln296829/how-to-use-and-troubleshoot-dell-docking-station-wd15?lang=en Dell WD-15 Docking station] || USB-C || 0424:2807 || USB Ports and charging works. Audio sinks and DP status changes are detected (needs VCONN HW mod and ANX firmware) || pmOS || Unknown || HDMI, VGA and DP might work after a kernel update. ANX firmware is needed for charging after VCONN mod.
|-
|USB-C Hub || [https://www.microsoft.com/en-us/mobile/accessory/hd-500/specifications Microsoft HD-500 Dock] || USB-C || -- || USB Hub, Display Out, and Power Delivery all works. (needs VCONN HW mod and ANX firmware) || [https://wiki.mobian-project.org/doku.php?id=mods Mobian] || Unknown ||
|-
|USB-C Hub || [https://support.hp.com/us-en/product/hp-elite-x3-lap-dock/12088822/document/c05320203 HP Elite x3 LapDock] || USB-C || -- || Dock display, keyboard/trackpad, and Power Delivery all works. (needs VCONN HW mod and ANX firmware) || [https://wiki.mobian-project.org/doku.php?id=mods Mobian] || Unknown || Haven't tested micro-HDMI port or the internal USB-C hub.
|-
|USB-C Hub || [https://www.kjell.com/se/produkter/dator/mac-tillbehor/plexgear-multiadapter-for-usb-c-med-7-anslutningar-p62099 Plexgear 7-port multi adapter with PD and SD-card reader] || USB-C || USB-hub: 0bda:5411 (RTS5411); Ethernet: 0bda:8153 (RTL8153); SD-card reader: 05e3:0749; Audio: 0c76:161f; 2109:0102; 0c76:161f || Everything seems to work. PD, 3x USB 2.0 ports, ethernet, HDMI, SD-card, audio. || Arch Linux || 1.2 with VCONN mod (CC switches removed) ||
|-
|}

[[Category:PinePhone]]

PinePhone v1.2b

2020-10-31T18:45:59Z

E1337: my bad, was just the link title being wrong

DRAFT:

The PinePhone v1.2b is a hardware revision of the PinePhone that started shipping in Q4 2020.

This page contains information and resources which are specific to the v1.2b revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see [[PinePhone#Hardware Revisions]].

== Schematics ==
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2b%20Released%20Schematic.pdf Hardware schematic v1.2b] (for the Manjaro Community Edition)

== Changes from v1.2a ==
* A bug was fixed, where connecting a VBUS powered device lowered the screen brightness (resistor R1318 changed to NC).

== Known issues ==
The backlight issue of v1.2 is still present, see [[PinePhone v1.2#Backlight]].

[[Category:PinePhone]]

PinePhone v1.2b

2020-10-31T18:45:17Z

E1337: this could be WRONG, but I think postmarketOS edition was 1.2a, manjaro 1.2b

DRAFT:

The PinePhone v1.2b is a hardware revision of the PinePhone that started shipping in Q4 2020.

This page contains information and resources which are specific to the v1.2b revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see [[PinePhone#Hardware Revisions]].

== Schematics ==
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2b%20Released%20Schematic.pdf Hardware schematic v1.2a] (for the PostmarketOS Community Edition)

== Changes from v1.2a ==
* A bug was fixed, where connecting a VBUS powered device lowered the screen brightness (resistor R1318 changed to NC).

== Known issues ==
The backlight issue of v1.2 is still present, see [[PinePhone v1.2#Backlight]].

[[Category:PinePhone]]

PinePhone v1.1 - Braveheart

2020-07-19T22:16:14Z

E1337: fixing bold

The PinePhone v1.1 "Braveheart" is a hardware revision of the PinePhone that shipped in January 2020.

This page contains resources which are exclusive to the 1.1 revision of the PinePhone. For other revisions, or for resources related to all PinePhone revisions, see [[PinePhone]].

== Schematic ==

[http://files.pine64.org/doc/PinePhone/PinePhone_Schematic_v1.1_20191031.pdf Hardware schematic]

== Changes from 1.0 ==

Braveheart is slightly different from the 1.0 revision of the Pinephone. These differences should not require creating different images.

# Added CPU shielding and cover plate
# Swap PC3 to FLASH_EN and PD24 to FLASH_TRIGOUT, where previously they were reversed
# Add pulldown resistor on PD24 (FLASH_TRIGOUT) so the flash LED does not light on boot
# Connect WiFi enable to VD33
# Set the EG25G's PWRKEY on by default (see resistor R1526)
# Add R630 resistor location, populate with 0K by default. Allows adjusting to different battery thermistors in case this is not possible in software.
# Add voltage shift to Pogo pins I2C-CLK, I2C-DATA, and INT. The Pogo Pin specified voltage is 3.3v while the A64's I2C is 2.8V.
# A64 LINEOUTN is disconnected from the speaker amplifier, making the speaker output single-ended instead of differential

== Known issues ==

This section lists problems known on the 1.1 revision hardware, possibly because they carried over from the 1.0 revision. Most of these were fixed in the 1.2 revision mainboard.

=== Need a way to distinguish v1.1 from v1.2 from U-Boot SPL ===

''Resolved in v1.2 by PL6 being connected directly to the modem, instead of through the level shifter, so it is pulled low at boot.''

To load the correct device tree, there needs to be some hardware feature that can distinguish the two versions. This can be as simple as an I/O pin that is pulled differently by default between v1.1 and v1.2. Reading the pin in SPL will tell us which device tree to use.

=== WiFi module cannot be disabled or reset in software ===

''Resolved in v1.2 by connecting PL2 to the WiFi module's WiFi reset pin.''

Neither the <tt>WL-REG-ON</tt> nor <tt>WL-PMU-EN</tt> signal is connected to anything, and the WiFi module's <tt>CHIP_EN</tt> pin is connected (through the killswitch) to a regulator that cannot be turned off (easily, if at all). So while the killswitch works, there's no way to disable the WiFi module in software. This will lead to excess power consumption when WiFi is turned off.

=== Magnetometer's IRQ signal is routed to the wrong pin ===

''Resolved in v1.2 by connecting the magnetometer's <tt>DRDY</tt> pin to PB1.''

It needs to go to DRDY, not to INT. The kernel driver expects the trigger events to be fired when DRDY changes, and does not even configure the interrupts to be enabled on the INT pin.

Software workaround is to disable magnetometer interrupt in the devicetree, and use a hrtimer or some other software triggering mechanism for IIO devices.

=== Speaker output could be differential ===

''Resolved in v1.2 by connecting <tt>LINEOUTP</tt> to the speaker amplifier's <tt>INP</tt> input.''

Using a differential connection to the speaker amplifier would significantly lower the noise floor of the speaker, and would allow doubling the max volume.

=== Modem AP_READY signal is not connected ===

''Resolved in v1.2 by connecting PH7 to <tt>AP_READY</tt> instead of <tt>WAKEUP_IN</tt>.''

The [https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG9x_Power_Management_Application_Note_V1.0.pdf modem's power management documentation] describes how to implement modem power saving. The modem can wake up the host using either the Ring Indicator pin (section 4.5) or USB remote wakeup (section 4.3). Either way, it suggests the <tt>AP_READY</tt> signal needs to be connected. The modem needs that signal to know when the host is asleep (and the modem needs to queue its messages and wake it up), and when the host has finished waking up (and is ready to receive the queued messages).

=== Modem RI signal routing prevents wakeup ===

''Resolved in v1.2 by connecting <tt>RI</tt> to PL6.''

The EG25G's Ring Indicator (RI) pin is currently routed to GPIO pin PB2. The A64 needs to receive interrupts via this pin while suspended, so the modem can wake up the A64 (for incoming calls and text messages). The only GPIO bank that can receive interrupts while the A64 is suspended is Port L (on <tt>R_PIO</tt>).

'''Note''': Port L is powered by VCC-PL, and runs at 1v8, so it should ''not'' have a level shift to DCDC1/3v3 between the AP and the modem, like DTR currently has. The way DTR is currently connected is a bug.

=== Excess power usage while driving VBUS ===

''Resolved in v1.2 by connecting PL9 and <tt>VBUS_CTRL</tt> on the ANX7688 to <tt>N_VBUSEN</tt> on the PMIC.''

The <tt>N_VBUSEN/DRIVEVBUS</tt> input on the AXP803 PMIC, labeled <tt>USB-DRVVBUS</tt> on the schematic, is not connected to the USB OTG boost regulator enable input, because R1300 is marked "NC". This prevents the AXP803 from automatically detecting when the USB port is being powered from the battery. Thus, the PMIC continues to draw power from the USB port, and this doubles the drain on the battery (since the whole phone is being powered by the USB OTG boost regulator). This could be fixed by populating R1300.

The ANX7688's VBUS_CTRL pin should also be connected to the DRVVBUS signal to perform role switching in hardware without needing OS interaction. In that case PD6 becomes an input. Otherwise, we would need to hook up the VBUS status change interrupt from the ANX7688 to control the USB PHY driver.

=== ANX7688 power supply situation is problematic ===

''Resolved in v1.2 by powering always-on 3v3 from DCDC1, video-related 3v3 from DLDO1, 1v8 from GPIO-LDO1, and 1v0 controlled by PD11.''

ANX7688 has four power inputs: 3v3, 1v8, 1v0, and HDMI_VT (which is also 3v3).
* The main 3v3 input, to AVDD33, should always be on according to the datasheet. For this reason, it should be connected to an always-on regulator, such as DCDC1, so DLDO1 can be turned off when the screen is off. It has extremely low power consumption.
* HDMI_VT is only needed during video transmission, and should remain connected to DLDO1.
* The only other 3v3 consumer is the VCONN_EN pull-ups. These could be pulled to GPIO1-LDO (1.8V) instead; the pins are open drain.
* The DVDD18 input should also always be on according to the datasheet. It has extremely low power consumption. I recommend connecting it and the PL11 pull-up to VCC-PL, so GPIO1-LDO can be turned off.
* The remaining 1v8 inputs only need to be enabled when a USB cable is connected (supply or OTG). They are connected to their own regulator (GPIO1-LDO), so that is fine. (Note that the next issue suggests removing the pull-ups for POWER_EN and RESET_N.)
* The 1v0 input is only needed when a USB cable is connected (supply or OTG). It is currently controlled by DLDO1, but I think controlling it with GPIO1-LDO would be an improvement. That way DLDO1 only needs to be enabled when transmitting video, not always when a cable is connected.

=== Modem PWR_KEY signal resistor population ===

''Resolved in v1.2 by separating the modem <tt>PWRKEY</tt> (PB3) and <tt>STATUS</tt> (PH9) signals.''

On the dev phone (1.0) this signal was connected to PB3. This allows for turning on/off the modem via GPIO from a kernel driver. If proper power down is to be implemented in the kernel for the modem, to allow safe shutdown of the modem before turning off the 4g-pwr-bat, kernel has to be able to signal to the modem to shut down and wait 30s. This is not possible on braveheart. Without this signal, kernel can't do anything to shut down the modem, and would have to rely on userspace to properly manage the modem power up/down sequence. Relying on userspace risks users shutting down the modem without proper wait time of 30s, risking modem damage (flash data corruption).

It would be nice to also have access to the STATUS signal from the modem, so that the driver can detect whether the modem is on or off (userspace might have turned modem off already via AT commands). Given that PWR_KEY pulse will either turn the modem on or off, based on the current status, it's necessary to know the current status before sending the pulse.

There's a STATUS signal routed to PWR_KEY on BraveHeart, that keeps the PWRKEY deasserted when the modem is on and it's not possible to pull it up from PB3, even if R1516 would be optionally mounted.

So after powerup you can't change PWR_KEY signal anymore from PB3 even if R1516 is mounted, and it's not possible to turn off the modem via PB3.

=== Modem has access to sensors on I2C1 ===

''Resolved in v1.2 by disconnecting the modem's I2C port.''

The modem is a master on the I2C1 bus. A malicious firmware on the modem would be able to read the phone's gravity/light/proximity sensors and prevent the main Linux OS from reading them. The [https://www.quectel.com/UploadImage/Downlad/Quectel_WCDMA&LTE_Audio_Design_Note_V1.1.pdf modem's audio design note] describes the <tt>AT+QIIC</tt> command which can be used to read and write registers on I2C devices.

According to the modem documentation, its I2C interface is only used for direct connection to a standalone audio codec. On the PinePhone, since the modem's audio is routed through the A64 SoC, the modem's I2C interface has no legitimate use.

The modem's I2C interface should be left floating. U1503 pins A1, A2, B1, and B2 can be disconnected, and R1527/R1528 can be removed.

=== Allow access the modem debug UART ===

''Not resolved in v1.2 -- would have required moving several other GPIOs.''

Instead of the modem's I2C pins, which aren't very useful (see above), it would be great to have access to the modem's debug UART, for debugging/updating the modem. This could be on UART3 (PD0-PD1, no flow control), while the main modem UART is on UART4 (PD2-PD5, with flow control).

=== Modem UART flow control is broken ===

''Not resolved in v1.2 -- assumption is that USB will be used for high-bandwidth modem I/O.''

BB-TX and BB-RX are connected to UART3 (PD0/PD1). BB-RTS and BB-CTS are connected to UART4 (PD4/PD5). To use hardware flow control, TX/RX would need to be connected to UART4, swapping PD0/PD1 with the motor control and rear camera reset GPIOs at PD2/PD3. This would need a device tree change.

Hardware flow control can be disabled with the <tt>AT+IFC</tt> command, and USB can also be used for commands instead of the UART. So the impact of this problem is unclear.

=== ANX7688 power/reset control pulled the wrong way ===

''Not resolved in v1.2 -- this has minimal impact.''

Both <tt>ANX_POWER_EN</tt> and <tt>ANX_RESET_N</tt> have pull-ups when they should not. Both signals need to be pulled low by default. They only need to be brought high (turning the chip on) when a USB cable is attached; and they should only be brought high after the 1v8 and 1v0 regulators are turned on. <tt>ANX_POWER_EN</tt> needs an external pull-down. <tt>ANX_RESET_N</tt> has an internal pull-down.

=== VCONN_EN signals are possibly inverted ===

''Further investigation determined that the hardware is correct as-is in v1.1, so no change was made.''

I don't have a datasheet for the AW3512 chips, but I assume the enable input is active-high. VCONN1_EN and VCONN2_EN are open-drain. When they are open, it appears that VCONN should be enabled. But right now, when they are open, VCONN is disabled, because the AW3512 EN pin will be pulled low by the FET.

=== Cameras have the same default I2C address ===

''Resolved in software by reprogramming the one of the cameras' I2C addresses at boot.''

This makes it hard to keep both of them powered at the same time and switch quickly between them (on the per-frame basis) without having to re-initialize the sensors on each switch, which takes some time.

=== USB Power issue preventing charge and battery-less operation (one-off HW issue ?) ===

''Seems to be a one-time hardware issue, no change needed?''

I received a PinePhone that never charged when plugged on USB. Also the phone does not boot when plugged without the battery. I tried: computer, 1A charger, 2A Asus charger, 2.1A battery. On OSes: latest pmOS and Ubuntu Touch, default test software.
Apart from that (USB power issue), the phone seems to work correctly. The phone is seen has a "PinePhone" when connected with USB to a Linux computer. See https://forum.pine64.org/showthread.php?tid=9042

Investigations:
If I measure VBUS (aka DCIN in older schematics) on the USB-C daughter board connector (using multimeter, touch the leftmost pins on the bottom row, they can be reached even with the flex cable plugged), I get when flex cable unplugged: 4.7V (sometimes 2.3V but less often and not reproducibly), when flex cable plugged: 1.21V (it should be 5V!).

I did measurements using names from "PinePhone USB-C small board schematic v1.0 20190730.pdf" given to me by TL on the Telegram dev chat.
I measure C101 to be 3.3 uf instead of 4.7 uf according to schematics. I measure C104 to be 265 pf, C105 to be 0.26nf, C106 to be > 10 uf (my tool does not go above)., C107 to be: 0.18nf.

I decided to bypass OVP to try fixing my PinePhone:

<gallery mode="traditional">
File:Braveheart_VBUS_1_from_diode.jpg|A 0.3mm insulated wire takes VBUS_1 (VBUS unprotected from overvoltages) from diode. See OVP component in PDF "PinePhone USB-C small board top placement v1.0 20190730.pdf".
File:Braveheart_VBUS_1_to_VBUS_at_pogopin.jpg|At the appropriate pogopin of my Braveheart, VBUS_1 is plugged directly to VBUS to bypass OVP which is not working on my USB-C daughter board. ! Be careful that in revisions following Braveheart the pogopins usage could change ! Do not inject 5V in 3V3 bus or I2C !
File:Braveheart_bypass_OVP_U102_AW338XX.jpg|The wire passing behind the battery.
</gallery>

With this bypass, the phone is able to boot with or without the battery, and to charge the battery. As this is a hack that reduces safety I will try to have my USB-C daughter board replaced.

=== USB-C CC pins are pulled to the GND by AW3512 (VCONN switches) when VCONN is off ===

'''This issue is also present on the PinePhone 1.2 (CE) version.''' It was fixed with revision 1.2a.

This issue prevents cable plug/orientation detection and USB-PD communication. ANX always sees cable as plugged even if none is plugged. There's no SW workaround for automatic detection of cable plug or power role.

In SW this can only be worked around by manual selection of PinePhone's data and power role by the user.

HW workaround is desoldering U1305 and U1309 switches (BGA like packages). This will void the VCONN control, but it will release the CC pins for their proper connection detection and negotiation roles. I confirmed that desoldering fixes the issue. (Howto: https://megous.com/dl/tmp/pp-usbc-fix.jpg)

HW fix is to replace AW3512 with a variant of the chip that preserves the EN signal polarity and that doesn't have the "quick discharge function" that ties the output to the GND via a 75 Ohm resistor when the switch is OFF. mozzwald used NCP334FCT2G as a replacement.

=== Pogo Pins supply 5v0, not 3v3 ===

''No hardware change suggested, to maintain accessory compatibility.''

This is possibly just a documentation issue. [https://wiki.pine64.org/index.php/PinePhone#Pogo_Pins The wiki claims] they provide a "3.3v power source", and on this page, "The Pogo Pin specified voltage is 3.3v". But according to the schematic, they are connected to <tt>USB-5V</tt>, the output of the 5V boost regulator.

PinePhone v1.1 - Braveheart

2020-07-19T22:15:39Z

E1337: moving remark that usb-cc issue is also present in 1.2 ce to the top

The PinePhone v1.1 "Braveheart" is a hardware revision of the PinePhone that shipped in January 2020.

This page contains resources which are exclusive to the 1.1 revision of the PinePhone. For other revisions, or for resources related to all PinePhone revisions, see [[PinePhone]].

== Schematic ==

[http://files.pine64.org/doc/PinePhone/PinePhone_Schematic_v1.1_20191031.pdf Hardware schematic]

== Changes from 1.0 ==

Braveheart is slightly different from the 1.0 revision of the Pinephone. These differences should not require creating different images.

# Added CPU shielding and cover plate
# Swap PC3 to FLASH_EN and PD24 to FLASH_TRIGOUT, where previously they were reversed
# Add pulldown resistor on PD24 (FLASH_TRIGOUT) so the flash LED does not light on boot
# Connect WiFi enable to VD33
# Set the EG25G's PWRKEY on by default (see resistor R1526)
# Add R630 resistor location, populate with 0K by default. Allows adjusting to different battery thermistors in case this is not possible in software.
# Add voltage shift to Pogo pins I2C-CLK, I2C-DATA, and INT. The Pogo Pin specified voltage is 3.3v while the A64's I2C is 2.8V.
# A64 LINEOUTN is disconnected from the speaker amplifier, making the speaker output single-ended instead of differential

== Known issues ==

This section lists problems known on the 1.1 revision hardware, possibly because they carried over from the 1.0 revision. Most of these were fixed in the 1.2 revision mainboard.

=== Need a way to distinguish v1.1 from v1.2 from U-Boot SPL ===

''Resolved in v1.2 by PL6 being connected directly to the modem, instead of through the level shifter, so it is pulled low at boot.''

To load the correct device tree, there needs to be some hardware feature that can distinguish the two versions. This can be as simple as an I/O pin that is pulled differently by default between v1.1 and v1.2. Reading the pin in SPL will tell us which device tree to use.

=== WiFi module cannot be disabled or reset in software ===

''Resolved in v1.2 by connecting PL2 to the WiFi module's WiFi reset pin.''

Neither the <tt>WL-REG-ON</tt> nor <tt>WL-PMU-EN</tt> signal is connected to anything, and the WiFi module's <tt>CHIP_EN</tt> pin is connected (through the killswitch) to a regulator that cannot be turned off (easily, if at all). So while the killswitch works, there's no way to disable the WiFi module in software. This will lead to excess power consumption when WiFi is turned off.

=== Magnetometer's IRQ signal is routed to the wrong pin ===

''Resolved in v1.2 by connecting the magnetometer's <tt>DRDY</tt> pin to PB1.''

It needs to go to DRDY, not to INT. The kernel driver expects the trigger events to be fired when DRDY changes, and does not even configure the interrupts to be enabled on the INT pin.

Software workaround is to disable magnetometer interrupt in the devicetree, and use a hrtimer or some other software triggering mechanism for IIO devices.

=== Speaker output could be differential ===

''Resolved in v1.2 by connecting <tt>LINEOUTP</tt> to the speaker amplifier's <tt>INP</tt> input.''

Using a differential connection to the speaker amplifier would significantly lower the noise floor of the speaker, and would allow doubling the max volume.

=== Modem AP_READY signal is not connected ===

''Resolved in v1.2 by connecting PH7 to <tt>AP_READY</tt> instead of <tt>WAKEUP_IN</tt>.''

The [https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG9x_Power_Management_Application_Note_V1.0.pdf modem's power management documentation] describes how to implement modem power saving. The modem can wake up the host using either the Ring Indicator pin (section 4.5) or USB remote wakeup (section 4.3). Either way, it suggests the <tt>AP_READY</tt> signal needs to be connected. The modem needs that signal to know when the host is asleep (and the modem needs to queue its messages and wake it up), and when the host has finished waking up (and is ready to receive the queued messages).

=== Modem RI signal routing prevents wakeup ===

''Resolved in v1.2 by connecting <tt>RI</tt> to PL6.''

The EG25G's Ring Indicator (RI) pin is currently routed to GPIO pin PB2. The A64 needs to receive interrupts via this pin while suspended, so the modem can wake up the A64 (for incoming calls and text messages). The only GPIO bank that can receive interrupts while the A64 is suspended is Port L (on <tt>R_PIO</tt>).

'''Note''': Port L is powered by VCC-PL, and runs at 1v8, so it should ''not'' have a level shift to DCDC1/3v3 between the AP and the modem, like DTR currently has. The way DTR is currently connected is a bug.

=== Excess power usage while driving VBUS ===

''Resolved in v1.2 by connecting PL9 and <tt>VBUS_CTRL</tt> on the ANX7688 to <tt>N_VBUSEN</tt> on the PMIC.''

The <tt>N_VBUSEN/DRIVEVBUS</tt> input on the AXP803 PMIC, labeled <tt>USB-DRVVBUS</tt> on the schematic, is not connected to the USB OTG boost regulator enable input, because R1300 is marked "NC". This prevents the AXP803 from automatically detecting when the USB port is being powered from the battery. Thus, the PMIC continues to draw power from the USB port, and this doubles the drain on the battery (since the whole phone is being powered by the USB OTG boost regulator). This could be fixed by populating R1300.

The ANX7688's VBUS_CTRL pin should also be connected to the DRVVBUS signal to perform role switching in hardware without needing OS interaction. In that case PD6 becomes an input. Otherwise, we would need to hook up the VBUS status change interrupt from the ANX7688 to control the USB PHY driver.

=== ANX7688 power supply situation is problematic ===

''Resolved in v1.2 by powering always-on 3v3 from DCDC1, video-related 3v3 from DLDO1, 1v8 from GPIO-LDO1, and 1v0 controlled by PD11.''

ANX7688 has four power inputs: 3v3, 1v8, 1v0, and HDMI_VT (which is also 3v3).
* The main 3v3 input, to AVDD33, should always be on according to the datasheet. For this reason, it should be connected to an always-on regulator, such as DCDC1, so DLDO1 can be turned off when the screen is off. It has extremely low power consumption.
* HDMI_VT is only needed during video transmission, and should remain connected to DLDO1.
* The only other 3v3 consumer is the VCONN_EN pull-ups. These could be pulled to GPIO1-LDO (1.8V) instead; the pins are open drain.
* The DVDD18 input should also always be on according to the datasheet. It has extremely low power consumption. I recommend connecting it and the PL11 pull-up to VCC-PL, so GPIO1-LDO can be turned off.
* The remaining 1v8 inputs only need to be enabled when a USB cable is connected (supply or OTG). They are connected to their own regulator (GPIO1-LDO), so that is fine. (Note that the next issue suggests removing the pull-ups for POWER_EN and RESET_N.)
* The 1v0 input is only needed when a USB cable is connected (supply or OTG). It is currently controlled by DLDO1, but I think controlling it with GPIO1-LDO would be an improvement. That way DLDO1 only needs to be enabled when transmitting video, not always when a cable is connected.

=== Modem PWR_KEY signal resistor population ===

''Resolved in v1.2 by separating the modem <tt>PWRKEY</tt> (PB3) and <tt>STATUS</tt> (PH9) signals.''

On the dev phone (1.0) this signal was connected to PB3. This allows for turning on/off the modem via GPIO from a kernel driver. If proper power down is to be implemented in the kernel for the modem, to allow safe shutdown of the modem before turning off the 4g-pwr-bat, kernel has to be able to signal to the modem to shut down and wait 30s. This is not possible on braveheart. Without this signal, kernel can't do anything to shut down the modem, and would have to rely on userspace to properly manage the modem power up/down sequence. Relying on userspace risks users shutting down the modem without proper wait time of 30s, risking modem damage (flash data corruption).

It would be nice to also have access to the STATUS signal from the modem, so that the driver can detect whether the modem is on or off (userspace might have turned modem off already via AT commands). Given that PWR_KEY pulse will either turn the modem on or off, based on the current status, it's necessary to know the current status before sending the pulse.

There's a STATUS signal routed to PWR_KEY on BraveHeart, that keeps the PWRKEY deasserted when the modem is on and it's not possible to pull it up from PB3, even if R1516 would be optionally mounted.

So after powerup you can't change PWR_KEY signal anymore from PB3 even if R1516 is mounted, and it's not possible to turn off the modem via PB3.

=== Modem has access to sensors on I2C1 ===

''Resolved in v1.2 by disconnecting the modem's I2C port.''

The modem is a master on the I2C1 bus. A malicious firmware on the modem would be able to read the phone's gravity/light/proximity sensors and prevent the main Linux OS from reading them. The [https://www.quectel.com/UploadImage/Downlad/Quectel_WCDMA&LTE_Audio_Design_Note_V1.1.pdf modem's audio design note] describes the <tt>AT+QIIC</tt> command which can be used to read and write registers on I2C devices.

According to the modem documentation, its I2C interface is only used for direct connection to a standalone audio codec. On the PinePhone, since the modem's audio is routed through the A64 SoC, the modem's I2C interface has no legitimate use.

The modem's I2C interface should be left floating. U1503 pins A1, A2, B1, and B2 can be disconnected, and R1527/R1528 can be removed.

=== Allow access the modem debug UART ===

''Not resolved in v1.2 -- would have required moving several other GPIOs.''

Instead of the modem's I2C pins, which aren't very useful (see above), it would be great to have access to the modem's debug UART, for debugging/updating the modem. This could be on UART3 (PD0-PD1, no flow control), while the main modem UART is on UART4 (PD2-PD5, with flow control).

=== Modem UART flow control is broken ===

''Not resolved in v1.2 -- assumption is that USB will be used for high-bandwidth modem I/O.''

BB-TX and BB-RX are connected to UART3 (PD0/PD1). BB-RTS and BB-CTS are connected to UART4 (PD4/PD5). To use hardware flow control, TX/RX would need to be connected to UART4, swapping PD0/PD1 with the motor control and rear camera reset GPIOs at PD2/PD3. This would need a device tree change.

Hardware flow control can be disabled with the <tt>AT+IFC</tt> command, and USB can also be used for commands instead of the UART. So the impact of this problem is unclear.

=== ANX7688 power/reset control pulled the wrong way ===

''Not resolved in v1.2 -- this has minimal impact.''

Both <tt>ANX_POWER_EN</tt> and <tt>ANX_RESET_N</tt> have pull-ups when they should not. Both signals need to be pulled low by default. They only need to be brought high (turning the chip on) when a USB cable is attached; and they should only be brought high after the 1v8 and 1v0 regulators are turned on. <tt>ANX_POWER_EN</tt> needs an external pull-down. <tt>ANX_RESET_N</tt> has an internal pull-down.

=== VCONN_EN signals are possibly inverted ===

''Further investigation determined that the hardware is correct as-is in v1.1, so no change was made.''

I don't have a datasheet for the AW3512 chips, but I assume the enable input is active-high. VCONN1_EN and VCONN2_EN are open-drain. When they are open, it appears that VCONN should be enabled. But right now, when they are open, VCONN is disabled, because the AW3512 EN pin will be pulled low by the FET.

=== Cameras have the same default I2C address ===

''Resolved in software by reprogramming the one of the cameras' I2C addresses at boot.''

This makes it hard to keep both of them powered at the same time and switch quickly between them (on the per-frame basis) without having to re-initialize the sensors on each switch, which takes some time.

=== USB Power issue preventing charge and battery-less operation (one-off HW issue ?) ===

''Seems to be a one-time hardware issue, no change needed?''

I received a PinePhone that never charged when plugged on USB. Also the phone does not boot when plugged without the battery. I tried: computer, 1A charger, 2A Asus charger, 2.1A battery. On OSes: latest pmOS and Ubuntu Touch, default test software.
Apart from that (USB power issue), the phone seems to work correctly. The phone is seen has a "PinePhone" when connected with USB to a Linux computer. See https://forum.pine64.org/showthread.php?tid=9042

Investigations:
If I measure VBUS (aka DCIN in older schematics) on the USB-C daughter board connector (using multimeter, touch the leftmost pins on the bottom row, they can be reached even with the flex cable plugged), I get when flex cable unplugged: 4.7V (sometimes 2.3V but less often and not reproducibly), when flex cable plugged: 1.21V (it should be 5V!).

I did measurements using names from "PinePhone USB-C small board schematic v1.0 20190730.pdf" given to me by TL on the Telegram dev chat.
I measure C101 to be 3.3 uf instead of 4.7 uf according to schematics. I measure C104 to be 265 pf, C105 to be 0.26nf, C106 to be > 10 uf (my tool does not go above)., C107 to be: 0.18nf.

I decided to bypass OVP to try fixing my PinePhone:

<gallery mode="traditional">
File:Braveheart_VBUS_1_from_diode.jpg|A 0.3mm insulated wire takes VBUS_1 (VBUS unprotected from overvoltages) from diode. See OVP component in PDF "PinePhone USB-C small board top placement v1.0 20190730.pdf".
File:Braveheart_VBUS_1_to_VBUS_at_pogopin.jpg|At the appropriate pogopin of my Braveheart, VBUS_1 is plugged directly to VBUS to bypass OVP which is not working on my USB-C daughter board. ! Be careful that in revisions following Braveheart the pogopins usage could change ! Do not inject 5V in 3V3 bus or I2C !
File:Braveheart_bypass_OVP_U102_AW338XX.jpg|The wire passing behind the battery.
</gallery>

With this bypass, the phone is able to boot with or without the battery, and to charge the battery. As this is a hack that reduces safety I will try to have my USB-C daughter board replaced.

=== USB-C CC pins are pulled to the GND by AW3512 (VCONN switches) when VCONN is off ===

**This issue is also present on the PinePhone 1.2 (CE) version.** It was fixed with revision 1.2a.

This issue prevents cable plug/orientation detection and USB-PD communication. ANX always sees cable as plugged even if none is plugged. There's no SW workaround for automatic detection of cable plug or power role.

In SW this can only be worked around by manual selection of PinePhone's data and power role by the user.

HW workaround is desoldering U1305 and U1309 switches (BGA like packages). This will void the VCONN control, but it will release the CC pins for their proper connection detection and negotiation roles. I confirmed that desoldering fixes the issue. (Howto: https://megous.com/dl/tmp/pp-usbc-fix.jpg)

HW fix is to replace AW3512 with a variant of the chip that preserves the EN signal polarity and that doesn't have the "quick discharge function" that ties the output to the GND via a 75 Ohm resistor when the switch is OFF. mozzwald used NCP334FCT2G as a replacement.

=== Pogo Pins supply 5v0, not 3v3 ===

''No hardware change suggested, to maintain accessory compatibility.''

This is possibly just a documentation issue. [https://wiki.pine64.org/index.php/PinePhone#Pogo_Pins The wiki claims] they provide a "3.3v power source", and on this page, "The Pogo Pin specified voltage is 3.3v". But according to the schematic, they are connected to <tt>USB-5V</tt>, the output of the 5V boost regulator.

PinePhone v1.2

2020-07-07T22:36:05Z

E1337: /* USB */

The PinePhone v1.2 is a hardware revision of the PinePhone that shipped in 2020.

This page contains information and resources which are specific to the v1.2 revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see [[PinePhone]].

== Schematic ==

[http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf Hardware schematic]

== Changes from v1.1 ==

The v1.2 mainboard revision changes the routing of several GPIOs to fix bugs and to improve power management. Therefore, it needs an updated device tree. The state of PL6 at boot can be used to distinguish between v1.1 (it can be pulled high) and v1.2 (it will remain low).

# The WiFi module's <tt>CHIP_EN</tt> input (connected to the kill switch) is now pulled down, so the WiFi will turn off reliably when the switch is off.
# PL2 is now connected to the WiFi module's reset pin, allowing the WiFi to be turned off or reset in software.
# The magnetometer's <tt>DRDY</tt> pin is now connected to PB1, allowing interrupt-driven periodic sensor readings.
# <tt>LINEOUTP</tt> is again connected to the speaker amplifier's INP input (like in v1.0), increasing the SNR of the rear speaker.
# PH7 is now connected to the modem's <tt>AP_READY</tt> input (instead of <tt>WAKEUP_IN</tt>), allowing the modem to buffer URCs (interrupts) while the phone is asleep.
# The modem's <tt>RI</tt> output and <tt>DTR</tt> input had their GPIOs swapped between PL6 and PB2, so the <tt>RI</tt> signal can be detected without powering the main pin controller.
# Both PL9 and <tt>VBUS_CTRL</tt> (from the ANX7688) are now connected to <tt>N_VBUSEN</tt> on the PMIC. This causes the PMIC to automatically stop drawing power from the USB port when supplying power to a USB-OTG peripheral. It also allows the ANX7688 to automatically control the direction of current flowing through the USB port.
# As part of the previous change, the ANX7688's reset input was moved to PD6; this pin previously controlled the USB OTG power.
# Some of the regulators supplying the ANX7688 were rearranged, to reduce power consumption when the USB port is not connected and not being used to transmit video.
# As part of the previous change, PD11 now controls the ANX7688's 1v0 digital power domain.
# The modem's <tt>STATUS</tt> output is now connected to PH9, allowing the modem on/off state to be visible in software (note: this only works while the modem is powered). Since it is no longer connected to PB3, reading <tt>STATUS</tt> no longer turns the modem on.
# The modem no longer has access to the I2C bus containing the sensors.
# <tt>HBIAS</tt> is now connected to the headphone jack.

== Quirks ==

=== Backlight ===

Backlight LED current regulation depends on gpio0-ldo voltage stability due to feedback voltage from current sensing resistor being modified via SoC's PWM pin and pullup resistor to gpio0-ldo. gpio0-ldo also powers the CTP controller and light/proximity sensor, among other things. When backlight brightness is very low and the CTP controller actively communicates on the I2C bus the backlight blinks heavily. It's not a very good idea to tie boost converter's current regulating feedback circuit to the potential source of noise, especially since the noise will have much larger effect when the backlight LED current is low. It's possible this can be mitigated if C1110 can be raised to 22-47uF range, or by changing the resistor values in the feedback circuit.

PWM duty cycle for the lowest brightness of the backlight is also not very predictable, varying from 7-20% (tested with a small sample size of 2 devices). Therefore it's not possible to come up with a single device tree brightness settings that will work for everyone, requiring per-device calibration.

On PinePhone 1.0, this was not the case, PWM signal was directly fed to the CE pin of the regulator, and lowest brightness setting seems more stable. On the other hand, the lowest achievable brightness was brighter than on 1.1+.

=== USB ===

[[PinePhone_v1.1_-_Braveheart#USB-C_CC_pins_are_pulled_to_the_GND_by_AW3512_.28VCONN_switches.29_when_VCONN_is_off|USB-C CC pin issues from BraveHeart]] are still present in the original 1.2 revision boards, since they were discovered after production of 1.2. Revision 1.2a fixes these.

PinePhone v1.2

2020-07-07T22:35:50Z

E1337: /* USB */

The PinePhone v1.2 is a hardware revision of the PinePhone that shipped in 2020.

This page contains information and resources which are specific to the v1.2 revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see [[PinePhone]].

== Schematic ==

[http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf Hardware schematic]

== Changes from v1.1 ==

The v1.2 mainboard revision changes the routing of several GPIOs to fix bugs and to improve power management. Therefore, it needs an updated device tree. The state of PL6 at boot can be used to distinguish between v1.1 (it can be pulled high) and v1.2 (it will remain low).

# The WiFi module's <tt>CHIP_EN</tt> input (connected to the kill switch) is now pulled down, so the WiFi will turn off reliably when the switch is off.
# PL2 is now connected to the WiFi module's reset pin, allowing the WiFi to be turned off or reset in software.
# The magnetometer's <tt>DRDY</tt> pin is now connected to PB1, allowing interrupt-driven periodic sensor readings.
# <tt>LINEOUTP</tt> is again connected to the speaker amplifier's INP input (like in v1.0), increasing the SNR of the rear speaker.
# PH7 is now connected to the modem's <tt>AP_READY</tt> input (instead of <tt>WAKEUP_IN</tt>), allowing the modem to buffer URCs (interrupts) while the phone is asleep.
# The modem's <tt>RI</tt> output and <tt>DTR</tt> input had their GPIOs swapped between PL6 and PB2, so the <tt>RI</tt> signal can be detected without powering the main pin controller.
# Both PL9 and <tt>VBUS_CTRL</tt> (from the ANX7688) are now connected to <tt>N_VBUSEN</tt> on the PMIC. This causes the PMIC to automatically stop drawing power from the USB port when supplying power to a USB-OTG peripheral. It also allows the ANX7688 to automatically control the direction of current flowing through the USB port.
# As part of the previous change, the ANX7688's reset input was moved to PD6; this pin previously controlled the USB OTG power.
# Some of the regulators supplying the ANX7688 were rearranged, to reduce power consumption when the USB port is not connected and not being used to transmit video.
# As part of the previous change, PD11 now controls the ANX7688's 1v0 digital power domain.
# The modem's <tt>STATUS</tt> output is now connected to PH9, allowing the modem on/off state to be visible in software (note: this only works while the modem is powered). Since it is no longer connected to PB3, reading <tt>STATUS</tt> no longer turns the modem on.
# The modem no longer has access to the I2C bus containing the sensors.
# <tt>HBIAS</tt> is now connected to the headphone jack.

== Quirks ==

=== Backlight ===

Backlight LED current regulation depends on gpio0-ldo voltage stability due to feedback voltage from current sensing resistor being modified via SoC's PWM pin and pullup resistor to gpio0-ldo. gpio0-ldo also powers the CTP controller and light/proximity sensor, among other things. When backlight brightness is very low and the CTP controller actively communicates on the I2C bus the backlight blinks heavily. It's not a very good idea to tie boost converter's current regulating feedback circuit to the potential source of noise, especially since the noise will have much larger effect when the backlight LED current is low. It's possible this can be mitigated if C1110 can be raised to 22-47uF range, or by changing the resistor values in the feedback circuit.

PWM duty cycle for the lowest brightness of the backlight is also not very predictable, varying from 7-20% (tested with a small sample size of 2 devices). Therefore it's not possible to come up with a single device tree brightness settings that will work for everyone, requiring per-device calibration.

On PinePhone 1.0, this was not the case, PWM signal was directly fed to the CE pin of the regulator, and lowest brightness setting seems more stable. On the other hand, the lowest achievable brightness was brighter than on 1.1+.

=== USB ===

[[PinePhone_v1.1_-_Braveheart#USB-C_CC_pins_are_pulled_to_the_GND_by_AW3512_.28VCONN_switches.29_when_VCONN_is_off|USB-C CC pin issues from BraveHeart]] are still present in the original 1.2 boards, since they were discovered after production of 1.2. Revision 1.2a fixes these.

PinePhone

2020-06-09T23:16:12Z

E1337: remove confusing mention of "mounted" pinephone drive, since for flashing it shouldn't be mounted

The PinePhone is a smartphone created by Pine64, capable of running mainline Linux and supported by many partner projects. The BraveHeart Edition was the first publicly-available version of the phone, though it came without a fully functional OS (factory test image) and was geared specifically towards tinkerers and hackers. Its successor is the Community Edition, which is expected to be shipped in June 2020 and will be available for at least five years.

== First time installation ==

[[File:PinePhone-3.jpg|400px|thumb|right|PinePhone is capable of running a multitude of different Linux mobile OSes]]

From the factory the battery has a sticker on it that isolates the battery from the phone. The battery '''will not''' charge until this is removed.

After unboxing remove the back panel using the notch in the corner of the back panel. Then remove the battery and peel off the clear plastic sticker below it that isolates the charging contact. Then replace the battery. See [[PinePhone#Battery|Battery]] for more information.

== Specifications ==

'''Dimensions:''' 160.5 x 76.6 x 9.2mm 
'''Weight:''' Between 180-200 grams 
'''SIM Card:''' Micro-SIM 
'''Display:'''
: '''Size:''' 5.95 inches (151mm) diagonal
: '''Type:''' HD IPS capacitive touchscreen, 16M colors
: '''Resolution:''' 1440x720, 18:9 ratio 
'''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64] 
'''RAM:''' 2GB LPDDR3 SDRAM 
'''Internal Storage:''' 16GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC 
'''Back Camera:''' Single 5MP, 1/4", LED Flash 
'''Selfie Camera:''' Single 2MP, f/2.8, 1/5" 
'''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if killswitch 6 is deactivated) 
'''Communication: [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EG25-G_LTE_Specification_V1.1_Preliminary_20180522%20(002).pdf EG25-G]'''
: '''LTE:''' B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41
: '''WCDMA:''' B1, B2, B4, B5, B6, B8, B19
: '''GSM:''' 850, 900, 1800, 1900 (MHz)
: '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot
: '''Bluetooth:''' 4.0, A2DP
: '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
'''Sensors:''' Accelerometer, gyro, proximity, ambient light, compass 
'''[[#Killswitch configuration|Killswitches]]:''' Modem, Wifi & Bluetooth, Microphone, Cameras 
'''[[#Battery|Battery]]:''' [https://wiki.pine64.org/images/0/04/PinePhone_Battery_model_QZ01-396172-2750.pdf 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

== Hardware Revisions ==

# [[Project Anakin]]
# [[Project Don't be evil|"Project Don't Be Evil" devkit]]
# [[PinePhone v1.0 - Dev|PinePhone v1.0 - Developer batch]]
# [[PinePhone v1.1 - Braveheart]]
# [[PinePhone v1.2‎]] - Community Edition

== Hardware Addons ==

=== PinePhone Hardware Accessory Compatibility ===
See [[PinePhone Hardware Accessory Compatibility]] for a list of devices working with the PinePhone (depending on their OS support)

=== USB-C Connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, and also can make use of the USB-C capability to integrate HDMI signals. Some USB-C hubs are available that offer power throughput, USB connection, HDMI port and Ethernet connection. The driver that would make this connection available is not supported at this time.

=== Pogo Pins ===

The PinePhone has 6 pogo pins on the back allowing for custom hardware extensions such as wireless charging or an IR blaster. The pogo pins provide access to an interrupt line, power input to charge the battery, 3.3 V power source (disputed: see [[PinePhone_v1.1_-_Braveheart#Pogo_Pins_supply_5v0.2C_not_3v3]]), and an I2C interface.

'''A step/stl/stp (3D model) file for the back cover is [http://files.pine64.org/doc/PinePhone/PinePhone%20Back%20Cover%20ver%200.5.stp freely available] for creating custom cases that interface with the pogo pins.'''

=== Serial console ===

[[File:Uart pinephone connection.gif|250px|thumb|left|UART serial connector for PineBook and PinePhone]]
The PinePhone has a serial port in the headphone connector, it's activated by the 6th contact on the dipswitch. If the switch is on then the headphone connector is in audio mode, if it's off then it's in UART mode. This uart serial connection can also be used for communication with other devices from the PinePhone.

The UART is 115200n8

The pinout for the serial connector on the tablet side is:

* Tip: RX
* Ring: TX
* Sleeve: GND

The serial connection is 3.3V

You can also buy the debug cable from [https://store.pine64.org PINE64 Store]
The store cable uses a 4 ring plug, as seen in the [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf PDF], but a 3 ring plug works just as well. That cable uses a CH340 chipset based serial to USB converter, but any 3.3v serial connection can be used.

== Killswitch configuration ==

[[File:PinePhone switches.jpeg|400px|thumb|right|Photo of BraveHeart switches from OSAKANA TARO on Twitter]]

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.

# Modem: On enables 2G/3G/4G communication and GNSS hardware, off disables.
# WiFi/BT: On enables Wi-Fi and Bluetooth communication hardware, off disables.
# Microphone: On enables audio input from on-board microphones (not 3.5mm jack), off disables.
# Rear camera: On enables the rear camera, off disables.
# Front camera: On enables the front camera, off disables.
# Headphone: On enables audio input and output via the 3.5mm audio jack, off switches the jack to hardware UART mode.

== Battery ==

The [https://wiki.pine64.org/images/0/04/PinePhone_Battery_model_QZ01-396172-2750.pdf supplied battery] is [https://forum.pine64.org/showthread.php?tid=8120&pid=53307#pid53307 meant to be] compatible with Samsung part number EB-BJ700BBC / BBE / CBE from the 2015 J7 phone. There is [https://forum.pine64.org/showthread.php?tid=8563&pid=55053#pid55053 a report] that the EB-BJ700CBE isn't quite the same size, causing the back not to fit properly.

The battery terminals, in order from nearest the edge to nearest the middle, are:

# +ve
# thermistor
# -ve
# not connected

The battery includes a protection circuit that isolates it in a number of fault conditions, including if it is discharged too far. The fully discharged battery [https://forum.pine64.org/showthread.php?tid=8563&pid=55377#pid55377 can be recharged] by connecting the phone to a charger. Once it has charged sufficiently you will be able to boot the phone.

If your battery is hard to remove from the phone, try loosening the screws around it. Possibly cutting up a piece of plastic and sliding it under the battery as a pull tab can work too.

{{Note|The BraveHeart Edition ships with a plastic sticker between the battery and the phone. You need to open the back cover (gently), then remove the battery and finally remove the sticker. This is to protect the device from turning on during shipping.}}

[[File:PinePhone battery1.png|600px|thumb|centre|Photo of Brave Heart case from OSAKANA TARO on Twitter]]
[[File:PinePhone battery3.jpeg|600px|thumb|centre|Photo of Brave Heart battery sticker from OSAKANA TARO on Twitter]]

{{Hint|The EG25 modem and RTL8723CS Wifi/bluetooth do not work without battery power, even if you are supplying enough power to the PinePhone with USB-C.}}

There has been [https://forum.pine64.org/showthread.php?tid=8960 a report on the forum] that this sticker can bend the pins that make connection between the battery and the phone: please check your setup carefully after removing the sticker.

== Modem and Carrier Support ==

{{Hint|There is a document about using the modem from January 18th 2020 by user ''megi'' [https://megous.com/dl/tmp/modem.txt here]. The script at the end to disable the modem before power off is pretty essential to avoid corrupting your modem's flash memory.}}

To check if the PinePhone is supported on your carrier:

Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed under the [[#Specifications|specifications]] section).

It is likely that there will be a few frequencies that your carrier uses which are not supported by the PinePhone. Not all of the carrier's frequencies need to be supported by the PinePhone for it to work - as long as ''most'' of them are supported, you will still get good coverage.

=== Voice Mail ===

Some phone operating systems may not have support for accessing your voicemail by holding down the 1 key. If you are in Canada and using rogers or a rogers associated carrier (such as Chatr), you can access your voice mail by calling an external number, see: https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers

In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/

=== APN settings ===

For tested APN settings and how to apply them see [[PinePhone APN Settings]].

== Operating Systems ==

The PinePhone will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distribution (because the PinePhone uses the mainline kernel), there are a few that are designed specifically for mobile use on devices like the PinePhone

The [[PinePhone Software Releases]] page has a complete list of currently supported phone-optimized Operating System images that work with the PinePhone as well as other related software information. As soon as more patches got mainlined and distributions ship with the updated kernel, they will also be able to run unmodified on the device.

=== Installation instructions ===

For instructions how to install the operating systems on the eMMC or SD card see [[PinePhone Installation Instructions]].

=== Flashing eMMC using Jumpdrive ===

[[File:jumpdrive.jpg|400px|thumb|right|Jumpdrive running on the PinePhone]]
The internal eMMC flash storage can be flashed using the Jumpdrive utility by Danct12 and Martijn from postmarketOS.
This utility boots from micro SD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.
The process of flashing and OS to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a SD card. You can use the 'DD' command or a utility such as Etcher or Gnome Disks, etc.

Latest Jumpdrive can be found [https://github.com/dreemurrs-embedded/Jumpdrive/releases/ here].

==== Detailed Usage Instructions ====

# Download the Jumpdrive image
# Flash the Jumpdrive image to a micro SD card
# Boot the PinePhone from the Jumpdrive micro SD card
# Connect the PinePhone to your computer using USB-A -> USB-C cable
# Flash the exposed PinePhone drive (e.g. /dev/mm..., check for the right device in dmesg, GNOME disks, or similar, and make sure it's unmounted) with your chosen OS image
# Once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card
# The process is now finished, and you can boot from eMMC

Jumpdrive also acts as a rescue image in case if you messed up your installation. To do so, you can telnet to '''172.16.42.1''', mount rootfs and fix it!

==== Resize file system ====

If you flash a 4GB image distribution (such as phosh+debian) to your eMMC, your eMMC will only have a 3.7G partition on it. To use the entire 14.7G on the eMMC, run the following commands:

# sudo cfdisk /dev/sdX
# Change to [Resize] in the ncurses program, resize the 3.7G partition to 14.7G, and [Write]
# sudo resize2fs /dev/sdXY

Replace X with your drive's name. Replace Y with the partition you resized in cfdisk.

==== Feedback ====

If you've found an issue or want to improve the tool consider these sites:

* Issues: https://github.com/dreemurrs-embedded/Jumpdrive/issues
* Pull Requests: https://github.com/dreemurrs-embedded/Jumpdrive/pulls

== Frequently Asked Questions ==

For a list of frequently asked questions (including information regarding the shipping), see [[PinePhone FAQ]].

== PinePhone Board Information, Schematics and Certifications ==
* PinePhone Main Board Schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2]
** [[PinePhone_v1.2|PinePhone Schematic ver 1.2 change list]]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard Schematic ver 1.1]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component top placement drawing ver 1.1]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1]
* PinePhone USB-C Small Board Schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20schematic%20v1.0%2020190730.pdf PinePhone USB-C small board Schematic ver 1.0]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20top%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component top placement drawing ver 1.0]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20bottom%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component bottom placement drawing ver 1.0]
* PinePhone Certifications:
** [http://files.pine64.org/doc/cert/PinePhone%20FCC%20SDOC%20Certificate-S19112602605001.pdf PinePhone FCC Certificate]
** [https://fcc.report/FCC-ID/2AWAG-PINEPHONE RF Exposure SAR Information from FCC ID site]
** [http://files.pine64.org/doc/cert/PinePhone%20CE%20RED%20Certificate-S19112602602.pdf PinPhone CE RED Certificate]
** [http://files.pine64.org/doc/cert/PinePhone%20ROHS%20Report.pdf PinePhone ROHS Report]

== Datasheets for Components and Peripherals ==
* Allwinner A64 SoC information:
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]
** [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
** [http://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]
* X-Powers AXP803 PMU (Power Management Unit) information:
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]
* LPDDR3 (178 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 Datasheet]
* eMMC information:
** [http://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf Kimtigo eMMC Datasheet]
* CMOS Camera module information:
** [http://files.pine64.org/doc/datasheet/pinephone/QZ01-rear-2019-0717(HW)%20Model.pdf PinePhone 5M Pixel Real CMOS Image Sensor Module]
** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module Datasheet]
** [http://files.pine64.org/doc/datasheet/pinephone/QZ01-front-2019-0717(HW)%20Model.pdf PinePhone 2M Pixel Front CMOS Image Sensor Module]
** [http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module Datasheet]
* LCD Touch Screen Panel information:
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20LCD-QZ01.pdf 5.99" 1440x720 LCD IPS Panel Specification]
** [http://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703 LCD Controller Datasheet]

** [http://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf GOODiX GT917S Capacitive Touch Controller Datasheet]
* Lithium Battery information:
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf PinePhone Lithium Battery Specification]
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20ZCV%20Curve%20Chart.xlsx PinePhone Lithium Battery ZCV Curve Chart]
* Wifi/BT module information:

* LTE module information:
** [http://files.pine64.org/doc/datasheet/pinephone/Quectel_EG25-G_LTE_Specification_V1.0.pdf Quectel EG25-G LTE Module Specification]
** [[Media:Quectel EC25EC21 AT Commands Manual V1.2.pdf|EC25&EC21 AT Commands Manual]]
* Sensors:
** [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetomater Datasheet]
** [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS Datasheet]
** [http://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]
* Digital Video to USB-C Bridge:
** [https://www.analogix.com/en/system/files/AA-002281-PB-6-ANX7688_Product_Brief.pdf ANX7688 Product Brief]
* Case information:
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Exploded%20Diagram%20ver%201.0.pdf PinePhone Case Exploded Diagram]
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Back%20Cover.stp PinePhone Back Battery Cover 3D file]

== Developer works ==
=== Megous ===

* [https://xnux.eu/howtos/pine64-pinephone-getting-started.html Getting start with PinePhone Hardware]
* [https://xnux.eu/devices/pine64-pinephone.html#toc-pine64-pinephone State of development progress]
* [https://xnux.eu/news.html PinePhone Technical News and Update, also applies to other Allwinner devices including PINE A64 SBC]

== External links ==
* [https://store.pine64.org/?post_type=product Pine64 shop]

PinePhone v1.2

2020-06-07T15:19:19Z

E1337: /* USB */

The PinePhone v1.2 is a hardware revision of the PinePhone that shipped in 2020.

This page contains information and resources which are specific to the v1.2 revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see [[PinePhone]].

== Schematic ==

[http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf Hardware schematic]

== Changes from v1.1 ==

The v1.2 mainboard revision changes the routing of several GPIOs to fix bugs and to improve power management. Therefore, it needs an updated device tree. The state of PL6 at boot can be used to distinguish between v1.1 (it can be pulled high) and v1.2 (it will remain low).

# The WiFi module's <tt>CHIP_EN</tt> input (connected to the kill switch) is now pulled down, so the WiFi will turn off reliably when the switch is off.
# PL2 is now connected to the WiFi module's reset pin, allowing the WiFi to be turned off or reset in software.
# The magnetometer's <tt>DRDY</tt> pin is now connected to PB1, allowing interrupt-driven periodic sensor readings.
# <tt>LINEOUTP</tt> is again connected to the speaker amplifier's INP input (like in v1.0), increasing the SNR of the rear speaker.
# PH7 is now connected to the modem's <tt>AP_READY</tt> input (instead of <tt>WAKEUP_IN</tt>), allowing the modem to buffer URCs (interrupts) while the phone is asleep.
# The modem's <tt>RI</tt> output and <tt>DTR</tt> input had their GPIOs swapped between PL6 and PB2, so the <tt>RI</tt> signal can be detected without powering the main pin controller.
# Both PL9 and <tt>VBUS_CTRL</tt> (from the ANX7688) are now connected to <tt>N_VBUSEN</tt> on the PMIC. This causes the PMIC to automatically stop drawing power from the USB port when supplying power to a USB-OTG peripheral. It also allows the ANX7688 to automatically control the direction of current flowing through the USB port.
# As part of the previous change, the ANX7688's reset input was moved to PD6; this pin previously controlled the USB OTG power.
# Some of the regulators supplying the ANX7688 were rearranged, to reduce power consumption when the USB port is not connected and not being used to transmit video.
# As part of the previous change, PD11 now controls the ANX7688's 1v0 digital power domain.
# The modem's <tt>STATUS</tt> output is now connected to PH9, allowing the modem on/off state to be visible in software (note: this only works while the modem is powered). Since it is no longer connected to PB3, reading <tt>STATUS</tt> no longer turns the modem on.
# The modem no longer has access to the I2C bus containing the sensors.
# <tt>HBIAS</tt> is now connected to the headphone jack.

== Quirks ==

=== Backlight ===

Backlight LED current regulation depends on gpio0-ldo voltage stability due to feedback voltage from current sensing resistor being modified via SoC's PWM pin and pullup resistor to gpio0-ldo. gpio0-ldo also powers the CTP controller and light/proximity sensor, among other things. When backlight brightness is very low and the CTP controller actively communicates on the I2C bus the backlight blinks heavily. It's not a very good idea to tie boost converter's current regulating feedback circuit to the potential source of noise, especially since the noise will have much larger effect when the backlight LED current is low. It's possible this can be mitigated if C1110 can be raised to 22-47uF range, or by changing the resistor values in the feedback circuit.

PWM duty cycle for the lowest brightness of the backlight is also not very predictable, varying from 7-20% (tested with a small sample size of 2 devices). Therefore it's not possible to come up with a single device tree brightness settings that will work for everyone, requiring per-device calibration.

On PinePhone 1.0, this was not the case, PWM signal was directly fed to the CE pin of the regulator, and lowest brightness setting seems more stable. On the other hand, the lowest achievable brightness was brighter than on 1.1+.

=== USB ===

[[PinePhone_v1.1_-_Braveheart#USB-C_CC_pins_are_pulled_to_the_GND_by_AW3512_.28VCONN_switches.29_when_VCONN_is_off|USB-C CC pin issues from BraveHeart]] are still present, since they were discovered after production of 1.2.

PinePhone v1.2

2020-06-07T15:18:06Z

E1337: Adding in USB CC note referencing to the BraveHeart page with the details

The PinePhone v1.2 is a hardware revision of the PinePhone that shipped in 2020.

This page contains information and resources which are specific to the v1.2 revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see [[PinePhone]].

== Schematic ==

[http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf Hardware schematic]

== Changes from v1.1 ==

The v1.2 mainboard revision changes the routing of several GPIOs to fix bugs and to improve power management. Therefore, it needs an updated device tree. The state of PL6 at boot can be used to distinguish between v1.1 (it can be pulled high) and v1.2 (it will remain low).

# The WiFi module's <tt>CHIP_EN</tt> input (connected to the kill switch) is now pulled down, so the WiFi will turn off reliably when the switch is off.
# PL2 is now connected to the WiFi module's reset pin, allowing the WiFi to be turned off or reset in software.
# The magnetometer's <tt>DRDY</tt> pin is now connected to PB1, allowing interrupt-driven periodic sensor readings.
# <tt>LINEOUTP</tt> is again connected to the speaker amplifier's INP input (like in v1.0), increasing the SNR of the rear speaker.
# PH7 is now connected to the modem's <tt>AP_READY</tt> input (instead of <tt>WAKEUP_IN</tt>), allowing the modem to buffer URCs (interrupts) while the phone is asleep.
# The modem's <tt>RI</tt> output and <tt>DTR</tt> input had their GPIOs swapped between PL6 and PB2, so the <tt>RI</tt> signal can be detected without powering the main pin controller.
# Both PL9 and <tt>VBUS_CTRL</tt> (from the ANX7688) are now connected to <tt>N_VBUSEN</tt> on the PMIC. This causes the PMIC to automatically stop drawing power from the USB port when supplying power to a USB-OTG peripheral. It also allows the ANX7688 to automatically control the direction of current flowing through the USB port.
# As part of the previous change, the ANX7688's reset input was moved to PD6; this pin previously controlled the USB OTG power.
# Some of the regulators supplying the ANX7688 were rearranged, to reduce power consumption when the USB port is not connected and not being used to transmit video.
# As part of the previous change, PD11 now controls the ANX7688's 1v0 digital power domain.
# The modem's <tt>STATUS</tt> output is now connected to PH9, allowing the modem on/off state to be visible in software (note: this only works while the modem is powered). Since it is no longer connected to PB3, reading <tt>STATUS</tt> no longer turns the modem on.
# The modem no longer has access to the I2C bus containing the sensors.
# <tt>HBIAS</tt> is now connected to the headphone jack.

== Quirks ==

=== Backlight ===

Backlight LED current regulation depends on gpio0-ldo voltage stability due to feedback voltage from current sensing resistor being modified via SoC's PWM pin and pullup resistor to gpio0-ldo. gpio0-ldo also powers the CTP controller and light/proximity sensor, among other things. When backlight brightness is very low and the CTP controller actively communicates on the I2C bus the backlight blinks heavily. It's not a very good idea to tie boost converter's current regulating feedback circuit to the potential source of noise, especially since the noise will have much larger effect when the backlight LED current is low. It's possible this can be mitigated if C1110 can be raised to 22-47uF range, or by changing the resistor values in the feedback circuit.

PWM duty cycle for the lowest brightness of the backlight is also not very predictable, varying from 7-20% (tested with a small sample size of 2 devices). Therefore it's not possible to come up with a single device tree brightness settings that will work for everyone, requiring per-device calibration.

On PinePhone 1.0, this was not the case, PWM signal was directly fed to the CE pin of the regulator, and lowest brightness setting seems more stable. On the other hand, the lowest achievable brightness was brighter than on 1.1+.

=== USB ===

[[PinePhone_v1.1_-_Braveheart#USB-C_CC_pins_are_pulled_to_the_GND_by_AW3512_.28VCONN_switches.29_when_VCONN_is_off|USB CC issues from BraveHeart]] are likely still present, since they were discovered after production of 1.2.

PinePhone Software Releases

2020-05-22T08:17:22Z

E1337: /* Other Resources */

This page contains a list of all available releases for the PinePhone as well as links to further resources.

See [[PinePhone Installation Instructions]] on how to install the operation systems.

Note: Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.

= Software Releases =
This is a list of OSes that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used, if possible required patches are included.

== postmarketOS ==
[[File:PostmarketOS-logo.png|100px]]

postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and Phosh.

* ''' Download location '''
Rather than downloading a demo image, postmarketOS [https://wiki.postmarketos.org/wiki/Installation_guide recommends the use of their script], pmbootstrap, that can tailor build your SD card for you.

Note: pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC].

Demo images can be found [http://images.postmarketos.org/pinephone/ here].

* ''' username/password '''
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own username and password (the Phosh lock screen requires your password, but only presents a numeric keyboard, so you should use only numbers in your password).

* ''' What works, what does not work '''
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]

If you install Firefox browser (or are using a demo image that already has it installed) then [https://wiki.postmarketos.org/wiki/Firefox these hints] in the pmOS wiki are recommended.

* ''' How to contribute and report defects '''
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker] for PinePhone support. See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

== Ubuntu Touch by UBports ==
[[File:Ubports-logo.png|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community. Installation instructions can be found on [https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.

* ''' Download location '''
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

* ''' username/password '''
Set up during boot

* ''' What works, what does not work '''
Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].

* ''' How to contribute and report defects '''
See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page]. See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

== Mobian ==
[[File:Debian-logo.png]]

An unofficial Debian build for ARM64 running with the Phosh user interface (developed by Purism, Phosh uses Wayland instead of Xorg). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot). Current version is Debian Bullseye.

* ''' Download location '''
[http://images.mobian-project.org/ Mobian downloadable images]

Don't forget to extract the image before installing:
$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://gitlab.com/mobian1/wiki/-/wikis/Install project page] for specific installation instructions.

* ''' username/password '''
mobian/1234

* ''' What works, what does not work '''

See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.

Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

* ''' How to contribute and report defects '''
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker]. As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Mobian issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask. Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

* ''' Notes '''
See [[Mobian for PinePhone]] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== SailfishOS ==


Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.

* ''' Download location '''
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).
* ''' username/password '''

Set PIN on initialization.

* ''' What works, what does not work '''
May 4th 2020: The SFOS image is now the latest 3.3.0.16 release. This has resolved many problems (for example MTP file transfer now works) but there are several glitches, the most serious being total freeze requiring reboot. Random hissing noise for about 10 seconds. This release of SF has Nextcloud integration.

May 9th 2020: Voice calls now work in pipeline, arriving in builds within days. If you have a Jolla registration a minor bug means you have to submit the request twice. WiFi is intermittent. The battery indicator previously only showed level at boot, now improved but far from reliable.

If you're not familiar with SFOS pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. The Storeman app for openrepos is now preinstalled, and also Webcat browser as the built in browser is not working at the moment.

* ''' How to contribute and report defects '''

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues SailfishOS wiki] for links to their forum as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS SailfishOS wiki] for options to contribute

* ''' Notes '''
OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like crust or changes of partition layout are added then you need to reflash.

== PureOS ==
[[File:Pureos.png]]

PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.

* ''' Download location '''
This is an unofficial/unsupported PinePhone port by ''mozzwald'' and maintained by clover that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here].

* ''' source code '''
If you want to report a bug or look at what goes into the PinePhone build of PureOS, visit the Git [http://pureos.ironrobin.net/git/clover/pinephone/ repository].

* ''' username/password '''
purism/123456

* ''' Build instructions '''
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].

== Fedora ==
[[File:Fedora-logo.png|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum].

* ''' Download location '''
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]

* ''' username/password '''
pine/1111

* ''' What works, what does not work '''
WiFi, Bluetooth, SMS, Data, Calls all work! There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution.

* ''' How to contribute and report defects '''
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker]. Be sure to include logs if applicable! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github].

== Arch Linux ARM ==
[[File:Archlinux-logo.png|100px]]

An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.

* ''' Download location '''
https://github.com/dreemurrs-embedded/Pine64-Arch/releases

* ''' username/password '''
alarm/alarm

* ''' What works, what does not work '''
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.

To access the device, ssh to 172.16.42.1 with the credentials above.

* ''' How to contribute and report defects '''
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub].

== Manjaro ARM ==
[[File:Manjaro-logo.svg|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.

* ''' Download location '''
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro forum announcement of Alpha5 version]

* ''' username/password '''
** manjaro/1234
** root/root

* ''' What works, what does not work '''
See Manjaro's [https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 announcement]. In particular, phone calls do not yet work from the Phone application.

* ''' How to contribute and report defects '''

See the end of the [https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 announcement].

== Maemo Leste ==


[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions].

* ''' Download location '''
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

* ''' username/password '''
root/toor

You may use "sudo" directly.

* ''' What works, what does not work '''
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).

* ''' How to contribute and report defects '''
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]. Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available.

== Nemo Mobile ==


Nemo Mobile is the open source build of Sailfish OS, see the new website nemomobile.net.

You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to SD card/emmc on the PinePhone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).

* ''' Download location '''
Download location is [https://github.com/neochapay/nemo-device-dont_be_evil/ here on GitHub]. The latest version is not an image file and therefore not for beginners!

Alternative easy installation method: install Sailfish on your PP first (follow instructions on this page under Sailfish). Enable developer mode.
In the terminal run as root (devel-su):

ssu ar nemo-devel-ux http://repo.merproject.org/obs/home:/neochapay:/nemo-ux/sailfish_latest_armv7hl/

then
pkcon refresh

then install the nemo-specific Glacier packages:

pkcon install lipstick-glacier-home-qt5

If necessary, reboot.

* ''' username/password '''

* ''' What works, what does not work '''
Scroll down the page [https://github.com/neochapay/nemo-device-dont_be_evil/ here].

* ''' How to contribute and report defects '''
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's Github page]

== KDE Neon ==


Based on KDE Neon for the desktop, comes with Plasma Mobile.

* ''' Download location '''
Plasma mobile images can be found [https://images.plasma-mobile.org/pinephone/ here].

* ''' username/password '''
phablet/1234

* ''' What works, what does not work '''

* ''' How to contribute and report defects '''

== NixOS ==


''NixOS support is handled through the Mobile NixOS project.''

* [https://mobile.nixos.org/ Project home page]
* [https://github.com/NixOS/mobile-nixos Source code repository]

There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].

* ''' What works, what does not work '''

This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.

<cite>
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.
</cite>

* ''' How to contribute and report defects '''
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a PinePhone when reporting issues. Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== LuneOS ==


Based on WebOS by LG, comes with Luna Next desktop environment.

* ''' Download location '''
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage.

* ''' username/password '''

* ''' What works, what does not work '''

* ''' How to contribute and report defects '''

= Factory Test OS =
On the BraveHeart model there was a pmOS based basic factory test OS pre-installed on the eMMC. Martijn Braam from pmOS has improved the functionality of the image considerably.

Since the 20200501 version it is able to test all the hardware. It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image. The downloadable image just does the hardware tests.

Do not flash eMMC to test your device, just copy it to mSD and test from there. New versions are distributed as part of the pmOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one that is marked pine-pinephone-YYYYMMDD-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

= Installing other ARM64 distributions =
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distribution to the PinePhone.

'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.

If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).

# Create a boot (from 4 MB to about 252 MB) and root (from 252 MB to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).
# Edit /etc/fstab to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6 or later).
# Follow the README instructions, which involves copying the kernel modules into the SD card rootfs and writing u-boot and the bootloader.

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki.
* [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 BraveHeart hardware details]] (details specific to the BraveHeart handsets).
* [[PinePhone_v1.2|PinePhone 1.2 UBports CE hardware details]] (details specific to the UBports Community Edition handsets).
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here].

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://store.pine64.org/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards]

PinePhone Software Releases

2020-05-22T00:05:20Z

E1337: /* Other Resources */

This page contains a list of all available releases for the PinePhone as well as links to further resources.

See [[PinePhone Installation Instructions]] on how to install the operation systems.

Note: Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.

= Software Releases =
This is a list of OSes that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used, if possible required patches are included.

== postmarketOS ==
[[File:PostmarketOS-logo.png|100px]]

postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and Phosh.

* ''' Download location '''
Rather than downloading a demo image, postmarketOS [https://wiki.postmarketos.org/wiki/Installation_guide recommends the use of their script], pmbootstrap, that can tailor build your SD card for you.

Note: pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC].

Demo images can be found [http://images.postmarketos.org/pinephone/ here].

* ''' username/password '''
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own username and password (the Phosh lock screen requires your password, but only presents a numeric keyboard, so you should use only numbers in your password).

* ''' What works, what does not work '''
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]

If you install Firefox browser (or are using a demo image that already has it installed) then [https://wiki.postmarketos.org/wiki/Firefox these hints] in the pmOS wiki are recommended.

* ''' How to contribute and report defects '''
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker] for PinePhone support. See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

== Ubuntu Touch by UBports ==
[[File:Ubports-logo.png|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community. Installation instructions can be found on [https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.

* ''' Download location '''
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

* ''' username/password '''
Set up during boot

* ''' What works, what does not work '''
Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].

* ''' How to contribute and report defects '''
See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page]. See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

== Mobian ==
[[File:Debian-logo.png]]

An unofficial Debian build for ARM64 running with the Phosh user interface (developed by Purism, Phosh uses Wayland instead of Xorg). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot). Current version is Debian Bullseye.

* ''' Download location '''
[http://images.mobian-project.org/ Mobian downloadable images]

Don't forget to extract the image before installing:
$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://gitlab.com/mobian1/wiki/-/wikis/Install project page] for specific installation instructions.

* ''' username/password '''
mobian/1234

* ''' What works, what does not work '''

See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.

Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

* ''' How to contribute and report defects '''
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker]. As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Mobian issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask. Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

* ''' Notes '''
See [[Mobian for PinePhone]] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== SailfishOS ==


Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.

* ''' Download location '''
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).
* ''' username/password '''

Set PIN on initialization.

* ''' What works, what does not work '''
May 4th 2020: The SFOS image is now the latest 3.3.0.16 release. This has resolved many problems (for example MTP file transfer now works) but there are several glitches, the most serious being total freeze requiring reboot. Random hissing noise for about 10 seconds. This release of SF has Nextcloud integration.

May 9th 2020: Voice calls now work in pipeline, arriving in builds within days. If you have a Jolla registration a minor bug means you have to submit the request twice. WiFi is intermittent. The battery indicator previously only showed level at boot, now improved but far from reliable.

If you're not familiar with SFOS pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. The Storeman app for openrepos is now preinstalled, and also Webcat browser as the built in browser is not working at the moment.

* ''' How to contribute and report defects '''

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues SailfishOS wiki] for links to their forum as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS SailfishOS wiki] for options to contribute

* ''' Notes '''
OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like crust or changes of partition layout are added then you need to reflash.

== PureOS ==
[[File:Pureos.png]]

PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.

* ''' Download location '''
This is an unofficial/unsupported PinePhone port by ''mozzwald'' and maintained by clover that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here].

* ''' source code '''
If you want to report a bug or look at what goes into the PinePhone build of PureOS, visit the Git [http://pureos.ironrobin.net/git/clover/pinephone/ repository].

* ''' username/password '''
purism/123456

* ''' Build instructions '''
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].

== Fedora ==
[[File:Fedora-logo.png|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum].

* ''' Download location '''
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]

* ''' username/password '''
pine/1111

* ''' What works, what does not work '''
WiFi, Bluetooth, SMS, Data, Calls all work! There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution.

* ''' How to contribute and report defects '''
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker]. Be sure to include logs if applicable! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github].

== Arch Linux ARM ==
[[File:Archlinux-logo.png|100px]]

An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.

* ''' Download location '''
https://github.com/dreemurrs-embedded/Pine64-Arch/releases

* ''' username/password '''
alarm/alarm

* ''' What works, what does not work '''
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.

To access the device, ssh to 172.16.42.1 with the credentials above.

* ''' How to contribute and report defects '''
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub].

== Manjaro ARM ==
[[File:Manjaro-logo.svg|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.

* ''' Download location '''
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro forum announcement of Alpha5 version]

* ''' username/password '''
** manjaro/1234
** root/root

* ''' What works, what does not work '''
See Manjaro's [https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 announcement]. In particular, phone calls do not yet work from the Phone application.

* ''' How to contribute and report defects '''

See the end of the [https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 announcement].

== Maemo Leste ==


[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions].

* ''' Download location '''
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

* ''' username/password '''
root/toor

You may use "sudo" directly.

* ''' What works, what does not work '''
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).

* ''' How to contribute and report defects '''
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]. Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available.

== Nemo Mobile ==


Nemo Mobile is the open source build of Sailfish OS, see the new website nemomobile.net.

You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to SD card/emmc on the PinePhone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).

* ''' Download location '''
Download location is [https://github.com/neochapay/nemo-device-dont_be_evil/ here on GitHub]. The latest version is not an image file and therefore not for beginners!

Alternative easy installation method: install Sailfish on your PP first (follow instructions on this page under Sailfish). Enable developer mode.
In the terminal run as root (devel-su):

ssu ar nemo-devel-ux http://repo.merproject.org/obs/home:/neochapay:/nemo-ux/sailfish_latest_armv7hl/

then
pkcon refresh

then install the nemo-specific Glacier packages:

pkcon install lipstick-glacier-home-qt5

If necessary, reboot.

* ''' username/password '''

* ''' What works, what does not work '''
Scroll down the page [https://github.com/neochapay/nemo-device-dont_be_evil/ here].

* ''' How to contribute and report defects '''
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's Github page]

== KDE Neon ==


Based on KDE Neon for the desktop, comes with Plasma Mobile.

* ''' Download location '''
Plasma mobile images can be found [https://images.plasma-mobile.org/pinephone/ here].

* ''' username/password '''
phablet/1234

* ''' What works, what does not work '''

* ''' How to contribute and report defects '''

== NixOS ==


''NixOS support is handled through the Mobile NixOS project.''

* [https://mobile.nixos.org/ Project home page]
* [https://github.com/NixOS/mobile-nixos Source code repository]

There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].

* ''' What works, what does not work '''

This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.

<cite>
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.
</cite>

* ''' How to contribute and report defects '''
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a PinePhone when reporting issues. Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== LuneOS ==


Based on WebOS by LG, comes with Luna Next desktop environment.

* ''' Download location '''
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage.

* ''' username/password '''

* ''' What works, what does not work '''

* ''' How to contribute and report defects '''

= Factory Test OS =
On the BraveHeart model there was a pmOS based basic factory test OS pre-installed on the eMMC. Martijn Braam from pmOS has improved the functionality of the image considerably.

Since the 20200501 version it is able to test all the hardware. It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image. The downloadable image just does the hardware tests.

Do not flash eMMC to test your device, just copy it to mSD and test from there. New versions are distributed as part of the pmOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one that is marked pine-pinephone-YYYYMMDD-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

= Installing other ARM64 distributions =
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distribution to the PinePhone.

'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.

If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).

# Create a boot (from 4 MB to about 252 MB) and root (from 252 MB to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).
# Edit /etc/fstab to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6 or later).
# Follow the README instructions, which involves copying the kernel modules into the SD card rootfs and writing u-boot and the bootloader.

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|PinePhone hardware details]] in this Pine64 wiki.
* [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 BraveHeart hardware details]] (details specific to the BraveHeart handsets).
* [[PinePhone_v1.2|PinePhone 1.2 UBports CE hardware details]] (details specific to the UBports Community Edition handsets).
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here].

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://store.pine64.org/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards]