Related
There seems to be a very annoying bug on my new XDAII that is running the 1.6O O2 ROM.
If I am on the phone and i receive a call that alerts me that there is a call is waiting, and I decline to answer it, the sound is cut off and I can't hear the caller anymore. Cancelling the current call and re-dialling is the only way of getting 'sound back'.
Furthtermore, another irritating bug is that if the phone rings and I answer after only 1-2 rings, I can't hear anything for a few seconds and have to wait those couple of seconds before i can speak to the other person. This doesn't seem to happen if the call is answered after 3-4 rings.
Any help would be appreciated.
Me too - only answer I found was to turn off call waiting.
Poor solution.
Same for me, i too had to turn off call waiting, however i found that if you are using a bluetooth headset when the second call comes in and you decline to answer it, it just transfers the current call the the phone and you can continue it there
Same problem here.
I find that if you put the call on hold and then resume - the voice will come back.
VERY irritating.
Same for me too, I have T-Mobile 1.60 and using BTHTools 1.1.0.0...
Do you use BTHTools?
yes l am using BT tools.
regards,
hasnain
I performed a hard reset...
Did NOT install BT Tools - and had the same problem.
Mine did this long before using BT tools also.
I also have the same problem....
Is it an incompatibility between the phone and Bt Tools?
Is there any solution other than turning off call waiting?
Does anyone face the 2nd problem that I mentioned:
Sometimes when I pick up the phone after it rings, it takes a couple of seconds before i can hear the caller. This happens more often when picking the phone up within 1 or 2 rings.
This problem was aroung in the I-mate ROM 1.66.
They fixed both with the 1.72 ROM.
ketinson said:
This problem was aroung in the I-mate ROM 1.66.
They fixed both with the 1.72 ROM.
Click to expand...
Click to collapse
i DON'T THINK THIS IS FIXED IN 1.72. i STILL HAVE THESE SAME PROBLEMS TOO, RUNNING t-MOBILE 1.72.
While running 1.60 I replaced the Radio Stack only with the O2 original release version - sorry don't remember version number - and it worked without these two very annoying bugs in the phone. i think it is a problem with the readio stack version only.
After losing the voice with an incoming call I can get the voice back without redialing by placing the call on hold and then resuming.
I have the same problems with or without bluetooth tools and with or without a BT headset.
Now, I have T-Mobile's 1.72 installed and am afraid to reload the working radio stack becasue of the "downgrade disaster" with 1.72. I am anxiously waiting for either a stable 1.72 or XDA Developers to help us out of this mess with this ****ty ROM.
This forum is fantastic. Thanks to everyone.
Steve
I had the problem in the 1.66 ROM, and no longer have it with 1.72!
I've just installed the new O2 1.72 ROM and am still having the same problem.
I am also suffering from a problem I was having on the old ROM. Many times when I receive a call and press the green answer button, it takes between 2-5 seconds for me to hear the person calling. The person calling also hears a similar period of slience before he/she can hear me.
The same thing also happens sometimes when I call out, where only once 2-3 rings into the call or if the other party has already picked up thephone can I hear or say something.
I'm not sure if caller ID or Photo ID has anything to do with it as I have around 1380 contacts on my xda.
This problem is extremely annoying and was wondering if there is anyone out there who has faced the problem and may have an answer for it.
Us too
We have two xda2 with 1.72, and same thing, there is a 5 second delay upon recieving any call, and sometimes there is a hangup duriong call waiting???
I never had that problem until I installed Bluetooth Tools...now it always happens. Though as someone's suggested, holding and resuming seems to do the trick.
I have the german T-Mobile MDA-Pro with D1. (whytf can't I specifly that in my profile ?) I experience some strange thing with it. When I pick up the phone when someone calls me (by pressing the green phone button) it takes a while until the other side can hear me.
So whenever I answer a call (by pressing that green phone button) I will have to wait 5-8 seconds after the buttonpress until I say something or else the other side wont hear what I say and still thinks I havent answered the phone yet.
Yes! indead...I've got the same problem. is it a software bug?
I too have the same problem, and sometimes it hangs up the call even when I press the green button.
I've posted before and everyone has said 'Use the search'...I have and can't find anything relevent (don't think the search facility of this is very good).
Can someone PLEASE point us.
I really do miss the speed and efficiency of my XDA2s!
I have had some experience of this, it does delay mine was worse before I got rid of all th O2 tat, it is now liveable with, however it is cutting off when I press the answer button !!! OR IS IT after conducting tests using another mobile I found out that
1) the phone does not take very long before O2 divert the call to Voicemail
2) the phone starts ringing long before you know anything about it (its worse if the phone is asleep) it can be a good few seconds before it makes any indication noises
3) it carries on playing the ringtone after the call has been diverted which gives the impression that pressing the answer button is futile.
I have talked to the technical suppport of t-mobile germany and they told me they era aware of this issue and they will be releasing an update in Q12006 that will resolve this issue.
I have talked to the technical suppport of t-mobile germany and they told me they are aware of this issue and they will be releasing an update in Q12006 that will resolve this issue.
I too have this problem and for the moment while i await any future fixes from O2 or others, i am using the following short-term fix; Under phone settings I have changed the delay period before calls are forwarded to ansafone if unanswered (this works on O2 anywa). One problem with this is that callers may give up before they are diverted to ansafone if you set the delay too long
did this really resolve the issue I was talking about in my initial post ? (that when I pick up the phone by pressing the green button the caller can not hear me for the fist 10 seconds )
I have XDA Exec and kept getting confused why my GF always sounded confused and puzzled when I answered the phone, Id say "hello" and she would wait a while, then say "Hello? you there?"
I never realised it was MY phone that was cutting off my voice at the start of the call.
In regards to the delay ringing, and answering etc, I am giving all my friends instructions to bloody well keep ringing! I turn answerphone off normally as my phone is always on. If you want to speak to me, keep ringing till i answer, if I dont want to talk, ill reject the call.
Why ring twice and hang up? I could be doing anything that takes more than 2 seconds to get that damn phone out of my pocket, get it out the case, open it, see who is calling, press the button, damn, missed call.
Same problem here. I am seriously thinking about using this as just a PDA. I don't think it's practical to use a phone that only works some times. Somebody on HoFo said that the Universal isn't meant to be used as a phone, it can, but it isn't meant to be. I'm starting to agree.
I just like the idea of not having to carry around a phone AND a pda. I kind of hoped that's what the universal offers. But it kind of looks like it doesn't ...
Its a great phone when used as a hands free device, answers almost straight away, and has great volume unlike most hands free - my callers also comment that the line quality is excellent even if a few metres away from the phone.
I do always feel stupid though when using the phone as a standard phone, would feel more comfy putting a brick to my head.
I use the old phone ringer as my incomming call notifictaion and I hear my phone in plenty of time. The standard o2 incoming notification sound was useless. I don't know what T Mobile have but might be worth trying a different notification sound.
Cheers
I will have to wait 5-8 seconds after the buttonpress until I say something or else the other side wont hear what I say and still thinks I havent answered the phone yet
Click to expand...
Click to collapse
Did anybody found a solution for this? this is very annoying.
Agreed, its just ridiculously slow - I worry whether or not I've hung up on people too, it takes a good few seconds before the line is actually dropped, let alone for the interface to update.
I've stopped using the "suspend" option and the phone seems to work like you'd expect (even on a cheap cell phone!). But the battery life is suffereing. Hopefully my new spare battery should be here soon.
I've stopped using the "suspend" option and the phone seems to work like you'd expect
Click to expand...
Click to collapse
You mean I should walk around with some spare batteries in my pockets. :wink:
I think my pockets are too small for so many things.
Does anybody knows if this problem is known to HTC? Is there going to be an update?
It isn't possible that a phone doesn't act like a phone in these features that are already working 100 years. I want to pick up my phone and talk immediatly
By the way how do I switch off the "suspend" mode?
What is the "suspend" mode and how do I switch it off?
Look at Settings>Systems Tab>Power>Advanced Tab
Uncheck to "Turn off device if not used.."
This will stop the "suspend" mode
eeek ! Now I know why I would need an extra battery ....
Hey, I've been lurking these forums for a while but I thought I'd come on to ask a question. I tried asking on sprintmogul.net but they didn't really help.
I've had my mogul for a few months but lately it's been developing a really annoying problem. I'm really not sure where it started exactly so I can't blame any apps in particular. When I receive a call the caller ID / ring and vibrate go off perfectly - the problem happens when I try to answer the call. Generally one of three things happens:
1 - The call connects instantly and just works - this happens pretty rarely, I remember the last time it happened the person calling was also on Sprint, if that makes any difference.
2 - The phone will just sort of hang there for about 10 seconds, caller ID popup still there, the ring stops though. Eventually the popup disappears and I get a missed call notification, as if I never clicked the answer button. This is what usually happens.
3 - The phone hangs like in situation 2, but the call eventually connects. This only happens if I press answer almost immediately after the phone starts to ring.
I'm on winMo 6.1 with the latest radio and am not running any major mods or hacks, just a few reg edits. I'll probably try a hard reset soon but ideas on things to try would be appreciated!
I am seeing this also, on both my own xv6800 and my wife's. It's VERY annoying.
I upgraded my XV6800 to 6.1 using the official upgrade. It's giving me trouble answering calls. When a call comes in I see the notification but when I try to press the Green phone button or the left soft button labeled 'Answer' it doesn't do it! It's like the keys are slow or something. When I use the soft button is DOES flash the soft button label like it recognized the button press. But it does not answer the call! I've had this happen at least a dozen times now so I know it's not just me fumbling with the keys. 9 times of of 10 I can't answer a call!
I've tried hard resetting the device and the symptom persists. I've tried using it without the microSD card loaded. Still the same trouble.
Has anyone else seen this? Or can you recommend a solution?
so your saying it doesn't show "connected"?
I had something similar to what your describing but it would show as "connected" on my phone. I couldn't hear anything when I'd answer. I realized after several attempts it was that the phone was paired to my cars bluetooth... I was trying to dial my phone as I was walking away from my car but I was still within 30 ft of the car... so all speaker and microphone was still being redirected to the cars system. lol. Same can happen with a bluetooth headset where the conversation (speaker/mic) is redirected to the headset that may be in your pocket or on the kitchen counter. But it would at least show as "connected" on the phone.
I feel stupid/foolish for shareing that experience but figured just maybe its what your experiencing.
Thanks,
Ben
*edit: by the way... when I had the 6.1 vzw upgrade I had no problem placeing and receiving calls, with the exception of the "user error" I described above. You could always try rolling back to 6.0 and upgrade again. Did you install any other new software after the upgrade to 6.1?
I have been experiencing something similar. PPC 6800 (not Verizon) with 6.0. When phone is locked and call comes in, can’t answer with the button or with BT. 6800 keeps ringing long after caller goes to voice mail. The only way to escape is soft reset. I’m running the original ROM & Radio that came with the 6800.
ygohome said:
so your saying it doesn't show "connected"?
I had something similar to what your describing but it would show as "connected" on my phone. I couldn't hear anything when I'd answer. I realized after several attempts it was that the phone was paired to my cars bluetooth... I was trying to dial my phone as I was walking away from my car but I was still within 30 ft of the car... so all speaker and microphone was still being redirected to the cars system. lol. Same can happen with a bluetooth headset where the conversation (speaker/mic) is redirected to the headset that may be in your pocket or on the kitchen counter. But it would at least show as "connected" on the phone.
Click to expand...
Click to collapse
Nope, never shows connected. It's like the UI has gotten hung somewhere and isn't passing control over to the phone app.
No bluetooth pairings have ever been done to this phone, not before the upgrade and certainly none since. BT isn't even enabled.
Tim may be on to something regarding the lock situation. I've found the lock method a lot less friendly than before 6.1. Can't quite pin it down but it just doesn't seem to unlock properly. Again, it seems to be related to something making the phone 'slow'. On-screen keypresses in the Lock app don't seem to register with the same speed as before 6.1. I can tap a couple of them and not see anything on the screen, then they all run through (showing the screen buttons getting pressed).
My Xv6800 Verizon Does The Same Thing. I Push The Green Hard Button To Answer And It Takes Like 5 Seconds To Answer. It Seems To Happen More When I Have Programs Like Internet Explorer Up, But There Is Still Plenty Of Memory So I Cant See Why It Would Be So Slow. Its Just Frustrating Because Sometimes It Takes So Long The Call Goes To Voicemail And Nobody (fiancee Included) Believes Me! Any Help From Anyone?
fyi... i use an auto close program so when I close an application it really closes. I don't have the slow response or ability to not answer within 5 secs, etc. maybe it is a low memory issue you are experiencing. I don't lock my phone so that may be it too. Sorry I'm not much help here.
ygohome said:
fyi... i use an auto close program so when I close an application it really closes. I don't have the slow response or ability to not answer within 5 secs, etc. maybe it is a low memory issue you are experiencing. I don't lock my phone so that may be it too. Sorry I'm not much help here.
Click to expand...
Click to collapse
No, it's definitely not a low memory issue. It's doing this fresh after a reboot having had no other apps even started.
Hi,
I have been searching on the internet for a long time but didnt find any other user with the similar issue. Whenever I try to disconnect the call, most of the times I have to tap on END CALL button multiple times. I am using 910C. Haven't tried a factory reset yet, but was looking for some other sensible solution.
I am using Stock ROM - Not rooted yet. Running 4.4.4, Build No. KTU84P.N910CXXU1ANK5.
Thanks,
Danish
you need something like this in the post
http://forum.xda-developers.com/showpost.php?p=56494204&postcount=4
B.No Call end screen - There won't be call end screen, call will be disconnected right from Incall screen without showing End call screen
this is for snapdragon , so before flashing, be cautious.
Thanks a lot pratik for your guidance, but I believe I mentioned, I am on Exynos N910C. The link you have shared is for Snapdragon. Also, instead of a work around, I was interested more in the reason and an actual fix of this issue.
Thanks,
Danish
pratik_193 said:
you need something like this in the post
http://forum.xda-developers.com/showpost.php?p=56494204&postcount=4
B.No Call end screen - There won't be call end screen, call will be disconnected right from Incall screen without showing End call screen
this is for snapdragon , so before flashing, be cautious.
Click to expand...
Click to collapse