You can set TAKE_AUDIO_FOCUS permission of that app to ignore: appops set TAKE_AUDIO_FOCUS ignore Using https://github.com/mirfatif/PermissionManagerX this can be done conveniently for any app: Disclosure: I'm the author of PMX.

You can try Google Family Link App which gives a reasonable informed control over multiple devices.

Instead, use the path Settings> Battery Saver> Extreme Battery Saver> Essential Apps and check the box next to the app you want unrestricted. To use an app while Extreme Battery Saver is on, tap the app that is paused, on the message that shows, tap Unpause temporarily. After a few minutes, you’ll get a notification to pause. To let the app pause again, do nothing or swipe away the notification. To stay unpaused longer, tap Wait until. You can also go into Extreme Battery Saver, tap essential apps, and select that app to be unrestricted when the battery saver is on.

Google Play Store is not necessary for installation or uninstallation of apps. All your installed apps are shown in the app list in Android settings. There you can also uninstall apps. On most Android versions you can also make a long-touch on an app icon on the launcher and then open the App info page where you can uninstall/disable an app.

Android System Recovery "root integrity check" will check your read-only system partition for modifications. If anything is reported, flash memory is either corrupt or something (or someone) had root access and modified stock ROM intentionally. Your device is therefore compromised/corrupted. Flash stock ROM from fastboot. In case you want to modify/delete reported files, read back system.img from SP Flash Tool and loop-mount ext4 partition image on linux PC

The issue was of Permissions - to solve the issue run the following commands in AndroidSU pm grant com.offsec.nethunter android.permission.ACCESS_FINE_LOCATION pm grant com.offsec.nethunter android.permission.ACCESS_COARSE_LOCATION pm grant com.offsec.nethunter android.permission.READ_EXTERNAL_STORAGE pm grant com.offsec.nethunter android.permission.WRITE_EXTERNAL_STORAGE pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_SU pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_NH pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_NH_LOGIN The above commands are given by developer of Nethunter App, @yesimxev you can check the discussion on gitlab - https://gitlab.com/kalilinux/nethunter/apps/kali-nethunter-app/-/issues/306 You can also check this video, https://drive.google.com/file/d/1-5DN66pL2_uk7qzVk8st6l9eiTYSlvPz/view?usp=sharing , to see what was the problem !!

Unpack apk, search and replace the string and repack Also there's an app that can change link behaviour

The Handcent Next SMS app was flagged by Play Protect and taken down from the Play Store on March 26 due to embedding a malicious 3rd-party library and returned on March 30 with an updated, clean version. Timeline On March 26, according https://android.stackexchange.com/users/371073/user223149 while https://android.stackexchange.com/q/246037/44325 , Got this answer from support: Our app Handcent Next SMS has been misidentified as malware by Google, we are in talks with Google to get our app back to play store. [...] Around 1 hour later, this was later confirmed on the official https://www.handcent.com/ , https://twitter.com/Handcent/status/1507549097288380416 , and https://www.facebook.com/handcent/posts/2198804186934782 , Our app Handcent Next SMS has been misidentified as malware by Google, we are in talks with Google to get our app back to play store. [...] https://www.reddit.com/r/androidapps/comments/to1ss4/comment/i26xjel/?utm_source=reddit&utm_medium=web2x&context=3 sent an email to Handcent support and got a reply, I got a reply this morning with an explanation and an attachment with v9.9.9. *Security patch to fix a potential threat *Other fixes to make sure it's in a good safe state I installed it, and so far, so good. [...] Meanwhile, on March 28, Handcent posted an update to the same channels. https://www.handcent.com/ We have resolved the issue, together with Google. The app will return to the play store soon. [...] https://twitter.com/Handcent/status/1508282177926021126 We have resolved the issue, together with Google. It usually takes one day or two. [...]. It’s safer and good to go now. https://www.facebook.com/handcent/posts/2200406613441206 We have resolved the issue, together with Google. The app will return to the play store soon. It usually takes one day or two. [...]. It’s safer and good to go now. On March 30, the app was back on the Play Store with v9.9.9.1. https://www.handcent.com/ also mentions, We are pleased to announce that Handcent Next SMS is back to the Google Play . [...] Handcent also followed up on their social media on March 31. https://twitter.com/Handcent/status/1509374817752952832 Next SMS is now back on the play store, you could go to the play store and install it. [...] https://www.facebook.com/handcent/posts/2202641403217727 Next SMS is now back on the play store, you could go to the play store and install it. [...] Those who sent an email might also receive a follow-up reply mentioning the app version on the Play Store, Next SMS is now back on the play store, you could go to the play store and install it 9.9.9.1. [...] Cause I decided to send an email to Handcent Support and received the v9.9.9 APK file, then also downloaded the APK for v9.9.9.1 after it was published on the Play Store. After decompiling and comparing the content with v9.9.8.6 and v9.9.8.5, one noticeable thing is the removal of coelib.c.couluslibrary since v9.9.9 (including v9.9.9.1 from the Play Store). AppCensus published a blog article written by Joel Reardon on April 6, titled https://blog.appcensus.io/2022/04/06/the-curious-case-of-coulus-coelib/ . It explained what and how this library worked in detail. Quoting a relevant part about this specific incident, Disclosure The following table are the apps that we confirmed communicating with mobile.measurelib.com. We reported this issue to Google on October 20th, 2021 along with this list of apps. They investigated it and removed these and other apps containing the SDK from the Play Store. [...] App Name Privacy Policy Installations phone email IMEI GPS router SSID router MAC [...] [...] [...] [...] [...] [...] [...] [...] [...] https://play.google.com/store/apps/details?id=com.handcent.app.nextsms https://web.archive.org/web/20220118151158/https://www.handcent.com/static/%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20ApplicationPrivacyStatement.html 1 million+ no yes yes no yes yes [...] [...] [...] [...] [...] [...] [...] [...] [...] (Emphasis added) An article from Android Police published on April 7, titled https://www.androidpolice.com/google-play-store-boots-data-harvesting-software-intelligence/ also stated, Still, there is some hope for those who have lost income streams from Google's ban. The company may allow some apps to return — as long as they delete the Measurement Systems code. The first few are in fact already back.

Remove the drivers for any OTHER peripherals from the linux kernel used in your AOSP build..... I don't know how is it done etc refer to the linux documentation as well as AOSP documentation to figure it out

By design*, the application cannot access the external storage if it does not have the READ_EXTERNAL_STORAGE permission granted. Allowlisted means that the permission is granted to the application. Probably medial and aural collection are the defaults medias for ringtones or notifications ( https://developer.android.com/reference/android/provider/MediaStore.Audio.AudioColumns#IS_RINGTONE or https://developer.android.com/reference/android/provider/MediaStore.Audio.AudioColumns#IS_NOTIFICATION ) as no special permission is needed to be accessed. By design*: Supposing that the application does not exploit a vulnerability on the Android system.

If the app does not disallow backup in it's AndroidManifest.xml then you should able to retrieve the data using adb backup. Some older apps make use of key/value storage which is not included in backup by default. To include this data change the adb backup command to: adb backup -keyvalue -f oilchangesBackup.ab com.cooly.OilChangeSchedulePro Just make sure to use the correct packageName of the app because if you make a typo the backup file will be empty.

In the 'Res' directory after decompiling

Android apps can only access some resources if you explicitly give permissions for that. One app can request this permission, but you are free to give it or not, and even to revoke that permission in a later moment. These are the permission types you can give: Body sensors: Get sensor info about your vital signs. Calendar: Use your default calendar. Call logs: Access and change your call history. Camera: Use your camera to take pictures or videos. Contacts: Access your contacts list. Location: Gets your device’s location. Learn about location settings. Microphone: Record audio. Nearby Bluetooth devices: Apps can discover and connect to nearby devices. Phone: Make and manage phone calls. Physical activity: Get info about your activity like walking, biking, step count, and more. SMS: Access incoming and send outgoing text messages. Storage: Get photos and other files on your phone. Files and media: Use photos, media, and other files on your phone. If you want, for instance, to revoke the microphone or camera access from all apps in your device, follow these steps: On your phone, open the Settings app. Tap Privacy. Turn off Camera access or Microphone access. The same thing can be done for your storage, for instance... https://support.google.com/android/answer/9431959?hl=en#zippy=%2Ctypes-of-permissions%2Cdisable-camera-or-microphone-access-on-your-device

I totally understand your concern but there's nothing you can do for this. Your telecom operator is doing the whitelisting (of those apps) on their end; there's nothing you can do as a client.

This is a Color OS bug with Android 11. Me too facing this since a few days so can confirm.

Here's the methods you can use to set custom time for specific apps: Xposed Hook - You can use Xposed modules that hook into date time functions inside the app. Everytime the app requests date time the module returns custom data. AppSettings, Xprivacy, Xprivacy Lua are few well known modules. (For using Xposed without root you can use taichi / virtualXposed) Frida Hook - Just like Xposed you can hook date time methods to return different data. I cannot find an example of this, but it's very possible. Patch Smali - You can decompile the apk and patch all date time calls with constant values. So it returns same date and time. Some thrid party cloner apps do this for you with nice GUI.

I hate to possibly be the bearer of bad news, but that is the exact same icon that appeared after i accepted a "system update" which sadly was NOT what it claimed. It's odd that the icon remains on your homescreen though so it may be something harmless. You can read about it here https://blog.malwarebytes.com/cybercrime/mobile/2021/04/android-system-update-malware-steals-photos-videos-gps-location/

For privacy reasons fingerprints images can never be accessed by Android apps. The following text is about Google Nexus/Pixel phones, but as far as I know it also applies to phones of other manufacturer: Your fingerprint data is stored securely and never leaves your Pixel or Nexus phone. Your fingerprint data isn't shared with Google or any apps on your device. Apps are notified only whether your fingerprint was verified. https://support.google.com/pixelphone/answer/6300638 The reader is only usable by Android itself for authentication. As an app developer you can only ask Android to perform an authentication and in the end get the result (success/failure).

To close this issue: Thanks for the suggestions: @alecxs: The https://f-droid.org/en/packages/org.pocketworkstation.pckeyboard works great, and as it can represent a full keyboard, it feels very familiar. On screen portrait mode it's a bit more difficult to use though. @IrfanLatif: https://github.com/mirfatif/AnySoftKeyboard looks very promising as it's easier to use in portrait mode and has better access for foreign languages.

The recent version of Slack v22.01.11.0 for Android I can see on https://apkpure.com/de/slack/com.Slack defines in it's AndroidManifest.xml android:minSdkVersion="26" so this app requires at least Android 8.0. The Galaxy S6 comes (according to https://www.gsmarena.com/samsung_galaxy_s6-6849.php ) with Android 5.0.2 (Lollipop), upgradable to Android 8.0 (Oreo). So if your device is fully upgraded to Android 8 you should be able to install Slack from https://play.google.com/store/apps/details?id=com.Slack or from a web site that provides the APK like https://apkpure.com https://apkmirror.com ...