Anyone else having a wierd loud noise when a call waiting comes in? I fisrt got this after flashing radion 3.42.30 and dcd 3.2.2
I flashed to dcd 3.23, and it was still there.
I re-flashed the radio, and its still there.
jtg
(33)
yeah, I recently noticed it as well. It sounds like an alarm of some sort. Very annoying
omg yes it happened to me last night. That is horrible. Anyone have any idea what that could be? I am running DCD3.2.3 with 3.42.30 radio
I had that exact thing happen with the 3.42.02 radio from the official sprint rom. I recently switched to 3.42.30 and I've yet to experience it again. Infact I just tested it before I made this post. I know thats not much help since you all have the .30 radio, but just wanted to pass along my experience. I guess the only other thing I have done differently is before I updated the radio to .30 I switched from SPL 2.40 to 2.47.
Perhaps try doing a fresh install of the radio and then the rom+cab?
JerrytheGreat said:
Anyone else having a wierd loud noise when a call waiting comes in? I fisrt got this after flashing radion 3.42.30 and dcd 3.2.2
I flashed to dcd 3.23, and it was still there.
I re-flashed the radio, and its still there.
jtg
(33)
Click to expand...
Click to collapse
i heard it was a diamond call waiting sound if so i hate it
Hmmm...I guess I should go look for a new radio and see if it changes.
Any of the heavy hitters want to chime in?
dcd? gc14?
rickyrecaro said:
i heard it was a diamond call waiting sound if so i hate it
Click to expand...
Click to collapse
No way....It is a ear screeching sound that stops you mid sentence while talking. I was like "Holy S***t, One second please my phone is acting up" to a customer I was talking with.
i just get this weird little noise in the beginning of a outgoing call, and for some reason the phone app itself pops up after i close a window to an app.
i get that alarm sound too. its kinda random. sometimes on BT it sounds fine. but its not the radio its the rom i think. i never had the issue when i was on 3.0.4 and 3.42.30
DCD bug?
kflipproductions said:
i get that alarm sound too. its kinda random. sometimes on BT it sounds fine. but its not the radio its the rom i think. i never had the issue when i was on 3.0.4 and 3.42.30
Click to expand...
Click to collapse
DCD-u reading this? Do you think we've got a bug? I'm on alltel--others--is it carrier specific?
What dialer are you using?
the vogue dialer-dcd's default
I'm using dcd's kitchen, no OEMs added, just enterprise, entertainment, vc, and everything else as defaults.
I'm on alltel, I do use activesync with exchange, spb pocketplus, google maps, livesearch, htc gps viewer, and wififofun2.
jtg
gc14 said:
What dialer are you using?
Click to expand...
Click to collapse
Diamondish Black Titan Dialskin v.2.23
kflipproductions said:
Diamondish Black Titan Dialskin v.2.23
Click to expand...
Click to collapse
It's not the custom dialer that is doing this, because the custom dialer is just a skin (images) .
It's the Vouge Dialer found in the kitchen.
I cooked the Vouge dialer and got that annoying sound when ever I have call waiting.
I did not use the kitchen just the dcd rom 3.2.3 and radio 3.42.30...It is really getting annoying now.. anyone have any ideas?
I have the call waiting problem too. I first hear the regular call waiting sound followed by about five loud beeps that sound like someone keeps pressing a button on the other end.
It's not the custom dialer that is doing this, because the custom dialer is just a skin (images) .
Click to expand...
Click to collapse
Not every custom dialer is just a skin with images.
My thoughts
If you happen to own an old phone with caller ID that doesn't support call waiting/caller id, then you will hear a very similar sound. I believe that loud noise is actually the caller ID info being sent, on a standard pots phone it's only sent once, but it's possible that cells send multiple bursts in case the phone misses one of them.
Then again, I, who know nothing, is just giving my 2 cents on this.
BTC
gc14 said:
Not every custom dialer is just a skin with images.
Click to expand...
Click to collapse
True. But I was referring to the custom dialer he is using. Because I helped create it.
Related
Hi
I downloaded from HTC website the hotfix for bluetooth
Kai06492.CAB I installed the file and deleted the cab file now I have an icon showing the hotfix as a program!!
I have deleted the cab and soft reset my phone and i still have the icon on my program files.
does anybody has the same problem? how can I delete it from my programs
Thanxs
the icon in the programs menu is just a shortcut (in /windows/start menu/programs/) im sure you can just delete the shortcut and have it gone from the menu
defaultdotxbe said:
the icon in the programs menu is just a shortcut (in /windows/start menu/programs/) im sure you can just delete the shortcut and have it gone from the menu
Click to expand...
Click to collapse
Thank you very much!
I haven't heard of such a fix before. Does it work? I went to the HTC site and could not find it. I searched this whole site and could not find it. Does anyone have a copy please.
AGY said:
Hi
I downloaded from HTC website the hotfix for bluetooth
Kai06492.CAB I installed the file and deleted the cab file now I have an icon showing the hotfix as a program!!
I have deleted the cab and soft reset my phone and i still have the icon on my program files.
does anybody has the same problem? how can I delete it from my programs
Thanxs
Click to expand...
Click to collapse
From the name of the CAB and from this post, http://forum.xda-developers.com/showthread.php?p=1750060 it appears that this is for the Kaiser. Can anyone confirm that this works for the Titan/Mogul? If so, this might be the Holy Grail to get Bluetooth working on my PPC-6800.
Has anyone tried this, and can confirm or deny if this fixes any Bluetooth issues on their Titan/Mogul?
what bluetooth issues are we talking about now (since 2.17 came out, my BT has been perfect)?
Dishe said:
what bluetooth issues are we talking about now (since 2.17 came out, my BT has been perfect)?
Click to expand...
Click to collapse
I haven't had my Mogul that long, but with the DCD 1.6.10 kitchen and either my Blueant Z9 or my Plantronics 510, I sometimes lose my BT connection if I have my headset in my right ear and the phone on my left hip or even in my left inside jacket pocket.
With MSVC 1.6, about half the time I get asked to repeat my command, but it never accepts the repeated command. I think this is the same problem as VC confirmation, which is known not to work on the Mogul.
When VC does understand my command, it takes 5-10 seconds before it repeats it back and acts on it, and most times the voice is very low volume and scratchy.
To JimSmith94,
FYI...
Bluetooth radio waves do not travel through water and since the human body comprises of 70% water, you may lose signal if your BT headset and phone are located on opposing sides of your body.
I wear mine on the same side and never lose BT signal...
xweaponx said:
To JimSmith94,
FYI...
Bluetooth radio waves do not travel through water and since the human body comprises of 70% water, you may lose signal if your BT headset and phone are located on opposing sides of your body.
I wear mine on the same side and never lose BT signal...
Click to expand...
Click to collapse
Yes, I am aware of how Bluetooth works. The point I was trying to make, but apparently didn't, is that I had none of these issues with MSVC 1.6 and my PPC-6700. It seems that Bluetooth in general and MSVC specifically don't work nearly as well on my Mogul as they did on my Apache.
If no one else has these issues with the Mogul, could this be a kitchen issue, or a hardware problem that I need to talk to Sprint about, and see about swapping out my phone?
JimSmith94 said:
Yes, I am aware of how Bluetooth works. The point I was trying to make, but apparently didn't, is that I had none of these issues with MSVC 1.6 and my PPC-6700. It seems that Bluetooth in general and MSVC specifically don't work nearly as well on my Mogul as they did on my Apache.
If no one else has these issues with the Mogul, could this be a kitchen issue, or a hardware problem that I need to talk to Sprint about, and see about swapping out my phone?
Click to expand...
Click to collapse
The BT drivers on the titan do not work as it should and M$VC 1.6 does not work with WM6 as it should either, if you search around you will find this to be true from day one.
Anyone else having problems getting MSVC to respond to questions on the new ROM? With the new Sprint stock ROM and MSVC v1.6.17913, it doesn't answer me when I ask it a question. If I don't say anything, I get the default "thunk" sound when it times out, so it's acting as if it does answer me when I say something, but nothing comes through my headset. Phone calls work fine through the headset though.
I loaded my OEMs with DCD's 2.3.2 kitchen before I knew it had a problem, and got the same results with MSVC, except that it also turned off all sounds on the phone, just like the reported one call issue. A soft reset fixed the sounds until I tried to activate MSVC again.
I'll try DCD's 3.0.x kitchen when it's ready, but I'm beginning to suspect that MSVC needs to be updated to work with the new ROM.
MSVC seems to be working fine so far with the 3.0.0 kitchen.
Hey everyone....for some strange reason, whenver i get a call or text message the ringer or notification stays on even when im the call. I noticed this in some of the later DCD 2.2.x roms. IS anyone else having this problem or know how to fix this...any help is greatly aprpeciated
me too
I noticed this as well just upgraded yesterday using the newest sprint, then puting in a cooked DCD...Thanks, I love it, but the notification(vibrate) stays on and I get no sound from the speaker (media player, ringer, etc)...still searching for a solution
Bratcop said:
I noticed this as well just upgraded yesterday using the newest sprint, then puting in a cooked DCD...Thanks, I love it, but the notification(vibrate) stays on and I get no sound from the speaker (media player, ringer, etc)...still searching for a solution
Click to expand...
Click to collapse
my problem is a little different, im getting too much sound....lol....when im on a call and i receive another call or text, i still hear the ringtone for that action and it usually repeats itself a couple times making it so that i cant hear the person im talking to on the phone. I think i read somewhere that what ur talking about maybe due to picking Lockstream DRM as an option in the kitchen....did u do that?
not I
I didn't cook it myself, downloaded it complete. I added the registry entries I found on this board and I am closer. I still don't get a ring, bur media player now plays and the phone always vibrates when a call. It just seems a little fishy on the ringer end of things...
did you guys that cooked the rom all include the Lockstream DRM package when you built?
if so, I have some problem with the package, and leaving it out of your ROM might resolve your problem for now.
let me know.
DCD, thanks for the help with the ROM and the Kitchen! I haven't cooked up anything yet but I am sure I will give it a try.
Could this be the cause of the problems I am having...I loaded Olipro 2.40, then applied the latest Sprint ROM to my Alltel phone. This gave me the newest radio 3.35.04. I then loaded your final version 2.3.2. I have the ringer issue detailed above, as well as no camera function...I am considering reloading your 2.3.2, then going with the radio 3.27. Also, what's the deal with the PRL file, do I need to change mine from 30029 to something else?
Thanks again man...if you aren't already, you are gonna be a wealthy man some day...
dcd1182 said:
did you guys that cooked the rom all include the Lockstream DRM package when you built?
if so, I have some problem with the package, and leaving it out of your ROM might resolve your problem for now.
let me know.
Click to expand...
Click to collapse
DCD, i didnt use the Lockstream DRM package. Im not sure when i noticed this....i know its happening now and when i was using that later of ur 2.2.X series....maybe its something that happens normally and im just now noticing it, but i dont remember if even the stock roms did this....am i supposed to her the ringtone and notifications when im on the phone? is that common?
PS...thanks for ur hard work on this stuff, ur roms are great
sorry
sorry to get this thread careening off course
I found more info on the dropped speaker on this thread...
http://forum.xda-developers.com/showthread.php?t=376012&page=15
Thanks again.
Default Prophet ringing tone goes silent after certain numbers of dialing
I wonder if anyone notice the problem exist eversince WM6 ROM. I have tried many version of WM6, WM6.1 and now WM6.5, they are all having the same problem
After making certain calls using the keypad, the ringing tone disappear (incoming call ringing tone and the keypad tone all disappear)
Second incident is that when I'm on the call and caller waiting is activated (second person trying to call me) the phone will also go total silent from there on.
The solution is to turn off the phone and restart.
After the phone restart, the ringing tone & dialer keytone work fine. After few dialings the fault happen again.
Does anyone has the solution?
Cheers
smarvest said:
Default Prophet ringing tone goes silent after certain numbers of dialing
I wonder if anyone notice the problem exist eversince WM6 ROM. I have tried many version of WM6, WM6.1 and now WM6.5, they are all having the same problem
After making certain calls using the keypad, the ringing tone disappear (incoming call ringing tone and the keypad tone all disappear)
Second incident is that when I'm on the call and caller waiting is activated (second person trying to call me) the phone will also go total silent from there on.
The solution is to turn off the phone and restart.
After the phone restart, the ringing tone & dialer keytone work fine. After few dialings the fault happen again.
Does anyone has the solution?
Cheers
Click to expand...
Click to collapse
What Rom are you using ?
Have you installed a dialler cab file yourself ?
or any other cabs to do with tones ie.. reminders or different tones for different callers ?
This seems like a problem specific to yourself as no one else has complained of this problem ,So i am thinking it's something you install your self that would also explain why you have the problem on several roms
wapvirus said:
What Rom are you using ?
Have you installed a dialler cab file yourself ?
or any other cabs to do with tones ie.. reminders or different tones for different callers ?
This seems like a problem specific to yourself as no one else has complained of this problem ,So i am thinking it's something you install your self that would also explain why you have the problem on several roms
Click to expand...
Click to collapse
i have same problem with my i mate jamin , only offical rom works fine, when i upgraded to cooked wm6.1 also wm6.5 i am facing same problem , nothing extra installed on that , if i put phone for long standby fone becomes silent , what is soul plz,
changed all radio versions also but same
thanks in advance
Nothing extra added to all the WM6.x ROM that I have tried but yet the problem remains.
Perhaps you didn't dial as much number as I do, that's why you haven't experienced that.
In fact there were other threads discussing the same problem but no ones seems to have the right answer.
Im having same problem too, totally silent. It happen when use keypad to find/dail contacts, few click heard sound, then totally silent. I tried install/remove dailpad but the problem still exists, tried off keypad sound, changing ROM yet the problem remains.
I did install a ROM (Dont remember which one and when) and the problem happens everyday until I need to change to other ROM.
Maybe someone could come out with solution.... Anyone?
How can someone come out with a solution when you all discribe your problem so badly none of you can tell wich rom you are using build blah blah
wapvirus said:
How can someone come out with a solution when you all discribe your problem so badly none of you can tell wich rom you are using build blah blah
Click to expand...
Click to collapse
Perhaps you might not read the post carefully, we are saying of all the WM6.0, WM6.1 & WM6.5 ROM that we have tried have similar problem.
If you haven't experienced them, perhaps the best way to learn is to install the latest build -WM6.5 Build 23001 - 23016 WWE bikertibi edition at http://forum.xda-developers.com/showthread.php?t=532122
Then post us the solution if you have got one, thank you.
Cheers
smarvest said:
Perhaps you might not read the post carefully, we are saying of all the WM6.0, WM6.1 & WM6.5 ROM that we have tried have similar problem.
If you haven't experienced them, perhaps the best way to learn is to install the latest build -WM6.5 Build 23001 - 23016 WWE bikertibi edition at http://forum.xda-developers.com/showthread.php?t=532122
Then post us the solution if you have got one, thank you.
Cheers
Click to expand...
Click to collapse
Yes i have read but this problem only exists in the latest builds of 6.5 and by the way i built some of those ROMs so your suggestion is out the window
I stopped building and releasing after 23004 because i was noticing to many bugs the only way to stop this with these latest builds is to change the way we cook the ROMs there is no fix. The files that are causing the problems are in the wrong partition so they can't be read when called on by the kernel of the OS (Like they don't exist)
This is why all the builds after 21100 have problems
You can Read all about it here:
http://forum.xda-developers.com/showthread.php?t=544445
As for all the ROMs having problems well i have run some of these 6.0 and 6.1 roms for months with no problems (and not just me many others on this forum)
These problems are 6.5 related
wapvirus said:
Yes i have read but this problem only exists in the latest builds of 6.5 and by the way i built some of those ROMs so your suggestion is out the window
I stopped building and releasing after 23004 because i was noticing to many bugs the only way to stop this with these latest builds is to change the way we cook the ROMs there is no fix. The files that are causing the problems are in the wrong partition so they can't be read when called on by the kernel of the OS (Like they don't exist)
This is why all the builds after 21100 have problems
You can Read all about it here:
http://forum.xda-developers.com/showthread.php?t=544445
As for all the ROMs having problems well i have run some of these 6.0 and 6.1 roms for months with no problems (and not just me many others on this forum)
These problems are 6.5 related
Click to expand...
Click to collapse
Great!
I wonder if you can suggest us a good WM6.1 version with link for Prophet G3 that doesn't have those bug to test and report to you.
Cheers
smarvest said:
Great!
I wonder if you can suggest us a good WM6.1 version with link for Prophet G3 that doesn't have those bug to test and report to you.
Cheers
Click to expand...
Click to collapse
Ermmm i don't want to be biased but what about my latest 6.1 this is a good stable ROM for you to try
http://forum.xda-developers.com/showthread.php?t=545229
Workaround
Hi all,
if you want to workaround the problem, just turn off the keypad sound.
Phone --> Menu --> options... --> Keypad: Off.
Nir
nir-k said:
Hi all,
if you want to workaround the problem, just turn off the keypad sound.
Phone --> Menu --> options... --> Keypad: Off.
Nir
Click to expand...
Click to collapse
Have you tried it? Does it work?
I don't quite like the idea because by enabling the keypad sound that's how I get to know whether the income call will ring or not. Because I have lost many incoming calls due to the bug, not knowing someone is calling.
Cheers
wapvirus said:
Ermmm i don't want to be biased but what about my latest 6.1 this is a good stable ROM for you to try
http://forum.xda-developers.com/showthread.php?t=545229
Click to expand...
Click to collapse
Is there any clean version available without Manila for maximum memory available?
smarvest said:
Is there any clean version available without Manila for maximum memory available?
Click to expand...
Click to collapse
look at dioxda2 roms he has some very good clean builds
smarvest said:
Default Prophet ringing tone goes silent after certain numbers of dialing
I wonder if anyone notice the problem exist eversince WM6 ROM. I have tried many version of WM6, WM6.1 and now WM6.5, they are all having the same problem
After making certain calls using the keypad, the ringing tone disappear (incoming call ringing tone and the keypad tone all disappear)
Second incident is that when I'm on the call and caller waiting is activated (second person trying to call me) the phone will also go total silent from there on.
The solution is to turn off the phone and restart.
After the phone restart, the ringing tone & dialer keytone work fine. After few dialings the fault happen again.
Does anyone has the solution?
Cheers
Click to expand...
Click to collapse
Might be helpful to know that IPL, SPL, model (G3 or G4) and GSM, you have installed.
Arimxda said:
Might be helpful to know that IPL, SPL, model (G3 or G4) and GSM, you have installed.
Click to expand...
Click to collapse
IPL -1.00
SPL -2.G3.4PDA
Model G3
GSM -02.47.21
OS 6.5.23016
Hope to hear from you soon
smarvest said:
IPL -1.00
SPL -2.G3.4PDA
Model G3
GSM -02.47.21
OS 6.5.23016
Hope to hear from you soon
Click to expand...
Click to collapse
I have this setup:
IPL -2.15.0001
SPL -2.G4.4PDA
Model G4
GSM -02.19.21 [Ideal performance of the battery (for my setup and
installed programs)]
OS 6.5.23017
Already I have commented that I do not have these problems.
Perhaps the problem is caused by your s200 model (G3). I am not an expert, but if a common problem exists: Something must exist commonly to all,,, I think,,,
My caller can hear me for few minutes, while continue talking caller cannot hear me and I can hear very well. Recording works fine. Even after downgraded to original I-Mate version WM5 and ATT Stripped wm6.1 same results. IF I slide it and press the place near the mike while talking it again start working for few more minutes. Can you suggest any solution ?
Changing the OS won't help, you will need to upgrade the Radio. The problem is either the network or your Radio/hardware. If you do upgrade the Radio ONLY use the SDCard method. Check the WIKI for more info.
Thank you very much, Finally radio 1.48.00.00 SDCard method upgrade resolved the issue.