| | default policy preventing background app to notify user ?
Please Login to Remove!
I have a VoIP application (vmobile), running on OS5. It should, according to the developer, be able to notify the user if an incoming call arrives.
However, in some cases, it does not. The developer told me, they tested the functionality, and, it does work, however, they never tested it against a device tied to a BES. Their guess is, there is some policy stopping the program from notifying the user.
I have a very relaxed policy, most things are set to the default settings of the default policy, and, those things, which are not default dont relate to notification while locked.
What does not work:
If the device locks itself after 2minutes, and, the screen is dark, I will not get notified of an incoming call. The calling party will get an "unavailible" answer on the phone, and, if I later unlock the device, i will see (and hear) the call notification, even if it has been dropped minutes ago.
In all other cases:
Locked by the dedicated lock key
Or, locked by the security password, but screen accidentally on.
The notification works.
I changed the security setting of the program and its modules to even allow reset of the security timer, but, this does not make a difference. The program has all other permission set to allowed.
There is no application policy on the server.
I personally suspect no policy or BES related problem, rather something with the firmware, or, energy saving settings of the handheld.
Does anyone have an idea why the incoming call notification does not work in this case (which is btw. the most likely case: phone locked, and screen dark)?
And, if it is related to some policy, which of the 4xx settings i have to tune?
Posted via BlackBerryForums.com Mobile
Last edited by nobody7290 : 12-11-2012 at 05:38 AM.