Showing results for 
Search instead for 
Did you mean: 

Bluetooth issues with ROG phone 7 and vehicle pairing / app crashing / bluetooth not disconnecting

Star III

Been using my brand new ROG phone 7 (ASUS_AI2205_E) for a week now. I am noticing a few bluetooth / connectivity issues:

1. The bluetooth does not seem to disconnect from my car when I get out. My car says it is not connected to my phone, but on the phone, it still says it is connected to the car. This is somewhat a pain because some apps, such as google maps assume I am still in my car and switches to drive mode.

2. I also noticed that just when I get out of my car (around the time when my bluetooth should ideally disconnect), my phone seems to get unresponsive and apps might crash. One time, the screen froze and I could not even pull down the notification tray, and I had to manually restart. One other time, the phone had auto restarted.

Wondering if anyone else has noticed these...


Star I

I have the first issue. It stays connected on the phone and I have to turn bluetooth off to be able to use speakerphone for example. Also, in the car the music plays but the phone fails to connect. I had similar issues with other bluetooth devices but the device worked fine until I used a phone app to send updates to the device, then it started a connection loop like the phone does in the car.




I have a couple of questions.

1.- Which firmware version is your phone on? You can find this by going to Settings -> System -> About phone -> Device name.
2.- Which Car model do you have?

3.- Could you maybe help us with a log so that the R&D team can check what could be producing the issue? I'm writing the info down below and when done feel free to send me a PM with the link.


Please follow the below steps to enable the built-in log tool (Bug reporter).
1.  Open “Calculator APP”
2.  Enter “.19595+=”
3.  Select the Log type according to the type of issue you want to capture. “Bluetooth”
4.  After your selection the log tool will exit so you can duplicate the issue or wait for it to happen. Try to use the screen recorder to show your issue when possible. If you can't screen record your issue, then please take a screenshot right after the issue has occurred (as a timestamp) so we know where to look in the log.
5.  Navigate back to the log tool via calculator and Tap "FINISH AND SHARE".
6. It takes several minutes for the log to generate. You can exit and do other stuff in the meantime. A silent notification will tell you once the process is done. Tap the notification and then the share button to upload the file to Google Drive and share the link with a moderator. Just make sure to change the permission first so that everyone with the link has permission to view it.
Note: When you're no longer planning on logging your device, enter “.09595+=” in the calculator and the log tool will stop as well as deleting all stored log files. Make sure to share via calculator. The files found in internal storage -> asus_log are not the correct files (they are only 1.2kb)

So I'm not sure if this one was for me, but I had something interesting take place. The other day on a chat with Asus Support they had me try Safe Mode and a Factory Reset, all of which failed to work and I was issues an RMA.

However, I hadn't shipped it yet when you responded so I figured I'd enable the log to at least see if something stuck out. After I enabled the log, I deleted the bluetooth connection currently there and reconnected to my truck and it was successful. Think that was weird I disabled the log again and deleted the connection and remade it and it was successful again. Thinking perhaps it was because the phonebook was empty I disconnected and recreated the connection again but this time with a contact and it was successful a third time.

Any idea why enabling and disabling that log might have triggered it to work? Not only did the phone connect, but when I shut the truck off the phone properly saw the Bluetooth terminate and my phone app worked fine.

Star I

To update at least my experience, the "fixing" that happened didn't last. The phone is going through RMA process.