Maemo Leste Wiki - User contributions [en]

PinePhone

2022-08-16T04:10:40Z

Auanta: /* Make apps show up on desktop */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* '''VoLTE should work out-of-the-box.''' If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

To view a list of currently installed apps, do:

$ sudo apt list --installed | less

This should help you figure out for which apps to configure .desktop icons. A benefit with all this is that you can decide which apps you want to show or hide.

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key. It should be used in landscape mode for best results, as there are additional display issues in portrait mode.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

=== Customize the Keyboard ===

TODO: write this

=== More Tips & Tricks ===

Visit [https://leste.maemo.org/Tricks '''this page'''] for more general advice on customizing Maemo on your PinePhone.

[[Category:Device]]

PinePhone

2022-08-16T04:09:35Z

Auanta: /* More Tips & Tricks */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* '''VoLTE should work out-of-the-box.''' If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

To view a list of currently installed apps, do:

$ sudo apt list --installed | less

This should help you figure out for which apps to configure .desktop icons.

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key. It should be used in landscape mode for best results, as there are additional display issues in portrait mode.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

=== Customize the Keyboard ===

TODO: write this

=== More Tips & Tricks ===

Visit [https://leste.maemo.org/Tricks '''this page'''] for more general advice on customizing Maemo on your PinePhone.

[[Category:Device]]

PinePhone

2022-08-16T04:08:53Z

Auanta:

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* '''VoLTE should work out-of-the-box.''' If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

To view a list of currently installed apps, do:

$ sudo apt list --installed | less

This should help you figure out for which apps to configure .desktop icons.

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key. It should be used in landscape mode for best results, as there are additional display issues in portrait mode.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

=== Customize the Keyboard ===

TODO: write this

=== More Tips & Tricks ===

Visit [https://leste.maemo.org/Tricks this page] for more general advice on customizing Maemo on your PinePhone.

[[Category:Device]]

Tricks

2022-08-16T04:06:44Z

Auanta:

__FORCETOC__

= Randomize MAC Address =
Some users may wish to change the MAC address of an interface, for e.g. to prevent wifi networks associating their MAC address with their network usage pattern.

The macchanger package addresses this by either automatically or manually changing the MAC address of enabled interfaces.

apt install -y macchanger

During installation, the package configuration allows user to select automatic change of MAC address when interface is brought up. This may interfere with USB networking. As an alternative, user can manually change the wlan0 MAC.

macchanger wlan0 -e -a
ifconfig wlan0 up

= Keyboard / Mouse sharing with PC =
To use a Leste device while working at desktop it can be convenient to share mouse and keyboard of the host pc with the leste device. The 'barrier' client/server program, forked from 'synergy', allows this.

https://github.com/debauchee/barrier Barrier software-KVM switch

A hildonized Maemo-leste binary of the client is not available at time of this writing. Developers and testers may wish to disable undesired modules included with the barrier source, before compiling.

= Touchscreen support in Firefox (firefox-esr) =

Add the necessary environment variable:

echo "MOZ_USE_XINPUT2 DEFAULT=1" >> /etc/security/pam_env.conf

Then in firefox, open '''about:config''' and set '''dom.w3c_touch_events.enabled''' to '''1'''.

You can also set a mobile useragent by creating a string key called '''general.useragent.override'''.
Then set something like this:

Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0

= Customize console colors =

TODO: explain how to make console white on black text

PinePhone

2022-08-16T03:09:53Z

Auanta:

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* '''VoLTE should work out-of-the-box.''' If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

To view a list of currently installed apps, do:

$ sudo apt list --installed | less

This should help you figure out for which apps to configure .desktop icons.

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key. It should be used in landscape mode for best results, as there are additional display issues in portrait mode.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

=== Customize the Keyboard ===

TODO: write this

[[Category:Device]]

PinePhone

2022-08-16T03:04:18Z

Auanta: /* Make apps show up on desktop */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* '''VoLTE should work out-of-the-box.''' If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

To view a list of currently installed apps, do:

$ sudo apt list --installed | less

This should help you figure out for which apps to configure .desktop icons.

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key. It should be used in landscape mode for best results, as there are additional display issues in portrait mode.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

[[Category:Device]]

PinePhone

2022-08-16T03:03:26Z

Auanta: /* Make apps show up on desktop */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* '''VoLTE should work out-of-the-box.''' If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

To view a list of app currently installed apps, do:

$ sudo apt list --installed | less

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key. It should be used in landscape mode for best results, as there are additional display issues in portrait mode.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

[[Category:Device]]

PinePhone

2022-08-16T02:57:20Z

Auanta: /* Note about Calculator */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* '''VoLTE should work out-of-the-box.''' If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key. It should be used in landscape mode for best results, as there are additional display issues in portrait mode.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

[[Category:Device]]

PinePhone

2022-08-16T01:42:23Z

Auanta: /* Note about Calculator */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* '''VoLTE should work out-of-the-box.''' If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key. It should be used in landscape mode for best results.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

[[Category:Device]]

PinePhone

2022-08-16T01:02:53Z

Auanta: /* More Information */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* '''VoLTE should work out-of-the-box.''' If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

[[Category:Device]]

PinePhone

2022-08-16T01:01:21Z

Auanta: /* More Information */ update

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

[[Category:Device]]

PinePhone

2022-08-16T00:27:52Z

Auanta: /* Time zone / World Clock */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

[[Category:Device]]

PinePhone

2022-08-16T00:27:06Z

Auanta: more advice

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Unhide the keyboard ===

The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).

=== Note about Calculator ===

The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

[[Category:Device]]

Main Page

2022-08-15T23:36:13Z

Auanta: /* Description */ link to IRC channel about Matrix bridge

== Description ==

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, PinePhone, Allwinner Tablets and more.

You can find us on '''irc.libera.chat''', channel '''#maemo-leste''', you can [[IRC_channel|use Matrix]] to connect if you wish.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the [[Nokia_N900]], the [[Motorola Droid 4]] and the [[PinePhone]]. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.

== Useful resources, lists and pages ==

* To get started with a new install, see [[Getting_Started|Getting Started]].
* Read our [[Leste_FAQ|Frequently Asked Questions]]
* List of [[:Category:Device]] with support to varying degrees
* Latest downloadable images: https://phoenix.maemo.org/view/Images/
* List of "extras" software packages that have a wiki page: https://leste.maemo.org/Category:Extras
* Read how to get started with [[Development]]
* You have an application you want to see in Leste? Please let us know [[Wishlist|here]].
* For a list of presentations/talks featuring Maemo Leste, see [[Talks]]

== Links ==

<div>
The central point of meeting and talking is '''IRC''' ('''irc.libera.chat''' in '''#maemo-leste''') and this thread: https://talk.maemo.org/showthread.php?t=100192.

* Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

* Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

* Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

* Our Github subdomain: [https://maemo-leste.github.io/ https://maemo-leste.github.io/]

* Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

* Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/

* Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

* Our IRC chat history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt] and https://libera.irclog.whitequark.org/maemo-leste/ (previously: https://freenode.irclog.whitequark.org/maemo-leste/)

* Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

* Our Package index and info: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

* Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

* Our Forum [https://talk.maemo.org/forumdisplay.php?f=66 https://talk.maemo.org/forumdisplay.php?f=66]

* RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]

* Our Twitter: [https://twitter.com/maemoleste @maemoleste]

* Distrowatch: [https://distrowatch.com/dwres.php?resource=submit Maemo Leste] (give us an upvote)
</div>

PinePhone

2022-08-15T23:08:22Z

Auanta: /* Install Using Tow-Boot */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Make keyboard show on Firefox/Iceweasel ===

The keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar). This will be fixed in a future release (image tested: 20220731).

[[Category:Device]]

PinePhone

2022-08-15T22:56:29Z

Auanta:

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Make keyboard show on Firefox/Iceweasel ===

The keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar). This will be fixed in a future release (image tested: 20220731).

[[Category:Device]]

PinePhone

2022-08-15T22:52:23Z

Auanta: formatting, reorganizing

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Make keyboard show on Firefox/Iceweasel ===

The keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar).

[[Category:Device]]

PinePhone

2022-08-15T22:45:39Z

Auanta: /* From the booted microSD */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Make keyboard show on Firefox/Iceweasel ===

The keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar).

[[Category:Device]]

PinePhone

2022-08-15T22:45:16Z

Auanta: /* Using JumpDrive */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Install Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== From the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Make keyboard show on Firefox/Iceweasel ===

The keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar).

[[Category:Device]]

PinePhone

2022-08-15T22:44:59Z

Auanta: /* Using Tow-Boot */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install Using Tow-Boot ====

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== From the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Make keyboard show on Firefox/Iceweasel ===

The keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar).

[[Category:Device]]

PinePhone

2022-08-15T22:44:18Z

Auanta: /* From microSD card */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Using Tow-Boot ====

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== From the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Make keyboard show on Firefox/Iceweasel ===

The keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar).

[[Category:Device]]

PinePhone

2022-08-15T22:41:14Z

Auanta:

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== From microSD card ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Using Tow-Boot ====

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== From the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Make keyboard show on Firefox/Iceweasel ===

The keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar).

[[Category:Device]]

PinePhone

2022-08-15T22:36:49Z

Auanta: /* eMMC Installation */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== From microSD card ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Using Tow-Boot ====

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== From the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

[[Category:Device]]

PinePhone

2022-08-15T22:36:07Z

Auanta: reorganizing

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
''Note: Currently '''not working'''''

'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''
==== From microSD card ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Using Tow-Boot ====

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== From the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

[[Category:Device]]

PinePhone

2022-08-15T22:33:27Z

Auanta: Formatting

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== From microSD card ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

Modify the image to use eMMC paths. '''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

==== Using Tow-Boot ====

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

==== Using JumpDrive ====

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== From the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

[[Category:Device]]

PinePhone

2022-08-15T22:30:12Z

Auanta: formatting

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

[[Category:Device]]

PinePhone

2022-08-15T22:25:49Z

Auanta:

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

[[Category:Device]]

PinePhone

2022-08-15T22:25:04Z

Auanta: tip: desktop icons for apps

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

== Make apps show up on desktop ==

Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])

[[Category:Device]]

PinePhone

2022-08-15T22:23:16Z

Auanta: /* Installing apps */ moving to new section

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

[[Category:Device]]

PinePhone

2022-08-15T22:22:01Z

Auanta: /* Launching apps (such as Firefox/Iceweasel) */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
There is also the app store.

Note: Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

[[Category:Device]]

PinePhone

2022-08-15T22:20:31Z

Auanta: adding some tips

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== Installing apps ===

Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
There is also the app store.

Note: Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop ([https://wiki.archlinux.org/title/Desktop_entries examples])

=== Launching apps (such as Firefox/Iceweasel) ===

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

[[Category:Device]]

Main Page

2022-08-15T21:49:34Z

Auanta: /* Description */ formatting

== Description ==

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, PinePhone, Allwinner Tablets and more.

You can find us on '''irc.libera.chat''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the [[Nokia_N900]], the [[Motorola Droid 4]] and the [[PinePhone]]. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.

== Useful resources, lists and pages ==

* To get started with a new install, see [[Getting_Started|Getting Started]].
* Read our [[Leste_FAQ|Frequently Asked Questions]]
* List of [[:Category:Device]] with support to varying degrees
* Latest downloadable images: https://phoenix.maemo.org/view/Images/
* List of "extras" software packages that have a wiki page: https://leste.maemo.org/Category:Extras
* Read how to get started with [[Development]]
* You have an application you want to see in Leste? Please let us know [[Wishlist|here]].
* For a list of presentations/talks featuring Maemo Leste, see [[Talks]]

== Links ==

<div>
The central point of meeting and talking is '''IRC''' ('''irc.libera.chat''' in '''#maemo-leste''') and this thread: https://talk.maemo.org/showthread.php?t=100192.

* Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

* Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

* Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

* Our Github subdomain: [https://maemo-leste.github.io/ https://maemo-leste.github.io/]

* Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

* Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/

* Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

* Our IRC chat history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt] and https://libera.irclog.whitequark.org/maemo-leste/ (previously: https://freenode.irclog.whitequark.org/maemo-leste/)

* Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

* Our Package index and info: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

* Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

* Our Forum [https://talk.maemo.org/forumdisplay.php?f=66 https://talk.maemo.org/forumdisplay.php?f=66]

* RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]

* Our Twitter: [https://twitter.com/maemoleste @maemoleste]

* Distrowatch: [https://distrowatch.com/dwres.php?resource=submit Maemo Leste] (give us an upvote)
</div>

Main Page

2022-08-15T21:43:34Z

Auanta: /* Links */ formatting (make it eye catching)

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, PinePhone, Allwinner Tablets and more.

You can find us on '''irc.libera.chat''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the [[Nokia_N900]], the [[Motorola Droid 4]] and the [[PinePhone]]. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.

== Useful resources, lists and pages ==

* To get started with a new install, see [[Getting_Started|Getting Started]].
* Read our [[Leste_FAQ|Frequently Asked Questions]]
* List of [[:Category:Device]] with support to varying degrees
* Latest downloadable images: https://phoenix.maemo.org/view/Images/
* List of "extras" software packages that have a wiki page: https://leste.maemo.org/Category:Extras
* Read how to get started with [[Development]]
* You have an application you want to see in Leste? Please let us know [[Wishlist|here]].
* For a list of presentations/talks featuring Maemo Leste, see [[Talks]]

== Links ==

<div>
The central point of meeting and talking is '''IRC''' ('''irc.libera.chat''' in '''#maemo-leste''') and this thread: https://talk.maemo.org/showthread.php?t=100192.

* Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

* Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

* Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

* Our Github subdomain: [https://maemo-leste.github.io/ https://maemo-leste.github.io/]

* Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

* Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/

* Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

* Our IRC chat history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt] and https://libera.irclog.whitequark.org/maemo-leste/ (previously: https://freenode.irclog.whitequark.org/maemo-leste/)

* Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

* Our Package index and info: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

* Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

* Our Forum [https://talk.maemo.org/forumdisplay.php?f=66 https://talk.maemo.org/forumdisplay.php?f=66]

* RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]

* Our Twitter: [https://twitter.com/maemoleste @maemoleste]

* Distrowatch: [https://distrowatch.com/dwres.php?resource=submit Maemo Leste] (give us an upvote)
</div>

Main Page

2022-08-15T21:35:36Z

Auanta: /* Links */

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, PinePhone, Allwinner Tablets and more.

You can find us on '''irc.libera.chat''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the [[Nokia_N900]], the [[Motorola Droid 4]] and the [[PinePhone]]. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.

== Useful resources, lists and pages ==

* To get started with a new install, see [[Getting_Started|Getting Started]].
* Read our [[Leste_FAQ|Frequently Asked Questions]]
* List of [[:Category:Device]] with support to varying degrees
* Latest downloadable images: https://phoenix.maemo.org/view/Images/
* List of "extras" software packages that have a wiki page: https://leste.maemo.org/Category:Extras
* Read how to get started with [[Development]]
* You have an application you want to see in Leste? Please let us know [[Wishlist|here]].
* For a list of presentations/talks featuring Maemo Leste, see [[Talks]]

== Links ==
<div>
The '''central point of meeting and talking''' is IRC (irc.libera.chat in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

* Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

* Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

* Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

* Our Github subdomain: [https://maemo-leste.github.io/]

* Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

* Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/

* Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

* Our IRC chat history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt] and https://libera.irclog.whitequark.org/maemo-leste/ (previously: https://freenode.irclog.whitequark.org/maemo-leste/)

* Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

* Our Package index and info: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

* Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

* Our Forum [https://talk.maemo.org/forumdisplay.php?f=66]

* RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]

* Our Twitter: [https://twitter.com/maemoleste @maemoleste]

* [https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

Main Page

2022-08-15T21:35:13Z

Auanta: /* Links */ reorganized, formatting, add a couple links

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, PinePhone, Allwinner Tablets and more.

You can find us on '''irc.libera.chat''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the [[Nokia_N900]], the [[Motorola Droid 4]] and the [[PinePhone]]. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.

== Useful resources, lists and pages ==

* To get started with a new install, see [[Getting_Started|Getting Started]].
* Read our [[Leste_FAQ|Frequently Asked Questions]]
* List of [[:Category:Device]] with support to varying degrees
* Latest downloadable images: https://phoenix.maemo.org/view/Images/
* List of "extras" software packages that have a wiki page: https://leste.maemo.org/Category:Extras
* Read how to get started with [[Development]]
* You have an application you want to see in Leste? Please let us know [[Wishlist|here]].
* For a list of presentations/talks featuring Maemo Leste, see [[Talks]]

== Links ==
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]
<div>
The '''central point of meeting and talking''' is IRC (irc.libera.chat in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

* Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

* Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

* Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

* Our Github subdomain: [https://maemo-leste.github.io/]

* Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

* Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/

* Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

* Our IRC chat history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt] and https://libera.irclog.whitequark.org/maemo-leste/ (previously: https://freenode.irclog.whitequark.org/maemo-leste/)

* Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

* Our Package index and info: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

* Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

* Our Forum [https://talk.maemo.org/forumdisplay.php?f=66]

* RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]

* Our Twitter: [https://twitter.com/maemoleste @maemoleste]

* [https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

PinePhone

2022-08-15T20:57:38Z

Auanta: /* Status */ moved section closer to status/functionality

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:56:04Z

Auanta: /* More Information */ moving this section to the status section

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:53:47Z

Auanta: /* Notes */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:52:25Z

Auanta: /* Notes */ Maemo how to contact

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:47:07Z

Auanta: /* Status */ moved functionality summary to this section from Notes for coherence

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images.] '''

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:44:06Z

Auanta: /* Notes */ moving functionality back to the other section about functionality

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images.] '''

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:40:37Z

Auanta: /* Install image to eMMC */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

''' [https://maedevu.maemo.org/images/pinephone/ Testing images repo.] '''

''' What you can do with the 20220206 image:'''

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently '''not working'''''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:39:50Z

Auanta: /* Modify the image to use eMMC paths */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

''' [https://maedevu.maemo.org/images/pinephone/ Testing images repo.] '''

''' What you can do with the 20220206 image:'''

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning''', this '''no longer works''' in latest images since boot.txt was removed. Please update this section.''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently not working, needs testing''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:38:19Z

Auanta: /* eMMC Installation */ moved warning

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

''' [https://maedevu.maemo.org/images/pinephone/ Testing images repo.] '''

''' What you can do with the 20220206 image:'''

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===
==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

'''''Warning, this no longer works in latest images since boot.txt was removed. Please update this section.'''''

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently not working, needs testing''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:36:26Z

Auanta: /* Installation */ trimmed unnecessary cruft at top

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

''' [https://maedevu.maemo.org/images/pinephone/ Testing images repo.] '''

''' What you can do with the 20220206 image:'''

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==
Unlike most phones, it's pretty simple.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===

'''''Warning, this no longer works in latest images since boot.txt was removed. Please improve this section.'''''

==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently not working, needs testing''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:29:57Z

Auanta: /* Prepare the SD card */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

''' [https://maedevu.maemo.org/images/pinephone/ Testing images repo.] '''

''' What you can do with the 20220206 image:'''

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==

(Work in Progress)

Currently:
* working out how to install .tar.gz

Unlike most phones, it's pretty simple.

Download the image and the corresponding <code>.sha</code> file, then verify the image's integrity:

$ cat maemo-leste-*-arm64-pinephone-*.img.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz

or

$ cat maemo-leste-*-arm64-pinephone-*.tar.gz.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.tar.gz

Verify that the number that each command spits out is exactly the same number. If it is not, do not use the image. Try redownloading or ask for help.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare results. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===

'''''Warning, this no longer works in latest images since boot.txt was removed. Please improve this section.'''''

==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently not working, needs testing''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:29:19Z

Auanta: /* Write the image to an SD-Card. */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

''' [https://maedevu.maemo.org/images/pinephone/ Testing images repo.] '''

''' What you can do with the 20220206 image:'''

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==

(Work in Progress)

Currently:
* working out how to install .tar.gz

Unlike most phones, it's pretty simple.

Download the image and the corresponding <code>.sha</code> file, then verify the image's integrity:

$ cat maemo-leste-*-arm64-pinephone-*.img.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz

or

$ cat maemo-leste-*-arm64-pinephone-*.tar.gz.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.tar.gz

Verify that the number that each command spits out is exactly the same number. If it is not, do not use the image. Try redownloading or ask for help.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
press 'p' to view current table
press 'o' to erase and make a new table
press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare results. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step (read warnings below).'''''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===

'''''Warning, this no longer works in latest images since boot.txt was removed. Please improve this section.'''''

==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently not working, needs testing''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:24:46Z

Auanta: /* Write the image to an SD-Card. */ add checksum instructions, formatting

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

''' [https://maedevu.maemo.org/images/pinephone/ Testing images repo.] '''

''' What you can do with the 20220206 image:'''

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==

(Work in Progress)

Currently:
* working out how to install .tar.gz

Unlike most phones, it's pretty simple.

Download the image and the corresponding <code>.sha</code> file, then verify the image's integrity:

$ cat maemo-leste-*-arm64-pinephone-*.img.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz

or

$ cat maemo-leste-*-arm64-pinephone-*.tar.gz.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.tar.gz

Verify that the number that each command spits out is exactly the same number. If it is not, do not use the image. Try redownloading or ask for help.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
press 'p' to view current table
press 'o' to erase and make a new table
press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

''DO NOT'' copy-paste these instructions.

Download the latest image from [https://maedevu.maemo.org/images/pinephone/ here] and the associated checksum file.

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare results. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
''Be very careful with this step (read warnings below).''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.

=== eMMC Installation ===

'''''Warning, this no longer works in latest images since boot.txt was removed. Please improve this section.'''''

==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently not working, needs testing''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:15:29Z

Auanta: /* SD Card Installation */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

''' [https://maedevu.maemo.org/images/pinephone/ Testing images repo.] '''

''' What you can do with the 20220206 image:'''

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==

(Work in Progress)

Currently:
* working out how to install .tar.gz

Unlike most phones, it's pretty simple.

Download the image and the corresponding <code>.sha</code> file, then verify the image's integrity:

$ cat maemo-leste-*-arm64-pinephone-*.img.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz

or

$ cat maemo-leste-*-arm64-pinephone-*.tar.gz.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.tar.gz

Verify that the number that each command spits out is exactly the same number. If it is not, do not use the image. Try redownloading or ask for help.

=== SD Card Installation ===
==== Prepare the SD card ====

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
press 'p' to view current table
press 'o' to erase and make a new table
press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image from [https://maedevu.maemo.org/images/pinephone/ here].
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
''Be very careful with this step (read warnings below).''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

If using a Windows machine, you can use [https://etcher.io/ Etcher] NOTE: Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

=== eMMC Installation ===

'''''Warning, this no longer works in latest images since boot.txt was removed. Please improve this section.'''''

==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently not working, needs testing''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]

PinePhone

2022-08-15T20:14:54Z

Auanta: /* Write the image to an SD-Card. */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Pine64
|codename=
|dimensions=
|release_date=
|soc=Allwinner A64
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

''' [https://maedevu.maemo.org/images/pinephone/ Testing images repo.] '''

''' What you can do with the 20220206 image:'''

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

== Installation ==

(Work in Progress)

Currently:
* working out how to install .tar.gz

Unlike most phones, it's pretty simple.

Download the image and the corresponding <code>.sha</code> file, then verify the image's integrity:

$ cat maemo-leste-*-arm64-pinephone-*.img.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz

or

$ cat maemo-leste-*-arm64-pinephone-*.tar.gz.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.tar.gz

Verify that the number that each command spits out is exactly the same number. If it is not, do not use the image. Try redownloading or ask for help.

=== SD Card Installation ===
==== Prepare the SD card ====

# Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
press 'p' to view current table
press 'o' to erase and make a new table
press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

# Download the latest image from [https://maedevu.maemo.org/images/pinephone/ here].
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
''Be very careful with this step (read warnings below).''
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer.

If using a Windows machine, you can use [https://etcher.io/ Etcher] NOTE: Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to.

Make absolutely sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the device you selected, make sure it is the correct one.

Do not use partition numbers, or it won't boot. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar.

=== eMMC Installation ===

'''''Warning, this no longer works in latest images since boot.txt was removed. Please improve this section.'''''

==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

''Note: Currently not working, needs testing''

'''From the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]:'''

=== Using Tow-Boot ===

If you flashed tow-boot to the PinePhone (instructions [https://tow-boot.org/devices/pine64-pinephoneA64.html here]), the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing Maemo Leste to the 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.

=== Using JumpDrive ===

You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.

The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

=== From the booted microSD ===
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.
# Extract the image file so that it only ends in ".img"
# 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 phone, remove microSD card and then turn on the phone.

== More Information ==

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* VoLTE should work out-of-the-box. If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
*

=== How to take a picture ===

Maemo userland to take pictures or make videos is not ready yet.

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Also the graphical tool "qcam" should work, but it has some color space conversion bugs. Run it with:
$ qcam -r gles -spixelformat=SBGGR8,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

[[Category:Device]]