做网站市场价格多少app网络推广方案

客户在测试Android系统定时开关机时，发现设置一个系统时间，重启之后，系统时间就变了，认为这个是BUG  排查了log发现有一段这样的打印：

05-14 08:45:28.004   575   575 D AlarmManager: mWakeupWhiteList={com.android.calendar, com.cghs.stresstest, com.android.deskclock}
05-14 08:45:28.005   575   575 I AlarmManager: Current time only 1747179928005, advancing to build time 1747201672000
05-14 08:45:30.205   575   575 W ===>LZP[hym8563_rtc_set_time] 125-4-14,5: 47:52-3
05-14 08:45:30.207   120   120 W ===>LZP[hym8563_rtc_read_time] 125-4-14,5: 47:52-3
05-14 14:47:52.010   575   660 D AlarmManager: setImplLocked() callingPackage=android
05-14 14:47:52.010   575   575 V SystemServerTiming: StartAlarmManagerService took to complete: 12ms
05-14 14:47:52.011   575   575 D SystemServerTiming: StartInputManagerService
05-14 14:47:52.011   575   660 D AlarmManager: setImplLocked() callingPackage=android
05-14 14:47:52.012   575   575 I InputManager: Initializing input manager, mUseDevInputEventForAudioJack=false
05-14 14:47:52.012   575   575 V SystemServerTiming: StartInputManagerService took to complete: 2ms

意思是系统目前时间比构建时间早，于是就把系统构建时间设置成了当前时间，因此客户看起来这个是有问题的，感觉这个确实是Android系统有点多此一举了。。。