PINE64 - User contributions [en]

PinePhone APN Settings

2022-10-06T15:57:02Z

Ferenc: /* Setting the APN */ Gnome already has this list.

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.

== Gnome ==

'''One of the biggest actively maintained open (Creative Commons Public Domain) database of mobile broadband service providers''', <br/>
and their APN settings is maintained by the Gnome project, and is available in their [https://gitlab.gnome.org/GNOME/mobile-broadband-provider-info/-/blob/main/serviceproviders.xml serviceproviders.xml]. <br/>
It is a rare case, when you don't find your own provider in that list,
but if it happens, then please consider contributing to it upstream. <br/>
If your provider is in that database, then for setting up the APN, you only have to select your provider from the list under <code> Settings > Network > Network Dropdown > Add new connection</code>. <br/>
Further details are [https://help.gnome.org/users/gnome-help/stable/net-mobile.html.en described by the Gnome help].

== 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) <br>
in /home/alarm/.mms/modemmanager/mms
<pre>
[Modem Manager]
CarrierMMSC=http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS_APN=Fast.t-mobile.com
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true

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

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

== Penny Mobil (Germany) ==

APN settings:

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

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

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

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

== Red Pocket (USA) ==

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

APN settings:

name: Red Pocket
APN: RESELLER

== Rogers (Canada) ==

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

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

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

== Simyo (Spain) ==

APN settings:
APN: orangeworld

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

== SFR (France) ==

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

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

== Sunrise (Switzerland) ==

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

== Swisscom (Switzerland) ==

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

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

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

== Telekom (Germany) ==

APN settings:

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

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

== Telekom (Hungary) ==

APN settings:

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

== Telenor/Yettel (Hungary) ==

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

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

== Telenor (Sweden) ==

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

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

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

== Tello (USA) ==

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

MMS settings:

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

== Telstra (Australia) ==

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

== Three (UK) ==

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

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

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

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

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

== Tracfone (USA) ==

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

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

Use the following APN settings:

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

To use Verizon's network:

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

MMS has worked with the following settings:

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

== T-Mobile (Czech Republic) ==

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

== Verizon Contract (USA) ==

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

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

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

vzwapp
vzwims

== Videotron (Canada) ==

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

== Virgin Mobile (Canada) ==

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

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

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

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

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

These settings work on 4G.

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

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

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

= Carriers that do not work =

== FreedomPop (USA) ==
VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to '''fp.com.attz'''. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit.

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

== Sprint (USA) ==

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

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

== Visible (USA) ==

Visible does not have any way to approve unsupported phones, it might be possible through APN settings, but requires more research and dev time. Even activating a SIM using a supported phone, and then moving it to the Pinephone does not work.

== Other ==

Other VoLTE services.

= External links =

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

[[Category:PinePhone]]

PinePhone APN Settings

2021-07-30T19:18:56Z

Ferenc: /* Telekom (Germany) */

The [https://en.wikipedia.org/wiki/Access_Point_Name APN] setting is the gateway between your carrier's cellular network and the '''public Internet'''. The APN setting - if not set automatically by the user's OS - has to be set by the user to enable the use of the mobile Internet on the phone.

= Setting the APN =

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

== Distributions with Phosh ==

APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (Arch Linux ARM, PureOS, Debian + Phosh) or <code> Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).



= List of tested carriers =

Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.

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

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

== AT&T-based ==

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

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

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

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

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

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

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

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

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

Other settings seem to work, too. [https://forum.congstar.de/Tarife/Tarif-Produktberatung/46325-Mobil-surfen-mit-congstar-manuelle-Einstellungen-zum-mobilen-Internet-APN/ Congstar mentions]

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

== Eastlink Wireless (Canada) ==

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

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

== Free (France) ==

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

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

== Freedom Mobile (Canada) ==

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

== Google Fi (USA) ==

These are settings that Google provides for their "data-only" SIM cards, but also appears to work fine with the normal SIM card for texting and calling.

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

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

== Hofer Telekom (Austria) ==

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

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

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

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

== Koodo (Canada) ==

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

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

== KT (South Korea) ==

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

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

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

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

These settings work on 4G.

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

== Mineo (Japan) ==

Tested with S plan (Softbank) and D plan (Docomo). Mobile LTE data currently working only on Phosh-based OSes, because they use Network Manager and Modem Manager. Ubuntu Touch not working yet, see issue #58. https://gitlab.com/ubports/community-ports/pinephone/-/issues/58

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

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

== Mint Mobile (USA) ==

Call their customer service to activate using the number on their website, or activate on their [https://my.mintmobile.com/activation website]. You may also need to reboot your phone.

Use the following APN settings:

Name: Ultra
APN: Wholesale

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

== Mobile Vikings (Belgium) ==

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

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

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

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

Source: autoconfig on ubports

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

Source: https://assistance.orange.fr/mobile-tablette/tous-les-mobiles-et-tablettes/depanner/probleme-avec-un-service-d-orange-internet-sms-mms-mails-cloud-tv/mms/configurer-un-apn-internet-et-mms_192948-738196

== Penny Mobil (Germany) ==

APN settings:

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

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

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

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

== Red Pocket (USA) ==

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

APN settings:

name: Red Pocket
APN: RESELLER

== Rogers (Canada) ==

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

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

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

== Simyo (Spain) ==

APN settings:
APN: orangeworld

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

== Sunrise (Switzerland) ==

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

== Swisscom (Switzerland) ==

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

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

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

== Telekom (Germany) ==

APN settings:

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

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

== Telekom (Hungary) ==

APN settings:

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

== Telenor (Sweden) ==

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

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

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

== Telstra (Australia) ==

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

== Three (UK) ==

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

== Tracfone (USA) ==

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

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

Use the following APN settings:

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

To use Verizon's network:

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

== Verizon Contract (USA) ==

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

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

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

vzwapp
vzwims

== Videotron (Canada) ==

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

== Virgin Mobile (Canada) ==

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

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

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

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

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

These settings work on 4G.

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

= Carriers that do not work =

== FreedomPop (USA) ==
VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to '''fp.com.attz'''. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit.

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

== Sprint (USA) ==

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

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

== Visible (USA) ==

Visible does not have any way to whitelist unsupported phones, it might be possible through APN settings, but requires more research and dev time. Even activating a SIM using a supported phone, and then moving it to the Pinephone does not work.

== Other ==

Other VoLTE services.

= External links =

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

[[Category:PinePhone]]

PinePhone Carrier Support

2021-07-30T19:16:51Z

Ferenc: /* Europe */

{{under construction}}

{{hint|MMS currently doesn't work in any distribution on the PinePhone without a [[PinePhone_Carrier_Support#MMS_workarounds|script]]! This means images and group chats will not work in text messages.}}

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

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

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

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

= Tested and working carriers =

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

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

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

== Europe ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Not tested || ArchLinux - 30 July 2021
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date) with Phosh, 2021-06-07
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm (Phosh,SXMO) 2021/04/29
*Manjaro - Phosh 2021/04/29
*Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
*Manjaro - Plasma Dev 2020/11/21
*Ubuntu Touch - 2020/11/26
*KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| USA || Verizon || No || No || No || No ||
*Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
*Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
*Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| USA || FaithWireless (AT&T) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 2021/04/29 (version 0.10.1-1, see the [[PinePhone_Carrier_Support#AT.26T|AT&T issues]] below.)
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
*Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 0.10.2 2021/05/29
|}

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

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

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

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

|}

= Special carrier notes =

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

Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:

== USA ==
=== AT&T ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. The PinePhone seems to work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. VoLTE is as yet untested.

However, it is likely AT&T will drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.

=== Consumer Cellular ===

Consumer Cellular is a MVNO that uses both AT&T and T-Mobile networks. On the AT&T network LTE data works without special configuration. If you transfer a SIM card from another phone to the PinePhone, you may need to contact customer support in order for them to register the IMEI association to the correct hardware; in one case it was first incorrectly identified as a Samsung Google Nexus Prime before later being correctly identified by the modem model Quectel EG25-G. Customer support also explicitly enabled VoLTE on the device. After VoLTE instructions on this site were followed and APN instructions on the Consumer Cellular site were followed, VoLTE was confirmed working.

=== Cricket Wireless ===
Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).

=== SimpleMobile ===
SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.

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

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

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

While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.

=== Verizon ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.

Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.

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

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

It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.

== Europe ==
=== Telekom Germany ===
With low signal, there may be loud interference noise audible in calls on the receiving end. It has not yet been tested whether or not this problem is carrier specific. An easy fix is extending the modem antenna with aluminum foil (or similar) inside the back cover of the phone.

= Known issues =
Known issues:
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

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

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

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

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

[[Category:PinePhone]]

PinePhone

2020-03-04T22:00:49Z

Ferenc: /* USB-C Connector */ Fix: USD => USB

The PinePhone is a smartphone created by Pine64, capable of running mainline Linux and supported by many partner projects. The "BraveHeart" edition was the first publicly-available version of the phone, though it came without a fully functional OS (factory test image) and was geared specifically towards tinkerers and hackers. People looking for a stable consumer-grade phone should wait for the final release, which is expected to occur in March 2020 and will be available for at least five years.

== "BraveHeart" PinePhone Unboxing and First Time Preparation Guide ==

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

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

After unboxing remove the back panel. Then remove the battery and peel off the clear plastic sticker below it that isolates the charging contact. Then replace the battery. See [[#Battery]] for more info.

If you power on the phone the factory test image will boot. RTL8723CS (WiFi modem) will fail unless there is a WiFi network in range for it to see and the battery is charged. EG25 will fail until battery is changed.

By default there is no true OS image installed on Braveheart phones. An SD card with a bootable image needs to be inserted into the phone. See section 12 below for a list of OS options. Note the SD and sim sockets are stacked on each other The SD slot is the "shallower" socket and the SIM card goes in the "deeper" socket.

'''Some videos that illustrate the process:'''

[https://www.youtube.com/watch?v=ACcxegtDVBI Excellent first time guide video from Rob Braxman Tech]

[https://www.youtube.com/watch?v=Z0FMW72_OYcI Flash an OS to microSD card video from Rob Braxman Tech]

== Specifications ==

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

== PinePhone Board Information, Schematics and Certifications ==
* PinePhone Main Board Schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard Schematic ver 1.1]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component top placement drawing ver 1.1]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1]
* PinePhone USB-C Small Board Schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20schematic%20v1.0%2020190730.pdf "Braveheart" PinePhone USB-C small board Schematic ver 1.0]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20top%20placement%20v1.0%2020190730.pdf "Braveheart" PinePhone USB-C small board component top placement drawing ver 1.0]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20bottom%20placement%20v1.0%2020190730.pdf "Braveheart" PinePhone USB-C small board component bottom placement drawing ver 1.0]
* PINE A64 Certifications:
** Not yet available

== 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]
* CMOS Camera module information:
** [http://files.pine64.org/doc/datasheet/pinephone/QZ01-rear-2019-0717(HW)%20Model.pdf PinePhone 5M Pixel Real CMOS Image Sensor Module]
** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module Datasheet]
** [http://files.pine64.org/doc/datasheet/pinephone/QZ01-front-2019-0717(HW)%20Model.pdf PinePhone 2M Pixel Front CMOS Image Sensor Module]
** [http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module Datasheet]
* LCD Touch Screen Panel information:
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20LCD-QZ01.pdf 5.99" 1440x720 LCD IPS Panel Specification]
** [http://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703 LCD Controller Datasheet]

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

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

== Developer works ==

=== Megous ===
[https://xnux.eu/howtos/pine64-pinephone-getting-started.html Getting start with PinePhone Hardware]

[https://xnux.eu/devices/pine64-pinephone.html#toc-pine64-pinephone State of development progress]

[https://xnux.eu/news.html PinePhone Technical News and Update, also applies to other Allwinner devices including PINE A64 SBC]

== Hardware Revisions ==

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

== Hardware Addons ==

===[[PinePhone Hardware Accessory Compatibility]] list===
List of devices working with the PinePhone (depending on OS support)

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

===Pogo Pins===

The PinePhone has 6 "pogo pins" on the back allowing for custom hardware extensions such as wireless charging or an IR blaster. The pogo pins provide access to an interrupt line, power input to charge the battery, 3.3v power source, and an I2C interface.

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

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

The uart is 115200n8

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

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

The serial connection is 3.3V

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

== Killswitch configuration ==

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.

[[File:PinePhone switches.jpeg|600px|thumb|left|Photo of Brave Heart switches from OSAKANA TARO on Twitter]]

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

== Battery ==

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

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

# +ve
# thermistor
# -ve
# not connected

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

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

'''Your Brave Heart phone ships with a plastic sticker between the battery and the phone. You need to open the back cover (gently), then remove the battery and finally remove the sticker. This is to protect the device from turning on during shipping.

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

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

'''Note''': the EG25 modem and RTL8723CS wifi/bluetooth do not work without battery power, even if you are supplying enough power to the Pinephone with USB-C.

== Modem and Carrier Support ==
There is a document about using the modem by user ''megi'' [https://megous.com/dl/tmp/modem.txt here.] This is from circa 18 Jan 2020.

Note at this date there is no TL;DR version - the script at the end to disable the modem before power off is pretty essential to avoid corrupting your modem's flash memory.

To check if the PinePhone is supported on your carrier:

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

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

== Factory Test Requirements ==

Most of the self tests should just work, but a couple of them will fail unless certain requirements are met.

=== RTL8723CS - WiFi ===

* The self test needs a visible access point nearby so it can discover an SSID.
* The self test may fail if the battery charge is too low.

=== EG25 - Modem ===

* A working micro-SIM that doesn't require a PIN to unlock
* Enough battery charge

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

The [[PinePhone Software Release#Software_Releases|'PinePhone Software Releases']] page has a complete list of currently supported Operating System images that work with the PinePhone as well as other related software information.

The list includes OS images and descriptions of:

[{{fullurl:PinePhone_Software_Release#postmarketOS}} http://files.pine64.org/sw/pine64_installer/json/postmarketos.png] [[PinePhone_Software_Release#postmarketOS|'''postmarketOS''']]

[{{fullurl:PinePhone_Software_Release#Ubuntu_Touch_by_UBPorts}} http://files.pine64.org/sw/pine64_installer/json/ubports.png] [[PinePhone_Software_Release#Ubuntu_Touch_by_UBPorts|'''Ubuntu Touch by UBPorts''']]

[[File:Ryodebianphosh.png]] [[PinePhone_Software_Release#Debian_.2B_Phosh|'''Debian + Phosh''']]

[{{fullurl:PinePhone_Software_Release#Maemo_Leste}} http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png] [[PinePhone_Software_Release#Maemo_Leste|'''Maemo Leste''']]

[{{fullurl:PinePhone_Software_Release#SailfishOS}} http://files.pine64.org/sw/pine64_installer/json/sailfishos.png] [[PinePhone_Software_Release#SailfishOS|'''SailfishOS''']]

[{{fullurl:PinePhone_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/manjaro.png] [[PinePhone_Software_Release#Manjaro_ARM|'''Manjaro ARM''']]

[{{fullurl:PinePhone_Software_Release#NixOS}} http://files.pine64.org/sw/pine64_installer/json/nixos.png] [[PinePhone_Software_Release#NixOS|'''NixOS''']]

[{{fullurl:PinePhone_Software_Release#LuneOS}} http://files.pine64.org/sw/pine64_installer/json/luneos.jpg] [[PinePhone_Software_Release#LuneOS|'''LuneOS''']]

[{{fullurl:PinePhone_Software_Release#Nemo_Mobile}} http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png] [[PinePhone_Software_Release#Nemo_Mobile|'''Nemo Mobile''']]

[{{fullurl:PinePhone_Software_Release#KDE_Neon}} http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png] [[PinePhone_Software_Release#KDE_Neon|'''KDE Neon''']]

[[File:Auroraos.jpeg]] [[PinePhone_Software_Release#Aurora|'''Aurora''']]

PineTime

2020-01-29T14:06:02Z

Ferenc: /* Development efforts */ Create nested table for Zehpyr implementations

== Frequently asked questions ==

'''Read this first!'''

* [https://wiki.pine64.org/index.php/Frequently_asked_questions_about_the_PineTime Click here to see frequently asked questions about the dev kit]
* [https://wiki.pine64.org/index.php/Lup_Yuen_Lee_Q%26A_about_PineTime Lup Yuen Lee Q&A about PineTime]

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

== SWD Pinout ==
The devkits have exposed SWD pins for flashing and debugging. The pinout is:
[[File:PineTime_SWD_location.jpg]]

== Driving the peripherals ==

=== 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)
| Clock/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.

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

=== How to write battery friendly software? ===

The key to save battery is to enable only what you need when you need it. NRF52832 has a lot of functionalities allowing you to draw as little current as possible. Here are some tips and tricks:

* Disable / shutdown / put in sleep mode '''all devices around the MCU''' (display controller, touch controller, external memory,...).
* Disable all '''peripheral inside the MCU''' when you don't need them (SPI, TWI(I²C),...). The power management of the NRF52832 is very smart and will completely shut down (power off and disable the clock) the peripheral when the software disables it.
* Put the MCU to sleep as soon and as often as possible. If you are not using a RTOS, this is done by calling ''WFE'' (wait for event) instruction. Most of the time, RTOS implement this functionality. For example, FreeRTOS calls it the ''tickless mode'' : it puts the CPU in sleep mode when no task is planned for execution for more than a specified time, and wakes up as soon as an event is detected or when a task is ready to run.
* Do not use logging (JLink RTT, SWO, semihosting,...), it uses a lot of power.
* Ensure that the debug circuitry of the MCU is not enabled when you measuring the battery life. The debug peripheral is enabled as soon as you connect a debugger to the device, and '''is not automatically disabled''', even if you disconnect the debugger. The software running in the NRF52832 cannot disable the debug peripheral. How to disable the debug circuitry:
- using ''nrfjprog --reset''
- using JLinkExe : issue the command ''writeDP 1 0''
* Read [https://infocenter.nordicsemi.com/pdf/nRF52832_Rev_2_Errata_v1.1.pdf the errata sheet of the MCU] and apply workarounds if they apply to you soft.

=== 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 informations are available in 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
|0x05 = SLEEP
|-
|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 : ''' 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!

== Programming firmware ==

=== Using JLink programmer and nrfjprog tools ===

The following steps have been tested with the Segger JLink embedded in the [https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52-DK NRF52-DK development board].

1. Connect the Pinetime SWD pins to the debugger (P20 on NRF52-DK)

{| class="wikitable"
!Pintime
!JLink
|-
|GND
|GND
|-
|SWDCLK
|SWDCLK
|-
|SWDIO
|SWDIO
|-
|VCC (3.3V)
|VTG (target detect)
|}

2. Unlock the device and erase the memory. '''You need to execute this step only once, to remove the read protection on the memory. Note that it will erase the whole flash memory of the MCU!''' :

nrfjprog -f NRF52 --recover

3. Program the BLE softdevice (if needed by the firmware). Replace PATH_TO_NRF_SDK by the path where you unzipped the [https://www.nordicsemi.com/Software-and-Tools/Software/nRF5-SDK NRF52 SDK] :

nrfjprog -f NRF52 --program /PATH_TO_NRF_SDK/components/softdevice/s132/hex/s132_nrf52_6.1.1_softdevice.hex --sectorerase

4. Program the firmware (replace firmware.hex by the actual filename of the firmware):

nrfjprog -f NRF52 --program firmware.hex --sectorerase

5. Reset and run the new firmware:

nrfjprog -f NRF52 --reset

=== Using OpenOCD and a Raspberry Pi ===

Instructions in [https://medium.com/@ly.lee/build-and-flash-rust-mynewt-firmware-for-pinetime-smart-watch-5e14259c55 Medium post], subsequently [https://medium.com/@ly.lee/openocd-on-raspberry-pi-better-with-swd-on-spi-7dea9caeb590 updated] with a more reliable method under development, so may be a bit of a moving target.

=== Using OpenOCD and a JLink ===

Start OpenOCD:

openocd \
-c 'interface jlink; transport select swd; source [find target/nrf52.cfg]' \
-c 'init'

Now you can connect to `127.0.0.1` port `4444` using telnet to invoke OpenOCD commands. GDB should be available on port `3333`.

=== Using STM32 bluepill as blackmagic probe ===

Instructions in [https://forum.pine64.org/showthread.php?tid=8816&pid=57095#pid57095 forum post] or [https://gist.github.com/darnel/dac1370d057e176386ca4026418abc2b gist] (mac os)

== Manual / Articles ==

* [https://github.com/najnesnaj/pinetime-zephyr Beginner manual explained how you to programs and install zephyr on PineTime Dev Kit, big thanks to najnesnaj :-)]

* [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://www.zephyrproject.org/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]

== Development efforts ==

{| class="wikitable"
!
! Project Homepage
! Project Source
! PineTime Implementations

|-
! FreeRTOS
|https://www.freertos.org
| https://sourceforge.net/projects/freertos/
| [https://github.com/JF002/Pinetime JF002/Pinetime]
[https://github.com/kaythe/pinetime-os kaythe/pinetime-os]

|-
! Zephyr
| https://www.zephyrproject.org
| https://github.com/zephyrproject-rtos/zephyr
|
{|
|[https://github.com/najnesnaj/pinetime-zephyr najnesnaj/pinetime-zephyr]
|-
|[https://github.com/SuperPrower/pinetime_zephyr_sample_fw SuperPrower/pinetime_zephyr_sample_fw]
|-
|[https://github.com/Dejvino/pinetime-hermes-firmware Dejvino/pinetime-hermes-firmware]
|}

|-
! mynewt
| https://mynewt.apache.org/about/
| https://github.com/apache/mynewt-core
| [https://github.com/lupyuen/pinetime-rust-mynewt lupyuen/pinetime-rust-mynewt]

|-
! MbedOS
| https://os.mbed.com
| https://github.com/ARMmbed/mbed-os
| [https://github.com/sethitow/awesome-pinetime sethitow/mbed-pinetime]

|-
! RIOT
| http://riot-os.org/
| https://github.com/RIOT-OS/RIOT/
| [https://github.com/bosmoment/PineTime-apps bosmoment/PineTime-apps]

|-
! TinyGo
| https://tinygo.org
| https://github.com/tinygo-org/tinygo
| [https://github.com/aykevl/go-smartwatch aykevl/go-smartwatch]

|-
! MicroPython
| https://micropython.org/
| https://github.com/micropython/micropython
| [https://github.com/daniel-thompson/wasp-os daniel-thompson/wasp-os]
|-
! AdaFruit bootloader
|
| https://github.com/adafruit/Adafruit_nRF52_Bootloader
| [https://github.com/daniel-thompson/wasp-bootloader daniel-thompson/wasp-bootloader]

|-
! UI concepts and drawings
|
|
| [https://gitlab.com/arteeh/pinetimeos arteeh/pinetimeos]

|-
|}

== Datasheets and Schematics ==

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

=== Component Datasheets ===
* NORDIC SoC information:
** [http://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf NORDIC nRF52832 Product Brief]
* PMU (Power Management Unit) information:
** [http://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]
** [http://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]
* SPI Flash information:
** [http://files.pine64.org/doc/datasheet/pinetime/MX25L6433F,%203V,%2064Mb,%20v1.6.pdf Macronix 64Mb(8MB) SPI NOR Flash]
** [http://files.pine64.org/doc/datasheet/pinetime/MX25L12835F,%203V,%20128Mb,%20v1.6.pdf Macronix 128Mb(16MB) SPI NOR Flash]
* LCD Panel:
** [http://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:
** [http://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]
** [http://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/5/51/CST816S%E6%95%B0%E6%8D%AE%E6%89%8B%E5%86%8CV1.1.en.pdf English Translation]
* Sensor:
** [http://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial VAcceleration Sensor Product Brief]
** [http://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]

= Community =
* [https://forum.pine64.org/forumdisplay.php?fid=134 PineTime forum]
* [https://riot.im/app/#/room/#pinetime64:matrix.org Matrix Channel] (No login required to read)
* IRC: Server us.pine64.xyz. Type /list to see all channels
* [https://t.me/pinetime Telegram group]
* [https://discordapp.com/invite/DgB7kzr Discord server invite link]

PineTime RTOS Comparison

2019-12-07T14:00:23Z

Ferenc: Add link to FreeRTOS contact a support page

{| class="wikitable"
!
! Project Homepage
! Project Source
! Sponsor
! Language
! PineTime Implementations

|-
! FreeRTOS
|https://www.freertos.org
| https://sourceforge.net/projects/freertos/
| [https://www.freertos.org/RTOS-contact-and-support.html Amazon Web Services]
| C
|
|-
! Zephyr
| https://www.zephyrproject.org
| https://github.com/zephyrproject-rtos/zephyr
| Linux Foundation
| C
|

|-
! mynewt
| https://mynewt.apache.org/about/
| https://github.com/apache/mynewt-core
| Apache Foundation
| C
| https://github.com/lupyuen/stm32bluepill-mynewt-sensor/tree/pinetime

|-
! Tock
| https://www.tockos.org
| https://github.com/tock/tock
|
| Rust
|

|-
! MbedOS
| https://os.mbed.com
| https://github.com/ARMmbed/mbed-os
| ARM
| C/C++
|

|-
! TinyGo
| https://tinygo.org
| https://github.com/tinygo-org/tinygo
|
| Go
| https://github.com/aykevl/go-smartwatch
|-
|}

Pinebook Pro

2019-11-27T23:00:31Z

Ferenc: Let's be precise, currently it's only the utility which is open source here, not the firmware. https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater/issues/6

= User Guide =

== Introducing PineBook Pro ==
[[File:PBP.jpg|400px|thumb|right|Pinebook Pro running stock Debian with MATE]]

The Pinebook Pro is a Linux and *BSD ARM laptop from [https://www.pine64.org/ PINE64]

It is built to be a compelling alternative to mid-ranged Chromebooks that people convert into Linux laptops. It features an IPS 1080p 14″ LCD panel, a premium magnesium alloy shell, high capacity eMMC storage, a 10,000 mAh capacity battery, and the modularity that only an open source project can deliver.

Key features include: the RK3399 SOC; USB-C for data, video-out and power-in (3A 5V); privacy switches for the microphone, BT/WiFi module, and camera; and expandable storage via NVMe (PCIe 4x) with an optional adapter.

The Pinebook Pro is equipped with 4GB LPDDR4 system memory, high capacity eMMC flash storage, and 128Mb SPI boot Flash. The I/O includes: 1x micro SD card reader (bootable), 1x USB 2.0, 1x USB 3.0, 1x USB type C Host with DP 1.2 and power-in, PCIe 4x for an NVMe SSD drive (requires an optional adapter), and UART (via the headphone jack by setting an internal switch).

The keyboard and trackpad both use the USB 2.0 protocol. The LCD panel uses eDP MiPi display protocol.

Many different Operating Systems (OS) are freely available from the open source community and partner projects. These include various flavors of Linux (Ubuntu, Debian, Manjaro, etc.) and *BSD.

== Software and OS Image Downloads ==
=== [[Pinebook Pro_Software_Release|Pinebook Pro]] ===
Under [[Pinebook Pro Software Release|'Pinebook Pro Software and OS Image Download Section']] you will find a complete list of currently supported Operating System images that work with the Pinebook as well as other related software.

The list includes OS images and descriptions of:
* [{{fullurl:PinebookPro_Software_Release#Debian_Desktop}} http://files.pine64.org/sw/pine64_installer/json/debian.png] [[PinebookPro_Software_Release#Debian Desktop|'''Debian Desktop (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Bionic_LXDE}} http://files.pine64.org/sw/pine64_installer/json/lxde.png] [[PinebookPro_Software_Release#Bionic LXDE|'''Bionic LXDE (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Bionic_Mate}} http://files.pine64.org/sw/pine64_installer/json/mate.png] [[PinebookPro_Software_Release#Bionic Mate|'''Bionic Mate (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Chromium}} http://files.pine64.org/sw/pine64_installer/json/chromium.jpg] [[PinebookPro_Software_Release#Chromium|'''Chromium (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Android_7.1_microSD}} http://files.pine64.org/sw/pine64_installer/json/android_7.png] [[PinebookPro_Software_Release#Android_7.1_microSD|'''Android 7.1 (microSD Boot)''']]           [{{fullurl:PinebookPro_Software_Release#Android_7.1_eMMC}} http://files.pine64.org/sw/pine64_installer/json/android_7.png] [[PinebookPro_Software_Release#Android_7.1_eMMC|'''Android 7.1 (eMMC)''']]

----

=== Quick Links to OS Images Build Sources===
'''Some of the provided OS images are still in <span style="color:#FF0000">beta or nightly build</span> and only fit for testing purposes. These images ought to be avoided for normal usage - use them at <span style="color:#FF0000">your own risk</span>'''
* [https://github.com/ayufan-rock64/linux-build/releases/ ayufan's Linux build repo]
* [https://github.com/ayufan-rock64/chromiumos-build/releases ayufan's Chromium OS build repo]
* [https://github.com/mrfixit2001/debian_desktop/releases mrfixit2001's Linux debian desktop build repo]

== Keyboard ==
The Pinebook Pro is available in two keyboard configurations: ISO and ANSI. Both the keyboard and trackpad in the Pinebook Pro use the USB 2.0 protocol and show up as such in xinput. The keyboard features function (Fn) keys in the F-key row, which include display brightness controls, sound volume, trackpad lock, and other functionality. There is also a custom PINE64 logo key that functions as Menu/Super key. It has also a secondary functionality for setting the privacy switches.

The keyboard firmware binary can be flashed from userspace using the provided open source utility.

Documentation for the keyboard can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].

=== Typing special characters ===
The UK ISO Layout does not have dedicated keys for characters like the German umlauts (Ä,Ö,Ü, etc). Certain characters can still be generated by means of either key combinations or key sequences.
{| class="wikitable"
!Character
!Key combination/sequence
|-
|Ä, Ö, Ü, ä, ö, ü
|[[Wikipedia:AltGr_key|[AltGr]]]+["] followed by [A], [O], [U], [a], [o] or [u]
|-
|µ
|[AltGr]+[m]
|-
|Ø, ø
|[AltGr]+[O], [AltGr]+[o]
|-
|@
|[AltGr]+[q] (as on the German layout)
|-
|ß
|[AltGr]+[s]
|-
|§
|[AltGr]+[S]
|-
|°
|[AltGr]+[)]
|}

=== Privacy Switches ===
There are three privacy switches mapped to the F10, F11 and F12 keys on the Pinebook Pro keyboard. They de/activate the following:

{| class="wikitable"
|+ Privacy switch function and description
! Combination
! Effect
! Description
|-
! scope=row | PINE64 logo key+F10
| Microphone Privacy switch || CAPs lock LED blinks. 2 blinks = enabled, 3 blinks = disabled
|-
! scope=row | PINE64 logo key+F11
| WiFi Privacy switch || NUM lock LED blinks. 2 blinks = enabled, 3 blinks = disabled. '''Re-enabling requires reboot''' (or a [//forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645 command line hack to bind/unbind]).
|-
! scope=row | PINE64 logo key+F12
| Camera privacy switch || CAPs lock and NUM lock LEDs blink together. 2 blinks = enabled, 3 blinks = disabled
|}

'''(Press the PINE64 logo key plus Fn (10/11/12) for 3 seconds)'''

The keyboard uses special firmware that operates separately of the operating system. It detects if either the F10, F11 or F12 key, and the Pine key were pressed for 3 seconds. This disables the peripherals as listed above by cutting off their power. Which has the same result as cutting off the power to each peripheral with a physical switch. This implementation is very secure since the firmware that determines whether a peripheral gets power is not a part of the Pinebook Pro’s operating system. So the power state value for each peripheral cannot be overridden or accessed from the operating system. The power state setting for each peripheral is stored across reboots.

== Trackpad ==

The trackpad is large, smooth (metallic to-the-touch), and has two actuating buttons. It is the only component of the Pinebook Pro held in place with strong adhesive tape. It supports multi-touch functionality.
Documentation for the trackpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].
The trackpad firmware binary can be flashed from userspace using the provided open source utility (https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater).

'''Everyone with a Pinebook Pro produced in 2019 should update their keyboard and trackpad firmware.'''

Brief description of trackpad flashing process (please refer to original documentation for details)

Before you start:
Your Pinebook Pro should be either fully charged or, preferably, running of mains. This utility will be writing chips on the keyboard and trackpad, so a loss of power during any stage of the update can result in irrecoverable damage to your trackpad or keyboard.

The scripts ought to work on all OSs available for the Pinebook Pro. Some OSs may, however, require installation of relevant dependencies.

What you'll need:

*Your Pinebook Pro fully charged / running off of mains power
*Connection to WiFi
*An external USB keyboard/ access to the Pinebebook Pro via ssh

What you need to do:

<pre>
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo apt-get install build-essential libusb-1.0-0-dev xxd
make
</pre>

Step 1
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-1
sudo reboot
</pre>

Step 2 (after reboot)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2
sudo reboot
</pre>

== Power Supply ==
* Input Power: 5V DC @ 3A
* Mechanical: 3.5mm OD / 1.35mm ID, Barrel jack
* USB-C 15W PD quickcharge
* Only use one power input at a time, barrel jack OR USB-C

== LEDs ==
In total there are four LEDs on the Pinebook Pro, three of which are placed in the top left side of the keyboard, and one near the barrel-port:

:1. The red LED next to the barrel-port indicates charging. It will illuminate when mains power is supplied to the Pinebook Pro from either the standard power supply unit or a USB-C smartphone charger.

:2. The power indicator LED on the Pinebook Pro supports three different colours: green, amber and red. It is also capable of flashing/blinking to indicate activity. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused).

:3. The Num lock, green LED.

:4. The Caps lock, green LED.

(The Num and Caps lock LEDs have a secondary function. When the privacy switches get activated they blink to confirm that switch has been activated.)

== Webcam ==
* 1080p resolution
* Some people test with the application Cheese
WIP

== Microphones ==
Some Pinebook Pro chassis have 2 microphone labeled holes. Only the left microphone is populated.

== Bluetooth and WiFi ==
WIP

== LCD Panel ==
* 1080p resolution
WIP

== Using the UART ==
[[File:PBPUART.jpeg|400px|thumb|right|Headphone Jack UART wiring reference]]

UART output is enabled by flipping the UART switch to the ON position (item 9). To do so you need to remove the Pinebook Pro's bottom cover - please follow [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly proper disassembly and reassembly protocol]. The OFF position is towards the touchpad, the ON position is towards the display hinges.

With the UART switch in the ON position, console is relayed via the audiojack and the laptop's sound is turned OFF. PINE64 store sells [https://store.pine64.org/?product=pinebook-serial-console a dedicated serial console] but you can make your own if you have a serial console USB 2.0 adapter and old/ broken headphones. If you do make your own cable, please ensure that you are using a 3.3v interface (such as the CH340, FTDI-232R or PL2303 - which are often sold in 3.3v and 5v variants) to avoid damage to the CPU.

Insert the USB plug of the cable into an open USB port on the machine which will monitor. Run the following in a terminal:

<code>
$ lsusb
</code>

you should find a line similar to this:

<code>
Bus 001 Device 058: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
</code>

You may have to clean the USB contacts of the Serial cable to get a good connection if you do not find that line.

The audio jack of the Serial cable should be fully inserted into the Pinebook Pro audio port.

Serial output should now be accessible using screen, picocom or minicom (and others).
Examples:

<code>
screen /dev/ttyUSB0 1500000

picocom /dev/ttyUSB0 -b 1500000

minicom -D /dev/ttyUSB0 -b 1500000</code>

Current versions of u-Boot do not use the UART for console output. The console function is activated by the Linux kernel. Thus, if you use a non-Pinebook Pro Linux distro and want the UART as a console, you have to manually enable it.

== Using the optional NVMe adapter ==
The optional NVMe adapter allows the use of M.2 cards that support the NVMe standard, (but not SATA standard).

=== Installing the adapter ===

The v2.1 SSD adapter that is shipped with the initial Pinebook Pro batches has a couple of problems although with a little hacking they can still be used. There is [https://forum.pine64.org/showthread.php?tid=8322&pid=52700#pid52700 an unofficial tutorial on the forums] describing the mods.

=== Using as data drive ===
As long as the kernel in use has both the PCIe and NVMe drivers, you should be able to use a NVMe drive as a data drive. Even automounting at boot, (from eMMC or SD card). This applies to both Linux and FreeBSD, though Android or Chromium OS may need testing. Simply use the normal partitioning and file system creation tools.

=== Using as OS root drive ===
It is not possible to boot directly off a NVMe drive. The SoC does not include the NVMe boot code, thus the NVMe is not in the SoC's boot order.

Howevever, it is possible to initially boot off an eMMC or SD card, then transfer to a root file system on the NVMe. Even have all the other file systems on the NVMe. except <code>/boot</code>.<br/>
Instructions for doing this are not complete as of 2019/11/20, but the forums has had people doing this with successful results.

== Using the PineBook Pro ==

=== Bypass Cables ===
The mainboard features two (disconnected by default) bypass cables that are only to be used with the battery disconnected. The female (10) male (6) ends of the bypass cables can be connected to provide power to the mainboard if you need to run the laptop without a battery. Please refer to this [http://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf engineering notice].

WARNING: Do not connect the bypass cables with the battery connected. Using the bypass cables with the battery connected can permanently damage the computer.

=== [[Pinebook_Service_Step_by_Step_Guides|Pinebook Service Step-by-Step Guides]] ===
<span style="color:#FF0000">Placeholder for Pinebook Pro specific guides</span>

Under [[Pinebook_Service_Step_by_Step_Guides|'Service Guides for Pinebook']] you can find instructions guides concerning disassembly of:

'''Note: The installation process on Pinebook Pro similar to 14" Pinebook'''

'''Note: The installation process is the reverse order of removal guide'''

* 14″ Pinebook Lithium Battery Pack Removal Guide
* 14″ Pinebook LCD Panel Screen Removal Guide
* 14″ Pinebook eMMC Module Removal Guide

= Troubleshooting guide =
Tips, tricks and other information for troubleshooting your Pinebook Pro
=== New from the factory - Pinebook Pro won't boot / power on ===
* Some Pinebook Pros came from the factory with the eMMC switch in the disabled position. It should be switched towards the back / hinge to enable the eMMC.<br>
* The eMMC may have come loose during shipment. [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly Open] the back and verify that the eMMC is firmly seated.<br>
* You may want to try unplugging the SD card daughterboard ribbon cable and see if it powers on (remove the battery and peel off a bit of the tape before unplugging it to avoid damage). If it does, try reseating it on both sides. It might have come loose during shipping.
* It's possible that your eMMC is empty from the factory. Simply create a bootable SD card and see if your Pinebook Pro boots. If so, you can then write an OS image to the eMMC.

=== Pinebook Pro won't boot when using UART console cable ===
* If you're using the UART cable sold on the Pine Store, you may want to see if it boots after you disconnect it. Some users report that custom-made cables based on FTDI UART adapters do not cause this issue.

=== Pinebook Pro will not power on after toggling the eMMC enable/disable switch ===
* This may happen if you meant to toggle the UART/Headphone switch (9) towards touchpad for headphone use and instead you toggled the eMMC enable/disable switch (24).
* After reenabling eMMC by toggling switch (24) towards hinge, if Pinebook Pro does not turn on then press the RESET button (28). It is clearly marked 'reset' on the PCB board.

=== Keys not registering / missing keys when typing ===
This issue occurs when your thumb or edge of the palm makes contact with left or right tip of the trackpad when you type. This is due to the palm rejection firmware being too forceful. Instead of only disabling the trackpad, so your cursor does not move all over the screen, it disables both the trackpad and the keyboard.

Using Fn+F7 to disable the touchpad will keep it from also disabling the keyboard.

A [https://forum.pine64.org/showthread.php?tid=8407 firmware update] has been released to address this.

=== WiFi issues ===
* First, check the privacy switches to make sure your WiFi is enabled. They are persistant. See [[Pinebook_Pro_Main_Page#Privacy_Switches]]
* Next, you may have to modify the file "/etc/NetworkManager/NetworkManager.conf" as user "root", and replace "managed=false" with "managed=true". Then reboot.
* For connections that drop and resume too often, it maybe WiFi power management from earlier OS releases. Later OS releases either removed WiFi power management, or default to full power. Try an updated OS.

=== Accessory Hardware Compatibility ===

[[PBP_HW_Compatibiity|PineBookPro Hardware Compatibility]]

= Technical Reference =

== Accessing the Internals - Disassembly and Reassembly ==
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]

'''WARNING:''' Do not open the laptop by lifting the lid while the Pinebook Pro bottom cover is removed - this can cause structural damage to the hinges and/or other plastic components of the chassis such as the IO port cut-outs.

'''WARNING:''' When removing the back cover plate, use care if sliding fingertips between back cover plate and palm rest assembly. The back cover plate edges are sharp.

When disassembling the laptop make sure that it is powered off and folded closed. To remove the bottom cover of the Pinebook Pro, first remove the ten (10) Phillips head screws that hold the bottom section of the laptop in place. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis.

During reassembly, make sure that the back-screw standoffs are in place and seated correctly. To reassemble the Pinebook Pro, slide the bottom section into place so it meets the front lip of the keyboard section. Secure the front section (where the trackpad is located) in place using the short screws in the front left and right corners. Then proceed to pop in the bottom panel into place. Secure the bottom section (where hinges are located) by screwing in the left and right corners. Then screw in the remaining screws and run your finger though the rim on the chassis to make sure its fitted correctly. Note that the front uses the remaining 2 short screws.

NOTE: The screws are small and should only be finger tight. Too much force will strip the threads. If after installing screws the back cover plate has not seated properly on one side, open the display and hold the base on either side of the keyboard and gently flex the base with both hands in opposing directions. Once the side pops further in, then recheck the screws on that side. If it does not pop back in, just let it be.

== Pinebook Pro Internal Layout ==

=== Main chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM (21)
* SPI NOR flash memory (29)
* eMMC flash memory (26)
* WiFi/BT module (27)

=== Mainboard Switches and Buttons ===
There are two switches on the main board: disabling the eMMC (24), and enabling UART (9) via headphone jack.

The Reset and Recovery buttons (28): the reset button performs an immediate reset of the laptop. The Recovery button is used to place the device in maskrom mode; this mode allows flashing eMMC using Rockchip tools (e.g. rkflashtools).

[[File:PBPL_S.jpg]]

=== Key Internal Parts ===
{| class="wikitable"
|+ Numbered parts classification and description
! Number
! Type
! Descriptor
|-
! scope=row | 1
| Component || RK3399 System-On-Chip
|-
! scope=row | 2
| Socket || PCIe 4X socket for optional NVMe adapter
|-
! scope=row | 3
| Socket || Speakers socket
|-
! scope=row | 4
| Socket || Trackpad socket
|-
! scope=row | 5
| Component || Left speaker
|-
! scope=row | 6
| Connector || Male power bridge connector
|-
! scope=row | 7
| Socket || Keyboard Socket
|-
! scope=row | 8
| Component || Optional NVMe SSD adapter
|-
! scope=row | 9
| Switch || UART/Audio switch - outputs UART via headphone jack
|-
! scope=row | 10
| Socket || Female power bridge socket
|-
! scope=row | 11
| Socket || Battery socket
|-
! scope=row | 12
| Component || Trackpad
|-
! scope=row | 13
| Component || Battery
|-
! scope=row | 14
| Component || Right speaker
|-
! scope=row | 15
| Socket || Micro SD socket
|-
! scope=row | 16
| Socket || Headphone / UART jack
|-
! scope=row | 17
| Socket || USB 2.0
|-
! scope=row | 18
| Socket || Daughterboard-to-mainboard ribbon cable socket
|-
! scope=row | 19
| Cable || Daughterboard-to-mainboard ribbon cable
|-
! scope=row | 20
| Component || microphone
|-
! scope=row | 21
| Component || LPDDR4 RAM
|-
! scope=row | 22
| Socket || Mainboard-to-daughterboard ribbon cable socket
|-
! scope=row | 23
| Socket || Microphone socket
|-
! scope=row | 24
| Switch || Switch to hardware disable eMMC
|-
! scope=row | 25
| Antenna || BT/WiFI antenna
|-
! scope=row | 26
| Component || eMMC flash memory module
|-
! scope=row | 27
| Component ||BT/WiFi module chip
|-
! scope=row | 28
| Buttons || Reset and recovery buttons
|-
! scope=row | 29
| Component || SPI flash storage
|-
! scope=row | 30
| Socket || eDP LCD socket
|-
! scope=row | 31
| Socket || Power in barrel socket
|-
! scope=row | 32
| Socket || USB 3.0
|-
! scope=row | 33
| Socket || USB type C
|}

== Bootable Storage ==

The Pinebook Pro is capable of booting from eMMC, USB 2.0, USB 3.0, or an SD card. It cannot boot from USB-C. The boot order of the hard-coded ROM of its RK3399 SoC is: SPI NOR, eMMC, SD, USB OTG.

At this time, the Pinebook Pro ships with a Debian + MATE build with [https://www.denx.de/wiki/U-Boot/ uboot] on the eMMC. Its boot order is: SD, then eMMC. Booting off USB storage is not currently available, but will be in the future.

(An update has been pushed for the default Debian + MATE build that improves compatibility with booting other OSs from an SD card. In order to update, fully charge the battery, establish an internet connection, click the update icon in the toolbar, and then reboot your Pinebook Pro. Please see [https://forum.pine64.org/showthread.php?tid=7830 this log] for details.)

Please note that PCIe, the interface used for NVMe SSD on the Pinebook Pro, is not bootable on the RK3399 and therefore is not a part of the boot hierarchy. It is possible to run the desired OS from NVMe by pointing extlinux on the eMMC to rootfs on the SSD. This requires uboot, the Kernel image, DTB, and extlinux.conf
in a /boot partition on the eMMC.

=== eMMC information ===

The eMMC storage will show up as multiple block devices:
*mmcblk1boot0 - eMMC standard boot0 partition, may be 4MB
*mmcblk1boot1 - eMMC standard boot1 partition, may be 4MB
*mmcblk1rpmb - eMMC standard secure data partition. may be 16MB
*mmcblk1 - This block contains the user areas

Only the last is usable as regular storage device in the Pinebook Pro.
The device number of "1" shown above may vary, depending on kernel.

=== Boot sequence details ===

The RK3399's mask 32KB ROM boot code looks for the next stage of code at byte off-set 32768. This is where u-Boot code would reside on any media that is bootable.

== Pinebook Pro Dimensions ==
* Dimensions: 329mm x 220mm x 12mm (WxDxH)
* Weight: 1.26Kg

== SoC and Memory Specification ==
[[File:Rockchip_RK3399.png|right]]
* Based on Rockchip RK3399

=== CPU Architecture ===
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
** Full implementation of the ARM architecture v8-A instruction set (both AArch64 and AArch32)
** ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
** ARMv8 Cryptography Extensions
** VFPv4 floating point unit supporting single and double-precision operations
** Hardware virtualization support
** TrustZone technology support
** Full CoreSight debug solution
** One isolated voltage domain to support DVFS
* Cortex-A72 (big cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
** Superscalar, variable-length, out-of-order pipeline
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
* Cortex-A53 (little cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
** In-order pipeline with symmetric dual-issue of most instructions
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Cortex-M0 (control processors):
** [https://developer.arm.com/ip-products/processors/cortex-m/cortex-m0 Cortex-M0 CPU]
** Two Cortex-M0 cooperate with the central processors
** Architecture: Armv6-M
** Thumb/Thumb2 instruction set
** 32 bit only

=== GPU Architecture ===
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provide stunning visuals for UHD content.
* Frequency 650MHz
* Throughput 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2., Vulkan 1.0*., OpenCL™ 1.1, 1.2., DirectX® 11 FL11_1., RenderScript™.

=== System Memory ===
* RAM Memory:
** LPDDR4
** Dual memory channels on the CPU, each 32 bits wide
** Quad memory channels on the RAM chip, each 16 bits wide, 2 bonded together for each CPU channel
** 4GB as a single 366 pin mobile RAM chip
* Storage Memory:
** 64GB eMMC module, can be upgraded to a 128GB eMMC module. (The initial PINE64 community build version shipped with a 128GB eMMC.)

=== Battery ===
* Lithium Polymer Battery (10,000 mAH)

=== Display ===
* 14.1" 1920x1080 IPS LCD panel

=== Video out ===
* USB-C Alt mode DP up to 3840x2160 p60

=== Audio ===
* 3.5mm stereo earphone/microphone plug
* Build in stereo speakers

=== Network ===
* WiFi:
** 802.11 b/g/n/ac
** Dual band: 2.4Ghz & 5Ghz
** Single antenna
* Bluetooth 5.0

=== Expansion Ports ===
* MicroSD card:
** Bootable
** Supports SD, SDHC and SDXC cards, up to 512GB
** Version SD3.0, up to 50MB/s
* USB ports:
** 1 x USB 2.0 Type-A Host Port, bootable
** 1 x USB 3.0 Type-A Host Port, 5Gbps, is not bootable
** 1 x USB 3.0 Type-C OTG Port, 5Gbps, (includes laptop charging function), is not bootable
* Headphone jack switchable to UART console mux circuit
* Optional NVMe adapter:
** PCIe 2.x, 5GT/s per lane
** 4 PCIe lanes, can not be bifurcated, (however, can be used with 1 or 2 lane NVMe cards)
** Maximum length for M.2 card is 80mm (M.2 2280)
** Power: 2.5W continuous, 8.25W peak momentary
** Does not support SATA M.2 cards
** Does not support USB M.2 cards

== Pinebook Pro Schematics and Certifications ==
* Pinebook Pro Main Board Schematic And Silkscreen:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_mainboard_schematic.pdf Pinebook Pro Main Board ver 2.1 Schematic]
** [https://wiki.pine64.org/images/3/30/Pinebookpro-v2.1-top-ref.pdf Pinebook Pro ver 2.1 Top Layer Silkscreen]
** [https://wiki.pine64.org/images/b/b7/Pinebookpro-v2.1-bottom-ref.pdf Pinebook Pro ver 2.1 Bottom Layer Silkscreen]
* Pinebook Pro Daughter Board Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_daughterboard_schematic.pdf Pinebook Pro Daughter Board ver 2.1 Schematic]
* Optional Pinebook Pro NVMe Adapter Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_NVMe-adapter_schematic.pdf Pinebook Pro NVMe Adapter Board ver 2.1 Schematic]
* Serial Console Earphone Jack Pinout:
** [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinkbook Serial Console Earphone Jack Pinout]
* Pinebook Pro Case:
** [https://send.firefox.com/download/b34c14f3e0a3d66d/#15Cx1vBaGKmJr57y85U2qQ AutoCAD DWG File]
* Pinebook Pro Certifications:
** Not Yet Available

== Datasheets for Components and Peripherals ==
* Rockchip RK3399 SoC information:
** [http://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [http://opensource.rock-chips.com/images/2/28/Rockchip_RK3399_Datasheet_V1.8-20180529.pdf Rockchip RK3399 Datasheet V1.8]
** [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
** [http://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (366 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 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 SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [http://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Wireless related info:
** [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]
* Audio Codec (ES8316)
** [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]
* LCD Panel:
** [http://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]
* Touchpad information:
** [http://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf Touchpad Specification for Pinebook Pro model]
* Keyboard information:
** [http://www.sinowealth.com/ftp/ph/SH68F83/SH68F83V2.0.pdf Sinowealth SH68F83 Datasheet]
** US ANSI: XK-HS002 MB27716023
* Full HD Camera sensor:
** [http://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification in Chinese]
** [http://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Data Sheet]
* Lithium Battery information:
** [http://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification for 14" model]

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=111 Pinebook Pro Forum]
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [[RockPro64 Guides]]
* [http://www.pine64.xyz:9090/?channels=ROCK64 ROCK64/ROCKPro64 IRC Channel]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]

Pinebook Pro

2019-11-23T06:09:01Z

Ferenc: /* Keyboard */ Link to "Datasheets for Components and Peripherals"

= User Guide =

== Introducing PineBook Pro ==
[[File:PBP.jpg|400px|thumb|right|Pinebook Pro running stock Debian with MATE]]

The Pinebook Pro is a Linux and *BSD ARM laptop from [https://www.pine64.org/ PINE64]

It is built to be a compelling alternative to mid-ranged Chromebooks that people convert into Linux laptops. It features an IPS 1080p 14″ LCD panel, a premium magnesium alloy shell, high capacity eMMC storage, a 10,000 mAh capacity battery, and the modularity that only an open source project can deliver.

Key features include: the RK3399 SOC; USB-C for data, video-out and power-in (3A 5V); privacy switches for the microphone, BT/WiFi module, and camera; and expandable storage via NVMe (PCIe 4x) with an optional adapter.

The Pinebook Pro is equipped with 4GB LPDDR4 system memory, high capacity eMMC flash storage, and 128Mb SPI boot Flash. The I/O includes: 1x micro SD card reader (bootable), 1x USB 2.0, 1x USB 3.0, 1x USB type C Host with DP 1.2 and power-in, PCIe 4x for an NVMe SSD drive (requires an optional adapter), and UART (via the headphone jack by setting an internal switch).

The keyboard and trackpad both use the USB 2.0 protocol. The LCD panel uses eDP MiPi display protocol.

Many different Operating Systems (OS) are freely available from the open source community and partner projects. These include various flavors of Linux (Ubuntu, Debian, Manjaro, etc.) and *BSD.

== Software and OS Image Downloads ==
=== [[Pinebook Pro_Software_Release|Pinebook Pro]] ===
Under [[Pinebook Pro Software Release|'Pinebook Pro Software and OS Image Download Section']] you will find a complete list of currently supported Operating System images that work with the Pinebook as well as other related software.

The list includes OS images and descriptions of:
* [{{fullurl:PinebookPro_Software_Release#Debian_Desktop}} http://files.pine64.org/sw/pine64_installer/json/debian.png] [[PinebookPro_Software_Release#Debian Desktop|'''Debian Desktop (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Bionic_LXDE}} http://files.pine64.org/sw/pine64_installer/json/lxde.png] [[PinebookPro_Software_Release#Bionic LXDE|'''Bionic LXDE (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Bionic_Mate}} http://files.pine64.org/sw/pine64_installer/json/mate.png] [[PinebookPro_Software_Release#Bionic Mate|'''Bionic Mate (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Chromium}} http://files.pine64.org/sw/pine64_installer/json/chromium.jpg] [[PinebookPro_Software_Release#Chromium|'''Chromium (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Android_7.1_microSD}} http://files.pine64.org/sw/pine64_installer/json/android_7.png] [[PinebookPro_Software_Release#Android_7.1_microSD|'''Android 7.1 (microSD Boot)''']]           [{{fullurl:PinebookPro_Software_Release#Android_7.1_eMMC}} http://files.pine64.org/sw/pine64_installer/json/android_7.png] [[PinebookPro_Software_Release#Android_7.1_eMMC|'''Android 7.1 (eMMC)''']]

----

=== Quick Links to OS Images Build Sources===
'''Some of the provided OS images are still in <span style="color:#FF0000">beta or nightly build</span> and only fit for testing purposes. These images ought to be avoided for normal usage - use them at <span style="color:#FF0000">your own risk</span>'''
* [https://github.com/ayufan-rock64/linux-build/releases/ ayufan's Linux build repo]
* [https://github.com/ayufan-rock64/chromiumos-build/releases ayufan's Chromium OS build repo]
* [https://github.com/mrfixit2001/debian_desktop/releases mrfixit2001's Linux debian desktop build repo]

== Keyboard ==
The Pinebook Pro is available in two keyboard configurations: ISO and ANSI. Both the keyboard and trackpad in the Pinebook Pro use the USB 2.0 protocol and show up as such in xinput. The keyboard features function (Fn) keys in the F-key row, which include display brightness controls, sound volume, trackpad lock, and other functionality. There is also a custom PINE64 logo key that functions as Menu/Super key. It has also a secondary functionality for setting the privacy switches.

The keyboard firmware is open sourced can be flashed from userspace using the provided utility.

Documentation for the keyboard can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].

=== Typing special characters ===
The UK ISO Layout does not have dedicated keys for characters like the German umlauts (Ä,Ö,Ü, etc). Certain characters can still be generated by means of either key combinations or key sequences.
{| class="wikitable"
!Character
!Key combination/sequence
|-
|Ä, Ö, Ü, ä, ö, ü
|[[Wikipedia:AltGr_key|[AltGr]]]+["] followed by [A], [O], [U], [a], [o] or [u]
|-
|µ
|[AltGr]+[m]
|-
|Ø, ø
|[AltGr]+[O], [AltGr]+[o]
|-
|@
|[AltGr]+[q] (as on the German layout)
|-
|ß
|[AltGr]+[s]
|-
|§
|[AltGr]+[S]
|-
|°
|[AltGr]+[)]
|}

=== Privacy Switches ===
There are three privacy switches mapped to the F10, F11 and F12 keys on the Pinebook Pro keyboard. They de/activate the following:

{| class="wikitable"
|+ Privacy switch function and description
! Combination
! Effect
! Description
|-
! scope=row | PINE64 logo key+F10
| Microphone Privacy switch || CAPs lock LED blinks. 2 blinks = enabled, 3 blinks = disabled
|-
! scope=row | PINE64 logo key+F11
| WiFi Privacy switch || NUM lock LED blinks. 2 blinks = enabled, 3 blinks = disabled. '''Re-enabling requires reboot''' (or a [//forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645 command line hack to bind/unbind]).
|-
! scope=row | PINE64 logo key+F12
| Camera privacy switch || CAPs lock and NUM lock LEDs blink together. 2 blinks = enabled, 3 blinks = disabled
|}

'''(Press the PINE64 logo key plus Fn (10/11/12) for 3 seconds)'''

The keyboard uses special firmware that operates separately of the operating system. It detects if either the F10, F11 or F12 key, and the Pine key were pressed for 3 seconds. This disables the peripherals as listed above by cutting off their power. Which has the same result as cutting off the power to each peripheral with a physical switch. This implementation is very secure since the firmware that determines whether a peripheral gets power is not a part of the Pinebook Pro’s operating system. So the power state value for each peripheral cannot be overridden or accessed from the operating system. The power state setting for each peripheral is stored across reboots.

== Trackpad ==

The trackpad is large, smooth (metallic to-the-touch), and has two actuating buttons. It is the only component of the Pinebook Pro held in place with strong adhesive tape. It supports multi-touch functionality.

The trackpad firmware is open sourced and can be flashed from userspace using the provided utility (https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater).

Documentation for the trackpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].

== Power Supply ==
* Input Power: 5V DC @ 3A
* Mechanical: 3.5mm OD / 1.35mm ID, Barrel jack
* USB-C 15W PD quickcharge
* Only use one power input at a time, barrel jack OR USB-C

== LEDs ==
In total there are four LEDs on the Pinebook Pro, three of which are placed in the top left side of the keyboard, and one near the barrel-port:

:1. The red LED next to the barrel-port indicates charging. It will illuminate when mains power is supplied to the Pinebook Pro from either the standard power supply unit or a USB-C smartphone charger.

:2. The power indicator LED on the Pinebook Pro supports three different colours: green, amber and red. It is also capable of flashing/blinking to indicate activity. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused).

:3. The Num lock, green LED.

:4. The Caps lock, green LED.

(The Num and Caps lock LEDs have a secondary function. When the privacy switches get activated they blink to confirm that switch has been activated.)

== Webcam ==
* 1080p resolution
* Some people test with the application Cheese
WIP

== Microphones ==
WIP

== Bluetooth and WiFi ==
WIP

== LCD Panel ==
* 1080p resolution
WIP

== Using the UART ==
[[File:PBPUART.jpeg|400px|thumb|right|Headphone Jack UART wiring reference]]

UART output is enabled by flipping the UART switch to the ON position (item 9). To do so you need to remove the Pinebook Pro's bottom cover - please follow [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly proper disassembly and reassembly protocol]. The OFF position is towards the touchpad, the ON position is towards the display hinges.

With the UART switch in the ON position, console is relayed via the audiojack and the laptop's sound is turned OFF. PINE64 store sells [https://store.pine64.org/?product=pinebook-serial-console a dedicated serial console] but you can make your own if you have a serial console USB 2.0 adapter and old/ broken headphones. If you do make your own cable, please ensure that you are using a 3.3v interface (such as the CH340, FTDI-232R or PL2303 - which are often sold in 3.3v and 5v variants) to avoid damage to the CPU.

Insert the USB plug of the cable into an open USB port on the machine which will monitor. Run the following in a terminal:

<code>
$ lsusb
</code>

you should find a line similar to this:

<code>
Bus 001 Device 058: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
</code>

You may have to clean the USB contacts of the Serial cable to get a good connection if you do not find that line.

The audio jack of the Serial cable should be fully inserted into the Pinebook Pro audio port.

Serial output should now be accessible using screen, picocom or minicom (and others).
Examples:

<code>
screen /dev/ttyUSB0 1500000

picocom /dev/ttyUSB0 -b 1500000

minicom -D /dev/ttyUSB0 -b 1500000</code>

Current versions of u-Boot do not use the UART for console output. The console function is activated by the Linux kernel. Thus, if you use a non-Pinebook Pro Linux distro and want the UART as a console, you have to manually enable it.

== Using the optional NVMe adapter ==
The optional NVMe adapter allows the use of M.2 cards that support the NVMe standard, (but not SATA standard).

=== Installing the adapter ===

The v2.1 SSD adapter that is shipped with the initial Pinebook Pro batches has a couple of problems although with a little hacking they can still be used. There is [https://forum.pine64.org/showthread.php?tid=8322&pid=52700#pid52700 an unofficial tutorial on the forums] describing the mods.

=== Using as data drive ===
As long as the kernel in use has both the PCIe and NVMe drivers, you should be able to use a NVMe drive as a data drive. Even automounting at boot, (from eMMC or SD card). This applies to both Linux and FreeBSD, though Android or Chromium OS may need testing. Simply use the normal partitioning and file system creation tools.

=== Using as OS root drive ===
It is not possible to boot directly off a NVMe drive. The SoC does not include the NVMe boot code, thus the NVMe is not in the SoC's boot order.

Howevever, it is possible to initially boot off an eMMC or SD card, then transfer to a root file system on the NVMe. Even have all the other file systems on the NVMe. except <code>/boot</code>.<br/>
Instructions for doing this are not complete as of 2019/11/20, but the forums has had people doing this with successful results.

== Using the PineBook Pro ==

=== Bypass Cables ===
The mainboard features two (disconnected by default) bypass cables that are only to be used with the battery disconnected. The female (10) male (6) ends of the bypass cables can be connected to provide power to the mainboard if you need to run the laptop without a battery. Please refer to this [http://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf engineering notice].

WARNING: Do not connect the bypass cables with the battery connected. Using the bypass cables with the battery connected can permanently damage the computer.

=== [[Pinebook_Service_Step_by_Step_Guides|Pinebook Service Step-by-Step Guides]] ===
<span style="color:#FF0000">Placeholder for Pinebook Pro specific guides</span>

Under [[Pinebook_Service_Step_by_Step_Guides|'Service Guides for Pinebook']] you can find instructions guides concerning disassembly of:

'''Note: The installation process on Pinebook Pro similar to 14" Pinebook'''

'''Note: The installation process is the reverse order of removal guide'''

* 14″ Pinebook Lithium Battery Pack Removal Guide
* 14″ Pinebook LCD Panel Screen Removal Guide
* 14″ Pinebook eMMC Module Removal Guide

= Technical Reference =

== Accessing the Internals - Disassembly and Reassembly ==
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]

'''WARNING:''' Do not open the laptop by lifting the lid while the Pinebook Pro bottom cover is removed - this can cause structural damage to the hinges and/or other plastic components of the chassis such as the IO port cut-outs.

'''WARNING:''' When removing the back cover plate, use care if sliding fingertips between back cover plate and palm rest assembly. The back cover plate edges are sharp.

When disassembling the laptop make sure that it is powered off and folded closed. To remove the bottom cover of the Pinebook Pro, first remove the ten (10) Phillips head screws that hold the bottom section of the laptop in place. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis.

During reassembly, make sure that the back-screw standoffs are in place and seated correctly. To reassemble the Pinebook Pro, slide the bottom section into place so it meets the front lip of the keyboard section. Secure the front section (where the trackpad is located) in place using the short screws in the front left and right corners. Then proceed to pop in the bottom panel into place. Secure the bottom section (where hinges are located) by screwing in the left and right corners. Then screw in the remaining screws and run your finger though the rim on the chassis to make sure its fitted correctly. Note that the front uses the remaining 2 short screws.

NOTE: The screws are small and should only be finger tight. Too much force will strip the threads. If after installing screws the back cover plate has not seated properly on one side, open the display and hold the base on either side of the keyboard and gently flex the base with both hands in opposing directions. Once the side pops further in, then recheck the screws on that side. If it does not pop back in, just let it be.

== Pinebook Pro Internal Layout ==

=== Main chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM (21)
* SPI NOR flash memory (29)
* eMMC flash memory (26)
* WiFi/BT module (27)

=== Mainboard Switches and Buttons ===
There are two switches on the main board: disabling the eMMC (24), and enabling UART (9) via headphone jack.

The Reset and Recovery buttons (28): the reset button performs an immediate reset of the laptop. The Recovery button is used to place the device in maskrom mode; this mode allows flashing eMMC using Rockchip tools (e.g. rkflashtools).

[[File:PBPL_S.jpg]]

=== Key Internal Parts ===
{| class="wikitable"
|+ Numbered parts classification and description
! Number
! Type
! Descriptor
|-
! scope=row | 1
| Component || RK3399 System-On-Chip
|-
! scope=row | 2
| Socket || PCIe 4X socket for optional NVMe adapter
|-
! scope=row | 3
| Socket || Speakers socket
|-
! scope=row | 4
| Socket || Trackpad socket
|-
! scope=row | 5
| Component || Left speaker
|-
! scope=row | 6
| Connector || Male power bridge connector
|-
! scope=row | 7
| Socket || Keyboard Socket
|-
! scope=row | 8
| Component || Optional NVMe SSD adapter
|-
! scope=row | 9
| Switch || UART/Audio switch - outputs UART via headphone jack
|-
! scope=row | 10
| Socket || Female power bridge socket
|-
! scope=row | 11
| Socket || Battery socket
|-
! scope=row | 12
| Component || Trackpad
|-
! scope=row | 13
| Component || Battery
|-
! scope=row | 14
| Component || Right speaker
|-
! scope=row | 15
| Socket || Micro SD socket
|-
! scope=row | 16
| Socket || Headphone / UART jack
|-
! scope=row | 17
| Socket || USB 2.0
|-
! scope=row | 18
| Socket || Daughterboard-to-mainboard ribbon cable socket
|-
! scope=row | 19
| Cable || Daughterboard-to-mainboard ribbon cable
|-
! scope=row | 20
| Component || microphone
|-
! scope=row | 21
| Component || LPDDR4 RAM
|-
! scope=row | 22
| Socket || Mainboard-to-daughterboard ribbon cable socket
|-
! scope=row | 23
| Socket || Microphone socket
|-
! scope=row | 24
| Switch || Switch to hardware disable eMMC
|-
! scope=row | 25
| Antenna || BT/WiFI antenna
|-
! scope=row | 26
| Component || eMMC flash memory module
|-
! scope=row | 27
| Component ||BT/WiFi module chip
|-
! scope=row | 28
| Buttons || Reset and recovery buttons
|-
! scope=row | 29
| Component || SPI flash storage
|-
! scope=row | 30
| Socket || eDP LCD socket
|-
! scope=row | 31
| Socket || Power in barrel socket
|-
! scope=row | 32
| Socket || USB 3.0
|-
! scope=row | 33
| Socket || USB type C
|}

== Bootable Storage ==

The Pinebook Pro is capable of booting from eMMC, USB 2.0, USB 3.0, or an SD card. It cannot boot from USB-C. The boot order of the hard-coded ROM of its RK3399 SoC is: SPI NOR, eMMC, SD, USB OTG.

At this time, the Pinebook Pro ships with a Debian + MATE build with [https://www.denx.de/wiki/U-Boot/ uboot] on the eMMC. Its boot order is: SD, then eMMC. Booting off USB storage is not currently available, but will be in the future.

(An update has been pushed for the default Debian + MATE build that improves compatibility with booting other OSs from an SD card. In order to update, fully charge the battery, establish an internet connection, click the update icon in the toolbar, and then reboot your Pinebook Pro. Please see [https://forum.pine64.org/showthread.php?tid=7830 this log] for details.)

Please note that PCIe, the interface used for NVMe SSD on the Pinebook Pro, is not bootable on the RK3399 and therefore is not a part of the boot hierarchy. It is possible to run the desired OS from NVMe by pointing extlinux on the eMMC to rootfs on the SSD. This requires uboot, the Kernel image, DTB, and extlinux.conf
in a /boot partition on the eMMC.

=== eMMC information ===

The eMMC storage will show up as multiple block devices:
*mmcblk1boot0 - eMMC standard boot0 partition, may be 4MB
*mmcblk1boot1 - eMMC standard boot1 partition, may be 4MB
*mmcblk1rpmb - eMMC standard secure data partition. may be 16MB
*mmcblk1 - This block contains the user areas

Only the last is usable as regular storage device in the Pinebook Pro.
The device number of "1" shown above may vary, depending on kernel.

=== Boot sequence details ===

The RK3399's mask 32KB ROM boot code looks for the next stage of code at byte off-set 32768. This is where u-Boot code would reside on any media that is bootable.

== Pinebook Pro Dimensions ==
* Dimensions: 329mm x 220mm x 12mm (WxDxH)
* Weight: 1.26Kg

== SoC and Memory Specification ==
[[File:Rockchip_RK3399.png|right]]
* Based on Rockchip RK3399

=== CPU Architecture ===
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
** Full implementation of the ARM architecture v8-A instruction set (both AArch64 and AArch32)
** ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
** ARMv8 Cryptography Extensions
** VFPv4 floating point unit supporting single and double-precision operations
** Hardware virtualization support
** TrustZone technology support
** Full CoreSight debug solution
** One isolated voltage domain to support DVFS
* Cortex-A72 (big cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
** Superscalar, variable-length, out-of-order pipeline
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
* Cortex-A53 (little cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
** In-order pipeline with symmetric dual-issue of most instructions
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Cortex-M0 (control processors):
** [https://developer.arm.com/ip-products/processors/cortex-m/cortex-m0 Cortex-M0 CPU]
** Two Cortex-M0 cooperate with the central processors
** Architecture: Armv6-M
** Thumb/Thumb2 instruction set
** 32 bit only

=== GPU Architecture ===
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provide stunning visuals for UHD content.
* Frequency 650MHz
* Throughput 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2., Vulkan 1.0*., OpenCL™ 1.1, 1.2., DirectX® 11 FL11_1., RenderScript™.

=== System Memory ===
* RAM Memory:
** LPDDR4
** Dual memory channels on the CPU, each 32 bits wide
** Quad memory channels on the RAM chip, each 16 bits wide, 2 bonded together for each CPU channel
** 4GB as a single 366 pin mobile RAM chip
* Storage Memory:
** 64GB eMMC module, can be upgraded to a 128GB eMMC module. (The initial PINE64 community build version shipped with a 128GB eMMC.)

=== Battery ===
* Lithium Polymer Battery (10,000 mAH)

=== Display ===
* 14.1" 1920x1080 IPS LCD panel

=== Video out ===
* USB-C Alt mode DP up to 3840x2160 p60

=== Audio ===
* 3.5mm stereo earphone/microphone plug
* Build in stereo speakers

=== Network ===
* WiFi:
** 802.11 b/g/n/ac
** Dual band: 2.4Ghz & 5Ghz
** Single antenna
* Bluetooth 5.0

=== Expansion Ports ===
* MicroSD card:
** Bootable
** Supports SD, SDHC and SDXC cards, up to 256GB
** Version SD3.0, up to 50MB/s
* USB ports:
** 1 x USB 2.0 Type-A Host Port, bootable
** 1 x USB 3.0 Type-A Host Port, 5Gbps, is not bootable
** 1 x USB 3.0 Type-C OTG Port, 5Gbps, (includes laptop charging function), is not bootable
* Headphone jack switchable to UART console mux circuit
* Optional NVMe adapter:
** PCIe 2.x, 5GT/s per lane
** 4 PCIe lanes, can not be bifurcated, (however, can be used with 1 or 2 lane NVMe cards)
** Maximum length for M.2 card is 80mm (M.2 2280)
** Power: 2.5W continuous, 8.25W peak momentary
** Does not support SATA M.2 cards
** Does not support USB M.2 cards

== Pinebook Pro Schematics and Certifications ==
* Pinebook Pro Main Board Schematic And Silkscreen:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_mainboard_schematic.pdf Pinebook Pro Main Board ver 2.1 Schematic]
** [https://wiki.pine64.org/images/3/30/Pinebookpro-v2.1-top-ref.pdf Pinebook Pro ver 2.1 Top Layer Silkscreen]
** [https://wiki.pine64.org/images/b/b7/Pinebookpro-v2.1-bottom-ref.pdf Pinebook Pro ver 2.1 Bottom Layer Silkscreen]
* Pinebook Pro Daughter Board Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_daughterboard_schematic.pdf Pinebook Pro Daughter Board ver 2.1 Schematic]
* Optional Pinebook Pro NVMe Adapter Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_NVMe-adapter_schematic.pdf Pinebook Pro NVMe Adapter Board ver 2.1 Schematic]
* Serial Console Earphone Jack Pinout:
** [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinkbook Serial Console Earphone Jack Pinout]
* Pinebook Pro Certifications:
** Not Yet Available

== Datasheets for Components and Peripherals ==
* Rockchip RK3399 SoC information:
** [http://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [http://opensource.rock-chips.com/images/2/28/Rockchip_RK3399_Datasheet_V1.8-20180529.pdf Rockchip RK3399 Datasheet V1.8]
** [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
** [http://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (366 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 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 SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [http://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Wireless related info:
** [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]
* Audio Codec (ES8316)
** [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]
* LCD Panel:
** [http://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]
* Touchpad information:
** [http://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf Touchpad Specification for Pinebook Pro model]
* Keyboard information:
** [http://www.sinowealth.com/ftp/ph/SH68F83/SH68F83V2.0.pdf Sinowealth SH68F83 Datasheet]
** US ANSI: XK-HS002 MB27716023
* Full HD Camera sensor:
** [http://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification in Chinese]
** [http://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Data Sheet]
* Lithium Battery information:
** [http://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification for 14" model]

= Troubleshooting guide =
Tips, tricks and other information for troubleshooting your Pinebook Pro
=== New from the factory - Pinebook Pro won't boot / power on ===
* Some Pinebook Pros came from the factory with the eMMC switch in the disabled position. It should be switched towards the back / hinge to enable the eMMC.<br>
* The eMMC may have come loose during shipment. [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly Open] the back and verify that the eMMC is firmly seated.<br>
* You may want to try unplugging the SD card daughterboard ribbon cable and see if it powers on (remove the battery and peel off a bit of the tape before unplugging it to avoid damage). If it does, try reseating it on both sides. It might have come loose during shipping.
* It's possible that your eMMC is empty from the factory. Simply create a bootable SD card and see if your Pinebook Pro boots. If so, you can then write an OS image to the eMMC.

=== Pinebook Pro won't boot when using UART console cable ===
* If you're using the UART cable sold on the Pine Store, you may want to see if it boots after you disconnect it. Some users report that custom-made cables based on FTDI UART adapters do not cause this issue.

=== Pinebook Pro will not power on after toggling the eMMC enable/disable switch ===
* This may happen if you meant to toggle the UART/Headphone switch (9) towards touchpad for headphone use and instead you toggled the eMMC enable/disable switch (24).
* After reenabling eMMC by toggling switch (24) towards hinge, if Pinebook Pro does not turn on then press the RESET button (28). It is clearly marked 'reset' on the PCB board.

=== Keys not registering / missing keys when typing ===
This issue occurs when your thumb or edge of the palm makes contact with left or right tip of the trackpad when you type. This is due to the palm rejection firmware being too forceful. Instead of only disabling the trackpad, so your cursor does not move all over the screen, it disables both the trackpad and the keyboard.

Using Fn+F7 to disable the touchpad will keep it from also disabling the keyboard.

[https://forum.pine64.org/showthread.php?tid=8030 A firmware update is planned] to address this.

=== WiFi issues ===
* First, check the privacy switches to make sure your WiFi is enable. They are persistant. See [[Pinebook_Pro_Main_Page#Privacy_Switches]]
* Next, you may have to modify the file "/etc/NetworkManager/NetworkManager.conf" as user "root", and replace "managed=false" with "managed=true". Then reboot.

=== Accessory Hardware Compatibility ===

[[PBP_HW_Compatibiity|PineBookPro Hardware Compatibility]]

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=111 Pinebook Pro Forum]
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [[RockPro64 Guides]]
* [http://www.pine64.xyz:9090/?channels=ROCK64 ROCK64/ROCKPro64 IRC Channel]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]

Pinebook Pro

2019-11-23T06:07:00Z

Ferenc: /* Trackpad */ Link to "Datasheets for Components and Peripherals"

= User Guide =

== Introducing PineBook Pro ==
[[File:PBP.jpg|400px|thumb|right|Pinebook Pro running stock Debian with MATE]]

The Pinebook Pro is a Linux and *BSD ARM laptop from [https://www.pine64.org/ PINE64]

It is built to be a compelling alternative to mid-ranged Chromebooks that people convert into Linux laptops. It features an IPS 1080p 14″ LCD panel, a premium magnesium alloy shell, high capacity eMMC storage, a 10,000 mAh capacity battery, and the modularity that only an open source project can deliver.

Key features include: the RK3399 SOC; USB-C for data, video-out and power-in (3A 5V); privacy switches for the microphone, BT/WiFi module, and camera; and expandable storage via NVMe (PCIe 4x) with an optional adapter.

The Pinebook Pro is equipped with 4GB LPDDR4 system memory, high capacity eMMC flash storage, and 128Mb SPI boot Flash. The I/O includes: 1x micro SD card reader (bootable), 1x USB 2.0, 1x USB 3.0, 1x USB type C Host with DP 1.2 and power-in, PCIe 4x for an NVMe SSD drive (requires an optional adapter), and UART (via the headphone jack by setting an internal switch).

The keyboard and trackpad both use the USB 2.0 protocol. The LCD panel uses eDP MiPi display protocol.

Many different Operating Systems (OS) are freely available from the open source community and partner projects. These include various flavors of Linux (Ubuntu, Debian, Manjaro, etc.) and *BSD.

== Software and OS Image Downloads ==
=== [[Pinebook Pro_Software_Release|Pinebook Pro]] ===
Under [[Pinebook Pro Software Release|'Pinebook Pro Software and OS Image Download Section']] you will find a complete list of currently supported Operating System images that work with the Pinebook as well as other related software.

The list includes OS images and descriptions of:
* [{{fullurl:PinebookPro_Software_Release#Debian_Desktop}} http://files.pine64.org/sw/pine64_installer/json/debian.png] [[PinebookPro_Software_Release#Debian Desktop|'''Debian Desktop (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Bionic_LXDE}} http://files.pine64.org/sw/pine64_installer/json/lxde.png] [[PinebookPro_Software_Release#Bionic LXDE|'''Bionic LXDE (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Bionic_Mate}} http://files.pine64.org/sw/pine64_installer/json/mate.png] [[PinebookPro_Software_Release#Bionic Mate|'''Bionic Mate (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Chromium}} http://files.pine64.org/sw/pine64_installer/json/chromium.jpg] [[PinebookPro_Software_Release#Chromium|'''Chromium (microSD and eMMC Boot)''']]
* [{{fullurl:PinebookPro_Software_Release#Android_7.1_microSD}} http://files.pine64.org/sw/pine64_installer/json/android_7.png] [[PinebookPro_Software_Release#Android_7.1_microSD|'''Android 7.1 (microSD Boot)''']]           [{{fullurl:PinebookPro_Software_Release#Android_7.1_eMMC}} http://files.pine64.org/sw/pine64_installer/json/android_7.png] [[PinebookPro_Software_Release#Android_7.1_eMMC|'''Android 7.1 (eMMC)''']]

----

=== Quick Links to OS Images Build Sources===
'''Some of the provided OS images are still in <span style="color:#FF0000">beta or nightly build</span> and only fit for testing purposes. These images ought to be avoided for normal usage - use them at <span style="color:#FF0000">your own risk</span>'''
* [https://github.com/ayufan-rock64/linux-build/releases/ ayufan's Linux build repo]
* [https://github.com/ayufan-rock64/chromiumos-build/releases ayufan's Chromium OS build repo]
* [https://github.com/mrfixit2001/debian_desktop/releases mrfixit2001's Linux debian desktop build repo]

== Keyboard ==
The Pinebook Pro is available in two keyboard configurations: ISO and ANSI. Both the keyboard and trackpad in the Pinebook Pro use the USB 2.0 protocol and show up as such in xinput. The keyboard features function (Fn) keys in the F-key row, which include display brightness controls, sound volume, trackpad lock, and other functionality. There is also a custom PINE64 logo key that functions as Menu/Super key. It has also a secondary functionality for setting the privacy switches.

The keyboard firmware is open sourced can be flashed from userspace using the provided utility.

Documentation for the keyboard can be found in Datasheets for Components and Peripherals.

=== Typing special characters ===
The UK ISO Layout does not have dedicated keys for characters like the German umlauts (Ä,Ö,Ü, etc). Certain characters can still be generated by means of either key combinations or key sequences.
{| class="wikitable"
!Character
!Key combination/sequence
|-
|Ä, Ö, Ü, ä, ö, ü
|[[Wikipedia:AltGr_key|[AltGr]]]+["] followed by [A], [O], [U], [a], [o] or [u]
|-
|µ
|[AltGr]+[m]
|-
|Ø, ø
|[AltGr]+[O], [AltGr]+[o]
|-
|@
|[AltGr]+[q] (as on the German layout)
|-
|ß
|[AltGr]+[s]
|-
|§
|[AltGr]+[S]
|-
|°
|[AltGr]+[)]
|}

=== Privacy Switches ===
There are three privacy switches mapped to the F10, F11 and F12 keys on the Pinebook Pro keyboard. They de/activate the following:

{| class="wikitable"
|+ Privacy switch function and description
! Combination
! Effect
! Description
|-
! scope=row | PINE64 logo key+F10
| Microphone Privacy switch || CAPs lock LED blinks. 2 blinks = enabled, 3 blinks = disabled
|-
! scope=row | PINE64 logo key+F11
| WiFi Privacy switch || NUM lock LED blinks. 2 blinks = enabled, 3 blinks = disabled. '''Re-enabling requires reboot''' (or a [//forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645 command line hack to bind/unbind]).
|-
! scope=row | PINE64 logo key+F12
| Camera privacy switch || CAPs lock and NUM lock LEDs blink together. 2 blinks = enabled, 3 blinks = disabled
|}

'''(Press the PINE64 logo key plus Fn (10/11/12) for 3 seconds)'''

The keyboard uses special firmware that operates separately of the operating system. It detects if either the F10, F11 or F12 key, and the Pine key were pressed for 3 seconds. This disables the peripherals as listed above by cutting off their power. Which has the same result as cutting off the power to each peripheral with a physical switch. This implementation is very secure since the firmware that determines whether a peripheral gets power is not a part of the Pinebook Pro’s operating system. So the power state value for each peripheral cannot be overridden or accessed from the operating system. The power state setting for each peripheral is stored across reboots.

== Trackpad ==

The trackpad is large, smooth (metallic to-the-touch), and has two actuating buttons. It is the only component of the Pinebook Pro held in place with strong adhesive tape. It supports multi-touch functionality.

The trackpad firmware is open sourced and can be flashed from userspace using the provided utility (https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater).

Documentation for the trackpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].

== Power Supply ==
* Input Power: 5V DC @ 3A
* Mechanical: 3.5mm OD / 1.35mm ID, Barrel jack
* USB-C 15W PD quickcharge
* Only use one power input at a time, barrel jack OR USB-C

== LEDs ==
In total there are four LEDs on the Pinebook Pro, three of which are placed in the top left side of the keyboard, and one near the barrel-port:

:1. The red LED next to the barrel-port indicates charging. It will illuminate when mains power is supplied to the Pinebook Pro from either the standard power supply unit or a USB-C smartphone charger.

:2. The power indicator LED on the Pinebook Pro supports three different colours: green, amber and red. It is also capable of flashing/blinking to indicate activity. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused).

:3. The Num lock, green LED.

:4. The Caps lock, green LED.

(The Num and Caps lock LEDs have a secondary function. When the privacy switches get activated they blink to confirm that switch has been activated.)

== Webcam ==
* 1080p resolution
* Some people test with the application Cheese
WIP

== Microphones ==
WIP

== Bluetooth and WiFi ==
WIP

== LCD Panel ==
* 1080p resolution
WIP

== Using the UART ==
[[File:PBPUART.jpeg|400px|thumb|right|Headphone Jack UART wiring reference]]

UART output is enabled by flipping the UART switch to the ON position (item 9). To do so you need to remove the Pinebook Pro's bottom cover - please follow [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly proper disassembly and reassembly protocol]. The OFF position is towards the touchpad, the ON position is towards the display hinges.

With the UART switch in the ON position, console is relayed via the audiojack and the laptop's sound is turned OFF. PINE64 store sells [https://store.pine64.org/?product=pinebook-serial-console a dedicated serial console] but you can make your own if you have a serial console USB 2.0 adapter and old/ broken headphones. If you do make your own cable, please ensure that you are using a 3.3v interface (such as the CH340, FTDI-232R or PL2303 - which are often sold in 3.3v and 5v variants) to avoid damage to the CPU.

Insert the USB plug of the cable into an open USB port on the machine which will monitor. Run the following in a terminal:

<code>
$ lsusb
</code>

you should find a line similar to this:

<code>
Bus 001 Device 058: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
</code>

You may have to clean the USB contacts of the Serial cable to get a good connection if you do not find that line.

The audio jack of the Serial cable should be fully inserted into the Pinebook Pro audio port.

Serial output should now be accessible using screen, picocom or minicom (and others).
Examples:

<code>
screen /dev/ttyUSB0 1500000

picocom /dev/ttyUSB0 -b 1500000

minicom -D /dev/ttyUSB0 -b 1500000</code>

Current versions of u-Boot do not use the UART for console output. The console function is activated by the Linux kernel. Thus, if you use a non-Pinebook Pro Linux distro and want the UART as a console, you have to manually enable it.

== Using the optional NVMe adapter ==
The optional NVMe adapter allows the use of M.2 cards that support the NVMe standard, (but not SATA standard).

=== Installing the adapter ===

The v2.1 SSD adapter that is shipped with the initial Pinebook Pro batches has a couple of problems although with a little hacking they can still be used. There is [https://forum.pine64.org/showthread.php?tid=8322&pid=52700#pid52700 an unofficial tutorial on the forums] describing the mods.

=== Using as data drive ===
As long as the kernel in use has both the PCIe and NVMe drivers, you should be able to use a NVMe drive as a data drive. Even automounting at boot, (from eMMC or SD card). This applies to both Linux and FreeBSD, though Android or Chromium OS may need testing. Simply use the normal partitioning and file system creation tools.

=== Using as OS root drive ===
It is not possible to boot directly off a NVMe drive. The SoC does not include the NVMe boot code, thus the NVMe is not in the SoC's boot order.

Howevever, it is possible to initially boot off an eMMC or SD card, then transfer to a root file system on the NVMe. Even have all the other file systems on the NVMe. except <code>/boot</code>.<br/>
Instructions for doing this are not complete as of 2019/11/20, but the forums has had people doing this with successful results.

== Using the PineBook Pro ==

=== Bypass Cables ===
The mainboard features two (disconnected by default) bypass cables that are only to be used with the battery disconnected. The female (10) male (6) ends of the bypass cables can be connected to provide power to the mainboard if you need to run the laptop without a battery. Please refer to this [http://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf engineering notice].

WARNING: Do not connect the bypass cables with the battery connected. Using the bypass cables with the battery connected can permanently damage the computer.

=== [[Pinebook_Service_Step_by_Step_Guides|Pinebook Service Step-by-Step Guides]] ===
<span style="color:#FF0000">Placeholder for Pinebook Pro specific guides</span>

Under [[Pinebook_Service_Step_by_Step_Guides|'Service Guides for Pinebook']] you can find instructions guides concerning disassembly of:

'''Note: The installation process on Pinebook Pro similar to 14" Pinebook'''

'''Note: The installation process is the reverse order of removal guide'''

* 14″ Pinebook Lithium Battery Pack Removal Guide
* 14″ Pinebook LCD Panel Screen Removal Guide
* 14″ Pinebook eMMC Module Removal Guide

= Technical Reference =

== Accessing the Internals - Disassembly and Reassembly ==
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]

'''WARNING:''' Do not open the laptop by lifting the lid while the Pinebook Pro bottom cover is removed - this can cause structural damage to the hinges and/or other plastic components of the chassis such as the IO port cut-outs.

'''WARNING:''' When removing the back cover plate, use care if sliding fingertips between back cover plate and palm rest assembly. The back cover plate edges are sharp.

When disassembling the laptop make sure that it is powered off and folded closed. To remove the bottom cover of the Pinebook Pro, first remove the ten (10) Phillips head screws that hold the bottom section of the laptop in place. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis.

During reassembly, make sure that the back-screw standoffs are in place and seated correctly. To reassemble the Pinebook Pro, slide the bottom section into place so it meets the front lip of the keyboard section. Secure the front section (where the trackpad is located) in place using the short screws in the front left and right corners. Then proceed to pop in the bottom panel into place. Secure the bottom section (where hinges are located) by screwing in the left and right corners. Then screw in the remaining screws and run your finger though the rim on the chassis to make sure its fitted correctly. Note that the front uses the remaining 2 short screws.

NOTE: The screws are small and should only be finger tight. Too much force will strip the threads. If after installing screws the back cover plate has not seated properly on one side, open the display and hold the base on either side of the keyboard and gently flex the base with both hands in opposing directions. Once the side pops further in, then recheck the screws on that side. If it does not pop back in, just let it be.

== Pinebook Pro Internal Layout ==

=== Main chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM (21)
* SPI NOR flash memory (29)
* eMMC flash memory (26)
* WiFi/BT module (27)

=== Mainboard Switches and Buttons ===
There are two switches on the main board: disabling the eMMC (24), and enabling UART (9) via headphone jack.

The Reset and Recovery buttons (28): the reset button performs an immediate reset of the laptop. The Recovery button is used to place the device in maskrom mode; this mode allows flashing eMMC using Rockchip tools (e.g. rkflashtools).

[[File:PBPL_S.jpg]]

=== Key Internal Parts ===
{| class="wikitable"
|+ Numbered parts classification and description
! Number
! Type
! Descriptor
|-
! scope=row | 1
| Component || RK3399 System-On-Chip
|-
! scope=row | 2
| Socket || PCIe 4X socket for optional NVMe adapter
|-
! scope=row | 3
| Socket || Speakers socket
|-
! scope=row | 4
| Socket || Trackpad socket
|-
! scope=row | 5
| Component || Left speaker
|-
! scope=row | 6
| Connector || Male power bridge connector
|-
! scope=row | 7
| Socket || Keyboard Socket
|-
! scope=row | 8
| Component || Optional NVMe SSD adapter
|-
! scope=row | 9
| Switch || UART/Audio switch - outputs UART via headphone jack
|-
! scope=row | 10
| Socket || Female power bridge socket
|-
! scope=row | 11
| Socket || Battery socket
|-
! scope=row | 12
| Component || Trackpad
|-
! scope=row | 13
| Component || Battery
|-
! scope=row | 14
| Component || Right speaker
|-
! scope=row | 15
| Socket || Micro SD socket
|-
! scope=row | 16
| Socket || Headphone / UART jack
|-
! scope=row | 17
| Socket || USB 2.0
|-
! scope=row | 18
| Socket || Daughterboard-to-mainboard ribbon cable socket
|-
! scope=row | 19
| Cable || Daughterboard-to-mainboard ribbon cable
|-
! scope=row | 20
| Component || microphone
|-
! scope=row | 21
| Component || LPDDR4 RAM
|-
! scope=row | 22
| Socket || Mainboard-to-daughterboard ribbon cable socket
|-
! scope=row | 23
| Socket || Microphone socket
|-
! scope=row | 24
| Switch || Switch to hardware disable eMMC
|-
! scope=row | 25
| Antenna || BT/WiFI antenna
|-
! scope=row | 26
| Component || eMMC flash memory module
|-
! scope=row | 27
| Component ||BT/WiFi module chip
|-
! scope=row | 28
| Buttons || Reset and recovery buttons
|-
! scope=row | 29
| Component || SPI flash storage
|-
! scope=row | 30
| Socket || eDP LCD socket
|-
! scope=row | 31
| Socket || Power in barrel socket
|-
! scope=row | 32
| Socket || USB 3.0
|-
! scope=row | 33
| Socket || USB type C
|}

== Bootable Storage ==

The Pinebook Pro is capable of booting from eMMC, USB 2.0, USB 3.0, or an SD card. It cannot boot from USB-C. The boot order of the hard-coded ROM of its RK3399 SoC is: SPI NOR, eMMC, SD, USB OTG.

At this time, the Pinebook Pro ships with a Debian + MATE build with [https://www.denx.de/wiki/U-Boot/ uboot] on the eMMC. Its boot order is: SD, then eMMC. Booting off USB storage is not currently available, but will be in the future.

(An update has been pushed for the default Debian + MATE build that improves compatibility with booting other OSs from an SD card. In order to update, fully charge the battery, establish an internet connection, click the update icon in the toolbar, and then reboot your Pinebook Pro. Please see [https://forum.pine64.org/showthread.php?tid=7830 this log] for details.)

Please note that PCIe, the interface used for NVMe SSD on the Pinebook Pro, is not bootable on the RK3399 and therefore is not a part of the boot hierarchy. It is possible to run the desired OS from NVMe by pointing extlinux on the eMMC to rootfs on the SSD. This requires uboot, the Kernel image, DTB, and extlinux.conf
in a /boot partition on the eMMC.

=== eMMC information ===

The eMMC storage will show up as multiple block devices:
*mmcblk1boot0 - eMMC standard boot0 partition, may be 4MB
*mmcblk1boot1 - eMMC standard boot1 partition, may be 4MB
*mmcblk1rpmb - eMMC standard secure data partition. may be 16MB
*mmcblk1 - This block contains the user areas

Only the last is usable as regular storage device in the Pinebook Pro.
The device number of "1" shown above may vary, depending on kernel.

=== Boot sequence details ===

The RK3399's mask 32KB ROM boot code looks for the next stage of code at byte off-set 32768. This is where u-Boot code would reside on any media that is bootable.

== Pinebook Pro Dimensions ==
* Dimensions: 329mm x 220mm x 12mm (WxDxH)
* Weight: 1.26Kg

== SoC and Memory Specification ==
[[File:Rockchip_RK3399.png|right]]
* Based on Rockchip RK3399

=== CPU Architecture ===
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
** Full implementation of the ARM architecture v8-A instruction set (both AArch64 and AArch32)
** ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
** ARMv8 Cryptography Extensions
** VFPv4 floating point unit supporting single and double-precision operations
** Hardware virtualization support
** TrustZone technology support
** Full CoreSight debug solution
** One isolated voltage domain to support DVFS
* Cortex-A72 (big cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
** Superscalar, variable-length, out-of-order pipeline
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
* Cortex-A53 (little cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
** In-order pipeline with symmetric dual-issue of most instructions
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Cortex-M0 (control processors):
** [https://developer.arm.com/ip-products/processors/cortex-m/cortex-m0 Cortex-M0 CPU]
** Two Cortex-M0 cooperate with the central processors
** Architecture: Armv6-M
** Thumb/Thumb2 instruction set
** 32 bit only

=== GPU Architecture ===
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provide stunning visuals for UHD content.
* Frequency 650MHz
* Throughput 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2., Vulkan 1.0*., OpenCL™ 1.1, 1.2., DirectX® 11 FL11_1., RenderScript™.

=== System Memory ===
* RAM Memory:
** LPDDR4
** Dual memory channels on the CPU, each 32 bits wide
** Quad memory channels on the RAM chip, each 16 bits wide, 2 bonded together for each CPU channel
** 4GB as a single 366 pin mobile RAM chip
* Storage Memory:
** 64GB eMMC module, can be upgraded to a 128GB eMMC module. (The initial PINE64 community build version shipped with a 128GB eMMC.)

=== Battery ===
* Lithium Polymer Battery (10,000 mAH)

=== Display ===
* 14.1" 1920x1080 IPS LCD panel

=== Video out ===
* USB-C Alt mode DP up to 3840x2160 p60

=== Audio ===
* 3.5mm stereo earphone/microphone plug
* Build in stereo speakers

=== Network ===
* WiFi:
** 802.11 b/g/n/ac
** Dual band: 2.4Ghz & 5Ghz
** Single antenna
* Bluetooth 5.0

=== Expansion Ports ===
* MicroSD card:
** Bootable
** Supports SD, SDHC and SDXC cards, up to 256GB
** Version SD3.0, up to 50MB/s
* USB ports:
** 1 x USB 2.0 Type-A Host Port, bootable
** 1 x USB 3.0 Type-A Host Port, 5Gbps, is not bootable
** 1 x USB 3.0 Type-C OTG Port, 5Gbps, (includes laptop charging function), is not bootable
* Headphone jack switchable to UART console mux circuit
* Optional NVMe adapter:
** PCIe 2.x, 5GT/s per lane
** 4 PCIe lanes, can not be bifurcated, (however, can be used with 1 or 2 lane NVMe cards)
** Maximum length for M.2 card is 80mm (M.2 2280)
** Power: 2.5W continuous, 8.25W peak momentary
** Does not support SATA M.2 cards
** Does not support USB M.2 cards

== Pinebook Pro Schematics and Certifications ==
* Pinebook Pro Main Board Schematic And Silkscreen:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_mainboard_schematic.pdf Pinebook Pro Main Board ver 2.1 Schematic]
** [https://wiki.pine64.org/images/3/30/Pinebookpro-v2.1-top-ref.pdf Pinebook Pro ver 2.1 Top Layer Silkscreen]
** [https://wiki.pine64.org/images/b/b7/Pinebookpro-v2.1-bottom-ref.pdf Pinebook Pro ver 2.1 Bottom Layer Silkscreen]
* Pinebook Pro Daughter Board Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_daughterboard_schematic.pdf Pinebook Pro Daughter Board ver 2.1 Schematic]
* Optional Pinebook Pro NVMe Adapter Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_NVMe-adapter_schematic.pdf Pinebook Pro NVMe Adapter Board ver 2.1 Schematic]
* Serial Console Earphone Jack Pinout:
** [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinkbook Serial Console Earphone Jack Pinout]
* Pinebook Pro Certifications:
** Not Yet Available

== Datasheets for Components and Peripherals ==
* Rockchip RK3399 SoC information:
** [http://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [http://opensource.rock-chips.com/images/2/28/Rockchip_RK3399_Datasheet_V1.8-20180529.pdf Rockchip RK3399 Datasheet V1.8]
** [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
** [http://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (366 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 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 SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [http://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Wireless related info:
** [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]
* Audio Codec (ES8316)
** [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]
* LCD Panel:
** [http://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]
* Touchpad information:
** [http://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf Touchpad Specification for Pinebook Pro model]
* Keyboard information:
** [http://www.sinowealth.com/ftp/ph/SH68F83/SH68F83V2.0.pdf Sinowealth SH68F83 Datasheet]
** US ANSI: XK-HS002 MB27716023
* Full HD Camera sensor:
** [http://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification in Chinese]
** [http://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Data Sheet]
* Lithium Battery information:
** [http://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification for 14" model]

= Troubleshooting guide =
Tips, tricks and other information for troubleshooting your Pinebook Pro
=== New from the factory - Pinebook Pro won't boot / power on ===
* Some Pinebook Pros came from the factory with the eMMC switch in the disabled position. It should be switched towards the back / hinge to enable the eMMC.<br>
* The eMMC may have come loose during shipment. [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly Open] the back and verify that the eMMC is firmly seated.<br>
* You may want to try unplugging the SD card daughterboard ribbon cable and see if it powers on (remove the battery and peel off a bit of the tape before unplugging it to avoid damage). If it does, try reseating it on both sides. It might have come loose during shipping.
* It's possible that your eMMC is empty from the factory. Simply create a bootable SD card and see if your Pinebook Pro boots. If so, you can then write an OS image to the eMMC.

=== Pinebook Pro won't boot when using UART console cable ===
* If you're using the UART cable sold on the Pine Store, you may want to see if it boots after you disconnect it. Some users report that custom-made cables based on FTDI UART adapters do not cause this issue.

=== Pinebook Pro will not power on after toggling the eMMC enable/disable switch ===
* This may happen if you meant to toggle the UART/Headphone switch (9) towards touchpad for headphone use and instead you toggled the eMMC enable/disable switch (24).
* After reenabling eMMC by toggling switch (24) towards hinge, if Pinebook Pro does not turn on then press the RESET button (28). It is clearly marked 'reset' on the PCB board.

=== Keys not registering / missing keys when typing ===
This issue occurs when your thumb or edge of the palm makes contact with left or right tip of the trackpad when you type. This is due to the palm rejection firmware being too forceful. Instead of only disabling the trackpad, so your cursor does not move all over the screen, it disables both the trackpad and the keyboard.

Using Fn+F7 to disable the touchpad will keep it from also disabling the keyboard.

[https://forum.pine64.org/showthread.php?tid=8030 A firmware update is planned] to address this.

=== WiFi issues ===
* First, check the privacy switches to make sure your WiFi is enable. They are persistant. See [[Pinebook_Pro_Main_Page#Privacy_Switches]]
* Next, you may have to modify the file "/etc/NetworkManager/NetworkManager.conf" as user "root", and replace "managed=false" with "managed=true". Then reboot.

=== Accessory Hardware Compatibility ===

[[PBP_HW_Compatibiity|PineBookPro Hardware Compatibility]]

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=111 Pinebook Pro Forum]
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [[RockPro64 Guides]]
* [http://www.pine64.xyz:9090/?channels=ROCK64 ROCK64/ROCKPro64 IRC Channel]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]

PineTime RTOS Comparison

2019-11-21T00:15:44Z

Ferenc: Add mynewt with PineTime implementation

{| class="wikitable"
!
! FreeRTOS
! Zephyr
! mynewt
! Tock
! MbedOS
! TinyGo
|-
! Project Homepage
| https://www.freertos.org
| https://www.zephyrproject.org
| https://mynewt.apache.org/about/
| https://www.tockos.org
| https://os.mbed.com
| https://tinygo.org
|-
! Project Source
| https://sourceforge.net/projects/freertos/
| https://github.com/zephyrproject-rtos/zephyr
| https://github.com/apache/mynewt-core
| https://github.com/tock/tock
| https://github.com/ARMmbed/mbed-os
| https://github.com/tinygo-org/tinygo
|-
! Sponsor
| Amazon
| Linux Foundation
| Apache Foundation
|
| ARM
|
|-
! Language
| C
| C
| C
| Rust
| C/C++
| Go
|-
! PineTime Implementations
|
|
|
*https://github.com/lupyuen/stm32bluepill-mynewt-sensor/tree/pinetime
|
|
|
*https://github.com/aykevl/go-smartwatch
|}

PinePhone

2019-11-20T23:32:09Z

Ferenc: /* Modem and Carrier Support */ Add German carriers

The PinePhone is a smartphone created by Pine64, capable of running mainline Linux and supported by many partner projects. A "braveheart" edition is currently available for purchase from the PINE64 store, though it should be noted that this version comes without a preinstalled OS, and is geared specifically towards tinkerers and hackers. People looking for a stable consumer-grade phone should wait for the final release, which is expected to occur in March 2020 and will be available for at least five years.

== Specifications ==

'''Dimensions:''' 160.5 x 76.6 x 9.2mm <br>
'''Weight:''' Between 180-200 grams <br>
'''Build:''' Plastic <br>
'''SIM Card:''' Micro-SIM <br>
'''Display:'''
: '''Size:''' 5.95 inches (151mm) diagonal
: '''Type:''' HD IPS capacitive touchscreen, 16M colors
: '''Resolution:''' 1440x720, 18:9 ratio <br>
'''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64] <br>
'''RAM:''' 2GB LPDDR3 SDRAM <br>
'''Internal Storage:''' 16GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC <br>
'''Back Camera:''' Single 5MP, 1/4", LED Flash <br>
'''Selfie Camera:''' Single 2MP, f/2.8, 1/5" <br>
'''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if killswitch 6 is deactivated) <br>
'''Communication:'''
: '''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:''' 850/900/1800/1900MHz
: '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot
: '''Bluetooth:''' 4.0, A2DP
: '''GPS:''' Yes, with A-GPS, GLONASS
'''Sensors:''' Accelerometer, gyro, proximity, ambient light, compass <br>
'''[[#Killswitch configuration|Killswitches]]:''' Modem, Wifi & Bluetooth, Microphone, Cameras <br>
'''Battery:''' 2750-3000 mAh Li-Po (replaceable with any Samsung J7 form-factor battery) <br>
'''I/O:''' USB Type-C (SlimPort), USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== History ==

The PinePhone was announced at [https://archive.fosdem.org/2019/ FOSDEM 2019], February 2-4, 2019. The first [[Project Don't be evil]] devkit was on display at the Pine64 booth during the weekend.

=== Hardware revisions ===

The PinePhone platform went through two "developer kit" phases that partner projects used to prove their software on the upcoming platform.

# [[Project Anakin]]
# [[Project Don't be evil]]

Additionally, two "early adopter" revisions of the platform were created:

# [[PinePhone 1.0 "Developer"]]
# [[PinePhone 1.1 "Brave Heart"]]

The first generally available PinePhone batch was [[PinePhone 1.1 "Brave Heart"]]. Pre-orders for this batch started on November 15, 2019. It is expected to ship sometime in December 2019 to January 2020.

A "full release" Pinephone, which will likely have board revision 1.2, will be released in 2020.

== Killswitch configuration ==

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

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

== Modem and Carrier Support ==
{| class="wikitable"
!Carrier
!Bands
!PinePhone Support?
!Notes
|-
| USA:Verizon
| B2, B4, B5, B13, B66
| style="background: #9F9;" | Supported
|-
| USA:T-Mobile
| B2, B4, B5, B12, B66, B71
| style="background: #9F9;" | Supported
|-
| USA:Sprint
| B25, B26, B41
| style="background: #9F9;" | Supported
|-
| UK:EE 4G
| B1, B3, B7, B20
| style="background: #9F9;" | Supported
|-
| UK:O2 4G
| B1, B3, B20, B40
| style="background: #9F9;" | Supported
|-
| UK:Three 4G
| B3, B20, B32
| style="background: #FFB;" | Partial
| Not B32
|-
| UK:Vodafone 4G
| B7, B20, B32
| style="background: #FFB;" | Partial
| Not B32
|-
| China:China Mobile
| B38, B39, B40, B41
| style="background: #9F9;" | Supported
|-
| Germany:T-Mobile
| B1, B3, B7, B8, B20, B22, B28, B32, B38
| style="background: #FFB;" | Partial
| Not B32
|-
| Germany:Vodafone
| B1, B3, B7, B8, B20, B22, B28, B32, B38
| style="background: #FFB;" | Partial
| Not B32
|-
| Germany:O2
| B1, B3, B7, B8, B20, B22, B28, B38
| style="background: #9F9;" | Supported
|-


|}
* Note 1: although [https://www.4g.co.uk/4g-frequencies-uk-need-know/ 4g.co.uk] reports UK:Three and UK:Vodafone use 1400MHz SDL (Band 32) for LTE, as at November 2019 it is believed this is in theory only and not in practice!
* Note 2: according to [https://www.inside-digital.de/ratgeber/5g-lte-mobilfunk-frequenzen-deutschland-band-uebersicht inside-digital.de] in Germany in 2019, Band 32 is only for one-way data boosting, not meant to be used for cellphones but for Homespots, like Vodafone GigaCube

== Software Support ==
Please see the [[PinePhoneOS]] page for details of images available for the PinePhone and how to install them.

PinePhone Software Releases

2019-11-20T21:47:19Z

Ferenc: /* Where/how to report defects */ Add issue tracker for PinePhonen support

[[PinePhone]] Operating Systems

= Software installation =

Initial (new) OS installation should be to an SDcard.

== Preparation of SDcard ==
* Download your chosen image from the options below
* Extract and write the image to an SDcard
* Plug SD card into phone
* Boot phone
If you need step-by-step instructions for writing an image to an SDcard, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.

== Installation to eMMC ==
* Prepare a new SDcard as above
* Boot the phone
* Run a magic script (to be defined/written/...)

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

= Software and OS Image Downloads =

== Postmarket OS ==
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png

postmarketOS also has a script pmbootstrap that can build your SDcard for you, [https://forum.pine64.org/showthread.php?tid=8285 see for example this forum thread.]

=== Download location ===
[http://images.postmarketos.org/pinephone/ Direct download from postmarketOS image site]

=== userid/password ===
demo/demo

=== What works ===

=== What does not work ===

=== Where/how to report defects ===
*[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]
*[https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS PinePhone wiki page]
*[https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) postmarketOS PinePhone '''devkit''' wiki page]

=== Contributions ===
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== Ubuntu Touch by UBPorts ==
http://files.pine64.org/sw/pine64_installer/json/ubports.png

=== Download location ===
[https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ Jenkins Project rootfs-pinephone]

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/how to report defects ===

You should use the built-in Ubuntu Touch feature to "Report a bug". See [https://ubports.com/blog/ubports-blog-1/post/github-106 UBports] own tutorial on how to submit defects.

=== Contributions ===
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== KDE Plasma ==
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png

=== Download location ===
* Not Yet Ready

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/howto report defects ===

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== Sailfish OS ==
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png

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

The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card.

'''Instructions:'''

1. Download the flashing script

2. Insert a microSD card in your device

3. Make the script executable: <code>chmod +x flash-it.sh</code>

4. Execute it: <code>./flash-it.sh</code>

5. Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

'''Note''': The script will format and flash the SD card, make sure that you don't have any important data on the SD card!

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/how to report defects ===

=== Contributions ===
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== Maemo Leste ==
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png

=== Download location ===
[http://maedevu.maemo.org/images/pinephone-dontbeevil/ Maemo Leste test builds download]

=== userid/password ===
root/toor

=== What works ===

=== What does not work ===

=== Where/how to report defects ===

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== NixOS ==
http://files.pine64.org/sw/pine64_installer/json/nixos.png

=== Download location ===
* Not Yet Ready

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/how to report defects ===
See [https://nixos.org/nixos/community.html Bugs section on this page.]

=== Contributions ===
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== LuneOS ==
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg

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

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/how to report defects ===

=== Contributions ===

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== Nemo Mobile ==
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png

=== Download location ===
* Not Yet Ready

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/how to report defects ===

=== Contributions ===

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]
* [https://store.pine64.org/?post_type=product Pine64 shop]
* [[PinePhone]] hardware details
* [https://linux-sunxi.org/Main_Page sunxi community wiki]

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

PinePhone Software Releases

2019-11-20T21:41:36Z

Ferenc: /* Where/how to report defects */ Fix link to the devkit page, add add link to the actual phone's page

[[PinePhone]] Operating Systems

= Software installation =

Initial (new) OS installation should be to an SDcard.

== Preparation of SDcard ==
* Download your chosen image from the options below
* Extract and write the image to an SDcard
* Plug SD card into phone
* Boot phone
If you need step-by-step instructions for writing an image to an SDcard, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.

== Installation to eMMC ==
* Prepare a new SDcard as above
* Boot the phone
* Run a magic script (to be defined/written/...)

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

= Software and OS Image Downloads =

== Postmarket OS ==
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png

postmarketOS also has a script pmbootstrap that can build your SDcard for you, [https://forum.pine64.org/showthread.php?tid=8285 see for example this forum thread.]

=== Download location ===
[http://images.postmarketos.org/pinephone/ Direct download from postmarketOS image site]

=== userid/password ===
demo/demo

=== What works ===

=== What does not work ===

=== Where/how to report defects ===
*[https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS PinePhone wiki page]
*[https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) postmarketOS PinePhone '''devkit''' wiki page]

=== Contributions ===
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== Ubuntu Touch by UBPorts ==
http://files.pine64.org/sw/pine64_installer/json/ubports.png

=== Download location ===
[https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ Jenkins Project rootfs-pinephone]

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/how to report defects ===

You should use the built-in Ubuntu Touch feature to "Report a bug". See [https://ubports.com/blog/ubports-blog-1/post/github-106 UBports] own tutorial on how to submit defects.

=== Contributions ===
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== KDE Plasma ==
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png

=== Download location ===
* Not Yet Ready

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/howto report defects ===

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== Sailfish OS ==
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png

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

The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card.

'''Instructions:'''

1. Download the flashing script

2. Insert a microSD card in your device

3. Make the script executable: <code>chmod +x flash-it.sh</code>

4. Execute it: <code>./flash-it.sh</code>

5. Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

'''Note''': The script will format and flash the SD card, make sure that you don't have any important data on the SD card!

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/how to report defects ===

=== Contributions ===
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== Maemo Leste ==
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png

=== Download location ===
[http://maedevu.maemo.org/images/pinephone-dontbeevil/ Maemo Leste test builds download]

=== userid/password ===
root/toor

=== What works ===

=== What does not work ===

=== Where/how to report defects ===

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== NixOS ==
http://files.pine64.org/sw/pine64_installer/json/nixos.png

=== Download location ===
* Not Yet Ready

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/how to report defects ===
See [https://nixos.org/nixos/community.html Bugs section on this page.]

=== Contributions ===
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== LuneOS ==
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg

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

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/how to report defects ===

=== Contributions ===

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

== Nemo Mobile ==
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png

=== Download location ===
* Not Yet Ready

=== userid/password ===

=== What works ===

=== What does not work ===

=== Where/how to report defects ===

=== Contributions ===

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]
* [https://store.pine64.org/?post_type=product Pine64 shop]
* [[PinePhone]] hardware details
* [https://linux-sunxi.org/Main_Page sunxi community wiki]

<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div>

PineTime

2019-11-18T20:07:36Z

Ferenc: /* Datasheets for Components */ Fix typo: 'Hear Rate' -> 'Heart Rate'

= PINE64 SmartWatch "PineTime" =
The PINE64 SmartWatch, dubbed "PineTime", is a product of a community effort for an open source smartwatch in collaboration with wearable RTOS and Linux app developers & communities.

PineTime development has been broken down into two distinct phases:
* Phase One - PineTime Dev Kit Project on October 2019
* Phase Two - Introducing the PineTime smartwatch around Q1 2020, depending on development results in Phase 1.

== PineTime Concept Photo ==
[[File:PineTime_leaflet.jpg]]

== PineTime Case and Charging Cradle Photos ==
[[File:PineTime_on_wrist_Photo.jpg]]
[[File:PineTime_PPG_Sensor_Photo.jpg]]
[[File:PineTime_Charging_Cradle_Photo.jpg]]

== PineTime DevKit internal Photos ==
[[File:PineTime_Devkit-1.jpg]]
[[File:PineTime_Devkit-2.jpg]]
[[File:PineTime_Devkit-3.jpg]]

[[File:PineTime_Devkit-4.jpg]]
[[File:PineTime_Devkit-5.jpg]]
[[File:PineTime_Devkit-6.jpg]]

== Watch Information ==
* LAUNCH:
** Announced: Tweet on 13 September 2019
** Devkit Release: October, 2019
** Expected Release: Q1/Q2 2020, pending on development result
** Availability: at least 5 years

* BODY:
** Dimensions: 37.5mm x 40mm x 11mm
** Weight: 38 grams
** Build: Zinc Alloy and Plastic
** Environmental Rating: IP67 (waterproof to 1 meter of immersion; '''not applicable to devkits''')

* DISPLAY:
** Type: IPS capacitive touchscreen, RGB 65K colors
** Size: 1.3 inches
** Resolution: 240x240 pixels, 1:1 ratio

* PLATFORM:
** OS: Various open source RTOS such as Zephyr, FreeRTOS, Mbed, Mynewt, or NuttX. See [[PineTime RTOS Comparison]].
** SoC: NORDIC Semiconductor nRF52832
** CPU: 64MHz ARM Cortex-M4F

* MEMORY:
** Internal: 512KB Flash, 64KB RAM
** Additional: SPI NOR 8 MB Flash

* COMMUNICATION:
** Bluetooth 5 (including Low Energy)

* FEATURES:
** Sensors: Accelerometer, PPG Heart Rate Sensor
** Actuator: Vibrator

* BATTERY:
** Built-in LiPo 170-180mAh battery
** Charging: Proprietary 2pin 5V 500mA, USB type A plug

* PRICE:
** USD $22.99 (PineTime pebble and charging cradle, based on phone on PineTime devkit hardware configuration)
** USD $2 and up (20mm straight generic wrist band: silicone, NATO, Milanese steel, leather, and etc)

== PineTime Schematic and Certifications ==
* PineTime Main Board Schematic:
** [http://files.pine64.org/doc/PineTime/PineTime%20Schematic-V1.0a-20191103.pdf PineTime Schematic ver1.0a]
** [http://files.pine64.org/doc/PineTime/PineTime%20Port%20Assignment%20rev1.0.pdf PineTime GPIO Port Assignment ver1.0]
* PineTime Certifications:
** not yet available

== PineTime DevKit SWD Probe ==
* PineTime SWD probe pinout definition:
[[File:PineTime_SWD_location.jpg]]

=== PineTime SWD Probe Usage Method ===
Slightly bend or zig-zag the probe pins to the left and right to strengthen contact to the SWD pins on the dev kit.

'''Note''': The color coding on the SWD probe wires is random and meaningless.

[[File:PineTime_SWD_Plugin.jpg]]

== Driving the peripherals ==

=== Display ===

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

=== Battery ===

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.

== Datasheets for Components ==
* NORDIC SoC information:
** [http://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf NORDIC nRF52832 Product Brief]
** [http://files.pine64.org/doc/datasheet/pinetime/nRF52840%20product%20brief.pdf NORDIC nRF52840 Product Brief]
* PMU (Power Management Unit) information:
** [http://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]
** [http://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]
* SPI Flash information:
** [http://files.pine64.org/doc/datasheet/pinetime/MX25L6433F,%203V,%2064Mb,%20v1.6.pdf Macronix 64Mb(8MB) SPI NOR Flash]
** [http://files.pine64.org/doc/datasheet/pinetime/MX25L12835F,%203V,%20128Mb,%20v1.6.pdf Macronix 128Mb(16MB) SPI NOR Flash]
* LCD Panel:
** [http://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:
** [http://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]
** [http://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/5/51/CST816S%E6%95%B0%E6%8D%AE%E6%89%8B%E5%86%8CV1.1.en.pdf English Translation]
* Sensor:
** [http://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial VAcceleration Sensor Product Brief]
** [http://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]

== Articles ==
** [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]