Anyone know how to achieve this? Gravity box used to allow this. I'm have xposed/magisk installed so I'm open to anything.
The notification sounds are too loud but the ring sound is too quiet.
If it was like past versions of Android (8?) and phones, Google made a change to link them as one level. The App that I found that allows for seperate volume and notification control is 'Volume Butler'. It's simple and works well. There may be other Apps that can do this, but, at the time I needed it, it was the only one.
tonyo123 said:
If it was like past versions of Android and Phones, Google made a chnage to link them. The App tyat I use that allows for seperate volume control is 'Volume Butler'. It's simple and works well. There may he other Apps that can do this but at the time I needed it, it was the only one.
Click to expand...
Click to collapse
Yeah I searched all over the forums and those seems to be only apps that might work. Not sure how power hungry those apps are constantly monitoring app activity.
I was hoping something smaller that works on magisk or xposed.
Agenesis said:
Anyone know how to achieve this? Gravity box used to allow this. I'm have xposed/magisk installed so I'm open to anything.
The notification sounds are too loud but the ring sound is too quiet.
Click to expand...
Click to collapse
This is the app I use to do that. Works great. No extra battery drain with it either.
Related
I know xposed framework would allow this option but I don't believe it is supported for this device yet. Is there anybody else who has figured a way to separate these two volumes? I need the phone to be able to ring at night as I'm on call but not be woken by email and other notifications.
Thanks for any help.
seperate notification/ring volume
wterryiv said:
I know xposed framework would allow this option but I don't believe it is supported for this device yet. Is there anybody else who has figured a way to separate these two volumes? I need the phone to be able to ring at night as I'm on call but not be woken by email and other notifications.
Thanks for any help.
Click to expand...
Click to collapse
Looks like volume butler will work for now until xposed comes out.
wterryiv said:
I know xposed framework would allow this option but I don't believe it is supported for this device yet. Is there anybody else who has figured a way to separate these two volumes? I need the phone to be able to ring at night as I'm on call but not be woken by email and other notifications.
Thanks for any help.
Click to expand...
Click to collapse
This is a must have feature for me. CyanogenMod has this feature, but is not stable just yet.
Sent from my Nexus 5 using Tapatalk
wterryiv said:
I know xposed framework would allow this option but I don't believe it is supported for this device yet. Is there anybody else who has figured a way to separate these two volumes?
Click to expand...
Click to collapse
Try Volume Butler. Lots of settings, works really well.
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3
take a screenshot of your classic looking dialer and post it here.
simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.
So, i received my OnePlus 6 about 2 days ago and so far i´m loving it!
One thing i miss from my old Lg G4 (and maybe all other Androids) is having a dedicated slider in the volume control for notification levels.
Anyone else agree with this?
It's also common to have a check box to make it follow ringtone volume so that leaves the option to disable it when wanted.
I use Ringer & Notification Volume Unlink Module in xposed. You'll need root to use the xposed framework.
And another one i just noticed,
When casting from a nearby device to Mibox i get the usual notification saying a device is casting but i cannot control it's volume.
That too should be included in the expandable volume controls (it is on other versions of android)
ohhsaft said:
I use Ringer & Notification Volume Unlink Module in xposed. You'll need root to use the xposed framework.
Click to expand...
Click to collapse
Thank you but so far i don't see any reason to root this phone, i heard the Oxygen team are quite attentive with incorporating user feedback into their updates, and as i'm asking for something which is common and already exists on other versions of Android i think it should be included.
So far that's the first reason to root and it's not yet enough for me to start tinkering with it.
I get so tired of not being able to hear my Assistant when I trigger it with the screen off and would really like a way to make sure that my adjustments to volume don't impact Assistant. I seem to remember something like this existing in the HTC days where volume could be controlled on a per-app basis but I haven't heard of anything recently. Is there such a tweak? You would think with how hard Google pushes their Assistant that they would have done something about it themselves.
They should have had a volume mixer for Android a long time ago. Similar to windows
rester555 said:
They should have had a volume mixer for Android a long time ago. Similar to windows
Click to expand...
Click to collapse
Agreed. I swear I used to use custom ROMs with this on my HTC devices but I never needed such functionality. Now that I have a Pixel that actually works with the trigger phrase (my OnePlus 9 would just randomly stop working so I mapped long press power button to Assistant instead), I want to use it, but when I use my device, I turn the volume down lower than it would have to be for me to be able to hear my Assistant from a distance so I end up having to pick my phone up anyway :/
EtherealRemnant said:
Agreed. I swear I used to use custom ROMs with this on my HTC devices but I never needed such functionality. Now that I have a Pixel that actually works with the trigger phrase (my OnePlus 9 would just randomly stop working so I mapped long press power button to Assistant instead), I want to use it, but when I use my device, I turn the volume down lower than it would have to be for me to be able to hear my Assistant from a distance so I end up having to pick my phone up anyway :/
Click to expand...
Click to collapse
It used to be that you'd edit several lines in (I believe) build.props (or some props file) in a terminal app that would bypass the volume limit. That may still work, it's just been so long, I can't remember anymore but I might try searching old threads in old devices and see what I can find.
This might get you somewhere
Build.prop - sound quality improvement
Almost everyone who has ever put ROOT rights on Android has heard about such a file as build.prop and tweaks for it. In this article, we will look at all the lines of this file with which you can
devlister.com
Is there any way to set a specific apps volume?
I am literally going mad over the fact that Google assistant is linked to media volume. Since I always have media volume at 25% I can't hear what the assistant says...
I've tried Google with no avail, I can only find threads leading to a Samsung store locked app and to apps removed from play store.
I am rooted and I've looked at magisk modules but can't find anything there either.
Is it just impossible on pixel devices to adjust assistant volume seperate from media volume?
Macrodroid/Tasker would work.
Would be something like:
If "google assistant" in foreground set volume to "x%".
xtcislove said:
Macrodroid/Tasker would work.
Would be something like:
If "google assistant" in foreground set volume to "x%".
Click to expand...
Click to collapse
I tried looking at tasker but I can't find Google assistant as an app there.
And also, I couldn't understand how to get it to turn volume back to previous value afterwards when I was testing around on other apps.
BunnyPig said:
I tried looking at tasker but I can't find Google assistant as an app there.
And also, I couldn't understand how to get it to turn volume back to previous value afterwards when I was testing around on other apps.
Click to expand...
Click to collapse
idk about tasker but im sure you can do it with macrodroid.
You can pick the app or define the package name.
You can pick actual volume probably with macrodroid internal tools but 100% with command line (adb shell dumpsys audio) you can store the value in a custom variable and restore this value if assistant is not in foreground anymore.
I sure its doable with macrodroid
xtcislove said:
idk about tasker but im sure you can do it with macrodroid.
You can pick the app or define the package name.
You can pick actual volume probably with macrodroid internal tools but 100% with command line (adb shell dumpsys audio) you can store the value in a custom variable and restore this value if assistant is not in foreground anymore.
I sure its doable with macrodroid
Click to expand...
Click to collapse
I tried using macrodroid now but it doesn't do anything when I speak to assistant. I allowed accessibility option, root, disabled battery optimization etc but it won't do anything. Tried using screen content as well but same result unfortunately.
Is it anything wrong with the macro itself?
Edit: added another image to show some other triggers I've tried.
BunnyPig said:
I tried using macrodroid now but it doesn't do anything when I speak to assistant. I allowed accessibility option, root, disabled battery optimization etc but it won't do anything. Tried using screen content as well but same result unfortunately.
Is it anything wrong with the macro itself?
Edit: added another image to show some other triggers I've tried.
Click to expand...
Click to collapse
Its working for me.
If i say hey google media is set to 100%, if i exit it get set to 25%.
You only need a way now to capture the volume you used before. Thats pretty easy too. I can look tomorrow or later if you cant get it to work.
xtcislove said:
Its working for me.
If i say hey google media is set to 100%, if i exit it get set to 25%.
You only need a way now to capture the volume you used before. Thats pretty easy too. I can look tomorrow or later if you cant get it to work.
Click to expand...
Click to collapse
Tried your macro but still doesn't do anything. If I just try it on something else, say phone app it works flawlessly same as mine did, but not Google assistant. Have you installed the play store version (asking because I can install the store version but it's already installed with the stock os so I haven't)?
BunnyPig said:
I tried looking at tasker but I can't find Google assistant as an app there.
And also, I couldn't understand how to get it to turn volume back to previous value afterwards when I was testing around on other apps.
Click to expand...
Click to collapse
I tried to make this work in Tasker, and at least on QPR3 I couldnt get it to work....the app is Assistant so should be one of the first apps in the list.
BunnyPig said:
Tried your macro but still doesn't do anything. If I just try it on something else, say phone app it works flawlessly same as mine did, but not Google assistant. Have you installed the play store version (asking because I can install the store version but it's already installed with the stock os so I haven't)?
Click to expand...
Click to collapse
I made a full wipe today and installed latest A13 stable release from march 13.
You might like to tick the box to show system apps and try it with the 2 assistant apps (xenrollment and the other).
You might need to install Macrodroid Helper app....
xtcislove said:
I made a full wipe today and installed latest A13 stable release from march 13.
You might like to tick the box to show system apps and try it with the 2 assistant apps (xenrollment and the other).
You might need to install Macrodroid Helper app....
Click to expand...
Click to collapse
I have the assistant boxes checked (both of them) in the previous image I've posted.
I also tried installing the play store version of assistant to see if that made any difference but no, macrodroid does nothing when assistant opens.
I'll try macrodroid helper later to see if that makes any difference.
Update: it now just works, well, wonky but it works. I set a timer instead of the trigger fired and it works, but only when the phone is unlocked. If it's sleeping and I ask the assistant something it won't raise the volume, or rather the triggers won't work. Is this normal or have I missed a setting that prevents macrodroid from working while the phone is sleeping?
If you're rooted you could use this:
https://www.xda-developers.com/app-volume-control-individual-volume-levels-android/
It allows to individually set volumes per app.
I'm using it to be able to let Spotify run as background music while playing games.
wooki said:
If you're rooted you could use this:
https://www.xda-developers.com/app-volume-control-individual-volume-levels-android/
It allows to individually set volumes per app.
I'm using it to be able to let Spotify run as background music while playing games.
Click to expand...
Click to collapse
Doesn't work either, I tried it earlier and I tried iy again just to be sure, I manually add Google and Google assistant at 100% volume but it doesn't do anything. I made sure to disable macrodroid as well just in case it would interfere but it made no difference.
Also, that app won't recognize assistant in the audio stream, so I don't think it will be able to control the volume from assistant. That's what I gathered from reading the documentation as well.