• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Fix for signal strenth on the horizon (FOR MARCH!!)

Spoke with VZW technical support today about the terrible signal strength on the Gnex. they state that it is a known problem for them and there is nothing that they can do at this point. but she stated there is a fix in the works. (software update?) set to roll out in March.

Sorry, not worth waiting that long to find out if a fix could even possibly fix the issue. Returning the phone today and re activating my old iphone and waiting for the next group of android phones.

She did tell me that they are going to release a "droid Razr Pro" in january. we'll see. if so all the Razr buyers will be pissed. :)
 
Yeah, it seems every time I call Verizon tech support they just happen to have the same exact phone I have and know that an update is just around the corner. I wouldn't put much trust into their word. One of the reasons I got the GNex is because I knew Google would keep this phone up to date and I wouldn't have to rely on Big Red.
 
Spoke with VZW technical support today about the terrible signal strength on the Gnex. they state that it is a known problem for them and there is nothing that they can do at this point. but she stated there is a fix in the works. (software update?) set to roll out in March.

Sorry, not worth waiting that long to find out if a fix could even possibly fix the issue. Returning the phone today and re activating my old iphone and waiting for the next group of android phones.

She did tell me that they are going to release a "droid Razr Pro" in january. we'll see. if so all the Razr buyers will be pissed. :)

I just like the fact that she knows and is willing to talk about the Droid Razr Pro that is coming in January, but nobody could say a word about the Nexus when it was a week away. lol

FWIW, there are a couple of updates in the works and any of them could potentially help with the signal issues that so many have. I think you could call 3 different CSRs and get 3 different expected dates.
 
I just like the fact that she knows and is willing to talk about the Droid Razr Pro that is coming in January, but nobody could say a word about the Nexus when it was a week away. lol

FWIW, there are a couple of updates in the works and any of them could potentially help with the signal issues that so many have. I think you could call 3 different CSRs and get 3 different expected dates.
Not only that, but those same 3 CSRs would all most likely be repeating what they saw on the internet, not anything official from Verizon.
 
I just like the fact that she knows and is willing to talk about the Droid Razr Pro that is coming in January, but nobody could say a word about the Nexus when it was a week away. lol

FWIW, there are a couple of updates in the works and any of them could potentially help with the signal issues that so many have. I think you could call 3 different CSRs and get 3 different expected dates.
3? I would expect 4 or 5 different dates from 3 CSR's. :D
 
Apparently VZW knows about the Galaxy Nexus signal issues and is working on a software fix:

Verizon Support: Update to Address Galaxy Nexus Signal Strength in the Works – Droid Life


Issue though is the Thunderbolt was able to be improved by fixing 3g/4g instability, but the TB did not have a weak dBm signal.

How does VZW fix a weak signal? Since the wifi is also weak, maybe Samsung stepped down the mW to conserve battery.

Seems the only way is to increase the power to the radios (if possible ).
 
According to the CSR I just talked to Samsung is aware of the issue and they are expecting an update in January...whatever.
 
I would argue with this. there is no problem with how the phone "displays the signal"

I am getting dropped calls and no data.

Its a signal reception problem
 
Depends how the software accesses the hardware.

Take your computer for example. Has anyone ever seen the blue screen of death error that says "IRQ Less than or equal to" error? That is a driver error. The software was trying to access part of the hardware incorrectly. Updating the driver resolves this issue. The problem is knowing what driver.

Probably a similar problem.

If the issue has both hardware and software components than a software update may only be able to partially improve things... not correct them. ;)
 
Back
Top Bottom