disabling the internal screen-wake involved disabling the system app "moto display"
but as you might imagine, the internal screen-wake isnt really much of an issue for a foldable phone, and this doesnt disable the movement screen-wake on the external screen
i'd like for the external screen to stop turning on everytime i walk by or move, and for it to only turn on when i click the power button
is there a way? do i need root?
Turn off peak display in the display settings.
aha!
peek wasnt in my display settings at all with moto display disabled, (not sure why outside display peek functioned without it) but by re-enabling it and toggling peek off via settings > display, both screens have peek off
tested disabling moto display afterwards and it keeps this non-peek for both screens, but disabling moto display app is no longer needed regardless. still not sure why disabling the app without first detoggling only deactivated peek for the 1 screen but doesnt matter anymore ty
Related
I have the Verizon LG G4 vs986 running 5.1 (10b) but I've been unable to get Gravity Screen - On/Off 2.3.1 to work as it's not turning the screen off. Does anyone have this working on the G4 and can you share your settings? Thanks!
Almighty1 said:
I have the Verizon LG G4 vs986 running 5.1 (10b) but I've been unable to get Gravity Screen - On/Off 2.3.1 to work as it's not turning the screen off. Does anyone have this working on the G4 and can you share your settings? Thanks!
Click to expand...
Click to collapse
Been using it since the beginning (and G3 as well). After removing Power Nap Alpha 0.7 working flawless. Have you enabled Administrative Permissions?
Yes, enabled that. Can you let me know how you have the settings for the program setup? I was able to get the screen to go off once when I first installed it but never could get the screen to turn on and I have the PIN enabled lock screen.
Almighty1 said:
Yes, enabled that. Can you let me know how you have the settings for the program setup? I was able to get the screen to go off once when I first installed it but never could get the screen to turn on and I have the PIN enabled lock screen.
Click to expand...
Click to collapse
On
Any Direction = Check
Lying Face up= Check
Turn off by proximity = Check
Turn on by proximity = Check
Keep screen on by Motion = Check (sensitivity 70)
Booster = Check
Running During Call = Check
Notification = Check
Low Priority = Check
Start at boot = Check
I have the unlocked version so I also have some apps whitlisted
Device Administrator = Check (for both delayed lock and regular screen off permission, 2 separate)
All the rest I have UNCHECKED
Thanks! Think you covered everything except what do you have for the following settings:
Pocket Sensor Angle
Landscape mode
Table Sensor Angle
Turn Screen ON by Motion-Timeout
Turn Screen ON by Motion-Sensitivity
False Turn-On Protection in Pocket
It seems my screen is turning off because of the 15 second display timeout in the phone settings and not because of Gravity, what do you have for the phone's display timeout settings? I changed it to always keep display on and the screen does go off, but doesn't turn on until I tap the screen.
Is the screen supposed to turn on by itself or does one have to tap the screen?
Almighty1 said:
Thanks! Think you covered everything except what do you have for the following settings:
Pocket Sensor Angle
Landscape mode
Table Sensor Angle
Turn Screen ON by Motion-Timeout
Turn Screen ON by Motion-Sensitivity
False Turn-On Protection in Pocket
It seems my screen is turning off because of the 15 second display timeout in the phone settings and not because of Gravity, what do you have for the phone's display timeout settings? I changed it to always keep display on and the screen does go off, but doesn't turn on until I tap the screen.
Is the screen supposed to turn on by itself or does one have to tap the screen?
Click to expand...
Click to collapse
Pocket sensor = 60 (default I think, it becomes inactive with Any direction checked)
Landscape mode = Unchecked
Table sensor angle = 2
Turn on by motion = Unchecked
Keep On by motion sensitivity = 70
I don't have a false turn on protection in pocket option
Screen timeout = 15 seconds
On my device T Mo G4 H811 no tapping of screen required, all screen on and off functions are performed by Gravity (every now and then it doesn't read the proximity sensor, but 99% of the time it functions as it should).
The default setting should have gotten you working, all these setting are more of a fine tuning to your liking rather than actual functionality of the app itself. Have you tried uninstalling, reboot and reinstalling? Proximity sensor working? Not sure what else you can do other than contact the developer. I had and issue a couple versions ago and it was addressed fairly quickly with an update (I'm sure I wasn't the only one in that case).
Hope this helps you out.
I think once you select Any Direction (Flip Cover), the angles for both Pocket Sensor and Table Sensor becomes inactive, Turn Screen OFF by Proximity becomes inactive as well. I actually figured out the problem as it was the app that was turning the screen off but I am running Power Nap as well which puts the phone in deep sleep mode so I had to add GS to the exclude list in Power Nap before GS worked correctly and turned the screen back on. I already tried uninstalling from the app, rebooting and installing earlier but the problem was Power Nap. I have the unlocked version and it does have the false turn on protection option which is the last option under the Turn Screen ON by Motion section.
Almighty1 said:
I think once you select Any Direction (Flip Cover), the angles for both Pocket Sensor and Table Sensor becomes inactive, Turn Screen OFF by Proximity becomes inactive as well. I actually figured out the problem as it was the app that was turning the screen off but I am running Power Nap as well which puts the phone in deep sleep mode so I had to add GS to the exclude list in Power Nap before GS worked correctly and turned the screen back on. I already tried uninstalling from the app, rebooting and installing earlier but the problem was Power Nap. I have the unlocked version and it does have the false turn on protection option which is the last option under the Turn Screen ON by Motion section.
Click to expand...
Click to collapse
Yeah... Power Nap. Loved it on the G3 but on this phone it still has some issues. I stopped using it because even though I whitelisted certain apps some of those whitelisted apps actually weren't being allowed to remain active. Gravity wasn't one of them but Root call blocker was and boy was that a treat at times.
Glad you got it worked out.
zoman7663 said:
Yeah... Power Nap. Loved it on the G3 but on this phone it still has some issues. I stopped using it because even though I whitelisted certain apps some of those whitelisted apps actually weren't being allowed to remain active. Gravity wasn't one of them but Root call blocker was and boy was that a treat at times.
Glad you got it worked out.
Click to expand...
Click to collapse
Interesting, how do you check if the app is active or not since the screen is off?
Almighty1 said:
Interesting, how do you check if the app is active or not since the screen is off?
Click to expand...
Click to collapse
Trial and error... Root Call Blocker worked fine (whitelisted) when the screen was on but failed to work when screen off. What turns off my apps when screen off? Power Nap. Disable Power Nap and Root Call Blocker worked fine (screen on and off). So my conclusion was Power Nap even though whitelisted Root Call Blocker was failing to leave that app active.
zoman7663 said:
Trial and error... Root Call Blocker worked fine (whitelisted) when the screen was on but failed to work when screen off. What turns off my apps when screen off? Power Nap. Disable Power Nap and Root Call Blocker worked fine (screen on and off). So my conclusion was Power Nap even though whitelisted Root Call Blocker was failing to leave that app active.
Click to expand...
Click to collapse
Interesting, in my case, Powernap didn't put any app to sleep as before yesterday, my battery would last 2-2.5 hours with the screen off then I started greenifying everything except those I know that needs to run in the background and now the battery lasts 9 hours with Gravity Screen. I left White Pages ID without greenifying it.
I don't know if it is a bug but if I disable the moto display, the screen will not turn on when a notification comes in. Is there a way to enable the default Ambient Display?
jluna1 said:
I don't know if it is a bug but if I disable the moto display, the screen will not turn on when a notification comes in. Is there a way to enable the default Ambient Display?
Click to expand...
Click to collapse
Seems I overlooked this post, I was wondering the same thing!
Was anyone ever able to get stock ambient display (not Moto Active Display) working?
I ave tried all configs and disable all moto app with no success, when i disable the moto display app the ambient display setting appears but the phone doesn't wake when a notification comes in... ¿Maybe it needs a root thing, xposed or something else?
I was also hoping for a solution to this, I would love to use ambient display.
Has anyone has an issue where the screen won't turn on after using the fingerprint sensor? I can feel it unlock but I sometimes have to hold the power button until the power off/reboot menu comes up which then starts the display up from being all black. Have Magisk beta and Xposed installed so maybe that's the issue?
Not So Pro said:
Has anyone has an issue where the screen won't turn on after using the fingerprint sensor? I can feel it unlock but I sometimes have to hold the power button until the power off/reboot menu comes up which then starts the display up from being all black. Have Magisk beta and Xposed installed so maybe that's the issue?
Click to expand...
Click to collapse
Is AOD on or off? What happens when it's on?
Badger50 said:
Is AOD on or off? What happens when it's on?
Click to expand...
Click to collapse
AOD is on. So what happens is if the phone is on my desk and AOD is showing time, it'll show the notification briefly then just go black(nothing is covering proximity sensor and notification light is blinking). I then usually have to either do the power menu trick I mentioned or just restart the phone. If it's in my pocket on the other hand I'll pull it out and it'll be black with a notification light.
Oddly enough it usually only occurs with Snapchat so I think it may have to do with having snaptools installed?
Not So Pro said:
AOD is on. So what happens is if the phone is on my desk and AOD is showing time, it'll show the notification briefly then just go black(nothing is covering proximity sensor and notification light is blinking). I then usually have to either do the power menu trick I mentioned or just restart the phone. If it's in my pocket on the other hand I'll pull it out and it'll be black with a notification light.
Oddly enough it usually only occurs with Snapchat so I think it may have to do with having snaptools installed?
Click to expand...
Click to collapse
Quite possibly so. I know nothing about snap face, snap chat, or whatever these social media apps do. Although, you may try clearing the app data and cache on said app to see if it helps. No guarantees though. As is the case with many things android! ??
I've had the same issue ever since I installed, I believe, the nav bar immersive mod. Not sure, around same time. I was able to hurt power button twice for camera and that would pull it up and u could switch back to screen. I don't have xposed or Snapchat, so I don't think either of those are it. It's random when it happens to me.
I've had similar issues. I'm not rooted and have never used Snapchat or AOD. I do use immersive mode for some apps so I've thought that might be causing it. Like stated above, I can get the screen to come on my double tap to open the camera or just holding the phone face down and tap the back a couple times then flip back over and the screen comes on.
I'm also having this issue. Ambient display seems to prevent the issue for me. If I reboot the issue is gone for a period as well. Not rooted but have immersive mode acrive via nav bar hider.
shmity said:
I'm also having this issue. Ambient display seems to prevent the issue for me. If I reboot the issue is gone for a period as well. Not rooted but have immersive mode acrive via nav bar hider.
Click to expand...
Click to collapse
Ok so a little more testing. When Ambient display is set to always on, I have no issue, maybe a slight lag when waking/unlocking. When ambient is set to tap or pick up i get issues, when ambient display is set to off at all times, i have no issue. Plugging the phone in to charge seems to force the issue to happen.
Edit: Seems that even with ambient display off totally the issue pops up. Strange thing is if i unlock the phone and take a screen shot, its totally black.
I to have this happen and like sportytony I use camera to wake device. Sometimes that too takes a bit. Most of the time when it finally does wake there will be a notification that systemui isn't responding. So I wonder if it's related.
Ok, I've been having this issue happen multiple times a day. I use this immersive app: https://play.google.com/store/apps/details?id=in.tsdo.elw
Since I have turned all ambient display options off and made sure that System UI is unchecked in the immersive app i haven't had an issue at all.
Its definitely related to system UI, com.android.systemui to be precise
i used to try to set up Power Nap on this device, but it can't find System UI in app list, make me unable to whitelist it, thus causing same issue like yours,
Screen wont turn on after sleep, since System UI wake up is blocked
I was using hide navbars and had this issue
I uninstalled and never had that problem again
Sent from my Google Pixel 2 XL using XDA Labs
Didn't expect all these replies but I'm going to try to untick system UI and see what happens. Thank you all!
I installed LineageOS 17.1 on my Moto G6 "ali". Its working fantastically except there seems to be no way to turn off the 'idle' screen that shows the Time/Date, and the battery percentage at the bottom.
Lock Screen is set to none, Screen Saver is set to none, Moto -> Ambient Display is set to off. I've turn off everything I can find, but the screen is still there. I believe it is killing my battery because an LCD screen cannot turn on just a few pixels the way an OLED screen can and I think thats what this page was made for. Anyone know whats going on and how to turn it off?
Strange. What GApps have you installed? Can you try without for evaluation?
After a lot of trial and error and asking around, the problem has been found. Display -> Lock Screen -> Always show Time is the setting, but Display -> Lock Screen is not available when the Lock Screen is set to None in Security. I added a PIN lock, got to the menu to turn off Always show Time, then removed the PIN lock, and its fixed now!
Is anyone else experiencing their camera app no longer functioning? I can't open the app without it closing immediately. I'm on stock ROM and first started to experience this last night out of the blue while using cR Droid. I haven't done anything to cause this type of behavior, so I'm not sure if the latest version is just buggy. I've tried uninstalling updates and reinstalling but I still have the same problem.
RetroTech07 said:
Is anyone else experiencing their camera app no longer functioning? I can't open the app without it closing immediately. I'm on stock ROM and first started to experience this last night out of the blue while using cR Droid. I haven't done anything to cause this type of behavior, so I'm not sure if the latest version is just buggy. I've tried uninstalling updates and reinstalling but I still have the same problem.
Click to expand...
Click to collapse
it just closes? or shows a blank screen? (you checked camera access is enabled in QS).
Go to play store and hit uninstall on the camera (it'll revert the camera back to the default version the phone came with).
Also try the camera in another app (it doesn't use gcam but the camera api). Also try gcam in safe mode..
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
RetroTech07 said:
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
Click to expand...
Click to collapse
Tasker/Automate script to detect when you're connected to your car's particular Bluetooth (assuming it has that), and when so, turn sensors off, and when not connected to your car's Bluetooth, then turn sensors on.
RetroTech07 said:
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
Click to expand...
Click to collapse
there is an adb command to do this
Code:
adb shell settings put secure doze_quick_pickup_gesture 0