https://wiki.pine64.org/api.php?action=feedcontributions&user=KJ7RRV&feedformat=atomPINE64 - User contributions [en]2024-03-29T07:26:34ZUser contributionsMediaWiki 1.37.1https://wiki.pine64.org/index.php?title=PineTime&diff=20541PineTime2023-08-20T15:48:30Z<p>KJ7RRV: /* Useful articles and blog posts */</p>
<hr />
<div>[[File:Pinetime.png|400px|thumb|right|The PineTime]]<br />
<br />
The '''PineTime''' is a free and open source smartwatch capable of running custom-built open operating systems. Some of the notable features include a heart rate monitor, a week-long battery, and a capacitive touch IPS display that is legible in direct sunlight. It is a fully community driven side-project which anyone can contribute to, allowing you to keep control of your device.<br />
<br />
== Getting started ==<br />
<br />
'''Read these first!'''<br />
<br />
* [[Upgrade PineTime to InfiniTime 1.0.0|Upgrading your new PineTime to InfiniTime 1.0.0]]<br />
* [[PineTime Devkit Wiring]]<br />
* [[Reprogramming the PineTime|Reprogramming the PineTime (development kit)]]<br />
* [[Switching your PineTime between InfiniTime and Wasp-os]]<br />
<br />
The frequently asked question can be found in the article [[PineTime FAQ]].<br />
<br />
== Default OS ==<br />
<br />
The current default operating system on the PineTime is called [[InfiniTime]], you can find more information about the firmware on its GitHub page. First devkits shipped with a proprietary custom firmware.<br />
<br />
You can find a list of available firmware and other software here: [[PineTime Development]]<br />
<br />
== Companion Apps ==<br />
<br />
PineTime/InfiniTime needs a companion app to e.g. upload a firmware, get notifications from a phone, or just get the date/time. <br />
Here are some companion apps:<br />
<br />
* [https://www.gadgetbridge.org Gadgetbridge] (Android >= 4.4) - Companion mobile app, supports updating firmware/bootloader, send notifications, etc.<br />
* [https://openrepos.net/content/piggz/amazfish Amazfish] (SailfishOS and Linux) - Companion mobile and desktop app, supports updating firmware/bootloader, send notifications, etc.<br />
* [https://github.com/alexr4535/siglo Siglo] (Linux) - Companion desktop app.<br />
* [https://github.com/ZephyrLabs/PinetimeFlasher PinetimeFlasher] (Windows) - Companion desktop app, only supports flashing firmware.<br />
* [https://apps.apple.com/us/app/nrf-connect-for-mobile/id1054362403 nRFConnect] (iOS) - Only supports flashing firmware. The app is closed source and versions after 4.24.3 don't work for the PineTime anymore<br />
* [https://github.com/xan-m/InfiniLink InfiniLink] (iOS) - Companion mobile app in development. Supports updating firmware/bootloader, setting date and time, Apple Music controls, and battery and heart rate data.<br />
* [https://gitea.elara.ws/Elara6331/itd ITD] (Linux)<br />
<br />
== Specifications ==<br />
* '''Dimensions:''' 37.5 x 40 x 11mm<br />
* '''Weight:''' 38 grams<br />
* '''IP Rating:''' IP67 (waterproof to 1 meter (sealed edition!))<br />
* '''Display:'''<br />
** '''Size:''' 1.3 inches (33mm) diagonal<br />
** '''Type:''' IPS capacitive touchscreen, RGB 65K colors<br />
** '''Display Controller:''' ST7789<br />
** '''Resolution:''' 240x240 pixels<br />
* '''System on Chip:''' Nordic Semiconductor nRF52832<br />
* '''Flash:''' 512KB with additional 4MB SPI NOR<br />
* '''RAM:''' 64KB<br />
* '''Bluetooth:''' [[PineTime_Bluetooth|5.0 (including Bluetooth Low Energy)]]<br />
* '''Sensors:''' Accelerometer, Heart rate sensor<br />
* '''Feedback:''' Vibration motor<br />
* '''Battery:''' 170-180mAh 3.8V LiPo<br />
<br />
== Community ==<br />
<br />
=== Forum ===<br />
* [https://forum.pine64.org/forumdisplay.php?fid=134 PineTime forum]<br />
<br />
=== Chat ===<br />
* [https://matrix.to/#/#pinetime:matrix.org Matrix Channel] (No login required to read)<br />
* IRC Server: [ircs://irc.pine64.org#pinetime irc.pine64.org] Channel: PineTime<br />
* [https://t.me/pinetime Telegram group]<br />
* [https://discordapp.com/invite/DgB7kzr Discord server invite link]<br />
<br />
Developers and coding:<br />
* [https://matrix.to/#/#pinetime-dev:matrix.org Matrix Channel] (No login required to read)<br />
* [https://t.me/pinetime_dev Telegram group]<br />
* [https://discordapp.com/invite/DgB7kzr Discord server invite link]<br />
<br />
=== Development efforts ===<br />
<br />
To read more about development on the PineTime, the projects available and more technical details, check out [[PineTime Development]]<br />
<br />
=== Useful articles and blog posts === <br />
<br />
If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.<br />
<br />
* [https://www.ncartron.org/one-week-with-my-pinetime---a-feedback.html Using the PineTime in production (January 2021)]<br />
* [https://lupyuen.github.io/articles/sneak-peek-of-pinetime-smart-watch-and-why-its-perfect-for-teaching-iot Sneak Peek of PineTime Smart Watch… And why it’s perfect for teaching IoT]<br />
* [https://lupyuen.github.io/articles/building-a-rust-driver-for-pinetimes-touch-controller Building a Rust Driver for PineTime’s Touch Controller]<br />
* [https://lupyuen.github.io/articles/porting-druid-rust-widgets-to-pinetime-smart-watch Porting (druid) Rust Widgets to PineTime Smart Watch]<br />
* [https://lupyuen.github.io/articles/optimising-pinetimes-display-driver-with-rust-and-mynewt Optimising PineTime’s Display Driver with Rust and Mynewt]<br />
* [https://electronut.in/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/ Getting Started with Zephyr RTOS on Nordic nRF52832 hackaBLE]<br />
* [https://blog.aegrel.ee/absniffer-cmsis-dap-sniffer.html Removing the lock and installing another firmware on the nRF52832 using CMSIS-DAP dongle on Linux]<br />
* [https://github.com/JF002/nrf52-baseproject/wiki/Build,-program-and-debug-NRF52-project-with-JLink,-CMake-and-CLion Build, program and debug NRF52 project with JLink, CMake and CLion]<br />
* [https://www.nrbtech.io/blog/2020/1/4/using-clion-for-nordic-nrf52-projects Using CLion for Nordic nRF52 projects]<br />
* [https://dev.to/aaronc81/flashing-your-pinetime-using-an-st-link-and-openocd-54dd Flashing your PineTime using an ST-Link and OpenOCD]<br />
* [https://zephyrlabs.github.io/Watchfaces/ Zephyrlabs: just a bunch of watchfaces made for the pinetime]<br />
* [https://pankajraghav.com/2021/04/03/PINETIME-STOPCLOCK.html Creating a stopwatch in Pinetime (with Infinitime)]<br />
* [https://kj7rrv.com/fixing-a-pinetime-charging-cradle Fixing a broken charging cradle]<br />
* [[PineTime Custom Watchface Tutorial]]<br />
* [[PineTimeStyle]]<br />
<br />
== Hardware ==<br />
<br />
=== Display ===<br />
<br />
Note: The factory-default software on the PineTime does not auto-detect the display being disconnected when it has already booted. That can cause garbled output, to fix it just restart the PineTime.<br />
<br />
The display is driven using the ST7789 display controller. Use the following pins to drive the screen:<br />
<br />
{| class="wikitable"<br />
|-<br />
! PineTime pin<br />
! ST7789 pin<br />
|-<br />
| LCD_SCK (P0.02)<br />
| SPI clock<br />
|-<br />
| LCD_SDI (P0.03)<br />
| SPI MOSI<br />
|-<br />
| LCD_RS (P0.18)<br />
| Command/Data pin (CD)<br />
|-<br />
| LCD_CS (P0.25)<br />
| Chip select<br />
|-<br />
| LCD_RESET (P0.26)<br />
| Display reset<br />
|-<br />
| LCD_BACKLIGHT_{LOW,MID,HIGH}<br />
| Backlight (active low)<br />
|}<br />
<br />
Notes:<br />
<br />
* Chip select must be held low while driving the display. It must be high when using other SPI devices on the same bus (such as external flash storage) so that the display controller won't respond to the wrong commands.<br />
* SPI must be used in mode 3. Mode 0 (the default) won't work.<br />
* LCD_BACKLIGHT_* is used to enable the backlight. Set at least one to low to see anything on the screen.<br />
* Use SPI at 8MHz (the fastest clock available on the nRF52832) because otherwise refreshing will be super slow.<br />
<br />
'''References''':<br />
<br />
[https://github.com/adafruit/Adafruit-ST7735-Library/ Adafruit ST7789 driver in cpp]<br />
<br />
=== Battery measurement ===<br />
<br />
Reading whether the PineTime has power attached is easy: simply read the charge indication pin (P0.12). When it is high it is running on battery, when it is low it is charging.<br />
<br />
Reading the battery voltage is a bit harder. For that you can use the battery voltage pin on P0.31 (AIN7). The returned value is 12 bits, which means it is 0..4095. You can get the measured voltage with the following formula, assuming a reference voltage of 3.3V (this is configurable in the ADC):<br />
<br />
adcVoltage = adcValue / (4095 / 3.3)<br />
<br />
The measured voltage is actually half of the actual battery voltage, because the ADC is connected between a voltage divider where both resistors are 1MΩ. This can be corrected by multiplying the value:<br />
<br />
batteryVoltage = adcValue * 2 / (4095 / 3.3)<br />
<br />
It's often better to avoid floating point values on embedded systems and in this case there is no reason to use float at all, we can just represent the value in millivolts. Therefore the formula can be simplified to:<br />
<br />
batteryVoltage = adcValue * 2000 / (4095 / 3.3)<br />
batteryVoltage = adcValue * 2000 / 1241<br />
<br />
Converting this voltage to an estimated capacity in percent requires a more complicated algorithm, because Lithium-ion batteries have a non-linear discharge curve.<br />
<br />
=== Button ===<br />
<br />
The button on the side of the PineTime is disabled by default. To enable it, drive the button out pin (P0.15) high.<br />
<br />
While enabled, the button in pin (P0.13) will be high when the button is pressed, and low when it is not pressed.<br />
<br />
Note that the button consumes around 34µA when P0.15 is left high. To reduce current consumption, set it to low most of the time and only set it to high shortly before reading it. The button needs a short time to give good outputs though, setting P0.15 high at least four times in a row seems to result in enough delay that P0.13 has a stable output.<br />
<br />
=== Touch panel ===<br />
<br />
The touch panel is controlled by a Hynitron CST816S chips. Unfortunately, there is not much information about this chip on the internet apart from the datasheet below and a [https://github.com/lupyuen/hynitron_i2c_cst0xxse/ reference driver]. This is enough to implement a basic driver, but crucial information needed to implement advanced functionalities are missing (I²C protocol and registers, timings, power modes,...).<br />
<br />
==== Pins ====<br />
<br />
* P0.10 : Reset<br />
* P0.28 : Interrupt (signal to the CPU when a touch event is detected)<br />
* P0.06 : I²C SDA<br />
* P0.07 : I²C SCL<br />
<br />
==== I²C ====<br />
<br />
* Device address : 0x15<br />
* Frequency : from 10Khz to 400Khz<br />
<br />
'''NOTE: ''' The controller goes to sleep when no event is detected. In sleep mode, the controller does not communicate on the I²C bus (it appears disconnected). So, for the communication to work, you need to tap on the screen so that the chip wakes-up.<br />
<br />
'''NOTE: ''' The I²C bus, also known as TWI bus, has known issues, make sure to write your TWI driver with timeouts.<br />
<br />
==== Touch events ====<br />
<br />
Touch information is available from the 63 first registers of the controller. Remember: the device is in sleep mode when no touch event is detected. It means that you can read the register only when the touch controller detected an event. You can use the ''Interrupt'' pin to detect such event in the software. <br />
<br />
These 63 bytes contain up to 10 touch point (X, Y, event type, pressure,...) : <br />
<br />
{| class="wikitable"<br />
! Byte<br />
! Bit7<br />
! Bit6<br />
! Bit5<br />
! Bit4<br />
! Bit3<br />
! Bit2<br />
! Bit1<br />
! Bit0<br />
|-<br />
|0<br />
|colspan="8"|?<br />
|-<br />
|1<br />
|colspan="8"|GestureID : (Gesture code ,<br />
<br />
0x00: no gesture,<br />
<br />
0x01: Slide down,<br />
<br />
0x02: Slide up,<br />
<br />
0x03: Slide left,<br />
<br />
0x04: Slide right,<br />
<br />
0x05: Single click,<br />
<br />
0x0B: Double click,<br />
<br />
0x0C: Long press) <br />
|-<br />
|2<br />
|colspan="4"|? <br />
|colspan="4"|Number of touch points <br />
|-<br />
|3<br />
|colspan="2"|Event (0 = Down, 1 = Up, 2 = Contact)<br />
|colspan="2"|?<br />
|colspan="4"|X (MSB) coordinate<br />
|-<br />
|4<br />
|colspan="8"|X (LSB) coordinate<br />
|-<br />
|5<br />
|colspan="2"|?<br />
|colspan="2"|Touch ID<br />
|colspan="4"|Y (MSB) coordinate<br />
|-<br />
|6<br />
|colspan="8"|Y (LSB) coordinate<br />
|-<br />
|7<br />
|colspan="8"|Pressure (?)<br />
|-<br />
|8<br />
|colspan="8"|Miscellaneous (?)<br />
|}<br />
<br />
Bytes 3 to 8 are repeated 10 times (10*6 + 3 = 63 bytes).<br />
<br />
'''NOTES'''<br />
<br />
* The touch controller seems to report only 1 touch point<br />
* Fields X, Y, Number of touch points and touch ID are updated. The others are always 0.<br />
<br />
==== Registers ====<br />
<br />
The reference driver specifies some registers and value, but there is no information about them: <br />
<br />
{| class="wikitable"<br />
<br />
!Register<br />
!Address<br />
!Description<br />
|-<br />
|HYN_REG_INT_CNT<br />
|0x8F<br />
|<br />
|-<br />
|HYN_REG_FLOW_WORK_CNT<br />
|0x91<br />
|<br />
|-<br />
|HYN_REG_WORKMODE <br />
|0x00<br />
|0 = WORK, 0x40 = FACTORY<br />
|-<br />
|HYN_REG_CHIP_ID<br />
|0xA3<br />
|<br />
|-<br />
|HYN_REG_CHIP_ID2<br />
|0x9F<br />
|-<br />
|HYN_REG_POWER_MODE<br />
|0xA5<br />
|0x03 = SLEEP (reset the touchpanel using the reset pin before using this register : pin_low, delay 5ms, pin_high, delay 50ms then write 3 to register 0xA5)<br />
|-<br />
|HYN_REG_FW_VER<br />
|0xA6<br />
|<br />
|-<br />
|HYN_REG_VENDOR_ID<br />
|0xA8<br />
|<br />
|-<br />
|HYN_REG_LCD_BUSY_NUM<br />
|0xAB<br />
|<br />
|-<br />
|HYN_REG_FACE_DEC_MODE_EN<br />
|0xB0<br />
|<br />
|-<br />
|HYN_REG_GLOVE_MODE_EN<br />
|0xC0<br />
|<br />
|-<br />
|HYN_REG_COVER_MODE_EN<br />
|0xC1<br />
|<br />
|-<br />
|HYN_REG_CHARGER_MODE_EN<br />
|0x8B<br />
|<br />
|-<br />
|HYN_REG_GESTURE_EN<br />
|0xD0<br />
|<br />
|-<br />
|HYN_REG_GESTURE_OUTPUT_ADDRESS<br />
|0xD3<br />
|<br />
|-<br />
|HYN_REG_ESD_SATURATE 0xED<br />
|0xED<br />
|<br />
|}<br />
<br />
'''WARNING : ''' <del>Writing the SLEEP command (write 0x05 in HYN_REG_POWER_MODE) seems to freeze the controller (it returns only static values) until the battery is totally drained and the whole system reset. Analysis and debugging is more than welcome!</del><br />
<br />
=== Accelerometer ===<br />
The on board accelerometer in devices shipped before July 2021 is a Bosch BMA421, connected to the I2C bus.<br />
Devices shipped after July 2021 use a Bosch BMA425 accelerometer.<br />
<br />
==== Pins ====<br />
<br />
* P0.06 : I²C SDA<br />
* P0.07 : I²C SCL<br />
* P0.08 : Interrupt<br />
<br />
I2C Device address : 0x18<br />
<br />
=== Reducing power consumption ===<br />
<br />
The PineTime appears to be able to sleep with a current consumption of [https://github.com/InfiniTimeOrg/InfiniTime/issues/53#issuecomment-783654321 only 66µA].<br />
<br />
To investigate current consumption, it's a good idea to disable everything possible to get the lowest current consumption possible, and then re-enable things one by one. Here is one way to get a baseline current consumption of 60µA, as measured from the 3.3V pin with the battery disconnected:<br />
<br />
* Enable the DC/DC regulator. This doesn't affect the current consumption while sleeping, but almost halves the runtime current consumption.<br />
* Use the low-frequency (32.768kHz) oscillator.<br />
* Leave all pins in their default state, except for P0.05 (SPI CS) and P0.25 (LCD CS) which should be configured as an output and set to high.<br />
* Put the heart rate sensor in sleep mode by setting the PDRIVER (0x0C) register to 0, see [https://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf#page=12 the HRS3300 datasheet for details].<br />
* Put the SPI flash in [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf#page=38 deep power-down mode] by setting flash CS high, then low, then writing the byte 0xb9 on the SPI bus, and then setting flash CS high again.<br />
* Sleep in a loop, using WFE or WFI (if you're using the Nordic SoftDevice, call <code>sd_app_evt_wait</code> instead).<br />
<br />
Here are some current consumption statistics (current consumed in addition to the baseline power), roughly ordered from large to small:<br />
<br />
{| class="wikitable"<br />
!Source<br />
!Current<br />
!Notes<br />
|-<br />
|SWD<br />
|3.05mA<br />
|Power cycle the chip after programming to avoid this, it can hide other inefficiencies.<br />
|-<br />
|LCD<br />
|5.61mA<br />
|Set the LCD to sleep mode when not used, using SLPIN.<br />
|-<br />
|Backlight high <br />
|12.27mA<br />
|-<br />
|Backlight mid<br />
|5.51mA<br />
|-<br />
|Backlight low<br />
|1.83mA<br />
|-<br />
|ADC left enabled<br />
|1.3mA<br />
|Stopping SAADC brings the current back to the baseline. It seems that it doesn't need to be disabled entirely.<br />
|-<br />
|UART left enabled<br />
|1.25mA<br />
|Some bootloaders might leave the UART enabled after they start the application, leading to high current consumption.<br />
|-<br />
|Edge triggered pin interrupts<br />
|0-0.47mA?<br />
|It appears that under some configurations, edge triggered interrupts result in a large power drain. One way to avoid this is by using the pin sense mechanism.<br />
|-<br />
|Accelerometer<br />
|0.15mA<br />
|151µA in performance mode, 99µA with performance mode disabled but power saving disabled, 50µA while polling on a high interval (100Hz, average 4 samples), 14µA when running at the lowest possible setting that still counts steps (50Hz, no averaging).<br />
|-<br />
|HRS sensor is enabled<br />
|0.1mA<br />
|The HRS3300 sensor is enabled on power on. Write byte 0x00 to the PDRIVER register (0x0C) to set it in sleep mode.<br />
|-<br />
|BUTTON_OUT left high<br />
|0.04mA<br />
|See [[#Button|Button]] for how to avoid this.<br />
|-<br />
|SPI flash sleep mode<br />
|0.014mA<br />
|Sleep mode still consumes power. Put it in [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf#page=38 deep power down mode] to avoid this.<br />
|-<br />
|SPI, I2C<br />
|(negligible)<br />
|SPI and I2C appear to consume very little power when idle, around 1µA or less.<br />
|}<br />
<br />
== Accessory == <br />
<br />
The following accessory is compatible with the PineTime.<br />
<br />
=== Watch band ===<br />
<br />
The PineTime uses a standard 20mm watch band / strap. There is a [https://forum.pine64.org/showthread.php?tid=9392&pid=81902 thread] in the forum discussing this.<br />
<br />
Due to the watches design. Retention for the spring bars are recessed into the watch. Not all 20mm bands / straps work. This is especially the case for Nato style bands / straps being too thick.<br />
<br />
<br />
Known working bands:<br />
<br />
* [https://www.bisonstrap.com/products/bisonstrap-waterproof-sport-silicone-watch-bands-black?variant=40103305543773 BISONSTRAP 20mm Quick Release Silicone Watch Band] / [https://www.amazon.com/dp/B08XTNKQSJ Amazon US]<br />
* DMVEIMAL 20mm Quick Release Watch Band Metal Strap / [https://www.amazon.com/gp/product/B0BGJC8CXG Amazon US]<br />
* Morsey 20mm Quick Release Watch Band / [https://www.amazon.com/dp/B08DD57SHV Amazon US]<br />
<br />
=== Cases ===<br />
There are no cases for PineTime yet, but some cases for Fitbit are suitable for it. Cases for Fitbit have one microphone hole, which is unnecessary for the PineTime, but otherwise they fit perfectly.<br />
<br />
* [https://www.aliexpress.com/item/1005003150606521.html Soft TPU case for Fitbit Versa 2/Versa Lite from AliExpress]<br />
<br />
The community designed the following cases:<br />
* [https://www.thingiverse.com/thing:4172849 PineTime Smart Watch case by dara0s at thingiverse]<br />
* [https://www.thingiverse.com/thing:4651462 PineTime dev kit back fix by joaquimorg at thingiverse]<br />
* [https://www.thingiverse.com/thing:4763267 PineTime dev kit charging holder v4 by zevix81 at thingiverse]<br />
* [https://www.prusaprinters.org/prints/88913-pinetime-charger-case PineTime Charger Travel Case by brett at PrusaPrinters]<br />
<br />
== Datasheets, Schematics and Certifications ==<br />
<br />
=== Schematics ===<br />
* [https://files.pine64.org/doc/PineTime/PineTime%20Schematic-V1.0a-20191103.pdf PineTime Schematic ver1.0a]<br />
* [https://files.pine64.org/doc/PineTime/PineTime%20Port%20Assignment%20rev1.0.pdf PineTime GPIO Port Assignment ver1.0]<br />
<br />
Note: The part number for the SPI FLASH in the schematic diagram is not correct, the PineTime features a larger external FLASH device, see below.<br />
<br />
=== Chip Datasheets ===<br />
<br />
NORDIC nRF52832 information:<br />
* [https://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf nRF52832 Product Brief]<br />
* [https://infocenter.nordicsemi.com/pdf/nRF52832_PS_v1.4.pdf nRF52832 Product Specification v1.4]<br />
<br />
ARMv7-M information:<br />
* [https://developer.arm.com/documentation/ddi0403/ee/?lang=en ARMv7-M Architecture Reference Manual]<br />
<br />
=== Component Datasheets ===<br />
<br />
PMU (Power Management Unit) information:<br />
* [https://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]<br />
* [https://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]<br />
<br />
SPI Flash information:<br />
* [https://www.elnec.com/en/device/XTX/XT25F32B+%28QuadSPI%29+%5BSOP8-200%5D/ XTX XT25F32B 32Mb(4MB) SPI NOR Flash] (data sheets for this part are hard to find but it acts similar to other QuadSPI SPI NOR Flash such as [https://www.macronix.com/Lists/Datasheet/Attachments/7426/MX25L3233F,%203V,%2032Mb,%20v1.6.pdf Macronix 32Mb(4MB) SPI NOR Flash])<br />
* [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf XTX XT25F32B]<br />
* IDs for XT25F32B are: manufacturer (0x0b), device (0x15), memory type (0x40), density (0x16)<br />
<br />
LCD Panel:<br />
* [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20LCD%20Panel.jpg 1.3" 240x240 IPS LCD Panel Specification for PineTime]<br />
* [https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf 11.6" Sitronix LCD Driver/Controller Datasheet]<br />
<br />
Touchpad information:<br />
* [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]<br />
* [https://files.pine64.org/doc/datasheet/pinetime/CST816S数据手册V1.1.pdf 11.6" Hynitron CST816S Capacitive Touch Controller Datasheet in Chinese]<br />
* [https://wiki.pine64.org/images/2/2f/CST816S.zip Touch Controller Datasheet en]<br />
<br />
Sensor:<br />
* [https://datasheet.lcsc.com/lcsc/1912111437_Bosch-Sensortec-BMA425_C437656.pdf BOSCH BMA425 Triaxial Acceleration Sensor Datasheet on current PineTime device]<br />
* [https://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial Acceleration Sensor Product Brief on early PineTime device]<br />
* [https://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]<br />
<br />
=== Certificates ===<br />
* [https://files.pine64.org/doc/cert/FCC_Grant_PineTime_2AWAG-PINETIME_DTS.pdf PineTime FCC Certificate]<br />
* [https://files.pine64.org/doc/cert/CTL2203033031-W%20RED%20Certificate.pdf PineTime CE Certificate]<br />
<br />
=== Manuals ===<br />
* [[:File:PineTime Quick Start Guide.pdf|PineTime Quick Start Guide]]<br />
<br />
[[Category:PineTime]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_Carrier_Support&diff=13277PinePhone Carrier Support2022-07-10T05:31:15Z<p>KJ7RRV: /* North America */ remove old Tello line</p>
<hr />
<div>{{under construction}}<br />
<br />
This page contains hints on setting up cellular network connectivity for specific carriers.<br />
For more general information, see the carrier support section of [[PinePhone#Modem]]. For the APN settings see [[PinePhone APN Settings]].<br />
<br />
= Check compatibility =<br />
To check if the PinePhone is supported on your carrier:<br />
<br />
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 in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).<br />
<br />
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.<br />
<br />
= Tested and working carriers =<br />
<br />
The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):<br />
<br />
== Asia ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021<br />
|-<br />
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021<br />
|-<br />
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021<br />
|-<br />
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021<br />
|-<br />
| China || China Mobile || Yes || Not tested || Yes || No || Mobile NixOS, December 2021<br />
|-<br />
| China || China Telecom || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022<br />
|-<br />
| Japan || Rakuten Mobile || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (rivised from January 2021)<br />
|}<br />
<br />
== Africa ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Europe ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)<br />
|-<br />
|-<br />
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)<br />
|-<br />
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh<br />
|-<br />
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21<br />
|-<br />
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021<br />
|-<br />
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022<br />
|-<br />
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022<br />
|-<br />
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021<br />
|-<br />
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date) with Phosh, 2021-06-07<br />
|-<br />
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15<br />
|-<br />
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28<br />
|-<br />
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma<br />
|-<br />
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30<br />
|-<br />
| Hungary || Telenor || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24<br />
|-<br />
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30<br />
|-<br />
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15<br />
|-<br />
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15<br />
|-<br />
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14<br />
|-<br />
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23<br />
|-<br />
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13<br />
|-<br />
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile<br />
|-<br />
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch<br />
|}<br />
<br />
== North America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI || Modem Firmware<br />
|-<br />
|-<br />
| USA || AT&T || Yes || Yes || Yes || Yes || <br />
* Mobian - Phosh <br />
|-<br />
| USA || T-Mobile || Yes || No || Yes || Yes || <br />
* Arch Linux Arm 2020/11/29 <br />
* Mobian - Phosh <br />
* Manjaro - KDE Plasma Mobile<br />
|-<br />
| USA || T-Mobile || Yes || Yes || Yes || Yes || <br />
* Mobian Bookworm (Phosh) (2022-03-08) <br />
|| EG25GGBR07A08M2G_01.003.01.003 <br />
|-<br />
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm (Phosh,SXMO) 2021/04/29 <br />
*Manjaro - Phosh 2021/04/29 <br />
*Mobian - Phosh 2021/3/20<br />
|-<br />
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy || <br />
*Manjaro - Plasma Dev 2020/11/21 <br />
*Ubuntu Touch - 2020/11/26 <br />
*KDE Neon 2020/11/02<br />
|-<br />
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes || <br />
*Mobian - Phosh 2021/3/14<br />
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26<br />
*Ubuntu Touch 2021/5/24<br />
*Manjaro - Phosh 2022/3/25<br />
|-<br />
| USA || Patriot Mobile <br> (T-Mobile) || Yes || Yes <br> chatty v0.6.1 <br> mmsd-tng v1.8 || Yes || Yes || <br />
*Arch Linux Arm - Phosh 2022/01/12<br />
|-<br />
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes || <br />
*DanctNIX (Arch Linux ARM) - Phosh 2022-07-09<br />
|-<br />
| USA || TracFone || No || No || No || No || <br />
*postMarketOS - Phosh 2022/06/28<br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/1<br />
|-<br />
| USA || US Mobile || Yes || Not tested || Yes || Not Tested || <br />
*Mobian - Phosh 2022/01/09<br />
|-<br />
| USA || Verizon || No || No || No || No ||<br />
*Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes) <br />
|-<br />
| USA || Verizon || Not tested || Not tested || Yes || Not via gui || <br />
*Manjaro - KDE Plasma Mobile 2021/5/10 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Not via gui || <br />
*Manjaro - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*postmarketOS - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Arch - Phosh 2021/5/31 <br />
|-<br />
| Canada || Freedom || Yes || Not tested || Yes || Yes || <br />
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25 <br />
|-<br />
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested || <br />
*Mobian - Phosh 2021/11/18<br />
|-<br />
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes || <br />
*Manjaro - Phosh 2021/06/26<br />
|-<br />
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 0.10.2 2021/05/29<br />
|-<br />
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||<br />
*Mobian - Phosh Weekly 2022/04/13<br />
*PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13<br />
*PostmarketOS - Phosh v21.12 (stable) 2022/04/13<br />
*PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13<br />
*PostmarketOS - sxmo edge 2021/09/09<br />
|-<br />
| USA || Ting || Yes || Yes - buggy || Yes || Yes || <br />
*Manjaro - Phosh 2021/12/10 <br />
|-<br />
|}<br />
<br />
== South America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Australia / Oceania ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.<br />
|-<br />
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.<br />
|-<br />
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).<br />
|-<br />
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh<br />
|-<br />
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)<br />
|-<br />
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh<br />
|}<br />
<br />
== Middle East ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022<br />
|-<br />
|-<br />
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022<br />
|-<br />
|-<br />
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022 <br />
|-<br />
|-<br />
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
= Special carrier notes =<br />
<br />
{{Warning|This section contains providers which do not work or require special settings or actions to work.}}<br />
<br />
Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:<br />
<br />
== USA ==<br />
=== AT&T ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.<br />
<br />
AT&T may drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.<br />
<br />
=== Consumer Cellular ===<br />
<br />
Consumer Cellular is a MVNO that uses both AT&T and T-Mobile networks. On the AT&T network LTE data works without special configuration. If you transfer a SIM card from another phone to the PinePhone, you may need to contact customer support in order for them to register the IMEI association to the correct hardware; in one case it was first incorrectly identified as a Samsung Google Nexus Prime before later being correctly identified by the modem model Quectel EG25-G. Customer support also explicitly enabled VoLTE on the device. After VoLTE instructions on this site were followed and APN instructions on the Consumer Cellular site were followed, VoLTE was confirmed working.<br />
<br />
=== Cricket Wireless ===<br />
Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).<br />
<br />
=== Faith Wireless ===<br />
Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)<br />
<br />
=== SimpleMobile ===<br />
SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.<br />
<br />
=== Sprint ===<br />
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.<br />
<br />
=== T-Mobile ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).<br />
<br />
T-Mobile's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].<br />
<br />
While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.<br />
<br />
=== Verizon ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.<br />
<br />
Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.<br />
<br />
=== TracFone ===<br />
Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.<br />
<br />
=== Google Fi ===<br />
Only T-Mobile service works currently, not US Cellular or Sprint.<br />
The APN is h2g2.<br />
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].<br />
<br />
Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps. <br />
<br />
It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.<br />
<br />
== Europe ==<br />
=== Telekom Germany ===<br />
With low signal, there may be loud interference noise audible in calls on the receiving end. It has not yet been tested whether or not this problem is carrier specific. An easy fix is extending the modem antenna with aluminum foil (or similar) inside the back cover of the phone.<br />
<br />
=== Orange Poland ===<br />
Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.<br />
<br />
== Asia ==<br />
=== China Telecom ===<br />
The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.<br />
<br />
Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:<br />
<pre><br />
AT+QMBNCFG="autosel",0<br />
AT+QMBNCFG="select","ROW_Generic_3GPP"<br />
AT+QCFG="ims",1<br />
</pre><br />
<br />
=== SoftBank ===<br />
SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS.<br /><br />
A free SIM is available, but that one is data only.<br /><br />
The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.<br />
<br />
ソフトバンク社のUSIMカードはIMEIロックで御座います。<br /><br />
なお、Android又はiOS限定です。<br /><br />
フリーSIMもありますが、これはデータのみSIMです。<br /><br />
ソフトバンク社を使っているMVNOで同じ問題があるかもしれませんので、出来ればMNOはNTTドコモ又はauをご選択下さい。<br />
<br />
= Known issues =<br />
Known issues:<br />
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.<br />
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.<br />
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.<br />
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].<br />
<br />
= MMS workarounds =<br />
These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:<br />
<br />
* JMMS: [https://git.sr.ht/~amindfv/jmms]<br />
* silvermms: [https://gitlab.com/5ilver/silvermms]<br />
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]<br />
<br />
There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.<br />
<br />
= Resources =<br />
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]<br />
<br />
<br />
[[Category:PinePhone]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_Carrier_Support&diff=13276PinePhone Carrier Support2022-07-10T05:12:15Z<p>KJ7RRV: /* North America */</p>
<hr />
<div>{{under construction}}<br />
<br />
This page contains hints on setting up cellular network connectivity for specific carriers.<br />
For more general information, see the carrier support section of [[PinePhone#Modem]]. For the APN settings see [[PinePhone APN Settings]].<br />
<br />
= Check compatibility =<br />
To check if the PinePhone is supported on your carrier:<br />
<br />
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 in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).<br />
<br />
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.<br />
<br />
= Tested and working carriers =<br />
<br />
The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):<br />
<br />
== Asia ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021<br />
|-<br />
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021<br />
|-<br />
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021<br />
|-<br />
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021<br />
|-<br />
| China || China Mobile || Yes || Not tested || Yes || No || Mobile NixOS, December 2021<br />
|-<br />
| China || China Telecom || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022<br />
|-<br />
| Japan || Rakuten Mobile || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (rivised from January 2021)<br />
|}<br />
<br />
== Africa ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Europe ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)<br />
|-<br />
|-<br />
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)<br />
|-<br />
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh<br />
|-<br />
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21<br />
|-<br />
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021<br />
|-<br />
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022<br />
|-<br />
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022<br />
|-<br />
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021<br />
|-<br />
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date) with Phosh, 2021-06-07<br />
|-<br />
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15<br />
|-<br />
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28<br />
|-<br />
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma<br />
|-<br />
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30<br />
|-<br />
| Hungary || Telenor || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24<br />
|-<br />
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30<br />
|-<br />
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15<br />
|-<br />
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15<br />
|-<br />
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14<br />
|-<br />
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23<br />
|-<br />
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13<br />
|-<br />
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile<br />
|-<br />
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch<br />
|}<br />
<br />
== North America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI || Modem Firmware<br />
|-<br />
|-<br />
| USA || AT&T || Yes || Yes || Yes || Yes || <br />
* Mobian - Phosh <br />
|-<br />
| USA || T-Mobile || Yes || No || Yes || Yes || <br />
* Arch Linux Arm 2020/11/29 <br />
* Mobian - Phosh <br />
* Manjaro - KDE Plasma Mobile<br />
|-<br />
| USA || T-Mobile || Yes || Yes || Yes || Yes || <br />
* Mobian Bookworm (Phosh) (2022-03-08) <br />
|| EG25GGBR07A08M2G_01.003.01.003 <br />
|-<br />
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm (Phosh,SXMO) 2021/04/29 <br />
*Manjaro - Phosh 2021/04/29 <br />
*Mobian - Phosh 2021/3/20<br />
|-<br />
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy || <br />
*Manjaro - Plasma Dev 2020/11/21 <br />
*Ubuntu Touch - 2020/11/26 <br />
*KDE Neon 2020/11/02<br />
|-<br />
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes || <br />
*Mobian - Phosh 2021/3/14<br />
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26<br />
*Ubuntu Touch 2021/5/24<br />
*Manjaro - Phosh 2022/3/25<br />
|-<br />
| USA || Patriot Mobile <br> (T-Mobile) || Yes || Yes <br> chatty v0.6.1 <br> mmsd-tng v1.8 || Yes || Yes || <br />
*Arch Linux Arm - Phosh 2022/01/12<br />
|-<br />
| USA || Tello (T-Mobile) || Yes || No || Yes || Yes || <br />
*postMarketOS - Phosh 2021/8/15<br />
|-<br />
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes || <br />
*DanctNIX (Arch Linux ARM) - Phosh 2022-07-09<br />
|-<br />
| USA || TracFone || No || No || No || No || <br />
*postMarketOS - Phosh 2022/06/28<br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/1<br />
|-<br />
| USA || US Mobile || Yes || Not tested || Yes || Not Tested || <br />
*Mobian - Phosh 2022/01/09<br />
|-<br />
| USA || Verizon || No || No || No || No ||<br />
*Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes) <br />
|-<br />
| USA || Verizon || Not tested || Not tested || Yes || Not via gui || <br />
*Manjaro - KDE Plasma Mobile 2021/5/10 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Not via gui || <br />
*Manjaro - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*postmarketOS - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Arch - Phosh 2021/5/31 <br />
|-<br />
| Canada || Freedom || Yes || Not tested || Yes || Yes || <br />
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25 <br />
|-<br />
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested || <br />
*Mobian - Phosh 2021/11/18<br />
|-<br />
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes || <br />
*Manjaro - Phosh 2021/06/26<br />
|-<br />
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 0.10.2 2021/05/29<br />
|-<br />
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||<br />
*Mobian - Phosh Weekly 2022/04/13<br />
*PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13<br />
*PostmarketOS - Phosh v21.12 (stable) 2022/04/13<br />
*PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13<br />
*PostmarketOS - sxmo edge 2021/09/09<br />
|-<br />
| USA || Ting || Yes || Yes - buggy || Yes || Yes || <br />
*Manjaro - Phosh 2021/12/10 <br />
|-<br />
|}<br />
<br />
== South America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Australia / Oceania ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.<br />
|-<br />
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.<br />
|-<br />
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).<br />
|-<br />
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh<br />
|-<br />
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)<br />
|-<br />
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh<br />
|}<br />
<br />
== Middle East ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022<br />
|-<br />
|-<br />
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022<br />
|-<br />
|-<br />
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022 <br />
|-<br />
|-<br />
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
= Special carrier notes =<br />
<br />
{{Warning|This section contains providers which do not work or require special settings or actions to work.}}<br />
<br />
Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:<br />
<br />
== USA ==<br />
=== AT&T ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.<br />
<br />
AT&T may drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.<br />
<br />
=== Consumer Cellular ===<br />
<br />
Consumer Cellular is a MVNO that uses both AT&T and T-Mobile networks. On the AT&T network LTE data works without special configuration. If you transfer a SIM card from another phone to the PinePhone, you may need to contact customer support in order for them to register the IMEI association to the correct hardware; in one case it was first incorrectly identified as a Samsung Google Nexus Prime before later being correctly identified by the modem model Quectel EG25-G. Customer support also explicitly enabled VoLTE on the device. After VoLTE instructions on this site were followed and APN instructions on the Consumer Cellular site were followed, VoLTE was confirmed working.<br />
<br />
=== Cricket Wireless ===<br />
Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).<br />
<br />
=== Faith Wireless ===<br />
Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)<br />
<br />
=== SimpleMobile ===<br />
SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.<br />
<br />
=== Sprint ===<br />
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.<br />
<br />
=== T-Mobile ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).<br />
<br />
T-Mobile's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].<br />
<br />
While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.<br />
<br />
=== Verizon ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.<br />
<br />
Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.<br />
<br />
=== TracFone ===<br />
Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.<br />
<br />
=== Google Fi ===<br />
Only T-Mobile service works currently, not US Cellular or Sprint.<br />
The APN is h2g2.<br />
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].<br />
<br />
Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps. <br />
<br />
It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.<br />
<br />
== Europe ==<br />
=== Telekom Germany ===<br />
With low signal, there may be loud interference noise audible in calls on the receiving end. It has not yet been tested whether or not this problem is carrier specific. An easy fix is extending the modem antenna with aluminum foil (or similar) inside the back cover of the phone.<br />
<br />
=== Orange Poland ===<br />
Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.<br />
<br />
== Asia ==<br />
=== China Telecom ===<br />
The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.<br />
<br />
Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:<br />
<pre><br />
AT+QMBNCFG="autosel",0<br />
AT+QMBNCFG="select","ROW_Generic_3GPP"<br />
AT+QCFG="ims",1<br />
</pre><br />
<br />
=== SoftBank ===<br />
SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS.<br /><br />
A free SIM is available, but that one is data only.<br /><br />
The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.<br />
<br />
ソフトバンク社のUSIMカードはIMEIロックで御座います。<br /><br />
なお、Android又はiOS限定です。<br /><br />
フリーSIMもありますが、これはデータのみSIMです。<br /><br />
ソフトバンク社を使っているMVNOで同じ問題があるかもしれませんので、出来ればMNOはNTTドコモ又はauをご選択下さい。<br />
<br />
= Known issues =<br />
Known issues:<br />
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.<br />
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.<br />
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.<br />
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].<br />
<br />
= MMS workarounds =<br />
These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:<br />
<br />
* JMMS: [https://git.sr.ht/~amindfv/jmms]<br />
* silvermms: [https://gitlab.com/5ilver/silvermms]<br />
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]<br />
<br />
There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.<br />
<br />
= Resources =<br />
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]<br />
<br />
<br />
[[Category:PinePhone]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_APN_Settings&diff=13275PinePhone APN Settings2022-07-10T05:06:04Z<p>KJ7RRV: /* List of tested carriers */ Add Tello</p>
<hr />
<div>The [https://en.wikipedia.org/wiki/Access_Point_Name APN] setting is the gateway between your carrier's cellular network and the '''public Internet'''. The APN setting - if not set automatically by the user's OS - has to be set by the user to enable the use of the mobile Internet on the phone.<br />
<br />
= Setting the APN =<br />
<br />
The location of the APN setting depend on the user interface the distribution is using.<br />
<br />
== Distributions with Phosh ==<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (Arch Linux ARM, PureOS, Debian + Phosh) or <code> Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
<!--== Distributions with Plasma Mobile ==<br />
<br />
Todo--><br />
<br />
= List of tested carriers =<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
== 4ka (Slovakia) ==<br />
Name: 4ka Internet<br />
APN: internet<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.4ka.sk/vitajte/navody-a-nastavenia/detail-navodu<br />
<br />
== AT&T-based ==<br />
<br />
=== AT&T (USA) ===<br />
APN: NXTGENPHONE<br />
MMSC: http://mmsc.mobile.att.net<br />
MMS proxy: proxy.mobile.att.net<br />
<br />
APN: <code>phone</code> may alternatively work. (see <br />
<br />
Source: https://www.att.com/support/article/wireless/KM1218306/<br />
<br />
=== AT&T Mexico (Mexico) ===<br />
<br />
APN: <code> wap.attmex.mx </code><br />
<br />
=== Cricket (USA) ===<br />
APN: <code>phone</code> or <code>ndo</code> or <code>NXTGENPHONE</code><br />
<br />
== Blau.de (Germany) ==<br />
APN: internet.eplus.de<br />
Username: eplus<br />
Password: gprs<br />
<br />
Source: https://www.my-gps.org/412-apn-einstellungen-deutschland<br />
<br />
== Bouygues Telecom (France) ==<br />
Name: Bouygues Telecom<br />
APN: mmsbouygtel.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.assistance.bouyguestelecom.fr/s/article/parametrage-mobile-email-mms-internet<br />
<br />
== Congstar - Telekom Net (Germany) ==<br />
Name: Telekom Internet<br />
APN: internet.telekom<br />
Username: telekom<br />
Password: telekom<br />
<br />
Other settings seem to work, too. [https://forum.congstar.de/Tarife/Tarif-Produktberatung/46325-Mobil-surfen-mit-congstar-manuelle-Einstellungen-zum-mobilen-Internet-APN/ Congstar mentions]<br />
<br />
Name: Congstar Internet<br />
APN: internet.telekom<br />
Username: congstar<br />
Password: cs<br />
<br />
== Eastlink Wireless (Canada) ==<br />
<br />
Name: Eastlink Internet<br />
APN: wisp.mobi.eastlink.ca<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.apnsettings.org/canada/eastlink-ca/<br />
<br />
== Free (France) ==<br />
<br />
Name: Free<br />
APN: free<br />
Username: free<br />
Password: <empty><br />
<br />
Source: https://mobile.free.fr/assistance/46.html<br />
<br />
== Freedom Mobile (Canada) ==<br />
<br />
Name: 1<br />
APN: internet.freedommobile.ca<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Google Fi (USA) ==<br />
<br />
These are settings that Google provides for their "data-only" SIM cards, but also appears to work fine with the normal SIM card for texting and calling. <br />
<br />
Name: Google Fi<br />
APN: h2g2<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://support.google.com/fi/answer/6330195?hl=en<br />
<br />
== Hofer Telekom (Austria) ==<br />
<br />
Name: HoT Internet<br />
APN: webaut<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.hot.at/config/faqs/HoT_Einstellungen_Endgera_te.pdf<br />
<br />
== kölbi (Costa Rica) ==<br />
Name: Costa Rica:Kolbi:Internet<br />
APN: kolbi3g <br />
Username: <empty><br />
Password: <empty><br />
<br />
Note: alternatively <code>kolbi4g</code> also works as APN.<br />
<br />
== Koodo (Canada) == <br />
<br />
Name: Internet/MMS 2<br />
APN: sp.koodo.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.4gapn.com/ca/en/koodo<br />
<br />
== KT (South Korea) ==<br />
<br />
Name: KT LTE<br />
APN: lte.ktfwing.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
Name: KT 3G<br />
APN: alwayson.ktfwing.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
Note: APN automatically detected in Manjaro Phosh. Use either KT LTE or KT 3G according to your subscription.<br />
<br />
== Lebara (UK) ==<br />
Name: Lebara<br />
APN: uk.lebara.mobi<br />
Username: wap<br />
Password: wap<br />
<br />
These settings work on 4G.<br />
<br />
Ignore Default/asdamobiles.co.uk APN if present.<br />
<br />
== Magenta LTE (Austria) ==<br />
<br />
Name: Magenta<br />
APN: internet.t-mobile.at<br />
Username: t-mobile<br />
Password: tm<br />
<br />
Source: https://www.magenta.at/faq/entry/%7Etechnische-anfrage%7Esmartphone%7Efunktionen%26dienste/%7EInternet_APN%7Emaster<br />
<br />
== Mineo (Japan) ==<br />
<br />
Tested with S plan (Softbank) and D plan (Docomo). Mobile LTE data currently working only on Phosh-based OSes, because they use Network Manager and Modem Manager. Ubuntu Touch not working yet, see issue #58. https://gitlab.com/ubports/community-ports/pinephone/-/issues/58<br />
<br />
Name: Mineo<br />
APN: mineo-d.jp<br />
Username: mineo@k-opti.com<br />
Password: mineo<br />
<br />
Source: https://support.mineo.jp/manual/network_setup_d.html<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Call their customer service to activate using the number on their website, or activate on their [https://my.mintmobile.com/activation website]. You may also need to reboot your phone.<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
If the first one doesn't work try this one: <br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: autoconfig on ubports<br />
<br />
== Movistar (Colombia) ==<br />
<br />
Name: Movistar Internet<br />
APN: internet.movistar.com.co<br />
Username: movistar<br />
Password: movistar<br />
<br />
== Orange Telecom (France) ==<br />
Name: Orange Internet<br />
APN: orange<br />
Username: orange<br />
Password: orange<br />
<br />
Source: https://assistance.orange.fr/mobile-tablette/tous-les-mobiles-et-tablettes/depanner/probleme-avec-un-service-d-orange-internet-sms-mms-mails-cloud-tv/mms/configurer-un-apn-internet-et-mms_192948-738196<br />
<br />
== Orange (Poland) ==<br />
Name: Internet IPv4<br />
APN: internet<br />
Username: internet<br />
Password: internet<br />
<br />
Source: https://www.orange.pl/omnibook/konfiguracja-internetu-mms-sms-w-telefonie#<br />
<br />
Note: don't forget to activate sim-card using official android/ios app.<br />
<br />
== Patriot Mobile (USA T-Mobile) ==<br />
Internet<br />
<pre><br />
Name: T-Mobile<br />
APN: Fast.t-mobile.com<br />
Username: <empty><br />
Password: <empty><br />
</pre><br />
MMS (requires chatty v0.6.1 and mmsd-tng v1.8) <br><br />
in /home/alarm/.mms/modemmanager/mms<br />
<pre><br />
[Modem Manager]<br />
CarrierMMSC=http://mms.msg.eng.t-mobile.com/mms/wapenc<br />
MMS_APN=Fast.t-mobile.com<br />
CarrierMMSProxy=NULL<br />
DefaultModemNumber=NULL<br />
AutoProcessOnConnection=true<br />
AutoProcessSMSWAP=true<br />
<br />
[Settings]<br />
UseDeliveryReports=false<br />
TotalMaxAttachmentSize=600000<br />
MaxAttachments=25<br />
AutoCreateSMIL=true<br />
ForceCAres=false<br />
</pre><br />
<br />
Source: https://www.t-mobile.com/support/devices/not-sold-by-t-mobile/byod-t-mobile-data-and-apn-settings<br />
<br />
== Penny Mobil (Germany) ==<br />
<br />
APN settings:<br />
<br />
name: Penny Mobil<br />
APN: internet.t-mobile<br />
username: t-mobile<br />
password: tm<br />
<br />
== Public Mobile (Canada) ==<br />
Internet only, mms not tested.<br />
<br />
Name: Public Mobile<br />
APN: sp.mb.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://productioncommunity.publicmobile.ca/t5/Phones-Hardware/How-do-I-set-up-data-APN-on-my-smartphone/td-p/3<br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Rogers (Canada) ==<br />
<br />
Name: 4G/LTE Rogers Data<br />
APN: ltemobile.apn<br />
Username: <empty><br />
Password: <empty><br />
<br />
Name: 3G Rogers Data<br />
APN: internet.com<br />
Username: wapuser1<br />
Password: wap<br />
<br />
Source: https://communityforums.rogers.com/t5/Wireless-Knowledge-Base/Rogers-APN-Settings/ta-p/410438, <br />
<br />
== Simyo (Spain) ==<br />
<br />
APN settings:<br />
APN: orangeworld<br />
<br />
Source: https://blog.simyo.es/simyo-configuracion-internet-wap-mms/configura-tu-movil/<br />
<br />
== SFR (France) ==<br />
<br />
APN settings:<br />
Name: SFR webphone<br />
APN: sl2sfr<br />
username: <empty><br />
password: <empty><br />
<br />
Source: https://assistance.sfr.fr/tel-mobile/utilisation-param/parametrer-apn-sfr-mobile.html<br />
<br />
== Sunrise (Switzerland) ==<br />
<br />
Name: Sunrise<br />
APN: internet<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Swisscom (Switzerland) ==<br />
<br />
Name: Swisscom<br />
APN: gprs.swisscom.ch<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Tele2 (Sweden) ==<br />
Name: tele2<br />
APN: 4G.tele2.se<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.tele2.se/support/felsokning-guider/tjanster-installningar/mms-och-data<br />
<br />
== Telekom (Germany) ==<br />
<br />
APN settings:<br />
<br />
Name: Telekom<br />
APN: internet.t-mobile<br />
Username: t-mobile<br />
Password: tm<br />
<br />
Source: https://www.telekom.de/hilfe/mobilfunk-mobiles-internet/mobiles-internet-e-mail/apn-mobilfunk/wie-lauten-die-apn-fuer-mobilfunk?samChecked=true<br />
<br />
== Telekom (Hungary) ==<br />
<br />
APN settings:<br />
<br />
Name: Default<br />
APN: internet.telekom<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Telenor (Hungary) ==<br />
<br />
Name: Telenor<br />
APN: online<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://apn.how/hungary/telenor-hungary<br />
<br />
== Telenor (Sweden) ==<br />
<br />
Name: Telenor SE<br />
APN: services.telenor.se<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.telenor.se/kundservice/vanliga-fragor/min-mobil-surfplatta/vad-har-telenor-for-apn-installningar/<br />
<br />
== Telia (Finland) ==<br />
Name: internet<br />
APN: internet<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Tello (USA) ==<br />
<br />
Name: T-Mobile<br />
APN: fast.t-mobile.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
MMS settings:<br />
<br />
MMSC: http://wholesale.mmsmvno.com/mms/wapenc<br />
APN: fast.t-mobile.com<br />
Proxy: <empty><br />
<br />
== Telstra (Australia) ==<br />
<br />
Name: Telstra Internet/WAP<br />
APN: telstra.iph<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Three (UK) ==<br />
<br />
Name: 3<br />
APN: three.co.uk<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Ting (USA) ==<br />
Using the X3 sim card:<br />
Name: Ting Data<br />
APN: wireless.dish.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
For MMS configuration had success using:<br />
MMSC: http://wholesale.mmsmvno.com/mms/wapenc<br />
<br />
The article mentions using this APN for a hotspot, but unconfirmed<br />
Name: Ting Hotspot<br />
APN: tethering.dish.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://help.ting.com/hc/en-us/articles/205428698-APN-setup-guide#android-apn-settings-with-the-x3-sim-card-0-1<br />
<br />
== Tracfone (USA) == <br />
<br />
''BYOP SIM Card Kit'' works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit.<br />
<br />
3G/4G data known to work with Verizon & AT&T SIMs (most likely works for T-Mobile as well).<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
Username: <empty><br />
Password: <empty><br />
<br />
To use Verizon's network:<br />
<br />
Name: Tracfone<br />
APN: TRACFONE.VZWENTP<br />
Username: <empty><br />
Password: <empty><br />
<br />
MMS has worked with the following settings:<br />
<br />
MMSC: http://mmsc.cingular.com<br />
MMS Proxy: proxy.mvno.tracfone.com<br />
<br />
== T-Mobile (Czech Republic) ==<br />
<br />
Name: T-Mobile CZ<br />
APN: internet.t-mobile.cz<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Verizon Contract (USA) ==<br />
<br />
There are several APN names which can be used, for example:<br />
<br />
Name: 4G LTE Contract<br />
APN: vzwinternet<br />
Username: <empty><br />
Password: <empty><br />
<br />
Other APN names which appear, and may work if the above does not:<br />
<br />
vzwapp<br />
vzwims<br />
<br />
== Videotron (Canada) ==<br />
<br />
Name: Videotron<br />
APN: media.ng<br />
Username: free<br />
Password: <empty><br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Vodafone (Czech Republic) ==<br />
Name: internet<br />
APN: internet<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.vodafone.cz/pece/osobni-a-firemni/otazky/zaciname-s-chytrym-telefonem/pripojeni-nastaveni-internetu-v-telefonu/<br />
<br />
== Vodafone (UK) ==<br />
Name: Vodafone<br />
APN: wap.vodafone.co.uk<br />
Username: wap<br />
Password: wap<br />
<br />
These settings work on 4G.<br />
<br />
Ignore Default/asdamobiles.co.uk APN if present.<br />
<br />
== winSIM (Germany) ==<br />
Name: winSIM<br />
APN: internet<br />
Username: <empty><br />
Passwort: <empty><br />
<br />
Source: https://service.winsim.de/help/showGeraeteeinstellungen (Requires login)<br />
<br />
= Carriers that do not work =<br />
<br />
== FreedomPop (USA) ==<br />
VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to '''fp.com.attz'''. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
<br />
APN: <code>fp.com.attz</code><br />
<br />
== Sprint (USA) ==<br />
<br />
Sprint is currently not supported due to unknown issues, see also [[PinePhone Carrier Support#Sprint]]. Any input regarding this issue is highly appreciated. <br />
<br />
APN: <code>cinet.spcs</code><br />
<br />
== Visible (USA) ==<br />
<br />
Visible does not have any way to approve unsupported phones, it might be possible through APN settings, but requires more research and dev time. Even activating a SIM using a supported phone, and then moving it to the Pinephone does not work.<br />
<br />
== Other ==<br />
<br />
Other VoLTE services.<br />
<br />
= External links =<br />
<br />
* See also https://forum.pine64.org/showthread.php?tid=9150<br />
* LineageOS APN and MMS defaults - https://github.com/LineageOS/android_vendor_lineage/blob/lineage-19.1/prebuilt/common/etc/apns-conf.xml<br />
<br />
<br />
[[Category:PinePhone]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=12183PinePhone Software Releases2022-01-06T21:15:03Z<p>KJ7RRV: </p>
<hr />
<div>This page contains a list of all available OS releases for the [[PinePhone]], as well as links to other resources.<br />
<br />
See [[PinePhone Installation Instructions]] on how to install the operating systems.<br><br />
However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]].<br />
<br />
{{Hint| '''Note:''' Some releases may not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}<br />
<br />
= Software Releases =<br />
<br />
This is a list of OSes that specifically support the PinePhone.<br />
Since PinePhone support is included in Mainline Linux, in principle, any ARM Linux OS can be used if possible required patches are included.<br />
<br />
== DanctNIX (Arch Linux ARM) ==<br />
[[File:Archlinux-logo.png|right|100px]]<br />
<br />
(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, sxmo or barebones.<br />
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).<br />
<br />
* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]<br />
<br />
'''Download location'''<br />
<br />
Get both stable and test builds at [https://github.com/dreemurrs-embedded/Pine64-Arch/releases GitHub releases].<br />
<br />
'''username/password'''<br />
<br />
{| class="wikitable"<br />
! Default user<br />
| <code>alarm/123456</code><br />
|-<br />
! root<br />
| <code>root/root</code><br />
|}<br />
<br />
'''What works, what does not work'''<br />
<br />
Most of the things should works<br />
<br />
'''How to contribute and report defects'''<br />
<br />
There are archmobile chat rooms on Matrix ([https://matrix.to/#/#archmobile:kde.org #archmobile:kde.org]) and Telegram ([https://t.me/archmobile @archmobile]).<br />
You may find the Discord, Matrix and Telegram of DanctNIX community at [https://github.com/DanctNIX/danctnix/blob/master/README.md#channel-list the Channel list section of DanctNIX/README.md], read the [https://github.com/DanctNIX/danctnix/blob/master/docs/CODE_OF_CONDUCT.md Code of Conduct].<br />
<br />
Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].<br />
<br />
== ExpidusOS ==<br />
<br />
A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].<br />
<br />
* [https://expidusos.com ExpidusOS official website]<br />
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]<br />
* [https://discord.gg/GVfBF2w Midstall Software Discord server]<br />
* GitHub: [https://github.com/ExpidusOS ExpidusOS]<br />
<br />
'''Download location'''<br />
<br />
Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".<br />
<br />
'''username/password'''<br />
<br />
expidus/expidus<br />
<br />
'''What works, what does not work'''<br />
<br />
The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).<br />
<br />
== Fedora ==<br />
[[File:Fedora-logo.png|right|100px]]<br />
<br />
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.<br />
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]<br />
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]<br />
<br />
'''Download location'''<br />
<br />
* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]<br />
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]<br />
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]<br />
<br />
There is also an FTP server with images build every night @ ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)<br />
<br />
'''username/password'''<br />
<br />
On github images use:<br />
pine/123456<br />
<br />
On Nightly images from FTP use<br />
pine/1111<br />
<br />
'''What works, what does not work'''<br />
<br />
WiFi, Bluetooth, SMS, Data, Calls all work!<br />
<br />
There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker].<br />
Be sure to include logs if applicable!<br />
Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].<br />
<br />
<br />
<br />
== Gentoo ==<br />
[[File:GentooLogo.png|right|100px]]<br />
<br />
{{hint|Please consider cross-compiling the software on the computer.<br />
Long compilation times and heat production can lead to a reduced lifespan of the phone.}}<br />
<br />
There are unofficial Gentoo overlays with ebuilds for the PinePhone.<br />
There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.<br />
You will be using the arm64 version of Gentoo.<br />
<br />
'''Documentation'''<br />
<br />
* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone<br />
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone<br />
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)<br />
<br />
'''Overlay locations'''<br />
<br />
* https://gitlab.com/bingch/gentoo-overlay<br />
* https://github.com/stealthgun/gjdwebserver-overlay<br />
<br />
== GloDroid ==<br />
<br />
{{Hint|There can be large intervals between release update, so available images may be outdated and do not reflect the state of the current developments.}}<br />
<br />
A fully open source port of Android to the PinePhone.<br />
<br />
GitHub: [https://github.com/GloDroid/ GloDroid]<br />
<br />
'''Download location'''<br />
<br />
Stable image (last release at 2021-11-25)<br />
<br />
[https://github.com/GloDroid/glodroid_manifest/releases GloDroid]<br />
<br />
'''What works, what does not work'''<br />
<br />
Works: WiFi, screen dimming, touchscreen and charging work.<br />
Don't work: Bluetooth, Telephony, GPS, Sound<br />
<br />
== LuneOS ==<br />
[[File:WebOS-Ports-logo.png|right|100px]]<br />
<br />
LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by the WebOS Ports community.<br />
<br />
* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]<br />
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]<br />
* GitHub: [https://github.com/webOS-ports WebOS Ports]<br />
<br />
'''Download location'''<br />
<br />
* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
<br />
It is recommended to use ''bmaptool'', which is faster than dd, and can decompress archived image files on-the-fly.<br />
<br />
Syntax is:<br />
<br />
bmaptool copy [from] [to]<br />
<br />
For example:<br />
<br />
bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-177.rootfs.wic.gz /dev/mmcblk0<br />
<br />
.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require file extension to be .img.<br />
<br />
== Maemo Leste ==<br />
[[File:Maemoleste-logo.png|right|100px]]<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,<br />
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it.<br />
The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.<br />
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].<br />
The current version is Devuan Beowulf (Debian Buster) and has simultaneous support for both Devuan and Debian.<br />
<br />
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].<br />
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 build]).<br />
Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
* [https://maemo-leste.github.io/ Maemo Leste website]<br />
* [https://leste.maemo.org/Main_Page Maemo Leste Wiki]<br />
** [https://leste.maemo.org/PinePhone PinePhone wiki page]<br />
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]<br />
* GitHub: [https://github.com/maemo-leste maemo-leste]<br />
* Twitter: [https://twitter.com/maemoleste @maemoleste]<br />
<br />
'''Download location'''<br />
<br />
[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].<br />
<br />
'''username/password'''<br />
<br />
root/toor<br />
<br />
You may use <code>sudo</code> directly.<br />
<br />
'''What works, what does not work'''<br />
<br />
For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>].<br />
The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.<br />
<br />
Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.<br />
To track known issues, you may use these search terms:<br />
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],<br />
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].<br />
<br />
Learn about<br />
[https://leste.maemo.org/Development development],<br />
[https://leste.maemo.org/Development/Porting_Packages porting packages],<br />
[https://leste.maemo.org/Development/Building_Packages building packages],<br />
[https://leste.maemo.org/Development/Tasks todo list],<br />
and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian].<br />
Some tasks have funding available.<br />
<br />
== Manjaro ARM ==<br />
[[File:Manjaro-logo.svg|right|100px]]<br />
<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
'''Download location'''<br />
<br />
* Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]<br />
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]<br />
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)<br />
<br />
'''username/password'''<br />
<br />
{| class="wikitable"<br />
! Default user<br />
| <code>manjaro/123456</code><br />
|-<br />
! root<br />
| <code>root/root</code><br />
|}<br />
<br />
'''What works, what does not work'''<br />
<br />
{{Hint| '''Note:''' At the first boot, the Phosh image will be loaded at a TTY login prompt for multiple minutes.}}<br />
<br />
See Manjaro's release announcements on their forum.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].<br />
<br />
== Mobian ==<br />
[[File:Debian-logo.png|right|100px]]<br />
<br />
An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).<br />
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).<br />
Current version is Debian Bookworm.<br />
<br />
'''Download location'''<br />
<br />
[https://images.mobian-project.org/pinephone/weekly/ Weekly] /<br />
[https://images.mobian-project.org/pinephone/installer/ Installer] /<br />
[https://images.mobian-project.org/pinephone/ Stable]<br />
<br />
Extract the image before installing:<br />
<br />
$ gzip -d Downloads/mobian-pinephone-*.img.gz<br />
<br />
See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.<br />
<br />
'''username/password'''<br />
<br />
mobian/1234<br />
<br />
'''What works, what does not work'''<br />
<br />
See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki] for most up to date status.<br />
<br />
Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker].<br />
As a general rule, issues with third-party apps (even the default ones) should be reported upstream.<br />
A Mobian issue would be related to getting the hardware to work on the PinePhone, <br />
but if unsure where the issue should be reported just open a ticket or ask.<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].<br />
<br />
'''Notes'''<br />
<br />
See [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.<br />
<br />
== Multi-distro demo image ==<br />
<br />
{{Warning | This is a demo image for testing different OSes before installing a regular image. Attempting to use this image productively is highly discouraged. The kernel is shared across the different OSes and is not updated.}}<br />
<br />
This image allow users to try many of the above Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.<br />
<br />
* Main page: https://xnux.eu/p-boot-demo/<br />
* Git repo: https://megous.com/git/pinephone-multi-boot/<br />
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)]<br />
<br />
'''Update 2021-06-02, using megi's kernel 5.13-rc4'''<br />
<br />
DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.<br />
<br />
This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.<br />
<br />
For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].<br />
<br />
* [http://dl.xnux.eu/p-boot-multi-2021-06-02.torrent Download torrent file from author's website]<br />
* [http://dl.xnux.eu/p-boot-multi-2021-06-02/ Download img.zst from author's website] (speed limited to 512KiB/s)<br />
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]<br />
** '''File name:''' multi.img.zst<br />
** '''SHA-256:''' <span style="word-break: break-all">9b099cdfece3ba862348ca32af6c51a41a1d161b1d897f9928ae8be3c824a0b6</span><br />
** '''File Size:''' 6.57GiB<br />
<br />
* [https://files.pine64.org/os/PinePhone/Multi/p-boot-multi-2021-06-02.img.gz Direct download img.gz from pine64.org] (re-zipped from zstd to gzip)<br />
** '''File name:''' p-boot-multi-2021-06-02.img.gz<br />
** '''MD5:''' 2abdaafb01dd7519f678b5a7c6538493<br />
** '''File Size:''' 6.8GB<br />
<br />
Due to its size, download though torrent is suggested by the author on its main page.<br />
<br />
{{hint | '''Note about .zst archive file:'''<br />
<br />
On Linux, you may install or compile <code>zstd</code>, and write the image to SD card by using <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.<br />
<br />
On Windows, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd], it provides different installation method in the README.md.Install and extract the .img file from the zst archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].}}<br />
<br />
Also see [[PinePhone Installation Instructions]].<br />
<br />
'''username/password'''<br />
<br />
All passwords, including root passwords, are <code>1111</code>.<br />
sxmo username is <code>user</code>.<br />
<br />
== Nemo Mobile ==<br />
[[File:nemo_mobile.png|right|100px]]<br />
<br />
Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].<br />
<br />
* Website: [https://nemomobile.net/ Nemo Mobile UX team]<br />
* [https://wiki.merproject.org/wiki/Nemo Mer Wiki page]<br />
<br />
'''Download location'''<br />
<br />
See the [https://nemomobile.net/installation/ installation page] on their website for the newest release and installation guides.<br />
<br />
'''What works, what does not work''' <br />
<br />
Development is now moving very fast after rebasing. For the current devel image, Wifi, SMS and Bluetooth works.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
For the Nemo Mobile UX itself:<br />
* GitHub issues: https://github.com/nemomobile-ux/main/issues<br />
<br />
For hardware:<br />
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues<br />
<br />
== NixOS ==<br />
[[File:nixos.png|right|100px]]<br />
<br />
NixOS support is handled through the Mobile NixOS project.<br />
<br />
* Project home page: [https://mobile.nixos.org/ Mobile NixOS]<br />
* PinePhone device page: [https://mobile.nixos.org/devices/pine64-pinephone.html Pine64 PinePhone — Mobile NixOS]<br />
* GitHub: [https://github.com/NixOS/mobile-nixos NixOS/mobile-nixos]<br />
<br />
There is no pre-built complete image.<br />
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],<br />
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].<br />
<br />
'''What works, what does not work'''<br />
<br />
Currently, it boots, it's just as compatible as the Android-based devices are with Mobile NixOS.<br />
It even supports a bit more since it can use WiFi.<br />
<br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository].<br />
Please specify that you are using a PinePhone when reporting issues.<br />
Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].<br />
<br />
== OpenMandriva Lx ==<br />
[[File:Oma-logo-22042013_300pp.png|right|100px]]<br />
<br />
{{Hint| '''Note:''' This image is solely for testing purposes.}}<br />
<br />
OpenMandriva Lx with Plasma Mobile as UI.<br />
<br />
'''Download location'''<br />
<br />
The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].<br />
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.<br />
<br />
'''What works, what does not work'''<br />
<br />
From the [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing 4.3 announcement],<br />
in future updates (4.3 and later), "Phone calls are working, and we have rewritten the camera app to be far more useful".<br />
<br />
== openSUSE ==<br />
[[File:SLEM-OS-logo.png|right|100px]]<br />
<br />
Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,<br />
except what needs to be changed for the PinePhone.<br />
The images include <i>zypper</i> (RPM) as the default package manager,<br />
and have access to virtually the same (open source) software as our desktop repositories,<br />
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.<br />
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.<br />
<br />
'''Download links'''<br />
<br />
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]<br />
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]<br />
<br />
To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].<br />
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.<br />
<br />
You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.<br />
<br />
'''Username/Password'''<br />
<br />
The login credentials are pine/1234 and root/linux.<br />
Change (or disable) the root password once you are set up.<br />
<br />
'''What works and what does not work'''<br />
<br />
You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].<br />
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].<br />
You will also find information in our wiki on how to report issues (Contributing section).<br />
<br />
== postmarketOS ==<br />
[[File:PostmarketOS-logo.png|right|100px]]<br />
<br />
postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.<br />
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).<br />
<br />
As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.<br />
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.<br />
<br />
When using the installer images (recommended), it is possible to:<br />
* encrypt the installation<br />
* install from the SD card to eMMC<br />
<br />
Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.<br />
<br />
Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.<br />
<br />
'''Download location'''<br />
<br />
* [https://postmarketos.org/download/ Download page]<br />
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]<br />
<br />
'''Username/password'''<br />
<br />
* Test images: user/147147<br />
* When using the installer images or building an image with pmbootstrap, you set your own username and password.<br />
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.<br />
<br />
'''What works, what does not work'''<br />
<br />
See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support.<br />
See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.<br />
<br />
== PureOS ==<br />
[[File:Pureos.png|right|100px]]<br />
<br />
{{Warning|This project is no longer under development and has been abandoned. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian Mobian] instead}}<br />
<br />
{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}<br />
<br />
[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.<br />
<br />
* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there<br />
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]<br />
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS<br />
<br />
'''Download location'''<br />
<br />
Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.<br />
<br />
Also see:<br />
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]<br />
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi<br />
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone<br />
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com<br />
<br />
== Sailfish OS ==<br />
[[File:Sailfish_logo.png|right|100px]]<br />
<br />
[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].<br />
<br />
* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.<br />
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]<br />
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]<br />
<br />
'''Download location'''<br />
<br />
'''Flashing script'''<br />
<br />
The Sailfish OS 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].<br />
<br />
The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.<br />
Note: The script will format and erase the SD card!<br />
<br />
Instructions:<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc. <br />
<br />
'''username/password'''<br />
<br />
Set PIN on initialization.<br />
<br />
* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.<br />
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''<br />
* When a screen with a loading circle is displayed, just left/right swipe it away.<br />
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.<br />
<br />
'''What works, what does not work'''<br />
<br />
See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.<br />
<br />
There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.<br />
<br />
Git repo links are at the top of this OS section. other repos that may be helpful:<br />
<br />
* [https://github.com/sailfish-on-dontbeevil GitHub project page]<br />
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]<br />
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)<br />
<br />
See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.<br />
<br />
'''Notes'''<br />
<br />
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.<br />
== Slackware ==<br />
<br />
Unofficial slackware images with xfce for the pinephone<br />
<br />
Discussion thread: [https://forum.pine64.org/showthread.php?tid=12181&highlight=slackware+pinephone Thread]<br />
<br />
Download link: http://dl.fail.pp.ua/slackware/images/pinephone/<br />
== SkiffOS ==<br />
[[File:SkiffOS-Icon-1.png|right|100px]]<br />
<br />
Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.<br />
<br />
Provides the reliability of firmware with the ease-of-use of package managers.<br />
<br />
Upgrade over-the-air via a simple rsync script, or copying 3 files.<br />
<br />
Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.<br />
<br />
Use configuration packages to configure distro:<br />
<br />
{| class="wikitable"<br />
! Package !! Distro<br />
|-<br />
| core/pinephone_neon || KDE Neon via Ubuntu repositories<br />
|-<br />
| core/pinephone_nixos || Nixos Mobile<br />
|-<br />
| core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh<br />
|-<br />
| core/pinephone_ubports || Ubuntu Ports for PinePhone<br />
|-<br />
| core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant<br />
|-<br />
| core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant<br />
|-<br />
| core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant<br />
|}<br />
<br />
The boot-up OS is upgraded independently from the containers.<br />
<br />
'''Download location'''<br />
<br />
The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].<br />
<br />
== Sxmo ==<br />
<br />
A collection of Suckless programs to create a mobile UI. Based on postmarketOS.<br />
<br />
'''Download location'''<br />
<br />
Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the ''/pine64-pinephone/sxmo/'' sections respectively).<br />
<br />
'''username/password'''<br />
<br />
user/147147<br />
<br />
'''How to contribute and report defects'''<br />
<br />
Contributing information is listed [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].<br />
<br />
== Ubuntu Touch ==<br />
[[File:Ubports-logo.png|right|100px]]<br />
<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.<br />
Installation instructions can be found on<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].<br />
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.<br />
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.<br />
<br />
'''Download location'''<br />
<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]<br />
<br />
'''username/password'''<br />
<br />
Set up during boot<br />
<br />
'''What works, what does not work'''<br />
<br />
Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page], or directly here [https://devices.ubuntu-touch.io/device/pinephone/#deviceOverview]<br />
<br />
'''How to contribute and report defects'''<br />
<br />
See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].<br />
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.<br />
<br />
= Tools =<br />
<br />
There are software tools, that can be booted on the PinePhone.<br />
<br />
== JumpDrive ==<br />
<br />
JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].<br />
<br />
See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.<br />
Make sure to download the "PinePhone" image and to unpack the archive before flashing.<br />
<br />
= Factory Test OS =<br />
<br />
{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}<br />
<br />
On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.<br />
The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later.<br />
Since the 20200501 version, it is able to test all the hardware.<br />
It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image.<br />
The downloadable image just does the hardware tests.<br />
Do not flash eMMC to test your device, just dd it to microSD and test from there.<br />
New versions are distributed as part of the postmarketOS distribution.<br />
<br />
Links:<br />
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)<br />
* [https://gitlab.com/MartijnBraam/factorytest Git repo]<br />
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]<br />
<br />
== Factory-loaded OS builds ==<br />
<br />
These are different operating system builds that was preloaded in the factory with testing utility.<br />
<br />
Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.<br />
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.<br />
<br />
All the download links below are direct download from pine64.org.<br />
<br />
<div style="overflow: auto;"><br />
{| class="wikitable" style="white-space: nowrap"<br />
! OS<br />
! Download Link<br />
! File Size<br />
! MD5<br />
|-<br />
| Beta Edition<br />
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]<br />
| 1.78GB<br />
| <code>f16bce93504a52217540ac886863a418</code><br />
|-<br />
| Mobian<br />
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]<br />
| 1.41GB<br />
| <code>015be381ff4e650a7fca6d4eaa90d63d</code><br />
|-<br />
| KDE<br />
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]<br />
| 2.28GB<br />
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code><br />
|-<br />
| Manjaro<br />
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]<br />
| 1.04GB<br />
| <code>4edfd4dceaefdd32a3417c1727161c29</code><br />
|-<br />
| postmarketOS<br />
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]<br />
| 517MB<br />
| <code>244093be2f6d728fcbd1d29114607727</code><br />
|-<br />
| Ubuntu Touch<br />
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]<br />
| 1.05GB<br />
| <code>2d7f5271e7a281db8f1b1219bedbe131</code><br />
|}<br />
</div><br />
<br />
= Installing other ARM64 distributions =<br />
<br />
{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.<br />
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}<br />
<br />
{{Hint|'''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.}}<br />
<br />
General steps:<br />
<br />
# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.<br />
# 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 instead (in archive mode, like <code>rsync -ar</code>).<br />
# Edit <code>/etc/fstab</code> to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.<br />
<br />
If you would like to see examples or specific commands for how to complete these steps, see:<br />
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release<br />
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi<br />
<br />
= Other Resources =<br />
Community<br />
* [[Main_Page#Community_and_Support|Links to the community services]]<br />
<br />
Hardware information<br />
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki<br />
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]<br />
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]<br />
* 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]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://pine64.com/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [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]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]<br />
<br />
[[Category:PinePhone]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_Pro&diff=12114PinePhone Pro2021-12-25T18:57:59Z<p>KJ7RRV: /* Editions and revisions */ Fix links</p>
<hr />
<div>[[File:Pinephone_double.png|400px|thumb|right|Rendering of the PinePhone Pro]]<br />
<br />
The '''PinePhone Pro''' is <i>PINE64</i>'s flagship smartphone announced on October 15, 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC, which is a specialized version of the RK3399 made specifically for the PinePhone Pro.<br />
<br />
== Introduction ==<br />
<br />
The PinePhone Pro is PINE64’s second Linux-only smartphone and a successor to the original PinePhone. It does not, however, replace the original PinePhone. It should also not be considered a second generation PinePhone; it is a higher-end device, with much better specs, aimed at those who wish to daily-drive a fully open Linux Stack. Achieving this goal will, however, take time as the software and overall Linux smartphone ecosystem needs to mature.<br />
<br />
More information about the PinePhone Pro can be found on the device [https://www.pine64.org/pinephonepro/ main page].<br />
<br />
=== State of the software ===<br />
<br />
Presently, at the time of writing (late 2021), the PinePhone Pro is aimed solely at early adopters and developers. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile Linux, in more general, to reach a higher degree of maturity.<br />
<br />
Bear in mind that the software for Linux smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.<br />
<br />
If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the community chat (see [[Main Page#Community and Support]])!<br />
<br />
=== Editions and revisions ===<br />
Similarly to the original PinePhone, various PinePhone Pro editions are planned, the first of which is the Developer Edition (aimed at developers, as the name entails) followed by the Explorer Edition, which is aimed at early adopters.<br />
<br />
* [[PinePhone Pro Developer Edition]]<br />
* [[PinePhone Pro Explorer Edition]]<br />
<br />
=== Help and support ===<br />
<br />
Still have any questions regarding software, shipping, or ordering after reading this Wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].<br />
<br />
Please keep in mind that PINE64 is not like a regular company (see [https://www.pine64.org/philosophy/ PINE64 philosophy]), and currently that support resources are sparse - the best way to get support quickly is to ask in the community chat! Please only contact PINE64 directly if questions couldn't be solved via the community chat or this wiki.<br />
<br />
== First time setup ==<br />
<br />
{{Hint|Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.}}<br />
<br />
When shipped the battery is isolated from the mainboard contacts using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge until it is removed and some of the device’s functionality may not function properly.<br />
<br />
The PinePhone Pro's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Notice: Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins. An adapter from a nano to a micro SIM is included in the box.<br />
<br />
To remove the sticker after unboxing the phone:<br />
<br />
# Carefully remove the back panel using the notch in the corner of the back cover without overbending it<br />
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)<br />
# Peel off the clear plastic sticker below it, which isolates the charging contacts<br />
# Reinsert the battery<br />
<br />
<gallery mode="nolines" widths="400px" heights="400px"><br />
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.<br />
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.<br />
</gallery><br />
<br />
== Software ==<br />
<br />
At the time of the release, in late 2021, the PinePhone Pro is in an early development stage. That said, the device has benefited greatly from work done on the original PinePhone, which means that even early development images feature all core functionality, such as: functional UI, sensors and even the modem (to a degree).<br />
<br />
The development is expected to proceed very quickly compared to progress done on the original PinePhone as much of the fundamental work can carry over to the new device.<br />
You can follow development efforts on [https://xnux.eu/log/ Megi's blog], the dedicated [[PinePhone Pro Development]] section as well as on individual project’s Wiki’s and repositories.<br />
<br />
=== Boot order ===<br />
<br />
On the PinePhone Pro the eMMC (the internal storage of the phone) has a higher boot priority than the microSD card (see [[RK3399 boot sequence#Boot sequence details]] for details regarding the boot sequence). That behavior is in contrast to the original PinePhone with the Allwinner A64 SoC, where the microSD card has a higher boot priority.<br />
<br />
What this means: For the PinePhone Pro this means, that inserting a flashed microSD card to boot a new installation is not sufficient to boot a microSD card if there is already a valid installation of a bootloader on the eMMC present. The boot order behavior can be altered non-permanently by various way, for example by either not having a bootloader installed to the eMMC or by pointing the bootloader installed on the eMMC to the installation on the microSD card.<br />
<br />
=== Installation instructions ===<br />
<br />
Due to the above explained [[PinePhone Pro#Boot order|boot order]] of the PinePhone Pro, the eMMC has a higher boot priority than the microSD card and the user has to consider this behavior. This means that you cannot boot from a SD card with an OS present on the device's eMMC.<br />
<br />
{{Template:note|If you ordered a '''PinePhone Pro Developer Edition''' intended for developing and coming with an Android factory OS preinstalled, please see [[PinePhone Pro Developer Edition#Nuking the factory AOSP installation]] to learn how to remove the bootloader and the preinstalled OS of the eMMC, to be able to boot and test operating systems from the microSD card easily.<br />
}}<br />
<br />
That said, booting from SD can be achieved using a modified u-boot (or a different bootloader) on eMMC, which seeks out a bootable partition on SD first. At the time of writing, this hasn’t been achieved yet but is a planned feature.<br />
<br />
It is strongly recommended you perform all testing from a SD card, leaving the eMMC vacant.<br />
<br />
=== Software releases ===<br />
<br />
The [[PinePhone Pro Software Releases]] page has a complete list of currently supported phone-optimized operating system images that work with the PinePhone Pro.<br />
<br />
== Specifications ==<br />
<br />
* '''Dimensions:''' 160.8 x 76.6 x 11.1mm<br />
* '''Weight:''' Approx. 220g<br />
* '''SIM Card:''' Micro-SIM<br />
* '''Display:'''<br />
** '''Size:''' 6 inches (151mm) diagonal<br />
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™<br />
** '''Resolution:''' 1440x720, 18:9 ratio<br />
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz<br />
* '''RAM:''' 4GB LPDDR4 @ 800MHz<br />
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC<br />
* '''Back [[#Camera|Camera]]:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash<br />
* '''Front Camera:''' 8MP, OmniVision OV8858 front-facing camera<br />
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)<br />
* '''Communication:'''<br />
** '''[[#Modem|Modem]]:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]<br />
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28<br />
** '''LTE-TDD''': B38, B39, B40, B41<br />
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19<br />
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)<br />
** '''WLAN & Bluetooth:''' AMPAK AP6255 WiFi 11ac + Bluetooth V4.1<br />
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS<br />
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass<br />
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras<br />
* '''[[#Battery|Battery]]:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)<br />
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification<br />
<br />
== Privacy switch configuration ==<br />
<br />
[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]<br />
<br />
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.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Number<br />
! Name<br />
! Description<br />
|-<br />
| 1<br />
| Modem<br />
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.<br />
|-<br />
| 2<br />
| WiFi / Bluetooth<br />
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.<br />
|-<br />
| 3<br />
| Microphone<br />
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.<br />
|-<br />
| 4<br />
| Rear camera<br />
| "On" enables the rear camera, "off" disables it.<br />
|-<br />
| 5<br />
| Front camera<br />
| "On" enables the front camera, "off" disables it.<br />
|-<br />
| 6<br />
| Headphone<br />
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART mode. NOTE: The buad rate may be 1500000 instead of 115200.<br />
|}<br />
<br />
== Components ==<br />
<br />
{| class="wikitable"<br />
! Component<br />
! Model<br />
|-<br />
| Touchscreen<br />
| <br />
|-<br />
| Rear camera<br />
| <br />
|-<br />
| Camera flash<br />
| <br />
|-<br />
| Front camera<br />
| <br />
|-<br />
| LCD<br />
| <br />
|-<br />
| WiFi<br />
| <br />
|-<br />
| Bluetooth<br />
| <br />
|-<br />
| Modem<br />
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]<br />
|-<br />
| GNSS/GPS<br />
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]<br />
|-<br />
| Magnetometer<br />
| <br />
|-<br />
| Ambient light / Proximity<br />
| <br />
|-<br />
| Accelerometer / Gyroscope<br />
| <br />
|-<br />
| Vibration motor<br />
| <br />
|-<br />
| Notification LED<br />
| <br />
|-<br />
| Volume buttons<br />
| Buttons connected to the KEYADC<br />
|-<br />
| Power button<br />
| <br />
|-<br />
| Battery fuel gauge<br />
| <br />
|}<br />
<br />
== Datasheets, schematics and certifications ==<br />
<br />
== Press ==<br />
<br />
For an overview about media of the PinePhone Pro you can use for the news, blogs, or similar see [[PinePhone Pro Press]].<br />
<br />
== External links ==<br />
* [https://www.pine64.org/pinephonepro/ Product Page]<br />
* [https://www.youtube.com/watch?v=wP2-6Z74W44 Announcement video]<br />
* [https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blog post] with the announcement<br />
<br />
[[Category:PinePhone Pro]][[Category:Rockchip RK3399]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=12113PinePhone Software Releases2021-12-25T18:42:25Z<p>KJ7RRV: Improve grammar</p>
<hr />
<div>This page contains a list of all available OS releases for the [[PinePhone]], as well as links to other resources.<br />
<br />
See [[PinePhone Installation Instructions]] on how to install the operating systems.<br><br />
However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]].<br />
<br />
{{Hint| '''Note:''' Some releases may not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}<br />
<br />
= Software Releases =<br />
<br />
This is a list of OSes that specifically support the PinePhone.<br />
Since PinePhone support is included in Mainline Linux, in principle, any ARM Linux OS can be used if possible required patches are included.<br />
<br />
== Arch Linux ARM ==<br />
[[File:Archlinux-logo.png|right|100px]]<br />
<br />
(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, sxmo or barebones.<br />
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).<br />
<br />
* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]<br />
<br />
'''Download location'''<br />
<br />
Get both stable and test builds at [https://github.com/dreemurrs-embedded/Pine64-Arch/releases GitHub releases].<br />
<br />
'''username/password'''<br />
<br />
{| class="wikitable"<br />
! Default user<br />
| <code>alarm/123456</code><br />
|-<br />
! root<br />
| <code>root/root</code><br />
|}<br />
<br />
'''What works, what does not work'''<br />
<br />
Most of the things should works<br />
<br />
'''How to contribute and report defects'''<br />
<br />
There are archmobile chat rooms on Matrix ([https://matrix.to/#/#archmobile:kde.org #archmobile:kde.org]) and Telegram ([https://t.me/archmobile @archmobile]).<br />
You may find the Discord, Matrix and Telegram of DanctNIX community at [https://github.com/DanctNIX/danctnix/blob/master/README.md#channel-list the Channel list section of DanctNIX/README.md], read the [https://github.com/DanctNIX/danctnix/blob/master/docs/CODE_OF_CONDUCT.md Code of Conduct].<br />
<br />
Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].<br />
<br />
== ExpidusOS ==<br />
<br />
A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].<br />
<br />
* [https://expidusos.com ExpidusOS official website]<br />
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]<br />
* [https://discord.gg/GVfBF2w Midstall Software Discord server]<br />
* GitHub: [https://github.com/ExpidusOS ExpidusOS]<br />
<br />
'''Download location'''<br />
<br />
Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".<br />
<br />
'''username/password'''<br />
<br />
expidus/expidus<br />
<br />
'''What works, what does not work'''<br />
<br />
The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).<br />
<br />
== Fedora ==<br />
[[File:Fedora-logo.png|right|100px]]<br />
<br />
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.<br />
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]<br />
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]<br />
<br />
'''Download location'''<br />
<br />
* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]<br />
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]<br />
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]<br />
<br />
There is also an FTP server with images build every night @ ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)<br />
<br />
'''username/password'''<br />
<br />
On github images use:<br />
pine/123456<br />
<br />
On Nightly images from FTP use<br />
pine/1111<br />
<br />
'''What works, what does not work'''<br />
<br />
WiFi, Bluetooth, SMS, Data, Calls all work!<br />
<br />
There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker].<br />
Be sure to include logs if applicable!<br />
Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].<br />
<br />
<br />
<br />
== Gentoo ==<br />
[[File:GentooLogo.png|right|100px]]<br />
<br />
{{hint|Please consider cross-compiling the software on the computer.<br />
Long compilation times and heat production can lead to a reduced lifespan of the phone.}}<br />
<br />
There are unofficial Gentoo overlays with ebuilds for the PinePhone.<br />
There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.<br />
You will be using the arm64 version of Gentoo.<br />
<br />
'''Documentation'''<br />
<br />
* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone<br />
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone<br />
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)<br />
<br />
'''Overlay locations'''<br />
<br />
* https://gitlab.com/bingch/gentoo-overlay<br />
* https://github.com/stealthgun/gjdwebserver-overlay<br />
<br />
== GloDroid ==<br />
<br />
{{Hint|There can be large intervals between release update, so available images may be outdated and do not reflect the state of the current developments.}}<br />
<br />
A fully open source port of Android to the PinePhone.<br />
<br />
GitHub: [https://github.com/GloDroid/ GloDroid]<br />
<br />
'''Download location'''<br />
<br />
Stable image (last release at 2021-11-25)<br />
<br />
[https://github.com/GloDroid/glodroid_manifest/releases GloDroid]<br />
<br />
'''What works, what does not work'''<br />
<br />
Works: WiFi, screen dimming, touchscreen and charging work.<br />
Don't work: Bluetooth, Telephony, GPS, Sound<br />
<br />
== LuneOS ==<br />
[[File:WebOS-Ports-logo.png|right|100px]]<br />
<br />
LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by the WebOS Ports community.<br />
<br />
* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]<br />
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]<br />
* GitHub: [https://github.com/webOS-ports WebOS Ports]<br />
<br />
'''Download location'''<br />
<br />
* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
<br />
It is recommended to use ''bmaptool'', which is faster than dd, and can decompress archived image files on-the-fly.<br />
<br />
Syntax is:<br />
<br />
bmaptool copy [from] [to]<br />
<br />
For example:<br />
<br />
bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-177.rootfs.wic.gz /dev/mmcblk0<br />
<br />
.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require file extension to be .img.<br />
<br />
== Maemo Leste ==<br />
[[File:Maemoleste-logo.png|right|100px]]<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,<br />
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it.<br />
The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.<br />
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].<br />
The current version is Devuan Beowulf (Debian Buster) and has simultaneous support for both Devuan and Debian.<br />
<br />
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].<br />
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 build]).<br />
Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
* [https://maemo-leste.github.io/ Maemo Leste website]<br />
* [https://leste.maemo.org/Main_Page Maemo Leste Wiki]<br />
** [https://leste.maemo.org/PinePhone PinePhone wiki page]<br />
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]<br />
* GitHub: [https://github.com/maemo-leste maemo-leste]<br />
* Twitter: [https://twitter.com/maemoleste @maemoleste]<br />
<br />
'''Download location'''<br />
<br />
[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].<br />
<br />
'''username/password'''<br />
<br />
root/toor<br />
<br />
You may use <code>sudo</code> directly.<br />
<br />
'''What works, what does not work'''<br />
<br />
For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>].<br />
The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.<br />
<br />
Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.<br />
To track known issues, you may use these search terms:<br />
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],<br />
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].<br />
<br />
Learn about<br />
[https://leste.maemo.org/Development development],<br />
[https://leste.maemo.org/Development/Porting_Packages porting packages],<br />
[https://leste.maemo.org/Development/Building_Packages building packages],<br />
[https://leste.maemo.org/Development/Tasks todo list],<br />
and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian].<br />
Some tasks have funding available.<br />
<br />
== Manjaro ARM ==<br />
[[File:Manjaro-logo.svg|right|100px]]<br />
<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
'''Download location'''<br />
<br />
* Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]<br />
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]<br />
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)<br />
<br />
'''username/password'''<br />
<br />
{| class="wikitable"<br />
! Default user<br />
| <code>manjaro/123456</code><br />
|-<br />
! root<br />
| <code>root/root</code><br />
|}<br />
<br />
'''What works, what does not work'''<br />
<br />
{{Hint| '''Note:''' At the first boot, the Phosh image will be loaded at a TTY login prompt for multiple minutes.}}<br />
<br />
See Manjaro's release announcements on their forum.<br />
Recent ones:<br />
[https://forum.manjaro.org/t/manjaro-arm-beta-17-with-phosh-pinephone/86898 Phosh],<br />
[https://forum.manjaro.org/t/manjaro-arm-beta7-with-plasma-mobile-pinephone/81679 Plasma] and<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha3-with-lomiri-pinephone/49923 Lomiri].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].<br />
<br />
== Mobian ==<br />
[[File:Debian-logo.png|right|100px]]<br />
<br />
An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).<br />
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).<br />
Current version is Debian Bookworm.<br />
<br />
'''Download location'''<br />
<br />
[https://images.mobian-project.org/pinephone/weekly/ Weekly] /<br />
[https://images.mobian-project.org/pinephone/installer/ Installer] /<br />
[https://images.mobian-project.org/pinephone/ Stable]<br />
<br />
Extract the image before installing:<br />
<br />
$ gzip -d Downloads/mobian-pinephone-*.img.gz<br />
<br />
See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.<br />
<br />
'''username/password'''<br />
<br />
mobian/1234<br />
<br />
'''What works, what does not work'''<br />
<br />
See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki] for most up to date status.<br />
<br />
Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker].<br />
As a general rule, issues with third-party apps (even the default ones) should be reported upstream.<br />
A Mobian issue would be related to getting the hardware to work on the PinePhone, <br />
but if unsure where the issue should be reported just open a ticket or ask.<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].<br />
<br />
'''Notes'''<br />
<br />
See [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.<br />
<br />
== Multi-distro demo image ==<br />
<br />
{{Warning | This is a demo image for testing different OSes before installing a regular image. Attempting to use this image productively is highly discouraged. The kernel is shared across the different OSes and is not updated.}}<br />
<br />
This image allow users to try many of the above Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.<br />
<br />
* Main page: https://xnux.eu/p-boot-demo/<br />
* Git repo: https://megous.com/git/pinephone-multi-boot/<br />
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)]<br />
<br />
'''Update 2021-06-02, using megi's kernel 5.13-rc4'''<br />
<br />
DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.<br />
<br />
This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.<br />
<br />
For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].<br />
<br />
* [http://dl.xnux.eu/p-boot-multi-2021-06-02.torrent Download torrent file from author's website]<br />
* [http://dl.xnux.eu/p-boot-multi-2021-06-02/ Download img.zst from author's website] (speed limited to 512KiB/s)<br />
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]<br />
** '''File name:''' multi.img.zst<br />
** '''SHA-256:''' <span style="word-break: break-all">9b099cdfece3ba862348ca32af6c51a41a1d161b1d897f9928ae8be3c824a0b6</span><br />
** '''File Size:''' 6.57GiB<br />
<br />
* [https://files.pine64.org/os/PinePhone/Multi/p-boot-multi-2021-06-02.img.gz Direct download img.gz from pine64.org] (re-zipped from zstd to gzip)<br />
** '''File name:''' p-boot-multi-2021-06-02.img.gz<br />
** '''MD5:''' 2abdaafb01dd7519f678b5a7c6538493<br />
** '''File Size:''' 6.8GB<br />
<br />
Due to its size, download though torrent is suggested by the author on its main page.<br />
<br />
{{hint | '''Note about .zst archive file:'''<br />
<br />
On Linux, you may install or compile <code>zstd</code>, and write the image to SD card by using <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.<br />
<br />
On Windows, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd], it provides different installation method in the README.md.Install and extract the .img file from the zst archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].}}<br />
<br />
Also see [[PinePhone Installation Instructions]].<br />
<br />
'''username/password'''<br />
<br />
All passwords, including root passwords, are <code>1111</code>.<br />
sxmo username is <code>user</code>.<br />
<br />
== Nemo Mobile ==<br />
[[File:nemo_mobile.png|right|100px]]<br />
<br />
Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].<br />
<br />
* Website: [https://nemomobile.net/ Nemo Mobile UX team]<br />
* [https://wiki.merproject.org/wiki/Nemo Mer Wiki page]<br />
<br />
'''Download location'''<br />
<br />
See the [https://nemomobile.net/installation/ installation page] on their website for the newest release and installation guides.<br />
<br />
'''What works, what does not work''' <br />
<br />
Development is now moving very fast after rebasing. For the current devel image, Wifi, SMS and Bluetooth works.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
For the Nemo Mobile UX itself:<br />
* GitHub issues: https://github.com/nemomobile-ux/main/issues<br />
<br />
For hardware:<br />
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues<br />
<br />
== NixOS ==<br />
[[File:nixos.png|right|100px]]<br />
<br />
NixOS support is handled through the Mobile NixOS project.<br />
<br />
* Project home page: [https://mobile.nixos.org/ Mobile NixOS]<br />
* PinePhone device page: [https://mobile.nixos.org/devices/pine64-pinephone.html Pine64 PinePhone — Mobile NixOS]<br />
* GitHub: [https://github.com/NixOS/mobile-nixos NixOS/mobile-nixos]<br />
<br />
There is no pre-built complete image.<br />
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],<br />
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].<br />
<br />
'''What works, what does not work'''<br />
<br />
Currently, it boots, it's just as compatible as the Android-based devices are with Mobile NixOS.<br />
It even supports a bit more since it can use WiFi.<br />
<br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository].<br />
Please specify that you are using a PinePhone when reporting issues.<br />
Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].<br />
<br />
== OpenMandriva Lx ==<br />
[[File:Oma-logo-22042013_300pp.png|right|100px]]<br />
<br />
{{Hint| '''Note:''' This image is solely for testing purposes.}}<br />
<br />
OpenMandriva Lx with Plasma Mobile as UI.<br />
<br />
'''Download location'''<br />
<br />
The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].<br />
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.<br />
<br />
'''What works, what does not work'''<br />
<br />
From the [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing 4.3 announcement],<br />
in future updates (4.3 and later), "Phone calls are working, and we have rewritten the camera app to be far more useful".<br />
<br />
== openSUSE ==<br />
[[File:SLEM-OS-logo.png|right|100px]]<br />
<br />
Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,<br />
except what needs to be changed for the PinePhone.<br />
The images include <i>zypper</i> (RPM) as the default package manager,<br />
and have access to virtually the same (open source) software as our desktop repositories,<br />
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.<br />
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.<br />
<br />
'''Download links'''<br />
<br />
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]<br />
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]<br />
<br />
To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].<br />
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.<br />
<br />
You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.<br />
<br />
'''Username/Password'''<br />
<br />
The login credentials are pine/1234 and root/linux.<br />
Change (or disable) the root password once you are set up.<br />
<br />
'''What works and what does not work'''<br />
<br />
You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].<br />
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].<br />
You will also find information in our wiki on how to report issues (Contributing section).<br />
<br />
== postmarketOS ==<br />
[[File:PostmarketOS-logo.png|right|100px]]<br />
<br />
postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.<br />
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).<br />
<br />
As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.<br />
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.<br />
<br />
When using the installer images (recommended), it is possible to:<br />
* encrypt the installation<br />
* install from the SD card to eMMC<br />
<br />
Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.<br />
<br />
Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.<br />
<br />
'''Download location'''<br />
<br />
* [https://postmarketos.org/download/ Download page]<br />
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]<br />
<br />
'''Username/password'''<br />
<br />
* Test images: user/147147<br />
* When using the installer images or building an image with pmbootstrap, you set your own username and password.<br />
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.<br />
<br />
'''What works, what does not work'''<br />
<br />
See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support.<br />
See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.<br />
<br />
== PureOS ==<br />
[[File:Pureos.png|right|100px]]<br />
<br />
{{Warning|This project is no longer under development and has been abandoned. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian Mobian] instead}}<br />
<br />
{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}<br />
<br />
[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.<br />
<br />
* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there<br />
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]<br />
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS<br />
<br />
'''Download location'''<br />
<br />
Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.<br />
<br />
Also see:<br />
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]<br />
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi<br />
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone<br />
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com<br />
<br />
== Sailfish OS ==<br />
[[File:Sailfish_logo.png|right|100px]]<br />
<br />
[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].<br />
<br />
* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.<br />
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]<br />
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]<br />
<br />
'''Download location'''<br />
<br />
'''Flashing script'''<br />
<br />
The Sailfish OS 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].<br />
<br />
The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.<br />
Note: The script will format and erase the SD card!<br />
<br />
Instructions:<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc. <br />
<br />
'''username/password'''<br />
<br />
Set PIN on initialization.<br />
<br />
* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.<br />
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''<br />
* When a screen with a loading circle is displayed, just left/right swipe it away.<br />
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.<br />
<br />
'''What works, what does not work'''<br />
<br />
See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.<br />
<br />
There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.<br />
<br />
Git repo links are at the top of this OS section. other repos that may be helpful:<br />
<br />
* [https://github.com/sailfish-on-dontbeevil GitHub project page]<br />
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]<br />
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)<br />
<br />
See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.<br />
<br />
'''Notes'''<br />
<br />
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.<br />
== Slackware ==<br />
<br />
Unofficial slackware images with xfce for the pinephone<br />
<br />
Discussion thread: [https://forum.pine64.org/showthread.php?tid=12181&highlight=slackware+pinephone Thread]<br />
<br />
Download link: http://dl.fail.pp.ua/slackware/images/pinephone/<br />
== SkiffOS ==<br />
[[File:SkiffOS-Icon-1.png|right|100px]]<br />
<br />
Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.<br />
<br />
Provides the reliability of firmware with the ease-of-use of package managers.<br />
<br />
Upgrade over-the-air via a simple rsync script, or copying 3 files.<br />
<br />
Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.<br />
<br />
Use configuration packages to configure distro:<br />
<br />
{| class="wikitable"<br />
! Package !! Distro<br />
|-<br />
| core/pinephone_neon || KDE Neon via Ubuntu repositories<br />
|-<br />
| core/pinephone_nixos || Nixos Mobile<br />
|-<br />
| core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh<br />
|-<br />
| core/pinephone_ubports || Ubuntu Ports for PinePhone<br />
|-<br />
| core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant<br />
|-<br />
| core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant<br />
|-<br />
| core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant<br />
|}<br />
<br />
The boot-up OS is upgraded independently from the containers.<br />
<br />
'''Download location'''<br />
<br />
The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].<br />
<br />
== Sxmo ==<br />
<br />
A collection of Suckless programs to create a mobile UI. Based on postmarketOS.<br />
<br />
'''Download location'''<br />
<br />
Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the ''/pine64-pinephone/sxmo/'' sections respectively).<br />
<br />
'''username/password'''<br />
<br />
user/147147<br />
<br />
'''How to contribute and report defects'''<br />
<br />
Contributing information is listed [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].<br />
<br />
== Ubuntu Touch ==<br />
[[File:Ubports-logo.png|right|100px]]<br />
<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.<br />
Installation instructions can be found on<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].<br />
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.<br />
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.<br />
<br />
'''Download location'''<br />
<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]<br />
<br />
'''username/password'''<br />
<br />
Set up during boot<br />
<br />
'''What works, what does not work'''<br />
<br />
Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page], or directly here [https://devices.ubuntu-touch.io/device/pinephone/#deviceOverview]<br />
<br />
'''How to contribute and report defects'''<br />
<br />
See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].<br />
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.<br />
<br />
= Tools =<br />
<br />
There are software tools, that can be booted on the PinePhone.<br />
<br />
== JumpDrive ==<br />
<br />
JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].<br />
<br />
See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.<br />
Make sure to download the "PinePhone" image and to unpack the archive before flashing.<br />
<br />
= Factory Test OS =<br />
<br />
{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}<br />
<br />
On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.<br />
The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later.<br />
Since the 20200501 version, it is able to test all the hardware.<br />
It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image.<br />
The downloadable image just does the hardware tests.<br />
Do not flash eMMC to test your device, just dd it to microSD and test from there.<br />
New versions are distributed as part of the postmarketOS distribution.<br />
<br />
Links:<br />
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)<br />
* [https://gitlab.com/MartijnBraam/factorytest Git repo]<br />
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]<br />
<br />
== Factory-loaded OS builds ==<br />
<br />
These are different operating system builds that was preloaded in the factory with testing utility.<br />
<br />
Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.<br />
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.<br />
<br />
All the download links below are direct download from pine64.org.<br />
<br />
<div style="overflow: auto;"><br />
{| class="wikitable" style="white-space: nowrap"<br />
! OS<br />
! Download Link<br />
! File Size<br />
! MD5<br />
|-<br />
| Beta Edition<br />
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]<br />
| 1.78GB<br />
| <code>f16bce93504a52217540ac886863a418</code><br />
|-<br />
| Mobian<br />
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]<br />
| 1.41GB<br />
| <code>015be381ff4e650a7fca6d4eaa90d63d</code><br />
|-<br />
| KDE<br />
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]<br />
| 2.28GB<br />
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code><br />
|-<br />
| Manjaro<br />
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]<br />
| 1.04GB<br />
| <code>4edfd4dceaefdd32a3417c1727161c29</code><br />
|-<br />
| postmarketOS<br />
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]<br />
| 517MB<br />
| <code>244093be2f6d728fcbd1d29114607727</code><br />
|-<br />
| Ubuntu Touch<br />
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]<br />
| 1.05GB<br />
| <code>2d7f5271e7a281db8f1b1219bedbe131</code><br />
|}<br />
</div><br />
<br />
= Installing other ARM64 distributions =<br />
<br />
{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.<br />
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}<br />
<br />
{{Hint|'''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.}}<br />
<br />
General steps:<br />
<br />
# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.<br />
# 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 instead (in archive mode, like <code>rsync -ar</code>).<br />
# Edit <code>/etc/fstab</code> to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.<br />
<br />
If you would like to see examples or specific commands for how to complete these steps, see:<br />
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release<br />
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi<br />
<br />
= Other Resources =<br />
Community<br />
* [[Main_Page#Community_and_Support|Links to the community services]]<br />
<br />
Hardware information<br />
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki<br />
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]<br />
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]<br />
* 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]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://pine64.com/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [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]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]<br />
<br />
[[Category:PinePhone]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=User:KJ7RRV/QMFbrick&diff=11983User:KJ7RRV/QMFbrick2021-12-09T17:51:54Z<p>KJ7RRV: </p>
<hr />
<div>'''Trojan:Linux/QMFbrick''' (usually called QMFbrick; sometimes simply called "the PinePhone malware" or "the malware") is a family of malware targeting the [[PinePhone]].<br />
<br />
Three variants are known:<br />
<br />
* QMFbrick.A: bundled with a Snake game in an Arch package<br />
* QMFbrick.B: bundled with wlsunset in an Arch package<br />
* QMFbrick.C: bundled with wlsunset in a Debian package<br />
<br />
The trojans have been spread by anonymous download links in the Pine64 and DanctNIX chats.<br />
<br />
The A variant was tested by Danct12 and is known to use systemd to set a timer to soft-brick the modem and wipe / on the first Wednesday after installation at 20:00 local time.<br />
<br />
KJ7RRV is currently working on reverse engineering QMFbrick and attempting to write a removal tool, initially focusing on the B variant.<br />
<br />
It seems that running "sudo systemctl disable --now shadlow.timer" before 20:00 on a Wednesday (local time) will stop the A variant from doing any damage. This is not guaranteed, however, and it may or may not work with B and C.<br />
<br />
It is not known if the malware has any effects if it is disabled before the activation time. Out of an abundance of caution, a phone that has been infected, even if the malware has been disabled, should not be considered trustworthy.</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=User:KJ7RRV/QMFbrick&diff=11947User:KJ7RRV/QMFbrick2021-12-08T14:40:15Z<p>KJ7RRV: </p>
<hr />
<div>'''Trojan:Linux/QMFbrick''' (usually called QMFbrick; sometimes simply called "the PinePhone malware" or "the malware") is a family of malware targeting the [[PinePhone]].<br />
<br />
Three variants are known:<br />
<br />
* QMFbrick.A: bundled with a Snake game in an Arch package<br />
* QMFbrick.B: bundled with wlsunset in an Arch package<br />
* QMFbrick.C: bundled with wlsunset in a Debian package<br />
<br />
The trojans have been spread by anonymous download links in the Pine64 and DanctNIX chats.<br />
<br />
The A variant was tested by Danct12 is known to use systemd to set a timer to soft-brick the modem and wipe / on the next Wednesday at 20:00 local time.<br />
<br />
KJ7RRV is currently working on reverse engineering QMFbrick and attempting to write a removal tool, initially focusing on the B variant.<br />
<br />
It seems that running "sudo systemctl disable --now shadlow.timer" before 20:00 on a Wednesday (local time) will stop the A variant from doing any damage. This is not guaranteed, however, and it may or may not work with B and C.<br />
<br />
It is not known if the malware has any effects if it is disabled before the activation time. Out of an abundance of caution, a phone that has been infected, even if the malware has been disabled, should not be considered trustworthy.</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=User:KJ7RRV/QMFbrick&diff=11944User:KJ7RRV/QMFbrick2021-12-08T07:07:37Z<p>KJ7RRV: </p>
<hr />
<div>'''Trojan:Linux/QMFbrick''' (usually called QMFbrick; sometimes simply called "the PinePhone malware" or "the malware") is a family of malware targeting the [[PinePhone]].<br />
<br />
Three variants are known:<br />
<br />
* QMFbrick.A: bundled with a Snake game in an Arch package<br />
* QMFbrick.B: bundled with wlsunset in an Arch package<br />
* QMFbrick.C: bundled with wlsunset in a Debian package<br />
<br />
The trojans have been spread by anonymous download links in the Pine64 and DanctNIX chats.<br />
<br />
The A variant was tested by Danct12 is known to soft-brick the modem and wipe /.<br />
<br />
KJ7RRV is currently working on reverse engineering QMFbrick and attempting to write a removal tool, initially focusing on the B variant.<br />
<br />
It seems that running "sudo systemctl disable --now shadlow.timer" before 20:00 on a Wednesday (local time) will stop the A variant from doing any damage. This is not guaranteed, however, and it may or may not work with B and C.<br />
<br />
It is not known if the malware has any effects if it is disabled before the activation time. Out of an abundance of caution, a phone that has been infected, even if the malware has been disabled, should not be considered trustworthy.</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=User:KJ7RRV/QMFbrick&diff=11943User:KJ7RRV/QMFbrick2021-12-08T07:05:57Z<p>KJ7RRV: </p>
<hr />
<div>'''Trojan:Linux/QMFbrick''' is a family of malware targeting the [[PinePhone]].<br />
<br />
Three variants are known:<br />
<br />
* QMFbrick.A: bundled with a Snake game in an Arch package<br />
* QMFbrick.B: bundled with wlsunset in an Arch package<br />
* QMFbrick.C: bundled with wlsunset in a Debian package<br />
<br />
The trojans have been spread by anonymous download links in the Pine64 and DanctNIX chats.<br />
<br />
The A variant was tested by Danct12 is known to soft-brick the modem and wipe /.<br />
<br />
KJ7RRV is currently working on reverse engineering QMFbrick and attempting to write a removal tool, initially focusing on the B variant.<br />
<br />
It seems that running "sudo systemctl disable --now shadlow.timer" before 20:00 on a Wednesday (local time) will stop the A variant from doing any damage. This is not guaranteed, however, and it may or may not work with B and C.<br />
<br />
It is not known if the malware has any effects if it is disabled before the activation time. Out of an abundance of caution, a phone that has been infected, even if the malware has been disabled, should not be considered trustworthy.</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=User:KJ7RRV/QMFbrick&diff=11942User:KJ7RRV/QMFbrick2021-12-08T05:39:56Z<p>KJ7RRV: </p>
<hr />
<div>'''Trojan:Linux/QMFbrick''' is a family of malware targeting the [[PinePhone]].<br />
<br />
Three variants are known:<br />
<br />
* QMFbrick.A: bundled with a Snake game in an Arch package<br />
* QMFbrick.B: bundled with wlsunset in an Arch package<br />
* QMFbrick.C: bundled with wlsunset in a Debian package<br />
<br />
The trojans have been spread by anonymous download links in the Pine64 and DanctNIX chats.<br />
<br />
The A variant was tested by Danct12 is known to soft-brick the modem and wipe /.<br />
<br />
KJ7RRV is currently working on reverse engineering QMFbrick and attempting to write a removal tool, initially focusing on the B variant.<br />
<br />
It seems that running "sudo systemctl disable --now shadlow.timer" before 20:00 on a Wednesday (local time) will stop the A variant from doing any damage. This is not guaranteed, however, and it may or may not work with B and C.</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=User:KJ7RRV/QMFbrick&diff=11941User:KJ7RRV/QMFbrick2021-12-08T04:51:56Z<p>KJ7RRV: Created page with "'''Trojan:Linux/QMFbrick''' is a family of malware targeting the PinePhone. Three variants are known: * QMFbrick.A: bundled with a Snake game in an Arch package * QMFbri..."</p>
<hr />
<div>'''Trojan:Linux/QMFbrick''' is a family of malware targeting the [[PinePhone]].<br />
<br />
Three variants are known:<br />
<br />
* QMFbrick.A: bundled with a Snake game in an Arch package<br />
* QMFbrick.B: bundled with wlsunset in an Arch package<br />
* QMFbrick.C: bundled with wlsunset in a Debian package<br />
<br />
The trojans have been spread by anonymous download links in the Pine64 and DanctNIX chats.<br />
<br />
The A variant was tested by Danct12 is known to soft-brick the modem and wipe /.<br />
<br />
KJ7RRV is currently working on reverse engineering QMFbrick and attempting to write a removal tool, initially focusing on the B variant.</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=Category:PinePhone_Revisions&diff=11712Category:PinePhone Revisions2021-10-23T03:36:47Z<p>KJ7RRV: Created page with "Revisions of the PinePhone Category:PinePhone"</p>
<hr />
<div>Revisions of the [[PinePhone]]<br />
[[Category:PinePhone]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_v1.1_-_Braveheart&diff=11711PinePhone v1.1 - Braveheart2021-10-23T03:35:48Z<p>KJ7RRV: </p>
<hr />
<div>The PinePhone v1.1 "Braveheart" is a hardware revision of the PinePhone that shipped in January 2020.<br />
<br />
This page contains resources which are exclusive to the 1.1 revision of the PinePhone. For newer revisions or for resources related to other PinePhone revisions see [[PinePhone#Hardware revisions]].<br />
<br />
== Schematic ==<br />
<br />
[http://files.pine64.org/doc/PinePhone/PinePhone_Schematic_v1.1_20191031.pdf Hardware schematic]<br />
<br />
== Changes from 1.0 ==<br />
<br />
Braveheart is slightly different from the 1.0 revision of the Pinephone. These differences should not require creating different images.<br />
<br />
# Added CPU shielding and cover plate<br />
# Swap PC3 to FLASH_EN and PD24 to FLASH_TRIGOUT, where previously they were reversed<br />
# Add pulldown resistor on PD24 (FLASH_TRIGOUT) so the flash LED does not light on boot<br />
# Connect WiFi enable to VD33<br />
# Set the EG25G's PWRKEY on by default (see resistor R1526)<br />
# Add R630 resistor location, populate with 0K by default. Allows adjusting to different battery thermistors in case this is not possible in software.<br />
# 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.<br />
# A64 LINEOUTN is disconnected from the speaker amplifier, making the speaker output single-ended instead of differential<br />
<br />
== DIY Hardware fixes ==<br />
Some of the known issues can be fixed with more or less involved hardware modifications:<br />
* VCONN mod: USB-C CC pins are pulled to GND, [[PinePhone_1.2_VCONN_Hardware_Fix|removing small switches]] can make USB-OTG work. A proper fix is to replace those with another component.<br />
* [[PinePhone 1.1 VBUS power usage Hardware Fix]] to lower power consumption, especially when the phone is powered off.<br />
* PMIC mod<br />
<br />
== Known issues ==<br />
<br />
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.<br />
<br />
=== Need a way to distinguish v1.1 from v1.2 from U-Boot SPL ===<br />
<br />
''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.''<br />
<br />
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.<br />
<br />
=== WiFi module cannot be disabled or reset in software ===<br />
<br />
''Resolved in v1.2 by connecting PL2 to the WiFi module's WiFi reset pin.''<br />
<br />
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 privacy switch) to a regulator that cannot be turned off (easily, if at all). So while the privacy switch works, there's no way to disable the WiFi module in software. This will lead to excess power consumption when WiFi is turned off.<br />
<br />
=== Magnetometer's IRQ signal is routed to the wrong pin ===<br />
<br />
''Resolved in v1.2 by connecting the magnetometer's <tt>DRDY</tt> pin to PB1.''<br />
<br />
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.<br />
<br />
Software workaround is to disable magnetometer interrupt in the devicetree, and use a hrtimer or some other software triggering mechanism for IIO devices.<br />
<br />
=== Speaker output could be differential ===<br />
<br />
''Resolved in v1.2 by connecting <tt>LINEOUTP</tt> to the speaker amplifier's <tt>INP</tt> input.''<br />
<br />
Using a differential connection to the speaker amplifier would significantly lower the noise floor of the speaker, and would allow doubling the max volume.<br />
<br />
=== Modem AP_READY signal is not connected ===<br />
<br />
''Resolved in v1.2 by connecting PH7 to <tt>AP_READY</tt> instead of <tt>WAKEUP_IN</tt>.''<br />
<br />
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).<br />
<br />
=== Modem RI signal routing prevents wakeup ===<br />
<br />
''Resolved in v1.2 by connecting <tt>RI</tt> to PL6.''<br />
<br />
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>).<br />
<br />
'''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.<br />
<br />
=== Excess power usage while driving VBUS ===<br />
<br />
''Resolved in v1.2 by connecting PL9 and <tt>VBUS_CTRL</tt> on the ANX7688 to <tt>N_VBUSEN</tt> on the PMIC.'' A [[PinePhone 1.1 VBUS power usage Hardware Fix | crude hardware workaround]] is also possible.<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== ANX7688 power supply situation is problematic ===<br />
<br />
''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.''<br />
<br />
ANX7688 has four power inputs: 3v3, 1v8, 1v0, and HDMI_VT (which is also 3v3).<br />
* 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.<br />
* HDMI_VT is only needed during video transmission, and should remain connected to DLDO1.<br />
* 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.<br />
* 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.<br />
* 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.)<br />
* 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.<br />
<br />
=== Modem PWR_KEY signal resistor population ===<br />
<br />
''Resolved in v1.2 by separating the modem <tt>PWRKEY</tt> (PB3) and <tt>STATUS</tt> (PH9) signals.''<br />
<br />
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).<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Modem has access to sensors on I2C1 ===<br />
<br />
''Resolved in v1.2 by disconnecting the modem's I2C port.''<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Allow access the modem debug UART ===<br />
<br />
''Not resolved in v1.2 -- would have required moving several other GPIOs.''<br />
<br />
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).<br />
<br />
=== Modem UART flow control is broken ===<br />
<br />
''Not resolved in v1.2 -- assumption is that USB will be used for high-bandwidth modem I/O.''<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== ANX7688 power/reset control pulled the wrong way ===<br />
<br />
''Not resolved in v1.2 -- this has minimal impact.''<br />
<br />
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.<br />
<br />
=== VCONN_EN signals are possibly inverted ===<br />
<br />
''Further investigation determined that the hardware is correct as-is in v1.1, so no change was made.''<br />
<br />
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.<br />
<br />
=== Cameras have the same default I2C address ===<br />
<br />
''Resolved in software by reprogramming the one of the cameras' I2C addresses at boot.''<br />
<br />
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.<br />
<br />
=== USB-C CC pins are pulled to the GND by AW3512 (VCONN switches) when VCONN is off ===<br />
<br />
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.<br />
<br />
In SW this can only be worked around by manual selection of PinePhone's data and power role by the user.<br />
<br />
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)<br />
<br />
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.<br />
<br />
This issue is also present on the PinePhone 1.2 (CE) version and was fixed with revision 1.2a. See the [[PinePhone_1.2_VCONN_Hardware_Fix|workaround]] for affected revisions.<br />
<br />
=== Pogo Pins supply 5v0, not 3v3 ===<br />
<br />
''No hardware change suggested, to maintain accessory compatibility.''<br />
<br />
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.<br />
<br />
<br />
[[Category:PinePhone]]<br />
[[Category:PinePhone Revisions]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_v1.2&diff=11710PinePhone v1.22021-10-23T03:35:25Z<p>KJ7RRV: </p>
<hr />
<div>The PinePhone v1.2 is a hardware revision of the PinePhone that was shipped in 2020 as UBports Community Edition.<br />
<br />
This page contains information and resources which are specific to the UBports Community Edition (v1.2 PCB) revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see [[PinePhone#Hardware revisions]].<br />
<br />
== Schematics ==<br />
<br />
* [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf Hardware schematic v1.2] (2020-03-10, for the UBports Community Edition)<br />
<br />
== Changes from v1.1 ==<br />
<br />
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).<br />
<br />
# The WiFi module's <tt>CHIP_EN</tt> input (connected to the privacy switch) is now pulled down, so the WiFi will turn off reliably when the switch is off.<br />
# PL2 is now connected to the WiFi module's reset pin, allowing the WiFi to be turned off or reset in software.<br />
# The magnetometer's <tt>DRDY</tt> pin is now connected to PB1, allowing interrupt-driven periodic sensor readings.<br />
# <tt>LINEOUTP</tt> is again connected to the speaker amplifier's INP input (like in v1.0), increasing the SNR of the rear speaker.<br />
# 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.<br />
# 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.<br />
# 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.<br />
# As part of the previous change, the ANX7688's reset input was moved to PD6; this pin previously controlled the USB OTG power.<br />
# 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.<br />
# As part of the previous change, PD11 now controls the ANX7688's 1v0 digital power domain.<br />
# 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.<br />
# The modem no longer has access to the I2C bus containing the sensors.<br />
# <tt>HBIAS</tt> is now connected to the headphone jack.<br />
<br />
== Known issues ==<br />
<br />
=== Backlight ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
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+.<br />
<br />
Additionally there is also another backlight issue, where the brightness is lower when connecting a VBUS powered device, https://xnux.eu/log/#022.<br />
<br />
=== USB ===<br />
The USB-C CC pins are pulled to the GND by AW3512 (VCONN switches) when VCONN is off. 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.<br />
<br />
The issue was was fixed with revision 1.2a. See [[PinePhone_1.2_VCONN_Hardware_Fix]] for details and an instruction about how to do the hardware fix.<br />
<br />
In SW this can only be worked around by manual selection of PinePhone's data and power role by the user.<br />
<br />
Hardware workaround is to desolder 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 (see https://xnux.eu/devices/pp-usbc-fix.jpg).<br />
<br />
Hardware 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. User ''mozzwald'' used NCP334FCT2G as a replacement.<br />
<br />
<br />
[[Category:PinePhone]] <br />
[[Category:PinePhone Revisions]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_v1.2a&diff=11709PinePhone v1.2a2021-10-23T03:35:03Z<p>KJ7RRV: </p>
<hr />
<div>The PinePhone v1.2a is a hardware revision of the PinePhone that started shipping in Q3 2020.<br />
<br />
This page contains information and resources which are specific to the v1.2a revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see [[PinePhone#Hardware revisions]].<br />
<br />
== Schematics ==<br />
* [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf Hardware schematic v1.2a] (2020-06-08, for the postmarketOS Community Edition)<br />
<br />
== Changes from v1.2 ==<br />
* A thermal pad was added to the SoC alongside a graphene foil covering the metal shielding of the mainboard which is in direct contact with the LCD backplane to help dissipate heat. Another graphene foil sticker was added to the rear cover of the device to help disperse thermals from the back of the modem.<br />
* Fixed a rectangular dead spot of the touchscreen under the speaker grill<br />
* Antenna changes<br />
* USB-C CC fix for video out and OTG functionality<br />
<br />
== Known issues == <br />
<br />
The backlight issue of v1.2 is still present, see [[PinePhone v1.2#Backlight]]. There is also another backlight issue, where the brightness is lower when connecting a VBUS powered device, https://xnux.eu/log/#022.<br />
<br />
<br />
[[Category:PinePhone]]<br />
[[Category:PinePhone Revisions]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_v1.2b&diff=11708PinePhone v1.2b2021-10-23T03:34:38Z<p>KJ7RRV: </p>
<hr />
<div>The PinePhone v1.2b is a hardware revision of the PinePhone that started shipping in Q4 2020.<br />
<br />
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]].<br />
<br />
== Schematics ==<br />
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2b%20Released%20Schematic.pdf Hardware schematic v1.2b] (for the Manjaro Community Edition)<br />
<br />
== Changes from v1.2a ==<br />
* A bug was fixed, where connecting a VBUS powered device lowered the screen brightness (resistor R1318 changed to NC).<br />
<br />
== Changes with the Beta Edition ==<br />
* Due to the global pandemic early 2021 and the component shortage as a result, the magnetometer in the Beta Edition had to be replaced from an LIS3MDL to an AF8133J.<br />
<br />
== Known issues == <br />
<br />
* HDMI hotplug detection is not reliable due to [https://xnux.eu/log/#045 a HW bug in level shifting circuitry for the hot plug detect (HPD) signal between HDMI bridge and A64 SoC.]<br />
* It is not known if three issues of previous revisions are still present and if yes to which degree, or if they have been fixed by removing resistor R1318, see [[PinePhone v1.2#Backlight]] for some details. Please edit this page once this has been confirmed. Mind that there is currently a likely software-related bug present, which also causes the screen to flicker. The bug usually happens after abruptly shutting down the phone previously (for example by forcing it off), in contrast to powering it off.<br />
<br />
<br />
[[Category:PinePhone]]<br />
<br />
[[Category:PinePhone Revisions]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=Project_Anakin&diff=11707Project Anakin2021-10-23T03:34:13Z<p>KJ7RRV: </p>
<hr />
<div>= The Project "Anakin" - Phase 1 of PINE64 Smartphone "PinePhone" Development Kit =<br />
Project Anakin is a marsh-up kit for the PINE64 Smartphone dubbed "PinePhone". It is used in the early stages of development as a starting point for affiliated projects. <br />
PinePhone development has been broken down into three distinct phases: <br />
* First phase - Project Anakin <br />
* Second phase - purpose-built development kit code named "Don't be evil". It will be introduced at FOSDEM 2019 <br />
* Lastly, the third phase which is the PinePhone itself - scheduled to be released in Q3 2019 (pending on software development).<br />
<br />
The Anakin kit consists of following components:<br />
* SoPine Module<br />
* SoPine Model A baseboard<br />
* Pine A64 Wifi/BT module<br />
* 16GB eMMC module<br />
* 5 Mega Piixel CMOS Camera Sensor <br />
* 7" Touch Screen LCD Panel<br />
* Playbox Enclosure<br />
* Lithium Ion Battery case (note: battery not included, can accommodate 1-3 pieces of 18650 size Lithium Ion batter. In general, one is good enough)<br />
* Quectel EC20 R2.1 LTE Module (note: The SIM tray design not distinguish polarity well and all reverse slot in)<br />
<br />
[[File:Anakin_kit_1.jpg]] [[File:Anakin_kit_2.jpg]] [[File:Anakin_kit_4.jpg]] [[File:Anakin_kit_3.jpg]]<br />
<br />
You can also flash an OS image manually; please follow the instructions below.<br />
<br />
= Software and OS Image Downloads =<br />
<br />
== Arch Linux mainline build by anarsoul ==<br />
* [https://github.com/anarsoul/linux-build/releases/latest Direct download latest release build from anarsoul github and look for archlinux-xfce-sopine-xxxxxxxx-x.img.xz]<br />
* Login with<br />
** User Name: alarm, Password: alarm<br />
** User Name: root, Password: root<br />
* please login root and execute "pacman -Syu" for latest update<br />
* Standby feature not yet implemented<br />
<br />
== AOSC Community mainline minimum build by icenowy ==<br />
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]<br />
** [https://github.com/AOSC-Dev/aosc-os-arm-bsps/tree/master/sunxi/u-boot-sun50i-a64-sopine-baseboard Icenowy's github for A64 SoC]<br />
* Login with<br />
** username: aosc<br />
** password: anthon<br />
<br />
= Mali-400 64-bit Driver =<br />
== Mali-400 64-bit Driver [20171220] ==<br />
* [[Mali_Driver|Mali 64-bit X11 and Wayland Driver Download]]<br />
<br />
== Quick Links to Build Sources of OS Images ==<br />
* [https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix A64 mainline status matrix chart]<br />
<br />
'''Some these OS images labelled as <span style="color:#FF0000">beta or nightly builds</span> which means they are only fit for testing purposes<br />
<br />
'''These images should be <span style="color:#FF0000">used at your own risk</span> and are not fit for normal use'''<br />
<br />
* [https://github.com/anarsoul/linux-build/releases/latest Arch Linux XFCE]<br />
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ longsleep BSP Linux]<br />
* [https://github.com/ayufan-pine64/linux-build/releases/latest/ ayufan Linux]<br />
<br />
= [[Accessories_Step_by_Step_Guides|Accessories Step-by-Step Guides]] =<br />
Under [[Accessories_Step_by_Step_Guides|'Guides for PINE A64(+) accessories']] you can find instructions and guides concerning:<br />
* Playbox Enclosure<br />
* Bluetooth and WiFi module<br />
* 7" Touch Screen LCD Panel<br />
<br />
= SoC and Memory Specification =<br />
* Based on Allwinner A64/R18<br />
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.''' <br />
[[File:Allwinner_A64.jpg]] [[File:Allwinner_R18.png]]<br />
<br />
== CPU Architecture ==<br />
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1152Mhz]<br />
* A power-efficient ARM v8 architecture<br />
* 64 and 32bit execution states for scalable high performance<br />
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function<br />
* Support Large Physical Address Extensions(LPAE)<br />
* VFPv4 Floating Point Unit<br />
* 32KB L1 Instruction cache and 32KB L1 Data cache<br />
* 512KB L2 cache<br />
<br />
== GPU Architecture ==<br />
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php ARM Mali400MP2 Dual-core GPU]<br />
* Support OpenGL ES 2.0 and OpenVG 1.1 standard<br />
<br />
== System Memory ==<br />
* RAM Memory Variants: 2GB LPDDR3.<br />
* Storage Memory: SPI Flash and optional eMMC module from 16GB up to 64GB<br />
<br />
= Project Anakin, SOPine Module and Baseboard Information, Schematics, and Certifications =<br />
* Model "A" Baseoard Dimensions: 133mm x 80mm x 19mm<br />
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, 3.5OD/1.35ID Barrel DC Jack connector, Euler connector<br />
* [https://wiki.pine64.org/images/7/7d/Pine64_Board_Connector.png PINE A64 Connector Layout @courtesy of norm24]<br />
* [https://wiki.pine64.org/images/d/da/Pine64_Connector.JPG PINE A64 Connector List]<br />
* [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Pin-Assignments-ver-1.0.pdf SOPine Module Pin Assignment ver 1.0]<br />
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20Pin%20Assignment%20160119.pdf PINE A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)]<br />
** [https://synfare.com/599N105E/hwdocs/pine64/index.html Good documentation about PINE A64, A64+, and A64-LTS GPIO pins article]<br />
* SOPine Module Schematic:<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Schematic-ver-0.9.pdf SOPine Module Schematic]<br />
* SOPine Model "A" Baseboard Schematic and PCB Board Resource:<br />
** '''SOPine model "A" Baseboard is an hardware open source project but is not "OSH" compliant'''<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Baseboard%20Model%20A%20Rev%20B20170207.DSN SOPine Model "A" Baseboard Schematic capture Rev B DSN source file]<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Baseboard%20Model%20A%20Rev%20B20170207.pdf SOPine Model "A" Baseboard Schematic Rev B PDF file]<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20baseboard%20PCB%20layout%20PCB%20Job.tar SOPine Model "A" Baseboard PCB Job source file]<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20basedboard%20GERBER.tar SOPine Model "A" Baseboard PCB Gerber file]<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20baseboard%20PCB%20layout%20PDF.tar SOPine Model "A" Baseboard PCB Layout PDF file]<br />
* SOPine (together with model "A" baseboard) Certification:<br />
** [https://files.pine64.org/doc/cert/SOPine%20FCC%20certification%20VOC20170428.pdf SOPine with model "A" baseboard FCC Certificate]<br />
** [https://files.pine64.org/doc/cert/SOPine%20CE%20certification%20VOC20170428.pdf SOPine with model "A" baseboard CE Certificate]<br />
** [https://files.pine64.org/doc/cert/SOPine%20ROHS%20certification%20VOC20170322.pdf SOPine with model "A" baseboard RoHS Certificate]<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Allwinner A64/R18 SoC information:<br />
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.''' <br />
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]<br />
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner-R18-Brief%20Sheet.pdf Allwinner R18 SoC Brief Introduction]<br />
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64/R18 SoC Data Sheet V1.1 (Official Released Version)]<br />
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64/R18 SoC User Manual V1.0 (Official Release Version)]<br />
* X-Powers AXP803 PMU (Power Management Unit) information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]<br />
* LPDDR3 information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 Datasheet]<br />
* eMMC information:<br />
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/H26M64003DQR%20Datasheet.pdf Hynix eMMC Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE_eMMC_NCEMBSF9-xxG%20SPEC%20A0%2020150730.pdf Foresee eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]<br />
* '''Project Anakin module/component related information:'''<br />
** 5MPixel Rear CMOS Camera module information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf PINE64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/S5K4EC%205M%208%205X8%205%20PLCC%20%20Data%20Sheet_V1.0.pdf S5K4EC 5MP CMOS Image Sensor SoC Module Datasheet]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/S5K4ECGX_EVT1_DataSheet_R005_20100816.pdf S5K4EC 5MP CMOS Image Sensor SoC Chip Datasheet]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/s5k4ec.c S5K4EC 5MP CMOS Image Sensor Driver Source Code in C language]<br />
** LCD Touch Screen Panel information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/FY07024DI26A30-D_feiyang_LCD_panel.pdf 7.0" 1200x600 TFT-LCD Panel Specification]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/HK70DR2459-PG-V01.pdf Touch Panel Specification]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/GT911%20Capacitive%20Touch%20Controller%20Datasheet.pdf GOODiX GT911 5-Point Capacitive Touch Controller Datasheet]<br />
** Lithium Battery information:<br />
<br />
** Ethernet PHY information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for PINE A64+ Board]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8201cp.pdf Realtek RTL8201 10/100M Ethernet Transceiver for PINE A64 Board]<br />
** Wifi/BT module information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]<br />
** Enclosure information:<br />
*** [https://files.pine64.org/doc/datasheet/case/playbox_enclosure_20160426.stp Playbox Enclosure 3D file]<br />
** Connector information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]<br />
** LTE module information:<br />
[[File:QUECTEL_EC20_Dongle-small.jpg]]<br />
*** Note: The current Project Anakin kit deploy on using Quectel EC20_R2.1 which belongs to EC25 family. Actual production will use EC25 and EG25-G (still preliminary) module pending on region.<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC20_R2.1_LTE_Specification_V1.1.pdf Quectel EC20 R2.1 LTE Module Specification]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_LTE_Specification_V1.4.pdf Quectel EC25 LTE Module Specification]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EG25-G_LTE_Specification_V1.1_Preliminary_20180522%20(002).pdf Quectel EG25-G LTE Module Specification]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25&EC21_QuecCell_AT_Commands_Manual_V1.1.pdf Quectel EC25 LTE Module AT Cammands Set Manual]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Hardware_Design_V1.3.pdf Quectel EC25 LTE Module Hardware Design Guide]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Reference_Design_Rev.D_20161111.pdf Quectel EC25 LTE Module Reference Design Guide]<br />
<br />
= Other Resources =<br />
* [https://linux-sunxi.org/Pine64#Manufacturer_images Linux Sunxi Wiki page on PINE A64]<br />
* [https://github.com/apritzel/pine64 Linux Image created by Andre Przywara]<br />
* [https://github.com/longsleep/build-pine64-image PINE64 Linux build scripts, tools and instructions by Longsleep]<br />
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ PINE64 Linux image by Longsleep]<br />
* [https://softwarebakery.com/shrinking-images-on-linux Shrinking images on Linux by FrozenCow]<br />
* [https://osmocom.org/projects/quectel-modems/wiki/EC25/24 Quectel EC-25 LTE module open source information]<br />
<br />
[[Category:PinePhone]] [[Category:Allwinner A64]]<br />
[[Category:PinePhone Revisions]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=Project_Don%27t_be_evil&diff=11706Project Don't be evil2021-10-23T03:34:00Z<p>KJ7RRV: </p>
<hr />
<div>= The Project "Don't be evil" - Phase 2 of PINE64 Smartphone "PinePhone" Development Kit =<br />
<br />
Project Don't be evil is an actual smartphone developer kit for the PINE64 Smartphone dubbed "PinePhone". It is used in the early stages of development as a starting point for affiliated projects. <br />
PinePhone development has been broken down into three distinct phases: <br />
* First phase - Project Anakin <br />
* Second phase - purpose-built development kit code named "Don't be evil" and introduced at FOSDEM 2019 <br />
* Lastly, the third phase which is the PinePhone itself - scheduled to be prototype released in Q3 2019 and BTO batch released with mobile OS parents in Q4 2019 (pending on software development).<br />
<br />
[[Image:Qee3ovj.jpg|200px]]<br />
[[Image:Qsud2Gt.jpg|200px]]<br />
[[Image:Martijnpocket.jpg|200px]]<br />
<br />
= Project Don't be evil, Baseboard and SOPine Module Information, and Schematics =<br />
* Baseboard Dimensions: 165mm x 76mm x 19.5mm<br />
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, USB type-C connector<br />
* Baseboard Schematic:<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone-devkit%20Board%20Structure.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Structure]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone-devkit-SCH%20Ver%201.1.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.1 Schematic]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone%20Dev%20Kit%20Ver%201.1_PCB.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.1 PCB Artwork]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone-devkit-SCH%20Ver%201.2.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.2 Schematic]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone%20Dev%20Kit%20Ver%201.2_PCB.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.2 PCB Artwork]<br />
* SOPine Module Schematic:<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Schematic-ver-0.9.pdf SOPine Module Schematic]<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Pin-Assignments-ver-1.0.pdf SOPine Module Pin Assignment ver 1.0]<br />
* Wifi/BT module information:<br />
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]<br />
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20Pin%20Assignment%20160119.pdf PINE A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)]<br />
<br />
<br />
= SoC and Memory Specification =<br />
* Based on Allwinner A64/R18<br />
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.''' <br />
<div style=float:right>[[File:Allwinner_A64.jpg]] [[File:Allwinner_R18.png]]</div><br />
<br />
== CPU Architecture ==<br />
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1152Mhz]<br />
* A power-efficient ARM v8 architecture<br />
* 64 and 32bit execution states for scalable high performance<br />
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function<br />
* Support Large Physical Address Extensions(LPAE)<br />
* VFPv4 Floating Point Unit<br />
* 32KB L1 Instruction cache and 32KB L1 Data cache<br />
* 512KB L2 cache<br />
<br />
== GPU Architecture ==<br />
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php ARM Mali400MP2 Dual-core GPU]<br />
* Support OpenGL ES 2.0 and OpenVG 1.1 standard<br />
<br />
== System Memory ==<br />
* RAM Memory Variants: 2GB LPDDR3.<br />
* Storage Memory: SPI Flash and optional eMMC module from 16GB up to 64GB<br />
<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Allwinner A64/R18 SoC information:<br />
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.''' <br />
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]<br />
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner-R18-Brief%20Sheet.pdf Allwinner R18 SoC Brief Introduction]<br />
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64/R18 SoC Data Sheet V1.1 (Official Released Version)]<br />
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64/R18 SoC User Manual V1.0 (Official Release Version)]<br />
* X-Powers AXP803 PMU (Power Management Unit) information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]<br />
* LPDDR3 information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 Datasheet]<br />
* eMMC information:<br />
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/H26M64003DQR%20Datasheet.pdf Hynix eMMC Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE_eMMC_NCEMBSF9-xxG%20SPEC%20A0%2020150730.pdf Foresee eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]<br />
* '''Project Don't be evil module/component related information:'''<br />
** 2MPixel front CMOS Camera module information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/GC20355Mp-module_for_pinephone_devkit.pdf 2MP CMOS Image Sensor Module Drawing]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/GC2035%20Product%20Brief.pdf GalaxyCore GC2035 2MP CMOS Image Sensor Product Brief]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/GC2035%20DataSheet.pdf GalaxyCore GC2035 2MP CMOS Image Sensor Datasheet]<br />
** 5MPixel Rear CMOS Camera module information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/ATK-OV5640-5Mp-module_for_pinephone_devkit.pdf 5MP CMOS Image Sensor Module Drawing]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OmniVision OV5640 5MP CMOS Image Sensor Datasheet]<br />
*** [https://www.arducam.com/downloads/modules/OV5640/OV5640_Software_app_note_parallel.pdf OmniVision OV5640 5MP CMOS Image Sensor Software Application Note]<br />
** LCD Touch Screen Panel information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/XBD572-IPS-HI010A%20SPEC.pdf 5.7" 1440x720 IPS LCD Panel Specification]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/JD9365D_DS_Preliminary_V0.01_20170427.pdf fiti JD9365D LCD Controller Datasheet]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/XBD572-IPS-HI010A%20SPEC.pdf 5.7" Front Panel Touch Screen Specification]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/FT6336GU_Upgrade_Spec_Ver1.0.pdf FocalTech FT6336GU Front Panel Touch Screen Specification]<br />
** Lithium Battery information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/ncr18650b.pdf Panasonic NCR18650B 3350mAH Lithium Ion Battery Specification]<br />
** Ethernet PHY information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver]<br />
** Wifi/BT module information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]<br />
** LTE module information:<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_LTE_Specification_V1.4.pdf Quectel EC25 LTE Module Specification]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EG25-G_LTE_Specification_V1.1_Preliminary_20180522%20(002).pdf Quectel EG25-G LTE Module Specification]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25&EC21_QuecCell_AT_Commands_Manual_V1.1.pdf Quectel EC25 LTE Module AT Cammands Set Manual]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Hardware_Design_V1.3.pdf Quectel EC25 LTE Module Hardware Design Guide]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Reference_Design_Rev.D_20161111.pdf Quectel EC25 LTE Module Reference Design Guide]<br />
** Sensors:<br />
*** [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetomater Datasheet]<br />
*** [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS Datasheet]<br />
*** [https://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]<br />
<br />
<br />
<br />
= Software and OS Image Downloads =<br />
<br />
== Postmarket OS Early Alpha test build [microSD Boot] ==<br />
<div style=float:right>[[File:postmarketos.png|right|100px]]</div><br />
* Suitable for PinePhone "Don't Be Evil" Dev Kit version 1.1 and version 1.2<br />
* There are two type of LCD panels. For long touch screen cable, please use the build with inverted wording.<br />
* DD image (for 8GB microSD card and above)<br />
** [https://images.postmarketos.org/pinephone/ Direct download from postmarketOS image site]<br />
** [https://wiki.postmarketos.org/wiki/Pine_Don%27t_be_evil_devkit_(pine-dontbeevil) postmarketOS PinePhone "Don't Be Evil" dev kit wiki site]<br />
<br />
== UBPorts mainline build ==<br />
<div style=float:right>[[File:ubports.png|right|100px]]</div><br />
* [https://ci.ubports.com/job/rootfs-pinephone/ UBPorts Jenkins for PinePhone]<br />
<br />
The link above seems to be broken, if so try this:<br />
[https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ Jenkins Project rootfs-pinephone]<br />
<br />
== KDE Plasma Mobile build ==<br />
<div style=float:right>[[File:plasma_mobile.png|right|100px]]</div><br />
* Not Yet Ready *<br />
<br />
== Sailfish OS build ==<br />
<div style=float:right>[[File:sailfishos.png|right|100px]]</div><br />
The Sailfish OS image is build on Gitlab CI, the latest image can be installed using our [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script] written in Bash.<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card.<br />
<br />
'''Instructions:'''<br />
<br />
1. Download the flashing script<br />
<br />
2. Insert a microSD card in your device<br />
<br />
3. Make the script executable: <code>chmod +x flash-it.sh</code><br />
<br />
4. Execute it: <code>./flash-it.sh</code><br />
<br />
5. Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
'''Note''': The script will format and flash the SD card, make sure that you don't have any important data on the SD card!<br />
<br />
<br />
== Maemo Leste build ==<br />
<div style=float:right>[[File:maemo_leste.png|right|100px]]</div><br />
* Works on dev kit versions 1.1 and 1.2 <br />
* DD image to a micro SD (8GB+) or eMMC <br />
** [https://maedevu.maemo.org/images/pinephone-dontbeevil/ Maemo Leste test builds download]<br />
<br />
== NixOS build ==<br />
<div style=float:right>[[File:nixos.png|right|100px]]</div><br />
* Not Yet Ready *<br />
<br />
== LuneOS build ==<br />
<div style=float:right>[[File:luneos.jpg|right|100px]]</div><br />
* [https://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone and thanks to Tofe]<br />
* Tofe recommends using bmaptool ; for example "bmaptool copy https://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0" <br />
<br />
== Nemo Mobile build ==<br />
<div style=float:right>[[File:nemo_mobile.png|right|100px]]</div><br />
* Not Yet Ready *<br />
<br />
= Mali-400 64-bit Driver =<br />
<br />
== Mali-400 64-bit Driver [20171220] ==<br />
* [[Mali_Driver|Mali 64-bit X11 and Wayland Driver Download]]<br />
<br />
<br />
== Quick Links to Build Sources of OS Images ==<br />
* [https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix A64 mainline status matrix chart]<br />
<br />
'''Some these OS images labelled as <span style="color:#FF0000">beta or nightly builds</span> which means they are only fit for testing purposes<br />
<br />
'''These images should be <span style="color:#FF0000">used at your own risk</span> and are not fit for normal use'''<br />
<br />
* [https://github.com/anarsoul/linux-build/releases/latest Arch Linux XFCE]<br />
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ longsleep BSP Linux]<br />
* [https://github.com/ayufan-pine64/linux-build/releases/latest/ ayufan Linux]<br />
<br />
= Errata for ver1.1 and ver1.2 board =<br />
<br />
'''1. Please DON'T insert micro SIM card to dev kit board micro SIM card slot, the SIM data, VPP, and GND signal have been misplaced. A miciPCIe adapter with sim card holder 9shown as below photo) will be provide to developers to correct this mistake.'''<br />
<br />
[[File:MiniPCIe_with_sim_slot_adapter.png|200px]]<br />
<br />
<br />
'''2. The PinePhone dev kit doesn't charge due to VBUS on SOPine module is not connected. Please connect R9688 solder pads with 0 ohm resistor or using thin wire bridge up the solder pads. Location shows as below:'''<br />
<br />
[[File:PinePhone_VBUS_charging_small.png|200px]]<br />
<br />
<br />
'''3. The SOPINE's SPI NOR flash storage and the devkit's camera flash (heh) share the same GPIO pins. The flash storage may not be used.'''<br />
<br />
[[File:SOPINE-SPI-Flash.png|200px]] [[File:Pinephone-1.1-flash-schematic.png|200px]]<br />
<br />
<br />
'''4. On the camera flash GPIO conflict, the new assignment of GPIO PB3 pin for SGM3140 FLASH_EN and GPIP PD7 for FLASH_TRIGOUT. Please note that PD7 is also LCD_ID pin which may not be used.'''<br />
<br />
[[File:GPIO_PB3_location.jpg|200px]]<br />
GPIO PB3 location<br />
<br />
[[File:U54_SGM3140_FLASH_EN pin location.jpg|200px]]<br />
U54 SGM3140 FLASH_EN pin location<br />
<br />
[[File:Flash_GPIO_Reassigned.jpg|200px]]<br />
Flash GPIOs Reassigned wiring<br />
<br />
= Other Resources =<br />
* [https://linux-sunxi.org/Pine64#Manufacturer_images Linux Sunxi Wiki page on PINE A64]<br />
* [https://github.com/apritzel/pine64 Linux Image created by Andre Przywara]<br />
* [https://github.com/longsleep/build-pine64-image PINE64 Linux build scripts, tools and instructions by Longsleep]<br />
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ PINE64 Linux image by Longsleep]<br />
* [https://softwarebakery.com/shrinking-images-on-linux Shrinking images on Linux by FrozenCow]<br />
* [https://osmocom.org/projects/quectel-modems/wiki/EC25/24 Quectel EC-25 LTE module open source information]<br />
<br />
[[Category:PinePhone]] [[Category:Allwinner A64]]<br />
[[Category:PinePhone Revisions]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_v1.0_-_Dev&diff=11705PinePhone v1.0 - Dev2021-10-23T03:33:20Z<p>KJ7RRV: </p>
<hr />
<div>The PinePhone v1.0 is the developer hardware revision of the PinePhone.<br />
<br />
This page contains resources which are exclusive to the 1.0 revision of the PinePhone. For other revisions, or for resources related to all PinePhone revisions, see [[PinePhone#Hardware revisions]].<br />
<br />
== Schematic ==<br />
* [https://wiki.pine64.org/images/3/30/PinePhone_Schematic_v1.0_20190708.pdf PinePhone v1.0 Schematic 20190708]<br />
<br />
* [https://wiki.pine64.org/images/4/41/PinePhone_mainboard_v1.0_component_placement_top.pdf Pinephone V1.0 Mainboard Top Layer Silkscreen]<br />
* [https://wiki.pine64.org/images/0/09/PinePhone_mainboard_v1.0_component_placement_bottom.pdf Pinephone V1.0 Mainboard Bottom Layer Silkscreen]<br />
* [https://wiki.pine64.org/images/d/df/PinePhone_daughterboard_v1.0_component_placement_top.pdf Pinephone V1.0 Daughterboard Top Layer Silkscreen]<br />
* [https://wiki.pine64.org/images/9/9f/PinePhone_daughterboard_v1.0_component_placement_bottom.pdf Pinephone V1.0 Daughterboard Bottom Layer Silkscreen]<br />
<br />
== Changes from Don't Be Evil ==<br />
<br />
<br />
== Known issues ==<br />
<br />
See [[PinePhone_v1.1_-_Braveheart#Known_issues|the known issues with v1.1 (Braveheart)]], which are all carried forward from v1.0.<br />
<br />
<br />
[[Category:PinePhone]]<br />
[[Category:PinePhone Revisions]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=Category:PinePhone_Pro&diff=11704Category:PinePhone Pro2021-10-23T03:32:12Z<p>KJ7RRV: </p>
<hr />
<div>Articles related to [[PinePhone Pro]]<br />
[[Category:PinePhone]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_Pro&diff=11667PinePhone Pro2021-10-18T04:55:55Z<p>KJ7RRV: </p>
<hr />
<div>[[File:Pinephone_double.png|400px|thumb|right|Rendering of the PinePhone Pro]]<br />
<br />
The '''PinePhone Pro''' is PINE64's flagship smartphone announced on October 15, 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC, which is a specialized version of the RK3399 made specifically for the PinePhone Pro.<br />
<br />
== Introduction ==<br />
<br />
== Specifications ==<br />
<br />
* '''Dimensions:''' 160.8 x 76.6 x 11.1mm<br />
* '''Weight:''' Approx. 215g<br />
* '''SIM Card:''' ?Micro-SIM?<br />
* '''Display:'''<br />
** '''Size:''' 6 inches (151mm) diagonal<br />
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™ <br />
** '''Resolution:''' 1440x720, 18:9 ratio<br />
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz<br />
* '''RAM:''' 4GB LPDDR4 @ 800MHz<br />
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC<br />
* '''Back [[#Camera|Camera]]:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash<br />
* '''Front Camera:''' 5MP OmniVision OV5640 front-facing camera<br />
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)<br />
* '''Communication:'''<br />
** '''[[#Modem|Modem]]:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]<br />
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28<br />
** '''LTE-TDD''': B38, B39, B40, B41<br />
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19<br />
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)<br />
** '''WLAN & Bluetooth:''' AMPAK AP6255 WiFi 11ac + Bluetooth V4.1<br />
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS<br />
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass<br />
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras<br />
* '''[[#Battery|Battery]]:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)<br />
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification<br />
<br />
== Components ==<br />
<br />
== Press ==<br />
<br />
For an overview about media of the PinePhone Pro you can use for the news, blogs, or similar see [[PinePhone Pro Press]].<br />
<br />
== PinePhone board information, schematics and certifications ==<br />
<br />
== Datasheets for components and peripherals ==<br />
<br />
== Developer works ==<br />
*[https://xnux.eu/log/#047 Megi]'s blog post about the device<br />
<br />
== External links ==<br />
* [https://www.pine64.org/pinephonepro/ Product Page]<br />
* [https://www.youtube.com/watch?v=wP2-6Z74W44 Announcement video]<br />
* [https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blog post] with the announcement<br />
<br />
<br />
[[Category:PinePhone]] [[Category:PinePhone Pro]] [[Category:Rockchip RK3399]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=Main_Page&diff=11653Main Page2021-10-16T04:27:56Z<p>KJ7RRV: </p>
<hr />
<div>PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.<br />
<br />
PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.<br />
<br />
For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo]. <br />
<br />
= Devices =<br />
<br />
[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]<br />
<br />
You can learn more about the following ARM and RISC-V devices manufactured by PINE64:<br />
<br />
* Phones: '''[[PinePhone]]''' and '''[[PinePhone Pro]]'''<br />
* Tablets: '''[[PineNote]]''' and '''[[PineTab]]'''<br />
* Smartwatch: '''[[PineTime]]'''<br />
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''<br />
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''<br />
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''<br />
* IP camera: '''[[PineCube]]'''<br />
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''<br />
<br />
= Community and Support =<br />
<br />
Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.<br />
<br />
== Chat Platforms ==<br />
<br />
PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot. The community chat platforms are the following:<br />
<br />
* '''Discord''': Use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.<br />
* '''Matrix'''<br />
* '''Telegram'''<br />
* '''IRC''': The server is <i>irc.pine64.org</i>. There is a WebIRC client on <i>www.pine64.org/web-irc</i>, but use of a dedicated client is advised. Use <code>/list</code> command to see the full list of channels.<br />
<br />
{{note|1=The activity of community members varies depending on the time of day and the number of active users, so please be patient and do not expect questions to be answered immediately.}}<br />
{| class="wikitable"<br />
! Channel !! Matrix !! Telegram !! IRC<br />
|-<br />
| PINE64 News<br />
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]<br />
| [https://t.me/PINE64_News @PINE64_News]<br />
| Unavailable<br />
|-<br />
| General PINE64 chat<br />
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]<br />
| [https://t.me/mtrx_pine64 @mtrx_pine64]<br />
| #pine64<br />
|-<br />
| PINE A64(+), A64-LTS & SOPine<br />
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]<br />
| [https://t.me/pine64sopine @pine64sopine]<br />
| #lts-sopine<br />
|-<br />
| ROCK64 / ROCKPro64<br />
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]<br />
| [https://t.me/mtrx_rock64 @mtrx_rock64]<br />
| #rock64<br />
|-<br />
| Quartz64<br />
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]<br />
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]<br />
| #quartz64<br />
|-<br />
| Quartz64 Development<br />
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]<br />
| [https://t.me/q64dev @q64dev]<br />
| #quartz64-dev<br />
|-<br />
| Pinebook and Pinebook Pro<br />
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]<br />
| [https://t.me/mtx_pinebook @mtx_pinebook]<br />
| #pinebook<br />
|-<br />
| PinePhone<br />
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]<br />
| [https://t.me/pinephone @pinephone]<br />
| #pinephone<br />
|-<br />
| PineNote<br />
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]<br />
| [https://t.me/pinenote @PineNote]<br />
| #pinenote<br />
|-<br />
| PineTab<br />
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]<br />
| [https://t.me/PineTab @PineTab]<br />
| #pinetab<br />
|-<br />
| PineTime<br />
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]<br />
| [https://t.me/pinetime @pinetime]<br />
| #pinetime<br />
|-<br />
| PineTime Development<br />
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]<br />
| [https://t.me/pinetime_dev @pinetime_dev]<br />
| #pinetime-dev<br />
|-<br />
| Pinecil<br />
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]<br />
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]<br />
| #pinecil<br />
|-<br />
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable<br />
|-<br />
| Cube<br />
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]<br />
| [https://t.me/pinecube @pinecube]<br />
| #cube<br />
|-<br />
| Nutcracker<br />
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]<br />
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]<br />
| #nutcracker<br />
|-<br />
| LoRa<br />
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]<br />
| [https://t.me/pine64lora @pine64lora]<br />
| #lora<br />
|-<br />
| Off-topic<br />
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]<br />
| [https://t.me/pine64offtopic @pine64offtopic]<br />
| #Offtopic<br />
|}<br />
There is an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.<br />
<br />
== Forums ==<br />
<br />
PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.<br />
<br />
The official PINE64 forum can be accessed here:<br />
* [https://forum.pine64.org/ Official PINE64 Forum]<br />
<br />
Also, these are the official Subreddits:<br />
<br />
* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]<br />
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]<br />
<br />
= Helpful Information for Beginners =<br />
<br />
* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules<br />
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.<br />
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_Pro&diff=11652PinePhone Pro2021-10-15T22:21:32Z<p>KJ7RRV: /* Press */</p>
<hr />
<div>[[File:Pinephone_double.png|400px|thumb|right|Rendering of the PinePhone Pro]]<br />
<br />
The '''PinePhone Pro''' is PINE64's flagship smartphone announced in October 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC.<br />
<br />
== Introduction ==<br />
<br />
== Specifications ==<br />
<br />
* '''Dimensions:''' 160.8 x 76.6 x 11.1mm<br />
* '''Weight:''' Approx. 215g<br />
* '''SIM Card:''' ?Micro-SIM?<br />
* '''Display:'''<br />
** '''Size:''' 6 inches (151mm) diagonal<br />
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™ <br />
** '''Resolution:''' 1440x720, 18:9 ratio<br />
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz<br />
* '''RAM:''' 4GB LPDDR4 @ 800MHz<br />
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC<br />
* '''Back [[#Camera|Camera]]:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash<br />
* '''Front Camera:''' 5MP OmniVision OV5640 front-facing camera<br />
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)<br />
* '''Communication:'''<br />
** '''[[#Modem|Modem]]:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]<br />
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28<br />
** '''LTE-TDD''': B38, B39, B40, B41<br />
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19<br />
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)<br />
** '''WLAN & Bluetooth:''' AMPAK AP6255 WiFi 11ac + Bluetooth V4.1<br />
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS<br />
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass<br />
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras<br />
* '''[[#Battery|Battery]]:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)<br />
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification<br />
<br />
== Components ==<br />
<br />
== Press ==<br />
<br />
For an overview about media of the PinePhone Pro you can use for the news, blogs, or similar see [[PinePhone Pro Press]].<br />
<br />
== PinePhone board information, schematics and certifications ==<br />
<br />
== Datasheets for components and peripherals ==<br />
<br />
== Developer works ==<br />
*[https://xnux.eu/log/#047 Megi]'s blog post about the device<br />
<br />
== External links ==<br />
* [https://www.pine64.org/pinephonepro/ Product Page]<br />
* [https://www.youtube.com/watch?v=wP2-6Z74W44 Announcement video]<br />
* [https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blog post] with the announcement<br />
<br />
<br />
[[Category:PinePhone]] [[Category:PinePhone Pro]] [[Category:Rockchip RK3399]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=Category:PinePhone_Pro&diff=11628Category:PinePhone Pro2021-10-15T16:33:23Z<p>KJ7RRV: Created page with "Articles related to PinePhone Pro"</p>
<hr />
<div>Articles related to [[PinePhone Pro]]</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_Pro&diff=11623PinePhone Pro2021-10-15T14:30:26Z<p>KJ7RRV: </p>
<hr />
<div>The PinePhone Pro is an upgraded [[PinePhone]]. It has 4 GB RAM and 128 GB eMMC, and has a hexa-core RK3399S processor. The RK3399S is a special version of the RK3399 made specifically for the PinePhone Pro.</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_Pro&diff=11622PinePhone Pro2021-10-15T14:28:19Z<p>KJ7RRV: Created page with "The PinePhone Pro is an upgraded PinePhone."</p>
<hr />
<div>The PinePhone Pro is an upgraded [[PinePhone]].</div>KJ7RRVhttps://wiki.pine64.org/index.php?title=PinePhone_Carrier_Support&diff=11572PinePhone Carrier Support2021-10-06T15:33:29Z<p>KJ7RRV: /* North America */ TracFone works</p>
<hr />
<div>{{under construction}}<br />
<br />
{{hint|MMS currently doesn't work in any distribution on the PinePhone without a [[PinePhone_Carrier_Support#MMS_workarounds|script]]! This means images and group chats will not work in text messages.}}<br />
<br />
This page contains hints on setting up cellular network connectivity for specific carriers.<br />
For more general information, see the carrier support section of [[PinePhone#Modem]]. For the APN settings see [[PinePhone APN Settings]].<br />
<br />
= Check compatibility =<br />
To check if the PinePhone is supported on your carrier:<br />
<br />
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 in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).<br />
<br />
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.<br />
<br />
= Tested and working carriers =<br />
<br />
The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):<br />
<br />
== Asia ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021<br />
|-<br />
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021<br />
|-<br />
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021<br />
|-<br />
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021<br />
|}<br />
<br />
== Africa ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Europe ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21<br />
|-<br />
| UK || Sky Mobile || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021<br />
|-<br />
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || Free || Yes || Not tested || Yes || Not tested || ArchLinux - 30 July 2021<br />
|-<br />
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021<br />
|-<br />
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date) with Phosh, 2021-06-07<br />
|-<br />
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28<br />
|-<br />
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma<br />
|-<br />
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30<br />
|-<br />
| Hungary || Telenor || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24<br />
|-<br />
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30<br />
|-<br />
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15<br />
|-<br />
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15<br />
|-<br />
|}<br />
<br />
== North America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| USA || T-Mobile || Yes || No || Yes || Yes || <br />
* Arch Linux Arm 2020/11/29 <br />
* Mobian - Phosh <br />
* Manjaro - KDE Plasma Mobile<br />
|-<br />
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm (Phosh,SXMO) 2021/04/29 <br />
*Manjaro - Phosh 2021/04/29 <br />
*Mobian - Phosh 2021/3/20<br />
|-<br />
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy || <br />
*Manjaro - Plasma Dev 2020/11/21 <br />
*Ubuntu Touch - 2020/11/26 <br />
*KDE Neon 2020/11/02<br />
|-<br />
| USA || Mint Mobile (T-Mobile) || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/14<br />
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26<br />
*Ubuntu Touch 2021/5/24<br />
|-<br />
| USA || Tello (T-Mobile) || Yes || No || Yes || Yes || <br />
*postMarketOS - Phosh 2021/8/15<br />
|-<br />
| USA || TracFone (T-Mobile) || Yes || Not tested || Yes || Yes || <br />
*Arch - Phosh 2021-10-06<br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/1<br />
|-<br />
| USA || Verizon || No || No || No || No ||<br />
*Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes) <br />
|-<br />
| USA || Verizon || Not tested || Not tested || Yes || Not via gui || <br />
*Manjaro - KDE Plasma Mobile 2021/5/10 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Not via gui || <br />
*Manjaro - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*postmarketOS - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Arch - Phosh 2021/5/31 <br />
|-<br />
| Canada || Freedom || Yes || Not tested || Yes || Yes || <br />
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25 <br />
|-<br />
| USA || FaithWireless (AT&T) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 2021/04/29 (version 0.10.1-1, see the [[PinePhone_Carrier_Support#AT.26T|AT&T issues]] below.)<br />
|-<br />
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes || <br />
*Manjaro - Phosh 2021/06/26<br />
|-<br />
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 0.10.2 2021/05/29<br />
|-<br />
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||<br />
*PostmarketOS - sxmo edge 2021/09/09<br />
|-<br />
|}<br />
<br />
== South America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Australia / Oceania ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Middle East ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Israel|| Cellcom prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
|-<br />
| Israel|| Golan TC || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Partner prepay || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Pelephone prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Hot prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| 019 prepay|| No || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
= Special carrier notes =<br />
<br />
{{Warning|This section contains providers which do not work or require special settings or actions to work.}}<br />
<br />
Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:<br />
<br />
== USA ==<br />
=== AT&T ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. The PinePhone seems to work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. VoLTE is as yet untested.<br />
<br />
However, it is likely AT&T will drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.<br />
<br />
=== Consumer Cellular ===<br />
<br />
Consumer Cellular is a MVNO that uses both AT&T and T-Mobile networks. On the AT&T network LTE data works without special configuration. If you transfer a SIM card from another phone to the PinePhone, you may need to contact customer support in order for them to register the IMEI association to the correct hardware; in one case it was first incorrectly identified as a Samsung Google Nexus Prime before later being correctly identified by the modem model Quectel EG25-G. Customer support also explicitly enabled VoLTE on the device. After VoLTE instructions on this site were followed and APN instructions on the Consumer Cellular site were followed, VoLTE was confirmed working.<br />
<br />
=== Cricket Wireless ===<br />
Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).<br />
<br />
=== SimpleMobile ===<br />
SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.<br />
<br />
=== Sprint ===<br />
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.<br />
<br />
=== T-Mobile ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).<br />
<br />
T-Mobile's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].<br />
<br />
While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.<br />
<br />
=== Verizon ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.<br />
<br />
Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.<br />
<br />
=== Google Fi ===<br />
Only T-Mobile service works currently, not US Cellular or Sprint.<br />
The APN is h2g2.<br />
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].<br />
<br />
Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps. <br />
<br />
It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.<br />
<br />
== Europe ==<br />
=== Telekom Germany ===<br />
With low signal, there may be loud interference noise audible in calls on the receiving end. It has not yet been tested whether or not this problem is carrier specific. An easy fix is extending the modem antenna with aluminum foil (or similar) inside the back cover of the phone.<br />
<br />
= Known issues =<br />
Known issues:<br />
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.<br />
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.<br />
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.<br />
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].<br />
<br />
= MMS workarounds =<br />
These scripts allow partial MMS support on a [[PinePhone]]:<br />
<br />
* JMMS: [https://git.sr.ht/~amindfv/jmms]<br />
* silvermms: [https://gitlab.com/5ilver/silvermms]<br />
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]<br />
<br />
There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.<br />
<br />
= Resources =<br />
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]<br />
<br />
<br />
[[Category:PinePhone]]</div>KJ7RRV