Database Develop

For ALL PEOPLE HOT FIX BLUETOOTH BY HTC

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....

Fring - How did you install it?

Hi,
I am having trouble installing Fring on the latest Dutty Rom. Has anybody else experienced this problem?
I install the cab to either memory or storage and it still does the same thing... It just loads the splash screen up and hangs there?
I contacted fring about this problem and they replied with the following:
"Hello Colin,
Thank you for contacting our support team.
We are aware of the issue and working to solve it in the near future.
Make sure to check our blog for version updates http://www.fring.com/blog
Please feel free to contact us again should you have any further queries.
Thank you,
Neta
fring Support "
I see alot of people on this forum using Fring and I was just wondering how they went around installing it?
Thanks,
Colin Jensen

Worked fine for me on Dutty's V3 - I installed it and ran it with wi-fi turned off and was surprised that it automatically turned wi-fi on to connect.

Same here
Yeah, I got the same problem on my phone. I have had Fring on my before but it was acting buggy so I uninstalled it and looked for the newer version of it and tried installing it but I install it and like you said the splash screen comes up and just hangs.
Did you ever get it to work? I see that this is an old thread.
cjensen25 said:
Hi,
I am having trouble installing Fring on the latest Dutty Rom. Has anybody else experienced this problem?
I install the cab to either memory or storage and it still does the same thing... It just loads the splash screen up and hangs there?
I contacted fring about this problem and they replied with the following:
"Hello Colin,
Thank you for contacting our support team.
We are aware of the issue and working to solve it in the near future.
Make sure to check our blog for version updates http://www.fring.com/blog
Please feel free to contact us again should you have any further queries.
Thank you,
Neta
fring Support "
I see alot of people on this forum using Fring and I was just wondering how they went around installing it?
Thanks,
Colin Jensen
Click to expand...
Click to collapse

I had the same problem on my phone when I installed for a brief period of time last week. I ended up uninstalling......

i have installed the cab on a number of ROMS, never had any issue..

official tilt 6.0 rom didn't work, q mobile 1.2 rom didn't work...official tilt 6.1 rom, @ least it actually opens now (no more error screen) but doesn't get past loading. 3 roms, still haven't been able to get it working over here.

yep, confirmed, same problem, multiple roms, multiple ways of installing, multiple connections when opening program, Fring is still just stuck on the splash screen that says "Fring is loading" I had it working at one point in my Kaiser's life but nothing now seems to revive it, been trying for months, there are no fixes that I have seen online. Any good alternatives?

No problem so far.....
been using it for over 1month now....
installing and uninstalling for more than 8times
i justgot my kaiser....thats why with all thecustomization....
am using a russian Wm6.1 rom

I have the same issue
I tried every known fix that can be googled... I also contacted Fring... no help. It seems to be a huge problem with the 6.1 Roms. Someone here should have a fix...

Nope, it's fring's job to get it right, not much we can do... and they unfortunately dont seem to care much about WM6.1 users given the number of reports they've had for weeks/months about the problem and their everlasting "we're gonna investigate it" answer.

akadragon said:
I tried every known fix that can be googled... I also contacted Fring... no help. It seems to be a huge problem with the 6.1 Roms. Someone here should have a fix...
Click to expand...
Click to collapse
I have just installed Fring today on PDACornerUltimate ROM v15, it works properly.
I was able to make a SIP call to Fringe Testcall as well as SkypeOut call.

akadragon said:
I tried every known fix that can be googled... I also contacted Fring... no help. It seems to be a huge problem with the 6.1 Roms. Someone here should have a fix...
Click to expand...
Click to collapse
Yep, they just released a new version that works.

Language settings
I've the same problem with Fring that I've with google map.
My PPC regional settings are set to China, since it's the olny way to display chinese caracters everywhere in the OS (notice the OS is in English).
But, fring's language (like google map) is choosen according to those settings... it's very annoying.
Does anybody if there is a way to disable this feature (registry hack...) ?
Thanks,

Fring on kaiser
i just installed fring on my kaiser im using duttys_wm6.1 hybrid v2 and dont have a problem with it. it loaded up properly and everything seems to be working. my only thought is maybe a high amount of cpu usage, (programs that are running from start-up?) that is slowing everything down and causing the app to hang of freeze. thats just my thought. im probably wrong. anytime i have an issue with any kind of app freezing of not starting up thats usually were i look first. i hope that this helps. if not im sorry and at least i tried.
John

MMS/SMS Pics too small

Apologies if this has been posted before. (I couldn't find it in the Diamond archive).
Whenever I receive either a picture or video in a text message it is almost too small to see.
I am using an unlocked Diamond on O2 in the UK.
Thanks

Pics
You can edit the send recieve size limits in the reg.

Is there a difinitive fix for this yet? prefrably without altering the reqistry. I am still having this problem! o2 seem to be a bit stumped with it!

Is there anyone that can help here?
Who else is having this problem on o2 or even other UK networks. I think it really needs looking into but never seem to get any response.
o2 don't seem to be able to help us and all they suggested was xda-developers.
Personally I think it is o2 causing the problem and they just don't know how to fix it!!

It does seem like an o2 problem. A new Vodafone HTC worked fine. It received 3m pics from my old Nokia but when I tried to send a 3m pic with the HTC it failed. All I could send was a low res version. It arrived in full screen size, unlike the tiny ones I receive.

I don't seem to have any problems sending MMS's to people, just receiving them. They always come in at 3k. All settings on phone are fine regarding resolutions and download limits. All the same as my girlfriends XDA Ignito and hers works just fine. I just can't understand it.

This is an O2 diamond issue, as the diamond isn't supported by O2 when images are sent the sending server cannot recognise the phone and send it as a default image size, you need to fool the sending server into thinking the phone is supported.
follow this fix, worked for me: http://forum.xda-developers.com/showthread.php?t=359584
Regards
Craig

dikkytikka said:
Apologies if this has been posted before. (I couldn't find it in the Diamond archive).
Whenever I receive either a picture or video in a text message it is almost too small to see.
I am using an unlocked Diamond on O2 in the UK.
Thanks
Click to expand...
Click to collapse
Try To install the attached patch it worked for me on my touch pro and let me know if it worked

Excelent I will try this later tonight!!
Edit- Tell you what the search on this forum does my head in, Can never find what you search for!!

the guitarist said:
Try To install the attached patch it worked for me on my touch pro and let me know if it worked
Click to expand...
Click to collapse
Big thanks!!
This seems to have done the trick!!!
Rich

the guitarist said:
Try To install the attached patch it worked for me on my touch pro and let me know if it worked
Click to expand...
Click to collapse
Worked great. Thank you!

I know this thread is somewhat old, but these tiny MMS pics were driving me insane. I just wanted to express my appreciation.
Thank you. This worked perfectly on my unlocked Fuze.

Didn't seem to work on my diamond damnit!

Hot Fix for resolving the prolonged ring response issue in HTC Touch Pro

Hi Guys,
There is a new hotfix from HTC regarding the above issue here is the below link.
http://www.htc.com/europe/SupportDownload.aspx?p_id=140&cat=0&dl_id=502
Hot Fix for resolving the prolonged ring response issue in HTC Touch Pro Release Date: 2009-02-19 Category: Hotfix
The device will keep ringing for a few seconds after the caller hangs up the call. You may answer a phone call without anyone responding on the other and think it’s a dropped call, but actually it’s because the caller has already discontinued the call. If you encounter this problem, please install this hot fix to resolve this issue.
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 the hot fix, first select the check box below. Next, select the hot fix and the desired FTP site then click Download.
Copy the hot fix, which is an .exe file, to your device.
To install the hot fix, tap the .exe file and follow the on-screen instructions.
* If you perform a hard reset of your device, you need to reinstall the hot fix after the hard reset.

Unable to install: Incorrect version error?
Any ideas?

I called support and they said that might be for the previous version of ROM... and they will call me for the news...

bauerpavel said:
Unable to install: Incorrect version error?
Any ideas?
Click to expand...
Click to collapse
Same here...

Sorry guys, same problem for me too.
I dont mind if some mod can delete this thread.

Taking a look at the contents of the download, it looks as though the highest version of the OS that it will accept is 4.21 - I think this must be either an error in the packaging, or we've got a REALLY old fix. I tried to patch the EXE with a more up to date OS version number, but it was having none of it - it probably fails a checksum or something, and says that there's something wrong with the certificate, or that there's a file missing.
Maybe somebody could look to repackage it?
Cheers,
Steve.

http://www.htc.com/europe/SupportDownload.aspx?p_id=140&cat=0&dl_id=502
Keyword in there is EUROPE! Its not for USA guys its also not for CDMA.

xboxexpert said:
http://www.htc.com/europe/SupportDownload.aspx?p_id=140&cat=0&dl_id=502
Keyword in there is EUROPE! Its not for USA guys its also not for CDMA.
Click to expand...
Click to collapse
Last time I checked, the UK was in Europe.
Cheers,
Steve.

this is for GSM unlocked versions only just like the new rom that is out.
from what i hear the US CDMA versions are on there way.

bog3nator said:
this is for GSM unlocked versions only just like the new rom that is out.
Click to expand...
Click to collapse
Which is what I've got, and it simply won't install.
Cheers,
Steve.

Installed fine on my device.
The delay before the ringing starts seems to have grown shorter, but not by much.

Installed nicely on my TIR v11R-Based Raphael

Once again, North America is left waiting...as I understand it, this works only on European branded phones? I guess it is the branding at&t puts on them that causes the updates (for at&t phones) to be delayed 3-6 months.

Well I've no idea why it doesn't install on mine then as I have a HTC unbranded European Touch Pro with the latest released ROM on it.
Cheers,
Steve.

StevePritchard said:
Well I've no idea why it doesn't install on mine then as I have a HTC unbranded European Touch Pro with the latest released ROM on it.
Cheers,
Steve.
Click to expand...
Click to collapse
I have a HTC unbranded European Touch Pro with the latest released ROM, I have the same problem.

alonroz said:
Installed fine on my device.
The delay before the ringing starts seems to have grown shorter, but not by much.
Click to expand...
Click to collapse
try an app called diamond tweak. i think it has a setting to force the phone to ring as soon as call comes in

xternal said:
try an app called diamond tweak. i think it has a setting to force the phone to ring as soon as call comes in
Click to expand...
Click to collapse
Finally!!! Thank you very much for that tip! That problem has been driving me insane since I bought the phone, and finally its fixed =)

dafunk said:
Finally!!! Thank you very much for that tip! That problem has been driving me insane since I bought the phone, and finally its fixed =)
Click to expand...
Click to collapse
it doesn't off phone vibration?

Two official HTC's fixes for Diamond

Published today: http://www.htc.com/pl/supportdownloadlist.aspx?p_id=133&act=sd&cat=all
Descriptions:
Hotfix for resolving skipping during audio playback for HTC Touch Diamond
If you encounter skipping during audio playback, please download this hotfix to solve this problem.
Hotfix for resolving grayed out Repeat option on reminders for HTC Touch Diamond
If you can not uncheck the Repeat Reminders in Sound & Notifications in some circumstance, please download this hotfix to resolve the problem.
Good luck and good night...

Its not even compatible with the Diamond so wtf??

ainatar said:
Its not even compatible with the Diamond so wtf??
Click to expand...
Click to collapse
It depends on your ROM version. In my case only second (for reminders) fix is applicable.

Hahaha. Polish HTC can't release the polish ROM version (in fact - WWE ROM with 3rd party localization, and they say bull**** about being tested in microsoft), so they are offering the sound hotfix instead.
edit: oh no, the update is worldwide! So congrats to HTC Poland for pasting the link into their website.

These fixes are not only on PL HTC pages, and I think there are not related with HTC Poland.

I hope some peeps here can make the audio fix work for all ROM's as it won't install on mine

doesn't install on mine either.....

Help
Downloaded the audio fix and when it went to restart, it got to the "Touch Diamond" screen and froze up. Tried three soft resets, did not work, even broke down and tried a hard reset still froze on that screen, tried hooking up to the computer and turning on the phone, same thing.
Any help would be great.
Thanks
Fyi the touch diamond screen comes up then I see the gyrator info on the bottom of the screen then nothing, just stays there, going on a half hour now.

Says it's not compatible with my Diamond when I try to install to my official HTC 2.03 (swedish) rom... On the other hand I've never experienced the audio lag issue so maybe that explains it

guess its more a sloppy action from HTC, since the other hotfox works without a flaw.
Espeical since a user already made a cab that works with every rom.
http://forum.xda-developers.com/showpost.php?p=3644961&postcount=421

And when a fix for the GPS?

i m using nataly 2.2 ROM, cannot install that fix a well.
By reading the xml, seem like it install a OEM_Misc.dll ...dont know what that is. ....

Install the cab from here http://forum.xda-developers.com/showthread.php?t=505928&highlight=hotfix the one on post 10 (HTC Audio Hotfix.cab)
Has done the job for me.