Go ahead and file this one in the Super Cool Tech category. A Russian blog, Rozetked.ru, posted video of a Galaxy S2 running two copies of Android at the same time. The three-and-a-half minute video takes us through a demo switching between a pair of ROMs while playing music from both, proving that the hardware resources can be shared. After the audio segment, we are shown decently high frame rates on a 3D benchmarking app and Angry Birds. According to the team behind the project, running two concurrent instances of Android only takes about 10% off of battery life while the impact on system speed is negligible.
Another day, another round of nightly builds for the upcoming CyanogenMod 10.1. This time, the latest release of the custom ROM that brings Android 4.2 has been made available on a further 3 devices: the Google Nexus S, Nexus S 4G, and the ASUS Transformer Pad 300 (TF300T).
It could oftentimes be unstable and not properly tested, lacking any changelogs, but eventually evolving into alphas, betas, release candidates, and finally stable releases.
The dedicated Android community has a way of tracking down OTA update files almost before the rollout begins. This is again the case for the newest Android 4.1.2 update for some variants of the unlocked Nexus S. Waiting for updates is for chumps, so get your Nexus S in hand, and proceed with caution.
To use this update file, your Nexus S has to meet the following conditions:
Back in July, Google made available the stock Jelly Bean images for a couple of the Nexus S variants, as well as the GSM Galaxy Nexus, and Nexus 7. Today, the build for the global Nexus S (soja) got updated to Android 4.1.1 (JRO03L), and the Nexus S 4G (sojas) Jelly Bean 4.1.1 image (JRO03R) made its way to Google's image download site, as well.
Unfortunately, there's still no sign of Jelly Bean showing up for the Korean version of the Nexus S (or the LTE Galaxy Nexii, for that matter). Sorry, guys - looks like we'll have to keep waiting for those.
Just earlier today, we found Sprint documents that confirmed the Galaxy Nexus variant on the Now Network would be receiving Jelly Bean today. Now, a Sprint employee has confirmed on its community message board that the Nexus S rollout will begin today. As with the GNex update, this will be an OTA, so no, refreshing over and over won't get it to you any faster.
Of course, it's still a reminder that CDMA Nexii get the short end of the stick. Not too short, mind you, as both of these phones will get Jelly Bean long before most devices from other manufacturers.
CDMA-based Nexuses (Nexii?) tend to get the short end of the stick when it comes to timely updates. The promise of the Nexus is that you'll always have the latest Android experience just the way Google imagines it. While the international version of the Galaxy Nexus has had Jelly Bean for a while, Sprint's been left in the cold. Until, tomorrow, September 6th, if Android Central's source is correct.
Here's the email that a tipster sent in:
After the successful landing of NASA's Curiosity rover on Mars this month, space exploration is once again at the forefront of everyone's minds. While the rover goes about its mission on the red planet, there are plenty of other exciting projects happening closer to home.
One of those projects is the CubeSat Launch initiative (CSLI), in which nanosatellites built by teams across the United States are hitching a ride into orbit on rockets planned for upcoming launches. The satellites are around 4 inches long, have a volume of one quart and weigh in the region of 3 pounds.
In order for a project to be eligible to participate in the CSLI, it must address aspects of science, exploration, technology development, education or operations.
Piracy is a major issue for Android, and even more so for Android developers, which is why Jelly Bean introduced App Encryption. But this may be a case of the cure being worse than the disease: hundreds of developers of paid apps have chimed in on a Google Code thread, claiming that the encryption (or more accurately, the location of installed and encrypted apps from the Google Play Store) makes their apps entirely unusable, as account information and other stored data is removed after a device reboot. As a result, Google has apparently disabled the security feature for the Play Store on Jelly Bean devices.
The time has come friends. Factory images are now available for several Nexus devices. The current factory image (JRO03[C-E] depending on the device) is available for most Nexus S variants, though the Korean and Sprint versions are conspicuously absent. Similarly, the Verizon-branded Galaxy Nexus is still off the list, but all other Galaxy Nexus versions are accounted for. And, of course, the carrier-less Nexus 7's factory image is available.
For those who prefer bullet points, here are the devices with factory images available as well as the build number for each:
- Nexus S (soju): Android 4.1.1 (JRO03E)
- Nexus S (sojua): Android 4.1.1 (JRO03E)
- Galaxy Nexus (yakju): Android 4.1.1 (JRO03C)
- Galaxy Nexus (takju): Android 4.1.1 (JRO03C)
- Nexus 7 (nakasi): Android 4.1.1 (JRO03D)
If you need to get back to the way things were when you first got your device, you can download the images from Google's download site right here.
After owners of the Nexus S i9023 and i9020T got an official 4.1.1 Jelly Bean OTA last night, the update has become available for the Nexus S' i9020A variant as well.
Just like before, the update can be downloaded straight from Google's servers, though Google has indicated that the OTA should be rolling out to Nexus S phones on "a number of carriers," meaning the wait for an automatic update prompt shouldn't be long.
RT @googlenexus: We've started rolling out Android 4.1, Jelly Bean, to Nexus S phones on a number of carriers with more to come. Enjoy!...