Difference between revisions of "User:Fxc"

From PINE64
Jump to navigation Jump to search
(+1)
 
(26 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Export ==
https://wiki.pine64.org/wiki/Special:AllPages?from=&to=&namespace=0&hideredirects=1
https://wiki.pine64.org/wiki/Special:Export
[[User:Fxc/export]]
Cutoff: 16 April 2023
22 September 2023: PineTab-V, PineTab2
== Wiki keep ==
* [[PinePhone APN Settings]]
* [[PinePhone Carrier Support]]
== Getting started ==
The Ox64 can be flashed using an UART connection or by connecting the device to the computer using USB-C.
=== Using UART ===
To flash the Ox64 using an UART connection, first connect your UART device as pictured below:
[[File:|360px]]
Then do the following steps:
* Do not connect the micro-USB cable or ''VBUS'' yet
* Press and hold the ''BOOT'' button
* Connect the micro-USB cable or connect ''VBUS''
* Wait for a few seconds
* Release the ''BOOT'' button
=== Using USB ===
To flash the Ox64 using a USB-C connection to a computer:
{{Info|This won't be possible on the first batch of Ox64 devices from October 2022, see [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff here].}}
* ...
== Chaos ==
== Chaos ==
* [[ROCKPro64 Software Releases]]
* [[ROCKPro64 Software Releases#Android]]
* [[Special:ListFiles]]
* [[Special:ListFiles]]
* [[Pinebook Pro]]
* [[Pinebook Pro]]
* [[Getting started]]
* [[Getting started]]
* [[PINE H64]]
* [[SOEDGE Software Releases]]
* [[SOEDGE Software Releases]]
* [[PineBuds Pro]] -> stub sections, lacks user manual steps
* [[PineBuds Pro]] -> stub sections, lacks user manual steps
* [[Special:UncategorizedPages]]
* [[Accessories_Step_by_Step_Guides]] -> Explanation for which devices this applies
* Rename Accessories_Step_by_Step_Guides section to Accessories everywhere
* [[PineTime#Community]] redundant information. Might be solved with a template per article
* [[SOQuartz Software Releases]]


== ChatGPT: Flashing with dd ==
== ChatGPT: Flashing with dd ==
Line 46: Line 95:


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


You can learn more about the following ARM and RISC-V devices manufactured by PINE64:
You can learn more about the following ARM and RISC-V devices manufactured by PINE64:
Line 87: Line 134:
Makerspace:  
Makerspace:  
* [[Pinecil]], [[PinePower]], [[PineCone]] and [[Pinedio]]
* [[Pinecil]], [[PinePower]], [[PineCone]] and [[Pinedio]]


== Pinebook notes ==
== Pinebook notes ==
Line 99: Line 145:
| ✅ || ❓ || ❌
| ✅ || ❓ || ❌
|-
|-
|}
== PineBuds Pro suggestion ==
<nowiki>== Community projects ==</nowiki>
The following community projects are currently being worked on:
* [[PineBuds_Pro/Project:_Wireless_charging|Wireless charging]], bringing wireless charging to the PineBuds Pro case using the vacant contacts
* [[PineBuds_Pro/Project:_Silicone_case|Silicone case]], a transparent silicone case, bringing an improved grip to the case
== Suspicious protectionfilms24.com link spam ==
* https://wiki.pine64.org/index.php?title=PineTime&diff=15276&oldid=14695
* https://wiki.pine64.org/index.php?title=PinePhone_Pro&diff=15447&oldid=14781
* https://wiki.pine64.org/index.php?title=PinePhone&diff=15448&oldid=15260
== Software state draft ==
{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="width: 240px;"  | Component
! scope="col" style="width: 150px;" | Status (pre-flashed)¹
! scope="col" style="width: 150px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="2" | Bootloader
| <code>U-Boot</code>
| colspan="2" style="background:Red; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop<sup>[https://wiki.pine64.org/wiki/PinePhone_Pro#Installation_instructions]</sup>; Occasionally the eMMC fails to boot<sup>[Citation]</sup>
|-
| <code>SPI</code>
| colspan="2" style="background:Red; text-align:center;" | Unfinished
| SPI memory is currently empty in the Explorer Edition batch, a corrupted installation on the eMMC has a higher boot priority than a fresh microSD card installation, leading to a involved recovery procedure<sup>[Citation]</sup>
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| style="background:Red; text-align:center;" | Critical bugs
| style="background:Yellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating<sup>[https://www.pine64.org/2022/03/15/march-update-introducing-the-quartzpro64/]</sup>;
|-
| <code>Suspend</code>
| style="background:Red; text-align:center;" | Not working
| style="background:Yellow; text-align:center;" | Experimental
| Suspend only available in recent specific images<sup>[Citation]</sup>
|-
| <code>Updates</code>
| style="background:Red; text-align:center;" | Critical bugs
| style="background:Yellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating<sup>[Citation]</sup>; Pacman database lock preventing updates<sup>[Citation]</sup>; Keyring bug<sup>[Citation]</sup>
|-
! scope="row" rowspan="5" | Modem
| <code>Stability</code>
| colspan="2" style="background:Red; text-align:center;" | Critical bugs
| The modem crashes frequently, which can lead to missed calls<sup>[Citation]</sup>
|-
| <code>Phone</code>
| colspan="2" style="background:Red; text-align:center;" | WIP
| The modem crashes frequently, which can lead to missed calls<sup>[Citation]</sup>; bad call audio quality<sup>[Citation]</sup>; software improvements expected within multiple months and contributions are welcome.
|-
| <code>SMS</code>
| colspan="2" style="background:Green; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem<sup>[Citation]</sup> or by the provider blocking specific TANs in their network<sup>[Citation]</sup>.
|-
| <code>MMS</code>
| colspan="2" style="background:Yellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:Red; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:Green; text-align:center;" | Working
|
|-
| <code>Touch</code>
| colspan="2" style="background:Green; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| colspan="2" style="background:Red; text-align:center;" | Not working
| Driver not implemented yet, camera not operational
|-
| <code>Front camera</code>
| colspan="2" style="background:Red; text-align:center;" | Not working
| Driver not implemented yet, camera not operational
|-
| <code>Camera flash</code>
| colspan="2" style="background:Yellow; text-align:center;" | Unknown
|
|-
| <code>WiFi</code>
| colspan="2" style="background:Green; text-align:center;" | Working
| WiFi is expected to work. Note: Proprietary firmware and some remaining tasks, such as looking into "monitor mode"
|-
| <code>Bluetooth</code>
| colspan="2" style="background:Yellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing Proprietary<sup>[Citation]</sup>; Bluetooth in general dodgy under Pulseaudio.<sup>[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire]</sup> Note: Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:Yellow; text-align:center;" | WIP
| aGPS to be implemented; long waiting times to get a fix; No preinstalled application
|-
| <code>Sensors</code>
| colspan="2" style="background:Yellow; text-align:center;" | Unknown
| Status of "3 Axis Magnetometer", "Geo Magnetic Sensor", "Ambient light / Proximity", "Accelerometer / Gyroscope" is unknown.
|-
| <code>Vibration motor</code>
| colspan="2" style="background:Green; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:Yellow; text-align:center;" | Unknown
|
|-
| <code>Buttons</code>
| colspan="2" style="background:Green; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="4" | Accessory compatibility
| <code>Keyboard Add-on</code>
| colspan="2" style="background:Yellow; text-align:center;" | WIP
| The keyboard add-on compatibility is work-in-progress. Top row symbols not implemented as designed<sup>[Citation]</sup>; Keyboard hot-plugging not supported<sup>[Citation]</sup>; Battery state not exposed in the pre-flashed operating system state<sup>[Citation]</sup>; general driver bugs<sup>[Citation]</sup>
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:Red; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:Yellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software and driver functionality is missing, details will follow in a bug report.<sup>[Citation]</sup>
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:Red; text-align:center;" | Not implemented
| No software support implemented
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:Yellow; text-align:center;" | Software rendering only
| Waydroid is an Android container used to run Android applications. Currently can only be started using software rendering <sup>[Citation]</sup>
|-
|}
¹ Status of the feature at the time of the last factory installation without updates
² Status of the feature with an up-to-date reference image
== Chat ==
* https://sackheads.org/~bnaylor/spew/away_msgs.html
* Inclusive language, Linux
== Test 2 ==
<table cellspacing="0" cellpadding="0" border="0" style="box-sizing:border-box; border:1px #d33 solid; background: transparent; margin-top:0.5em;padding:0.5em 1em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top" style="padding-right: 5px;">'''Warning: '''</td><td valign="top">{{{msg|{{{1|}}}}}}</td></tr></table>
<table cellspacing="0" cellpadding="0" border="0" style="box-sizing:border-box; border:1px #d33 solid; background: transparent; margin-top:0.5em;padding:0.5em 1em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top" style="padding-right: 5px;">'''Warning: '''</td><td valign="top">{{{msg|{{{1|}}}}}}</td></tr></table>
<table cellspacing="0" cellpadding="0" border="0" style="box-sizing:border-box; border:1px #d33 solid; background: transparent; margin-top:0.5em;padding:0.5em 1em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top" style="padding-right: 5px;">'''Warning: '''</td><td valign="top">{{{msg|{{{1|}}}}}}</td></tr></table>
<table cellspacing="0" cellpadding="0" border="0" style="box-sizing:border-box; border:1px #d33 solid; background: transparent; margin-top:0.5em;padding:0.5em 1em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top" style="padding-right: 5px;">'''Warning: '''</td><td valign="top">{{{msg|{{{1|}}}}}}</td></tr></table>
{{Warning|Test}}
{{Warning|Test}}
{{Warning|Test}}
{{Warning|Test}}
== Test ==
{{Note|Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua.}}
== Safety ==
=== Charging and Battery ===
Notes:
* Correct charger
* High power usage in certain scenarios
* Handling of the battery
* (Optional: Charging keyboard and phone at the same time)
* (Optional: Connecting a USB-C to USB-C cable from phone to keyboard)
== Ubuntu Touch ==
{| class="wikitable" style="width: 800px;"
!colspan="2" style="background: #a7d7f9;"|Ubuntu Touch
|-
|colspan="2"|Image
|-
|colspan="2"|A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community. Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
|-
|rowspan="1" style="width: 200px;"|Download location
|[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]
|-
|rowspan="2"|user-id/password
| abc
|-
| 123
|-
|What works, what does not work?
|[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]
|-
|How to contribute and report defects?
|[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]
|-
|Contributions
|[https://ubports.com/foundation/sponsors See UBports website for how to donate.]
|-
|colspan="2" style="background: #cecece"| Installation
|-
|colspan="2"| Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.
|-
|colspan="2" style="background: #cecece"| Notes
|-
|colspan="2"| Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.
|-
|}
== Image ==
{| class="wikitable" style="width: 800px;"
|-
|colspan="2"|Image
|-
|colspan="2"|Description
|-
|rowspan="1" style="width: 120px;" | Author
| Test
|-
| License
| CC0
|-
| SVG location
| Test
|}
== Licenses template ==
Test:
{|style="border:1px solid #a2a9b1; padding: 0 10px 0 10px; width: 80%; margin: 4px 10%;"
|
|style="width: 40px"|[[Image:CC_some_rights_reserved.svg|90px|center]] [[Image:Cc-by new white.svg|24px|center]]
|style="padding: 20px"|''This file is licensed under the [https://en.wikipedia.org/wiki/en:Creative_Commons Creative Commons] [https://creativecommons.org/licenses/by/3.0/deed.en Attribution 3.0 Unported] license.''
|}
|}


Latest revision as of 22:41, 22 September 2023

Export

https://wiki.pine64.org/wiki/Special:AllPages?from=&to=&namespace=0&hideredirects=1

https://wiki.pine64.org/wiki/Special:Export

User:Fxc/export

Cutoff: 16 April 2023

22 September 2023: PineTab-V, PineTab2

Wiki keep


Getting started

The Ox64 can be flashed using an UART connection or by connecting the device to the computer using USB-C.

Using UART

To flash the Ox64 using an UART connection, first connect your UART device as pictured below:

[[File:|360px]]

Then do the following steps:

  • Do not connect the micro-USB cable or VBUS yet
  • Press and hold the BOOT button
  • Connect the micro-USB cable or connect VBUS
  • Wait for a few seconds
  • Release the BOOT button

Using USB

To flash the Ox64 using a USB-C connection to a computer:

Note: This won't be possible on the first batch of Ox64 devices from October 2022, see here.
  • ...

Chaos

ChatGPT: Flashing with dd

Flashing a disk image to a microSD card using the dd command involves writing the disk image file to the microSD card. This process is performed through the terminal on Linux or macOS. Here are the steps to flash a disk image to a microSD card using dd:

1. Determine the device name of the microSD card: On Linux or macOS, you can use the lsblk or diskutil list command to find the name of the microSD card (e.g., /dev/sdb). Make sure to properly identify the microSD card, as using the wrong device name can result in data loss.

2. Unmount the microSD card: If the microSD card is already mounted, you need to unmount it before flashing the disk image. On Linux, you can use the umount command. On macOS, you can use the diskutil unmount command.

3. On Linux or macOS, open a terminal window.

4. Flash the disk image to the microSD card: Use the following command to flash the disk image to the microSD card: 

sudo dd if=path_to_disk_image.img of=/dev/sdX bs=4M conv=fsync
  • Replace path_to_disk_image.img with the path to the disk image file.
  • Replace /dev/sdX with the device name of the microSD card you determined in step 1.

5. Wait for the process to complete: The dd command will not provide any output until it has completed the process. This may take several minutes, depending on the size of the disk image and the speed of your computer and microSD card.

6. Eject the microSD card: Once the dd command has completed, eject the microSD card. On Linux, you can use the eject command. On macOS, you can use the diskutil eject command.

Note: Before flashing the disk image, make sure to backup any important data on the microSD card, as this process will erase all existing data on the card.

ChatGPT: Flashing with Etcher

Here are the steps to flash a disk image to a microSD card:

  1. Download and install a disk image writing tool: A commonly used tool for this purpose is Etcher, which is available for Windows, Mac, and Linux.
  2. Insert the microSD card into your computer: Make sure that you have an SD card reader, or an adapter to connect the microSD card to your computer.
  3. Open the disk image writing tool: Launch Etcher and select the disk image file you want to flash to the microSD card.
  4. Select the target device: In Etcher, select the microSD card from the list of available drives.
  5. Start the flashing process: Click the "Flash" button to start the process of writing the disk image to the microSD card. This process may take a few minutes, depending on the size of the disk image and the speed of your computer.
  6. Verify the flash: After the flash is complete, Etcher will verify the integrity of the image to make sure it was written correctly.
  7. Eject the microSD card: Once the flash is complete and verified, safely eject the microSD card from your computer. You can now use the microSD card with the device it was intended for.

Note: Before flashing the disk image, make sure to backup any important data on the microSD card, as this process will erase all existing data on the card.

Main example

Devices

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

Phones:

Phone accessories:

Tablets:

Wearable:

Laptops:

Single-board computers:

Set-top box:

Clusters and modules:

IP camera:

Makerspace:

Pinebook notes

Merge https://wiki.pine64.org/wiki/1080P_Pinebook_Software_Releases into https://wiki.pine64.org/wiki/Pinebook_Software_Releases

Compatibility
 Pinebook 11.6″ Pinebook 11.6" 1080p  Pinebook 14″
✅ ❓ ❌

Collapsible test

Retrieved from "https://wiki.pine64.org/index.php?title=User:Fxc&oldid=20763"