11-30-2009 02:10 PM
Storm 2, 9550 with OS 126.96.36.1990
I have an app that uses a constant connection to receive push notifications from a server. The problem I am seeing is when this connection is active, if you try to load the voice dialing app it will hang while saying "Initializing, pleased wait." Once the connection in my app ends, the voice dialing app will finish loading and says "Say a Command." What is the voice dialing app doing that would cause them to interfere like this?
11-30-2009 02:46 PM
I would look for some synchronization issue? Does your code that waits for the push run withint a sybchronized block? Do you lock something like RuntimeStore?
12-01-2009 01:20 PM
See whether the Voice Dialing application attempts network I/O on startup. On way to find this out is to change the Event Log log level to Debug, then fire up the Voice Dialing application, and then scan the log for connection attempts.
12-01-2009 01:23 PM
Can I confirm that the 'hold up' you are seeing only occurs when loading the voice dialing app? Other things, like the Browser, for example, load up fine?
Have you tried using your application on the Simualtor?
BTW, I suggested the synchronized as a possible issue, becuase of the way the standard RIM supplied push listener code does a synchronized, as you can see here:
How To - Open a push listener connection
Article Number: DB-00434
How does this code compare with yours?
12-02-2009 12:26 PM - edited 12-02-2009 04:40 PM
Good try, but I would not have expected that to change anything either.
I'll admit to being a bit lost here.
One suggestion would be to attach the device to a debugger, change the Event Logging level to display Information messages and watch the Event log in the debugger window. No idea what you will see there, but maybe something useful.
Alternatively, create a really cut down version of your app, and see if the problem still occurs (what do I mean by really cut down - just listen and throw away for example). If the problem still occurs, this will be easy to give to RIM (or us here) to see if they/we can help. If it doesn't, then add the tricky bits from your app until it breaks. Sorry, this is clearly not an easy option!