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-16-2013 07:03 PM
not sure what the hard limit is. some of the highest-priority threads in the system are part of the io-audio driver (most are 50, and at least one interrupt thread is 51).
definitely would be interesting to see code that works ok on playbook but not a dev alpha (which has a better cpu).
It looks like setting the thread priority for the tone generation thread to 52 solves the problem. Wonder why a priority of 50 works on the PlayBook.
01-17-2013 12:02 AM - edited 01-17-2013 12:03 AM
playbook audio drivers are probably running at a different priority.
when you have the time, I'd still like to run your problematic code (or an equivalently cpu-intensive generator) by the audio guys
I would hate to see your app stop working reliably if someone bumps the audio driver priority up in the future.
02-20-2013 08:44 PM
02-20-2013 08:48 PM
02-21-2013 07:37 AM
02-21-2013 08:12 AM
02-21-2013 08:32 AM
02-21-2013 09:11 AM