Database Users

Very strange problem with my newly replaced g1

Ok, so I got water damage... alot of water damage.. to my g1 yesterday morning, paid the $130 deductible to have it replaced under warranty... and i just got the replacement in today
i went to tmobile since i lost my old sim card that i took out of my old g1 yesterday, and had them activate a new one for me, put it in, and was running rc33, everything was working fine until people started texting me, so here is my best attempt to explain my issue
If a tmobile customer txt messages me, everything is fine
If i text my self, everything is fine
Any other carrier i have timestamp issues, exactly 4 hours off (ex: its 8pm and it says 4pm on the timestamp)
However, it gets weirder than that, if I look at the list of people who have messaged me, timestamps for most recent message plus the brief display of the last message is correct for any carrier, if i open the message though, its incorrect. what this causes is something like this:
Bob: (message) 4:01
Bob: (message) 4:09
Bob: (message) 4:18
Bob: (message) 4:32
Me: (message) 8:02
Me: (message) 8:11
Me: (message) 8:20
Me: (message) 8:33
Now while these times are made up, its the best way to describe it, if bobs message shows 4:01, it actually came in at 8:01, and it only shows incorrectly when i open bobs individual thread, if viewing the list of threads, it will actually show as 8:01
This happens with both the stock messaging app, and chomp sms pre cupcake, i have no other apps installed, and ive changed no other settings
tmobile and i went over apn settings, refreshed me on the network, battery pulls, wipes, all sorts of crap for a hour and a half when tmobile finally said there is nothing they can do, to call there insurance company that sent me the replacement and have them send me a new phone
i was lucky enough to have a woman who was not only nice, but had a g1 and understood how to use it when talking to tmobile, however when talking to the insurance company, it was a guy who had no idea what he was talking about when it came to g1's
he first asked me to remove the battery, hold the power button to "drain the last of the power from the g1 so it forgets everything it last did" for 15 seconds, then power on, of course didnt work, then he tells me he had received an email/memo about timestamp issues with cupcake... so i tell him that im running rc33 and not cupcake, so he tells me that i need to update to cupcake and see if that fixes the issue, even though he had just gotten an email about timestamp issues with cupcake, so they wont send me a new g1 untill i get a OTA update from tmobile for cupcake
i decided not to wait, and i started to go through the root process, i just downgraded to rc29, just logged into the gmail and decided before going on, id test it again, had a verizon customer send me a txt, same issue, both with rc33 and rc29...
now ive got another g1, currently running ion, no problems with that one, its of course in the exact same area, and right next to me, again, no problems at all
tmobile has no known issues in my area for the network
tmobile has nothing reported about this with rc33, nor any other firmware according to the woman i spoke to
im going to go ahead and root and goto ION, but i figured id wait before doing that and post this issue here incase its a simple fix that i can do before flashing to ion, any ideas guys?

I had the same problem too, but it went away on its own
I believe it was a T-Mo network problem as someone in another thread said, but I can't say for sure.

ei8htohms said:
I believe it was a T-Mo network problem as someone in another thread said, but I can't say for sure.
Click to expand...
Click to collapse
do you remember which thread? i did a search, didnt see it before i posted up, but maybe i missed it or searched wrong

My phone was doing the same thing on tues-wed-thursday , i thought it was roms so i was flashing like 3 diff roms per day lol it finally seems to have went away today though , give it time t-mobile will straighten it out just delete messages quick as they come for now lol

soba5150 said:
My phone was doing the same thing on tues-wed-thursday , i thought it was roms so i was flashing like 3 diff roms per day lol it finally seems to have went away today though , give it time t-mobile will straighten it out just delete messages quick as they come for now lol
Click to expand...
Click to collapse
ok sounds good
sorry for waisting a thread then, thanks guys

Error Code 67 - No 3G Data - Out of the blue!

Just happened out of the blue. Had wifi on, but wasn't at home, so went to turn it of, did some facebook checking and then checked for a prl update...now no 3g data and EC67.
Looks like it forgot our sprint user name and password.
Tried doing a ##3282#, which did nothing and ##775# doesn't work.
Running Fresh 3.2 and the new htc kernel.
Sent from my PC36100 using XDA App

Have you tried updating profile? That'll usually fixit
Sent from my PC36100 using XDA App

kixcastillo77 said:
Have you tried updating profile? That'll usually do it
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Tried that but of course sense 3G doesn't work, it gave me the same error faster than I could press dismiss.
I'll try again via wifi and 4g.
EDIT: Looks like that fixed it - Thanks! Haha. I can't believe that I didn't think to try it over wifi/4g, but I remember trying to update my PRL over wifi/4g and it wouldn't work, awhile back.
EDIT 2: It didn't work. Haha. The Firmware updated without giving me the error, but now the profile update is giving me a 1020 error.
EDIT 3: I think I fixed it. I remembered that I had that startup cleaner app running and that it might be killing off the handsfree updater. Looks like I'm golden now.

I had the same issue yesterday, I updated profile a few times, didn't work. Updated PRL twice, it worked. I think it was a coincidence that it worked, probably an issue at Sprint's end.

I was having this issue last night and couldnt figure out why.. my wifi tether kept stalling out and my 3g kept going in and out.

Same here, they must have done something yesterday

Welcome to hell, dude. My wife and I have been experiencing these errors for weeks now. I have tried everything in the book and nothing seems to be a permanent fix. Updating PRL and Profile is temporary at best. PRI Update to 1.40, then to 1.77 did nothing either. This bites.

Wow. When it first happened I was taking my Grandma to the store and half expected to find everybody on XDA freaking out and it had been some national/regional bug that screwed everybody's evo up - Must not have been big, but something to hit a few of us.
It's working just fine this morning after I did a ##3282# and turned up startup cleaner.

I had this same issue the last couple days. Fine today so far. Nyc area btw.
Sent from the void...

I just called them and they told me that they are having network issues in my area and there is an "open ticket." I'm sitting here thinking something is wrong with my phone until 3 other people on sprint told me they couldnt make calls.

same here nyc also did 1.7 pri update i figure thats was the problem now i am stuck with 1.34 (hours and hours took me to go back ) now i dont know what to do should i go back to 1.7 since is every one?

sf103100 said:
same here nyc also did 1.7 pri update i figure thats was the problem now i am stuck with 1.34 (hours and hours took me to go back ) now i dont know what to do should i go back to 1.7 since is every one?
Click to expand...
Click to collapse
Not the PRI. I've been with 1.34 forever, never changed it and I had this issue.

wuclan48 said:
Not the PRI. I've been with 1.34 forever, never changed it and I had this issue.
Click to expand...
Click to collapse
i had 1.40 did update to 1.7 had major problems so i had to go back to 1.34 now i cant get 1.40 back (i dont have problems with 1.34 )
Just be clear

sf103100 said:
i had 1.40 did update to 1.7 had major problems so i had to go back to 1.34 now i cant get 1.40 back (i dont have problems with 1.34 )
Just be clear
Click to expand...
Click to collapse
I updated to the 1.7 PRI last night after I got the error codes figured out. Haven't had a problem, yet, but it's been off this morning anyhow.
Never had a problem with 1.34 PRI, but last night, after installing 1.7, I did a few speedtests in bed and I constantly got 150/190 up and 550/600 down, and before I was getting either better than those, by 50% or worse than those by 50%.

This is a frequent occurrence (at least in New York City). It's annoying but don't worry about it. Anything you try to correct it will only be a temporary fix until it eventually goes away at random.

I've had Error Code 67 come up once in a while since I got my phone. Sometimes it comes in bursts, maybe 4 or 5 in a row. Super annoying. I called Sprint today and they had me update the profile a couple of times which did nothing as I kept getting the error while on the phone with them. They are sending me out a replacement Evo in the mail which I should get tomorrow. I'll report if it fixes the problem. Tech Support mentioned they do have them in stock if anyone else feels like they might be in the same boat.

FunkyAroma said:
This is a frequent occurrence (at least in New York City). It's annoying but don't worry about it. Anything you try to correct it will only be a temporary fix until it eventually goes away at random.
Click to expand...
Click to collapse
I'm in NYC as well and I can't stand this error. If there was a way to supress I would be a lot more happy since if the error pops up while you are typing a number into the dialer it will clear out all the numbers after you press dismiss.

The error code is a result of Sprint working on upgrading the network to increase 3G capacity. I was getting the error messages when my PRI was 1.37, and I have gotten them a few times after updating to 1.77. At first I used to try updating my profile, but I would get the error message again. What worked for me was turning off my 4G (I'm in NYC, and there is a few test towers up), then turning on airplane mode for a minute or so, then turning it off again. For me, the 3G would kick in, and I won't have the error.

I am getting the error on 3G with 4g off or 4g since I got the phone. Sprint rep said it's not normal so Lets see what my replacement does.

looks like it hard us in NYC hard.
anyone else have horrendous battery life today after fixing this? I barely used it, I only got about 8 hours. I fully charged it when i got home, and literally watched it go down from 100% to 80% in 15 minutes..

Help with voicemail update pls

Ive updated my voicemail to the new update around 3 wks ago or so. Last night I started getting voicemails that were a couple days old that I didn't even know about. So I sent myself some voicemails and didn't get them. I then uninstalled the new voicemail update and when it uninstaleed I got some more old voicemails pop up. After that I got the popup that said a mandatory update is available. I it ok to reinstall the update and then it says no updates available. I have the notification telling me bout the update but every time I try to update it says no update available. I've tried everything. I just completed a hard reset that sprint tech. Told me to do and nothing. The sprint tech said he never heard if it and wants me to take it to a repair center to see if they can push it. I don't mind doing that but I live 45 mins from a repair center and if for some reason I have to do another wipe I'll be in the same position. Anybody know what to do or heard of this? Everything else updates just fine. Thank you

Having the same problem...I wouldn't bet it is a hardware problem.

mcaragio said:
Having the same problem...I wouldn't bet it is a hardware problem.
Click to expand...
Click to collapse
Theres a thread abbot this ready and done said voicemail is down to feb29th our something to that effect
Sent from my SPH-D700 using XDA App

Download a rom with newer cm-android.apk. adb into phone and remove current version. Adb new voice mail to /system/app. Well try it. It was perfect for me. Good luck.
Sent from my SPH-D700 using XDA App

[Q] Error sending/receiving MMS "National access coverage not available."

Hello,
Lately I have been unable to send or receive text messages that contain pictures or videos. The error message is always the same "National access coverage not available."
I called Verizon, on Thursday of last week (1-13), and the technician was unable to figure out the problem. He escalated it to the next level and said that someone would be contacting me in a day or 2. Well it's now Wednesday (1-19) of the following week and so far, nothing!
Has anyone else run into this problem? If so, what's the fix? Any help would be appreciated, especially since Verizon has been no help at all!
I'm using a Moto Droid2 ver, 2.3.2 Rooted and OC'd @ 2.25Ghz
Thanks,
Scott

Dial *228 and update your PRL.

silverfang77 said:
Dial *228 and update your PRL.
Click to expand...
Click to collapse
Thanks for the reply.
Unfortunately, it didn't work. I updated it waited the 15 minutes. When it didn't work I rebooted the phone figuring maybe it needed to be refreshed or something, (long time windows tech, reboot fixes everything!) but still nothing. Just that same message.

I get the exact same error when sending or receiving MMS 50 percent of the time with the first initial try... *228 does not fix this.. verizon cannot fix it either...

OK, got tired of waiting for Verizon to call back. On the phone with 2nd tier support now for about the last hour, so far nothing.

Mine started doing that on mms after using juice defender app and I had to do a factory reset to fix it.

OK, got finished with the Verizon tech, who was very helpful, but we still could not resolve the issue.
She removed and reloaded my data from the server, switched me to another IP address and did a few other behind the scenes things but nothing worked. She suggested doing the factory reset, but I'm ready to give up troubleshooting this issue yet. If all else fails, then I guess I will have no other option.
Since sending MM text's in not a huge part of what I use my phone for, I may just wait for the next release of the software and hope that fixes it.
In the mean time I'll just keep playing with settings and searching Google and the message boards in the hope that someone can come up with a fix that doesn't involve having to wipe it.

rtfield said:
Mine started doing that on mms after using juice defender app and I had to do a factory reset to fix it.
Click to expand...
Click to collapse
I used to use that app, but removed it long before this started happening. I wonder if it left behind some orphan files that are somehow in there wreaking havoc?
Since the problem still existed even running the phone in safe mode, I would think that would not be the case, but anythings possible.

my phone does the same thing with same message... if i try again to download message it will usually come through, but if it happens on outgoing message it will never go through

1250x said:
my phone does the same thing with same message... if i try again to download message it will usually come through, but if it happens on outgoing message it will never go through
Click to expand...
Click to collapse
That's the thing. Since so many people are having the same or similar issue, I just find it hard to believe it's not something on Verizon's side or with their software. This many people screwing up their phone's in the exact same way all around the same time just seem a little suspect to me.

Mine happened 6 months ago. Just reset it and see what happens. All your apps with reinstall by themselves.

rtfield said:
Mine happened 6 months ago. Just reset it and see what happens. All your apps with reinstall by themselves.
Click to expand...
Click to collapse
Yeah, I guess I'm going to have to try something. I want to make a nandroid backup first just to be safe and then I'll give it a shot.
Thanks.

This is great!
So, I just finished the factory reset (which DID fix the problem) and was starting to configure all my custom settings when the Verizon tech I spoke with called me back. She said that she had just spoken to Motorola and they said it was a known problem with their phones! They are not sure what it is yet, but they are working on it. In the mean time, the only thing they can suggest is to reset the phone as a work around!
I asked the Verizon tech if there was any kind of documentation about this that she could send me, but of course there isn't. And there's also nothing on the Motorola site about the error either, at least nothing I could find.
While it doesn't make the situation go away, it does make me feel better knowing what the root of the problem is, sort of. Only problem is, there is no guarantee that it won't happen again.

i turn airplane mode on then off... works for me

Im having the same problem. I even reflashed to stock motorola, still does it. I noticed if i hold down on failed pics or tap download a few times it works. The problem seems to be triggering the data on and off from the send button.
Sent from my LogicPD Zoom2 using XDA App

S.Meezy said:
i turn airplane mode on then off... works for me
Click to expand...
Click to collapse
Yes, I had heard that worked for some people, and I did try that but it still didn't work. Even so, that would only be a work around and not really fixing the issue.
V.A.T.Juice said:
Im having the same problem. I even reflashed to stock motorola, still does it. I noticed if i hold down on failed pics or tap download a few times it works. The problem seems to be triggering the data on and off from the send button.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
Interesting, since I did the factory rest I haven't had a problem. If it happens again, I'll be sure to check that.

[Q] Roaming Indicator Off

Hey all,
I recently bought an (AT&T) LG G2 off eBay, as my iPhone 5S just wasn't cutting it for me.
The day before it came I went into AT&T and asked for a new nano-SIM, it was given to me with no questions asked. The next day, I got it, put the SIM card in, and called to activate it. Everything went fine with customer service, and it activated with no problem, or so I thought.
Everything was looking good, and before I got off the phone with AT&T, I rebooted just to be positive. Once it was back on, I realized in the status bar in the top left it said "Roaming Indicator Off". I told the rep, and he said that was very weird, so we began troubleshooting. Around a half an hour into this, I received a text, I went to go respond to it and when I pressed send it said "No USIM Card". I told him about this as well, so we began troubleshooting both issues.
After about an hour he bumped me up to Android technical support, where I painfully continued with troubleshooting. During all of this I accidentally tried to make a call, and voila, it all went away. The status bar now said "AT&T" and I was able to send texts just fine. I told him about it and just said "That's weird, but awesome!". I rebooted the phone one more time just to make sure, and what do you know, it did it again. The same message came up in my status bar, as well as the inability to send texts.
There was a lot of things tried to fix it, including a master reset, the manual configuration of APN's, and a different text message center address. Trust me when I say, we've done just about everything possible. In fact, the next day he called me back with an LG rep on the line, they too couldn't figure it out.
At first they thought it was a hardware problem, but since making one phone call after a reboot fixes everything, they're leaning toward software. However, there was nothing else they could do.
I guess it isn't really that big of a deal, considering I can just make a call everytime I restart my phone. But I'd really like to get rid of the problem completely.
Thanks for any help you may be able to offer!
-Andrew

had this problem with my att g2 also whenever i rebooted my phone, the way i got rid of it was just to make a phone call or call voicemail and it went away

theteam said:
had this problem with my att g2 also whenever i rebooted my phone, the way i got rid of it was just to make a phone call or call voicemail and it went away
Click to expand...
Click to collapse
You never fixed it? Are you still using your G2, and does it still occur?

andrewlima said:
You never fixed it? Are you still using your G2, and does it still occur?
Click to expand...
Click to collapse
Not a permanent fix, It only occur when I reboot my phone which I rarely do. I am still using it.

Eifes phone just started having the same issue. Mine however does not but, Its not the OEM OS either... Maybe i'll have to root hers too....

awesome thanks.
theteam said:
had this problem with my lgg2t g2 also whenever i rebooted my phone, the way i got rid of it was just to make a phone call or call voicemail and it went away. Immediately. Tyvm
Click to expand...
Click to collapse
what a relief its easily fixable.