From my research, it seemed like a lot of people had the issue of echoing when using speakerphone for 3rd-party apps, such as Hangouts, on the 2014 Moto X running Lollipop. Has anyone tried it out using 6.0? Wondering if this issue has been fixed or not?
Related
Hi all,
I hope you can help me out with this, I've been looking a lot for a while in google and found no answers so my frustration led me to post on this forum. Here is the situation:
Back on 2013 I had the Magicjack app installed on my Moto X XT1058 (AT&T) stock android 4.4.2, I believe the app version was 2.7.710.1 or 2.6.661.3, and it worked fine. After installing latest versions, when I made a call I could hear the others but they couldn't hear me, I thought it was due to a magicjack compatibility issues, but all the subsequent versions didn't work either, so I had to keep using the older version.
Yesterday I factory reset my phone and installed the most updated Magicjack app hoping the problem would be solved but still the same issue, so I tried to install the old version but now it crashes immediatly once I open the app, so I cannot use the app anymore. I've been surfing in google hoping someone has the same problem but can't find anything, so it seems I'm the only one with this issue. I'm hoping someone had the same problem and found out how to solve it.
Thank you very much.
sergethug said:
Hi all,
I hope you can help me out with this, I've been looking a lot for a while in google and found no answers so my frustration led me to post on this forum. Here is the situation:
Back on 2013 I had the Magicjack app installed on my Moto X XT1058 (AT&T) stock android 4.4.2, I believe the app version was 2.7.710.1 or 2.6.661.3, and it worked fine. After installing latest versions, when I made a call I could hear the others but they couldn't hear me, I thought it was due to a magicjack compatibility issues, but all the subsequent versions didn't work either, so I had to keep using the older version.
Yesterday I factory reset my phone and installed the most updated Magicjack app hoping the problem would be solved but still the same issue, so I tried to install the old version but now it crashes immediatly once I open the app, so I cannot use the app anymore. I've been surfing in google hoping someone has the same problem but can't find anything, so it seems I'm the only one with this issue. I'm hoping someone had the same problem and found out how to solve it.
Thank you very much.
Click to expand...
Click to collapse
I use magickjack and had the same problem. I found a workaround. When you make the call press the speakerphone button to turn it on. Then press it again to turn it off. After that it works perfectly for the call. However it's not permanent. I have to do this every call I make.
Sent from my XT1058 using Tapatalk
AGISCI said:
I use magickjack and had the same problem. I found a workaround. When you make the call press the speakerphone button to turn it on. Then press it again to turn it off. After that it works perfectly for the call. However it's not permanent. I have to do this every call I make.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot man, such an easy solution... In any case its weird this happens on moto x, i live with my two brothers, one with S3 the other with Nexus 5 and they don't have any issues... Anyway I don't mind pressing the speaker each time, thanks again!!
I am experiencing a similar problem with my ACER Wifi only tablet ( no sim version). Any suggestions please.
I had been using ACR call recorder since about November and it had been working great but recently I went to listen to some recordings and they were not there. I left a negative review and was informed that with androind 5.0 motorola had disabled the 2 way call recording feature they used.
Is there a way around this? Can I reenable this feature somehow? I am happy to root and boot a custom rom I just want to know for sure that will solve the problem before I do it.
Can anyone offer any advice at all on this? even to say it isnt possible or it is?
This thread Lists the Moto X (with root) as working but doesn't speciffy 1st/2nd Gen. (though there is mention of the Moto G 2nd Gen).
1r1sh said:
Can anyone offer any advice at all on this? even to say it isnt possible or it is?
Click to expand...
Click to collapse
I use Total Recall Call Recorder by Killer Mobile on mine, just need to be rooted. There was a motorola hack within the app if I remember correctly. But it works fine for me and I'm on 5.0.
I have the issue of moto voice turning off randomly, it all started when I turned on google voice instead for a day then switched back but I made sure to turn off google voice before turning on moto voice, does anyone have a similar issue or a solution? ( I have attached a snapshot of my system version )
I have same problem , when i drive my car and i say " ok moto x" my phone not answer me, and when i look in moto voice the option is disable :/
Sent from my XT1097 using XDA Premium 4 mobile app
Android.is.better94 said:
I have the issue of moto voice turning off randomly, it all started when I turned on google voice instead for a day then switched back but I made sure to turn off google voice before turning on moto voice, does anyone have a similar issue or a solution? ( I have attached a snapshot of my system version )
Click to expand...
Click to collapse
I have the same problem... I notice that this started since I installed Xposed, maybe is related somehow. Also if I force close Google Search the voice commands just turn off.
same here, lollipop stock with EU firmware, no root. Seems like this beahviour is following the latest and recent Moto app update.
Didn't enabled Ok Google Hotword anyway.
Since updating to B852, every time I make or receive calls from hangouts or whatsapp the earpiece is mute and I have to switch to speakerphone. Not sure if it is ROM or app related. Earpiece does work normal when calling using SIM and phone app.
Anyone encountered this?
relic said:
Since updating to B852, every time I make or receive calls from hangouts or whatsapp the earpiece is mute and I have to switch to speakerphone. Not sure if it is ROM or app related. Earpiece does work normal when calling using SIM and phone app.
Anyone encountered this?
Click to expand...
Click to collapse
It is most likely the third party app problem and since regular calling works, it is up to the developers of the app to fix this.
Can anyone confirm this if it is related to app problem?
relic said:
Can anyone confirm this if it is related to app problem?
Click to expand...
Click to collapse
I also have b852 installed, and I haven't had any issues with it whatsoever, but I'm also not using those apps.
Greetings everyone,
I originally posted this on the Lenovo official forums but haven't receive any feedback. I was wondering if anyone else had encountered this issue. After a fresh (re)boot, my phone will work as expected using the standard speaker for calls in and out. However, after using Moto Voice once or twice to make calls out all incoming and outgoing calls start with speakerphone no matter what I do. I've confirmed this behavior in safe mode - it's only after using Moto Voice. Google Assistant can be used and not trigger the issue.
Has anyone else had this happen?
Maybe clear data and cache and see if that helps? I'm not really familiar with Moto Voice but have you considered Google Assistant? I just assumed Moto Voice(and similar apps like Samsung Bixby) are just OEM's trying to harvest the data for their own use rather than giving it to Google.
Sent from my Moto G6 Plus using Tapatalk
Xplorer4x4 said:
Maybe clear data and cache and see if that helps? I'm not really familiar with Moto Voice but have you considered Google Assistant? I just assumed Moto Voice(and similar apps like Samsung Bixby) are just OEM's trying to harvest the data for their own use rather than giving it to Google.
Sent from my Moto G6 Plus using Tapatalk
Click to expand...
Click to collapse
I did a clear cache and data on all Moto apps, still persisted. As mentioned, Google Assistant works fine without triggering the issue but I'd still like to confirm if this is a Moto bug or something else interfering.