PINE64 - User contributions [en]

PineTab2 FAQ

2023-07-19T00:39:15Z

Moobythegoldensock:

This is a collection of tutorials and frequently asked questions for the PineTab2.

== Tutorials ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (or the USB-C to USB-C cable)
* Some knowledge of your variation of Android

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

=== Screen Rotation ===
==== Auto-rotating the Screen ====
Auto-rotation is handled by your operating system. However, the following general steps should work on distributions that support iio-sensor-proxy:

* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* Some desktop environments, such as KDE, default to only allowing screen rotation while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor-->Display Configuration-->Uncheck "Only when in tablet mode" and click "Apply."

==== Rotating the Login Screen ====
Login screen orientation is handled by your operating system. Below are the instructions for the SDDM login screen that ships with the factory image:

By default, the login screen is set to display in portrait mode. If you wish to change it to landscape mode to match the keyboard while in the case, use the following steps ([https://forum.pine64.org/showthread.php?tid=18313 Credit to chzbacon]) :

* Install necessary software: <code>sudo pacman -S xorg-xrandr xorg-xinput</code>
* Edit /usr/share/sddm/scripts/Xsetup. For example, using nano: <code>sudo nano /usr/share/sddm/scripts/Xsetup</code> and add the following two lines to the end of file:
** <code>xrandr --output DSI-1 --mode 800x1280 --rate 60.00 --rotate right</code>
** <code>xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1</code>
* Now edit /etc/sddm.conf.d/sddm.conf, for example: <code>sudo nano /etc/sddm.conf.d/sddm.conf</code> and add the following two lines (case sensitive):
** <code>[X11]</code>
** <code>DisplayCommand=/usr/share/sddm/scripts/Xsetup</code>
*Reboot, and your login screen should now display in landscape mode.

== Frequently Asked Questions ==

=== General ===

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

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

==== I am a casual user with minimal Linux experience. Is this device for me? ====
The PineTab 2 is considered early release at this point, and the community is expected to develop support for it over time. For example, the [[PineTab2#Known_Issues]] page details several features that are not yet fully working. You may at times need to troubleshoot this device and some development experience is ideal if you want to realize the tablet's full potential at this stage.

For these reasons, the PineTab2 may not be the ideal device for casual users. However, if you feel up to the challenge and want to learn while joining a great community, you are more than welcome! Please join one of our [[Main_Page#Chat_Platforms|chat platforms]]: the community is always happy to help!

==== What works, what doesn't? ====

Please see [[PineTab2#Known_Issues]].

==== I only know Python, can I help with drivers? ====
Yes, if you learn C first. Otherwise, no. (This response isn't trying to be snarky, this question was asked so many times it really needed to be here.)

=== Hardware ===

==== Does the Tablet support a Pen? ====
No, adding a digitiser for pen inputs would make the price too high.

==== Is there SPI Flash? ====
Yes! A 128 Mbit flash chip (sk25lp128) is reportedly present on production devices.

=== Software ===
==== What operating systems are currently available? ====
The PineTab2 uses ARM operating systems. Please see [[PineTab2 Releases]] for a current list of software releases.

==== How can I install an operating system on the SD card / eMMC? ====

See [[PinePhone Installation Instructions|Installation Instructions]].

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

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

=== Booting ===

==== What's the boot order for SD cards and eMMC? ====
The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. Please see the [[PinePhone Installation Instructions#PineTab2|boot priority]] page for more detailed information.

==== Can I install a different OS on my PineTab2? ====

Yes! While all PineTab2 come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card. See [[PinePhone Installation Instructions|Installation Instructions]] and [[PineTab2 Releases]] for how to install them.

=== Bluetooth ===

==== The Bluetooth isn't working ====
The BES2600 Bluetooth driver still needs to be implemented. Please see the [[#Networking Using USB]] section above for a workaround.

=== Wi-Fi ===

==== The Wi-Fi isn't working ====
The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing: at the moment it causes system crashes. Please see the [[#Networking Using USB]] section above for a workaround.

=== Video ===

==== Can PineTab2 play back DRM content such as Netflix? ====
Yes, though the specific implementation depends on your installed operating system.

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

=== Shipping ===
==== I did not receive an order confirmation ====
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get an order confirmation email.

==== When does the tablet ship? ====
For up-to-date information when the shipping date is estimated, see the edits in the corresponding forum thread.

==== It is shipping day but I did not receive a shipping notification ====
For shipments with DHL, the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.

==== What about import taxes? =====
Import taxes have to be paid by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.

[[Category:Rockchip RK3566]]

PineTab2 FAQ

2023-07-19T00:37:53Z

Moobythegoldensock: Formatting

This is a collection of tutorials and frequently asked questions for the PineTab2.

== Tutorials ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (or the USB-C to USB-C cable)
* Some knowledge of your variation of Android

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

=== Screen Rotation ===
==== Auto-rotating the Screen ====
Auto-rotation is handled by your operating system. However, the following general steps should work on distributions that support iio-sensor-proxy:

* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* Some desktop environments, such as KDE, default to only allowing screen rotation while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor-->Display Configuration-->Uncheck "Only when in tablet mode" and click "Apply."

==== Rotating the Login Screen ====
Login screen orientation is handled by your operating system. Below are the instructions for the SDDM login screen that ships with the factory image:

By default, the login screen is set to display in portrait mode. If you wish to change it to landscape mode to match the keyboard while in the case, use the following steps ([https://forum.pine64.org/showthread.php?tid=18313 Credit to chzbacon]) :

* Install necessary software: <code>sudo pacman -S xorg-xrandr xorg-xinput</code>
* Edit /usr/share/sddm/scripts/Xsetup. For example, using nano: <code>sudo nano /usr/share/sddm/scripts/Xsetup</code> and add the following two lines to the end of file:
** <code>xrandr --output DSI-1 --mode 800x1280 --rate 60.00 --rotate right</code>
** <code>xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1</code>
* Now edit /etc/sddm.conf.d/sddm.conf, for example: <code>sudo nano /etc/sddm.conf.d/sddm.conf</code> and add the following two lines (case sensitive):
** <code>[X11]</code>
** <code>DisplayCommand=/usr/share/sddm/scripts/Xsetup</code>
*Reboot, and your login screen should now display in landscape mode.

== Frequently Asked Questions ==

=== General ===

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

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

==== I am a casual user with minimal Linux experience. Is this device for me? ====
The PineTab 2 is considered early release at this point, and the community is expected to develop support for it over time. For example, the [[PineTab2#Known_Issues]] page details several features that are not yet fully working. You may at times need to troubleshoot this device and some development experience is ideal if you want to realize the tablet's full potential at this stage.

For these reasons, the PineTab2 may not be the ideal device for casual users. However, if you feel up to the challenge and want to learn while joining a great community, you are more than welcome!

Please join one of our [[Main_Page#Chat_Platforms|chat platforms]], the community is always happy to help!

==== What works, what doesn't? ====

Please see [[PineTab2#Known_Issues]].

==== I only know Python, can I help with drivers? ====
Yes, if you learn C first. Otherwise, no. (This response isn't trying to be snarky, this question was asked so many times it really needed to be here.)

=== Hardware ===

==== Does the Tablet support a Pen? ====
No, adding a digitiser for pen inputs would make the price too high.

==== Is there SPI Flash? ====
Yes! A 128 Mbit flash chip (sk25lp128) is reportedly present on production devices.

=== Software ===
==== What operating systems are currently available? ====
The PineTab2 uses ARM operating systems. Please see [[PineTab2 Releases]] for a current list of software releases.

==== How can I install an operating system on the SD card / eMMC? ====

See [[PinePhone Installation Instructions|Installation Instructions]].

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

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

=== Booting ===

==== What's the boot order for SD cards and eMMC? ====
The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. Please see the [[PinePhone Installation Instructions#PineTab2|boot priority]] page for more detailed information.

==== Can I install a different OS on my PineTab2? ====

Yes! While all PineTab2 come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card. See [[PinePhone Installation Instructions|Installation Instructions]] and [[PineTab2 Releases]] for how to install them.

=== Bluetooth ===

==== The Bluetooth isn't working ====
The BES2600 Bluetooth driver still needs to be implemented. Please see the [[#Networking Using USB]] section above for a workaround.

=== Wi-Fi ===

==== The Wi-Fi isn't working ====
The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing: at the moment it causes system crashes. Please see the [[#Networking Using USB]] section above for a workaround.

=== Video ===

==== Can PineTab2 play back DRM content such as Netflix? ====
Yes, though the specific implementation depends on your installed operating system.

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

=== Shipping ===
==== I did not receive an order confirmation ====
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get an order confirmation email.

==== When does the tablet ship? ====
For up-to-date information when the shipping date is estimated, see the edits in the corresponding forum thread.

==== It is shipping day but I did not receive a shipping notification ====
For shipments with DHL, the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.

==== What about import taxes? =====
Import taxes have to be paid by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.

[[Category:Rockchip RK3566]]

PineTab2 FAQ

2023-07-19T00:35:19Z

Moobythegoldensock: Formatting

This is a collection of tutorials and frequently asked questions for the PineTab2.

== Tutorials ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (or the USB-C to USB-C cable)
* Some knowledge of your variation of Android

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

=== Screen Rotation ===
==== Auto-rotating the Screen ====
Auto-rotation is handled by your operating system. However, the following general steps should work on distributions that support iio-sensor-proxy:

* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* Some desktop environments, such as KDE, default to only allowing screen rotation while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor-->Display Configuration-->Uncheck "Only when in tablet mode" and click "Apply."

==== Rotating the Login Screen ====
Login screen orientation is handled by your operating system. Below are the instructions for the SDDM login screen that ships with the factory image:

By default, the login screen is set to display in portrait mode. If you wish to change it to landscape mode to match the keyboard while in the case, use the following steps ([https://forum.pine64.org/showthread.php?tid=18313 Credit to chzbacon]) :

* Install necessary software: <code>sudo pacman -S xorg-xrandr xorg-xinput</code>
* Edit /usr/share/sddm/scripts/Xsetup. For example, using nano: <code>sudo nano /usr/share/sddm/scripts/Xsetup</code> and add the following two lines to the end of file:
** <code>xrandr --output DSI-1 --mode 800x1280 --rate 60.00 --rotate right</code>
** <code>xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1</code>
* Now edit /etc/sddm.conf.d/sddm.conf, for example: <code>sudo nano /etc/sddm.conf.d/sddm.conf</code> and add the following two lines (case sensitive):
** <code>[X11]</code>
** <code>DisplayCommand=/usr/share/sddm/scripts/Xsetup</code>
*Reboot, and your login screen should now display in landscape mode.

== Frequently Asked Questions ==

=== General ===

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

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

==== I am a casual user with minimal Linux experience. Is this device for me? ====
The PineTab 2 is considered early release at this point, and the community is expected to develop support for it over time. For example, the [[PineTab2#Known_Issues]] page details several features that are not yet fully working.

You may at times need to troubleshoot this device and some development experience is ideal if you want to realize the tablet's full potential at this stage. However, if you feel up to the challenge and want to learn while joining a great community, you are more than welcome!

Please join one of our [[Main_Page#Chat_Platforms|chat platforms]], the community is always happy to help!

==== What works, what doesn't? ====

Please see [[PineTab2#Known_Issues]].

==== I only know Python, can I help with drivers? ====
Yes, if you learn C first. Otherwise, no. (This response isn't trying to be snarky, this question was asked so many times it really needed to be here.)

=== Hardware ===

==== Does the Tablet support a Pen? ====
No, adding a digitiser for pen inputs would make the price too high.

==== Is there SPI Flash? ====
Yes! A 128 Mbit flash chip (sk25lp128) is reportedly present on production devices.

=== Software ===
==== What operating systems are currently available? ====
The PineTab2 uses ARM operating systems. Please see [[PineTab2 Releases]] for a current list of software releases.

==== How can I install an operating system on the SD card / eMMC? ====

See [[PinePhone Installation Instructions|Installation Instructions]].

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

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

=== Booting ===

==== What's the boot order for SD cards and eMMC? ====
The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. Please see the [[PinePhone Installation Instructions#PineTab2|boot priority]] page for more detailed information.

==== Can I install a different OS on my PineTab2? ====

Yes! While all PineTab2 come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card. See [[PinePhone Installation Instructions|Installation Instructions]] and [[PineTab2 Releases]] for how to install them.

=== Bluetooth ===

==== The Bluetooth isn't working ====
The BES2600 Bluetooth driver still needs to be implemented. Please see the [[#Networking Using USB]] section above for a workaround.

=== Wi-Fi ===

==== The Wi-Fi isn't working ====
The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing: at the moment it causes system crashes. Please see the [[#Networking Using USB]] section above for a workaround.

=== Video ===

==== Can PineTab2 play back DRM content such as Netflix? ====
Yes, though the specific implementation depends on your installed operating system.

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

=== Shipping ===
==== I did not receive an order confirmation ====
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get an order confirmation email.

==== When does the tablet ship? ====
For up-to-date information when the shipping date is estimated, see the edits in the corresponding forum thread.

==== It is shipping day but I did not receive a shipping notification ====
For shipments with DHL, the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.

==== What about import taxes? =====
Import taxes have to be paid by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.

[[Category:Rockchip RK3566]]

PineTab2 FAQ

2023-07-18T20:09:49Z

Moobythegoldensock: Remove How-to and FAQ from PineTab2 page and recreate them here.

This is a collection of tutorials and frequently asked questions for the PineTab2.

== Tutorials ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (or the USB-C to USB-C cable)
* Some knowledge of your variation of Android

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

=== Screen Rotation ===
==== Auto-rotating the Screen ====
Auto-rotation is handled by your operating system. However, the following general steps should work on distributions that support iio-sensor-proxy:

* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* Some desktop environments, such as KDE, default to only allowing screen rotation while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor-->Display Configuration-->Uncheck "Only when in tablet mode" and click "Apply."

==== Rotating the Login Screen ====
Login screen orientation is handled by your operating system. Below are the instructions for the SDDM login screen that ships with the factory image:

By default, the login screen is set to display in portrait mode. If you wish to change it to landscape mode to match the keyboard while in the case, use the following steps ([https://forum.pine64.org/showthread.php?tid=18313 Credit to chzbacon]) :

* Install necessary software: <code>sudo pacman -S xorg-xrandr xorg-xinput</code>
* Edit /usr/share/sddm/scripts/Xsetup. For example, using nano: <code>sudo nano /usr/share/sddm/scripts/Xsetup</code> and add the following two lines to the end of file:
** <code>xrandr --output DSI-1 --mode 800x1280 --rate 60.00 --rotate right</code>
** <code>xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1</code>
* Now edit /etc/sddm.conf.d/sddm.conf, for example: <code>sudo nano /etc/sddm.conf.d/sddm.conf</code> and add the following two lines (case sensitive):
** <code>[X11]</code>
** <code>DisplayCommand=/usr/share/sddm/scripts/Xsetup</code>
*Reboot, and your login screen should now display in landscape mode.

== Frequently Asked Questions ==

=== General ===

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

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

==== I am a casual user with minimal Linux experience. Is this device for me? ====
The PineTab 2 is considered early release at this point, and the community is expected to develop support for it over time. For example, the [[PineTab2#Known_Issues]] page details several features that are not yet fully working.

You may at times need to troubleshoot this device and some development experience is ideal if you want to realize the tablet's full potential at this stage. However, if you feel up to the challenge and want to learn while joining a great community, you are more than welcome!

Please join one of our [[Main_Page#Chat_Platforms|chat platforms]], the community is always happy to help!

==== What works, what doesn't? ====

Please see [[PineTab2#Known_Issues]].

==== I only know Python, can I help with drivers? ====
Yes, if you learn C first. Otherwise, no. (This response isn't trying to be snarky, this question was asked so many times it really needed to be here.)

=== Hardware ===

==== Does the Tablet support a Pen? ====
No, adding a digitiser for pen inputs would make the price too high.

==== Is there SPI Flash? ====
Yes! A 128 Mbit flash chip (sk25lp128) is reportedly present on production devices.

=== Software ===
==== What operating systems are currently available? ====
The PineTab2 uses ARM operating systems. Please see [[PineTab2 Releases]] for a current list of software releases.

==== How can I install an operating system on the SD card / eMMC? ====

See [[PinePhone Installation Instructions|Installation Instructions]].

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

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

=== Booting ===

==== What's the boot order for SD cards and eMMC? ====
The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. Please see the [[PinePhone Installation Instructions#PineTab2|boot priority]] page for more detailed information.

==== Can I install a different OS on my PineTab2? ====

Yes! While all PineTab2 come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card. See [[PinePhone Installation Instructions|Installation Instructions]] and [[PineTab2 Releases]] for how to install them.

=== Bluetooth ===

==== The Bluetooth isn't working ====
The BES2600 Bluetooth driver still needs to be implemented. Please see the [[#Networking Using USB]] section above for a workaround.

=== Wi-Fi ===

==== The Wi-Fi isn't working ====
The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing: at the moment it causes system crashes. Please see the [[#Networking Using USB]] section above for a workaround.

=== Video ===

==== Can PineTab2 play back DRM content such as Netflix? ====
Yes, though the specific implementation depends on your installed operating system.

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

== Shipping ==
=== I did not receive an order confirmation ===
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get an order confirmation email.

=== When does the tablet ship? ===
For up-to-date information when the shipping date is estimated, see the edits in the corresponding forum thread.

=== It is shipping day but I did not receive a shipping notification ===
For shipments with DHL, the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.

=== What about import taxes? ===
Import taxes have to be paid by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.

[[Category:Rockchip RK3566]]

PineTab2

2023-07-18T20:09:34Z

Moobythegoldensock: Moved tutorials and FAQ to the PineTab2 FAQ page.

PineTab2

2023-07-18T19:21:44Z

Moobythegoldensock: Moved installation instructions to the PinePhone Installation Instructions Page

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

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

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

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

== Getting started ==

The PineTab2 box contains two smaller boxes.

The first package includes:
* the PineTab2,
* a short user guide,
* a power cable and
* the UART adapter Note that the UART adapter is in the same package as the power cable in a second compartment and can be a bit hidden, search for it.

The second box has the keyboard in it.

=== First start ===

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

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

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

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

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

== Software ==

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

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

=== Software Releases ===

* The PineTab2 ships with ''Danctnix Arch Linux ARM''. The factory image can be found here:
** https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)
** {{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}
* All other releases for the PineTab2 will be listed under [[PineTab2 Releases]] as they're released. Your contributions are wanted!

=== Installation instructions ===

The PineTab2 is capable of running different operating systems from the internal flash memory (eMMC) and from microSD card. Please see the [[PinePhone Installation Instructions|Installation Instructions]] for detailed instructions. Please also note the info under the [[PinePhone Installation Instructions#PineTab2|boot priority]] entry when booting from microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above linked procedure.

== Keyboard cover==

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

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

The external keyboard has 5 connection pins (the golden pins).
4 are standard USB connectors, one is to detect that the keyboard is connected.

== Specifications ==

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

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

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

=== Known Issues ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

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

* Plug the adapter face-up in the USB-C port furthest away from the power button. If all the lights are lit, you have the wrong port: only the green light should be lit when you first plug it in.
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

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

PineTab2 mainboard schematic:

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

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

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:

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

== Frequently Asked Questions ==

'''Does the Tablet support a Pen?'''

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

'''Can I run Android on it?'''

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

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

'''Is there SPI Flash?'''

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

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

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

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

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

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

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

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

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

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

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

== How-to ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (or the USB-C to USB-C cable)
* Some knowledge of your variation of Android

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

=== Auto-rotating the Screen ===
* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* By default, the screen will only rotate while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor-->Display Configuration-->Uncheck "Only when in tablet mode" and click "Apply."

=== Rotating the Login Screen ===
By default, the login screen is set to display in portrait mode. If you wish to change it to landscape mode to match the keyboard while in the case, use the following steps ([https://forum.pine64.org/showthread.php?tid=18313 Credit to chzbacon]) :

* Install necessary software: <code>sudo pacman -S xorg-xrandr xorg-xinput</code>
* Edit /usr/share/sddm/scripts/Xsetup. For example, using nano: <code>sudo nano /usr/share/sddm/scripts/Xsetup</code> and add the following two lines to the end of file:
** <code>xrandr --output DSI-1 --mode 800x1280 --rate 60.00 --rotate right</code>
** <code>xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1</code>
* Now edit /etc/sddm.conf.d/sddm.conf, for example: <code>sudo nano /etc/sddm.conf.d/sddm.conf</code> and add the following two lines (case sensitive):
** <code>[X11]</code>
** <code>DisplayCommand=/usr/share/sddm/scripts/Xsetup</code>
*Reboot, and your login screen should now display in landscape mode.

== External Links ==

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

[[Category:Rockchip RK3566]]

PinePhone Installation Instructions

2023-07-18T19:20:24Z

Moobythegoldensock: Fixed link

This section has generic installation instructions.

For specific installation instructions for each distribution please see the software releases pages:

* for the '''PinePhone''': [[PinePhone Software Releases]]
* for the '''PinePhone Pro''': [[PinePhone Pro Software Releases]]
* for the '''PineTab2''': [[PineTab2 Releases]]

== Boot priority ==

=== PinePhone Pro ===

For details regarding the boot priority on the PinePhone Pro see [[PinePhone Pro#Boot order]].

=== PinePhone ===

The PinePhone always boots from the microSD card first. It is therefore recommended to have a microSD card handy. It is '''not''' possible to lock themself out of the phone when the installation on the internal storage (the eMMC) fails, as a correctly flashed microSD card will always boot. Note: Booting from USB is not supported by the hardware, a live USB stick will not boot.

The phone will also try to boot from microSD cards, which were previously flashed with an OS and formatted later, causing the phone to fail to boot. See [[#Reuse SD card for data storage on system booting from eMMC|reuse SD card]] on how to format the microSD card properly, including wiping the residues of u-boot.

=== PineTab2===

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

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

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

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info above). It should now boot the new operating system from the microSD card.

== Installation to the microSD ==

To install an image to the microSD card:

# Download your chosen image from [[PinePhone Software Releases]] for the regular '''PinePhone'', [[PinePhone Pro Software Releases]] for the '''PinePhone Pro''', or [[PineTab2 Releases]] for the '''PineTab2.'''
# Extract the compressed file
# Write the image to your microSD card, see below
# Plug microSD card into phone (make sure to use the top slot, not the bottom slot)
# On the '''PinePhone Pro''': The eMMC might have to be disconnected to boot from the microSD card, see [[PinePhone Pro#Boot order]]
# Boot phone

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the micro-SIM in the lower slot.]]

=== Flashing the microSD ===
==== Using dd ====
Make sure to select the correct device using <code>lsblk</code>. Then run <code>dd</code> with the selected device:

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

{{Info|The image needs to be written to the whole device, not to partition 1. Make sure you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target.}}

==== Using bmaptool ====
Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device:

Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 Gb file.

==== Using graphical tools ====
GUI applications such as Etcher and GNOME Disks can be used to flash the microSD too.
* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

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

== Installation to the eMMC ==

=== From the booted microSD OS ===
# Flash an OS to the microSD card (and optionally resize the partition, see below)
# Insert microSD card and boot the device (phone or tablet)
# Download the desired OS' image on the booted OS or transfer it to the microSD card
# Extract the image file if it is archived
# Flash the image file to eMMC using <code>dd if='''IMAGE.img''' of=/dev/'''mmcblkX''' bs=1M status=progress conv=fsync</code> where X is the number label of the eMMC (of the disk, not the partition!). Use the command <code>lsblk</code> to check your devices: typically with the current kernel the microSD card is ''/dev/mmcblk0'' and the eMMC is ''/dev/mmcblk2'' but as always with ''dd'' be extremely cautious to get the devices correct.
# Turn off device, remove microSD card and then turn on the device.

=== Using JumpDrive ===

{{Info|This only applies to the regular '''PinePhone''', not the '''PinePhone Pro''' or '''PineTab2'''.}}

[[File:jumpdrive.jpg|400px|thumb|right|Jumpdrive running on the PinePhone]]
The internal eMMC flash storage can be flashed using the Jumpdrive utility by Danct12 and Martijn from postmarketOS.
This utility boots from micro SD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.
The process of flashing an OS to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card. You can use the dd command or a utility such as Etcher or Gnome Disks, etc.

Latest Jumpdrive can be found [https://github.com/dreemurrs-embedded/Jumpdrive/releases/ here].

# Download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]
# Flash the Jumpdrive image to a microSD card
# Boot the PinePhone from the Jumpdrive microSD card
# Connect the PinePhone to your computer using USB-A -> USB-C cable
# Flash the exposed PinePhone drive (e.g. ''/dev/mm...'', check for the right device in <code>dmesg</code>, GNOME disks, or similar, and make sure it's unmounted) with your chosen OS image
# Once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive microSD card
# The process is now finished, and you can boot from eMMC

The Jumpdrive image is smaller than 50MB. You can keep an microSD card specifically for using Jumpdrive, and there are 64MB microSD cards sold cheaply that will suffice. Jumpdrive also acts as a rescue image in case if you messed up your installation. To do so, you can telnet to '''172.16.42.1''', mount rootfs and fix it!

=== SD to eMMC via installer ===

An special installer image booted from the microSD card can be used to flash the eMMC as well. Mobian and postmarketOS installer images for the Pinephone series and the PineTab 2 factory image booted from microSD card will simply ask the user if they want to install to eMMC. The feature lives in the distribution-agnostic calamares-extensions repository (see [https://github.com/calamares/calamares-extensions/pull/7 calamares-extensions#7]), so other distributions might adopt this in the future.

=== Using Tow-Boot ===

Tow-Boot is an opinionated distribution of the U-Boot bootloader. It includes an USB Mass Storage Mode, which exposes the flash drive(s) to a computer connected to the phone via USB-C. The Tow-Boot bootloader has to be installed if it is not pre-installed already. For instructions see the following links:

* '''PinePhone:''' https://tow-boot.org/devices/pine64-pinephoneA64.html
* '''PinePhone Pro:''' https://tow-boot.org/devices/pine64-pinephonePro.html

If Tow-Boot is installed the phone can be started into USB Mass Storage Mode by holding the ''volume up'' key on startup.

The steps of flashing an operating system to the phone after booting Tow-Boot's USB Mass Storage Mode and connecting the phone to a computer is identical to that of any other storage medium - e.g. a microSD card. You can use the dd command or a utility such as Etcher or Gnome Disks from the computer the phone is connected to.

== Resize partition to fit disk space ==

{{Info|Many operating systems already include a script, which is resizing the partition on first boot, where this step is not required.}}

Once you've flashed the OS to your microSD card or eMMC storage, you may also need to expand the partition to fill all the available space.

=== Resize SD card's partition using computer ===

For microSD cards, insert the microSD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image. To do the flashing you have two options:

==== Using Growpart ====

Install growpart and run:
growpart /dev/'''mmcblkX''' '''Y'''
resize2fs /dev/'''mmcblkXpY'''
where ''X'' is the storage device and ''Y'' is the partition number (viewable from <code>lsblk</code>).

If you get any errors about missing or unknown commands, use <code>apt-cache search</code> to find and install the needed software. Also don't forget to use <code>sudo</code>.

==== Using Parted ====

Parted's interactive mode and resize work well together. Do this before you put your microSD card into your device for the first time for best results.

sudo parted /dev/'''<your_sd_card_device>'''
(parted) resizepart 2 100%
(parted) quit
sudo resize2fs /dev/'''<the_second_sd_card_PARTITION>'''

=== Resize from within the Device ===

eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the microSD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. If you booted from the microSD card, you can follow the above guidelines on how to resize from a computer.

MicroSD card: It is generally not possible to boot from eMMC to partition the unmounted microSD card, because of the boot order - you would have to write the image to the empty microSD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the microSD card while booted from microSD card! Resizing a currently mounted partition can have weird results.

== Reuse SD card for data storage on system booting from eMMC==
Once you have installed your release of choice to eMMC, you may wish to use an microSD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the microSD card to store boot software, which you need to clear.

This can be done as follows on any Linux system:
lsblk
to check the device of your microSD card – as an example lets assume it is /dev/mmcblk0
then
sudo dd if=/dev/zero of=/dev/'''[DEVICE]''' bs=8k seek=1 count=4
will clear the relevant sectors of your card.

Since Danctnix (arch) switched to a gpt partition table from mbr in May of 2022 it installs u-boot at an offset of 128k instead of 8k, which means this command must be used instead
sudo dd if=/dev/zero of=/dev/'''[DEVICE]''' bs=32k seek=4 count=1

== Web resources ==

* [https://www.youtube.com/watch?v=7HMkU43P9hw Youtube video on how to flash OS images on the Pinephone (SD or eMMC) by Tech Pills]
* [https://www.youtube.com/watch?v=u65dofYFAPY Youtube video on How to install different operating systems on the PinePhone plus an Mobian overview by Elatronion]

[[Category:PinePhone]][[Category:Guide]]

PinePhone Installation Instructions

2023-07-18T19:13:27Z

Moobythegoldensock: PineTab2 boot order

This section has generic installation instructions.

For specific installation instructions for each distribution please see the software releases pages:

* for the '''PinePhone''': [[PinePhone Software Releases]]
* for the '''PinePhone Pro''': [[PinePhone Pro Software Releases]]
* for the '''PineTab2''': [[PineTab2]]

== Boot priority ==

=== PinePhone Pro ===

For details regarding the boot priority on the PinePhone Pro see [[PinePhone Pro#Boot order]].

=== PinePhone ===

The PinePhone always boots from the microSD card first. It is therefore recommended to have a microSD card handy. It is '''not''' possible to lock themself out of the phone when the installation on the internal storage (the eMMC) fails, as a correctly flashed microSD card will always boot. Note: Booting from USB is not supported by the hardware, a live USB stick will not boot.

The phone will also try to boot from microSD cards, which were previously flashed with an OS and formatted later, causing the phone to fail to boot. See [[#Reuse SD card for data storage on system booting from eMMC|reuse SD card]] on how to format the microSD card properly, including wiping the residues of u-boot.

=== PineTab2===

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

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

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

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info above). It should now boot the new operating system from the microSD card.

== Installation to the microSD ==

To install an image to the microSD card:

# Download your chosen image from [[PinePhone Software Releases]] for the regular '''PinePhone'', [[PinePhone Pro Software Releases]] for the '''PinePhone Pro''', or [[PineTab2 Releases]] for the '''PineTab2.'''
# Extract the compressed file
# Write the image to your microSD card, see below
# Plug microSD card into phone (make sure to use the top slot, not the bottom slot)
# On the '''PinePhone Pro''': The eMMC might have to be disconnected to boot from the microSD card, see [[PinePhone Pro#Boot order]]
# Boot phone

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the micro-SIM in the lower slot.]]

=== Flashing the microSD ===
==== Using dd ====
Make sure to select the correct device using <code>lsblk</code>. Then run <code>dd</code> with the selected device:

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

{{Info|The image needs to be written to the whole device, not to partition 1. Make sure you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target.}}

==== Using bmaptool ====
Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device:

Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 Gb file.

==== Using graphical tools ====
GUI applications such as Etcher and GNOME Disks can be used to flash the microSD too.
* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

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

== Installation to the eMMC ==

=== From the booted microSD OS ===
# Flash an OS to the microSD card (and optionally resize the partition, see below)
# Insert microSD card and boot the device (phone or tablet)
# Download the desired OS' image on the booted OS or transfer it to the microSD card
# Extract the image file if it is archived
# Flash the image file to eMMC using <code>dd if='''IMAGE.img''' of=/dev/'''mmcblkX''' bs=1M status=progress conv=fsync</code> where X is the number label of the eMMC (of the disk, not the partition!). Use the command <code>lsblk</code> to check your devices: typically with the current kernel the microSD card is ''/dev/mmcblk0'' and the eMMC is ''/dev/mmcblk2'' but as always with ''dd'' be extremely cautious to get the devices correct.
# Turn off device, remove microSD card and then turn on the device.

=== Using JumpDrive ===

{{Info|This only applies to the regular '''PinePhone''', not the '''PinePhone Pro''' or '''PineTab2'''.}}

[[File:jumpdrive.jpg|400px|thumb|right|Jumpdrive running on the PinePhone]]
The internal eMMC flash storage can be flashed using the Jumpdrive utility by Danct12 and Martijn from postmarketOS.
This utility boots from micro SD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.
The process of flashing an OS to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card. You can use the dd command or a utility such as Etcher or Gnome Disks, etc.

Latest Jumpdrive can be found [https://github.com/dreemurrs-embedded/Jumpdrive/releases/ here].

# Download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]
# Flash the Jumpdrive image to a microSD card
# Boot the PinePhone from the Jumpdrive microSD card
# Connect the PinePhone to your computer using USB-A -> USB-C cable
# Flash the exposed PinePhone drive (e.g. ''/dev/mm...'', check for the right device in <code>dmesg</code>, GNOME disks, or similar, and make sure it's unmounted) with your chosen OS image
# Once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive microSD card
# The process is now finished, and you can boot from eMMC

The Jumpdrive image is smaller than 50MB. You can keep an microSD card specifically for using Jumpdrive, and there are 64MB microSD cards sold cheaply that will suffice. Jumpdrive also acts as a rescue image in case if you messed up your installation. To do so, you can telnet to '''172.16.42.1''', mount rootfs and fix it!

=== SD to eMMC via installer ===

An special installer image booted from the microSD card can be used to flash the eMMC as well. Mobian and postmarketOS installer images for the Pinephone series and the PineTab 2 factory image booted from microSD card will simply ask the user if they want to install to eMMC. The feature lives in the distribution-agnostic calamares-extensions repository (see [https://github.com/calamares/calamares-extensions/pull/7 calamares-extensions#7]), so other distributions might adopt this in the future.

=== Using Tow-Boot ===

Tow-Boot is an opinionated distribution of the U-Boot bootloader. It includes an USB Mass Storage Mode, which exposes the flash drive(s) to a computer connected to the phone via USB-C. The Tow-Boot bootloader has to be installed if it is not pre-installed already. For instructions see the following links:

* '''PinePhone:''' https://tow-boot.org/devices/pine64-pinephoneA64.html
* '''PinePhone Pro:''' https://tow-boot.org/devices/pine64-pinephonePro.html

If Tow-Boot is installed the phone can be started into USB Mass Storage Mode by holding the ''volume up'' key on startup.

The steps of flashing an operating system to the phone after booting Tow-Boot's USB Mass Storage Mode and connecting the phone to a computer is identical to that of any other storage medium - e.g. a microSD card. You can use the dd command or a utility such as Etcher or Gnome Disks from the computer the phone is connected to.

== Resize partition to fit disk space ==

{{Info|Many operating systems already include a script, which is resizing the partition on first boot, where this step is not required.}}

Once you've flashed the OS to your microSD card or eMMC storage, you may also need to expand the partition to fill all the available space.

=== Resize SD card's partition using computer ===

For microSD cards, insert the microSD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image. To do the flashing you have two options:

==== Using Growpart ====

Install growpart and run:
growpart /dev/'''mmcblkX''' '''Y'''
resize2fs /dev/'''mmcblkXpY'''
where ''X'' is the storage device and ''Y'' is the partition number (viewable from <code>lsblk</code>).

If you get any errors about missing or unknown commands, use <code>apt-cache search</code> to find and install the needed software. Also don't forget to use <code>sudo</code>.

==== Using Parted ====

Parted's interactive mode and resize work well together. Do this before you put your microSD card into your device for the first time for best results.

sudo parted /dev/'''<your_sd_card_device>'''
(parted) resizepart 2 100%
(parted) quit
sudo resize2fs /dev/'''<the_second_sd_card_PARTITION>'''

=== Resize from within the Device ===

eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the microSD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. If you booted from the microSD card, you can follow the above guidelines on how to resize from a computer.

MicroSD card: It is generally not possible to boot from eMMC to partition the unmounted microSD card, because of the boot order - you would have to write the image to the empty microSD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the microSD card while booted from microSD card! Resizing a currently mounted partition can have weird results.

== Reuse SD card for data storage on system booting from eMMC==
Once you have installed your release of choice to eMMC, you may wish to use an microSD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the microSD card to store boot software, which you need to clear.

This can be done as follows on any Linux system:
lsblk
to check the device of your microSD card – as an example lets assume it is /dev/mmcblk0
then
sudo dd if=/dev/zero of=/dev/'''[DEVICE]''' bs=8k seek=1 count=4
will clear the relevant sectors of your card.

Since Danctnix (arch) switched to a gpt partition table from mbr in May of 2022 it installs u-boot at an offset of 128k instead of 8k, which means this command must be used instead
sudo dd if=/dev/zero of=/dev/'''[DEVICE]''' bs=32k seek=4 count=1

== Web resources ==

* [https://www.youtube.com/watch?v=7HMkU43P9hw Youtube video on how to flash OS images on the Pinephone (SD or eMMC) by Tech Pills]
* [https://www.youtube.com/watch?v=u65dofYFAPY Youtube video on How to install different operating systems on the PinePhone plus an Mobian overview by Elatronion]

[[Category:PinePhone]][[Category:Guide]]

PinePhone Installation Instructions

2023-07-18T19:08:32Z

Moobythegoldensock: Added PineTab2 info. If this change is reverted, please also revert the removal of boot info from the PineTab2 page.

This section has generic installation instructions.

For specific installation instructions for each distribution please see the software releases pages:

* for the '''PinePhone''': [[PinePhone Software Releases]]
* for the '''PinePhone Pro''': [[PinePhone Pro Software Releases]]
* for the '''PineTab2''': [[PineTab2]]

== Boot priority ==

=== PinePhone Pro ===

For details regarding the boot priority on the PinePhone Pro see [[PinePhone Pro#Boot order]].

=== PinePhone ===

The PinePhone always boots from the microSD card first. It is therefore recommended to have a microSD card handy. It is '''not''' possible to lock themself out of the phone when the installation on the internal storage (the eMMC) fails, as a correctly flashed microSD card will always boot. Note: Booting from USB is not supported by the hardware, a live USB stick will not boot.

The phone will also try to boot from microSD cards, which were previously flashed with an OS and formatted later, causing the phone to fail to boot. See [[#Reuse SD card for data storage on system booting from eMMC|reuse SD card]] on how to format the microSD card properly, including wiping the residues of u-boot.

=== PineTab2===

For details regarding the boot priority on the PineTab2 see [[PineTab2#Installation Instructions]]

== Installation to the microSD ==

To install an image to the microSD card:

# Download your chosen image from [[PinePhone Software Releases]] for the regular '''PinePhone'', [[PinePhone Pro Software Releases]] for the '''PinePhone Pro''', or [[PineTab2 Releases]] for the '''PineTab2.'''
# Extract the compressed file
# Write the image to your microSD card, see below
# Plug microSD card into phone (make sure to use the top slot, not the bottom slot)
# On the '''PinePhone Pro''': The eMMC might have to be disconnected to boot from the microSD card, see [[PinePhone Pro#Boot order]]
# Boot phone

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the micro-SIM in the lower slot.]]

=== Flashing the microSD ===
==== Using dd ====
Make sure to select the correct device using <code>lsblk</code>. Then run <code>dd</code> with the selected device:

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

{{Info|The image needs to be written to the whole device, not to partition 1. Make sure you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target.}}

==== Using bmaptool ====
Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device:

Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 Gb file.

==== Using graphical tools ====
GUI applications such as Etcher and GNOME Disks can be used to flash the microSD too.
* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

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

== Installation to the eMMC ==

=== From the booted microSD OS ===
# Flash an OS to the microSD card (and optionally resize the partition, see below)
# Insert microSD card and boot the device (phone or tablet)
# Download the desired OS' image on the booted OS or transfer it to the microSD card
# Extract the image file if it is archived
# Flash the image file to eMMC using <code>dd if='''IMAGE.img''' of=/dev/'''mmcblkX''' bs=1M status=progress conv=fsync</code> where X is the number label of the eMMC (of the disk, not the partition!). Use the command <code>lsblk</code> to check your devices: typically with the current kernel the microSD card is ''/dev/mmcblk0'' and the eMMC is ''/dev/mmcblk2'' but as always with ''dd'' be extremely cautious to get the devices correct.
# Turn off device, remove microSD card and then turn on the device.

=== Using JumpDrive ===

{{Info|This only applies to the regular '''PinePhone''', not the '''PinePhone Pro''' or '''PineTab2'''.}}

[[File:jumpdrive.jpg|400px|thumb|right|Jumpdrive running on the PinePhone]]
The internal eMMC flash storage can be flashed using the Jumpdrive utility by Danct12 and Martijn from postmarketOS.
This utility boots from micro SD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.
The process of flashing an OS to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card. You can use the dd command or a utility such as Etcher or Gnome Disks, etc.

Latest Jumpdrive can be found [https://github.com/dreemurrs-embedded/Jumpdrive/releases/ here].

# Download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]
# Flash the Jumpdrive image to a microSD card
# Boot the PinePhone from the Jumpdrive microSD card
# Connect the PinePhone to your computer using USB-A -> USB-C cable
# Flash the exposed PinePhone drive (e.g. ''/dev/mm...'', check for the right device in <code>dmesg</code>, GNOME disks, or similar, and make sure it's unmounted) with your chosen OS image
# Once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive microSD card
# The process is now finished, and you can boot from eMMC

The Jumpdrive image is smaller than 50MB. You can keep an microSD card specifically for using Jumpdrive, and there are 64MB microSD cards sold cheaply that will suffice. Jumpdrive also acts as a rescue image in case if you messed up your installation. To do so, you can telnet to '''172.16.42.1''', mount rootfs and fix it!

=== SD to eMMC via installer ===

An special installer image booted from the microSD card can be used to flash the eMMC as well. Mobian and postmarketOS installer images for the Pinephone series and the PineTab 2 factory image booted from microSD card will simply ask the user if they want to install to eMMC. The feature lives in the distribution-agnostic calamares-extensions repository (see [https://github.com/calamares/calamares-extensions/pull/7 calamares-extensions#7]), so other distributions might adopt this in the future.

=== Using Tow-Boot ===

Tow-Boot is an opinionated distribution of the U-Boot bootloader. It includes an USB Mass Storage Mode, which exposes the flash drive(s) to a computer connected to the phone via USB-C. The Tow-Boot bootloader has to be installed if it is not pre-installed already. For instructions see the following links:

* '''PinePhone:''' https://tow-boot.org/devices/pine64-pinephoneA64.html
* '''PinePhone Pro:''' https://tow-boot.org/devices/pine64-pinephonePro.html

If Tow-Boot is installed the phone can be started into USB Mass Storage Mode by holding the ''volume up'' key on startup.

The steps of flashing an operating system to the phone after booting Tow-Boot's USB Mass Storage Mode and connecting the phone to a computer is identical to that of any other storage medium - e.g. a microSD card. You can use the dd command or a utility such as Etcher or Gnome Disks from the computer the phone is connected to.

== Resize partition to fit disk space ==

{{Info|Many operating systems already include a script, which is resizing the partition on first boot, where this step is not required.}}

Once you've flashed the OS to your microSD card or eMMC storage, you may also need to expand the partition to fill all the available space.

=== Resize SD card's partition using computer ===

For microSD cards, insert the microSD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image. To do the flashing you have two options:

==== Using Growpart ====

Install growpart and run:
growpart /dev/'''mmcblkX''' '''Y'''
resize2fs /dev/'''mmcblkXpY'''
where ''X'' is the storage device and ''Y'' is the partition number (viewable from <code>lsblk</code>).

If you get any errors about missing or unknown commands, use <code>apt-cache search</code> to find and install the needed software. Also don't forget to use <code>sudo</code>.

==== Using Parted ====

Parted's interactive mode and resize work well together. Do this before you put your microSD card into your device for the first time for best results.

sudo parted /dev/'''<your_sd_card_device>'''
(parted) resizepart 2 100%
(parted) quit
sudo resize2fs /dev/'''<the_second_sd_card_PARTITION>'''

=== Resize from within the Device ===

eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the microSD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. If you booted from the microSD card, you can follow the above guidelines on how to resize from a computer.

MicroSD card: It is generally not possible to boot from eMMC to partition the unmounted microSD card, because of the boot order - you would have to write the image to the empty microSD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the microSD card while booted from microSD card! Resizing a currently mounted partition can have weird results.

== Reuse SD card for data storage on system booting from eMMC==
Once you have installed your release of choice to eMMC, you may wish to use an microSD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the microSD card to store boot software, which you need to clear.

This can be done as follows on any Linux system:
lsblk
to check the device of your microSD card – as an example lets assume it is /dev/mmcblk0
then
sudo dd if=/dev/zero of=/dev/'''[DEVICE]''' bs=8k seek=1 count=4
will clear the relevant sectors of your card.

Since Danctnix (arch) switched to a gpt partition table from mbr in May of 2022 it installs u-boot at an offset of 128k instead of 8k, which means this command must be used instead
sudo dd if=/dev/zero of=/dev/'''[DEVICE]''' bs=32k seek=4 count=1

== Web resources ==

* [https://www.youtube.com/watch?v=7HMkU43P9hw Youtube video on how to flash OS images on the Pinephone (SD or eMMC) by Tech Pills]
* [https://www.youtube.com/watch?v=u65dofYFAPY Youtube video on How to install different operating systems on the PinePhone plus an Mobian overview by Elatronion]

[[Category:PinePhone]][[Category:Guide]]

PineTab2

2023-07-09T14:15:06Z

Moobythegoldensock: wording

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

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

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

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

== Getting started ==

The PineTab2 box contains two smaller boxes. The first package includes the PineTab2, a short user guide, a power cable and the UART adapter Note that the UART adapter is in the same package as the power cable in a second compartment and can be a bit hidden, search for it. The second box has the keyboard in it.

=== First start ===

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

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

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

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

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

== Software ==

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

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

=== Releases ===

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

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

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

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

=== Installation instructions ===

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

'''Preparing the microSD card'''

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

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

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

Graphical applications:

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

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

Command-line tools:

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

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

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

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

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

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

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Keyboard ==

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

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

== Specifications ==

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

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

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

=== Known Issues ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

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

* Plug the adapter face-up in the USB-C port furthest away from the power button. If all the lights are lit, you have the wrong port: only the green light should be lit when you first plug it in.
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

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

PineTab2 mainboard schematic:

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

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

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:

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

== Frequently Asked Questions ==

'''Does the Tablet support a Pen?'''

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

'''Can I run Android on it?'''

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

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

'''Is there SPI Flash?'''

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

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

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

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

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

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

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

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

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

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

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

== How-to ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (or the USB-C to USB-C cable)
* Some knowledge of your variation of Android

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

=== Auto-rotating the Screen ===
* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* By default, the screen will only rotate while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor-->Display Configuration-->Uncheck "Only when in tablet mode" and click "Apply."

=== Rotating the Login Screen ===
By default, the login screen is set to display in portrait mode. If you wish to change it to landscape mode to match the keyboard while in the case, use the following steps ([https://forum.pine64.org/showthread.php?tid=18313 Credit to chzbacon]) :

* Install necessary software: <code>sudo pacman -S xorg-xrandr xorg-xinput</code>
* Edit /usr/share/sddm/scripts/Xsetup. For example, using nano: <code>sudo nano /usr/share/sddm/scripts/Xsetup</code> and add the following two lines to the end of file:
** <code>xrandr --output DSI-1 --mode 800x1280 --rate 60.00 --rotate right</code>
** <code>xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1</code>
* Now edit /etc/sddm.conf.d/sddm.conf, for example: <code>sudo nano /etc/sddm.conf.d/sddm.conf</code> and add the following two lines (case sensitive):
** <code>[X11]</code>
** <code>DisplayCommand=/usr/share/sddm/scripts/Xsetup</code>
*Reboot, and your login screen should now display in landscape mode.

== External Links ==

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

[[Category:Rockchip RK3566]]

PineTab2

2023-07-09T14:12:41Z

Moobythegoldensock: UART clarification

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

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

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

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

== Getting started ==

The PineTab2 box contains two smaller boxes. The first package includes the PineTab2, a short user guide, a power cable and the UART adapter Note that the UART adapter is in the same package as the power cable in a second compartment and can be a bit hidden, search for it. The second box has the keyboard in it.

=== First start ===

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

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

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

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

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

== Software ==

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

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

=== Releases ===

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

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

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

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

=== Installation instructions ===

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

'''Preparing the microSD card'''

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

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

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

Graphical applications:

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

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

Command-line tools:

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

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

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

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

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

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

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Keyboard ==

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

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

== Specifications ==

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

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

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

=== Known Issues ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

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

* Plug the adapter face-up in the USB-C port furthest away from the power button. If you see red and blue lights, you have the wrong port: only the green light should be lit.
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

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

PineTab2 mainboard schematic:

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

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

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:

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

== Frequently Asked Questions ==

'''Does the Tablet support a Pen?'''

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

'''Can I run Android on it?'''

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

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

'''Is there SPI Flash?'''

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

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

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

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

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

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

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

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

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

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

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

== How-to ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (or the USB-C to USB-C cable)
* Some knowledge of your variation of Android

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

=== Auto-rotating the Screen ===
* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* By default, the screen will only rotate while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor-->Display Configuration-->Uncheck "Only when in tablet mode" and click "Apply."

=== Rotating the Login Screen ===
By default, the login screen is set to display in portrait mode. If you wish to change it to landscape mode to match the keyboard while in the case, use the following steps ([https://forum.pine64.org/showthread.php?tid=18313 Credit to chzbacon]) :

* Install necessary software: <code>sudo pacman -S xorg-xrandr xorg-xinput</code>
* Edit /usr/share/sddm/scripts/Xsetup. For example, using nano: <code>sudo nano /usr/share/sddm/scripts/Xsetup</code> and add the following two lines to the end of file:
** <code>xrandr --output DSI-1 --mode 800x1280 --rate 60.00 --rotate right</code>
** <code>xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1</code>
* Now edit /etc/sddm.conf.d/sddm.conf, for example: <code>sudo nano /etc/sddm.conf.d/sddm.conf</code> and add the following two lines (case sensitive):
** <code>[X11]</code>
** <code>DisplayCommand=/usr/share/sddm/scripts/Xsetup</code>
*Reboot, and your login screen should now display in landscape mode.

== External Links ==

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

[[Category:Rockchip RK3566]]

PineTab2

2023-07-08T21:57:59Z

Moobythegoldensock: Rotate Login Screen

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

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

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

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

== Getting started ==

The PineTab2 box contains two smaller boxes. The first package includes the PineTab2, a short user guide, a power cable and the UART adapter Note that the UART adapter is in the same package as the power cable in a second compartment and can be a bit hidden, search for it. The second box has the keyboard in it.

=== First start ===

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

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

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

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

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

== Software ==

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

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

=== Releases ===

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

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

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

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

=== Installation instructions ===

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

'''Preparing the microSD card'''

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

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

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

Graphical applications:

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

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

Command-line tools:

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

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

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

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

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

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

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Keyboard ==

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

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

== Specifications ==

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

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

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

=== Known Issues ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

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

* Plug the adapter in the USB-C port furthest away from the power button
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

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

PineTab2 mainboard schematic:

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

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

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:

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

== Frequently Asked Questions ==

'''Does the Tablet support a Pen?'''

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

'''Can I run Android on it?'''

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

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

'''Is there SPI Flash?'''

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

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

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

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

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

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

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

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

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

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

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

== How-to ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (or the USB-C to USB-C cable)
* Some knowledge of your variation of Android

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

=== Auto-rotating the Screen ===
* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* By default, the screen will only rotate while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor-->Display Configuration-->Uncheck "Only when in tablet mode" and click "Apply."

=== Rotating the Login Screen ===
By default, the login screen is set to display in portrait mode. If you wish to change it to landscape mode to match the keyboard while in the case, use the following steps ([https://forum.pine64.org/showthread.php?tid=18313 Credit to chzbacon]) :

* Install necessary software: <code>sudo pacman -S xorg-xrandr xorg-xinput</code>
* Edit /usr/share/sddm/scripts/Xsetup. For example, using nano: <code>sudo nano /usr/share/sddm/scripts/Xsetup</code> and add the following two lines to the end of file:
** <code>xrandr --output DSI-1 --mode 800x1280 --rate 60.00 --rotate right</code>
** <code>xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1</code>
* Now edit /etc/sddm.conf.d/sddm.conf, for example: <code>sudo nano /etc/sddm.conf.d/sddm.conf</code> and add the following two lines (case sensitive):
** <code>[X11]</code>
** <code>DisplayCommand=/usr/share/sddm/scripts/Xsetup</code>
*Reboot, and your login screen should now display in landscape mode.

== External Links ==

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

[[Category:Rockchip RK3566]]

PineTab2 Releases

2023-07-08T21:17:14Z

Moobythegoldensock: Added PostmarketOS

This page contains a list of all available releases and tools for the [[PineTab2]] in alphabetical order.

The installation instructions can be found under [[PineTab2#Installation instructions]].

__TOC__

== Linux ==

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

(Unofficial) Arch Linux ARM maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

==== Download ====

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz

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

==== Notes ====

* Currently ships without a Wi-Fi and Bluetooth driver
* [https://wiki.archlinux.org/title/SDDM#KDE_Plasma_Wayland_hangs_on_shutdown_and_reboot system hangs on reboot/shutdown] (SDDM bug, workaround possible)
* [https://forum.pine64.org/showthread.php?tid=18313 screen rotated 90°, workaround possible]
* [https://github.com/ScottFreeCode/Pine64-Arch/tree/master/PKGBUILDS/pine64/alsa-ucm-pinetab2 HP/Speaker switching via Alsa UCM]

----

=== Buildroot ===
[[File:Buildroot.png|right|100px]]

Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation.

An external tree for the PINE64 PineTab2 is developed and maintained by ''Danct12'' (same developer behind the PineTab2 port of ''Arch Linux ARM'').

==== Download ====

* The repository and build instructions can be found [https://github.com/Danct12/buildroot_pinetab2 here].

----

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

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh. The current version of the base Debian system is Debian Bookworm. See the installation instructions [https://wiki.debian.org/InstallingDebianOn/PINE64/PineTab2 here]. If you have questions about Mobian, please ask them in the [https://matrix.to/#/#mobian:matrix.org Mobian Matrix room].

==== Download ====

* [https://images.mobian.org/pinetab2/ Images]

{{Info|U-Boot is required to boot the images. If you have the factory image installed and updated to the latest version, you can boot Mobian from an SD card without installing U-Boot.}}

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

==== Notes ====
* The development is work in progress. Mobian's support for the PineTab2 is maintained by [https://salsa.debian.org/julianfairfax Julian]. The Mobian wiki can be found [https://wiki.mobian-project.org/ here].
* In order to connect to the device using SSH/SCP, you need to install SSH on the device. You can do this by executing the following in a shell: "sudo apt-get install ssh", afterwards you can connect via SSH/SCP using the PineTab2's IP address on port 22.
* When installing Mobian with full disk encryption and booting with the keyboard case connected, you will have to touch the screen or press a key to show the decryption screen. This is an [https://gitlab.com/postmarketOS/osk-sdl/-/issues/148 upstream issue].

----

=== NixOS ===
[[File:NixOS.webp|right|100px]]

NixOS is an immutable Linux distribution built around the Nix configuration language. The NixOS image for PineTab2 uses some downstream modifications to packages, such as an U-Boot package based on 2023.07-rc4 and a kernel also used by the Arch Linux Arm image.

This image is extremely basic and currently boots to a console. A NixOS configuration can be applied after booting to gain a full graphical system.

==== Download ====

* https://github.com/nabam/nixos-rockchip/releases

==== Notes ====

After booting, download this flake to the pinetab and place it at '''/etc/nixos/flake.nix''':

* https://git.asonix.dog/asonix/pinetab2-nixos/raw/branch/main/flake.nix

Run the following commands:

$ sudo su
> cd
> nixos-rebuild switch
> nixos-rebuild switch # yes, do it two times
> reboot

After rebooting, there will be a new user account.

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

----

=== postmarketOS ===
[[File:PostmarketOS_logo.png|right|80px]]

'''postmarketOS''' extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.

It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4 and more). As of writing, this distro is currently in testing and no official releases are available for download. Instead, users will need to create their own image with the distribution's install and development tool <code>pmbootstrap</code>.

====Download====
* [https://wiki.postmarketos.org/wiki/PINE64_PineTab_2_(pine64-pinetab2) Pinetab2 Device Page]
* Build the image with [https://wiki.postmarketos.org/wiki/Pmbootstrap pmbootstrap] and flash it to an SD.

----

=== Ubuntu Touch ===
[[File:Ubports-logo.png|right|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community. The port is currently maintained by Oren Klopfer (oklopfer).

The bootloader (u-boot) comes pre-flashed in the port. Installation just requires flashing the <code>.img.xz</code> to an SD or the eMMC.

==== Download ====

[https://gitlab.com/ook37/pinephone-pro-debos/-/releases UBports 20.04 PineTab2 Latest Releases]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| Set during boot
|-
! root
| <code>phablet/1234</code>
|}

==== Notes ====

Scroll down to the middle of [https://gitlab.com/ook37/pinephone-pro-debos/ the GitLab project page] to see which features work.

Contributions and bug reports can be made at the [https://gitlab.com/ook37/pinephone-pro-debos/ UBports PineTab2 GitLab page]. See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

----

=== Rhino Linux ===
[[File:rhino-linux-logo.png|right|100px]]

Rhino Linux is an Ubuntu-based distribution that uses the rolling-release model by tracking the <code>devel</code> branch of repositories. The port is currently maintained by Oren Klopfer (oklopfer).

The bootloader (u-boot) comes pre-flashed in the port. Installation just requires flashing the <code>.img.xz</code> to an SD or the eMMC.

==== Download ====
[https://rhinolinux.org/download/ Rhino Linux Downloads] (select Pine64 on the dropdown)

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

==== Notes ====
Foundational to the distribution is [https://pacstall.dev Pacstall], a Debian-based user repository inspired by the AUR. Additionally, RL comes with [https://rhinolinux.org/unicorn/ Unicorn], a custom modified version of XFCE with various modernizations and improvements, including auto-rotation for mobile devices.

[https://discord.gg/reSvc8Ztk3 Discord] - [https://matrix.to/#/#rolling-rhino-remix:matrix.org Matrix] - [https://github.com/rhino-linux GitHub] - [https://rhinolinux.org/wiki/ Wiki]

[[Category:Rockchip RK3566]]

PineTab2

2023-07-07T14:19:09Z

Moobythegoldensock: Auto-rotation instructions

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

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

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

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

== Getting started ==

The PineTab2 box contains two smaller boxes. The first package includes the PineTab2, a short user guide, a power cable and the UART adapter Note that the UART adapter is in the same package as the power cable in a second compartment and can be a bit hidden, search for it. The second box has the keyboard in it.

=== First start ===

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

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

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

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

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

== Software ==

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

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

=== Releases ===

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

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

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

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

=== Installation instructions ===

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

'''Preparing the microSD card'''

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

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

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

Graphical applications:

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

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

Command-line tools:

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

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

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

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

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

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

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Keyboard ==

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

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

== Specifications ==

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

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

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

=== Known Issues ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

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

* Plug the adapter in the USB-C port furthest away from the power button
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

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

PineTab2 mainboard schematic:

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

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

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:

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

== Frequently Asked Questions ==

'''Does the Tablet support a Pen?'''

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

'''Can I run Android on it?'''

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

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

'''Is there SPI Flash?'''

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

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

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

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

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

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

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

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

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

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

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

== How-to ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

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

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

=== Auto-rotating the Screen ===
* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* By default, the screen will only rotate while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor-->Display Configuration-->Uncheck "Only when in tablet mode" and click "Apply."

== External Links ==

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

[[Category:Rockchip RK3566]]

PineTab2

2023-07-07T10:35:14Z

Moobythegoldensock: britty —> brltty

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

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

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

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

== Getting started ==

The PineTab2 box contains two smaller boxes. The first package includes the PineTab2, a short user guide, a power cable and the UART adapter Note that the UART adapter is in the same package as the power cable in a second compartment and can be a bit hidden, search for it. The second box has the keyboard in it.

=== First start ===

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

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

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

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

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

== Software ==

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

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

=== Releases ===

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

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

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

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

=== Installation instructions ===

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

'''Preparing the microSD card'''

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

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

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

Graphical applications:

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

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

Command-line tools:

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

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

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

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

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

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

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Keyboard ==

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

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

== Specifications ==

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

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

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

=== Known Issues ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

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

* Plug the adapter in the USB-C port furthest away from the power button
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

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

PineTab2 mainboard schematic:

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

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

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:

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

== Frequently Asked Questions ==

'''Does the Tablet support a Pen?'''

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

'''Can I run Android on it?'''

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

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

'''Is there SPI Flash?'''

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

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

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

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

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

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

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

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

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

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

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

== How-to ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

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

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

== External Links ==

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

[[Category:Rockchip RK3566]]

PineTab2

2023-07-06T23:42:14Z

Moobythegoldensock: Troubleshooting uart for Ubuntu-based distros.

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

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

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

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

== Getting started ==

The PineTab2 box contains two smaller boxes. The first package includes the PineTab2, a short user guide, a power cable and the UART adapter Note that the UART adapter is in the same package as the power cable in a second compartment and can be a bit hidden, search for it. The second box has the keyboard in it.

=== First start ===

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

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

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

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

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

== Software ==

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

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

=== Releases ===

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

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

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

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

=== Installation instructions ===

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

'''Preparing the microSD card'''

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

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

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

Graphical applications:

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

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

Command-line tools:

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

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

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

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

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

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

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Keyboard ==

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

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

== Specifications ==

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

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

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

=== Known Issues ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

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

* Plug the adapter in the USB-C port furthest away from the power button
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the britty service is likely conflicting with this device. Britty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask britty.service</code>

== Board information, schematics and certifications ==

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

PineTab2 mainboard schematic:

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

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

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:

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

== Frequently Asked Questions ==

'''Does the Tablet support a Pen?'''

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

'''Can I run Android on it?'''

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

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

'''Is there SPI Flash?'''

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

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

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

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

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

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

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

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

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

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

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

== How-to ==

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

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

=== Networking using USB ===

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

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

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

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

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

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

You can use an Android phone as a network adapter.

You'll need:

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

Do the following in order:

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

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

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

Prerequisite:

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

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

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

Make sure to open the iPhone once you reconnect.

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

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

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

You'll need:

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

Do the following in order:

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

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

== External Links ==

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

[[Category:Rockchip RK3566]]

PineTab2

2023-06-03T14:27:45Z

Moobythegoldensock: Provided instructions for multi-state adapters and installing usb_modeswitch (not included in the default image.)