Jump to content

Android Auto malfunctions

Ethan Boggio
 Share

Recommended Posts

Ethan Boggio New Member

Ethan Boggio

Posted
Posted

Hello y'all! Here's some info... I own a 2018 Silverado with 8" touch screen and use a Samsung S8 phone. When using navigation weather it be Google Maps or Waze my screen jumps around. Jumps ahead, to the far left and far right. It also stutters. It doesn't always do it but does it enough. It's very frustrating to say the least. Has anyone else had this issue and were you able to fix it? If so how? I'm at the end of my rope here.

mikeyk101 Senior Enthusiast

mikeyk101

Posted
Posted

I had exact problem with my Galaxy Note 8. It worked fine when I first got it but then began doing the same thing. I could sometimes toggle location and it would help for a little while but would end up doing it again. I complained on Android Auto forum and they blamed Samsung and Chevy. I complained on Samsung forum and they blamed Chevy and Waze. I complained on Waze forums and they blamed Android Auto. And IIRC, Chevy blamed both of them. I never did get it fixed. The only thing that worked was getting rid of the Note 8 and upgrading. I know have a Galaxy Note 20 Ultra 5g and it pretty much solved the problem. I will occasionally get freezes but few and far between. One suggestion you could try is to uninstall Android Auto and Waze, restart the phone and install fresh copies of each. If that doesn't work, you may have to upgrade or go with a different brand. The problem did seem to happen a lot with the Samsung Galaxy S8 and the Note 8 for some reason...

MikeBMW Senior Enthusiast

MikeBMW

Posted
Posted (edited)

I really hate to be "that person" aka Apple fan boy, but my iPhone, even running the IOS 15 Beta (I'm a developer), the only issue I've had is connectivity, on occasion, wherein the infotainment screen is still looking for the phone after plugging in the USB.
A simple unplug and replug always connects it.
I wish I had more experience with Android to help but this is all I can add ... sorry. :(

Edited by MikeBMW
mikeyk101 Senior Enthusiast

mikeyk101

Posted
Posted
5 hours ago, CrawlSlow said:

Try different cable, try different phone, if all fails try reprogram the HMI.

For whatever reason, Samsung Galaxy S8 phones as well as the Samsung Galaxy Note 8 like I had were known for problems with Android Auto. I dealt with it for a while and discovered that there were many others in the same boat. There was a lot of fingerpointing from all sides but no one seemed to want to or be able to solve it. The only solution I found was switching to a newer phone. And I am still using the same USB-C cable that I was originally using on my Note 8 on my Note 20 and it works just fine. 

mikeyk101 Senior Enthusiast

mikeyk101

Posted
Posted (edited)
9 hours ago, CrawlSlow said:

For note 8 or s8, enable developers mode and change usb type to MDI as default and see if that helps. If not, just use your note 20. 

I actually enable Developer Mode on all my phones as one of the first things I do after getting it. I went through all of that including even opening developer mode inside of Android Auto after the AA folks had me do it. That can be done by opening Android Auto on your phone, going into AA settings, tap on version info 10 times and then switching developer mode on and off by clicking on the 3 dots in upper right while in AA settings. Like I mentioned, for S8 and Note 8, it's a known problem that none of the involved parties including Android Auto, Waze, Samsung, or Chevrolet seem to be able to or want to solve. And now that both the S8 and Note 8 are basically obsolete, I think it's pretty much going to be ignored. 

Edited by mikeyk101
Spikes Enthusiast

Spikes

Posted
Posted
10 hours ago, mikeyk101 said:

For whatever reason, Samsung Galaxy S8 phones as well as the Samsung Galaxy Note 8 like I had were known for problems with Android Auto. I dealt with it for a while and discovered that there were many others in the same boat. There was a lot of fingerpointing from all sides but no one seemed to want to or be able to solve it. The only solution I found was switching to a newer phone. And I am still using the same USB-C cable that I was originally using on my Note 8 on my Note 20 and it works just fine. 

S8 was really not a great phone (compared to various other gens, like S7 was good). Samsung tends to have an every other version type of thing like Microsoft does.

 

Also too, the S8 is over 4 years old now so I wouldn't be surprised if people have issues with it still.

  • Like 1

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

  • Latest Articles

  • Posts

    • Jsdirt
      2010 Avalanche 5.3 not running correctly after engine swap.

      By Jsdirt · Posted

      If everything checks out at the MAF, then the MAF is BAD, new or not.   You don't need a signal generator to troubleshoot this. PCM needs ALL powers and ALL grounds able to light a halogen headlight bulb - if it can light the bulb bright, then the wiring is good enough to run the PCM.   Best thing you can do for yourself is spend some time here: scannerdanner.com - Check out all his YouTube videos on similar issues. If you decide to subscribe it's the best bang-for-buck ratio in the automotive world, hands-down. He's got TONS of free vids on YouTube, too.
    • Tyler Gibbs
      PF63 Oil Filters Going Away?

      By Tyler Gibbs · Posted

      You got that Hengst D110??
    • contrabombarde
      2010 Avalanche 5.3 not running correctly after engine swap.

      By contrabombarde · Posted

      Yes, I used my multimeter to probe all of the wires at the MAF, both with the sensor connected, sensor disconnected, key on engine off, key on engine running, etc etc etc. I probed all of the wires again at the PCM, at the connectors, etc. All voltages are what they should be according to the service manual/wiring diagrams. All grounds are good, less than 20 millivolts from the battery negative under load. Both at the connector of the MAF, at the PCM connector etc.      I know this throws a pretty big wrench into things, but this truck was acting up before the swap. I don't have very much information, if any on what was causing it, but if you cleared all of the dtcs it would do the same thing where it would crank, fire, then die. And it would do the same thing a dozen or so times, and eventually it would start and run, but the difference is that it would run and actually be drivable. Whereas now if you can drive it at all, it goes into reduced power mode almost immediately, and even then it's not running correctly. When you come to a stop at a light it stumbles down to for 500 RPM before catching itself and returning to the smooth idle. And if you go more than about 50% throttle then it immediately goes back to doing the misfire thing.    Like I said, I know that throws a wrench into things, and unfortunately I was not able to pull any data or anything like that before I did this work, so I don't have much to go on.    I'm trying to not fixate on one particular thing as the cause of the problem, but it seems like all avenues are pointing me towards the PCM. Like I said I have tested the wiring extensively (see above), and during cranking the sensor does produce seemingly legitimate values at least according to my multimeter, but as soon as the engine fires those values quickly descend into gibberish. I've tried it with multiple different known working sensors, I have done literally every test I can think of multiple times on the wiring (probing the signals, probing the pins with the sensors unplugged, probing the pins at the PCM, voltage drop, voltage drop under load, continuity, ohms, and double-checking everything against the wiring diagrams/ proper values in the service data.)    Another thing that pushes me towards a possible PCM failure is, I have noticed in troubleshooting a little bit taking a break and coming back, that when I leave the truck to sit for a while and cool off, it starts and runs smoothly when I first start it up. However once it warms up. It starts having problems. For example, when I went out to the truck this morning after it had been sitting overnight, I was actually able to drive it down the block. And then once I got on the throttle a Little bit after going about a thousand ft, it started misfiring again. I pulled it back into the driveway, shut it down, and started it back up. It idled smoothly. As soon as I touched the throttle it did the misfire thing again. From then on as soon as I started it it would misfire. I shut the truck off and went to go get a coffee and do a bit more research. When I came back out I started the truck up and it immediately went into the smooth idle. After a couple of minutes of playing around with it, it would not idle smoothly anymore. Let it sit a couple of hours, rinse and repeat. This makes me think with temperature change something is going wrong inside the PCM. I have the PCM out of the 2007 donor vehicle and I'm thinking of getting a one-day subscription to the ACDelco programming service to try and program that and see if it helps.   Like I said, I'm really trying to not fixate myself on one potential cause, but it seems everything is pointing me towards PCM failure. I would really like to try to confirm that, but unfortunately I don't have an oscilloscope or a signal generator to do the GM service procedure where you feed 5 khz into the signal pin. 
    • Jsdirt
      2010 Avalanche 5.3 not running correctly after engine swap.

      By Jsdirt · Posted

      Ahh, sorry about that - I got some bad info. Newdude is correct. That's what I get for working 13 hours straight ... on my "vacation", lol.   Should've checked the files I had instead of the internet.   Anyway ... this is GREAT news, since this would've been an absolute friggin nightmare to get working.   I don't think the lack of VVT is causing this - you've got another issue. Wiring, I'm betting.   I'm telling you right now, your computer isn't bad. If it worked before the swap, it's working now. You need to do some more (better) diagnostics and figure out exactly what you're missing. Did you test every wire directly at the MAF? Have 5V reference? Ground? If you're reading ZERO g/s, your Hz isn't much use - it's going to be the wrong value anyway. The MAF is not working, and you need to find out WHY.   I got this off the net, so VERIFY first: Pin A: Black (BLK) wire, Circuit 552, serves as the Sensor Return (Ground).  Pin B: Tan (TAN) wire, Circuit 472, carries the Intake Air Temperature (IAT) signal.  Pin C: Yellow (YEL) wire, Circuit 492, is the primary MAF Sensor Signal output to the PCM. Pin D: Pink (PNK) wire, Circuit 339 or 539, provides Ignition 1 Voltage (Power).  Pin E: Tan/Black wire, Circuit 552 or similar, often associated with the Intake Air Temperature ground or signal return.  Global-A list: https://postimg.cc/KKJnQC85    
    • parthery
      GM Hard Folding Tonneau by REV review

      By parthery · Posted

      Correct....the end user can't reach to Realtruck directly like they can if they purchase a Bak, Undercover, etc...  It has to go through a dealer.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...