my universal replaces my laptop, my blackberry, and even my widescreen tv (to some extent) not to mention does all these other neat things (i never seem to play games though i have several RPG's loaded).
BUT
I have had extremely bad luck printing with the Universal. I have (2) H4355's that i use for my GPS; that work with both printboy 7 and the clearvue apps quite reliably with my HP 460 (both bluetooth and WIFI cards). but the Universal is so hit or miss. if i'm lucky a softreset followed immediately by printing has worked but - that's an idiotic proceedure to have to follow (although i will do it....)
I have done all my experimentation on the QTEQ ROM with radio 1.13 with a hard reset and JUST the cleavue apps loaded. and it's still flakey.
is anyone having any luck at all better than me? ever since the SIPIX prect printer came out i've been obessed with being able to print. even if i could use a spare H3455 as a print server somehow. i's a pathetic obession but i really, really, really what it to work.
any ideas?
Related
Has anybody managed to get the smartpad 2E working with xda? wwwsiibusinessproducts.com
i got it working with the xda2 with out a problem
I have a Seiko InkLink, which works fine with the PCA over USB, but I can't get the infra-red clip-on to work with the XDA2.
I've gone to connections and made sure that "Receive Incoming Beams" was checked, and I've fooled around with changing the COM ports (which one is it supposed to be?), but aside from that, can't think what else to do. Anyone any ideas?
Oh, and another thing.
When I run the InkLink software, the XDA soft-resets itself after a few minutes. If I don't run the InkLink software, it runs fine, so I strongly suspect the software isn't quite right.
This is all on the XDA2. I haven't tried with XDA1. Maybe its a WM2003 thing?
i have the same problem. it works with the desktop but not the xda2.
The ir lights up on the device that clips to the top of the A4pad and the light changes speed when I write but nothing appears on the XDA2 screen. I have tried running the test program but I get a message stating the IR port (i assume it means the XDA2 port) is being used by another program but I dont have anything else running in the background.
receive beam is turned on - i have tried it both on and off. My XDA2 has reset itself a couple of times since installing the software - so i have given up and removed it.
i wonder if there is another program installed that is effecting things.
any clues ?
There is something screwy about the irda on the xda1 and the xda2, if you install tomtom2 on the ipaq and look for the ports available, you see the com ports and also generic infrared port, I have an infrared adaptor which allows me to use gps on ipaq 1910 which doesnt have a serial port, however trying to do the same with xda, all thats offered is infrared port, choose that and the machine locks. I wonder if other pda's besides xda1 and 2 allocate the irda to a virtual port. I have asked about this numerous times here on the forum and scoured the web but to no avail.
After various teething problems, it now works flawlessly on my XDA2, and I'm really very impressed.
I've no idea why InkLink was resetting my machine, but I think maybe it was because I had the wrong port selected and it was just picking up rubbish from an unconnected port. Still shouldn't crash, but anyway, it works if you connect to the right port.
Also, I think the batteries they supply with it only last 5 minutes. Having replaced them, my troubles seem to be over.
Only fault is the general hassle factor of the IR clip. If there was a bluetooth version, it would be so much better (provided the bluetooth worked!)
onepieceman said:
After various teething problems, it now works flawlessly on my XDA2, and I'm really very impressed.
Click to expand...
Click to collapse
I'm dying to know how you made it work?
I don't think I did anything specific.
I think the most likely thing was I finally selected the correct COM port. You need to select COM1, and this won't be available if you have something else using that port (such as the "receive beams" application, but maybe you have something else). Just to confirm, "receive beams" must be OFF!
Also, make sure your batteries are OK.
I suggest you get it working first with the InkLink connected via USB to your PC. If that works, then you can be sure that the pen and the InkLink clip work OK. That will then leave the IrDA transmitter, its battery, and the PocketPC hardware/software/config as sources of potential trouble. I can vouch for the software working on an XDA2, so that should just leave the IrDA transmitter and its battery.
Oh, just forgot, I did download the latest version of InkLink from the Seiko site. My version is 3.3, while it came supplied with 3.2. Don't know if it makes a difference, but worth a try. Also, make sure you select InkLink as your hardware. I believe it defaults to SmartPad.
Can't think of anything else you need to do. You certainly don't need to do anything weird.
hello all-
i am stubbornly trying to get my ppc-6600 to be able to browse network shares. i can FTP and activesync to my hearts content via bluetooth, but network access only works once and then flakes out, requiring a hard reset to work again, thus eliminating any convenience of wireless connections. i have tried various stacks from this forum, with little success. i am currently running the toshiba stack, but i can hardly tell any difference, because the "about" section in bt settings still refers to broadcom. however, i do have a new option in network cards that is toshiba.
anyway, is there anyone who has had consistent success with this on a phone like mine (blue angel?) i have seen some references to some other models, but not this one.
tia!
okay, so i take it i am the only one with any interest in this??
I have a BlueAngel / SX66 on Cingular. I have been through every ROM upgrade you can imagine, all with the hopes that SOME DAY the bluetooth will work properly. More specifically, I have a stick BMW and it's impossible for me to talk on this thing and drive at the same time, not to mention really unsafe, but I absolutely need to talk in the car because I'm on the move a lot. There is a bluetooth headset interface in the car that I know is pretty damn good because it works so beautifully with Motorola devices (specifically the somewhat ancient V600 I have). My SX66 can barely get through 3 seconds of being connected to it before it just goes haywire and drops the connection, locks up my stereo, etc. It's a disaster. So every time a new ROM comes out I sit for hours upgrading just hoping that maybe this time it will work. I've tried a Motorola HS810, HS850, a Logitech Mobile Freedom, a Jabra BT800, and an Ericsson HBH600. Not one of them can consistently hold a connection without it dropping here and there and me having to go to the Bluetooth manager and "reconnect". These are all reputable headsets that work flawlessly with other devices.
Conclusion: The MS bluetooth stack is pathetic.
Problem: I want my SX66 to work with JUST ONE bluetooth device flawlessly. It doesn't need to be the car necessarily, but that would be really sweet if it did. I have recently upgraded to WM5 in another feeble attempt, but alas WM5 doesn't appear to be compatible with GoodLink, the messaging sync software that I'm tied to that makes me use this god awful device (I won't use a Treo because the Palm UI is garbage and it has its own host of problems I've seen). I'm going to have to downgrade back to 1.40 to get GoodLink to work again because its pretty vital to me.
Question: Does anyone know how to get Bluetooth to work consistently with any headset, paired with an SX66? I seriously have sank like $400 just in headsets trying to get this piece of crap to work. If there are any stack upgrades, firmware flashes, etc. WHATEVER I'm willing to try anything. This is the only Windows based device available on the market that is compatible with GoodLink and has a qwerty keyboard that's easy to use.
FYI, the BA uses the Broadcom/Widcomm BT stack, unless you've upgraded it to WM5.
Well i bought a hMotorola HT820 and i have done a lot of searching on here and cant seem to find anything. When i turn on the headphones and go into the vista wireless set up it finds the unit well. it will pair it up and say that its working just fine. but when i go to play a song it will not work. does anyone have any advice. i am so nervious looking on google for a other hour and it just not working at all . please
d
can anyone offer any help?
Hi there, since I don't have any computer with windows vista, I wouldn't wanted to answer, but, since I also have been int this situation (when I asked for something else), well, here we go.
In your place I would first test the headphones with another computer, at least one that doesn't have vista, XP is well proven with bluetooth devices, as long as you do follow the exact instructions of the external BT dongle (if this is the case), why? Well XP stack does not work on many BT devices, so the maker of those, warns and explains you how to disable XP drivers and how to install theirs.
I've tested my HT820s long time ago, with a USB BT dongle (about 9 euro) and they worked the best I ever heard (considering that I bought them from a chinese Ebay seller and I'm pretty sure that they are a fake, or should I say, a copy of the original), the stack used for this BT dongle is a very well known one, the bluesoleil stack.
Then, you could pass on and try with vista, check your BT interface maker's site, check (if any) vista driver updatings, etc.
Hope this helps.
After much searching and Googling, I'm a bit stumped.
I'm currently running VP3G's 2.0.1h variant of the WM6 ROMs, and A2DP works beautifully. So does CoPilot / MSN Live Search / Google Earth with Bluetooth GPS. But together? Skip goes the audio.
Some playing with the BitPool setting got me more or less audio before the skips. The BlueTooth GPS is the one that comes with the CoPilot bundle, SirfSTAR III, running at 4800 baud. Fairly standard fare. The A2DP headset is the Sony Ericsson HBH-DS970 headphones. Ideally, I'd like to be able to use it for satnav - you've guessed it - via the bluetooth headphones.
I haven't tried installing the Widcomm stack yet, although that's next on my list. It'd just be nice to do it "natively" with the WM6 bluetooth drivers if possible.
Thanks in advance!
The Hermes has a hard enough time just with A2DP, co-existing with a BT GPS receiver will be really pushing the device's capabilities. You can try installing Sleuth255's A2DPFix v1.0 which does a really good job of fixing A2DP issues in general, but I suspect that you may be asking too much from our poor little devices...
John
Well, installing the Widcomm stack solved it hands down - whilst it seemed to use a little more CPU, it worked fine with the bluetooth GPS and the bluetooth audio, with the satnav application broadcasting audio via the headset.
I'll try the A2DP fix, and see if it does any good with the MS stack. Still, at least I've got a way around the problem now!
N2A said:
Well, installing the Widcomm stack solved it hands down - whilst it seemed to use a little more CPU, it worked fine with the bluetooth GPS and the bluetooth audio, with the satnav application broadcasting audio via the headset.
Click to expand...
Click to collapse
Interesting! I have always considered the Widcomm stack to be miles better than the M$ one (even though M$ has made quite some improvement recently), but just never had enough time to really play around with it to get it working on my TyTN. There was an effort started late last year to raise $500 for the first person to release a working version of the stack, but unfortunately it fizzled.
This might be enough to get me to try again. I am going on vacation for two weeks starting Sunday, this would be a good project for a rainy day -- I am going camping, it always rains when you're camping!!
John
Oh, absolutely, it wouldn't be a camping trip if it wasn't pouring down
After playing around with it some more (using the 0.3 version from the thread), it seems a bit flakey, sometimes failing to update properly, but I think that's more down to CoPilot than the stack - MSN Live Search and Google Maps seemed to work just fine when I was listening to my music. Nothing fancy on the music score either, just plain old Windows Media Player. A lower CPU usage program might help the satnav program - I'll try some alternatives shortly.
The A2DP fix made no difference at all, although I suspect that's mainly for the awful MS implementation on WM5. I haven't really noticed all that much difference in sound quality between the two stacks, although some people rave about the Widcomm, but maybe I'm just not as attuned as some people
There's no doubt that the Widcomm stack is better than the MS one, although it's not without it's apparent issues of course. I tend to use the MS one for general usage and the Widcomm if I need to do more than one bluetooth thing at once. Seems to work for now, although I need to put it in more heavy testing.
Both stacks give the odd skip, but I tend to think that may well be down to how much CPU usage I'm pushing out of the poor little thing
The problem with the Widcomm stack being ported properly was that it wasn't really organised all that well. If someone steps up to the podium, I'm pretty certain people will pay for the functionality. It's just finding someone with the skills and time to do it!
Give it a try, although beware of the potential caveats - reading up on the thread is recommended.