where? how?
i only have SyncML, Roadsync, google...
LE: I mean native support, not roadsync to make it clear...
bump.
is there a "standard" mail apk that i could use to add an exchange account?
we know 2.1 supports multi exchange. 1 is for gmail but another one?
why on earth did sony ericsson disable this?
I'd like this too. Just got rid of my milestone which had exchange support in 2.1.
WTF? : is any possibility change mail.apk with native exchange support from diferent device ? (after root) or it`s problem litle bit deeper ... kernel module etc. ?
i love SE engineers
I'm interested to an exchange client ..decent
RoadSync it's a bug with some code lines
Related
Hi,
I have been using the Megatron v1 ROM on my O1... The question I wish to ask is whether there is a difference in the default mail app of the original LG FW and Megatron ?
Because I was able to connect to my company's Exchange server and sync mail but I cant do so now after switching to Megatron ... (It could also be a policy change by my company and I cant reach out to the admins) ... So I dont want to unnecessaily go back to LG FW as the Megatron ROM is simply awesome ...
PS: I was unable to post directly in the Megatron thread as I am new to the forum and they wont let me post in the development section
I think there is something different between the way the stock mail app interacts w/ an exchange server and how Megatron interacts w/ exchange server. For me, I had no problem setting up my exchange account with the stock phone. When I installed Megatron, the exchange server required me to add a security password/pin to my phone. Not sure how Megatron triggered the exchange server to be more secure, but it does.
It also removes the Wifi Calling ability, too, unfortunately. These 2 things led me to go with JoeMomRom instead.
-Nick
After switching from SGS to SGS2 I'm experiencing problems with my work mail. We use Zimbra as an Exchange alternative.
The problem is, all incoming mail is shown with full headers and source. HTML-mail is shown as source as well. In addition, special characters seem to be messed up. IMAP from the same server works correctly.
I've had the problem confirmed by a friend on his SGS2.
Has anyone else experienced this? Is anyone out there using the SGS2 with an Exchange server? If it works correctly for you, maybe it's something with Zimbra and the email-app version on the SGS2. Would it be possible to replace the new version with the one from the original SGS?
Edit: Maybe I should also mention that I sync contacts and calendar from the server, or I would just have switched to IMAP and waited for Samsung to fix the app.
Same thing here...
Hi,
I have exactly the same issue with SGS2 syncing with Zimbra 7.1.1.
Works well with email app non modified by Samsung on Nexus S.
Zimbra support guys said it is not their issue and marked the bug as WONTFIX:
Thank you for the information and the research. I have raised the following bug report which has been marked as WONTFIX as it is not a zimbra specific issue:
Zimbra Bug ID 60480
However there may be some updates posted there from time to time so it may be worth adding yourself to the CC list of the bug.
It is difficult to submit the bug to Samsung as they say "we do not offer support for ActiveSync problems - contact Microsoft"...
Same problem for me and all my collegue, and for different phone (GS2, HTC HERO with cyanogenmod, NEXUS S, etc). With HTC sense on my HERO it's OK. I think it's relate to Zimbra (or Exchange 2003 protocol?) Any info?
I forget, my workaround is Enhanced Email from the market (paid application).
When I used the stock email and activesync against my corporate email (Zimbra via NotifyLink) I noticed that the MIME headers were coming through in the e-mail and making it unusable.
The Zimbra guys think its a bug introduced in 2.3.x of the Samsung enhanced e-mail client in the way that it handles MIME (as it worked on 2.2.x):
Bug 60480 on bugzilla zimbra com (cant post link)
New to all this so my question is how feasible would it be to see what changed between 2.2 and 2.3 and possibly fix 2.3 e-mail client
Another workaround would be to find a 2.2.1 email.apk and use that instead? (i'm on 2.3.3)
Hi there, I'm now working over CM 7.2 for Atrix 4G, here's the thing... I'm tryiing to get email sync native, as it is in CM9, but I'm not sure of what shall I modify... there's the option of adding a "work account" and add an e-mail this way but it's kind of frustrating... not very friendly for what I'm trying to do...
So resuming, I would like to integrate the e-mail sync option in CM 7.2 the way it is in CM 9...
Any ideas?
Thanks you all guys
PS: Sorry about my english
noone? basically what I'm trying to do is:
In CM9, when you want to add a new e-mail account from setting, it just asks you for e-mail adress and pw.
In CM 7.2 it asks (work account):
*e-mail adress
*pw
*domain/user name
*pw
*server
So I want CM 7.2 adding e-mail account settings yo be just as simple as tey are in CM9
is there a way? or just keep adding it from e-mail app?
Don't quote me on this but I believe the newer exchange apps have code that does much of the work for you by querying the Exchange server and figuring out the domain being used as well as the username from your email and password. That is why they probably don't ask you for the extra fields.
If this is true, you might need to look into how the Exchange apps accomplish this and see if you can somehow make modifications yourself.
I am not near my dev machine and so I don't remember if the android source contained the relevant code for Email.apk. You will have to check.
Cheers!
I'm actually thinking on that but it's quiet annoying to compare line by line apks...anyway tonight think I'll do that...tweeted turl to see if he can help me with this stuff...but I'm starting to believe it can be so much work for a simple stuff like it actually is...the problem is mail.apk may have some sync issues the way it's now done
Sent from my MB860 using XDA
Lately I have been wondering why Android still does not have native support for CalDAV & CardDAV, when both have been the de-facto open standard for contacts and calendar sync for years. Is there no native support because Google wants it to make it more difficult to use alternatives to their services? (In my case: NextCloud/ownCloud, which I can add right away even to an old Iphone, but still do not work with android out of the box without something like DAVDroid) Or are there plans to integrate it into future versions?
What's the problem with installing an app? Android has a native API for contacts and calendars, so I guess they can't be accused of making it "difficult". They probably just don't want to make it "too easy".
One could also ask why 99,9% of app developers don't support APK distribution but require users to use GApps & Play Store …
xv22gk said:
What's the problem with installing an app? …
Click to expand...
Click to collapse
Which is not answering my question whether it is planned to have native support for CalDAV/CardDAV.
CardDAV / CalDAV are open standards for data exchange just like IMAP, NTP, SMTP and so on. It would be only natural for android to support them