latest
Android has gone through quite a few changes during its short 6 years of life. The Android that drives most of the world's smartphones of today would be almost unrecognizable to what was launched in late 2008. We've seen massive visual changes, expansion to almost every conceivable form factor, and a completely fleshed-out content ecosystem for multimedia and apps. As the operating system matured, some elements have successfully grown with it, and others have become dead weight. Naturally, progress calls for the replacement of those pieces that haven't scaled well. We've seen an excellent example of this when ART came to replace Dalvik as the standard Android runtime. With the release of Lollipop, a similar project emerged that promises to replace a part of the existing app development toolchain with a pair of new compilers called Jack and Jill.
It looks like Google is putting the last nail in Dalvik's coffin, and the new Android Runtime (ART) is about to take the throne. A pair of commits turned up last night in the master branch of the Android Open Source Project (AOSP) repository that spell certain doom for the Android runtime we've known and loved for all these years. The first of the two changes completely wipes the /libdvm (Dalvik Virtual Machine) folder from AOSP, and the second takes care of changing all of the relevant configuration files and startup scripts to call on the ART runtime. Yup, this is the end for Dalvik.
It was only 3 months ago when we first met the brand new Android Runtime, dubbed ART. In that time it has gained a substantial following by enthusiasts throughout the Android community. Given its "preview" status and warnings from the Android team that ART wasn't ready for the general population, it appeared unlikely that it would officially take the place of Dalvik anytime soon. However, a new commit to the Android Open Source Project (AOSP) is strong evidence that ART may become the default runtime in the next version of Android.
Shortly after the new Android Runtime made its grand entrance, I ran a pretty exhaustive (and exhausting) series of performance benchmarks that showed ART wasn't really ready to blow us away. At the time, I opted to avoid the topic of battery life because it is so difficult to test accurately and with unbiased, meaningful results. As it turns out, that was dumb. Yup, so many of you have asked, I finally had no choice but to dive in and run a battery of tests on...well, the battery.
By now you've probably heard about ART and how it will improve the speed and performance of Android, but how does it actually perform today? The new Android Runtime promises to cut out a substantial amount of overhead by losing the baggage imposed by Dalvik, which sounds great, but it's still far from mature and hasn't been seriously optimized yet. I took to running a battery of benchmarks against it to find out if the new runtime could really deliver on these high expectations. ART is definitely showing some promise, but I have to warn you that you probably won't be impressed with the results you'll see here today.
It's fair to say that Android went through some chaotic years in the beginning. The pace of development was frantic as the operating system grew at an unprecedented rate. An as-yet undetermined future led to decisions that were made to conform to existing hardware and architectures, the available development tools, and the basic need to ship working code on tight deadlines. Now that the OS has matured, the Android team has been giving more attention to some of the components that haven't aged quite as well. One of the oldest pieces of the Android puzzle is the Dalvik runtime, the software responsible for making most of your apps run. That's why Google's developers have been working for over 2 years on ART, a replacement for Dalvik that promises faster and more efficient execution, better battery life, and a more fluid experience.
[For Developers] Smali / Baksmali Updated v2.0 Beta Is Out, Now Multithreaded For Your Pleasure
If you're in the modding and theming community, your work is about to get a bit faster, because Smali v2.0 is now in beta and firing on all cylinders.
If you're in the modding and theming community, your work is about to get a bit faster, because Smali v2.0 is now in beta and firing on all cylinders. The new version brings multithreaded processing and a few tweaks to the language that should result in cleaner-looking code.
This week, we saw a new kid among Android decompilers hit the street - JEB. JEB is a full featured, commercial dalvik decompiler aimed at security researchers and reverse engineers. Although many other decompilers exist, such as DED, Androguard, baksmali, dex2jar, undx, etc and most of them are free and work quite well, JEB comes with features not seen in most free tools:
Myriad is continuing their quest to make Android apps run on just about everything with the release of Alien Dalvik 2.0. The latest operation system in their crosshairs is none other than iOS -- specifically the iPad branch of iOS. That's right, Android apps on an iPad.
Some combinations are as natural as peanut butter and jelly - Avatar & 3D, Apple & dictatorship, and Conan O'Brien & late-night comedy, to name a few. But are Android apps and the BlackBerry PlayBook also such a sweet match? If you ask RIM, the answer is a firm, definitive "yes."
About 2 weeks ago, BGR broke the rumor of RIM's upcoming tablet, the BlackBerry PlayBook, possibly being capable of running Android apps sometime after launch, which the latest rumors put at the end of March/beginning of April with a price sticker of $499.99. The company was seriously looking into this possibility and was trying to decide whether using the Dalvik virtual machine (the same one Android uses to run its apps) was a viable way to move forward. BGR is usually very credible, so the rumor definitely had legs.
Zurich-based mobile software developer Myriad Group has announced the launch of "Alien Dalvik", an emulator which will enable unmodified Android apps to run on devices not using the Android OS.
As if Oracle's, Microsoft's, and Apple's [1] [2] suits weren't giving Android enough headache, today, Gemalto, an Amsterdam-based digital security company, added some fuel to the flames by filing a patent infringement suit against Google and its partners HTC, Samsung, and Motorola. The suit claimed that Android and the Dalvik operating environment incorporated Gemalto's patented Java Card technology without the company's permission.
As you may have heard, Oracle (who now own Sun and the Java programming language) filed a patent infringement suit against Google related to the use of Java on the Android platform (particularly in the Dalvik VM, details on TechCrunch if you’re interested). Google has responded to Oracle’s suit, and they are ready to make a stand: