PINE64 - User contributions [en]

Main Page

2023-09-05T00:19:47Z

Thomzane: Add the woodpecker accessory

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications, please read the [[PINE64 brand and logo|article about our brand and logo]].

== Devices ==

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following devices manufactured by PINE64:

* Phones: '''[[PinePhone]]''' and '''[[PinePhone Pro]]'''
* Phone accessories: '''[[PinePhone (Pro) Add-ons]]''' and '''[[PinePhone (Pro) Keyboard]]'''
* Tablets: '''[[PineTab]]''', '''[[PineTab2]]''', '''[[PineTab-V]]''' and '''[[PineNote]]'''
* Wearable: '''[[PineBuds Pro]]''', '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''' and '''[[Pinebook Pro]]'''
* Laptop accessories: '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Ox64]]''', '''[[STAR64]]''', '''[[Quartz64]]''', '''[[QuartzPro64_Development|QuartzPro64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS]]''', '''[[PINE H64 Model A]]''' and '''[[PINE H64|PINE H64 Model B]]'''
* Single-board computer accessories: '''[[Woodpecker]]'''
* Set-top box: '''[[RockBox]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPINE]]''', '''[[SOPINE Baseboard]]''', '''[[SOEDGE]]''', '''[[SOEDGE Baseboard]]''', and '''[[SOQuartz]]'''
* IP camera: '''[[PineCube]]'''
* Power adapter: '''[[PinePower]]'''
* Soldering iron: '''[[Pinecil]]'''
* Makerspace: '''[[PineCone]]''' and '''[[Pinedio]]'''

== Community and Support ==

Community collaboration and support is focused around the chat platforms and forums described below. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

=== Chat Platforms ===

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot.

{{hint|PINE64 community is not some always responding, restless commercial customer service, or some sort of almighty existence that can resolve all your problems. When participating in community discussions, please be patient and do not expect questions to be answered immediately, certainly, or currently.
* The activity of community members varies depending on the time of day and the number of active users.
* Whether your questions will be answered & whether the answers are right and definitive, depends on the information you provide, and, after all, difficulty of your questions & community members' ability.
* Read [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] to learn more.
* Please read [[PINE64 Community Rules and Code of Conduct]].

'''Note:'''
* PINE64 uses a bridge bot (''[https://github.com/42wim/matterbridge matterbridge]'' with some modifications), which allows Discord, IRC, Matrix, and Telegram users to see and participate in the community chat.
* The bot name is "Pine64 Protocol Droid" and if you see this, look in the message to see the actual author of the message.
* When the bot relays messages it will show the platform the user is using: ''[D]'' for ''Discord'', ''[I]'' for ''IRC'', ''[M]'' for ''Matrix'' and ''[T]'' for ''Telegram''.
}}

The community chat platforms are the following:

* '''Discord''': use this '''[https://discord.gg/pine64 Invite Link]'''. All PINE64 discord channels are immediately viewable, do not need to join separate channels like the Telegram/Matrix table below.
* '''IRC''': the server is irc.pine64.org. Use <code>/list</code> command or the table below to see the full list of channels.
* '''Matrix and Telegram''': See the table below.

{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://matrix.to/#/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://matrix.to/#/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://matrix.to/#/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://matrix.to/#/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://matrix.to/#/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://matrix.to/#/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz-dev
|-
| Star64
| [https://matrix.to/#/#star64:matrix.org #star64:matrix.org]
| [https://t.me/star64_sbc @star64-sbc]
| Unavailable
|-
| Pinebook and Pinebook Pro
| [https://matrix.to/#/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://matrix.to/#/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://matrix.to/#/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://matrix.to/#/#pinetab64:matrix.org #pinetab64:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://matrix.to/#/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #Pinetime
|-
| PineTime Development
| [https://matrix.to/#/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| PineBuds Pro
| [https://matrix.to/#/#pinebuds:matrix.org #pinebuds:matrix.org]
| [https://t.me/+nJVhM0mZ9KhlYmZl @pinebuds]
| Unavailable
|-
| Pinecil
| [https://matrix.to/#/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinecil Development
| [https://matrix.to/#/#pinecil-dev:matrix.org #pinecil-dev:matrix.org]
| [https://t.me/+8_pdKqXrVuQ4OTk1 Pinecil-dev]
| Unavailable
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| PineCube
| [https://matrix.to/#/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker, Ox64
| [https://matrix.to/#/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://matrix.to/#/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://matrix.to/#/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}

There is also an unofficial Matrix Space at [https://matrix.to/#/#pine64-space:matrix.org #pine64-space:matrix.org] for supported clients that organizes all of the above matrix channels into one place.

=== Forums ===

PINE64 runs an official forum powered by the open-source forum server software ''MyBB''. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

== Helpful Information for Beginners ==

* '''[[Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[How to Contribute]]''': Information about how to contribute to different partner projects
* '''[[Where to Report Bugs]]''': Information about how to report bugs
* '''[[Project]]''': A variety of well documented PINE64 projects to serve as inspiration

User:Thomzane/Woodpecker

2023-09-05T00:17:21Z

Thomzane: Correct markdown to markup.

The '''Woodpecker''' Edition Serial Console is powered by the CH340G chipset enabled simple USB to Serial communication for PINE64 related project development.

The S1 jumper can be set to 5V or 3.3V.

[https://pine64.com/product/serial-console-woodpecker-edition/ PINE64 store page]

User:Thomzane/Woodpecker

2023-09-05T00:16:44Z

Thomzane: Creating the wiki page for the woodpecker

The '''Woodpecker''' Edition Serial Console is powered by the CH340G chipset enabled simple USB to Serial communication for PINE64 related project development.

The S1 jumper can be set to 5V or 3.3V.

[PINE64 store page](https://pine64.com/product/serial-console-woodpecker-edition/)

PinePhone APN Settings

2022-05-17T20:58:46Z

Thomzane: Add settings for AT&T in USA

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 (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>

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

== 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-18.1/prebuilt/common/etc/apns-conf.xml

[[Category:PinePhone]]

PinePhone Carrier Support

2022-05-17T20:54:37Z

Thomzane: Update AT&T carrier notes.

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

== 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 || No || Yes || Yes ||
*postMarketOS - Phosh 2021/8/15
|-
| USA || TracFone (T-Mobile) || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021-10-06
|-
| 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.

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

== 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]]

PinePhone Carrier Support

2022-05-17T20:48:59Z

Thomzane: Add AT&T

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

== 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 || No || Yes || Yes ||
*postMarketOS - Phosh 2021/8/15
|-
| USA || TracFone (T-Mobile) || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021-10-06
|-
| 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. 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).

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

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

== 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]]

Pinecil

2022-05-16T20:31:55Z

Thomzane: Add 3D printed Multipart Pinecil Case by Pjotrke

[[File:Pinecil-bb2-01_rotate.jpg|400px|thumb|right|The Pinecil]]

The '''Pinecil''' is a portable, temperature controlled soldering iron. It also has the intended use of being a Risc-V development device using a breakout board.

== Description ==
The Pinecil's main features are:

* Portability
* Settable temperature
* Soldering tips:
** Replaceable
** More than half a dozen available. [https://pine64.com/product-category/pinecil/ Currently sold] as 2 separate sets of 4, one fine set, the other larger.
** Compatible with TS100
* Flexible power sources:
** Barrel jack
** USB Type C power delivery
* GD32V Development platform
** Board schematics are open. Software is open. Create your own!
** [https://pine64.com/product/pinecil-break-out-board/ Pinecil breakout board]lets you use JTAG, GPIO, A2D, SPI, and more.

There are additional features that include (Useful for devkit use):

* A Programmable Gigadevice Risc-V GD32VF103 embedded processor
* 0.67" Monochrome Display that can render text or graphics
* Support for Idle detection, for automatic power down of tip
* Programmable with [https://doc.nucleisys.com/nuclei_sdk/design/soc/gd32vf103.html tools from Gigadevice], [https://github.com/riscv-software-src/homebrew-riscv HomeBrew] or [https://wiki.debian.org/RISC-V#Cross_compilation Linux RISC-V].

== Usage ==

Pinecil comes with a separate heating element / tip. After inserting its barrel into the end of the handle, lightly tighten the screw onto it. Loosen this screw when changing out the tip.

The USB port, connected to any host, provides enough power to drive the user interface, but not necessarily enough to heat the tip. 5 volts from a USB 2 port will only display the user interface.

To check the firmware version, hold down the "-" button. It will display something like "v2.14.2425902 17-01-21", suggesting its actual release date, here 2021-01-17. Clicking the "+" button repeatedly reveals various internal settings, such as hardware version, current temperature, time since power-on, and number of motions detected. Clicking "-" returns to the regular display of current temperature, target temperature, and supply voltage. At other times it may show power draw.

To actually heat up the tip, you will need a power supply that can provide 12V or more. This may be a dedicated power supply with a standard barrel connector (+ center, - outside) that supplies anywhere from 12V to 21V, or a USB-C supply that can negotiate up to such a voltage. (You probably have a suitable supply disused in a box somewhere. Most Android chargers since about 2015 should work.)

Clicking "+" starts the tip heating. The display then shows power draw, current temperature, supply voltage, and estimated time to reach target temperature. You can adjust the target temperature with further clicks of "+" and "-" buttons. Waiting for the regular display to return, then holding down "-" for a moment turns the heat off. You can watch the temperature measurement go up and down. Certain settings involve holding down both buttons.

The iron will "sleep", switching to a lower temperature, after it has been put down for a short time, and heat up again when it is picked up.

Clicking "-" when heat is off steps through menus to control a variety of settings, such as the sleep temperature, time until sleep, motion sensitivity, temperature units (C or F) etc.

'''Menu Items''' items (accurate for firmware 2.16)

* Power settings
** Power source (cutoff choices for voltage and battery operation)
** QC voltage (voltage to negotiate for with QC chargers (9..22 volts in 0.2V steps, recommended up to 21 volts)
** PD timeout (compatibility setting for some picky QC power supplies, allowing to set a shorter amount of time for PD negotiation in 100ms steps)
* Soldering Settings
** Boost Temperature
** Heat on power up (Auto Start)
** Temperature Change (short click)
** Temperature Change (long click)
** Allow locking buttons (when soldering)
* Sleep mode
** Motion Sensor Sensitivity
** Sleep Temperature
** Sleep Timeout
** Shutdown Timeout
** Hall Sensor Sensitivity
* User Interface
** Temperature Units (C/F)
** Display orientation (auto/right/left)
** Cooldown Blink
** Scrolling Speed (slow/fast)
** Reverse +/- buttons
** Animation speed (off/slow/medium/fast)
** Animation loop
** Screen brightness (1..10)
** Screen inversion
** Detailed idle screen
** Detailed solder screen
* Advanced Settings
** Power Limit (watts)
** Factory Reset?
** Calibrate Temperature
** Calibrate Voltage
** Power Pulse (watts)

== Pictures ==

Pre-release:
<gallery>
File:Pinecil_Exploded_Diagram_ver_0.9.png|Pinecil renders|alt=alt language
File:PinecilPrototype.jpg|Pinecil prototype|alt=alt language
</gallery>

Production:
<gallery>
File:Pinecil-bb2-01.jpg|Pinecil and TS-B2 retail package|alt=alt language
File:Pinecil-Case-Red-1.jpg|Pinecil red casing|alt=alt language
</gallery>

== Pinecil tips ==
* Uses TS-100 compatible tips
* Tip model TS-B2 is the default tip supplied with the Pinecil
* Tip set 1 (left) & 2 (right): 
[[File:PinecilTipSets.jpg|800px]]

== Specifications ==
* '''Dimensions:''' 170mm with solder tip or 98mm without solder tip x 12.8mm x 16.2mm
* '''Weight:''' 30g with solder tip, 20g without solder tip
* '''CPU:''' GD32VF103TB 32-bit RV32IMAC RISC-V “Bumblebee Core” @ 108 MHz
* '''Display:''' 0.67" QUG 9616TSWCG02 96x16 Monochrome Matrix display
* '''Memory:'''
** 128KB Flash
** 32KB SRAM
* '''DC in (only one of the following at a time):'''
** 12V- 21V DC5525 Barrel Jack - Using a 5521 (which requires excessive force) will [https://forum.pine64.org/showthread.php?tid=13237 BREAK the connector].
** USB-C 12-20V PD
** QC3.0
** Recommend operating voltage 12-21V, some components can tolerate higher voltages at "absolute maximum" but it's very ill-advised

== Pinecil board information, schematics and certifications ==

* Pinecil mainboard schematic:
** [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v1.0a_20201120.pdf Pinecil mainboard schematic ver 1.0 20201120, this is production version schematic]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Top PDF file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Bottom PDF file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Top Drawing file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Bottom Drawing file]

* Pinecil certifications:
** [https://files.pine64.org/doc/cert/Pinecil%20CE%20RED%20Certificate-S20102803801001.pdf Pinecil CE RED Certificate]
** [https://files.pine64.org/doc/cert/Pinecil%20FCC%20Certificate-S20102803802001.pdf Pinecil FCC Certificate]
** [https://files.pine64.org/doc/cert/Pinecil%20RoHS10%20Certificate-S20102803803001.pdf Pinecil ROHS Certificate]

* Pinecil breakout board schematic:
** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_Schematic_v1.0_20201005.pdf Pinecil breakout board schematic ver 1.0 20201005]
** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_PCB_layout_v1.0_20201005.pdf Pinecil breakout board PCB layout ver 1.0]
* Photos:
<gallery>
File:Pinecil-breakout-board-02.jpg|Store photo
File:Pinecil breakout top.jpg|Top view
File:Pinecil breakout bottom.jpg|Bottom view
</gallery>

== Manuals ==
* [[:File:USER MANUAL - QUICK START PINECIL multi lang EU+DE+FR.pdf|Pinecil Quick Start Guide]]
* [[:File:Pinecil Shell Replacement Guide.pdf|Pinecil Shell Replacement Guide]]

== Firmware ==

The official firmware that comes with the Pinecil is IronOS. You will want that if you just want to use your Pinecil as a soldering iron. It's a good idea to check for updates periodically, as development is very active and there may be new bug fixes available.

If you want to see the latest versions, visit the [https://github.com/Ralim/IronOS/releases GitHub repository for IronOS, from Ralimtek]

For update instructions, please visit the [https://github.com/Ralim/IronOS/blob/master/Documentation/Flashing.md#pinecil-pine64 update documentation on GitHub].

== Development efforts ==

{| class="wikitable"
!
! Project Homepage
! Firmware Images
! Description

|-
! Ralimtek
| [https://github.com/Ralim/IronOS/ Ralim/IronOS]
| https://github.com/Ralim/IronOS/releases/
| Officially endorsed Pinecil firmware
|-
! Alvin Wong
| [https://github.com/alvinhochun/gd32vf103-pinecil-demo-rs alvinhochun/gd32vf103-pinecil-demo-rs]
|
| Collection of Rust code demos for Pinecil
|}

== Batch changes ==

* For the first manufacture batch (October 2020, order number 158xxx) of the Pinecil, the copper ring connecting the earth screw to the tip was omitted as the engineering team found the TS100 design lacking. For the second round onwards, an improved design copper ring has been included as standard, and is also included with the replacement red and black handles. For normal operation of the iron, omission of the ring does not impact it's operation. If you are working with ESD components, you will however need it in order to ground the iron tip via the earth screw at the back of the iron.

* The first batch of Pinecil's were rated 12-24v @ 65W. After some heated discussion on the discussion group, it was decided that it would be downgraded to 12-21V @ 60W, due to concern over the connection of the DC jack to the USB-PD chip, which has a recommended maximum of 21v, and absolute maximum of 28v.

== Disassembly steps ==

# Remove tip if present.
## Let tip cool down.
## Loosen top (display side) screw (PH1) on the tip side of the device.
## Gently pull tip out.
# Slide rubber off towards the tip side.
# Remove the ground screw (longer screw on the top side towards the port side) (PH1).
# Remove the bottom screw (at the tip side, between the legs) (PH1).
# Slightly pull the two halves of the case apart at the tip side, enough to get a fingernail or guitar pick between the halves.
# Move the pick down the length of the split to loosen the bottom half's clips from the top half of the case.
# Once loose, remove the bottom half by moving it forward (it is retained by the top half at the port side).
# Remove the screws retaining the copper tip contacts (PH000, M1.4 x 5).
# Remove the now loose copper tip contacts.
# Gently push the board towards the tip side by pushing on one of the ports (for example, by using a misaligned USB C connector).
# The PCB assembly is now free to be lifted out.
## The key caps are now no longer retained, carefully set aside the top half, or remove the caps and store them separately.

== Assembly steps ==

# Place the key caps into their recesses in the top half of the case.
# Place the PCB assembly into the top half of the case ports first.
## Lower the rest of the board into the case and move the PCB assembly towards the port side of the case (the DC barrel connector may be a firm place to gently push).
# Install the copper tip contacts.
## Orient the contact to align the alignment pin with the alignment hole next to the big hole on one of the big gold pads.
## Install and gently tighten the PH000 screw until the clip is no longer loose.
# Place the bottom half of the case into the top half by sliding the lip on the port side (side without the feet) of the bottom half under the arch of the port side of the top half.
# Gently close the case by bringing the two halves together, paying attention to each clip's alignment and ensuring the case edges align.
# Install the short PH1 screw at the bottom of the tip side of the case.
# Install the longer PH1 screw at the ground connection point at the top side of the case (between the display and the ports).
# Slide the rubber sleeve on (larger ridge first).
# Gently insert tip.
# Gently tighten the top PH1 screw to retain the tip.

== Power Supply Compatibility ==

The Pinecil can either work with a 12-21V battery or power supply via the 5525 (5.5mm outer diameter, 2.5mm post) centre-positive jack, or with any USB power supply that supports the QC2, QC3 or USB-PD (Power Delivery) specification. QC2 and most QC3 power supplies will only be able to provide a maximum of 12V, limiting the Pinecil to about 17W of thermal capability. A suitable USB-PD power supply / power bank will be able to provide 20V, allowing the Pinecil to deliver the full 60W of heat to soldering tip.

For certain QC power adapters, there is a limited time for QC negotiation, otherwise voltage will fall back to 5V. 
Starting from firmware v2.16, there is a PD timeout setting (in 100ms steps) which allows QC negotiation start earlier. 
This enables some QC adapters to work (like some of the Baseus QC chargers) but may result problems with PD negotiation on slower PD adapters.

For certain adapters, a PD timeout value of 15 is needed while most of PD adapters are also work using this value.

Known working QC/PD/barrel power adapters / power banks include:

Power adapter:
* [https://pine64.com/product/pinepower-120w-desktop-power-supply-us-version/ PinePower Desktop]
* [https://www.nekteck.com/product/usb-if-certified-usb-c-charger-nekteck-60w-type-c-wall-charger-power-delivery-pd3-0-travel-charger-compatible-with-macbook-pro-2018-macbook-air-ipad-pro-pixel-3-galaxy-note-9-s9-with-6ft-cable/ Nekteck 60W with 6ft cable]
* Notebook AC Adapter HP L30757-002 (PD@20V)
* Notebook AC Adapter Lenovo ADLX65YLC3D (PD@20V)
* Notebook AC Adapter Lenovo LN-A0403A3C (Barrel 20V/2A)
* Notebook AC Adapter Delta Electronics ADP-65JH BB (DC@19V) and ADP-90CD DB
* Notebook AC Adapter LITEON PA-1700-02 (DC@18.5V, 65W)
* Smartphone Charger Samsung EP-TA20EWE (QC2@9V)
* Smartphone Charger Google Pixel G1000-US (PD@9V)
* Nintendo Switch AC Adapter (USB-C wall-wart) (PD@15V)
* Notebook Docking Station HP Thunderbolt Dock 230W G2 (PD@20V)
** (had problems with lower firmware versions, but works fine Pinecil firmware: 2.15 and DockingStation firmware: 1.0.69.1)
* Ankosen 65W USB C Charger for Mac Book and Laptop Fast Wall Charger, GaN PD 3.0 Power Adapter Amazon $9.99 (https://www.amazon.com/dp/B08T1P7ZRW)
* Apple 140W USB-C Power Adapter A2452 (PD@20V)
* Amazon Basics 65W One-Port GaN USB-C PD 3.0 (https://www.amazon.com/gp/product/B087MD5MYH)
* Charger Harbor SAIL01 65W Dual USB-C Power Delivery GaN PPS $12.99 (https://www.amazon.com/dp/B097CVQ868)

Adapters:
* Elecjet AnyWatt SQ, USB-C to Lenovo Square Slim-Tip Adapter 45W or 65W, used with a 65W Lenovo Supply (PD@20V, Pinecil shows 64W)

Power bank:
* [http://beta.blitzwolf.com/-p-15.html Blitzwolf BW-P1 10400mAh QC2]
* [https://www.bestbuy.com/site/insignia-80w-26800-mah-portable-charger-for-most-usb-c-laptops-black/6419522.p?skuId=6419522 Insignia 80W 26,800mAh NS-PWLB80]
* Baseus BiPow 10000mAh 18W PD&QC3.0
* [https://www.amazon.de/gp/product/B07KRLRCDJ/ Intenso 7332330 Powerbank PD 10000 - External Battery PowerDelivery & QuickCharge3] - 10000mAh Powerbank, the Pinecil shows 12V and about 17W when heating up, using USB C PD (Red Silicone Pinecil cable)
* Marbero M87 30W PD 3.0
* [https://www.amazon.co.uk/Charmast-23800mAh-Delivery-Portable-Compatible/dp/B08ML1PHB2 Charmast C2032 65W Power Bank], maximum power at 20V is only available from the IN/OUT usb C port, the OUT usb C port delivers only 12V.

Limited usability:
* Nillkin 63W USB Car Charger Quick Charge 3.0 PD (Pinecil Firmware: 2.14.2425902)
** QC3@9V/12V and PD@15V work, PD@20V doesn't
** PD@20V works fine when using PDC004-20V or ZY12PDN on dc jack (DC@20V, limit: 45W)

Not compatible:
* Smartphone Charger RAVpower 30W Dual USB Turbo Wall Charger (Should provide QC3@9V/12V, but only provides 5 V on both ports)
* Sabrent HB-B7C3 USB3 hub, 7 data ports, 3 charge ports, 60W supply -- does not negotiate higher voltages.

== Cases and 3D Models ==

* [https://github.com/kohkohwastaken/3D-Models/tree/main/Pine64 3D model of Pinecil by kohkoh]
* [https://www.thingiverse.com/thing:4727212 Pinecil compact case]
* [https://www.thingiverse.com/thing:4723235 Pinecil and tips case]
* [https://www.thingiverse.com/thing:4734830 T12 Tip Adapter]
* [https://www.thingiverse.com/search?q=pinecil Thingiverse search for 'Pinecil']
* [https://www.thingiverse.com/thing:5186002 Multipart Pinecil Case by Pjotrke]

== Caring for a soldering iron ==

https://www.weller-tools.com/how-to-care-for-soldering-iron-tips/

https://www.eevblog.com/forum/beginners/best-way-to-clean-oxidized-soldering-iron-tip/

== Checklist ==

Upon receipt, or buying a used Pinecil, one may want to check the following:
# the display turns on when 5-21V is supplied
#* via USB type C or 5525 center positive barrel
# it gets 20V from a 20V capable USB PD charger
#* check both orientations of the type C connector
# in update mode, it shows up on a computer as a GD32 DFU bootloader (or longan nano)
#* this requires a data capable USB cable
#* to enter update mode, press <code>-</code> (button near back/ground screw) while powering on
# both buttons work
#* <code>-</code> to enter menu or decrease temperature, long press to get software version info or to turn off heating
#* <code>+</code> to turn on heating or select a menu item
# the displayed text rotates according to gravity when orientation is set to Automatic
#* menu -> User interface -> Display orientation -> Automatic
# all 3 external screws are present
## one near the back near the screen (ground screw)
## one at the front on top (to hold the tip in)
## one at the front on the bottom (to hold the case together)
# the tip is clean (uniformly silver at the front, with no pitting or texture)
#* see [[#Caring for a soldering iron]] in case it is used
# it heats up an installed tip, and stops increasing when it reaches the set point
#* this may draw up to ~3A, make sure the supply can provide that
#* minor overshoot may occur, but, disconnect power if the temperature keeps going up
# the reported temperature is correct
#* if no direct measurement is possible, set it to ~230°C and see if it melts SAC (lead-free) solder (~190°C for leaded)
# if there are multiple tips, check all of them

== Datasheets for components and peripherals ==
* GigaDevice RISC-V SoC information:
** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_Datasheet_Rev%201.1.pdf GigaDevice RISC-V GD32VF103TB SoC Datasheet V1.1]
** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_User_Manual_EN_V1.2.pdf GigaDevice RISC-V GD32VF103TB SoC Usermanual V1.2]
* Display Module information:
** [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG 9616TSWCG02 Display Module Datasheet]
* USB Type-C PD Controller information:
** [https://files.pine64.org/doc/datasheet/pinecil/FUSB302-D.PDF ON Semiconductor FUSB302 USB Type-C PD Controller Datasheet]
* Sensor information:
** [https://files.pine64.org/doc/datasheet/pinecil/BMA223-Bosch.pdf Bosch BMA223 Acceleration Sensor Datasheet]
** [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Silicon Lab Si7210 Hall-Effect Magnetic Position Sensor Datasheet]
** [https://files.pine64.org/doc/datasheet/pinecil/TMP35_36_37.pdf Analog Device TMP36 Temparature Sensor Datasheet]
* Power Regulator information:
** [https://files.pine64.org/doc/datasheet/pinecil/RT7272B-05.pdf Ricktek RT7272B 3A Switching Power Regulator Datasheet - on mainboard]
** [https://files.pine64.org/doc/datasheet/pinecil/LP6498B6F.pdf LowPowerSemi LP6498B6F 1.2A Switching Power Regulator Datasheet - on breakout board]
* Power MOSFET Switch information:
** [https://files.pine64.org/doc/datasheet/pinecil/Changjiang-Electronics-Tech-CJ-CJQ7328.pdf Chang Jiang CJQ7328 8A MOSFET Datasheet]
* OP Amp information:
** [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGMicro SGM8557-1 Low Noise OP Amp Datasheet]

== Community links ==

* [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Telegram]
* [https://matrix.to/#/#pinecil:matrix.org Matrix]
* [https://discordapp.com/invite/DgB7kzr Discord]

[[Category:Pinecil]]

Pinecil

2022-03-09T01:49:31Z

Thomzane: Update notes based on my experience flashing IronOS 2.17 on the 2nd batch with the help of the forum.

[[File:Pinecil-bb2-01_rotate.jpg|400px|thumb|right|The Pinecil]]

The '''Pinecil''' is a portable, temperature controlled soldering iron. It also has the intended use of being a Risc-V development device using a breakout board.

== Description ==
The Pinecil's main features are:

* Portability
* Settable temperature
* Soldering tips:
** Replaceable
** More than half a dozen available. Currently sold as 2 separate sets of 4, one fine set, the other larger.
** Compatible with TS100
* Flexible power sources:
** Barrel jack
** USB Type C power delivery

There are additional features that include (Useful for devkit use):

* A Programmable Gigadevice Risc-V GD32V embedded processor
* 0.67" Monochrome Display that can render text or graphics
* Support for Idle detection, for automatic power down of tip

== Usage ==

Pinecil comes with a separate heating element / tip. After inserting its barrel into the end of the handle, lightly tighten the screw onto it. Loosen this screw when changing out the tip.

The USB port, connected to any host, provides enough power to drive the user interface, but not necessarily enough to heat the tip. 5 volts from a USB 2 port will only display the user interface.

To check the firmware version, hold down the "-" button. It will display something like "v2.14.2425902 17-01-21", suggesting its actual release date, here 2021-01-17. Clicking the "+" button repeatedly reveals various internal settings, such as hardware version, current temperature, time since power-on, and number of motions detected. Clicking "-" returns to the regular display of current temperature, target temperature, and supply voltage. At other times it may show power draw.

To actually heat up the tip, you will need a power supply that can provide 12V or more. This may be a dedicated power supply with a standard barrel connector (+ center, - outside) that supplies anywhere from 12V to 21V, or a USB-C supply that can negotiate up to such a voltage. (You probably have a suitable supply disused in a box somewhere.)

Clicking "+" starts the tip heating. The display then shows power draw, current temperature, supply voltage, and estimated time to reach target temperature. You can adjust the target temperature with further clicks of "+" and "-" buttons. Waiting for the regular display to return, then holding down "-" for a moment turns the heat off. You can watch the temperature measurement go up and down. Certain settings involve holding down both buttons.

The iron will "sleep", switching to a lower temperature, after it has been put down for a short time, and heat up again when it is picked up.

Clicking "-" when heat is off steps through menus to control a variety of settings, such as the sleep temperature, time until sleep, motion sensitivity, temperature units (C or F) etc.

'''Menu Items''' items (accurate for firmware 2.16)

* Power settings
** Power source (cutoff choices for voltage and battery operation)
** QC voltage (voltage to negotiate for with QC chargers (9..22 volts in 0.2V steps, recommended up to 21 volts)
** PD timeout (compatibility setting for some picky QC power supplies, allowing to set a shorter amount of time for PD negotiation in 100ms steps)
* Soldering Settings
** Boost Temperature
** Heat on power up (Auto Start)
** Temperature Change (short click)
** Temperature Change (long click)
** Allow locking buttons (when soldering)
* Sleep mode
** Motion Sensor Sensitivity
** Sleep Temperature
** Sleep Timeout
** Shutdown Timeout
** Hall Sensor Sensitivity
* User Interface
** Temperature Units (C/F)
** Display orientation (auto/right/left)
** Cooldown Blink
** Scrolling Speed (slow/fast)
** Reverse +/- buttons
** Animation speed (off/slow/medium/fast)
** Animation loop
** Screen brightness (1..10)
** Screen inversion
** Detailed idle screen
** Detailed solder screen
* Advanced Settings
** Power Limit (watts)
** Factory Reset?
** Calibrate Temperature
** Calibrate Voltage
** Power Pulse (watts)

== Pictures ==

Pre-release:
<gallery>
File:Pinecil_Exploded_Diagram_ver_0.9.png|Pinecil renders|alt=alt language
File:PinecilPrototype.jpg|Pinecil prototype|alt=alt language
</gallery>

Production:
<gallery>
File:Pinecil-bb2-01.jpg|Pinecil and TS-B2 retail package|alt=alt language
File:Pinecil-Case-Red-1.jpg|Pinecil red casing|alt=alt language
</gallery>

== Pinecil tips ==
* Uses TS-100 compatible tips
* Tip model TS-B2 is the default tip supplied with the Pinecil
* Tip set 1 (left) & 2 (right): 
[[File:PinecilTipSets.jpg|800px]]

== Specifications ==
* '''Dimensions:''' 170mm with solder tip or 98mm without solder tip x 12.8mm x 16.2mm
* '''Weight:''' 30g with solder tip, 20g without solder tip
* '''CPU:''' GD32VF103TB 32-bit RV32IMAC RISC-V “Bumblebee Core” @ 108 MHz
* '''Display:''' 0.67" QUG 9616TSWCG02 96x16 Monochrome Matrix display
* '''Memory:'''
** 128KB Flash
** 32KB SRAM
* '''DC in (only one of the following at a time):'''
** 12V- 21V DC5525 Barrel Jack
** USB-C 12-20V PD
** QC3.0
** Recommend operating voltage 12-21V, some components can tolerate higher voltages at "absolute maximum" but it's very ill-advised

== Pinecil board information, schematics and certifications ==

* Pinecil mainboard schematic:
** [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v1.0a_20201120.pdf Pinecil mainboard schematic ver 1.0 20201120, this is production version schematic]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Top PDF file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Bottom PDF file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Top Drawing file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Bottom Drawing file]

* Pinecil certifications:
** [https://files.pine64.org/doc/cert/Pinecil%20CE%20RED%20Certificate-S20102803801001.pdf Pinecil CE RED Certificate]
** [https://files.pine64.org/doc/cert/Pinecil%20FCC%20Certificate-S20102803802001.pdf Pinecil FCC Certificate]
** [https://files.pine64.org/doc/cert/Pinecil%20RoHS10%20Certificate-S20102803803001.pdf Pinecil ROHS Certificate]

* Pinecil breakout board schematic:
** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_Schematic_v1.0_20201005.pdf Pinecil breakout board schematic ver 1.0 20201005]
** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_PCB_layout_v1.0_20201005.pdf Pinecil breakout board PCB layout ver 1.0]
* Photos:
<gallery>
File:Pinecil-breakout-board-02.jpg|Store photo
File:Pinecil breakout top.jpg|Top view
File:Pinecil breakout bottom.jpg|Bottom view
</gallery>

== Firmware Image Releases ==

* [https://github.com/pine64/pinecil-firmware-updater/releases/latest Latest Pinecil Firmware Updater] for MacOS and Windows

* [https://files.pine64.org/os/Pinecil/Pinecil_firmware_20201115.zip Pinecil production firmware 20201115, thanks to Ralimtek]

Links to development firmware and documentation:

* [https://github.com/Ralim/IronOS/releases GitHub repository for IronOS, from Ralimtek]
* [https://github.com/Ralim/IronOS/blob/master/Documentation/Flashing.md GitHub link for IronOS flashing documentation]

== Batch changes ==

* For the first manufacture batch (October 2020, order number 158xxx) of the Pinecil, the copper ring connecting the earth screw to the tip was omitted as the engineering team found the TS100 design lacking. For the second round onwards, an improved design copper ring has been included as standard, and is also included with the replacement red and black handles. For normal operation of the iron, omission of the ring does not impact it's operation. If you are working with ESD components, you will however need it in order to ground the iron tip via the earth screw at the back of the iron.

* The first batch of Pinecil's were rated 12-24v @ 65W. After some heated discussion on the discussion group, it was decided that it would be downgraded to 12-21V @ 60W, due to concern over the connection of the DC jack to the USB-PD chip, which has a recommended maximum of 21v, and absolute maximum of 28v.

== Development efforts ==

{| class="wikitable"
!
! Project Homepage
! Firmware Images
! Description

|-
! Ralimtek
| [https://github.com/Ralim/IronOS/ Ralim/IronOS]
| https://github.com/Ralim/IronOS/releases/
| Officially endorsed Pinecil firmware
|-
! Alvin Wong
| [https://github.com/alvinhochun/gd32vf103-pinecil-demo-rs alvinhochun/gd32vf103-pinecil-demo-rs]
|
| Collection of Rust code demos for Pinecil
|}

== How to update a firmware ==

The official firmware that comes with the Pinecil is IronOS, you will want that if you just want to use your Pinecil as a soldering iron.

If you're using the manual firmware update method described below, you can [https://github.com/Ralim/IronOS/releases/ download new IronOS releases from here].

While you can't brick your Pinecil permanently (DFU is in ROM); a firmware update can make your Pinecil inoperable if you flash an invalid firmware. However, flashing a working firmware using these same instructions will remedy that.

{{warning|1=Do not have a barrel jack PSU plugged in at the same time as a USB-C cable. Doing this will severely damage your computer, or Type-C PSU.}}
=== With application ===

# Download Pinecil Firmware Updater for [http://pinecil.pine64.org/updater/get-binaries.php?platform=win64 Windows], [http://pinecil.pine64.org/updater/get-binaries.php?platform=macos64 MacOS], or build by yourself from [https://github.com/pine64/pinecil-firmware-updater sources].
# (Windows only) Be sure that you have installed Microsoft Visual C++ Redistributable x64. Else, you can download it [http://pinecil.pine64.org/updater/vc_redist.x64.exe here]
# Open it, select operating system you want to flash and click '''Flash'''. (Don't connect Pinecil yet)
# Follow application instructions for correct Pinecil connection to your PC.
# '''In case of error''': If you will get error about erasing the Pinecil, you need to tick '''Mass Erase''' checkbox and try again.

=== Manually ===

Method tested on Linux, should work on any OS which supply dfu-util 0.10+.

# Use the command <code>dfu-util -V</code> to check your version. If your distro comes with 0.9 you might soft-brick your Pinecil, install the latest stable release from [http://dfu-util.sourceforge.net/ sourceforge].
# Enter the update mode. For that, unplug a barrel jack PSU if you have one plugged in. Then, plug USB cable while holding *-* button (button that's closest to USB-C port). The screen may be blank which is fine.
# Check that your Pinecil is available by listing devices with <code>dfu-util -l</code> and look for device with 28e9:0189 ID. Try running with sudo if your device is not listed. If dfu-util reports <code>alt=0, name="@Internal Flash /0x08000000/128*001Kg"</code> you are fine, otherwise you need to upgrade to 0.10+, important part is <code>128*001Kg</code>, which is flash amount of blocks and block size, as a chip used in Pinecil have 128 KB of Flash with 1KB page size
# Make a firmware backup: <code>dfu-util -d 28e9:0189 -a 0 -U ~/pinecil/internal.flash.stock -s 0x08000000</code>
## <code>28e9:0189</code> -- USB Device ID (can be obtained from <code>lsusb</code> or <code>dfu-util -l</code> but in dfu-util output it might be hard to identify the Pinecil device)
## <code>-a 0</code> -- selects partition to flash. List of possible options can be obtained via <code>dfu-util -l</code>. Partition 0 - internal SPI flash. Partition 1 - fuses (description of fuses can be found in User Manual for the chip)
## <code>-U</code> -- specifies a mode. U is upload, which means that firmware will be downloaded and saved to file (yes, that's confusing, but it is what it is, feel free to verify that in a manual of your version of dfu-util). Command must be followed by a path to file where you want to save your firmware. dfu-util will refuse to dump firmware if you already have a file with that name.
## <code>-s 0x08000000</code> -- specify the address in a flash from which dump will start. This can be obtained from <code>dfu-util -l</code>.
# Flash a new firmware: <code>dfu-util -d 28e9:0189 -a 0 -D Pinecil_EN.bin -s 0x08000000:mass-erase:force</code>
## <code>-D</code> -- is a mode to Download firmware to the device (yes, that's confusing, but you indeed Upload from device and Download to device with dfu-util). That should follow the file with the firmware. Update archive from Ralim usually contains two files: <code>.hex</code> and <code>.bin</code>. One that is required - is <code>.bin</code>. <code>_EN</code> is the language code of the firmware, means that <code>_EN</code> will flash english version of firmware.
## <code>-s 0x08000000:mass-erase:force</code> -- specified the address where to flash the file. <code>:mass-erase:force</code> is required to force-erase flash before updating firmware with the first batch, otherwise you might have unpredictable results.
## If it fails with <code>Error during special command "MASS_ERASE" get_status</code> (as has happened with recent shipments) then use ...<code>-s 0x08000000</code> without attempting "mass-erase". Full command example: <code>dfu-util -d 28e9:0189 -a 0 -D Pinecil_EN.bin -s 0x08000000</code>
## If the hex and dfu files cannot be flashed, convert the hex file to bin with this command: <code>objcopy --input-target=ihex --output-target=binary Pinecil_EN.hex Pinecil_EN.bin</code>

== Disassembly steps ==

# Remove tip if present.
## Let tip cool down.
## Loosen top (display side) screw (PH1) on the tip side of the device.
## Gently pull tip out.
# Slide rubber off towards the tip side.
# Remove the ground screw (longer screw on the top side towards the port side) (PH1).
# Remove the bottom screw (at the tip side, between the legs) (PH1).
# Slightly pull the two halves of the case apart at the tip side, enough to get a fingernail or guitar pick between the halves.
# Move the pick down the length of the split to loosen the bottom half's clips from the top half of the case.
# Once loose, remove the bottom half by moving it forward (it is retained by the top half at the port side).
# Remove the screws retaining the copper tip contacts (PH000).
# Remove the now loose copper tip contacts.
# Gently push the board towards the tip side by pushing on one of the ports (for example, by using a misaligned USB C connector).
# The PCB assembly is now free to be lifted out.
## The key caps are now no longer retained, carefully set aside the top half, or remove the caps and store them separately.

== Assembly steps ==

# Place the key caps into their recesses in the top half of the case.
# Place the PCB assembly into the top half of the case ports first.
## Lower the rest of the board into the case and move the PCB assembly towards the port side of the case (the DC barrel connector may be a firm place to gently push).
# Install the copper tip contacts.
## Orient the contact to align the alignment pin with the alignment hole next to the big hole on one of the big gold pads.
## Install and gently tighten the PH000 screw until the clip is no longer loose.
# Place the bottom half of the case into the top half by sliding the lip on the port side (side without the feet) of the bottom half under the arch of the port side of the top half.
# Gently close the case by bringing the two halves together, paying attention to each clip's alignment and ensuring the case edges align.
# Install the short PH1 screw at the bottom of the tip side of the case.
# Install the longer PH1 screw at the ground connection point at the top side of the case (between the display and the ports).
# Slide the rubber sleeve on (larger ridge first).
# Gently insert tip.
# Gently tighten the top PH1 screw to retain the tip.

== Power Supply Compatibility ==

The Pinecil can either work with a 12-21V battery or power supply via the 5525 (5.5mm outer diameter, 2.5mm post) centre-positive jack, or with any USB power supply that supports the QC2, QC3 or USB-PD (Power Delivery) specification. QC2 and most QC3 power supplies will only be able to provide a maximum of 12V, limiting the Pinecil to about 17W of thermal capability. A suitable USB-PD power supply / power bank will be able to provide 20V, allowing the Pinecil to deliver the full 60W of heat to soldering tip.

For certain QC power adapters, there is a limited time for QC negotiation, otherwise voltage will fall back to 5V. 
Starting from firmware v2.16, there is a PD timeout setting (in 100ms steps) which allows QC negotiation start earlier. 
This enables some QC adapters to work (like some of the Baseus QC chargers) but may result problems with PD negotiation on slower PD adapters.

For certain adapters, a PD timeout value of 15 is needed while most of PD adapters are also work using this value.

Known working QC/PD/barrel power adapters / power banks include:

Power adapter:
* [https://pine64.com/product/pinepower-120w-desktop-power-supply-us-version/ PinePower Desktop]
* [https://www.nekteck.com/product/usb-if-certified-usb-c-charger-nekteck-60w-type-c-wall-charger-power-delivery-pd3-0-travel-charger-compatible-with-macbook-pro-2018-macbook-air-ipad-pro-pixel-3-galaxy-note-9-s9-with-6ft-cable/ Nekteck 60W with 6ft cable]
* Notebook AC Adapter HP L30757-002 (PD@20V)
* Notebook AC Adapter Lenovo ADLX65YLC3D (PD@20V)
* Notebook AC Adapter Lenovo LN-A0403A3C (Barrel 20V/2A)
* Notebook AC Adapter Delta Electronics ADP-65JH BB (DC@19V) and ADP-90CD DB
* Notebook AC Adapter LITEON PA-1700-02 (DC@18.5V, 65W)
* Smartphone Charger Samsung EP-TA20EWE (QC2@9V)
* Smartphone Charger Google Pixel G1000-US (PD@9V)
* Nintendo Switch AC Adapter (USB-C wall-wart) (PD@15V)
* Notebook Docking Station HP Thunderbolt Dock 230W G2 (PD@20V)
** (had problems with lower firmware versions, but works fine Pinecil firmware: 2.15 and DockingStation firmware: 1.0.69.1)
* Ankosen 65W USB C Charger for Mac Book and Laptop Fast Wall Charger, GaN PD 3.0 Power Adapter Amazon $9.99 (https://www.amazon.com/dp/B08T1P7ZRW/ref=cm_sw_r_oth_api_glt_fabc_X68FK4PW9VH02M4NK8CA?_encoding=UTF8&psc=1)
* Apple 140W USB-C Power Adapter A2452 (PD@20V)

Adapters:
* Elecjet AnyWatt SQ, USB-C to Lenovo Square Slim-Tip Adapter 45W or 65W, used with a 65W Lenovo Supply (PD@20V, Pinecil shows 64W)

Power bank:
* [http://beta.blitzwolf.com/-p-15.html Blitzwolf BW-P1 10400mAh QC2]
* [https://www.bestbuy.com/site/insignia-80w-26800-mah-portable-charger-for-most-usb-c-laptops-black/6419522.p?skuId=6419522 Insignia 80W 26,800mAh NS-PWLB80]
* Baseus BiPow 10000mAh 18W PD&QC3.0
* [https://www.amazon.de/gp/product/B07KRLRCDJ/ Intenso 7332330 Powerbank PD 10000 - External Battery PowerDelivery & QuickCharge3] - 10000mAh Powerbank, the Pinecil shows 12V and about 17W when heating up, using USB C PD (Red Silicone Pinecil cable)
* Marbero M87 30W PD 3.0
* [https://www.amazon.co.uk/Charmast-23800mAh-Delivery-Portable-Compatible/dp/B08ML1PHB2 Charmast C2032 65W Power Bank], maximum power is 47W at 20V from the IN/OUT usb C port, and 16.4W at 12V from the other OUT usb C port.

Limited usability:
* Nillkin 63W USB Car Charger Quick Charge 3.0 PD (Pinecil Firmware: 2.14.2425902)
** QC3@9V/12V and PD@15V work, PD@20V doesn't
** PD@20V works fine when using PDC004-20V or ZY12PDN on dc jack (DC@20V, limit: 45W)

Not compatible:
* Smartphone Charger RAVpower 30W Dual USB Turbo Wall Charger (Should provide QC3@9V/12V, but only provides 5 V on both ports)
* Sabrent HB-B7C3 USB3 hub, 7 data ports, 3 charge ports, 60W supply -- does not negotiate higher voltages.

== Cases and 3D Models ==

* [https://github.com/kohkohwastaken/3D-Models/tree/main/Pine64 3D model of Pinecil by kohkoh]
* [https://www.thingiverse.com/thing:4727212 Pinecil compact case]
* [https://www.thingiverse.com/thing:4723235 Pinecil and tips case]
* [https://www.thingiverse.com/thing:4734830 T12 Tip Adapter]
* [https://www.thingiverse.com/search?q=pinecil Thingiverse search for 'Pinecil']

== Caring for a soldering iron ==

https://www.weller-tools.com/how-to-care-for-soldering-iron-tips/

https://www.eevblog.com/forum/beginners/best-way-to-clean-oxidized-soldering-iron-tip/

== Checklist ==

Upon receipt, or buying a used Pinecil, one may want to check the following:
# the display turns on when 5-21V is supplied
#* via USB type C or 5525 center positive barrel
# it gets 20V from a 20V capable USB PD charger
#* check both orientations of the type C connector
# in update mode, it shows up on a computer as a GD32 DFU bootloader (or longan nano)
#* this requires a data capable USB cable
#* to enter update mode, press <code>-</code> (button near back/ground screw) while powering on
# both buttons work
#* <code>-</code> to enter menu or decrease temperature, long press to get software version info or to turn off heating
#* <code>+</code> to turn on heating or select a menu item
# the displayed text rotates according to gravity when orientation is set to Automatic
#* menu -> User interface -> Display orientation -> Automatic
# all 3 external screws are present
## one near the back near the screen (ground screw)
## one at the front on top (to hold the tip in)
## one at the front on the bottom (to hold the case together)
# the tip is clean (uniformly silver at the front, with no pitting or texture)
#* see [[#Caring for a soldering iron]] in case it is used
# it heats up an installed tip, and stops increasing when it reaches the set point
#* this may draw up to ~3A, make sure the supply can provide that
#* minor overshoot may occur, but, disconnect power if the temperature keeps going up
# the reported temperature is correct
#* if no direct measurement is possible, set it to ~230°C and see if it melts SAC (lead-free) solder (~190°C for leaded)
# if there are multiple tips, check all of them

== Datasheets for components and peripherals ==
* GigaDevice RISC-V SoC information:
** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_Datasheet_Rev%201.1.pdf GigaDevice RISC-V GD32VF103TB SoC Datasheet V1.1]
** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_User_Manual_EN_V1.2.pdf GigaDevice RISC-V GD32VF103TB SoC Usermanual V1.2]
* Display Module information:
** [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG 9616TSWCG02 Display Module Datasheet]
* USB Type-C PD Controller information:
** [https://files.pine64.org/doc/datasheet/pinecil/FUSB302-D.PDF ON Semiconductor FUSB302 USB Type-C PD Controller Datasheet]
* Sensor information:
** [https://files.pine64.org/doc/datasheet/pinecil/BMA223-Bosch.pdf Bosch BMA223 Acceleration Sensor Datasheet]
** [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Silicon Lab Si7210 Hall-Effect Magnetic Position Sensor Datasheet]
** [https://files.pine64.org/doc/datasheet/pinecil/TMP35_36_37.pdf Analog Device TMP36 Temparature Sensor Datasheet]
* Power Regulator information:
** [https://files.pine64.org/doc/datasheet/pinecil/RT7272B-05.pdf Ricktek RT7272B 3A Switching Power Regulator Datasheet - on mainboard]
** [https://files.pine64.org/doc/datasheet/pinecil/LP6498B6F.pdf LowPowerSemi LP6498B6F 1.2A Switching Power Regulator Datasheet - on breakout board]
* Power MOSFET Switch information:
** [https://files.pine64.org/doc/datasheet/pinecil/Changjiang-Electronics-Tech-CJ-CJQ7328.pdf Chang Jiang CJQ7328 8A MOSFET Datasheet]
* OP Amp information:
** [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGMicro SGM8557-1 Low Noise OP Amp Datasheet]

== Community links ==

* [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Telegram]
* [https://matrix.to/#/#pinecil:matrix.org Matrix]
* [https://discordapp.com/invite/DgB7kzr Discord]

[[Category:Pinecil]]

PinePhone Pro Developer Edition

2021-12-15T01:22:57Z

Thomzane: Update backup size

= Introduction =
The Developer Edition was the first edition of the PinePhone Pro, shipped to developers in December 2021. The aim of the the Developer Edition was to give development community access to the hardware prior to end-users, boost development efforts and allow for porting of existing mobile Linux operating systems to the new hardware.
It featured the same mainboard revision as the Explorer Edition that followed in early 2022, and came in a box that was labelled "Explorer Edition".

= Getting started =
This post is aimed strictly at developers receiving their PinePhone Pro dev units. Please note that the following instructions do not apply to Explorer Edition or other future editions of the PinePhone Pro - everything below is only pertinent to the dev phones.

Consider this a crash course rather than a comprehensive overview; you are also welcome to participate in documenting the process (and everything else related to the PinePhone Pro) on the Wiki. You can either create a Wiki account or use your [forum.pine64.org PINE64 forum] credentials to log in.

== Getting the hardware ready ==
After unpacking the PinePhone Pro from its box, detach the back cover (looking at the back of the phone, there is a fingernail notch on the left leading edge) and remove the plastic tab between the battery and mainboard. You can also flip the headphone jack privacy switch at this point - this enables UART output via the headphone jack. Serial console works the [https://wiki.pine64.org/wiki/PinePhone#Serial_console same way as on the original PinePhone.]

= Factory hardware test image =

The PinePhone Pro developer edition ships with a BSP AOSP factory image flashed to the eMMC. This image includes a number of factory applications meant to validate operation of the sensors, the modem, cameras, LCD & touch panel, etc. You’ll have to nuke the AOSP build to run a Linux installation on the PinePhone Pro. Booting from SD with the AOSP factory build present on eMMC is not possible due to the SoCs native boot order.

== Changing the language of factory AOSP ==

This is optional and only if you want to test out the AOSP test image.

# Swipe up from the bottom of the screen.
# Tap on the Gear icon.
# Tap on the 2nd from last option that has an i inside of a circle icon.
# Tap on the first choice with the globe icon.
# Tap on the first choice with the language icon.
# Tap on the second choice to add another language.
# Tap on your language in the list.
# If there is a secondary choice required, tap on the preferred country.
# Tap the four horizontal bars icon to the right of the new second language and drag to the top of the list to set the new language as the default.

== Backing up the factory AOSP ==

It may be a good idea to create an image of the eMMC in case you want to flash it back. Free up at least 117GB of disk space. Install <code>adb</code>.

<code>adb root && adb pull /dev/block/mmcblk1 ~/pinephonepro-factory-AOSP.img</code>

== Nuking the factory AOSP installation ==

To be able to boot from the microSD card easily it is recommend to wipe the bootloader from the pre-installed operating system on the eMMC due to the eMMC being higher in the boot priority than the microSD card.

=== Method 1: Via ADB ===
In the factory test image, navigate to setting (gear icon) > at the very bottom of the settings list you will find a phone icon with rk3999mid written underneath it > tap the last (bottom) setting 7 times in quick succession. Following this, you *may* need to do the following: open the Settings application and enable USB debugging in Settings > System > Developer Options > USB debugging. Then connect the PinePhone Pro to your PC with the supplied USB-C cable.

Please note: It is recommended to charge the device to at least 50% before proceeding with wiping the eMMC.

{{Hint|Note: You may have gotten a Chinese factory image; in the settings menu you can change the language to English by selecting the gray info icon (系统, one from bottom), then the first option (语言..), and again the first option (also 语言), then press +, English and drag it to the top of the list).}}

Connect the phone to your computer and check <code>adb devices</code> in the terminal. The phone should be registered as attached. If the device doesn't show you may want to try a different port or cable. Then enter <code>adb shell</code> followed by <code>su</code> to gain root access. At this point you can erase the eMMC installation:

<code>cat /dev/zero > /dev/block/mmcblk1</code>

The phone will freeze and then the screen will go blank. Let it sit for no less than 10 minutes and then power it off by holding down the power button. You’ll know the phone is powered down when the notification LED turns off.

=== Method 2: Via serial cable ===

Another method of erasing the image is to connect serial console, break into U-Boot when it says to press Ctrl-C, and then the "mmc erase" command can be used to zero blocks on the eMMC. For example, "mmc erase 0 16384" will zero the first 8MB, and is enough to stop it from being bootable. The baud rate for the serial console is 1500000.

== Flashing Linux ==
You will want to do all your testing and development on a SD card; you DO NOT want to flash an OS to eMMC at this time. Builds frequently break at this early development stage and recovering from a corrupted eMMC installation is presently time consuming and tedious. A fast 16-64GB micro SD card for $15 will work just fine.

There are a handful of OS builds available for the PinePhone Pro already. These can be found under the [https://wiki.pine64.org/wiki/PinePhone_Pro#Software_releases Software Releases] Wiki section.

If you are a developer porting your own distribution to the PinePhone Pro, please make sure to make an entry for it in the Software Releases section on the Wiki. If you want / need help with entering your build onto the Wiki please ping one of the mods or admins in the chats (see Forums and Chats drop-down menu).

= Resources =
Aside from the PINE64 Wiki there are also other useful resources scattered across different Wikis, repositories and blogs. In time these will be gathered into one place - the [https://gitlab.com/mobian1/devices/eg25-manager/-/merge_requests/41#note_744117720 DevZone] - which will help to streamline the development process.

At the time of publishing, these are some of the notable resource, listed in no particular order:

* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) postmarketOS Wiki]
* [https://xnux.eu/log/ Megi’s (b)log]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/ DanctNIX repository]
* [https://github.com/manjaro-pinephone Manjaro repository]

= Development and discussion =
You will run into issues, there’s just no way around it, and doing it ‘on your own’ isn’t really a viable option since you’re one of the first people to hold a PinePhone Pro. The development process on a device such as this is a collaborative process, and I therefore encourage you to participate in the community. There are many ways to interact with other developers, including [https://matrix.to/#/!LZirCxnkkeBudrQzPj:matrix.org?via=matrix.org Matrix], [https://t.me/pinephone Telegram], [https://discord.gg/pine64 Discord] and [https://www.pine64.org/web-irc/ IRC].

There is also a lesser known chat for developers only. Lesser known doesn’t mean top secret, but I will not be posting a link to it here to keep the number of non-dev participants to a minimum. If you join one of the general chats and let others know you received a dev phone, then I’m sure someone will point you in the right direction.

[[Category:PinePhone Pro]]

PinePhone Pro Developer Edition

2021-12-14T20:27:31Z

Thomzane: I left out a step.

= Introduction =
The Developer Edition was the first edition of the PinePhone Pro, shipped to developers in December 2021. The aim of the the Developer Edition was to give development community access to the hardware prior to end-users, boost development efforts and allow for porting of existing mobile Linux operating systems to the new hardware.
It featured the same mainboard revision as the Explorer Edition that followed in early 2022, and came in a box that was labelled "Explorer Edition".

= Getting started =
This post is aimed strictly at developers receiving their PinePhone Pro dev units. Please note that the following instructions do not apply to Explorer Edition or other future editions of the PinePhone Pro - everything below is only pertinent to the dev phones.

Consider this a crash course rather than a comprehensive overview; you are also welcome to participate in documenting the process (and everything else related to the PinePhone Pro) on the Wiki. You can either create a Wiki account or use your [forum.pine64.org PINE64 forum] credentials to log in.

== Getting the hardware ready ==
After unpacking the PinePhone Pro from its box, detach the back cover (looking at the back of the phone, there is a fingernail notch on the left leading edge) and remove the plastic tab between the battery and mainboard. You can also flip the headphone jack privacy switch at this point - this enables UART output via the headphone jack. Serial console works the [https://wiki.pine64.org/wiki/PinePhone#Serial_console same way as on the original PinePhone.]

= Factory hardware test image =

The PinePhone Pro developer edition ships with a BSP AOSP factory image flashed to the eMMC. This image includes a number of factory applications meant to validate operation of the sensors, the modem, cameras, LCD & touch panel, etc. You’ll have to nuke the AOSP build to run a Linux installation on the PinePhone Pro. Booting from SD with the AOSP factory build present on eMMC is not possible due to the SoCs native boot order.

== Changing the language of factory AOSP ==

This is optional and only if you want to test out the AOSP test image.

# Swipe up from the bottom of the screen.
# Tap on the Gear icon.
# Tap on the 2nd from last option that has an i inside of a circle icon.
# Tap on the first choice with the globe icon.
# Tap on the first choice with the language icon.
# Tap on the second choice to add another language.
# Tap on your language in the list.
# If there is a secondary choice required, tap on the preferred country.
# Tap the four horizontal bars icon to the right of the new second language and drag to the top of the list to set the new language as the default.

== Backing up the factory AOSP ==

It may be a good idea to create an image of the eMMC in case you want to flash it back. Free up at least 128GB of disk space. Install <code>adb</code>.

<code>adb root && adb pull /dev/block/mmcblk1 ~/pinephonepro-factory-AOSP.img</code>

== Nuking the factory AOSP installation ==

To be able to boot from the microSD card easily it is recommend to wipe the bootloader from the pre-installed operating system on the eMMC due to the eMMC being higher in the boot priority than the microSD card.

=== Method 1: Via ADB ===
In the factory test image, navigate to setting (gear icon) > at the very bottom of the settings list you will find a phone icon with rk3999mid written underneath it > tap the last (bottom) setting 7 times in quick succession. Following this, you *may* need to do the following: open the Settings application and enable USB debugging in Settings > System > Developer Options > USB debugging. Then connect the PinePhone Pro to your PC with the supplied USB-C cable.

Please note: It is recommended to charge the device to at least 50% before proceeding with wiping the eMMC.

{{Hint|Note: You may have gotten a Chinese factory image; in the settings menu you can change the language to English by selecting the gray info icon (系统, one from bottom), then the first option (语言..), and again the first option (also 语言), then press +, English and drag it to the top of the list).}}

Connect the phone to your computer and check <code>adb devices</code> in the terminal. The phone should be registered as attached. If the device doesn't show you may want to try a different port or cable. Then enter <code>adb shell</code> followed by <code>su</code> to gain root access. At this point you can erase the eMMC installation:

<code>cat /dev/zero > /dev/block/mmcblk1</code>

The phone will freeze and then the screen will go blank. Let it sit for no less than 10 minutes and then power it off by holding down the power button. You’ll know the phone is powered down when the notification LED turns off.

=== Method 2: Via serial cable ===

Another method of erasing the image is to connect serial console, break into U-Boot when it says to press Ctrl-C, and then the "mmc erase" command can be used to zero blocks on the eMMC. For example, "mmc erase 0 16384" will zero the first 8MB, and is enough to stop it from being bootable. The baud rate for the serial console is 1500000.

== Flashing Linux ==
You will want to do all your testing and development on a SD card; you DO NOT want to flash an OS to eMMC at this time. Builds frequently break at this early development stage and recovering from a corrupted eMMC installation is presently time consuming and tedious. A fast 16-64GB micro SD card for $15 will work just fine.

There are a handful of OS builds available for the PinePhone Pro already. These can be found under the [https://wiki.pine64.org/wiki/PinePhone_Pro#Software_releases Software Releases] Wiki section.

If you are a developer porting your own distribution to the PinePhone Pro, please make sure to make an entry for it in the Software Releases section on the Wiki. If you want / need help with entering your build onto the Wiki please ping one of the mods or admins in the chats (see Forums and Chats drop-down menu).

= Resources =
Aside from the PINE64 Wiki there are also other useful resources scattered across different Wikis, repositories and blogs. In time these will be gathered into one place - the [https://gitlab.com/mobian1/devices/eg25-manager/-/merge_requests/41#note_744117720 DevZone] - which will help to streamline the development process.

At the time of publishing, these are some of the notable resource, listed in no particular order:

* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) postmarketOS Wiki]
* [https://xnux.eu/log/ Megi’s (b)log]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/ DanctNIX repository]
* [https://github.com/manjaro-pinephone Manjaro repository]

= Development and discussion =
You will run into issues, there’s just no way around it, and doing it ‘on your own’ isn’t really a viable option since you’re one of the first people to hold a PinePhone Pro. The development process on a device such as this is a collaborative process, and I therefore encourage you to participate in the community. There are many ways to interact with other developers, including [https://matrix.to/#/!LZirCxnkkeBudrQzPj:matrix.org?via=matrix.org Matrix], [https://t.me/pinephone Telegram], [https://discord.gg/pine64 Discord] and [https://www.pine64.org/web-irc/ IRC].

There is also a lesser known chat for developers only. Lesser known doesn’t mean top secret, but I will not be posting a link to it here to keep the number of non-dev participants to a minimum. If you join one of the general chats and let others know you received a dev phone, then I’m sure someone will point you in the right direction.

[[Category:PinePhone Pro]]

PinePhone Pro Developer Edition

2021-12-14T19:04:17Z

Thomzane: Note about backing up.

= Introduction =
The Developer Edition was the first edition of the PinePhone Pro, shipped to developers in December 2021. The aim of the the Developer Edition was to give development community access to the hardware prior to end-users, boost development efforts and allow for porting of existing mobile Linux operating systems to the new hardware.
It featured the same mainboard revision as the Explorer Edition that followed in early 2022, and came in a box that was labelled "Explorer Edition".

= Getting started =
This post is aimed strictly at developers receiving their PinePhone Pro dev units. Please note that the following instructions do not apply to Explorer Edition or other future editions of the PinePhone Pro - everything below is only pertinent to the dev phones.

Consider this a crash course rather than a comprehensive overview; you are also welcome to participate in documenting the process (and everything else related to the PinePhone Pro) on the Wiki. You can either create a Wiki account or use your [forum.pine64.org PINE64 forum] credentials to log in.

== Getting the hardware ready ==
After unpacking the PinePhone Pro from its box, detach the back cover (looking at the back of the phone, there is a fingernail notch on the left leading edge) and remove the plastic tab between the battery and mainboard. You can also flip the headphone jack privacy switch at this point - this enables UART output via the headphone jack. Serial console works the [https://wiki.pine64.org/wiki/PinePhone#Serial_console same way as on the original PinePhone.]

= Factory hardware test image =

The PinePhone Pro developer edition ships with a BSP AOSP factory image flashed to the eMMC. This image includes a number of factory applications meant to validate operation of the sensors, the modem, cameras, LCD & touch panel, etc. You’ll have to nuke the AOSP build to run a Linux installation on the PinePhone Pro. Booting from SD with the AOSP factory build present on eMMC is not possible due to the SoCs native boot order.

== Changing the language of factory AOSP ==

This is optional and only if you want to test out the AOSP test image.

# Swipe up from the bottom of the screen.
# Tap on the Gear icon.
# Tap on the bottom option that has an i icon on the left.
# Tap on the first choice with the language icon.
# Tap on the second choice to add another language.
# Tap on your language in the list.
# If there is a secondary choice required, tap on the preferred country.
# Tap the sandwich icon to the right of the new second language and drag to the top of the list to set the new language as the default.

== Backing up the factory AOSP ==

It may be a good idea to create an image of the eMMC in case you want to flash it back. Free up at least 128GB of disk space. Install <code>adb</code>.

<code>adb root && adb pull /dev/block/mmcblk1 ~/pinephonepro-factory-AOSP.img</code>

== Nuking the factory AOSP installation ==

To be able to boot from the microSD card easily it is recommend to wipe the bootloader from the pre-installed operating system on the eMMC due to the eMMC being higher in the boot priority than the microSD card.

=== Method 1: Via ADB ===
In the factory test image, navigate to setting (gear icon) > at the very bottom of the settings list you will find a phone icon with rk3999mid written underneath it > tap the last (bottom) setting 7 times in quick succession. Following this, you *may* need to do the following: open the Settings application and enable USB debugging in Settings > System > Developer Options > USB debugging. Then connect the PinePhone Pro to your PC with the supplied USB-C cable.

Please note: It is recommended to charge the device to at least 50% before proceeding with wiping the eMMC.

{{Hint|Note: You may have gotten a Chinese factory image; in the settings menu you can change the language to English by selecting the gray info icon (系统, one from bottom), then the first option (语言..), and again the first option (also 语言), then press +, English and drag it to the top of the list).}}

Connect the phone to your computer and check <code>adb devices</code> in the terminal. The phone should be registered as attached. If the device doesn't show you may want to try a different port or cable. Then enter <code>adb shell</code> followed by <code>su</code> to gain root access. At this point you can erase the eMMC installation:

<code>cat /dev/zero > /dev/block/mmcblk1</code>

The phone will freeze and then the screen will go blank. Let it sit for no less than 10 minutes and then power it off by holding down the power button. You’ll know the phone is powered down when the notification LED turns off.

=== Method 2: Via serial cable ===

Another method of erasing the image is to connect serial console, break into U-Boot when it says to press Ctrl-C, and then the "mmc erase" command can be used to zero blocks on the eMMC. For example, "mmc erase 0 16384" will zero the first 8MB, and is enough to stop it from being bootable. The baud rate for the serial console is 1500000.

== Flashing Linux ==
You will want to do all your testing and development on a SD card; you DO NOT want to flash an OS to eMMC at this time. Builds frequently break at this early development stage and recovering from a corrupted eMMC installation is presently time consuming and tedious. A fast 16-64GB micro SD card for $15 will work just fine.

There are a handful of OS builds available for the PinePhone Pro already. These can be found under the [https://wiki.pine64.org/wiki/PinePhone_Pro#Software_releases Software Releases] Wiki section.

If you are a developer porting your own distribution to the PinePhone Pro, please make sure to make an entry for it in the Software Releases section on the Wiki. If you want / need help with entering your build onto the Wiki please ping one of the mods or admins in the chats (see Forums and Chats drop-down menu).

= Resources =
Aside from the PINE64 Wiki there are also other useful resources scattered across different Wikis, repositories and blogs. In time these will be gathered into one place - the [https://gitlab.com/mobian1/devices/eg25-manager/-/merge_requests/41#note_744117720 DevZone] - which will help to streamline the development process.

At the time of publishing, these are some of the notable resource, listed in no particular order:

* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) postmarketOS Wiki]
* [https://xnux.eu/log/ Megi’s (b)log]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/ DanctNIX repository]
* [https://github.com/manjaro-pinephone Manjaro repository]

= Development and discussion =
You will run into issues, there’s just no way around it, and doing it ‘on your own’ isn’t really a viable option since you’re one of the first people to hold a PinePhone Pro. The development process on a device such as this is a collaborative process, and I therefore encourage you to participate in the community. There are many ways to interact with other developers, including [https://matrix.to/#/!LZirCxnkkeBudrQzPj:matrix.org?via=matrix.org Matrix], [https://t.me/pinephone Telegram], [https://discord.gg/pine64 Discord] and [https://www.pine64.org/web-irc/ IRC].

There is also a lesser known chat for developers only. Lesser known doesn’t mean top secret, but I will not be posting a link to it here to keep the number of non-dev participants to a minimum. If you join one of the general chats and let others know you received a dev phone, then I’m sure someone will point you in the right direction.

[[Category:PinePhone Pro]]

PinePhone Pro Software Releases

2021-12-14T16:23:52Z

Thomzane: Copy image and description from https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian

This page contains a list of all available releases and tools for the [[PinePhone Pro]].

== Software releases ==

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

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, sxmo or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch/ dreemurrs-embedded/Pine64-Arch]

==== Download ====

Get both stable and test builds at [https://github.com/dreemurrs-embedded/Pine64-Arch/releases GitHub releases].

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

----

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

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

==== Download ====

* Phosh: [https://github.com/manjaro-pinephone/phosh-dev/releases Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile-dev/releases Dev]

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

----

=== Mobian ===
[[File:Debian-logo.png|right|100px]]

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

==== Download ====

[https://images.mobian-project.org/pinephonepro/ Images]

==== Notes ====
WIP. See [https://gitlab.com/mobian1/devices/pinephonepro-support pinephonepro-support].

----

=== NixOS ===
[[File:nixos.png|right|100px]]

NixOS is a Linux distribution built on top of the Nix package manager using declarative configuration to allow reliable system upgrades.
==== Download ====

==== Notes ====
WIP. See https://github.com/NixOS/mobile-nixos/issues/440

----

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

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

==== Download ====
Official images for the PinePhone Pro will be available once it is in the "community" category of devices. Until then, build your own image with pmbootstrap.

See the [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) pine64-pinephonepro] page of the postmarketOS wiki for details.



== Tools ==

== Factory releases ==

PinePhone Pro Software Releases

2021-12-14T15:47:43Z

Thomzane: Fix link

This page contains a list of all available releases and tools for the [[PinePhone Pro]].

== Software releases ==

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

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, sxmo or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch/ dreemurrs-embedded/Pine64-Arch]

==== Download ====

Get both stable and test builds at [https://github.com/dreemurrs-embedded/Pine64-Arch/releases GitHub releases].

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

----

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

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

==== Download ====

* Phosh: [https://github.com/manjaro-pinephone/phosh-dev/releases Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile-dev/releases Dev]

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

----

=== Mobian ===

==== Download ====

[https://images.mobian-project.org/pinephonepro/ Images]

==== Notes ====
WIP. See [https://gitlab.com/mobian1/devices/pinephonepro-support pinephonepro-support].

----

=== NixOS ===
[[File:nixos.png|right|100px]]

NixOS is a Linux distribution built on top of the Nix package manager using declarative configuration to allow reliable system upgrades.
==== Download ====

==== Notes ====
WIP. See https://github.com/NixOS/mobile-nixos/issues/440

----

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

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

==== Download ====
Official images for the PinePhone Pro will be available once it is in the "community" category of devices. Until then, build your own image with pmbootstrap.

See the [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) pine64-pinephonepro] page of the postmarketOS wiki for details.



== Tools ==

== Factory releases ==

PinePhone Pro Software Releases

2021-12-14T15:47:15Z

Thomzane: Move mobain to alphabetical

This page contains a list of all available releases and tools for the [[PinePhone Pro]].

== Software releases ==

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

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, sxmo or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch/ dreemurrs-embedded/Pine64-Arch]

==== Download ====

Get both stable and test builds at [https://github.com/dreemurrs-embedded/Pine64-Arch/releases GitHub releases].

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

----

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

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

==== Download ====

* Phosh: [https://github.com/manjaro-pinephone/phosh-dev/releases Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile-dev/releases Dev]

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

----

=== Mobian ===

==== Download ====

[Images](https://images.mobian-project.org/pinephonepro/)

==== Notes ====
WIP. See [https://gitlab.com/mobian1/devices/pinephonepro-support pinephonepro-support].

----

=== NixOS ===
[[File:nixos.png|right|100px]]

NixOS is a Linux distribution built on top of the Nix package manager using declarative configuration to allow reliable system upgrades.
==== Download ====

==== Notes ====
WIP. See https://github.com/NixOS/mobile-nixos/issues/440

----

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

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

==== Download ====
Official images for the PinePhone Pro will be available once it is in the "community" category of devices. Until then, build your own image with pmbootstrap.

See the [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) pine64-pinephonepro] page of the postmarketOS wiki for details.



== Tools ==

== Factory releases ==

PinePhone Pro Software Releases

2021-12-14T15:45:43Z

Thomzane: Add Mobian

This page contains a list of all available releases and tools for the [[PinePhone Pro]].

== Software releases ==

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

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, sxmo or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch/ dreemurrs-embedded/Pine64-Arch]

==== Download ====

Get both stable and test builds at [https://github.com/dreemurrs-embedded/Pine64-Arch/releases GitHub releases].

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

----

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

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

==== Download ====

* Phosh: [https://github.com/manjaro-pinephone/phosh-dev/releases Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile-dev/releases Dev]

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

----

=== NixOS ===
[[File:nixos.png|right|100px]]

NixOS is a Linux distribution built on top of the Nix package manager using declarative configuration to allow reliable system upgrades.
==== Download ====

==== Notes ====
WIP. See https://github.com/NixOS/mobile-nixos/issues/440

----

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

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

==== Download ====
Official images for the PinePhone Pro will be available once it is in the "community" category of devices. Until then, build your own image with pmbootstrap.

See the [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) pine64-pinephonepro] page of the postmarketOS wiki for details.



=== Mobian ===

==== Download ====

[Images](https://images.mobian-project.org/pinephonepro/)

==== Notes ====
WIP. See [https://gitlab.com/mobian1/devices/pinephonepro-support pinephonepro-support].

== Tools ==

== Factory releases ==

PinePhone Pro Developer Edition

2021-12-14T15:28:02Z

Thomzane: Add IRC link

= Introduction =
The Developer Edition was the first edition of the PinePhone Pro, shipped to developers in December 2021. The aim of the the Developer Edition was to give development community access to the hardware prior to end-users, boost development efforts and allow for porting of existing mobile Linux operating systems to the new hardware.
It featured the same mainboard revision as the Explorer Edition that followed in early 2022, and came in a box that was labelled "Explorer Edition".

= Getting started =
This post is aimed strictly at developers receiving their PinePhone Pro dev units. Please note that the following instructions do not apply to Explorer Edition or other future editions of the PinePhone Pro - everything below is only pertinent to the dev phones.

Consider this a crash course rather than a comprehensive overview; you are also welcome to participate in documenting the process (and everything else related to the PinePhone Pro) on the Wiki. You can either create a Wiki account or use your [forum.pine64.org PINE64 forum] credentials to log in.

== Getting the hardware ready ==
After unpacking the PinePhone Pro from its box, detach the back cover (looking at the back of the phone, there is a fingernail notch on the left leading edge) and remove the plastic tab between the battery and mainboard. You can also flip the headphone jack privacy switch at this point - this enables UART output via the headphone jack. Serial console works the [https://wiki.pine64.org/wiki/PinePhone#Serial_console same way as on the original PinePhone.]

= Factory hardware test image =

The PinePhone Pro developer edition ships with a BSP AOSP factory image flashed to the eMMC. This image includes a number of factory applications meant to validate operation of the sensors, the modem, cameras, LCD & touch panel, etc. You’ll have to nuke the AOSP build to run a Linux installation on the PinePhone Pro. Booting from SD with the AOSP factory build present on eMMC is not possible due to the SoCs native boot order.

== Changing the language of factory AOSP ==

This is optional and only if you want to test out the AOSP test image.

# Swipe up from the bottom of the screen.
# Tap on the Gear icon.
# Tap on the bottom option that has an i icon on the left.
# Tap on the first choice with the language icon.
# Tap on the second choice to add another language.
# Tap on your language in the list.
# If there is a secondary choice required, tap on the preferred country.
# Tap the sandwich icon to the right of the new second language and drag to the top of the list to set the new language as the default.

== Backing up the factory AOSP ==

It may be a good idea to create an image of the eMMC in case you want to flash it back.

<code>adb root && adb pull /dev/block/mmcblk0 ~/pinephonepro-factory-AOSP.img</code>

== Nuking the factory AOSP installation ==

To be able to boot from the microSD card easily it is recommend to wipe the bootloader from the pre-installed operating system on the eMMC due to the eMMC being higher in the boot priority than the microSD card.

=== Method 1: Via ADB ===
In the factory test image, navigate to setting (gear icon) > at the very bottom of the settings list you will find a phone icon with rk3999mid written underneath it > tap the last (bottom) setting 7 times in quick succession. Following this, you *may* need to do the following: open the Settings application and enable USB debugging in Settings > System > Developer Options > USB debugging. Then connect the PinePhone Pro to your PC with the supplied USB-C cable.

Please note: It is recommended to charge the device to at least 50% before proceeding with wiping the eMMC.

{{Hint|Note: You may have gotten a Chinese factory image; in the settings menu you can change the language to English by selecting the gray info icon (系统, one from bottom), then the first option (语言..), and again the first option (also 语言), then press +, English and drag it to the top of the list).}}

Connect the phone to your computer and check <code>adb devices</code> in the terminal. The phone should be registered as attached. If the device doesn't show you may want to try a different port or cable. Then enter <code>adb shell</code> followed by <code>su</code> to gain root access. At this point you can erase the eMMC installation:

<code>cat /dev/zero > /dev/block/mmcblk1</code>

The phone will freeze and then the screen will go blank. Let it sit for no less than 10 minutes and then power it off by holding down the power button. You’ll know the phone is powered down when the notification LED turns off.

=== Method 2: Via serial cable ===

Another method of erasing the image is to connect serial console, break into U-Boot when it says to press Ctrl-C, and then the "mmc erase" command can be used to zero blocks on the eMMC. For example, "mmc erase 0 16384" will zero the first 8MB, and is enough to stop it from being bootable. The baud rate for the serial console is 1500000.

== Flashing Linux ==
You will want to do all your testing and development on a SD card; you DO NOT want to flash an OS to eMMC at this time. Builds frequently break at this early development stage and recovering from a corrupted eMMC installation is presently time consuming and tedious. A fast 16-64GB micro SD card for $15 will work just fine.

There are a handful of OS builds available for the PinePhone Pro already. These can be found under the [https://wiki.pine64.org/wiki/PinePhone_Pro#Software_releases Software Releases] Wiki section.

If you are a developer porting your own distribution to the PinePhone Pro, please make sure to make an entry for it in the Software Releases section on the Wiki. If you want / need help with entering your build onto the Wiki please ping one of the mods or admins in the chats (see Forums and Chats drop-down menu).

= Resources =
Aside from the PINE64 Wiki there are also other useful resources scattered across different Wikis, repositories and blogs. In time these will be gathered into one place - the [https://gitlab.com/mobian1/devices/eg25-manager/-/merge_requests/41#note_744117720 DevZone] - which will help to streamline the development process.

At the time of publishing, these are some of the notable resource, listed in no particular order:

* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) postmarketOS Wiki]
* [https://xnux.eu/log/ Megi’s (b)log]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/ DanctNIX repository]
* [https://github.com/manjaro-pinephone Manjaro repository]

= Development and discussion =
You will run into issues, there’s just no way around it, and doing it ‘on your own’ isn’t really a viable option since you’re one of the first people to hold a PinePhone Pro. The development process on a device such as this is a collaborative process, and I therefore encourage you to participate in the community. There are many ways to interact with other developers, including [https://matrix.to/#/!LZirCxnkkeBudrQzPj:matrix.org?via=matrix.org Matrix], [https://t.me/pinephone Telegram], [https://discord.gg/pine64 Discord] and [https://www.pine64.org/web-irc/ IRC].

There is also a lesser known chat for developers only. Lesser known doesn’t mean top secret, but I will not be posting a link to it here to keep the number of non-dev participants to a minimum. If you join one of the general chats and let others know you received a dev phone, then I’m sure someone will point you in the right direction.

[[Category:PinePhone Pro]]

PinePhone Pro Developer Edition

2021-12-14T15:25:37Z

Thomzane: Specify sandwich icon

= Introduction =
The Developer Edition was the first edition of the PinePhone Pro, shipped to developers in December 2021. The aim of the the Developer Edition was to give development community access to the hardware prior to end-users, boost development efforts and allow for porting of existing mobile Linux operating systems to the new hardware.
It featured the same mainboard revision as the Explorer Edition that followed in early 2022, and came in a box that was labelled "Explorer Edition".

= Getting started =
This post is aimed strictly at developers receiving their PinePhone Pro dev units. Please note that the following instructions do not apply to Explorer Edition or other future editions of the PinePhone Pro - everything below is only pertinent to the dev phones.

Consider this a crash course rather than a comprehensive overview; you are also welcome to participate in documenting the process (and everything else related to the PinePhone Pro) on the Wiki. You can either create a Wiki account or use your [forum.pine64.org PINE64 forum] credentials to log in.

== Getting the hardware ready ==
After unpacking the PinePhone Pro from its box, detach the back cover (looking at the back of the phone, there is a fingernail notch on the left leading edge) and remove the plastic tab between the battery and mainboard. You can also flip the headphone jack privacy switch at this point - this enables UART output via the headphone jack. Serial console works the [https://wiki.pine64.org/wiki/PinePhone#Serial_console same way as on the original PinePhone.]

= Factory hardware test image =

The PinePhone Pro developer edition ships with a BSP AOSP factory image flashed to the eMMC. This image includes a number of factory applications meant to validate operation of the sensors, the modem, cameras, LCD & touch panel, etc. You’ll have to nuke the AOSP build to run a Linux installation on the PinePhone Pro. Booting from SD with the AOSP factory build present on eMMC is not possible due to the SoCs native boot order.

== Changing the language of factory AOSP ==

This is optional and only if you want to test out the AOSP test image.

# Swipe up from the bottom of the screen.
# Tap on the Gear icon.
# Tap on the bottom option that has an i icon on the left.
# Tap on the first choice with the language icon.
# Tap on the second choice to add another language.
# Tap on your language in the list.
# If there is a secondary choice required, tap on the preferred country.
# Tap the sandwich icon to the right of the new second language and drag to the top of the list to set the new language as the default.

== Backing up the factory AOSP ==

It may be a good idea to create an image of the eMMC in case you want to flash it back.

<code>adb root && adb pull /dev/block/mmcblk0 ~/pinephonepro-factory-AOSP.img</code>

== Nuking the factory AOSP installation ==

To be able to boot from the microSD card easily it is recommend to wipe the bootloader from the pre-installed operating system on the eMMC due to the eMMC being higher in the boot priority than the microSD card.

=== Method 1: Via ADB ===
In the factory test image, navigate to setting (gear icon) > at the very bottom of the settings list you will find a phone icon with rk3999mid written underneath it > tap the last (bottom) setting 7 times in quick succession. Following this, you *may* need to do the following: open the Settings application and enable USB debugging in Settings > System > Developer Options > USB debugging. Then connect the PinePhone Pro to your PC with the supplied USB-C cable.

Please note: It is recommended to charge the device to at least 50% before proceeding with wiping the eMMC.

{{Hint|Note: You may have gotten a Chinese factory image; in the settings menu you can change the language to English by selecting the gray info icon (系统, one from bottom), then the first option (语言..), and again the first option (also 语言), then press +, English and drag it to the top of the list).}}

Connect the phone to your computer and check <code>adb devices</code> in the terminal. The phone should be registered as attached. If the device doesn't show you may want to try a different port or cable. Then enter <code>adb shell</code> followed by <code>su</code> to gain root access. At this point you can erase the eMMC installation:

<code>cat /dev/zero > /dev/block/mmcblk1</code>

The phone will freeze and then the screen will go blank. Let it sit for no less than 10 minutes and then power it off by holding down the power button. You’ll know the phone is powered down when the notification LED turns off.

=== Method 2: Via serial cable ===

Another method of erasing the image is to connect serial console, break into U-Boot when it says to press Ctrl-C, and then the "mmc erase" command can be used to zero blocks on the eMMC. For example, "mmc erase 0 16384" will zero the first 8MB, and is enough to stop it from being bootable. The baud rate for the serial console is 1500000.

== Flashing Linux ==
You will want to do all your testing and development on a SD card; you DO NOT want to flash an OS to eMMC at this time. Builds frequently break at this early development stage and recovering from a corrupted eMMC installation is presently time consuming and tedious. A fast 16-64GB micro SD card for $15 will work just fine.

There are a handful of OS builds available for the PinePhone Pro already. These can be found under the [https://wiki.pine64.org/wiki/PinePhone_Pro#Software_releases Software Releases] Wiki section.

If you are a developer porting your own distribution to the PinePhone Pro, please make sure to make an entry for it in the Software Releases section on the Wiki. If you want / need help with entering your build onto the Wiki please ping one of the mods or admins in the chats (see Forums and Chats drop-down menu).

= Resources =
Aside from the PINE64 Wiki there are also other useful resources scattered across different Wikis, repositories and blogs. In time these will be gathered into one place - the [https://gitlab.com/mobian1/devices/eg25-manager/-/merge_requests/41#note_744117720 DevZone] - which will help to streamline the development process.

At the time of publishing, these are some of the notable resource, listed in no particular order:

* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) postmarketOS Wiki]
* [https://xnux.eu/log/ Megi’s (b)log]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/ DanctNIX repository]
* [https://github.com/manjaro-pinephone Manjaro repository]

= Development and discussion =
You will run into issues, there’s just no way around it, and doing it ‘on your own’ isn’t really a viable option since you’re one of the first people to hold a PinePhone Pro. The development process on a device such as this is a collaborative process, and I therefore encourage you to participate in the community. There are many ways to interact with other developers, including [https://matrix.to/#/!LZirCxnkkeBudrQzPj:matrix.org?via=matrix.org Matrix], [https://t.me/pinephone Telegram], [https://discord.gg/pine64 Discord] and IRC.

There is also a lesser known chat for developers only. Lesser known doesn’t mean top secret, but I will not be posting a link to it here to keep the number of non-dev participants to a minimum. If you join one of the general chats and let others know you received a dev phone, then I’m sure someone will point you in the right direction.

[[Category:PinePhone Pro]]

PinePhone Pro Developer Edition

2021-12-14T15:24:08Z

Thomzane: Add AOSP language instructions

= Introduction =
The Developer Edition was the first edition of the PinePhone Pro, shipped to developers in December 2021. The aim of the the Developer Edition was to give development community access to the hardware prior to end-users, boost development efforts and allow for porting of existing mobile Linux operating systems to the new hardware.
It featured the same mainboard revision as the Explorer Edition that followed in early 2022, and came in a box that was labelled "Explorer Edition".

= Getting started =
This post is aimed strictly at developers receiving their PinePhone Pro dev units. Please note that the following instructions do not apply to Explorer Edition or other future editions of the PinePhone Pro - everything below is only pertinent to the dev phones.

Consider this a crash course rather than a comprehensive overview; you are also welcome to participate in documenting the process (and everything else related to the PinePhone Pro) on the Wiki. You can either create a Wiki account or use your [forum.pine64.org PINE64 forum] credentials to log in.

== Getting the hardware ready ==
After unpacking the PinePhone Pro from its box, detach the back cover (looking at the back of the phone, there is a fingernail notch on the left leading edge) and remove the plastic tab between the battery and mainboard. You can also flip the headphone jack privacy switch at this point - this enables UART output via the headphone jack. Serial console works the [https://wiki.pine64.org/wiki/PinePhone#Serial_console same way as on the original PinePhone.]

= Factory hardware test image =

The PinePhone Pro developer edition ships with a BSP AOSP factory image flashed to the eMMC. This image includes a number of factory applications meant to validate operation of the sensors, the modem, cameras, LCD & touch panel, etc. You’ll have to nuke the AOSP build to run a Linux installation on the PinePhone Pro. Booting from SD with the AOSP factory build present on eMMC is not possible due to the SoCs native boot order.

== Changing the language of factory AOSP ==

This is optional and only if you want to test out the AOSP test image.

# Swipe up from the bottom of the screen.
# Tap on the Gear icon.
# Tap on the bottom option that has an i icon on the left.
# Tap on the first choice with the language icon.
# Tap on the second choice to add another language.
# Tap on your language in the list.
# If there is a secondary choice required, tap on the preferred country.
# Tap and drag the new second language to the top of the list to set it as the default.

== Backing up the factory AOSP ==

It may be a good idea to create an image of the eMMC in case you want to flash it back.

<code>adb root && adb pull /dev/block/mmcblk0 ~/pinephonepro-factory-AOSP.img</code>

== Nuking the factory AOSP installation ==

To be able to boot from the microSD card easily it is recommend to wipe the bootloader from the pre-installed operating system on the eMMC due to the eMMC being higher in the boot priority than the microSD card.

=== Method 1: Via ADB ===
In the factory test image, navigate to setting (gear icon) > at the very bottom of the settings list you will find a phone icon with rk3999mid written underneath it > tap the last (bottom) setting 7 times in quick succession. Following this, you *may* need to do the following: open the Settings application and enable USB debugging in Settings > System > Developer Options > USB debugging. Then connect the PinePhone Pro to your PC with the supplied USB-C cable.

Please note: It is recommended to charge the device to at least 50% before proceeding with wiping the eMMC.

{{Hint|Note: You may have gotten a Chinese factory image; in the settings menu you can change the language to English by selecting the gray info icon (系统, one from bottom), then the first option (语言..), and again the first option (also 语言), then press +, English and drag it to the top of the list).}}

Connect the phone to your computer and check <code>adb devices</code> in the terminal. The phone should be registered as attached. If the device doesn't show you may want to try a different port or cable. Then enter <code>adb shell</code> followed by <code>su</code> to gain root access. At this point you can erase the eMMC installation:

<code>cat /dev/zero > /dev/block/mmcblk1</code>

The phone will freeze and then the screen will go blank. Let it sit for no less than 10 minutes and then power it off by holding down the power button. You’ll know the phone is powered down when the notification LED turns off.

=== Method 2: Via serial cable ===

Another method of erasing the image is to connect serial console, break into U-Boot when it says to press Ctrl-C, and then the "mmc erase" command can be used to zero blocks on the eMMC. For example, "mmc erase 0 16384" will zero the first 8MB, and is enough to stop it from being bootable. The baud rate for the serial console is 1500000.

== Flashing Linux ==
You will want to do all your testing and development on a SD card; you DO NOT want to flash an OS to eMMC at this time. Builds frequently break at this early development stage and recovering from a corrupted eMMC installation is presently time consuming and tedious. A fast 16-64GB micro SD card for $15 will work just fine.

There are a handful of OS builds available for the PinePhone Pro already. These can be found under the [https://wiki.pine64.org/wiki/PinePhone_Pro#Software_releases Software Releases] Wiki section.

If you are a developer porting your own distribution to the PinePhone Pro, please make sure to make an entry for it in the Software Releases section on the Wiki. If you want / need help with entering your build onto the Wiki please ping one of the mods or admins in the chats (see Forums and Chats drop-down menu).

= Resources =
Aside from the PINE64 Wiki there are also other useful resources scattered across different Wikis, repositories and blogs. In time these will be gathered into one place - the [https://gitlab.com/mobian1/devices/eg25-manager/-/merge_requests/41#note_744117720 DevZone] - which will help to streamline the development process.

At the time of publishing, these are some of the notable resource, listed in no particular order:

* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) postmarketOS Wiki]
* [https://xnux.eu/log/ Megi’s (b)log]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/ DanctNIX repository]
* [https://github.com/manjaro-pinephone Manjaro repository]

= Development and discussion =
You will run into issues, there’s just no way around it, and doing it ‘on your own’ isn’t really a viable option since you’re one of the first people to hold a PinePhone Pro. The development process on a device such as this is a collaborative process, and I therefore encourage you to participate in the community. There are many ways to interact with other developers, including [https://matrix.to/#/!LZirCxnkkeBudrQzPj:matrix.org?via=matrix.org Matrix], [https://t.me/pinephone Telegram], [https://discord.gg/pine64 Discord] and IRC.

There is also a lesser known chat for developers only. Lesser known doesn’t mean top secret, but I will not be posting a link to it here to keep the number of non-dev participants to a minimum. If you join one of the general chats and let others know you received a dev phone, then I’m sure someone will point you in the right direction.

[[Category:PinePhone Pro]]

PinePhone Pro

2021-12-14T15:09:46Z

Thomzane: Link to new page for Explorer Edition

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

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

== Introduction ==

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

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

=== State of the software ===

Presently, at the time of writing (late 2021), the PinePhone Pro is aimed solely at early adopters and developers. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile Linux, in more general, to reach a higher degree of maturity.

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

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

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

* [https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition Developer Edition]
* [https://wiki.pine64.org/wiki/PinePhone_Pro_Explorer_Edition Explorer Edition]

=== Help and support ===

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

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

{{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 mainboard contacts using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge until it is removed and some of the device’s functionality may not function properly.

The PinePhone Pro's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Notice: Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins. An adapter from a nano to a micro SIM is included in the box.

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>

== Software ==

At the time of the release, in late 2021, the PinePhone Pro is in an early development stage. That said, the device has benefited greatly from work done on the original PinePhone, which means that even early development images feature all core functionality, such as: functional UI, sensors and even the modem (to a degree).

The development is expected to proceed very quickly compared to progress done on the original PinePhone as much of the fundamental work can carry over to the new device.
You can follow development efforts on [https://xnux.eu/log/ Megi's blog], the dedicated [[PinePhone Pro Development]] section as well as on individual project’s Wiki’s and repositories.

=== Boot order ===

On the PinePhone Pro the eMMC (the internal storage of the phone) has a higher boot priority than the microSD card (see [[RK3399 boot sequence#Boot sequence details]] for details regarding the boot sequence). That behavior is in contrast to the original PinePhone with the Allwinner A64 SoC, where the microSD card has a higher boot priority.

What this means: For the PinePhone Pro this means, that inserting a flashed microSD card to boot a new installation is not sufficient to boot a microSD card if there is already a valid installation of a bootloader on the eMMC present. The boot order behavior can be altered non-permanently by various way, for example by either not having a bootloader installed to the eMMC or by pointing the bootloader installed on the eMMC to the installation on the microSD card.

=== Installation instructions ===

Due to the above explained [[PinePhone Pro#Boot order|boot order]] of the PinePhone Pro, the eMMC has a higher boot priority than the microSD card and the user has to consider this behavior. This means that you cannot boot from a SD card with an OS present on the device's eMMC.

{{Template:note|If you ordered a '''PinePhone Pro Developer Edition''' intended for developing and coming with an Android factory OS preinstalled, please see [[PinePhone Pro Developer Edition#Nuking the factory AOSP installation]] to learn how to remove the bootloader and the preinstalled OS of the eMMC, to be able to boot and test operating systems from the microSD card easily.
}}

That said, booting from SD can be achieved using a modified u-boot (or a different bootloader) on eMMC, which seeks out a bootable partition on SD first. At the time of writing, this hasn’t been achieved yet but is a planned feature.

It is strongly recommended you perform all testing from a SD card, leaving the eMMC vacant.

=== Software releases ===

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

== Specifications ==

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

== Privacy switch 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
! Description
|-
| 1
| Modem
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART mode.
|}

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
|
|-
| Rear camera
|
|-
| Camera flash
|
|-
| Front camera
|
|-
| LCD
|
|-
| WiFi
|
|-
| Bluetooth
|
|-
| 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
|
|-
| Ambient light / Proximity
|
|-
| Accelerometer / Gyroscope
|
|-
| Vibration motor
|
|-
| Notification LED
|
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
|
|-
| Battery fuel gauge
|
|}

== Datasheets, schematics and certifications ==

== Press ==

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

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

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

PineTime

2021-04-21T01:20:32Z

Thomzane: Fix thingiverse typo and add designers

== Frequently asked questions ==

'''Read these first!'''

* [[PineTime FAQ| Frequently Asked Questions about the devkit]]
* [[Reprogramming the PineTime|Reprogramming the PineTime (development kit)]]

== Default OS ==

The current default operating system on the PineTime is called [[InfiniTime]], you can find more information about the firmware on its GitHub page. First devkits shipped with a proprietary custom firmware.

You can find a list of available firmware and other software here: [[PineTime Development]]

== Short overview ==
'''Dimensions:''' 37.5 x 40 x 11mm 
'''Weight:''' 38 grams 
'''IP Rating:''' IP67 (waterproof to 1 meter (sealed edition!)) 
'''Display:'''
: '''Size:''' 1.3 inches (33mm) diagonal
: '''Type:''' IPS capacitive touchscreen, RGB 65K colors
: '''Display Controller:''' ST7789
: '''Resolution:''' 240x240 pixels 
'''System on Chip:''' Nordic Semiconductor nRF52832 
'''Flash:''' 512KB with additional 4MB SPI NOR 
'''RAM:''' 64KB 
'''Bluetooth:''' [[PineTime_Bluetooth|5.0 (including Bluetooth Low Energy)]] 
'''Sensors:''' Accelerometer, Heart rate sensor 
'''Feedback:''' Vibration motor 
'''Battery:''' 170-180mAh LiPo

= Community =

== Forum ==
* [https://forum.pine64.org/forumdisplay.php?fid=134 PineTime forum]

== Chat ==
* [https://app.element.io/#/room/#pinetime:matrix.org Matrix Channel] (No login required to read)
* IRC Server: [ircs://irc.pine64.org#pinetime irc.pine64.org] Channel: PineTime
* [https://t.me/pinetime Telegram group]
* [https://discordapp.com/invite/DgB7kzr Discord server invite link]

=== Developers and coding ===
* [https://app.element.io/#/room/#pinetime-dev:matrix.org Matrix Channel] (No login required to read)
* [https://t.me/pinetime_dev Telegram group]
* [https://discordapp.com/invite/DgB7kzr Discord server invite link]

== Development efforts ==

To read more about development on the PineTime, the projects available and more technical details, check out [[PineTime Development]]

== Useful articles and blog posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://www.ncartron.org/one-week-with-my-pinetime---a-feedback.html Using the PineTime in production (January 2021)]

* [https://medium.com/swlh/sneak-peek-of-pinetime-smart-watch-and-why-its-perfect-for-teaching-iot-81b74161c159 Sneak Peek of PineTime Smart Watch… And why it’s perfect for teaching IoT]

* [https://medium.com/@ly.lee/building-a-rust-driver-for-pinetimes-touch-controller-cbc1a5d5d3e9 Building a Rust Driver for PineTime’s Touch Controller]

* [https://medium.com/@ly.lee/porting-druid-rust-widgets-to-pinetime-smart-watch-7e1d5a5d977a Porting (druid) Rust Widgets to PineTime Smart Watch]

* [https://medium.com/@ly.lee/optimising-pinetimes-display-driver-with-rust-and-mynewt-3ba269ea2f5c Optimising PineTime’s Display Driver with Rust and Mynewt]

* [https://electronut.in/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/ Getting Started with Zephyr RTOS on Nordic nRF52832 hackaBLE]

* [https://blog.aegrel.ee/absniffer-cmsis-dap-sniffer.html Removing the lock and installing another firmware on the nRF52832 using CMSIS-DAP dongle on Linux]

* [https://github.com/JF002/nrf52-baseproject/wiki/Build,-program-and-debug-NRF52-project-with-JLink,-CMake-and-CLion Build, program and debug NRF52 project with JLink, CMake and CLion]

* [https://www.nrbtech.io/blog/2020/1/4/using-clion-for-nordic-nrf52-projects Using CLion for Nordic nRF52 projects]

* [https://dev.to/aaronc81/flashing-your-pinetime-using-an-st-link-and-openocd-54dd Flashing your PineTime using an ST-Link and OpenOCD]

* [https://zephyrlabs.github.io/Watchfaces/ Zephyrlabs: just a bunch of watchfaces made for the pinetime]

*[https://pankajraghav.com/2021/04/03/PINETIME-STOPCLOCK.html Creating a stopwatch in Pinetime (with Infinitime)]

== Hardware ==

=== Display ===

Note: The factory-default software on the PineTime does not auto-detect the display being disconnected when it has already booted. That can cause garbled output, to fix it just restart the PineTime.

The display is driven using the ST7789 display controller. Use the following pins to drive the screen:

{| class="wikitable"
|-
! PineTime pin
! ST7789 pin
|-
| LCD_SCK (P0.02)
| SPI clock
|-
| LCD_SDI (P0.03)
| SPI MOSI
|-
| LCD_RS (P0.18)
| Command/Data pin (CD)
|-
| LCD_CS (P0.25)
| Chip select
|-
| LCD_RESET (P0.26)
| Display reset
|-
| LCD_BACKLIGHT_{LOW,MID,HIGH}
| Backlight (active low)
|}

Notes:

* Chip select must be held low while driving the display. It must be high when using other SPI devices on the same bus (such as external flash storage) so that the display controller won't respond to the wrong commands.
* SPI must be used in mode 3. Mode 0 (the default) won't work.
* LCD_DISPLAY_* is used to enable the backlight. Set at least one to low to see anything on the screen.
* Use SPI at 8MHz (the fastest clock available on the nRF52832) because otherwise refreshing will be super slow.

'''References''':

[https://github.com/adafruit/Adafruit-ST7735-Library/ Adafruit ST7789 driver in cpp]

=== Battery measurement ===

Reading whether the PineTime has power attached is easy: simply read the charge indication pin (P0.12). When it is high it is running on battery, when it is low it is charging.

Reading the battery voltage is a bit harder. For that you can use the battery voltage pin on P0.31 (AIN7). The returned value is 12 bits, which means it is 0..4095. You can get the measured voltage with the following formula, assuming a reference voltage of 3.3V (this is configurable in the ADC):

adcVoltage = adcValue / (4095 / 3.3)

The measured voltage is actually half of the actual battery voltage, because the ADC is connected between a voltage divider where both resistors are 1MΩ. This can be corrected by multiplying the value:

batteryVoltage = adcValue * 2 / (4095 / 3.3)

It's often better to avoid floating point values on embedded systems and in this case there is no reason to use float at all, we can just represent the value in millivolts. Therefore the formula can be simplified to:

batteryVoltage = adcValue * 2000 / (4095 / 3.3)
batteryVoltage = adcValue * 2000 / 1241

Converting this voltage to an estimated capacity in percent requires a more complicated algorithm, because Lithium-ion batteries have a non-linear discharge curve.

=== Button ===

The button on the side of the PineTime is disabled by default. To enable it, drive the button out pin (P0.15) high.

While enabled, the button in pin (P0.13) will be high when the button is pressed, and low when it is not pressed.

=== Touch panel ===

The touch panel is controlled by a Hynitron CST816S chips. Unfortunately, there is not much information about this chip on the internet apart from the datasheet below and a [https://github.com/lupyuen/hynitron_i2c_cst0xxse/ reference driver]. This is enough to implement a basic driver, but crucial information needed to implement advanced functionalities are missing (I²C protocol and registers, timings, power modes,...).

==== Pins ====

* P0.10 : Reset
* P0.28 : Interrupt (signal to the CPU when a touch event is detected)
* P0.06 : I²C SDA
* P0.07 : I²C SCL

==== I²C ====

* Device address : 0x15
* Frequency : from 10Khz to 400Khz

'''NOTE : ''' The controller go to sleep when no event is detected. In sleep mode, the controller does not communicate on the I²C bus (it appears disconnected). So, for the communication to work, you need to tap on the screen so that the chip wakes-up.

==== Touch events ====

Touch information is available from the 63 first registers of the controller. Remember: the device is in sleep mode when no touch event is detected. It means that you can read the register only when the touch controller detected an event. You can use the ''Interrupt'' pin to detect such event in the software.

These 63 bytes contain up to 10 touch point (X, Y, event type, pressure,...) :

{| class="wikitable"
! Byte
! Bit7
! Bit6
! Bit5
! Bit4
! Bit3
! Bit2
! Bit1
! Bit0
|-
|0
|colspan="8"|?
|-
|1
|colspan="8"|GestureID : (Gesture code ,

0x00: no gesture,

0x01: Slide down,

0x02: Slide up,

0x03: Slide left,

0x04: Slide right,

0x05: Single click,

0x0B: Double click,

0x0C: Long press)
|-
|2
|colspan="4"|?
|colspan="4"|Number of touch points
|-
|3
|colspan="2"|Event (0 = Down, 1 = Up, 2 = Contact)
|colspan="2"|?
|colspan="4"|X (MSB) coordinate
|-
|4
|colspan="8"|X (LSB) coordinate
|-
|5
|colspan="2"|?
|colspan="2"|Touch ID
|colspan="4"|Y (MSB) coordinate
|-
|6
|colspan="8"|Y (LSB) coordinate
|-
|7
|colspan="8"|Pressure (?)
|-
|8
|colspan="8"|Miscellaneous (?)
|}

Bytes 3 to 8 are repeated 10 times (10*6 + 3 = 63 bytes).

'''NOTES'''

* The touch controller seems to report only 1 touch point
* Fields X, Y, Number of touch points and touch ID are updated. The others are always 0.

==== Registers ====

The reference driver specifies some registers and value, but there is no information about them:

{| class="wikitable"

!Register
!Address
!Description
|-
|HYN_REG_INT_CNT
|0x8F
|
|-
|HYN_REG_FLOW_WORK_CNT
|0x91
|
|-
|HYN_REG_WORKMODE
|0x00
|0 = WORK, 0x40 = FACTORY
|-
|HYN_REG_CHIP_ID
|0xA3
|
|-
|HYN_REG_CHIP_ID2
|0x9F
|-
|HYN_REG_POWER_MODE
|0xA5
|0x03 = SLEEP (reset the touchpanel using the reset pin before using this register : pin_low, delay 5ms, pin_high, delay 50ms then write 3 to register 0xA5)
|-
|HYN_REG_FW_VER
|0xA6
|
|-
|HYN_REG_VENDOR_ID
|0xA8
|
|-
|HYN_REG_LCD_BUSY_NUM
|0xAB
|
|-
|HYN_REG_FACE_DEC_MODE_EN
|0xB0
|
|-
|HYN_REG_GLOVE_MODE_EN
|0xC0
|
|-
|HYN_REG_COVER_MODE_EN
|0xC1
|
|-
|HYN_REG_CHARGER_MODE_EN
|0x8B
|
|-
|HYN_REG_GESTURE_EN
|0xD0
|
|-
|HYN_REG_GESTURE_OUTPUT_ADDRESS
|0xD3
|
|-
|HYN_REG_ESD_SATURATE 0xED
|0xED
|
|}

'''WARNING : ''' <del>Writing the SLEEP command (write 0x05 in HYN_REG_POWER_MODE) seems to freeze the controller (it returns only static values) until the battery is totally drained and the whole system reset. Analysis and debugging is more than welcome!</del>

===Accelerometer===
The on board accelerometer is Bosch BMA421, connected to the I2C bus.

==== Pins ====

* P0.06 : I²C SDA
* P0.07 : I²C SCL
* P0.08 : Interrupt

I2C Device address : 0x18

== Datasheets and Schematics ==

=== Schematics ===
* [https://files.pine64.org/doc/PineTime/PineTime%20Schematic-V1.0a-20191103.pdf PineTime Schematic ver1.0a]
* [https://files.pine64.org/doc/PineTime/PineTime%20Port%20Assignment%20rev1.0.pdf PineTime GPIO Port Assignment ver1.0]

Note: The part number for the SPI FLASH in the schematic diagram is not correct, the PineTime features a larger external FLASH device, see below.

=== Chip Datasheets ===
* NORDIC nRF52832 information:
** [https://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf nRF52832 Product Brief]
** [https://infocenter.nordicsemi.com/pdf/nRF52832_PS_v1.1.pdf nRF52832 Product Specification v1.1]
* ARMv7-M information:
** [https://static.docs.arm.com/ddi0403/eb/DDI0403E_B_armv7m_arm.pdf ARMv7-M Architecture Reference Manual]

=== Component Datasheets ===
* PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]
** [https://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]
* SPI Flash information:
** [https://www.elnec.com/en/device/XTX/XT25F32B+%28QuadSPI%29+%5BSOP8-200%5D/ XTX XT25F32B 32Mb(4MB) SPI NOR Flash] (data sheets for this part are hard to find but it acts similar to other QuadSPI SPI NOR Flash such as [https://www.macronix.com/Lists/Datasheet/Attachments/7426/MX25L3233F,%203V,%2032Mb,%20v1.6.pdf Macronix 32Mb(4MB) SPI NOR Flash])
** [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf XTX XT25F32B]
** IDs for XT25F32B are: manufacturer (0x0b), device (0x15), memory type (0x40), density (0x16)
* LCD Panel:
** [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20LCD%20Panel.jpg 1.3" 240x240 IPS LCD Panel Specification for PineTime]
** [https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf 11.6" Sitronix LCD Driver/Controller Datasheet]
* Touchpad information:
** [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]
** [https://files.pine64.org/doc/datasheet/pinetime/CST816S数据手册V1.1.pdf 11.6" Hynitron CST816S Capacitive Touch Controller Datasheet in Chinese]
** [https://wiki.pine64.org/images/2/2f/CST816S.zip Touch Controller Datasheet en]
* Sensor:
** [https://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial VAcceleration Sensor Product Brief]
** [https://wiki.pine64.org/images/c/cc/Bst-bma400-ds000.pdf BOSCH BMA400 3-axes ultra-low power accelerometer datasheet]
** [https://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]

== Community case design ==

* [https://www.thingiverse.com/thing:4172849 PineTime Smart Watch case by dara0s at thingiverse]
* [https://www.thingiverse.com/thing:4651462 PineTime dev kit back fix by joaquimorg at thingiverse]
* [https://www.thingiverse.com/thing:4763267 PineTime dev kit charging holder v4 by zevix81 at thingiverse]

[[Category:PineTime]]

PineTab

2020-10-20T18:49:06Z

Thomzane: Add note about disabling sleep.

{{warning|1=IMPORTANT INFORMATION for '''Early Adopters''' - please [[PineTab/Early-Adopter|'''CLICK HERE''']] - some '''known issues''' are listed there}}

The PineTab is a 10" tablet created by Pine64.

== Specifications ==
* '''Dimensions:''' 11mm x 175mm x 260mm (Thickness, Width, Height)
* '''Weight:''' 575g (Tablet alone)
* '''Build:''' Plastic
* '''Storage:'''
** 64GB of internal eMMC storage
** MicroSD slot, bootable
** M.2 SSD slot, supports SATA and USB devices only, not NVME (optional)
* '''Cameras:''' 2Mpx Front, 5Mpx Rear
* '''SOC:''' Allwinner A64 Quad Core
* '''CPU:''' 4x ARM A53 1.152GHz
* '''GPU:''' Mali 400 MP2
* '''RAM:''' 2GB LPDDR3
* '''I/O:''' HD Video Out (Mini HDMI), Micro USB 2.0 OTG, USB 2.0 A host, 3.5mm Headphone/Mic combo,
* '''Network'''
** WiFi (802.11b/g/n, 2.4GHz only)
** Bluetooth 2.1
** M.2 LTE / Cell MODEM card, (optional, and takes place of optional M.2 SSD)
* '''Screen:''' 10.1" IPS 800x1280 Capacitive LCD
* '''Attachments/Accessories:''' Magnetically attached keyboard (optional)
* '''Battery:''' 6000MAh (6Ah)
* '''Misc. features:'''
** Volume rocker and home button
** Speakers and Microphone
** 2.5mm OD 0.7mm ID DC Jack Power (5V 2A) Port

== Keyboard ==
'''Overview:''' The PineTab detachable keyboard features a full function row, FN key functionality, meta key (where the Windows key would be) and all of the keys you need for daily use.

'''FN keys:''': Pause/play (F2), Stop (F3), Previous(F4), Next(F5), Music (F6), Mail (F7), Home (F8), Mute (F9), Vol- (F10), Vol+ (F11), Disable touchpad (F12), NumLock (Insert), Scroll Lock (Delete), PgUp (Up Arrow), PgDn (Down Arrow), Home (Left Arrow), End (Right Arrow), Digital Numpad (7,8,9,0,U,I,O,P,J,K,L,;,M,.,/)

==Versions==
* "pinetab-dev": development version sent to ~100 developers. This one is like the Early Adopter version, but has a different display panel.
* [[PineTab/Early-Adopter|Early Adopter]]: the first hardware revision of the PineTab, which shipped to customers.

[[File:PineTabBoard.jpeg|400px|thumb|right|The insides of the PineTab]]

== PineTab board information, schematics and certifications ==
* PineTab mainboard schematic:
** [http://files.pine64.org/doc/PineTab/PineTab%20Schematic%20v1.2-20191125.pdf PineTab mainboard Released Schematic ver 1.2]
** [http://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-top.pdf PineTab mainboard component placement ver 1.2 - Top View]
** [http://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-bottom.pdf PineTab mainboard component placement ver 1.2 - Bottom View]
* PineTab keyboard schematic:
** PineTab keyboard and Pinebook (Pro) keyboard using same controller and from same engineering source
** [http://files.pine64.org/doc/PineTab/Pinetab%20HB092A%20Keyboard%20Schematic.pdf PineTab Keyboard Schematic]
** [http://files.pine64.org/doc/PineTab/HB092_0884232458_Hynitron_PTP_20200514_662905_Linux_US_BackLight_CRC_175057F5.hex PineTab keyboard firmware code]
** [http://files.pine64.org/doc/PineTab/SH68F83V2.0.pdf PineTab Keyboard Controller Datasheet]

* PineTab certifications:
** [http://files.pine64.org/doc/cert/PineTab%20FCC-SDOC%20Certificate-S20060600404001.pdf PineTab FCC Certificate]
** [http://files.pine64.org/doc/cert/PineTab%20CE-RED%20Certificate-S20060600403.pdf PineTab CE RED Certificate]
** [http://files.pine64.org/doc/cert/PINETAB%20ROHS%20TEST%20REPORT.pdf PineTab ROHS Test Report]

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

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

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

* eMMC information:
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [http://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 64GB SanDisk eMMC Datasheet]

* CMOS camera module information:
** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
** [http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

* LCD touch screen panel information:
** [http://files.pine64.org/doc/datasheet/pinetab/GT9271.pdf GOODiX GT9271 Capacitive Touch Controller datasheet]
** [http://files.pine64.org/doc/datasheet/pinetab/GT9271_Config_20200818_142030_V66.cfg PineTab GT9271 Capacitive Touch Controller configuration file]

* Lithium battery information:

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

== Operating Systems ==
The PineTab will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PineTab uses the mainline kernel), only few of them will actually be usable on Early Adopters PineTab, due to specifics of working with LCD panel. Among those listed all except for postmarketOS have working builds.

=== UBPorts ===
[[File:Ubports-logo.png|100px]]
The UBPorts Ubuntu Touch is what preinstalled on PineTab Early Adopters batch.

It can update itself, and also jenkins daily build can be downloaded [https://ci.ubports.com/job/rootfs/job/rootfs-pinetab/ here]

In the event that WiFi fails to connect, the USB port can be used with an appropriate dongle to connect for internet using ethernet cable.

=== postmarketOS ===
[[File:PostmarketOS-logo.png|100px]]
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices.

It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...), and allows to encrypt your installation.

As of writing, postmarketOS supports the "pinetab-dev" and the Early Adopters versions of the PineTab.

Refer to the [https://wiki.postmarketos.org/wiki/PINE64_PineTab_(pine64-pinetab) PineTab wiki page] for installation instructions.

=== Arch Linux ARM ===
[[File:Archlinux-logo.png|100px]]
Arch Linux ARM with Phosh as the UI selection, maintained by the DanctNIX community.

The latest image can be downloaded [https://github.com/dreemurrs-embedded/Pine64-Arch/releases here]

=== Manjaro ARM ===
[[File:Manjaro-logo.svg|100px]]
The first Manjaro ARM image confirmed to be working on Early Adopters PineTab can be downloaded [https://next.manjaro.org/index.php/s/aeXDtbWnnBNEM2Q here], ref [https://forum.manjaro.org/t/manjaro-arm-alpha2-with-phosh-pinetab/150/12 forum thread].

Older Manjaro images with several different environments, including Phosh and Plasma, but '''not working on Early Adopters PineTab''' can be downloaded [https://osdn.net/projects/manjaro-arm/storage/pinetab/ here]

=== Mobian ===
[[File:Debian-logo.png|100px]]
Mobian is a project providing Debian images for mobile devices.

PineTab images can be downloaded [https://images.mobian-project.org/pinetab/ here]. Password is '''1234'''

== Installation instructions ==
For instructions on how to install the operating systems to the eMMC or microSD card see [[PinePhone Installation Instructions]]. The information is almost the same for the PineTab, as it is a very similar device. Do not try to use the PinePhone images though, use the PineTab images linked above.

=== Testing ===
To test an OS, just flash its image onto an microSD card, plug it into PineTab, and reboot.
Note that USB stick won't work.
Also note that you need to "flash", not just copy the file onto the card.
Also remember that you need to unpack image file if it's packed!

You can do it using Ubuntu Touch installed on the PineTab! For now, only Mobian is supported by the guide below.

* First, make sure you have enough free disk space and empty Downloads directory on the PineTab (while not strictly necessary, empty Downloads dir will simplify your typing. You can just move all files from there to another directory).
* Turn off Sleep when idle in the settings. Settings > Battery > Sleep when idle: Never
* Go to the Mobian link above and download compressed image (the one ending with .img.gz) - usual recommendation is to download latest, i.e. lowest one.
* Open terminal and type this in it:
cd Downloads
ls
* It should show you the name of the file you've just downloaded
* This file is compressed, so first you need to uncompress it. Type this into terminal:
gunzip *.gz && echo done
* This command will take some time (you won't see any progress until it's done). It either will succeed (and print "done") and fail (and print why).
* Now, let's have a look at disks. Type this into terminal:
lsblk
* It should show you a tree of disks and their partitions. If you don't have microSD card inserted yet, all of them begin with mmcblk2. Also, some of them have something in the "MOUNTPOINT" column
* Insert microSD card into PineTab. Note that all information on it will be deleted, so don't insert one with valuable information on it!
* type `lsblk` into terminal again.
* Note that now tree of disks has one or more new entries - starting with mmcblk0 - that's partitions of your microSD card.
* Confirm that size of mmcblk0 is close to size of the microSD card, and all lines starting with mmcblk0 have empty "MOUNTPOINT" column.
* now type this:
sudo dd if=`ls` of=/dev/mmcblk0 bs=1M status=progress
* It will take some time, depending on speed of your microSD card and size of image file
* Now, reboot your PineTab - type this into terminal:
sudo reboot
* PineTab should boot from the microSD you've just flashed

== Tips and tricks ==

=== Reset ===

If your PineTab is in unknown state or doesn't want to start.
Press power button for 7-8s. It makes a sound and you know it's totally off. 3 seconds after, power button again for 2-3s and it will start to boot. - thanks
@Aperricio on IRC for this hint

=== Display rotated 90° on Arch ARM ===
With the following command you can turn the display to landscape:

* echo 1 | sudo tee /sys/class/graphics/fbcon/rotate

This command does not persist a reboot.

[[Category:PineTab]] [[Category:Allwinner A64]]