# Question
Title: Nexus 5 full disk encryption stuck 12 hours in?
I have loved my Nexus 5 since it was released with KitKat, and last evening I decided to enable full disk encryption, which I expected might take around an hour or so. It's now about 12 hours in with no visible change. All I see are the Marshmallow four animated dots. I've never seen any progress display on encrypting the disk, and of course I'm trying to avoid rebooting the phone for fear that the disk will be a jumbled mess and I could either lose my data or even brick the phone.

What is the best course of action at this point, and possible consequences?

# Answer
Could it be that your device is rooted? If yes, google a bit, there are some tutorials which could help. In that case killing or deactivating SuperSU (or similar) could bring success.

Here is what sometimes seem to work (answer is from aikidork):

1. Install Busybox (I have Stericson version), RootExplorer file manager, a terminal Emulator (or enable USB debugging), and SuperSU (no promises about this working on other root managers!)
2. Set up a fingerprint lockscreen. Configure ALL your fingers you want to use ahead of time since this won't be configurable later!
3. Using Root Explorer, copy/backup the following files to external SD:

`/data/system/locksettings.db` ,

`/data/system/locksettings.db-shm` ,

`/data/system/locksettings.db-wal`
4. Kill all running apps.
5. Launch command prompt in ADB or Terminal Emulator.
6. Execute `su` so that your prompt changes from "$" to "#" (you are now root)
7. Kill the SuperSU daemon to temporarily disable root mode (lasts until reboot):

`pkill -KILL daemonsu`
8. Your root daemon will kick you out of privileged status during shutdown, changing "#" prompt back to "$" (root is temporarily disabled).
9. DO THIS STEP IMMEDIATELY without rebooting or launching more apps! Go to the default security screen and select Encrypt Device. Set up a password lock screen as required (8 digits with at least one number). Plug in to power if not using ADB. Confirm the encryption operation.
10. If everything is working well, you will see the encryption screen, a soft-reboot splash screen, and then a progress indicator counting up to 100%. If it moves beyond zero, congrats your encryption is working! Wait for this to finish.
11. Now, to restore the lock screen, unlock the phone and launch your Root Explorer again.
12. Restore the three files you backed up earlier to their exact locations, overwriting the replacement ones that the encryption setup created.
13. Wait for phone to lock (or reboot once more) and confirm that you can unlock the phone with fingerprint.

PS: I currently have the same problem but none of the mentioned solutions helped so far.

**UPDATE:** This seems to be a common issue when an app is still holding open files. However, there is no official way to determine which process is causing these issue so far and it is recommended to have a chat with the support.
> 1 votes

# Answer
Success! As with others I had to uninstall an app or two to get it to work. Logcat gave the info I needed with these lines:

`03-14 12:16:28.983 149 173 W Vold : Tearing down stale mount /mnt/asec/com.exozet.android.catan-1^M`

`03-14 12:16:29.002 149 173 W Vold : Tearing down stale mount /mnt/asec/ginlemon.flowerpro-1^M`

So I removed Settlers of Catan (fun game) and SmartLauncher Pro (googling told me that's what the second app is). After that everything went fine.

I suggest using a file browser to see what you have in /mnt/asec/ and removing those apps. For me those two apps were the only two things in that directory, so it may be that the bug is dealing with stuff in that directory. If so this is a way to identify the problem apps without running logCat. Good luck!
> 1 votes

# Answer
If you're rooted, the encryption process will hang while booting, before the encryption even starts. It's safe to restart your phone when this happens.

If you have a Nexus, unrooting is just a matter of reflashing stock `boot.img`. This doesn't delete your data or anything, it just replaces the boot partition modified by SuperSU with the default one, which is required by the encryption process.

Step by step guide:

* Download stock firmware for your phone here: https://developers.google.com/android/images
* Extract `boot.img`
* Turn off your phone, then turn it on by holding volume down + power button. This will get you into the bootloader interface.
* Connect USB, install drivers
* Run `fastboot flash boot boot.img` \- assuming fastboot and boot.img are in the same directory
* Reboot your phone
* You're un-rooted and the encryption should work now

Just tested this on a Nexus 5. After the encryption's finished, you can root your phone again.
> 1 votes

---
Tags: nexus-5, 6.0-marshmallow, disk-encryption
---


# Question
Title: How do I change the default share folder in dropbox?
When I want to upload files to dropbox from external apps (share button) I always get directed to the same dropbox folder. Even if I delete it, it will come back from the dead next time I share with dropbox.

Is there a way to choose a different folder to share with dropbox when using third party apps?

# Answer
> 1 votes
I think I had the same problem and it was very easy solving this. If you are in the "share" dialog just use the back button of your phone and you are back in the parent folder. Found the solution here. So I hope that also solves your problem!

---
Tags: dropbox
---


# Question
Title: My LG X Power volume keeps resetting to 2
I turn down my ringer to 0, with no vibrate. I leave it on my desk, and when I get a message, I hear the message ding. When I check, the volume is at 2 (i mean 2 levels higher than vibrate).

This is happening several times a day. What could be causing it?

I'm using Android 6.0.1

# Answer
> 0 votes
I figured it out.

It was the "Call Blocker" app from AndroidRock.

The problem went away after I uninstalled the app. To be sure, I reinstalled it, and the problem came back. I tried this about 3 or 4 times to confirm.

https://play.google.com/store/apps/details?id=com.androidrocker.callblocker&hl=en

---
Tags: 6.0-marshmallow, hardware, lg, volume
---


# Question
Title: How to use Microsoft Exchange ActiveSync to sync Hotmail and Outlook contacts to Android?
I have sync issues with Microsoft Exchange ActiveSync, when using its service with my Hotmail account. (I'm using a Samsung Galaxy Note 4 with Android 6.0.1, if that helps)

These are the steps I took to reproduce the issue,

1. Go to the settings page
2. Under the Personalization Section I select Accounts
3. Select Add Account
4. Select Microsoft Exchange ActiveSync
5. Entered my Email Address and Password
6. Select Next
7. Uncheck all the checkboxes except Sync Contacts.
8. Select Next
9. Name the Account and select Done

Now that I had setup the account, I took the following steps to test my contact sync

1. Create a new contact on the device using the contacts app and selecting the microsoft exchange activesync as the account and fill in a name and contact number.
2. Save the contact.
3. Go to outlook's webapp
4. log into the same microsoft account and create a contact.
5. Save the contact.

Finally I went to my phone and made sure sync was switched on and looked for the contact I had made using the outlook's webapp. I also looked on outlook's webapp for the contact created on the phone.

The final result:

* Sync from Outlook.com to android =\> WORKING

(The contact I created using the outlook.com web app was visible in both the web app and the phone)

* Sync from Android to Outlook =\> BROKEN

(The contact was only visible on the phone ie: missing from the outlook web app)

How can I fix the BROKEN Android to Outlook sync?

**\___________________________________________UPDATE\___________________________________________**

1. I haven't tried using another android phone, I don't have one lying around at the moment. I'll give it a shot when I can and let you know.
2. I do not sync my contacts with my google account, how is this possible? I am trying to sync my MS account contacts to my android phone. I wasn't aware of a connection between the MS account and my Google account contacts.
3. I've already tried syncing the emails, no luck. Issue still persists.

# Answer
> 0 votes
It turns out that Microsoft Does NOT Support 2 way sync between android devices and hotmail or windows live accounts.

I got in touch with the outlook customer service rep for android and they confirmed this.

I hope MS figures this one out sooner rather than later.

# Answer
> 0 votes
Have you tried connecting another Android phone? It would be a nice AB testing to see where's the problem.

The first answer that comes to mind is to check whether your contacts not set to sync with Google contacts. In some cases that prevents everything from working correctly.

Another solution is to enable syncing email alongside with syncing contacts. Some Android phones don't update other data correctly till emails syncing is turned off.

And the last option is switching to the software called Akruto to check if that could fix everything. You can find all instructions and video guide on the official website: http://www.akruto.com/best-ways-to-sync-android-with-microsoft-outlook/

Hope this helps!

# Answer
> 0 votes
So after a few weeks of trying to figure out the root cause of the issue, it turns out that Microsoft Exchange Active Sync only supports One Way sync for your windows live accounts to your Android devices.

This was confirmed by MS Customer Service once I installed the Outlook App for Android and had a chat about Sync Issues.

Apparently MS is working on fixing the Sync Issues and providing us with true two way Sync, but as of 29th of April 2017, this has not yet happened.

---
Tags: sync, exchange, outlook, active-sync, hotmail
---


title: fastboot not finding SPH-L720 on Linux

text:
# Question
Title: fastboot not finding SPH-L720 on Linux
This is with Ubuntu 13.10 on the host and a Sprint Samsung Galaxy S4 SPH-L720.

When in normal mode, 'adb devices' finds my phone.

I do 'adb reboot bootloader' to reboot my phone into bootloader mode.

'fastboot devices' comes back empty. 'sudo fastboot devices' also comes back empty.

I have setup the udev rules file accordingly (replaced my real login with myuser)

```
~  cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="myuser"

```

lsusb returns the following (fyi, the device is an S4, not an S2)

```
Bus 002 Device 006: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)

```

I've read a ton of articles on this and I can't get this working. Any help is appreciated. Thanks!

# Answer
> 1 votes
Accordingly to the answer to this question, Samsung devices do not support fastboot. This thread on XDA Forums states the same.

---
Tags: linux, samsung-galaxy-s-4, fastboot
---


# Question
Title: How to change the display name in the Google Play Store app?
In the Google Play Store app, the account name is shown inside the drawer menu.

How to change that name?

# Answer
There should be a pre-installed Android app in your phone called Play Games. Click that. You will see your username and your display pic. Click your username and then the top right edit icon of a pen. That way you can change your Google PlayStore username. Hope this helps :)
> 3 votes

# Answer
From Google help Edit your Google Account information

> You can edit information like your name, birthday, gender, and the email and phone number associated with your account. This basic information is used to help others get in touch with you more easily in products like Hangouts, Gmail, and Maps.
>
> * Sign in to My Account.
> * In the "Personal info & privacy" section, select Your personal info.
> * Choose the information you want to edit and follow the onscreen instructions.
> 2 votes

---
Tags: google-play-store
---


# Question
Title: App installed from apk, but not in app drawer and in settings
I have installed an app fusing its apk. After installation, I clicked on 'Done'. Then, I checked app on `app drawer` and `Settings->Apps`, it was not found there. I am running Nova launcher, in Lineage Os 14.1,Rooted, Xiaomi Redmi 1s. Earlier, in settings it showed 47 apps installed, now it shows 48 apps installed(including hidden app).

1. I have checked for app in /data/app, app not found.
2. Installed Quickshortcutmaker to create app shortcut, but app not found.
3. Tried to hide in Nova settings, app not found.
4. Tried to reinstall that apk, it overwrites app like an update.

I need to uninstall this app.

The app is PixBar (installed apk), In file name like this `com_dunrite_pixbar-10011002.apk.apk`. And while opening through es (for install), it showed package as `net.upper.master.support.texas.stem.threw`, which is found as malware(google). I try some apps like this(install from apk), but, this have no option to uninstall, which I have never experienced before.

# Answer
Seems like a spying apps which can install in stealth mode and never being detected.

Try with ADB commands to check if it appears in the list of installed apps and eventually delete it.

1. Download Minimal ADB and fastboot. Unzip and run it. (Windows machines)
2. On the phone, enable USB debugging in Settings \> Developer Options \> USB Debugging. If the Developer Options is not present: Go to Settings \> About then hit 7 times on Build number then go back to Settings.
3. Depending on your phone, you'll need drivers for your device to be detected (Windows).
4. Connect the phone to the computer. On the terminal window, type `adb devices` \[press enter\] this checks if the phone is detected. Output : `xxxxxxx devices`
5. Type `adb shell` \[press enter\]
6. Type `pm list packages -f` \[press enter\]. A long list of apps with their packages name will output, just check if your app is listed.
7. Then to delete the app, type `cd /system/app` \[press enter\] or `cd /system/priv-app` \[press enter\] depending on the app location and then type `rm app_name.apk` \[press enter\] (app names are case sensitive).

Note: *An alternative for Minimal ADB and fastboot which is available for Linux, Mac and Windows as well, can be found in the answers on Is there a minimal installation of ADB?.*

Since you are using Nova Launcher, I remember you can hide apps. Check if you didn't do so inadvertently.

* Go to Nova's Settings menu, by either long-pressing on the home screen and selecting the “Settings” icon in the bottom right, or heading into the app drawer and tapping the “Nova Settings” icon.
* Open the second entry **App & widget drawers**
* In the **Drawer groups** section, select the \**Hide apps\* option.
* Then check if the app appears there and eventually uncheck the check mark.
> 1 votes

---
Tags: applications, lineageos, 7.1-nougat, nova-launcher, redmi-1s
---


# Question
Title: Turn on USB debugging using command-line
I have a Samsung Galaxy S2 and a PC running Debian 8. How can I turn on USB debugging using command-line on my PC without touching the phone?

# Answer
**If the question is simply "using the command-line"**

Let it be ~~simple~~ (root possibly\[1\] required):

```
settings put global development_settings_enabled 1
settings put global adb_enabled 1

```

And then you need to

```
echo "mtp,adb" > /data/property/persist.sys.usb.config

```

**If you want to do this *without touching your phone***

Then I'm feeling interesting because in most cases you won't gain access to command line via PC before enabling ADB, so it's impossible to enable this prior to touching your phone.

It is in any case possible but made extremely difficult. Please also bear in mind that if your bootloader hasn't been unlocked yet, unlocking it will **wipe all data** on your phone, making this alternate way mostly useless except for rescuing a brick.

---

1. Actually you only need either 'system' or 'shell' privilege, but 'system' is impossible to access without rooting and 'shell' is granted only if you're already logging in via adb, where it makes no sense to enable adb while it's already active.
> 11 votes

---
Tags: usb-debugging, command-line
---


# Question
Title: HARD BRICKED AFTER INSTALLING 4.4.4 UPDATE IN MOTO E 1st gen
When I updated my mobile, it power offed then it gone to bootloader mode then I pressed on normal power, but it didn't, so I press on recover, it gone to TWRP mode and I pressed on recover, there some codes happened, and then it gone off. till then nothing working.

not even charging, and not opening bootloader too.

pls I need your suggestion. THANK YOU

This video on Youtube (published March 2015) is showing same problem that I have. You can see in the comments that still this problem is going on.

see article about Easy JTAG on internet. you can understand how this begin and end.

# Answer
> 0 votes
There are really only 4 viable solutions for a hard bricked Moto "letter" device, assuming this is truly hard bricked and not a battery or charging issue. Being hard bricked on one of these devices means that the bootloader is inaccessible and the device doesn't boot, if the bootloader is inaccessible we have few options remaining for self-repair.

**Qualcomm HS-USB Qloader 9008** \- All Qualcomm devices have the ability to be hard flashed *with the proper files*. Although this is an option for many devices, it is not for these devices because Moto/Lenovo will not release the necessary files. Thus this is not a valid option for these devices, I only bring this up because searching the internet will return many references to this tool, but we cannot use it thanks to Moto/Lenovo policy on these devices. - Source

**JTAG programming** \- Requires an external device and ROM files, assuming the partitioning is still intact this is a viable option although for lower end or older devices, the price of the programmer is often significantly more than the value or replacement cost of the device, with modest units costing around $200USD (source) without the necessary cables which sometimes need to be purchased separately or fabricated, and the initial cost of this device when new was $100USD and it's current value is around $30USD, most likely makes this option undesirable.

**Authorized Service Center** \- Have the device repaired by an authorized Moto service center. Due to the age of this device, it is likely out of warranty and the cost will likely be more than the device's value or replacement cost. I have no reference for this information, so it might be worth your time to investigate it yourself, if this was the result of an official OTA update, it may be possible to find a sympathetic ear at a local authorized repair center.

So this brings us to the **Final Option**... As noted in some of my previous options, the cost/value of the device needs to be considered here. The Moto E is a low-end, low cost device and was released in May 2014, just over 3 years ago. This device has very little value and a replacement unit would likely cost less than any valid repair option, so it may just be time to discard/recycle the device and purchase a new or used replacement device.

Like many things in life, not everything can be feasibly or economically repaired, sometimes you just have to accept that and move on.

# Answer
> 0 votes
Rolling back to old os may be difficult. So you can try custom os. But if you need stock rom back try fastboot rom. Check whether fastboot rom is available for you. You may want to use tool to do that

# Answer
> 0 votes
Just something before my answer : *softbrick* is when you still CAN boot into recovery functions of the phone (`fastboot` or `recovery`) or still see some logo appearing on your screen at plug / bootup state ;

While *hardbrick* is when everything went wrong and you destroyed a reserved system / bootloader space that you weren't supposed to touch anyway, so your phone can no longer access anything.

Supposing, from your answer that you are ***hardbricked***, if nothing shows upw , well... Your phone is pretty much stuck in this state...

It is a good idea to ask a reseller or the manufacturer for a repair; but sometimes this involves a **full** motherboard change because you touched some DRMs or OEM stuff needed for boot.

---
Tags: boot, bootloader, reboot
---


# Question
Title: Can't switch off functionality do not disturb
I've activated the functionality do not disturb for 6 hours for my phone, so all the sounds were turned off. Then I switched off my phone while thr functionality was still on without switching it off. When i open it up again I found that do not disturb it's still on, i can't deactivate or activate it, the volumes seekbars look like when they are switched off by the functionality, but i can hear sounds, and I can't move the volumes level, apart from the multimedia one

# Answer
You need to create an avent of some minutes, that starts and stops the do not disturb, after that everything will be ok
> 0 votes

---
Tags: 6.0-marshmallow, nexus-5, volume-control, do-not-disturb
---


# Question
Title: Sound via Bluetooth shuts off during quiet
We have a Samsung Galaxy Tab 4 10.1, running Android 5.1.1 (U.S. Cellular, if it matters). We're connecting it to a Sony HT-CT80 Soundbar via Bluetooth.

While this works perfectly most of the time, during some shows that feature extended periods of quiet (such as Law & Order SVU, when there's an extended pause in the conversation, of about 5 seconds or so), the speaker appears to disconnect, in that the speaker is completely silent. When sound returns on the show we'll miss less than a second of the sound before the speaker starts back up. We've also had it do this while listening to the radio (WPR - Wisconsin Public Radio - via their Android app).

The tablet is connected via USB and fully charged, with the screen on the entire time. The soundbar is plugged in and doesn't lose power.

We've tried checking the bluetooth settings but don't see anything obvious, and suggestions online suggested that keeping the screen on might help with keeping the bluetooth connected, but as noted above the screen is definitely staying on.

Are we missing a setting that might explain why the tablet appears to be temporarily disconnecting during periods of quiet?

# Answer
It's the "feature" of the soundbar called "Auto Standby" -- it shuts down the audio amplifier when there is no audio to play, and then it needs some time in order to turn the amplifier back on when it detects that audio has returned. Unfortunately, it does that even when connected to power source (to reduce power consumption). I've checked the manual (https://docs.sony.com/release/HTCT80\_EN\_ES\_FR.pdf), and it seem that on your model it isn't possible to turn auto standby off.

The only workaround is to prevent the soundbar from going into standby by periodically playing sound on it, but that will be very annoying, since it must be a real sound, not silence.
> 0 votes

---
Tags: bluetooth-audio
---


# Question
Title: Does the space used by app increase on updating?
I'm working on Samsung Galaxy On7, Android 6.0-Marshmallow. Many apps like MS excel and word comes inbuilt, so I cannot move them to sd card, and they are taking up huge space on the phone memory.

Now, b other of these apps have released updates of size about 50MB. The mobile data is not a problem, but will the size of the app increase if I update it? If it increases, then I cannot install the updates.

I tried contacting the app developers but got no response from their side. So, it'll be very helpful to me if anyone knowing this can explain the bit.

N.B.: I don't have a rooted phone, and nor do I want to root it, and thereafter use apps like Link2SD.

# Answer
> 3 votes
If you are asking about the apps that came pre-installed with your device: Yes, their updates definitely will consume additional space, for a simple reason: The pre-installed apps are stored on the `/system` partition, which is read-only during normal operations¹ – so the update cannot be written there. Instead, it goes to the user `/data` partition. So with an update applied, there are always 2 copies of the app on your device.

You can easily tell affected apps when going to *Settings › Apps* and checking their entry. If it shows a button labeled "uninstall updates", that's a clear indicator.

All you can do in such cases is "disabling" the app – that is, if you don't use it anyway. Disabled apps are not updated, and already installed updates will be removed when disabling them. If at a later point you decide to enable them again, updates will be applied again as well.

---

¹ That usually means: always, except when applying system updates

---
Tags: applications, updates, internal-storage
---


# Question
Title: What is the easiest way to record gameplay on android?
I have a Moto g3. Is it possible to record android gameplay in the same way fraps records pc gameplay?

# Answer
> 3 votes
Play Games provide a way to record gameplays. You can capture your gameplay in 720p or 480p, and choose to add video of yourself and commentary via your device's front facing camera and microphone.

**Steps**:

* Open the Play Games app.
* Select a game to open the game details page.
* At the top of the game details page, touch the record icon.
* Select your desired video quality setting. You can record in 480p SD or 720p HD.
* Based on your device's available storage space, you'll be shown the maximum video length that you can record.
* Touch Launch to start your game. You'll see a floating video bubble appear with recording settings.
* Touch the record icon.
* After a 3-second countdown, your recording will begin.

Notes: *To stop recording: Touch the floating video bubble, then the red stop icon Stop icon. To dismiss recording: Drag the floating video bubble into the center of the screen. Drop the video bubble over the "X" to dismiss your recording. Once you are finished recording, the video will save to your phone or tablet. You will also see an option to share your video online.*

Source: Google support

---
Tags: motorola-moto-g3
---


title: Nexus 5X in setup wizard mode

text:
# Question
Title: Nexus 5X in setup wizard mode
I was developping an Android app on my stock 7.1.2 nexus 5X and next thing you know, the bottom buttons are not working anymore and I can't open the notification tray. I can't access developer options because "they are not enabled on this user", and user settings are not working (when I click on it nothing happens).

I saw online that it was related to some corruption somewhere, and that the phone was in "setup wizard" mode. The easy solution is to open the wizard back or reset the configuration using adb, but I'm facing a security exception because the `SetupWizardActivity` is not exported... I also tried the Nova Launcher trick but same security issue there. I finally wiped the cache partition, with no success.

Here is the command I tried and its output :

```
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity

Starting: Intent { cmp=com.google.android.setupwizard/.SetupWizardTestActivity }
java.lang.SecurityException: Permission Denial: starting Intent { flg=0x10000000 cmp=com.google.android.setupwizard/.SetupWizardTestActivity } from null (pid=9864, uid=2000) not exported from uid 10026
    at android.os.Parcel.readException(Parcel.java:1684)
    at android.os.Parcel.readException(Parcel.java:1637)
    at android.app.ActivityManagerProxy.startActivityAsUser(ActivityManagerNative.java:3137)
    at com.android.commands.am.Am.runStart(Am.java:643)
    at com.android.commands.am.Am.onRun(Am.java:394)
    at com.android.internal.os.BaseCommand.run(BaseCommand.java:51)
    at com.android.commands.am.Am.main(Am.java:124)
    at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
    at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:262)

```

Do any of you have a solution ? I would really like to not factory reset the device :(

# Answer
> 0 votes
I ended up factory resetting the phone. It looks like there is no solution to resolve this issue if it has not been rooted beforehand, or at least the bootloader unlocked. You can't even unlock the bootloader since developer options are not accessible when the phone is bugging like this.

---
Tags: adb, setup-wizard
---


title: GT-i9195I not recognized by USB

text:
# Question
Title: GT-i9195I not recognized by USB
I was not able to boot into system and thought it was a good idea to format the sdcard and flash a new firmaware. Unfortunately I can't find a working rom. So I decided to Flash stock rom or update twrp (hoping this will fix my flash problem).

When plugin my phone to my pc it will be recognized fine (when in TWRP) by adb. But when I boot into bootloader nothing happens.
Linux and Windows do not even recognize that there is a device plugged in. I tried several Drivers on Windows. On Linux I did nothing because I do not get the vendors ID form fastboot (because the device is not recogniced by the pc).
I tried several cables and different PCs. But I don't get it working.

Because of formatting the sdcard and not be able to boot into system I can't enable USB Debugging.

If you need more information please ask.
I am glad about every help / hint I can get.

Thank you very much and Kind regards
j0chn

# Answer
Samsung devices don't have fastboot, except for Samsung Nexus devices. What you call fastboot is Download mode in which no fastboot commands is recognized.

I think the computer is detecting the device but not as a fastboot device. On Windows, go to the Device Manager, you should see `Samsung Mobile USB modem` which is used as flashing interface. No USB Debugging needed here.

Flashing stock firmware on Samsung devices is easy. Just download the firmware and the flasher (Odin for Windows or Heimdall for Mac).
> 0 votes

---
Tags: adb, rom-flashing, fastboot, twrp
---


# Question
Title: How remove blank white screen after unlocking
I am using ASUS Z010D Android Smartphone. Recently it shows a white blank screen after unlocking. I need to touch the back button to return the home screen. Anybody knows how to remove the white screen please telling the instructions.

======= UPDATED =======

My mobile has been infected malware, ads so that the white blank screen is always shown at the time of sliding to unlock the phone. I have tried to reset it several times but it could not be recovered. Actually, we need to go through several steps to setup our phone if we choose to refactor it. But the ads still exists even if I do not finish the setup process. I guess the root has been infected malware/ads as well.

=======================

Thanks for taking your time to read the message.

# Answer
> 1 votes
I have had your same problem these days, my mom's phone (your same model) was full with pop ups ad. This kind of problem are caused by spyware/malware apps. I did a hard reset, but nothing.

I looked in the preinstalled apps (*Settings* -\> *Apps* -\> *ALL*) for something strange. I found two *Download Manager* apps. I disinstalled the one without the icon. This resolved all my issues. Hope can help you because for me was really annoying.

# Answer
> 0 votes
i had this issue, and just solved it, i think. I'm on Galaxy S7 Edge. First I went to settings and went to applications, then noticed a strange app with a blank icon, i couldn't unninstall it nor force stop it. Then went to some forums like this one and foind that it may be a malware. Went to play store and downloaded Malwarebytes, ran the scan, and found 1 malware, that one with the blank icon, then i realized that i didn't need the Malwarebytes, just search for administr... on setting, to find 'Device administrators', i noticed that the blank app was a admin, that's why i couldn't unninstall it. Thats it!

# Answer
> 0 votes
Just go to settings - apps - and see the first app without any name and a blank icon .. uninstall it ..problem solved

---
Tags: lock-screens, malware, ads
---


# Question
Title: Samsung S6 keep showing Device Security "1 threat detected"
I have found the App "androidlost" to be very useful in order to be able to found my lost phone ...

But on my Samsung S6, I keep getting Device Security "1 threat detected" regarding this App and they tell me to remove it. Please how can I remove this notification because I want to keep this App.

References:

Lost Android at google play

https://www.androidlost.com

# Answer
> 0 votes
There is a workaround provided at XDA forums which involves disabling the security log agent. I believe it is also the cause for the "Threat detected" alert notification.

1. Install free Package Disabler from Google Play Store.
2. Launch this app, search and disable "Security Log Agent".

Doesn't need root :)

This should fix this annoying notification again.

Reference

1. Unauthorized actions have been detected. error

---
Tags: security, lost-phone
---


# Question
Title: Unable to flash stock ROM of Moto X Dev edition
I have a Motorola X 2013 Dev edition unlocked (XT1053) that I'm trying to flash the stock firmware onto after using Cyanogenmod12. However, the process is failing. Following Motorola's instructions...

> After downloading the image for your device:
>
> 1. Make sure you have a Moto Pure Edition or a Developer Edition device.
> 2. Make sure you download the corresponding recovery image from the above portal.
> 3. To flash, put the phone in fastboot mode:
>
> 1. Power OFF your device
>     2. Then Power ON + Volume Down
>
> Alternatively, you can reboot into fastboot mode if you have adb...`adb reboot bootloader`.
> 4. Next flash the images using fastboot:
>
> ```
> $ fastboot flash partition gpt.bin
> $ fastboot
> $ flash motoboot motoboot.img
> $ fastboot reboot-bootloader
> $ fastboot flash logo logo.bin
> $ fastboot flash boot boot.img
> $ fastboot flash recovery recovery.img
> $ fastboot flash system system.img
> $ fastboot flash modem NON-HLOS.bin
> $ fastboot erase modemst1
> $ fastboot erase modemst2
> $ fastboot flash fsg fsg.mbn
> $ fastboot reboot
>
> ```
>
> You also have the option to erase all the data on your device with
>
> ```
> $ fastboot erase
> $ fastboot erase cache
>
> ```
> 5. After performing this sequence, you can relock your device with
>
> ```
> $ fastboot oem lock
>
> ```

When I try to flash gpt.bin, the following error appears on my phone

```
downgraded security version
update gpt_main version failed
preflash validation failed for GPT

```

Now I've looked into this quite a bit and found that it is caused by Motorola's own security protections. The only thing I can find to get around it is waiting for the new security patches. However, those threads I find are pre dropped support. Cyanogenmod is probably responsible for this since it is still getting security patches. Therefore, there never will be an updated stock to flash.

How do I get around this issue? I have a nandroid backup of the phone pre-Cyanogen, but I'd rather just flash a clean stock than use the backup if possible.

# Answer
> 0 votes
I've been in a similar situation with the XT1052 model, I don't know if the script below will work for you.

Boot in fastboot, either manually or through ADB. Then type:

```
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear

```

---
Tags: rom-flashing, fastboot, moto-x
---


# Question
Title: How to import an OBF map file into OsmAnd?
The map file provided by OsmAnd for a particular region has inaccuracies, so I would like to use this fixed OBF file instead.

How to do that?

Below is the procedure described on the website providing the fixed map, unfortunately it did not seem to work (when viewing the whole country the regions downloaded within OsmAnd (official OBF files) are highlighted in green, but the non-official region does not show in green).

> First, uninstall any standard OsmAnd maps of the region, because they will conflict with your custom map.
>
> Copy the map file to the Android device. If you have downloaded the map file from this site, be sure to unzip it first.
>
> For example, use a network-capable file manager, such as ES File Explorer.
>
> Put the map into the osmand data folder (you can check which it is under Settings → General → Misc → Data folder )
>
> It seems that the map needs to be renamed once within OsmAnd's Map manager (Map management → Local → Select your file → Rename) before it is actually recognized by OsmAnd.
>
> Afterwards, don't forget that you have to change the description language (Configure map → Description language) to English to see the transliterated place names.
>
> Also, as the base world map has not been created using JapanMapTranslate, you will need to zoom in a bit so that your local map is actually used.

Note: Unlike my other question How to import a .obf POI file in OsmAnd this question is about maps, not POIs. Answers at that question do not solve the problem here.

# Answer
To view OBFs that I didn't download through OsmAnd, I first had to change the directory where its data is stored to one where I can push stuff (non-rooted phone).

For that, I first went to Settings \> General settings \> \[Miscellaneous\] Data storage folder and switched it to "Manually specified...". I decided it would be `/storage/emulated/0/osmand` as this is a place I can see when connecting the phone to my laptop. OsmAnd asked whether it should move all its config files there, I said sure, go ahead.

I put the OBFs directly at the root of `/storage/emulated/0/osmand`. It lost all the maps I had downloaded through the app after the folder change, so I had to download the world map again, for example, and it ended up at the root of the folder too, that's how I figured it out.

It may take an OsmAnd kill and restart for it to detect new maps, and the trick above of renaming the file through the map manager indeed made it be inspected by OsmAnd and marked in green as a region for which a detailed map was available. Even before the renaming, its content would still be used though, so as soon as you see something corresponding to your OBF in the map manager, everything should be OK.
> 2 votes

---
Tags: maps, offline-map, osmand
---


# Question
Title: Where are the Game save files located in PC?
I have installed Bluestack on my PC and I began by installing a game called Townsmen and I played nicely. However, I want to backup the files that are created by the Bluestack program since I regularly restore my PC due to it get infected with Adwares and Malwares. I do not want to start the game again from scratch.

I know the default location for the installation is `C:\Program Files\BlueStacks` in Windows XP and some of the settings are stored in `C:\Documents and Settings\All Users\Application Data`. But I can't find that particular file with the name Townsmen.

Where & how can I access them from the PC?

# Answer
You can do that manually from the Bluestack app player by doing the following

**1 - Backup the game saves :**

* Download ES File Explorer from the app store/Play Store
* Open ES File Explorer and go to the Root Folder (click on **"/"** in the navigation bar)
* Go to `/data` folder, and then open the folder `/data` inside it (final path: `/data/data`)
* Now you can see a lot of folders name like `com.android.something` or `com.something.somethingelse`. Scroll down and look for a folder named `com.hg.townsmen6`. Long press on it and then click on the three dots (on the bottom right corner of the screen) and choose **Copy to**.
* After clicking **OK**, you will get a toast notification that the copy went successful.
* Now go back to your desktop (Windows desktop) and go to this path `C:\ProgramData\BlueStacks\UserData\SharedFolder`, you will find your folder there. Save it somewhere safe.

**2 - Restore the game's progress after a fresh install do the following :**

* When fresh installing, use this tutorial to get a prerooted Bluestack application Latest Bluestacks 0.9.14.4604 With SuperUser March 2015
* Install the app Townsmen from the app store along with the ES Explorer app (do not open the app Townsmen before finishing the next step.
* Copy back the folder we backed up earlier in the `/data/data` folder
* Now open your game and enjoy.
> 7 votes

# Answer
All Android files (including game saves) are located inside VDI files (VirtualBox drive image) at `C:\ProgramData\BlueStacks\UserData\SharedFolder`. You can try to convert them into image which can be mounted, but on Windows it's easier to install Total Commander app with FTP or SCP plugin, then transfer the game save files via network. Alternatively backup them via the cloud.

See also:
> 0 votes

---
Tags: sd-card, files, bluestacks
---


title: Undo failed encryption?

text:
# Question
Title: Undo failed encryption?
I am on Android 6 (AOKP), TWRP installed, and Xposed/Xprivacy. I wanted to encrypt the device from the settings dialog but apparently that failed - it just sits there with the boot animation doing nothing.

I can adb shell into it, logcat says:

```
06-03 03:58:47.076 E/BootAnimation(22199): couldn't find audio_conf.txt
06-03 03:58:51.208 W/vold    (  260): type=1400 audit(0.0:9568213): avc: denied { read } for name="fd" dev="proc" ino=3926686 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
06-03 03:58:51.208 W/vold    (  260): type=1400 audit(0.0:9568214): avc: denied { getattr } for path="/proc/248/cwd" dev="proc" ino=3926688 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:58:51.208 W/vold    (  260): type=1400 audit(0.0:9568215): avc: denied { getattr } for path="/proc/248/root" dev="proc" ino=3926689 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:58:51.208 W/vold    (  260): type=1400 audit(0.0:9568216): avc: denied { getattr } for path="/proc/248/exe" dev="proc" ino=3926690 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:59:11.618 W/vold    (  260): type=1400 audit(0.0:9568217): avc: denied { read } for name="fd" dev="proc" ino=3926686 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
06-03 03:59:11.622 W/vold    (  260): type=1400 audit(0.0:9568218): avc: denied { getattr } for path="/proc/248/cwd" dev="proc" ino=3926688 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:59:11.622 W/vold    (  260): type=1400 audit(0.0:9568219): avc: denied { getattr } for path="/proc/248/root" dev="proc" ino=3926689 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:59:11.622 W/vold    (  260): type=1400 audit(0.0:9568220): avc: denied { getattr } for path="/proc/248/exe" dev="proc" ino=3926690 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:59:11.679 E/Cryptfs (  249): unmounting /data failed: Device or resource busy
06-03 03:59:11.698 W/vold    (  260): type=1400 audit(0.0:9568221): avc: denied { read } for name="fd" dev="proc" ino=3926686 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
06-03 03:59:11.698 W/vold    (  260): type=1400 audit(0.0:9568222): avc: denied { getattr } for path="/proc/248/cwd" dev="proc" ino=3926688 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:59:11.698 W/vold    (  260): type=1400 audit(0.0:9568223): avc: denied { getattr } for path="/proc/248/root" dev="proc" ino=3926689 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:59:11.698 W/vold    (  260): type=1400 audit(0.0:9568224): avc: denied { getattr } for path="/proc/248/exe" dev="proc" ino=3926690 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:59:11.752 W/vold    (  260): type=1400 audit(0.0:9568225): avc: granted { read write } for name="mmcblk0p32" dev="tmpfs" ino=9999 scontext=u:r:vold:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file
06-03 03:59:11.752 W/vold    (  260): type=1400 audit(0.0:9568226): avc: granted { read write open } for name="mmcblk0p32" dev="tmpfs" ino=9999 scontext=u:r:vold:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file
06-03 03:59:11.752 W/vold    (  260): type=1400 audit(0.0:9568227): avc: granted { getattr } for path="/dev/block/mmcblk0p32" dev="tmpfs" ino=9999 scontext=u:r:vold:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file
06-03 03:59:11.832 W/vold    (  260): type=1400 audit(0.0:9568228): avc: granted { read } for name="mmcblk0p47" dev="tmpfs" ino=10059 scontext=u:r:vold:s0 tcontext=u:object_r:userdata_block_device:s0 tclass=blk_file
06-03 03:59:11.832 W/vold    (  260): type=1400 audit(0.0:9568229): avc: granted { read open } for name="mmcblk0p47" dev="tmpfs" ino=10059 scontext=u:r:vold:s0 tcontext=u:object_r:userdata_block_device:s0 tclass=blk_file
06-03 03:59:11.832 W/vold    (  260): type=1400 audit(0.0:9568230): avc: granted { ioctl } for path="/dev/block/mmcblk0p47" dev="tmpfs" ino=10059 ioctlcmd=1260 scontext=u:r:vold:s0 tcontext=u:object_r:userdata_block_device:s0 tclass=blk_file
06-03 03:59:11.835 E/Cryptfs (  249): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/extra
06-03 03:59:11.841 D/Cryptfs (  249): Just asked init to shut down class main
06-03 03:59:11.841 W/vold    (  249): emulated unmount requires state mounted
06-03 03:59:11.841 W/vold    (  249): public:179_129 unmount requires state mounted
06-03 03:59:31.935 W/vold    (  260): type=1400 audit(0.0:9568231): avc: denied { read } for name="fd" dev="proc" ino=3926686 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=dir permissive=0
06-03 03:59:31.935 W/vold    (  260): type=1400 audit(0.0:9568232): avc: denied { getattr } for path="/proc/248/cwd" dev="proc" ino=3926688 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:59:31.935 W/vold    (  260): type=1400 audit(0.0:9568233): avc: denied { getattr } for path="/proc/248/root" dev="proc" ino=3926689 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:59:31.935 W/vold    (  260): type=1400 audit(0.0:9568234): avc: denied { getattr } for path="/proc/248/exe" dev="proc" ino=3926690 scontext=u:r:vold:s0 tcontext=u:r:logd:s0 tclass=lnk_file permissive=0
06-03 03:59:32.007 E/Cryptfs (  249): unmounting /data failed: Device or resource busy
06-03 03:59:32.007 W/SocketClient(  249): write error (Broken pipe)
06-03 03:59:32.007 W/SocketClient(  249): Unable to send msg '200 8 -1'

```

Now, is it possible to undo the beginning of the encryption, since apparently no sectors were encrypted yet? Maybe I could somehow overwrite the luks header, restore the original one, or maybe the key (if there is one) is still in memory? I do have a TWRP backup from maybe 2 months ago.

I cannot `su` anymore, so that may be a problem.... it just hangs. But I am afraid that if I reboot, every last chance of recovery will be gone.

mount says:

```
rootfs on / type rootfs (ro,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /sys/fs/cgroup type tmpfs (rw,seclabel,relatime,mode=750,gid=1000)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /sys/fs/cgroup/bfqio type cgroup (rw,relatime,bfqio)
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (ro,seclabel,noatime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/radio on /firmware/radio type vfat (ro,context=u:object_r:firmware_file:s0,noatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/platform/msm_sdcc.1/by-name/adsp on /firmware/adsp type vfat (ro,context=u:object_r:firmware_file:s0,noatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
/dev/block/loop0 on /su type ext4 (rw,seclabel,noatime,data=ordered)

```

# Answer
I finally found the answer here: Cryptfs : unmounting /data failed: Device or resource busy

In short: just rebooting worked, nothing was written to disk at all yet.

Note to self: always make a backup right before potentially destructive operations. Saves quite a lot of headaches :)

The answer above also says booting into safe mode fixes the problem. I have yet to verify that.
> 0 votes

---
Tags: data-recovery, disk-encryption
---


# Question
Title: How to Enable Android Opera mini browser off-road mode?
Recently I found that, enabling off-road mode in Opera mini browser is a great way to hide my browsing data from ISP. So I installed the version 24.0.2254. But I couldn't find the option in enable the off-road mode. Seems like this option is available in old versions but not in latest ones. Is off-road mode is obsolete now or is there any alternative options available?

# Answer
> 0 votes
In newer versions of Opera Mini, Offroad mode is automatically enabled. If you are concerned about your browsing data (Privacy), you can use a VPN.

---
Tags: google-play-store, browser, opera-mini, opera-browser, browser-add-ons
---


title: Does "test-keys" mean device is rooted?

text:
# Question
Title: Does "test-keys" mean device is rooted?
I have Android phone that fails to boot after working happily some time.

I'm trying to install official firmware update zip from manufacturer's site, but update fails with errors:

```
  E: footer is wrong
  E: signature verification failed
  E: install package error, result = 7

```

Google results suggest that official updates can fail integrity verification only if the device is rooted (yes, I've re-downloaded the update several times, the file is ok). As the phone does not boot, I cannot use the "root check" app or terminal etc. On top of the recovery menu, after the ROM version (I guess) there's a line: **user/test-keys**.

**Is this a sign that the device is rooted?**

# Answer
> 5 votes
**It means that firmware on your device is not signed by release keys and is vulnerable**

> The Android tree includes *test-keys* under `build/target/product/security`. Building an Android OS image using `make` will sign all .apk files using the test-keys. Since the test-keys are publicly known, **anybody can sign their own .apk files with the same keys, which may allow them to replace or hijack system apps** built into your OS image. For this reason it is critical to sign any publicly released or deployed Android OS image with a special set of release-keys that only you have access to.

(Emphasis Supplied)

This SO question supports

> Release-Keys and Test-Keys has to do with how the kernel is signed when it is compiled. Release-Keys means it was signed with an official Key from an official developer. Test-Keys means it was signed with a custom key generated by a third-party developer. From a security standpoint Release-Keys generally means the kernel is more secure, which is not always the case

and hence is a security risk as reiterated in this XDA post

**Does it mean my device is rooted?**

The fact that you have not been able to apply official firware updates ( which check for root ) indicates that the device may be rooted (in addition ). You can verify in alternate ways (other than apps ) as mentioned here How can I tell if I have root?

Related Can I 'trick' my device into thinking it's unrooted?

---
Tags: rooting, recovery-mode
---


# Question
Title: Google Play: Error downloading app - insufficient space
After one of the latest updates (not sure if it was the last one or a previous one) of the Google Play app, I am having an error trying to update a large app (42MB). It says:

> Error Downloading . There is insufficient space on the device.

My device is a Samsung P1000 running Froyo. It's rooted, but the error was there before rooting it.

A quick Google search showed several Samsung users having the same problem (the app in question that was giving me the headache is Smurf's village). Some said that removing the updates to the Android Market (Google Play) app would fix it, but to me it was of no avail.

I also tried the procedure in this Google help FAQ to no avail.

Now I am stuck with a prehistoric version of the Market (that works on small apps) and still cannot update Smurf's Village or install big apps. How can I fix this?

EDIT: device has over 2GB of internal SD storage, 27GB of external SD card, so space is not an issue.

# Answer
> 9 votes
For me, it was all about killing and rebuilding a bigger cache. I want it registered on SE so other people having the same problem can find an answer googling for it.

The problem seems to be with the size of the partition the cache is in. It is mounted on a 20-30MB partition in the phone internal SD card.

The fix that worked to me was described in this blog post.

THE BLOCK BELOW IS TAKEN FROM Jimmy Halim's blog post, and used with his permission.

> After browsing around, I found out that the cache folder (that I assume used by the market) is using small partition (around 20mb in my case). So to solve this we need to change it to bigger partition.
>
> You gonna need Android Terminal Simulator or equivalent terminal app. This will also require your Android rooted.
>
> Type `su` (root permission request will be shown: you need to approve it).
>
> Type `cd /`
>
> Type `umount /cache`
>
> Type `mount -o rw,remount -t rootfs rootfs /` (to set the folder access to rw – read write)
>
> Type `rmdir /cache` (delete cache folder). I personally using root explorer to do point 5-6.
>
> Type `mkdir /sdcard/cache`
>
> Type `ln -s /sdcard/cache /cache` (to link cache folder to /sdcard/cache – which should have bigger partition size)

My p1000 was rooted and had terminal emulator and busybox installed. I just typed the commands in the order described by Jimmy Halim (kudos to him).

Searching for the background to this question, I also found this forum post (in portuguese) that seems to (untested by me) solve the problem using an app.

\[begin portuguese posting\]

Para solucionar o problema, eu precisei modificar o tamanho do cache do telefone

\[end portuguese posting\]

# Answer
> 0 votes
Can you check how much space is left in internal storage of your device? You can do that by going to Settings-\>Applications-\>Storage Use and see how much is free space in internal storage. If the value is less that what the app needs (i.e. 42 Mb) then it means that you have to free up some space before installing.

To free up:

1. Best is to visit the app list and remove unwanted one, starting with the one that occupies more space.
2. Move the heavy apps to SD Card. Though I suspect this could be possible only from GingerBread onwards and not in your Froyo.

# Answer
> 0 votes
Just to add some other things to try if @Mindwin's answer doesn't work for you:

1) Delete your logs located in `/data/log`.

* You can do this by either going to the recovery menu and deleting the logs (if the option is available for you, it isn't for every phone). Or if you have a rooted phone you can run `rm -r` in this folder from a terminal emulator.

2) If you can install apps, the `SD Maid` app can remove any lingering cache or apk files that are sometimes left over after removal.

3) If your phone is a Samsung Galaxy, you can dial `*#9900#` from the dial screen and then choose the second option: "Delete Dumpstate/logcat".

---
Tags: google-play-store, internal-storage, samsung-galaxy-tab, insufficient-memory
---


# Question
Title: HTC Desire 526 stuck "Proccessing" after factory reset
I just recently factory reset my htc desire 526 and when I turned it back on, this happened

and then this happened

I've tried going into recovery mode and rebooting from there, i've also reset from the recovery screen, but every time it leads up to that point. its currently been stuck there for like 30-40 mins,

Help appreciated, Thanks

# Answer
Turn phone off remove the sim card and start your phone again.
> -2 votes

# Answer
Turning it off taking out the battery and the sim card replacing the battery and turning it back on got my phone past that page. Rekia87 was right.
> 0 votes

---
Tags: htc-desire
---


# Question
Title: Help in identifying the pop up notification icon
Can anyone please help me figure out the icon provided by me in the screenshot that appears on the top left corner of the notification bar which looks like a message box with an exclamation mark! Whether it is an app notification icon or android system based icon.

>

# Answer
> 0 votes
You can pull down the notification bar, tap and hold on the notification and then tap "**i**" to show more information about the app that pushed the notification.

---
Tags: applications, notification-icons
---


# Question
Title: Using Official Raspberry Pi Power Supply to charge phone?
I have a Moto G 3rd Gen, and my phone charger broke. I have both the raspberry pi official 10W power supply and the raspberry pi official 13W power supply. Can I use either or both of them to charge my moto g 3rd gen?

# Answer
USB standards specify 5V plus / minus 0.25 V which is supplied by pi 10W supply whereas 13 W supply is 5.1 V which is not recommended

~~So you can use the 10W power supply~~

Thanks to Ghanima in comments , who pointed out something I overlooked

> The 13W supply is listed as 5.1 V with a 2% line regulation (that would be 5.1 V plus/minus 0.1 V) which puts it well within the USB spec

So you can use **both chargers safely**, as pointed out in other answer giving additional reasons. Sorry for missing this detail
> 3 votes

# Answer
As @beeshyams answered, the USB Standards specify that charging voltage should be 5.00V ± 0.25V, i.e. 4.75V~5.25V.

Most cables have resistance, which lowers the **actual** voltage that your phone receives. A typical 1-meter long 24AWG cable eats approximately 0.5V. So some good chargers have a feature called **loss compensation**. These chargers raise their output voltage when a load is detected. In my case a Samsung charger (shipped with S5/Note 4) can raise output V to 5.6V at a load of 2 Amperes. It's completely safe to use the 13W charger if it doesn't exceed 5.5V. It will be faster than the regular 10W one. But if it only output power at 5.1V, the speed boost isn't quite noticeable.
> 3 votes

---
Tags: charging
---


# Question
Title: How to check the current platform of Android OS?
There are 4 common platform such as: ARM, ARM64, x86 and x86\_64 on which Android can run.

**How can I check which platform I'm on within Android OS?** So I can check whether my app is compatible with it or not.

I'm using different emulators (BlueStacks on Mac, Genymotion on Demand, etc.), so I'd like to check basically which platform they're exactly emulating, because some apps works for me on BlueStacks, but not on Genymotion.

# Answer
If you have set up, it's a one-liner at the shell prompt:

```
$ adb shell "getprop ro.product.cpu.abi"
arm64-v8a

```

In this example, the device asked answered that it has a 64bit ARM V8a CPU (second line).

Note: You can also run the quoted command in a terminal emulator running on the device / emulator. In there, it's just `getprop ro.product.cpu.abi`.
> 10 votes

# Answer
CPU -Z is a versatile app that gives you SoC information apart from some other apps

From app description on play store
> 6 votes

---
Tags: android-x86, compatibility, emulators
---


title: 64GB phone storage but only 8 available

text:
# Question
Title: 64GB phone storage but only 8 available
I have a pad with 64GB internal storage space. It seems I can only use 8GB at a time. All the apps I tried shows 48GB free storage, but I don't have the chance to access all this memory. Does anybody knows how to solve that issue? thanks in advance.

# Answer
> 0 votes
This can be one of the reasons below:-

1. Maybe the storage was mistakenly partitioned when the manufacturing guys were installing the OS.
2. There's some real problem with the hardware or software. Contact the nearest service centre.
3. The storage is corrupted. Did you do some experiments?

The problem can be something different also. I also had the same problem when I rooted and flashed a custom OS on my phone. The problem was due to some code error in the ROM which made useless partitions in the storage and rendered the storage of no use. If this is the case with your tab, then try flashing a different ROM.

---
Tags: internal-storage
---


# Question
Title: Does the LG Aristo work with gamepads, if so how can I connect it too the ípega?
I have an LG Aristo and I recently got an ípega Bluetooth controller off the wish website, the phone isn't rooted an I don't know much on what to do so it's not working for any of my games I don't know what to do please help...

# Answer
> 0 votes
You can connect your GamePad to your LG as you connect headphones or any wireless devices.

Your gamepad supports android 3.2 and above.

**METHOD 1:**

* Install `iPega Game Center English version`(Google for that). and install it. This will serve as IPEGA remote Bluetooth gamepad driver for your Android device.
* Enable Bluetooth on your LG phone.
* Once you have installed the IPEGA Game Center successully you need to enable BitGames IME as default input.
* Turn on the controller by pressing Y + Home button simultaneously. Wait until the red LED indicator blinks as it pairs with your device.
* Once the red LED indicator blinks, open the IPEGA Game Center application. Go to ***mydevice*** and ***bind controller***.
* A console will open. This will help you calibrate your controller. Try moving the joystick and the buttons.
* Done. Test it with a supported game or an emulator.

**METHOD 2:**

If you have the PG-9028 model, you won't need the IPEGA Bluetooth controller app.

* Turn on your IPEGA PG-9028. Also, make sure that your LG Bluetooth is turned on.
* Now, on your IPEGA Bluetooth controller, press and hold both the X + HOME button, simultaneously.
* Wait until you see the LED from your IPEGA gamepad with touchpad blinking constantly.
* On your mobile device, open the Bluetooth menu. Scroll down (if needed) and look for Available Devices.
* What you should look for is “PG-9028” or sometimes Android will see it as a keyboard input device.
* Select PG-9028 to start pairing. Once the pairing is successful, you will notice that the LED light on your IPEGA PG-9028 will stop blinking.
* Done.

---
Tags: lg, game-controllers
---


# Question
Title: How to install adb tools on Linux with no GUI?
I need to use the adb command on my Linux machine which does not have a GUI. Is it possible to install SDK tools without a GUI? I am using Debian 8

# Answer
From the command-line, you can run:

```
sudo apt-get install android-tools-adb android-tools-fastboot

```

Source: Installing ADB and Fastboot.

Note: If you're already logged as `root`, you can skip `sudo`.
> 0 votes

---
Tags: adb, linux
---


# Question
Title: How to create Android EC2 AMI from scratch?
I've tested all Genymotion on-Demand AMIs, but they doesn't work for me, since some apps are not compatible with 64-bit platform.

I'd like to create my own x86 (32-bit) AMI where I can install The Open GApps, then install some other apps. What would be a good starting point to do that?

# Answer
> 0 votes
To save compile times of the entire Android OS (see: Requirements and Building of Android OS) and your custom ROM builds from hours, it is possible to use Android Open Source Project AMI as a starting point for building the entire AOSP build environment which is pre-configured and completely synced with the repo on this app and ready to go.

Once the instance is ready, run these commands to compile the Android OS:

```
$ cd aosp && . build/envsetup.sh
$ lunch aosp_arm-BUILDTYPE
$ make -j4

```

The `BUILDTYPE` is one of the following:

* `user`: limited access; suited for production,
* `userdebug`: like "user", but with root access,
* `eng`: development configuration with additional debugging tools.

See: Preparing to build.

The solution above eliminates the need to host a build environment on the local machine, or require the Linux OS.

---
Tags: android-emulator, cloud, genymotion
---


# Question
Title: Duplicate Text Messages, Verizon: DroidX2
I have a DroidX2 on Verizon and I always get duplicate text messages and it's super annoying. Is there a simple way to fix this? Or is this a carrier issue?

# Answer
This does sound like a network (carrier) issue, however, do you have any applications that intercept text messages? If so, uninstall it, and see if that helps.

Edit: i just got this issue on an ICS rom. What i think it could be - your network holds the text, and tries to send it if your phone is turned off, or has no signal. It then tries to send them. After it has sent, the network doesn't actually realise it, and sends it again.
> 3 votes

# Answer
Yes this is clearly a carrier issue.

If you are using the stock sms application, I've never come across this apart from carrier forwarding.
> 0 votes

# Answer
Sounds like a carrier issue, as said. However, this could be due to an issue with your connection?

You could possibly do a Factory Default Reset, and see if that alleviates the problem. Could be a faulty installation causing the connection to send twice or something? Not too sure how that works, but it might be worth a shot.

If not, then possibly contact your Carrier, regarding the issue, and they may have an appropriate answer for your query.
> 0 votes

# Answer
My wife had the same problem on her phone and as the resident tech, it fell to mo to resolve it. She has a Blu VIVO XL V0030UU 16GB 4G LTE Unlocked GSM Phone. I tried disabling any apps on the phone that may have been receiving SMS texts and forwarding them on to no avail. Our carrier is Tmobile. What finally worked was going into the settings and disabling "Enhanced 4G LTE mode".

My working theory at this point is that the SMS is transmitted and times out waiting for an ACK and then resends.
> 0 votes

---
Tags: sms, verizon
---


# Question
Title: Enabling ADB on Nexus 6 with dead screen
So I acquired a Nexus 6 with a completely dead screen. (Dead as in I cannot see anything)

The phone powers on (and off) and is detected by my computer.

I want to be able to see the phone's display on my computer. I believe the process will be straight forward if I mange to get ADB enabled

The phone is presumably locked (I do know the unlock pattern) and USB debugging is disabled.
`adb devices` gives no output

When I boot into recovery mode, `fastboot devices` recognizes my device.

The phone is probably unrooted and has a locked bootloader. I do not need to preserve any data.

If I manage to get ADB working, I known of tools that will allow me to view my phone screen, which is my end goal.

I looked at Broken screen while debug mode was disabled. How can I re-enable adb? but when I tried booting CWM recovery rom, I got the message "FAILED (remote failure)" because the bootloader is locked? Similar problem with Android toolkit.

Anyone know of a way to enable ADB through fastboot when *USB debugging is not enabled*

Thanks in advance

EDIT: I followed this guide to not avail

```
$sudo fastboot flash recovery twrp-3.1.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11757 KB)...
OKAY [  0.535s]
writing 'recovery'...
OKAY [  0.189s]
finished. total time: 0.724s
$ sudo fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...

```

# Answer
> 4 votes
I followed this guide

1. I went into fastboot mode by holding down the power button (force restart) and the volume down key (recovery mode)
2. I downloaded a twrop image from: https://dl.twrp.me/shamu/
3. fastboot flash recovery twrp.img
4. fastboot reboot (while holding the volume down key see note)
5. Then I booted the recovery image
6. adb with root permissions detected my device. If you get a permission denied error try killing adb and running with sudo

\*Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

---
Tags: adb, fastboot, rom, usb-debugging, broken-screen
---


title: can't flash or enter recovery mode

text:
# Question
Title: can't flash or enter recovery mode
hi i got a xiaomi redmi note 3 pro and i wanted to flash the latest version of miui, so my previous build that i got was a rooted phone with twrp and i wanted to flash with otg. i did the common process y'know wipe etc.

but while it was restarting it stop at the boot logo a long time..... and still , i can just enter fastboot mode and not the recovery.. when i'm trying to restart it or anithing like this i shows the logo again

i started my research to find a solution and tried to start recovery with adb fastboot on my pc, but my pc didn't detect my device. i searched the internbet for a suitable driver but found nothing.

and now i need help. plsssss i need your help

# Answer
You'll use fastboot mode to flash a ROM to your phone. A Windows computer is needed.

Important Note: *Make sure that your device is fully charged or has enough power for this process. This guide will help you update your device to the latest MIUI ROM version. All user data will be purged in this process. Please back up your data and think twice before proceeding.*

1. Download full ROM from the official site
2. Download MIUI ROM Flashing tool
3. Download drivers ans install them
4. Turn off the device. Press the Volume down button and the Power button at the same time to enter Fastboot mode. Then connect the device to the computer via a micro USB cable.
5. Unzip the ROM you previously downloaded. Open the file folder for the unzipped ROM pack, and copy its path on the computer.
6. Unzip the MIUI ROM flashing tool downloaded in Step 2, and double click on it to install. After installation is completed, open MiFlash.exe and paste into the address bar the ROM file folder path copied in the previous step. Click on the first button (circled out in yellow) to Refresh, and MiFlash should automatically recognize the device. Then click the second button (circled out in red) to flash the ROM file to the device.
7. Wait until the progress bar inside MiFlash turns fully green, which means the ROM has been successfully installed. Then your device should automatically boot to the new version.
8. Done.
> 1 votes

---
Tags: adb, rom-flashing, recovery-mode, fastboot, xiaomi
---


# Question
Title: D855 CM13 Nightly to Lineage 14.1 Nightly Upgrade
I have the latest nightly build of CM13(cm-13.0-20161108-NIGHTLY-d855.zip) installed on my LG G3(d855). And I want to upgrade it to Lineage OS 14.1 nightly builds(for example latest right now: lineage-14.1-20170529-nightly-d855-signed.zip).

Is it possible to upgrade without wiping the data?

# Answer
> 0 votes
Found the Answer:

If you already have CM or an unofficial AOSP based ROM, you don't have to wipe your device - in the download section there's an "experimental" build that you can install over your existing AOSP based ROM and it will migrate you to LOS without needing to wipe (potentially - it may not work and boot loop, in which case you'd need to wipe anyway).

To install:

1. Download both the nightly/weekly/stable version of LOS 14.1 and the "experimental" image.
2. Boot to TWRP
3. Install the "experimental" build
4. Reboot

* After a reboot, the system should load and a watermark saying "cm to lineage migration build" should be all over the screen. If this is the case - everything worked fine! Continue to the next step. If it didn't boot, just reboot to TWRP and wipe the device as per the instructions above and continue with the instructions in the article.
    * If everything went fine, reboot, go back to TWRP, install the regular image and reboot back to a fully working Lineage OS.

Reference:

However, now I need to find experimental build which was removed from LineageOS download section couple of months ago.

Thanks anyways

---
Tags: cyanogenmod, lg-g3, lineageos
---


# Question
Title: My Android Phone Keeps Telling me that it is on Silent
Ever since I updated my mobile to Android Version 6.01 I get notifications regarding my phone being on silent... This only happens when I plug it onto charge.

Its rather annoying that it keeps telling me this for two reasons:

A: The phone is on Vibrate not Silent

B:I chose to put it on vibrate I don't understand why it needs to keep telling me this.

The same applies for when I leave battery saver mode on, it tells me its on and that the performance is effected. I leave it on battery saver for a reason...

Is there any way to disable these "Helpful" Messages in the settings as I cannot for the life of me find a setting that references this, even in the developer mode. My phone is a Samsung Galaxy S5 Mini if that provides any assistance...

# Answer
> 1 votes
I went into Samsung+ app, went to Settings and turned off Diagnostic Notifications. Have not seen the notification since.

# Answer
> -1 votes
Samsung Galaxy. Following Rick's tip that it was a Samsung app, I disabled the app in the app manager. That worked for me.

---
Tags: notifications
---


# Question
Title: How do I tether my android phone mic to my windows computer
I do not want to buy a standalone mic to be used on my Windows computer. Can I use the mic in my android phone as the mic for my Windows computer?

# Answer
The easiest thing would probably be WO Mic.
> 0 votes

---
Tags: microphone
---


# Question
Title: What are the correct specs of Tecno W3 smart phone?
I would like to by Tecno W3 smart phone (Android 6.0 Marshmallow).

I googled to know its GPU. Some websites said it's **Mali-400 GPU** such as:

1. http://bestmobs.com/tecno-w3/
2. http://naijaquest.com/tecno-w3-specs-features-reviews-and-price-official/

And other websites said it's **Mali-400MP2 GPU** such as:

1. http://www.androidphonesinnigeria.com/tecno-w3-full-specifications-features-price/
2. http://www.droidafrica.com/tecno-w3-brings-android-60/

The official website of the phone does not give any information about the GPU nor the part number of the CPU IC.

How can I know the real GPU when I test the phone at the shop? Is there an android test code? Thank you very much,

# Answer
> 1 votes
Test it with CPU-Z when you're in store and permitted to access the device.

# Answer
> 1 votes
**TL;DR** If your model supports 4G LTE, then its GPU is **Mali-400 MP2**. If it has no 4G support, its GPU is **Mali-400 MP** (single core).

I noticed that there might be **2 different models** of that phone. Older one (doesn't support 4G cellular network) uses MediaTek MT6572, while newer one (4G cellular) uses MT6582.

Both MT6572 and MT6582 have ARM Mali-400 GPU built in. MT6572 has only one GPU core, thus called **Mali-400 MP**. MT6582 has 2 cores built, so it's called Mali-400 **MP2**.

ARM **Mali-400** is the **name** of the core (and architecture), while **MP2** states that there are 2 Mali-400 cores. So in all, **Mali-400 MP2** is a specific configuration of Mali-400.

The two different statement do not conflict with each other, only the first one not telling how many cores there is.

---
Tags: hardware, gpu, tech-specs
---


# Question
Title: root access failed or busybox was not found
```
Phone: Xiaomi Redmi 4 prime
Rom (custom): lineage-13.0
Xposed: xposed-v87-sdk23-arm64
Root: SuperSU.Pro.2.82

```

Right now everything works just fine and those apps that need root privileges to work properly, asking for root permission and after granting, they work fine;

There's just one app call Performance Profile (an xposed module) that after running asserts that: **"root access failed or busybox was not found"**

I do have successfully installed BusyBox 6.7.3.0

What is the problem with this app?

**Update 1**: I uninstalled BusyBox 6.7.3.0 and installed BusyBox 1.26.2 and using BusyBox Checker Pro 2.0 got the following results showing that everything is ok.

# Answer
> 0 votes
flash rooting using SuperSU-v2.65 solved the problem.

# Answer
> 0 votes
**A wild guess**: You did not correctly install busybox.

BusyBox is **not** a simple application, it's a executable binary that should supposedly be located in `/system/xbin`. A correct installation of BusyBox includes copying the binary and creating symbolic links.

Judging by the version number you gave, you might probably installed something like "BusyBox installer" from Google Play or so. The (currently) newest BusyBox binary version is 1.26.1, so you may want to check again if **BusyBox** is installed correctly, **not an app from GP**.

---
Tags: root-access, xposed-framework, busybox
---


# Question
Title: How to change my default save location from sd to internal memory card of phone?
I have a dooge x5 max pro android 6.0 . How can i change the save location by simple steps?

# Answer
> 0 votes
The steps for changing default Storage is the same for many Android devices. You just need to go in **Settings \> Storage** and charge the **Preferred Install Location** to SD Card.

---
Tags: file-system
---


# Question
Title: remap ab shutter 3 buttons to record video
I have a lg g5 with the built-in camera app. I bought a remote shutter (ab shutter 3) which is a remote control (bluetooth based) for the camera which has two buttons: one for android and for iOS (iphone). Apparently, the "iphone" button also works for androind (I think it is the 'volume up' button but i'm not sure). The shutter works great but the problem is that both buttons take a picture. What I want is to remap one of the buttons to make video recordings. I think that this problem is equivalent to remapping the 'volume up' button in the built-in camera app to make video recordings instead of taking pictures. How can I do that?

# Answer
I solved this problem on a Galaxy S7 running Android 7.0. Go into the camera settings and scroll down to the bottom. Click on "Volume key function" and select "Record video". I can now click the top button on my AB Shutter 3 to record video.
> 2 votes

---
Tags: camera, video-recording, bluetooth-pairing
---


# Question
Title: Can I safely delete items in my "downloaded apps" folder?
I want to free up space on my phone and was wondering if I can delete items in my "downloaded apps" folder. I know on my computer there is a difference between the downloaded file and the installed application and that once the application is installed the downloaded file can be deleted. But I wasn't sure about my phone.

# Answer
> 1 votes
**Direct answer**: Yes you can safely delete the apk you download once it is installed.

**Developed answer**: Any apk file you download goes to the external storage (either external sdcard or fuse-mounted internal storage that appears as external storage). Installing an apk is just a matter of copying it to internal storage (inside a folder within /data partition). so once installed, the apk becomes redundant, and it is safely to remove the one you downloaded.

# Answer
> 0 votes
If the folder you are refering has the apks of the apps you have downloaded then they can be deleted since they are not requied for the app to function.

# Answer
> -1 votes
When I attempt a delete of a file in the downloaded apps folder on 5 June 2017 on my Galaxy Prevail, a box appears advising that the app will be uninstalled.

---
Tags: file-management
---


# Question
Title: Many apps using sound crash after approx 15 minutes
I have a 100% normal Samsung Galaxy A3 2015 (SM-A300FU) with Android 5.0.2. It is non rooted. I notice that every time I use an app using sound (this might be an effect, but not the cause):

* WhatsApp phone call
* Music Folder Player Full
* a webradio app (that plays radio continuously)

the app crashes after ~ 15 minutes. It happens with no dialog box, it returns to desktop screen.

**What could cause such a bug? How to solve this?**

# Answer
> 0 votes
@xavier\_fakrat's useful answer provides many potential reasons that could have caused the crash. After more investigation, here is what caused the crashes: the Android **app optimisation** feature, that can be found in Settings \> **Battery** \> Optimisation.

The solution for me was to disable optimisation for Whatsapp and music player apps.

# Answer
> 1 votes
The issue of applications constantly crashing in Android Lollipop may be attributed to bugs in this Android version or other reasons which are described below:

1. **Audio bug (possibly AudioFocusLost)**

This bug is described by a user on this thread: Why are my music player apps crashing frequently since recent Android update.

> This is an inherent flaw in Lollipop where apps crash constantly. You notice this with music apps as audio stops. Some apps stop restart where they left off, others don’t. With this bug when the app crashes, the audio just cuts out, there is no on-screen error message.

In addition, more information about this bug is revealed through an error logging of different audio apps by one user, and it produced this error:

`Java.lang.Exception: AudioFocusLost`

With some possible reasoning that;

> this exception handling may have been broken across audio apps in Android Lollipop, or possibly an overly aggressive process causing this exception in other apps

Source: https://www.reddit.com/r/GalaxyS6/comments/34ipjr/music\_players\_pausing\_andor\_closing\_when\_playing/

---

2. **Over-utilisation of system resources (e.g RAM)**

It is possible that with many applications running in the background, the system resource tends to become overconsumed by RAM and CPU hungry processes such as social media apps etc.

In this case the inbuilt task manager in Samsung devices tend to kill such processes unless explicitly turned off in Smart Manager settings to conserve power and memory to cores apps (*known system apps to me include media scanner and DRM content storage –consume a lot of resources when apps accessing related media are in use*).

That is, I why I think it’s a possible cause although certain android versions have more pronounced effects than others, possibly due to poor memory management in a certain Android version.

---

3. **Android System Webview bug**

This component was also held responsible for causing app crashes due to a buggy update. Many apps using the feature (typically those rendering webpages internally) could also crash. Newer versions are based on chromium however. So uninstalling the buggy update could save app crashes.

---

This is not the whole list of bugs causing application crashes in Lollipop, but there may be more but with respect to the question I found these reasons to be more closely related to the issue in question.

**Possible fixes**

1. Before going to any advanced operations, regular cleaning of application cache and closing recent application no longer needed is a good habit to preserve system resources.

---

2. Prioritising the affected applications in system mangers (Smart Manager) and preventing be “killed” when RAM is too low.

If this is futile, then more advanced operations are required.

---

3. Wiping cache partition

Follow these steps:

* Turn off your device
* Press and hold the combination of keys (press and hold Volume Down, Volume Up and the Power button)
* Hold the buttons until the Recovery menu shows up
* Use Volume buttons to navigate to Recovery mode (and select it using the Power button)
* In the Recovery mode menu, navigate to Wipe cache partition and select it with the Power button
* When this is completed, navigate to Reboot system

---

4. Factory reset

* If nothing seems to work, maybe your device needs a fresh start.
    * Factory data reset will wipe everything off, all the apps, settings, etc. Don’t forget to backup your files!
    * Go to Settings
    * Tap Backup & Reset
    * Next, tap Factory data reset
    * Tap Reset phone

---

5. Upgrade Android version

* Upgrading the OS version can be an important way to solve bugs as developers often fix bugs in subsequent OS versions. You can do this through Settings ≥\>System updates and check for available updates. Alternatively downloading appropriate firmware files from manufacturers' website and flashing via Odin

References

---
Tags: 5.0-lollipop, audio, crashes
---


# Question
Title: WiFi not working on Samsung Galaxy S3: "WifiStateMachine( 2240): Failed to load driver"
**Problem description:**

I have a WLAN problem with my Samsung Galaxy S3 (GT-I930). I cannot activate WiFi. Logcat shows me that the driver could not be loaded (detailed WiFi logging has been activated via the developer options):

```
D/WifiService( 2240): setWifiEnabled: true pid=3142, uid=1000<br>
E/WifiService( 2240): Invoking mWifiStateMachine.setWifiEnabled<br>
E/WifiStateMachine( 2240):  InitialState !CMD_START_SUPPLICANT 0 0<br>
E/WifiStateMachine( 2240): Failed to load driver

```

The `netcfg` command does not list any `wlan0` interface:

```
lo       UP     127.0.0.1/8   0x00000049 00:00:00:00:00:00
sit0     DOWN     0.0.0.0/0   0x00000080 00:00:00:00:00:00
ip6tnl0  DOWN       0.0.0/0   0x00000080 00:00:00:00:00:00
rmnet0   DOWN       0.0.0/0   0x00001090 00:00:00:00:00:00
rmnet1   DOWN       0.0.0/0   0x00001090 00:00:00:00:00:00
rmnet2   DOWN       0.0.0/0   0x00001090 00:00:00:00:00:00

```

In the WLAN advanced settings, there is no MAC address available.

The WiFistatus that can be reached via the `**#*#*4636#*#***` service code on the phone number pad lists the following information:

Wi-Fi state: Disabled
Network state:
Supplicant state: UNINITIALIZED
RSSI: -127
BSSID:
SSID:
Hidden SSID: false
IPaddr: 0.0.0.0
MAC addr:
Network ID: -1
Link speed: -1 Mbps
Scan results:

**Android version:**

The phone is rooted, ClockworkMod Recovery (CWM) is installed. I tried different custom ROMs (see next point "history"). The current Android version is 5.0.2 (ROM: Liquid Smooth Lollipop, Kernel-Version: 3.0.31-CM-gdd7ad6a)

**History**

At first, I rooted my phone and flashed **Cyanogenmod 10.2 cm-10.2.0-i9300** (Stable Version, Android 4.3)). Everything worked fine (including WiFi) and I was pleased with the smoothness and beauty of the Cyanogenmod.

Out of curiosity, I tried a **Cyanogenmod cm-11-20150614-NIGHTLY-i9300** (Android 4.4) and faced the problem the first time. After returning from airplane mode, the WiFi was broken. I assumed the nightly build to be still buggy and reflashed the Cyanogenmod 10.2. However, I was not able to get the WiFi back.

After that, I returned to a **stock ROM** but no luck. The WiFi was still dead.

I started to consider that it might be a hardware issue and got a **new WLAN antenna as well as a new WLAN-speaker-thingy**. I changed the parts and tried again with Cyanogenmod 10.2. Guess what, the WiFi was working again. But unfortunately not very long. I am not quite sure but I assume the WiFi went away again after returning from airplane mode.

Well, I then tried two other custom ROMs: **SlimKat 4.4. Slim-i9300-4.4.4.build.9.0-OFFICIAL-8312** and **Liquid Smooth Lollipop (5.0.2)** which is still on the phone.

**On Liquid Smooth, I was able to get the WiFi back a couple of times** (meaning I could see local networks in range and even connect to one of them) but never really long and in the end, it died again forever.

I am really confused about the question: Is it a software or a hardware issue? I sent the WLAN speaker module back to the merchant and tried another one but was not able to revive the WLAN since then.

**Other things I tried**

I tried some WLAN fixer apps (without success):

* Wifi Fixer
* Blade Wifi Fix
* FXR WiFi fix and rescue 1.5.0

I tried some useless stuff with the `wpa_supplicant.conf` file that I have read about in another forum.

In addition to that, I also did googling and I think I got through the whole first page of search results for a lot of search terms.

**Logcats**

I pasted the detailed logcats in Pastebin:

**I would really appreciate any kind of help or advice. What can I still try? What could be the cause of the problem? Anything I have overlooked?**

# Answer
> 1 votes
After looking at your `dmesg`, if I am understanding it right, your WiFi device is identified as `mmc2` and an external card

```
<6>[   18.525295] c1 mmc2: card inserted.
<4>[   18.525962] c1 wifi_platform_set_power = 1
<4>[   18.525970] c1 ------------------------------------------------------------------------------------------------
<4>[   18.525978] c1 brcm_wlan_power Enter: power on
<6>[   18.525983] c1 111brcm_wlan_power Enter: power on
<4>[   18.525988] c1 gpio_table = [2]

<7>[   18.526198] c1 WLAN: GPIO_WLAN_EN = 1
<4>[   18.730036] c1 wifi_platform_bus_enumerate device present 1
<4>[   18.730044] c1 gpio_table = [6]

```

And is cycling on and off because it is having the wrong/excessive voltage being pumped into it.

```
<6>[   16.407671] c1 mmc2: card inserted.
<3>[   16.635241] c0 mmc2: cmd 52 command index error error
<3>[   16.636109] c0 mmc2: cmd 52 command index error error
<3>[   16.641166] c0 mmc2: cmd 8 command crc error
<3>[   16.641729] c0 mmc2: cmd 5 command end bit error
<3>[   16.642015] c0 mmc2: cmd 5 command end bit error
<4>[   16.642068] c0 mmc2: host doesn't support card's voltages
<3>[   16.642080] c0 mmc2: error -22 whilst initialising SDIO card
<3>[   16.643112] c0 mmc2: cmd 55 command end bit error

```

With new hardware, you require a new kernel build with correct device support compiled into the kernel. Whether or not this "cycling" is damaging your new hardware I can't be sure. It wasn't really clear in your question but I am assuming these were internal changes to your phone's hardware? You will likely need to get the specifics of that new hardware and find the driver/kernel-source/support and port it into your current source and compile a new build, modules, and all.

Basically, any room you flash on this "new" device is likely going to fail in the WiFi department, and flashing even back to stock via the/an official firmware release is not likely to fix it.

# Answer
> -1 votes
Renaming the `data\misc\wifi\wap_supplication.conf` file has fixed the problem for some people.

The Android system by default will recreate the `wap_supplication.conf` file after renaming or removing it. In my case, either way, it did work but for a short amount of time. Finally, I just relapsed the wireless adapter, so it's likely a hardware problem.

---
Tags: wi-fi, rooting, 5.0-lollipop, samsung-galaxy-s-3, custom-roms
---


# Question
Title: How can I change notification volume on Android 6.0?
I have an option to change alarm or ringtone volume in Settings, but not notifications as I had in 4.3.

How can I change notification volume on Android 6.0 **without changing ringtone volume**?

I would prefer a solution that doesn't *require* root, but would accept one that requires root if it's impossible otherwise.

3rd-party app is acceptable if there's no way to do so in the OS.

I already considered a hack of setting ringtone to a very loud sound and notifications to artificially quiet sound file, please don't offer that as a "solution" since it doesn't allow adjustments.

# Answer
I'm not aware of a native solution, but my app listing for Volume control has an app called Ringer & Notification Unlink. It requires root and the XPosed framework, but should do its job. From the app description:

> Since ICS, Google has decided to link the volume of ringer and notification volume together. This Xposed module can separate the two streams as they were before ICS.

I have not tried it myself and especially cannot tell whether it works fine with Marshmallow – but the changelog for the latest version explicitly mentions it should: "support for Android 6".
> 2 votes

# Answer
I have android 6. LG g4. When I change volume with my buttons there is a little gear to the right of the bar. If I press it there is a new window where there are separate bars for ringer, notification, & media
> 0 votes

# Answer
Go to settings volume and there are seperate controls for ringtone notification media and systems
> -3 votes

---
Tags: settings, audio, 6.0-marshmallow
---


# Question
Title: "OK Google" stops working after a phone call
Most of the time, the "OK Google" feature of Google Assistant works fine. I say "OK Google" and it goes into *listen* mode. However, everytime I finish a phone call, my phone no longer goes into *listen* mode when I say, "OK Google". Doesn't matter whether it's immediately after the call or half an hour later, it basically just ignores me completely.

Rebooting the phone is the only solution I've found that fixes it. I am currently on Android 7, but I believe this was an issue on Android 6 as well. I have a Galaxy S7.

Is there something **else apart from rebooting** I can do to stop this from happening?

# Answer
> 1 votes
Go to settings then under app section find google app and after that clear it's cache and data .

---
Tags: google-assistant
---


title: Reset ringtone picker preferences

text:
# Question
Title: Reset ringtone picker preferences
My Samsung Galaxy S2 on Gingerbread was set to use Handcent as the default ringtone picker, and I accidentally changed this back to the built-in ringtone picker. How do I get it to use Handcent again? I went to Handcent, cleared the checkbox and marked it back again, but it didn't help.

# Answer
You can use Handcent app as the default ringtone picker. To set Handcent as default ringtone picker, go to

> Settings | Applications | Manage Applications | All | Android System (Sound picker for SE phones)

Click '**Clear Defaults**' button.

After this, When you are choosing a ringtone, You will be presented with a dialog box asking you to select one of the application as ringtone picker. Enable the **'Use by default for this action'** Check-box and select Handcent. This will set Handcent as your default ringtone picker.
> 4 votes

# Answer
in android 4.1/4.2 etc etc its called "media storage" (the one you clear the defaults of)

ya i did just actually go through the whole list and pick it out of ALL of them .. and OMFG IT WORKED ..

hey, sorry im late, but, people seem to be clicking these defaults and not knowing how to clear them (like me) then they go and search for it and nobody knows ..

im actually kind of thankful that it wasnt something more difficult to find, so .. there you go . . "media storage" on samsung galaxy s2 android 4.1
> 4 votes

# Answer
For those that have Samsung 8 the place to reset the default apps is Settings|Apps|App Manager| Go to the Three dots on top right and from the pull-down select Reset app preferences
> 2 votes

# Answer
One workaround would be to temporarily install another app that has a ringtone picker in order to show the ringtone picker selection screen, select Handcent, and remove the temporary app. For example, you can try Zedge.
> 1 votes

---
Tags: ringtone, default-applications, handcent-sms
---


title: Random text string in messages

text:
# Question
Title: Random text string in messages
Recently i factory reset my LG Tribute HD. As soon as setup compleated. I got a message from a random number. Any clue what this is? It reminds me if stagefright.

# Answer
**Wild guess:** It's an encoded message from a terrorism organization telling about a scheduled event :)

**Serious Analysis:** Call your carrier support for more information. This looks like some internal information (metadata) that accidentally leaked out. I made this guess because that message

1. Uses colon for field separator (*very* common in Unix systems)
2. Contains a time stamp (1496949959776 is `19:25:59.776, Jun 8, 2017 UTC`)
3. Contains a Base64-encoded data, which gives a 20-byte nonsense after decoding
4. Contains an unused number from Seville, Ohio
5. Contains a 32-character code in an unknown format

If you don't want to dig too deep or you're not so curious, then you can safely ignore it.
> 1 votes

---
Tags: sms, factory-reset
---


# Question
Title: Where can I find the list of all updates released by Google for Nexus devices?
it's been a while since I updated my Nexus 10 tablet and with each new update, I'm being notified of further newer updates. I've updated my device 6-7 times in 3 days. Where can I find the list of all released updates so I can decide whether I want to update to get certain feature in a later update or not?

# Answer
In the link below they have the factory images for all the versions of Androids for Nexus and Pixel devices

https://developers.google.com/android/images
> 0 votes

# Answer
Ok. I found that there's a list of all security updates here:

https://source.android.com/security/bulletin/

Edit: will update if I find the list for each device.
> -1 votes

---
Tags: updates, ota-update
---


# Question
Title: Does ZTE prevent the use of adoptive storage with Marshmallow?
I was trying to format a 32 GB Samsung SD card for adoptive storage in a ZTE Z815 running Marshmallow, but the only option is portable. What's going on here?

# Answer
> 0 votes
Your device doesn't have this feature enabled by OEM . Similar to other models as you can see from Google search and for another ZTE model Convert portable SD to Internal SD where option is unavailable

Same is the case with some Samsung devices. You would need to search at places like XDA for workaround like this

Also see this question for workarounds

How can I move apps to SD on non-adopted Marshmallow storage?

---
Tags: 6.0-marshmallow, adoptable-storage
---