text:
Check what storage an app uses?
Is there a way to check what storage a third party application is using? i.e  which of these it uses?

If you are rooted, this is quite easy to find out.
First you need to find the app's package name, e.g. com.swype.android.inputmethod for Swype, or com.google.android.apps.maps for Google Maps, for example.  You can usually search for the app in Android Market, and the link will contain its package name, e.g. https://market.android.com/details?id=com.google.android.apps.maps would be the link to Google Maps.  Usually the package names are descriptive enough that you can simply guess which app they represent just by looking at it.
You can do a few simple ls commands in Terminal Emulator or ADB shell to find out the app's name, and where it's stored.  However, you will need to have root access to the device since app and data storage is protected.
Pre-installed apps are generally located in /system/app directory.  Use the command ls -l /system/app/ to find how much space a particular system app is taking up:
ls -l /system/app/Browser.*
-rw-r--r-- root     root               418098 2011-06-26 01:05 Browser.apk
-rw-r--r-- root     root               472760 2011-06-26 01:05 Browser.odex

On most Stock ROMs you will see an .odex file along with a .apk file for each app - those are pre-compiled binaries optimized for your given device.  You cannot remove them.
3rd-party apps are installed to /data/app or /data/app-private directories.  Command ls -l /data/app/[package_name_here]* should return the amount of space taken up by this app on internal memory.  For example, here's the output of looking at Google Maps apk:
# ls -l /data/app/com.google.android.apps.maps*
ls -l /data/app/com.google.android.apps.maps*
-rw-r--r-- system   system            6330104 2012-02-04 09:01 com.google.android.apps.maps-2.apk

The app data and settings are located on /data/data/ partition.  There you will find a directory for each installed app, e.g. /data/data/com.google.android.apps.maps/ for preferences and settings related to the Google Maps app.  Again, ls -l /data/data/com.google.android.apps.maps/* will return a listing of all files with their sizes:
# ls -l /data/data/com.google.android.apps.maps/*
ls -l /data/data/com.google.android.apps.maps/*
-rw------- app_189  app_189              3783 2012-02-07 11:29 mobilemaps.clients.google.com.443
-rw------- app_189  app_189                37 2012-02-01 16:14 nlp_GlsPlatformKey
-rw------- app_189  app_189               208 2012-02-07 11:21 macs
drwxrwx--x app_189  app_189                     2012-02-01 16:14 webviewCache
-rw------- app_189  app_189              2450 2012-02-07 11:21 nlp_state
drwx------ app_189  app_189                     2012-02-01 16:14 selectors
-rw------- app_189  app_189               290 2012-02-07 11:21 nlp_devices
drwx------ app_189  app_189                     2012-02-01 16:14 models
-rw-rw---- app_189  app_189             18432 2012-02-03 13:29 google_analytics.db
-rw-rw---- app_189  app_189              5120 2012-02-07 10:38 google_latitude.db
-rw-rw---- app_189  app_189              6144 2012-02-01 16:14 webviewCache.db
-rw-rw---- app_189  app_189              5120 2012-02-05 17:27 local_active_places.db
-rw-rw---- app_189  app_189              4096 2012-02-05 17:27 da_destination_history
-rw-rw---- app_189  app_189              5120 2012-02-05 17:49 LayerInfo
-rw-rw---- app_189  app_189              5120 2012-02-05 17:26 search_history.db
-rw-rw---- app_189  app_189              6144 2012-02-03 13:29 userfeedback.db
-rw-rw---- app_189  app_189             14336 2012-02-01 16:14 webview.db
-rw-rw---- app_189  app_189                38 2012-02-07 11:13 DATA_SYNC_DATA_LOCAL
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_145479516184369608
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_4406538396446325405
-rw-rw---- app_189  app_189              1813 2012-02-05 13:48 DATA_PROTO_CLIENT_SAVED_PHOTO_CACHE
-rw-rw---- app_189  app_189               338 2012-02-06 23:41 DATA_TILE_HISTORY
-rw-rw---- app_189  app_189                12 2012-02-05 17:49 DATA_SAVED_REMOTE_ICONS_DATA_BLOCK
-rw-rw---- app_189  app_189             36580 2012-02-01 16:14 DATA_RemoteStringsBlock_en
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_240647554975296207
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_443613581827136957
-rw-rw---- app_189  app_189              5620 2012-02-05 17:49 DATA_SAVED_BGFS_3
-rw-rw---- app_189  app_189                57 2012-02-05 17:49 DATA_STARRING
-rw-rw---- app_189  app_189               573 2012-02-05 10:04 NavZoomTables.data
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_-7991748045000310303
-rw-rw---- app_189  app_189               217 2012-02-05 15:29 DATA_LAYER_4
-rw-rw---- app_189  app_189             26756 2012-02-01 16:14 DATA_PHOTO_-4352347968798340772
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_-1960244636679913737
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_7546641620697631512
-rw------- app_189  app_189                34 2012-02-07 11:21 nlp_clts
-rw-rw---- app_189  app_189              2492 2012-02-07 11:30 DATA_location_history
-rw-rw---- app_189  app_189                11 2012-02-01 16:14 DATA_LAYER_0
-rw-rw---- app_189  app_189              1186 2012-02-01 16:14 ZoomTables.data
-rw-rw---- app_189  app_189                11 2012-02-05 17:49 DATA_SAVED_BGFS_EXTRA_3
-rw-rw---- app_189  app_189             18994 2012-02-05 17:49 DATA_PROTO_SAVED_CATEGORY_TREE_DB
-rw-rw---- app_189  app_189               247 2012-02-05 17:49 event_store_v2_driveabout
-rw-rw---- app_189  app_189              5294 2012-02-05 10:05 DA_LayerInfo
-rw-rw---- app_189  app_189               380 2012-02-05 16:23 DATA_LAYER_5
-rw-rw---- app_189  app_189             11387 2012-02-05 17:49 DATA_SYNC_DATA
-rw------- app_189  app_189                35 2012-02-07 11:21 cp_state
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_-6319433669272599441
-rw-rw---- app_189  app_189                76 2012-02-01 16:14 DATA_ServerControlledParametersManager.data
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_-4787236618283354619
-rw-rw---- app_189  app_189                57 2012-02-01 16:14 DATA_star_details_index
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_-7325828578927889496
-rw-rw---- app_189  app_189                76 2012-02-05 17:27 DATA_ServerControlledParametersManager_DA.data
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_-5041077772587057686
-rw-rw---- app_189  app_189                42 2012-02-05 17:26 DATA_PROTO_SAVED_RECENT_LAYERS
-rw-rw---- app_189  app_189                21 2012-02-05 10:04 DATA_SAVED_BGSF_
-rw-rw---- app_189  app_189               263 2012-02-05 11:30 DATA_LAYER_2
-rw-rw---- app_189  app_189                26 2012-02-01 16:14 NavigationParameters.data
-rw-rw---- app_189  app_189               330 2012-02-05 17:27 DA_DirOpt_en_US
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_-4817178430903221341
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_8476874153932292760
-rw-rw---- app_189  app_189            141298 2012-02-05 17:27 DATA_Restrictions
-rw-rw---- app_189  app_189                29 2012-02-05 17:49 DATA_PROTO_SAVED_LAYER_STATE
-rw------- app_189  app_189                61 2012-02-01 16:14 nlp_params
-rw-rw---- app_189  app_189                 0 2012-02-05 17:27 DATA_Restrictions_lock
-rw-rw---- app_189  app_189             26756 2012-02-01 16:31 DATA_PHOTO_8041021750103678571
-rw-rw---- app_189  app_189             10237 2012-02-03 13:28 DATA_star_details_0
-rw-rw---- app_189  app_189                 6 2012-02-05 17:49 DATA_RECENT
-rw-rw---- app_189  app_189              5048 2012-02-06 23:41 DATA_Preferences
-rw-rw---- app_189  app_189                65 2012-02-01 16:14 network_initiated_prefs.xml
-rw-rw---- app_189  app_189                65 2012-02-01 16:14 friends_app_widget_preferences.xml
-rw-rw---- app_189  app_189              1269 2012-02-01 16:14 ids.xml
-rw-rw---- app_189  app_189               250 2012-02-03 13:27 settings_preference.xml
-rw-rw---- app_189  app_189                65 2012-02-01 16:14 cache_settings_preference.xml
-rw-rw---- app_189  app_189               358 2012-02-07 11:28 checkin_notification_preferences.xml
-rw-rw---- app_189  app_189               119 2012-02-01 16:14 com.google.android.apps.maps_preferences.xml
-rw-rw---- app_189  app_189               345 2012-02-05 17:49 DriveAbout.xml
-rw-rw---- app_189  app_189               317 2012-02-07 10:38 LOCATION_REPORTING.xml

Android 2.2 (Froyo) introduced the ability to move apps to SD card (or "external storage" on some devices).  This introduces a level of complexity since portions of the app get moved around.  For every app that you move to SD Card/media area, the system creates a virtual mount point named /dev/block/dm-X, where "X" is a sequential number.  It them moves the app's APK (Android package) file and some preferences there.  You can view this by issuing a mount command in shell/terminal emulator.  Along with other usual mounts, it should show which apps were moved to SD Card like in an example below:
/dev/block/dm-0 /mnt/asec/com.metago.astro-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.a0soft.gphone.aTrackDog-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

Here I moved Astro file manager and aTrackDog apps to the SD Card on my phone.  Use ls /mnt/asec/ to view the directories created for the moved apps.  Issuing command ls -l /mnt/asec/* will list the file sizes within those folders:
# ls -l -a /mnt/asec/*
ls -l -a /mnt/asec/*
-r-xr-xr-x system   root               332826 2012-02-07 11:21 pkg.apk
dr-xr-xr-x system   root                        2012-02-07 11:21 lib
-r-xr-xr-x system   root              2363522 2012-02-07 11:18 pkg.apk
dr-xr-xr-x system   root                        2012-02-07 11:18 lib

The wrapper for the virtual partition gets stored inside a hidden ".android_secure" folder of the SD Card:
# ls -a -l /mnt/sdcard/.android_secure
ls -a -l /mnt/sdcard/.android_secure
----rwxr-x system   sdcard_rw          4290560 2012-02-07 11:18 com.metago.astro-1.asec
----rwxr-x system   sdcard_rw          2161664 2012-02-07 11:21 com.a0soft.gphone.aTrackDog-1.asec

Once moved the app's APK will no longer be under /data/app/ or /data/app-private/ folders.
Another area of interest is Dalvik Cache - an area that contains cached data for each installed app.  Upon first boot-up or new app installation the system generates a .dex file for each app that it uses for quicker start-up.  These files are stored on /data/dalvik-cache/ partition.  Command ls -l /data/dalvik-cache/*[package_name_here]* will return the space taken up by the app's Dalvik cache.  For example, here's how much space is taken up by Google Maps app:
# ls -l /data/dalvik-cache/*com.google.android.apps.maps*
ls -l /data/dalvik-cache/*com.google.android.apps.maps*
-rw-r--r-- system   app_189           4406016 2012-02-04 09:01 data@app@com.google.android.apps.maps-2.apk@classes.dex

Next, the /cache partition of the internal memory may be used by apps.  The command ls -l /cache/ will show you all files stored there, along with sizes and owner information.  For example, on my phone here's the output:
# ls -l /cache/
ls -l /cache/
-rw-r--r-- app_13   app_13            3640954 2012-02-07 09:16 downloadfile-1.apk
drwxrwx--- system   cache                       2011-12-31 21:03 recovery
drwxrwx--- root     root                        2011-12-31 21:00 lost+found

Besides the standard directories, there is a file named downloadfile-1.apk that belongs to something named "app_13".  I can cross-reference this "app_13" name to the listing of ls -l /data/data/ to see that this file belongs to Android's built-in downloader:
# ls -l /data/data/
ls -l /data/data/
......
drwxr-x--x app_13   app_13                      2011-12-31 21:02 com.android.providers.downloads.ui
......

Finally, apps can use the SD Card for their own purposes, and there is really no way to track this, unless the app names its folders something recognizable.

You can also use the find command to locate various pieces of the app on your device: find / -name *[package_name_here*, for example find / -name *com.metago.astro* to find all portions of Astro app, and then do the ls -l on each located piece.

This is a fantastic write up. Thanks for including so many examples!

The du utility is also handy for this purpose.  For example du -skd 1 /data/data | sort -nr will list off all the apps' data folders (but not the individual files) neatly sorted from largest to smallest.

Chahk's answer really deserves more attention, great answer.
I would however recommend the app DiskUsage, which gives a better visualization of used space. For the best features, root is recommended, but not strictly needed.

DiskUsage doesn't require root. I use it myself, and my devices are most definitely not rooted.

@Al Everett You are correct, I have edited to better reflect that. You can use DiskUsage for /sdcard/ and /storage/extSdCard without root, but if you want to poke around in the OS folders, then root is needed. Most importantly, /data/ (which houses /sdcard). See This answer


text:
Getting DeadObjectException on uninstalling any app using adb
On a fairly old non-rooted Galaxy Tab A-tablet I wanted to uninstall all the Samsung and Microsoft apps and most of the Google packages to make it faster. Using adb shell pm uninstall -k user 0 I uninstalled 106 packages but after com.sec.android.app.music I suddenly can't uninstall packages anymore. Instead, I get a DeadObjectException and the tablet reboots:
$ adb shell pm uninstall -k user 0 flipboard.boxer.app

    android.os.DeadObjectException
            at android.os.BinderProxy.transactNative(Native Method)
            at android.os.BinderProxy.transact(Binder.java:628)
            at android.os.BinderProxy.shellCommand(Binder.java:675)
            at com.android.commands.pm.Pm.runShellCommand(Pm.java:299)
            at com.android.commands.pm.Pm.runUninstall(Pm.java:674)
            at com.android.commands.pm.Pm.run(Pm.java:170)
            at com.android.commands.pm.Pm.main(Pm.java:103)
            at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
            at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:315)

It looks to me like pm needs something that isn't there, so I might have uninstalled something that it needs. My question is, how do I find out what it was, and, assuming it wasn't the Samsung music app, why did it function correctly until after I installed that?
In an attempt to start over I have reset the tablet to factory settings and all the apps are there again, including the music app, but even now I get the same error when attempting to uninstall any of them.

First, I noticed that user needs some dashes to look like --user Second are you sure that is the package name? "clipboard.boxer.app" because general but not always the case it starts with a com.package.name

OP also posted on XDA Forum, just in case the issue has been resolved there but not here yet.

@AndrewT Sorry for the cross posting but my question got no response there which made me wonder if I even found the right forum for this problem. Can you tell me if it is?

@Lilfuzzybunny007 Thanks for the double dashes suggestion. I will try it when I get home tonight.

@Mr.Wrong no worries :) I accidentally found your thread on XDA while researching for this issue, so I decided to link it here... just in case there are additional details posted on there but not here. FWIW, this question is on-topic on here (issues faced by Android end/power-users).

Are you able to uninstall other packages or is it only this package that fails to uninstall? Have you tried to reboot the device?

@Robert I get this error with any package I attempt to uninstall. The above is just an example.

So it appeared @Lilfuzzybunny007's suggestion worked. Thanks everyone!

I noticed that user needs some dashes to look like --user
Second are you sure that is the package name? "clipboard.boxer.app" because general but not always the case it starts with a com.package.name

source: Stack Exchange

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

sort: votes


text:
Android lock screen password not being recognized
I flashed the latest Cyanogenmod ROM for my device (Samsung Captivate) last night and after doing so I set a numeric lock screen password.  I then customized my phone and spent a goodly amount of time working on it and locked and unlocked it successfully multiple times.  This morning when I woke up and went to unlock it, my password did not work.  I have tried the password (and combinations thereof) over 100 times and it never unlocks.  I also never get the "Lost Password" button on the lock screen to use my Gmail account to unlock the device.  Does anyone know if there is a way to connect to the device using an ADB shell and reset the password? I am able to get to a shell and can run commands.  Any help is appreciated.

Yes, you can delete the PIN data from the settings database. In the below instructions, anything that follows a # or sqlite> is a command you should enter (from an adb shell):
# cd /data/data/com.android.providers.settings/databases
# sqlite3 settings.db
sqlite> delete from secure where name='lockscreen.password_type';
sqlite> delete from secure where name='lockscreen.password_salt';
sqlite> .exit
# reboot

When the phone reboots the PIN lock should be disabled. If this doesn't work then try executing the following from within sqlite (second might not be needed):
sqlite> select * from secure;
sqlite> select * from system;

These two commands will simply list all entries in the secure and system tables, respectively. That will help you find the proper rows that need to be deleted in the case that they are named differently (though I don't think they will be as I just tested this on my own CyanogenMod 7 install).

I ended up re-flashing and restoring from a Titanium backup I had.  However, out of sheer curiosity, I am testing what you have posted and even after deleting the two entries from the database file and rebooting the lock is still on the screen and I can find no way around it.  I did confirm that both lockscree.password_type and _salt are no longer in the database file.  Any other suggestions?  Like I said this is not critical at this point, it is now an experiment in Android security.

@t11m: Hm, I'm not aware of any other relevant entries offhand, but maybe I'll mess around with it a little bit. Just deleting those two definitely works for me if I set up a PIN lock...

Here is how a Samsung GT-S5300 was unlocked which according to the user would not recognise its screen lock PIN anymore.
No data was lost during the process. The device was not rooted, nor did it had anything fancy installed. An internet connection ---WiFi or G2/3/4--- is required though.

Unplug the charger from your device.
Install the free version of Screen Lock Bypass Reset. Ignore any warnings about purchasing the Pro version.
Once installed, a bypass can be activated by plugging in the charger.
The black Screen Lock Bypass Reset screen appears. Hit the return key ⏎ on your device to show the temporarily unlocked device desktop.
This offers a window of opportunity to approve the Lock & Erase application which can be sent from any internet the Google Android Device Manager website.
After approval, it may take anything up to half an hour to become visible on the Google Android Device Manager website.
Once visible on the website, click on Lock to enter a new PIN.
The device can now be unlocked with the new PIN.

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


text:
Does my Android phone uses battery or outlet power to operate while being charged?
I am curious about knowing which power source does my android uses up, while it is being charged while switched on..
I know i can test it by keeping it in charging and pulling the battery.. but i am unsure if its safe enough..
Anyone having any ideas??
If it uses outlet/USB power for operation,then i can be assured of keeping it plugged in and use wifi tethering for net surfing for long periods.. without thinking of any battery damage due to prolonged charging..am i right on this?

From my experience, my phone (HTC Desire) seems to use battery while being charged... or at least a combination of both. Reason is, while plugged in, if I am doing something intensive - eg playing games, I notice that either the battery % hasn't really increased or has actually decreased!
Also, not sure which phone you are using, so the behaviour maybe different to the Desire, but I'm guessing it uses a lithium-ion battery - here is some good info on "the best way to use Li-ion batteries" http://arstechnica.com/gadgets/news/2011/02/ask-ars-what-is-the-best-way-to-use-an-li-ion-battery.ars
Basically:

They don't have memory
Don't worry about overcharging
Don't completely deplete the battery - lowest ~20%
Use your battery - you need to 'exercise' the battery
Try to keep the battery cool

The Nexus 9 actually loses battery while playing games while charging

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


text:
My android phone was stolen. How worried should I be with all my google data inside the phone?
Ok, so my samsung galaxy 5 was stolen. I had gmail, calendar, twitter(tweetdeck), facebook, ... all my personal data in it.
I didn't have any app installed that could wipe this information from a sms (tried to install PlanB through the market, but I don't think it'll work).
I already changed my google password and I'm proceeding to change facebook and twitter as well.
Is this enough? How much of this information (old emails, tweets, ...) are saved in the phone's memory? Can I prevent access to this just by changing my passwords?
I've blocked my SIM card with my provider, so I guess the phone currently have no internet or telephone line access.
Here in Brazil we can also block a stolen cell phone with the IMEI number, but I don't know exactly what this means. Will this brick the phone or just prevent it from being registered in the network?

I suspect PlanB won't work after you change your Google password.

Remote wipe programs like Plan B only work if your phone still has battery and still has a data connection through the internet to download the app, if you'd pre-loaded a program like LookOut then it would work without a data connection but would still need a phone network connection to receive an SMS text message or something like that. If you've blocked your SIM and/or blocked your IMEI then it's too late to use a remote wipe program as you don't have any way to get any kind of message to your phone any more, you need to do the wipe before getting anything blocked by your phone company.
Did you have any kind of unlock code (pattern or number, or something like that)? If so that should stop the thief easily getting to any of the data on the phone itself, and if they enter the wrong code/pattern a number of times it totally locks the phone out, and you need to go online (and log in with your Google account) to unlock it. They can apparently still get to data that's directly saved on your phone if they plug the phone into a PC that has the Android Developer tools on it and use the ADB command, but even then some things like the central Accounts database are encrypted to stop them getting your passwords.
Blocking the phone via IMEI will stop anyone else being able to use the phone on a phone network, it won't do any wiping or bricking at all.
There's also your SD card, the thief can just pop that out of the phone and straight into a computer or another phone, nothing on there is protected, see this previous question for a discussion on what personally identifiable info might be on the SD card: Is there any contact information on the SD card?

The phone storage should be readable as well via ADB.

@Matthew is it, I thought you had to enter your lock code before it would allow direct access, like Blackberrys and similar do? Not something that occurred to me, as my phone removes the lock totally when I'm at home via the Unlock with Wifi app I assumed that was why I was never prompted for it. Bit of a security hole in that case.

I've never had to enter the code on my phone, and I can't find anything to suggest that it's different for others, although some do want the option. In the end, there's not a lot you can do to thwart someone with physical access unless you encrypt everything.

@matthewRead USB debuging has to be enabled  on the phone in order to use adb. This is off by default.

@Flow Only when the phone's booted up. I've accessed my phone via adb from either recovery or download mode while USB debugging was off, since obviously those modes don't check OS settings.

If you have your sasmung account setup, you can track, lock and wipe your phone from the samsung website.
This is the one : Samsung Phone Locator
But remember, this would need you to have setup the Samsung account already.

If your mobile was stolen you can use Android device manager to erase data on your stolen mobile, ring the device, find exact location of mobile.
It requires mobile to be online for it to work.


text:
How can I execute a script on the SD card and be able to pass arguments to it?
I tried executing a script on the sdcard as is because on FAT, everything is 777.
./.profile
./.profile: permission denied

I added this as the initial command for the Android shell and it executes it just fine:
eval "$(cat /sdcard/.profile)"

So what I'm wondering is: Is there a way I can execute a script on the sdcard (other than the way I found out) and be able to pass arguments to it or do I need to do it the normal BTEP way (in its data directory)?

Does sh .profile arg1 arg2 works?

You know what, that's a good idea. I have to stop over complicating things :-P

Moved from comments and expanded.
Invoking the script with the shell directly sh .profile arg1 arg2 should work. If it become cumbersome to invoke the shell and typing the arguments, you can also create an alias, most terminal emulators allows you to specify an initial command to run at the start of a session.

You will probably be unable to directly execute scripts from your sdcard. At least without root. Reason is, with most ROMs sdcards are mounted using the noexec flag -- which means, as the term suggests: "no exec from here". Of course, having root you could simply remount the sdcard while removing this option.
Why might this option be forced? I'd say for security reasons. While on internal storage, apps are quite limited regarding where they might write to, on sdcards they can write everywhere. So this could be used by some "evil guys/girls" to place their malware scripts -- but that's just a guess.

That makes sense.


text:
How do I prevent screen dimming for specific apps?
My phone has Android 4.0.4 (ICS). Now, I use several apps for reading like browser, Wikipedia, Adobe Reader, etc. Only Adobe has a screen dimmer setting.
Is there an app or setting that allows me to stop the screen from turning off while I have any of these apps open for reading?

That's one of the many things Tasker does for me, with a quite simple profile:

Condition: App (select your browser, reader, etc., multiple apps can be selected simultaneously)
Task: Display-Timeout (all sliders to max = never)

Optionally, you also can adjust screen brightness. Then, as soon as one of the selected apps is running in the foreground, that action triggers – the screen won't turn off anymore. When you bring another app in front which was not selected with your condition, Tasker reverts to the previous state automatically.
Of course, there are also several apps available just doing that and nothing else; but having one app (tasker) that can doing this and so much more, I forgot about them long ago...

Found this while searching for info on how to prevent screen dimming in KOReader. In KOReader in top settings > Settings (Cogwheel icon) > Screen > with Automatic Dimmer enabled it is possible to set Idle time for dimmer to a custom value.
Disabling Automatic Dimmer did not result in the screen not dimming, since it seems KOReader then was following general system settings for which I wanted to keep screen dimming.

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


text:
Apps can't see wide-angle camera in Xiaomi Redmi Note 9
I have a Xiaomi Redmi Note 9. With the built-in Camera app, I can make a video using the wide-angle camera (x0.6). But using DJI Mimo, A Better Camera, or Filmic Pro, I can use only my standard camera (x1.0).
Can I fix it somehow?

As far as I know such "special cameras" are often not accessible via Android's standard camera API, hence each app needs to be adapted for your device to be able to use e.g. the wide angle camera. This require a lot of effort so not every camera app developer does this.
Therefore the answer is: You can't fix this on your own, only the developer of the camera app can adapt the app to make it work.


text:
How to flash Cubot R11 stock ROM on bricked phone?
I am using Ubuntu and while attempting to root my Cubot R11 phone using fastboot, I ended up on a boot-loop cycle. Also, power+volume-up to enter recovery mode isn't working.

Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds

How can I fix this issue (Linux tools preferred)?

You can use SP Flash Tool. You need MediaTek MT65xx USB VCOM Preloader USB Drivers for it. If you care about data, you should make a full rom dump (or at least nvdata metadata oemkeystore and userdata partition). You need a scatter file for this. A scatter file you can create with WwR MTK v2.30.
If fastboot is working, you can try "fastboot format:ext4 cache" to fix bootloop. You can try to port a TWRP and "fastboot boot recovery.img" then you get full access via adb in recovery (and if metadata is still intact it will hopefully decrypt userdata).
If the bootloop is caused by flashing TWRP, install Universal Disable_Dm-Verity_ForceEncrypt.zip to disable the dm-verity boot chain validation.


text:
Can't add icons to home screen
I have an ASUS ZenPad 3S 10 (Z500M, model P027) and I can't add any shortcut icon from the app drawer to the home screen by pressing and dragging.
I know I used to have this option, but now something has changed and prevented it.

Welcome to Android Enthusiasts! Have you tried to clear the cache of your launcher? Try another launcher and check if the issue remains.

The issue might be that the launcher layout is locked. Try to remove or replace an icon already present in launcher and if you can't move the icon, then most likely the layout is locked.
To turn off the option, the ways are different in different launchers, try going to launcher settings and find option to lock the desktop layout or something similar and turn it off.

Thanks to everyone, I did not know that it is an app that launches Android out of the root; now I do.
After researching several launcher apps, I got enough understanding to look for the launcher for my tablet. I found it under default apps and it is actually part of the onboard software apps, i.e. resident and native to the hardware, that can not be uninstalled but it has two levels/layers and one of those levels put the app's icon on the bottom drawer so that it can be accessed as I was looking for.


text:
My SD Card gets corrupted every time my phone reboots or shuts down
I have a 32GB SD card, however, every time I mount it into my phone (Huawei Y5II), it shows a message that the SD card is corrupted and I should reformat it.
I backed up my files to my PC, and formatted my sd card. After that, the SD card finally worked.
However, every time my phone is rebooted or shuts down, the SD card just gets corrupted again.
Meanwhile, I found another solution without formatting, by using CHKDSK in command prompt, which did work, but it's still the same every time the phone reboots or shuts down and back, it says SD card is corrupted!
I have tolerated this problem for a year now.
Now I think because of this, I experience more issues with my SD card. Like some files suddenly turning into 0 bytes, some files getting missing, files being renamed, etc.
Should I replace my sd card(or phone) with another one? If yes, do you have any suggestions on what brand or model?

Have you tested the sd-card that it really has 32GB flash? There are cards on the market that claim to have 32GB bit only contain 16GB or less flash. Such a card could explain why it alway sis getting corrupted. Use a tool like h2testw to test the sd-card after formatting it.

Seems like an exceptional case, Android should un-mount SD card cleanly on shut down and run fsck (equivalent to Windows' chkdsk) on device boot.

It's more likely that your SD card came corrupted. Have you tried with another SD card?


text:
How can I reset MIUI 11 features?
I turned off MIUI optimization and some features were lost and I can't retrieve them after I turn it on again.

I've done that but I still can't get back the MIUI 11 UI display

You need to enable Developer options on your MI device.
To unblock the developer options,

Go to Settings >About, find the MIUI version and tap 7 times continuously.
You could see a message “You have enabled developer option” once you have successfully done that.
To access developer options, Goto Settings > Additional settings > Developer options.
Now scroll down till the end to see the option to toggle MIUI Optimization. You’ll need to restart the device once you enable the option.

Even though it is just a toggle which we enable, it causes the way which the system behaves, in turn changes the way many apps behave.

Source


text:
Is it possible to restore an ASUS Backup on an emulator?
I had created a backup file using Asus Backup app Link Playstore from my Asus ZenFone (Android 5.1).
I have lost my Asus phone and I'd like to restore the backup into an emulator.

Does Genymotion have any ASUS VM?
Is there any Emulator that support Asus Backup App?
Are there ASUS Zenfone Emulators?
Can I, in any way use Android Studio to restore my Backup created using ASUS Backup App?
Asus Provide System file from there official site. Can I flash that(Custom Rom) into any Emulator?

Is there any way I can install Asus Backup app in Laptop and restore the Backup I have made?
Is there anything that I can try?

Playstore link gives error in desktop,but opens correctly when choose open with playstore app in android

The app description is funny: "ASUS Backup will NOT backup the data stored in the internal storage" - if it does not backup the internal storage what else does it backup? Anyway I would first check the backup file itself if it is a known format. Use an hex editor to view it and test to with various tools like 7zip.

Means It does not backup pictures snd other suffs Example: If you backup Galley app, It doesnt backup images,videos etc... but it does backup Gallery app and App data like app settings etc..

extension,, format is .abu1

I think ASUS just just the wrong term because "internal storage" means normally all the data on your internal flash, this includes all apps, all app private data + the internal sdcard folder with music/pictures/videos. If the description would be correct the only part ASUS backup could backup would be data on the external sd-card.

The description is wrong.. I have used that app many times is past.. It does backup App Data

@Robert Can I do something with android studio

Android Studio is for developing apps, not reading Asus backup files. If you are a programmer you can reverse engineer the Asus backup app e.g. using Jadx or apktool. Additionally you can reverse-engineer the backup files you have, but that also requires a bit of experience.

@Robert Is there any way around by flashing custom rom on an emulator..see 5th point..

If such a custom ROM would exists, most likely yes. However custom ROMs for emulators are pretty rare as to find one specific for the old Asus device you are searching - unlikely. IMHO if the backup is really of that value to you you should buy a used Asus zenfone. Or try to to sind a smartphone test farm that has Zenphones (a test farm allows to remotely access a physical device for a limited time).

@Robert https://android.stackexchange.com/questions/218061/flash-custom-rom-on-android-emulator


text:
AppMgrIII doesn't uninstall android bloatware - only disable
I have an old LGLS660 with 4 MB internal memory making install of new apps almost impossible - added MicroSD card to expand by 16 GB - rooted successfully with kingoroot.
So I d/l this app I was able to move some apps but not uninstall the android ones I don't use which was the entire point of all this fiddling.
How should I get rid of the unwanted apps?

after looking at KINGOROOT more carefully I realized it has built in tools to remove the android apps. So I uninstalled this program b/c it was not necessary.


text:
Combining two single sim phones (backup) into one dual sim phone
Is there any method of combining the Android backups from two mobile phones when I move from two single sim phones to a dual sim phone?
I have a Samsung Galaxy S4 running my UK contract SIM, and a ZTE running my PAYG German sim.
I have just purchased a S9+ and I want to use both sims in the one phone. This is not an issue for me.
I have some data stored on the S4 which I do not wish to lose, and some data stored on the ZTE which I also do not wish to lose.
The Android backup show for both phones by name, but I can only use one to migrate my data.
How do I combine the data on two different phones, into a single backup that can be used on my S9.

Backups of what ? Contacts? Photos? Apps? Are both those earlier devices rooted? What Android versions are they running?  Do you plan to root the new device? Please [edit] to add these and more information that would help folks answer


text:
How can I install the Google Apps Package (Play Store, ...) on my Android device?
I have recently installed a custom ROM and cannot find the Play Store. It seems like all apps that belong to Google are missing.
How can I install the Google Apps Package (Play Store, ...) on my Android device?

@tomm13b: Cyanogenmod are not "official", the only official distribution of Gapps is from manufacturers that shipped a device that passes the CTS and Google Play for updates.

Background
Only Android devices that are licensed by the Open Handset Alliance contain the so called Google Apps. Usually people associate apps like Google Maps, Google Play Store, etc. with Android, but because of the open-source nature of Android, manufactures can sell Android devices without Google Apps and therefore avoid to pay the license fee.
Custom ROMs
At first cyanogenmod shipped its ROM with pre-installed Google Apps. In September 2009 the founder of Cyanogen received a cease and desist letter from Google, demanding that the Google Apps not be included in the team's ROMs, since the ROM could be ported to devices which are not licensed to have the Google Apps. In turn, that would bypass the requirement for the devices to be licensed. For a few days, development on the ROM ceased, there were outcries from Android users all over the Internet, and many bloggers suspected Google had just shot itself in the foot.
Eventually, an alternate method was found, whereby Google Apps are not included in the ROM proper but the Google Apps which came with a device would be backed up by the device's custom recovery or another app, and then re-installed onto the device once the new ROM was flashed. This would therefore "Google-ify" one's ROM.
Source
How to install Google Apps?
Generally speaking:
First download the package corresponding to your version of android. Currently (november 2015), there are several "distributors" of Gapps available. Each typically offers a set of packages per android version, each package with more content. The apps in the packages range from a lite package with the basic apps (~100MB) to all of googles apps(200+MB). The applications themselves are untouched.

If you don't want to or cannot root your device:

Flash the Gapps (Google Apps Package) zip package with a custom recovery.

You may first need to flash a custom recovery (like CWM or TWRP) using a PC tool such as Fastboot or Odin/Heimdall. This flashing in turn may require an unlocked bootloader on the phone.

If root is not a problem: (See if you can root the device)

Some stock recoveries will let you "update with adb". Just install adb, then adb command to install is:adb sideload gapps.zip--assuming the package is in the adb folder and is called gapps.zip
You may also install a custom recovery like in the unrooted case.
Root typically allows android apps to flash a new recovery (i.e. without a pc).
OR
Install a ROM with the Google Framework, if it exists for your device. Though many ROM developers have followed CyanogenMod's example of separating distribution.
If you flash a Gapps ROM, it may be possible to re-flash with another non-Gapps ROM afterwards while retaining the Gapps. This assumes the android versions are compatible.
Most users capable of flashing a ROM will be capable of flashing Gapps separately.
Further References

How to install Google Apps (GApps) on your Android Device / Phone

The download links do not seem to work.

As detailed in the FAQ, download the appropriate gapp from this site

http://opengapps.org/

Then install it using recovery.

I wanted to add to this as there is no link to where to get the GApps.  The newest group is Open Gapps.  These do not work with EVERY custom ROM, but the vast majority (and those based on AOSP should work).
Open Gapps: http://opengapps.org/
This site is awesome because when loaded you get a basic UI with a couple selections that allows you to specify what you want (some packages have more google apps, others have less), they even have an option to include the Aroma Installer version which when flashed in TWRP or clockwork will actually bring up a menu system which you can tap to make selections of which apps and which settings you would like at the time of the install! Of course it is large as it includes everything, but it can be nice to be able to customize the gapps install as you are installing it (and yes it has the ability to save your selections for future installs at the end of the setup UI it will ask if you want to save your selections.  If you do future installs it just opens the UI and you tap to load the saved file and done).
Open Gapps has help ?s all over and documentation on their site to help you with many questions.
Cyanogen MOD has their own version of Gapps (page lists gapps packs for every version of CM ROM from CM4+ on this page.  Note that as of CM11 CM Roms can now flash Open Gapps.):
https://wiki.cyanogenmod.org/w/Google_Apps
(looks like as of CM13 they have stopped their custom Gapps zips and now fully use Open Gapps).
With these 2 links you should be good to flash GApps with just about any version of Android (I can not account for a severely custom job done by someone that may not work with Open and/or CM GApps, as we know what happens when we assume in the tech world!).


text:
What does HBOOT mean?
My best guess as of now is "partition and mount point layout". But it feels like there's more to it, since the bootloader can identify the HBOOT by name.
I've been flashing custom ROMs for quite a while now, but I still haven't quite grasped what HBOOT really is or means.

HBOOT is bootloader. It lives inside NAND's first partition, mtd0 (if partition map is MTD). It is loaded in memory (RAM) when device is switched ON. Its jobs are:

Check the Hardware.
Initialize the Hardware.
Start the Operating System (Either Android or Recovery).

HBOOT can also support doing more than this like flashing ROMs.
Something More: Nandroid backup and restore don't touch HBOOT.

Curious, is HBOOT manufacturer specific or is it the common name for the bootloader?

@CatShoes HBOOT is manufacturer specific term.. generally used by HTC.

@SachinSekhar Thanks, I have an HTC phone so I see it all the time, but didn't seem to find it with other devices, just wasn't sure.  Thanks, again.

Also the Nexus 9 uses H-BOOT.Even though it is a Nexus.Other Nexus devices use Google bootloader


text:
Sense 4: How to add items to pull down menu?
I just received a HTC One S with Sense 4 installed. I've seen on other Android devices that the pull down menu contains different settings, such as a Wifi button.

Is there a way to add these buttons to the Sense 4 pulldown menu?

Use Widgetsoid from Play Store.

I cannot check you image (corporate proxy forbids), but I take it you mean those "toggle buttons" to switch on/off things like Wifi, Bluetooth, etc. In this case, you can do so e.g. with Elixier (first picture1) or Notification Toggle (second picture2)

Some Custom ROMs also come with something similar pre-installed, as e.g. CyanogenMod does.

I am unable to see left or right picture. Both are at bottom.

Here's the screenshot: https://i.sstatic.net/dZfVJ.jpg :)

Easy is your name... I am not Easy. Thanks for declaring me winner. Tell me if you want its party. BTW, I am using Mobile Web.

Are you really silent?

For chatting I use the chat :) Btw: Better now with the pics? I really forgot to keep the mobile apps/web in mind, thanks for reminding me. Will use above style for pics in the future.


text:
Where is "Stay Awake" option in Ice Cream Sandwich on the Galaxy S3?
I just upgraded to the Samsung Galaxy S III (Ice Cream Sandwich) from the Motorola Droid Bionic (Gingerbread).  On my Bionic, there was a "Stay Awake" check box that made it so my "Screen will never sleep while charging" under Settings->Applications->Development.
I can't find that checkbox on my S3.
Where is that setting in ICS and/or is there another way to keep my screen from turning off in ICS?
Thanks.

It must be a SGS3 thing. On my Galaxy Nexus I find it under Settings | Developer options | Stay awake.

Related questions: http://android.stackexchange.com/questions/13342 http://android.stackexchange.com/questions/12912 http://android.stackexchange.com/questions/6158 http://android.stackexchange.com/questions/23622

Not a direct answer to your question, but I use widgetsoid and add a toggle widget to either the pull down menu or my home screen to toggle "stay awake" settings.

Samsung removed "Stay Awake" from TouchWiz back in the first OTA for the Galaxy S1. Other ROMs like CyanogenMod still have it, and other AOSP based ROMs as well.
Be very careful using any kind of "Stay Awake" options with these devices that have the Super AMOLED screens. I used to use it when developing and testing the apps. I now have a "burn" in the screen from the time and the top bar.

Burn-in is not such a big risk as with older versions of Android since the Holo theme is darker than the previous ones. But a good point.

unless it is 100% black, anything that is on the screen in the "same state" can burn in.

At least in vanilla ICS it's in Settings -> Developer options -> Stay awake, correct me if it's not there in GSIII.
If it's not there, you can try a couple of apps that can do this, at least on older Galaxy series phones.
StayAwake
Stay Awake Widget

Thank you for your answer.  It was good, but not as good as the "you really don't want to do that" answer from Ryan.

My (non-rooted, stock) SGS3 has just been updated OTA to Jelly Bean 4.1.2, and the "Stay awake" option is now present under Developer options (second item, after "Desktop backup password" - the order of options has changed, I think).
Technically not an answer, because the question says "in ICS", but ... upgrade to JB!
(I haven't installed StayAwake or any such app, so this must have come from Samsung, so I assume they are OK with the risk of display burn-in.)

Do you have the "Developer options" menu under Settings?
If not, you may have to enable it.
Go to Settings >
About phone and quickly touch several times (about 10 times) on "Build number".
You'll see a toast saying "You're a developer now".
Then you'll find the stay awake option under "Developer options".


text:
Can I manually download my wifi settings to my Android device from my Google account?
I just purchased my fourth ever Android device - An HSPA+ Samsung Galaxy Nexus phone.
When I purchased my second and third devices (Samsung Galaxy Tab 10.1 and an Asus Transformer Pad TF300T), I found that after I logged into my Google account during my device setup, my devices downloaded all my known wifi hotspots and the network passwords to them, and could immediately connect to any private wifi network that had been saved on my first Android device (An HTC Nexus One).
However, for some reason, this didn't happen on my Galaxy Nexus when I set it up. In fact, when I set up my Transformer Pad, not only did it download my wifi settings, but it also automatically downloaded the apps I had installed on my other devices. My new Galaxy Nexus didn't do that either. I know I checked the box to 'restore backup from Google account' when I set up the device. I did have some trouble logging in at first, so maybe that's the reason?
I'd really like to get my wifi network settings downloaded to this device. I have dozens of hotspots from friend's houses, client's offices, etc, that I don't want to have to re-enter the information for. Is there some way to manually restore this information to my Galaxy Nexus since it wasn't restored during my initial setup? I tried removing my Google account from the device and re-adding it, but that didn't work. Thanks in advance for any suggestions.

I found this page on Google's support site which states the following about restoring your phone's settings during the initial setup:
"Important: If you want to restore your settings, you must do that now during setup. You can’t restore data after setup is complete."
Based on this, I'm guessing there's no way to restore my account data at this point, short of doing a factory reset on the phone and starting over (undesirable at this point). I'd love to be wrong though.

This answers my question "Can I manually recover all my apps installed in another phone with Google account login?". I think the answer is No. But it really annoy, I skip the login period and I cannot restore all my settings.

It is possible to recover Android settings through bmgr.
List your sets using bmgr list sets
Example output:
36df6csd30288e33 : phone
3c559c36e65a9b49 : tablet

Now you can restore com.android.providers.settings with the set you want:
adb shell bmgr restore 36636c7730288e33 com.android.providers.settings

If your previous device was setup to backup your personal data such as WiFi passwords, Browser bookmarks, User dictionary, a list of installed Market applications and other customized settings, all is backed up to Google's servers.
The Automatic restore feature must be Enabled to allow your phone to contact Google's servers an retrieve the previous backup data.
So, carefully, access the settings panel by:

Stating at your home screen, select Apps;
Select Settings;
Go to PERSONAL section, select Backup & reset;
From the BACKUP & RESTORE section configure what you need:
Ensure the appropriate account is selected from the Backup account field before attempting any configuration settings.
Some important considerations:

A setting is Enabled when a check mark is present.
If data back up is disabled, existing backups are deleted from Google's servers.

Useful and related reading:

Backup and Restore Service: Android
Google Backup and Restore Options - Galaxy Nexus by Samsung

Thanks. Unfortunately the screens you point to still don't allow manual restore of backed up data. I do have the backup/automatic restore options checked. Based on what I'm seeing at http://support.google.com/mobile/bin/static.py?hl=en&page=guide.cs&guide=1091391&topic=1088495&answer=168906 , I'm guessing manual restore isn't possible. Also the T-Mobile support page you linked to indicated that there is apparently a known issue with restore at the moment, which may be why my apps and settings didn't restore properly.

Backup and Restore Service: Android needs registration in t-mobile.com :-(.


text:
Applications on SD Card disappear: Gingerbread bug or hardware error?
I have an Huawei Honour running 2.3.6. I have plenty of apps installed and some I have moved to a 32GB sd card.
Now I notice that quite randomly some application that are stored on the sd card just disappear. (I am not talking about the apps become unavailable when mounting the USB file system on a PC, as that is to be expected.)
All that remains is a placeholder-icon that will be removed once I click it, and every hint that this app was ever installed is gone. I have to go to the playstore and reinstall it.
Now I wonder what the source of this problem could be. Is it Gingerbread, or a hardware error (the device itself, or the sd card)?

Do you have an SD card reader or anything of the sort? Might be worthwhile to check the card for errors/bad blocks if you have the ability to do so, I suppose.

I've been Googling this problem for a few days now.  It appears to be based in some startup bug wherein the launcher app scans for existing applications before the SD card (internal or external) is mounted.  First off, use FileManager or equivalent to look at your SD card's contents.  If you see some grey icons with the app names or "com.[appname]" , then you're suffering from this bug.
There are a variety of work-arounds posted in various forums -- too many for me to provide links here.  Rumor has it that ICS 4.04 and JellyBean may have fixed the bug.  In the meantime, you might want to try Link2SD and/or cautious use of tools like App2SD which promise to tell the user which apps should not be moved.


text:
Samsung Gear S3 music sync
I mainly use my Gear S3 for listening music while running or doing exercises in gym. But It is very annoying to add new songs into it. First I have to download new songs to my computer, then I have to transfer downloaded songs to my android phone and then to my Gear S3.
Is there any solutions to make it easier. Best case scenario would be that, I have one folder in my PC and if I add song into there or delete songs, it will sync automatically to gear s3 as well. Maybe it is somehow possible to sync folder in PC to the android and from android to gear s3.
Hope that someone have had similar wish and have found solution.


text:
How to restore deleted pictures from LG K8?
I accidentally deleted some pics of my daughters that was sent in a txt. I found some recovery apps to get them back but my phone has to be rooted.
How do I root my phone and what does it mean?

Welcome to Android Enthusiasts. Kindly look into this for basics of rooting.

You will not need root access if the device runs android 5.0 or above, A photo recovery software is able to recover photos easily without root due to the new changes in Android 5.0 and above, It's still not clear why Android has left this out of the root only features but it's still handy.
The first thing to remember with data recovery is that deleted files are not actually deleted but rather marked as replaceable files ready for new data to replace it, this means you should not to add any new data to the device or it will overwrite the deleted files, so if you fill up the device with more photos, all the old ones will be non repairable ( unless you have software that is powerful enough ) .. Some people say it's possible to repair a file that has been overwritten 7 to 36 times but i don't believe that..
Anyway, the first thing you should try is DiskDigger
This link is to their no root version Photo Recovery
A tip for using disk digger :   Sometimes changing the default storage path in settings > storage will allow DiskDigger to scan the SD Card as the internal storage. It's sometimes helpful to reverse the default storage device between scans if you couldn't find the files you're looking for


text:
Adding a new account to my Samsung phone
I wanted to change account on my phone so I removed it from Accounts (it was the only google account on my device).
Now when I try to add a new account the Settings application is closes itself (force closes?). I've tried clearing the cache of all Google related apps and signing in to Google and Chrome apps.

There might be a third party app that's in your way. Therefore, try adding the account while in safe mode. Because while you're in safe mode, all third party apps are disable, so they can't make any trouble.
To go into safe mode, turn your phone off, and then turn it back on while holding down on the volume down button. When the phone turns on, it will say safe mode on the bottom left of your screen.
Now try adding the account while in safe mode. Go to settings → accounts → and account → Google....

Didn't work, the same happened.


text:
Can I use Droid Explorer to migrate my apps and app data from one device to another?
Examples:
Migrate from old Firestick (small one) to a new one?
Migrate from Note 4 to Note 8?
Or is ADEBAR or something like that a better solution?
If Droid Explorer is the solution can anyone point me at the steps? Not seeing anything after some searching - tho to be fair, this app came off a post in a StackExchange post.

This is the closest to migrate that you can do without additional apps. From what I know, use Android 6 and newer with a valid Google account where all Playstore apps are recorded. I have not tried on older than Android 6 for these to work.
Enable its Google backup and auto sync options. Activate all application that have a backup/restore, such as Whatsapp.
When you login to the new device, the contacts, wireless settings and those auto backup can be restored. The respective Android apps from Google Play Store are listed as Library in My apps & games. Select and install back the required games.


text:
Root Gone but still works for many Apps
I Have a Verizon Galaxy Nexus which was rooted. I used an OTA Rootkeeper to keep the root after I upgraded to 4.0.4 which worked great, I was able to use root well after the OTA update. But recently the root has stopped working however the apps that I had saved permission before the mysterious removal of root still work. So I can use Sixaxis, Wifi Tether, File Explorer with root permissions, etc. They all work great however any new app I download is unable to get root access. I first noticed it trying to flash a rom.
When I go into SU app says I have a outdated binary and when I try to update it (from 3.0.3) it fails to gain root access.
Any ideas why I've lost root access and how I can get it back short of going back through the entire root process?

What exactly do you mean when you say "root has stopped working"?  Are there any error messages?

No error messages. As I said in the post I had root on my phone that worked fine but recently something has changed which has caused it to break i.e. new apps I can install can't gain root access. But apps that previously had root permission still work.

Looks like problem with su program rather than root.

Having "root" just means you have a working su binary installed (the "su" application is generally just a management front-end for the linux-level binary installed in /system/bin or /system/xbin).  So, something has gone wrong with the binary, or the way its installed, or its permissions, or its location, or ...
I suspect the apps that still work must have chown'd themselves once at setup time?  So they only need su to work once, and after that they're good to go.
If you can connect an adb shell or run an Android Terminal (that was just the first play store search hit, I'm not endorsing that specific terminal), type "su" and see if you get a meaningful error.  You can use adb to copy a new su binary over, or just re-"root" the device.  See the FAQ questions here: http://androidsu.com/superuser/faq/


text:
Can't enable "Developer options" on Redmi devices
The official guide says:

On Android 4.1 and lower, the Developer options screen is available by default. On Android 4.2 and higher, you must enable this screen as follows:

Open the Settings app.
(Only on Android 8.0 or higher) Select System.
Scroll to the bottom and select About phone.
Scroll to the bottom and tap Build number 7 times.
Return to the previous screen to find Developer options near the bottom.

I'm using Android 8.1 and there's no "System" option, but there's "About phone" right on the first Settings screen. However, inside "About phone", there's no "Build number". My phone is a Redmi 6, did they change the Android interface, or Android 8.1 interface is different, or what?
]
]

It is not a big secret that the Xiaomi uses MIUI which is a heavily modified Android OS.
Just searching the net quickly gets you the result that on MIUI you have to tap the field MIUI Version 7 times.
Anyway you could have found out that yourself by just tapping all available fields 7 times...

MIUI is just one of the many different words around here. And yes, if this site didn't exist we all could try every possibility, every time a problem appears.

Try this one too:
Settings->About phone->Software info->Build number. Now tap it 7 times, then you will be in developer mode. Good luck!

Hi, is this answer about the Redmi/Xiaomi device? Since some brands customize their own Android, some settings are located differently based on their device models and Android version, so it'd be great to mention the device model and Android version. Thanks.


text:
MAM and Android: fingerprint option never shown
We're trying to configure Intune so that people with Android devices can access their corporate email through Outlook for Android. In the Access Requirements blade (dashboard > client apps- app protection policies > intune app protection - properties), we've activated PIN (including simple PINs) and fingerprint for accessing the apps.
Whenever a user tries to access the corporate email through Outlook, it's prompted to install the Intune app (company portal app) from the store. After doing that, the user is asked for a PIN after setting up the corporate email account in Outlook. After the specified timeout, the user will be asked for a PIN again. However, the app never allows the users to use fingerprints to unlock the app. It will only allow the user to enter the PIN.
The Intune portal seems to imply that I should be able to use a fingerprint (instead of a PIN) to access the mail, but we've tried it on a couple of Android Devices (OnePlus 3T and 5T) and the fingerprint option is never shown.
Any ideas on what's happening?
Thanks.

Have you read https://social.technet.microsoft.com/Forums/en-US/cd36899e-5bb3-41f6-9754-7d1833dfa4ec/fingerprint-instead-of-pin?forum=microsoftintuneprod?

Hello Robert. Yes I've tried following the docs for setting intine, but I'm surely missing something...

In order for it to work, you need to create a work profile and associate the fingerprint to that profile.


text:
How to insert 2 SIM cards on Ulefone Armor 9?
I have the Ulefone Armor 9. It states it has a Hybrid Dual SIM (Nano-SIM, dual stand-by). In the settings, it seems it says there are 2 slots for SIM cards. But for the life of me, I cannot figure out how to put in 2 SIM cards.
Opening the slot seems there's only a place for 1.

Has anyone seen this before? How is it supposed to work?

A hybrid dual SIM slot is a technology that offers both features of a SIM card and a MicroSD card.
The hybrid dual SIM slot also means the OEM provided just two spaces instead of the traditional three slots for dual SIM cards and a MicroSD card. In other words, either two SIM cards are used or one SIM card slot is sacrificed to serve the role of a MicroSD slot.
Simply put, you have two options:

Dual SIM (one micro/nano SIM + one micro/nano SIM)
One micro/nano SIM + MicroSD card

ah ok, thanks! How do I open the right hand side to put in the sim/sd?

To open the second slot, push the pin-like end of the tool that's supplied with the phone (or a needle or other small pin) into the tiny hole at the end of the secondary cover.


text:
After HR I get this error: com.google.process.gapps was interrupted
Lately I have had some problems with my Asus Zenpad 7, a strange message:

"Unfortunatly com.google.process.gapps was interrupted"

which doesn't stop appearing, my use of the tablet is now limited to what I can do in the miliseconds I have between messages.
I tried many things such as reinstalling Play Store and Google Services, cleaning cache and reactivating the download manager but nothing worked.
Therefore I decided to hard reset, in fact I clicked two options on the Restore Mode of Zenpad 7: Wipe Cache and Wipe Data/Factory Reset, but the messages keep appearing.
I have the tablet rooted using KingRoot, and it may be something I have done while playing with Play Store patches (don't know what, I was just seeing what Lucky Patcher had).
Any suggestions?

Tried flashing the firmware? I think something got corrupted flashing should solve this

You are welcom. :)

Well, sorry to the moderators if they have to do something but as I don't know how to finish this things when the answer is in the comments just to say I did like @esQmo_ said and flashed the firmware from asus page and everything ok.


text:
How Do I Stop Double Email Alerts?
On my Android 2.2 phone, I have the Gmail app and the regular Mail icon on the desktop GUI. Unfortunately when I get a message, I get two alerts, usually about 4 to 15 seconds apart from each other. How can I just get one alert that new mail has come in, not two?

I went into the Gmail app and turned off the alerts there under Settings, reached by the Menu key. That way, they both receive the mail, but only one sends the alert. Don't know why I didn't think of this before, thinking it was going to be much harder.

more generally, if you used multiple email clients to access the same email account, then you need to turn off notification for all except one of them.


text:
Encrypt Tablet in Android 3.1 hangs indefinitely
I've recently gotten an Asus EEE Pad Transformer (my first Android device) and I love it. I've updated it to 3.1 right away.
I tried to enable the "Encrypt tablet" option. After following the on-screen advice (fully loaded battery and having the charger attached), I entered the PIN and pushed the button.
And waited.
And waited.
And waited.
All the time the tablet showed the green "encrypting" droid full screen, but didn't show any progress meter or any other text (even the system bar was disabled).
After several hours there was no visible progress (the introduction screen mentioned that it can take "an hour or longer") and after a while I shut down and rebooted the tablet. Everything worked just as fine as before, but nothing was encrypted.
I've attempted this a few times now, but every time it showed the exact same result (i.e. none).
I've searched around and found several accounts of the same thing happening to other 3.0-users and not a single post saying "yes, tablet encryption worked just fine for me".
Can someone shed some light on this? Or at least post a "it worked for me, sorry"?
Note that this tablet is not rooted and I don't plan to do that (yet).

I recently updated my TF101 to Android 3.2 and will soon re-try the encryption. I'll post when I have more information.

It seems to be a general problem. I was trying this on my Asus Eee Pad with physical keyboard which actually allows to minimize the "encryption process" and go to settings. However checking running processes doesn't show any activity that would suggest that something is actually happening.


text:
After removing old system app and installing the new version, it forces close
I'm using a custom ROM of CyanogenMod 7 (Android 2.3.5) on ZTE Racer. The ROM came with some default system apps like Gmail, Google Translate, Youtube and Adobe Reader. The old version of these apps are kept in internal storage even if you update them, so to save space I uninstalled the updates and them removed them using Root Manager.
The problem is that when I installed the updated versions from Market, they force close during opening (I found out later that Google Translate force close only when trying to translate something).
I had backed up everything before uninstall, and I noticed that if I install the backed up version manually and then update it through Google Play, they work fine. Checking the storage space left, I can say that the old versions were this way deleted, so I suppose the result should be the same.
Since I did not notice that Google Translate wasn't working, I deleted the backed up apk file, so I can't put it to work again.
My question is: anyone knows why does this happen? And if so, how could I make the updated version of Google Translate to work now that I do not have the old default apk anymore?
Edit: I tried installed again to trace the exact error message and it is now working, though I have done anything explicitly.

Which device? Which system apps did you remove? I would recommend to delete parts of the gapps package, cause it could lead to the kind of problems.

First step would be to look at the Android log after a fc has happened.

Thanks for the link, I'll consider using that next time something crashes, though I remember seeing the details of the "report" and it was a NullPointerException. I have tried one last time to install it directly from Google Play and it's now working, I'm not sure why (I had already rebooted after uninstall it).

I cannot say for all apps you listed -- but for some, the following applies:
Some system apps (as e.g. the market/playstore app) have to be present in /system in order to work. For the Playstore app, the reason is: The permission to install other "packages" is only granted if one of the following two conditions is met:

it is signed with the same certificate as the system (ROM) itself -- which does NOT apply in your case, due to the custom ROM used
it is installed as "system app" (i.e. below /system) -- which did no longer apply in your case, since you uninstalled the app from there

Expecting the pre-conditions given, developers might have forgotten to include a check and implement appropriate exception handling -- which then may lead to the described force-close.
Similar constellations might apply to other apps/packages as well -- though I'm not sure what should make the Google Translate app so special (maybe it has some special hooks I missed).
You could try to find out by following Roxan's advice, to integrate the app as "system app" again using e.g. Titanium backup, and see if it still force-closes.

Instead of doing this manually, use Titanium Backup Pro.
It allows you to integrate updates to ROM for all system apps.
So after installing this, long press your desired app and choose the option integrate update.


text:
Is it possible to add home screens to a Sony Xperia?
I've an Xperia Mini/Pro. I would like to add another home screen. At the moment there are 5 different home screen. Is it possible to add more to the Xperia launcher  ?
I don't want to change launcher, i find Xperia stock launcher very ..comfortable with the function 'corners' .
Thanks

this might help:
http://forum.xda-developers.com/showthread.php?t=1138791
you would need to have your phone rooted for this hack. It is for Xperia Play, but would work on other Xperias, as I've done this before on my Xperia Arc S successfully.

Just swap your launcher.You can use go launcher


text:
How to install ClockworkMOD Recovery on Sony Xperia Neo V (MT11a)?
I have rooted my MT11a with UnlockRoot v2.4.2 and the "superuser" app has appeared. The tutorial said my phone should be requesting to upgrade 4.0.2.A.0.42 to another number ending in .62, but the Update Center says the phone is completely up to date. I should be getting the BusyBox after this update, but the update is not happening. Have I missed a step? The phone is working just fine. I downloaded the ROM Manager, and it is requesting to get "ClockworkMOD Recovery" in order to operate. All this I'm doing to get the cyanogen mod.

Which tutorial? Please provide a link.

Flow, the Neo V is "just" the Neo with a 5MP camera, I guess. I don't know if they differ much internally. I think I've successfully installed the CMOD Recovery, I'm trying to work things out now.

Oh, and I suggest you extend the scope of your question by asking "How can I install cyanogen mod on the Sony Xperia Neo V?"

I am aware that the V is just a striped down version. But when it comes to installing custom mods small (hardware) differences matter. But it seems that the V has a stable cyanogen mod release, so you should be fine. Feel free to answer your own question if you have successfully installed CM. It seems that the CM wiki has no page about installing CM on the Neo V, I am sure you would get some rep this way :). You can always join the chat and idle around looking for help.

Unfortunately Sony does not have a recovery partition as expected! Its a boot+recovery combined hence no real CWM per se and if it goes wrong that's the entire handset in unusable state, which generally makes things trickier to flash custom roms etc. The only work-around is to unlock the boot loader, root the handset, and then install a CWM apk which gets installed into /system directory and acts a pseudo recovery.

@t0mm13b Could you drop by the chat?

@PeterTamaroff as you finally managed to install CWM: Could you answer your own question, add your solution, and then accept the answer? Thanks!

I managed to install CWM, but not Cyanogen. I really don't have the time now.

Unlocking the bootloader is not required for CWM on the Neo V, you just need root.

Probably the easiest way is to use x-Parts (formerly known as CWM Installer).

Thanks for that! Is there any way to uninstall a recovery before installing another?

Break your phone and have it repaired, in general the technicians will thoroughly flash your phone :) So there must be one but I wasn't able to find it when I needed to.

Hehe, it seems however that the version X-parts installed was the same version I had. Now I'm backing up my device with CWR to see if I can install Cyanogen 9.0. Any things I should be careful with?

I think you are confusing your ROM version (4.0.2.A.0.42) with CWM's version. Doesn't matter if you want to replace your ROM by Cyanogenmod anyway :) Remember to put the zip on your SD card before flashing the Cyanogenmod kernel as it doesn't work with the stock ROM or vice versa. Also, Cyanogenmod 9.1 is already out.

How do I flash the "kernel"?

You will find a guide to the complete procedure here

Erik, one last thing. I accidentally made an extra backup which didn't even complete because my SD is full, how do I delete that backup, or any other previously done backup using CWR?

"Now reboot your phone and your phone should have updated to CyanogenMod 9.0 which runs over Ice Cream Sandwich!" I don't have Ice Cream Sandwich. What can I do?

let us continue this discussion in chat


text:
How do I recalibrate the battery of my phone?
After a year using my phone, I noticed the battery drains too fast, but after shutting down I manage to make it work again for a couple of minutes before it shuts down automatically.
I read that to recalibrate the battery, you should fully charge it and by various means  delete the batterystats.bin file. (examples with clockworkmod or using an app)
The thing is...

"When you follow the steps to recalibrate your battery and delete the batterystats.bin file from your phone, you are getting rid of more than what you think… Stored inside that batterystats.bin file, your phone keeps detailed logs of the capacity of your battery and uses it on how it can be utilized more efficiently." Read Full

or oppositely, quoting Dianne Hackborn

"It (refering batterystats.bin) has no impact on your battery life."

I know it's not possible to make it as good as new, but at least reset it in a way it would read that last bit of energy accurately?

Android shuts down your OS before it actually becomes completely flat, in order to ensure it has enough power to do so safely and completely (which is why you can power it back up again, but then it shuts itself off again).  Over time, your battery does need to be recalibrated as the system stats on battery usage get wonky and the battery itself won't store as much of a charge as it could.
For most phones, the proper procedure is:

Let the phone run until it shuts itself off.
Without turning the phone on, plug it in and let it fully charge up.
Unplug, turn the phone on and let it run flat again.
Battery and battery stats are now recalibrated.

Deleting batterystats.bin isn't generally necessary.
You should find your battery lasting much longer now (I know this works well on my Samsung SK4G - I go from not being able to last the day to being able to last a full day and night)
If memory serves, one is supposed to recalibrate one's battery like this every 30-90 days.

Logos would you quote some source?

Most phone manuals will have this somewhere, and there are tons of references if you google.  The steps vary somewhat between them, but the ones I outlined are the most important ones.  Here's a few:
http://mugen.tv/2012/06/lithium-ion-smartphone-batteries-how-often-to-calibrate-to-prolong-life/
http://www.batteryfaq.net/battery-tips/some-tips-to-tell-you-how-to-calibrate-smartphone-battery-1738.html
http://forum.xda-developers.com/showthread.php?t=1616598

Recalibrating your battery won't actually make it last longer. What it might do is ensure that the battery level display is more accurate, so that when it says it's at zero, it's actually at zero.
Personally, I used an app like Battery Calibration (requires root) and it seems to help. To be fair though, I haven't actually tested the actual levels myself, so it's a qualitative judgement.
If you're having battery life issues it's more likely that you apps running (background or otherwise) that are draining your battery. Either go to Settings > Battery and check out which apps are draining your battery the most - typically it will be your screen, then cell/wifi radios.
Sadly, the only true "reset" is to go out and buy yourself a new battery. Sorry!


text:
What does it mean to "brick" your phone?
I'm considering unlocking the bootloader on my Verizon Galaxy S3 (SCH-I535).  However, a guide I was reading made this statement:

Once you have unlocked your phone’s bootloader using this app, you must not receive any over-the-air (OTA) updates or via Samsung Kies. Doing so will result in bricking your phone.

I understand that bricking a phone means rendering it unusable, but does this also mean unrecoverable?  When a phone is "bricked", does that mean it is virtually impossible to restore it to a working state?
I'm a little concerned about the risk if that is the case.

Related: Bootloader/BIOS, flashing ROM and correlated risks. Why Android devices are more brickable than PCs?

The term "brick" usually refers to the stone, which means: "device can only be used as paper-weight". Taken literally, there's no way to "unbrick".

However, you also find terms like "hard-brick" and "soft-brick" used, which makes the term "brick" less absolute: A soft-brick is something you easily can recover from (count it as a "temporary paper-weight"), mostly by software-based solutions (e.g. re-flash your phone) -- while a "hard-brick" is rather meant in the way the original term points to.
Still, technically spoken, even a "hard-bricked" device could be "unbricked" -- but mostly this is more expensive then getting a new device.
As for the warranty declaration you quoted: For a normal user, it's almost impossible to (hard-) brick his device. Even when flashing a custom ROM, this can rarely happen, as there are many security-layers involved. Almost always you can boot your device into some fall-back mode where it is at least recognized by some "flashing software", so you could simply flash another/the original firmware back. Which means, the risk you are taking is to "soft-brick" your device1. A "hard-brick" is quite unlikely with "normal operations" like rooting or flashing custom ROMs.
See also:

Wikipedia: Brick
RootzWiki: Brick

1 I just learned: "Unless you've got a Samsung device and used the software recommended by Samsung". So better don't use Kies etc., but rather Odin, just to give an example.

Upvoted for the info. Wished I could upvote another time for the pic of the brick. :-D

Great answer.  @Sparx I upvoted for you on the brick.

Ultimate answer.. Ha..Ha..

My xperia c is not giving any response on pressing any combinations of keys. I  installed Z2 rom in it. After successful installation, it hasn't reboot. It is showing a response only when connected to charger or PC via usb cable and that is the display of a RED LIGHT and nothing else. Does it means it is hard bricked? Suggest me what to do..

@choxx if it were "hard bricked", it would show no response at all usually. For deeper insight and solving your issue, I however recommend asking a separate issue – and give a few more details (what you did that might have led to the issue). If it is detected by your PC, you could e.g. flash a different ROM (the ROM might be unfit for your device). You could also check whether it's possible to boot into recovery/bootloader/safe-mode (include results with your question then). // Ah, I see you've already done that :)

Brick is a much-hyped word that gets bandied about without understanding what it is.
There's two types of brick, hard and soft. Let's go through this to make the distinction clearer.

Hard - this is where the handset will absolutely refuse to boot at the press of the power button.
Diagnostics: Dead screen, no power. That is the symptom of a hard brick.
Reason: This can happen by inadvertently pulling the cable when flashing a ROM or even an update via the handset's supporting software such as Samsung Kies, Sony's PC Companion Suite etc. That is the worst case, that is why in this scenario, always, make, sure that no cable gets pulled unless told so by the supporting software in question. The other way is this, flashing in that manner when the battery power is low. Hence for that reason, it is recommended to have at least 75% of battery power in place prior to doing the update in that fashion. It's known as hard-brick, and requires specialist cables and stripping the device down to the circuitry board to revive it via JTAG cables.
Soft - this can happen through a bad flashing of the ROM in which yields the following.
Diagnostics: it has power when the power button is pressed, and/or, the screen comes on.
Reason: It can be a user error on this part. For example, failing to clear/wipe the data/cache, can cause Android to go into a bootloop because of the mismatches with the Android's virtual machine and the apps installed, or more than likely, a corrupted dalvik cache. The other, is flashing a ROM that is not designated for the handset which can cause the kernel to go into a bootloop. This is generally easier to fix, but hangs, that is known as a soft-brick.

With those two separate forms of brick, it is generally speaking, a scaremongering tactic.
The one pure simple reason why carriers do not recommend unlocking the boot-loader, is not just for the warranty. It's more down to the fact, if the handset ever gets stolen, then unlocking the bootloader will wipe everything, and reinitialize the handset to factory state, thereby all your contacts, call logs, messages and apps gets wiped cleanly. Also, this is to reduce the amount of support in the carriers, with people calling in or ringing up the technical support, "What happened with my handset - I did something and lost my contacts?"
Just to finish off this answer, you can revert it back, by relocking the bootloader at a later stage if you wish, that is in the event the hardware got damaged and hand it back in for repairs.

Great information, and I'm glad to hear that I can relock my bootloader if need be.

That said, you also can un-root (even easier as relock I'd say). But I doubt you'll ever feel like it -- unless in a case of warranty, of course :)

My xperia c is not giving any response on pressing any combinations of keys. I  installed Z2 rom in it. After successful installation, it hasn't reboot. It is showing a response only when connected to charger or PC via usb cable and that is the display of a RED LIGHT and nothing else. Does it means it is hard bricked?

@choxx oh dear, you flashed a Z2 rom ( for Sony Xperia Z2 ) on a Xperia C, that rom is not compatible right? You have checked and confirmed this? In any case, sounds like a soft brick, try reverting back, but this time, USE a specific rom designated for Xperia C in your case.


text:
Why can I not assign exec permissions to a file on the SD card?
shell@android:/sdcard/SW # ls -l
-rw-rw-r-- root     sdcard_rw      128 2012-09-22 11:42 usb0config.sh
shell@android:/sdcard/SW # chmod 777 usb0config.sh
shell@android:/sdcard/SW # ls -l
-rw-rw-r-- root     sdcard_rw      128 2012-09-22 11:42 usb0config.sh
shell@android:/sdcard/SW #

Why can I not assign exec permissions to a file on the SD card?
$ adb shell su -c mount |grep -si sdcard
/dev/block/vold/179:97 /mnt/ext_sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/ext_sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

$ adb shell su -c "mount -t vfat -o umask=0000 /dev/fuse /mnt/sdcard"
mount: Block device required

Now it seems remount successfully.
$ adb shell su -c "mount -t vfat -o remount,umask=0000 /dev/fuse /mnt/sdcard"

but the file yet cannot be assigned 777 mode.
shell@android:/sdcard/Sw # ls -l
-rw-rw-r-- root     sdcard_rw      128 2012-09-22 11:42 usb0config.sh
shell@android:/sdcard/Sw # chmod 777 usb0config.sh
shell@android:/sdcard/Sw # ls -l
-rw-rw-r-- root     sdcard_rw      128 2012-09-22 11:42 usb0config.sh

The mount info doesn't change comparing to before remount's.
$ adb shell su -c mount |grep -si sdcard
/dev/block/vold/179:97 /mnt/ext_sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/ext_sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/fuse /mnt/sdcard fuse rw,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Unless you've done something unusual with your device, the SD card will be formatted as a FAT file system, which does not support *nix file permissions. This Linux FAQ entry from one of MIT's professors explains it a bit, and also explains how you can potentially use mount options to change the permission mode of the device (this would require root, though, and affect all files/folders on the device). Also, the SD card in Android is mounted by default with the -noexec flag.
For the exec bit you'd probably want to remount with a umask of 0000, since the umask is essentially a binary NOT of the permissions you want (so umask 0000 says don't mask out any permissions, allow them all). Untested, but doing it temporarily would be something along the lines of:
mount -t vfat -o umask=0000 /dev/your/sdcard/device /mnt/sdcard

The mount point may need to be changed from /mnt/sdcard to something slightly different depending on your device. Again, though, I believe mount requires that you have root permissions for this.

I try remount using your gave command, but failed, please see supplement of my question.

please see my question's update.

@VictorS: It looks like you have both an internal and an external SD card. The internal one is not treated the same way, and I don't know if there's a way to get it re-mounted with the permissions you want. Alternatively, though, you could execute your script by invoking sh: sh usb0config.sh.


text:
INSTALL_FAILED_NO_MATCHING_ABIS on Android 9
I am trying to install an APK that contains armeabi-v7a native libraries, on an emulator with KVM enabled. When I try to install the APK on to the running device, I am facing this error: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]
As per https://developer.android.com/studio/releases/emulator#30-0-0, the error above shouldn't occur on Android 9 or 11

Android 11 system images
You can now create an AVD that runs Android 11 by selecting either of the available API level 30 system images:

x86: Includes both x86 and ARMv7 ABIs.
x86_64: Includes x86, x86_64, ARMv7 and ARM64 ABIs.

Support for ARM binaries on Android 9 and 11 system images
If you were previously unable to use the Android Emulator because your app depended on ARM binaries, you can now use the Android 9 x86 system image or any Android 11 system image to run your app – it is no longer necessary to download a specific system image to run ARM binaries. These Android 9 and Android 11 system images support ARM by default and provide dramatically improved performance when compared to those with full ARM emulation.

My environment is Ubuntu 18.04 (LTS).
Here are some of my setup commands:
tools https://dl.google.com/android/repository/commandlinetools-linux-6200805_latest.zip
sdkmanager --install "system-images;android-28;default;x86" "emulator" "platform-tools" "platforms;android-28" (at this step feel free to replace x86 with x86_64)
Note I have tried with google-apis/playstore services and it allows the installation but fails at runtime.
avdmanager create avd -n "x86" -k "system-images;android-28;default;x86" (same steps of replacement apply)
`emulator @x86 -no-boot-anim -noaudio -no-window -verbose -wipe-data -partition-size 1024 -qemu -enable-kvm
Is it something I'm missing? editing the build.prop file doesn't help.

Even though Google states that this works for the Android 9 and 10 images, as well from my experience, it works only for the Android 11 preview images.
I have tested this on Windows using the latest default x86 Google-enabled images shown in the emulator manager for Android 10 and 11. As test app, I used a Telegram armv7-only APK file from 2019:

Android-R - (Android 11 preview) Google Play Intel x86 Atom System Image (revision: 1)

Installation success, app start success

Android-29 (Android 10) - Google Play Intel x86 Atom System Image (revision: 8)

Installation failed INSTALL_FAILED_NO_MATCHING_ABIS

Therefore, my results contradict the Google description you quoted in your question. At the moment, only the preview x86 images of Android R seem to be capable of running armv7 apps.
Test environment: Windows 10 64-bit with Intel Haxm installed.

I'll try this, you don't specify a --channel option do you? Also Android-29 is Android 10 as per https://developer.android.com/studio/releases/platforms#9.0 or is that a typo? I couldn't see support for arm translation for api level 29 in their doc's. I am also assuming you have haxm enabled, just to know that potentially KVM is not causing the problem (I mean it should doc's state that it should be used along side with hardware acceleration)

@Anton Android-29 is not a typo. I have tested an image for 10 and the preview for 11. I don't use the command-line at all, just the avd manager. Latest Haxm is installed and enabled. But as Haxm is only for x86 the arm emulation should be done by the OS running in the emulator.

I am going to mark the answer as correct, but mine still doesn't work, it's because I am running headless emulator and it only supports up to api 27 (https://androidstudio.googleblog.com/2019/02/emulator-2818-canary.html)

The other answer is great, but I wanted to add a little more detail. The
comment about Android 9 or 11 is correct, but it depends on the APK.
If the APK is armeabi-v7a, then Android 9 (API 28) will work. Also the
emulator should be x86.
If the APK is arm64-v8a, then Android 11 (API 30) will work. Also the
emulator should be x86_64.
https://stackoverflow.com/questions/36414219/install-failed-no-matching-abis