Fixed
Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #2
il...@google.com <il...@google.com> #3
Here is what I found:
On API 31+, time was not updated after the host was waken up. While on API 30 and under, time was updated after host was waken up. The main difference is caused by switching the modem simulator. In API 30 and under, time will be updated whenever signal strength query is received.
Looking at the code in API 31+ for time update when signal strength query is received, I think it is possible that timeUpdate is not invoked
void NetworkService::HandleSignalStrength(const Client& client) {
std::vector<std::string> responses;
std::stringstream ss;
if (WakeupFromSleep()) {
misc_service_->TimeUpdate();
} else if (first_signal_strength_request_) {
first_signal_strength_request_ = false;
misc_service_->TimeUpdate();
}
android_last_signal_time_ = time(0);
auto response = BuildCSQCommandResponse(GetCurrentSignalStrength());
responses.push_back(response);
responses.push_back("OK");
client.SendCommandResponse(responses);
}
Description
Component used: Fragment Version used: 1.3.0-alpha06
With the change in b/156527405 to use
setMaxLifecycle()
to controlmoveToState()
,FragmentScenario
should allow you to set an initialLifecycle
state.This would allow developers to stop the Fragment at the
CREATED
state and verify state before moving it upward toSTARTED
orRESUMED
.