text:
How to unpack/repack system.img of android ROM?
I have OnePlus 6T device which has A/B partition system and has a ROM of user type i.e [ro.build.type]: [user]. This device is rooted with Magisk. I have a requirement(Want to place customized sepolicy file under system_root directory) to modify system.img.
I have tried different tools like:

simg2img :

OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/img-tools$ ./simg2img system.img sys.raw
Invalid sparse file format at header magi
Failed to read sparse file
OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/img-tools$

imgtools

OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/imgtool$ sudo ./imgtool system.img extract
[sudo] password for OMEN:
system.img is not a recognized image. Sorry
OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/imgtool$

and more tools even on windows..

but none of them is capable of parsing my system.img.
I have copied system.img directly from OnePlus6T ROM setup which installs Android 9 on this device without any issue.
Any help on:

How to fix the system.img so it will be extracted and repacked fine?
Any command that can unpack/repack system.img?
Any working tool to accomplish this task?

Update 1: I have run file system.img and I found that its ext2 image and the tools support ext4.
system.img: Linux rev 1.0 ext2 filesystem data, UUID=d09c08e9-628d-590e-a610-3a14de2a8db0 (extents) (large files) (huge files)

Update 2: Tried to find the magic number and have following result:
OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/imgtool$ xxd system.img | head
00000000: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000010: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000020: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000030: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000050: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000060: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000070: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000080: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000090: 0000 0000 0000 0000 0000 0000 0000 0000  ................
OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea/imgtool$

Update 3 Fing the image already unpacked. So to add the required file, I have mount the image as sudo mount -o loop system.img system_mount and then tried to copy the contents to another folder with cp system_mount/* system/ so that I can add the required file and make new image out of it but I got following errors:
root@OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea# mkdir system && cp system_mount/* system/
cp: omitting directory 'system_mount/acct'
cp: cannot stat 'system_mount/bin': No such file or directory
cp: cannot stat 'system_mount/bt_firmware': No such file or directory
cp: cannot stat 'system_mount/bugreports': No such file or directory
cp: cannot stat 'system_mount/cache': No such file or directory
cp: cannot stat 'system_mount/charger': No such file or directory
cp: cannot stat 'system_mount/charger_log': No such file or directory
cp: omitting directory 'system_mount/config'
cp: omitting directory 'system_mount/d'
cp: omitting directory 'system_mount/data'
cp: omitting directory 'system_mount/dev'
cp: cannot stat 'system_mount/dsp': No such file or directory
cp: cannot stat 'system_mount/etc': No such file or directory
cp: cannot stat 'system_mount/firmware': No such file or directory
cp: omitting directory 'system_mount/lost+found'
cp: omitting directory 'system_mount/mnt'
cp: omitting directory 'system_mount/odm'
cp: omitting directory 'system_mount/oem'
cp: omitting directory 'system_mount/op1'
cp: omitting directory 'system_mount/op2'
cp: cannot stat 'system_mount/persist': No such file or directory
cp: omitting directory 'system_mount/postinstall'
cp: omitting directory 'system_mount/proc'
cp: cannot stat 'system_mount/product': No such file or directory
cp: omitting directory 'system_mount/res'
cp: omitting directory 'system_mount/sbin'
cp: cannot stat 'system_mount/sdcard': No such file or directory
cp: omitting directory 'system_mount/storage'
cp: omitting directory 'system_mount/sys'
cp: omitting directory 'system_mount/system'
cp: omitting directory 'system_mount/vendor'
root@OMEN-by-HP-Laptop-15-dc0xxx:~/WorkArea#

Does the system.img you have start with hex 3AFF 26ED? If not check if the file header magic bytes is something known.

It is showing as 00 00 00 00.. Please check the Update 2.

Looks like the image is already unpacked.

Oh really :o So, how to add a file in this .img file?

Sorry, I thought that it is obvious to mount an ext2/4 file if you want to modify it.

Mounting has some problem. Let me add it to the question.

Are you sure the mount command failed? These messages look more like warnings to me.

use busybox cp -acv instead of cp if you want to preserve permissions. selinux enabled (x86_64) binary of busybox (works on pc) sudo mount -t ext4 -o loop,rw,noatime system.img system_mount works only when directory system_root exist in same location as system.img

@Robert because of your advice I downloaded Ubuntu and was able to extract all the files from the img file. Do you know how to pack it back?

These commands don't work always: sometimes the system_new.img size becomes greater than system.img.ext4 and hence it doesn't flash on the device. As per my knowledge, the new image size should be equal to or less than the size of the original system image. ---- If anyone will be able to determine the new commands then please share it.
To Unpack-Modify-Pach the system.img, I have followed the following procedure:
a) Unpacking

Run file system.img and make sure that system.img is Android Sparse Image.
Rename system.img to system.img.ext4. // Not required if you will use other name for raw image in below steps.
With simg2img system.img.ext4 system.img, you will get a raw image file named system.img
With mkdir system, create directory to mount system.img
With sudo mount -t ext4 -o loop system.img system/ you will get all files of system.img in system folder

b) Modifying

With ls -l system/init.rc note permissions: 750
With sudo chmod 777 system/init.rc give write permissions
With sudo echo "#MODIFICATION " >> system/init.rc done some modification in init.rc
With sudo chmod 750 init.rc reset init.rc to the noted permissions

c) Calculate system sector size

With tune2fs -l system.img | grep "Block size\|Block count" you will get block size and count
With echo $((1553064 * 4096)) multiply both results. I got 6361350144

d) Packing

With sudo make_ext4fs -s -l 6361350144 -a system system_new.img system/ you will get system_new.img “Android Sparse Image” that has all changes

Getting 'can't set android permissions - built without android support' error when executing the packing command. Any idea?

Never get this error. Probably using another(or previous version of) make_ext4fs tool can resolve your problem.

Thanks for your response, Could you please tell me what is the 'sys/' mentioned in the tail of the packing command means?

It should be system/ means the folder in which raw system.img extracted. Fixed it in the answer as well.

These commands don't work always: sometimes the system_new.img size becomes greater than system.img.ext4 and hence it doesn't flash on the device. As per my knowledge, the new image size should be equal to or less than the size of the original system image. ---- If anyone will be able to determine the new commands then please share it with me too.

Maybe it is just that you need to specify a bigger size when using the -l flag. The file provided should be the total size needed to store the whole new folder.

Easy and it works:
truncate --size=3000M system.img
mke2fs -t ext4 -L system_rw system_rw.img
sudo mount system_rw.img
sudo cp -R --preserve=all /path_to_the_ronly_system.img_mountpoint/. /system_rw_mountpoint

Example for cp: sudo cp -R --preserve=all /media/user/_/. /media/user/system_rw/
That's all folks.

Use this tool on linux, I was able to extract the image of my emulator using ext4 on vm running ubuntu.
https://github.com/qmfrederik/extfstools
Still figuring out a way to pack it back.
Will update here once I am able to do it

Why not simply mount? Repacking is simple. Create sparse file with truncate. Do mkfs.ext4 and mount. Add files and umount. No special tools needed. But how would you preserve permissions, ownership, timestamps, xattr of files this way?

@IrfanLatif I don't know how to mount on VM. and b) I am noob at ubuntu. Installed vm last night. c) Until last night permissions etc were alien to me. I just need to run a small app on auto on a server on emulator so I don't think i need to worry about permissions but i do want to provide root access to some apps . Do you mind having a chat about it and helping me out ?

Chat on what? Ask a question specifically if not answered already. For Linux/Android basics do some research and study. I'm available to help if not available otherwise.

@IrfanLatif I am unable to create an image for android 7.1.1 which actually works on emulator. I am extracting image of an emulator as well.


text:
ADB shell gets "stuck" connecting to Samsung S10, must open other ADB shell to "unstuck" it
On Ubuntu, I often use adb shell and other operations such as adb push and adb pull over a USB cable.
On Nexus 5 it always worked perfectly. But since I switched to Samsung S10e I have this very surprising problem:

I open a terminal on my laptop, run adb shell.
I type normally in ADB shell (ls, typing enter, etc), the expected output appears.
As I continue typing, suddenly my typed character is not shown, as if the USB connection was stuck.
I have found a strange workaround: When that happens, I open another terminal and run adb shell in it.
Immediately, that "unstucks" the first terminal, and the "stucked" characters appear.
Now I can use the first terminal again, until it gets stuck again.
When that happens, I type a few characters in the second terminal, and that solves the problem again.
Inevitably as I repeat the trick several times, the second terminal gets stuck too.
When that happens, I open a third terminal, and that "unstucks" the first and second terminals.
Etc. Sometime I need to open a fourth terminal.

This also happens with other ADB commands.
Question: How to investigate the problem? Is there any Android setting that could mitigate or even solve the problem?

only when battery is 100% or always?

@alecxs: Always.

Hm.. i have this when connected adb over wifi when device goes to sleep

i guess we can assume the reason is related to this? https://android.stackexchange.com/questions/216103

@alecxs: The moisture problem started 16 days ago. On the opposite, the present problem has existed since the day I bought the phone (several months ago).

any news on this? I'm having the same problem with a Galaxy S9

source: Stack Exchange

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

sort: votes


text:
Recent apps getting closed without closing them
Samsung S9 -
In the recent apps view, the apps that were used recently are getting closed automatically.
If you do not use an app for more than one hour, then the app gets closed.
My phone forced me for an update, but after the update the apps in the recent apps view were getting closed automatically.
In the previous versions / before the update, I manually needed to close them in the recent apps.
How to prevent the apps in the recent apps not to get closed?
Steps to reproduce the issue:

Open 10 apps.
Go to the navigation bar.
Hit the recent apps button.
You can see the few of the applications that were used recently
Wait for a period of 6-7 hours/not to use the app in that time frame.
Most of the apps were closed automatically without closing them in the recent apps.

I found others with the same issue here

Basically Android is freeing up RAM space by killing the processes of unused apps. This is normal. It doesn't make sense to let an app process run for a very long time when the user is not using it actively. Why do you want to let the processes run until you close them manually? After one point of time, your phone will surely start crashing.

@WrichikBasu On of the application is a game that I was able to continue after a gap of 6-7 Hours before the update,  But now I need to work on the game from the start.  I tried to look into Device care -> memory, It only shows up to free up the ram / process used by RAM. nothing about keeping the app / process alive. even if it is not being used.

If Samsung allowed that before the update, either it was a bug, or the developers were mad. And this IS about keeping the process alive. Android automatically frees memory and kills app processes that the user has not used for long. The only way this can be changed is by the app itself. Even then, an app executing for 6 hours on the main thread is not acceptable at all.

@Wrichik Killing an app processes is common on Android, indeed. However if the OS kills an app it AFAIR remains in the recents list so that you can switch back to them. If you select such an killed app it starts again.

@Robert As far as my experience goes, selecting that app is like starting the app all over again.

Are there any official forms for Android / Pie OS where I can post this as an issue/Bug?

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


text:
How to view device kernel information (verbose)?
I need to view my device kernel info, in particular the architectures.  The device is not rooted, therefore uname command isn't available in local terminal, but cat /proc/version doesn't have an option to increase verbosity (that I'm aware of) like -a for uname.  Is there any other method I can use to see this information?

What device are you using? In most phones I have used, uname is installed by default. What information about the architecture do you want to access?

The getprop command has a number of values that are related to the architecture. Check out getprop | grep abi.

If it's the architecture that you are looking in particular, then from the terminal you can type arch command.
You can also try CPU-Z to check the kernel architecture on its System tab.
Note : The assumption that uname is only found on rooted devices is unfounded. I have a device not rooted on Android 8.1 that has uname thanks to toybox.

arch is not available via adb on my phone (Sony XA2, Android 9).

@Robert toybox is not installed on your phone? Or is toybox installed but arch has not been packaged with it?

Arctiic's question is about an unrooted device. Mine is unrooted, too. Therefore of course "toybox" is not installed. Installing such executables system wide plus PATH require a rooted device.

@Robert I think toolbox and toybox are part of stock Android, how would you get getprop and setprop without them. Nothing restricts apps executing /system/bin/uname -m or the uname syscall (including SELinux and seccomp). Also uname is part of every busybox release. Get one with Termux or place in /data/local/tmp and execute from adb shell. Multiple options.

@Irfan OK, you are right, there is a toybox and toolbox, however neither of them supports arch on my device (Sony XA2, Android 9 security update 2019-08-01).

@Robert same here. Busybox does have; it's also a wrapper over uname syscall.


text:
Installing rom zip through TWRP replaces recovery instead of intalling os
I formatted my Oneplus 6t and was able to install TWRP, but when I install the zip for LineageOS, instead of installing it as the OS, it just replaces the TWRP recovery with a Lineage one, and I am still unable to boot into system.
Log.txt

Possible duplicate of Why can't I write to recovery using fastboot on A/B device?

alright I actually figured it out: the trick is to flash the stock ROM using this tool and then fastboot TWRP, install the TWRP and then install Lineage all without formatting the internal storage. I don't know why that works, but it does.


text:
Is there any way to disable the repeated animation in the notification bar, for app update downloads?
I've just acquired an Android 9 phone.  It is part of the Android One scheme, so the software should be really stock Android.  I do not currently wish to install a custom ROM, or otherwise mod the OS at a root level.
I've turned it on, and obviously it started catching up with updates :-).
I don't like that it keeps showing an animated download icon at the top of the screen.  I don't want my attention repeatedly drawn to this, thanks.  (I don't know why anyone would?)
I have set "Remove animations" in the accessibility settings.  However, the animation still keeps appearing.
Is there a way to disable this animation?
Presumably I could go in "Manage Notifications" and disable Google Play Store, but...
I happened to notice that in "Manage Notifications", if I click on "Google Play Store" (instead of the toggle button next to it), I get a detailed list of notifications which I can disable individually.  Some of these look important.  I don't want to disable notifications that critical security updates have been released for Chrome, Play Services, and so on!
I can see seven "categories" of notifications.  Does one of these cover the animated download icon?  If so, what else will it disable?

High priority
Account alerts
App updates available
Updated apps
Security and maintenance
Connectivity
Device setup

I don't have Android 9, but if some of the notifications are like on Android 8, then you can try the following:

Open Settings -> Apps & Notifications. Click on "See all apps", then the 3-dot and select Show system apps.
Look for Download Manager, click on it.
Click "App Notifications" or "Notifications", then disable "In progress"

Note: You may find 2 Download Manager. One of them will have the notifications' categories listed.

Settings -> Apps -> All apps shows Google Play Services and com.google.android.apps.handwriting.ime, but it does not show Download Manager. Google Play Services has a category for "System update", which at least provides some reassurance, but nothing else relevant.

"Manage notifications" is equivalent to Settings -> Apps & Notifications -> Notifications -> See all from last 7 days. This shows a list of apps sorted by most recent notification. It includes Google Play Services. When the download icon was animating, I think the "notifications drawer" showed a notification from the specific app - Play Services for system updates, Play Store for app updates, and the same for the Map app when downloading offline maps.

@sourcejedi I find it strange that there is  no Download Manager listed among your apps even when you select to show system apps. Are you able to view the list of all apps installed on your phone?

Sorry, I hadn't followed your instructions correctly.

@sourcejedi The same notification is also present on Android 9. Did stop also stop the animated download icon?

Yes, thanks for the answer!


text:
Term for decoding symbols / icons
The top of the phone often has symbols to indicate features such as battery life, cell tower signal strength, wifi strength, etc.
Is there a commonly accepted term for said symbols?  Usually there is a list of symbols and the symbol's meaning.  This list should have a name: what is the name of this list?
The idea is that the term for said list would be found in the phone's manual, when trying to lookup what an unknown symbol communicates.

Are you looking for say IconA is usually called this, IconB usually called that, etc?

@ReddyLutonadio  Good question: I have tried to clarify the ask

Maybe kind of related:Complete list of Lollipop system icons shown in notification bar?

The right ones are status bar icons and left ones are called notification bar icons. This is what I have read anywhere. You would have hard luck finding out the meaning of many of those icons because OEMs do not keep their user manual either exhaustive or updated.


text:
Minimal way to always have screen on on Android?
I'm preparing a bunch of tablets using a minimal android OS (https://slimroms.org/).  And was wondering if there's a way to always have the display on (i.e. disable Sleep and Auto Screen lock) without needing to use third party apps.  I've got full root access via SSH and ADB etc - hoping there's some setting in /proc or as a kernel boot argument that I can make.
These are intended to be "We would like your feedback" tablets which are out on public display - so the display should never dim or lock etc. They're always going to be plugged in so power saving etc isn't going to be an issue.

Looks like WindowManager.LayoutParams.FLAG_TURN_SCREEN_ON could be a possible way (run from a cronjob or service ??) - however, looks like this has been deprecated in API level 27 onwards :-/.

Related or possible duplicate: https://android.stackexchange.com/q/207081/247431

Hmmm - a bit hacky but this might work: https://stackoverflow.com/questions/29072501/how-to-unlock-android-phone-through-adb

https://play.google.com/store/apps/details?id=by4a.setedit22

Set the 'keep awake while plugged in' setting
(Screen will never sleep while charging)
Settings - Developer options - Stay awake: on
or from terminal
svc power stayon true

if the user can press the power button, set the screen lock to "none" (not even swipe) and
use Tasker/MacroDroid/Automate to watch the power button. or run a watchdog from shell
the following example depends on three android binaries
/system/bin/toolbox
/system/bin/toybox
/system/bin/input
# (replace first line with while 1)
until [ $(($(toybox cat /sys/class/power_supply/ac/online)+$(toybox cat /sys/class/power_supply/*usb/online))) -eq 0 ]
  do
    case "$(toolbox getevent -lc4 /dev/input/event2 | toybox head -n1)" in
      *KEY_POWER*)
        input keyevent KEYCODE_WAKEUP
      ;;
    esac
done

the above code checks for charger is connected as entry point for the loop. the loop exit when charger is disconnected. /dev/input/event2 may vary for your device. you can check which input event has only 3x buttons [Vol+|Vol-|Pwr] from getevent -il (for more generic code look here)

Ugh - maybe spoke too soon.  After a certain amount of time (even with "Settings -> Developer Options -> Stay Awake On") the screen will dim, and dims almost to the point where you can't see anything.  A "tap" will bring the screen back to full brightness - but is there a way to maintain 100% brightness ?

not sure if there is a keycode for unlock. the only other harmless input event i can imagine is a mouse cursor moving (not touch/swipe) but the cursor might be visible

Actually another thought I just had - is there somewhere where you can set the "dim" percentage for the display.  E.g. If dim is going to 30% of the total screen brightness, can I set "dim" to 100%.  This way - even if the screen is going into "dim" mode it won't matter (i.e. no need to send 'tap'/'mouse'/'key' events to the display)

Hmmm - wonder if I can use some of the commands from https://github.com/Genymobile/scrcpy/issues/101 to achieve what I want (via the "adb shell settings put system screen_*" commands).  After looking at https://developer.android.com/reference/android/provider/Settings.System there seems to be quite a few settings that have been deprecated though.....

@PatrickRynhart if you use it in kiosk mode with very limited gui, just send a tap to corner every 15 seconds i don't think this harms much (will drop notifications). for more safety you can increase the display timeout up to 30 min and decrease the tap frequency (even tap outside of display will work) while [ 1 ]; do input tap 720 1260; sleep 15; done

Thank you - yes we're using them for kiosks.  Will try this out but this looks like a good workaround.  Thank you - Patrick


text:
Settings keep resetting after restart Oppo ColorOS
I have an Oppo R17 (Model CPH1879) running ColorOS V5.2.1 based on Android 8.1.0.
The problem is that every time I restart my device or if its battery runs out, some of my settings are reset to default. Not all my settings, I'll make it clear.
I realized that it is mainly

The Auto-lock setting; keeps resetting to 15 seconds and I have to change it back to 2 minutes as it was,
My alarm ringtone is reset to the default ringtone whereas I keep changing it to a custom file.

As of now I am not even sure if anything else changes besides these 2.
Since the ColorOS is still relatively new, searching on Google got me absolutely nowhere. Anyone come across this before or know how to fix this?


text:
In which Android system file can I remove Wi-Fi password field?
If I would root my device based on Android (v4.0.4), which system file and how can I change to remove from the graphic interface the field where we manually type a password when connecting to new Wi-Fi hotspot?
ps. This is an additional and separate question to Which Android system file(s) should I change to connect only to specific Wi-Fi hotspots

The GUI for new Wifi connections should be part of the settings app. Therefore there is not "just one file". Additionally the settings app is a system app signed with the system key (which you don't have). Therefore modifying the settings app is a complicated topic.

@Robert thanks! Maybe there is a solution with the wpa_supplicant_scan function?


text:
Dumpsys Meminfo reporting inconsistent values ((Free Ram + Used Ram + Lost Ram) > Total Ram) Nokia 1
Below is my log as stated in the title the value of Dumpsys Meminfo do not add up to total ram.
My device is NOKIA 1
Android 8.1.0
To reproduce these results I opened 10 apps using adb shell monkey and then took a dumpsys meminfo using This Command.
adb shell dumpsys -t 60 meminfo
My intution is
Free RAM + Used RAM + Lost RAM = Total RAM
416,633K + 760,054K + -17,123K = 1,159,564K

Total RAM (Though Summing) = 1,159,564 K
Total RAM (Reported by Dump Sys) = 951,952K

Why is there a difference in Total RAM ?
Here is the App list
com.google.android.youtube
com.google.android.apps.messaging
com.google.android.music
com.android.contacts
com.google.android.calculator
com.android.chrome
com.android.camera2
com.alibaba.aliexpresshd
com.amazon.mShop.android.shopping
com.cam001.selfie
com.daraz.android

I opened these apps with 20 second gaps to make sure that app opend completely.
  Total PSS by process:
       84,517K: com.google.android.apps.docs (pid 10596 / activities)
       71,280K: com.amazon.mShop.android.shopping (pid 10319 / activities)
       59,903K: com.alibaba.aliexpresshd (pid 9826 / activities)
       56,000K: system (pid 720)
       55,667K: com.hmdglobal.support (pid 10891)
       51,705K: com.android.systemui (pid 1161 / activities)
       40,915K: com.google.android.gms.persistent (pid 1529)
       32,720K: com.lenovo.anyshare.gps (pid 9140)
       29,314K: com.google.android.gms (pid 1680)
       24,049K: com.evenwell.UsageStatsLogReceiver (pid 9860)
       22,398K: com.android.chrome (pid 9588 / activities)
       20,676K: com.android.launcher3 (pid 1615 / activities)
       20,132K: com.uc.vmate (pid 7787)
       20,098K: com.google.android.inputmethod.latin (pid 1139)
       19,382K: video.like (pid 4663)
       18,346K: libweexjsb.so (pid 10111)
       18,100K: com.google.android.music:ui (pid 9020 / activities)
       18,004K: com.android.settings (pid 7279 / activities)
       16,362K: com.alibaba.aliexpresshd:channel (pid 10142)
       15,781K: com.android.vending (pid 7678)
       15,400K: com.android.chrome:sandboxed_process0 (pid 9632)
       13,429K: com.google.android.calculator (pid 9502 / activities)
       12,023K: surfaceflinger (pid 289)
       11,217K: com.uc.vmate:rainbow (pid 7889)
       10,448K: com.lenovo.anyshare.gps:transfer (pid 8380)
       10,311K: video.like:service (pid 9926)
       10,020K: camerahalserver (pid 426)
        9,585K: com.google.android.music:main (pid 9039)
        9,373K: com.android.phone (pid 1323)
        7,786K: com.opera.browser.beta (pid 9724)
        7,629K: com.google.android.partnersetup (pid 10869)
        6,198K: com.mediatek.ims (pid 1316)
        5,358K: android.process.acore (pid 8929)
        4,348K: merged_hal_service (pid 282)
        4,096K: com.evenwell.OTAUpdate (pid 1570)
        4,094K: android.hardware.graphics.composer@2.1-service (pid 280)
        4,033K: com.google.process.gapps (pid 7909)
        4,033K: mediaserver (pid 420)
        3,900K: audioserver (pid 409)
        3,849K: android.hardware.audio@2.0-service-mediatek (pid 273)
        3,751K: vtservice (pid 415)
        3,652K: com.evenwell.pushagent (pid 1552)
        3,639K: android.process.media (pid 7353)
        3,613K: com.google.process.gservices (pid 1633)
        3,557K: media.codec (pid 424)
        3,472K: /init (pid 1)
        3,219K: com.evenwell.autoregistration (pid 7239)
        2,901K: zygote (pid 407)
        2,900K: drmserver (pid 413)
        2,883K: com.android.chrome:webview_service (pid 10008)
        2,823K: mtkmal (pid 297)
        2,705K: media.extractor (pid 419)
        2,701K: com.evenwell.batteryprotect (pid 7220)
        2,691K: mtkrild (pid 760)
        2,604K: mnld (pid 406)
        2,588K: rilproxy (pid 849)
        2,546K: com.android.smspush (pid 1708)
        2,539K: cameraserver (pid 411)
        2,444K: com.evenwell.emm (pid 1546)
        2,383K: com.android.partnerbrowsercustomizations (pid 9618)
        2,158K: mtk_agpsd (pid 432)
        1,825K: wpa_supplicant (pid 1241)
        1,414K: netd (pid 421)
        1,392K: android.hardware.wifi@1.0-service (pid 281)
        1,386K: vold (pid 262)
        1,313K: logd (pid 251)
        1,290K: android.hardware.drm@1.0-service.widevine (pid 278)
        1,237K: vendor.mediatek.hardware.wfo@1.0-service (pid 284)
        1,234K: wfca (pid 298)
        1,186K: ueventd (pid 205)
        1,157K: vendor.mediatek.hardware.pq@2.0-service (pid 435)
        1,151K: keystore (pid 417)
        1,123K: installd (pid 416)
        1,085K: wificond (pid 423)
        1,082K: aal (pid 408)
        1,068K: android.hardware.sensors@1.0-service-mediatek (pid 425)
          959K: ged_srv (pid 1516)
          958K: hwservicemanager (pid 253)
          857K: mediadrmserver (pid 418)
          852K: android.hardware.keymaster@3.0-service (pid 261)
          840K: gatekeeperd (pid 437)
          827K: dm_agent_binder (pid 412)
          797K: storaged (pid 422)
          787K: thermalserviced (pid 290)
          771K: android.hardware.broadcastradio@1.1-service (pid 275)
          734K: healthd (pid 285)
          715K: ccci_fsd (pid 292)
          703K: android.hardware.bluetooth@1.0-service-mediatek (pid 274)
          690K: android.hardware.cas@1.0-service (pid 276)
          669K: ccci_mdinit (pid 294)
          667K: vendor.mediatek.hardware.imsa@1.0-service (pid 283)
          665K: android.hardware.gatekeeper@1.0-service (pid 279)
          662K: ip6tables-restore (pid 481)
          659K: netdagent (pid 443)
          652K: adbd (pid 1503)
          637K: vtservice_hidl (pid 272)
          629K: android.hardware.configstore@1.0-service (pid 277)
          615K: fuelgauged (pid 291)
          598K: servicemanager (pid 252)
          569K: gsm0710muxd (pid 696)
          554K: epdg_wod (pid 442)
          553K: android.hidl.allocator@1.0-service (pid 271)
          553K: lmkd (pid 287)
          552K: dumpsys (pid 10758)
          541K: vndservicemanager (pid 254)
          541K: bbs_fih_log (pid 330)
          540K: program_binary_service (pid 438)
          516K: thermald (pid 414)
          511K: tombstoned (pid 441)
          510K: batterywarning (pid 410)
          485K: ipsec_mon (pid 430)
          457K: iptables-restore (pid 480)
          451K: pandoraservice (pid 306)
          424K: ccci_rpcd (pid 296)
          409K: sysenv_daemon (pid 434)
          405K: wifi2agps (pid 436)
          395K: thermal (pid 427)
          386K: wmt_launcher (pid 300)
          385K: storageproxyd (pid 444)

  Total PSS by OOM adjustment:
      204,221K: Native
           55,667K: com.hmdglobal.support (pid 10891)
           18,346K: libweexjsb.so (pid 10111)
           12,023K: surfaceflinger (pid 289)
           10,020K: camerahalserver (pid 426)
            7,629K: com.google.android.partnersetup (pid 10869)
            4,348K: merged_hal_service (pid 282)
            4,094K: android.hardware.graphics.composer@2.1-service (pid 280)
            4,033K: mediaserver (pid 420)
            3,900K: audioserver (pid 409)
            3,849K: android.hardware.audio@2.0-service-mediatek (pid 273)
            3,751K: vtservice (pid 415)
            3,557K: media.codec (pid 424)
            3,472K: /init (pid 1)
            2,901K: zygote (pid 407)
            2,900K: drmserver (pid 413)
            2,823K: mtkmal (pid 297)
            2,705K: media.extractor (pid 419)
            2,691K: mtkrild (pid 760)
            2,604K: mnld (pid 406)
            2,588K: rilproxy (pid 849)
            2,539K: cameraserver (pid 411)
            2,158K: mtk_agpsd (pid 432)
            1,825K: wpa_supplicant (pid 1241)
            1,414K: netd (pid 421)
            1,392K: android.hardware.wifi@1.0-service (pid 281)
            1,386K: vold (pid 262)
            1,313K: logd (pid 251)
            1,290K: android.hardware.drm@1.0-service.widevine (pid 278)
            1,237K: vendor.mediatek.hardware.wfo@1.0-service (pid 284)
            1,234K: wfca (pid 298)
            1,186K: ueventd (pid 205)
            1,157K: vendor.mediatek.hardware.pq@2.0-service (pid 435)
            1,151K: keystore (pid 417)
            1,123K: installd (pid 416)
            1,085K: wificond (pid 423)
            1,082K: aal (pid 408)
            1,068K: android.hardware.sensors@1.0-service-mediatek (pid 425)
              959K: ged_srv (pid 1516)
              958K: hwservicemanager (pid 253)
              857K: mediadrmserver (pid 418)
              852K: android.hardware.keymaster@3.0-service (pid 261)
              840K: gatekeeperd (pid 437)
              827K: dm_agent_binder (pid 412)
              797K: storaged (pid 422)
              787K: thermalserviced (pid 290)
              771K: android.hardware.broadcastradio@1.1-service (pid 275)
              734K: healthd (pid 285)
              715K: ccci_fsd (pid 292)
              703K: android.hardware.bluetooth@1.0-service-mediatek (pid 274)
              690K: android.hardware.cas@1.0-service (pid 276)
              669K: ccci_mdinit (pid 294)
              667K: vendor.mediatek.hardware.imsa@1.0-service (pid 283)
              665K: android.hardware.gatekeeper@1.0-service (pid 279)
              662K: ip6tables-restore (pid 481)
              659K: netdagent (pid 443)
              652K: adbd (pid 1503)
              637K: vtservice_hidl (pid 272)
              629K: android.hardware.configstore@1.0-service (pid 277)
              615K: fuelgauged (pid 291)
              598K: servicemanager (pid 252)
              569K: gsm0710muxd (pid 696)
              554K: epdg_wod (pid 442)
              553K: android.hidl.allocator@1.0-service (pid 271)
              553K: lmkd (pid 287)
              552K: dumpsys (pid 10758)
              541K: vndservicemanager (pid 254)
              541K: bbs_fih_log (pid 330)
              540K: program_binary_service (pid 438)
              516K: thermald (pid 414)
              511K: tombstoned (pid 441)
              510K: batterywarning (pid 410)
              485K: ipsec_mon (pid 430)
              457K: iptables-restore (pid 480)
              451K: pandoraservice (pid 306)
              424K: ccci_rpcd (pid 296)
              409K: sysenv_daemon (pid 434)
              405K: wifi2agps (pid 436)
              395K: thermal (pid 427)
              386K: wmt_launcher (pid 300)
              385K: storageproxyd (pid 444)
       56,000K: System
           56,000K: system (pid 720)
       77,468K: Persistent
           51,705K: com.android.systemui (pid 1161 / activities)
            9,373K: com.android.phone (pid 1323)
            6,198K: com.mediatek.ims (pid 1316)
            4,096K: com.evenwell.OTAUpdate (pid 1570)
            3,652K: com.evenwell.pushagent (pid 1552)
            2,444K: com.evenwell.emm (pid 1546)
       84,517K: Foreground
           84,517K: com.google.android.apps.docs (pid 10596 / activities)
       88,556K: Visible
           40,915K: com.google.android.gms.persistent (pid 1529)
           29,314K: com.google.android.gms (pid 1680)
           15,781K: com.android.vending (pid 7678)
            2,546K: com.android.smspush (pid 1708)
       20,098K: Perceptible
           20,098K: com.google.android.inputmethod.latin (pid 1139)
        6,858K: A Services
            3,639K: android.process.media (pid 7353)
            3,219K: com.evenwell.autoregistration (pid 7239)
       20,676K: Home
           20,676K: com.android.launcher3 (pid 1615 / activities)
       80,608K: B Services
           59,903K: com.alibaba.aliexpresshd (pid 9826 / activities)
           18,004K: com.android.settings (pid 7279 / activities)
            2,701K: com.evenwell.batteryprotect (pid 7220)
      320,869K: Cached
           71,280K: com.amazon.mShop.android.shopping (pid 10319 / activities)
           32,720K: com.lenovo.anyshare.gps (pid 9140)
           24,049K: com.evenwell.UsageStatsLogReceiver (pid 9860)
           22,398K: com.android.chrome (pid 9588 / activities)
           20,132K: com.uc.vmate (pid 7787)
           19,382K: video.like (pid 4663)
           18,100K: com.google.android.music:ui (pid 9020 / activities)
           16,362K: com.alibaba.aliexpresshd:channel (pid 10142)
           15,400K: com.android.chrome:sandboxed_process0 (pid 9632)
           13,429K: com.google.android.calculator (pid 9502 / activities)
           11,217K: com.uc.vmate:rainbow (pid 7889)
           10,448K: com.lenovo.anyshare.gps:transfer (pid 8380)
           10,311K: video.like:service (pid 9926)
            9,585K: com.google.android.music:main (pid 9039)
            7,786K: com.opera.browser.beta (pid 9724)
            5,358K: android.process.acore (pid 8929)
            4,033K: com.google.process.gapps (pid 7909)
            3,613K: com.google.process.gservices (pid 1633)
            2,883K: com.android.chrome:webview_service (pid 10008)
            2,383K: com.android.partnerbrowsercustomizations (pid 9618)

  Total PSS by category:
      120,452K: .dex mmap
       85,362K: .so mmap
       77,628K: Native
       68,219K: .apk mmap
       65,610K: Dalvik
       46,060K: GL mtrack
       25,774K: .art mmap
       25,312K: Dalvik Other
       24,384K: Unknown
       16,813K: .oat mmap
       14,974K: EGL mtrack
       12,700K: Stack
       12,308K: Other mmap
        1,326K: Other dev
          730K: Ashmem
          709K: .ttf mmap
           76K: .jar mmap
            0K: Cursor
            0K: Gfx dev
            0K: Other mtrack

  Total RAM:   951,952K (status normal)
   Free RAM:   416,633K (  320,869K cached pss +    72,320K cached kernel +    23,444K free)
   Used RAM:   760,054K (  639,002K used pss +   121,052K kernel)
   Lost RAM:   -17,123K
       ZRAM:   104,800K physical used for   357,032K in swap (  428,372K total swap)
     Tuning: 128 (large 256), oom   184,320K, restore limit    61,440K (low-ram)

Addition Information DUMPSYS, VMSTAT
Total RAM:   951,952K (status normal)
 Free RAM:   420,263K (  286,451K cached pss +   112,720K cached kernel +    21,092K free)
 Used RAM:   729,271K (  610,175K used pss +   119,096K kernel)
 Lost RAM:    -7,523K
     ZRAM:    86,648K physical used for   322,252K in swap (  428,372K total swap)
   Tuning: 128 (large 256), oom   184,320K, restore limit    61,440K (low-ram)

C:\Users\ab>adb shell /system/bin/vmstat
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa
 4  1 318204  27884    900 335664  477  667  2422   747    0 2797 20 18 62  1

C:\Users\ab>adb shell /system/bin/free -k
                total        used        free      shared     buffers
Mem:           951952      903968       47984        1868         900
-/+ buffers/cache:         903068       48884
Swap:          428372      324320      104052

Do you have root? What's the output of /data/data/com.termux/files/usr/bin/vmstat and /data/data/com.termux/files/usr/bin/free -k and /system/bin/vmstat and /system/bin/free -k?

Unfortunately I do not have a rooted devices.

free command should still work, it just reads /proc/meminfo. Also try vmstat, may be you sepolicy allows reading /proc/stat.

I have added the results of vmstat and free command


text:
How to enter in TWRP/recover on Huawei P9 lite with keys?
I have a p9 lite Huawei.
I can boot into twrp with this command
adb reboot recovery

But without adb, I cannot enter in recovery mode.
If I push Volume Down+Power, it goes into bootloader (I can see a green droid logo).
If I push Volume Up+Power, it opens the EMUI recovery.
How to get recovery mode with twrp?Is possible with fastboot?
I have installed the twrp with
fastboot flash recovery twrp.img

Are you sure that TWRP was/is installed properly? Because it seems that you have 2 recoveries.

I have installed with fastboot flash recovery twrp.img

Does it make a difference when usb cable is connected? you can try 'fastboot oem reboot-recovery' or 'fastboot oem reboot recovery' or 'fastboot boot twrp.img' or you can try to flash twrp on erecovery (may brick your device) ask in the forum where you downloaded TWRP does really nobody know it?

I have found a workaround to enter in recovery.
a)Turn off device
b)Push power+VolumeDown
c)We enter in bootloader mode, with volumeup key we select the "recovery" and press power
d)Device reboot to twrp

thats so simple i used this often that i didn't consider you haven't tried that before and completely forgot about it

The basic process of installing TWRP on every phone is to boot into TWRP itself first so TWRP could overwite the recovery partition and replace the stock Android recovery with TWRP itself.
Step 1:
Boot into bootloader / fastboot mode
Step 2:
Make sure that your device's boot loader is unlocked. If not, please follow this tutorial on forum.xda-developers.com by user Mandrigan. https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
Step 3:
Boot into fastboot mode again. Type in the command
fastboot flash xxxxx.img
Where xxxxx.img is your TWRP image file name.
Step 4:
Immediately boot into recovery (make sure you don't boot into Android!!!)
Step 5:
While in TWRP, Press "Mount" and tick on "System" box. Then go to "Advanced" --> "File Manager" find a folder with the name "system". Go into that folder and scroll down until you find a file with something like "recovery-from-boot.xxx". Press on the file name and press on "Rename" and add ".bak" at the end of the file name and it should look like this "recovery-from-boot.xxx.bak"
Step 6:
It is recommended to flash either SuperSU or Magisk so TWRP stays and it doesn't get overwritten by stock Android recovery.
Installation is done and you should have TWRP as your permanent recovery!!

the question is about key combo not how to flash recovery. besides this the fastboot command you stated is incorrect, and bootloader can't be unlocked (not from huawei, at least. they won't provide unlock codes)


text:
Can I schedule my Android phone to mute notifications of a specific app at specific times?
I don't want to receive work emails on weekends.
Can I schedule my Android phone to mute notifications of a specific app at specific times?

Welcome to Android Enthusiasts! Can you be clear? You want to mute notifications of some apps or you don't want to receive emails? They are completely different questions? Or is it you want to mute notifications of your email app although they will still be received?

No, the only way is to enable "Don't Disturb" mode and adjust priorities so you can just receive notifications for the selected priority type on weekends for example


text:
Why does my twrp custom recovery not work?
I've recently wanted to root my phone I unlocked the bootloader and followed a tutorial of how to add the twrp custom recovery I complete it and everything seems fine but when I turn on my custom recovery it just shows the android recovery
My phone is a allwiev p7_pro
I've used the recovery file from XDA developers

It is best if you list the instructions or at least link the tutorial which you followed.

https://android.stackexchange.com/a/214929

Keep in mind that do NOT boot into system after flashing TWRP. Take out the battery, insert it, and boot into recovery. If you don't have a removable battery, boot to recovery from fastboot/adb as soon as you finish flashing.


text:
Whatsapp isn't performing the expected daily backup
I have a Galaxy S10e with Whatsapp backup setup to backup daily to google drive, according to the guidelines on Samsung's website:

However the backup isn't taking place automatically.  It only backs up if I manually initiate it.  What could be the reason that Whatsapp isn't doing it?

Four points: 1. Change backup frequency to "daily". 2. Change "Wi-Fi only" to "Wi-Fi and Cellular" under Back up over. 3. Select a backup account. 4. Disable battery optimizations for WhatsApp. Do these solve the problem?

how do I disable battery optimizations?

That actually differs from device to device, but if you have the Smart Manager app provided by Samsung, you should have that option there (under Battery option). Otherwise, do a search in Settings.


text:
How to get fast charging diagnostics information
I want to find out what type of Fast Charging is supported by different combinations of Android device, cable and charger.
I have a variety of devices, from different manufacturers and with different Android versions; a selection of USB chargers with different rated voltage and current outputs; and a miscellany of USB cables and adaptors.  I want to work out which ones to use to get the fastest charge rate for each.  Also, I would like to be able to decide which new chargers/powerbanks to buy for best compatibility.  I understand that there are various different methods of Fast Charging (as explained at battery - How does fast charging work?).  Unfortunately, the documentation supplied with my devices is pretty sparse.
Is there some way (an app, diagnostic screen, API call, etc.) that I can get my devices to tell me some of the following:

Which fast charging standard(s) does the Android device support (e.g. Qualcom Quick Charge 2.0, USB Power Delivery 3.0, etc.)?
Which fast charging standard(s) does the connected charger support?
What standard is actually in use?

Alternatively, are there any good rules for inferring what standard is in use from the current being drawn?
I have seen various apps that display the charging current, but the ones I have tried haven't displayed information about the standard being used.
This question is similar to How do I know that a charger is a Turbo Charger for my Moto, but I want to know about the supported standards, not just "am I fast charging?".  Also, I would like some way of interrogating the hardware, rather than having to google the specs for each device and charger separately.  For clarity, I am only interested in wired USB charging, not wireless.

One way would be to identify the used charging chip in each device, e.g. using a device tear down like those from ifixit.com. Based on the used chip the chip's data sheet should contain the detailed information about the supported charging methods.

Unfortunately it isn't easy to find this information - especially for chargers.  I don't want to start cracking them open myself! Hence I was after a software-based method of getting the device to tell me itself.

AFAIK, no, it's not possible. Reasons :

Android only tells you the levels at which the device is considered to be charging normally or fast charging. This was based initially on current and now on power in watts. See Andrew's answer and also my answer there.
There are at least 5 proprietary fast charging technologies and obviously all details are not made public. Recognizing the device, the type of charging is a complex interplay between battery, charger and OS and is charging technology specific (whether current or voltage or a combination of both is used to charge fast) . The device may /may not recognize and notify if a different technology charger is used.
Even within the same technology, there can be variations; for example Qualcomm 2.0 increases current while Qualcomm 3.0 increases power (product of current and voltage).

IMO your mission would need you to have rooted devices, see the levels at which charging normally or rapidly is determined (first bullet point) and determine, if you can, from the system files what type of technology is used. It's easier to Google. To the best of my knowledge, there is no app that can help ( I may be wrong here, haven't updated myself)


text:
Part of mobile screen not working
I have an Android mobile Meizu m5 which has a Flyme OS.Until recently the phone has been working just fine. However recently i noticed that the lower part of the screen has stopped working. I tried the touch detector tool and it also didnt work in that specific area which is
On random occasions the screen stated acting weird and clicking random buttons. Antiviruses didnt catch any problem however the antivirus of meizu showeved that there was something in the TouchPal. I transfered my contacts and sms and did a full factory reset however the issue still presisted and then meizus owns antivirus also didnt give any issue.I also took off the screen protector but still no luck.
Waiting for help. Thanks

If you are willing to resize the screen so as to use only its working part, my answer might help you out. See Resize screen to display only on working part of semi-functional touchscreen

@Firelord any solution without resizing? As sometimes the whole screen just glitches and clicks random things

@Talha Usually when a part of the touch screen stops working and a factory reset does not help this is a hardware defect. Therefore I see the three options: 1. resize the screen so that it doe snot use the non-working area. 2. repair the hone (usually means complete new screen) 3. Buy a new phone.

@Robert but that portion starts working for some times on random occasions. So shouldnt it be a software issue?

I had exactly the same problem one year ago with m5. I agree that it appears to be a software problem since it sometimes disappear . I bought an M6 and moved on,  but I will send it to service shop since it is still n the warranty period. You can now buy an M8 for the same money

@magma thanks for your response. So i suppose there is no possible fix

Well, I think the  only possibility is to send it to a repair center and see what happens. I will do it asap since my 2 year EU warranty is expiring soon. They will keep it for 30-40 days they told me. That's why I bought a new model in the meantime

@magma oh ok well mabye i'll try to do the same.Thanks


text:
My android phone is often getting affected with virus
My problem :
Hello friends. I use Asus zenfone go T500 android phone. My problem is, my phone often gets affected by some kind of virus which sometimes installs some chinese apps without my knowledge and sometimes it causes troubles to other system apps and because of this i fequently get a message displaying unfortunately stopped working.
What I have done:

I tried resetting my phone(factory reset).
But even after resetting after a few days the same problem occurs again. So i thought of reinstalling my stock rom and hence i downloaded the stock rom from the official asus site and reinstalled it. Everything was fine. But again after some days the same problem. What i mean here is no matter any time i scan my phone with some antivirus or factory reset or reinstall ROM the behavour still exists.
I tried updating all my system and installed apps but no use.

My predictions:
What i predicted as a problem was this that my phones private ip address must have been stolen somehow and some idiot from some country is DOS attacking my phone.
Other info

NOTE: I once rooted my phone and then later i reinstalled the stock
ROM to get rid of it

My phone: ASUS Zenfone GO LTE
Model: ASUS_X003 (T500)
OS: KitKat - 4.4.4
ROM: WW-SKU

I am sorry what what you write in the section "My predictions" is totally nonsense, starting that a private IP address can't be "stolen", furthermore this address is usually not static and third - a private IP is by default not reachable from the Internet (as it is private).

Sorry @Robert. Am a rookie. Never mind. I didn't know that.

Honestly I don't see a specific problem with your device. Things you have described were very common in the days of KK. it causes troubles to other system apps what kind of trouble? i fequently get a message displaying unfortunately stopped what stops working? An app or some system component? installs some chinese apps without my knowledge it's alarming. May be the apps are from your OEM. They put more junk on devices than a normal user would do himself. Will have to look into the list of all non-AOSP apps on your device (system or user).

Lots of malware writers make malwares to make money, so developing a virus would do no good to them. Better ways of making money is to force installation of some apps which loads ads for you, or collects your personal data and sells it to third-parties, or just plainly demand ransom for your personal data. Check out this list to know the categories of Android malwares.
Whenever you get into a problem repeatedly you should wonder why so? In this case the biggest problem is you (the user) using an archaic version of Android that was launched in 2013 (6 years ago!). Neither Google, nor your OEM would support the device for that long. Meanwhile, since OS is actually a software built using codes,and because codes can be buggy the bugs get exploited by some malwares writers and the result is what you are experiencing with your device.
The only solution as I see is to keep reviewing the code for vulnerabilities and fixing them. This is near impossible for users so we expect OS developers or OEMs to do this for us. Some OEMs support the device for some period, others don't. In that case, the user can turn elsewhere and see if some third-party is doing this job (custom ROM developers). If even that doesn't work, one should either stop using the device with any new app or updates or with internet connectivity, or to personally port a custom ROM built using secure and new OS code, or simply switch to a device which uses the latest Android version and would be supported for a while.
To summarize, there is no point in fixing this problem technically because your device is asking itself to get compromised again, sooner or later. Switch to a newer Android version.
Note: it may be possible to prevent exploitation of some vulnerabilities in an older Android version using SELinux or some other security framework, but I am not aware of any attempt in this direction.

+1 for the older OS. But i would like to know which app is it that is exploiting my code creating trouble. Is there any way I can find it ?

@Thameem It does not have to be an app. Exploits especially on old phones can be triggered via Wifi scanning (depending on the used Wifi chipset you have), SMS receiving, browsing the Web, and of course installing a malicious app. As malicious apps mostly don't start directly to behave bad (they are waiting some hours or days) identifying the malicious app can take some time...


text:
What is /data/backup/ for on android and culd i delet the files in there (try to backup with TWRP)
I need to delete the files in that folder becouse i try to make a backup with TWRP of my system but the files (or just one of them) is abording my backup and i get errror 255
I:Error adding file '/data/backup/xwLBFGdSbAq4bs4zMw1ZvB' to '/data/media/0/TWRP/BACKUPS/4741abba/2019-08-18--12-41-39_lineage_dipper-userdebug_9_PQ3A190705003_bd/data.ext4.win000'
Fehler beim Erstellen der Sicherung. (Error while creating a Backup)
I:ERROR tarList for thread ID 0
Fehler beim Erstellen der Sicherung. (Error while creating a Backup)
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/4741abba/2019-08-18--12-41-39_lineage_dipper-userdebug_9_PQ3A190705003_bd/data.info'
Prozess createTarFork() endete mit FEHLER: 255 (Proces endet with error: 255)
Sicherung fehlgeschlagen, bereinige Sicherungs-Verzeichnis (Backup faild, Clean ?Files?)
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/4741abba/2019-08-18--12-41-39_lineage_dipper-userdebug_9_PQ3A190705003_bd/recovery.log

the errors where parthely in german but i wrote a hopfully good enough translation behind them.
for the phone:

xiaomi mi 8
256 GB (9% used)

This answer shows that the folder is related to Google Cloud backups.
I experimented by deleting it. When I restarted the phone, it was re-created. The files and folders that were in it, were also re-created. I'll assume that it is safe to delete.

Thanks for your help it helpt me to get a bit further (and for some reson it fixed some unrelated issuses with PayPal and Youtube constantly crashing) but now "/data/user_de/0/a0Z6S+HEvYJ8pZcV0,E9,ymTR56jLMsc8iPdsD/xrvhihYJWRngkT87Y1vpUA/7n2ZEWwmUMUZ60wLuEvTHmgwlHzDypp2T3fIgZyeBAC" is the problem. On any chanse do you now if i can delete that?

@Philipp My phone has /data/user_de/0 folder that seems to contains preferences and databases of apps installed. All the folders are name after app packages. Try to navigate to that folder you named and check that file. If the folder and the file are irrelevant, delete them.

So i got into the folder but all the folders have names like "a0Z6S+HEvYJ8pZcV0,E9,ymTR56jLMsc8iPdsD" do you have any clue if thats just encrypted names or something? and ther are no folders with the name of apps.

@Philipp Yes, they might be encrypted. From Android, copy and paste that folder to a different place, then from TWRP delete it, and try carrying on the backup.

cant i coppy an paste it vom TWRP, bcouse i dont know how to get to the folder in any other way

@Philipp If you know how to use commands from the terminal, then you can do it from TWRP.


text:
What is `/system/app/AutomationTest_JBUP.apk`?
For backing up data from and repairing a stock Samsung Galaxy S2 (see How to copy / modify data from a soft-bootlooping Samsung Galaxy S2 (GT-I9100)), I used a recovery ROM (PhilZ-cwm6-XWMS3-FOP-5.15.9-signed.zip, SHA256: 406a617e8b378384bde40dd2dc6234c0660a1b4f592b6c25b3be6b6f078b9eec). This recovery ROM works without having to re-install the stock firmware (which, on this phone, is normally required). As a side-effect, it also installed the "Superuser" app, making it possible to become root.
After turning on the phone a few times, I was asked whether I want to allow "Automation Test" to gain super user privileges. What application is that and where does it come from? It seems like it is stored here: /system/app/AutomationTest_JBUP.apk.

According to this thread from Xda-developers, AutomationTest_JBUP.apk is listed among the apps that can safely be removed from a Samsung Galaxy S2. That will mean it comes installed by the manufacturer as default app.
Its package name is com.sec.android.app.DataCreate and analysis of a subsequent version shows that it is from Samsung. I have no idea of its purpose.


text:
Stop Google play store from Auto updating
Okay so this is a weird issue but hear me out. I own an LG G4 and as usual, the play store updates itself to stay on the latest version. But I noticed the original play store that came on the phone is faster, not laggy, and the UI just looks better. Is there a way I can keep the phone ON that older version? Every time I downgrade it, it just updates soon after.

Unless you block Download Manager, Google Play Services and Google Pay Store from accessing internet, then you can't stop it from updating. Blocking them will also have the effect of preventing other apps to update which I presume you don't want.

Yeah. It's just that the new playstore is more laggy for me, and I'm not a huge fan of the UI.

If you can try to find a modified version of your Google Play Store that doesn't allow udates, and but I have never tested them on non rooted devices.


text:
Galaxy s9+ not charging via USB-C cable and not quick charging at all
I ran into a problem with my Galaxy s9+ recently, it won't charge at all using my Samsung 25 Watt Wall Charger and also won't charge using my Aukey 26800mah power bank when connected via USB-C. It however will charge when I connect my phone to the power bank using a USB-A to USB-C cable. As of right now there is no way I can quick charge my phone, even using a brand new Samsung charger that came in the box will not quick charge my phone, only cable charging.
What chargers I tested:

The in the box Samsung charger

This will charge my phone, but only "cable charging", no fast charging

Samsung 25 Watt Wall Charger

This one won't charge my phone at all

Aukey PA-6Y

This one charges my phone with quick charge, but only when using the USB-A connector, and won't charge my phone when using the USB-C port
This one is also an interesting case, as it has a USB-A and USB-C plug

Lenovo 65 Watt laptop charger

This one won't charge my phone at all

I tested all of these chargers at 2 different physical locations and 2 different sockets at each location so I cannot possibly be a problem with the Socket. I also tested all these chargers with my brothers Galaxy s10+ and each of these chargers charge his phone with quick charging.
But I have also been seeing some very weird behaviour from my phone. For example: I bought the 25 Watt Samsung wall charger brand new and tested it out, it worked perfectly. A day later I wanted to plug in my phone again and it won't charge anymore, just for me to unplug it, turn around the USB-C connector and plug it in and to work again. Once more a day later I wanted to charge my phone again, only for it to not work at all, no matter the USB-C orientation (which shouldn't matter anyways).
I've exhausted every opportunity at my disposal and don't know what could possibly be the problem. I also brought in my phone to my cell carrier (where I have it insured) only for them to say "it quick charges with this charger, I don't see a problem". The only constant I was able to find was that my phone won't charge when using a USB-C to USB-C cable, but will charge (and sometimes quick charge) when using a USB-A to USB-C cable (I tried this on the Aukey charger and the two Samsung chargers back this up)
So my question is this: Does anyone have any idea what could be causing this and how I could fix this?

Have you enabled quick charging in the settings? According to the Samsung documentation quick charging via cable is disabled by default (because it reduces the battery life time).

Weird, I never turned it on and just checked that it is in fact turned on. Else the Aukey adapter wouldn't have quick charged my phone


text:
Accidentally rebooted OnePlus 6 with no OS installed, how to get back to TWRP?
In the process of installing LineageOS on my OnePlus 6 A6003, I accidentally pressed "reboot to system" when there was no OS installed. How can I get back to TWRP? I've tried holding Power+Vol Down but it just boots with the oneplus logo then unlocked bootloader warning then black screen with the status LED on.

Let us continue this discussion in chat.

I solved my problem with this tool.
Instructions:

Download the zip;
  Unpack the zip in a folder;
  Reboot the OnePlus 6 in fastboot mode (Power and volume-);
  Connect the OnePlus 6 to PC;
  Run flash-all.bat flasher you need;
  Wait until the process end;
  The phone will automatically reboot.

Downloads: https://www.androidfilehost.com/?w=files&flid=271877

Hello. Would you please follow our [answer] guide to write a good, self-contained answer. As the answer currently is, it would lose its usefulness if the link expires. Links are supposed to be mentioned to download some item or suggest a reading material.

@Firelord but the answer will be useless anyway if the link goes down because the tool itself will be inaccessible...?

the tool might be available on some mirror or some other forum/website but the tutorial might not be.

You need to press vol-up + power and then briefly (1-2 secs) let go of the power button (don't let go of the vol-up button yet!) and hold it down again until you see the TWRP splash screen.

When I do this I just get back to fastboot mode


text:
Wi-Fi hotspot with access of device storage
Is it possible to create Wi-Fi hotspot on Android phone with access of device storage through that network?
I'm able to create hotspot OR share storage through network, but is it possible to do it together at same time, with just one device?

How are you sharing access to device storage? You can use some server app to host an http/ftp/webdav etc., servers and bind them to a network interface if needed be. Is this not what you want btw?

@Firelord these apps what i tried need connection through Wi-Fi to share storage. My question is how to connect them to the hotspot from same device (no another Wi-Fi)

@Francis hotspot is the Wi-Fi. Other than some technical differences, a device should not differentiate between a hotspot and a Wi-Fi router. All that you need is the IP address to access a device on network. It makes no difference if the IP is static or is assigned by WiFi router or hotspot. Though some app might have unnecessary limitation of WiFi requirement.

Your question is not quite clear and I assume that you wanted to turn on Hotspot on your first device and connect to the Hotspot on your second device and access the Internal Storage of the first device.
What you could try is by using a File Manager app called "FX File Manager: The file manager with privacy" and it is available for download in the Google Play Store
Step 1:
Open up FX and navigate to the Web Access feature.

Step 2:
Turn on your Wi-Fi Hotspot
Step 3:
Turn on Web Access by pressing on the "Power On" button

Step 4:
A web "link" and a password will be displayed and you will need to type in this "link" on the second device (make sure you are connected to the first device's hotspot on your second device)
Step 5:
Enter the "link" displayed in Web Access and enter the password if prompted.
There you have it, you should have access to your first device's storage!


text:
Avoid porn/nude recommendation in feed of android you tube app?
How can i avoid video containing porn/nude content from appearing up in feed/recommendation of my youtube app?

Open Youtube's settings, click General.
Enable "Restricted Mode".
Restart Youtube.

I tried it and somehow it show a reduction but not completely or dominantly

@engr Because it was showing before, I guess maybe there are still remnants of data from whatever used to be shown before. Close Youtube, its clear data and cache, start it and see if there is any difference.  However, you should also know that Restricted Mode is not 100% bulletproof.


text:
How to fix "signatures do not match previously installed version" error?
I'm using a Moto G6. With the latest update to android 9, they removed the capability of using the built-in Dolby Audio equalizer for some stupid reason.
I found this Reddit post that had a way to modify the APK to make this work. I followed all the steps. I decided to try the 20 band equalizer steps and made a backup of the previous work before starting. However, when I finally got to the ADB install DaxUI2.apk, it didn't work. I got this error:

adb: failed to install DaxUI2.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.dolby.dax2appUI signatures do not match previously installed version; ignoring!]

This was saddening, but no biggie, right? Because I already had a backup. I renamed the DaxUI2 folder to DaxUI2broken, renamed my backup to DaxUI2, and I tried again, with just the first part (minus the appendix). Once I did this, though, I got the exact same error.
I'd like to be able to fix this, so if anyone knows how, please tell me!

I made sure I had removed com.dolby.dax2appUI though. I ran pm list packages | grep dolby, and I had just com.dolby.daxservice. I can post a screenshot if needed.

here is the link:https://imgur.com/a/5G84ZUU

just uninstall the current app and then run it again.

connect device to PC. Turn USB Debugging on
Execute these command
adb shell
pm list packages|grep <Package Name>

You'll get a package name for it which would look like com.xyz.example
adb shell pm uninstall <package name>

those days adb has unstall cmd: adb uninstall <package name>


text:
Where can I modify to make a custom rom allow debug any apk without android:debuggable="true" in AndroidManifest.xml?
I am try to debug a android app which have integrity check. Then I can not decompile it and change AndroidManifest.xml. And this app do not work in emulator. Therefore, I try to flash a custom ROM which can debug any app without flag android:debuggable="true" in my real devices. I tried changing the ro.debuggable=1 in default.prop in boot.img then flash to my device. But It did not change anything. Please give me some suggestion. Thank you very much.
Edit: custom ROM I use is CarbonRom this is the link: https://basketbuild.com/devs/CarbonROM/.OLD/Nougat/sirius

Android stores the information about which app is debuggable in the file /data/system/packages.list. Therefore you can simply mark any app you want as debuggable after installation and without modifying the app itself.

I did not think every thing is simple like this. I will try it. Thank you very much.

I try edit /data/system/packages.list but It did not work. I can not choose debug app in dev option.

The Debug app selector is a different topic. You were talking about the debuggable flag, which is definitely possible after changing the packages.list, I already did this and were able to connect to the app using the Android debugger.

Do you know how to select debug app after change packages.list? I can not choose the app I want to debug in developer option.

I assume this list is only updated when an app is installed. Try to restart the device. Alternatively you can always start the app with debugging via adb (am start -D ...).

Finally, I knew the problem. I don't need to choose at developer option. Just use the command you give me: am start -D [package]. Thank you very much.


text:
Google drive high data usage
I'm not sure if this is the right place to post...
Yesterday, i opened Google drive to check and spreadsheet and everything looked fine. Today i see that this night Google drive has used about 600MB of mobile data on the background. It's been 2 weeks since i connected to a WiFi network and around 1 month since i opened Drive. Obviously, i have now disabled background data usage for that app on Android settings but I'm afraid that this can happen again with another app.

What has been using that much mobile data (maybe sync or updates?) and how can i avoid this happening in the future?
Is it safe to disable background data usage on every app (except messaging apps)?

Thanks and sorry for my bad English.

Did you download something using a browser? In some MI devices, for some reason,
some downloads initiated by browser unnecessarily are directed into Google drive app even when defaults are off.

I have a mi A2, but i haven't downloaded anything except that spreadsheet, that i opened trough a link to drive.google.com


text:
Data recovery from encrypted phone based on glitches in the encryption?
To make a long story short I needed to root my phone and didn't notice the warning that unlocking the bootloader erased all contents of the memory.
I contacted a data recovery company and told them that the memory was encrypted and the phone used Android 6. In response I was told that there was a chance, albeit small, that they could recover some data. However, they were unsuccessful and in their report they blamed the encryption.
This made me pretty upset since the encryption was the first thing I mentioned in my contact with them. When I called and complained about this I got the very "interesting" answer: sometimes there is a glitch when enabling encryption leaving some of the storage unencrypted and we might be able to recover that.
Is this really true??? It sounds completely absurd that something like that could happen frequent enough so they could base their business model on it. In my ears it sounds like a bad excuse for charging me money for something that could "never" work.

An Android 6 the encryption was AFAIR not enabled by default. Considering a large storage and an encryption algorithm that only encrypts the data but leaves the rest untouched there is a chance of being able to recover something, if the encrypted time is not too long. Also how you use the phone can change the recovery rate. Also on some older devices factory reset and re-encryption had flaws not erasing everything. Anyway they told you that the chance was low - and their business model is not "recovering data" but "searching for recoverable data".

i don't believe that data is recoverable from encrypted partition when keys are wiped, and android 6 uses FDE full disk encryption, so a partially unencrypted partition won't be mountable. maybe he was talking about the (unencrypted) encryption footer at end of partition, with this it would be possible to decrypt. Besides this, they spend time in trying to recover, you must pay for the try

I'm not an expert in the filed, it's just an analyses of the case according to my limited knowledge.
ANDROID'S ENCRYPTION
Android supports two modes of encryption; FDE and FBE. FDE encrypts whole block device i.e. userdata partition using Linux kernel's dm-crypt framework, while FBE is based on fscrypt available since Android 7. From data recovery's aspect, approach is similar for both. Both offer strong encryption and what's been attacked by hackers is not the encryption itself, but Android's mechanism to create and store keys required for decryption.

sometimes there is a glitch when enabling encryption leaving some of the storage unencrypted

You are right, it's interesting. FDE, AFAIK, encrypts the whole block device, just excluding the crypto footer at the end of partition which includes keys for decryption. Initially all sectors might not be encrypted as is the case with inplace encryption:

vold checks to see if a sector is in use before reading and writing it, which makes encryption much faster on a new device that has little to no data.

But the skipped sectors are the ones which contain no data in filesystem. However as data is written to the sectors (or if the encryption was initialized with random data which doesn't seem to be the case with Android), they get encrypted and very soon whole block device becomes one giant high entropy block of data with no visible structure. It's impossible to distinguish encrypted data from random noise. TRIM, however, if supported by hardware, kernel, filesystem and the OS, may reveal the empty space in filesystem. But reading from that space only returns zeros.
POSSIBLE METHODS OF DATA RECOVERY
Data recovery works in two ways generally:

Read just the file contents by carving method / signature search
Or read the complete files along with metadata (file names, timestamps, permissions) from filesystem

Possible methods are:

Reading flash memory through firmware controller (Flash Translation Layer) of eMMC using commonly available APIs e.g. of Liux kernel. It's the FTL which stores LBAs to PBAs mapping, and information related to partitions, bad sectors, deleted data etc. This can be done by exposing partitions to a PC in some bootloader mode if available, or by using some lower level communication protocol e.g. JTAG or by chip-off method.
Or accessing silicon cells directly which is possible only with sophisticated equipment found in forensic labs, and not without manufacturer’s data sheet. In this case only carving method is possible. Data read from cells is random bytes from un-partitioned space and all 50+ partitions, including the ones which don't have filesystems at all. So the probability of recovering useful data is almost negligible, particularly of reasonably larger files. If the data saved is encrypted (using FDE, FBE or any other method), chances with this method are nil for sure.

The choice of method depends on multiple factors like if the purpose is:

To recover deleted data
To recover data off a dead phone
To break the encryption mechanism, e.g. in case of forensics, phone theft etc.

Data recovery can be done either:

On the device e.g. in recovery mode if the device is unlocked and some custom recovery environment is available.
Or off the device. It's the only option in most cases as the devices have bootloaders locked. But if your device was shipped with Android 5+, the chances are it must have hardware-backed encryption enabled which makes it almost impossible to recover - even undeleted - data off-the-device, except trying some hacks, because you can't brute force RSA keys.

BOOTLOADER UNLOCKING
Keeping all above facts and you situation in view, only an on-the-device or semi-offline approach can be tried to recover data. But then comes the bootloader unlocking part.
Google demands from SoC/OEM vendors to completely erase data on bootloader unlocking:

As a best practice, unlockable Android devices must securely erase all user data prior to being unlocked.
  ...
  Failure to implement these protections is considered a moderate level security vulnerability.

Quoted from here:

When the fastboot flashing unlock command is sent...
  ...
  a factory data reset should be done to prevent unauthorized data access

Depending on the device a BLKSECDISCARD, BLKDISCARD or a complete overwrite with zeros is recommended. It's then followed by filesystem creation which may again issue TRIM. Same happens during a factory reset i.e. userdata and cache partitions are completely erased (though conformance in past has been bad). See this answer for more details.
BLKDISCARD and FITRIM are Linux kernel's IOCTLs which issue special commands to underlying eMMC devices depending on their capabilities. TRIM is issued by the filesystem to the FTL, requesting the actual physical erasure of data blocks (LBAs) which have been deleted from the filesystem. DISCARD is kind of TRIM for whole block device. TRIM obviously doesn't touch undeleted files, filesystem structure and drive's partition table. BLKDISCARD saves nothing at all on block device, including the crypto footer. Both of these commands belong to Logical Sanitization level of secure data deletion. So is ERASE command issued by BLKSECDISCARD IOCTL, while others issued by the same - including SECURE TRIM, SECURE ERASE and SANITIZE - are considered of Digital Sanitization level i.e. they cause even more secure deletion. Even a complete overwrite with zeros will render data irrecoverable - at least without melting eMMC - because of Overprovisioning and Garbage Collection.
POSSIBILITY OF DATA RECOVERY
So in short these commands (if supported by underlying hardware and if required drivers provided by vendors) don't leave much space for deleted data recovery. Encryption adds to the trouble. As explained above, encryption type with FDE is, a kind of, all or nothing. If even a small part of crypto footer is erased during bootloader unlocking, forget about decryption. Quoted from a lead engineer for Android security (ref):

If you plan to resell or discard your device and you haven’t already, encrypt it and then perform a factory reset

And so does the removal of LUKS header on Linux. Quoted from warnings section on official page:

By far the most questions on the cryptsetup mailing list are from people that managed to damage the start of their LUKS partitions, i.e. the LUKS header. In most cases, there is nothing that can be done to help these poor souls recover their data.

So without the crypto footer which contains encrypted master key, RSA key (hardware-bound) and other information related to encryption, everything is random data. But even if we assume that crypto footer wasn't erased in your case and hardware-backed encryption wasn't a hurdle either, the problems aren't over. With dm-crypt FDE a master key is used to encrypt / decrypt sectors (512B each) individually when they are written / read respectively (every sector has it's own IV). After decrypting userdata partiton a new virtual block device is created at /dev/block/dm-0 which contains a filesystem, mostly ext4.
In order to mount the filesystem, the sectors containing basic structure of filesystem must be intact e.g. superblock(s), directory entries, inode tables, inode/block bitmaps, journal etc. It's next to impossible that all of this wasn't overwritten when unlocking bootloader and creating new filesystem. So the old filesystem is gone and what you would be left with is carving method which has a very small success rate particularly because of file fragmentation of large files. Mostly what you get is small nameless thumbnails or text files, that too after so many assumptions.
CONCLUSION
Bootloader unlocked on an encrypted device, the probability of data recovery seems very near to zero.
RELATED

What makes data recovery difficult?
How to get data off a completely dead Android phone?
Reliably Erasing Data From Flash-Based Solid State Drives


text:
Purpose of sdcardwritable file
In some directories there's .sdcardwritable file. It's a empty file. What is purpose of this file?

I don't thing the file is a part of stock Android. Some custom ROM or app must be putting that. If not figured out, there is a slightly hard way to find out who did that: https://android.stackexchange.com/a/214284/218526

I think it's something like .nomedia file.

.nomedia is defined in AOSP, sdcardwritable isn't.


text:
Make home screen icons round again, after Huawei update
Yesterday I installed a suggested update on my Huawei nova3i, to EMUI version 9.1.0
There is one change which I don't like.  Many apps installed from the app store used to have round icons, but now they have square icons.
See in this before and after, how the 'Calm', 'MeeWee' and 'Vimeo' icons have changed shape:

(We can also see that the icons grew a little bit larger, which I don't really find appealing either.)
Is it possible to restore the old look, with smaller round icons for apps from the App Store?
(I am willing to install a theme if I have to, but I don't really want the default icons, wallpapers and text to change!)

I guess the device somehow lost my theme, and this ugly look is the fallback "no theme found" behaviour.
Anyway, I downloaded the "Legend" theme from this website, and used these instructions to apply it.
After I applied that theme (although I think any theme would do), I got a reasonable compromise: smaller icons and rounded-square borders.  This is certainly improvement.

Now I just need to reset the font and wallpaper, which I can do.
Still, if anyone knows how to get the really round icons again, I would like that.


text:
How to fix sdcard empty under root with Kingoroot?
My sdcard is empty when I use su. I have gained root using Kingoroot.
This answer shows the SuperSU solution (mount namespace separation).
How to mount an sdcard to su? What additional information should I provide to get help?
It's a MTK device with Android 4.4.

I never used Kingoroot, so can't be sure if it provides and option for master mount (su mm) or not. You can switch to Magisk or SuperSU once the device is rooted. If you can't or don't want to, you can use:
su -c 'nsenter -t 1 -m /system/bin/sh'

from commandline instead of simple su. This will make you switch to root mount namespace. For details see this answer.
nsenter is usually available as busybox applet.
Since mount namesapce was implemented in Android 6, this might not be the problem with your KK device.
PS:
If Kingoroot works for you, it indicates that your device has some serious security flaw(s). Do consider an upgrade.

Empty output, as well as /storage/sdcard0

https://pastebin.com/uZwv5GYG

The link you provided contains "DISABLE INTERNAL MEMORY (/data/media/0) AND USE EXTERNAL SD CARD AS INTERNAL STORAGE" But /data/media/ contains only an obb folder

https://pastebin.com/RGaR7grk  mount /dev/block/vold/179:8 /my_sdcard still gives Usage: mount [-r] [-w] [-o options] [-t type] device directory

I have rebooted the device and mount -o rw,remount /; mkdir /my_sdcard; mount -t vfat /dev/block/vold/179:8 /my_sdcard kinda works ls /my_sdcard shows the list of files on the sdcard. /my_sdcard is still empty in root explorer

I did  mount -o uid=0,gid=0 -t vfat /dev/block/vold/179:8 /my_sdcard, mount still shows uid=1023,gid=1023


text:
Can I get non ASCII numerals globally (without rooting my device)?
I'm using 'Redmi note 7 pro'. This device has a huge language support, but unfortunately it does not handle numerals efficiently. It supports non-ASCII numerals in some places (eg. dates, phone numbers) but doesn't support them in some places (eg. Dialpad, time)
Is there any way to make this setting global (and not local)?
Is there any software which can change the UI in a way which enables unicode everywhere?

Could you clarify a little bit more? And perhaps, a specific one (in what language is the non-ASCII numerals?). Do you mean displaying non-ASCII (might be restricted to the font used by the app), or inputting non-ASCII (use 3rd-party keyboard apps)?

Ok so I have selected Marathi (an Indian language) as my system language. This language uses Devanagari script. Right now I am able to see some system apps names in Devanagari, numerals at some places, but not everywhere.


text:
App not showing up in app store search result
I am trying to download this app in samsung galaxy s4 with android 5.0.1
I have tried looking for it in another phone with android 4.2 but it doesn't show up when I search for it in the playstore (even though the search box autocomplete shows me the exact name of the app when typing the first few letters). I assumed this was because the app says it's for Android 4.4 and up so I tried the samsung phone with Android 5.0.1 but the problem is still same. In both phones the search results are similar, but neither one of them shows me the one I want
Why is this happening? The two phones are signed into app store through different google accounts. Is there any way to go directly to the page for this app using the Play Store app, instead of searching for it? I cannot do this through the browser because I don't have the google password for the Android 5.0.1 phone.

On their web site there is a list of supported devices: https://nextradioapp.com/supported-devices/

It's because the app is not compatible with your device, and thus Google Play Store app filters those out because the user won't be able to install from it anyway (APK sideloading is always possible though).
As stated in Android Developer's official documentation,

How filters work on Google Play
Google Play uses the filter restrictions described below to determine whether to show your application to a user who is browsing or searching for applications from the Google Play app.
When determining whether to display your app, Google Play checks the device's hardware and software requirement, as well as its carrier, location, and other characteristics. It then compares those against the restrictions and dependencies expressed by the application's manifest file and publishing details.
If the application is compatible with the device according to the filter rules, Google Play displays the application to the user. Otherwise, Google Play hides your application from search results and category browsing, even if a user specifically requests the app by clicking a deep link that points directly to the app's ID within Google Play.
(Emphasis mine)

Note that app developer can also exclude individual device model manually.

Exclude your app from certain devices
Manage excluded devices per app
To prevent app crashes, you can exclude your app from being available to individual devices on Google Play. Making this change manually excludes your whole app—you can't exclude individual APKs.
By manually excluding devices with known compatibility issues, you can help provide a better experience for your users.

For this specific case, NextRadio Free Live FM Radio depends on the FM receiver chip on the user's device. The update since January 2, 2019 also states that it doesn't support streaming anymore and only use FM-radio.

WHAT'S NEW
NextRadio is going back to basics. Streaming is no longer supported, but you can still tune to your favorite local stations on FM-enabled devices.

On the other hand, Samsung Galaxy S4 doesn't have FM radio, and it will be pointless to install the app since it won't work properly. Note that the user can always sideload the APK if they want.

so the manifest file determines if the app is excluded from search results? Isn't it better from the developers point of view if the app shows up in the results?

@user17915 1) yes, the manifest file affects the filter, 2) the result is only hidden on the Play Store app, but it's still shown on the Play Store web, you still can't install it from there anyway. On the other hand, the developer can only affect the filter, they can't choose to show but prevent the installation from Play Store app. Hence, if they allow it to be displayed on the Play Store app, someone with incompatible device can install it, but then they realize it doesn't work, then give 1-star rating, which is worse than preventing it altogether.

As there is no Android manifest setting for FM I assume that the developer has manually white listed the supported devices using the mentioned method to "exclude individual device model manually).


text:
How can I import a list of words and shortcuts into my Android Personal Dictionary?
jc able
ab about
bv above
ac account
This is a sample of the words and shortcuts that I'm trying to add into my Personal Dictionary. I've tried exporting my current dictionary with shortcuts and the text file inside of the zip contains this:
# Gboard Dictionary version:1
q   ing
# From OS
jc  able
t   the
I'm able to import the above file, but as soon as I copy and paste my words into it I'm hit with an "Import failed" toast.
Here"s the full wordlist that I'm trying to copy and paste into the other file.
I've also tried the User Dictionary Manager app with no success as it doesn't seem to support shortcuts for words. It just assumes that the shortcut is part of the word.
Why isn't this working? What do I have to do too make it work?

I had a look at your file and couldn't import the words to Gboard either. There are 3 errors that make Gboard ignore your words and shortcuts: space between words & shortcuts and no language for the words.
Error 1:  Space between words & shortcuts
Your words and shortcuts are separated by spaces. That's not correct. They must be separated by Tab. I didn't know that either. I created some words and shortcuts, then exported them. When I opened the exported file in a code editor, only then could I see that the separator was not a space but a tab character.
Error 2:  No language for the words
This error is minor. Your words didn't belong to any dictionary language. It seems when you don't add the language, the words & shortcuts are not imported or GBoard just decides to ignore and select a language for you (I have not checked why). So, you must add a language at the end of each words separated of course by Tab characters.
Error 3:  No dictionary version
Add the dictionary version at start of the file. GBoard ignores the language (see Error 2) which is bad if like me you have many languages enabled.
I have not found yet how to add words to the "All languages" dictionary (although you didn't ask).

I imported to "all languages" successfully, i had a line at the top of the file like this "# Gboard Dictionary version: 1"


text:
Can i add money to a google play gift card and how
Can I add funds, and how if I can. If I had a 10 pound Google play card and I needed 14 pounds on it can i add 4 pounds to it?

Answer is to your question is No, you cannot add an amount to a gift card after purchase. You'll have to purchase another gift card & redeem both in order to accumulate the desired amount.
As per the Comments
There is no information which actually states this. but this document says that user can use multiple gift cards to complete the purchase. What I've seen is, third party seller sells the gift card & updates the gift card number with the amount to google. so I don't think there is any provision to update amount later. otherwise they would have stated that way.
 https://play.google.com/intl/ALL_ALL/about/card-terms/

Any supportive information to link to? Some rule or policy stated somewhere accessible to document this?

there is no information which actually states this. but in below-given documents says that user can use multiple gift cards to complete the purchase. What I've seen is, third party seller sells the gift card & updates the gift card number with the amount to google. so I don't think there is any provision to update amount later. otherwise they would have stated that way. https://play.google.com/intl/ALL_ALL/about/card-terms/

People tend not to read comments, and, they are transitory, so information can be lost. Please edit your additional information into your post to solidify it. Thanks.

Done that . Thanks


text:
How to undo "Enable autofill for [website]" in Firefox?
My question is similar to [Undo "Disable autofill for [app]" one), but the solution doesn't work for me, so please bear with me.
I'm using Keepass2Android for autofill. It works great in most apps. It also worked in Firefox until one day I pressed Enable autofill for [website URL]. Now it doesn't work for this website. There's no autofill popup, so I can't undo this like I could in other apps. I've also done this in Firefox Preview and it stopped working altogether for all sites in that browser.
What I've tried:

Solution from this question - I don't have the 3 dots button
Reinstall Keepass2Android - no change
Reinstall Firefox - no change
Clear Firefox cache and data - no change

I'm using OnePlus 6T with latest OxygenOS (Android P-based).

The issue went away either due to Keepass2Android update last month or upgrade to Android 10. I won't try to enable autofill now because I'd rather have it working and I don't want to take any chances.

External autofill apps change a certain boolean in the Firefox for Android configuration variables, this "setting" can nly set back to the old setting by completely uninstalling and reinstalling Firefox or better by changing it in: about:config

goto about:config
search for: dom.forms.autocomplete.formautofill
set it back to true
refresh your login window and... fixed!

As I wrote in the question, reinstalling Firefox didn't fix it. I can't verify if about:config method works because the issue went away on its own.

looks very possible that the reinstalling Firefox method does not work as by default Google (Play Services) saves and syncs app settings for when you reinstall them. But I had the same problem and for me the about:config method worked.


text:
Play store stuck on 'Download Pending' or 'Waiting to Download'. How to fix?
TL;DR - How to uninstall the Google Play store?

A friend of mine deleted my Google Account as a prank (don't know how it is a prank). When I came home, I just logged in and tried to install some apps, but it wasn't downloading and stuck on Download Pending.
Here is a list of troubleshooting I did:

Force stopped and disabled. Cleared data and cache. Uninstalled updates. Restarted the APK but still didn't work. Yes, I also gave it time to update.

I deleted all my other accounts and just kept my Google Account. Did the same as 1), didn't work.

OK. I remembered that there are modded Play Stores available online. So I downloaded the Lucky Patcher Google Play Store (modded) ver. 14. something and it didn't work. Also, did 1) again after I installed it.

When I uninstall the update for the modded app, it requires authorization, meaning I would have to sign in again. No problem, but there is no option to log out, meaning the arrow drop-down doesn't appear. Also, I signed out from Settings and relogged in from Play Store, but still, when I open it, it asks for authorization again.

I tried to install the Gapps again. In the XDA forum, it was stated that you just need to install the package again and it will replace the existing Gapps. I did it. I downloaded the nano package. But it asks for Authorization. Still no drop-down.

I am back again with the Lucky Patcher app. It will let me browse APK and use Play Services, but it won't let me install APKs.
How to uninstall Play Store and reinstall it?

As you installed GApps on your own you are using a custom ROM. May be just just ran into the Google certification for custom ROMS which is now required. Old installations continue to work, but it is required for new installations. Deleting and re-adding the Google account may be considered by Google as new installation: https://lineageos.org/Google-Play-Certification/

I had a similar issue after trying to install a custom ROM onto an old tablet. In my case, the solution was to change to a different build of GApps.
I had tried to install the Slim6 ROM (Android 6.0.1 Marshmallow) onto a Samsung Galaxy Tab 2 GT-P5110), with Open GApps Pico (also tried Nano).  This appeared to work: I could add my Google Account and browse apps in the Google Play Store, but anything I tried to install or update just hung on "Pending..."  None of the normal advice about clearing caches worked.  I fixed the problem by installing the Delta version of GApps base, after which everything seemed to work fine. I didn't even run into the Certification issue mentioned by @Robert - maybe my setup was too old!
If you run into the Pending Downloads problem after installing a custom ROM, my advice is to research the threads for your ROM in the XDA Forums, and look for a known-good version of GApps that works with that ROM.  Hope this helps someone else in the future!