Sxmo - Simple X Mobile Released for the Pinephone (new minimalistic UI & image)
yeah, it started out of date (1969) but I used ntpd to sync it with my PC's ntp server which solved that

to be clear, only the pinephone related packages are failing. the regular alpine stuff is downloading and updating just fine

Code:
[ mo@TMobil: ~ ]$ sudo apk cache download -v 2>&1 | grep UNTRUST
ERROR: linux-postmarketos-allwinner-5.9.10_git20201123-r1: UNTRUSTED signature
ERROR: libmm-glib-9999-r2: UNTRUSTED signature
ERROR: charging-sdl-0.1-r1: UNTRUSTED signature
ERROR: triggerhappy-0.5.0-r0: UNTRUSTED signature
ERROR: u-boot-pinephone-2020.07_git20200803-r1: UNTRUSTED signature
ERROR: device-pine64-pinephone-0.15-r0: UNTRUSTED signature
ERROR: firmware-pine64-rtl8723bt-0_git20200705-r0: UNTRUSTED signature
ERROR: firmware-pine64-ov5640-0_git20201028-r0: UNTRUSTED signature
ERROR: device-pine64-pinephone-nonfree-firmware-0.15-r0: UNTRUSTED signature
ERROR: xkeyboard-config-9999-r2: UNTRUSTED signature
ERROR: gtk+3.0-9999_git20201022-r0: UNTRUSTED signature
ERROR: sxmo-dmenu-4.9.6-r0: UNTRUSTED signature
ERROR: sxmo-dwm-6.2.9-r0: UNTRUSTED signature
ERROR: sxmo-st-0.8.3.3-r0: UNTRUSTED signature
ERROR: sxmo-surf-2.0.3-r0: UNTRUSTED signature
ERROR: sxmo-svkbd-1.0.5-r0: UNTRUSTED signature
ERROR: modemmanager-9999-r2: UNTRUSTED signature
ERROR: modemmanager-openrc-9999-r2: UNTRUSTED signature
ERROR: sxmo-utils-1.1.11-r1: UNTRUSTED signature
ERROR: sxmo-xdm-1.1.12-r0: UNTRUSTED signature
ERROR: postmarketos-ui-sxmo-0.2-r0: UNTRUSTED signature
any plans on releasing the software stack as a standalone package?
I've been eyeing installing sxmo on top of a barebones ArchARM install
Just updated as of today (12/14/2020), got complaints about conflicting XDM, keyboard went away, so no clean reboot possible. When restarted, no XDM came up, no keyboard either.
(12-14-2020, 05:58 PM)vandys Wrote: Just updated as of today (12/14/2020), got complaints about conflicting XDM, keyboard went away, so no clean reboot possible.  When restarted, no XDM came up, no keyboard either.
Same here - reflashed SD [edge] OK.
(12-13-2020, 06:16 PM)hiimtye Wrote: any plans on releasing the software stack as a standalone package?
I've been eyeing installing sxmo on top of a barebones ArchARM install

I know there is one person on the IRC channel working on Sxmo on Arch. Should be quite possible as everything is properly tagged and package tarballs exist (which the Alpine packages use). Just a matter of writing the PKGBUILDs for Arch.




(12-14-2020, 07:16 PM)--- Wrote:
(12-14-2020, 05:58 PM)vandys Wrote: Just updated as of today (12/14/2020), got complaints about conflicting XDM, keyboard went away, so no clean reboot possible.  When restarted, no XDM came up, no keyboard either.
Same here - reflashed SD [edge] OK.

Regarding the XDM error - this is a one-time error requiring user-intervention since we switched our packaging to use the official XDM rather then a fork. The user intervention needed is basically to run `apk fix`.

See:
https://postmarketos.org/edge/2020/12/14/sxmo-1.2.0/

Also for more details on the new 1.2.0 release see the release announcement at:
https://lists.sr.ht/~mil/sxmo-announce/%...roy.lxd%3E

Also a new 1.2.0 image has been released:
https://lists.sr.ht/~mil/sxmo-announce/%...ail.com%3E

The biggest change in 1.2.0 is a rework of the gestures. With the new gestures rework, many things previously only accessible through buttons are now also accessible using gestures. Also in 1.2.0 the keyboard is now from upstream svkbd and vastly improved.

Maarten put together a nice video of some of the new features on 1.2.0 at:
https://diode.zone/videos/watch/9651fd70...1007b8509e
mil
(12-13-2020, 06:16 PM)hiimtye Wrote: any plans on releasing the software stack as a standalone package?
I've been eyeing installing sxmo on top of a barebones ArchARM install

I know there is one person on the IRC channel working on Sxmo on Arch. Should be quite possible as everything is properly tagged and package tarballs exist (which the Alpine packages use). Just a matter of writing the PKGBUILDs for Arch.




(12-14-2020, 07:16 PM)--- Wrote:
(12-14-2020, 05:58 PM)vandys Wrote: Just updated as of today (12/14/2020), got complaints about conflicting XDM, keyboard went away, so no clean reboot possible.  When restarted, no XDM came up, no keyboard either.
Same here - reflashed SD [edge] OK.

Regarding the XDM error - this is a one-time error requiring user-intervention since we switched our packaging to use the official XDM rather then a fork. The user intervention needed is basically to run `apk fix`.

Thanks!  Without a keyboard, a small exercise.  I'll see if I can ssh in, or perhaps get a keyboard via the convergence dock. Smile


All the other distros seem clunky after getting used to a lean (even elegant) UI.  Worth the trouble!
[quote pid='85776' dateline='1608009887']

Regarding the XDM error - this is a one-time error requiring user-intervention since we switched our packaging to use the official XDM rather then a fork. The user intervention needed is basically to run `apk fix`.

[/quote]
I got on to my phone and did this operation; rebooted and still no XDM.
ssh'ed on to the phone and ran xdm manuall, and it came up.
Who's supposed to be launching it?  I'll have to take a look.
I'm also unable to start XDM. I don't think an X server is started on bootup as it stalls at the screen with the PostmarketOS logo, and a prompt to login in the top corner.
I SSH'd in and tried to manually start XDM with:
sudo DISPLAY=:0 xdm
but no xdm session was launched. will try to tinker with it later after I get the kids from school.

note: there were errors regarding storage space on the last update. I'm not sure where the apk performs it's updates, but if it's in a tmpfs partition, then that's an issue. while updating the kernel the error was no space left on device. I thought that might be the /boot partition, but there's plenty of space left on that so I'm thinking it's an issue with tmpfs space not actual storage.
to remedy, I performed a series of steps:

I forced a reinstall of the packages that might be related to xdm:
sudo apk fix postmarketos-ui-sxmo sxmo-xdm-config sxmo-xdm-config-openrc xdm xdm-openrc

then I forced a reinstall of the kernel to force a reflash to /boot (from memory, package might be different):
sudo apk fix linux-postmarketos-allwinner

then I set xdm as the default run level:
sudo rc-update add xdm default

then I restarted. I may have performed some unnecessary steps, but I got it resolved *shrug*

the phone is charging now, so we'll see if I have to fix any further damage later. when I started, it was at 14%. it doesn't like charging while the screen is on, which it has been all day at the login screen. it also doesn't like to charge over 90% so I'm not sure what that's about.
(11-28-2020, 05:41 PM)hiimtye Wrote: update: I can select different devices, but selecting speakers powers them on, but no sound comes through them
so I resolved this, by accident. when I was configuring my conky display, I set my old tconk.sh script to run, and one of my extra config options in it is to swap in a .asoundrc depending on what sound system I'm using (I have one for pulse/OSS, one for pulse/alsa, one for alsa/dmix). I swapped in the pulse/alsa one (as that's the one I use on my PC, which the script is configured for) and lost sound. I swapped in the alsa/dmix one and the speakers work fine now. for reference, here's my alsa/dmix .asoundrc:


Code:
# This configuration works for sharing sound in WINE and normal apps
pcm.my_card {
    type hw
    card 0
    device 0
}

ctl.my_card {
  type hw
  card 0
}

pcm.dmixed {
    type dmix
    ipc_key 1024
    slave {
        pcm "my_card"
    period_time 0
    period_size 1024
    buffer_size 8192
    rate 44100
    #format "S32_LE"
    #periods 128
    }
}

ctl.dmixed {
  type hw
  card 0
}

pcm.dsnooped {
    type dsnoop
    ipc_key 2048
    slave {
        pcm "my_card"
    }
}

ctl.dsnooped {
  type hw
  card 0
}

pcm.asymed {
    type asym
    playback.pcm "dmixed"
    capture.pcm "dsnooped"
}

ctl.asymed {
  type hw
  card 0
}

pcm.pasymed {
    type plug
    slave.pcm "asymed"
}

ctl.pasymed {
  type hw
  card 0
}

pcm.dsp0 {
    type plug
    slave.pcm "asymed"
}

ctl.dsp0 {
  type hw
  card 0
}

pcm.!default {
    type plug
    slave.pcm "asymed"
}

ctl.!default {
  type hw
  card 0
}


Possibly Related Threads…
Thread Author Replies Views Last Post
  PostmarketOS sxmo pinephone keyboard keymaps? afwtioane 2 2,063 09-11-2022, 04:37 AM
Last Post: manubert
  sxmo pim nextcloud Uturn 8 6,094 02-22-2022, 03:23 PM
Last Post: TRS-80
  Battery life on sxmo xark 1 2,098 02-12-2022, 10:07 AM
Last Post: TRS-80
  Official Channels for Sxmo Support anjanmomi 2 3,088 02-12-2022, 09:50 AM
Last Post: TRS-80
  sxmo & php --- 2 1,788 01-31-2022, 01:45 PM
Last Post: ---
  sxmo improvements unrealb2 7 5,701 11-17-2021, 06:43 AM
Last Post: fdlamotte
  SXMO on Debian IVp 0 2,184 08-21-2021, 02:33 PM
Last Post: IVp
  Megi's multiboot sxmo image aithal 1 2,190 06-14-2021, 08:07 AM
Last Post: fdlamotte
  SXMO svkbd with joypad layout [for basic dosbox play] streak 0 1,492 05-27-2021, 08:47 AM
Last Post: streak
  Sxmo on Arch IVp 4 6,436 05-19-2021, 03:18 AM
Last Post: dukla2000

Forum Jump:


Users browsing this thread: 2 Guest(s)