Add UserScript and DevTools supports to Chromium based and WebView based browsers using Xposed framework.
We hook the onUpdateUrl
function in UserScript.kt,
add URL comparison there and evaluate JavaScript using the javascript:
scheme (or DevTools Protocol when possible).
Chromium based browsers, such as Egde, Bromite, Samsung Internet, and Brave, are fully supported.
Most WebView based browsers are also supported, if not, please report it. Note for WebView based browsers users: you only need to enable this module for the browser application you wish to use, not for any possible WebView applications, neither for the Android system.
ChromeXt requires Xposed framework.
For root users, install LSPosed first, pick up the latest built APK from my repo's GitHub Actions and install it.
For non-root users,
I modify a bit LSPatch to support ChromeXt
; here is how to use it:
lspatch-release
from my GitHub Actions.ChromeXt.apk
from my GitHub Actions.lspatch.jar
(with some suffix) and ChromeXt-signed.apk
.arm64_ChromePublic.apk
as example) using the following command: java -jar lspatch.jar arm64_ChromePublic.apk -d -v -m ChromeXt-signed.apk --force
. If java
environment is not available, please consider using the provided manager
APK.Notes: currently to download files from GitHub Actions
, one needs to log in GitHub.
The author uploads releases to Xposed-Modules-Repo when needed, but not that frequently.
You can then install UserScripts from popular sources: URLs that ends with .user.js
.
Currently, ChromeXt supports almost all Tampermonkey APIs:
Resources
panel of eruda), GM_unregisterMenuCommand, GM_download, unsafeWindow (= window)These APIs are implemented differently from the official ones, please refer to the source files Local.kt and GM.js if you have doubts or questions.
Moreover, there is the powerful (also dangerous) GM.ChromeXt
API, which must be declared by @grant GM.ChromeXt
to unlock its usage.
It is locked by default so that the users are protected from malicious UserScripts exploiting ChromeXt.
This API allows scripts to use the JavaScript method ChromeXt.dispatch(action, payload)
, which is fundamental to implement other APIs. (Hence, one can find usage examples in GM.js).
Dispatched action
and payload
are handled by Listener.kt.
To manage scripts installed by ChromeXt
, here are a simple front end hosted on github.io and two mirrors of it (in case that you have connection issues): onrender.com, netlify.app.
If you cancel the prompt of installing a new UserScript, then you can edit it directly in Chrome.
Use the Install UserScript
page menu to install your modified UserScript.
From the three dots page menu, ChromeXt offers you the
Developer tools
menu for the UserScript manager front end,Eruda console
menu for other pages.For Edge
browser, these menus are moved to the page info menu,
which locates at the left corner inside the URL input bar.
For WebView based browsers and Samsung Internet, these menu items are presented in the context menu.
Since WebView based browsers have no unified designs, the following first four features are not supported for them. (By the same reason, they are neither supported for Samsung Internet.)
The application ChromeXt
is able to
Google
,The reversed priority order of opening which Chromium based browsers is given in AndroidManifest.xml.
By default, the history forward gesture of Chrome is available near the vertical center of screen.
On other areas, only the system gesture is available.
One can disable this behavior through the Developer options
menu.
(Tap seven times on the Chrome version from the Chrome settings, you will see the Developer options
menu.)
(In Vivaldi browsers, Developer options
menu is removed by its developers.)
ChromeXt adds a book icon in the page menu to enable reader (distiller) mode manually.
Bookmarks can be exported in HTML format through the Developer options
menu.
For blocking network requests, I recommend to use AdAway
or any proxy AD Blocker such as clash
.
A content cosmetic blocker is embedded into ChromeXt with the help of eruda.
To use it, first open the Eruda console
.
In the Elements
panel, one can use the pointer
icon to select elements on the page.
After clicking the delete
icon for a selected element, a corresponding filter will be saved to the Resources
panel,
where one can manage previous added filters.
These filters are saved in the browser even after clearing the site's data.
Another way to block ADs is using the Content-Security-Policy to block some scripts from loading.
One can edit the User-Agent from the Info
panel of Eruda console
.
A valid User-Agent should contain only ASCII characters.
Currently, ChromeXt only changes the User-Agent
HTTP header, which
works well but is deprecated.
For Chromium based browsers, when the User-Agent spoofing is not taking effects, refresh the page using the reload button in the page menu. (By contrast, a swipe refresh might be insufficient.)
Note that the DevTools can also change User-Agent.
Before you submit your pull-requests, please ensure that the command
./gradlew build
or gradlew.bat build
produces no warnings and no errors.
Here are corresponding files you might want / need to change:
file
schemeOpen in Chrome
functionGM_info
adb forward
to support non-root usersGM_log
logsiframe
and local server to run general WebExtensionsstyle-src
rule for eruda
, such as Mastodon