yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] ssrij:
I have updated the APK link for latest beta (sorry for delays, was out so didn't get time to do so). It's mostly updates to translations.

I have decided against including incomplete stats in the new UI so as to not clutter it, they will be available in the old UI, and you will automatically be switched to it if there's incomplete stats saved on your device

Xposed permission issue will be fixed when I hear back from the developer about a possible fix, I don't experience this issue so it's very difficult to fix it for others

There are quite a lot of issues reported related to whitelist and not getting notifications and as I have said so many times, whitelisting does not guarantee that your app will be able to access the network and/or provide notifications. Only GCM High Priority notifications are delivered during Doze.

Noticed there was someone who had trouble streaming Spotify on WiFi even after whitelisting it. By default, WiFI is put to sleep on screen off, you can make it stay on during screen off in WiFi settings, that should hopefully fix the issues.

I have an exam on the 7th July and won't be providing any more updates until then. After that, I'll look into existing issues and fix some of the remaining fixable issues. Rest of them are highly device specific and difficult to reproduce, so I will look into them later.
[Android Apps and Games] Hawgfan486:
Started having issues again today. While changing my Locating Method setting yesterday did seem to help, it didn't fix it completely and today it just got worse. After awhile I was able to narrow down the problem. My phone was coming out of Doze everytime I put it in my pocket. I could move it around and toss it around as much as I wanted and it would stay in Doze as long as it was out in the open. As soon as I put it in my pocket I would mark the time and walk around for a couple minutes, and GSam and Greenify showed my phone exiting Doze everytime I put it in my pocket.

Anyone else experience this with 1.3.7 Rev 44? Issue with proximity sensor maybe? Or maybe just an isolated case with my phone. I realize now that I didn't notice it yesterday because I was off work and home so my phone was hardly ever in my pocket. I have since rolled back to 1.3.2 Rev 34 and so far it hasn't missed or randomly exited a Doze session regardless of what I do with my phone (knock on wood!).
[Android Apps and Games] ianmacd:
Welcome back, Suyash. I know you're a student and, given the time of year, I assumed you were busy studying for your exams.

Don't take the demands of people here too seriously. People need to remember that you've been quiet for only a week or two. Before that, you were updating ForceDoze daily, sometimes multiple times daily. We're all a little spoilt by the sterling service you provide. You don't owe any of us a thing, and I, for one, am grateful for the work you have already done, whether or not you find the time and energy to work on ForceDoze more in the future.

Regarding Xposed, which version are you using? 85.x? I have the same phone as you, so I'm curious why you would see different behaviour to me? I wonder if it could be interference from another module; perhaps Greenify? I'm just clutching at straws, really.
[Android Apps and Games] ssrij:
Sensors are disabled on screen off, so your proximity sensor will not work and won't be able to detect when your phone enters/leaves your pocket. Have you by chance turned on "Don't disable sensors on screen off"?
[Android Apps and Games] AdiSimpson:
tested with changes and without, reseting etc. everytime its empty.
[Android Apps and Games] cssoz:
And that feature would be the one under Doze enhancements 'disable motion sensing for doze (non root - experimental)'?
[Android Apps and Games] Hawgfan486:
I tried both the default settings and the non-root experimental option. I've never once checked the “don't disable sensors on screen off" option. Even if I had accidentally checked that option (even though I didnt), why would my phone not exit Doze when moving it around freely with my hand, but then exit Doze as soon as I put it in my pocket and walk around? And yes I am absolutely sure I am not accidentally hitting any button whatsoever when I put it in my pocket. Trust me, I have been troubleshooting this build being buggy for me for the past 4 days and have tried both default settings and non-root workaround settings, uninstalling and reinstalling etc.

But as soon as I installed an earlier build (1.3.2 rev 34) Forcedoze has been working perfect 100% of the time.

But yes, thank you for all the work you've put into this app! I will send another donation when I can!
[Android Apps and Games] sshark:
Do you mind uploading or sending via PM 1.3.2_rev_34 apk?

Thanks
[Android Apps and Games] kryshnakishore:
How is the new update?? Is it working well
[Android Apps and Games] SaggyAfiq:
The "Disable motion sensing for doze Root" still doesn't work properly. Other than that, app works like it is suppose to be.
[Android Apps and Games] kryshnakishore:
****, I expected, let wait for some more weeks till his exams
[Android Apps and Games] zaibansari20:
I think this app prevent phone from Deep Sleep

I was testing on it and I saw that this app prevent my phone from Deep Sleeping
[Android Apps and Games] SaggyAfiq:
Apparently the "Non-root disable motion sensing" also doesn't work for me. Which makes my phone can never go into doze mode when I'm walking etc.
[Android Apps and Games] ianmacd:
You don't actually need either the root or the non-root Disable motion sensing for Doze options. Those slightly confusingly named options keep motion detection turned on system-wide, but mask the motion from Doze.

By default, ForceDoze disables motion detection system-wide anyway.
[Android Apps and Games] Hawgfan486:
Try using the default settings. Choose the "reset to default" option if you want to be sure everything is back to default (will have to input the DUMP command again).

I've had a lot of trouble with latest build from the Play Store (1.3.7 Rev 44) keeping my phone in Doze while in motion, and a few others have stated the same. Here's what GSam logged:

This is with the latest build, trying both default settings and non-root experimental setting. Phone refused to stay in Doze:

[IMG="GSam 1"]https://s32.postimg.org/6r8oqhj85/GSam_Screenshot1.png[/IMG]

This is 2 hours later, after uninstalling the latest build and reinstalling an older build. Working great:

[IMG="GSam 2"]https://s31.postimg.org/s67d9282z/GSam_Screenshot2.png[/IMG]

This is what it looks like today. Ever since rolling back to a previous build, ForceDoze has been working perfect.

[IMG="GSam 3"]https://s32.postimg.org/72jpjwjn9/GSam_Screenshot3.png[/IMG]
[Android Apps and Games] lexullde:
It happens exactly the same in my z3c with stock rom :(

never any stats, to uninstall end because I guess it does not work well on my device
[Android Apps and Games] okij:
Thanks for reporting and your GSAM screenshots!

Which older build of ForceDoze are you using and which method of disabling of motion sensing did you select in options?
[Android Apps and Games] proag:
Could someone please upload a fully working build? Thanks
[Android Apps and Games] Arstoien:
Please don't comment before getting familiar with the development of the app and the etiquette in the forum. Demanding ignorant posts like yours have been toxic here before.

Sent from my Nexus 5
[Android Apps and Games] proag:
I've been following this thread since the beginning. I just asked for a previous build which was fully working since the newer ones are not, I don't see anything toxic in it.
[Android Apps and Games] Arstoien:
I not mentioning "previous" in your original post changes the meaning quite substantiolly imo. Anyway, good that's clear.

Sent from my Nexus 5
[Android Apps and Games] ssrij:
All builds are stable and working
[Android Apps and Games] pururava:
Need some help here... Previously i was using rev44 with root and exposed module.. Even though ignoring motion sensor part wasnt working.. At least rest of the app was working fine... E.g. Whitelisting apps, entering doze immediatly after lock screen etc..

Then i installed rev47..

From then on, having an error whenever i try to add/remove apps from Whitelist..

It says "system package id=10185 without permission android.permission.DUMP"

So even that "enter doze immediately after lock screen" isnt also working..

Things i have already tried

1)wiping app data

2)totally uninstalling app

3)reset to default from inside the app

4)uninstalling rev47 and going back to rev44 apk

5)restoration of backup of rev44 with data from titanium backup which i was sure was working for me

6)enabling /disabling xposed module

7)permission changes from supersu app to make sure forcedoze app is getting proper su permission

I am at my wits end.. Why isnt even rev44 working anymore..

Why isnt it getting dump permission even on root?
[Android Apps and Games] ssrij:
Are you rooted? The error is being caused by the missing DUMP permission, which is automatically granted when you accept the root request. If you're not rooted then you have to grant it manually via ADB.

I would recommend doing a full uninstall (remove any backups or files) and make sure no files are left over in /data/app and /data/data related to the app
[Android Apps and Games] pururava:
Yes..rooted..

And tried full uninstall too multiple times...

It worked good for 4-5 days on rev 44..

Then i tried rev 47 and thats where error started..

I got dump permissions initially.. Used app for 5-6 days.. N now m nt getting dump permission
[Android Apps and Games] ssrij:
See my edited post
[Android Apps and Games] pururava:
I too edited my post... :p:p

---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------

Even though i tried uninstalling n re-installing multiple times.. I will try it 1 more time (may be i ll get lucky this time) n get back to you about its results.
[Android Apps and Games] ssrij:
Strange, I don't know what is revoking the permission on your phone. Maybe check the logcat to see what's going on (after it happens with you). The DUMP permission is never revoked unless you uninstall the app (obvious) or reset the app from the app's Settings.
[Android Apps and Games] pururava:
Ok.. I am back after testing..

Steps i took

1) uninstalled forcedoze

2)went to root explorer and opened /data/app and /data/data and confirmed there was nothing related to "com.suyashsrijan.forcedoze"

3)rebooted phone

4)to be on safe side, opened google play store and downloaded your app from scratch instead of using old apk

5)granted su permission.... Still NO DUMP PERMISSION

6)activated xposed module and rebooted phone.. Still NO DUMP PERMISSION

There is one minor change.. I dont know if it is of any importance..

The error msg "system package uid=10185 without permission android.permission.DUMP" shows different number now... It shows 10003 instead of 10185...

Should i send logs to you?
[Android Apps and Games] ssrij:
Yeah send them to me. Which device are you on?
[Android Apps and Games] pururava:
Motorola g4 plus XT1643 with android version marshmallow 6.0.1

I dont know how to attach files from phone so sent logs with Dropbox direct share links.

Hope it's okay with you.

App log - - - > https://db.tt/SuE3H5id

Full LogCat - - - > https://db.tt/rPLFn5b1
[Android Apps and Games] kulguy:
ForceDoze on non-root doesn't work.

I did a factory reset and installed ForceDoze on that clear system. And still it refused to work properly.

It worked well until two or more updates before the last build. Maybe the dev made a mistake then.

This time, I didn't install Greenify at all, so nothing could conflict with ForceDoze about Doze.

Could someone give me a link of ForceDoze working build? from what I read from this thread, 34 or so build seems to work properly.
[Android Apps and Games] freezingpoint:
I was using rev 44 and suddenly the disable motion sensor stopped working. Installed the beta version, still the same. Using s7 edge.
[Android Apps and Games] ssrij:
Have you changed any settings?
[Android Apps and Games] dobermann24:
Hey. After install beta doze dont work. Now i go back whit reset setting and reinstall. Doze dont work anymore.
[Android Apps and Games] boomop:
ForceDoze is working perfectly on my OPO (SultanXda 13.1)
[Android Apps and Games] ssrij:
Before reporting any issues, grab a logcat and attach it with your post. Simply posting "It doesn't work" is not helpful
[Android Apps and Games] turtle254:
v 1.3.7 rev46 Works perfectly on galaxy s6(non root) .... set at Default position. Thanks
[Android Apps and Games] dobermann24:
Thats true. Here its log
[Android Apps and Games] sohailss111:
Can someone help me in breaking this down and understanding it...
[Android Apps and Games] AdiSimpson:
After updating ROM with wiping dalvik+cache statistics are working now.

Also ForceDoze works now after setting delay to 1. At setting 0 it does not really work. I have 1.3.7 b46 installed.
[Android Apps and Games] putti71:
Hi. Since today i am using this app with xposed module, but in betterbatterystats it shows that the app takes 4% of battery usage. Isn't that too much?

Gesendet von meinem SM-G935F mit Tapatalk
[Android Apps and Games] manuela1986:
I have a funny 'problem'. I have a rooted galaxy s5 with stock 6.0.1. This app mostly works, but... I use PowerAmp alot. Whenever the screen is off, GSAM says the phone is in doze mode even though the PowerAmp is active. Which is cool, I think the battery drains slower than before using this app. That 'doze line' on that graph is full almost all the time when the screen was off. I have the motion sensors disabled in the Force Doze app, so this works fine even when I am on a bus to work, listening to music with my headphones. On nightshifts I also listen to my music during my worktime. And this is where it gets funny. As soon as I start working and walking with my music on, the doze line shows that the phone wakes up five or more times every single minute. And battery drains faster because of that ofc. The screen is off and all. I don't understand, how is it that the doze works fine when I am on a bus and the phone is obviously moving, but it starts waking up when I am walking? I don't know alot about Android, so I apologize, if my question is stupid to others with more knowledge.
[Android Apps and Games] AdiSimpson:
So did some tests, and for me it goes only into doze with delay 1, with setting 0 it does not work.
[Android Apps and Games] leonguerrer0:
should i check disable motion sensing for doze? thanks
[Android Apps and Games] chrcol:
I put this on my opo phone which I am currently struggling to maintain good idle battery life since upgrading it to MM. Last night I installed it, activated the disable sensor options, made instant freeze on screen off, turned off in greenify so no conflict and I went to sleep, the battery had about 20% left.

9 hours later I tried to wake up phone and dead, so 20% went in that 9 hours, with wifi and mobile data off. Currently charging so I can boot up the phone but doze for me hasnt been a great experience.

On my s5 901f I have turned doze off completely (at least I think I have but greenify is still sending me doze notices) and now have battery life the same as kitkat on that phone. On my oneplusone I was getting 20 days battery life on omnirom 5.1 although that was after I fixed a load of google wakelocks. I cannot remember which wakelocks I fixed so the same hasnt been done on CM13 6.0 but with doze the phone is worse in idle than it was on 5.1. and I am still trying to fix it.
[Android Apps and Games] Hawgfan486:
The apps default settings disable the motion sensors system-wide. So there's nothing you have to check in the settings to get the sensors disabled feature.

The Disable Motion Sensors for Doze is an experimental workaround feature that doesn't disable sensors system-wide, instead it just prevents the Doze feature itself from having access to the sensors. If you have issues with the experimental option, uncheck it and the default settings will still prevent your phone from exiting Doze upon movement.

Those screenshots are of build 1.3.2 Rev 34. And I'm just using the default settings, because this is an older build that actually doesn't even have either of the experimental workaround options.

I'm still using that build and its been working perfect for me. I don't want to put off people from using the latest build. Obviously, if the latest build works for you than you should definitely use that one instead. It just hasn't worked consistently for me, so I'm opting for an older version, at least until another build comes out and I'll try that one.
[Android Apps and Games] milojoseph:
Alright I'm testing lastest beta and I can confirm that it doesn't help phone go to doze mode. I have to revert back to an old mod
[Android Apps and Games] johno4444:
I had the same issue, so have uninstalled the beta version. The phone was not going into deep sleep otherwise
[Android Apps and Games] sohailss111:
Hey guys. Please help. I have a Galaxy S6. Non rooted. I don't want to root it also. Which build is working properly right now without any bugs? As in doze is working properly and also doze doesn't wake up because of any movement ( what options to tick for this?).
[Android Apps and Games] ssrij:
If you turn on an experimental option and say the app's not working then I cannot help here. In the screenshot above, Disable Motion sensing for Doze, which is an experimental option, is turned on. Try again with the option off
[Android Apps and Games] ssrij:
The only possible way for the app to use significant battery is when you've either turned on Doze Delay or turned off Ignore Lockscreen timeout in the app's Settings, which makes the app use a temporary wake lock for the duration of the delay/timeout and the effects of the wake lock can increase if you turn on/off your phone a lot.
[Android Apps and Games] ssrij:
That's a little strange, can you try setting the delay back to 0 and let the app work for a few hours and provide a logcat?

Also, have you change any other setting in the app?
[Android Apps and Games] Arstoien:
Even when I have the delay set to 0s, the log says "Waiting for 300000ms and then entering Doze", and then when I turn on the screen it says "Cancelling enterDoze() because user turned on screen and 300000ms has not passed or disableWhenCharging=true" (I'm not charging).
[Android Apps and Games] leonardoroza:
I'm getting CMActions FC with it. Anyone?
[Android Apps and Games] liver20:
Doze settings editor, not have wakelocks. With force doze that is awesome, too wakelocks.

Enviado desde mi Z1 mediante Tapatalk
[Android Apps and Games] ssrij:
That's because your lockscreen timeout is probably set to 30 mins, you can change that in Security Settings on your phone. The delay used by the app is calculated by adding the lockscreen delay (so Doze doesn't kick in before the OS locks your phone) + the user specified delay. For me, I've set it to lock 'Immediately' so the delay for me is 0 + 0 (in Doze Delay) = 0ms
[Android Apps and Games] Arstoien:
Aah, ok, that's really useful info. So in that case it's probably working perfectly. Maybe worth adding as a footnote or something, that the "Doze delay" starts after the screen is locked. Perhaps changing the description of the setting from "Add a delay before Doze mode kicks in after screen-off" to "... after screen is locked".
[Android Apps and Games] ssrij:
It's still the same thing, because the screen would only be locked by the OS if the screen is off (the OS would automatically turn off the screen if the screen is not off before the lockscreen timeout).
[Android Apps and Games] Arstoien:
What I meant was only that "screen off" to me means me turning off my screen. The screen isn't locked at the same point in time, but some fixed time afterwards. So to me it sounded like "locked" is more accurate. Just a suggestion. Thanks for the responses and info. Just tested it and it's working just fine.

PS: One question: if I have some apps, which I've set to "not optimised" in the OS battery optimisations, they should also work as whitelisted when dozing with your app, right? I'm asking, since your "whitelist" setting doesn't show the apps that I've whitelisted in the OS. Are the two different in any way?
[Android Apps and Games] JuanVillagran:
Downloading right now, but i have a question, can ForceDoze work with Greenify? I mean does it create any kind of problems or do i have to uninstall Greenify?

Edit: It doesn't ask for root permission, is that normal?
[Android Apps and Games] ssrij:
If it didn't ask for root then most likely your root app automatically granted it root without prompt. I am not completely sure why that happens
[Android Apps and Games] colonel_lp:
[MENTION=5427507]ssrij[/MENTION] I posted this on last page but don't know if you saw it :

05-17 07:41:35.161 I/ForceDoze(11213): android.permission.DUMP already granted, skipping SU check

there is nothing in super SU logs to say anything about force doze, and force doze debug logs are greyed out so it doesn't have root. maybe it tells you what you need to know.

xperia Z3 d6603 | RSXW mm
[Android Apps and Games] Ashray_Vk:
Hey [MENTION=5427507]ssrij[/MENTION]

Have you checked the log I posted a few pages back ? Does that help with the problem I had mentioned even after updating to the latest version ?
[Android Apps and Games] restNow:
First of all, thank you [MENTION=5427507]ssrij[/MENTION] for this awesome app! I love it.

But I have one problem, i don't know if it's just my setup or something else.

I have a lockscreen setting of 30 seconds (Android Settings - Lockscreen - "Automatically Lock" > after 30seconds). Additionally i have a ForceDoze timeout of 1 minute - which adds to 90 seconds. With this settings it almost never works - see my log:

05-17 20:02:31.489 6793 6793 I ForceDozeService: Screen OFF received,
05-17 20:02:31.496 6793 6793 I ForceDozeService: Waiting for 90000ms and then entering Doze,
05-17 20:07:17.419 6793 6793 I ForceDozeService: Doze delay: 1ms,
05-17 20:07:17.419 6793 6793 I ForceDozeService: Screen ON received,
05-17 20:07:17.422 6793 6793 I ForceDozeService: Cancelling enterDoze() because user turned on screen and 90000ms has not passed or disableWhenCharging=true

It should have entered Doze-Mode at about 20:04:01, but that didn't happen.

When i set both timeouts to 0, it works most of the time, like this:

05-17 18:41:25.283 4561 4561 I ForceDozeService: Screen OFF received,
05-17 18:41:25.289 4561 4561 I ForceDozeService: Waiting for 0ms and then entering Doze,
05-17 18:41:25.298 4561 4561 I ForceDozeService: Entering Doze,
05-17 18:41:37.770 4561 4577 I ForceDozeService: Now forced in to idle mode,
05-17 18:42:21.422 4561 4561 I ForceDozeService: Disabling motion sensors,
05-17 18:42:21.537 4561 4561 I ForceDozeService: Doze delay: 0ms,
05-17 18:42:21.537 4561 4561 I ForceDozeService: Screen ON received,
05-17 18:42:21.538 4561 4561 I ForceDozeService: Exiting Doze,
05-17 18:42:21.619 4561 4692 I ForceDozeService: Stepped to: ACTIVE,
05-17 18:42:22.579 4561 4561 I ForceDozeService: Re-enabling motion sensors

Some weird behaviour i just noticed in this log: "Disabling motion sensors" is just happening when screen is turned on.

Do you know what could be the problem here?
[Android Apps and Games] marvasten:
Moto G 2015

Nice app. However settings are not available for me. I'm on Moto G 2015, rooted and I know this doesn't have the gyroscope sensor (so doze is not 100% functional). Is that the reason? If not, what is the problem?

Can be this used with Greenify aggressive doze at the same time?