I'm really annoyed by the fact that I miss calls because the ringer volume was too low. But I have tried everything, and I mean everything, to try to correct that. You name the ringer volume locking app, I no doubt tried it. Tasker, etc. as well. None of them work at either locking the ringer volume at 100%, or raising it to 100% when a call comes in.
Since other people don't seem to have this problem.... I'm wonder, is it possible that the Manu kernel I install could be blocking something? Or what about the MIUI XJ ROM I got from here? Any other clues?!
When you're playing a music file without headphone, is the speaker giving loud sound then?
If yes, then your speaker is allright.
If no, plug in headphones and check the volume through your headphone. If the volume is also low there, then your amplifier is broken.
Cyanoid said:
I'm really annoyed by the fact that I miss calls because the ringer volume was too low. But I have tried everything, and I mean everything, to try to correct that. You name the ringer volume locking app, I no doubt tried it. Tasker, etc. as well. None of them work at either locking the ringer volume at 100%, or raising it to 100% when a call comes in.
Since other people don't seem to have this problem.... I'm wonder, is it possible that the Manu kernel I install could be blocking something? Or what about the MIUI XJ ROM I got from here? Any other clues?!
Click to expand...
Click to collapse
I use Volume Control app. But then again you said you tried every volume app there is.
Manu is not blocking anything as I've been with ManU kernel for a long while.
Try to change your ringtone. Some ringtones are louder than others.
Well, the problem has nothing to do with the choice of ringtone I'm using. If the volume is too low, I'm obviously not going to hear the phone, regardless of the volume of the ringtone.
TheRamon: I think you may have misunderstood the issue. It's not that the volume is low all the time. It's that it may have been turned down or off for various reasons, and I need the ringer vol to be 100% when a call comes in.
There are many apps that will do this, but absolutely none have worked properly on my Desire. So if we've ruled out the kernel, and others with Desires have managed to accomplish this through apps.... why am I not able to do the same?!
There is no particular indication anywhere that the phone is not working properly.
Have you ever flashed another rom to test?
via xda app
stankyou said:
Have you ever flashed another rom to test?
via xda app
Click to expand...
Click to collapse
No, I haven't. But that's because it's a big deal (for me, anyway) to do that. I have to go through hours and hours settings things back up similar to what I had. So I don't change ROMs too often. Truth be told, I never really had luck with any ringer volume lock app on the Desire, and that's 2 years looking. They all mess up in one way or another, making them unuseable. It's just that it seems to be even more the case since I installed MIUI XJ with the Manu kernel. But I don't know. There may be no connection. All I know is that other Desire users have no (or little) problems with the ringer lock apps and I do!
Cyanoid said:
No, I haven't. But that's because it's a big deal (for me, anyway) to do that. I have to go through hours and hours settings things back up similar to what I had. So I don't change ROMs too often. Truth be told, I never really had luck with any ringer volume lock app on the Desire, and that's 2 years looking. They all mess up in one way or another, making them unuseable. It's just that it seems to be even more the case since I installed MIUI XJ with the Manu kernel. But I don't know. There may be no connection. All I know is that other Desire users have no (or little) problems with the ringer lock apps and I do!
Click to expand...
Click to collapse
Im not really asking you to switch rom. What im saying is nandbackup your current rom and flash a different one. Check if the volume issues disappear or not. Since you are using an AOSP based rom, my suggestion is to flash a Sense based rom and see if the issue remains. At least you'll have an idea if its just a rom related issue or not and determine the next troubleshooting step from there. It will be difficult to find a solution if you don't try to isolate where the problem is coming from.
via xda app
Ok, I actually did switch ROMS.... I'm on the latest stock MIUI GB ROM for the Desire, after wiping everything, and all stock apps. I just downloaded and tried a couple of locking apps; Ring Lock, Smart Volume.... they don't work! Smart Volume buzzes when I change the volume, but it happily allows me to do so!
So now I'm wondering if its MIUI itself that is preventing volume locking. Yet I doubt it, because I think we'd have heard that from MIUI users. Each volume control app seems to have its own reason for not working. Some will lock volume settings with each other, but still allow you to change the ringer volume. Some will have dialog boxes go into an infinite loop if you try to change the ringer volume. Some will vibrate a notification when you change the ringer vol., but will still allow you to do so. Even in Tasker, I set a profile to change the brightness and the volume upon ring... it changes the brightness, but not the volume. Since each app has a different type of failure, one would logically conclude that it's the apps that are simply faulty.
But then there's the irrefutable fact that while some find these apps faulty (sometimes for the same reason I did), I'm guessing not everyone with a Desire has been unable to get the ringer volume to stay locked. So I still don't know if it's an inherent problem with the Desire. But if it's due to MIUI, I'll have to live with it. Because... I like MIUI a bit more than I hate the fact that I can't control the ringer volume!
Update: I just discovered this, so I've yet to confirm.... but I just tried an escalating ring app.... and it actually worked on my Desire. I left the phone on low, the app started low and took the volume to max. That means, the volume is/may be controllable on this device, by a 3rd party. Just before this, I started messing about in Superuser, looking at the tons of logs it creates. Turns out, by default, Superuser was not giving full permissions to my apps - specifically the right to make calls and related etc. I set all such.apps to full permissions.
I will try with a ring locker app tomorrow (but even the escalating ring app is actually perfect for my needs!)..
Related
I noticed this earlier today and it's driving me NUTS!! Various system sounds (so far I've found the dialing tone, lock/unlock click, and default keyboard sounds) all of a sudden are practically inaudible. I can hear them but only if I hold the speaker up to my ear while dialing, typing, etc. All volume levels are turned up all the way like I always have them, what gives?!? I'm very confused by this...
Possibly blown speakers? Have you tried music?
Swyped from my sexy EVO.
are you sure your system volume is up? You can check it with Audio Manager.
Uhh yeah like I said, all volume levels are ALL the way up.
Nope not blown as ringtones, etc. come through the speaker just fine.
You running stock? Try a reset/clean flash?
Yes everything is stock and I'm trying to avoid the obvious (resetting the phone)
Are all of these things y'all have suggested not obvious to the average user? I don't mean to be rude in the least but I always try several things to fix an issue before I seek out help...
igobyzach said:
Yes everything is stock and I'm trying to avoid the obvious (resetting the phone)
Are all of these things y'all have suggested not obvious to the average user? I don't mean to be rude in the least but I always try several things to fix an issue before I seek out help...
Click to expand...
Click to collapse
haha. you may be surprised sometimes Always got to cover all the bases.
I have no idea what's causing you issues, but I experience something sort of simlar, and have yet to figure it out. I don't use any audio feedback or lockscreen unlock sounds or anything like that. My ringer and notifications always work fine. The thing for me that is odd, is my boot animation sound. No matter what sound I use, it plays halfway through EXTREMELY loud, and then it suddenly cuts to about 1/3 the volume that it started playing at. It's random, and doesn't happen every time, but definitely enough for me to notice. I have no idea what causes it, but wouldn't be surprised if it's the same type of issue.
Download an app called audio manager. Your system volume got stuck down and won't go up without that type of app, since we cannot change it in settings.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
Rydah805 said:
Download an app called audio manager. Your system volume got stuck down and won't go up without that type of app, since we cannot change it in settings.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
Click to expand...
Click to collapse
+1 same thing happened to me and that was the only way i could fix it
AudioManager allows you to change the system sound settings, which is otherwise impossible via the standard Android interface. That solved my problem.
You can easily miss this one but it is very unpleasant if it catches you off-guard. Please read carefully. I posted this in the Desire and Desire S forums because those are the phones on which I discovered the bug. If anyone has anything against it please feel free to delete either thread.
I found a humongous BUG in a new Sense / GingerBread (I haven't tried FroYo, it may exist there also). I confirmed it on Desire with AceSMod007, SGBS and Cool3D Sense 3.0 and original stock ROM on HTC Desire S. Whatever the culprit is, whose ever fault it was, HTC or Google screwed up big time (something like famous -88dBm-wifi-stupidity)!!
Problem and how reproduce it:
1. Put your child to sleep (important!)
2. (…2 hours of hard work later ) Set the ringer volume to minimum so that you can hear it in a complete silence while your kid sleeps and you are working on your computer. Or you could be on a meeting… my point remains. Let's say that 30% is enough for the ringer volume.
3. Do whatever you want with the phone: play YouTube video (on very low volume, of course), enter your favorite navigation app, browse contacts, surf the web, change sound profiles with the official HTC widget… but please, for the love of god, DO NOT touch the Dialer App (the big phone button at the bottom of the screen)
4. As soon as you enter your Dialer App (weather you are about to make call or you are answering the incoming call or you just want to see call history) the strangest thing happens: our beloved phone decides that it would be appropriate to increase System sounds volume to maximum.
5. That is not the biggest problem. This one is IMPORTANT: After you initiate a call (using Dialer) ringer volume goes back to the value it had previously when you received your last call. Weird?! Steps to reproduce a problem:
a. set your ringer volume to X%, (X > 0)
b. receive a call (call yourself from your other phone and reject it), note that X% should now be "remembered"
c. set ringer volume manually to Y% (Y ≠ X, use some extreme values to tell the difference easily, say 10% and 90%)
d. enter Dialer app and call anyone (12345 will do),
e. hang up
f. check the ringer volume – it went back to X% (scary? )
g. in special case, if you initially set X to 0% the ringer volume will not revert to 0% but will stay Y% instead (hence the X > 0 restriction in the first step)
6. Ask yourself: Why the hell Dialer app changes my systems sounds or ringer volume and should I really (REALLY?!?!) check the ringer volume each time after using my phone just to be sure nothing will go wrong in a "silent environment"??? WTF?!?
Can you guys confirm this please? I checked system sounds volume using sound mixer in Notification Toggle app but I am sure there are other ways to check it. Ringer volume is present in the settings.
I am planning to contact HTC but knowing how useless is their support do you think a petition is the solution? Or should we send them a ton of mails?
Note: Once more, this is tested with Sense ≥ 2.1 and GingerBread ROMs (including Desire S stock). You can try it with FroYo if you like.
Best regards to all of you!! I enjoy being part of this community and during past few years it taught me a lot.
Thank you!
Nice catch, any reports on devices from other makers than HTC?
interesting..
Nasty!
For those that have the all powerful (although not free) tasker application, I wonder if we could use it in order to reset volume levels to ensure that you don't get bitten again!
Not got time right now to test....I wonder if bug still there on sense 3.0 and sense 3.5?
hmmm very interesting...
ben_pyett said:
Not got time right now to test....I wonder if bug still there on sense 3.0 and sense 3.5?
Click to expand...
Click to collapse
I am also planning to test it on Sensation (as soon as I get hold to it)
coolexe said:
hmmm very interesting...
Click to expand...
Click to collapse
I really hoped that devs like you will stumble upon this thread. Now we have a chance... or at least a hope.
I wonder how things are doing with AOSP GB ROMs? Anyone?
ben_pyett said:
Nasty!
For those that have the all powerful (although not free) tasker application, I wonder if we could use it in order to reset volume levels to ensure that you don't get bitten again!
Click to expand...
Click to collapse
Thanx for the suggestion! I am using Llama for a while and I totally forgot about Tasker. I played a bit with Tasker Trial version today and it can be "fixed" this way. Althougt Tasker must be paid for after 7 days and this is not actual solution... but it works If anyone needs Tasker guidance feel free to contact me.
This strange sound bug is present in the official ("developers") 2.3.3 Gingerbread update for the Desire, tested and confirmed!
I noticed this from the beginning, but didn't pay much attention to it because I thought it was my fault. But it happens again and again and I'm sure I don't do anything to cause this.
The problem: often when I haven't used the phone for a while the ringer volume is mysteriously turned down to a miminum level.
I now lock the ringer volume with an app, so this kinda solved the problem for me. Nevertheless I'm wondering if there are others who have this weird volume behavior.
BTW this is not the "classical" volume bug that was solved a few days ago with the OTA patch.
Can't say I ever have any problem like that. Might be an app on your phone that is turning the volume down? I agree it's definitely not the button bug since you can't change the volume with those buttons without unlocking the screen.
Sent from my Galaxy Nexus using XDA App
appelflap said:
I noticed this from the beginning, but didn't pay much attention to it because I thought it was my fault. But it happens again and again and I'm sure I don't do anything to cause this.
The problem: often when I haven't used the phone for a while the ringer volume is mysteriously turned down to a miminum level.
I now lock the ringer volume with an app, so this kinda solved the problem for me. Nevertheless I'm wondering if there are others who have this weird volume behavior.
BTW this is not the "classical" volume bug that was solved a few days ago with the OTA patch.
Click to expand...
Click to collapse
This might be an app. For example the 1Password reader app changes your volume based on some setting in the app.
yep. since day 1. no idea what causes and it's definitely no app causing it as i returned to factory settings to test it out and i still had the same issue
i honestly think it's the placement of the volume buttons but really difficult to be certain, as sometimes i will find the phone on vibrate and i am 100% i haven't touched the volume button.
At least now i am know i am not going crazy as this has been my one and only gripe about the phone
what app are you using to keep the volume locked?
Does you phone have the update? If not, then I'd assume it is the bug.
Why would I assume that. Cause the bug picks up noise on the volume keys, which control volume of everything, ringers, media, notifications, ect. The buttons control different things depending on what screen you might happen to be on. So it's possible that the bug could change your ringer volume as well.
coleburns said:
yep. since day 1. no idea what causes and it's definitely no app causing it as i returned to factory settings to test it out and i still had the same issue
i honestly think it's the placement of the volume buttons but really difficult to be certain, as sometimes i will find the phone on vibrate and i am 100% i haven't touched the volume button.
At least now i am know i am not going crazy as this has been my one and only gripe about the phone
what app are you using to keep the volume locked?
Click to expand...
Click to collapse
Ahhh thx, this was driving me bananas .. at least I now know that it can be mysteriously reproduced on other devices. I've tried to monitor my own actions but I'm also pretty sure I don't accidentally touch the volume keys. I didn't do extensive research because I just thought it wasn't worthwhile. But because I missed some calls lately because of this it is now pretty high on my annoyance list.
The app I'm using is Volume + (free version will do). Until now it seems to work well. It runs a background service and intercepts volume key presses events and pushes the volume back to a saved level. (Could have used that for the other volume bug)
mobilehavoc said:
This might be an app. For example the 1Password reader app changes your volume based on some setting in the app.
Click to expand...
Click to collapse
Always difficult to say, but I wiped my device a few days ago to root it and didn't install many apps yet (only twitter and thumb keyboard)
Luxferro said:
Does you phone have the update? If not, then I'd assume it is the bug.
Why would I assume that. Cause the bug picks up noise on the volume keys, which control volume of everything, ringers, media, notifications, ect. The buttons control different things depending on what screen you might happen to be on. So it's possible that the bug could change your ringer volume as well.
Click to expand...
Click to collapse
I've installed the latest update (build ITL41F). Maybe the fix doesn't cover all scenarios yet?
Sounds like interference to me. The fix added a 2ms de-bounce time which is ALOT. What frequency is your network on? You should try fixing it to 3g just to check if that fixes it. If it does its most likely interference.
I wonder if you have a bad ground connection in it somewhere (hardware fault).
If you can tell me the frequency your network uses (or your operator and i'll look it up) I can calculate the GSM burst time and see how it fits in 2ms. Ironically the burst arrives when you're about to receive a call so its turning the ringer down just before it rings lol
kam187 said:
Sounds like interference to me. The fix added a 2ms de-bounce time which is ALOT. What frequency is your network on? You should try fixing it to 3g just to check if that fixes it. If it does its most likely interference.
I wonder if you have a bad ground connection in it somewhere (hardware fault).
If you can tell me the frequency your network uses (or your operator and i'll look it up) I can calculate the GSM burst time and see how it fits in 2ms. Ironically the burst arrives when you're about to receive a call so its turning the ringer down just before it rings lol
Click to expand...
Click to collapse
My operator uses 900 MHz (for 2G) /1800 MHz (3g) . Operator is T-Mobile Netherlands
Btw I just accidentaly catched the bug doing it's nasty thing on 3g.
Anyone know where to report this?
Can't replicate this myself, however before submitting this as a bug maybe worth checking out the logcat trace around the time the volume is changing.
With the "SAV" issue, I seem to recall someone saw overrun errors in the log around the time of interference.
You may find something similar in the log or likewise there maybe some entries in there detailing a rogue process doing something a bit wacky which causes your issues.
Highland3r said:
Can't replicate this myself, however before submitting this as a bug maybe worth checking out the logcat trace around the time the volume is changing.
With the "SAV" issue, I seem to recall someone saw overrun errors in the log around the time of interference.
You may find something similar in the log or likewise there maybe some entries in there detailing a rogue process doing something a bit wacky which causes your issues.
Click to expand...
Click to collapse
SAV issue, overruns start on line 4
I'm also having this issue using: ICL35F.I9250XWKL2.
I can't find a way to reproduce it. If/when I find more info, I'll try to keep up to date.
From preliminary tests I've conducted, I now find Talk 4.0.2-235179 to be the culprit.
I have notification on and its tone is Silent. If I'm chatting with someone and that someone replies, the volume changes to 0???
I've written an app that polls the volume and notifies when it changes. Later today I might post the code.
Talk in Silent
Finally have a found the real reason. When Talk is set to:
Notification: System Bar;
Sound: Silent.
When a message comes and the chat is in foreground, the volume is changed to level 3.
The program I've made, once started, poles the sound level each 5 seconds and when it's different a notification appears.
To this post I've attached the .apk, its source and a silent ringtone to overcome this bug.
DoomFragger said:
Finally have a found the real reason. When Talk is set to:
Notification: System Bar;
Sound: Silent.
When a message comes and the chat is in foreground, the volume is changed to level 3.
The program I've made, once started, poles the sound level each 5 seconds and when it's different a notification appears.
To this post I've attached the .apk, its source and a silent ringtone to overcome this bug.
Click to expand...
Click to collapse
Thanks for your detective work. This is exactly what was causing my volume to seemingly change at random. It was especially annoying because some days I use gtalk quite a bit and other days not at all.
I linked to your post and this thread on the relevant Google Code Android bug report that someone had created back in December for the same issue. It can be found here if anyone cares to star the issue in hopes of giving this bug more exposure: http://code.google.com/p/android/issues/detail?id=22579
I can confirm the problem. It only happens with Talk in the foreground running and with the silent notification on.
Thank you very much, I got the new One X and was wondering if it was a software bug in HTC software....guess not
So my wife will be getting a call for a phone interview this Wednesday, and she's concerned about a recent issue with her AT&T S3 running on CM11 nightly 3/22. Her in-call volume is always extremely low regardless of how high the volume is set for calls. I have heard other accounts of this issue cropping up on various devices with builds of CM11 dating back to last year, but I've never come across a fix.
Has anyone encountered this and then resolved it permanently? My wife is very stressed worrying about not being able to hear the interviewer when they call in two days.
Try a different rom, tasks aokp has always been loud for me.
Making the iPhone jealous one user at a time.
ScOULaris said:
So my wife will be getting a call for a phone interview this Wednesday, and she's concerned about a recent issue with her AT&T S3 running on CM11 nightly 3/22. Her in-call volume is always extremely low regardless of how high the volume is set for calls. I have heard other accounts of this issue cropping up on various devices with builds of CM11 dating back to last year, but I've never come across a fix.
Has anyone encountered this and then resolved it permanently? My wife is very stressed worrying about not being able to hear the interviewer when they call in two days.
Click to expand...
Click to collapse
CM11 is available in stable. Why would you/she want to run the phone on a nightly? Guess you have enough time before Wednesday to update to either a stable version or go stock - even if only for the interview.
If you rely on your phone as a phone and actually need it up and running 100% all day everyday, you should be on the stock ROM. I'm sorry but all of these AOSP ROMs are full of bugs that get annoying after a while; one of them being the low call volume.
¿Will-it-Blend? said:
If you rely on your phone as a phone and actually need it up and running 100% all day everyday, you should be on the stock ROM. I'm sorry but all of these AOSP ROMs are full of bugs that get annoying after a while; one of them being the low call volume.
Click to expand...
Click to collapse
I lol'd at this. If you need to actually use your phone you shouldn't be on xda. Good stuff.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Djspinister said:
I lol'd at this. If you need to actually use your phone you shouldn't be on xda. Good stuff.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I lol'd even more at your useless post. I use stuff like V4A and Xposed (if you even know what that is) all the time from this site. You can be on XDA and still expect your phone to work. I was just pointing out that low call volume has always been an issue on a lot of AOSP ROMs, and if you need to use your phone to make a lot of phone calls, you should be on the STOCK ROM.
I'm on an aosp ROM, and I use my phone to make a lot of calls, so you're saying I need to be on stock ROM? Lol... What is "stuff like v4a and xposed"? Sounds complicated for us simple folks. :silly:
Bro, I've been on aosp ROMs since day one.. And never had any issue from phone.apk
BTW I'm not sure of cm still have this but in advance option setting and under sound, there's an option to gain extra volume for voice call.. Try it out and stop with the stock joke Lol
Sent from my SAMSUNG-SGH-I747 using Tapatalk
My S3 has been on CM since the day I got it, and CM11 since it came out, and on nightlies. Never had a single issue with call volume. As a matter of fact, I found that CM11 nightlies were overall a lot more stable than even the stock 4.3..
Since she's expecting important calls, you may get her sim card on your phone while you fix the phone for her.
Larry2999 said:
CM11 is available in stable. Why would you/she want to run the phone on a nightly? Guess you have enough time before Wednesday to update to either a stable version or go stock - even if only for the interview.
Click to expand...
Click to collapse
CM11 is only nightly on d2lte.
I would say if you use it for work and if you're wife doesn't know too much about AOSP, go back to stock.
I had this same exact problem on my Galaxy S3. All my volume settings are at highest, and even when i press the volume up rocker during the call, it doesn't get louder. HERE'S THE SOLUTION THO (after countless hours of trying many, many different things)! Not sure if this works for other phones.
During the call, if you press the volume button, you should see the volume level bar with the "settings" icon next to it appear on your screen (look at the screen while the call is in progress). Press the "settings" button to open up the volume menu. If you're having low volume, you probably have all the volumes at their max. Put your finger on the volume slider and just move it lower then back higher, and you should notice that the volume goes higher than it was before. It's almost like it's stuck at what it thinks is the MAX level, and by sliding it back and forth, it's "unstucking" it, and allowing it to go higher to the true max level. Not sure why it does this, but after doing this, it should remain at the new higher volume for the next calls. I did notice that if you adjust the volume lower for anything else (say when you're watching a video, or turning it down because the ringer or notification sound is too loud), then it will get back to the low call volume and you have to slide it again to get it unstuck.
If anyone knows how to report this issue to the CM 11 coders, please forward...
Hope that helps!
geesedude said:
I had this same exact problem on my Galaxy S3. All my volume settings are at highest, and even when i press the volume up rocker during the call, it doesn't get louder. HERE'S THE SOLUTION THO (after countless hours of trying many, many different things)! Not sure if this works for other phones.
During the call, if you press the volume button, you should see the volume level bar with the "settings" icon next to it appear on your screen (look at the screen while the call is in progress). Press the "settings" button to open up the volume menu. If you're having low volume, you probably have all the volumes at their max. Put your finger on the volume slider and just move it lower then back higher, and you should notice that the volume goes higher than it was before. It's almost like it's stuck at what it thinks is the MAX level, and by sliding it back and forth, it's "unstucking" it, and allowing it to go higher to the true max level. Not sure why it does this, but after doing this, it should remain at the new higher volume for the next calls. I did notice that if you adjust the volume lower for anything else (say when you're watching a video, or turning it down because the ringer or notification sound is too loud), then it will get back to the low call volume and you have to slide it again to get it unstuck.
If anyone knows how to report this issue to the CM 11 coders, please forward...
Hope that helps!
Click to expand...
Click to collapse
More simple than that, press volume down while in call then press volume up. That's all you need.
CM volume blaster Mod
polobunny said:
More simple than that, press volume down while in call then press volume up. That's all you need.
Click to expand...
Click to collapse
CHECK MY SIGNATURE
You are welcome
i created CM Volume Blaster for free
MrFhenix said:
CHECK MY SIGNATURE
You are welcome
i created CM Volume Blaster for free
Click to expand...
Click to collapse
Which is in no way related to the current issue of the volume being ridiculously low but then being fine after playing with it.
polobunny said:
More simple than that, press volume down while in call then press volume up. That's all you need.
Click to expand...
Click to collapse
That works as well That said, this is a pretty annoying thing. Hope they fix it with future updates.
polobunny said:
More simple than that, press volume down while in call then press volume up. That's all you need.
Click to expand...
Click to collapse
It's so simple, but this is what worked for my wife. Apparently she had just been mashing the volume up button the whole time. I forgot to report back in this thread after we discovered that.
Curious what some of you are doing as far as managing volume since Pie. And if my complaint below annoys anyone else.
My complaint about Pie is the fact that the notification volume is married to the ring volume. Typically I want my phone to ring at about 75% and notifications to sound off about 30%.
I've tried sound profile and macro droid. What I've discovered is that even though in both of those applications you can adjust notification volume separate from ring volume like with Samsung, but what ever was last to change is what both are set to. It's very frustrating having my phone blast notifications at 75% or my phone ring at 30% and not hear it. I've created a few macros that almost solve the issue, but the macros are not 100% all the time.
I've searched high and low and can hardly find anyone else complain about this. That makes me wonder, am I missing something really simple?
Sent from my Pixel 2 XL using Tapatalk
Nope, it's been tied together for years, not just with the Pie update. On Oreo and previous versions i was able to use xposed and Gravitybox to separate the notification and ringtone volume levels, or on some custom roms they have that option built in. I updated to Pie, and gave up xposed/gravitybox.. but I would still like the ability to set notification and ring volumes separate. One day maybe..
Scratching my head as to why I never noticed until Pie, I've had my Pixel 2xl since May.
Any other solutions people use that don't require root?
Sent from my Pixel 2 XL using Tapatalk
scott2ya said:
Scratching my head as to why I never noticed until Pie, I've had my Pixel 2xl since May.
Any other solutions people use that don't require root?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I am currently trying out an app called precise volume. See if it works for you.
Sent from my [device_name] using XDA-Developers Legacy app
houtx2 said:
I am currently trying out an app called precise volume. See if it works for you.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
installed precise volume.. haven't noticed a difference yet, and when i go back in and check the settings it seems the system changes the values..
Yeah I remember now, I was using sound profile to manage my sounds. After the pie update I couldn't get it to work well with my DND rules, kept missing important calls, so I ditched it and went all native.
The hack job in doing now is using macrodroid (user friendly tasker like app) monitor for incoming calls and set ringer to 75% unless silent or vibrate, then wait 20 seconds and set volume back to 30%. That makes sure my notifications don't scream at me all the time.
I also set up the DND schedule in macrodroid mainly because using the native DND, it would use the last set volume and not wake me up for important calls. This way when my schedule activates DND, it will also set the ring volume all the way up so the important calls and texts will wake me up while muting everyone else.
Too much work to make all this happen, I miss my Samsung.
Sent from my Pixel 2 XL using Tapatalk
So no solution yet on this, I remember back in the first galaxy days, when I rooted and installed ROM... that was one of the options almost every custom ROM had... hard to belief it never made it all the way into an official google release...
You can always use Automagic (preferred) or Tasker to set up shortcuts. It can adjust each individually. The newest Automagic beta (gotta purchase it) can even intercept your volume buttons. Get creative with it and can probably find a better solution than you previously had.
You can try Volume Butler app from playstore. It works for me.
pvtjoker42 said:
Nope, it's been tied together for years, not just with the Pie update. On Oreo and previous versions i was able to use xposed and Gravitybox to separate the notification and ringtone volume levels, or on some custom roms they have that option built in. I updated to Pie, and gave up xposed/gravitybox.. but I would still like the ability to set notification and ring volumes separate. One day maybe..
Click to expand...
Click to collapse
I just bought a OnePlus 6T after being on a Samsung Note5 since it came out and forgot about this "feature" of stock Android. I don't know why it's too much to ask for these to be separate. Now if I want to silence notifications at night but allow the phone to ring I have to use the Do Not Disturb settings. Should be so much easier than this.
I remember one version of Android had the two sliders for notifications and ringtone separate, and you could select a checkbox to sync them only if you wanted.
What the heck!
I've been on CyanogenMod/LineageOS for the past years and now that I'm on OxygenOS with the OnePlus 6T I'm noticing this nonsense!
What's the problem on having the option to link the ringer and notification volume togheter or NOT???
And at the same time, what't the problem on having the option to choose to use the volume buttons for media or for ringer?
It's a software, leave us the options!
Same here. Lineageos user now oneplus 6. No separate notifications volume. Very very annoying. ****, maybe put an expert mode to android if you think people are confused by so many options. ?
Notification volumee
scott2ya said:
Curious what some of you are doing as far as managing volume since Pie. And if my complaint below annoys anyone else.
My complaint about Pie is the fact that the notification volume is married to the ring volume. Typically I want my phone to ring at about 75% and notifications to sound off about 30%.
Click to expand...
Click to collapse
Yes! I find it really, really annoying. I like to have notifications only just audible but ring tone quite loud and the fact that this is now impossible, is incredibly irritating and frustrating. What on earth were the Android Pie developers thinking of....
I haven't found any fix for it at all but I'm not as au fait with development as you are. I'll keep looking though. Perhaps there'll be a fix from Android Pie developers soon.
I gave my pixel 2xl to my son and picked up a note 9. Forgot how much I missed Samsung. No longer have to deal with that asinine decision to marry ring tone and notification sounds. Love my note9. But miss the camera from the pixel
Sent from my SM-N960U1 using Tapatalk
The easiest way to reduce notification volume is to use Audacity or similar and supress the loudness of the audio file. No need to root the device just for that.
It seems like a huge conspiracy. Why oh why google cannot affort to make it a setting to choose different volumes. It must be that apple is paying them to make android suck.
I miss all most my calls now on my new phone. I just do not hear them with my notifications off. I just cannot have notification volume on at work. I get hundreds of those each day.
But I maybe get a phone call once a week during office our? Also when going to sleep or watching tv or what ever it is super super irritating to get those super loud notifications.
They say is like this since kitkat. Well I come from kitkat and my kitkat did not work that way. Maybe I fixed it years ago but I cannot remember.
Now there seems to be a solution called "Volume Butler" but hey! This is no longer on google play? You would think that google discovered that some people dared having difference volume for ringones and notifications. !!!!
I have a rooted phone I cannot believe it is this complicated to seperate the volumes. and I so do not understand why google is forceing this. what could possibly be their motivation not to make this optional? Sure link by default not problem if we can just turn it of.
okay I found volume buttler some where else but it totallay does not sepperate the 2.
It only shows 2 sliders but only one works and works for both.
I cannot believe this. make my phone useless. Since people cannot call me like most of the time.
I have to get a seperate phone dumb phone? ith a seprate databundle just to get calls and my new . How evil is that. And people will not understand thay canot whats app me on my calling nummbers. They have to whatsapp me on my notification number.
Als this because of a lazy developer at google?
Screw fingerprint scanning or face recognition give me my seperate volumes.
And then people say give feed back! just go to settings / tips /feedback? Well my stock android 9 does not have that.
Getting desperate.
Maybe install 10 versions of each notifications sound and have an app rename them based on the volume I need. But still think it is totally unnessary! This is not a feature it is a basic function of the stupid phone.
I agree it's bs with stock not having this feature. On most custom Roms it's included.
This is on lineage 16
anand_kumar said:
The easiest way to reduce notification volume is to use Audacity or similar and supress the loudness of the audio file. No need to root the device just for that.
Click to expand...
Click to collapse
A genius and elegant solution for a stupid problem that should not be. :highfive: :victory: :highfive: