I have multiple Google accounts on my Android 10 (Samsung Galaxy M10s). Until today, I was using YouTube without signing in. Today I signed into YouTube with one Google account. Now I want to sign out from YouTube app but I don't find any such option.

I searched on internet and found Google Support Page which suggests to remove account from device in order to sign-out from YouYube app.

What I did:

Opened YouTube, go to manage accounts, removed the account from device, through which I have signed in YouTube; Then cleared the YouTube application data also.

But what I found is YouTube just auto signed in with my another Google account.

How do I sign out from YouTube?

How can I configure BlueStacks to have Android use dark mode?

On Android 10 I can use:

but I can't see the option on Android on BlueStacks:

My device: I use Android 9 on samsung galaxy s9.

Background: I believe there was a feature before (or maybe currently still, but I turned it off) about showing number of unread messages on apps like whatsapp, viber or the SMS app (and i guess gmail or facebook) or at the very least there's some kind of dot or something on a corner of the icon of such an app that indicates there exists at least 1 unread message (so the dot is an alternative to a specific number of unread messages).

My situation: I do not have such number or dot on icons on apps on my device. If I get a message on whatsapp or viber or regular SMS but say I have to install some updates and so my phone has to turn off or restart, then the notification of this message is gone.

Question: How do I see number or existence of unread messages on icons of apps such as viber and whatsapp and the SMS app?

I have tried looking this up, but

1. I wasn't able to find any articles specifically on Android 9 and Samsung Galaxy S9.

2. The solutions proposed in articles I've found on Android 9 but a different phone or on different versions of Android have not worked for me.

3. I've tried looking up some apps on the play store, but I haven't downloaded any because of the reviews.

Further to this Problem with intents :MacroDroid, the solution in the accepted answer works but sadly only for the first time (app error) . I have reported this to the developer

Meanwhile, I thought of trying to see if a broadcast intent would solve the problem. Lacking understanding of how intents work, I tried this and other combinations (ON in square bracket, Action same as class) , but couldn't get it to work.

Here is the Tasker intent that works

Request help in constructing broadcast intent.

NOTE:Please don't edit to make the images smaller for the sake of readability, let them be

I like to know where exactly the FileSync jobs are stored in a MyPhoneExplorer phone profile? (in what file, and which location (profile folder or AppData folder))?

I like to emigrate to a new phone and I have a lot of customized FileSync folders configured, all the folders have the same path on my new phone and I want the same folders and options as in the old phone. How can I easily import them into a new profile I created for my new phone? Without creating them all over again (would spare me a lot of work).

I searched all the config files in my old phone profile folder and hoped they were stored in "FileSync.dat", I copied that file to the new profile and restarted MyPhoneExplorer, but it did not seem to work, still no SyncJobs in the SyncFiles menu...

Thanks a lot in advance.

Due to some problems with my Acer Iconia 7 tablet (with KitKat 4.4) I decided to perform factory reset. However, because I have there some data that I did not want to lose I created a backup in HoloBackup. The backup was created succesfully (it has around 1 GB), but when I try to restore it, the process fails by error adb: archive is encrypted but no password given.
Now, at this point, I do not understand, because in developer settings I set a password to protect the backup feature of the tablet. But the error message sounds like a password protection is actually required for the .ab file itself. But in the settings nor in HoloBackup, I cannot see any way how to do it.
Can you help me please. Thank you.

My mother has the habit of ending the conversation by pressing the BACK button several times instead of hitting the red button. The perso she talk to can be heard after a few minutes (people are nosy and my mother is old). Is there an option or an application that contains a silent closing of conversation windows and was visible until the end of the conversation?

A few days ago I've updated my rooted(with magisk) galaxy s10(SM-G973F) to the latest firmware(patched with magisk) of ILO(G973FXXU7CTF1 - my previous firmware - G973FXXU4BTA8 - had one ui 2.0), and it seems that since then, it is pretty much bricked.

GBWhatsapp Mini doesn't work anymore(can't download media), Google Play tells me Netflix and a bunch of other apps are "not compatible with your device" and I can't connect my Galaxy Watch anymore(stuck on pairing).

I've previously tried to upgrade it to G973FXXU4CTC9 and had the same issue so I've downgraded back to G973FXXU4BTA8 and it was all fixed, but now it won't let me even downgrade(SW REV CHECK FAIL)..

What can I do then?

Thanks

I am not able to get the intent running for this out loud app. App description says

• Launch these activities to change the on/off state of Out Loud: com.hillman.out_loud.activity.OnActivity

• To change the on/off state through a broadcast intent, send a broadcast with these details:

Action: com.hillman.out_loud.ON_OFF Data: out_loud://on_off?state=[state]

whether I use activity or broadcast.

What am I doing wrong?

I am trying to start learning how to develop Android apps, and I tried to make a new project and navigate through Android Studio. I tried using the Emulator by creating a new virtual device and running my new test project with it, but no matter what i seem to do it never actually does anything once I click the "Run" button on both the AVD Manager and the main one you see on the top right area of Android Studio.

I keep seeing this after i try to click the Run button again after not seeing anything happen. and i can't seem to delete any of the files this is pointing to since Windows keeps complaining its being used by another application even after I close Android Studio and terminate adb.exe

I've been looking around for an answer and i've found things like "Uncheck Enable ADB Integration", or "Changing the Emulated Performance Graphics to Hardware/Software", but a lot of these answers are from threads that are 3+ years old so I don't think these are applicable anymore. can someone provide some insight to how to get this working? I am using Android Studio 3.6.3

PS: I want to make it clear that even after i restart my pc and delete these so called "*.lock" files, this changes absolutely nothing

EDIT: As requested here are some screenshots that hopefully answers some questions I was being asked.

My PC specs:

Android Virtual devices i have set up so far:

my installed SDK Tools:

As for the BIOS Virtualization question, if "Intel Virtualization Technology" is the same thing then yes it seems to be enabled for me

Let's say, if I download image file from mobile browser, opening it leads to the "open with" window where i see all of the installed gallery apps to choose from.

however, there are other apps (i.e. upwork messenger) from where if i download the image file, while opening it, there doesn't show up any image editor/gallery aps, instead quite unrelated apps (i.e. ms word or pdf viewer shows up) so i just can't open images...

what could be the reason for that and how to force apps (i.e. image apps) everywhere to be shown up when opening the image files.

I messed around with my phone (Huawei P10 VTR-L29) and unfortunately bricked it.

what happened

To give you the whole story, I tried to root it, but during the root process I found out that the device is encrypted so I had to "rollback". That worked fine and my phone was working ok with one issue - I wasn't able to update firmware via regular system updates. I saw the update, but wasn't able to download and install - it always ended up with some error.

That made me decide to reinstall the firmware from scratch. I followed general steps but yeah, I messed up.

current status

The only thing I can see now is

When I click on download latest version and recovery

But after a while it fails:

And I am stuck :( I can't get any further .. I tried to connect via ADB (but since I cannot get in the phone to enable USB Debugging (which might be the problem) I am unable to connect (nor ADB neither FASTBOOT can see the device).

I tried to create this file:

/etc/udev/rules.d/51-android.rules 

But when I run

sudo adb kill-server
sudo adb start-server
adb devices

It's still empty ... I can't even get to the "FACTORY RESET" by pressing and holding POWER + VOL:DOWN for some time; it always brings me back to the Huawei eRecovery

Do you guys have any idea how to fix this?
Or is that phone dead for good?

I don't care about the data inside.. I would only love to make it work again

EDIT

with the help of alecxs I made it to the fastboot&rescue mode

however this

sudo fastboot boot [img]

ends up with

downloading 'boot.img'...
OKAY [  1.052s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.056s

similar for

sudo fastboot flash recovery [img]

ends up with

target reported max download size of 471859200 bytes
sending 'recovery' (32040 KB)...
OKAY [  0.995s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.001s

EDIT2:

I asked as well one of my friends and we moved on a bit more ...

I tried to unlock the bootloader

sudo fastboot oem unlock [unlock_code]

Then I got this screen:

I went with the option (2) and that brought me to the first screen mentioned in this article "Huawei eRecovery"

but when I repeated the VOL:DOWN + USB:CABLE:PLUG trick :) I got this

I tried a different TWRP (for P10 specifically) from this link: XDA Devs - P10 TWRP

Flashing worked fine:

sudo fastboot flash recovery_ramdisk twrp_p10_0.1.img

I got:

target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24954 KB)...
OKAY [  0.771s]
writing 'recovery_ramdisk'...
OKAY [  0.232s]
finished. total time: 1.003s

after

sudo fastboot reboot

right after this command, I need to unplug the USB cable and hold VOLUME:UP to be able to get to TWRP (swipe.d to allow modifications) ... am there already

now I am looking for any ROM for my P10 to flash it. I want to try this one: TheUpgradeGuide.com - Pixel Experience

I downloaded the gApps and ROM ... uploaded it to the "Internal Storage" of the phone (there was a folder TWRP so I put it next to it)

.
..
/TWRP
rom.7z
gapps.zip

Went on wiping -> WIPE -> ADVANCED -> checked these

• Dalvik Cache
• System
• Cache
• Data

swiped to wipe (uplugged USB) .. but got this error:

Updating partition details ...
Failed to mount '/odm' (Invalid argument)
...done
Failed to unmount '/system' (Device or resource busy)
Full SELinux support is present
MTP Enabled
Failed to unmount '/system' (Device or resource busy)
Wiping Dalvik Cache Directories...
--Dalvik Cache Directories Wipe Complete!
Formatting Cache using make-ext4fs...
Wiping data without wiping /data/media ...
Done.
Failed to unmount '/system' (Device or resource busy)
Unable to wipe /system.
Updating partition details...
Failed to mount '/odm' (Invalid argument)
...done

EDIT 3

in the adb shell

~ # mount
rootfs on / type rootfs (rw,seclabel,size=1457112k,nr_inodes=364278)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
/dev/block/bootdevice/by-name/secure_storage on /sec_storage type ext4 (rw,context=u:object_r:teecd_data_file:s0,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
hdb on /dev/usb-ffs/hdb type functionfs (rw,relatime)
/dev/block/bootdevice/by-name/system on /system type ext4 (ro,seclabel,relatime,data=ordered)
/dev/block/bootdevice/by-name/vendor on /vendor type ext4 (ro,seclabel,relatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
/dev/block/sdd46 on /data type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
/dev/block/sdd46 on /sdcard type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
/dev/block/sdd13 on /cache type ext4 (rw,seclabel,relatime,data=ordered)

plus the ls output

~ # ls -ld $(find /dev/block -name by-name)/*
drwxr-xr-x    2 root         root              1020 Jan  4 18:02 /dev/block/bootdevice/by-name
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/boot_a -> /dev/block/sdd32
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/bootfail_info -> /dev/block/sdd14
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/cache -> /dev/block/sdd13
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/cust_a -> /dev/block/sdd43
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/dfx -> /dev/block/sdd19
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/dts_a -> /dev/block/sdd34
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/fastboot_a -> /dev/block/sdd24
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/frp -> /dev/block/sdc1
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/fw_hifi_a -> /dev/block/sdd28
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/fw_lpm3_a -> /dev/block/sdd21
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/hisee_fs -> /dev/block/sdd18
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/hisee_img_a -> /dev/block/sdd23
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/isp_boot_a -> /dev/block/sdd26
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/isp_firmware_a -> /dev/block/sdd27
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/misc -> /dev/block/sdd15
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modem_fw_a -> /dev/block/sdd36
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modem_om -> /dev/block/sdd7
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modem_secure -> /dev/block/sdd3
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modemnvm_backup -> /dev/block/sdd9
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modemnvm_factory -> /dev/block/sdd8
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modemnvm_img -> /dev/block/sdd10
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modemnvm_system -> /dev/block/sdd11
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modemnvm_update_a -> /dev/block/sdd38
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/nvme -> /dev/block/sdd4
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/oeminfo -> /dev/block/sdd5
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/patch_a -> /dev/block/sdd39
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/persist -> /dev/block/sdc2
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/product_a -> /dev/block/sdd42
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/recovery2_a -> /dev/block/sdd30
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/recovery_a -> /dev/block/sdd33
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved1 -> /dev/block/sdc3
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved10 -> /dev/block/sdd17
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved2 -> /dev/block/sdd16
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved3_a -> /dev/block/sdd22
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved4_a -> /dev/block/sdd37
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved5 -> /dev/block/sdd45
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/rrecord -> /dev/block/sdd20
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/secure_storage -> /dev/block/sdd6
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/sensorhub_a -> /dev/block/sdd31
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/splash2 -> /dev/block/sdd12
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/system_a -> /dev/block/sdd44
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/teeos_a -> /dev/block/sdd29
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/trustfirmware_a -> /dev/block/sdd35
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/userdata -> /dev/block/sdd46
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/vector_a -> /dev/block/sdd25
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/vendor_a -> /dev/block/sdd41
lrwxrwxrwx    1 root         root                16 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/version_a -> /dev/block/sdd40
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/vrl -> /dev/block/sdd1
lrwxrwxrwx    1 root         root                15 Jan  4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/vrl_backup -> /dev/block/sdd2

Ok, with the help of alecxs I managed to get a bit further (see the chat) but it seems like the TWRP is faulty (the one from the link above -> XDA).. nonetheless, any other TWRP is not working at all and I am landing on this screen instead :(

EDIT 4:

output of fastboot getvar all is here:

getvar:all FAILED (remote: Command not allowed)

EDIT 5:

see the output of the fastboot commands requested in the chat

#sudo fastboot oem get-bootinfo
...
(bootloader)  unlocked
OKAY [  0.006s]
finished. total time: 0.006s

$ sudo fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.007s

$ sudo fastboot oem get-build-number
...
(bootloader) :VTR-L29C432B151
OKAY [  0.007s]
finished. total time: 0.007s

$ sudo fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :VTR-L29C432B151
OKAY [  0.008s]
finished. total time: 0.008s

SOLVED

Finally, I made it and the phone is up and running :)

I downloaded Huru Updated (v0.3) and these files https://huaweidl.com/download/huawei-p10/vtr-l29/b151/

Followed these steps: https://www.getdroidtips.com/hurupdater-tool/

and yaaaay, it works :) after months of playing around ... big thx to alecxs for his immense help !!! this guys is a genius !!!

the only question now is to get from Android 7 (the stock I flashed) to 9.1 (the most updated one provided to p10) ... bec the native system update does not offer me an update :D but that's minor ..

EDIT: ok, following this manual xda-developers - Jannomag I was able to upgrade to 8.0 (with a little hiccup - just had to manually restart it multiple times) and then to 9.0 (no problem at all this time) and right after 9.0 it offered me (via system update) automatically the newest 9.1.0.263

How to do a whatsapp local backup and how to restore whatsapp using local backup.

I followed the steps mentioned in https://www.business-standard.com/article/technology/how-to-back-up-restore-whatsapp-chat-history-using-google-drive-storage-119072500591_1.html#:~:text=To%20find%20the%20local%20backup,folder%20inside%20the%20WhatsApp%20folder.

How to restore WhatsApp backup using microSD card

If you remove WhatsApp for any reason and install it again on the same device, the instant messenger notifies about the existing local backup and takes your permission to restore messages from it. Follow the steps below in case you switch to a new device and seek to restore WhatsApp chat history from local backup:

Step 1: Insert a microSD card in your old phone, if it has a slot

Step 2: Go to the phone’s file manager

Step 3: In the file manager, locate WhatsApp folder in root

Step 4: Copy the WhatsApp folder and transfer it to the microSD card

Step 5: Eject the microSD card safely and insert it in your new phone, if there is a slot

Step 6: Download and install WhatsApp on a new phone. Set it up and then uninstall it

Step 7: Replace the WhatsApp folder in your phone’s internal storage with the one saved in the microSD card

Step 8: In the file manager, navigate to sdcard/WhatsApp/Databases

Step 9: Rename the backup file you want to restore from msgstore-YYYY-MM-DD.1.db.crypt12 to msgstore.db.crypt12. It is possible that an earlier backup may be on an earlier protocol, such as crypt9 or crypt10. Don't change the number of the crypt extension

Step 10: Download and install WhatsApp again and select the option to restore the whatsapp data from "Google drive". But this time it will identify your local backup and notify if you would like to restore from it instead of visiting Google drive.

In case the old phone or the new phone does not have a microSD card slot, copy the WhatsApp folder from your phone’s internal storage on a desktop. Perform the step 6 mentioned above before transferring the folder in the new phone’s internal storage. Once you transfer the folder, perform Step 8 and onwards.

I have an Android device (actually I am using Bluestacks Android emulator but I expect the process to be the same). I have setup WhatsApp on this device. Now I want to move to another device. So I did a whatsapp local backup using WhatsApp -> settings -> Chat backup -> Backup

Now I manually copied the WhatsApp folder in the Andoid file system which has the folders Backups, Databases, Media

Now I manually transferred these folders and then installed Whatsapp on new Android device using the same phone number. But when I open Whatsapp in this new device, then I only see the option to restore from Google drive backup but not from local backup. So I clicked Skip but then I dont see my chats

What is the process to successfully backup and restore whatsapp data locally using Android emulator?

Edit: I think there is an issue with the Whatsapp backup I am using. For example, the Whatsapp folder that was restored from Google drive is detected properly by whatsapp when I copied it to local storage. But the Whatsapp backup that I copied from Bluestacks is not detected I dont know why

Edit2: I have opened whatsapp from my old Bluestacks device and backed up all whatsapp data to Google drive. Now in the new Bluestacks device I selected the Google drive account to restore the backup. But whatsapp is still not able to restore my chats etc. So this is probably a Bluestacks issue where I am not able to move the whatsapp backup from one device to another if I am using whatsapp on Bluestacks

So it looks like the whatsapp backup taken from an Android phone can be imported into Bluestacks. But the whatsapp backup taken from Bluestacks is not detected anywhere so I will loose the chat history, but atleast media is available in the whatsapp folders which I copied from my old Bluestacks device's Android file explorer.

For a Live DJ streaming setup (on a budget), I would like to be able to receive two or more video streams from two or more Android phones via USB tethering using the IP Webcam android application. It works with one phone, but when I try to add a second phone, I can't connect to it.

Both phones start a server on the same IP at port 8080. I can't change the IP address directly in the app, but I can change the port. I tried changing the port on one of the phones, but the connection is still not possible.

I can't seem to find if receiving data from 2 USB tethering sources, at the same time, is possible or not. So my first question would be the following: is it possible? And if yes, how could I start to solve this problem?

Thank you.

We regret to inform you that the Together Community(BETA) service will no longer be available as of 1 July 2020.

https://www.reddit.com/r/samsung/comments/hevmxm/samsung_health_app_ending_the_together_community/

https://content.samsungknowledge.com/notices/46/en-US/en_US.html

Question: This refers to the 'together' tab of the samsung health app and not the whole of the samsung health app right?

How can I add a visual effect on where one clicks on the screen on Android?

Similarly to what can be done in Windows:

I don't see any Show Touches in Developer Options:

Is there any browser (or its add-on) running on Android 4.0 where I can tweak UserAgent string?

I would like to use older Android device to view Microsoft To-Do list in a browser. But they obviously have Android version check, because they display only old OWA (Outlook Web Access) interface.

Apps already tested:

• Samsung Internet - seeing the old Outlook UI (also in desktop mode)
• UC Browser - this app is unable to start
• Opera Mini - seeing the old Outlook UI

I want to monitor the https traffic of an Android app downloaded from google play.

This app can only be run at Android N and above.

So I use Charles proxy and follow this document to modify the apk file.

Here's what I have done:

1. Download the app from google play.

2. Use apk extractor to get the apk file of the app.

3. Run apktool d the_app.apk to extract the apk file.

4. Modify res/xml/network_security_config.xml and AndroidManifest.xml based on the description of Charles Proxy document.

5. Run apktool b the_app to package the files back to an apk file.

6. Install the apk on my Android phone, whose version is 8.

7. My phone says "App not installed".

Why can't I install the modified apk on my phone?

I've disabled Google Play Protect on my phone.

The apktool is installed by following the description here.

Is there anything I missed?

I've found my Xiaomi redmi note 4 stuck in fastboot mode after the battery had died. I tried different ways to unbrick it but nothing helps. The list of ways I tried:

1. platform tools fastboot binary. fastboot reboot bootloader - still rebooting to fastboot. Also, adb binary doesn't recognize my device.
2. I can't use mi unlock tool because it doesn't see my phone.
3. Miflash doesn't recognize the device also.

Are there any other ways to unbrick it?

Edit: It's Mediatek Helio X20

Is my phone is bricked or not?The device is not turning on . I thought it was ran out of power. I connected it to my charger. But instead of charging, it shows a blinking battery symbol contains a circle. When I turned off the charger, my phone started flashing with the boot logo untill the end of its battery charge and it is not turning on. I'm not installed a custom rom or rooted it.Can anyone find a solution?

device:samsung galaxy note 3

model:SM-N900