cool glad it worked out. I didnt know it had been fixed since your response was "sorry i have no idea what that is."

How did samsung fix the bug? I thought the only way the NaN value could be declared was through a computational logic error within your APK. In fact I'm 90% sure of it, though I could be wrong.. So I'm really interested to hear what Samsung did to fix it, and what evidence did you actually have to isolate it to a "samsung bug".