New Doze on Go? - Greenify

What's so new about the Xposed version of the feature? I can still see it in the usual place as well as in the Xposed feature list.

I hope he found another way to go about Doze on the Go. Setting the motion sensing timeout to 0 really only messed with the SoT.

Dominik R said:
I hope he found another way to go about Doze on the Go. Setting the motion sensing timeout to 0 really only messed with the SoT.
Click to expand...
Click to collapse
How so? Mine is 180s at the moment.
That doesn't require Xposed though, so I'm not sure what is happening here.
Sent from my OnePlus3 using XDA Labs

Well Doze on the Go (or disabling significant motion) in beta 4 worked by setting the timeout to 0 (according to an xda thread). Feng said that was the only way to do it, but now he might have found a different way.

I'm on 2.9 beta 5 and I'm not able to turn on "doze on the go" feature.. it says incompatible rom but I'm on cyanogen 13 so I dubt it is the cause..
already read other user have the same issue so I suggest to wait for a fix before update
tomorrow i will send a log to dev

I confirm that this feature could not enable on CM 13 ROM
Sent from my Nexus 6P using Tapatalk

It won't enable on a stock Nexus 6P either. Probably a small bug in this new feature.

I'm at CM13 and I got the same error already told by another members...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So what I would know is: the problem is with Greenify or with CM13? I mean, greenify's dev can fix this problem or CM13 is permanently incompatible with the "doze on the go"? ?
I'm already used in the past OMNI, Dirty Unicorns, Paranoid Android, stock and nowadays CM13. Which "property" the ROM must have to "doze on the go" works? I'm asking because I don't wanna flash another ROM. and discover that the new one is incompatible too... ?

The same message appears for me on Pure Nexus.

Veronezzi said:
So what I would know is: the problem is with Greenify or with CM13? I mean, greenify's dev can fix this problem or CM13 is permanently incompatible with the "doze on the go"? ?
Click to expand...
Click to collapse
Problem lies with Greenify as many people are having this same issue with different ROMS. I am on Dirty Unicorns and I am getting this same message when trying to activate the Xposed version of Doze-On-The Go. Try to get a log of it when it happens and send to the Dev. The more logs, the better chances of this getting fixed.

I'm on CM 13 20160710 nightly on both my Nexus 4 and 7 (2013) with Greenify 2.9 beta 5 and "Doze on the GO" works fine. I even tried Forcedoze briefly and it worked ok as well, even though I no longer use it. So in my case, everything works as it should.
Oh yes, I should add that both devices use custom kernels, but I don't know if that makes any difference.

colin p said:
I'm on CM 13 20160710 nightly on both my Nexus 4 and 7 (2013) with Greenify 2.9 beta 5 and "Doze on the GO" works fine. I even tried Forcedoze briefly and it worked ok as well, even though I no longer use it. So in my case, everything works as it should.
Oh yes, I should add that both devices use custom kernels, but I don't know if that makes any difference.
Click to expand...
Click to collapse
Does the Xposed feature Doze On The Go work in Greenify for you? I am asking because there are two versions of it, one under normal Settings of Greenify and the other under Xposed Settings of Greenify.

I think the implementation of Doze on The Go in Greenify will still need a touch or perfecting,
i would suggest mix match it with ForceDoze...

tnsmani said:
Does the Xposed feature Doze On The Go work in Greenify for you? I am asking because there are two versions of it, one under normal Settings of Greenify and the other under Xposed Settings of Greenify.
Click to expand...
Click to collapse
Sorry, I don't use xposed, so the doze on the go setting I use would be under the normal settings in Greenify.
I guess I didn't read the thread good enough and didn't realize the problem was with xposed, my apologies and disregard my posting.
Sent from my Nexus 4 using Tapatalk

otonieru said:
I think the implementation of Doze on The Go in Greenify will still need a touch or perfecting,
i would suggest mix match it with ForceDoze...
Click to expand...
Click to collapse
What about with Naptime?
Sent from my OnePlus3 using XDA Labs

hi i have a nexus 6 on stock 7.1.1 unrooted
i have done :
To enable Aggressive Doze on Android 7.0+ (non-root):
adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
To enable Doze on the Go:
adb -d shell pm grant com.oasisfeng.greenify android.permission.DUMP
the first worked & i can slide to activate Aggressive Doze but Doze on the Go is greyed out cant slide it & its stated Incompatible with your device or ROM.
what gives?

iluvatrix said:
hi i have a nexus 6 on stock 7.1.1 unrooted
i have done :
To enable Aggressive Doze on Android 7.0+ (non-root):
adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
To enable Doze on the Go:
adb -d shell pm grant com.oasisfeng.greenify android.permission.DUMP
the first worked & i can slide to activate Aggressive Doze but Doze on the Go is greyed out cant slide it & its stated Incompatible with your device or ROM.
what gives?
Click to expand...
Click to collapse
Hello
Same here. i am on Stock 7.0 and Doze on the Go is greyed out.

Hello guys,
Same for me. Since i went to Nougat (7.0) update on my GS7, it's not possible to activate the Doze on the go command.

j1978 said:
Hello
Same here. i am on Stock 7.0 and Doze on the Go is greyed out.
Click to expand...
Click to collapse
keke7442 said:
Hello guys,
Same for me. Since i went to Nougat (7.0) update on my GS7, it's not possible to activate the Doze on the go command.
Click to expand...
Click to collapse
Don't need it. Doze on the go capability (equivalent functionality) is baked into Android 7/Nougat.

Davey126 said:
Don't need it. Doze on the go capability (equivalent functionality) is baked into Android 7/Nougat.
Click to expand...
Click to collapse
Excerpt from Greenify Knowledge Base;
Android 7.0 introduced native support of Doze on the Go and a new light doze mode, which blocks network access but not wake-up timers of the app. When movement is detected, it exits deep doze and keeps in light doze, and then goes back into deep doze after device is stationary for some time. The Greenify version of "Doze on the Go" will always keep your device in deep doze on Android 7.0, regardless of movement.
Click to expand...
Click to collapse
Without Doze on the Go, Deep Doze cannot be kept when moving.. On nougat, Greenify Doze on the go doesn't lose its benefit.

Related

Greenify auto hibernate not working

N
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So this goes on and on, not auto hibernating any app when I lock my screen or I do not use the apps. I have left the phone untouched. Tryed rooted greenify, then installed xposed and switched to boost mode, granted as administrator and turned in the service in accesibility menu... Help me.. Thank you!
rinxtzu said:
N
So this goes on and on, not auto hibernating any app when I lock my screen or I do not use the apps. I have left the phone untouched. Tryed rooted greenify, then installed xposed and switched to boost mode, granted as administrator and turned in the service in accesibility menu... Help me.. Thank you!
Click to expand...
Click to collapse
Is that latest beta?
Go for the stable one or turn the greenify access ability from setting.
Same here, I've been having an issue with Greenify Auto-Hibernation being stopped, and I can't figure out why. I made sure it is removed from Amplify, I whitelisted it in Power Nap, but I even turned off Power Nap to try and stop it, and I have it set as a Device Admin and Accessibility Services are activated. I'm rooted, using boost mode, xposed enabled. I did notice that it started not that long after switching to a 5.1.1 port from a Kit Kat ROM, is there any trick to make it work on LP that I'm not aware of?
I have the same problem with the latest beta.
I have the exact same apps and settings as 12gage above, but
12gage said:
... and Accessibility Services are activated...
Click to expand...
Click to collapse
Where do I set this?
Ubimo said:
I have the same problem with the latest beta.
I have the exact same apps and settings as 12gage above, but
Where do I set this?
Click to expand...
Click to collapse
That is in DEVICE>SETTINGS>Accessibility. But it is required to be enabled only if you are running Greenify in non-root mode.
Do you people have any warez installed, like LuckyPatcher?
tnsmani said:
That is in DEVICE>SETTINGS>Accessibility. But it is required to be enabled only if you are running Greenify in non-root mode.
Do you people have any warez installed, like LuckyPatcher?
Click to expand...
Click to collapse
No sir, I'm on Samsung so i even went into Smart Manager and turned off App Optimization because I thought that may have been causing it, but today I got the same message when opening Greenify
12gage said:
No sir, I'm on Samsung so i even went into Smart Manager and turned off App Optimization because I thought that may have been causing it, but today I got the same message when opening Greenify
Click to expand...
Click to collapse
Why don't you try to clear cache, data, forcestop, uninstall and reinstall Greenify and check?
After enabling Greenify as administrator, the problem Greenify not hibernating apps is gone.
I have the same problem, after installing greenify from the google play again. I have samsung galaxy s3
Custom rom: QS KK
Greenify as administrator,
How can I fix this? Please reply! thanks
I have fix by reflashing my ROM.
Why is greenify acting like that during uninstall/install in Google play? I have donate package as well.
Sent from my GT-I9300 using XDA-Developers mobile app
So I faced the problem when I flashed CM14 (unofficial) on my Nexus 5 (hammerhead).
Uninstalled the app and then reinstalled it again and it did the trick. So you guys can try that too!
Sent from my Nexus 5 using XDA-Developers mobile app
My phone (non-root) running on Android M, after the latest update on Greenify, the Automated Hibernation is enabled. However, the Apps that are marked to Hibernate after the Screen is turned off, don't Hibernate and Apps remain running!
Do I need to enable anything further for Automate Hibernate to work?
finneyp said:
My phone (non-root) running on Android M, after the latest update on Greenify, the Automated Hibernation is enabled. However, the Apps that are marked to Hibernate after the Screen is turned off, don't Hibernate and Apps remain running!
Do I need to enable anything further for Automate Hibernate to work?
Click to expand...
Click to collapse
Same issue here on my S7E.
rapozaum said:
Same issue here on my S7E.
Click to expand...
Click to collapse
Ditto! S7E here too. Anyone figure it out?
Is there a fix for this issue yet?
2ISAB said:
Is there a fix for this issue yet?
Click to expand...
Click to collapse
What issue? Some random dude and a few friends had a problem 15+ months ago while tens/hundreds of thousands use auto hibernate without issue. Such 'problems' are almost always confined to an individual device and usually self inflicted.
Best practice is to try the latest Greenify build, carefully document behavior if not to expectations and provide logs when requested.
I've found that it won't work for devices that have a password lock screen.
Problem solved!
Sent from my HTC One M9 using Tapatalk
2ISAB said:
I've found that it won't work for devices that have a password lock screen.
Problem solved!
Click to expand...
Click to collapse
Believe Smart Lock may be the culprit vs any form of lock screen security.

[UMIDIGI F1] Android P customizations, dark theme, gesture navigation

The Umidigi F1 is supposed to come with stock Android P; however, it seems that some features have been removed or disabled.
I can't find how to enable the Android P Dark Theme.
I can't figure out how to enable full screen gesture navigation or how to swap the back and recents buttons in the navbar.
I'm sure there are other things as well.
Can I use adb to enable those settings?
Is there some other way to re-enable these basic Android P features?
Swapping the back and recents buttons are in the Smart Assistant option in Settings. There you can also find the Umidigi version of navigation gestures.
As for Dark Theme, I have no idea, myself. The option's for sure not there by default.
I'm hopeful that someone will develop some custom roms for it, myself. The stock rom is not as smooth as I know vanilla Android is, and you can't turn on the battery % on the notification bar. Screen size is not adjustable, either.
jeffmikels said:
The Umidigi F1 is supposed to come with stock Android P; however, it seems that some features have been removed or disabled.
I can't find how to enable the Android P Dark Theme.
I can't figure out how to enable full screen gesture navigation or how to swap the back and recents buttons in the navbar.
Click to expand...
Click to collapse
I've randomly experienced a kind of dark mode in the notifications and volume control but can't consistently replicate it. It seems to be triggered by a dark wall paper. I have a dark wall paper and have dark volume control, but pull down notifications/menu are still white.
Download a cool little app called Powershade from the store. You can style your notifications/menu to whatever you like. You'll need to enable Powershade in Duraspeed to prevent it being stopped.
The stock Pie pill gesture isn't there, only 'slippy' gestures which constantly kick you back the home screen when typing (aka Sloppy gestures). This could easily be fixed by reducing the active area to one pixel, it currently sits over the space bar.
That, along with:
- Not supporting launchers
- Issues with photos being completely messed up (masses of low resolution duplicates)
- Constantly backward facing GPS indicator
- Unable to send images via whatsapp
- Power and earphones plugged in creates unbearable interference
...have made this phone unusable for me. Updates are too slow to depend on them and have so far just caused even more issues. Its such a shame, it could have been a great value for money phone, but turned out to be too good to be true.
I'm returning mine to Amazon. For a few pounds more I can get something I'm not constantly battling with.
Took this from an Umidigi forum, it works
:As for quickstep issue, all you guys have to do is to remove the package and it'll work flawlessly, even with custom launchers(I'm using Nova).
This is only temporarily until you factory reset OR OTA update the device.
1) Download minimal adb fastboot package from here: https://androidfilehost.com/?fid=962187416754459552
2) Go to Settings > System > About Phone and tap on "build number" about 8 times. You should see a message saying: "You are a developer now"
3) Back to the previous menu and you should see now a new item called "Developer options", go there, find and enable "USB debugging".
4) Now connect the phone to the PC via USB and select "Transfer files" on the phone.
5) Open a command line and go to the directory you extracted the adb tools to.
6) Run the command "adb devices", your device should shown. If not, you need to check the drivers.
7) Run "adb shell"
8) Run "pm uninstall -k --user 0 com.android.launcher3". It should show "success".
9) Reboot the device and you will be able to multitask until either factory reset OR update.
I just got two of these yesterday. Getting mine setup this morning. I have no problem with the phone charging through USB and playing music out my headphones- the audio is perfectly clear. I also installed whatsapp and had no problems sending a photo to a friend, and she got it. I see my gps on google maps just fine and it seems to work as intended. I've not tried any other launchers, yet, but I REALLY like this phone for the price point. Sad there isn't more activity on here from folks who have them.
https://forum.xda-developers.com/android/development/psa-project-treble-t3917284
GOONER13 said:
https://forum.xda-developers.com/android/development/psa-project-treble-t3917284
Click to expand...
Click to collapse
Hello, did you make any of the Treble ROMs work? I had no success with any!
Thanks!
Leo_Freitas said:
Hello, did you make any of the Treble ROMs work? I had no success with any!
Thanks!
Click to expand...
Click to collapse
Hi tried Descendant first and it's pretty nice, switched to Blissrom and been with it for a couple of weeks, handy having the Gapps included.
GOONER13 said:
Hi tried Descendant first and it's pretty nice, switched to Blissrom and been with it for a couple of weeks, handy having the Gapps included.
Click to expand...
Click to collapse
A step by step mini tutorial please?
Thanks!!
Magisk is working and Google Pay works with Magisk Hide.
Anyone have Xposed working? Link to version if you please.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kangburra said:
Magisk is working and Google Pay works with Magisk Hide.
Anyone have Xposed working? Link to version if you please.
Click to expand...
Click to collapse
Please can you tell me What Rom did you try this on? Have you tried camera2 API so Google camera can work ?
Use Arnova's Advanced 1.5
https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/
This is the ROM it arrived with
Kangburra said:
Magisk is working and Google Pay works with Magisk Hide.
Anyone have Xposed working? Link to version if you please.
View attachment 4749167
Click to expand...
Click to collapse
Please, can you try the magisk module double tap to wake with the umidigi f1?
Thanks!!
I can't find that module
monoculero said:
Please, can you try the magisk module double tap to wake with the umidigi f1?
Thanks!!
Click to expand...
Click to collapse
That would be pretty nice to have, but I think phones that support DT2W have to have hardware support for sensing the taps while off like most LG and HTC phones have. I'm using Glimpse notifications to get the screen wake for notifications like every phone should already have stock Yes, even though it's not AMOLED, it's got a 5150 mah battery FFS! 5 seconds of screen on a few times a day won't cost anything noticeable. And it hasn't either for 2 weeks I've been using it.
I too wonder if they'll ever get any kind of theming going though. That would sure be nice!
Umidigi f1 PLAY
Download SwiftKey keyboard. it allows u to move the keyboard up. basically fixing the sloppy slippery .

Greenify unable to use Accessibility service post Android 12L update

Hello Team,
I am having greenify donate version and been using it since very long. But recently post updating my pixel 6 pro with March Update (Android 12L) app has stopped working. App is able to open each targeted application's configuration window but unable to click/process force close option. If we manually click it then it will proceed with next app but same again getting fail to force close it.
Please help me sort this out or will it need a new app version to be launched?
Having the same problem since the update in March. Haven't been able to fix it no matter what I've tried.
I thought I was doing something wrong. I picked up a Pixel 6, currently running Android 12, SP2A.220405.004. I redownloaded Greenify and the donation package from my library, and I can't get it to work properly.
It will open App Info, and the screen might flash a few times, but eventually the screen returns to Greenify and nothing has been terminated.
If I click Force Stop myself, I'll be asked to confirm on the pop up, then the screen will move to the next App Info window. I repeat the process, and usually the automation will pause here for a couple seconds before resuming. During the entire half-automated process of closing apps, it seems Greenify has to pause every two (sometimes three) App Info windows and gather it wits about it.
Very frustrating. I'm really hoping there's a answer soon.
I'm using Android 12, SP2A.220405.004 and using greenify fine by using terminal systemizer and put into system app
I got the same issue on my pixel. I recommend you to uninstall Greenify and try this perfectly working alternative.
Hibernator:
https://play.google.com/store/apps/details?id=com.tafayor.hibernator
Same here on Android 12L revision 5.
When the automatic hibernation process is left, it doesn't work.
Else, if I pull down the notification panel and pull up it again while hibernation is in progress, it works. However, it must be done one at a time.
There are no attachments for this case.
Sorry.
I'm also facing the same issu in android 12L.
greenify cannot force close apps. it stucks.
I request the developer to please make it compatible for 12L.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
captmist said:
I got the same issue on my pixel. I recommend you to uninstall Greenify and try this perfectly working alternative.
Hibernator:
https://play.google.com/store/apps/details?id=com.tafayor.hibernator
Click to expand...
Click to collapse
Funny part is if I setup Hibernator app, then greenify starts working
abhi21sept said:
Funny part is if I setup Hibernator app, then greenify starts working
Click to expand...
Click to collapse
are you using Android 12L ?
abhi21sept said:
Funny part is if I setup Hibernator app, then greenify starts working
Click to expand...
Click to collapse
It's clear that A12 needs more than one app with Auto Hibernation active, to let Greenify work.
abhi21sept said:
Funny part is if I setup Hibernator app, then greenify starts working
Click to expand...
Click to collapse
So, you mean that installed hibernator app, then greenfy will work again in android 12L ? Thanks
Can someone explain what to configure exactly in both Hibernator and Greenify to get the proper force closes?
I haven't been able to reproduce this myself. I'm on Android 12, OnePlus 8T
This is happen because A12L/A13 don't allow some permissions for recently Greenify app (4.7.8+).
The installation is out of Play and app is "not verified" by Play Store.
Latest version from Play is 4.7.5 since 2019.
INSTRUCTIONS to fix permissions on early Greenify versions:
1. Install Greenify and Donation Pack from Play Store (4.7.5).
2. Grant root access for Greenify on KSU/Magisk.
3. Download and install (update automatically older version) Greenify 5.0 (search .apk on Google, uptodown and sourceforge).
3. Go on Android Settings and apply all permissions:
Settings > Apps > Special Apps Access
- Device Admin Apps > Greenify Automator: turn on
- Display over other apps: Allowed
- Device & App notifications > Allow notifications access: Allowed
- Usage access: Allowed
- Turn screen On: Allowed
Settings > Accessibility
- Greenify Automated Hibernation: turn on
Open Greenify app and finish the settings on app.
Shallow Hibernation isn't working, don't enable it.
Enjoy.

Force Doze Mode Force your phone into doze mode to save battery. (root only)

STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use the mod at your own risk there is no warranty or guarantee.
Version 5.3
Force Doze Mode will force the phone to sleep 1 minute after the screen turns off. Google will want to change it back to the default. So Force Doze Mode will check every 30 seconds to see if Google changed it, and will change it back. Force Doze Mode will disable all motion sensors, so even if your phone is moving it will still be sleeping. Force Doze Mode will put your phone to sleep for a maximum of 24 hrs each time the screen turns off. The phone will wake up from doze 5 minutes with a multiplying factor of 2.0, then phone will go back to sleep after 1 to a max of 5 minutes, so you will get your email push notifications. After the 24 hrs are up the motion sensor will be enabled but the phone will sleep for another 24 hrs if not moved. In order for the script to work correct Magisk must be excluded from battery optimization, Force Doze Mode will automatically exclude Magisk.
Version 6.0
Force Doze Mode will force the phone to sleep 1 minute after the screen turns off. Google will want to change it back to the default. So Force Doze Mode will check every 30 seconds to see if Google changed it, and will change it back. Force Doze Mode will disable all motion sensors for 30 days, so even if your phone is moving it will still be sleeping. Force Doze Mode will put your phone to sleep for a maximum of 30 days each time the screen turns off. The phone will wake up from doze 1 hr with a multiplying factor of 2.0, then phone will go back to sleep after 1 to a max of 5 minutes, so you will get your email push notifications.
Theoretically version 6.0 should provide better sleep time because the phone is not waking up so much from doze into maintenance mode. But the down side is you may not get your email push notifications for one hr then two hr's and so on. Force Doze Mode will automatically exclude Magisk.
Benchmarks are on second post down below.
Requirements
Android Nougat or higher
With Google or without, like LineageOS or a DeGoogled phone.
Magisk 20.4 or higher
Update or Downgrade
Flash in Magisk then reboot.
Credits, A Special Thank You
at Tsungi easz on how to tune the device_idle_constants settings properly. github
All benchmarks started out at 100% battery on an H910 with Oreo 8.0 and Google.
Version 5.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Version 6.0
I am still working on this project to expect updates. Just install on top of older versions and restart.
Got a new version to try out, v3.5.
I just got done with v4.0, we should see a HUGE amount of battery savings with this version.
Updated to v4.3
We should see another HUGE improvement with battery life on this version.
deleted
I am just going back to 4.3 it worked good.
Version 5.1 is the best to date, This should be the final version.
Version 5.2 changed time to every 30 seconds it looks to see if it was changed from 10 seconds.
v5.3 updated magisk script
New version 6.0
Darnrain1 said:
New version 6.0
Click to expand...
Click to collapse
Excellent work.
Do I have to use the modul, or is it possible to just use the script?
andray750 said:
Excellent work.
Do I have to use the modul, or is it possible to just use the script?
Click to expand...
Click to collapse
Thanks, you can just flash in Magisk and reboot. If you wanted to you can always extract the service.sh script and place it in /data/adb/service.d/ folder and reboot, that would work also. That is if you have Magisk installed. If you don't have Magisk installed I am not sure were to place the script at.
Update: I forgot to let you know you need to make the service.sh file executable 755
Darnrain1 said:
All benchmarks started out at 100% battery on an H910 with Oreo 8.0 and Google.
Version 5.3
View attachment 5792631
Version 6.0
View attachment 5792325
Click to expand...
Click to collapse
Do you use both, Light Doze and Deep Doze, or like Tsungi "casual Light Doze or limbo Light Doze" ?
Perhaps you could show the part of your output of "dumpsys deviceidle" where to see the global settings.
andray750 said:
Do you use both, Light Doze and Deep Doze, or like Tsungi "casual Light Doze or limbo Light Doze" ?
Perhaps you could show the part of your output of "dumpsys deviceidle" where to see the global settings.
Click to expand...
Click to collapse
I am only using Light doze because you can disable the motion detector in case the phone is moved. But for the most part light doze and deep doze are just about the same.
Darnrain1 said:
I am only using Light doze because you can disable the motion detector in case the phone is moved. But for the most part light doze and deep doze are just about the same.
Click to expand...
Click to collapse
So you do that with "motion_inactive_to"?
This is what I do now.(HtcU11, android8).
I edit "force-idle" "location_acuracy";
Until "min_time_to_alarm"is it YOUR script.
Works good so faar.
Would this work on a non LG phone running A13?

[Mod][Xposed] NoWakelock - Manage wakelock/alarm/service

About​With the update of Android version, doze mode is enough to suppress the power consumption of the background of the application, but some advanced users still hope to be able to control the wakelock alarm or service by themselves.
Amplify is good enough to meet the needs of most people, but after Android N, Amplify stops updating. NoWakeLock expects to achieve the same function as Amplify does on Android N and later.
The recent 2.x release fix many of the previous bugs, so here we are.
Features​
Full control of Wakelock/Alarm/Service, no feature limitations.
Application level support
Control Wakelock/Alarm/Service by application
Application-level Wakelock/Alarm regular expression interception support.
Limited multi-user support
Support for Android N+.
Fully open source, no private data collected and stored.
Compatibility​Android 7 ~ Android 12.
Tested with the EdXposed / LSPosed.
Planned​The stable version is planned to be released by the end of this year, if you have any feature suggestions welcome to discuss in the comments section / GitHub issue.
Download: Play | Github-releases​Source Code: Github​License: GNU GPLv3 (License).​​Version Information​Status: beta
Current Version: 2.0.0-beta5
Release Date: 2022-12-4
Created 2020-4-27
Last Updated 2022-08-19
Chat group​Telegram: https://t.me/nowakelock
Discord: @NoWakelock
Donate​If my work is helpful to you, just star on GitHub is enough.
Thanks​
Amplify.
XPrivacyLua
GravityBox
FAQ​What is Wakelock/Alarm/Service and how can I set it to maximize the effect?​Official Documents
wakelock
alarms
services
Another XDA GUIDE -> [GUIDE] The Total Newb's Guide to Wakelocks
Amplify offer some Wakelock/Alarm/Service information -> Amplify
WakeBlock also offer some information -> wakelocks
Wrong operation causes the device to fail to boot​There are two cases
The reason is the bug of Nowakelock, you need to uninstall Xposed framework and enter the system to clear Nowakelock data.
Go to RE -> File Management -> /data/adb/modules and select Xposed module and delete the folder.
If you have restricted the important system wake-up lock by mistake, you don't need to uninstall Xposed framework at this time.
Go to RE -> File Management -> /data/misc/xxx-xxx-xxx/prefs/com.js.nowakelock folder and delete it
xxx-xxx-xxx is a long random string, which may be different for each machine.
If you are not sure, you can only clear the Nowakelock data after entering the system to restore the error.
Whether private data is collected​All data is local and not uploaded anywhere, except for a possible future cloud disabling solution load.
NoWakelock does not collect or store any private data.
Need new features or find bugs​Please submit them at here and I will do my best to complete them.
I would like to help update the translation​Feel free to submit a PR.
Changelog
v2.0.0-beta5
- Masking an error output. This bug is subject to further investigation.
- UI adjustment
v2.0.0-beta4
- Add data backup/restore
v2.0.0-beta3
- Fix a typing bug, the first time you type 900 you will get 009.
- Add French support thanks to [@xerta555](https://github.com/xerta555).
- Some UI tweaks, alignment.
v2.0.0-beta2-1
- Urgently fix a data logging bug, please make sure to update beta2-1 version
did we need xposed or os root enough
xn0live said:
did we need xposed or os root enough
Click to expand...
Click to collapse
In fact, for most cases, just root is enough to handle the cases where you had to use xposed + amplify in the past.
For now, NoWakelock exists only for some users who want to manage wakelock/alarm finely.
LJY-JH said:
In fact, for most cases, just root is enough to handle the cases where you had to use xposed + amplify in the past.
For now, NoWakelock exists only for some users who want to manage wakelock/alarm finely.
Click to expand...
Click to collapse
Hi, I can confirm that the latest beta is working as intended on A12. Could you make an option to differentiate between safe and unsafe wakelocks to block like amplify to avoid blocking any system wakelock and avoid bootloop, etc.
maxs8007 said:
Hi, I can confirm that the latest beta is working as intended on A12. Could you make an option to differentiate between safe and unsafe wakelocks to block like amplify to avoid blocking any system wakelock and avoid bootloop, etc.
Click to expand...
Click to collapse
Yes, I'm trying to do that.
My idea is that the wakelock description should be a loadable external file rather than written into the source like amplify, but there are problems with multi-language support, which I'm still working out.
LJY-JH said:
In fact, for most cases, just root is enough to handle the cases where you had to use xposed + amplify in the past.
For now, NoWakelock exists only for some users who want to manage wakelock/alarm finely.
Click to expand...
Click to collapse
what is the newest version for android 12 with root
xn0live said:
what is the newest version for android 12 with root
Click to expand...
Click to collapse
I am not a native English speaker, so perhaps I am misrepresenting.
What I mean is that before android Q we had to use xposed+amplify in order to control the power consumption of our devices. But after android Q we may only need to use root + NapTime to achieve the same effect.
LJY-JH said:
I am not a native English speaker, so perhaps I am misrepresenting.
What I mean is that before android Q we had to use xposed+amplify in order to control the power consumption of our devices. But after android Q we may only need to use root + NapTime to achieve the same effect.
Click to expand...
Click to collapse
naptime not needed xpsoed or? and which version work on a12
xn0live said:
naptime not needed xpsoed or? and which version work on a12
Click to expand...
Click to collapse
naptime just need root.
Naptime - the real battery sav - Apps on Google Play
Makes your device sleep faster to save precious battery life when you need it
play.google.com
LJY-JH said:
Full control of Wakelock/Alarm/Service
Click to expand...
Click to collapse
Great job !
Just here to confirm that this magic potion works on Crdroid. Good job
UI is slightly confusing. I am not sure the numbers on the right side indicate seconds or what.
Obi_Wlan said:
Just here to confirm that this magic potion works on Crdroid. Good job
UI is slightly confusing. I am not sure the numbers on the right side indicate seconds or what.
Click to expand...
Click to collapse
wakelock count time
LJY-JH said:
wakelock count time
Click to expand...
Click to collapse
That's for the numbers on the left, I think. The number of times a particular wakelock was triggered.
Obi_Wlan said:
That's for the numbers on the left, I think. The number of times a particular wakelock was triggered.
Click to expand...
Click to collapse
The counting numbers are on the left and the accumulated time is on the right.
Obi_Wlan said:
That's for the numbers on the left, I think. The number of times a particular wakelock was triggered.
Click to expand...
Click to collapse
The time display does not follow a single time unit.
It starts in seconds, then it may be minutes, hours, etc.
This uses the same code as amplify, which seems to cause some problems.
Do we have to enable the app for which we want to restrict the wakelock/alarm in lsposed when we use the nowakelock app or is it not required
just select System Framework and setting.provider.
Sometimes my device freezes and I have to restart my phone. This is what my lsposed log looks like. Does anyone know what could be causing this? I should note that I haven't turned off the wakelocks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Categories

Resources