Hi Guys, Forgive me if this has been asked before, but I sure could not find it.
Anyway, My problem is: I recently updated my SG Note to ICS (India). After the upgrade I am unable to receive or make phone calls when my phone is connected to the Car Dock (Original Samsung Accessory). When I get a call with the phone connected to the car dock I am unable to see who is calling (blank screen) but can hear the ringing and then after a few rings I get an error message that says - "Phone Application Failed to Load". By the way, all was perfectly alright before ICS update.
Is anyone else facing this issue?
Please help with a solution, as I'm unable to receive or make calls or charge the phone (for fear of missing important calls) while travelling.
Hi Guys, No body has a clue to this issue. 54 reads and not a single reply!?!
Related
Hi,
I recently have had a big problem with my Fuze w/ the Energy Rom 2.0 Build 41609. Whenever someone calls be, and I attempt to answer the phone, nothing happens. The ringtone stops but the phone freezes for a few seconds then shows that I have a missed call.
Anyone had this problem before?
Thanks
-Roger
Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!
samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?
Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!
that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...
just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App
Hello,
I recently got lollipop update for my Nexus 5 OTA, After updating my phone i am experiencing issues while answering incoming calls. When i get an incoming call my phone rings and vibrate but nothing shows up on the screen.
I have to press the power button to bring my screen back to life and then unlock it to answer the incoming call. Without unlocking the phone i am not able to answer any incoming calls
This was not happening with 4.4.4. I am not sure if anyone else is facing same issue and i am not able to locate any workaround under settings of the phone. Any help on this will be highly appreciated.
Roy2208 said:
Hello,
I recently got lollipop update for my Nexus 5 OTA, After updating my phone i am experiencing issues while answering incoming calls. When i get an incoming call my phone rings and vibrate but nothing shows up on the screen.
I have to press the power button to bring my screen back to life and then unlock it to answer the incoming call. Without unlocking the phone i am not able to answer any incoming calls
This was not happening with 4.4.4. I am not sure if anyone else is facing same issue and i am not able to locate any workaround under settings of the phone. Any help on this will be highly appreciated.
Click to expand...
Click to collapse
Unfortunately this is a known issue that hundreds, if not thousands of people have been experiencing and reporting ever since the phone was released a year ago. So yes ever since 4.4, before even 4.4.2. Even more unfortunately it is a known issue that neither Google nor any carriers admit to own up to. Anyways to my knowledge no one knows if it is a software or hardware issue, but it is most likely not a carrier issue since it is reproduced on multiple different carriers. Anyways I will link you to the Google Forums thread that started on this issue a year ago and has hundreds of people posting and reporting it in that thread. You can find that post if you click right here.
The only solution is a work around, not a permanent solution. If you find out that someone called you, and the phone did not ring, restart the phone. It seems to have resolved the issue temporarily. I always restart mine every 2 to 3 days anyways to try to prevent it as little as possible, so that is what I would suggest. Also maybe state on your voice mail if you did not pick up to leave you a voice mail or send you a text so you know they called, because you been having issues with calls on your phone. That way you know someone called, because you will still get the text message or voice mail notification.
I had the problem mentioned in the second post (which may not be what OP was describing) and I solved it by trying out different radios. Latest one with Lollipop is fine, but the two before that weren't good.
hi all,
i noticed that during calls with the bundled headset (mh750) after rough 3 minutes the other side suddenly can't hear me, but i can hear them.
the receiver just thinks that the call has dropped.
I tried also another headset (of an old htc pre-android era) but the issues is still there.
googling for some minutes i read that there was a Android 5.0 bug that gives similar issues.
I'm not sure if it's a Hardware (z3's) issue or a software issue (android)
my firmware is 5.1.1 - 23.4.A.0.546 on d6603
Hello,
I have the same issue, after some days i lost the signal, ( with the stock firmware ) the phone was never rooted.
After i send to service, they told me the phone can not be repaired because this is related to mechanical shock, also i lost the warranty.
I'm not sure if this is ture.
Best.
Cris
Google now issue. Disable voice activation on any screen setting. Should fix it.
Does anyone else have this problem? I just got the Galaxy 4 smart watch (bluetooth, not lte version) a few days ago. When I initiate a call from the watch it dial and says "See phone" and the call is now coming through the phone. I can click a button on the phone to send the call back to the watch but obviously this defeats the convenience of not needing to have the phone in arms reach.
My husband figured out that its some kind of interference with other connected bluetooth devices (even though they are off), like my car and handsfree earpiece. If I unpair each of those items, calls work as they should. As soon as I re-pair another bluetooth device the problem resurfaces. I'd rather not have to pick one or the other to work if I can help it. Samsung support hasn't been able to fix it. Any ideas?
I should have clarified, I'm wondering both who does and who doesn't have this issue. Please comment even if yours works perfectly.
Samsung support seemed to suggest it was a software issue thar might be able to be fixed in a future update but I'm not sure if its an issue for anyone other than me.
Maybe you should take a look at this topic https://forum.xda-developers.com/t/...hange-default-behavior.4369423/#post-86031957