My 6p has worked well for some time, but for a while now it will just constantly drop carrier signal, it seems to do it more when an app is sending or receiving data. I thought maybe it was purenexus or the ex kernel, so I updated both to the current releases, there are no other mods besides root. I've never ran stock on it and the issue just started out of nowhere one day. It will usually pickup signal when it drops. Sometimes to speed it along I'll put it in airplane and then back. Sometimes that doesn't work and a reboot is needed. It's also on the latest vendor image because AFAIK that includes the modem radio. I'm kinda out of ideas, I'd like to avoid dealing with the carrier if I don't need to (t-mobile us)
Also, when on WiFi I noticed that cellular never seems to drop.
Having the same problem. It started recently and I'm not sure why. I'm on Cricket.
gr546jmn5 said:
My 6p has worked well for some time, but for a while now it will just constantly drop carrier signal, it seems to do it more when an app is sending or receiving data. I thought maybe it was purenexus or the ex kernel, so I updated both to the current releases, there are no other mods besides root. I've never ran stock on it and the issue just started out of nowhere one day. It will usually pickup signal when it drops. Sometimes to speed it along I'll put it in airplane and then back. Sometimes that doesn't work and a reboot is needed. It's also on the latest vendor image because AFAIK that includes the modem radio. I'm kinda out of ideas, I'd like to avoid dealing with the carrier if I don't need to (t-mobile us) Also, when on WiFi I noticed that cellular never seems to drop.
Click to expand...
Click to collapse
Several threads on the same dropping, cycling, having to reboot issue affecting T-Mo. Fairly new one here. You can also find a huge whinge fest thread here where every T-Mo user has tried every radio going back a year. If I were affected, I would make sure the issue was present on a bone stock device, then I would find a friend/relative and switch to a different carrier SIM, preferably a non-MVNO to see if it was resolved. It shouldn't take more than a few hours. At that point you're going to know whether it is your carrier or your device. If it is the carrier, provide them this information and ask for new SIM to be provisioned. They should also be able to look up your usage history and maybe find a solution for you. The beauty of owning a carrier unlocked phone is you can always get another carrier. If all this tells you it is a hardware issue, then you have already collected the evidence needed for a warranty claim.
Related
Any of you guys experiencing **** signal now? I sit in my room and i can't even get calls anymore. It show's it has service but i get no calls coming through. Sometimes i just get no service, whereas before the update I always got service here.. Also, after school where i barely get service inside, and i go outside i have to reboot the phone to get signal again.. wtf?
Any fixes?
Unfortunately, I'm getting the same experience. Already filed a ticket with T-Mo...they're going to look into it. This is ridiculous.
+1
Gotta agree with you here. I've noticed my phone spending more time with a big fat 'G' in the bar then the '3G'. Not very happy about it and wish I could just flash the original stock ROM back.
Where do u file a ticket
No problems here in the UK. Maybe its related to the 1700Mhz frequency. Is it the same in both 2g and 3g? compared to the same before in 2g and 3g of course.
My signal is just fine after the OTA... actually, get 1 more bar at my Dad's than I did before... his house is my true testing grounds since it is an old house with metal in the exterior walls at a low point on top of a hill... nobody gets coverage at his place minus 1-2 bars by the door, and 2-3 outside.
With my G1 I got 0-2 in the house, and my N1 gets 1-3 depending on where I am at. Better than any phone I have ever tested there, including BB's, WM's, and plain Janes.
do you have any custom radio settings or anything?
Same problem here. Really getting pissed off now.
Same here, posted about it earlier... I emailed google, no word yet!
since the update im always on 3g / H
one more note, I have never dropped a call on my BB's in the past and it happens all the time on my N1... if the damn screen wasnt so pretty I'd say f it!
I'm having the same issues but I am using AT&T. Even though I have full bars on Edge, I can't make nor receive calls or texts more often than before.
No issues after the ota, and still getting 3G/H 4bars most of the time. One wierd thing after the ota, is when I run speedtest, the nearest Server it locks on is 1,586 miles away It use to be in Las Vegas hood!
No decrease in network connectivity here... I'm actually seeing better 3G connectivity than before the update.
same here... and wouldnt you think full edge would mean 3g service? the radio in this phone is all f'd up
What method did you guys use to update? Did you remove the battery at all during the update, or did you let it go until it rebooted on its own?
Maybe try reflashing the update manually, really easy to do with or with out an unlocked boatloader and root. I am thinking you might have a bad flashing of the radio ROM or incomplete update. The radio ROM update has done wonders for so many, and was heavily tested for a couple weeks by Google, so I highly doubt it would be a step backwards... only way I could see the update itself being the 'root' of the problem is if it isn't compatiable with the broadcast radios being used in your area on the towers.
my nexus is MUCH better after the update. MUCH BETTER.
I did it manually step for step it went along with the directions and discription
pjcforpres said:
What method did you guys use to update? Did you remove the battery at all during the update, or did you let it go until it rebooted on its own?
Maybe try reflashing the update manually, really easy to do with or with out an unlocked boatloader and root. I am thinking you might have a bad flashing of the radio ROM or incomplete update. The radio ROM update has done wonders for so many, and was heavily tested for a couple weeks by Google, so I highly doubt it would be a step backwards... only way I could see the update itself being the 'root' of the problem is if it isn't compatiable with the broadcast radios being used in your area on the towers.
Click to expand...
Click to collapse
How do i Manually re apply the update ? My phone is NOT rooted and the bootloader is LOCKED. please advise
XfrostX said:
How do i Manually re apply the update ? My phone is NOT rooted and the bootloader is LOCKED. please advise
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=627823
Does a better job than I could/would.
Please, somebody tell me there's hope. 2 really annoying & disappointing things are happening. My bluetooth keeps randomly disconnecting, and to make matters worse the status bar icon still shows it is connected, but it's not. Second, I am dropping calls almost daily, and I'm mostly in places where 2 seconds before the drop I had 4 bars!!! I went to a store today & got a replacement SIM (50.01 vs. 39.01 markings) hoping that might solve it, not happening. And the signal strength almost never shows less than -105 dBm, sometimes -97. I NEVER had a dropped call or any bluetotth issues with either my old trusty G1 or the MT3G I just came from. I'm really trying to love the phone, it has so many positives. But the fact that it's a "phone" and it's basic function is skewered is pissing me off big time. Please, someone tell me I ain't the only one experiencing these issues, and, that either the OTA FroYo or Cyan's first ROM is gonna fix 'em? Better yet, any known fixes now? Are these issues in any way related to the data issues, possibly? When I called Tech Support last night they said to try a hard reset, but I really don't want to do so, unless I can flash one of the stock/de-TW'ed "stock" ROM's written about in the Dev. threads. Anyone have any concrete suggestions or explanations? Thanks...
Summary of baseband bugs in Nexus s
1) Having network selection set to manual ( i.e selecting 302490) will result in No Service on a reboot.
Solutions:
- Have to cycle airplane mode to get it to pick up service (can be done with automatically tasker)
- OR Use automatic network selection. (you can force wcdma only but that will reset the SMSC which is annoying if you go in and out of wind away/home areas and you want to roam.)
2) Being in a area with no service for extended periods of time 5+minutes(subway, basement, etc) will result in a dead baseband, meaning once you come into an area with service the phone will not reacquire signal, airplane mode will not work as the baseband is now crashed, cant maunally search for a network. Have to reboot to get signal.
Solutions:
-Use tasker to cycle airplane mode on and off when in no service areas i.e) search signal 4 minutes, airplane mode on 10 minutes. This will keep the baseband from crashing and possibly save battery.
-Use NoBars to accomplish the same thing ( tasker gives you a bit more flexibilty of course but harder to use) http://www.appbrain.com/app/nobars-battery-saver/com.tomdryer.nobars
- Use airplane edit to avoid turning wifi/bt off when airplane mode is on. http://www.appbrain.com/app/airplane-edit/net.cenkalti.airplane
3) WCDMA perferred does not work.
- No solution.
These are all software bugs/baseband so hopefully they will be resolved soon by google. Voice your concern on the google mobile forum though. These are reproducible on stock, and any ROM.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
i have yet to encounter the issue on point 1
but yes i do find issue 2 very often, indeed i have set mine to WCDMA only to prevent roaming
since i installed NoBars, it seems to have taken care of the problem
need a few more days to confirm
AllGamer said:
i have yet to encounter the issue on point 1
but yes i do find issue 2 very often, indeed i have set mine to WCDMA only to prevent roaming
since i installed NoBars, it seems to have taken care of the problem
need a few more days to confirm
Click to expand...
Click to collapse
Still unacceptable that we even have to do that. This is a flagship phone and these are pretty major issues. What goods a phone that cant get signal. Pretty annoyed especially since this is a 500$+ phone.
This comes from these 2 topics
[Q] Nexus S & WIND Mobile 3G Connection Issues http://forum.xda-developers.com/showthread.php?t=928661
Sudden Loss of Data on Nexus S http://forum.xda-developers.com/showthread.php?t=882518
it's worth a topic of its own as it very clear states all the issues and work around to the problems
johoja said:
Still unacceptable that we even have to do that. This is a flagship phone and these are pretty major issues. What goods a phone that cant get signal. Pretty annoyed especially since this is a 500$+ phone.
Click to expand...
Click to collapse
I agree with that
Is there a bug report opened on google code?
I can confirm the second problem.... :/
ekerazha said:
Is there a bug report opened on google code?
Click to expand...
Click to collapse
I believe google code is for AOSP issues, for Nexus S related issues I would do the following:
1) Tweet the issue to googlenexus, and romainguy
2) Post on the forum http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
I'm surprised they still haven't acknowledged it.
johoja said:
I believe google code is for AOSP issues, for Nexus S related issues I would do the following:
1) Tweet the issue to googlenexus, and romainguy
2) Post on the forum http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
I'm surprised they still haven't acknowledged it.
Click to expand...
Click to collapse
The problem is distinguishing what is a Nexus S hardware bug and what is a Gingerbread AOSP issue, especially since the NS is the only device running 2.3.x, so we can't compare our bugs to other devices to determine if it's AOSP or device-specific.
Google does tend to close bug reports out as saying it's not a code bug.
The support/help forum does also tend to get more active replies from Google employees than you ever see on the code site.
distortedloop said:
The problem is distinguishing what is a Nexus S hardware bug and what is a Gingerbread AOSP issue, especially since the NS is the only device running 2.3.x, so we can't compare our bugs to other devices to determine if it's AOSP or device-specific.
Google does tend to close bug reports out as saying it's not a code bug.
The support/help forum does also tend to get more active replies from Google employees than you ever see on the code site.
Click to expand...
Click to collapse
Going through forums and bug reports & according to AllGamer the Samsung Galaxy S devices suffered the same issues initially but were fixed with updates (and as we all know SGS does not have 2.3+ (Also I'm not sure if it was completely fixed). Since the NS is pretty much the same device I'm not surprised.
See this for example:
http://www.howardforums.com/showthr...-after-disconnected-to-Mobilicty-to-reconnect
The work around for SGS users was a little bit better though they have an option to specify WCDMA Bands i.e) 1700mhz only. That seems to fix the problem on SGS. Unfortunately 'Pure' Google doesn't have that option built in. ( I can't confirm the fix only going on what I've read. Don't have a SGS)
Based on that I'm going to go ahead and say its not a Gingerbread issue, it's more of a baseband issue. Also I think you can flash Gingerbread to an N1 (Cyanogenmod) I sold my N1 so can't verify for sure its not a Gingerbread only issue.
back on the SGS, the problem was only with 2.1 Eclair
after upgrading to 2.2 Froyo all those voice/network dropped issues were resolved
so it's possible we might be seeing a re-lapse of the problem in 2.3 GingerBread, perhaps 2.4 might fix this?
johoja said:
Going through forums and bug reports & according to AllGamer the Samsung Galaxy S devices suffered the same issues initially but were fixed with updates (and as we all know SGS does not have 2.3+ (Also I'm not sure if it was completely fixed). Since the NS is pretty much the same device I'm not surprised.
See this for example:
http://www.howardforums.com/showthr...-after-disconnected-to-Mobilicty-to-reconnect
The work around for SGS users was a little bit better though they have an option to specify WCDMA Bands i.e) 1700mhz only. That seems to fix the problem on SGS. Unfortunately 'Pure' Google doesn't have that option built in. ( I can't confirm the fix only going on what I've read. Don't have a SGS)
Based on that I'm going to go ahead and say its not a Gingerbread issue, it's more of a baseband issue. Also I think you can flash Gingerbread to an N1 (Cyanogenmod) I sold my N1 so can't verify for sure its not a Gingerbread only issue.
Click to expand...
Click to collapse
First off, I think we need to stop saying SGS and Galaxy S phones. There are numerous existing models, and they all have slightly different hardware, including the radio chips. There are also at least four new as yet un-released, but announced models that will be called Galaxy S phones as well, and they are significantly different than the ones that are derivative of the original i9000.
For example, I have the Galaxy S i9000, and I usually specify that when referring to it. This is important, because the issues and solutions on the Galaxy S Vibrant are not the same.
My i9000 came with Eclair, and got updated to Froyo, and I NEVER had these problems with the phone on AT&T's US network. My friend is using a US Vibrant on AT&T as well and he never has had the issues, either on Eclair or Froyo. So I'm not so sure you can throw blanket statements like that around. But that's true of any issue.
More directly to your response to me, I didn't say this particular issue was or wasn't a hardware or software issue...my only point was that since the Nexus S is the only phone to have Gingerbread officially, the line between what is a device problem and what is a GB general software problem are definitely blurred. Any third party builds from the GB source may have had issues fixed on them. I remember from my N1 days that cyanogen often addressed Google bugs in his builds...
distortedloop said:
First off, I think we need to stop saying SGS and Galaxy S phones. There are numerous models, and they all have slightly different hardware, including the radio chips.
For example, I have the Galaxy S i9000, and I usually specify that when referring to it. This is important, because the issues and solutions on the Galaxy S Vibrant are not the same.
My i9000 came with Eclair, and got updated to Froyo, and I NEVER had these problems with the phone on AT&T's US network. My friend is using a US Vibrant on AT&T as well and he never has had the issues, either on Eclair or Froyo. So I'm not so sure you can throw blanket statements like that around. But that's true of any issue.
More directly to your response to me, I didn't say this particular issue was or wasn't a hardware or software issue...my only point was that since the Nexus S is the only phone to have Gingerbread officially, the line between what is a device problem and what is a GB general software problem are definitely blurred. Any third party builds from the GB source may have had issues fixed on them. I remember from my N1 days that cyanogen often addressed Google bugs in his builds...
Click to expand...
Click to collapse
I was referring to the Vibrant. Maybe it only affects that specific model as well.
http://forum.xda-developers.com/showthread.php?t=819589
http://forum.xda-developers.com/showthread.php?t=772849
I just think its a little suspicious that they have the very similar issues.
The Vibrant and the Nexus S both have the same baseband platform -
Infineon X-Gold X616 (PMB9801).
Either way. Your right until we actually hear from Google about the issue this is all speculation. Hope they fix it soon
Maybe the issue is only present for the phones that have the chipset to handle AWS ( 1700mhz)
Now the cellular radio freezing issue I complained is identified as #2? Good!
Hopefully the forthcoming radio ROM will fix this issue.
johoja said:
Summary of baseband bugs in Nexus s
1) Having network selection set to manual ( i.e selecting 302490) will result in No Service on a reboot.
Solutions:
- Have to cycle airplane mode to get it to pick up service (can be done with automatically tasker)
- OR Use automatic network selection. (you can force wcdma only but that will reset the SMSC which is annoying if you go in and out of wind away/home areas and you want to roam.)
2) Being in a area with no service for extended periods of time 5+minutes(subway, basement, etc) will result in a dead baseband, meaning once you come into an area with service the phone will not reacquire signal, airplane mode will not work as the baseband is now crashed, cant maunally search for a network. Have to reboot to get signal.
Solutions:
-Use tasker to cycle airplane mode on and off when in no service areas i.e) search signal 4 minutes, airplane mode on 10 minutes. This will keep the baseband from crashing and possibly save battery.
-Use NoBars to accomplish the same thing ( tasker gives you a bit more flexibilty of course but harder to use) http://www.appbrain.com/app/nobars-battery-saver/com.tomdryer.nobars
- Use airplane edit to avoid turning wifi/bt off when airplane mode is on. http://www.appbrain.com/app/airplane-edit/net.cenkalti.airplane
3) WCDMA perferred does not work.
- No solution.
These are all software bugs/baseband so hopefully they will be resolved soon by google. Voice your concern on the google mobile forum though. These are reproducible on stock, and any ROM.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
Click to expand...
Click to collapse
johoja said:
I just think its a little suspicious that they have the very similar issues.
The Vibrant and the Nexus S both have the same baseband platform -
Infineon X-Gold X616 (PMB9801).
Either way. Your right until we actually hear from Google about the issue this is all speculation. Hope they fix it soon
Maybe the issue is only present for the phones that have the chipset to handle AWS ( 1700mhz)
Click to expand...
Click to collapse
That is interesting.
I wonder if it's actually only with those that handle AWS while actually connecting to AWS. As I mentioned in my previous post, my friend is using a Vibrant I setup for him on AT&T and he has no issues like the ones described above.
I think there's just some level of black-magic or voodoo or karma with cell phones; for some of us, few issues, for others, nightmares.
Changed on its own from WCDMA only to GSM/CDMA auto (PRL)
so i was manually sync-ing my gmails
and all of the sudden i see i was from HSPDA and BAM! it changed to R (roaming)
i was like WTF !!!!!!!!!
so i immediately switched to airplane mode, and back to cycle it to see if it changes back and no, it was still stuck in Roaming mode.
so i ended up manually changing it manually back to WIND from the network selection screen
and then i went to check on *#*#4363#*#* and found out it was not on WCDMA only
which makes it really weird, as i didn't change it at all.
this is the first time it has done that to me.
have any body else seen this problem before?
good thing is, it did not enable data roaming, so hopefully i did not incur any roaming charges, ... i guess i'll see when the monthly Bill arrives
Mine switches occasionally when I lose reception. Like you, I generally keep mine on wcdma only. I have no idea why this phone does this, as it has happened on the stock rom, modaco, and cyanogenmod.
My old Nexus One never did this. Luckily it seems like that problem hasn't happened for me in the last week or two, so it isn't very common.
Never had this but on my nexus 1 I would use auto prl and would get more battery. I changed it on my nexus s and it goes back to wcdma.
If u have roaming off, u should be good.
it might be another bug related to the baseband
perhaps more people can confirm and or reproduce the issue
AllGamer said:
it might be another bug related to the baseband
perhaps more people can confirm and or reproduce the issue
Click to expand...
Click to collapse
Ive had it happen once or twice. Not sure how to reproduce it. I got annoyed because once that happens you have to re-enter the SMSC.
I leave mine on GSM/cdma (prl) and manually select the network I want. That keeps it from roaming as well.
I have a few S4 phones on AT&T, running CyanogenMod (10.2.0). Around November 1st, two of the phones started having problems where calls get dropped within about 1 second (either making or receiving).
Internet and SMS is fine - only voice has problems.
AT&T says there's no network issue they can see. If this happened to only one phone, you might wonder if the phone just went bad, but two phones at roughly the same time suggests something else.
**If** the problem is not on AT&T's end (which I don't know for certain), then the only thing I can think of is that some app update caused this which I did on both phones (but I don't remember what I might have updated around then, and I'm not aware of a proper app update log that exists).
If I can't find another way of troubleshooting this, I'll wipe one of the phones, take the opportunity to update to the latest CM version and see if that fixes it - but I'm reluctant to do that due to the time and effort involved.
Does anyone have any other ideas?
Haphim said:
I have a few S4 phones on AT&T, running CyanogenMod (10.2.0). Around November 1st, two of the phones started having problems where calls get dropped within about 1 second (either making or receiving).
Internet and SMS is fine - only voice has problems.
AT&T says there's no network issue they can see. If this happened to only one phone, you might wonder if the phone just went bad, but two phones at roughly the same time suggests something else.
**If** the problem is not on AT&T's end (which I don't know for certain), then the only thing I can think of is that some app update caused this which I did on both phones (but I don't remember what I might have updated around then, and I'm not aware of a proper app update log that exists).
If I can't find another way of troubleshooting this, I'll wipe one of the phones, take the opportunity to update to the latest CM version and see if that fixes it - but I'm reluctant to do that due to the time and effort involved.
Does anyone have any other ideas?
Click to expand...
Click to collapse
Same thing happend to me, for the past 2 weeks i've been having a horrible connection with dropped calls and low bars.... i recently rooted and installed a new rom, and I thought that's whats causing the problem. But after At&t's horrible customer service i decided to drop them and switch to Tmobile today... dropped calls have improved but signal is still not where it used to be. So maybe it was at&t??
Hi,
I have seen some posts here with lost cell connectivity. However my issue is slightly different and started to appear few weeks back. I was rooted running stock 7.1.1 OS with Franco kernel. My phone started to loose signal all the time. You can just look at the signal bar and see the signal strength going all the way from 100% to 0% in every few seconds. I have tried different radio versions, new ROMs, restoring my Nandroid backup etc. Nothing seems to work. Changing to 3g shows the same issue and I have no signal on 2g only mode. I am in AT&T.
Also wanted to add that I can make out going calls from my phone. The issue is when its idle. I don't get any incoming calls due to this issue.
Any help will be highly appreciated. Currently using my office iPhone and feels terrible.
amith007 said:
Hi, I have seen some posts here with lost cell connectivity. However my issue is slightly different and started to appear few weeks back. I was rooted running stock 7.1.1 OS with Franco kernel. My phone started to loose signal all the time. You can just look at the signal bar and see the signal strength going all the way from 100% to 0% in every few seconds. I have tried different radio versions, new ROMs, restoring my Nandroid backup etc. Nothing seems to work. Changing to 3g shows the same issue and I have no signal on 2g only mode. I am in AT&T. Also wanted to add that I can make out going calls from my phone. The issue is when its idle. I don't get any incoming calls due to this issue. Any help will be highly appreciated. Currently using my office iPhone and feels terrible.
Click to expand...
Click to collapse
I'd run up to AT&T and ask for a new SIM. It's free and you rule out something on their end, and the SIM too when they provision it. Is your phone carrier (SIM) locked to AT&T? If so, I'd see about getting it unlocked so you can test other carriers. If already carrier unlocked have you tried borrowing a friends SIM on another network? If signal continues to drop it could be a hardware issue.
v12xke said:
I'd run up to AT&T and ask for a new SIM. It's free and you rule out something on their end, and the SIM too when they provision it. Is your phone carrier (SIM) locked to AT&T? If so, I'd see about getting it unlocked so you can test other carriers. If already carrier unlocked have you tried borrowing a friends SIM on another network? If signal continues to drop it could be a hardware issue.
Click to expand...
Click to collapse
I have tried with another sim. The issue still persist. Also I have tried my sim on a new device and it seems to work fine. So I am almost certain that the issue is with my phone. All I wonder is whether its hardware or software.
amith007 said:
I have tried with another sim. The issue still persist. Also I have tried my sim on a new device and it seems to work fine. So I am almost certain that the issue is with my phone. All I wonder is whether its hardware or software.
Click to expand...
Click to collapse
You sound proficient enough with flashing ROMS, radios, restoring Nandroids to know this already.... you are probably just postponing the inevitable: Back up and pull off all your data, format the partitions, and flash the latest full factory image from your PC using flash-all.bat. You will have your answer very quickly- in fact you will know even before you begin to set up your phone. If you are still under warranty this will be step number one with Google or Huawei.
v12xke said:
You sound proficient enough with flashing ROMS, radios, restoring Nandroids to know this already.... you are probably just postponing the inevitable: Back up and pull off all your data, format the partitions, and flash the latest full factory image from your PC using flash-all.bat. You will have your answer very quickly- in fact you will know even before you begin to set up your phone. If you are still under warranty this will be step number one with Google or Huawei.
Click to expand...
Click to collapse
My Nandroid backup was actually a vanilla 7.0 image. I will give this a try with the flash-all.bat and update here
Any update?