I’ve had a similar problem: on Android 4.4.2, hit detection for touch events works fine; however, on Android 4.0.3, I’m getting unpredictable results.

Sometimes, I have the problem you reported where touch events are firing on display objects that aren’t beneath the touch location (some object always seems to be hit, and it doesn’t seem related to its position relative to the touch location). However, the majority of times I’ve tried it on Android 4.0.3, a touch event never fires, even if an object appears beneath the touch location.

I’ve traced the issue to createjs.Container.prototype._getObjectsUnderPoint (Stage inherits from Container). Without the above touch fix, x and y passed into this function are always 0, so the touch fix is required. In the case where no events fire, _getObjectsUnderPoint seems to be returning null always. I can only *assume* that in the case where events are firing erroneously, the function is returning objects it shouldn’t be (false positives).

I’ve further traced this to the way the function performs hit detection i.e. by drawing each child to a canvas (with appropriate transform matrix), and then testing whether the alpha channel is > 1 (see _testHit). For some reason, this is going wrong on some Android versions. I’ve not been able to determine why, so my rather unsatisfactory workaround is to replace this hit test mechanism with a faster, but more rudimentary hit test where I assume each child display object is a rectangle. I obviously have to take scaling and registration points into account. I can post this somewhere if you’re interested?