OESF Portables Forum
Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Accessories => Topic started by: andreino on October 13, 2004, 06:30:37 am
-
hi, I have bought a dikom bluetooth cf card that is a windigo card
(manfid: 0x0279, 0x950b - btuart_cs) (http://www.windigosys.com/) that
look to be the same of a Cyber-blue card
(http://www.cyber-blue.com/english/product/cfcard/cfcard.html).
I have a sharp zaurus 5500 with original sharp rom 3.13.
I have installed bluez (I tried a lot of versions from 2.3 to 2.7) and always have the
same problem:
zaurus freeze when after connected I am loading a page with opera and at the same
time I touch the screen... so I have to do an hard reset.
Look like if I do not touch the screen whan loading/transfering all is ok.
Can you help me ?
I have no problems with hictool scan
I have no problems doing rfcomm 0 MACADDRESS 1
I have no problems connecting to gprs service
looks like other service like jabber give no problems
I have also tried with serial_cs and hciattach and bcsp/csr/etc but I always get an error
message (can"t initialize ..... )
thanks
bye
andrea
-
Have you tried the packages pointed to here:
http://www.zaurususergroup.com/modules.php...ename=Bluetooth (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=Bluetooth)
If you have got a connection working at all, then you are probably using the correct driver and settings.
I've not heard of a problem like this and have little idea of what it could be. The pcmcia interface on the Zaurus seems a bit flakey to me and I have locked my Zaurus up on several occassions just by pulling out my Bluetooth CF card at the wrong time. Perhaps there is some dodgy memory stuff going on with your card?
-
Yes I have tried the packages pointed there.... no problems with the connection....
Last time I have tried surfing without touching the screen when the led was blinking without freezing the zaurus... but when I touch the screen and opera is downloading a page... I have to do an hard reset... :-(