Hi,
I have a HTC Touch and have used it with several nav-programs and a bluetooth mouse. Works fine.
Now I bought myself a second GPS receiver as I did not want to carry it around (now I have one in each car)
however, I can't configure them simultaniously.
What I mean, they are both coupled with the phone.
One is coupled to the com port (6&7)
I can not couple the new one to a com-port without "uncoupling" the old one.
If I do that, and couple the new one this also works fine.
In basis it works, I just need to make sure the right GPS-receiver is coupled to the com-ports. But it would be nice if they could both be fully installed and the phone picks the one that is switched on......
Anybody know a solution to create this situation
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.
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.
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
tifosi256 said:
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
Click to expand...
Click to collapse
Hi,
I know there are some issues when it comes to Bluetooth and Android, and especially car kits.
Ref (sound quality): http://code.google.com/p/android/issues/detail?id=9888
Ref (disconnections): http://code.google.com/p/android/issues/detail?id=5452
This is supposed to be a fix (I did not get it to work properly): http://forum.xda-developers.com/showthread.php?t=731626
I know that Cyanogenmod has made some changes to their kernel in 6.1 that adresses audio quality (bitpool increased), and I also think that the disconnection is adressed. I'm actually testing it for the moment (6.1RC2).
Thanks very much for your reply - very useful. The link to disconnections that you gave shows someone else with the same car as us (slightly different model) with the same issue.
It's very strange as there are people reporting no problems at all with that car/phone combination.
Unfortunately, I can't try the suggested fix as I don't want to start mucking around with my ROM.
I have a problem with my Volvo and the Desire. No disconnections, but I can't get into the phonebook, using PBAP.
Flashing a MIUI Rom works charming for the bluetooth connectivity, however I'm missing my SenseUI.
Just hoping, praying, some def will include the AOSP bluetoothstack in a SenseUI-Rom
BMW Software update
Hi
I´d try contacting your local BMW workshop, to let them do a reading on your car to establish which software version your car have.
If it´s a rather old software version your car have, I´d suggest that you have it updated.
The software update might be the answer to your problems, and can also explain why other users with the same car don´t have this issue (they might have a newer software version than you).
Remember, this phone is way newer than the car, and also the software in it.
I´d give it a try
PS: Be advised. Updating from very old software to new software might cause "in car-hardware" compatibility issues, and demand new hardware in the car (computer modules ect.), so make sure you talk over which consequences the update could have for your specific car before the update is carried out
Cheers
-Buggi- (BMW workshop foreman in Denmark)
Thanks for that advice. I'll talk to the dealership and see about software upgrades. Fingers crossed!
I have a 2008 530i and my Desire (and my other halfs) work fine, so hopefully there is some newer firmware for yours. They facelifted the cars and slightly changed the iDrive in 2007 though so fingers crossed there is an update that fixes the pre-LCI models with a Desire.
Just for reference, this is sorted out now.
My I-Drive actually broke and I had a whole new unit put in (under warranty thankfully!). Since they were doing that, I begged them for the latest software, not just for the Bluetooth module, but for the system as a whole.
Since the software upgrade, the phone stays connected and everything works great.
The only fly in the ointment is that it seems that for some reason, not all numbers of contacts (or all contacts) make it into the car's phone book (most of them do).
Anyway, for anyone else having this issue, get BMW to upgrade your BT software (or the whole system if you're brave).
I have similar problem when i try to pair the phone with volkswagen tiguan 2010, it says "your phone in not supported"
I'm thinking of upgrading to this phone, one of the main reasons is that my current device, which has galaxy S guts, is not compatible with most bluetooth devices. I like to use an app called blueputdroid that turns my phone into a universal keyboard as well as an ELM bluetooth device that turns my phone into a dyno along with the torque app for my car.
For some reason the way samsung built the bluetooth makes it not work with a lot of these things, I know it's not the apps or 3rd party devices as I use my old G1 now for it, but would much rather just have my main phone be my one device.
Have any of you tested blueputdroid or any bluetooth devices? If not could someone try out blueputdroid with this phone (it's free in the market) any help would be much appreciated thanx!!
Says it has detected unsupported Bluetooth stack.. Install cyanogen Rom, etc.
Thanks, at least this phone is likely to get cyanogenmod support which will fix the problem my SK sure as hell won't
My GS2 works perfect with my ELM adapter. It worked perfect with my Vibrant too. I've never had a single problem with any bluetooth device on either of them.
I've had a lot of bluetooth problems with both my vibrant and now my GS2. Both work reliably with my wife's mini cooper bluetooth but they both have had problems connecting to the garmin nuvi I use for handsfree in my car (and forget about the A2DP on it).
I tried a lot of roms on my vibrant (incl stock) and they did lots of cool stuff but never made the BT connect reliably. Then I came across this thread: http://forum.xda-developers.com/showthread.php?t=795691
I made the suggested change to /system/etc/bluetooth/audio.conf and voila! I finally have good BT with my vibrant.
So I got my SG2 last week, rooted it and found that it also had the bad settings in /system/etc/bluetooth/audio.conf. However it also lacked BLN (backlight notification) and few other tweaks I've come to love on my vibrant so I flashed juggernaut 2.6. That fixed all the major foibles with the SG2 but it still won't reliably connect to my garmin.
I opened up the filesystem to find that /system/etc/bluetooth/audio.conf is no longer there! Does anyone know where it went?
Apparently I don't have enough posts to ask in the dev forum where juggernaut was posted http://forum.xda-developers.com/showthread.php?t=1322642 so I'm hoping someone will see this plee for help.
thanks
the phone has BT 3.0, but it is backward compatible with BT 2.0 and 1.0 devices
i haven't had any trouble using it with my car deck (streaming audio & phone), my large collection of stereo BT devices, and other BT enabled phones & PCs/Laptops
the remote control feature from the stereo headsets works properly, for fast forward, backward, play, pause, talk, mute, etc
the only thing i have yet need to test BT on is with a BT smart wrist watch
So, we got a Motorola Roadstar car kit the other week which works pretty well. It also transmits audio to the the radio, so we know that my son will use it as he can't live without Spotify. We liked it so much, I bought a second one for the other vehicle. However, now it's en-route, I'm worried that the phones (mine is on Dandroid) won't cope with two devices with the same name. As far as I can see, there is no way to change the name of the device, however, I assume the mac address will be different.
Anyone know if this will cause a problem on the phones (all Android based, either 4.3 or 4.4)? Anyone know of a solution, or do we need to send one back?
It'll be fine. I actually have multiple BT device with the same name. I think you can edit them in BT settings if you want but it really shouldn't make a difference. You can pick and choose which device you want paired with and you'll only be using one at a time anyway.