Android 4.4 KitKat KRT16M Release
The time has come! The newest iteration of our favorite mobile operating system is here, and it's now available for the Verizon Galaxy Nexus in Shiny ROM form. It seemed for, at least a moment, that the Galaxy Nexus was doomed as it received its EoL from Google. Of course, thanks to the developer community, that is not true, as we are about to see.
Android 4.4 KitKat has brought a multitude of changes to the OS. It'd be silly for me to try to list them all, so instead I'm just going to suggest that you check out either Droid-Life or AndroidPolice's comprehensive coverage of the update. If you haven't been following Android news lately, I'm sure you'll be pleasantly surprised.
For changes across builds of the ROM, head to the download post and checkout the changelog there.
This build is pretty much bone stock - in fact, it is odexed, so mods will not be compatible for the time being. No mods will be available for it right away, but information about mod availability will be out soon. Please do not flash mods for older builds with Android 4.4.
GAPPS ARE INCLUDED AND NOT REQUIRED.
You can continue to use SuperSU 1.65 to enable root in Android 4.4. The installer for this build will not keep root to avoid issues, so you will need to reinstall the SuperSU root package if you want to be rooted.
Please note, if you are install the 11/5 build or later of Android 4.4 KitKat and you were previously rooted, you should not need to reflash the SuperSU root ZIP.
The following information details what you must do prior to installing Android 4.4 KitKat. Failure to follow these instructions may result in a failed installation.
Please install this build only from ClockworkMod Recovery 188.8.131.52. You can flash ClockworkMod Recovery 184.108.40.206 using the flashable ZIP provided in the OP. You can flash it in any custom recovery like any other ZIP. After flashing it, reboot into recovery mode again.
The following information outlines some actions that you are recommended to take before installing the build. These are not required, but may reduce the amount of problems you run into.
- Only install to a device with sufficient battery power.
- Install the latest Verizon Galaxy Nexus radios before flashing.
- Install the latest Galaxy Nexus bootloader before flashing.
- Back up all app data you wish to keep
- Back up your system in recovery before modifying it
The following instructions are specific, step-by-step instructions for installing the build from internal storage, provided you have fulfilled the prerequisites above. (You can also install via ADB sideload, simply use that method instead of choosing from the sdcard.)
- Copy the ROM and any other required packages (such as SuperSU) to the root folder (/) of your internal storage.
- Reboot into ClockworkMod Recovery 220.127.116.11.
- (This step deletes all of your app data - make sure you back it up if you want to keep it. Your internal storage will not be affected.) Select 'wipe data/factory reset' then select 'Yes - Wipe all user data'
- Select 'wipe cache partition' then select 'Yes - Wipe Cache'
- Select 'advanced' then select 'wipe dalvik cache' then select 'Yes - Wipe Dalvik Cache'
- Return to the main menu by selecting '+++++Go Back+++++' then select 'install zip' then select 'choose zip from /sdcard'
- Select '0' and then select 'baldwinguy77_toro_aosp_110513-015450-signed.zip'
- **For root** repeat steps 6 and 7, but select the SuperSU installation ZIP instead of the ROM ZIP
- Return to the main menu and select 'reboot system now'
- **IF** ClockworkMod recovery prompts you with any questions, select 'No'
The only major bug right now involves an interaction between the new webviews and OpenGL. In some apps (e.g. the AOSP browser, Google Search) there are black boxes rendered randomly throughout the content. This is a consequence of incompatibility between our outdated GPU drivers and new surfaceflinger code. It is being actively worked on.
Another, more inconsistent bug, is a random reboot issue. This is 99% likely related to the bug above, so fixing that one should fix the reboots for the most part. As an aside, I had 3-4 reboots annoyingly close to each other at first, but once I got everything installed and just allowed the device to "rest" for a little, it seems to be very, very smooth.
As always, please report any and all bugs that you find! If you are having an issue that seems to be isolated to your device or setup, please consider PMing me in addition to posting in the thread. I may not catch all posts in the thread due to logistical shortcomings, but I will certainly read and respond to all PMs.
Lastly, I highly recommend that you add any bugs you consider to be significant to this Google Drive document (huge thanks to user xolanir!) so that we can keep some sort of list going. For now, you'll have to request permission to access via your Google account to post to the document. I'm hoping to get some sort of more systematic method up and running, but I'm juggling a lot right now. Thanks to everyone for your patience and understanding!
Edited by baldwinguy77, 09 November 2013 - 09:15 PM.