底电top alarms的原因分析和doze模式判断

Top Alarms:
    +28s850ms running, 3 wakeups, 3 alarms: u0a107:com.android.vending//这个com.android.vending是在system/etc/sysconfig/google.xml，在白名单里面，但是这个不是在底电测试时候执行的。大致看一下
      *walarm*:com.android.vending/com.google.android.finsky.receivers.FlushLogsReceiver   //这个我查了资料也弄不明白，啥原因，跟手机休眠下去无关，可能是我重启进去设置时间操作手机那段时间的，差不多也是这么20多秒长时间。
    
    +23s587ms running, 4 wakeups, 4 alarms: u0a81:com.android.providers.calendar
      *walarm*:com.android.providers.calendar.intent.CalendarProvider2        //这个日历的更新也是我之前自己设置时间的事件，跟底电无关
 
    +13s365ms running, 4 wakeups, 4 alarms: u0a93:com.google.android.gms     //谷歌移动服务，ido4手机配置文件里有在adb shell后的system/etc/sysconfig/google.xml里。配置里面com.google.android.gms
      *walarm*:com.google.android.intent.action.GCM_RECONNECT//这些服务都是白名单，省电模式下，后台也会运行
   
    +3s991ms running, 0 wakeups, 12 alarms: 1000:android       // +23m29s658ms  +40m42s572ms   TIME_TICK_ACTION     广播：当前时间已经变化，之前自己重新设置时间原因
      *alarm*:android.intent.action.TIME_TICK
   
    +2s950ms running, 0 wakeups, 3 alarms: 1000:com.tct.diagnostics//这个是TCL自己的一个设置。网上查的，具体实在不知道
      *alarm*:com.tct.action.DATABASE_TIME_TASK_ACTION
    
    +2s929ms running, 0 wakeups, 3 alarms: 1000:com.tct.diagnostics
      *alarm*:com.tct.action.REFRESH_TIMER_TASK_ACTION
   
    +1s796ms running, 2 wakeups, 2 alarms: u0a161:com.google.android.apps.messaging//安卓4.1以后谷歌在android上增加了 系统自带短信应用，我也没明白怎么起来的
      *walarm*:com.google.android.apps.messaging/.shared.analytics.AnalyticsAlarmReceiver
   
    +1s700ms running, 3 wakeups, 3 alarms: u0a172:com.google.android.apps.photos//谷歌原生app，跟自动同步有关，只是猜测
      
    +1s697ms running, 3 wakeups, 3 alarms: u0a93:com.google.android.gms //系统白名单的服务，后台会自启动，配置文件里面是 <allow-in-power-save package="com.google.android.gms" />
      *walarm*:com.google.android.gms/.checkin.EventLogServiceReceiver
   
    +1s550ms running, 0 wakeups, 1 alarms: u0a130:com.google.android.calendar    //这个是我之前先设置的年月，最后设置的时间的原因，跟手机底电下去无关
      *alarm*:com.google.android.calendar.widgetmonth.MonthViewWidgetProvider.MIDNIGHT
      
      
      
      doze相关判断：
      进程服务：//这边屏保doze模式是开的。
      01-01 08:00:54.347  2415  2467 I DreamController: Starting dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0
01-01 08:01:04.295  2415  2467 I DreamController: Stopping dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0
12-26 14:15:14.629  2415  2467 I DreamController: Starting dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0
12-26 14:15:19.937  2415  2467 I DreamController: Stopping dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0
12-26 14:15:27.447  2415  2467 I DreamController: Starting dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0
12-26 14:15:29.149  2415  2467 I DreamController: Stopping dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0
12-26 14:15:35.875  2415  2467 I DreamController: Starting dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0
12-26 15:20:13.079  2415  2467 I DreamController: Stopping dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0
      Service com.android.systemui.doze.DozeService:
 , dozeScreenBrightness=-1, dozeScreenState=UNKNOWN
   dozeScreenBrightness=-1, dozeScreenState=UNKNOWN
getDozeComponent()=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}

9,10114,l,apk,0,com.android.systemui,com.android.systemui.doze.DozeService,0,0,2
SERVICE com.android.systemui/.doze.DozeService 9fc6216 pid=2754
      doze screen state: OFF   
      doze screen brightness: -1//灭屏判断