Phone kit problem

[SHAUNE55]

Yes, do the SAPV2 test its a good enough way to test the car's phone system.

I've seen this issue before when the Viseeo wasn't pushed onto the UHI connector properly, it has to go on until the locking mechanism holds it in - sometimes thats quite a hard shove. (the driving around vibration causes some of the connections to disconnect, but as long as there is power the viseeo will stay on and paired with the phone)

R

I agree with that, I have to shove mine in with a bit of force quite fast or it doesn't connect properly even though it gets power to pair up with my phone.

 

[Pev]

Many thanks to Richard, Alfie and Shaune55 for your help with this. Of course it's a little early to be convinced of victory but the thought of the bluetooth issue finally being solved is too exciting not to post. I took Richard's advice and removed the unit, gave the contacts a blowing out and replaced it very firmly - to the point where I worried I was going too far. I yanked it back and forth to ensure it was locked, and I've enjoyed a full day of problem free bluetooth connectivity. The idea of it working perfectly stationary and getting disturbed by motion vibration does fit the symptoms, and I doubt I ever would have thought of that myself!

I've added a separate bluetooth unit for streaming music (connected to aux-in), and for the benefit anyone contemplating a similar setup with an android phone, I downloaded a free app called "choice dialer", which allows me to press the voice dialer button on the MB-2 and speak "next song" to handle song skipping plus some other redundant commands. Combined with PowerAmp for music playback I can get in the car with the phone in my briefcase, music plays automatically, voice commands to skip or pause (or theoretically request a particular artist etc but not very reliable), and music resumes after a phone call. Currently using a dodgy bluetooth receiver while I wait on a replacement Griffin Bluetrip to have everything fully concealed. Really hoping I can find an L-shape audio lead that will allow the cigarette lighter lid to close with the Bluetrip installed and operating. I was shocked to see the MB-3 had aux in but not aux-out!! If instead of the fm transmitter they had aux-out that would be a sweet device. Oh the lengths I must go to simply to comply with the law...

Thanks again for your help and putting up with my cranky outburst Let's hope the victory dance is not premature. For the record Viseeo's support team did get back to me on the next business day.

 

[SHAUNE55]

Pev....Glad you are having success.
I bought an adaptor for the cig lighter so I can plug three things in and to get round the ashtray lid closing problem I cut the plug off and wired it to the back of the cig lighter and have the adaptor at the side of the console and nothing plugged into the cig lighter.

 

[Pev]

Well for completion, I'm sorry to say the success was shortlived. Seems Shaune55 and I share a common foe. For now it's with the viseeo support team, I'll post a new thread if I get any more info, but as it is I just need to keep an eye on the dash for "no phone" and press the TEL button to wake it up again - seems very intermittent. I'll follow Richard's advice and try my SAP v2 with a sim in it to see if I get the same behaviour, hopefully that should isolate which side the issue is on.

But still, many thanks to the forums here for your efforts.

 

[nickwalk]

Hi all

It seems the same problem persists with the MB4 as I have exactly the same issue that when you plug the device it powers on and connects to phone and Viseeo appears on the display. Next time you get in the car the unit is dead with no power and no phone is on the display!

Done the firmware upgrade and give it a hard shove when plugging in but no luck and now really begin to annoy me!

Any ideas before it gets thrown in the bin?

Thanks

 

[npuk]

It could be a faulty viseeo or problem with the cars UHI, you need to try another cradle so you can check where the issue is.

 

[Pev]

From reading other people's similar experiences I've concluded that this is just a common fault of viseeo's and I wouldn't personally buy another without warranty. The car-side is definately fine for me, SAP works both with a SIM and using a Galaxy S it also worked with rSAP protocol (however useless fora smartphone since the phone's sim is disabled and therefore no data for emails etc). But in any case, I've isolated to the viseeo itself, and with the support asking for lots of irrelevant information I'm a bit loathed to go through all of that with little chance of anything but advice to buy another.

One difference between my and nickwalk's symptoms is that with mine the viseeo is fully on and functioning, it's simply the connection to the car that's broken. This has the painful side-effect of the phone thinking everything's great and letting bluetooth handle the call but no sound and no mic.

If I had my time over again, with the amount of wasted time, money and stress on this, assuming I kept the car I'd just fork over the marginally more cash (in hindsight) for a dynavin head unit. But that said their both made in the same region of the world so who knows.

Bluetooth is a sad stain on this otherwise awesome vehicle!