Related
I'm curious to know if anyone with a non t-mobile g1 experienced the same.
My phone was working fine this morning until it stop being able to register on the network with the above error. The only thing I did with it this morning was to put on a screen protector. I doubt it's related
A reboot in recovery mode and a wipe fixed the network registration issue so I guess some data were corrupted.
Hi.
I have the same problem now. Have tried to hardreset but still No service..
Can you help me??
avastdh said:
Hi.
I have the same problem now. Have tried to hardreset but still No service..
Can you help me??
Click to expand...
Click to collapse
Just get a new sim card
I have the same problem now - but it is extremely frustrating and I have tried, since I first wrote what is below to downgrade - but cupcake will not let me.
I have an unlocked - but also unrooted G1. I use it in Europe and in the US. While in Europe I got the message to upgrade and without thinking I did. Then while in Europe I could no longer use the phone as a phone. The update went fine and I had ‘cupcake’ but any SIM I put in (T-mobile, BASE etc) there was no signal and when I went to do it manually I got the message “your SIM does not allow a connection to this network”
So I did a hard reset, but then I could not get pas the start screen since I had no data connection (but I did seem to have phone connection again.
In a layover in Atlanta I tried again - I was able to log in and set up and all was great and good. I should note that I have an old data plan and use an alternative APN to access data. This worked fine in Atlanata where there is 3g connection.
Back home no win Florida… no phone service - same as in Brussels. same message. Worth noting - there is no T-mobile 3G service where I live.
After thinking about this for a while I am wondering if somehow I did not get the correct or full radio update…
if this is true - do you have any idea how to remedy the situation or how I would know if this is the problem?
I appreciate any help.
I have the same problem, any news about this?
I had this issue randomly about a week ago. Reboots didn't work, and I really didn't want to go through a wipe/re-flash. I called T-Mobile, they had me reboot [after I told them I had already done it] --- they ended up deleting me from the network and reboot my phone again, which apparently re-registered me on their network.
This is on T-Mobile US (SW Ohio to be specific)
Does anyone has any news about that? I was told that this might be a radio issue, so I tried to downgrade my celphone to version 62.33.20.0H_1.22.12.29, (using fw 1.0 too), it worked for some time then suddenly it gave me the same error that my sim card it's does not allow to this network, so I forced, again, to my network and the same message appear, I tried this sim in another celphone and worked, I tried another sim on my G1 and it didn't worked, this celphone was working when I lived in the US, but here in Brazil it's not working just like there.. my guess is that the Radio in other countries has any bug, does anyone here was able to fix that? any further advice?
thanks.
weird, i have this issue tonight on one of my unlocked g1's that would normally be working on ATT.
I'll update this post if/when I find a cure.
ohgood said:
weird, i have this issue tonight on one of my unlocked g1's that would normally be working on ATT.
I'll update this post if/when I find a cure.
Click to expand...
Click to collapse
I've been having the same issue of and on for a couple of months now with a G1 on Dutch T-mobile with dutch T-mobile SIM card, which is odd. Running CM mods so maybe the fact that i'm runnig non stock fw causes this?
I get this problem from time to time. Almost never around town where coverage is good, but when I'm on the road in a lot of places where coverage from any provider is poor this happens, especially if it keeps having to switch back and forth between roaming and not roaming. I even get this on T-Mobile and they are my provider. Usually a reboot fixes it, but not always. I've never had it last more than an hour though.
Try reflashing the radio on your phone. Sometimes this helps solve odd connection issues.
beav_35 said:
Try reflashing the radio on your phone. Sometimes this helps solve odd connection issues.
Click to expand...
Click to collapse
according to my tries, this isn't related at all. i'd like to check in on this thread and see a known fix instead of maybes.
Had the same problem
I had this problem about a month ago, apparently simcards can go bad after a while; I had the same simcard for 5 years and it became unreadable. I went to a t-mobile dealer, bought a new simcard for $20, and I was finally able to get my connection back. It's a bit of an expensive route, but at least I didn't have to replace the entire phone.
xxvtcxx said:
I had this problem about a month ago, apparently simcards can go bad after a while; I had the same simcard for 5 years and it became unreadable. I went to a t-mobile dealer, bought a new simcard for $20, and I was finally able to get my connection back. It's a bit of an expensive route, but at least I didn't have to replace the entire phone.
Click to expand...
Click to collapse
my att sim is 4+ years old, but works fine in all but one phone in question, with the above error. also, I have a brand new tmo sim that throws the same error, only on that one phone- which leads me to believe its not a sim CARD problem at all.
all my phones are unlocked, in case of weird problems with any gsm carrier.
Looking at your sig, is this one of the phones with gnav? Because some of the earlier techniques of installing gnav have resulted in a "no service" signal. If it is one of the phones with gnav, try pushing the old build.prop files back into the phone.
xxvtcxx said:
Looking at your sig, is this one of the phones with gnav? Because some of the earlier techniques of installing gnav have resulted in a "no service" signal. If it is one of the phones with gnav, try pushing the old build.prop files back into the phone.
Click to expand...
Click to collapse
gave it a shot, used the normal build.trout... and same results. surely someone at tmobile is familiar with this problem ?
Same issue.
I am running cyanogenMod-4.2.12.2 with radio v. 2.22.19.26I on a t-mobile mytouch. I will lose service and the phone will not automatically reconnect to the network. When I manually select my network (wind mobile) it sometimes connects fine and sometimes I get a "your sim card does not allow a
connection to this network" error and must reset. I found this thread code.google.com/p/android/issues/detail?id=2845 where dozens of people running all different hardware (G1-hero) and all different software (stock cupcake, cyanogen, etc) all experiencing same problem. It seems this problem is happening regardless of the network (T-mobile, vodafone, orange & wind mobile). The problem seems to be happening through all different variables. Changing sims does not seem to fix it. Anyone have any ideas, this is very frustrating.
I've seen this issue as well, with the new Canadian provider Wind Mobile.
The issue seems to coincide with new towers being added onto the network. There are minor service disruptions that result in the network being temporarily screwed up. Going into and out of airplane mode seems to fix it every time.
Also note: These minor service disruptions do NOT ONLY affect my phone, but others (different brands) as well.
They've gotten better at adding towers without blowing up the whole network. It started out happening a few times every day. In the last week it happened only once.
Funny observation: When this happens, the DATA SERVICE recovers automatically, even though the signal gauge remains in X-no service mode. This part is probably android and/or dream related.
It is related with network
I've started to have the same issue tonight. I've rebooted several times and changed the SIM card with another from another operator but nothing helped.
Then i remembered that since I bring this phone from Belgium to Turkey, the regulations in Turkey requires the phone to be registered with its IMEI number to the telecomunications supreme board.
Altough i had initiated the registration process months ago, i thought that there may have been a problem with the registration, so i checked the boards web page.
It turned out that my IMEI is not registered and this most probably is the reason for the not allowed connection.
Tomorrow i will try to reach the board officials and i hope it solves the issue.
do you know what happened? i having the same issue right now and cant seem to find a way to solve it..
The details:
So I recently acquired my Nexus 4 on the T-Mobile $30 plan, coming from it's brother the Optimus G on Sprint.
It is rooted and running CM11 and I have been using Spare Phone and GrooveIP for VoIP calls with no problems whatsoever. I finally decided to pull the trigger and use the Play Store app to add LTE support since my area supports it. Got that working too so I'm feeling good, but I realized shortly after that I cannot make a VoIP call over data now. WiFi still works perfectly, but on data it will ring and connect but there is no audio sent or received from either party.
I reverted back to my working backup with no luck so I did the adb/fastboot method of returning the phone to the stock image and then rerooting, reinstalling the rom and then testing VoIP over data and still no luck. I then proceeded to reinable LTE and it works again.
So in short, I tried to revert to stock modem and APN settings with no luck, but I am currently on the .98/.33 hybrid modem with the fast.t-mobile apn settings again. Also not sure if something in the *#*#INFO#*#* menu could have messed it up, but that's why I reverted to stock...
The question:
Is there any other reason all of my VoIP apps would stop working over mobile data, but still work on WiFi?
highnoteuser said:
The details:
So I recently acquired my Nexus 4 on the T-Mobile $30 plan, coming from it's brother the Optimus G on Sprint.
It is rooted and running CM11 and I have been using Spare Phone and GrooveIP for VoIP calls with no problems whatsoever. I finally decided to pull the trigger and use the Play Store app to add LTE support since my area supports it. Got that working too so I'm feeling good, but I realized shortly after that I cannot make a VoIP call over data now. WiFi still works perfectly, but on data it will ring and connect but there is no audio sent or received from either party.
I reverted back to my working backup with no luck so I did the adb/fastboot method of returning the phone to the stock image and then rerooting, reinstalling the rom and then testing VoIP over data and still no luck. I then proceeded to reinable LTE and it works again.
So in short, I tried to revert to stock modem and APN settings with no luck, but I am currently on the .98/.33 hybrid modem with the fast.t-mobile apn settings again. Also not sure if something in the *#*#INFO#*#* menu could have messed it up, but that's why I reverted to stock...
The question:
Is there any other reason all of my VoIP apps would stop working over mobile data, but still work on WiFi?
Click to expand...
Click to collapse
A few people including myself have been discussing this issue in the thread I linked below. We haven't really found much out, though it seems that it is T-Mobile at fault when you consider all of the variables. Here is an argument by user Ztone:
"What helped me was arguing that I know five other users who's issue started happening exactly at the same time and only on T Mobile's network. There are only 4 components to this: the phone, groove IP, Google and T Mobile. It cannot be the phone or groove IP if many others are experiencing the same thing at the same time (not to mention the fact that I had wipe the phone and reinstalled everything clean). It can't be Google because then it wouldn't work on wifi. This leaves T Mobile. My Tech troubleshooter from t-mobile had me delete the data from Google IP and restart the phone. While I had the phone off she did something on her end to refresh something on T Mobile's network regarding data coming to my phone, then after I restarted the phone. It still didn't work, then she asked me to try on wifi and then it worked perfectly. That seemed to be the tipping point, when she escalated it to engineering. Whatever that means. But I was told to give it 72 hours. Yeah, I think we need to make some noise to T Mobile."
http://forum.xda-developers.com/nex...30-prepaid-plan-users-thread-t2001290/page322
So did you say when you re-enabled LTE the calls worked again? If so that would be a good temporary fix.
jjflemin said:
A few people including myself have been discussing this issue in the thread I linked below. We haven't really found much out, though it seems that it is T-Mobile at fault when you consider all of the variables. Here is an argument by user Ztone:
"What helped me was arguing that I know five other users who's issue started happening exactly at the same time and only on T Mobile's network. There are only 4 components to this: the phone, groove IP, Google and T Mobile. It cannot be the phone or groove IP if many others are experiencing the same thing at the same time (not to mention the fact that I had wipe the phone and reinstalled everything clean). It can't be Google because then it wouldn't work on wifi. This leaves T Mobile. My Tech troubleshooter from t-mobile had me delete the data from Google IP and restart the phone. While I had the phone off she did something on her end to refresh something on T Mobile's network regarding data coming to my phone, then after I restarted the phone. It still didn't work, then she asked me to try on wifi and then it worked perfectly. That seemed to be the tipping point, when she escalated it to engineering. Whatever that means. But I was told to give it 72 hours. Yeah, I think we need to make some noise to T Mobile."
http://forum.xda-developers.com/nex...30-prepaid-plan-users-thread-t2001290/page322
So did you say when you re-enabled LTE the calls worked again? If so that would be a good temporary fix.
Click to expand...
Click to collapse
Thanks for pointing me to that thread, I'll read up shortly. This all started for me between Saturday night and Sunday morning.
Re-enabling LTE does not fix it. I actually thought that broke it at first, but since reverting to factory settings didn't fix it I figured I might as well continue to enjoy LTE even if VoIP is broken.
highnoteuser said:
Thanks for pointing me to that thread, I'll read up shortly. This all started for me between Saturday night and Sunday morning.
Re-enabling LTE does not fix it. I actually thought that broke it at first, but since reverting to factory settings didn't fix it I figured I might as well continue to enjoy LTE even if VoIP is broken.
Click to expand...
Click to collapse
Yeah, unfortunately we have no solution yet. I'm in the same boat as you. I'm just glad it works over WiFi.
jjflemin said:
Yeah, unfortunately we have no solution yet. I'm in the same boat as you. I'm just glad it works over WiFi.
Click to expand...
Click to collapse
Tonight I'll test Spare Phone on my wife's (my old) Optimus on Sprint. I expect it will work normally and will report back to rule out the app itself since I will be using my same Google account.
highnoteuser said:
Tonight I'll test Spare Phone on my wife's (my old) Optimus on Sprint. I expect it will work normally and will report back to rule out the app itself since I will be using my same Google account.
Click to expand...
Click to collapse
Confirmed that VoIP on data works with Spare Phone and GrooveIP on other networks.
It appears that I am back in business with no change on my part...
I'm in Japan for a couple of weeks for work and signed up for the Japan pack that Sprint offers. I spent almost an entire week working with Sprint support ( ) trying to get data roaming working properly on the phone without much luck (voice and text worked great), but yesterday I lost all connectivity but wifi. Figuring I must have changed something I shouldn't have, I saved everything I could and did a hard reset on the phone.
It still won't connect to any networks. I've re-downloaded PRL and device configs over wifi in the settings but it doesn't even attempt to connect to any wireless networks, or see any for that matter.
I have 2 guesses here but I'd like some kind of confirmation here before I take any action.
1: Maybe my radio firmware is corrupted somehow? I'm not exactly sure how to check it but it just doesn't seem to be doing much of anything. In the SIM status page it says searching for network, but I have no way to know if that's really the case.
2: Since the phone has a Sprint SIM, does it has to be on an actual Sprint network to initialize the networks? (Not Softbank's network here in Japan?) I spent over an hour on Google Voice with them last night trying to get an answer/help but got absolutely nowhere.
The phone is currently all stock but I have no problem unlocking and installing recoveries/software/roms if need be. Any ideas what I can do here or am I just stuck without communication until I get home next week?
Usually the best route is to get a local prepaid sim while traveling but honestly I have no idea what sprint offers for roaming in Japan. Check your plan and see if there is an add on needed.
I'm not alone!
Also THIS IS STILL AN ISSUE!
It worked fine for me last time I came to Japan, about a year ago. This time, I only have voice and text, no data. Right now I'm backing everything up to do a factory reset.
Did you ever find a solution to this?
I'm not sure if you've already done your factory reset, but if you're on Sprint, don't do a reset. The phone can't reactivate itself off of Sprint towers. You have to be in the US when you do the reset. I was stuck with WiFi only for most of my time there because I reset mine.
I never found a solution other than dropping Sprint when I got back to the states. Switched to Verizon and never looked back, though I'm not sure what I'm going to do for my next trip with their ridiculous international rates.
I actually got it working last night.
Factory reset and restore over wifi
Update device config over wifi -> handles activation
Update PRL over wifi 3 times
Now it works
Oh, I'm glad it worked. Is yours on Sprint?
Yes, but I may have spoken too soon. It worked for a few hours and now isn't getting back on data. I think it may be SIM related, since I saw a weird SIM error pop up and rebooted my phone, which led to the data working the first time
They must have redone their activation system since I had my issue in July. At that time there was no way for the phone to reactivate without being on Sprint's system.
As far as the data, that's the same thing I had happen and they were never able to solve the problem. It would work for a little while then stop for no reason. If you find a solution I'd love to hear it though.
I'm wondering if I can flash a different radio or something
Hello everyone,
I just bought a Moto G4 16 GB with Amazon Ads for my wife, but we are facing a very annoying problem: the carrier signal always dies after 24 hours give or take. We tested with a different SIM card and the same thing happened. When this happens the device only shows "Emergency Calls Only" and we have to reboot the phone in order to get the signal back.
So, is anyone else facing this problem? Is this really a problem with this phone in particular or every moto g4 has this problem? Should I return the device to amazon?
Thank you very much for any information you can give me!
Zadornov said:
Hello everyone,
I just bought a Moto G4 16 GB with Amazon Ads for my wife, but we are facing a very annoying problem: the carrier signal always dies after 24 hours give or take. We tested with a different SIM card and the same thing happened. When this happens the device only shows "Emergency Calls Only" and we have to reboot the phone in order to get the signal back.
So, is anyone else facing this problem? Is this really a problem with this phone in particular or every moto g4 has this problem? Should I return the device to amazon?
Thank you very much for any information you can give me!
Click to expand...
Click to collapse
No problems here since I got my phone last week and I have T-Mobile. You might have to check your apn settings with your carrier.
Caltinpla said:
No problems here since I got my phone last week and I have T-Mobile. You might have to check your apn settings with your carrier.
Click to expand...
Click to collapse
I tested the SIM card in a different phone and it worked flawlessly (I also use T-Mobile). The strange thing is that the phone gets the signal very well during more or less one day, after that I have to reboot to get signal again.
Well, this is probably a problem in the device. I already asked Amazon to send a replacement.
Zadornov said:
I tested the SIM card in a different phone and it worked flawlessly (I also use T-Mobile). The strange thing is that the phone gets the signal very well during more or less one day, after that I have to reboot to get signal again.
Well, this is probably a problem in the device. I already asked Amazon to send a replacement.
Click to expand...
Click to collapse
Try my APN settings to see if it helps, but locations very important
Zadornov said:
I tested the SIM card in a different phone and it worked flawlessly (I also use T-Mobile). The strange thing is that the phone gets the signal very well during more or less one day, after that I have to reboot to get signal again.
Well, this is probably a problem in the device. I already asked Amazon to send a replacement.
Click to expand...
Click to collapse
I also have the cellular data always active checked off
Caltinpla said:
Try my APN settings to see if it helps, but locations very important
Click to expand...
Click to collapse
Thank you, but I just use the t-mobile network. In fact, my carrier is called campusSIMs and it is a MVNO that uses t-mobile network. So, my APN configs are a bit different from yours.
However, I didn't know about this mobile data thing. I didn't touch the developer options. Maybe, it can be a good idea.
Thank you!
It won't be your APN settings since that controls your data settings. If the sim is ok then it could be your phone.
Sent from my SM-T530NU using XDA-Developers mobile app
I'm seeing a similar problem with the data portion of the network (also on T-Mobile). While I'm able to send and receive calls and texts, data doesn't work. There's no indication that it's attached to LTE or even 3G (just a standard signal bar with no other information). I moved the SIM card back to the old phone it was in and it works fine.
Things actually worked yesterday, so something happened overnight to break it.
Damaniel said:
I'm seeing a similar problem with the data portion of the network (also on T-Mobile). While I'm able to send and receive calls and texts, data doesn't work. There's no indication that it's attached to LTE or even 3G (just a standard signal bar with no other information). I moved the SIM card back to the old phone it was in and it works fine.
Things actually worked yesterday, so something happened overnight to break it.
Click to expand...
Click to collapse
That could possible be the APN settings. Although usually it's the opposite, they don't work at first then they update from the network later on. Most times the APN settings will set themselves but on the odd occasion they need to manually edited. I don't use T-Mobile but the APN settings are easy enough to find.
Damaniel said:
I'm seeing a similar problem with the data portion of the network (also on T-Mobile). While I'm able to send and receive calls and texts, data doesn't work. There's no indication that it's attached to LTE or even 3G (just a standard signal bar with no other information). I moved the SIM card back to the old phone it was in and it works fine.
Things actually worked yesterday, so something happened overnight to break it.
Click to expand...
Click to collapse
Sounds like you need to manually enter the APN settings. What you describe is exactly what happens when it hasn't loaded an APN.
I'm "kinda" having an issue here. It's a little different though; the phone works ok for a while (for me about 3 hours, usually), and then I still get an LTE indicator, but have no network connection (get errors in apps/"No internet" page in chrome).
Other times, I lose LTE and get locked in 3g (H indicator), and can only get LTE back by going to Settings/More/Cellular Networks/ and toggle preferred network mode to 2g or 3g, let it connect (H or E), then toggle back to LTE.
Motorola responded to a bad Amazon review requesting I post asking for help on their forums.
Relevant link:
https://forums.lenovo.com/t5/Moto-G...ction-with-LTE-and-strong-signal/td-p/3377242
I'm active over on their forums also and it's good to post over there in case you ever want to do a soak test. They look at your posts there when they ask for soak testers. As for your problem, I've seen it shift back and forth if you are in an area between towers and one isn't sending out LTE. If it were that I wouldn't think you'd get it back so easily. There's an app, don't remember the name, that will show the towers and signal relative to your location, If might be interesting to look at that.
Having the same issue with radio. Just replied to your post, Kalash.
Ok, we got a new phone from Amazon and it has the same problem. So, I believe this phone does not work very well with MVNOs.
I notice that the problem is that the phone cannot reconnect to the network after losing the signal. For example, if you go to an area with bad signal and, eventually the signal vanishes, the phone will not be able to reconnect to the carrier network. The phone only reconnects after reboot. Airplane mode does not solve the problem.
This does not happen with my Blu Life One X. So, I think it is a software problem.
Zadornov said:
Ok, we got a new phone from Amazon and it has the same problem. So, I believe this phone does not work very well with MVNOs.
I notice that the problem is that the phone cannot reconnect to the network after losing the signal. For example, if you go to an area with bad signal and, eventually the signal vanishes, the phone will not be able to reconnect to the carrier network. The phone only reconnects after reboot. Airplane mode does not solve the problem.
This does not happen with my Blu Life One X. So, I think it is a software problem.
Click to expand...
Click to collapse
That's not true on all mvnos' apparently. My wife's phone is on Consumer Cellular, an AT&T mvno and it's never done that. We've been in a no service area several times and it's always connected immediately when getting service back.
I'm on T-Mobile network and had an issue two weeks ago where the phone randomly disconnected from the mobile network and stopped recognizing the SIM. T-Mobile store changed the SIM but it made no change so they offered to replace it but after a hard reset it magically worked.
Today I got the same issue and now the phone doesn't connect to the network (or WIFI for that matter). Before I do another hard reset I thought I'd post here to see if anyone else has had the same issue and if there is a suggested fix. I'm pretty stumped on this one.
I'm not rooted but the phone is unlocked through T-Mobile and I received the OnePlus unlock code but haven't done anything with it. Currently on the 10.0.27 build.
whiteblazer01 said:
I'm on T-Mobile network and had an issue two weeks ago where the phone randomly disconnected from the mobile network and stopped recognizing the SIM. T-Mobile store changed the SIM but it made no change so they offered to replace it but after a hard reset it magically worked.
Today I got the same issue and now the phone doesn't connect to the network (or WIFI for that matter). Before I do another hard reset I thought I'd post here to see if anyone else has had the same issue and if there is a suggested fix. I'm pretty stumped on this one.
I'm not rooted but the phone is unlocked through T-Mobile and I received the OnePlus unlock code but haven't done anything with it. Currently on the 10.0.27 build.
Click to expand...
Click to collapse
Were you on 10.025 build when it first started? If it's happening with multiple phones on multiple software versions,it makes me wonder if you need to file a ticket with T-Mobile on your line. If the Wi-Fi issue is happening only on the newer firmware, it could be the Wi-Fi was a coincidence and that there is something wrong with your network settings on T-Mobile'a side.
10.0.27 could have a Wi-Fi bug, as I'm hearing a few reports to this happening to a few people. But the mobile data side suggests something happening outside of your phone.
I know it's kind of a long shot, but it's what would make sense overall if this is happening on your replacement phone as well.
I don't recall if I was on 10.025 when it first happened, though I want to say I wasn't as I don't believe I have done any updates since it happened. I don't know why the WIFI is also happening, but bluetooth still works just fine (I didn't mention that in the beginning). When I try to select the "SIM & Network" menu in Settings it seems to freeze. If I file a ticket with T-Mobile I believe they would simply want to replace my phone entirely (that's what they were working on the last time I brought this issue to their attention). Just a point of clarification, I'm still using the original phone and having the issue a second time, when a full hard reset (with erasing personal data) seemed to resolve the problem, at least temporarily.
It sucks because I could just reset the phone again and probably fix it but it's a pain to continually restore all the settings, apps, and settings within each app. I could also replace the phone but then I will be getting a locked phone and will have to go through the unlock process again (which I could do, it wasn't all that bad).