Related
If you are using the stock Android TV firmware and when you sideload some apps you see some strange visual effect like a distortion or black popup not accessible or the mouse icon doubled this is caused by the HW Overlay bug.
This not happen in any other Android device with hdmi output, is the first time that i see it.
Well, you could workaround this annoying bug disabling HW overlay in developer options.
Unfortunately in the stock firmware of the Nexus Player you don't have this field in developer options.
On the Nexus Player, to workaround the bug and select manually "Disable HW Overlay" / "Always use GPU for screen compositing" you can do in this way:
( you need root permissions )
Install Terminal Emulator, enable the virtual keyboard in the Nexus Player to write well in Terminal Emulator and type:
su
service call SurfaceFlinger 1008 i32 1
As suggested by KalenXI you can also disable at boot time the HW Overlay in this way:
" You can either use Tasker and the Secure Settings plugin to set it on boot. Or use Tasker's shell action to run "service call SurfaceFlinger 1008 i32 1" as root on boot. "
http://forum.xda-developers.com/showpost.php?p=57863961&postcount=62
For Intel developers:
The problem on cursor overlay appear when the mouse icon is present and before the system remove the icon, a multi touch gesture add sprites.
Mainly the switch between mouse icon and sprite fails.
You can test also with an hardware multi touch trackpad.
This problem is not present in any other device.
For the proplem on popup i not have idea.
For sure the HW Overlay needs corrections.
Thanks.
I was connected to my monitor through HDMI, unfortunately my monitor had an issue with its HDMI pixel ratio, and the monitor didn't have an over scan feature... I was tired of using my overscan app, so I connected the player to an HDMI to VGA adapter (with audio splitter), and sense I've started using the VGA adapter I have had no ghosting, of the mouse, ghost images, or otherwise, and no black block appears around the mouse icon/ see through icon (sprite glitch)
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?
[UPDATED]
Hello guys,
A little introduction:
I'm an XDA user for quite a while now, but never started an own thread. As I like playing with mods like Xposed, magisk or, in this case Tasker, I'd like to share my profile with those who find it handy too. Also I think there're way more advanced tasker guides and tricks and this is rather easy, but I'd love to share it anyways with you
What does this profile do?
It's pretty simple and basic. This profile lets you magically wake your phone with holding your hand (for example) close to the approximity sensor, but also (only on S8/S8+) trigger the Iris scanner, which would usually need to be tapped on, since Samsung doesn't allow 3rd-party apps to wake the phone! But we'll get this anyways But here's a video. You will see what I mean:
Click here for YT video (XDA embedding doesn't seem to work here)
Requirements:
Magisk (root) (*note: If you have rooted your phone with another method Secure Settings won't work, due to lack of development)
Secure Settings (*note: If you know another tasker plug-in, which can wake the device feel free to take that)
Tasker of course
Within Tasker you need to set proximity sensor (Under UI) to "yes". This ensures, that the sensor won't be killed from doze or anything else
And of course you need a working Secure Settings App. Make sure System+ module is active and granted root (Works very well with Magisk). Because it's enabled by default, it might be necessary to disable and re-enable it
If you meet all the requirements: Let's start
So step 1 : Create a new profile in Tasker with 3 status:
Sensor -> Proximity sensor
Display [Turned off]
Variable -> Variable value = %ONLYONCE to Undone (This is important, so the screen will be woken up only once after you turned off your device and not every time you put your hands to the sensor)
Name the executed task "Wake device" for example and let it run: (Go on in step 2)
Step 2: The executing task of the profile you just created should run this:
Task -> Wait = 350ms (adjustable to your needs)
Plug-In -> Secure Settings -> Configuration -> Wake device = Screen dim 15 seconds (adjustable)
Variable -> Set variable -> %ONLYONCE to Done
Code -> Run shell -> Command = "input tap 840 190" (No quotation marks) [Use root = yes] (*note: this creates a tap input, as if you were tapping on that specific spot, and triggers the Iris scanner. Also make sure that tasker has root privileges)
Step 3: Create a 2nd profile with the event Display -> Device unlocked
The executed task to this profile should be:
Task -> Wait = 3 seconds
Variable -> Set Variable -> %ONLYONCE to Undone
And that's about it Any time you wave your hand over the proximity sensor now or let's say pull it out of your pocket the screen goes on, the Iris scanner is triggered and your phone unlocks
Please hit the thanks button if you could find any benefit of this Guide and the profile and please feel free to leave some feedback You can also import the profile to your tasker. I attached it at the bottom
*Note: All iris scanner related tasks and profiles can be adjusted to devices without Iris scanners, but this profile isn't that handy on other devices apparently
3-25-22 update: Looks like the new code will be on line 33 for Android 12. It was on line 32 for Android 11. In addition to three_key_mode, you'd also want to add alert_slider_mode to your script (same identifiers as three key mode 1-3).
11-15-22 update: for Android 13 it will be on line 37
Hi, all.
Just got my 6T last week and loving it, except for the dang slider. I just have a bad feeling it's gonna fail one of these days, so decided to poke around and see if there is any soft solutions available. Oxygen slider module for Xposed doesn't appear to work. You can set up tasker to toggle the vibrate mode, which will take care of the sldier piece, but you won't see the vibrate icon in the upper right corner. There is also another app (silent mode toggle), which basically does the same thing as Tasker, but once again, no cigar on the icons. I was able to toggle the vibrate/silent/ring via the three_Key_mode command in global settings, but that didn't actually change the ringer mode. I've kept looking and looking until I've stumbled onto this post:
https://gist.github.com/tniessen/ea3d68e7d572ed7c607b81d715798800
I've then pulled up the pie build and found the interface declaration for the ringer mode (void setRingerModeInternal(int ringerMode, String caller) which is the 18th line (function index) here:
https://github.com/aosp-mirror/plat...e/media/java/android/media/IAudioService.aidl
What you will need:
1. Root, since we're modifying system parameters
2. Smanager or another script tool
3. Slider has to be in the ring mode for these to work properly (I'm sure somebody more proficient than me can figure out if the slider can be bypassed in other modes)
Create a new script and call it Vibrate (or something else you want to call that mode). Enable su (root privilege) on it. Inside type:
settings put global three_Key_mode 2
service call audio 18 i32 1 s16 text
############
(do not copy below ^ the above)
three_key_mode 2 - display vibrate icon
i32 1 - enable vibrate mode
s16 text - just random string caller
For Ring (or something else you want to call that mode). Enable su (root privilege) on it. Inside type:
settings put global three_Key_mode 3
service call audio 18 i32 2 s16 text
############
(do not copy below ^ the above)
three_key_mode 2 - display ring icon
i32 2 - enable ring mode
s16 text - just random string caller
For Silent(or something else you want to call that mode). Enable su (root privilege) on it. Inside type:
settings put global three_Key_mode 1
service call audio 18 i32 0 s16 text
############
(do not copy below ^ the above)
three_key_mode 1 - display silent icon
i32 0 - enable silent mode
s16 text - just random string caller
Now you can add these scripts as toggles onto your home screen. Hopefully, some people can find this useful.
I have no need for this, but it's always nice to see someone find a solution like this on their own. Nice find!
with the new Android 10 rollout, "service call audio 18" needs to be updated to "service call audio 30" for these to work.
Seriously, the greatest
RussianBear said:
with the new Android 10 rollout, "service call audio 18" needs to be updated to "service call audio 30" for these to work.
Click to expand...
Click to collapse
Boy, I've been looking for a way to do this for a while, and it's been sitting here the whole time! Thank you!
Hooray for automated control of ring mode!
dismembered3po said:
Boy, I've been looking for a way to do this for a while, and it's been sitting here the whole time! Thank you!
Hooray for automated control of ring mode!
Click to expand...
Click to collapse
Lol I was perplexed why nobody else had this done before (other than thru tasker, etc.).
RussianBear said:
Lol I was perplexed why nobody else had this done before (other than thru tasker, etc.).
Click to expand...
Click to collapse
So, if I didn't have a way to make my phone automatically do this stuff, I forget, and wind up waking the kids up in the middle of the night.
I've been using Automate for years for this purpose, but then I got my 6T. Aaaaaand....
RussianBear said:
Lol I was perplexed why nobody else had this done before (other than thru tasker, etc.).
Click to expand...
Click to collapse
You know, I was just about to post that this wasn't working. I'd been testing it for a while, and was frustrated.
Then, I realized that "auduo" is NOT how to spell "audio."
Would be awesome if someone could find a way to do this with the slider in any position. That way the slider can be repurposed for other functions and tasker.
Thank you for this.
I was missing the service call line from when i tried to work this out last year.
I've now got it working perfectly in tasker
PeteT said:
Thank you for this.
I was missing the service call line from when i tried to work this out last year.
I've now got it working perfectly in tasker
Click to expand...
Click to collapse
Good deal! When we get android 11 on 6t, the new code will be on line 32. I already have it working on 8T.
RussianBear said:
Good deal! When we get android 11 on 6t, the new code will be on line 32. I already have it working on 8T.
Click to expand...
Click to collapse
Thats good to know, thank you
I am using a 7 pro, so as and when this gets an update, i'll update my tasks
Hi RussianBear
I can't get this to work on Android 11. I am using a OnePlus 9 Pro. Does it still work for you?
If it does, would you mind sharing the full 'service call' line?
Thank you
See my 8T thread: https://forum.xda-developers.com/t/how-to-bypassing-slider-to-change-ringer-volume.4207221/
Thank you for your quick reply. I had everything correct apart from ticking 'use root'. Doh
PeteT said:
Thank you for your quick reply. I had everything correct apart from ticking 'use root'. Doh
Click to expand...
Click to collapse
Good deal! How you liking the 9, btw?
I really like it. I wasn't sure if it would be a good replacement over the 7 Pro but the 9 Pro feels well balanced in the hand, Performance is great and the wireless fast charge is incredible. For me it is a good upgrade.
I have installed a magisk module called butterlimits which feels like it extends battery life and improves the responsiveness of the phone.
Hello guys,
Firstly, congrats for this perfect workaround.
I was trying to do same thing with Tasker and my phone...
Only that my phone is Oneplus 7T... (noob here)
So now I have no vibration while someone calling, no matter where the position the slider is. I have also tried to enable the vibration from the Setting, but nothing happened.
Vibration for notifications (and every thing else) is working fine.
Do you have any idea how to bring back the call vibration?
Thanks in advance...
RussianBear said:
Good deal! When we get android 11 on 6t, the new code will be on line 32. I already have it working on 8T.
Click to expand...
Click to collapse
Looks like the new code will be on line 33 for Android 12.
in addition to three_key_mode, you'd also want to add alert_slider_mode to your script (same identifiers as three key mode 1-3).
11-15-22 update: for Android 13 it will be on line 37
Can somebody help me with a task to turn off aod when face down or in pocket on a samsung s21 FE?
Thanks!
Not bullet proof but you can give it a try...........
creat a new task > custom setting > system > aod_mode > value 0
create a new profile > find sensor or gesture > find face down
add the above task to the profile.
** you can reverse aod on I believe is using value 1
eeeemc said:
Not bullet proof but you can give it a try...........
creat a new task > custom setting > system > aod_mode > value 0
create a new profile > find sensor or gesture > find face down
add the above task to the profile.
** you can reverse aod on I believe is using value 1
Click to expand...
Click to collapse
Sadly it doesn't work.
But thanks
last resort ............
same as previous nmethod but change aod_mode to:
aod_tap_to_show_mode
use value 0
Actually I'm on Samsung A71 and using such methods
Mrawy said:
Sadly it doesn't work.
But thanks
Click to expand...
Click to collapse
eeeemc said:
last resort ............
same as previous nmethod but change aod_mode to:
aod_tap_to_show_mode
use value 0
Actually I'm on Samsung A71 and using such methods
Click to expand...
Click to collapse
It doen't work, maybe I need to give tasker some permissions trough adb?
Mrawy said:
It doen't work, maybe I need to give tasker some permissions trough adb?
Click to expand...
Click to collapse
I'm not sure if extra permission is required as not in my case.
May be try below experimental task if it works so that it proofs tasker custom settings is available on your device :
custom settings > system > blue_light_filter > value 1
This turn on Samsung's reading mode and if you manually hit play button from within tasker after you create this blue light test task , then you check from the dropdown tilt to see if the blue light icon is on or not.
if it is on , means custom setting is availble on your device without extra permission.
if this is the case , use custom setting to use the 'FIND' button step-by-step go to AOD on/off menu and set it. ( hope you know custom setting has 'FIND' function to manually choose the require action in your case is to find the AOD )
On Huawei P30 Pro, to disable AOD make task like a photos in attachment.
To use this task You Need use ADB DEBUGGING and Tasker Permissions app or adb command. Read more:
https://tasker.joaoapps.com/userguide/en/help/ah_secure_setting_grant.html
I toggle my AOD on my Samsung device. It's just as the first reply said.
custom setting > system > aod_mode > value 0 to turn it off, and 1 to turn it on.
To test the adb setting on your device, just create a simple task that toggles AOD. EG when you are connected to wifi, set it off, or somethign else you can use to easily test.
If that works (which it should), then it's the sensor part that has the issue.