Background

Background

Silahkan klik beberapa gambar di bawah ini

  • image1
  • image2
  • image3
  • image4
  • image2
  • image1
  • image4
  • image3

We’re glad to Google and its developers for letting Android be an Open Source Project; accessed by anyone and everyone! Most of the code gets updated as soon as the new version of Android is announced, but this one just came from nowhere! Google has recently updated its JellyBean 4.2.1 code on AOSP (Android Open Source Project) to two (2) new branches namely android 4.2.1_r1.1 and android-4.2.1_r1.2 with corrosponding build number to be JOP40G. 
Here is a complete RAW changelog of the Source: [LINK]
Capture
We’ve got a few assumptions:

  • JOP40E and JOP40F were Initial builds before JOP40G
  • The changes are minor and not major
  • Most changes are Nexus 4 (mako) specific
  • Bluetooth fix hasn’t been merged yet, we shall expect it to be in 4.2.2 release
This is not 4.2.2, so please keep it clear in your mind. The source is just a minor update to the earlier JOP40D build.

If you’re a Developer who desires to build the latest AOSP JOP40G release for his/her device, visit here for complete Instructions directly Google.



source 

What is VTS?

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, which means 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.

Features

  • Never before seen UI
    • Fully featured IDE 
    • Seamless integration of useful external tools
      • ApkTool
      • Smali/Baksmali
      • ADB
      • Zipalign
      • Sign
      • dex2jar
      • Winmerge
      • Remote Theme Injector (RTI)
      • many more
    • Work with your apks just like having real java code
    • Support for apks and framework jars
    • Easily keep track of multiple apks/jars with the Solution Explorer
    • Manage big projects with ease
  • Edit smali code like never before
    • Syntax highlighting
    • Live syntax error checking
    • Jumping to smali references (method calls, fields, classes, gotos)
    • Help files on almost every smali command and topic
    • Connection between smali code and public.xml to expose hex references
    • Have a helpful look at the java source of any smali file if needed
    • Paste often used smali snippets right from the editor
  • Enhanced XML workflow
    • Easy navigation in XML documents
    • Follow XML resource paths and jump to the source file with a simple click
    • Previews of color codes, images and string resources directly in the xml file
  • Edit M10 files with great usability
    • Support for all Sense versions (3.0, 3.5, 3.6, 4.0, 4.1, 4.5)
    • Work with m10 files either with the dedicated M10 project or via the combined APK project
    • Decompile m10 images of all Sense versions to create HTC Sense themes
    • Quickly analyze the contents with the M10-Structure viewer
    • Validate your m10 changes with the syntax checker
    • Unimportant m10 parts are greyed out or completely hidden
  • Unpack and repack boot images (boot.img)
    • Easily edit any content of your boot.img
    • Dedicated syntax highlighting for *.rc and *.prop files
    • Advanced support for files modes and symlinks
    • Native implementation, no need for cygwin or the dsixda kitchen
  • Communicate with your device with yet to be seen ease
    • Tight integration of many ADB commands
    • Push apks easily to any place on your device
    • Remote import files to edit them with VTS
    • Debug your device with the integrated Logcat-Viewer
  • Enhance your workflow with useful additions
    • Easily create backups of your projects 
    • Dedicated compare interface for easy comparision of files, folders or projects
  • Hundreds of other awesome features (seriously, you really have to see and try it yourself)

Changelog

The changelog can be found here:
VTS Changelog (The changelog can also be found inside VTS)

Latest version for Windows Vista and newer

Download: Virtuous Ten Studio 2.1.30.7910
Released: 30.01.2013
MD5: 4FA752D6A32587A5CDEA8DA8056A5C39

Latest version for Windows XP

Download: Virtuous Ten Studio 1.11.21.7216
Released: 21.11.2012
MD5: 4C3B27D953D24D8E0C0CD18DDB749B88

android jelly bean 
 
For a long time now, Gingerbread 2.3 has been the dominant version of Android. More than 50% of devices ran Gingerbread up until recently, despite the OS being years old. Ice Cream Sandwich and Jelly Bean are catching up and have taken 29% and 13.6% of the Android pie, respectively. That’s 12.2% on Jelly Bean 4.1 and 1.4% on Jelly Bean 4.2

As the graphic above shows, Jelly Bean and Ice Cream Sandwich are running on more and more devices. There are a variety of reasons for this. People are buying newer devices running the newer operating systems. Sony’s 2011 Xperia line up have all been updated to ICS along with other older devices like the HTC Thunderbolt. A very small percentage can even be attributed to rooted devices running updated custom ROMs. So it’s really been a group effort getting things up to date.

Despite some great advances by Ice Cream Sandwich and Jelly Bean, Gingerbread still remains on top with a commanding 45.6%. These numbers are down from prior measurements and are continuing to trend that way. Nevertheless, it is a little sad that a 2 year old version of the OS is still dominate. Of course, this means that fragmentation continues to be a problem for Android.

Will Ice Cream Sandwich or Jelly Bean ever overtake Gingerbread?

It will eventually to be sure. While Gingerbread has been the dominate Android version for awhile now, Android continues to evolve and grow. This means that eventually Gingerbread will fade into obscurity. It just won’t be going silently into that good night.
One potential reason for Gingerbread’s continued success may be the cheap Android phone market. The best Android phones have quad core processors, run Jelly Bean, and have all sorts of awesome features. However, the cheap smartphones are just now getting to dual cores and to Ice Cream Sandwich.

Consider this, the Galaxy Note 2 running Jelly Bean costs over $300 on a new contract from just about everywhere. There are many mid-range phones and tablets that run Ice Cream Sandwich that are cheaper but not usually free. What is important to note is that devices like the new LG MyTouch on T-Mobile, a reportedly new device running Gingerbread, are still on the shelves and being handed out for free. Once those cheap, low end devices are being shipped with ICS and Jelly Bean, that’s when Gingerbread numbers will really start to decline.



Nexus devices are full of Android perks. One of the perks of being part of the Nexus family is factory images. Google provides these for Nexus users so that they can easily return their phones or tablets back to an out of box, factory condition should the need ever arise. Thankfully, the Nexus 4 factory image has reappeared on the Google Developers site after mysteriously disappearing shortly after release. Google gave no comment as to why the images were previously pulled. We’re happy to see it return.

Nexus 4 Occam Android 4.2.1 Factory Images

If you’re into rooting, running custom ROM’s, or custom kernels on your Nexus 4, it’s always a good idea to have a copy of the factory images stashed away somewhere just in case. To get back to stock, you’ll need a working copy of fastboot installed and working drivers (Windows). Then, you simply plug your phone into your computer via USB cable, extract the archive file, and run the appropriate shell script or batch file depending on whether your running Linux or Windows. It’s that simple.
Now we just need the official Nexus 4 binaries and full AOSP support. Come on Qualcomm get with the program.

Download Nexus 4 JOP40D factory image via Google Developers.