Call issue - Xperia Z Q&A, Help & Troubleshooting

I've got a problem with calls. On stock ROMs and Paranoid Android, with every kerenels.
Sometimes I can't hear the person with who I'm talking but only on "normal mode". When I activate loudspeaker or plug in headphones I can hear without problems but after deactivating or plugging out the problem comes back and I can't hear anything. This occurs not always but very often.
Can someone helps?

I had this issue you may want to check with other people around here who are running cyanogenmod as far as I know mine was spoiled so I had to change it no idea if it was cause by cyanogenmod highly doubt it

I have the same issue! I actually had it when I was running OEM software, before rooting I sent it in to sony with the complaint 3 times. Each time they returned it with simply a software update applied.
I find if you cover and uncover the light sensor a couple of times it tends to fix itself, but its frustrating!

Yes, very frustrating! But this must be a software defect.
Maybe someone could make a fix...

Any help?

I highly doubt that it is a software defect issue but if it is a really software defect issue causing the ear speaker to fail then sony has some explaining to do nevertheless some of them reported the same issue with cyanogenmod 11.0 so honestly I dont know what is causing this but overall it seems like quite a big issue..
http://talk.sonymobile.com/t5/Xperi...e-can-t-hear-me-with-my-xperia-zl/td-p/758763
did you amplify the speaker or did anything to it, in the past etc ? like fauxsound
if you never did did you remain on stock kernel with cm11 all the way

Yes. I used some mods like pxa, but without any mods and with the problem exists

kael2404 said:
Yes. I used some mods like pxa, but without any mods and with the problem exists
Click to expand...
Click to collapse
then your hardware is damage sent it to the service centre

But it exists only sometimes and mostly with weak range

kael2404 said:
But it exists only sometimes and mostly with weak range
Click to expand...
Click to collapse
yeah it is damaged how long did you have your xperia z cause I had mine for 1 year 3 months before it died today it works fine.

huh? so what is causing this? sound-mods or just bad luck? had my xperia z 1 year 4 months and so far its ok... (*touch wood*) will be gutted if it dies...

must be sound mod blow out the speaker o.o no idea but I got mine fully replaced.

I had the same Problem. After installing Sound About from playstore and disabled headphone detection the Problem is gone

haha it isn't the old 'dust in the headphone socket' problem is it?

Related

[Q] That screen...

I've scoured the internet in attempt to resolve this issue, and I know it's been talked about many a time before, but this just doesn't have an answer yet afaik.
Does anybody have any experience with fixing the inaccuracy of the touch screen after prolonged use? I love the nexus one, it's by far the best phone I've owned; but this little bug makes the phone completely unrealistic in real-world use.
If this isn't a software issue, it has to be something with the digitizer being powered off and back on to remove the accuracy bug. In that case, is there any low-level way to turn the digitizer off and back on as fast as possible every X seconds? That would mean losing touch capability for a few milliseconds, but is much better than locking and unlocking the phone each time it "goes wild."
I had given up all hope that this issue could be resolved in any fashion as dodgy hardware is, well...dodgy. Nothing can be done about it right?
I haven't had a screen wonk since starting in on the CM7 nightlies many moons ago!
IN YOUR FACE WONK!
Is there an FAQ about this digitizer issue?
JoeSchmoe007 said:
Is there an FAQ about this digitizer issue?
Click to expand...
Click to collapse
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
DirkGently1 said:
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
Click to expand...
Click to collapse
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Hollow.Droid said:
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Click to expand...
Click to collapse
When accuracy goes berserk - does powering phone off/on help?
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Well, the touchscreen issue is nothing more than a bad digitizer that was released with the phone and never improved during manufacture of the device. All Nexii have the same one, although people suffered the problem in varying degrees. What would happen is every so often your touch on the screen would register in the wrong place so you may be selecting a shortcut on your homescreen to launch an app, but it might register the touch as being an inch higher/lower/somewhere random. the solution has always been to simply press the power button to turn the screen off/on again. This would fix the issue... until it occurred again.
The call wonk is really in two parts. Stock GB ROMs had a habit of introducing a slight delay in one party being able to hear the other during the start of a call. On CM7 ROMs it was a more significant issue of black screens and freezes during the start of a call. These didn't affect affect everyone though, and even Cyanogen himself didn't have it on on his own device.
EDIT: The other issue affecting the N1 was a weak, and often failing, power button. With the need to keep using it to fix the screen wonk the problem was made worse. That's why you might often see mentions of Trackball wake as it reduced the need to use the power button, therefore extending it's life. Trackball wake is only available on custom ROMs so bear that in mind too!
The phone isn't perfect but with the custom ROM devs doing there thing it's pretty decent for me
Hollow.Droid and DirkGently1 - I appreciate your responses.
Can I bring your attention to my other question to which nobody responded yet?
http://forum.xda-developers.com/showthread.php?t=1077733
JoeSchmoe007 said:
When accuracy goes berserk - does powering phone off/on help?
Click to expand...
Click to collapse
When the issue happens you just lock and unlock the screen to fix it. No need for a reboot.
This issue isn't really such a big deal. It happens once a week or so, and it takes a few seconds to black out the screen then unlock, problem gone.

Low mic volume on speakerphone

When i activate speakerphone during a Call suddenly the mic volume drops dramatically, other persons could barely hear me.
Do you guys suffer similar conditions ?... I am not sure to return it or not, as the mic work perfectly if speaker is not activated.
Created this thread just to find out how many Note owners are having similar issues..If this is a software issue everyone of us on latest firmware should be having this issue. Otherwise I might need to send it to repair center..
_K****ij said:
When i activate speakerphone during a Call suddenly the mic volume drops dramatically, other persons could barely hear me.
Do you guys suffer similar conditions ?... I am not sure to return it or not, as the mic work perfectly if speaker is not activated.
Created this thread just to find out how many Note owners are having similar issues..If this is a software issue everyone of us on latest firmware should be having this issue. Otherwise I might need to send it to repair center..
Click to expand...
Click to collapse
yes I do. it wasn't like that when I bought the phone so I suspect the ICS update has broken it.
bashville said:
yes I do. it wasn't like that when I bought the phone so I suspect the ICS update has broken it.
Click to expand...
Click to collapse
Are you on latest firmware? I didn't had this since I updated to latest one. Running stock 4.0.4 ICS right now.
_K****ij said:
Are you on latest firmware? I didn't had this since I updated to latest one. Running stock 4.0.4 ICS right now.
Click to expand...
Click to collapse
I've updated to 4.0.4 (stock over the air update) and I still have the issue. I read somewhere that the galaxy note has 2 mics one at the bottom which is used when in normal phone mode and one at the top which is used when in speakerphone mode. I think the one at the top is faulty (given there are not many search hits for it on google I'd guess the problem is hardware and not firmware related).

[Q] people complain they cant hear me

Hi i'm using a rooted htc one and people often complain they cant hear me during calls. I was wondering if there was anyway I could enhance the microphone so that my voice is louder. I'm using android 4.1.2 and sense 5. The case i'm using has a hole on the back in the top right corner and on the bottom to the left of the usb adapter jack where I think the microphone(s) are. I looked at other threads but I was having this problem before I rooted my htc one and was hoping that now it has been rooted there was some sort of hiden control I can use to turn up the michrophone setting. Thanks
bump
If it wasn't working right before you rooted it, then it means it is a hardware problem. I don't think this is necessarily a sensitivity issue. I think it has to do with the noise canceling.
Talk to HTC or whatever carrier you have.
Also, make sure to hide all signs of root!
Hej layzz, there is a thread with a similar problem: http://forum.xda-developers.com/showthread.php?t=2380867
Just as I mentioned there, it could be the hole at the underside of your case being just way to small, or (as I realized just recently) a very special hardware problem (so to say). During calls I had always covered the mic with my little finger, no wonder no one understood me.
Give it a shot
Xayden said:
Hej layzz, there is a thread with a similar problem: http://forum.xda-developers.com/showthread.php?t=2380867
Just as I mentioned there, it could be the hole at the underside of your case being just way to small, or (as I realized just recently) a very special hardware problem (so to say). During calls I had always covered the mic with my little finger, no wonder no one understood me.
Give it a shot
Click to expand...
Click to collapse
i had a similar problem too, i upgraded to 4.2.2 on 2.24 (ARHD) and now its fixed.
the proximity sensor is also fixed
Muhammad.Muayad said:
i had a similar problem too, i upgraded to 4.2.2 on 2.24 (ARHD) and now its fixed.
the proximity sensor is also fixed
Click to expand...
Click to collapse
The mic hole at the bottom of the device is clearly visible. Would you mind posting a link to that rom please?
layzz said:
The mic hole at the bottom of the device is clearly visible. Would you mind posting a link to that rom please?
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2183023
This ROM is based on 4.2.2 on 2.24 all my problems are pretty much fixed
I have this very same problem on my brand new stock device. I created a thread for the same problem. I found that the earpiece quality was brilliant but again people could not hear me or said I was very quite. I experimented with case on and case of and calls to different phones and 9/10 times the problem was there. I then decided to install android revolution hd to see if there was a problem with the stock rim for some reason. Sadly this didn't work. I then turned my attention to the lower microphone. Now I am not suggestion you do this by any means however in my case I felt I had nothing to lose as I was going to have to send the phone to HTC to get fixed if I could not sort it myself.
I got the small sim removal tool and stuck it into the mic hole in a bid to try and open the hole up abit as it seemed very small and I wondered also if it was blocked. I did this a little at a time and then tried calling people to see if there was any change. Instantly there was an improvement. However, now it seemed like 5\10 calls were low. So, I tried the same again.
I now have not had the problem in the last 15 or so calls I have made however what I have noticed is that now for what ever reason when I'm in calls the person on the other end sounds a little distorted through the earpiece. Don't know why this should be and maybe a completely unrelated problem or something linked to installing the other rom. Either way at least people can hear me now.
Sent from my HTC One using xda premium
Thanks everyone. The problem seems to be fixed after installing that custom rom

Bluetooth audio streaming issue with CM roms

Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
konaman said:
Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
Click to expand...
Click to collapse
Well... if you're playing with CM, you're bound to get burned. There are a couple of reasons;
1) Everybody (and I mean *everybody*) throws stuff at the CM gerrit server (sometimes, even for comedy/trolling purposes), these bits being thrown at it are mostly independent and generally NOT tested in conjunction with all the other bits that get thrown at it. So what happens, is one of the maintainers sees a commit they like and adds it, sometimes not realizing the consequences of it, and major breakage happens.
2) Sometimes in the aforementioned situation, minor breakage happens, and it can persist for months, or even forever.
3) CM12 is very young, with lots of changes still flying. It is by no means stable, or even settled.
4) The CM definition of "stable" is that which nobody bothers working on any more. I.e., everybody right now is interested in Android 5.0, so 4.4 is not getting much attention... it is "stable" -- despite being horribly broken in many many ways.
If it works well with the factory system image, then you pretty much have the answer... it is a defect that has been introduced to CM. I think that CM has their own bug tracker that you can use, but I'm not sure if they have even opened it up to receive reports against 5.0 yet.
BTW: Sweet truck eh? I have a 2011. Pay some attention to the front cab mounts. If you look up into the cab mounts with a flashlight, you will notice that at the back where they are welded onto the main frame rails, there is a huge opening to the inside of the boxed section. When you drive through salty road slime in the winter, all that salt crap that flies off the front wheels gets sprayed up and into the INSIDE of the boxed section of the frame. Get a tube of roof repair tar from HD, and a couple of old CD's. Cut the CD's down to a diameter of 3.5 inch. Stick the cut down CD's up into the opening of the cab mounts and tar them in really well. While you are at it with the tar, plug up all the other holes into the frame around the front wheels (you may need some plastic plugs for this). That will keep the road sludge out of the frame, so it won't rust from the inside out.
I am running LiquidSmooth/franco kernel. I am running the 1/19 build because it was the last with the nice Dark UI and have no problems with Bluetooth in my Prius. I mainly use Pandora.
@ doitright
Thanks for the reply. I have a better understanding about cm roms from it and I have been searching this issue all over. It is definitely a cm problem.
As for my truck, yeah I love it. I have the double cab TRD off road 4x4 model. When the weather clears/warms up I will check the areas you mentioned. I know the history on Toyota frames all too well.
@ prod
I had the same issue with that rom as well.
Are you still having issues with this on nexus 6? I am on s5 and willing to buy a nexus 6 to fix it but i'm starting to wonder if it will matter.
konaman said:
Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
Click to expand...
Click to collapse
jd603 said:
Are you still having issues with this on nexus 6? I am on s5 and willing to buy a nexus 6 to fix it but i'm starting to wonder if it will matter.
Click to expand...
Click to collapse
I had constant problems with this phone. I am not new to flashing roms or modding phone by any means but this phone had me beat. CM roms had the Bluetooth issue and I never got it fixed. Normal roms worked pretty good but the phone was still buggy.
I got so sick of it that I sold it. Though it has been a few months ago, maybe they got the bugs worked out, idk. I couldn't take it anymore.
I went got a 128gb iPhone 6 plus now and have never been happier. I haven't had an iPhone since the 4 and I forgot how flawless they operate out of the box.

Speaker crackle/distortion is it hardware och software related?

Hi!
Seen many others facing the issue with speakers crackling/get distorted att hight volumes on notifications/ringtones. For example alarm sound named Oxygen sounds distorted on higher volume and also the ringtone Ganymede. But youtube and such sounds like they should even att highest volume. Is this on all phones? Is it software or hardware related? Absolutley loving the phone but if my speakers are broke I need to try and get a replacement.
Can anyone confirm that they have no distortion/crackle at all?
Br J
Jaxione said:
Hi!
Seen many others facing the issue with speakers crackling/get distorted att hight volumes on notifications/ringtones. For example alarm sound named Oxygen sounds distorted on higher volume and also the ringtone Ganymede. But youtube and such sounds like they should even att highest volume. Is this on all phones? Is it software or hardware related? Absolutley loving the phone but if my speakers are broke I need to try and get a replacement.
Can anyone confirm that they have no distortion/crackle at all?
Br J
Click to expand...
Click to collapse
No problem for me here, not even on the highest volume level. If some users have this issue its probably a hardware faillure rather then software.
Jaxione said:
Hi!
Seen many others facing the issue with speakers crackling/get distorted att hight volumes on notifications/ringtones. For example alarm sound named Oxygen sounds distorted on higher volume and also the ringtone Ganymede. But youtube and such sounds like they should even att highest volume. Is this on all phones? Is it software or hardware related? Absolutley loving the phone but if my speakers are broke I need to try and get a replacement.
Can anyone confirm that they have no distortion/crackle at all?
Br J
Click to expand...
Click to collapse
Some devices are facing this issue. If it's only happening on highest volume then it's a software issue or else it's a hardware issue
SAW_JOK3R said:
Some devices are facing this issue. If it's only happening on highest volume then it's a software issue or else it's a hardware issue
Click to expand...
Click to collapse
If it is a software issue, how come only some devices have it and not all?
Br J
Jaxione said:
If it is a software issue, how come only some devices have it and not all?
Br J
Click to expand...
Click to collapse
I've no proper explanation to give But same happening with force shutdown / random force reboot issue. It's affecting Many users but not All
SAW_JOK3R said:
I've no proper explanation to give But same happening with force shutdown / random force reboot issue. It's affecting Many users but not All
Click to expand...
Click to collapse
This sucks How could they solve software issues that is only affecting some phones? If I send mine back It will take 2-3 weeks for it to come back. And I think the company that I bought it from will just scratch their heads and find no problem with the phone. I from sweden and Motorola isnt represented here so I have to go through the company I bought it from sucks. Will never buy from them again.
Br J
Jaxione said:
This sucks How could they solve software issues that is only affecting some phones? If I send mine back It will take 2-3 weeks for it to come back. And I think the company that I bought it from will just scratch their heads and find no problem with the phone. I from sweden and Motorola isnt represented here so I have to go through the company I bought it from sucks. Will never buy from them again.
Br J
Click to expand...
Click to collapse
It's not their fault. It's Google's fault. Go to this Google Forum Topic and go to first page. You can see it's marked as complete by a google employee. Fix will come with the new update
SAW_JOK3R said:
It's not their fault. It's Google's fault. Go to this Google Forum Topic and go to first page. You can see it's marked as complete by a google employee. Fix will come with the new update
Click to expand...
Click to collapse
Read throught the thread. The only thing google are saying is that the cant reproduce the problem. Can read anywhere that they will fix it.
Mvh J
Jaxione said:
Read throught the thread. The only thing google are saying is that the cant reproduce the problem. Can read anywhere that they will fix it.
Mvh J
Click to expand...
Click to collapse
They can only fix it by update
SAW_JOK3R said:
They can only fix it by update
Click to expand...
Click to collapse
If you read through that thread you will se that it was set to completed because of that the google employee couldnt reproduce the problem and therefor asks people to ask for a replacement phone. So I dont think they marked this thread Completed because it will be solved in an update.
Br J
Jaxione said:
If you read through that thread you will se that it was set to completed because of that the google employee couldnt reproduce the problem and therefor asks people to ask for a replacement phone. So I dont think they marked this thread Completed because it will be solved in an update.
Br J
Click to expand...
Click to collapse
Yeah, I know. That's why said. As it's marked as completed, that means the support team of the forum was not able to solve the issue so they've forwarded the issue to Google devs to solve it
SAW_JOK3R said:
Yeah, I know. That's why said. As it's marked as completed, that means the support team of the forum was not able to solve the issue so they've forwarded the issue to Google devs to solve it
Click to expand...
Click to collapse
Lets hope they do. It must be software related in my case. Noticed a thing when testing a bit today. When I hold my phone normally the "crackle" / "bad sound" comes from the top speaker and the bottom one sounds fine but if I turn the phone to landscape mode the crackle jumps down to the bottom speaker and the top speaker sounds fine. Reaaally strange
Br J
Jaxione said:
Lets hope they do. It must be software related in my case. Noticed a thing when testing a bit today. When I hold my phone normally the "crackle" / "bad sound" comes from the top speaker and the bottom one sounds fine but if I turn the phone to landscape mode the crackle jumps down to the bottom speaker and the top speaker sounds fine. Reaaally strange
Br J
Click to expand...
Click to collapse
The crackle problem does the same on me ,except the landscape experiment which I haven't done .But if it really occurs just as you explain ,than it is most probably (or it looks like) software related issue. Anyway it indeed seems strange :|
I just enabled encryption and regarding cracks and rispy sound it seems better.
Maybe someone else who have this issue can test?
I definitely have this issue. On latest M firmware on Sprint variant. I manually flashed firmware.. Saw somewhere else on here where someone solved problem by installing viper audio and setting to super hi quality sound.. May try that. Seems like I recall on og Nexus 7 some kernels would cause the device to get too hot (like the charger that came with phone does for me..) And speakers would get messed up as a result and distort. Hope that's not the case here. :banghead:
Its most likely software. It almost sounds the same as the speaker distortion that the one m8 had when running cm due to the lack of proper audio drivers. Its most likely a driver issue which is why some have had success with viper. For now I would not max out volume when using the phone just to protect the speakers and we will just have to wait and see if google releases a fix.
toknitup420 said:
Its most likely software. It almost sounds the same as the speaker distortion that the one m8 had when running cm due to the lack of proper audio drivers. Its most likely a driver issue which is why some have had success with viper. For now I would not max out volume when using the phone just to protect the speakers and we will just have to wait and see if google releases a fix.
Click to expand...
Click to collapse
I sure hope that you and others who've said same are correct. If that is the case Google needs to get with it and push an image that fixes it asap.
Update: (Sprint N6-latest firmware-M..) I installed Dirty Unicorn test build 5.1 dated 3/29 from their G+ community and not one crackle comes out even on the highest volume my device is fine. Was not like that on stock Google rom.. I was getting a feedback sound coming from exterior speakers as well and its not present anymore. Just wanted to share that.

Categories

Resources