A JavaScript runtime and development environment on the Android platform that supports accessibility services, and its development goals are similar to JsBox and Workflow.
Since the original author no longer maintains the Auto.js project,
I plan to continue the maintainer project on the original basis. This project will be transferred
from autojs The project is named Autox.js. What you are looking
at is the project based on the original version 4.1. Later, I will introduce how to develop and
run the project itself. More developers are welcome to participate in the maintenance and upgrade
of this project. The latest Autox.js Address, many original project
paths in the document, I do not intend to replace them if the original project is not deleted,
to show respect for the original author. The encryption-related content in this document may
conflict with the actual operation. If you want to write code encrypted to protect intellectual
property rights, please refer to the project https:github.comkkevsekk1webpack-autojs I will gradually
improve and update the program code, keep it as much as possible Consistent.
This project is obtained from hyb1996 autojs and named as Autox.js (autojs modified version). What you are looking at now is the project based on the original 4.1 version. Later we will discuss how the project itself The development and operation are introduced, and more developers are welcome to participate in the maintenance and upgrade of this project. Mozilla Public License Version 2.0 adopted by hyb1996 + non-commercial use, for various reasons, this product adopts GPL-V2 license, whether other contributors, or use of this product, must be used in accordance with the relevant requirements of MPL-2.0+ non-commercial use and GPL-V2.
About the two protocols:
- Autox.js Docs： http://doc.autoxjs.com/
- Open Source Address: https://github.com/kkevsekk1/AutoX
- PC Develop: VS Code Extension
- Official Forums：www.autoxjs.com
- autoxjsChangelog
https://github.com/kkevsekk1/AutoX/releases
- universal: Universal version (don't care about the size of the installation package, just use this version, including the following 2 CPU architectures so)
- armeabi-v7a: 32-bit ARM device (preferred for spare)
- arm64-v8a: 64-bit ARM device (mainstream flagship)
- Simple and easy-to-use automation functions implemented by accessibility services
- Floating window recording and running
- More professional & powerful selector API, providing search, traversal, information acquisition, operation, etc. on the controls on the screen. Similar to Google's UI testing framework UiAutomator, you can also use it as a mobile UI testing framework
- Using JavaScript as the scripting language, and supporting functions such as code completion, variable renaming, code formatting, search and replacement, etc., it can be used as a JavaScript IDE
- Supports the use of e 4 x to write the interface, and can package Java Script as apk file, you can use it to develop gadget applications
- Supports the use of root privileges to provide more powerful screen tap, swipe, record and run shell commands. Recording and recording can generate js files or binary files, and the playback of recorded actions is relatively smooth
- Provides functions such as taking screenshots, saving screenshots, finding colors in pictures, and finding pictures
- Can be used as a Tasker plugin, combined with Tasker for daily workflow
- With an interface analysis tool, similar to Android Studio's LayoutInspector, it can analyze the interface level and scope, and obtain the control information on the interface.
This software is different from software such as Button Wizard. The main differences are:
- Autox.js is mainly aimed at automation and workflow, and is more convenient for daily work, such as automatically blocking notifications when starting a game, one-click WeChat video with a specific contact (this problem has occurred on Zhihu, and it is difficult for the elderly to perform complex tasks.) operation and children for WeChat video), etc.
- Autox.js compatibility is better. Coordinate-based button sprites and script sprites are prone to resolution problems, while control-based Auto.js does not have this problem
- Autox.js does not require root privileges to perform most tasks. Only related functions that require precise coordinates to click and slide require root privileges
- Autox.js can provide functions such as interface writing, not only as a script software
- Official Forums： autojs.org
- Docs：Online documentation is here. Documentation is still incomplete at the moment.
- Example：Some examples can be viewed here, or viewed and run directly within the app.
To be added, but is anyone really interested in this? Welcome to contact me to communicate
This product is licensed under the GPL-V2 license
For historical reasons, the protocol of the Autojs Project has to be followed:
Based on the Mozilla Public License Version 2.0 with the following terms: Non-Commercial Use - The source code and binary products of this project and its derived projects may not be used for any commercial or for-profit use
No one in the original text states that the license is MPL2.0, and the newly added files or modified (only for repairing your own) code adopts GPL-V2, and relevant declarations are required.
// SPDX-License-Identifier: GPL-2.0
// Claim your copyright- If you use GPL-2.0 declared code or compiled binaries. You need to open source all your code.
- If you only use MPL-2.0 stuff, you need to open source the relevant code you modified.
- Open source does not mean free use, and open source does not mean prohibiting commercial use!
- Open source things can be commercialized, but you need to open source according to the regulations!
- Commercial products can be open source, such as redhat!
- If you do not use open source products according to the open source agreement, you can understand the source of openwrt and the domestic infringement cases in recent years!
- That is your freedom, not restricted by this agreement, just like linux runs software
- Whether this product can be used for commercial use depends on the original autojs, because many functions and codes are copyrighted by autojs.
- Whether autojs can be commercialized depends on your understanding of the accompanying "non-commercial use" and its legal benefits.
- Anyway, this product will not use autojs for commercial use.
Command description: Run the command in the project root directory, if using Windows powerShell < 7.0, use the command containing ";"
./gradlew inrt:assembleTemplateDebug && ./gradlew inrt:cp2APPDebug && ./gradlew app:assembleV6Debug && ./gradlew app:installV6Debug
#or
./gradlew inrt:assembleTemplateDebug ; ./gradlew inrt:cp2APPDebug ; ./gradlew app:assembleV6Debug ; ./gradlew app:installV6DebugThe generated debug version APK file is under app/build/outputs/apk/v6/debug with the default signature
./gradlew inrt:assembleTemplate && ./gradlew inrt:cp2APP && ./gradlew app:assembleV6
#or
./gradlew inrt:assembleTemplate ; ./gradlew inrt:cp2APP ; ./gradlew app:assembleV6The generated APK file is an unsigned APK file. Under app/build/outputs/apk/v6/release, it needs to be signed before it can be installed.
First run the following command:
./gradlew inrt:assembleTemplate && ./gradlew inrt:cp2APP
#or
./gradlew inrt:assembleTemplate ; ./gradlew inrt:cp2APPThen click the Android Studio Run button
First run the following command:
./gradlew inrt:assembleTemplate && ./gradlew inrt:cp2APP
#or
./gradlew inrt:assembleTemplate ; ./gradlew inrt:cp2APPThen click Android Studio menu "Build" -> "Generate Signed Bundle APK..." -> check "APK" -> "Next" -> select or create a new certificate -> "Next" -> select "v6Release" -> "Finish" Generated APK file, under app/v6/release