title: Mobile Data stopped working

text:
# Question
Title: Mobile Data stopped working
I have a Nokia Sirocco 8.1 mobile phone, about 2 weeks ago now my mobile data turned off or stopped working, I contacted my carrier (Boost mobile who use the Telstra network in Australia) they went through all resetting data and checked my SIM activity, all good their end but phone still does not CONNECT.

I contacted Nokia support and they also went through all resetting options and suggestions, I even purchased a new SIM and tried it, still no connection, last thing was a full factory reset of my phone, but still no data connection, all other functions work on the phone, calls, text, wifi all PERFECT.

I have Youtubed for answers as well, tried everything all suggestions but still no Data: is there an inbuilt antenna that picks up data signal or is it a circuit board issue that needs replacing or do I just have a dud phone?

I have to say I have had the phone for over a year and have had no issues, I have used 650 Mbs of a 30Gb plan so I have plenty of Data available, please help me I am very frustrated at the moment.

# Answer
I had Data roaming issues with my Nokia 8.1 Sirocco phone, tried all avenues for answers, Telstra support, Nokia support, all resets and even tried a full factory reset but all efforts did not work.

I sent my phone to Nokia in Sydney, they called me and told me phone was working there, I had to reset my APN protocol and APN roaming protocol.

From settings → network & internet mobile networks → advanced → access point names and changed settings from `IPv4` to `IPv4 / IPv6`, pressed the 3 dots top right hand corner and pressed save.

It works now again, hope this helps anyone with same issues.
> 1 votes

---
Tags: mobile-data, mobile-network
---


# Question
Title: Will a CDMA carrier's LTE work on a GSM-only phone?
More specifically, I'd like to know if a Sprint-based carrier (Tello) will work on a Xiaomi Redmi Note 8 (M1908C3JG).

# Answer
> 0 votes
**No**

Will my phone work says Redmi Note **7** does not work on Tello.

Readme Note 7 has more operating frequencies than Readme Note 8 (see Network section- Note 8 frequencies are a sub set of Note 7 ) but Readme Note 7 doesn't work with Tello.

If you switch carriers, you have a 25 % coverage as indicated here, but that would need you to do homework to find out which carrier and if that frequency (s) are used where you operate

---
Tags: 4g, gsm, carriers, cdma
---


# Question
Title: Can't enable Developer Mode on Nexus 7 2013 with tapping the Build Number
I am trying to root Nexus 7 2013 and for the purpuse I need to enable USB debugging. As instructed from multiple resources, to **enable developer mode** one needs to **tap the build number 7 times**. Did that, plenty of times, but nothing happens.

I saw this other question on the matter, where the case appeared to be that there were multiple users, but in my case there is just one user on the tablet.

About info picture: http://prntscr.com/rmo70x

# Answer
> 2 votes
The problem was that the tablet had installed **Family Link**. Once I removed the account from Family Link, tapping the build option worked.

---
Tags: root-access, 6.0-marshmallow, developer-options
---


# Question
Title: TWRP: adb devices works in recovery but fails in sideload mode
I want to install a custom rom (LineageOS with microG) on My Asus Zenfone Max Pro M1. I followed every steps detailed in the tutorial (enable debugging, unlock bootloader, run fastboot, flash TWRP, reboot in recovery, backup then wipe the system with TWRP).

My problem is when I want to sideload the custom rom. So, `adb devices` works and detects my phone in recovery mode. However, as soon as I lauch the sideload mode in TWRP, `adb devices` is not able to detect my phone anymore and the command `adb sideload xxxxxx.zip` fails because it cannot see any device.

I'm running TWRP 3.2.3, my computer runs on GNU/Linux (Xubuntu 18.04), I have the latest version of the Android SDK.

It is the same question as here from 2015: Device disappears from ADB devices when entering sideload but there was no answer.

Thanks in advance

# Answer
Eventually, I found a workaround (which is not a fix but it allowed me to continue the installation).

Since my device was detected in discovery, I did not used sideload. I just pushed the image to the sdcard with:

```
adb push xxxxx.zip /sdcard/

```

and then I installed the image from the sdcard directly in TWRP.
> 9 votes

# Answer
I have this issue when the adb server is running without root permissions. Try:

```
$ killall adb
$ sudo adb devices

```

This will run the adb server with the correct permissions, then you'll be able to sideload.
> 1 votes

---
Tags: twrp, lineageos, side-loading
---


# Question
Title: Device serial number (using ADB commands)
I'm using an automation platform that has an ADB session which requires the *device\_serial\_list*, which is the serial number. However, if I do `adb get-serialno` I get a different value than the one shown in this website

**Edit:** when you input your IMEI, it shows you several info about your phone and one of them is the Serial Number which is different than the previous one, so I'm not sure what should be the one to use in this case.

**Edit 2:**

The previous pic comes in a link starting by "https://www.imei.info/check/lg-warranty-checker"

# Answer
It looks like you are confusing two different numbers:

* `adb get-serialno` gives you the *serial number* of the device.
* Link in your question is referring to IMEI number which can be obtained by `adb shell service call iphonesubinfo 1` (see this and this for more)

Going by the context, you should use the first number (serial number) and not IMEI number.

Both serial and IMEI numbers are usually found in the *about phone* section in device settings.

**Edit:** Post the edit made by OP, I entered my device IMEI number and it returned the following info, only format shared here, not actual digits `IMEI.info: TAC: AAAAAA FAC: BB SNR: CCCCCC CD: D` \[1\]

The serial number you are referring to SNR above is the 6 digit (6 C's) is the serial number, which is manufacturer-defined, **NOT** the serial number returned by `adb` (verified, adb command returns 8 digit serial number)

So, the answer remains same, use the adb command output

---

Additional Info

\[1\]: Output in the linked site corresponds to **pre 2004** format

> As of 2004, the format of the IMEI is `AA-BBBBBB-CCCCCC-D`, although it may not always be displayed this way

(see section - Structure of the IMEI and IMEISV (IMEI software version) in the IMEI wiki
> 8 votes

---
Tags: adb, imei
---


# Question
Title: How do I get wireless hotspot (tethering) working on an SGH-t999L with Andoid 4.3 LUVUBMK4
I have a galaxy s3 SGH-t999l which is the t Mobile G3 LTE version. I'm rooted using the root 66 MK4 stock recovery tar in odin. I'm running TWRP recovery as well.

The problem is that I cannot get wireless tethering/hotspot to work no matter what I try- here are the things I've already tried-

Wifi Tetherr Treve Mod - I've tried nearly every version of Wifi Tether as well, with nearly every possible setting. Tried setting it up with s3 profile, with galaxy nexus profile, etc. All this ever does is start with errors, tell me to check the log and then when I do tell me that there is no log file.

Native Hotspot mod - this is an odin tar that is supposed to work, but there's no version for my baseband (Mk4), just MK3 and all that does is make android hang at boot to where I have to reflash android back to the t999l root66 MK4 stock.

Wifi tethering 4.3 enable- there are a number of these, from zip files to install in cwm to directions on what files to edit and how in the android system. Nothing has worked.

I got this app Wifi Tether Router that supposedly worked, but while I can get it to actually start up without any errors, as far as I can figure wlan0 doesn't exist. When I do a netcfg in terminal no wlan0 entry appears, at least.

I can currently use FoxFi to tether with a usb cable and pdanet, so I'm not that pressed I'd just like to figure out how to get it to work.

# Answer
> 1 votes
I'm gonna answer my own question here. Apparently, something I did enabled the built in wifi tethering... before, it would fail when it attempted to validate it with T-Mobile, but now it goes through that part just fine. . When it makes the hotspots, it is named foxfisomething-or-another so foxtrot MIGHT have something to do with it, but I think it was one of the flashable zips. . When I figure it out for certain, I'll update this answer.

# Answer
> 1 votes
Download netshare pro apk. It works with 2 phones or you can connect to your router via wps button. If you use it with another phone your carrier cannot tell your using your hotspot and it's unlimited.

---
Tags: samsung-galaxy-s-3, wifi-tethering
---


# Question
Title: Downloading and installing the DEBIAN ARM packages and installing them on Termux?
Ok, so I was looking for a terminal emulator for android and I found Termux. Then I discovered that it has "apt-get" as a package manager and I played around with it and installed a few packages. Then I had the idea! Debian also runs on a few ARM devices so I should be able to find the URL of the repo where the packages are collected. I searched the internet to no avail. So now I have two questions: \- What's the URL to the Kali or Debian package repo containig ARM packages? \- How do I install the packages after downloading "package.deb"?

# Answer
Termux's repository of ARM packages can be found at: termux.net/dists/stable/main/binary-arm/

Additional resources that may be of interest:
> 5 votes

# Answer
I have added debian arm / Ubuntu package in termux by editing source.list file

you will find it at

> /data/data/com.termux/files/usr/etc/apt/

unfortunately I couldn't sign !
> 2 votes

# Answer
The solution: HOWTO install Debian 10 (buster) on your non-rooted Android smartphone

## What is it?

In other words: exactly what you are looking for.

**Disclaimer**: I am hosting that repository.
> 1 votes

---
Tags: android-emulator, terminal
---


title: Recovery mode doesn't work

text:
# Question
Title: Recovery mode doesn't work
I've followed these steps to try to root my phone. Then, I continue following this guide but I'm stuck where it says "Paso 2":

I'm trying to access the recovery mode in my PC with the adb reboot recovery command but my smartphone shows the "No command" message and icon on the screen and after I while, it just restart normally.

I just wanted to install Magisk so I did.

```
C:\adb>adb reboot-bootloader

C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (21104 KB)...
OKAY [ 0.491s]
writing 'recovery'...
OKAY [ 0.235s]
finished. total time: 0.736s
C:\adb>fastboot reboot
rebooting...

finished. total time: 0.010s

```

and then I was expecting to be able to enter the recovery mode, but I've tried all the possible key combinations and I can

Actually, before the "No command" screen I get a warning message asking me to visit: g.co/ABH saying that "**your device software cannot be checked for corruption. Lock the bootloader. PRESS THE KEY POWER TO PAUSE BOOT. Your device will boot up automatically after a while**" and it just restarts normally

I also found this file: /system/recovery-from-boot.p I've read this is preventing me from entering in the recovery mode, but as I'm not root, I can't find a way to delete it or rename it...any suggestion, please?

More info about my phone:

Also, my goal is to install Magisk, so if there is any other way to do it, it will be welcome too.

# Answer
> 2 votes
When you are in fastboot mode you can directly start the recovery image without installing it:

```
fastboot boot recovery.img

```

Alternatively if you want to start the installed recovery rom execute

```
fastboot flash recovery recovery.img
fastboot reboot bootloader

```

and then select `Recovery` using Vol-Up/Down buttons + Power button to start the recovery ROM.

Note that some stock firmware images will replace the recovery ROM back to the original one once you start the main OS. This is automatic "updating of the recovery ROM" is part of the boot process.

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


# Question
Title: How to stop music apps from changing lockscreen
I am not new to Android, but this is the first thing that has actually stumped me. I noticed my default music app (Xperia Z1ˢ BTW) and Spotify both change my lock screen to the album of whatever I'm listening to. Is there any way to turn this feature off easily? I know my way around android, but I don't know the coding language. This isn't really a problem, but a few album art covers are not exactly school appropriate.

**update**

I have checked the default music app settings, and there is no option to change for this issue either. I'm using Android 5.0.2, and the offensive album art is through Spotify. I also have checked my settings for this, there are no "music" options.

# Answer
> 4 votes
You can achieve this by **blocking all notifications** from the app. This will prevent Spotify from showing any notifications, including the album art on the lockscreen. The app will still work and play without issue.

Keep in mind this also prevents Spotify from showing the play controls on the lockscreen as well, so if you want to play/pause/next-track/previous-track, you will have to open your phone. I would suggest adding the Spotify widget to your home screen so you have quick access if you need to pause playback quickly.

Thankfully, you can still control the volume with the hardware volume buttons, even if the screen is off/locked, so if you quickly need to stop music you could at least turn the volume down quickly.

Below is quick tutorial. I'm running an older version of Android but you should still have the option to Block All notifications regardless. Your options will just look a little different from mine. Hopefully this works and is sufficient for your needs!

# Answer
> 0 votes
This option isn't implemented in the spotify app yet. This has been posted on the Spotify community forum as a "New Idea" - Option to disable album art on lock screen and is still in the same status.

The only way I could think you can turn the album art on lockscreen off is by completely turning off the notification for Spotify app(`Settings -> Sound & notifications -> App notification -> Spotify -> Block`). But this would hide all the notifications.

# Answer
> 0 votes
There are 2 Xposed modules for this, I'm also a Spotify user and I hate when whatever OG rapper's explicit album art shows up on my lockscreen.

.

**http://repo.xposed.info/module/com.chaimchaikin.lockscreenalbumartremover**

> Removes full screen Album Art (i.e. when playing music) from the lock screen for Android 5.x

.

**http://repo.xposed.info/module/com.audio.privacy**

> Removes album art and title/artist information from lock screen audio controls (and any other RemoteController) On 5.0 and 5.1 only the album art hiding is effective as the controls are player specific. If you want to hide these too, set a password and configure your phone to hide notifications for your player.

.

I use the second one because I'm on Kitkat. Haven't had any issues.

You'll need a **rooted** phone to install Xposed framework, but it's definitely worth it. (GravityBox/XBlast Tools are the most common add-ons, which let you customize SystemUI -- status bar colors, clock, screen off animation, etc.)

# Answer
> 0 votes
There is a general way of blocking apps from changing your lock screen. Go to Settings -\> Device -\> Display -\> Screen wakes to: and change it from "Lock Screen Notifications" to "Unlock".

Keep in mind that this will block ALL apps from changing your lock screen, not just music apps ...but it seems like only music apps use this feature anyway.

\*This is for Android 6.0 but it is probably the same for Android 5.0. The exact path to this setting my be different depending on your OS.

# Answer
> 0 votes
if rooted + edxposed, you can use GravityBox:

lockscreen tweaks -\> disable media art

tested on OnePlus 6T OOS 10.3.2 (Android Q)

---
Tags: lock-screens
---


# Question
Title: Is it a bad idea to let your phone keep charging all the time?
I read somewhere that long periods of charging can be bad for the battery and the best level to keep your battery at is around 50%. Is this true?

If it is then after how long will the battery show any signs of being affected?

# Answer
For the first part of your question, see Ideal charging / discharging percentage for maximum battery life?. Answers there explain in detail, so yes, it is *true*

Second part, after *how long...* depends on *how often* you charge it the wrong way, your usage (how many cycles of charge) etc and one cannot put a figure to it. Bear in mind that batteries even without being used lose a significant amount of life due to aging. So, it's a bit complicated to separate cause and effect. I don't think it will show up soon but maybe about an year or so (no backing to substantiate)

See answer here for more details Battery capacity wear-down, and its relationship to charging practices
> 0 votes

---
Tags: battery, charging, battery-life
---


# Question
Title: Why I cannot grant "Allow all the time" location permission to WhatsApp?
I have a Pixel 4 and Android 10 stock. I want to share my location for a few hours with a friend using WhatsApp, but the system only offers me these options for location permission:

* Allow only while the app is in use
* Deny

But there is no "Allow all the time". I'm afraid that it won't work without that permission.

I guess Google removed that option for that particular application, other apps have it enabled. Is that right?

PS: I'm aware of who owns WhatsApp and their issues.

# Answer
So here is the problem: the latest (non-beta) WhatsApp is set up with a target platform of Android 10, but the developers failed to include a request for `ACCESS_BACKGROUND_LOCATION` in the `manifest.xml` file in the APK.

This is a problem because this is a new permission introduced in Android 10, and any app not requesting it which also targets Android 10 is assumed to not want background location access.
> 2 votes

---
Tags: whatsapp-messenger, permissions, android-10, location-services
---


# Question
Title: Galaxy Note3 is not recognized by Odin ("SeAndroid not enforcing: set Kernel")
My Galaxy Note3 is not recognized by Odin because its stuck in recovery with `SeAndroid not enforcing: set Kernel`. When I reboot into TWRP recovery, it's recognized by the computer but still fails to acknowledge on Odin.

* **Device:** SM-N9005T Samsung Galaxy Note3.
* **Odin Downloader:** 3.10 (I also have version 3.07)
* **Computer:** desktop running Windows 7 Ultimate

# Answer
> 1 votes
i think you are mixing up things

Odin requires your device to be booted in download mode, not recovery mode. if you are in twrp you must leave revovery mode, you can reboot into bootloader from twrp menu. other method to boot into download mode is button combination Volume Down + Home + Power. then select Continue with Volume Up

SeAndroid not enforcing is just a info message which tells you everything is all right. for full access to partitions TWRP requires kernel which allow setting selinux permissive. if SeAndroid is enforcing it would prevent TWRP from working properly

side note: whatever you want to flash from Odin, you could do from twrp command line, too. twrp has full access to all partitions and skilled user can raw write partition images with adb push or dd

---
Tags: samsung, rom-flashing, odin, seandroid
---


# Question
Title: /data's data is garbled in TWRP. How to decrypt
So this is quite another `android` story but I promise to keep is as short n dry as poss. The issue was some of my Apps weren't able to access /extsd folders with non root & so I deicided to give `magisk module` app `systematizer` a shot. With that also installed Pixel3fy ( or whatever heck its called ) & & `Viper4Android`
I dunno if that has any bearing. Removed Pixel after I booted on a blank screen and data got `encrypted` ( due to that Pixel Mod ? No sure. I can mount /data but all file names under L1 folders are `encrypted` aka garbled ) . I am running `Q Havoc` on top of `TWRP` on `Qualcomm` chip mobile . Earlier , TWRP would ask me my pattern and `decrypt` `/data` and `/system` and I had access to these via `TWRP`. Now ( related to Mod installation ? ), it does NOT ask me for pattern and I can mount these partitions but they remain encrypted. I want my `internal data` . So `Format` `/data` is not an op.
**What I did:
**

-- reinstalled this `TWRP + Vmeta via Fastboot`.( hoping that the pattern will come back again but went futile ) After that no OS load. Just reboots to `TWRP`
-- Followed this by installing boot.img + magisk zip again and Disable\_Dm-Verity\_ForceEncrypt zip
after all this it could BOOT TO LOGO and then HANGS ON LOGO
**Questions :
** -- How do I get TWRP to decrypt /data ( esp int. storage ) .After that I dont mind doing a fresh install after /data format . I want my int data.
--alternatively how can I successfully boot any way so I can backup my internal data
-- take a look at this, where he says you can `decrypt` data by `backup` --\> `format` --\> `restore`. But `/data` is `encrypted` so backup and restore ...isn't it futile ? if I backup this data some form. My understanding is that its useless cos its `encrypted` and restore will be fruitless since the data is encrypted with Unlock pin + key stored in Meta partition. I dont have any more backup. My last Nandroid was of stock rom. The `/recovery /vendor` are same `/system` and `/data` are not. I in fact tried `/recovery` `Nandroid` restore - no use
After that I can do a 'format' and get my OS working.
A subtle clarification. Once I removed the `Pix3ly` module I could boot the phone. `TWRP` would not decrypt data after I tried command line

```
adb decrypt twrp <pattern>

```

I thoughtlessly shot myself in the foot by not backing up my `partitions` via `TWRP` and ended up doing a `TWRP` reinstall, which is when I got stuck-\> will only boot to recovery --\> ( `flashboot boot.img + Magisk` ) --\> Now it will not reboot to `recovery` but stuck at Logo. Thats where I am now.
So yes any potentially offending module was removed and that got me to boot but TWRP re-installation hosed everything. Desperate not to loose data I installed orange fox recovery to see if that can `decrypt` ( of course never had hi Hopes ) and still no light .
`stock recovery` cant handle `Havoc`. Stock ROM is `Pie` and this is Q so that wont match and even then issue is `/data` is not getting `decrypted` so any ROM wont boot is my humble , nimble understanding but do let me know if there's something that can work

```
    Starting TWRP 3.3.1-milankragujevic_9.0_v1-8c0bcc8b on Sun May 31 06:29:22 1970
 (pid 406)
I:=> product model: 'Redmi (A'
I:=> using device id: 'Redmi_A'
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/class/android_usb/android0/f_mass_storage/lun0/file' does not exist, USB storage mode disabled
TW_INCLUDE_CRYPTO := true
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:Got max brightness 2047 from '/sys/class/leds/lcd-backlight/max_brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 2047
I:LANG: en
Starting the UI...
setting DRM_FORMAT_RGBX8888 and GGL_PIXEL_FORMAT_RGBX_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
  vi.bits_per_pixel = 32
  vi.red.offset   =   0   .length =   8
  vi.green.offset =   8   .length =   8
  vi.blue.offset  =  16   .length =   8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
framebuffer: 0 (720 x 1520)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 2047
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 0.666667x and height 0.791667x, offsets x: 0 y: 0 w: 0 h: 0
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page splash
I:Switching packages (splash)
=> Linking mtab
=> Processing /etc/recovery.fstab
I:Reading /etc/recovery.fstab
I:Processing '/boot'
I:Processing '/recovery'
I:Processing '/system_root'
I:Created '/system_root' folder.
I:Processing '/system_image'
I:Processing '/vendor'
I:Processing '/vendor_image'
I:Processing '/data'
I:Processing '/cache'
I:Processing '/cust'
I:Created '/cust' folder.
I:Processing '/misc'
I:Processing '/external_sd'
I:Created '/external_sd' folder.
I:Done processing fstab files
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:File Based Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using Keymaster HAL: 4 from QTI for encryption.  Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@4.0::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/unencrypted/key
upgrade_key failed, code -38
e4crypt_initialize_global_de returned fail
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using Keymaster HAL: 4 from QTI for encryption.  Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@4.0::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/unencrypted/key
upgrade_key failed, code -38
e4crypt_initialize_global_de returned fail
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using Keymaster HAL: 4 from QTI for encryption.  Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@4.0::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/unencrypted/key
upgrade_key failed, code -38
e4crypt_initialize_global_de returned fail
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/Redmi_A'
I:Settings storage is '/data/media/0'
I:Decrypt adopted storage starting
I:PageManager::LoadFileToBuffer loading filename: '/data/system/storage.xml' directly
I:No /data/system/storage.xml for adopted storage
Updating partition details...
I:App found at '/system_root/system/priv-app/twrpapp'
I:Data backup size is 9887MB, free: 9730MB.
...done
I:Unmounting main partitions...

Partition Logs:
/boot | /dev/block/mmcblk0p52 | Size: 64MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p52
   Display_Name: Boot
   Storage_Name: boot
   Backup_Path: /boot
   Backup_Name: boot
   Backup_Display_Name: Boot
   Storage_Path: /boot
   Current_File_System: emmc
   Fstab_File_System: emmc
   Backup_Method: dd

/recovery | /dev/block/mmcblk0p53 | Size: 64MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p53
   Display_Name: Recovery
   Storage_Name: recovery
   Backup_Path: /recovery
   Backup_Name: recovery
   Backup_Display_Name: Recovery
   Storage_Path: /recovery
   Current_File_System: emmc
   Fstab_File_System: emmc
   Backup_Method: dd

/system_root | /dev/block/mmcblk0p59 | Size: 4092MB Used: 1453MB Free: 2638MB Backup Size: 1453MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Mount_Read_Only
   Primary_Block_Device: /dev/block/mmcblk0p59
   Display_Name: System
   Storage_Name: System
   Backup_Path: /system_root
   Backup_Name: system_root
   Backup_Display_Name: System
   Storage_Path: /system_root
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files

/system_image | /dev/block/mmcblk0p59 | Size: 4096MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p59
   Display_Name: System Image
   Storage_Name: System Image
   Backup_Path: /system_image
   Backup_Name: system_image
   Backup_Display_Name: System Image
   Storage_Path: /system_image
   Current_File_System: emmc
   Fstab_File_System: emmc
   Backup_Method: dd

/vendor | /dev/block/mmcblk0p60 | Size: 975MB Used: 672MB Free: 303MB Backup Size: 672MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Mount_Read_Only
   Primary_Block_Device: /dev/block/mmcblk0p60
   Display_Name: Vendor
   Storage_Name: Vendor
   Backup_Path: /vendor
   Backup_Name: vendor
   Backup_Display_Name: Vendor
   Storage_Path: /vendor
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files

/vendor_image | /dev/block/mmcblk0p60 | Size: 1024MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p60
   Display_Name: Vendor Image
   Storage_Name: Vendor Image
   Backup_Path: /vendor_image
   Backup_Name: vendor_image
   Backup_Display_Name: Vendor Image
   Storage_Path: /vendor_image
   Current_File_System: emmc
   Fstab_File_System: emmc
   Backup_Method: dd

/data | /dev/block/mmcblk0p62 | Size: 21916MB Used: 9887MB Free: 9730MB Backup Size: 9887MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
   Symlink_Path: /data/media/0
   Symlink_Mount_Point: /sdcard
   Primary_Block_Device: /dev/block/mmcblk0p62
   Crypto_Key_Location: footer
   Display_Name: Data
   Storage_Name: Internal Storage
   Backup_Path: /data
   Backup_Name: data
   Backup_Display_Name: Data
   Storage_Path: /data/media/0
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files
   MTP_Storage_ID: 65537

/cache | /dev/block/mmcblk0p57 | Size: 355MB Used: 0MB Free: 355MB Backup Size: 0MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
   Primary_Block_Device: /dev/block/mmcblk0p57
   Display_Name: Cache
   Storage_Name: Cache
   Backup_Path: /cache
   Backup_Name: cache
   Backup_Display_Name: Cache
   Storage_Path: /cache
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files

/cust | /dev/block/mmcblk0p61 | Size: 802MB Used: 298MB Free: 503MB Backup Size: 298MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
   Primary_Block_Device: /dev/block/mmcblk0p61
   Display_Name: Custom
   Storage_Name: Custom
   Backup_Path: /cust
   Backup_Name: cust
   Backup_Display_Name: Custom
   Storage_Path: /cust
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files

/misc | /dev/block/mmcblk0p30 | Size: 1MB
   Flags: IsPresent
   Primary_Block_Device: /dev/block/mmcblk0p30
   Display_Name: misc
   Storage_Name: misc
   Backup_Path: /misc
   Backup_Name: misc
   Backup_Display_Name: misc
   Storage_Path: /misc
   Current_File_System: emmc
   Fstab_File_System: emmc
   Backup_Method: dd

/external_sd | /dev/block/mmcblk1p1 | Size: 30161MB Used: 11029MB Free: 19131MB Backup Size: 11029MB
   Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable IsPresent Is_Storage
   Primary_Block_Device: /dev/block/mmcblk1p1
   Display_Name: External SD
   Storage_Name: External SD
   Backup_Path: /external_sd
   Backup_Name: external_sd
   Backup_Display_Name: External SD
   Storage_Path: /external_sd
   Current_File_System: f2fs
   Fstab_File_System: vfat
   Backup_Method: files
   MTP_Storage_ID: 65538

I:Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip)
I:Loading zip theme
I:Loading package: TWRP (/twres/ui.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/cz.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/de.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/el.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/es.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/fr.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/hu.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/it.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/nl.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pl.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pt_BR.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pt_PT.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/ru.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sk.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sl.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sv.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/tr.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/uk.xml' directlyparsing languageFileparsing languageFile done
I:PageManager::LoadFileToBuffer loading filename: '/twres/ui.xml' directly
I:Checking resolution...
I:Scaling theme width 0.666667x and height 0.791667x, offsets x: 0 y: 0 w: 0 h: 0
I:Loading resources...
I:Failed to load image from indeterminate013, error -1
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Including file: /twres/portrait.xml...
I:PageManager::LoadFileToBuffer loading filename: '/twres/portrait.xml' directly
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page main
I:Loading page main2
I:Loading page install
I:Loading page flash_confirm
I:Loading page flash_zip
I:Loading page flash_done
I:Loading page flash_sleep_and_reboot
I:Loading page flashimage_confirm
I:Loading page clear_vars
I:Loading page reboot_system_routine
I:Loading page confirm_action
I:Loading page action_page
I:Loading page singleaction_page
I:Loading page action_complete
I:Loading page filecheck
I:Loading page rebootcheck
I:Loading page appcheck
I:Loading page wipe
I:Loading page advancedwipe
I:Loading page formatdata
I:Loading page formatdata_confirm
I:Loading page checkpartitionlist
I:Loading page partitionoptions
I:Loading page refreshfilesystem
I:Loading page selectfilesystem
I:Loading page backup
I:Loading page backup_options
I:Loading page backupname1
I:Loading page backupname2
I:Loading page backupencryption
I:Loading page backupencryption2
I:Loading page checkbackuppassword
I:Loading page backup_run
I:Loading page restore
I:Unable to open '/data/media/0/TWRP/BACKUPS/Redmi_A'
I:Loading page restore_read
I:Loading page restore_decrypt
I:Loading page try_restore_decrypt
I:Loading page restore_select
I:Loading page renamebackup
I:Loading page restore_run
I:Loading page mount
I:Loading page usb_mount
I:Loading page usb_umount
I:Loading page system_readonly_check
I:Loading page reboot
I:Loading page rebootapp
I:Loading page system_readonly
I:Loading page settings
I:Loading page settings_timezone
I:Loading page settings_screen
I:Loading page settings_vibration
I:Loading page settings_language
I:Loading page copylog
I:Loading page advanced
I:Loading page partsdcardsel
I:Loading page partsdcardcheck
I:Loading page partsdcard
I:Loading page htcdumlock
I:Loading page repackselect
I:Loading page repackconfirm
I:Loading page lock
I:Loading page filemanagerlist
I:Loading page filemanageroptions
I:Loading page choosedestinationfolder
I:Loading page filemanagerrenamefile
I:Loading page filemanagerrenamefolder
I:Loading page filemanagerchmod
I:Loading page filemanagerconfirm
I:Loading page filemanageraction
I:Loading page decrypt
I:Loading page decrypt_pattern
I:Loading page trydecrypt
I:Loading page terminalcommand
I:Loading page sideload
I:Loading page fixcontexts
I:Loading page slideout
I:Loading page select_storage
I:Loading page select_language
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
Startup Commands:
ro.boottime.adbd=3507457029
ro.boottime.init=3078
ro.boottime.init.selinux=111
ro.boottime.init.cold_boot_wait=181
ro.boottime.logd=3484639790
ro.boottime.ueventd=3290798384
ro.boottime.qseecomd=3514871769
ro.boottime.recovery=3488612394
ro.boottime.keymaster-4-0=3581855571
ro.boottime.gatekeeper-1-0=3582846248
ro.boottime.servicemanager=3583835988
ro.boottime.set_permissive=3487782759
ro.boottime.hwservicemanager=3476452186
ro.config.ringtone=omni_ringtone1.ogg,omni_ringtone1.ogg
ro.config.alarm_alert=omni_alarm1.ogg
ro.config.notification_sound=omni_notification1.ogg
dalvik.vm.isa.arm.variant=cortex-a15
dalvik.vm.isa.arm.features=default
dalvik.vm.dexopt.secondary=true
dalvik.vm.usejit=true
dalvik.vm.lockprof.threshold=500
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.appimageformat=lz4
dalvik.vm.usejitprofiles=true
dalvik.vm.stack-trace-dir=/data/anr
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.image-dex2oat-filter=verify-at-runtime
dalvik.vm.dex2oat-minidebuginfo=true
debug.atrace.tags.enableflags=0
ro.art.hiddenapi.warning=1
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.opa.eligible_device=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.boot.dp=0x0
ro.boot.emmc=true
ro.boot.efuse=1
ro.boot.console=ttyMSM0
ro.boot.selinux=permissive
ro.boot.baseband=msm
ro.boot.configfs=true
ro.boot.dtbo_idx=6
ro.boot.hardware=qcom
ro.boot.keymaster=1
ro.boot.bootdevice=7824900.sdhci
ro.boot.secureboot=1
ro.boot.avb_version=1.1
ro.boot.usbconfigfs=true
ro.boot.verifiedbootstate=orange
ro.omni.device=olivelite
ro.omni.version=9-20191120-olivelite-HOMEMADE
ro.omni.version.security_patch=
ro.twrp.boot=1
ro.twrp.version=3.3.1-milankragujevic_9.0_v1
ro.vndk.lite=true
ro.vndk.version=28
ro.wifi.channels=
ro.allow.mock.location=1
ro.build.id=PQ3B.190801.002
ro.build.date=Wed Nov 20 16:49:01 CET 2019
ro.build.date.utc=1574264941
ro.build.host=milan-laptop
ro.build.tags=test-keys
ro.build.type=eng
ro.build.user=milan
ro.build.flavor=omni_olivelite-eng
ro.build.display.id=omni_olivelite-eng 9 PQ3B.190801.002 eng.milan.20191120.164901 test-keys
ro.build.product=olivelite
ro.build.selinux=1
ro.build.version.sdk=28
ro.build.version.base_os=
ro.build.version.release=9
ro.build.version.codename=REL
ro.build.version.incremental=eng.milan.20191120.164901
ro.build.version.preview_sdk=0
ro.build.version.all_codenames=REL
ro.build.version.security_patch=2099-12-31
ro.build.version.min_supported_target_sdk=17
ro.build.description=omni_olivelite-eng 9 PQ3B.190801.002 eng.milan.20191120.164901 test-keys
ro.build.characteristics=default
ro.bionic.ld.warning=1
ro.kernel.android.checkjni=1
ro.secure=0
ro.treble.enabled=true
ro.zygote=zygote32
ro.product.cpu.abi=armeabi
ro.product.cpu.abilist=armeabi
ro.product.cpu.abilist32=armeabi
ro.product.cpu.abilist64=
ro.product.name=omni_olivelite
ro.product.brand=Xiaomi
ro.product.model=Redmi (A
ro.product.device=olivelite
ro.product.locale=en-US
ro.product.manufacturer=Xiaomi
ro.baseband=msm
ro.bootmode=unknown
ro.hardware=qcom
ro.revision=0
ro.services.whitelist.packagelist=com.google.android.gms
ro.bootimage.build.date=Wed Nov 20 16:49:01 CET 2019
ro.bootimage.build.date.utc=1574264941
ro.bootimage.build.fingerprint=Xiaomi/omni_olivelite/olivelite:9/PQ3B.190801.002/milan11201649:eng/test-keys
ro.bootloader=unknown
ro.debuggable=1
ro.modversion=OmniROM-9-20191120-olivelite-HOMEMADE
ro.setupwizard.enterprise_mode=1
ro.property_service.version=2
ro.control_privapp_permissions=enforce
ro.actionable_compatible_property.enabled=false
init.svc.adbd=running
init.svc.logd=running
init.svc.ueventd=running
init.svc.qseecomd=running
init.svc.recovery=running
init.svc.keymaster-4-0=running
init.svc.gatekeeper-1-0=running
init.svc.servicemanager=running
init.svc.set_permissive=stopped
init.svc.hwservicemanager=running
twrp.crash_counter=0
twrp.action_complete=0
crypto.ready=1
tombstoned.max_tombstone_count=50
sys.usb.ffs.ready=1
ro.build.fingerprint=Xiaomi/omni_olivelite/olivelite:9/PQ3B.190801.002/milan11201649:eng/test-keys
hwservicemanager.ready=true
log.tag.stats_log=I
ro.logd.size.stats=64K
ro.persistent_properties.ready=true
pm.dexopt.boot=extract
pm.dexopt.ab-ota=speed-profile
pm.dexopt.shared=speed
pm.dexopt.install=speed-profile
pm.dexopt.inactive=verify
pm.dexopt.bg-dexopt=speed-profile
pm.dexopt.first-boot=extract
ro.boot.serialno=39b2a4210606
ro.serialno=39b2a4210606
service.adb.root=1
net.bt.name=Android
net.tethering.noprovisioning=true
sys.usb.state=mtp,adb
sys.usb.controller=msm_hsusb
persist.sys.usb.config=adb
persist.sys.dalvik.vm.lib.2=libart.so
persist.sys.disable_rescue=true
sys.usb.config=mtp,adb
ro.vendor.build.security_patch=2099-12-31
vendor.sys.listeners.registered=true
ro.crypto.type=file
ro.crypto.state=encrypted

SELinux contexts loaded from /file_contexts
Full SELinux support is present.
tw_get_context got selinux context: u:object_r:media_rw_data_file:s0
I:Got default contexts and file mode for storage files.
I:TWFunc::Fixup_Time: Pre-fix date and time: 1970-05-31--06-29-29
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: no ats files found, leaving untouched!
I:Copied file /cache/recovery/log.gz to /cache/recovery/last_log.gz
I:Attempt to load settings from settings file...
I:InfoManager file '/data/media/0/TWRP/.twrps' not found.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/Redmi_A'
I:Mount: Unable to find partition for path '/etc'
I:Copied file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:TWFunc::Set_Brightness: Setting brightness control to 2047
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
parsing languageFile
parsing languageFile done
I:Translating partition display names
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/Redmi_A'
I:Starting MTP
I:sending message to add 65537 '/data/media/0' 'Internal Storage'
I:Message sent, add storage ID: 65537 '/data/media/0'
I:sending message to add 65538 '/external_sd' 'Micro SD card'
I:Message sent, add storage ID: 65538 '/external_sd'
MTP Enabled
I:[MTP] Starting MTP
I:Switching packages (TWRP)
I:Set page: 'system_readonly'
I:[MTP] created new mtpserver object
I:[MTP] mtppipe add storage 65537 '/data/media/0'
E:[MTP] Failed to start usb driver!I:[MTP] mtppipe add storage 65538 '/external_sd'
I:operation_start: 'Toggle System Mount'
I:operation_end - status=0
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
I:Starting Adb Backup FIFO
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 2047
I:Set page: 'advanced'
I:Set page: 'filemanagerlist'
I:Set page: 'filemanageroptions'
I:Set page: 'filemanagerlist'
I:Set page: 'advanced'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
E:[MTP] request read returned -1, errno: 5I:Set page: 'install'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 2047
I:Set overlay: ''
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0

```

# Answer
> 3 votes
I was in a similar issue on a Nokia running a stock ROM. Basically Magisk module killed my phone and the TWRP won't allow decryption.

I was able to boot successfully to system again by.. Removing Magisk, because in the absence of Magisk, the Magisk modules shouldn't load and hence the system should boot just fine. I did that by flashing my stock boot image. Then I took a backup and did a reset.

You didn't specify which device you're using. But on an A/B device you can flash your original boot image from Havoc (from the exact same build you're currently on -- in case you installed any updates) on the active boot slot (double check that the boot slot didn't change while phone was trying to boot and fell back to the other slot when the active couldn't boot.

For the boot image, it is important for it to be from the exact same build, except the mismatched "Android OS level and OS version" can cause the phone to not boot.

---
Tags: twrp, data-recovery, fastboot, encryption, partitions
---


# Question
Title: How do I undo "always show pictures from this sender" on Android gmail?
I accidentally clicked 'Always Display Images from This Sender' ('Always show pictures from this sender' in 2020) and was wondering if there's a way to undo this setting in Android gmail.

It's straightforward to undo on web Gmail, but not the same with Android (that I know of). Any help is appreciated!

# Answer
In the Android Gmail app,

From the main inbox or inside any email: Bring up the Menu \> Settings \> General Settings. Now click the Menu button again to bring up sub-menu of options \> Clear picture approvals.

**WARNING**: This clears ALL your approved sender settings, I believe there is no option to revoke by individual email senders.
> 62 votes

# Answer
I needed to clear this setting for a single email address. I followed these steps:

1. Open Gmail (mail.google.com) in a web browser
2. Open an email from the sender which *has* an image in it
3. In the top left of the email it will have the sender's name and below that "*to me*" with a little down arrow next to it
4. Click the little down arrow and then click *Don't display from now on*
> 30 votes

# Answer
If you do it from from gmail you can do it on a by sender basis. Here are the instructions: https://productforums.google.com/forum/#!topic/gmail/v0rJQjdR-Pc

> click show details then click Images from this sender are always displayed. Don't display from now on.
>
> NOTE YOU WILL ONLY SEE THAT OPTION IF THERE ARE EXTERNALLY LINKED IMAGES - NOT IF THERE ARE INSERTED OR ATTACHED IMAGES
> 4 votes

# Answer
In 2020 there is still a working solution to the problem of having accidentally chosen "Always display pictures from this sender" in the Android Gmail app (how I miss Inbox).

Gmail app \> Settings \> General Settings \> Triple Dot Menu \> Clear Picture Approvals.

PS I'm adding my answer here even though it's a partial duplicate of another (with lots of up votes). I ignored the other answer since it referenced a specific version of Gmail from 2013 figuring that it was no longer valid. Hopefully this answer will help others like me who skip the other answer.

FYI If all else fails there is a "nuclear option":

Clear the Gmail app's storage

1. Open System Settings app on Android.
2. Find the Gmail app details where you can clear cache and storage (Settings \> Apps and Notifications \> See all applications \> Gmail on Android 10).
3. Choose "Clear storage".

Your stored accounts should persist but the unintended consequence of this action is that all your Gmail settings customizations like more sensible swipe behaviors will be lost. You have to ask yourself if the cure is worse than the disease.
> 2 votes

---
Tags: gmail
---


# Question
Title: Activate alarm, ringtone or audio using ADB?
I have misplaced a junker phone (LG G3 running Lineage). However, it's still on, and ADB is accessible over TCP/IP. (The phone doesn't have a SIM, so I can't call it.)

Is there a way to turn on the ringer or other audio from ADB? I've tried a couple of remote-screen apps (adb-remote-control.jar and scrcpy) but although they appear to connect, and scrcpy even gets a screen image that looks correct, neither of them seem to send events correctly, so I can't control the phone.

I suspect there's a way to launch an app (Phone? Alarm?) with a "Play Ringtone" intent, but I don't know how.

# Answer
> 1 votes
Suggestion of Google find my phone worked: Google knows where your phone is, even if you don't.

From another user, you can also do it with ADB:

```
adb push t.mp3 /sdcard/
adb shell am start -a android.intent.action.VIEW -d file:///sdcard/t.mp3 -t audio/mp3

```

> (Playing a video file the same way or starting youtube (`adb shell am
>  start -a android.intent.action.VIEW -d
>  https://www.youtube.com/watch\?v\=oVQqmH4ufCQ`)) will not produce any sound if the device is locked it seems like)

---
Tags: adb, alarm, remote-control, ringtone
---


# Question
Title: How to get a list of latest apps released on Play Store sorted by date?
Is there any way to get a list of recently released apps on Google Play Store sorted according to date added?

# Answer
**ShivamSoni**

As **google play store** have **daily adds New Updates** of Apps of thousand/lakhs/millions of new versions all of them are new for Play store .

But still **I searched and founded** links for **new releases** sections for you in **play store website** options. I am **sharing below links** of **website** of new releases and option to search apps latest releases apps category wise. But i dont think its possible to sort all apps list date wise launch option in app or website.

https://play.google.com/store/apps/new?hl=en

https://play.google.com/store/apps/collection/cluster?clp=Si8KKQojcHJvbW90aW9uXzMwMDA3OTJfbmV3X3JlbGVhc2VzX2FwcHMQBxgDOgIIAQ%3D%3D:S:ANO1ljKj5O4&gsr=CjFKLwopCiNwcm9tb3Rpb25fMzAwMDc5Ml9uZXdfcmVsZWFzZXNfYXBwcxAHGAM6AggB:S:ANO1ljILDUU&hl=en

In **Google Play store App version 19.3.36** there are **tabs** named **"for you, Top Charts, Categories....."** tabs of at **very last** there is a tab in last **"Early Access"** which shows latest to be launched beta developing Apps and games.

**There are many 3rd party apps** that you can utilizes to sort and easy your work about **one of popular one i searched** is called **AppBrain App Market**, and can be **downloaded for free** via **Google Play** (see the link at the below). **The best way to find new apps in Google Play.**

https://play.google.com/store/apps/details?id=com.appspot.swisscodemonkeys.apps&referrer=utm\_source%3Dappbrain%26utm\_medium%3Dappbrain\_web%26utm\_campaign%3Dappbrain\_web

**According to appbrain website link says product details says**

https://www.appbrain.com/app/appbrain-app-market/com.appspot.swisscodemonkeys.apps

> **Description**
>
> The best way to find new apps in Google Play (Android market).
>
> Make the Android market usable, and find your next favorite app, live wallpaper or widget: \- App recommendations \- New and hot apps of the day \- Find top Android apps with a price drop \- Share your best apps (eg twitter/facebook) \- Tracks market update: notifies of updates available \- Fast uninstaller \- Browse "my apps" on www.appbrain.com and install apps with a sync instead of barcode scanner \- Keep your list of installed apps as a backup on AppBrain.com
>
> AppBrain is the best way to discover top Android apps in the Android market and to manage your apps. The recommended apps helper provides recommendations based on what you already use. We also have recommended games. It does not work with the Amazon app store.
>
> The manage apps is like a killer file explorer / task manager for your already installed apps: \- Start app, Quick uninstaller, share to Facebook \- Fast sync widget to access AppBrain from the desktop and backup your apps to the cloud \- app2sd functionality to move apps to sd (app 2 sd) \- Find market update: notifies you of any updates available
>
> Discover cool apps and top games in the Android market: \- sort by hot apps today, hot apps this week, highest rated apps, price drops etc \- Filter apps by free apps, paid apps, price reduced apps, app2sd enabled apps, new apps \- Fast search over the entire Android market \- Unlike applanet or black market, these are only legal apps.
>
> AppBrain is the best app market and app discovery tool for Android apps from the Android Market. It allows you to easily find the best apps in the Market, the free apps and downloads, the price drops, live wallpaper, widgets and much more.

Hope this app will help you any further option i will get i will update in the answer.

> Hope my **answer suggestions helped you** if any thing helped you out from your search or my or others help do tell me what **helped you in comments** for my knowledge. if any **doubts or further clarification** feel free to ask and if worked do **not forget to accept and vote for the answer**
> 1 votes

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


# Question
Title: How to continue using an android system with a broken touchscreen?
I have many working android cellphones with broken touchscreen but with a working screen and I would like to use them as computing device and/or additional screen. Is there a way to do that?

# Answer
Provided your device has an unlockable bootloader and a custom recovery (I strongly advice against buying devices which are artificially destined to become useless, that should be prohibited by law), you should.

In any case I advice anyone worrying their device could break anytime to already have unlocked bootloader and activated wifi and adb (through network, if worrying about usb port breaking) at boot. Remember that if you are unlocking your bootloader for the first time doing so WILL DELETE all userdata and if you are not in Europe it could void your warranty.

First of all, proceed to install `fastboot` and `adb` on your pc, connect the device to the pc and then

* unlock fastboot (the bootloader) on the device and flash the TWRP custom recovery (if no custom recovery is available you could somehow extract your base recovery image and enable adb and root access editing its `default.prop`);
* boot recovery and open a shell with `adb shell`;
* find `system` and `userdata` (and probably `boot`) partitions with `fdisk -l /dev/block/mmcblk0`;
* mount `system` with `mount -t ext4 <system_partition_file> <mountpoint>`);
* enabling debug is unnecessary cumbersome if you didn't have already enabled it.

First try adding the following into `system`'s `build.prop`:

```
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1

```

If that didn't work, you could try switching to `1` the `adb_enabled` setting in `<data_partition_mount_point>/system/users/0/settings_global.xml`.

If even that didn't work, then you have to rebuild your `boot` image, properly editing the `default.prop` file to enable adb and then switching the `adb_enabled` setting like above.

You can find information on how to do that here (keep in mind that it will probably require device-specific information like `kernel_offset`, `ramdisk_offset`, `second_offset` and `tags_offset` so you have to find those somewhere first).

+ unmount `system` and mount `userdata`;
    + add your adb server public key (placed into `~/.android/adbkey.pub`) into `userdata`'s `/misc/adb/adb_keys` (with a text editor or any other means) to skip device confirmation;
    + umount `userdata` and reboot the device;

Now that you can connect through adb, install `scrcpy` on your operating system and use the device remotely from your computer.

And if like me you forgot your pin code, you can disable it by moving the files starting with `locksettings` from `/data/system`. Remember that if you are using file-based encryption, moving or directly changing the pin in the sqlite3 database with

```
UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled';

```

will make your encrypted file inaccessible.

### References
> 2 votes

---
Tags: data-recovery, screen, linux, touchscreen, broken-screen
---


# Question
Title: How to get USB file transfer working on Oreo 8.1?
I always used to transfer files between my laptop and Nexus 5X phone. Upon connecting the USB cable, there used to be a notification thingy on my phone showing USB options, which was default on 'Charging' and then when changing that to File Transfer, I could transfer files.

I recently had to reset my phone and now that I have a new, freshly installed Oreo 8.1.0 environment, this USB notification does not appear anymore. And the device does not show up on my laptop at all.

While searching for a solution I came across these suggestions which I already tried:

* Enabling developer mode on Android (clicking 7x on Build number in About).
* In developer options, enable and disable USB debugging.
* Clearing the cache and data storage for the 'External storage' and 'Media storage' apps, and rebooting my phone, and wait for a while.
* In developer options, there is something called "Select USB configuration" which is on "MTP (Media Transfer Protocol)". Changed that to "Charging" or "PTP (Picture Transfer Protocol)" and back.

None of these helped, unfortunately. Any hints?

Note that the cable is fine. It works OK on other phones, and upon connecting my phone to my laptop, it does show the charging indicator in the battery icon. It's just the USB notification and file transfer related options that are no longer there.

# Answer
> 5 votes
Go into Developer options, scroll down to "Select USB Configuration" and select MTP ( Media Transfer Protocol ) even if it's already selected.

This solved the problem for me.

# Answer
> 1 votes
* Go to developer options
* Make sure using "USB Debugging" is disabled
* Set "Always Prompt when connecting to USB" to ON
* Make sure your phone is unlocked when you connect to the PC/Laptop
* Select "File Transfer" in the options.

I learned this from Huawei Support who were very easy to deal with from here in the UK.

# Answer
> 1 votes
For Lineage OS you need to go to Developer options

* disable "USB Debugging"
* scroll down and between "Tethering hardware acceleration" and "Show bluetooth devices without name" you could find
* "Select USB Configuration" and press it.

That's it. but my phone showed me the Internal storage only after I picked up PTP first, tried to extract images (unsuccessfully) and when I returned back to MTP everything was OK .

# Answer
> 1 votes
The old menu which used to be available from the charge notification is now well buried (Moto G5) at:

System → Settings → Connected devices → USB → Transfer files.

# Answer
> 0 votes
Go to developer options\> enable usb debugging \> click Revoke USB debugging authorisations Press and hold down power+volume up until phone vibrate and restart. After that the problem should be solved. But remember, this is not a permanent solution.

# Answer
> 0 votes
Under settings did you go to Connected Devices and you will see USB listed there.

Also for the notification not showing anymore, under settings, go to Apps and notifications \> Notifications \> Notifications again and at the top right click the 3 dots menu and select "Reset App Preference"

This way any notifications won't be blocked from showing and when you attach the USB it should come up again

# Answer
> 0 votes
For me it was an hardware problem. The usb cable I was using was able to charge the phone but for some unknown reason it didn't work for the transfer.

I changed cable and suddendly it worked flawless..

---
Tags: usb, file-transfer, 8.1-oreo
---


# Question
Title: Merging whatsapp database of two different accounts
So, I have two WhatsApp accounts `A` and `B`. `A` has chat history only till December '19 while `B`'s chat history start from January '20. I want to have one account with mobile number that of `A`, groups of `B` and chat history combined. For that I plan to

1. Somehow introduce `A`'s chat history to account `B` by modifying Whatsapp databases.
2. Then doing a change number of `B` to `A`. (This step will delete old `A` account)

I want help with the first step.

PS: I have looked online on how to merge Whatsapp databases but they all address merging databases of same account here I have to different accounts and also all articles on it are really old.

# Answer
Merging two different account in whatsapp is not possible, when you change the number, all your groups will remain same but it can not merge two accounts. Whatsapp backup or restore the chat on the bases of phone number only,when you start new number, it can not recognize it as same account.
> 1 votes

---
Tags: whatsapp-messenger, sqlite, chat-history
---


# Question
Title: Fastboot detects phone in the fastboot mode but not when phone is on
I'm trying to flash a custom recovery image with `fastboot flash recovery recovery.img` but it can't find the image, hence I'm powering it on and getting into location where the image is to execute the command. The problem is fastboot doesn't detect the phone when the phone is on but ADB does detect it. How can I troubleshoot this ?

# Answer
Fastboot images have to be stored on the PC where you execute the fastboot command not on the device.

Therefore the common process is:

1. PC: Download the image to be flashed
2. Boot the device into bootloader/fastboot mode
3. Connect the device to the PC via USB
4. Execute on the PC `fastboot flash <target_partition> <path to the image on the PC>`

Flashing firmware images that are stored as image file on the device is usually a job for a recovery ROM such as TWRP.
> 1 votes

---
Tags: adb, fastboot
---


title: Enabling Multi User Feature on Realme 3

text:
# Question
Title: Enabling Multi User Feature on Realme 3
Can anybody help me with enabling the multiple user feature like stock Android without rooting. I've tried getting the default.prop through adb and changing some properties and then replacing the copy on the phone with that but it wouldn't let me, cause my phone is not rooted and it's telling that I don't have permission. I don't wanna try rooting the phone just yet, cause it's a relatively new unit.So there's probably no stable root guide for it yet and so I don't wanna accidentally hard brick my phone.

Please somebody help me with this.If you have any suggestions and thank you in advance.

# Answer
> 1 votes
No, multi user feature is not available in Realme 3 containing Coloros 6.And you cannot enable it without rooting. Realme 3 is based on Mediatek chipset, so you will not get good support for third party ROMs. But in future this phone will get RealmeUI update, which may bring multi user feature.

---
Tags: rooting, multi-user, oppo-coloros
---


# Question
Title: How does Android know my password contains only numbers?
My Android phone's unlock type is set to a password, but it only contains numbers for fast unlocking (I'm well aware that a PIN is an option, but this way presents more possibilities to an attacker). My phone's USB storage is encrypted so that I must enter my password on boot, and when I do, I am provided with a numerical-only keyboard. How does my phone know that my password only contains numbers? Does it store the password in plain text?

# Answer
Your password certainly shouldn't be being stored in plain text, although without reviewing the exact software your phone is running I can't rule the possibility out. More likely, when you set the password, it checked which characters are used and set a flag (in the plain-text portion of the system where the boot code and device unlock functionality live) indicating which keyboard type was most suitable. It probably *shouldn't* do that, but it could reasonably be described as a convenience feature.

Alternative explanation: are you 100% sure that, when you set your password, you did it in a way that allowed setting non-numeric characters? Maybe you have a PIN by accident. Try changing your password, and see what keyboard it gives you. If it's the full keyboard that you expect, that's an argument for the "sets a flag" theory. Try adding a single letter or symbol the the password and seeing if it changes the keyboard presented when unlocking.
> 5 votes

---
Tags: security, password, password-protection
---


# Question
Title: How to remove X button on video overlay?
YouTube version 15.08.52 on Android 5.0.1 (Lollipop) is showing a X button on the video overlay user interface and it has to be tapped to hide the UI.

I searched on the internet and some posts say it's because the accessibility options "Switch Access" and "Accessibility Menu" are turned on, but in my case, the setting Switch Access is off and there is no option for Accessibility Menu.

How can I disable the option to show the X button so that the UI is hidden automatically?

# Answer
1. Open YouTube
2. Click on your picture on the top-right corner
3. Click on settings
4. Click on Accessibility
5. Disable the thing.
> 1 votes

---
Tags: 5.0-lollipop, youtube
---


# Question
Title: Creating and flashing image to Android device
I have created an image of my Android device (Lenovo A6000) using the command

```
adb shell -c su 'dd if=/dev/block/mmcblk0p23 > data.img'

```

Now I would like to flash this image to the same device, and I am trying to accomplish this using fastboot in the following way

```
sudo fastboot flash data data.img

```

I am using the latest version of fastboot shipped with Android's SDK.

Doing the above command I get the error

```
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk:
don't care size 4894735982 is not a multiple of the block size 4096
fastboot: ../libsparse/sparse.c:143:
           write_all_blocks: Assertion `pad >= 0' failed.

```

I suspect it has something to do with the sizes, the image appears to have size ~5GB while the reported max download size appears to be ~2GB.

But I am not sure what the real error is and how to fix it?

Can someone tell me where the mistake is and how to solve it? It seems that if I make a smaller image I can flash it properly.

# Answer
> 2 votes
Android fsutils (on Ubuntu) comes with tools you need. You can also find them on GitHub. You need: `simg2img`, `simg2simg`, `img2simg`, `make_ext4fs`, and some terminal knowledge.

`sudo simg2simg ./data.img ./data.raw.img`

This gives you an image that can be mounted on Linux. To mount it, create an empty folder, then issue command...

`sudo mount -t ext4 -o loop ./data.raw.img [new_folder_name]/`

You can the find all the files in the folder you created. When you're done with the changes you want to make. Use this to make an Android image for fastboot.

`sudo make_ext4fs -s -l [size_of_partition_in_bytes] -a data ./data data_new.img`

The output will be the file data\_new.img. Then you just use fastboot to flash like you normally would.

# Answer
> 0 votes
You can try this command from `adb shell`:

```
cat /proc/partitions

```

But `mount` lets you see `/dev/block/bootdevice/by-name/` (in my case).

So if you do:

```
ls -al /dev/block/bootdevice/by-name/

```

You have all blocks you want to add.

But I'm still searching for how to add straight to a computer instead of an SD card.

---
Tags: rom-flashing, fastboot
---


# Question
Title: Install custom system, on unlocked bootloader
I have buy a china device. and i will install custom ROM / system Name of Phone:

**MYCELL i11 pro**

ebay: https://www.ebay.com/itm/i11Pro-6-1-8GB-128GB-Smartphone-Android-9-1-Dual-SIM-Mobile-Cell-Phone-Unlocked/402019064450?ssPageName=STRK%3AMEBIDX%3AIT&var=671879680646&\_trksid=p2057872.m2749.l2649

I have unlocked the boot-loader And i have take backup of ROM/Firmware.

I use (SP\_Flash\_Tool-5.1916\_Linux) to flash new system.img. But then i do that i got stuck on boot logo, then i flash back to official ROM, so i can run the phone again.

My question is how i can install another firmware to the phone. Any one can help me ?

Thanks for your time

# Answer
> 0 votes
I got it to work with install another system on the phone !

Model phone MT6570

```
step 1:
Download: https://www.needrom.com/download/blu-studio-j2-s590q-2/
step 2:
Format the hole phone (with MT6570_Android_scatter) from step 1
step 3:
Load the new (MT6570_Android_scatter.txt) from the step 1
step 4:
From the real Firmware (https://www.needrom.com/download/i11-pro/)
step 5:
Change the real preloader, lk, boot, recovery, logo, md1img, secro, cahce, userdata
step 6:
Load the system.img from step 1
step 7:
Wait for boot up

```

Hope the helps other :)

It works for me !

---
Tags: rom, device-firmware, mediatek
---


title: Android: the print quality is bad

text:
# Question
Title: Android: the print quality is bad
we have a problem with Android printing. The print qualitity is bad.

* The font has podium on the edge
* "Gaps" in the font inside
* broken lines

**We have the following printers:**

* Samsung Xpress M2026W
* Brother HL-L2350DW

The connection is made via WLAN.

**We tried the following variant:**

* Samsung & Brother Print Service:
    + via external Apps (Adobe Reader)
    + our own native App (printerHelper, printManager, ...)
* Samsung Mobile Print App:
    + Direct call and print of a PDF / image (JPEG / PNG)
    + Call through our app with explicit intent
* Samsung Cloud Print
* Brother Mobile Print App:
    + Direct call and print of a PDF / image (JPEG / PNG)

The only variant with good print is printing with a desktop PC (Windows 10, Ubuntu 14.04 and 18.04)

So there is generally no Problem with the printers.

It was tested on Android 6, 7, 8 & 9 and many tablets and smartphones (LG, Lenovo, Nexus, Pixel and Huawei)

To exclude images and fonts that could cause problems, we also tested third-party PDFs and docx with Arial.

Are there solutions to that? Be it settings (Android, manufacturer App or printer) or programmatic solutions? We would be so far, the printer directly address, if this is possible?! Also, we could imagine hiring consulting firms, if anybody knows any on this topic?

# Answer
> 3 votes
I had the same problem when printing from android to my Brother HL-2340D. My prints included a barcode which couldn't even be scanned when printed from my android-device. What I did to fix it was downloading Brother Print Service Plugin With this installed you get a new option in the list of printers. With this one there's a new button in the print-settings, "MORE OPTIONS" pressing this takes you to a new with 2 more settings, 1 being Quality. The options there are "Normal", "Fine", "Best" with the default being "Fine". This prints in about the same quality as without the plugin. Maybe a tad better. "Best" prints in about the same quality as the default settings on my pc, which is 600 DPI.

Oh, and the "Normal" option is anything but normal.

---
Tags: printing
---


# Question
Title: How to give permission to record video in DU Recorder app?
Can someone tell me how can I enable this permission that is being asked in the screenshot below?

# Answer
> 1 votes
Go to Settings, Apps, and then find your app. Inside there should be a list of permissions. Enable the ones that are disabled.

# Answer
> 1 votes
Disable "Display over apps" for the DU Recorder app from the phone settings. That worked for me.

---
Tags: permissions, video
---


# Question
Title: How to inspect HTTPS traffic of a third-party app on Android 9+
I want to inspect inside HTTPS-encrypted packets that an app is sending. It is not my app, I don't have its source code.

My device is rooted, so I can modify `/system/etc/security/cacert` if needed, for instance to do man-in-the-middle proxying.

Up to Android 8, one could just install a self-made certificate, but it does not work anymore. I have Android 9, but I can upgrade if needed.

# Answer
As tipped by @beeshyams, HttpCanary is perfect for this.

You need a rooted device, of course.

HttpCanary takes care of all of the difficult steps (certificate generation and installation) transparently.

It shows a list of requests (filterable by app), and details of each request and response.

The best feature is this overlay showing request while I am using other apps (bottom right):

Even though the Google Play page says "*HttpCanary core codes are opened in Github*", https://github.com/MegatronKing/HttpCanary does not contain most of the source code, so I believe it is not open source.
> 1 votes

---
Tags: proxy, troubleshooting, certificates, https, debug
---


# Question
Title: Is it possible to access another partition from recovery partition using command line?
Here's a situation: I've got Meizu 5 pro flashed with Flyme 6 which I flashed using TWRP recovery. I made few tweaks of the partitions (deleting and recreating and renaming) and then I wiped data.

Now the phone boots but as soon as it hits main interface I get error saying "internal storage is running out the process has been stopped" then it reboots and starts over, hits the message, reboots, starts over .... stays in this loop.

I still have access to:

* Meizu's recovery mode (which is kinda useless if I can't access root directory)
* locked fastboot mode (also little bit useless if it's locked)
* recovery partition through USB

I also have MRT dongle for repairing Chinese phones but it doesn't seem to work unless the phone boots fully into Android.

What I can do about this ? Any help much appreciated.

# Answer
The answer is no. The partition will show up as a root directory in command line interface. The same goes when trying to browse the partition with Python.
> 1 votes

---
Tags: rom-flashing, recovery-mode, custom-roms
---


# Question
Title: What feature of Android provide security to reset the /system changes on reboot?
I am stuck in a weird situation where I have two Android 10 phones from Samsung. I have rooted the stock recovery of both device as instructions given here. The problem is when I change something via recovery like create a new /system/etc/init/custom.rc file then on One device it persist on /system after reboot but on another it doesn't. The changes does persist when I reboot to recovery back.

I want to understand which layer of Android applied this feature:

* Kernel
* Stock recovery
* System
* or another

Any suggestion? and how to fix it?

# Answer
> 1 votes
Removing `avb` checks form `boot.img/ramdisk/fstab.qcom` has fixed the issue.

---
Tags: twrp, system, kernel, systemless-root, init.d
---


# Question
Title: Samsung (Galaxy S4) does not show Authorize USB debugging dialog box
I am trying to follow the instructions here, but my phone never displays the "Authorize USB Debugging" option.

On the PC side, `adb devices` shows that the PC see the device, but it is listed as "offline" and I cannot use `adb shell` to talk to it.

Moreoever, if I unplug the device, `adb devices` does not list it at all, so I assume that the adb server is able to see the phone and simply cannot talk to it.

**How can I force the "Allow USB Debugging" to appear on the phone?**

I have already tried restarting both devices and disabling and enabling USB debugging on the phone.

# Answer
> 28 votes
I have had this happen multiple times on multiple Android devices. Solved every time by putting the device in Photo transfer (PTP) mode.

ADB will not work for me when my device is in MTP or any other mode.

# Answer
> 12 votes
My SAMSUNG Galaxy S4 sometimes bothers me with this annoying offline status message too. I always fix it by trying options below:

* Try to **revoke the USB Debugging authorization** on `Developer Options` menu.
* Try using `adb kill-server` and the `adb usb` commands.
* Try to **replug your device** if none of above works.
* Try **Restarting your device**.
* Turn *USB Debugging* **OFF** and **ON** again.
* Try to Turn *Developer Options* **OFF** and **ON** again.

hope it hepls.

# Answer
> 8 votes
I am not sure if you ever solved this problem, but I ran into this problem, and tried out many many different procedures, each of which might have helped others, but this is 2016 and a summary might help.

A brand new phone bought in 2016 didn't work when I installed Android Studio on Linux. A phone bought in 2015 worked without a problem. A new phone didn't work with the exact same configuration.

When I have Android Studio open, the AVD manager didn't show the new phone, but showed the old one. The old phone, when connected on the USB plug, threw a dialog asking me to confirm the fingerprint of the RSA key, but the new phone didn't show the same dialog when connected.

I found a tip at https://stackoverflow.com/questions/18011685/cant-connect-nexus-4-to-adb-unauthorized and tried it out and it worked for me.

I removed two files adbkey and adbkey.pub from ~/.android. Apparently android-studio detects this and creates the keys immediately. As soon as this occurs, the new phone threw the dialog open and started working. I am able to see the phone on the Android-Studio's AVD menu and start running the applications.

adb version 1.0.31, BUT, if I try to run 'adb devices' on the command line, Android-Studio stops showing this phone on the AVD menu.

I still don't see the phone (but that does not bother me as I am able to see the phone from the AVD menu). adb command line utility only showed an emulator that was running, but not the phone connected in debugging mode, one that was seen on the AVD menu, up until the command was run.

```
$ adb devices
adb server is out of date.  killing...
* daemon started successfully *
List of devices attached
emulator-5554   device

```

At this point, reconnecting the phone does not help. AVD menu only showed the emulator that was still running on my computer.

You have to run 'adb kill-server'. Once that is done, and if you open up the AVD menu, Android Studio initializes its own ADB and the phone shows up on the AVD menu.

adb version 1.0.31 Android Studio 2.1

So in summary: two things.

1. Delete adbkey and adbkey.pub from ~/.android while Android Studio is open.
2. Do not run command line utility adb. It messes with the server instance run by Android Studio. The server instance from commandline works for some phones but not all. Android-Studio works with all the phones I have.

All the above is of course after making sure:

* you tap the 'build number' thing 7 times and enabling the USB debugging mode...
* tried 'revoking the debug permissions' many times
* tried rebooting the phone a few times
* enable/disable/enable usb debugging mode,

All the above steps seemed like voodoo things to try, but essentially they didn't work, except the ones I listed above.

(Update: Adding this line that was originally a comment, but belongs in the answer).

I also had to add the new phone's vendor ID to /etc/udev/rules.d/51-android.rules file to help identify the new phone and to set the permissions.

# Answer
> 3 votes
I just had this happen to me. Debugging was working fine at the office, but broken at home.

Turned out to be my usb cable. Everytime I plugged it in, it would charge but I never received the Allow USB Debugging prompt.

I tried a second cable, same thing.

Third cable was the charm, worked fine with a better cable.

# Answer
> 1 votes
## I required "Default USB configuration" to be set to "MIDI"

Windows 10, current as of 24 June 2019. Samsung Galaxy S8 plus.

After 6 months of trying random things and being frustrated I figured it out today!

Of course I had done the obviously necessary steps:

a. On the phone, enable USB Debugging through Developer Options: https://stackoverflow.com/questions/18103117/how-to-enable-usb-debugging-in-android

b. On the computer, install the appropriate "OEM USB driver" for your phone manufacturer: https://developer.android.com/studio/run/oem-usb.html#Drivers

I did those a long time ago, but only recently managed to get the following two things right:

### 1. Important to choose the right USB cable

A cable might work wonderfully for charging your phone from your laptop, but not work for data transfer (because different pins are used for these purposes). An easy way to check that you have the right cable, set your phone's "Default USB Configuration" in Developer Settings to "Transferring files".

You should be able to see your phone and its contents in Windows File Explorer.

### 2. Set your phone's "Default USB Configuration" to "MIDI"

Over the last few months' annoyance, I never tried this. Why the hell would that be right?! Today by chance I tried it. I got the "Allow USB debugging?" prompt rather than the "Allow access to phone data?" that we get when connecting with the other USB configurations.

On the Chrome Dev Tools "Remote Devices" panel, within 1 or 2 seconds the phone shows up. Hooray!

This is reproducible, i.e. when you keep computer and phone connected, and flick between the settings of "Default USB configuration", the phone appears and disappears from Chrome Dev Tools Remote Devices, within a second or two. Only appears when phone is set to "MIDI".

On the Chrome Dev Tools "Remote Devices" panel, within 1 or 2 seconds the phone shows up. Hooray!

### \[edit\] 3. You might have to set it away from MIDI and then back to MIDI

I have found a few times that it stops working inexplicably, but it can be fixed by going to Developer Options, setting to something *other than* MIDI, waiting for the "pling plong" sound from your Windows computer, and then set it back to MIDI.

# Answer
> 1 votes
If it shows Unauthorized but if you do not see the RSA prompt on the phone, do the following.

Linux

```
which adb

```

Windows

```
where adb

```

Identify all the duplicate entries in the path. Remove duplicates.

Now do

```
adb kill-server
adb start-server

```

# Answer
> 0 votes
I had to delete the adbkey from /data/misc/adb on the phone and then

In adb shell type \> adb kill-server In adb shell type \> adb start-server

Now connecting the USB cable brought back the options. For some strange reason I revoked the authorization and been spending hours to get it back..

Thanks..

# Answer
> 0 votes
I've had the same issue and it turned out that having the USB mode set to file transfer instead of charging caused my issue. As soon as I set it to charging mode, it fixed my problem and I was prompted for debugging.

# Answer
> 0 votes
My problem came down to that I did not have the ADB (Android Debug Bridge) installed on my computer.

I followed the instructions here, and actually downloaded it here. Once I installed the ADB onto my computer, I ran the commands: `adb kill-server` and then `adb start-server`.

After doing all this, my root finally worked! I'm not sure if the `adb` steps are necessary, but I went ahead and performed them. Then when I reconnected my phone, the dialog for giving my computer permissions actually popped up and I was able to root.

# Answer
> 0 votes
This answer is for anyone currently facing this horrendously annoying problem (2019+)

Here are some general stuff to try out:

If you've tried and failed for about 5 hours with the above techniques, you can work your way to a custom solution that helped me. Or you can take a look at the question I asked directly.

> It seems like the profile of the computer(perhaps the RSA key fingerprint) was automatically recognized by the android device and so it didn't ask for any permissions. From there, I'm still kind of trying to understand it. But basically, as soon as I reset(factory reset) my computer, it started prompting me for authorization again. I'm sure the factory reset was on the extreme end of options, but it worked in the end.

# Answer
> 0 votes
This is what worked for me:

1. Delete `adbkey` and `adbkey.pub` files from `~/.android` folder
2. run `adb kill-server`
3. run `adb usb`

# Answer
> 0 votes
Dont't forget to install `adb` for this to work.

For Debian/Ubuntu it's as simple as:

```
sudo apt install adb

```

# Answer
> 0 votes
Try to install Android USB Driver for your OS. Here is the Samsung one for Windows machines:

https://developer.samsung.com/mobile/android-usb-driver.html

---
Tags: adb, samsung-galaxy-s-4, chrome-for-android, usb-debugging, samsung-galaxy-s-8
---


# Question
Title: Disable "DeX on PC" notification each time S10 connected to PC
Since a recent update (I can't say exactly which or when) each time I connect my Samsung S10 to my PC, I get a `Samsung DeX` notification...

I don't want DeX, but I do want to get rid of the notification every time I connect my phone.

Is it possible disable/remove the notification? The `app notifications` is not giving me the slide-switch option to disable it...

# Answer
> 9 votes
If you would rather remove Dex from your phone instead of disabling it, and you have ADB and USB debugging setup, you can remove it with this command:

```
adb shell "pm uninstall -k --user 0 com.sec.android.app.dexonpc"

```

# Answer
> 2 votes
Open Settings, go to Apps. Press the three dot symbol, and tap "show system apps". Then go to Dex for PC, tap storage, clear cache. Go back one screen, tap Force stop and Disable. You might have to repeat this after reboot or software upgrade, haven't tested that.

---
Tags: notifications, samsung-dex
---


# Question
Title: Gifted Android Huawei Media Pad hard reset not working, what to do?
I was gifted a Huawei Media Pad, Model BG2-W09, from an elderly woman who no longer used it, and have factory reset, and tried to hard reset it to no avail. I would like to use it, but the how-to guides have all failed me. Please advice, ladies and gentlemen. it would be greatly appreciated!

# Answer
> 0 votes
HardReset.info: Afterwards press and hold the Volume Up + Power button at the same time for a few seconds.Wipe data on HUAWEI MediaPad T3 7

Relase held keys as soon as the Huawei logo appears on the screen. Use the Volume buttons to scroll to "wipe data/factory reset" and confirm that option with the Power button.Format HUAWEI MediaPad T3 7 Once more choose "wipe data/factory reset" from the menu and accept it with Power key.Restore HUAWEI MediaPad T3 7

Now accept option "reboot system now" by using Power button.Master Reset HUAWEI MediaPad T3 7 The factory reset will be completed as soon as the HUAWEI Welcome Panel shows up. Congratulations! You have just performed the hard reset operation

---
Tags: huawei
---


# Question
Title: Disable email sync outside working hours
Is there any way or a mail app where I can set a (per account) sync time? I would like the app to only ***fetch*** mails from my (work) account Mo-Fri 9-5 or if I manually sync.

I use k-9 mail since I got my first Android phone and it has a "quiet time" feature. But this seems somewhat broken in recent Android versions and I would like to have something even more aggressive if possible so I can set the app to not even download new emails from my email account at certain times.

Android version 8 (phone) and 9 (tablet).

# Answer
> 1 votes
FairEmail is a popular open source Email client (crossed 100,000 downloads) which can do this for *all accounts (global)* but *not per account*. This is because of maintenance and support of app plus battery consumption.

However, you can still use automation for custom polling to achieve individual account sync (this is a pro feature)

You can set the day /hour wise schedule

Developer is very active and responsive as you can see from the XDA thread, which is the right place to get your questions answered.

I am an extremely satisfied user of FairEmail and not affiliated anyway with it.

---
Tags: email
---


# Question
Title: How can I reformat internal storage on Android?
I'd like some assistance with formatting the internal storage of my phone. I've managed to unbrick it and to flash TWRP recovery but I can see that capacity of the internal storage is only 33 MB which is clearly wrong. Before I started doing all this it had GB of capacity not MB. So clearly I need to fix this. I tried to use Windows's disk manager but the manager isn't detecting the phone or the storage.

Can I have some guidance here ? It's Meizu 5 pro. Any helpful input much appreciated.

`cat /proc/partitions` gives me:

```
major   minor  #blocks  name
   8       0   61071360  sda
   8       1   1024      sda1
   8       2   256       sda2
   8       3   256       sda3
 259       0   4096      sda21
 259       1   8192      sda22
 259       2   2048      sda23
 259       3   4096      sda24
 259       4   4096      sda25
 259       5   24576     sda26
 259       6   32768     sda27
 259       7   32768     sda28
 259       8   20480     sda29
 259       9   20480     sda30
 259      10   20480     sda31
 259      11   20480     sda32
 259      12   20480     sda33
 259      13   2621440   sda41
 259      14   524288    sda42
 259      15   57663468  sda43
 259      16   38912     sda44
   8      16   4096      sdb
   8      32   4096      sdc
 179      0    30253056  mmcblk0
 179      1    30252032  mmcblk0p1

```

`ls -ld /dev/block/bootdevice/by-name/*` gives me "No such file or directory"

**Note:**

The phone hasn't got any OS running at the moment.

I managed to use ADB and fdisk to get a list of locations (`fdisk /dev/block/sda`) in the phone. Then I pressed "p" for a print out. I marked locations or partitions in question. Cache takes up all the storage whereas "userdata" gets only 38MB. In advanced mode where I get to make changes when I press "p" again I get different output. I don't understand this.

**Update:**

I modified the partition table to make it look like the way I need:

The problem I'm dealing with right now is that the phone doesn't want to mount the devices. Can't get it to mount system, cache, userdata. I made sure "userdata" is still vfat and cache is ext4. Order number of partitions have changed though. Does that matter ?

**latest update:**

Looks like I was right for once. When I ran `mount -a` to mount all devices I got error because devices are assigned to different partition number.

# Answer
check your file system type is ext4 or f2fs with `mount`

in TWRP you can format from command line (beware this is factory reset /data and /sdcard is lost)

```
adb shell
umount /sdcard /data
mount -r /system
mount -r /vendor
export PATH=/system/bin:/sbin
export LD_LIBRARY_PATH=/system/lib64:/system/vendor/lib64:/vendor/lib64:/system/lib:/system/vendor/lib:/vendor/lib
/system/bin/sh
mke2fs -t ext4 /dev/block/sda44 [fs-size]
or
mkfs.f2fs /dev/block/sda44 [fs-size]

```

Note: fs-size is optional. depending on encryption method you may reserve last -16384 bytes for encryption footer. in this case calculate sectors
> 0 votes

---
Tags: internal-storage, twrp, partitions
---


# Question
Title: Is there a way to check when my Android screen was on and off?
Is there a way to check when my Android screen was on and off? I am doing a medical control of when I go to sleep and when I wake up and the screen on/off is a great way of doing it.

# Answer
> 1 votes
You can setup an automation app to log those events in a file. Tasker and MacroDroid, both are capable apps that can do this.

---
Tags: screen
---


# Question
Title: How many different types of YouTube Vanced are there?
I have many YouTube accounts, and signing in and out is inconvenient. That's why I use different YouTube Vanced for different YouTube accounts. At present, I have three YouTube Vanced: version pink, blue, and this one of which I don't know the name.

I need another version of YouTube Vanced other than these 3 for my other YouTube account.

I can't use apps like Dual Apps to make a copy of YouTube Vanced because then signing in won't work. I have also downloaded many versions from the internet but in the end, I found them all similar to my previously installed versions of YouTube Vanced.

How many different types of YouTube Vanced are there?

# Answer
There are 4 YouTube Vanced versions: Blue, Pink, Dark, and Black.

You already have YouTube Vanced Blue and Pink. I'm not sure if you have Black or Dark, but one of them should work for you.

This XDA thread contains download links as well.

Some Alternative Apps

1. NewPipe Link
2. YouTube Go Link
3. OgYouTube Link
> 1 votes

---
Tags: youtube
---


# Question
Title: How to set static IP on command line or adb shell?
I can't seem to use `netcfg` on Nougat. If I use `ifconfig ip` is not updating.
If there is another method to change IP on command line or `adb shell`, I am all ears.

# Answer
> 5 votes
You can try using `ip` command.

How it compares to ifconfig

Edit: To set up an IP address you can use:

> ip address add 192.168.0.77 dev eth0

or the long form

> ip addr add 192.168.0.77/24 broadcast 192.168.0.255 dev eth0

look up current config using

> ip addr show

# Answer
> 0 votes
In you terminal, run these commands:

```
adb root
adb shell
$ ifconfig eth0 192.168.138.2  # to fix your address
$ netcfg  # show address

```

---
Tags: adb, networking, shell, 7.1-nougat
---


title: how to re-install TWRP from Linux?

text:
# Question
Title: how to re-install TWRP from Linux?
```
Android version:       4.4.3
HTC Sense version:     6.0
software number:       2.23.661.2
HTC SDK API level:     6.25

kernel version:        3.4.0-g52343b3
                       and @ABM105 #1
                       SMP PREEMPT
build version:         2.23.661.2.CL3568029 release-keys

```

Previously I was locked in a loop where only `TWRP` was available. The developer option is certainly enabled. At the moment, not sure how to get back to the `TWRP` menu.

How do I accomplish a fresh install of a new version of `TWRP`? I was going to connect it with Linux.

TWRP says:

> How can I uninstall or remove TWRP from my device?
>
> For the vast majority of devices, you don't actually remove TWRP to get back to the stock recovery. Installing a different recovery is your only real option. Simply install whatever recovery that you want and that will overwrite or replace TWRP. Usually you can follow the instructions on our website for installing TWRP manually, only use the file for whatever recovery you are choosing to install instead of the TWRP file.
>
> Note, we don't keep or maintain a database of stock recoveries. If you are trying to reinstall the stock recovery, you will have to find a copy of the stock recovery on your own.

although I'm not entirely clear on what they mean by "another recovery", but, how do I actually install from Linux?

see also:

https://www.xda-developers.com/how-to-install-twrp/ https://www.androidguru.eu/twrp-installation-tutorial-linux-mint-ubuntu-users/

basically, so long as I get the correct image it's quite simple? Since it was already installed I don't need to muck with locked boot loaders??

What does "fastboot oem lock" do?

# Answer
> 1 votes
The quoted text is for "uninstalling" TWRP

If i understand your question correctly, your only concern is to update TWRP to newer version

before flashing new image it is recommended to test if it works without flashing (not all devices support this)

```
fastboot boot twrp.img

```

installing TWRP depends on device

some devices don't have recovery partition. in this case you need another self installing zip file which will install TWRP in recovery-ramdisk in boot partition

if device has separate recovery partition you can simply flash the partition image

this can be done from fastboot

```
fastboot flash recovery twrp.img

```

from pc command line

```
adb push twrp.img /dev/block/bootdevice/by-name/recovery

```

or even from TWRP itself in Advanced - Terminal

```
cat /external_sd/twrp.img > /dev/block/bootdevice/by-name/recovery

```

Some TWRP variant does allow backup/restore recovery. in this case you can just rename the `twrp.img` into `recovery.emmc.win`, place it into empty backup folder `TWRP/BACKUPS/*/recovery` and restore backup

Note: Your bootloader must remain unlocked as long as TWRP (or any other modified partition) is installed. re-locking bootloader is only recommended after you flashed full stock ROM including stock recovery. Otherwise you will brick

---
Tags: twrp, fastboot, bootloader, htc, formatting
---


title: How to install split-apk as system app?

text:
# Question
Title: How to install split-apk as system app?
I would like to know if its possible to convert a split-apk user app to a system app. One example is the google messaging app, it has a couple of apk files, lib and oat folders and base.dm file in its own /data/app/ folder. I tried copying everything to /system/app without success.

This question has already been asked here, but it hasn't been answered.

I'm using Android 10 rooted with Magisk. I already tried moving a regular .apk file to /system/app without any issues.

# Answer
> 1 votes
Figured it out after a bit of troubleshooting. Done using Root Explorer.

Copy "base.apk" and "lib" folder from "/data/app/xyz" to "/system/app/xyz" and set the permissions. Make sure to not delete the files from /data/app/xyz after copying!

Example with Google Messages:
\- Create a folder called "GoogleMessages" in "/system/app"
\- Remount "/system" as read-write when warned
\- Copy "base.apk" and "lib" folder from "/data/app/com.google.android.apps.messaging-xyz" to the new folder
\- Rename "base.apk" to "GoogleMessages.apk"
\- Give respective permissions to the folders and files.

Permissions for folders -\> rwxr-xr-x
Permissions for .apk and files inside lib -\> rw-r--r--

I can't guarantee that this will work on every device, just make sure to have a proper backup ready if something breaks or just use the file manager in recovery to delete the created folder.

---
Tags: root-access, apk, system-apps
---