ADB Application Manager Pro

Hidden Settings: every setting says what it does and which values it takes. Under each name the list shows a short description and a Values: line (for example 0 = off; 1 = priority interruptions only; 2 = total silence; 3 = alarms only), with the value the setting holds now in bold. The editor has an About box with the same, one value to a line and a Now: line that follows what you type; the documented values are buttons (2 · total silence). The app now knows about 1,100 settings of Android's Global, Secure and System tables (the common ones written out in plain words, the rest from Android's own documentation). A setting nobody describes gets a guess from its name and value (What it probably is: a switch, a time in milliseconds, an app's own setting, a Samsung one). A setting that takes more than on and off (wifi_on, zen_mode) is never flipped by a press and hold. The search also looks in the values text. A link, How to read this list, opens a short explanation of the three tables, a row and the kinds of value. Connected Devices > Hidden Settings shows the same text. The text is in assets/hsinfo.js, made by tools/hsinfo/build.py. Morphe Patcher: bundles are read again. Every bundle (the official Morphe Patches, Gboard and the others) showed "Could not be read" with KotlinReflectionInternalError: Unresolved class: class java.lang.String. The patcher reads the patches of a bundle with Kotlin reflection, which needs Kotlin's built-in metadata (kotlin/*.kotlin_builtins) and its service files at run time. The dex conversion had dropped them, and a computer's Java finds them on the class path, so only a phone failed. They are now part of the engine and of the APK (together with ARSCLib's framework files for resource patches), and build.sh refuses to build an engine without them. The same bundle that failed now lists 166 patches in the engine.

Write a review

• 

  Сергей Викторович 6d ago