[Q] Can't hang up & dropped calls? - myTouch 4G Q&A, Help & Troubleshooting

If anyone has advice, I'd be very grateful: Just today I've started running into some issues with the dialer, calls and call waiting:
-When I'm on a phone call and I ignore an incoming call, my first call disconnects
-Occasionally I can't end a call (hang up)
-Occasionally when I dial a number, I hear nothing. I hang up and redial and the call goes through.
-Sometimes I've been seeing the Dialer at the top of the battery use list with 90+%
I'm running CM 6.1.2 RC2 glacier
Any ideas? I've force-closed Dialer and rebooted so far, still having issues.

U need to ask stuff like this in the thread of the rom.

thanks, i'll do that

inkling said:
If anyone has advice, I'd be very grateful: Just today I've started running into some issues with the dialer, calls and call waiting:
-When I'm on a phone call and I ignore an incoming call, my first call disconnects
-Occasionally I can't end a call (hang up)
-Occasionally when I dial a number, I hear nothing. I hang up and redial and the call goes through.
-Sometimes I've been seeing the Dialer at the top of the battery use list with 90+%
I'm running CM 6.1.2 RC2 glacier
Any ideas? I've force-closed Dialer and rebooted so far, still having issues.
Click to expand...
Click to collapse
This sounds like a bad flash.
Redownload the file to make sure you have a good clean copy.
Make sure you are using the correct gapps.
In recovery mode, WIPE DATA/FACTORY RESET BEFORE FLASHING!
On first boot let it sit at the sign-in screen for a solid 10 minutes before you touch it. There are all sorts of background processes and "thinking" happening.
I ran that rom for a few weeks and it was perfectly stable with none of the problems you mentioned.

Thanks, but I'm fairly certain the flash was alright. I ran it for several weeks without problems, installed it as you described and after a full wipe. MD5 sum was fine, etc. Well in any case I've moved on to the nightlies of CM7 so we'll see... thanks for the advice.

inkling said:
Thanks, but I'm fairly certain the flash was alright. I ran it for several weeks without problems, installed it as you described and after a full wipe. MD5 sum was fine, etc. Well in any case I've moved on to the nightlies of CM7 so we'll see... thanks for the advice.
Click to expand...
Click to collapse
Ah right on, I'm right there with you. Keep my tips in mind for next time, especially wiping before flash and letting it sit on first boot. Big improvement in stability!

I will, thanks!

Related

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.

Mogul is so slow it's crawling!

I updated to rom 3.35.651.2 (official rom) about a month ago. I added all my warez and tweeks. Everything was working awesome until about 5 days ago. Now it's all FOOBAR.
I have to soft reset my phone several times a day (more than 5) just to make it usable. Else it just stalls and the screen shows bits of different things thats going on.
For example, on the home screen, i try to open a txt msg, and it shows the body of the txt msg, but the top and bottom bars of the home screen. That's it. It lags so bad only a soft reset will correct it.
I'm not sure what's going on but i read a while back others were having similar issues with the update. Did we figure out if that was a bug or is it just a few unlucky people?
I run memaid to clean it up and it still doesn't help. I was using spb back up but that doesn't work on this rom either, it just hangs although it appears to create a file, and the file is then unusable (the backup).
What are your thoughts?
Just so you have a better idea of how bad it is, i just made a call using one of the spb phone suits. It's the picture calling deal. I click on the tab to show the pictures, i click on the picture and the phone dials and the call goes through.
The problem is that unlike it did before, i can't even pull up the call status screen, which would normally come up on its own. During the call, i can't even switch to it, it's stuck on the home screen.
The call ends, and all you can see is the same thing since the call started, the selected contact highlighted. And it's stuck there!
Any ideas?
thanks
Flash a DCD titan [6.1] rom.
Dunno what you did, but it seems to be the installation [update of registry] that causes the phone to become so damn slow. Custom roms are lean and mean.
Yeah, that's what I was thinking of doing but i'm a noob with the custom roms. I read up on them when I updated to the latest official rom, but i was confused
I guess i'll have to try to figure it out again.
Thanks for the reply.

Guava has not been working for 2days

I use guava + gizmo+ gv quite often, but as of yesterday I hvnt been able to place a call at all...it would still register and give me the green light, but when I dial and hit call, it just stays there without doing anything
3g and wifi...no dice...
Anyone else experiencing this?...any resolution?
Itried re installing the app.....and even wiped my phone clean and tried, also downgraded to an older cyanogenmod...still won't work
bigjoe87865 said:
I use guava + gizmo+ gv quite often, but as of yesterday I hvnt been able to place a call at all...it would still register and give me the green light, but when I dial and hit call, it just stays there without doing anything
3g and wifi...no dice...
Anyone else experiencing this?...any resolution?
Itried re installing the app.....and even wiped my phone clean and tried, also downgraded to an older cyanogenmod...still won't work
Click to expand...
Click to collapse
Use SIPDroid. Its free and they are always updating. Gizmo5 stole the code from an older SIPdroid version anyways.
ditto
try to log in to your GV account and make the call from there and connect the call to your Gizmo5, your call might go through. It worked once or twice today. the weird part was when I received the call, the phone no started with "sip:34234234" where 34234234 is my GV #
I think what's happening has something to do with Google's recent purchase. The first thing they did when they bought Gizmo5 was removing the registration page. so let's hope the next step would be integrating GUAVA into GV App.

[Q] Can't make phone calls, Data still works

So, I went to make a phone call earlier and realized I hit the wrong number. I ended the call immediately and then immediately tried to call the right number and the call just ended before it even rang. Now I am unable to make phone calls as every time I try to call any number it says calling and then the call just instanly ends. Anyone have any idea what is going on?
First option would be to power off and pull the battery. If it doesn't work after trying that, than second option would be to perform a hard reset.
Regards,
Tom
are you running the stock rom, or are you rooted with clockwork recovery installed, and running a different rom?
I have definitely tried rebooting, removing battery, sim, etc. I have now discovered that this only happens when I am at work. I am going to have to do more extensive testing to figure out exactly where I can make calls and where I can't but could it have something to do with which tower I am connected to? I have full signal and data and sms work fine.
*edit* I have not rooted it yet or installed a custom ROM.
Okay, well. Now it appears to be working. Now I'm really confused. Anyone have any ideas what is going on?
nope, it sounds nuts to me.
i would recommend using the phone a lot and trying to recreate the problem under specific circumstances. perhaps its a faulty piece of hardware.

[Q] No Voice (incoming or outgoing) on Nexus 4?

OK, having a huge problem with my Nexus 4. I'm still running stock kernel/ROM (although I am rooted) and everything about the phone works great EXCEPT for the phone itself! What I mean by this is: everything works (data, texts, tethering, et cetera), I can make and receive calls... but on those calls, there is no sound in *either direction*; when on a call, the mic doesn't pick up my voice, nor does the speaker relay the caller's voice. WTF?
My in-call volume is set to maximum, as checked via Power Toggles.
I've also noticed that the phone has a hell of a time hanging up after a call. For instance, I make a call on the N4 (again, no voice/sound during said call), and when I go to hang up the phone screen simply says "hanging up" and hangs like that for almost a minute. If I try to make another call after that, I get an error "Call Not Sent".
Any ideas how I might be able to track this problem down?
I should also mention that I don't know how long this problem has been present. I really don't use voice calling very much. When I tested the phone when I first received it, I simply made a call from it and to it from our land line and made sure it rang... I didn't think that there might be any issues with the call itself!
I have a brand new N4 that I just rooted using WugFresh toolkit and I see now that I can't hear anything during a call nor can the other person hear anything.
I've tried downgrading to .33 and .27. Also reflashing .48 with no success.
What should I do?
If you are experiencing the same problem I was, it wasn't fixable. I tried everything (reflashing stock, trying different ROMs, etc.)... and apparently it was just a hardware defect. I contacted Google and after explaining the issue (which they hadn't heard about at that point) they shipped me a new phone, which works perfectly.
I would highly recommend not wasting your time trying to diagnose the issue further and get in touch with Google about getting a replacement.
Cheers,
Matt
Thanks a lot for getting back to me. I contacted them and they already sent a replacement unit.
I found a thread on Google forums with six pages of people complaining about this. Apparently is not an isolated problem. Half of the people have the problem after updating to 4.2.2 and the other half (last pages) are all with new phones (4.2.2).
jumped in been a while since I had a play with LS - first impression love the splash screen :good:
Same problem, no warranty
Lucky you guys who were still under warranty. My Nexus 4 is 2 years old now and I just got this problem. It seems to be software related. The mic and speaker works for anything else other than placing phone calls. Furthermore, even if I plug a standard headset thought the 3.5mm jack, still no luck. The same with bluetooth headset.
It's interesting that when this problem started I would be able to place or receive a call once per reboot, i.e., after rebooting, the speaker and mic would work on the first call, but not for the second call unless I reboot the phone. Now I doesn't work even after reboot.
Gargabe?
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem.
Reverting to stock solved the issue form me until a fix for CM11 will be found.
BTW there is a bug report for CM11.
I can't post links but the code is CYAN-5728 on the CM bugtracking system.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
The issue is with Google Play Services. more specifically the checkin service within it.
(this is from the CM bugtracking system , code: CYAN-5728, as stated by pupillo)
download/install the app "DisableService" from the play store. (must be rooted)
under the [System] tab, browse to "Google Play Services", tap it, then browse to "checkinservice", uncheck. (it will prompt for superuser, allow)
restart phone
try placing/receiving a call
none of u guys spent even 1 second to check this forums for answer. there have been at least 2-3 threads about this issue, all of them containing/linking to the fix.

Categories

Resources