Jump to content

Recommended Posts

Posted (edited)

Anyone with a 14-15 who did this upgrade using Android Auto and a Samsung phone have any issues with voice activation to ok google via the phone picking up my voice? My phone did an update and now it doesnt work. But does work with bluetooth and if I push the mic button on the bottom right of the screen. I was thinking of getting the 16 Red denali cluster so that feature would work on my steering wheel.  Then I'd have to sell my 15 Red Denali cluster.

 

It is such an inconvenience to have to reach ALL THE WAY OVER to push it. Lol. 

Edited by RACERX7775
Posted (edited)

 I have a Note 8, but I would suspect it's not necessarily as much the phone as it is the Google voice inconsistencies. I did the entire upgrade including the cluster so I could use the steering wheel controls and it worked great. Had to take the cluster out to have something reworked on it. And for the time I didn't have the cluster the Google Voice just didn't work as well as I would have hoped. So from my own experience, I would recommend anyone who does the upgrade, do the cluster upgrade or get the existing cluster programmed so you can use the steering wheel controls. So much easier

Edited by djewell
  • Like 1
Posted

I’m sure this has been covered somewhere in the 74 pages of this thread.... but it takes a lot to go through them.....so my apologies....

 

im starting to gather parts to upgrade my 14 to be CarPlay capable. I’m going to buy a module and a 2.5 HMI and have it programmed. I can’t seem to find a good list of module part numbers that will work.  WAMS only has 4 part numbers listed on their website and literally none of the modules on eBay match up to any of those numbers. Can anyone shed light on this? I know it needs to be a U2M or U2K but there’s a wide range of part numbers with those RPO codes. 
 

im planning on using costal to program once I get parts in 

  • Like 1
Posted
I’m sure this has been covered somewhere in the 74 pages of this thread.... but it takes a lot to go through them.....so my apologies....
 
im starting to gather parts to upgrade my 14 to be CarPlay capable. I’m going to buy a module and a 2.5 HMI and have it programmed. I can’t seem to find a good list of module part numbers that will work.  WAMS only has 4 part numbers listed on their website and literally none of the modules on eBay match up to any of those numbers. Can anyone shed light on this? I know it needs to be a U2M or U2K but there’s a wide range of part numbers with those RPO codes. 
 
im planning on using costal to program once I get parts in 

The WAMS list is a best practices list so that they maintain full warranty compliance. They can work with you on fitment of other modules. Send them an inquiry on their website. They’ll take care of ya.


Sent from my iPhone using Tapatalk
Posted
23 hours ago, RACERX7775 said:

Anyone with a 14-15 who did this upgrade using Android Auto and a Samsung phone have any issues with voice activation to ok google via the phone picking up my voice? My phone did an update and now it doesnt work. But does work with bluetooth and if I push the mic button on the bottom right of the screen. I was thinking of getting the 16 Red denali cluster so that feature would work on my steering wheel.  Then I'd have to sell my 15 Red Denali cluster.

 

It is such an inconvenience to have to reach ALL THE WAY OVER to push it. Lol. 

Did you have the cluster reprogrammed?

Posted
9 hours ago, cbrsilv15 said:

Did you have the cluster reprogrammed?

I started with my 14 silverado dash cluster and upgraded to 2.5 Android Auto and a 14-15 Denali cluster.  At that time, we pretty much had to get the matching year to make it work. Which meant the steering wheel controls for Android Auto would NOT work. Which wasnt a big deal. So, when I hooked everything up, I was stoked when all I had to do was say OK GOOGLE so my phone could hear it, and it worked perfectly. But since my phone updated, it doesnt respond if I have my cable hooked up. My phone also used to have android auto on it. That is now gone also.  I shot a message to WAMS, and the only way to do it from now, is to sell my cluster and find a 16 Denali "RED", not blue, cluster and have it programmed for my truck.

Posted

I have a 2014 Z71 silverado that i'm waiitng on the 2.5 upgrade to arrive from dokus, my question is about the cluster, will it only work with a denali cluster? or can I get a 2017-2018 z71 cluster and have it programmed? 

Posted
2 minutes ago, Jocobe Betancourt said:

I have a 2014 Z71 silverado that i'm waiitng on the 2.5 upgrade to arrive from dokus, my question is about the cluster, will it only work with a denali cluster? or can I get a 2017-2018 z71 cluster and have it programmed? 

Your 2014 cluster will work, but will need to be re-programmed for the volume and skip buttons to work with Android Auto. The buttons will function as normal with the radio and bluetooth music streaming. 

  • Like 1
Posted
1 minute ago, truckmann said:

Your 2014 cluster will work, but will need to be re-programmed for the volume and skip buttons to work with Android Auto. The buttons will function as normal with the radio and bluetooth music streaming. 

ok awesome, where would be the best place to go to get it reprogrammed?

Posted
ok awesome, where would be the best place to go to get it reprogrammed?

www.WhiteAutoandMedia.com


Sent from my iPhone using Tapatalk
Posted
5 minutes ago, truckmann said:

Your 2014 cluster will work, but will need to be re-programmed for the volume and skip buttons to work with Android Auto. The buttons will function as normal with the radio and bluetooth music streaming. 

will the cluster work with apple car play? because I just have an iphone that I want the cluster to work for. 

Posted
will the cluster work with apple car play? because I just have an iphone that I want the cluster to work for. 

Apple CarPlay and Android Auto functionality relies on the newer 2.5 HMI hardware and Radio Module for it to function. In addition, it used to be, that you needed to upgrade the cluster too to allow the “press and hold” button on the wheel to interact with your phone. That is no longer the case.

I did a video showing that here -


So to get CP/AA to be fully integrated, you need the cluster to be programmed and the HMI hardware.


Sent from my iPhone using Tapatalk
Posted
39 minutes ago, pgamboa said:


Apple CarPlay and Android Auto functionality relies on the newer 2.5 HMI hardware and Radio Module for it to function. In addition, it used to be, that you needed to upgrade the cluster too to allow the “press and hold” button on the wheel to interact with your phone. That is no longer the case.

I did a video showing that here -

 

 

 

is that the only thing that will not work if I do not upgrade the cluster? 

39 minutes ago, pgamboa said:

 

 

Posted
 

Correct. You can still use the voice “Hey Siri/Ok Google” to invoke your assistant.


Sent from my iPhone using Tapatalk

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

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...