ApkSpy | View your APK manifest on the PC.
ApkSpy
Version: 1.8.19
Last update of the program in the header:05.02.2017
Short description:
View APK manifest on PC.
Description:
Application to run on a PC under Windows - allows users to view all the information on APC, including the name of the application and the requesting application permission.
What is good in this application - is its simplicity. Simply download the APK, dragging it to the program window and learn everything you need.
ApkSpy relies on aapt.exe tool from the Android SDK, so you'll need to install it (or just copy aapt.exe from somewhere, this is the only file needed to run ApkSpy)
Known issues:
file names in Unicode may not work.
Subject to the XDA-Developers 1.
Subject to the XDA-Developers 2.
Developer: ido
Russian interface: Unknown
Download:
Version: 1.8.19 ApkSpy (Post Latent # 58017036)
Post has been editedvadeus - 02.03.17, 17:31
Version: 1.8.19
Last update of the program in the header:05.02.2017
Short description:
View APK manifest on PC.
Description:
Application to run on a PC under Windows - allows users to view all the information on APC, including the name of the application and the requesting application permission.
What is good in this application - is its simplicity. Simply download the APK, dragging it to the program window and learn everything you need.
ApkSpy relies on aapt.exe tool from the Android SDK, so you'll need to install it (or just copy aapt.exe from somewhere, this is the only file needed to run ApkSpy)
Known issues:
file names in Unicode may not work.
Subject to the XDA-Developers 1.
Subject to the XDA-Developers 2.
Developer: ido
Russian interface: Unknown
Download:
Version: 1.8.19 ApkSpy (Post Latent # 58017036)
Past versions
Version: ApkSpy v0.6 + aapt.exe 
ApkSpy06.zip (1.61 MB)
ApkSpy06.zip (1.61 MB) Post has been editedvadeus - 02.03.17, 17:31
Reason for editing: edit
Russian description
Application to run on a PC under Windows - allows users to view all the information on APC, including the name of the application and the requesting application permission.
What is good in this application - is its simplicity. Simply download the APK, dragging it to the program window and learn everything you need.
ApkSpy relies on aapt.exe tool from the Android SDK, so you'll need to install it (or just copy aapt.exe from somewhere, this is the only file needed to run ApkSpy)
Known issues:
file names in Unicode may not work.
What is good in this application - is its simplicity. Simply download the APK, dragging it to the program window and learn everything you need.
ApkSpy relies on aapt.exe tool from the Android SDK, so you'll need to install it (or just copy aapt.exe from somewhere, this is the only file needed to run ApkSpy)
Known issues:
file names in Unicode may not work.
Meanwhile, the application is developed (by a different author):http: //forum.xda-devel...owthread.php t = 2710041?
POSCO author long ago abandoned the project, it has long been rewritten APKSpy by dmagician
http: //forum.xda-devel...owthread.php t = 2710041?
He rewrote it and added functionality, but the program is now written in .Net (4.0), weigh more mega against 36Kb and buggy. I did a version to run on XP failed - flies with exception clr20r3, without even having to show the window. Works, all well, by calling the AAPT (attached to the "local" attachem APKSpy 0.6).
Attachem all available versions, one that will work.
ApkSpy_v1.7.zip(152.46 KB)
ApkSpy_v1.8.zip(799.72 KB)
ApkSpy_v1.8.2.zip(801.3 KB)
I enclose a Batch script quickly showing the application name, version, and All Android API version required to run a specific APK (minSdkVersion - the minimum version of the API to run, targetSdkVersion - recommended version of the API).
Pts helps when you need to find out what "final" version of the application runs on your version of Android.
Downloading all the old versions of APK, which can find and check the script demands.
Once we find the version, in which minSdkVersion equal to or less than the version of the API, respectively, your version of Android - it means at least this version you can try to put on your system. Those. established it is established, will not swear. Work, too, is likely to be, but no, "there are no guarantees." The official version of the compatibility of specific applications to specific versions of the Android developers have to report, but they do, almost never, do not, possibly because many of them do not really know about "some sort of versions." Shaft driven and score at all, but what happens and enjoy the quiet, the old versions are no longer working - can vtyuhat new, which appeared for a long time, "unobtrusive" ads or other "warm tube" features ..
It should be noted that in certain moments, Google itself officially stops supporting acc versions of Android, and then begins to obstruct developers from laying out on the Market / Play new versions of applications that are compiled with support for older versions of the API (stupidly did not give a spread). The support for third parties and their products of any version of the API, and, respectively, Android, apparently Google does concern should not, however, a "discreet" encouraging developers to transition to the new version of the API, resp., More stringent requirements on the minimum version of Android, brings incompatibility of new application versions with older versions of android, although it had no objective reason that all also "gently stimulates the sale of new devices with the new" warm the lamp android. "
Can often be dull zapatchit minSdkVersion with rebuilding APK how some APKTool-th and it will work, but this number is, of course, is not always a ride, POSCO can be used when compiling newer versions of procedure calls, including to change the number or set of parameters, their dimension that does not allow the application to work with the old the API, even if there are no objective grounds for this. (Eg. References to the new features that are not in the old API.)
It is not always the only requirement is the minimum version of the API, and, respectively. Android.
Sometimes, on the contrary, the older programs do not want to work in the new version of Android. The program is put, but hangs or otherwise not working properly at startup. Such cases are rare, but do happen.
In addition to the version of Android from the program may be other requirements, including to the presence of a specific Hardware, without which it is established, but it will not work.
Script
======
APK is transmitted only command-line option. Without parameters shows a sign of conformity Android and Android versions of the API. It uses all the same AAPT.
For the "Dummies": Copy the code to the clipboard, open a new text file (eg Notepad-th), stock code there, save asAPKVer.bat
Command prompt: APKVer Programma.apk
All output goes to the console. Run "from Vind" useless flash of the window and "does not show anything." :)
Versions outputs at the end respectively. row and in HEX (hexadecimal),
for example he writes:
A: android: minSdkVersion (0x0101020c) = (type 0x10) 0x8
A: android: targetSdkVersion (0x01010270) = (type 0x10) 0x11
Field value number is outputted to the line end.
Translate it easier than ever:
Minimum version API = 0x8 = 8 (i.e. that hexadecimal 8, which is also a decimal 8, poskim 0A or less, resp. 10).
API 8 corresponds Android 2.2.x or higher
Recommended version API = 0x11 = 0x10 + 0x01 = 16 + 1 = 17 decimal
API 17 corresponds Android 4.2.x or higher.
For the future, including the hexadecimal record as 0xChISLO typical for C and C-like programming language.
In Assmeblere, Pascal, many languages and their records just at the end add h - ie instead of 0x11 will be written 11h.
The finished plate to translate hexadecimal to decimal:
from 0 to 9 = 0 to 9
0A - 0F = 10 - 15
10 - 19 = 16 - 25
1A - 1F = 26 - 31
20 - 29 = 32 - 41
2A - 2F = 42 - 47
If desired, you can alter the script to display information "simple," or even just compared the version of the API with the Android version, and displays this information.
At XDA have another script RenameAPK, enabling massively rename the APK in the folder according to the regulations of their official name and version, taken from the manifesto of all toyzhe utility AAPT
http://forum.xda-developers.com/showthread.php?t=1330359
I attach also the latest version of ADB 1.0.36 with the XDA, bargain with Fastboot from the same fresh SDK 24 (AAPT included was not)
fastboot_adb (1.0.36) _110716_r24.0.rar(793.23 KB)
As well as the older, widespread version of ADB 1.0.32 bargain with Fastboot and AAPT v0.2-2201632 from the same kit.
adb-binaries-windows-1.0.32.zip(1.2 MB)
http: //forum.xda-devel...owthread.php t = 2710041?
He rewrote it and added functionality, but the program is now written in .Net (4.0), weigh more mega against 36Kb and buggy. I did a version to run on XP failed - flies with exception clr20r3, without even having to show the window. Works, all well, by calling the AAPT (attached to the "local" attachem APKSpy 0.6).
Attachem all available versions, one that will work.
ApkSpy_v1.7.zip(152.46 KB)ApkSpy_v1.8.zip(799.72 KB)ApkSpy_v1.8.2.zip(801.3 KB)I enclose a Batch script quickly showing the application name, version, and All Android API version required to run a specific APK (minSdkVersion - the minimum version of the API to run, targetSdkVersion - recommended version of the API).
Pts helps when you need to find out what "final" version of the application runs on your version of Android.
Downloading all the old versions of APK, which can find and check the script demands.
Once we find the version, in which minSdkVersion equal to or less than the version of the API, respectively, your version of Android - it means at least this version you can try to put on your system. Those. established it is established, will not swear. Work, too, is likely to be, but no, "there are no guarantees." The official version of the compatibility of specific applications to specific versions of the Android developers have to report, but they do, almost never, do not, possibly because many of them do not really know about "some sort of versions." Shaft driven and score at all, but what happens and enjoy the quiet, the old versions are no longer working - can vtyuhat new, which appeared for a long time, "unobtrusive" ads or other "warm tube" features ..
It should be noted that in certain moments, Google itself officially stops supporting acc versions of Android, and then begins to obstruct developers from laying out on the Market / Play new versions of applications that are compiled with support for older versions of the API (stupidly did not give a spread). The support for third parties and their products of any version of the API, and, respectively, Android, apparently Google does concern should not, however, a "discreet" encouraging developers to transition to the new version of the API, resp., More stringent requirements on the minimum version of Android, brings incompatibility of new application versions with older versions of android, although it had no objective reason that all also "gently stimulates the sale of new devices with the new" warm the lamp android. "
Can often be dull zapatchit minSdkVersion with rebuilding APK how some APKTool-th and it will work, but this number is, of course, is not always a ride, POSCO can be used when compiling newer versions of procedure calls, including to change the number or set of parameters, their dimension that does not allow the application to work with the old the API, even if there are no objective grounds for this. (Eg. References to the new features that are not in the old API.)
It is not always the only requirement is the minimum version of the API, and, respectively. Android.
Sometimes, on the contrary, the older programs do not want to work in the new version of Android. The program is put, but hangs or otherwise not working properly at startup. Such cases are rare, but do happen.
In addition to the version of Android from the program may be other requirements, including to the presence of a specific Hardware, without which it is established, but it will not work.
Script
======
APK is transmitted only command-line option. Without parameters shows a sign of conformity Android and Android versions of the API. It uses all the same AAPT.
For the "Dummies": Copy the code to the clipboard, open a new text file (eg Notepad-th), stock code there, save asAPKVer.bat
Command prompt: APKVer Programma.apk
All output goes to the console. Run "from Vind" useless flash of the window and "does not show anything." :)
@echo off
if -% 1 == - goto _ListAPIs
C: \ ADB \ aapt.exe dump xmltree% 1 AndroidManifest.xml>% TEMP% \% 1.text
FIND / I "package"% TEMP% \% 1.text
FIND / I "versionName"% TEMP% \% 1.text
FIND / I "minSdkVersion"% TEMP% \% 1.text
FIND / I "targetSdkVersion"% TEMP% \% 1.text
del% TEMP% \% 1.text
goto _Exit
: _ListAPIs
echo.
echo Marshmallow 6.0 API level 23
echo Lollipop 5.1 API level 22
echo Lollipop 5.0 API level 21
echo KitKat 4.4 - 4.4.4 API level 19
echo Jelly Bean 4.3.x API level 18
echo Jelly Bean 4.2.x API level 17
echo Jelly Bean 4.1.x API level 16
echo Ice Cream Sandwich 4.0.3 - 4.0.4 API level 15, NDK 8
echo Ice Cream Sandwich 4.0.1 - 4.0.2 API level 14, NDK 7
echo Honeycomb 3.2.x API level 13
echo Honeycomb 3.1 API level 12, NDK 6
echo Honeycomb 3.0 API level 11
echo Gingerbread 2.3.3 - 2.3.7 API level 10
echo Gingerbread 2.3 - 2.3.2 API level 9, NDK 5
echo Froyo 2.2.x API level 8, NDK 4
echo Eclair 2.1 API level 7, NDK 3
echo Eclair 2.0.1 API level 6
echo Eclair 2.0 API level 5
echo Donut 1.6 API level 4, NDK 2
echo Cupcake 1.5 API level 3, NDK 1
echo (no code name) 1.1 API level 2
echo (no code name) 1.0 API level 1
: _Exit
if -% 1 == - goto _ListAPIs
C: \ ADB \ aapt.exe dump xmltree% 1 AndroidManifest.xml>% TEMP% \% 1.text
FIND / I "package"% TEMP% \% 1.text
FIND / I "versionName"% TEMP% \% 1.text
FIND / I "minSdkVersion"% TEMP% \% 1.text
FIND / I "targetSdkVersion"% TEMP% \% 1.text
del% TEMP% \% 1.text
goto _Exit
: _ListAPIs
echo.
echo Marshmallow 6.0 API level 23
echo Lollipop 5.1 API level 22
echo Lollipop 5.0 API level 21
echo KitKat 4.4 - 4.4.4 API level 19
echo Jelly Bean 4.3.x API level 18
echo Jelly Bean 4.2.x API level 17
echo Jelly Bean 4.1.x API level 16
echo Ice Cream Sandwich 4.0.3 - 4.0.4 API level 15, NDK 8
echo Ice Cream Sandwich 4.0.1 - 4.0.2 API level 14, NDK 7
echo Honeycomb 3.2.x API level 13
echo Honeycomb 3.1 API level 12, NDK 6
echo Honeycomb 3.0 API level 11
echo Gingerbread 2.3.3 - 2.3.7 API level 10
echo Gingerbread 2.3 - 2.3.2 API level 9, NDK 5
echo Froyo 2.2.x API level 8, NDK 4
echo Eclair 2.1 API level 7, NDK 3
echo Eclair 2.0.1 API level 6
echo Eclair 2.0 API level 5
echo Donut 1.6 API level 4, NDK 2
echo Cupcake 1.5 API level 3, NDK 1
echo (no code name) 1.1 API level 2
echo (no code name) 1.0 API level 1
: _Exit
for example he writes:
A: android: minSdkVersion (0x0101020c) = (type 0x10) 0x8
A: android: targetSdkVersion (0x01010270) = (type 0x10) 0x11
Field value number is outputted to the line end.
Translate it easier than ever:
Minimum version API = 0x8 = 8 (i.e. that hexadecimal 8, which is also a decimal 8, poskim 0A or less, resp. 10).
API 8 corresponds Android 2.2.x or higher
Recommended version API = 0x11 = 0x10 + 0x01 = 16 + 1 = 17 decimal
API 17 corresponds Android 4.2.x or higher.
For the future, including the hexadecimal record as 0xChISLO typical for C and C-like programming language.
In Assmeblere, Pascal, many languages and their records just at the end add h - ie instead of 0x11 will be written 11h.
The finished plate to translate hexadecimal to decimal:
from 0 to 9 = 0 to 9
0A - 0F = 10 - 15
10 - 19 = 16 - 25
1A - 1F = 26 - 31
20 - 29 = 32 - 41
2A - 2F = 42 - 47
If desired, you can alter the script to display information "simple," or even just compared the version of the API with the Android version, and displays this information.
At XDA have another script RenameAPK, enabling massively rename the APK in the folder according to the regulations of their official name and version, taken from the manifesto of all toyzhe utility AAPT
http://forum.xda-developers.com/showthread.php?t=1330359
I attach also the latest version of ADB 1.0.36 with the XDA, bargain with Fastboot from the same fresh SDK 24 (AAPT included was not)
fastboot_adb (1.0.36) _110716_r24.0.rar(793.23 KB)As well as the older, widespread version of ADB 1.0.32 bargain with Fastboot and AAPT v0.2-2201632 from the same kit.
adb-binaries-windows-1.0.32.zip(1.2 MB)Prozhku came across this while looking for something to see "on the fly" data-apk files. I liked. Actually, all I was looking for, was discovered in this little one.
After integration into Total Commander (the button with the% P% S-parameter) has become even more convenient to work with.
Among the few drawbacks, as noted - glitches with the renaming of unicode-application name (and with individual characters in the name). With the names of packages no problems noted.
Translated version 0.6, use. Included upx-compressed aapt.exe.
ApkSpy_06rus.zip(1.34 MB)
Post has been editedvovanKARPO - 05.02.17, 21:44
After integration into Total Commander (the button with the% P% S-parameter) has become even more convenient to work with.
Among the few drawbacks, as noted - glitches with the renaming of unicode-application name (and with individual characters in the name). With the names of packages no problems noted.
Translated version 0.6, use. Included upx-compressed aapt.exe.
Attached files
ApkSpy_06rus.zip(1.34 MB)Post has been editedvovanKARPO - 05.02.17, 21:44
Reason for editing: spoiler
ApkSpy 1.8.19 Updated
15th November 2016
What's new in this version:
- Fixed some Date parsing function (zipped file with no time stamp) in ZipStorer (by @Jaime Olivares) maybe causing some of the error reported here ...
More information on XDA
ApkSpy_v1.8.19.zip (809.84 KB) 4 >>>
ApkSpy_v1.8.19 + aapt.zip (2.11 MB)  |
The names in the Cyrillic alphabet apps are not friends
 |
Alternative
Apk-Info 0.7 Updated
27th April 2016
What's new in this version:
- APK-Info 0.7M (17.04.0216)
- - Added Dansk language (thanks to mosu).
- - Added Farsi language (thanks to HesamEdin).
- - Added French language (thanks to VSO Sofwtare)
- - Added German language (thanks to mosu)
- - Updated aapt (Android Build Tool) to 23.0.3 (compatibile with Androdi Marshmallow_ SKK23)
More information on XDA
** Changelog
APK-Info-0.7M.zip (1.3 MB) A source:https://mega.nz/#!KdpV...XKxP4uk8fFSaJmYQ1olBWc
Updated
29.08.2016
What's new in this version:
- APK-Info 0.7P (29.08.2016)
- - Replace aapt 24.0.0 with 23.0.6 for compatibility problem with apk name.
- - Add supprt for SDK 24 (Android 6.0.1) / SDK 25 (Android 7.0)
More information on XDA
** Changelog
APK-Info-0.7P.zip (1.32 MB) A source:https://mega.nz/#!fV4W...3SAq-BahU3bZP1RNX5_w0Q
+ Russian interface:
APK-Info-GUI.ini(20.57 Kb)APK-Info.ini(647 bytes) |
Similarly. The names in the Cyrillic alphabet apps are not friends
 |
Post has been editedLatent - 06.02.17, 00:37
Reason for editing: + APK-Info-0.7P.zip (cap on XDA no rules and new versions are lost in the subject)
I looked for a solution for application names in Cyrillic
in CMD you can change the encoding usingchcp 65001
And then the team gets all the available information about the application.
aapt d badging [apk]
Read the name in Cyrillic aapt, as we see can. So we must be wise as the developers to use it.
in CMD you can change the encoding usingchcp 65001
And then the team gets all the available information about the application.
aapt d badging [apk]
Default cmd.exe uses cp866 encoding. Current encoding can be viewed chcp team. Sometimes you need to use the terminal Unicode. To do this, use the font "Lucida Console" and switch the encoding command
>chcp<codepage>
where the parameter<codepage>for UTF-8 is 65001
Apk-Cyrilic.bat
Run:
Apk-Cyrilic.bat est.driver_1.6.5.1317.apk
We get a text file:
est.driver_1.6.5.1317.apk.txt
As you can see all readable:
application-label: 'ECT: Driver'
application-label-ru: 'ECT: Driver'
>chcp<codepage>
where the parameter<codepage>for UTF-8 is 65001
Apk-Cyrilic.bat
:: Change the code page to the Russian text was readable (for applications in Cyrillic)
C: \ WINDOWS \ system32 \ chcp 65001>nul
aapt d badging% 1>% 1.txt
pause
C: \ WINDOWS \ system32 \ chcp 65001>nul
aapt d badging% 1>% 1.txt
pause
Run:
Apk-Cyrilic.bat est.driver_1.6.5.1317.apk
We get a text file:
est.driver_1.6.5.1317.apk.txt
package: name = 'est.driver' versionCode = '193' versionName = '1.6.5.1317'
sdkVersion: '5'
targetSdkVersion: '9'
uses-permission: 'android.permission.ACCESS_FINE_LOCATION'
uses-permission: 'android.permission.ACCESS_COARSE_LOCATION'
uses-permission: 'android.permission.ACCESS_WIFI_STATE'
uses-permission: 'android.permission.CHANGE_WIFI_STATE'
uses-permission: 'android.permission.INTERNET'
uses-permission: 'android.permission.ACCESS_NETWORK_STATE'
uses-permission: 'android.permission.WRITE_EXTERNAL_STORAGE'
uses-permission: 'android.permission.VIBRATE'
uses-permission: 'android.permission.WAKE_LOCK'
uses-permission: 'android.permission.READ_PHONE_STATE'
uses-permission: 'android.permission.CALL_PHONE'
uses-permission: 'android.permission.WRITE_SETTINGS'
uses-feature-not-required: 'android.hardware.telephony'
uses-feature-not-required: 'android.hardware.location'
uses-feature-not-required: 'android.hardware.location.gps'
uses-feature-not-required: 'android.hardware.location.network'
uses-feature-not-required: 'android.hardware.wifi'
application-label: 'ECT: Driver'
application-label-ru: 'ECT: Driver'
application-label-en: 'EST: Driver'
application-label-mn: 'EST: Driver'
application-label-cs: 'EST: Řidič'
application-label-et: 'EST: Taksojuht'
application-label-pt: 'EST: Motorista'
application-label-uz: 'EST: Xaydovchi'
application-icon-120: 'res / drawable-hdpi-v4 / icon.png'
application-icon-160: 'res / drawable-hdpi-v4 / icon.png'
application-icon-240: 'res / drawable-hdpi-v4 / icon.png'
application-icon-320: 'res / drawable-hdpi-v4 / icon.png'
application-icon-65535: 'res / drawable-hdpi-v4 / icon.png'
application: label = 'ECT: Driver' icon = 'res / drawable-hdpi-v4 / icon.png'
launchable-activity: name = 'est.driver.ESTActivity' label = '' icon = ''
uses-permission: 'android.permission.READ_EXTERNAL_STORAGE'
uses-implied-permission: 'android.permission.READ_EXTERNAL_STORAGE', 'requested WRITE_EXTERNAL_STORAGE'
uses-feature: 'android.hardware.touchscreen'
uses-implied-feature: 'android.hardware.touchscreen', 'assumed you require a touch screen unless explicitly made optional'
main
other-services
supports-screens: 'small' 'normal' 'large' 'xlarge'
supports-any density: 'true'
locales: '--_--' 'ru' 'en' 'mn' 'cs' 'et' 'pt' 'uz'
densities: '120' '160' '240' '320' '65535'
sdkVersion: '5'
targetSdkVersion: '9'
uses-permission: 'android.permission.ACCESS_FINE_LOCATION'
uses-permission: 'android.permission.ACCESS_COARSE_LOCATION'
uses-permission: 'android.permission.ACCESS_WIFI_STATE'
uses-permission: 'android.permission.CHANGE_WIFI_STATE'
uses-permission: 'android.permission.INTERNET'
uses-permission: 'android.permission.ACCESS_NETWORK_STATE'
uses-permission: 'android.permission.WRITE_EXTERNAL_STORAGE'
uses-permission: 'android.permission.VIBRATE'
uses-permission: 'android.permission.WAKE_LOCK'
uses-permission: 'android.permission.READ_PHONE_STATE'
uses-permission: 'android.permission.CALL_PHONE'
uses-permission: 'android.permission.WRITE_SETTINGS'
uses-feature-not-required: 'android.hardware.telephony'
uses-feature-not-required: 'android.hardware.location'
uses-feature-not-required: 'android.hardware.location.gps'
uses-feature-not-required: 'android.hardware.location.network'
uses-feature-not-required: 'android.hardware.wifi'
application-label: 'ECT: Driver'
application-label-ru: 'ECT: Driver'
application-label-en: 'EST: Driver'
application-label-mn: 'EST: Driver'
application-label-cs: 'EST: Řidič'
application-label-et: 'EST: Taksojuht'
application-label-pt: 'EST: Motorista'
application-label-uz: 'EST: Xaydovchi'
application-icon-120: 'res / drawable-hdpi-v4 / icon.png'
application-icon-160: 'res / drawable-hdpi-v4 / icon.png'
application-icon-240: 'res / drawable-hdpi-v4 / icon.png'
application-icon-320: 'res / drawable-hdpi-v4 / icon.png'
application-icon-65535: 'res / drawable-hdpi-v4 / icon.png'
application: label = 'ECT: Driver' icon = 'res / drawable-hdpi-v4 / icon.png'
launchable-activity: name = 'est.driver.ESTActivity' label = '' icon = ''
uses-permission: 'android.permission.READ_EXTERNAL_STORAGE'
uses-implied-permission: 'android.permission.READ_EXTERNAL_STORAGE', 'requested WRITE_EXTERNAL_STORAGE'
uses-feature: 'android.hardware.touchscreen'
uses-implied-feature: 'android.hardware.touchscreen', 'assumed you require a touch screen unless explicitly made optional'
main
other-services
supports-screens: 'small' 'normal' 'large' 'xlarge'
supports-any density: 'true'
locales: '--_--' 'ru' 'en' 'mn' 'cs' 'et' 'pt' 'uz'
densities: '120' '160' '240' '320' '65535'
As you can see all readable:
application-label: 'ECT: Driver'
application-label-ru: 'ECT: Driver'
Read the name in Cyrillic aapt, as we see can. So we must be wise as the developers to use it.
I contact the author. Someone can, slowly, to collect on any platform stable version (any tools) to support transfer the APK file on the command line (instead of or in parallel with Drag'n'Drop functionality). The conclusion in this case, to give:
1. In the window - ie, as of now, and do not need to alter anything,
2. In the console, with support for redirection to a file (such as "APKUtil MyApp.apk>Report.txt ", ie the creation of the report).
3. To provide for both functional, depending on the configuration of (h-z keys com line or .ini)
4. To provide for the conclusion in the report is only interested in the fields, depending on the configuration of (h-h keys com line anyway) - for example:
- only the application name and version,
- only or additional requirements for the API or directly, the Android version
- only or additional requirements for the permits.
- a kind of format of the output, conversion to "chelovekoponyatny" look, cutting off the excess.
- Other options of what can be useful to do.
This functionality allows you to create reports from APK pile, for example, running cyclically in a folder for each file. And because you can rename and provide templates - as someone useful, for example, by com.app ... or the name of the version.
5. Write a plugin for FAR and / or Total Commander with a similar or more extensive functionality.
The list is very long ...
Please do not be taken as "list of demands" - this is just the options of ideas. Who on that much and who have the desire, the ability and time to develop - he will choose which of the proposed he is willing and able to implement and in what form. The fact remains. On this day no advanced tools for working with APK not, and in fact it is very necessary to all those that they APK not only starts, but creates them something new, trying to change the world for the better.
In theory, because for APKshek can make the most of the functionality from a wide view of the manifesto in one form or another, or rename files (as an example of the action) to patch the binary fields of any resource within, such as the rights, requirements for the API (they are sometimes overestimated due the machinations of developers of Google or disorder, believes that the new the API, all of a sudden, it became better meet the objectives of manufacturing another "calendars"), automatic repacking and perepodpisyvaniya, or even call dalvik decompiler with the patch and rebuilding. Limitless creative possibilities of any level of complexity.
All the same, APK thing is not too complicated. People understand far more complex structures and for years wrote an extremely complex, multi-function code. Somebody, for comparison, try to see what it can do Hiew with binary data and Nate code for all common processors, a rich feature set is hidden in a small utility, which the author wrote in the days of his youth, in the 90s for DOS (a main part) and supports little to this day.
1. In the window - ie, as of now, and do not need to alter anything,
2. In the console, with support for redirection to a file (such as "APKUtil MyApp.apk>Report.txt ", ie the creation of the report).
3. To provide for both functional, depending on the configuration of (h-z keys com line or .ini)
4. To provide for the conclusion in the report is only interested in the fields, depending on the configuration of (h-h keys com line anyway) - for example:
- only the application name and version,
- only or additional requirements for the API or directly, the Android version
- only or additional requirements for the permits.
- a kind of format of the output, conversion to "chelovekoponyatny" look, cutting off the excess.
- Other options of what can be useful to do.
This functionality allows you to create reports from APK pile, for example, running cyclically in a folder for each file. And because you can rename and provide templates - as someone useful, for example, by com.app ... or the name of the version.
5. Write a plugin for FAR and / or Total Commander with a similar or more extensive functionality.
The list is very long ...
Please do not be taken as "list of demands" - this is just the options of ideas. Who on that much and who have the desire, the ability and time to develop - he will choose which of the proposed he is willing and able to implement and in what form. The fact remains. On this day no advanced tools for working with APK not, and in fact it is very necessary to all those that they APK not only starts, but creates them something new, trying to change the world for the better.
In theory, because for APKshek can make the most of the functionality from a wide view of the manifesto in one form or another, or rename files (as an example of the action) to patch the binary fields of any resource within, such as the rights, requirements for the API (they are sometimes overestimated due the machinations of developers of Google or disorder, believes that the new the API, all of a sudden, it became better meet the objectives of manufacturing another "calendars"), automatic repacking and perepodpisyvaniya, or even call dalvik decompiler with the patch and rebuilding. Limitless creative possibilities of any level of complexity.
All the same, APK thing is not too complicated. People understand far more complex structures and for years wrote an extremely complex, multi-function code. Somebody, for comparison, try to see what it can do Hiew with binary data and Nate code for all common processors, a rich feature set is hidden in a small utility, which the author wrote in the days of his youth, in the 90s for DOS (a main part) and supports little to this day.
boipelo @ 17.09.16, 17:03
Included upx-compressed aapt.exe.
You, and respectively, in Latent assembly "ApkSpy_v1.8.19 + aapt.zip" a strange aapt.exe
Created (compiled, probably) 06/02/2014, size 1698KB, and is a post-compression UPX-th.
I gathered a few binaries, all versions v0.2. The most "old" is the date of 13/03/13 and the size of 855KB. Other - v0.2-2201634 (number probably refers to the build number) has a 1424KB size. Third - v0.2-2679779 - 1425KB in size, attached to the Latent files with APK-Info V0.7M / P and of which he mentions as: "Replace aapt 24.0.0 with 23.0.6 for compatibility problem with apk name." Where he was able to extract the marked version number, I'll never know. The binaries of such sequences can not find. The utility provided AAPT version command that outputs the higher value given by me. All 3 versions shown no signs of any package or executable file compressor, as well as with the mind, after cursory inspection did not have signs of interference.
Unpacked version packed with UPX - came 6066KB. V0.2 version of its "no build number." Created 02.06.2014.
Compilers are now no different "efficiency" is not enough, Android SDK and the ADB, in particular, (as well as other utilities from his kit like aapt) all compiled by different compilers because of what they "always" differ greatly in size. But oversize already 4 times from "the previous record" has caused some suspicion. Leafing through, flipping through the data, I did not find anything suspicious, no visible containers, pieces of encrypted code or other payload is not observed. Instead, there is a huge amount to link the debris. Most likely not disable linking of debug information, but it may simply something extra nalinkovali. "Empty space" is almost there.
Either way, the size of the "normal" exe has grown in recent years, twice during that version is still v0.2. A similar situation with adb, although there is at least the last part of the version number changes. In general fastboot version number where either can not be traced. Who knows clarify the situation with the numbering aapt versions, as well as the adb, and fastboot, assemblies, sizes and so forth. Perhaps in the source code are some changes that are suddenly not recognized any version numbers, any "change history", which, incidentally, is also nowhere to be seen. Perhaps it is somewhere in the bowels of the SDK ...
©savagemessiahzine.com2005-2019. All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement