android:isSplitRequired, android:debuggable,
android:testOnly
. Recompilation requires the presence of aapt's binaries. The installation request appears when the app is first launched. If you have not done so, the download is done in "Settings" Build and Decompile "Replace Tools" Download for ... "
Base path: /system/framework/..
They can also be located in/system/vendor / framework, etc. in adjacent directories. If these directories exist (a rare occurrence).Then decompile and compile as a regular apk. To save the original META-INF and manifest – enable the "Match to original" radio button in the decompilation settings.
When building, debugging data is stored in Smali files, such as.line, .param
, and so on.
<application />
the attribute value in the manifest in the tag android:debuggable
to true
. Notifies the system that it is a debug application. Allows you to extend access to logging of this application. Interaction with the functionality of this function is possible only with the help of special tools (such as Android Studio, as well as debugging at the ADB level, etc.). This option does not apply to Logcat - the number of debug entries in the system log will not change if this parameter is changed. To specify such an application as the current one for debugging, select it in the "System Settings" For developers " Debugging Application "(the paths may differ).
This question needs to be clarified.
By default, the resource IDs inside resources.arsc are set in arithmetic progression. In some cases, it may be broken – some places inside the value types may not be filled in (they are unoccupied).
These places are set from the APKTOOL_DUMMY stub to restore the integrity of the progression. These lines are not used by anyone and do not affect anything.
A small note:If you delete a resource object from res/values/public.xml, then during the build, it will try to find such a free space and set its ID in it. If there are no available places, it will be added at the end of the list of items in its category. It is not recommended to do this with object IDs that are specified in Smali – this will cause a crash, because the resource specified by ID was moved (it no longer exists as such).
Deleting it public.xml this will force Apktool to create a progression from scratch – then APKTOOL_DUMMY will not be installed anywhere, because there are no free spaces between the starting and closing ID.
The need for APKTOOL_DUMMY is determined solely by the user. This may also be required if the decompiled project has a specif. structure among IDs (in particular, due to custom attributes and / or obfuscation).
During the build, the DEX and ARSC files are cached in the build folder. If you didn't change the resources after the previous build and re – built the apk,. arsc will not be created again, but will be picked up from the cached instance, because its hash is identical (not modified). This also applies to Smali (DEX files). Speeds up the apk build process by skipping recompilation.
Deleting a folder is accompanied only by freeing up space. After that, during the next build,. dex and. arsc will be re-created "from scratch" and the folder will be recreated. Activating this option allows you to automatically delete a folder after a successful build. Activate it if desired.
true, false, %1$d/%2$d
, now also includes vector graphics, references, and so on, as well as corrects some lines after auto-translation. Go to "Settings" → "Signature", select "Create key".
Signature algorithm:
Difference in the length of the certificate hash (after signing the apk). SHA256withRSA is optimal. We leave it by default. MD5 is considered insecure. Detailed differences can be found on the Internet.
Type:
Specifies the storage type. By default, JKS (can also be known as .keystore). Detailed differences can be found on the Internet.
Path to the key:
Output storage location for the key. The file name is entered automatically, and you can change it at the end if you want.
Alias:
Alias for the key. Specified during import/operation.
Storage and key password:
Password to protect the storage and the key itself before importing/using it. For convenience, you can make them identical.
Key Size:
Specifies the number of bits (length) of the key signature to read. The default value is 2048. Increasing the size increases its cryptographic strength, but it is more difficult to analyze (slower). Set using an informative geometric progression (2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, and so on)
Validity period:
The time from the creation date when the key's authenticity expires. Specified in years.
The following information is required to inform you about the signature owner. Specify as desired:
Name, position, organization, city, region/state, country.
The "Save" button completes the creation and places the key store in the previously specified path.
The "Create and use" button additionally imports the final file in place of the user signature.
In other words, it is important to preserve the directory structure!
After the necessary actions, we will archive the file with the apk extension back.Yes.
Please note!
All ciphers that are backward compatible can be converted back. This is done in the lower input window.Home screen → Three hours in the upper-right corner → "Settings" → "About the app" → "Disable update checking".
To select the target project-above "Build" there is a drop-down menu, there is an item MPatcher.