Choose your cart
Choose your cart
Receive up to $504 promo credit ($180 w/Welcome Unlimited, $360 w/ 5G Start, or $504 w/5G Do More, 5G Play More, 5G Get More or One Unlimited for iPhone plan (Welcome Unlimited and One Unlimited for iPhone plans can't be mixed w/other Unlimited plans; all lines on the account req'd on respective plans)) when you add a new smartphone line with your own 4G/5G smartphone on an eligible postpaid plan between 2/10/23 and 4/5/23. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met.
$699.99 (128 GB only) device payment purchase or full retail purchase w/ new smartphone line on One Unlimited for iPhone (all lines on account req'd on plan), 5G Start, 5G Do More, 5G Play More or 5G Get More plan req'd. Less $699.99 promo credit applied over 36 mos.; promo credit ends if eligibility req’s are no longer met; 0% APR.
hard reset your device 5.0 scrambled your ops also wipe cache while your at it find a pc and repair your ops with upgrade assistant with vzw a rep should offer a hyperlink
The rest your on your own do all of what I have suggested still broken have them ship off a replacement
Also don't check edit screen capture it will create 2 captures instead of one
I'm having the same issue. Researching led me to this board. Also, on occasion I'm receiving a "roaming" status in the top left corner.
Tried that, and it made no difference at all. Any more ideas?
I am still struggling with this. I have 0 signal. I have to reboot if I
want my cellular connectivity to re-negotiate with the network.
On Apr 30, 2015 10:57 AM, "The_Disturbed1" <forums@verizonwireless.com>
Turning airplane mode on and back off off is not resolving the issue.
Verizon are you going to fix this or what?
As you suggested, I uninstalled the updates for the Android System Webview, and my phone was able to reacquire a phone signal without a reboot after a service loss. Unfortunately it did not help my 4G radio since it wouldn't reacquire a signal until I rebooted. So although removing the updates seemed to help a little it did not fully resolve the problem.
I am also having the exact same issue as described by everyone else here. With so my reports this can't be coincidence.