Users might have pins in their bookmarks that they want to use for routing, since the centerpoint/cursor are hard to accurately line up, and Nominatim is not always reliable in providing desired results. We may want to also allow specifying the group manually, in case users want to route between pins in different groups (like if they have a group for home/work, and a group for favorite coffee shops or restaurants).
I would argue that we should by default merge left and right modifiers into
c, and then provide alternatives for specifying only one side (maybe
lsfor Left-Shift or
_ uis also mapped to
shellpipe mepo_ui_menu_pref_url.sh, requiring
pin_purgeto be remapped elsewhere.
The current behavior for 0.3 is to add pins to the currently-active group. For a future where async STDIN/scripts are a thing, we'll want calls to
pin_addto be able to specify which group they should be placed in (like if a background script incrementally adds nearby POIs as you move around).
The issue is in the sxmo_megiaudioroute program, which sets the volumes manually. You can use sxmo_vol.sh to then set the audio volume higher.
Of course, this is still a bug in my eyes, and should probably be handled by setting a higher default volume in sxmo_megiaudioroute.
I've seen this before during a fresh boot, from which only a reboot will fix it. It's probably a bug in the kernel, Xorg, or dwm I would guess.
This is an error you get when polkit isn't running, and so ModemManager can't find it on DBus. Make sure to
rc-service polkit startand
rc-update add polkit bootto ensure it's started and runs before ModemManager. You will probably need to
rc-service modemmanager restartfor MM to start seeing polkit.
I've also got the same error; I can workaround it by using sudo in a terminal, but the Networks GUI doesn't work. I'm also on pmOS edge, and a month-old Sxmo (so it's not because of recent Sxmo changes).
+1 to this, especially IPC control. dbus would be the "right" way to do this, but since dbus isn't exactly the simplest thing to work with, we could implement a custom text-based IPC protocol over a domain/TCP socket.