[largeselection]

So I did manage to track down a nexus at a vzw store that would sell it to me for full price. Hooray!

Now something strange just happened that I can't recall reading about...my nexus is charging at the moment on my desk and I just looked over at it because the screen turned on. Upon closer inspection I saw a phone icon in the notification pane, so I dragged it down to check it out and it said it was connected to a phone call at the number "22899".

Anyone else's nexus automatically dialing the activation line?

[largeselection]

So doing some research leads me to believe that the phone is automatically trying to update the PRL. Has this happened to anyone else?

What PRL do you all have listed? Settings, About Phone, Status -> PRL

I have 52642, is that not what it should be?

Bad news is that I have horrible service in my office so it can't complete the call successfully. Should I try and go outside where I have service and just dial *22899 myself?

[Laramie]

I have PRL 15908. My phone keeps doing the same thing. Seems like it happened the same time friday morning and again this morning.

It's also only happening when I'm at home where we have horrible service. Most spots will go between no service at all and 1 bar.

Hopefully somebody else has more info. I also wonder if updating while in a good service area would do any good. It's annoying that it will just auto dial and then even when I hit "END" it will redial again and I can only get it to stop with a reboot.

[Andrew Ruffolo]

So doing some research leads me to believe that the phone is automatically trying to update the PRL. Has this happened to anyone else?

What PRL do you all have listed? Settings, About Phone, Status -> PRL

I have 52642, is that not what it should be?

Bad news is that I have horrible service in my office so it can't complete the call successfully. Should I try and go outside where I have service and just dial *22899 myself?

Are you using the gnex on verizon? Weird PRL. Mine is 15098

[Hosehead]

15098 here in PA.

Sent from my Galaxy Nexus using Tapatalk

[Salacon]

I had this happen on my Verizon Galaxy Nexus as well. It happened soon after I received and activated it. It tried to do it quite a bit, but it finally stopped trying and hasn't done it since, so I suppose it achieved what it wanted to do.

My PRL is also 15098. No idea what it was before, though, if it was different at all.

[protonchain]

PRL is 15098 here in socal

[sdiego]

I am in San Diego, Ca and mine says 15095 strange.

[CBCstillmatic]

Mine is 15098 here in NJ. I can't even call *22899 or *228 it just says call not sent so I can't update roaming manually anyway unless there is another way?

[hiwayfuzz]

I thought we were not suppose to dial any if the *228 numbers on 4G phones..now phones are doing it on their own...nice

Sent from my Galaxy Nexus using Tapatalk

[CBCstillmatic]

I thought we were not suppose to dial any if the *228 numbers on 4G phones..now phones are doing it on their own...nice

Sent from my Galaxy Nexus using Tapatalk

Ah did not know that! My first 4G phone...thanks now I know and knowing is half the battle

Sent from my Galaxy Nexus using Tapatalk

[SoCoolCurt]

mine was doing the same thing just a little bit ago. I'm sitting here watching football and noticed the screen was on. When I picked it up, I noticed a call in progress and pulled down the notification window and the screen shut off. It did this 2 or three times (the screen turning off) until I finally was able to end the call. Then it just dialed the number again when I set it down and I had to the same dance but this time I listened to it instead of ending it and it said it was provisioning and had the same *228 music from 3G phones. After about 2 minutes it ended the call on its own and hasn't done it since. I can't tell if its fixed the voice/data drop issue I was having or not and it won't let me call *22899 manually (or *228). My PRL is 52642 in Maryland (not sure what it was before). All I know it succeeded in doing is creeping me out...

[largeselection]

Oddly enough it must have completed one of those calls successfully because I'm now at PRL: 15098

[Premium1]

Are you using the gnex on verizon? Weird PRL. Mine is 15098

Mine is also that prl.

[JediJesus95]

My wifes did that right after activation. Weird.

[quintilis]

mine is 15086 in the Bay Area, weird

[Tom in Bristol]

Did a little digging re PRLs (Preferred Roaming Lists) and Phil did a short article last May:

http://www.androidcentral.com/whats-prl

May or may not be relative to poor reception/radio performance.

There are a couple links in the Comments to the article (Yeah, I know...one of them is Wiki - shrug).

[Hondo_Lane]

interesting... mine just did this and i searched that number and saw this thread. I have no idea it anything updated or not...

[ohiomoto]

Mine did it once.

[yapkuen]

Pure, rampant speculation here by someone who doesn't even own a Galaxy Nexus, so take it with a bucket of salt: I wonder if the battery problems and the auto-dialing *228 are related? Perhaps a lot of people are having their batteries drained by their Galaxy Nexi constantly trying to dial out for provisioning?

[Laramie]

***Tinfoil Hat Time***

My phone did this about 4 separate times, each time my phone was on my nightstand which is an absolute deadzone. Yesterday, I finally walked to the kitchen, and the call connected and the programming music. Phone hasn't tried to dial since.

Interesting note, I can now steadily send texts from areas of the house/property where I couldn't when I first got my GN. Not sure what happened, but maybe the roaming list does have something to do with data/towers/etc.

Whatever the case, I have noticed a slight increase in ability to send texts and make/receive calls in spots that used to be dead.

[packisback]

My phone first did this a week ago when Verizon had the nationwide data outage. I figured it was related to that and thought nothing more of it until today. I am working this week in a remote area with absolutely no cell coverage (no voice, 1x, 3g, or LTE). The phone tried to call *22899 but of course couldn't connect to anything. It then continued to try to call *22899 over and over again and each time I would end the call knowing it couldn't connect. The phone continued to try to call until I finally got annoyed and shut it off.

Has anyone been able to get an answer from Verizon as to why this is happening. They act confused when I explain it to them and ask if I want to exchange the phone for a new one (which I don't because I don't think it is something wrong with my individual phone).

[daso]

Mine did it two times right around the outage and never happened again. I called VZW and they said it was due to the GN trying to find service. Load of BS, but it never happened again.

[joat25]

ditto here, even posted about it around a week ago. seemed to do it several times after i got it (which was also around the time of the 4g outage).
i assumed it was related to an incomplete activation or update.
hasn't done it for about 2 weeks so i imagine it got what it needed.

[sdiego]

Since it won't let you manually dial that number, I learned if you just program the number as a contact, it then will dial out. I am here in San Diego Ca. and I went from I think 15095 to 52616. I may try again in a different part of the city and see if it changes again. I don't see really much difference in my case.