modelorona / modelorona/TapLock

Quick Settings volume control (to preserve hardware volume buttons)

Open
#24 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
29
Forks
5
Avg merge
12d 13h
Merged PRs (30d)
2

Description

Hello,
First of all, I want to thank you for the wonderful app — it works better than many other lock screen apps out there.

I’m opening this issue to suggest adding a Quick Settings volume control. I’m not sure if this goes against the project’s vision or not, but I’d still like to explain why I’m proposing this feature. I think many people want to use double tap, QS tiles, or widgets to lock the screen because:

  1. It’s more convenient.
  2. It helps extend the lifespan of the physical power button.

The same logic applies to the volume buttons, I’d also like to press them less often physically, especially when I need to adjust the volume frequently.

As for why I’m suggesting this in your app, despite there being many other apps that already offer this feature —
When I started using your app, I noticed that the lock screen you coded responds faster than anything else, and it feels like a real pleasure to use. That’s why I thought that a Quick Settings volume control written by you, by your code (even as a small addition to TapLock) would be a very nice extra.

And yes, this is just a request; the decision is, of course, up to you. Thank you for your attention 😌

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named in the issue. First inspect the Android project for existing Quick Settings and volume-control entry points, then clarify the tile behavior and acceptance criteria before estimating implementation; done should mean the requested control works without relying on hardware volume buttons.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.