yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] ssrij:
That's strange, I don't understand the relation between Doze and Samsung Pay. It's weird it would cause Samsung Pay to stop working. Did it work when you enabled the option to not disable motion sensors on screen off (motion sensors is also unrelated to Samsung Pay but still)?
[Android Apps and Games] ssrij:
Yeah I have other things to do in a day, but I'll be pushing a new update soon to the beta channel
[Android Apps and Games] optimummind:
Even after uninstalling ForceDoze, Samsung Pay never came back. I had to do a factory reset to revive it.
[Android Apps and Games] ssrij:
Hmm, my phone is rooted so I cannot really check what's going on (because I can't use Samsung Pay on a rooted phone). Have you tried using Android Pay instead?
[Android Apps and Games] optimummind:
No, I haven't tried Android Pay.
[Android Apps and Games] kumbangdesa:
I'm rooted and using v1.3.7 rev44 but I can't tick "disable mobile data during doze". I'm back to previous version v1.3.3 rev 37 that I'm always using it before.

Sent from my Note5 SM-N9208
[Android Apps and Games] ssrij:
What happens when you try ticking it? Are you rooted?
[Android Apps and Games] kumbangdesa:
Yes I'm already root. Can't tick it because it greyed out.

Sent from my Note5 SM-N9208
[Android Apps and Games] ssrij:
Try reinstalling, should fix it
[Android Apps and Games] Knox316:
sorry for the quetion but, whats the difference? http://xdaforums.com/android/apps-games/root-doze-settings-editor-android-t3235130

too many similar apps on xda :S
[Android Apps and Games] Ipse_Tase:
Ummm...did you READ? "Requires root". Case closed.
[Android Apps and Games] kachimasu:
I just installed and configured.

Is the service running in the background when I close ForceDoze app?
[Android Apps and Games] Broken303:
as long as the service is activated on the apps mainscreen. unless you disabled it, you should also be able so see a persistend notificafion, which is an indication for the service being active.
[Android Apps and Games] Ritchiejoe:
Would someone be kind enough to simplify how I whitelist apps etc via tasker? :confused:
[Android Apps and Games] bigmike35:
Can anyone suggest settings that need to be check on/off for a Stock, non-rooted user. I have a S7 Edge. I already ran the ADB commands to get the app to work. Currently just have, turn off while charging checked, show presistent not checked, ignore lock screen check and disable motion sensing for doze checked, set at 2 mins or value is at 2 (assuming it is mins). Should anything else be checked or not check. Been trying to read through thread but keep seeing rooted users more. Thanks for the feedback
[Android Apps and Games] Hawgfan486:
Create a new task and select the plus sign in the bottom center to add an action, then select System > Send Intent. To add an app to whitelist, put com.suyashsrijan.forcedoze.ADD_WHITELIST under Action. Under the first Extra, put "packageName:name.of.your.package." So say your app is GSam Battery Monitor, under Extra you would put exactly this: packageName:com.gsamlabs.bbm

And do the exact same thing to remove the app from the whitelist just change the intent to com.suyashsrijan.forcedoze.REMOVE_WHITELIST under Action. And then just add the tasks to a context to create a profile.

If you're new to tasker: try just testing it out first by something simple like your context being State > Display > Display Orientation and change Is to landscape. Then add the Send Intent task you just created (the one that adds an app to the whitelist) to that Display State context to create a profile. On the profiles tab, select and hold on the Send Intent task you just added (it should now be next to a green right arrow) and then select Add Exit Task, and add the Send Intent task you created that removes the app from whitelist. That should now show up next to a red left arrow, directly underneath the first Send Intent task. Now you should be able to do a simple test to make sure it's working right by opening up ForceDoze, rotating your device to go into Landscape mode, and check to see if your app was added to whitelist (while still in landscape mode). If it was added, rotate back to portrait mode and back out of the whitelist and go back in and the app should no longer be there.

---------- Post added at 10:59 PM ---------- Previous post was at 10:40 PM ----------

I have been getting some inconsistencies with GSam Battery Monitor, is this normal? ForceDoze logs that it always goes into Doze mode. GSam sometimes shows differently. I also have Greenify and have turned on it's Doze notifications to also help keep track (I don't have it's aggressive doze option enabled, just using its Doze notifications). Greenify's notifications are ALWAYS the same as what GSam shows. Does ForceDoze always log the screen time off as a Doze session even if the phone doesn't actually "Doze"?

not sure if these screenshots are gonna show up but I'll try. Not sure what the rules are about images on here so I'll hide them in case they are really large for some reason

[IMG="screenshot1"]https://s32.postimg.org/9obwvl2v9/Force_Doze_screenshot1.jpg[/IMG]

[IMG="screenshot2"]https://s32.postimg.org/kjahnfath/Force_Doze_screenshot2.jpg[/IMG]
[Android Apps and Games] NickosD:
Can someone explain me what the "disable motion sensing for doze" do?

It will disable the motion sensors while doze is active so it won't be interrupted?
[Android Apps and Games] noisyriver:
I noticed exactly the same here with the newer FD versions. GSAM shows me no force doze sessions anymore. So I'm back to 1.3.2_rev_34 which works very well for me. I have the feeling, something is wrong with newer updates.
[Android Apps and Games] milojoseph:
Can you share apk plz
[Android Apps and Games] Freezy202:
Yes as you already said :)
[Android Apps and Games] B3311:
Same here, mentioned it in an earlier post.

Rev 38 works for me, nothing later.
[Android Apps and Games] okij:
Looking at GSAM, I often see the same, especially for the nighttimes (when my phone is connected to the Wi-Fi network), but so far I didn't care as I still have the feeling that ForceDoze works. But then again, I always had low battery consumption at night, as the Wi-Fi signal is very good, so I'm not sure.

Anyway, for tests I switched back to rev 34 for last night and GSAM also didn't show the Doze periods. Not sure about rev 38, maybe I should test this again too.

BTW, I'm using the "Disable motion sensing for Doze (root)" method.

I hope that [MENTION=5427507]ssrij[/MENTION] can give us some feedback on this issue (ForceDoze stats vs. GSAM and Greenify stats) and will have a look into it.

Looking at the GitHub repository, I'm a bit worried that there hasn't been any work on this project since two weeks now. :crying:
[Android Apps and Games] ps89:
Since you're using the root method, you can look at the Xposed log to make sure the feature is working. The Xposed log should contain the following line:

ForceDozeXposed: usePermanentDoze: false, useXposedSensorWorkaround: true, serviceEnabled: true.

The feature has been a hit or miss for me. Most of the time my Xposed log shows:

ForceDozeXposed: usePermanentDoze: false, useXposedSensorWorkaround: false, serviceEnabled: false.

So I'm using the non-root method for now.

Hope this helps. :)
[Android Apps and Games] okij:
I just took a look at my Xposed log and saw exactly the same. :(

So ForceDoze isn't working at all in this case? :confused: I'm asking because ForceDoze's battery stats state that the device is entering and exiting doze mode as it should. Are the ForceDoze stats wrong and the GSAM graphs and Greenify logs right?

We really need [MENTION=5427507]ssrij[/MENTION] to look after this.

[MENTION=5335027]ps89[/MENTION]: Which version of ForceDoze are you running? Do you use the "Disable motion sensing for Doze (non-root, experimental)" option? When I tested this feature the last time (the version it was introduced), it was exiting and re-entering Doze mode like havoc when the device was moved, thus doing more harm than good and leading to a quite high battery drain.
[Android Apps and Games] ps89:
Hello [MENTION=4916555]okij[/MENTION], With the 'false' values, ForceDoze still puts the device into Doze quickly. However, I believe any movement will cause the device to exit from Doze.

Based on my observation, disabling the 'Disable motion sensing for Doze (root)' option, restarting your device, enabling the option and restarting your device will make the feature work. But, it'll go back to square one once you restart your device again.

I'm running the latest beta version. I haven't had much luck in getting the root method to run properly since I started using ForceDoze when it was at version 1.2.x. The non-root method is working for me but definitely not as good as the root method (when it was working properly).
[Android Apps and Games] turtle254:
I hope he has not given up on this project !

This is probably the best Apps I have, and his work is greatly appreciated

by all.
[Android Apps and Games] okij:
I now also tested this behaviour, with the following result:

Just toggling the "Disable motion sensing for Doze (root)" option off and on before rebooting does the trick, so you don't have to reboot between disabling and enabling this option.

Rebooting without first toggling this option leads to the observed bug, i.e. in the Xposed log useXposedSensorWorkaround and serviceEnabled are both false and Doze is not working properly, which can also be checked in GSAM graph.

So there must be a bug in ForceDoze or its Xposed module which prevents that the current state of "Disable motion sensing for Doze (root)" is properly interpreted, so it has to be disabled and re-enabled before each reboot. [MENTION=5427507]ssrij[/MENTION]

I'm wondering if the users who reported that the Xposed module isn't working on their device actually "just" experienced this bug.
[Android Apps and Games] ps89:
Toggling the setting before rebooting works. Thanks for the tip. :)
[Android Apps and Games] milojoseph:
can you guys share apk plz
[Android Apps and Games] okij:
Thanks for confirming! :)

I think with this information this bug should be fixable quite easily by [MENTION=5427507]ssrij[/MENTION]. :fingers-crossed:

---------- Post added at 08:58 AM ---------- Previous post was at 08:44 AM ----------

I shared the rev 38 apk here. Again, I hope that this is OK for [MENTION=5427507]ssrij[/MENTION], otherwise I will remove the file again.

Generally I don't think it's a good idea to keep and use old versions that aren't maintained anymore by Suyash.

But because of this it's just the more important that the remaining bugs get fixed soon.

Please. :):)

BTW, [MENTION=5427507]ssrij[/MENTION], in the meanwhile I managed to get ForceDoze turned off while doing a GPS recording with Tasker and Notification Listener plugin, so even though it still would be a nice feature for ForceDoze to to automatize this (as other, similar apps don't have such feature), I don't consider it as too important anymore. ;) There are more important things to fix, e.g. the Xposed module issue that [MENTION=5335027]ps89[/MENTION] and me talked about in the last couple of posts.
[Android Apps and Games] liver20:
Tonight i left 6%

Wakelock

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[Android Apps and Games] kryshnakishore:
Disable motion sensing for doze- if I enable this what happens? Can any one explain pls

---------- Post added at 08:31 AM ---------- Previous post was at 08:29 AM ----------

Thanks for old APK, do u have still the oldest apk? Bcoz initial apk tend to work better
[Android Apps and Games] kryshnakishore:
Oh cool so enabling it makes FD even better. Thanks for the info
[Android Apps and Games] AdiSimpson:
My Doze Battery stats are always empty. Is this a bug?
[Android Apps and Games] kryshnakishore:
Did u enable app or check privacy settings of app
[Android Apps and Games] AdiSimpson:
Yes its enabled, privacy there is only phone setting and its enabled.
[Android Apps and Games] kryshnakishore:
Then reset app & reboot, this should help
[Android Apps and Games] AdiSimpson:
I did, but still empty.
[Android Apps and Games] B3311:
No, the opposite.

http://xdaforums.com/showthread.php?p=67393787
[Android Apps and Games] zsandras:
Thank you very much mate, your post helped me to start ForceDoze to work :good:

---------- Post added at 02:50 PM ---------- Previous post was at 02:26 PM ----------

Thank you mate for experience sharing.:o
[Android Apps and Games] Hawgfan486:
Not exactly. From what I understand, there are 2 ways to have ForceDoze keep your phone in Doze even while your phone is in motion. The first way is with the Default settings. ForceDoze, by default, disables your phone's motion sensors system-wide to prevent your phone from exiting Doze when your phone is moved. Some people reported issues with disabling motion sensors system-wide, so ssrij gave the option of another way to keep your phone in Doze during movement. This workaround setting effects the motion sensors for just Doze itself, instead of disabling sensors system-wide. It's an experimental feature, as it says in the app's settings.

At least that is my understanding of the settings. Someone let me know if I am incorrect in any way! Here is ssrij explaining the experimental workaround feature:

edit: this is my understanding of the features on a non-rooted device, I'm not sure exactly how the root option works.
[Android Apps and Games] cssoz:
Does using ForceDoze via no-root + DUMP permission mess up with sensors features for 1+3, like the wave your hands, flip cover etc?

or you already have a fix for this ?

Thanks
[Android Apps and Games] Ritchiejoe:
I thought this app had revived my android experience, but after a week my battery is flying back down again :(
[Android Apps and Games] moriel5:
Try an older version.
[Android Apps and Games] Hawgfan486:
Have you been tracking the Doze sessions with something like GSam? It will show you if your phone is still entering and staying in Doze mode properly. As much as I love this app and as much as it's helped my battery life, the logs in the app that show the Doze sessions aren't always accurate. In my experience, ForceDoze just logs the screen time off as a Doze session even if the phone doesn't actually "Doze". Only way to accurately track your Doze sessions is with GSam, or even Greenify's Doze Notification option.

Anyway, after a couple days of ForceDoze working great, I noticed that ForceDoze wasn't keeping my phone in Doze whenever in motion. After a day or two of frustration and changing settings and uninstalling/reinstalling the app, I realized that I had changed my Locating Method on my phone's setting to GPS Only. Ever since I changed the setting back to High Accuracy, ForceDoze has been working great and keeping my phone in Doze 95% of the time. I don't know if anyone else has experienced this or if it's common knowledge and I'm just late to the party, but try changing your Locating Method setting if it's on GPS Only.
[Android Apps and Games] Ipse_Tase:
Not in my experience it doesn't. I still get to wake up the phone waving the hand over the proximity sensor...and get vibration notifications when i pick up the phone and have a missed event.

---------- Post added at 14:25 ---------- Previous post was at 14:24 ----------

BTW: where would one find "an older version"? Usually I do app backups, but for a while we were getting daily updates so I couldn't keep pace. Would be nice to still have access to a few versions...one never knows.
[Android Apps and Games] noisyriver:
Interesting, I'm also on GPS only. And I observed exactly the same, with newer FD I have no doze sessions anymore when device is in motion. According to GSAM. Older versions work fine.

[MENTION=635976]ssr[/MENTION]ji should really look into this.
[Android Apps and Games] Hawgfan486:
Yea I've been using the 1.3.7 Rev 44 build that's currently the version in the Google Play store, and it has been a night and day difference with Forcedoze depending on what my Locating Method setting is on. I just found out about this app about a week ago, so I'm not sure if any of the earlier builds were affected by the Location setting on your phone or not.
[Android Apps and Games] Joy Bangla:
how to check doze sessions in GSAM? do i need pro/root?
[Android Apps and Games] ianmacd:
I am one of the people for whom the Xposed module has never worked, so I was intrigued to read that I may be able to cajole it into working simply by toggling the Disable motion sensing for Doze (root) option off and on. On the other hand, it was hard to imagine that I hadn't already done that multiple times in an attempt to get the module working.

Sure enough, after toggling that option off and back on and then rebooting, the Xposed module still didn't work. I tried it multiple times and the module always failed to be properly hooked on reboot.

Next, I tried toggling the Xposed module itself. I disabled and reenabled it, and then for good measure also disabled and reenabled ForceDoze via its master switch. Finally, I toggled the Disable motion sensing for Doze (root) option again and then rebooted. This time, the Xposed module came up active.

So, simply toggling Disable motion sensing for Doze (root) doesn't work for me, but in combination with toggling the Xposed module

itself and the ForceDoze master switch, it does. I haven't done any further testing to determine whether either of the latter two actions can be omitted without changing the result, but I suspect that toggling the Xposed module does nothing useful.

It would be great if [MENTION=5427507]ssrij[/MENTION] could look into this bug. It seems that it should be fixable with relatively little effort.
[Android Apps and Games] kryshnakishore:
Development is ending. Thread will be closed
[Android Apps and Games] carabinieri5675:
Why?

Gesendet von meinem ONEPLUS A3003
[Android Apps and Games] pomhg:
Hi [MENTION=5427507]ssrij[/MENTION], looks like even I got rooted, moving the app to /system/priv-app folder and changing the app permission with 644, still not working on android N DP4.

...ForceDozeService: Security exception: Neither user 10094 nor current process has android.permission.DEVICE_POWER., 06-28 11:10:34.739 5369 21160 I ForceDozeService: , 06-28 11:10:34.739 5369 21160 I ForceDozeService: java.lang.SecurityException: Neither user 10094 nor current process has android.permission.DEVICE_POWER....

Here is the log.

View attachment app_log_forcedoze.txt
[Android Apps and Games] okij:
Thanks for reporting this!

Now please also have a look if the "Disable motion sensing for Doze (root)" function keeps working all the time (as long as you don't reboot, of course.)

For me it stopped working again after some hours and the GSAM graph showed no (or only very short) Doze periods then.

Therefore I currently try the "Disable motion sensing for Doze (non-root)" option again and so far it's working quite nicely. When I tried this option the first revision it was introduced, I wasn't happy with it, because Doze was turned off and on like havoc when moving the device, which seems to be fixed in the current 1.3.7 rev 44. I still have to observe if the battery savings are appropriate in everyday use.

+1 for this.

[MENTION=5427507]ssrij[/MENTION], where are you? Some days ago you wrote that you'll be pushing a new update soon to the beta channel. Please give us at least a short feedback. Our discussions about ForceDoze are a bit pointless when the developer isn't participating and we don't even know if they are heard. We miss you.
[Android Apps and Games] ianmacd:
Bummer. It was short-lived for me, too.

It was definitely working for me last night in the small hours, but I just biked the children to school, returned home and then noted the familiar and annoying spurts of 15 to 30 seconds of Doze as the device had repeatedly gone to sleep and awoken from the motion.

Literally the only thing done with the phone between getting the Xposed module working and leaving the house this morning was plugging it in to charge it. I wonder if the disabling of Doze that is performed when the device is connected to a power source is the culprit here, toggling something about the module that is not restored when the device is disconnected again.

So, it seems that there are at least two bugs related to the module: It's tricky to activate it in the first place and then tricky to keep it active over time. Perhaps they are related.

Back to system-wide motion disablement for the time being.
[Android Apps and Games] B3311:
I'm out of here until the dev deigns to address our problems .

The problens are myriad and yet [MENTION=5427507]ssrij[/MENTION] has not been around to reply to any of them. I notice currently that FD isn't even present in my Xposed logs and I've tried every fix posted here.

I appreciate that devs have lives too. But so many different problems posted, we're trying unsuccessfully to fix them ourselves and the only man with the answers is hugely conspicuous by his absence.. draw your own conclusions. I have. And it's no offence to [MENTION=5427507]ssrij[/MENTION] but if he doesn't want to help for whatever reason, say so. We need your help. Do you want to or not? No biggie either way - your app your life, your time, your choice - but I think many of us would appreciate an answer.
[Android Apps and Games] ssrij:
I've already talked about most of the issues some people are facing many pages back, they aren't new. Those issues don't have any immediate fixes, for example, the Xposed module not activating properly is a permission issue related to Xposed and I've had an extensive discussion with the developer and the developer of GravityBox over at GitHub some time back, and I am looking to reopen it because initially it worked fine but I guess the issue is appearing for some users.

It's very difficult to fix issues which I cannot reproduce and issues about which I cannot gather technical information from logs. I watch the thread every day, but I cannot post anything unless I have fixed the issue(s). I have already pushed a new update earlier this morning to the beta channel that fixes some of the issues, but more will be fixed with time.
[Android Apps and Games] ssrij:
Such low values will waste battery even more (i.e if you turn off screen and turn on again many times) i.e making the device enter/exit Doze more frequently will deplete battery life faster.
[Android Apps and Games] B3311:
Thank you. I'll test again tomorrow and posts more logs than you need?
[Android Apps and Games] ssrij:
As I explained many pages back, the app creates a log entry when it makes your device enter Doze and again when it makes your device exit Doze. If your device gets knocked out of Doze for some reason (i.e movement), it won't be logged, and as a reason, the stat will not be accurate.
[Android Apps and Games] turtle254:
New update is not on your web site? For a side install.

Thanks for your work.
[Android Apps and Games] ssrij:
Have you changed any settings in the app? Can you provide a logcat?
[Android Apps and Games] ssrij:
Yes, the only way around it would be to not disable sensors from Settings, but that would make your device exit Doze on movement
[Android Apps and Games] ssrij:
Yeah, some things have changed in Android N thus preventing the app from running properly on N Developer Preview. I am not sure if there's a fix for it, but I'll post an update when I can find one
[Android Apps and Games] okij:
Hi ssrij, it's great that you are back here!:good:

I'm on the beta channel but didn't receive an update yet.

Moreover, the latest changes on your GitHub repository are 5 days old and just translation fixes.

So what's been changed in the code and where's the update??
[Android Apps and Games] ssrij:
Updates take up to 24 hours to be live, should be live soon. I'll just update the APK link now. I've been out all day so haven't had the chance to push the code yet, but will do shortly