https://wiki.pine64.org/api.php?action=feedcontributions&user=Madez&feedformat=atomPINE64 - User contributions [en]2024-03-28T15:39:12ZUser contributionsMediaWiki 1.37.1https://wiki.pine64.org/index.php?title=PinePhone_FAQ&diff=10673PinePhone FAQ2021-06-08T18:50:26Z<p>Madez: /* How can I turn on the backlight? */</p>
<hr />
<div>A list of frequently asked question.<br />
<br />
== Hardware ==<br />
<br />
=== Revisions ===<br />
==== What are Community Editions? ====<br />
Community Editions of the PinePhone were versions of the PinePhone which came preinstalled with the operating system of a partner project and featured the logo of the project on the back panel. The Community Edition was intended to help partner projects developing these systems: "Community editions are meant to bring exposure to partner-projects operating systems and communities, as well as help finance ongoing development.", [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ source].<br />
<br />
==== Is the Community Edition hardware the latest revision? ====<br />
The Community Edition program (featuring the mainboard numbers 1.2 through 1.2b and branded back covers) which provided the branded PinePhones has since ended, and a Beta Edition has since been released. The only difference between each Community Edition is the inclusion of crucial bug fixes, with the last issue being fixed with the 1.2b motherboard shipping with the Manjaro CE PinePhones. The 1.2b motherboard is also currently used in the Beta Edition PinePhones, however the Beta Edition units do not ship with any back cover branding. There are currently no plans for further hardware revisions.<br />
<br />
Aside from the back cover, the only other difference between each Community Edition is that starting with the postmarketOS PinePhone, a convergence package option was released that adds another gigabyte of ram to the phone and a 32GB eMMC instead of a 16GB eMMC. Convergence packages also included a dock for plugging in USB peripherals and connecting to an HDMI monitor, however you can purchase a generic USB-C dock to use with a 2GB PinePhone. <br />
<br />
The predecessor to the Convergence Edition PinePhones was the Braveheart Edition intended for developers to bring up the platform, which had the version number 1.1. For more details about the topic see [[PinePhone#Hardware Revisions]].<br />
<br />
==== Will there be other Community Editions? ====<br />
Five Community Editions have been announced: [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ UBports], [https://www.pine64.org/2020/06/15/june-update-postmarketos-ce-pinephone-shipping-pine64-cluster/ postmarketOS], [https://www.pine64.org/2020/08/31/pinephone-manjaro-community-edition/ Manjaro], [https://www.pine64.org/2020/12/01/kde-community-edition-is-now-available/ KDE], and [https://www.pine64.org/2021/01/17/mobian-community-edition/ Mobian]. Since the release of the Mobian edition, the Beta Edition PinePhones have been released and the Community Edition Program has ended.<br />
<br />
==== In simple terms, what are the differences between Braveheart and the new Community Edition? ====<br />
The Braveheart PinePhone was the first public revision of the PinePhone which was intended solely for developers and Linux enthusiasts. The UBports Community Edition was the next revision of the PinePhone with an updated mainboard based on feedback from the Braveheart Edition, see [[PinePhone#Hardware Revisions]]. All current revisions of the PinePhone continue to be intended for developers and enthusiasts, however, PINE64 will be starting to offer partnered retail units of the PinePhone which will have a better warranty and technical support (keep in mind even then it is not intended for a broader audience at this time, as the software still needs work and the hardware does not hold up well to modern consumer standards).<br />
<br />
==== Will there be a newer revision after the Community Editions? ====<br />
Starting with the UBports Community Edition the PinePhone has gotten CE and FCC certifications, repeating the certification process due to changes in the hardware design is very expensive, so the 1.2b motherboard is viewed as the final revision. The PinePhone (and parts for them) will be produced and sold for at least 5 years.<br />
<br />
==== Will there be hardware differences between the Community Editions? ====<br />
<br />
Besides the varied back covers, starting with the launch of the PostmarketOS CE there has been the release of a convergence package option for the PinePhone which includes more ram and storage, and an included dock for convenience. There has also been multiple hardware changes starting with the UBports CE (mainboard 1.2) and ending with the Manjaro CE (mainboard revision 1.2b). There are currently no plans for future hardware changes for a few years.<br />
<br />
==== How powerful is the PinePhone's hardware? ====<br />
<br />
The PinePhone is about on par with a Raspberry Pi 3 in terms of CPU power, however going by GFLOPS it has half the GPU power. The Pi 3's Videocore IV does 24 GFLOPS, and the Mali 400 MP2 on the PinePhone only 10.8.<br />
<br />
Despite this, using software rendering the PinePhone is capable of smoothly rendering at 1080p resolution or higher. However, with a fully GPU-accelerated mobile environment you should expect a more sluggish experience outputting to such resolutions. Unfortunately, the Mali 400 MP2 (a 2008 arm mobile GPU) simply isn't intended to push 1080p resolution. With that said, the VPU of the PinePhone has been shown to handle smooth H.264 1440p30 video playback using Cedrus and gstreamer as documented [https://xnux.eu/log/#001 here]. Further, the PinePhone should be more than capable of a smooth phone experience when used in conjunction with well optimized software that makes use of its hardware features. It is also more than capable of running many light games (including 3D ones such as SuperTuxKart), and retro gaming. Expect further speed improvements over time as the drivers are improved, and in the meanwhile you can look into slightly [[overclocking]] the device (at your own risk).<br />
<br />
=== Sound ===<br />
<br />
The default ringtone for Mobian Phosh can be found at /usr/share/sounds/freedesktop/stereo/phone-incoming-call.oga<br />
<br />
=== Modem ===<br />
<br />
==== The modem isn't working ====<br />
<br />
In order to use the modem and Wi-Fi/Bluetooth, you need to ensure the battery is inside the device and has a sufficient charge. Even when supplying the phone with enough power, the modem and Wi-Fi chip will not work without a connected battery. Further, double check that you have not put the SD card into the sim card slot, or vice versa.<br />
<br />
==== Does the PinePhone only wake up from sleep for calls and texts? ====<br />
<br />
Yes. Unless the PinePhone is configured to wake up every few minutes from deep sleep in crust (At the cost of battery life. However, in the future there may be other solutions), then there is not any way to get any notifications for applications. The modem on the PinePhone will wake the device for incoming calls and texts however, and the real-time clock is also capable of waking the device for alarms.<br />
<br />
=== Battery ===<br />
<br />
==== The battery is stuck inside the phone ====<br />
<br />
The battery can be stuck in the phone if the screws of the frame are overtightened.<br />
<br />
If your battery is stuck inside the PinePhone, grab a screwdriver and completely unscrew all the screws of the midframe. Then pull out the battery (you may have to fully take off the midframe in some cases to get it out). And then rescrew the midframe, but only tighten the screws to the point where they are just barely tight to hold. This should allow you to remove the battery easily.<br />
<br />
==== The battery is discharging while the phone is powered off (Braveheart Edition) ====<br />
<br />
The issue is not present on the Community Edition. Due to a hardware bug, after power off, the phone still consumes 20–30mA which drains the battery in 3-4 days. A manual procedure to fix the hardware bug is described [https://xnux.eu/devices/pp-pmic-fix.jpg here].<br />
<br />
==== The battery only charges to ~84% ====<br />
<br />
Some pre-made OSes using megi's kernel limit the maximum amount of charge to roughly ~84% in the hope of prolonging the battery life, as repeatedly reaching the upper level of battery charge reduces the battery's lifetime (this is <b>not</b> a safety feature!). The same effect however also applies when repeatedly draining the battery to a low level - users are therefore advised to consider if that setting is reasonable depending on their usage. The setting can be overwritten via Sysfs, to let the battery fully charge (this can lower the replaceable's battery lifetime considerably depending on the charging behavior!):<br />
<br />
{{warning|The following instructions are directed towards expert-level users and developers!}}<br />
<br />
<code>echo 4350000 > /sys/class/power_supply/axp20x-battery/voltage_max_design</code><br />
<br />
=== Kill Switches ===<br />
==== What are the kill switches doing? ====<br />
<br />
{| class="wikitable"<br />
|-<br />
! Number<br />
! Name<br />
! Explanation<br />
! Description<br />
|-<br />
| 1<br />
| Modem<br />
| Pulls Q1501 gate up (FET killing modem power)<br />
| "On" enables cellular communication and GNSS hardware, "off" disables it.<br />
|-<br />
| 2<br />
| Wi-Fi / Bluetooth<br />
| Pulls up CHIP_EN<br />
| "On" enables Wi-Fi and Bluetooth communication hardware, "off" disables it.<br />
|-<br />
| 3<br />
| Microphone<br />
| Breaks microphone bias voltage from the SoC<br />
| "On" enables audio input from on-board microphones (not 3.5mm jack), "off" disables it.<br />
|-<br />
| 4<br />
| Rear camera<br />
| Pulls up PWDN on OV5640 <br />
| "On" enables the rear camera, "off" disables it.<br />
|-<br />
| 5<br />
| Front camera<br />
| Pulls up PWDN on GC2145<br />
| "On" enables the front camera, "off" disables it.<br />
|-<br />
| 6<br />
| Headphone<br />
| Pulls up IN2 on analog switch BCT4717ETB<br />
| "On" enables audio input and output via the 3.5mm audio jack, "off" switches the jack to hardware UART mode.<br />
|}<br />
<br />
=== Memory ===<br />
<br />
==== What's the speed difference between the eMMC and SD cards? ====<br />
Maximum transfer speed of the eMMC is around 85 MB/s, while SD cards are limited to approximately 23 MB/s (even with faster cards).<br />
<br />
=== GPS ===<br />
<br />
==== GPS doesn't work ====<br />
<br />
Like almost all smartphones, the PinePhone GPS antenna is small and can only get a first fix unassisted if the GPS signal is very strong. To make first fix faster and more reliable, phones download assistance data either from the phone network or from the internet. The GPS in the PinePhone modem supports the internet based assistance method, as detailed in the modem documentation, but this is currently only supported by a few distributions, and a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] that shows it can work.<br />
<br />
Until aGPS support becomes standard you'll have to make some manual changes - see for example [https://wiki.mobian-project.org/doku.php?id=location Mobian wiki]<br />
<br />
==== GPS can't determine direction ====<br />
<br />
Currently, due to the magnetometer not being hooked up in software at this time, it is not possible for GPS software to use the phone's compass functionality. This means while you are walking it will not be possible to determine the direction of travel. This is not as much of an issue for vehicles as the faster speeds mean that it is possible to estimate the direction of travel, however it will still be an issue should the vehicle travel through a tunnel and loose GPS signal.<br />
<br />
== Software ==<br />
<br />
=== Installation ===<br />
<br />
==== How can I install an operating system on the SD card / eMMC? ====<br />
<br />
See [[PinePhone Installation Instructions]].<br />
<br />
=== Updating ===<br />
<br />
Read the [[PinePhone Updating Instructions]].<br />
<br />
=== Booting ===<br />
<br />
==== What's the boot order for SD cards and eMMC? ====<br />
<br />
The PinePhone will automatically boot from microSD if a bootable card is inserted. If no (bootable) microSD is found, it will boot from eMMC.<br />
<br />
==== How can I select different OSes at boot? ====<br />
<br />
There was a project by Danct12 which allowed the user to select different OSes at boot, but the repository has since been archived: https://github.com/dreemurrs-embedded/Pineloader.<br />
<br />
==== I turned on my Manjaro CE PinePhone. The red LED and screen backlight are briefly lit, then both are not and it will not boot. ====<br />
<br />
This can be the result of at least one situation:<br />
<br />
# The eMMC installation became corrupt or otherwise unbootable<br />
# An SD card is present but not bootable (consider [[PinePhone#Detailed usage instructions]])<br />
<br />
If there is an installation of Manjaro on both the eMMC & an SD card, the SD card will always boot first on the device. Try taking the SD card out and booting the installation that is on the eMMC. If the problem persists, it is likely there is an issue with both installations and you will need to reinstall your distribution. You may also want to check with your distribution's maintainers if boot issues are a common problem in a recent update.<br />
<br />
==== I did not install an update in Ubuntu Touch and I'm stuck on the PINE64 logo after rebooting. ====<br />
<br />
# Use a USB A-C cable to plug your phone into your PC<br />
# Hold the PinePhone's power button for 4 seconds or more to power it off.<br />
# Wait 5 seconds<br />
# Hold the Volume Up and Power buttons on the PinePhone to boot into recovery. You should see the LED light red, then yellow, then green. The "Installing update" screen will appear, but a progress bar to indicate update progress will not. Ignore the "Installing update" part.<br />
# Your PC may automatically mount the PinePhone's partitions. If it does, Safely Remove or Eject all of them.<br />
# Open a terminal on your PC. Type <code>telnet 172.16.42.1</code><br />
# You should receive the text 'Welcome to Rescue SD Shell!'<br />
# In the new Rescue SD shell, type <code>umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync</code><br />
# Once this command pipeline finishes, type <code>sync && reboot -f</code><br />
<br />
Your PinePhone should reboot into Ubuntu Touch. Now head to Settings -> Updates and install the new update! <br />
<br />
If these steps did not solve your issue, please create a new thread here on the PINE64 forums, note what the problem looks like, then say that you've tried these steps already.<br />
<br />
This is caused by corruption on the userdata partition. Normally this should be fixed by 'e2fsck' in the initramfs, however, an error in image creation means that that version of e2fsck is unable to correct the corruption. This has been fixed in all new PinePhone updates, so if you update from the factory image to any other image available to the PinePhone now, you will not experience this issue any longer.<br />
<br />
==== I turned on my PinePhone running Ubuntu Touch. The red LED is lit and it will not boot. ====<br />
# Hold the power button until the light turns off<br />
# Hold the power button until the light turns on<br />
<br />
You may need to repeat these steps more than once.<br />
<br />
This is caused by u-boot apparently trying to use the eMMC before it is ready. We are not entirely sure why this occurs yet.<br />
<br />
==== Can I install a different OS on my Community Edition? ====<br />
<br />
Yes! While all the Community Edition PinePhones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see [[PinePhone Installation Instructions]] and [[PinePhone Software Releases]] on how to install them.<br />
<br />
=== Other ===<br />
<br />
==== How can I enable SSH? ====<br />
<br />
In Ubuntu Touch you can run "sudo start ssh" to get a one-time start, or edit /etc/init/ssh.override and remove the manual line to make it auto-start.<br />
<br />
In other distributions you may have to install SSH through its package manager and then proceed to use its init system to enable it. For Manjaro, Arch, and Mobian you can use "systemctl enable" and "systemctl start" command to enable and start ssh.<br />
<br />
==== What works, what doesn't? ====<br />
<br />
For Ubuntu Touch see https://gitlab.com/ubports/community-ports/pinephone#what-works-what-doesnt.<br />
<br />
Other distributions will have different levels of functionality. Please refer to the release page of your chosen distribution for further information.<br />
<br />
==== I can't connect to a 2.4Ghz Wi-Fi network in Ubuntu Touch. ====<br />
<br />
Reboot your device by holding the power button until the "Power" dialog appears, then pressing "Restart".<br />
<br />
If that does not fix the issue, note that all the following conditions must be met to use Wi-Fi on the PinePhone:<br />
<br />
# The plastic tab between the battery and the device's battery contacts has been removed<br />
# The battery is installed<br />
# The Wi-Fi killswitch, #2, on the rear of the device is switched "ON"<br />
<br />
Wi-Fi in the PinePhone only seems stable after a warm reboot like this.<br />
<br />
==== What's the status of Android for the PinePhone? ====<br />
<br />
Currently, there isn't any major push to get Android running well on the PinePhone. The developer Icenowy did get a Android image to run and partly work, it was however slow and buggy, with major functions not working. A solution for running some of your android apps may be found in Anbox as of now. Anbox is currently not included in Ubuntu Touch. In other distributions your millage may vary on what applications will run and how well.<br />
<br />
==== Why are my apps loading slower than on my Android phone? ====<br />
<br />
Android has multiple techniques in place to speed up launching applications after the first launch, such as the "Dalvik cache".<br />
<br />
Using an alternative filesystem such as F2FS on the eMMC (which is considerably faster than running software on the SD card) may help improve performance slightly. Over time you can expect further optimizations and improvements in various distributions that will help speed up the PinePhone.<br />
<br />
==== How can I turn on the backlight? ====<br />
<br />
When the brightness setting is too low, the backlight turns off completely. At which point this happens requires calibration. It also depends on whether the pinephone is connected to a charger or not, due to how the backlight is physically regulated. The backlight can be turned on by increasing the brightness setting. If the brightness setting is too low but non-zero, as can happen when using a gui slider, try connecting the phone to a charger.<br />
<br />
On most systems the brightness setting is an integer between 0 and 1000 and available at runtime in /sys/class/backlight/backlight/brightness and stored at shutdown and loaded at boot from /var/lib/systemd/backlight/platform-backlight:backlight:backlight by systemd-backlight@backlight:backlight.service. Changing the brightness setting can be done at runtime, for example over SSH, by executing as root <code>echo 500 > /sys/class/backlight/backlight/brightness</code>. The stored brightness setting can be modified using another system, by mounting at $mnt the root filesystem of the system you want to fix and executing <code>echo 500 > $mnt/var/lib/systemd/backlight/platform-backlight\:backlight\:backlight</code>.<br />
<br />
=== SMS ===<br />
<br />
==== The phone does not receive SMS ====<br />
<br />
Sometimes incoming SMS messages are not being received, but outgoing ones, phone calls and data are working fine. One potential cause could be SMS messages that linger in the modem's queue (10 or more of them). This queue appears to be persistent across reboots and also re-imaging the OS.<br />
<br />
On Mobian and Manjaro, the ModemManager does all the communications with the 3G modem including phone calls, cellular data, GPS and SMS. This may not be the case with other PinePhone OSes.<br />
<br />
You can access the ModemManager using the mmcli command.<br />
<br />
'''Mobian:'''<br />
<br />
<pre>$ sudo mmcli -m 0 --messaging-list-sms<br />
Found 10 SMS messages:<br />
/org/freedesktop/ModemManager1/SMS/0 (received)</pre><br />
<br />
'''Manjaro:'''<br />
<br />
<pre>$ sudo mmcli -m 3 --messaging-list-sms<br />
/org/freedesktop/ModemManager1/SMS/77 (received)</pre><br />
<br />
For Mobian, delete all the messages like this:<br />
<br />
<code>$ sudo mmcli -m 0 --messaging-delete-sms=1</code> (Repeat with 1 through 10 to delete all the messages)<br />
<br />
For Manjaro, delete all the messages like this:<br />
<br />
<code>$ sudo mmcli -m 3 --messaging-delete-sms=77</code> (Repeat with all listed messages)<br />
<br />
Note that the "-m 0" or "-m 3" refers to modem 0 or 3 (the only one in a PinePhone). For more help on the messaging related actions available in mmcli you can check the help with <code>mmcli --help-messaging.</code> This article is also helpful in learning: https://electronproton.com/mmcli-command-examples/. For your particular configuration, you may need to try different "-m #" combinations, e.g., "-m 2" or "-m 4." "-m 0" is not always the default.<br />
<br />
It should also be noted that recent releases of Mobian and postmarketOS now include a userspace daemon called [https://gitlab.com/mobian1/devices/eg25-manager eg25-manager], which helps manage the modem and ensure proper operation.<br />
<br />
== Shipping ==<br />
=== I did not receive an order confirmation ===<br />
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get an order confirmation email.<br />
<br />
=== When does the phone ship? ===<br />
For up-to-date information when the phone's shipping date is estimated, see the edits in the corresponding forum thread.<br />
<br />
=== It is shipping day but I did not receive a shipping notification ===<br />
For shipments with DHL the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.<br />
<br />
=== When does my phone ship if I order now? ===<br />
Orders made after Friday, 22nd May 2020 are shipped after the first bulk of pre-orders has been shipped. The exact date is not known yet due to various reasons, it may be a few weeks after the first bulk shipped. [https://forum.pine64.org/showthread.php?tid=9942 The forum] will be edited with updated information and you will receive a shipping notification when the device was shipped.<br />
<br />
=== What about import taxes? ===<br />
Import taxes have to be paid by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.<br />
<br />
== Accessories ==<br />
<br />
=== Protection ===<br />
==== Which screen protector should I use? ====<br />
<br />
Protecting your screen is important, especially for devices like the PinePhone that doesn't have access to the newest glass technology.<br />
The Braveheart and Community Editions of the PinePhone comes with a plastic film screen protector installed, and PINE64 sells a tempered glass screen protector [https://pine64.com/product/pinephone-tempered-glass-screen-protector/ in their store].<br />
<br />
You can also buy a third-party screen protector, as the screen protectors for the iPhone 11 Pro Max/XS Max fit the PinePhone pretty well based on [https://forum.pine64.org/showthread.php?tid=8458&pid=65409#pid65409 this] forum post.<br />
<br />
=== Batteries ===<br />
==== I want a replacement battery, which one should I buy? ====<br />
<br />
Replacement batteries for US customers are available in the store.<br />
<br />
Currently the PinePhone battery is known to be compatible with replacement batteries for the Samsung J700. Specifically, models "EB-BJ700BBC" and "EB-BJ700BBE" are compatible with all PinePhone models, and "EB-BJ700CBE" is compatible with Community Editions [https://www.reddit.com/r/PINE64official/comments/kcof97/pinephone_replacement_battery_found_and_tested/gfrx4p2/?utm_source=reddit&utm_medium=web2x&context=3 after UBPorts] (due to plastic tabs on its bottom which only the newer phones [https://forum.pine64.org/showthread.php?tid=11901 have tolerance for]).<br />
<br />
=== External hardware ===<br />
<br />
==== Will PINE64 sell other add-ons made for the PinePhone? ====<br />
<br />
Yes, currently there is a keyboard case [https://forum.pine64.org/showthread.php?tid=8537&pid=55396#pid55396 with similarities to the Psion 5] which includes an internal battery, and a [https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/ Qi wireless charging] add-on planned, both of which PINE64 intends to directly sell. There is the potential for future add-ons such as a game pad, however that is currently just an idea and not in any way planned.<br />
<br />
==== Which 3rd party hardware can connect to my PinePhone? ====<br />
<br />
See [[PinePhone Hardware Accessory Compatibility]].<br />
<br />
<br />
[[Category:PinePhone]]</div>Madezhttps://wiki.pine64.org/index.php?title=PinePhone_FAQ&diff=10672PinePhone FAQ2021-06-08T18:46:48Z<p>Madez: /* How can I turn on the backlight? */</p>
<hr />
<div>A list of frequently asked question.<br />
<br />
== Hardware ==<br />
<br />
=== Revisions ===<br />
==== What are Community Editions? ====<br />
Community Editions of the PinePhone were versions of the PinePhone which came preinstalled with the operating system of a partner project and featured the logo of the project on the back panel. The Community Edition was intended to help partner projects developing these systems: "Community editions are meant to bring exposure to partner-projects operating systems and communities, as well as help finance ongoing development.", [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ source].<br />
<br />
==== Is the Community Edition hardware the latest revision? ====<br />
The Community Edition program (featuring the mainboard numbers 1.2 through 1.2b and branded back covers) which provided the branded PinePhones has since ended, and a Beta Edition has since been released. The only difference between each Community Edition is the inclusion of crucial bug fixes, with the last issue being fixed with the 1.2b motherboard shipping with the Manjaro CE PinePhones. The 1.2b motherboard is also currently used in the Beta Edition PinePhones, however the Beta Edition units do not ship with any back cover branding. There are currently no plans for further hardware revisions.<br />
<br />
Aside from the back cover, the only other difference between each Community Edition is that starting with the postmarketOS PinePhone, a convergence package option was released that adds another gigabyte of ram to the phone and a 32GB eMMC instead of a 16GB eMMC. Convergence packages also included a dock for plugging in USB peripherals and connecting to an HDMI monitor, however you can purchase a generic USB-C dock to use with a 2GB PinePhone. <br />
<br />
The predecessor to the Convergence Edition PinePhones was the Braveheart Edition intended for developers to bring up the platform, which had the version number 1.1. For more details about the topic see [[PinePhone#Hardware Revisions]].<br />
<br />
==== Will there be other Community Editions? ====<br />
Five Community Editions have been announced: [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ UBports], [https://www.pine64.org/2020/06/15/june-update-postmarketos-ce-pinephone-shipping-pine64-cluster/ postmarketOS], [https://www.pine64.org/2020/08/31/pinephone-manjaro-community-edition/ Manjaro], [https://www.pine64.org/2020/12/01/kde-community-edition-is-now-available/ KDE], and [https://www.pine64.org/2021/01/17/mobian-community-edition/ Mobian]. Since the release of the Mobian edition, the Beta Edition PinePhones have been released and the Community Edition Program has ended.<br />
<br />
==== In simple terms, what are the differences between Braveheart and the new Community Edition? ====<br />
The Braveheart PinePhone was the first public revision of the PinePhone which was intended solely for developers and Linux enthusiasts. The UBports Community Edition was the next revision of the PinePhone with an updated mainboard based on feedback from the Braveheart Edition, see [[PinePhone#Hardware Revisions]]. All current revisions of the PinePhone continue to be intended for developers and enthusiasts, however, PINE64 will be starting to offer partnered retail units of the PinePhone which will have a better warranty and technical support (keep in mind even then it is not intended for a broader audience at this time, as the software still needs work and the hardware does not hold up well to modern consumer standards).<br />
<br />
==== Will there be a newer revision after the Community Editions? ====<br />
Starting with the UBports Community Edition the PinePhone has gotten CE and FCC certifications, repeating the certification process due to changes in the hardware design is very expensive, so the 1.2b motherboard is viewed as the final revision. The PinePhone (and parts for them) will be produced and sold for at least 5 years.<br />
<br />
==== Will there be hardware differences between the Community Editions? ====<br />
<br />
Besides the varied back covers, starting with the launch of the PostmarketOS CE there has been the release of a convergence package option for the PinePhone which includes more ram and storage, and an included dock for convenience. There has also been multiple hardware changes starting with the UBports CE (mainboard 1.2) and ending with the Manjaro CE (mainboard revision 1.2b). There are currently no plans for future hardware changes for a few years.<br />
<br />
==== How powerful is the PinePhone's hardware? ====<br />
<br />
The PinePhone is about on par with a Raspberry Pi 3 in terms of CPU power, however going by GFLOPS it has half the GPU power. The Pi 3's Videocore IV does 24 GFLOPS, and the Mali 400 MP2 on the PinePhone only 10.8.<br />
<br />
Despite this, using software rendering the PinePhone is capable of smoothly rendering at 1080p resolution or higher. However, with a fully GPU-accelerated mobile environment you should expect a more sluggish experience outputting to such resolutions. Unfortunately, the Mali 400 MP2 (a 2008 arm mobile GPU) simply isn't intended to push 1080p resolution. With that said, the VPU of the PinePhone has been shown to handle smooth H.264 1440p30 video playback using Cedrus and gstreamer as documented [https://xnux.eu/log/#001 here]. Further, the PinePhone should be more than capable of a smooth phone experience when used in conjunction with well optimized software that makes use of its hardware features. It is also more than capable of running many light games (including 3D ones such as SuperTuxKart), and retro gaming. Expect further speed improvements over time as the drivers are improved, and in the meanwhile you can look into slightly [[overclocking]] the device (at your own risk).<br />
<br />
=== Sound ===<br />
<br />
The default ringtone for Mobian Phosh can be found at /usr/share/sounds/freedesktop/stereo/phone-incoming-call.oga<br />
<br />
=== Modem ===<br />
<br />
==== The modem isn't working ====<br />
<br />
In order to use the modem and Wi-Fi/Bluetooth, you need to ensure the battery is inside the device and has a sufficient charge. Even when supplying the phone with enough power, the modem and Wi-Fi chip will not work without a connected battery. Further, double check that you have not put the SD card into the sim card slot, or vice versa.<br />
<br />
==== Does the PinePhone only wake up from sleep for calls and texts? ====<br />
<br />
Yes. Unless the PinePhone is configured to wake up every few minutes from deep sleep in crust (At the cost of battery life. However, in the future there may be other solutions), then there is not any way to get any notifications for applications. The modem on the PinePhone will wake the device for incoming calls and texts however, and the real-time clock is also capable of waking the device for alarms.<br />
<br />
=== Battery ===<br />
<br />
==== The battery is stuck inside the phone ====<br />
<br />
The battery can be stuck in the phone if the screws of the frame are overtightened.<br />
<br />
If your battery is stuck inside the PinePhone, grab a screwdriver and completely unscrew all the screws of the midframe. Then pull out the battery (you may have to fully take off the midframe in some cases to get it out). And then rescrew the midframe, but only tighten the screws to the point where they are just barely tight to hold. This should allow you to remove the battery easily.<br />
<br />
==== The battery is discharging while the phone is powered off (Braveheart Edition) ====<br />
<br />
The issue is not present on the Community Edition. Due to a hardware bug, after power off, the phone still consumes 20–30mA which drains the battery in 3-4 days. A manual procedure to fix the hardware bug is described [https://xnux.eu/devices/pp-pmic-fix.jpg here].<br />
<br />
==== The battery only charges to ~84% ====<br />
<br />
Some pre-made OSes using megi's kernel limit the maximum amount of charge to roughly ~84% in the hope of prolonging the battery life, as repeatedly reaching the upper level of battery charge reduces the battery's lifetime (this is <b>not</b> a safety feature!). The same effect however also applies when repeatedly draining the battery to a low level - users are therefore advised to consider if that setting is reasonable depending on their usage. The setting can be overwritten via Sysfs, to let the battery fully charge (this can lower the replaceable's battery lifetime considerably depending on the charging behavior!):<br />
<br />
{{warning|The following instructions are directed towards expert-level users and developers!}}<br />
<br />
<code>echo 4350000 > /sys/class/power_supply/axp20x-battery/voltage_max_design</code><br />
<br />
=== Kill Switches ===<br />
==== What are the kill switches doing? ====<br />
<br />
{| class="wikitable"<br />
|-<br />
! Number<br />
! Name<br />
! Explanation<br />
! Description<br />
|-<br />
| 1<br />
| Modem<br />
| Pulls Q1501 gate up (FET killing modem power)<br />
| "On" enables cellular communication and GNSS hardware, "off" disables it.<br />
|-<br />
| 2<br />
| Wi-Fi / Bluetooth<br />
| Pulls up CHIP_EN<br />
| "On" enables Wi-Fi and Bluetooth communication hardware, "off" disables it.<br />
|-<br />
| 3<br />
| Microphone<br />
| Breaks microphone bias voltage from the SoC<br />
| "On" enables audio input from on-board microphones (not 3.5mm jack), "off" disables it.<br />
|-<br />
| 4<br />
| Rear camera<br />
| Pulls up PWDN on OV5640 <br />
| "On" enables the rear camera, "off" disables it.<br />
|-<br />
| 5<br />
| Front camera<br />
| Pulls up PWDN on GC2145<br />
| "On" enables the front camera, "off" disables it.<br />
|-<br />
| 6<br />
| Headphone<br />
| Pulls up IN2 on analog switch BCT4717ETB<br />
| "On" enables audio input and output via the 3.5mm audio jack, "off" switches the jack to hardware UART mode.<br />
|}<br />
<br />
=== Memory ===<br />
<br />
==== What's the speed difference between the eMMC and SD cards? ====<br />
Maximum transfer speed of the eMMC is around 85 MB/s, while SD cards are limited to approximately 23 MB/s (even with faster cards).<br />
<br />
=== GPS ===<br />
<br />
==== GPS doesn't work ====<br />
<br />
Like almost all smartphones, the PinePhone GPS antenna is small and can only get a first fix unassisted if the GPS signal is very strong. To make first fix faster and more reliable, phones download assistance data either from the phone network or from the internet. The GPS in the PinePhone modem supports the internet based assistance method, as detailed in the modem documentation, but this is currently only supported by a few distributions, and a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] that shows it can work.<br />
<br />
Until aGPS support becomes standard you'll have to make some manual changes - see for example [https://wiki.mobian-project.org/doku.php?id=location Mobian wiki]<br />
<br />
==== GPS can't determine direction ====<br />
<br />
Currently, due to the magnetometer not being hooked up in software at this time, it is not possible for GPS software to use the phone's compass functionality. This means while you are walking it will not be possible to determine the direction of travel. This is not as much of an issue for vehicles as the faster speeds mean that it is possible to estimate the direction of travel, however it will still be an issue should the vehicle travel through a tunnel and loose GPS signal.<br />
<br />
== Software ==<br />
<br />
=== Installation ===<br />
<br />
==== How can I install an operating system on the SD card / eMMC? ====<br />
<br />
See [[PinePhone Installation Instructions]].<br />
<br />
=== Updating ===<br />
<br />
Read the [[PinePhone Updating Instructions]].<br />
<br />
=== Booting ===<br />
<br />
==== What's the boot order for SD cards and eMMC? ====<br />
<br />
The PinePhone will automatically boot from microSD if a bootable card is inserted. If no (bootable) microSD is found, it will boot from eMMC.<br />
<br />
==== How can I select different OSes at boot? ====<br />
<br />
There was a project by Danct12 which allowed the user to select different OSes at boot, but the repository has since been archived: https://github.com/dreemurrs-embedded/Pineloader.<br />
<br />
==== I turned on my Manjaro CE PinePhone. The red LED and screen backlight are briefly lit, then both are not and it will not boot. ====<br />
<br />
This can be the result of at least one situation:<br />
<br />
# The eMMC installation became corrupt or otherwise unbootable<br />
# An SD card is present but not bootable (consider [[PinePhone#Detailed usage instructions]])<br />
<br />
If there is an installation of Manjaro on both the eMMC & an SD card, the SD card will always boot first on the device. Try taking the SD card out and booting the installation that is on the eMMC. If the problem persists, it is likely there is an issue with both installations and you will need to reinstall your distribution. You may also want to check with your distribution's maintainers if boot issues are a common problem in a recent update.<br />
<br />
==== I did not install an update in Ubuntu Touch and I'm stuck on the PINE64 logo after rebooting. ====<br />
<br />
# Use a USB A-C cable to plug your phone into your PC<br />
# Hold the PinePhone's power button for 4 seconds or more to power it off.<br />
# Wait 5 seconds<br />
# Hold the Volume Up and Power buttons on the PinePhone to boot into recovery. You should see the LED light red, then yellow, then green. The "Installing update" screen will appear, but a progress bar to indicate update progress will not. Ignore the "Installing update" part.<br />
# Your PC may automatically mount the PinePhone's partitions. If it does, Safely Remove or Eject all of them.<br />
# Open a terminal on your PC. Type <code>telnet 172.16.42.1</code><br />
# You should receive the text 'Welcome to Rescue SD Shell!'<br />
# In the new Rescue SD shell, type <code>umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync</code><br />
# Once this command pipeline finishes, type <code>sync && reboot -f</code><br />
<br />
Your PinePhone should reboot into Ubuntu Touch. Now head to Settings -> Updates and install the new update! <br />
<br />
If these steps did not solve your issue, please create a new thread here on the PINE64 forums, note what the problem looks like, then say that you've tried these steps already.<br />
<br />
This is caused by corruption on the userdata partition. Normally this should be fixed by 'e2fsck' in the initramfs, however, an error in image creation means that that version of e2fsck is unable to correct the corruption. This has been fixed in all new PinePhone updates, so if you update from the factory image to any other image available to the PinePhone now, you will not experience this issue any longer.<br />
<br />
==== I turned on my PinePhone running Ubuntu Touch. The red LED is lit and it will not boot. ====<br />
# Hold the power button until the light turns off<br />
# Hold the power button until the light turns on<br />
<br />
You may need to repeat these steps more than once.<br />
<br />
This is caused by u-boot apparently trying to use the eMMC before it is ready. We are not entirely sure why this occurs yet.<br />
<br />
==== Can I install a different OS on my Community Edition? ====<br />
<br />
Yes! While all the Community Edition PinePhones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see [[PinePhone Installation Instructions]] and [[PinePhone Software Releases]] on how to install them.<br />
<br />
=== Other ===<br />
<br />
==== How can I enable SSH? ====<br />
<br />
In Ubuntu Touch you can run "sudo start ssh" to get a one-time start, or edit /etc/init/ssh.override and remove the manual line to make it auto-start.<br />
<br />
In other distributions you may have to install SSH through its package manager and then proceed to use its init system to enable it. For Manjaro, Arch, and Mobian you can use "systemctl enable" and "systemctl start" command to enable and start ssh.<br />
<br />
==== What works, what doesn't? ====<br />
<br />
For Ubuntu Touch see https://gitlab.com/ubports/community-ports/pinephone#what-works-what-doesnt.<br />
<br />
Other distributions will have different levels of functionality. Please refer to the release page of your chosen distribution for further information.<br />
<br />
==== I can't connect to a 2.4Ghz Wi-Fi network in Ubuntu Touch. ====<br />
<br />
Reboot your device by holding the power button until the "Power" dialog appears, then pressing "Restart".<br />
<br />
If that does not fix the issue, note that all the following conditions must be met to use Wi-Fi on the PinePhone:<br />
<br />
# The plastic tab between the battery and the device's battery contacts has been removed<br />
# The battery is installed<br />
# The Wi-Fi killswitch, #2, on the rear of the device is switched "ON"<br />
<br />
Wi-Fi in the PinePhone only seems stable after a warm reboot like this.<br />
<br />
==== What's the status of Android for the PinePhone? ====<br />
<br />
Currently, there isn't any major push to get Android running well on the PinePhone. The developer Icenowy did get a Android image to run and partly work, it was however slow and buggy, with major functions not working. A solution for running some of your android apps may be found in Anbox as of now. Anbox is currently not included in Ubuntu Touch. In other distributions your millage may vary on what applications will run and how well.<br />
<br />
==== Why are my apps loading slower than on my Android phone? ====<br />
<br />
Android has multiple techniques in place to speed up launching applications after the first launch, such as the "Dalvik cache".<br />
<br />
Using an alternative filesystem such as F2FS on the eMMC (which is considerably faster than running software on the SD card) may help improve performance slightly. Over time you can expect further optimizations and improvements in various distributions that will help speed up the PinePhone.<br />
<br />
==== How can I turn on the backlight? ====<br />
<br />
When the brightness is too low, the backlight turns off completely. At which point this happens requires calibration. It also depends on whether the device is being charged or not, due to how the backlight is physically regulated. The backlight can be turned on by increasing the brightness. If the brightness is too low but non-zero, as can happen when using a gui slider, try connecting the phone to a charger.<br />
<br />
On most systems the brightness level is an integer between 0 and 1000 and available at runtime in /sys/class/backlight/backlight/brightness and stored at shutdown and loaded at boot from /var/lib/systemd/backlight/platform-backlight:backlight:backlight by systemd-backlight. Changing the brightness can be done at runtime, for example over SSH, by executing as root <code>echo 500 > /sys/class/backlight/backlight/brightness</code>. The stored brightness can be modified using another system, by mounting at $mnt the root filesystem of the system you want to fix and executing <code>echo 500 > $mnt/var/lib/systemd/backlight/platform-backlight\:backlight\:backlight</code>.<br />
<br />
=== SMS ===<br />
<br />
==== The phone does not receive SMS ====<br />
<br />
Sometimes incoming SMS messages are not being received, but outgoing ones, phone calls and data are working fine. One potential cause could be SMS messages that linger in the modem's queue (10 or more of them). This queue appears to be persistent across reboots and also re-imaging the OS.<br />
<br />
On Mobian and Manjaro, the ModemManager does all the communications with the 3G modem including phone calls, cellular data, GPS and SMS. This may not be the case with other PinePhone OSes.<br />
<br />
You can access the ModemManager using the mmcli command.<br />
<br />
'''Mobian:'''<br />
<br />
<pre>$ sudo mmcli -m 0 --messaging-list-sms<br />
Found 10 SMS messages:<br />
/org/freedesktop/ModemManager1/SMS/0 (received)</pre><br />
<br />
'''Manjaro:'''<br />
<br />
<pre>$ sudo mmcli -m 3 --messaging-list-sms<br />
/org/freedesktop/ModemManager1/SMS/77 (received)</pre><br />
<br />
For Mobian, delete all the messages like this:<br />
<br />
<code>$ sudo mmcli -m 0 --messaging-delete-sms=1</code> (Repeat with 1 through 10 to delete all the messages)<br />
<br />
For Manjaro, delete all the messages like this:<br />
<br />
<code>$ sudo mmcli -m 3 --messaging-delete-sms=77</code> (Repeat with all listed messages)<br />
<br />
Note that the "-m 0" or "-m 3" refers to modem 0 or 3 (the only one in a PinePhone). For more help on the messaging related actions available in mmcli you can check the help with <code>mmcli --help-messaging.</code> This article is also helpful in learning: https://electronproton.com/mmcli-command-examples/. For your particular configuration, you may need to try different "-m #" combinations, e.g., "-m 2" or "-m 4." "-m 0" is not always the default.<br />
<br />
It should also be noted that recent releases of Mobian and postmarketOS now include a userspace daemon called [https://gitlab.com/mobian1/devices/eg25-manager eg25-manager], which helps manage the modem and ensure proper operation.<br />
<br />
== Shipping ==<br />
=== I did not receive an order confirmation ===<br />
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get an order confirmation email.<br />
<br />
=== When does the phone ship? ===<br />
For up-to-date information when the phone's shipping date is estimated, see the edits in the corresponding forum thread.<br />
<br />
=== It is shipping day but I did not receive a shipping notification ===<br />
For shipments with DHL the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.<br />
<br />
=== When does my phone ship if I order now? ===<br />
Orders made after Friday, 22nd May 2020 are shipped after the first bulk of pre-orders has been shipped. The exact date is not known yet due to various reasons, it may be a few weeks after the first bulk shipped. [https://forum.pine64.org/showthread.php?tid=9942 The forum] will be edited with updated information and you will receive a shipping notification when the device was shipped.<br />
<br />
=== What about import taxes? ===<br />
Import taxes have to be paid by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.<br />
<br />
== Accessories ==<br />
<br />
=== Protection ===<br />
==== Which screen protector should I use? ====<br />
<br />
Protecting your screen is important, especially for devices like the PinePhone that doesn't have access to the newest glass technology.<br />
The Braveheart and Community Editions of the PinePhone comes with a plastic film screen protector installed, and PINE64 sells a tempered glass screen protector [https://pine64.com/product/pinephone-tempered-glass-screen-protector/ in their store].<br />
<br />
You can also buy a third-party screen protector, as the screen protectors for the iPhone 11 Pro Max/XS Max fit the PinePhone pretty well based on [https://forum.pine64.org/showthread.php?tid=8458&pid=65409#pid65409 this] forum post.<br />
<br />
=== Batteries ===<br />
==== I want a replacement battery, which one should I buy? ====<br />
<br />
Replacement batteries for US customers are available in the store.<br />
<br />
Currently the PinePhone battery is known to be compatible with replacement batteries for the Samsung J700. Specifically, models "EB-BJ700BBC" and "EB-BJ700BBE" are compatible with all PinePhone models, and "EB-BJ700CBE" is compatible with Community Editions [https://www.reddit.com/r/PINE64official/comments/kcof97/pinephone_replacement_battery_found_and_tested/gfrx4p2/?utm_source=reddit&utm_medium=web2x&context=3 after UBPorts] (due to plastic tabs on its bottom which only the newer phones [https://forum.pine64.org/showthread.php?tid=11901 have tolerance for]).<br />
<br />
=== External hardware ===<br />
<br />
==== Will PINE64 sell other add-ons made for the PinePhone? ====<br />
<br />
Yes, currently there is a keyboard case [https://forum.pine64.org/showthread.php?tid=8537&pid=55396#pid55396 with similarities to the Psion 5] which includes an internal battery, and a [https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/ Qi wireless charging] add-on planned, both of which PINE64 intends to directly sell. There is the potential for future add-ons such as a game pad, however that is currently just an idea and not in any way planned.<br />
<br />
==== Which 3rd party hardware can connect to my PinePhone? ====<br />
<br />
See [[PinePhone Hardware Accessory Compatibility]].<br />
<br />
<br />
[[Category:PinePhone]]</div>Madezhttps://wiki.pine64.org/index.php?title=PinePhone_FAQ&diff=10671PinePhone FAQ2021-06-08T17:22:53Z<p>Madez: /* How can I turn on the backlight? */</p>
<hr />
<div>A list of frequently asked question.<br />
<br />
== Hardware ==<br />
<br />
=== Revisions ===<br />
==== What are Community Editions? ====<br />
Community Editions of the PinePhone were versions of the PinePhone which came preinstalled with the operating system of a partner project and featured the logo of the project on the back panel. The Community Edition was intended to help partner projects developing these systems: "Community editions are meant to bring exposure to partner-projects operating systems and communities, as well as help finance ongoing development.", [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ source].<br />
<br />
==== Is the Community Edition hardware the latest revision? ====<br />
The Community Edition program (featuring the mainboard numbers 1.2 through 1.2b and branded back covers) which provided the branded PinePhones has since ended, and a Beta Edition has since been released. The only difference between each Community Edition is the inclusion of crucial bug fixes, with the last issue being fixed with the 1.2b motherboard shipping with the Manjaro CE PinePhones. The 1.2b motherboard is also currently used in the Beta Edition PinePhones, however the Beta Edition units do not ship with any back cover branding. There are currently no plans for further hardware revisions.<br />
<br />
Aside from the back cover, the only other difference between each Community Edition is that starting with the postmarketOS PinePhone, a convergence package option was released that adds another gigabyte of ram to the phone and a 32GB eMMC instead of a 16GB eMMC. Convergence packages also included a dock for plugging in USB peripherals and connecting to an HDMI monitor, however you can purchase a generic USB-C dock to use with a 2GB PinePhone. <br />
<br />
The predecessor to the Convergence Edition PinePhones was the Braveheart Edition intended for developers to bring up the platform, which had the version number 1.1. For more details about the topic see [[PinePhone#Hardware Revisions]].<br />
<br />
==== Will there be other Community Editions? ====<br />
Five Community Editions have been announced: [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ UBports], [https://www.pine64.org/2020/06/15/june-update-postmarketos-ce-pinephone-shipping-pine64-cluster/ postmarketOS], [https://www.pine64.org/2020/08/31/pinephone-manjaro-community-edition/ Manjaro], [https://www.pine64.org/2020/12/01/kde-community-edition-is-now-available/ KDE], and [https://www.pine64.org/2021/01/17/mobian-community-edition/ Mobian]. Since the release of the Mobian edition, the Beta Edition PinePhones have been released and the Community Edition Program has ended.<br />
<br />
==== In simple terms, what are the differences between Braveheart and the new Community Edition? ====<br />
The Braveheart PinePhone was the first public revision of the PinePhone which was intended solely for developers and Linux enthusiasts. The UBports Community Edition was the next revision of the PinePhone with an updated mainboard based on feedback from the Braveheart Edition, see [[PinePhone#Hardware Revisions]]. All current revisions of the PinePhone continue to be intended for developers and enthusiasts, however, PINE64 will be starting to offer partnered retail units of the PinePhone which will have a better warranty and technical support (keep in mind even then it is not intended for a broader audience at this time, as the software still needs work and the hardware does not hold up well to modern consumer standards).<br />
<br />
==== Will there be a newer revision after the Community Editions? ====<br />
Starting with the UBports Community Edition the PinePhone has gotten CE and FCC certifications, repeating the certification process due to changes in the hardware design is very expensive, so the 1.2b motherboard is viewed as the final revision. The PinePhone (and parts for them) will be produced and sold for at least 5 years.<br />
<br />
==== Will there be hardware differences between the Community Editions? ====<br />
<br />
Besides the varied back covers, starting with the launch of the PostmarketOS CE there has been the release of a convergence package option for the PinePhone which includes more ram and storage, and an included dock for convenience. There has also been multiple hardware changes starting with the UBports CE (mainboard 1.2) and ending with the Manjaro CE (mainboard revision 1.2b). There are currently no plans for future hardware changes for a few years.<br />
<br />
==== How powerful is the PinePhone's hardware? ====<br />
<br />
The PinePhone is about on par with a Raspberry Pi 3 in terms of CPU power, however going by GFLOPS it has half the GPU power. The Pi 3's Videocore IV does 24 GFLOPS, and the Mali 400 MP2 on the PinePhone only 10.8.<br />
<br />
Despite this, using software rendering the PinePhone is capable of smoothly rendering at 1080p resolution or higher. However, with a fully GPU-accelerated mobile environment you should expect a more sluggish experience outputting to such resolutions. Unfortunately, the Mali 400 MP2 (a 2008 arm mobile GPU) simply isn't intended to push 1080p resolution. With that said, the VPU of the PinePhone has been shown to handle smooth H.264 1440p30 video playback using Cedrus and gstreamer as documented [https://xnux.eu/log/#001 here]. Further, the PinePhone should be more than capable of a smooth phone experience when used in conjunction with well optimized software that makes use of its hardware features. It is also more than capable of running many light games (including 3D ones such as SuperTuxKart), and retro gaming. Expect further speed improvements over time as the drivers are improved, and in the meanwhile you can look into slightly [[overclocking]] the device (at your own risk).<br />
<br />
=== Sound ===<br />
<br />
The default ringtone for Mobian Phosh can be found at /usr/share/sounds/freedesktop/stereo/phone-incoming-call.oga<br />
<br />
=== Modem ===<br />
<br />
==== The modem isn't working ====<br />
<br />
In order to use the modem and Wi-Fi/Bluetooth, you need to ensure the battery is inside the device and has a sufficient charge. Even when supplying the phone with enough power, the modem and Wi-Fi chip will not work without a connected battery. Further, double check that you have not put the SD card into the sim card slot, or vice versa.<br />
<br />
==== Does the PinePhone only wake up from sleep for calls and texts? ====<br />
<br />
Yes. Unless the PinePhone is configured to wake up every few minutes from deep sleep in crust (At the cost of battery life. However, in the future there may be other solutions), then there is not any way to get any notifications for applications. The modem on the PinePhone will wake the device for incoming calls and texts however, and the real-time clock is also capable of waking the device for alarms.<br />
<br />
=== Battery ===<br />
<br />
==== The battery is stuck inside the phone ====<br />
<br />
The battery can be stuck in the phone if the screws of the frame are overtightened.<br />
<br />
If your battery is stuck inside the PinePhone, grab a screwdriver and completely unscrew all the screws of the midframe. Then pull out the battery (you may have to fully take off the midframe in some cases to get it out). And then rescrew the midframe, but only tighten the screws to the point where they are just barely tight to hold. This should allow you to remove the battery easily.<br />
<br />
==== The battery is discharging while the phone is powered off (Braveheart Edition) ====<br />
<br />
The issue is not present on the Community Edition. Due to a hardware bug, after power off, the phone still consumes 20–30mA which drains the battery in 3-4 days. A manual procedure to fix the hardware bug is described [https://xnux.eu/devices/pp-pmic-fix.jpg here].<br />
<br />
==== The battery only charges to ~84% ====<br />
<br />
Some pre-made OSes using megi's kernel limit the maximum amount of charge to roughly ~84% in the hope of prolonging the battery life, as repeatedly reaching the upper level of battery charge reduces the battery's lifetime (this is <b>not</b> a safety feature!). The same effect however also applies when repeatedly draining the battery to a low level - users are therefore advised to consider if that setting is reasonable depending on their usage. The setting can be overwritten via Sysfs, to let the battery fully charge (this can lower the replaceable's battery lifetime considerably depending on the charging behavior!):<br />
<br />
{{warning|The following instructions are directed towards expert-level users and developers!}}<br />
<br />
<code>echo 4350000 > /sys/class/power_supply/axp20x-battery/voltage_max_design</code><br />
<br />
=== Kill Switches ===<br />
==== What are the kill switches doing? ====<br />
<br />
{| class="wikitable"<br />
|-<br />
! Number<br />
! Name<br />
! Explanation<br />
! Description<br />
|-<br />
| 1<br />
| Modem<br />
| Pulls Q1501 gate up (FET killing modem power)<br />
| "On" enables cellular communication and GNSS hardware, "off" disables it.<br />
|-<br />
| 2<br />
| Wi-Fi / Bluetooth<br />
| Pulls up CHIP_EN<br />
| "On" enables Wi-Fi and Bluetooth communication hardware, "off" disables it.<br />
|-<br />
| 3<br />
| Microphone<br />
| Breaks microphone bias voltage from the SoC<br />
| "On" enables audio input from on-board microphones (not 3.5mm jack), "off" disables it.<br />
|-<br />
| 4<br />
| Rear camera<br />
| Pulls up PWDN on OV5640 <br />
| "On" enables the rear camera, "off" disables it.<br />
|-<br />
| 5<br />
| Front camera<br />
| Pulls up PWDN on GC2145<br />
| "On" enables the front camera, "off" disables it.<br />
|-<br />
| 6<br />
| Headphone<br />
| Pulls up IN2 on analog switch BCT4717ETB<br />
| "On" enables audio input and output via the 3.5mm audio jack, "off" switches the jack to hardware UART mode.<br />
|}<br />
<br />
=== Memory ===<br />
<br />
==== What's the speed difference between the eMMC and SD cards? ====<br />
Maximum transfer speed of the eMMC is around 85 MB/s, while SD cards are limited to approximately 23 MB/s (even with faster cards).<br />
<br />
=== GPS ===<br />
<br />
==== GPS doesn't work ====<br />
<br />
Like almost all smartphones, the PinePhone GPS antenna is small and can only get a first fix unassisted if the GPS signal is very strong. To make first fix faster and more reliable, phones download assistance data either from the phone network or from the internet. The GPS in the PinePhone modem supports the internet based assistance method, as detailed in the modem documentation, but this is currently only supported by a few distributions, and a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] that shows it can work.<br />
<br />
Until aGPS support becomes standard you'll have to make some manual changes - see for example [https://wiki.mobian-project.org/doku.php?id=location Mobian wiki]<br />
<br />
==== GPS can't determine direction ====<br />
<br />
Currently, due to the magnetometer not being hooked up in software at this time, it is not possible for GPS software to use the phone's compass functionality. This means while you are walking it will not be possible to determine the direction of travel. This is not as much of an issue for vehicles as the faster speeds mean that it is possible to estimate the direction of travel, however it will still be an issue should the vehicle travel through a tunnel and loose GPS signal.<br />
<br />
== Software ==<br />
<br />
=== Installation ===<br />
<br />
==== How can I install an operating system on the SD card / eMMC? ====<br />
<br />
See [[PinePhone Installation Instructions]].<br />
<br />
=== Updating ===<br />
<br />
Read the [[PinePhone Updating Instructions]].<br />
<br />
=== Booting ===<br />
<br />
==== What's the boot order for SD cards and eMMC? ====<br />
<br />
The PinePhone will automatically boot from microSD if a bootable card is inserted. If no (bootable) microSD is found, it will boot from eMMC.<br />
<br />
==== How can I select different OSes at boot? ====<br />
<br />
There was a project by Danct12 which allowed the user to select different OSes at boot, but the repository has since been archived: https://github.com/dreemurrs-embedded/Pineloader.<br />
<br />
==== I turned on my Manjaro CE PinePhone. The red LED and screen backlight are briefly lit, then both are not and it will not boot. ====<br />
<br />
This can be the result of at least one situation:<br />
<br />
# The eMMC installation became corrupt or otherwise unbootable<br />
# An SD card is present but not bootable (consider [[PinePhone#Detailed usage instructions]])<br />
<br />
If there is an installation of Manjaro on both the eMMC & an SD card, the SD card will always boot first on the device. Try taking the SD card out and booting the installation that is on the eMMC. If the problem persists, it is likely there is an issue with both installations and you will need to reinstall your distribution. You may also want to check with your distribution's maintainers if boot issues are a common problem in a recent update.<br />
<br />
==== I did not install an update in Ubuntu Touch and I'm stuck on the PINE64 logo after rebooting. ====<br />
<br />
# Use a USB A-C cable to plug your phone into your PC<br />
# Hold the PinePhone's power button for 4 seconds or more to power it off.<br />
# Wait 5 seconds<br />
# Hold the Volume Up and Power buttons on the PinePhone to boot into recovery. You should see the LED light red, then yellow, then green. The "Installing update" screen will appear, but a progress bar to indicate update progress will not. Ignore the "Installing update" part.<br />
# Your PC may automatically mount the PinePhone's partitions. If it does, Safely Remove or Eject all of them.<br />
# Open a terminal on your PC. Type <code>telnet 172.16.42.1</code><br />
# You should receive the text 'Welcome to Rescue SD Shell!'<br />
# In the new Rescue SD shell, type <code>umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync</code><br />
# Once this command pipeline finishes, type <code>sync && reboot -f</code><br />
<br />
Your PinePhone should reboot into Ubuntu Touch. Now head to Settings -> Updates and install the new update! <br />
<br />
If these steps did not solve your issue, please create a new thread here on the PINE64 forums, note what the problem looks like, then say that you've tried these steps already.<br />
<br />
This is caused by corruption on the userdata partition. Normally this should be fixed by 'e2fsck' in the initramfs, however, an error in image creation means that that version of e2fsck is unable to correct the corruption. This has been fixed in all new PinePhone updates, so if you update from the factory image to any other image available to the PinePhone now, you will not experience this issue any longer.<br />
<br />
==== I turned on my PinePhone running Ubuntu Touch. The red LED is lit and it will not boot. ====<br />
# Hold the power button until the light turns off<br />
# Hold the power button until the light turns on<br />
<br />
You may need to repeat these steps more than once.<br />
<br />
This is caused by u-boot apparently trying to use the eMMC before it is ready. We are not entirely sure why this occurs yet.<br />
<br />
==== Can I install a different OS on my Community Edition? ====<br />
<br />
Yes! While all the Community Edition PinePhones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see [[PinePhone Installation Instructions]] and [[PinePhone Software Releases]] on how to install them.<br />
<br />
=== Other ===<br />
<br />
==== How can I enable SSH? ====<br />
<br />
In Ubuntu Touch you can run "sudo start ssh" to get a one-time start, or edit /etc/init/ssh.override and remove the manual line to make it auto-start.<br />
<br />
In other distributions you may have to install SSH through its package manager and then proceed to use its init system to enable it. For Manjaro, Arch, and Mobian you can use "systemctl enable" and "systemctl start" command to enable and start ssh.<br />
<br />
==== What works, what doesn't? ====<br />
<br />
For Ubuntu Touch see https://gitlab.com/ubports/community-ports/pinephone#what-works-what-doesnt.<br />
<br />
Other distributions will have different levels of functionality. Please refer to the release page of your chosen distribution for further information.<br />
<br />
==== I can't connect to a 2.4Ghz Wi-Fi network in Ubuntu Touch. ====<br />
<br />
Reboot your device by holding the power button until the "Power" dialog appears, then pressing "Restart".<br />
<br />
If that does not fix the issue, note that all the following conditions must be met to use Wi-Fi on the PinePhone:<br />
<br />
# The plastic tab between the battery and the device's battery contacts has been removed<br />
# The battery is installed<br />
# The Wi-Fi killswitch, #2, on the rear of the device is switched "ON"<br />
<br />
Wi-Fi in the PinePhone only seems stable after a warm reboot like this.<br />
<br />
==== What's the status of Android for the PinePhone? ====<br />
<br />
Currently, there isn't any major push to get Android running well on the PinePhone. The developer Icenowy did get a Android image to run and partly work, it was however slow and buggy, with major functions not working. A solution for running some of your android apps may be found in Anbox as of now. Anbox is currently not included in Ubuntu Touch. In other distributions your millage may vary on what applications will run and how well.<br />
<br />
==== Why are my apps loading slower than on my Android phone? ====<br />
<br />
Android has multiple techniques in place to speed up launching applications after the first launch, such as the "Dalvik cache".<br />
<br />
Using an alternative filesystem such as F2FS on the eMMC (which is considerably faster than running software on the SD card) may help improve performance slightly. Over time you can expect further optimizations and improvements in various distributions that will help speed up the PinePhone.<br />
<br />
==== How can I turn on the backlight? ====<br />
<br />
When the brightness is too low, the backlight turns off completely. At which point this happens requires calibration. It also depends on whether the device is being charged or not, due to how the backlight is physically regulated. Recovering from the backlight being off can be done by increasing the brightness. If the brightness is too low but non-zero, as can happen when using a gui slider, try connecting the phone to a charger.<br />
<br />
On most systems the brightness level is an integer between 0 and 1000 and available at runtime in /sys/class/backlight/backlight/brightness and stored at shutdown and loaded at boot from /var/lib/systemd/backlight/platform-backlight:backlight:backlight by systemd-backlight. Changing the brightness can be done at runtime, for example over SSH, by executing as root <code>echo 500 > /sys/class/backlight/backlight/brightness</code>. The stored brightness can be modified using another system, by mounting at $mnt the root filesystem of the system you want to fix and executing <code>echo 500 > $mnt/var/lib/systemd/backlight/platform-backlight\:backlight\:backlight</code>.<br />
<br />
=== SMS ===<br />
<br />
==== The phone does not receive SMS ====<br />
<br />
Sometimes incoming SMS messages are not being received, but outgoing ones, phone calls and data are working fine. One potential cause could be SMS messages that linger in the modem's queue (10 or more of them). This queue appears to be persistent across reboots and also re-imaging the OS.<br />
<br />
On Mobian and Manjaro, the ModemManager does all the communications with the 3G modem including phone calls, cellular data, GPS and SMS. This may not be the case with other PinePhone OSes.<br />
<br />
You can access the ModemManager using the mmcli command.<br />
<br />
'''Mobian:'''<br />
<br />
<pre>$ sudo mmcli -m 0 --messaging-list-sms<br />
Found 10 SMS messages:<br />
/org/freedesktop/ModemManager1/SMS/0 (received)</pre><br />
<br />
'''Manjaro:'''<br />
<br />
<pre>$ sudo mmcli -m 3 --messaging-list-sms<br />
/org/freedesktop/ModemManager1/SMS/77 (received)</pre><br />
<br />
For Mobian, delete all the messages like this:<br />
<br />
<code>$ sudo mmcli -m 0 --messaging-delete-sms=1</code> (Repeat with 1 through 10 to delete all the messages)<br />
<br />
For Manjaro, delete all the messages like this:<br />
<br />
<code>$ sudo mmcli -m 3 --messaging-delete-sms=77</code> (Repeat with all listed messages)<br />
<br />
Note that the "-m 0" or "-m 3" refers to modem 0 or 3 (the only one in a PinePhone). For more help on the messaging related actions available in mmcli you can check the help with <code>mmcli --help-messaging.</code> This article is also helpful in learning: https://electronproton.com/mmcli-command-examples/. For your particular configuration, you may need to try different "-m #" combinations, e.g., "-m 2" or "-m 4." "-m 0" is not always the default.<br />
<br />
It should also be noted that recent releases of Mobian and postmarketOS now include a userspace daemon called [https://gitlab.com/mobian1/devices/eg25-manager eg25-manager], which helps manage the modem and ensure proper operation.<br />
<br />
== Shipping ==<br />
=== I did not receive an order confirmation ===<br />
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get an order confirmation email.<br />
<br />
=== When does the phone ship? ===<br />
For up-to-date information when the phone's shipping date is estimated, see the edits in the corresponding forum thread.<br />
<br />
=== It is shipping day but I did not receive a shipping notification ===<br />
For shipments with DHL the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.<br />
<br />
=== When does my phone ship if I order now? ===<br />
Orders made after Friday, 22nd May 2020 are shipped after the first bulk of pre-orders has been shipped. The exact date is not known yet due to various reasons, it may be a few weeks after the first bulk shipped. [https://forum.pine64.org/showthread.php?tid=9942 The forum] will be edited with updated information and you will receive a shipping notification when the device was shipped.<br />
<br />
=== What about import taxes? ===<br />
Import taxes have to be paid by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.<br />
<br />
== Accessories ==<br />
<br />
=== Protection ===<br />
==== Which screen protector should I use? ====<br />
<br />
Protecting your screen is important, especially for devices like the PinePhone that doesn't have access to the newest glass technology.<br />
The Braveheart and Community Editions of the PinePhone comes with a plastic film screen protector installed, and PINE64 sells a tempered glass screen protector [https://pine64.com/product/pinephone-tempered-glass-screen-protector/ in their store].<br />
<br />
You can also buy a third-party screen protector, as the screen protectors for the iPhone 11 Pro Max/XS Max fit the PinePhone pretty well based on [https://forum.pine64.org/showthread.php?tid=8458&pid=65409#pid65409 this] forum post.<br />
<br />
=== Batteries ===<br />
==== I want a replacement battery, which one should I buy? ====<br />
<br />
Replacement batteries for US customers are available in the store.<br />
<br />
Currently the PinePhone battery is known to be compatible with replacement batteries for the Samsung J700. Specifically, models "EB-BJ700BBC" and "EB-BJ700BBE" are compatible with all PinePhone models, and "EB-BJ700CBE" is compatible with Community Editions [https://www.reddit.com/r/PINE64official/comments/kcof97/pinephone_replacement_battery_found_and_tested/gfrx4p2/?utm_source=reddit&utm_medium=web2x&context=3 after UBPorts] (due to plastic tabs on its bottom which only the newer phones [https://forum.pine64.org/showthread.php?tid=11901 have tolerance for]).<br />
<br />
=== External hardware ===<br />
<br />
==== Will PINE64 sell other add-ons made for the PinePhone? ====<br />
<br />
Yes, currently there is a keyboard case [https://forum.pine64.org/showthread.php?tid=8537&pid=55396#pid55396 with similarities to the Psion 5] which includes an internal battery, and a [https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/ Qi wireless charging] add-on planned, both of which PINE64 intends to directly sell. There is the potential for future add-ons such as a game pad, however that is currently just an idea and not in any way planned.<br />
<br />
==== Which 3rd party hardware can connect to my PinePhone? ====<br />
<br />
See [[PinePhone Hardware Accessory Compatibility]].<br />
<br />
<br />
[[Category:PinePhone]]</div>Madezhttps://wiki.pine64.org/index.php?title=PinePhone_Carrier_Support&diff=10649PinePhone Carrier Support2021-06-07T15:46:14Z<p>Madez: /* Europe */</p>
<hr />
<div>{{under construction}}<br />
<br />
{{hint|MMS currently doesn't work in any distribution on the PinePhone without a [[PinePhone_Carrier_Support#MMS_workarounds|script]]! This means images and group chats will not work in text messages.}}<br />
<br />
This page contains hints on setting up cellular network connectivity for specific carriers.<br />
For more general information, see [[PinePhone#Modem_and_carrier_support|Modem and carrier support]]. For the APN settings see [[PinePhone APN Settings]].<br />
<br />
= Check compatibility =<br />
To check if the PinePhone is supported on your carrier:<br />
<br />
Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed in the [https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.pdf modem specification sheet]).<br />
<br />
It is likely that there will be a few frequencies that your carrier uses which are not supported by the PinePhone. Not all of the carrier's frequencies need to be supported by the PinePhone for it to work - as long as ''most'' of them are supported, you will still get good coverage.<br />
<br />
= Tested and working carriers =<br />
<br />
The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):<br />
<br />
== Asia ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021<br />
|-<br />
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021<br />
|-<br />
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021<br />
|}<br />
<br />
== Africa ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Europe ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21<br />
|-<br />
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021<br />
|-<br />
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date) with Phosh, 2021-06-07<br />
|-<br />
|}<br />
<br />
== North America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| USA || T-Mobile || Yes || No || Yes || Yes || <br />
* Arch Linux Arm 2020/11/29 <br />
* Mobian - Phosh <br />
* Manjaro - KDE Plasma Mobile<br />
|-<br />
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm (Phosh,SXMO) 2021/04/29 <br />
*Manjaro - Phosh 2021/04/29 <br />
*Mobian - Phosh 2021/3/20<br />
|-<br />
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy || <br />
*Manjaro - Plasma Dev 2020/11/21 <br />
*Ubuntu Touch - 2020/11/26 <br />
*KDE Neon 2020/11/02<br />
|-<br />
| USA || Mint Mobile (T-Mobile) || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/14<br />
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26<br />
*Ubuntu Touch 2021/5/24<br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/1<br />
|-<br />
| USA || Verizon || No || No || No || No ||<br />
*Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes) <br />
|-<br />
| USA || Verizon || Not tested || Not tested || Yes || Not via gui || <br />
*Manjaro - KDE Plasma Mobile 2021/5/10 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Not via gui || <br />
*Manjaro - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*postmarketOS - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Arch - Phosh 2021/5/31 <br />
|-<br />
| Canada || Freedom || Yes || Not tested || Yes || Yes || <br />
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25 <br />
|-<br />
| USA || FaithWireless (AT&T) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 2021/04/29 (version 0.10.1-1, see the [[PinePhone_Carrier_Support#AT.26T|AT&T issues]] below.)<br />
|-<br />
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 0.10.2 2021/05/29<br />
|}<br />
<br />
== South America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Australia / Oceania ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Middle East ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Israel|| Cellcom prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
|-<br />
| Israel|| Golan TC || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Partner prepay || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Pelephone prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Hot prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| 019 prepay|| No || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
= Special carrier notes =<br />
<br />
{{Warning|This section contains providers which do not work or require special settings or actions to work.}}<br />
<br />
Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:<br />
<br />
== USA ==<br />
=== AT&T ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. The PinePhone seems to work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. VoLTE is as yet untested.<br />
<br />
However, it is likely AT&T will drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.<br />
<br />
=== Cricket Wireless ===<br />
Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).<br />
<br />
=== SimpleMobile ===<br />
SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.<br />
<br />
=== Sprint ===<br />
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.<br />
<br />
=== T-Mobile ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).<br />
<br />
T-Mobile's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].<br />
<br />
While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.<br />
<br />
=== Verizon ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.<br />
<br />
Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.<br />
<br />
=== Google Fi ===<br />
Only T-Mobile service works currently, not US Cellular or Sprint.<br />
The APN is h2g2.<br />
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].<br />
<br />
Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps. <br />
<br />
It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.<br />
<br />
= Known issues =<br />
Known issues:<br />
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.<br />
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.<br />
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.<br />
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].<br />
<br />
= MMS workarounds =<br />
These scripts allow partial MMS support on a [[PinePhone]]:<br />
<br />
* JMMS: [https://git.sr.ht/~amindfv/jmms]<br />
* silvermms: [https://gitlab.com/5ilver/silvermms]<br />
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]<br />
<br />
There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.<br />
<br />
= Resources =<br />
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]<br />
<br />
<br />
[[Category:PinePhone]]</div>Madezhttps://wiki.pine64.org/index.php?title=PinePhone_APN_Settings&diff=10648PinePhone APN Settings2021-06-07T13:57:35Z<p>Madez: /* Congstar - Telekom Net (Germany) */</p>
<hr />
<div>The [https://en.wikipedia.org/wiki/Access_Point_Name APN] setting is the gateway between your carrier's cellular network and the '''public Internet'''. The APN setting - if not set automatically by the user's OS - has to be set by the user to enable the use of the mobile Internet on the phone.<br />
<br />
= Setting the APN =<br />
<br />
The location of the APN setting depend on the user interface the distribution is using.<br />
<br />
== Distributions with Phosh ==<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (Arch Linux ARM, PureOS, Debian + Phosh) or <code> Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
<!--== Distributions with Plasma Mobile ==<br />
<br />
Todo--><br />
<br />
= List of tested carriers =<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
== 4ka (Slovakia) ==<br />
Name: 4ka Internet<br />
APN: internet<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.4ka.sk/vitajte/navody-a-nastavenia/detail-navodu<br />
<br />
== AT&T-based ==<br />
<br />
=== AT&T (USA) ===<br />
APN: <code>phone</code> or <code>NXTGENPHONE</code> if "phone" does not work (see https://www.att.com/support/article/wireless/KM1218306/).<br />
<br />
=== AT&T Mexico (Mexico) ===<br />
<br />
APN: <code> wap.attmex.mx </code><br />
<br />
=== Cricket (USA) ===<br />
APN: <code>phone</code> or <code>ndo</code> or <code>NXTGENPHONE</code><br />
<br />
== Blau.de (Germany) ==<br />
APN: internet.eplus.de<br />
Username: eplus<br />
Password: gprs<br />
<br />
Source: https://www.my-gps.org/412-apn-einstellungen-deutschland<br />
<br />
== Bouygues Telecom (France) ==<br />
Name: Bouygues Telecom<br />
APN: mmsbouygtel.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.assistance.bouyguestelecom.fr/s/article/parametrage-mobile-email-mms-internet<br />
<br />
== Congstar - Telekom Net (Germany) ==<br />
Name: Telekom Internet<br />
APN: internet.telekom<br />
Username: telekom<br />
Password: telekom<br />
<br />
Other settings seem to work, too. [https://forum.congstar.de/Tarife/Tarif-Produktberatung/46325-Mobil-surfen-mit-congstar-manuelle-Einstellungen-zum-mobilen-Internet-APN/ Congstar mentions]<br />
<br />
Name: Congstar Internet<br />
APN: internet.telekom<br />
Username: congstar<br />
Password: cs<br />
<br />
== Eastlink Wireless (Canada) ==<br />
<br />
Name: Eastlink Internet<br />
APN: wisp.mobi.eastlink.ca<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.apnsettings.org/canada/eastlink-ca/<br />
<br />
== Free (France) ==<br />
<br />
Name: Free<br />
APN: free<br />
Username: free<br />
Password: <empty><br />
<br />
Source: https://mobile.free.fr/assistance/46.html<br />
<br />
== Freedom Mobile (Canada) ==<br />
<br />
Name: 1<br />
APN: internet.freedommobile.ca<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Google Fi (USA) ==<br />
<br />
These are settings that Google provides for their "data-only" SIM cards, but also appears to work fine with the normal SIM card for texting and calling. <br />
<br />
Name: Google Fi<br />
APN: h2g2<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://support.google.com/fi/answer/6330195?hl=en<br />
<br />
== Hofer Telekom (Austria) ==<br />
<br />
Name: HoT Internet<br />
APN: webaut<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.hot.at/config/faqs/HoT_Einstellungen_Endgera_te.pdf<br />
<br />
== kölbi (Costa Rica) ==<br />
Name: Costa Rica:Kolbi:Internet<br />
APN: kolbi3g <br />
Username: <empty><br />
Password: <empty><br />
<br />
Note: alternatively <code>kolbi4g</code> also works as APN.<br />
<br />
== Koodo (Canada) == <br />
<br />
Name: Internet/MMS 2<br />
APN: sp.koodo.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.4gapn.com/ca/en/koodo<br />
<br />
== Lebara (UK) ==<br />
Name: Lebara<br />
APN: uk.lebara.mobi<br />
Username: wap<br />
Password: wap<br />
<br />
These settings work on 4G.<br />
<br />
Ignore Default/asdamobiles.co.uk APN if present.<br />
<br />
== Mineo (Japan) ==<br />
<br />
Tested with S plan (Softbank) and D plan (Docomo). Mobile LTE data currently working only on Phosh-based OSes, because they use Network Manager and Modem Manager. Ubuntu Touch not working yet, see issue #58. https://gitlab.com/ubports/community-ports/pinephone/-/issues/58<br />
<br />
Name: Mineo<br />
APN: mineo-d.jp<br />
Username: mineo@k-opti.com<br />
Password: mineo<br />
<br />
Source: https://support.mineo.jp/manual/network_setup_d.html<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Call their customer service to activate using the number on their website, or activate on their [https://my.mintmobile.com/activation website]. You may also need to reboot your phone.<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
If the first one doesn't work try this one: <br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: autoconfig on ubports<br />
<br />
== Orange Telecom (France) ==<br />
Name: Orange Internet<br />
APN: orange<br />
Username: orange<br />
Password: orange<br />
<br />
Source: https://assistance.orange.fr/mobile-tablette/tous-les-mobiles-et-tablettes/depanner/probleme-avec-un-service-d-orange-internet-sms-mms-mails-cloud-tv/mms/configurer-un-apn-internet-et-mms_192948-738196<br />
<br />
== Penny Mobil (Germany) ==<br />
<br />
APN settings:<br />
<br />
name: Penny Mobil<br />
APN: internet.t-mobile<br />
username: t-mobile<br />
password: tm<br />
<br />
== Public Mobile (Canada) ==<br />
Internet only, mms not tested.<br />
<br />
Name: Public Mobile<br />
APN: sp.mb.com<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://productioncommunity.publicmobile.ca/t5/Phones-Hardware/How-do-I-set-up-data-APN-on-my-smartphone/td-p/3<br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Rogers (Canada) ==<br />
<br />
Name: 4G/LTE Rogers Data<br />
APN: ltemobile.apn<br />
Username: <empty><br />
Password: <empty><br />
<br />
Name: 3G Rogers Data<br />
APN: internet.com<br />
Username: wapuser1<br />
Password: wap<br />
<br />
Source: https://communityforums.rogers.com/t5/Wireless-Knowledge-Base/Rogers-APN-Settings/ta-p/410438, <br />
<br />
== Simyo (Spain) ==<br />
<br />
APN settings:<br />
APN: orangeworld<br />
<br />
Source: https://blog.simyo.es/simyo-configuracion-internet-wap-mms/configura-tu-movil/<br />
<br />
== Sunrise (Switzerland) ==<br />
<br />
Name: Sunrise<br />
APN: internet<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Swisscom (Switzerland) ==<br />
<br />
Name: Swisscom<br />
APN: gprs.swisscom.ch<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Tele2 (Sweden) ==<br />
Name: tele2<br />
APN: 4G.tele2.se<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.tele2.se/support/felsokning-guider/tjanster-installningar/mms-och-data<br />
<br />
== Telekom (Germany) ==<br />
<br />
APN settings:<br />
<br />
Name: Telekom<br />
APN: internet.t-mobile<br />
Username: t-mobile<br />
Password: tm<br />
<br />
Source: https://www.telekom.de/hilfe/mobilfunk-mobiles-internet/mobiles-internet-e-mail/apn-mobilfunk/wie-lauten-die-apn-fuer-mobilfunk?samChecked=true<br />
<br />
== Telenor (Sweden) ==<br />
<br />
Name: Telenor SE<br />
APN: services.telenor.se<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.telenor.se/kundservice/vanliga-fragor/min-mobil-surfplatta/vad-har-telenor-for-apn-installningar/<br />
<br />
== Telia (Finland) ==<br />
Name: internet<br />
APN: internet<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Telstra (Australia) ==<br />
<br />
Name: Telstra Internet/WAP<br />
APN: telstra.iph<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Three (UK) ==<br />
<br />
Name: 3<br />
APN: three.co.uk<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Tracfone (USA) == <br />
<br />
''BYOP SIM Card Kit'' works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit.<br />
<br />
3G/4G data known to work with Verizon & AT&T SIMs (most likely works for T-Mobile as well).<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
Username: <empty><br />
Password: <empty><br />
<br />
To use Verizon's network:<br />
<br />
Name: Tracfone<br />
APN: TRACFONE.VZWENTP<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Verizon Contract (USA) ==<br />
<br />
There are several APN names which can be used, for example:<br />
<br />
Name: 4G LTE Contract<br />
APN: vzwinternet<br />
Username: <empty><br />
Password: <empty><br />
<br />
Other APN names which appear, and may work if the above does not:<br />
<br />
vzwapp<br />
vzwims<br />
<br />
== Videotron (Canada) ==<br />
<br />
Name: Videotron<br />
APN: media.ng<br />
Username: free<br />
Password: <empty><br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username: <empty><br />
Password: <empty><br />
<br />
== Vodafone (Czech Republic) ==<br />
Name: internet<br />
APN: internet<br />
Username: <empty><br />
Password: <empty><br />
<br />
Source: https://www.vodafone.cz/pece/osobni-a-firemni/otazky/zaciname-s-chytrym-telefonem/pripojeni-nastaveni-internetu-v-telefonu/<br />
<br />
== Vodafone (UK) ==<br />
Name: Vodafone<br />
APN: wap.vodafone.co.uk<br />
Username: wap<br />
Password: wap<br />
<br />
These settings work on 4G.<br />
<br />
Ignore Default/asdamobiles.co.uk APN if present.<br />
<br />
= Carriers that do not work =<br />
<br />
== FreedomPop (USA) ==<br />
VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to '''fp.com.attz'''. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
<br />
APN: <code>fp.com.attz</code><br />
<br />
== Sprint (USA) ==<br />
<br />
Sprint is currently not supported due to unknown issues, see also [[PinePhone Carrier Support#Sprint]]. Any input regarding this issue is highly appreciated. <br />
<br />
APN: <code>cinet.spcs</code><br />
<br />
== Visible (USA) ==<br />
<br />
Visible does not have any way to whitelist unsupported phones, it might be possible through APN settings, but requires more research and dev time. Even activating a SIM using a supported phone, and then moving it to the Pinephone does not work.<br />
<br />
== Other ==<br />
<br />
Other VoLTE services.<br />
<br />
= External links =<br />
<br />
* See also https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
<br />
[[Category:PinePhone]]</div>Madezhttps://wiki.pine64.org/index.php?title=PinePhone_Carrier_Support&diff=10647PinePhone Carrier Support2021-06-07T13:35:54Z<p>Madez: /* Europe */</p>
<hr />
<div>{{under construction}}<br />
<br />
{{hint|MMS currently doesn't work in any distribution on the PinePhone without a [[PinePhone_Carrier_Support#MMS_workarounds|script]]! This means images and group chats will not work in text messages.}}<br />
<br />
This page contains hints on setting up cellular network connectivity for specific carriers.<br />
For more general information, see [[PinePhone#Modem_and_carrier_support|Modem and carrier support]]. For the APN settings see [[PinePhone APN Settings]].<br />
<br />
= Check compatibility =<br />
To check if the PinePhone is supported on your carrier:<br />
<br />
Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed in the [https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.pdf modem specification sheet]).<br />
<br />
It is likely that there will be a few frequencies that your carrier uses which are not supported by the PinePhone. Not all of the carrier's frequencies need to be supported by the PinePhone for it to work - as long as ''most'' of them are supported, you will still get good coverage.<br />
<br />
= Tested and working carriers =<br />
<br />
The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):<br />
<br />
== Asia ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021<br />
|-<br />
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021<br />
|-<br />
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021<br />
|}<br />
<br />
== Africa ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Europe ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21<br />
|-<br />
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021<br />
|-<br />
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date 2021-06-07) with Phosh<br />
|-<br />
|}<br />
<br />
== North America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| USA || T-Mobile || Yes || No || Yes || Yes || <br />
* Arch Linux Arm 2020/11/29 <br />
* Mobian - Phosh <br />
* Manjaro - KDE Plasma Mobile<br />
|-<br />
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm (Phosh,SXMO) 2021/04/29 <br />
*Manjaro - Phosh 2021/04/29 <br />
*Mobian - Phosh 2021/3/20<br />
|-<br />
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy || <br />
*Manjaro - Plasma Dev 2020/11/21 <br />
*Ubuntu Touch - 2020/11/26 <br />
*KDE Neon 2020/11/02<br />
|-<br />
| USA || Mint Mobile (T-Mobile) || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/14<br />
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26<br />
*Ubuntu Touch 2021/5/24<br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/1<br />
|-<br />
| USA || Verizon || No || No || No || No ||<br />
*Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes) <br />
|-<br />
| USA || Verizon || Not tested || Not tested || Yes || Not via gui || <br />
*Manjaro - KDE Plasma Mobile 2021/5/10 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Not via gui || <br />
*Manjaro - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*postmarketOS - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Arch - Phosh 2021/5/31 <br />
|-<br />
| Canada || Freedom || Yes || Not tested || Yes || Yes || <br />
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25 <br />
|-<br />
| USA || FaithWireless (AT&T) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 2021/04/29 (version 0.10.1-1, see the [[PinePhone_Carrier_Support#AT.26T|AT&T issues]] below.)<br />
|-<br />
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 0.10.2 2021/05/29<br />
|}<br />
<br />
== South America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Australia / Oceania ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Middle East ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Israel|| Cellcom prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
|-<br />
| Israel|| Golan TC || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Partner prepay || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Pelephone prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Hot prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| 019 prepay|| No || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
= Special carrier notes =<br />
<br />
{{Warning|This section contains providers which do not work or require special settings or actions to work.}}<br />
<br />
Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:<br />
<br />
== USA ==<br />
=== AT&T ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. The PinePhone seems to work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. VoLTE is as yet untested.<br />
<br />
However, it is likely AT&T will drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.<br />
<br />
=== Cricket Wireless ===<br />
Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).<br />
<br />
=== SimpleMobile ===<br />
SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.<br />
<br />
=== Sprint ===<br />
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.<br />
<br />
=== T-Mobile ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).<br />
<br />
T-Mobile's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].<br />
<br />
While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.<br />
<br />
=== Verizon ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.<br />
<br />
Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.<br />
<br />
=== Google Fi ===<br />
Only T-Mobile service works currently, not US Cellular or Sprint.<br />
The APN is h2g2.<br />
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].<br />
<br />
Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps. <br />
<br />
It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.<br />
<br />
= Known issues =<br />
Known issues:<br />
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.<br />
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.<br />
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.<br />
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].<br />
<br />
= MMS workarounds =<br />
These scripts allow partial MMS support on a [[PinePhone]]:<br />
<br />
* JMMS: [https://git.sr.ht/~amindfv/jmms]<br />
* silvermms: [https://gitlab.com/5ilver/silvermms]<br />
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]<br />
<br />
There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.<br />
<br />
= Resources =<br />
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]<br />
<br />
<br />
[[Category:PinePhone]]</div>Madezhttps://wiki.pine64.org/index.php?title=PinePhone_Carrier_Support&diff=10646PinePhone Carrier Support2021-06-07T12:53:46Z<p>Madez: /* Europe */</p>
<hr />
<div>{{under construction}}<br />
<br />
{{hint|MMS currently doesn't work in any distribution on the PinePhone without a [[PinePhone_Carrier_Support#MMS_workarounds|script]]! This means images and group chats will not work in text messages.}}<br />
<br />
This page contains hints on setting up cellular network connectivity for specific carriers.<br />
For more general information, see [[PinePhone#Modem_and_carrier_support|Modem and carrier support]]. For the APN settings see [[PinePhone APN Settings]].<br />
<br />
= Check compatibility =<br />
To check if the PinePhone is supported on your carrier:<br />
<br />
Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed in the [https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.pdf modem specification sheet]).<br />
<br />
It is likely that there will be a few frequencies that your carrier uses which are not supported by the PinePhone. Not all of the carrier's frequencies need to be supported by the PinePhone for it to work - as long as ''most'' of them are supported, you will still get good coverage.<br />
<br />
= Tested and working carriers =<br />
<br />
The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):<br />
<br />
== Asia ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021<br />
|-<br />
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021<br />
|-<br />
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021<br />
|}<br />
<br />
== Africa ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Europe ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21<br />
|-<br />
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021<br />
|-<br />
| Germany || Congstar || Not tested || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date 2021-06-07) with Phosh<br />
|-<br />
|}<br />
<br />
== North America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| USA || T-Mobile || Yes || No || Yes || Yes || <br />
* Arch Linux Arm 2020/11/29 <br />
* Mobian - Phosh <br />
* Manjaro - KDE Plasma Mobile<br />
|-<br />
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm (Phosh,SXMO) 2021/04/29 <br />
*Manjaro - Phosh 2021/04/29 <br />
*Mobian - Phosh 2021/3/20<br />
|-<br />
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy || <br />
*Manjaro - Plasma Dev 2020/11/21 <br />
*Ubuntu Touch - 2020/11/26 <br />
*KDE Neon 2020/11/02<br />
|-<br />
| USA || Mint Mobile (T-Mobile) || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/14<br />
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26<br />
*Ubuntu Touch 2021/5/24<br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/1<br />
|-<br />
| USA || Verizon || No || No || No || No ||<br />
*Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes) <br />
|-<br />
| USA || Verizon || Not tested || Not tested || Yes || Not via gui || <br />
*Manjaro - KDE Plasma Mobile 2021/5/10 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Not via gui || <br />
*Manjaro - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*postmarketOS - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Arch - Phosh 2021/5/31 <br />
|-<br />
| Canada || Freedom || Yes || Not tested || Yes || Yes || <br />
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25 <br />
|-<br />
| USA || FaithWireless (AT&T) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 2021/04/29 (version 0.10.1-1, see the [[PinePhone_Carrier_Support#AT.26T|AT&T issues]] below.)<br />
|-<br />
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 0.10.2 2021/05/29<br />
|}<br />
<br />
== South America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Australia / Oceania ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Middle East ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Israel|| Cellcom prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
|-<br />
| Israel|| Golan TC || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Partner prepay || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Pelephone prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Hot prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| 019 prepay|| No || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
= Special carrier notes =<br />
<br />
{{Warning|This section contains providers which do not work or require special settings or actions to work.}}<br />
<br />
Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:<br />
<br />
== USA ==<br />
=== AT&T ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. The PinePhone seems to work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. VoLTE is as yet untested.<br />
<br />
However, it is likely AT&T will drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.<br />
<br />
=== Cricket Wireless ===<br />
Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).<br />
<br />
=== SimpleMobile ===<br />
SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.<br />
<br />
=== Sprint ===<br />
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.<br />
<br />
=== T-Mobile ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).<br />
<br />
T-Mobile's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].<br />
<br />
While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.<br />
<br />
=== Verizon ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.<br />
<br />
Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.<br />
<br />
=== Google Fi ===<br />
Only T-Mobile service works currently, not US Cellular or Sprint.<br />
The APN is h2g2.<br />
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].<br />
<br />
Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps. <br />
<br />
It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.<br />
<br />
= Known issues =<br />
Known issues:<br />
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.<br />
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.<br />
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.<br />
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].<br />
<br />
= MMS workarounds =<br />
These scripts allow partial MMS support on a [[PinePhone]]:<br />
<br />
* JMMS: [https://git.sr.ht/~amindfv/jmms]<br />
* silvermms: [https://gitlab.com/5ilver/silvermms]<br />
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]<br />
<br />
There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.<br />
<br />
= Resources =<br />
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]<br />
<br />
<br />
[[Category:PinePhone]]</div>Madezhttps://wiki.pine64.org/index.php?title=PinePhone_FAQ&diff=10645PinePhone FAQ2021-06-07T12:29:29Z<p>Madez: /* Other */</p>
<hr />
<div>A list of frequently asked question.<br />
<br />
== Hardware ==<br />
<br />
=== Revisions ===<br />
==== What are Community Editions? ====<br />
Community Editions of the PinePhone were versions of the PinePhone which came preinstalled with the operating system of a partner project and featured the logo of the project on the back panel. The Community Edition was intended to help partner projects developing these systems: "Community editions are meant to bring exposure to partner-projects operating systems and communities, as well as help finance ongoing development.", [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ source].<br />
<br />
==== Is the Community Edition hardware the latest revision? ====<br />
The Community Edition program (featuring the mainboard numbers 1.2 through 1.2b and branded back covers) which provided the branded PinePhones has since ended, and a Beta Edition has since been released. The only difference between each Community Edition is the inclusion of crucial bug fixes, with the last issue being fixed with the 1.2b motherboard shipping with the Manjaro CE PinePhones. The 1.2b motherboard is also currently used in the Beta Edition PinePhones, however the Beta Edition units do not ship with any back cover branding. There are currently no plans for further hardware revisions.<br />
<br />
Aside from the back cover, the only other difference between each Community Edition is that starting with the postmarketOS PinePhone, a convergence package option was released that adds another gigabyte of ram to the phone and a 32GB eMMC instead of a 16GB eMMC. Convergence packages also included a dock for plugging in USB peripherals and connecting to an HDMI monitor, however you can purchase a generic USB-C dock to use with a 2GB PinePhone. <br />
<br />
The predecessor to the Convergence Edition PinePhones was the Braveheart Edition intended for developers to bring up the platform, which had the version number 1.1. For more details about the topic see [[PinePhone#Hardware Revisions]].<br />
<br />
==== Will there be other Community Editions? ====<br />
Five Community Editions have been announced: [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ UBports], [https://www.pine64.org/2020/06/15/june-update-postmarketos-ce-pinephone-shipping-pine64-cluster/ postmarketOS], [https://www.pine64.org/2020/08/31/pinephone-manjaro-community-edition/ Manjaro], [https://www.pine64.org/2020/12/01/kde-community-edition-is-now-available/ KDE], and [https://www.pine64.org/2021/01/17/mobian-community-edition/ Mobian]. Since the release of the Mobian edition, the Beta Edition PinePhones have been released and the Community Edition Program has ended.<br />
<br />
==== In simple terms, what are the differences between Braveheart and the new Community Edition? ====<br />
The Braveheart PinePhone was the first public revision of the PinePhone which was intended solely for developers and Linux enthusiasts. The UBports Community Edition was the next revision of the PinePhone with an updated mainboard based on feedback from the Braveheart Edition, see [[PinePhone#Hardware Revisions]]. All current revisions of the PinePhone continue to be intended for developers and enthusiasts, however, PINE64 will be starting to offer partnered retail units of the PinePhone which will have a better warranty and technical support (keep in mind even then it is not intended for a broader audience at this time, as the software still needs work and the hardware does not hold up well to modern consumer standards).<br />
<br />
==== Will there be a newer revision after the Community Editions? ====<br />
Starting with the UBports Community Edition the PinePhone has gotten CE and FCC certifications, repeating the certification process due to changes in the hardware design is very expensive, so the 1.2b motherboard is viewed as the final revision. The PinePhone (and parts for them) will be produced and sold for at least 5 years.<br />
<br />
==== Will there be hardware differences between the Community Editions? ====<br />
<br />
Besides the varied back covers, starting with the launch of the PostmarketOS CE there has been the release of a convergence package option for the PinePhone which includes more ram and storage, and an included dock for convenience. There has also been multiple hardware changes starting with the UBports CE (mainboard 1.2) and ending with the Manjaro CE (mainboard revision 1.2b). There are currently no plans for future hardware changes for a few years.<br />
<br />
==== How powerful is the PinePhone's hardware? ====<br />
<br />
The PinePhone is about on par with a Raspberry Pi 3 in terms of CPU power, however going by GFLOPS it has half the GPU power. The Pi 3's Videocore IV does 24 GFLOPS, and the Mali 400 MP2 on the PinePhone only 10.8.<br />
<br />
Despite this, using software rendering the PinePhone is capable of smoothly rendering at 1080p resolution or higher. However, with a fully GPU-accelerated mobile environment you should expect a more sluggish experience outputting to such resolutions. Unfortunately, the Mali 400 MP2 (a 2008 arm mobile GPU) simply isn't intended to push 1080p resolution. With that said, the VPU of the PinePhone has been shown to handle smooth H.264 1440p30 video playback using Cedrus and gstreamer as documented [https://xnux.eu/log/#001 here]. Further, the PinePhone should be more than capable of a smooth phone experience when used in conjunction with well optimized software that makes use of its hardware features. It is also more than capable of running many light games (including 3D ones such as SuperTuxKart), and retro gaming. Expect further speed improvements over time as the drivers are improved, and in the meanwhile you can look into slightly [[overclocking]] the device (at your own risk).<br />
<br />
=== Sound ===<br />
<br />
The default ringtone for Mobian Phosh can be found at /usr/share/sounds/freedesktop/stereo/phone-incoming-call.oga<br />
<br />
=== Modem ===<br />
<br />
==== The modem isn't working ====<br />
<br />
In order to use the modem and Wi-Fi/Bluetooth, you need to ensure the battery is inside the device and has a sufficient charge. Even when supplying the phone with enough power, the modem and Wi-Fi chip will not work without a connected battery. Further, double check that you have not put the SD card into the sim card slot, or vice versa.<br />
<br />
==== Does the PinePhone only wake up from sleep for calls and texts? ====<br />
<br />
Yes. Unless the PinePhone is configured to wake up every few minutes from deep sleep in crust (At the cost of battery life. However, in the future there may be other solutions), then there is not any way to get any notifications for applications. The modem on the PinePhone will wake the device for incoming calls and texts however, and the real-time clock is also capable of waking the device for alarms.<br />
<br />
=== Battery ===<br />
<br />
==== The battery is stuck inside the phone ====<br />
<br />
The battery can be stuck in the phone if the screws of the frame are overtightened.<br />
<br />
If your battery is stuck inside the PinePhone, grab a screwdriver and completely unscrew all the screws of the midframe. Then pull out the battery (you may have to fully take off the midframe in some cases to get it out). And then rescrew the midframe, but only tighten the screws to the point where they are just barely tight to hold. This should allow you to remove the battery easily.<br />
<br />
==== The battery is discharging while the phone is powered off (Braveheart Edition) ====<br />
<br />
The issue is not present on the Community Edition. Due to a hardware bug, after power off, the phone still consumes 20–30mA which drains the battery in 3-4 days. A manual procedure to fix the hardware bug is described [https://xnux.eu/devices/pp-pmic-fix.jpg here].<br />
<br />
==== The battery only charges to ~84% ====<br />
<br />
Some pre-made OSes using megi's kernel limit the maximum amount of charge to roughly ~84% in the hope of prolonging the battery life, as repeatedly reaching the upper level of battery charge reduces the battery's lifetime (this is <b>not</b> a safety feature!). The same effect however also applies when repeatedly draining the battery to a low level - users are therefore advised to consider if that setting is reasonable depending on their usage. The setting can be overwritten via Sysfs, to let the battery fully charge (this can lower the replaceable's battery lifetime considerably depending on the charging behavior!):<br />
<br />
{{warning|The following instructions are directed towards expert-level users and developers!}}<br />
<br />
<code>echo 4350000 > /sys/class/power_supply/axp20x-battery/voltage_max_design</code><br />
<br />
=== Kill Switches ===<br />
==== What are the kill switches doing? ====<br />
<br />
{| class="wikitable"<br />
|-<br />
! Number<br />
! Name<br />
! Explanation<br />
! Description<br />
|-<br />
| 1<br />
| Modem<br />
| Pulls Q1501 gate up (FET killing modem power)<br />
| "On" enables cellular communication and GNSS hardware, "off" disables it.<br />
|-<br />
| 2<br />
| Wi-Fi / Bluetooth<br />
| Pulls up CHIP_EN<br />
| "On" enables Wi-Fi and Bluetooth communication hardware, "off" disables it.<br />
|-<br />
| 3<br />
| Microphone<br />
| Breaks microphone bias voltage from the SoC<br />
| "On" enables audio input from on-board microphones (not 3.5mm jack), "off" disables it.<br />
|-<br />
| 4<br />
| Rear camera<br />
| Pulls up PWDN on OV5640 <br />
| "On" enables the rear camera, "off" disables it.<br />
|-<br />
| 5<br />
| Front camera<br />
| Pulls up PWDN on GC2145<br />
| "On" enables the front camera, "off" disables it.<br />
|-<br />
| 6<br />
| Headphone<br />
| Pulls up IN2 on analog switch BCT4717ETB<br />
| "On" enables audio input and output via the 3.5mm audio jack, "off" switches the jack to hardware UART mode.<br />
|}<br />
<br />
=== Memory ===<br />
<br />
==== What's the speed difference between the eMMC and SD cards? ====<br />
Maximum transfer speed of the eMMC is around 85 MB/s, while SD cards are limited to approximately 23 MB/s (even with faster cards).<br />
<br />
=== GPS ===<br />
<br />
==== GPS doesn't work ====<br />
<br />
Like almost all smartphones, the PinePhone GPS antenna is small and can only get a first fix unassisted if the GPS signal is very strong. To make first fix faster and more reliable, phones download assistance data either from the phone network or from the internet. The GPS in the PinePhone modem supports the internet based assistance method, as detailed in the modem documentation, but this is currently only supported by a few distributions, and a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] that shows it can work.<br />
<br />
Until aGPS support becomes standard you'll have to make some manual changes - see for example [https://wiki.mobian-project.org/doku.php?id=location Mobian wiki]<br />
<br />
==== GPS can't determine direction ====<br />
<br />
Currently, due to the magnetometer not being hooked up in software at this time, it is not possible for GPS software to use the phone's compass functionality. This means while you are walking it will not be possible to determine the direction of travel. This is not as much of an issue for vehicles as the faster speeds mean that it is possible to estimate the direction of travel, however it will still be an issue should the vehicle travel through a tunnel and loose GPS signal.<br />
<br />
== Software ==<br />
<br />
=== Installation ===<br />
<br />
==== How can I install an operating system on the SD card / eMMC? ====<br />
<br />
See [[PinePhone Installation Instructions]].<br />
<br />
=== Updating ===<br />
<br />
Read the [[PinePhone Updating Instructions]].<br />
<br />
=== Booting ===<br />
<br />
==== What's the boot order for SD cards and eMMC? ====<br />
<br />
The PinePhone will automatically boot from microSD if a bootable card is inserted. If no (bootable) microSD is found, it will boot from eMMC.<br />
<br />
==== How can I select different OSes at boot? ====<br />
<br />
There was a project by Danct12 which allowed the user to select different OSes at boot, but the repository has since been archived: https://github.com/dreemurrs-embedded/Pineloader.<br />
<br />
==== I turned on my Manjaro CE PinePhone. The red LED and screen backlight are briefly lit, then both are not and it will not boot. ====<br />
<br />
This can be the result of at least one situation:<br />
<br />
# The eMMC installation became corrupt or otherwise unbootable<br />
# An SD card is present but not bootable (consider [[PinePhone#Detailed usage instructions]])<br />
<br />
If there is an installation of Manjaro on both the eMMC & an SD card, the SD card will always boot first on the device. Try taking the SD card out and booting the installation that is on the eMMC. If the problem persists, it is likely there is an issue with both installations and you will need to reinstall your distribution. You may also want to check with your distribution's maintainers if boot issues are a common problem in a recent update.<br />
<br />
==== I did not install an update in Ubuntu Touch and I'm stuck on the PINE64 logo after rebooting. ====<br />
<br />
# Use a USB A-C cable to plug your phone into your PC<br />
# Hold the PinePhone's power button for 4 seconds or more to power it off.<br />
# Wait 5 seconds<br />
# Hold the Volume Up and Power buttons on the PinePhone to boot into recovery. You should see the LED light red, then yellow, then green. The "Installing update" screen will appear, but a progress bar to indicate update progress will not. Ignore the "Installing update" part.<br />
# Your PC may automatically mount the PinePhone's partitions. If it does, Safely Remove or Eject all of them.<br />
# Open a terminal on your PC. Type <code>telnet 172.16.42.1</code><br />
# You should receive the text 'Welcome to Rescue SD Shell!'<br />
# In the new Rescue SD shell, type <code>umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync</code><br />
# Once this command pipeline finishes, type <code>sync && reboot -f</code><br />
<br />
Your PinePhone should reboot into Ubuntu Touch. Now head to Settings -> Updates and install the new update! <br />
<br />
If these steps did not solve your issue, please create a new thread here on the PINE64 forums, note what the problem looks like, then say that you've tried these steps already.<br />
<br />
This is caused by corruption on the userdata partition. Normally this should be fixed by 'e2fsck' in the initramfs, however, an error in image creation means that that version of e2fsck is unable to correct the corruption. This has been fixed in all new PinePhone updates, so if you update from the factory image to any other image available to the PinePhone now, you will not experience this issue any longer.<br />
<br />
==== I turned on my PinePhone running Ubuntu Touch. The red LED is lit and it will not boot. ====<br />
# Hold the power button until the light turns off<br />
# Hold the power button until the light turns on<br />
<br />
You may need to repeat these steps more than once.<br />
<br />
This is caused by u-boot apparently trying to use the eMMC before it is ready. We are not entirely sure why this occurs yet.<br />
<br />
==== Can I install a different OS on my Community Edition? ====<br />
<br />
Yes! While all the Community Edition PinePhones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see [[PinePhone Installation Instructions]] and [[PinePhone Software Releases]] on how to install them.<br />
<br />
=== Other ===<br />
<br />
==== How can I enable SSH? ====<br />
<br />
In Ubuntu Touch you can run "sudo start ssh" to get a one-time start, or edit /etc/init/ssh.override and remove the manual line to make it auto-start.<br />
<br />
In other distributions you may have to install SSH through its package manager and then proceed to use its init system to enable it. For Manjaro, Arch, and Mobian you can use "systemctl enable" and "systemctl start" command to enable and start ssh.<br />
<br />
==== What works, what doesn't? ====<br />
<br />
For Ubuntu Touch see https://gitlab.com/ubports/community-ports/pinephone#what-works-what-doesnt.<br />
<br />
Other distributions will have different levels of functionality. Please refer to the release page of your chosen distribution for further information.<br />
<br />
==== I can't connect to a 2.4Ghz Wi-Fi network in Ubuntu Touch. ====<br />
<br />
Reboot your device by holding the power button until the "Power" dialog appears, then pressing "Restart".<br />
<br />
If that does not fix the issue, note that all the following conditions must be met to use Wi-Fi on the PinePhone:<br />
<br />
# The plastic tab between the battery and the device's battery contacts has been removed<br />
# The battery is installed<br />
# The Wi-Fi killswitch, #2, on the rear of the device is switched "ON"<br />
<br />
Wi-Fi in the PinePhone only seems stable after a warm reboot like this.<br />
<br />
==== What's the status of Android for the PinePhone? ====<br />
<br />
Currently, there isn't any major push to get Android running well on the PinePhone. The developer Icenowy did get a Android image to run and partly work, it was however slow and buggy, with major functions not working. A solution for running some of your android apps may be found in Anbox as of now. Anbox is currently not included in Ubuntu Touch. In other distributions your millage may vary on what applications will run and how well.<br />
<br />
==== Why are my apps loading slower than on my Android phone? ====<br />
<br />
Android has multiple techniques in place to speed up launching applications after the first launch, such as the "Dalvik cache".<br />
<br />
Using an alternative filesystem such as F2FS on the eMMC (which is considerably faster than running software on the SD card) may help improve performance slightly. Over time you can expect further optimizations and improvements in various distributions that will help speed up the PinePhone.<br />
<br />
==== How can I turn on the backlight? ====<br />
<br />
When the phone boots but the backlight is off, the display is still faintly readable under a bright light. The backlight can be enabled by increasing its brightness. On most systems the brightness level is an integer between 0 and 1000 and available at runtime in /sys/class/backlight/backlight/brightness and stored at shutdown and loaded at boot from /var/lib/systemd/backlight/platform-backlight:backlight:backlight by systemd-backlight. Changing the brightness can be done at runtime, for example over SSH, by executing as root <code>echo 500 > /sys/class/backlight/backlight/brightness</code>. The stored brightness can be modified using another system, by mounting at $mnt the root filesystem of the system you want to increase the brightness of and executing <code>echo 500 > $mnt/var/lib/systemd/backlight/platform-backlight\:backlight\:backlight</code>.<br />
<br />
=== SMS ===<br />
<br />
==== The phone does not receive SMS ====<br />
<br />
Sometimes incoming SMS messages are not being received, but outgoing ones, phone calls and data are working fine. One potential cause could be SMS messages that linger in the modem's queue (10 or more of them). This queue appears to be persistent across reboots and also re-imaging the OS.<br />
<br />
On Mobian and Manjaro, the ModemManager does all the communications with the 3G modem including phone calls, cellular data, GPS and SMS. This may not be the case with other PinePhone OSes.<br />
<br />
You can access the ModemManager using the mmcli command.<br />
<br />
'''Mobian:'''<br />
<br />
<pre>$ sudo mmcli -m 0 --messaging-list-sms<br />
Found 10 SMS messages:<br />
/org/freedesktop/ModemManager1/SMS/0 (received)</pre><br />
<br />
'''Manjaro:'''<br />
<br />
<pre>$ sudo mmcli -m 3 --messaging-list-sms<br />
/org/freedesktop/ModemManager1/SMS/77 (received)</pre><br />
<br />
For Mobian, delete all the messages like this:<br />
<br />
<code>$ sudo mmcli -m 0 --messaging-delete-sms=1</code> (Repeat with 1 through 10 to delete all the messages)<br />
<br />
For Manjaro, delete all the messages like this:<br />
<br />
<code>$ sudo mmcli -m 3 --messaging-delete-sms=77</code> (Repeat with all listed messages)<br />
<br />
Note that the "-m 0" or "-m 3" refers to modem 0 or 3 (the only one in a PinePhone). For more help on the messaging related actions available in mmcli you can check the help with <code>mmcli --help-messaging.</code> This article is also helpful in learning: https://electronproton.com/mmcli-command-examples/. For your particular configuration, you may need to try different "-m #" combinations, e.g., "-m 2" or "-m 4." "-m 0" is not always the default.<br />
<br />
It should also be noted that recent releases of Mobian and postmarketOS now include a userspace daemon called [https://gitlab.com/mobian1/devices/eg25-manager eg25-manager], which helps manage the modem and ensure proper operation.<br />
<br />
== Shipping ==<br />
=== I did not receive an order confirmation ===<br />
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get an order confirmation email.<br />
<br />
=== When does the phone ship? ===<br />
For up-to-date information when the phone's shipping date is estimated, see the edits in the corresponding forum thread.<br />
<br />
=== It is shipping day but I did not receive a shipping notification ===<br />
For shipments with DHL the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.<br />
<br />
=== When does my phone ship if I order now? ===<br />
Orders made after Friday, 22nd May 2020 are shipped after the first bulk of pre-orders has been shipped. The exact date is not known yet due to various reasons, it may be a few weeks after the first bulk shipped. [https://forum.pine64.org/showthread.php?tid=9942 The forum] will be edited with updated information and you will receive a shipping notification when the device was shipped.<br />
<br />
=== What about import taxes? ===<br />
Import taxes have to be paid by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.<br />
<br />
== Accessories ==<br />
<br />
=== Protection ===<br />
==== Which screen protector should I use? ====<br />
<br />
Protecting your screen is important, especially for devices like the PinePhone that doesn't have access to the newest glass technology.<br />
The Braveheart and Community Editions of the PinePhone comes with a plastic film screen protector installed, and PINE64 sells a tempered glass screen protector [https://pine64.com/product/pinephone-tempered-glass-screen-protector/ in their store].<br />
<br />
You can also buy a third-party screen protector, as the screen protectors for the iPhone 11 Pro Max/XS Max fit the PinePhone pretty well based on [https://forum.pine64.org/showthread.php?tid=8458&pid=65409#pid65409 this] forum post.<br />
<br />
=== Batteries ===<br />
==== I want a replacement battery, which one should I buy? ====<br />
<br />
Replacement batteries for US customers are available in the store.<br />
<br />
Currently the PinePhone battery is known to be compatible with replacement batteries for the Samsung J700. Specifically, models "EB-BJ700BBC" and "EB-BJ700BBE" are compatible with all PinePhone models, and "EB-BJ700CBE" is compatible with Community Editions [https://www.reddit.com/r/PINE64official/comments/kcof97/pinephone_replacement_battery_found_and_tested/gfrx4p2/?utm_source=reddit&utm_medium=web2x&context=3 after UBPorts] (due to plastic tabs on its bottom which only the newer phones [https://forum.pine64.org/showthread.php?tid=11901 have tolerance for]).<br />
<br />
=== External hardware ===<br />
<br />
==== Will PINE64 sell other add-ons made for the PinePhone? ====<br />
<br />
Yes, currently there is a keyboard case [https://forum.pine64.org/showthread.php?tid=8537&pid=55396#pid55396 with similarities to the Psion 5] which includes an internal battery, and a [https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/ Qi wireless charging] add-on planned, both of which PINE64 intends to directly sell. There is the potential for future add-ons such as a game pad, however that is currently just an idea and not in any way planned.<br />
<br />
==== Which 3rd party hardware can connect to my PinePhone? ====<br />
<br />
See [[PinePhone Hardware Accessory Compatibility]].<br />
<br />
<br />
[[Category:PinePhone]]</div>Madez