I got cm-12.1 working. Or, at least booting.
It works with no sound, no hw acceleration and unfortunately, no browser. Chromium crashes with a ERROR :GL_OUT_OF_MEMORY : glBufferData: . It works in cm-12.0. I have uploaded changes for 12.1 on github. Building directions are the same. Just find the correct directories. I renamed some of the 12.0 ones to include 12.0 in the branch names.
I left out an important change to frameworks_base. This is from the README.md file. To deal with data/media and sdcard installs a change to frameworks/base is required. It was written by steven676. I have incorporated it here:
https://github.com/drmarble/android_frameworks_base/tree/storage-config-12.0
I have found that building as userdebug instead of eng makes the builds much faster. Quadrant scores doubled to ~1300.
Sorry about the difficulties with the local manifest. When I am modifying an existing tree I use git commands, eg:
git remote add drmarble
https://github.com/drmarble/android_frameworks_base.git
then
git fetch drmarble
This gets all my branches.
Finally git checkout drmarble/storage-config-cm12.1
This will get reset to the default repo branch when you repo sync (unless you have made uncommitted changes). Just checkout again.
This method is handy when you build for multiple devices on the same source tree. You can just checkout any changed directories for a specific device. I think that there are even better ways involving repo and repo branches. I have enough trouble understanding git. I use shell scripts for my builds and just put the checkout code in there. eg:
Code:
pushd kernel/bn/encore
git checkout sluo/encore-omap3-3.0.y-l-backports
popd
or for local branches
Code:
pushd frameworks/base
git checkout storage-config-cm-12.1
popd
pushd hardware/ti/omap3
git checkout no-omx
popd
Sorry about forgetting about frameworks/base.
---------- Post added at 12:15 AM ---------- Previous post was at 12:03 AM ----------
Just a warning. I disabled boot animation because we can't both optimize for art and animate a boot at the same time. It will just sit on a black screen for several minutes before informing you that it is optimizing apps. Plugging in a usb cable and running adb logcat will encourage you that it isn't frozen. I know that eng builds automatically allow adb as root on first boot. I think I managed to set it up for userdebug builds too so you don't have to authenticate on a blank screen.
