Are you having trouble staying in 3G (getting stuck in 1X), VZW TP2 folks?

[janko10]

Originally Posted by jason559

I have a Sprint TP2, I couldn't find another thread for Sprint users. But, I am having this issue on this unit. Exchanged the first two TP2s for other issues, but the first two didn't have this issue. The third one does. It has the other normal issues, dead pixels, bad ear piece sound, but I know those are the norm.

But, if I travel around town, it gets stuck in 1x mode and the only way to get out of it is to hold down the end key. If I go into communications tab and turn off data and back on that doesn't fix it.

So, not sure if I should contact Sprint for an exchange or if I should wait to see if there is some sort of fix. I doubt they are going to be happy about another exchange...

Do you know if you're roaming on VZW when you have the problem? Another Sprint user said he's having this issue when he roams on VZW.

[8notime]

Originally Posted by jason559

I have a Sprint TP2, I couldn't find another thread for Sprint users. But, I am having this issue on this unit. Exchanged the first two TP2s for other issues, but the first two didn't have this issue. The third one does. It has the other normal issues, dead pixels, bad ear piece sound, but I know those are the norm.

But, if I travel around town, it gets stuck in 1x mode and the only way to get out of it is to hold down the end key. If I go into communications tab and turn off data and back on that doesn't fix it.

So, not sure if I should contact Sprint for an exchange or if I should wait to see if there is some sort of fix. I doubt they are going to be happy about another exchange...

Based on my past experience with them, I can't imagine trying to deal with Sprint on this issue.

[jason559]

Originally Posted by janko10

Do you know if you're roaming on VZW when you have the problem? Another Sprint user said he's having this issue when he roams on VZW.

No, no roaming, I have roaming turned off (no roaming plan).

[janko10]

Originally Posted by jason559

No, no roaming, I have roaming turned off (no roaming plan).

Well if that's the case then we're probably looking at a physical hardware problem with the radio itself or another component in the phone.

[NotATreoFan]

My phone has now been in 3G for 15 hours, which is the longest yet. Here's what I did:

1. Download and flash the VZW ROM that is one step below the ship one.
2. *228 once
3. Download and flash the VZW ship ROM
4. *228 twice (option 1 and 2)

I ran a mobile speedtest at DSLReports, and I went from 120kbps to 2400kbps.

I am still going through with my phone exchange since I'm also having issues with call quality through the handset speaker, so I will have 2 full days to test this fix.

[8notime]

Originally Posted by NotATreoFan

My phone has now been in 3G for 15 hours, which is the longest yet. Here's what I did:

1. Download and flash the VZW ROM that is one step below the ship one.
2. *228 once
3. Download and flash the VZW ship ROM
4. *228 twice (option 1 and 2)

I ran a mobile speedtest at DSLReports, and I went from 120kbps to 2400kbps.

I am still going through with my phone exchange since I'm also having issues with call quality through the handset speaker, so I will have 2 full days to test this fix.

Thanks for posting. Can you tell me what the radio version is in that ROM? Any other functionality that is not there that you know of? I was considering flashing to that ROM also, but wasn't sure what to expect from it. I've gone 15 hours before, but that's still a good sign if you haven't.

[NotATreoFan]

Originally Posted by 8notime

Thanks for posting. Can you tell me what the radio version is in that ROM? Any other functionality that is not there that you know of? I was considering flashing to that ROM also, but wasn't sure what to expect from it. I've gone 15 hours before, but that's still a good sign if you haven't.

1.88.07WV is the radio on my phone now.

For the downgrade, I flashed: "RUU_Rhodium_W_VERIZON_WWE_1.18.605.6_RS_1.87WV_NV _VZW_1.50_0529_PRL58002_Ship"

For the upgrade, which is the same as the shipped ROM, I flashed: "RUU_Rhodium_W_VERIZON_WWE_1_1_.18.605.12_RS_1.88. 07WV_NV_VZW_1.65_0811_PRL58002_Ship"


Both ROMs are available here.

[8notime]

I should have read your first post closer. I missed the fact that you downgraded and then upgraded again.

[dshay]

Been having the issue from the start. Thought I was "cured" on Friday, survived pretty much the whole weekend except for 1 20 minute period of 1x-ness. Flew to my work-site today, took the phone out of flight mode and bang, back to 1X. Did the usual *228 1, *228 2, battery out rituals, all to no avail.

Called Verizon again, who I had called on Friday and they were going to get me a new phone until they realized they were sold out. Told them that "others" were experiencing the same problem. She only found evidence of one other ticket in the system. I wonder how many of the others responding to the poll in the positive have reported the issue to Verizon? Can those who have please respond? If so, with your ticket # if you don't mind? [I forgot to get mine, but will as soon as I call them back].

Had me go into ##DEBUG to check some things, but then had me go into ##778 and edit mode, on the Home SID/Home NID screen, changed my first value from a "21" to a "73" which she indicated as a "more restrictive" value. After a (another...) reset, this put me in 3G. Not sure if this will stick or not, just wanted to report in...

For those who have had Verizon do anything, what have they done?

[8notime]

Originally Posted by dshay

but then had me go into ##778 and edit mode, on the Home SID/Home NID screen, changed my first value from a "21" to a "73" which she indicated as a "more restrictive" value. After a (another...) reset, this put me in 3G. Not sure if this will stick or not, just wanted to report in...

It sounds like they had you change your SID from once in Michigan to one in Ohio. Do you have a Michigan # but reside in Ohio? I have a similar situation on my phone where my SID matches where my phone # came from but I actually reside in a completely different state.

BTW: If what they said about there only being 1 other trouble ticket opened about this is true, that ticket would have to be mine, because I definitely opened one.