Hi,
I just bought a used H8314 XZ2 Compact.
During call I have no sound if I press the speaker button (on Android 10 and Los 19).
What I did before I noticed the problem : phone was on stock. Unlock the bootloader, install Lineageos 19. Used the phone; during call speaker not working.
Downgrade to Android 10 stock, the speaker still not work...
If I do the Microphone and speakers Xperia Tests, I can ear the sound coming from loudspeaker but the test failed for the microphone. But microphone is working...
Could anybody tell me please if it's a hardware issue ?
EDIT : I just did a test with music. Sound is just coming out from the top speaker, nothing from the bottom speaker. With my other XZ2C sound is coming out from both speakers.
I've contact the vendor, of course, this never happened before.
Is it possible that unlocking the bootloader and installing Lineageos 19 can broke the the bottom speaker ?
Related
Call volume is hearable only though Rear Speaker and Headset only.
Is there any fix or workaround is available to force Audio to the front Earpiece,
Currently Using CM14.1 on My Xperia M dual
Hi Guys.
Here is my system
Moto Z2 Force XT-1789-06
Reteu
Oreo 8.0
TWRP 3.2.3-1
Magisk V.17
My problem
After the phone is no longer sound. You just hear something quietly from the speaker. You can increase the volume but it does not get louder. If I now dial a number again and hang up immediately, the sound is back to normal.
So it is also who I connect the moto mod of JBL. After connecting you will hear the sound again from the phone speaker and when I dial a number again and immediately hang up the sound from the JBL Moto Mod
Does one have an idea what that can be and possibly a solution?
Many Thanks
Translate with Google
Have a something similar problem. If I hear music over bluetooth the sounds a little bit volume down when I go to some websites, not all. Maybe there are few bugs, oreo came very fast in december. I think we should wait until we can get the Pie-Update very soon. There are all perfect then. Maybe we will by the first people who get it, because the Z3 has SD835 and gets first as flaggship and so the next moto flaggship and most expensive device is the Z2 Force with 799€. So maybe in 2 or 3 months. We don't got 8.1, so we will be at least by the first people who get 9.0. Maybe then battery status of bluetooth sound device is then readable. This feature is roll out with 8.1, what we are missing. Very sad.
After I updated to Android 10, a few of my friends on Discord said that they can barely hear me. I made sure my mic was as sensitive as possible in Discord and I barely saw the audio meter go up. Used an app to record my voice and noticed how quiet it is. I've tested this on both PixelDust and stock, and the microphone problem was still there. I downgraded to Pie for a bit and noticed that my mic was normal again, but when I updated back to 10, my mic was insanely quiet again. Is there any way to change your microphone volume in Android?
I can't say about Discord but make sure you have not fallen victim to the infamous microphone issue which plagued the OG Pixels widely, myself included.
It seems that Android 10 is forcing my mic to use the earpiece mic instead of the speaker mic in every app by default now.
Edit: After further testing, plugging in any headset won't change the mic input either. It's stuck on the earpiece mic.
Hello, i use a Xperia Z1 compact on stock 5.1.1 - 14.6.A.1.236
root with super su 2.82 / xposed framwork 89
Got a problem since more than one year with calling signal transmitting quality when using my loudspeaker.
It appears that all my contacts ear disgracious sounds and other reverbs of their voices when loudspeaker is active during calls.
I have no sound mods. And i have switch off all sony sounds mods in setting.
And every sounds are good for me, loudspeaker sound is ok , and all test are good is sony testing mode (speakers and mics work well)
Any idea? i don't want to clean flash and reinstall because i'm not sure that it will solve my problem.
Thanks.
Hi everybody,
I recently bought an used phone in Spain. The phone arrived with android 9 (I don't remember exactly which version) and I checked all the functions with the service menu. The only thing that worked badly was the secondary microphone, which had a recording volume extremely low. I thought it could be fine anyway. So I updated the phone OTA, then I did a companion restore (to 52.1.A.0.618). At that point I put the sim, and made the first whatsapp call. Everything was fine at the beginning but at the end of the call, the speaker started croaking (badly). From the service test I identified the bottom speaker (the one called right) as the malfunctioned one. So, thinking it was the fault of the update I downgraded to Android 9, following the guide on that forum, but it didn't work. Then I updated again with flashtool to Android 10, first with the Italian firmware (to 52.1.A.0.672), then with the Iberian firmware (to 52.1.A.0.618). But in both cases even the microphone no longer works correctly. If I record video, the microphone works fine, while if I make calls, the microphone works only if I put it on loud speaker. In the normal mode the interlocutor hears me but at a very low volume. Same problem from the service test. The microphone works, but only if I speak attached to the microphone hole. I tried to clean with a toothbrush, but problem still there. The phone has no cover.
Any one faced similar problems?
Fixed by replacing them. Now facing touch screen issue (updated to 52.1.A.0.672)
Hi,
I bought an XZ2 Compact recently and downloaded every updates. The last one is the 52.1.A.3.49 and I have the problem with the microphone : working for recordings or calls on loud speaker but not working for calls without the loud speaker.
What can I do ?
bracci47 said:
Fixed by replacing them. Now facing touch screen issue (updated to 52.1.A.0.672)
Click to expand...
Click to collapse
I have very similar problems with a used phone that I bought (secondary microphone very low volume). Am I reading you correctly, that you installed a new microphone and this fixed the issue?