text:
Samsung A20s stuck in safe mode and volume button is completely gone
I have Samsung Galaxy A20s. It's stuck in safe mode, and the volume button is completely gone.
I tried all the guides I could find to take off safe mode but my problem is not having volume buttons.
Can I use my PC instead, like USB debugging?

Sounds to me like at least one volume button is permanently firing even if not pressed. That is a hardware problem that can only be fixed on hardware level - that means you need to repair the volume buttons in a repair shop.

Wait for the battery to drop.
And do you have USB debugging on?


text:
Problems with wifi and mobile data after adb
This is problem I faced with: I was need to test a few features in a test app but my emulator had troubles with wifi connection so I decided to upload the app on my own cell phone through adb install "app".
After I setted up the proxy - adb shell settings put global http_proxy "ip":8181 (i was need to intercept a few request from the tesp app)
and the last thing I did were adb tcpip 9090 and adb connect "ip":9090 (for connecting over wifi).
That's all I did and the internet connection on my phone just disappeared (wifi and mobile data). I tried to reset networks setting but It doesn't working at all ofс I can do full reset but it's my plan "B" :)
But my telegram and WhatsApp works (I can text in it but when I try to search something my browser tell me: "No internet connection"

Remove the global proxy you set.

Thanks bud! This command adb shell settings put global http_proxy :0 will remove the proxy am I right?

Yes. Answered here.

source: Stack Exchange

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

sort: votes


text:
What is the official Android repository containing APKSIGNER?
What is the official source for apksigner as referenced e.g. in this answer? People are citing Android Studio, Android SDK Build Tools/Platform Tools/Command Line Tools etc. (as well as some shady archives on Google Drive), but non of these contain the program. I've downloaded, installed and searched them all.
Alternatively, what is the official source for Android SDK Build Tools 24.0.3, which allegedly contains the apksigner?
I've found an apksigner.jar and apksigner.bat inside a private Google repository, but running
apksigner verify --verbose --print-certs <APK file>
apksigner.bat verify --verbose --print-certs <APK file>
apksigner.jar verify --verbose --print-certs <APK file>

doesn't work (no output). This is the content of said batch file apksigner.bat:
@echo off
REM Copyright (C) 2016 The Android Open Source Project
REM
REM Licensed under the Apache License, Version 2.0 (the "License");
REM you may not use this file except in compliance with the License.
REM You may obtain a copy of the License at
REM
REM     http://www.apache.org/licenses/LICENSE-2.0
REM
REM Unless required by applicable law or agreed to in writing, software
REM distributed under the License is distributed on an "AS IS" BASIS,
REM WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
REM See the License for the specific language governing permissions and
REM limitations under the License.

REM don't modify the caller's environment
setlocal

REM Locate apksigner.jar in the directory where apksigner.bat was found and start it.

REM Set up prog to be the path of this script, including following symlinks,
REM and set up progdir to be the fully-qualified pathname of its directory.
set prog=%~f0

rem Check we have a valid Java.exe in the path.
set java_exe=
if exist    "%~dp0..\tools\lib\find_java.bat" call    "%~dp0..\tools\lib\find_java.bat"
if exist "%~dp0..\..\tools\lib\find_java.bat" call "%~dp0..\..\tools\lib\find_java.bat"
if not defined java_exe goto :EOF

set jarfile=apksigner.jar
set "frameworkdir=%~dp0"
rem frameworkdir must not end with a dir sep.
set "frameworkdir=%frameworkdir:~0,-1%"

if exist "%frameworkdir%\%jarfile%" goto JarFileOk
    set "frameworkdir=%~dp0lib"

if exist "%frameworkdir%\%jarfile%" goto JarFileOk
    set "frameworkdir=%~dp0..\framework"

:JarFileOk

set "jarpath=%frameworkdir%\%jarfile%"

set javaOpts=
set args=

REM By default, give apksigner a max heap size of 1 gig and a stack size of 1meg.
rem This can be overridden by using "-JXmx..." and "-JXss..." options below.
set defaultXmx=-Xmx1024M
set defaultXss=-Xss1m

REM Capture all arguments that are not -J options.
REM Note that when reading the input arguments with %1, the cmd.exe
REM automagically converts --name=value arguments into 2 arguments "--name"
REM followed by "value". apksigner has been changed to know how to deal with that.
set params=

:firstArg
if [%1]==[] goto endArgs
set a=%~1

    if [%defaultXmx%]==[] goto notXmx
    if %a:~0,5% NEQ -JXmx goto notXmx
        set defaultXmx=
    :notXmx

    if [%defaultXss%]==[] goto notXss
    if %a:~0,5% NEQ -JXss goto notXss
        set defaultXss=
    :notXss

    if %a:~0,2% NEQ -J goto notJ
        set javaOpts=%javaOpts% -%a:~2%
        shift /1
        goto firstArg

    :notJ
    set params=%params% %1
    shift /1
    goto firstArg

:endArgs

set javaOpts=%javaOpts% %defaultXmx% %defaultXss%
call "%java_exe%" %javaOpts% -Djava.ext.dirs="%frameworkdir%" -jar "%jarpath%" %params%

UPDATE: As suggested, I've now tried apksigner from Android Build Tools. Here is the output:
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): false
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
Signer #1 certificate DN: CN=Unknown, OU=Unknown, O=Fiducia IT AG, L=Unknown, ST
=Unknown, C=DE
Signer #1 certificate SHA-256 digest: 53a6afa8f0d219bba2fe84154f256ecec85b34175f
fee5b7387fda0afcc12605
Signer #1 certificate SHA-1 digest: addb5ed43a27660e41acb1d39e85ddd7b9c9807c
Signer #1 certificate MD5 digest: 1be8c130e83eb6b36e4aff93bcdd1b28
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: 671eafb570fa9e82cb7a8d5c435dad3d86990a09d5b
20f41b42e3152b3cd5a6a
Signer #1 public key SHA-1 digest: c021e779e6086e20a7c60b05a0c30b94c59c83ba
Signer #1 public key MD5 digest: d42dc7a6bcb0ace30d8ac316bc321c9c
WARNING: META-INF/androidx.navigation_navigation-fragment.version not protected
by signature. Unauthorized modifications to this JAR entry will not be detected.
 Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.camera_camera-camera2.version not protected by signat
ure. Unauthorized modifications to this JAR entry will not be detected. Delete o
r move the entry outside of META-INF/.
WARNING: META-INF/androidx.customview_customview.version not protected by signat
ure. Unauthorized modifications to this JAR entry will not be detected. Delete o
r move the entry outside of META-INF/.
WARNING: META-INF/services/ya.k not protected by signature. Unauthorized modific
ations to this JAR entry will not be detected. Delete or move the entry outside
of META-INF/.
WARNING: META-INF/androidx.room_room-runtime.version not protected by signature.
 Unauthorized modifications to this JAR entry will not be detected. Delete or mo
ve the entry outside of META-INF/.
WARNING: META-INF/androidx.camera_camera-lifecycle.version not protected by sign
ature. Unauthorized modifications to this JAR entry will not be detected. Delete
 or move the entry outside of META-INF/.
WARNING: META-INF/androidx.browser_browser.version not protected by signature. U
nauthorized modifications to this JAR entry will not be detected. Delete or move
 the entry outside of META-INF/.
WARNING: META-INF/com.google.android.material_material.version not protected by
signature. Unauthorized modifications to this JAR entry will not be detected. De
lete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.savedstate_savedstate-ktx.version not protected by si
gnature. Unauthorized modifications to this JAR entry will not be detected. Dele
te or move the entry outside of META-INF/.
WARNING: META-INF/androidx.activity_activity-ktx.version not protected by signat
ure. Unauthorized modifications to this JAR entry will not be detected. Delete o
r move the entry outside of META-INF/.
WARNING: META-INF/kotlinx_coroutines_play_services.version not protected by sign
ature. Unauthorized modifications to this JAR entry will not be detected. Delete
 or move the entry outside of META-INF/.
WARNING: META-INF/androidx.slidingpanelayout_slidingpanelayout.version not prote
cted by signature. Unauthorized modifications to this JAR entry will not be dete
cted. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.dynamicanimation_dynamicanimation.version not protect
ed by signature. Unauthorized modifications to this JAR entry will not be detect
ed. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.exifinterface_exifinterface.version not protected by
signature. Unauthorized modifications to this JAR entry will not be detected. De
lete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.sqlite_sqlite-ktx.version not protected by signature.
 Unauthorized modifications to this JAR entry will not be detected. Delete or mo
ve the entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-extensions.version not protected
by signature. Unauthorized modifications to this JAR entry will not be detected.
 Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.versionedparcelable_versionedparcelable.version not p
rotected by signature. Unauthorized modifications to this JAR entry will not be
detected. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-livedata-ktx.version not protecte
d by signature. Unauthorized modifications to this JAR entry will not be detecte
d. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.preference_preference-ktx.version not protected by si
gnature. Unauthorized modifications to this JAR entry will not be detected. Dele
te or move the entry outside of META-INF/.
WARNING: META-INF/androidx.preference_preference.version not protected by signat
ure. Unauthorized modifications to this JAR entry will not be detected. Delete o
r move the entry outside of META-INF/.
WARNING: META-INF/androidx.navigation_navigation-ui.version not protected by sig
nature. Unauthorized modifications to this JAR entry will not be detected. Delet
e or move the entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-runtime.version not protected by
signature. Unauthorized modifications to this JAR entry will not be detected. De
lete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.room_room-ktx.version not protected by signature. Una
uthorized modifications to this JAR entry will not be detected. Delete or move t
he entry outside of META-INF/.
WARNING: META-INF/androidx.appcompat_appcompat-resources.version not protected b
y signature. Unauthorized modifications to this JAR entry will not be detected.
Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.appcompat_appcompat.version not protected by signatur
e. Unauthorized modifications to this JAR entry will not be detected. Delete or
move the entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-livedata.version not protected by
 signature. Unauthorized modifications to this JAR entry will not be detected. D
elete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.navigation_navigation-runtime.version not protected b
y signature. Unauthorized modifications to this JAR entry will not be detected.
Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.navigation_navigation-runtime-ktx.version not protect
ed by signature. Unauthorized modifications to this JAR entry will not be detect
ed. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.window_window.version not protected by signature. Una
uthorized modifications to this JAR entry will not be detected. Delete or move t
he entry outside of META-INF/.
WARNING: META-INF/androidx.cursoradapter_cursoradapter.version not protected by
signature. Unauthorized modifications to this JAR entry will not be detected. De
lete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.savedstate_savedstate.version not protected by signat
ure. Unauthorized modifications to this JAR entry will not be detected. Delete o
r move the entry outside of META-INF/.
WARNING: META-INF/androidx.fragment_fragment.version not protected by signature.
 Unauthorized modifications to this JAR entry will not be detected. Delete or mo
ve the entry outside of META-INF/.
WARNING: META-INF/androidx.vectordrawable_vectordrawable.version not protected b
y signature. Unauthorized modifications to this JAR entry will not be detected.
Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.fragment_fragment-ktx.version not protected by signat
ure. Unauthorized modifications to this JAR entry will not be detected. Delete o
r move the entry outside of META-INF/.
WARNING: META-INF/androidx.sqlite_sqlite-framework.version not protected by sign
ature. Unauthorized modifications to this JAR entry will not be detected. Delete
 or move the entry outside of META-INF/.
WARNING: META-INF/androidx.core_core.version not protected by signature. Unautho
rized modifications to this JAR entry will not be detected. Delete or move the e
ntry outside of META-INF/.
WARNING: META-INF/androidx.vectordrawable_vectordrawable-animated.version not pr
otected by signature. Unauthorized modifications to this JAR entry will not be d
etected. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.localbroadcastmanager_localbroadcastmanager.version n
ot protected by signature. Unauthorized modifications to this JAR entry will not
 be detected. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-viewmodel-savedstate.version not
protected by signature. Unauthorized modifications to this JAR entry will not be
 detected. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.security_security-crypto.version not protected by sig
nature. Unauthorized modifications to this JAR entry will not be detected. Delet
e or move the entry outside of META-INF/.
WARNING: META-INF/androidx.navigation_navigation-common-ktx.version not protecte
d by signature. Unauthorized modifications to this JAR entry will not be detecte
d. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.biometric_biometric.version not protected by signatur
e. Unauthorized modifications to this JAR entry will not be detected. Delete or
move the entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-livedata-core.version not protect
ed by signature. Unauthorized modifications to this JAR entry will not be detect
ed. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.navigation_navigation-common.version not protected by
 signature. Unauthorized modifications to this JAR entry will not be detected. D
elete or move the entry outside of META-INF/.
WARNING: META-INF/kotlinx_coroutines_android.version not protected by signature.
 Unauthorized modifications to this JAR entry will not be detected. Delete or mo
ve the entry outside of META-INF/.
WARNING: META-INF/androidx.legacy_legacy-support-core-utils.version not protecte
d by signature. Unauthorized modifications to this JAR entry will not be detecte
d. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.viewpager2_viewpager2.version not protected by signat
ure. Unauthorized modifications to this JAR entry will not be detected. Delete o
r move the entry outside of META-INF/.
WARNING: META-INF/androidx.transition_transition.version not protected by signat
ure. Unauthorized modifications to this JAR entry will not be detected. Delete o
r move the entry outside of META-INF/.
WARNING: META-INF/androidx.print_print.version not protected by signature. Unaut
horized modifications to this JAR entry will not be detected. Delete or move the
 entry outside of META-INF/.
WARNING: META-INF/androidx.documentfile_documentfile.version not protected by si
gnature. Unauthorized modifications to this JAR entry will not be detected. Dele
te or move the entry outside of META-INF/.
WARNING: META-INF/androidx.core_core-ktx.version not protected by signature. Una
uthorized modifications to this JAR entry will not be detected. Delete or move t
he entry outside of META-INF/.
WARNING: META-INF/androidx.emoji2_emoji2-views-helper.version not protected by s
ignature. Unauthorized modifications to this JAR entry will not be detected. Del
ete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.recyclerview_recyclerview.version not protected by si
gnature. Unauthorized modifications to this JAR entry will not be detected. Dele
te or move the entry outside of META-INF/.
WARNING: META-INF/androidx.tracing_tracing.version not protected by signature. U
nauthorized modifications to this JAR entry will not be detected. Delete or move
 the entry outside of META-INF/.
WARNING: META-INF/androidx.startup_startup-runtime.version not protected by sign
ature. Unauthorized modifications to this JAR entry will not be detected. Delete
 or move the entry outside of META-INF/.
WARNING: META-INF/androidx.navigation_navigation-fragment-ktx.version not protec
ted by signature. Unauthorized modifications to this JAR entry will not be detec
ted. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-livedata-core-ktx.version not pro
tected by signature. Unauthorized modifications to this JAR entry will not be de
tected. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.arch.core_core-runtime.version not protected by signa
ture. Unauthorized modifications to this JAR entry will not be detected. Delete
or move the entry outside of META-INF/.
WARNING: META-INF/androidx.emoji2_emoji2.version not protected by signature. Una
uthorized modifications to this JAR entry will not be detected. Delete or move t
he entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-viewmodel-ktx.version not protect
ed by signature. Unauthorized modifications to this JAR entry will not be detect
ed. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-runtime-ktx.version not protected
 by signature. Unauthorized modifications to this JAR entry will not be detected
. Delete or move the entry outside of META-INF/.
WARNING: META-INF/services/ta.z not protected by signature. Unauthorized modific
ations to this JAR entry will not be detected. Delete or move the entry outside
of META-INF/.
WARNING: META-INF/INDEX.LIST not protected by signature. Unauthorized modificati
ons to this JAR entry will not be detected. Delete or move the entry outside of
META-INF/.
WARNING: META-INF/androidx.activity_activity.version not protected by signature.
 Unauthorized modifications to this JAR entry will not be detected. Delete or mo
ve the entry outside of META-INF/.
WARNING: META-INF/androidx.drawerlayout_drawerlayout.version not protected by si
gnature. Unauthorized modifications to this JAR entry will not be detected. Dele
te or move the entry outside of META-INF/.
WARNING: META-INF/androidx.interpolator_interpolator.version not protected by si
gnature. Unauthorized modifications to this JAR entry will not be detected. Dele
te or move the entry outside of META-INF/.
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/.
WARNING: META-INF/androidx.lifecycle_lifecycle-viewmodel.version not protected b
y signature. Unauthorized modifications to this JAR entry will not be detected.
Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.camera_camera-core.version not protected by signature
. Unauthorized modifications to this JAR entry will not be detected. Delete or m
ove the entry outside of META-INF/.
WARNING: META-INF/androidx.swiperefreshlayout_swiperefreshlayout.version not pro
tected by signature. Unauthorized modifications to this JAR entry will not be de
tected. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-service.version not protected by
signature. Unauthorized modifications to this JAR entry will not be detected. De
lete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.lifecycle_lifecycle-process.version not protected by
signature. Unauthorized modifications to this JAR entry will not be detected. De
lete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.loader_loader.version not protected by signature. Una
uthorized modifications to this JAR entry will not be detected. Delete or move t
he entry outside of META-INF/.
WARNING: META-INF/androidx.viewpager_viewpager.version not protected by signatur
e. Unauthorized modifications to this JAR entry will not be detected. Delete or
move the entry outside of META-INF/.
WARNING: META-INF/androidx.cardview_cardview.version not protected by signature.
 Unauthorized modifications to this JAR entry will not be detected. Delete or mo
ve the entry outside of META-INF/.
WARNING: META-INF/androidx.navigation_navigation-ui-ktx.version not protected by
 signature. Unauthorized modifications to this JAR entry will not be detected. D
elete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.coordinatorlayout_coordinatorlayout.version not prote
cted by signature. Unauthorized modifications to this JAR entry will not be dete
cted. Delete or move the entry outside of META-INF/.
WARNING: META-INF/kotlinx_coroutines_core.version not protected by signature. Un
authorized modifications to this JAR entry will not be detected. Delete or move
the entry outside of META-INF/.
WARNING: META-INF/androidx.camera_camera-view.version not protected by signature
. Unauthorized modifications to this JAR entry will not be detected. Delete or m
ove the entry outside of META-INF/.
WARNING: META-INF/androidx.annotation_annotation-experimental.version not protec
ted by signature. Unauthorized modifications to this JAR entry will not be detec
ted. Delete or move the entry outside of META-INF/.
WARNING: META-INF/androidx.sqlite_sqlite.version not protected by signature. Una
uthorized modifications to this JAR entry will not be detected. Delete or move t
he entry outside of META-INF/.
WARNING: META-INF/androidx.core_core-splashscreen.version not protected by signa
ture. Unauthorized modifications to this JAR entry will not be detected. Delete
or move the entry outside of META-INF/.

What is the meaning?

You forgot to include the error message(s) that you get when you try to execute apksigner. Without them it is difficult to guess what is going wrong. jar files have to be started by the command java -jar apksigner.jar arguments_to_apksigner. The recommended Java version is at the moment 11.

Cross-posted from Stack Overflow: https://stackoverflow.com/q/72876327/2821954

@Robert But that is precisely the issue: There is no error message from apksigner, just a blank line in the CLI

I have extended my original answer by a section how to get apksigner without installing Android SDK or Android Studio:
Apksigner is a Java tool and Google provides for start-up a batch file apksigner.bat(Windows) respectively a shell script apksigner.sh (Linux, MacOS).
As mentioned before it is included in each build-tools version of Android SDK. If you don't want to install the whole Android SDK (with or without Android Studio) you can directly download build tools and extract and execute apksigner. Links to the all build-tools are provided on this website (the provided links go to the original Google download locations).
I prefer apksigner from build-tools v30:

build-tools 30.0.1 Linux
build-tools 30.0.1 MacOS
build-tools 30.0.1 Windows

You only need the file lib/apksigner.jar from the archive (thus it doesn't matter for which platform you download the build-tools package). Extract it  and open a shell in the folder. Then execute java -jar apksigner.jar.
To execute you need Java 9 or higher (best one of the Java LTS versions 11 or 17 - e.g. the Eclipse Adoptium OpenJDK release https://adoptium.net).
Using this direct approach the command to execute apksigner is
java -jar apksigner.jar verify --verbose --print-certs "Signal-website-universal-release-4.49.13.apk"

...that is a much more rounded answer now. But it leaves one important aspect unanswered: What about official sources? Is the Google repository that you linked an official source, i.e. can it be trusted? If so, on what basis? On first glance, it could be someone's private Google drive with malware-loaden files. And we're lacking an official source, there is no way for us (at the moment) to verify the authenticity of any of those files from that Google drive. Remember that this question relates to software authentication issues - you can't authenticate software using compromised tools

(The unspoken assumption here, of course, is to consider Google Inc. itself a trusted source - which it is not, as exhaustively proven. So strictly speaking, we're still talking about relative security with the metric "authenticity of software relative to its original".)

@kerstin92 Please have a look into the URLs they are dl most likely for download so the host should be unrelated to Google Drive. As far as I know these are the same URLs use by Android SDK for download. If you are unsure about authenticity then please just use the official Android SDK with Android Studio download link from Google web pages.

So these are official Google repositories?

"If you are unsure about authenticity then please just use the official Android SDK with Android Studio download link from Google web pages." - Android Studio doesn't contain apksigner. If you think it does, you may point towards the exact folder

@kerstin92 Android Studio itself doesn't contain apksigner, but it should contain the official Android SDK Manager that users can use to download any version of build tools from there. The download location will be the same as the location of the Android SDK Manager. Also, yes, dl.google.com is the official Google repo; the linked URL is the same as the one used by the Android SDK Manager.

@kerstin92 If you download and install Android Studio at the end of the installation Android Studio will start, you have to accept the Android SDK license and automatically build-tools for API 33 is downloaded. If you modify the installation and don't start Android Studio at the end the installation is incomplete and thus you don't have apksigner. After a full installation Apksigner can be found here: C:\Users\%username%\AppData\Local\Android\Sdk\build-tools\33.0.0\apksigner.bat

@Robert That is super weird. I ran the installation with all options enabled, but didn't immediately start Android Studio but closed the installer first. Does that mean that Build Tools only get installed if Android Studio is immediately launched after installation, directly from the installer, and never if the installer is closed (without any notification indicating this and no option to install it afterwards)? That would be some truly bizarre behavior

@kerstin92 I assume that build-tools are always automatically installed on first start of Android Studio. As Andrew already mentioned you can install all SDK components at any time using the Android Studio integrated SDK manager.

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Google Keep keeps signing me out
The following messages appear

You’ve been signed out. Please reload the page to sign in again and continue working.
Access to Keep is unauthorized.

Tried both browser and app, but did not work.
Only happen on one account.
Time happened: 06/07/2022.
Location: UTC+7.
Does my account get locked or is it a server-side problem?

Related issue (in 2017): "Access to Keep is unauthorised" error message, but looks like there's no service disruption on the Google side at the moment.

I'm also on UTC+7, but I didn't face this issue at all. However, I'm afraid it's unlikely for us to know if your account is locked or not because we're not Google support.

This sounds like someone is signing your session out from account security controls.  Verify your account is secure, sign all other sessions out, change password, turn on 2FA, and verify no backup recovery method is insecure.

If it continues to occur, you may want to check that your emails and SMS are not being forwarded out, or if your mobile account has eSIM's/DIGITS provisioned without your knowledge.

It's fixed now i dont know what happen it's just occurs without  any  notification


text:
Is it possible to dump an Android partition with file-based encryption (FBE)?
Consider an unrooted Android 9.0 device with file-based encrypted (FBE), a locked bootloader and only recovery and download modes available. Is there any way to dump the internal storage either to the SD card or via USB, especially the user data partition /data?
Note: The objective is not to decrypt the data, but merely to gain read access to the bit patterns residing in /data.

You're only hope (without physically accessing the disk) would be through ADB and I don't think there are any commands that will do as you ask. But even if there is a command, FBE encrypts the file system with a Device Encryption (DE) key, meaning the data be extra useless unless you can physically extract the DE key from the device. Also, the DE key is per user too, so you can't even root the phone afterwards to perform cryptographic operations with the DE key (factory reset wipes the old DE key and creates a new user with a new DE key).

I should add that this is specific to Android 10+. Older versions that supported FBE had fewer protections (i.e. meta-data wasn't required to be encrypted prior to Android 10+).

@free_coupons_for_sale_1023 "FBE encrypts the file system with a Device Encryption (DE) key" - What does this imply? Are you suggesting that on top of a file-by-file encryption there is an additional layer that encrypts the entire disk again (meaning an additional encryption of the already individually encrypted files)? Please clarify

DE and CE keys are loose terms. They just refer to keys that are derived from the device itself versus the user's credentials, respectively. The key that is used to encrypt the file system contents is derived from both a device generated key and the user's credentials. This means that decrypting data straight from disk needs more than just the password, it needs a DE key. And the phones that provide a StrongBox will require physical extraction of the keys from the StrongBox. For phone's like the Pixel 6, the StrongBox has built in tamper detection.

@free_coupons_for_sale_1023 This if off-topic

You asked me to clarify what I meant. I guess I didn't explicitly answer your question, so I will do that now: "Are you suggesting that on top of a file-by-file encryption there is an additional layer that encrypts the entire disk again" -- No, the file system contents is not encrypted twice (at least no in this aspect). Rather, the encryption key that is used is partly derived from a DE key. So, if you want to look at the raw data of the disk, then you're going to see garbage regardless of whether you have user credentials or not. If this hasn't been helpful, let me know and I'll delete it.

@free_coupons_for_sale_1023 No, that was actually helpful. The reason behind this question is not decryption of data (as stated explicitly), but targeting individual files for deletion (e.g. setting all bits to zero). In order to do this, I need the information of how files are distributed over the memory, i.e. where the bits that make up a file are located. This information would be inaccessible if the entire disk had an additional encryption layer. If, however, only individual files are encrypted, then their individual memory locations should be stored somewhere in clear text...

...i.e. beginning of file, end of file, and maybe offsets if the file is fragmented. And this location map of files is what I need access to, so I can pick out a specific memory region that is occupied by a single file (and by that file only) and flip the bits so as to delete it.

It is not possible to dump the userdata partition. According to the FBE docs:

The recovery partition is unable to access the DE-protected storage on the userdata partition.

Therefore, you won't be able to read the userdata partition without extracting the storage drive from the device. Furthermore, if you are running Android 11+, then the filesystem metadata is encrypted with a device encryption key. So if your goal is to determine the location of a file, you would also need to extract the DE key from the physical component that protects it, if applicable.
From as far as I can tell, unless you have a cyber forensics lab, there is not an easy way to even get read access to the partition.
EDIT:
Looking at your previous question, it sounds like you soft-bricked your device. In which case, if your goal is to recover the device, you can't without root, as mentioned on this XDA thread:

It fails because it's a system app. With root it's possible to install it but not without.
You need to do a factory reset from recovery to get all the apps in /system/app and /system/priv-app back.

Comments are not for extended discussion; this conversation has been moved to chat.

you can dump it with a bootloader exploit like kamakiri or direct access to the chip, see forensicswiki


text:
Does File-Based Encryption (FBE) in contrast to Full-Disk Encryption (FDE) allow deletion of individual encrypted files?
As far as I understand, Android 9.0 switched from Full-Disk Encryption (FDE) to File-Based Encryption (FBE), which means that encryption is done on a file-by-file basis by default.
If Android no longer encrypts the entire internal storage (or partitions) but only individual files, shouldn't it also be possible to delete individual encrypted files, preferably from an unrooted device?

Going by your comments below you might wish to [edit] your question to include your reason – i.e. along the lines of "I need to delete {this file}, how can I do this", which would increase chances to get the answer you're after. // Apart from that: I did not check, but FBE might also encrypt the file (and directory) names – so though you might be able to delete a specific file you'd have a hard time identifying it. Next question left is: can you access that file at all (without root)?

@Izzy "I did not check, but FBE might also encrypt the file (and directory) names" - Did you seriously just rephrase my question and frame it as some sort of answer?? xD

Of course, what else? You didn't even ask your real question ;) As for the quoted part: See my comment below. I'm using FBE on my Linux machine, and file names as well as directory names are encrypted along – so all you can see is "garbage". // And now it's your turn to [edit] your question to fit the "narrative" you really have in mind :D People can only answer questions as they are – and yours seems to miss the part you really wanted to ask (going by your comments).

As you don't ask the question you want to have answered, I won't place an answer – but you can read the specs yourself (keyword: metadata encryption). As for expertise, check my profile and my publications, they should speak for themselves. Also hover your mouse over the diamond next to my username for some additional clues ;) That said, I withdraw from here as I see my help is not wanted. Hope you still find the facts you're looking for.

Warning: I am not a security expert.
The samsung link you provided says:

Each file is independently encrypted using AES-256-XTS, with a unique File Encryption Key that is derived from a Primary Key.

Which means that a non-credential encrypted (possibly unencrypted) copy of the location of the files must be stored somewhere. Therefore, in theory, if a person had physical access to the device, then they would be able to derive each files location without the user's credentials.
That being said, why are you worried about someone deleting individual files as opposed to deleting an entire disk? If someone has the ability to selectively delete data from the phones storage, then you're already screwed.

@free_coupons_for_sale_1023: Actually, I'm the one in need of a deletion after accidentally uninstalling a system app via ADB shell using pm uninstall, which modifies an app configuration file inside the secured user data partition (/data/system/users/0/package-restrictions.xml to be exact). A stock version of this config file is automatically restored on boot upon deletion, so deleting this file solves my problem.

@free_coupons_for_sale_1023: By the way, the requirement for deletion is not by my own choice, but imposed through Android's security architecture (see source.android.com/security/verifiedboot, source.android.com/security/trusty, developer.samsung.com/teegris/overview.html) which is prone to locking out the owner from his/her own data.

That post is not related to my question and does not provide an answer either.

Edited as there was some confusion. Changed wording from "an unencrypted (at lease not credential encrypted)" to "a non-credential encrypted (possibly unencrypted)". This is to emphasizes that meta-data may be encrypted (the samsung link doesn't specify), but not by user credentials. This means that if the person had physical access to the phone, its theoretically possible to unencrypt the meta-data (by physically extracting the DE key), without user credentials.

No idea how you get to the conclusion that an unencrypted copy must be stored somewhere. I'm using FBE on my Linux machine, it only stores the encrypted files. The "unencrypted copy" is rather "virtual"; think of it as a "file system driver" which shows the encrypted files through an additional layer as the corresponding unencrypted content (and file name). Next, the difference to FDE is that, with the device locked, using FDE you couldn't even access the "drive" to delete anything, while with FBE you can access the disk but not read the files (or their names).

@Izzy I think he's referring to the meta data of files (or memory addresses/ranges)

Same comment to that: what is the conclusion based upon? What sense would it make to encrypt something while keeping the clear copy around?

@Izzy Think about this: If an individual file and its metadata is encrypted, then how do you find the location of the encrypted file on the disk to decrypt it? You wouldn't be able to. The answer is that the metadata is not encrypted with user credentials. Or equivalently, "a non-credential encrypted (possibly unencrypted) copy of the location of the files must be stored somewhere."

Not necessarily. There could be an encrypted container holding the metadata. Note that the specs clearly say both are encrypted. When decrypting, the entire structure is decrypted – not each entry separately. If you've ever used something like GoCryptFS (which I use on my Linux machine) you will see what I mean: GoCryptFS is basically FBE. It works on directory level, though (encrypting every file in-place). You can move the entire dir and mount it somewhere else, even on another machine. So there's no unencrypted copy involved.

@Izzy Let's move to chat


text:
Anbox doesn't have a WiFi in settings
I installed an Anbox to test a few features in a test app (the app needs a WiFi connection) but I found out that I don't have WiFi in the settings. Don't know what to do.

I installed an Anbox without snap:
1)apt install anbox
2)mkdir /var/lib/anbox
3)mv android_amd64.img /var/lib/anbox
Image was downloaded from https://build.anbox.io/android-images/2018/07/19/

I would assume that this is because Anbox is not an emulator but just a run-time container for Android apps. It just provides network access without emulating a mobile or Wifi connection.

Based on Docs » Advanced use » Network Configuration, I think Robert is right.

Thanks, I checked this, really I have an anbox0: 'ip' but why I don't have any internet connection? I'm trying to use a "WebView browser" in the anbox and always get this ERROR: Webpage not available  The webpage https://google.com/ could no be loaded because: net::ERR_PROXY_CONNECTION_FAILED
When I use ifconfig inside of the container I don't see my wlan0 (only lo and eth0).


text:
Can't install TWRP to my Xiaomi Mi 11 Lite 5G NE (lisa)
Every time I try to install TWRP (or any other custom recovery) to my Xiaomi Mi 11 Lite 5G NE (lisa), I get these errors.
If I try fastboot flash recovery TWRP.img, I get this error:
Sending 'recovery' (196608 KB)                                             OKAY [  4.826s]
Writing 'recovery'                                        FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed

And every time I try to boot into the recovery immediately: fastboot boot TWRP.img, it boots but the screen stays black.
Windows makes the connected sound, and if I check adb devices, it shows that the device is in recovery mode. But I can't see any recovery on my phone.
I tried it with 4 different custom recoveries and all of them gave the same errors/reactions.
How can I fix this?

I'm not an expert at all on partition and image flashing, but from the error (recovery_a) No such partition, looks like the recovery partition was deleted? Did you do something else before this issue started happening?

I don't believe that device has separate recovery partition at all


text:
How to make sure Android'a notification can give sound and vibrate?
I bought some Xiaomi phones to play video games, and then set a notification so that when something happens in the game while I am on the computer, then the phone would play some audio and also vibrate.
However, it is strange that some phone would do both. Some only vibrate, and some do not do either, but just slide down a narrow dialog at the top of the screen for a few seconds. It is even the case that a phone that played audio would stop playing audio a few days later, with nothing changed for the notification settings.
Is there a way to make them all work reliably?
I was thinking of the Do Not Disturb but the notifications are set to "give notification even in Do Not Disturb mode", so this should not be the reason.

Based on the notification you can use automation to trigger playing audio and vibrate

Example


text:
How to change microphone volume/gain settings in LineageOS?
I'm using LineageOS (it says it is Android 10).
First time I'm trying to use headphone mic, and I got very surprised (and very, very pissed) that there isn't anything in Settings where I can regulate which mic do I want to be active, and the gain/volume for the microphone.
So is it possible to change microphone settings in LineageOS - and if so, how?

I also had a microphone volume problem in recording apps (not on phone calls).
It's probably very device and OS specific, but I was able to change it by editing /system/vendor/etc/mixer_paths_0.xml. It requires root to mount /system -o remount,rw and to write the file.
In the following section I changed the MIC3 Volume value from 4 to 25 :
        <path name="gain-media-headset-mic">
                <ctl name="MIC3 Volume" value="4" />
                <ctl name="MIC3 Boost Volume" value="2" />
                <ctl name="ADC Left Gain" value="127" />
                <ctl name="ADC Right Gain" value="127" />
        </path>

The phone is on LineageOS 16 (Android 9).


text:
POCO M3 Pro 5g not booting up after unexpected shutdown. It does not charge as well
I was using my phone scrolling on Facebook then it suddenly shuts down. After that I tried to boot it but after holding the power button for 15 secs It shows that its out of battery. but I know my battery life was at 98% cause I just finished charging.
1 day has passed since.
Here's what It tried so far but failed:

I charge my phone but the charging screen does not appear. but it only shows the empty battery screen.
Tried to hard reset by holding the power button and volume down.
Drain the battery for 1 day then booting it.
Boot it while charging.
Hard reset while charging.
Tried to charge it for up to 2hrs then boot it.

Can someone tell me what's the the problem and how I can fix it?

https://forum.xda-developers.com/t/4465909

I was the one who ask this one. Wanted to get answers from multiple channels.


text:
Everything freezes during booting virtual device in genymotion/android studio
I can't understand what's going -  every time I try to boot virtual device in genymotion or android studio my laptop just freezes and needs to reboot. Every process just stuck. Can't fix this problem.
I boot my Linux from an external ssd.
Technical parameters of my computer is more over than enough to using android emulator like android studio or genymotion (i7-10750H and 2070 RTX).
Any ideas?

Have you tried what happens if you create a regular VirtualBox virtual machine and boot it? If it also freezes then it is a pure VirtualBox problem and thus unrelated to Android.

I don't try any VM yet. I will try.
I want try to check virtualization on my kali (it's not on VM) but don't know how.


text:
How can I see which Google account WhatsApp is using for its backing up?
How can I see which Google account WhatsApp is using for its backing up?
For example, I have various Google accounts on my phone.

From the WhatsApp app, go to Settings - Chats - Chat backup. Under "Google Drive settings", there is "Google Account" entry that shows the current Google account used to backup.
It is also possible to change the Google account from there. From WhatsApp FAQ - How to back up to Google Drive

Change the account you want to use for backups

Open WhatsApp.
Tap More options > Settings > Chats > Chat backup > Google Account.
Select the Google account you’d like to back up your chat history to.

Note: If you change your Google account, you’ll lose access to any backups saved in that account.


text:
Three different APK file sizes for the same version/build app?
I'm getting three different APK file sizes for supposedly the same version/build app:

Version
1
from Evozi: 22.485.694 bytes

Version
2
from Apkpure: 22.766.408 bytes

Version 3 from Aptoide:
18.641.648 bytes

Why?
Which file is the original one and which two are fakes? Could you please confirm that the Evozi downloader is trying to "slip" you a APK version (here: 2.7.2) different from the Google Play store link that you provided (here: 2.7.3) or that both Apkpure and Aptoide are claiming publishing more recent publishing dates (here: 08-09-2021 and 14-09-2021) than the original (06-09-2021)? Why is this happening?
UPDATE 1: As per request, I've extracted all APKs. The results are even more concerning:

Version 1 from Evozi: 957 Files, 51 Folders, 24.757.075 bytes

Version 2 from Apkpure: 819 Files, 21 Folders, 25.118.159 bytes

Version 3 from Aptoide: 4319 Files, 101 Folders, 31.704.315 bytes

...4319 files?!
UPDATE 2: As suggested, I used apksigner to take a look at the certificates inside the APKs:
Version 1 from Evozi: 957 Files, 51 Folders, 24.757.075 bytes
C:\Users\...\Desktop>java -jar apksigner.jar verify --verbose --print-certs com.starfinanz.mobile.android.dkbpushtan_30044_apps.evozi.com.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): false
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
Signer #1 certificate DN: CN=Niels Mathea, OU=IT Betrieb Bank, O=DKB Service GmbH, L=Potsdam, ST=Brandenburg, C=DE
Signer #1 certificate SHA-256 digest: e5067dca4553173a1dd76352a8287b293960119689244ac58d0552703efe4268
Signer #1 certificate SHA-1 digest: b4199718eaa0e676755af77419fb59abf7fece00
Signer #1 certificate MD5 digest: 0a566744818c6fb89f4c900a1502cf1c
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: d878ba65ddcd7bbd0d9fd284f0bc61762c7ecb83ecb6c58c8c138939fb661f7f
Signer #1 public key SHA-1 digest: dbf739ed124f07181b3cdd1867bdd0eb63da3d71
Signer #1 public key MD5 digest: 94fcb9a87a8ec48eed706456a93ab0cd
WARNING: META-INF/androidx.customview_customview.version not protected by signature. Unauthorized modifications to this JAR entry will not be detected. Delete or move the entry outside of META-INF/.
[...]

Version 2 from Apkpure: 819 Files, 21 Folders, 25.118.159 bytes
C:\Users\...\Desktop>java -jar apksigner.jar verify --verbose --print-certs "DKB TAN2go_v2.7.3_apkpure.com.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): false
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
Signer #1 certificate DN: CN=Niels Mathea, OU=IT Betrieb Bank, O=DKB Service GmbH, L=Potsdam, ST=Brandenburg, C=DE
Signer #1 certificate SHA-256 digest: e5067dca4553173a1dd76352a8287b293960119689244ac58d0552703efe4268
Signer #1 certificate SHA-1 digest: b4199718eaa0e676755af77419fb59abf7fece00
Signer #1 certificate MD5 digest: 0a566744818c6fb89f4c900a1502cf1c
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: d878ba65ddcd7bbd0d9fd284f0bc61762c7ecb83ecb6c58c8c138939fb661f7f
Signer #1 public key SHA-1 digest: dbf739ed124f07181b3cdd1867bdd0eb63da3d71
Signer #1 public key MD5 digest: 94fcb9a87a8ec48eed706456a93ab0cd
WARNING: META-INF/androidx.customview_customview.version not protected by signature. Unauthorized modifications to this JAR entry will not be detected. Delete or move the entry outside of META-INF/.
[...]

Version 3 from Aptoide: 777 Files, 21 Folders, 25.059.540 bytes
C:\Users\EPI-SMLM\Desktop>java -jar apksigner.jar verify --verbose --print-certs  com-starfinanz-mobile-android-dkbpushtan-30049-59302957-c297d2d2df90587173f6f8b78fce939d.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): false
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
Signer #1 certificate DN: CN=Niels Mathea, OU=IT Betrieb Bank, O=DKB Service GmbH, L=Potsdam, ST=Brandenburg, C=DE
Signer #1 certificate SHA-256 digest: e5067dca4553173a1dd76352a8287b293960119689244ac58d0552703efe4268
Signer #1 certificate SHA-1 digest: b4199718eaa0e676755af77419fb59abf7fece00
Signer #1 certificate MD5 digest: 0a566744818c6fb89f4c900a1502cf1c
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048
Signer #1 public key SHA-256 digest: d878ba65ddcd7bbd0d9fd284f0bc61762c7ecb83ecb6c58c8c138939fb661f7f
Signer #1 public key SHA-1 digest: dbf739ed124f07181b3cdd1867bdd0eb63da3d71
Signer #1 public key MD5 digest: 94fcb9a87a8ec48eed706456a93ab0cd
WARNING: META-INF/androidx.customview_customview.version not protected by signature. Unauthorized modifications to this JAR entry will not be detected. Delete or move the entry outside of META-INF/.
[...]

There is a long list of warnings coming with each APK. Also, as indicated in the comments, Aptoide provided the wrong APK - file size and number of contained files/folders have been updated.
Anyone know what to make of this output?

Comments are not for extended discussion; this conversation has been moved to chat.

If you have multiple APK files from different untrusted sources it is wise to question their authenticity. You already performed the basic steps for doing so, especially checking their cryptographic signatures using apksigner is the most important one.
From the apksigner output the most important part is the certificate SHA-256 digest. APKs that have the same certificate SHA-256 hash are guaranteed to come from the same developer (assuming the keys has not ben lost/stolen, or the developer has sold the project to a different developer).
In your case the versions from Evozi and Apkpure have the same hash but the one from Aptoide is totally different, even the certificate DN is totally different. The reason for that I will explain at the end of this answer, first focus on Evozi and Apkpure.
Evozi and Apkpure
You know that both versions come from the same developer, but the authenticity of that developer is still unknown. As there is no directory where you can look-up Android developer certificate hashes we have to improvise.
So we end up for the certificate SHA-256 and SHA-1 hash (SHA-1 is no longer the best for security but it still costs several thousand dollar and a lot of time to break it) on popular search engines like Google. If you do so you will find plenty of entries for the SHA-1 hash that all belong to download site or threads about the DKB app. And the posts are not all new but go back e.g. to 2017, so the chance is high that both APKs from Evozi and Apkpure are genuine.
But then the question remains why are they different?
You have to know that there are several reasons why they are different.
Different internal version?
Android apps have two version numbers: the versionName (a string with arbitrary content) that is displayed to the user and one internal versionCode number that is a plain integer number which is increasing at least by one with every new version (no commas, dots, and so on are allowed). To check the internal versionCode we  have to look into the decoded AndroidManifest.xml of each APK. On a PC I prefer Jadx for doing so.
Evozi version:
android:versionCode="30044" android:versionName="2.7.2"

ApkPure version:
android:versionCode="30049" android:versionName="2.7.3"

As you can see both APKs have a different internal and external version as both version values are different.
A lot APK download sites to not gather APK files on their own, instead they rely on user uploads. Also APK files don't contain a release date, therefore those site use the upload date to them as date they display. So the date shown on Evozi and ApkPure is usually days or even weeks after the official release date.
But it would have been possible that only versionCode differs and versionName stays the same. In such a case there would be two possibilities:

Multiple versions had been released without changing the public version number, e.g. because there was a minor bug that had been fixed in the newer version, and the developer decided that this change was too small for a new version number.

The Android eco system is very fragmented. Different Android versions and Android hardware with very different hardware is used (e.g. screen size and density). Originally Android APKs were designed to include everything for every hardware configuration but that increased the app size and consumed storage and internet traffic that was partially unnecessary. So Google introduced multiple features to address that problem. Starting from the possibility to provide different APKs for different device types or model up to the newest system that the developer uploads an app bundle and Google generates the final APK file(s) individually for each device model.

Aptoide
Aptoide in difference to other sites which provides APK files for download is not a download site, instead it is an App store. This means the download they provide on their web site are not the app you have searched for. Instead it is the Aptoide app store app. This explains the different signature, certificate DN and the totally different content of the downloaded APK file.
But the Aptoide APK file you have downloaded is not just the general store app, it is a special version that contains the meta data of the app you wanted to download. Once you have installed this Aptoide app store app an dialog opens and asks if you want to download and install the linked "DKB-TAN2go" app.


text:
Encrypting an SD card so that it will also work on a new phone
I have a LG G8 running Android 10. Your basic, unrooted, stock ROM phone commercial phone. It has a 64GB SD card where I place most of my data.
I want to know how I could achieve the following 2 goals simultaneously:

I'd like the files on the SD card to be encrypted so that if I lose my phone, the person who finds it cannot access the data on the SD card

If the phone dies on me, I'd like to be able to access the data on the SD card, simply by inserting the card in a new Android phone. Since it's encrypted, I'm fine with entering a password or decryption key that I would extract from my current phone.

Caveats:

My future phone will be by a different manufacturer since LG has abandoned Android manufacturing. So no suggestions specific to my current phone.
I don't want to set up proper backup for my SD card (eg using SyncThing or similar tools). I already know how to do backups, and it's what I'll do if there is no other choice, it's just common sense.
I don't want to use 3rd party commercial apps or (more tolerable) open-source/F-Droid apps, though you are free to mention them for other people who find this question. I want a solution supported by the base Android OS (eg Developer Mode), or with standard tools like adb.
I don't want to root my phone or change my ROM from the stock

There are other questions similar to mine (5 to 10 years old), where the answer is "you can't decrypt your encrypted SD card from your old phone". But in all those questions the OP has broken his/her old phone, or forgotten the password. That is not my case, my phone still works, and I can take action to prepare for the future.

Afraid you might be asking the impossible. If you want a manufacturer/device independent encryption "in userland", to my knowledge there's nothing offered by the "stock system" (you'd at least need root to extract the keys) – so going with a 3rd-party app will be your only option. You can find some candidates in my corresponding app listing.

So even with Developer Mode and adb, I cannot extract the encryption keys, and in the future transfer them to a new phone (again by adb) when needed?

The encryption keys are bound to the device and can not be extracted. If you use an encrypted SD-card make sure you always backup it's content.

That's unfortunate. Thanks for setting the record straight.


text:
List apps (not) supporting adb backup
Is there a reliable way to identify all the installed apps that do (not) support adb backup?
I am running a LinageOS and seem to be forced to reinstall to upgrade. I would like to check which apps I need to manually back up or where I need to be prepared to lose data.

I found this script, but it does not properly identify Signal as not supporting backups... https://sourceforge.net/projects/no-adb-backup-app-lister/files/

Is your device rooted? If yes may be an app like OAndBackupX or NeoBackup would be helpful, even if such apps can not backup all apps because cryptographic keys in AndroidKeyStore are protected as far as I know.

No, my device is not rooted, but boot loader is unlocked, so it might be possible to root it. Still intrigued how one might identify apps refusing adb backup.

Note that a backup created with root requires restore with rot. So this would also affect the new installation.

Turns out upgrading only requires adb sideload, without erasing any data.

Should you need it again: my little tool Adebar creates device documentation including listing installed apps (examples here). Apps having the ALLOW_BACKUP flag should allow backups, the others obviously not. As around Android 11/12 this got more granular, I'm not sure if the missing flag would mean no backups allowed at all, or how else the "partly backups" are marked (have neither Android 12 here not the time to investigate).


text:
How does one transfer data from an iPhone 6 to a Pixel 6 pro that has already been set up (without a reset)?
So this is not the first time I turn on my Pixel 6 pro. When I connect the devices with a cable (this https://www.amazon.com/gp/product/B071G6NLHJ/ref=ask_ql_qh_dp_hza)  no options appear so it is unclear what to do next to transfer the data and the video I was watching doesn't suggest what to actually do:
https://www.youtube.com/watch?v=i1IPSE2avCE
and I've tried a bunch of things like google one etc but the contacts and the videos from my iphone 6 s are NOT on my pixel.
What do I need to do to get this to work?

this never happens (https://support.google.com/pixelphone/answer/7129740?hl=en#zippy=%2Ccopy-data-from-your-old-phone-with-a-cable-recommended):

When asked to “Copy Apps & Data,” tap Next and then Copy your data.

I also tried google one but I don't see my contacts or videos form my iphone on my pixel. Why?

cross: https://www.quora.com/unanswered/How-does-one-transfer-data-from-an-iPhone-6-to-a-Pixel-6-Pro-that-has-already-been-set-up and https://www.reddit.com/r/Pixel6/comments/vv5xwv/how_does_one_transfer_data_from_an_iphone_6_to_a/ and https://apple.stackexchange.com/questions/443591/how-does-one-transfer-data-from-an-iphone-6-to-a-pixel-6-pro-that-has-already-be

perhaps this will do it? the first option? the second one seems more work? https://www.youtube.com/watch?v=MEdVU96bol8

cross to pixel reddit: https://www.reddit.com/r/Pixel6/comments/vv6roi/how_does_one_transfer_data_from_an_iphone_6_to_a/

honestly the main take away is to do it once during setup of the phone.
Will post it as a community answer since I'm not too happy that I had to download a third party app and that it doesn't seem to be using the cables I bought...I used the Send Anywhere (File Transfer) app. Instructions in video here: https://www.youtube.com/watch?v=MEdVU96bol8 in text:

download Send Anywhere (File Transfer) app
choose the videos, photos, contacts etc from the iphone
choose the pixel to be a receiver
get the code from the iphone put it in the receiver
then click send

done...or at least I hope the transfer happens. Going on right now.


text:
Network connection not working while calling Xiaomi 10T
My boyfriend and I call a lot, and for the last few months we noticed that he isn't able to use his 5G network when we are calling. We call a lot and we don't always have a wifi connection, so it is necessary for us to fix this issue.
His profider is Telford.
The phone in question is the Xiaomi 10T.
He is currently using MIUI 13.
We appreciate any tips and fixes <3

Voice over 5g is as far as I know not yet available in most mobile networks, so if a call comes the phone has to switch to LTE or UMTS or GSM (depends on what is available in your country and your mobile network provider). And for LTE voice only works if VoLTE is active and available by your MNO.

The simplest solution would be using  VoIP, eg whatsapp calls. As mentioned by @Robert , device should fallback to LTE and VoLTE while calls are made. Can you share the output after doing this: (1) Dial *#*#4636#*#* (2) choose phone information (3) then the drop down menu and tell me what's being shown under "IMS Status"

@Robert can u review my comment once?


text:
Pixel 3's mp4 videos don't have thumbnails in Windows 10
My Google Pixel 3 phone saves videos as mp4 files that have no thumbnails in Windows Explorer.

(This screenshot shows files on my PC that I'd moved via USB from the Pixel 3.)
Apparently many other Pixel 3 owners report this same annoying situation; the problem isn't specific to my device.
How can I make my Pixel 3 generate thumbnails properly?

What app have you used to create the videos? May be the files are simply defect or not in the expected MP4 format or using a codec that Windows does not understand. Try a tool like mediainfo of ffprobe to detect the actual file format and the used codecs.

I just got the answer here: https://superuser.com/questions/1730808/how-to-fix-regenerate-thumbnails-for-mp4-files-in-windows-10-recorded-by-pixe?noredirect=1#comment2676847_1730808

Please do not cross post the same question on multiple Stackexchange sites.

That videos don't show a thumbnail in Windows Explorer is because you look at the files via USB and Media Transfer Protocol (MTP).
If you would copy the video to a local hard disk Windows Explorer is capable of showing a thumbnail. But if the file is on a connected device that is accessed via MTP, thumbnails are disabled because of the disability of the MTP protocol:
The main difference between a local file and a file on an MTP device is that on a MTP device you can only read the complete file, not the first may be 100KB like it is possible on any local disk: MTP is a file oriented protocol instead of block oriented protocol as it is common for other file-systems.
That means if Windows Explorer wants to create thumbnails on it's own it has to completely download the whole file - and that for every file!
So why does thumbnail exists for pictures?
The MTP protocol bases on Picture Transfer Protocol (PTP) which defines a command to receive pictures in a scaled quality. That makes it possible to request an image in a very low resolution which can be used as thumb nail. As the protocol is designed to transfer pictures it seems like Android does only implements scaled image retrieval for image files like JPEG.

I appreciate your answer, but I think it must be mistaken. (I've already moved these files from the Pixel 3 to my PC via USB.) I will update my answer to specify. Thanks.


text:
Where is "su" addon package for rooting LineageOS 17 and newer?
On the current LineageOS Extras Download, you can see su packages for versions up to LineageOS version 16. Where are the newer packages?

This functionality was discontinued. The de facto method of achieving root in newer LineageOS releases is Magisk.


text:
Can I read data and IMEI of a phone that can't be powered up?
I have an old Android phone Kyocera Hydro Icon C6730, which is stuck in powering up, while being connected to the power strip. Its battery is also old and I'm not sure if it is still working correctly. I have removed the SD card from the phone, and am thinking about parting away with the phone.

Can a computer read the data stored in the phone  without it being powered-on or started? If yes, is it done by connecting the phone to the computer, via a USB cable, treating the phone as a USB storage device?

Is it still possible to read off the IMEI of the phone? (I saw an 18-digit DEC number and a 14-digit HEX number, both with bar codes, in the back inside the phone, under the battery. It looks like this photo below. Is the HEX number listed there IMEI?)

Thanks.

Usually one of those numbers is the IMEI, the other the serial number. As for reading the data: no, to my knowledge without being powered up the device won't be usable via USB. You'd need special hardware to that using JTAG AFAIK.

@Izzy Thanks. Are you sure one of them is IMEI not MEID? How do you know if a number if IMEI or MEID?

Isn't the MEID just the same as an IMEI but for CDMA phones? Note that the IMEI has a manufacturer specific prefix called Type Allocation Code (TAC). Some manufacturer have multiple TAC numbers, not sure about Kyocera. e.g. Kyocera has used TAC 01509900 on recent phones.

One of the numbers on that label inside your phone should be the IMEI number.
IMEI numbers are typically represented using decimal, and when represented in decimal, are 13 or 15 digits long, plus 1 Luhn checksum digit, for a total of 14 or 16 digits, respectively.  Of course, like all integers, they can be represented in any base, including hexadecimal.
As for the actual data on the phone, I know of no easy way to get the data off the non-volatile memory chip(s) without providing power to the device and having it, at the least, enter recovery mode.
BTW, if anyone is interesting in reading about Mr. Luhn and his scientific research, Wikipedia is a good place to start.

Thanks. How can I tell if a number is IMEI or some other number like MEID?

@Tim You can try entering the value into an IMEI checker... let me find one or two for you...

@Tim Here are 2 I found: https://swappa.com/imei  and  https://ting.com/byod#

Thanks. (1) Can the two links tell the difference between IMEI and MEID or some other kind of numbers? (2) Are IMEI and MEID both IDs of a phone device? Why having two kinds of IDs? Which one is more similar to MAC address of a network interface in a computer?

@Tim You're welcome.  For your first question, they should be able to, yes.  For your next 2 questions, I used to know the detailed answers to those specific questions, but have long forgotten.  I think Wikipedia will have reasonably accurate answers if you search for both acronyms.


text:
Live Transcribe & Notification offline languages
I can not find it anywhere. Is list of languages supported for download and offline transcribe published somewhere?
When I check languages on my current old phone, none of them are shown as available for download.
It would be very helpful to use transcribe without an internet connection, but I don't want to risk buying a new smartphone with 6 GB RAM to find out I can't download my language.
Thank you very much :)

On Google Pixel 3a, the languages that are available for download and offline use are:

English (Australia)
English (United Kingdom)
English (United States)
French (France)
German (Germany)
Italian (Italy)
Japanese (Japan)
Spanish (Spain)

This is consistent with the Play Store's listing as of an update on May 11, 2022.

What's new
• Transcribe offline in English, Japanese, German, Italian, Spanish and French. More to come.

However, as the question has mentioned, offline use is only available on certain devices:

Use Live Transcribe offline
Download languages for offline use
Important: You can download languages for offline use on Android devices with at least 6GB RAM and on all Pixel devices. Not all languages are available for offline use.

On Nexus 5 with only 2 GB RAM, languages are not available for download.


text:
How can I prevent my Pixel running Android 12 from automatically updating the OS?
Android is telling me it'll soon update my OS:

How can I prevent that?
I use a Pixel 6 running Android 12.
I've disabled the automated updates in the developer options:

On Pixel 4a, this works for me. In developer options disable "automatic system updates". You will still get notified (first screen shot), click the back button or go to home screen to "dismiss" that notification

@beeshyams Got it, thanks!


text:
How to revive an old 4.2.2 phone?
Because of "reasons" (or at this point mostly out of curiosity) I find myself with an old Wiko Iggy phone running Android 4.2.2 that after being factory reset is unable to install anything at all from the play store. Searching for specific apps in the store returns only books or movies, searching for apps in a browser and opening the relative page on the store shows the app all right, but tapping "install" only goes so far as showing the permissions overview; agreeing and trying to install produces a "no connection" error (of course the phone is connected to a WiFi network and logged in into a google account).
Is there anything I can do? My suspicion is that I should somehow recover an old APK for play services and install that, but I'm not sure how to do that.

I assume the "no connection" is caused by the problem that Android 4.2 has not TLS1.2 enabled by default for HTTPS connections. A large number of server now require that version or newer. Newer versions of Google Play Services and Play store may have implemented a workaround for this so installing them could be a solution. But you need to manually download both APKs for third party sites like apkmirror APKPure and so on.

Robert is correct, this is what I have to do on my old tablet because Google Play Store doesn't want to work for me... it's why I am trying to find a way to update my Android version with the low RAM flag


text:
Advice for selecting proper ROM for my old device
I have quite old device PocketBook SURFpad 3 (10,1")(specs). And I want to update it, to more modern android version. Unfortunately, I have not done it before, so I would like to ask about an advice. The first step is selecting ROM with right architecture(ARMv7/6...). What are the criterias for selecting of ROM? Should i pay attention only on ARMv7 or specific processor MT8382.
I would be very appreciate for any advices.

there is no ROM for your device


text:
Is there a way to lock the Google Translate app to a specific Japanese character set (camera translate)?
I'm using my phone to translate menus etc in a Japanese videogame (PS4/5), and it tells me like 12 different things it could be. It's ridiculous. Isn't there a specific Japanese character set games use? Can I lock the app to that???

Unlike Chinese which has traditional and simplified character sets, there is only 1 Japanese character set.
However, looks like the translation quality is more unreliable in "Instant" mode. Some possible causes:

The quality/size of the image, which may affect the optical character recognition (OCR, or simply image-to-text). Blurry/small text will be harder to interpret, and any background near the text may also obstruct the clarity.
The Japanese word itself, since without more context, some words can have many interpretations, or...
The algorithm sacrifices quality for speed. In "Instant" mode, the app tries to translate as quickly as possible and will continuously retranslate the image, even for a static image.

For more reliable translation, it is better to use the "Scan" mode instead of the "Instant" mode since it also provides the original text so that the user can cross-check with other dictionaries/translation tools.

Scan sucks. Instant mode is still working better in spite of being annoying. I sit 2ft from a 55" 4K screen and put my elbow on my desk to stabilize the phone. Plus these phones have like 12000 megapixel lenses now. This should work better. Was just hoping to improve it before the new game releases on Wednesday.

@MentallyIrregular then perhaps Google Translate is not the most suitable app for your case, though I don't know any alternatives. You might want to ask for a better live translation app on [softwarerecs.se] then.


text:
Smartwatch: forcing a factory reset without USB debugging?
I recently made a mistake on my watch "h1-c-aladeng"(watch model) or "Lanix Ilium LT510"(the model in "Find My Device"). I now can look at the smartwatch and can't do anything like "here".
Right now I want to know if I'm still able to save my smartwatch by factory resetting it. by the way, It has only 1 physical button that works like a home/power button. When pressed multiple times it pops a "reset setting" window on the screen but can't press the confirm button.
It doesn't have USB debugging turned on, so I can't use ADB to reset. I search on the web for some tools but can't help either. so is there a way I can factory reset my smartwatch without USB debugging?

Does this answer your question? How can I disable "Simulate Secondary Display" when the simulated secondary display prevents me from reaching the button?


text:
Is there any way to stream video from camera when the phone is locked?
I'm using video call on an android phone in order to keep an eye on my grandmother 24/7. The thing is that the light from the screen is troubling her to sleep, but when she locks the phone, the camera turns off. Is there anything I could do? Until recently, you could use discord with locked screen and the camera was working perfectly, but that changed last week, and now even video call on discord turns off when the screen is locked.
Thanks!


text:
Shutdown android device after disconnect charger
I need shutdown android system after disconnect charger.
I have android 6.0.1 (rooted), and I'm looking for to power off phone, when it's not charging. I'm looking for programming solution. I have power on phone when I start charging phone. To do it I changed init.rc file. Now I looking for which file I can change, to achive power off phone after disconneted charger.
I have this code in init.rc:
on charger
    setprop ro.bootmode "normal"
    setprop sys.powerctl "reboot"

To test, I added this to function "on charge"r too:
sleep 300
/system/bin/busybox poweroff -f

and finally I have:
on charger
    setprop ro.bootmode "normal"
    setprop sys.powerctl "reboot"
    sleep 300
    /system/bin/busybox poweroff -f

but it didn't work.
I tested:
/system/bin/setprop sys.powerctl shutdown

/system/bin/svc power shutdown

/system/bin/busybox poweroff -f

Phone never shutdown after connect charger (this was only test, I need shutdown after disconnect charger, not after connect, but why this commands didn't work?).

Does this answer your question? How to power off when charger is removed?

Hej IrfanLatif, yes, I try this script copy-paste to my init.rc file, and it didn't work.

It won't work as it is in init.rc file because it's a shell script, not an init script.


text:
S22 Wifi Hotspot/USB Tether/Ethernet Tether not working
I have a Samsung S22 and i was trying to share the internet connection to my PC but i tried wifi hotspot/usb/ethernet tether but none of them is working,on the PC it says Connected and Internet Access but website wouldnt load and had a "The Site Can't be reached" error. I tried  connecting to my laptop and ipad too, same problem.I vaguely remember i tried to do the same thing previously and it didnt work too so i use my backup phone using the same sim card and i think it worked?


text:
Do 'memory boost' do really do something or is it a figment of imagination or something?
I have no clue whether they work or not. Most apps. give or have something called 'memory boost' but there is no indication to know whether that really solves the issue or not. The issue is at times, especially in games, sometimes the app. hangs. Now by itself, it could mean many things, including memory leakage. Now while I can't figure out if it's memory leakage or whatnot on the mobile, the next best thing seems to be the above. But even after using any of the apps, the above continues to happen i.e. temporary hanging of apps. The mobile is new and everything. And this is on Android 12 on a Samsung Galaxy phone

Sorry but I don't understand a word of what you have written. What is your question?

No. Memory booster apps can't do anything real. Memory management is a low level thing. Apps don't have access to such core features of operating system.

@Robert  irfan got it but you didn't. Basically, there are tonnes of apps. that claim to optimize the memory, just type 'memory booster' in Google Play Store and you will know what I mean. Apparently, they are all faking.

Whenever some cleanup app claims to have a memory booster, I'd skip that app entirely. All they do is "clean up memory" by killing processes to "free up memory" – which in most cases is rather counter-productive (as either those processes immediately restart, or the corresponding app just would need longer to startup affterwards and also use more resources like battery in the process). Task killers were a thing with early Android versions (before 4.x), and might be useful today in special cases where an app runs havoc – but else the OS manages memory pretty well nowadays.


text:
My android phone won't accept correct PIN/password after I tried to change my screen lock password
I have a Realme 8 phone as my primary device.
It had a PIN and my fingerprint set up as the screen lock. Around a week ago at around 4 am, I decided to change my PIN as I keep changing screen locks after some 5-6 months. So this time I decided to use PASSWORD (which contains alphanumeric strings and not just numbers like PIN) which I use on my laptop as well.
So I navigated to settings to change it, I entered my current 5-digit-PIN as asked, then I enter my new password (alphanumeric) and then at the final step when I had to tap on "Done", I think I accidentally pressed back button.
Now after that, when I turned my screen off, I was expecting new Password screen but it was not there (yes I get it, I didn't tap on DONE so it makes sense). As expected, it was again PIN screen which makes sense.
What does NOT make sense is that when I entered my old 5-digit-PIN, it said incorrect password try again. I've tried my PIN like a 1000 times, it just don't work.
But I could still use a fingerprint right? Yes I was able to unlock my phone through fingerprint.
As I researched more about this issue, I found an easy fix to this common problem, which was to restart the device (worst mistake). It worked for everybody except me.
I restarted my device.
Bang. Now I cannot even use my fingerprint (as when an Android device restarts, it doesn't let us unlock the device with fingerprint, a well known fact). So I'm locked out.
Is there a way to unlock the device with the fingerprint after rebooting?
I cannot factory reset it as it has Gigabytes of my data that I have unfortunately not backed up anywhere else.
Please note that the screen calibration is not damaged, I can see what numbers I am typing in the PIN field. It just does not work.
Also there is no option of Forget password as well as Google forget password.
I can try PINs as many times I want. There is no timer after, say 5, incorrect attempts. I have tried 100 PINS at a time consecutively.
I can boot into Realme's stock recovery, it has an option of "Update phone (without losing data)" when I click it, it asks for a "Password" this time (not specifically PIN), on an alphanumeric QWERTY keyboard. But neither the PIN works, nor the password that I had entered at around 4 am.
USB debugging is turned off, hence I cannot try ADB. I can access the notification action center and can connect with WiFi as well.
Any idea what should be done now? It has my really really important data I cannot afford to lose.
It also didn't had an SD card hence I'm worried if formatting it and then data recovery will work or not.
Any help is appreciated. If someone wants to know the PIN or password for some reason, let me know. Thank you everyone

uh.. sorry but ydo you still want an answer?

@44yu5h if you know it then for sure yes. Although I have formatted the phone and all data is now gone, but your answer could help others.


text:
Phone doesn't recognize usb
Mine phone (Honor 10) doensn't recognize an usb connection, execept for charging.
The initial problem was connecting my phone to a 3D-printer.
Because this didn't work, I tried to connect a usb-flash disk to the phone with an OTG adapter. The usb-flash disk has a led. It flicks 2 times and that is it. Doesn't recognize the disk.
Things i tried:
My phone should be OTG capable -- I downloaded 2 OTG checker apps
The disk/3D-printer/OTG adapter are working correctly as i checked with my new phone (wich i don't want to use)
I turned on USB debugging in the development settings
Anyone who can help me?
Thanks in advance


text:
Factory reset install blocked by Google FRP
I have a Tecno Phantom 8. It has Android 7.
I'm trying to reinstall it using the "Recovery Mode" via "Factory Data Reset".
Google has something called FRP.
I do not have the google account that was registered in the phone. I tried to use my own google account. But FRP blocks the reinstallation of the phone without the original email.
That's good but kinda dumb since I cannot even reinstall my own phone. And now I'm stuck in the setup screen.
Any idea how I can do it ? Should I buy any tool that can help ?

FRP is a protection that was added for preventing that a phone thief (who doesn't know the phone PIN or Google password) can erase the phone data and then sell it as used phone.

@Robert lol I'm screewed. The phone is locked. I was trying to root it and now this bugs me so much.

There is a simple rule to avoid FRP: Always perform factory reset from with the main Android OS in settings or delete Google account from account list. The FRP will not trigger. There are also tools that claim to bypass FRP, not sure how reliable they are.

@Robert well I did not follow that rule and now I'm stuck.


text:
How to recover data from a Huawei P30 Lite with a black screen?
I'd like to recover messages, photos and videos if possible. I know the PIN code to the device and I believe both the fingerprint scanner and face recognition are working just fine.
Device: Huawei P30 Lite (original edition, not the new edition)
USB debugging is not enabled on the device. Although the screen is black, I believe the device is otherwise fully functional.
I've tried:

HiSuite (failed as required USB debugging)
adb devices via Android Platform Tools (failed as I presume it requires USB debugging)

The device appears like this when connected to my PC via USB:

Your main problem is that usually Android phones are not usable before you have logged in the first time after boot. Not sure how Huawai devices handle this, but an Google Android devices after a reboot you have to login using password/pin (no face or fingerprint unlock). If this is also required on your device you could try to connect a simple USB keyboard and type the pin without screen.

Okay, thanks @Robert . I'll give that a go when I next can.

HiSuite is backup tool for PC


text:
How to configure a radius server for WLAN (PEAP) in Android12?
After having upgraded my mobile phone from Android 8 to Android 12 I realized that the WLAN settings are different.
Specifically I find no way to configure a radius server for the domain when using 802.1x EAP (PEAP).
Why can't I enter a radius server for the domain any more?

There never was a "RADIUS server" field in Android, and there could not have been, as the client device does not speak RADIUS in the first place and cannot influence the server that will be used – it's the access points that relay the EAP messages from clients over RADIUS (or over a different protocol, or even implements EAP internally, as hostapd might do).
What Android did have was the "Domain" field which is used for verifying the PEAP server certificate's CN/SAN, and this field still exists in Android 12 – although it only appears after you select something from the "CA certificates" dropdown (e.g. "Use system certificates" if your network uses public web CAs for PEAP):

The "Domain" field is used like wpa_supplicant's domain_suffix_match= and accepts a suffix for the certificate's CN/SAN, e.g. a SAN of "radius1.example.com" would be matched either by the exact radius1.example.com or by the suffix example.com.

When I try; I see these fields (cannot make a screenshot for security reasons, BTW): "EAP Method" (PEAP), "Phase 2-Authentication" (MSCHAPV2), "CA Certificate" (Some CA, System Certificates not being offered), "Identity" (blank yet), "Anonymous Identity" (blak yet), and finally "Password" (blank yet). Nothing more. On the old phone I had "Domain" before "Identity".

If "System Certificates" isn't in the list at all (regardless of whether it would be suitable or not), I'm tempted to guess that the option was hidden by some kind of custom security policy, and that the domain field was hidden by the same security policy as well. (Hopefully the policy sets it to the correct value.)

As it's my own new device, I wonder where such settings could be hidden. I realized that in new Android the WLAN certificates are different from system certificates.


text:
How to select ASCII characters, using a Samsung keyboard?
On my computer, I regularly type French, German and other characters, using their ASCII code, such as:

± : ASCII code 177
Ç : ASCII code 199
œ : ASCII code 156
ß : ASCII code 223

On a computer, this is fairly simple, using the following keyboard shortcuts:Alt+0177, Alt+0199, Alt+0156 and Alt+0223.
How can I type those characters on a Samsung Galaxy smartphone, using the standard Samsung keyboard?

No idea about the Samsung keyboard but you can customize AnySoftKeyboard according to your needs. I did the same to add multiple Unicode characters which I use quite often.

On Samsung, you need to hold down the character associated with it. For example, if you want to input Ç on the keyboard, hold down the regular c, and a display of special variants of c will be shown. Guide your finger to the special character while holding the screen and let go when it highlights the character or when your finger is touching it.
Boom, you have your character. As for characters like ß which are on their own and aren't special variants like Ç, use the letter that sounds like it. ß is pronounced like "sh" or "ss", so hold s and select ß.

I've managed typing the "Ç", the "ß" and the "œ" by holding the keys 'C', 's' and 'o' down, but do you know how to type '±'?

@Dominique You do the same with the + symbol. As I said, variants of a letter or the phonetic sound of a letter usually match the corresponding location of the symbol. C leads to Ç, and so forth. In this case, it's the + symbol. This is on my samsung, so it's not the same version but the keyboards do seem to be synchronized across versions.

When keeping the "+" pressed, no extra characters are shown. I have Samsung keyboard version 3.5.45.2, it mentions that the latest version is already installed.


text:
Searching for and copying Android app text elements running it on a PC
Problem: some Android apps present large portions of text and/or large forms, which, unlike web pages, are not friendly to searching or copy-pasting. Consider a generated value (like ticket reservation id, but longer) that you can't search for (to verify) or select (to copy).
Can we somehow run this unfriendly app on a PC and have a browser-like (maybe even devtools-like) interaction with its whole layout, doing anything we want with the displayed text values? What simulator or VM could help?

Have you tried the commands mentioned here? https://stackoverflow.com/questions/26586685/is-there-a-way-to-get-current-activitys-layout-and-views-via-adb

For copy-pasting, a possible alternative is to take a screenshot and share it to a text recognition app (e.g. Google Lens).


text:
Gabb Plus sim card locked
My Gabb phone's sim card got locked. It's my only phone, so I can't call or text any number. I don't know my PUK code, which it requires to unlock. How would I unlock it?
Thanks in advance.

Contact you mobile network provider, that is the only way.

@Robert thanks! I got my PUK and it is all fixed.

Contact your service provider and it should work.
Or, you can look at the sim card box (if you got one) and it will say.


text:
How to disable (or configure) being prompted for password/PIN for "additional security"?
Android devices seem to generally require you to enter your PIN/password after successfully authenticating with your fingerprint.
The reasons for why this is happening and what triggers it are already layed out in Conditions for triggering "pin required for additional security“.
Now, with my old phone, this was annoying, with my new one this seems to happen with every second unlock. Hence, it needs to go. Really. Anyone here who knows how to

deactivate the feature altogether or
configure specific conditions for when it happens?


text:
Sony TV XBR-49X705D (Android TV) connect bluetooth headphones
I want to connect Bluetooth headphones to a TV Sony XBR-49X705D.
The TV has Bluetooth, and I was able to join a keyboard, but when I tried to connect the headphones, it didn't work. Is there a way to make this work? Can I buy a USB adapter to improve this Android TV's Bluetooth capabilities?


text:
Prevent app from using in-app purchases?
I installed an app and it has a subscription for the pro version in-app.

It automatically selects the account and shows the added cards in the subscription popup window

I cannot change the payment account, I guess it grabs the account from Google Pay installed on my phone which I use for everyday payments.
I don't like it, I don't like when some arbitrary app that I don't trust has access to my payment profile by default, and I like to disable such possibility for the app. Is there a way?
I don't understand where this possibility comes from, I didn't grant any payment permissions for the app.

Is this permission inherent for any app and I can't disable it?
Answering future questions: I tried to install this app from another account like suggested here, I tried to reinstall, and I even installed this app from APK in the end. No result. It still points to the same payment account, I guess it was saved from the first time in the very beginning when I installed the app from it.

AFAIK there's no permission to prevent apps from doing IAPs. com.android.vending.BILLING's protection level is "Normal", so cannot be revoked. There exist some hacks but they won't work without root.

protection level is "Normal", so cannot be revoked it's odd because payment cards information is sensitive one, and accessing it by any app, even installed from APK, is not safe

Related, but unanswered: https://android.stackexchange.com/q/106251/96277

@Suncatcher when you make purchases (in-app or initial) from Play Store, it's the Play Store app (and possibly Play Services) which have access to your Google account details including the payment methods, not the other apps. What you see is a part of the Play Store app, not the one you are (not) going to purchase.

Are you aware that the second screen shot shows GooglePlay and not the app? Apps don't have access to your payment data. They can only tell GooglePlay to show the matching purchase dialog. Even if you make an in-app purchase the data the app gets seems to be very limited. See also my question and the comments about in-app purchase and privacy: https://android.stackexchange.com/questions/246557/privacy-of-in-app-purchases-how-much-user-data-does-the-app-developer-get

ok then, I got your point guys, the app doesn't have access to Payments API and don't see this data. This, however, doesn't answer my main question: how to prevent app even trigger this Play Store dialog? I treat these "purchase me" popups as ads and I want to do with them the same that I do with ads - to adblock.

@Suncatcher root your device and try to use Intent firewall. Nothing less than that.

Honestly at this point just stop using the app and search for an alternative. Why do you want to keep using one which shoves a subscription down your throat?

it was a purely scientific research question for learning the ecosystem ;)

For an in-app purchase the app that has the in-app purchases cooperates with Google Play Store app. In that process the app does not get access to the payment info, that is all handled by Google Play Store app.
According to what I know this is what happens when a user performs an in-app purchase:
Preparation: When publishing the app the app developer registers all possible in-app purchases at Google so Google knows exactly for what app what in-app purchases are possible.
On user side the following steps are preformed:

The app shows a button to perform an in-app purchase.
If the user clicks on that button some Google provided code inside the app is triggered that contacts GooglePlay Store app. In that communication Play Store verifies that the app is genuine (app signature is checked). Then the information about the selected in-app purchase package is sent to Play Store app. Also an "obfuscated user name" (the unique identifier of your user account within that app) is sent so that app can later identify for which account a successful subscription has been bought.
Google Play Store app takes over and shows the purchase dialog like your second screen shot.
If the user confirms the subscription in Google Play Store purchase dialog, payment will be performed an Google backend issues a purchase token that is send to the Play Store and for that forwarded to the app you made the purchase for. In that token the previously mentioned obfuscated user name is included and the data what in-app purchase was purchased.

This doesn't answer my main question: how to prevent app even trigger this Play Store dialog?

@Suncatcher Based on your question I assumed that the actual question is about the account data being accessed by the app. On unrooted devices you can't prevent an app from opening in-app purchase dialog. You can only prevent the actual purchase by setting Play Store to always ask for the account password when doing a purchase (see Play Store settings -> Authentication). The only other way I know would be to modify (-> resign) the app. Then in-app purchase would directly fail and no dialog opens. But that also means the app is disconnected from Play Store updates.


text:
How do I transfer my messenger account to a new phone?
I am using messenger without facebook. How do I transfer my account to a new phone? The app on a new phone immediately asks me for a facebook account.

If you are talking about Facebook Messenger you should write that in your question.

Edit: I read your Messenger question as if it were about your text Messages. I don't know if Messenger texts are the same as text Messages. The below works on text Messages. (I don't have experience with Messenger.)
I used SMS Backup And Restore, the free version. It allows you to save the current instance of your Messages in a file on the old phone. Then email that file to yourself (or at least save it in some fashion). Then install SMS Backup And Restore on the new phone and restore the saved file from the older phone on the new phone.


text:
Why was my launcher setup reset after inserting a SIM card?
I have a new phone, and I started to "customize" it while still using my old one.
When I felt the phone is ready for switch-over, I inserted the SIM card from the old phone.
That worked, but after opening the MMS sent by the provider, it caused some app to be installed without my explicit consent.
A moment later I realized that my launcher configuration was reset to default:
All my icons and folders that I had placed and created before were gone!

Is that usual for Android 12 (Oppo's "Color OS" 12.1), or is it unusual?
Is there any chance to get my setup of the launcher back?

I was thinking whether removing the SIM card again would restore my launcher, but then I though:
Better ask here!

That a manufacturer installs additional bloatware apps based on the customer country is nothing new. I wasn't aware that for the country detection the SIM may be used. Unfortunately I don't see any chance that removing the SIM card will revert the changes. Android does not provide a way to save app data in a way that would later allow to go back to that state. All changes are permanent.

So installation of the provider's app did the layout reset? I had uninstalled that apps in the meantime as I don't need them. Also my phone knew the region I live in before inserting the SIM card.

As I found out, the provider's "Welcome" app installed itself as "launcher" without Android asking me for permissions to do so (how did they manage that?).
Also it did not just reset the start screen, but also changed some display options regarding that status bar.