If your ASUS ROG Phone 9 has gone silent, missing vibrations for calls, messages, or in-game alerts, it can be a real nuisance. This is a common glitch that's usually easy to resolve with a few checks in the phone's settings or a quick restart.
Perform a Quick Restart
Start with a force restart to clear any temporary software hiccups. Press and hold the Power button for about 15 seconds, until you see the ROG logo appear and the phone reboots. This simple step refreshes the system and often brings the vibration motor back online immediately.
Check Your Sound and Vibration Profile
Your phone might be in a silent or Do Not Disturb mode. Swipe down from the top of the screen to open the Quick Settings panel. Look for the sound mode icon, it might say "Silent," "Vibrate," or "Sound." Make sure it's set to either "Vibrate" or "Sound" to enable vibrations. You can also long-press the sound tile to dive into the full sound settings.
Verify the Core Vibration Settings
Open the Settings app and go to Sound & vibration. Here, you'll find the main controls. Ensure "Vibrate for calls" is toggled on. If it's already on, try turning it off and back on again. This menu is also where you can check the vibration intensity, which we'll get to next.
Adjust the Vibration Strength
The ROG Phone 9 lets you fine-tune how strong vibrations feel. In Settings > Sound & vibration, tap on "Vibration intensity." You'll see separate sliders for calls, notifications, and touch feedback. If the vibration feels weak or nonexistent, slide these all the way to the maximum to test. Sometimes a software glitch can reset these values lower than you'd like.
Inspect App-Specific Notification Settings
If vibrations are missing only from specific apps like your messaging app or games, the issue is likely in that app's notification settings. Go to Settings > Apps, select the problematic app, and tap "Notifications." Make sure notifications are enabled for that app and look for a "Vibrate" toggle within each notification category, ensuring it's switched on.
Test Vibration in Safe Mode
Booting into Safe Mode disables all third-party apps. If vibration works normally here, a recently installed app is likely causing a conflict. To enter Safe Mode, press and hold the Power button until the power menu appears. Then, long-press the "Power off" option on your screen. A prompt will ask if you want to reboot to Safe Mode, tap "OK." To exit, just restart your phone normally.
Check for System Software Updates
Outdated software can sometimes cause hardware communication issues, including with the vibration motor. ASUS releases updates to fix these kinds of bugs. Go to Settings > System > System update and tap "Check for update." If an update is available, install it and see if that resolves the silent treatment from your phone.
Review Gaming and Performance Modes
This is specific to your ROG Phone. The X Sense game mode or other performance profiles might have settings that alter vibration behavior to reduce distractions or save power during intense sessions. Open the Armoury Crate app and check your game profiles or system modes. Look for any settings related to haptic feedback or notifications and ensure they're not disabling vibrations globally.
Reset App Preferences or System Settings
If the issue persists, you can reset app notification preferences without losing personal data. Go to Settings > System > Reset options. Tap "Reset app preferences." This resets notification settings, background data restrictions, and app permissions for all apps, which can clear up misconfigured app behavior. For a broader reset, the same menu has "Reset Wi-Fi, mobile & Bluetooth," which can sometimes help with deeper system glitches.
Consider a Hardware Test or Physical Factors
While less common, it's worth considering physical causes. The ROG Phone 9 is a powerful device, and the Snapdragon 8 Elite chip can generate significant heat during extended gaming. In my experience, extreme, sustained heat can sometimes cause temporary sensor or motor issues. Let the phone cool down completely and try again. If you've recently updated to Android 15, there could also be a temporary compatibility bug that a future patch will address.