text:
How do I edit/view android system.img files located SDK emulator images
I want to edit a few files inside android-30\google_apis_playstore system.img which resides in sdk/system-images. I'm using WSL ubuntu 18.04, I do fdisk -lL system.img to mount with the right offset
which returns
Disk system.img: 2.7 GiB, 2832203776 bytes, 5531648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 419B5BC3-59EE-4BEA-AA53-FF67E1D7406E

Device      Start     End Sectors  Size Type
system.img1  2048    4095    2048    1M Linux filesystem
system.img2  4096 5529599 5525504  2.7G Linux filesystem

and by doing sudo mount -t auto -o ro,loop,offset=2097152 ./system.img /mnt/loop
it fails like this
mount: /mnt/loop: wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.

I have also tried to use simg2img which is said that it will convert the image to a raw image in which I can mount it which yields invalid sparse file
simg2img system.img raw.img
Invalid sparse file format at header magic
Failed to read sparse file

Do you have any idea of how to open or mount the system.img file and edit a few files?

guess off-topic but try dd skip=offset count=size | simg2img or kpartx. there is also --writeable-system flag for modifications on runtime


text:
What is the package name for the default Samsung Gallery App?
Deleted it while debloating my Samsung Galaxy S21 Ultra. I am unable to install it via the Samsung store. Thank you in advance!

The default package name of the Samsung Gallery app (at least on my Samsung device here) is
com.sec.android.gallery3d

https://play.google.com/store/apps/details?id=com.sec.android.gallery3d

Same on my Samsung Galaxy A7

source: Stack Exchange

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

sort: votes


text:
Google can't record now as Duo is recording
Hi All
Whenever I am making call in Duo some Error message is coming in screen like Google can't record now as Duo is recording.and while Playing pubg and stream in Omlet arcade same Error is coming like Omlet arcade can't record now as Pubg is recording. Can any one solve this issue please

What is your device and Android version (there is a difference between pre Android 10 those running Android 10+)?

IQOO3. Android Version -11

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


text:
Apps started to crash left and right - is it the recent WebView issue?
I'm using Xioami MI 9 SE. Over the past day or two, I've started experiencing mysterious crashes on startup with several applications, including a Radio receiver app (local to Israel); Opera occasionally, APKPure; and one or two others.
Now, I noticed other people experiences something similar on their Samsung phones, and also a few new items about a multi-app-crash issue:
Are your Android apps crashing? You’re not alone.
so I thought my situation may be related. However, the workaround suggested at the link doesn't work for me, since MIUI doesn't even show an "Android System Webview" app.
So, could it be the same issue? ANd - how do I restore my system to working order?
Note: Downloading and installating the latest APKPure version does not seem to resolve the crash.

Install all available app updates, especially Chrome.

@Robert: That's a bit of a problem, since I was using APKPure to check what those are.

You should:

Locate the latest version of the Android System Webview app using any web browser, and using a search engine
Download & install the APK. You will find it is actually an update, and a version Android System Webview is installed on your phone already; it's just hidden from you somehow.

This worked for me; the apps mentioned above stopped crashing.


text:
Nexus 5 not appearing in fastboot devices menu
I'm attempting to flash Android 4.4.4 KitKat onto my old Nexus 5, but when I run the fastboot devices command, it does not show my device's serial number. When I try doing the ADB sideload command though, it works. The "flash-all.bat" file doesn't work either as it says <waiting for device>. I am currently using platform-tools version 31.0.0.

Fastboot only works when you boot into bootloader mode. If adb sideload works you are most likely in recovey and not bootloader mode.

@Robert I am in bootloader mode. It still doesn't appear. The bootloader is also unlocked too.

Check device manager if the fastboot drivers are correctly installed.

Fixed it. Thought I already had the Google USB Drivers already installed but guess not.

drivers have to be installed separately for each boot mode


text:
AOSP 7.1.2 - Firefox (Fennec and IceCat) result with just a white screen
I have installed a Custom ROM (AOSP 7.1.2) on a Samsung tablet. It is rooted, and also has gapps (pico).
Most everything works - except, when I installed both versions of Firefox for mobile - Fennec and IceCat (both via F-Droid), and the installation was successful (though neither of them asked for any permissions).
However, when I start either of them, they simply start as a white screen, and ... nothing happens (Fennec occasionally crashes after a few seconds of white screen, I have not seen IceCat crash so far, it just keeps at the white screen).
I captured a bit of logcat - first fennec is started, then icecat - it has been pasted here:
https://pastebin.com/ijGSr8X0
Would anyone have any idea as to why specifically these two Firefox apps start with nothing else but a white screen; and how to fix that?
(BTW, I use the same IceCat on an Android 4.x device; it works fine there.)

Posting the whole logcat is not useful at least truncate it and only post the log from the point on where you start one of the apps.

I'm voting to close this question because the concerned custom ROM in all likelihood is the cause of the problem. Firefox is actively supported for Android 5 and above. There is no reason it would suddenly go nuts for Android 7 alone. @sdaau, it is best if you ask the ROM maintainer to take a look at this and fix it. Probably a bug.

Sorry about the log being too verbose, I wasn't really sure what would have been most relevant. In any case, I did a bit of research, and the last Firefox Focus version that works on this device/OS for me is 8.0.19, anything above that has the blank screen problem. For F-droid Fennec, I tried going all the way down to 68.6.0 which did not work, and I stopped there.

Btw, one more this: the Firefox Focus 8.0.19 runs fine the first time, when it runs for the setup wizard, after that browsing works fine. But if you close it down and restart it, then it fails again (either crash, or blank screen). Workaround for this is: Settings / Apps / Firefox Focus / Storage / Clear Data & Clear Cache / (back) Force Stop ; then when starting it again, it will run the wizard again, and it will work.


text:
Bootloop MIUI 12 after reboot (Xiaomi POCO X3 NFC)
I got bootloop after MIUI 12 phone restart (Xiaomi POCO X3 NFC).
Using Magisk 21, TWRP v3.4.
I was able to get out the kernel logs, but can not identify where is the problem, what causes the bootloop.
Anybody can identify what causes the bootloop?
Here is the dmesg.log file content.
The full log is in pastebin:
https://pastebin.com/GcAJyz93
dmesg.log content (partial):
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.117-perf-g0abcc55 (builder@c4-miui-ota-bd081.bj) (clang version 8.0.12 for Android NDK) #1 SMP PREEMPT Wed Sep 16 17:33:15 CST 2020
[    0.000000] Boot CPU: AArch64 Processor [51df805e]
[    0.000000] Powerup reason=0x80081
[    0.000000] Machine: Qualcomm Technologies, Inc. SDMMAGPIE PM6150 IDP
[    0.000000] OF: reserved mem: OVERLAP DETECTED!
[    0.000000] disp_rdump_region@9c000000 (0x000000009c000000--0x000000009d800000) overlaps with cont_splash_region@9c000000 (0x000000009c000000--0x000000009d800000)
[    0.000000] OF: reserved mem: OVERLAP DETECTED!
[    0.000000] cont_splash_region@9c000000 (0x000000009c000000--0x000000009d800000) overlaps with dfps_data_region@9e300000 (0x000000009d700000--0x000000009d800000)
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000ff800000, size 4 MiB
[    0.000000] OF: reserved mem: initialized node cdsp_region, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x00000001fa800000, size 36 MiB
[    0.000000] OF: reserved mem: initialized node mem_dump_region, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000fd800000, size 32 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000fcc00000, size 12 MiB
[    0.000000] OF: reserved mem: initialized node adsp_region, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000fc400000, size 8 MiB
[    0.000000] OF: reserved mem: initialized node sp_region, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000fb400000, size 16 MiB
[    0.000000] OF: reserved mem: initialized node qseecom_ta_region, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000f5800000, size 92 MiB
[    0.000000] OF: reserved mem: initialized node secure_display_region, compatible id shared-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000085700000, size 6 MiB
[    0.000000] OF: reserved mem: initialized node hyp_region@85700000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000085e00000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node xbl_aop_mem@85e00000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000085fff000, size 0 MiB
[    0.000000] OF: reserved mem: initialized node sec_apps_region@85fff000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000086000000, size 2 MiB
[    0.000000] OF: reserved mem: initialized node smem@86000000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000086200000, size 45 MiB
[    0.000000] OF: reserved mem: initialized node removed_region@86200000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x000000008ab00000, size 5 MiB
[    0.000000] OF: reserved mem: initialized node camera_region@8ab00000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x000000008b000000, size 132 MiB
[    0.000000] OF: reserved mem: initialized node modem_region@8b000000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000093400000, size 5 MiB
[    0.000000] OF: reserved mem: initialized node pil_video_region@93400000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000093900000, size 30 MiB
[    0.000000] OF: reserved mem: initialized node cdsp_regions@93900000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000095700000, size 30 MiB
[    0.000000] OF: reserved mem: initialized node pil_adsp_region@95700000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000097500000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node wlan_msa_region@97500000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000097680000, size 0 MiB
[    0.000000] OF: reserved mem: initialized node npu_region@97680000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000097700000, size 0 MiB
[    0.000000] OF: reserved mem: initialized node ips_fw_region@97700000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000097710000, size 0 MiB
[    0.000000] OF: reserved mem: initialized node ipa_gsi_region@97710000, compatible id removed-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x0000000097715000, size 0 MiB
[    0.000000] OF: reserved mem: initialized node gpu_region@97715000, compatible id removed-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009e400000, size 20 MiB
[    0.000000] OF: reserved mem: initialized node qseecom_region@9e400000, compatible id shared-dma-pool
[    0.000000] Removed memory: created DMA memory pool at 0x000000009f800000, size 30 MiB
[    0.000000] OF: reserved mem: initialized node cdsp_sec_regions@0x9f800000, compatible id removed-dma-pool
[    0.000000] On node 0 totalpages: 1480425
[    0.000000]   DMA zone: 6956 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 445161 pages, LIFO batch:31
[    0.000000]   Normal zone: 16176 pages used for memmap
[    0.000000]   Normal zone: 1035264 pages, LIFO batch:31
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] random: fast init done
[    0.000000] random: get_random_bytes called from start_kernel+0x94/0x558 with crng_init=1
[    0.000000] percpu: Embedded 23 pages/cpu s53656 r8192 d32360 u94208
[    0.000000] pcpu-alloc: s53656 r8192 d32360 u94208 alloc=23*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1457293
[    0.000000] Kernel command line: rcupdate.rcu_expedited=1 rcu_nocbs=0-7 console=ttyMSM0,115200n8 androidboot.hardware=qcom androidboot.console=ttyMSM0 androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 service_locator.enable=1 androidboot.usbcontroller=a600000.dwc3 swiotlb=2048 loop.max_part=7 cgroup.memory=nokmem,nosocket androidboot.selinux=permissive androidboot.init_fatal_reboot_target=recovery buildvariant=eng androidboot.verifiedbootstate=orange androidboot.keymaster=1  androidboot.bootdevice=1d84000.ufshc androidboot.boot_devices=soc/1d84000.ufshc androidboot.serialno=d2c7e1d2 androidboot.product.hardware.sku=surya androidboot.cpuid=0xf9f4016b androidboot.multisim_config=dsds androidboot.dp=0x0 androidboot.baseband=msm msm_drm.dsi_display0=dsi_nt36672c_tianma_fhd_video_display: androidboot.fpsensor=gdx androidboot.lcmtype=dsi_nt36672c_tianma_fhd_video_display androidboot.dtbo_idx=10 androidboot.dtb_idx=9 androidboot.secur
[    0.000000] I am goodix fingerprint  --syhg
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.000000] software IO TLB: mapped [mem 0xf5400000-0xf5800000] (4MB)
[    0.000000] Memory: 5509764K/5921700K available (17918K kernel code, 2716K rwdata, 7256K rodata, 6144K init, 6808K bss, 207136K reserved, 204800K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  RCU dyntick-idle grace-period acceleration is enabled.
[    0.000000]  All grace periods are expedited (rcu_expedited).
[    0.000000]  Tasks RCU enabled.
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: no VLPI support, no direct LPI support
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000017a60000
[    0.000000]  Offload RCU callbacks from CPUs: 0-7.
[    0.000000] arch_timer: cp15 and mmio timer(s) running at 19.20MHz (virt/virt).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000003] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000016] clocksource: Switched to clocksource arch_sys_counter
[    0.002044] Console: colour dummy device 80x25
[    0.002065] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.002075] pid_max: default: 32768 minimum: 301
[    0.002172] Security Framework initialized
[    0.002181] SELinux:  Initializing.
[    0.002238] SELinux:  Starting in permissive mode
[    0.002280] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.002296] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.014225] ASID allocator initialised with 65536 entries
[    0.016320] Hierarchical SRCU implementation.
[    0.023875] MSM Memory Dump base table set up
[    0.023899] MSM Memory Dump apps data table set up
[    0.026399] smp: Bringing up secondary CPUs ...
[    0.035824] GICv3: CPU1: found redistributor 100 region 0:0x0000000017a80000
[    0.035870] CPU1: Booted secondary processor [51df805e]
[    0.045321] GICv3: CPU2: found redistributor 200 region 0:0x0000000017aa0000
[    0.045355] CPU2: Booted secondary processor [51df805e]
[    0.054822] GICv3: CPU3: found redistributor 300 region 0:0x0000000017ac0000
[    0.054853] CPU3: Booted secondary processor [51df805e]
[    0.064412] GICv3: CPU4: found redistributor 400 region 0:0x0000000017ae0000
[    0.064442] CPU4: Booted secondary processor [51df805e]
[    0.074092] GICv3: CPU5: found redistributor 500 region 0:0x0000000017b00000
[    0.074123] CPU5: Booted secondary processor [51df805e]
[    0.084544] CPU features: Unsupported CPU feature variation detected.
[    0.084578] GICv3: CPU6: found redistributor 600 region 0:0x0000000017b20000
[    0.084630] CPU6: Booted secondary processor [51df804e]
[    0.094922] GICv3: CPU7: found redistributor 700 region 0:0x0000000017b40000
[    0.094977] CPU7: Booted secondary processor [51df804e]
[    0.095224] smp: Brought up 1 node, 8 CPUs
[    0.095253] SMP: Total of 8 processors activated.
[    0.095259] CPU features: detected feature: GIC system register CPU interface
[    0.095262] CPU features: detected feature: Privileged Access Never
[    0.095266] CPU features: detected feature: User Access Override
[    0.095269] CPU features: detected feature: 32-bit EL0 Support
[    0.095274] CPU features: detected: Hardware dirty bit management
[    0.095900] CPU: All CPU(s) started at EL1
[    0.095944] alternatives: patching kernel code
[    0.148958] Registered cp15_barrier emulation handler
[    0.148978] Registered setend emulation handler
[    0.149380] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.149407] futex hash table entries: 2048 (order: 6, 262144 bytes)
[    0.154482] pinctrl core: initialized pinctrl subsystem
[    0.155358] NET: Registered protocol family 16
[    0.157729] schedtune: configured to support 6 boost groups
[    0.158659] cpuidle: using governor menu
[    0.158700] cpuidle: using governor qcom
[    0.158828] NET: Registered protocol family 42
[    0.166431] vdso: 2 pages (1 code @         (ptrval), 1 data @         (ptrval))
[    0.166446] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.167668] DMA: preallocated 256 KiB pool for atomic allocations
[    0.168298] Failed to create IPC log0
[    0.168306] Failed to create IPC log1
[    0.168313] Failed to create IPC log2
[    0.168319] Failed to create IPC log3
[    0.168325] Failed to create IPC log4
[    0.168475] exit: IPA_USB init success!
[    0.168794] ramoops: dump_mem_sz=1048576,cxt->record_size=524288,cxt->size=4194304,cxt->console_size=1048576,cxt->ftrace_size=0,cxt->pmsg_size=2097152
[    0.179668] pstore: using zlib compression
[    0.180614] console [pstore-1] enabled
[    0.180712] pstore: Registered ramoops as persistent store backend
[    0.180727] ramoops: attached 0x400000@0x9d800000, ecc: 0/0
[    0.181939] msm-sn-fuse 786134.snfuse: serial num: f9f4016b buqingshuai
[    0.181956] msm-sn-fuse 786134.snfuse: fuse state: 0x0,0x0,0x0 buqingshuai
[    0.181969] msm-sn-fuse 786134.snfuse: SN interface initializedbuqingshuai
[    0.183946] sps:sps is ready.
[    0.186079] unable to find DT imem DLOAD mode node
[    0.187478] unable to find DT imem EDLOAD mode node
[    0.189987] msm_watchdog 17c10000.qcom,wdt: wdog absent resource not present
[    0.191569] msm_watchdog 17c10000.qcom,wdt: MSM Watchdog Initialized
[    0.192460] platform soc:mem_dump: assigned reserved memory node mem_dump_region
[    0.231609] platform soc:qcom,smem: assigned reserved memory node smem@86000000
[    0.232167] platform soc:qcom,msm-adsprpc-mem: assigned reserved memory node adsp_region
[    0.239512] platform 86d00000.qseecom: assigned reserved memory node qseecom_region@9e400000
[    0.240519] platform 62400000.qcom,lpass: assigned reserved memory node pil_adsp_region@95700000
[    0.241651] spmi spmi-0: PMIC arbiter version v5 (0x50000000)
[    0.241682] platform 8300000.qcom,turing: assigned reserved memory node cdsp_regions@93900000
[    0.241921] platform 4080000.qcom,mss: assigned reserved memory node modem_region@8b000000
[    0.242065] platform aae0000.qcom,venus: assigned reserved memory node pil_video_region@93400000
[    0.242197] platform 9800000.qcom,npu: assigned reserved memory node npu_region@97680000
[    0.243151] (NULL device *): msm_gsi_probe:4526 failed to create IPC log, continue...
[    0.247256] LCDB: qpnp_lcdb_regulator_probe: Failed to parse dt rc=-517
[    0.247894] platform soc:qcom,ipa_fws: assigned reserved memory node ips_fw_region@97700000
[    0.248036] spmi spmi-0: pmic_arb_wait_for_done: transaction failed (0x3)
[    0.265621] sdmmagpie-pinctrl 3400000.pinctrl: invalid resource
[    0.272544] rpmh_regulator_probe: smpf1: could not find RPMh address for resource
[    0.272817] rpmh_regulator_probe: smpf2: could not find RPMh address for resource
[    0.280209] pm6150_l17: supplied by pm6150_l11
[    0.280705] pm6150_l18: Bringing 1uV into 1696000-1696000uV
[    0.287962] rpmh_regulator_probe: ldof1: could not find RPMh address for resource
[    0.288178] rpmh_regulator_probe: ldof2: could not find RPMh address for resource
[    0.288383] rpmh_regulator_probe: ldof4: could not find RPMh address for resource
[    0.288590] rpmh_regulator_probe: ldof5: could not find RPMh address for resource
[    0.288791] rpmh_regulator_probe: ldof6: could not find RPMh address for resource
[    0.288989] rpmh_regulator_probe: ldof7: could not find RPMh address for resource
[    0.298302] OF: amba_device_add() failed (-16) for /soc/cti@6867000
[    0.331183] gpu_cx_gdsc: supplied by pm6150l_s2_level
[    0.333167] clk: add_opp: Set OPP pair (300000000 Hz, 572000 uv) on cpu0
[    0.333515] clk: add_opp: Set OPP pair (1804800000 Hz, 796000 uv) on cpu0
[    0.333581] clk: add_opp: Set OPP pair (300000000 Hz, 572000 uv) on cpu1
[    0.333912] clk: add_opp: Set OPP pair (1804800000 Hz, 796000 uv) on cpu1
[    0.333987] clk: add_opp: Set OPP pair (300000000 Hz, 572000 uv) on cpu2
[    0.334314] clk: add_opp: Set OPP pair (1804800000 Hz, 796000 uv) on cpu2
[    0.334391] clk: add_opp: Set OPP pair (300000000 Hz, 572000 uv) on cpu3
[    0.334715] clk: add_opp: Set OPP pair (1804800000 Hz, 796000 uv) on cpu3
[    0.334774] clk: add_opp: Set OPP pair (300000000 Hz, 572000 uv) on cpu4
[    0.335116] clk: add_opp: Set OPP pair (1804800000 Hz, 796000 uv) on cpu4
[    0.335179] clk: add_opp: Set OPP pair (300000000 Hz, 572000 uv) on cpu5
[    0.335520] clk: add_opp: Set OPP pair (1804800000 Hz, 796000 uv) on cpu5
[    0.335599] clk: add_opp: Set OPP pair (300000000 Hz, 572000 uv) on cpu6
[    0.336079] clk: add_opp: Set OPP pair (2304000000 Hz, 920000 uv) on cpu6
[    0.336163] clk: add_opp: Set OPP pair (300000000 Hz, 572000 uv) on cpu7
[    0.336645] clk: add_opp: Set OPP pair (2304000000 Hz, 920000 uv) on cpu7
[    0.336956] clk: add_opp: Set OPP pair (300000000 Hz, 568000 uv) on soc:qcom,cpu0-cpu-l3-lat
[    0.336969] clk: add_opp: Set OPP pair (300000000 Hz, 568000 uv) on soc:qcom,cpu6-cpu-l3-lat
[    0.336980] clk: add_opp: Set OPP pair (300000000 Hz, 568000 uv) on soc:qcom,cdsp-cdsp-l3-lat
[    0.338091] clk: add_opp: Set OPP pair (1459200000 Hz, 756000 uv) on soc:qcom,cpu0-cpu-l3-lat
[    0.338105] clk: add_opp: Set OPP pair (1459200000 Hz, 756000 uv) on soc:qcom,cpu6-cpu-l3-lat
[    0.338118] clk: add_opp: Set OPP pair (1459200000 Hz, 756000 uv) on soc:qcom,cdsp-cdsp-l3-lat
[    0.339104] sched-energy: Sched-energy-costs installed from DT
[    0.340268] cpufreq: driver osm-cpufreq up and running
[    0.340293] clk: clk_cpu_osm_driver_probe: OSM CPUFreq driver inited
[    0.344594] cam_cc-sdmmagpie ad00000.qcom,camcc: Registered Camera CC clocks
[    0.345114] qmp-aop-clk soc:qcom,aopclk: Registered clocks with AOP
[    0.346279] clk-rpmh soc:qcom,rpmh: Registered RPMh clocks
[    0.347430] disp_cc-sdmmagpie af00000.qcom,dispcc: Registered Display CC clocks
[    0.353445] gcc-sdmmagpie 100000.qcom,gcc: Registered GCC clocks
[    0.354360] gpu_cc_gmu_clk_src: set OPP pair(19200000 Hz: 49 uV) on 506a000.qcom,gmu
[    0.354379] gpu_cc_gmu_clk_src: set OPP pair(200000000 Hz: 49 uV) on 506a000.qcom,gmu
[    0.354526] gpu_cc_gx_gfx3d_clk_src: set OPP pair(180000000 Hz: 49 uV) on 5000000.qcom,kgsl-3d0
[    0.354593] gpu_cc_gx_gfx3d_clk_src: set OPP pair(700000000 Hz: 385 uV) on 5000000.qcom,kgsl-3d0
[    0.354619] gpu_cc_gx_gfx3d_clk_src: set OPP pair(825000000 Hz: 417 uV) on 5000000.qcom,kgsl-3d0
[    0.354677] gpu_cc-sdmmagpie 5090000.qcom,gpucc: Registered GPU CC clocks
[    0.355933] video_cc-sdmmagpie ab00000.qcom,videocc: Registered Video CC clocks
[    0.357753] KPI: Bootloader start count = 61534
[    0.357757] KPI: Bootloader end count = 267083
[    0.357760] KPI: Bootloader display count = 1438326266
[    0.357762] KPI: Bootloader load kernel count = 2470170460
[    0.357766] KPI: Kernel MPM timestamp = 285504
[    0.357768] KPI: Kernel MPM Clock frequency = 32768
[    0.357777] socinfo_print: v0.15, id=365, ver=1.0, raw_id=230, raw_ver=0, hw_plat=34, hw_plat_ver=65536
[    0.357777]  accessory_chip=0, hw_plat_subtype=0, pmic_model=65576, pmic_die_revision=131072 foundry_id=3 serial_number=4193517931 num_pmics=2 chip_family=0x60 raw_device_family=0x6 raw_device_number=0xc nproduct_id=0x40f num_clusters=0x1 ncluster_array_offset=0xb0 num_defective_parts=0xc ndefective_parts_array_offset=0xb4 nmodem_supported=0xff
[    0.357842] Minidump: Enabled with max number of regions 200
[    0.357875] Failed to setup PIL ipc logging
[    0.357878] msm_bus_fabric_rpmh_init_driver
[    0.357960] msm_bus: Probe started
[    0.358208] msm_bus_device 16e0000.ad-hoc-bus: Bus type is missing
[    0.358239] msm_bus_device 16e0000.ad-hoc-bus: Bus type is missing
[    0.358246] msm_bus_device 16e0000.ad-hoc-bus: Bus type is missing
[    0.358267] msm_bus_device 16e0000.ad-hoc-bus: Bus type is missing
[    0.358948] msm_bus: DT Parsing complete
[    0.361009] msm_bus_fab_init_noc_ops: Invalid Bus type
[    0.361083] msm_bus_fab_init_noc_ops: Invalid Bus type
[    0.361095] msm_bus_fab_init_noc_ops: Invalid Bus type
[    0.361141] msm_bus_fab_init_noc_ops: Invalid Bus type
[    0.366739] uw_ldo_ois_drv_regulator: supplied by pm6150l_bob
[    0.367341] arm-smmu 5040000.arm,smmu-kgsl:  non-coherent table walk
[    0.367346] arm-smmu 5040000.arm,smmu-kgsl:  (IDR0.CTTW overridden by FW configuration)
[    0.367350] arm-smmu 5040000.arm,smmu-kgsl:  stream matching with 5 register groups
[    0.368707] register_client_adhoc:find path.src 161 dest 627
[    0.368776] register_client_adhoc:Client handle 1 apps_smmu
[    0.368873] arm-smmu 15000000.apps-smmu:     non-coherent table walk
[    0.368878] arm-smmu 15000000.apps-smmu:     (IDR0.CTTW overridden by FW configuration)
[    0.368882] arm-smmu 15000000.apps-smmu:     stream matching with 79 register groups
[    0.369588] register_client_adhoc:find path.src 161 dest 627
[    0.369645] register_client_adhoc:Client handle 2 apps_smmu
[    0.369744] register_client_adhoc:find path.src 161 dest 627
[    0.369798] register_client_adhoc:Client handle 3 apps_smmu
[    0.369871] register_client_adhoc:find path.src 22 dest 773
[    0.369903] register_client_adhoc:Client handle 4 mnoc_hf_0_tbu
[    0.369980] register_client_adhoc:find path.src 22 dest 773
[    0.370007] register_client_adhoc:Client handle 5 mnoc_hf_1_tbu
[    0.370100] register_client_adhoc:find path.src 137 dest 772
[    0.370131] register_client_adhoc:Client handle 6 mnoc_sf_0_tbu
[    0.370188] register_client_adhoc:find path.src 154 dest 10076
[    0.370208] register_client_adhoc:Client handle 7 apps_smmu
[    0.370283] register_client_adhoc:find path.src 161 dest 627
[    0.370340] register_client_adhoc:Client handle 8 apps_smmu
[    0.370420] register_client_adhoc:find path.src 161 dest 627
[    0.370473] register_client_adhoc:Client handle 9 apps_smmu
[    0.370795] vgaarb: loaded
[    0.370921] qcom,qpnp-misc c440000.qcom,spmi:qcom,pm6150@0:qcom,misc@900: probe successful
[    0.371201] SCSI subsystem initialized
[    0.371239] usbcore: registered new interface driver usbfs
[    0.371247] usbcore: registered new interface driver hub
[    0.371345] usbcore: registered new device driver usb
[    0.371546] usb_phy_generic soc:usb_nop_phy: soc:usb_nop_phy supply vcc not found, using dummy regulator
[    0.371790] xiaomi_touch_probe enter
[    0.371793] xiaomi_touch_parse_dt touch,name:xiaomi-touch
[    0.371819] xiaomi_touch_probe over
[    0.371935] qcom,qpnp-power-on c440000.qcom,spmi:qcom,pm6150@0:qcom,power-on@800: PMIC@SID0 Power-on reason: Triggered from Hard Reset and 'cold' boot
[    0.371958] qcom,qpnp-power-on c440000.qcom,spmi:qcom,pm6150@0:qcom,power-on@800: PMIC@SID0: Power-off reason: Triggered from KPDPWR_N (Long Power Key Hold)
[    0.372053] input: qpnp_pon as /devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-00/c440000.qcom,spmi:qcom,pm6150@0:qcom,power-on@800/input/input0
[    0.372835] qcom,qpnp-power-on c440000.qcom,spmi:qcom,pm6150l@4:qcom,power-on@800: PMIC@SID4 Power-on reason: Triggered from PON1 (Secondary PMIC) and 'cold' boot
[    0.372859] qcom,qpnp-power-on c440000.qcom,spmi:qcom,pm6150l@4:qcom,power-on@800: PMIC@SID4: Power-off reason: Triggered from SOFT (Software)
[    0.373002] media: Linux media interface: v0.10
[    0.373010] Linux video capture interface: v2.00
[    0.373022] pps_core: LinuxPPS API ver. 1 registered
[    0.373024] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.373029] PTP clock support registered
[    0.374398] thermal_sys: VIRTUAL-SENSOR board sensor:
[    0.374401] board sensor: VIRTUAL-SENSOR
[    0.375507] tsens_tm_probe : unable to create IPC Logging 0 for tsens 0x000000000c263000
[    0.375509] tsens_tm_probe : unable to create IPC Logging 1 for tsens 0x000000000c263000
[    0.375512] tsens_tm_probe : unable to create IPC Logging 2 for tsens 0x000000000c263000
[    0.376266] tsens_tm_probe : unable to create IPC Logging 0 for tsens 0x000000000c265000
[    0.376269] tsens_tm_probe : unable to create IPC Logging 1 for tsens 0x000000000c265000
[    0.376272] tsens_tm_probe : unable to create IPC Logging 2 for tsens 0x000000000c265000
[    0.376697] EDAC MC: Ver: 3.0.0
[    0.377404] platform soc:qcom,ion:qcom,ion-heap@27: assigned reserved memory node qseecom_region@9e400000
[    0.377439] platform soc:qcom,ion:qcom,ion-heap@19: assigned reserved memory node qseecom_ta_region
[    0.377469] platform soc:qcom,ion:qcom,ion-heap@13: assigned reserved memory node sp_region
[    0.377495] platform soc:qcom,ion:qcom,ion-heap@10: assigned reserved memory node secure_display_region
[    0.377585] ION heap system created
[    0.377676] ION heap qsecom created at 0x000000009e400000 with size 1400000
[    0.377683] ION heap qsecom_ta created at 0x00000000fb400000 with size 1000000
[    0.377689] ION heap spss created at 0x00000000fc400000 with size 800000
[    0.377696] ION heap secure_display created at 0x00000000f5800000 with size 5c00000
[    0.389140] platform soc:qcom,ion:qcom,ion-heap@14: ion_secure_carveout: creating heap@0x9f800000, size 0x1e00000
[    0.389146] ION heap secure_carveout created
[    0.389167] ION heap secure_heap created
[    0.389790] qupv3_geni_se 8c0000.qcom,qupv3_0_geni_se: geni_se_probe Failed to allocate log context
[    0.389957] iommu: Adding device 8c0000.qcom,qupv3_0_geni_se:qcom,iommu_qupv3_0_geni_se_cb to group 0
[    0.390031] qupv3_geni_se ac0000.qcom,qupv3_1_geni_se: geni_se_probe Failed to allocate log context
[    0.390168] iommu: Adding device ac0000.qcom,qupv3_1_geni_se:qcom,iommu_qupv3_1_geni_se_cb to group 1
[    0.390473] PMIC@SID0: PM6150 v2.0 options: 0, 0, 0, 0
[    0.390571] PMIC@SID4: PM8150L v3.0 options: 0, 0, 0, 0
[    0.390608] spmi spmi-0: pmic_arb_wait_for_done: transaction failed (0x3)
[    0.390610] read failed rc=-5
[    0.390612] Invalid REVID peripheral type: 00
[    0.390618] qcom,qpnp-revid: probe of c440000.qcom,spmi:qcom,pm8009@a:qcom,revid@100 failed with error -22
[    0.391187] register_client_adhoc:find path.src 90 dest 512
[    0.391351] register_client_adhoc:find path.src 90 dest 585
[    0.391404] register_client_adhoc:find path.src 1 dest 676
[    0.391494] register_client_adhoc:find path.src 143 dest 777
[    0.391523] register_client_adhoc:Client handle 10 ipa
[    0.392931] ipa ipa3_smp2p_probe:7956 fail to get smp2p clk resp bit -517
[    0.393436] iommu: Adding device soc:ipa_smmu_ap to group 2
[    0.393628] iommu: Adding device soc:ipa_smmu_wlan to group 3
[    0.393930] iommu: Adding device soc:ipa_smmu_uc to group 4
[    0.396227] ipa ipa3_smp2p_probe:7956 fail to get smp2p clk resp bit -517
[    0.400456] Advanced Linux Sound Architecture Driver Initialized.
[    0.401240] Bluetooth: Core ver 2.22
[    0.401354] NET: Registered protocol family 31
[    0.401358] Bluetooth: HCI device and connection manager initialized
[    0.401379] Bluetooth: HCI socket layer initialized
[    0.401386] Bluetooth: L2CAP socket layer initialized
[    0.401431] Bluetooth: SCO socket layer initialized
[    0.402046] NetLabel: Initializing
[    0.402051] NetLabel:  domain hash size = 128
...

From TWRP, uninstall magisk, to rule out Magisk modules creating this //If it works update to Magisk v23 and add modules one by one to identify culprit - this is a guess and not based on logs

Thanks for this info. Finally I solved by reflashing the original boot.img.

The problem was with the boot image.
Solution steps:

I searched for exact POCO X3 NFC rom .TGZ file, and found it here:
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.7.0.QJGEUXM/

I downloaded the following file:
surya_eea_global_images_V12.0.7.0.QJGEUXM_20201221.0000.00_10.0_eea_6c03e13a9f.tgz

Extracted the "boot.img" file

Using
adb reboot bootloader
rebooted phone into bootloader mode.

Using
fastboot flash boot boot.img
finally I flashed the original boot.img

Rebooted with long press power button

Booted fine into MIUI.


text:
How to automate user actions?
I've seen a few questions similar to this before, but they all seem to be concerned with performing tasks in apps rather than actually simulating user action (e.g. swipes, taps, keypresses, etc.) in a similar manner to how AHK would work on Windows. I've seen a few solutions on the web calling for things like SL4A, but I can't find a clear explanation as to how I would go about fully automating an Android device.
Basically, what I want to do is open an app and activate a script (or something to the effect of a script, maybe an APK?) that will click on buttons and swipe up and down in a predetermined pattern (again, think AHK for Windows). Is something like this possible?

With Tasker and Autoinput app, yes.

There's lots of automation apps with such capabilities, like Automate: https://play.google.com/store/apps/details?id=com.llamalab.automate


text:
How to make Joplin app in my Android phone read-only?
I am using Joplin note taking app both in my Ubuntu 20.04 PC and Android phone running Android 10. I sync my notes from both devices into my Dropbox account such that the notes are same in both my PC and phone. I edit and add new notes from my PC only and use my phone to only read the notes. But sometimes by accident, I end up editing or outright deleting my notes from my phone.
So how can I set my Joplin app in Android phone to read-only mode to prevent any accidental deletion or update?

There are multiple apps in Play Store named "Joplin". Please edit your question and include a link to the app in Play Store you are talking about.

@Robert most likely this one but it is best if OP links it themselves.

If this is about this Joplin app, the app is open-sourced. Perhaps you (or anyone) can make a feature request if this feature hasn't been implemented.


text:
How can I configure Android to prevent the apparition of epilepsy-prone flashing displays?
From time to time, some program or website has epilepsy-prone flashing displays (Example - do NOT click if you are prone to epilepsy). Is there any to configure Android to prevent such displays so that individuals with epilepsy can avoid epileptic seizures when using their phone?

Control over such websites would come from the browser, so there is nothing Android can do there per se. Don't know about apps though.

@Firelord I was hoping they could prevent it at the OS level.

While I don't have epilepsy, this looks like a very interesting topic. However, a genuine question: do you know some ways to avoid it so that, while not perfect, we can perhaps find alternative solutions? I found some on (Web) accessibility for seizures and physical reactions to think if some apps can do it (like reduce screen's FPS to less than 3). But... even with Android being more than 10 years old, with millions of users & developers but no solution until now, I'm afraid it's not that easy...

From what I just checked on a couple Android devices, the Android developers have provided multiple settings to help those with various health conditions, but I see none that will likely help those with epilepsy not suffer from consequences of the well-known flashing screen trigger.
It's definitely something that could be handled at the OS level, but from what I've seen, it has unfortunately not been prioritized by the Android developers or their for-profit corporate overlords.
BTW, Gammy is an open-source project for Linux, FreeBSD, and Windows (not Android) that implements techniques that could potentially be modified to help those with epilepsy.  Converting it to a proof-of-concept that software can be written to help persons with epilepsy would not be too difficult.

Bummer, thanks for checking!

You're welcome Franck.  I added another section to the answer that might be of interest to you and others.


text:
How do I add an Outlook email signature on new Nokia 8V?
Recently upgraded on Verizon to the new Nokia 8V android phone.  I can't find anyway to add/change my Outlook email signature.
Any help is appreciated

In the Outlook Help PDF for Windows, the path is New Email > Signature, perhaps the same mechanism? Notably, the PDF for Android-based Outlook, and iOS-based Outlook are both devoid of signature instructions. Perhaps Mobile versions don't allow it?

To add a signature (text not html) on Outlook, simply go to Settings -> Signature.


text:
Galaxy S10+ - Gallery broken in weird ways - can't see pictures, can't save camera photos and can't take screenshots
I'm having a very strange problem today with my Galaxy S10+.
I had an update yesterday evening, and all of today it's been broken in a weird way. This'll be a longish post because I want to be really clear about the problems I'm having and explain what I've done so far to try fix it. Right off the bat I want to note that these problems are not exclusive to my SD card. My SD card works just fine and my pictures are stored across both my internal storage and the SD card. I've tried most of my troubleshooting with and without it in.
These problems occurred immediately after I finished an update. The Software Update Information says "G975FXXU9FUBD / G975FOTF9FUBD / G975FXXU9DUBD"
Basically, when I open the stock Gallery app, it shows absolutely nothing. None of my pictures or albums show at all. However, the automatically generated Stories work just fine. I can't select anything, I can't highlight anything, I can't change anything. All I see is a blank screen where I can swipe endlessly between Pictures and Albums and see a whole lot of nothing.
My files are perfectly fine and safe from what I can see. I've hooked it up to my computer and nothing is missing, damaged, broken or corrupted. They are all there in the My Files app and show all the thumbnails for the pictures. I've downloaded another Gallery app from the Play Store and all the pictures are there in the right order and the albums are there too.
But, if I say open a picture in My Files and click Gallery as the app to open the image with, it'll hang for a while then open a black screen with no buttons on it except the home bar, and all I can do is back out of it. Strangely, when I open the app tray after this, it'll only show the My Files app being open and not Gallery.
There are two very strange aspects to my problem too - I can't take photos with the camera or screenshots.
The Camera app won't save photos no matter whether I choose to point them to the internal storage or the SD card. It'll show the little preview box showing a picture was taken and do the little animation, but after a while that just turns back into the generic Gallery icon, says "Warning, camera failed" and closes itself.
If I'm quick and click on the icon that shows the picture I took, it'll just do the same thing. If I try click there before taking a picture, it'll just open the broken Gallery app after a delay of a few seconds.
I'd love to show some screenshots of my problems but I also can't take screenshots. I can press the button for it and get the overlay, but if I try to crop them or let it save, it just hangs on the overlay screen and I can't interact with anything and can only back out.
I can still save photos from online or from apps like Twitter, and apps like Messenger or Line which I use very often allow me to open and browse media and send pictures just fine. They also let me save pictures taken with the camera as long as it's through those apps and it saves those photos as I've set it in the settings of those apps, and I can see them in the My Files app right after.
After spending the whole day googling as best I can, so far I've tried the following;

Booting in Safe Mode (both with and without the SD card in) - The same problem exists in Safe Mode
Clearing the Cache/Data for various apps like Gallery, Media and Devices, My Files, Camera and all sorts
Looked for files called ".nomedia" on both the phone itself and through my computer and found nothing.
I was going to try deleting the "com.android.gallery3d" folder as suggested in a post which sounded a lot like my problem, but turns out I don't have that folder in the directory the post suggested.
Using a "media rescan" app.
Forcing an update through the Galaxy Store but it couldn't find an update for Gallery and wouldn't let me do anything with it.
Pressing the "uninstall update" button on the Gallery app settings page and it remained the same. Updated it through the Galaxy Store and no prizes for guessing the outcome there.
Literally just turning my device off for an hour and leaving it, then back on.
Literally just leaving the device on, locked for an hour.
Literally just leaving the device on with the Gallery app open in case it needed to refresh or something.

I've tried most of these both with and without the SD card in too.
I feel the problem has to be centred around Gallery because it's only ever when an app needs to use it as a medium for saving, viewing or interacting with a picture where it has issues.
The only thing I can really see that might be causing a problem is that I've got a LOT of pictures and videos. We're talking well over ten thousand pictures spread across the internal storage and the SD card. But a day ago when it worked perfectly fine that didn't seem to be an issue.
I've been using it all day and besides the gallery thing it's worked just fine. No other apps seem to be broken or have had any weird issues. My notifications are as they normally are. It's literally just any time I need to use the Gallery app.
So far all my troubleshooting has done is bother me by deleting the wallpapers and theme/icons I had on after coming out of Safe Mode. I'm completely stumped as to what to try short of a full factory restore, and I really don't want to have to take that option.
Any help would be really appreciated.

Have you tried to clear app data/cache of the gallery app? What is wired is that you can see the files from PC via USB/MTP. Have you tested if you can copy the files to the PC and they can be opened on the PC?

Clearing the app data and cache was one of the first things I tried, both in and out of Safe Mode.
All the files work fine on the PC. I'm currently working on moving them all across to back them up, and it's slow going but working just as you would expect. I don't think it's to do with my files as they work just fine in all other apps, it's cantered around the Gallery app.

Then some Samsung specific cache and/or thumbnail file(s) on device may be corrupt.

Okay so I seem to have fixed it. Robert gave me an idea, so I checked the button on the Apps settings page so I could view all the system apps, and then I cleared the data and cache of everything I could related even slightly to UI, media, storage, photos, videos and everything in between. I'm not sure at which point it was fixed, but it seems to have done the trick.

I had a very similar problem on my S10+:

Camera wouldn't save photos (though 3rd party camera app worked)
Screen capture wouldn't save
Opera browser wouldn't save downloads (though another browser worked)
Gmail wouldn't save attachments
Random Gmail crashes, usually 10-20 seconds after starting

It was pretty frustrating, especially the Gmail crash. Anyway, I took your advice and deleted the data/cache of various system apps one by one, then retested.
Happy to report that everything went back to normal after deleting data/cache from "Sec Media Storage"


text:
Disabling lock screen app in a Oukitel WP5 Pro afr
A friend just bought a Oukitel WP5 Pro powered by Android. It's up and running but he doesn't want the lock screen. In security it does not give the option "none". I went into app manager it doesn't so the app so i can't disable from there, I would really like some help. If I have to do a hard reset was should I do before I do it? I would like answers specifically for the Oukitel WP5 Pro. Thank you

Generally, there should be an equivalent of "swipe" when choosing the lock screen, but based on what I observe, it's not possible to remove the lock screen completely since it's baked into the Android system.

Do you get this message in your lock screen security settings: "disabled by administrator, encryption policy or credential storage"?

lock screen is dependency for encryption, therefore you can (maybe) set to none only if start from fresh factory reset (no specific WP5 answer just broad suggestion)


text:
No or very poor cell signal in areas I know have good signal
My phone worked fine till about the middle of yesterday. I live out in the country but usually I see 3 to 4 bars sitting at my desk in the basement. But now even if I walk up to the top of the hill (200 ft) on the property, from which I can see 3 cell towers, the signal comes and goes. For about 30 seconds there is full strength and then nothing, and I mean absolute zero signal, for a minute or 2. I had this problem last year as the phone was in warranty I just got a replacement. I figured the antenna wasn't connected correctly and it came loose. But to suddenly get this bad again, and I am sure I haven't dropped or jarred phone, I have to think something else is screwed up.
This morning I figure since I hadn't done any updates in a while I should do them. I used my WiFi connection to update and it worked for a couple minutes after I did the update, then the signal was gone again. This makes me think some setting is messed up but where and how to fix it is my problem.
As I drive around I get signal, but noticeably I have to be closer to a tower to get signal and then it gives me 4 to 5 bars otherwise nothing.
I have checked the "Mobile Network" settings; "Roaming" is on, "Preferred Network Type" is set to "Global", and "Enhanced 4G LTE Mode" is on. I have tried changing them all but no difference.
If it is relevant my phone is Motorola Moto E6
This is such an odd problem I am not even sure where to start digging for answers


text:
Where does the work profile app data stored? How to access them?
I am using Total Commander to view files in phone storage. I only see /emulated/0. I need to view and modify files in my work profile.
Any adb command or tool I can use?

Run adb shell pm list users to get a list of users. I have a work profile set up through Island, so I get
    UserInfo{0:Owner:13} running
    UserInfo{10: Island :50100030} running

The first number on each line is the user ID. This means the system user stores its files at /storage/emulated/0/, while Island (work profile) uses /storage/emulated/10/, at least on my device.
To access this directory, refer to this answer.


text:
No keyboard in lock screen
I really want to avoid factory resetting the phone since I know the password but just cant type it in.
Things I tried and failed:

rebooting my phone
adb since no usb debugging

Phone: Huawei Honor V10 on EMUI 9

Try to connect a simple USB keyboard (best no integrated USB hub, card reader, RGB lights,... ) via USB OTG adapter. Most phones support OTG which should allow you to enter the password/PIN

This works! Thanks!


text:
app keystore and certs in phone storage?
is there method to view and export files from phone storage keystore?
the android app i got has the keystore to managed digital user certs, it can be viewed via UI, i wanted to view them in phone storage but could not locate them.

Please be specific. Android has several "keystore" systems. Are you referring to the AndroidKeystore? This on modern devices a hardware protected storage for certificate and private keys. Which app are you  talking about?

@Robert the app that developer design encrypted the user and CA certs in 'Keystore'. I thought it should be visible in app location but i did not see any file. so I wondering what other method to view it.

Decompile the app and search for AndroidKeystore. It it uses this keystore type and you are on a recent device then the private keys are stored hardware protected. The keys can only be used on the device but not extracted. The AndroidKeystore is a system service that stores all keys+certs of all apps on the system.

@Robert i have the apk file only. can i decompile it? i did not own the source codes.

Decompile it e.g. using Jadx and search for the term AndroidKeystore.


text:
USB Camera for Google Duo in Philips Android TV
I have a Philips 49pus7503 Android TV. As you know, Google allows Duo calls on Android TV at late 2020. As I read in Google Duo in Android TV article from Google, it says that "Simply connect USB camera to TV, after that you can use this camera with microphone also.". I connect my old Logitech C270 camera, however Duo cannot find the camera. How can I do ? Thanks.

Looking at the Philips 49pus7503 manual online I don't see any mention of supporting a USB webcam.
And sadly, the Android Compatibility Definition Document gives device manufacturers the option of not supporting:

7.5.3. External Camera
MAY include support for an external camera that is not necessarily always connected.


text:
How to connect an encrypted phone to a network?
I forgot my PIN and my phone is encrypted. I cannot access any toolbar and all I can see is a black screen with the PIN request. I tried unlocking it through "Find my Mobile" but it does not work as my phone doesn't connect to any network due to it being locked. Is there any way to connect this encrypted phone to a network?

enter correct password for decrypting block device, or do factory reset. no workaround with find my device because android is not even started (and google removed unlock options anyway)

I do not think there is any other possible workaround besides finding the correct PIN or factory resetting the phone because the Android operating system hasn't even started yet so you can't turn on WiFi.

What you say is true for devices using Full Disk Encryption (FDE). As the OP mentions the black screen with the pin request this might indicate that the device indeed uses FDE. For newer devices using File Based Encryption (FBE) the PIN prompt would more look like a regular lock screen.


text:
wrong checksum(sha256) when copying from exfat samsung t7 touch external ssd to android(galaxy s10)
I bought a Samsung t7 touch SSD(1TB), it works just fine with my computer. but when I copy some files(200MB<) from the SSD to my phone which is a galaxy s10 the files get corrupted, and sometimes the SSD automatically disconnects itself from the phone while copying files.
I use the USBc to USBc cable that comes in the box.
Strange thing is that when it use the USBa to USBc cable in SSD's box and a USBa to USBc adapter that came with my phone, it is ok, but transfer speed is really slow.
By the way the USBc to USBc cable is not faulty cause I tested the cable with the SSD and my PC and it works fine, meaning all the files copy fast and with no problem regarding checksums.

probably related to MTP bug

@alecxs This question if I understand correctly seems to use the SSD via USB OTG. Thus there is no PC and MTP involved.

If you use the USBa workaround how much speed si "slow"? USB 2.0 speed ~30 MB/sec or USB 3.0 speed 500MB/sec? Have you tried different USBc cables? Have you experienced battery problems with your phone? More speed means much higher power consumption of SSD+phone, may be the battery does not supplay enough and the bits degrade.

when I use the USBc to USBc cable in the box connecting my phone directly to the SSD the problem exists, but when I use USBa to USBc adapter with USBa to USBc cable it's ok.


text:
How do I make the Calendar app stop harassing me about permissions?
A few months ago I got a new phone.  After a bit, I tapped on the Calendar app, and it popped up with a supremely silly request: it wanted access to my contact list!
Now there's no good reason why an app should need my contacts in order to show me a calendar, so I denied the permission, figuring it would go on just fine without it.  Apparently not; though!  The app failed to launch, and ever since then, multiple times a day, it's been throwing notifications at me that the Calendar app needs me to go in and enable that permission.
Well, screw that!  There is no conceivable reason why a calendar app could possibly require access to my contacts to run.  To support certain features, perhaps, but to run at all?  No.  Just no.  But it keeps spamming me with requests to enable it.
How do I make the notifications stop?  It's a system app that I can't uninstall, but at this point all I want is to shut the thing up!

What is the device model? Not all Calendar apps behave like that, so without any more information, it's difficult to find the solution. Otherwise... try a 3rd-party Calendar app instead.

Even if it is a system app you should be able to clear it's app data and may be even disable the whole calendar app. BTW: What is the package name of the calendar app? On my system the calendar app is not a system app.

OEMs suck, most of the times. That's why there's rooting and custom ROMs.


text:
Remove recently used emojis from Gboard
After switching from Samsung S7 Edge to Poco X3 NFC, although both on Android, I can't figure out how to remove recently used emojis, which is on Gboard.
I searched a lot but nothing related to Poco X3 NFC. The MIUI is 12.0.8
How to remove them from the keyboard?

clear data and cache of keyboard in settings >> apps >> gboard. i'd rather suggest to go for a keyboard which supports incognito mode like swiftkey

None of the trusted keyboards support this feature.
Start afresh after clearing data and cache of the app - Settings >> Apps >> G Board.
Then use incognito mode on keyboard if it supports. Microsoft SwiftKey has incognito mode. IDK about GBoard.

I agree not many keyboards are not "trusted", but I don't think I would put either Google's Gboard or Microsoft's SwiftKey in the "trusted" category.  Clear their data and cache and then use either for a couple weeks.  The amount of data that they will store during that time is nothing short of staggering.  Then try an open-source keyboard with similar functionality, and one can see the open-source keyboards will not store all that data.  I have yet to see anyone successfully explain what Google's Gboard and Microsoft's SwiftKey are really collecting/storing/transmitting.

I used the word 'trusted' based on "Contains ads" thing. I used to like some keyboard apps like fleksy but it has ads now. I know Google and MS are collecting data but just hoping that they are not selling it.

I had a similar experience.  I can't exactly remember the name of my old favorite keyboard app, but I think it was called Chrooma.  What I do remember is that it was great, and then they turned it into a promotion-filled mess.


text:
Can you connect to multiple vpns at the same time on android 11?
I have an always on VPN connection for security and privacy. I would like to connect to my home vpn for Music Player Deamon access. I would not like to announce my home IP to every WiFi I use. Can I and how to multi hop VPN on android 11, also second hop is conditional as I only want traffic for my system. I do not have root.

Does this answer your question? How to connect to multiple VPN in android

Not possible without root. With root you need to do manual configuration which requires at least basic familiarity with CLI.


text:
How to set Android home screen grid size to 6x6?
I use a Samsung Galaxy S9+. My home screen grid only allows till 5x6 grid. Is there any way to set customise grid layouts?

you need to install 3rd party launcher for example nova, cpl, rootless etc. they allow you to customize the home screen (not the samsung's).

You can try using another launcher. Nova Launcher for example allows to set 6x6 grid.
After installing, long-press on the home screen, select settings. When the settings open, click Home Screen -> Desktop grid, set it to 6x6.
There are other launchers that can also do it. Just search on your favorite app store.

I use Nova Launcher, it has many other nice features.

Install Good Lock from the Galaxy Store.
Then install Home Up in the 'Make Up' section.


text:
How to recover the encrypted data after a hard reset of a moto G8
I forgot my pattern to unlock my moto G8 so I decided to make a hard reset to access it; which I successfully did and gained access into my phone. I never had any data in the sd card nor google drive; I got access  to my Gmail acct, photos app etcetera; but then I realize that some apps like google messages, whats app, and some others didn't show the previous data or messages.
After trying to get that data I found that google has that old data encrypted and is asking me for the pattern (Which I forgot and that's the reason that I did the hard reset!!) I tried to get encrypted data using the new pattern with no success and i also used what I think was the old pattern but finally I got a warning saying that I have only 3 more chances to try the pattern before the data will be wiped off.
Does anyone of you guys know how to recover that encrypted data?


text:
How to use application buttons that are under the usual on-screen buttons (Back/Home/Tiled apps)
Many sites show buttons to accept/reject the cookie policy at the bottom of the screen. But on my phone (Xiaomi Note 7, Android 10) this puts them under the on-screen-buttons:

It seems that everything under the faint/thin line at the bottom is out of reach, either nothing happens or the on-screen buttons take precedence (on sites with thicker buttons, I can tap the button above the line)
Is there a way to avoid or mitigate this?

Zoom in the webpage near the navigation bar and than drag the content to the middle of the screen or wherever you are comfortable in accessing it. If you can't zoom in, then enable Force Zoom in your browser settings.  Chrome and Firefox both offer force zoom in their settings. Once enabled, zoom in would work on any site.

Turn on desktop site mode in your browser

How would that solve the problem?

@Firelord As far as my tests go it does, because in that case the site doesn't extend in the on-creen buttons area.

Works OK in the regular browser, but it turns out that my problem is mostly with sites displayed in the Reddit app and there is no such option.


text:
Unable to access Google Play store and Google Maps
I'm not able to access play store and maps with my google account, but it remains accessible with another google account.
I'm at a loss how to resolve this. Would anyone have any solution?

To try to resolve this, open a web browser and log into the Google Play store for your Google account by going to this URL:
https://play.google.com/store/account
When you do this, Google will request authentication information.  Once you provide this information, Google may allow you back into your own account again.  Or they may not; it's entirely up to their problematic systems which are documented incorrectly in their help database.
Google is infamous for locking people out of their own accounts, even when they provide their passwords.

This worked like a charm! I've been trying to find a solution for this since yesterday. Thank you!

You're welcome!  I'm glad to help, and I'm happy to hear it worked.  I'm not sure if you have sufficient reputation to upvote yet, but you can upvote helpful answers.  One thing I've learned as a general technique is to try to access anything broken from a different angle, such as from a web browser or a different OS.  That technique has helped me get out of jams a few times.


text:
One channel audio
When I record sound with my Samsung 9, with all the different apps (4 or 5) I've tested up to now, including the default one, the resulting file is one-channel.  Why?  Is there a way - if any - to have a 2-channel file as a result of an audio record via Android smartphone?  Thanks for any help.
Rodolfo

Have you tried to attach an external stereo microphone?

Yes, I did record trough an external microphone connected to the smartphone via a small USB sound card: and the result is still 1-channel.  The same microphone connected in the same way to the PC records in 2-channel mode.


text:
How to stop Samsung Galaxy S20 vibrating on resuming and entering lock mode?
My Samsung Galaxy S20 vibrates every time the screen times out and enters lock mode and vice-versa when I press the right button to exit the lock mode and start using the phone.
How do I remove this behavior?

its just a haptic feedback i guess. is it unbearable?

I understand, but it's my wife's phone and she's raising hell about it!

Someone here has same problem - https://eu.community.samsung.com/t5/mobile-apps-services/need-to-disable-vibrate-on-lock-unlock/td-p/1849864
It is different phone but I guess you can try. It is basically suggesting to turn off NFC.
Usual method - Settings>Sounds&vibration. Find settings related to vibration and keyboard feedback. Tweak settings to your liking.


text:
My RCA Voyager Tablet is in a bootloop and I can't get into recovery mode
Can anyone help me please, My RCA Voyager Tablet is in a bootloop and it keeps showing the logo screen. I was trying to install the trwp for my tablet but I think I accidentally put the worng trwp file into my RCA tablet. I tried to go into recovery mode but nothing happened and I tried flashing it but I couldn't find any firmware file for my model ( my model is rct6873W42) I also tried connecting my computer to my tablet and it's not detecting my RCA Voyager Tablet. I hope someone can please help? P.s I also think it's brick but I am not completely sure.


text:
Can I access "/data/user/0/" folder in Android emulator from Ubuntu PC?
I am using Ubuntu 18.04.
From Android Studio with the following code I am getting file directory
Context ctx = getApplicationContext();
final File filesDir = ctx.getFilesDir();

which is /data/user/0/com.example.ipfs/files/. I am running my app on Android Emulator. How do I go to the /data/user/0/com.example.ipfs/files/ folder from my PC?

If your emulator runs userdebug ROM so that ADBD runs with root privileges, then simply do adb root; adb shell ls /data/user/0/com.example.ipfs/files/. If it's a final user build (usually the one with Play Services), then you first need to root your emulator (MagiskOnEmulator). See Why are superuser permissions needed to acess /data partition? and Why “adb root” does nothing?

For this, Android Studio has the feature called Device File Explorer that will allow you to view the connected device or emulator internal files. This is useful especially when you are utilising the getFilesDir() as a path to save your app generated files & hence are not able to see them with the standard File Manager.
From the main menu, go to View -> Tool Windows -> Device File Explorer. You can then select your device / emulator from the drop down list.
To access /data/user/0/com.example.ipfs/files/, just go to the directory data/data/com.example.ipfs/files from the list displayed in the Device File Explorer once your device / simulator is connected.

I am using Ubuntu 22.04 right now I tried this solution using AndroidStudio2022 and it's work and I figure out it was pointing to a hidden files below..

PATH:
/home/[user]/.cache/Google/AndroidStudio2022.1/device-explorer/[device_emulator_name]/data/user/0/[project_name]
Example:
/home/awen/.cache/Google/AndroidStudio2022.1/device-explorer/Pixel_5_API_32
[emulator-5554]/data/user/0/com.example.html_pdf_demo


text:
Connected android device is not showing up in android studio in m1 Mac mini
I have installed android studio in m1 Mac mini and connected pixel-5 to it. The device is not listing, instead it is showing "loading devices". I have the same setup in intel MacBook Pro and it is showing the pixel-5 when connected. Thanks in advance.

Have you enabled on the phone Developer Options and then "Android Debug Bridge" option?

Is the ADB working? Try adb on the terminal (whether inside Android Studio or from Mac's)

@Robert the developer option is enabled already

@AndrewT. the adb seems to be working, checked adb devices and the device is showing

Fixed the issue, I tried with sample code from android studio itself, for that the a specific sdk version was missing. Installed that and after syncing Gradle file, the device is showing now.


text:
Is restoring WhatsApp media (photos) from Google Drive enough, or should I also sync it with Google Photos?
I have a Google Drive backup for my WhatsApp, and I think it also includes media (photos). But my phone is also filled with WhatsApp photos and I want to back it up to Google Photos. Now I am confused as to how the restore will work in case I lost my phone.
Will I only need to restore from Google Drive and it will include all the media? Or will I have to synch it with Google Photos as well?

Anything under /whatsapp/Media is part of WhatsApp GD backup.

@defalt at least if Settings > Chats > Backup > Including Videos is switched on.

If you backup it to Google drive it will include all the media


text:
Globally turn vibrations
This question comes up occasionally - but in the hope there is now a way to do it I'll ask again.
Is there a way to toggle vibrations (specifically on Samsung's UI 3.0)?
Example use-case: at work, with my phone on my desk, I'd rather have a quiet discreet sound notification than a vibration (which is more disturbing to my colleagues).
At the moment, I'd have to go through every single app and turn off vibration for all notifications to achieve this.
I struggle to believe that Google haven't introduced this in 2021!

A little less hassle. Turn vibration on or off on per app basis, not for every notification of every app individually: https://android.stackexchange.com/a/215658/218526

I currently hesitate to close this question as a dupe of your previous question: How do I disable all vibrations on a Samsung A51 running One UI 2.1?. Note that some features may be available on some devices but not on other devices, and Google doesn't fully control what Samsung (and other vendors) want to put on their devices.

@AndrewT. yeh, fair comment. The pedant in me did think that because it's new UI version it could be a different question. (and I'm utterly frustrated than Android doesn't have this 6 years after the other 2 main mobile OSs did, one of which they've effectively forced out of the market)


text:
Is it possible to create a .ISO or .IMG of my smartphone and emulate it in a Android Emulator?
I have a Moto G6 running Android 9. I would like to generate a ISO or IMG of my smartphone and load it by using a Android Emulator in a computer. Is that possible?

Android firmware is device specific and needs to be adapted to the hardware. For an emulator you need an image that has been created for the Android emulator.

@Robert I think that's a good answer! How about copy and paste it as an answer?


text:
Redirect the output of 'time' to a file
I'm getting the following error when trying to capture the output of time to a file (reference).
adb shell su 0 "{ time -p echo hello world; } 2> /data/local/tmp/file"
/system/bin/sh: syntax error: unexpected '}'

But the command is successful when running without su i.e. adb shell "{ time -p echo hello world; } 2> /data/local/tmp/file"
Please provide inputs on why it's not working when running with su.

Both ADB and Android's su aren't very sane when it comes to handling arguments. Quote the whole command you are passing to adb shell. Also provide -c to su like adb shell 'su -c "{ time -p echo hello world; } 2> /data/local/tmp/file"'.

-c with su is not working in my environment. It's throwing invalid uid/gid error. I checked with giving the command adb shell 'su 0 "{ time -p echo hello world; } 2> /data/local/tmp/file"', then it's considering entire thing as a command name. It's throwing the error su: failed to exec { time -p echo hello world; } 2> /data/local/tmp/file: No such file or directory.

You must be correct. As I already said, behavior of sh and su on Android devices is very much inconsistent. Strange things occur, even on different Android versions, particularly related to arguments and I/O streams. Better not rely on it for scripting. For interactive use first do adb shell and then run the command.

I'm getting similar error when I tried  to run the same command with sudo sudo { time -p echo hello world; } 2> /tmp/file in ubuntu terminal, but the command is successful without sudo.

Obviously that won't work. sudo runs an executable (the first argument), optionally with some arguments. But { is not and executable. Also your command ends at ;, so the terminal shell (bash or whatever you are using) doesn't know what } is. Because it's also not an executable, neither shell's built-in command. { and } just create a block within current shell to group some commands, like ( and ) create a sub-shell. So you need to run like: sudo sh -c '{ time -p echo hello world; } 2> /tmp/file'. I suggest you read about how to work with shell. It's not Android specific.


text:
How do you root a merlinnfc? (Redmi note 9/10X 4G)
Hey there people of this.. site.
I've tried every "Real" method of rooting xiaomi 11.0.5 (My current ROM)
I've tried patched vbmeta images, TWRP, and all of the one click root apps ( Yes my antivirus did flag all of them), and I mean ALL of them. Kingo root, king root, whatever.
I've tried 2 TWRP methods:
The official one: I flashed the recovery partition with the "merlin" image (Yes this did in-fact worked, and my OEM is unlocked btw)
Result: The recovery partition DID NOT BOOT. simply stayed at ADB recovery for a while and rebooted.
An un-official method: I flashed 3 main partitions. Vbmeta, Misc, and recovery. The result? A firm-brick. Somewhere in between in severity of a soft / hard brick. What I mean by this is that it booted and just.. stayed black. There wasn't even a post screen saying "REDMI Powered By Android", luckily it somehow went into ADB recovery allowing me to go into fastboot and flashing the stock global ROM. And.. it worked, thank God.
Other recovery ROMS don't seem to support this device (merlinnfc) like orange fox for example.
In a sense, I've tried everything, and I am yet to defeat the 2020 November security patch.

Does this answer your question? Kingo Root fails and gives error code 0x11f116 (Xiaomi Redmi Note 9)

Does this answer your question? How to install Team Win Recovery Project and Root Xiaomi Redmi Note 9


text:
How to get key to decrypt msgstore.db.crypt12 database in Whatsapp in non-root Android?
I want to decrypt msgstore.db.crypt12 in my non-rooted android phone. I tried multiple steps using adb but nothing worked
run-as com.whatsapp
adb backup com.whatsapp

How can I do so? Is there any way to backup full android to a file on laptop and extract key from it? Please suggest.

https://forum.xda-developers.com/showthread.php?t=2770982&page=33


text:
Android runtime permission's internal working?
I was checking Android runtime permissions and was very curious about how Android runtime permissions work. Like if some application is asking for access to external storage, it will ask for permission, user will be presented with a dialog, and after pressing allow button, app will be granted read/write external storage. I just want to know what happens internally when user presses allow button on the dialog, what are the changes internally occur in Android.
I know permissions are stored in different files like /data/system/packages.list, /data/system/packages.xml and /data/system/users/0/runtime-permissions.xml but changing them manually does not effect app's permission preference. So what actually happens when user give permission to certain app, what corresponding file gets updated?

What happens internally when you grant or revoke a permission depends on which permission you are talking about. In case of Storage permission, the Android framework switches mount namespace of the app process. See details in my answer to What is /storage/emulated/0/?. Similarly for some other permissions Android relies on kernel by mapping manifest permissions with DAC UIDs/GIDs/groups. See How Android's permissions mapping with UIDs/GIDs works?.

For many other permissions Android just keeps a record of the permission state in the files you mentioned and later ActivityManagerService enforces them on apps. Manually editing these files doesn't work because these files are cached in Android framework. You can reboot the device immediately to make changes effective. See an example case here: How to grant an app a permission that isn't in its manifest?

Thank you @IrfanLatif for your comments, actually I have read all your answer you have posted here and on XDA. As you said reboot the device immediately to make changes effective, will it work for all permissions, or only permissions which are handled by DAC?

It's not guaranteed that manual changes will always work. If the changes aren't justified (e.g. not requested in manifest or the app not entitled to have that permission), Android may reset them on reboot or when app tries to use that permission. In other cases manual changes should work for all permissions irrespective of whether the permission is handled by Android framework in Java stack itself or by some underlying kernel framework.

I just tried on my phone, disabling storage and microphone permissions from app settings and then changing them manually, with immediate reboot, it worked.

one more question what does flags do in this line <item name="android.permission.RECORD_AUDIO" granted="true" flags="300" />

Android's PackageManager/PermissionManager may attach one or more flags with a permission state for its internal record when simply remembering granted or revoked state isn't enough. E.g. when user taps on "Deny and don't ask again", Android attaches USER_FIXED flag to that permissions so that when the app asks again for the same permission, Android won't show the user the request dialog. 300 is binary number 100101100. Every 1 bit denotes a set flag.

See details here: https://developer.android.com/reference/android/R.attr#protectionLevel and here: https://github.com/aosp-mirror/platform_frameworks_base/blob/android-11.0.0_r1/core/java/android/content/pm/PackageManager.java#L3307

Thank you IrfanLatif.


text:
How to know if a broken screen phone has been factory reset?
I have an old Samsung phone with a broken screen and pass code but before I try to unlock my phone I want to know if there is any possible way to know if it has been factory reset because if it has then I won't need to open it.
I would also like to add that I have a different phone that has been factory reset so is there anyway to know if it has a backup?

How old? some phones can be flashed on locked bootloader, means availbility to flash adb enabled boot or recovery. some phones aren't encrypted, allowing raw dump of userdata partition

Honestly I'm not sure but it looks quite old, it has a duos symbol in the right hand corner and it's smaller than Tha palm of my hand with a rectangular Shape. Can I send u a Pic?

this should work for any Spreadtrum chipset, except no fastboot available, but you can gather information from heimdall and/or custom recovery (or even dump/flash boot partition straight from adb commands while on custom recovery) https://android.stackexchange.com/q/232319

combination firmware should have adb enabled by default, can be flashed without data loss. SuperSU for j1minive3g should work too, but not sure about this will wipe data

you should be able to reach download mode and flash TWRP custom recovery with heimdall. you can't copy files if device is encrypted, but you can modify boot or system from twrp adb shell. report back once you have adb shell, will give you instructions

First of all thx for all your help.     I'm not gonna lie tho but you seem very knowledgeable on the subject and I really barely understood anything (no offense, I just don't know much) so in summary I just need to find and download "adb shell" on my pc and then come back?

follow first link and download platform-tools. use any mobile phone for testing. enable usb-debugging in developer options and connect usb cable. execute adb.exe adb devices and authorize connection on phone screen. now you should be able to open adb shell you will see $ prompt. you can browse files for example cd /sdcard and ls. now you understand how successful adb looks like. you can now connect the broken phone and see if adb devices show something (probably not). But you can follow my last comment and flash TWRP. after flashing, boot into recovery and check adb shell is working


text:
Black screen when opening a random camera app on Galaxy S7 Edge on LineageOS 18.1
Since last week I upgraded my Samsung Galaxy S7 Edge from Samsung's stock firmware to LineageOS 18.1 by using this message of the XDA forum and installed the "full" edition of NicGApps. Since yesterday the camera does not always work, which is a behavior I never experienced on the stock Samsung firmware at all. When I open the camera app the screen is black. Also, when I change to the front facing camera. The only temporary solution is to reboot my device and everything works again.
During these two days, I rebooted my device three times, and that cannot be the intention. I tried this with several apps: OpenCamera, Footej Camera, the QR Code scanner of my banking app, all the same and as I wrote, after a reboot everything runs normal again. Does someone know a permanent solution?

When using an unofficial LineageOS version bugs like the one you describe can appear. Please report it in the XDA forum thread where you got the ROM from so that the ROM developer is aware of it and may be is able to fix it. Here we can do nothing to help you.

Thank you! I just posted the same question here

Looks like you're not alone... the post by Damjan94 on Mar 26 also mentioned this: "When videocalling with facebook, or discord, after 30 mins, or so, the camera stops responding, and both apps + provided camera app are only able to open a video stream for a second, before throwing an error that the camera couldn't be opened(discord and facebook just fail quietly)... a reboot fixes the camera, and it works fine for another 30 or so minutes."

... and browsing back the thread, there were some more reports about the camera issues.

Thanks, I downgraded to Lineageos 17.1, as mentioned in the thread.

Did that fix the issues you were experiencing?

Yes, everything works stable now

Great! Thank you for the update!


text:
How do I archive old phone numbers?
I have contacts from years ago (college friends, old colleagues, etc.) that I don't want to delete, but I also don't want to accidentally butt-dial at 3 am. How do I archive those old numbers for future use, but hide them from my phone app?
I've been told that I can put them all in a different gmail account, or under a different label, and then hide those from display in my contacts app, but that only works for when I'm using my contacts app. All those old phone numbers are still listed in my text and phone apps.
I've tried 4 different phone apps (Google Voice, Google Phone, Android Phone, and Should I Answer) and none of them appear to allow me to hide contacts or only view contacts from specific gmail accounts. Same issue with text apps (WhatsApp, Android Messages, Google Message, MySMS, etc.).
It really should not be this difficult to tell Android "I just want to see a list of numbers I created, not every single phone number I have ever saved in my entire life."

I agree 100%.  This problem is a PITA, and AFAIK Google has not offered any feasible solution.  In addition, if an app steals your list of contacts, or anyone's cloud database gets compromised, every single contact you ever had gets released into the wild.
My current solution is not ideal, and is really a workaround.  It consists of three primary processes:

Use only local contacts, and do not sync contacts at all.  If you really want synced contacts, sync them with a private cloud operating on your own server.

Regularly backup all your contacts to a CSV or JSON file.  Manually cut and paste all the contacts from that backup that you don't currently need to an "old contacts" file.  After removing many of the contacts from the original file, delete all contacts on Android and import the smaller file of current contacts.  Of course, before deleting anything, ensure the export-import round-trip will work and no data (such as contact images and custom fields) is lost.

Now that you have a smaller list of contacts on Android, assign a tag/label to contacts you still want to have handy, but you will rarely contact.  Then hide all contacts with that tag/label from showing.  As you noted, this only works in your contacts app, but the larger issue is dealt with by process #2 above.

This workaround model is certainly not ideal, and is time-consuming, but I know of nothing better offered by Google.  Remember, Google is primarily a data mining company, and they seldom offer tools that result in them collecting less of your data.
An alternative to the above workaround system is to move all contacts to the OpenContacts app or the Contact Book app.  They are both completely open-source and store all contacts in their own private databases.  Google apps and other apps cannot read those contact databases (unless they are malicious and breach the Android security model).  You can use one of those apps by itself or in combination with the standard Android contacts databases.  If you do this, all apps with appropriate Android permissions will be able to see the Android contacts, but not those stored in the OpenContacts app or Contact Book app.

Thank you! I'll probably try one of your workarounds. I'll feel safer knowing that my Contacts aren't being datamined or whatever, too.

You're welcome! One thing I also do is remove the Contacts permission from any app that does not really need my contacts.  Which, in my case, is every app except one.  Note that Google apps will often give themselves access to your contacts even after you have set them to have no access to your contacts.  This inappropriate sneakiness often happens when the device is rebooted or their apps update.


text:
Android device ro.crypto.state returns "encrypted", but I can access the /data partition. How?
I have a OnePlus 3 with an unlocked bootloader and LineageOS. I forget the PIN and I am trying to recover access to it, and I have access to the recovery. The data is encrypted.
My understanding is that, if the device is using FBE, the value adb shell getprop ro.crypto.state will return encrypted, and the /data partition will be impossible to read.
Despite the fact that adb shell getprop ro.crypto.state returns encrypted, and despite the fact that I have not entered the PIN stored in the hardware keystore, I am able to browse and copy files from /data using adb shell.
So this seems to be in conflict: I should not be able to access /data if that returns encrypted. Is this true? If not, why is this not a conflict?
(I apologize if this has been asked before, I could not find any questions on this.)

interesting, sure it is FBE encrypted? check recovery.log

I can't immediately check from that, but, adb shell getprop ro.crypto.type returns blank. It's Android 10 so it's probably FDE

That you can access FBE encrypted data files without unlocking is expected, check the file content. E.g. try to open an APK file from /data/app/ and execute a ZIP test on it. If it is a valid ZIP it is not encrypted.

OnePlus3 supports FDE. If forceencrypt flag is missing in fstab then the device is nit encrypted.

another easy way to check if /dev/block/dm-0 is mounted on /data your device is FDE encrypted (and in that case when TWRP didn't ask for screen lock - it is simply default_password)


text:
How do I force a new DHCP IP address on my Android?
I have a Linux system with the default DHCP server (ISC) and an Android phone Galaxy J7 which connects and gets its IP address from the DHCP server.
Right now, the Galaxy J7 was allocated an address automatically, but I'd like to force assign a different one. I've changed the settings in the DHCP server and I know those work since I had those used before and it was just fine. Now I changed the network IP address for my new WiFi router so the device was assigned a new IP automatically before I changed the setup to force the static IP.
How do I force the phone to pick the new IP address? I tried for forget the WiFi setup and re-enter it, but the exact same IP was re-assigned. So I think that the server memorize that IP. I looked in the leases:
less /var/lib/dhcp/dhcpd.leases

and I can't find the IP of my phone!?
I tried to restart the server too, but that usually doesn't help at all and guess what... It didn't do anything about the existing lease (and yet it's not in the list of leases!)
So I'm at a loss.
For Linux, I've seen that you can use dhcpclient -r and then dhcpclient to reassign a new IP. But for the Android, Termux says those commands do not exist. I probably need to properly reset on both side...
Someone has done that successfully before?

You should focus on server side. Android's DHCP client is in Java stack which isn't configurable or manually controllable. It's the server which remembers MAC vs. IP mapping and usually reassigns the same IP. DHCP client may also remember the IP address and may forward that in a new DHCP request but ultimately it's the server who decides which IP to assign.

@IrfanLatif Oh! I finally got it. The DHCP was not running correctly and thus did not properly distribute IP addresses. Once I fixed the server, the IPs were properly assigned again. Since I did not have any issues with my server in a long time, I did not think of checking that part. Thank you.


text:
Whatsapp Bug - Voice is not sent outside of local network
I encountered a somehow strange problem, which leaves me in the dark. I have a Samsung S10 connected to my local WLAN. When i call my relatives - whether voice or video call - my voice and video is not send to the other person. However, when i call my other phone - also connected to the local WLAN - everything just works fine. I disconnected the phone, deleted the WLAN connection, reinstalled WhatsApp and restarted the phone, but nothing seems to work. Calling my relatives from another phone also works just as expected.
Does anybody know a solution or a something i could try?

Several network devices on your or the internet provider side (for your connection or your relatives) can block Whatsapp voice/video traffic. Make test calls with other Whatsapp contacts outside of your network to check if the problem is your network[provider] or the one of your relatives.

Thank you for your answer. I already tested it with several relatives in different locations. Every other phone in our household works fine. I can only think of a hard reset, but i really would like to know the issue.

I was speaking about tests with other Whatsapp users outside of your household/WiFi.


text:
How to stop an SMS message thread from being a "conversation" in Android 10?
I have noticed today that in the SMS Messages app on Android 10, it's very easy to add someone to the "conversations" feature which enables contact-specific message and notification settings by clicking on the thread in question, clicking on the ellipses in the top right, then Details. The thread is then a "conversation". It is very easy to do this by mistake. I do not want specific messaging options for specific contacts.
On Android 11 a contact can easily be stopped from being a "conversation" by going to:
Messages thread > vertical ellipses ⋮ > Open Details > Click Notifications > Click "This is a conversation"
However, in Android 10 the "this is a conversation" option does not exist.
How does one remove a thread from being in a "conversation" on Android 10?
EDIT: This is for a Sony Xperia 10 II, the app in question is the standard Google messaging app.

Just to make sure this is not something that's customized by the vendor, consider mentioning the device model and the name/package of the SMS Messages app (I'm currently assuming it's the Google's one)

@AndrewT. thanks Andrew, updated.


text:
Faster alternative to `input`?
I'm trying to automate a task on my (non-rooted) Android phone.
While I have it "working" using input, it is quite slow due to taking ~0.7s per event. (Basically, I just need to send a bunch of tap events, so what I have now is a sequence of adb shell input tap $x $y.)
I tried sendevent, but it gives me "permission denied". (I'm not sure why; the device is allegedly writable by the input group, of which the shell user is a member... and obviously, the input command can send events.)
Is there some trick to getting sendevent to work? Or some way to send multiple commands in a single invocation of input?
I'd prefer solutions that don't require installing third-party software...

I would recommend to edit your post and add more details on the task you want to automate. Based on what you have written it seems to be related to typing text, but the rest is not clear, which makes it difficult to write a good answer.

@Robert, sorry... not text, just a bunch of tap events with known x,y coordinates. Basically, I just want to send a bunch of tap events to specific points, but it's really slow right now because input is slow.

See scrcpy Issues: Input (screen presses) via command line? and answer to scrcpy - Why your adb shell cmd execute so fast?

So... really crappy method: fork adb... as in, run it on the local shell in the background, using &. This is super-ugly and somewhat dependent on each instance executing with consistent timing (and probably not too polite to the android device, asking it to spin up all those Java processes), but it works.
Example:
tap() { adb shell input tap "$@" & sleep 0.02 }
tap 500 500
tap 600 600
tap 700 700

...will send tap events to (500, 500), (600, 600) and (700, 700) in fairly quick succession.

EDIT: Below you can find a way to use sendevent, however as I figured since posting, sendevent will not work on later Android devices, as access to input devices from shell has been explicitely disabled in SELinux policy. I don't know a way to work around this without rooting. The recommended way is to use UiAutomation#injectInputEvent. That's Java code, so one could write a service, which forwards events received on some interface. That leads far way beyond this question. Anyway, my sendevent solution you may still use on some devices.

You can find complete sendevent examples online (eg in this blog post), but none worked for me out of the box, so I had to tweak things a bit.
First of all, if you want to use sendevent, you should figure out the right event device first. getevent can be used to obtain this info, either getevent -p or getevent -i will tell you the event dev <-> device connections, so you can find the event associated with your touchscreen device.
You can also use getevent to see how a real tap event looks like on your device. Just run adb shell, start getevent, then tap on the screen (for some reason adb shell getevent didn't return the events):
/dev/input/event2: 0003 0039 000025e9
/dev/input/event2: 0001 014a 00000001
/dev/input/event2: 0003 0035 00000320
/dev/input/event2: 0003 0036 000002ae
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0003 0030 00000005
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0003 0039 ffffffff
/dev/input/event2: 0001 014a 00000000
/dev/input/event2: 0000 0000 00000000

You get a bunch of hex codes. Try the same with getevent -l:
/dev/input/event2: EV_ABS       ABS_MT_TRACKING_ID   000025e8
/dev/input/event2: EV_KEY       BTN_TOUCH            DOWN
/dev/input/event2: EV_ABS       ABS_MT_POSITION_X    000002f8
/dev/input/event2: EV_ABS       ABS_MT_POSITION_Y    000002f2
/dev/input/event2: EV_ABS       ABS_MT_TOUCH_MAJOR   00000005
/dev/input/event2: EV_ABS       ABS_MT_TOUCH_MINOR   00000004
/dev/input/event2: EV_SYN       SYN_REPORT           00000000
/dev/input/event2: EV_ABS       ABS_MT_TRACKING_ID   ffffffff
/dev/input/event2: EV_KEY       BTN_TOUCH            UP
/dev/input/event2: EV_SYN       SYN_REPORT           00000000

and you will see the labels for the codes (where applicable), so you can match the codes with the labels. If you don't want a generic solution, just want it to work on your own device, then you only have to recreate the tap sequence you've just seen. (Be careful with the hex codes, getevent prints hex, but sendevent expects decimal.)
This is the code I use in one of my scripts:
EV_SYN=0
EV_KEY=1
EV_ABS=3
BTN_TOUCH=330
BTN_TOUCH_DOWN=1
BTN_TOUCH_UP=0
SYN_REPORT=0

ABS_MT_TRACKING_ID=57
ABS_MT_POSITION_X=53
ABS_MT_POSITION_Y=54
ABS_MT_TOUCH_MAJOR=48
ABS_MT_TOUCH_MINOR=49

event_dev=`adb shell getevent -pl 2>/dev/null | sed -e ':a;N;$!ba;s/\n / /g' | awk '/ABS_MT_TOUCH/{print \$4}'`

tracking_id=1111
POS_X=600
POS_Y=800

adb shell "
        sendevent $event_dev $EV_ABS $ABS_MT_TRACKING_ID   $tracking_id
        sendevent $event_dev $EV_KEY $BTN_TOUCH            $BTN_TOUCH_DOWN
        sendevent $event_dev $EV_ABS $ABS_MT_POSITION_X    $POS_X
        sendevent $event_dev $EV_ABS $ABS_MT_POSITION_Y    $POS_Y
        sendevent $event_dev $EV_ABS $ABS_MT_TOUCH_MAJOR   5
        sendevent $event_dev $EV_ABS $ABS_MT_TOUCH_MINOR   4
        sendevent $event_dev $EV_SYN $SYN_REPORT           0
"

adb shell "
        sendevent $event_dev $EV_ABS $ABS_MT_TRACKING_ID   -1
        sendevent $event_dev $EV_KEY $BTN_TOUCH            $BTN_TOUCH_UP
        sendevent $event_dev $EV_SYN $SYN_REPORT           0
"

It works on my non-rooted device, but you may have to tweak it to match your device codes and sequences.


text:
Does software update decrease device performance?
I’ve been using an Android tablet for a month, and I’ve just got a notification on an update for my tab for Android 11 or One UI 3 (not sure if they mean the same thing). I’m on Android 10.
Based on my experience in using iOS devices, every major update decreases my older device’s performance and battery life for some reason. I’m used to seeing updates as something to avoid.
Do software updates have any bad effects on an Android device’s performance/battery life?

Apps tend to grow because of new features, new bug fixes for certain devices or Android versions. Larger apps have more code to execute, and require more RAM.


text:
Google Play Store uses mobile network, ignoring Data Saver settings?
One of my apps is allowed to use the mobile network, and all others are confined to wifi. This is specified in my Data Saver settings, but according to GlassWire, Google Play Store is still using the mobile network. Any suggestions on how to confine Google Play Store to wifi are welcome.

Google Play Store and Google Play Services self update is known to update when they "want" no matter if you are on WiFi or mobile and what settings you have configured.

That is a shame! Looks like another reason to avoid Android...

Yes, Google allows their apps to break all sorts of rules.  For example, turn permissions to their app off, then reboot, and you'll notice they get those permissions back.  It's sneaky and nasty.

Google Play Store and Google Play Services self update is known to update when they "want" no matter if you are on WiFi or mobile and what settings you have configured.
I am not sure if the respect data saver settings but as Google Play Store is a system app permissions and settings do not apply to it.
And you have agreed to those updates when setting up your device. The following screenshot is from the setup-wizard that shows up on a new device/after a factory reset (see section marked in yellow).

I don't mind updating, I do mind updating on the mobile net when wifi is available.

@eezacque When you are on Wifi mobile data connection is disabled, thus when you are on Wifi you are not on mobile. If your device does not use Wifi then because the Wifi connection seems to have no internet connection.