Bluetooth Options For 2008 Silverado

[Royal Vader]

did you try the "power" button on the mirror itself that turns this function on/off?

 

 

 

yup that fix it ! man i fill stupid

 

thanks

 

 

No reason to feel stupid - That's why this forum is here. There are a lot of bells and whistles on our trucks. It's easy to miss one once in a while.

[jmitchell]

Hey everyone, I've been researching this mod for the past couple weeks between this forum, the CadillacForum and many others. I went ahead and ordered two modules (two vehicles) from rev281 off eBay. So here is the summary of what I've got going and the issues with each:

 

1. Car #1: 2007 Chevy Tahoe, Non-Nav & Bose. Installed VCIM #20756237 (+ BT antenna). All functions working properly except the caller ID on the DIC only displays the number ~40% of the time. Both outgoing and incoming. For instance, just made three calls this morning and the first two going out showed caller ID, then first one coming in nothing (and nothing in either direction after that). Last night, using a different phone, I drove to the store and everything worked. Drove back, and nothing worked from the start (both directions). So I have ruled out that its my phone causing the issue. Very sporadic and no rhyme or reason to it. Similar issue from ChevroletForum but with their 2009 Tahoe with factory BT...Link Here. It would work in a 2010 but not in their 2009, but they never had a solution. I have deleted the phone from the VCIM and deleted the GM Motors from my phone and completely paired everything again. Any ideas here? Could I have a faulty antenna or VCIM?

 

2. Car #2: 2007 Chevy Tahoe, NAV & Bose (no-DVD). Installed VCIM #20827036 (+BT antenna). Can't access the phone from the steering wheel "mute/answer" button. With the radio OFF, I hold the "mute/answer" button and get absolutely nothing. With the radio ON, I hold the button and get a "beep", then must say "Onstar" then say phone commands i.e. "Call Home" and it will call at that point. I can also access the phone menu directly by pushing the "phone" button on the mirror, then pushing the "mute/answer" button twice at which point it prompts "Ready" and I can tell it to call, dial, etc. Similar to the video in the first post on this page... Link Here. I updated the Nav disc to ver. 4.0c this morning (was all I had) but that didn't work either. Could this be a Nav disc update issue that I would need the most recent disc or any ideas?

 

I plan on swapping the two VCIM's and antennas between the two vehicles today here in a couple of hours to see if that makes a difference, but I'm running out of ideas. I feel like I have exhausted all the forums and can't seem to find similar issues or at least solutions to these issues. Any ideas on these issues??? Thanks for your help. Can't wait to get this working!

[mc7719]

Hmmm. I've installed the 237 unit in my Sierra with no issue with the caller ID. I imagine it would be the same as your Tahoe. Could it be a loose connection of one of the three plugs in the back on the VCIM? are the J1, J2, etc plugs in the right sockets? Besides checking your connections, I would say it might be an internal VCIM issue.

[jmitchell]

I will pull it out and recheck the individual wires, but I know each of the J1, J2, etc. plugs are in the right place because if you look closely the female ports are each uniquely different so you can't mess it up. Funny thing is, I had it temporarily placed near the floor and it worked flawlessly for 4 days, then unplugged the unit to fish wires and place module in its stock location and now I have the Caller ID issue. Very strange.

[jmitchell]

Quick Update:

 

I swapped out the two units today and found that the steering wheel button of the Nav vehicle is indeed an issue with the vehicle as the other VCIM had the same issue with that vehicle. We have a 2011 Nav disc on its way and hopefully that will remedy that problem.

 

As for the Caller ID on the non-Nav vehicle, I did not have a problem with Caller ID with the #20827036 VCIM (even though I only checked it twice briefly) but after re-installing the #20756237 VCIM, I once again am not getting Caller ID on the DIC. I am trying to send this back to rev281 tomorrow and will report back with a different unit when I get it. I have requested a swap for a #20827036 VCIM and hopefully that will remedy the problem.

[~kyle]

I'm sure you've probably checked already but just in case, did you check to make sure that your cell phone is compatible with the factory system?

 

http://www.gm.com/handsfree/index.jsp?bran...mp;landing=true

[jmitchell]

Yes sir, I have. It does connect, make calls, and caller ID works some of the time but I would say at least 50% of the time caller ID doesn't work. All other features work flawless. Going back today for an exchange with the other 20827036 VCIM.

[leverlution]

Yes sir, I have. It does connect, make calls, and caller ID works some of the time but I would say at least 50% of the time caller ID doesn't work. All other features work flawless. Going back today for an exchange with the other 20827036 VCIM.

 

 

Probably wont help you all, but just an fyi. My stock 2010 with OEM bluetooth does that. Both with my Droid 1 and Droid 2. A lot of the times its blank, doesn't show the number. Most of the time when I get an INCOMING call it shows, but not always. Most of the time when I make an OUTGOING call it Doesn't show.

 

Like I said, probably wont help you all, but thought I would add that info just in case.

[jmitchell]

Have you tried to troubleshoot it yet? Sounds like we have the exact same issue. I have a Blackberry Tour (Verizon) and wife has iPhone 4 (AT&T) both of which have the same issue with the caller ID. I will report back with the new unit to see if that makes a difference. If so, maybe with yours under warranty you could get it replaced by GM.

[leverlution]

Have you tried to troubleshoot it yet? Sounds like we have the exact same issue. I have a Blackberry Tour (Verizon) and wife has iPhone 4 (AT&T) both of which have the same issue with the caller ID. I will report back with the new unit to see if that makes a difference. If so, maybe with yours under warranty you could get it replaced by GM.

 

To be honest, im pretty anal about stuff but its never bothered me enough to care. Had I known this was an issue with you all, I would have had them take a look at it. I figured it was just a litttle buggy and since GM doesn't allow onstar to do any over the air updates, it would prolly never get fixed anyway. Its actually at the dealer as we speak for maint 1 and some BS squeaks (doors creaking on rough roads, and I had a weird grinding noise under the bed for about 10 miles anytime I hit the brakes hard but it went away). Im leaving for St Louis next week, wont be back for 2 months. Not sure when I could take it in for you all

[dfs41]

I thought I'd throw my 2 cents worth in here as well.

I have spent the past few years working to get a decent working bluetooth hands-free system for my 2007 Suburban. After taking advantage of many of the posts here over the years, I figured I better give a bit back!

I have used a few different 'set ups' over the years (cig-blue, bluefusion) that have worked with sometimes acceptable communication quality and assorted vehicle electronic glitches, and have recently switched to the 20827036 bluetooth vcim.

As documented here in this thread, the vcim swap was relatively simple - just a bit of a challenge getting the original module out of the truck. Hook up and reassembly was as easy as noted.

The 2007 Suburban and the 036 proved to be a little different to 'pair' than some of the other modules that were listed here. Pushing and holding the 'talk' button didn't allow direct access to the bluetooth set up. Other searching through the Cadillac site tipped me to pushing the blue 'phone' button on the rear view mirror once, then pressing the 'talk' button on the steering wheel twice. I then was able to say 'bluetooth' and continue with pairing my iphone.

Since then I have played around with the system, and after holding the 'talk' button on the wheel for a couple of seconds, I can say 'onstar', and then when the system announces 'onstar ready', I can say 'bluetooth' and access the bluetooth functions of my iphone. One thing I did stumble on, was that the voice dial feature of the iphone could be accessed without having to set up any of the 'voice tags'. By following the above sequence to access the bluetooth functions, I can say 'voice'. The system then accesses my paired iphone, and prompts me for the name of the call recipient - as per the usual operation of the iphone.

Without question this vcim swap is the most pleasant sounding hands-free set up to date. Operation is great, and sound quality is even better - even at highway speeds.

The only potential challenge is that a day and half after install, and about a 6-10 ignition cycles, the radio (nav) displayed 'xm theftlocked' on the screen. The warning went away when I changed xm stations, and continued to play all the xm stations, but it did get my attention. I have since cycled the ignition sequence about a half dozen times - most with the warning and continuing to play the xm. I don't know whether this is due to the change of the vcim, or the disruption after removing the bluefusion from inline with the xm module.

I'll let you know if the warning continues or (hopefully) settles back into standard rhythm. For the record, it is the original factory navigation head-unit, and the original factory xm box.

Also, I have no interest is getting onstar to hook back up with this. I was fully aware that it probably wouldn't, and was prepared to trade an unused onstar for quality hands free.

Many thanks to everyone here that pushed to et this sorted over the past years. A great site!

[Brewboy]

Hey guys as someone who has done this mod I just wanted to remind all the new people trying this that On* has come out with the entire On* and BT system in a new add on Rear View Mirror.

 

Its plug and play, purchased through Best Buy this Spring.

 

I think its $299 + monthly On*

 

Just another option for those not wanting to do the VCIM swap and loose On*

[csester]

Hey guys as someone who has done this mod I just wanted to remind all the new people trying this that On* has come out with the entire On* and BT system in a new add on Rear View Mirror.

 

Its plug and play, purchased through Best Buy this Spring.

 

I think its $299 + monthly On*

 

Just another option for those not wanting to do the VCIM swap and loose On*

 

Can you tell me more about this or where I can find info on the net? I would love to have BT, but dont want to loose my On*

[Brewboy]

Hey guys as someone who has done this mod I just wanted to remind all the new people trying this that On* has come out with the entire On* and BT system in a new add on Rear View Mirror.

 

Its plug and play, purchased through Best Buy this Spring.

 

I think its $299 + monthly On*

 

Just another option for those not wanting to do the VCIM swap and loose On*

 

Can you tell me more about this or where I can find info on the net? I would love to have BT, but dont want to loose my On*

 

 

Check out the story here

 

I know it says NON GM VEHICLES but it is going to include GM vehicles without On* as well.

 

http://www.leftlanenews.com/ces-gm-to-offe...cles-video.html

[lamontqsanford]

hi all

i'm new here i read 90% of these posts very cool stuff i really like to do this mod i have an 2008 sierra with nav/bose i have a aftermarket blue-tooth witch sucks.would love to do this mod so my question is what do i need

 

20783877 -- VCIM for models (w/ bose, nav & bluetooth)

15938939 - BT antenna

25851951 - Switch -

 

i have a factory wheel switch are these the same also do i still need to have it reprogrammed i don't care about on star? I'm ready to order it .I'm off work the week from Xmas's to new years this would be a good time for me to do this

 

thanks

 

looks like your parts are right but most dealers wont sell you the VCIM as its restricted by GM

 

Only Fire, Theft or Warranty claim with a 2009 or newer VIN will be accepted. Ebay is your best bet.

 

When you buy the steering wheel switch all you are really paying for is the symbol painted on the switch, your older switch will do the job.

 

Maybe buy that later if you really want it.

 

 

New to this particular forum, but this seems to be the most comprehensive (or at least longest) thread pertaining to factory BT conversion. I just finished repairing a 2007 NBS Crew DRW Sierra and now that I'm driving it daily, decided to search for some BT integration options, and luckily I stumbled accross you guys. I've scanned most of the thread and it appears that success rates with this conversion have some disparity, so I want to offer to do my conversion in a manner that helps prove or disprove any solutions if I can. Also, I would have ended up buying a Scosche instead of trying this if it hadn't been for you guys.

 

It is an SLT, but does not have NAV. Of course it has On* and the audio is the US9(6CD with MP3 input jack). I have recovered a VCIM module 20783877 with the BT antenna from a wrecked 2009 Silverado2500 that I have. The wrecked 2009 that supplied the VCIM is owned by my company, so I have all pertinent VIN data if that is somehow necessary. My 2007 does not have a paid On* subscription, but I can connect and the system appears to be completely functional. I don't know if the 2009 had a paid and active On* acct, as we purchased the vehicle from auction and not the original owner.

 

Would those who have been heavily involved in monitoring this from start to finish like to have me attempt the install and/or reprogramming (via dealer or On*) in any particular sequence to try and ferret out any of the mysteries of why it(ON*) sometimes works and sometimes doesn't. I have a favor I can call in with one of my dealers if I need to, but it might be a week or two before I could make that visit.

 

For myself, I don't care about having On*, but when I sell this in a year or two, it would be nice to have everything correctly functional, or I'd swap the VCIM back to the original. I do use XM and I haven't seen any related issues in these posts, but want to make sure I don't "break" anything with that.

 

I appreciate the resource developed here and hope I can contribute a bit more.