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
Related
Hi all,
Would appreciate help and comments on the following issues I have with my new XDA IIs. Have always been a Palm user but some issues that I face looks more than just software issues.
1. Reception - When my phone comes out from an area without phone reception, it does not get back connection until someone calls or sms. So no outgoing calls possible until someone calls me or sms me. It's a major pain in the neck.
2. Bluetooth - does not work with my Motorolla headset which worked brlilliantly with Nokia and Sony Ericsson. I can hear the other party but they hear everything else loud except my voice soft.
3. Hangs a lot or rather, sluggish at times
4. Does not cut off calls even when end call button on the handsfree set is pressed.
Can anyone help???
In my opinion why don't you Upgrade your ROM, there's lots of articles in this forum how to upgrade your handset.. "Search" Follow the instructions and I assume your device will work properly once for all
Get the latest v1.31 ROM update from O2 service center
As far as the hangs go, I would clean out every unnecessary thing that's in the \Windows\Startup folder. This is stuff that is automatically started up on a soft reset. Stuff like the "aPerSave..." file links for example should be moved somewhere else for safe keeping. I have a PDA2K, so I don't know if you have the same files as I do, but I imagine they are pretty siilar. The Pocket PC OS is limited to 32 running processes and out of the box the PDA2K is running close to that number already. I imagine the IIs is configured similarly. Starting more than 32 processes can cause others to shut down prematurely, causing hangs. So, getting rid of the unnecessary processes leaves more free for apps later on as you are using the device.
I had many unexplained hangups on my PDA2K until I cleaned out that Startup folder. Once I did that, the hangs vanished.
Answer to Question 4:
Unfortunately the button is not supposed to hang up. (I think it puts it in Mute mode?)
Firstly, I have been searching this forum for about 2 hours. I have found a few threads with the same issues, but they are either not relevant or I have tried the solutions within the threads and they have not worked. Also, the threads I have found are a few months old. I have also searched the ROM thread seen below.
ROM: [06 Nov 2011][MAG/cLK] NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13]
Device: HTC HD2
ROM Installation Method: MAGLDR 1.13
SPL: 2.08.HSPL
When I accept an incoming call, the phone application hangs and after about 10 seconds I get a force close notification. Sometimes this is accompanied with a buzzing sound from my speaker. In some instances I have to remove the battery to restart the phone as it totally freezes.
This happened on Android 2.3.5 (of the ROM linked above) so I upgraded to 2.3.7 (of the ROM linked above) to see if it would fix the issue. It has not. I also wiped the phone and reinstalled the ROM, and again it hasn't fixed the issue.
Also, I do not have Skype installed so it's definetely not that.
I would have posted in the ROM thread but it wouldn't let me.
Any suggestions?
Many thanks in advance. I can provide additional information should it be required.
Benetration said:
Firstly, I have been searching this forum for about 2 hours. I have found a few threads with the same issues, but they are either not relevant or I have tried the solutions within the threads and they have not worked. Also, the threads I have found are a few months old. I have also searched the ROM thread seen below.
ROM: [06 Nov 2011][MAG/cLK] NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13]
Device: HTC HD2
ROM Installation Method: MAGLDR 1.13
SPL: 2.08.HSPL
When I accept an incoming call, the phone application hangs and after about 10 seconds I get a force close notification. Sometimes this is accompanied with a buzzing sound from my speaker. In some instances I have to remove the battery to restart the phone as it totally freezes.
This happened on Android 2.3.5 (of the ROM linked above) so I upgraded to 2.3.7 (of the ROM linked above) to see if it would fix the issue. It has not. I also wiped the phone and reinstalled the ROM, and again it hasn't fixed the issue.
Also, I do not have Skype installed so it's definetely not that.
I would have posted in the ROM thread but it wouldn't let me.
Any suggestions?
Many thanks in advance. I can provide additional information should it be required.
Click to expand...
Click to collapse
this isnt something about your phone so try another rom or tell the developers.
linkin_p said:
this isnt something about your phone so try another rom or tell the developers.
Click to expand...
Click to collapse
thanks a lot, i have same issue...maybe i'll try another ROM
buzzing HD2
Sometimes it happens on my HD2 on diferent rooms: NexusHD2 3.2, NexusHD2 ICS 1.1, MIUI 1.12.30, MIUI 2.2.17. It is not often. Any sollution?
It's same here! I am starting to think that the problem is with my phone! I tryed meny different ROM and settings...it always the same!
It doing it 2-3 times per day.
How to fix it ?
same problem
I'm using CM9 (v2.8) android 4.0.4 and facing the same problem. I tried many ROMs but can't fix the problem. Also tried some solution on this 4rum but no help until now.
I'm going to throw my HD2.
Same here
I have the same issues with different rom using nand or nativeSD.
1 on 2 receiving call, the phone freezes with a buzzing sound. I must to take the battery out to restart the phone.
same problem
I have the same problem with my HD2!
The phone freezes after I receive an incoming call with a buzzing sound/no sound. Sometimes it shows the error message of com.android.phone process, in other cases I need to remove the battery and restart the phone.
I have tried different kind and version of ROM(for e.g. NexusHD2, MIUI, TouchWizMod v3.0) but the freezing issue is still not solved.
As far as I checked the freezing is not related to any kind of installed software.
If anybody has a solution to this problem please share with me/us. I really do not want to get rid of my HD2.
Thanks in advance.
------------------------------------------------------------------------------------------------------------------------------------------------------------
I have found the solution. The reason why the phone did not work is the Viber application. I uninstalled it a moth ago and thence everything works well. I use the WeChat app instead of Viber and my phone works like a charm.
By the way, a member of the Viber team has commented on this forum that their application does not support any kind of custom ROM currently.
Im facing the same problem,its killing me, its been worst recently ! I cant answer any call on my HD2
this problem happend first time on android 4+ roms,
I tried diffrent roms after that, but still not fixed, anyone can help us to find a solution?!
-----
anyone using CLk has this problem?!
Im using Magldr
Im having the same problem here. Found no sulition currently. ROM - tytung NexusHD2 2.5
The phone freezes after I receive an incoming call with a buzzing sound/no sound. Sometimes it shows the error message of com.android.phone process, in other cases I need to remove the battery and restart the phone.
Click to expand...
Click to collapse
hmm same here, tried some different ROMS - SD (froyo) and NANDs (2 gingerbreads, now ICS), tried these on both of my HD2s, also changed RADIO from 2.15.50.14 to 2.08.50.05 - nothing helps.
sometimes when im getting a call (usually it happens twice a week, some weeks more often, some less), i press the button and the phone/app freezes, sometimes with a buzzing sound.
after that, system doesnt respond normally, on GB sometimes it autorebooted....
also tried without viber AND tried directly after reinstalling the different ROMS with no contacts, original ringtones - also happens there sometimes!
i dont think that could be a hardware problem, because both of my hd2 phones act the same way.....
any solution since that time?
At the moment I have latest Jelly Bean by cotulla, with Cyanogenmod, and when I make a call, the screen is black (turned off) even though I don't have it close to my head and sensor is not covered. When I abort the call, it doesn't respond and stays dark with button panel highlighted for several seconds, and only after I press power button for several times it awakens. The same happens for incoming calls. The phone is not usable as phone with such things happening... That's frustrating.
So, let me sum up what people (and I) have had on the subject:
1. Various Android ROMs were tried and issue is always present.
2. In my case, stock Windows 6.5 has a very similar issue - incoming calls are even ignored! At least I had the described problem after I decided to have an "old" but working phone and reverted to the stock ROM instead of Android. Alas, the phone was still having glitches when answering.
3. We don't know exactly how many HD2 are affected by the issue but it looks like more than 1% which is pretty much to be a serious issue.
I might assume we faced an intermittent hardware issue, that does not always reveal itself, and can only be reproduced after a certain "failure". I think it's hardware dependent because my phone was working fine but suddenly ceased to do that.
I'm very sceptical about fixing this issue for me or other users. It's an obsolete phone and any mass hardware issues that is not reported by manufacturer (btw, could this be checked out?) will scarcely be considered. The whole thing makes me think we just have to switch to our phones are gaming/browsing accessories, since it just doesn't work and the issue is apparently non-trivial to be examined. I would be though glad to provide any information and logs... but who cares? Even cotulla doesn't think HD2 is worth developing any more....
Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
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.
Hey guys,
since amazon is out of stock - and therefore, getting a replacement device is kind of difficult - and I'm still waiting for oneplus to respond, I'd like to hear from you if you encountered similar issues with your OP6:
During calls, I can hear the other side just fine, but the person on the other side can not hear me most of the time. Sometimes, it seems some shreds of voice are being transmitted. It happened on about 90% of calls. There are calls that are perfectly fine, but most of the time, the phone is unusable.
What I could test so far:
- it happens in handset mode, speakerphone and with a bluetooth headset
- it happens on both SIMs, swapping them does not change anything
- it happens on 2G as well as 3G (no VoLTE available yet)
- the microphone works fine if I use the audio recorder (outside of calls)
- calls made via VoIP-software seem not to be affected, though audio quality on the other side isn't that great either (but that might be unrelated)
- sometimes, it seems to happen mid-call
Both SIMs did obviously work fine in my previous device (OP3), signal strength in calls is about -70dBm, both SIMs are on T-Mobile (Germany).
I'm on an A6003 with OOS 5.1.5, Baseband is MPSS.AT.4.0.c2.10-00012-SDM845_GEN_PACK-1.147963.5, bootloader is unlocked and rooted with Magisk.
I did find a thread describing similiar issues on the oneplus-forums (https://forums.oneplus.com/threads/dual-sim-issues.838595/#post-18474985), but I'm currently unable to login to their forums, for whatever reason.
Can any of you guys give me a hint on what to test to narrow down if it's a hardware or a software issue or maybe even suggest a workaround?
I'm happy to provide more details where necessary.
I'll probably have to switch back to my OP3 anyway, so I could give the Android P beta a shot and see if it happens there as well.
Best Regards.
So, it turns out (*after* factory resetting and flashing Android P of course ><) that the echo test number I've been using is equally broken on otherwise working phones, so most of my test results are null and void. I'll give it some more testing...
Just a heads-up for users who may stumble upon this thread in the future: call quality problems are mostly gone after updating to 5.1.6 (and replacing SIM-cards).
I've bought a OP6 just three days ago and I've updated it immediately to OS 5.1.8 (I've also rooted it) and the phone calls problems (call drops and other person can't hear my voice sometimes) are present.
I hope OnePlus will fix the issues not so later...
Unfortunately, I can't rule out that replacing the SIM-cards actually fixed the issue - it might be worth a shot. I haven't had any issues since my last post.