News
GTO recently shared this with other enthusiasts.
Can't believe it's 3 years since the launch and Mahindra still hasn't fixed it! The damn Android Auto keeps disconnecting from the phone. Personally, I use Bluetooth streaming as the volume levels are noticeably louder & I need that in the soft-top convertible (as outside sounds come in easily).
BHPian ph03n!x has shared the following:
I figured out that Apple Carplay in the Thar is rock stable while a cousin was playing DJ in a recent long drive - iPhone users on the forum too have indicated this.
I looked stuff up and figured that there are devices that connect to the vehicle's Carplay and can then display Android Auto (or Carplay) through them. And I bought one a month ago, which solved the Android Auto disconnect issue. I bought this for 15k during the sale. I also figured (after it's too late to return mine!) that there are other products like this that have only the functionality I need for 10k - the box I bought is also a standalone media player that can take a SIM card and stream Netflix, YouTube etc., which I don't need / use.
A Team-BHP Fan who prefers to stay anonymous writes in:
Hi Rush,
I was reading your Thar thread and read about the Android Auto issue. My daily is an XUV300 which has the same infotainment system hardware and I wanted to share my personal experience
- Please use only the Genuine Phone OE cable (e.g. Samsung, OnePlus depending on what you use).
- Try to keep the phone on a flat surface or a snug place (I know Thar has limited storage) if possible to minimise its movement while driving.
- Also, put USB cable organizers to ensure the cable movement is minimal when the vehicle goes over a broken surface. They also make the cable look more organized which is an added bonus. You can get something like this.
- Lastly, get a new cable every 1-2 years depending on usage. I have realised that the issue happens more frequently as the cable starts ageing.
This has reduced the disconnection problem significantly to almost zero in short trips.
Here's what BHPian BleueNinja had to say about the matter:
Even the XUV 700 seems to be plagued with this Android Auto disconnect problem.
The workaround I have implemented on XUV is that I first connect my Android phone wirelessly and then connect the charging cable to the phone to minimise battery loss.
For the Thar, a similar approach can be taken but I guess an external device will be needed to help with wireless connection because Thar doesn't support wireless connectivity natively.
Here's what BHPian rajeevsulu had to say about the matter:
I connect my phone using the OEM cable that comes with the phone. When the cable was getting frayed, I bought a high-speed data cable which did not work. Only the OEM cables work. Via the cable, AA is stable till I engage the reverse gear. Once the rear camera display comes on and then goes away when you engage 1st gear, only Google Maps is displayed on half the screen! The other half is blank.
The only way to get it to work is to unplug the cable at the phone end or to shut the engine off and restart it. It becomes cumbersome when you have to do it mid-drive. It sure can be improved.
Here's what BHPian Dr.AD had to say about the matter:
Personally for me, in my 2023 Thar which I have driven for 8,500km for now, this was never the issue. Android Auto is rock solid and worked great for me for my travels, from Day 1 of ownership.
Maybe I just got lucky, because one person's experience does not hold any statistical value. However, I have empirical evidence to believe that the choice of cable is a make-or-break deal for Android Auto.
I use cables from a brand called "Cable Creation", and I have had a very good experience with those cables. Here is one cable that I use.
This works well for Android Auto without any disconnection at all. Then I also have a longer (3ft long) cable from Cable Creations and that also works great!
However, once by mistake, I plugged in some other USB cable that I had lying somewhere in the glove box, the one I had no problems with in the past. But this time, it took a while for the headunit Android Auto app to get started and recognize my phone, and instantly I could see the connection was unstable. Same phone, same car, same headunit. Just another cable (which also worked in the past) and this time bad connection. I switched back to my usual cable and again Android Auto fired instantly and everything was smooth. I tried it again with the other cable (just to verify the issue) and again a bad connection. Back to my usual cable and again all fine.
So my suggestion is to please keep trying different cables of reputed brands and see if you find a "stable cable connection", and maybe this will solve the problems!
Here's what BHPian sandeepmohan had to say about the matter:
I suspect this problem has more to do with the hardware behind the dashboard. It's also about Android Auto being fussy as the software works on a wide range of hardware.
My experience is from a different vehicle. I recently retrofitted a Road Top Android Auto/Apple Car Play box to my car. I face the exact same issue. No luck with a new cable either. Wired Android Auto disconnects at random intervals.
The same cable connected to the stock stereo fitted in a Mitsubishi Outlander offers a stable connection. Works flawlessly.
It is practically impossible to position your phone with zero movement in your car. Even if you do find the phone stable, the cable will move, with vehicle movement. I am not sure if that is the main reason for disconnects.
I got into Developer Mode on my phone (As my phone is running Android 10) and enabled Wireless Android Auto. This offers a more stable connection than wired.
It might be worth prying out the head unit on a Thar and checking if it has a wireless antenna terminal. For all you know, they would have skimped on plugging in a WIFI Antenna which limits the wireless capability of the unit.
Check out BHPian comments for more insights and information.