d0a3929327
This commit moves knowledge of the upper / lower bounds for valid manual date suggestions to (internal) API calls. It adds a test to confirm the API calls are used to configure the date dialog. Further, it removes redundant filtering from the client that would prevent suggestion calls being made if the settings UI considers them invalid. Year bounds are already used to limit the UI entry, and the system server will return false from the service call if the suggestion is invalid, though the SettingsUI doesn't do anything (behaviorally) with the false before or after this change. After this change it is logged. The goal of this change is to allow users with devices that don't have the Y2038 issue to enter dates > 2037. This could have been done with a smaller change, but the use of the new internal class TimeDetectorHelper means that the bounds logic is in one place. The lower bound (on mobile devices) can now be changed relatively easily by touching one class. Bug: 228967927 Test: m RunSettingsRoboTests ROBOTEST_FILTER="com.android.settings.datetime" Change-Id: Iaf1ca8220e0e96773aa71b595da9c1ba1e50d59d
24 lines
793 B
Java
24 lines
793 B
Java
/*
|
|
* Copyright (C) 2016 The Android Open Source Project
|
|
*
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
* you may not use this file except in compliance with the License.
|
|
* You may obtain a copy of the License at
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
* See the License for the specific language governing permissions and
|
|
* limitations under the License.
|
|
*/
|
|
|
|
package com.android.settings.datetime;
|
|
|
|
import android.content.Context;
|
|
|
|
public interface UpdateTimeAndDateCallback {
|
|
void updateTimeAndDateDisplay(Context context);
|
|
}
|