As a file without source it looks suspicious at first glance for someone not familiar with Gradle. Adding a short explanation with link to the verification process would've been beneficial.

https://docs.gradle.org/current/userguide/gradle_wrapper.html#wrapper_checksum_verification

I'm using android 11 Build RQ3A.211001.001. This had been a problem for a while, normally showing up after charging the phone. In the past rebooting the phone would fix the problem but now lock will not function unless i give it "accessibility" access to the phone. I don't know if this is a problem but it didn't need it before and I would think locking the screen wouldn't take special access (but what do i know). I'm using lock 1.4.1 installed from F-Droid. I updated from 1.4.0 to see if it fixed the issue.

Would it be possible to have the app turn off the screen without necessarily (according to system settings) immediately locking?

The app stops to work regularly. See Screenshot.
Also the screen becomes a "screenshot" of the current screen with a border around it.
I tried to make a screenshot, but the file ended up being all black only.

Your app does not come up if it was not in foreground...If I close the app and then lock the phone, and then unlock phone your app does not show up.

Hello! This is the perfect app for me, I love to lock the screen by tapping a button. I looked for an open source option and found it. Congratulations to the developers.

I have a suggestion for a future update: the option of a minimalist icon with a black background for those using amoled screen and black wallpaper. It would be a few pixels less wasting battery. If someone could do this it would be perfect for my use. Thanks.

Note: I don't know if I sent this in the right channel, this is my first time using GitHub.

Fingerprint/face unlock is disabled after locking phone with Lock app, which is quite inconvenient. As a workaround, some apps (OFF+, for example) just turn the screen off and disable key events for a few seconds until hardware lock is activated. Would you consider adding this functionality as an option?

Thanks for your Lock app. I use it all the time to lock my phone.

At the moment I have to switch to the home screen, where I can tap the Lock app to lock my phone. I would love to do it with a double tap onto the home button.

If this app becomes an assistant app, I would be able to set it in Settings > Apps > Advanced > Default apps > Assist & voice input.

Do you think, that's possible?

You can add Screenshots for F-Droid, too, if you want.

https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/

https://gitlab.com/snippets/1895688

Consider adding notification shade widget. It is crucial for locking screen without going to launcher everytime.
Given your app is open, a user can be assured in safety of giving advanced permissions (like accessibility ones) compared to proprietary alternatives that can run who-knows-what in the background.

It is implemented in other similar non-fossa apps as following:

Hi, After installations from f-droid on my old samsung galaxy 4s, running Android version 4.4.2.

I tried to uninstalled but get error message:
Error uninstalling %s. Fail to uninstall due to unkown error.

What can possible be the issue?
Thanks in advance.

Lint errors on translations:

:app:lintVitalRelease/home/krt/src/fdroiddata/build/name.seguri.android.lock/app/src/main/res/values/strings.xml:2: Error: "app_name" is not translated in "it" (Italian) [MissingTranslation]
    <string name="app_name">Lock</string>
            ~~~~~~~~~~~~~~~

   Explanation for issues of type "MissingTranslation":
   If an application has more than one locale, then all the strings declared
   in one language should also be translated in all other languages.

   If the string should not be translated, you can add the attribute
   translatable="false" on the <string> element, or you can define all your
   non-translatable strings in a resource file called donottranslate.xml. Or,
   you can ignore the issue with a tools:ignore="MissingTranslation"
   attribute.

   By default this detector allows regions of a language to just provide a
   subset of the strings and fall back to the standard language strings. You
   can require all regions to provide a full translation by setting the
   environment variable ANDROID_LINT_COMPLETE_REGIONS.

   You can tell lint (and other tools) which language is the default language
   in your res/values/ folder by specifying tools:locale="languageCode" for
   the root <resources> element in your resource file. (The tools prefix
   refers to the namespace declaration http://schemas.android.com/tools.)

1 errors, 0 warnings

I can workaround that locally with echo -e "android { lintOptions { disable 'MissingTranslation'\n\ndisable 'ExtraTranslation' } }" >> app/build.gradle, but instead this should either be fixed on your side or workaround like this on your side as well.