You want to take a look at "net.rim.device.api.applicationcontrol", take a look at the classes and interface.
I have one application that sets permissions at startup, the main function creates and pushes a screen. In the screen's constructor I call super(); followed by a call to setupPermissions();
private void setupPermissions()
{
ApplicationPermissionsManager man = ApplicationPermissionsManager.getInstance();
int[] requiredPerms = new int[] { ApplicationPermissions.PERMISSION_MEDIA, ApplicationPermissions.PERMISSION_RECORDING, ApplicationPermissions.PERMISSION_FILE_API };
ApplicationPermissions perms = man.getApplicationPermissions();
boolean change = false;
for(int i = 0; i < requiredPerms.length; i++)
{
if(perms.containsPermissionKey(requiredPerms[i]))
{
if(perms.getPermission(requiredPerms[i]) != ApplicationPermissions.VALUE_ALLOW)
{
change = true;
perms.addPermission(requiredPerms[i]);
}
}
else
{
change = true;
perms.addPermission(requiredPerms[i]);
}
}
if(change)
{
man.invokePermissionsRequest(perms);
}
} Though I don't have it implemented I would like to implement ReasonProvider because it drives me nuts when a application requires a permission for something that seems totally unrelated to the application (such as a calculator that requires BlueTooth access. Why?).
As for what you need:
- Connection->PERMISSION_WIFI and PERMISSION_BLUETOOTH
- Inject events->PERMISSION_INPUT_SIMULATION
- read/write files->PERMISSION_FILE_API
------------------------------------------------------------
Three simple rules:
1. Please use the search bar before making new posts.
2. Kudo posts that you find helpful.
3. If a solution has been found for your post, mark it as solved.
--I code too much. Well, too bad.
