Hi all,

Just as a follow-up from Maarten's last email about the 1.3.0 release, I've
triggered the CI to build a new image.

The new 1.3.0 image is available at:
http://images.lrdu.org/pinephone/

Also, an additional quick note.. pmOS is also now building weekly Sxmo images.
The images built via pmOS's infra are really no different then our own CI which
may eventually be deprecated but is remaining for now for immediate release
testing and nightly testing around upcoming releases.

The only thing to note is the default username / password is different for

On Thu, Dec 31, 2020, at 8:24 AM, Maarten van Gompel wrote:
> There were a few new upstream commits at suckless for dmenu, I now
> integrated these into our tree.
> 
> --
> 
> Maarten van Gompel (proycon)
> https://proycon.anaproy.nl
>

Great - thanks for that. This does bring up the question of how to handle
tagged versions after upstream version updates. The way sxmo tracks
all forks for version numbers is sucklessversion.sxmoversion. E.g. for
dmenu we forked off 4.9 and were at our 7th revision. So our last tag

On Wed, Dec 30, 2020, at 4:15 AM, Maarten van Gompel wrote:
> On 20-12-30 06:12, Anjandev Momi wrote:
> > I have been using this patch for the past couple of days and it works
> > perfectly. It especially improves the touch user experience on smaller
> > ui elements (ie. files).
> >
> > The only thing left to decide is: do we want to have a environmental
> > variable that will decide whether this is enabled?
> >
> > I like the patch as is and dont want to add more environmental variables
> > but I won't merge until there has been sufficient discussion from the
> > community.
> 
> Great work! I think this patch is a definite improvement over the old 

Hi all,

Just a quick note, a new image for the 1.2.0 release of Sxmo has been rolled.

The the new 1.2.0 image is available at:
http://images.lrdu.org/pinephone/

To see the full changelog for 1.2.0, reference Maarten's earlier announce
email or check the generated changelog at:
https://git.sr.ht/~mil/sxmo-docs/tree/master/CHANGELOG.md

-- 
Note on versioning for the curious:
In early versions we had been correlating sxmo-utils minor version numbers

Anjandev Momi <anjan@momi.ca> wrote:
> diff --git a/scripts/appscripts/sxmo_rss.sh b/scripts/appscripts/sxmo_rss.sh
> index 2b50862..d298932 100755
> --- a/scripts/appscripts/sxmo_rss.sh
> +++ b/scripts/appscripts/sxmo_rss.sh
> @@ -1,8 +1,8 @@
>  #!/usr/bin/env sh
>  FETCHENABLED=1
>  
> -if [ -f "$XDG_CONFIG_HOME/sxmo/sfeedrc" ]; then
> -	SFEEDCONF="$XDG_CONFIG_HOME/sxmo/sfeedrc"
> +if [ -f "$XDG_DATA_HOME/sxmo/sfeedrc" ]; then
> +	SFEEDCONF="$XDG_DATA_HOME/sxmo/sfeedrc"
>  elif [ -f "$HOME/.sfeed/sfeedrc" ]; then

From: Miles Alan <m@milesalan.com>

---
 scripts/modem/sxmo_modemmonitor.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/modem/sxmo_modemmonitor.sh b/scripts/modem/sxmo_modemmonitor.sh
index bfb9916..16ef306 100755
--- a/scripts/modem/sxmo_modemmonitor.sh
+++ b/scripts/modem/sxmo_modemmonitor.sh
@@ -64,6 +64,7 @@ checkforincomingcalls() {
 		grep -Eo '[0-9]+ incoming \(ringing-in\)' |
 		grep -Eo '[0-9]+'
 	)"
[message trimmed]

From: Miles Alan <m@milesalan.com>

Use dbus to monitor for missed calls. Missed calls used to work but had a
regression due to the work to make text/calls used dbus. This adds the proper
dbus hook for missed calls as well and also changes the incoming call
notification to allow for multiple incoming calls (theoretically).

Tested for a single caller and transitioning the pickup notification
into a missed call notification and all is working good.
---
 scripts/modem/sxmo_modemmonitor.sh       | 20 +++++++++++++++++---
 scripts/modem/sxmo_modemmonitortoggle.sh |  3 ++-
 2 files changed, 19 insertions(+), 4 deletions(-)
[message trimmed]

From: Miles Alan <m@milesalan.com>

This way if someone wants a longer or shorter timeout that possible
by setting the env var SXMO_SUSPENDTIMEOUTS.

Also change the default to be 35s. This is roughly the duration of
ringing for an incoming phone call.
---
 programs/sxmo_screenlock.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/programs/sxmo_screenlock.c b/programs/sxmo_screenlock.c
index 34ed5e7..d7aba7f 100644
--- a/programs/sxmo_screenlock.c
[message trimmed]

Maarten van Gompel <proycon@anaproy.nl> wrote:
> This looks good to me, the less temporary hacks the better. Have you
> been testing this the past few days? Does it indeed not negatively
> impact the suspension? Since the 5.9 upgrade it does all seem more
> reliable and less crashy.
> 
> 
> On 20-10-27 04:14, Anjandev Momi wrote:
> > With the megi 5.9 kernel and other suspend-related merge requests in
> > postmarketos, disabling these drivers is no longer needed. All of this
> > should result in a more reliable suspending system.
> >

Thanks Anjan - this is way more reliable from my testing. I've applied

Hi all,

To follow up on Anjan's great work on the sxmo-utils 1.1.11 release,
I've also restored the Sxmo image baking infra and rolled a 0.1.11
release image for anyone who just wants to burn an SD card.

The new 0.1.11 image is available at:
http://images.lrdu.org/pinephone/

The changelog showing all of the sxmo-utils 1.1.10 -> 1.1.11 changes is at:
https://git.sr.ht/~mil/sxmo-docs/tree/master/CHANGELOG.md

Cheers,
Miles