uiautomator parser for Android
Tested against Bluestacks 5 / Python 3.11, directly in the terminal
pip install cyuiautomatordump
Cython and a C compiler must be installed!
You also need to compile https://github.com/opsengine/cpulimit
Gets a UI Automator dump, processes it, and returns the result as a DataFrame.
Parameters:
package (str): The package name.
memdisk_path (str): The path to the memory disk.
memdisk_size (int): The size of the memory disk in MB.
memdisk_su (str): The superuser command.
memdisk_sh (str): The shell command.
memdisk_try_all_rw_remount_combinations (bool): Whether to try all read-write remount combinations.
max_cpu_percentage_for_process (int): The maximum CPU usage percentage for the process.
sleep_after_starting_cpu_limiter (float): The sleep time after starting the CPU limiter.
add_screenshot (bool): Whether to add a screenshot to the DataFrame.
screen_width (int): The width of the screen.
screen_height (int): The height of the screen.
debug (bool): Whether to enable debug mode.
uiautomator_nice (int): The nice value for UI Automator.
uiautomator_sleep_between_retries (float): The sleep time between retries for UI Automator.
uiautomator_shell (bool): Whether to use the shell in the subprocess.
uiautomator_timeout (int): The timeout for UI Automator.
Yields:
pd.DataFrame: The processed UI Automator dump as a DataFrame.
from cytonuiautomatordump import get_cyuiautomator_dump
geni = get_cyuiautomator_dump(
package= "com.instagram.android",
memdisk_path="/media/ramdisk",
memdisk_size=256,
memdisk_su="su",
memdisk_sh="sh",
memdisk_try_all_rw_remount_combinations=False,
max_cpu_percentage_for_process=10,
sleep_after_starting_cpu_limiter=0.5,
add_screenshot=False,
screen_width=720,
screen_height=1280,
debug=False,
uiautomator_nice=-19,
uiautomator_sleep_between_retries=0.3,
uiautomator_shell=True,
uiautomator_timeout=20,
)
counter = 0
while True:
df = next(geni)
print(df)
counter = counter + 1
print(counter)
Metadata
Release files for cytonuiautomatordump 0.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cytonuiautomatordump-0.10.tar.gz | 26.8 kB | Without provenance | Details for cytonuiautomatordump-0.10.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cytonuiautomatordump-0.10-py3-none-any.whl | Python 3 | none | any | Details for cytonuiautomatordump-0.10-py3-none-any.whl |
Total release size: 54.5 kB
Release files / cytonuiautomatordump-0.10.tar.gz
| Download URL | cytonuiautomatordump-0.10.tar.gz |
|---|---|
| Size | 26.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e775d2b17c47382921184a1f4d9373b47ffc5d9f7c8f1c86ad55bb644fad5571
|
|
BLAKE2b-256 checksum How to use checksums |
44cf8049d2ec7067a80134e703db7ff425ffcd0a48e3c6389e3c33b7cd5dc830
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Release files / cytonuiautomatordump-0.10-py3-none-any.whl
| Download URL | cytonuiautomatordump-0.10-py3-none-any.whl |
|---|---|
| Size | 27.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
841cb82416e3e86bdf7c24a2b9a831968657c8b261b4d0e8fd0cd4a48d51d88e
|
|
BLAKE2b-256 checksum How to use checksums |
d30cb6da8ce2ed1d011563cdb8cce65d2114d451e79e3aa977863fbf18100eb9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Security for cytonuiautomatordump 0.10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.