Jump to content

HELP: Adding Wireless Android Auto to 2020 Trail Boss LT

Transient
 Share

Recommended Posts

Transient Senior Enthusiast

Transient

Posted
Posted (edited)

I have been trying to add wireless Android Auto on my truck via a dongle that connects to my phone via Bluetooth.  I initially started with Motorola's MA1.  I followed the directions to the letter, but it didn't work.  I disconnected Bluetooth to mychevrolet, and gone as far as unpairing because the phone would try connecting again on its own.  I even made the truck forget my phone.  Phone is Samsung Galaxy S21 Ultra.  Going through the processes, the result is the same with the radio unable to find the phone.  This isn't just an issue with the Motorola MA1.  After a week of failures I decided to see if another device would work, and purchased the AAWireless dongle.  Going through the install processes the result was the same -- failure. 

 

I'd like to get one of these to work, and refund the other.  Is there anybody experienced with these devices and able to help?

Edited by Transient
Dave Schlabowske Enthusiast

Dave Schlabowske

Posted
Posted

2020 Sierra SLT here.  Had the exact same problem trying to get the Motorola MA1 dongle to work. Finally went into the Radio/Entertainment Center and Reset to Factory Defaults. Dongle connected immediately and has been flawless ever since. Hope this helps. 

  • Thanks 1
Transient Senior Enthusiast

Transient

Posted
  • Author
Posted (edited)
14 hours ago, Dave Schlabowske said:

2020 Sierra SLT here.  Had the exact same problem trying to get the Motorola MA1 dongle to work. Finally went into the Radio/Entertainment Center and Reset to Factory Defaults. Dongle connected immediately and has been flawless ever since. Hope this helps. 

Thanks.  I'll look into that to ensure it doesn't delete the GM factory navigation I already have installed.  I don't doubt that last part doesn't make sense.  After all, why would somebody want Android Auto when they have the factory navigation?  I recently moved from California to Florida.  I ended up renting a house because I'll be here for only 3 years.  It's in a brand new area.  The roads aren't even on the GM Nav files.  Not sure if I'm able to get updated maps.  Just thought I'd give Google Maps a try because it's cheaper, and I assumed easier, to install.  I assume Google would be quicker to get the updated maps from. 

Edited by Transient
GETGONE Enthusiast

GETGONE

Posted
Posted

When did you buy the AAWireless dongle? They've had a couple software and firmware updates in the year or so I've owned it. Also, what version of Android do you have? I know my previous Motorola phone kept crashing when running wired Android Auto and Google maps. I haven't had any of those issues once I got a new phone that had Android 10.0 and now 11.

Transient Senior Enthusiast

Transient

Posted
  • Author
Posted (edited)
On 9/4/2023 at 3:46 PM, GETGONE said:

When did you buy the AAWireless dongle? They've had a couple software and firmware updates in the year or so I've owned it. Also, what version of Android do you have? I know my previous Motorola phone kept crashing when running wired Android Auto and Google maps. I haven't had any of those issues once I got a new phone that had Android 10.0 and now 11.

Just bought the AAWireless off Amazon within the last 2 weeks.  I have Android version 13.  My phone is a Samsung S21 Ultra.  Android Auto version is 10.2.633224, or something like that.  I did plug in with a wire and had no issues running Android Auto.  If like to go wireless so I can drop my phone in the wireless charger and drive. 

Edited by Transient
GETGONE Enthusiast

GETGONE

Posted
Posted

I'm using a Motorola One 5G UW Ace running Android 12 and it works fine. There was just a software and firmware update to AAWireless last week.

SEBFL Enthusiast

SEBFL

Posted
Posted

Are you using a VPN or a virtual VPN like DuckDuck tracking blocker? They will affect your wireless WIFI connection to run Driving Mode (FKA AA Auto). I'm running 13 as well along with DuckDuck tracking blocker and it affects my connection as will any VPN which need to be turned off for Driving Mode to function properly.

GETGONE Enthusiast

GETGONE

Posted
Posted

I forgot about the VPN issue. It specifically mentions that if you have one you need to turn it of while using AAWireless.

Transient Senior Enthusiast

Transient

Posted
  • Author
Posted
On 9/7/2023 at 2:22 PM, SEBFL said:

Are you using a VPN or a virtual VPN like DuckDuck tracking blocker? They will affect your wireless WIFI connection to run Driving Mode (FKA AA Auto). I'm running 13 as well along with DuckDuck tracking blocker and it affects my connection as will any VPN which need to be turned off for Driving Mode to function properly.

Nope.  No VPN usage here.  Only person in my household that uses that is my wife, and it's only when she's out of country. 

Transient Senior Enthusiast

Transient

Posted
  • Author
Posted
On 9/7/2023 at 6:25 PM, GETGONE said:

I forgot about the VPN issue. It specifically mentions that if you have one you need to turn it of while using AAWireless.

I returned the AAWireless kit to Amazon and got a full refund.  Stuck with the Motorola unit due to throwing away the packaging, otherwise I would've returned it too.  I think I'm going to do an upgrade through WAMS.

  • 11 months later...
moose09876 Enthusiast

moose09876

Posted
Posted

This worked on my generic dongle:

  • remove the AAWireless device from the phone's Bluetooth devices

  • remove the head unit from the phone's bluetooth devices

  • remove the phone from the head unit's list of Bluetooth devices

  • reset the AAWireless device (other devices, press and hold the button on it for about 45 seconds; during that time it should change color several times)

  • unplug the AAWireless device

  • connect AAWireless device to vehicle USB

  • pair AAWireless device with phone in the phone's bluetooth settings

  • wait for 30 seconds while phone connects to AAWireless

  • after the Map screen/Android Auto should pop up

  • phone should prompt for bluetooth access to vehicle

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   5 Members, 0 Anonymous, 1,931 Guests (See full list)

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...