cospravit.txt

--------------------------------
Hadanie warningov v kode:
Toto hladaj:
@SuppressLint
@SuppressWarnings
//noinspection

------------------

Ked nejde git push, skus v terminaly AS:
git config credential.helper store

--------------------------------

Preco uz nie je PPP v GPlay:

Google restrictions:
1. Android - All Wi-Fi related functions not working since Android 10.
2. Google Play - Google require (currently) Android 10+ for applications. In application exists gradle configuration parameter:
    targetSdkVersion targetSdk
  and in PPP must be target sdk = 28. Android 10 is 29.

In stores, in which is currently deployed PPP, restriction about target sdk not exists.

----------------------------------------

indicator color and its complementary color:
dark tema: indicator:62a9f8 -> accent:f8b162 -> event delay:#F862F4
light tema: indicator:4289d8 -> accent:cc893e -> event delay:#D842D4

https://www.canva.com/colors/color-wheel/

------------------------

Widget Preview Builder:
https://play.google.com/store/apps/details?id=lav.widgetpreviewbuilder.free&hl=en_US&gl=US

------------------------

Ulohy, ktore su spravene [x] a ktore nie [ ]:
[ ] Priority Notification Event
[x] Normal media volume, headphone media volume, Bluetooth media volume
[ ] Sony's "Stamina" mode as profile preference - skor Power save change senzor
[ ] USB connection to PC as storage device, USB connection to PC as camera, connection to USB stick in accessories parameter for events
[ ] option to hide PPP from Launcher
[ ] Set min and max CPU frequency
[ ] Open a website with profile
[ ] profile/event search
[x] Persistent profile/event: sets its options every x minutes - asi periodic sensor
[ ] Android Wear support?
[ ] (AND, OR, XOR, NOT. Or at least NOT.)<-NOT is already available in most preferences. If that stays, that does the same.
[ ] a plugin system? (very small core app, ability to install additional event preferences, maybe only time event preinstalled)

------------------------

System.Settings:
notifications_use_ring_volume ---+--> ze by na odlinkovanie zvonenia a notifikacii?
unlink_volumes_together ---------+
mute_streams_affected
mode_ringer_streams_affected

System.Global:
heads_up_notifications_enabled

Ako disablovat lockscreen, 2 kroky:
1. nastavit, ze power tlacitko nema lockovat
  /data/system/locksettings.db - lockscreen.power_button_instantly_locks (0,1)
  len je otazka, ci toto existuje aj na starsich androidoch ako 5.0
2. nastavit lockscreen timeout 
  Settings.Secure - lock_screen_lock_after_timeout (milisekundy)

---------- PIN/password

1. ako zrusim pin/heslo

deviceManager.setPasswordMinimumLength(compName, 0);
boolean result = deviceManager.resetPassword("", DevicePolicyManager.RESET_PASSWORD_REQUIRE_ENTRY);

2. ako nahodim pin/heslo

DevicePolicyManager deviceManager = (DevicePolicyManager)getSystemService(Context.DEVICE_POLICY_SERVICE);
ComponentName compName = new ComponentName(MessageService.this, LockAdmin.class);  

boolean active = deviceManager.isAdminActive(compName);  

if (active) { 
  deviceManager.setPasswordQuality(compName,DevicePolicyManager.PASSWORD_QUALITY_UNSPECIFIED);
  deviceManager.setPasswordMinimumLength(compName, 5);

  boolean result = deviceManager.resetPassword("blablabla", DevicePolicyManager.RESET_PASSWORD_REQUIRE_ENTRY);
}

3. password quality:

DevicePolicyManager.PASSWORD_QUALITY_SOMETHING - pattern lock?
DevicePolicyManager.PASSWORD_QUALITY_BIOMETRIC_WEAK - tvar, odtlacok prstu?
DevicePolicyManager.PASSWORD_QUALITY_NUMERIC - pin?
DevicePolicyManager.PASSWORD_QUALITY_ALPHABETIC - heslo?
DevicePolicyManager.PASSWORD_QUALITY_ALPHANUMERIC - heslo?
DevicePolicyManager.PASSWORD_QUALITY_COMPLEX - heslo?

--------------------------------

Direct boot:
- Asi nemozem spravit, nepodporuje to WorkManager. :-(
- toto je super na to, aby sa PPP startol aj pri uzamknutej obrazovke.
- android.intent.action.LOCKED_BOOT_COMPLETED vid:
    https://medium.com/@jordan_shifter/direct-boot-on-android-nougat-71f06c4a7c9e
- Ak nepuzijes direct boot, tak apka pada napr. v Fabric, android_job.
  To preto, lebo chcu pouzivat shared preferences a v uzamknutej obrazovke bez direct boot
  to spadne na IllegalStateException.

  Fabric, android-job uz nepouzivam, treba testnut s Firebase Crashlytics a WorkManager

- Ako spravit podporu Direct boot:
    https://developer.android.com/training/articles/direct-boot

- Len mam taky strasne blby pocit, ze neviem ako movnut shared preferences z device do credential storage.
  Vid:
    https://developer.android.com/reference/android/content/Context#moveSharedPreferencesFrom(android.content.Context,%20java.lang.String)
    https://developer.android.com/reference/android/content/Context#moveDatabaseFrom(android.content.Context,%20java.lang.String)
  Alebo, ze by pomohlo toto?
    https://stackoverflow.com/questions/51377089/android-crashlytics-fails-on-direct-boot-due-to-disk-encryption

------------------

ActivateProfileHelper.setScreenTimeout()
- disableScreenTimeoutInternalChange = true;
- pre kazdy timeout z parametra:
	if (PPApplication.lockDeviceActivity != null)
	    // in LockDeviceActivity.onDestroy() will be used this value to revert back system screen timeout
	    PPApplication.screenTimeoutBeforeDeviceLock = 15000;
	else {
      	    Settings.System.putInt(appContext.getContentResolver(), Settings.System.SCREEN_OFF_TIMEOUT, xxx);
      	}
- nerobi 6, 8. Preco?
- zavola:
        setActivatedProfileScreenTimeout(appContext, 0);
- zavola work:
	DisableScreenTimeoutInternalChangeWorker.class

- volane z:
  - ActivateProfileHelper.execute() - aktivacia profilu ak je obrazovka zapnuta
  - LockDeviceActivity.onDestroy() - na nastavenie timeoutu, ak sa este nenastavil
  - ScreenOnOffBroadcastReceiver.onReceive() na ACTION_USER_PRESENT

ActivateProfileHelper.setActivatedProfileScreenTimeout()
- ulozi do shared preferences timeout.
- ulozi to aj do ApplicationPreferences.prefActivatedProfileScreenTimeout
- pouzije to v ScreenOnOffBroadcastReceiver.onReceive() na ACTION_USER_PRESENT
- pouzije to aj v LockDeviceActivity.onDestroy() na vratenie timeoutu

- volane je z:
  - ActivateProfileHelper.setScreenTimeout() - nastavi 0, lebo netreba nastavovat na screen On ACTION_USER_PRESENT
  - ActivateProfileHelper.execute - nastavi profile parameter _deviceScreenTimeout, ak je screen off
  - SettingsContentObserver.onChange() - nastvi 0 ak posledny zapamatany timeout je iny ako aktualny. a  nie je to internalChange
                                                  ActivateProfileHelper.disableScreenTimeoutInternalChange
                                         to aby sa nepouzila na ten screen On ACTION_USER_PRESENT. Tu sa predpoklada, ze zmena prisla z vonka.

premenna PPApplication.screenTimeoutBeforeDeviceLock:
- tu si pamatam, aky timeout je pred spustenim LockDeviceActivity.
- na onCreate() ho zistuje
- na onDestroy() nastavi spat timeout na tuto odpamatanu hodnotu
- na onDestroy() potom nastavi timeot na hodnotu ApplicationPreferences.prefActivatedProfileScreenTimeout.


Takto sa nastavuje tiemout pri aktivacii profilu:
        // screen timeout
        if (Permissions.checkProfileScreenTimeout(appContext, profile, null)) {
            if (PPApplication.isScreenOn) {
                if (PPApplication.screenTimeoutHandler != null) {
                    PPApplication.screenTimeoutHandler.post(() -> {
                        setScreenTimeout(profile._deviceScreenTimeout, appContext);
                    });
            }
            else {
                setActivatedProfileScreenTimeout(appContext, profile._deviceScreenTimeout);
            }
        }
- cize ak je screen on, nastavi sa timeount hned.
- ak je screen off, nastavi sa timeount az v ScreenOnOffBroadcastReceiver.onReceive() na ACTION_USER_PRESENT
  cize len sa hodnota ulozi do ApplicationPreferences.prefActivatedProfileScreenTimeout.
Toto cele chapem.

-----------------------

Zmena hlasitosti profilom:

Toto su parametre:
forRingerMode -> true, ak menim aj ringer mod?
- ak profil meni ringer mod, ton zvonenia, notifikacie, systemu, DTMF, tak je true
- inac je false
forProfileActivation -> true ak volam pre aktivaciu profilu?
- ak je volane z ActivateProfileHelper.execute(), je true, cize ano ide o aktivaciu profilu
- ak je volane z PhoneCallListener.setLinkUnlinkNotificationVolume() je false, cize je to pocas hovoru
  aby sa vykonal unlink.

setRingerVolume(appContext, profile.getVolumeRingtoneValue()); -> pozri co za premennu to nastavuje
- ApplicationPreferences.prefRingerVolume
  meni sa pri starte PPP, pri aktivacii profilu, pri zmene hlasitosti zvonenia v systeme
setNotificationVolume(appContext, profile.getVolumeNotificationValue()); -> pozri co za premennu to nastavuje
- ApplicationPreferences.prefNotificationVolume
  meni sa pri starte PPP, pri aktivacii profilu, pri zmene hlasitosti notifikacii v systeme
  meni sa aj na hlaitost zvonenia pri unlinku, podla mna preto, lebo v podstate je len 1 volume
  pri zmerovananych hlasitostiach, tak nech su rovnake.

-> Len ak je system ringer mode audible, alebo ak ApplicationPreferences.prefRingerMode=0
-> ringerMode == 0 znamena, ze je nenastaveny. Ide o ringer mod podla Profile.RINGERMODE_*
if (isAudibleSystemRingerMode(audioManager, systemZenMode/*, appContext*/) || (ringerMode == 0)) {

...

  -> tu zistujem ci ma zlinkovane (merged) ringing a notificartion
     vrati to:
       if (ApplicationPreferences.applicationForceSetMergeRingNotificationVolumes > 0)
         ApplicationPreferences.applicationForceSetMergeRingNotificationVolumes == 1
         - cize ak je natrdo v Settongs, ze ma zmergovane
       else
       	 ApplicationPreferences.prefMergedRingNotificationVolumes
     cize v podstate bud ak uzivatel nastavil natvrdo, ze ma zmergovane alebo a detekcia vratila, ze ma zmergovane
  if (ActivateProfileHelper.getMergedRingNotificationVolumes() &&
      ApplicationPreferences.applicationUnlinkRingerNotificationVolumes) {
    -> ma zmergovane a ma zapnuty unlink
    ...
  } else {

    -> tu zistujem ci ma zlinkovane (merged) ringing a notificartion
       vrati to:
         if (ApplicationPreferences.applicationForceSetMergeRingNotificationVolumes > 0)
           ApplicationPreferences.applicationForceSetMergeRingNotificationVolumes == 1
           - cize ak je natrdo v Settongs, ze ma zmergovane
         else
         	 ApplicationPreferences.prefMergedRingNotificationVolumes
       cize v podstate bud ak uzivatel nastavil natvrdo, ze ma zmergovane alebo a detekcia vratila, ze ma zmergovane
    if (!ActivateProfileHelper.getMergedRingNotificationVolumes()) {
     -> nie je zmergovane
      ...
      -> nastavuje hlasitost notifikacie, ale z ApplicationPreferences.prefNotificationVolume
         nastavi sa hore na zaciatku
      volume = ApplicationPreferences.prefNotificationVolume;
    }

    -> nastavuje hlasitost zvonenia, ale z ApplicationPreferences.prefRingerVolume
       nastavi sa hore na zaciatku
    volume = ApplicationPreferences.prefRingerVolume;
    -> zapisuje sa aj do servisu, NACO?
    PhoneProfilesService.getInstance().ringingVolume = volume;
  ...

  }
...

}

    static void getMergedRingNotificationVolumes(Context context) {
        synchronized (PPApplication.profileActivationMutex) {
            ApplicationPreferences.prefMergedRingNotificationVolumes =
                    ApplicationPreferences.getSharedPreferences(context).getBoolean(PREF_MERGED_RING_NOTIFICATION_VOLUMES, true);
        }
    }
    static boolean getMergedRingNotificationVolumes() {
        if (ApplicationPreferences.applicationForceSetMergeRingNotificationVolumes > 0)
            return ApplicationPreferences.applicationForceSetMergeRingNotificationVolumes == 1;
        else
            return ApplicationPreferences.prefMergedRingNotificationVolumes;
    }

Ak v Settings menim ringtone na Pixeli, meni sa STREAM_RING aj STREAM_NOTIFICATION
Ale ako pozeram, tak sa to ignoruje, tie zmeny v observeri, lebo prave aktivujem porfil.
To je to, co to ma aj robit.
Tak preco kua to na tej Xperii robi inac? Jedine mi zostava to testnut u Marta. Logovat si to.

------------------

Night mode - cize zlty film:
Pozeraj toto:
/home/henrisko/Stiahnuté/Tweaker-master/app/src/main/java/com/zacharee1/systemuituner/views/NightModeView.kt
/home/henrisko/Stiahnuté/Tweaker-master/app/src/main/java/com/zacharee1/systemuituner/services/tiles/NightModeTile.kt
/home/henrisko/Stiahnuté/Tweaker-master/app/src/main/java/com/zacharee1/systemuituner/prefs/NightModePreference.kt

Je to aplikacia SysteUI Tunner. Mas ho v S10.

--------------

Night light (blue light filter):

Vypada to, ze takto sa to robi:

if (isActive) {
    if (Build.VERSION.SDK_INT == Build.VERSION_CODES.N) { // API 24, ale skontroluj
        prefManager.saveOption(SettingsType.SECURE, "twilight_mode", 0)
        writeSecure("twilight_mode", 0)
    } else {
        prefManager.saveOption(SettingsType.SECURE, "night_display_activated", 0)
        writeSecure("night_display_activated", 0)
    }
} else {
    if (Build.VERSION.SDK_INT == Build.VERSION_CODES.N) { // API 24, ale skontroluj
        prefManager.saveOption(SettingsType.SECURE, "twilight_mode", 1)
        writeSecure("twilight_mode", 1)
    } else {
        prefManager.saveOption(SettingsType.SECURE, "night_display_activated", 1)
        writeSecure("night_display_activated", 1)
    }
}

fun Context.writeSecure(key: String?, value: Any?): Boolean {
    if (key.isNullOrBlank()) return false
    return try {
        Settings.Secure.putString(contentResolver, key, value?.toString())
        true
    } catch (e: SecurityException) {
        false;
    }
}

const val TWILIGHT_MODE = "twilight_mode"
const val NIGHT_DISPLAY_ACTIVATED = "night_display_activated"
const val NIGHT_DISPLAY_AUTO_MODE = "night_display_auto_mode"
const val NIGHT_DISPLAY_COLOR_TEMPERATURE = "night_display_color_temperature"
// tiet dve este musim zistit, ci vobec vie nastavit.
// v aplikacii to nie je
const val NIGHT_DISPLAY_CUSTOM_START_TIME = "night_display_custom_start_time"
const val NIGHT_DISPLAY_CUSTOM_END_TIME = "night_display_custom_end_time"

// pre API 24
writeSecure(NightModeView.TWILIGHT_MODE, info.twilightMode)

// pre API 25+
writeSecure(NightModeView.NIGHT_DISPLAY_ACTIVATED, info.nightModeActivated)
writeSecure(NightModeView.NIGHT_DISPLAY_AUTO_MODE, info.nightModeAuto)
writeSecure(NightModeView.NIGHT_DISPLAY_COLOR_TEMPERATURE, info.nightModeTemp)

Zdroj: https://github.com/zacharee/Tweaker/blob/master/app/src/main/java/com/zacharee1/systemuituner/services/tiles/NightModeTile.kt

Bude potrebovat WRITE_SECURE_SETTINGS.
Testovane cez System UI Tuner s grantnutym WRITE_SECURE_SETTINGS na Pixel 3a.

---
Testni to potom este na Samsungu, ci to ide. Neviem, niekde som cital, ze to zhasne obrazovku
a pomoze len restart mobilu. Len neviem ci to bolo pri tomto.
!!! Hm, tak ako som pisal. Na Samsungu to zhaslo obrazovku.
!!! Aj ked zmenim len automaticke zapinanie.
!!! Takze toto urcite nemozem spravit.
!!! Ale? Mozno System UI tuner zapise len pri zmene automatiky aj to zapnutie. A to je mozno problem.
!!! Testni, testni testni.

Mozno taky test tam dat, ze nech si uzivatel skusi a za par sekund vrati, teda ak to pojde.
Vyskusaj aj to. Testuj na Galaxy S10.
Ak to vrati, tak potom to sprav tak, ze uzivatel musi cez test dako prejst. A len ak potvrdi
(najlepsie 2x) ze to nezhaslo obrazovku, tak to nastav ako povolene.

Cize sprav na to dialog s tymi 3 parametrami:
1. nemenit/zapnut/vypnut
2. automaticke zapinanie
3. teplota farby
4. Test tlacitko a len ak ho potvrdi, tak povolit OK.
   To s tym OK, to treba ten preference spravit dako inac nez obycajne.
   S pouiztim public Dialog onCreateDialog(Bundle savedInstanceState)
---

Toto je, ked to hore nepojde. Cize zavolanie Settings. Take uz mam pri nejakych parametroch profilu:

ACTION_NIGHT_DISPLAY_SETTINGS

Zdroj: https://developer.android.com/reference/android/provider/Settings#ACTION_NIGHT_DISPLAY_SETTINGS

Sprav aspon toto, lebo na Galaxy mi to hore vyplo obrazovku. :-(

------------------

EventsHandler.handleEvents()
- volane strasne vela krat zaujima ma restart udalosti a samotny orientacny senzor
- SENSOR_TYPE_DEVICE_ORIENTATION
  - z OrientationScanner.runEventsHandlerForOrientationChange() - zisti, aky thread to pouziva
  - z PPPExtenderBroadcastRecveiver.onReceive() - je to volane v HandlerThread - vroadcast treba, lebo senzor sleduje aplikacie na popredi

------------------------

Orientation sensor:
Light senzor sa generuje hrozne casto. Na Samsungu donekonecna a par krat za sekundu.
Spravil som sice:
- ze sa neregistruje, ak ziadna udalost ho nepouziva
- ze sa ma handler volat az o polovicu intervalu
Ale aj tak to musi zrat vela. Kazdych 5 sekund volat eventsHandler je proste vela.
Zatial mam nenapadlo, co s tym. Do nastaveni senzora daj aspon info preference o tom ze check light zerie bateriu.

-----------------------

Treba pravo SYSTEM_ALERT_WINDOW pre (od API 29) - HOTOVO:
- doExecuteForRunApplications()
- PREF_PROFILE_DEVICE_MOBILE_DATA_PREFS
- PREF_PROFILE_DEVICE_NETWORK_TYPE_PREFS
- profile._deviceLocationServicePrefs
- profile._deviceWiFiAPPrefs
- profile._deviceVPNSettingsPrefs
- profile._deviceWallpaperChange
- profile._deviceVPN
- profile._deviceCloseAllApplications
- Permissions.grantPlayRingtoneNotificationPermissions()
- ActivateProfileHelper.putSettingsParameter() - cize zavolanie PPPPS

Toto neviem, mozno treba, mozno nie: netreba
- CustomACRAEmailSender.send()

-----------------------

6.4:
- Add: Added support for Shizuku for some profile parameters which requires ROOT.
- Change: Event priority displayed in Editor as sensor, also with pass status.
- Change: Added "Do Not Use" event priority. This event will be started, even when is running event with higher priority.
- Change: Added filter into contacts dialog.
- Change: Added special dialog for "Draw over apps" permission with link to web page with solutions, when is not possible to grant this permission.
- Change: Added button about installation from GitHub in Extender installation dialog, when installation is from Galaxy Store. Because Galaxy Store requires Samsung Account.
- Change: For activation of profile from Activator: direct open of profile preferences, if in it are some errors.
- Change: Changes in check for latest Extender and PPPPS version and installation of dialogs.
- Change: Updated Features in README.md.
- Fixed bugs
- Updated translations

-------------------

java.lang.IllegalStateException: You are adding too many system settings.
You should stop using system settings for app specific data package: sk.henrichg.phoneprofilesplus

Tato exception nie je sposobena tym, ze uz je prilis vela veci nakonfigurovanych v profile?
Neviem kedy sa nastavuje pocitadlo. Ze by to bola vec threadu? Lebo vsetko v ActivateProfileHelper
volam v jednom threade.

Raz uz mi toto vzniklo aj pri inom parametri, ktory by nemal byt null, takz enull to nie je:
PHONE_MODEL=SM-A145P
BRAND=samsung
at sk.henrichg.phoneprofilesplus.ActivateProfileHelper.execute(ActivateProfileHelper.java:4838)
 Settings.System.putInt(appContext.getContentResolver(),
                                        Settings.System.SCREEN_BRIGHTNESS,
                                        profile.getDeviceBrightnessManualValue(appContext));
Tu sa nahadzuje integer takze profile.getDeviceBrightnessManualValue(appContext) nevrati null.

Mozno sa to uvolnuje postupne, ako to nahadzuje do db. Tak mozno to ani nie je vec threadu, ale package.
Proste prilis vela veci naraz menim. Sa to cachuje Ako ale toto vyriesit? Hm, hm.

HOTOVO tak, ze zapisujem len ak uz taha hodnota nie je zapisana. To by mohlo dost zmensit pocet zapisov.

--------------------------

NFC senzor:

Aplikacia NFC Tags:
- zapisuje tag takto:
  - DATA: com.miui.calculator
  - FORMAT: External (04) = NfcRecord.TNF_EXTERNAL_TYPE
  - TYPE: android.com:pkg
  - PAYLOAD: com.miui.calculator
Aplikacia NFC Tasks okamzite spisti Kakulacku, ziaden sys dialog, ci tag precitat sa nezobrazi.

PPP:
- zapisuje tag takto:
  - DATA: hhh
  - FORMAT: Media (02) = NdefRecord.TNF_MIME_MEDIA
  - TYPE: application/vnd.phoneprofilesplus.events
  - PAYLOAD: hhh
Dialog sa zobrazuje.

No a teraz otazka: preco sa zobrazuje ten hnusny dialog?

Skus teda pouzit tiez External.
Ako spravit Intent + ako spravit NdfeRecord:
https://developer.android.com/develop/connectivity/nfc/nfc#ext-type

-------------------------------------

Profil a novy parameter "Block phone calls"

Ak je role nastavene, uz nefunguje jeho znovu-nastavenie, nozbrazuje sa ten bottom sheet na to.
Ide len zrusit v Settings "Caller ID & spam app".
Ak je nastavena ina apka ako PPP, zobrazi sa bottom sheet, takze toto je OK.
Ako postupovat:
1. ak je nastavene PPP, disablovat tuto volbu HOTOVO
2. zobrazovat v summary stav, cize k tomu, co tam uz je dat pred to este stav. HOTOVO

Treba permission na tie kontakty. Contacts.
Samotny contacts a groups dialog, pyta pravo. Je volane: Permissions.grantContactsDialogPermissions(prefContext).
Cize treba uz iba klasicky ako u inych parametroch. HOTOVO

Treba este zistit, ci netreba dake dalise pravo.
Ak bude treba, treba este dorobit Phone permission pre:
<uses-permission android:name="Manifest.permission.ANSWER_PHONE_CALLS" />
<uses-permission android:name="Manifest.permission.CALL_PHONE" />
NETREBA, testnute.

A pridaj ešte contact list type, ako je v call senzore.
No ale tuto nie je dobra vec, davat tam EventPreferencesCall.CONTACT_LIST_TYPE_NOT_USE.
Prilis kriticke je toto blokovanie. Ta hodnota by znamenala, ze kazdy jeden hovor by to blokovalo.
HOTOVO

Import/Export
- kontakty treba zakriptovat, pozri to u udalosti
- kontakty treba dat, ze ich nechcem do backupu, je na to aj dialog, ten treba tiez upravit
HOTOVO

"Block phone calls" -> treba spravit indikator HOTOVO

V servise nesmies blokovat, ak kontakty nie su nastavene. HOTOVO

-------------------------------

Volane: restartEventsWithRescan()
DataWrapper:
- stopEventsForProfile() - false - kedy volane? - daj true, je to volane z EditorProfileListFragment.deleteProfile()
- startEventAtFirstFtart() - false 2x - kedy volane? - nastav podla toho odkial je volane, cize pridaj parameter manualRestart

EventStatic:
- runStopEvent() - false - kedy volane? - daj true, je to volane len z GUI

RestartEventsWithDealyWorker:
- doWork() - false = kedy volane? - nastav podla dat z workera

TimeChangedReceiver:
- doWork() - false - kedy volane? - daj true, sice znova zacne duration, ale nevadi, toto je volane len na zmenu time zony

---

Volane: restartEventsWithDelay()
EditorEventListAdapter:
- clearView() - false - kedy volane? - daj true, je to volane pri manualnom presuvani itemov eventov v Editore

GrantPermisionActivity:
- finishGrant() - false - kedy volane? - daj true vo vsetkych pripadoch, je to volane ked monci grant, ktory je bud z Editora alebo z notifikacie

PPExtenderBroadcastReceiver:
- onReceive() 0 false - kedy volane? - daj true, volane len raz, ked sa nakonektuje Extender

------------------
- Add: Added "Application run duration" into "Application sensor".
- Add: "Phone calls" parameter for block calls.
- Add: New senzor "Music sensor" to detect music playing.

- Change: Fixed not working click to notification about new PPPPS version.
- Change: Fixed not working notification about new PPP version.
- Change: Increased delay between set sound mode and volumes.
- Change: Fixed not working change of volume in DND Priority in Motorola.
- Change: Better summary for profile parameter "Generate notification".
- Change: Removed Galaxy Store form README.md.
- Change: Removed Important info about Galaxy Store end of support.
- Change: Fixed not working change of ringing volume when is set Priority DND, in all devices with Android 14+.
- Change: Airplane mode parameters as sub-screen.
- Change: Set wifi/on using "svc wifi" command, which do not generates prompt (HyperOs).
- Change: Better notification channels descriptions.
- Change: Bypass DND for some notifications.
- Change: Set "Package name" as required for custom "Action" + "Broadcast".
- Change: Displays toast from "Test" button for test of broadcast intent in Intent editor.
- Change: Fixed show Important info about required versions of PPPE, PPPPS at PPP start.
- Change: Installation of PPPPutSettings with InstallWithOptions.
- Change: Profile parameter name "Lock screen" to "Unlock device".
- Change: Added "Image wallpaper for lock screen" into profile "Change wallpaper".
- Change: Disable "Wifi hotspot" SIM is not inserted.
- Change: Disable "Default SIM card" if SIM is not inserted.
- Change: Check more than 2 SIM cards in some profile/event parameters
- Change: Allowed activation form event for end of duration "Activate default profile".
- Change: Allowed activation from event for end of duration "Undo the profile"
- Change: Allowed activation from event for end of duration "Restart events"
- Change: Save activated profile to FIFO when is activated manually.
- Change: Added (Z) information into Important info for profiles.
- Change: HyperOs - disable Wi-Fi, Bluetooth ON/OFF ask dialogs with appops command.
- Change: Change wallpaper: added recycle() for bitmaps after set wallpaper.
- Change: Change wallpaper in MIUI. Added info for not working good WallpaperManager.setBitmap().
- Change: fixes in manifest file for activities with excludeFromRecents.
- Change: Fixed close of foreground application when night mode is changed from profile.

- Fix: Fixed not working "Screen timeout" in OnePlus. Requires root, Shizuku.
- Fix: Color of row in Activity log.
- Fix: Change wallpaper with "(I) Change to image with".

- Fixed bugs.
- Updated translations.