I've got the Moto X GSM developers edition with Kitkat 4.4 unlocked and rooted. I am on H2O wireless (AT&T MVNO). I've had this setup for about a month.
At least several times a day, I'll hear a quick beep in my bluetooth headset alerting me to the fact that I have no mobile signal. I look at the phone and I have zero bars for maybe 30 seconds and then it goes back to (usually) 4 bars. This happens at home, where I always seem to have 4 bars except for these incidents, so it is not like I am in a marginal signal area and it is going between 1 and 0 bars. It also happens when driving around Portland OR on the major freeways. It doesn't happen in the same spots, so I don't think I am driving through a weak signal area. If I'm driving around it happens more often than when I am at home - maybe 10 or more times on a two hour trip.
At least four times I have been driving and the phone kept dropping signal and getting it back maybe 8 or 10 times until it finally lost the signal for good. I powered off and on and then the signal was fine. Once I left the phone on after the signal had dropped out completely until I stopped driving and was in an area that I know that I have had good signal strength before. I left the phone on for at least 10 minutes and the signal would not come back until I power cycled the phone.
Searching here and with google, I couldn't find reports of signal problems like this with the Moto X. So I'm guessing that this isn't some problem endemic to the Moto X. I can't believe that this is normal behavior for a phone on the AT&T network (I just ported from Page Plus on Verizon towers when I got the Moto X and I never got signal dropouts). Could there be something faulty in my phone? Should I try to get a warranty exchange from Motorola? Or is there anything else I can do to debug/fix the problem? Thanks.
There's a reflash toolkit around here. Use it. It fixed a similar issue I was having
MotoX Developer Edition
When you say you ported from page plus, do you mean you are using a verizon moto x on H2O?
If so that could be part of your problem. However, i was having an issue where my Verizon moto x wouldn't connect to 3G on Verizon. It would go from LTE to 1x. I factory reset and it didn't fix it.
Ultimately before I returned it to moto I tried a sbf to 4.2.2 and then accept the ota for 4.4. and that fixed my problems.
All the files for flashing back to 4.2.2 are in the Dev section. Just be sure to backup anything that is important to you. All data will be deleted.
Sent from my XT1060 using Tapatalk
mawells787 said:
When you say you ported from page plus, do you mean you are using a verizon moto x on H2O?
If so that could be part of your problem. However, i was having an issue where my Verizon moto x wouldn't connect to 3G on Verizon. It would go from LTE to 1x. I factory reset and it didn't fix it.
Ultimately before I returned it to moto I tried a sbf to 4.2.2 and then accept the ota for 4.4. and that fixed my problems.
All the files for flashing back to 4.2.2 are in the Dev section. Just be sure to backup anything that is important to you. All data will be deleted.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
No, I don't have the Verizon Moto X, as I said, I have a GSM developers edition Moto X. I was just mentioning Page Plus as my previous experience with never seeing any dropped service. I don't have any previous experience with AT&T towers, so I don't know what might be normal for them. I know coverage is not as good as Verizon in my area, but I can't believe what I am seeing is normal.
I think you are talking about data service, am I right? I am not talking about data, I am talking about problems with voice/text service. I could try going back to 4.2.2 and then taking the OTA, but that is basically the path I took to get where I am now, so I'm not too hopeful that it would change anything.
Same problem here /:
Just wanted to add some info here, experiencing the same issue unfortunately.
GSM Unlocked Moto X 16GB, running off MVNO Straight Talk AT&T LTE.
I'll have several instances where I won't be able to send texts. Every time it bounces back with a "Failure to send SMS" error, and I'll notice that the signal strength will fluctuate rapidly from 0-3 bars. Data works fine, but texts don't send
Had it happen at school, AT&T service is great there. Gonna try it with my Optimus G tomorrow and report back to confirm if it's a device issue.
UPDATE: Moto X issue. Going to call them for a moto maker replacement.
Carbon Trooper said:
UPDATE: Moto X issue. Going to call them for a moto maker replacement.
Click to expand...
Click to collapse
What issue did they say it was? Had this happen twice randomly in 2 weeks, but no sure if it's the phone or the network - otherwise signal has been great.
Ckryt said:
What issue did they say it was? Had this happen twice randomly in 2 weeks, but no sure if it's the phone or the network - otherwise signal has been great.
Click to expand...
Click to collapse
They didn't give me any details I just got to order a new one for free, and they'll take a look at the old Moto X when they get it. Hopefully the new one doesn't do this crazy stuff.
If any issues come up, i'll just return it. Don't see a bright future for Motorola anyways...
johninor said:
I've got the Moto X GSM developers edition with Kitkat 4.4 unlocked and rooted. I am on H2O wireless (AT&T MVNO). I've had this setup for about a month.
At least several times a day, I'll hear a quick beep in my bluetooth headset alerting me to the fact that I have no mobile signal. I look at the phone and I have zero bars for maybe 30 seconds and then it goes back to (usually) 4 bars. This happens at home, where I always seem to have 4 bars except for these incidents, so it is not like I am in a marginal signal area and it is going between 1 and 0 bars. It also happens when driving around Portland OR on the major freeways. It doesn't happen in the same spots, so I don't think I am driving through a weak signal area. If I'm driving around it happens more often than when I am at home - maybe 10 or more times on a two hour trip.
At least four times I have been driving and the phone kept dropping signal and getting it back maybe 8 or 10 times until it finally lost the signal for good. I powered off and on and then the signal was fine. Once I left the phone on after the signal had dropped out completely until I stopped driving and was in an area that I know that I have had good signal strength before. I left the phone on for at least 10 minutes and the signal would not come back until I power cycled the phone.
Searching here and with google, I couldn't find reports of signal problems like this with the Moto X. So I'm guessing that this isn't some problem endemic to the Moto X. I can't believe that this is normal behavior for a phone on the AT&T network (I just ported from Page Plus on Verizon towers when I got the Moto X and I never got signal dropouts). Could there be something faulty in my phone? Should I try to get a warranty exchange from Motorola? Or is there anything else I can do to debug/fix the problem? Thanks.
Click to expand...
Click to collapse
Carbon Trooper said:
Just wanted to add some info here, experiencing the same issue unfortunately.
GSM Unlocked Moto X 16GB, running off MVNO Straight Talk AT&T LTE.
I'll have several instances where I won't be able to send texts. Every time it bounces back with a "Failure to send SMS" error, and I'll notice that the signal strength will fluctuate rapidly from 0-3 bars. Data works fine, but texts don't send
Had it happen at school, AT&T service is great there. Gonna try it with my Optimus G tomorrow and report back to confirm if it's a device issue.
Click to expand...
Click to collapse
Ckryt said:
What issue did they say it was? Had this happen twice randomly in 2 weeks, but no sure if it's the phone or the network - otherwise signal has been great.
Click to expand...
Click to collapse
Just mentioning I have the XT 1053 and have replaced it 2 times. All had the issue mentioned. Some worse than others. I never rooted or done anything to my phone I'm currently testing 4.2.2 since 4.4 and 4.4.2 have been giving me the problem. I'll update if I notice anything.
Also a whole thread here of people are having the same issue:
http://forums.androidcentral.com/moto-x/348535-i-love-my-moto-x-but.html
Someone should reach out to the Motorola engineers on G+ they usually respond pretty fast!
drago10029 said:
Just mentioning I have the XT 1053 and have replaced it 2 times. All had the issue mentioned. Some worse than others. I never rooted or done anything to my phone I'm currently testing 4.2.2 since 4.4 and 4.4.2 have been giving me the problem. I'll update if I notice anything.
Also a whole thread here of people are having the same issue:
http://forums.androidcentral.com/moto-x/348535-i-love-my-moto-x-but.html
Someone should reach out to the Motorola engineers on G+ they usually respond pretty fast!
Click to expand...
Click to collapse
Thanks for the link - I didn't find that thread when I was searching around to see if other people were having the problem.
I am still having the problem. How often it happens each day varies a lot. Some days it hardly happens at all and others it will happen dozens of times. I just installed 4.4.2 a few days ago, so it hasn't been long enough to tell if it has improved with the update. It has happened only a few times since I updated.
This happened to me a few times....only when I was leaving lte and going to 3g. The phone seemed to hang a bit switching over from lte to h+.
I'm thinking if I lived in an area where it switched back and forth a lot, I'd have a real problem. Probably unless a better fix comes along....forcing 3g only would solve it. Though that would be pretty crappy.
Thats what I noticed in my case anyway.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
The x is a msm8960 too. http://forum.xda-developers.com/showpost.php?p=43152766&postcount=1
aviwdoowks said:
The x is a msm8960 too. http://forum.xda-developers.com/showpost.php?p=43152766&postcount=1
Click to expand...
Click to collapse
the link you posted was in russian and google wouldn't translate it.
drago10029 said:
the link you posted was in russian and google wouldn't translate it.
Click to expand...
Click to collapse
It only confirms my claims in my op.
---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------
If a Rsd restore solves your moto x 4g problems then we have more confirmation.
aviwdoowks said:
It only confirms my claims in my op.
---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------
If a Rsd restore solves your moto x 4g problems then we have more confirmation.
Click to expand...
Click to collapse
*#*#4636#*#* OR the Play apps: Phone Info will break the radio IF you select the 3 dots and mess with the band!!
RSD flash or Matts utility is the only fix. Flash of a new radio did not work.
Click to expand...
Click to collapse
Also if you're referring to the above as a fix, I never messed with "phone info' settings and the problem was always apparent even fresh from the factory! :/
drago10029 said:
Also if you're referring to the above as a fix, I never messed with "phone info' settings and the problem was always apparent even fresh from the factory! :/
Click to expand...
Click to collapse
Obviously it is likely to be HW then. Yet Rsd restore may fix it.
aviwdoowks said:
Obviously it is likely to be HW then. Yet Rsd restore may fix it.
Click to expand...
Click to collapse
If it did fix it, then it sure wouldn't be hardware related, but that would be interesting. And it is suspect that only some people are having this issue and others aren't unless other people just aren't reporting it. So many thoughts lol
My wife's phone was having this issue. Would just drop cellular connection. You could make it happen by running a speedtest, as soon as it hit the upload part of the test it would drop all connectivity and a few seconds later it would reconnect. I waited for 4.4.2 to be pushed and that didn't fix it so I waited for the .sbf to flash it clean to 4.4.2 which didn't help either. I swapped her SIM in to my Moto X and it worked without issue.....putting it back in her Moto X and constant drops of cellular connectivity.
I finally had Motorola issue me an RMA to send it back for repairs. They were going to swap it out for new but when they realized it was a Developer Edition they said it had to be repaired. It's been with Motorola for two weeks so far with no info from them on what's going on. Very disappointed in their service so far. Apparently Motomaker versions get handled much faster than Developer Editions.
tcrews said:
My wife's phone was having this issue. Would just drop cellular connection. You could make it happen by running a speedtest, as soon as it hit the upload part of the test it would drop all connectivity and a few seconds later it would reconnect. I waited for 4.4.2 to be pushed and that didn't fix it so I waited for the .sbf to flash it clean to 4.4.2 which didn't help either. I swapped her SIM in to my Moto X and it worked without issue.....putting it back in her Moto X and constant drops of cellular connectivity.
I finally had Motorola issue me an RMA to send it back for repairs. They were going to swap it out for new but when they realized it was a Developer Edition they said it had to be repaired. It's been with Motorola for two weeks so far with no info from them on what's going on. Very disappointed in their service so far. Apparently Motomaker versions get handled much faster than Developer Editions.
Click to expand...
Click to collapse
Yeah it's true Moto maker phone's just get replaced! no questions asked. You ask me their warranty needs work! Also I've tried 4.2.2 and 4.4. Using wifi on and off and nothing has fixed the issue for me. I told them about the issue and got my refund. This is a problem and should be fixed.
This phone would be great if it didn't have camera issues and the MMS and LOS bug I hope you get it fixed. otherwise, let Moto know, be aggressive in your point, speak to a supervisor and get your money back! Best of luck to you.
It's a known 4.4.2 issue that's supposed to be fixed with the 4.4.3 update, among other things. Some of the fixes are Nexus 5 specific, while others are shared issues. I'm currently experiencing the data drop outs frequently, tried everything without luck.
LINK
I have a weird issue popping up and both Google and my tech savvy friends are having no luck in solving it.
My Nexus 6 was originally purchased through AT&T. When I got Project Fi, I worked with a Google rep to flash the Fi firmware onto it so it would be unlocked and work with the Fi network. That was all back in early August. I kept using the phone switching my AT&T and Fi sims in and out whenever needed (AT&T still remains my primary carrier, Fi was more for when I traveled internationally) and it worked fine.
For the last three weeks, I was using my AT&T sim in a Galaxy S6 Edge I was borrowing and was using nothing in my Nexus 6. At the end of last week, I put my AT&T sim back into the N6 but could not make any calls. I can receive calls but I can't make them from my end. Whenever I try (with Wi-Fi on or off), I get the message "We could not complete your call. Please try again" and it hangs up.
Can anyone think of any reason this is happening or how to fix it? Thanks!
Last July, I switched over to MetroPCS from Verizon with my girlfriend to save money and ever since then, I've had all kinds of problems:
Some numbers can't call or text, and even though I'm now with MetroPCS, the Verizon boot screen is still there along with a bunch of Verizon apps I can't get rid of. The phone also alerts that the SIM card isn't from Verizon. On top of that, the upper left says "T-Mobile".
I am not able to update to Nougat because of this.
Is there anything I can do to get the update?
I switched from Verizon to Tmobile. I can not get update from verizon by OTA. You need connect your phone to computer, download VZW Software Upgrade Assistant. Then you can update your phone.
Yes, you can not get rid of Verizon boot screen, you can disable some verizon apps, the alert of no verizon sim will be shown each time you reboot the phone. And I believe MetroPCS is using Tmobile network, so displaying Tmobile logo is normal.
xlazerxx said:
Last July, I switched over to MetroPCS from Verizon with my girlfriend to save money and ever since then, I've had all kinds of problems:
Some numbers can't call or text, and even though I'm now with MetroPCS, the Verizon boot screen is still there along with a bunch of Verizon apps I can't get rid of. The phone also alerts that the SIM card isn't from Verizon. On top of that, the upper left says "T-Mobile".
I am not able to update to Nougat because of this.
Is there anything I can do to get the update?
Click to expand...
Click to collapse
That answers my question! I appreciate it!
Been experiencing "invalid SIM" error messages on Google Fi after the Pie update. It seems to happen when trying to connect to Sprint. I've tried removing the SIM, reactivating, factory reset. Nothing works.
Anyone else having this problem? It's happening on both my X4 A-1 and my wife's X4 A-1.
Happened to me. Thought I scratched my SIM when adding an sd card to the phone after upgrading to Pie. I contacted Fi and was sent a new SIM which hasn't fixed the issue. Factory reset and reflashing the upgrade didn't do anything.
Same here, my normal use is sprint...startup of sim is configuration of sprit dm... Get sim icon then searching in cell triangle. Signal info App data shows correct sim data for Sprint tower. After twice would access cell site but never got data connection or cell phone even though signal info app would show connected. Then fail, tried to access us cellular but complete sim failure. Removed sim returned to my "daily" Pixel working normally. I guess a push update in the future for us Fi base...have read this happening on first devices that went to Pie way back in August..... Our great android ONE .....
Different waters, same boat
I'm having the exact same issue. Wish I would have waited to take the update.
Same problem here. Restart doesn't help...tried all suggestions on the web using repair codes...only thing left to try is factory reset but have read that doesn't fix it(anybody here tried?).
Sent from my SM-T350 using Tapatalk
Google is aware of this problem and said they're working on a fix.
dgt02 said:
Google is aware of this problem and said they're working on a fix.
Click to expand...
Click to collapse
In troubleshooting I am now getting the same error using my Moto X4 Amazon prime version on 8.1. I was playing around with the various repair codes to understand how they would react compared to my wifes Moto X4 Android One 9.0. I started to get invalid sim error after repairing on Sprint. Now I get the same errors on both 8.1 and 9.0 (invalid sim switching to Sprint). Looks like the problem is a little deeper and more complex than just the Pie upgrade.
At least both still work on Tmobile (the strongest carrier locally). Anxiously awaiting a fix.
A friend at work told me today he saw the invalid sim message and he is a regular Sprint customer so I agree this seems to be a Sprint issue.
It's not just X4A1 models. Regular X4 also. However, my X4A1 was purchased from Google. Quite a disappointing intro to Fi.
I bought 3 Moto X4s for my wife & kids directly from Google Fi. Kids are on Oreo & the wife is on Pie. All 3 phones get the dreaded Invalid SIM error when switching to Sprint. Now, every now and then, I can force connect to an "Unknown Carrier" with Mobile Network Code (MNC) 310-000 (Sprint is 310-120 & T-Mobile is 310-260). When connected to MNC 310-000, I got speeds of up to 74Mbps (I triple checked that wifi was off!). I believe that Sprint is doing network upgrades & for some reason the Moto X4 phones can connect to their test network but not their live network. Anyone else have any insights?
My Fi Moto X4 is Pie same thing. I also have US Cellular in this area and I can if Forced, connect to US Cell but oddly will always revert to T-Mobile. T-Mobile is zero most of the time but will never just try the other two in my coverage area. On Sprint will sim lock, which in the end is which of course locks it up.
I have 2 Pixels (first) Nov, Dec google factory images when were released I found same thing, but a 50-50 to get Sprint to show sprint dm services and complete....registering to specific tower coverage+sim + imei? When working on Sprint would always switch to T-Mobile. Now in the good old days would never go to T-Mobile, Sprint was preferred, then US Cellular, then if found any signal T-Mobile. Jan Images work so far with NO SIM LOCK. I can on my Pixel use a radio.img from Oct 18 and will work like the past on Dec images. So........waiting for "monthly" two months later updates, I guess.
it looks like it has the right frequencies to operate on Verizon, and it will initially connect to the network on boot, but then drops off.
Any ideas here?
Hi - Mine arrived over the weekend and I put in my Verizon 5G sim card and i was able to connect to verizon data network. All things data worked.
But I can't place or receive calls as volte isn't working (my account has volte active). I don't have 5G where I live - so I'm on the LTE network.
I opened a support case with Asus this morning - they said to wait 24 to 48 hours for their engineers to review it. They originally told me to call Verizon, which Verizon told me they can't help. Verizon said Asus has to work with them to get the phone certified. I'm not sure what to do at this point except wait for Asus to reply. I will be returning it if they don't get it sorted out very quickly.
Out of the box I had data only without ability to make calls. After rooting the the phone and installing LineageOS I was able to make calls and and operate the phone on Verizon network without any issues.
noesi5 said:
Out of the box I had data only without ability to make calls. After rooting the the phone and installing LineageOS I was able to make calls and and operate the phone on Verizon network without any issues.
Click to expand...
Click to collapse
Can anyone confirm this? And if so, why does LineageOS work, but not the default ROM?
briank6932 said:
Can anyone confirm this? And if so, why does LineageOS work, but not the default ROM?
Click to expand...
Click to collapse
I just tried it and it depends. I had the exact same symptoms:
- Data worked fine
- Texts works fine
- Calls didn't work at all
And I installed lineage 19 and then everything is normal and great. No idea why though.
EDIT: I installed lineage 19, staxisos, omnirom and all had this problem:
- Data fine, calls, fine, texts could send
- Couldn't receive texts.
After the level 2 verizon tech told me the phone was a loss I returned it. Now after doing a ton more research I found out that it might be because I simply took the sim from my old pixel 4 and popped it in. It seems you need a new sim card or you need to somehow have your line switched to be "cdma-less". Looking at these articles:
r/verizon
r/SonyXperia
OnePlus community
The guide presented on the oneplus community gives me hope I could still use this phone with verizon, but it appears to be a daunting task. If anyone has navigated the customer service and succeeded with this specific phone, I might rebuy it.