[NIGHTLY] "AOKP" For Droid 4 For MotoICS Leak
** FLASHING ROMS WILL VOID YOUR WARRANTY AND COULD POTENTIALLY DAMAGE YOUR PHONE **
This isn't so much a ROM announcement as it is a direction to find the unofficial nightly builds of AOKP for the Droid 4 (based on Motorola ICS leaks)
AOKP Nightly Download Link (ROMbot)
Download GApps Here (04/29 Goo-Inside GApps Link).
FLASH THE GAPPS.ZIP FILE AFTER YOU FLASH THE ICS.ZIP
WHAT do I need to run this ROM?
- Running a Motorola ICS leak (.206, .208, .211, etc)
- I recommend that you run Safestrap v2.00 to install this. Here's how to use Safestrap
And you can download Safestrap for the Droid 4 (v2.x for ICS-leak users) here:
Safestrap « Hash-of-Codes
WHAT can I expect to work right now?
- 4G and basic phone function
- All sensors
- Camera, Panorama and Face-unlock
- Video Recording
- HD YouTube
Current Known Issues [6/25/2012]?
- The CM9 built-in Wifi Tether won't work. You need to use the "Wifi Tether" app that's bundled into the ROM. Once you open it, hit [menu] and "Settings". Select "Change Device-Profile" to "Generic ICS".
- Wifi connection issue related to the stock TI MAC address being assigned to the wifi chip. I need to figure out how to reload the chip MAC from the eeprom.
- Currently, there is a bug in the rotation display of the phone. What I mean is, that when you take the phone and rotate it, the display will squeeze in on itself and then pop back out. This is a *known* issue and I'm working very hard to fix it.
- Data Connection app is better than it used to be (should be much easier to get a data connection), BUT it's still a work in progress. Not everyone will get data on boot. And it looks like I'm not honoring when user's select "LTE/CDMA" vs. "LTE/CDMA/GSM/WCDMA" in the settings. I'll try to dig into that as well.
- Bluetooth bug is still around (lol?) so be careful about leaving BT active when you don't have a device connected for now.
- CAPS LOCK key Inop
- HOME capacitive button Inop
- [06/24/2012] Hard keyboard cursor keys are mixed up.
WHO works on this?
Myself and @DHacker29 work as a team to build AOSP-based ROMs (and device setups) for several Motorola phones. Typically, I do the coding work in C, C++ or Java while DHacker maintains the blobs, runs merges with CM/AOKP sources, and solves device issues which require less coding.
WHAT is a "nightly"?
It's an automated build ran from a script. It basically: deletes the current set of output files, sync's with github, and then attempts to do a brand new build. It can break at times, in which case we'll fix it (usually this happens when there are framework changes which didn't get merged).
WHY would I want this?
- Since we work on several devices, this is how we decided to start keeping builds up-to-date. Rather than spend several hours a week on builds and uploading. This happens automatically every night around 2am PST.
- It's up to you the community to identify good "stable" builds.
Feel free to follow me on Twitter as I do sometimes make announcements there before I do forum postings:
Hashcode (@Hashcode0f) on Twitter
We maintain all of our code at github:
[ COMING SOON ]