After fully upgrading my new Pro with "sudo pacman -Syyu --noconfirm", I installed openssh and attempted to make "sudo" not ask for password. Now, after changing Plasma style, restarting and unlocking the screen, all I see is this:

       

The icon is "Settings" which I put on the home screen. The screen reacts to device rotation, but otherwise does not react to anything. The "Settings" icon does not react either.

Good news is that ssh works — I can ssh to the phone and control it (change screen brightness for example).

Any ideas how to bring the UI back please?

UPDATE: After power off and power on again, the issue has gone. But what was it? How to prevent it?

I have added this line to the sudoers config:

Hey all,

     I have been using my PinePhone quite consistently now for months now and have been enjoying the experience.  I had to run out and buy a cheap flip phone though out of necessity because it seems my modem may have died.

I have tried resetting the device, even letting it sit off for a while, and messing with the physical switches, but to no avail.  The cellular icon is grayed out and has a slash through it, and the mobile options have completely disappeared from settings.

Has anyone had this issue, and is there a fix, or do I need a new mobo?

grimlok

Just received my first Pro, switched off the modem, mic and both cameras, plugged in charger, connected WiFi and attempted to update/upgrade the soft:

   

Rebooted, tried again — same thing.

Note that the updates' size appears zero. Weird.

How to debug it? Can I try the same via CLI to see some details? Isn't this a common/known issue with new Pros?

The address bar and tabs in Firefox (mobian) are at the bottom. I find this disagreeable. Is there any way to move them back to the top?

The PPP wiki describes the permanent and a temporary boot sequence.  I find the wiki to conflict itself.  I think many users are showing confusion and posting numerous threads because they don't understand what is being told to them.  There is also another batch of new user coming. Toward that end, I have extracted the Boot Sequence discussion from the wiki.  I have posted my comments (in red) next to each line.  Hopefully this can get to the root of alot of confusion if someone can provide the mods.  If I have made bad interpretations, I'd like to know.

Boot Order:
On the PinePhone Pro the eMMC (the internal storage of the phone) has a higher boot priority than the microSD card (see boot sequence details for details regarding the boot sequence). That behavior is in contrast to the original PinePhone with the Allwinner A64 SoC, where the microSD card has a higher boot priority. (OK)

The Explorer Edition comes with a modified U-Boot pointing to the microSD card pre-installed to the eMMC. (OK, but no reason why)
The microSD card can be (temporarily) booted instead of the pre-installed operating system, when the power key is shortly held at boot. (Says temporary sd boot)
To always boot from the microSD card it is recommended to wipe U-Boot from the eMMC.(This conflicts with 1st line above.  Removing the temporary UBoot would make it go back to eMMC, it looks to me.  Also, does not say specifically what file to remove.
When the pre-installed bootloader was overwritten with a bootloader without such a configuration, the RE button underneath the back cover of the phone can also be used to temporarily bypass the eMMC. (what does "was" mean?  What configuration, does this mean a configuration with the temporary UBoot removed? I think this says the RE button can also make device boot from SD.  Does not say how to apply RE; one press-then power on, hold down, hold down and press power on?)
The button may however only be pressed shortly for a few seconds during boot, otherwise the eMMC won't be initialized in the operating system.  ( This seems to conflict with previous statement and says hold RE for a few seconds makes boot to eMMC.  Previous statement said it would bypass eMMC and boot to sd.)

Also, further down in wiki, in a yellow box. 

Due to the specific boot order it is currently strongly recommended to boot from the microSD card only. Please ask in the community chat if you have any questions regarding the installation  (no reason given as to why to boot from SD and not the eMMC that any phone should run from.  Also does not say this is a temporary thing.)

Thanks for reading this and also for any clarifications.      tom kosvic

Throughout these threads there are a myriad of hardware button, RE button combinations suggested to accomplish specific things.  At times these seem to be conflicting with other suggested combinations.  I am talking about; power on key, volume up-down, RE button, connect to charger,  or connect to computer.   Some instructions say, for example,  hold RE; plug in USB, OR hold power on: hold volume down, etc.  

Would someone knowledgeable either point me (all of us) to a list of these key combinations or create a list?  Need the key combination and what is the purpose.  Also any special instructions such as: "Hold RE for 5 seconds after release of power on key".

Thanks,       tom kosvic

After about two days of use with a new SIM my ability to send and receive voice telephone calls stopped working.
I can still send and receive SMSs.
This is a Pinephone 3/32 running Linux mobian 5.15-sunxi64 #1 SMP Tue Feb 15 08:08:10 UTC 2022 aarch64 GNU/Linux
I am assuming there is probably a file that got loaded with junk but a restart, even running updates has not re-enabled phone calls.
I cannot
-dial number from dialpad screen
-dial numbaers from call log
-receive/answer calls and no incoming/missed calls appear in call log

GPS works, SMS works

I have never gotten my 3g/4g data to ever connect.
I have been using this installation to follow Mobian for several months with another SIM installed and rarely made and received successful telephone calls; but first began using Pinephone as my primary two days ago and the error occurred after 3-4 hours of use where the calls were received and rang the ringtone both when awake and in sleep/standby mode..

Sorry if there is an obvious answer to this eg. no.

I am at manjaro-arm-installer but that does not seem to be for Pinephone.

So... I know for live images eg. Ubuntu via USB there's a nice little button like "install to hard drive".

I think I've read in a few places you're not supposed to flash eMMC from SD card. However it seems there's no JumpDrive yet. I have not looked too much into Tow boot if it's applicable...

Am I supposed to while booted in SD card wipe the eMMC and setup a partition ext4 boot and all that/write the Pinephone Pro Beta 11 image onto eMMC directly?

Just confirm before I brick this device that I just received today.

edit: My main goal is starting the OS from scratch, if there was a factory reset option I would use that (doesn't really make sense, tin foil hat I know).

Received my "PINEPHONE - Beta Edition with Convergence Package Linux SmartPhone" today. Lucky me  (or not?)

Vanilla manjaro shown T-Mobile with my SIM card, as expected, because I took it from my old phone and many people report that this trick works just fine, for example here. Unfortunately OS was so glitchy, that I didn't try to make a call and updated it as soon is it got some battery charge. Had no issues with update and newer version looks better:

uname says plasma-mobile 5.16.11.1-manjaro-arm
plasmashell --version says 5.24.2
cat /etc/lsb-release says manjaro 22.01 (funny, but I don't see it here)

All privacy pins are in upper position, ON.

At this point, if I go to Settings > Cellular Networks > SIM Cards, I do see my SIM 0, and it show IMEI, T-Mobile. Modem details detects my phone number and says enabled: true, state: disabled, registration state: unknown registration status, firmware version is missing - that i don't understand and it looks confusing. next it says interface cdc-wdm0 and then detailed info looks good.
for some reason folder "/var/lib/ofono/" contains two folders with my IMEI (second one has "-3" suffix) that is strange.
Also running something like "ofonoctl list" gives an error "could not aquire org.ofono.Manager on dbus"... with a typo in "acquire"...

Finally if I do a call at plasma-dialer (the "Phone" app) it instantly slides "Dialer" screen (or tab whatever) to an "Active call list" screen, that is blank. If I repeat that several times quickly - sometimes I see that something blinks, like it's trying to call, but that disappears immediately. Tried with and without data on. 

T-Mobile requires VoLTE, so I checked that: