in the threaded text messages, when i text it will show my time, but when i receive a text it will show as an hour earlier...anyone know how to fix?
anything??????????
Is it only from a certain person? or anyone who sends you a text. I would say it's a time zone issue, or DST issue on either yours or the other persons phone.
BTC
BillThyCat said:
Is it only from a certain person? or anyone who sends you a text. I would say it's a time zone issue, or DST issue on either yours or the other persons phone.
BTC
Click to expand...
Click to collapse
its from everybody....but those people happen to be in a different time zone an hour behind me...not sure if that matters but i will try to text someone in the same timezone as me
i tried texting someone in my timezone and i still have this error.....any ideas on a fix?
you sure your timezone is correct? dunno why else it would be doing that...
I'm not near my phone, currently, but would a Daylight Savings box be checked/unchecked?
My guess would still be a timezone issue, is your phone activated in a different time zone than where you are currently at? Maybe when it passed thru their switch it picks up the time zone from your account and ignores what the phone tells it.
Other than that, I am out of ideas.
BTC
BillThyCat said:
My guess would still be a timezone issue, is your phone activated in a different time zone than where you are currently at? Maybe when it passed thru their switch it picks up the time zone from your account and ignores what the phone tells it.
Other than that, I am out of ideas.
BTC
Click to expand...
Click to collapse
that may be it, because i am from texas but i am stationed on CT and tx is an hour behind CT...only weird thing about it is that this happened once before, but the issue went away somehow and i dont remember if i did something for it to go away or if it just did it by its self
I have this same problem as well with my mogul. I was recently at my cottage where I tend to roam and where there is no EVDO coverage either(only 1x), I was texting a friend of mine with a diff. area code but still in the same time zone and there was a 3 hour difference each time he replied. Hope someone can come up with a fix, kind of annoying.
niketom843 said:
I have this same problem as well with my mogul. I was recently at my cottage where I tend to roam and where there is no EVDO coverage either(only 1x), I was texting a friend of mine with a diff. area code but still in the same time zone and there was a 3 hour difference each time he replied. Hope someone can come up with a fix, kind of annoying.
Click to expand...
Click to collapse
Did you ask him to verify his TZ was set correct on his phone?
BTC
well i had to go back to verizon stock rom to get my data working and then when i updated back to 3.2.6 is was working....no more complaints from me
Just updated from the newest stock Telus ROM to DCD 3.2.6 and sent myself a text using the Telus website and the timestamp was correct.
BillThyCat said:
Did you ask him to verify his TZ was set correct on his phone?
BTC
Click to expand...
Click to collapse
yes, his time zone was correct.
Related
Hello,
I looked around a bit about finding the A-key. I just had my phone remotely fixed for the authentication problem, but they never told me the A-key even though I asked.. I was wondering if there was a way to pull it off the phone..
This is verizon, the akey is blank in EPST.. I tried CDMA Workshop and it got a bunch of crazy info but errored out on when getting the a-key. I also looked through qpst but it doesnt look like a-key is in there(under service programming).
Anyone have any ideas? Im about to start flashing and Id hate to be on the phone with verizon for another couple of hours every time this happens.
Before I called verizon I even tried generating my own Akey with that akey calculator but that didnt really work..
Thanks
some verizon service areas do not use an akey stored on the phone but instead they authorize in their sytem based on your esn and some identifier your radio sends them. This is the way it is in my area. the verizon tech told me all of their systems will be moving this way, supposed to help prevent phone cloning and some other security issues.
I was assured that all i would need to do is call if it tells me phone not authorized and they will correct it.
rmancl said:
some verizon service areas do not use an akey stored on the phone but instead they authorize in their sytem based on your esn and some identifier your radio sends them. This is the way it is in my area. the verizon tech told me all of their systems will be moving this way, supposed to help prevent phone cloning and some other security issues.
I was assured that all i would need to do is call if it tells me phone not authorized and they will correct it.
Click to expand...
Click to collapse
Ah I see so you're saying that it actually is blank not just hidden away..
Alright, thanks.
I gotta say im thinking this is true. I just flashed my phone to NexVisions rom and cant activate so im gunna have to wait till morning to get it activated because tech support stops working in the middle of the night i guess. If its as simple as it sounds, I will report back as such.
Soooo I left the phone plugged in on the otherside of the house (I figured I cant get calls why bother bringing it im my room) and it wasnt able to make calls i figured no out no in so i shouldnt be able to get calls. I wake up this morning to 16 missed calls because someone called in at work and Im the only one who can work.... it activated at some point in the night. *228 worked just fine... completely baffled... just worked out of the blue, does this have something to do with recieving calls? any ideas?
blksprk said:
Soooo I left the phone plugged in on the otherside of the house (I figured I cant get calls why bother bringing it im my room) and it wasnt able to make calls i figured no out no in so i shouldnt be able to get calls. I wake up this morning to 16 missed calls because someone called in at work and Im the only one who can work.... it activated at some point in the night. *228 worked just fine... completely baffled... just worked out of the blue, does this have something to do with recieving calls? any ideas?
Click to expand...
Click to collapse
When it wasnt authenticated before i called verizon I got the calls but I couldnt answer them and they would be missed calls after one ring or so.. Maybe thats what was happening in ur case..
Could be that verizons systems updated themselves or something..
Ok, I jumped into upgrading the ROM on the xv6800 I picked up from Verizon earlier today. After lots of looking around, I determined that I needed and located the SPL / bootloader (Olipro 2.40), a custom ROM cooked up courtesy of DCD, and the 3.27 Radio ROM.
Got the bootloader going, upgraded the ROM and got the dreaded locked Verizon screen. Didn't take long to figure out I needed to load the Radio ROM so I then got that loaded.
Immediately I started getting the message that my phone needed to be programmed, so I started to dial *228 but my phone just said "Call Lost" or something along those lines. Then I noticed it was just searching for signal continuously.
Weird thing is, after a LONG while (as I searched this forum for a couple of hours and tried and re-tried flashing the ROMS) I had signal, I did the OTA programming and upon reboot lost signal again.
I have now used the relock tool to return to the official Verizon ROM and I now have signal again. However, I have to call in for the AKEY.
Anybody else experience complete loss of signal? (not the data drop issue)
Edit: Just a side note, I called VZW tech support and basically admitted to flashing the ROM and flashing back. He wanted to know how I knew about the AKEY...told him I had been in wireless for years (true, but years ago as well) and was very knowledgeable. He shrugged it off and was happy to give me the key. I'm back up and running, but a bit gun shy to go flash the ROM again tonight. What time does VZW tech support shut down??? LOL
Im on sprint but changing my Mobile IP Settings helped me fixed this same problem.
limezednem said:
Im on sprint but changing my Mobile IP Settings helped me fixed this same problem.
Click to expand...
Click to collapse
Did you copy these from the EPST before you flashed the ROM?
Oh yeah, forgot to mention that I re-entered the MSID and the MDN.
Still can't connect to data....probably have to call tech support again soon. blah...
try using the msid and reset your ip to Mobi'e Prefoired
sandiegodude said:
try using the msid and reset your ip to Mobi'e Prefoired
Click to expand...
Click to collapse
Can you explain a bit further? Are you talking about MIP_MODE? That is set to "Mobile IP Preferred"
Ok, so I tried again and it happened again. I'm sitting here looking at a phone that is constantly searching.
This time the MSID and MDN are intact.
Any suggestions?? Which IP settings would I be checking and what should I be setting them to?
And as before, I now have signal about 20 minutes later (faster this time than last night.)
I need to do an OTA programming, I'm sure it will die again after the reboot.
Programming now.....rebooting.....and it's dead again. Any thoughts?????
Edit: Almost 20 minutes later again and I have signal, but not authorized again...guess I'm calling support for the A Key once more. Soft reset takes signal offline again.
I'm running a NexVision ROM based on DCD's 2.2.4, Sprint network. This issue happened to me three times, but not until after I loaded PRL 60711 (with Sprint). Was probably just a coincidence, though. Since then, it's been fine for a week.
Well, it came back up again. So it looks like I've narrowed it down to just a long delay in acquiring signal.
I'm on the phone w/ VZW now getting my A Key once again.
I dont know much about verizon but isnt the Akey always the same? Also, try toggling the MIP back and forth a few times. That has worked for some of us.
The A Key changes each time on VZW from what I understand. That comes from sources on here as well as VZW techs. I didn't write it down today and the one I did write down last night is @ the office so I have no way to compare for a definitive answer.
What would I toggle the key back and forth from/to? Can you explain that in a bit more detail? THX
Edit: Is this what you were suggesting? Under M.IP Settings
Changed MIP_MODE to Mobile IP Only then reset
Changed to Simple IP Only then reset
Changed to and back to Mobile IP Preferred
Tried and no go.
Sorry to hear it didn't work. It seemed to have helped a couple of us in this thread. Maybe it might take a couple more tries. But we all seem to be having the same problem.
Just found this post:
http://forum.xda-developers.com/showpost.php?p=1944961&postcount=1
Tried again...no good. Maybe I'll try a few more times just for posterity.
Geckotek said:
Just found this post:
http://forum.xda-developers.com/showpost.php?p=1944961&postcount=1
Tried again...no good. Maybe I'll try a few more times just for posterity.
Click to expand...
Click to collapse
Well, good luck! Haha
limezednem said:
I dont know much about verizon but isnt the Akey always the same? Also, try toggling the MIP back and forth a few times. That has worked for some of us.
Click to expand...
Click to collapse
Verizon isn't using the a-key (at least not in all locations) to validate the phone. They have some other authentication in house that gets reset by them. My a-key is blank, but after the update, I had to authenticate my phone to be able to make calls.
It appears they use both because they have given it to me twice now.
But back to the task @ hand...does anybody have a guess at why it would take 15+ minutes to acquire signal?
I did find one temp solution on my VZW phone:
after a reset, while the phone is searching for a signal, I went to the phone func and entered *22803. It then finds a roaming signal and starts "programming". At that point I hit call end and it picks up the signal and goes to EV, full bars. The phone says programming unsuccessful, but if I close the phone and re-open it, everything is fine.
pkp190 said:
I was also having this problem, what I did that fixed the problem was i reentered the MSID and MDN in the ##MSL# screen. Then allowed the phone to reset. from that point forward I get signal as soon as it powers on from reset. Hope this helps.
Click to expand...
Click to collapse
Thanks pkp190!!!!
Edit: Spoke too soon. After another *228 the problem has returned and trying it again didn't fix it this time.
radio
It seems to my feeble mind that the problem your are experiencing is caused by the flaky 3.27 radio rom. Its the very reason I have, unfortunately, given up on the gps roms. Some people report no problems at all, and others report serious issues. For me it was a problem so I gave up and went back to dcd1.7.0 which I find to be the best rom yet.
Some people have reported that toggling MIP settings (see http://forum.xda-developers.com/showpost.php?p=1944961&postcount=1) helps but for me it didn't work. You could try that and see if it helps your case.
Others have reported that recooking a new rom with fewer OEMs might solve the problem. Once again, for me, it didn't work.
Otherwise, you might have to just wait for a new radio to be "officially" released before gps is a reality for you.
Geckotek said:
The A Key changes each time on VZW from what I understand. That comes from sources on here as well as VZW techs. I didn't write it down today and the one I did write down last night is @ the office so I have no way to compare for a definitive answer.
What would I toggle the key back and forth from/to? Can you explain that in a bit more detail? THX
Edit: Is this what you were suggesting? Under M.IP Settings
Changed MIP_MODE to Mobile IP Only then reset
Changed to Simple IP Only then reset
Changed to and back to Mobile IP Preferred
Tried and no go.
Click to expand...
Click to collapse
I think that in areas where the A-key is still used you can consider the a-key like a serial number for a piece of software (in this case ur authenticating into the verizon network).. there is an algorithm based on your ESN and any random number of keys can be generated to fit the algorithm and be accepted.
In other words although they may give you different A-keys every time that you call all of them are equally valid and can be entered to authenticate into the network.
Its like a keygen for pirated software when u can keep hitting that generate button to make random keys but all of them work in theory(not that I have ever contemplated using or used pirated goods)
Hope you guys/gals can help me out with this one!? I really don't want to flash back to Alltel's outdated rom.
Everything has been working great! The phone has no problems making/receiving calls, internet doesn't drop while downloading files, GPS has been really great, IR beams, bluetooth, and so on are all working better than they every have.
But, as soon as I leave my home area (Lynchburg, VA) the phone cannot make/receive calls, and the internet will not connect. For example I am traveling today in Roanoke, VA (normally solid triangle now flashing) and I try to make a call the recorded voice (Verizon) says that it cannot authenticate my phone. I called Alltel customer service and he could not see my phone either. What's funny is if I dial *611 I can talk to customer support. None of these things were happening until the upgrade.
Thanks for your help! Hope I did not leave anything out. If you have any questions, please ask!
Do you have the latest alltel prl?
gcincotta said:
Do you have the latest alltel prl?
Click to expand...
Click to collapse
I believe I do? It says I have 30031.
Thanks for the quick reply, keep them coming! I really need to get this fixed. I didn't realize how much my job depends on this damn phone! lol
yeah agree with gcincotta, check your prl. should be 30031 i believe. then check your epst. ##778 send. click on edit. 000000. when you are in your nam settings, check to make sure that everything looks like it should. i would say especially check the SID and make sure its for your local area. then check your security settings, make sure the HDR pass is your ESN. I cant think of anything else really.
have you tried doing a *228
update the roaming first, let your phone restart.
start again, update the programming with option 3
the only other thing i can think of is that the ESN might be jacked. look at your phone info (just in settings) and check the ESN, make sure it matches whats on the box that your phone came with. i have heard of these flashes sometiems erasing the ESN to 000000
It's not the PRL...
I went through this a couple weeks ago, it's a "security issue" with your account and Alltel's roaming partners. You need to call 1-888-295-3569 and tell them you are getting that recorded message when out of your "home area". They will ask a couple questions like "are you roaming now", "are you on that phone now" and SHOULD take you less than 5 minutes to get squared away.
YMMV, but they fixed me up quick.
I got this information from this post so proper credit is given: http://forums.wirelessadvisor.com/491543-post10.html
I am a Lynchburg, VA alltel 6800 user as well. I have been running the DCD 3.0.1 rom for the past week or so. I haven't had any issues, and I was in roanoke monday evening.
Have you checked the HDR AN AUTH Password in epst?
Send me a pm,
Marlin
Does anyone know about the PRL?
I am sitting in an area right now in New Hampshire where there is no Alltel coverage. Because I used to be VZW cust with Blackberry I know that in this house VZW has full coverage with EVDO data available. I also know that the Sprint Towers can been seen by my phone but just barely and there is no EVDO available in this area with Sprint.
According to Alltel the PRL is setup to have Sprint be the first choice for Roaming and there is no way to change it.
Does anyone know if there is a way to set my PRL to have VZW as the first Roaming choice?
Mr.Ellsworth
Mills00013 said:
yeah agree with gcincotta, check your prl. should be 30031 i believe. then check your epst. ##778 send. click on edit. 000000. when you are in your nam settings, check to make sure that everything looks like it should. i would say especially check the SID and make sure its for your local area. then check your security settings, make sure the HDR pass is your ESN. I cant think of anything else really.
have you tried doing a *228
update the roaming first, let your phone restart.
start again, update the programming with option 3
the only other thing i can think of is that the ESN might be jacked. look at your phone info (just in settings) and check the ESN, make sure it matches whats on the box that your phone came with. i have heard of these flashes sometiems erasing the ESN to 000000
Click to expand...
Click to collapse
Everything looks fine, but where do I find the HDR pass? I see the ESN (Hex,Dec). I will have to check the ESN with the box, but it is not 000000.
I did the *228 option 2, but not the option 3. Since everything was working in my home area, I thought it was ok. I will give that a try when I get back home.
And yes, I used to be able to make calls from here. I travel 4 states, and have never had a problem at any of my stores.
Thanks for the help!
jake1s said:
It's not the PRL...
I went through this a couple weeks ago, it's a "security issue" with your account and Alltel's roaming partners. You need to call 1-888-295-3569 and tell them you are getting that recorded message when out of your "home area". They will ask a couple questions like "are you roaming now", "are you on that phone now" and SHOULD take you less than 5 minutes to get squared away.
YMMV, but they fixed me up quick.
I got this information from this post so proper credit is given: http://forums.wirelessadvisor.com/491543-post10.html
Click to expand...
Click to collapse
Did you call them on your phone or from a landline? The only way I can call them from the phone is *611. I have been reluctant to call them again, because I thought they might ask if I have flashed my phone?! If nothing else works, I will have to.
Thanks!
I actually waited until I got back into my home area and called since I couldn't call out and didn't have another phone handy, but he said if you call from another phone WHILE roaming it makes it easier for them to verify that's the problem.
If you're still out I'd grab a landline or a friends phone, shouldn't take you long. After they are done, and they will probably tell you, you'll have to power cycle the phone.
EDIT: He didn't even question the radio version or ANYTHING about me messing with my phone. Just did his thing, sure enough I now call out in areas I couldn't before.
jake1s,
I was wondering that, I thought they might have a way of telling. Did not want to lose my warranty just yet. lol
Everyone else,
Thanks for all your help, I will keep you posted on what happens. I'm sure this had to happen to others, and maybe they just don't know it yet since they have not traveled out of their home area? Maybe it's just a Alltel/Verizon thing, not Alltel/Sprint.
Thanks!
hinds73 said:
jake1s,
I was wondering that, I thought they might have a way of telling. Did not want to lose my warranty just yet. lol
Everyone else,
Thanks for all your help, I will keep you posted on what happens. I'm sure this had to happen to others, and maybe they just don't know it yet since they have not traveled out of their home area? Maybe it's just a Alltel/Verizon thing, not Alltel/Sprint.
Thanks!
Click to expand...
Click to collapse
Happened to me with Alltel/Sprint. I called Alltel, said I had the message, told them where I was and my phone number. It was fixed in 2 minutes flat. I called from a coworkers phone.
jake1s said:
It's not the PRL...
I went through this a couple weeks ago, it's a "security issue" with your account and Alltel's roaming partners. You need to call 1-888-295-3569 and tell them you are getting that recorded message when out of your "home area". They will ask a couple questions like "are you roaming now", "are you on that phone now" and SHOULD take you less than 5 minutes to get squared away.
YMMV, but they fixed me up quick.
I got this information from this post so proper credit is given: http://forums.wirelessadvisor.com/491543-post10.html
Click to expand...
Click to collapse
Well, this is what worked. I'm not sure exactly what he did, but in about 2 or 3 minutes it was fixed.
Thanks for all the help!
So, all of my family just signed up for AT&T from T-Mobile and most of us got Galaxy S II's from Amazon for $0.01 (good deal). However, my brother and I are both having data issues. We'll be connected to HSPA+ with 4/5 bars, but sometimes anything that requires data (webpage, email) won't load, an there will be minimal data activity in the status bar. I have to click links multiple times for a connection to finally occur (if not wait a minute). Other times, I've waited so long I've turned airport mode on and off. My brother tested his GSII next to someone's Atrix, and their Atrx loaded a webpage without any latency, while my brother's browser just sat there with the initial loading bar, no network activity.
I haven't done much testing/replacing the ROM/radio, because methinks the stock ROM shouldn't be having this problem in the first place. Can I check logcat w/o root?
Could this be a cellular issue? We ported our numbers from T-Mobile, and still have the T-Mobile account. I never had to activate my AT&T phone when I got it from Amazon (came with SIM card, worked out of box). I also noticed strange behavior. I had both my old T-Mobile phone and my new AT&T phone on at the same time, and my T-Mobile phone rang, even though I had supposedly ported my number to AT&T. So if that can happen maybe it's some crazy SIM issue going on?
Any advice or pointers of assistance from the GSII forum would be appreciable.
Thanks!
Sounds like the AT&T sim card is not activated, or fully activated. Id call them and verify. Also make sure that you are on a 4G data plan... that can also cause issues with data.
When you port a number it can take up to 48 hours to fully port the number. Until it is done both phones will ring. The reason for the bad satanist that even though it works out of box you have to call Att to set the account up the rest of the way. I can't tell you how many people came into my store due to this.
zelendel said:
When you port a number it can take up to 48 hours to fully port the number. Until it is done both phones will ring. The reason for the bad satanist that even though it works out of box you have to call Att to set the account up the rest of the way. I can't tell you how many people came into my store due to this.
Click to expand...
Click to collapse
Bad satanist?
zelendel said:
When you port a number it can take up to 48 hours to fully port the number. Until it is done both phones will ring. The reason for the bad satanist that even though it works out of box you have to call Att to set the account up the rest of the way. I can't tell you how many people came into my store due to this.
Click to expand...
Click to collapse
You work for AT&T? That is funny on so many levels.
Red5 said:
You work for AT&T? That is funny on so many levels.
Click to expand...
Click to collapse
Lol, that is hilarious and awesome at the same time. Talk about best android sales rep!
Sent from my páhhōniē
Update: Just took phone out of pocket and loaded cnn.com. Tooks ~20 seconds before page even started loading (beyond initial bit of browser loading bar). Both up/down HSPA+ became active at various points in the time frame.
This seems to be a common occurrence. I remember talking to an AT&T rep from Georgia or something because my dad called her to get our account in order. She called my phone, as was like "Oh you're talking on your GSII? -- it must already be activated then." She made no indication that it still needed to be activated.
Sorry damn keyboard. I ment bad data connection.
I used to run a small retailer but still do freelance support for a few of the Att stores around town. You would be amazed how many store managers have no idea about the products they sell lmao
Call Att and get tech support and have them refreash your connection to the data servers. That should fix you right up.
zelendel said:
Sorry damn keyboard. I ment bad data connection.
Click to expand...
Click to collapse
Bad satanist is much better
Sent from my páhhōniē
Originally Posted by zelendel
Sorry damn keyboard. I ment bad data connection.
Click to expand...
Click to collapse
Bad satanist is much better
Sent from my páhhōniē
Click to expand...
Click to collapse
You win.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
I suddenly can't send or receive any text messages. I don't have a clue what caused it. Last night I installed the app wifikill and used it for a few minutes which did cause my phone to reboot and for some reason made it look for a profile update, firmware update and prl update. Everything else seems to be working, so I'm not sure what's going on. I already attempted to delete everything in my phone and restore from a nandroid backup before this happened, and the problem still persist. Any ideas of what could have caused this and how to fix it?
I don't know if it is related or not, but I've been having texting issues with the LTE as well. Sometimes they go through, sometimes they don't and I end up turning airplane mode on, then off after waiting 30 seconds.
I've also been having MAJOR delays in getting sent messages (some are coming in more than 2 hours after they were sent to me according to the time stamps on the incoming messages)
It is really driving me crazy (oh, and along with data crapping out as well with no rhyme or reason as to why and when).
fastamx79 said:
I don't know if it is related or not, but I've been having texting issues with the LTE as well. Sometimes they go through, sometimes they don't and I end up turning airplane mode on, then off after waiting 30 seconds.
I've also been having MAJOR delays in getting sent messages (some are coming in more than 2 hours after they were sent to me according to the time stamps on the incoming messages)
It is really driving me crazy (oh, and along with data crapping out as well with no rhyme or reason as to why and when).
Click to expand...
Click to collapse
+1 to this issue.
That's no really the same problem I'm having. I simply can't send or receive text messages at all. It just suddenly started happening with no warning, so I'm not sure what caused it or how to fix it. Please let me know if anyone else is having this problem. If I don't hear anything soon, I'm thinking about unrooting my phone and re-locking the bootloader and taking it to sprint to see if they can do anything with it.
NoClemency said:
That's no really the same problem I'm having. I simply can't send or receive text messages at all. It just suddenly started happening with no warning, so I'm not sure what caused it or how to fix it. Please let me know if anyone else is having this problem. If I don't hear anything soon, I'm thinking about unrooting my phone and re-locking the bootloader and taking it to sprint to see if they can do anything with it.
Click to expand...
Click to collapse
I would run the ruu which will put you back to stock and see if the problem remains.
njfoses said:
I would run the ruu which will put you back to stock and see if the problem remains.
Click to expand...
Click to collapse
Sadly I already did that, and it still wasn't able to send or receive text messages. But here is the real kicker. Soon as I made a call to one of my friends who also knows a lot about phones to ask him if he had any suggestions, all the text messages that I made that wouldn't send all sent. By simply making a phone call, the phone must of connected with the sprint towers and made it start working. Super bizarre, but it's working again. So now I'm in the process up setting everything back up. Thank you Titanium Back up.
I'm currently experiencing modified version of your problem. I can't send text messages, but I can receive them. The only messages I can send are picture messages because they are looked upon as data.
NoClemency said:
Sadly I already did that, and it still wasn't able to send or receive text messages. But here is the real kicker. Soon as I made a call to one of my friends who also knows a lot about phones to ask him if he had any suggestions, all the text messages that I made that wouldn't send all sent. By simply making a phone call, the phone must of connected with the sprint towers and made it start working. Super bizarre, but it's working again. So now I'm in the process up setting everything back up. Thank you Titanium Back up.
Click to expand...
Click to collapse
Are you new to Sprint? Text messaging on Sprint has done this on several different devices for the past two years (since I joined Sprint). And when I make a phone call several tend to come through.
Oddly enough this doesn't happen in Utah when I go to visit, only Puerto Rico (where I live).
Try making a phone call and updating your prl within Sprint Zone. That fixed it for me.
I tried EVERYTHING to fix my phone. I rooted, unlocked and installed 2 different ROMS. None helped. I had to update my PRL every hour, and sometimes that didn't help either. I wiped everything, unrooted and relocked, ran RUU and went to Sprint. They replaced my phone. They are not allowed to work on these phones currently, so you'll either get a new one or a reconditioned one. Because I signed up for insurance, I got a new one.
I have not had any of the same issues since getting a new one. To me, it seems the issue is the PRL. It's showing that it's been updated, but it's not updating. There's a conflict between what Sprint sees on their side and your phone. But.. I'm not a Sprint tech, so I don't know.
All I know is I have a NEW phone and the problem is FIXED. For now anyways..
shinedown87 said:
Are you new to Sprint? Text messaging on Sprint has done this on several different devices for the past two years (since I joined Sprint). And when I make a phone call several tend to come through.
Oddly enough this doesn't happen in Utah when I go to visit, only Puerto Rico (where I live).
Click to expand...
Click to collapse
Actually know, I've been with Sprint close to 20 years now. I've always had a lot of different problems with them, but I've never had this particular problem before. But I'm glad I got it figured out, and everything is working again.