Related
***Update 10/29/08***
Just found this update, supposedly from someone high up at Microsoft. Seems plausible to me.
***Update 12/1/08***
I "guess" that fix made the problem a little better for me, but it didn't stop the error. The good news is MS has released a fix for the problem.
We'll see...
I'm going the reverse the instructions from the preceeding "fix" (registry edit), delete my current gmail account, soft reset, apply the MS patch, then recreate my account.
***End of update 12/1/08***
If you've used gmail for outgoing email long enough I'll bet you've seen this error while trying to send at some point, which then prevents you from sending any more emails via gmail:
"The message could not be sent. Check that you have network coverage and that your account information is correct. Then try sending again."
I've seen it using many dcd/no2chem roms using gps and non gps radios.
There are loads of "fixes" on various forums that suggest specifying server port numbers, requiring/not requiring SSL, etc. .It's been my experience that only one fix fixes the issue consistently.
From the Kaiser forum:
jgmdean said:
I usually have to delete the account and then add it again with a different name.
Click to expand...
Click to collapse
Creating this new account with a different name is the only fix I've found that works consistently, at least for a couple weeks.
Status...
I said in the other thread (http://forum.xda-developers.com/showpost.php?p=2398125&postcount=82) I would wait to test... Well guess I am not good at waiting.
After recreated with a UNIQUE name it is sending fine. I will see how long it lasts.
Another thread here with some of the setup info.
http://forum.xda-developers.com/showthread.php?t=385575&highlight=gmail+imap+sending
Yup, I've needed to create unique names from Gmail to Gmail6 before to get messages sent.
Never seems to work for more than a couple weeks.
7-12 thru 7-18... Looks like I am on Gmail02
This is a real pain!
That it is!
All I've been able to do is file an error report with Google.
Sure would be nice if someone knew Pocket Outlook well enough to investigate...
I'm having the same trouble and don't use Google for email.
I monitor 4 accounts with my Tilt and the one that causes me problems is the Exchange account, using IMAP and SMTP. The other 3 IMAP accounts use Courier/Qmail and they have never posed a problem.
I even tried sending my Exchange account email using my Qmail SMTP server and it too triggers the error.
It has gotten to be such a pain in the ass that I'm evaluating FlexMail which works so far, but is a bit slow.
My money is on a problem with Pocket Outlook.
../mk
For what it's worth, I use a free app called Seven (http://community.seven.com/) to have my Gmail messages pushed to pOutlook my phone, and I've never encountered this problem that you guys are describing.. and i've been using it for about 8 months now.
Thanks for the tip on Seven. Nice how it runs behind the scenes, preserving Pocket Outlook's interface. Too bad how it'll only retrieve messages < 30 days old, but it'll be a good fix for me if it stops these errors...
Huh, I hadn't noticed that limitation, but now that you mention it, it would be kinda nice to be able to go back in my email history a little further (heck, we've got enough internal storage space for it). Anyway, good luck with it.
There's always native gmail...
I prefer to use native gmail running in GC's Java midlet. With native gmail, you get...
a familiar gmail interface
20MB attachments received right on your 6800
full access to read and modify your contacts
access to your complete gmail history, with search
your gmail labels
THREADED messages!
What's missing? A way for your 68000 to inform you, "You've got mail".
Updated first post.
Does this affect DCD roms or just the stock Verizon one? or both?
omg
I have been tearing my hair out since I have had my phone over this. could not figure it out, only solution was to delete the account and re-add
I will follow and try this
Thanks
Hi - I have a similar issue with gmail. Incoming works perfectly via imap, however outgoing emails do not work at all. I tried the smtp fix patch from MS, changing outgoing smtp.gmail.com to smtp.gmail.com:465 or 587 and it still doesn't work. Also tried to create the account again to no avail.
I used the standard settings on gmail site https://mail.google.com/support/bin/...y?answer=78886 - dunno what I am missing here!! Any help would be nice
I am trying this on a brand new htc diamond.
I am using FlexMail 4 and have never had a problem sending or receiving with gMail IMAP. I can not, either, send emails using ms pocket outlook. I can receive emails just fine. This is a bug in MS Pocket Outlook as described by earlier post.
I "guess" that fix made the problem a little better for me, but it didn't stop the error. The good news is MS has released a fix for the problem.
We'll see...
I'm going the reverse the instructions from the preceeding "fix" (registry edit), delete my current gmail account, soft reset, apply the MS patch, then recreate my account.
I don't know if you guys are using 6.1 or not, I just found this thread while googling the error message and found a solution that worked for me.
Here is the official Microsoft patch for this problem and it seems to have worked (at least so far) for me. I just downloaded the cab, my phone restarted, and sending emails works again.
http://www.microsoft.com/downloads/...d2dd-44f2-86e5-1e53aad7fb7a&displaylang=en&tm
Hope that helps.
I was and still am running 6.1 (dcd 3.2.6). After applying that patch I don't get the error as often, but I still get it with gmail and my work IMAP. I haven't had to recreate any accounts since the patch, only a soft reset's required to start sending again. So, for me the patch has been an improvement but not a fix.
To me, a fix here will be the best part about 6.5, assuming they fixed it (I have no idea)...
Thanks all.
Just to say the MS patch seems to have fixed things - this evening at least.
Interestingly, I've got three different gmail-based accounts on my phone. Two of them stopped sending, but the third remained unaffected.
Thanks again!
MMS Debacle/Debate/Laughter/Annoyance
Apps related but Development related for Future Builds, Move if Needed
"Error in Server Response" ***THIS APPLIES TO THE TOUCHWIZ MMS.APK VERSION***
It has been posted numerous times and people still numerous times have had problems & been easily dis-missed with the 10 or so work arounds suggested that still inevitably don't work for some select few out there. I have posted attempted possible solutions in the Apps section before & troubleshooted my own MMS problems for the past 2 months till blue in the face. I wanted to share everything I have tried and everything I have noticed in an effort that maybe a Developer out there can correct the issue for us.
Brief summary to Developers for what I think is the problem or solution: I believe in order for outgoing MMS picture messages to work you have to either A: Have the MMS.apk properly re-format the phone number that it pulls from the contacts list by removing the dashes and maybe adding the 1 in front. MMS has always worked without the 1 or the +1 in front for me.
B: Have the Contacts.apk or Contacts list designed so that it only saves phone numbers without dashes in them. I think from some of the recent Contact.apk's I messed with that current builds are not automatically putting dashes in anymore when phone numbers are saved so that may be helping alot of people.
Now onto what I have noticed past several months:
Many have dissed the poor people with failing MMS picture messaging by simply suggesting removing dashes, adding 1, adding +1, trying Handcent, Chomp SMS, Go SMS. etc etc. Also those same people said MMS works fine or works fine for them. However I question how many of those people are using Contacts saved to their actual phone as myself as it appears if your using your Google account or your SIM card to save your contacts to than this issue does not seem to exist. Also, removing dashes is not an option for Phone saved contacts or not in my current ROM build. Some newer ROM Contacts builds looks like it will let you save numbers without dashes now. Mine does not with Phone contacts. People wiht Google contacts probably did not have to worry about that as they could edit within Google. It specifically exists for people and myself with Contacts saved to their phone who may or may not be using their SIM or Google account to save their contacts to. I tried various APN and separate MMS apn settings with no difference.
I have pulled and tried just about every MMS.apk from AOSP and various froyo builds. Always Handcent, Chomp, Go SMS formatted and worked perfectly for MMS picture messaging. AOSP always worked for me but I had other issues with attaching Audio that caused force closes. propably due to my aging Obsidian V4.2 ROM. My issue was on previous build ROMs as well and been on my ROM since freshly loaded up to now where you cant recognize it is Obsidian anymore with all my mods. SMS always worked period. MMS always received perfectly for me. MMS always sent perfectly as long as I manually typed in the number without a 1 or +1 needed. MMS always worked when replying to an already received SMS/MMS. Only specifically when selecting Contacts to create a SMS/MMS does the "Error In Server Response" exist leading one to believe that its a formatting problem somewhere between MMS.apk and Contacts.apk when the softwares transfer over the phone number/contact information to create the message header.
This has been the only issue I would love fixed short of using alternative Handcent, Chomp, Go etc. It is also the reason why I have held off flashing newer builds as it is some work to re-setup my entire customized phone and still have the problem remain as I have been reading in recent Team Whiskey Nero v5 builds still.
Maybe I'm retarded or maybe I'm onto something but I felt I should put my efforts out there for developers to examine and also to take a Users poll of MMS issues regarding which people are using various ways to save their Contacts....SIM, Phone, Google account to pin point the cause.
Thank You for reading, sharing, and looking into this. If I had programming skills I would rewrite the damn MMS.apk myself since every other 3rd party seems to work and format the numbers properly to send MMS without issue.
MMS Issues
God knows I've tried just about all the ROMs in the forum and unless it's either the stock rom or one of the leaked ones, Touchwiz MMS has never worked. If I used the custom ROMs MMS suite it's fine. As soon as I mod it for Touchwiz MMS it pukes.
ive tested almost every rom and i always have my contacts save through sim and my mms is flawless every time.
I've had this issue a few times. I do NOT save my contacts to phone or sim, they are ONLY in my Google account. I finally went and edited all my contacts on the Google Contacts website to remove the dashes and 1s, and now it works fine every time.
raduque said:
I've had this issue a few times. I do NOT save my contacts to phone or sim, they are ONLY in my Google account. I finally went and edited all my contacts on the Google Contacts website to remove the dashes and 1s, and now it works fine every time.
Click to expand...
Click to collapse
Same story here. Removed the dashes and now MMS messages send perfectly.
As a way of troubleshooting why it seems to works for some people and not at all for others (even when considering the no-dash, no-paren formatting), it might make sense for people to post their configuration:
Think I'm interested in learning if people who are having this problem are
* syncing to Google,
* not syncing with Google,
* if they are typing in a phone number,
* if they are looking up a contact by name,
* if they are replying to a sent message,
* and so on.
My thought is that if we provide a little detail about each configuration - especially those that aren't working, that we might be able to figure out what's really going on.
Thanks.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant General
So far seems the majority of people are using the "Cloud" Google/Gmail Account to store their contacts and do not have the "Error In Server Response" problem. Few SIM card saving people said they have an issue but most of those have always seemed to work. Nobody has voted saving to their Phones as of yet....
Mainly cause SIM only saves basic information...the Name & the phone number so little room for error in storing the Contact data.
Contacts saved to Phone can save pictures, addresses, e-mails etc etc so I think because of that ability to save additional information it affects formatting somehow when the number is pulled and transferred over to the MMS messaging when creating a new picture message to send.
Seems like best answer for everyone is to use their Gmail/Google account to save & edit their Contacts if saving to Phone keeps causing the problem. Which is probably what I will do but have been avoiding because I do not want to see all my Gmail contacts and e-mail contacts on the phone at the same time hence why I liked keeping a clean Contacts list primarily on my phone.
***I Love all the people that voted I'm retarded
feelx77, it has nothing to do where the contact is saved, and EVERYTHING to with whether or not there are dashes in the phone number.
A phone number with dashes, ie: 000-000-0000 = "error in server response", every time, no exceptions.
A phone number without dashes, ie: 0000000000 = works fine.
Ah, but it does matter where it saved because certain locations willl or will not let you edit the dashes out and/or because SIM already saves the contact information in a basic information format without pictures, addresses, e-mails etc etc. Which is stated in my lenghty long post. Removing the dashes is already a well known solution but depending on where contacts are saved it may not allow the editin gor it may still not work with or without adding the 1 or +1 as well.
I'm full aware of the dashes removal trick. Hence why I recommended that maybe the MMS.apk (Touchwiz Version Messaging Program) or the Contacts.apk that hands over the contacts header to the MMS.apk should be rewritten/reprogrammed to automatically remove dashes in the phone number header regardless of what saved source was used IE: Gmail, SIM, or Phone.
Also this "Error In Server Response" is strictly in regards to MMS (Picture Messaging when creating a new picture message and selecting existing Contacts from within the Touchwiz Messaging app. This is not in regards to standard SMS (text messaing)
Clarified further?
BUMP
Its been a while so thought to BUMP for more poll statistics etc.
I finally caved last month and just moved my contacts over to my Google/Gmail account and as expected, as already known, I've had no problems sending MMS that way or off my SIM card. Just gave up trying to fix or get MMS Picture Messaging to work with having my contacts saved to the phone. Only saved contacts saved to the phones memory always returned the "Error In Server Response" when selcting a contact in the drop down in the messaing app.
Over all I'm going to like using Google/Gmail saved contacts better, was just avoiding as I was too lazy to port them all over and the error or issue should not have existed in the first place using phone saved contacts.
Just wanted to share, and BUMP this thread for anyone still having issues or wanting to vote in the poll. Laterz...
Hi all, sorry for the new guy question (at least that's what I think it is):
Problem Statement - I have my phone set up to make all calls through google voice. This works fine. However, the phone.apk and thus the call log always shows the google voice routing number as opposed to the person I am actually calling.
Review - I have done some searching and it appears this is the same thing on, at least, some other devices (SIII for one). I have not found any way to "fix" this, however, and am reaching out here. It may be an LG thing or an ICS thing or no thing at all.
Solutions:
Question 1 - does anyone know if there is any solution to this?
Question 2 - in doing some looking around it seems that the best approach might be to try a different phone.apk. The best approach I have seen, but have not yet tried, is to download the stock ICS phone.apk from here: http://forum.xda-developers.com/showthread.php?t=1735507 or something. change permissions to rw-rw-rw- and copy into system/app . will this work? What is in there now is LGphone.apk, do I have to change the name of phone.apk to LGphone.apk?
Thanks in advance for any consideration of this.
Best Regards,
Dave
I'd like to find a resolution to this issue as well. it's rather frustrating. and no, i will not be adding the Google Relay# to my contact list as a workaround. i just want the call log to report the contact i called..
Anyone find a solution yet?
I figure once the AOSP 4.2 roms have their camera and GPS issues sorted out, I won't be bothered by this issue any more.
Sent from my LG-E970
GV outbound call log repair
The only way I found was to install this app called GV Outbound Call Log Repair. I've tested it and it does work. This app seems to periodically wake up, contact GV and replace the number in the call log with GV call log number.
saratv said:
The only way I found was to install this app called GV Outbound Call Log Repair. I've tested it and it does work. This app seems to periodically wake up, contact GV and replace the number in the call log with GV call log number.
Click to expand...
Click to collapse
Thanks for sharing. I just bought it and it's working great so far. The only concern I have is that it syncs your call log every 30 seconds which seems like a battery drain. I wish you could set how often it syncs. At any rate any fix is better than none :good:
I recently got an SGS5, and I noticed something that has started to annoy me. Judging on what I can read online and from googling I am not the only one annoyed by it. But so far no one has actually provided a viable and working solution as far as I see it.
Problem:
I have several contacts with multiple phone numbers under them, and when I get texts from the various number it creates one new thread/conversation pr number they text me from and its getting to the point where it is getting annoying. Isn't there some way to fix or correct this?. ie where the phone defaults to respond to the last number it got a text from, from that contact, or that it simply defaults to sending a text out on the default selected number or asks?.
I am not looking for something or a solution that will merge all my threads back in time, but for something that works going forward so that all threads created from today and onwards gets merged.
I know Google Hangout apparently can do this, but I don't want to use Google Hangout as my default messaging app, and I am presently using HandCent in case there is a setting inside Handcent that I just need to set.
But I hope someone might have a working solution to my problem/issue & thanks in advance.
I get service related SMS from different sources such as VK-XXXBANK, AB-XXXBANK etc. Because the same provider sends the message from different source each time, there is no continuity. Only way to restore sanity is to merge all such threads together into one mega thread so that the timeline is proper.
DISA actually does this and I have been using this for sometime. But due to some reason in case of re-installation or change of ROM, it will not load any old conversation until the same sends a new message. This leads to many old messages not being visible at all even by searching. I have to abandon DISA due to this reason.
I am looking for another application that has this conversation merging feature. QKSMS has this as a filed bug but there seems to be no action in that front.