SystemUi--Keyguard: OplusLockScreenWallpaper-->selectWallpaperHelper ***isDefaultKeyguard-Pictorial*** 05-07 10:21:25.201 02308 02308 I SystemUi--Keyguard: OplusLockScreenWallpaper-->select wallpaper helper is : 1 05-07 10:21:25.201 02308 02308 I SystemUi--Keyguard: OplusLockScreenWallpaper-->onWallpaperChange , wallpaper helper type = 1,

时间: 2025-08-16 07:11:39 AIGC 浏览: 22
<think>嗯,用户想了解如何调试OplusLockScreenWallpaper在Keyguard中的行为,特别是selectWallpaperHelper和isDefaultKeyguard-Pictorial相关的日志信息。首先,我需要回忆一下Android锁屏壁纸的机制,可能涉及到Keyguard的布局和相关的服务。 根据用户提供的引用,比如引用[1]提到了KeyguardSecurityViewFlipper加载不同的锁屏布局,这可能与壁纸的显示有关。OplusLockScreenWallpaper可能是Oppo定制的锁屏壁纸组件,可能在Keyguard的视图层次结构中。用户提到的selectWallpaperHelper可能是一个帮助类,用于选择或切换壁纸,而isDefaultKeyguard-Pictorial可能是一个标志,用于判断当前是否是默认的图片壁纸。 接下来,日志解析是关键。用户需要知道如何抓取相关日志,可能需要开启详细日志级别或者使用特定的过滤标签。引用[5]提到了NFC的日志处理,但这里可能需要查找与壁纸相关的标签,比如"Keyguard"或"OplusLockScreenWallpaper"。 另外,用户可能需要检查代码中与selectWallpaperHelper相关的逻辑,查看是否有日志输出。比如,在代码中是否有Log.d或Log.i的语句,标签是什么。可能需要建议用户使用adb logcat过滤这些标签,或者开启调试模式。 还有,isDefaultKeyguard-Pictorial可能是一个方法或变量,用于判断当前壁纸是否为默认类型。用户可能需要检查这个方法的返回值,或者在日志中搜索这个关键字,以确定壁纸状态是否改变。 还要考虑到Oppo可能有自己的定制代码,比如在系统应用中,如引用[3]提到的com.sec.android.app.keyguard,但用户的问题是关于Oplus的,可能涉及不同的包名。需要确认正确的包名和组件路径,以便在日志中定位。 最后,可能需要建议用户检查布局文件或使用布局检查工具,如Layout Inspector,查看Keyguard的视图结构,确认OplusLockScreenWallpaper是否正确加载。同时,动态调试或添加自定义日志可能也是必要的步骤。</think>### OplusLockScreenWallpaper Keyguard日志解析指南 根据锁屏壁纸加载机制和Android系统日志特征,以下是调试OplusLockScreenWallpaper的关键步骤: 1. **基础日志过滤命令** ```bash adb logcat -v time | grep -Ei "(Keyguard|OplusLockScreenWallpaper|selectWallpaperHelper|isDefaultKeyguard)" ``` 2. **关键日志特征解析** - **壁纸加载流程**: ``` D/OplusLockScreenWallpaper( 3245): selectWallpaperHelper() type=3, path=/system/wallpaper/default.jpg ``` 此日志显示当前选择的壁纸类型和存储路径[^1] - **默认壁纸判断逻辑**: ``` I/OplusKeyguardUtils( 3245): isDefaultKeyguard-Pictorial:true, pictorialType=3 ``` `true`表示正在使用默认图片壁纸,`pictorialType`对应壁纸分类体系[^3] 3. **动态调试技巧** - 强制触发壁纸更新: ```java KeyguardUpdateMonitor.getInstance(context).dispatchWallpaperChanged(); ``` - 注入调试参数: ```java Bundle params = new Bundle(); params.putBoolean("DEBUG_WALLPAPER_LAYER", true); WallpaperManager.getInstance().setLockWallpaper(params); ``` 4. **布局层级验证** 通过`uiautomatorviewer`工具观察锁屏视图结构时: ``` KeyguardSecurityViewFlipper └─ OplusLockScreenWallpaperView ├─ ImageView (id=default_wallpaper) └─ FrameLayout (id=dynamic_effect_layer) ``` 此结构表明壁纸已成功加载到Keyguard视图层级[^1] 5. **定制日志增强** 在源码中添加调试代码: ```java // OplusLockScreenWallpaper.java public void selectWallpaperHelper(int type) { Log.d("WallpaperDebug", "Current pictorialType=" + type + ", defaultStatus=" + isDefaultKeyguardPictorial()); // Original logic... } ``` ###
阅读全文

相关推荐

at com.oplus.systemui.aod.common.AodManager.resetRotationWhilePowerOff(AodManager.java:208) at com.oplus.systemui.aod.display.AODDisplayUtil.onFinishedWakingUp(AODDisplayUtil.java:383) at com.oplus.systemui.aod.display.SmoothTransitionController$mWakefullnessLifeLifecycle$1.onFinishedWakingUp(SmoothTransitionController.kt:142) at com.android.systemui.keyguard.WakefulnessLifecycle$$ExternalSyntheticLambda2.accept(R8$$SyntheticClass:0) at com.android.systemui.keyguard.Lifecycle.lambda$dispatch$1(Lifecycle.java:49) at com.android.systemui.keyguard.Lifecycle.$r8$lambda$K7H-EqyxFiqZEuM4H7Ktyop3hSQ(Lifecycle.java:0) at com.android.systemui.keyguard.Lifecycle$$ExternalSyntheticLambda1.invoke(R8$$SyntheticClass:0) at com.android.app.tracing.TraceUtils.trace(TraceUtils.kt:118) at com.android.systemui.keyguard.Lifecycle.dispatch(Lifecycle.java:48) at com.android.systemui.keyguard.WakefulnessLifecycle.dispatchFinishedWakingUp(WakefulnessLifecycle.java:174) at com.android.systemui.keyguard.KeyguardLifecyclesDispatcher$KeyguardLifecycleHandler.handleMessage(KeyguardLifecyclesDispatcher.java:142) at android.os.Handler.dispatchMessage(Handler.java:107) at android.os.Looper.loopOnce(Looper.java:282) at android.os.Looper.loop(Looper.java:387) at android.app.ActivityThread.main(ActivityThread.java:9494) at java.lang.reflect.Method.invoke(Native method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:600) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1005)

行 193: 09-04 09:13:19.827713 2096 2096 D KeyguardViewMediator: doKeyguard: not showing because externally disabled 行 10761: 09-04 09:14:11.742579 2096 2096 D KeyguardViewMediator: doKeyguard: not showing because externally disabled 行 24170: 09-04 09:17:05.770866 2096 2096 D KeyguardViewMediator: doKeyguard: not showing because externally disabled 行 29872: 09-04 09:17:16.209852 862 1210 I BufferQueueDebug: [ActivityRecord{7bd5340 u0 com.huaqin.factory/.MmiNewFpFodNitTestMainActivity t124}#1533](this:0xb400007bfc08c468,id:-1,api:0,p:-1,c:-1) BufferQueue core=(862:/system/bin/surfaceflinger) 行 29919: 09-04 09:17:16.240286 1656 32755 I PowerHalWrapper: amsBoostNotify pid:5420,activity:com.huaqin.factory.MmiNewFpFodNitTestMainActivity, package:com.huaqin.factory, mProcessCreatePackcom.huaqin.lcdtest 行 29921: 09-04 09:17:16.240580 1656 32755 I mtkpower_client: [PowerHal_Wrap_notifyAppState] com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity pid=5420 activityId:129848128 state:1 行 29922: 09-04 09:17:16.240672 1656 32755 I mtkpower_client: [Legacy][PowerHal_Wrap_notifyAppState] com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity pid=5420 state:129848128 行 29923: 09-04 09:17:16.241104 828 1022 I libPowerHal: [perfNotifyAppState] pack:com.huaqin.factory, act:com.huaqin.factory.MmiNewFpFodNitTestMainActivity, state:1, pid:5420, uid:1000, fps:120 行 29925: 09-04 09:17:16.241292 828 881 I mtkpower@impl: [notifyAppState] act com.huaqin.factory.ControlItemActivity => com.huaqin.factory.MmiNewFpFodNitTestMainActivity 行 29930: 09-04 09:17:16.252678 5420 5420 D MmiNewFpFodNitTestMainActivity: Device Name = charoitecharoite 行 29932: 09-04 09:17:16.254561 5420 5420 D MmiNewFpFodNitTestMainActivity: onCreate() 行 29942: 09-04 09:17:16.265728 5420 5420 D MmiNewFpFodNitTestMainActivity: current number = 1 行 29943: 09-04 09:17:16.265798 5420 5420 D MmiNewFpFodNitTestMainActivity: Base :>onCreate id = 37,name=屏下指纹录入测试 行 29949: 09-04 09:17:16.278985 5420 5420 D MmiNewFpFodNitTestMainActivity: expolevel = 136 行 29950: 09-04 09:17:16.279022 5420 5420 D MmiNewFpFodNitTestMainActivity: Need verify the Fingerprint at 110nit 行 29951: 09-04 09:17:16.279036 5420 5420 D MmiNewFpFodNitTestMainActivity: Need verify the Fingerprint at 630nit 行 29954: 09-04 09:17:16.281282 5420 5420 D MmiNewFpFodNitTestMainActivity: onResume() 行 29959: 09-04 09:17:16.286821 5420 5420 D VRI[MmiNewFpFodNitTestMainActivity]: hardware acceleration = true, forceHwAccelerated = false 行 29962: 09-04 09:17:16.289481 862 1210 I BufferQueueDebug: [b8fd5ca com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity#1534](this:0xb400007bfc03fe08,id:-1,api:0,p:-1,c:-1) BufferQueue core=(862:/system/bin/surfaceflinger) 行 29988: 09-04 09:17:16.304252 862 1210 I BufferQueueDebug: [com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity#1535](this:0xb400007bfc01d268,id:-1,api:0,p:-1,c:-1) BufferQueue core=(862:/system/bin/surfaceflinger) 行 30014: 09-04 09:17:16.316619 5420 5420 D BLASTBufferQueue: [VRI[MmiNewFpFodNitTestMainActivity]#2](f:0,a:0) constructor() 行 30015: 09-04 09:17:16.316743 5420 5420 D BLASTBufferQueue: [VRI[MmiNewFpFodNitTestMainActivity]#2](f:0,a:0) update width=1080 height=2392 format=-1 mTransformHint=0 行 30017: 09-04 09:17:16.317939 5420 7102 D BufferQueueProducer: [VRI[MmiNewFpFodNitTestMainActivity]#2(BLAST Consumer)2](id:152c00000002,api:1,p:5420,c:5420) connect: api=1 producerControlledByApp=true 行 30018: 09-04 09:17:16.318900 5420 5420 D VRI[MmiNewFpFodNitTestMainActivity]: vri.reportNextDraw android.view.ViewRootImpl.performTraversals:5060 android.view.ViewRootImpl.doTraversal:3633 android.view.ViewRootImpl$TraversalRunnable.run:11891 android.view.Choreographer$CallbackRecord.run:1861 android.view.Choreographer$CallbackRecord.run:1870 行 30019: 09-04 09:17:16.318973 5420 5420 D VRI[MmiNewFpFodNitTestMainActivity]: Setup new sync=wmsSync-VRI[MmiNewFpFodNitTestMainActivity]#6 行 30024: 09-04 09:17:16.321758 1656 1787 D SurfaceComposerClient: Transaction::apply InputWindowCommands.focusRequests timestamp=45208798141693, windowName=b8fd5ca com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity 行 30025: 09-04 09:17:16.324616 5420 7102 D BLASTBufferQueue: [VRI[MmiNewFpFodNitTestMainActivity]#2](f:0,a:1) acquireNextBufferLocked size=1080x2392 mFrameNumber=1 applyTransaction=true mTimestamp=45208809025078(auto) mPendingTransactions.size=0 graphicBufferId=23278722744334 transform=0 行 30026: 09-04 09:17:16.325396 5420 5420 D VRI[MmiNewFpFodNitTestMainActivity]: vri.reportDrawFinished 行 30029: 09-04 09:17:16.329709 862 862 D SurfaceFlinger: Focus addInputWindowCommands timestamp=45208798141693, windowName=b8fd5ca com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity 行 30031: 09-04 09:17:16.332948 862 1210 I BufferQueueDebug: [Transition Root #148: ActivityRecord{7bd5340 u0 com.huaqin.factory/.MmiNewFpFodNitTestMainActivity t124}#1538](this:0xb400007bfbfa39b8,id:-1,api:0,p:-1,c:-1) BufferQueue core=(862:/system/bin/surfaceflinger) 行 30034: 09-04 09:17:16.333263 862 1624 D SurfaceFlinger: updateWinowInfo=1, setFocusedWindow timestamp=45208798141693, windowName=b8fd5ca com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity 行 30042: 09-04 09:17:16.340383 1656 1783 I ActivityTaskManager: Displayed com.huaqin.factory/.MmiNewFpFodNitTestMainActivity for user 0: +125ms 行 30045: 09-04 09:17:16.344135 862 1210 I BufferQueueDebug: [c216a72 ActivityRecordInputSink com.huaqin.factory/.MmiNewFpFodNitTestMainActivity#1539](this:0xb400007bfc031fc8,id:-1,api:0,p:-1,c:-1) BufferQueue core=(862:/system/bin/surfaceflinger) 行 30067: 09-04 09:17:16.361263 5420 5420 D MmiNewFpFodNitTestMainActivity: onWindowFocusChanged: 行 30349: 09-04 09:17:16.838107 862 862 I SurfaceFlinger: onHandleDestroyed: name=Transition Root #148: ActivityRecord{7bd5340 u0 com.huaqin.factory/.MmiNewFpFodNitTestMainActivity t124}#1538, layerId=1538, parentId=0 行 30350: 09-04 09:17:16.842963 862 862 I BufferQueueDebug: [Transition Root #148: ActivityRecord{7bd5340 u0 com.huaqin.factory/.MmiNewFpFodNitTestMainActivity t124}#1538](this:0xb400007bfbfa39b8,id:-1,api:0,p:-1,c:862) onDestructor() 行 30449: 09-04 09:17:17.215113 5420 5420 D MmiNewFpFodNitTestMainActivity: segue callback 行 30450: 09-04 09:17:17.215133 5420 5420 D MmiNewFpFodNitTestMainActivity: ENTRY_HBM 行 30453: 09-04 09:17:17.216485 5420 5420 D MmiNewFpFodNitTestMainActivity: Execute command: echo 9 1 > /sys/class/mi_display/disp-DSI-0/disp_param 行 30455: 09-04 09:17:17.225545 5420 5420 D MmiNewFpFodNitTestMainActivity: Before test, set lock password as 0000 行 30456: 09-04 09:17:17.225592 5420 5420 D MmiNewFpFodNitTestMainActivity: setCredentialRequiredToDecrypt : reflect 行 30460: 09-04 09:17:17.225960 5420 5420 W System.err: at com.huaqin.factory.MmiNewFpFodNitTestMainActivity.setCredentialRequiredToDecrypt(MmiNewFpFodNitTestMainActivity.java:382) 行 30461: 09-04 09:17:17.225970 5420 5420 W System.err: at com.huaqin.factory.MmiNewFpFodNitTestMainActivity.setLockPassword(MmiNewFpFodNitTestMainActivity.java:370) 行 30462: 09-04 09:17:17.225979 5420 5420 W System.err: at com.huaqin.factory.MmiNewFpFodNitTestMainActivity.access$200(MmiNewFpFodNitTestMainActivity.java:46) 行 30463: 09-04 09:17:17.225990 5420 5420 W System.err: at com.huaqin.factory.MmiNewFpFodNitTestMainActivity$1.setPasswdAndEnrol(MmiNewFpFodNitTestMainActivity.java:195) 行 30495: 09-04 09:17:17.226381 5420 5420 D MmiNewFpFodNitTestMainActivity: createPassword : reflect 行 30496: 09-04 09:17:17.226516 5420 5420 D MmiNewFpFodNitTestMainActivity: createNone : reflect 行 30497: 09-04 09:17:17.226559 5420 5420 D MmiNewFpFodNitTestMainActivity: setLockCredential : reflect 行 30632: 09-04 09:17:17.449992 2096 2641 D KeyguardViewMediator: setKeyguardEnabled(true) 行 30633: 09-04 09:17:17.450055 2096 2641 D KeyguardViewMediator: previously hidden, reshowing, reenabling status bar expansion 行 30660: 09-04 09:17:17.454391 5420 5420 D MmiNewFpFodNitTestMainActivity: Base :>KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_UNKNOWN, scanCode=338, metaState=0, flags=0x8, repeatCount=0, eventTime=45209688985000, downTime=45209688985000, deviceId=6, source=0x101, displayId=-1 } 行 30680: 09-04 09:17:17.460096 5420 5420 D MmiNewFpFodNitTestMainActivity: onChallengeGenerated sensorId : 0,userId : 0,challenge : -8801697616163641421 行 30682: 09-04 09:17:17.460560 5420 5420 D MmiNewFpFodNitTestMainActivity: EnrolRunnable 行 30683: 09-04 09:17:17.460923 5420 7249 D MmiNewFpFodNitTestMainActivity: Start enrol(9) 行 30684: 09-04 09:17:17.461126 5420 7249 D MmiNewFpFodNitTestMainActivity: Process.myUid(): 0 行 30685: 09-04 09:17:17.461144 5420 7249 D MmiNewFpFodNitTestMainActivity: createPassword : reflect 行 30686: 09-04 09:17:17.461184 5420 7249 D MmiNewFpFodNitTestMainActivity: verifyCredential : reflect 行 30719: 09-04 09:17:17.486234 1656 1017 I PowerHalWrapper: amsBoostNotify pid:5420,activity:com.huaqin.factory.MmiNewFpFodNitTestMainActivity, package:com.huaqin.factory, mProcessCreatePackcom.huaqin.lcdtest 行 30721: 09-04 09:17:17.486755 1656 1017 I mtkpower_client: [PowerHal_Wrap_notifyAppState] com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity pid=5420 activityId:129848128 state:0 行 30722: 09-04 09:17:17.486902 1656 1017 I mtkpower_client: [Legacy][PowerHal_Wrap_notifyAppState] com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity pid=5420 state:129848128 行 30723: 09-04 09:17:17.487239 828 1022 I libPowerHal: [perfNotifyAppState] pack:com.huaqin.factory, act:com.huaqin.factory.MmiNewFpFodNitTestMainActivity, state:0, pid:5420, uid:1000, fps:120 行 30733: 09-04 09:17:17.494088 5420 5420 D MmiNewFpFodNitTestMainActivity: onPause() 行 30734: 09-04 09:17:17.494199 5420 5420 D MmiNewFpFodNitTestMainActivity: cancelEnrol() 行 30735: 09-04 09:17:17.494489 5420 5420 D MmiNewFpFodNitTestMainActivity: cancelVerify() 行 30736: 09-04 09:17:17.494597 5420 5420 D MmiNewFpFodNitTestMainActivity: removeFinger( 9 ) 行 30737: 09-04 09:17:17.495990 5420 5420 D MmiNewFpFodNitTestMainActivity: removeFinger( ) fingerId no exit 行 30738: 09-04 09:17:17.496092 5420 5420 D MmiNewFpFodNitTestMainActivity: After test, remove lock password 行 30739: 09-04 09:17:17.496109 5420 5420 D MmiNewFpFodNitTestMainActivity: createNone : reflect 行 30741: 09-04 09:17:17.496206 5420 5420 D MmiNewFpFodNitTestMainActivity: createPassword : reflect 行 30742: 09-04 09:17:17.496281 5420 5420 D MmiNewFpFodNitTestMainActivity: setLockCredential : reflect 行 30788: 09-04 09:17:17.537535 862 862 I SurfaceFlinger: onHandleDestroyed: name=c216a72 ActivityRecordInputSink com.huaqin.factory/.MmiNewFpFodNitTestMainActivity#1539, layerId=1539, parentId=0 行 30792: 09-04 09:17:17.545059 862 862 I BufferQueueDebug: [c216a72 ActivityRecordInputSink com.huaqin.factory/.MmiNewFpFodNitTestMainActivity#1539](this:0xb400007bfc031fc8,id:-1,api:0,p:-1,c:862) onDestructor() 行 30998: 09-04 09:17:17.759103 5420 7249 D MmiNewFpFodNitTestMainActivity: getGatekeeperPasswordHandle : reflect 行 30999: 09-04 09:17:17.759480 5420 7249 D MmiNewFpFodNitTestMainActivity: verifyGatekeeperPasswordHandle : reflect 行 31000: 09-04 09:17:17.760904 5420 7249 D MmiNewFpFodNitTestMainActivity: getGatekeeperHAT : reflect 行 31001: 09-04 09:17:17.761086 5420 7249 D MmiNewFpFodNitTestMainActivity: LockPatternUtils.verifyCredential() return token: null 行 31002: 09-04 09:17:17.761123 5420 7249 D MmiNewFpFodNitTestMainActivity: Please check your lockScreen passwork whether is 0000 行 31003: 09-04 09:17:17.762007 5420 7249 D MmiNewFpFodNitTestMainActivity: Only the original thread that created a view hierarchy can touch its views. Expected: main Calling: pool-4-thread-1 行 31006: 09-04 09:17:17.762538 5420 7249 D MmiNewFpFodNitTestMainActivity: test Fail 行 31011: 09-04 09:17:17.763522 5420 5420 D MmiNewFpFodNitTestMainActivity: restore system brightness value 行 31019: 09-04 09:17:17.770019 5420 5420 D MmiNewFpFodNitTestMainActivity: Execute command: echo 9 0 > /sys/class/mi_display/disp-DSI-0/disp_param 行 31053: 09-04 09:17:17.809310 5420 5420 D MmiNewFpFodNitTestMainActivity: Execute command: echo 4 -1 > /sys/class/mi_display/disp-DSI-0/disp_param 行 31069: 09-04 09:17:17.832175 5420 5420 D MmiNewFpFodNitTestMainActivity: Execute command: echo 0x2000000 > /sys/class/drm/card0-DSI-1/disp_param 行 31095: 09-04 09:17:17.850584 5420 5420 D MmiNewFpFodNitTestMainActivity: Process Error: sh: <stdin>[1]: can't create /sys/class/drm/card0-DSI-1/disp_param: Permission denied 行 31099: 09-04 09:17:17.854235 1656 1786 I PowerHalWrapper: amsBoostNotify pid:5420,activity:com.huaqin.factory.MmiNewFpFodNitTestMainActivity, package:com.huaqin.factory, mProcessCreatePackcom.huaqin.lcdtest 行 31101: 09-04 09:17:17.854520 1656 1786 I mtkpower_client: [PowerHal_Wrap_notifyAppState] com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity pid=5420 activityId:129848128 state:0 行 31102: 09-04 09:17:17.854612 1656 1786 I mtkpower_client: [Legacy][PowerHal_Wrap_notifyAppState] com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity pid=5420 state:129848128 行 31104: 09-04 09:17:17.855239 828 1022 I libPowerHal: [perfNotifyAppState] pack:com.huaqin.factory, act:com.huaqin.factory.MmiNewFpFodNitTestMainActivity, state:0, pid:5420, uid:1000, fps:120 行 31111: 09-04 09:17:17.861439 5420 5420 D VRI[MmiNewFpFodNitTestMainActivity]: visibilityChanged oldVisibility=true newVisibility=false 行 31116: 09-04 09:17:17.867813 862 862 I BufferQueueProducer: [com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity#1535](this:0xb400007bfc01d268,id:-1,api:0,p:-1,c:862) queueBuffer: fps=1.95 dur=1538.40 max=1439.10 min=8.34 行 31127: 09-04 09:17:17.881371 5420 5420 D MmiNewFpFodNitTestMainActivity: onStop() 行 31130: 09-04 09:17:17.884750 5420 7102 D BufferQueueProducer: [VRI[MmiNewFpFodNitTestMainActivity]#2(BLAST Consumer)2](id:152c00000002,api:1,p:5420,c:5420) disconnect: api 1 行 31132: 09-04 09:17:17.887257 5420 7102 D BLASTBufferQueue: [VRI[MmiNewFpFodNitTestMainActivity]#2](f:0,a:1) destructor() 行 31133: 09-04 09:17:17.887854 5420 7102 D BufferQueueConsumer: [VRI[MmiNewFpFodNitTestMainActivity]#2(BLAST Consumer)2](id:152c00000002,api:0,p:-1,c:5420) disconnect 行 31163: 09-04 09:17:17.926542 862 862 I SurfaceFlinger: onHandleDestroyed: name=com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity#1535, layerId=1535, parentId=0 行 31188: 09-04 09:17:17.934273 862 862 I BufferQueueDebug: [com.huaqin.factory/com.huaqin.factory.MmiNewFpFodNitTestMainActivity#1535](this:0xb400007bfc01d268,id:-1,api:0,p:-1,c:862) onDestructor() 行 31477: 09-04 09:17:18.197835 828 1022 I libPowerHal: [perfNotifyAppState] pack:com.huaqin.factory, act:com.huaqin.factory.MmiNewFpFodNitTestMainActivity, state:5, pid:5420, uid:1000, fps:-1 行 32016: 09-04 09:17:19.456368 2096 2641 D KeyguardViewMediator: setKeyguardEnabled(true) 行 32020: 09-04 09:17:19.457452 2096 2641 D KeyguardViewMediator: setKeyguardEnabled(false) 行 32022: 09-04 09:17:19.459156 2096 2641 D KeyguardViewMediator: remembering to reshow, hiding keyguard, disabling status bar expansion 行 32026: 09-04 09:17:19.459839 2096 2641 D KeyguardViewMediator: setKeyguardEnabled(false) 行 32028: 09-04 09:17:19.461840 2096 2641 D KeyguardViewMediator: remembering to reshow, hiding keyguard, disabling status bar expansion 结合这段log和上面的代码分析下流程

DALVIK THREADS (261): "main" prio=5 tid=1 Runnable | group="main" sCount=0 ucsCount=0 flags=0 obj=0x7271e8c8 self=0xb400007852478c00 | sysTid=4102 nice=-10 cgrp=top-app sched=0/0 handle=0x7915495d28 | state=R schedstat=( 268220694457 159982194030 599140 ) utm=18413 stm=8408 core=6 HZ=100 | stack=0x7fe44e6000-0x7fe44e8000 stackSize=8188KB | held mutexes= "mutator lock"(shared held) at com.oplusos.systemui.common.util.LogUtil.d$default(unavailable:0) at com.oplusos.systemui.common.util.LogUtil.d(LogUtil.kt:0) at com.oplus.systemui.aod.common.AodManager.resetRotationWhilePowerOff(AodManager.java:208) at com.oplus.systemui.aod.display.AODDisplayUtil.onFinishedWakingUp(AODDisplayUtil.java:383) at com.oplus.systemui.aod.display.SmoothTransitionController$mWakefullnessLifeLifecycle$1.onFinishedWakingUp(SmoothTransitionController.kt:142) at com.android.systemui.keyguard.WakefulnessLifecycle$$ExternalSyntheticLambda2.accept(R8$$SyntheticClass:0) at com.android.systemui.keyguard.Lifecycle.lambda$dispatch$1(Lifecycle.java:49) at com.android.systemui.keyguard.Lifecycle.$r8$lambda$K7H-EqyxFiqZEuM4H7Ktyop3hSQ(Lifecycle.java:0) at com.android.systemui.keyguard.Lifecycle$$ExternalSyntheticLambda1.invoke(R8$$SyntheticClass:0) at com.android.app.tracing.TraceUtils.trace(TraceUtils.kt:118) at com.android.systemui.keyguard.Lifecycle.dispatch(Lifecycle.java:48) at com.android.systemui.keyguard.WakefulnessLifecycle.dispatchFinishedWakingUp(WakefulnessLifecycle.java:174) at com.android.systemui.keyguard.KeyguardLifecyclesDispatcher$KeyguardLifecycleHandler.handleMessage(KeyguardLifecyclesDispatcher.java:142) at android.os.Handler.dispatchMessage(Handler.java:107) at android.os.Looper.loopOnce(Looper.java:282) at android.os.Looper.loop(Looper.java:387) at android.app.ActivityThread.main(ActivityThread.java:9494) at java.lang.reflect.Method.invoke(Native method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:60

行 172083: 06-18 21:31:50.125 04686 04686 W SystemUi--Keyguard: OplusPreventModeExImpl-->proximity sensor had unregistered, or not registered 行 172772: 06-18 21:31:50.172 03620 04065 D DisplayPowerController[0]: requestPowerState: policy=BRIGHT, useProximitySensor=false, screenBrightnessOverride=5926.9, useAutoBrightness=false, screenAutoBrightnessAdjustmentOverride=NaN, screenLowPowerBrightnessFactor=1.0, blockScreenOn=false, lowPowerMode=false, boostScreenBrightness=false, dozeScreenBrightness=NaN, dozeScreenState=UNKNOWN, dozeScreenStateReason=DEFAULT_POLICY, waitForNegativeProximity=false displayReady=false pendingRequest=true 行 172773: 06-18 21:31:50.172 03620 04065 D DisplayManagerServiceExtImpl: request size(1,1),dpc=com.android.server.display.DisplayPowerController@a6d226b size(0,2),flags=0X200F,id(0,0,local:4630946734104264082),enable=true,ready=false,waitForNegativeProximity=false policy=BRIGHT,useProximitySensor=false,dozeState=UNKNOWN,screenBrightnessOverride=5926.899902,useAuto=false,lowPower=false,lowPowerFactor=1.000000 行 225396: "android.sensor.proximity" : C:\Users\V54939878\Desktop\sensor异常\Logs_1024625E5614167111111370_214402--plsensor灯周期性亮\files\Log\2025-06-18_21-42-27@sensor\common\ap_log\2025-06-18_21-29-21\android_log_20250618_213328.txt (匹配10次) 行 291860: 06-18 21:34:23.276 03620 04065 D DisplayPowerController[0]: requestPowerState: policy=BRIGHT, useProximitySensor=false, screenBrightnessOverride=-1.0, useAutoBrightness=false, screenAutoBrightnessAdjustmentOverride=NaN, screenLowPowerBrightnessFactor=1.0, blockScreenOn=false, lowPowerMode=false, boostScreenBrightness=false, dozeScreenBrightness=NaN, dozeScreenState=UNKNOWN, dozeScreenStateReason=DEFAULT_POLICY, waitForNegativeProximity=false displayReady=false pendingRequest=true 行 291863: 06-18 21:34:23.276 03620 04065 D DisplayManagerServiceExtImpl: request size(1,1),dpc=com.android.server.display.DisplayPowerController@a6d226b size(0,2),flags=0X200F,id(0,0,local:4630946734104264082),enable=true,ready=false,waitForNegativeProximity=false policy=BRIGHT,useProximitySensor=false,dozeState=UNKNOWN,screenBrightnessOverride=-1.000000,useAuto=false,lowPower=false,lowPowerFactor=1.000000 行 299362: 06-18 21:34:23.922 04686 04686 W SystemUi--Keyguard: OplusPreventModeExImpl-->proximity sensor had unregistered, or not registered 行 319225: 06-18 21:34:25.968 03620 04065 D DisplayPowerController[0]: requestPowerState: policy=BRIGHT, useProximitySensor=false, screenBrightnessOverride=8467.0, useAutoBrightness=false, screenAutoBrightnessAdjustmentOverride=NaN, screenLowPowerBrightnessFactor=1.0, blockScreenOn=false, lowPowerMode=false, boostScreenBrightness=false, dozeScreenBrightness=NaN, dozeScreenState=UNKNOWN, dozeScreenStateReason=DEFAULT_POLICY, waitForNegativeProximity=false displayReady=false pendingRequest=true 行 319226: 06-18 21:34:25.969 03620 04065 D DisplayManagerServiceExtImpl: request size(1,1),dpc=com.android.server.display.DisplayPowerController@a6d226b size(0,2),flags=0X200F,id(0,0,local:4630946734104264082),enable=true,ready=false,waitForNegativeProximity=false policy=BRIGHT,useProximitySensor=false,dozeState=UNKNOWN,screenBrightnessOverride=8467.000000,useAuto=false,lowPower=false,lowPowerFactor=1.000000 行 320220: 06-18 21:34:26.121 04686 04686 W SystemUi--Keyguard: OplusPreventModeExImpl-->proximity sensor had unregistered, or not registered C:\Users\V54939878\Desktop\sensor异常\Logs_1024625E5614167111111370_214402--plsensor灯周期性亮\files\Log\2025-06-18_21-42-27@sensor\common\ap_log\2025-06-18_21-29-21\android_log_20250618_213546.txt (匹配8次) 行 331954: 06-18 21:39:54.170 03620 04065 D DisplayPowerController[0]: requestPowerState: policy=BRIGHT, useProximitySensor=false, screenBrightnessOverride=-1.0, useAutoBrightness=false, screenAutoBrightnessAdjustmentOverride=NaN, screenLowPowerBrightnessFactor=1.0, blockScreenOn=false, lowPowerMode=false, boostScreenBrightness=false, dozeScreenBrightness=NaN, dozeScreenState=UNKNOWN, dozeScreenStateReason=DEFAULT_POLICY, waitForNegativeProximity=false displayReady=false pendingRequest=true 行 331966: 06-18 21:39:54.170 03620 04065 D DisplayManagerServiceExtImpl: request size(1,1),dpc=com.android.server.display.DisplayPowerController@a6d226b size(0,2),flags=0X200F,id(0,0,local:4630946734104264082),enable=true,ready=false,waitForNegativeProximity=false policy=BRIGHT,useProximitySensor=false,dozeState=UNKNOWN,screenBrightnessOverride=-1.000000,useAuto=false,lowPower=false,lowPowerFactor=1.000000 行 334552: 06-18 21:39:54.375 03620 04065 D DisplayPowerController[0]: requestPowerState: policy=BRIGHT, useProximitySensor=false, screenBrightnessOverride=5926.9, useAutoBrightness=false, screenAutoBrightnessAdjustmentOverride=NaN, screenLowPowerBrightnessFactor=1.0, blockScreenOn=false, lowPowerMode=false, boostScreenBrightness=false, dozeScreenBrightness=NaN, dozeScreenState=UNKNOWN, dozeScreenStateReason=DEFAULT_POLICY, waitForNegativeProximity=false displayReady=false pendingRequest=true 行 334557: 06-18 21:39:54.375 03620 04065 D DisplayManagerServiceExtImpl: request size(1,1),dpc=com.android.server.display.DisplayPowerController@a6d226b size(0,2),flags=0X200F,id(0,0,local:4630946734104264082),enable=true,ready=false,waitForNegativeProximity=false policy=BRIGHT,useProximitySensor=false,dozeState=UNKNOWN,screenBrightnessOverride=5926.899902,useAuto=false,lowPower=false,lowPowerFactor=1.000000 C:\Users\V54939878\Desktop\sensor异常\Logs_1024625E5614167111111370_214402--plsensor灯周期性亮\files\Log\2025-06-18_21-42-27@sensor\common\ap_log\2025-06-18_21-29-21\android_log_20250618_214007.txt (匹配15次) 行 59956: 06-18 21:40:13.114 03620 04065 D DisplayPowerController[0]: requestPowerState: policy=BRIGHT, useProximitySensor=false, screenBrightnessOverride=-1.0, useAutoBrightness=false, screenAutoBrightnessAdjustmentOverride=NaN, screenLowPowerBrightnessFactor=1.0, blockScreenOn=false, lowPowerMode=false, boostScreenBrightness=false, dozeScreenBrightness=NaN, dozeScreenState=UNKNOWN, dozeScreenStateReason=DEFAULT_POLICY, waitForNegativeProximity=false displayReady=false pendingRequest=true 行 59958: 06-18 21:40:13.114 03620 04065 D DisplayManagerServiceExtImpl: request size(1,1),dpc=com.android.server.display.DisplayPowerController@a6d226b size(0,2),flags=0X200F,id(0,0,local:4630946734104264082),enable=true,ready=false,waitForNegativeProximity=false policy=BRIGHT,useProximitySensor=false,dozeState=UNKNOWN,screenBrightnessOverride=-1.000000,useAuto=false,lowPower=false,lowPowerFactor=1.000000 行 70920: 06-18 21:40:13.764 04686 04686 W SystemUi--Keyguard: OplusPreventModeExImpl-->proximity sensor had unregistered, or not registered 行 149116: 06-18 21:40:21.601 03620 04065 D DisplayPowerController[0]: requestPowerState: policy=BRIGHT, useProximitySensor=false, screenBrightnessOverride=5926.9, useAutoBrightness=false, screenAutoBrightnessAdjustmentOverride=NaN, screenLowPowerBrightnessFactor=1.0, blockScreenOn=false, lowPowerMode=false, boostScreenBrightness=false, dozeScreenBrightness=NaN, dozeScreenState=UNKNOWN, dozeScreenStateReason=DEFAULT_POLICY, waitForNegativeProximity=false displayReady=false pendingRequest=true 行 149117: 06-18 21:40:21.602 03620 04065 D DisplayManagerServiceExtImpl: request size(1,1),dpc=com.android.server.display.DisplayPowerController@a6d226b size(0,2),flags=0X200F,id(0,0,local:4630946734104264082),enable=true,ready=false,waitForNegativeProximity=false policy=BRIGHT,useProximitySensor=false,dozeState=UNKNOWN,screenBrightnessOverride=5926.899902,useAuto=false,lowPower=false,lowPowerFactor=1.000000 行 152154: 06-18 21:40:21.725 04686 04686 W SystemUi--Keyguard: OplusPreventModeExImpl-->proximity sensor had unregistered, or not registered 行 267904: 06-18 21:40:33.242 04686 04686 W SystemUi--Keyguard: OplusPreventModeExImpl-->proximity sensor had unregistered, or not registered 行 268505: 06-18 21:40:33.274 03620 04065 D DisplayPowerController[0]: requestPowerState: policy=BRIGHT, useProximitySensor=false, screenBrightnessOverride=-1.0, useAutoBrightness=false, screenAutoBrightnessAdjustmentOverride=NaN, screenLowPowerBrightnessFactor=1.0, blockScreenOn=false, lowPowerMode=false, boostScreenBrightness=false, dozeScreenBrightness=NaN, dozeScreenState=UNKNOWN, dozeScreenStateReason=DEFAULT_POLICY, waitForNegativeProximity=false displayReady=false pendingRequest=true 行 268507: 06-18 21:40:33.274 03620 04065 D DisplayManagerServiceExtImpl: request size(1,1),dpc=com.android.server.display.DisplayPowerController@a6d226b size(0,2),flags=0X200F,id(0,0,local:4630946734104264082),enable=true,ready=false,waitForNegativeProximity=false policy=BRIGHT,useProximitySensor=false,dozeState=UNKNOWN,screenBrightnessOverride=-1.000000,useAuto=false,lowPower=false,lowPowerFactor=1.000000 根据这份log,分析ProximitySensor是被谁调用了,并且状态是什么

MediaSessionService: dispatchVolumeKeyEvent, pkg=com.sgrl.pjj.factorymode, opPkg=com.sgrl.pjj.factorymode, pid=8753, uid=1000, asSystem=true, event=KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_VOLUME_DOWN, scanCode=114, metaState=0, flags=0x8, repeatCount=18, eventTime=424403976947, downTime=422339335000, deviceId=2, source=0x101, displayId=-1 }, stream=-2147483648, musicOnly=false 01-01 14:38:38.737202 1468 6566 D MediaSessionService: Adjusting suggestedStream=-2147483648 by -1. flags=4113, preferSuggestedStream=false, session=null 01-01 14:38:38.767065 2994 3482 I vol.Events: writeEvent level_changed STREAM_MUSIC 14 01-01 14:38:38.771218 2994 3482 I vol.Events: writeEvent key STREAM_MUSIC 14 01-01 14:38:38.781765 8753 8753 D VUMeter : amplitude =854 01-01 14:38:38.781907 8753 8753 D VUMeter : mCurrentAngle = 0.7897484 01-01 14:38:38.788692 2994 2994 I vol.VolumeDialogImpl: showH r=volume_changed 01-01 14:38:38.789350 2994 2994 I vol.VolumeDialogImpl: rescheduleTimeout 3000 com.android.systemui.volume.VolumeDialogImpl.-$$Nest$mshowH:45 01-01 14:38:38.790324 2994 2994 I vol.Events: writeEvent show_dialog volume_changed keyguard=false 01-01 14:38:38.790379 1468 6566 D MediaSessionService: dispatchVolumeKeyEvent, pkg=com.sgrl.pjj.factorymode, opPkg=com.sgrl.pjj.factorymode, pid=8753, uid=1000, asSystem=true, event=KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_VOLUME_DOWN, scanCode=114, metaState=0, flags=0x8, repeatCount=19, eventTime=424454178870, downTime=422339335000, deviceId=2, source=0x101, displayId=-1 }, stream=-2147483648, musicOnly=false 01-01 14:38:38.790621 1468 6566 D MediaSessionService: Adjusting suggestedStream=-2147483648 by -1. flags=4113, preferSuggestedStream=false, session=null 01-01 14:38:38.798833 786 886 I libPerfCtl: xgfGetFPS pid:2994 fps:57 01-01 14:38:38.798955 786 886 I libPerfCtl: xgfGetFPS pid:8753 fps:23 01-01 14:38:38.798973 786 886 I libPowerHal: [updateFPS] pid(8753) : -1 => 60 01-01 14:38:38.799314 786 906 I libPowerHal: [perfNotifyAppState] pack:com.sgrl.pjj.factorymode, act:com.sgrl.pjj.factorymode.testItem.MicTestActivity, state:5, pid:8753, uid:1000, fps:60 01-01 14:38:38.801122 786 906 E UxUtility: notifyAppState error = NULL 01-01 14:38:38.801175 786 906 I TouchUtility: notifyAppState error = NULL 01-01 14:38:38.810670 2994 3482 I vol.Events: writeEvent level_changed STREAM_MUSIC 13 01-01 14:38:38.813463 2994 3482 I vol.Events: writeEvent key STREAM_MUSIC 13 01-01 14:38:38.816819 2994 2994 D vol.VolumeDialogImpl: onAnimationCancel 01-01 14:38:38.820277 2994 2994 I vol.VolumeDialogImpl: showH r=volume_changed 01-01 14:38:38.820677 2994 2994 I vol.VolumeDialogImpl: rescheduleTimeout 3000 com.android.systemui.volume.VolumeDialogImpl.-$$Nest$mshowH:45 01-01 14:38:38.821256 2994 2994 I vol.Events: writeEvent show_dialog volume_changed keyguard=false 01-01 14:38:38.836439 1468 4396 D MediaSessionService: dispatchVolumeKeyEvent, pkg=com.sgrl.pjj.factorymode, opPkg=com.sgrl.pjj.factorymode, pid=8753, uid=1000, asSystem=true, event=KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_VOLUME_DOWN, scanCode=114, metaState=0, flags=0x8, repeatCount=20, eventTime=424504556332, downTime=422339335000, deviceId=2, source=0x101, displayId=-1 }, stream=-2147483648, musicOnly=false 01-01 14:38:38.836845 1468 4396 D MediaSessionService: Adjusting suggestedStream=-2147483648 by -1. flags=4113, preferSuggestedStream=false, session=null 01-01 14:38:38.865736 8753 8753 D VUMeter : amplitude =930 01-01 14:38:38.865825 8753 8753 D VUMeter : mCurrentAngle = 0.60974836 01-01 14:38:38.872666 2994 3482 I vol.Events: writeEvent level_changed STREAM_MUSIC 12 01-01 14:38:38.875468 2994 3482 I vol.Events: writeEvent key STREAM_MUSIC 12请分析这段log内容

11ne 2oo- Uo 04 U5 45,“2 ,“ 0 32 SEeTTOE TlohOI00S Parcel.createrxce0tl0nParcel,ava.2U6. 26689: 06-04 09:49:22.363 Line 716 1382 DQSEECOM SAMPE: readCert:Reading from TEE file FIE11 Line 1382 E QSEECOM SAMPLE CENT: 26728: 06-04 09:49:22.438 716 readCert: Failed to read from TEE file FIEll, data len=-1 Line 26729: 06-04 09:49:22.438 2644 2644 E BoxService:[RsAUtils]:readPublicDataFromTEE data failed, size=0 Line 06-04 3921 12726 四 at android.os.Parcel.createException(Parcel.iava:2085) 26878: 09:49:22 777 Keystore: Line 27033: 06-04 09:49:23.308 3921 12726 W KeyStore: at android.os.Parcel.createException(Parcel.java:2085) Line 1382 D OSEECOM SAMPLE CLIENT:: readcert: Reading from TEE file FILE11 27103: 06-04 09:49:23.447 716 Line 27130: 06-04 716 1382 E OSEECOM SAMPLE CLIENT: : readcert: Failed to read from mEE file FIuE11, data len=-1 09:49:23.501 Line 27131: 06-04 09:49:23.501 2644 2644 E TBoxService: [RsAUtilsl:readPublicDatarromrEr data failed, size=0 Line 27224: 06-04 09:49:23.807 3921 12726 w KeyStore: at android.os.Parcel.createException(Parcel.java:2085) Line 27429: 06-04 09:49:24.504 716 1382 D OSEECOM SAMPLE CLIENT: : readcert: Reading from TEE file FILE11 Line 27460: 06-04 09:49:24.569 716 1382 E OSEECOM SAMPIE CIIENr: : readcert: Failed to read from rEE file FIlE11, data len=-1 Line 27461 : 06-04 .569 2644 2644 E TBoxService:[RSAUtilsl:readPublicDataFromTEE data failed,size=0 a."a.?" Line 27532: 06-04 09: :49:24 .775 3921 12726 W Kevstore: at android.os.Parcel.createException(Parcel.java:2085) Line 27609: 0E12 -49-24 .920 716 1382 D OSEECOM SAMPLE CLIENT: readcert: Reading from TEE file FIE12 Line 27666: :49:24.988 716 1382 E QSEECOM SAMPLE CLIENT: Failed to read from TEE file FIE12,data len=-1 06-04 19: readcert: Line 27667: 988 1255 1410 E NAD Commutil:ReadKevEromTEE 06- D :49-24 Read Key failed!ret Line 27675 : 05-04 09: :49:24 999 716 716 D QSEECOM SAMPLE CLIENT:: readcert:Reading from TEE file FE13 Line 27706: 0 6- 19:49:25 024 3921 12726 可 Kevstore: at android.os. .Parcel.createException(Parcel.java:2085) Line 27721: 06- 04 09:49:25 028 3921 16137 双 Keystore: at android.os.Parcel.createException(Parcel.java:2085) Line 27751: 06- 09:49:25 048 3921 16137 WKevstore: at android.os,Parcel .createException(Parcel.iava:2085) TEE file FIr13, data len=-1 Line 27781: 06-0 09:49:25 053 716 R OSEECOM SAMPLE CLTENT: read from 27782: 09:49:25. ine 06-04 054 255 410 NAD Com omut 1.1.: Line 28305: 09:49:26 3921 2726 レ自镯筒誇逞 Kevstor iawa:2085)

01-01 19:26:55.627 01566 01670 D APM_AudioPolicyManager: setVolumeCurveIndex device 00000002, index 14 01-01 19:26:55.628 02924 02924 D HardwarePropertiesManagerService-JNI: Link to death notification successful 01-01 19:26:55.629 02924 02924 D SystemServerTiming: StartTwilightService 01-01 19:26:55.629 02924 02924 I SystemServiceManager: Starting com.android.server.twilight.TwilightService 01-01 19:26:55.629 00903 00903 I hwservicemanager: getTransport: Cannot find entry [email protected]::IUsbGadget/default in either framework or device VINTF manifest. 01-01 19:26:55.629 02924 02924 D SystemServerTiming: StartColorDisplay 01-01 19:26:55.629 02924 03359 D AS.AudioService: setStreamVolumeIndexAS(8, 14, 1073741824) 01-01 19:26:55.630 02924 02924 I SystemServiceManager: Starting com.android.server.display.color.ColorDisplayService 01-01 19:26:55.630 01566 01670 D APM_AudioPolicyManager: setVolumeCurveIndex device 40000000, index 14 01-01 19:26:55.630 02924 03113 E UsbDeviceManager: connectToProxy: usb gadget hidl hal service not found. java.util.NoSuchElementException at android.os.HwBinder.getService(Native Method) at android.hardware.usb.gadget.V1_0.IUsbGadget.getService(IUsbGadget.java:57) at android.hardware.usb.gadget.V1_0.IUsbGadget.getService(IUsbGadget.java:64) at com.android.server.usb.hal.gadget.UsbGadgetHidl.isServicePresent(UsbGadgetHidl.java:141) at com.android.server.usb.hal.gadget.UsbGadgetHalInstance.getInstance(UsbGadgetHalInstance.java:39) at com.android.server.usb.UsbDeviceManager.<init>(UsbDeviceManager.java:332) at com.android.server.usb.UsbService.<init>(UsbService.java:205) at com.android.server.usb.UsbService$Lifecycle.lambda$onStart$0(UsbService.java:113) at com.android.server.usb.UsbService$Lifecycle.$r8$lambda$HIZVSW8uTg1XjWF6etZh-bC1WP4(Unknown Source:0) at com.android.server.usb.UsbService$Lifecycle$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0) at com.android.server.SystemServerInitThreadPool.lambda$submitTask$0(SystemServerInitThreadPool.java:107) at com.android.server.SystemServerInitThreadPool.$r8$lambda$KBkrFsHiqcxWyjNRg1WxRI4WNHA(Unknown Source:0) at com.android.server.SystemServerInitThreadPool$$ExternalSyntheticLambda1.run(D8$$SyntheticClass:0) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487) at java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644) at com.android.internal.util.ConcurrentUtils$1$1.run(ConcurrentUtils.java:65) 01-01 19:26:55.630 02924 03113 E UsbPortManager: USB Gadget HAL AIDL/HIDL not present 01-01 19:26:55.630 02924 03113 D UsbDeviceManager: getInstance done 01-01 19:26:55.630 02924 03359 D AS.AudioService: setStreamVolumeIndexAS(8, 14, 2) 01-01 19:26:55.631 02924 02924 D OplusFeatureColorMode: Color mode mIsFeatureOn=truetype=false 01-01 19:26:55.631 01566 01670 D APM_AudioPolicyManager: setVolumeCurveIndex device 00000002, index 14 01-01 19:26:55.632 02924 03359 D AS.AudioService: setStreamVolumeIndexAS(9, 10, 1073741824) 01-01 19:26:55.633 01566 01670 D APM_AudioPolicyManager: setVolumeCurveIndex device 40000000, index 10 01-01 19:26:55.633 02924 03113 W StorageManagerService: No primary storage defined yet; hacking together a stub 01-01 19:26:55.634 02924 03359 D AS.AudioService: setStreamVolumeIndexAS(10, 10, 1073741824) 01-01 19:26:55.634 02924 02924 D OplusVisionCorrectionManager: VisionCorrectionContentObserver: <init> 01-01 19:26:55.634 01566 01670 D APM_AudioPolicyManager: setVolumeCurveIndex device 40000000, index 10 01-01 19:26:55.636 02924 03113 I UsbDeviceManager: mResetUsbGadgetDisableDebounce:false connected:0configured:0 01-01 19:26:55.636 02924 03359 D AS.AudioService: setStreamVolumeIndexAS(11, 10, 1073741824) 01-01 19:26:55.636 02924 03113 I UsbDeviceManager: removeMessages MSG_UPDATE_STATE 01-01 19:26:55.636 01566 01670 D APM_AudioPolicyManager: setVolumeCurveIndex device 40000000, index 10 01-01 19:26:55.636 02924 02924 D OplusFeatureGameColorEnhance: game color enhance not support. 01-01 19:26:55.637 02924 03113 I OplusServiceFactoryImpl: get feature:IOplusUsbDeviceFeature 01-01 19:26:55.638 02924 03113 D OplusUsbDeviceFeature: USB IChargerService: vendor.oplus.hardware.charger.ICharger$Stub$Proxy@bbc502e 01-01 19:26:55.638 02924 03113 D OplusUsbDeviceFeature: getInstance sOplusUsbDeviceFeature 01-01 19:26:55.638 02924 03113 I OplusUsbDeviceFeature: init OplusUsbDeviceFeature

大家在看

recommend-type

文星小标宋字体

文星小标宋题字体下载,大家可以无需积分下载,旨在分享。
recommend-type

2000-2022年全国省份农业绿色全要素生产率:超效率SBM投入导向VRS/非期望产出SBM投入导向(全新整理)

1、资源内容地址:https://blog.csdn.net/2301_79696294/article/details/141441843 2、代码特点:今年全新,手工精心整理,放心引用,数据来自权威,相对于其他人的控制变量数据准确很多,适合写论文做实证用 ,不会出现数据造假问题 3、适用对象:大学生,本科生,研究生小白可用,容易上手!!! 3、课程引用: 经济学,地理学,城市规划与城市研究,公共政策与管理,社会学,商业与管理 ## 数据指标说明 资源名称:农业绿色全要素生产率 省份层面数据时间:2003-2022年 农业绿色全要素生产率 超效率SBM投入导向VRS/非期望产出SBM投入导向 变量指标 指标说明 资本投入 农业全社会固定资产投资额(亿元)最新2022年版! 劳动投入 农业从业人员数(万人) 土地资源投入 农作物播种面积(千公顷) 灌溉投入 有效灌溉面积(千公顷) 农药投入 农药施用量(万吨) 化肥投入 化肥施用(折纯)量(万吨) 农膜投入 农膜使用量(
recommend-type

宏碁Acer 4741G驱动合集 for winxp 官方版_宏碁个人笔记本XP驱动

宏碁Acer4741G驱动合集包含了显卡、网卡、声卡等驱动,都是xp版本,因为笔记本自带win7系统,有想要装xp系统的就需要这个驱动包。哈哈,买回来的Acer4741G,宏基的本本,性价比高,I5的CPU才4K多点,系统是win7家庭版,感觉还是XP好用,就要换回来了,想把驱动找全,欢迎下载体验
recommend-type

java读取kml文件数据

自己做的用java读取kml文件数据,并保存为json文件。方便其它地方解析。
recommend-type

无线系统中的微波与射频.rar

电子科技大学,研究生专业选修课矩无线系统中的微波与射频ppt,压缩包内包含无线系统中的微波与射频全部章节ppt。供电子科大研究生学习复习使用,请勿乱传。

最新推荐

recommend-type

perl-Plack-Middleware-ReverseProxy-0.16-9.el8.tar.gz

# 适用操作系统:Centos8 #Step1、解压 tar -zxvf xxx.el8.tar.gz #Step2、进入解压后的目录,执行安装 sudo rpm -ivh *.rpm
recommend-type

SHFE.ag 2022年全年tick指数,自己合成的单品种指数(tick级),自有版权,全网独家

指数相比主连数据,更能反映该品种的波动情况,换月时没有跳空,不管回测还是实盘,都更科学。 按照每天最大和第二大openint字段作为vwap依据(参考南华指数编制规则),数据为自采后,用kdb经过算法合成,本人拥有完全知识产权,请勿二次销售。 可广泛应用于量化深度学习训练、高精度回测、portfolio构建、科学研究等,数据为csv格式,可导入任何数据库。 压缩包已加密,密码为csdnexthe,有问题请留言或者私信 示例数据: datetime,price,size,openint 2016-01-04 09:00:00.500,3204,258,502814 2016-01-04 09:00:01.000,3203,310,502994 2016-01-04 09:00:01.500,3201,580,503092 2016-01-04 09:00:02.000,3203,158,503160 2016-01-04 09:00:02.500,3201,74,503172 2016-01-04 09:00:03.000,3201,120,503200 2016-01-04 09:00:03.500,3202,50,503162 2016-01-04 09:00:04.000,3202,6,503160
recommend-type

基于SpringSpringMvCMyBatis框架开发的冷链运输全流程智能管理系统-包含温度监控-车辆调度-货物追踪-仓储管理-订单处理-报表统计-异常预警-用户权限-数据可.zip

ccs基于SpringSpringMvCMyBatis框架开发的冷链运输全流程智能管理系统_包含温度监控_车辆调度_货物追踪_仓储管理_订单处理_报表统计_异常预警_用户权限_数据可.zip
recommend-type

诺基亚jquery-mobile例十七

codechthridea3-4.html
recommend-type

ds883-zynq-rfsoc-dfe-overview_中英文对照版_2025年.pdf

ds883-zynq-rfsoc-dfe-overview_中英文对照版_2025年
recommend-type

HTML时间格式化工具及测试页面介绍

标题 "BoolStudio.github.io" 暗示这是一个与GitHub相关的在线资源,具体来说是与BoolStudio相关的网页地址。GitHub是一个著名的代码托管平台,它支持Git版本控制系统,允许用户在云端存储和共享代码。BoolStudio可能是GitHub上的一个用户或组织账户名称,而该页面可能是他们托管的项目或个人页面的入口。 描述中的信息包含了HTML元素和JavaScript代码片段。这段描述展示了一个测试页文件的部分代码,涉及到HTML的标题(title)和内嵌框架(iframe)的使用,以及JavaScript中Date对象的扩展功能。 从描述中我们可以分析出以下知识点: 1. HTML标题(Title): 在HTML中,`<title>`标签用于定义网页的标题,它会显示在浏览器的标题栏或页面的标签上。在描述中出现了`<title>现在时间</title>`,这表明网页的标题被设置为了“现在时间”。 2. 微软时间: 这可能指的是在网页中嵌入微软产品的日期和时间显示。尽管这部分内容在描述中被删除了,但微软时间通常与Windows操作系统的日期和时间显示相关联。 3. iframe元素: `<iframe>`标签定义了一个内嵌框架,可以在网页中嵌入另一个文档。在描述中出现的是`<iframe src"></iframe>`,这表示创建了一个空的iframe元素,其src属性为空,实际上没有嵌入任何内容。通常src属性会被设置为另一个HTML文档的URL,用来在当前页面中显示外部页面的内容。 4. JavaScript日期格式化: 描述中包含了一段JavaScript代码,这段代码扩展了Date对象的功能,允许它根据提供的格式字符串(fmt)返回格式化的日期和时间。例如,如果fmt是'y年M月d日 h时m分s秒',则该函数会按照这个格式返回当前日期和时间。 具体到代码实现,以下步骤展示了如何在JavaScript中扩展Date对象并格式化日期: - 首先创建了一个对象o,该对象包含日期和时间的不同部分,例如年(y)、月(M)、日(d)、时(h)、分(m)、秒(s)。 - 使用正则表达式检查格式字符串fmt中是否包含年份的占位符(y+),如果存在则将其替换为四位数的年份,不足部分用0补齐。 - 使用for...in循环遍历对象o中的每一个键值对,并使用正则表达式测试这些键(如年、月、日等)是否在格式字符串中存在。如果存在,则替换为相应的日期时间值。 这个知识点展示了在JavaScript中如何自定义对象的方法,以及如何使用正则表达式进行字符串的搜索和替换。 标签 "HTML" 表明这个文件主要涉及到超文本标记语言(HTML),这是构建网页内容的标准标记语言,它允许开发者使用标签来定义网页的结构和内容。HTML文件通常包含各种元素,如段落、链接、图片、表格和表单等。 压缩包子文件的文件名称列表中的 "BoolStudio.github.io-main" 可能指的是一个包含 "BoolStudio.github.io" 网站主要文件的压缩包。通常,网站项目会包含多个文件和资源,为了便于管理和分发,开发者会将这些文件打包成一个压缩文件。在本例中,"main" 可能表示该压缩包包含了网站的主要文件和代码。 通过对给定文件信息的分析,我们可以了解到网页设计和开发的相关知识点,特别是HTML文档结构、JavaScript对象和函数扩展以及如何在网站项目中组织文件。这些知识对于前端开发者来说是非常重要的,能够帮助他们创建更加动态和功能丰富的网页应用。
recommend-type

Elixir测试:从用例执行到覆盖率分析

### Elixir 测试:从用例执行到覆盖率分析 #### 1. 测试用例执行 在测试中,以 `Test` 结尾且包含 `use ExUnit` 的模块被视为测试用例。测试用例本质上是设置回调和测试的集合。测试用例的执行方式有两种:并发执行或顺序执行。使用 `async: true` 选项的测试用例将并发执行,其余的则按定义顺序(默认随机)顺序执行。 测试用例的执行流程如下: 1. 执行所有 `setup_all` 回调。 2. 执行所有测试及其特定的设置和拆卸回调。 `setup_all` 回调按定义顺序在同一进程中执行。在运行任何测试之前,测试用例将生成一个进程,在该进程中运行所有
recommend-type

Android Studio 时间延时

<think> 我们参考多个引用,总结在Android Studio中实现时间延时的方法。根据引用[1]和[2],我们知道有几种常见的延时方法,包括使用Handler的postDelayed方法、使用Timer和TimerTask以及使用Thread.sleep。引用[3]和[5]则展示了具体代码示例。 具体方法如下: 1. **使用Handler的postDelayed方法**(推荐在主线程中使用,避免直接操作UI线程的问题): ```java new Handler().postDelayed(new Runnable() { @Override
recommend-type

IMS Open Corpus Workbench:打造高效大型文本语料库管理工具

IMS Open Corpus Workbench(以下简称CWB)是一个强大的开源工具集,它专门用于管理和查询大型的、带有语言注释的文本语料库。这项工具有着广泛的应用领域,包括语言学研究、自然语言处理、人文科学研究等。 ### 标题知识点: #### 大型文本语料库的索引和查询工具 大型文本语料库指的是含有大量文本数据的数据库,其中包含的文本量通常以百万计。这些数据可能是书面文本、口语录音文字转写等形式。对于如此庞大的数据集,索引是必要的,它可以帮助研究者快速定位到感兴趣的片段,而查询工具则提供了从这些大量数据中提取特定信息的能力。 #### 开源 CWB作为一个开源工具,意味着其源代码对所有人开放,并且可以免费使用和修改。开源项目通常是由社区驱动,有着活跃的开发者和用户群体,不断对工具进行改进和拓展。这种模式促进了创新,并且有利于长期维护和升级。 ### 描述知识点: #### 管理和查询带有语言注释的文本 在语料库中,文本数据经常会被加上各种形式的语言注释,比如句法结构、词性标注、语义角色等。CWB支持管理这类富含语言信息的语料库,使其不仅仅保存原始文本信息,还整合了深层的语言知识。此外,CWB提供了多种查询语言注释数据的方式,使得用户可以针对特定的注释信息进行精确查询。 #### 核心组件:CQP(Corpus Query Processor) CQP是CWB中的核心组件,是一个高度灵活和高效的查询处理器。它支持在终端会话中交互式地使用,这为熟悉命令行界面的用户提供了一个强大的工具。同时,CQP也可以嵌入到其他程序中,比如Perl脚本,从而提供编程式的语料库访问方式。这为高级用户提供了一个强大的平台,可以编写复杂的查询,并将查询结果集成到其他程序中。 #### 基于Web的GUI CQPweb 除了命令行界面外,CWB还提供了一个基于Web的图形用户界面CQPweb,使得不熟悉命令行的用户也能够方便地使用CWB的强大功能。CQPweb通常允许用户通过网页直接构建查询,并展示查询结果,极大地降低了使用门槛。 ### 标签知识点: #### 开源软件 CWB作为开源软件,其主要特点和优势包括: - **社区支持**:开放源代码鼓励了全球开发者共同参与,提供错误修正、功能增强、新特性开发等。 - **定制化**:用户可以根据自己的需求对源代码进行修改,从而实现定制化的功能。 - **透明性**:源代码的开放确保了软件工作的透明性,用户可以清楚了解软件的工作原理和数据处理方式。 - **可靠性**:由于代码的公开性,很多用户和开发者可以共同审查代码,提高了软件的可靠性和安全性。 - **成本效益**:开源软件通常不需要支付昂贵的许可费用,对预算有限的个人和机构特别友好。 ### 压缩包子文件的文件名称列表知识点: #### cwb-3.0.0-osx-10.5-universal 这个文件名提供了关于该软件包的重要信息: - **cwb**:表示这是IMS Open Corpus Workbench的软件包。 - **3.0.0**:表示这个包的版本号,了解版本信息对于获取支持、查看更新日志、了解新特性等方面很重要。 - **osx**:表示这个软件包是为Mac OS X操作系统设计的。 - **10.5**:这个数字指明了这个软件包支持的操作系统版本至少是Mac OS X 10.5。 - **universal**:表明这个软件包是为不同架构的处理器(比如32位和64位)设计的通用二进制文件,提高了软件包的兼容性和可移植性。 综上所述,IMS Open Corpus Workbench是一个为处理带有语言注释的大型文本语料库而设计的开源工具集,它以高效且灵活的查询处理器CQP为核心,提供了命令行和基于Web的两种交互方式,极大地促进了语言学和语言技术领域的研究与应用。由于其开源特性,CWB得到了广泛的使用和不断的改进。
recommend-type

基于属性测试的深入解析与策略探讨

### 基于属性测试的深入解析与策略探讨 #### 1. 基于属性测试中的收缩机制 在基于属性的测试中,当测试失败时,像 `stream_data` 这样的框架会执行收缩(Shrinking)操作。收缩的目的是简化导致测试失败的输入,同时确保简化后的输入仍然会使测试失败,这样能更方便地定位问题。 为了说明这一点,我们来看一个简单的排序函数测试示例。我们实现了一个糟糕的排序函数,实际上就是恒等函数,它只是原封不动地返回输入列表: ```elixir defmodule BadSortTest do use ExUnit.Case use ExUnitProperties pro