[wooka]

Haha I've also bought one of these boxes (the basic version without a SIM). I'll give it a shot.

The latest is that I had my IP wiring (engine to the tail light) changed last week. I'm elsewhere right now with the SN so haven't been able to drive the thar about. Will post back within 3 weeks or so whether the IP wiring has been any help. I really doubt it. My ICE 'silver box' was replaced twice by Nippon including my USB wiring - alas, no dice.

I even tried Carsifi (have one now if anyone's interested) to go wireless AA but it only disconnected as frequently as ever. The same thing works flawlessly all day in a Jeep renegade.

Alas, Mahindra, why Nippon...?

[AutoNoob]

I was in similar situation with my 2021 Swift since almost the first month. The Android Auto used to hang and there were these outcomes :

1. phone would be auto-disconnected and wouldn't reconnect;
   
2. Going back to homescreen would not allow to go back to AA. After few attempts the phone would be auto-disconnected and wouldn't reconnect;
   
3. If the HU was kept on AA screen only, the HU sometimes would go in auto-reboot and then start working normally.

In case 1 and 2, phone won't reconnect even after physically disconnecting and reconnecting. Then only two solutions remained:

1. stop the vehicle, turn-off, wait for about 2min and restart vehicle. Things would go normal till next hang. OR
   
2. resetting the HU from its settings.

Did multiple trials :

• various cables original, branded, localdifferent phone
• cleaning USB ports on phone and vehicle
• Ensuring phone apps like GMaps, Spotify have no power or data restrictions while in background
• Resetting infotainment and phone

Still the issue remained.

I observed that this was more frequent when the system had multiple things running parallel e.g. Navigation (in foreground) and music play via Spotify OR Navigation (in foreground) and phone call in background.


The Solution:

All this while I was in touch with my SA as well. Few weeks back he called to inform that a trial firmware update is available. I went rushing and got the update. Now, the AA still goes to hang occasionally but the frequency has reduced significantly and it's bearable. Also, once it hangs, just physically disconnecting and reconnecting phone resumes it. Now waiting for stable release.

So, I think in case of Mahindra Thar as well, it's related to some software bug. The only reliable solution would be a firmware update from M&M.

[rajeevsulu]

Originally Posted by ph03n!x

Did Android Auto work without disconnection for 2 - 3 hours for you - I remember you doing long drives non-stop, so if it worked without disconnection (neither by you switching off or unplugging nor the HU doing it's thing), it'll be interesting to compare your HU with mine!

Yes, I have done a few non stop runs of upto 5 hours or more duration and it never threw a tantrum. If you are somewhere this side or me in coimbatore, we can meet.
Cheers

[Kosfactor]

Originally Posted by AutoNoob

I observed that this was more frequent when the system had multiple things running parallel e.g. Navigation (in foreground) and music play via Spotify OR Navigation (in foreground) and phone call in background.

*Snip*

So, I think in case of Mahindra Thar as well, it's related to some software bug. The only reliable solution would be a firmware update from M&M.

Good observation.

It`s got something to do with the USB controller \ firmware being old, it accepts only certain amounts of data or disconnects afterwards. If the cable is 2.0 it may force the phone to send less data perhaps.

Perhaps we can experiment with the developer settings of Android Auto by scaling the video to the basic resolution and selecting AAC instead of PCM in the audio output, maybe even switch the audio app in the phone to use low bitrate etc.

[AutoNoob]

Originally Posted by Kosfactor

If the cable is 2.0 it may force the phone to send less data perhaps.

All my cables before and after the firmware update are same (USB 2.0), and issue is almost resolved after firmware update. So I think cable protocol itself might not be an issue.

Infact, I doubt the data rate will be so high that it overwhelms USB 2.0; unless HD video stream is running from mobile to HU.

Perhaps we can experiment with the developer settings of Android Auto by scaling the video to the basic resolution and selecting AAC instead of PCM in the audio output, maybe even switch the audio app in the phone to use low bitrate etc.

This is new to me. I'll try this as well.

[ph03n!x]

Originally Posted by Kosfactor

Can someone try a cheap USB 2.0 cable and let us know? It would be rated for a max of 480 mbps, should cost only about 300 Rs or less.

Did that - in fact some of the OE devices/ cables (Moto Z2 Force, Huawei P30 Pro) combinations I had were USB 2.0.

And if it's the cable/ interface, Apple Carplay should display the same behaviour - but it does not. The Android box I now have connects to the Thar through Carplay, and stays connected.

I can now safely say this issue is resolved for me...

Originally Posted by Kosfactor

...

Perhaps we can experiment with the developer settings of Android Auto by scaling the video to the basic resolution and selecting AAC instead of PCM in the audio output, maybe even switch the audio app in the phone to use low bitrate etc.

Played around with this too - including the transcoding settings under USB Audio routing.

Like I said, I've spent 3 years doing everything within the phone, AA, settings, cables purview.

The model of the ICE system that comes with my Thar is N3000D, and the USB controller in it is made by Telechips with a version of 320.17.1 - I was getting into the details of this controller when I took the easy way out by buying the Carlinkit Android box...

Originally Posted by AutoNoob

All my cables before and after the firmware update are same (USB 2.0), and issue is almost resolved after firmware update. So I think cable protocol itself might not be an issue.

Infact, I doubt the data rate will be so high that it overwhelms USB 2.0; unless HD video stream is running from mobile to HU.

This is new to me. I'll try this as well.

Maruti was decent enough to find a solution for this issue and update the firmware. I am using AA through an external Android box to bypass M&M's crappy Android Auto implementation!

[Kosfactor]

^ This is no doubt a HU problem, it is deactivating the USB based on some parameters. I'm trying to see if there is a work around without having to purchase another device.

The odd number series 5OO's Android auto was stable with different phones we used over cable , even the music quality was very good. So my guess is this is some other head unit model that they are using which is defective.

[sharma1arjun]

I got both the head unit and the IP wiring changed in my RWD thar.
Still the disconnections are there. Ive used OE cable and multiple others as well. I have given up now.
I think we should collectively report this somehow.

Originally Posted by ph03n!x

Did Android Auto work without disconnection for 2 - 3 hours for you - I remember you doing long drives non-stop, so if it worked without disconnection (neither by you switching off or unplugging nor the HU doing it's thing), it'll be interesting to compare your HU with mine!

The first time I complained in the service center about this issue, they sent a 4x4 thar at my home with the mechanic.
We tested AA in that car first, there were no disconnections, it worked absolutely fine. Then we swapped HU with mine in the same car, which worked flawlessly. After that the spare car's HU was attached in my car, disconnected after 30 minutes.

We even swapped the usb ports to fully test the systems in both the cars. Their thar had no issues.

After this they ordered new IP wiring and replaced it in my car. I am still faacing disconnections. I think this has something to do with the power supply which due to inconsistent power suspends the usb connection and the phone acts like the USB has been connected for the first time.

Also there is one more thing. The wiring, the first time IP wiring was ordered for my thar with the VIN, Mahindra shipped the wrong wiring wirh different couplers, which was later replaced with the correct one. This makes me think, are there different types of wiring in differente thars. Maybe it's the wiring that is causing this issue.

Let me know your thoughts on this.

[ph03n!x]

Originally Posted by sharma1arjun

...
We even swapped the usb ports to fully test the systems in both the cars. Their thar had no issues.
...

The issue is intermittent, and no saying how soon or long it takes to come.

Originally Posted by sharma1arjun

...
After this they ordered new IP wiring and replaced it in my car. I am still faacing disconnections. I think this has something to do with the power supply which due to inconsistent power suspends the usb connection and the phone acts like the USB has been connected for the first time.
...

The issue is not just with the USB port - but probably with the Android Auto implementation with this USB Controller - Apple Carplay does not disconnect for 5 - 6 hours at a go, which will not be the case if it is just a port issue.

Originally Posted by sharma1arjun

...
Also there is one more thing. The wiring, the first time IP wiring was ordered for my thar with the VIN, Mahindra shipped the wrong wiring wirh different couplers, which was later replaced with the correct one. This makes me think, are there different types of wiring in differente thars. Maybe it's the wiring that is causing this issue.
...

I'm guessing this is because the first few batches of Thar shipped with 2 USB Ports - one for connecting to the HU and the other a fast charging port. The fast charging was later dropped from the spec, which would mean change in wiring too...

[sharma1arjun]

Originally Posted by ph03n!x

The issue is intermittent, and no saying how soon or long it takes to come.

I kept that thar for 3 days after the HU change. I am sure the android auto connection was solid.

Originally Posted by ph03n!x

The issue is not just with the USB port - but probably with the Android Auto implementation with this USB Controller - Apple Carplay does not disconnect for 5 - 6 hours at a go, which will not be the case if it is just a port issue.

This means an update from Mahindra can fix this? If so we all can collectively do something about it. What do you think?

[ph03n!x]

Originally Posted by sharma1arjun

I kept that thar for 3 days after the HU change. I am sure the android auto connection was solid.
...
...
This means an update from Mahindra can fix this? If so we all can collectively do something about it. What do you think?

Mahindra are definitely following this thread, so hopefully something will come out of it.

I'll also check the version/ differences between mine and @rajeevsulu's HU in his RWD (which doesn't disconnect), hopefully something will come out of it...

[sharma1arjun]

Originally Posted by ph03n!x

Mahindra are definitely following this thread, so hopefully something will come out of it.

I'll also check the version/ differences between mine and @rajeevsulu's HU in his RWD (which doesn't disconnect), hopefully something will come out of it...

If you want I can provide you with my HU model and version as well. Maybe it'll help.

[vedirah]

Do you guys have any updates on this? I still face this issue on my XUV 300 and it's annoying.

[wooka]

So far, using an external AI box on car play protocols seems to be the only option. Phoenix above had a detailed write up.

Please see the quoted text in the first post of this thread

[rajeevsulu]

Originally Posted by vedirah

Do you guys have any updates on this? I still face this issue on my XUV 300 and it's annoying.

Hi, I have had no disconnect issues whatsoever. Mine is a RWD Thar 2023 March model. I use OE cables which comes with the phone. I think mine is a one off because two RWD Thars in my vicinity have the issue. I don't know what to make of it.

Cheers