Question and Answer about Android from Stack Exchange network.

How can I set the Teams default meeting settings so that the video + microphone are always turned off by default?

I use MS Teams on Android 10 with Samsung Galaxy S9.

When trying to connect the app to web.whatsapp.com, the app insists to "unlock to link a device", meaning I get the same screen as when I turn my phone's screen on after it sleeps.

I know other WhatsApp users don't need to do that, they get right into the QR screen without any security measures.

So why does it happen?

Hallo Stack Exchange Community,

I have android 10 and 11 Samsung Tablets and I want to set the tablet (device) MAC on a specific SSID.

I dont need to know how to set it via Wifi Settings, because it changes after a restart. Source: https://www.easytechguides.com/disable-device-security-on-a-samsung-galaxy/

Is there any way to set it permanently? If not a simple no will do, but I still kinda hope that I did not find the right way to do it.

Other Sources: https://wifi-helpcenter.nokia.com/hc/en-us/articles/360056890733-Issues-with-random-MAC-addresses-Android-10-iOS-14- https://source.android.com/devices/tech/connect/wifi-mac-randomization

When there is multiple Android-devices connected with Linux computer (using Linux Mint 20.2 Cinnamon, which is based on appropriate Ubuntu 20.04 LTS version) and scrcpy v1.12 then how to keep multiple devices awake? When one device connected, then I used:

adb shell svc power stayon true

... and it worked.

When multiple devices, then there will be an error message:

error: more than one device/emulator

Tried find a solution, but no luck so far. Tried to connect devices one at a time and then run, but it didn't work. Having one device using OxygenOS 9.0.6, which is based on Android appropriate version. Second device has LineageOS 18.1, which is based on Android 11.

Using following commands to connect with multiple devices:

scrcpy -s <ID1> -m 1024 -S&
scrcpy -s <ID2> -S&

The -S will turn of device screen, once it is connected. I would like to keep screen on at computer, while using scrcpy, but device screen should be turned off at the same time.

Tried also GUI but it didn't help either. One device with Android 9 has screen always on, but another device with Android 11 will time out and also scrcpy window will turn off. I know, that there is a shortcut key CTRL+O at scrcpy, which helps to turn off device screen or using -S will do it immediately after connecting.

Any idea, how to solve this?

I bought an SD card of 64 gb for my Razer Phone 2 and I'd like to transfer big data in it (Spotify songs, videos, useless apps). I can't find any option to safely move data from my phone to the SD card. On top of it, i inserted the card, l installed it as memory extension and, out of nowhere i filled up 20 gb on it!! That is, my phone continues to have 97% of usage data plus 20 more GB on the SD card created apparently from thin air. How's it even possible? Did google just transfer there stuff, what criterion did it even use?

I downloaded an app 'files to SD card' which could do the transfer, however when selecting the root of the SD card it returns me the following message : 'no root directory has been selected'. I am afraid my card has been installed as extension of the SD card and thus cannot be used to transfer data from the phone to the SD card. However, after the creation of the 20 additional gb, i am afraid of reformatting the SD card to reinstall it differently. Hope this is clear enough

Is it possible to set the timezone of an android device (either a physical device or and emulator) to a timezone that doesn't actually exist (for instance, GMT+00:03 or GMT-500:00)? I tried reading the docs, and it seems like the data type supports that in theory, but I have no idea how you'd actually do that in practice, or if there's some reason it's impossible that I'm missing.

Starting from today, some apps on my phone just kept crashing. At first it was mostly Google-related apps, and since I've had issues with Google Play services crashing before, I took the usual route of deleting app data and uninstalling updates. However, the issues persisted, and spread to other apps. Google kept crashing, the stock e-mail app kept crashing,my third party SMS app kept crashing... Some apps crash when I open them, some don't. For some the problem is solved by uninstalling and reinstalling them, for some it isn't. Google-based apps like YouTube and Play Store work fine, but others like Chrome don't. I can't seem to find a single "triggering" event that could have started this, apart from maybe some background update. I am running Android 8.1.0 on a Samsung Galaxy J7(2016).

Is there any way to solve this ?

EDIT : I found the common factor between all those apps : they all store data on my SD card, which is still accessible but awfully slow. I'm guessing this is the root of the issue. However, I didn't specifically chose for those apps to be stored on the SD card, it seems Android automatically offloaded data there, and I don't know how to reverse it.

When using Bluetooth audio in my mark7 VW GTI with my Pixel 3 on Android 11 the GTI can no longer receive any metadata other than the track positon. On-screen and steering-wheel controls that used to work to skip, pause, play, etc. all are unresponsive. This started at some point a year ago probably after an Android system update. Unfortunately the car does not have built-in android auto integration. My wife's LGthinq 7 has no issues.

Multiple attempts at resetting the Bluetooth settings on my phone and the car and repairing have not fixed the issue.

I'm trying to unlock my bootloader so that I can root my Samsung Galaxy Note 10 plus.

The problem is that fastboot devices doesn't show any devices, so I found out that I need to install new fastboot drivers.

The first step is to locate your phone in Device Manager while it is in fastboot, but my phone is not showing up in in Device Manager at all while in fastboot.

Usually when I plug in my phone (or any device) into my PC the Device Manager refreshes and I hear the sound Windows makes when a new device is detected, but none of those thing happen if I connect my phone that is in fastboot.

I know that the USB port and cable are working because adb devices and Device Manager work fine and actually show my phone when it's not in fastboot.

So how do I install new fastboot drivers without the Device Manager?

OR

How do I make the Device Manager detect my phone while it's in fastboot?

I have Garmin Swim 2.

On my Pixel 3A XL installed Garmin Connect, it works fine.

But I want also see data on Google Fit.

Unfortunately Garmin Swim 2 doesn't connect with Google Fit and I need to install third party app do this.

I installed Health Sync.

Look like it's working:

But I don't see any activities in Google Fit where I didn't have my phone with me, for example swimming, sleep and so on.

On Garmin Forum I found the following:

in Settings of Google Fit, under Tracking Preferences, Turn off " Track your activities" Use Phone sensors to automatically track metrics like steps and distance.

Okay, I did this, but it didn't help.

What I should do to sync Garmin Connect with Google Fit?

When I'm on the go, I want to use internet tethering and debugging over USB to develop mobile apps with my Pixel 3A, but I don't want to charge the phone, because I want to waste energy on my MacBook as little as possible.

Is it possible to disable charging when the device is connected to my laptop, if so how? I know that I can set up debugging over WiFi and use a mobile hotspot, but I can't stand my hotspot performance and WiFi drains energy from my laptop as well.

I connect to my Wireguard endpoint with the official wireguard app. Everything works fine but in order to stop the VPN connection, I must find and restart the app.

Since the VPN activity is visible in the taskbar

... I was hoping for a way to quickly manage it from there.

Is this possible?

It disappeared out of the blue a few weeks ago. I searched the web and did a trick to make it reappear. It was shown for weeks and then suddenly disappeared again a few days ago.

What causes this, a bug?

I have a new Nokia 5.4 TA-1337 with Android 10. Every so often, the notification drawer that's supposed to come up when swiping down from the top of the screen (darkening the screen, showing the Wifi, Bluetooth, Do Not Disturb, Flashlight, Auto-Rotate and Battery Saver buttons/tiles, as well as any outstanding notifications) comes up at random.

It doesn't appear to be related to whether or not there are any new notifications. Sometimes it's also the other way around (the notification drawer disappearing when I actually wanted it).

It happens constantly (multiple times while writing this question alone).

What causes this? What can I do to fix it?

i root my Device (A320F)(Galaxy A3 2017) and after that enable adoptable storage via TWRP zip installer package ... every things is OK and with Titanium Backup Move All my app To adoptable storage ...

but now when i want to Update my app via play Store give me Error

and this is Full LogCat of Finsky : Download

i thinks interest line in log is

07-22 11:07:16.405 31501 31710 E Finsky  : java.io.IOException: Cannot automatically move com.alopeyk.customer from decf87e0-1c08-4b00-8cee-3a4d11ad36cc to internal storage

and with Install with adb from my PC this is Error :

and this is what happen when i try update any apps ..

I think if i fix mount point SD card address issue will be fixed but how ? please help

this is mount point in my device

Summary - Update 2:
I am not deleting the question content, to preserve history ( but an admin may if appropriate delete that content) but things have change since. A day after I can into the below mentioned TWRP createTarFork() error 255 issue I could manage the data restore /data from TWRP Nandroid backup. The issue is for 2nd install of the same stock ROM - I run into a bootloop. The TWRP backup itself was from an Encrypted partition being restored to another partition ( Encrypted or otherwise regardless ). Trying to get to the RC of the bootloop & some way I an restore my /data I've attached logs of bad & normal boot below.

this is older history. May go directly to update 1 below , skipping it :
Boot-looped and got stuck in powered by android logo. Logcat hasnt been much useful. Wanna know what's causing the stuck. All I have is this from /sys/fs/pstore/console-ramoops-0

'[email protected]::ISensorManager/default': No such file or directory

I am attaching Entire /sys/fs/pstore/console-ramoops-0

what seems the issue ?
I have TWRP backups of vendor system boot that i tinkered restores with. No Luck. This is stock MIUI ROM with TWRP as recovery base so after flashing dm-verify-no encrypt.zip ( cant recall the exact name ) + certification.zi & permssiver I get past MIUI logo but now looping at powered by android logo

fsck outcomes

    olivelite:/ # e2fsck /dev/block/mmcblk0p60
e2fsck 1.43.3 (04-Sep-2016)
/dev/block/mmcblk0p60: clean, 4614/65536 files, 184349/262144 blocks
olivelite:/ # fsck /dev/block/mmcblk0p60
/sbin/sh: fsck: not found
127|olivelite:/ # e2fsck -v /dev/block/mmcblk0p60
e2fsck 1.43.3 (04-Sep-2016)
/dev/block/mmcblk0p60: clean, 4614/65536 files, 184349/262144 blocks
olivelite:/ # e2fsck -v /dev/block/mmcblk0p59
e2fsck 1.43.3 (04-Sep-2016)
/dev/block/mmcblk0p59: clean, 4547/262144 files, 680379/1048576 blocks
olivelite:/ # e2fsck -v /dev/block/mmcblk0p62
e2fsck 1.43.3 (04-Sep-2016)
data: clean, 62826/1389536 files, 3383723/5667584 blocks
olivelite:/ # e2fsck -v /dev/block/mmcblk0p57
e2fsck 1.43.3 (04-Sep-2016)
/dev/block/mmcblk0p57: clean, 33/98304 files, 22707/98304 blocksenter 

fsck sounds clean for all partitions
Here is the **logcat** & here's **dmesg** from logcat it could be a decryption issue. But that's only for boot twrpasks for pattern and decrypts just fine. Why cant it happen during boot- that's my hunch on the prob. Not trying to lure in that direction. Like Mikko said pretty much everything screams so its difficult to nab the culprit
Gonna try /data backup wipe and restore lets see...
. Update
as I suspected it appears to be encryption related. the previous successful install had a pattern lock ( at the time that install was built, I flashed - permissiver.zip, certificate.zip & dm-verity-force-encryption w default ops to disable verity & disable forced encryption ) - butTWRP nandroid backup itself is never encrypted. When tried to restore it - I always ended up with TWRP createTarFork() error 255 which is a very generic error - with multiple RC's. In my case it happens immediately ( previous data was wiped & formatted all relevant partitions . Only way I could successfully restore was use flashtool ( that runs fastboot commands underneath ) to install stock -> fastboot twrp & patched magisk boot install and then restore /data ( after running magisk & dm verity attempt twrp restore ) - in that case restore was successful. So with above steps I could successfully restore /data but that restored /data will get stuck in bootloop ( if twrp backups arent encrypted , why then does a simple wipe & format not allow TWRP restore ? only flashtool de-novo stock install will permit restore ? . I read a bug in twrp will not let backup from encrypted partition be restored onto un-encrypted ..ok so I also encrypted de-novo stock install with same pattern & after successfully restoring /data got stuck in the same bootloop again ) .
while I am using this de-novo stock install right now with 'bare minimal survival kit' apps. I could pull up logs of what a successful boot looked like to compare with boot loop after /data restored I uploaded earlier ( as suggested by Mikko - need bad boot and normal boot logs to compare ) .
So the big Question
is how in the world can I get back /data to restore from my Nandroid backup without boot looping
Uploaded these :
Normal boot pmsg-ramoops , dmesg, ramoops ( last 2 are pretty much the same - if you read ramoops- good enough ), logcat Needless to say restore's being attempted on the same stock ROM

I have a galaxy S20+ and a generic USB c to HDMI cable. I connected the phone to a Philips monitor but I don't see anything on the monitor and in the USB settings I only see USB controlled by: connected device. And when trying to switch it to This device, I get an error saying "couldn't switch". Not sure if this cable isn't compatible by phones or if there's any settings I can change.

This is on a Samsung Galaxy S20e which came with Android 9 and was upgraded to 10.
If I enter only 4 characters, the OK button remains inactive.

I've tried with chrome://flags/# disabling tab-grid-layout reloading several times the browser, but no change works.

I've read a lot of articles on the web, some of them indicate this procedure, others to disable also flags like tab-groups, and so on, but currently nothing seems to work. (In fact, tab-groups, on the last Chrome realise, isn't available.)

Any solution?

I have a Samsung Galaxy Tab A 8.0". I haven't rooted the device (and don't really want to).

Until today, I was running Android 10. Today I installed an update that upgraded it to Android 11.

I'm using Termux (now installed from F-Droid) and PasswdSafe. (CORRECTION: I thought I was using the F-Droid version.)

Until now, I've been using Termux commands to copy my password database into a directory under /storage/emulated/0/data and using PasswdSafe to access it. After the update from Android 10 to 11, I can no longer access that directory from Termux. (The Unix permissions imply I should be able to; obviously there's an Android-specific restriction.)

$ ls -ld /storage/emulated/0/data
drwxrwx--- 4 root everybody 4096 Jun  9 21:12 /storage/emulated/0/data
$ groups
u0_a192 inet everybody u0_a192_cache all_a192
$ cd /storage/emulated/0/data
bash: cd: /storage/emulated/0/data: Permission denied
$

Ideally, I would like to have a directory such that both Termux and PasswdSafe have read/write access. Read/write access for Termux and read-only access for PasswdSafe would also work.

I also have an SD card mounted as /storage/0000-0000.

UPDATE: I thought I was using the version from F-Droid rather than from the Play Store, but both the Play Store and F-Droid on the device say I have termux version 0.101, while https://f-droid.org/packages/com.termux/ says the current version is 0.117. There may be a conflict, perhaps introduce when I did a factory reset a few weeks ago (it may have automatically reinstalled the Play Store version). I'll try completely uninstalling termux from the Play store and then installing from F-Droid.

UPDATE 2: I had thought that updating to the latest version Termux from F-Droid had fixed the problem, but there's still something odd (and possibly sporadic) going on. I'm not currently able to update files under /storage/emulated/0/data, or to cd to that directory. But I have files under that directory that were updated after I upgraded to Android 11, so I was able to at some point. I'll try to narrow down the problem.