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..
I was thinking of posting this in the general section but posting it here seemed more appropriate as I think the issue at hand is of a more technical nature. If this is not the case I apologize in advance.
I recently purchased a Black HTC Magic (Rogers branding) for use on the AT&T network here in the states. Since then I have had a very difficult time initiating calls while connected via 3G (UMTS/HSDPA). Even in high or low signal situations.
Unfortunately there doesn't seem to be any consistency to my ability to make a call while on 3G. At times 5/5 calls would be successful and other times 1/5 calls are successful (the latter being true more often than not).
Suspecting there was some issue with my device being on 3G I forced my device to use 2G (EDGE) connections only. At which point my reliability issues go away completely (from what I can tell).
I don't experience any strange issues with using my data connection while on 3G/2G so it seems to be specific to voice.
Another interesting thing to note is while trying to initiate a call with the Google Voice application on 3G, I experience the same call initiation issues as mentioned above. Google Voice works as expected while on 2G.
I experience these issues on the original shipping Roger's ROM, as well as all the other 3rd party ROMS (HoFo, Cyanogen, etc...)
Here is information about my device from fastboot...
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP50000)
CPLD-12
RADIO-3.22.20.17
Apr 20 2009, 15:30:43
Is it possible that my SIM card may be causing issues?
Anyone else with a North American Magic experiencing issues on AT&T? I appreciate any help you guys could provide.
your phone is ok
perhaps you might have heard... iphone great phone...AT&T absolute **** network
with dropped calls, and constant diverts to voice mail. dont sweat it. its AT&T not
your mobile.
I would have to agree that it's probably the network, although I might be wrong. I also have a Rogers Magic running on AT&T in Arizona, and I have this issue as well, but not nearly as frequently as you do. This same problem used to happen from time to time with my HTC Fuze and my BlackBerry Curve.
I've had a variety of different devices on the AT&T network (Northeast/Washington, D.C) and although yes I have experienced AT&T's wonderful network. What I'm experiencing just doesn't seem right. Makes me wonder if it's my SIM or particular build....
your phone is ok
perhaps you might have heard... iphone great phone...AT&T absolute **** network
with dropped calls, and constant diverts to voice mail. dont sweat it. its AT&T not
your mobile.
MOD EDIT
Moved into general discussion forum as not related to android development
if you are not using a newer sim card i would start by changing that. i was using an older 3g sim which i have used with many phones and i found that by changing to a brand new sim the few connectivity issues i had have gone away
which ROM?
Just a question, but which ROM is everyone here using? I, too, experience the random inability to make phone calls over HSDPA. I was told by an at&t rep in-store today that the Rogers Magic does not 'show up' in their system as 3g capable. Pure bs is what I think, but lets rule out software, yes?
If it is not your sim card then it is most likely your network.
Calls over 3G/HSDPA is fine on my Magic and was also fine on my Nokia N79 using the same Cingular SIM card that I have. However, making outgoing Google Voice calls over 3G/HSDPA is a no go.
Yeah...making calls was fine on my Unlocked Touch Diamond, too...but it's NOT on the Magic (32a).
SO...I'd just have to guess that it's *probably* not the SIM card.
I was told (via an exceptionally helpful phone rep) that the "voice 3g" in my area is not very good, but that the "data 3g" is much better. Which (she says) is why I have trouble making phone calls, but that data works fine.
I don't think so...but without *that* answer, I'm left with the AT&T stock "well, we don't support *unlocked* phones, sir, we can't guarantee that they'll work with our network".
ARRRRRGH! REALLY?! SO, phones with the same chipset, using the same technology won't have the same results?
PLEASE, FCC, INVESTIGATE THIS B.S!
Hey radikaled, I have some new developments with GV and outgoing calls. If I set the GV call options to "ask for each call" the issue of calling over 3G appears to be alleviated somewhat. Basically, when initiating a call, you will be prompted on whether you'd like to make the call via GV or not. At this point, wait a few seconds at this prompt and then choose GV. So far the call has successfully connected 100% of the time.
It appears that the data connection is too slow to establish fully over 3G, therefore, the call fails if you don't wait the few seconds before choosing to call via GV.
Let me know if this works for you.
I too had issues with my ROgers Magic unlocked on ATT. When I first got it I used the original ROM and then the HoFo ROM. Both had similar issues with dropping calls when switching from EDGE to 3G and back. I also dropped more calls than normal.
I recently switched to Cyanogens ROM and new radio. I have not had any issues since and then. Calls and switching is very stable. Also the clarity and volume is also much better. Just my experience. Very pleased with this phone on ATT now.
awtryau89 said:
I too had issues with my ROgers Magic unlocked on ATT. When I first got it I used the original ROM and then the HoFo ROM. Both had similar issues with dropping calls when switching from EDGE to 3G and back. I also dropped more calls than normal.
I recently switched to Cyanogens ROM and new radio. I have not had any issues since and then. Calls and switching is very stable. Also the clarity and volume is also much better. Just my experience. Very pleased with this phone on ATT now.
Click to expand...
Click to collapse
Thanks for sharing your experience. May give CM ROM a shot.
Good read.
Nice post. Interesting topic.
I tried to send several other users your way...I'm sure they eventually checked this out. I've come across this issue with some other folks recently too.
Best of luck though.
Me TOO!
I also have a similar problem. When connected with HSDPA, about one third of the calls I make fail immediately, even with full signal strength. I then wait a few seconds and dial again, and it works. I actually am using the sim card from a previous nokia POS phone I had from two years ago; the ATT people just took it out of the previous crap phone and put it into my poor fuze. How much does a new SIM card cost? Can I get a new SIM card without att bothering me about not having the stock rom? I'm using Da_G's clean fuze 23008 winmo 6.5 with the 1.12.25.19 radio. I live in the Youngstown, Ohio area (between cleveland and pittsburgh), so cell reception on any network is pretty bad, but it seems the ATT/cingular network around here is particularily bad. Any ideas?
I have 2 X10's on my person.
The first being perfect, and does what it should do, minus bluetooth hf car kit...
The second is also new, but a certain network dont want it back, so am eager to say the least to make it work for wifey.
Right, it does this.....
You switch on, it boots up with a sim card, but hangs an X in the signal area... for a while too... Then it finds 3G and works... but it drops to GPRS and even though theres signal, does it hell as like. No calls, texts or data. Then it X's for 2 mins. Finds 3G and works, drops to GPRS and so on...
Lots of spares, but is this a quick fix? I want it to work for the wife see...
sad lol
Have you tried to do a repair using SEUS? Might help sort out the radio issues.
from my experience that is a sim issue, how old is the sim you were using in it, if it is a 2G sim then you will experience the above, try setting it to GSM only to test it. If that is the problem then a simple new sim will fix it. We have it a lot with people who dont upgrade there sim with a new handset.
I'm on my second x10 and its fine. I tried my daughters sim and that did it too. Have also tried reloading firmware too,,, no go.
Sent from my X10i using XDA App
I had a problem almost similar to this when I just got my X10. What I noticed was the Auto Internet button was grayed out, so I put in my providers internet setting manually. But the signal keeps coming in and out. Then I decided to update the software to UK Generic and after that, I did not encounter this problem anymore. The Auto Internet button was not grayed out anymore after the update to UK Generic R2BA026...
Hi, i was using CM7 for a week, then suddenly, the mobile network begin to be freaky, cant stay on a network, cant make call and anything, I already cheked the apn settings and everything..
also switched to wcdma prefferred, to gsm only, or to wcdma sometime got signal, but after 1 or 2 minutes, cant connect to a network...
anyone can help please..
I'm having this as well ever since the update.
Gingerbread is half-baked if you ask me.
it seems to make and receive calls only in EDGE (in GSM ONLY mode), but when i change it to preferred wcdma or to wcdma only to get 3G, sometime get full signal but cant make any calls and also cant use data and sometimes got no service.. only in EDGE mode..
all this happen after using CM7 for a week... anyone please help..
baseband and radio are 32.50.0032U_5.12.00.08...
I also restore it to stock to FROYO FRF33 and the same issue, dont know what cause it..
I'm not sure it is fully related to gingerbread. I'm still using CM6 and had this issue on and off for about 3 days. It seems to have cleared up for me (knock on wood)
Sent from my Nexus One using XDA App
yess im having the same problem, i also noticed it after flashing to either honeycomb alpha or the new gingerbread update [i did both within an hour] but i cant fix this problem...:/
still cant connect to 3G, only in EDGE mode...
cant connect to a 3G network, already changed the radio to 5.08, 5.12 and downgrade it to 4.06 and nothing...
anyone know this issue??
if I cant solve it, I might gonna sell my Nexus One..,
Network issues have nothing to do with the phone, if they're constant with different ROMs. Check with your service provider.
Jack_R1 said:
Network issues have nothing to do with the phone, if they're constant with different ROMs. Check with your service provider.
Click to expand...
Click to collapse
is not the service provider, I change the sim card to another phone, and the 3G works flawless.
Also, put another sim of other carries with the same band, changed the APN settings, and it's the same problem with 3G, only work on 2G...
In that case, 2 options:
1) Wipe and check again.
If still doesn't work -
2) Hardware failure. Use the warranty.
I've been recently (1-2 months) battling with Data problems also and I don't know what the issue is. I know it isn't my Carrier because I just spent the whole month on the phone with them and they actually sent a Guy TO MY HOUSE to test the connection. I've never had problems before until around CM7 and me switching plans (which is what I thought it was).
My problem is that it works, but data just stops and doesn't want to reconnect. I have to toggle Airplane mode or reset to jump start it. I think changing towers while driving might do this too.
I've done the same tests. Changed Sim, Swapped Sims, etc. EDGE seems to be stable for me but 3G is wonky. I've flashed a PASSIMG and started from scratch that way back to root and CM7. I've downgraded my HBoot and reupgraded it. I've wiped and changed radio versions.
Right now I plan to swap to a few other Gingerbread roms and see if that fixes it. My N1 being my only internet connection it is hard to download other custom roms but I grabbed a few from work and put on my SD card.
I'm not blaming CM7 but at this point I'm really thinking about changing phones.
Ive read that there are issues with the Nexus One gps. Is this true and if so, what issues have you experienced?
PS. GPS doesnt have anything to do with the carrier does it?
well... my nexus already have 1 year, I'll sell it in a very cheap price, and buy the INSPIRE 4G and root it...
thx for your help guys..
I'm having a problem with my 3g connection since I flashed a new ROM.
I'm not sure if this is related to the fact that I'm using an unlocked Defy on AT&T. I won this phone a year ago, and I've been using it unlocked on AT&T since March with no problem.
I'm new to modding, but OCD about streamlining my electronics. My friend suggested rooting my device and flashing a new ROM. I decided on stock Nordic Froyo, and it makes me so happy not to see all the T-mobile crap in my apps tray. BUT the collateral damage is not so hot. I have no 3g or even 2g connection anymore.
I tried the fix in this thread http:// forum.xda-developers.com/showthread.php?t=944258 and was able to get a signal with 4 bars instead of the previous state of emergency calls only, but no letters like E or 3g and no ability to use the internet/transfer data. I also installed the broadband switcher in this thread http://forum.xda-developers.com/show....php?t=1052745 and tried all of the T-mobile US bands. No luck. I did reset the APN to default. No change. I've been using wifi, but will have to go back to work soon. Not having access to the smart part of my smartphone will feel sort of like having an arm cut off.
I'm not sure what to do next. I could try flashing another ROM, but from what I've read in the forums, that's no guarantee. If anyone has any suggestions to help a noob, I'd be forever grateful.
(And yes, I did first post this as a reply to another AT&T thread, but I think my problem is different than that OP's issue.)
Thanks in advance!
did u try the international baseband..
I just did. Same issue.
I've also tried the Argentine and Central American basebands. No luck. AT&T broadcasts 850/1900 while T-Mobile does 850/1700/2100, but 850 worked fine for the last 10 months. I don't get why things would fall apart now.
UPDATE: I was able to fix the problem by manually entering APN info. Am running on H now.