Let Google know about signal issues here

[jnl813]

Because they're not going to just let us sit here without a decent signal, how bad is it for you guys? On mine I see the bars grey but its still able to connect. Same thing with wifi.

Sent from my Nexus S 4G using Tapatalk

 

[fixxxer1022]

do we even know if google, sprint or smasung is looking into a fix as we speak? seems no one has any answers. it's pretty common to see this is a radio issue.

 

[fixxxer1022]

Done definatelly a problem, doubt anything will be done about it as there are not many Sprint Nexus S users

yeah im shocked there are not more nexus users. i may just take this back next weekend and wait for the evo3d.

i won't buy another samsung product.

 

[hatsoffexpress]

FiXXXer, I don't know if you XDA, but there are actually some pretty prolific developers already on the good ship Nexus S. And I'm not trying to defend myself from cognitive dissonance here, I'm trying to pep talk.

That being said...the signal issue is so, so sad to me. The camera is a wimp, and these items are really software related, and if not, the Nexus line was bastardized in one generation. The N1 set the benchmark for what an Android phone could and should be, but if the above mentioned items are hardware and not software related, shame on Google for letting Samsung do that.

 

[chhay]

hello all,

I just got my Nexus S 4G a couple days ago. 4G signal is very spotty. I have seen 2 out of 3 bars, the when 4G is going into idle mode, it seems like the connection was dropped. NS4G seems to struggling with that: I see the phone connect then disconnected from the 4G network. regarding 3G, definitely much weaker compared to any other sprint phones nearby. They have to fix this.

google, samsung, and sprint haven't publicly acknowledge and announced any fixes yet, but seems like sprint tech team is looking into it (source: sprint community forum)
there are 18 full pages right now on the sprint community forum, and a customer getting response from sprint CEO Dan Hess. so we'll see. Here is the link to the forum:

Sprint Community: Signal Issues with Nexus S

there's also a link on that forum pointing to a binaries for Nexus S phones. basically a spreadsheet of which company is responsible for what (hw/sw) in making NS. Here it is:

Binaries for Nexus Phones - Google Support for Nexus Phones - Google Code

I really hope they fix this before my 30 days is up. all we can do right now is make our voice heard and patiently wait for them to do something.

 

[redtooth]

hello all,

I just got my Nexus S 4G a couple days ago. 4G signal is very spotty. I have seen 2 out of 3 bars, the when 4G is going into idle mode, it seems like the connection was dropped. NS4G seems to struggling with that: I see the phone connect then disconnected from the 4G network. regarding 3G, definitely much weaker compared to any other sprint phones nearby. They have to fix this.

google, samsung, and sprint haven't publicly acknowledge and announced any fixes yet, but seems like sprint tech team is looking into it (source: sprint community forum)
there are 18 full pages right now on the sprint community forum, and a customer getting response from sprint CEO Dan Hess. so we'll see. Here is the link to the forum:

Sprint Community: Signal Issues with Nexus S

there's also a link on that forum pointing to a binaries for Nexus S phones. basically a spreadsheet of which company is responsible for what (hw/sw) in making NS. Here it is:

Binaries for Nexus Phones - Google Support for Nexus Phones - Google Code

I really hope they fix this before my 30 days is up. all we can do right now is make our voice heard and patiently wait for them to do something.

If thats true and samsung is responsible for the update we might as well trade them in now!!

 

[mgwally]

Include me in the list! I'm returning this phone if it doesn't get an OTA update soon.

It's not like the hardware hasn't been out for a while. I don't get it.

Sent from my Nexus S 4G using Tapatalk

 

[chhay]

yep, it looks like samsung is to blame on this hardware problem.

 

[jtfishbein]

Include me in the list! I'm returning this phone if it doesn't get an OTA update soon.

It's not like the hardware hasn't been out for a while. I don't get it.

Sent from my Nexus S 4G using Tapatalk

Just switched back to the Evo. Going to return the Nexus tomorrow, since this is my 3rd replacement. I give up as I need something more reliable.

Sent from my PC36100 using Tapatalk

 

[splmonster]

Done definatelly a problem, doubt anything will be done about it as there are not many Sprint Nexus S users

This is completely incorrect.. I'm seeing many places sold out of them here in PHX. I also have received numerous emails from Sprint, and Samsung that the issue is currently being worked on and that they are aware of the issue, at least now.

yep, it looks like samsung is to blame on this hardware problem.

The issue is not hardware.. It's software and drivers. Been confirmed by Sprint, Google, and Samsung. They know of the issue now, so everyone should be patient. All devices have many issues upon release.

Just switched back to the Evo. Going to return the Nexus tomorrow, since this is my 3rd replacement. I give up as I need something more reliable.

Sent from my PC36100 using Tapatalk

I personally feel that returning to fix the issue is the wrong thing to do. The issue is strictly software, and drivers. The phone just came out not that long ago, and you can't expect perfection on any devices. Heck the EVO on launch suffered these issues and more for over a month.

Please remember guys this device was released May 8th, it has not been out very long at all. So the word is "patience"! Stop assuming it's hardware fault, things like these usually are not. Only because these parts are tested before they ever get into the device.

 

[chhay]

splmonster, thanks for the updates. I really hope you are right that they are working on this issue. i feel that they should publicly announced something or have a press release on this. at least that would stop people from returning their phones, along with that, they should relax the 30-day return policy. if sprint wants to gain customers from att and verizon, they need to take the high road, and offer unparallel customer service. latest survey had them tie with verizon. hope that sprint can survive if att and t-mobile merged. I know that nexus s 4g hardware isn't that up-to-date, many other devices coming out with better hardware, but google put alot into this phone to make it smooth and easy to use. besides this problem, i don't think there's nothing wrong with nexus s 4g.

 

[jtfishbein]

This is completely incorrect.. I'm seeing many places sold out of them here in PHX. I also have received numerous emails from Sprint, and Samsung that the issue is currently being worked on and that they are aware of the issue, at least now.




The issue is not hardware.. It's software and drivers. Been confirmed by Sprint, Google, and Samsung. They know of the issue now, so everyone should be patient. All devices have many issues upon release.



I personally feel that returning to fix the issue is the wrong thing to do. The issue is strictly software, and drivers. The phone just came out not that long ago, and you can't expect perfection on any devices. Heck the EVO on launch suffered these issues and more for over a month.

Please remember guys this device was released May 8th, it has not been out very long at all. So the word is "patience"! Stop assuming it's hardware fault, things like these usually are not. Only because these parts are tested before they ever get into the device.

I'm not returning it just bc of the reception, as I was a launch day evo adopter, and it had a similar situation. What bugs me is that I cannot use my speakerphone. The most basic feature was unable to be used bc of a terrible echo that only subsided when you remove the battery cover.

I'm just torn bc the phone is great except for those few issues.

Sent from my PC36100 using Tapatalk

 

[splmonster]

I'm not returning it just bc of the reception, as I was a launch day evo adopter, and it had a similar situation. What bugs me is that I cannot use my speakerphone. The most basic feature was unable to be used bc of a terrible echo that only subsided when you remove the battery cover.

I'm just torn bc the phone is great except for those few issues.

Sent from my PC36100 using Tapatalk

So the speaker was vibrating the battery cover during speaker phone? Let me test mine out and see if I suffer from that. Something like that is an easy fix, you could put like some sound deadening material on the cover or foam pieces to make it more sturdy. Let me try mine...

 

[splmonster]

splmonster, thanks for the updates. I really hope you are right that they are working on this issue. i feel that they should publicly announced something or have a press release on this. at least that would stop people from returning their phones, along with that, they should relax the 30-day return policy. if sprint wants to gain customers from att and verizon, they need to take the high road, and offer unparallel customer service. latest survey had them tie with verizon. hope that sprint can survive if att and t-mobile merged. I know that nexus s 4g hardware isn't that up-to-date, many other devices coming out with better hardware, but google put alot into this phone to make it smooth and easy to use. besides this problem, i don't think there's nothing wrong with nexus s 4g.

It's nothing new, usually no devices get any sort of publicity or press releases when it comes to these things. The most you see is blog or review sites making articles about it. However those things are good, because it causes them to fix it faster. You also need to remember all devices and carriers have these issues, not just Sprint. Heck Verizon is always having issues with Android devices. A current big one is the T-Bolt rebooting constantly. The Nexus S is not up-to-date correct, but the hardware it consumes was optimized for GB and it utilizes what Android offers right now. All the dual-core stuff isn't even supported yet by Android. It works, but it's not optimized. Don't worry my sources at Sprint here said the issue is pretty widespread and they know about it.

 

[redtooth]

I personally feel that returning to fix the issue is the wrong thing to do. The issue is strictly software, and drivers. The phone just came out not that long ago, and you can't expect perfection on any devices. Heck the EVO on launch suffered these issues and more for over a month.

Please remember guys this device was released May 8th, it has not been out very long at all. So the word is "patience"! Stop assuming it's hardware fault, things like these usually are not. Only because these parts are tested before they ever get into the device.
__________________
All hail the Android!

I really like the phone but I feel these signal problems are completely unacceptable. Nothing on this phone is new technology. I can?t believe the proper amount of testing was done prior to launch. I expected some small issues but this is not a small issue. My phone is completely unusable as a phone in places I spend 60% of my time. My lowly Palm Pre gets far better signal in these same places and friends with other Android devices get even better signal than that. I still have not decided what I will do as I truly hope they can fix this issue soon. I do not however think I will let my 30 day return period expire without some sign of improvement. I cannot imagine buying a $200 device and the primary function of the device does not work. It would be like buying a new car that would only do 25 mph. How long would you be willing to wait for a fix for that? I really do like this phone but it?s got to function or it?s just not worth it. I hope this gets fixed before the end of the month.

 

[AndroidOne]

I personally feel that returning to fix the issue is the wrong thing to do. The issue is strictly software, and drivers. The phone just came out not that long ago, and you can't expect perfection on any devices. Heck the EVO on launch suffered these issues and more for over a month.

Sorry but I will disagree with you on this one, the Nexus IS NOT a new phone as the EVO was on launch date, is new on the Sprint network but has been out for months on T-Mo. Samsung/Google had ample time to sort out bugs on this one including the low notification/ringtone volume on this device.

In regards to the radios, I will agree ours are different than the GSM version, however I will not give Samsung a pass on this one either, they already have ample experience with Sprint CDMA radios to have screwed up this one so badly, as for the 4G, they also have experience building WiMax radios and drivers (remember the Epic). So there is no excuse for this, at least the Evo was the FIRST 4G phone out there and growing pains were to be expected.

GIven Samsung's reputation for (un)timely fixes and updates, I do not plan to keep this phone past the end of my 30-period unless a fix is released before then and I strongly advise everyone else to do the same. Spotty signal reception defeats the primary purpose of this device which is BEING A PHONE.

I don't know about the rest of you, but I did not paid hard earned money to get a device that misses calls because the radio or the driver is defective, I actually paid good money for this device (full price) with FULL EXPECTATION that it was going to work AS A PHONE, if it can't, then is useless to me.

 

[splmonster]

Sorry but I will disagree with you on this one, the Nexus IS NOT a new phone as the EVO was on launch date, is new on the Sprint network but has been out for months on T-Mo. Samsung/Google had ample time to sort out bugs on this one including the low notification/ringtone volume on this device.

In regards to the radios, I will agree ours are different than the GSM version, however I will not give Samsung a pass on this one either, they already have ample experience with Sprint CDMA radios to have screwed up this one so badly, as for the 4G, they also have experience building WiMax radios and drivers (remember the Epic). So there is no excuse for this, at least the Evo was the FIRST 4G phone out there and growing pains were to be expected.

GIven Samsung's reputation for (un)timely fixes and updates, I do not plan to keep this phone past the end of my 30-period unless a fix is released before then and I strongly advise everyone else to do the same. Spotty signal reception defeats the primary purpose of this device which is BEING A PHONE.

I don't know about the rest of you, but I did not paid hard earned money to get a device that misses calls because the radio or the driver is defective, I actually paid good money for this device (full price) with FULL EXPECTATION that it was going to work AS A PHONE, if it can't, then is useless to me.

Well I will just chime in and say once again. The radio is not DEFECTIVE! I know many of you have continued to repeat this over and over. However me personally every Android device I ever purchased at launch always sufferered with signal issues in the beginning. One that comes to mind was the EVO, which suffered radio problems for over a month and a update was finally released to fix it. Again 99% of devices usually come out with this exact same issue. So nothing new to see here... The best thing I can say to anyone, is welcome to the world of being a early adopter of devices. It's been this way for years.

 

[FocusFreak]

Sorry but I will disagree with you on this one, the Nexus IS NOT a new phone as the EVO was on launch date, is new on the Sprint network but has been out for months on T-Mo. Samsung/Google had ample time to sort out bugs on this one including the low notification/ringtone volume on this device.

In regards to the radios, I will agree ours are different than the GSM version, however I will not give Samsung a pass on this one either, they already have ample experience with Sprint CDMA radios to have screwed up this one so badly, as for the 4G, they also have experience building WiMax radios and drivers (remember the Epic). So there is no excuse for this, at least the Evo was the FIRST 4G phone out there and growing pains were to be expected.

GIven Samsung's reputation for (un)timely fixes and updates, I do not plan to keep this phone past the end of my 30-period unless a fix is released before then and I strongly advise everyone else to do the same. Spotty signal reception defeats the primary purpose of this device which is BEING A PHONE.

I don't know about the rest of you, but I did not paid hard earned money to get a device that misses calls because the radio or the driver is defective, I actually paid good money for this device (full price) with FULL EXPECTATION that it was going to work AS A PHONE, if it can't, then is useless to me.

Sorry but this is SPRINTS fault. The Evo 4G had nearly identical problems the Nexus is having. Weak 4G and only a bar or two of wifi sitting in front of a router. Far too coincidental that two different phones from two different manufacturers would be doing pretty much the exact same thing on Sprints network but no problems on the T Mobile version.

 

[splmonster]

Sorry but this is SPRINTS fault. The Evo 4G had nearly identical problems the Nexus is having. Weak 4G and only a bar or two of wifi sitting in front of a router. Far too coincidental that two different phones from two different manufacturers would be doing pretty much the exact same thing on Sprints network but no problems on the T Mobile version.

When the new PRL came out for Sprint devices after the big change in coverage. My 3G, 4G seem to get much worse signal, and the speeds were much slower. Again my knowledge knows that PRL's should have 0 to do with it. However it seems Sprints network is having issues at least in Phoenix. This was across about 10 devices I observed, all being different. The Nexus S on T-Mob is having issues, they have posted topics on Google's site forum of it having issues. Many are posting within that topic. Let me find it..

 

[AndroidOne]

Well I will just chime in and say once again. The radio is not DEFECTIVE! I know many of you have continued to repeat this over and over. However me personally every Android device I ever purchased at launch always sufferered with signal issues in the beginning. One that comes to mind was the EVO, which suffered radio problems for over a month and a update was finally released to fix it. Again 99% of devices usually come out with this exact same issue. So nothing new to see here... The best thing I can say to anyone, is welcome to the world of being a early adopter of devices. It's been this way for years.

Sorry, I have been an early adopter since the Treo 300 - my first smartphone - so I do agree with you that all new phones have issues. I am also an early adopter of the Evo and the Epic and I too remember the issues you mention here, however, the first OTA for the Evo happened within two weeks of release, the Epic, no so.

However, with the Nexus is different, the signal issues (and I am not talking about those reported with 4G or wifi) are causing some, including me, to miss calls and have dropped calls where signal on the network is good for anyone else, where signal is excellent with my Evo or Epic. This goes to the basic function of this device which is being a phone. That DID NOT happen with my Evo or Epic even at the beginning. This is NOT a network issue, is a phone issue, otherwise all other Sprint phones in this area would have the same problem and they don't. And please understand I am not talking about what the bars say, if the bars read zero but you are able to make calls then no problem. I am talking about being on a call and loosing connection because signal fades. So far I have reactivated my Evo and is what I am using until there is a fix for the Nexus.

This is something that needs to to be fixed by Samsung ~ as in other computing devices, drivers for the chipsets are provided by the manufacturer. My position is simple, if Samsung - or whoever is responsible for this issue - don't fix it before the trial period is over, I will not keep this device because telephony is not an option, is the most basic functionality I expect. Others may decide on their own, but this is what a trial period is for, to make sure the device works for you and if it doesn't, then take it back.

Can not understand this forum sometimes, if a phone is a little sluggish playing Angry Birds that is inexcusable and a valid reason for immediate return because "this phone sucks!", but if the device is unreliable for making/receiving calls, the advise is no problem, just hang in there and it will be fixed at some point? I believe we need to get our collective priorities realigned here... this IS a phone, and if it does not work well as such by the end of the trial period then nothing else matters in my book.

I really like this phone and want to keep it, but can't/won't unless it actually works as a phone.