Jump to content

User:Rontti

From postmarketOS Wiki
pmOS logo This user has a pmOS's GitLab profile.

Linux enthusiast and upcycling fan with a decade of FOSS experience

Notes on samsung-lt023g

  • my device doesn't vibrate, no need to stop holding keys to enter flash mode
  • need to check whether SECCOMP support is sufficient for running flatpaks
  • investigate pmbootstrap chroot -r as a stopgap for having working wifi ootb?
  • kernel cmdline changes aren't picked up?; debug shell is only accessible over telnet; start holding volume up as the samsung logo disappears, the postmarketOS bootup animation freezes

Notes on installing pmOS on beryllium

Notes on running pmOS edge with phosh, systemd and FDE on beryllium

Below is a list of problems encountered during my first daily-driving trial run during Feb 2025, intended as a sort of personal todo list for filing bugs and improving the documentation. Wifi and bluetooth (disregarding one pair of wireless buds) worked out-of-the-box, and I was able to get text messages, calls and mobile data working without much trouble. While the run was cut short due to user error, I did enjoy the experience and look forward to trying it out again soon, perhaps with SXMO.

  • the touchscreen feels too sensitive – pretty sure I was able to type without actually touching the screen
  • SIM pin entry shows up but fails to unlock the card, need to remove pin prior to inserting card
  • mic might work during calls OOTB if the correct one is selected? s/pipewire/pulseaudio/g instructions on wiki are aimed for sxmo, need to retry
  • WEP provider may need to be selected manually in settings
  • sensors seem to work, but
    • automatic display brightness needs smoothing
    • the layout is messed up for a second after screen rotation, could be covered up with an animation?
  • the "about" -dialog of gtk3 apps as well as the "app store" are too wide and must be closed via the home screen
  • megapixel config needs to be upstreamed; snapshot "works" OOTB
  • flatpaks fail to launch with setuid error -> pmaports#3572
  • signal-desktop and telegram-desktop conflict, resulting in a broken installation of the latter
    • signal-desktop is somewhat usable after rescaling using its own menubar's option – (most?) notifications show up on the lockscreen while suspended without murdering the battery life, and copy-pasting text from Firefox is possible albeit fiddly (could really use a paste button in the keyboard)
    • installing some vulkan package (the one for SDM 845?) breaks Wayland(?) apps after reboot, including the terminal and phone app which meant calls would ring silently
    • likely related: pmaports#3569
  • nftables does work, you can lock yourself out ;)
  • ttyescape isn't included by default when using pmbootstrap
  • neither debug-shell's instructions nor the Full disk encryption page cover unlocking the disk manually (in case the on-screen-keyboard bugs out) – it's LUKS for future reference

Additionally, on a non-systemd install, I was able to get Waydroid working with internet access by manually setting the default route to 192.168.240.1 (not 250 as documented here – is this device specific?).

My devices

Device Notes
Samsung Galaxy Tab 3 7.0 (samsung-lt023g) rootfs only worked on SD card and USER partition
Xiaomi POCO F1 (xiaomi-beryllium) notes on daily driving phosh on user page