PINE64 - User contributions [en]

User:Fxc

2023-01-13T16:22:55Z

Danel: /* Suspicious protectionfilms24.com link spam */

== Suspicious protectionfilms24.com link spam ==
* https://wiki.pine64.org/index.php?title=PineTime&diff=15276&oldid=14695
* https://wiki.pine64.org/index.php?title=PinePhone_Pro&diff=15447&oldid=14781
* https://wiki.pine64.org/index.php?title=PinePhone&diff=15448&oldid=15260

Can you explain, how my edits are spam?

== Software state draft ==

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="width: 240px;" | Component
! scope="col" style="width: 150px;" | Status (pre-flashed)¹
! scope="col" style="width: 150px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="2" | Bootloader
| <code>U-Boot</code>
| colspan="2" style="background:Red; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop[https://wiki.pine64.org/wiki/PinePhone_Pro#Installation_instructions]; Occasionally the eMMC fails to boot[Citation]
|-
| <code>SPI</code>
| colspan="2" style="background:Red; text-align:center;" | Unfinished
| SPI memory is currently empty in the Explorer Edition batch, a corrupted installation on the eMMC has a higher boot priority than a fresh microSD card installation, leading to a involved recovery procedure[Citation]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| style="background:Red; text-align:center;" | Critical bugs
| style="background:Yellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://www.pine64.org/2022/03/15/march-update-introducing-the-quartzpro64/];
|-
| <code>Suspend</code>
| style="background:Red; text-align:center;" | Not working
| style="background:Yellow; text-align:center;" | Experimental
| Suspend only available in recent specific images[Citation]
|-
| <code>Updates</code>
| style="background:Red; text-align:center;" | Critical bugs
| style="background:Yellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[Citation]; Pacman database lock preventing updates[Citation]; Keyring bug[Citation]
|-
! scope="row" rowspan="5" | Modem
| <code>Stability</code>
| colspan="2" style="background:Red; text-align:center;" | Critical bugs
| The modem crashes frequently, which can lead to missed calls[Citation]
|-
| <code>Phone</code>
| colspan="2" style="background:Red; text-align:center;" | WIP
| The modem crashes frequently, which can lead to missed calls[Citation]; bad call audio quality[Citation]; software improvements expected within multiple months and contributions are welcome.
|-
| <code>SMS</code>
| colspan="2" style="background:Green; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[Citation] or by the provider blocking specific TANs in their network[Citation].
|-
| <code>MMS</code>
| colspan="2" style="background:Yellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:Red; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:Green; text-align:center;" | Working
|
|-
| <code>Touch</code>
| colspan="2" style="background:Green; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| colspan="2" style="background:Red; text-align:center;" | Not working
| Driver not implemented yet, camera not operational
|-
| <code>Front camera</code>
| colspan="2" style="background:Red; text-align:center;" | Not working
| Driver not implemented yet, camera not operational
|-
| <code>Camera flash</code>
| colspan="2" style="background:Yellow; text-align:center;" | Unknown
|
|-
| <code>WiFi</code>
| colspan="2" style="background:Green; text-align:center;" | Working
| WiFi is expected to work. Note: Proprietary firmware and some remaining tasks, such as looking into "monitor mode"
|-
| <code>Bluetooth</code>
| colspan="2" style="background:Yellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing Proprietary[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire] Note: Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:Yellow; text-align:center;" | WIP
| aGPS to be implemented; long waiting times to get a fix; No preinstalled application
|-
| <code>Sensors</code>
| colspan="2" style="background:Yellow; text-align:center;" | Unknown
| Status of "3 Axis Magnetometer", "Geo Magnetic Sensor", "Ambient light / Proximity", "Accelerometer / Gyroscope" is unknown.
|-
| <code>Vibration motor</code>
| colspan="2" style="background:Green; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:Yellow; text-align:center;" | Unknown
|
|-
| <code>Buttons</code>
| colspan="2" style="background:Green; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="4" | Accessory compatibility
| <code>Keyboard Add-on</code>
| colspan="2" style="background:Yellow; text-align:center;" | WIP
| The keyboard add-on compatibility is work-in-progress. Top row symbols not implemented as designed[Citation]; Keyboard hot-plugging not supported[Citation]; Battery state not exposed in the pre-flashed operating system state[Citation]; general driver bugs[Citation]
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:Red; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:Yellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software and driver functionality is missing, details will follow in a bug report.[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:Red; text-align:center;" | Not implemented
| No software support implemented
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:Yellow; text-align:center;" | Software rendering only
| Waydroid is an Android container used to run Android applications. Currently can only be started using software rendering [Citation]
|-
|}

¹ Status of the feature at the time of the last factory installation without updates

² Status of the feature with an up-to-date reference image

== Chat ==
* https://sackheads.org/~bnaylor/spew/away_msgs.html

* Inclusive language, Linux

== Test 2 ==

<table cellspacing="0" cellpadding="0" border="0" style="box-sizing:border-box; border:1px #d33 solid; background: transparent; margin-top:0.5em;padding:0.5em 1em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top" style="padding-right: 5px;">'''Warning: '''</td><td valign="top">{{{msg|{{{1|}}}}}}</td></tr></table>
<table cellspacing="0" cellpadding="0" border="0" style="box-sizing:border-box; border:1px #d33 solid; background: transparent; margin-top:0.5em;padding:0.5em 1em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top" style="padding-right: 5px;">'''Warning: '''</td><td valign="top">{{{msg|{{{1|}}}}}}</td></tr></table>

<table cellspacing="0" cellpadding="0" border="0" style="box-sizing:border-box; border:1px #d33 solid; background: transparent; margin-top:0.5em;padding:0.5em 1em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top" style="padding-right: 5px;">'''Warning: '''</td><td valign="top">{{{msg|{{{1|}}}}}}</td></tr></table>

<table cellspacing="0" cellpadding="0" border="0" style="box-sizing:border-box; border:1px #d33 solid; background: transparent; margin-top:0.5em;padding:0.5em 1em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top" style="padding-right: 5px;">'''Warning: '''</td><td valign="top">{{{msg|{{{1|}}}}}}</td></tr></table>

{{Warning|Test}}
{{Warning|Test}}

{{Warning|Test}}

{{Warning|Test}}

== Test ==
{{Note|Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua.}}

== Safety ==

=== Charging and Battery ===

Notes:
* Correct charger
* High power usage in certain scenarios
* Handling of the battery
* (Optional: Charging keyboard and phone at the same time)
* (Optional: Connecting a USB-C to USB-C cable from phone to keyboard)

== Ubuntu Touch ==

{| class="wikitable" style="width: 800px;"
!colspan="2" style="background: #a7d7f9;"|Ubuntu Touch
|-
|colspan="2"|Image
|-
|colspan="2"|A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community. Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
|-
|rowspan="1" style="width: 200px;"|Download location
|[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]
|-
|rowspan="2"|user-id/password
| abc
|-
| 123
|-
|What works, what does not work?
|[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]
|-
|How to contribute and report defects?
|[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]
|-
|Contributions
|[https://ubports.com/foundation/sponsors See UBports website for how to donate.]
|-
|colspan="2" style="background: #cecece"| Installation
|-
|colspan="2"| Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.
|-
|colspan="2" style="background: #cecece"| Notes
|-
|colspan="2"| Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.
|-
|}

== Image ==

{| class="wikitable" style="width: 800px;"
|-
|colspan="2"|Image
|-
|colspan="2"|Description
|-
|rowspan="1" style="width: 120px;" | Author
| Test
|-
| License
| CC0
|-
| SVG location
| Test
|}

== Licenses template ==

Test:

{|style="border:1px solid #a2a9b1; padding: 0 10px 0 10px; width: 80%; margin: 4px 10%;"
|
|style="width: 40px"|[[Image:CC_some_rights_reserved.svg|90px|center]] [[Image:Cc-by new white.svg|24px|center]]
|style="padding: 20px"|''This file is licensed under the [https://en.wikipedia.org/wiki/en:Creative_Commons Creative Commons] [https://creativecommons.org/licenses/by/3.0/deed.en Attribution 3.0 Unported] license.''
|}

== Collapsible test ==

{| role="presentation" class="mw-collapsible mw-collapsed wikitable" style="max-width: 60%"
| Notes
|-
| Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.
|}

PineTime

2023-01-13T16:22:05Z

Danel: Undo revision 15478 by Fxc (talk): Straight up, what the hell. They are the only screen srotectors I have found for PineTime and they have been mentioned elsewhere in the community. Please, stop revert.

[[File:Pinetime.png|400px|thumb|right|The PineTime]]

The '''PineTime''' is a free and open source smartwatch capable of running custom-built open operating systems. Some of the notable features include a heart rate monitor, a week-long battery, and a capacitive touch IPS display that is legible in direct sunlight. It is a fully community driven side-project which anyone can contribute to, allowing you to keep control of your device.

== Frequently asked questions / Getting started ==

'''Read these first!'''

* [[Upgrade PineTime to InfiniTime 1.0.0|Upgrading your new PineTime to InfiniTime 1.0.0]]
* [[PineTime FAQ| Frequently Asked Questions about the PineTime]]
* [[PineTime Devkit Wiring]]
* [[Reprogramming the PineTime|Reprogramming the PineTime (development kit)]]
* [[Switching your PineTime between InfiniTime and Wasp-os]]

== Default OS ==

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

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

== Companion Apps ==

PineTime/InfiniTime needs a companion app to e.g. upload a firmware, get notifications from a phone, or just get the date/time.
Here are some companion apps:

* [https://www.gadgetbridge.org Gadgetbridge] (Android >= 4.4) - Companion mobile app, supports updating firmware/bootloader, send notifications, etc.
* [https://openrepos.net/content/piggz/amazfish Amazfish] (SailfishOS and Linux) - Companion mobile and desktop app, supports updating firmware/bootloader, send notifications, etc.
* [https://github.com/alexr4535/siglo Siglo] (Linux) - Companion desktop app.
* [https://github.com/ZephyrLabs/PinetimeFlasher PinetimeFlasher] (Windows) - Companion desktop app, only supports flashing firmware.
* [https://apps.apple.com/us/app/nrf-connect-for-mobile/id1054362403 nRFConnect] (iOS) - Only supports flashing firmware. The app is closed source and versions after 4.24.3 don't work for the PineTime anymore
* [https://github.com/xan-m/InfiniLink InfiniLink] (iOS) - Companion mobile app in development. Supports updating firmware/bootloader, setting date and time, Apple Music controls, and battery and heart rate data.
* [https://gitea.arsenm.dev/Arsen6331/itd itd] (Linux)

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

= Community =

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

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

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

== Development efforts ==

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

== Useful articles and blog posts ==

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

* [https://www.ncartron.org/one-week-with-my-pinetime---a-feedback.html Using the PineTime in production (January 2021)]
* [https://lupyuen.github.io/articles/sneak-peek-of-pinetime-smart-watch-and-why-its-perfect-for-teaching-iot Sneak Peek of PineTime Smart Watch… And why it’s perfect for teaching IoT]
* [https://lupyuen.github.io/articles/building-a-rust-driver-for-pinetimes-touch-controller Building a Rust Driver for PineTime’s Touch Controller]
* [https://lupyuen.github.io/articles/porting-druid-rust-widgets-to-pinetime-smart-watch Porting (druid) Rust Widgets to PineTime Smart Watch]
* [https://lupyuen.github.io/articles/optimising-pinetimes-display-driver-with-rust-and-mynewt Optimising PineTime’s Display Driver with Rust and Mynewt]
* [https://electronut.in/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/ Getting Started with Zephyr RTOS on Nordic nRF52832 hackaBLE]
* [https://blog.aegrel.ee/absniffer-cmsis-dap-sniffer.html Removing the lock and installing another firmware on the nRF52832 using CMSIS-DAP dongle on Linux]
* [https://github.com/JF002/nrf52-baseproject/wiki/Build,-program-and-debug-NRF52-project-with-JLink,-CMake-and-CLion Build, program and debug NRF52 project with JLink, CMake and CLion]
* [https://www.nrbtech.io/blog/2020/1/4/using-clion-for-nordic-nrf52-projects Using CLion for Nordic nRF52 projects]
* [https://dev.to/aaronc81/flashing-your-pinetime-using-an-st-link-and-openocd-54dd Flashing your PineTime using an ST-Link and OpenOCD]
* [https://zephyrlabs.github.io/Watchfaces/ Zephyrlabs: just a bunch of watchfaces made for the pinetime]
* [https://pankajraghav.com/2021/04/03/PINETIME-STOPCLOCK.html Creating a stopwatch in Pinetime (with Infinitime)]

= Hardware =

== Display ==

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

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

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

Notes:

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

'''References''':

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

== Battery measurement ==

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

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

adcVoltage = adcValue / (4095 / 3.3)

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

batteryVoltage = adcValue * 2 / (4095 / 3.3)

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

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

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

== Button ==

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

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

== Touch panel ==

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

=== Pins ===

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

=== I²C ===

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

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

'''NOTE: ''' The I²C bus, also known as TWI bus has known issues, make sure to write your TWI driver with timeouts.

=== Touch events ===

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

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

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

0x00: no gesture,

0x01: Slide down,

0x02: Slide up,

0x03: Slide left,

0x04: Slide right,

0x05: Single click,

0x0B: Double click,

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

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

'''NOTES'''

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

=== Registers ===

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

{| class="wikitable"

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

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

==Accelerometer==
The on board accelerometer in devices shipped before July 2021 is a Bosch BMA421, connected to the I2C bus.
Devices shipped after July 2021 use a Bosch BMA425 accelerometer.

=== Pins ===

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

I2C Device address : 0x18

= Accessory =

== Watch band ==

The PineTime uses a standard 20mm watch band / strap. There is a [https://forum.pine64.org/showthread.php?tid=9392&pid=81902 thread] in the forum discussing this.

== Screen protectors ==
Screen protectors for PineTime:

* [https://www.protectionfilms24.com/article/2x-vikuiti-screen-protector-cv8-pine64-pinetime-442381.html Vikuiti screen protector CV8 (2pcs)]
* [https://www.protectionfilms24.com/article/6x-savvies-su75-screen-protectorpine64-pinetime-1642381.html Savvies SU75 UltraClear Screen Protector (6pcs)], [https://www.protectionfilms24.com/article/18x-savvies-su75-screen-protectorpine64-pinetime-2342381.html (18pcs)]

== Cases ==
There are no cases for PineTime yet, but some cases for Fitbit are suitable for it. Cases for Fitbit have one microphone hole, which is unnecessary for the PineTime, but otherwise they fit perfectly.

* [https://www.aliexpress.com/item/1005003150606521.html Soft TPU case for Fitbit Versa 2/Versa Lite from AliExpress]

The community designed the following cases:
* [https://www.thingiverse.com/thing:4172849 PineTime Smart Watch case by dara0s at thingiverse]
* [https://www.thingiverse.com/thing:4651462 PineTime dev kit back fix by joaquimorg at thingiverse]
* [https://www.thingiverse.com/thing:4763267 PineTime dev kit charging holder v4 by zevix81 at thingiverse]
* [https://www.prusaprinters.org/prints/88913-pinetime-charger-case PineTime Charger Travel Case by brett at PrusaPrinters]

= Datasheets, Schematics and Certifications=

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

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

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

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

== Certificates ==
** [https://files.pine64.org/doc/cert/FCC_Grant_PineTime_2AWAG-PINETIME_DTS.pdf PineTime FCC Certificate]
** [https://files.pine64.org/doc/cert/CTL2203033031-W%20RED%20Certificate.pdf PineTime CE Certificate]

== Manuals ==
* [[:File:PineTime Quick Start Guide.pdf|PineTime Quick Start Guide]]

[[Category:PineTime]]

User talk:Fxc

2023-01-13T16:19:12Z

Danel: /* Request to involve Manual of style */

== Carrier Support ==
Can you please explain why you keep removing my additions to [[PinePhone_Carrier_Support]] -- [[User:Mikehenson|Mike]] 02:22:09 29 April 2021 (UTC)
: You keep adding your provider in the wrong section. You want to add it in the section "Tested and working" but you keep adding it to the section "Does not work / special notes". Regards --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 12:13, 29 April 2021 (UTC)
:: Thank you! I added it to [[PinePhone_Carrier_Support#North_America]] -- [[User:Mikehenson|Mike]] 17:09:09 29 April 2021 (UTC)

== Discussion on what to do with the Rock64 page ==

Hi, I'm asking you about this since you seem to be one of the more active contributors of the wiki.

I recently noticed that there are two ROCK64 pages, one is [[ROCK64]], the other is [[Rock64]]. They seem to duplicate a lot of information, and the latter appears to contain a large list of links already covered in the software releases page.

What should be done about this? Should we delete [[Rock64]] and make it a redirect? --[[User:CounterPillow|CounterPillow]] ([[User talk:CounterPillow|talk]]) 19:20, 13 May 2021 (UTC)

:For now I've decided to make it a redirect, upon seeing that the user who created it also created other pages which were just carbon copies of the respective actual pages at the time. Maybe some spam thing? --[[User:CounterPillow|CounterPillow]] ([[User talk:CounterPillow|talk]]) 06:24, 14 May 2021 (UTC)

:: Yup, I would have recommended a redirect too. The SBC articles and especially their naming is quite chaotic so (radically) cleaning up the wiki and finding a better structure between different articles is something which has to be done sooner or later anyway. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 12:38, 14 May 2021 (UTC)

== Re: Your edits in PinePhone ==

Good day, Fxc! Thank you very much for your help in moving my recent edits to their more suitable places: this stuff took me plenty of time to figure out & test, and hopefully our work could be valuable to the fellow PinePhone users.

Unfortunately, I noticed that "IMEI check and change" has been reverted for the reason "Illegal wiki contents removed". Please tell, "illegal" - in what country? I.e. PINE64 is a Hong Kong company, while a Pine64 wiki website is hosted in Slovakia, - and I can't any info that changing IMEI in either Hong Kong or Slovakia is illegal, or at least posting the "how-to" information about this. And what isn't forbidden - is allowed. For the majority of countries ''(not taking some totalitarian ones into account)'', changing IMEI is as legal as changing the MAC address which has been allowed to stay.

Since a "pinephone change imei" seems to be a popular Google request (it's even more popular than "pinephone change os"), I'd like to preserve this information for the public usage. If, to be able to do that, I need to re-word/extend the warning about the possible legal issues (something like "please check the laws of your country before doing that") - please let me know.

At the same time I understand this advanced information is probably not suitable for the main PinePhone page. Please tell what's the more appropriate place in your opinion - [[PineModems]], [[PinePhone_Software_Tweaks]] or [[PinePhone_FAQ#Modem]] ?

: Please don't re-add information regarding the IMEI on the wiki. Regarding software information: there is currently no place for it, [[PinePhone Software Tweaks]] was a quick idea - if you have other ideas feel free! The PineModems article is more on the hardware side of different modems and in the FAQ it would probably fit but that article isn't read very often. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 21:46, 23 August 2021 (UTC)

== Removing the addition about battery ==

Hello all,

I think it was not so good to remove the section, explaining how exactly one could get a good replacement battery
and make it fit into PP without any difficulties. Because this is actually a problem: there are any replacement battries
and fitting the J7 battery into the PP without filing it could result in a broken phone.

ref: https://wiki.pine64.org/index.php?title=PinePhone&diff=15200&oldid=15102
--[[User:Pptester|Pptester]] ([[User talk:Pptester|talk]]) 14:16, 13 January 2023‎ (UTC)

: Said section doesn't fit the quality requirements of the rest of the page, as written in the edit note. There are multiple issues here. The newer PinePhone revisions have a bigger battery compartment for the plastic tabs on some batteries (the ones which are deemed incompatible due to the size in the battery paragraph). The paragraph is telling users to use a sharp object on batteries, which is a big no no. People can do that on their personal items but telling users to do so without sufficient warnings (colors, specialized templates PRIOR the instructions) is a red flag. The wiki also tries to be OS-agnostic as much as possible, which the commands are not. The same is the problem for random systemd service files, while distributions are not shipped with systemd - and a systemd service file isn't even the right solution anyway, it's a cheap workaround for not knowing the proper solution to apply sysfs changes permanently. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 14:38, 13 January 2023 (UTC)

== Request to involve Manual of style ==

Hello, I have noticed from the histories that you are a very active wiki editor and I would like to announce my new initiative, [[Help:Manual of style]]. It's important, because there are many articles to go through, to improve and to "standardize", but before that we need to create some kind of guide for these. --[[User:Tree|Tree]] ([[User talk:Tree|talk]]) 15:48, 13 January 2023 (UTC)
: I don't agree with this assessment, we're not Wikipedia and only a small number of contributors. What the wiki needs at least is a new user account telling people to do what they think seems appropriate with zero consensus - and even less a surplus of meta discussion contribution instead of actual contributions to wiki pages. For your personal drafts please use your userspace (for example under https://wiki.pine64.org/wiki/User:Tree/Manual_of_style). If the drafts are in a good state and there no concerns we can move them. Mind that copying whole articles removes the submission history, which is usually undesirable if preventable. The Pinecil article is also not the prime example. Regards, --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 15:50, 13 January 2023 (UTC)
:: Of course, the intention is not to make a huge manual similar to Wikipedia... however, that doesn't mean we can't make some guidelines. At least, it would be necessary to make a manual about the structures and general formatting. You could have expected that others would also add their opinions to the discussion page. I don't think the age of the contributer matters if the edits are good. --Tree