May 13

iPad 2’s New 32nm SoC Improves Battery Life ...

The lower priced iPad 2 that Apple introduced upon the release of the 3rd generation iPad in March has a new, more energy efficient processor that can increase battery life by over two hours compared to the “original” iPad 2, AnandTech reported Friday. The “new” iPad 2, designated “iPad 2,4” uses a 32 nanometer SoC (system on a chip), compared to the 45 nanometer SoC on its predecessor.

Apple’s current iPad lineup, including the “new” iPad 2 with a 32nm A5 SoC (source: AnandTech)

The Samsung-sourced chip grants benefits to both Apple and consumers. from Apple’s perspective, the new SoC gives Apple the ability test out the 32nm process, likely to make its way into the next iPhone, on an existing architecture with lower volume, minimizing risk in the event of complications. It also helps lower manufacturing costs. 

For consumers, the chip performs at the same level as the “original” iPad 2, while providing better battery life and cooler operating temperatures.

In a Wi-Fi web browsing test, the 32nm iPad 2 scored 11.7 hours of battery life, compared to 10.1 hours for the 45nm version, an increase of 1.6 hours or 15.8 percent.

Under a processor-intensive gaming test using Infinity Blade 2, the 32nm iPad 2 nets 7.9 hours, compared to 6.12 hours for the 45nm iPad 2, a 1.78 hour increase, or 29 percent. a less stressful gaming test, Riptide GP, has the 32nm version reaching 8.82 hours compared to 6.77 hours for the 45nm iPad 2.

Finally, with a video playback test using 720p H.264 content, the 32nm iPad 2 gets an astonishing 15.7 hours of battery life compared to 13.3 hours for the 45nm version.

Chart by The Mac Observer from AnandTech data.

This increased battery life is accompanied by lower operating temperatures, with the 32nm iPad 2 reaching a maximum temperature of 33.2 degrees Celsius compared to 34.2 degrees on the 45nm iPad 2 and 41.9 degrees on the warmer-running 3rd generation iPad. 

With such a significant increase in battery life, the 32nm iPad 2 may be useful for individuals who don’t need the 3rd generation iPad’s faster graphics performance or the improved resolution “retina display.”

Unfortunately, as AnandTech points out, the 32nm iPad 2,4 is difficult to find, with Apple and many of its partners still selling leftover stock of the 45nm iPad 2,1. There’s also no way to tell what version of the iPad 2 is in the box without opening it and running system benchmarking and profiling software like GeekBench.

Availability may improve over time as the original stock of 45nm iPad 2’s run out but, for now, if you’re in the market for an iPad 2 make sure the retailer you purchase it from has a good return policy in case the model you pick up isn’t 32nm.

iPad 2’s New 32nm SoC Improves Battery Life Over 2 Hours

Feb 26

Google ends full support for CDMA devices, ...

Disturbing news from the official Android developer website: it appears that nearly all reference to CDMA phones and tablets has disappeared from the official documentation. This includes Android source code and factory ROMs for Verizon’s CDMA version of the Galaxy Nexus and Motorola XOOM, as well as the Nexus S 4G. What this implies (and only implies) is that Google is no longer providing official updates for the removed devices, as is generally expected of “developer” hardware. the GSM Nexus S and WiFi-only Motorola XOOM are still present, as are the two initial images for the Galaxy Nexus CDMA/LTE, though these are marked as “archived, for reference only”.

After a fast and frenzied response from angry Nexus owners, Google clarified its position on the Android Contributors Google Groups page. Basically, the company has decided to remove CDMA devices from its official support documentation because the technology and software required to make them function correctly is closed-source. the radios and other APK files for a CDMA device must be digitally signed by a carrier, something that can’t be open-sourced, and therefore isn’t included in the Android Open Source Project. it boils down to this: Google can’t control every aspect of the software, and based on the principles of “Nexus” and developer devices, CDMA devices don’t really qualify.

Here’s the official statement in its entirety:

Hello! This is a quick clarification about support for CDMA devices.

For various technical reasons, recent CDMA Android devices implement core telephony functionality in .apk files provided in binary form by the carriers. To function correctly, these .apk files must be signed by the so-called “platform” key. however, when an individual creates a custom build from the AOSP source code, they don’t use the same signing key as these CDMA flies were signed with.the result is that these files don’t work properly, and pure AOSP builds running on these devices can’t place calls, access mobile data, and so on. Because we aim to make sure that we are as clear as possible about the degree of support that devices have, we updated the docs over at source.android.com to reflect this reality.We will still make available as many as possible of the closed-source binaries for these devices, and Nexus devices will continue to have unlockable bootloaders. And, of course, GSM/HSPA+ devices are still supported, as are any other devices we’re able to support. We’ve simply updated the documentation to be clearer about the current extent of CDMA support.We are of course always working to improve support, and we’ll keep everyone updated as we make improvements. Thanks as always for your interest in AOSP!

Google will still support the Galaxy Nexus LTE, Nexus S 4G and XOOM CDMA, at least as long as the hardware is compatible with updated versions of Android. But it won’t be with the same direct support that GSM developer devices enjoy. This probably means that updates to the Galaxy Nexus will come through Verizon… just like all the other Android phones out there. Presumably that gives Verizon or any other CDMA carrier the option to either delay or ignore the update. This isn’t an agreeable position for many Nexus S, Galaxy Nexus and XOOM owners, as it sullies the “pure Google experience” that’s expected (if not explicitly promised) from a developer device.

The timing is suspect. the removal of CDMA devices comes just a day after AT&T’s reinstatement of Google Wallet on the Android Market. since Verizon customers can only access Google Wallet via a work-around, whatever tense relationship between the developers and the carrier seems to have been kept to the status quo. This could have been the last straw for Google, or it might be completely unrelated. Neither party seems willing to speak on the subject.

The Verge contacted Google on the subject and got this response:

Every day, Android developers openly distribute applications via Android Market. Google is also a developer within this ecosystem and we want to offer the apps we develop such as Google Wallet, so people have access to the full range of functionality offered by the platform.

It’s important to note that the three devices in question still have unlockable bootloaders, and that isn’t likely to change. ever. the Galaxy Nexus LTE, Nexus S 4G and XOOM CDMA are still valid as developer devices, in the sense that you can download Android code, compile it and run it on them without any barriers. Custom ROMs and other mods will not be affected. Even so, the sudden drop in priority support is certain to ruffle the feathers of serious Android enthusiasts, many of whom bought these phones and tablets based on that support alone. We’ll keep you updated on this story as it progresses.

Google ends full support for CDMA devices, including Verizon’s Galaxy Nexus

This Tablet PC Post was also found by:

    software updates to radio-cdma on galaxy nexus
    Tablet pc with cdma function