Database Develop

Cing8125 users: 217 ROM w/CF2,ringers,themes and A2DP on ftp

I suspect this is as close to the perfect ROM as I can make for you folks, until I find something else universally useful to add..
This ROM has the following characteristics:
-Based on QTek 2.17.7.102
-OS 5.1.195 Build 1487.2.0.0
-Radio 02.07.10
-Protocol 412.1.03
-Includes assorted ringers, themes, OmapClock, and yes, A2DP
- .NET Compact Framework is integrated. It is build 2.0.5238.0
- .NET Compact Framework 1 has been left in. Build 1.0.4292.2
-Did I mention it has A2DP integrated?
-It is not coded to a specific carrier, so theoretically you shouldn't have to CID unlock. HOWEVER, I ask, no, I demand that you CID unlock before installing. Only then will you be allowed to grovel in the forum for help if you run into problems achieving a successful flash.
-Each morning at 7am it will gently vibrate, go start the coffee maker, fetch the newspaper, feed the dogs, and start your bath. Should you leave it at home it's likely to cuddle with your wife...it has no loyalties.
It can be found here until it gets moved:
ftp://xda:[email protected]_RUU_WIZARD_217_AKU2_WWE_CF2_A2DP.exe
If anyone asks me to make this ROM using 2.08 I'll send my legions of monkeys to harass and belittle you in public.

Thanks man, this is kick ass.

MY HERO!
Dude, you ROCK!!! You have made my decision to get this phone more and more worth it. Thanks again!

A2DP Not Working
So, I CID Unlocked and installed this new ROM successfully. Then I went to the connections screen and enabled bluetooth. Opened up Bluetooth Settings and created a new partnership with my Moto HT820. Went through all the normal steps and it found Hands Free and Wireless Stereo services on my headphones device. I saved the settings.
In 2.08/2.87, at this point I would press the right ear button, which would activate Wireless Stereo mode and I would see a music icon in the top bar. It didn't happen on this new ROM. Another method is to go back to the Bluetooth settings and click&hold on the device and you see a list of services (Hands Free and Wireless Stereo) and then choose Wireless Stereo. On this new ROM, only Hands Free is listed. If I choose to edit the device, it lists that Wireless Stereo is supported on the headphones, but it is not available as a mode on the phone.
I will be going back to 2.08/2.87 for now. Let me know If you happen to figure out what's might be going on.
Thanks!

Hey Summiter .... canyou? .... are you going to? .... I need? .... would you? .... nevermind can't think of anything

A2DP not working with HT820
I've successfully flashed this ROM and tried to pair Motorola HT820 headset but it was not recognized as Wireless Stereo. It was recognized like Hands-free only.
Anyone knows how to make it work? Thanks

Does this ROM still have the issue where the device won't vibrate from standby?
Also... for those of us just tuning in...
What's the benefit of having additional components (like CF) loaded through the extended ROM? When they're installed, will they live in ROM instead of taking up precious storage space? Or is it just the convenience of having everything install from one place?
Maybe Voice Commander in the next release...?

the non-vibrate thing is part of the rom, as MS made it that way. and voice command isn't free, so i doubt he'd include it in the rom.

amg212 said:
Does this ROM still have the issue where the device won't vibrate from standby?
Also... for those of us just tuning in...
What's the benefit of having additional components (like CF) loaded through the extended ROM? When they're installed, will they live in ROM instead of taking up precious storage space? Or is it just the convenience of having everything install from one place?
Maybe Voice Commander in the next release...?
Click to expand...
Click to collapse
CF goes to main memory regardless of the settings you choose at installation (you can choose Storage Card >>> it installs w/o error message to main memory).
You can see the appropriate files in the \windows directory. They all start with GACxxxx.
Cheers
hrb

Good Stuff...
One question though. Does this still have the battery indicator moved to the top. I just flashed yesterday without issue but I'm thinking the battery indicator can be optioned. Obviously this is a miniscule issue compared to the other great work you've done. Thanx guy.
J

the battery icon at the top is part of the AKU2.

darkjedi said:
the non-vibrate thing is part of the rom, as MS made it that way. and voice command isn't free, so i doubt he'd include it in the rom.
Click to expand...
Click to collapse
I was talking about Voice Commander - not MSVC

Oi Vey!
I'm all settled in on v2.87. everything works, wifi, a2dp, btaudio e.g.
What extras is this going to buy me??
Maybe I'll hold off for a little longer.
Still, thumbs up to Summiter. :wink:

as much as a pain in the ass it is, the 2.17 rom with A2DP is MUCH more stable than the test rom.

Hi Summiter,
I'm set to receive my 8125 this week. I've been doing as much reading and bookmarking as I can until I have the phone in my hands, but I haven't seen this question posted yet.
When a user loads your ROM, does the phone start at the beginning of the customization process (setting time zones, preferences, etc) or do your customizations piggyback as the defaults? What's making me ask is I see you've mapped your camera button to the omap 252 overclock setting and I'm curious what to expect when I load this ROM. Thanks!

100Tbps said:
Hi Summiter,
I'm set to receive my 8125 this week. I've been doing as much reading and bookmarking as I can until I have the phone in my hands, but I haven't seen this question posted yet.
When a user loads your ROM, does the phone start at the beginning of the customization process (setting time zones, preferences, etc) or do your customizations piggyback as the defaults? What's making me ask is I see you've mapped your camera button to the omap 252 overclock setting and I'm curious what to expect when I load this ROM. Thanks!
Click to expand...
Click to collapse
Your phone looses all setting and resets as if you just took it out of the box. Its a pain to do over but most of us have become pretty proficient at it with our mulitude of ROM reloads ;-)

Can anyone confirm that they have A2DP working on this ROM?
For folks that have reported not being able to get A2DP working - can you confirm whether the file "bta2dp.dll" exists in your windows directory? It's a hidden file so you'll need to set your file manager to view all files.
Thanks.

Is there an upgrade in one of these ROM versions for the Bluetooth? Im having issues with my 8125 and my BMW hands free car kit. My contact list doesnt show up on my display in the car. I had a SE 710a and it worked perfectly. With my 8125 I cant get the contact list on the hands free.

If you've CID unlocked previously, and you have 2.17 now, can you just use this ROM directly? Or is it necessary to downgrade and then CID unlock again? Sorry for the noob question.

Summiter...
There has been talk and concern about the 8125 erasing data on the sd card if you set your email options to save attachments to it. I was wondering if you knew anything about this and/or the new ROM version might fix the issue.

ATT WM6 (leacked) TO oficial Vodafone WM6

thous who allredy did or going to go from ATT WM6 (leacked) TO oficial Vodafone WM6 whot are the Advanteges and Disadvanteges ??

Couple of positives:
- Seems a bit quicker
- Doesn't have the AT&T junkware clogging it up
I am having a problem with Activesync however. I can only connect as Guest. It does not prompt me to set up a relationship. Unfortunately, I cannot synchronize. Anyone know how to resolve this?

Guest Only key
You need to change the key for GuestOnly in registry on your PC. It's located at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services". Find the key for Guest Only, and either delete the key entirely, or change the value to "0".

I think this is more of a side effect of the hard reset than anything else. I tried the official vodafone ROM against the leaked ATT rom, there was no difference except for the absence of ATT software. When I flashed back to the leaked ATT rom, it was just as fast. The only other difference seems to be that the vodafone firmware version is 1.47.02 whereas the leaked ATT is 1.47.25.

FreshJiveX said:
You need to change the key for GuestOnly in registry on your PC. It's located at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services". Find the key for Guest Only, and either delete the key entirely, or change the value to "0".
Click to expand...
Click to collapse
Thanks a bunch. That did the trick!!!

how about voice quality?
When I had the Vodafone ROM people complained that they can't hear me well and with the ATT everybody could hear me crystal clear.
can someone confirm they had the same problem

Vanilla Voda Rom?
Hi all. Just wondering. What do I need to do to make this Rom a vanilla one.
There are alot of folders and stuff when you look into the extended rom. I just do not want to delet something that is important for the normal functions of my phone.
Thanks

jeo100 said:
how about voice quality?
When I had the Vodafone ROM people complained that they can't hear me well and with the ATT everybody could hear me crystal clear.
can someone confirm they had the same problem
Click to expand...
Click to collapse
My 750, with WM5 (from factory) had problems when I would use the speakerphone. People would complain of not being able to hear well.
With the ATT leaked ROM (WM6), that problem still remained.
I am glad to report that with the latest, official Palm UK ROM (VFU) I am able to use the speakerphone at lengths with no complaints from folks on the other side. This is a great benefit for me as I use the speakerfone frequently.
As for the voice quality while holding up to my ear or over a BT headset, it's always been acceptable.

[SOLVED] How to have VoIP and GPS working in Diamond !

Hi,
I think it can be a solution for everyone who wants to use M$ VoIP and GPS in his Diamond (till today if you use VoIP, GPS goes dead).
IMHO problem was one file called dnsapi.dll in VoIP cab which overwrite original one in ROM. It caused that GPS goes dead.
I've removed this file from my OEM package and cooked a ROM with VoIP. I tested this and VoIP and GPS is working without any problems.
I using only OEM packages - if someone can make a cab file from attached OEM package and test it, maybe we will have a solution for everyone !
[2008-08-08] UPDATE - CABs can be found here - http://forum.xda-developers.com/showpost.php?p=2497988&postcount=8

Sound great!!
This is what i´ve been waiting for... fring does the trick... but BAD.
Sweet.

Good idea, a shame I don't know how to make a .cab.
None of the VoIP programs I tested work on the diamond (even Fring doesn't work properly...)

d3us said:
Good idea, a shame I don't know how to make a .cab.
None of the VoIP programs I tested work on the diamond (even Fring doesn't work properly...)
Click to expand...
Click to collapse
Fring and Skype 6.1 works fine on my Diamond and the GPS too.

halloj said:
Fring and Skype 6.1 works fine on my Diamond and the GPS too.
Click to expand...
Click to collapse
I'm not talking about Skype and Fring - issue was with VoIP drivers from M$. With that you can dial via e.g. Halonet from normal dialpad.
Anyone tried to make proper CAB? For chefs attached OEM package is ready to cook.

Hi,
I tried to make a proper cab, but apparently I failed
I damaged my original dnsapi.dll, now I have one with filedate
31.01.07; could someone upload the original one from a 1.37 rom?
Thanks,
Seven

mcseven said:
Hi,
I tried to make a proper cab, but apparently I failed
I damaged my original dnsapi.dll, now I have one with filedate
31.01.07; could someone upload the original one from a 1.37 rom?
Thanks,
Seven
Click to expand...
Click to collapse
Here you are...

Aaaah, thanks Saves me from Hardreset because the VOIP drivers wouldn't uninstall anymore... Have something in return: Here you have two CABs which do not install a dnsapi.dll, and tested them on my diamond. Works perfectly. You even dont have to reset the phone...
If feedback is positive, maybe the OP could change topic into "[solved]..."?
One tiny thing left to do: Change the ipdialplan.xml to make VOIP dial those "+1 (999) 1212 - 1212" numbers as well ^^
Thanks and enjoy,
Seven

what gps program are you using ?

iliescu902 said:
what gps program are you using ?
Click to expand...
Click to collapse
I've tested in HTC GPS Tool and Automapa (Polish navigation).
Anyone tried CAB prepared by mcseven?

I used tomtom 7, outdoor gps and mobile terminal emulator to see nmea records on COM4 directly. all 3 programs were running simultaneously and were receiving GPS.
I also tried to connect the VOIP to my asterisk, works as well, but cannot call any +1* numbers or numbers with brackets, since I dont know how to change the ipdialplan.xml in /windows...

I didn't know wich one of the .cab I should install so I installed both; I started with the drivers, it did nothing then I installed WM6Voip, it seemed to work. So I installed SIPconfigTool to configure my connection and I tested TomTom, the GPS was detected (whereas it wasn't with the original WM6Voip). Nevertheless, I tried to use my VoIP account over 3G but it couldn't connect (whereas Fring can connect).

works fine using tomtom 7 and GoSIP...

Yes, possibly the built-in VOIP cannot use STUN functionality, and fring can. I believe that to be a firewall issue.
However, now I seem to have that 5 seconds silence bug. I establish a connection, but 5 seconds into a call the diamond ceases to transmit voice. Receiving voice from the remote party however continues flawlessly. No Headset connected and not put into a docking station. Has anyone a similar problem or even a solution to that?

mcseven said:
Aaaah, thanks Saves me from Hardreset because the VOIP drivers wouldn't uninstall anymore... Have something in return: Here you have two CABs which do not install a dnsapi.dll, and tested them on my diamond. Works perfectly. You even dont have to reset the phone...
If feedback is positive, maybe the OP could change topic into "[solved]..."?
One tiny thing left to do: Change the ipdialplan.xml to make VOIP dial those "+1 (999) 1212 - 1212" numbers as well ^^
Thanks and enjoy,
Seven
Click to expand...
Click to collapse
I've installed both your CAB's. But i'm wondering why I can use VoIP to call? Should I have another program installed?

I've installed both your CAB's. But i'm wondering why I can use VoIP to call? Should I have another program installed?
Click to expand...
Click to collapse
Well, yes. Use a program called SIP config (anyone you like, I use this one) to program your provider settings into the phone. Then make sure to visit Settings->Phone->"Internet" Tab and change it from "Never" to a setting of your liking. After that (and pressing ok in the top right corner) it should register with your VOIP provider as soon as there is a data connection available. If your phone places a call via VOIP, it will ring a short audible "beep" prior to connecting. I found no way to tell it explicitly "use cellular network" or "use VOIP network" for placing a call. Perhaps this will be added in a later ROM.
However, now I seem to have that 5 seconds silence bug. (...)
Click to expand...
Click to collapse
I believe that to be a firewall issue as well. Yesterday I went home from work and put the phone directly into my home Wifi net with direct connection to my asterisk server. Everything works fine.
Today I used another access point at work, and it worked fine as well, so if you are having trouble getting voice to the remote party it most likely is your firewall's fault.
btw I have not found a way to use the internal=headset speaker, it will always use the loudspeaker for received audio.

wow, big THANKS.
works fine for me. Could connect to my Axon PBX with SIP and GPS also runs fine (Tested with tomtom7 and WMMiniGPS).
I realy waited for that and had also two hard resets behind me previous during tests

It almost works for me. I can connect, but my voice doesn't arrive to the other side of the line at all. Neither does the voice of the other side arrive to me. The line is open, but seems 'dead'.... what am I doing wrong?

ipdialplan.xml for sipgate in Germany
Fantastic, with the new cabs now GPS and WM6VoIP works. Attached a dialplan which I modified last year for my Kaiser. It works with my sip provider in Germany (sipgate) and you can dial local plan, leading 00 or + or 0. It may work also for others.

voip speaker
Great job!
Is there already any solution for the intern/extern speaker problem?

No Sound in Call (Intermitant)

Occasionally I have a problem where when making or receiving calls I pick up and there is no sound. If I Soft Reset I can make the call and it works fine. It's been starting to happen more often recently, and is really bugging me. It happens both when I'm using the phone speaker, and my headset.

what rom are you using? I have noticed the same thing the last couple of days since upgrading to L26 M2D v1

ah, here it is the same thread.
I use WM 6.1 htc version
Is there no bugfix?

Have you tried flashing a new radio?
Ta
Dave

data at info:
ROM: 3.28.407.0 GER
funkempfänger (i guess it's the radio): 1.65.16.25
protocoll: 25.83.40.02H
it was updated with the new htc 6.1 version what i've heard.
or can i downgrade it to a version that is working fine? when yes, where is the file to do so..

Right now I'm using Radio 1.58.16.27, I'll try another one, which do you recommend?

I was using 1.65.29.22, switched to 1.65.24.36 (I was using this with L26 diamond V12 with no issues)
had the same issue today.

hm, looks like a big upcoming problem for everyone...

what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff

virusv69 said:
what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff
Click to expand...
Click to collapse
Old thread but still, I've been experiencing this issue on the Hyperdragon series of ROMs from late October. Also had this problem in the past on some of Dutty's roms. The latest Raphael version (15/11/2008) has not exhibited this problem in 4 days. Only difference I can see is a slightly newer version of MSVC (1.6.19965).
Cheers.

gatewayer said:
hm, looks like a big upcoming problem for everyone...
Click to expand...
Click to collapse
I am getting the same problem intermittently, with a soft reset as the solution.
I am running a bone stock AT$T rom,recently upgraded to 6.1. It started happening post upgrade.
An upgrade problem?

same here... im playing around with different radios, it has to be a radio issue imo

I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine

1stPeregrine said:
I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine
Click to expand...
Click to collapse
My phone rings and notifies just fine when Texts,emails and calls come in. It answers just fine, but there is no sound. Then when I try to call people back, there is no dial sound and the call appears to not go through, until I do a soft reset, then all is back to normal.....................for a while.......................

I'm having this issue also. The other party can hear me when I answer, but I can't hear anything after the initial incoming-call ringing. A power-cycle restores normal operation but only for a while.
ROM: 3.28.405.0 WWE, 05/02/2008
Radio: 1.71.09.01
Protocol: 25.75.40.02.eMo

I'm in same boat as everyone else here.
Sometimes my phones rings, but when I answer I have no sound and other party can't hear me. Other times, my phone doesn't ring and all audio is muted (despite volume on). Soft reset is the only thing that works for me.
I gotta say this is really pissing me off. I'm missing lots of important calls because my phone doesn't ring when it should, or if I'm lucky it rings but has no audio so I have to soft-reset and wait 5 minutes for my phone to reboot & re-establish signal all whilst my clients are trying repeatedly to call me.
I'm willing to try other radios, but no one seems to have any working suggestions.
Thought maybe it was software, since I don't remember this happening after my initial WM6.1 upgrade. Uninstalling S2U2 didn't work (happened again today). Just uninstalled Voice Command, too, but haven't tested yet. VC's been flaky since upgrading to 6.1, working sometimes, failing to announce calls other times, plus occasional VC crashes at boot claiming "out of memory" which is blatantly untrue.
Just out of curiousity, is everyone with this problem using Voice Command, or just some of us?
Think I might have to go back to WM 6.0 since 6.1 didn't solve my Bluetooth issues plus screwed up Destinator...oh well. Schap's WM6 4.31 was best ROM anyway.

Anyone having any luck with this problem?
Like I said, I was running AT$T WM6 with no issues. The I updated to WM6.1 and started having these call issues.
Last week I flashed to HD III still no joy. SJ says that he is running the same radio as me, 1.65.24.36 with no problems.
Is it " my " phone? Microsuck 6.1 ? The radio ? Has anyone solved this with a new radio flash ?
I run a business on this phone and it is getting really frustrating, I don't want to go back to 6.0 just so I can get my phone calls?
I'm not just whining, looking for sucess stories.

Hi, havent been here in a while but i thought i'd add to the list. I have recently flashed HD3 (one of the early november editions) and it was without problems until friday when i dropped my fone. Ever since then i have had the intermittent sound in call which is only fixed by a soft reset (exactly the same as denco7). I haven't changed the radio since dutty's 1st diamond rom (a while ago) as i haven't had any problems but now im thinking about it.
Current setup (from device info):
ROM version: HD_III_Jade WWE
ROM date: 09/30/08
Radio version: 1.65.24.36
Protocol version: 25.94.40.06H
Not using MSVC

Recently flashed to HD III Blackstone hoping this might work but still having the problem.
I also flashed radios 1.65.24.36 and 1.70.18.02
and now I am running 1.70.19.09....... and it is still happening. It has got to be something in WM 6.1. Cannot be a software conflict, because it was happening when I was running bone stock AT$T 6.1 upgrade with no software add ons.
Again, I would hate to think that I have to downgrade to 6.0 just to get my phone calls.

Damn WM6.1 sound!
Well, I thought I'd let everyone know that I've uninstalled all my favorite apps from my Kaiser. No MSVC, no S2U2, occasional hands-free Bluetooth, and no A2DP. In that time, I've had only 2 incidents of no sound for the last 3 weeks--much better than no sound every few days or even several times a day. Don't know that the apps have anything to do with it since denco7 had same problem on an unadulterated AT&T ROM.
The big question is why do we all have the same sound problem but most WM6.1 Kaiser users do not (if everyone did I'm sure there would be a lot more *****ing). If we could reproduce it at will, we'd at least have something to focus on. Not knowing that, I'll have to guess and say that I suspect one or more of the following:
WM6.1 and/or the 1.65+ radios required for WM6.1 introduced some sound bug (deadlock, dereferenced pointer, etc.). The more apps that interact with sound and/or the radio, the more likely the bug will be triggered. But even if this is true, why does it happen to us but not to others?
The bug exists only in a particular base ROM source used by the ROM cookers. Still, should be affecting more people.
Maybe people who customize their phones are more likely to reset and clear any conditions that lead to no sound? Doesn't seem likely, but hey...
The problem exists only in specific Kaiser versions, perhaps even in conjunction with only specific WM6.1 builds and/or radios. I think there's been 5+ different hardware versions of the Kaiser line, but I can't find where I read this or how to tell what version your Kaiser is.
Bluetooth affecting sound? Got absolutely nothing to back this up other than WM6.1 supposedly fixed a lot of Bluetooth problems and during the time of my frequent lockups, I was using A2DP to stream an audiobook to my car's Parrot MK6000. Finished the audiobook & quit traveling so much, so I rarely used Bluetooth during the last few weeks when I've had only 2 no sound incidents. BTW, I upgraded to WM6.1 specifically because of the Bluetooth fixes, hoping they fixed the 100% CPU usage after finishing a hands-free call and fixed the A2DP dropping after calls. WM6.1 didn't fix either, so what did they do? Maybe their "fixes" just introduced new problems?
Possible dead zone f'ing up the radio and consequently sound? I offer this only because when I was working in a particular dead zone I had frequent sound problems. For some reason, my phone has problems reconnecting after leaving this dead zone and I have to reboot. Occasionally it would reconnect without rebooting, but I never correlated this to no sound. However, I haven't been there in weeks, and my problems with sound decreased (although I also uninstalled apps & quit using Bluetooth as much). Went there last Friday, and while I was there I found I had no Windows sounds. Could dead zones or even just temporary signal loss be f'ing up the radio and consequently the sound?
These are all just guesses--I'm just throwing out some possibilities so we can find something in common between us. However, I gotta say that if I don't find a solution soon, I'm going to switch back to WM6. Threaded messages are nice, but they're not worth this no sound headache.
BTW, I'm using:
AT&T Tilt (purchased within a month of initial release)
ROMeOS v4.21.1 (OS v5.2.20273, AKU 1.3.3)
Radio 1.71.09.01

Bluetooth not connecting via Microsoft sync on Ford vehicles

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