text:
Disable heads-up notifications
How to disable heads-up notifications (pop-up notifications)?
(These are the notifications that show at the upper part of the screen and obstruct the view.)

You can use adb for this. adb shell settings put global heads_up_notifications_enabled 0 should do the trick

@Aayush Where should I type this?

First of all you'll have to install adb on your pc and then connect your phone and run the commands
Installing ADB

Download adb installer from HERE on your pc
Run the setup and do as directed to install adb.
See THIS video for reference

Connecting device and running command

To use ADB with your Android device, you must enable a feature called USB debugging. Open your phone’s app drawer, tap the Settings icon, and select “About Phone”. Scroll all the way down and tap the “Build Number” item seven times. You should get a message saying you are now a developer.

Head back to the main Settings page, and you should see a new option near the bottom called “Developer Options”. Open that, and enable “USB Debugging”.

Later on, when you connect your phone to your computer, you’ll see a popup entitled “Allow USB Debugging?” on your phone. Check the “Always allow from this computer” box and tap OK. Select connection type to MTP from charge only if this doesn't pop up.
Take a look at THIS if you're stuck somewhere.. Everything mentioned above is demonstrated here with pictures

Now open command prompt and type adb devices. You'll see a device listed there.

Enter adb shell settings put global heads_up_notifications_enabled 0 to distable it. And if you want to enable it back again enter adb shell settings put global heads_up_notifications_enabled 1

Does this command need to be run after every reboot of the phone?

Nope...........

Go to Settings > Applications & Notifications> Notifications.

This affects the normal notifications, but not the so-called heads-up notifications.

Not yet tested; probably doesn't show anything (not even in the status bar) and also disables sounds:

Go to Settings -> Apps -> App info
For each app that shows heads-up notifications:

Tap on that app
Tap on App notifications
For each type of notifications ("Lite" (the cryptically named Facebook app) has about 20 types):

Tap on the name of the type of notification
Tap Importance -> Low (No sound or visual interruption)


text:
Is it possible to keep the user data with a smartphone that boots to the data wipe menu?
My smartphone turns on without passing the OS loading screen, then loads the recovery menu (Redmi-Recovery 3.0). I can't turn off the device, I tried waiting for the battery to run off, charge it and turn it on again, it still can't boot properly. In fact, it won't stay turned off even when the charger is first inserted after the battery has been depleted.
The phone is a Xiaomi Redmi Note 9, OS is MIUI (not sure which version), the menu items are: system reboot (reboots and gets back to this screen), connect to PC with the Mi Assistant (I tried to use the Mi PC Suite, but the device isn't detected, I guess because USB debugging is off on the device), wipe memory (I guess this wipes the system partition along with all the files).
I think my only option is is to wipe everything and hope that it will then boot properly. I was wondering if there is a way to only "restore" the operating system, without touching the user's data (I think I've seen something of this sort both on Linux ans Windows before).
I am also concerned about the phone not staying turned off (I am a bit scared the battery controller is gone for some reason).
Since I have a backup phone that I can use I'm planning of waiting on this question for a week or so and see of something comes up.

no, there is no way. because the whole system is read-only, factory reset will just reset userdata nothing more

btw seems power button is stuck or is wet

@alecxs it seems something like that (probably something got wet), but it has already been 48 hours

A factory reset literally deletes the contents of the user data partition, if you found a way to "reset" and leave the user data intact, you didn't really do anything.

guess the volume button is wet, too. that's why it boots into recovery. no need for factory reset, just wait a week

source: Stack Exchange

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

sort: votes


text:
Is the "History" tab gone from Wikipedia after latest update?
After latest update to Wikipedia mobile app for Android (3-4 weeks ago, the one that introduced many changes in user interface), I cannot find "History" functionality or tab.
I've checked the usual place (three dot menu on article) and probably all other and... nothing.
Is this functionality removed after the latest update of this  application? How can I browse articles that I've read recently?

It is still there. But you have to click on Search to view your history.

You need to be in the main Wiki app screen for this to work. If you tap "Search" (the same icon, in the same place) while being on any article, you will only be able to see list of recent searches and not list of recently visited articles.

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Why does my Android 10 phone needs to be called multiple times before rining?
My Nokia 7.2 Android 10 phone has the following strange problem that is 100% reproducible:

Sits there doing nothing for 10 or 20 minutes.
Receives a phone call but does not ring.
Receives another phone call soon without ringing.
Receives another phone call soon without ringing.
Receives another phone call and rings finally. It will continue to ring if a phone call is received soon.

Again, the above can be reproduced reliably.  Could anyone offer a tip on how to fix this?

This is somehow reminded me of a feature in "Do Not Disturb" mode. Are you using it? Otherwise, have you checked the settings inside the Phone app?

I had never heard of this feature.  I have just checked the settings and you are right - it was turned on.  I do not know how this happened.  Could you turn your comment into an answer for me to accept?

I've had that issue with my older phone (a Samsung) at my home office and my new phone (a Pixel 5a) seems to have the same problem.
I think that in my case it is because the phone is not accepting WiFi calls automatically and I have a bad connection to the cell tower (I'm in a canyon so the antenna is just not properly positioned).
The one way I've found to fix this (At least temporarily) is to make a call to my landline and hang up. That will wake up the call over WiFi feature and then it works well.

As mentioned in a comment under the question, the other reason might be the "Do No Disturb" feature. That was not my issue, though.

This is caused by the "Do Not Disturb" mode and its "allows repeat callers" feature.
The "Do Not Disturb" mode can prevent interruptions from all phone calls, though some contacts can be whitelisted, and may also allow repeat callers to interrupt the user.
The setting can be accessed from Settings - Sound & vibration - Do Not Disturb - People - Calls - Allow repeat callers.

Allow repeat callers
If the same person calls a second time within a 15-minute period

To prevent the first (few) call suppression, turn off the Do Not Disturb mode.


text:
Updating to LineageOS 17.1, replacing su with Magisk
Up to 16.1, LineageOS provided su as an add-on, in the shape of an extra zip file which could be installed along with the OS itself using a recovery image such as TWRP.
However, with 17.1 they have discontinued their su addon and no longer support root access. Those who still want it are getting pointed to “one of the other su solutions out there”.
A quick search pointed me to Magisk as pretty much the only solution under active development. However, the install instructions are a bit confusing.
The device is a OnePlus One (bacon), upgrading from LOS 15.1. For now, I am just interested in having a replacement for what su offered up to LOS 16.1; any other features offered by Magisk are secondary to me.
Will it work if I just grab the latest Magisk zip from the Github release page and install it alongside the OS, through the recovery of my choice (currently on TWRP 3.2.2-0)? Or is using Magisk Manager a hard requirement?
Are there any major differences in UX over my current LOS + su setup?

I just went through the trouble of solving a similar situation for a OnePlus Nord. Meaning getting root access via Magisk on a LineageOS 17.1 device.

"Will it work if I just grab the latest Magisk zip"?
Yes. I sideloaded it with the LineageOS recovery and after rebooting the system I was able to grant root access to apps using magisk.

Are there any major differences in UX over my current LOS + su setup?
Yes. By installing the magisk zip-file you will get the magisk App which is used for managing your root privileges. I do not have the root option in developer options anymore (as I was used to when using su).

Unfortunately I don't have a bacon here to test your specific case, but maybe my experience will still be helpful.


text:
Emulating Sony devices for Android Studio
I have a project that requires me to test it on a Sony device. Unfortunately, I don't have a physical device.
Is there a Sony emulator for Android Studio?

Sony once had a service where you could run your app remote on a physical Sony Xperia device. The service was called "Sony Remote Device Lab Service" but it seems to no longer exist nowadays.

Android Emulators are based off the Google Android Studio SDK Emulator and don't contain any Manufacturer proprietary code/API.
The general properties to change when creating a hardware profile are screen resolution, screen size and RAM. If needed there are additional hardware properties you can configure.
If there is a particular model you need to duplicate, creating an emulator with the same screen resolution, screen size, RAM and OS version would be a good place to start.

Android Studio only provides Google phones as a built in  hardware profile. But you can create a new hardware profile and customize it accordingly. In the AVD Manager > Create new emulator, On the Hardware page Clone a device and customize it or to create a hardware profile from scratch, click create hardware profile and there you can create it from scratch.


text:
Audio files not deleting?
Apologies if this has been answered, I attempted to search for answers and found nothing for my specific issue.
I've got several music files I'm trying to delete from my device (motorola e5 cruise, if this helps any) and while they stay deleted for around a day or so, they always come back fully. I can't get rid of them, and they take up a lot of space.
It's worth noting this device has given me grief as far as deletions before; it automatically deletes images after a day if I move them to a different folder, and I didn't notice until I would look for something important and find it gone. It's extremely frustrating, and I would appreciate any help I can get for these issues, but primarily the music files if you can. Thank you very much!

Are we talking about music you copied to the device or do they belong to an app? Are the music files saved in the "internal storage" section (/sdcard) or on an external sd-card? If it is the latter the app you use for deleting needs to request special permissions for deleting files on the external ad-card. If it just deletes them and does not check for errors the files are never deleted, just the central database entry is removed.

I'm a little ignorant of tech, so please excuse me if I answer poorly. It's music I've downloaded and doesn't belong to an app, and it's saved into my internal storage. So it doesn't need to ask for special permission in that case, right? Just in the case of it belonging to an app/it being saved to an external sd card?

I was asking because if it belongs to an app the might just restore the files. Hence it was the question to understand if the delete process just fails or is really done but later reverted. BTW: could you please edit your question and add the infor about your phone (manufacturer and model) + the user Android major version? Especially on Android 10+11 there were major changes that could be the reason for your problem if the used app for deleting is not yet Android 10/11 ready.

"it automatically deletes images after a day if I move them to a different folder" is there any app with cloud service used like google photos? "they stay deleted for around a day or so, they always come back fully" maybe the location is write protected? some devices run in emergency mode where the whole userdata partition is mounted read-only - that mean any changes will revert on reboot (even factory reset) i first heard about such thing 4 years ago https://forum.xda-developers.com/showthread.php?t=3472891&page=2


text:
Micro sd card doesn't show up after I formated it as internal storage
I have the Xiaomi Mi A1 device and has Android 9 running on it. I just bought a new micro sd card cause my internal storage is full. When I first inserted it, I chose the option "format it as internal storage". I migrate the data, but it fails when it got around 60%ish, so I manually move some apps to the sd card from the app settings. However, not all apps has that option. I only able to move apps like Facebook, Ms. Word, etc. But I don't really think of it that much, I guess that's how it is. And now my problem is that, apparently, after I formatted it as internal storage, the sd card doesn't show up in the file manager (I use X-Plore and google files) because I also want to move my photos and videos. Though I was able to move some apps to it through the apps settings.
I tried to format it as normal storage (forgot the option name, "format as portable storage" I think?). It shows up in the file manager, and I can move my photos and videos, but now I can't move my apps to it. So my question is that

Is that how it is? When you format a sd card as internal storage, the file manager can't read it? or am I missing any setting?
I figured out maybe because my sd card is broken, I bought an SanDisk Ultra microSDHC UHS-I Class 10 and it says up to 80MB/s speed, 533x. Perhaps got a better recommendation?

Sorry for bad english, I'm not native.

If a new sd-card "breaks" by just using it often it is a fake (sd-card contains less flash than it claims to have). If you have a PC and a micro-sd-card USB reader use one of this tools to test if your card is genuine: https://www.raymond.cc/blog/test-and-detect-fake-or-counterfeit-usb-flash-drives-bought-from-ebay-with-h2testw/

yes thats normal, there exist no external storage any longer because you have adoptable storage. you can check this from terminal with df you will see /mnt/expand/.../media (which is your MicroSD Card) is mounted to /storage/emulated

Does this answer your question? How to free Internal Storage by moving data or using symlink / bind-mount with Adoptable Storage?

one thing you can do is split MicroSD Card in two partitions (mixed) https://android.stackexchange.com/q/145457 https://android.stackexchange.com/q/213312


text:
How do I turn off the sound of Zoom on Android? (not the mic)
I'm joining a Zoom call on my laptop, but I also want to join the same call on my Android device in order to share my Android device's screen and to use my Android device's camera. I don't want to hear other people's voices coming from both my laptop and my phone, I only want to hear their voices coming from my laptop. So I need to turn off the volume on my Android phone.
If I press the Volume down button, Zoom won't let me decrease the volume all the way to zero. I expected they developed the app this way to help users who don't realise that the volume on their device is set to zero. However, in my use-case, this is proving annoying, as I'm now hearing the same voices coming from my phone and from my laptop.
How do I turn off sound on an Android device when on a Zoom call?

When you're joining a meeting, you can find an option "Call via Device Audio" under the button menu "Join Audio".  If you don't enable it, you can't hear the participants' voice.

Or You may disconnect the audio from the more options present at the right- bottom (the dots)

The only solution I have found for this so far is to plug in some headphones into the phone, without wearing the headphones. That way, I don't hear the sound output by the Zoom app on the phone.


text:
What is the most stable kernel for my ALE-L21 (2015) alice and ROM?
I'm pretty sure that this is already a weak legacy device but I want it to be useful and stable in performance to the max. Can you suggest the ultimate kernel for my 7.1.2 AOSP based custom ROM?

Note: I'm using a vanilla kernel.

custom kernels are always trial & error there is no most stable


text:
Xiaomi A2 stuck in a reboot loop because of data partition
I installed the October 2020 update for my Xiaomi A2, and then it entered a reboot loop, giving me a "Cannot load Android system" message.
Actually, when I boot up the phone, I automatically get to the recovery menu, which only gives me two options: wipe the data partition, or reboot. And rebooting sends me back to the recovery menu.
Here's what I did:

First, using fastboot, I reinstalled the entire OS except the data partition. That ended up in the same reboot loop.
Then, using TWRP and executing it with fastboot boot twrp-3.4.0-1-jasmine_sprout.img I could adb shell into my device. From there I ran an fsck -f which did find a couple inode problem. But fixing those problems still did yield the same reboot loop.
Using TWRP again, I locally cloned my data partition using adb pull /dev/block/mmcblk0p69 data.img, then I tried the "wipe the data partition" option. My phone did reboot properly, but of course it was reset to factory settings.

Question: is there a way I can restore my phone to a working state with my previous data? I really don't want to reconfigure all of it…
Also I don't really understand what's the problem with my original data partition. Is there a way to know why Android doesn't want to boot with it and why it sends me to the recovery partition?
More info:

Running fsck on the local data.img says it has no error whatsoever
I can mount the data.img and browse it. It's full of, well, files!

in twrp do 'adb pull /tmp/recovery.log' and check if there is something like "successfully decrypted" - be aware for FBE you can't wipe locksettings.db https://android.stackexchange.com/q/216155

So, here's the best I could do:

Try to boot normally
The phone will crash and try to reboot to the recovery partition.
At that very instant, press volume down and power, so that it goes to fastboot instead
From fastboot, launch TWRP with fastboot boot twrp-3.4.0-1-jasmine_sprout.img
Once in TWRP, get a shell using adb shell
Then from this shell, look at the file /sys/fs/pstore/console-ramoops-0. It contains the previous kernel boot log!

In my case, here's what the boot log contains : init: Rebooting into recovery, reason: enablefilecrypto_faile. So apparently something is wrong with Androi File-Based Encryption…


text:
Is a rooted phone still required to pass '-k' in ADB's package remove command?
I successfully ran pm uninstall --user 0 packagename without the -k argument on my phone which isn't rooted, despite the XDA article saying it's needed.

Does this answer your question? How to re-enable apps using ADB?

-k is option to keep cache + appdata:
/data/user*/0/<pkgname>
without that option only the .apk file remains on the device:
/system/app/<pkgname>/base.apk
pm install-existing <pkgname> will re-enable app with/without appdata depending on -k
(explained in section How to Re-Install)

I know, but what confuses me is that the articles I read say that you need to be rooted to be able to leave out the -k, but I excluded it on my unrooted phone (just to try) and it worked fine, so I don't know if root's still a requirement.

So what happens when you exclude -k? Does anything other than the app get deleted?


text:
Android 5.1 Emulated abd push give adb: error: failed to copy etc... remote Read-only file system
Hi I'm not trying to change the system just upload some file to the /storage/sdcard folder or /sdcard i do
adb push etc /storage/sdcard
and I get
adb: error: failed to copy 'etc' to '/storage/sdcard/etc': remote Read-only file system
the thing is only happens on android 5.1 it must be a bug i read many post about remount the system but it is not the system what i need to remount it is the userdata partition it should be writable, i have create many times the AVD maybe it is something i did but always i get the same result
if i do df in shell i get
/dev                   498.4M    28.0K   498.4M   4096
/sys/fs/cgroup         498.4M    12.0K   498.4M   4096
/mnt/asec              498.4M     0.0K   498.4M   4096
/mnt/obb               498.4M     0.0K   498.4M   4096
/system                  1.4G     1.2G   180.2M   4096
/cache                  61.0M    56.0K    60.9M   4096
/data                    7.7G   571.6M     7.1G   4096

i can't upload files , if i install es Explorer says the sdcard it is unmounted but don't shows the internal storage where it is the internal storage ? some one can tell me please what it is happen here ?

/data/media see this question https://android.stackexchange.com/questions/205430/what-is-storage-emulated-0

@Robert thank you that lead me to something but i realize the problem it is on  the emulator the usbstorage it is active the all the time then i cant access it from android i think should be a way start the emulator whiteout the usb connected  i will read thank you

the error message is misleading - target directory does not exist

@alecxs that's correct in my attempt to create the AVD from command line in the creation of a custom hardware profile it doesn't give you an option to create the sdcard it ask you if it will be SD Card support and the path for it but never ask the size to create it, you must create it whit mksdcard and then add the path to config.ini and then it works ! this only has happen to me in android-22 "5.1 lollipop" and i have upgrade everything in the SDK tools recently


text:
recover text messages
I have an Huawei running the latest Android.  I accidentally deleted some Very important text messages and they haven't been backed up.  Is there anyway I can retrieve them?

no, not from the device itself. check notification logs maybe there is some kind of copy


text:
Customize Google Assistant button
I am using a Motorola phone which has a dedicated Google Assistant button, but I don't use the assistant much.
Is it possible to customize the button and use it for some other activity?

Fortunately there is a way..
Download this Button Mapper , grant the accessibility permission then click on add a button then press the button to record it and then set the function you want! Simple as that.
Remember to turn off battery optimization for Button Mapper app because if the app is paused by the battery optimization then no hardware buttons will work (touch screen will work). You'll have to go to settings and kill the Button Mapper app to get hardware buttons working again.
This is the only way to change the button function without root.

If you only want to customize the Google Assistant button, then Assistant Shortcuts is a good solution.
By setting it as the device's "assistant", you have a single button press to perform any function you specify. I'm currently using it to take screenshots.


text:
Can I copy data to be restored, if phone is stuck in bootloop?
My phone is stuck in a bootloop. I can get into TWRP recovery, which has a file manager. I can also connect the USB cable to computer and see the phones internal memory. Is there a way to copy text messages and WhatsApp messages so I can restore them on another phone?
I'm afraid the filesystem may have been corrupted. When I go to /data/data/ I expect to see names like "WhatsApp" or "Facebook" but everything is random...like +NiZZaTrs3RFzYegpkEk

Comments are not for extended discussion; this conversation has been moved to chat.

Does this answer your question? /data's data is garbled in TWRP. How to decrypt

Does this answer your question? Backup WhatsApp from NANDROID

@Firelord please confirm the comments in chat will not be deleted by the system

@JonDon Hello. The comments are not deleted on their own. Only the chat room freezes after inactivity for consecutive seven days. Even after that, you can still read all the comments at any point of time in the future.

This was a long process with lots of side problems coming up. Somethings I don't know why they worked or did not work. I will give a recount of what did work in hopes the information will be useful in the future.
At a high level the idea is to backup the data partition, reflash firmware and ROM to fix the bootloop, reload the backed up data partition. Perhaps in some cases this would be enough, but recall the whole data partition is restored - you can't choose individual files or apps. In my case this corrupted some system settings but the data and apps were still there. I used Titanium backup to back those up to external storage, then flashed firmware and ROM again.
Whenever the phone is stuck use the "hard shutdown method" by holding the volume up and power button and waiting for the phone to vibrate 3 times. At this point the phone is off.
STEPS

The first thing to do is get into recovery mode with TWRP.
(If you already can do this, skip to step 3.)
https://twrp.me/sony/sonyxperiax.html

Notes About Sony Devices:
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily.  Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility.
TWRP may not work on your device unless you install other custom software as well.

You will need adb and fastboot, in Windows represented as adb.exe and fastboot.exe which run in command line terminal - (for adb and fastboot Windows XP click here)
If you do not have TWRP, follow these instructions (for the Xperia XZ1 Compact)
a) download the ZIP file from here (it is that TWRP but with working adb)
b) extract the img from the ZIP file (not a flashable zip)
c) connect the phone to the computer via a USB cable in fastboot mode. To put the phone in fastboot mode, completely power it off. Then hold the volume up button and the power button at the same time until the light on the phone turns on. connect the phone to the USB cable if it's not already.
d) If you're on Windows, open a command prompt with administrative privileges by right clicking on it and choosing "run as administrator". I recommend to use cmd.exe and not the Windows PowerShell. Navigate to the platform-tools folder with the cd command. Type in fastboot devices. If nothing is returned or it says "unauthorized" that means you need to install the correct drivers. The official drivers are here but I found I couldn't install them directly. I needed to download the Google USB Driver and replace android_winusb.inf with that from Sony. I found I needed to reboot using advanced options to disable Windows Driver Verification in order to install the drivers. Right click on the inf and choose "install".

Now that the drivers are installed, from the elevated command prompt run
fastboot devices
fastboot flash recovery C:\path\to\folder\twrp-3.3.1-0-lilac-android10-2.img

Boot to recovery. This can be done by turning off the phone, holding the volume down button and power on button at the same time until the screen turns on.
(If it doesn't work you can also boot image from fastboot without flashing)
fastboot boot C:\path\to\folder\twrp-3.3.1-0-lilac-android10-2.img

If your phone uses FBE file-based encryption the data will be encrypted with lock screen password/PIN (hence the strange file names in /data/data such as +NiZZaTrs3RFzYegpkEk). Newer versions of TWRP support decryption. TWRP should prompt you for a password when it first starts, however I found this buggy and it sometimes just didn't ask for a password. If this happens try restarting the phone in recovery or reflashing TWRP. Also going into terminal emulator from Advanced, try the command twrp decypt [password], see here if you had a pattern.

Backup your (decrypted) data from TWRP backup menu. make sure backup location is MicroSD Card or USB storage. Only choose the Internal Storage if you planning to save all your files to PC before factory reset.

Don't forget to backup Internal Storage manually as it is not included in TWRP backup. You can do this via cmd line
adb devices
adb pull /sdcard C:\path\to\folder

Note for adb to work, the phone must be in recovery mode (i.e. TWRP is open)

Download Flashtool, a ROM of your choice and compatible firmware. You can try to flash the same ROM that you have been using, but I was unable to find  stock ROM for this phone. I recommend Lineage 16 with this firmware (Lineage requires 47.2.A.11.228). I tried Lineage 17.1 but setup would go into a loop. Also download GApps Pico for Arm64 and Android 9. Download Magisk zip and apk. This is needed if you're going to use Titanium Backup to backup the apps and data you want to save. Perhaps in some situations this isn't needed if you can migrate without root.

Install Flashtool.

In Flashtool flash the FTF for the firmware first. Then flash the ROM (e.g. Lineage).

Boot into TWRP and install Gapps pico and Magisk. Magisk is needed for root which is needed by Titanium Backup, which will be used later.

The phone should be able to boot normally now. Give it plenty of time (e.g. 10 minutes). Take a break to go for a walk.

Confirm everything is working relatively ok. For example browse the web, download a simple app from the play store. If it's not, flash a different firmware or ROM with Flashtool.

Install and setup Titanium Backup. If you prefer alternative you can also use Migrate! (from the Google Play Store or anywhere else)

Reboot to TWRP

Restore only the data partition.

Clear cache and reboot to system.

In my experience all the data and apps were restored. But some system functionality was broken (like the WiFi). If it wasn't we would be done on this step :)

Use Titanium Backup to selectively backup the apps and data you want to keep. Make sure the backup is put on an SD card or USB storage so it won't get over written.
If your device is not working, there is also a method to do this 'offline' from recovery. refer to the Migrate support thread on forum.xda-developers.com (development in progress)

Do a factory reset from TWRP -> Wipe -> Format Data -> type 'yes'
if Format Data fails, Repeat step 7 and 8.

The phone should be working normally again.

Use Titanium Backup or Migrate to restore the apps and data from step 18.

Done.


text:
What is "Carrier Location Service"?
What is Carrier Location Service in Android?
If I try to allow it, there are 3 options:

Allow all the time
Allow only when using the app
Deny

What are the effects?

What you describe is the request if an app is allowed to access your location. Are you sure this request is for the Carrier Services app?

I couldn't really find references to "Carrier Location Service", but I found "Carrier Location Access" instead on OnePlus (1, 2) and MotoG (1)

It is com.coloros.locationproxy.
It is actually a system app found in Color OS,Realme UI, Funtouch OS, Oxygen OS (Color OS based versions), etc (basically OSs of brands under BBK Electronics)


text:
Why are these picture-related apps blank?
I've been wondering a lot about this when it happened which I was using Walli* app yet after I have changed my ROM, maybe the app gets blank no matter how I install it. But after a time, I've also realized that there is another app called Reface with the same problem in which I can't use them because they're blank like there is no connection to the Internet.

Note: I'm using Cloudflare Family DNS on my router and Firewall settings such SPI and DOS protection.
My ROM: AOSP based 7.1.2 Android custom ROM

Have you tried with other WiFi/mobile data? This may be a connection/network/firewall configuration issue, not an Android issue.

@AndrewT. Not yet but the other apps are working?

Well, it depends on where the sources of the images come from, and whether they're blocked by the firewall and/or Cloudflare Family DNS..?

I don't know yet. However, Cloudflare Family DNS also blocks malware.

The problem was solved by installing Exposed via recovery instead of Magisk


text:
Blocked SIM card and getting asked for PUK on Lineage OS 17.1
I installed Lineage OS 17.1 on my Samsung Galaxy S3. Everything worked just fine until I put in my SIM card. The first thing which happened after booting was getting directly asked for the PUK code although I didn't even enter a PIN at all. So I just rebooted the phone again which made it not recognize the SIM card anymore.
After that, I put my SIM card in my Samsung Galaxy S5 with stock ROM and I got the message that my SIM card is permanently blocked.
Any idea what happened there?

no clue. sounds like lineageos has tried to unlock sim for it's own but i am not aware about such "feature"?

I didn't expect that "feature" at all :D

can you reproduce with another sim card?

I was affraid to put in another working simcard so i put in an old one. It didnt even ask for a pin, just didnt recognize it where as an old iphone asked for a pin after i put it in there.

On the LineageOS web site there is no LineageOS 17.1 for Galaxy S3. Are you sure you have installed a genuine LineageOS ROM or is it just a LineageOS based customROM? In the latter you are never sure what mdifications were made by the ROM author.

@Robert I'm not sure it might be not genuine. I downloaded it from that source:
https://forum.xda-developers.com/galaxy-s3/development/rom-lineageos-17-1-t4047715

that ROM is Status: Alpha for developers, not for daily drivers. find a stable ROM with no bugs, make a fresh install of stock ROM before flashing custom ROM

thanks, will do.

You have SIM password. You enter wrong password. Then it ask for PUK code. PUK code is link with sim card.
Use sim on normal mobile. Is it ask PUK code.
You can get PUK code from customer care. You can also get it from your online register account.
Get PUK code and use it. Weather sim card work after it.

you missed the point OP "didn't even enter a PIN at all" - it is a LineageOS bug (inofficial test build) and will happen again as soon as SIM is inserted


text:
if project treble aims to separate the platform and vendor partitions, why is the kernel source code needed when building system.img (platform)
if project treble aims to separate the platform and vendor partitions so they can be updated separately, why is the kernel source code needed when building system.img (platform) for AOSP, isn't the kernel source code provided by the vendor side?
p.s is the kernel source code used to build the core system/framework files or is it only used in the boot.img/recovery.img?

what do you mean?

i mean for system-as-root devices it may require kernel source to build system.img

is the kernel source used to build the core system/framework files?

https://source.android.com/devices/bootloader/partitions/system-as-root

do the core platform framework files in the system partition contain kernel specific code in a device which is not system as root?

consider self-answering your question here on android enthusiasts for sharing knowledge


text:
Determine what APPS are Android Auto Compatible
When I connect my cell phone to my vehicle, Android Auto displays a very limited list of APPs that are on my phone:

(The clipped APP at the bottom is weather).
Supposedly more APPs that are compatible with that interface will be released.
How do I determine if an APP on Google Play is compatible? I don't see anything on the Google Play webpage for a given APP that indicates it can be used or not used for Android Auto.
(In particular, I want navigation with offline maps beyond what Google Maps offers).

There is a special category in Google Play Store that lists apps ready for Android Auto:
https://play.google.com/store/apps/collection/promotion_3001303_android_auto_all
If you have an APK and want to check if it is ready for Android Auto you can look at it's AndroidManifest.xml file inside the APK. It should contain an entry like this:
<meta-data android:name="com.google.android.gms.car.application" android:resource="...."/>

For more details see Add support for Android Auto to your media app.


text:
Read data on SD card which was formated as Internal storage of Android OS
I have a Lenovo Vibe K5 Plus with Android 8.1.0. I plugged in a new SD card (Kingston MicroSDHC 32 GB) and this SD card was formatted as Internal storage, so data on this SD card was accessible by connecting the mobile phone to the PC.
However, yesterday I removed the SD card from my mobile phone and I did a big mistake that I clicked something in Settings -> Storage, something like forget SD card. So now I have got an SD card with my data (photos, music, etc.) which I cannot read on a PC with an SD card reader.
Is there any chance to read my data from this SD card? I looked that in my phone some data has .nomedia.

restore backup of phone from previous state (before forgetting sdcard)

Did you click FORMAT Sdcard? If you did then your data is gone and unfortunately you can not recover it

I did not format SD card, because it was removed from phone. Data should be still on it, but i do not know, if it possible to read them with any special software or how....?

Hello, I do not have any backups, because all worked properly. I expect if there is some option (program) to read my SD card data. I did some research, that now SD card is crypted...but I do not know if is posible to read them.

in that case your data is lost forever - SD card formatted as internal storage Recovery Data - Completely securely deleting a single file - How long does it take to crack DES and AES?

The "forget" option tells the Android system you no longer have the card. What it then "forgets" is the encryption key needed to encrypt/decrypt this specific card. So basically you've locked the safe and threw away the keys; without the keys, there's no reasonable way to open the safe again.
Thus, your data are lost. It might be possible to regain the key (e.g. if the device is rooted; you could create an image of all its file systems and use forensic methods to find and extract the deleted key). But not only would that require your device to be rooted, the effort to find and extract the key is not low, and chances are it's meanwhile overwritten. If your data are worth a 4-digit value (EUR or USD) to you, you could contact a forensics company to give it a try – but chances are rather low.
Permit me a note to one of your comments on your question:

I do not have any backups, because all worked properly.

That's exactly the point-in-time when one does perform a backup: you need the data intact. You cannot create good backups of a broken system – but at that point you'll need a backup to repair it, as we've just learned.
Also see: How to get Adoptable storage encryption key without root access after I “forget it” (answer: you can't).


text:
Documentation of /system/addon.d
Placing scripts into /system/addon.d/ makes them execute before and after every OTA packag upgrade.
This
is
used
or
mentioned
in
multiple
places.
I have multiple questions about this:

Is this a general Android feature or just provided by many custom ROMs? If only ROMs, any notable exceptions?
Where is the documentation / specification / source ? I would like to get to the APIs that I can work with.
(related) What is it with this /tmp/backuptool.functions that seemingly anyone is sourcing at the beginning of the script. How could I find out which functions are provided by this and what they do?

Thanks a lot!

It's not a standard, but just a convention which is followed by many in custom ROM world. IIRC it's the LineageOS/CM who introduced the idea. So their repo is the best place to see latest changes.
There is no complicated API, just a few bash script functions to backup/restore some files during OTAs (dirty flashes).


text:
APK signature verified but warns file "not protected by signature"?
I'm using apksigner to verify the authenticity of a Google Podcast apk that I downloaded from an apk mirror. This apk (and older versions) verifies successfully (v1/v2/v3) and returns exit code 0 but in the output I see this warning:
WARNING: META-INF/services/com.google.protobuf.GeneratedExtensionRegistryLoader not protected by signature. Unauthorized modifications to this JAR entry will not be detected. Delete or move the entry outside of META-INF/.
I do not understand what the impact of that is. If the APK is signed, and verified, why do I see this warning? Does it mean the APK could be trojaned or modified? How could an attacker exploit that?
I am downloading some older versions of some Google apps and I want to be sure they aren't trojaned, which is why I'm trying to verify the authenticity before I install them on my phone.

Summary
The warning you have encountered only applies to the APK signature v1, but as the APK file contains also a v2 and v3 signature you can safely ignore this message as every modification on the APK file can be detected by the newer signature schemes.
However even if the signature can be verified it does not mean that the APK file is genuine. It still could be resigned after modification, therefore you should carefully compare the certificate digests (shown when verifying it using apksigner verify --verbose --print-certs) of the APK to be verified and compare it to other APK files of the same app developer. See this answer of How can I verify the authenticity of an APK file I downloaded? for details how to compare the certificate digest of an APK.
Detailed explanation
First of all as you can see what you get is a WARNING not an ERROR. If relevant file(s) of the APK file would have been modified the verification would fail and you would get an ERROR message.
To understand the warning message you need a little understanding of Java and how Java signatures (APK signature v1) work. This old signature is stored inside the JAR in two files: META-INF/CERT.SF and META-INF/CERT.RSA. Of course a signature can not sign the files it is written into , hence those files are excluded by the signature.
Additionally the META-INF directory is location of the MANIFEST.MF - a file that is only relevant for Java on Desktop but not used by Android at all.
There can be additional files in the META-INF directory, considering the standard Java directory layout no code should be stored inside files within the META-INF directory.
Because of all this Sun as the original inventor of Java decided to exclude the META-INF directory from the Java code signature at all. Several years later Google just used the Java signature for APK files which is now known as APK signature v1.
Therefore for the APK signature v1 the files inside the META-INF directory are not covered by the signature and hence can be modified without being recognized if you only verify
Because of several attacks on the APK signature itself (such as including the same file multiple times with different content in the APK Google decided to develop a completely new APK signature that does not apply on the APK content but on the overall APK file itself. This was the beginning of APK signature v2 and it's successors.
These new APK signature schemes do sign the complete APK content at once, not excluding a single file that is stored inside the APK file.
Back to the Google Podcast APK, verifying it using apksigner outputs the following:
java -jar apksigner.jar verify --verbose "Google Podcasts Discover free trending podcasts_v1.0.0.301897054_apkpure.com.apk"
Verifies
Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): true
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
WARNING: META-INF/services/com.google.protobuf.GeneratedExtensionRegistryLoader not protected by signature. Unauthorized modifications to this JAR entry will not be detected. Delete or move the entry outside of META-INF/.

As you can see the APK file is signed not only by an v1 signature but also a v2, v3 and v4 signature. This means that the WARNING only applies to the signature created by the v1 scheme. You can easily verify that by modifying a single character inside the file META-INF/services/com.google.protobuf.GeneratedExtensionRegistryLoader as it is stored uncompressed within the APK file. You can simple open the APK file in an hex editor, modify a character in the section that belongs to that file (it is the first ZIP entry within the APK) and then again verify the APK:
java -jar apksigner.jar verify --verbose "Google Podcasts Discover free trending podcasts_v1.0.0.301897054_apkpure.com - modified.apk"
DOES NOT VERIFY
ERROR: APK Signature Scheme v3 signer #1: APK integrity check failed. CHUNKED_SHA256 digest mismatch. Expected: <ac8a15569352655a22f13d3c565c2c0e5c62dc70c8f6f8c10f6fbfa63decb19b>, actual: <aa5622cd904500c38424562ef4b5be9e5716d10a85985a41f35e4ed834cee8fe>
ERROR: APK Signature Scheme v3 signer #1: APK integrity check failed. VERITY_CHUNKED_SHA256 digest mismatch. Expected: <56eeebd545733fd6408cd6a30b8bcf98a557076167902b6d9502b5aca86b78e89b42220000000000>, actual: <c37e1e1436cfd62f89592c48211ffb6ad2f1dff0f69d2203072f1e6c3872a5919b42220000000000>

As you can see now the APK signature is considered invalid. I don't know why the v3 signature fails first, may be the signatures are not verified in order v1, v2, v3...
From my understanding all signatures except v1 should fail on the modified APK file.

Thanks Robert (+1 for now ;)! Maybe you also want to point out that just because verify succeeds does not mean you've got no Trojan (or whatever) – as a completely different signing key might have been used? AFAIR jarsigner -certs -verify -verbose can be used to show details of the certificate used. But then, if the APK was downloaded to update an already installed app, Android would not accept the update if signatures do not match – so that would only be relevant to first-installs.

@Izzy: Thanks Izzy, you are correct. I excluded this from my answer as it is already covered by the answer "newguy" has linked to in the question: https://android.stackexchange.com/a/218161/104486 hence I assumed that he is alerady aware of that topic, but for other users it might be still relevant.

Great, thanks! Especially using apksigner instead of jarsigner, so v2+ is covered as well. I'd upvote again, but not even a mod can do that :D

...but what the "Verified for SourceStamp: false" means? Is it a security issue?

@g.pickardou Source code comment from AOSP: "SourceStamp improves traceability of apps with respect to unauthorized distribution." hence I would assume that is the signature only apps downloaded via Play Store can have. A False value here may just mean that it does not exist thus may not originate from Play Store. Most of my APKs have a False value there.


text:
no write permission to memory card storage from termux
is it possible to write/edit the files on the memory card with Termux
i tried the command:
termux-setup-storage
but it only gives the permission to write on my device storage(/emulated/0/)

Writing to the external sd-card section is only possible using the Java-API. As Termux applications are usually regular Linux programs writing to the external sd-card is not possible as far as I know.

If your device is rooted you can use root to write to memory card.

is it possible if i use beanshell[on termux] to write into memory card


text:
Getting root access on meizu x8 (Andriod 8.1.0)
I tried various methods that I can found on the web to get root access, but none of them worked. I do not trust the vendor-provided method of getting root access. Does anyone know a way to get root access on meizu x8?

What all did you try? your question is not clear. Do you know how to manually root? if no have you tried one-tap root apps?

try to root manually then

This seems to be the firmware for your device. meizu X8 Flyme

Can you get the boot.img from the firmware? If yes I will answer an official answer on how to root.

Disclaimer: I take no responsibility on the steps below. Root at your own risk.
As per Aayush's comment, I would advice you to read up more on rooting. Make sure you understand the ins and outs and the consequences of rooting, nd the possibility of bricking your device, before you attempt to root.

Install Magisk Manager on your device.
Copy the boot.img to your device.
Run Magisk Manager.

On the right near Magisk click on Install.
Untick Recovery Mode.
Click on NEXT.
Tick the "Select and Patch a File"
Now select the boot.img file you copied to your device. This will patch the file and save it to you Download folder.
Copy the patched file to your PC.

Enable USB debugging and OEM Unlocking in your developer settings.
Unlock the bootloader (usually this can be done in fastboot by running fastboot flashing unlock. If this doesn't work google "unlock bootloader" with your device name). This will factory reset your device, you will loose all data.
Flash the patched boot image file in fastboot fastboot flash boot <path-to-the-patched=image-file>.
Reboot your device fastboot reboot.
After setting up your device again, install again Magisk Manager on your device. And follow the directions. It will install the Magisk (Note: it will install Magisk not Magisk Manager which you just installed yourself) to your device and you should have root).

GOOD LUCK

Sruly, your effort is great!(+1) but i'd recommend Joy Jin not to root his device since he doesn't has proper knowledge and there's a high possibility of him bricking his phone.


text:
Conected to TV and control device via remote
I connected my Samsung Galaxy Tab S6 with my LG tv over HDMI and it works good so far.
But what I am missing, is the possibility to control my tablet with the LG remote controller.
When I connect my tablet via SmartView it works, but not when doing so via HDMI.
(I want the connection to be via HDMI because of different reasons.)
Is there some option that I missed?
Or is it simply not possible to send the needed signals over HDMI to my tablet?
If so, do you know of some workaround? Like connecting your smartphone to the tablet and use it as touchpad? I would like to avoid buying a bluetooth mini keyboard.
Kind regards

For forwarding remote control commands via HDMI the tablet would have to support "HDMI CEC". As the tablet is not directly connected via HDMI but instead a MHL adapter is used I don't know if the HDMI CEC commands can pass this adapter at all and second if the tablet supports HDMI CEC commands at all.


text:
How to clean app cache using script every time the phone boot?
I know there's many app that clean cache every boot but I would like to use init.d/script to save storage.
Dalvik-cache is /data/dalvik-cache/arm/ as I can just rm -rf *
But, app cache is located at /data/data/app_name/cache and don't know how to automate it, because cache folder is a sub-directory
I'm new to bash scripting and this would help me significantly in programming overall
Phone is magisk'ed Android 10.

that doesn't make sense you will slow down your apps, increase mobile data and premature emmc wear-out. however you can use find https://android.stackexchange.com/q/220648

It's for practice, I don't really use it. find is a great help thanks!

I forgot array is such a thing. I solved my own problem
# Assigning app-name into $apps
apps=($(ls /data/data/))

# Looping each app
for app in "${apps[@]}"; do

  # Deleting $app/cache/ contents
  rm -rf /data/data/$app/cache/*
  done


text:
Drag'n'drop event moving gone in Calendar... again
Google Calendar's event's drag'n'drop functionality stopped working... again, after nearly exactly two years since previous report. Tried to restart both Google Calendar and phone itself (Motorola Moto Z2 Play with Android 8.0.0), cleared app cache and then data, without any results.
I did very little to my phone before that happened:

no configuration changed,
nothing actually doing with my phone.

I have only installed one new up -- FakeStandby -- as suggested here, but since this app has nothing to do with the calendar itself, I would be surprised, if that would be a source of the problem.
To clarify problem:
On a day view (not: agenda) long-pressing any event now brings no effect. Previously it caused an event box to be risen up visually above others, and moving finger around screen allowed to move event to some other hour or day. Now, drag'n'drop functionality does not exist / does nothing.
Is there any know report about some bug, bug's regression or is this a generally known problem? Or is this again my stupid phone going wako in exactly the same way during second anniversary of the moment, this problem appeared for the first time?
EDIT: From what I have learned, when Calendar becomes "locked" (no event's drag'n'drop) all items in calendar are visually more flat than usual. When functionality "returns" they again become a little bit 3D-like.

What worked the last time you had this problem? Did you try that again?

On contrary to initial believes, it was (is) FakeStandby that is causing these problems!
This app is designed to FakeStandby mode, by turning off screen, but not causing actual standby mode. This causes that all other apps are not notified about phone being in standby and continue working in background (below FakeStandby).
To achieve this, FakeStandby must be able to control all apps (at least that's what its author claims). And in order to do so, it adds itself to the "Accessibility" section of the configuration:

And... that's all. Having FakeStandby Service turned off causes Google Calendar application to lose / disable / turn off event's drag'n'drop functionality. Why? Unfortunately, I have no idea.
The simplest workaround -- for having Google Calendar's full functionality and not being forced to uninstall FakeStandby -- is to kill this app after each use. Long-press on its icon > App Info > Force Stop does the magic. Until next run of FakeStandby, Google Calendar will have full functionality.
Since this is a system service, killing it with Force Stop will also automatically reset its setting in Accessibility > Downloaded Services to Off. When you run FakeStandby next time and attempt to activate it (by pressing its button on the right side of the screen) you will see a message:

If this is too annoying for you or impractical, because you're using FakeStandby too often then I think there is no other option rather than a split decision:

find some FakeStandby replacement or
stop using drag'n'drop functionality in Google Calendar.

I am pretty sure that this is some kind of bug in FakeStandby itself, not in Google Calendar. As I have two other apps listed in Accessibility > Downloaded Services (namely: Nova Launcher and Kaspersky Safe Kids). Both apps has their setting set to Off by default (because ability to observe screen and control other apps is used in them only in a rare, specific scenarios).
But, I have just managed to test that setting it to On for any of these two does not cause described problems with Google Calendar. So this got to be "something" in between FakeStandby and Oreo (I have no ability to test this issue in other versions of Android system).

This is interesting.  May I recommend reporting this issue to both Google and the author of Fake Standby?

Great idea about that, but unfortunately I don't think I can do this. I don't know, if Fake Standby's author has any bug tracking service established. And I completely don't believe in reporting any bug to anything related to Google. For past 15-20 years I have the feeling that they have all their users and all their bug reports deeply below spine, so for me even searching on where to report Google Calendar's bugs are 100% waste of time, sorry.

Here you have some examples of really huge and annoying bugs (like the one with rich event details editor) not fixed for THREE YEARS, even when affecting all users: https://itfuckup.com/2017/10/26/new-google-calendar-design-oh-shit/ + https://itfuckup.com/?s=Google+Calendar

I completely agree regarding your observations of Google.  They really are horrible.  Due to their behavior (for which you cite some great examples), I avoid their products as much as possible (which is almost completely).  Unlike Google, the Fake Standby author is very responsive.  Here is the Fake Stanby issue tracker: https://github.com/JonasBernard/FakeStandby/issues

Thank you. Issue reported: https://github.com/JonasBernard/FakeStandby/issues/17

You're welcome. Glad to help.


text:
unable to flash rom in edl mode using linux qdl or even qfil or miflash. what could be the error?
i have a redmi note 3 snapdragon variant.
i was using it casually and i pulled its back cover and wassss in deep thoughts when i accidentaly or stupidly removed the battery flap when phone was on. i put thhe battery back it didnt turn on and i plugged the charger it gave red blinking light no screen on. so it was stuck no change even after many methods.
i plugged it in windows laptop and was surprised it recognized as in edl mode(although not instantly learned becuase i am not much knowledgeable).
so after trying many miflash or qfil or and many tricks for them given by xda, i couldnt flash the rom, so many sahara errors or hello packet errors.
i tried the linux method and it still gave hello packet error on linux using qdl tool.
so i am not sure if emmc is damaged or its is locked. in one xda thread one guy said it could be emmc read or write locked. any tips.
update; the error or log i recieve:
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ image: 13 offset: 0x0 length: 0x34
END OF IMAGE image: 13 status: 20
received non-successful result

Does this answer your question? Sahara fail while trying to flash a rom into my phone

nope, i am using the linux method given in that answer. but i am getting the error not mentioned there.

after booting in EDL emergency download mode there is a ~ 2 seconds timeout as stated in comments

yeah but my device is stuck in edl mode. no matter what. doesnt matter if its 30 or hour

that's probably too long try start flashing immediately when connecting usb cable. also check lsusb if device is detected in 9008 mode

if you think device is read-only try to just read something with edl.py https://android.stackexchange.com/q/226838

can u explain more about lsusb

press ctrl + alt + T and type lsusb in terminal


text:
Phone temperature sensor not working - Charging slow - How to fix?
Recently, something has happened to my phone's temperature sensor. It's showing ridiculously high values for the temperature (over 100 degrees), even though it's very cold. This has caused my phone to refuse fast charging, and it charges very, very slowly. (~7 hours to charge)
Is there anyway I could turn off a sensor or fake its value so that my phone charging returns to normal?
Or is there anyway to force the phone to ignore the thermal limits during charging? (I know it's dangerous but I have no choice)
Deleting the thermal engine file doesn't fix the issue.
P.S: Android 10 | Qualcomm chipset | Rooted + Xposed

You have not mentioned anywhere that you have root access but since you've added aa root-access tag i'm assuming you have root access.
Sensor disabler is what you are searching for. Just be careful!
P.S.: Take a look at this too https://forum.xda-developers.com/moto-maxx/help/how-to-disable-temp-sensor-t3504585
Generally in all phones temperature is the battery temperature and as far as i have read in many threads this is rare and indicates terrible hardware issue. And there is no way to change the value. There must be a way to bypass the temperature check though. I'd recommend you to go to a shop and get it diagnosed.

Thanks for the reply.
Yes I have root access.
The app you mentioned doesn't have any options for the temperature sensor.

Generally in all phones temperature is the battery temperature and as far as i have read in many threads this is rare and indicates terrible hardware issue. And there is no way to change the value. There must be a way to bypass the temperature check though. I'd recommend you to go to a shop and get it diagnosed. Comment when you see this. I'll delete my answer

Thanks. No need to delete it. It might help someone else with a sensor problem.
Of course my #1 thought was to get it repaired, but I couldn't find any official support center for that brand in my country.


text:
My Galaxy Tab A SM-T510 won't unlock security screen with correct code or thru find my mobile unlock
My tablet won't unlock screen with correct code , clicks into wait try again in 29 seconds . Using the find my mobile site try to unlock screen that way , comes back with Something went wrong and does not unlock. Any other way to get into it without having to do a hard reset

unfortunately besides the official methods there is no other way. even bruteforce attack makes no sense because you already know code. i recommend to wait 72 hours and try again


text:
How to remove rounded black corners which appeared after system upgrade?
I recently let my Nokia 3.1 to upgrade to Android 10.
I don't know if it's Nokia's will or Google's but rounded black corners appeared on my screen, and are kept permanently visible during any app runtime.
Is there a way to remove this feature ? I have found nothing in the system configuration menus. I also tried some app implementing custom corners but apart to add another layer of corners, it can't remove the ones I initially want to disappear.
Some pictures:

The rounded corners don't appear in screenshots.

Found this on reddit (thanks to "jyapayne"):
adb shell settings put secure sysui_rounded_size 1
adb shell settings put secure sysui_rounded_content_padding 5

First line is the corner "roundness" and second line ist the padding of the status-bar elements to the edge.
The Thread

link The sysui_rounded_size 1 removes almost completely the corners. The value 0 removes the bottom corners, top ones are unaffected. Negative values, "null", don't nothing. "default" value or deleting the key bring back the default corners. The source (I suppose it is) doesn't mention any other available key to turn the corners off completely.


text:
what can i do to bring back to life mi samsung galaxy a 51?
Days ago my phone restarted and stopped on the android/samsung logo.
i tried to do a hard reset on the recovery menu, but when the process finished the phone stopped on the android logo again. i did this process many times but it happened again.
after that i tried using Odin3 to install an official firmware, the process finished successfully, but when it restarted again stopped on the logo. i turned off the phone with the power off and volume down buttons, then i used the recovery mode (i tried to much to access to it, i was thinking that i cannot access to) combination keys, i did the hard reset again, and it showed the charging icon (seems to be frozen with no animation, some times happens). i cant turn it on disconnected to the pc or charger.

how old is that device?

6 months at least

Please claim it to seller under warranty we can't help you


text:
Backup MMS on Android without Google Play Services
Is there a way to backup and restore MMS without Google Play Services? I'm running Graphene OS on a Pixel 3 (no root). Thanks in advance!

Maybe using one of the SMS/MMS Backup & Restore apps? I've never tried them (myself, I use TitaniumBackup, but that requires root). Note 2 of the apps in the list are available via F-Droid; but Epistolaire cannot restore (it just backs up to JSON), and SMS Gate backs up to IMAP (I found no word on restore), so you're probably left with side-loading one of the tracker ridden candidates…


text:
"Screen Recording" in LG Android
I have an LG V40, and in both Android 9 and 10, it seems that the "Screen Recording" app is always running, and not possible to keep it Stopped.
Greenify shows it as running in "Foreground":

If I force hibernation, seconds later it will be running in Foreground again.
It is not possible to disable this app, and it requires access to Camera and Microphone:

These permissions cannot be removed either:

Should I be concerned?
Is there any way I can fully disable this app?
My OS is European.

Hello. Unlike forums, our site follows a Q&A approach, and we also allow self-answering the question. You can choose to tick the check mark on the answer below if it has helped you out, or you can post a solution "as an answer below" that has worked for you. :-)

@Firelord - I know that... I was simply adding the output of the commands for reference, since I can't add to the comments below. Was it really necessary to remove it?..

@Firelord - and I don't agree with marking the question as Duplicate. The other question is about disabling apps downloaded in Google Play, without uninstalling them. That's NOT what I'm asking here. I wish there was a way to report these unnecessary changes by moderators..

Your edit about the error in the command was in response to the suggestion you received from user Aayush. However, in the comments on the answer, you later was able to resolve the issue with that suggestion. Since Aayush edited his answer to reflect your findings (the correct command that would not give the error and would work, that is), there is no value in keeping the error related info in your question.

I disagree with your disagreement about duplicate question. Whether an app is third party or a system app the answer to the linked question works equally on them. For what it is worth, one can just edit the title there from 'third party' to 'system' apps and the answer would remain applicable, valid and useful.

Use adb to disable the app. And download a trusted  screen recorder.
For installed apps:
adb shell pm list packages should list all the packages on your device. Then use adb shell pm disable <package_to_disable>
to disable an installed app.
For system apps:
For system apps just the disable command is different  adb shell pm disable-user --user 0 <package_to_disable>
if you want to see the disabled apps use adb shell pm list packages -d
Take a look at this https://www.xda-developers.com/disable-system-app-bloatware-android/

Thank you. Unfortunately, that doesn't seem to work. adb shell pm disable com.lge.gametools.gamerecorder : "Security exception: Shell cannot change component state for com.lge.gametools.gamerecorder/null to 2". I put the whole output at the end of my question above.

Aah - this worked: adb shell pm disable-user --user 0 com.lge.gametools.gamerecorder : "Package com.lge.gametools.gamerecorder new state: disabled-user". Exactly as per what the article says :) -- if you edit your question to put "disable-user" instead of "disable", I'll mark it as accepted. Thanks!!

Glad to help  ;)


text:
How can I find / transfer a single app's data files to a new phone? (unrooted)
I just got a new phone and I was able to have almost all my apps and data transfer over without an issue. Neither phone has root access.
But a couple apps (a game, a cocktail app) didn't transfer their data and don't have sync options.
I've looked through File Explorer but I can't seem to find an obvious folder for app data. I swear this used to be accessible but I assume it got changed around at some point.
I have dev knowledge so if I need to use adb or something I can. That said, ideally I can do this wirelessly because the old phone can't seem to be found by my computers.

How do I find the data files for an app?
Once I have the files, are there any extra steps beyond copy/paste like permissions or using adb?

Does this answer your question? Transfer Android app with offline data to NEW PHONE without ROOT

I'll check once I'm back with my new phone. Is there really no way to just do it myself through the file system? It has to be an app or adb?

https://android.stackexchange.com/q/47924 you don't have access to file system not even read access


text:
SoC compute-resource usage monitor for single app
I need to understand the compute resource usage of a compute-intensive app; this includes the CPU (ideally including the core ID), GPU, DSP, AI Engine in the processor (for Quallcom chips). I have found many ways to track the CPU usage per app, but am yet to find one that tracks the GPU or DSP usage per app.
What can I use to monitor the compute-resource usage of an app?

Can the device be rooted or not?

Preferably not, but I'm willing to explore that option.

@MorrisonChang I'm willing to root the phone, would it be possible to get that information?

The more custom (DSP/AI engine) stuff may require access to SOC SDKs, but if rooted, look into https://developer.android.com/training/testing/performance


text:
What to do if my legacy device gets slower when Xposed Framework is enabled?
I'm using Xposed Framework 89 ver. on my Android 7.1.2 AOSP custom ROM: AOSiP which makes it slower but once I disable it my phone gets faster than the state of enabling. What can I do? Is there a lite version of it?

Is the device slower by your perception or is it only slower in some benchmark? Unfortunately the Xposed framework is designed to hook the central Dalvik-VM which is used (forked) by every app. Hence a little bit lower speed is excepted having Xposed installed. Usually with Xposed installed (without any modules) the device should not get much slower, however if you have a badly designed Xposed module this can be the cause.

It seems a little after a downgraded its version from 89ver to 88ver.


text:
Package manager has died while checking permission
Caused by: java.lang.RuntimeException: Package manager has died at android.app.ApplicationPackageManager.checkPermission(ApplicationPackageManager.java:427)
Caused by: android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
Can anyone help me what does this mean and how to prevent this?

A DeadObjectException can occur if two Android processes are communicating with each other and one of them dies while transferring data to the other. The other process will then throw a DeadObjectException.
In your case the "other" process was the PackageManager process which was communicating to a second process - may be a system service for listing packages?
There is not an easy solution how to prevent such an error. The only chance you have is by checking the adb logcat output for errors when you access the package manager.
The reason why the other process (whatever process it is) fails may be corrupt data.


text:
How to flash a custom rom on galaxy on5 pro
I'm an Android fan and I have a Samsung Galaxy On5 Pro.
It is currently running Android Marshmallow 6.1.
I want it to get upgraded to Android Nougat 7.1.1.
I don't have a recovery.
How can I install TWRP?
How do I do it?
Edit:
I got TWRP and installed android nougat 7.1.1
How do I install android 8.1?

Root your device at your own risk!

Check your device model number. (for SM-G550FY/SM-G550T1/SM-G5500T2/SM-G5500 only)
Select TWRP Based on the mobile model number.
Make sure your device battery is charged above 50%
Backup your current files and data, just in case (save them on external storage).
Flash TWRP using odin
Install SuperSU.

For detailed information see https://www.androidinfotech.com/root-samsung-galaxy-on5-sm-g550-lollipop-marshmallow/ and https://rootmydevice.com/root-samsung-galaxy-on5-pro/


text:
fastboot commands work. fastboot oem commands hang
My final objective is to do "fastboot oem off-mode-charge 0".  I've done this successfully with a Teclast P80H.  But I'm having trouble with a rino3 pro.  Specifically:
"fastboot devices" shows me "mt6572v1_phone fastboot" and "fastboot --version" shows me "30.0.4-6686687".  "fastboot reboot" works.  "fastboot reboot bootloader" works.
However, "fastboot oem " seems to never return back to my Windows Command Prompt.  It seems hung.  "fastboot oem off-mode-charge 0" hangs.  I must control-C to get out.  "fastboot oem device-info" hangs.  "fastboot oem junkyjunk" hangs.  It seems that ALL/ANY "fastboot oem" command hangs.  ("fastboot eom" with no following command, of course, returns "fastboot: usage: empty oem command.)
Well, maybe it's not strictly oem commands that hang.  "fastboot flashing get_unlock_ability" seems to hang as well.
My device is a rino3 pro.  Android Settings tells me "Hardware: MTK6763" and "Processor: 8 core" and "Android 9.1" if that matters.

fastboot oem commands are (as the command implies) oem/manufacturer and often even device specific.

your device looks like a scam. it is most likely a fake phone with dummy camera, 512MB of RAM, 4GB of storage and android 4.2.2 https://android.stackexchange.com/q/130278

Oh, hello @alecxs.  You responded to my other post as well.  That would be funny if it's a fake phone with dummy camera.  My product does not need to use either of those!  That would make the fake actually perfect!  The GUI and USB do operate.  Please see my other message at https://android.stackexchange.com/questions/230362/fastboot-not-working-with-new-teclast-p80h?noredirect=1#comment302886_230362


text:
Can I access the Memo data without rooting?
I basically need to do two things with my Memo notes, which I was unable to do with any simple means:

backup all of them to a file on my PC (to the hell with cloud backups, I wasn't able to get my own files out of there)
get access to the full creation date/times (the Memo app will only show date for older notes)

I tried but haven't found any easier way to accomplish this, so I concluded that the only way is to get the internal data files which the Memo app uses (and try to open it somehow).
Is it possible to somehow get that file(s) without rooting the phone?
I don't know how the permissions on non-rooted phone are set, but could another specialized app be able to fetch that file? I tried to use Total Commander app and to look up different directories mentioned e.g. here but I didn't find anything.
I want to avoid rooting if possible since I heard it's a big operation, laborous and risky.
I have Samsung S7 with Android 8.0.0.
EDIT: I was able to transfer (using Samsung Smart Switch on PC and phone) the file named memo.nmmm to my PC without rooting! But only transfer, not open! So now:

Is this file how it is stored on my phone, or if it was created by the Smart Switch app?
How do I open this memo.nmmm file? It doesn't look like any known file type, file(1) on Linux doesn't recognize it:

analyzing sqlite databases is a hassle, using the app which created that database is your best option. nevertheless you can create adb backup of app and extract it, but DB-Browser-for-SQLite or SQLite-Explorer can not read everything, afaik only Sanderson-Forensic-Toolkit-for-SQLite will handle it. but you will have more fun with XML memos Opening .memo files from Samsung default memo app (btw rooting involves factory reset you would lose all data)

@alecxs 1) the sqlite was just a guess.. unfortunatelly the file doesn't look like any known file type (see updated Q), which also rules out the .memo question (probably slightly different memo app on different phone/system version). 2) "nevertheless you can create adb backup of app and extract it" - this is interesting! So I can get to the app data without rooting? How? See if I can get something better than this damn file. Thanks!

no, adb backup only contain sqlite database. How can I access the files in "/data/data" and copy them into memory card without root?

https://www.staff.hs-mittweida.de/~pawlaszc/fqlite

I have the same desire to backup all my Samsung Memo data in plain text on my computer. I also used Samsung Smart Switch (using default settings) to transfer the information to my computer, then found there was an opaque memo.nmmm file.
I renamed memo.nmmm to memo.zip and found I could extract the archive successfully.
This extraction output three files:

memo.bk
SmartSwitchBackup.json
SSMDummyValue.exml

The JSON file is plain-text, but doesn't seem to contain Memos. I assume that the other files are encrypted, because I couldn't read them. I assumed that exml stands for "encrypted xml", so it's probably possible to brute force the decryption key by searching for the <?xml version=" string.
It seems the researchers here had a similar idea. They apparently developed a decryption tool as published here but the full-text PDF is not available for public download. Sadly, I could find any public tool that decrypted my local data (I did try this but the most recent software did not work as claimed - perhaps an older version of the software might do what the article says, but I didn't pursue that - yet).
However, realising that the publications by the researchers above showed that there's both PIN-based and default encryption for the backups (both happen on the phone before the data is transmitted to the computer, as per their diagrammes), I realised I should actually look at the Smart Switch settings to see if there's a way to remove the encryption settings.
On the phone, open Samsung Smart Switch app.
Press the vertical-ellipsis "kebab" menu:
⋮ → Settings
which takes you to
Smart Switch Settings.
Under the Security heading, there is an External storage encryption option which contains:

Secure with Samsung Account
Secure with password
No encryption

I changed the setting from the first option to the last option and ran Smart Switch backup again.
Sadly, it doesn't seem to have made the files much easier to read. It still outputs the opaque memo.nmmm archive and that still extracts the same three files, with the same file sizes each. Between the first encrypted output and the second unencrypted output, I ran a binary diff on the memo.bk and SSMDummyValue.exml files. The memo.bks are completely different, but the SSMDummyValue.exmls are the same except for the last third of the file. The SmartSwitchBackup.json files didn't text-diff well until I auto-formatted them and then it was obvious they were identical.
So, my remaining options are

wait for the authors of this to respond to my request for the full PDF (but I am not with any institution, so someone else might have better chances) to see if it contains any software that may help decrypt the Memo files
try to obtain an older version of this software, perhaps by contacting those forensics experts
try to brute force decrypt the SSMDummyValue.exml file using the encryption methods mentioned in the aforementioned forensics publications

All of these options take more time than I have right now, so I thought that I would post my current findings here in case it helps someone reach the next steps. I will update my answer later when I have found a more full solution.


text:
Android cannot forward packets
Target:
Perform IP forwarding for devices within the same local network. (The real target is transparent proxy but the IP forwarding is a prerequisite)
Network setup:
All devices are in the same local network 192.168.0.0/16.

main router 192.168.1.1
Android phone 192.168.2.1 (network interface wlan0)
computer 192.168.2.10 gateway set as 192.168.2.1
others like Raspberry Pi at 192.168.1.11

Android setup:

Data disabled, only WiFi connects.
rooted Android 10 (Pixel 2 XL)
enabled ip forwarding by sysctl -w net.ipv4.ip_forward=1
netfilter: on all tables of nat, mangle, filter and raw, run iptables -F -t <table_name> and iptables -X -t <table_name>
rp_filter: Disable by sysctl -w net.ipv4.conf.all.rp_filter=0 and sysctl -w net.ipv4.conf.wlan0.rp_filter=0

Result:

the computer cannot access to the Internet, ping, dig, browser, nothing works.
the computer connects to local devices without any problem (like ping router 192.168.1.1, SSH to the Raspberry Pi, or use FireFox through the SOCK5 proxy hosted on the Pi).
Android phone connects to the Internet perfectly.

Debug:

using iptables -t <table_name> -L -v to show packet count, all chains have some packets, *except the FORWARD chain of both raw, mangle tables shows Chain FORWARD (policy ACCEPT 0 packets, 0 bytes). After some googling, rp_filter is the suspect but I'm sure it's turned off.

NetFilter (iptables) operates at higher OSI layer. What about IP routing (ip rule and ip route)? Are they set up correctly? Android doesn't use main table by default, unlike normal Linux distros. Related: How to send all internet traffic to a SOCKS5 proxy server in local network? and How to port-forward internet using Android Hotspot to PC?

Thanks to @Irfan Latif, I found the solution myself.
It's right that packets are sent to the last unreachable rule of ip rule, because they fail to match any previous rules:
# result of `ip rule`
... (no rules match)
22000:  from all fwmark 0x0/0xffff iif lo lookup wlan0
32000:  from all unreachable

So I added a rule to route incoming traffic from local network to route table wlan0 by:
ip rule add from 192.168.0.0/16 iif wlan0 table wlan0


text:
Is it possible to add insurance cards to Google Pay?
I just received a new insurance card and would like to keep it in Google Pay. It's not a debit card that can be scanned as a method of payment; I would just like to keep digital copies of all of my cards in a single place on my phone. My State Farm app gave me the option of saving a copy of my car insurance to Google Pay, and I'm hoping there's a manual way to do this for other cards.
I've tried using the Add Pass feature, but there doesn't seem to be an option for just uploading an image.

It would be Google Wallet and not Google pay, but that's what I want to know too.


text:
How can I restore a local backup of WhatsApp to a specific data profile created using Titanium backup app?
In Titanium Backup app I have multiple data profiles for WhatsApp. I am using WhatsApp in 1st data profile and I need to restore a local backup of another WhatsApp number to 2nd data profile. How can I do it without uploading it to Google drive ? Where are the data of apps stored for each Titanium Backup profile ?

Did you ever manage to resolve this?


text:
How do I toggle grayscale in Android 11?
In Android 10 I had grayscale display turned on. This was achieved by dragging editing the dropdown shade to add the Grayscale tile.
I just updated to Android 11. The display is still in grayscale, but the Grayscale tile is removed, so there doesn't seem to be any way to turn it off! I sometimes want to when using the camera, but then switch back to grayscale for day-to-day use. How can I toggle grayscale in Android 11? Moreover, is there a quick way to do so? The old way (pre-Android 10) involved turning on developer mode and changing a deeply embedded developer setting.

EDIT: There is a new Bedtime Mode tile. When I turned it on and off, color was restored. Turning bedtime mode on goes into grayscale, but also sets Do Not Disturb. So I can turn on grayscale only be entering bedtime mode and then turning off Do Not Disturb. This is less than ideal. Also, bedtime mode only lasts till the following morning. Is there a way to either (a) recover turning on grayscale without bedtime, or (b) change bedtime mode to last until turned off?

Actually you can schedule and customize the Bedtime mode.
If you long press the Bedtime mode tile, it'll open the Bedtime mode screen.

In the schedule option, select all the days and in the time select 00.00 to 23.59, so as to keep it on almost the whole day(max. possible time - 23hrs 59 mins a day).
If you tap the Customize option, you can see a way to turn off the DND mode.

That's it, done! Now you can simply tap the Bedtime tile and it'll remain on
Once you've done this, you need not turn off DNS, while enabling Bedtime mode, as it's customized now.

A small point: Bedtime mode turns off an hour before if you've set an alarm, say you set an alarm at 5.00 a.m. Then, the screen turns back colorful at 4.00 a.m. And if you set an alarm daily at that time, schedule bedtime from say, 5.05 to 5.04 or so

A bit of a hack. This mostly works, but the final "small point" is an annoyance. What if I have multiple alarms during the day, e.g. to wake up in the morning but also for recurring events or meetings? Is there any way to change bedtime mode behavior to not exit one hour before an alarm?

@LeeHachadoorian I think in that case, we have manually tap the bedtime mode after each alarm. I think we can't stop it to not exit before an alarm. It's generally an-hour when I use the "System clock alarm" but when I set an alarm using "Google clock", it turn off exactly at the time when the alarm is kept. So may be you can get rid off that one-hour time. But, yeah it turns off at the time of alarm

This guy in reddit has a great approach: https://www.reddit.com/r/GooglePixel/comments/9w4xc8/easy_toggle_between_monochrome_and_color_display/
He shares that the Accessibility feature in Android has the ability to easily toggle monochrome in Android 11, even if there's no shortcut available from the pull-down menu. On my Pixel 3, I go to Settings, Accessibility, look for Color Correction, and turn that on to get black and white. Then scrolling down in the Color Correction menu, under Options, select "Color correction shortcut" to either swipe up with two fingers to toggle between monochrome and color, or hold both volume buttons. Enjoy!

The post linked does not say that this applies to Android 11, and the method described does not appear to describe or work with Android 11. I'm pretty sure that this applies to Android 9 or earlier.

Good point, his post is from 2 years ago, but both methods that he mentions (dev mode or accessibility) work for me on my  Pixel 3 with Android 11. I don't see the same thing on my Samsung M8 tablet, so maybe this is only for order phones. On Android 11, if you go to Settings, then Accessibility, in the "Display" area, do you have a Color Correction row you can click on, where turning it on turns everything greyscale? I have it on my Pixel 3. Then the best part is having the Color Corrections shortcut, which is in the same Color Corrections activity.

@Sammy Cakes - I have Android 11 on a Pixel 4, and the color correction option you reference above only provide options to adjust color to compensate for different manifestations of colorblindness. I couldn't find a grayscale option which is composed of only white, black, and the shades between.

Pixel 3a on Android 12 has grayscale as one of the options for color correction. However, this might not apply to other devices since each manufacturer can customize many things, including developer options and accessibility settings.

You can turn on grayscale permanently from the developer options. Go to settings -> about phone -> software information -> click on build number repeatedly until you unlock developer options. Then go back into settings -> developer options and find "simulate color space" under hardware accelerated rendering. You can choose monochromancy there and it will greyscale your phone everywhere without turning off or relying on bedtime mode.

Pixel 3a on Android 12 has this menu. However, this might not apply to other devices since each manufacturer can customize many things, including developer options and accessibility settings.

Going along with the first answer @19aksh
You can an add a quick toggle.
So when it's clicked, it just goes into greyscale only, leaving out the no audio and time restraints.
This is a Xiaomi Redmi 10, Android 11

I was referring to the Bedtime mode.

Try this app.. https://play.google.com/store/apps/details?id=com.vegardit.grayswitch
Grant it the write secure settings permission through adb and change the settings accordingly.
And if you don't want to use a 3rd party app then try these commands..
  adb shell settings list secure (if not in this then try the other 2)
  adb shell settings list system
  adb shell settings list global

and see if there is a option of grayscale. If there is then.. adb shell settings put global <name> 0 to disable and 1 to enable back.


text:
Why is Wechat consuming a huge amount of storage
I am a very light wechat user, using it only for work to communicate with suppliers, yet my wechat constantly gets bloated, have had to clear it every month or so.
Below is an image with wechat consuming a large part of my internal storage.

Often people talk about the media taking most of the data, but this doesnt seem to add up with this image

Edit: The second ~13GB is also related to wechat, it is under com.tencent.mm/MicroMsg/xlog/...
After a app info -> clear storage it looks like this.

Did you try this.. Go to WeChat-->Me-->Settings-->General-->Storage clear cache and temporary files. Set auto-delete temp pics and videos after specific time if there is an option

You can see above the cache is 11kb. I am not a heavy user of wechat, and with 1 active thread with very low traffic i dont see 13 gb of media coming from it.


text:
How to send .apk file over mobile Gmail?
Since .apk is a regular executable file, I was more than sure that I will be able to trick mobile Gmail in the same way as I was able to trick PC version of Gmail years ago to force it to send a PC executable (.exe) which it prevented as well. Turned out, I was wrong.
Usually changing file extension to .dat or some other or compressing it with password (encrypting  file) was enough for PC version of Gmail.
However, for mobile version, everything that I have ready at a hand and tried failed as well:

sending as plain file (obviously),

changing .apk extension to .dat or some other,

compressing with ZIP with no password,

compressing with ZIP (ultra compression) and encrypting archive with a password,

compressing with 7ZIP (ultra compression) and encrypting archive with a password,

using an 7 years old idea of double compression:

compress .apk file into .zip file without password,
compress resulting .zip file again into another .zip file with password / encryption.

If mobile Gmail is able to detect that I am sending .apk executable file even in 7zip compressed file with password (or it can prevent me from sending such file for any other reasons) do I have any option left? Is there any way to send .apk file over mobile Gmail (attach them to message composed in mobile Gmail)?

If you pack it with 7zip and enable filename encryption everybody need to know the password to read anything from the created archive. Please note that your question is off-topic here as it can be shortened to "How do I send any data via GMail in a way that it can not be read by Google".

Are other methods acceptable? Most of us just upload the APK to Google Drive, use the Share link, and state it on Gmail...

Try GPG encryption.

@Robert I totally agree with you (on both solution and the fact that it makes my question off-topic), so I'll most likely VTC my own question as well. However, to clarify. Not every 7zip client offers this option. The one that I am currently using (Solid Explorer 2) does not. It only password-protects 7zip archives but does not use filename encryption and so, such files fails on Gmail.

@AndrewT. This is the thing that irritates me the most in the whole picture. I cannot send certain files, because Google prevents me from doing so, because it knows better than me that they can be harmful. In the same time it allows me to upload such file to Google Drive and share a link to it. Either I am missing some key point here or this is totally wrong. This only changes channel (from delivering potentially harmful payload via attachement to a link), but the security concerns remains.

@IrfanLatif as in answer to Robert -- my file and folder browser does not offer such option. The same as encoding payload as base64 etc. Compressing files (with or without password, but without filename encryption) with 7zip or zip are the only options that Solid Explorer 2 offers.

@trejder sir blocking .apk files and encrypted archives as email attachments is clearly mentioned in GMail policy: https://support.google.com/mail/answer/6590. No one here can help you with that. Better ask Google. What I suggested is definitely going to work (if email attachment is the only option you want to go with). It's because GPG encryption is very common in emails. Don't limit your options. Some explorer app can't be the ultimate solution to all of your problems. You may look for something else. E.g. use Termux or OpenKeychain for GPG/PGP encryption. Both are open-source and free.

Blocking .apk files and encrypted archives as email attachments is clearly mentioned in GMail policy:

To protect you against potential viruses and harmful software, Gmail doesn't allow you to attach certain types of files, including:
...

Password protected archives whose content is an archive

To protect your account, Gmail doesn't allow you to attach certain types of files...:
.ade, .adp, .apk, ...

So no one can help with that except Google. You can go with file sharing as suggested by others here, and Google as well:

If you're sure the file is safe, you can ask the sender to upload the file to Google Drive. Then send it as a Drive attachment.

Source: https://support.google.com/mail/answer/6590
But if email attachment is the only option you want to go with, use GPG/PGP encryption which is very commonly used in emails, even to encrypt whole emails including subject and body. Many e-mail clients provide OpenPGP-compliant email security. On Android you can use Termux or OpenKeychain for GPG file encryption. Both are open-source and free (I've no affiliation with either).


text:
How to change a thermal printer’s Bluetooth baud rate?
I want to print image using thermal printer through Bluetooth from Android device.
I connect Android phone to printer (printer model: XP-318B/XP-318BM) through Bluetooth then by using BluetoothPrint app I send command to print image, the printer started to print a part of image then it stopped for half second and than it resume printer then it stops for half second then resume and it continues like this until it finish printing the image, white rows appear at the places which the printer was stopping as in the image.
First, I thought it was a programming issue, so I connect the printer though USB and then printed the same image it perfectly printed, so I'm thinking it is the baud rate of the printer's Bluetooth.
I search for two days with out any good results  how to change the baud rate.
I found these tutorials, but I couldn't change the baud rate .

“Instruction of Change Baud Rate for Bluetooth Printer (To 115200bps)”
“How to Set Baud Rate for 58mm Thermal Printer”

What can I do?

You state, "I found these tutorials, but I couldn't change the baud rate." What did you try? Did you use Bus Hound? Did you use IPrinter software? Were there error messages? What else have you done?

Have you tried printing a lower resolution image?

I confess that I do not understand was a baudrate is, in relation to Bluetooth. The baudrate make a sense in relation to a serial interface, like RS-232. Bluetooth and USB have their own timing. Only when a serial converter is used, the baudrate has a significance.

Thank you for reply  DrMoishe Pippik.  yes, I did as the steps says even Bus Hound software said complete after pressing run button, but nothing changed, I also used Iprinter tool it connect to printer and I can print (print Test) from Iprinter, but when it comes to set baud rate nothing happen.

thank you for reply  Mokubai . it is already low, the printer has the capability to printer it I tried it with USB and it print the same image perfectly  fast and accurate.

Hi  Claude Frantz, yes even Bluetooth has Baud rate as serial.

Bluetooth is a pretty low bandwidth link to begin with. It can maybe do a theoretical maximum of 2 megabits while USB 2 can do 480 megabits.

Please connect the PC via Bluetooth to the printer. If it still does not work, the problem is unrelated to Android.

Mokubai - I have other printer (GOOJPRT  PT-210) work also with Bluetooth can print image without and mistake, this mean Bluetooth technology got the ability to print.

Robert - I did try with PC Bluetooth I got same result as android. yes it unrelated to android it related to hardware of Bluetooth (baud rate setting)


text:
Rooting Huawei mediapad T3 7 Wifi
I want to flash magisk on my device but i haven't been able to unlock the bootloader. I was wondering if i could patch the boot.img of the firmware file i found online then flash it with spflash tool. Would it work? Has anyone tried this?

Since mid 2018 Huawei does no longer allow to unlock devices, hence rooting Huawei devices has become extremely difficult. https://www.xda-developers.com/xda-huawei-decision-stop-bootloader-unlocking/

if SP Flash Tool can by-pass secure boot and flash it that will work. in Magisk Manager Advanced Settings enable keep avb/dm-verity preserve force encryption. but do a readback first for backup purposes

another method try mtk-su not sure it works for MT8127

or buy unlock code from dc unlocker


text:
Understanding the sending of commands in adb shell
I am trying to talk to the modem embedded within a module through adb shell but since I'm accessing the HW remotely, i'm not sure of the original setup and may need some help clarifying:
adb shell runs in linux and following is how I was able to run the command:
cat /dev/smd0 &
echo -e "AT\r" > /dev/smd0

what's the main point behind the first line with &? Doesn't that run things in the background? How does removing it not output the result to the terminal?
the interpretation of the second line: writes/sends the string to the application processor from the linux host over smd0 AT port. Is that legit?

Your question is about communicating with modem, not simply ADB shell. Communication with modem is very hardware specific and mostly closed-source, undocumented, not available for public use. Do mention your hardware specs. Also XDA and other forums are more suitable places for such kind of hacking stuff.

the 2nd line sends a request to serial. the 1st line is waiting for result. in order to make this work one must listening before sending request, that way the answer can not missed. one can accomplish that by running the listening process in background while sending request in same time. it is usual like for handling of named pipes