Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
05-13-2010 10:34 PM
We are actively working on the solution and are trying to get a fix out as soon as possible. We understand the impact and importance of this issue and it is a top priority.
Now for some background information so that you aren't left in the dark and also have a better understanding of the root of the problem.
05-27-2010 08:16 AM
I thought I would provide an update. We have successfully completed our fix for the frozen navigation issue and we are currently going through our rounds of testing. We should have an update available for download fairly soon. How soon will all depend on how little we find during our testing cycles.
Thanks again for your patience on this issue
06-29-2010 09:48 AM
How are you guys getting on with this? Have you got a rough ETA yet?
We have the issue resolved from the development side now... there was a bit of a hiccup where we also found some issues with Menus in a similar situation.
We are just trying to get the final testing fit into the testing group's cycles. Most folks are all consumed with testing BlackBerry 6 at the moment so unfortunately I don't have an ETA for you yet
08-10-2010 10:01 PM
I figured I would give an update on this topic. The latest patch released to support BlackBerry 6 includes the patch to resolve the hanging issue with focus based navigation mode.
You may want to try out the patch to ensure that it resolves your issues.
01-12-2011 09:05 PM
any work around for Blackberry 5?
in case of have patch worked on Blackberry 5 simulator, may it able to run on existing Blackberry 5 device? or we have to upgrade device too?
04-11-2011 09:22 AM
Tim we have installed WebWorks 2.5.1 for Visual Studio and are still experiencing this issue. We don't have a deadlock, but there is a significant delay in UI response from trackpad.
04-11-2011 06:52 PM
Is the delay showing up on both 6.0 and 5.0? Or just 6.0?
We have made some improvements on the focus based navigation mode coming up in the next release of the SDK. Mostly these improvements are surrounding mixing trackpad with touch navigation like what is found on the Torch.
We also have a group working on speed improvements for Navigation mode. We have found some places where we can significantly speed it up. We are just working on what is the best way to implement these changes.
04-12-2011 09:19 AM
Tim, we resolved the problem using information from your Peformance Tip on DOM updates. In our application, we load a single main page.
If we get and load data in the body onload event, trackpad navigation is fine. If after loading the main page, we load data from a button click and update our data container div, the trackpad navigation is very sluggish as moves and clicks are delayed in the event processing queue. The more data we return the more poor the response.
We format all of our html on the server and inject it into innerHTML in one shot. Using your perfomance tip of removing our container div from the DOM, filling the container with content, and then injecting back into the DOM solved the problem.
The issue was worse on 6.0 than 5.0 devices. Thanks so much for the tip!