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-05-2013 04:50 PM
I believe I reported this same issue on the Dev Alpha A a while ago: http://supportforums.blackberry.com/t5/Android-Run
But now I'm seeing it on my Z10 (software release 10.0.10.90), so it definitely needs a solution!
Is there an update on this issue? Is it fixed in 10.1?
06-03-2013 09:27 AM
Today I received a fresh error report and this time the Build.DISPLAY is 10.1.0.103
I thought this issue is fixed in 10.1 but I have a customer who originally reported this from 10.0 and seems he upgraded to 10.1 and still has this problem.
Any update on this???
06-03-2013 10:04 AM
In my experience, once the problem appears, it's there until the device is "security wiped", and this held true for when I upgraded from 10.0 to 10.1 - the damaged application remained broken in 10.1. However when I security wiped the 10.1 device and reinstalled the app I was unable to get the problem to reappear.
Hope this helps!