The rest of the TARE classes use pure Android Fragments and will have an
issue trying to create an androidx Fragment, so switch from using an
androidx Fragment to an android Fragment.
Bug: 158300259
Test: manual
Change-Id: I4c27198a66bd51b3822421116b46ae3d80d589ff
Implements methods that update the AlarmManager Global Settings String
when the user confirms a value in the Dialog. updateAlarmManagerValue
takes the key of the factor being edited and the edited value enterd by
the user in the dialog assigning it as the current value of the key.
This a new string is then rebuilt with the updated values and assigned
to be the new Settings Global String.
Bug: 195056102
Bug: 195055895
Test: Manual
Change-Id: I5776822c665bdfa052f23099d367ba8cf29743df
Takes the AlarmManager csv string and parsees it for key:value
pairs. These key value pairs are then used to fill in information that
the DialogFragment class needs to display information. An ArrayMap is
used to initialize and store a key and the values associated with it
through a data object class. This data can be retrived in updated by
providing only a key.
Bug: 195056296
Bug: 195056102
Bug: 195055428
Test: Manual
Change-Id: Ia11f41bdd1790f7f3483d33148c251c58243e890
This CL is the base framework for creating and adjusting TARE factor
values. TareFactorDialogFragment sets the basic outline for a factor
that uses a DialogBox to adjust the value. It takes the "title" or name
of the factor, the key that will be associated with the factor, and an
initial value for the factor; then sets up everything so that the factor
value can be easily changed and stored. These factors are also
registered into the settings observer class.
Bug: 195055619
Bug: 193238774
Test: Manual (Made a temporary class instance of the DialogFragment and
showed it in inactive apps onResume())
Change-Id: I3bb67717175e70eab3bbb11f4a42ee63a42f60bc
