I’m an iPhone user myself, so I am not well familiar with how Google and simultaneous Xiaomi backup management.

My father who has Xiaomi Redmi Note 8 Pro told me all his contacts are missing. I’ve tried to restore the contacts on the phone, but Xiaomi backup management wasn’t even loading (showing errors at "loading backup 0%"). I wasn't able to find Google Contacts at all on the phone.

I took a route of logging in to my father’s Google account on the web browser and then proceed to contacts.google.com where I could see all his contacts in trash and the "reason" was listed as "Deleted on Sprd - ums512_1h10_Natv". I was able to restore all the contacts from trash (thankfully) and immediately after restoring the contacts there on contacts.google.com the contacts appeared on the phone.

I am googling this message and see some traces of similar problems with contacts but nothing that looks useful.

How could I find out what app, system component or a setting could cause the contacts to be deleted? And how could I configure my father’s phone to prevent this problem in the future? Loosing contacts is a real horror story.

Thank you!

Let say on my home Wifi, I want to use DNS server "X" and on work WiFI, I want to use another DNS-server: "Y", on cellular a server "Z" and so on. Is this possible to do this automatically? (Preferably without root) There seems to be loads of "DNS-apps" on play store, but I can't find any that do this. (have not tried them all)

I've got a relatively new Galaxy A71. With all my previous Android phones, my camera photos automatically got picked up in Google Photos. This phone, for some reason, doesn't work that way; if I want my photos to upload to Google, I have to select and share them manually. Inside Google Photos itself, in the section to select "Device folders", it tells me "Your camera folder is automatically backed up." But, fact: it's not.

How do I fix this?

Issue; when downloaded to a Mac, the .zip file was unzipped. The issue was resolved by downloading files from the vendor with Windows.

The goal is to install the factory Android 10 ROM:

HE_FULL_UPDATE_10-16-10.00-QG-U00-STD-HEL-04.zip

and wipe the existing configured ROM. The .zip file contents were copied to a micro SD card, which was installed in the Android device.

From Android Recovery Mode, I tried to install the files that were visible, however the failures returned are captured on the photo:

A list of files is returned by user@mac HE_FULL_UPDATE_10-16-10 % find .

./compatibility.zip
./.DS_Store
./care_map.pb
./META-INF
./META-INF/.DS_Store
./META-INF/com
./META-INF/com/.DS_Store
./META-INF/com/symbol
./META-INF/com/symbol/DeviceManifest.xml
./META-INF/com/android
./META-INF/com/android/otacert
./META-INF/com/android/metadata
./payload_1.bin
./payload_properties.txt
./payload_properties_1.txt
./payload.bin

For some reason not all file are displayed in Android Recovery Mode. Which file is the to be selected and how to enable its selection from the Android Recovery Mode?

Attempt to flash .zip file failed:

I am trying out the APK signature scheme v4 introduced in Android 11. I use the apksigner from the Android Sdk and it seems to work fine: it signs the .apk and generates the .idsig file as expected:

$ apksigner sign -v --ks ~/keystore.jks --ks-key-alias testkey app.apk
Keystore password for signer #1:
Signed

$ ls
app.apk  app.apk.idsig

However, when I use the same apksigner tool to verify the signature, it outputs the following:

$ apksigner verify -v ./app.apk
Verifies
Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): true
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
WARNING: META-INF/com/android/build/gradle/app-metadata.properties not protected by signature. Unauthorized modifications to this JAR entry will not be detected. Delete or move the entry outside of META-INF/.
... # and a bunch of other v1-related warnings

So it successfully verifies based on APK Signature Scheme v3 and doesn't take into account the .idsig at all (modifying the .idsig file does not affect the verification result). I expect Verified using v4 scheme (APK Signature Scheme v4): to also be true.

Am I missing something?

I need help debugging something. My company recently purchased an Zebra MC220K, and it is unable to resolve internal DNS domains. I have tried all of the following:

1. Forget the network.
2. Enable / disable airplane mode.
3. Change the wifi configuration to 'static' and manually put in the DNS server that we use.
4. Install termux and doing a DNS lookup, which resulted in the correct ip should be referring to.
5. Factory reset the device.
6. Check a dozen other android devices (S8, S10, S20, Galaxy Tab, Google Pixel, etc), all of which work as expected.
7. Run an android 10 vm, which also works as expected.

I am at a loss, I have no clue why I am still getting ERR_NAME_NOT_RESOLVED when using Chrome / Firefox / Edge / Samsung Internet / Brave / Opera. Literally any browser throws this error, clearly indicating something wrong in the software.

Are there any other tests I should perform, or do I just yeet back the product because it doesnt work?

Now a time, whenever you make a login or anything using a username or password, Google prompts you to save the password in your primary account.

Unlike earlier, when it was limited to browsers only, but now the prompt comes even when you're logging with an app.

How is Google able to know that it is login and they have to prompt to save password?

I would like to be able to copy some text (e.g., from a website viewed in Google Chrome) and paste it so that the pasted text uses markdown, e.g. to contain links. On Microsoft Windows + Chrome, I use the Google Chrome extension Paste as Markdown . How can I do that on Android?

I use Android 10 with Samsung Galaxy S9.

I am running LineageOS 18.1 on my Raspberry Pi 4 with 4 GB (using this ROM: https://konstakang.com/devices/rpi4/LineageOS18/). It worked, until I tried getting into TWRP to root the device. But, since TWRP is touch and I didn't knew this before, I got stuck since I have no touchscreen. Now, if I turn the device off and on again after a few seconds, it still boots into TWRP and asks me if I want to install it to /system. But how do I get into the normal Android mode again. And since the RPi4 has no buttons like Volume Up, Down and Power, I can't boot normally into the system. So how can I modify the files to get out of there or is there any other way to get out of TWRP without buying a touchscreen?

According to the screenshot below, background applications have a lower download and upload speed:

The screenshot says:

Keep the app open for getting the best and upload speed.

How can I avoid that?

I use Android 10 with Samsung Galaxy S9.

How can I kill an app by holding the back button in Lineage OS 18?

One of the first things I've always done when installing a new Android was to enable developer options, then scroll down to the very bottom and enable the toggle for `Kill app back button"

Kill the foreground app by long-pressing the back button

I just upgraded to LineageOS 18, and I was very sad to discover that this option is missing!

How can I replace this functionality on LineageOS 18 so that I can force-close misbehaving apps by holding down the back button?

Why is it that the GrapheneOS (Android ROM) project crypographically signs their releases with signify instead of PGP?

The install documentation for GrapheneOS instructs the user to install the signify-openbsd project from apt and use it with the official GrapheneOS release signing public key to verify the authenticity of their releases.

• https://releases.grapheneos.org/factory.pub

Most software projects use PGP to sign their releases.

Why does GrapheneOS use signify?

I noticed that the files stored on Pixel's Recorder app (if not backed up/synced) cannot be easily imported from other apps.

They are stored in /data/data/com.google.android.apps.recorder/files/recordings which I understand requires root access to directly access the files outside of the Recorder app.

My question - and I apologize in advance for the newbie nature of this question - is, on a non-rooted phone, how easily could these files be accessed by an app that has permission to access media files or all files? Thinking of malicious apps, or apps like TikTok which have been known to gather/access more data than they need.

How can I configure Microsoft Teams so that it doesn't disconnect the audio when I receive a phone call during a Teams meeting? I use Android 10 with Samsung Galaxy S9.

I have a Gmail account and 7 of my friends including me have added the google account to our android devices. However, it can be used for the features like Find My Phone and subsequently can be used to erase the data if any one of us wishes to do so.

So, how do I make that Gmail account just send me notifications for new emails, and not allow it to trace my phone using features like Find My Phone? I have searched in the web, but didn't get any way to achieve what I want. Any suggestions regarding this would be of much help to me.

In other words, is there a way to add the Gmail account like just another email account (e.g. Outlook etc.) in our devices?

I'm looking for a way to remove the preinstalled Gmail app (not account, I meant the app itself). My web searches yield methods to remove gmail account, not the app. Just to add, I had managed to finish the default android setup/installation (when the phone was 1st activated after purchase) by using a non-gmail account. It worked just fine til today (almost 1 year).

Gmail/Gmaps/Photos/Other G-Apps is just another app in android. Just quite puzzled why it can't be uninstalled just like any other app. I'd prefer a non-root removal solution if possible.

If it is not, appreciate if you can include a way to 'undo' the root after the app removal. Terminal based or debug mode solution are still acceptable as long as the phone can still be switched back to 'non-root' mode later. Fyi, I'd prefer the phone to operate in 'non-root' whenever possible as a (tiny) phone cybersecurity effort.

p/s : This post share a method to disable it.. but not (afaik) uninstall.

I have a persistent problem with notifications to all apps on my OnePlus6+ where they typically are delayed 30-60s, often I will get several notifications showing at once or when I unlock my phone suddenly I get notifications.

I can test with gmail, Slack, Messenger, WhatsApp and any other app where I have a version open on my PC at the same time

I've only ever owned Android smartphones, and only from OnePlus so I do not know if this is just how Android works or is a 'feature' of OxygenOS/OnePlus hardware. But it's happened across multiple versions of Android and hardware for several years.

It suggest PUSH notifications are not really being PUSHed but polled, like the phone is only checking periodically.

I see it whether on WiFi or cellular networks and it's quite irritating. Can anyone give me any information or advice about it?

I have updated my Pixel 5 to Android 12 Beta, and in the last update, the "app" or service called "dex2oat64" eats too much battery.

I found some thread in Reddit, but they also don't know the answers like me.

What is this app/service?

I have a Gabb Wireless which is an Android that is programmed to be "dumb". By "dumb", I mean it only has core apps such as Settings, Phone, Messaging, etc. I like it because it is not additive to where I can't focus on my school.

It has some major drawbacks though. To keep kids from messing up the restrictions, they pretty much bricked the phone. I can't flash, ADB*, install apps**, or unlock the bootloader*** the way other sites say to do.

All I want to do is host a web server and customize the OS a bit. I have contacted the distributor and of course, they would not reveal anything.

Stars:

1. The original way to allow USB debugging/Developer mode is gone.
2. The store was removed and you can't install raw APKs.
3. When I boot into the Bootloader, the screen is blank with "=> FASTBOOT mode..." at the bottom.

Overall, I am disappointed with the extremes which the company took. I have gotten them to admit that the device is hackable. Of course, any device is hackable so I did not get much from that.

Any ideas?

I am trying to flash twrp to my ZTE Axon 7 but until now I just keep getting errors every time I try to flash something.

Device is already wiped and bootloader unlocked.

I am in fastboot mode, I also get some unknown error in MiFlash. So basically I haven't really been able to flash anything.

Already tried different ports and cables, don't have any other cables lying around. PC does have a ryzen 5800x, some maybe that is the problem?

D:\ZTE Axon 7>fastboot devices
a773911d        fastboot

D:\ZTE Axon 7>fastboot flash recovery "D:\ZTE Axon 7\twrp-3.5.2_9-0-ailsa_ii.img"
Sending 'recovery' (16104 KB)                      FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed

I also tried some commands like "clear cache" and "reboot bootloader" but they produce the same kind of error.

Really running out of ideas on this one, i've already tried numerous things and keep getting a variation of these "Write to device failed" errors all the time.

When I look at any guides/videos online it just works, but not for me.

Trying to use fastboot boot (different usb ports):

C:\adb-platform-tools>fastboot boot twrp-3.5.2_9-0-ailsa_ii.img
Sending 'boot.img' (16104 KB)                      FAILED (Status read failed (Too many links))
fastboot: error: Command failed

C:\adb-platform-tools>fastboot boot twrp-3.5.2_9-0-ailsa_ii.img
Sending 'boot.img' (16104 KB)                      FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed

C:\adb-platform-tools>fastboot boot twrp-3.5.2_9-0-ailsa_ii.img
Sending 'boot.img' (16104 KB)                      FAILED (Status read failed (Too many links))
fastboot: error: Command failed