Related
Hi all,
I've been trying not to let this bother me too much but it just does. Why, when we've come so far with mobile technology, are basic things like this still not done properly?! specifically:
1. my hero doesn't actually start ringing for at least 3 rings on the callers side? this it might not seem much but is almost 10 seconds that the caller is waiting before I know about it. By the time I do and get to the phone I will almost miss the call.
2. this may be a handcent problem but I don't get the trackball flashing 2-3 seconds and the actual audio notification for 5-10 seconds.
-
l just want these things to feel instant and zippy. Is that too much to ask? I don't think so considering this handset can show me which constellation I'm looking at and that there is a 'titty/tapas bar 500 yds that way'.
Is there anything I can do to improve these fustrations?
Don't get me wrong, I think the handset is generally great but don't want a 'Jack of all trades, master of nothing'.
R,ant over.
Orangepeel.
Sent from my T-Mobile_G2_Touch using the XDA mobile application
powered by Tapatalk
Hi,
I get the same problem with my phone not registering a call for atleast 10 seconds and usually missing calls, it's very annoying!
Something I've found that helped me was to prolong the time it takes before the caller is sent to your voicemail i.e. your phone SHOULD ring for longer before the caller gives up...
Search the forums for the code you need to enter to prolong the time period (I think it's 30 seconds).
Hope this helps...
It depends on the rom your running.
For example the latest VillainRom rings instantly now but always used to be quite delayed.
the handset is very well aware of the incoming call, it just takes a few seconds to ring and display the call. when you are listening to music you will notice that it stops, then after a few seconds it will start to ring. try to use .ogg ringtones, apperantly that makes it better.
Lennyuk said:
It depends on the rom your running.
For example the latest VillainRom rings instantly now but always used to be quite delayed.
Click to expand...
Click to collapse
I'm using Modaco 3.2 and have always had this issue since upgrading from the Stock rom months ago!
Are you saying that the latest Villain ROM (based on 2.1) fixes this issue?
So in theory this problem should be rectified once 2.1 is officially released??!
bunt83 said:
I'm using Modaco 3.2 and have always had this issue since upgrading from the Stock rom months ago!
Are you saying that the latest Villain ROM (based on 2.1) fixes this issue?
So in theory this problem should be rectified once 2.1 is officially released??!
Click to expand...
Click to collapse
yes it seems to be fixed in VillainRom 5.2 or its certainly a lot better than it was.
This fix was something the Dev (Nathan) did I think so official 2.1 may still have the problem
Lennyuk said:
yes it seems to be fixed in VillainRom 5.2 or its certainly a lot better than it was.
This fix was something the Dev (Nathan) did I think so official 2.1 may still have the problem
Click to expand...
Click to collapse
Interesting!
I guess I'll wait until 2.1 is released and see if that fixes the problem otherwise I'll be switching to the Villain ROM based on the official 2.1!
Cheers for the info Lenny...
okay so i've used the phiremod skinnyEVO1.5 and Mdeejay eVo Sense Stock and i've had the same problem with both. Whenever i make a phonecall/receive a phonecall, as soon as the person and i end the call my phone goes completely unresponsive. the screen goes completely black, and none of the hardware keys light up
the only thing ive found that can get the phone to come back 'to life' so the speak is to call the phone again and end the call on my phone with the end button.this doesnt always work though.
im running the Chunkydroidrom in WM and have radio 2_12_50_02
i even updated the kernel on the Mdeejay build and it still happens
is there anything that can be done to fix this?
please help me guys
different build, but same issue, nexus one by ummmmmmmmm matc forget which version. radio 2.15, wm chunky gtx sense with that CHT 2.0 i think..................
so far our windows mobile rom is the same cook, could be where to start im about to change my winmo rom
i just changed my windows mobile rom to ozdroid and im still having the same problem, and when i use the included bootloader i get robotic/froggy sounds in phone calls. maybe its not running clrcad correctly so ill try it the old fashioned way and see what happens
please
bump
can someone pleasee help?
good luck in finding help. Ive had some of the same issues i believe. My phone will completely freeze during a call for now apparent reason. it'll working fine in the call in the just freeze during my call. I tried different winmo roms that are suggested for droid builds. i believe i tried every radio available for tmo and about every build of driod and the problem is still there. It may run fine for a day then it starts freezing. I've posted a question about this yesterday and 97 people have viewed it and one person suggested i return the phone. I don't believe that its a hardware issue, more like a software issue. I guess i better learn how to pull the logs and then i may get a reply. i just haven't found a place that it explains it well enough for me to do it myself. My persistence will prevail though, cause I'm addicted.
Well please if you ever figure it out please let me know as this can get quite annoying
Sent from my HTC HD2 using XDA App
Disable Auto-Rotate in the Settings>Display.
See if that helps.
I had the same problem. I have Advanced Task Killer installed and it was set to kill apps on screen off. I turned off the option to kill apps on screen off and so far it solved my phone call = unresponsive phone.
I have theese issues only if i have certain call recorder softwares installed .. try uninstalling them , and if nothing helps delete ur data.img and do a fresh start(u can back it up tho if it prooves unusefull)
@souljaboy
what exactly do you mean by certain call recorder softwares installed? such as which ones?
@JonSolo
i disabled auto rotate and i still experienced the problem during phonee calls
@mike91t
i changed my auto kill to every 4 hours, so i'll let you know what happens with that over the course of the week
Same problem here, I've turned off screen autorotate, and I don't have any task killers installed. Everything works fine, and even a call or two, then it stops working and audio during calls doesn't work, and phone app becomes unresponsive.
have you tried a different radio rom?! maye 2.14 will help.
fruchtfliege said:
have you tried a different radio rom?! maye 2.14 will help.
Click to expand...
Click to collapse
well i waws thinking about changing to 2.14 but the android build im using recommends certain roms for best performance so i was going to keep using the radio rom and see if anything improved, so far i dont really think its working, so i might change to 2.14 because people seem to be having the less problems with it
Anyone else? Im not exactly sure if its Phone.apk, DialerTabeActivity.apk, or simply the act of voice calls that is causing it. But it seems as though whenever i make a call, or have an incoming call, my phone almost cant handle it. It lags out like crazy.
This morning, my phone started ringing. There was so much lag that i couldnt answer the phone in time. Also, when i go to hang up a voice call, it often takes the "end call" button almost 10seconds to respond. Lastly, just earlier, i ended a call with my buddy. It LITERALLY took 3 minutes between the time i ended that call, and started a new one. Thats how bad the lag was.
Anyone else experiencing this? Any ideas how to fix it? Maybe its the modem?
This lag is literally intolerable, and a major inconvenience to efficiency.
PS - No, im not running a lagfix. I experimented with and without, and i determined that overall my phone performs better without it.
PPS - This is not me being oCD about my phone or a ROM. Im not being that "never satisfied" guy. Everything else with the ROM is great, its just this one thing.
Im using Eugene's B_Stock_1120_100 kernel, found here: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=28
TopShelf10 said:
Anyone else? Im not exactly sure if its Phone.apk, DialerTabeActivity.apk, or simply the act of voice calls that is causing it. But it seems as though whenever i make a call, or have an incoming call, my phone almost cant handle it. It lags out like crazy.
This morning, my phone started ringing. There was so much lag that i couldnt answer the phone in time. Also, when i go to hang up a voice call, it often takes the "end call" button almost 10seconds to respond. Lastly, just earlier, i ended a call with my buddy. It LITERALLY took 3 minutes between the time i ended that call, and started a new one. Thats how bad the lag was.
Anyone else experiencing this? Any ideas how to fix it? Maybe its the modem?
This lag is literally intolerable, and a major inconvenience to efficiency.
PS - No, im not running a lagfix. I experimented with and without, and i determined that overall my phone performs better without it.
PPS - This is not me being oCD about my phone or a ROM. Im not being that "never satisfied" guy. Everything else with the ROM is great, its just this one thing.
Im using Eugene's B_Stock_1120_100 kernel, found here: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=28
Click to expand...
Click to collapse
I would try starting from stock and working back up to nero v4.1.
I appreciate eugenes work but thats where most of my problems come from. Using nero v3 and experimenting with eugenes kernals(I was bored) I had constant lag, random reboots, panic/safe mode, freezes, couldnt access external sd card etc... Try starting from stock. Are you using titanium backup with system info.
intruda119 said:
I would try starting from stock and working back up to nero v4.1.
I appreciate eugenes work but thats where most of my problems come from. Using nero v3 and experimenting with eugenes kernals(I was bored) I had constant lag, random reboots, panic/safe mode, freezes, couldnt access external sd card etc... Try starting from stock. Are you using titanium backup with system info.
Click to expand...
Click to collapse
It sucks because this particular kernel of his offers almost everything i want in a 2.2 kernel (BLN, bootup/shutdown animations, lagfixes, OC/UV, and i also love the recovery menu).....although, with this ROM at least, the only lagfix that works is Voodoo, and the OC is only clocked at 1120ghz.
I was wondering if maybe this was causing it. And im mildly depressed to learn that it very well may be. I like TW's kernels, but they just seem to be battery destroyers.
So are you saying not to use this Eugene kernel at all? Should I try a TW one instead? Sorry but stock kernels suck and i want to avoid them if possible.
PS - I dont know what youre asking in terms of TiBu
I just tried it while on Wi-Fi, call came in, no lag answering it, I browsed engadget website, and no out of ordinary lag.
Flash back to stock and go back to the ROM, see if it resolves the issue.
EDIT: I am using Voodoo though
had same problem and i had just come from a fresh odin to stock. couldn't take it and went back to axura latest rom. plus vringo and video tonez don't work with roms with voice start and shutdowns.
hi all
i have been using nand android builds since day one , and in most of the builds i am having this same issue
sometimes when i receive a phone call the system just hangsout and then gives me a force close msg for the phone application !!
either way , if i force close or not , no further phone calls can be answered and the phone will freeze for about 30 seconds with every call
also when this happens the volume buttons wont modify the volume for the media anymore and the phone wont give any sounds
so is there something i can do to get rid of this ?
i tried android builds based on 2.3.3 and 2.3.4 , miui , sense , no sense , and i have this issue with all of them
again , it happens like 10% of the times
hope i get an answer to this
I want to ask what exactly rom are you using (does it use newest tytung r10 kernel?) and tell you that I have not been experiencing these issues with NexusHD2 2.8 rom (2.3.4).
fpu
i tried typhoon , rafdroid , ndt miui , and plenty more and i think typhoon and ndt miui has the latest kernel
have you ever tried receiving a phone call while the camera application is running
this seems to trigger the issue many times , not always tho
if you have the call recorder running turn it off. it was causing me lot's of problems.
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
domenukk said:
Hi,
I have the same problem.
No matter what kernel.
Already hardresettet and reinstalled everything. Radio, Magldr, Rom, you name it.
I even did format 10 (or what ever it's called)
Anyone else experiencing this?
Will get a logcat later.
Click to expand...
Click to collapse
+1 Same ****...
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
I just recieved a phonecall without problems.
Flashed the .12 radio from http://forum.xda-developers.com/showthread.php?t=611787&highlight=radio
however... My rom feels a bit slower now.
I am playing with it now.
Maybe clearing Dalvik cache will help. Or the issue comes back... Will see.
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Synthezys said:
Got the same problem, tried different ROM's but no result. I'm thinking already to switch back to WM 6.5 :\
Click to expand...
Click to collapse
Switching Radio to something.12 did the trick for me.
No problems for two days now.
domenukk said:
Switching Radio to something.12 did the trick for me.
No problems for two days now.
Click to expand...
Click to collapse
Leo_RADIO_2.12.50.02_2 - is this good?
Synthezys said:
Leo_RADIO_2.12.50.02_2 - is this good?
Click to expand...
Click to collapse
Yes that's it. Works fine for me
Mea culpa just today I had the same issue, for first time.
It's nothing major and reboot made it work fine again, but breaks my belief in HD2 as perfect, native-like Android device.
[email protected] said:
Are You using Magldr? I had that problem with mag. Than i switched to cLK. and im okay.
Click to expand...
Click to collapse
Beside changing of radio, THIS seems to be interesting.
I'm on MAG but considering switching to cLK (for many reasons - fastboot support being one, second that I don't need 99% of MAGLDR features).
Let's see how it all pans out ;-)
fpu
It just happened again! On the new rom... :/
There is a thread, however, stating that it's due to skype.
This can very well be true.
http://forum.xda-developers.com/showthread.php?t=1164058
but I need skype to stay on contact with my girlfriend... why can't android support skype natively instead of sipthings? -.-
Well still... anyone tried clk (instead of magldr) and skype?
Disable "Audible touch tones". It's under Sound in Settings, it did the trick for me.
I thought this was against robot voice?
well what ever. let's give it a try. Thx
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
An0n1mUs said:
In my case, first call after reboot always had the robot voice. To fix it I'd just hang up and call again. But lately on non-Sense ROM's, the first call would go with robot voice and then I would get Force close on the phone app. This fixed it for me.
BTW I have T8585 Leo with 2.12 radio.
Click to expand...
Click to collapse
For me recieving a call does nothing but a very bad noise. hd2 nearly freezes after that. I cannot hang up most of the times. If I somehow manage to, phone app forcecloses and connection cannot be reestablished until I pull out the battery...
Good old Robotvoice. I wish that was my problem.
i have switched to cLK about 3 days ago and till now i have got no problems at all
Hi,
in the last days with my S3 on every call I had which went for more than 1 minute the other person suddenly couldn't hear me anymore. Sometimes it happened after a minute, sometimes after 3 minutes, but in the last 4 calls it happened every time!
Reception came back after some seconds and from then on it was really bad, the other person had hard problems understanding me.
I searched around and found this thread of GNex owners having the same problem:
http://androidforums.com/samsung-galaxy-nexus/472451-vzw-other-person-cant-hear-me.html
Then I found it in the Issues DB too
http://code.google.com/p/android/issues/detail?id=24019
Do you guys know more? it is really bad, since this is my business phone so nearly every call is an important one and it really bugs me out.
Anyone having same problems?
I hope someone can help me out.
Yes I have the exact problem. It's driving me nuts and I've tried different roms and kernels.
Sent from my GT-I9300
Have you tried to DISable the noise canceling feature?
No but I will try it and report back.
By the way I'm on stock LF6 4.0.4 in Germany (with o2 as my carrier. Unbranded. )
Is the noise canceletion buggy?
Sent from my GT-I9300 using xda app-developers app
I've read that some kernels cause issues like this.
Also, in UK, in Birmingham on Orange, I have been having issues like this, and it usually occurs when the Signal Switches over from Orange to T-Mobile, mid call, and once onto T-Mobile signal, the call breaks up or goes quiet.
Maybe an issue switching from 2G to 3G or back mid call also?
BobFL said:
Have you tried to DISable the noise canceling feature?
Click to expand...
Click to collapse
Will try also. The only reason I haven't got rid of this phone is it mostly happens on o2 calls, I am on giffgaff which is run by o2, The op is o2! Hmmm
Sent from my GT-I9300 using xda app-developers app
just yesterday I again had the issue....and my noice cancelling was off...so this is not causing it....
I'm bumping this in hope someone has a cure.
The new rom LFB is not yet published for Germany but for UK. Perhaps it makes a difference? Can somebody in UK with LFB who previously had the issue please check?
Same problem, no solution
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
the-0ne said:
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Which ROM are you using right now?
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Try this for a fix
goto settings
sound
Toggle on then off or off then on the screen lock sounds then try again :good:
the-0ne said:
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Hey,
just so you know. I am on CM9 and I have kind of the same issue. Sometimes audio is unidirectional, both ways actually, unable to recreate it so far. What always seems to work is my bluetooth headset. Switiching between the two of them makes me lose audio entirely. I have tried many things, even rebooting the phone Sometimes it helps, sometimes it doesn't. I'm guessing it has something to do with BT.
I am NOT facing the issue with losing audio in the middle of the call when the display goes to sleep. The display goes to sleep because of the ligth sensor, btw. - not because the system is idling The display is not needed once the phone realizes it's attached to your ear (lights off).
It's driving me nuts
BUT: CM9 is amazing so far. It's fast, it's open, everything works just fine. Except for the phone as a phone of course
change modem
Oomahey said:
Which ROM are you using right now?
Click to expand...
Click to collapse
Using Stock right now. OTA updates till Jun 26th.
badaeng said:
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Click to expand...
Click to collapse
Mine's currently DDLF3
winwiz said:
Toggle on then off or off then off the screen lock sounds then try again
Click to expand...
Click to collapse
I've just tried this, will report back. How do you think lock sounds affect the mic, though?
avetny said:
change modem
Click to expand...
Click to collapse
Does CM9 come with an integrated modem switcher? I don't like messing around with "packages" too much. The more you mod everything, the less stuff has got to do with each other and it is more likely to run into trouble, because as a developer you can't really consider every side effect
So if this is actually about the modem (which I doubt, because the connection is just fine, it's just the audio output and input that is kind of broken) - what modem would I use with CM9? Can I just flash a random one over the current one?
Appreciate the advice.
Andreas
I notice that as soon as I take the phone away from my ear and the screen lights up I can again be heard... Wonder if there's a problem with the light off sensor affecting the mics too... It ALWAYS goes away when I remove the phone from my ear and the light sensor allows the backlight to come on again...
Might be a crazy thought but the evidence does seem to support this. I haven't turned off the light sensor in settings yet, if I even can, but was going to try next call...
I updated to BLG8 and I will see tomorrow if it happens again. Today I already had one call which lasted 11 minutes without interruptions. I will report as soon as I got more calls to test.
I had the same prob...
I just reflashed the official firmware frm the service centre.
Sent from my GT-I9300 using xda app-developers app
Same problem here. Tried several roms, kernels and modems. Only one working for me is Checkrom v3 with xxlbf... but here also after a while some calls it reappears... I reflash modem and I am set for the next couple calls... then again
Ps: i am from Romania on Vodafone
Sent from my GT-I9300 using xda premium
I'm the OP and I now didnt had the problem for 2 months with the last stock ICS build.
It seems to be resolved.
I'm now on JB since today (XXDLIH) and will report if it comes back.