Getting exchange activesync working on Android devices has alaways been a huge challenge, while being the single most important feature for me. Same settings would work fine on one Android device and would fail on another. e.g. my exchange server settings work well in T-Mobile myTouch 3G, 4G and the Moto devices, yet would fail on the Samsung Vibrant and T-Mobile G2 (biggest bummer). It seems to boil down to an enforcement by the exchange server requiring a to set a PIN on the device. This is when hell breaks loose. On some devices it goes through fine and on others it pops up the error message "Setup could not finish The server requires security features your phone doesn not support". The biggest surprise/bummer thus far is that my settings work on Verizon's Galaxy Tab while fails on T-Mobile's version which throws the same error message.
So is this a limitation of the deivice H/W itself or is it a limitation of the SW build in the device? Nonetheless, this is way too frustrating. Unfortunately my T-Mobile Galaxy Tablet has to go back if this is not fixable.
Related
G'day all XDA'ers. I got my phone from eXpansys unlocked just a week or so ago. This is not my first Windows phone but my first WP7 device for sure. I have been using the forums and the wiki to get my Focus up and rocking.
All is going well except full data service. No i know it sounds odd but data service is "kinda" working. By that i mean that i can get my corporate Exchange email ok and for some reason m.cnn.com will come in ok. For a local newspaper site it will render about 1/4 of the main page and thats it and Fark i will get a logo. All other sites fail in either stock IE or Browser+. Its trying.......just not succeeding. Looks like GMail and Hotmail can't sync over this borked celldata connection either - company Exchange only.
Last phone was a Blackberry and verified with the carrier that no flags or anything needed to be changed on their end. I verified with the *#7465625# that all locks are disabled. Most annoying is that i popped my SIM into my gf's iPhone and everything works fine.....and it was unlocked and she is with a different carrier.
I put on Samsung's Network Profile tool but i don't have any other network profiles to select. Auto config is on.
Not sure where else to look. Calls work, SMS works, MMS isn't supported on my carrier so didn't test. I really thought i had it figured out until the iPhone test worked.
For reference carrier is M3 Wireless Bermuda but to keep it interesting my liveID is registered to Canada.
Thoughts?
Also i got the Device Info app from Marketplace and see i am getting an IP and it is from my carrier's range. And though i should add that APN settings have been triple checked.
The Network Selection type is manual with carrier network selected and roaming is enabled.
And as an update the Hotmail did eventually update.......no word on the GMail
Little more detail
This might be a carrier limitation......maybe. I noticed that when i popped my gf's SIM into my phone i see a Digicel network profile now in Samsung's tool. Even after swapping out my M3 SIM the Digicel profile is still there - no M3 profile loaded/created. I need to get the data service on my gf's phone reactivated for a test but there might be something here.
Again....a small handful of sites work and Exchange and Hotmail works. I can't see the rhyme or reason of it. Google.com mostly loads (no logo) but detects my gmail account....but m.google.com won't work. Mobile version of bermudasun works but not other paper. m.cnn.com is groovy but not m.youtube.com.
will post back with more detail. Wish i could see what the carrier proxy or dns information was......
I am an Exchange 2003 admin at a company with over 500 devices using ActiveSync across multiple platforms and revisions.
We enabled ActiveSync policies this week, forcing a 4 character password down to the device, with the setting "wipe after x failed password attempts" disabled.
Within 48 hours, 3 users have reported their Samsung Fascinates (and one US Cellular Samsung Mesmerize - which appears to be the same CDMA Galaxy S variant) have randomly reverted to stock. The user was not doing anything in particular at the time, nor did they enter their PIN incorrectly.
Does anyone know if Verizon has acknowledged this issue, or plans to provide a fix? It feels wrong having to ask these users to go buy Touchdown, when every other Android phone works out of the box.
My guess would be that it's an issue with 2.1 not really the fact that it's a galaxy s.
2.2 has better support for exchange AS. Depending on the trust you can place on the user I'd suggest creating a new policy for them that doesn't require the pin but request that they use the pin, until the Galaxy S gets froyo.
I'll do a nandroid backup on my phone and enable the policy for my phone and see if it happens to me, I'm not running the stock kernel though so it could be different for me.
Unfortunately we can't do per-device polices with exchange 2003 without some trickery on a users extended AD attributes. And, since there's no way to identify Fascinate users, they report their AS user agent as 'android', so it's difficult to be proactive until they call in with the problem.
I don't think it's related to all galaxy s variants, plenty of Epic and TMobile Galaxy users are fine, but the US Cellular variant appears to be a direct copy of the Fascinate, also on 2.1update1, and exhibits the same symptoms.
Users are lying. They fat fingered the password or the screen came on in their pocket. I work IT in a company that has about 5k android devices and about 20k of iphone bb and windows phones. The exchange admin is a android enthusiast and we talk often, when they started enforcing wipe policy they were swamped by calls about devices wiping themselves but after users got used to entering the passcode the calls pretty much stopped.
Sent from my SCH-I500 using XDA App
Except we don't set that as part of the policy, as stated in the OP. I can mess up my PIN an unlimited amount of times with no ill effect.
There are threads about this on androidforums as well as the vzw forum, but I can't link with my low post count. I just wanted to come to the place where I knew there was the most knowledge with this issue.
Hmm, I have not specifically tested this, so I don't know if Samsung added this functionality or not, but the stock mail client for Android 2.1, to the best of my knowledge, does not support PIN code passwords. That functionality was added into Froyo by Google. I suppose it's entirely possible that the mail client on the Fascinate is buggy and causing this issue.
I know what you mean about having to tell them to pay for a mail app, but I think they'll be happy about it after the fact, after seeing how much better Touchdown really is. The stock mail client is so bare-bones, it's honestly quite ridiculous. Google really needs to get their act in gear and code a decent, full-featured mail client, because right now the iPhone beats Android at Exchange syncing, even though it also can't hold a candle to Touchdown.
Greetings. I am a new user to XDA but a longtime reader and geek who uses and is well familiar with multiple desktop and mobile OS's. I say this because the problem I am writing about is possibly the most confusing I have ever faced. In fact, if it wasn’t happening to me personally I would swear it was impossible, so please read on. I would be grateful for any – any – ideas. I will attempt to describe the problem and my troubleshooting steps as clearly and concisely as possible – but it’s a weird problem so needs some discussion.
PRECIS: Samsung Galaxy S II intermittently loses ability to connect to and sync with IMAP servers, BUT ONLY intermittently and ONLY on one particular mobile network. Much testing has been performed as detailed in this post.
HARDWARE / OS: Galaxy S II originally purchased on contract from Three UK, unlocked, and currently running Android 2.3.4, debranded to XXKG5 firmware and generic CSC XEU.
SIMs USED: Roshan (Afghanistan) pay-as-you-go and AT&T (USA) contract with unlimited international data.
SYNOPSIS: I have good data connectivity (slow EDGE, but generally reliable) from the local Afghan provider Roshan using my PAYG SIM. I am able to set up both of my IMAP accounts, have them log in, sync, send mail, etc, but after an indeterminate amount of time, routinely lose the ability to connect at all. However, all other data services and syncing continue to work fine (web browsing, Gmail, calendar, contacts etc) – only IMAP connectivity is broken. No errors appear, but mail just stops coming. Once this has occurred, the only thing that seems to correct the problem is time – it will eventually start working again, but is by no means reliable. Changing how often the accounts check for new mail has no effect. A change to Wi-Fi restores connectivity to the IMAP servers immediately, but then the problem returns over the Roshan mobile network. Yet, I can swap in my AT&T SIM and all works fine immediately, reliably, and never displays the problem. The IMAP connectivity issue exists only with my Roshan PAYG SIM, and only after some amount of time.
HARDWARE TROUBLESHOOTING: The phone and IMAP have worked fine on multiple networks in multiple countries. In the UK, on 3UK and Orange. In the UAE, on Etisalat and du – all with good HSDPA connections. In Afghanistan, the AT&T SIM connects usually to Etisalat but other networks as well, all with EDGE data where available. (Unfortunately for scientific testing, AT&T does not allow connection to Roshan.) And also in Afghanistan, my PAYG Roshan SIM works fine with everything EXCEPT the IMAP problem. Altogether, it seems the GS2 itself works as advertised.
MOBILE NETWORK (ROSHAN) TROUBLESHOOTING: The exact same PAYG Roshan SIM which causes the problem in the GS2 allows a reliably-syncing connection (and servers automatically detected, BTW) over the same mobile network to the same servers using my old iPhone 3G running iOS 4.2.1. Likewise, my boss has perfect service to these servers using this same network with his Roshan PAYG SIM in my old Nexus One on Android 2.3.4. And, my GS2 does fine on this network for all except IMAP.
ANDROID OS TROUBLESHOOTING: In an effort to troubleshoot a potential glitch in the OS, I have flashed multiple versions. The Roshan/IMAP problem exists on both the 3UK-branded H3GKF4 2.3.3 as well as generic XXKG5 2.3.4. And again, a Nexus One running 2.3.4 on the Roshan network does fine also – incidentally also in my office, so at least theoretically connected to the same cell path.
EMAIL CLIENT TROUBLESHOOTING: In an effort to isolate a fault with the Samsung email client, I purchased and installed Enhanced Email, with both 2.3.3 and 2.3.4 installed. Same results: fine on Wi-Fi, fine with AT&T, unreliable in both clients with Roshan PAYG SIM.
(LACK OF) CONCLUSION: Can it be possible that I have uncovered a ridiculously obscure bug? How can just one data service type (IMAP) be affected on just one network (Roshan) yet all other services are fine, and the IMAP problem does not exist with other SIM’s and/or networks? Is there anything something like a traceroute I could run to see what’s happening to my IMAP requests?
If you’re still reading, thanks for staying with me this far. I’m completely baffled, and frankly, more than a little frustrated that what is meant to be the best smartphone in the world can't reliably get my mail on the network I need it to, while a tired old iPhone and Nexus do so all day long. Any ideas?
Kind regards,
Adam
UPDATE: Did nothing, started working
All --
For the past two workdays, IMAP email has arrived in both the Samsung Email client (set to check every 5 minutes) and Enhanced Email (set to check every 10) on the Roshan mobile network. I have done absolutely nothing to cause this to happen.
Of course I am very pleased all is working as advertised, but the episode has still somewhat tarnished my previously stellar opinion of this phone and diminished my trust in it to a degree. Regardless, I'm glad. If the problem resurfaces, I will repost here.
I suspect the reader will agree that "it just started working" isn't a very satisfying fix, so if someone else experiences a similar issue with IMAP and/or knows more about how it works, I would really like to learn. Feel free to drop me a line on <<[myxdausername] at gmail dot com>>.
Kind regards,
Adam
Hi,
I am looking for help solving an issue that has me, my colleagues, and our IT department stumped. I have a Google Edition S4 running on AT&T. My colleague has the AT&T version of the phone. His phone can connect to our corporate exchange server normally, while mine fails with the following error:
"Couldn't Finish - This server requires security features that your Android device does not support, including <owa hostname>"
Any ideas what may be causing this? My device is encrupted and has a pin enabled.
anyone?
I have to admit I am a bit out of element here (with Samsung devices), but I am kind of at a loss on where to go for help with this so I thought I would throw this out there...
I have a customer that uses a proprietary app that includes an industry standard SIP softphone client, we have hundreds of these deployed and working fine, with the exception of bone stock Verizon branded Samsung Galaxy S7 (and Edge) devices but only when on WiFi networks, on mobile data it works fine.
EDIT: We discovered the Verizon Samsung Galaxy Note 5 is exhibiting the same behavior as well.
The client software (Mitel MiCollab for Mobile) installs and works normally when on mobile data, but the SIP softphone cannot register to the SIP server on any WiFi network. Take the exact same app and settings to any other device we have tried and it works fine. It is as if when connected to WiFi, something built into the device is blocking the ports used by the SIP phone, we have actually taken one and factory defaulted it, setup email and the client software without installing anything else and it still fails, so it isn't an app that is added by the user that is causing a problem. Other Samsung devices like the S6 and J7 devices work fine, so it is something specific to the S7 & Note 5 series.
Anyone have any ideas here? I have limited access to the device, just figured enthusiasts like XDA users might have some insight into the device.