I think it was on this very list that we determined that most (all?) Samsung phones crash when you use SoundPool. The short answer is that you're not going to be able to change the phones out in the wild at all.
In this particular case, though, threads are involved, so there's a significant chance that you're not reasoning about the order-of-access issue correctly -- and that it's happening in an order you don't expect. I am not enough of a Java expert to answer that question definitively -- you'd be better off asking about it on a Java forum, the android-developer forum, or StackOverflow. But seriously, the "flavor" of the bug as you describe it isn't at all a platform-specific bug; it's a timing/threading bug. Tim On 9/26/2011 3:48 PM, sebastian_bugiu wrote: > I have an application in android market that does not work on htc > desire and I am positive the issue is not in my code. Basically I have > a private static final field that is initialized to a reference to an > object and yet whenever I access that object from another thread it > throws a NullPointerException even though it is initialized. > > It works in the emulator but I have not tested the application on many > phones. But on those that I tested it works. > -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
