Hey guys!
I have a problem on my unlocked Moto X (1058).
After the last update (4.4.3), my GPS is losing lock everytime. I'm used to use my Moto Assist on my Moto X to listen any incoming message and call, but after this update, my GPS shows my location almost 1 km far from my home and, due that, Moto Assist is not working properly.
I realized this issue happened only with "High Precision" mode (the one that uses 3g and wifi, found in Settings > Localization) activated. "Only in device" mode shows my correct location, but I can't use Moto Assist like this.
It wasn't happening with 4.4.2. Do anybody have any idea of what it could be? I have already cleanend some apps caches, full reset, but the problem keeps going on.
I'm kind sorry for my english.
Thanks,
I have an unlocked XT1053 on 4.4.3 and use high accuracy with the gps on in Location. I had difficulty initially getting Assist Home to work, but finally got the home location set. I took about a half mile walk one evening and after returning home, Assist still didn't work. I turned off the phone for the evening and when I started it the next morning, Assist started working all by itself. It has been flawless since.
Even I am having GPS signal issues with my X updated to 4.4.3
Sent from my XT1053
prakashr85 said:
Even I am having GPS signal issues with my X updated to 4.4.3
Sent from my XT1053
Click to expand...
Click to collapse
Hmmm I am having GPS issues too. I am on Verizon with a locked boot loader and write protection disabled. NOTE: I have NOTE updated to 4.4.3 but i did get the new version of assist the day before I started having problems. However, uninstalling Assist did not fix the problem. I talked to Verizon and Moto and neither new of an issue.
Anyone know whats causing this???
Related
I am on the AT&T Variant of the Moto X and was wondering if anyone was having issue with Touchless Controls not working. It has been working fine since day one and I noticed today that it wouldn't work. I rooted using the Moto Root and then PwnMyMoto. When I boot, the option to use them is turned off and when I enable it I get no response from saying the keyword. If I try to retrain it, It will not respond to the "Okay Google Now" Attempts. I've verified that the mic is working fine and I've tried several different noise levels.
If anyone has a solution or suggestion, let me know to possible help people who have this issue
Abstract_Logic said:
I am on the AT&T Variant of the Moto X and was wondering if anyone was having issue with Touchless Controls not working. It has been working fine since day one and I noticed today that it wouldn't work. I rooted using the Moto Root and then PwnMyMoto. When I boot, the option to use them is turned off and when I enable it I get no response from saying the keyword. If I try to retrain it, It will not respond to the "Okay Google Now" Attempts. I've verified that the mic is working fine and I've tried several different noise levels.
If anyone has a solution or suggestion, let me know to possible help people who have this issue
Click to expand...
Click to collapse
I'm having the exact same issues on my Verizon Moto X. I'm hoping you found a fix for yours or that someone can chime in
Tried a factory reset?
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
640k said:
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
Click to expand...
Click to collapse
Hmm, it doesn't seems like poor performance. I ended up every task and it still happened.
However, I noticed that when I check the "2G ONLY" option it comes back to work. Maybe it's something with the HSPA/HSPA+ connection.
it could be completely carrier dependent then. my experience has been with vzw.
Moto X "Call Ended"
I have experienced this same problem in Houston on the T-Mobile network after switching over to Android. My T-Mobile rep told me they have had towers vandalized for copper which has impacted service for them, I believe he said it was about 15 towers and 10K a pop to get things corrected. What gets me is I was on a Bold 9900 and while I had signal problems in the affected areas of town I didn't not experience the "call ended" issue. I can also call other T-Mobile phones from those same areas but not land lines so to me this seems like a possible network routing issue which I have seen before between specific carriers.
If the problem does continue I may have to switch carriers. T-Mobiles service was previously outstanding in Houston but recently had not been great after the 4G LTE upgrades. I support multiple hospitals and need service to work correctly and will work with the T-Mobile Engineers to see if I can make headway on that front. I noticed another MotoX user reporting he only had the issue when flying in to Houston for work and that everything worked for him outside of Houston. His solution was to operate in 2G mode which for me is really not an option. I have to handle a lot of tasks over the network while on calls.
Anyways I would appreciate it if others could post if they are experiencing these issues and give as many details as possible so we can try to isolate the root cause of this problem and if found to be a carrier issue we can escalate with them. Thanks
dicarli said:
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
Click to expand...
Click to collapse
Call Ended Issue Resolved
Hi All,
I see this Call Ended Issue in many brands. So I assume the error is a combination of the Network along with the SimSlot.
I tried various combinations for my Moto-E mobile.
Before i post the solution i found, Let me provide a brief about the problem.
I use Vodafone network on sim1 slot and Uninor network on Sim2 slot. I started facing the call ended issue on my sim 1 vodafone network.
I inter changed the sim's and found the network working absolutely fine. This makes me to understand that the sim1 slot with the vodafone carrier has some network issue where that IMEI code has some problem.
i tried to place the vodafone sim again on the sim 1 slot and found the problem persists. So i came to that conclusion.
Hope this might help you and provide a instantaneous and temporary resolution.
Thanks,
Praveen.
Call Ended problem still going...
Hey,
I just rooted my Moto X (XT 1053), like 5 min ago, in the hope to fix this same problem. I`m no programer/developer and have nothing against rooting, I just don`t think I`m that kind of user. Anyway, about a week ago my phone started to drop my calls right after dialing. I restored factory settings, updated it and nothing worked. I took it for service and they offered to charge me 150 bucks to restore factory settings and update the software. So I was kinda forced to root and try to fix it this way. The problem is that I probably don`t understand half of what you guys say, so if there are any kind souls out there, please help me out.
To sum it up:
- No Sim Card error
- I get carrier services and can use mobile internet (3G because 4G is still too explensive here in Brazil)
- Directly drops my calls
- Won't receive calls
- Won't send or receive text messages via carrier (just over 3G or wifi)
I`ve tried another carrier's Sim Card, no go.
I`ve tried my Sim Card on another phone and it worked just dandy, so I really don`t think it`s carrier related.
I`m running Android 4.4.3, as the other updates weren`t available for my phone via Motorola. I thought maybe updating to a newer version of Android might do the trick. I just have no clue on how to do that on a rooted phone... or on a non rooted phone for that matter.
Can anyone give me any tips/pointers/etc... ?
Thanks!
I have the same issue with my moto x on Verizon. Have you been able to figure it out?
sorry if this has been answered but I have searched all over and cant find it.
So I took the spint OTA the other day and now every one in awhile i recieve Assisted dialing error / Invalid Mobile country code. I have turned off assisted dialing but I'm still getting this error. It takes me off 4g and says its on 3g but yet no connection seems to be there at all. anyone else have this problem?
david.herh said:
sorry if this has been answered but I have searched all over and cant find it.
So I took the spint OTA the other day and now every one in awhile i recieve Assisted dialing error / Invalid Mobile country code. I have turned off assisted dialing but I'm still getting this error. It takes me off 4g and says its on 3g but yet no connection seems to be there at all. anyone else have this problem?
Click to expand...
Click to collapse
Did you do a factory reset, I know you lose everything but in my past experience, factory reset after taking an ota is a must.
Sent on my Moto X
I've been intermittently getting this error for the past couple of days too. And yes, I did a factory reset after the KitKat OTA.
I am also getting this notification a few times a day. Both my "current country" and "reference country" are correctly set to USA, and it doesn't matter if I have assisted dialing turned on or off. Fortunately, it doesn't seem to affect the cell signal.
Just got my Sprint Moto X two days ago and did the KitKat update immediately on receiving.
Doing a search on it, it seems to have been infrequently reported going back several years, and always on Motorola devices. And sometimes has been reported as causing loss of the cell signal until you reboot.
fwald said:
I am also getting this notification a few times a day. Both my "current country" and "reference country" are correctly set to USA, and it doesn't matter if I have assisted dialing turned on or off. Fortunately, it doesn't seem to affect the cell signal.
Just got my Sprint Moto X two days ago and did the KitKat update immediately on receiving.
Doing a search on it, it seems to have been infrequently reported going back several years, and always on Motorola devices. And sometimes has been reported as causing loss of the cell signal until you reboot.
Click to expand...
Click to collapse
It's not a huge deal but kind of annoying. And it only started happening to me a few days ago.
clankfu said:
It's not a huge deal but kind of annoying. And it only started happening to me a few days ago.
Click to expand...
Click to collapse
Agreed. If it ever starts resulting in loss of cell signal, however, it will be a huge pain.
I have this happening as well. It seems to happen often when the phone registers to a new tower while I am driving. To make it go away I "change" my country to USA. I changed it last night while driving and it went away. I haven't had it back since. I don't know if this is a random issue with sprint's network or if it is problem with the phones. Perhaps we can try to figure this out?
I have my # connected to Google Voice.
My phone is a replacement phone from Motorola.
My phone would not self-activate, I had to call and get it manually programmed by Sprint support.
Do we have anything in common?
My phone would not self activate either but that's the only thing in common on those grounds.
dshiznit00 said:
I have this happening as well. It seems to happen often when the phone registers to a new tower while I am driving. To make it go away I "change" my country to USA. I changed it last night while driving and it went away. I haven't had it back since. I don't know if this is a random issue with sprint's network or if it is problem with the phones. Perhaps we can try to figure this out?
I have my # connected to Google Voice.
My phone is a replacement phone from Motorola.
My phone would not self-activate, I had to call and get it manually programmed by Sprint support.
Do we have anything in common?
Click to expand...
Click to collapse
Wasn't it already on USA?
I also have my number integrated with Google Voice via Sprint.
I seem to get this error whenever it switches from wifi to mobile data.
[
dshiznit00 said:
I have this happening as well. It seems to happen often when the phone registers to a new tower while I am driving. To make it go away I "change" my country to USA. I changed it last night while driving and it went away. I haven't had it back since. I don't know if this is a random issue with sprint's network or if it is problem with the phones. Perhaps we can try to figure this out?
I have my # connected to Google Voice.
My phone is a replacement phone from Motorola.
My phone would not self-activate, I had to call and get it manually programmed by Sprint support.
Do we have anything in common?
Click to expand...
Click to collapse
I'm integrated with Sprint/Google Voice, but was getting it right off the bat before I even set up GV.
Mine is a new phone.
My phone also would not self-activate, I went to the Sprint web site and entered the MEID and UCC but still had to call them.
However, I only experienced the problem 1-2 more times since my post. I only had the phone in my house, which I suppose doesn't eliminate tower switching but makes it less likely.
I've since unlocked the bootloader and rooted and haven't had it once after that.
It does seem to be a Sprint-only issue with the Moto X this time, but if you do a Google search it was a rare issue with other Moto phones.
Whenever I get a phone call while not on WiFi the below image pops up and causes the screen to lock. How do I get rid of it???
No ideas?
Until Verizon's LTE calling update some time this fall, the Moto X can't support voice and data at the same time.
No such problem on AT&T....
Just like Chris said, VZW needs to release a sw update so we can have Advance Calling(http://phandroid.com/2014/09/20/verizon-moto-x-launch-without-simultaneous-voice-data/). Until then, you have to be on wifi if you want to simultaneously talk and surf...
I understand that there needs to be an update, is there anyway to get rid of that message? It screws up answering and hanging up calls. Thanks
This "feature" is one of the reasons I switched back to the HTC One M8... Not being able to use Data and Voice at the same time is so 10 years ago - no clue why the hell they took a step back like this. I really like the moto X 2014, but with that "feature" and bluetooth not working properly (stuttering when playing music) I just can't use the device. - Additionally root/native tethering without paying for it are show stoppers. All stuff I can do with the m8, hopefully the Nexus 6 isn't impeded by the same shortcomings of the moto x
I've noticed everything you said as well. I'm going to give the X to my wife to replace her GS4 and just get the nexus. When the X was ordered they hadn't announced that it would be on VZW yet...
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.