Handle some quirks manually, they will be added to the script soon:
Run apk del postmarketos-hidden-desktop-entries before the upgrade
If you use Phosh, manually apk add gnome-software-plugin-apk afterwards
After the upgrade, if you have megapixels installed: apk del megapixels and apk add postmarketos-default-camera (will install megapixels again in case of the pinephone, but on the Librem 5 it will install millipixels)
External display not working. #1778. Not a regression.
Suspend is not working, not a regression.
Audio is now working! While anything is playing there is a pretty loud hiss. I worry that some applications may setup pulseaudio while they're not actually playing anything, causing this hiss to remain. But this is probably better than no audio.
Bluetooth could scan and find devices. Attempting to pair with my bluetooth keyboard using bluetoothctl yielded error: org.bluez.Error.Failed br-connection-create-socket. I have never tried to use bluetooth before on this device. It could be an issue with my configuration and/or not a regression.
Front camera worked, but curiously there are three other video devices in /dev. video0 through 4. The front camera was video1. Cheese reports "Error during camera setup: No device found" perhaps for this reason? I'm fairly certain Cheese worked by default before, so this is probably a regression. Although the webcam isn't really useful for anything, so also probably not worth blocking over.
I'm not sure whether to create an issue for these problems, so I leave them here for now. Hopefully testing from @StevenVB will make this more apparent.
Verdict:
Probably best to fix the backlight issue first, in my opinion! (Fixed!)
Audio is now working! While anything is playing there is a pretty loud hiss. I worry that some applications may setup pulseaudio while they're not actually playing anything, causing this hiss to remain. But this is probably better than no audio.
In my case, the hiss is only present if the screen brightness is between 51% and 98%. Setting the brightness to either 50% or 100% fixes the issue.
I read in the pine64 forums that is seems to be related to power regulation, but I don't think that anyone has seriously debugged this.
I found mention of this right before you replied. There is a very audible high-pitched whine at certain backlight levels, but there is also an ever-present static hiss that seems to be unrelated to the backlight level.
Shipmode is likely broken, unsure how to test this.
Yes, a fix is being worked on in !4128 (merged). Clayton also wrote in the MR how it can be tested (
!4128 (comment 1409310172)). But as we know it's broken right now, I'd wait with testing until it is merged to v23.06 soon - or test the MR if you like.
GPS should be working when gnss-share-0.7.1 lands in Alpine 3.18. The aports repo has the update, but the Alpine aarch64 builder has been offline/nonfunctional...
Thanks for the test. This doesn't look good, can you create an issue? We'll probably not be able to resolve this for v23.06 but if somebody wants to look into it, at least then there is an issue that tracks the current state.
EDIT: I wonder if this is caused by buggy automatic screen brightness.
@ollieparanoid
20230601-0726-postmarketOS-v23.06-plasma-mobile-3.9-oneplus-fajita.img looks better after I did a complete OS reinstall. It sees simcard and shows bars.
Device boots and it's possible to login (password: 147147)
Hardware:
Automatic screen rotation works
Brightness control works
Light sensor (Automatic brightness) works
Touch (with multitouch) works
Buttons work
Haptic feedback works
Fuel gauge works
Charger detected and charging works (100% charging always)
Sound over speaker works
USB OTG / host mode
Torch / flashlight
GPS works (not calibrated)
Magnetometer or compass works
NFC works
IR blaster works
Sound:
Speakers, headphones and earpiece work
Headphones selected automatically when plugged in
Microphone works
Connectivity:
Bluetooth (BT headphones connect)
WiFi
Cellular: (It don't recognize sim at all. It worked on previous builds)
Mobile data works
SMS works
Making a call works
Receiving a call works
Proximity sensor works
Camera:
Front camera
Lens actuator (autofocus) works
Rear camera
Lens actuator (autofocus) works
Extra notes:
Slow to open FireFox. It took a minute then opened 2 instances.
Had to manually rotate screen because I was not able to click on a checkbox in the browser.
It's not recognizing sim-card.
Camera not working.
GPS not calibrated.
Had to manually adjust brightness.
@ndbits thanks for testing! The SIM card issue is odd, I've checked here and it seems to work on for me. Could you maybe fetch syslogs (logread > syslog.log) and dmesg with the broken SIM?
note that you need to increase log levels first to get something useful from modemmanager, and it will contain sensitive data. I suggest getting the logs, but looking at it yourself if there's something obvious that would cause it not to work, remove personal data like phone numbers if needed and post that interesting part here.
Device boots and it's possible to login (password: 147147)
Hardware:
Automatic screen rotation works
Brightness control works
Light sensor (Automatic brightness) works
Touch (with multitouch) works
Buttons work
Haptic feedback works
Notification led works
# I cannot tell if it is working or not. It does not blink when I have an unread SMS notification, but I do not know if it should in that scenario.
Fuel gauge works
Charger detected and charging works
External display
Sound over HDMI/DP works
Did not test, as I don't have the right adapter
USB OTG / host mode
Torch / flashlight
GPS works
Magnetometer or compass works
NFC works
IR blaster works
Sound:
Speakers, headphones and earpiece work
Headphones selected automatically when plugged in
Microphone works
Connectivity:
Bluetooth
WiFi
Cellular:
Mobile data works
SMS works
Making a call works
Receiving a call works
Proximity sensor works
Camera:
Front camera
Lens actuator (autofocus) works
Rear camera
Lens actuator (autofocus) works
Extra notes:
After upgrade, kasts stopped working. I cannot open the app from the UI. From the terminal I get the following errors, which so far I was unable to fix (notice that neither the apk nor the flatpak version work):
shift-mq:~$ flatpak run org.kde.kastsFailed to create wl_display (No such file or directory)qt.qpa.plugin: Could not load the Qt platform plugin "wayland"in"" even though it was found.This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.Available platform plugins are: eglfs, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, xcb.shift-mq:~$ kasts error: XDG_RUNTIME_DIR is invalid or not set in the environment.Failed to create wl_display (No such file or directory)qt.qpa.plugin: Could not load the Qt platform plugin "wayland"in"" even though it was found.This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, xcb.Aborted
There might be a plasma bug affecting plasma Apps in PHOSH.
Edited: after additional checks, it seems that it was more of a problem with kasts. See my comment below.
shift-mq:~$ kasts Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. QSocketNotifier: Can only be used with threads started with QThread Database version 6 QQmlApplicationEngine failed to load component qrc:/main.qml:163:34: Type GlobalSearchField unavailable qrc:/GlobalSearchField.qml:13:1: module "org.kde.kirigamiaddons.labs.components" is not installed
Which led me to think that there was a dependency missing:
After installing it, kasts started working: sudo apk add kirigami-addons. Therefore it seems that this was more of a packaging issue for kasts than something related to the release.
I edited my previous post with the test results. I left the note with the problem, but added a checkmark for "testing complete".
I will open a different report for the issue with packaging kasts. Thank you!
[ ] Charger detected and charging works(known broken)
[N/A] External display
[N/A] Sound over HDMI/DP works
[ ] USB OTG / host mode(known broken)
[ ] Torch / flashlight(known broken)
GPS works (untested)
Magnetometer or compass works (untested)
NFC works (untested)
[N/A] IR blaster works
Sound:
Speakers, headphones and earpiece work
Headphones selected automatically when plugged in (caveat - if the speakers device is selected as default, it doesn't switch back to the earpiece/headset device)
Device boots and it's possible to login (password: 147147)
Hardware:
Automatic screen rotation works
Brightness control works
Light sensor (Automatic brightness) works (know broken)
Touch (with multitouch) works
Buttons work (assigned the center button to trigger application fullscreen, quite nice)
Haptic feedback works (know broken)
Notification led works
Fuel gauge works
Charger detected and charging works
[N/A] External display
[N/A] Sound over HDMI/DP works
USB OTG / host mode
Torch / flashlight (know broken)
GPS works (With SIM card and mobile data using PureMaps, slow, inaccurate)
Magnetometer or compass works (know broken)
[N/A] NFC works
[N/A] IR blaster works
Chipset specific features:
SMP works (all CPU codes detected)
Frequency scaling works, full range available (CPU only seems to scale max to 998.400 MHz, more should be available)
Device suspend works (Enabled Suspend and waited a few minutes, then I was able to call the phone and pick it up. Not sure if device really entered sleep mode)
Hardware video encoder/decoder works (don't know how to test it)
GPU/3D acceleration works
Sound:
Speakers, headphones and earpiece work
Headphones selected automatically when plugged in
Microphone works
Connectivity:
Bluetooth
WiFi
Cellular:
Mobile data works (Most of the time stuck on 2G even outside, takes long time to switch to 4G)
SMS works
Making a call works
Receiving a call works (Rejecting a call requires two presses on the hangup icon: After first rejection it reappears again, caller side stops hearing the dial tone during this)
Proximity sensor works (know broken)
Camera:
Front camera (know broken)
Lens actuator (autofocus) works (know broken)
Rear camera (know broken)
Lens actuator (autofocus) works (know broken)
Extra notes:
Phosh and most apps does not really like such a small resolution display. On the Lockscreen 'Slide to unlock' text and 'Unlock' button is cut in half. In applications the bottom of active screen is sometimes cut out.
Device boots and it's possible to login (password: 147147)
(installed to test on sdxc card itself)
(installer thinks that it needs touch keyboard though (not regression))
(note installer cannot set password 147147 because need at least 8 characters? bug?) (6)
Hardware:
Brightness control works
Touchpad works
keyboard works
Notification led works
Fuel gauge works
Charger detected and charging works
External display (usb c adaptor display not detected (usb + ethernet ok))
Sound over HDMI/DP works
Sound:
Speakers, headphones work (not working but working on edge emmc install?) (5)
Headphones selected automatically when plugged in
Connectivity:
Bluetooth (usb mouse works)
WiFi
Camera:
Front camera (cheese segfaults, vlc works /dev/video3)
Extra notes:
apk add cheese -> dm crypt failed and thus could not install cheese, seems partition is just full
ext4-fs error (device dm-0): __ext4_new_inode:1276: comm apk: failed to insert inode 41385: doubly allocated?
ext4-fs errir (device dm-0) in ext4_free_inode:362: Corrupt filesystem
-> it seems the /dev/mapper/root is only 2GB in size-> partition does not get resized on boot?
sdc 8:32 1 58,2G 0 disk
├─sdc1 8:33 1 228M 0 part /run/media/steven/pmOS_boot
└─sdc2 8:34 1 2,1G 0 part
└─luks-710d9bf6-3324-4589-9ad2-c1de014a0513
253:0 0 2,1G 0 crypt /run/media/steven/pmOS_root
-> 64Gb sd card seems faulty.
-> retest with non installer version, same issue, partition is not resized! (even on other 4Gb sdcard) (2)
-> retest with pmbootstrap generating to the sdcard (encrypted, 4Gb)
gnome:
auto date and time ok but automatic timezone cannot be enabled (requires location services and internet access) ? (3)
gnome-keyring issue -> install eg fractal or pika backup (via flathub) and it does not have a keyring (4)
-> fractal keeps asking credentials each boot
-> pika backup fails to backup
Verdict:
(1) cheese segfauls (sigsegv in pw_thread_loop_get_loop() from libpipewire-0.3.so.0)
(2) partition is not resized (if using installer or 23.06 load), could this be related to my spi towboot?
(3) timezone not detected or not able to choose so wrong, no regression but imho feels bad (only works with pmbootstrap because its selected from host)
(4) gnome keyring does not work, no regression but imho breaks easy usage (no solution found yet)
(5) sound does not work out of the box (pmbootstrap 23.06 version and 23.06 non installer image, works on emmc installed edge image with only a reboot)
(6) seems strange that you cannot set a 6 char password via the installer but the default image can set 147147 ?
(2) partition is not resized (if using installer or 23.06 load), could this be related to my spi towboot?
Can you make a separate issue in pmaports?
(3) timezone not detected or not able to choose so wrong, no regression but imho feels bad (only works with pmbootstrap because its selected from host)
It can be chosen in the settings, but agreed that it would be more userfriendly to be able to choose it during installation. Created https://gitlab.com/postmarketOS/ondev2/-/issues/10 to implement it at some point in the new installer.
(4) gnome keyring does not work, no regression but imho breaks easy usage (no solution found yet)
Is this #1767 or something different? Please point to an existing issue or create one
(5) sound does not work out of the box (pmbootstrap 23.06 version and 23.06 non installer image, works on emmc installed edge image with only a reboot)
Not sure what you mean, please make a separate issue. There are reports of having sound working on it though.
(6) seems strange that you cannot set a 6 char password via the installer but the default image can set 147147 ?