Added an option that allows users to disable the foreground notification / task that keeps the application alive in the background while no torrents are downloading

• Fixed how torrentsFinished() handles verifying torrents are downloading
• Added an option in behavior settings that lets the user disable/enable the keep alive settings
  • When disabled, the notification/task will be removed when all torrents complete their downloads
  • When enabled, previous behavior is retained
• This change does not affect the Shutdown when downloads complete settings

Note, this does not shut the application, it just disables the notification/task that keeps the application running in the background when no torrents are downloading

To avoid overwriting stable versions of the application when testing on production devices, I modified the debug build type to install separately from the release version as well as display a different icon (inverted color) and "DEBUG" at the end of its name to avoid confusion.

No other changes were made but the app name and icon in the AndroidManifest.xml file are based on items in the generated.xml file which get created when gradle builds, so testing release to the store / F-Droid should be done when possible

• Added settings options to set a custom battery percentage to stop downloads at
  • There is a switch preference that is disabled unless you enable the battery control key
    • Enabling this switch pops a dialog that explains that using this feature will consume additional battery
  • There is a seekbar preference that is disabled unless you enable the custom battery control key
    • The range of this preference is 10 - 90 to avoid errors in the math for pausing
    • The textview displaying the value does not update in real time, only after setting the value
• Added logic to the TorrentTaskService to handle not pausing downloads at the regular 15% interval if the custom battery control key is enabled
• Added logic to TorrentDownload to handle pausing downloads when the custom battery control threshold is pased
  • If a user manually resumes a download, it will not automatically pause again until after the threshold is passed again (charged then discharged). This is identical to current behavior

• A user can now type the infohash of a torrent directly into "Add Link" and it will add the torrent
  • Any string not containing the MAGNET_PREFIX or HTTP(S)_PREFIX will automatically attempt to convert to an infohash using the new INFOHASH_PREFIX

The swig().is_listening() does not seem to be checking for what we want it to be checking for when utilizing this notification. The client still has an active session and is listening even though connectivity is offline. Whether that is a defect in their library or abstract behavior, it doesn't seem necessary to use that library for this.

I just did we do in WifiReceiver and check the connectivity of wifi OR cellular to determine if the client is listening. This may break the concept of "isListening" in the app so it may be valuable to rename or create a new method if you feel. I'm not sure what is considered "listening".

Additionally, should we be checking the user's preference for wifi-only to determine what "listening" is in this method? Right now i just check if wifi or cellular is connected, because technically you CAN start a download on cellular manually if you have wifi only on. Please weigh in on this.

Let me know if this looks right to you or if the overhead of constantly creating that connectvitymanager may be negative.

First ver of transl. Gonna check how does it look in-app. Maybe some updates will follow. Otherwise fine app and looking forward for next development.

I make a first PR for kotlin support and have an example for AddLinkDialog. If it's ok to you, I will take effort for converting and refactoring the others.

Feel free to reject if you want to stay with Java.

In AddLinkDialog, the clipboardDialog and clipboardViewModel are not actually used, but I cannot resolve the clip data this time (always get null for primaryClip). I keep them as they are by now as I'm not familiar to ClipboardManager

Within this PR, I haven't enabled Kotlin coroutine yet.

• TorrentTaskService will now verify that all torrent downloads are out of the DOWNLOADING state before attempting to shut down the app
• Added the FLAG_ACTIVITY_CLEAR_TOP flag to the intent to launch MainActivity from AddTorrentActivity
  • The behavior without this causes multiple layers of MainActivity to be created, meaning the app won't fully shut down at shut down, it'll just close the top layer. This change fixes that behavior

Imagine pause is false and the battery is not charging. Then

pause &= !Utils.isBatteryCharging(context);

expands to

pause = pause && !Utils.isBatteryCharging(context);

pause = false && true

pause = false

That is not the expected behaviour.

Now my change will expand to:

pause = false || true

pause = true

That is the expected behaviour.

Created a black theme as an option in the menu. This theme is different than the dark theme in that it uses pure black (#000000). This lets OLED-based screens turn off their pixels in the fully black areas.

• Added the appropriate checks to apply the black themes in all relevant activities
  • Split the Utils.isDarkTheme logic out into a Utils.getTheme method so Utils.isBlackTheme could leverage it as well as future themes
• Defined @color/black as #000000
• Created the appropriate option in the options menu
• Created the appropriate style, leveraging the dark theme where appropriate.
  • I kept the background of popups and dialogs from the dark theme so they can be seen against the black backgrounds they sit on. All text and accent colors are unchanged from the dark theme
• Added the appropriate drawables for the black theme

NOTE: Though I changed it and it seems fine, I do not know what <item name="backgroundBlank">...</item> actually is. If I should be changing that color to something different than the normal background style, let me know.

Android 13 supports themed app icons. This requires that the application provides an adaptive icon, and a monochrome app icon.

This change adds the monochrome icon and modifies ic_launcher.xml to use it.

The monochrome icon is taken from ic_launcher_foreground.xml without the gradient.

In recent years because of the advancement of technology many English words are common in day to day Farsi conversations. One of these words is 'link'. In Farsi the word 'لینک' which is equal to 'link' is more correct word in compare to its translation 'پیوند'. I am a native Farsi speaker, if you need more information about this fill free to contact me.