About the device: PinePhone:
Perhaps youâre in a line of work where security is a must, or a hard-core Linux enthusiast, or perhaps youâve just got enough of Android and iOS and youâre ready for something else â the PinePhone may be the next Phone for you. Powered by the same Quad-Core ARM Cortex A53 64-Bit SOC used in our popular PINE A64 Single Board Computer, the PinePhone runs mainline Linux as well as anything else youâll get it to run.
The purpose of the PinePhone isnât only to deliver a functioning Linux phone to end-users, but also to actively create a market for such a device, as well as to support existing and well established Linux-on-Phone projects. All major Linux Phone-oriented projects, as well as other FOSS OSâ, are represented on the PinePhone and developers work together on our platform to bring support this this community driven device.
PinePhone Pro:
The Pinephone Pro is all you love about the PinePhone, except with better specifications. It has a 6-Core RK3399S SoC and 4 GB RAM, which is a huge upgrade compared to the regular Pinephones Allwinner A64 and 2/3 GB of RAM.
More information can be found on the Pine64 PinePhone Pro page.
How to install:
Download the image/xz file from the download location. Verify that the download completed successfully.
After that, install Etcher (sudo pacman -S etcher if on Manjaro) and burn the to an SD card (8 GB or larger).
The PinePhone (Pro) should recognize the SD card as a bootable device and boot from it.
Thanks Strit,
i took this opportunity to reflash my pinephone to rid myself of self inflicted screen scaling issues.
I had some wayland errors on first boot but after that everything was ok.
I had to use the git link as Manjaro Downloads still points at beta13.
I am curious about the issue with the modem being disabled on boot not being listed as known. This is a rather serious and quite long-standing (over a year now I think) issue.
Or was this fixed with a re-flash? I am still running the Beta Edition image with simply all updates applied.
Strange. I have to enabled it after every boot. Sometimes I have to reboot it several times and do that until it actually works. Even though it shows âenabledâ it might not be working. After I got it working it will keep working until I have to reboot (which is basically daily because of the issue with the lock screen no longer taking input). In earlier builds (several months ago) after enabling the modem I had to enter my SIM again.
This only started like a year ago. It was working fine with the initial Beta Edition and only showed up after I had the phone for quite a while.
On every reboot I am asked to enter my SIM but that only unlocks the modem and does not enable it.
I was not the only one to have this issue. I got more context about this, as well as the command to enable the modem, with from other users. But I canât find the post anymore. Maybe I am remembering wrong and just read the post and did not participate.
Status | lock: sim-pin
| unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: locked
| power state: on
The modem is not available for a very brief time after you entered your PIN: error: couldn't find modem.
When it works again and you get:
Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: disabled
| power state: on
After running sudo mmcli -m any -e:
Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: registered
| power state: on
| access tech: lte
| signal quality: 62% (recent)
In this state it is working (i.e. able to receive texts).
I am curious about the sim-pin2 lock. What is that?
I will try to fetch the state the next time it not working even though it is enabled.
Is there any other log I could potentially get some info for this?
The modem is also disabled and not re-enabled when the system was suspended (I accidentally left off the power cable so the system went low on battery).
It is a missing feature of the mobile powersaving KCM (kde configuration module / System Settings module). You can bring up the desktop dialog with kcmshell5 powerdevilprofilesconfig, and there you can set less aggressive power management when on AC power (well, what it thinks is AC â any USB power source will be considered âon ACâ, even a power bank, which is IMHO a feature).
Note that there is no way to suspend the CPU without suspending WiFi, so if you need the WiFi to stay up, you need to disable suspending altogether when plugged to AC (which is how I have set up my PinePhone).
I have discovered that when I wish down the menu there ist a âCaffeineâ button. When I push this button then I I can do the maintenance window with ansible etc
maybe some of you know who this can be done on a cli way?
latest plasma mobile does not update due to various dependendy problem. After installing RC 3 I followed this link Pinephone doesn't boot after latest upgrade - #2 by Darksky and the phone worked since (without DAV syncing). But the recent update is not installing here.
Hey Strit, Iâm new to the forums but I have been working with Pinephone beta edition for some time now. I am excited about the device and the grass roots wish list built into the product. What Iâm wondering about right now tho; where is the Beta 16 thread at? We need to be reporting and talking on that.
Beta 16 for Plasma Mobile is the best performing release for Pinephone so far in my experience. I tested on SD and worked so well, I subsequently flashed to eMMC and itâs even better. This is totally subjective but it seems even more stable on eMMC.
The only drawback I have seen is suspension. When the phone goes into suspend, there seem to be various problems, however this has been less of a problem while flashed to eMMC. Remediation of the issue can be done by activating âcaffeineâ. I have left the phone on all day, screen went blank, hit power button, and it came back with no problem.
On doing hdmi display testing I noticed that there was no sound. After some command line probing, I saw that there was a very good reason for this. âNote Device 4â below in output of âinxi -b --usbâ:
So basically, we have visual function to hdmi but no hdmi audio driver to push sound. Some suggestions to remediate this would be welcome; such as, do we have a âsun9i-a80-hdmi-audioâ hardware driver?
Bear in mind that Strit has not created a plasma mobile forum entry for Beta 16 yet, so as of right now (1/14/24) we cannot report to a Beta 16 forum except for individual entries.
Kevin, I want to thank you because although you donât know it you have already helped me out two times before in the last 2 days. One was on kwallet deactivation, another was on powerdevilprofilesconfig to avoid suspension, and now an hdmi driver for pinephone. Thank you three times and I owe you.
Sorry, I forgot to mention help with wifi; âkcmshell5 networkmanagementâ to fix getting around Pam integration and keep wifi password stored. Thatâs four; so thanks four times and I owe you.
