android dev day 4----Intent

安卓开发资源:http://www.verycd.com/topics/2929580/

java SE

oracle ...:查询语句

XML

jdbc

html css、 AJAX

jsp servlet

ssh:..+...+...


Intent
  是acitivity之间跳转的桥梁,负责数据的传递。
 第一种用法:
 Intent intent = new Intent(Context,类名.class);
   第一个参数是要从哪个activity跳转。
   第二个参数是要跳转的目标activity。
 第二种用法:
   Intent intent = new Intent();
    intent.setClass(Context,类名.class);
  startActivity(intent);
  传递参数的方法:
  第一种:通过Bundle
   a、绑定数据
  Bundle bundle = new Bundle();
  bundle.putString("pwd",p); 绑定一个字符串
  bundle.putChar(key, value);绑定一个字符
  //把bundle对象绑定在intent上
   intent.putExtra("bundle", bundle);
   可以去传递8种基本类型和其数组类型的数据,和普通对象。
    b、获取数据:
        //从intent对象上获取bundle对象
      Bundle bundle =intent.getBundleExtra("bundle");
// 从bundle对象上获取相对应类型的数据
String user = bundle.getString("user");
String pwd = bundle.getString("pwd");
第二种:把数据直接绑定在intent上
a、绑定数据
     intent.putExtra("user", u);
     intent.putExtra("pwd", p);
 b、获取数据
    String user = intent.getStringExtra("user");
    String pwd = intent.getStringExtra("pwd");
在项目中常用第二种进行数据传递
 Activity之间跳转的步骤:
   1、创建第二个activity
   2、在清单文件中注册activity
   3、设置与该activity对应的布局文件
   4、在需要跳转的监听器中创建
      Intent intent = new Intent();
      intent.setClass(参数一,参数二);
      参数一代表当前activity的对象,参数二是要
   跳转的activity的类名.class
   5、向intent中绑定需要传递的数据
     intent.putExtra(String key,Object value);
   6、调用startActivity(intent)
   7、如果需要第二个activity返回处理的结果需要把
  第6个步骤中调用的方法替换成startActivityForResult(intent, LOGIN_REQUEST)
 该方法中第一个参数是intent对象,第二个参数是一个请求码(int类型)\
   8、如果需要第二个activity中返回结果,则需要在、
  第二个activity中调用setResult(MainActivity.LOGIN_RESULT, intent);
 该方法中第一个参数是结果码(int类型),第二个参数是
 intent。
   9、需要在第一个activity中重写
 onActivityResult(int requestCode, int resultCode, Intent data)
 该方法中的第一个参数是请求码,第二个参数是结果码,第三个参数是绑定数据
 的intent对象
  10、在清单文件中注册activity的步骤:
      <activity
            android:name=".LoginActivity"
            android:label="@string/app_name" >
        </activity>
   android:name是activity的名字
   android:label是该activity标签的名字
  如果activity作为该应用程序的入口activity则在
  </activity>前加上如下:
     <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
      </intent-filter>
---Activity的生命周期
  1、Activity的状态
    Activity处于的状态就是其生命周期处于的状态。
  2、状态的种类
       运行状态:activity处于运行
      暂停状态: 在锁屏前或者是被另外一个activity部分遮挡
      停止状态:被另外一个activity完全遮挡。
  3、与生命周期相关的方法:
    onCreate():当系统创建activity实例以后触发该方法
    onStart():是当执行完onCreate方法或者onRestart方法以后触发
    onRestart():这个activity由停止状态变为运行状态,触发该方法
    onResume():是在onStart方法后面调用
    onPause():是当activity被部分遮挡后触发该方法
    oStop():当activity被完全遮挡会触发该方法
    onDestory():是当按返回键或者调用finish方法会触发该方法
  4、activity处于运行状态
    流程: onCreate-->onStart-->onResume
    a、由系统创建该activity的实例对象
    b、触发该activity的onCreate方法,在该方法
   中可以设置与该activity对应的布局文件,初始化组件
    c、触发onStart方法
    d、触发onResume方法
    e、activity处于运行状态
  5、Activity由运行状态到暂停状态,然后恢复到运行状态
  流程: onResume-->onPasue-->onResume
  a、当另外一个activity部分遮挡住该Activity
  b、触发onPasue方法,在该方法中保存数据的操作,
  该Activity处于暂停状态
  c、当Activity再次到屏幕的最前面
  d、触发OnResume方法
  e、该Activity处于运行状态
 6、由运行状态到停止状态,再到运行状态
  流程: onResume-->onPasue-->onStop-->onRestart-->onStart-->onResume
  a、当另外一个activity完全遮挡住该Activity
  b、触发该ACtivity的onPasue方法
  c、触发该Activity的OnStop方法
  d、当该activity再次回到屏幕的前端
  e、触发该Activity的onRestart方法
  f、触发该Activity的onStart方法
  g、触发该Activity的onResume方法
  h、该Activity处于运行状态
 7、由运行状态到销毁
  流程:onResume-->onpasue-->onStop-->onDestory
  a、当用户点击返回键或者调用了finish方法
  b、触发onPasue--onStop--onDestory
 8、销毁
  当手机电量过低或者内存不足,会把处于暂停状态和
停止状态的activity销毁。
 9、如果从A的Activity跳转到B的Activity,在从
B的Activity跳转到A的Activity:
  可以在B的Activity中调用startActivity(intent)
但是这种跳转回去的Activity和之前的Activity不是同一个
对象。
 用finish方法或者按返回键回到上一个Activity是同一个
Activity。

06-17 03:01:00.882 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: filePath is /vendor/bin/cat 06-17 03:01:00.882 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the in_command is:/vendor/bin/cat /sys/kernel/kiwi_v2/power_stats 06-17 03:01:00.882 1875 1875 E vendor.oplus.hardware.wifi-aidl-service: wifiPopen error 06-17 03:01:00.882 3198 7415 E OplusWifiHalServiceAidlImpl: IOplusWifiService.executeDriverCommandWithResult failed: android.os.ServiceSpecificException: (code 0) 06-17 03:01:00.883 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: filePath is /vendor/bin/cat 06-17 03:01:00.883 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the in_command is:/vendor/bin/cat /sys/kernel/peach/power_stats 06-17 03:01:00.883 1875 1875 E vendor.oplus.hardware.wifi-aidl-service: wifiPopen error 06-17 03:01:00.883 3198 7415 E OplusWifiHalServiceAidlImpl: IOplusWifiService.executeDriverCommandWithResult failed: android.os.ServiceSpecificException: (code 0) 06-17 03:01:00.883 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: filePath is /vendor/bin/cat 06-17 03:01:00.883 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the in_command is:/vendor/bin/cat /sys/kernel/peach_v2/power_stats 06-17 03:01:00.883 1875 1875 E vendor.oplus.hardware.wifi-aidl-service: wifiPopen error 06-17 03:01:00.884 3198 7415 E OplusWifiHalServiceAidlImpl: IOplusWifiService.executeDriverCommandWithResult failed: android.os.ServiceSpecificException: (code 0) 06-17 03:01:00.884 3198 7415 D OplusWifiPowerStatsManager: strStartIndex = 36 strEndIndex= 74 06-17 03:01:00.884 3198 7415 D OplusWifiPowerStatsManager: wlan fw idle time from open wifi : -1525478740 06-17 03:01:00.884 3198 7415 D OplusWifiPowerService: mSoftApIface is null 06-17 03:01:00.885 3198 7415 V OplusWifiPowerMcsTrxInfor: *****---> map:{wlan0_on_time=3842, wlan0_idleTimeMillis=3223, wlan0_tx_time=339, wlan0_rx_time=280, wlan0_on_time_scan=2108, wlan0_on_time_nan_scan=0, wlan0_on_time_bg_scan=0, wlan0_on_time_roam_scan=0, wlan0_on_time_pno_scan=320, wlan0_on_time_hs20_scan=0} 06-17 03:01:00.892 3198 7415 D OplusBatteryManager: getPsyBatteryRm: 1402 06-17 03:01:00.892 3198 7415 D OplusWifiPowerService: mStartBatteryCapacity = 1402 06-17 03:01:00.892 3198 7415 D OplusWifiPowerLogCollect: diable wifi collect power log , mIsEnableQcomCollectLog = 0 06-17 03:01:00.899 3198 3198 D OplusTetheringNotification: onReceive: action: android.intent.action.SCREEN_OFF 06-17 03:01:00.903 29625 29625 D StyleCardEventMonitor: onScrolled: dx = 0dy = 0 06-17 03:01:00.932 3198 4624 W OplusStorageManagerFeature: mScreenReceiver action:android.intent.action.SCREEN_OFF 06-17 03:01:00.933 5775 7147 I metis_v2_AppSwitchStateManager: isScreenOn:false isScreenIsLock:true,deviceState:,deviceTypeName [base|com.oplus.metis|1.5.5-f48228a] 06-17 03:01:00.934 3198 4624 W OplusStorageManagerFeature: turn screenOff, maintPrepared:false 06-17 03:01:00.935 3198 4624 W OplusStorageManagerFeature: sendToTarget over,paramStr:4 06-17 03:01:00.944 29625 29625 D StyleCardEventMonitor: onScrolled: dx = 0dy = 0 06-17 03:01:00.946 3198 4624 I OplusStorageManagerFeature: FsReserveSpace data partition fstype:f2fs 06-17 03:01:00.947 3198 4624 I OplusStorageManagerFeature: FsReserveSpace data device path:/dev/block/dm-98 06-17 03:01:00.952 3198 7415 D OplusBatteryManager: getPsyBatteryRm: 1400 06-17 03:01:00.953 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: filePath is /vendor/bin/cat 06-17 03:01:00.953 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the in_command is:/vendor/bin/cat /sys/kernel/wifi/power_stats 06-17 03:01:00.953 1875 1875 E vendor.oplus.hardware.wifi-aidl-service: wifiPopen error 06-17 03:01:00.953 3198 7415 E OplusWifiHalServiceAidlImpl: IOplusWifiService.executeDriverCommandWithResult failed: android.os.ServiceSpecificException: (code 0) 06-17 03:01:00.954 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: filePath is /vendor/bin/cat 06-17 03:01:00.954 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the in_command is:/vendor/bin/cat /sys/kernel/qca6390/power_stats 06-17 03:01:00.954 1875 1875 E vendor.oplus.hardware.wifi-aidl-service: wifiPopen error 06-17 03:01:00.954 3198 7415 E OplusWifiHalServiceAidlImpl: IOplusWifiService.executeDriverCommandWithResult failed: android.os.ServiceSpecificException: (code 0) 06-17 03:01:00.954 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: filePath is /vendor/bin/cat 06-17 03:01:00.954 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the in_command is:/vendor/bin/cat /sys/kernel/qca6750/power_stats 06-17 03:01:00.954 1875 1875 E vendor.oplus.hardware.wifi-aidl-service: wifiPopen error 06-17 03:01:00.955 3198 7415 E OplusWifiHalServiceAidlImpl: IOplusWifiService.executeDriverCommandWithResult failed: android.os.ServiceSpecificException: (code 0) 06-17 03:01:00.955 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: filePath is /vendor/bin/cat 06-17 03:01:00.955 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the in_command is:/vendor/bin/cat /sys/kernel/qca6490/power_stats 06-17 03:01:00.966 3198 4624 E OplusStorageManagerFeature: FsReserveSpace read data label failed.java.nio.file.NotLinkException: /dev/block/dm-98 06-17 03:01:00.966 3198 4624 E OplusStorageManagerFeature: at sun.nio.fs.UnixFileSystemProvider.readSymbolicLink(UnixFileSystemProvider.java:515) 06-17 03:01:00.966 3198 4624 E OplusStorageManagerFeature: at java.nio.file.Files.readSymbolicLink(Files.java:1432) 06-17 03:01:00.966 3198 4624 E OplusStorageManagerFeature: at com.android.server.storage.OplusStorageManagerFeature.onMessageFsReserveSpace(OplusStorageManagerFeature.java:2159) 06-17 03:01:00.966 3198 4624 E OplusStorageManagerFeature: at com.android.server.storage.OplusStorageManagerFeature.onStorageManagerMessageHandle(OplusStorageManagerFeature.java:1521) 06-17 03:01:00.966 3198 4624 E OplusStorageManagerFeature: at com.android.server.StorageManagerService$StorageManagerServiceHandler.handleMessage(StorageManagerService.java:790) 06-17 03:01:00.966 3198 4624 E OplusStorageManagerFeature: at android.os.Handler.dispatchMessage(Handler.java:107) 06-17 03:01:00.966 3198 4624 E OplusStorageManagerFeature: at android.os.Looper.loopOnce(Looper.java:282) 06-17 03:01:00.966 3198 4624 E OplusStorageManagerFeature: at android.os.Looper.loop(Looper.java:387) 06-17 03:01:00.966 3198 4624 E OplusStorageManagerFeature: at android.os.HandlerThread.run(HandlerThread.java:85) 06-17 03:01:00.966 3198 4624 I OplusStorageManagerFeature: FsReserveSpace data label:dm-98 06-17 03:01:00.966 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is POWER DEBUG STATS 06-17 03:01:00.966 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 4096 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is ================= 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 4078 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is cumulative_sleep_time_ms: -1525478678 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 4060 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is cumulative_total_on_time_ms: 317414745 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 4022 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is deep_sleep_enter_counter: 2178774 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3983 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is last_deep_sleep_enter_tstamp_ms: 0 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3949 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_register_fmt: 0 06-17 03:01:00.970 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3914 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is num_debug_register: 20 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3892 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[0]: 0x0 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3869 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[1]: 0x76a269e 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3845 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[2]: 0x68713 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3815 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[3]: 0x23513dc6 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3787 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[4]: 0xc2705 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3756 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[5]: 0x107784 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3728 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[6]: 0x0 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3699 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[7]: 0x0 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3675 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[8]: 0x8d354b65 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3651 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[9]: 0x84da 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3620 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[10]: 0x0 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3593 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[11]: 0xb303011 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3568 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[12]: 0xd14ab 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3537 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[13]: 0x3cc35b3a 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3508 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[14]: 0xd271b 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3476 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[15]: 0xd76f6 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3447 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[16]: 0x0 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3418 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[17]: 0x0 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3393 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[18]: 0x6ffed24b 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3368 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the buf of executeDriverCommand is debug_registers[19]: 0x51cf 06-17 03:01:00.971 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: , remain_len is 3336 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: getQcomFwActiviteTime = POWER DEBUG STATS 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: ================= 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: cumulative_sleep_time_ms: -1525478678 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: cumulative_total_on_time_ms: 317414745 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: deep_sleep_enter_counter: 2178774 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: last_deep_sleep_enter_tstamp_ms: 0 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_register_fmt: 0 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: num_debug_register: 20 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[0]: 0x0 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[1]: 0x76a269e 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[2]: 0x68713 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[3]: 0x23513dc6 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[4]: 0xc2705 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[5]: 0x107784 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[6]: 0x0 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[7]: 0x0 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[8]: 0x8d354b65 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[9]: 0x84da 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[10]: 0x0 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[11]: 0xb303011 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[12]: 0xd14ab 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[13]: 0x3cc35b3a 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[14]: 0xd271b 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[15]: 0xd76f6 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[16]: 0x0 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[17]: 0x0 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[18]: 0x6ffed24b 06-17 03:01:00.972 3198 7415 D OplusWifiPowerStatsManager: debug_registers[19]: 0x51cf 06-17 03:01:00.973 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: filePath is /vendor/bin/cat 06-17 03:01:00.973 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the in_command is:/vendor/bin/cat /sys/kernel/kiwi_v2/power_stats 06-17 03:01:00.973 1875 1875 E vendor.oplus.hardware.wifi-aidl-service: wifiPopen error 06-17 03:01:00.973 3198 7415 E OplusWifiHalServiceAidlImpl: IOplusWifiService.executeDriverCommandWithResult failed: android.os.ServiceSpecificException: (code 0) 06-17 03:01:00.973 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: filePath is /vendor/bin/cat 06-17 03:01:00.973 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the in_command is:/vendor/bin/cat /sys/kernel/peach/power_stats 06-17 03:01:00.973 1875 1875 E vendor.oplus.hardware.wifi-aidl-service: wifiPopen error 06-17 03:01:00.973 3198 7415 E OplusWifiHalServiceAidlImpl: IOplusWifiService.executeDriverCommandWithResult failed: android.os.ServiceSpecificException: (code 0) 06-17 03:01:00.974 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: filePath is /vendor/bin/cat 06-17 03:01:00.974 1875 1875 D vendor.oplus.hardware.wifi-aidl-service: the in_command is:/vendor/bin/cat /sys/kernel/peach_v2/power_stats 06-17 03:01:00.974 1875 1875 E vendor.oplus.hardware.wifi-aidl-service: wifiPopen error 06-17 03:01:00.975 3198 7415 E OplusWifiHalServiceAidlImpl: IOplusWifiService.executeDriverCommandWithResult failed: android.os.ServiceSpecificException: (code 0) 06-17 03:01:00.975 3198 7415 D OplusWifiPowerStatsManager: strStartIndex = 36 strEndIndex= 74 06-17 03:01:00.975 3198 7415 D OplusWifiPowerStatsManager: wlan fw idle time from open wifi : -1525478678 06-17 03:01:00.977 29625 29625 D StyleCardEventMonitor: onScrolled: dx = 0dy = 0 06-17 03:01:00.994 1248 1253 I android.system.suspend-service: Last release wakelock name = PowerManagerService.Broadcasts 06-17 03:01:00.994 1248 1253 I android.system.suspend-service: mAutosuspendEnabled=1 06-17 03:01:00.994 1248 15298 I android.system.suspend-service: Start checking autosuspend client... 06-17 03:01:00.995 1248 15298 I android.system.suspend-service: autosuspend client checking completed. 06-17 03:01:00.995 1248 15298 I android.system.suspend-service: Start checking autosuspend client... 06-17 03:01:00.995 1248 15298 I android.system.suspend-service: autosuspend client checking completed. 06-17 03:01:00.995 1248 15298 I android.system.suspend-service: Android start to suspend... 06-17 03:01:01.010 29625 29625 D StyleCardEventMonitor: onScrolled: dx = 0dy = 0 06-17 03:01:01.043 29625 29625 D StyleCardEventMonitor: onScrolled: dx = 0dy = 0 06-17 03:01:03.977 1249 12660 I keystore2: system/security/keystore2/watchdog/src/lib.rs:319 - Watchdog thread idle -> terminating. Have a great day. 06-17 03:01:03.980 1798 14927 I QC2Comp : [avcD_34552] Stats: Pending(0) i/p-done(0) Works: Q: 0/Done 0|Work-Rate: Q(0.0/s Avg=0.0/s) Done(0.000/s Avg=0.000/s)| Stream: 30.00fps 0.0Kbps 06-17 03:01:03.980 1798 14927 I QC2Comp : [avcD_34552] Mem-usage: | Total: 0.000 MB 06-17 03:01:03.980 1971 2397 D VRR [OTI]: handleIdle from 0 to 1 06-17 03:01:03.981 1971 2397 D VRR [OTI-HW]: isStateReady 0 06-17 03:01:03.981 1971 2397 D VRR [OTI-HW]: rate range: min {id=1, hwcId=1, resolution=1080x2412, vsyncRate=60.00 Hz, dpi=391.89x392.72, group=0, vrrConfig=N/A} cur {id=0, hwcId=0, resolution=1080x2412, vsyncRate=120.00 Hz, dpi=391.89x392.72, group=0, vrrConfig=N/A} max {id=0, hwcId=0, resolution=1080x2412, vsyncRate=120.00 Hz, dpi=391.89x392.72, group=0, vrrConfig=N/A} 06-17 03:01:03.981 1971 2397 D VRR [OTI-HW]: keep rate. 06-17 03:01:03.991 1629 1709 E minksocket: MinkIPC_QRTR_Service: client with node 1 port 5d78 went down 06-17 03:01:03.992 3613 3617 E Diag_Lib: [IMS_AP]"ims-rtp-daemon ims_rtp_qmi_handler_thread_func waiting on select thread>" 06-17 03:01:03.996 7560 7764 W Looper : Slow delivery took 2901ms SysUiBg h=com.android.systemui.appops.AppOpsControllerImpl$H c=com.android.systemui.appops.AppOpsControllerImpl$H$1@88bc2b2 m=0 06-17 03:01:03.996 7560 7764 W Looper : Drained 06-17 03:01:03.996 10127 14685 D gaia-GaiaConnectChecker: start connect check++ 06-17 03:01:03.997 1001 6750 D CustomLogManagerService: WorkHandler msg.what :5 06-17 03:01:04.000 16127 8880 D QualityProtectService: handleMessage: 2 06-17 03:01:04.000 16127 8880 I QualityProtectService: mStartReason: performance_data_collect 06-17 03:01:04.000 16127 8880 I QualityProtectProcessorManager: already startMonitor, do nothing 06-17 03:01:04.000 16127 8880 D QualityProtectService: perfDataReportCheck not ok 06-17 03:01:04.001 10127 16667 D gaia-GaiaConnectChecker: start connect check++ 06-17 03:01:04.002 2162 2162 E AwakeServiceAnr4Main: [anrCheckRunnable],start execute check runnable. 06-17 03:01:04.008 7560 10306 I PluginSeedling--Origin: OSenseManager-->isMEMHighPressure oldState:false newState: false isMEMHighPressure:false 06-17 03:01:04.009 1629 1709 E minksocket: MinkIPC_QRTR_Service: client with node 1 port 5d79 went down 06-17 03:01:04.009 3613 3617 E Diag_Lib: [IMS_AP]"ims-rtp-daemon ims_rtp_qmi_handler_thread_func waiting on select thread>" 06-17 03:01:04.011 3198 7464 E OplusUIFirst_TS: Failed to connect bpf bin: -1 06-17 03:01:04.011 12802 13808 E AwakeServiceAnr4UI: [linkToMainProcess],receive callback,isAwakeUIServiceInit=true 06-17 03:01:04.015 29625 29625 D StyleCardEventMonitor: onScrolled: dx = 0dy = 0 06-17 03:01:04.017 1629 1709 E minksocket: MinkIPC_QRTR_Service: client with node 1 port 5d7a went down 06-17 03:01:04.017 3613 3617 E Diag_Lib: [IMS_AP]"ims-rtp-daemon ims_rtp_qmi_handler_thread_func waiting on select thread>" 06-17 03:01:04.020 3198 7438 D CompatChangeReporter: Compat change id reported: 151861875; UID 10125; state: ENABLED 06-17 03:01:04.020 7560 7567 I ndroid.systemui: gc_priority_optimize ctrlAppThreadUx sharedAppUxFd=892pid=7560tid=7567value=130 ret=2 06-17 03:01:04.024 1629 1709 E minksocket: MinkIPC_QRTR_Service: client with node 1 port 5d7b went down 06-17 03:01:04.025 3613 3617 E Diag_Lib: [IMS_AP]"ims-rtp-daemon ims_rtp_qmi_handler_thread_func waiting on select thread>" 06-17 03:01:04.036 1001 6750 D CustomLogManagerService: curTemp:270 limit:390 06-17 03:01:04.036 1001 6750 D CustomLogManagerService: checkUploadStatus: isSceenOn=false activeNetType=1 isCharging=false isUploading:false temperatureLimit:false 06-17 03:01:04.036 1001 6750 D CustomLogManagerService: sys.log.customer=false 06-17 03:01:04.036 1001 6750 D CustomLogManagerService: isHaveCustomLogCollecting :false 06-17 03:01:04.037 3198 4624 W libc : Unable to set property "persist.sys.oppo.fsReservedBlocks" to "283438": PROP_ERROR_READ_DATA (0x8) 06-17 03:01:04.043 3198 7438 V GrammaticalInflectionUtils: AttributionSource: android.content.AttributionSource@c67bc4f2 does not have READ_SYSTEM_GRAMMATICAL_GENDER permission. 06-17 03:01:04.045 7560 7567 I ndroid.systemui: gc_priority_optimize ctrlAppThreadUx sharedAppUxFd=892pid=7560tid=7567value=768 ret=0 06-17 03:01:04.048 29625 29625 D StyleCardEventMonitor: onScrolled: dx = 0dy = 0 06-17 03:01:04.049 1561 30360 E TetherController: property_get sys.radio.data.modem_share_flag return 0, 1! 06-17 03:01:04.050 3198 3198 W Looper : Slow delivery took 2828ms main h=android.os.Handler c=com.android.server.theia.TheiaSystemJankDecteor$1@95930c8 m=0 06-17 03:01:04.050 3198 3502 D VRR [OPlusGameStatusManager]: handleMessage: 7004 06-17 03:01:04.050 3198 3502 D VRR [OPlusGameStatusManager]: handleBrightnessDone 06-17 03:01:04.050 3198 7437 D OplusOwmMonitorCenter: apName Sync to OWM in Helper: 06-17 03:01:04.050 3198 4624 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: StorageManagerService 06-17 03:01:04.050 3198 4624 E AndroidRuntime: java.lang.RuntimeException: failed to set system property "persist.sys.oppo.fsReservedBlocks" to "283438" (check logcat for reason) 06-17 03:01:04.050 3198 4624 E AndroidRuntime: at android.os.SystemProperties.native_set(Native Method) 06-17 03:01:04.050 3198 4624 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:267) 06-17 03:01:04.050 3198 4624 E AndroidRuntime: at com.android.server.storage.OplusStorageManagerFeature.onMessageFsReserveSpace(OplusStorageManagerFeature.java:2229) 06-17 03:01:04.050 3198 4624 E AndroidRuntime: at com.android.server.storage.OplusStorageManagerFeature.onStorageManagerMessageHandle(OplusStorageManagerFeature.java:1521) 06-17 03:01:04.050 3198 4624 E AndroidRuntime: at com.android.server.StorageManagerService$StorageManagerServiceHandler.handleMessage(StorageManagerService.java:790) 06-17 03:01:04.050 3198 4624 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107) 06-17 03:01:04.050 3198 4624 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:282) 06-17 03:01:04.050 3198 4624 E AndroidRuntime: at android.os.Looper.loop(Looper.java:387) 06-17 03:01:04.050 3198 4624 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:85) 06-17 03:01:04.050 3198 7365 I MR2ServiceImpl: Updating composite discovery preference | preference: RouteDiscoveryRequest{ preferredFeatures={}, activeScan=false }, active routers: [] 06-17 03:01:04.051 3198 7603 I Osense-PsiDetector: 1915,234,4581,7679,41,270,251,1807,1964,620,1141,0,8,7618
最新发布
07-09
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值