Extend the API to query phone volume and vibration settings, maybe even set them.
Currently, when developing a alarm clock app, there is no way to tell if the user has his phone set to vibrate only, so a soundeffect set by the user is played even if he has set his phone to vibrate. I find this very confusing, even though the builtin alarm clock behaves the same way.
This would also be good to have for games, so when you launch a game in a quiet environment not all heads turn the user's way :)
Example: alarms with different volumes.
The media volume should be independent of the phone's ringer volume. When we have our headphones on, we don't listen to music on full volume and hence reduce the phone's volume level. But when we remove the headphone the phone volume level continues to be at the reduced level, hence when a phone call comes we can hardly hear the phone ringing.
The button sound on virtual keyboard is too loud when typing, that forces me to volume down when I type, because of this situation I may forget to volume down, and miss my calls..
Allow users to set volume levels separately for different things. This way games or ringtones or music could be quiet but the alarms are still loud.
When we set the phone in silent or vibration only modes - the system should force the sound-off on all the apps/games/notifications. Think about this case, you are in a meeting/movie theater and you want to do something as play a game/update something - in this cases, the phone should not let the apps/games play sounds.
It will be a good idea to give the developers away to check if the phone is in a silent mode or not - and then they will handle this issue.
Split the volume settings up to support different volumes for ringer, music, alarm, etc.
We believe this scenario has been solved this by giving the user more finite control on the ringer and notifications versus media and apps in Windows Phone 8.1. If a user decides to set the volume to a certain level, we should respect that.
If you disagree with this, please provide user/developer scenario and help us drive more into this.
Troppi limiti WP 8.1. Di questo passo si andrà indietro.
I wanted to develop a simple app to programmatically set the phone mode depending on some input factors and cannot because of this stupid oversight.
Please implement this!
Giang Coi commented
Krzysztof Nasiłowski commented
Hacen un teléfono q tiene la tecla debsonido frágil y el app no funciona......y quieren que no pensemos en cambiar de marca???
If this problem isnt fix soon I will get an iphone and stop worring for Nokia stupid apps
Erica Melgarejo commented
Actualicen la aplicación para Windows phone 8.1 por favor
It would be good if apps could change the sound level if you want this. E.g. turn off sounds triggered by your are in a meeting (Outlook and busy). I sincerely hope this will be included in Win 10.
this os seems made by stupid students. Why should an app change volume? Maybe because the buttons doesnt works anymore? Maybe an app can change the volume after 23:00 or if i am at work. You know what utility means, or you are too ignorant to undertstand what user want?
Giuseppe G commented
If a user want to control volume by software, that is what HIS NEED!
WP will die if you continue on this way!!!
I will be the first who will switch to Android!
But what the **** are you doing!?!? I really don't understand!
Clearly windows gets back to its rigidity that resulted in its demise from the top position.
Scheduling of volume profile was a very very useful function to us working people so that we can set our phones as a real personal assistant. Go on vibrate between x hours to y hours, maybe offline between z hours to zz hours. Loud between certain hours. It is such a basic functionality that not having it hurts.
It is not a question of respecting users settings. This feature will EXTEND users wishes give him more flexibility.
Hi, I had voted on this issue with additional comments. If these changes in the API are already present in Windows Mobile 10, then I believe that's acceptable to shelve for 8.1.
However, if not, I'd like to provide this simple scenario:
-> Profile Management: App/Built in (Cortana?)
Simply put, the classic profile structure once available for phones is the base case here. I want to set a simple scheduler for my day. A silent profile either based on time (730AM - 4PM, M-F) or location (Approaching work...). One for normal volume (anytime and anywhere else) and one for Quiet Hours, all based. Quiet hours is a bit extreme for a medium ground. So to do all this, either handle it, or open the API up. Alert the user, just like with location, that they are granting app access to this item.
Scenario: Whatever material you use for the volume control buttons on your phones isn't strong enough to even last a year, so now I can't change the volume my phone outputs audio thus I must use headphones in a quiet room to even hear the slightest thing.
Fix: Make an app, or an update for apps that are already made for this problem so that I can actually change the volume of my phone.
Glad my contracts almost up though, switching back to apple soon :|
Alexander M. Batishchev commented
So wasn't it declined? Why then marked as 'done'?
The scenario is a profile app: change volume and other settings based on a profile - time, location, etc.
There is a scenario: For apps that have situational awareness. E.g. Shut the phone silent while in a meeting and revert back to normal volume when the meeting ends.
My old Symbian phone was able to do that (with an app called "situations" + many many more possibilities). This was awesome in university, when everybody was fiddeling with their phone before the lessons/lectures started, and I just couldn't be bothered, because the phone knew it had to go silent
Chris Schaller commented
I want to make a sort of scheduling assistant app, not necessarily for meetings, but as a manager I have defined periods of the day for productivity that I do not want my developers phones bugging them or other people in our code house, I want to silence or turn down the volume. I already have a TFS integrated app that tells us what to do and when, it was an obvious feature that was easy to do on other platforms that we cannot do on windows. Fix it because it is a standard API across handsets, let us developers deal with the users when they use our app. If the user didn't want another way to access the volume controls, they wouldn't install our app. So the control really is back with the user.
David Romero commented
What if the user wants an app to control the volume? Shouldn't we respect that too?
BTW, why mark it as done when you're obviously rejecting it?
Can't control volume, any progress on This?