I\'ve found that one of my application posted on the market produces weird results on some phones. Upon investigation it turns out there is an issue with one function which
This was a JIT bug that was active in the JellyBean source from late 2012 through early 2013. In short, if two or more double-precision constants that were different in the high 32 bits, but identical in the low 32 bits were used in the same basic block the JIT would think they were the same, and inappropriately optimize one of them away.
I introduced the defect in: https://android-review.googlesource.com/#/c/47280/
and fixed it in: https://android-review.googlesource.com/#/c/57602/
The defect should not appear in any recent Android builds.