Blue toothe won't hang up - Touch Pro2 CDMA

Anyone have this issue or a fix? BT connects perfect, works, perfect, but the command to hang up on the BT device dosen't properly hang up, and the phones returns the #777 error.
It does answer from the BT device properly. It does with with my other cell phones.
TP2 VZW

I had the same problem with my Voyager Pro headset and found that if I hit the button once, wait a second and hit it a second time it hangs up. Maybe it will work for you.

I have the same issue.
Using Moto HT710 and VZW stock ROM

same issue in w/ 09 bmw nav/bt connection. I have to grab the phone and press the end button as it never hangs up.

cab might fix it
Over at PPCGeeks.com some have fixed the issue using the cab in this thread: http://forum.ppcgeeks.com/showthread.php?t=90155
I am having the issue with my Ford Sync system. I will test the results of the cab this afternoon and post them. Hopefully this works because it is fairly annoying.
Here is the cab if anyone wants it.

Well it didnt work for my Verizon TP2 and the Ford Sync system, hopefully someone else has better luck with it.

This seems to work for me. It hangs up almost instantly now. Thanks for the find.

rsbrown69 I am glad I could help, could you post which version of the TP2 you have (verizon, tmobile, ATT). I just want to know if it worked on another verizon phone or not, if so I will hard reset and give it another shot.

wlawyer said:
rsbrown69 I am glad I could help, could you post which version of the TP2 you have (verizon, tmobile, ATT). I just want to know if it worked on another verizon phone or not, if so I will hard reset and give it another shot.
Click to expand...
Click to collapse
I am using the mostly stock Sprint TP2. The only main modification I have done is the Touch Pro 2 cleanup http://forum.ppcgeeks.com/showthread.php?t=88640

Looking at the thread on PPCGeeks it looks like mostly sprint users having luck with the cab as well. Hopefully something will come along for the verizon version as well.

I have the Sprint version and have installed the cab. I do not see any improvement. I experience intermittent problems with or without the cab. It doesn't seem to make a difference. FWIW, I use the Jawbone Prime and Jawbone 2. Same with either.

Just out of curiosity did you do a soft reset after the install? I remember someone mentioning that in the original PPCGeek thread.

Yes, I did a soft reset. Actually, a soft reset with or without the cab seems to solve the problem....for a while. Then it shows up again. It is a bit strange.

doesnt work
I tried it on my Sprint TP2 and it does not work either. I installed it and did a soft reset and it still does not work for me either.
It would be the best thing that happened if it did work cause I use my BT all day and this sleep mode BT thing on the TP2 is cool for battery life but it sucks for using the BT feature which to me is more important than battery life and I have car chargers and usb chargers so I would rather have a working BT.
Does anyone have a cab or fix that will allow the BT to function like the old Touch Pro? That phone had a great BT even if the battery life was poor.
Thanks for the attempt to fix the issue but it is a no go here.

Does not work on stock VZW rom

Didn't work on my TP2 VZW either.

The one person that has responded that it worked had the cleanup cab installed. I am going to try a full reset and put only the cleanup cab and the bluetooth cab on and see if I can get results. Yeah this bug is that annoying to me. http://forum.ppcgeeks.com/showthread.php?t=88640

Ok I did a hard reset, programmed the phone, installed the cleanup cab, installed the bluetooth cab, joined the phone to my ford sync system, made a call, and guess what... the phone hung up beautifully using my standard steering wheel control for sync. There must be something in that cleanup cab that is either A) the actual fix or B) a necessary piece of the fix. Sorry but I am not going to hard reset again to test it, mine is working so hopefully this info can help you guys as well. On a side note that cleanup cab is pretty nice but read the thread to make sure you want/need all that is included.

wlawyer said:
Ok I did a hard reset, programmed the phone, installed the cleanup cab, installed the bluetooth cab, joined the phone to my ford sync system, made a call, and guess what... the phone hung up beautifully using my standard steering wheel control for sync. There must be something in that cleanup cab that is either A) the actual fix or B) a necessary piece of the fix. Sorry but I am not going to hard reset again to test it, mine is working so hopefully this info can help you guys as well. On a side note that cleanup cab is pretty nice but read the thread to make sure you want/need all that is included.
Click to expand...
Click to collapse
The cleanup cab alone hadn't fixed the problem for me so that is when I tried this threads fix. So far it works more often than not but it still does not hang up every once in a while. Must be a combination of things between the cleanup cab and this one but still not the correct fix, better but not enough.

Mine worked none of the time before, I basically had to wait for the caller to hang up or pull my phone out of my pocket and press end, so any improvement is huge for me. I am traveling this weekend and next week so hopefully I will have more info to report at least with my setup with Sync (never got into the earpieces, so not testing that).

Related

MS Voice Command not working..for many of us..

I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Atra said:
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Click to expand...
Click to collapse
What else do you have loaded on your phone(s) that have this issue. I use VC on all WM6 and WM5 roms that I've run (and ones I've cooked, like the Crossbow Reloaded ones you mentioned) and have never had this error and I've never tweaked around registry settings. I just install the cab and it works...
Are you installing VC 1.6 US?
With all the WM6 roms i've used (not as many as some but i'm new here) I haven't had an issue with VC 1.6 US either.
don't think it's a definite answer, but i did have this problem in the past when i installed voice command on my memory card rather than on phone memory. sometimes during loadup after a soft reset i would get that error...think it's because it takes longer to load from the card and voice command is setup to run right away (always in the background)...
if it's installed on the phone memory...dunno...sorry
I run VC 1.6 US and have never had a problem with it. I always install it in main memory.
I give..
Going back to WM5 Molski. To answer some of the post..
It's VC 1.6
No other software loaded..Fresh flash.
Installed to device, not storage *only option offered for install location*.
Get a message during device install: (...recommend installing to main memory. Do you still want to install to "."...) I answer Yes because it just aborts install to say No.
Thanks for the replies guys..
<--[Totally Screwed]
OK, now I have no sound from the speakers and Mic not working. While in Phone mode, the speaker button stays in the On position and won't turn off. Got the old Voice Command registry settings in place but it seems the new problem is the culprit. Going to start a new thread with new problem unless someone has any ideas..
Closing out
Back up and functioning on Molski 3.3 Crossbow. From what I can tell, during the WM 6 load, the speaker phone option became stuck in the On position but the speakers and Mic were not functioning. Voice Command seemed to know there was a problem and gave the "..restart VC.." message. After re-flashing Molski (a few times, still no joy), I flashed with the wired earbud/Mic connected. After flash and phone restart, I removed the headset while in phone mode. Speaker button reset to normal, phone speakers/mic started working again. Reloaded Voice Command and all worked.
aaahh the joys of PDAdome.. Where else can you get the thrill of accomplishment by getting back to the same friggin place
Thanks again for the replies all..
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Give Molski a try..
Avatar28 said:
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Click to expand...
Click to collapse
I didn't have any problems with his roms (..and went back to it with no probs). Only started having problems after I tried the Faria WM6. If the Molski works for you let me know. We'll give Faria a nudge.. Good Luck!
VC issues I've run across
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
At one point I had a strange issue with the bluetooth microphone.... VC would work fine (I'd ask "what time is it" and it would tell me the time) but when I was in a call, no one could here me.... I ended up enabling and then disabling auto gain control... wallah, mic works again.... weirdness.... (don't think this was rom related)
Anyway... the roms that I've had this problem with was XDA Mobile 6 (release 1... relase 2 is kicking a$$) and I think NBD 7.1... never had a problem with a ny Pandora cooked roms.....
Anyway... my $.02... (I'll probably get change)
kudo's to the rom wizards that be...
never had a problem. Installed in a few different roms. works fine
installed to main memory.
wolverine9827 said:
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
Click to expand...
Click to collapse
Voice Command Bluetooth Fix
View attachment 43147
I can't take credit for this and I can't give credit but Thank you...!
I've used this and has worked when VC w/n initiate via earpiece.
There's several threads on the specifics of this cab.

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

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?

Can't answer my phone!!

OK, I've been having this problem for a good couple of months now. About half the time that someone calls me, when I hit the Talk button on my phone it just mutes the ringer and doesn't answer the phone. Usually I try the 'Slide to answer' deal, and that just slides over to Answer and still doesn't do anything. I know the actual button is fine, it works great, i've tested it over and over again. I've changed HardSPL, ROM's, Radio's, etc. and I still see the same issue. What is wrong?! or is anyone else having something similar at least?
So I guess no one else has this issue, at all, with any ROM, radio, etc.?! I guess there must be something wrong with my phone. That kind of sucks.
schwags said:
OK, I've been having this problem for a good couple of months now. About half the time that someone calls me, when I hit the Talk button on my phone it just mutes the ringer and doesn't answer the phone. Usually I try the 'Slide to answer' deal, and that just slides over to Answer and still doesn't do anything. I know the actual button is fine, it works great, i've tested it over and over again. I've changed HardSPL, ROM's, Radio's, etc. and I still see the same issue. What is wrong?! or is anyone else having something similar at least?
Click to expand...
Click to collapse
I had the same issue with my htc mogul. These suggestions worked, give it a try (i will NOT take credit for these great tips/found them by searching):
dial ##778#/EPST/Modem Settings, change the slot cycle index number to 1
and or if that didn't fix it...
Take a look at your HKLM/Comm/ConnMgr/Planner/Settings/SuspendResume
It is a multi-sz value and should be #777. If it shows anything like ~GPRS or
something containing GPRS, change it back to #777 and soft reset.
Once I changed it back to #777, I can answer the call immediately when data is on, time and time again. Prior to this, there was a significant delay.
Please backup your phone prior to making these changes...
Good luck...
montecristo1 said:
I had the same issue with my htc mogul. These suggestions worked, give it a try (i will NOT take credit for these great tips/found them by searching):
dial ##778#/EPST/Modem Settings, change the slot cycle index number to 1
and or if that didn't fix it...
Take a look at your HKLM/Comm/ConnMgr/Planner/Settings/SuspendResume
It is a multi-sz value and should be #777. If it shows anything like ~GPRS or
something containing GPRS, change it back to #777 and soft reset.
Once I changed it back to #777, I can answer the call immediately when data is on, time and time again. Prior to this, there was a significant delay.
Please backup your phone prior to making these changes...
Good luck...
Click to expand...
Click to collapse
Thanks for the help, I don't know if I believe any of that though. First of all, the # codes are carrier specific, I have AT&T, what's your service? These codes didn't work at all for me. Second of all, I mentioned that I've changed ROM's numerous times, along with Radios, etc. and I still have the same issue. Maybe this worked for you, but for me it doesn't. I've been trying some stuff recently, re-flashing SPL, hardSPL, Stock ROMs, and I'm hoping the problem goes away although I'm not that confident. I keep thinking it must be physical as my phone's "talk" button works perfect. Every time I try it it always responds appropriately, except when trying to answer a call. Beyond that, when it does screw up, it at least mute's the ringer, so I know it's responding somewhere.
I'm not sure what to do about this. Guess I'd better just wait it out for a TP2 and sell this one and forget about it. Could be due to bad blocks, I've had numerous problems in the past that I've been able to pretty much prove were a result of bad blocks in the phone's memory. Oh well, thanks for trying, although none of that works!!
I assume he has Sprint.
I have the same problem answering calls too, and I think it's because of the slidetoanswer dialer. I'm using xECK29x's 6.5 ROM.
rccola159 said:
I assume he has Sprint.
I have the same problem answering calls too, and I think it's because of the slidetoanswer dialer. I'm using xECK29x's 6.5 ROM.
Click to expand...
Click to collapse
Thanks for the input, I think I'm going to try a different dialer for a while and see if that solves the problem. I wouldn't be surprised if that's the issue.
While his codes may be different (I'm also with AT&T), he may be onto something... I have had the same issue, but after reading this post, I have been watching, and the times the phone prevents me from answering are when I have had some sort of data (browser, GPS, etc) open in another window.
My 2 cents FWIW
schwags said:
So I guess no one else has this issue, at all, with any ROM, radio, etc.?! I guess there must be something wrong with my phone. That kind of sucks.
Click to expand...
Click to collapse
I have an unlocked euro touch pro and cannot answer a call by touching the onscreen answer button. It will continue to ring tho. I have gotten in the habit of just using the hardware answer key. I've flashed numerous diff roms and all are this way, even the htc updated rom from their site. The only one that worked was the oem rom preloaded on the phone from factory. Not a big issue to me. I just deal with it.
Have this problem with energy's Roms. If you are on his 3.0 still go into Start>Tweaks>Advanced Config. Scroll down to Phone, Click on Phone Skin then Disable it. The setup of the call is different. Be sure to re enter you voicemail for it is erased when you disable the skin. Worked for me. No problems here. BTW you must understand that any Rom you flash will not be perfect!
I also have the same problem. And i to beleve its the new dialer thing. will try and change it, although i realy like the way you can search a contact with it. The other one is just a litte to small i feel. Anyway thanx for a good tip.
I'm also running into the same problem. I'll try disabling the phone skin to see how that works out.
Thanks everyone for your input!! I was a little scared to see no one answer this is at first, but now I can see this is a common problem. The dialer has to be the issue here, I've been running a standard dialer (not the phone canvas) for a couple days now and it's been perfect everytime.
montecristo1 said:
I had the same issue with my htc mogul. These suggestions worked, give it a try (i will NOT take credit for these great tips/found them by searching):
dial ##778#/EPST/Modem Settings, change the slot cycle index number to 1
and or if that didn't fix it...
Take a look at your HKLM/Comm/ConnMgr/Planner/Settings/SuspendResume
It is a multi-sz value and should be #777. If it shows anything like ~GPRS or
something containing GPRS, change it back to #777 and soft reset.
Once I changed it back to #777, I can answer the call immediately when data is on, time and time again. Prior to this, there was a significant delay.
Please backup your phone prior to making these changes...
Good luck...
Click to expand...
Click to collapse
Hey, it worked! I can't thank you enough, as this has been bugging the heck outa me. My slot cycle index was already set to 1, but my SuspendResume setting in the registry was "GPRS_bye_if_device_off". I had gotten to the point that I knew my problem was related to having a data connection going, but I had no idea where to go from there, and had no luck when searching the forums for a solution. Now my phone answers almost immediately, even whan I have a data connection going. Thanks again.

Categories

Resources