PINE64 - User contributions [en]

PineTab2

2023-06-11T18:04:46Z

Dachalife: /* How-to */ added KaiOS phone

[[File:PineTab2 Front.jpg|250px|thumb|right|The PineTab2 with the detachable keyboard attached]]

The '''PineTab2''' is PINE64's successor to the original [[PineTab]] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover.

The tablet is designed around the Rockchip RK3566 processor, which features 4 energy-efficient Cortex-A55 64-bit ARM cores and enjoys good mainline Linux support. Similarly packaged RISC-V tablet is [[PineTab-V]].

Pre-orders started on the 13th of April 2023, with pricing starting at USD 159 for the 4GB/64GB version and USD 209 for the 8GB/128GB version. The PineTab2 began shipping on June 2, 2023.

== Getting started ==

The PineTab2 can be started by pressing and holding the power button for two seconds. The device is initialized at the first boot and will power-cycle while the partition table is populated.

{{Info|If the initialization process is interrupted it might lead to a corrupted operating system installation. In that case reinstall the operating system as explained below.}}

The PineTab2 ships with ''DanctNix Arch Linux'' and comes with a pre-set user and the default password <code>123456</code>.

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>alarm / 123456</code>
|}

You can create a new user and set your own password after the initial boot. To do so, go to ''system settings'' -> ''users'' and create a new profile using your preferred name and password.

== Software ==

All operating systems for the PineTab2 are delivered by community developers and partner projects. Aside from the operating system that comes pre-installed on your device, you can install and run any other operating system available for the PineTab2. Most, if not all operating systems for the PineTab2 are open and free, such as Linux and BSD.

Since most software issues will be release-specific, please see the [[PineTab2 Releases]] page for additional software related instructions, tips, and tricks.

=== Releases ===

The PineTab2 ships with ''Danctnix Arch Linux ARM''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no stable releases. All releases for the PineTab2 will be listed under [[PineTab2 Releases]] as they're released. Your contributions are wanted!

=== Installation instructions ===

The PineTab2 is capable of running different operating systems from the internal flash memory (eMMC) and from microSD card.

'''Preparing the microSD card'''

To write an operating system to the microSD card (typically called "flashing" in the community), you need to first download a compatible image from the [[#Releases|releases]] section.

Next you need to decompress the downloaded image. The images are typically compressed in an archive format such as ''xz'' to reduce the download size. If you are using a graphical tool such as ''balenaEtcher'' or ''Gnome Disks'' it will handle the decompression of the image in the flashing step automatically.

Further you need to flash the image to the microSD card. This can be done using various tools, for example ''balenaEtcher'' (recommended for new users), ''Gnome Disks'' or command-line tools such as ''cp'' and ''dd''. Insert the microSD card in a microSD card reader connected to your computer and then choose a tool of your liking.

Graphical applications:

* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

* '''Gnome Disks''' (Linux): Select the microSD card target device on the left side in the ''Disks'' list. Then select the three dot menu on the top right and click on ''Restore Disk Image...''. Select the image, verify the correct device is selected and then click on ''Start Restoring...''.

Command-line tools:

* '''cp''': <code>sudo cp '''IMAGE.img''' /dev/'''[DEVICE]'''</code>

* '''dd''': <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>

{{Info|Make sure to replace '''IMAGE.img''' and '''[DEVICE]''' with the filename of the image (double check if it is decompressed and has the file extension ''.img'') and the device name. You can use the command <code>lsblk</code> to find the device name. Make sure to flash to the whole device instead of partition 1 and that you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target. Be very careful to select the correct device, as the tools can overwrite your data when the wrong device is selected.}}

Then insert the microSD card into the PineTab2.

{{Hint|'''Note regarding the boot order:''' The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. The pre-installed bootloader on the internal memory (eMMC) tries to boot from the microSD card first. In some cases it can be required to bypass the bootloader, for example if the bootloader is corrupted or was overwritten by a bootloader with varying settings.}}

Picture of the USB UART inserted into the PineTab2. The switch to disable the eMMC and SPI is located on the top right of the image:

[[File:PineTab2 USB UARTv2.jpg|600px]]

{{Hint|To force the device to boot from the microSD card, the eMMC and the SPI can be disabled by using the debug UART adapter shipped with the device. Set the ''SD BOOT MASKROM'' switch on the adapter to the position ''ON'' and plug it into the USB/PD charging port. Then power on the tablet and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the eMMC.}}

It should now boot the new operating system from the microSD card.

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''SoC:''' Rockchip RK3566
* '''CPU:''' 4x ARM Cortex-A55 @ 1.8 GHz
** 32KB L1 Instruction Cache and 32KB L1 Data Cache per core
** 512KB unified system L3 cache
** ARMv8 Cryptography Extensions
* '''GPU:''' Mali-G52 MP2 @ 800 MHz
** Supported by the open source 'Panfrost' driver in Linux and Mesa
** Supports OpenGL 3.1 and OpenGL ES 3.1 with many newer extensions
* '''NPU:''' 0.8 TOPS Neural Processing Unit
* '''RAM:''' 4GB or 8GB LPDDR4
* '''Storage:'''
** 64GB or 128GB internal eMMC ([https://www.szyuda88.com/product-77313-276594.html SiliconGo SGM8 100C-S36BCG]; eMMC 5.1, up o 400MB/s)
** 1x MicroSD slot
* '''Display:''' 10.1" IPS LCD Resolution 1280x800
* '''Cameras:'''
** Front: 2Mpx, chipset: Galaxycore GC02M2
** Rear: 5Mpx, chipset: Omnivision OV5648
* '''Battery:''' 6000 mAh (22.2Wh)
* '''Buttons:''' Power, volume up, volume down
* '''Network:'''
** Wi-Fi
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 (bottom, device mode by default; power input)
** 1x MicroHDMI
** 1x 4 pole 3.5mm audio jack (microphone right) and headphone detection
** 2x speakers + microphone (microphone left)
** 1x 5 pin (USB 2.0; <=680mA) Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''Multimedia:'''
** rkdjpeg: 1080p120 JPEG decode
*** no driver in mainline yet
** hantro: JPEG/VP8/H.264 encode, 1080p MPEG-2/H.263/VP8/H.264 AVC decode
*** mainline driver does not yet support all codecs/functions
*** see [[Mainline Hardware Decoding]] and [[Mainline Hardware Encoding]]
** rkvdec2: 4K H.264 AVC Main10 L5.1/H.265 HEVC Main10 L5.1/VP9 Profile 0 and 2 L5.1 decode
*** no driver in mainline yet
** rkvenc2: 4K H.264 AVC/H.265 HEVC encode
*** no driver in mainline yet
* '''Build:''' Metal and Plastic
* '''Dimensions:''' 242x161x9mm
* '''Misc:'''
** Protective cover with keyboard

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

Linux mainline is already quite far along for the device, as the SoC is the same as is used in the Quartz64 line of devices. Some minor pinetab2-specific adjustments can be found [https://github.com/TuxThePenguin0/linux/tree/device/pine64-pinetab2_stable here] Check the main article for the big picture; PineTab2 specific issues are listed here.

=== Known Issues ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs porting/major cleanup. This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* Suspend does not currently work due to a driver issue. Suspend is disabled in the factory image for your protection. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

The USB-C UART adapter can be connected to the PineTab2 to debug boot issues at the early boot:

* Plug the adapter in the USB-C port furthest away from the power button
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>

== Board information, schematics and certifications ==

[[File:PPineTab2-pcb.jpg|thumb|right|PineTab2 Board]]

PineTab2 mainboard schematic:

* [https://files.pine64.org/doc/PineTab/PineTab2_V2_schematic-20230417.pdf PineTab2 mainboard Released Schematic-20230417 ver 2.0]

PineTab2 certifications:
* [https://fccid.io/2A8NB-PINETAB2 FCC: 2A8NB-PINETAB2]

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:

* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet]
* [https://opensource.rock-chips.com/images/2/26/Rockchip_RK3568_TRM_Part1_V1.3-20220930P.PDF Rockchip RK3566 and RK3568 TRM (Technical Reference Manual)]

== Frequently Asked Questions ==

=== Does the Tablet support a Pen? ===

No, adding a digitiser for pen inputs would make the price too high.

=== Can I run Android on it? ===

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

=== Is there SPI Flash? ===

Yes! A 128 Mbit flash chip (sk25lp128) is reportedly present on production devices.

=== My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this? ===

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

=== How does the Tablet compare to a Pinebook Pro? ===

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

=== What is the Performance of the PineTab2 compared to the PineTab-V? ===

The PineTab2 is notably faster than the PineTab-V. You can see this by [https://github.com/ThomasKaiser/sbc-bench/blob/master/Results.md comparing the Quartz64 sbc-bench results to the Star64 ones]. Performance should not be a factor of consideration when purchasing a PineTab-V.

=== Does PineTab2 play back DRM'd Content such as Netflix? ===

Yes. Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

=== I only know Python, can I help with drivers? ===

Yes, if you learn C first. If that's too big of a hurdle, then no. (This response isn't trying to be snarky, this question was asked so many times it really needed to be here.)

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, plug the included debug adapter into the charging USB-C port and switch the white switch to its "ON" position to bypass eMMC/SPI boot. This tries to boot from SD, and if no SD is inserted, enters Maskrom mode.

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

==== Performing USB Tethering with a KaiOS phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use a KaiOS phone for mobile Internet use with your PineTab2.

You'll need:

* A KaiOS phone
* A USB OTG adapter (hama #00200311 tested)
* Your device’s charging cable
* Some knowledge of your KaiOS phone

Do the following in order:

* Plug the device into the PineTab2 using the USB cable and a USB OTG adapter
* On your KaiOS phone, open settings (specifics from here may vary on version)
* Navigate to "Network & Connectivity"
* Navigate to "Internet Sharing"
* Select "USB" and select On under USB tethering (Note: This option will be greyed out unless connected to the PineTab2)

You should now see a new network interface on the PineTab2 and it should show a wired connection icon.

== External Links ==

* [https://www.pine64.org/2022/12/15/december-update-merry-christmas-and-happy-new-pinetab/ December 2022 Community Update]
* [https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ February 2023 Community Update]

[[Category:Rockchip RK3566]]

PinePhone APN Settings

2022-08-26T18:56:47Z

Dachalife: /* Telenor (Hungary) */ Updated for telco name change

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.

= Setting the APN =

The location of the APN setting depend on the user interface the distribution is using.

== Distributions with Phosh ==

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).



= List of tested carriers =

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.

== 4ka (Slovakia) ==
Name: 4ka Internet
APN: internet
Username: <empty>
Password: <empty>

Source: https://www.4ka.sk/vitajte/navody-a-nastavenia/detail-navodu

== AT&T-based ==

=== AT&T (USA) ===
APN: NXTGENPHONE
MMSC: http://mmsc.mobile.att.net
MMS proxy: proxy.mobile.att.net

APN: <code>phone</code> may alternatively work. (see

Source: https://www.att.com/support/article/wireless/KM1218306/

=== AT&T Mexico (Mexico) ===

APN: <code> wap.attmex.mx </code>

=== Cricket (USA) ===
APN: <code>phone</code> or <code>ndo</code> or <code>NXTGENPHONE</code>

== Blau.de (Germany) ==
APN: internet.eplus.de
Username: eplus
Password: gprs

Source: https://www.my-gps.org/412-apn-einstellungen-deutschland

== Bouygues Telecom (France) ==
Name: Bouygues Telecom
APN: mmsbouygtel.com
Username: <empty>
Password: <empty>

Source: https://www.assistance.bouyguestelecom.fr/s/article/parametrage-mobile-email-mms-internet

== Congstar - Telekom Net (Germany) ==
Name: Telekom Internet
APN: internet.telekom
Username: telekom
Password: telekom

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]

Name: Congstar Internet
APN: internet.telekom
Username: congstar
Password: cs

== Eastlink Wireless (Canada) ==

Name: Eastlink Internet
APN: wisp.mobi.eastlink.ca
Username: <empty>
Password: <empty>

Source: https://www.apnsettings.org/canada/eastlink-ca/

== Free (France) ==

Name: Free
APN: free
Username: free
Password: <empty>

Source: https://mobile.free.fr/assistance/46.html

== Freedom Mobile (Canada) ==

Name: 1
APN: internet.freedommobile.ca
Username: <empty>
Password: <empty>

== Google Fi (USA) ==

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.

Name: Google Fi
APN: h2g2
Username: <empty>
Password: <empty>

Source: https://support.google.com/fi/answer/6330195?hl=en

== Hofer Telekom (Austria) ==

Name: HoT Internet
APN: webaut
Username: <empty>
Password: <empty>

Source: https://www.hot.at/config/faqs/HoT_Einstellungen_Endgera_te.pdf

== kölbi (Costa Rica) ==
Name: Costa Rica:Kolbi:Internet
APN: kolbi3g
Username: <empty>
Password: <empty>

Note: alternatively <code>kolbi4g</code> also works as APN.

== Koodo (Canada) ==

Name: Internet/MMS 2
APN: sp.koodo.com
Username: <empty>
Password: <empty>

Source: https://www.4gapn.com/ca/en/koodo

== KT (South Korea) ==

Name: KT LTE
APN: lte.ktfwing.com
Username: <empty>
Password: <empty>

Name: KT 3G
APN: alwayson.ktfwing.com
Username: <empty>
Password: <empty>

Note: APN automatically detected in Manjaro Phosh. Use either KT LTE or KT 3G according to your subscription.

== Lebara (UK) ==
Name: Lebara
APN: uk.lebara.mobi
Username: wap
Password: wap

These settings work on 4G.

Ignore Default/asdamobiles.co.uk APN if present.

== Magenta LTE (Austria) ==

Name: Magenta
APN: internet.t-mobile.at
Username: t-mobile
Password: tm

Source: https://www.magenta.at/faq/entry/%7Etechnische-anfrage%7Esmartphone%7Efunktionen%26dienste/%7EInternet_APN%7Emaster

== Mineo (Japan) ==

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

Name: Mineo
APN: mineo-d.jp
Username: mineo@k-opti.com
Password: mineo

Source: https://support.mineo.jp/manual/network_setup_d.html

== Mint Mobile (USA) ==

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.

Use the following APN settings:

Name: Ultra
APN: Wholesale

Source: https://www.mintmobile.com/setup-for-android/

== Mobile Vikings (Belgium) ==

Name: Mobile Vikings
APN: web.be
Username: web
Password: web

Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-

If the first one doesn't work try this one:

Name: Mobile Vikings
APN: web.be
Username: <empty>
Password: <empty>

Source: autoconfig on ubports

== Movistar (Colombia) ==

Name: Movistar Internet
APN: internet.movistar.com.co
Username: movistar
Password: movistar

== Orange Telecom (France) ==
Name: Orange Internet
APN: orange
Username: orange
Password: orange

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

== Orange (Poland) ==
Name: Internet IPv4
APN: internet
Username: internet
Password: internet

Source: https://www.orange.pl/omnibook/konfiguracja-internetu-mms-sms-w-telefonie#

Note: don't forget to activate sim-card using official android/ios app.

== Patriot Mobile (USA T-Mobile) ==
Internet
<pre>
Name: T-Mobile
APN: Fast.t-mobile.com
Username: <empty>
Password: <empty>
</pre>
MMS (requires chatty v0.6.1 and mmsd-tng v1.8) 
in /home/alarm/.mms/modemmanager/mms
<pre>
[Modem Manager]
CarrierMMSC=http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS_APN=Fast.t-mobile.com
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true

[Settings]
UseDeliveryReports=false
TotalMaxAttachmentSize=600000
MaxAttachments=25
AutoCreateSMIL=true
ForceCAres=false
</pre>

Source: https://www.t-mobile.com/support/devices/not-sold-by-t-mobile/byod-t-mobile-data-and-apn-settings

== Penny Mobil (Germany) ==

APN settings:

name: Penny Mobil
APN: internet.t-mobile
username: t-mobile
password: tm

== Public Mobile (Canada) ==
Internet only, mms not tested.

Name: Public Mobile
APN: sp.mb.com
Username: <empty>
Password: <empty>

Source: https://productioncommunity.publicmobile.ca/t5/Phones-Hardware/How-do-I-set-up-data-APN-on-my-smartphone/td-p/3

== Red Pocket (USA) ==

You can choose AT&T, Verizon, T-Mobile or Sprint network.

APN settings:

name: Red Pocket
APN: RESELLER

== Rogers (Canada) ==

Name: 4G/LTE Rogers Data
APN: ltemobile.apn
Username: <empty>
Password: <empty>

Name: 3G Rogers Data
APN: internet.com
Username: wapuser1
Password: wap

Source: https://communityforums.rogers.com/t5/Wireless-Knowledge-Base/Rogers-APN-Settings/ta-p/410438,

== Simyo (Spain) ==

APN settings:
APN: orangeworld

Source: https://blog.simyo.es/simyo-configuracion-internet-wap-mms/configura-tu-movil/

== SFR (France) ==

APN settings:
Name: SFR webphone
APN: sl2sfr
username: <empty>
password: <empty>

Source: https://assistance.sfr.fr/tel-mobile/utilisation-param/parametrer-apn-sfr-mobile.html

== Sunrise (Switzerland) ==

Name: Sunrise
APN: internet
Username: <empty>
Password: <empty>

== Swisscom (Switzerland) ==

Name: Swisscom
APN: gprs.swisscom.ch
Username: <empty>
Password: <empty>

== Tele2 (Sweden) ==
Name: tele2
APN: 4G.tele2.se
Username: <empty>
Password: <empty>

Source: https://www.tele2.se/support/felsokning-guider/tjanster-installningar/mms-och-data

== Telekom (Germany) ==

APN settings:

Name: Telekom
APN: internet.t-mobile
Username: t-mobile
Password: tm

Source: https://www.telekom.de/hilfe/mobilfunk-mobiles-internet/mobiles-internet-e-mail/apn-mobilfunk/wie-lauten-die-apn-fuer-mobilfunk?samChecked=true

== Telekom (Hungary) ==

APN settings:

Name: Default
APN: internet.telekom
Username: <empty>
Password: <empty>

== Telenor/Yettel (Hungary) ==

Name: Telenor
APN: online
Username: <empty>
Password: <empty>

Source: https://apn.how/hungary/telenor-hungary

== Telenor (Sweden) ==

Name: Telenor SE
APN: services.telenor.se
Username: <empty>
Password: <empty>

Source: https://www.telenor.se/kundservice/vanliga-fragor/min-mobil-surfplatta/vad-har-telenor-for-apn-installningar/

== Telia (Finland) ==
Name: internet
APN: internet
Username: <empty>
Password: <empty>

== Tello (USA) ==

Name: T-Mobile
APN: fast.t-mobile.com
Username: <empty>
Password: <empty>

MMS settings:

MMSC: http://wholesale.mmsmvno.com/mms/wapenc
APN: fast.t-mobile.com
Proxy: <empty>

== Telstra (Australia) ==

Name: Telstra Internet/WAP
APN: telstra.iph
Username: <empty>
Password: <empty>

== Three (UK) ==

Name: 3
APN: three.co.uk
Username: <empty>
Password: <empty>

== Ting (USA) ==
Using the X3 sim card:
Name: Ting Data
APN: wireless.dish.com
Username: <empty>
Password: <empty>

For MMS configuration had success using:
MMSC: http://wholesale.mmsmvno.com/mms/wapenc

The article mentions using this APN for a hotspot, but unconfirmed
Name: Ting Hotspot
APN: tethering.dish.com
Username: <empty>
Password: <empty>

Source: https://help.ting.com/hc/en-us/articles/205428698-APN-setup-guide#android-apn-settings-with-the-x3-sim-card-0-1

== Tracfone (USA) ==

''BYOP SIM Card Kit'' works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit.

3G/4G data known to work with Verizon & AT&T SIMs (most likely works for T-Mobile as well).

Use the following APN settings:

Name: Tracfone
APN: RESELLER
Username: <empty>
Password: <empty>

To use Verizon's network:

Name: Tracfone
APN: TRACFONE.VZWENTP
Username: <empty>
Password: <empty>

MMS has worked with the following settings:

MMSC: http://mmsc.cingular.com
MMS Proxy: proxy.mvno.tracfone.com

== T-Mobile (Czech Republic) ==

Name: T-Mobile CZ
APN: internet.t-mobile.cz
Username: <empty>
Password: <empty>

== Verizon Contract (USA) ==

There are several APN names which can be used, for example:

Name: 4G LTE Contract
APN: vzwinternet
Username: <empty>
Password: <empty>

Other APN names which appear, and may work if the above does not:

vzwapp
vzwims

== Videotron (Canada) ==

Name: Videotron
APN: media.ng
Username: free
Password: <empty>

== Virgin Mobile (Canada) ==

Settings might work with Bell Canada too since it is the same network.

Name: Mobile Fast Web
APN: pda2.bell.ca
Username: <empty>
Password: <empty>

== Vodafone (Czech Republic) ==
Name: internet
APN: internet
Username: <empty>
Password: <empty>

Source: https://www.vodafone.cz/pece/osobni-a-firemni/otazky/zaciname-s-chytrym-telefonem/pripojeni-nastaveni-internetu-v-telefonu/

== Vodafone (UK) ==
Name: Vodafone
APN: wap.vodafone.co.uk
Username: wap
Password: wap

These settings work on 4G.

Ignore Default/asdamobiles.co.uk APN if present.

== winSIM (Germany) ==
Name: winSIM
APN: internet
Username: <empty>
Passwort: <empty>

Source: https://service.winsim.de/help/showGeraeteeinstellungen (Requires login)

= Carriers that do not work =

== FreedomPop (USA) ==
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.

APN: <code>fp.com.attz</code>

== Sprint (USA) ==

Sprint is currently not supported due to unknown issues, see also [[PinePhone Carrier Support#Sprint]]. Any input regarding this issue is highly appreciated.

APN: <code>cinet.spcs</code>

== Visible (USA) ==

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.

== Other ==

Other VoLTE services.

= External links =

* See also https://forum.pine64.org/showthread.php?tid=9150
* LineageOS APN and MMS defaults - https://github.com/LineageOS/android_vendor_lineage/blob/lineage-19.1/prebuilt/common/etc/apns-conf.xml

[[Category:PinePhone]]

PinePhone Carrier Support

2022-08-26T18:54:45Z

Dachalife: /* Europe */ Added telco name change

{{under construction}}

This page contains hints on setting up cellular network connectivity for specific carriers.
For more general information, see the carrier support section of [[PinePhone#Modem]]. For the APN settings see [[PinePhone APN Settings]].

= Check compatibility =
To check if the PinePhone is supported on your carrier:

Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

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.

= Tested and working carriers =

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

== Asia ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021
|-
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|-
| China || China Mobile || Yes || Not tested || Yes || No || Mobile NixOS, December 2021
|-
| China || China Telecom || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022
|-
| Japan || Rakuten Mobile || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (rivised from January 2021)
|}

== Africa ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Europe ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)
|-
|-
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)
|-
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh
|-
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021
|-
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| 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
|-
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor/Yettel || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14
|-
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23
|-
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13
|-
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile
|-
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI || Modem Firmware
|-
|-
| USA || AT&T || Yes || Yes || Yes || Yes ||
* Mobian - Phosh
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || T-Mobile || Yes || Yes || Yes || Yes ||
* Mobian Bookworm (Phosh) (2022-03-08)
|| EG25GGBR07A08M2G_01.003.01.003
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm (Phosh,SXMO) 2021/04/29
*Manjaro - Phosh 2021/04/29
*Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
*Manjaro - Plasma Dev 2020/11/21
*Ubuntu Touch - 2020/11/26
*KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
*Manjaro - Phosh 2022/3/25
|-
| USA || Patriot Mobile (T-Mobile) || Yes || Yes chatty v0.6.1 mmsd-tng v1.8 || Yes || Yes ||
*Arch Linux Arm - Phosh 2022/01/12
|-
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes ||
*DanctNIX (Arch Linux ARM) - Phosh 2022-07-09
|-
| USA || TracFone || No || No || No || No ||
*postMarketOS - Phosh 2022/06/28
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| USA || US Mobile || Yes || Not tested || Yes || Not Tested ||
*Mobian - Phosh 2022/01/09
|-
| USA || Verizon || No || No || No || No ||
*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)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
*Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
*Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested ||
*Mobian - Phosh 2021/11/18
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
*Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh Weekly 2022/04/13
*PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13
*PostmarketOS - Phosh v21.12 (stable) 2022/04/13
*PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13
*PostmarketOS - sxmo edge 2021/09/09
|-
| USA || Ting || Yes || Yes - buggy || Yes || Yes ||
*Manjaro - Phosh 2021/12/10
|-
|}

== South America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Australia / Oceania ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.
|-
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.
|-
| 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).
|-
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh
|-
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)
|-
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh
|}

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| 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
|-
|-
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022
|-
|-
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-

|}

= Special carrier notes =

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

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:

== USA ==
=== AT&T ===
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.

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.

=== Consumer Cellular ===

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.

=== Cricket Wireless ===
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).

=== Faith Wireless ===
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)

=== SimpleMobile ===
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.

=== Sprint ===
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

=== T-Mobile ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).

T-Mobile's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].

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.

=== Verizon ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on
[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.

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.

=== TracFone ===
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.

=== Google Fi ===
Only T-Mobile service works currently, not US Cellular or Sprint.
The APN is h2g2.
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

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.

== Europe ==
=== Telekom Germany ===
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.

=== Orange Poland ===
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.

== Asia ==
=== China Telecom ===
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.

Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:
<pre>
AT+QMBNCFG="autosel",0
AT+QMBNCFG="select","ROW_Generic_3GPP"
AT+QCFG="ims",1
</pre>

=== SoftBank ===
SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS. 
A free SIM is available, but that one is data only. 
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.

ソフトバンク社のUSIMカードはIMEIロックで御座います。 
なお、Android又はiOS限定です。 
フリーSIMもありますが、これはデータのみSIMです。 
ソフトバンク社を使っているMVNOで同じ問題があるかもしれませんので、出来ればMNOはNTTドコモ又はauをご選択下さい。

= Known issues =
Known issues:
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* 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.
* 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.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

= MMS workarounds =
These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

= Resources =
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]

[[Category:PinePhone]]

Pinebook Pro Hardware Accessory Compatibility

2022-08-26T18:29:49Z

Dachalife: /* Bluetooth hardware */ added JBL Clip 3

Please test as many things as you can find with your [[Pinebook Pro]] and share the results here. Some devices which should work don't!

= Storage =

== NVMe SSD drives ==
Only PCI Express M.2 drives can work, due to the available connectivity of the Pinebook Pro. Consequently, SATA or USB M.2 cards will not work.

You need to buy and install the M.2 adapter in order to fit one, please see [[Pinebook Pro#Using the optional NVMe adapter]]

Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.

{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W PS 1: 2.00W PS 2: 2.00W PS 3: 0.1W PS 4: 0.005W APSTE Disabled by default ||
|-
| 2280 || Corsair MP400 || 1 TB || CSSD-F1000GBMP400R2 || fail || || PS 0: 5.55W PS 1: 4.49W PS 2: 3.97W PS 3: 0.0490W PS 4: 0.0018W APSTE Disabled by default ||
|-
| 2280 || Crucial P1 || 1 TB || CT1000P1SSD8 || good || With PS 2 and APST impact on battery life seems to be minimal. Running powerstat seems to confirm little additional power draw. || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.0300W PS 4: 0.0030W APSTE: enabled by default || Yes
|-
| 2280 || Crucial P2 || 500GB || CT500P2SSD8 || ok || problems loading from u-boot [http://u-boot.10912.n7.nabble.com/NVMe-boot-issues-on-RockPro64-td424863.html] || PS 0: 3.50W PS 1: 1.90W PS 2: 1.50W PS 3: 0.0700W PS 4: 0.0020W APSTE: enabled by default || No
|-
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: enabled by default || Yes
|-
| 2280 || Kingston A2000 || 1 TB || SA2000M81000G || good || || same as 250 GB || Yes
|-
| 2280 || Kingston KC2500 || 2 TB || SKC2500M82000G || good || PCB too thick for supplied holder nut, used another one || same as A2000 models above || Yes
|-
| 2280 || Kingston NV1 || 250 GB || SNVS/250G || good || Kingston's specifications claim that the 250 GB model consumes 1.5W max, but smartctl/nvme-cli report much higher values. The drive appears to be fully stable. || PS 0: 6.00W PS 1: 3.00W PS 2: 1.50W PS 3: 0.025W (non-op) PS 4: 0.004W (non-op) APSTE: enabled by default || Battery drain feels high. Not sure how to confirm APST is really working.
|-
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||
|-
| 2242 || Lexar NM520 || 256 GB || LNM520-256RBNA || good ||For some data on power use and performance, see [https://forum.pine64.org/showthread.php?tid=9029 here.] || PS 0: 3.05W PS 1: 2.44W PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].
|-
| 2280 || XPS SX8200 || 512 GB || ASX8200PNP-512GT-C || good || Performed [https://forum.pine64.org/showthread.php?tid=8322 these] steps for physical installation. Currently rooting from drive. || ||
|-
| 2280 || Intel 660p M.2 || 512 GB || SSDPEKNW512G8X1 || good || PS 1 (2.70W) will work without issues, even under heavy load. Recommended over PS 2, as PS 2 will incur an additional 80% performance penalty. APSTE shows enabled but drive does not support it. || PS 0: 3.50W PS 1: 2.70W PS 2: 2.00W || No
|-
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W PS 1: 3.00W PS 2: 2.20W APSTE Disabled by default || No
|-
| 2280 || Intel 660p M.2 || 2 TB || SSDPEKNW020T8 || good || [https://forum.pine64.org/showthread.php?tid=7524&pid=49300#pid49300 Performance tests results] || PS 0: 5.50W PS 1: 3.60W PS 2: 2.60W PS 3: 0.0300W PS 4: 0.0040W || No
|-
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes
|-
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W Need to use lower power. ||
|-
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No
|-
| 2280 || PNY CS1030 || 500GB || CS1030 || good || || PS 0: 4.50W PS 1: 2.70W PS 2: 2.16W PS 3: 0.0700W PS 4: 0.0050W APSTE: Enabled||
|-
| 2280 || PNY CS3030 || 1 TB || M280CS3030-1TB-RB || || || PS 0: 10.57W PS 1: 7.00W PS 2: 5.22W PS 3: 0.0490W PS 4: 0.0018W APSTE: ||
|-
| 2280 || Samsung 970 EVO Plus || 250 GB || MZ-V7S250BW || fail || Tested on Manjaro-ARM as root drive. Limited to PS 2 and Volatile Write Cache off gives the most stable results, but it will still hang on a hdparm test. || ||
|-
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W PS 1: 4.3W PS 2: 2.1W ||
|-
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||
|-
| 2280 || Samsung 970 PRO || 1 TB || MZ-V7P1T0BW || good || || PS 0: 6.20W PS 1: 4.30W PS 2: 2.10W PS 3: 0.04W PS 4: 0.005W APSTE: enabled by default || Yes
|-
| 2280 || Silicon Power P34A60 || 1TB || SP001TBP34A60M28 || Usable || Power eager, but doesn't seem to use all 9W all the time, only under heavy I/O || PS 0: 9W || N/A
|-
| 2280 || Silicon Power P34A60 || 256 GB || SPCC M.2 PCIe SSD || detected || ASIN B07ZH6QR8Q "Silicon Power PCIe M.2 NVMe SSD 256GB Gen3x4" / PCIe A60 || PS 0: 6.77W PS 1: 5.71W PS 2: 5.19W APSTE Enabled by default || No
|-
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||
|-
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No
|-
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board. (*Might be too power hungry. More testing needed.) || ||
|-
| 2242 || Sabrent Rocket || 1 TB || SB-RKTQ-1TB || good || || PS 0: 5.55W PS 1: 4.49W PS 2: 3.97W PS 3: 0.049W PS 4: 0.0018W APSTE: available || Yes
|-
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled Power states N/A || N/A
|-
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || ||
|-
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || ||
|-
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || good || Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W PS 1: 2.70W PS 2: 1.90W PS 3: 0.0250W PS 4: 0.0050W APSTE Disabled by default || N/A
|-
| 2280 || WD Blue SN550 || 500GB || WDC WDS500G2B0C-00PXH0 || good || || PS 0: 3.50W PS 1: 2.40W PS 2: 1.90W APSTE enabled by default with 5.9 kernel (Manjaro XFCE) || No
|-
| 2280 || WD Blue SN500 || 500GB || WDS500G1B0C || fail || Works OK on power state 2 (2.5W), but hangs the system whenever there is intense IO (peak draw) on the drive || ||
|-

| 2242 || WD PC SN520 || 256GB || SDAPMUW-256G-1101 || good || || APSTE enabled by default PS 0: 2.6W PS 1: 2.6W PS 2: 1.7W ||
|-
| 2280 || WD PC SN730 || 512GB || SDBPNTY-512G-1032 || good || No touchpad issues. Works after latest updates. ||APST enabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.0700W PS 4: 0.0025W || No
|-
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default PS 0: 5.00W PS 1: 3.50W PS 2: 3.00W||
|-
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.07W PS 4: 0.0025W||
|-
| 2280 || WD BLACK SN750 || 1TB || WDS100T3X0C-00SJG0 || mixed || Drive works as expected (so far) though with 50% reduction in battery life. Unable to set power mode (due to APST being enabled?). Also unable to suspend PineBook Pro with NVMe drive attached. From dmesg: rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout! PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x100 returns -110 PM: Devvice f8000000.pcie failed to suspend noirq: error -110 PM: no irq suspend of devices failed || APST enabled by default PS 0: 6.00W PS 1: 3.50W PS 2: 3.00W PS 3: 0.1000W PS 4: 0.0025W || No
|-
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled Power states N/A || N/A
|-
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default Power states PS 0: 3.60W PS 1: 2.60W PS 2: 2.20W PS 3: 0.005W PS 4: 0.005W ||
|-
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default PS 0: 4.50W PS 1: 2.70W PS 2: 2.16W PS 3: 0.07W PS 4: 0.002W||
|-
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||
|-
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. Higher power consumption modes cause the PBP to crash || PS 0 5.55W PS 1 4.49W PS 2 3.97W PS 3 0.0490W PS 4 0.0018W ||No
|-
| 2280 || Digifast Ace || 256 GB || DGFA256M2L01 || good ||No touchpad issues. Board not trimmed. || PS 0 6.77W PS 1 5.71W PS 2 5.19W PS 3 0.0490W PS 4 0.0018W ||Yes
|-
| 2280 || Toshiba XG6 || 256 GB || KXG60ZNV256G || good || || PS 0: 6.00W PS 1: 2.70W PS 2: 1.30W PS 3: 0.0500W PS 4: 0.0050W PS 5: 0.0030W APSTE: enabled by default || No
|-
| 2280 || SK hynix Gold P31 gen3x4 || 500 GB || SHGP31-500GM-2 || good || SvenKiljan's arch+towboot with 5.15.8-1-manjaro arm kernel ps1:574.65MB/s (ps0 0.500-2.1GB/s)343 MB/s r/w ps2:63.78-187/45.1 MB/s r/w on encrypted root /tmp || PS 0: 6.30W PS 1: 2.40W PS 2: 1.90W PS 3: 0.0500W PS 4: 0.0040W APSTE: enabled || No, see "workaround(cron job+nvme-cli)"
|-
|}

== microSD Cards ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||
|-
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds
|-
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.
|-
|SD Card || Sandisk Ultra 16GB || || fail || Works for a short period of time but locks up completely after a certain amount of written data
|-eMMC
|SD Card || Sandisk Ultra 32GB || || good || Worked fine for booting a live image so I could install an OS onto the integrated eMMC storage
|-
|SD Card || Sandisk Ultra 64GB (Old from 2015) || || fail || ^
|-
|SD Card || Sandisk Ultra Plus 64GB || || good ||
|-
|SD Card || Sandisk Ultra Plus 128GB || || good ||
|-
|SD Card || Sandisk Extreme 64GB || || good || Speeds seem a little slow (67MB/s read compared to 160MB/s rating) but response time and reliability is good
|-
|SD Card || Sandisk Extreme Pro 64GB || || good ||
|}

= USB hardware =

== USB Card Readers ==

Standalone card readers only, please; see below for multifunction devices.

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||
|-
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||
|}

== USB Networking ==

Standalone network devices only, please; see below for multifunction devices

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|-
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good ||
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|-
|USB WiFi Dongle || TP-Link TL-WN725N || 0bda:8179 || good || RTL8188EUS, Driver=rtl8188eu from MrFixit stock Debian, works better than internal Broadcom, but signal still not great, https://www.amazon.com/gp/product/B008IFXQFU/
|-
|USB WiFi Dongle || Shenzhen Dudes Tech #8541553244 || 0bda:c811 || mixed || plug/play on stock Armbian Buster with driver rtl8821cu; could not get operating driver built on MrFixit Debian or Manjaro KDE Plasma. Works 2x+ better than internal Broadcom on Armbian. https://www.amazon.com/gp/product/B07F595V22/
|-
|USB WiFi Dongle || Edimax EW-7811Un || 7392:7811 || good || Plug and play on Manjaro ARM and stock Debian from official images with driver rtl8192cu. https://www.amazon.com/gp/product/B003MTTJOY/
|}

== USB Multifunction Devices ==

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C Hub || Samsung EE-P5000 || || Power is passed through from hub to Pinebook Pro; Ethernet, HDMI, and USB-A do not work ||
|-
|USB-C Hub || Insignia NS-PU378CHM || || Power is passed through from hub to Pinebook Pro; USB-A works; HDMI does not work ||
|-
|USB-C Hub || Dell WD19TB || || Power is passed through from hub to Pinebook Pro; Ethernet and USB-A work; Neither Display Port nor HDMI work; audio not tested ||
|-
|USB-C Hub || Totu 8-in-1 || 058f:8468, 2109:0817 USB3, 1a40:0801, 2109:2817 USB2, bda:8153 RTL8153 Gigabit Ethernet || Network, USB, Card Reader, Power Good, HDMI Not Working || Amazon Smile [https://smile.amazon.com/gp/product/B07FX2LW35/]
|-
|USB-C Hub || Delock 87721 || || Network Works, USB Works, Card Reader not tested, Power Good, HDMI Works but does not show as an extra output in X. It just mirrors the default display || Delock 87721 [https://www.delock.de/produkte/G_87721/merkmale.html?setLanguage=en]
|-
|USB-3 combo hub (network, card slots, usb ports) || generic || 05e3:0610 hub, 0bda:8153 gigE, 05e3:0743 card reader || Network good, usb ports good, card reader good ||
|-
|USB-C combo hub (network, card slots, usb ports) || generic || 05e3:0612 hub, 0bda:8153 realtek gigE || Network good, usb ports fail, card reader fail ||
|-
|5-1 USB-C hub || [https://www.aliexpress.com/item/32954358411.html from aliexpress] || 05e3:0626 hub || HDMI, Network, USB-3, USB-C PD [http://www.sympato.ch/~dryak/files/usbc-dock.jpg good] || Might need changing orientation or USB-C cable
|-
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|USB-C combo hub || [https://www.amazon.com/gp/product/B07XKRGQQ2/ from Amazon] || 0c76:161f 0c45:6321 2109:0813 1a40:0101 || good || Everything works: AltMode DP, Ethernet, SD card, USB-A and C, and charging using the stock Debian, and Ubuntu.
|-
|USB-C dock || i-Tec USB-C Metal Nano Dock 4K HDMI w/ LAN || 0bda:0411 hub, 0bda:8153 ethernet || mixed || plug & play with Manjaro, HDMI tested w/ fullHD only, works but only in one polarity. Sound output works, USB hub works. HDMI output may not be recognized by Plasma if dock is connected with HDMI port disconnected. NIC recognized by kernel, but untested if link actually works. USB power delivery works only in one polarity. Unfortunately HDMI works with opposite polarity than USB PD.
|-
|USB-C dock || Planet Computers Gemini USB-C hub || 0bda:0411 hub, 0bda:8153 ethernet || good || USB works, NIC recognized by kernel, but untested if link actually works. Interestingly, dmesg shows unconnected alternate mode DP, but no connector is present. It seems as if PlanetCom actually made custom version of above i-Tec device.
|-
|USB-C dock || DELL USB-C to HDMI/VGA/Ethernet/USB 3.0 DA200g || idVendor=05e3, idProduct=0610, bcdDevice=49.70 || mixed || USB works, detected as u port usb hub, the rest is not working
|-
|USB-C dock || Lenovo ThinkPad 40A9 || 17ef:3063 17ef:1021 17ef:1026 17ef:3060 17ef:3062 17ef:1025 || mixed || USB hub works, audio device works, ethernet device works, display does NOT despite plug's orientation
|-
|USB-C Hub || CableCreation 7-in-1 USB C Hub SKU: CD0786 || 0bda:8153 2109:0817 2109:8888 2109:2817 || mostly || Works, but workaround needed for DP alt-mode. Need to have the hub plugged in, sans passthru charger, on boot. plugging in after boot causes errors in dmesg. Seems to be the exact same hardware as Insignia NS-PUCHUB219
|}

== USB C alternate mode DP ==
Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works
|-
|USB-C to HDMI adapter || Choetech HUB-H06 || || good || Advertises support for 4K@60Hz, tested up to 1080p@60Hz, worked in both Debian and Manjaro 2020-04-04
|-
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60
|-
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.
|-
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25
|-
|USB C Hub to HDMI VGA SD TF Card Reader 3USB 3.0 and USB C Power Pass-Through Port || MOKiN|| || good || tested to 1080p, sdcards can read from one write to another --Manjaro 2020-11-11 https://smile.amazon.com/gp/product/B07MP9P6B7/
|-
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||
|-
|USB-C combo hub (HDMI, VGA, Ethernet, card slots, USB 2 & 3 || Powlaken || 05e3:0610 0bda:8153 || USB, Power, Ethernet and SD good, HDMI and VGA fail
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power Passthru || Digitus DA-70865 || || USB, Ethernet and MicroSD/SD good, video crashes System (fail). || Tested on Manjaro w/ Kernel 5.5. You have to turn the USB-C connector upside down for it to work. Video seems to be a driver issue.
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power pass-through) || generic || || Ethernet and MicroSD/SD good, USB fail, video up to 1080p. || https://forum.pine64.org/showthread.php?tid=8728
|-
|USB-C Dock (DP, HDMI, 1Gbps Ethernet, SD card slot, 2 USB 3 Ports, USB-C power in port || goFanco || || DP, Ethernet & USB good, (HDMI & SD card untested). Video tested good to 1080p || Tested on default Debian
|-
|USB-C Dock (HDMI, USB 3.0 x 2, USB-C PD Pass Thru Power Port Up to 100W, SD/TF Card Reader || Hiearcool 7-in-1 || || HDMI, USB, Power Port good, SD/TF Reader fail || Default Debian
|-
|USB-C 3.0 Multi-Port Hub (HDMI, USB 3.0 x 1, USB-C charge only) || Linden LITCAD17 || || HDMI and USB good, Power Port fail || Default Debian & ayufan Ubuntu
|-
|USB-C to DP adapter || Nekteck || 04b4:5210 || good || Shows up as "Cypress Semiconductor Corp. Billboard Device" in lsusb and dmesg output. Works in latest Manjaro (as of January 26, 2020) with no issues. Only FullHD resolutions available on Debian.
|-
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60
|-
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good
|-
|USB-C Travel Dock with DP ALT-MODE || Targus DOCK411-A || 0835:2a01 (BILLBOARD DEVICE) 0bda:8153 (RTL8153 GbE Adapter) || GbE: works, HDMI: works, USB3.0 port: works, VGA: unknown || HDMI@1080p@60Hz: works OK, HDMI@4K@30Hz: works but buggy. GbE is only picked up when the USB C is plugged in with one certain side facing upwards. It is not detected the other way around. (Sounds weird, but reproduced it multiple times.)
|-
|USB-C to DP adapter || MediaGearPro AC0011 || 2109:0100 (USB 2.0 BILLBOARD) || DP: works || Only 1080p@60Hz is available, 4K resolutions not possible in contrast to what the manufacturer claims.
|-
|USB-C to DP cable || Generic on ebay || || good but with issues || Had some wonky framerates when tested on a 144hz monitor, 60hz mode was actually sent as ~48hz, 120hz mode was actually sent at ~112hz and 144hz mode was actually sent at ~120hz
|-
|UGREEN Hub USB C 9 in 1 HDMI and VGA || UGREEN || || good || VGA and HDMI works but not at the same time. HDMI audio not tested. Switching between HDMI and VGA need to replug the hub.
|-
|USB-C Dock 6-in-1 HDMI || Ugreen 50771 || || HDMI: works, Ethernet: works, 3x USB: works, USB-PD: works || Tested on Manjaro 2020/03/18 Works USB-C PD Chargers provided they can do 5V3A, works with 5V3A USB-C Raspberry Pi 4 power supply (Doesn't work with 5V2A USB-C). No HDMI Audio.
|-
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ CHOETECH V-XCP-0012BK] || || good
|-
| [https://www.apple.com/ca/shop/product/MQ4H2AM/A/thunderbolt-3-usb%E2%80%91c-cable-08-m Thunderbolt 3 (USB‑C) Cable (0.8 m)] || Apple || || Display Port Alternate Mode: Fails, USB-PD: works || Tested on Manjaro 2020/05/29 - Charges but no video
|-
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot
|-
|USB-C combo hub || Moreslan 11in1 (https://www.amazon.fr/gp/product/B08397B66G) || || good || GbE: OK, HDMI: OK, 4 usb ports: OK, Power via USB-C: OK, microSD: OK, TFT: OK, Jack: OK, VGA: Not tested; UPDATE: HDMI Display not working anymore since Manjaro release 20.08
|-
|USB-C Multiport Adapter || [https://www.wentronic.com/en/usb-ctm-multiport-adapter-hdmi-ethernet-pd-white-62105 Goobay 62105] || || Fail || GbE: OK, UBS port: OK, Power via USB-C: OK, HDMI: Does generate an image, but it jumps X pixels right from time to time (4K@30 and FHD)
|-
| USB Type-C to HDMI Adapter || Insignia NS-PU369CH-WH || 0bda:5400|| good || tested on kernel 5.5.0, video out works, audio not tested
|-
| Portable USB Display || UPerfect 15.6 inches 1080P Portable Monitor Stand for Mobile Touchscreen (https://www.uperfectmonitor.com/collections/15-6-inches-portable-monitor/products/15-6-inches-1080p-portable-monitor-stand) || || Power via USB-C: works, DP-Alt video: works, Touchscreen fails || Tested on armbian on 20210820
|}

== USB other ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Wireless Mouse || Logitech M705 Marathon || || good || Uses Logitech receiver. Battery level detected in power settings.
|-
|Wireless Mouse || Logitech G305 || || good || Uses Logitech receiver
|-
|Gamepad || Sertronics SNES Style Controller || || good || Tested in retroarch, Sertronics is also known as Berrybase
|-
|Drawing tablet || XP Pen G430s || 28bd:0913 || good || Hardware works, official software not used, tablet was configured using udev rules which are more functional than official software anyway
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|}

----

= Bluetooth hardware =
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Bluetooth Headphones || COWIN SE7 Noise Cancelling Headphones || || good || Pairs and plays audio with stock Debian OS. More detail [https://forum.pine64.org/showthread.php?tid=8192&pid=60682#pid60682 here].
|-
|Bluetooth Headphones || DO-SV-BTIES03 || || good || Tested on Manjaro ARM - kde
|-
|Bluetooth Headphones || JBL LIVE400BT || || good || Connect very rapidly. Sometimes there is some sort of lagging to the sound stream, fix includes disconnecting them from Bluetooth and turning them off. Sound quality is good.
|-
|Bluetooth Headphones || JBL LIVE650BTNC || || good || Have 2, both connect very rapidly. Sometimes there is some sort of lagging to the sound stream, fix includes disconnecting them from Bluetooth and turning them off. General sound quality is good.
|-
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.
|-
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro
|-
|Bluetooth Headset & USB Audio || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.
|-
|Bluetooth Headset || TaoTronics TT-BH090 || || good || Microphone not tested but should work as expected of a normal Linux machine
|-
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good ||
|-
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||
|-
|Bluetooth Mouse || Logitech M557 || || good ||
|-
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||
|-
|Bluetooth Mouse || Logitech MX Ergo || || good || Works flawlessly both on Manjaro and Armbian.
|-
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||
|-
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"
|-
|Bluetooth Mouse || Media-tech || MT1120 BT5.2 || good ||
|-
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||
|-
|Bluetooth Mouse || Technet || MGS479 || good ||
|-
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile
|-
|Bluetooth Speaker || JBL Clip 3 || || good || Works fine in Kali
|-
|Bluetooth Trackball Mouse || Elecom Deft Pro Wired / Wireless / Bluetooth Trackball || || good || Main buttons (left, right, forward, back, scroll wheel, trackball itself work flawlesly, but without elecom software additional buttons do not work. Works in all 3 modes - wired, with wireless USB dongle and in Bluetooth mode.
|-
|Bluetooth Trackball Mouse || Kensington Expert Wireless Trackball || || good ||
|}

----

= Other hardware =

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|[https://www.aliexpress.com/item/32831647303.html USB charging cable] || - || - || good || Got the cable a while back so may not be identical to current product
|-
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.
|-
|Printer || Samsung Xpress SL-M2026w Laser Printer || || not working || Was not able to make it work due to the lack of drivers.
|}

[[Category:PineBook Pro]]

Project

2021-10-01T18:45:53Z

Dachalife: /* Introduction and Instructions */

__TOC__

'''PINE64 Community Projects Wiki Page'''

<div style="border:1px solid #2E9CD7; background-color:#D6ECF7; padding:3px; text-align: center; margin-bottom: 5px;">
The '''PINE64''' Wiki is community-driven and can be edited by '''''anyone''''' who wishes to contribute.

'''Please remember to always login into the Wiki to see the latest updates'''. You can use your PINE64 forum login details.

There are currently '''[[Special:Allpages|{{NUMBEROFARTICLES}} projects]]''' on this wiki.
</div>
== Introduction and Instructions ==
This Wiki section offers a variety of projects for PINE64 devices. It is co-created and driven by users like yourself, so feel free to browse the listed projects or even submit your own. If you are interested in contributing a project then '''please first read''' though the following two sub-sections (on Contributing New Projects and Authorship) before entering your submission.

'''All submissions are welcome. You can submit hardware-based projects, software-based projects or a mix of the two'''. For example, you could build an NAS server enclosure for your PINE64 SBC and then create a software-based tutorial on how to take advantage of the setup you built.

If you feel that a particular theme or project type is not represented on the Wiki then please create a post about it in the relevant section on the [https://forum.pine64.org/ PINE64 forum].

=== Contributing New Projects ===

There are a number of ways in which you can contribute new projects to this Wiki section. Projects can be submitted by:
*Adding a link to a post on the forum, blog, git instructions, etc.,
*Adding a link to an article (please read about authorship in 1.2)
*Adding a [https://en.wikipedia.org/wiki/Wikipedia:How_to_create_a_page new entry to the Wiki]
*Adding a link to a video or audio file with project instructions
*Adding links to documents (e.g. Google docs, PDFs, etc,.) of images hosted on Google Drive, Imgur, etc,.
*A combination of two or more of the above

The preferable way of submitting a new project is by '''creating a new Wiki entry''' as this assures that it will be '''easy to locate''' by other users. Wiki entries can include attachments in the form of photos, videos, documents and external links (e.g. to formatted code); making them ideal for storing complex and lengthy tutorials and instructions.
That said, if you do not wish to migrate your project tutorial from another place (e.g. the forums) then a link to the complete write-up, code, video or another medium will suffice.

'''Adding an entry to the listing in the relevant project section should follow this syntax:'''

| Name || Device || Link to project || Notes about the project

=== Authorship ===

If you are the author of the submitted project, be sure to credit yourself accordingly. You are also welcome to remain anonymous if you prefer.
However, if you are linking or referencing an external project or source code that has been written up/ recorded/ created '''by someone else''' then you '''must credit the person or organisation''' that the project and/or related resources belong to.

== Gaming Projects ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | PINE64 Retro Gaming Projects
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:Retrogame_icon.png | frame | Most PINE64 devices are capable of emulating old computer and video game consoles such as the Nintendo Entertainment System. ]]
{|
|+'''Suitable Devices for this Project'''
|-
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-LTS-small_icon.png]]
! style="text-align: float:center; margin:0.46em 0.2emc; width: 175px;" | [[File:Pinebook-small_icon.png]]
! style="text-align: float:right; margin:0.46em 0.2emc; width: 175px;" | [[File:ROCK64-small_icon.png]]
|-
| PINE A64/A64+ || PINE A64-LTS/SoPine || PINEBOOK || ROCK64
|}
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-
| HeadShot || LTS/A64 || [https://forum.pine64.org/archive/index.php?thread-496.html Pine A64 in a Playstation] || Pine A64 in a Playstation Case using original controllers
|-
| Luke || A64/LTS || [https://forum.pine64.org/archive/index.php?thread-5202.html Arcade Cabinet]|| A custom built min-arcade cabinet using the Pine A64 + LCD screen
|-
| Luke/Pfeerick|| LTS/A64 || [https://forum.pine64.org/showthread.php?tid=4800 Retroarch] || Install a dedicated Retroarch build on a minimal xenial image
|-
| spoonerdee || LTS/A64/Pinebook || [https://www.youtube.com/watch?v=VM4AvsBKfMo Emulation on Android] || Video showing emulation on Pine A64 running android.
|-
| rtissera || Rock64 || [https://github.com/rtissera/RetroPie-Setup/releases/ RetroPie Early build]|| An early build of RetroPie for Rock64
|-
| Seph || Rock64 || [https://forum.gimx.fr/viewtopic.php?f=21&t=2470 GIMX on Rock64]|| GIMX allows you to use peripherals, such as mice and keyboards, on consoles using a SBC like the Rock64
|-
|}
|}

== Desktop Computer Projects ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | Desktop Applications of PINE64 SBCs
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:Computer_icon.png | frame | All PINE64 Single Board Computers are capable of acting as destkop computers. This includes a variety of Linux destkop environments (such as Mate or XFCE) as well as different types of Android. ]]
{|
|+'''Suitable Devices for this Project'''
|-
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-LTS-small_icon.png]]
! style="text-align: float:right; margin:0.46em 0.2emc; width: 175px;" | [[File:ROCK64-small_icon.png]]
|-
| PINE A64/A64+ || PINE A64-LTS/SoPine || ROCK64
|}
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-
| Swapnil Bhartiya|| A64 || [https://www.linux.com/news/build-20-computer-pine64 Debian desktop on Pine64] || Installing Debian Mate on simple image
|-
| AKINWALE|| A64/LTS || [https://nanite.co/2016/08/07/building-monodevelop-for-the-pine64/ MonoDevelop] || Install MonoDevelop integrated development environment and forward it via SSH
|-
| Ray Hightower || A64/LTS || [https://rayhightower.com/blog/2016/04/04/pine64-quick-start-guide-using-mac-os-x/ Destkop Quick Start Guide] || A desktop environment quick start guide for Pine A64
|-
|}
|}

== Network Attached Storage (NAS) Projects ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | NAS Projects
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:NAS_icon.png | frame | Most PINE64 Single Board Computers feature Gigabit Ethernet connections and multiple USB 2.0 / 3.0 ports, and are therefore well suited for domestic NAS applications.]]
{|
|+'''Suitable Devices for this Project'''
|-
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-LTS-small_icon.png]]
! style="text-align: float:right; margin:0.46em 0.2emc; width: 175px;" | [[File:ROCK64-small_icon.png]]
|-
| PINE A64/A64+ || PINE A64-LTS/SoPine || ROCK64
|}
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-
| Ptheven || A64/LTS/Rock64 || [https://forum.pine64.org/showthread.php?tid=5231 RAID 0] || A RAID 0 setup for you PINE64 SBC
|-
| Ptheven || A64/LTS/Rock64 || [https://forum.pine64.org/showthread.php?tid=5177 SMB setup] || Instructions to set up shares on your PINE64 SBC
|-
| Ptheven || A64/LTS/Rock64 || [https://forum.pine64.org/showthread.php?tid=4971 NFS share] || Instructions on how to set up an NFS share on the Rock64
|-
| Ptheven || A64/LTS/Rock64 || [https://forum.pine64.org/showthread.php?tid=4925 Adding USB Storage] || Adding USB Storage, Linux Formatting and Permissions
|}
|}

== Media Server and Player Projects ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | Media Server and Player Projects
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:Mediaplayer_icon.png | frame | All PINE64 Single Board Computers are capable of acting at media servers as well as playback devices. Dedicated Linux destributions such as LibreELEC as well as Android TV make for great couch media consumption experiences. Your device may also perform the role of a media server.]]
{|
|+'''Suitable Devices for this Project'''
|-
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-LTS-small_icon.png]]
! style="text-align: float:right; margin:0.46em 0.2emc; width: 175px;" | [[File:ROCK64-small_icon.png]]
|-
| PINE A64/A64+ || PINE A64-LTS/SoPine || ROCK64
|}
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-
| JulianM || A64 || [https://forum.pine64.org/archive/index.php?thread-1563-2.html MDP Server + Speakers] || A custom build of MDP Server and speakers using a Pine A64
|-
| Jeremy Graham || A64/LTS || [https://jez.me/article/plex-server-on-a-pine64-how-to Manual Plex Server Installation] || Manual Plex Server installation on Pine A64
|-
| Learnincurve || A64/LTS || [https://forum.pine64.org/showthread.php?tid=3482 Squeezebox] || Squeezbox on Pine A64 + LCD
|-
| Ronnie Bailey || A64/LTS || [https://hmongbuy.net/video/59_SfaBLGdk EMBY ] || EMBY server on the Pine A64
|}
|}

== Projects Utilising General Purpose Input/Output (GPIO) Pins ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | GPIO Projects
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:GPIO_icon.png | frame | All PINE64 Single Board Computers have a set of GPIO pins that you can use in your project. The PINEBOOK can also make use GPIO using different means ... you can read about them in this section.]]
{|
|+'''Suitable Devices for this Project'''
|-
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:center; margin:0.46em 0.2emc; width: 175px;" | [[File:Pinebook-small_icon.png]]
! style="text-align: float:right; margin:0.46em 0.2emc; width: 175px;" | [[File:ROCK64-small_icon.png]]
|-
| PINE A64/A64+ || PINE A64-LTS/SoPine || PINEBOOK || ROCK64
|}
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-
| machinehum and MarkHaysHarris777|| PINEBOOK || [https://forum.pine64.org/showthread.php?tid=5055 uSD Breakout] || This project allows 6 GPIO pins to be accessed via SD card slot
|-
| MarkHaysHarris777 || Pinebook/A64/LTS || [https://forum.pine64.org/showthread.php?tid=4418 PADI GPIO expansion] || PADI IoT Dongle used for GPIO Expansion
|-
| pfeerick || A64/LTS || [https://forum.pine64.org/archive/index.php?thread-2088.html GPIO Basics] || Controlling Pine64 GPIO via the filesystem (sysfs) on linux
|-
| NANITE || A64/LTS || [https://nanite.co/ Controlling an Arduino] || Controlling an Arduino connected to the PINE64 over I2C with C and C#
|-
| Rieul Techer || A64/LTS || [https://hackaday.io/project/10879/instructions Ethereum & CitizenWat]|| Ethereum and CitizenWat Installation on a Pine64+ board
|-
| TARINGA! || A64/LTSI || [https://www.taringa.net/posts/ebooks-tutoriales/19673288/Server-web-gpio-Pine64.html GPIO over web Server] || Web server for Pine A64 GPIO setup instructions
|-

|}
|}

== Server Projects ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | Server/Docker Projects
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:server_icon.png | frame | All PINE64 Single Board Computers can be used as a wide variety of servers. Common applications include LAMP and Docker servers, but a there is nearly a limitless amount of plausible server applications.]]
{|
|+'''Suitable Devices for this Project'''
|-
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:right; margin:0.46em 0.2emc; width: 175px;" | [[File:ROCK64-small_icon.png]]
|-
| PINE A64/A64+ || PINE A64-LTS/SoPine || ROCK64
|}
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-
| Hypriot OS || PINE A64/A64+/A64-LTS/SOPine || [https://blog.hypriot.com/post/the-pine-a64-is-about-to-become=the-cheapest-ARM-64-bit-platform-to-run-Docker/ Pine A64 Docker] || Docker on Pine A64, applies to other PINE64 devices
|-
| doertepn || A64/LTS/Rock64 || [https://www.youtube.com/watch?v=K6ZFws2x3qE OwnCloud tutorial] || Tutorial on manually installing OwnCloud on the Pine A64
|-
| wahdooyah || Rock64/LTS/A64 || [https://forum.pine64.org/showthread.php?tid=1167 Deluge server] || Deluged Torrent Server on the Pine A64
|-
| tomd || Rock64/A64/LTS || [https://forum.pine64.org/showthread.php?tid=829 Pi-Hole] || Pi-Hole DNS server on a Pine A64
|-
| rallar8 || A64/LTS || [https://www.reddit.com/r/pine64/comments/4xhhfr/ssh_and_pine64_as_a_server_a_guide_part_1/ Server Operation, OpenVPN, SSH] || Remotely setting up your Pine A64 Server and using using OpenVPN.
|-
| PiVPN|| Rock64/A64/LTS || [https://www.pivpn.io/ PiVPN] || Tutorial on how to set up PiVPN on a Debian-based distribution
|-
| pine64nutz || Rock64/A64/LTS || [https://forum.pine64.org/showthread.php?tid=794 VNC Server] || Install and setup a VNC server for remote destkop access
|-
| Michael Greene|| A64/LTS || [https://blog.mike-greene.com/pine64-octoprint-part-1/ Octoprint Server] || Octroprint Server on the Pine A64 installation tutorial
|-
| Michael Lenardson || Rock64/A64/LTS || [https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-nextcloud-on-ubuntu-16-04 Next Cloud] || Installation procedure that works on Pine A64/LTS and Rock64 running Ubuntu 16.04
|-
| Jose Fierro || Rock64/A64/LTS || [https://devandadmin.com/rock64-lamp-wordpress-lets-encrypt-ssl-part-1/ WordPress/Web Server] || Rock64: LAMP + WordPress + Let’s Encrypt SSL
|-
| Yuan Gao || Rock64/A64/LTS || [https://ee-fans.com/pi-dashboard Status Monitor] || Rock64: Monitor Rock64 status, like CPU usage, RAM usage, network traffic, etc. on webpage.
|-
| Yuan Gao || Rock64/A64/LTS || [https://ee-fans.com/https://ee-fans.com/how-to-install-lamp-lnmp-on-rock64-with-aapanel-2/ Web Server] || Install LAMP/LNMP on Rock64 and easily to add SSL and other things.
|}

== Cluster/Docker Computing Projects ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | Cluster Projects
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:Cluster_icon.png | frame | Have you got two or more PINE64 Single Board Computer board? Consider building a cluster. Clutering of two or more PINE64 boards presents as a fantastic oportunity to explore and learn about node failure management, task scheduling, debuggin, data sharing and much more.]]
{|
|+'''Suitable Devices for this Project'''
|-
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-LTS-small_icon.png]]
! style="text-align: float:right; margin:0.46em 0.2emc; width: 175px;" | [[File:ROCK64-small_icon.png]]
|-
| PINE A64/A64+ || PINE A64-LTS/SoPine || ROCK64
|}
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-
| Climbers.net|| PINE A64/A64+/A64-LTS/SOPine || [https://climbers.net/sbc/bargain-pine-a64-cluster/ 5 Node Cluster with PINE A64+] || Cluster in a dedicated acrylic case
|-
| Quantum Cannibal|| A64/LTS || [https://www.youtube.com/watch?v=ZCl3kZqbp3w Docker Cluster Build] || Videos detailing Docker on a Pine A64 cluster
|-
| Vivek Juneja || A64/LTS || [https://www.vivekjuneja.in/2016/08/29/arm-cloud-cluster/ Swarm Cluster] || Instructions to build a swarm cluster using Pine A64/LTS
|-
| Kurt Stam || LTS || [https://medium.com/@kurt.stam/docker-on-pine64-centos-7-arm64-b4606632f28d Docker CentOS] || Docker on a Pine A64 cluster running CentOS
|-
| DiversITEurope || A64/LTS || [https://www.diversit.eu/post/2016/07/13/running-docker-on-pine64.html Docker Installation] || Docker installation instructions for Pine A64
|-
| Mimuni || Rock64 || [https://github.com/docker/compose/issues/5198 Rock64 Docker-compose] || Build docker-compose on Rock64 Board
|-
|}
|}

== Home Automation Projects ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | Home Automation Projects
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:Homeautomation_icon.png | frame | PINE64 Single Board Computers - all equipped with milti-core SOCs and GPIO - can become an adition to, or the basis for, your home automation project. Use an existing platform like OpenHAB which is compatible with commercially available devices, add aditional functionality to MotionEye, or just hack away and make things your own.]]
{|
|+'''Suitable Devices for this Project'''
|-
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-LTS-small_icon.png]]
! style="text-align: float:right; margin:0.46em 0.2emc; width: 175px;" | [[File:ROCK64-small_icon.png]]
|-
| PINE A64/A64+ || PINE A64-LTS/SoPine || ROCK64
|}
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-
| FrankA2 || A64 || [https://www.instructables.com/id/Inexpensive-Touchscreen-Life-Command-Center-Using-/ Life Command Center]|| Display weather, email and information about home using a Pine A64
|-
| Sytone || A64/LTS || [https://www.sytone.com/2016/08/running-home-assistant-on-pine64/ Home Assistant] || Running home assistant on Pine A64
|-
| Pineadmin || LTS/A64 || [https://forum.pine64.org/showthread.php?tid=2395 Node-RED] || Install Node-RED for for wiering together hardware devices on the Pine A64/LTS
|-
| Moustage || LTS/A64 || [https://www.domoticz.com/forum/viewtopic.php?t=13142 Domoticz setup instructions] || Domoticz on Pine64 using some cheap I2C modules
|-
| Andrew Klimovski || A64/LTS || [https://andrew-klimovski.blogspot.co.uk/2017/03/home-automation-openhab2-on-pine64.html OpenHAB Basics] || Basic installation and setup of OPneHAB on Pine A64 running Ubuntu
|-
| Jewgeni R || A64/LTS || [https://www.youtube.com/watch?v=j19QPLnZRcc ioBroker] || Video about ioBroker on Pine A64 N.B. In German
|-
| Deviant Engineer || A64/LTS/Rock64 || [https://deviantengineer.com/2016/09/hass-dietpi/ Z-Wave bindings DietPi] || Z-Wave Bindings + Home Assistant installation from DietPi
|-
|}
|}

== Robotics Projects ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | Robotics Projects
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:Robotic_icon.png | frame | Use your PINE64 Single Board Computer featuring a milti-core SOCs and GPIO to have a go at robotics. Download an existing Open Source robotics project from Github or start your own; browse this section for inspiration and resources.]]
{|
|+'''Suitable Devices for this Project'''
|-
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-LTS-small_icon.png]]
! style="text-align: float:right; margin:0.46em 0.2emc; width: 175px;" | [[File:ROCK64-small_icon.png]]
|-
| PINE A64/A64+ || PINE A64-LTS/SoPine || ROCK64
|}
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-

| Name || Device || Link to project || Notes about the project

|}
|}

== PADI IoT Stamps Projects ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | PADI Projects
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:PADIstamp_icon.png | frame | PADI is a tiny microcontroller that can be used in conjunction with your PINE64 SBC or the Pinebook ]]
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-
| thomash || PADI || [https://forum.pine64.org/showthread.php?tid=4586 Programming via IDE] || Programming PADI with Arduino IDE
|-
| MarkHaysHarris777 || PADI || [https://forum.pine64.org/showthread.php?tid=2482 Programming PADI] || Programming PADI basics
|-

|}
|}

== Other Projects ==
{| style="border: 2px solid black; border-spacing: 0; margin: 1em auto;"
! style="border: 1px solid black; padding: 5px; background: #efefef;" | Other Projects
|-
| colspan="3" style="border: 1px solid black; text-align: center; border-spacing: 0" |
[[File:Otherproject_icon.png | frame | You have no doubt come up with something that we didn't think about, and that is truly great. Perhaps your project is interesting enough that it will be granted its own section. After all if you have imagination then sky is the limit.]]
{|
|+'''Suitable Devices for this Project'''
|-
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-small_icon.png]]
! style="text-align: float:left; margin:0.46em 0.2em; width: 175px;" | [[File:PINE_A64-LTS-small_icon.png]]
! style="text-align: float:center; margin:0.46em 0.2emc; width: 175px;" | [[File:Pinebook-small_icon.png]]
! style="text-align: float:right; margin:0.46em 0.2emc; width: 175px;" | [[File:ROCK64-small_icon.png]]
|-
| PINE A64/A64+ || PINE A64-LTS/SoPine || PINEBOOK || ROCK64
|}
{| class="wikitable"
! scope="col" style="width: 175px;" | Project Author(s)
! scope="col" style="width: 175px;" | Device(s)
! scope="col" style="width: 175px;" | Project Link
! scope="col" style="width: 175px;" | Notes
|-
| bits_and_wires || Pinebook || [https://forum.pine64.org/showthread.php?tid=5302 case mod] || Pinebook Case modification
|-
| MarkHaysHarris777 || Pinebook || [https://forum.pine64.org/showthread.php?tid=5026 Serial Console Cable] || Serial over 3.5 jack plug on the Pinebook
|-
| MarkHaysHarris777 || Pinebook || [https://forum.pine64.org/showthread.php?tid=5013 Case mod Serial Console] || Case mod to access serial console switch inside the case
|-
| doertepn || A64/LTS || [https://www.youtube.com/watch?v=gDcEWgvO7NA Picture frame] || A Pine A64 picture frame using an old Apple computer
|-
| vovakurz || A64/LTS || [https://ishwestscriptwault.wordpress.com/2016/12/29/running-unifi-controller-5-on-pine64-en/ Ubiquiti UAPs rely on a UniFi] || CA UniFi relay for better/Smoother WiFi roaming.
|-
| iPhyse || A64/LTS || [https://www.instructables.com/id/Holodock-Pine64/ Holodoc Project] || Instructions on creating a holographic doc using the Pine A64
|-

| carlosviansi || A64/LTS || [https://forum.pine64.org/archive/index.php?thread-423.html Weather station] || Weather Station using Pine A64 + I2C POT
|-
| KnReLe || Pine A64 || [https://forum.pine64.org/showthread.php?tid=142&pid=18238#pid18238 RTL-SDR] || RTL-SDR software that works out-of-the-box on the Pine A64
|-
| sgjava || Pine A64/LTS || [https://forum.pine64.org/showthread.php?tid=4468 Pine64 with small OLED] || Adding a small OLED screen to Pine A64
|-
| Dmoreno || Pine A64/LTS || [https://forum.pine64.org/showthread.php?tid=3078 Karaoke]|| Karaoke software running on Pine A64
|-
| wahdooyah || A64/LTS || [https://forum.pine64.org/showthread.php?tid=1219 Phone Notifications] || Pushing notifications from home network to cell phone
|-
| rontant || Rock64/A64/LTS || [https://forum.pine64.org/showthread.php?tid=4971 migrating rootfs to HDD/SSD] || Tutorial for migrating rootfs to an external diver
|-
| Ron Kamphuis || Rock64 || [https://medium.com/@perfectstormtd/deploying-full-iota-node-on-a-rock64-4gb-arm64-board-34d3f6cb473a IOTA Node] || Deploying full IOTA node on a ROCK64 4GB
|-
| Lior Pachter || Rock64 || [https://liorpachter.wordpress.com/2018/01/29/bioinformatics-on-a-rock64/ Bioinformatics on a Rock64] || Kallisto bioinformatics for computational biologists
|-
| evilbunny || Rock64 || [https://forum.pine64.org/showthread.php?tid=5723&pid=35580#pid35580/ WiFi with WebGUI] || A DIY WiFI AC AP / Router with WebGUI
|-
| rmbusy || Rock64 || [https://forum.pine64.org/showthread.php?tid=5166 Survaillance system] || A DIY surveillance system using the Rock64 running Motion
|}
|}

PinePhone Security

2021-09-27T17:50:55Z

Dachalife: /* SSH */

{{under construction}}

TODO intro

== Encryption ==

While encryption alone is not sufficient to protect sensitive data, it is an important tool to safeguard data in certain attack vectors.

=== Full-Disk Encryption ===

Full-disk encryption encrypts the entire disk (except for the boot bits). Currently some OSes such as postmarketOS and Mobian offer an installation image, which have the option to encrypt the entire disk. Some OSes, such as postmarketOS (via pmbootstrap) and Arch Arm also offer an installation script for an fully encrypted installation.

Decryption is done at boot after entering the encryption password via an on-screen keyboard (Osk-sdl).

=== Encrypted home directory ===

== SSH ==

An open SSH port is a typical gateway for attackers on any device exposed to the public Internet. Exposed devices might be attacked within minutes after being exposed. Typically such attacks try default passwords such as "12345", potentially putting the user at risk after connecting the phone to an open/unsecured access point, activating mobile data or mobile Internet.

For safety reasons it is highly recommended to only use SSH in combination with keys, instead of simple numeric passwords.

TODO: simply how-to of creating and copying SSH keys + certain SSH settings

== Hardening ==

== Hardware ==

=== USB ===

== Validation ==
=== dm-verity ===

PinePhone Security

2021-09-27T17:44:21Z

Dachalife: /* Encryption */

{{under construction}}

TODO intro

== Encryption ==

While encryption alone is not sufficient to protect sensitive data, it is an important tool to safeguard data in certain attack vectors.

=== Full-Disk Encryption ===

Full-disk encryption encrypts the entire disk (except for the boot bits). Currently some OSes such as postmarketOS and Mobian offer an installation image, which have the option to encrypt the entire disk. Some OSes, such as postmarketOS (via pmbootstrap) and Arch Arm also offer an installation script for an fully encrypted installation.

Decryption is done at boot after entering the encryption password via an on-screen keyboard (Osk-sdl).

=== Encrypted home directory ===

== SSH ==

An open SSH port is a typical gateway for attackers on any device exposed to the public Internet. Exposed devices might be attacked within minutes after being exposed. Typically such attacks try default passwords such as "12345", potentially putting the user at risk after connecting the phone via unprotected WiFis or mobile Internet.

For safety reasons it is highly recommended to only use SSH in combination with keys, instead of simple numeric passwords.

TODO: simply how-to of creating and copying SSH keys + certain SSH settings

== Hardening ==

== Hardware ==

=== USB ===

== Validation ==
=== dm-verity ===

User:JF/Getting-started-draft

2021-09-27T17:11:11Z

Dachalife: /* Draft from JF */

== Draft from JF ==

'''Dear Pinetimer,'''

Congratulations on your new smartwatch devkit.

'''Getting started:'''

This devkit is running InfiniTime, one of many open source firmwares available for the PineTime. Like many others, this project is still under development, but already provides functionalities such as time synchronization with your phone, over-the-air (OTA) firmware upgrades and support from companion applications like Gadgetbridge on Android and Amazfish on SailfishOS. You can learn more about InfiniTime on the website of the project (https://infinitime.io/) or its Github repository (https://github.com/JF002/Pinetime).

The OTA upgrade functionality allows you to install new versions of InfiniTime, or even other compatible firmwares like Hypnos (https://github.com/endian-albin/pinetime-hypnos) and Klok (https://gitlab.com/caspermeijn/klok).

Please note that it is still recommended to have an SWD debugger at hand in case the OTA upgrade fails or if you need to install a new version of the bootloader.

There are many other projects under development. The complete list, containing much more information (technical details, FAQ, howtos...), is available on the Pine64 Wiki (https://wiki.pine64.org/).

'''Are you are a developer?'''

Welcome to the community! You can choose to contribute to an existing project, or start yours from scratch. All you need is an SWD debugger (ST-LinkV2, J-Link, OpenOCD probe,...) and some programming knowledge.

'''Is it possible to contribute without programming knowledge?'''

Yes, of course! You can join the community, test the new firmware versions and their features, report bugs, write documentation and/or articles about Pinetime...

'''Links:'''
* Wiki: [https://wiki.pine64.org/index.php?title=PineTime https://wiki.pine64.org/index.php?title=PineTime]
* Forum: [https://forum.pine64.org/forumdisplay.php?fid=134 https://forum.pine64.org/forumdisplay.php?fid=134]
* Chat rooms:
** [https://app.element.io/#/room/#pinetime:matrix.org Matrix] (No login required to read)
** [ircs://irc.pine64.org#pinetime IRC irc.pine64.org] channel: #pinetime
** [https://t.me/pinetime Telegram]
** [https://discordapp.com/invite/DgB7kzr Discord]

* A cool article from Lup
* Another super article from Lup
* I think Lup wrote another amazing article
* ...

----

== Another (simpler) draft from JF ==
NOTE : this is a much simple version of the guide. It is intended to be printed on a small piece of paper that'll ship in the box of the devkit. It redirects the user to the wiki, so we should write a new wiki page that contains more info and links, and ensure this new page is well visible from the front page of the wiki

'''Quick start guide'''

1. Learn more about the PineTime and available firmware on the Wiki from Pine64 (https://wiki.pine64.org/index.php?title=PineTime)
<< Add A QR Code to the wiki >>

2. Connect your SWD debugger
<< Add simple schema / picture >>

3. Contribute to existing projects or create your own

4. Join the community of developers

5. Have fun

== Another draft ==
TODO

PinePhone

2021-09-24T20:02:04Z

Dachalife: /* PinePhone accessory */ Accessories

[[File:PinePhone Beta Edition.png|400px|thumb|right|Rendering of the PinePhone Beta Edition]]

The '''PinePhone''' is a smartphone created by PINE64. It is capable of running mainline Linux and is supported by many partner projects.

The Braveheart Edition of the PinePhone was the first publicly available version of the phone. It shipped without a fully functional operating system and was geared specifically towards early adopters. The Braveheart Edition's successors were the Community Editions, which featured a branded backcover and box of selected community projects. The Community Editions became available in June 2020. The Beta Edition featuring Manjaro with Plasma Mobile is the latest edition, it became available in March 2021.

== Introduction ==

The PinePhone is not a regular phone and you might not get the latest and greatest hardware and this years' newest innovation. You will get a device with good mainline support with a great community behind it.

=== State of the software ===

First things first, the PinePhone is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience.

Bear in mind that the software for Linux on phones is very early, 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.

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]])!

=== Help and support ===

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

Please keep in mind that PINE64 is not like a regular company (see [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.

== First time installation ==

{{Hint|Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.}}

When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge until this is removed and the modem, WiFi and Bluetooth will not work until the battery is connected.

The PinePhone's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. An adapter from a nano to a micro SIM might be included under tape in the camera notch of the phone's packaging. 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.

To remove the sticker after unboxing the phone:

# Carefully remove the back panel using the notch in the corner of the back cover without overbending it
# 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)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

<gallery mode="nolines" widths="400px" heights="400px">
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.
</gallery>

== Operating systems ==

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

=== Software releases ===

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

=== Installation instructions ===

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

Relevant subsections of the article for installing OSes to the PinePhone are:

* [[PinePhone Installation Instructions#Boot_priority|Boot priority]]
* [[PinePhone Installation Instructions#Installation_to_the_microSD|Installation to the microSD]]
* [[PinePhone Installation Instructions#Installation_to_the_eMMC|Installation to the eMMC]]
* [[PinePhone Installation Instructions#Resize_partition_to_fit_disk_space|Resize partition to fit disk space]]
* [[PinePhone Installation Instructions#Reuse_SD_card_for_data_storage_on_system_booting_from_eMMC|Reuse SD card for data storage on system booting from eMMC]]

== Specifications ==

* '''Dimensions:''' 160.5 x 76.6 x 9.2mm
* '''Weight:''' Between 180 ~ 200 grams
* '''SIM Card:''' Micro-SIM
* '''Display:'''
** '''Size:''' 5.95 inches (151mm) diagonal
** '''Type:''' HD IPS capacitive touchscreen, 16M colors
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64]
* '''RAM:''' 2GB or 3GB LPDDR3 SDRAM
* '''Internal Storage:''' 16GB or 32GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''Back [[#Camera|Camera]]:''' Single 5MP, 1/4", LED Flash
* '''Front Camera:''' Single 2MP, f/2.8, 1/5"
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if killswitch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|Modem]]:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot
** '''Bluetooth:''' 4.0, A2DP
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|Battery]]:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| Rear camera
| OmniVision OV5640
|-
| Camera flash
| SGMICRO SGM3140
|-
| Front camera
| GalaxyCore GC2145
|-
| LCD
| Xingbangda XBD599
|-
| WiFi
| Realtek RTL8723CS
|-
| Bluetooth
| Realtek RTL8723CS
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| Magnetometer
| ST LIS3MDL
|-
| Ambient light / Proximity
| SensorTek STK3335
|-
| Accelerometer / Gyroscope
| InvenSense MPU-6050
|-
| Vibration motor
| Unknown model
|-
| Notification LED
| LED0603RGB
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
| X-Powers AXP803
|-
| Battery fuel gauge
| X-Powers AXP803
|}

See the [[PinePhone_component_list|PinePhone Component List]].

== Hardware revisions ==

The following are all hardware revisions of the PinePhone that have existed, ordered by the time of their releases:

* [[Project Anakin]]
* [[Project Don't be evil|"Project Don't Be Evil"]] – development kit (devkit)
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] – developer batch
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] – Braveheart
* [[PinePhone v1.2‎]] – Ubports Community Edition
* [[PinePhone v1.2a]] – postmarketOS Community Edition
* [[PinePhone v1.2b]] – Manjaro Community Edition, KDE Community Edition, Mobian Community Edition and Beta Edition

== Hardware accessory ==

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

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

=== Pogo pins ===

[[File:Pinephone pogo.png|400px|thumb|right|The pogo pins, as visible under the back cover.]]

The PinePhone has six pogo pins on the back allowing for custom hardware extensions such as wireless charging, an IR blaster, a keyboard extension or extended battery case. The pogo pins provide access to an interrupt line, power inputs/outputs and an I2C interface.

{| class="wikitable"
| Interrupt
| SDA
| SCL
|-
| DCIN
| USB-5V
| GND
|}

DCIN and USB-5V are the names used in the schematics. The actual behavior of these pogo pins is not obvious based on their names. DCIN is connected both to the VBUS line of the USB Type-C connector and to the ACIN/VBUS inputs on the PMIC. This means that, depending on a number of factors, DCIN may be at 0 V or 5 V. USB-5V is connected at the output of an LP6226 DC/DC boost converter (5 V), which in turn is fed by the PS output of the PMIC. The boost converter is enabled or disabled by a GPIO output from the A64 SoC, controlled by software (e.g. the Linux kernel). Depending on inputs and decision made by the PMIC, PS may be at the battery voltage (fed "directly" by the battery through a [https://www.zxcompo.com/ transistor] controlled by the PMIC), or at the "USB" voltage (fed by the PMIC's ACIN/VBUS inputs). This means that depending on a number of factors, USB-5V may be at battery voltage (between 3.0 V and 4.3 V), or at 5 V.

Because the PinePhone may act as a USB host (providing 5 V at the USB Type-C connector's VBUS to a connected device) or as a USB device (drawing from a 5 V source on the USB Type-C connector's VBUS), DCIN is actually not strictly an input nor an output. Some community analysis of the PinePhone schematic (and some testing) indicates that you can connect a 5 V power supply to DCIN in order to power the phone at the PMIC's ACIN/VBUS inputs (and, as a side effect, charge the battery). This may not be safe to do in all conditions, e.g., when the phone is acting as a USB host to a connected USB device. It should also be safe to use DCIN as a power output from the PinePhone, e.g., when a USB Type-C charger is connected, you can draw current directly from the USB Type-C port's VBUS, which is provided by the charger. Please note that, when using DCIN as an output from the PinePhone, DCIN isn't "always on"; it may be 0 V. It is currently not documented on how much current can be safely drawn.

USB-5V should be safe to use as an "always on" power output from the PinePhone. Depending on a number of factors, voltage may be from 3 V to 5 V; thus, if you are using USB-5V to power your pogo-pins expansion board, you will probably need to use DC/DC converters/regulators as appropriate. USB-5V is on even while the A64 SoC is powered down.

The I2C and interrupt lines have pull-ups on the phone side. The I2C lines are pulled up to 3v3 by the phone.

For a breakout board see [https://github.com/SMR404/PinephonePogoBreakout here]. For an example project see Martijn's blog post [https://blog.brixit.nl/making-a-backcover-extension-for-the-pinephone/ "Making a backcover extension for the PinePhone"].

PINE64 store currently sells the [https://pine64.com/product/pinephone-flex-break-out-board/?v=0446c16e2e66 PinePhone Flex Breakout Board]. With the pitch being 2.54 mm, this Flex Breakout Board may have leads soldered directly to the contacts for use in a solderless board. A non-soldered solution would be to use a [https://www.digikey.com/en/products/detail/te-connectivity-amp-connectors/5-520315-6/2258879 TE AMP Connector] that will accept a Flat Flexible Cable 2.54 mm pitch.

=== Back cover ===
A step file for the back cover for creating custom cases is freely available [https://files.pine64.org/doc/PinePhone/PinePhone%20Back%20Cover%20ver%200.5.stp here].

=== Serial console ===

[[File:PinePhone_Serial_Cable.png|400px|thumb|right|Pinout of the serial adapter.]]

The PinePhone has a serial port in the headphone connector, it's activated by the 6th contact on the dipswitch. If the switch is set to "on", the headphone connector is in audio mode, if it is set to "off" it's in UART mode. The UART serial connection can also be used for communication with other devices from the PinePhone.

The UART is 115200n8.

The pinout for the serial connector is:

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

You can buy a serial debug cable from the [https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/ PINE64 Store]. The store cable uses a 4 ring plug, as seen in the [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf here], but a 3 ring plug works just as well. The cable uses a CH340 chipset based serial to USB converter, but any 3.3v serial connection can be used. Because it is a "host"/DTE it means that you need a ''cross modem cable'' ([https://en.wikipedia.org/wiki/Null_modem Null Modem]) with TX on Tip to be connected to RX. A cable like e.g. [https://www.ftdichip.com/Products/Cables/USBTTLSerial.htm FTDI TTL-232R-3V3-AJ] which has TX on Tip and RX on Ring fits perfectly.

== Killswitch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]

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

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

== Camera ==

The PinePhone has two cameras, OmniVision OV5640 with 5MP (up to 2592 x 1944 pixels) as rear camera and GalaxyCore GC2145 with 2MP (up to 1600 x 1200 pixels) as front camera.

[[File:Rose.jpg|400px|thumb|none|Example picture taken on the PinePhone's rear camera by Martijn Braam using his app ''Megapixels''.]]

Further details regarding the camera and the Megapixels camera app can be found on [https://blog.brixit.nl/tag/phones/ Martijn's blog].

== Battery ==
{{Hint|The EG25-G modem and the RTL8723CS WiFi and Bluetooth combo do not work without battery power, even when enough power is supplied to the PinePhone via the USB Type-C port.}}

The phone ships with a protective plastic sticker between the battery and the phone to protect the device from turning on during shipping. You need to gently open the back cover, then remove the battery and finally remove the sticker and check that the pins aren't bent. Note: If the battery is stuck inside the phone, the mid screw in the lower part of the midframe needs to be slightly loosened, see [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|here]].

The [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf supplied battery] is meant to be compatible with Samsung part number EB-BJ700BBC / BBE / CBE from the 2015 J7 phone. The extended life aftermarket BBU does fit, although it is a tight fit.

The battery terminals, from the nearest to the battery edge to the nearest to the middle of battery, are as follows:

{| class="wikitable"
| style="min-width: 90px; text-align: center;" | +ve
| style="min-width: 90px; text-align: center;" | thermistor
| style="min-width: 90px; text-align: center;" | -ve
| style="min-width: 90px; text-align: center;" | not connected
|}

The battery includes a protection circuit that isolates it in a number of fault conditions, including if it is discharged too far. The fully discharged battery can be recharged by connecting the phone to a charger with a sufficient output. Once it has charged sufficiently you will be able to boot the phone.

== Modem ==

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem.

=== AT commands ===

A list of documented AT commands can be found for example in this [[:File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf|AT commands documentation]] from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website [http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands here].

To send AT commands to the modem under Linux, <code>minicom</code> or the often-preinstalled <code>atinout</code> utility:

atinout example:
<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+... command here
> EOF
cat ./out.txt # to see the result of a command execution
</pre>

minicom example:

<code>minicom -D /dev/ttyUSB2</code>

=== VoLTE ===

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most OSes try to set the correct profile automatically.

To list the available VoLTE profiles:

<pre>
AT+QMBNCFG="list"

+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x0501081F,201901141
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,201909271
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,201904281
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,201911081
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,201807052
</pre>

To select a profile manually, select the best fitting one or a generic one if none fits:

<pre>
AT+QMBNCFG="select","ROW_Generic_3GPP"
</pre>

Then enable Voice over LTE using:

<pre>
AT+QCFG="ims",1
</pre>

And reboot the modem to apply the settings:

<pre>
AT+CFUN=1,1
</pre>

To check the status of VoLTE during a call, the AT command <code>CLCC</code> can be used:

<pre>
AT+CLCC

+CLCC: 1,1,0,1,0,"",128
+CLCC: 2,1,0,1,0,"",128
</pre>

In the fourth item of the list, "0" means voice and and "1" means data. If both rows have "1" then the voice call is being carried over VoLTE.

=== APN settings ===

The APN setting is only required for a public Internet connection ("data") on the phone. For tested APN settings and how to apply them see [[PinePhone APN Settings]].

=== Carrier support ===
The page [[PinePhone Carrier Support]] contains information about the frequency support of different carriers and hints on setting up cellular network connectivity.

=== Documents ===

Detailed information about the modem can be found on the [https://xnux.eu/devices/feature/modem-pp.html#toc-modem-on-pinephone page of the developer megi], including reverse-engineered parts of the firmware and its functions. There is also a document about using the modem from January 18th 2020 by megi [https://megous.com/dl/tmp/modem.txt here]. A script at the end of the document showcases a way to poweroff the modem before powering off the phone, which is integrated into most of the available OSes.

=== Firmware update ===

{{Hint|The following instructions are directed towards professional users. It is highly recommend to make sure the update process is not interrupted to prevent the modem from bricking.}}

The modem firmware can be updated to a newer version if it is outdated. The firmware version can be checked using the following AT command (at the example of <code>atinout</code>, alternatively <code>minicom</code> can be used to communicate with the modem too):

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+QGMR
> EOF
cat ./out.txt # should output OK
</pre>

If the version number is 01.001.01.001 ''(EG25GGBR07A08M2G_01.001.01.001)'' it is recommended to update the firmware to version 01.002.01.002 ''(EG25GGBR07A08M2G_01.002.01.002)'' due to various bug fixes.

'''Pre-update checklist:'''

Please make sure all requirements of the checklist are fulfilled. If the update process is interrupted it will lead to a corrupted firmware of the modem, causing it to brick. Recovering a bricked modem is exponentially more complicated and requires the user to boot a special mode by physically bridging test points on the modem.

* The battery needs to be charged sufficiently
* The phone needs to be plugged into a charger
* Deep sleep is recommended to be disabled as it can interrupt the update process
* It is recommended to close all other running applications
* Use common sense while doing the update, don't do the update while being impaired in any way

To get the latest firmware, clone the repository of user Biktorgj on the phone:

<pre>git clone https://github.com/Biktorgj/quectel_eg25_recovery</pre>

After cloning the directory, open it with cd:

<pre>cd quectel_eg25_recovery</pre>

Then run qfirehose, which starts the flashing process:

<pre>sudo ./qfirehose -f ./</pre>

The modem will automatically reboot after the update process is done. The boot process takes around 30 to 60 seconds. After that it is highly recommended to reboot the device.

=== Firmware modifications ===

See [[PineModems]] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery.

=== GPS / GNSS ===
The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem is controlled via a separate set of AT commands. The AGPS data upload uses the file management AT commands, which also have their own manual. These are linked in the [[PinePhone#Datasheets for components and peripherals|documentation section]] below.

As with most smartphones, the PinePhone has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. While the hardware supports AGPS data upload, it isn't yet implemented in current distributions. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] which can be made to work, but support needs to be added to ModemManager, oFono etc. before it will be easy to use.

Basic testing of GNSS reception can be done by using the AT command interface (/dev/ttyUSB2) from a terminal progam like minicom and the data output interface (/dev/ttyUSB1) to feed NMEA data into gpsmon or some other progam that can parse standard NMEA sentences.

[[File:Gpsmon eg25g.png|400px|thumb|none|gpsmon decoding GPS data from /dev/ttyUSB1]]

To check if GNSS data output is enabled, you can

cat /dev/ttyUSB1

this should display a stream of NMEA sentences

$GPVTG,,T,,M,,N,,K,N*2C
$GPGSA,A,1,,,,,,,,,,,,,,,,*32
$GPGGA,,,,,,0,,,,,,,,*66

=== Voice mail ===

The operating systems of the PinePhone may not have support for accessing your voicemail by holding down the 1-key. Carriers might support accessing the voice mail via an external number however. If you are in Canada and using rogers or a rogers associated carrier (such as ''Chatr''), you can access your voice mail by calling an external number, see [https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers here]. In America, AT&T also has support for accessing your voicemail via an external phone number, see [https://www.att.com/support/article/wireless/KM1009101/ here].

== Safety ==

=== Charging safety ===

The PinePhone supports up to 5V 3A (15W) Quick Charge, it follows the USB Power Delivery specification. Only compatible phone chargers may be used, charging the phone with incompatible chargers (for example laptop chargers with a higher voltage) is prohibited. Charging the phone releases heat, general safety recommendations must be followed, see the section ''Thermal safety''.

=== Thermal safety ===

With the Allwinner A64 being an older generation SoC with a large 40nm chip, the phone produces quite some heat with medium or higher use and especially also during charging or when using USB accessories, like a docking station. Measurements to prevent damage to the phone and to its surroundings need to be taken by the user. This includes especially a proper handling of the phone: do not charge the phone in a way where heat builds up around the phone without being able to escape. Especially don't charge your phone under a pillow, blankets, in pockets or bags. Charging the phone produces heat and charging the phone in a way, where the excessive heat can't dispose around the phone poses an immediate fire risk.

The user might notice that the phone gets warm under usage, compared to phones with more up-to-date hardware. Under normal circumstances these temperatures don't pose a risk while being in the levels within the safe operating temperatures (which lay far beyond the point where components can be too hot to touch). Higher temperatures might especially be experienced on the top side of the screen and on the inside of the phone at the RF shield of the modem. The higher temperature of the RF shield of the modem is commonly caused by the SoC on the opposite side of the mainboard, the RF shield of the modem is used to disperse heat of the SoC. In newer mainboard revisions starting from 1.2a there are also thermal pads on the back cover and between the SoC's RF shield and the screen, dispersing heat on the screen and on the back cover. In the past there has been safety issues regarding thermal safety functions, causing temperature reads to not properly work over an extended period of time, which was causing heat damage in some cases (see the documentation of that issue by the developer Megous [http://xnux.eu/log/#018 here] and [http://xnux.eu/log/#017 here]). While the developers are working hard to prevent such issues, they can't be excluded under all circumstances (see [[PinePhone#State_of_the_software|state of the software]]). The users are expected to monitor their phones' thermal safety at every point at this state of the software.

It is highly recommend to update the phone on a regular basis to always get the latest improvements. The default settings to throttle the performance and to shut down the phone when reaching critical temperatures might be set to a too high point depending on the specific usage and usage length. Under GNU/Linux the phone's thermal management behavior can be modified via the Thermal Sysfs driver to achieve lower temperatures and preventing the screen and other components to potentially take damage, see [[PinePhone Thermal Tweaks]] for the details.

== Frequently asked questions ==

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

== Modifications and repairs ==

=== Swapping in a new mainboard revision ===

The mainboard can be replaced, for example for upgrading to a newer hardware revision or if it is faulty. The replacement board does not have an OS preinstalled, to test if everything is working after swapping the mainboard a flashed SD card is required. The mainboard also comes with a non-functional firmware on the ANX chip, a newer firmware version has to be flashed as explained below to get certain USB functionality to work.

==== Replacing the mainboard ====

{{Hint|Replacement boards come with an empty eMMC, which means that trying to boot from them looks like the board is faulty (no LEDs, no screen, no reaction of the phone). Please boot an OS from SD card.}}

Prior to replacing your PinePhone’s mainboard please read the steps outlined in bullet points below and watch the attached video.

# You’ll need a small Phillip’s screwdriver and a prying tool to swap out the PinePhone’s mainboard.
# Remove the PinePhone’s back cover. See your quick start guide for details.
# Remove the battery as well as any inserted SD and SIM cards.
# Unscrew all 15 Phillip’s head screws around the midframe of the phone.
# Gently pry up the midframe using a guitar pick or credit card corner. It is easiest to separate the midframe at one of the bottom edges. Work your way around all the sides of the phone until the midframe separates from the phone’s body.
# Detach all ribbon cables and “Lego” connectors. List of things to detach: 1) two “Lego” connects at the bottom of the mainboard. 2) u.FL antenna connect and touchscreen digitizer on PCD left side. 3) LCD ribbon cable top of mainboard, next to audio/ UART jack.
# Pry the mainboard up gently from the left-hand side.
# Remove front and main cameras and reset them into the new mainboard.
# Check that the rubber proximity sensor housing is in the chassis, not stuck to the removed mainboard.
# Place the new mainboard in the chassis, hooking in on the plastic tabs on left side and pressing down firmly on opposite side, and follow the steps (7-2) in reverse. When reattaching the midframe take care that no cables are out of place or trapped, as they may be damaged when tightening screws.

After swapping the mainboard the phone won't boot as there is no OS on the replacement board's eMMC preinstalled. To boot an OS insert a flashed SD card.

A video tutorial by Martijn Braam can be found here (or alternatively a video tutorial by user brigadan with additional notes about the camera swap and proximity sensor isolator [https://www.youtube.com/watch?v=J3AJEF7akkw here]):
[[File:Pinephone_martijn_pcb_replacement.png|thumb|none|600px|link=https://www.youtube.com/watch?v=5GbMoZ_zuZs|Watch Martijn Braam's video tutorial here: https://www.youtube.com/watch?v=5GbMoZ_zuZs.]]

==== Flashing the ANX firmware ====

===== Method 1 =====

After swapping the mainboard the ANX7688 chip has to be flashed for full USB functionality.

Download the latest ANX7688 firmware image on the phone:

wget https://xff.cz/git/linux-firmware/plain/anx7688-fw.bin

Execute as root ("sudo su") on the phone:

cp anx7688-fw.bin /lib/firmware/
echo 1 > /sys/class/typec/port0/device/flash_eeprom

===== Method 2 =====

Booting a factory test image will automatically flash the ANX7688 chip. See [[PinePhone Software Releases#Factory Test OS|Factory Test OS]] for such an image.

=== Replacing the screen ===

Before attempting to replace the screen be sure to review the section on [[#Swapping in a new mainboard revision|replacing the mainboard]] since that will get you most of the way there. Be aware that the replacement screen is actually the entire front frame of the phone and there are components that will need to be swapped from your old screen.

* Make sure you have a precision screwdriver set that has the correct size Philips tip. The screws are very small and the heads can easily be stripped if the screwdriver is not correct - if you feel your screwdriver slipping, stop what you are doing and try one that is a better fit. A magnetized screwdriver will help in not losing screws, as will a magnetic parts holder to keep them in while working.

* There are a number of components and cables as well as the insulator sheet under the battery that are glued in place. A hair dryer will loosen the glue and make them much easier to remove. You may want to order extra cables along with the screen just in case.

* The vibration motor, which is part of the USB-C board assembly and glued into place, will come apart easily and be damaged if you pry it up in the wrong place. Make sure you pry from underneath the complete part, not midway on its housing. The ribbon cable attaching this to the USB-C board is small, thin, and fragile so be careful with that as well.

* The new screen comes with new side switches and insulator sheet but there are a number of parts that need to be transferred from the old screen, like the thin coax cable running up the side, the phone ear speaker, proximity sensor gasket, and a gold-colored mesh glued in place that needs to be transferred to a flexible circuit included on the new screen. If you don't swap over the proximity sensor rubber gasket the screen will immediately turn off after logging in. Be careful when routing the coax cable that it goes around the screw holes or you may drive a screw right through the cable.

Take your time, use the right tools, be careful and you should be rewarded with success.

=== Spare parts not available in the PINE64 store ===

* Earpiece dimensions: 12x6x2 mm. Compatible with Xiaomi Mi2 / Mi3 / Mi4, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

== Press ==

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

== PinePhone board information, schematics and certifications ==

* PinePhone mainboard schematic:
** [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2b%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2b]
** [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2a]
** [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2]
** [[PinePhone_v1.2|PinePhone schematic ver 1.2 change list]]
** [https://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard Schematic ver 1.1]
** [https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component top placement drawing ver 1.1]
** [https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1]
** [[PinePhone component list]]
* PinePhone USB-C small board schematic:
** [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20schematic%20v1.0%2020190730.pdf PinePhone USB-C small board Schematic ver 1.0]
** [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20top%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component top placement drawing ver 1.0]
** [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20bottom%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component bottom placement drawing ver 1.0]
* PinePhone certifications:
** [https://files.pine64.org/doc/cert/PinePhone%20FCC%20SDOC%20Certificate-S19112602605001.pdf PinePhone FCC Certificate]
** [https://fcc.report/FCC-ID/2AWAG-PINEPHONE RF Exposure SAR Information from FCC ID site]
** [https://files.pine64.org/doc/cert/PinePhone%20CE%20RED%20Certificate-S19112602602.pdf PinePhone CE RED Certificate]
** [https://files.pine64.org/doc/cert/PinePhone%20ROHS%20Report.pdf PinePhone ROHS Report]
** Note: PinePhone's Type Allocation Code (TAC) is 86769804

== Datasheets for components and peripherals ==

* Allwinner A64 SoC information:
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

* X-Powers AXP803 PMIC (Power Management IC) information:
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

* LPDDR3 (178 Balls) SDRAM:
** [https://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 datasheet]

* eMMC information:
** [https://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf Kimtigo eMMC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinephone/QZ01-rear-2019-0717(HW)%20Model.pdf PinePhone 5M Pixel Real CMOS Image Sensor Module]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
** [https://usermanual.wiki/Document/OV5640FirmwareUserGuideV10.952852672.pdf OV5640 Embedded Firmware User Guide – VCM AF Module]
** [https://files.pine64.org/doc/datasheet/pinephone/QZ01-front-2019-0717(HW)%20Model.pdf PinePhone 2M Pixel Front CMOS Image Sensor Module]
** [https://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

* LCD touch screen panel information:
** [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20LCD-QZ01.pdf 5.99" 1440x720 LCD IPS Panel specification]
** [https://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703 LCD Controller datasheet]
** [https://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf GOODiX GT917S Capacitive Touch Controller datasheet]

* Lithium battery information:
** [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf PinePhone Lithium Battery specification]
** [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20ZCV%20Curve%20Chart.xlsx PinePhone Lithium Battery ZCV curve chart]
** [https://cad.onshape.com/documents/5194d6303f021e6f300b70a0/w/7b63ac4c32ed63dfd78c7840/e/5d43c0ce5b665bae10082a08 PinePhone Lithium Battery 3D onshape drawing]

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

* LTE module information:
** [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]]
** [[File:Quectel_EG25-G_Hardware_Design_V1.4.pdf]]
** [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]]
** [[File:Quectel_EC2xEG25-GEG9xEM05_FILE_AT_Commands_Manual_V1.0.pdf]]
** [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_GNSS_Application_Note_V1.3.pdf]]

* Sensors:
** [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetometer Datasheet]
** [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS datasheet]
** [https://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]

* Digital video to USB-C bridge:
** [https://www.analogix.com/en/system/files/AA-002281-PB-6-ANX7688_Product_Brief.pdf ANX7688 product brief]

* Case information:
** [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Exploded%20Diagram%20ver%201.0.pdf PinePhone case exploded diagram]
** [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Back%20Cover.stp PinePhone back cover 3D file]

* Other components:
** See the [[PinePhone_component_list|Component List]]

== Developer works ==

The following resources have been made available by Ondřej Jirman, a developer for the Pinephone:

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

== External links ==
* [https://pine64.com/product-category/pinephone/ The PinePhone on the official Pine store]
* [https://pine64.com/product-category/smartphone-spare-parts/ PinePhone spare parts on the official Pine store]
* [https://pine64.com/product-category/smartphone-accessories/ PinePhone accessories on the official Pine store]

[[Category:PinePhone]] [[Category:Allwinner A64]]

PinePhone Carrier Support

2021-09-24T18:57:31Z

Dachalife: /* Europe */

{{under construction}}

{{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.}}

This page contains hints on setting up cellular network connectivity for specific carriers.
For more general information, see [[PinePhone#Modem_and_carrier_support|Modem and carrier support]]. For the APN settings see [[PinePhone APN Settings]].

= Check compatibility =
To check if the PinePhone is supported on your carrier:

Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

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.

= Tested and working carriers =

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

== Asia ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2020
|-
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|}

== Africa ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Europe ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Not tested || ArchLinux - 30 July 2021
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| 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
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm (Phosh,SXMO) 2021/04/29
*Manjaro - Phosh 2021/04/29
*Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
*Manjaro - Plasma Dev 2020/11/21
*Ubuntu Touch - 2020/11/26
*KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
|-
| USA || Tello (T-Mobile) || Yes || No || Yes || Yes ||
*postMarketOS - Phosh 2021/8/15
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| USA || Verizon || No || No || No || No ||
*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)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
*Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
*Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| USA || FaithWireless (AT&T) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 2021/04/29 (version 0.10.1-1, see the [[PinePhone_Carrier_Support#AT.26T|AT&T issues]] below.)
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
*Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
*PostmarketOS - sxmo edge 2021/09/09
|-
|}

== South America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Australia / Oceania ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-

|-
| Israel|| Golan TC || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-

|}

= Special carrier notes =

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

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:

== USA ==
=== AT&T ===
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.

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.

=== Consumer Cellular ===

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.

=== Cricket Wireless ===
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).

=== SimpleMobile ===
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.

=== Sprint ===
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

=== T-Mobile ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).

T-Mobile's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].

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.

=== Verizon ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on
[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.

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.

=== Google Fi ===
Only T-Mobile service works currently, not US Cellular or Sprint.
The APN is h2g2.
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

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.

== Europe ==
=== Telekom Germany ===
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.

= Known issues =
Known issues:
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* 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.
* 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.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

= MMS workarounds =
These scripts allow partial MMS support on a [[PinePhone]]:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

= Resources =
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]

[[Category:PinePhone]]

PinePhone APN Settings

2021-09-23T15:39:51Z

Dachalife: Added Telenor settings for Nyíregyháza, Hungary

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.

= Setting the APN =

The location of the APN setting depend on the user interface the distribution is using.

== Distributions with Phosh ==

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).



= List of tested carriers =

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.

== 4ka (Slovakia) ==
Name: 4ka Internet
APN: internet
Username: <empty>
Password: <empty>

Source: https://www.4ka.sk/vitajte/navody-a-nastavenia/detail-navodu

== AT&T-based ==

=== AT&T (USA) ===
APN: <code>phone</code> or <code>NXTGENPHONE</code> if "phone" does not work (see https://www.att.com/support/article/wireless/KM1218306/).

=== AT&T Mexico (Mexico) ===

APN: <code> wap.attmex.mx </code>

=== Cricket (USA) ===
APN: <code>phone</code> or <code>ndo</code> or <code>NXTGENPHONE</code>

== Blau.de (Germany) ==
APN: internet.eplus.de
Username: eplus
Password: gprs

Source: https://www.my-gps.org/412-apn-einstellungen-deutschland

== Bouygues Telecom (France) ==
Name: Bouygues Telecom
APN: mmsbouygtel.com
Username: <empty>
Password: <empty>

Source: https://www.assistance.bouyguestelecom.fr/s/article/parametrage-mobile-email-mms-internet

== Congstar - Telekom Net (Germany) ==
Name: Telekom Internet
APN: internet.telekom
Username: telekom
Password: telekom

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]

Name: Congstar Internet
APN: internet.telekom
Username: congstar
Password: cs

== Eastlink Wireless (Canada) ==

Name: Eastlink Internet
APN: wisp.mobi.eastlink.ca
Username: <empty>
Password: <empty>

Source: https://www.apnsettings.org/canada/eastlink-ca/

== Free (France) ==

Name: Free
APN: free
Username: free
Password: <empty>

Source: https://mobile.free.fr/assistance/46.html

== Freedom Mobile (Canada) ==

Name: 1
APN: internet.freedommobile.ca
Username: <empty>
Password: <empty>

== Google Fi (USA) ==

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.

Name: Google Fi
APN: h2g2
Username: <empty>
Password: <empty>

Source: https://support.google.com/fi/answer/6330195?hl=en

== Hofer Telekom (Austria) ==

Name: HoT Internet
APN: webaut
Username: <empty>
Password: <empty>

Source: https://www.hot.at/config/faqs/HoT_Einstellungen_Endgera_te.pdf

== kölbi (Costa Rica) ==
Name: Costa Rica:Kolbi:Internet
APN: kolbi3g
Username: <empty>
Password: <empty>

Note: alternatively <code>kolbi4g</code> also works as APN.

== Koodo (Canada) ==

Name: Internet/MMS 2
APN: sp.koodo.com
Username: <empty>
Password: <empty>

Source: https://www.4gapn.com/ca/en/koodo

== KT (South Korea) ==

Name: KT LTE
APN: lte.ktfwing.com
Username: <empty>
Password: <empty>

Name: KT 3G
APN: alwayson.ktfwing.com
Username: <empty>
Password: <empty>

Note: APN automatically detected in Manjaro Phosh. Use either KT LTE or KT 3G according to your subscription.

== Lebara (UK) ==
Name: Lebara
APN: uk.lebara.mobi
Username: wap
Password: wap

These settings work on 4G.

Ignore Default/asdamobiles.co.uk APN if present.

== Mineo (Japan) ==

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

Name: Mineo
APN: mineo-d.jp
Username: mineo@k-opti.com
Password: mineo

Source: https://support.mineo.jp/manual/network_setup_d.html

== Mint Mobile (USA) ==

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.

Use the following APN settings:

Name: Ultra
APN: Wholesale

Source: https://www.mintmobile.com/setup-for-android/

== Mobile Vikings (Belgium) ==

Name: Mobile Vikings
APN: web.be
Username: web
Password: web

Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-

If the first one doesn't work try this one:

Name: Mobile Vikings
APN: web.be
Username: <empty>
Password: <empty>

Source: autoconfig on ubports

== Orange Telecom (France) ==
Name: Orange Internet
APN: orange
Username: orange
Password: orange

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

== Penny Mobil (Germany) ==

APN settings:

name: Penny Mobil
APN: internet.t-mobile
username: t-mobile
password: tm

== Public Mobile (Canada) ==
Internet only, mms not tested.

Name: Public Mobile
APN: sp.mb.com
Username: <empty>
Password: <empty>

Source: https://productioncommunity.publicmobile.ca/t5/Phones-Hardware/How-do-I-set-up-data-APN-on-my-smartphone/td-p/3

== Red Pocket (USA) ==

You can choose AT&T, Verizon, T-Mobile or Sprint network.

APN settings:

name: Red Pocket
APN: RESELLER

== Rogers (Canada) ==

Name: 4G/LTE Rogers Data
APN: ltemobile.apn
Username: <empty>
Password: <empty>

Name: 3G Rogers Data
APN: internet.com
Username: wapuser1
Password: wap

Source: https://communityforums.rogers.com/t5/Wireless-Knowledge-Base/Rogers-APN-Settings/ta-p/410438,

== Simyo (Spain) ==

APN settings:
APN: orangeworld

Source: https://blog.simyo.es/simyo-configuracion-internet-wap-mms/configura-tu-movil/

== Sunrise (Switzerland) ==

Name: Sunrise
APN: internet
Username: <empty>
Password: <empty>

== Swisscom (Switzerland) ==

Name: Swisscom
APN: gprs.swisscom.ch
Username: <empty>
Password: <empty>

== Tele2 (Sweden) ==
Name: tele2
APN: 4G.tele2.se
Username: <empty>
Password: <empty>

Source: https://www.tele2.se/support/felsokning-guider/tjanster-installningar/mms-och-data

== Telekom (Germany) ==

APN settings:

Name: Telekom
APN: internet.t-mobile
Username: t-mobile
Password: tm

Source: https://www.telekom.de/hilfe/mobilfunk-mobiles-internet/mobiles-internet-e-mail/apn-mobilfunk/wie-lauten-die-apn-fuer-mobilfunk?samChecked=true

== Telekom (Hungary) ==

APN settings:

Name: Default
APN: internet.telekom
Username: <empty>
Password: <empty>

== Telenor (Hungary) ==

Name: Telenor
APN: online
Username: <empty>
Password: <empty>

Source: https://apn.how/hungary/telenor-hungary

== Telenor (Sweden) ==

Name: Telenor SE
APN: services.telenor.se
Username: <empty>
Password: <empty>

Source: https://www.telenor.se/kundservice/vanliga-fragor/min-mobil-surfplatta/vad-har-telenor-for-apn-installningar/

== Telia (Finland) ==
Name: internet
APN: internet
Username: <empty>
Password: <empty>

== Telstra (Australia) ==

Name: Telstra Internet/WAP
APN: telstra.iph
Username: <empty>
Password: <empty>

== Three (UK) ==

Name: 3
APN: three.co.uk
Username: <empty>
Password: <empty>

== Tracfone (USA) ==

''BYOP SIM Card Kit'' works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit.

3G/4G data known to work with Verizon & AT&T SIMs (most likely works for T-Mobile as well).

Use the following APN settings:

Name: Tracfone
APN: RESELLER
Username: <empty>
Password: <empty>

To use Verizon's network:

Name: Tracfone
APN: TRACFONE.VZWENTP
Username: <empty>
Password: <empty>

== Verizon Contract (USA) ==

There are several APN names which can be used, for example:

Name: 4G LTE Contract
APN: vzwinternet
Username: <empty>
Password: <empty>

Other APN names which appear, and may work if the above does not:

vzwapp
vzwims

== Videotron (Canada) ==

Name: Videotron
APN: media.ng
Username: free
Password: <empty>

== Virgin Mobile (Canada) ==

Settings might work with Bell Canada too since it is the same network.

Name: Mobile Fast Web
APN: pda2.bell.ca
Username: <empty>
Password: <empty>

== Vodafone (Czech Republic) ==
Name: internet
APN: internet
Username: <empty>
Password: <empty>

Source: https://www.vodafone.cz/pece/osobni-a-firemni/otazky/zaciname-s-chytrym-telefonem/pripojeni-nastaveni-internetu-v-telefonu/

== Vodafone (UK) ==
Name: Vodafone
APN: wap.vodafone.co.uk
Username: wap
Password: wap

These settings work on 4G.

Ignore Default/asdamobiles.co.uk APN if present.

= Carriers that do not work =

== FreedomPop (USA) ==
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.

APN: <code>fp.com.attz</code>

== Sprint (USA) ==

Sprint is currently not supported due to unknown issues, see also [[PinePhone Carrier Support#Sprint]]. Any input regarding this issue is highly appreciated.

APN: <code>cinet.spcs</code>

== Visible (USA) ==

Visible does not have any way to whitelist 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.

== Other ==

Other VoLTE services.

= External links =

* See also https://forum.pine64.org/showthread.php?tid=9150

[[Category:PinePhone]]