Loosing touch events

Hello!

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?

With best regards,
Alexander

As I know, when we use Accelerometer in application, touch events will be lost sometimes on bada platform. Does you application use Accelerometer ?

Yes, my app uses accelerometer. Is it any solution to avoid the problem? May be to switch off accelerometer before scene change

Sorry, I haven’t found a solution to avoid this issue. Could you make a simplest demo which use both acc and muti-touch, and reproduce this bug?

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.

Hello!
I created simple demo with this bug. I also posted questions into samsung support Russian(http://developer.bada.com/badaforum/board/thread/view.do?boardName=002&messageId=44083&curPage=1&searchType=title) and English(http://developer.bada.com/badaforum/board/thread/view.do?boardName=bada-cc&messageId=44128&startPage=1&curPage=1) forums, and into Samsung Premium Support Service. Now I’m waiting for the answer. If I get something, I’ll post 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

Thanks very much. Hope samsung can fix this bug as soon as possible.
Alexander Trutchenko wrote:

Hello!
I created simple demo with this bug. I also posted questions into samsung support Russian(http://developer.bada.com/badaforum/board/thread/view.do?boardName=002&messageId=44083&curPage=1&searchType=title) and English(http://developer.bada.com/badaforum/board/thread/view.do?boardName=bada-cc&messageId=44128&startPage=1&curPage=1) forums, and into Samsung Premium Support Service. Now I’m waiting for the answer. If I get something, I’ll post 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

This is just to verify that the issue is random and produce when accelerometer and touches are used at the same time. Lets wait for it solution.

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…

Ok,hope this issue will be resolved in the next sdk!

Ok,hope this issue will be resolved in the next sdk!