I flashed DCD's recent ROM and now I cant make outgoing calls. Says I have an authenticity error.
OK I have read some posts that people contacted verizon twice and ran tons of tests. They wouldnt tell me my A-Key....
Some people posted that verizon gave it to them easily.
Does anyone have some insight????? I need to make calls.
What can I do?????
Call Verizon and tell them you did a hard reset and now you are getting that authentication error. They will make you do a *228 after they set it up on there end and it will update all your info. I know this cuz I have done it twice.
I called them twice and did the tests and *228 a couple of times with them and still NOTHING.
Verizon opened a Trouble Ticket for me and told me to call back tomorrow....
Any other ideas?
You just got a bad tech. Twice I was lucky. Just try again and tell them you did a hard reset and this happened. If you get a good tech they will know what to do. Tell them you can receive calls but can't send out calls, see what they tell you
All xv6800s don't have A KEYs - it depends on what part of the US they were
shipped to - that is what vzw told me. My phone didn't have one. I had the same problem you did and I called VZW (ask for a tech because the csrs don't
have a clue) and told them I did a hard reset and could not make outgoing calls.
They fixed me up over the phone and my phone works great.
narodk said:
You just got a bad tech. Twice I was lucky. Just try again and tell them you did a hard reset and this happened. If you get a good tech they will know what to do. Tell them you can receive calls but can't send out calls, see what they tell you
Click to expand...
Click to collapse
yeh, and make sure you are calling technical support for your device and not customer service. i flashed last week, the day i got my phone, so when i got the error, i guess it was more understandable, took me like 5 minutes of troubleshooting until he generated a new a-key.
one thing we should all be aware of. my tech said that it was weird because for some reason theres been a large amount of xv6800's calling needing an a-key replaced. so its possible that verizon may be aware of all this upgrading and losing the a-key.
you know what though. I checked my A-Key before upgrading and there was nothing there. It must be another setting causing this.
I performed an upgrade on my phone (scary) to get the GPS working:
(http://www.phonenews.com/how-to-add-gps-to-htc-mogul-xv6800-p4000-titan-2663/)
But... now, when my girlfriend sends me a text message with a smiley (we're both on Verizon), I get the following: Preceding msg modified, Media objects were removed. She gets a similiar message sent back to her that media objects were removed.
Anyone know how to prevent this message and allow media objects?
Thanks!
Has ANYONE else experienced this?
Has ANYONE else experienced this?
Click to expand...
Click to collapse
Yes, this is not a rom issue. It's a network issue with Verizon that I am looking into. It only happens when people with non smartphones (your girlfriend) send SMS messages to people with smartphones (you) that are either over 160 characters in length or have smileys (EMS). I am working with Verizon to get it fixed.
I get this message under the same situations but im with alltel...NON-smartphone to smartphone.... I have noticed that it states that message but the "smiley"s still get sent and the message is the same as what was sent but still get that message... I have just ignored.
I get this message under the same situations but im with alltel...NON-smartphone to smartphone.... I have noticed that it states that message but the "smiley"s still get sent and the message is the same as what was sent but still get that message... I have just ignored.
Click to expand...
Click to collapse
Must be the same network issue with alltel. It's not an issue with the rom though I can assure you.
I am in no way thinking its the rom.... figured that it had to do with non smart to smartphone...Was just adding that is happens with alltel also...But I dont see a difference in was was sent and what was recieved when I get the messages...I think it has to do with the longer messages cause it seems that is the only time I get those notices...Like I said I just ignore them..they dont cause any lack of function
gc14 said:
Yes, this is not a rom issue. It's a network issue with Verizon that I am looking into. It only happens when people with non smartphones (your girlfriend) send SMS messages to people with smartphones (you) that are either over 160 characters in length or have smileys (EMS). I am working with Verizon to get it fixed.
Click to expand...
Click to collapse
hey gc, any headway on this fix?
hey gc, any headway on this fix?
Click to expand...
Click to collapse
Well as far as Verizon goes, these phones are not EMS capable and therefore will NOT break the message up into 2 separate messages. However, for Verizon to Verizon SMS messages, Verizon's network automatically splits the message up on the network side regardless of EMS capability on the phone. The problem was that this was not happening on the network side either. My trouble ticket has been escalated like 3 times and I've finally been informed that it's a known issue with certain message centers. They installed updates to them with a bug that makes certain message centers not split them up like they're supposed to. I was told that some still work, and others don't. I was also told that the network engineers are working on fixing the broken message centers and once they're fixed they'll contact me and let me know.
As far as other carriers go, it's DEFINITELY not the rom or radio. I would put money on it that it's the same issue with the network, but can't be 100% sure because I haven't dealt directly with them.
gc14 said:
Well as far as Verizon goes, these phones are not EMS capable and therefore will NOT break the message up into 2 separate messages. However, for Verizon to Verizon SMS messages, Verizon's network automatically splits the message up on the network side regardless of EMS capability on the phone. The problem was that this was not happening on the network side either. My trouble ticket has been escalated like 3 times and I've finally been informed that it's a known issue with certain message centers. They installed updates to them with a bug that makes certain message centers not split them up like they're supposed to. I was told that some still work, and others don't. I was also told that the network engineers are working on fixing the broken message centers and once they're fixed they'll contact me and let me know.
As far as other carriers go, it's DEFINITELY not the rom or radio. I would put money on it that it's the same issue with the network, but can't be 100% sure because I haven't dealt directly with them.
Click to expand...
Click to collapse
for some reason, it only works on the sending end. i sent a 23 text message today with 1400 somethin characters that went through fine to another verizon phone, or any other phone (always worked on the xv6800). but the return text was 335 characters and only the first 160 came through with the preciding msg modified error.
for some reason, it only works on the sending end. i sent a 23 text message today with 1400 somethin characters that went through fine to another verizon phone, or any other phone (always worked on the xv6800). but the return text was 335 characters and only the first 160 came through with the preciding msg modified error.
Click to expand...
Click to collapse
Right, well that was the issue anyway. Sending out from the xv6800 always worked. Still does. It's when non smartphones send to the xv6800, the bug in the message centers will not split the message up like it should.
has anyone found a solution for this problem? I can confirm that it happens when a non-smart phone sends to a smartphone (env2 to xv6800). it must be the way that the non-smart phones encode their long texts.
anyone found a solution to this/heard back from their company? I am on Verizon.
This is an issue with Verizon Message Centers on their network. This cannot be fixed unless their engineers apply a network patch on their end. The discussion about it can end, cuz there's nothing that can be done.
gc14 said:
This is an issue with Verizon Message Centers on their network. This cannot be fixed unless their engineers apply a network patch on their end. The discussion about it can end, cuz there's nothing that can be done.
Click to expand...
Click to collapse
They could always just revert back to a regular cell phone so they can get smilies.
I agree that receiving any messages larger than 160 characters from non-smartphones would be a great fix. I'm tired of telling people.... "hey.. your message got cut off at....XXX... can you send me the rest?"... If they don't have unlimited text... this just escalates their text usage.
gc14 said:
This is an issue with Verizon Message Centers on their network. This cannot be fixed unless their engineers apply a network patch on their end. The discussion about it can end, cuz there's nothing that can be done.
Click to expand...
Click to collapse
Nothing can be done? Doesn't customer complaint usually warrant severity and priority of issues? I see this thread is a few months old but the problem is still there... seems like either their support and resolution process either sucks or not enough people have reported the problem to justify "engineering powah" to get the network fixed.
Nothing can be done? Doesn't customer complaint usually warrant severity and priority of issues? I see this thread is a few months old but the problem is still there... seems like either their support and resolution process either sucks or not enough people have reported the problem to justify "engineering powah" to get the network fixed.
Click to expand...
Click to collapse
Nothing can be done on our end, and nothing can be done by CSR's or Tech Support. The only remedy for this problem is, like I said, a network patch from the network engineers on their message centers.
gc14 said:
Nothing can be done on our end, and nothing can be done by CSR's or Tech Support. The only remedy for this problem is, like I said, a network patch from the network engineers on their message centers.
Click to expand...
Click to collapse
Ya I understand your points but "nothing can be done on our end" assumes having people opening their own subsequent tickets would accomplish nothing... I truly believe customer complaint has a lot to do with it especially in the formality of tickets.
I personally just called to find out more about this and the CSR was pretty quick to understand the situation and insisted opening a ticket was a good step towards resolution... He asked for specific examples of numbers and times msgs had this happen and created a ticket... I really doubt they'll just take the ticket and close it because it's a "known issue," unless it's being consolidated into a larger work order but even if that's the case I'm sure it will just emphasize the need for a fix... I don't know about verizon but typically SLA to customers is monitored and SOMETHING would come out of an additional ticket.
Still hoping for a fix here. This is retarded, the most exspensive phone they sell, and I can't get text messages that their free phones get fine?
The problem is a lack of EMS support for these phones correct? Well couldn't EMS support be added to the phone itself? I just don't get what is different about our phones as far as the NETWORK is concerned...
GC14: can you reccomend at least a place to ***** to, to get this fixed, as far as a number / e-mail / department within verizon?
This problem just started today!! i never installed GC's arcsoft cab 5.0.31.25 and always used 5.0.31.19.. and it worked fine.. after i installed 5.0.31.25.. the problem started.. hmm.. i dont think its GC's cab but what else do i think!?!?
madjokeer said:
This problem just started today!! i never installed GC's arcsoft cab 5.0.31.25 and always used 5.0.31.19.. and it worked fine.. after i installed 5.0.31.25.. the problem started.. hmm.. i dont think its GC's cab but what else do i think!?!?
Click to expand...
Click to collapse
if it used to work for you but doesn't anymore- maybe want to try this:
http://msdn.microsoft.com/en-us/library/aa919404.aspx
complete shot in the dark.
but searching and reading like a dozen other places with a pile of other wm phones on vz- the problem is wide spread- but some lucky son's of guns get it to work.
So might only be certain servers suck and if you get lucky the servers you use are ok and the right settings on wm might be all you need.
So I've been hearing a lot of good things about this ROM for us vibrant users.
Nonetheless, there is yet to confirm if the 911 issue is resolved? does anyone know and/or can confirm?
I am really surprised why people would even bother taking the risk of moving around with the 911 functionality.
I'm an old fart, 58 today, and lived most of my life before 911 existed. It no big deal to me. I have my local police and fire departments numbers on my phone and the same for where my elderly mother lives as I can't get her any help with 911 anyway. I don't see any more need than that. But that's me.
Thanks for the reply.
But I was wondering what about students, working professionals who tend to work away from their area (students studying in different cities) and for individuals who are travelling. You never know when an emergency strikes (kinda like the reason it was defined in the first place)
Sincerely,
alh.titan said:
Thanks for the reply.
But I was wondering what about students, working professionals who tend to work away from their area (students studying in different cities) and for individuals who are travelling. You never know when an emergency strikes (kinda like the reason it was defined in the first place)
Sincerely,
Click to expand...
Click to collapse
You should check the developers section for the threads about 911, this has been discussed already, it comes down to not having official samsung source code, everything that the devs have acomplish so far has been thru reverse engineering (very amazing btw) but with out time/money/equipment the devs cant do much.
I was running build 14, tried build 15 and had real trouble with it, recommend trying 14 first or waiting for 16. Haven't tried 911.
E911 has indeed been fixed in CM7.
http://review.cyanogenmod.com/#change,11492
As long as the CM9 build doesn't have a custom libaudio for Vibrant, it should work. But, caveat emptor, as always with ROMs.
bobshute said:
I'm an old fart, 58 today, and lived most of my life before 911 existed. It no big deal to me. I have my local police and fire departments numbers on my phone and the same for where my elderly mother lives as I can't get her any help with 911 anyway. I don't see any more need than that. But that's me.
Click to expand...
Click to collapse
So someone who lived most of their lives before seat belts were invented should be able to say that they aren't worried that their car doesn't have seat belts because they were alive for many years before seat belts came out? New safety technology is always going to be coming out. When the next thing comes out every person on the planet will have lived most of their lives before it existed but that doesn't mean that they shouldn't be using it.
Having the local police and fire department phone numbers in your phone are not a replacement to 911.
- 911 calls can be made on wireless networks that you are not a subscriber of. You're out of service on T-Mobile, but you can pick up a signal from some small company. They aren't going to allow you to call a standard number but you can call 911. If you have an old phone with no SIM card, you can't call the fire department but you can call 911.
- Your location is sent when you call 911. If you just call the police department, they will not know where you are. Because you are calling from a cell phone you could literally be anywhere. This may not seem important but there are many times when the caller is unsure of his location or is unable to communicate his location to the operator.
- 911 calls are automatically routed/transferred to the correct answering point. If you're out of town, you don't want to call your hometown fire department. Calling 911 assures you will always be connect to the correct people.
There are also other advantages but I don't really understand them well enough to explain them, but I do know that they provide many advantages over simply dialing the police department. There is a reason that the government has many laws regarding the 911 system and how it interacts with cell phones; there are many important advantages of the E911 system.
This is my first post, so I apologize if I forget anything. I did search for this question but couldn't find any threads related to this issue on this phone.
The short version: My phone sometimes doesn't respond to incoming calls. Outgoing calls work fine. I don't get missed call notifications and it takes hours to get voice mail notification. This is not a constant problem, if I reboot the problem goes away for a while. The length of time varies, but in less than a week, I'm back in this state.
The longer version: I got this phone at the end of November 2011. I started writing apps on it right away. I think it was in January that I first noticed that I was getting voice mails without missed calls. I went into the AT&T store and told them what I was seeing. They switched out the SIM card and told me to see if that fixed it. It didn't. I contacted AT&T tech support twice and they said they reset the notifications for my phone on their end. The problem persisted. A few days ago, I exchanged my phone for another unit. Now this unit is doing the same thing.
I have the smallest data plan, so I keep the packet data off most of the time.
I'm a software engineer working mainly in Windows Mobile, but seeing the popularity of Android, I wanted to get some experience in that, too. I've only been writing Android apps for a few months in my free time, so I don't have a lot of experience, but I can't imagine that the little apps I'm writing are causing this.
AT&T claims to have never heard of this before. How do I fix this? Please help me, XDA-Developers, you're my only hope.
Samsung Galaxy S2 from AT&T
Stock ROM
What other information can I provide?
Thanks!
Eric
You are not alone, m8.
It has happened to me all the time, I mean once in a while, never go away.
Since all call weren't really important, I just ignored.
Note: it happened on all of my phone from candy-bar style to flip-fone to smart phone.
Att is very likely screwing you. Don't trust those guys, they do lie...
A very odd thing is happening. I added a Phone to my Cricket account for my daughter. Just a cheap LG Fortune. Of course it came with a new sim/phone number. When she communicates with Android users via text everything is fine. When she sends texts to my sister and her friends that have iPhones, they receive the message just fine, but when they reply to my daughter's messages, another unknown user replies to the text. My daughters phone never gets the reply. Unfortunately the person responding is not very friendly and is cussing telling my sister to stop harassing him. I'm assuming maybe this has something to do with iMessage which the previous phone number owner may have had. But I'm not sure.
Any idea what's going on here and how I can fix it? I may need to go back to Cricket and have them change her phone number.