@johndoe said in Upgrading Pinephone from 20.04 to 24.04:
@newguy I think it is very likely, that you break the system that way, because Ubuntu Touch is not meant to be updated with apt.
The PinePhone port is, you can't update it using the normal System Settings approach.
Hello everyone!
I have a PinePhone (original, not Pro) which is currently running Ubuntu Touch 20.04. I'd like to upgrade the device to run Ubuntu Touch 24.04.
As far as I can tell, 24.04 does not officially support the PinePhone and does not offer an official upgrade path.
With that said, I'm familiar with upgrading Debian and Ubuntu machines manually from one version to the next using APT. Has anyone tried something similar with the PinePhone?
I suspect doing a manual upgrade will work, at least to get the proper upgraded packages in place. However, I'm concerned this method might result in me trying to boot an incompatible kernel.
@Keneda You linked to build images for 20.04, which I said I already have. I'm looking for a way to upgrade my PinePhone to version 24.04.
@Lakotaubp I feel like no one has actually read the question.
I already have 20.04 Focal installed on my PinePhone and its packages are up to date for the 20.04 branch. This is not an issue, it's been running for a couple of years and getting security updates for the 20.04 branch.
What I am asking is if it is possible to to an in-place upgrade from 20.04 to 24.04 using the command line APT tools. I want to upgrade from Focal to Noble, but there are not any Noble images built for the PinePhone.
@johndoe said in Upgrading Pinephone from 20.04 to 24.04:
@newguy I think it is very likely, that you break the system that way, because Ubuntu Touch is not meant to be updated with apt.
The PinePhone port is, you can't update it using the normal System Settings approach.
Hello everyone!
I have a PinePhone (original, not Pro) which is currently running Ubuntu Touch 20.04. I'd like to upgrade the device to run Ubuntu Touch 24.04.
As far as I can tell, 24.04 does not officially support the PinePhone and does not offer an official upgrade path.
With that said, I'm familiar with upgrading Debian and Ubuntu machines manually from one version to the next using APT. Has anyone tried something similar with the PinePhone?
I suspect doing a manual upgrade will work, at least to get the proper upgraded packages in place. However, I'm concerned this method might result in me trying to boot an incompatible kernel.
@darshpreets said in Running a Home Server on Ubuntu Touch – Feasibility & Experiences?:
Hi all,
Has anyone here successfully run a home server directly on Ubuntu Touch?
I have, from my PinePhone.
What kind of services you’ve managed to run (e.g., web server, file server, SSH, media streaming)
OpenSSH, file server, web server, torrent service.
How stable the system is for 24/7 operation
Perfectly. It's just like running Ubuntu Server.
Any limitations due to the read-only root filesystem or confinement
No. If you are really worried about filesystem permissions you can set up a container to host your services.
Recommended tools or packages to make it work
Nothing special required. Remember, Ubuntu Touch is Ubuntu. The same packages and guides apply.
@AppLee It's a good theory. But, as you said, I'm not interacting with the phone. It's locked, sitting on a shelf. No notifications are coming in and the device isn't being touched.
I think there must be a service or background job that is causing the phone to "wake up" or adjust screen settings. Just need to track down what it is.
I have a follow-up question.
Using the above path I can change the brightness, but the screen only remains dimmed temporarily (about ten minutes). After that the screen brightens again.
The PinePhone has a brightness range from around 0 to 3000 and the system automatically resets the backlight to 943 after a period.
The "automatically adjust brightness" option is turned off under the battery/power settings.
What service would automatically brighten the screen while the phone is locked and not being used interactively?
@Vehi_MV said in Dimming the display without locking:
@guru
Hi. You can set the brightness of display from terminal.
For example if you want 50% brightness you can use the following command:
echo 50 > /sys/class/leds/lcd-backlights/brightness
In case anyone else finds this thread, this was very helpful, but the path isn't the same on my system. I'm running 20.04 on the PinePhone and the path for dimming/brightening the screen is:
/sys/devices/platform/backlight/backlight/backlight/brightness
Update: I found the solution. At least when using command line programs like mplayer.
UBports on the PonePhone seems to default to trying to use PulseAudio, which doesn't work. It needs to be using ALSA, but the regular user account selects the wrong ALSA device by default. For some reason the root user gets the right device.
I used the "aplay -l" command to get a list of local audio devices:
$ aplay -l
card 0: PinePhone
card 1: sun9ihdmi
It seems the regular user is selecting card 1 when it needs to be selecting card 0.
So to play audio with mplayer (or other audio players) I need to manually specify card 0. With mplayer that looks like this:
mplayer -ao alsa:device=hw=0 audio-file.mp3
I'm currently looking for a way to make this selection permanent and consistent for all audio players, but for now I can at least funnel audio through mplayer on my PinePhone.
I'm running UBports 20.04 on a PinePhone.
An issue I've run into is no applications are able to produce sound when run as the regular user, phablet. This means the settings panel, web browser, and terminal applications such as mplayer cannot produce sound. Even when the volume controls are at max, no sound comes out, either through the phone's speak or through headphones when they are plugged in.
However, audio does work when applications are run as the root user. If I run "sudo mplayer audio-file.mp3" I get sound, but just "mplayer audio-file.mp3" produces no sound.
I've checked and the phablet user is part of the audio group. And the /dev/dsp and /dev/dsp1 devices are present and grant write access to the audio group.
Anyone else running into this? Anyone have a suggested fix? I'm a bit puzzled why phablet can't produce audio but root can.
Update: I have found that copying data directly to /dev/dsp can cause noise to be produced. For example, running "cat sound.wav >> /dev/dsp" causes noise to be produced by the phone's speaker. So I can confirm my user has write access to the audio device. It just seems media apps and web browsers run as my user (phablet) are not able to properly get audio to output while root can.