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

Declining Reception

hey guys! I was reading over CyanogenMod Forum that it could be an issue with the new baseband update C_01.3E.03P. this might be a solution for it. I downloaded and my reception got a lot better... try this:

thanks to CELLZEALOT!

"There are different versions of the update.zip baseband installation file, at least two that I am aware of.
I don't know which one is up on ROM manager but it appears to be the older version because it says it will require *228 activation after installing the update.zip.

The original file created by teh_steve on alldroid used the baseband files from the ESE53 SBF file because the version numbers are the same: C_01.3E.03P for both ESE53 and the official ESE81 update. They are not, in fact, the same files. The ESE81 Update.zip does NOT require reactivation after running it because it is an upgrade installation that is meant to preserve the service programming while updating the rest of the NVM to the new version. This is to avoid the need for users to be forced to activate after the OTA update.

This new version was put into the same zip file that teh_steve created and was posted on alldroid in that same thread.


http://alldroid.org/...70&d=1270146038

That is the right file that you want to use with the ESE81 baseband files in upgrade format that will keep your service programming intact.

The question remains if there is any actual difference in the baseband versions themselves given they have the same version number, despite being different size files.
To answer that question will require looking at the NVM itself to compare the values.

This is something I am looking at right now but don't have the time to do it right. Now that diag mode access is possible on CM with the new kernels it makes it easier to do but is still a pretty involved process of comparing the NV items.

Anyone having any issues should run the update.zip file from that link and see if it doesn't fix it"

:D
 
FWIW - I've done the *228 thing only once since I upgrated to the OTA 2.1.

Again - FWIW, In the Virginia Beach, VA area, I'm almost always running all 4 bars and 3G. The first week of Apr 2010, I took a trip to New Mexico. In ABQ, I had the same signal strength. When I was in Truth or Consequences (about 170 miles south of ABQ), I had 2 bars in the hotel and 3 or 4 outside and almost always had 3G. Even at White Sands National Monument - I had great signal strength.

Running the OTA 2.1-update1, baseband: C_01.3E.03P, build ESE81. Not OC'ed. Not rooted (obviously).
 
Same here in Peoria, IL. Seeing quite a few 1X where it should be 3G. Didn't start noticing it until after the 2.1 update. Verizon folks think everything is OK here, but the number of dropped calls and VM's showing up with no rings...that's a problem in my book!

-S
 
I have been noticing a lot of 1X activity on my phone too. This was before the update and has maintained the same state of annoying since the update. Last weekend, I went to Pennsytucky (OK, it wasn't the middle of nowhere in PA but the cow : people ratio was almost even.) I have full 3G signal. I know those are probably towers they aquired from Altell, but WTF?

Just like with Sprint using Verizon's towers in my area, why is there such a discrepancy in reception if the hardware is supposedly the same? If it is because there are too many people using VZW 3G in DC, it is time to start campaigning for AT&T's iPhone.
 
I notice the signal strength and 1x 3g issue a lot.. very noticeable change

there is no doubt in my mind they changed something up on us. I bet to reduce usage and bandwidth.
 
I was going to move it to my Tinfoil Hat thread because I wanted to say that Apple is punishing us for making fun of the iPad, but your theory makes more sense.
 
I notice the signal strength and 1x 3g issue a lot.. very noticeable change

there is no doubt in my mind they changed something up on us. I bet to reduce usage and bandwidth.

So your theory is that Verizon intentionally CRIPPLED their device in order to limit their customer's use?

If that proves to be true I will be leaving Verizon with the quickness!
 
So your theory is that Verizon intentionally CRIPPLED their device in order to limit their customer's use?

If that proves to be true I will be leaving Verizon with the quickness!

sure, why not? you really think, in this day and age, it is that far fetched? PA LEASE

they are selling the hell out of these phones. slightly cripple them and maybe it cuts down on usage a bit? a theory is a theory. no proof, but possible for sure.
 
I never said it was far fetched. Where did I say I didn't believe it? I simply said if proven true I will dump Verizon.

I know I know.. was not accusing you, just saying

but we will never know for sure. ever.

prime example, look at the cigarette industry who denied the negative effects of smoking despite the internal memos that showed they knew. we are never going to get a VZW internal memo saying they knew they purposefully changed the band so as to slightly hamstring the phone to reduce usage and cell strain.

but if it is not purposeful, how does stuff like this happen. SO many people, not only on this Droid forum, report this issue. how would they not know? how would it "slip" by? well, I don't think this kind of stuff "slips" by as they know messing with the band can change people's reception and so if they tested, they would have to have known it is obvious the band change screwed us... so how else do you explain it ;)
 
Ever since the 2.1 update my reception has been so bad i cant talk in or around my own house. I used to have perfect calls anywhere through my house. Its starting to get ridiculous to have a phone that i cant use because i cant hear anyone on it and they can barley hear me.
 
I am pretty sure this is more of a 2.1 thing than anything I mean the Nexus One came with 2.1 and since opening day has had horrible reception with dropping to edge all the time. Seems weird that the two phones that have it now have the same issue? Also Verizon would never make people's signal suck to save on bandwidth because that doesn't help them at all. Oh and may I also mention the Incredible with 2.1 has horrible reception and drops to 1X a lot so I am pointing the blame at 2.1 and eagerly waiting for 2.2
 
This was happening to some of us before the update. I also was in the wilds of PA this weekend and never had a single drop to 1X. If the network is not scalable enough to handle the new traffic load with all of the android phones, they are not much better than AT&T for data. I will kick them into the pit just like in that movie 300.... I'll do it, Verizon. Don't test me.
 
Well to disprove it is the network overloaded. I can tell you that in downtown Houston I get much better and faster service than in the middle of nowhere in Lubbock. This turned to Verizon the week I arrived here and I have much slower speeds and drop to 1X where at home in Houston I have never dropped down!
 
Same with me. I'm in the SF Bay Area, one of the most data hungry places in the country so that could be my problem. But that was more common with iPhones I thought, not Verizon so idk what is going on.
 
I'm going most of this morning without signal at all where I had 3g before the 2.1 update. This is happening on both mine and my wife's Droid. Has Verizon even addressed this issue?
 
call VZW and tell them... people need to let them know. us complaining here doesn't mean jack. put them on notice with a simple free call to their CS or tech support.
 
I've called Verizon. After explaining the issue their solution was to exchange my phone for a refurbished unit. I told them it was the exact same on the second Droid to which they had no answer and pushed the exchange. I don't want a used phone to replace a good phone that is having a service issue. I'll get nothing fixed that way.
 
to no real avail I will presume, I tell them that I am reading about this recent decline in forums all over the web.. which is true. just to hit the point home so they don't try the

"lets do a factory reset" or "exchange it for a refurb" lines on me as those will not fix an issue reported by many all over the web.
 
FWIW, Today 5-7-10 the *228 PRL update Actually Had an Effect! This is apparently not an isolated happy moment. I discovered another thread here by random accident, updated via *228, and immediately increased from 1 bar indoors to a steady 3 indoors. Hope this helps

{edit} I'm on, and *228 applies to the VZW network.
 
Back
Top Bottom