Sometimes my application loses touch events after scene replace or when the app starts (none of the layer on the scene get touches). The bug is only on Bada devices (1.2 and 2.0) (on ios devices and win32 all works fine). To cure the issue is enough to switch off and switch on device screen with back button.
Did anybody face such kind of problem? And could you give me a piece of advice how to avoid it?
Our QA team can’t find steps to reproduce the bug. It reproduces from time to time. I think there is no sense in demo because we don’t know the bug reasons. If I get any new information about the issue, I’ll note about it.
I think this is the bug of bada system. So we need to sort out a simple demo to give a feedback to samsung.
Alexander Trutchenko wrote:
Our QA team can’t find steps to reproduce the bug. It reproduces from time to time. I think there is no sense in demo because we don’t know the bug reasons. If I get any new information about the issue, I’ll note about it.
PS I can’t attach a .rar file with the demo (size 3-4 MB). Write “413. Request entity is too long” when I try to post it. So I add only description file for Samsung, download the demo project from forums
Hi all!
I got the answer from Samsung Premium Support:
We apologize for the delay caused,we could simulate the issue and submitted for detailed analysis and the defect number is B0100405587. “Frequent attach and detach listener to SensorManager causes whole screen to freeze”. It would be published in the following link once the fix is done. http://developer.bada.com/badaforum/board/thread/list.do?boardName=notice
There is still no defect with this number at the link. So we are waiting…