Controller notifications of errors (parameters out of range, etc), will need to be stored to be displayed in the notification bar. Errors communicating will also need to be stored to be intermixed with the controller notifications.
Store the errors and notifications inside a database table. The fields will be an auto id, current system milliseconds, error message and read field.
The table will allow for creation of the large notification messages that are on ICS and later.
The notifications will be persistent unless they are clicked on (which will open the app and mark the errors as read) or unless they are cleared via the notification bar. If you simply open the app up, it will not clear the notifications.
You can open up an Errors section of the app that will display a history of the errors and notifications that were received. You will have the ability to clear the history from there.
This implementation will be handled in multiple phases.
Stage 1
Creation of error table
Storing errors inside table
Displaying notification based on errors inside table
Launching app from notification to clear errors
Use IntentService to clear the errors and then launch the app if necessary
Set IntentService as DeletePending Intent
Stage 2
Displaying error history from app
Deleting error history from app
Stage 3 ( #61 Notifications )
Creation of notification table
Display notifications inside app
Create/Delete/Update of notifications inside app
App inserting in errors table based on notifications
Controller notifications of errors (parameters out of range, etc), will need to be stored to be displayed in the notification bar. Errors communicating will also need to be stored to be intermixed with the controller notifications.
Store the errors and notifications inside a database table. The fields will be an auto id, current system milliseconds, error message and read field. The table will allow for creation of the large notification messages that are on ICS and later.
The notifications will be persistent unless they are clicked on (which will open the app and mark the errors as read) or unless they are cleared via the notification bar. If you simply open the app up, it will not clear the notifications.
You can open up an Errors section of the app that will display a history of the errors and notifications that were received. You will have the ability to clear the history from there.
This implementation will be handled in multiple phases.