My Samsung Galaxy S8 alerted me that the storage was critically full and may result in data corruption or failure to boot. I immediately deleted some apps to free up 2GB. But I am worried that it may have taken steps without my knowledge, such as clearing / disabling recently deleted (an issue as my screen was bugging and may have deleted by ghost touch without me knowing) or automatic lossy compression (an issue as I require some images to not have any compression artefacts). I am also concerned that the 2GB free may be a result of these optimisations, or whether it is a reasonably consequence of the handful of apps I deleted, plus the alert being given when there was already some storage free. I have two main questions: 1. are either of those issues likely? 2. how can I check whether these optimisations have been implemented?

I found out that when I zip the apk with ultra level zip compressor, the file size was effectively reduced. Why didnot developer let that compressed version out like js.minify? How to convert those apk file to ultra zip apk file?

The Camera App natively supports 64MP and I have read that my phone (Samsung Galaxy S20+ 5G) may be able to go even higher. I'm taking lots of pictures in 64MP and it's great, but I've noticed an issue. The images appear to be compressed with visible compression artifacts in the lossy jpeg format. I'd much prefer that that they are stored losslessly when taken and later I can deal with how I want to compress/handle them. I have not yet found an app or setting that can do this. Most of the apps and settings I've used to get a RAW image generally work, but none have preserved the capacity to take pictures in 64MP, instead they apply to 4k, which is not what I'm interested in especially. I've tried the Camera App's Pro Mode, Open Camera, CameraMX and Lightroom. I even tried using a special build of Google's Camera App for my phone that I got from XDA Developers. And CameraMX just crashes at start.

Is it possible to record video from an android camera directly as MJPEG? I am interested in MJPEG for quality purposes. I don't want to record video via default android settings and then convert to MJPEG, but directly from the camera device as MJPEG. Is this possible? I can't find any information suggesting this is possible.

When I use apps like Discord, Facebook Messenger, Zoom, and Google Meets to call people, it compresses the audio like it would in a normal phone call, even though using those same apps from the desktop give much better audio. How do I go about making this audio sound better and not so compressed? I'm using a Pixel 3 XL and am on AT&T (although most of the calls happen over Wi-Fi so I don't see how that matters).

Most android roms have only one zram device [zram0] but linux distros use many zram like zram0, zram1 .... Why is it like that? Does using many zram consumes more power or adds complexity? what's the exact reason?

Please try to understand this question carefully before marking this as duplicate. Do the Android OS has inbuilt support for .zip and .rar files ? I am not asking about any third-party software, because I know that there is a difference between OS support and software support. I am asking this because I have found bootanimation.zip and shutdownanimation.zip files inside /system/media/ folder.

I don't know why, but for some reason, the google music don't play them directly, everytime, it opens winRAR on my Nexus 5X then plays it. This only happens to the mp3 that I downloaded from internet, ie. sites like: youtube to mp3, clipconverter.cc I am trying to make a playlist of youtube podcasts, and for somereason, I need to click the file, it opens winrar, then plays it, and if I uninstall winrar, then i can't play the music... How do I solve this? I quite like the current music player native to my nexus 5x, and it's not working out after a few weeks of trying....

Many custom recoveries, like TWRP, have an option to use compression when creating nandroid backups. By default, this option is typically disabled. Is it safe to use the compression option? Are the only downsides the time that must be spent to compress the nandroid and the possible need for temporary working space to perform the compression? Any other reasons why that option is typically disabled by default?