VAIO Z1 to Mobile Problems!

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › VAIO Z1 to Mobile Problems!

1 | 2 | 3

11 posts

Geek

#622 11-Jul-2003 02:31

You could try a different version of Bluespace I guess.

The fact is that FloAt works fine through Bluespace, so if I was going to point the finger it would be at the Sony Ericsson. How come they can't get their software to work when someone else has? Seems like they are just trying to pass the buck onto Sony Vaio to save them debugging their own software.

Personally, I'd like to Sync my phone with my desktop PC which only has the native XP Bluetooth driver (as I have a Microsoft Bluetooth dongle). The Sony Ericsson software doesn't even pretend to support that!

Here is an interesting quote from the front page of the Extended Systems website:

Sony Ericsson's Communication Suite must be installed prior to running XTNDConnect PC. The Communication Suite is developed by Sony Ericsson and is responsible for establishing and maintaining the communication layer between XTNDConnect PC and your Sony Ericsson phone. Although XTNDConnect PC is fully compatible with Windows XP O/S, Sony Ericsson's communication suite is not fully compatible at the present time. For any problems connecting or maintaining a connection to your Sony Ericsson phone from a Windows XP workstation, please contact Sony Ericsson support at http://www.sonyericsson.com/support.

Obviously they have been overrun with complaints from people who got XTNDConnect bundled with a Sony Ericsson phone...

freitasm

BDFL - Memuneh
80652 posts

Uber Geek
+1 received by user: 41044

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#626 11-Jul-2003 08:48

I use XTNDConnect with my T39m and it works very well. Mind you I have a TDK Bluetooth on my desktop.

I've received the T610 for review a couple of weeks ago and I'm not getting this phone. I couldn't connect and keep a Bluetooth connection. I tried my iPAQ H3970, my desktop, my laptop (all different Bluetooth devices). The T610 connected ok, but only the first one. If I disconnected and tried again, I was required to power off and on the mobile, and pair again!

Perhaps you should check the mobile phone and perhaps declare it a bad product, like Mobile Burns?

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

StuWhite

11 posts

Geek

#630 11-Jul-2003 10:03

Interesting you should say that. I have had the same problem with losing bluetooth on my Vaio every so often and needing to shut everyting down before reconnecting.

I haven't had that problem at all on my desktop when using my Microsoft dongle and the native XP bluetooth stack. I have had FloAt connected for the last 12 hours continuously without dropping off. I can manually disconnect and reconnect without a problem. Perhaps the T610 has a problem with the serial connection set up by the TDK driver and Sony Bluespace?

Perhaps there is nothing wrong with XTNDConnect. I think it's the SE Communication Suite that is rubbish. Hopefully they will either improve it or slap a label on the box of the T610 which reads "WARNING: Not Compatible with Microsoft or Sony Bluetooth Software".

The Mobile Burns review was interesting. He said that the ability to keep a signal in the US was poor and thought this may be because it was tuned for Europe. I can assure you it is pretty poor in Europe as well (the UK anyway). I was a little upset to find I can't get a signal in places with a dodgy signal when others with old cheap phones have no problem...

peterpan

8 posts

Wannabe Geek
Inactive user

#642 12-Jul-2003 02:09

Latest news from germany ;-):
I had a 70 minutes phone talk with Sony second level support. Now they blame the phone itself. The problem should be that it is unable to provoke a bluetooth-pairing from its side. I at least always tried to pair it from the notebook side and get an authentification from the phone. They bet it WOULD work if it was possible to establish a connection from the phones side, which was not possible. Now the are "escalating" the case and promised me to call every day to give me an update. Todays call said: We are still working on it. No further results. Next call on monday...

peterpan

8 posts

Wannabe Geek
Inactive user

#697 17-Jul-2003 23:24

Vaio Link called this morning. There is a Bluespace NE / Bluetooth driver update available which fixes our problem. I havent tested it yet but if there is any interest I will send an update about that shortly.

JimmyMac

3 posts

Wannabe Geek

#698 18-Jul-2003 01:35

Just to let you guys know... I had EXACTLY the same problem with my Z1SP & T610.

I installed the new driver updated, it didn't go smoothly... the update requires your machine to reboot a couple of times, my machine got caught up in an infinite loop! Everytime I booted up... the previous installation process would continue.

Clicking cancel on each startup paused the installation... My mahine had problems with uninstalling the Virtual com port and would force my machine to restart.

After manually uninstallung the bluetooth driver this seemed to have fixed the problem. I can now sync with outlook using my T610!! woohoo!

Bluespace seems to be behaving excatly how it should...

Now I'm very happy.

enjoy!

Please feel free to email me if any of you guys have a problem.

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

StuWhite

11 posts

Geek

#699 18-Jul-2003 01:42

Yay! The update seems to have done the job. I didn't have the 'infinite loop' problem.

mateypeeps

4 posts

Wannabe Geek

#702 18-Jul-2003 04:38

Hey guys,

First off, where does this patch live? There's no sign of it in the official download page on Vaio Link Europe?

Second, the update on my bug report to Sony. After 3 days, I got an email back saying that my problem had been solved. I logged onto the support site to find out the result, and was told (SURPRISE SURPRISE) that I needed to reinstall the t610 desktop software.

I responded with a long list of URLs that demonstrate the frustration that many people have had with this problem. So far, nothing - not even a whiff of this patch you refer to.

Anyway, if you can get me that info, I can solve the problem for them!

StuWhite

11 posts

Geek

#703 18-Jul-2003 05:24

Try http://www.vaio-link.com

You'll need to enter the serial number of your machine. It was written on the bottom when you bought it but (if you're like me) was probably scratched off within the first 2 weeks so is now illegible. You'll need to spend time searching around in your registry to find the copy kept there, as Sony won't let you download anything without it.

If, like me, your serial number is not recognised by Sony for the purpose of registering your product, don't worry, the support website does seem to recognise it...

On the subject of Sony Ericsson support. They sent me an email 13 days ago saying that a technical advisor will be contacting me within 48 hours. I haven't heard from them since...

JimmyMac

3 posts

Wannabe Geek

#705 18-Jul-2003 06:53

the new update can be found on the vaio-link website.

the ftp link is:
ftp://ftp.vaio-link.com/pub/vaio/bluetooth/Bluetooth_Update_102_Z.exe

info about this new update:
http://www.vaio-link.com/UK/info/Bluetooth_Update_102_Z.htm

hope this helps.

chriscaller

5 posts

Wannabe Geek

#711 18-Jul-2003 21:51

Thanks for all your efforts on this everybody.

Unfortunately I'm still having trouble synching with XTND Conncect. Here's what I've done:

1) Checked that my Z1 is running WinXP SP1. Removed Bluetooth Virt Com Port, then Installed the BT patch from VIAO-link. Rebooted then completed the installation.

2) Re-installed SE Comm Suite, rebooted.

3) Tried it all out after successfully performing Device and Service discovery on BlueSpace NE, but no joy - communication errors so that XTND Connect can't see the phone & am unable to configure either Outlook or Phone on XTND Conn.

4) Tried Floats Media Control and can get a connection - with errors. Am able to download phonebook & txts, but synching produces an error 303...

5) tried removing BT Virt Com Port again, then re-installing the BT patch. Tried reinstalling SE Comm Suite. Only thing I've not tried yet is re-installing BlueSpace NE from the recovery discs... Will be trying that next

If anyone has spotted that I've missed something or done a no no, could they let me know?

Thanks all,

Chris

Dell

Shop now for Dell laptops and other devices (affiliate link).

peterpan

8 posts

Wannabe Geek
Inactive user

#712 19-Jul-2003 00:53

I need help again -
as I said I tried the famous update on my Z1, BUT I still have one problem. Phone monitor does not find COM4. (re-installed BT driver / Virtual COM etc. - no success at all)

Surprising to me: I did the same on my girl-firends Z1 (same configuration) and everything is working smoothly. Its almost perfect - syncinq and dial-up functionality is stable.

Conclusion: Something seems to block COM4 on my Z1. Please - has anybody got an idea what this could be or how I could figure it?

THANKS1

mateypeeps

4 posts

Wannabe Geek

#713 19-Jul-2003 02:18

Hey Peter,

Perhaps you could list what you've gone running on your laptop that your girlfriend does not?

I'm going to try and apply this patch later and would like to know what apps may be causing problems.

JimmyMac

3 posts

Wannabe Geek

#714 19-Jul-2003 04:26

"Only thing I've not tried yet is re-installing BlueSpace NE from the recovery discs... "

but the new patch should have uninstalled Bluespace... and then reinstalled v3.1.00.04240
Did this not work for you?

chriscaller

5 posts

Wannabe Geek

#715 19-Jul-2003 04:36

JimmyMac

I presume that it did, as I was able to use Bluespace NE after installing the patch.

I just mean that in my desparation I've tried re-installing everything else to get it working, but without any results so far!!

When I installed the patch, as far as I could tell everything seemed to install etc as it should - however the acid test of actually getting it to sync failed and failed again... :(

Chris

1 | 2 | 3