The problem with the CM project is most of the devices it tries to support are not open source. What I mean is that the drivers for the radio, GPU, audio, etc. chips are not available in source form like Android itself (via AOSP). In order to compile a ROM for any device, the developers have to rely on binary blobs ripped from an official update or a different device. Unfortunately, that means bad support for devices that don't get updates by their manufacturer.
Case in point - Samsung Galaxy S2. The S2 had an official ICS ROM release by Samsung and devs managed to get a stable build of CM9 running on it. However, as of now there is no official JB update for the S2 and CM 10 is far from stable on that device. There are problems with the Yamaha sound chip (low volume), problems with the graphics chip (Hardware Composer), USB, TV-out, etc.
I am really hopeful about the new Nexus devices though. The Nexus 10 is the most OSS friendly Android device I've seen - everything except the GPU driver is available as open source.
Yep, I bought an HTC One S with the same issues. I've learnt my lesson- my first Android phone was a Nexus One so I didn't know how annoying it is. I'm buying a Nexus 4 and selling the One S.
There is a list of known issues with the latest nightlies[1]. I was talking about the international version of S2 (i9100), because that is what I tried CM10 on a few weeks ago.
Case in point - Samsung Galaxy S2. The S2 had an official ICS ROM release by Samsung and devs managed to get a stable build of CM9 running on it. However, as of now there is no official JB update for the S2 and CM 10 is far from stable on that device. There are problems with the Yamaha sound chip (low volume), problems with the graphics chip (Hardware Composer), USB, TV-out, etc.
I am really hopeful about the new Nexus devices though. The Nexus 10 is the most OSS friendly Android device I've seen - everything except the GPU driver is available as open source.