Google Galaxy Nexus ("tuna")

Galaxy Nexus Specifications
Codename tuna
Vendor: Google
Type: Phone
Also known as: maguro | toro | toroplus 
Platform: TI OMAP4460
CPU: 1.2 GHz dual-core  OMAP4
GPU: PowerVR SGX540
Bluetooth: 3.0+HS
Wi-Fi: 802.11 a/b/g/n
GSM freq: 850 900 1800 1900 MHz GSM/GPRS/EDGE | 850 900 1700 1900 2100 MHz UMTS/HSPA+
LTE freq: not supported
Main camera: 5 MP (flash: LED)
Secondary camera: 1.3 MP
Peripherals: A-GPS / MHL / NFC / capacitive touchscreen / 3-axis accelerometer / 3-axis gyroscope / barometer / digital compass / proximity and light sensors / dual microphones


Supported Unlegacy Android Versions: aosp-4.4 | aosp-6.0 | aosp-7.1

Get latest Galaxy Nexus builds


How to install Unlegacy Android on the Galaxy Nexus

Source code



If you have issues or run into trouble please take a look at our "Frequently Asked Questions"

Special Notes

The first public build has something exclusive for the Galaxy Nexus, yet unseen on any other OMAP4 device: all carveouts reserved for Ducati (the multimedia subsystem of OMAP4, responsible for hardware-accelerated video decoding, encoding and camera functionality) have been switched over to CMA.

A few words for those who see CMA for the first time:

"The Contiguous Memory Allocator (CMA) makes it possible for device drivers to allocate big contiguous chunks of memory after the system has booted.
The main difference from the similar frameworks is the fact that CMA allows to transparently reuse memory region reserved for the big chunk allocation as a system memory, so no memory is wasted when no big chunk is allocated.
Once the alloc request is issued, the framework will migrate system pages to create a required big chunk of physically contiguous memory."

This means that a total of 996 MB physical memory is available to the system, while keeping Ducati fully working - this is a huge step forward, coming from the 694 MB available in the last factory image released by Google (Android 4.3).

While CMA was just recently implemented for this device, thanks to one of our developers (let's just call him Luden), it's quite stable: even under heavy memory pressure, the system manages to free up the required memory in order to start up Ducati and launch the requested multimedia functionality in a few seconds at most.