2 Updates for Cruise on Htc e-club - Touch Cruise General

6/16/2008
Hot fix for resolving Bluetooth headset sound problem that occurs when reconnecting with HTC Touch Cruise
If you are using the Bluetooth headset, “Jabra JX10”, “Jabra BT500” or “Samsung WEP 150”, and the headset becomes out of range or undetected by the HTC Touch Cruise, in certain circumstances, you may be unable to hear any sound from the headset even after it has reconnected successfully with HTC Touch Cruise. Please install this hot fix to improve the connection when using the above-mentioned Bluetooth headsets.
6/16/2008
Hot fix for resolving unsteady Bluetooth headset connection with HTC Touch Cruise
When you are using a Bluetooth headset and the HTC Touch Cruise goes to sleep/idle mode, the Bluetooth connection becomes unsteady in certain circumstances. The Bluetooth headset may reconnect and disconnect intermittently. If this problem occurs, please install this hot fix onto your device.

Thanks for the update. I downloaded both of them, but I get an error when trying to install "Please use the correct version to install this Hotfix Program". I haven't seen this error before, so I'm, not sure what it means.
Dave
omaga said:
6/16/2008
Hot fix for resolving Bluetooth headset sound problem that occurs when reconnecting with HTC Touch Cruise
If you are using the Bluetooth headset, “Jabra JX10”, “Jabra BT500” or “Samsung WEP 150”, and the headset becomes out of range or undetected by the HTC Touch Cruise, in certain circumstances, you may be unable to hear any sound from the headset even after it has reconnected successfully with HTC Touch Cruise. Please install this hot fix to improve the connection when using the above-mentioned Bluetooth headsets.
6/16/2008
Hot fix for resolving unsteady Bluetooth headset connection with HTC Touch Cruise
When you are using a Bluetooth headset and the HTC Touch Cruise goes to sleep/idle mode, the Bluetooth connection becomes unsteady in certain circumstances. The Bluetooth headset may reconnect and disconnect intermittently. If this problem occurs, please install this hot fix onto your device.
Click to expand...
Click to collapse

I install both too without any problem

omaga said:
I install both too without any problem
Click to expand...
Click to collapse
Hmm. Are you running a WWE version ROM?

I use the Swedish WM6 rom at the moment

I'm currently on udk Vega R3 and am seeing the same error message "Please use the correct version to install this Hotfix Program".

Can it be so that you cant install the fixes if you have cooked rom??

omaga said:
Can it be so that you cant install the fixes if you have cooked rom??
Click to expand...
Click to collapse
Could be, but I'm using the stock WWE rom. I sent an email to HTC support, and they said that there were no patches available for the Touch Cruise, which is kinda confusing since the patches are on the HTC E-Club web page.
Dave

dfields said:
Thanks for the update. I downloaded both of them, but I get an error when trying to install "Please use the correct version to install this Hotfix Program". I haven't seen this error before, so I'm, not sure what it means.
Dave
Click to expand...
Click to collapse
- 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 performed a hard reset of your device, you need to reinstall the hot fix after the hard reset.

Problem Installing Patches
I to have the problem of "worng version"
i am using a cooked ROM
has anyone with cooked WM6.1 ROM succeeded installing the patches???
is there anyway to circumvent this error??

Reyjabs,
Not sure what you're getting at here. I've copied the file (multiple times), ran the exe(s), tapped OK as per the on-screen instructions, then I get the error. I'm running a stock rom, and I haven't done a hard reset.
Dave
reyjabs said:
- 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 performed a hard reset of your device, you need to reinstall the hot fix after the hard reset.
Click to expand...
Click to collapse

dfields said:
I sent an email to HTC support, and they said that there were no patches available for the Touch Cruise, which is kinda confusing since the patches are on the HTC E-Club web page.
Click to expand...
Click to collapse
Very odd comment no patches availble for Cruise? that is just what you can wait of htc, no one nows nothing.. so typical
The fix install just like a cab file and then it softreset when tick ok, another thing is then if the fix helps

omaga said:
Very odd comment no patches availble for Cruise? that is just what you can wait of htc, no one nows nothing.. so typical
The fix install just like a cab file and then it softreset when tick ok, another thing is then if the fix helps
Click to expand...
Click to collapse
DOH!!! Solved the issue. I forgot that I had been trying to get the BlackBerry Connect software to work, and during that I had changed the AKU to 0.4.2 since there were many posts that said that sometimes is needed to get the software to install/work correctly on other devices. I eventually gave up since it seems that no one has been able to get the BBC software to work on the TC. I changed the AKU back to 0.4.5 and the patches installed OK. Now to see if they work.
Dave

Please what is AKU
Can you explain what you did so mybe it will work on my cruise too...

Guy.xda said:
Can you explain what you did so mybe it will work on my cruise too...
Click to expand...
Click to collapse
if you use Total Commander you can change the registry value of Aku. mine was set at .1.0.2
I changed this to .0.4.5 and i could then install the patch.
HKLM\System\Versions\Aku

Yeah that's correct I'm not aware of anyone who's been able to get the Blackberry Connect software working on the Cruise. Ended up enabling Push mail on the exchange server, works like a charm and much better than the laggy BC software.

hambola said:
Yeah that's correct I'm not aware of anyone who's been able to get the Blackberry Connect software working on the Cruise. Ended up enabling Push mail on the exchange server, works like a charm and much better than the laggy BC software.
Click to expand...
Click to collapse
Yeah. I use push for my home email, but wanted the BBC for my work email. Can't use push there since we're still on Exchange 5.5....Oh well. Might be able to do it when corporate takes over the email...
Dave

i installed both patch on my italian cruise.
it resolve my problem with motorola HS850 bluetooth headset (after 3-5 sec of conversation i can't hear nothing).
my headset was not listed in patch description.

Where???
member.htc.com

"6/16/2008
Hot fix for resolving unsteady Bluetooth headset connection with HTC Touch Cruise
When you are using a Bluetooth headset and the HTC Touch Cruise goes to sleep/idle mode, the Bluetooth connection becomes unsteady in certain circumstances. The Bluetooth headset may reconnect and disconnect intermittently. If this problem occurs, please install this hot fix onto your device."
LMAO!! I e-mailed the support about this multiple times, funny how they mentioned nothing of an upcoming fix.
I wish I had saved the e-mails - but basically they denied that anyone else had this problem, and they gave me a list of headsets that they had "tested" on the cruise...and they went on to say that just because they had "tested" them, didn't guarantee that they would actually perform how they should. I went on to say that I had tested my headsets with other devices, and they had absolutely no issues.
It's great that they fixed it finally (I'm installing right now, hopefully the fix actually works)...but why do they have to be like that?

Related

HTC Bluetooth Hot Fix

Hi,
HTC today posted a hot fix for bluetooth at their e-Club.
Description:
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.
Br,
Mads
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
Extracted madsnm's posted cab, which is the same as nadavi's. This is a replacement file for OEM\OEMDrivers\TIInit_4_2_38.bts (a.k.a. \windows\TIInit_4_2_38.bts for non-chefs).
I've re-attached it as the naked file (without the cab installer or the self-extracting exe installer).
Any decent chef should be able to figure out how to turn a single file into an OEM package
Edit: Forgot to add that there are no registry entries, as I've already created registry dumps before/after install...
Edit3: It *IS* the same as the one in the AT&T 1.60 ROM. I did a file compare and there are no binary differences.
Although I am not having any problems as mentioned in the fix log, but the idea of HTC releasing something for us is great .
taiseer999 said:
Although I am not having any problems as mentioned in the fix log, but the idea of HTC releasing something for us is great .
Click to expand...
Click to collapse
Thats right!
Waiting for WM6.1 ROM! or maybe new WM06 Full Touch rom from HTC....
Just my two Cents....
Nadavi
Nadavi said:
Thats right!
Waiting for WM6.1 ROM! or maybe new WM06 Full Touch rom from HTC....
Just my two Cents....
Nadavi
Click to expand...
Click to collapse
well, 6.1 ROM doesnt really looks appealing to me, i believe most of us would want our freaking D3D driver to improve our kaiser speed.
come'on HTC, give us our driver. We want our kaiser to work @ its full potential!
almost forgot, to the brothers at the top 3 post, THANKS for sharing!
Solved my "bad" connection to the BT carset - thx....
ruffruff said:
well, 6.1 ROM doesnt really looks appealing to me, i believe most of us would want our freaking D3D driver to improve our kaiser speed.
come'on HTC, give us our driver. We want our kaiser to work @ its full potential!
almost forgot, to the brothers at the top 3 post, THANKS for sharing!
Click to expand...
Click to collapse
OT but the driver is there. Look here for more info. There's also an XDA thread on this. We just need to tweak it out for general purpose acceleration.
Sleuth255 said:
OT but the driver is there. Look here for more info. There's also an XDA thread on this. We just need to tweak it out for general purpose acceleration.
Click to expand...
Click to collapse
It doesn't say much if they hacked something for Coreplayer, or it was a general fix from HTC for all Windows Mobile devices running the MSM chipset.
Would be nice if the Kaiser was as snappy as that dual-keyboard Pantech running WM6 Standard.
I'm at loss to say if all the UI (and general system) lag is from too much use of .NET, lack of hardware accelerated graphics drivers, or Pro just runs slower than Standard because of the touch-screen support.
Hmm...wonder why i didn't get an email from the e-Club about this. I log into the site and find the fix just fine but I thought I'm supposed to get a notification about it (i'm pretty positive that was my preference when signing up)
Anyway, does this hot fix help in pairing bluetooth with car kits and devices that had problems or were incompatible thus far.
I've never experienced dropped calls with my BT connection, but I do have another problem that is pissing me off.
I have two different Pioneer stereos in two different vehicles. The AVIC-Z1 and the Premier DEH-P980BT.
When I first try to initiate a call with the 980, the connection is made, but the audio is somewhere in limbo between the phone and car speakers. There is a BT connection, but it takes about a minute and a half to actually start sounding through the speakers. By that time, the receiving end has hung up.
Since it only happens for the first call of the ride, I've been getting in the car, calling my voicemail, and waiting until I can hear the voicemail prompts. After that, I can make and receive call normally until I shut the car off.
If this fixes the problem I'm having, I'll be ecstatic.
Hi,
I have no noticable problems with BT exept the sound quality. Will be anything better or maybe worst if I install this upgrade? Does anybody have experience on it?
Thx
Mikus
NuShrike said:
It doesn't say much if they hacked something for Coreplayer, or it was a general fix from HTC for all Windows Mobile devices running the MSM chipset.
Would be nice if the Kaiser was as snappy as that dual-keyboard Pantech running WM6 Standard.
I'm at loss to say if all the UI (and general system) lag is from too much use of .NET, lack of hardware accelerated graphics drivers, or Pro just runs slower than Standard because of the touch-screen support.
Click to expand...
Click to collapse
Sounds like they had to change something with the drivers. So they're there but poorly implemented. And sounds like they'll give us driver info once its released. I'll buy it if it fixes the D3D support!
Still garbled on my Tilt with an Infinity G35..now how do I deleted the Kai6492_HotFix from my Programs directory? I can't see to find it...yet the icon is still there. Any one know?
Flapjack said:
I've never experienced dropped calls with my BT connection, but I do have another problem that is pissing me off.
I have two different Pioneer stereos in two different vehicles. The AVIC-Z1 and the Premier DEH-P980BT.
When I first try to initiate a call with the 980, the connection is made, but the audio is somewhere in limbo between the phone and car speakers. There is a BT connection, but it takes about a minute and a half to actually start sounding through the speakers. By that time, the receiving end has hung up.
Since it only happens for the first call of the ride, I've been getting in the car, calling my voicemail, and waiting until I can hear the voicemail prompts. After that, I can make and receive call normally until I shut the car off.
If this fixes the problem I'm having, I'll be ecstatic.
Click to expand...
Click to collapse
here's what causes that issue on my phone:
hit the ms voice command button and hear the beep prompt.
now hold the button down till you get the cancel beep.
now make a call. you will get no audio either direction.
turn the phone off, and the sound starts working. turn it back on and it's gone again.
key the ms voicecommand button again and let the time expire instead of holding to cancel.
make another call, and the audio will be fine, except for a 5 to 10 second delay.
see if this is how your phone behaves also. if I don't ever cancel a ms voicecommand by holding the button down, everything seems to work fine.
After installing the "fix" I could no longer use voice dial with any of my bluetooth headsets. Uninstalling the fix fixed it.....go figure.....
I think that HTC really need to have more, serious, knowledgable beta testers to tryout this stuff with various software and hardware scenarios before releasing the device. Some of these "bloggers" that they send new, unreleased devices to are either cronies or don't know much, or will not test the devices thoroughly and/or report back to HTC what problems that they experienced. I am a Verizon and AT&T user. Have seen these anamolies between diferent devices for some time now. The Mogul and XV6800 don't have the same issues we have, however, I guarantee you they do have others such as the De-activated GPS flaw that happened recently in the Mogul.
Unfortunately my Kaiser didn't work still with this hotfix. I installed on my device few times, I rebooted the headset and nothing. Probably it's like that because my ROM is 1.83, it's original polish version of it. How can I resolve the problem of bt headset ?
The fix file is a CAB (download from HTC e-club)... I install the CAB and find a link under software menu... I tap it... and another installation is done... I must soft reset the device... and stop...
Okai... so I think in this way the fix is gone... but... I have yet the cab installed under Software CAB and Installed application... can I uninstall it? The trashes pissing me :-D
or for att users go here....
http://forum.xda-developers.com/search.php?searchid=8811535

WM6.1 and MS Voice Command

Did anyone get it to work on wm6.1? i install it and it installs, but when i try to go to settings it will not go any farther. I like to have in say whos calling. Its a feature i can't live without! any help would be appreciated!
wolfskin
I think this is a problem when using the "official" 6.1 base. When I load it, it freezes after the install (like when it tries to load the "Help" file) and I must SR the phone. The next boot will be fine until it seems to start the Voice Command program, at which point will freeze the device. I had to hard reset to recover.
Others have reported Dutty's and other 6.1 releases not based on the "official" ROMs work with Voice Command.
i have it installed, haven't noticed any problems or than it needs to be tweaked to anounce calls. all other features, buttons, menus work.
i cant resist this one
READ THE FORUMS
http://forum.xda-developers.com/showthread.php?t=365118&page=6
1.6.1722 works out of the box for me, even launches from the headset. HOWEVER, it totally doesn't recognize ANYTHING I say! Totally the opposite of my normal experience. Normally I have to install ZaJules BTCommand, enable, reset, disable, reset to get the headset launch to work.
Hmm, I'll have to try another version.
***Update***
after radio update it is working PERFECTLY! Also it does seem to make a big difference which minor version of MSVC you're using - 1.6.17913 is what I have, my manager has 1.6.4xxx and his won't work from the headset after trying all my common tricks (although he's on Dutty v4, not 6.1)
Mine works with Schaps...
I am the same way, i must have MSVC for my blutooth carkit...Schaps is the only one i could get it to work well on; however, I din't try it on Dutty's
Just Tested on Alex's WM6.1 Home BETA 2
Works Great.
No problems...works on WM6.1
OK Guys... Do this test... Press and say "play music", it will ask you by saying "what do you want to play?", say "Anything" ( one of the choices), and let me know if it works.
I have dutty V3 and it works fine. On any wm6.1 rom, it will freeze. That is what I am experiencing with VC.
Same Here, no issues (Except the caller id anouncement)
Works fine for wm6.1 and its fine with my parrot carkit actually bluetooth audio much much better now
WM6.1 VoiceCommand 1.6 US
Works fine here - in fact BETTER than with original TYTN release where it would often hang just after hoing the lookup till you hit the Red Phone Key.
Now that it sounds like BT volume is better with 6.1, has anyone taken the time to compare registry settings between WM6 and WM6.1 to see what the differences are?
asking it to play music, and than anything works for me, no issues.
Laubscherc said:
Same Here, no issues (Except the caller id anouncement)
Click to expand...
Click to collapse
Did you go into Settings-Personal-VC and check "announce incoming callers"?
Mine is working completely without any hacks.
In the official 3.03 used in Alex's 6.1 Beta 1, MSVC didn't work for me, crashed the settings.
Now with Alex's Beta 2 he used official 3.02 and MSVC works perfectly.
asfoor said:
OK Guys... Do this test... Press and say "play music", it will ask you by saying "what do you want to play?", say "Anything" ( one of the choices), and let me know if it works.
I have dutty V3 and it works fine. On any wm6.1 rom, it will freeze. That is what I am experiencing with VC.
Click to expand...
Click to collapse
I am experencing the same issue,
I have dutty V4 and it works fine. On any wm6.1 rom, I get the Voice Command.asx error message (The file Voice Command cannot be open. Either it is not signed with a trusuted cerification, or one of it components cannot be. found. If problem persists, try reinstalling orrestoring this file). Ireinstalled several this and soft reset also, but the issue still remain.
Help!
MELPHBOY said:
I am experencing the same issue,
I have dutty V4 and it works fine. On any wm6.1 rom, I get the Voice Command.asx error message (The file Voice Command cannot be open. Either it is not signed with a trusuted cerification, or one of it components cannot be. found. If problem persists, try reinstalling orrestoring this file). Ireinstalled several this and soft reset also, but the issue still remain.
Help!
Click to expand...
Click to collapse
Use Kaiser Tweak in disable the trusted certification.
alltheway said:
Use Kaiser Tweak in disable the trusted certification.
Click to expand...
Click to collapse
Not true....
The Voice Command.asx is NOT part of Kaiser Tweak Menu. There are only two certificates to disable or enable. Even if you were to disable both the WiFi certificate announcement or the BT Certificate announcement, the VC.asx certificate right violation still shows when you request or command the VC, and will not respond to the command.
Did you locate the certificate disable/enable on your phone Kaiser Tweak before you decided to post your response?
Unless you can prove me wrong, I AM WAITING.........
pkley said:
1.6.1722 works out of the box for me, even launches from the headset. HOWEVER, it totally doesn't recognize ANYTHING I say! Totally the opposite of my normal experience. Normally I have to install ZaJules BTCommand, enable, reset, disable, reset to get the headset launch to work.
Hmm, I'll have to try another version.
***Update***
after radio update it is working PERFECTLY! Also it does seem to make a big difference which minor version of MSVC you're using - 1.6.17913 is what I have, my manager has 1.6.4xxx and his won't work from the headset after trying all my common tricks (although he's on Dutty v4, not 6.1)
Click to expand...
Click to collapse
What radio did you upgrade to ? just tried all 3 and still doesnt work for me

Can't turn on the bluetooth

hello,
unfortunately i cannot turn on the bluetooth from comm manager, it turns on and after 1 second is off again.
any solution for this problem?
thanks.
I have had this problem before and unfortunately am having it again. Only solution I have ever found for this is a hard reset and then reinstalling all your apps. If you try to restore from a backup from Sprite Backup, for instance, the problem remains. This would lead me to believe that it's a setting or a registry issue somewhere but I haven't been able to locate exactly what would be causing it and don't know enough about programming in WM to write something to figure it out.
Not a great answer but there it is.
db
MegaHz said:
hello,
unfortunately i cannot turn on the bluetooth from comm manager, it turns on and after 1 second is off again.
any solution for this problem?
thanks.
Click to expand...
Click to collapse
Hi, I have a Uk version of the touch cruise and I have the same problem. I just did a hard reset but the problem remains. Turning bluetooth on is impossible. It just try's to turn it on and shuts it off immediately.
Maybe it has something to do with GPRS? I am always connected to the internet. I tried to disconnect but then bluetooth still doesn't work. Can anyone help? Thnx!
No one has a clue?
I had this prob with bluetooth and wifi following the use of wmwifirouter- after hard reset and no wmwifi all goes well...
On a French SFR rom
any other idea?
Same problem... beginning to wish I'd gone all Apple and bought an iPhone. Anyway.... To trun it on, I had to go to Comm Manager>Settings>Bluetooth>Mode>Turn on Bluetooth. That worked despite the Comm Manager still showing Bluetooth as "off".
It only connects 1/2 the time to my headset or handsfree in the car
Otherwise, the phone crashes only once a day! Great! Thanks!
ok, great to see more people having the same problem but i hope that someone has a sollution...
When I try to turn bluetooth on in the communications settings i get a message saying there is a hardware error! :S
Ohw btw, I'm not using any router programs or other and my WIFI works fine.
has anybody of you having this problem tried to change to another rom?
if yes? did this worked?
any news on this?
No news, I don't want to try for a different rom because i don't think it will change anything. It just seems like its a faulty device which is a real shame. I've already contacted the place where i bought it and see if i can get a new one.
I also have problems with my microphone during calls, photo camera does often not work and the touchpad reacts very slowly to my touches. Very annoying!!!!
Yup, am returning mine to HTC aswell. Not even sure I want it back. WiFi stopped working too, and then it stopped receiving text messages, and everyone said they couldn't hear me when I called them. Great
Some of you guys got a bad device, there are thousands out there working properly.
If some of you guys flashed a newer Radio, the one form the test-ROM, then this is your problem.
And some of you guys have a quite gay branded ROM (slow responsiveness of touchpad). The original HTC ROM on the FTP and even more so a cooked ROM would solve alot of your problems. But be aware, flashing without having a backup ready is going to void your warranty if you want to exchange it having a custom/non-original ROM on the device.
What's up Schaggo
I am experiencing the same problem these gentlemen are mentioning and my ROM is not gay or lesbian. It is the original one.
TC is my 7th HTC device and I can see the quality of the ROMs decreasing a lot on every new device. I feel like HTC needs a real competitor to move up its arse quicker.
All I can say is that it really annoys me to hard reset this [email protected] everytime I "accidentally" use a native feature called Flight Mode. By bluetooth seems to fly away and never get back.
Lots of time the GPRS settings have to be reconfigured too. Some people I know have problems with GMail IMAP4 accounts when sending messages after some time. I never had this problem on my Kaiser neither on my Niki.
The lack of a video driver really is an egg on our faces, because I can't believe my ole Qtek 9100 responds quicker than these "all the bells and whistles" Qualcomm 7200 super-duper geared up devices.
So, if you feel like not contributing, please do not mess around.
Your signature tells me you are a wise man, but your comments show me otherway.
-Feaps
PB of BT still there with custom rom
MegaHz said:
has anybody of you having this problem tried to change to another rom?
if yes? did this worked?
Click to expand...
Click to collapse
Hi
I've tried many custom rom and the PB continue. "PB with the hardware oh BT".
Hard reset doent change anything.
my initial rom (SFR France) was working
custom rom (blackwidow + Bepe 058) are buging...
nedd some help !
Thanks alot for that input feaps. I guess I have to clarify a little bit.
My answer was supposed to be pointing in different directions. The first and general information I tried to contribute was, that it is not a common Polaris problem to have a broken Bluetooth unit. Which doesn't help at all to ppl affected, but it should tell them, that they probably got a bad device and should exchange it first before blameing htc in general and shouting for an iPhone.
It only was partially directed at specific persons. At madinga for example: did you try hardresetting your device? It could be a corruption in your system which causes all those problems. I doubt it though, if you suffer the loss of so many functions at the same time I suspect the mainboard to be broken. But nonetheless, hardreset it, see if its working, BEFORE you put your backup back on the device again since that could restore the corruption. If it doesnt work, exchange your unit, I hope you'll get a working one back.
My second line was directed at all people which have overwritten their original Radio with the 1.58.25.14 originating from the HTC Test ROM which can be found on the ftp server. The Bluetooth part of that Radio is flawed and leads to the problems described in this thread. I quite nicely pointed that out and told people where to have a look before shouting around. I do know that because I tried it myself and couldnt get my Bluetooth devices working. Once I flashed the original Radio back, my BT problems were gone.
And my third line - in which I may chose the wrong words, 'gay' for example - holds information targeted at people with for example the branded french SFR ROM or the original HTC french ROM. The SFR ROM is just horribly branded and if you go through the threads here you'll find people complaining about problems which then turn out to be related to the ROM. The french HTC ROM is flawed as well, it has severe problems with the volume control. I don't exactly remember what it was, but it's a flawed ROM, thats for sure. The German o2 ROM isnt flawless either, I know that because I originally had that ROM. Once I flashed my orbit 2 with the original HTC WWE ROM, I found it to be working alot better and smoother than with the o2 ROM originally provided. And this is where my last line comes into play: if you suffer problems related to your currently flashed ROM, they could be diminished by flashing an alternative ROM. But if your device is broken, and I personally and strongly believe that everybody fooling around in this forum should be intelligent enough and able to determine the sense of my words, eg. if he/she suffers a ROM problem or if the device just simply is dead and take appropriate actions.
And now to your contribution feaps. I feel personally attacked by your words. Thats why I defended my words in all the paragraphs above. Trust me, I've had enough mobile devices of all sorts to know what it means to get a not working once. Its frustrating and makes you want to throw it out of the window. And being able to see the quality decrease over time is just another drop on a hot stone. I agree. But be honest, if your BT unit works and stopps working once you engage a software based function, the problem is software related, dont you think? As for the GPRS settings, I cant tell. Since I use a free ROM which has the wizard built in (o2 removed it from their ROM) I didnt switch my SIM and the configuration worked, automatically and every single time. And I do use IMAP as well on my personal E-Mail account. Until now I didnt run across any problems, so I cant give you any feedback on that either.
So rethink again if I mess around or not or if I actually try to contribute and help the freshmen, coming into this forum and flashing whatever they find and breaking their devices. And recommending to flash the original HTC ROM, which should be/is the base for everything floating around, breaking your devices, is a serious input to everybody.
Edit: I forgot to add, pointed at nooms, there are cooked ROMs out there which stupidly have the new, flawed Radio baked in. Which Radio are you on? Try Start > Settings > Tab System > Device Information > Tab Version. Are you inadvertedly still on Radio 1.58.25.14 or back to (original) 1.58.21.23?
Hi everyone,
I agree with Schaggo completely. Most of the time problems have something to do with the software on the device. But I a not a tweaker like most of you guys, i've just bought my first (and hopefully not last) HTC phone. If i have problems of some kind, all i can do is reset the thing. A hard reset if necessary. I've done that many times. I can't change the software that comes standard and i don't think i should be the one who has to do that. Shouldnt HTC be doing that??
Anyway, Bluetooth keeps saying it has an hardware error. My radio version is a standard 1.58.21.23 but isnt finding any radiostations here in holland. Is it also broken? (sorry, i know, its a bit off topic)
You're right
schaggo said:
(...)
My answer was supposed to be pointing in different directions.
(...)
And now to your contribution feaps. I feel personally attacked by your words.
(...)
But be honest, if your BT unit works and stopps working once you engage a software based function, the problem is software related, dont you think?
(...)
As for the GPRS settings, I cant tell. Since I use a free ROM which has the wizard built in (o2 removed it from their ROM) I didnt switch my SIM and the configuration worked, automatically and every single time. And I do use IMAP as well on my personal E-Mail account. Until now I didnt run across any problems, so I cant give you any feedback on that either.
(...)
So rethink again if I mess around or not or if I actually try to contribute and help the freshmen, coming into this forum and flashing whatever they find and breaking their devices.
Click to expand...
Click to collapse
Well put. Sorry for being rude, but I keep seeing people offending others day after day in this forum that used to be high level; but that doesn't mean I should act the same way.
I totally misread you and please accept my apologies.
My ROM is: 1.25.405.1 WWE
ROM Date: 12/11/07
Radio Version: 1.58.21.23
Protocol Version: 25.65.30.04H
One thing I could notice is that HTC has a flaw in the Flush HKCU to Permanent Memory While Shutting Down. Some keys are not written.
One example is the MagiCall (an app I use) registration key. The software maker had to write a flush app for doing that. Another example is the Start>Settings>System>Error reporting. No matter what you chose, after a power cycle or a soft reset, it always go back to "Disable...".
I have, also, already tested the device after the hard reset with no extra apps on it. Same lame behavior on BT...
So, SW QA levels are really dropping fast on new HTC models. That is pretty bad.
But anyway, I have an open case with HTC and if I find something contributive I will toch base with this thread.
Once again, sorry for being rude.
Best,
-Feaps
Furio83 said:
Anyway, Bluetooth keeps saying it has an hardware error. My radio version is a standard 1.58.21.23 but isnt finding any radiostations here in holland. Is it also broken? (sorry, i know, its a bit off topic)
Click to expand...
Click to collapse
Then I guess you most probably got a bad unit. I guess the only solution at this time is an exchange.
The Radio-Firmware doesnt control the FM Radio btw The Radio-Firmware controls connections to the providers network, Wireless LAN and Bluetooth. But the FM Radio seems to be really bad in the Polaris, a lot of ppl I know complain about it.
feaps said:
please accept my apologies.
Click to expand...
Click to collapse
No problem dude! There is no need for such an excessive appology. We are in a Forum and people have different oppinions and I think its totally acceptable to shout at each other. I just wanted to express that I'm not in accord regarding your judgement of my post. But thanks a lot, I seriously really appreciate it!
Yes, your device seems pretty standard to me and the scenario you described logically made me think of a software error. But this seems very unlikely now. I'm out of ideas for the moment then, I guess you have to return or exchange it too.
You are perfectly right about the dropping SW QA though. You can notice the registry glitch in other areas as well: backlight timer always reset to 30 sec, and there are more settings all over the place which don't get saved properly.
Again, no problem, everybody lets be cool
Bluetooth doesn't turn on
I have the same problem. Did anyone find a solution?
Also camera fails to initialize, touch pad is sometimes very slow for initial reaction. I have NO added programs beyond manafacturer originals and have tried a number of hard resets. Doesn't help.
Jeremy

HELP!!!!!

Until about 3 days ago the sound on my phone worked perfectly, I have installed dutty's rom for about 1 month ago. On friday or something the sound simply dissapaired from the phone, and now I am only able to hear sounds through headphones/earplugs.
I have discovered that if i press the wheel on the side inwards, the sound returns as long as I am holding my finger there. What is causing this, and how can i possibly fix it?
I can't anylonger hear when the phone is ringing or anytthing
What radio are you using? Try updating your radio and reading the wiki.
http://wiki.xda-developers.com/index.php?pagename=DuttySeriesKaiser
Problem: I have no sound.
Solution: You need to install a Windows Mobile 6.1 radio.
Click to expand...
Click to collapse
List of Kaiser radios:
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Radio
From what I get he didn't flash anything new or change anything? I would try a hard reset and see if that fixes it if not flash a new ROM and Radio that is known to work and if that doesn't work trade it for a refurb from your provider.
I just tried both hard-reset and installing a new rom. It is not working as I have seen yet. I don't think its a hardware error because i have never lost the phone on ground yet, and it has never been in contact with water. I have also tried to reset the software, but nothing helps
I also can't remember installing a software or making any changes other then gps fix previously before the problems started occuring. Might it be possible that somehow a change or something somewhere have made my phone uncompitable with the current radios?
As I said previously, I get trough the headphone. the odd thing is that i get the sound on the phone back if i press the scrollwheel inward a bit hard. I think there is a registry error or something somewhere.
Though this is very annoying because I can't hear when the phone is ringing. The phone is too big to be in my pocket, and then i need to keep it in my jacket.
I would be grateful if anyone could provide a solution to this-
though i have read through the wiki, and I find it strange that a rom and radio that previously were working, suddenly stops working.
amik5 said:
though i have read through the wiki, and I find it strange that a rom and radio that previously were working, suddenly stops working.
Click to expand...
Click to collapse
I fully agree. I have the same problem with all Dutty's ROM. Once I pair the bluetooth device the first time and have it connected, from then on the sound goes to bluetooth headset. Thus, I miss calls if I am not wearing my bluetooth headset 24/7.
When the bluetooth headset is disconnected, still there is no sound from the phone. Again, I miss calls.
The Radio which I use with Dutty's ROM is alway included in the ROM.
Maybe, some registry settings?
KOR!
But the strange thing here is that the sound worked perfectly until some days ago, but maybe i should try to just reset the whole phone back to its original setting, and then reinstall everything?
I think its just annoying that something like this occurs when the phone is working perfectly.
Though i don't need to wear headsets when i am talking in the phone; the inbound speakers are working as they are supposed to
Ok, i have tried every radio possible now, and none of them works
amik5 said:
Ok, i have tried every radio possible now, and none of them works
Click to expand...
Click to collapse
Try to install a different ROM which has built in Radio with the ROM. Such as this:
http://forum.xda-developers.com/showthread.php?t=381837
Hope this is helpful.
KOR!
flash it to original radio and rom, if it still does not work i think it's time to get that replaced. you may have to warranty it.
How do I do that? If there is any help, I have 2 other htc kaisers at home if there is possible to retrieve anything from them
amik5 said:
How do I do that? If there is any help, I have 2 other htc kaisers at home if there is possible to retrieve anything from them
Click to expand...
Click to collapse
Just flash some other ROM and see what happens. Either flash the ROM from the link I have given or flash the original ROM.
Spend half an hour and you will know if it is software or hardware problem.
The easy way is to download the ROM from the link given above and let us know the results!
KOR!
Same problem here. I noticed that it only happens after pairing it with bluetooth. I was on the ROM for a month before i pair it with bluetooth and then voila ... no sound.
However, my problem can be temporarily solve by resetting the phone. I was about to flash to the latest Dutty's and see how...
amik5 said:
Until about 3 days ago the sound on my phone worked perfectly, I have installed dutty's rom for about 1 month ago. On friday or something the sound simply dissapaired from the phone, and now I am only able to hear sounds through headphones/earplugs.
I have discovered that if i press the wheel on the side inwards, the sound returns as long as I am holding my finger there. What is causing this, and how can i possibly fix it?
Click to expand...
Click to collapse
You should have made this post in the thread of the ROM you're using!
You don't have a signature so we don't know what the @#$% you have on your phone.
It's not like Dutty only has 1 ROM out.
There's several individuals who go thru Dutty's threads & help individuals like yourself.
So, if you post there....you will get the help you need.
Moderators.....please close this useless thread !
Leechoonhwee said:
Same problem here. I noticed that it only happens after pairing it with bluetooth. I was on the ROM for a month before i pair it with bluetooth and then voila ... no sound.
However, my problem can be temporarily solve by resetting the phone. I was about to flash to the latest Dutty's and see how...
Click to expand...
Click to collapse
Has anyone tried reinstalling the BT then.
Leechoonhwee said:
Same problem here. I noticed that it only happens after pairing it with bluetooth. I was on the ROM for a month before i pair it with bluetooth and then voila ... no sound.
However, my problem can be temporarily solve by resetting the phone. I was about to flash to the latest Dutty's and see how...
Click to expand...
Click to collapse
Just tried Dutty's April 1 (no April fool) ROM and it doesn't have the above problem. Here is the link for it:
http://forum.xda-developers.com/showthread.php?t=380991
KOR!
In the future, please reply to an existing thread when reporting problems. Please do not create new threads.
If you're not sure why this thread was closed, see the forum rules or watch this video.
Resetting the Rom
I have a phone where the hardware is malfunctioning, and i want to send the phone back for repair. The only problem is reinstalling the previous OS.
I had originally a norwegian OS (1.56.409.8711). I do have acess to another kaiser with the OS i want, so is there anyway to retrieve it from the phone?

2 problems with cruise

I have these 2 issues if anyone could help out that would be great
1. I'm having trouble with windows update whenever i try the update from the settings menu this error shows up "connection to update server was not available. check your data connections settings and ensure the device date and time are correct", however on my side everything is ok i think
--- any idea what to do?
2. I'm also having trouble connecting my phone to my laptop via bluetooth, i don't know how to solve this one either please help
Thanks
somji0 said:
I have these 2 issues if anyone could help out that would be great
1. I'm having trouble with windows update whenever i try the update from the settings menu this error shows up "connection to update server was not available. check your data connections settings and ensure the device date and time are correct", however on my side everything is ok i think
Thanks
Click to expand...
Click to collapse
As there exists no update - just don't do it!!
TDO
i hear what you saying.. but i find it weird its not working anymore before i would update properly and just tell me no updates availalbe just recently about 1 day ago its starts giving me this problem havn't done anything different to the phone have not added any new programs .. very strange i find
somji0 said:
2. I'm also having trouble connecting my phone to my laptop via bluetooth, i don't know how to solve this one either please help
Click to expand...
Click to collapse
Any leads you can give us? Error messages, description of the error, ....
Anybody with "working" Windows Update, PLEASE, publish the registry settings in your [HKEY_LOCAL_MACHINE\System\Autoupdate].
Example (official english ROM 1.25.405.1. WWE from 12/11/07):
---------------------------------------
(WARNING, something below does not work since corrupted):
[HKEY_LOCAL_MACHINE\System\Autoupdate]
"Automatic"=dword:00000000
"ClientLCID"=dword:00000409
"DetectionCookie"="JVs7o87q5UixJ+vDOyhzoAMAAAD/AgAAAQMAACICAAAcAAAA6gAAACMCAAAdAAAAAAMAABEAAAAbAAAAX/3//z35//88+f//"
"FirstTime"=dword:00000000
"IntervalEndTime"=dword:000000f0
"IntervalStartTime"=dword:0000003c
"LastCheck"=hex:\
00,13,0a,f2,e6,d5,c8,01
"LastResult"=dword:00000000
"NextRunNormalInterval"=dword:00093a80
"OmaDmSessionTimeout"=dword:00000258
"OTA"=dword:00000000
------------------------------------------------
Have you paring your Cruise with your laptop via BT?? do that first, and you have/can surf with your phone so the connection settings are allright??. If you have this 2 done right all you do is open Internet Sharing->Bluetooth PAN-> connect and go to BTnetwork on your laptop klic connect and you are in the net. I use my Cruise as a modem and its works just perfect!! I use a BT Dongle, have no BT built in my laptop
Look here http://www.wifizard.com/tutorialsXP/generic_bluetooth_pan/index.htm
hope this help
What are you doing with the Windows Update?? you never find anything. totaly useless.
igoivo said:
Anybody with "working" Windows Update, PLEASE, publish the registry settings in your [HKEY_LOCAL_MACHINE\System\Autoupdate].
Example (official english ROM 1.25.405.1. WWE from 12/11/07):
Click to expand...
Click to collapse
---------------------------------------
(WARNING, something below does not work since corrupted):
[HKEY_LOCAL_MACHINE\System\Autoupdate]
"Automatic"=dword:00000000
"ClientLCID"=dword:00000409
"DetectionCookie"="JVs7o87q5UixJ+vDOyhzoAMAAAD/AgAAAQMAACICAAAcAAAA6gAAACMCAAAdAAAAAAMAABEAAAAbAAAAX/3//z35//88+f//"
"FirstTime"=dword:00000000
"IntervalEndTime"=dword:000000f0
"IntervalStartTime"=dword:0000003c
"LastCheck"=hex:\00,13,0a,f2,e6,d5,c8,01
"LastCheck"=hex:\00,BE,5F,2D,92,A8,c8,01
"LastResult"=dword:00000000
"LastResult"=dword:80004005
"NextRunNormalInterval"=dword:00093a80
"OmaDmSessionTimeout"=dword:00000258
"OTA"=dword:00000000
------------------------------------------------
However, I get reply "No updates available at this time" (which is true, AFAIK).
Thank you, Bodisson, for publishing your /autoupdate data. Unfortunately it is not enough to make "working" Windows Update.
As far as i know there aren't any update packages... so even if WU works it won't do anything...

Categories

Resources