Related
Im new to the MDA vario. Just swapped it with another phone...
So far i've removed the sim lock with the help of unlockitnow and thats all thats been done to it.
I would like to use my bluetooth stereo Sony Ericsson headset for listening to music on the Vario but it doesnt support the specific protocol. Am I right in thinking that I can perform a rom update on this device so that it would support the bluetooth stereo protocol.
I use the device for exchange push email, surfing and hopefully wireless music. Is there a rom you guys can point me to that will allow me to do what I want? I believe there is another lock (CID)?? I need to remove to use other roms on the device.
if you are not sure of what you are doing it's better off that you use the official ROM update... go to your T-Mobile's website to check for it...
vseehua said:
if you are not sure of what you are doing it's better off that you use the official ROM update... go to your T-Mobile's website to check for it...
Click to expand...
Click to collapse
After doing the above its well worth reading through the wizard forums as all the info you need is there.
Think I have the current version already. I've got push email but I dont think it supports the stereo bluetooth protocol which is what I want....
Hello,
HTC have publied a HOT FIX FOR BLUETOOH
"/12/2007
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Go to htc club an enjoy.
Downloaded it from HTc.cOM
Installation instructions
Follow the instructions below to download and install the hot fix on your device:
Make sure you have Microsoft ActiveSync® installed on your Windows XP PC or Windows Mobile Device Center on your Windows Vista® PC. You can find Microsoft ActiveSync from this link or Windows Mobile Device Center from this link.
Connect and synchronize your device with your PC via Microsoft ActiveSync® or Windows Mobile Device Center using the USB cable.
To download thehot fix, first select the check box below. Next, select thehot fix and the desired FTP site then click Download.
Copy the hot fix, which is a cab file, to your device.
To install the hot fix, tap the cab file and follow the on-screen instructions.
Here is the file:
http://rapidshare.com/files/77588898/TyTNII_BT_Hotfix.zip
Enjoy,
Nadavi
for tytnII, but how about att tilt? is it rom specific?
Hope this will work. Thanks for the tip.
private69 said:
Hello,
HTC have publied a HOT FIX FOR BLUETOOH
"/12/2007
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Go to htc club an enjoy.
Click to expand...
Click to collapse
This does not show up on the updates for my TyTynII (downloads are serial number specific) only in the generic downloads.
I think its best if you only apply this IF you suffer with any Bluetooth problem.
The old adage, 'If it ain't broke, don't fix it!'
Re: does this work on AT&T Tilt?
In the HTC 1.56 ROM, this file is a replacement for \Windows\TIInit_4_2_38.bts a.k.a. (OEM\OEMDrivers\TIInit_4_2_38.bts for chefs). There is nothing else in that cab (see upgrading forums thread for better description)
Edit: I was wondering if I kept quiet, how many people would have experienced a placebo effect and said that it works great and makes bluetooth 10x better on AT&T...
Summary
If you happen to be an AT&T Tilt user that has flashed to an HTC ROM, this fix will work for you. If you're running an AT&T ROM, or you have no idea what a ROM is, but you know your phone says AT&T on it, it does nothing.
Does this fix the issue were bluetooth is dropped after finishing a call ?
Thanks for letting us ATT users know that it doesn't do anything. Guess we don't have this issue But on a serious note does this actually fix anything besides a supposed call dropping? I don't have that issue but of course we all have tons of issues with BT quality.
I have install the update listed above on a Tilt running the RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship Rom and the Bluetooth quality has jumped 100%. My Bluetooth stereo headphones sound great.
Thanks for starting this thread.
Awesome, thanks! I was going to ask if anyone had drop call problems as it happened to me twice last night and I happened to have my BT headset on
sirooga said:
Thanks for letting us ATT users know that it doesn't do anything. Guess we don't have this issue But on a serious note does this actually fix anything besides a supposed call dropping? I don't have that issue but of course we all have tons of issues with BT quality.
Click to expand...
Click to collapse
I have a lot of crackling background on my BT headset. Did not have that on the 8525. Also, there seems to be less functionality supported in the Tilt implementations, regarding the BT, vs the 8525 (I was running a cooked ROM though on my 8525). What i mean by that, is that I was able to use the BT buton to activate the voice dial using the MS VM. In addition, hitting the BT button twice was getting me a redial. Not anymore. I wonder is this has to do with the AT&T ROM or not? Is this a genuine HTC issue?
kaluzu said:
I have a lot of crackling background on my BT headset. Did not have that on the 8525. Also, there seems to be less functionality supported in the Tilt implementations, regarding the BT, vs the 8525 (I was running a cooked ROM though on my 8525). What i mean by that, is that I was able to use the BT buton to activate the voice dial using the MS VM. In addition, hitting the BT button twice was getting me a redial. Not anymore. I wonder is this has to do with the AT&T ROM or not? Is this a genuine HTC issue?
Click to expand...
Click to collapse
Before I switched to Dutty's ROMs, I was running the stock Tilt Rom for a few days, and then the newer Tilt ROM for a week. Both of those AT&T Tilt Stock roms gave me no issues like you mentioned. I heavily use my BT headset (Jawbone), and use Microsoft Voice Command (I very seldom use the dialer as its easier to just speak and have the phone dial for me). Pressing once on my headset would always bring up MS VC so I could issue it commands, and pressing twice on my headset always did a redial.
Now that I'm on Dutty's 7b, I have the same behaviors there too. Not sure what to tell you (other than some BT headsets don't work well with WM6, but if you were using the same headset on your 8525 then thats probably not the case).
As always... YMMV
_Alex_ said:
This file does not exist in the AT&T Tilt ROM, so it's doubtful it will harm or help to install this.
Click to expand...
Click to collapse
I checked the AT&T's 1.60.502.3 rom and it does exist. I didn't check the stock AT&T rom so I don't know if it wasn't there. I did a file comparison with ExamDiff between HTC's fix (22,490 bytes), AT&T's 1.60.502.3 version (22,490 bytes) and HTC's 1.56.405.5 version (23,899 bytes). It appears AT&T's newest rom already has the fix so anyone using the following roms should not have to apply the fix:
AT&T stock 1.60.502.3
Kyphur's XDA Live
Dutty's AT&T Variants
Custel's Series
_Alex_'s 1.60
any of DK's roms (shameless plug)
Is rapidshare the only place to get this? I am behind a firewall.
jgermuga said:
Is rapidshare the only place to get this? I am behind a firewall.
Click to expand...
Click to collapse
Cab fix attached.
akadonny said:
I checked the AT&T's 1.60.502.3 rom and it does exist. I didn't check the stock AT&T rom so I don't know if it wasn't there. I did a file comparison with ExamDiff between HTC's fix (22,490 bytes), AT&T's 1.60.502.3 version (22,490 bytes) and HTC's 1.56.405.5 version (23,899 bytes). It appears AT&T's newest rom already has the fix so anyone using the following roms should not have to apply the fix:
AT&T stock 1.60.502.3
Kyphur's XDA Live
Dutty's AT&T Variants
Custel's Series
_Alex_'s 1.60
any of DK's roms (shameless plug)
Click to expand...
Click to collapse
Just realized this while doing some diffs and was going to repost. (Microsoft file find sux ) Original post edited...
mfrazzz said:
Before I switched to Dutty's ROMs, I was running the stock Tilt Rom for a few days, and then the newer Tilt ROM for a week. Both of those AT&T Tilt Stock roms gave me no issues like you mentioned. I heavily use my BT headset (Jawbone), and use Microsoft Voice Command (I very seldom use the dialer as its easier to just speak and have the phone dial for me). Pressing once on my headset would always bring up MS VC so I could issue it commands, and pressing twice on my headset always did a redial.
Now that I'm on Dutty's 7b, I have the same behaviors there too. Not sure what to tell you (other than some BT headsets don't work well with WM6, but if you were using the same headset on your 8525 then thats probably not the case).
As always... YMMV
Click to expand...
Click to collapse
Give this a read. I have MS VC 1.6 working just fine on my Jabra BT250 after following the instructions.
you can ignore the first part about removeing the cybertron dialer or whatever.
http://forum.xda-developers.com/showpost.php?p=998205&postcount=9
I'll try it. Thx for the tip. I am not sure if this only works for 8525/TyTn (I do have the TyTn II/Kaiser)
Edit:
Tried. Sorry, did not work. Oh well. will see, but for now I wil stick with the AT&T ROM.
Hi,
there is something weird about that fix:
when the cab is on the kaiser, you tap on the file to install it.
you believe it's installed but in program files , you may find
a "kai6492_hotfix" shortcut, you tap on it and the choices are install or exit
it's seems there an identity check to be sure it's on a kaiser
"module id is kais(required kais)"
then if "equal" "ok" then install
and soft reset needed
why two install required ?
the kai6492_hotfix is still in program files after that
and last VC1.6 was working on my bt headset(but the voice recognition succeded about only 10%,i think because of audio quality when i am speaking) but i could ear vc1.6 replies ou questions)
now it is not working anymore.
when i click on the button(headset) before it was launching voice command as the harware button (assigned to it) could do it
now the same button launches the phone dialer(as i was tapping on "call"(green phone)).
ps; since that hotfix, i haven't been able, any more, to install btIO-0.6-wm5 cab
Deleted cause not worth it....
Hey guys, hope you can help.
Successfully updated my V1615 to WM6.1 on Friday.
Before I did this, I had TomTom installed which used to get a lock on to the satellites in less than 30 seconds.
I used the device with TomTom on Saturday and after an initial delay of locking on (which I assumed normal as it was a fresh install) it worked.
However trying to use it today and it just will not pick up a signal.
The ROM I used was the Vodafone one linked to from the Wiki list. (3.08.161.0) (Radio 1.64.08.21).
I have also tried Changing the Radio ROM to 1.65.17.10 but no difference.
It's set to Other NMEA device, 4800 baud and COM4 like it always was. I have run a QuickGPS download.
Strange thing is, when I go into the GPS config in TomTom I used have all the satellites listed in gray which would then turn blue when locked on but now they aren't listed at all.
Please help! I do have a bluetooth gps receiver from when I had my Hermes so I can get but part of the reason to get the Kaiser is so I have an all in one unit. I'm just in the middle of a hard reset to try again but does anyone have any thoughts on the matter? It's gone from being a brilliant GPS unit to a dodo!
Thanks!
Test if Google Maps finds some satelittes, just to check if there is a problem with TomTom
http://www.google.co.uk/mobile/gmm/stp-js.html
If that doesn't work, I'd reinstall the old ROM and see if the functionality returns and if it doesn't assume you have somehow broken the GPS.
funkygibbon said:
Hey guys, hope you can help.
Successfully updated my V1615 to WM6.1 on Friday.
Before I did this, I had TomTom installed which used to get a lock on to the satellites in less than 30 seconds.
I used the device with TomTom on Saturday and after an initial delay of locking on (which I assumed normal as it was a fresh install) it worked.
However trying to use it today and it just will not pick up a signal.
The ROM I used was the Vodafone one linked to from the Wiki list. (3.08.161.0) (Radio 1.64.08.21).
I have also tried Changing the Radio ROM to 1.65.17.10 but no difference.
It's set to Other NMEA device, 4800 baud and COM4 like it always was. I have run a QuickGPS download.
Strange thing is, when I go into the GPS config in TomTom I used have all the satellites listed in gray which would then turn blue when locked on but now they aren't listed at all.
Please help! I do have a bluetooth gps receiver from when I had my Hermes so I can get but part of the reason to get the Kaiser is so I have an all in one unit. I'm just in the middle of a hard reset to try again but does anyone have any thoughts on the matter? It's gone from being a brilliant GPS unit to a dodo!
Thanks!
Click to expand...
Click to collapse
wow you picked the wrong radio to change too. You should have read about it before changing to 1.65.17.10. You should do some research on what you did to yourself.
redbandana said:
wow you picked the wrong radio to change too. You should have read about it before changing to 1.65.17.10. You should do some research on what you did to yourself.
Click to expand...
Click to collapse
Well he already said 1.64 didn't work either. Maybe you should read what's written.
-IK- said:
Well he already said 1.64 didn't work either. Maybe you should read what's written.
Click to expand...
Click to collapse
Maybe you should read the thread that redbandana is talking about... maybe the bit about it being locked to your phone and you can't downgrade it... not really a good choice 'cos he's now stuck with that radio and also maybe stuck with WM6.1 (which also sucks - WM6.0 faster and more stable imho).
I had to do a hard reset and reinstall apps. TomTom no longer works. LiveSearch does RunGPS does. Neither TomTom or GPSTest can find the GPS. Any suggestions? When you choose other NMEA device in TomTom options are Serial on USB and COM7: that's it.
Thanks for any suggestions.
Well, it works now! I used to be able to get a lock on indoors, but now I can't. However if I go outside I cado get a lock on in TomTom. It seems like the GPS is now less sensitive, but hey, it works aand that's the main thing.
I'll do a search later but does anyone have a link to the thread regarding this dodgy radio. I did try and downgrade it but as you say, it didn't. I have some more coming in this week anyway so I can give this to someone who doesn't need/want GPS and I'll have the shiny new one. Ah the joys of working in IT!
Oh, and thanks to IK for the Google Maps link, brilliant app! I'd seen it on the PC but not pocket PC.
FWIW, my Tomtom uses the "Internal GPS" setting, not "other NMEA device"
Robert
funkygibbon said:
Well, it works now! I used to be able to get a lock on indoors, but now I can't. However if I go outside I cado get a lock on in TomTom. It seems like the GPS is now less sensitive, but hey, it works aand that's the main thing.
I'll do a search later but does anyone have a link to the thread regarding this dodgy radio. I did try and downgrade it but as you say, it didn't. I have some more coming in this week anyway so I can give this to someone who doesn't need/want GPS and I'll have the shiny new one. Ah the joys of working in IT!
Oh, and thanks to IK for the Google Maps link, brilliant app! I'd seen it on the PC but not pocket PC.
Click to expand...
Click to collapse
This is the link for the 'dodgy radio'. It looks like it is also an AT&T only radio.
Thanks ach2. Did a search and have spent all morning readin it!
I'm now having issues with the actual phone operation, intermitant no sound or buzzing.
I think I'm going to take a chance and return it to Vodafone. They do a next day swap under our corporate contract.
If there is any comeback I'll just plead ignorance!
Satrted to have the buzzing earpiece and broken camera issue with this radio, so it's gone back to Vodafone as faulty! Replacement is currently still on stock Vodafone WM6.0 ROM. To be honest I think I'll stick with 6.0, as 6.1 didn't really offer anything over it.
Roll on 7.0!!
funkygibbon said:
Satrted to have the buzzing earpiece and broken camera issue with this radio, so it's gone back to Vodafone as faulty! Replacement is currently still on stock Vodafone WM6.0 ROM. To be honest I think I'll stick with 6.0, as 6.1 didn't really offer anything over it.
Roll on 7.0!!
Click to expand...
Click to collapse
If you're sticking to WM6.0 (i do too) try Q-mobile 1.2 with radio 1.27.12.17 or 1.27.12.32 - they both work well in the UK.
funkygibbon said:
To be honest I think I'll stick with 6.0, as 6.1 didn't really offer anything over it.
Roll on 7.0!!
Click to expand...
Click to collapse
My friend, you need this (Vodafone WM 6.1 pre release) and use it with this Niki 1.58.11.07 Radio.
Been running this for a few days and basically I've changed my opinion on my V1615 from wanting to sell to now enjoying using it.
Highlights include 30 - 55 second GPS fix in TomTom, much much better speaker phone and better call quality.
Try these out and I'm sure you'll agree.
Thanks guys, maybe I'll try them over the weekend.
Actually, that Vodafone 6.1 ROM is the one I tried and to be honest I didn't see much difference between that and the stock 6.0 one.
As long as I'm outside I get a lock on in TomTom in about 15 seconds which is good enough for me. On my old one that I bricked I was sure I used to get a signal inside as well.
I'm just looking at the Wiki for the Q-mobile one.
Thanks again for the help, suggestions and info. This is what makes the internet great! Complete strangers helping each other out.
funkygibbon said:
Thanks guys, maybe I'll try them over the weekend.
Actually, that Vodafone 6.1 ROM is the one I tried and to be honest I didn't see much difference between that and the stock 6.0 one.
As long as I'm outside I get a lock on in TomTom in about 15 seconds which is good enough for me. On my old one that I bricked I was sure I used to get a signal inside as well.
I'm just looking at the Wiki for the Q-mobile one.
Thanks again for the help, suggestions and info. This is what makes the internet great! Complete strangers helping each other out.
Click to expand...
Click to collapse
Do you not experience the key lock bug in WM 6? Was one of the main reasons why I upgraded to 6.1.
-IK- said:
Do you not experience the key lock bug in WM 6? Was one of the main reasons why I upgraded to 6.1.
Click to expand...
Click to collapse
What's that? Is that the one where you press end call to end a call and sometimes it locks your touch screen? If so yes, but not very often.
Yeah something to do with when you set your device with a password and it goes into sleep mode during a call and then you wake it up and the start menu stops working.
Considering the G1 doesn't have a standard 2.5 or 3.5mm jack for line out, stereo bluetooth was the only other option. who wants to use a retarded adapter on your headset??
Is there any way to add support for this later? It has to be a software fix, as WM didn't have Stereo Bluetooth until WM6. Any ideas?
You're about a month late discovering this one
I've heard that the Google devs are working on a new bluetooth stack that may support A2DP. I've been poring over so many forums lately, I couldn't begin to tell you exactly where. But even review sites say "...bluetooth (A2DP to come later)." When is anybody's guess.
"supposedly" there will be an update the same day it releases to add in A2DP support...
yeah ive heard of 2 updates after release or on release one major and the other not......but again who knows
rantrav said:
yeah ive heard of 2 updates after release or on release one major and the other not......but again who knows
Click to expand...
Click to collapse
I hope the other update is video recording...
Oh well, this is STILL the best device T-Mobile has released since the HTC Wizard (aka T-Mobile MDA). And maybe add Outlook support w/ Activesync and Exchange. Well, that might take awhile but someother software might work just as well. Either way,
Does anyone know if word, excel, and powerpoint will work in some kind of fashion?
sino8r said:
I hope the other update is video recording...
Oh well, this is STILL the best device T-Mobile has released since the HTC Wizard (aka T-Mobile MDA). And maybe add Outlook support w/ Activesync and Exchange. Well, that might take awhile but someother software might work just as well. Either way,
Does anyone know if word, excel, and powerpoint will work in some kind of fashion?
Click to expand...
Click to collapse
Im not too sure as to how great this source is....they said that there will one minor update and the other will big a big one with having to reset the device....so I really do not know I will try to find it tomorrow..i think that it was on the tmonews.com site...but i will look into it. if it is just a person then i wont post anything else about it but if it has some sort of source then i will be sure to post it.
sino8r said:
Does anyone know if word, excel, and powerpoint will work in some kind of fashion?
Click to expand...
Click to collapse
So far, all they're promising is read-only for Office docs.
beartard said:
So far, all they're promising is read-only for Office docs.
Click to expand...
Click to collapse
Even if we can install Docs-to-go?
Has DataViz put out an Android client?
G1 Bluetooth
I've asked in various stores and got different answers, so I'm hoping someone with a G1 can give me a definitive answer.
Will the G1 allow another device to access the internet over bluetooth??
Specifically I make a lot of use of my TomTom sat nav during the day, and I rely on it getting traffic updates over the web by bluetooth with my phone. Before I buy a G1 will this still work?
TIA
Dave
maybe?
For now no. maybe some one will develop
Poo, that means I have to still carry a PDA and a phone, I was hoping I could put both together by getting a G1.
You can get GPS Maps and Web access through your G1, so you wont need your TomTom. However, it wont be as detailed or have voice.
hotelier said:
You can get GPS Maps and Web access through your G1, so you wont need your TomTom. However, it wont be as detailed or have voice.
Click to expand...
Click to collapse
YET!!! LOL
The hardware is there, but the software isn't finished yet. Right now the only thing Bluetooth can do in Android is connect to a hands-free headset. As I understand, Google is still working on the Bluetooth API and the other profiles will be enabled in a future software update.
Personally, I'm waiting for A2DP. Not a whole lot of point in loading a phone with music if it doesn't work with my headphones.
hotelier said:
You can get GPS Maps and Web access through your G1, so you wont need your TomTom. However, it wont be as detailed or have voice.
Click to expand...
Click to collapse
We use our PDAs alongside our TomToms in vehicles, and to be honest I quite like having them seperate for various reasons.
I'll just have to wait for bluetooth internet then maybe reconsider my position.
drum said:
We use our PDAs alongside our TomToms in vehicles, and to be honest I quite like having them seperate for various reasons.
I'll just have to wait for bluetooth internet then maybe reconsider my position.
Click to expand...
Click to collapse
I agree I like having separate devices. I don't like combining too many things into one object because you can't use them at the same time. I have a TomTom, a MP3/video player, and the G1 now... But I like the fact that when the TomTom is not up to date I can switch to the G1... and if I find myself without my MP3 player I can just use my G1. I like having the option but I don't use it on a daily basis.
TomTom traffic
I understand your concern as I have a similar problem. I have the Vario II and I have had a lot of trouble with it (WM6.1) connecting to the Tomtom traffic server. My case may be complicated by the fact that I ride (tomtom rider) and I cannot get the phone to fix things in the middle of the ride The problem started when Micro$oft changed DUP bluetooth connection and everything gets messed up. I was considering the android G1 as long as I can get the traffic service that I paid but I cannot use. And just to clarify, I do have a single tomtom unit which does the GPS and all the things. The phone is only to provide connection to the tomtom plus service.
I hope that comes soon.
flashing blue led for enabled bluetooth?
is there one? mine doesnt, yours?
Mine blinks when bluetooth is active... not sure if it's only when a device is connected or not but that would be nice to only see it when devices are connected.
Every time I try to sync my AT&T Fuze with my Lincoln, I have to start over creating a new sync connect via Bluetooth. I didn't have this problem with my old AT&T Tilt. Does anyone know how to make this work properly?
I have the same problem with my Touch Pro & Altima 08. After making the first call via bluetooth I have to start over creating an new sync. I didn't have this problem with my old O2 Atom Exec
I had this consistently happening with my Dell D620 until I loaded the (unofficial) follow-up to .Net3.5 Mobile: Microsoft_[1].Net_Configuration.CAB (have .Net 3.5 on my TP)
Afterwards, my issue disappeared.
johnston21 said:
I had this consistently happening with my Dell D620 until I loaded the (unofficial) follow-up to .Net3.5 Mobile: Microsoft_[1].Net_Configuration.CAB (have .Net 3.5 on my TP)
Afterwards, my issue disappeared.
Click to expand...
Click to collapse
Where did you download this from?
i think the bluetooth on the fuze is dodgy cuz i couldnt even connect to my g/f Sprint Mogul to send her a ringtone, both phones pop up a message saying unable to communicate with device or something like that, i know its not my g/f phone cuz i have connect her cell to her laptop manytimes but i havnt really used my cellphone *The Fuze* bluetooth much.
Same issue, my wife's navigator has the same issue. However I had this installed (LINK)
But on my neighbors Ford Fusion, no problem at all.
mstaxin said:
Where did you download this from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=373721
1'st post.
Microsoft.Net
Microsoft.Net CF 3.5 fixed the problem as well as several other problems I was having on the Fuze. I highly recommend that everyone download a copy of this and install it on your devices. I think it will solve most of our problems.
mstaxin said:
Microsoft.Net CF 3.5 fixed the problem as well as several other problems I was having on the Fuze. I highly recommend that everyone download a copy of this and install it on your devices. I think it will solve most of our problems.
Click to expand...
Click to collapse
Are you referring to the actual .net 3.5 CE, or the Config fix/mod cab I posted a link to?
The actual from Microsoft's website.
allthatinny said:
i think the bluetooth on the fuze is dodgy cuz i couldnt even connect to my g/f Sprint Mogul to send her a ringtone, both phones pop up a message saying unable to communicate with device or something like that, i know its not my g/f phone cuz i have connect her cell to her laptop manytimes but i havnt really used my cellphone *The Fuze* bluetooth much.
Click to expand...
Click to collapse
I don't have that problem. I send and receive bluetooth files fine. Since you admitted you don't do it often, I'm going to side with user error.
While not a TP/Fuze, my touch did this in a rental i had. I ended up just deleting EVERY paired device and starting from scratch. Worked fine since.
The problem came back yesterday. It appears every time you restart the car, Microsoft Sync doesnot see the FUZE until you go into the FUZE's bluetooth and tell it SET AS HANDS FREE. I do not know if this is a FUZE problem(Bug) or a Microsoft Sync problem. It seems that it's a FUZE BUG! How do we get it fixed?
Hey there everyone, I posted on another tread about this issue, and I think I resolved it. Happy bluetoothing:
drewsky208 said:
I was having a problem not unlike yours, where I pair it the first time, and all is well, and the next time it doesn't do anything. I fiddled with my car's bluetooth (BMW ULF), and a headset and they would connect, after fiddling, but just not on startup. I finally determined that it appeared that the phone was not setting up a keepalive with the paired object. I found two reg keys in the bluetooth stack that were relevant. I changed them, and it now works exactly as you would expect every time!
Keys:
HKLM/Software/Microsoft/Bluetooth/Audiogateway
ConnectHFOnCall=0
The default is 1, which instructs to only connect on a call
PowerSave=0
The default is also 1, but this makes bluetooth be "awake" all the time
Change the settings, soft boot and you shoudl be good to go!
Hope that helps
Click to expand...
Click to collapse