Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bring back screen lock #6770

Open
freefilesync opened this issue Apr 3, 2019 · 13 comments
Open

Bring back screen lock #6770

freefilesync opened this issue Apr 3, 2019 · 13 comments
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning

Comments

@freefilesync
Copy link

A while ago it used to be possible to lock the screen to ignore touch events.

Like I imagine many people, I use Osmand in a bike phone holder. When it's raining, condensation builds up on the inside and makes Osmand think that it randomly is getting screen touches.

Very annoying, as it makes the map dance around. Can you bring back the little padlock that stops this from happening?

@scaidermern
Copy link
Contributor

According to #1855 this feature has been dropped several years ago (<= 2016).

@freefilesync
Copy link
Author

freefilesync commented Apr 3, 2019 via email

@vshcherb vshcherb added the Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning label Apr 4, 2019
@eindgebruiker
Copy link

Yes please. I use Osmand both on my bicycle and on my motorbike. In the rain Osmand sometimes completely disappears from the screen.

@sonora
Copy link
Member

sonora commented Sep 1, 2021

I think there's apps out there facilitating this and worth looking, at e.g. "Touch Lock - disable your touch screen" (https://play.google.com/store/apps/details?id=com.kidscrape.touchlock.lite).

@Rowin63
Copy link

Rowin63 commented Jan 18, 2022

"Touch lock" is fine, but unfortunately it also blocks Osmand from being operated via bluetooth controller (CI controller)

@habitoti
Copy link

habitoti commented Jun 1, 2022

I think rain is actually the biggest issue with touch devices. An iPhone is perfectly fine with getting wet at all, but raindrops keep generating touches on the display and OSMAND starts doing all sorts of crazy things when riding through heavy rain. What would actually be good is to block the whole display and only release again when operating some side button, like e.g. a volume control.
I wouldn't say it's just nice-to-have. Right now I found it actually to be unusable while I unfortunately had to ride 2h through heavy rain... :-(

@schmadde
Copy link

schmadde commented Jul 8, 2023

For me this is not only "nice to have" but not having this (any more) is a major showstopper and make the whole app unusable in rainy conditions.

@le-martre
Copy link

+1 This happened to me today on my motorcycle, started raining and it's just impossible to keep the navigation working in these conditions without having to take your eyes/hands off the road to readjust. Very necessary !

@floppy-engineer
Copy link

+1 The app HAS motorcycle/bike profiles but they removed corresponding functionality. Not cool (

@sonora
Copy link
Member

sonora commented Oct 15, 2023

It's not trivial to package this universally into OsmAnd. Have you tried specialized Apps like Touch Protector?

@floppy-engineer
Copy link

Nope. I preferred to have only necessary application on my phone. But thanks, I've seen the reference to such type of apps in the tread. I checked such app and I don't like extensive access privileges on it. Maybe it's possible to find a pure app)

@Jasper-Ben
Copy link

+1

Not having this feature makes osmand useless on the bike the moment there is only the slightest bit of rain involved.

Regarding the forementioned thirdparty app I fully agree with @floppy-engineer. I only run FOSS software on my de-googled phone, I don't want to have to rely on a "shady" closed-source app with extended privileges for this functionality.

@Sonwon1
Copy link

Sonwon1 commented Jul 4, 2024

Yes, please bring this back!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning
Projects
None yet
Development

No branches or pull requests