Nope .

OEMs these days store lockscreen password on some separate partition => resetting /data and /system doesnt make the phone 'forget' the prev password.

But there is a solution that works on most of the devices (the solution is flashing all partitions without formatting the partitions that store imei). Get the firmware flash tool for your device (eg sp flash for mediatek devices, something similar exists for qualcomm devices too).. A googling in the format "how to flash stock firmware on " would lead you to the right page.

I can't give any specific guide since you haven't mentioned your device model and there exists no generic guide except the outline I mentioned above.

I think i will just post links to the project called scrcpy and it does it over adb. There is no point in me tutoring about something that has been tutored on the internet.

https://github.com/Genymobile/scrcpy

https://www.xda-developers.com/scrcpy-control-android-on-pc/

Most of the apps are now not permitted to access /sdcard/data

• the only app i know which can access this folder is Files(not files by google)[com.google.android.documentsui]
• a few days ago i see this app called https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en&gl=us
  

~ $ ls /emulated/0/Android/data/
ls: cannot access '/emulated/0/Android/data/': No such file or directory
~ $ ls /sdcard/Android/data/

ls: cannot open directory '/sdcard/Android/data/': Permission denied

It asked the permission to access this folder, with files like allowing access to newly inserted memory card,

---

is there a way to make termux ask to allow access to that folder

---

or, is there a command to do it like, termux-setup-storage

Or is there a way to do it directly with am command

And I'm not a rooted user

I'm helping an organization that has a website with some moderate-level complexity, past the point of just a bunch of static web pages but not to the point where they have a developer on staff.

To catch anything that breaks as they make website updates, I'd like to set up some automated end-to-end tests to run daily to do things like fill out a form and make sure that it takes the user to the right page, and check a dashboard to make sure it shows the right information. I could write Selenium tests, but I'd prefer to do something that they can maintain and update themselves in the future without writing code.

Are there any tools that would let a user "record" interactions with a website (or easily program them from a visual interface) and set expectations for the result, and then allow the user to schedule the test to be run on a regular basis?

Thanks!

This is usually a https://github.com/SeleniumHQ/selenium/issues/8415 . You can fork chromedrive and add a fix.

I don't know what tools you are using but I see you have manual-testing tagged. There are a few very easy to use manual testing tools (DevTools & Lighthouse) available in your browser already that you can use for your initial exploratory testing and then build off of it.

I find that DevTools has some great performance tools built in. You can imitate a mobile device with a poor network connection very easily, with little to no knowledge//experience of performance testing.

Here are some great sites to get started:

1. https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/evaluate-performance/
2. https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/speed/get-started
3. https://www.digitalocean.com/community/tutorials/how-to-use-chrome-dev-tools-to-find-performance-bottlenecks
4. https://developers.google.com/web/tools/lighthouse/

I started using the label/notes section in the OnePlus Clock app for more detailed notes because then I could also get alarmed + reminded about them at certain times during the day. It's a fair bit of notes and reminders, enough to make me try very hard to retrieve them (and then never use the clock app for notetaking again).

I finally updated my Oneplus 6T to Android 11 (the update came out last November I believe) and the clock app updated too... with a 50 character limit on each alarm. I am now locked out of reading all my notes. However, the notes are still there. I know this because the preview text for the label/note is longer than the character limit and shows more than I am able to see when editing the note. If I were to save over the note with only 50 characters though, it would delete all the data and thus I am not touching the alarms at all until I get a fix.

Anyway, here's what I've thought of/tried:

• Any solution involving rooting my phone: would like to avoid this option for now as it seems risky for my given phone based on what I have read but would try if no other option works/if someone convinces me it would be fine

• Using adb backup to backup com.oneplus.deskclock's data: although I did this and I believe it was successful, I have no way of verifying what I backed up exactly (the backup file seems too small for what should be in it). I could use the android-backup-extractor on GitHub, but I doubt the data will be in text form (need the app to view the data is my guess) and I also could not figure out how to set it up anyway, so my next steps were...

• Using my backup.ab file to restore com.oneplus.deskclock's data in the app on a different device. So far I have tried using BlueStacks (OnePlus Clock APK installs, but when I attempt to open it, it never shows up, likely because not OxygenOS), my old OnePlus 3 (incapable of running the correct version of clock app needed, also tried restoring my backup--does not result in any new alarms showing up on the system clock app as you would expect), an Android emulator (have not even attempted yet because I'm not sure if it would be able to run the clock app since it isn't OxygenOS, mainly waiting for input here before I even bother trying that behemoth-sounding task), and my current OnePlus 6T (too scared to try installing a previous version as I'm worried it will potentially erase or compromise data).

I have already invested a lot of time into this and feel all my leads could be deadends and I don't want to spend more time than I have to do this. So, I'm seeking help here now in hopes someone can help me streamline the rest of what I have to do.

Following a factory reset after an Android problem, I started setting up my phone like it was a new one. Next day I was locked out of it for 24 hours, which I understand is a google protection system. Now I can login, but I get 'Android Starting ...'. This has been going on for over 60 minutes. What should I do?

Since Android 10, Android Auto is integrated as a system app but hidden for phone users. Users may have to install Android Auto for Phone Screens app to use it on their phones.

According to https://support.google.com/androidauto/answer/9468382 ,

Starting with Android 10, Android Auto is built into the phone as a technology that enables your phone to connect to your car display. [...]

If you don't have an Android Auto compatible car or prefer to access Android Auto on your phone screen, there are 3 options:

• If you're upgrading your phone from Android 9 to Android 10, make sure that your phone already has Android Auto installed before you upgrade. If so, the app icon will carry over to your newly upgraded device.
• You can use https://support.google.com/android/answer/2819582 to backup and restore from another device that already has Android Auto app installed.
• You can also go to the Play Store and download https://play.google.com/store/apps/details?id=com.google.android.projection.gearhead.phonescreen , which is only available on Android 10 or higher devices. Once you install the app, you can continue to use Android Auto on your phone screen.

---

According to GSM Arena, https://www.gsmarena.com/_doogee_s88_pro-10754.php comes with Android 10 already. Thus, Android Auto app is hidden by default and users need to install Android Auto for Phone Screens if they want to use it from their phone.

On the other hand, https://www.gsmarena.com/google_pixel_3a-9408.php comes with Android 9 and Android Auto pre-installed. Thus, when it's updated to Android 10 (and beyond), the app icon is still shown on the app drawer.

I damaged my old phone. The screen is almost completely shattered to the point I cannot see or touch it. Everything else works fine. I have a USB otg cable and can use a keyboard to type in my PIN. Is there a way I can retrieve my text messages? Even if I could just mount it for file transfer so I can copy over the latest backups that would be great. Now if I plug it into a computer nothing shows up because it's in 'charging only' mode. It is running LineageOS with root enabled. I thought it had adb but it is not working. I also can get into TWRP but can't get by the lock screen, I seem to recall the OTG doesn't work with TWRP.

Contents of recovery.log from adb pull

Starting TWRP 3.5.2_9-0-2bc3eccd on Mon Nov 13 05:17:09 1972
 (pid 590)
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/class/android_usb/android0/f_mass_storage/lun0/file' does not exist, USB storage mode disabled
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/class/leds/wled/brightness
I:Found brightness file at '/sys/class/leds/wled/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 1600
I:LANG: en
Starting the UI...
setting DRM_FORMAT_RGB565 and GGL_PIXEL_FORMAT_RGB_565
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
  vi.bits_per_pixel = 32
  vi.red.offset   =   0   .length =   8
  vi.green.offset =   8   .length =   8
  vi.blue.offset  =  16   .length =   8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
framebuffer: 0 (720 x 1280)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 1600
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 0.666667x and height 0.666667x, offsets x: 0 y: 0 w: 0 h: 0
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page splash
I:Switching packages (splash)
=> Linking mtab
=> Processing /etc/recovery.fstab for SAR-detection
I:Reading /etc/recovery.fstab
I:Done processing fstab files
I:SAR-DETECT: SAR System detected
=> Processing /etc/recovery.fstab
I:Reading /etc/recovery.fstab
I:Processing '/boot'
I:Processing '/system'
I:Created '/system_root' folder.
I:Processing '/system_image'
I:Processing '/vendor'
I:Processing '/vendor_image'
I:Processing '/oem'
I:Processing '/cache'
I:Processing '/data'
I:FBE contents 'ice', filenames ''
I:Processing '/recovery'
I:Processing '/dsp'
I:Created '/dsp' folder.
I:Processing '/misc'
I:Processing '/firmware'
I:Processing '/bt_firmware'
I:Created '/bt_firmware' folder.
I:Processing '/efs1'
I:Processing '/efs2'
I:Processing '/mnt/vendor/persist'
I:Created '/mnt/vendor/persist' folder.
I:Processing '/sdcard1'
I:Created '/sdcard1' folder.
I:Processing '/usb-otg'
I:Created '/usb-otg' folder.
I:Done processing fstab files
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:File Based Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using Keymaster HAL: 3 from QTI for encryption.  Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@3.0::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/unencrypted/key
Key upgraded in memory but not updated in folder: /data/unencrypted/key
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
Added key 212974880 (ext4:7e2c2ec01f8f350c) to keyring 41419702 in process 590
Added key 144230274 (f2fs:7e2c2ec01f8f350c) to keyring 41419702 in process 590
Added key 232568469 (fscrypt:7e2c2ec01f8f350c) to keyring 41419702 in process 590
contents mode 'ice' filenames 'aes-256-heh'
Wrote system DE key reference to:/data/unencrypted/ref
e4crypt_init_user0
Preparing: /data/misc/vold/user_keys
Preparing: /data/misc/vold/user_keys/ce
Preparing: /data/misc/vold/user_keys/de
Skipping non-de-key ..
Skipping non-de-key .
Using Keymaster HAL: 3 from QTI for encryption.  Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@3.0::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/misc/vold/user_keys/de/0
Key upgraded in memory but not updated in folder: /data/misc/vold/user_keys/de/0
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
Added key 963511470 (ext4:1f22a164457530fa) to keyring 41419702 in process 590
Added key 866500849 (f2fs:1f22a164457530fa) to keyring 41419702 in process 590
Added key 400409343 (fscrypt:1f22a164457530fa) to keyring 41419702 in process 590
Installed de key for user 0
Using synthetic password method
Handle is '0c2d2ce4f11d9576'
I:PageManager::LoadFileToBuffer loading filename: '/data/system/users/0.xml' directly
Using synthetic password method
Handle is '0c2d2ce4f11d9576'
I:User 0 is not decrypted.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/BH9086U09E'
I:Settings storage is '/data/media/0'
Updating partition details...
I:Data backup size is 16518MB, free: 1410MB.
I:Unable to mount '/sdcard1'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
I:Unmounting main partitions...
Partition Logs:

/boot | /dev/block/bootdevice/by-name/boot | Size: 64MB

Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img SlotSelect

Primary_Block_Device: /dev/block/bootdevice/by-name/boot

Display_Name: Boot

Storage_Name: boot

Backup_Path: /boot

Backup_Name: boot

Backup_Display_Name: Boot

Storage_Path: /boot

Current_File_System: emmc

Fstab_File_System: emmc

Backup_Method: dd
/system_root | /dev/block/bootdevice/by-name/system | Size: 4921MB Used: 2569MB Free: 2352MB Backup Size: 2569MB

Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent SlotSelect Mount_Read_Only

Primary_Block_Device: /dev/block/bootdevice/by-name/system

Display_Name: System

Storage_Name: System

Backup_Path: /system_root

Backup_Name: system

Backup_Display_Name: System

Storage_Path: /system_root

Current_File_System: ext4

Fstab_File_System: ext4

Backup_Method: files
/system_image | /dev/block/bootdevice/by-name/system | Size: 5000MB

Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img SlotSelect

Primary_Block_Device: /dev/block/bootdevice/by-name/system

Display_Name: System Image

Storage_Name: system_image

Backup_Path: /system_image

Backup_Name: system_image

Backup_Display_Name: System Image

Storage_Path: /system_image

Current_File_System: emmc

Fstab_File_System: emmc

Backup_Method: dd
/vendor | /dev/block/bootdevice/by-name/vendor | Size: 1511MB Used: 384MB Free: 1127MB Backup Size: 384MB

Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up IsPresent SlotSelect Mount_Read_Only

Primary_Block_Device: /dev/block/bootdevice/by-name/vendor

Display_Name: Vendor

Storage_Name: Vendor

Backup_Path: /vendor

Backup_Name: vendor

Backup_Display_Name: Vendor

Storage_Path: /vendor

Current_File_System: ext4

Fstab_File_System: ext4

Backup_Method: files
/vendor_image | /dev/block/bootdevice/by-name/vendor | Size: 1536MB

Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img SlotSelect

Primary_Block_Device: /dev/block/bootdevice/by-name/vendor

Display_Name: Vendor Image

Storage_Name: vendor_image

Backup_Path: /vendor_image

Backup_Name: vendor_image

Backup_Display_Name: Vendor Image

Storage_Path: /vendor_image

Current_File_System: emmc

Fstab_File_System: emmc

Backup_Method: dd
/oem | /dev/block/bootdevice/by-name/oem | Size: 371MB Used: 70MB Free: 300MB Backup Size: 70MB

Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up IsPresent

Primary_Block_Device: /dev/block/bootdevice/by-name/oem

Display_Name: OEM

Storage_Name: OEM

Backup_Path: /oem

Backup_Name: oem

Backup_Display_Name: OEM

Storage_Path: /oem

Current_File_System: ext4

Fstab_File_System: ext4

Backup_Method: files
/cache | /dev/block/bootdevice/by-name/cache | Size: 352MB Used: 0MB Free: 351MB Backup Size: 0MB

Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent

Primary_Block_Device: /dev/block/bootdevice/by-name/cache

Display_Name: Cache

Storage_Name: Cache

Backup_Path: /cache

Backup_Name: cache

Backup_Display_Name: Cache

Storage_Path: /cache

Current_File_System: ext4

Fstab_File_System: ext4

Backup_Method: files
/data | /dev/block/bootdevice/by-name/userdata | Size: 22169MB Used: 16518MB Free: 1410MB Backup Size: 16518MB

Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage

Symlink_Path: /data/media/0

Symlink_Mount_Point: /sdcard

Primary_Block_Device: /dev/block/bootdevice/by-name/userdata

Display_Name: Data

Storage_Name: Internal Storage

Backup_Path: /data

Backup_Name: data

Backup_Display_Name: Data

Storage_Path: /data/media/0

Current_File_System: ext4

Fstab_File_System: ext4

Backup_Method: files

MTP_Storage_ID: 65537
/recovery | /dev/block/bootdevice/by-name/FOTAKernel | Size: 64MB

Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img

Primary_Block_Device: /dev/block/bootdevice/by-name/FOTAKernel

Display_Name: FOTAKernel

Storage_Name: FOTAKernel

Backup_Path: /recovery

Backup_Name: recovery

Backup_Display_Name: FOTAKernel

Storage_Path: /recovery

Current_File_System: emmc

Fstab_File_System: emmc

Backup_Method: dd
/dsp | /dev/block/bootdevice/by-name/dsp | Size: 11MB Used: 10MB Free: 1MB Backup Size: 10MB

Flags: Can_Be_Mounted Can_Be_Wiped IsPresent

Primary_Block_Device: /dev/block/bootdevice/by-name/dsp

Display_Name: dsp

Storage_Name: dsp

Backup_Path: /dsp

Backup_Name: dsp

Backup_Display_Name: dsp

Storage_Path: /dsp

Current_File_System: ext4

Fstab_File_System: ext4

Backup_Method: files
/misc | /dev/block/bootdevice/by-name/misc | Size: 1MB

Flags: IsPresent

Primary_Block_Device: /dev/block/bootdevice/by-name/misc

Display_Name: misc

Storage_Name: misc

Backup_Path: /misc

Backup_Name: misc

Backup_Display_Name: misc

Storage_Path: /misc

Current_File_System: emmc

Fstab_File_System: emmc

Backup_Method: dd
/firmware | /dev/block/bootdevice/by-name/modem | Size: 109MB Used: 89MB Free: 20MB Backup Size: 89MB

Flags: Can_Be_Mounted Can_Be_Wiped IsPresent Mount_To_Decrypt Mount_Read_Only

Primary_Block_Device: /dev/block/bootdevice/by-name/modem

Display_Name: Firmware

Storage_Name: Firmware

Backup_Path: /firmware

Backup_Name: firmware

Backup_Display_Name: Firmware

Storage_Path: /firmware

Current_File_System: vfat

Fstab_File_System: vfat

Backup_Method: files

Mount_Flags: 0, Mount_Options: context=u:object_r:firmware_file:s0
/bt_firmware | /dev/block/bootdevice/by-name/bluetooth | Size: 63MB Used: 0MB Free: 63MB Backup Size: 0MB

Flags: Can_Be_Mounted Can_Be_Wiped IsPresent Mount_To_Decrypt Mount_Read_Only

Primary_Block_Device: /dev/block/bootdevice/by-name/bluetooth

Display_Name: BT Firmware

Storage_Name: BT Firmware

Backup_Path: /bt_firmware

Backup_Name: bt_firmware

Backup_Display_Name: BT Firmware

Storage_Path: /bt_firmware

Current_File_System: vfat

Fstab_File_System: vfat

Backup_Method: files

Mount_Flags: 0, Mount_Options: context=u:object_r:firmware_file:s0
/efs1 | /dev/block/bootdevice/by-name/modemst1 | Size: 2MB

Flags: Can_Be_Backed_Up Has_SubPartition IsPresent

Primary_Block_Device: /dev/block/bootdevice/by-name/modemst1

Display_Name: EFS

Storage_Name: EFS

Backup_Path: /efs1

Backup_Name: efs1

Backup_Display_Name: EFS

Storage_Path: /efs1

Current_File_System: emmc

Fstab_File_System: emmc

Backup_Method: dd
/efs2 | /dev/block/bootdevice/by-name/modemst2 | Size: 2MB

Flags: Can_Be_Backed_Up Is_SubPartition IsPresent

SubPartition_Of: /efs1

Primary_Block_Device: /dev/block/bootdevice/by-name/modemst2

Display_Name: efs2

Storage_Name: efs2

Backup_Path: /efs2

Backup_Name: efs2

Backup_Display_Name: efs2

Storage_Path: /efs2

Current_File_System: emmc

Fstab_File_System: emmc

Backup_Method: dd
/mnt/vendor/persist | /dev/block/bootdevice/by-name/persist | Size: 27MB Used: 0MB Free: 26MB Backup Size: 0MB

Flags: Can_Be_Mounted Can_Be_Wiped IsPresent

Primary_Block_Device: /dev/block/bootdevice/by-name/persist

Display_Name: mnt/vendor/persist

Storage_Name: mnt/vendor/persist

Backup_Path: /mnt/vendor/persist

Backup_Name: mnt/vendor/persist

Backup_Display_Name: mnt/vendor/persist

Storage_Path: /mnt/vendor/persist

Current_File_System: ext4

Fstab_File_System: ext4

Backup_Method: files
/sdcard1 |  | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB

Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage

Primary_Block_Device: /dev/block/mmcblk0p1

Alternate_Block_Device: /dev/block/mmcblk0

Display_Name: Micro SDcard

Storage_Name: Micro SDcard

Backup_Path: /sdcard1

Backup_Name: sdcard1

Backup_Display_Name: Micro SDcard

Storage_Path: /sdcard1

Current_File_System: auto

Fstab_File_System: auto

Backup_Method: files

MTP_Storage_ID: 65538
/usb-otg |  | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB

Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage

Primary_Block_Device: /dev/block/sdg1

Alternate_Block_Device: /dev/block/sdg

Display_Name: USB OTG

Storage_Name: USB OTG

Backup_Path: /usb-otg

Backup_Name: usb-otg

Backup_Display_Name: USB OTG

Storage_Path: /usb-otg

Current_File_System: auto

Fstab_File_System: auto

Backup_Method: files

MTP_Storage_ID: 65539
I:Loading package: TWRP (/twres/ui.xml)

I:Load XML directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/zh_TW.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/zh_CN.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/uk.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/tr.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sv.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sl.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sk.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/ru.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pt_PT.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pt_BR.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pl.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/nl.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/ja.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/it.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/hu.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/fr.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/es.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/el.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/de.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/cz.xml' directly

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly

parsing languageFile

parsing languageFile done

I:PageManager::LoadFileToBuffer loading filename: '/twres/ui.xml' directly

I:Checking resolution...

I:Scaling theme width 0.666667x and height 0.666667x, offsets x: 0 y: 0 w: 0 h: 0

I:Loading resources...

I:Failed to load image from indeterminate013, error -1

I:Loading variables...

I:Loading mouse cursor...

I:Loading pages...

I:Including file: /twres/portrait.xml...

I:PageManager::LoadFileToBuffer loading filename: '/twres/portrait.xml' directly

I:Loading resources...

I:Loading variables...

I:Loading mouse cursor...

I:Loading pages...

I:Loading page main

I:Loading page main2

I:Loading page install

I:Loading page flash_confirm

I:Loading page flash_zip

I:Loading page flash_done

I:Loading page flash_sleep_and_reboot

I:Loading page flashimage_confirm

I:Loading page clear_vars

I:Loading page reboot_system_routine

I:Loading page confirm_action

I:Loading page action_page

I:Loading page singleaction_page

I:Loading page action_complete

I:Loading page filecheck

I:Loading page rebootcheck

I:Loading page wipe

I:Loading page advancedwipe

I:Loading page formatdata

I:Loading page formatdata_confirm

I:Loading page checkpartitionlist

I:Loading page partitionoptions

I:Loading page refreshfilesystem

I:Loading page selectfilesystem

I:Loading page backup

I:Loading page multiuser_warning

I:Loading page backup_options

I:Loading page backupname1

I:Loading page backupname2

I:Loading page backupencryption

I:Loading page backupencryption2

I:Loading page checkbackuppassword

I:Loading page backup_run

I:Loading page restore

I:Unable to open '/data/media/0/TWRP/BACKUPS/BH9086U09E'

I:Loading page restore_read

I:Loading page restore_decrypt

I:Loading page try_restore_decrypt

I:Loading page restore_select

I:Loading page renamebackup

I:Loading page restore_run

I:Loading page mount

I:Loading page usb_mount

I:Loading page usb_umount

I:Loading page system_readonly_check

I:Loading page reboot

I:Loading page reboot2

I:Loading page installapp

I:Loading page system_readonly

I:Loading page settings

I:Loading page settings_timezone

I:Loading page settings_screen

I:Loading page settings_vibration

I:Loading page settings_language

I:Loading page copylog

I:Loading page advanced

I:Loading page partsdcardsel

I:Loading page partsdcardcheck

I:Loading page partsdcard

I:Loading page htcdumlock

I:Loading page repackselect

I:Loading page repackconfirm

I:Loading page lock

I:Loading page filemanagerlist

I:Loading page filemanageroptions

I:Loading page choosedestinationfolder

I:Loading page filemanagerrenamefile

I:Loading page filemanagerrenamefolder

I:Loading page filemanagerchmod

I:Loading page filemanagerconfirm

I:Loading page filemanageraction

I:Loading page decrypt

I:Loading page decrypt_pattern

I:Loading page trydecrypt

I:Loading page terminalcommand

I:Loading page sideload

I:Loading page fixcontexts

I:Loading page slideout

I:Loading page select_storage

I:Loading page select_language

I:Loading page decrypt_users

I:Loading page changeTwrpFolder

I:Switching packages (TWRP)

Startup Commands:

ro.boottime.adbd=3262839855

ro.boottime.init=2880

ro.boottime.init.selinux=42

ro.boottime.init.cold_boot_wait=294

ro.boottime.logd=3240154123

ro.boottime.ueventd=2936342947

ro.boottime.recovery=3243357353

ro.boottime.keymaster-3-0=3285673711

ro.boottime.sbin_qseecomd=3263326365

ro.boottime.gatekeeper-1-0=3285201524

ro.boottime.servicemanager=3263773240

ro.boottime.set_permissive=3242896311

ro.boottime.hwservicemanager=3234879123

dalvik.vm.isa.arm.variant=generic

dalvik.vm.isa.arm.features=default

dalvik.vm.isa.arm64.variant=generic

dalvik.vm.isa.arm64.features=default

dalvik.vm.lockprof.threshold=500

dalvik.vm.stack-trace-dir=/data/anr

dalvik.vm.image-dex2oat-filter=verify-at-runtime

debug.atrace.tags.enableflags=0

ro.art.hiddenapi.warning=1

ro.boot.selinux=permissive

ro.boot.baseband=msm

ro.boot.configfs=true

ro.boot.hardware=lilac

ro.boot.keymaster=1

ro.boot.bootdevice=1da4000.ufshc

ro.boot.bootloader=xboot

ro.boot.veritymode=enforcing

ro.boot.usbcontroller=a800000.dwc3

ro.boot.verifiedbootstate=orange

ro.omni.device=lilac

ro.omni.version.security_patch=

ro.twrp.sar=true

ro.twrp.boot=1

ro.twrp.version=3.5.2_9-0

ro.vndk.lite=true

ro.vndk.version=28

ro.wifi.channels=

ro.allow.mock.location=1

ro.build.id=PQ3B.190801.002

ro.build.date=Sun Apr 11 20:36:45 UTC 2021

ro.build.date.utc=1618173405

ro.build.host=93f70f4836da

ro.build.tags=test-keys

ro.build.type=eng

ro.build.user=jenkins

ro.build.flavor=omni_lilac-eng

ro.build.display.id=omni_lilac-eng 16.1.0 PQ3B.190801.002 1 test-keys

ro.build.product=lilac

ro.build.version.sdk=28

ro.build.version.base_os=

ro.build.version.release=16.1.0

ro.build.version.codename=REL

ro.build.version.incremental=1

ro.build.version.preview_sdk=0

ro.build.version.all_codenames=REL

ro.build.version.security_patch=2025-12-31

ro.build.version.min_supported_target_sdk=17

ro.build.description=G8441-user 9 47.2.A.11.228 3311891731 release-keys

ro.build.characteristics=default

ro.bionic.ld.warning=1

ro.kernel.android.checkjni=1

ro.secure=0

ro.treble.enabled=false

ro.product.cpu.abi=arm64-v8a

ro.product.cpu.abilist=armeabi-v7a,armeabi

ro.product.cpu.abilist32=armeabi-v7a,armeabi

ro.product.cpu.abilist64=

ro.product.name=lilac

ro.product.brand=Sony

ro.product.model=G8441

ro.product.device=lilac

ro.product.manufacturer=Sony

ro.baseband=msm

ro.bootmode=unknown

ro.hardware=lilac

ro.revision=0

ro.bootimage.build.date=Sun Apr 11 20:36:45 UTC 2021

ro.bootimage.build.date.utc=1618173405

ro.bootimage.build.fingerprint=Sony/G8441/G8441:9/47.2.A.11.228/3311891731:user/release-keys

ro.bootloader=xboot

ro.debuggable=1

ro.property_service.version=2

ro.actionable_compatible_property.enabled=false

fbe.contents=ice

fbe.filenames=

init.svc.adbd=running

init.svc.logd=running

init.svc.ueventd=running

init.svc.recovery=running

init.svc.keymaster-3-0=running

init.svc.sbin_qseecomd=running

init.svc.gatekeeper-1-0=running

init.svc.servicemanager=running

init.svc.set_permissive=stopped

init.svc.hwservicemanager=running

twrp.user.0.decrypt=0

twrp.crash_counter=0

crypto.ready=1

sys.usb.ffs.ready=1

ro.build.fingerprint=Sony/G8441/G8441:9/47.2.A.11.228/3311891731:user/release-keys

hwservicemanager.ready=true

ro.persistent_properties.ready=true

ro.boot.serialno=BH9086U09E

ro.serialno=BH9086U09E

service.adb.root=1

net.bt.name=Android

sys.usb.state=adb

sys.usb.controller=a800000.dwc3

persist.sys.usb.config=adb

persist.sys.dalvik.vm.lib.2=libart.so

sys.usb.config=adb

sys.usb.configfs=1

ro.vendor.usb.pid_suffix=1F4

vendor.sys.listeners.registered=true

vendor.usb.rmnet.func.name=rmnet_bam

vendor.usb.rndis.func.name=rndis_bam

ro.crypto.type=file

ro.crypto.state=encrypted
I:Is encrypted, do decrypt page first

I:Switching packages (TWRP)

I:Set page: 'decrypt'

I:Set page: 'main'

I:Set page: 'clear_vars'

I:Set page: 'main2'

I:Set page: 'install'

I:Set page: 'main'

I:Set page: 'clear_vars'

I:Set page: 'main2'

SELinux contexts loaded from /file_contexts

Full SELinux support is present.

I:Switching packages (TWRP)

I:TWFunc::Fixup_Time: Pre-fix date and time: 1972-11-13--05-17-29

I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch

I:TWFunc::Fixup_Time: will attempt to use the ats files now.

I:TWFunc::Fixup_Time: Setting time offset from file /data/vendor/time/ats_2, offset 1552783865350

I:TWFunc::Fixup_Time: Date and time corrected: 2022-01-27--06-08-34

I:Path /cache/recovery/log.gz does not exist. Unable to copy /cache/recovery/last_log.gz

I:Attempt to load settings from settings file...

I:InfoManager file '/data/media/0/TWRP/.twrps' not found.

I:Backup folder set to '/data/media/0/TWRP/BACKUPS/BH9086U09E'

I:Copied file /etc/recovery.fstab to /cache/recovery/recovery.fstab

I:Version number saved to '/cache/recovery/.version'

I:Unable to mount '/sdcard1'

I:Actual block device: '', current file system: 'auto'

I:Unable to mount '/usb-otg'

I:Actual block device: '', current file system: 'auto'

I:TWFunc::Set_Brightness: Setting brightness control to 1600

I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly

parsing languageFile

parsing languageFile done

I:Translating partition display names

I:Backup folder set to '/data/media/0/TWRP/BACKUPS/BH9086U09E'

I:Switching packages (TWRP)

I:Set page: 'system_readonly'

I would assume that the different maximum up/dl speed are a result of different LTE implementations. LTE exists in quite a few versions with different capabilities regarding the maximum transmission speed and how many channels can be aggregated.

For example the value DL/UL as 102400/51200 seems to be LTE Cat 3 (100 Mbit/s down, 50 Mbit/s up).

My guess is that you can't change it because the value depends on the used LTE hardware in the phone (and of course the used mobile network).

Last but not least some data plans limit the maximum download/upload speed. The values shown by your Realme 8 30MBit down and 15MBit/s to not correspond to an LTE category. The next matching one would be LTE Cat 2 with 50 Mbit/s down and 25 Mbit/s up. So most likely this is a limitation of the used data plan or the phone shows the effective transmission speed which is limited by the signal strength.

Conclusion: No you can't change the values via adb as this is either a hardware limitation by your phone, the mobile network or of your data plan.

You can simply copy the adb private adb public key file to a new computer or a different user profile:

# Windows
%USERPROFILE%\.android\adbkey
%USERPROFILE%\.android\adbkey.pub
Linux/MacOS
~/.android/adbkey

~/.android/adbkey.pub

Afterwards you may have to restart the local adb server if it is running. You can do so executing adb kill-server. Afterwards the new adb keys should be used and you can open adb connection to your phone.

there is isn't a direct way doing that. unfortunately Google voice to text translation is terribly biased. it offers various accents for English but it will not translate anything perfectly and errors remain.

so how do you force corrections that come from bad voice to text translation ?
from settings go to dictionary & add Franck and make Frank the shortcut. I believe this is the closest you can come to what you you want to achieve

I found https://play.google.com/store/apps/details?id=com.omarbs.bluesched&hl=en_US&gl=US that seems to do what you need. It's description:

Bluetooth Scheduler offers you the posibility to turn On and turn Off bluetooth module in different moments of the day, and/or through the week with day independent configurations, making you to save battery charge.

There is 2 different modes (1 active each time):

Simple mode: Lets you make schedules independent of the day, that should apply everyday.

Weekly mode: Lets you easily configure schedules for each day of the week.

I didn't find a way to do it without an app (a native way). However, if you didn't like this app and you are a developer, https://developer.android.com/guide/topics/connectivity/bluetooth/setup and build yourself your app for that.

I'm not an Android developer, I am a developer in many other contexts.

I have a simple question that I don't see an answer to on Google: Can a standard android application (no rooting required) listen to a socket on a high numbered port? E.e. only using standard in-app permissions?

Any reference to the documentation on the available permissions would be a nice addition for this weekend warrior Android coder to-be.

I want to use rclone-mount on Android to mount remote directories from my own server as well as from pCloud. I want the mount points to be established automatically at boot time and to remain mounted full time.

I have not been able to install Magisk on this device yet. See https://android.stackexchange.com/questions/242322/how-to-install-magisk-without-an-unlocked-bootloader

I tried the following rclone-mount method with Termux:

https://android.stackexchange.com/questions/225604/how-to-mount-rclone-on-android

Unfortunately, that results in permissions errors that I have not been able to solve. I posted a question about it here:

https://android.stackexchange.com/questions/242247/how-to-use-rclone-mount-with-termuxboot

That remains unresolved. I have worked on this for many hours, so I could add more info to my other question if needed. However, with the assistance of @alecxs I tried another approach and resolved the permission errors. Now rclone can now successfully mount both pcloud and my own server when I run the commands at the CLI.

My current question is, how to automate this without Termux:Boot or Magisk? II can't install Magisk and Termux gave me tons of trouble for a couple weeks and I only got this working by ditching Termux. Again, see the above question if you think you know the reason for the Termux problems.)

---

For background, and to possibly help others, I am listing all my steps so far since the commands are working and this might prove to be a useful supplement for https://android.stackexchange.com/users/218526/irfan-latif 's great answer that helped me get started with rclone-mount on Android.

• removed Termux (& verified all files are gone)
• removed Magisk app (the module was never installed)
• kept original SuperSU v2.82 (& verified it doesn't have trackers)
• gave network access permissions to apps running under root in AFWall+
• used "Simple SSHD" app (from F-Droid) to access device via SSH (from my PC)
• I have a working rclone.conf file already
• my env var LD_LIBRARY_PATH is empty and I did not have to modify it with this method
• my device is Arm64
• echo $PATH = /sbin:/system/sbin:/system/bin:/system/xbin and I put the binaries into /system/bin EDIT: @alecxs pointed out that these custom binaries should have been installed to /system/xbin.

---

First, I put the binaries into the correct directories on my Android device:

cd /path/to/files/gocryptfs_fusermount-ARMHF_2021-01-13/

NOTE: the fusermount binary comes from XDA / mirfatif: https://forum.xda-developers.com/m/mirfatif.7805402/ https://forum.xda-developers.com/t/fusermount-on-android-rclone-mount.3866652/page-2#post-80237591

$ scp -P 2222 fusermount 192.168.1.123:~/

On Android, become superuser:

su

install fusermount binary:

mount -o rw,remount /system
mv /system/bin/fusermount /system/bin/fusermount.termux
cp ./fusermount /system/bin/fusermount
chmod 775 /system/bin/rclone
chown system:shell /system/bin/fusermount

check SELinux context and DAC permissions:

# ls -laZ /system/bin/fusermount
-rwxrwxr-x 1 system shell u:object_r:system_file:s0 114056 2021-10-25 01:29 /system/bin/fusermount

Install the official rclone binary: NOTE: The rclone binary I'm using is from: https://beta.rclone.org/test/testbuilds-latest/rclone-android-21-armv8a.gz

I have it on my phone at: /storage/emulated/0/Documents/rclone-android-21-armv8a

mount -o rw,remount /system
ls -la /system/bin/rclone
lrwxrwxrwx 1 system shell 42 2021-10-21 19:55 /system/bin/rclone -> /data/data/com.termux/files/usr/bin/rclone
rm /system/bin/rclone
cp /storage/emulated/0/Documents/rclone-android-21-armv8a /system/bin/rclone
chmod 775 /system/bin/rclone
chown system:shell /system/bin/rclone
ls -laZ /system/bin/rclone
-rwxrwxr-x 1 system shell u:object_r:system_file:s0 62257128 2021-10-26 19:45 /system/bin/rclone

Optional (if needed, restore SELinux context -- I did not need to do this):

restorecon -F /system/bin/rclone
restorecon -F /system/bin/fusermount

Finished, so mount readonly again:

mount -o ro,remount /system

Check the mount namespace:

# readlink /proc/1/ns/mnt
mnt:[4026531840]
# readlink /proc/self/ns/mnt
mnt:[4026531840]

If they don't match, run the command below. (Mine match)

nsenter -t 1 -m -- "$0"

Verify the remote is not already mounted:

# ls -la /mnt/runtime/write/emulated/0/mypcloud/

Set env var for rclone config:

export RCLONE_CONFIG=/data/data/org.galexander.sshd/files/rclone.conf

Now manually mount remote using rclone:

rclone -vvv mount mypcloud: /mnt/runtime/write/emulated/0/mypcloud --gid 9997 --dir-perms 0771 --file-perms 0660 --umask=0 --allow-other --cache-dir /storage/emulated/0/.cache --vfs-cache-mode full --vfs-cache-max-age 2h0m0s --vfs-cache-poll-interval 5m0s

Success!

to umount:

fusermount -u /mnt/runtime/write/emulated/0/mypcloud

There is really nothing new in the steps above that https://android.stackexchange.com/users/218526/irfan-latif didn't already discuss. However, there are differences. For example, I did not need to set LD_LIBRARY_PATH. Also, rclone emits this warning:

WARNING: linker: /system/bin/rclone: unsupported flags DT_FLAGS_1=0x8000001

However, that doesn't appear to be a problem. I also show more info about SELinux contexts and a few other things. There are enough differences from the existing answer that my steps might help someone else with their own troubleshooting.

---

Now, my main question how can I automate this at boot time without Termux:Boot or Magisk? I guess I could put a script into init somewhere, but I would appreciate an expert answer. I have reviewed a lot of answers about init.rc and executing scripts at boot. They have mostly sent me to solutions that were obsolete by Android 4.x and they also do not deal with the question of how to handle the case of booting up when a network connection is not available.

EDIT: @alecxs contributed the following idea for booting up when a network connection is not available:

until dumpsys connectivity | grep -iq state..connected
do
    sleep 1
done && rclone  & 

My device is running Android 7.0 (US Samsung Galaxy S8). It is rooted, I have true root, it has SuperSu 2.82, SELinux is permissive, and I can remount /system rw (as shown above). I do have the /system/su.d/ directory.

Also, related question, where is a good / safe location (path) on my Android device to keep my pcloud token and my private ssh key (for the remote SFTP server)?

As you can see in the attachment, i have denied access to microphone. But when I go to "All Permissions", it shows that the app can still use microphone. What does that mean? And how can I stop it from using my microphone?

I want to keep the sound output on the phone, the earpiece or the loudspeaker as it is normally when I connect an external microphone. It's detected as a headset so they're disabled as well as the microphone.

My internal microphone is dead, and I want to use this small jack microphone I have.

Is there an obscure setting, working app, or adb command for this?

I tried a few apps, but none of them worked. "Lesser AudioSwitch" got the closest. The microphone works so does the phone speakers, EXCEPT when I start a phone call, then the microphone input stops working and I'm not heard by the person I called. Which would be the main reason to use the microphone...

On my Play Store-included Chinese Android phone (Xiaomi Poco X3 NFC), I recently encountered an issue where I had to re-accept permissions for all of my apps. My VPN app failed, and I began getting errors that the phone itself was preventing me from connecting to a VPN. I tried clearing the cache, the files, re-installing the app, using new VPN client and configuration files, restarting the phone, etc. None of this helped.