Related
My accelerometer sensor has lost its cool. It basically goes in circles no matter what way the phone is turning. This becomes a problem because some apps use the sensor for orientation without having an option to turn it off. So my question is; is there any way to simply turn the sensor off, or disable its output? Just somehow make the OS not listen to it at all.
You can turn off screen rotation in the display settings, might help?
I've done that and it works for most things. But some apps disregard that setting and use the sensor for screen orientation anyway :-\ Thanks though.
There is a widget by Curvefish called autorotate onoff. You could try that, but it may not do any more than the manual disable did.
The MIUI rom has an option for auto rotation in its notification pulldown. I just turned it off and it keeps the portrait view through the OS and 3rd party apps. Might be worth a look.
Ooh thanks I'll try that!
I love the ambient display on the Nexus 6....so after unlocking, rooting, and installing double tap to wake, I am looking for a way to make this the default behavior for the lock screen - e.g. I'd like double tap to wake or the power button to simply enable the screen in ambient display mode rather than full color. Does anyone know a way to do this?
Thanks!
skylaneffz said:
I love the ambient display on the Nexus 6....so after unlocking, rooting, and installing double tap to wake, I am looking for a way to make this the default behavior for the lock screen - e.g. I'd like double tap to wake or the power button to simply enable the screen in ambient display mode rather than full color. Does anyone know a way to do this?
Thanks!
Click to expand...
Click to collapse
I haven't seen anything that does that. To be clear, you want the double tap and power button to act like ambient display's "shake to wake" where when you pick up the device (effectively a shake) it presents the ambient display screen?
Actually I'd like that too.
danarama said:
To be clear, you want the double tap and power button to act like ambient display's "shake to wake" where when you pick up the device (effectively a shake) it presents the ambient display screen?
Click to expand...
Click to collapse
Exactly!
Pocket mode, which is an option some custom ROMs have added to Ambient Display can kinda do this. What it does is it checks the proximity sensor, so when it is covered and then uncovered (like pulling it out of a pocket) the Ambient Display comes on. In actuality you can kinda wave your hand over the top part of the phone, without touching it.
cupfulloflol said:
Pocket mode, which is an option some custom ROMs have added to Ambient Display can kinda do this. What it does is it checks the proximity sensor, so when it is covered and then uncovered (like pulling it out of a pocket) the Ambient Display comes on. In actuality you can kinda wave your hand over the top part of the phone, without touching it.
Click to expand...
Click to collapse
Really? I thought pocket mode was to prevent the screen waking in your pocket
danarama said:
Really? I thought pocket mode was to prevent the screen waking in your pocket
Click to expand...
Click to collapse
1. pocket mode = proximity enabled after screen off, if detect NEAR state (covered by hand or somethings), doze will disable
until FAR state (uncovered), if FAR state is triggered, Doze will appears.
Click to expand...
Click to collapse
^ From Omni's Github which discusses the feature in more detail.
I've got gestures enabled in accessibility but when I have a notification and wave NY hand over sensor area it doesn't wake up or give me a view.
What could cause this?
I used the basic xml file with package disabler. Is there anything in there that could have caused it?
Jmgilliam16 said:
I've got gestures enabled in accessibility but when I have a notification and wave NY hand over sensor area it doesn't wake up or give me a view.
What could cause this?
I used the basic color file with package disabler. Is there anything in there that could have caused it?
Click to expand...
Click to collapse
hi,
firstly, the wake up gesture works fine for me. No issues, I have stock Rom (920C device) not rooted and no apps disabled. A few tips to remember. If correct setting is enabled in Accessibility /Dexterity and interaction /Gesture wake up . You don't wave your hand actually, its more of a "slow motion effect /action" over the device /sensor, than a fast wave etc.
Also check some combination in Settings if it is set correctly.... eg Notification reminder and LED indicator (re notification light flashing etc) clashes with each other.
And yes,
if you play around with apps like Package Disabler you must expect that disabling certain system apps can break other apps depending on the one you disabled ?
Good luck
Thanks. Will check all of that.
There is no "Gesture wake up" in my stock rooted N9208. Only direct Call, smart alert, silent and screenshot are available.
Elmar1801 said:
There is no "Gesture wake up" in my stock rooted N9208. Only direct Call, smart alert, silent and screenshot are available.
Click to expand...
Click to collapse
hi,
see screenshot attached, good luck
Elmar1801 said:
There is no "Gesture wake up" in my stock rooted N9208. Only direct Call, smart alert, silent and screenshot are available.
Click to expand...
Click to collapse
That's a different thing, gesture wake up is in Dexterity and Accessibility.
I've got mine "on".
You're right. Found it and it's working.
As most of you might know, OnePlus removed the proximity wake option from OOS lately, replacing it with the lift to wake feature. If you want to use the proximity wake feature, you either have to switch to a custom ROM or use an outdated version of OOS. Both options might be suited for most people, but in case you prefer to use latest OOS and still want to use proximity wake, I have some kind of workaround.
PLEASE NOTE: it seems that the given shell command does not work on Android Oreo (OOS Open Beta as of writing). Check the latest posts of this thread for any progress.
I came across this shell command, which will trigger the ambient display:
Code:
am broadcast -a com.android.systemui.doze.pulse com.android.systemui
A big shoutout to @Quinny899 for providing me the code to trigger ambient display by shell command.
You can use this command with Tasker to trigger it when the proximity sensor is covered for some seconds or even when you wave your hand over it. I haven't had the time to get such a profile working until now, but I know that it can be archived easily.
In case you use the above command, ensure you check the "use root" option in Tasker's context menu for the shell command!
EDIT: I managed to get this working :good: Below my implementation. I am sure there is room for optimization, but this is just a basic task and it works for me (OOS 4.5.13 with Tasker 5.0u6).
You need three profiles. Two of them will check the proximity sensor state while screen is off, the third one actually triggers the ambient display while screen is off and proximity sensor has been covered (by waving over it for example).
First of all, we need to ensure that Tasker will monitor the proximity sensor while screen is off. For this, open the three-dot menu, select Preferences and navigate to the Monitor tab. Set "Proximity Sensor" to "On". That's it.
Second, you have to enable the Ambient Display option via Settings -> Display, otherwise this won't work at all (thanks to @Devildire for confirmation)
Let's have a look at the needed profiles:
Code:
[B]PROFILE [I]Prox OFF[/I]
[/B]State -> Sensor -> Proximity Sensor -> invert
State -> Display -> Display State -> "Off"
[B]TASK [I]Proximity uncovered[/I]
[/B]Variable -> Set -> %Prox = false
[B]PROFILE [I]Prox ON[/I]
[/B]State -> Sensor -> Proximity Sensor
State -> Display -> Display State -> "Off"
[B]TASK [I]Proximity covered[/I]
[/B]Variable -> Set -> %Prox = true
[B]PROFILE [I]Wake Ambient Display[/I]
[/B]State -> Display -> Display State -> "Off"
State -> Variables -> Variable Value -> %Prox = true
[B]TASK [I]Wake Proximity Display[/I]
[/B]Task -> Wait -> 1s
Task -> IF -> %Prox = false
Code -> Run Shell -> am broadcast -a com.android.systemui.doze.pulse com.android.systemui (DON'T FORGET TO CHECK "USE ROOT")
That's it. Now turn off your screen and try to wake the ambient display by waving your hand over the proximity sensor.
EDIT: Tasker profiles can be found in post #7.
EDIT #2: @Arstoien provided us with an improved version of my basic tasks, check it out here.
Thanks for the guide on how to, great work from you for the community
OP updated with instructions. Feel free to comment and share your experience or any kind of optimization proposes. Please note that the implementation is only a rough imitation of the original proximity wake feature, most likely this implementation needs some polishing.
Hey there. Sounds intriguing... I'm not understanding the stacked profiles... It seems you've got it triggering with two conditions. How do you do that?
Or... Would it be possible to upload the profiles and tasks for importing?
@saccentekennedy
If you want to add another trigger to a profile, just long-press the first trigger condition and Tasker will prompt you with a popup window where you can select to add another trigger option.
If anyone else is interested, I might upload the profiles later.
Hi guys , any file so that we can import it on tasker (if it has such system) to get this. !!??!!
Please find attached the requested profiles.
EDIT: You might want to change the wait time within the wake ambient display task to 1s instead of 300ms, this one actually works way better.
Portgas D. Ace said:
Please find attached the requested profiles.
Click to expand...
Click to collapse
Works! Thanks for sharing this.
Is root required?
BloomerzUK said:
Is root required?
Click to expand...
Click to collapse
Yes look in the code last line
Mhm I have root, Tasker has a root-entry in magisk, added the profiles in post #7, changed the proximity sensor to yes, but it is not working.
Ok... So I've discovered that this breaks pocket mode... Every time I took my phone out to unlock with my finger, it had already registered several attempts my leg had made. I guess it makes sense this might be a problem.
dre-z said:
Mhm I have root, Tasker has a root-entry in magisk, added the profiles in post #7, changed the proximity sensor to yes, but it is not working.
Click to expand...
Click to collapse
As said before, this is just a rough workaround, it works for me (but not as perfect as the former in-built option). It works if you move your hand slowly over the sensor.
saccentekennedy said:
Ok... So I've discovered that this breaks pocket mode... Every time I took my phone out to unlock with my finger, it had already registered several attempts my leg had made. I guess it makes sense this might be a problem.
Click to expand...
Click to collapse
Hmm, I don't have this issue, but we might add another trigger option to the wake ambient profile: only trigger if display is face-up. This way it won't be triggered if the device is in your pocket.
After looking over what you steup in Tasker........The biggest question is "What does the phone do when it is in your pocket?" I think if you can figure out a solid Tasker-based solution to that question, this will be something worth using. Great work.
It works (more or less)
@dre-z:
try changing the wait time within the wake ambient display task to 1s instead of 300ms. Works better for me and might enable the whole thing on your device. 300ms to wait until your hand moved over the sensor completely seems to be a bit too short.
Portgas D. Ace said:
@dre-z:
try changing the wait time within the wake ambient display task to 1s instead of 300ms. Works better for me and might enable the whole thing on your device. 300ms to wait until your hand moved over the sensor completely seems to be a bit too short.
Click to expand...
Click to collapse
I think I am doing something wrong. Doesn't work at all. Thanks for your help anyways
Seems like the command is not working for me. The command triggers, but the screen doesn't wake up. Any ideas what's wrong?
Devildire said:
Seems like the command is not working for me. The command triggers, but the screen doesn't wake up. Any ideas what's wrong?
Click to expand...
Click to collapse
Did you check the "use root" option in the corresponding task?
I use the downloaded profles and yes, root is checked. Using OP5 up to date OOS.
Edit: maybe there is something wrong with shell execution. Can you give me information about what I have to enter using tasker's "send intent" action instead?
Hello to the community,
I have the following problem with my P10. When I am in an app and I touch the fingerprint scanner the phone goes to the launch screen (exit from the app). I think this happens after update b180. The fingerprint scanner works like the software circle button when I am in an app. How to deactivate that function?
Thank you!
I don't think you can turn it off. But I agree, it's annoying. Somebody thought it's super useful and they just had to put it there.
That happens after b180; in b151 didn't exist;
Nice. i actually want this behaviour. would prefer that i could use the fingerprint scanner "one button" option at the same time navigation bar is activated though.