Yes, it's a 4.2.2 related issue not a custom ROM issue. I've played with 3 different 4.1.2 custom ROMs and it works.
This seems to match my own findings as well - most 4.2.2 use cases are resulting in similar issues (or instability in general).
Any chance this can be fixed for the future then, if it's not just the concept of "custom roms" at fault?
I hope devs say someting about this issue because I bought the game and I can't go back to 4.1.x due to compability issues.
I have a Samsung Fascinate (Galaxy S1) and am running 4.2.2 and have had no problems. It is not Cyanogenmod though, but a custom Android build called GeeWiz, and it uses a modified Samsung 2.3.5 kernel.
See there are many variables.
Why devs do not say anything about this issue? I wish I had downloaded the game instead of buying it... I'm just asking for a reply...
I'm only seeing this issue when I plug in a gamepad or put the phone in the docking station (Note 2, Stock ROM)... which probably means that the event handler is botched and will lock up if there's some kind of unknown event. Newere versions are bound to send new events, so that fits. On a more positive note: Shane has confirmed that they're planning on updating the input code, which should solve this issue as well.
Any news about this issue? There have been two updates but none of them resolves this compatibility issue. I'm still waiting.