This shows you the differences between two versions of the page.
android:lpermission_model [2017/02/09 18:32] bill_coggins created |
android:lpermission_model [2017/05/10 16:37] (current) bill_coggins |
||
---|---|---|---|
Line 5: | Line 5: | ||
As such, if we change our target build to Jelly Bean (API 23) or higher then we must implement the new permission model. | As such, if we change our target build to Jelly Bean (API 23) or higher then we must implement the new permission model. | ||
- | Our current Android app permissions are predominately Normal. However all of our apps need 2 Dangerous permissions: ACCESS_FINE and WRITE_EXTERNAL. Code will need to be added to handle checking for and requesting access for these permissions. | + | ====== Permission model in Agtek Products ====== |
- | One app (SmartGrade) asks for a permission that is no longer available: READ_LOG. This permission was necessary for several GPS drivers. A solution to this problem is still outstanding. | + | Our current Android app permissions are predominately Normal. However all of our apps need 2 Dangerous permissions: ACCESS_FINE and WRITE_EXTERNAL. Code will need to be added to handle checking for and requesting access for these permissions. Note that the user can revoke access at anytime. |
+ | |||
+ | One app (SmartGrade) asks for a permission that is no longer available: READ_LOG. This permission was necessary for several GPS drivers. //**A solution to this problem is still outstanding.**// | ||
+ | |||
+ | Currently the access to GPS is created immediately (AppBaseActivity onCreate). We will need to add the check here plus we'll need to add **m_locMgr** null checks to **onResume** in //SmartDirt// and //SmartPlan//. The other apps should be ok. Any startup code will have to be called from both **onCreate** and the Permission Check dlg return in the case of having to ask the user. If access is refused, then the apps will be expected to close. | ||
Line 73: | Line 77: | ||
} | } | ||
</code> | </code> | ||
+ | |||
+ |