BeBuzz 10 Pro Version 2.0 (Now Headless)
After a long and tedious development and testing phase we are happy to announce that BeBuzz 10 Pro Version 2.0 with headless support is finally available!
BeBuzz Pro 2.0 is only available for OS 10.2.1 and later
This update is free for all users of BeBuzz 10 Pro. Download at BeBuzz 10 Pro - BlackBerry World
Changes and new features since version 1.5:
- Added headless support (no more need to keep running BeBuzz all the time)
- Added support for calendar events/reminders
- Added 30 more LED color combinations
- Now detects your device's notification profile (normal, silent, all alerts off etc) and mutes led, sound, vibrates accordingly
- Removed popups (due to incompatibility with headless support; please revert to BB10 native toast notifications)
- Removed silent mode switch (replaced by native profile detection support)
Please post all feedback like questions, suggestions and bug reports for BeBuzz Pro 2.0 here!
Problems with BeBuzz stops working, read below:
As some users have correctly mentioned headless apps are limited to a maximum memory usage of 3MB. (This is not the value you see in the device monitor.) When a headless app goes over this limit it will crash (be terminated).
We have very carefully optimized BeBuzz to absolutely stay below that limit at any time. We have done many many many stress tests to make sure this never happens. Obviously we cannot test all situations that might happen out in the wild.
If BeBuzz stops working at any point you can help us make sure this is not due to this limit by doing the following:
- Open the Device Monitor. Go to 'Memory'. Is BeBuzz in the list? If it is, how much memory use is it showing?
- How many contacts have you added to BeBuzz?
- How many e-mail accounts do you have on your phone?
- Do you have LED/sound or vibrate enabled for calendar events in BeBuzz?
- Do you have the coverage indicator LED enabled in BeBuzz?
If BeBuzz isn't showing in the Device Monitor, launch the BeBuzz icon, then close the active frame again. Now check the Device Monitor again.