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.
01-03-2014 04:16 PM
Hello everyone, this is my first post and I'm hoping to find a resolution to a recent problem that I have encountered. I have an android project that supports api level 9 to api level 19. The app uses the v7 appcompat support library which I need for backwards compatibility. I use actionbarsupport and everything works as expected on both android and fire os, but when I add blackberry nature to the project and run the app on my playbook(os version 22.214.171.1248) I get strange unexpected behavior. The orientation will automatically rote from portrait to landscape and then the actionbar will disappear leaving my app in a state were it is no longer navigable. Can somebody help.
Solved! Go to Solution.
01-06-2014 04:09 PM
Thanks for stopping by the forums!
I'm not sure if I can give you an exact answer, but here is some information that may prove useful.
Playbook is running a (very) old version of the Android Runtime (Gingerbread). That version does not have access to native code as you would on OS 10.2.1, nor does it have the wealth of improvements in the newer OS. On top of this, it can only successfully run code from SDK 10 and below.
Your specific issue could stem from either an incompatibility with the information above, or an unresolved bug in the Playbook OS.
My suggestion would be to try out the new 10.2.1 OS and see if the problem persists. If it does, you can file a bug report here and our devs can have a look.
01-07-2014 06:13 PM
Thank you for your response, I appreciate you taking the time to respond to my query. I have now resolved this issue and unsurprisingly it wasn't a blackberry issue but an android one. The problem was with revision 18 of the appcompatv7 library. Once I updated to revision 19 the issue that I was having was corrected. This issue was an issue that effected all gingerbread versions of my app and not just the blackberry version. I hadn't noticed because I haven't tested the app on a gingerbread device in a few weeks and I hadn't received any feedback from users.
I don't plan to update the os on my playbook because I would like to support older devices too and in this case if I had an updated os I might not have found this issue.
01-08-2014 11:53 AM
Awesome! I'm glad you found the solution.
Let me know if you need any more help