文件最后提交记录最后更新时间
test: add priority tests and update call sites for ISyncHibernateCallback Update all RegisterSyncHibernateCallback call sites with priority. Add tests for three-bucket storage, priority-based ordering, invalid priority handling, and cross-bucket unregister. Co-Authored-By: Agent Signed-off-by: wangyantian <wangyantian@huawei.com> Change-Id: I57ba8c1c04cdd1ba976553ace51889d9ae4dd58e1 个月前
style: power仓IDL化 Signed-off-by: wangjingchang <wangjingchang1@h-partners.com>11 个月前
feat: Add suspend takeover function interfaces modify code check issue Signed-off-by: MiniFace <guanxiaolei@huawei.com>10 个月前
feat: add ulsr callbck Signed-off-by: hxf233333 <huxiaofei11@huawei.com>6 个月前
feat: standardization of system sa code definition Signed-off-by: zhengpengyue <zhengpengyue1@huawei.com> Change-Id: I5511f91823133bda91b99b5226496085c89666a32 年前
feat: modify runninglock Signed-off-by: hxf233333 <huxiaofei11@huawei.com>2 年前
feat: Add OnAsyncPowerStateChanged interface Signed-off-by: wangyantian <wangyantian@huawei.com>1 年前
fix: add iproximity_controller Signed-off-by: cjw123qq <chenjunwu4@huawei.com>11 个月前
feat: add displayId parameter to RunningLock interfaces for multi-display support Add uint64_t displayId parameter to RunningLock SCREEN type locks to support filtering by display in multi-display scenarios. Changes: - Add displayId field to RunningLockParam and RunningLockInfo structs - Update IDL interfaces with displayId parameter - Update all layers (client, service, adapter, manager) with displayId parameter - Add POWER_MANAGER_ENABLE_DISPLAY_ID_FILTERING feature flag in powermgr.gni - Filtering logic guarded by feature flag for SCREEN type locks only - Use std::multimap to allow multiple displayId registrations per client - Prevent duplicate registrations for same (callback, displayId) pair - Fix death recipient handling: only remove when no callbacks remain - Add RemoveAllRunningLockChangedCallbacks and HasRunningLockChangedCallbacks methods - Conditional logging: displayId shown only when feature enabled - Add NormalizeDisplayId helper to treat displayId as UINT64_MAX when feature OFF - Add displayId parameter to OnAsyncScreenRunningLockChanged callback - Implement per-displayId notification tracking for RUNNINGLOCK_SCREEN type - HandleScreenLockNotify: tracks locks per displayId, notifies on 0->1 or 1->0 transitions - UINT64_MAX locks broadcast to all registered displayIds - LockCounter simplified: no mgr_ pointer, notification logic moved to RunningLockMgr - Release screenLockCountMutex_ before sending notifications to reduce contention - UpdateUnSceneLockLists moved after Increase/Decrease succeeds Unit tests: - RunningLockNative047-053: Test displayId parameter handling - RunningLockNative054: Test duplicate registration prevention - RunningLockNative055: Test RemoveAllRunningLockChangedCallbacks - RunningLockNative056: Test per-displayId notification transitions (0->1, 1->0) - RunningLockNative057: Test UINT64_MAX lock broadcast (acquire) - RunningLockNative058: Test UINT64_MAX lock broadcast (release) - RunningLockNative059: Test mixed scenario (specific displayId + UINT64_MAX) - RunningLockNative060: Test multiple displayIds independent notification - Fix existing tests to pass correct displayId when unregistering - Update callback tests to include displayId parameter Co-Authored-By: Agent Signed-off-by: z30053694 <zhangchen190@h-partners.com> Change-Id: I4beb6f8272803572a3e944a768ec8d882766b0d91 个月前
add the power key to screen Signed-off-by: suhaoo <1042497664@qq.com>7 个月前
feat: screen off pre callback Signed-off-by: chenbilu <chenbilu@huawei.com>2 年前
refactor: extract error table to common GetErrorMessage in power_errors.h Move duplicated error message tables from napi_errors.cpp, ohos.power.impl.cpp, and ohos.runningLock.impl.cpp into a shared inline GetErrorMessage() function in power_errors.h to eliminate redundancy. Co-Authored-By: Agent Signed-off-by: cjw123qq <chenjunwu4@huawei.com>1 个月前
!2089 merge feat/hibernate-callback-optimize into master test: add unit tests for ISyncHibernateCallback death recipient and lock optimization Created-by: wangyantian0 Commit-by: wangyantian Merged-by: openharmony_ci Description: > 请检查PR是否满足[《代码合入流程指导和规范》](https://gitee.com/openharmony/powermgr_power_manager/wikis/issue-commit-pr-standard) , 否则将不会审查通过。 **【关联Issue】** https://gitcode.com/openharmony/powermgr_power_manager/issues/1690 **【修改描述】** **【验证结果】** See merge request: openharmony/powermgr_power_manager!208920 天前
feat: standardization of system sa code definition Signed-off-by: zhengpengyue <zhengpengyue1@huawei.com> Change-Id: I5511f91823133bda91b99b5226496085c89666a32 年前
fix: A custom power-saving mode has been added Signed-off-by: yanghang <kongwei13@h-partners.com>11 个月前
feat: modify runninglock Signed-off-by: hxf233333 <huxiaofei11@huawei.com>2 年前
feat: Add OnAsyncPowerStateChanged interface Signed-off-by: wangyantian <wangyantian@huawei.com>1 年前
add screen off when people leaves Signed-off-by: houyujiao1 <houyujiao1@h-partners.com>2 个月前
feat: add displayId parameter to RunningLock interfaces for multi-display support Add uint64_t displayId parameter to RunningLock SCREEN type locks to support filtering by display in multi-display scenarios. Changes: - Add displayId field to RunningLockParam and RunningLockInfo structs - Update IDL interfaces with displayId parameter - Update all layers (client, service, adapter, manager) with displayId parameter - Add POWER_MANAGER_ENABLE_DISPLAY_ID_FILTERING feature flag in powermgr.gni - Filtering logic guarded by feature flag for SCREEN type locks only - Use std::multimap to allow multiple displayId registrations per client - Prevent duplicate registrations for same (callback, displayId) pair - Fix death recipient handling: only remove when no callbacks remain - Add RemoveAllRunningLockChangedCallbacks and HasRunningLockChangedCallbacks methods - Conditional logging: displayId shown only when feature enabled - Add NormalizeDisplayId helper to treat displayId as UINT64_MAX when feature OFF - Add displayId parameter to OnAsyncScreenRunningLockChanged callback - Implement per-displayId notification tracking for RUNNINGLOCK_SCREEN type - HandleScreenLockNotify: tracks locks per displayId, notifies on 0->1 or 1->0 transitions - UINT64_MAX locks broadcast to all registered displayIds - LockCounter simplified: no mgr_ pointer, notification logic moved to RunningLockMgr - Release screenLockCountMutex_ before sending notifications to reduce contention - UpdateUnSceneLockLists moved after Increase/Decrease succeeds Unit tests: - RunningLockNative047-053: Test displayId parameter handling - RunningLockNative054: Test duplicate registration prevention - RunningLockNative055: Test RemoveAllRunningLockChangedCallbacks - RunningLockNative056: Test per-displayId notification transitions (0->1, 1->0) - RunningLockNative057: Test UINT64_MAX lock broadcast (acquire) - RunningLockNative058: Test UINT64_MAX lock broadcast (release) - RunningLockNative059: Test mixed scenario (specific displayId + UINT64_MAX) - RunningLockNative060: Test multiple displayIds independent notification - Fix existing tests to pass correct displayId when unregistering - Update callback tests to include displayId parameter Co-Authored-By: Agent Signed-off-by: z30053694 <zhangchen190@h-partners.com> Change-Id: I4beb6f8272803572a3e944a768ec8d882766b0d91 个月前
fix: add screen running lock state change callback register interface Signed-off-by: cjw123qq <chenjunwu4@huawei.com> Co-Authored-By: Agent3 个月前
feat: add displayId parameter to RunningLock interfaces for multi-display support Add uint64_t displayId parameter to RunningLock SCREEN type locks to support filtering by display in multi-display scenarios. Changes: - Add displayId field to RunningLockParam and RunningLockInfo structs - Update IDL interfaces with displayId parameter - Update all layers (client, service, adapter, manager) with displayId parameter - Add POWER_MANAGER_ENABLE_DISPLAY_ID_FILTERING feature flag in powermgr.gni - Filtering logic guarded by feature flag for SCREEN type locks only - Use std::multimap to allow multiple displayId registrations per client - Prevent duplicate registrations for same (callback, displayId) pair - Fix death recipient handling: only remove when no callbacks remain - Add RemoveAllRunningLockChangedCallbacks and HasRunningLockChangedCallbacks methods - Conditional logging: displayId shown only when feature enabled - Add NormalizeDisplayId helper to treat displayId as UINT64_MAX when feature OFF - Add displayId parameter to OnAsyncScreenRunningLockChanged callback - Implement per-displayId notification tracking for RUNNINGLOCK_SCREEN type - HandleScreenLockNotify: tracks locks per displayId, notifies on 0->1 or 1->0 transitions - UINT64_MAX locks broadcast to all registered displayIds - LockCounter simplified: no mgr_ pointer, notification logic moved to RunningLockMgr - Release screenLockCountMutex_ before sending notifications to reduce contention - UpdateUnSceneLockLists moved after Increase/Decrease succeeds Unit tests: - RunningLockNative047-053: Test displayId parameter handling - RunningLockNative054: Test duplicate registration prevention - RunningLockNative055: Test RemoveAllRunningLockChangedCallbacks - RunningLockNative056: Test per-displayId notification transitions (0->1, 1->0) - RunningLockNative057: Test UINT64_MAX lock broadcast (acquire) - RunningLockNative058: Test UINT64_MAX lock broadcast (release) - RunningLockNative059: Test mixed scenario (specific displayId + UINT64_MAX) - RunningLockNative060: Test multiple displayIds independent notification - Fix existing tests to pass correct displayId when unregistering - Update callback tests to include displayId parameter Co-Authored-By: Agent Signed-off-by: z30053694 <zhangchen190@h-partners.com> Change-Id: I4beb6f8272803572a3e944a768ec8d882766b0d91 个月前
fix: updata the directory structure of power subsystem Signed-off-by: zhengpengyue <zhengpengyue1@huawei.com> Change-Id: Ia882c8bc1005d208d5d5186cc98c7720345f56c33 年前
feat: screen off pre callback Signed-off-by: chenbilu <chenbilu@huawei.com>2 年前