Android Oreo Squashes A Small VOIP Bug
Android 8.0 Oreo has introduced a number of new features and improvements, some obvious and some less so. A new subtle improvement is how Android Oreo handles VOIP calling. If you’ve not heard of VOIP calling, this is a way of handing a voice call over the internet connection – it’s the technology that underpins Google Hangouts Voice, Facebook Messenger, WhatsApp’s voice calling features, plus other applications. Thanks to Google Hangouts and Google Hangouts Dialler, over half of my monthly cellular data allowance is spent on Google Hangouts VOIP calls. In the last few years, Hangouts Voice Calling has improved in leaps and bounds, but there are some significant compromises on the Android platform, which stem from how the operating system does not consider a VOIP call to be the same as a cellular call.
On a VOIP call, the Android device knows that the user is on a call and it will blank the screen when the proximity sensor is triggered. This means that your ear does not operate a control when the ‘phone is pressed up against your face. On some Android devices, the proximity sensor effect is delayed compared with on a voice call. Now on a normal cellular call, the volume keys always remain active, which means you can adjust the sound level of your caller whilst talking. Unfortunately on a VOIP call, the volume keys are disabled when the screen is blanked. This means if you are wanting to adjust the volume you’ll need to move the ‘phone away from your ear, adjust the volume up or down, and replace the ‘phone to your face to listen to the results.
The good news is that Google has fixed this issue with Android Oreo. Those volume keys will remain active during a VOIP call. If you regularly use VOIP calling services, and if you find yourself having to constantly adjust the volume, Android Oreo’s fix should help things a lot. It’s also great to see Google adding and improving some of the basic communications features, and hopefully there will be less of a need to find workarounds in the future.
SOURCE [XDA Developers]