As expected, today Google made a management release for Android 4.2 official at their breakfast with Sundar event, bumping the release up to Android 4.3 and introducing a bunch of new features and fixes. The update brings everything that Google alluded was coming during Google I/O, and a few more.

On the graphics side, the big change is inclusion of support for OpenGL ES 3.0 in Android 4.3. Put another way, Android 4.3 now includes the necessary API bindings both in the NDK and Java for ES 3.0. This release brings the numerous updates we’ve been over before, including multiple render targets, occlusion queries, instances, ETC2 as the standard texture compression, a GLSL ES 3.0, and more.

 

We’ve also talked about the changes to the 2D rendering pipeline which improve performance throughout Android, specifically intelligent reordering, and merging, which cuts down on the number of draw calls issued to the GPU for 2D scenes. This improvement automatically happens with Android 4.3 and doesn’t require developer intervention, the pipeline is more intelligent now and optimizes the order things are drawn and groups together similar elements into a single draw call instead of multiple. In addition like we talked about, non-rectangular clips have hardware acceleration, and there’s more multithreading in the 2D rendering pipeline.

Google has been trying to increase adoption of WebM and along those lines Android 4.3 now includes VP8 encoder support for Stagefright. The platform APIs are updated accordingly for the ability to change settings like bitrate, framerate, and so forth. New DRM modules are now added as well, for use with MPEG DASH through a new MediaDRM API.

 

On the connectivity side we get a few new features, first is the WiFi scan mode which we saw leaked in a bunch of different ROMs. This exposes itself as a new option under the Advanced menu under WiFi settings, and during initial out of box setup. This new scanning mode allows Google to continue to further build out its WiFi AP location database to improve WiFi-augmented location services for its devices.

Like we saw hinted not so subtly at Google I/O, 4.3 also includes support for Bluetooth low energy (rebranded Bluetooth smart) through the new Broadcom-sourced Bluetooth stack. This OS-level support for BT Smart APIs will do a lot to ease the API fragmentation third party OEMs have resorted to in its absence.

Likewise Bluetooth AVRCP 1.3 is now included which supports better metadata communication for car audio and other devices, as well as better remote control.

Security gets improvements as well, Android 4.3 moves to SELinux MAC (mandatory access control) in the linux kernel. The 4.3 release runs SELinux in permissive mode which logs policy violations but doesn’t break anything at present.

A number of other security features are changed, including fixes for vulnerabilities disclosed to partners, better application key protection, removal of setuid programs from /system, and the ability to restrict access to certain capabilities per-application. Lastly there’s a new user profiles feature that allows for finer grained control over app usage and content.

We'll be playing around with the new features on the new Nexus 7 as well as the other Nexus devices getting the update (Nexus 4, Nexus 10, Nexus 7 (2012), and Galaxy Nexus). Google has already posted the factory images for those devices as well if you're too impatient to wait for the OTA and want to flash it manually. 

Source: Google

POST A COMMENT

69 Comments

View All Comments

  • Fergy - Friday, July 26, 2013 - link

    I found 2.3 and 4.2 really underwhelming. Getting control over app permissions is something I wanted day 1 from Android. And a start towards a more secure Android via SELinux is awesome news. I look forward to using devices with bluetooth low power. Reply
  • kenyee - Friday, July 26, 2013 - link

    Bluetooth LE is a *HUGE* improvement. That's been severely holding back a lot of the health/exercise related apps and all the competitors (iOS, WP7, BB) have had it for a while now.
    I'm just annoyed this won't work on the older N7 tablets, but I guess my tablet needed an upgrade anyways...
    Reply
  • xdrol - Wednesday, July 24, 2013 - link

    Still no OpenCL? Come on.. Reply
  • lilmoe - Wednesday, July 24, 2013 - link

    Renderscript......... Reply
  • xdrol - Wednesday, July 24, 2013 - link

    Yeah, and I have even less portable code than with OpenCL.. Reply
  • Krysto - Thursday, July 25, 2013 - link

    Good point, but whatever. OpenCL 2.0 is where it's at anyway for heterogeneous computing, and I'd rather they'd just start with that, maybe in Android 5.1 or something, next year, because the spec has just been finalized. Reply
  • tuxRoller - Wednesday, July 24, 2013 - link

    Finally!
    SELinux took way too long to get here. You don't get a huge performance hit with it, and running it in permissive mode with logging being sent to Goog so they can start developing appropriate policies (which, frankly, shouldn't be hard given that each installed app asks for its appropriate permissions).
    The improved drawing pipeline is welcome as even their flagship phone can stutter occasionally.
    Reply
  • watersb - Friday, July 26, 2013 - link

    I totally agree. Reply
  • EnerJi - Wednesday, July 24, 2013 - link

    Google, where is the find my phone / remote lock/wipe capabilities? Windows Phone, BlackBerry, and Apple all have this feature (some of them for years). This should be a core OS feature, not an app. Reply
  • thesmoosh - Wednesday, July 24, 2013 - link

    Check out the Google Apps Device Policy app. Covers all the scenarios you outlined (thought it may require Google Apps, I'm not sure). Reply

Log in

Don't have an account? Sign up now