Related
After I picked up the MDA I noticed that occasionally, while attempting an EDGE connection, the radio would appear to reset. Signal bars would disappear and the dots under the antenna would appear. The data connection would never take place and as far as I could tell the radio reset. This occurred several times in the course of a day. So did a hard reset on the phone which I hadn't done since picking it up. Now the symptom appears to have changed. Instead of it appearing to reset, it appears to "stick". Indicated signal strength never changes, the data connection is never actually made and eventually I turn the radio off and back on again via flight mode. Again, this only seems to happen while attempting a data connection, either EDGE or GPRS.
I've written Tmo support but I'm curious if this has happened to anyone else or if it may be a problem with my specific phone. And never having had a problem like this before, should I take the phone back to the store and ask for a replacement or do I need to hear that from Tmo?
Thanks!
I have a Cingular 8125 on TMO network and have the basically the same problem. GPRS/EDGE would occasionally stop working. Once it begins to "hang", I would notice the radio icon lose the bars and the dots would appear. However, It would reset on its own after a minute or two. This happens a number of times a day. Annoying the crap outta me.
The MDA ships with an older version of the radio rom. Maybe it would help if you updated it.
kamskii said:
I have a Cingular 8125 on TMO network and have the basically the same problem. GPRS/EDGE would occasionally stop working. Once it begins to "hang", I would notice the radio icon lose the bars and the dots would appear. However, It would reset on its own after a minute or two. This happens a number of times a day. Annoying the crap outta me.
Click to expand...
Click to collapse
yeah, that's the one. I'll see what Tmo has to say, I'm sure as hell not flashing a phone that's days old and well within the warranty period. In the off chance it's software, I did another hard reset and prevented it from installing the extrom stuff.
update: Customer support asked me to try another SIM, which I did. When that didn't help, they told me to bring it back and they'd give me another one. Hopefully that'll be the end of it.
hi,
have the same problem. I just "loose" the signal and it searches, searches .... and again. SR or flight mode on/off usually helps. but its really getting annoying. I have feeling it is in places where there is a weak signal (but just opinio, not a proven fact). Sometimes happens, sometimes not at all. Dont know what to do about it.
I've noticed the same with the Cingular 8125 on Cingular's network. The radio version is 1.09.11. I am wondering if the later radio version would make a difference?
exchguy said:
I've noticed the same with the Cingular 8125 on Cingular's network. The radio version is 1.09.11. I am wondering if the later radio version would make a difference?
Click to expand...
Click to collapse
I upgraded the Radio rom on my 8125 to 1.13.10. I *think* it helped, but to be honest, it still happens. I also now, as a habit, turn off GPRS by pressing the red button for 5 seconds. This seems to help a bit too.
It's really a crapshoot. There are times when I can stay connected to GPRS for hours and hours, while other days i would get kicked within minutes. When the 2.8.7.102 rom is officially released, I will load that in hopes of fixing this problem.
I've had this same problem for months no matter device I use. At first I thought it was because I was using non T-mobile branded phones, but since using devices like the T809 as a modem and the MDA I get the same problem, edge/gprs would connect and stop working/hang after while. Most likely its a network issue, and this didn't start happening to me until T-mobile released edge data service. I'm actually a sales rep for tmo and haven't heard anything from tech support.
I've not had it happen with 1.12.10 (I think) - NOT the 1.13 version, but the one before it. Flashed it the other day - perfect since. The stock T-Mo radio ROM did it once in a while, usually in a poor signal area.
Old Problem
This happened on my Treo 600 on T-Mobile. The problem seems to be city-specific, so it happened in Pasadena frequently but not in DC.
hi, i just got the tmobile MDA and everything works perfect, i dont seem to have the problem of the GPRS, the only problem i have is that the sound of the phone is too low. any suggestions?
P.S. whats the website to download updates and softwares for it?
thanks
PETER
Genesis3 said:
I've not had it happen with 1.12.10 (I think) - NOT the 1.13 version, but the one before it. Flashed it the other day - perfect since. The stock T-Mo radio ROM did it once in a while, usually in a poor signal area.
Click to expand...
Click to collapse
Yep, that was my experience exactly, I haven't had a problem even once since flashing 1.12. Thought about trying 1.13 but didn't want to push my luck. The phone seems to be 100% now.
I have a G4 T-mobile Vario (Wizard) that doesn't want to perform any of its "phone" functions. i.e. no calls in/out or text messages etc. The phone itself is on and is showing a full signal but when you try make a call it will start dialing and almost instantaneously hang up again, occasionally with some beeps to imply the call has failed. Has anybody come across anything similar? As far as I know the unit hasn't taken any knocks and all other functions are working okay.
Any help would be appreciated
*Update* Even the GPRS works! I don't understand!
similar problem
im almost having the same problem, mine goes from full bars to zero and back again while the cpu stays at 100% with no signal, yet somehow i can still get edge and connect to the net?
Have you tried flashing to a later radio version, like 2.71? It may solve your problems
ive tried 4 different radio versions.. it seems to me that the software that runs (service?) on the phone at startup that enables it to make voice calls keeps crashing and restarting and ive tried this on 5 different roms too and same result, it usually takes 5 - 10 soft resets, but it pops up and sometimes keeps crashing indefinitely and sometimes it eventually connects.. any ideas?
pyrorob said:
ive tried 4 different radio versions.. it seems to me that the software that runs (service?) on the phone at startup that enables it to make voice calls keeps crashing and restarting and ive tried this on 5 different roms too and same result, it usually takes 5 - 10 soft resets, but it pops up and sometimes keeps crashing indefinitely and sometimes it eventually connects.. any ideas?
Click to expand...
Click to collapse
update: well ive been using the amp rom and for some reason the radios been working perfectly. so maybe thats somethin to try
davidcrowe88 said:
I have a G4 T-mobile Vario (Wizard) that doesn't want to perform any of its "phone" functions. i.e. no calls in/out or text messages etc. The phone itself is on and is showing a full signal but when you try make a call it will start dialing and almost instantaneously hang up again, occasionally with some beeps to imply the call has failed. Has anybody come across anything similar? As far as I know the unit hasn't taken any knocks and all other functions are working okay.
Any help would be appreciated
*Update* Even the GPRS works! I don't understand!
Click to expand...
Click to collapse
phone is blacklisted. imei banned
imei blacklisted?
Hi,
I am having the same problem as the first poster of this thread.
My phone is a T-Mobile Vario
SPL 2.021.0001
IPL 2.021.0001
Radio 02.19.11
Protocol version 4.1.13.09
Rom version 2.21.2.6 WWE
Rom Date 3/9/06
Basically, I have what appears to be full signal strength. I make a phone call and it says "dialing" then immediately says "Call Ended" with a 00.00 time for the call.
If the imei is blacklisted is there any way I can get it un-listed?
Or is there some other fix I can use to get it working?
Regards,
John
What is a Blacklistet IMEI? Is it a stolen Device?
G4 with no phone ability
Hi,
Still have the problem posted in my earlier post.
I have tried to contact T-Mobile here in the UK using the "contact us" page, rang the numbers - nothing!!! Their phone system does not work.
They have a phone number listed where you supposedly can register your phone as lost or stolen so they can blacklist it, but the phone number does not work! If you are on T-Mobile you supposedly can phone them using 150 but that doesn't work either! So I can't phone them to ask if my imei number is on their list and if so how I go about getting it removed.
(I bought the phone off e-bay last week, and guess what? The seller hasn't responded to my e-mails asking if he ever made any phone calls using this phone!)
So at present I have a semi BRICK, the PDA part works perfectly well, just the problem with the phone bit.
If anybody has any ideas about what I could / should do next regarding the phone, I would like to hear them!
Regards,
John
Have you tried flashing to a new ROM? Its unlikely that it will work, but perhaps it will solve your problem.
Several times recently (I'm not sure whether it started after I installed the OTA update or if it happened once before then) I have noticed that my phone says "No service" and doesn't pick up T-Mobile again until I power cycle.
It's not that unusual for me to see 0 bars of signal strength in my house; there are dropouts at various places, and I saw the same thing with AT&T on previous phones, so it's not a T-Mobile or Nexus One issue. The problem is that, once every few days, I will pull out my phone and see 0 bars and "No service" instead of "T-Mobile," and nothing short of a power cycle reestablishes the connection. I've tried going into and out of Airplane mode, with no effect, and I also tried using Settings -> Wireless & networks -> Mobile networks -> Network operators, and it never found any.
Maybe related is that when I try to power cycle after this occurs I have trouble doing so -- a few seconds into the shutdown sequence the circling arrow stops moving, I get some sort of notification "ping" and the trackball lights up, and the phone just sits there for a long time. Eventually it reboots -- whether because whatever it's waiting for times out and it continues the shutdown sequence or whether it's responding to my frustrated poking at various buttons while it's sitting there apparently doing nothing, I don't know.
If it's a hardware issue, it's very intermittent; I always have service after the reboot, and as I said, this only happens once every few days. I'm inclined to think it's a software or configuration problem (I'm using the stock 2.1-update1 firmware). Any thoughts or suggestions? TIA.
It happened again this evening when I had some more time to play around with it, so I have a bit more information about this problem.
When I tried Settings -> Wireless & networks -> Mobile networks -> Network operators, the circular arrow spun for a minute or two and eventually a little pop-up appeared saying, "Error searching for networks" or something like that.
It occurred to me that the SIM card might be bad or have a bad connection, so I installed an app (using wifi -- which, BTW, I had on throughout this whole process) that allows you to copy your contacts onto the SIM card and ran it. That seems not to be the problem, though, since that app could access the SIM card just fine, while I still had no service.
I toggled Airplane mode on and off, but there was still no change. I then again searched for network operators; the circular arrow appeared and stopped, then a couple of seconds later the phone spontaneously rebooted and I have service again.
Anybody have any guesses as to what these symptoms might indicate?
Every so often i got service but I cna't send text messges unless I power cycle. If I try to airplane mode cycle it won't let me get out of the mode.
wow, a bit refreshing knowing that I'm not the only one with this issue.
I'm on T-mobile and within the last week I've had 2 occassions where I looked at my phone and noticed no service, a power cycle caused it to freeze on "powering off" screen and I would have to pull the battery. After it booted it I had full bars again.
Within the last 2 weeks I have had issues where I would not be able to send a text messages until i power cycled.
The last time I had no service was 4 hours ago. I had to pull the battery to power cycle and get service again.
Thanks for the reply. I, also, pulled the battery the first time it hung in the shutdown sequence, but as I said in my first message, since then I have managed to complete the power-down after the hang, either because whatever it was waiting for eventually timed out or because something I did (e.g., holding down the power button for several seconds) overrode the wait. Next time it happens I'll try just waiting to see if it will complete the shutdown on its own.
Just out of curiosity, did you have wifi enabled at the time this happened? Bluetooth? I'm not sure whether it's relevant, but I leave both on all the time.
As for the text message problem, I don't send a lot of texts, so I probably wouldn't have noticed if I were having that problem and can't comment on any correlation.
Oh, and a couple more questions: do you have NetCounter installed? And are you in a location where you sometimes or frequently get 0 bars of signal strength?
wmm said:
Several times recently (I'm not sure whether it started after I installed the OTA update or if it happened once before then) I have noticed that my phone says "No service" and doesn't pick up T-Mobile again until I power cycle.
It's not that unusual for me to see 0 bars of signal strength in my house; there are dropouts at various places, and I saw the same thing with AT&T on previous phones, so it's not a T-Mobile or Nexus One issue. The problem is that, once every few days, I will pull out my phone and see 0 bars and "No service" instead of "T-Mobile," and nothing short of a power cycle reestablishes the connection. I've tried going into and out of Airplane mode, with no effect, and I also tried using Settings -> Wireless & networks -> Mobile networks -> Network operators, and it never found any.
Maybe related is that when I try to power cycle after this occurs I have trouble doing so -- a few seconds into the shutdown sequence the circling arrow stops moving, I get some sort of notification "ping" and the trackball lights up, and the phone just sits there for a long time. Eventually it reboots -- whether because whatever it's waiting for times out and it continues the shutdown sequence or whether it's responding to my frustrated poking at various buttons while it's sitting there apparently doing nothing, I don't know.
If it's a hardware issue, it's very intermittent; I always have service after the reboot, and as I said, this only happens once every few days. I'm inclined to think it's a software or configuration problem (I'm using the stock 2.1-update1 firmware). Any thoughts or suggestions? TIA.
Click to expand...
Click to collapse
I have had similar issues with other phones...
For me it turned out to be an issue with my sim card.
wmm said:
Thanks for the reply. I, also, pulled the battery the first time it hung in the shutdown sequence, but as I said in my first message, since then I have managed to complete the power-down after the hang, either because whatever it was waiting for eventually timed out or because something I did (e.g., holding down the power button for several seconds) overrode the wait. Next time it happens I'll try just waiting to see if it will complete the shutdown on its own.
Just out of curiosity, did you have wifi enabled at the time this happened? Bluetooth? I'm not sure whether it's relevant, but I leave both on all the time.
As for the text message problem, I don't send a lot of texts, so I probably wouldn't have noticed if I were having that problem and can't comment on any correlation.
Click to expand...
Click to collapse
I usually have both bluetooth and Wifi enabled all the time...
Dont have netcounter installed.
Dunno about the SIM card issue, unless its a combo of the N1 and my SIM card, because I swap to using my BB 8900 once in a while and I never have text message or no service issues.
Im experiencing the same problem, I have dropped calls in some spots around town (when changing towers it seems), I drop service when inside my home and cant send texts (until a power cycle), horrible 3G speeds of less than 1MB/S all around town (driving and standing directly under the Tmobile Tower that across the street from the tmobile store).
NONE of this happened with my G1....my 3G speeds always sucked though but were usually around 1.5-2.1MB/S.
Im located in Fredericksburg,VA.
(MY PHONE IS NOT ROOTED AND IS RUNNING THE OTA UPDATE1)
Im pretty sure it was the radio update, cause after i get out of a place where i get no signal at all, and i get to a open place I have to reboot the phone to get signal again
I've been busy for the last six weeks or so and haven't been following N1 news around the net. Has anyone heard of any progress on this issue? It seemed to go away on my phone for a couple of weeks, but it's back with a vengeance: it's happened to me about once a day for the last few days, which is more frequently than any time since I've had the phone, so I'd really like to get this fixed somehow.
Can you take a youtube video of it? the more the better to get Google to fix it.
Also these issues seem to be related over here too http://www.google.com/support/forum/p/android/thread?fid=1cc152dbb797df2f000483d7c88e343e&hl=en
ram130 said:
Can you take a youtube video of it? the more the better to get Google to fix it.
Also these issues seem to be related over here too http://www.google.com/support/forum/p/android/thread?fid=1cc152dbb797df2f000483d7c88e343e&hl=en
Click to expand...
Click to collapse
Thanks for the link. It seems to me that several different problems are collected together there; mine is specifically the one where I go to zero bars (which happens fairly often; I have several dead spots in my house) and it never comes back.
A video of this would be pretty boring to watch; there's really nothing to see. The signal strength shows zero bars with an "x" and the home screen shows "no service." Trying to power off, or going into and out of airplane mode, shows the spinning arrow for a few seconds, then it stops; a few seconds later the screen goes blank; then a half-minute after that the multicolored "X" appears and the phone reboots itself.
No SMS Gateway
I think this is a separate issue for the phone not switching back to a connected state with the service provider. In the case of SMS, I have also noticed that you may have signal but you have no SMS gateway. No idea where it goes or why it does that.
For whatever reason you loose the SMS gateway phone number settings and become unable to send text messages without a reboot. This is evident by visiting:
Phone
dial *#*#4636#*#* (if you happen to mis-dial this start over after clearing the display or it won't work)
Phone information
Under SMSC: press Refresh.
If no number displays (in my case +12063130004) then you have no route for the SMS messages to take. Entering that number and pressing update will fix it but just restart so it can pick it back up from the SIM/Carrier configutation.
XfrostX said:
Im pretty sure it was the radio update, cause after i get out of a place where i get no signal at all, and i get to a open place I have to reboot the phone to get signal again
Click to expand...
Click to collapse
I have this issue sometime in a supermarket here, if I'm in it shopping for a while I loose all signal and have to reboot, also happened with my MyTouch jut didn't have to reboot the phone, but if I'm in there for a quick purchase, it works OK
@wmm, I'm seeing exactly the same issue (zero bars + reboots) and found another guy on the cyanogenmod forum with that problem. Maybe you can add your last_kmsg to this thread, even though you're on stock. http://forum.cyanogenmod.com/index.php?/topic/1599-loss-of-signal-no-reacquisition-issue/
wmm said:
Thanks for the link. It seems to me that several different problems are collected together there; mine is specifically the one where I go to zero bars (which happens fairly often; I have several dead spots in my house) and it never comes back.
A video of this would be pretty boring to watch; there's really nothing to see. The signal strength shows zero bars with an "x" and the home screen shows "no service." Trying to power off, or going into and out of airplane mode, shows the spinning arrow for a few seconds, then it stops; a few seconds later the screen goes blank; then a half-minute after that the multicolored "X" appears and the phone reboots itself.
Click to expand...
Click to collapse
Damn...Lets hope the next OTA fixes this then.
robert-qfh said:
@wmm, I'm seeing exactly the same issue (zero bars + reboots) and found another guy on the cyanogenmod forum with that problem. Maybe you can add your last_kmsg to this thread, even though you're on stock. http://forum.cyanogenmod.com/index.php?/topic/1599-loss-of-signal-no-reacquisition-issue/
Click to expand...
Click to collapse
Yep, that certainly sounds identical to my experience. Next time I have the problem I'll force a crash by toggling airplane mode instead of trying to power off (it seemed from the thread that last_kmsg would not be saved if there is a normal reboot, and indeed I have no last_kmsg from the reboot that resulted from trying to power cycle after the last time I had the problem).
Thanks for the cross-reference.
ram130 said:
Damn...Lets hope the next OTA fixes this then.
Click to expand...
Click to collapse
That would be nice, but I haven't seen any activity on the issue on the Android developers' board. Speaking as a programmer, these intermittent, once-every-few-days kinds of problems are a real pain to debug, so I can't blame people for not wanting to tackle the issue...
I had this issue but fixed it by installing the Radio Rom and OS again from the last update. Has not done it again. Now its a power button issue lol.
Hey dear devs,
so ive got a little problem. Im a flashjunkie and tried all the different firmwares. All eclair firmwares JM1/3/5/8/9 went fine for me and i had no problems, but since the first froyo (JPC) ive tested, ive got a little problem with froyo.
First some things about me and my phone. I live in germany, my provider is o2, and i also bought a brandet o2-phone. The first day i got it, i flashed to JM5 and unbrandet it, but now to my problem:
My phone hangs somtimes and very sporadic (1-2 times a week) normally after longer calls >10 minutes.
But let me explain a little deeper. It first appears with JPC (my first froyo).
Im doing a longer call and when i finish i take the phone of my ear and have a look an the display to end the call. But i cant click the hangup button. The green listener symbol in the upper left corner is there and blinking. The only thing i can do is to press the menu-button to get back to my homescreen. All is working fine then, but i cant do or recieve any calls because the upper-left green listener symbol is still there and blinking.
When i try to go to flightmode the phone normally hangs completely, only a reboot is fixing the problem. I also had the prob one time within a call. I was on the phone and suddenly my partner was gone.. i didnt hear anything and he also didnt hear anything. Same symptoms: green listener symbol blinking, and when trying to switch to flight mode, the phone crashes. Only reboot is working.
This problem appears in ALL froyo firmwares i tested (JPC, JPK, JPM, JPO), and yes a wiped, i cleared all caches, i reflashed all the firmwares, flashed with kies, flashed with odin (with and without repartition). So i did all the stuff we all used to do to get this problem fixed...
I first thought it was a failure of the beta-firwares, but also the JPO has the problem. There is one thing that might have to do with it... I live a little bit outside of the town and in my house i have a low signal. The problem appears in 9 of 10 cases in the house until now. That might be bad luck, because its very sporadic, and normally i do longer calls only when im at home... But it may also be part of the problem, perhaps because my phone wants to change the to another umts-provider, that has a better signal?
I also thougt that it may be a sim-problem, because my sim is about 5 years old. But i ordered a brandnew sim from o2 and yesterday i had the failure again. It only appears after or right in the call.
Has anyone experienced same problems? Or can help me find out what problem i have?
Thx for all answers
Cheers, Donald!
hi!
yes, i can second that! i have exactly the same problem with my o2-germany-provided SGS, even though I unbranded it by applying the scandinavian froyo-beta via registry hack. So far I did not find any solution. Sometimes this even happens during rahter short calls of 10-15 min. Too bad
Yes i can confirm the Problem. I'm with O2 Germany too. First I thought it is a Problem with both party's hanging up the same time. But I couldn't reproduce the problem at will...
So, the only thing, we can do at the moment is to wait for official o2 brandet firmware. Does anyone know when it will be released?
Greetz DN
Until now i haven't heard about a release date...
also on jf3!!!
i've got the same problem! but i had this bug already on stock eclair jf3!
so i updated via kies to official jpo ( i also tried jpc, jpm, jp6) and my phone still hangs sometimes. is it possible thats just a strange behavior on sgs with o2 germany?
or is there anybody else (other country or carrier) getting the same issues?
i get this bug every third call (when calling longer than 30 minutes)
....
hmm.. perhaps we found something that causes this o2-bug... There is a discussion in the german forum android-hilfe and there is mentioned that the homezone-indicator signal might be the failure, that you might have enabled.
So what about you? Have you also enabled this feature?
Today i called the O2 hot line and they told me that O2 did not receive the Froyo update from Samsung yet. So they haven't had a chance to test the Froyo release. That mens we have to wait for Samsung to give the update to German carryers for testing. I mean if they encounter the problem too they will fix it since it is a real annoying bug.
Look also at this boards and threads about the same issue:
ht_tp_: / /_ww w._ handy-faq._ de/forum/ samsung_i9000_galaxy_s_forum /174359-probleme_empfang.html (german, translate. google. de may help )
ht_tp_:_//_forum._o2online._de/t5/ Handys-und-Zubeh%C3%B6r/ Galaxy-S-Froyo-o2-WCDMA-massive-Probleme/ m-p/58562#M7640
(remove spaces between first parts of the links, as - unfortunately - I'm not allowed to post links cause of my "newbie" status )
I've got the same issues (hang after/while phonecall, aborted call, no net service and so on..)
Same problem here!
BUT mine locks up every 30 Minutes!
And I use drei.at (Austrian Provider) NOT O2.
So it seems, that its not a specific Problem within O2 only
Andy
happened to me once...but SGS unbranded with O2 sim...
Hey,
i have the same prob. When the phone lies all the night and some1 wants to call me at the next morning i'm not reachable. every morning. 100%
now i installed the i9000xxjm3 modem. lets see if it fix the prob;-)
Greets
logicmann
Hi,
there is finally news on that.
O2 meanwhile confirmed the issue to be connected to the homezone display in the Froyo firmwares.
They propose a solution where they delete the homezone data from the SIM card without affecting the homezone functionality as such. Just the homezone icon will not be displayed anymore.
So the assumption it has something to do with the O2 homezone became true.
Here is the thread (sorry, its German) in the official O2 forum:
http://forum.o2online.de/t5/Geräte-...-o2-WCDMA-massive-Probleme/td-p/45714/page/27
I just wonder if some clever developer here could even remove the homezone icon functionality out of the firmware. I somehow do not trust O2 to come up with their solution quickly enough...
Thanks
Andi
I've had a repeated problem (around 4 times so far) where my phone mobile radio must have died/reset while the phone was on standby with the screen off. When I wake the phone I am presented with the SIM pin code request screen. Usually entering the correct code reserects the phone. However last occurance it refused to accept the correct code so required a reboot to get it to work again.
Anyone else seen this?
I'm on O2 in the UK fyi.
Sent from my Nexus S using XDA App
ok I'll guess the answer myself...
I guess this is related to the random reboots people have been experiencing primarily on calls. I note some people say the phone can reboot while on standby, since I 'had' SIM pin code enabled this was as far as the reboot while on standby was getting. I've removed the pin code request which will mean I guess the phone just completes the reboot without requiring my input.
I'm hoping this is fixed with any update to the reboot during active calls issue that google confirm they have repeated themselves.
I've just had this happen on my Nexus S. What service provider are you with? I'm with Tesco (O2).
I'm O2, 30day rolling contract. Basically I've disabled the SIM Lock now so hopefully until the standby or call (not experienced this one yet) reboots occur the phone will just restart without my intervention required now.
Same here. After connecting the phone to the charger yesterday evening, this morning the SIM Enter PIN screen showed up (like the phone did a reboot overnight).
After checking the system services, I noticed the phone hasn't rebooted, because the services where running for more than 12 hours.
So the SIM Enter PIN screen showed up without reboot. I think a no-signal situation has preceded before this screen showed up (and maybe the GSM module has got a total reset).
This is on Telfort/KPN, The Netherlands.
Interesting ArnoutVos.. these were my original thoughts too since every time I've had the phone next to me and not seen it reboot just present me with the Enter SIM Pin screen. I just naturally assumed I was getting the at standby reboot some people had seen.
I've got the same problem on t-mobile. Probably about 6 times in 2 weeks so far. I've also had it where the signal bars at the top just show grey with a little cross by them and the only thing i can do to sort it is restart the phone.
It also drains the battery like mad whilst in this state.
I also had this 2 times (only had the phone 5 days)
That is, i turn on the screen and i have no signal, I dont think my phone has been restarted, as i dont see the sim pin screen, it has just lost the signal/radio died. And nothing seem to restore the signal, i've tried switching from 2g and back, only thing i found to get the signal back is a restart..
i have had the same problem with the signal dropping out on me all morning. sometimes i can make calls sometimes i cant and sometimes rebooting helps sometimes not. today i had the sim card replaced just to make sure and i thought it helped but it just did it to me again. its really frustrating...
I had the same problem about 10 times during the last week. It seems to correspond with the creation of Radio_dump files in the /sdcard/ dir.
Nexus S, Android 2.3.3 Root
I get the same issue on A1 in Austria, not sure what's causing it, but it is annoying.
Let me give my 2 cents:
Getting this same thing happening all through the various combinations of roms and radio firmware, device is Nexus S 9020T, network is T-Mobile in Croatia.
CM 7 with I9020XXJK8 radio
CM 7.0.2 with I9020XXJK8 radio
Blandroid 2.3.4 with I9020XXJK8 radio
Blandroid 2.3.4 with I9020XXKB1 radio
Sometimes there is no pin input screen, so if I don't notice the little icon in the notification bar I'm completely unavailable to calls and sms's. During the time if the Wifi is on it will continue functioning normally, and radio dumps get created.
Will give newer radio firmwares a try before I start crying in my pillow.
Edit: don't know if it happened with stock android 2.3.3 which came on the device, didn't have it on stock for more than 15 minutes.
Alas and damnations, again mobile network radio fail, this time with
radio I9020XXKB3 and blandroid 2.3.4, so issue still present.
Only fix is reboot, airplane toggle does nothing. Does anyone else in europe experience this with a USA T-mobile version nexus?
Giving I9020XXKD1 a try, still with blandroid now 2.3.4p1. Keeping my fingers crossed!
Well well...seems to be a common pattern, as its happened to me a few times also in the last week. First time ive experienced it also...just over a week.ago. cant remember which rom i was using as i.change quite often. May have been a new 2.3.4 mod or just 2.3.3 im not sure. Not a good thing obviously but not a big issue so far. Hasnt happened again since about 3 or 4 days ago now.
Sent from my Nexus S using XDA App
Such problems can occur when the SIM is disconnected from power or from reset line or has technical difficulties making it reboot.
Power or reset line can be disconnected if you have your connectors inside your Nexus bent. This can be tested by shaking your phone heavily in all directions. Be careful not to drop it. If the Enter SIM or the Enter PIN dialog appears, It's most likely a mechanical defect of your phone.
If the SIM is broken it may be reset itself. You can't really test this. Maybe something appears in the system or radio log. Another way would be to place your SIM in a known-to-work phone. If similar problems occur it's a broken SIM. You should call your provider to send you a new one.
bot47 said:
Such problems can occur when the SIM is disconnected from power or from reset line or has technical difficulties making it reboot.
Power or reset line can be disconnected if you have your connectors inside your Nexus bent. This can be tested by shaking your phone heavily in all directions. Be careful not to drop it. If the Enter SIM or the Enter PIN dialog appears, It's most likely a mechanical defect of your phone.
If the SIM is broken it may be reset itself. You can't really test this. Maybe something appears in the system or radio log. Another way would be to place your SIM in a known-to-work phone. If similar problems occur it's a broken SIM. You should call your provider to send you a new one.
Click to expand...
Click to collapse
Those are some good advices, thank you.
I would rule out bent pins as the cause and also no amount of shaking produces the problem, and the problem happened always when the phone was on the desk (and connected to wifi for what its worth).
However, a broken sim - maybe. I haven't had any problems with it so far in any of the 2 previous phones and I'm careful handling it, but the radio log suggestion is excellent.
I will definitely go through it next time it happens ( its "adb logcat -b radio" so others don't have to search for it)
Does anyone got a solution on this?
I found today about 10 - 15 dump-files located in my SD-Card.
Its probably caused by an App which we all use... but i couldnt figure out which one...
is there a dump-debbuging programm which i can use or something else?
It's kind of interesting
Using a Nexus S in Austria (T-Mobile)
I've "solved" this by disabling the PIN altogether and setting up a script to run when the network is changed to delete any radio dumps:
http://forum.xda-developers.com/showpost.php?p=17114685&postcount=26
It doesn't seem to matter which ROM, radio or kernel I use....I wonder if this is a hardware defect?
sorry to resurrect an old thread, but this is to report that on my sns on pete alfonso's 4.0.3 rom and matrix 14.5 CFS and KF1 + KD1, I still get this problem of the radio dying.
has anyone found a solution?
to be more precise, the mobile network connection (calls and data) randomly dies and the only way to get it back is to restart phone. airplane mode doesn't help.