Cause it's not specific Samsung 4.1.x device
It would be really weird if Samsung and Motorola did the same error independently on different OS versions, wouldn't it?
In the meantime we got the device and I think we are closing on a fix for that so it would be best if we would wait with your Motorola issue to see if it gets accidentally fixed by that as well
Filip