That last bit of info about Dalvik contradicts news that came out at about the same time saying that RIM won't be
using Dalvik due to a recent patent dispute between Google and Oracle.
That said, all those sources are claiming is that RIM is considering
using the Dalvik VM.
Though the RIM representative mentioned Dalvik, conflicting reports have stated that RIM won't end up
using the Dalvik engine, but rather a different option.
According to «multiple trusted sources» speaking to BGR, RIM is considering
using the Dalvik Java virtual machine, as used by Android, and potentially opening the door to the PlayBook and other QNX - based devices to run Android code.
This method requires downloading the Android SDK and then
using the Dalvik Debug Monitor to capture screenshots, which means you have to have the Motorola Xoom plugged into your computer via USB to take screenshots — not exactly convenient.
Just like other versions of Android, Honeycomb is a modern Linux - based OS which
uses the Dalvik virtual machine to run code similar to Java apps.
The rumor is that RIM is considering to
use Dalvik virtual machine for their QNX OS on the PlayBook and mobiles, which is the same as what Android currently uses.
Not exact matches
If nothing else, this points out how lame Android is after 2 years of trying to copy iOS and doing nothing innovative except stuffing more cores into an antiquated OS - the old
Dalvik machine that android
uses.
All applications you
use on your android device actually run in what's called a virtual machine, the
Dalvik runtime...
The matter is still sub-judice and
using the open source
Dalvik virtual machine ran the risk of RIM being sucked into the ongoing Google Oracle imbroglio.
No mention of what other method they will be
using at this time but a lot of companies have been creating virtualization platforms as of late, the latest being Myriad which has recently announced their Myriad Alien
Dalvik.
The Myriad Alien
Dalvik allows Android apps to run seamlessly on other platforms and will be demoed at Mobile World Congress later this month
using Nokia's MeeGo platform.
That's not to say Myriad Alien
Dalvik will be
used but nothing is stopping Research In Motion from reaching out to any other virtualization partners to help out.
Now, by
using the recovery menu select «wipe data factory reset», «wipe cache partition» and «Wipe
Dalvik Cache» (it is a good idea to backup the data before applying this step).
Presumably, the PlayBook will not run Android applications with pieces built
using Android's native development kit — pieces that run outside of
Dalvik.
Now, by
using the recovery menu select «wipe data factory reset», «wipe cache partition» and «Wipe
Dalvik Cache» (it is a good idea to backup the data before applying this step).
The
Dalvik cache is
used so that the device does not need to recompile apps, instead, it is compiling only the most necessary parts of it and caching that.
Also, as we have previously mention, the switch to the Android Runtime (ART) instead of
Dalvik is going to improve battery life during active
use.
Once in recovery,
use the main menu and select the following options: «wipe data factory reset», «wipe cache partition» and «wipe
dalvik cache».
Use the recovery options and clear the internal storage system — select «wipe data factory reset», «wipe cache partition» and «wipe
dalvik cache».
Moving over to ART, Android Runtime, permanently, Google promises a 15 - 20 % performance increase
using the same apps just by moving from
Dalvik to ART.
ART replaced the aging
Dalvik Virtual Machine and gave Google and developers greater control of Android on a deep level, as well as elevating performance and memory
use to new heights.