Hi,
I upgraded my ROM from WM6 to WM6.1 (Kavana's ROM) a couple of days ago, but my Route 66 N7 software can't work with my Adapt AD-300 GPS receiver anymore.
It's quite weird: my phone finds the receiver, I can add it as device and the connection looks OK. Only Route 66 keeps complaining it can't find a receiver. There is no GPS signal on the receiver, but before the upgrade the software could see the receiver with just a good BT signal. Now: nothing.
I have tried everything: serial connection yes/no, secure connection yes/no, COM6/COM7, enable incoming beams/BT to my phone. Nothing helps.
Anyone know about issues between Bluetooth devices, maybe Adapt specifically, and WM 6.1?
Otherwise, is there any software with which I can check the BT connection on my phone itself?
Only thing I haven't tried yet is factory reset the GPS receiver itself (I removed the battery for a couple of minutes, but don't know if this is sufficient).
Bah, I like 6.1 too much to revert to 6.0
-mod-: oh right, my phone is an S620.
Related
Hello, I have installed TomTom Navigator 5 in my Qtek s200, but I can't connect it with the bluetooth GPS if the telephone is switched off.
Tomtom runs ok, but doesn't find GPS device.
If I switch on the telephone there isn't any problem, tomtom runs ok and find the GPS device.
I have used tomtom, and dell GPS bluetooth GPS reveivers.
Someone knows if is there a solution to use the GPS with the telephone utility switched off?
Thanks!
ive got this problem too with my xda 1 which i only use as a satnav unit
I use the xda with a wired gps but tomtom complains there is no gps device because the unit is in flight mode, even tho im not trying to use any wireless signals.
anyone help ?
thanks.
I don't know if I understand you right, but I might have an explanation for this. On my Qtek 9100, I can't use a bluetooth GPS-receiver when the device is in flight-mode. Flightmode disables all radiosignals...and since bluetooth is sort of a radio signal, it's disabled as well
A solution might be to turn off and on your device and "cancel" when you're asked to enter your SIMs PIN-code. This way, the device is not in flight mode (so bluetooth works) but the telephone-reception is disabled.
I hope this helps, if not: let me know!
--Marc
yes that works but the phone device is still switched on so uses battery
the gps in question in my situation is a wired unit going directly to my old xda 1's com port so shouldnt matter if the phone or bluetooth are on or not. Even if the pda was in flight mode it shouldnt affect use of my wired gps as there are no radio signals.
seems like a 'bug' in the tomtom software that if the pda is in any kind of flight mode including the phone being off, it decides it cant communicate with any gps, no matter how its connected, as if they expect everyone to be using bluetooth gps' and just include the wired configuration as a legacy function.
malty
maltloaf said:
yes that works but the phone device is still switched on so uses battery
the gps in question in my situation is a wired unit going directly to my old xda 1's com port so shouldnt matter if the phone or bluetooth are on or not. Even if the pda was in flight mode it shouldnt affect use of my wired gps as there are no radio signals.
seems like a 'bug' in the tomtom software that if the pda is in any kind of flight mode including the phone being off, it decides it cant communicate with any gps, no matter how its connected, as if they expect everyone to be using bluetooth gps' and just include the wired configuration as a legacy function.
malty
Click to expand...
Click to collapse
Darn...sorry, I misunderstood. I'm using a bluetooth GPS-receiver myself, so I just took for granted that you also used a bluetooth device And indeed, looks like a bug...not very convenient.
--Marc
Concerning bluetooth devices:
This seems not to work with Windows Mobile 5.0.
With Pocket PC 2003 devices it is possible to use with TomTom bluetooth while in flight mode.
Here's a work around for Win 5.0:
1) Enable the phone and bluetooth in the Comm. manager.
2) Make the link to thte bluetooth gps in TomTom.
3) Disable the phone in the Comm. manager.
4) Return to TomTom.
The bluetooth link will be maintained until you exit Tomtom or try to link again.
This might also be the case with a wired gps.
AJ.
I recently upgraded to the KOzhura rom... it works great, but I'm having problems with bluetooth connectivity.
Prior to the upgrade, I had no problem connecting to my scoche bluetooth audio device (same as headphones, but with RCA outputs to tie to a radio). Now, I can't connect at all. I also cannot connect to my mogul ppc 6800 (altthough I never tried to do this prior to the rom upgrade). MY dell axim has no problems connecting to either.
Any ideas what the problem is?
Did I miss a patch or something?
i think there is a bug in that area, i use a bluetooth gps, and it drops out now and again, and it takes some time to come back online, in alright weather, so thats no it,
I reflashed it and it seems to be fine, or i will have to live with it untill HP releases the official version
Can someone give a definitive answer to this, I am using an Orange SPV M700 which I have flashed with the generic Dopod WM5 rom Version 1.23.405.2.
I have tried various WM6 roms and have had the same issues with them all, I loose bluetooth pairing authority, the wirless keys are lost and Tomtom map activations are lost too.
Is there a way to resolve this issue as I see there are a lot of users with the Trinity and WM6 in signatures, so someone must be doing something right.
After having flashed my phone from WM5 to WM6, the tomtom ID of my phone changed too... Perhaps Tomtom's support will help you with that?
I have no problem with bluetooth...
It's not that, perhaps I should have been a bit clearer.
After flashing to WM6 & pairing across bluetooth for the activesync, connecting it to my wireless & activating the tomtom maps, give it 24hours or so and these details are lost. Although the bluetooth PC is still in the paired devices, the pairing code needs to be re-entered as does the wireless key if I try to connect to that.
The Tomtom map needs reactivating again also.
peterelliott11 said:
The Tomtom map needs reactivating again also.
Click to expand...
Click to collapse
I already read somewhere about this.
When you do some pairing with bluetooth and PC sometimes you lose the maps!!
Don't have further details though
I have problems with my Bluetooth and the paired device in the car with almost every recent ROM.
After about 10 minutes driving with a connected phone, the Bluetooth shuts down on my Diamond. When I go to Settings -> ... > Bluetooth -> Mode -> Turn on Bluetooth is unchecked. If I check it again it connects again with the phone and about 10 minutes later it's off again.
I went back to the RUU_Diamond_HTC_WWE_EastEurope_1.93.479.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe. It's against my feelings, believe, etc. but I want to solve it .....
I installed Advanced Configuration Tool (3.0), went to Bluetooth -> Audio gateway power save and Disabled it. I did it because I was reading about suspended devices and power save features. I thought that the loss of Bluetooth is been caused by a saving power feature.
After a soft reset, the Bluetooth stays connected.
It's a start, but I'm not happy with it ... I would like to use cooked ROM's and optimal settings in the ROM.
There are other tweaks too in Bluetooth, for example the supported bitpool, etc. Perhaps those settings cause the shutdown of a connected Bluetooth device instaed of the power save feature.
Has anyone this kind of problems too with paired Bluetooth devices?
If so, would you like to help me to find the cause?
If not, can you describe what device you use (Jabra, TomTom, car radio, etc.), which ROM, which radio and extra tweaks?
Hi
I do have the same problem. I am using my Diamond with my Opel Astra (Vauxhall) and a CD70 radio with built in handsfree (Opel UHP). It disconnects after 10 minutes and after calls. Everything else works fine. Changing rom and radios has not helped so far. If I don't close the comm manager it stays connected but disconnects after a call because the comm manager is closed with the end of the call. Is there a way to force the comm manager not to close?
Olli
olliver said:
Hi
I do have the same problem. I am using my Diamond with my Opel Astra (Vauxhall) and a CD70 radio with built in handsfree (Opel UHP). It disconnects after 10 minutes and after calls. Everything else works fine. Changing rom and radios has not helped so far. If I don't close the comm manager it stays connected but disconnects after a call because the comm manager is closed with the end of the call. Is there a way to force the comm manager not to close?
Olli
Click to expand...
Click to collapse
I have a CD70 too in a Opel Zafira.
This "comm manager" thing is interesting, but it looks to me like an Opel issue.
Can't you flash firmwares by opel?
Riel said:
Can't you flash firmwares by opel?
Click to expand...
Click to collapse
That's an option, but my Trinity (P3600) performed great with the same car. Will an upgrade solve my problems? I know one thing, it's not cheap either.
I tried it with different ROM's, but it still happens.
I tried it with different radio's, nothing changed.
Till today, I've got now the new radio (v1.05.25.BS14).
http://forum.xda-developers.com/showthread.php?t=432770
It has fixed the delays in GPS + faster GPS fix and more important fo me Bluetooth didn't stop today.
I'm sure 100% sure yet, but seems to be better.
I got something to complain too about the new radio. The radio signal is less strong than the .05 radio.
Same problem here
My Vectra is equipped with CD70.
Previously I've owned a Kaiser and the problem was solved by one of the 6.1 radios, bluetooth connection was rock solid.
Right now I have the same problem with Diamond - after every single phone connection, when I'll hangup, the phone disconnects CD70. When I'll try to reconnect manually using CD70 everything is fine.
I've noticed that the same problem exists when I'm using Nokia bluetooth headset - one call, bluetooth connection dropped...
I've tried following Diamond radios:
.05
.07
.08
.BS14
and two Raphael radios by Bepe:
1.03.25.18
1.02.25.11
Each Diamond radio behaves the same way. Each Raphael radio adds a bonus - random bluetooth connection problems.
Right now I'm back with .05, I think I'll look for the software I've seen once (can't recall the name) - it's a PDA application designed for connecting to the car bluetooth systems and it has been cerftified to work fine with CD70.
Use Jetware Mobile for htc-diamond.
jetware
That's the software I couldn't remember the name.
Anyway I gave it a shot and it gets even worse, I couldnt get the connection lasting longer then 2-3 minutes, totally unstable
Right now I got back to radio .08 - the bluetooth link is rock solid, I guess I'll just need to get used to reconnecting after each phone call
Same bluetooth system in my car, same problems as you guys.
To avoid the disconnections after calls you need to go, with 'Advanced Config' to bluetooth->Audio gateway power save, and switch it to disabled.
For me this little change solve the 'first' problem, but I have another one that I don't know how to solve: the aparently random bluetooth disconections. Sometimes BT is not disconnected in hours, sometimes in days.
I am also using Jetware Mobile, but i didn't feel any improve...
The random ones depend on the radio rom version - I was using .05 and it was rock solid.
I will try .16 with audio gateway started and with power save disabled as you advised - I thought about it earler but previously I tried to disable the power save without enabling audiogateway service
Well, we will see if it works or not.
Hi,
I also have a Vectra CD/70 combination, for 2 yrs now.
I had a HTC3300 and 2years i had not a single problem with Bluetooth connection.
Now i have a HTC Diamond Touch Pro and have the same problems you guys have.
I tried all your suggestions, radio's and so on with no good result.
The good news is .. its an Opel problem and it seems to be that a Bluetooth Firmware Upgrade is available from Opel Germany. I just contacted my dealer and next week he will Upgrade my bluetooth firmware.
I will keep you guys informed.
Hello,
had the same problem with my Opel CD70.
Using Jetware Mobile and limited the entrys who copied to the car to a max. of 5. Also disable the call lists. Now it works.
I think the Opel/Vauxhall Bluetooth Connection disabels if to many entries are copied to the car.
Hello,
any News about our Bluetooth Problem ???
I also have a CD70 from Opel and I cannot understand why my Diamond swich of Bluetooth after a while ?
Is it an Opel-Problem or does anybody now an Application which helps ?
Thanks a lot for Your help,
Stepos
Hi,
I am currently using BTrestore (http://home.casema.nl/rgschmidt/WM/Downloads/BTRestore_V_1_0_0_PPC.ARMV4.CAB). This utility checks the status of the bluetooth stack every 5 secs and (re)enables it everytime it's down. It seems that the 5 secs are short enough to keep the phone connected. It's not a real solution and unfortunately this tool is sometimes instable too, but it absolutely extends the connection time with the UHP.
Maybe bullock can tell us if the carkit upgrade solves anything...??
I also created a ticket at HTC, but they refuse to troubleshoot user specific issues. They told me they only look into issues if they get enough calls from different users and to keep an eye on the update site (they seem to be able to solve issues without knowing what the actual issue is...). So I would encourage everyone here to create a HTC ticket for this issue. I still think it is an HTC issue: a bluetooth stack should never go down without any user intervention.
Good luck!
BTrestart and Jetware Mobile doesn`t help, my Touch diamond disconnect again from Opel CD70 and swiched off Bluetooth !
Can anybody help ?
Sorry guys, the OpelDealer is still "searching" for the Bluetooth upgrade.
After several phonecalls maybe next week (1st week of Febr) it will be made available to the dealer.
Like i said ... i willl keep you informed ... still have this lousy problem !!
..does anybody use the new Rom 2.03 ? Any difference ?
I also asked my Opel-Dealer for an Update of UHP, next week I 'll get new Information....
... well guys I had my CD70 updated !! I am/was very sceptical because the only thing they did was a re-install of the Language of the Navi System with a version 2005 CD. I asked if that was all to correct my Bluetooth problem .... the (smiling) answer was YES.
I have it now for 24hrs ...... and Bluetooth is still on )
I will let you know the result after a week !!
..i can't beleave it works with a 2005-update ! Great !
My Opel-Dealer is still busy in selling 10 Opel Corsa every day (..the magic word is "Abwrackprämie") , so I'll have a date there next week...
When I bought my Vectra the dealer had also to reinstall the Language-CD, maybey it was the wrong version....
...... Sorry guys ......
This update DOES not do the magic trick !! So we have to find another solution
who has the right idea ??
I currently have a Diamond and TP2 with stock ROM's.
Diamond worked perfect with carkit untill i performed major ROM upgrade from htc.com. now it will connect and not reconnect on either device or carkit restart.
My TP2 behaves EXACTLY the same - connects and drops after either restarting. when connected it works fine - voice/dialing etc etc.
My car kit is a JVC KS-BTA200 connected to my KW-AVX810 head unit.
i've read all comments on google/xda's etc - well almost all! to no avail.
the devices are all set to visible obviously and all paired. ive read that a registry edit possibly fixes the issue but my TP2 & Diamond dont have the required reg strings. (that i can find!!)
i have the remote registry tool installed on my Desktop - so im ready to make changes!
please, if anyone can help i will very grateful!!
radak23 said:
I currently have a Diamond and TP2 with stock ROM's.
Diamond worked perfect with carkit untill i performed major ROM upgrade from htc.com. now it will connect and not reconnect on either device or carkit restart.
My TP2 behaves EXACTLY the same - connects and drops after either restarting. when connected it works fine - voice/dialing etc etc.
My car kit is a JVC KS-BTA200 connected to my KW-AVX810 head unit.
i've read all comments on google/xda's etc - well almost all! to no avail.
the devices are all set to visible obviously and all paired. ive read that a registry edit possibly fixes the issue but my TP2 & Diamond dont have the required reg strings. (that i can find!!)
i have the remote registry tool installed on my Desktop - so im ready to make changes!
please, if anyone can help i will very grateful!!
Click to expand...
Click to collapse
Hi, I am using my Touch Pro 2 with the same HU and Bluetooth adaptor as you but no such problem so far.
It used to have this problem then I try to connect using Window CE as the phone setup and choose another Connection Key instead of default 0000 to pair the phone with the HU.
ok, well i just tried connecting via searching for the device from the HU. it finds my device - i tap enter (to connect on HU) then it just jumps to a blue flashing 'connecting' then goes to a yellow 'error' straight away. if i select 'open' on the HU then it connects (connecting with a different ID - a number '6') but only untill i restart the HU.
also as a test i just tried an Xperia (just had one laying around LOL) and it does the exact same as mine!! ARRRRGHHH!
so im glad to say i believe it is not an HTC issue!
ok so i have an update - the problem is my HU will not pair correctly and it will not store a pairing. great.
another quick one - have found others are having trouble with their HU/adapters. thanks anyway everyone!
TP2 Bluetooth and voice dialing working fine ???
Have you tried to reset your carkit? I had the same problem after the rom-update with my TP1 and I put my carkit (Bury CC9060) back to factory settings. So I did the same this morning after I updated my TP2 and now it works just like a charm. Of course I don't know if your carkit has this possibility. Good luck, greetz Ton
'iznogoooog' - yes it work perfectly until you restart either device - 'ton66' - unfortunatley a reset is pretty much all i can do!!! eeeeek!
hopefully a reset will fix it! - i did unplug my b/tooth adapter then switch the unit on - then off then plug it back in.. didnt change anything.. oh well! will do complete re-set 2day!
BTW:
thanks so much for everyones help!
Got a questions. I am using the AVX-826 with build in Bluetooh. I want to know if you guys get the Signal Strength show on your Head unit is correct. on my unit pair with TP2. The Signal Strength indicator doesn't move. it always show the strength with my phone is connected to the unit and it stay that way.
The Battery Strength indicator does work and show the correct battery level.
I have exactly the same prob!
Hi,
I have a AXV800 and a BTA200.
My first device was a Artemis with WM6.0. No problem so far!
Then I changend to a Diamond with WM 6.1 and had the same problem as mentioned before. Now I tried my new TP2 and still the same problem.
And I tried the old Artemis again with a new 6.1 ROM and the same problem as on the other two phones.
Now I think it depends on the WM build. 6.0 seems to work 6.1 not!!!!!!!!!!
I did a reset on my AVX800 two times without luck!
I think I'm going to use a normal phone without Windows mobile for the next test!
Schelbi.