Jump to content

Recommended Posts

Posted

A couple of weeks ago my voice commands stopped working to dial phone numbers by names in the directory. It will dial numbers if I call the numbers, it will find streets in navigation, but it won't pick up names in my phone directory. Anyone else having this problem? It answers back with "Pardon" or "who would you like to call".

Posted

I am using an Samsung Galaxy S7, Android. I have deleted and reset the bluetooth. The blue tooth is connecting and the music and telephone work. Just not voice recognition on contacts on the Truck. But the Voice Recognition works for navigation and if I say the number. really weird.

Posted

I took my car to the dealer and the charge me to to do two upgrades to the software. Still not working and now my parking detector in the front center is not accurate..... Frustrated!!

Posted

Ive have found with my s7 you have to go into the settings and allow the truck to wake the phone for voice activation to work. The other settings i had to play with was the speed that the phone receives your voice. I talk faster than the stock setting and it wouldnt understand my initial Contact description. My wifes name etc. It seems to be much better now. However it can be a bit spotty sometimes and it helps to wake your phone before you get into the truck. Also the Android app does work good if your connected via the usb. Hope this helps some.

Do some google searches about S7 and voice recognition etc.

Posted

My phone had been working with my truck for over a year. I also tried using my wife's iPhone and the same result. Where do you go to set the speed the phone or truck accepts the speed?

Posted

try under your phone settings. general management. language and input. then text to speech. speech rate. and pitch etc. Helped a little with mine. But sometimes it says it cant find the name I say. Even though it repeats the same name back to me. then my kid tries it and it works. Something to do with how i say the name etc.

  • 2 weeks later...
Posted

Bill Wong,

 

Have you been able to fix this issue. I have been searching for a few weeks regarding this issue and just came across your post. I have a Galaxy s7, and 2016 chevy traverse and my voice command was working just fine until a few weeks ago. Now It will not recognize any name in my contacts, which makes if useless when trying to make a call while driving, as I do not know peoples numbers off the top of my head anymore. I have repaired the devise and still same issue. Have you had any luck? This has been driving me nuts.

 

  • 2 weeks later...
Posted

So i took my truck to the dealer, and they said it was my phone. So my question to GM is: Is there a limit to the number of contacts the voice command/address book can handle? I think I have too many contacts in my address book.

Posted

Bill Wong,

 

Have you been able to fix this issue. I have been searching for a few weeks regarding this issue and just came across your post. I have a Galaxy s7, and 2016 chevy traverse and my voice command was working just fine until a few weeks ago. Now It will not recognize any name in my contacts, which makes if useless when trying to make a call while driving, as I do not know peoples numbers off the top of my head anymore. I have repaired the devise and still same issue. Have you had any luck? This has been driving me nuts.

 

I have not, but I have narrowed it down. I went to the Samsung booth at Best Buy and they updated my phone, still didn't work. Dealer is useless. I think it has to do with the number of contacts I have in my address book. Do you have a lot of contacts? I have over 3,700.

  • Like 1
Posted

A couple of weeks ago my voice commands stopped working to dial phone numbers by names in the directory. It will dial numbers if I call the numbers, it will find streets in navigation, but it won't pick up names in my phone directory. Anyone else having this problem? It answers back with "Pardon" or "who would you like to call".

ok all. I figured out the problem after getting the Truck software updates, replacing two batteries and getting my phone updated as well. The dealer told me that it was my phone, but in fact there is a limit to the number of contacts the Mylink will sync with. Once you go over the limit, the voice commands will not work search the contact list. Not sure if it loads all the contacts. What I had to do to fix the problem is delete contacts out of my phone. I went below 3,700 contacts and it started working again!!!!!!

  • Like 1
  • 1 month later...
Posted

So I have done everything you have and I only have 225 contacts in my phone. It still will not recognize the name I am saying. Like you said before, it will recognize the number just not the name.

Posted

ok all. I figured out the problem after getting the Truck software updates, replacing two batteries and getting my phone updated as well. The dealer told me that it was my phone, but in fact there is a limit to the number of contacts the Mylink will sync with. Once you go over the limit, the voice commands will not work search the contact list. Not sure if it loads all the contacts. What I had to do to fix the problem is delete contacts out of my phone. I went below 3,700 contacts and it started working again!!!!!!

So I have done everything you have and I only have 225 contacts in my phone. It still will not recognize the name I am saying. Like you said before, it will recognize the number just not the name.
Posted

I thought I had it figured out. What kind of phone are you using? I am using an Samsung 7. As a last resort, you should back up all your contacts and add one at a time. to see if it is a special character you put in on accident. That is the only think I can think of.

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

  • Latest Articles

  • Posts

    • I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...