High volume warning accept on Android N

[David]

I have a Samsung S7 Edge, and had a profile to auto accept the high volume prompt which was working perfectly until I upgraded to Android N.

The task was fairly simple - profile triggered every dialog, and would use Autoinput to click OK if %WIN ~ *high volume*

I finally figured out that when the screen is off the dialog pops OVER the lock screen, and %WIN is = Lock screen.

So it's not reading the dialog contents over lock screen. I tried using Autoinput UI query instead which seems to read the dialog (plus everything else, like notifications) but doesn't seem to fire when the lock screen is on.

Any pointers? This is driving me nuts.

[Rabangus]

There is a solution which turns the nag off entirely - have a look here:

https://www.xda-developers.com/how-to-automatically-disable-the-high-volume-warning-without-root/

You will need to buy AutoTools though...

[David]

Thanks. I tried that but guess it doesn't work for Samsung? I can set the variable but still get the warning regardless of what it's set to. Also, manually clicking the prompt doesn't change the variable value, so I guess Samsung uses something else... :(

[Rabangus]

Works fine for me on my Galaxy S7. Here's my settings:
https://1drv.ms/i/s!AhW1d3QyR3F7hL0-Yq7NCIV1j24KGA

You just need to add a couple of profiles to run that task - one each night, and the other on Tasker monitor start.

[David]

Yeah, that's the same as I have. Did you set it after 30 seconds? It prevents ever seeing it when connected to bluetooth?

I'm not sure what I could be doing wrong. I could be connected to adb, query the variable, turn up the volume and still got the prompt.

[Rabangus]

I set it after 30 seconds after boot, but there's no need to do that for the nightly profile. Also if you run the task manually it should still work.

Have you followed the first part of the guide to grant WRITE_SECURE_SETTINGS to Autotools? This should prevent the nag ever appearing - not just for bluetooth.

On 3 Oct 2017 01:27, "David" <tarheel...@gmail.com> wrote:

Yeah, that's the same as I have.  Did you set it after 30 seconds?  It prevents ever seeing it when connected to bluetooth?

I'm not sure what I could be doing wrong.  I could be connected to adb, query the variable, turn up the volume and still got the prompt.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/GQLfhDUQEpA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[David]

Yes. Would I see the value change if that went wrong somehow?

[Rabangus]

Hi David,

I'm really not sure what value you are expecting to change and where you would be expecting to see it change. I can only point you back to the guide on XDA - it does work.

On 4 Oct 2017 10:42, "David" <tarheel...@gmail.com> wrote:

Yes.  Would I see the value change if that went wrong somehow?

[David]

Here is what I mean. Steps:

1. Restart phone (so prompt gets reset)
2. Run Tasker task to set the audio_safe_volume_state to 2
3. Connect phone to PC via adb
4. Run command from PC: adb shell settings list global
Result (excluding other settings): audio_safe_volume_state=2
5. Connect phone to BT headset
6. Turn up volume
Result: Prompt still received!
7. Click OK on prompt
8. Run command from PC: adb shell settings list global
Result (excluding other settings): audio_safe_volume_state=2

I can repeat the same with 0, 1, or 3 and get the same result. No errors, I see the value change but still get the prompt. Also note that clicking OK on the prompt doesn't change it from where I set it.

[Rabangus]

Yeah, that sounds right. You don't need to keep connecting your phone to the PC to check the setting - you can use the Secure Settings plugin for that.

As you get no error messages I can only think that it's something to do with your settings. Have you definitely granted WRITE_SECURE_SETTINGS?

Have you checked the run log to see if it's throwing any errors when you run the task?

[David]

There are no errors in the log. And this is what I asked before...if it did not have the permission, why can I see it change it step 4? That seems unlikely to me.

Also, isn't it you in that thread in the comments of the xda article? If so, you mention this Secure Settings plugin...do you mean AutoTools? If so, how did you get it to show up under Device Administrators? I have a very limited amount of choices of apps there and no way to add others. I am still running the trial version of AutoTools but don't mind buying...if I was sure it was going to eliminate this warning, and I'm not. Or are you using a slightly different automation scheme than in the xda article?

In any case, I think I've found an acceptable workaround, in case others are struggling: I already had a profile for connecting to my car (the main thing I want the BT volume adjusted for). So I adjusted it to:
1. Use AutoInput to unlock the phone
2. Set the media volume to max
3. AutoInput click OK if %WIN ~ *high volume*
4. Set the media volume to max
5. Lock the phone
The unlocking gets around the %WIN not set issue, and this handles whether the prompt appears or not (in which case it skips step 3).

[Rabangus]

I'm using AutoTools Secure Settings, and I think the thing on XDA may have been a red herring, as that was the old Secure Settings and I'm not using that. I do have it installed though and set as a device administrator (it just showed up in the list), so if the two are linked it may be worth giving that a try.

I'm afraid I'm not a real expert on these things (I'm pretty new to Tasker) - it just works for me and I was trying to help. I'm glad you've found a workaround.

[David]

Sorry, no I appreciate it. Tasker is great, but can be frustrating at times, and that frustration probably shows above.