[DEV][WIP] CM9/Ice Cream Sandwich

I have been working on porting CM9 to the VS910. So far I have gotten it to boot to the lock screen.

What Works

• Boot animation
• Lock screen
• SurfaceFlinger
• logcat/adb shell
• 3d accel is half working. I have gotten SurfaceFlinger to load up and interface the proprietary drivers (from GB) correctly, but HardwareRenderer (java framework) fails because the drivers don't give up a valid config.

What Doesn't Work

• Touch screen
• HardwareRenderer (fails because HardwareRenderer.chooseEglConfig() returns null value)
• Everything else

Currently this ROM is totally unusuable for anything except for development. At this point, I do believe it is possible to get CM9 running, but it will take a good bit of developer effort. It would be helpful for any other developers around here to give some insight on the errors that come up in the adb logs.

How To Build

1. Follow Google's instructions for setting up a Linux system or VM for Android AOSP building
2. Follow CM9 build instructions up to brunch command
3. git clone git://github.com/andyichr/makerom.git to a location, such as ~/android/makerom
4. Overlay the files in ~/android/makerom/cm9-system/overlay onto the cm9/system directory (this adds vs910 brunch)
5. Adjust values in makerom.sh to match your own paths (MAKE SURE TO POINT IT AT A VALID KERNEL --I didn't include instructions for building a kernel)
6. Adjust values in makecm9.sh to match your own paths
7. Run ~/android/makerom/makecm9.sh to build cm9 (this takes a long time, depending on your system)
8. If build is successful, run ~/makerom/makerom.sh which will output a ROM which may be flashed to the device for testing

This is very rough work, but it proves that the basic parts of CM9/ICS do function on the Revolution. The cyanogenmod developers have already added some patches to the android source which allow ICS to run using video drivers from Gingerbread. This means it should be possible to get things working.

The current major problem with this ROM is that the HardwareRenderer does not initialize. Immediately after this, the main trebuchet process is killed and the system reboots itself after a while.

I will be happy to do what I can to support the process of porting CM9 to our phones. I read that a couple of other devs may be looking into porting CM7, but I think focusing on 9 might be more worth the effort, since we already have Gingerbread.

I have also attached a logcat to this post which should give developers some idea about what exactly is broken, which will lead to the first steps of debugging and porting.

Any interested developers should fork my repo on github (git://github.com/andyichr/makerom.git) which has the build scripts and patches.

That's about it for now. I very well may have left out some steps along the way. If you try to follow this process and it doesn't work out, let me know and I'll help you out.

ROM Download (very broken --only use for testing and development)

http://www.multiupload.com/GI0MLQYTE0 - Flash this if you want to see ICS boot to the lock screen or help test/debug. It's not useful for much else at this point.

We're getting there! I've already patched the android egl framework code slightly and built a kernel. CM team already patched frameworks/base for 2.3 video drivers. We'll patch what we have to to get this thing running! I am pretty busy but I will follow this thread and I hope for this to be a collaborative, transparent porting process! Good luck!

Hey guys n gals, I submitted CWM to koush today for a official build. And CWM Touch will be available once koush does his thing, or hets his automated stuff completed on builder. finished lol.

Hi All,

I'll give you a quick update on what's going on. I spent the weekend building and testing a build that has more support for our msm7x30 hardware. I did get the EGL problem out of the way, but the kernel is complaining about kgsl page faults. I believe this is because the build I have is using the gralloc.msm7x30 library built by the msm7x30 common config where we probably need to use the gralloc.msm7k library taken from a GB build because the drivers, firmware, and kernel are from GB.

Regarding the genlock support that thecubed mentioned, I found a CM build flag to turn off genlock support in the android build, which should allow us to use a kernel that doesn't have the genlock device driver. That said, I found a fellow developer named Isaac who is doing some great work on the Motorola Triumph. He's got a GB kernel that the applied genlock to. Looking at his work, it should be possible for me to do the same with our kernel. So, even though we may not _need_ genlock support in our kernel, it may be an easy win to get anyway, and it will make our kernel more ICS friendly.

From here, the next step I am going to do is merge what I can from Isaac's work (kernel and android device folder) into my own work. I'll also work on getting android to use our gralloc.msm7k rather than the generic msm7x30 one. It's not immediately obvious how to do that in the Android build config files, nor does it work to simply substitute our prebuilt library in system/lib/hw/.

Another thing -- beamer is sending me an extra phone of his for me to test with. This will help me tremendously as I won't have to backup my daily driver phone, take it apart, and reflash it every time I test a CM9 build. So, thanks a zillion, beamer! Your generosity will increase the efficiency of my process at least two-fold.

keynith said:

Is anyone actively working on this?

Sent from my VS910 4G using xda premium

Click to expand...

Click to collapse

I still need to finsh that repo so others can take a stab at it.

I been working on RIL with CM7, which will need to be working for CM9 too.

Not sure about dead dead but I just had a new baby and finished up a semester of school and also started a new day job so I just haven't had time for any new contributions. Also my testing phone is in an awkward state with ext4 partitions and an ext4 recovery but we have no actual working ext4 roms (my ics rom included). So I have to do a bit of work to even get back to regular testing.

That said I am not "done" with this phone by any means and also things have settled down in my life a bit and I won't sign up for any more classes until fall at the earliest.

Taking all that into consideration, this is something I do for fun and probably most other devs do it for fun too so you really just have to see what developers and hackers put out and be happy with that. When there are expectations about what will be released in the future then it just becomes a job that doesn't pay very well. My rate in the real world is good so I don't really need this type of open source "internship" if you will. I just want to give you all some insight into a developer's thought process on this type of thing. In other words just be happy with what is out already and hope, but don't expect, for new contributions.

Sent from my VS910 4G using xda premium