Problems with 3.27 radio on VZW XV6800

[GaryJohnson]

Hello all,

I've been searching for about a week for a solution to the issues I've been having, to no avail. I've seen some users complain about similar problems, but they're buried in the custom rom threads with no solutions. I'm curious to see if any others are experiencing what I'm seeing:

After flashing from stock VZW 2.09 Rom / 1.30.6 Radio to a custom Rom (tried Sprint Beta 3.16, DCD and No2Chem's) / 3.27 Radio, the phone will sit and search for a tower to connect to for 15-20 mintues. I confirmed that my EPST settings did not change, and my PRL is the same as before the flash. Once the connection is made, I do not seem to have any issues. After a soft reset or switching the radio on/off, it happens again. Performing a *228 option 1 does not seem to help at all.

The second problem is not too much of an issue, but I haven't seen anyone else describe quite the same thing. After each attempt to flash, I return to the stock Verizon radio and rom. I can always make incoming / outgoing calls without an issue, but attempting to connect to #777 for a data connection gives me a "incorrect username or password" error. Setting the username / password doesn't seem to matter, and the settings do not appear to hold. Every time I've had to badger tech support and they try things on their end until I'm back online. I've pushed them to tell me what they do so I can request it by name, but they've refused so far.

Has anyone experienced any of this? Does anyone have any ideas or solutions?

Thanks!

[kdj67f]

I don't know how much of this is coming fromn the phone end, because I have had 0 problems flashing ROMs and connection issues. I literally just flash, reboot and everything works without having to call in to TS.

I have read most of the threads dealing with connection issues and VZW, but I can offer no help, as my setup just works.

So I start to wonder if it is handset issues.

I had to call TS when I got the phone in the first place, as it was not set up for data authentication. I called TS, they switched some things on their end and since the first hour I have owned the phone, all is working.

[badutahboy]

Originally Posted by GaryJohnson

Hello all,

I've been searching for about a week for a solution to the issues I've been having, to no avail. I've seen some users complain about similar problems, but they're buried in the custom rom threads with no solutions. I'm curious to see if any others are experiencing what I'm seeing:

After flashing from stock VZW 2.09 Rom / 1.30.6 Radio to a custom Rom (tried Sprint Beta 3.16, DCD and No2Chem's) / 3.27 Radio, the phone will sit and search for a tower to connect to for 15-20 mintues. I confirmed that my EPST settings did not change, and my PRL is the same as before the flash. Once the connection is made, I do not seem to have any issues. After a soft reset or switching the radio on/off, it happens again. Performing a *228 option 1 does not seem to help at all.

The second problem is not too much of an issue, but I haven't seen anyone else describe quite the same thing. After each attempt to flash, I return to the stock Verizon radio and rom. I can always make incoming / outgoing calls without an issue, but attempting to connect to #777 for a data connection gives me a "incorrect username or password" error. Setting the username / password doesn't seem to matter, and the settings do not appear to hold. Every time I've had to badger tech support and they try things on their end until I'm back online. I've pushed them to tell me what they do so I can request it by name, but they've refused so far.

Has anyone experienced any of this? Does anyone have any ideas or solutions?

Thanks!

I have the exact same issue (I'm on cricket, not verizon.)

What makes it even more frustrating is it seems the GPS Roms freeze my phone at least once or twice a day, forcing me to soft reset, and leaving me without a phone for 20 min at a time (which is a SERIOUS pain for someone who uses 5,000 min/month.)

I'm glad to know the problem isn't tied to the cricket service, but I have no idea what it is. Hopefully someone can help us out.

[GaryJohnson]

I had briefly considered that the issue might be tied to the hardware (defective, or new revision), but since I'm on the same stock VZW radio / rom version as everyone else started with, and since the phone works perfectly fine under that configuration, I think the chances are pretty slim that it's hardware related.

I'm guessing that it might be some specific to my location or the tower I usually connect to, coupled with the fact that I'm using a potientially buggy radio version. The Verizon coverage map doesn't tell me if I'm in an EVDO Rev. A area, so I need to look into that.

Next weekend I will be visiting two remote areas that I usually can get Verizon signal in without roaming. What I will do is flash back to 3.27 before the trip, and soft-reset in each of those areas to see if the long connection waits are limited to just where I live.

badutahboy, I don't know much about Cricket. Are they a virtual network (piggy-backing on another carrier's network)? Do they have any Rev A coverage where you are?

[badutahboy]

Originally Posted by GaryJohnson

I had briefly considered that the issue might be tied to the hardware (defective, or new revision), but since I'm on the same stock VZW radio / rom version as everyone else started with, and since the phone works perfectly fine under that configuration, I think the chances are pretty slim that it's hardware related.

I'm guessing that it might be some specific to my location or the tower I usually connect to, coupled with the fact that I'm using a potientially buggy radio version. The Verizon coverage map doesn't tell me if I'm in an EVDO Rev. A area, so I need to look into that.

Next weekend I will be visiting two remote areas that I usually can get Verizon signal in without roaming. What I will do is flash back to 3.27 before the trip, and soft-reset in each of those areas to see if the long connection waits are limited to just where I live.

badutahboy, I don't know much about Cricket. Are they a virtual network (piggy-backing on another carrier's network)? Do they have any Rev A coverage where you are?

I hadn't even considered the Rev. A issue... Let me know if it works faster for you in a rev. A area...

Cricket doesn't have Rev. A at all.. In fact, they just barely launched evdo.

As for their network.. they don't piggyback on anyone.. They've got their own infrastructure for their home markets, but they roam on both sprint and verizon... I'd love to switch to verizon, but my bill would jump to $200+/month, and Cricket offers unlimited everything for $50... so I can't justify it.

[bradleyem]

I get the incorrect password error also, BUT ONLY when attempting to connect through BT DUN. The data connection on the phone works fine. BUT, if I do try to connect through BT DUN, then my data connection on the phone stops working too. After a soft reset the phone works fine again. I thought that maybe it had something to do with the fact that I disabled Multi-NAI, but I reenabled it and same thing. That was the only thing that I could think of that would differentiate the BT vs phone data connection.

[kyppcgeek]

I have Verizon and the XV6800 and knock on wood I have had no radio issues.

[GaryJohnson]

bradleyem, while you're seeing the same error as me, it doesn't sound like it's the same problem.

At this point, I've conceeded to the need to call up VZW with every radio flash. My bigger problem is the long connection time.

I've noticed a few more threads with people complaining about this -- both on Sprint and Verizon. Some people appear to have no issues. I'm wondering what the difference is. I've suspected location; I've soft-reset in a few different cities around Cleveland but still have the same problem. I'm driving into New York tomorrow, so I'll try it there for testing purposes and report what I see. What I'm looking for is confirmation that this issue is not hardware specific. As soon as I check that out it's back to stock VZW ROM / Radio and a bluetooth GPS. Instability (and akward form factor) is why I ditched my i730; I can wait for an official release.

So, on the 3.27 radio, has anyone experienced an extremely (and abnormal) long wait to connect to a tower in one location, and no wait at all in another location?

[jbh00jh]

I had the same exact problem you have
with the phone searching for a signal
using 3.27 radio . I had no problem with
a signal when I had the 1.30 , 1.47 ,
& 1.40 radios so its not the location. Got
to be a glich in the 3.27 rom. - like a
Sprint phone trying to connect to a vzw
tower.
I switched back to the dcd clean rom & the 1.40 radio and the phone works
great with the 1.40 radio - always a good
signal & no data connection problems.
I'll just wait for the htc updates.

[blasphemous_prime]

there are major problems with this custom ROM in general, and with the one i downloaded for my mogul after i installed a hard-SPL and the RUU afterwards, the biggest issue i had to live with was the fact that i had to reconnect my data sessions manually every hour. along with that, there's also no official GPS in it as well, which is a bigtime waste of program memory (i start off at 17mb max with added programs after bootup). it's as bad as verizon customers taking long enough to search for the nearest tower with a custom ROM like this... and the worst thing in the world is that there's no way to get rid of that hard-SPL unlocker even if i tried the titan 1.00 relocker 100 times over...