I have a new 8125 from Cingular (I think that's the same as a Wizard), and I tried to pair it with my 2005 Audi A6. The 8125 doesn't even see the car. Has anybode had a similar prolem, and so, is there a solution?
Hi Mike,
Just to let you know I have an Audi A4 with GSM prep and Bluetooth.
It works fine on my MDA Vario (wizard), but was crap on my old Sony Ericsson P900!.
If you look at www.audi-forums.com, a few people there have had Phone/Bluetooth problems with A6's which have been resolved by a firmware update from Audi.
Let me know how you get on.
Markee
My 8125 (TMO carrier) works perfectly with my 2006 A6 which has the technology package. Not only are calls clear and the connection fast, the car sucked all my contacts from my phone. Pretty darn neat.
Thanks for your help. I was able in the meantime to pair the phone with the car. I don't really know what changed, but after a few tries, the phone connected.
I tried to click on Markee's link, but it gave me an "unknown URL". Any alternative way to get to the forum?
@rambo6: My phone now pairs and I can use it, but I don't see the signal strength on the indicator in the car, nor do I get my contacts transferred. I noticed that my phone connects to the car in "handsfree" mode. Is there a setting that I am missing?
mike
Related
I am looking at getting a GPS module for use with my XDA II and want navigation software for when I return to Australia in a few months time.
I'm currently in Sydney on holiday and came across the Navman GPS 4400 Wireless receiver with Australian navigation software for AUD$849
I'm new to the idea of PPC GPS having previously used a stand alone GPS so I have a few questions to anyone currently using the Navman GPS 4400 with XDA II Australian software combination.
Is AUD$849 a good price?
Does it work well with the XDA II?
If I use a BT headset can I use the BT GPS at the same time?
Is the map coverage good, fair or poor?
Thanks.
Ed
NAVMAN and Upgrade ROM
I have used the 4400 with an XDA II in Europe, but I'm afraid that after a recent upgrade to the new O2 Asia 1.60ROM I have lost the functionailty completely. TOWA's BTTools 1.02, which worked well with the 1.52 ROM will not work with the upgraded ROM, nor will the BTTools 1.1. I can only set COM7 on the profile, which is precisely the COM port not available on the NAVMAN.
I could not use the BT Headset with the BT GPS at the same time.
As far as map coverage in Australia, I have seen it and it appears to be quite good.
I paid AU$1080 for the Euro maps so your price looks good, but check out the LeadTek GPS unit as well. It seems to have the edge over the 4400 as far as low strength areas are concerned.
Cheers
Fixed, of all the simple things
After yesterday's post, a friend and I had another try to get things working between the XDAII and the 4400, and succeeded.
Firstly make sure you unbond all other Bluetooth devices first so that the NAVMAN gets first pick of the ports.
Install "BTTools", the new 1.1 versions does work. When you bond with the 4400 you will still need to run the "enablechar.exe" program. You will be offered port 7 on TOWA's connect page.
When you open the NAVMAN software, select port 7, 57600 speed.
Here is a little tip that I overlooked. There will be a red box just to the left of the port selection box. If you tap that it opens the port and turns green!!!. How NAVMAN expect you to just find that is amazing as it is not labelled at all. Stupid Software design. (or possibly stupid operator ).
Anyway, happy driving when you get back.
About the only downside of a phone pda combo is that when the phone rings you lose your GPS screen, usually at a critical turn.
Cheers 8)
Thanks for the updated information Camstech, greatly appreciated.
I figure that since HTC manufactured the HP iPaq 6515, then it should have a place in this forum. I think this would be a great place to discuss this device.
What do you think?
Fernando
Hello folks:
I am looking for suggestions before I RMA my brand new iPaq 6515. I've owned enough pocket pc phones to know that this unit is probably defective, but I thought I'd give you a shout in case there are easy fixes I am missing:
a) I charged it for 24 hours and the device will not pickup the GPRS signal (the "G" on the top of the screen) unless it is plugged in. If you do a soft reset for instance and are away from a power source, this means you will not be able to connect to GPRS; not good. I tested this with three different SIM cards I have.
b) When you do get a GPRS signal (only when plugged into AC), you cannot navigate into any web pages nor download emails. I fooled around with the connection configurations to no avail.
c) The phone works intermittently and drops calls frequently. It is very difficult to make a phone call while not plugged in.
d) Bluetooth seems to be working OK. I paired with my PC without problems. However, when I tried to use the device as a bluetooth modem, it was unable to connect, GSM-GPRS radio problems mentioned in my notes above.
My sense is that there is an issue with the GSM/GPRS radio and how it gets power; difficult for me to tell. I'd be happy to try any suggestions you may have, but would like to resolve this quickly. I am getting this device for my wife as a christmas gift. I own a JASJAR and that works beautifully, so it is really frustrating to see how I cannot make this device work.
Thanks for any advice you can throw my way.
Fernando
I have been getting really mad with my polaris. I have the following headsets, jabra 8010, samsung wep200 and motorola s9. when the phone is in my pant pocket, I get tons of static when on calls. This is very annoying, are you guys experiencing similar problems with static on this phone, can't believe the bluetooth on this device sucks so bad.
i'm using the Blueant Z9, the Plantronics 510 and the Motorola H681 and i have not had any "static" complaints when used with my Orbit 2. note, however, that my Orbit 2 is running bepe's .53 WM 6.1 ROM.
i don't know much about the Samsung and the S9, but every Jabra that i've used has always had static issues with my HTC devices ...
I also bought the sony bluetooth watch which disconnects randomly from the phone, i also upgraded the radio, then the rom to the 0.53 Bepe, didn't solve anything. it is so bad, if I have 3g on, the calls gets dropped.
very frustrating. sending the phone back to mobileplanet.
curious to know where are you're having problems with 3G calls getting dropped... also, unless bepe's ROM had a different radio, my radio is stock. i used my phone for 1 hour straight today with the Z9, 3G and GPS all active and had no problems. during the call, i also received 14 emails from 3 different accounts.
sending the phone back due to dropped calls on 3G i can understand. hope you get it sorted out...
HTC Touch Dual (NIKI+NEON) & Fuze problems w/ ATT EP-5632 Bluetooth cordless phone
Hey all,
After searching in google & the XDA built in search for days I'm throwing in the towel & asking for help here. For some reason both my Touch Dual's (NIKI100 & NEON300) have a weird bluetooth 'drop' problem with my AT&T cordless phone which acts like a headset.
I've had an AT&T EP-5632 cordless phone system that links to a cell phone via Bluetooth for about a year & 1/2 now & it has served me well in my home office allowing me to keep my cell plugged in and gives me the ability to use any of my 4 cordless phones to talk on the cell and/or my vonage line. It has had its issues (such as sometimes the Bluetooth link breaks & I have to either turn off & back on Bluetooth on my cell, reboot my cell or power cycle the base) but that happened pretty rarely & wasn't a huge deal. My original phone I used with it was the AT&T 2125 (HTC Tornado) with WM5 & with it I rarely had any problems. After about a year I upgraded to an HTC S710 VOX that came with WM6 and although it fought me hard to do the original link and had the above 'vanishing cell' problem more often than the 2125 overall it was stable enough for me to use it daily making & receiving numerous calls. A few weeks ago I got a Touch Dual (NIKI100) with WM6 thinking I'd prefer a touch screen over full QWERTY to find it lacked the 850 GSM band & 850/1900 3G band AT&T uses but alas it was a new toy so I played with it anyway since we have some 1900 towers around. It too fought to link mostly because the keyboard was defaulting to characters not #'s so I was entering spaces not 0's for the password. lol Once linked I was happily using it with my EP-5632 cordless system via Bluetooth for a few days. One day I was on a cell call & another cell call came in. I was in the middle of a conversation so I let it go to voicemail. BIG mistake! As soon as the ringing stopped I was not able to hear the person I was talking to nor were they able to hear me even though my cordless still showed me as if I was connected (call timer running & not on home screen) & the cell screen showed me connected with call timer running so I quickly picked up the cell phone & they were there! We could talk fine so I hit the OFF button on my cordless to find it hung up my cell call! (So the ATT cordless was still connected via Bluetooth & controlling the cell but the voice portion was no longer being routed to my cordless but rather only on the cell) I quickly dialed the person back with the cordless to find we could not hear each other! I hung up & dialed directly with the cell to find the same thing.. After we tried calling each other a few times unable to hear each other he sent me a text message saying "What happened I can't hear you, can you hear me?" I ended up having to power cycle my Touch Dual to be able to talk to anyone (even directly on the cell not over Bluetooth) & once I did I could use the cordless or my cell AS LONG AS no one called me & I let it go to voicemail. (Tell me that's not odd!) I had already ordered a Touch Dual US NEON300 which arrived that same day so I moved my SIM over & linked it to my ATT to find it does the exact same thing! My 1st thought is that it is either a Touch Dual problem or possibly a WM6.1 problem since my S710 worked & had 6.0 which wasn't as good as my WM5 2125 but worked well enough to use. But both Dual's are worthless with this phone system unfortunately!
I broke down & bought a Fuze thinking that was an AT&T phone (I know, still made by HTC) but I assumed it would be more likely to work figuring AT&T would surely test it with their own AT&T branded cordless phone system, right? WRONG! I found a very strange thing. Even though the Fuze has WM6.1 on it, it does not do the same thing the Dual's do! If a call comes in it doesn't 'disconnect' the audio. WOO! The problem is that if I end a call then try to make or receive a call too quickly after it does the same thing as the Duals where the AT&T cordless initiates or connects the call via the Fuze but I can't talk to them on the AT&T! I have to pick up the Fuze & talk on it.. But unlike the Dual's I don't have to reboot anything to get it working again. I just have to wait like 20 seconds after a call completes before making another call. Inconvenient I know but not nearly as nasty as the problem I was having with the Dual's.
I searched & searched & found various people with odd Bluetooth issues linking with cars that sounded similar and many said the problems started when they upgraded to WM6.1 (either upgraded their ROM or bought a new phone with WM6.1) but some said WM6.0 had issues too although WM6 worked for me. Many people blamed Microsoft's Bluetooth stack, others blamed HTC because it seemed it was only HTC made phones that did it.
So my question is can these problems be fixed?
Perhaps with a patch from Microsoft or HTC?
Maybe by installing a different Bluetooth stack?
Maybe there are Bluetooth registry settings that are different (remember 2125 with WM5 works fine, S710 with SM6 works OK, Touch Dual NIKI100 with WM6 does same freaky thing as Touch Dual NEON300 with WM6.1 where the Fuze with WM6.1 mostly works, at least better than either Dual which makes me think it is NOT the WM version)
Could it be the radio version?
Maybe there is a cooked ROM I might try on either Dual or the Fuze that might fix it?
Maybe the issue has to do with the 2125 & S710 both being smartphones vs the Dual's & Fuze being WM Professional touch screen devices?
Perhaps it is some hardware incompatibility like Bluetooth chipset on the phones?
Sorry so long but I wanted to be thorough in case any of the minor details could help figure out the issue. I realize the problem could very well be a crappy Bluetooth implementation in the EP-5632 but from what I found I am not the only one with odd Bluetooth issues especially with HTC's running WM6.1 so even if someone else doesn't have these particular phones or the same ATT cordless system perhaps something useful to many others will come of this.
Thanks in advance for any input or possible solutions.
Bill
Quick follow up:
I did hard spl on my NIKI100 & flashed with "RUU Nike Radio 1.58.21.23S Modded" & "Tom_Niki_Project_v2.1.3_WWE" ROM & it FIXED the Bluetooth problem with my AT&T EP-5632! That is good news & bad news. The good news is obvious, it is fixed! The bad news is however that I'm selling that phone because it doesn't support the 850 GSM band or AT&T 3G (850/1900 bands). Btw for anyone searching on upgrading their NIKI to add the missing 850 band, of all the radios & ROM's I tried no combination was able to add the 850 GSM band so I assume the hardware is not there as has been noted in various places but not absolute so I had to try. I never expected it to add ATT 3G but like my Touch Diamond (yup I bought one of those last week to see how it worked with my ATT cordless phone & it acts just like my Fuze & I tried a few ROM's) I had hoped it would at least add the GSM band to give me better coverage around here but it was a bust. Guess bad news to anyone else searching on the subject.
So my dilema now is how do I do fix my NEON300? I suspect it was the ROM not the radio that was the fix but I can't say for certain unless I try others & I already put it all back to stock to ship out to the buyer tomorrow. (I had tried "RUU Nike Radio 1.71.09.01K" too but the phone went wacko & I couldn't make calls for long enough to test & didn't try others with this particular rom)
I noticed on the Niki Project thread there are a few mentions of Bluetooth changes:
* Bluetooth FTP 1.2.33281.9 Diamond [NEW]
* Bluetooth 1.6.5.0 Diamond [NEW]
* Bluetooth patch included
* Best Bluetooth A2DP settings
* Bluetooth DUN support
I suspect one of those is the magic fix that I am hoping I can apply whatever that was to my NEON300.. I'm hoping someone involved with the Niki Project can shed some light on what those updates are or do but perhaps I need to ask in that thread instead.
I'm also interested to hear back from anyone else who is having Bluetooth issues with the Dual (such as integration with cars I read so much about) to see if this radio/rom combo solves their problems or not.
Thanks in advance,
Bill
Hello
I have a German T-Mobile branded Touch Pro 2 which has been flashed to the WWE rom (1.86.401.0 build 67102), radio 4.49.25.17, protocol 61.44tc.25.32U.
I seem to be suffering from lousy bluetooth and wifi reception and was wondering if anyone else has had any problems,
For the bluetooth, it will struggle to work with a headset that is more than 3-5 feet away. For the wifi, it will struggle if it is more than 4-5m from the access point (with line of sight).
This is really really poor and I'm wondering if my unit is defective or whether they are all like this?
If it's a problem just with my one, does anyone know what the problem could be? I've seen a disassembly guide, which shows that the antenna module is at the top of the device and is relatively easily removed/replaced. Could it be a bad connection to the wifi/bluetooth antenna? The GSM/3G coverage is fine.
Any help appreciated.
Thanks,
Andrew
I have the same situation with my phone.
Mine is a US unlocked Touch Pro2 flashed with the WWE rom (2.07.401.1 build 80303), radio 4.49.25.88, protocol 61.44tc.25.33U.
Any suggestion?
I broke the screen on my old phone recently and bought a new Touch Pro 2. The new one is fine in terms of reception, so I imagine the first one (and possibly your one) are faulty. If you have the opportunity to return yours and swap it, I'd do so.
I'm going to take the old one apart to replace the screen. If I find out what's wrong with the reception along the way I'll let you know. I suspect the aerial is not properly seated/connected on the contacts on the motherboard.
Andrew
I have tried to troubleshoot my issue thinkin it could be my Altec headset. I paired it with my buddies phone "HTC Epic" and has clear connection for over 80 ft. Not the headset. I can't tell what it could be.
I have an EVO running Calkulin's EViO 2 ROM v1.2
Maybe its not that but not sure if its the Kernal or what.
My Wifi connections rock.