Can anyone confirm whether the G3 supports Doze?
It isn't mentioned in the Android M changelog for the G3, but is present in the Moto X Style changelog.
Moreover, Doze requires a 'significant motion detector' sensor to work, and sensor apps report it missing on the Moto G. Could it be because of the Sensor Hub/ lack of gyroscope?
To check whether Doze actually works: https://www.reddit.com/r/nexus5x/comments/3y8144/guide_finding_battery_issues_with_googles_battery/
tldr: take a bug report, extract the txt from the zip and upload it to Battery Historian 2.0
I looked at the output of my phone, there was no Doze bar, which means Doze did not even activate. Installed the new Greenify and forced aggressive Doze, which seemed to trigger Doze.
I'm not adding this to the general/battery thread as this is a separate issue.
Don't know if the G3 supports doze as I'm still waiting for the MM update (EU version).
But lack of gyroscope / suitable sensors _hardware_ is certainly not an issue.
See Google's specification for doze and SMD API.
https://source.android.com/devices/tech/power/mgmt.html
http://source.android.com/devices/sensors/sensor-types.html#significant_motion
The accelerometer in the G3 is perfectly fine for this purpose.
Might just be that Motorola has screwed in properly exposing this via the SMD API.
Its says we have doze here
http://motorola-blog.blogspot.co.uk/2015/10/marshmallow-and-smore.html
Doze mode isn't an "option" in Marshmallow, all devices will have it, it is a part of the core OS.
So yes, the Moto G has Doze Mode.
acejavelin said:
Doze mode isn't an "option" in Marshmallow, all devices will have it, it is a part of the core OS.
So yes, the Moto G has Doze Mode.
Click to expand...
Click to collapse
Yes it's part oft the core OS. Question is whether Moto G3 can make use of it. And that's only the case if a sensor like e.g. accelerometer is properly exposed via hal to trigger significant motion events.
Something which Motorola at least for the Moto G 2014 in the MM update apparently did not do for some reason. In CM13 devs were able to do it though. See discussions in Moto G 2014 forum.
So the question if Doze is properly working on Moto G3 or if Motorola also missed to properly expose the sensor is quite valid.
with greenify and root we can enable aggressive doze.... and seem to works
u42671 said:
Yes it's part oft the core OS. Question is whether Moto G3 can make use of it. And that's only the case if a sensor like e.g. accelerometer is properly exposed via hal to trigger significant motion events.
Something which Motorola at least for the Moto G 2014 in the MM update apparently did not do for some reason. In CM13 devs were able to do it though. See discussions in Moto G 2014 forum.
So the question if Doze is properly working on Moto G3 or if Motorola also missed to properly expose the sensor is quite valid.
Click to expand...
Click to collapse
I know, but it seems like the Significant Motion Detector sensor hasn't been exposed (to apps atleast); Doze cannot function without it.
Doze require the SMD sensor and GCM support.
..::Matr!x::.. said:
with greenify and root we can enable aggressive doze.... and seem to works
Click to expand...
Click to collapse
I know, my phone goes into Doze with Greenify, doesn't work without Greenify.
u42671 said:
Yes it's part oft the core OS. Question is whether Moto G3 can make use of it. And that's only the case if a sensor like e.g. accelerometer is properly exposed via hal to trigger significant motion events.
Something which Motorola at least for the Moto G 2014 in the MM update apparently did not do for some reason. In CM13 devs were able to do it though. See discussions in Moto G 2014 forum.
So the question if Doze is properly working on Moto G3 or if Motorola also missed to properly expose the sensor is quite valid.
Click to expand...
Click to collapse
The point is, we know it's there... it is even mentioned in the release notes: https://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/108725
Wait, now I am questioning myself... "App Standby" - is that Doze Mode or not?
Because according to this I am not sure now...
acejavelin said:
The point is, we know it's there... it is even mentioned in the release notes: https://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/108725
Wait, now I am questioning myself... "App Standby" - is that Doze Mode or not?
Because according to this I am not sure now...
Click to expand...
Click to collapse
App Standby and Doze are indeed two different things. I suppose there is a reason why in the Moto G release notes Motorola mentions only App Standby, while in the Moto X release notes both Doze and App Standby are mentioned...
https://motorola-mobility-en-in.custhelp.com/app/answers/prod_answer_detail/a_id/108821
But people have been getting better battery timings when the phone is kept stable and without any movement whatsoever.
Sent from my MotoG3 using Tapatalk
theundead176 said:
But people have been getting better battery timings when the phone is kept stable and without any movement whatsoever.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
The old addage... Correlation does not imply causation. Just because that is the case does mean the reason for it is Doze mode, there are other optimizations in Marshmallow besides Doze Mode, like App Standby, and perhaps just optimized code that could account for the difference, which for most users is not hugely significant which it should be with Doze mode.
Techguy18 said:
Can anyone confirm whether the G3 supports Doze?
It isn't mentioned in the Android M changelog for the G3, but is present in the Moto X Style changelog.
Moreover, Doze requires a 'significant motion detector' sensor to work, and sensor apps report it missing on the Moto G. Could it be because of the Sensor Hub/ lack of gyroscope?
To check whether Doze actually works: https://www.reddit.com/r/nexus5x/comments/3y8144/guide_finding_battery_issues_with_googles_battery/
tldr: take a bug report, extract the txt from the zip and upload it to Battery Historian 2.0
I looked at the output of my phone, there was no Doze bar, which means Doze did not even activate. Installed the new Greenify and forced aggressive Doze, which seemed to trigger Doze.
I'm not adding this to the general/battery thread as this is a separate issue.
Click to expand...
Click to collapse
install greenify and go to aggressive doze. dont enable it, just enable the notifications. leave your phone for 3 hours, and then check. you'll see greenify saying your phone was in doze from time to time. which means you have doze.
i've been reading this everywhere that our g3 doesnt have doze. weird how a rumor spreads so bad. doze is a core OS function and motorola cannot seem to do anything to disable it.
Related
I have a XT1031 running on Boost Mobile. I'm currently running official SlimKat build 9 but switch back to stock when I am expecting alot of calls since I can't find a voicemail app that works with Boost Mobile on custom ROMs. I've searched for months for a fix that works to correct the faulty proximity sensor but haven't had any luck. Does anyone know of a way to completely disable the proximity sensor?
BaumerGXP said:
I have a XT1031 running on Boost Mobile. I'm currently running official SlimKat build 9 but switch back to stock when I am expecting alot of calls since I can't find a voicemail app that works with Boost Mobile on custom ROMs. I've searched for months for a fix that works to correct the faulty proximity sensor but haven't had any luck. Does anyone know of a way to completely disable the proximity sensor?
Click to expand...
Click to collapse
I guess it is not possible to disable it... If you want to fix the proximity sensor you must flash your phone with an stock room...
The proximity sensor has been bad since I received the phone. It was a gift and out of warranty. My issue is there no matter if the phone is stock or running a custom ROM. I was hoping a dev would have some insight to disabling it with a prop/hex editor or something.
Caution DO NOT DO THIS unless you want your proximity sensor completely disabled!!!
Also you're doing this on your own risk!
So if your proximity sensor is not working at all, you can disable it completely by chopping it off the board. The light sensor is separate, so this won't affect your auto-brightness.
Open your phone (14 torx screws), pop out the back panel.Barware not to lose your Power and Volume keys.
You don't need to detach the battery, just go ahead and lift the board carefully ( there are videos on YouTube how to do that ).
Flip the board to your right hand side, be careful, the display flex is still attached, you don't want to break that.
You can now find both sensors on the top right corner of the board, the proximity sensor is the LEFT one when you face the board straight up.
Use a small flat screwdriver and with a semi-gentle push in its base you can chop it off.
You're done!
Reassemble carefully.
Thanks for the suggestion I'll try to find some of those YouTube vids you mentioned. But from what I've been reading is that the sensor is just an ambient light sensor that can detect proximity when coupled with an IR-LED so I'm not understanding how I can just chop off the prox sensor. I can't post the link but the article is on Andrux & me blog titled CT406: proximity and light sensor on MotoG
Sent from my Moto G
BaumerGXP said:
Thanks for the suggestion I'll try to find some of those YouTube vids you mentioned. But from what I've been reading is that the sensor is just an ambient light sensor that can detect proximity when coupled with an IR-LED so I'm not understanding how I can just chop off the prox sensor. I can't post the link but the article is on Andrux & me blog titled CT406: proximity and light sensor on MotoG
Sent from my Moto G
Click to expand...
Click to collapse
Proximity and light sensors are separate, so chopping off the proximity one won't affect anything, besides proximity not working and the circuit will report "open", which means no object near, hence your screen won't turn off.
There are many types of sensors and they might differ in the way they work.I seriously don't see what y you've said is related at all.
For anyone interested, I found a module for Xposed Framework called Disable Proximity Sensor and it works flawlessly
Sent from my XT1031
Hey guys, I'm a new user of SG6. I just sold my LG G2, and now I'm missing the function that keeps the screen off if the proximity sensor detects something. My battery is draining too fast and I suspect that in part is because of many accidental wakes.
Is there any configuration that makes such thing? Or any app with or without root to do it?
I'm also looking for an answer to this.
On my previous devices, I could use a feature of GravityBox to accomplish this, but it doesn't work on the S6. Maybe someone with Xposed experience can port the feature to a Samsung compatible version?
Hi, I made this app as a fork of the Xposed Enable Ambient Display app, because it would not work on my phone (which already has ambient display enabled, but not the handwave / proximity gesture)
The app when installed, and the service activated, will bring up the black screen that is used to peek at notifications (https://raw.githubusercontent.com/D...isplay/master/screenshots/ambient-display.png) when you wave at the proximity sensor, or take it out from your pocket.
Download link https://github.com/Rijul-Ahuja/Doze-On-Proximity/releases/download/V1.0/app-release.apk
Cheers!
There's no way of enabling this for samsung phones?
Sent from my SM-E700H using Tapatalk
Very interesting. Only one question: and about the battery? Consumption is high?
Chaninoza said:
There's no way of enabling this for samsung phones?
Sent from my SM-E700H using Tapatalk
Click to expand...
Click to collapse
Well, for starters, your kernel has to support it, I believe. I am not very sure - I don't delve into the realm of hardware.
On my device, it was enabled after this commit was merged : http://review.cyanogenmod.org/#/c/119408/
On some devices, this module might work http://repo.xposed.info/module/com.dvd.android.xposed.enableambientdisplay - it did not work on mine, but worked on my roommate's device - this module would actually disable ambient display on my phone for some reason, so I have made a standalone app from the service in it.
kryzeK said:
Very interesting. Only one question: and about the battery? Consumption is high?
Click to expand...
Click to collapse
In all, likelihood, yes. It will be high.
Wish this worked on nexus 5x. You ever think about making it a XPOSED module? I think lots of people would find it useful.
Rijul.A said:
Hi, I made this app as a fork of the Xposed Enable Ambient Display app, because it would not work on my phone (which already has ambient display enabled, but not the handwave / proximity gesture)
The app when installed, and the service activated, will bring up the black screen that is used to peek at notifications (https://raw.githubusercontent.com/D...isplay/master/screenshots/ambient-display.png) when you wave at the proximity sensor, or take it out from your pocket.
Download link https://github.com/Rijul-Ahuja/Doze-On-Proximity/releases/download/V1.0/app-release.apk
Cheers!
Click to expand...
Click to collapse
Your app is a life saver for people who need it, especially now that xposed is not available for nougat. Just awesome.:good::good::good:
Thread closed at OP's request!
The Flash
Forum Moderator
Because I googled around and I am not sure, some say it's built into the core of the OS, and others say it does need a gyroscope.
Any idea?
Well if I have Greenify set to keep logs and nothing else it reports that is been in doze.
I ran Doze Checker a few weeks back (got it from XDA) and according to the app the G3 lacks the sensors to properly support Doze.
JohannesKauffmann said:
I ran Doze Checker a few weeks back (got it from XDA) and according to the app the G3 lacks the sensors to properly support Doze.
Click to expand...
Click to collapse
Huh.... I have a Moto X play and when I turn on aggressive doze It Greenify it DOES work according to the notifications, Gsam reports Doze as well, thing is, it also doesn't have a gyro scope.
Moto G3 does support aggressive doze mode. No special sensors required for this.
Only the movement based doze mode (doze checker only checks for this one) is not supported due to lack of a gyroscope.
https://play.google.com/store/apps/details?id=com.franco.doze&hl=en This does a pretty decent job whether native Doze is fully supported or not.
I have CM13 on my Moto X Style (2015) and the ambient display uses ONLY the proximity sensors and not the excellent IR sensors. Tried to search for apps which can activate them but failed.
It would be great if the Ambient Display feature used the IR sensors.
CM13 is better in every way except this little setback.
Experts, I need your help!
Moto X Brick said:
I have CM13 on my Moto X Style (2015) and the ambient display uses ONLY the proximity sensors and not the excellent IR sensors. Tried to search for apps which can activate them but failed.
It would be great if the Ambient Display feature used the IR sensors.
CM13 is better in every way except this little setback.
Experts, I need your help!
Click to expand...
Click to collapse
I recommend telling the developer(s) of that ROM about this issue, since here, all we have as in information is your device, your issue, and your ROM. Please post your issue in your respective ROM thread.
I'm on stock, but had similar issues after I disabled some apps. The fix was to ensure that all of Moto, Moto Actions and Moto Display are enabled.