Hello everyone,
I have recently been experiencing a weird issue with making or receiving calls. About 20% of the time, I am able to successfully make and receive calls, and majority of the time I just see the dailer timer progressing but no audio output from the earpiece speaker. When I insert headphones or try speakerphone I am still unable to hear any audio from calls. However, music plays just fine from headphones. I can also send texts and MMS with no issues. Sometimes when power cycle the phone it will work for a couple calls only.
I have literally tried everything. Flashed different modems, went back to stock touchwiz, numerous factory resets, removed SIM/SD card, etc. with no luck. I am currently on the latest GPE build since my GS4 has the MDK bootloader. I have determined that it is not an issue with this ROM itself since no one else is experiencing this issue and I have seen it on the other ROMs I have recently tried.
If anyone has suggestions I'd really appreciate it. I have searched for days online and have not been able to find a solution that has worked, and I am beginning to think it is a hardware issue although my call audio works some of the time. Any input would be greatly appreciated.
OK Google Voice Search
I had a similar issue. I was able to resolve it by disabling the setting where you can say OK Google from anywhere on your phone and that fixed it. Unlike you, I am on the latest update, rooted. Maybe try messing with OK Google Detection settings, disable all of them and see if it starts working, then re-enable 1 at a time until you find the issue.
Dear community,
I'd like to adress an issue which occured on my i9300 after the udate to jelly bean over a year ago. It was the last official firmware update for the device and I was using the stock rom then. Soon, I noticed a huge distortion of my dialogue partner's voice and even the dial tone during hands-free in my car. Talking hands free is not possible because of that if the issue occurs. Random switching on and off the mobile seems to fix it sometimes, but not reproducibly. Meanwhile I am using kit kat via SlimRom (Slim-i9300 4.4.4. build. 9.0-OFFICIAL-8312) with Boeffla kernel (boeffla-kernel-2.8-Omnirom-i9300.recovery), and the problem still persists. Switching from bluetooth to phonespearks and back during a call sometimes fixes the issue, but sometimes it even worses it. Basically, sometimes distortion is there, sometimes not. On the web I found a few reports of the problem without solutions. Recently, I tried several modems / radios for my device because I had heared that might fix the problem, but to no avail. I further tried to alter the audio seetings in engineerig / service mode like suggested in this thread, but encountered a "locked" Audio-submenu - I simply cannot open it, while all the other options worked. This seems to happen and people say to change your modem, like in this S2-Thread. However, all the modems which I tested neither enabled me to enter the audio-menu, nor fixed the main issue - the distortion. Lastly, I dug up this thread mentioning to unblock the keystring-file in order to access the audio menu, but I have no idea what exactly I should do. Apart from this, I have no clue whether fiddling around in the service/audio-menu can fix the distortion-issue anyway. I should add that the device's speakers work flawlessly during non-hands-free calls. Furthermore, transmitting music via bluetooth to my car never causes distortion. Also, other devices, among which a S4 with lollipop, do not cause distortion.
So, long-story short: Can anyone help with the distorted audio-issue during hands-free? I now rely on hands free communication and will have to switch to a reliable device if I can't get it to work on my i9300. Thank you very much. Obviously, downgrading to a pre-jelly bean-Android might also fix the issue, but to be honest I don't want to give up all the benefits of kit kat in terms of usability.
Best regards!
My calls are always on speakerphone, doesn't matter if the speakerphone button is on or not, I don't believe this is a hardware problem even though my screen was replaced a few days ago, I mean how could it possibly be. I can't be the only one with this problem, I have searched everywhere, seems like I am. I'm running stock (rooted) so I don't believe it is a software problem either, I have tried rebooting and clearing cache so far.
Details: Stock E2303 MM Rooted. Only thing that could be screwing with audio is Viper4Android, and I uninstalled its drivers already. Also the headphone jack is dead if it matters.
Sorry for creating thread ahead of time, but the problem has been fixed by flashing stock using Flashtool, incase someone has the same problem.
I bought Xperia x a few weeks ago and I found audio output through loudspeaker is less compared to other phones out there. So I contacted sony care online and they told me to do speaker diagnosis test available in settings app. While testing I wasn't able to hear anything from speaker. Does that mean that my loud speaker has problem? Can anyone out there check and confirm that diagnosis test works well or not for you?
I tested this from diagnostic app in settings and I could hear both speakers.
Yes, both speaker should work (assuming your volume level >0). I am afraid you must return your phone.
I would respectably disregard the previous suggestion to return your phone as this appears to be an issue with Sony's app and nothing at all to do with the stability of the hardware itself.
When I first ran the diagnostics, all tests except the proximity sensor passed; including both speaker tests. I restarted the phone, reran the test, and the proximity sensor test passed without further troubleshooting. Unfortunately this time both speaker tests decided to randomly fail? I called my voicemail and the earphone speaker worked without issue, so I then turned on the loud speaker and it also appeared to work just fine.
I did this a couple more times and got the same results so I decided to troubleshoot the issue a bit further, and what I found was that Sony's app appears to wrap around built in diagnostics commands; which are the same commands that can be accessed and/or ran via the "Service Menu". After running both speaker tests from the Service Menu, I can confirm that the "real" diagnostics commands work just fine and sounds could be heard during both tests.
Please follow the steps below and see if manually running the diagnostics commands via the "Service Menu" produces different results then those provided by the Sony Support app.
1. Turn your volume up!
2. Dial *#*#7378423#*#*
3. Select "Service tests"
4. Select "Speaker" and listen for sound
5. Select "Earphone", then place the phone to your ear and listen for sound
If steps 4 & 5 play a sound, rest assured that your hardware is functioning just fine and a replacement WILL NOT BE NEEDED. If you are still unable to hear anything then keep on reading as the solution for me was literally nothing more then changing my ringtone back to a default tone.
There was only one variable that made sense here which was that I had changed my ringtone to a custom file stored on my SD card just before restarting my phone after the first test. So instead of assuming it was hardware related, right from the start my assumption was that the Sony Support app has a bug and could not properly link to ringtones that are stored outside of the default system location. I was able to verify this by changing my ringtone back to the default tone and re-running the Sony diagnostics and confirming that both tests produced sound just fine. Now if you still cannot get sound then I would suggest contacting Sony support to inquire further. If a replacement is actually needed, they will let you know.
Now...with regards to the rushed suggestion to replace your device...I feel I must comment towards such a ridiculously rushed conclusion...
Simply put, it's not right to send people on a wild goose chase without first taking the time to test things out for yourself... even a tiny lil itsty bit? Personally, I know I'd be pissed right off if I found out that I sent in my phone without there actually being a problem with it, and whether you realized it or not,, that is actually the least of the potential consequences? You really should have considered that some people might have to pay to ship it, and others might have to drive an hour or two to get to the nearest repair centre? So maybe...just maybe...even the simplest of suggestions like "restart your phone" or "ask google!", prior to suggesting that someone should replace it, would have proven to be infinitely more useful? I hate to be rude, and I get that you were just trying to help, but if you don't want to spend any time at all to test anything out for yourself, then maybe it is best to not comment on the issue in the first place? Just simply let them wait for someone who is...
This is just my two cents, but I firmly believe that no advice is better then bad advice...
EDIT:
Model: XA2 Ultra (H3223)
Build: 50.1.A.13.83 (Stock Rom)
Sony Support Version: 4.2.10
So I found 2 other issue with Sony's diagnostics tests.
1. When you run the wifi test it will pass, but it will leave your wifi disabled afterwards and it will not allow it to be turned back on until the phone is restarted. Manual testing worked just fine.
2. When you run the ambient light test, the image provided by Sony will show, but it will already be faded while under normal light conditions. It will work while under a bright light, but it does not function correctly under normal conditions. Manual testing works just fine.
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
its nokia that pushed the update they did not make the rom right
Same here I told nokia about it and they told me to wait for a bug fix. I told them I wanted to downgrade since your firmware bug broke my phone.
Just wait for a bug fix? So use a Phone that cant make calls right?
So payed a guy to unlock my boot loader to try to flash a rom so i can just make the phone usable.
I spend about 6 hours try to get the rom to work. With little to no luck I was able to get into twrp a few times.
So ya Im in the same boat. I just got this phone back 3 weeks ago from a rma due to a bad chargeing port. Now Im forced to pay some one to unlock the boot loader and try to get a custom rom Just to be able to call
If I cant get the rom working Im going to have to go spend like $200 on a new phone today just sucks
fisterkev said:
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
Click to expand...
Click to collapse
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
gumbyx84 said:
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
Click to expand...
Click to collapse
I haven't. Just using whatever over the air OS Nokia pushes to the phone.
yes I did pay to unlock the boot loader I used linage from the rom section
it has all the bugs of the stock rom. Cant call out or with out the loud noise bug and no voip apps work
I did get the Android 9 based rom to work. it has a few bugs but its usable.
I more or less gave up im looking at a iphone now.
I spend 20 hours or more trying to get this phone to work
first the usb port goes out and I cant charge.
2 weeks after having the phone back I got a magnetic cable so the usb port would not brake any more cable. That was like $20
After 2 weeks android 10 more or less bricks the phone (a phone that cant make calls)
Then I have to spend like $15 to pay the poor guy to unlock my boot-loader (he did a great job)
I spend a lot more time loading the linage android 10 rom for it to have the same bugs ( in no way is it the devs fault im sure he did not know).
... can unlock your bootloader for a small fee.
I would say all android 10 based rom will have those kind of problems. I can only confirm it on the android 10 linage one
When I flash twrp most of the time the twrp would just freeze if booting form the phone.
I had no problem loading it with fastboot works evey time. So I would only use it install the rom and just boot it when you need it. I would not suggesting flashing it to recovery as it only worked some of the time for me.
Hope all that info helps
QUOTE=gumbyx84;81261583]Have you guys modified the phone in any way like unlocking the bootloader or rooting?[/QUOTE]
---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------
The calling problem goes in and out. Some times it works some times it dose not. Facebook message outgoing calls the mic will not work, Same with google voice.
if i make calls with out google voice it works 1/2 the time. all the people have the same problem
https://community.phones.nokia.com/discussion/54374/android-10-after-update-on-nokia-7-1
diggeryo said:
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Click to expand...
Click to collapse
How to fix the phone call problems
To everyone having calling issues (distortion / squealing, or other people can't hear them), try this: Turn off Voice over LTE. You go to Settings -> Wireless and Networks -> Mobile Networks -> VoLTE, and turn that setting off. This fixed the problem for all 3 Nokia 7.1 phones in our family, when nothing else seemed to work.
Turning off VoLTE and wifi calling works, but VoLTE is important in my area with TMobile. Without it, too many dropped and missed calls. I actually downgraded from an Xperia XZ1 just to get VoLTE, now this happens.
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
Click to expand...
Click to collapse
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Thank you so much for sharing! Works like a charm
Unfortunately denying microphone for the Google app did not work for me. I also noticed no one can hear me when making videos calls (Hangouts, Duo, Facebook messenger).
I then decided to factory reset, but did not help. Both VoLTE and video calling still not working.
Anyone else with video calling mic issues?
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
Click to expand...
Click to collapse
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Confirm this recipe works for my TA-1085. Thanks much.
I solved my random voice problems (others can't hear me on Duo video call, duplex voice on the other side etc.) with the voice match assistant workaround until hopefully gets fixed in a next update. Don't know for sure if the thing is only on Nokia's side or Google app's as well on Android 10, since disabling Hey Google solves all issues
Will have to try/catch on future google app updates as well to find out
Sly_North said:
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
Click to expand...
Click to collapse
Under "Voice Match" I don't see any "Access With Voice Match" setting. What I do see is "Hey Google," which says "Access your Assistant any time you say "Hey Google" when your screen is on." Perhaps this is what your mean?
I tried this solution and it works, too. I think it also has the advantage of not completely shutting down Assistant's access to the microphone. Just waking up Assistant by voice. Much less of a price. Thanks!
Has anyone heard anything about a real fix for this issue? I've gotten two Android updates since the upgrade to Android 10, but this issue has not been fixed yet.
After extensive talks and inside info on Nokia's community forums, seems like a Maintenance update (MR) is on the way for May, which they say fixes -among others- both voice bugs. That is, the echo on calls plus sound distortion in some games (e..g Monument Valley 2 for me)
Cross your fingers everyone for a quick release and confirmation of the fixes!
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
dbal said:
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
Click to expand...
Click to collapse
Yes, they seem to have fixed the voice call problems with Whatapp, Wechat, Hangouts and etc since the Android 10 update.