I have recently purchased a navicore SIRF III but when i use it with tom tom on my hermes (WM6)I can connect it to the hermes via bluethooth with no problems but I can not get it to connect to a satellite. Tom tom asks me about what com port I am using im not sure what the correct settings are can anyone help me out?
I noticed on the hermes I have external gps settings? also when i connect the device when i search for the device on a tab it has COM ports which has no settings in.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks
BT
OK I have the same proglem whit my IGO plus, but the solving problem is very simple, the com port is 0, do not use auto search, simple assignee com port 0
in your navigation software.
Well indeed I have used com0. But actually you can use others like 4 and 9. If one does not work try another. (You may need a soft reset between changes in port settings)
Heres a little bit of info to help you know if what you are trying is working:
In the tomtom satellite screen (the one that shows a series of columns for each satellite - there is a useful verbal comment at the top of the screen it will say one of three things:
1
No GPS Device - (always says this initially for 2/3 seconds. If things are set correctly it will move to 2 (below) but if your ports are wrongly set it will stay on No GPS Device)
2
No Valid GPS Signal - (means it has found the GPS device, you have the ports set correctly and it is now trying to find satellites - anything from 2 or 3 seconds to several minutes if you this is the first time you are using GPS, it will then move to (3 belowi) if you are in range of satellites). Make sure you have an open clear view of the sky at least for the first time you are doing this step.
3
Other NMEA GPS Receiver (or similar)- (says this when locked on to satellites and working correctly)
The above 3 steps are useful just to check whether the setup and port is correct. Even if you do not want to use tomtom it's worth running it at least once just to iron out any port problems.
Mike
NB if you find yourself going round in circles with this and not getting anywhere - clean start by deleting the T partnership turning of the BT device, doining a soft reset. Now start again - what can happen is that after making several port changes etc, you can find that even when you pick one that should work, it doesn't - hence the need to clear out previous failed attempts.
Thankfully once you get it working, it generally works fine after that. (A good reason to have a full backup programme like SPB backup - it saves you the hassle of going through this kind of thing ever again - on this device at least!).
Navicore works well. I use the Sirf Star 3 slim - It's tiny and works well from my pocket:
http://www.blueunplugged.com/p.aspx?p=120534
Related
Hello
I have some Problems with my XDAII and the Nokia Car-Kit Bluetooth.
I become no connect with the Device.
Have elsawhere a Answer wy??
Greatings to all
Matrix
If you have the Nokia Carkit 112 like me, it won't work.
The carkit only supports the handsfree profile, the XDA II supports the headset profile only.
There are rumours that we *may* get a handsfree update in a future release of the firmware or possible in SP1 for Windows Mobile 2003, but I have not see anything conclusive.
Regards
Michael
@matrix
then you should try this: http://bluetooth.i-networx.de/
servus ize|man
I downloaded the latest version and will try it out on my Nokai 112 kit as soon as I get to my car friday.
Will post results.
Regards
Michael
I have tested this with my Nokia CK-1W carkit and XDA II, It does not quite work as yet, At the moment my phone bonds and communicates to the carkit but will not force the audio through the carkit, I have tested the carkit with a working Nokia phone and it works no problems.
I am attempting to assist Tobias in debugging this, he will post a debug version on Friday, I will run the tests that I have run with the current version and send him the logs.
Hopefully he will be able to help fix the issues. He has certainly been very helpful so far.
I had the same problems with the Nokia CK-1W. In the end I got that swaped with an Ericsson HCB-30 which works flawlessly. I think it works with the Ericsson unit as it has 'headset' profiles which the XDA II supports.
I've posted under in the 'Stocking it Up' forum but here are some pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BLUETOOTH TOOLS
I have tested the Bluetooth Tools but this software works not really yet.
I have more Problems after the update.
I am waiting for WM 2003 SP1
Thanks for all answers.
Greatings
MATRIX
No luck here either with the Nokia Carkit.
I don't even get the page asking which profile I want to use after bounding to the carkit and confirming the name.
I do get a 'click' when bounding, but on sign on any further communications with the phone.
Also the headset enablement icon has gone from the today options.
Regards
Michael
HCB-30 Not auto connecting after ignition switched back on.
Hello,I recently have bought the HCB-30 also after having a disastrous time with the Nokia CK-1W.
I have had it working fine when I create a new bond however when I switch off the ignition and lose power to the device It will not auto connect when I switch the ignition back on.
Is there something that I am doing wrong? am I being impatatient?
Can you advise if when you start your ignition your XDA II connects without you doing anything?
Cheers
Neil.
This is probably better off in the ROM forum, but since I don't do custom ROMS I never go in there myself and was hoping that someone here might have the answer.
I'm running ROM 1.56.405.1 (43972) WWE with radio version 1.13.25.24
and when using tomtom, I get no satellite info. Not a major problem I suppose, but just annoying.
Is there a better radio I could use that would give me back the sat info?
thanks
the same
i have the same problem with the miri V13 - ROM
thanks for reply
First tip would be to turn off Active GPS. Makes my TomTom app go screwy and have problems with satellites.
Secondly, check your Quick GPS satellite data and make sure its up to date.
Failing that, theres some HTC GPS Tool floating around this site and people a load more knowledgable about these things should be along soon to help diagnose and fix.
The A-GPS thing fixed all TomTom GPS problems for me and I can nail down a signal indoors in under one minute.
try disable A-GPS
thanks but I think you may have misunderstood.
I have no trouble getting a GPS signal (A-gps is already diasbled and my quick GPS infor is up to date).
but, in tomtom for example when it should show how many satellites I'm connected to, it always says none.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
twisted-pixel said:
This is probably better off in the ROM forum, but since I don't do custom ROMS I never go in there myself and was hoping that someone here might have the answer.
I'm running ROM 1.56.405.1 (43972) WWE with radio version 1.13.25.24
and when using tomtom, I get no satellite info. Not a major problem I suppose, but just annoying.
Is there a better radio I could use that would give me back the sat info?
thanks
Click to expand...
Click to collapse
which version of tomtom are you using ?
it's not tomtom that's the problem. it's because I've upgraded my ROM (official one) and now the radio isn't correctly givng me the satellite info.
so, I was hoping that someone could give me an idea of the latest stable radio version that would give me back the sat info.
i to am having this problem, and its very annoying.
I'm sure someone has mentioned this before and all it was was the TT version. I'm running 7.915 and have no problem. I think it's all down to the version not currectly supporting the rom.
Check you version anyone and report back
if that's the case then it has to be a combination of both. I'm running 7.45 too, and as I said, it used to report perfectly fine before i upgraded my ROM/Radio
Check your pm Twisted!
Hi, I saw the same here. TomTom 7.910.9185, but only the first time I launched it.
After using another GPS program, TomTom now detects the GPS receiver faster and shows coordinates and satellite info.
Tried to set it to "internal GPS receiver" and NMEA on COM4 and it works with both.
EDIT: The phone has the official HTC ROM and radio from April
EDIT2: It happens when the phone is in fligh mode (with phone, WiFi and bluetooth off). Tomtom never liked this and seems to think that you always need bluetooth to access the GPS receiver. In fact it gets the position data but not the satellite data when in fligh mode.
Hi everyone, I rooted my x10 the week it was rooted and since that time have always had an issue with my alpine w505 head unit and the blue-tooth.
It works but i have to turn the volume all the way up on the car audio to just barley hear anyone.
I was not to concerned and figured it was just a glitch and was waiting for android 2.1. well with the delay and pending release of the android update I decided to update my x10 from 016 to 026. I did a clean install and thought my blue-tooth issue would be gone, well it it the same.
The alpine unit works fine with my wives nokia, but my x10 is horrible.
I can tell you that it worked great with the default rogers rom. which makes me believe that it's an issue with the packaged files I'm using.
I used the rom from post 4 in the android development thread. as i was going to try and just update. but I did have an issue and decided to do a clean upgrade.
Has anyone else had an issue with a car blue-tooth device? or does anyone have the alpine w505?
Thanks
You are lucky the bluetooth works at all.........................................
The prime reason for me wanting 2.1 is so that the SE flagship experia can do the things my 2007 K800i does..........................................................
ok is everyone having issue's with bluetooth and android 1.6? or is this a x10 issue?
I have a parrot CK3100 and everything works fine, i have to set the volume half the way because it sounds too loud.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I bet you can't voice dial and the phone book does not transfer though!
I have my xperia on xxxxx24 working in a fashion with a nokia kit. In the menu, you have an option to keep the lights on for development purpose. Say yes to this. Re boot phone, switch on Bluetooth, connect, stick in car charger and it doesn't disconnect while lights are on cos x10 don't sleep.....
Sent from my X10i using XDA App
Bennachie said:
I bet you can't voice dial and the phone book does not transfer though!
Click to expand...
Click to collapse
It syncs with the phonebook, i'll take a pic the next time i use my car, about voice dial, i don't know how to do it
Bennachie said:
I bet you can't voice dial and the phone book does not transfer though!
Click to expand...
Click to collapse
I can confirm the X10i works flawlesly on the Bury C9060 too, and syncs phone book, also A2DP music works as it should, it never loses sync and bluetooth is available after approx 5 secs of starting the car.
You can also change tracks from the C9060 and voice dial is imo better than the parrot, I checked every device before going for the C9060.
Uploaded with ImageShack.us
I can't sync my phonebook on my jvc unit or look at the name of songs that are playing off my phone when I use bluetooth streaming. It works fine with the bold and iphone though
Bennachie said:
I bet you can't voice dial and the phone book does not transfer though!
Click to expand...
Click to collapse
Here i am
This is how the Agenda looks when you sync a phone that it isn't able to transfer your contacts(my old LG viewty for example):
X10i linked with parrot, notice the icon located at the low right side, that means it is transfering your contacts:
This is how Agenda looks now:
Let's see if it works...
Yep, working
You can check Exif data to view time/date of the pics and the camera(x10i ), it links 5 seconds after i turn on the car, never disconnects, however i can't do AD2P since parrot CK3100 can't support it
OP-- this sounds stupid but it happened to me so check. The media volume for bluetooth is different from the media volume coming out of the speaker/headphones. Try turning up the volume on the phone.
I have Google Maps with GPS location support on my eLocity. This is a short note describing what I put together -- I did no work here, I just found the appropriate notes left by others.
Update: Navigation works too. See below.
I had an eLocity that I put Dexter's v1.42 on. But the market on that does not show Google Maps. So I put Bestialbub's fix on top of that. And that did display google maps, so I downloaded it. However, for whatever reason, the resulting market was very unstable, and would force close, even as a background task when I wasn't using it.
But it was good enough to play with. And with it I got the fundamentals working, however, I did end up reflashing with the latest stock eLocity firmware and installing Bestialbub's market on top of that.
So I installed Google Maps on the eLocity.
The eLocity does not have a GPS, so you need some external GPS device. I used my Nexus One and an app called Bluetooth GPS Output
I believe that app cost a couple of bucks, and there are free apps that will do the samething and should work, but I found pretty good instructions on how to get Bluetooth GPS Output to work here.
What Bluetooth GPS Output does is to take the GPS information on my Nexus One and make it available over bluetooth to any connected bluetooth device that wants it.
I then basically followed the instructions from here.
Bluetooth Pair your phone and Archos tablet (I have the Archos 70 250 gb)
Open Bluetooth GPS out on your phone,and turn it on, you should see a screen showing satellite info
Archos Settings/Location and Security/Bluetooth GPS, then select my paired phone. If that is grayed out, try opening up the app on your phone before actually pairing your Archos with your phone.
Open up maps and enjoy the Navigation!
But the last step isn't that simple because the eLocity doesn't support Bluetooth GPS in the Location & security settings page.
But there are workarounds....
Similar to Bluetooth GPS Output, there are apps that do the reverse. Listen for a Bluetooth GPS Stream, and convert that into an internal android source.
And for that, I chose, an application called BluetoothGPS -- similar name, different developers.
I installed that on the eLocity.
At this point I made the eLocity discoverable over bluetooth and discovered it on my Nexus One. The two devices said they were paired but not connected. I'm not sure what that means. And still with this working, I still see on the eLocity, the Bluetooth is active but not really connected icon, while the Nexus shows a bluetooth connection has been made (though that could be indicating a connection with its dock which is 10 feet away.).
On the Nexus One to get Bluetooth GPS Output talking to Bluetooth GPS I:
Didn't do much if anything in Bluetooth GPS Output, I just started it
On the eLocity, I:
On the device's Application settings page, under development, I enabled "Allow mock locations"
I started the application Bluetooth GPS
On Bluetooth GPS's main tab, I enabled Mock GPS Provider
Bluetooth GPS presented a list box with my Nexus in it, and asked me to connect, so I did.
And on Bluetooth GPS settings tab, I frobbed some reconnect interval settings.
And with that, it basically seems to work. The connection does not seem incredibly stable, I am not sure if it's related to screen display timeouts and devices sleeping, or some other source of flakiness.
But it does seem to work.
So I took it out for a test drive, to see how well it worked. This was typical suburban driving. And only lasted about 30 minutes.
The nexus was plugged into the car, the elocity was on battery. Bluetooth on, Bluetooth GPS Output running, Bluetooth GPS running, and the map showed the current location. Great!
So I directed the map on the eLocity to take us to the post office, and ... waited ... and waited ... and nothing happened.
Aha, it needs data. So I turned on the Nexus One's wifi hotspot, connected the eLocity to that, and, ...
Success! Driving directions and navigation worked just fine, with one caveat. For whatever reason, i would tell me when I started up Navigation that if I wanted voice nav, I needed a plugin from the market, but when I said sure, go get it, the market would force close. However, voice navigation worked anyway.
During the 30 minutes I played with it, the connection between the two devices was nice and stable, and the map always displayed the right location and navigation worked as expected.
The eLocity is a very nice mapper compared to the Nexus One, for whatever reason, at equivalent zoom levels, the eLocity display shows much much more of the surrounding area than does the Nexus One. And physically the screen is about three times larger, and much easier to see in daylight (cloudy day though.)
However, the Nexus One displays a map where your current driving direction is always oriented to the top of the screen. This makes it very easy to orient where the next turn or landmark is.
Presumably because the eLocity does not have a digital compass, the eLocity always displays north to the top of the screen. This can be better at sometimes, as when you are trying to get a feel for where a very long route will take you, and worse at other times, when you're just trying to navigate through streets.
But all in all, pretty cool.
Note the Google Maps blue location dot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
grax!!!!!
Thanks!!!! great tutorial!!!!!!!
Hi all,
Recently bought an ASURE S3OVB (see link: goo.gl/FXsks9 [URL shortened to prevent cluttered post]) and installed into my 2010 Vx Zafira B. Everything is AWESOME and i really love the headunit, however I seem to be having difficulties with the Bluetooth connection.
So. My phone (Archos 50 Power) pairs up OK with no issues, but when I go to place (or receive) a call with via the phone itself or the headunits Dialler, the call is placed and connected OK but the audio is still coming out of the phones ear-piece, UNLESS i press the button underneath the END CALL button (pictured below).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have also noticed that, on the phone, no matter whether the bluetooth is connected or not, the icon (circled in the picture below) is ALWAYS set to phone ear-piece, and NEVER sets itself to BLUETOOTH, HOWEVER even if i place a call and change this setting to BLUETOOTH manually, the call audio is STILL routed through the phone's ear-piece.
What Im trying to establish is the following....
1) Am I doing something wrong, or is there a problem with one or other of my devices?
2) If there IS a problem with one of my devices, Which one is it? Both are pretty much NEW devices, and thus if I need to claim on a warranty, I want to claim on the correct one!
3) Is it likely a software or hardware issue? If so is there an easy (-ish) fix? I have toyed with SOUNDABOUT from the play-store on the PHONE, but have had no success (although there are a LOT of settings!)
Any help will be greatfully appreciated.
Thanks in advance!
Tegan1110
A-sure bluetooth
Hi
Did you sort out your bluetooth problem?. I recentely bought an a-sure and the same seems to happen with my alcatel pixi.
Ian
Westcoastboy said:
Hi
Did you sort out your bluetooth problem?. I recentely bought an a-sure and the same seems to happen with my alcatel pixi.
Ian
Click to expand...
Click to collapse
Do you have any other bluetooth devices connected? Mine was something to do with the smart watch i was using (alcatel gowatch). I have since gotten a new watch (sony smartwatch 3) and the issue is resolved. Hopes this helps!