Hey there,
I own the OPO now some days and my GF tried to phone me just some minutes ago and was not able to catch me as the system told her that I am currently not available.
Usually I should be reachable as the phone is online and has three bars signal strength and if I really wasn't reachable I should get a text message telling me that number 123456789 tried to reach me.
So she called on the land line and told me this. I immediately called myself from landline and the call arrived.. strange thing is that at this moment the text message arrived, about 5 minutes later.. Running 33R. Did a reboot now but still gives me a very strange feeling.. I think the phone was in DeepSleep but it didnt wake up..
Any one had this issue before? Any chance I can run some kind of diagnostic?
--edit--
Rebooted right now, called me again with signal there. Call did not arrive on phone but text message did... wtf?
And again rebooted and not reachable... ??
Another reboot and I am reachable... holy moly..
Related
The strangest thing. I just ported my number from att to sprint two weeks ago, and I haven't received any texts, calls or voicemails in the last few days and have been so busy with work I didn't think anything of it. However today I randomly received 15 texts and 5 voicemails. A lot of them were angrily asking me why I was ignoring their calls and texts. I was on the phone with sprint technical support and they reset my settings with the network and I started to receive all kinds of random texts from the last two days in random order. The technician said he never saw anything like that before. It's just so strange. My emails never stopped coming in, only the things that are sent directly from my phone from the sprint network. elguapo76 pointed out that I should have my phone on hybrid instead of just evdo, which I did. And diesel556 said
"I believe that text messages queue on the server if the device is unreachable. The same thing would happen if you went out of range on the Verizon network.
Unless you have a legitimate bug with the service."
Any ideas about what I should do to fix this? Or can anyone get more into depth with what this is? If there is a way to permanently fix this I would love to know. Thanks in advance!
Did you recently apply the update patch? It could have fixed an issue with the system throwing up a flag when your ROM gets low on storage. This was usually perpetuated by a ROM leak that many of us have experienced. Basically what happens is that if you have used bluetooth and it gets stuck connecting (hard to tell at times) it will create a 6mb-15mb core dump. Over time this will fill up your ROM storage memory. After your ROM gets filled to a certain point (whether by the bluetooth ROM leak or user function) it will throw up the flag to the server telling it to halt all sms and voicemails. Before the patch you could hard reset and recover your ROM storage memory but the flag would not come down. I know for myself it took me a couple of days to figure out I was not receiving sms/voicemails after I got some upset people emailing me why I had not got back to them. With the recent MR these bugs have been resolved and the flag could have been taken down thus freeing all your sms and voicemails from the pits of sms and voicemail hell. That's just a possible theory.
Would you say there were a plethora of bugs?
Interesting. Two days ago, I used my moto bluetooth headset for the first time. Curiouser and curiouser. However, I did use the update the day that it came out. I restored with nandroid and upgraded that same night, so I shouldn't have had that problem. Actually, when I tried to connect before the update, I couldn't even connect that headset to my phone.
jonnythan said:
Would you say there were a plethora of bugs?
Click to expand...
Click to collapse
A plethora! Jefe what is a plethora?
Yes I would say the Hero had a plethora of bugs!!! Thankfully HTC/Sprint gave us a sweater of an update!It's a sweater!!!
Now just fix the Android Market problem!
So I've got a few problems that seemed to have cropped up with my HTC Dream (hence the vague title!)
I'm running Android 1.5, Rogers Post-E911 firmware - I'd imagine that in itself is a problem, but whatever!
The main problem I'm having currently is that my phone keeps losing connection to the network. It says I have perfect connection/full bars, but any outbound calls just bounce me back to the home screen, any outgoing texts get the "Could not be sent" error, and anyone trying to contact me gets a message saying my phone is unavailable. I've factory reset my phone several times but this keeps happening.
The second problem I'm having is that a lot of the time when I start my phone, I get an error saying "Android.Process.Acore is not responding". Forcing it to close leaves me with a blank screen (background image with no icons). Telling it to wait just sends me to my regular home screen, and nothing appears to be wrong after that.
Both of these issues have been ongoing since about a month after purchasing the phone (Pre-E911) but have increased in frequency since the update.
Now I realize that the Dream is nowhere near the cream of the crop these days, but it's my only phone currently, so hopefully the geniuses on XDA Forums can solve my problem =D
Nobody? ~bump~
I wonder if anyone has seen this. Once every few days, I would look at my phone and find that the phone appeared to be starting up. I would see the no cell service icon, it would eventually connect after a minute or so. Then media scanner will start. Even notifications that I previously cleared will popup again. However, it was not a full restart since I never heard the phone startup sound.
Yes, I have had the exact same problem, it happened today. Today was the second time it has happened in just over a months time. I was at the gym and I got a phone call, didn't wanna answer so I rejected it and the person left a voicemail. Minutes after that, I experienced what you described.
Even after deleting the voice message, the voicemail icon still showed up in the notification bar and the phone kept reloading itself.
The phone would not even get to a point where I could use it, it stayed in a loop of reloading.
My issue may have been different, but I pinpointed it to the SIM card.
Here's the steps I took to resolve that issue, which resolved the "rebooting":
Put my SIM card into my old GoPhone (any ATT or unlocked phone should do)
Called my number from my landline and left a voice message
Called my voicemail from the GoPhone
Deleted my new voicemail
Put the SIM card back into the Captivate and it worked just fine
That same situation happened to me this morning. I was in the car and had pandora playing. Then it just stopped in the middle of a song and did what you described - I also didn't hear the start up sound, just saw the media scanner running and the no signal icon. After everything finished, I was able to start pandora back up. Phone has been running fine since. Strange.
Sent from my SAMSUNG-SGH-I897 using XDA App
When this happens, I also lost the bluetooth connection to my car. It appeared the bluetooth device was still paired but I couldn't connect to it. I had to unpair and pair it again. I also had to go through the initial screen of Vlingo again when I started it up.
I just had this happen an hour or so ago and have seen it multiple times before... for what it's worth.
Sent from my SAMSUNG-SGH-I897 using XDA App
I cannot make calls or send texts.
Ok so I have GummyCharged 1.9 Flashed for a bit now.
Everything has been fine up until now, this morning I get a text and go to respond, but it says message not sent every time. When I go to message details it says
"Error code: 2"
I then had one person call me and all there was, was constant static and no voice, then made a second call 30 seconds later and it was fine. I can get texts/calls perfectly fine.
Sometimes I can turn off data and then turn it back on I can send about 1 or 2 texts really quickly before the rest stop going through. Ive already shutdown pulled battery and everything...
Should I factory reset? Will that mess up my rom?
Or are there any other solutions?
PS Im using 3G(no 4G in my area).
Mr Grim xX said:
I cannot make calls or send texts.
Ok so I have GummyCharged 1.9 Flashed for a bit now.
Everything has been fine up until now, this morning I get a text and go to respond, but it says message not sent every time. When I go to message details it says
"Error code: 2"
I then had one person call me and all there was, was constant static and no voice, then made a second call 30 seconds later and it was fine. I can get texts/calls perfectly fine.
Sometimes I can turn off data and then turn it back on I can send about 1 or 2 texts really quickly before the rest stop going through. Ive already shutdown pulled battery and everything...
Should I factory reset? Will that mess up my rom?
Or are there any other solutions?
PS Im using 3G(no 4G in my area).
Click to expand...
Click to collapse
You can factory reset and see if that fixes the issue, it will wipe all your data, so back up anything that is important to you.
If that doesn't help I would flash back to stock and see if that fixes it. If not, a trip to Verizon is probably in the cards
when in doubt, do a full wipe & reinstall...
So, this is bit of a new issue, one I've not had before. I wish Hangouts/Messenger still had the Service Center ID in the settings in order to fix this, but, in the long/short run...
I unboxed my pixel and put my SIM in, started the phone. LTE/UMTS work perfect, locked right on, good signal/speeds, can place/receive calls, all is right in the world? I noticed after an hour I hadn't received any texts, and after feeling very unimportant, I sent a SMS to a friend, and got an immediate error. Out of curiosity, I went into the INFO settings (*#*#3646#*#*) and went into the SMSC settings. pressed refresh, which, populated an error. I manually typed mine, hit update, went back to hangouts, and voila!
The next day, I restarted the phone ( I like to do this often. I am also this user who actually turns their phone off from time to time ) and noticed upon restart, the problem resurfaced, like as if I never updated it to begin with.
Is this occurring with anyone else? I've yet to see a phone completely dump it. I'd prefer not to download another SMS application really, but, it's just inconvenient those few times I do restart it that I lose that SMSC number...
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
I'm having this same issue. I've contacted support about it, but haven't gotten a response yet (they said I would have an update yesterday).
If I manually put the SMSC in, and then Update, I can send texts briefly, but eventually I start getting an error 38 instead. A reboot and then manually entering the SMSC again allows me to send texts again.
vagosto said:
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
Click to expand...
Click to collapse
I'm curious if setting your mobile data to always-on would be a functional workaround to help until they can get this fixed for real. Have you tried that?