@Eric-H
miatoll

-rwxrwxrwx 1 system system 4,0K led 19 12:40 /sys/class/power_supply/battery/charging_enabled

@Antares86 what caused this? have you tried installing 24.04?

Another reboot helped, now indicator works, we can mark miatoll as working, just needed two reboot not just one

@Eric-H it is pretty much possible i did not look how is getting device name implemented, but device is identified as miatoll in logs, and also in releases http://system-image.ubports.com/utnext/arm64/android9plus/daily/ on same level as surya

I am not sure if i grabbed working build 0.4 from today

https://dpaste.com/DJSGN2QTL

can you make a release? thanks @paulcarroty

it should be available to test in QA

sudo umount /usr/share/session-migration/scripts
sudo ubports-qa install focal_-_PR_lomiri-system-settings_469
sudo ubports-qa install focal_-_PR_lomiri-indicator-network_130
sudo reboot

@Kharim ok that release may be broken, i havent tried it since author did not marked what is workign what not,

I am on some old build belive this one https://gitlab.com/debclick/uFirefox/-/jobs/7676432640/artifacts/browse/build/aarch64-linux-gnu/app/

@Kharim just open it with open store

try this firefox, I am using it daily with synced bookmarks from desktop

https://gitlab.com/debclick/uFirefox

https://gitlab.com/debclick/uFirefox/-/jobs/7997863762/artifacts/browse/build/aarch64-linux-gnu/app/

@Il-Dorato
not sure how to help you with terminal application with clipboard, i have no experience with pasting in there, I am applying those rules via ssh connection from my pc, other option is adb shell via usb cabale

noble will be released in the future, within a few months, since I am not able to install it on my phone (others do) I can try to cherry pick those commits into focal's devel

@Il-Dorato
got it, I'v set up wpa3 only network on mine unifi AP and it seems i have working fix waiting to be merged into noble

is it also some other device's issue that not every release can be installed? todays build seems to be also too big

also on mine device, miatoll - note 9 pro, i reported it https://gitlab.com/ubports/ubuntu-touch/-/issues/2218
it seems you can init connection with

nmcli dev wifi list

sudo nmcli dev wifi connect "AP WPA3-Only" password "xyz"

btw what is your network? WPA3 personal only?

@kristatos OSK fix seems to be merged, i am also waiting for adb

1. a) setting up password crashes, but password is set
2. b) even when setting numeric pin, when unlocking it asks offers me qwertz keyboard not numeric input
3. terminal is not opening
4. adb shell is not working for me

$ adb shell

• daemon not running; starting now at tcp:5037
• daemon started successfully
  adb: device unauthorized.
  This adb server's $ADB_VENDOR_KEYS is not set
  Try 'adb kill-server' if that seems wrong.
  Otherwise check for a confirmation dialog on your device.

one big plus, fingerprint unlock works

@mariogrip thank you, now it seems that latest build is okay,
version-66.json 2024-12-25 12:45
it just seems there is some keyboard no-vibrations issue in system settings, while morph is not opening keyboard at all

has there been a major change (breaking change?) that makes it necessary to resize the filesystem as a result?
I can't seem to install the latest version 64 (2024-12-23 12:44)
version a few days ago, I believe version 60 went "well" at least booting

I tried installing on top of version 60 via ubports-installer but it ended up boot-looping, then I reflashed the phone back to android and installed latest utnext but ended up in ubports recovery reporting "exit code 256, view recovery logs /cache/ubuntu-updater.log" which is the same error I had when moving from 16.04 to 20.04, which was fixed by resize filesystem "system"

the log file:

Loading keyring: image-master.tar.xz
Loading keyring: image-signing.tar.xz
umount: /dev/block/dm-0: Invalid argument
umount: /cache/system: Invalid argument
umount: /system_root: Invalid argument
umount: /mnt/system: Invalid argument
e2fsck 1.44.4 (18-Aug-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/dm-0: 11/196608 files (0.0% non-contiguous), 29884/786432 blocks
Formatting: data
Keyring doesn't exist: device-signing
Applying update: rootfs-1cc30f282c1d6dc014ad80a4b6cf84c82763919be5c2315b9d5b384b0665ddc4.tar.xz
mv: bad 'data/*': No such file or directory
Keyring doesn't exist: device-signing
Applying update: device-3480823f589b096575d103dc137e66ac10d62bdd8f0a4047931864c1a12bf956.tar.xz
tar: write error: No space left on device
joyeuse:/ # %  

@naizena are you on https:// of given site ?

@mihael on mine miatoll it seems to be
/sys/devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm6150l@5:qcom,wled@d800/backlight/backlight/brightness

and minimal value is 161, maximal is 4095

when i set from root to zero, it seems to be just black, that is fine i shall test minimal value at night

root@uxesPhone:/home/phablet# echo 1 > /sys/devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm6150l@5:qcom,wled@d800/backlight/backlight/brightness