Root [Boost Mobile] Virtuous Ten fix!

[mercury0x000d]

I got an update to VTS today which had the following changelog:

Changes in Version 2.3.27.9200
------------------------------
-VTS now remembers open documents for each project
-“Keep old signature” now automatically copies old AndroidManifest.xml for better compatibility
-Completely new set of icons (metro style)
-Added ability to manually specify/override java path
-Reworked recent files system. You are now able to provide a custom path where you want VTS to search for existing solution files.
-Settings are now completely based on public xml files
-Added “Fullscreen mode” (F11)

This is only a very small part of the changelog. Please check the in-app changelog after updating for the full list of changes.

The thing to note here is item #2, the "keep old signature" fix... we no longer have to copy over AndroidManifest.xml manually! Gotta love that. Just thought I'd share this with the other devs who had problems with signing APKs in the past with VTS.


Edit: tested this by building some modified APKs for Warp OEM 2.01, and it works flawlessly! The only catch is that you may have to re-import the APK first before it will build correctly due to the previous version not extracting the necessary data originally from the file. But no biggie

 

[chopolo]

I read it but didnt understand a word of it lol. wait a minute i'm not a dev!!!!!!no wonder i didnt get it lol.

 

[Skinnyjeans21]

What do you mean re-import the file? Its a little vague... :/

 

[mercury0x000d]

What do you mean re-import the file? Its a little vague... :/

Let's say you have a solution with several projects (APKs) in it. If any of the projects in the solution were decompiled from within the old version, you'll have to right click on that project, unload it, then re-import it into the solution.

In my case, I have a solution which implements the WOEM modified settings menu, which includes the Automount APK, No-Frills and the stock settings menu APK. I simply removed the stock settings menu APK from the solution, imported the finished settings APK which was output from the previous version of VTS (which already had all my modifications inside) and I was good to go. The APK now builds and pushes, and I can run it directly on my device with no manual modifications.

Hope this helps

 

[Skinnyjeans21]

Ahhh I see thanks!

 

[BLVCKHVLO]

Saaaaweeeeet! Of course all these fixes come out after I learned the hard way and am about to drop my first rom.

Same with UOT. I one thumbed a whole rom, boom- uot was back up. I wanted to throw my laptop in the trash lol.

I have become pretty accustom to apkchanger. There are still things you can manually do in there that can't be done with vst when it comes to compilation errors. Sometimes I just want to compile exclusively the file I worked on and pop it into the original apk (which you can't do with vst if it wont decompile or compile with brute force. VST takes care of baksmali though and keeps everything nice and consolidated. You have to have both in my books if you want perfection,