Lock screen or require long press to prevent unwanted touches

[surge919]

I mostly ride with my phone on a quad lock out front mount and now that it's starting to get warm outside the sweat is starting to pour :-)
Sometimes I ride with it in a pouch and it has the same issue.

I keep it pinned so it can't switch away from the app but the sweat (and rain when it's raining) lands on the screen and makes random presses. Most of the items require a long press but the pause/stop button is a single press so every once in a while the perfect drop hits the button and my ride no longer records.

Could you add an option to lock all key presses or at least make it so all button presses require a long key press?

thanks

[Sublimis]

Have you considered using the Waving mode (Display > General > Waving mode)? It locks all key presses within the app using a proximity sensor, without adding more complexity to the layout.

If that's not enough, maybe the correct solution would be to allow the Rec button to be completely removed from the layout. This means that record/pause/stop actions would have to be done from the left drawer (main menu).

Let us know what you think. Thanks for the feedback!

[surge919]

Have you considered using the Waving mode (Display > General > Waving mode)? It locks all key presses within the app using a proximity sensor, without adding more complexity to the layout.

I enabled Waving mode then tried waving my hand in front a couple of times but nothing seems to happen and I can still use the interface

If that's not enough, maybe the correct solution would be to allow the Rec button to be completely removed from the layout. This means that record/pause/stop actions would have to be done from the left drawer (main menu).

That could work.. options are good since even if the Waving mode worked, using it in a pouch may not work since pouches affect the sensors.

thanks

[surge919]

I downloaded the beta and noticed you added an option to remove the record button from the main screen. This worked great and I didn't have any accidental stoppages during my latest ride.

Would it be possible to instead of removing it, leave it and disable it? this would allow quickly seeing the status.

Since there's no indication, someone could think they started it and not realize they didn't until they notice the miles and/or timer hasn't changed.

[Sublimis]

That's a valid argument. But instead of providing a potentially confusing disabled button, we've added another indicator to the status bar, like this. What do you think? It could be additionally emphasized to stand out from the rest of the indicators, if there's a need.

[surge919]

good idea.. that's much cleaner. how about instead of a greyed out arrow for 'not recording' make it Red so it stands out. so a quick view of the screen makes it very clear of the state.

…

On Mon, Jun 3, 2024 at 11:43 AM Urban Biker ***@***.***> wrote: That's a valid argument. But instead of providing a potentially confusing disabled button, we've added another indicator to the status bar, like this. What do you think? It could be additionally emphasized to stand out from the rest of the indicators, if there's a need. image.png (view on web) <https://github.com/Sublimis/UrbanBiker/assets/3844660/ae2e1e50-1ca3-4070-83e4-28c17e1658e3> image.png (view on web) <https://github.com/Sublimis/UrbanBiker/assets/3844660/08ccfccd-5955-4507-bdaa-e84c279aab25> image.png (view on web) <https://github.com/Sublimis/UrbanBiker/assets/3844660/43e6e013-2e5f-493f-8da2-388137103684> — Reply to this email directly, view it on GitHub <#204 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABINB77ZTWCJBLQRU2EGWYLZFSFLPAVCNFSM6AAAAABIEWCDV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVGU2DOMJVG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Sublimis]

The red color is already used to indicate a "hard-pause", i.e. when the user pauses using a command (as opposed to the auto-pause shown above in yellow). And trust me, you don't want anything red in the status bar when nothing is going on, it's much better to have (almost) nothing.

Btw you can now test this behavior in the latest beta just released!

[surge919]

The hard pause is a red pause symbol
The arrow could be red instead of grey.

Red indicates something needs attention so I think it still applies to being stopped.

It's easier to notice than the grey arrow when outside.

Btw... Combined with native Android pinning, this worked great. No more unintentional stopping of the recording.

[surge919]

what are your thoughts on making the icon red when stopped?
Maybe a Red Arrow or Red Square.. instead of simply grey

[Sublimis]

The latest version (v8.12) contains a "hidden" switch to enable this alternative status bar behavior: On the Settings > Advanced screen, long tap the topmost box (please see the screenshot attached). A simple true/false will be the output to indicate the current status. Not sure if it is better than the default status bar behavior, but we could at least make it a regular option if you're convinced it would be useful?

[surge919]

looks good. this catches a person's attention since anything in RED needs attention so it's easier to see that the app isn't tracking

…

On Tue, Jul 9, 2024 at 9:56 AM Urban Biker ***@***.***> wrote: The latest version (v8.12) contains a "hidden" switch to enable this alternative status bar behavior: On the *Settings > Advanced* screen, long tap the topmost box (please see the screenshot attached). A simple true/false will be the output to indicate the current status. Not sure if it is better than the default status bar behavior, but we could at least make it a regular option if you're convinced it would be useful? Ub_hidden_switch.png (view on web) <https://github.com/Sublimis/UrbanBiker/assets/3844660/03d6ba1c-4e04-437d-be9d-00b22335dbdd> — Reply to this email directly, view it on GitHub <#204 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABINB7ZLYZJIJYURVQR4XODZLPTYRAVCNFSM6AAAAABIEWCDV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJXHAYTMMBYHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>