Jasper-1024
Modules can't be activated after 2.0.3
Modules can't be activated after 2.0.3, is it a problem with the system version or the lsposed version? Or do I need to turn off Xposed API protection? The Readme shows that it supports up to Android 12. I'm using Android 13 and https://github.com/JingMatrix/LSPosed
Normally, the A13 should not have this problem, and there is no need for cursor xposed api protection; Further investigation requires a log file. Please turn on debug mode and then export the log in xposed. I can investigate further. If there are privacy concerns with publishing to Github, you can email me. @Typhonling @SuperKenVery
I received the log file, thanks. After a brief analysis, it's very strange; this active check actually involves the nowakelock hook setting its own bool value to true. This issue does appear in the log.
The testing environments for Android 14 and Android 16 should be ready this week. We'll conduct a unified investigation into the activation and adaptation issues for Android 13 - Android 16, which may take a bit longer.
Version v2.0.5 has changed the new model active check logic, try it out. Yesterday I checked the hook position of xpsoed, it should not have changed from Android 13 to Android 16 beta2. 2.0.5 can currently work normally on Android 16 beta2. If there are any problems, please give feedback.
Hi, thanks for your great work!
However, it still crashes on my machine. I've sent my logs to your email. If it's not the correct log or you need more information or whatsoever please tell me!
EDIT: Sorry, the email didn't send due to network errors. I'll try again. EDIT2: Okay, it's now sent.
There seems to be a problem with the packaging. The version released on GitHub is different from the local Android Studio version;
I'm still looking into this issue. Most of the code was completed 2 years ago, and it seems necessary to refactor it extensively to re-adapt to the latest Android.
Oh, I found it's crashing because it tried to access apps in my work profile. After removing all apps in my work profile, it doesn't crash. Thanks for your great work! Have a nice weekend!
Oh, I found it's crashing because it tried to access apps in my work profile. After removing all apps in my work profile, it doesn't crash. Thanks for your great work! Have a nice weekend!
that also should not happened.. for now nowakelock should support work profile. Maybe there is another bug... next week maybe try to find out.
也许可以尝试v2.0.5/63。 它应该可以修复一些与此相关的错误。
这个版本依然会闪退，提示未激活，我是安卓14，oneui6.1.1。lsp官方内测版，也使用了工作空间功能。
另外我发现了一个问题，激活模块时作用域页面应该勾选系统框架和“”设置存储“这个东西，可是无论怎么尝试勾选设置存储，退出重进后都会发现它被取消勾引选了，感觉这里可能也有问题，如果需要日志，请告诉我
@AXEVO 激活模块时作用域页面应该勾选系统框架和“”设置存储“这个东西，可是无论怎么尝试勾选设置存储，退出重进后都会发现它被取消勾引选了
- 不需要担心, 这一点存在也能正常工作.
这个版本依然会闪退: 请遵循如下步骤
- lsposed 取消激活 -> reboot -> 清除数据, 并卸载 nowakelock -> reboot
- 安装 v2.0.5/63 在 lsposed 激活. -> reboot.
- 如果仍然闪退 或存在问题, 请在 设置打开调试模式, 在 lsposed 导出 log 可以通过邮件发给我.
- 非 aosp 上的问题可能无法保证一定有办法解决.
@AXEVO 激活模块时作用域页面应该勾选系统框架和“”设置存储“这个东西，可是无论怎么尝试勾选设置存储，退出重进后都会发现它被取消勾引选了
- 不需要担心, 这一点存在也能正常工作.
这个版本依然会闪退: 请遵循如下步骤
- lsposed 取消激活 -> reboot -> 清除数据, 并卸载 nowakelock -> reboot
- 安装 v2.0.5/63 在 lsposed 激活. -> reboot.
- 如果仍然闪退 或存在问题, 请在 设置打开调试模式, 在 lsposed 导出 log 可以通过邮件发给我.
- 非 aosp 上的问题可能无法保证一定有办法解决.
已经测试过了，这个版本如果工作空间存在，依然会闪退，但是删除工作空间之后可以正常开起来，我看了一下，删除工作空间之后进入软件，右上角的切换用户按钮点击后会有“主用户”和“工作资料”两个选项，而工作空间对应的是双开出来的软件。 感觉原因是软件不能很好处理双开和工作空间的问题，如果大佬需要日志，麻烦留一下邮箱，我会上传日志
目前对工作空间应用只支持 用户10 ,如果多用户的 user id 不是 10,那么可能就会出现闪退... 这里需要完全重写才行; 但是目前主要工作在重构 UI , 这个事情需要优先级可能并不高.
Currently, the workspace application only supports user 10. If the user ID for multiple users is not 10, then a crash may occur... This needs to be completely rewritten; however, the main focus is currently on refactoring the UI, so the priority for this task may not be high.
目前对工作空间应用只支持 用户10 ,如果多用户的 user id 不是 10,那么可能就会出现闪退... 这里需要完全重写才行; 但是目前主要工作在重构 UI , 这个事情需要优先级可能并不高.
Currently, the workspace application only supports user 10. If the user ID for multiple users is not 10, then a crash may occur... This needs to be completely rewritten; however, the main focus is currently on refactoring the UI, so the priority for this task may not be high.
是的，oneui上双开是用户95，工作空间是用户11，看来是这个原因了，那大佬大概什么时候能解决一下这个问题呢？看来只能以后再用这个模块了
目前对工作空间应用只支持 用户10 ,如果多用户的 user id 不是 10,那么可能就会出现闪退... 这里需要完全重写才行; 但是目前主要工作在重构 UI , 这个事情需要优先级可能并不高.
Currently, the workspace application only supports user 10. If the user ID for multiple users is not 10, then a crash may occur... This needs to be completely rewritten; however, the main focus is currently on refactoring the UI, so the priority for this task may not be high.
借楼想问问作者知不知道这个dream:doze是什么唤醒锁，我在网上查了下是熄屏显示和双击亮屏之类功能相关的，但是关掉这些功能照样有，这个唤醒锁一直在，手机完全不能进入休眠状态，待机耗电飞快
目前对工作空间应用只支持 用户10 ,如果多用户的 user id 不是 10,那么可能就会出现闪退... 这里需要完全重写才行; 但是目前主要工作在重构 UI , 这个事情需要优先级可能并不高. Currently, the workspace application only supports user 10. If the user ID for multiple users is not 10, then a crash may occur... This needs to be completely rewritten; however, the main focus is currently on refactoring the UI, so the priority for this task may not be high.
是的，oneui上双开是用户95，工作空间是用户11，看来是这个原因了，那大佬大概什么时候能解决一下这个问题呢？看来只能以后再用这个模块了
The next major refactoring version will solve it. Refactoring the UI with the help of cursor is going smoothly, saving a lot of time, so other functions will be completed faster, expected in April.
- https://t.me/nowakelock/9
目前对工作空间应用只支持 用户10 ,如果多用户的 user id 不是 10,那么可能就会出现闪退... 这里需要完全重写才行; 但是目前主要工作在重构 UI , 这个事情需要优先级可能并不高. Currently, the workspace application only supports user 10. If the user ID for multiple users is not 10, then a crash may occur... This needs to be completely rewritten; however, the main focus is currently on refactoring the UI, so the priority for this task may not be high.
是的，oneui上双开是用户95，工作空间是用户11，看来是这个原因了，那大佬大概什么时候能解决一下这个问题呢？看来只能以后再用这个模块了
v3.0.1 may fix this problem. be careful is a beta version https://github.com/NoWakeLock/NoWakeLock/releases/tag/v3.0.1%2F71