Virtuous Ten Studio v3.6.30.14100 Cracked

Virtuous Ten Studio v3.6.30.14100 Cracked
Requirements: Windows Vista and up, .NET Framework 4.5, Latest JRE
Overview: Virtuous Ten Studio (VTS) is the ultimate solution for the modification of android applications. This program allows you to manage entire Android projects within an easy to use and familiar environment.


Virtuous Ten Studio (VTS) is the ultimate solution for the modification of android applications. This program allows you to manage entire Android projects within an easy to use and familiar environment.

The intended group of users covers anyone from a themer over ROM devs up to the smali gods known for their awesome mods of existing apks. The modifcation of smali code is one of the biggest features in VTS. You can easily decompile, edit and recompile any apk or jar file.
However, the application is not limited to smali files. You can edit almost any file found inside an apk or jar.

Virtuous Ten Studio is also the official successor to the highly important M10Tools released 2011 by the Virtuous Team. You can easily edit any m10 file from Sense apps in order to resize, modify or theme them.

Additionally VTS brings support for un- and repacking of boot images (boot.img), a job that previously required a cygwin installation with the dsixda kitchen. Since VTS’ own implementation is a native windows solution, you don’t need dsixda or cygwin anymore.

VTS has been designed to run on Windows, has been in development for over a year and has gone through many stages of testing. We now feel that the it is mature enough to be released publicly.

Virtuous Ten Studio doesn’t have a lot of requirements. However, a few things are needed. Let’s start with the required software:

Windows Vista or later (including Windows
Windows XP support is only available for a few older versions
Microsoft .net framework 4.5 (.net 4.0 for Windows XP)
Lastest Java Runtime (JRE) (32-bit)
Working ADB drivers if you want to take advantage of the ADB integration

Even though there are no special hardware requirements, VTS runs a lot more performant with good hardware. Here a list of the biggest influences:

RAM: 2GB or more is recommended
Solid State Disks (SSDs) greatly improve the overall performance of VTS, almost every task is going to be completed quicker
Screen size: VTS can be configured to use a lot of screen real estate to directly display important information. A full HD (1080p) 21″ screen or bigger is recommended for the best experience (smaller screens work too of course)

Changelog:
3.6.30
Adjusted default configs to better reflect common usage scenarios
Added a “Self-Import” context menu entry to all projects which builds the project and directly imports the binary again. Useful for applying changes which require a fresh import (eg. debug symbols on/off in smali etc)
Changing the project configs now prompts you to do a self import so the project data always reflects the actual configuration (think of switching between resource decoding yes/no)
Updated java decompiler for better compatibility
Removed the ability to cancel tasks as it never actually cancelled anything but only removed them from the list, it’s more obvious now that you need to wait until the tasks finish
Added feature to prevent script editing while the script is running to prevent weird runtime errors
Fixed various bugs related to the script system and the documents
Visual script editor looks more streamlined now
Added several visual clues to the script editor to help the user navigate
Switching projects in the script editor now won’t reset the selected script type, so you can easily compare the scripts of different projects
Added a little help file for the script manager
The configuration manager can now be opened from the ribbon bar (even without loading any projects)
Added a basic SDK for writing your own custom plugins for VTS (in C#). You can find it in the VTS install folder


More Info: HERE