Related
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
hmmm
carlosmeldano said:
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
Click to expand...
Click to collapse
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
really?
madhukarmohan said:
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
Click to expand...
Click to collapse
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
yes
carlosmeldano said:
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
Click to expand...
Click to collapse
Yeah, few r experiencing that. i hv seen complaints in sony blog and here too. I asked this question few days back. but, I didnt get reply.
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
thx
UltraWelfare said:
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
Click to expand...
Click to collapse
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
carlosmeldano said:
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
Click to expand...
Click to collapse
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
UltraWelfare said:
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
Click to expand...
Click to collapse
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
carlosmeldano said:
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
Click to expand...
Click to collapse
I hope everything goes fine
no success
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
carlosmeldano said:
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
Click to expand...
Click to collapse
Bring it to a sony service(or how's it called to your country)
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
carlosmeldano said:
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services are just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
Click to expand...
Click to collapse
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
UltraWelfare said:
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
Click to expand...
Click to collapse
yes, that's another option. the other option is to cry off from purchase (I can do it within a week), they return the money, and I buy another one. I'll see as this is not that disturbing problem and I have no other problems with the phone like wifi bug or anything else.
someone said it's a bug so I hope 4.3 next month will solve it.
Background info: I've had my Xperia Z1 only for two to three weeks now. I've been enjoying every part of it, but I've come across three particular gripes I have to mention.
First, random app crashes. One time the Album crashes, the other time System crashed. It appears to be random, not based on anything you were or weren't doing at that moment. I don't think I'm the only one with this though.
Secondly, and here's where it gets weird: my on-screen buttons disappeared. I believe I was just closing GTA: San Andreas. Suddenly, the buttons were gone. I could scroll through the app drawer perfectly, still. That's the odd thing. I should've taken a screenshot if I realised this earlier. I will next time it happens, so let's hope I don't have to. After a while, the phone froze and I decided to reset it, after which everything returned to normal. I guess that's one part where hardware buttons beat software - they don't magically disappear (I hope..).
Lastly, I opened the camera and it looked like it lagged. I pressed the Home button twice or thrice, but then the entire device froze and it kept vibrating like hell! I don't particularly enjoy 5" vibrating devices so I decided to reset it as quickly as possible. No way that could've been good for the device.
Have you experienced one of the last two issues I've had? Or have you had something similar yet different?
Let me know below!
i
Hermantje said:
Background info: I've had my Xperia Z1 only for two to three weeks now. I've been enjoying every part of it, but I've come across three particular gripes I have to mention.
First, random app crashes. One time the Album crashes, the other time System crashed. It appears to be random, not based on anything you were or weren't doing at that moment. I don't think I'm the only one with this though.
Secondly, and here's where it gets weird: my on-screen buttons disappeared. I believe I was just closing GTA: San Andreas. Suddenly, the buttons were gone. I could scroll through the app drawer perfectly, still. That's the odd thing. I should've taken a screenshot if I realised this earlier. I will next time it happens, so let's hope I don't have to. After a while, the phone froze and I decided to reset it, after which everything returned to normal. I guess that's one part where hardware buttons beat software - they don't magically disappear (I hope..).
Lastly, I opened the camera and it looked like it lagged. I pressed the Home button twice or thrice, but then the entire device froze and it kept vibrating like hell! I don't particularly enjoy 5" vibrating devices so I decided to reset it as quickly as possible. No way that could've been good for the device.
Have you experienced one of the last two issues I've had? Or have you had something similar yet different?
Let me know below!
Click to expand...
Click to collapse
these are not important problem
>> repair ur phone firmware by PCcompanion
:good:
x102x96x said:
these are not important problem
>> repair ur phone firmware by PCcompanion
:good:
Click to expand...
Click to collapse
I'm sorry, what?
It's pretty important to not lose the three main on-screen buttons, not to mention having a device that doesn't vibrate like you-know-what.
What would repairing the firmware do? The phone is still new. There couldn't be anything wrong with the firmware, not solvable by flashing the same firmware over it again, I reckon.
x102x96x said:
these are not important problem
>> repair ur phone firmware by PCcompanion
:good:
Click to expand...
Click to collapse
That's not an answer, even a solution tho. Please be friendly, respect the other.
Sent from my C6903 using Tapatalk
i
Hermantje said:
I'm sorry, what?
It's pretty important to not lose the three main on-screen buttons, not to mention having a device that doesn't vibrate like you-know-what.
What would repairing the firmware do? The phone is still new. There couldn't be anything wrong with the firmware, not solvable by flashing the same firmware over it again, I reckon.
Click to expand...
Click to collapse
yeah these are problems and easily can be solved
by PC companion.
even more issue can appear on new phone.
these are bugs on ur ROM
when u repair firmware, PC companion will download latest firmware (available for ur region) and install it on ur phone.
That can solve ur problem.
-
if repairing by PCC didn't help u should download Flash-Tool for Xperia & firmware of another region and flash it.
u can find useful information about it here.
Source
:good:
omegahanggara said:
That's not an answer, even a solution tho. Please be friendly, respect the other.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Try repair is really the first thing to do with ROM dependent error, so there is nothing wrong with the answer.
harfot said:
Try repair is really the first thing to do with ROM dependent error, so there is nothing wrong with the answer.
Click to expand...
Click to collapse
How can this be a ROM dependent error when I just had my Xperia Z1 for a couple of weeks and updated to official Android 4.3 Jelly Bean through an Over The Air update? My Android firmware is as official and up-to-date as it gets right now.
EDIT: Actually, I wasn't even asking for a solution. I was purely wondering if anyone else had these specific issues as well.
Hermantje said:
How can this be a ROM dependent error when I just had my Xperia Z1 for a couple of weeks and updated to official Android 4.3 Jelly Bean through an Over The Air update? My Android firmware is as official and up-to-date as it gets right now.
EDIT: Actually, I wasn't even asking for a solution. I was purely wondering if anyone else had these specific issues as well.
Click to expand...
Click to collapse
Because any update (especially an OTA) might fail and because these errors (mentioned, i think, for the first time here) are ROM dependent.
So first thing I would do is trying the repair.
I'm aware that you only asked for similarities, but as the are annoying errors, we just wanted to help with a possible solution.
Are you running a 4.3 stock ROM?
Do you use bluetooth/have it turned on?
If yes to both, it is a bug in the 4.3 roms related to bluetooth. Only solution I am aware of is to restart the phone whenever it happens and if you can leave bluetooth off
footyfanatic said:
Are you running a 4.3 stock ROM?
Do you use bluetooth/have it turned on?
If yes to both, it is a bug in the 4.3 roms related to bluetooth. Only solution I am aware of is to restart the phone whenever it happens and if you can leave bluetooth off
Click to expand...
Click to collapse
Yes & no.
I never use bluetooth actually.
Hello!
Wifi and Bluetooth aren't working anymore When you try turning them on, them just turn off immediately. It has been going on after KitKat 4.4.3 update.
It's the same situation this member described in this thread: >>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-bluetooth-issues-t2808419<<<<
He also uploaded a video about this issue: >>>>youtube . com / watch? v = girqFv6eWnQ<<<<
I also have been reading this threads:
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479<<<<
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308<<<<
and the solution for this would be replace the WCNSS_qcom_wlan_nv.bin in the Persist folder. As my phone is not rooted, it seens impossible I had accidently deleted this file, right? Anyway, the Persist folder of my phone is empty. It's because my phone is not rooted so it doesn't show the files inside the folder? At the wlan/prima, there are the following files:
WCNSS_cfg.dat
WCNSS_qcom_cfg.ini
WCNSS_qcom_wlan_nv.bin (that's the file, right?)
WCNSS_qcom_wlan_nv_calibration.bin
WCNSS_qcom_wlan_nv_regulatory.bin
Is there some possible solution or I really need to send my phone to technical support?
I'm sorry about my English and my poor knowlegde. Thank's a lot!
rafaelrossignoli said:
Hello!
Wifi and Bluetooth aren't working anymore When you try turning them on, them just turn off immediately. It has been going on after KitKat 4.4.3 update.
It's the same situation this member described in this thread: >>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-bluetooth-issues-t2808419<<<<
He also uploaded a video about this issue: >>>>youtube . com / watch? v = girqFv6eWnQ<<<<
I also have been reading this threads:
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479<<<<
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308<<<<
and the solution for this would be replace the WCNSS_qcom_wlan_nv.bin in the Persist folder. As my phone is not rooted, it seens impossible I had accidently deleted this file, right? Anyway, the Persist folder of my phone is empty. It's because my phone is not rooted so it doesn't show the files inside the folder? At the wlan/prima, there are the following files:
WCNSS_cfg.dat
WCNSS_qcom_cfg.ini
WCNSS_qcom_wlan_nv.bin (that's the file, right?)
WCNSS_qcom_wlan_nv_calibration.bin
WCNSS_qcom_wlan_nv_regulatory.bin
Is there some possible solution or I really need to send my phone to technical support?
I'm sorry about my English and my poor knowlegde. Thank's a lot!
Click to expand...
Click to collapse
There is no way to prove that persist is vacant as you are unrooted. It is most likely a coinsident hardware failure. But still possible.
Go warranty replacement. Rsd restore is no help as persist is not in the XML.
aviwdoowks said:
There is no way to prove that persist is vacant as you are unrooted. It is most likely a coinsident hardware failure. But still possible.
Go warranty replacement. Rsd restore is no help as persist is not in the XML.
Click to expand...
Click to collapse
For first, thank you for your concern.
I see. It's a poor situation we have been seeing with others Moto X owners, especially after 4.4.3 update. Considering it's not a hardware issue and 4.4.4 update release (my phone is still in 4.4.3), is the 4.4.4 update worth it? I have been reading about increasing battery consumption after 4.4.4 update. I also have read about restoring the stock rom could be a worth try, even if your phone has never been rooted. What you say?
rafaelrossignoli said:
For first, thank you for your concern.
I see. It's a poor situation we have been seeing with others Moto X owners, especially after 4.4.3 update. Considering it's not a hardware issue and 4.4.4 update release (my phone is still in 4.4.3), is the 4.4.4 update worth it? I have been reading about increasing battery consumption after 4.4.4 update. I also have read about restoring the stock rom could be a worth try, even if your phone has never been rooted. What you say?
Click to expand...
Click to collapse
I have a Maxx now on 444, not rooted & 444 is fine. There is much feedback on x 444 around.
aviwdoowks said:
I have a Maxx now on 444, not rooted & 444 is fine. There is much feedback on x 444 around.
Click to expand...
Click to collapse
So I will try to update it on 4.4.4. A last question I forgot asking: my 3/4G is working fine. 3/4G has nothing to do with wifi/bluetooth hardware/software, right?
rafaelrossignoli said:
So I will try to update it on 4.4.4. A last question I forgot asking: my 3/4G is working fine. 3/4G has nothing to do with wifi/bluetooth hardware/software, right?
Click to expand...
Click to collapse
Correct.
I've sent my phone warranty. I'm a previous contact they told me it's probably a hardware issue. The battery comsumption has increased a lot and the explanation is that phone is constantly searching for wifi/bluetooth. Is it possible even with hardware failure?
When I get my phone back tell you what was it's problem and the possible solution.
Wifi and bluetooth had started working from nothing. Then, it stopped again. And it went this way several times since. Now, it's working properly, but it may stop anytime. Could it still be a hardware issue? I just have updated 4.4.4 yesterday. In one of the situations, I found the message "supplicant status: scanning".
rafaelrossignoli said:
Wifi and bluetooth had started working from nothing. Then, it stopped again. And it went this way several times since. Now, it's working properly, but it may stop anytime. Could it still be a hardware issue? I just have updated 4.4.4 yesterday. In one of the situations, I found the message "supplicant status: scanning".
Click to expand...
Click to collapse
Yes. based on the information you have provided, and my personal experience, I would suspect a hardware failure.
samwathegreat said:
Yes. based on the information you have provided, and my personal experience, I would suspect a hardware failure.
Click to expand...
Click to collapse
Well, wifi and bluetooth aren't working anymore since my last post. There's a big battery drain - something like 60% of battery life in 3 hours with phone - supposedly - in sleep mode, even when it is in airplane mode. It seems the system tries to find wifi and bluetooth. When I see my battery status, Android OS and Android System processes are draining more battery life than screen itself. Could it be a hardware failure even if wifi and bluetooth get back working sometimes?
I think I'll buy a lower cost android phone if I decide sending my Moto X warranty. It's complicated staying without a smartphone during 20~30 days.
I appreciate you all for the help and considerations.
Update: sending my Moto x warranty. Tell you what was wrong when I get it back
crappy wifi
rafaelrossignoli said:
Update: sending my Moto x warranty. Tell you what was wrong when I get it back
Click to expand...
Click to collapse
Have you managed to get an update? I think I am having the same exact problems.
Not a developer device so can't unlock the bootloader
Not rooted. \persist\ is empty if that would make any difference at all.
Surprisingly once when I restarted the phone in bptools menu options on the boot menu, the phone came up fine and I was able to turn on my wifi and bluetooth. After about 10 minutes, the phone restarted on it's own and ever since they won't turn on.
Did a full wipe, FDR and also wiped cache but still the same now. Booting using BPTools menu option doesn't help any more.
For the last couple weeks, my phone is just guzzling data on 4G. Having a wifi would help. Please don't suggest me to do a warranty repair That is what I might end up doing in about two weeks. The unlocked device was bought in India but I am now abroad.
Using XT1052 running Kitkat 4.4.4 - AsiaRetail.
mutukrp said:
Have you managed to get an update? I think I am having the same exact problems.
Not a developer device so can't unlock the bootloader
Not rooted. \persist\ is empty if that would make any difference at all.
Surprisingly once when I restarted the phone in bptools menu options on the boot menu, the phone came up fine and I was able to turn on my wifi and bluetooth. After about 10 minutes, the phone restarted on it's own and ever since they won't turn on.
Did a full wipe, FDR and also wiped cache but still the same now. Booting using BPTools menu option doesn't help any more.
For the last couple weeks, my phone is just guzzling data on 4G. Having a wifi would help. Please don't suggest me to do a warranty repair That is what I might end up doing in about two weeks. The unlocked device was bought in India but I am now abroad.
Using XT1052 running Kitkat 4.4.4 - AsiaRetail.
Click to expand...
Click to collapse
For first, thank you for reminding me about this thread. I bring bad news for you, unfortunately. It's 99% a hardware failure. In my case, it really was one. After 25 days, my phone was back from warranty with a new wifi/bluetooth hardware.
My phone was behaving the same way as yours. Sometimes the wifi was back working for a while, then my phone restarted and wifi was unavailable again. So, i recommend you send your phone warranty as soon as possible. Good luck!
rafaelrossignoli said:
So, i recommend you send your phone warranty as soon as possible. Good luck!
Click to expand...
Click to collapse
Well, I don't think I really have a choice here. I would be able to give my device for service only in about another 2 weeks so I have to live with 4G! I'll let you know how it goes. And thanks for the update...
wifi and bluetooth not turning On FIX
Hello everybody.i use a moto x (xt1052) 4.4.4 kitkat not rooted.
A week ago started having problems with wifi communication not turning on and a couple of days later bluetooth couldnt locate any connections
I fixed these problems by switching to ART Runtime from the developer settings.this will reboot your phone and starts upgrading your apps .after that wifi and bluetooth work fine .(for now..)
I am also wondering if anyone has any random reboots or its just my pocket..
Hope it helps for you too.
Cheers,Stelios
Updated: WiFi and Bluetooth stopped working again.leaning more on software issue than hardware.
are.petrakis said:
I fixed these problems by switching to ART Runtime from the developer settings.this will reboot your phone and starts upgrading your apps .after that wifi and bluetooth work fine .(for now..)
Updated: WiFi and Bluetooth stopped working again.leaning more on software issue than hardware.
Click to expand...
Click to collapse
Nope, that didn't help me at all. I think at least my issue is hardware related. Giving the phone for warranty repair on Thursday, let's see what happens.
Update
Been to the service center a week ago. Apparently the moment I explained my issue, they said it is an hardware issue and so the board needs a replacement. Got my phone back and it has been a week with no issues. Fingers crossed...
Well I updated my Moto X XT1092 to 5.1 yesterday. Since then, the ear speaker has stopped working during both incoming calls and outgoing calls. I can hear everything clearly while on loud speaker, however i can't hear a thing while enabling the ear speaker. The person I am talking to can hear everything though. After the update, i cleaned the device using clean master. I haven't done a factory reset yet and haven't done anything in the recovery either, hoping there is an easier fix to it. Can anybody help me fix it?
I am having the exact same issue. But in my case the earpiece worked initially and suddenly stopped working from yesterday. I tried rebooting the phone as well as rebooting in safe mode. Both didnt help. I also tried to clear the cache and data for the phone and dialer app, which didnt help either? I am planning to do a factory reset. Will that have any impact? I was on 5.0 pure edition when i sideloaded the 5.1 soak LPE23.32-14.
I forgot to mention that the earpiece worked initially in my case too. I did make one phone call and everything was fine till that point. And then it all started few minutes later. I did an ota update and I really wasn't expecting such issue. So if clearing cache and the dialler didn't help you fix the issue, I guess our only option is to factory reset. Let me know if factory resetting fixes the issue.
rectifyy said:
I forgot to mention that the earpiece worked initially in my case too. I did make one phone call and everything was fine till that point. And then it all started few minutes later. I did an ota update and I really wasn't expecting such issue. So if clearing cache and the dialler didn't help you fix the issue, I guess our only option is to factory reset. Let me know if factory resetting fixes the issue.
Click to expand...
Click to collapse
The factory reset didnt help too. Still having the same issue after factory reset
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Well, i found this link and it gives instructions on how to fix the earpiece issue...I will give it a go later. I am very surprised that factory reset didn't help either.
rectifyy said:
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Well, i found this link and it gives instructions on how to fix the earpiece issue...I will give it a go later. I am very surprised that factory reset didn't help either.
Click to expand...
Click to collapse
This didnt help either, Still the issue persists even after following every steps on that tutorial. Let me know if you have any luck with that
UPDATE:Finally got it working after updating to the latest build 23.16.3 posted in the general section
Nothing has worked for me so far. Is your phone xt1905? Well mine is xt1902 and I had updated it through ota before the entire issue started, and the build is 23.16.1. So I guess I'm already on the latest build. Do you have any suggestion regarding what i should do?
Hi,
I am also facing the same problem. I just updated my phone to 5.1 and now my ear speaker is not working one thing i noticed is if i connect a headphone, i am able to hear the sound, but the internal ear speaker of the phone is not working
Have anyone found any solution for it ?
Ear Speaker stop working after 5.1 update
Hi
I am also have same issue of ear speaker after 5.1 update.
I have done cache clear it doesn,t help.
I have done factory reset thrice my Moto X2.
After reset ear speaker start working but when i update pre installed apps then again ear speaker stop working. I have done it twice.
Third time i have reset my phone and now i am not updating any app.. its working fine..
Please help me to get out from this issue..
thanks
Ravneet Lohchab said:
Hi
I am also have same issue of ear speaker after 5.1 update.
I have done cache clear it doesn,t help.
I have done factory reset thrice my Moto X2.
After reset ear speaker start working but when i update pre installed apps then again ear speaker stop working. I have done it twice.
Third time i have reset my phone and now i am not updating any app.. its working fine..
Please help me to get out from this issue..
thanks
Click to expand...
Click to collapse
Someone over in the Motorola forums suggested checking to see if hearing aid compatibility was enabled in the settings of the dialer, and disabling it if it was.
Resolution for earpiece not working after 5.1 upgrade on moto x 2nd gen
walrusmonarch said:
someone over in the motorola forums suggested checking to see if hearing aid compatibility was enabled in the settings of the dialer, and disabling it if it was.
Click to expand...
Click to collapse
please note : Go to dialer and disable hearing aid, earpiece will start working.
No need of factory reset
I haven't updated to 5.1 and hearing aid isn't enabled.. Only thing I can think of is the dictionary update wifi required notification being the last thing that was done before losing sound in the ear piece. To remove dictionary updates is there a specific app I can clear data from?
owaismomin said:
please note : Go to dialer and disable hearing aid, earpiece will start working.
No need of factory reset
Click to expand...
Click to collapse
You legend, this worked! I've been trying everything. How the hell did they get enabled during the 5.1 update?
I found it a bit weird that it was working after factory reset and then suddenly stopped.
found this thread because my earpiece stopped working today. stock android 5.1 att moto x 2014. tried a bunch of stuff (hearing aid, wipe cache, reboot,..) didnt work. What did work for me was as simple as it gets. in my settings i turned everything off except cell signal (wifi, blutooth, location, screen rotate...) tried a call it worked. Dont know why or how but it did. havent tried turning everything back on yet. a bit scared to. Hope this helps someone.
!!UPDATE!! I do not think that helped . went out again and turning everything off didnt work.... So i back tracked to what I did before turning everything off. that step got my speaker back again for now at least. What that step was is i called my voicemail and inserted headphones in and out a couple times. I am thinking that the dialer thinks there are headphones plugged in so no speaker. I also believe it has to do with the dialer software since all other sounds and apps come out loudspeaker. using internal speaker test app internal speaker does not work when it is out. If it goes out again i will try headphones in that app to see if that resets it.
on I side note i just realized all my homescreen apps and widgets are gone. they are still installed just not on homescreen
So did anyone reach an effective solution regarding this issue or determined the root cause? It just happened to me today and i have been trying everything i have read online but nothing worked. Any help would be greatly appreciated.
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
affiatic said:
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
Click to expand...
Click to collapse
Tried doing that as well, didn't work.
Did anyone else find any solution?
I have wiped cache, cleaned the headphone jack, did the hearing aid thing.
Nothing has worked.
affiatic said:
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
Click to expand...
Click to collapse
Found the solution, it was water damage actually.
My mom forgot to tell me that water went in through the headphone jack.
And as water conducts electricity the phone thought headphones were plugged in. Cleaning it with a cloth and a toothpick and then shaking the phone a few times fixed it.
I think that's why cleaning your headphone jack fixed it as well affiatic, water went in probably.
My friend is suffering from the same situation.
1. Tried clearing data + cache for dialer app.
2. Hearing aid compatibility disabled.
3. Did factory reset.
Nothing has worked so far.
Can anybody elaborate the solution suggested in the below link? (Im getting 403 error opening the link.)
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Click to expand...
Click to collapse
Would be grateful if someone could provide a valide solution.
Model :- XT1092
Build :- 23.16.3
Moriarty82 said:
My friend is suffering from the same situation.
1. Tried clearing data + cache for dialer app.
2. Hearing aid compatibility disabled.
3. Did factory reset.
Nothing has worked so far.
Can anybody elaborate the solution suggested in the below link? (Im getting 403 error opening the link.)
Would be grateful if someone could provide a valide solution.
Model :- XT1092
Build :- 23.16.3
Click to expand...
Click to collapse
Have you ever tried to make or receive a call on your Moto X and you hear nothing on the other side, almost as if there isn’t even a connection made? Then when you try to call again, for some reason it works?
If you have experienced this, you also understand how frustrating it can be when you have to hang up and dial again, just to make a simple call. This problem plagued me for months of owning my 2014 Moto X, searching everywhere for a resolution to this hugely annoying problem. It wasn’t only me who was experiencing this issue either. A friend with the same phone was having the exact same problem as I, however it was impacting them even more, since it was used for their business. At this point, I figured that it wasn’t only the both of us experiencing the issue, but potentially many others owners as well. After much more searching, I came across a similar issue on a different phone, which listed some ideas to fix the issue. To my surprise, when I completed the process, the problem was fixed and has yet to return. Here is what I did…
Fix Inability to Hear Calls on Moto X
I had tried many different things to fix this issue, such as switching from Dalvik to Art, then back to Dalvik again. Rebooting the phone also didn’t seem to help much at all. Now for what fixed the error (scroll below for the steps).
First, I wanted to clear all cache, as that can sometimes fix simple issues. After I had entered the Recovery menu and cleared the cache, I noticed the problem had stayed away for a bit longer than a reboot, but eventually it came back again. Next, I put the phone into Safe Mode. Once the phone rebooted into Safe Mode, I shut down the device and plugged it in to my wall charger for two hours. To my surprise, after two hours when I turned my phone back on and tried making a call, I could hear the other side. The problem was gone and has yet to return, months later.
Anybody that has experienced this same issue, should try the steps below. It may just make your phone much less frustrating to operate.
Putting the Moto X into Recovery Mode to Delete Cache:
1. Power off your phone, by pressing down the power button until the power menu pops up and selecting*Power Off.
[http://salloiacono]
2. Wait a few seconds, then proceed to next step.
3. Hold down the*Volume Down*for a second, the while still holding down the*Volume Downbutton, also hold down the*Power Button*for about 3 seconds, then let go of*Power Button. If you did this correctly, you will see the*Boot Menu.
[http://salloiacono]4. Press the*Volume Down*button, until you have*Recovery*highlighted. Then pressVolume Up*to select*Recovery.
5. Your phone will appear to reboot and you should see this little guy.
[http://salloiacono]
Don’t worry, you didn’t break anything.
6. Now you must enter the*Recovery Menu.
– For Android 4.4.4: Hold down the*Volume Up*button for about 10-15 seconds and while holding that down, press the*Power Button.You should see a new menu pop up.
– For Android 5.0: Hold down the*Power Button*for a few seconds and while holding that down, press the*Volume Up*key. You should see a new menu pop up.
[http://salloiacono]
7. Press*Volume Down*until you have*Wipe Cache Partition*highlighted, then press thePower Button.*Your phone will now reboot. It is time for the next step.
Putting your Moto X into Safe Mode
1. Once your phone has fully rebooted, you are now ready to put your phone into*Safe Mode. Hold down the*Power Button*until thePower Menu*pops up. Now press and hold thePower Off*button.
[http://salloiacono]
2. After a few seconds, you should see a new window pop up warning about*Safe Mode. Press*OK. Your phone will now reboot intoSafe Mode.
[http://salloiacono]
3. Once your phone reboots into*Safe Mode,Power Off*your phone.
4. With your phone powered off, plug it into your wall charger for 2 hours.
5. After 2 hours, you may unplug your phone and turn it back on. Now you should be able to make and receive calls without the issues you were experiencing before!
Hope this works as well for you as it did for me!
Verstuurd vanaf mijn XT1092 met Tapatalk
Hi guys, just got my mix around a week ago. Flawless at first, no real complain, then this morning i noticed my smartband hasnt given me any notification and it turns out the phone bluetooth connection is dead.
Dead as in you can click it to tell it to turn itself on, but nothing happens. It doesnt recognise any bluetooth nearby either. Tried the test in the about section of the phone and it doesnt give me anything on the bluetooth status, just blank.
Tried restarting the phone, same thing. Factory reset, same thing. Im on 8.0 global rom straight from when i bought it. Any idea if this is hardware or software?
Thanks
I flashed EpicROM from last week and now I can't connect to my Bluetooth speaker. I can still see Bluetooth devices but it's not pairing. Worked on EpicROM from february
mr_sheen said:
Hi guys, just got my mix around a week ago. Flawless at first, no real complain, then this morning i noticed my smartband hasnt given me any notification and it turns out the phone bluetooth connection is dead.
Dead as in you can click it to tell it to turn itself on, but nothing happens. It doesnt recognise any bluetooth nearby either. Tried the test in the about section of the phone and it doesnt give me anything on the bluetooth status, just blank.
Tried restarting the phone, same thing. Factory reset, same thing. Im on 8.0 global rom straight from when i bought it. Any idea if this is hardware or software?
Thanks
Click to expand...
Click to collapse
That is vendor ROM.
Well at the very least you still able to toggle the bluetooth on and off, while mine just doesnt even budge. Really disappointing though...
mr_sheen said:
Well at the very least you still able to toggle the bluetooth on and off, while mine just doesnt even budge. Really disappointing though...
Click to expand...
Click to collapse
Think you are going to have to flash proper ROM
jazz452 said:
Think you are going to have to flash proper ROM
Click to expand...
Click to collapse
Yup. Im very rusty about all this rom flashing things nowadays. I'll read some and hopefully can flash some tonight, need my device up and running for monday morning :crying:
*edit:
Updated to 8.2 global and the Bluetooth still fudged. Guess im probably selling the phone then as it looks like hardware failure
mr_sheen said:
Yup. Im very rusty about all this rom flashing things nowadays. I'll read some and hopefully can flash some tonight, need my device up and running for monday morning :crying:
*edit:
Updated to 8.2 global and the Bluetooth still fudged. Guess im probably selling the phone then as it looks like hardware failure
Click to expand...
Click to collapse
Did that include full wipe?
jazz452 said:
Did that include full wipe?
Click to expand...
Click to collapse
Good point Jazz....when I dirty flashed to the 8.2 global rom I was having all kinds of forced closes literally almost every few seconds it seemed. It clearly stated in the guide if you go from developer rom to global you should do a complete wipe but I seemed to miss that part. I then re formatted and started from scratch and it worked like a charm after that...zero FCS. Give it another try if you didn't wipe it last time, could make the difference.
I'm from official rom 8.2.3.0 stable and without bluetooth since 3 days ... I wait for an official update or it's hardware problem ? What can i do ? I'm so sad and disappointed with this !
Nobody can help me ? It's software or hardware problem ?
[email protected] said:
Nobody can help me ? It's software or hardware problem ?
Click to expand...
Click to collapse
Try to do a clean flash with another rom, like global or last beta. Probaly, is a software problem.
I'm already on global rom ... A clean flash is full erase of the phone but Mi Mix without SD card is a big problem for backup all my phone ...
I gotts say i bought this phone with high hopes but it is a total c**p. Moving from opo5 I regret it all the way. My Bluetooth doesnt work also. I tried resetting phone and settings only since it doesn't back up app data (except for sone google spps) i dont want to factory reset. Anyone had a chance fixing it?
wolus666 said:
I gotts say i bought this phone with high hopes but it is a total c**p. Moving from opo5 I regret it all the way. My Bluetooth doesnt work also. I tried resetting phone and settings only since it doesn't back up app data (except for sone google spps) i dont want to factory reset. Anyone had a chance fixing it?
Click to expand...
Click to collapse
update firmware and install custom rom
wolus666 said:
I gotts say i bought this phone with high hopes but it is a total c**p. Moving from opo5 I regret it all the way. My Bluetooth doesnt work also. I tried resetting phone and settings only since it doesn't back up app data (except for sone google spps) i dont want to factory reset. Anyone had a chance fixing it?
Click to expand...
Click to collapse
Did you buy it new, which ROM, could it be vendor rom, do as suggested, back up you're data, install custom rom it's the only way to find out if it's hardware, no one else is reporting these sorts of problems even after 2 years of abuse.
Sorry posted in wrong section. I bought new global mix 2S and has latest ota.
wolus666 said:
Sorry posted in wrong section. I bought new global mix 2S and has latest ota.
Click to expand...
Click to collapse
Near enough mate.