I upgraded my Captivate to gingerbread/talon/continuum yesterday.
That went fine and everything was hunky dory.
Phone was working fine the whole day today, incoming/outgoing calls, data.
I came home and installed Skype and thats when all hell broke loose.
Now the phone part is dead (kinda!). I can make calls fine but if I get a incoming call, the call gets disconnected after 1 ring and I get a msg popup (like some error) but I cant really see what the message is.
I also noticed that it disconnects me from ATT network when a call comes in and then after a little bit it reconnects.
I also verified this by going to the About->Status screen and then making a call.
It normally says ATT but for a couple of secs after call drop it says 'Unknown'.
What did I do to screw it up and how can I fix it?
Thanks
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
mommehK said:
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
Click to expand...
Click to collapse
Sorry, I should have added that to my first post.
Yes, I did uninstall Skype and reboot the phone, just incase, but no difference.
Still the same.
Update:
After playing around with various things for a couple of hrs, I finally gave up and reflashed Continuum.
Everything started working again.
Applied my Ti backed up config and loaded Netflix. Same problem. Dialer died with an incoming call.
I reflashed Continuum again and everything started working as expected.
I then applied my Ti backup, still everything working.
I am in the process of updating all my apps and then lets see if everything is still working.
The only thing that is missing for now is the Netflix app.
I will keep everyone updated if its the Netflix app causing the issue or its the Skype.
activemind: Keep us posted if you find a cause. I am on a Samsung Vibrant (3g) via TMOB but have been having the same issue today with a completely different rom (simply honey). This is actually about the 6th thread I've found in the past two days having this same issue on Galaxy S phones.
I have had this problem before and what caused it was restoring system data with titanium. Make sure you are only restoring apps.
Sent from my GT-I9000 using XDA Premium App
Related
Hi all,
Sorry if this has been noted as one of the bugs with the official 6.1 upgrade, but after a bit of searching I was unable to find anything. Everything seemed to be fine until a couple hours ago. I was at work and hence had not used the phone itself for a while. I was setting up my email accounts again. then a hour or so later, the phone started vibrating for a notification of new emails and would not stop. I had to do a reboot. Now, every time I try to place a call, it uses the speakerphone, and will not switch back no matter what I do. I hit the button for speakerphone and there it says it has changed, and the icon in the status bar on the top also changes, but it still uses the speakerphone. I've not tried with my bluetooth in my car yet to see if that is working ok...
Any suggestions? This is a real problem for me and one that I need an answer to sooner rather than later.
Thanks in advance for your help.
Solved - the problem was with SRS Wow HD audio driver
Just FYI - incase anyone else is having the same problem.
I worked backwards and unintsalled each program I had put on one by one and tested the phone. Turned out that I forgot I had installed SRS Wow HD sound driver. Once I uninstalled that and rebooted, everything has worked fine since.
Sad that this does not work with 6.1 as it was a really nice piece of software.
Hi all,
Friend and I both have the Incredible S, loving it! He has a slight issue and I can't for the life of me solve it. Everything was working fine but now when he has an incoming call and the screen is off the incoming call screen flashes up briefly then disappears and device shows normal 'desktop' - you can't answer the call!
If you call his phone and the screen is active, incoming call screen pops up as expected and you can answer call.
Any ideas peeps?
Thanks
Ant
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Sliphorn said:
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Click to expand...
Click to collapse
Never worked it out, friend did factory reset in the end to fix it.
Ant
Bummer. Here's some info:
Latest Fresh EVO
Rom Manager
Rom Manager Janitor
Juice Defender Ultimate Juice
Titanium Backup Pro
Cachemate for Root
ShootMe
Adfree Android
adbwireless
Call Control (problem before this, though)
Launcher Pro
Any hints?
Having the same exact issue. This sucks... This started today for me around noon ( no calls before then), and has persisted throughout the day. Yesterday was fine.
I use Google voice for all of my calls.
The only thing I've done today that I haven't done every other day was that I installed the Gtalk app this morning. In the past, I've used Gmail directly. However, my computer was off during at least one of the phone calls I received today, so I can't imagine this could be it...
Perhaps because I installed gAlwaysIdle (an addition to Gtalk that makes you never go idle or always be idle) as well?
Does this correspond with anyone else's experience?
I'll probably just reflash my phone
<Rooted Atrix 4g running GingerBlur>
hmm this sounds like a serious firmware problem tho..
all i could suggest is flash a firmware that the most of the ppl are using, and dont got probs with...
well doing a good reboot seems to help alot these days. So disable the fastboot option en turn it off, wait a while (10 secs should be enough) en start the device again.
Also had some of the trouble like crashing things and this solved it for me. Give it a try and hope it will fix it.
Otherwise there seems to be no other way than a factory reset (go htc!)
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
tigane1 said:
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
Click to expand...
Click to collapse
Try aoip its up to date and works good.
schuylkillparanormal said:
Try aoip its up to date and works good.
Click to expand...
Click to collapse
working on downloading it but the download keeps failing -_-
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Mwas. said:
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes rom and cache/dalvik. And if I forgot I went back and wiped and re-installed it.
tigane1 said:
Yes rom and cachredowvik. And if I forgot I went back and wiped and re-installed it.
Click to expand...
Click to collapse
There's nothing wrong with the link try redownloading the ROM something might of got corrupted.
I fixed it. Kind of
I did a bit more searching using some different terms and people were having trouble with the proximity sensor on their phones causing similar problems so I turned mine off and the problem corrected itself! So now I guess I just have to deal without having a functioning proximity sensor during calls, oh well, not a biggie. I appreciate the help though guys.
Hi,
The last few days my dialer has been ridiculously slow in making a call. Typing in numbers is fine and accessing the call history is also fine but if I touch an entry to start a call it takes anywhere from 10-20 secs for the call to start. Oddly enough this issue is not present when using car dock mode.
Has anyone come across this before and found a solution?
BTW I am on stock 4.4.2
Thanks
I should probably mention what I have tried already
- Deleted call history
- Cleared data and cache from the phone app
- Turned off a tasker profile I had that involved dialing a number
- Uninstalled recently installed apps
- Turned off fast boot and restarted (this actually helped for a short while but it has reverted)
Any other ideas? I am reluctant to do a hard reset but if nothing else works then I might just do that or upgrade my phone since I am due an upgrade soon
Deanicus said:
I should probably mention what I have tried already
- Deleted call history
- Cleared data and cache from the phone app
- Turned off a tasker profile I had that involved dialing a number
- Uninstalled recently installed apps
- Turned off fast boot and restarted (this actually helped for a short while but it has reverted)
Any other ideas? I am reluctant to do a hard reset but if nothing else works then I might just do that or upgrade my phone since I am due an upgrade soon
Click to expand...
Click to collapse
did you try factory resset??
jujak82 said:
did you try factory resset??
Click to expand...
Click to collapse
No, not yet. I am hoping to avoid that if possible
Anyone else have any ideas? The issue is not with the dialer but quite literally with the phone app although as I mentioned in my OP, if I select a number to be dialled from the dialer in the car dock app, it works fine. Very perplexing!
For anyone who might be experiencing the same issue, whilst I have not fixed it I did find that if my phone is connected to a network (either via wifi or mobile data) the issue disappears. I don't know why that happens but it is a least a bit of a workaround
Hi,
Just having some issues with my note today. For some reason other side can hear me fine when making a normal voice call, but when using Skype, Viber or even trying to give a voice command to google it just won't listen.
The mic is working since voice calls are working just fine.
Does anyone have any idea what could be the problem?
I'm rooted with DK 4.1
Thanks!
I had a few issues with DK including mic issues. Like people couldnt hear me when I'm doing wifi calling and all those messaging programs also. Long time DK user since Note 3. I tried FireKat and now everything works, including Titanium (no stalling when recovering apps).
Thanks. I'll give this a try.
I'm on DK as well.
For me the issue creeps up after one phone call.
On clean boot it works fine and I can shoot videos or use Google Now etc. without issue. As soon as I initiate a call and the other side starts ringing I can hang up and never get mic functionality again for anything but phone calls.
From what I can tell it stems from a SuperSU binary change back in December. Why it only affects a few of us I don't know. I posted about it way back in December within the DK thread. How I attributed it to SuperSU is at the time I rolled back to an nandroid backup that worked and then applied one app update at a time until the issue creeped up again.
About a month ago I messed up and said yes to binary update on my phone . . haven't bothered rolling back to a backup though . .
Been planning on doing a full on wipe of the phone but decided to wait to see how things play out with LP based ROM updates.
Thanks for the details. I just moved to firekat and am really happy with the ROM
So I finally took the time to do a full wipe and install Dynamic Kat 4.1 clean and my microphone issue is resolved. Happy camper now.