I am developing an Android utility app and I need to trigger a custom vibration pattern as soon as the phone starts ringing. I have set up a BroadcastReceiver to listen for the 'android.intent.action.PHONE_STATE' action, but I am struggling to access the Vibrator service from within the onReceive method. Is it possible to initiate a vibration while the phone is in a ringing state, and what specific permissions are required in the Manifest to ensure this works on Android 12 and above?
3 answers
Yes, it is entirely possible, but you must ensure your app has the correct permissions. You need both android.permission.VIBRATE and android.permission.READ_PHONE_STATE in your AndroidManifest.xml. Inside the onReceive method, you can access the Vibrator service using context.getSystemService(Context.VIBRATOR_SERVICE). For modern Android versions (API 26+), you should use VibrationEffect.createOneShot() or createWaveform() to define the pattern. Keep in mind that for Android 10+, you also need to handle the "Background Execution" limits, which might require you to start a foreground service if the vibration needs to persist beyond a quick pulse.
That is a solid technical breakdown! However, with the privacy changes in more recent Android versions, does the user need to manually grant the "Phone" permission via a runtime prompt before the BroadcastReceiver can even detect the ringing state? I've noticed that even if the permission is in the Manifest, the onReceive code never triggers unless the user has explicitly allowed it in the app settings.
Using the Vibrator class is the right way to go. Just make sure to check if the device actually has a vibrator hardware using vibrator.hasVibrator() to avoid NullPointerExceptions on tablet devices or specific hardware configurations.
I agree with Brandon. Hardware checks are often overlooked in Android development. I also recommend using vibrator.cancel() once the call state changes to EXTRA_STATE_OFFHOOK or EXTRA_STATE_IDLE. Otherwise, depending on your waveform pattern, the phone might continue to vibrate even after the user has answered the call, which creates a very poor user experience.
Ryan, you've raised a critical point for modern software development. Since READ_PHONE_STATE is classified as a "Dangerous Permission," you cannot rely on the Manifest alone. You must implement a runtime check using ActivityCompat.requestPermissions(). If the user hasn't granted it, the system will silently block the broadcast. Furthermore, on Android 11+, if your app targets API 30, you might also need the READ_CALL_LOG permission depending on whether you are trying to access the incoming phone number or just the state change itself.