How can I obtain a link (a URL) to a specific email (or the entire thread, if necessary) in the Gmail Android app? I want to be able to click that link and open the specific email.

It's depends of set of rules which was used for analysis. First of all please ensure yourself is it a CERT-C, MISRA or e.g CWEC

Testing mission:

I want to test the correct data is represented on UI

The target system is the UI, so, you have to explore two aspects:

1 - Does my UI integrate correctly with the service(s)? 2 - Given that (1) holds, is the UI displaying the data correctly?

(1) can be tackled with https://pactflow.io/blog/what-is-contract-testing/ . In (2), you should have control over the inputs of your system (the UI), thus you can explore the data provided by the service(s) - this control comes from using test doubles, like mocks. Their acceptance tests and API documentation (e.g. OpenAPI) can be good source of ideas for what the services can provide.

I am using a One Plus 9R and somehow I cannot see the call history for callers.

In all my past Android phones I used to be able to get a list of past call times and durations etc by clicking on a particular caller name.

Any idea what could be wrong? I seem to be having the "Phone by Google" app installed and presumably that's my dialer.

I tried clearing the cache for that app. Anything else I should be trying?

You can use Servers Ultimate (com.icecoldapps.serversultimate) from Ice Cold Apps to ran VPN Server on your Android device. But it has limitations:

• VNC Server: doesn’t work on most devices.
• ARM based: Caddy, VPN, Port forward, MySQL monitor, Nginx, Traceroute
• Root needed: Port forwarder, VNC, VPN, SMB Native
• Permission SMS: start/stop rules
• Permission coarse location: wifi selector tool

1. download and extract ROM from https://www.xda-developers.com/samloader-download-updates-samsung-galaxy

   cd /media/xubuntu/1234567890ABCDEF
   sudo apt update
   sudo apt install android-sdk-ext4-utils android-sdk-libsparse-utils android-sdk-platform-tools-common android-tools-adb android-tools-fastboot f2fs-tools git python3.8 python3-pip
   git clone https://github.com/nlscc/samloader
   cd samloader
   
   pip3 install .
   
   cd ..
   
   sudo cp -av ~/.local/bin/samloader /usr/local/bin
   mkdir Android
   
   cd Android
   samloader -m SM-G531F -r SLK checkupdate
   
   samloader -m SM-G531F -r SLK download -v G531FDDU1APJ2/G531FODD1APJ2/G531FDDU1APJ2/G531FDDU1APJ2 -O .
   
   samloader -m SM-G531F -r SLK decrypt -v G531FDDU1APJ2/G531FODD1APJ2/G531FDDU1APJ2/G531FDDU1APJ2 -V 4 -i SM-G531F_1_20161116150254_w0xdzpk60j_fac.zip.enc4 -o SM-G531F_1_20161116150254_w0xdzpk60j_fac.zip
   unzip SM-G531F*.zip
   
   tar -vxf AP_G531F*.tar*
   
   

2. convert https://github.com/anestisb/android-simg2img into mountable disk image

   mv -v system.img system.sparse.img
   file system.sparse.img
   simg2img system.sparse.img system.img
   file system.img
   

   (optional) check if mountable

   mkdir system
   sudo mount -vo loop,ro,noexec,noload,noatime -t ext4 system.img system
   ls -a system
   sudo umount -v system
   

3. copy file to MicroSD Card

   adb push system.img /external_sd
   

   (optional) compare digest

   md5sum system.img
   adb shell md5sum /external_sd/system.img
   

4. write disk image from terminal dd

   adb shell
   find /dev/block -name by-name
   ls -l /dev/block/bootdevice/by-name/system
   dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system
   reboot recovery
   

5. disable dm-verity and recovery-from-boot.p (necessary for TWRP)

   adb disable-verity
   adb shell
   mount -w /system
   mv -v /system/recovery-from-boot.p /system/recovery-from-boot.bak
   

The issue got fixed, the issue was with the ROM. I had flashed a stock ROM from ASUS' website a month or so ago and due to that even factory resetting didn't help. I flashed a new Pixel Experience ROM on it by unlocking the bootloader and it fixed the issue. I'm now getting full speeds, 50 Mbps+

The main reason:

There is no revenue-generating stream for Linux on smartphones in comparison to Android.

Technical reasons, which can't be solved without heavy investments

Just porting Linux to SoC is not enough. Linux is only a kernel.

• You will need to develop a distro suitable for a smartphone.

• Android = 1. AOSP + 2. patches and blobs from SoC vendor + 3. user apps`

Patches and blobs from SoC vendor

#2 in the equation has restricted access. SoC vendors don't share internal details even with OEMs, only providing a minimum description for available APIs. Typical Android-capable SoC has a lot of proprietary peripheral modules (such as mentioned GPU or Audio, Image processing, radio modules). Some of them require OS drivers, others even specific complex FW with a separate OS. Even for some desktop peripherals, this factor blocks Linux support.

Existing attempts

There were attempts to develop an open-source smartphone. As we can see, they didn't get widespread till the moment, and some of the projects were discontinued. The main reason is the same: the model didn't prove its sustainability.

I have https://play.google.com/store/apps/details?id=com.appstar.callrecorderpro&hl=en&gl=US installed and it is recording phone calls, which I can see in the application. I would like to see these files in filesystem too. Where are they?

I see location Internal storage/CallRecordings, but it contains only few very old recordings, no any new ones.

I installed:

• the latest platform tools from google
• the universal adb driver
• the OnePlus USB driver

USB debugging & OEM unlock are on.

With the phone turned on everything runs fine. I can copy files onto the device and it shows up in adb and the device manager just fine.

But when I go into the bootloader, fastboot does not list or recognize the device and I noticed in the Device-Manager the phone shows up like https://i.imgur.com/Y4s4EEv.png . Idk if this is normal or not, but I'm out of ideas.

Any help would be much appreciated.