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.
09-12-2013 07:37 PM
09-15-2013 08:54 PM
There is documentation for this: Here,
Personally I couldnt get the Push Collector working but the Xandroid works according to others.
I tried making a UI + logic seperated app and tried invoking the logic part on system started but couldnt get it to work too.
If your headless app needs long running and is non triggered u need to submit a form at https://developer.blackberry.com/jam/headless/
I sure hope the internal devs release a simple start on system start hello world sort of example, both sample apps are too complicated and try to squeeze too many different features together
09-22-2013 07:12 AM
It's a strange idea to use a predefined TCP port in a headless service. What if another applications will use the same port all the time? Applications will work incorrectly.
09-22-2013 08:31 AM
09-22-2013 08:32 AM
09-22-2013 08:44 AM
I'd rather sent a server port from the UI part in the invocation request )
As I see _sys_run_headless shows that application can be possibly run all the time, but system can stop it eventually, restart and so on. Is it right?
"Long-running headless applications require the _sys_headless_nostop system permission to run at all times." - why should I ask BBRY for approval? Will this give me garanties that my headless part will work all the time, even on low memory due to another applications?
09-22-2013 08:54 AM
I am facing to problem of "failed to bind to port" at work too often due to some one decided to use predefined port thinking that "server and client must have negotiate with some predefination".
Would you like to get a negative reviews of the program due to someone use the same tcp port? BBRY should not provide such a REALLY BAD example of the IPC.