~hazardchem

Australia

Tinkerer :P

Devices I own:

  • Asus TUF Gaming FX506I running Alpine Linux
  • PinePhone 1.2b running sxmo pmOS
  • iPhone 10
  • PineTime


#596 Reliability Issues Tracker 2 days ago

Comment by ~hazardchem on ~mil/sxmo-tickets

I'd rather have one ticket per issue, that way we can use the tools that sr.ht provides to track the status.

Yeah happy to do that if thats how things work for sr.ht.

#596 Reliability Issues Tracker 4 days ago

on ~mil/sxmo-tickets

On Sun, Apr 14, 2024 at 10:39:24AM +0000, ~hazardchem wrote:

After reading a blog post by Drew DeVault (on mobile linux) and polling the sxmo irc I have come across some reliability issues that we should look at addressing

  • Lock, Unlock, and Screenoff loop behaves inconsistently:
    • Single button press will sometimes bring to an unexpected state.
  • Waking up when there is a call coming in, and the delay to displaying a call
    • And also trying to unlock the screen see point above
  • Battery percentage update post suspend, sometimes will take 5-10 seconds to update

Yup bugs, I'll take a look at them if I can find the time.

  • DWM vs Sway giving inconsistent experiences
    • Possibly the easiest way to solve this is to change dwm to i3 as they its the x11 version of sway but there could be opposition to that (myself would be opposed to that change)

The only thing to do here is file bugs / send patches and we'll try to get it fixed.

I don't think switching to i3 much as most of the difference are between xorg and wayland, and less between window manager specifics.

  • Volume bar is laggier than the brightness bar to display

This is because each 5% increment requires a call from lisgd to the inputhandler to pactl / brightnessctl. IIRC the case statement in the inputhandler takes a while to execute, on top of forking several shells which will take 5ms-10ms each and pactl takes 50ms-100ms. All together I think one loop is on the range of 200ms-300ms.

There's a few things I can think of that might help:

  • try moving the pactl calls straight into the lisgd commandline
  • modify lisgd to print gestures to stdout instead of calling system, and keep the input handler hook always running (this saves a fork)
  • batch events, e.g. if 3 volume up gestures are triggered while one is processing, instead of calling the script three times, call it with a count of 3
  • (more aggressive) have some daemon that handles gestures which can keep an open connection to pulse/pipewire. pactl alone takes 50ms-100ms on my phone, and I wouldn't be surprised if a good portion of that is setting up the dbus connection.

The main goal of this bug report is to provide some focus on how to get some reliability issues sorted and visibility of them. This can be updated to follow more issues that arise as well.

Let me know your thoughts on the topic as this is the only way we are going to get progress is by talking about them.

I'd rather have one ticket per issue, that way we can use the tools that sr.ht provides to track the status.

#596 Reliability Issues Tracker 5 days ago

Ticket created by ~hazardchem on ~mil/sxmo-tickets

After reading a blog post by Drew DeVault (on mobile linux) and polling the sxmo irc I have come across some reliability issues that we should look at addressing

  • Lock, Unlock, and Screenoff loop behaves inconsistently:
    • Single button press will sometimes bring to an unexpected state.
  • Waking up when there is a call coming in, and the delay to displaying a call
    • And also trying to unlock the screen see point above
  • Battery percentage update post suspend, sometimes will take 5-10 seconds to update
  • DWM vs Sway giving inconsistent experiences
    • Possibly the easiest way to solve this is to change dwm to i3 as they its the x11 version of sway but there could be opposition to that (myself would be opposed to that change)
  • Volume bar is laggier than the brightness bar to display

The main goal of this bug report is to provide some focus on how to get some reliability issues sorted and visibility of them. This can be updated to follow more issues that arise as well.

Let me know your thoughts on the topic as this is the only way we are going to get progress is by talking about them.

#10 Touch Input Not Moving Input Location From UI Bar 4 months ago

Ticket created by ~hazardchem on ~lanodan/badwolf

I have noticed an issue when using a touch screen device such as the PinePhone that when touching on a text input on a website that the input is still directed to wherever the UI element is selected and not to the web page.

The only way to get the text to input is to tab until the selected UI element passes the print button and before it reaches the search box.

Using a mouse does't have this issue as the text is directed to where I have clicked on.

#592 SMS with multiple newlines get cut off 4 months ago

Comment by ~hazardchem on ~mil/sxmo-tickets

Hi Willow,

Must have missed that patch. Aii resolved now

#592 SMS with multiple newlines get cut off 4 months ago

Ticket created by ~hazardchem on ~mil/sxmo-tickets

I have noticed on git branch of sxmo that sms get cut off if it has new lines and the rest is discarded. Examples are below.

Sent Text: 1st Test: Hello

There

2nd Test: Hello There

3rd Test: Hello There

How Are You

Received Texts: Received today at 21:46:38 Hello

Received today at 21:46:43 Hello

Received today at 21:46:58 Hello

#591 ligsd fails to start on latest git 5 months ago

Comment by ~hazardchem on ~mil/sxmo-tickets

Hi Willow,

Yep all sorted with using lastest lisgd, cheers!

#567 sxmo_init.sh not respecting user defined $XDG_RUNTIME_DIR 8 months ago

Comment by ~hazardchem on ~mil/sxmo-tickets

Laughs in factotum (when I'm running it as a VM)

#573 menu redesign 8 months ago

Comment by ~hazardchem on ~mil/sxmo-tickets

I just had a play around with vis-menu, works really nicely!

Did see it outputting double strings but it could be a visual glitch.

echo '1' | sed 's|$|\n2\n3\n|' | vis-menu

Gives choices like below: 1 2 3

And once you select something: 11 1

But if its stored as a variable it is a single digit output so must just be a visual glitch.

#567 sxmo_init.sh not respecting user defined $XDG_RUNTIME_DIR 10 months ago

Comment by ~hazardchem on ~mil/sxmo-tickets

After revisiting https://lists.sr.ht/~mil/sxmo-devel/patches/40196 on a fresh install I can confirm this is being used now as I have it set in my profile.