Just a quick update, our engineer is not sure what is going on (Hi Fred, definitely a wierd one. Got **** on it and will let you know as soon as I can. may be phone related too where something won't let go of the bluetooth connection. don't know yet. dang - wish I didnt sell my cts-v..) and has forwarded the issue to the lead engineer. I did respond back and let him know it was doing the SAME thing in my Avalanche. At least I know I'm not crazy and it was not doing this before!
That's kind of strange. I don't see what variable we all share that could have changed recently.
I will say that I continue to be pleased with the performance of the unit. I'm glad you guys used premium components. I used it with my windows down again and while the caller can definitely hear that I am driving with my windows down, I can still carry on the conversation. Pretty amazing, since this is beyond what is realistic for a usage scenario. I guess keep the thread updated as your engineer figures things out.
does installing this take anything away from the functionality of OnStar?
it takes away ALL the functionality of onstar. You have to unplug onstar to plug in the Galaxy box.
Just to keep you updated, the plot thickens more! I just hung up with a customer (he wanted to thank me again and get advice for a new phone) that has a 2007 CTS without NAV. When he shuts off his car the phone immediately disconnects from the Galaxy 1000. His unit was purchased around the same time as yours and was from the same "batch" as yours. I'm really scratching my head over this one now!
Yeah I think it's my car. Not a malfunction, just a design subtlety. Thanks for the update.
The plot thickens, they bench tested a few units and had the same result you have. I do not understand why/how the other gentleman is not having the same result. I received the following back a few minutes ago;
" I think we found the bug in the sw that caused the phone not to get the call back when shutting the car off. You can test my theory if you want. When in a call, shut off the car, then turn the ignition back to accessory and then back off. I bet when you do it a second time it goes off and transfers to the phone. We are working on it now...."
If you could try this and let me know,
Do I kill RAP (open the door) before cycling the ignition back to accessory first?
No, just turn it back to acc and then back off
Ok I'll try. That's interesting because power to the unit won't change, but I guess it reads a state off the bus and shuts down accordingly. I'll let you know what happens.
I tried doing it exactly as you said and it made no difference. When I opened the door to kill RAP, it did the screen-stay-on thing at which point I turned the key back to accessory and back off and the nav screen immediately went off and the phone call was back on the handset. I did this while the door was open. This is what I thought your engineer meant, and I think this confirms his bug. While we're talking about bugs, I've also seen the system pause audio and light the OnStar indicator as a result of me turning bluetooth off on my phone (not in call). This has happened a few times, but isn't consistent. I am willing to assume it's the phone somehow, but I thought I'd mention it.
Thanks for the input. I'm sorry for the crossed signals. The Onstar system itself may be looking for a phone when you turn off your bluetooth and therefore flash the audio. I know if I forget my phone the Galaxy will still pair to it as it is usually on my desk which is only 20 feet from my truck, then as I get down the street I hear a beep and the radio does "flash". This has reminded me on more than one occasion to go back and get my phone....
We were able to isolate the problem and correct it. I will be in touch with you to make arrangements to take of you.