Database Users

Microphone stops when I hit a numberkey if I'm calling an interactive menu system!

Ok, this is a real doozy.
This happened on my original Hermes, and now it's happening on my (three day old!) new one too (just tried to Ring Areti Internet to speak to someone on behalf of one of my clients, and the moment I pressed 0 to speak to someone the microphone seems to just cut out).
The root of the problem is: I can ring a number, whatever, and if I get to a menu system, I tap in the appropriate number to navigate through the system. However, the moment I do so, when I do eventually get through to someone they can't hear me. I can hear them fine, but my microphone has totally cut out - and even trying things like hitting mute / unmute makes no difference.
If I don't press a button, and either hang on until the menu system just puts me through to someone, the mic works fine. The worst thing about this problem is that it's unpredictable; it can happen all the time or it can just happen every so often, and there's no visual or audio indicators to say otherwise that the problem is occurring.
My two Hermes models are quite vastly different in model: the old one was an HT634 and this one is a 643, so the question of the problem being a hardware one spread across several models doesn't apply. This is REALLY ANNOYING, not only does it piss off the person on the other end but if you're stuck in a queue waiting to speak to someone for 20+ minutes, finally getting through and finding that you can't be heard is TOTALLY ANNOYING!
What's even more confusing is this: I thought it might be a permanent problem, so I tried ringing my home phone, then getting my friend to make like an interactive menu system and just say "press 1 to test this, press 2 to confirm that this is a really stupid thing I'm having to do for you, press 3 to confirm that you don't mind me hitting you after we're done testing this idea of yours"... You get the idea. I pressed a button (more than one in fact, the second time I tried it), waited the appopriate length of time that it would take in the real world to get connected, and started speaking - and the person on the landline could hear me fine.
The problem was also present (and intermittent) on my first Hermes, but it was unpredictable. I'm not in a great 3G signal area, and as I look at my phone at the moment it's gone back to GPRS. I also noticed on the MoDaCo forums that some people in London were suffering from problems where they couldn't hear callers, but the person at the other end could hear them fine (they suppose, as they weren't hung up on even though they couldn't hear their caller) - they had to force their phone back to 2G to resolve the problem. However, my microphone doesn't cut out during normal phone usage, so it's just really bugging me that I can't figure out why the hell this is happening!
My Hermes is pretty much stock: T-Mobile ROM, nothing cooked or patched, I just have the odd little bunch of harmless utilities installed: a screen cap application, Map24 Mobile, Microsoft Reader, Media Metrics Meter (usage tracker, you get paid £5 a month for submitting your stats to them so it pays for the Web 'n Walk), Opera Mobile, TCPMP, SMSDRFix, Vibra Switch, WM5NewMenu and Total Commander... They're the only significant additions.
This is driving me nuts! I never had this problem on my old Alpine, though granted it was on O2. I've even had this problem when calling the T-Mobile support line! Which as you can imagine is MOST frustrating.
Anybody have even the faintest idea as to how to solve this problem? It SEVERELY hinders my ability to ring any kind of helpline or support / sales line... And until I found an alternative (direct dial) number to get through to T-Mobile Customer Services, I wasn't even able to ring them!

had exactly the same problem with a Vario II. I couldn't set up my voicemail!
Exchanged unit for a new one and now works fine. No problems so far

flashflash said:
had exactly the same problem with a Vario II. I couldn't set up my voicemail!
Exchanged unit for a new one and now works fine. No problems so far
Click to expand...
Click to collapse
Argh... It took me long enough to get this replacement!!! Vario 2s are like golddust at the moment.
What model number is your new unit? Mine is an HT643 (first one was a 634)...

Instant Dropped calls on Cingular?

I keep getting calls that drop the second I hit the answer key. I'm using the latest Cingular based firmware for my 8525. Is anyone else experiencing this? I'm trying to determine if it is one of my installed apps or a problem with the phone itself. Thing is I have no apps that are meant to handle calls or VM so if other users are experiencing this please post.

I am not having this problem, 1st I've heard of anyone dropping calls instantly.
Were you located, I'm in chicago and know 4 other with the 8525 without any dropped calls.

NJ. I've been on the Cingular network for a few years now. I had an MPX220 before this.

In my opinion it may come from the magnet of the default case; give some try without it.

yeah, I've had it happen to me too. Interesdtingly, it didn't seem limited to my TyTN either. I had it on my 8125. Seems to happen most often when I answer using the softkeys instead of just pressing the green phone icon.

hmm. im not really sure which i answer the phone, both if im not wrong. I'll have to keep my eye out for that.

I was having a similar problem that turned out to be my case hitting the buttons as I pulled the phone out. I switched to a seidio clip case and it hasn't happened since.
there was a slight delay, so it actually disconnected about the time I hit the button. sometimes the call would answer instead of dropping, depending on which button was hit.

Same Problem on Vodafone
I bought 2 V1605s (tytn) 2 months ago for my business. I seem to have the exact same problem on both phones - about 20-30% of calls have this issue. Scenario is as follows:
Phone rings, after any amount of time Answer with either the green button or the soft keys and the call dies. The other party is routed to Voicemail at that time. While this problem is present I sometimes get a problem where I can't initiate a call - get an error that Cannont make an outgoing call due to lack of signal.
I have seen some suggestions that this (or similar problems) can happen when you are going into and out of coverage blackspots. My work and home areas both have blackspots, so it seems to fit with this.
Only solution I have found is a soft reset. I have tried the following:
- Set band selection to Manual - didn't work
- Set UMTS/GSM to GSM only - didn't work
- Do a hard reset (wiping data and other installed programs) - didn't work
- Make sure that all other applications are closed properly through task Manager (especially data-using ones) - Trying now - no results.
I'd appreciate any suggestions as I need this sorted - no matter how good this phone is as a PDA, I can't tolerate losing 30% of my incoming calls!

I've had similar issues. Last couple of days have been worse than others.
I am beginning to consider an alternate carrier -- the big V is better in and around NYC from what I understand

Cell will not answer calls

Anyone run into the phone not answering the call when you hit the answer button or wnaswer on screen? Any fixes or ideas?

yep... http://forum.xda-developers.com/showthread.php?t=370483
Tried to get started with narrowing down which app causes it but the thread fizzled. I ended up flashing to a newer DCD release and then only installed the bare bones apps I needed to get by and it's working fine so far.

Me too
ripshot_1 said:
Anyone run into the phone not answering the call when you hit the answer button or wnaswer on screen? Any fixes or ideas?
Click to expand...
Click to collapse
I have been having the similar problems. I can answer if I hold the button down a really long time or hold the slide at the end until the screen changes to the phone app. Usually I get a missed call though. I initially thought it may have been S2U2 or S2UP but after using and uninstalling both no resolution. I got no fixes or ideas as of yet, just uninstalling apps and seeing how it responds. On a positive note taking off all these apps has increased my standby memory considerably

So what you guys are saying is that out of nowhere your phones won't answer a call?
Or did you like flash a ROM and then wasn't able to pick up a call?
One thing that helped me was to change all ringtones to WMA on DCD's ROM's because MP3's dont seem to play all the time for a weird reason.
Also I changed the settings on my phone. In the the EPST I changed a setting in the Modem menu. I changed the Slot Cycle Index to "0" instead of "2" and it answers the calls faster.
These are just some ideas as I really dont know what issues you are having.

I just posted a long winded update to
http://forum.xda-developers.com/showthread.php?t=370483
Ultimate fix for me (experiencing non-answerable calls) was a hard reset. I'm blaming the AdvancedConfig tool or some setting it exposed to me to tweak.

i've had the same thing happen in the past so i would be interested if this gets figured out. i never figured out what it was, but since I back up nightly w/ sprite backup, i just restored the most recent registry backup and it took care of the problem both times it happened.

same happened to me - i couldnt answer a single call and had to call back whoever rang me up.
REALLY annoying.
i repaired it very easily, however.
i um...accidentally.. dropped my phone off a roof and the new one answers calls very well!
this also solved all the other problems i had with my earlier phone.
go figure!

I am having the same problem...hit the green talk button or the answer button and nothing happens. I have to call everyone back...so what I am hearing is that it is the advance config program that is causing it and a hard reset is the only option to fix it?

that appears to be the case - at least in my experience.

XV6900 Texting Problem

I just bought my xv6900 2 days ago and i noticed that each time my phone goes idle as it goes to sleep and when someone text messages me i dont get a notification until i turn on the phone again with the button on top of the phone. and also sometimes i dont receive a call and when i next turn back on my phone it says missed call..
does anyone perhaps have the same problem or know whats wrong with my phone?

I have had the same problem and can't figure it out. I've done a hard reset and that fixes it for a bit, but no long term solution.
I have the following Software Installed:
SPB Mobile Shell
VIP Ringtone Manager
Shubaroo Group SMS
Check this out
http://forum.xda-developers.com/archive/index.php/t-344852.html

i have yet to install any other apps that didnt come with the phone. and i read that forum link u gave me, it doesnt seem to be my battery because i know my battery was at 80% when this happend. its such a nice phone but this really pisses me off. wish there was a solution.

I am having the same issue. I called verzion and they know nothing about it. Everyone who has this please call. I really like this phone but if it doesnt work like a phone its useless.

I've seen same problem on a Sprint Touch so it's not specific to Verizon.
I had 2 Sprint Touch phones side by side and one would not wake up from suspend for an incoming text or phone call. The second Touch worked properly and they had the exact same configuration. No clue why some of the HTC Vogue's have this issue and others don't.
I would call Verizon and ask for a swap if they ignore your problem.

Well I did a hard reset and it worked great for few days! Now back to normal.. looks like it is going back to verizon. Not sure what to get though.

Got the same problem but some days it works fine and some days it doesnt. I througth i had to much stuff saved or downloaded on the phone but when i removed programs that i downloaded that i never used it didnt fix anything so im puzzled like everyone else here.

same issue
I have had mine for several months now, i just had to do a hard reset recently and my phone has done the same exact thing ever since. I thought maybe it was a problem with polling. I did notice this time I hard reset, verizon did not have me set my A key, instead they changed something on their side and had me do a 228 reprogram. So i wonder if something is being changed via this new method ( the guy told me he just figured out he could do it this way and not require me to set my akey ).

Weird issue

Hi all,
When the screen is locked, is it still possible to accidentally dial a number. Today my phone self-dialed a certain phone number a few times without me knowing. I normally have the screen locked so I thought maybe it was my headset that was redialing since it has that feature. The weird thing though is that it's not always the last phone number that was dialed or received that is called so a simple re-dial activation can't be the issue. Any ideas?
Thanks,
Ho'okani

I've has similar issues. only happens when I am connected via bluetooth. But both my headset and my car do it. I will randomly dial out number, very disturbing while i am driving. It does not happen often, and it usually is the last number called or recieved, but not always. I have had this happen on several diffeent roms now. the only thing I can think of would be something from the bluetooth stack.

ducktat, were you able to figure out what was happening and solve the issue?
Ho'okani

I had a problem like that on my Touch Pro. It turned out to be the Rom I had installed enabled wake up with new text messages. So after I received a text, my phone would be unlocked and then pocket dial people.... On second thought, I wasn't "locking" my phone, just manually rutting it to sleep

Don't think that's my problem. When I look at my phone after this happens, the screen is locked however it is sometimes on a contact screen but not necessarily the contact I called.
Thanks,
Ho'okani

Flashed to two different ROMs. problem did not happen with either. Running the latest energy ROM now, flawlessly. It does seem like a ROM issue.

ducktat said:
Flashed to two different ROMs. problem did not happen with either. Running the latest energy ROM now, flawlessly. It does seem like a ROM issue.
Click to expand...
Click to collapse
Which ROM was it happening with?

I'm using the stock rom from telstra.
Ho'okani