Hi, I did some testing as soon as I got your notification and app looks awesome and I've great hopes only going forward.
There are some things I just wanted to bring to your attention and I know it's just early releases so these minor bugs are expected.
The doze stats persistent notification (working perfectly in forcedoze on my a14) doesn't work and "Disable motion sensing for Doze" crashes the app.
There's been an old issue in which significant motion sensor is on all the time even during doze and using "sensors off" and when you use apps which tell you about battery usage/wakelocks during screen off; "android system" comes first in the list with significant motion sensor showing awake all the time.
I'm currently facing this same issue and my battery drain is kinda weird. Some times it'll be 1% drain for like 5 hours overnight and sometimes it'll be 1% per hour so like 5-6% overnight and in both the scenario above mentioned issue remains same.
Is it somehow possible to use some xposed/magisk module integrated with enforcedoze to forcibly turn that off?
Apart from that one confusing thing for me is that since both forcedoze and enforcedoze very strongly emphasis on not just doze but turning off motion sensing in the main screen itself, why is the "disable motion sensors on screen off" not activated by default, I understand the reason but then that should be brought to user's attention immediately/more strongly since the app itself declare that on main screen and github description.
Hoping for great releases in the future.
Thanks :)
Hi, I did some testing as soon as I got your notification and app looks awesome and I've great hopes only going forward. There are some things I just wanted to bring to your attention and I know it's just early releases so these minor bugs are expected.
The doze stats persistent notification (working perfectly in forcedoze on my a14) doesn't work and "Disable motion sensing for Doze" crashes the app.
There's been an old issue in which significant motion sensor is on all the time even during doze and using "sensors off" and when you use apps which tell you about battery usage/wakelocks during screen off; "android system" comes first in the list with significant motion sensor showing awake all the time.
I'm currently facing this same issue and my battery drain is kinda weird. Some times it'll be 1% drain for like 5 hours overnight and sometimes it'll be 1% per hour so like 5-6% overnight and in both the scenario above mentioned issue remains same.
Is it somehow possible to use some xposed/magisk module integrated with enforcedoze to forcibly turn that off?
Apart from that one confusing thing for me is that since both forcedoze and enforcedoze very strongly emphasis on not just doze but turning off motion sensing in the main screen itself, why is the "disable motion sensors on screen off" not activated by default, I understand the reason but then that should be brought to user's attention immediately/more strongly since the app itself declare that on main screen and github description.
Hoping for great releases in the future. Thanks :)