Hi all,
This is my first post here. Been mostly at ppcgeeks.
I and others have been having a problem with my HTC Touch on Sprint ever since upgrading to a cooked WM6.1 ROM. I have tried to custom ROMs and both have the same issue. So I'm thinking that it's a 6.1 thing. It could also be that I'm not using the radio really made for my device. So I'm hoping someone here can help us.
The issue is that whenever I hang up a call using my BT headset (Jabra 5010 with the sliding arm but it happens with other models too), the ringer profile automatically switches between settings. Meaning, if I start on vibrate for example, after the first call is switches to Ring, after the second, it switches to no sound and so on. Very annoying. It is not set to Automatic. I do not have the profiles or the calender on the today screen (some people suggested that as a possible answer).
So if any of you know how to fix it or if oyu are having the same issue, please reply.
Thanks and it's nice to be a member.
Aryeh
Related
Hello. My first posting. I have looked to see if this has already been asked.... After using mute or vibrate function on my XDA 2s unit, and then switching to making a call or trying to receive a call I can't hear the dial tone, or the other person on the other end of the call. I can only make and receive calls once I soft reset the unit. This is becoming a regular occurence. Any ideas would be much apprecaited.
Craig.
same problem
I also have same problem. my XDA IIs often have a problem with the incoming/outgoing calls which is I can't hear the tone nor the person's on the other end of the call (but the person on the other end of the call could hear my voice). It often (not always) happens without the device had a recent setting change or running program so on one occassion it just handles the calls perfectly and suddenly the problem happens and I also have to soft-reset it to make it back to normal, and it is becoming regular.
This is unfortunately a well known bug that none radio upgrade could solve so far...
Look at : http://forum.xda-developers.com/viewtopic.php?t=40417
The problem seems to occur only when Bluetooth is off... So the solution is to turn Bt On (and then off if you wish so) and it's ok without soft reset...
The best way to avoid it is to let Bt ON but to uncheck "Allow other devices to detect me" (forgive me if the english translation is not accurate but my PocketPC is in French) in the Bt parameters to avoid power consumption.
It worked for me so have a try
My phone wont ring though, BIZARRE, this is not to do with the rom though as i think it was happening with schaps, really really strange.
Any ideas, I just get a phone icon where the signal strength bar is showing handset. No callerid flashing up, not even an option to accept the incoming call. I go to phone options and test the ring tone and it plays just fine.
maybe i should reflash the radio, on 1.50 at the mo which i recently flashed to downgrade from 1.51, any ideas?
maybe i miss something totally obvious.
bumppppp? anyone?
same happening to mine on ultra ultra lite re-furbished
i had to flash another rom, then it worked. when i flashed back to same rom it didnt work again. the problem started after i added some cabs and did my regular tweaks. even with the fresh install of the same rom after flashing another rom it still didnt work.. i even changed radios
i'm on ultra lite, and it seems nice. So you saying i should flash another rom then come back to ultra lite?
Ok,
I just reflashed schaps, then flashed ultra lite.
I STILL have this wierd problem, what's going on?
Is my fone knackered? Not much good if it don't ring!
the rom has been discontinued and he is fixing it
known bug.....wait until new relase
shame it's a nice ROM, nice un' quick. fixed yet ?
same here..
I noticed that no sound was coming out of the phone when i did a soft reset and the Schap's Rom boot up with the animation + sound didnt sound. Also my speaker phone does not work. Basically and audible sound does not work!!!! i tried flashing it with dutty's rom, still same problem.. any ideas?
Hope this helps in resolving this issue!
Hi. I've run into this issue myself too. Here's my environment:
Cooked ROM via Pandora's Kitchen 7.1 with 3.61 OS
Using Dutty's Touch Dialer (2G) option in BuildOS
Everything was fine with the ringer for a whole week. I then decided to be a bit adventurous and went to look for a 3g dialer because the Touch one is only 2G. I then settled for Schen's 3G dialer 2.0 and followed his instructions in installing it (install OEMSign2007cert.cab first, then the dialer, which was the one with the dialer directory option). I didn't install any colored background cabs as provided by his package.
When I tested the dialer (outgoing portion), it seemed fine. I couldn't test the 3G option because we don't have 3G here yet. The problem began when I received my first call.
I was able to hear the incoming call beep through my BT headset, but that was the only indicator of an incoming call, in addition to the phone icon above the signal meter in the top bar signifying an incoming phone call. Besides that, there were no other indicator such as a pop-up window showing incoming caller's info, phone ringing, or even the vibrate function. I have my phone set to vibrate and ring with the Ringer-Vision.wma as the default ring tone.
I tested the vibrate and ring setting in the phone configuration panel and both the vibration function and ring tone worked. I tried several configurations such as vibrate only, ring only, etc, in addition to other various ring tones of different format (wma, mid, wav). All resulted in success in the phone configuration panel, but in failure when an incoming call came in.
To test the phone function, I used a land line, a cellular line, and SkypeOut. All three resulted in the same failure observed above.
Given that the only thing changed after that week was the 3G dialer, I proceeded to remove it and reboot. It reverted back to the Touch 2G dialer. When the phone rebooted, I retried the above tests and all resulted in the pop-up dialog with incoming caller information (plus the two softkey functions), vibration function, and the proper ringtone.
With the above results, would it help you guys in further diagnosing and fixing this problem? We are slated to have 3G within the next few months and I would like to be able to use this function.
Thanks!
Edit update: One other thing is that I tested the above both with and without my BT headset on.
Quakie
I do understand what you are talking about how you tested out the ringers in the phone options menu.. but for me any type of sound does not work, i ran tests there no sound, speaker phone does not work, MP3 do not sound. The sound only works through a head set. And when im on a call i could hear the other person and vise versa. So the problem is the speaker just went out after a couple of days of having Schap's rom. I tired flashing another rom a couple of days after. No luck. Any ideas?
-thanks
Hi,
I am a new member here and I currently own a HTC Touch Diamond.
I am planning on buying a new phone only months after buying this one mainly because of two issues:
- When someone calls me, the phone only starts ringing after a few rings on the caller's side. I have missed many calls simply because of the delayed ring so by the time it does ring, the caller has hung up. Weirdly enough there is no delay in the phone lighting up and notifying the user of an incoming call, it's just the ringing that is delayed, so obviously it can detect the incoming call accurately and it is just a firmware issue. Originally it would be delayed by about 5 rings, but after a few modifications I've done from some websites, I've managed to reduce it to about a 2-3 ring delay. Either case the delay itself is unacceptable.
- The ring-tone volume is ridiculously low. I have tried all methods available such as manually adjusting the volume through registry hacks, using an application called Diamond Tweak, etc, but it simply is not loud enough.
I was wondering if anyone has experienced these issues before and if there is a fix for them now. I did a lot of research into fixing this in the past few months and to no avail. I have now given up but given that this forum is so active, I figured I might ask for help here incase there is a solution that has eluded me. By the way HTC customer support is useless. They fail to even recognize the problem and almost always conclude with a response along the lines of "we've forwarded you issue to the technical team and will get back to you if a solution is found." I am almost certain that will never happen and I am extremely doubtful that they've even bothered to forward anything to anyone.
I was hoping as a last resort that this problem could be solved by replacing the Windows Mobile OS with Google Android OS, but it appears Android OS is still not fully compatible with the Touch Diamond.
Anyway, any help with this would be very much appreciated. Thanks!
Yeah, this is certainly a problem on stock diamonds. It's primarily caused by the speed at which the phone can access and render the phonecanvas, as well as the playing of a MP3 ringtone.
The low-hanging fruit is to use a [.wav] ringtone which is played natively in WM6. Also, if you're willing to flash a custom ROM, there are several that use optimized dialers (I made one) with better responsiveness. If you search, you'll come across a few:
GenY D2X
GenY D2The incoming call latency used to annoy me, it's why I initially signed up to xda, but it's something I haven't even noticed in quite awhile. I'll attach a [.wav] ringtone for you to try out.
hey has anybody got the sound for the rigtones working yet
is there a fix ? patch ? etc....
thanks
search the threads and you will find your answers there.
seriously?
if you want info on whether or not the ringtone/external speaker issue has been solved, check the dev threads. If there is a breakthrough they will all have updated it already since its a problem plaguing all rhodium devices.
lilchicano said:
search the threads and you will find your answers there.
Click to expand...
Click to collapse
Come on, man this was his first post, I understand that it's frustrating when someone posts without having read the stickies, but it's posts like that, which are so decidedly unhelpful.
For example, this is a good response, it berates him for not having read but it also contains USEFUL information:
ambegojapes said:
seriously?
if you want info on whether or not the ringtone/external speaker issue has been solved, check the dev threads. If there is a breakthrough they will all have updated it already since its a problem plaguing all rhodium devices.
Click to expand...
Click to collapse
thank you fenny.
Ring tones are working
Ring tones are fixed in the latest build as of 08/30/2010, i.e. sound is working in general.
In my case to actually get the handset to ring on incoming calls, I had to conduct the following steps (before that only the silent option was available as a "ring tone"):
go to settings -> Dev tools -> media scanning. Perform media scan. After that the OS restarted and the phone started ringing. Yeah...
cheers
BTW, I just noticed that the media scanning has to be conducted each time one the handset is turned on, otherwise the phone is not ringing.
Can anybody confirm that?
In addition I am not able change the ring tones in settings -> sound -> incoming calls. Why is that and can this be changed?
Has anyone found that if they use their own ringtone, an incoming call only rings once? I've tried converting my ringtones from .mp3 to .ogg but it still only rings once. If I switch to a stock ringer, the an incoming call rings over and over like it should.
ringtones
my tounch pro2 with the latest blazin build will use any mp3 i chose to use as a default ringtone and will ring more than once and play the full song. But on the other hand my other cell has all the same setup but only shows silent only, so it could be just the headset itself and not the build.
edlokien said:
my tounch pro2 with the latest blazin build will use any mp3 i chose to use as a default ringtone and will ring more than once and play the full song. But on the other hand my other cell has all the same setup but only shows silent only, so it could be just the headset itself and not the build.
Click to expand...
Click to collapse
It's the card. Format it with the HP tool. Full format. Also, BLAZN is pretty outdated (9.28 was the last update).
Had some issues with the touch tones not working correctly with the speakerphone enabled. Didn't find any threads here on XDA but found a few over on a couple other android forums.
Basically it seems that when using the touch tones with speakerphone enabled, the mic picks up the speaker phone and the receiving end hears each touch tone twice.
I had the issue when trying to call verizon wireless to enter my passcode, as well as trying to setup my voice mail. I have 3 separate Galaxy Nexus phones in my family, and the issue can be replicated on all 3 phones.
Also noticed lowering the volume on the speakerphone can alleviate the issue too, but it's just kind of annoying as I don't want to hold the phone up next to my ear when I'm trying to enter things on the dial pad.
I've also tried switching the DTMF setting between long and normal, the problem still exists
Hoping with a firmware update they can filter out the touch tone, or just not make the touch tones audible to ourselves. (I'm assuming
this is because the speaker is so close to the mic on the GN)
Anyway, I don't think there's a fix for it yet, but I'm just posting here to see if anyone else is experiencing the same issue, and to make people aware of it.
Also found the issue on google support here:
http://code.google.com/p/android/issues/detail?id=24467
Bump,
Anyone else run into the same issue? Or have some secret fix I don't know about? (Other than turning off the speaker lol)
Sent from my Galaxy Nexus using XDA App
This explains the problems I was having the other day trying to join a Go-To-Meeting - would not accept my pin.
I was on speaker phone too - ty for this !
I've had this problem on the GN and other devices as well. Sometimes I'll hit mute because it helps but also I don't want people/computer listening in.
_Gir_ said:
I've had this problem on the GN and other devices as well. Sometimes I'll hit mute because it helps but also I don't want people/computer listening in.
Click to expand...
Click to collapse
Just realized this before I came to post, thanks for pointing it out too! Mute FTW!!!
i too noticed this as well when i first got it and think that it ridiculous that it wasnt thought out better.
Another fix: Simply turn off audible touch tones in the settings menu.
Drawback is there's no feedback for the dialpad, anyone know of a way to get the vibrate on for the dialpad?
ConanOBrien said:
Another fix: Simply turn off audible touch tones in the settings menu.
Drawback is there's no feedback for the dialpad, anyone know of a way to get the vibrate on for the dialpad?
Click to expand...
Click to collapse
This is the workaround I've been using for about a month now with no issues. I had the same issue where the conference call service wasn't getting my pass code entered correctly.
Only issue now is the headset echo heard by connected parties, which has been reported and hope to be fixed soon. I've tried several workarounds here but none have been bulletproof.