I just updated my Bell Galaxy S to the Froyo update Bell has waiting in KIES but has hidden from the public.
I quickly found out that anyone who is using exchange 2010 (and possible 2007) as an email server is going to be VERY unhappy. The security model needed for activesync to work properly with exchange 2010 is broken in JK3 and JK4 (the Bell Froyo builds). It seems that the model is there for full exchange security, but is broken and the phone will not let the server have access to things like password changing and remote wipe etc and thus the connection attempt during setup fails. There is a way around this, but if involves getting your exchange administrator to globally remove the default security policies in exchange (some say for a short time, some say permanently until the Android bug is fixed). Once the default security model is removed from the users Activesync profile then Android can connect and email can be set up.
Hopefully Bell realizes this as a major issue and this is why or at least one of the reasons why they have yet to release it to the public. Supposedly the issue has been fixed by the Android devs in current builds of 2.2.1 but whether or not this will trickle down to Bell's official release of Froyo for the Galaxy S is yet to be determined.
Needless to say, BEFORE YOU UPGRADE VERIFY THAT IT IS GOING TO WORK!
Another alternative is to pull /system/apps/Email.apk from the SDK (or various other locations on the web) and replace the one on your phone.
I've had to do this on mine and it's been working fine.
Originally, I used the "Improved Email" app from http://www.mwebster.us, but it's been having similar issues and the dev doesn't have time to fix it.. Too bad since it was THE best thing out there..
Riley
i'll say there's no need to panic yet, as it's not the final version for public use
that's why it's not accessible via KIES without the Registry Hack
AllGamer said:
i'll say there's no need to panic yet, as it's not the final version for public use
that's why it's not accessible via KIES without the Registry Hack
Click to expand...
Click to collapse
I agree, there is no need to panic, I just wanted to give a warning to those eagerly waiting for the update. Don't be quick to jump on the update or you may find yourself in a whole world of hurt.
Skud51 said:
Another alternative is to pull /system/apps/Email.apk from the SDK (or various other locations on the web) and replace the one on your phone.
I've had to do this on mine and it's been working fine.
Originally, I used the "Improved Email" app from http://www.mwebster.us, but it's been having similar issues and the dev doesn't have time to fix it.. Too bad since it was THE best thing out there..
Riley
Click to expand...
Click to collapse
You have to be rooted to install an alternate Email.apk correct?
xgumbyx said:
You have to be rooted to install an alternate Email.apk correct?
Click to expand...
Click to collapse
Probably..
Hello,
Has anyone unlocked their Vibrant to Rogers then updated FROYO through KIES? I'm wondering if it is ok to do so before I proceed.
AllGamer said:
i'll say there's no need to panic yet, as it's not the final version for public use
that's why it's not accessible via KIES without the Registry Hack
Click to expand...
Click to collapse
As a software developer, I would say you should be worried. Unless they have completely different version they're waiting to upload, there's no way they're going to make any viable changes now to the firmware when they publicly announced Froyo will be available in mid December. If they want to change that, they will have to delay the release again. Probably to some time in January.
Rashar said:
Hello,
Has anyone unlocked their Vibrant to Rogers then updated FROYO through KIES? I'm wondering if it is ok to do so before I proceed.
Click to expand...
Click to collapse
As far as I know, updating OS shouldn't take it into account whether the phone is locked or not, so I don't think you should have any problem.
Yeria said:
As a software developer, I would say you should be worried. Unless they have completely different version they're waiting to upload, there's no way they're going to make any viable changes now to the firmware when they publicly announced Froyo will be available in mid December. If they want to change that, they will have to delay the release again. Probably to some time in January.
Click to expand...
Click to collapse
Time wise that you are correct, if they do approve the current ROM as is, then it'll need to be manually patched later, or wait for the next ROM release.
the SDK work around is very sound and feasible for NON Standard users, people that don't even want to root their phone will be out of luck unfortunately
usually those kind of file swapping requires rooting.
I'm experiencing exact same issue now. There is no way I can benefit from my Exchange account with this Froyo release.
As soon as you have Exchange account with Synck ON + Auti-sync ON it kills th battery in 3-4 hours. Constantly high CPU + network traffic.
Having only Emails with pull interval option is not a good workaround as Exchange users mostly benefit from Calendar sync, and not only emails.
When Auto-sync is OFF calendar is not updated automatically.
Can someone put any instructions on how to replace email.apk? What version can we use on Froyo? is it from 2.1 ?
vluzhko said:
I'm experiencing exact same issue now. There is no way I can benefit from my Exchange account with this Froyo release.
As soon as you have Exchange account with Synck ON + Auti-sync ON it kills th battery in 3-4 hours. Constantly high CPU + network traffic.
Having only Emails with pull interval option is not a good workaround as Exchange users mostly benefit from Calendar sync, and not only emails.
When Auto-sync is OFF calendar is not updated automatically.
Can someone put any instructions on how to replace email.apk? What version can we use on Froyo? is it from 2.1 ?
Click to expand...
Click to collapse
What Exchange version are you running? Do you have admin access? If you have 2010 I can help you get your phone syncing without needing to root it but it involves removing the default security policy for exchange so the server does not check if it has admin access to the phone during setup. If you have a large exchange organization then this probably isnt the best route for you. For me it was fine as it is my own personal server with minimal users/phones.
Does anyone know if the same flaw applies to hosted Exchange - microsoftonline exchange mail service?
xgumbyx said:
What Exchange version are you running? Do you have admin access? If you have 2010 I can help you get your phone syncing without needing to root it but it involves removing the default security policy for exchange so the server does not check if it has admin access to the phone during setup. If you have a large exchange organization then this probably isnt the best route for you. For me it was fine as it is my own personal server with minimal users/phones.
Click to expand...
Click to collapse
It is large organization. And it is Exchange 2003.
I tried Touchdown today. It also has issues connecting and reports Too Many timeouts during one minute. But it has option to wait in case of such timeouts so it does not drain the battery. On other hand with such a wait Exchange is useless as I do not ger Push at all.
Is there any update on Exchange issue?
My phone behaves weird all those days.
I'm on JK4 and our Exchange 2003 just log error every second (it is Err 3005 Http code 400 in event log). The only way to keep my phone alive is to either disconnect from Exchange or turn off Background Data. Both leads to the same result - no sync.
I tried all email.apk available with exchange fix - no luck.
Related
All,
I've let the first release of Imap Pusher Service out of the bag. It's still pretty rough, but if you configure it right, it works well enough that you may get a lot of enjoyment out of it.
The program runs in the background and subscribes to IMAP IDLE notifications. When the notifications arrive it can do a send/receive on the PocketOutlook account you specify, effectively enabling push email for your Gmail account (or other imap server that supports the IDLE command).
Again, there are some known issues with the current version (I will hopefully address these soon), but I would like to know what you think. Here's the link.
http://www.codeplex.com/ImapPusherService
Update: version 0.2.0 is released
Changes: more descriptive error messages, ability to turn on trace log to help me diagnose problems.
If you are having issues you would like to resolve, capture the trace log and send it to me.
Update: version 0.2.1 is released
Changes: found bug which was causing client to not be able to reconnect in some cirumstances, should be resolved.
Update: version 0.2.2 is released
Changes: fixed problem where IDLE command was not getting refreshed when IMAP server was being to chatty.
Update: version 0.2.3 is released
Changes: fixed problem where if IMAP server says that it has a server error this was ignored.
Update: version 0.5.0 is released
Changes: program will atttempt to connect data connection if not connected.
some resource leaks have been fixed, will hopefully prevent the hanging.
Update: version 0.6.0 is released
Changes: program allows you to save your settings, and will not prompt you next time you start it. To get the prompt again, currently you need to delete the settings file. Note that storing your settings stores your encrypted password on your device, and since this is an open source program, anyone can lookup how I do the encryption, so only use this option if you are comfortable, and change your email password if you lose your device!
Great
Great idea but... I can't manage to get it work.
I previously had a Gmail POP3 account which i setup to get mails manually.
Then I ran IMAPPusherservice, filled up parameters, OK... and then still waiting for emails...
What am I doing wrong ?
Thanks
Greg
gregouille said:
Great idea but... I can't manage to get it work.
I previously had a Gmail POP3 account which i setup to get mails manually.
Then I ran IMAPPusherservice, filled up parameters, OK... and then still waiting for emails...
What am I doing wrong ?
Thanks
Greg
Click to expand...
Click to collapse
Maybe (hopefully) a simple solution, did you enable imap in your account settings in gmail?
It works great with my GMX account, well done!
But it uses 30% CPU if there is no data connection active, nor does Pocket Outlook play a sound when it receives the email...
works great!
Works great even with google apps gmail. Thanks
I'd like to mention once again the full service of Mail2Web. I'm very happy with it.
For those who don't know: they're offering Free Exchange-Accounts there.
This means you can sync your contacts, todo's, calendar and your e-mail with it. The Microsoft DirectPush is screaming fast!
But another solution i'm taking a deeper look into, is Z-Push. It's an opensource implementation of the ActiveSync protocoll. Which basically means you'd be able to have the same functionality as with an Exchange-Server.
It runs out of the box with a php-enabled webspace (need the right to set aliases via .htaccess). Had to figure it out myself, but the guys in the fora are kind. Another advantage of this solution (beside it is OpenSource and you can extend it yourself) is the possibility to plug it onto various groupware solution.
BTW: Push-GMail is the most popular example in the forum there.
Sry for my english..
Greetz
i have problems with .net framework.
which one do i need?
snudel said:
i have problems with .net framework.
which one do i need?
Click to expand...
Click to collapse
I use .net framework 3.5
yeah, this release is quite a rough cut. its not very graceful if you enter your password incorrectly (double chck this if its not getting new mail). Or if you don't have the data connection runing already. for now it would be best to tell your data conection to sty on. I'm on a kaiser and I can easily use kaiser tweaks to do this. ad it was the default mode for my ppc6700 with sprint.
the reason why i'm bothering with this rather mail2web is that with mail2web you are entrusting your mail with yet another party, when google now supports everything you need for push obo.
anyway, if you configure this guy appropriately, even this early release should work for you. but if you are having trouble I hope to have a release out soon that wil identify your problems with ease. it just neds to contend with all the work I get paid to do ;-)
At the moment it requires .NET CF 3.5. This isn't strictly necessary from a functionality standpoint at the moment though, so I may try and downgrade it, if thats a problem.
client seems to disconnect, and not reconnect, after a while (mine was connected for a good 36 hours, this last time). I will have to track this down when I release a version with more tracing information (hopefully tonight).
this would be a great application to have once it starts working properly.
right now i use this other app whcih is a sms switch. you forward gmail to your sms address. when your phone gets the incoming sms for new mail, it automatically opens up poutlock and send/receives and gets you the new mail. this works great because you dont need to always be connected. it only connects when you get new mail. only problem is it uses SMS so if you dont have a unlimited text plan it's gonna really hurt you.
if you can develop this program it would be a great alternative. it would be even better if you dont always have to be connected as to save battery power.
The reason why I have released this is that it works pretty darn well now. With a glitch or two. IMAP IDLE, like ActiveSynch Direct Push require an open data connection though, because of the way that they work. The key is that they don't have to be broadcasting all the time, though. This works pretty well battery wise for most modern phones.
Any other form of notification would have to come through the data interaction your phone makes with the cell towers (like SMS), so you would probably have to pay for it (like SMS).
I've noticed that the new iPhone SDK has some allowance for notification routing, but I would assume this relies on keeping a data connection open.
version .2 is released, check first post for details.
gmurray said:
At the moment it requires .NET CF 3.5. This isn't strictly necessary from a functionality standpoint at the moment though, so I may try and downgrade it, if thats a problem.
Click to expand...
Click to collapse
I've been looking for something like this for quite some time now. I'll give the current version a try. Being that most devices come with .NET CF, it would be nice if it wasn't dependent on 3.5.
version .21 is released, should be more stable, see first post or project page for details.
version 0.22 is released, check first post for details.
i have subscribed and keepin my eye out on each release. version .21 worked on and off. it didnt retrieve mail as fast as it should and sometimes it didnt retrieve at all. will try new version soon. thanks for developing it.
do you need to have your inbox running on the ppc for this to work or will it automatically open the inbox? just wondering if i should keep the inbox open in the background at all times as well. i tried it with the box open and close and it didnt work that time so it may be a glitch since it works sometimes when the box was open. but when i tried again with it open and close it didnt work so hard to tell.
I'm now test the lastest version.. I would really like the following features:
- save settings in .ini file
- auto start service if windows mobile starts
- Auto dial if no internet connection is present
This is great, it's working really well. I second the above post about saving the settings and auto-starting, but I'm guessing that's something you're planning on adding anyway?
I used to have Outlook check my Gmail account over IMAP every ten minutes and drop the data connection after two minutes of inactivity. I'm not sure what kind of effect leaving the data connection permanently on will have on my battery, but I'm certainly willing to give it a go for a day or two to see. Emails sent to myself as a test are coming through in well under thirty seconds from sending, and that's over a slow GPRS connection.
The area I live in doesn't have the best reception though, being virtually out in the sticks and all. I've not left the house since installing this, but what can I expect if I temporarily have no signal and the data connection drops? Will I start getting "Cannot connect" type error messages?
Thanks for your hard work, I'll be keeping a close eye on this one.
Hi all,
About a month ago I enabled pushmail (company Exchange server) on my Touch HD and ever since I'm getting the message: "recent changes to your device require a restart".
It pops up every once in a while and ask me to restart my device.
When I restart nothing changes and the popup keeps on coming. If I select to restart later (which I do now) the popup dissappears and my HD functions normally.
I searched the web and the only thing I could find was a discussion on an Exchange Server setting, which I already verified with our Exchange Admin.
Anybody outthere with the same problem or perhaps even better, anybody with a solution?
Thanks,
Lars
Probably not but is your Exchange server pushing some sort of policy to your HD?
deedee said:
Probably not but is your Exchange server pushing some sort of policy to your HD?
Click to expand...
Click to collapse
Deedee,
Thanks for the rely, but as far as I understood from our Admin no policies are pushed.
Infact I'm currently the only one complaining about this. But that could be because I'm the only one not using the standard issue company PDA.
Lars
We have the same problem here too. It seems that anytime a policy is in place, exchange attempts to push it every 4 hours (for us). Then if the system is not rebooted, then it keeps prompting about every 10 mins to reboot.
If your exchange admin will, he can turn off the refresh setting (not recommended) and it will not keep trying to update the device. If he adds new policies, then turn it back on.
This only seems to affect WM6.1 devices, (regardless of the carrier), and exchange 2007 SP1.
ggiedd said:
We have the same problem here too. It seems that anytime a policy is in place, exchange attempts to push it every 4 hours (for us). Then if the system is not rebooted, then it keeps prompting about every 10 mins to reboot.
If your exchange admin will, he can turn off the refresh setting (not recommended) and it will not keep trying to update the device. If he adds new policies, then turn it back on.
This only seems to affect WM6.1 devices, (regardless of the carrier), and exchange 2007 SP1.
Click to expand...
Click to collapse
Hi, i have exactly same broblem too, maybe somebody help?
Same problem here with the HTC HD2 (windows mobile 6.5).
Synchronization is set to manual. Each time I do a synchonize, all mail is received correctly, but immediately followed by the message that because of "recent changes" the device requires a restart. Really annoying.
Don't know a solution yet...will also check Exchange server settings.
HTC HD2 constant reset
Yes same thing is happening here but the information provided here has given me something to approach our IT department on a possible solution.
Will get back with any valuable information I receive.
Did you get a response from the IT department? I am very curious as well, since I am currently updating a small software agent on the device, and this has triggered the ssame behaviour.
This is getting frustrating. I rooted my hero and installed the Damagecontrol 2.0.8.1 ROM specifically because I figured that 2.1 fixes the issue with sending mail via Exchange. The phone still does not send mail. It at least gives an error message, but the message is completely devoid of any real info.
Does anyone have any way to get the phone to send email? I can't believe that this has not been fixed in a whole year.
-Randy
Did a search on this forums only and came up with 7 threads.
Mail Exchange
I didn't read any as I don't use exchange.
But you might want to start there.
If that isn't enough, try search the whole of CDMA.
Thanks,
Bubba.
P.S. might try posting in Damagecontrol dev thread also.
None of those threads mention anything about the sending issue.
I can't believe no one else is using exchange sync.
-Randy
zesta said:
None of those threads mention anything about the sending issue.
I can't believe no one else is using exchange sync.
-Randy
Click to expand...
Click to collapse
I am using exchange on Fresh 2.0d with no issues. My exchange server is running exchange 2003.
I have mail and contacts sync'd through exchange.
I'm having the same issue on my Exchange server. It has to do with plain text, if you reply to an email I bet it works. You're probably running something like Mail Marshal which is blocking the email. After you've sent a new email check the sent on your Outlook, and you'll see it's there. It's this leak because it worked fine for me on 1.5
It has to be your specific exchange server setup. I'm using Exchange Server 2007 via ExchangeMyMail and no issues.
I use both a 2003 server and a 2007 server and I have no issues sending or anything. Biggest issue I have is that GAL doesn't come to the phone, I have to search to find names instead of browsing a list.
I agree it has to be your particular setting. Have you tried checking/unchecking the ssl connection option? I think I recall reading that you could receive but not send depending on that option and how your server ia setup.
-------------------------------------
Sent via the XDA Tapatalk App
I have had no problems with the 1.5 or 2.1 software in connecting to my exchange server. What does your mail administrator say? They could easily pull the server log files to see what is going on.
I am the mail administrator
Additional research shows that it is a problem specifically with HTC devices. They are not properly implementing the protocol.
The app is setting the "Content-Transfer-Encoding" to "utf-8" which is invalid.
My mail server is Zimbra 6.x, which uses the Exchange 2003 protocols. My guess is that the true Microsoft servers either have specific support for the non-compliant HTC devices, or just happen to work because Microsoft isn't closely following their own standards (which happens more than one would think).
Looks like there is an unofficial patch to work around this specific issue.
Maybe some enterprising person can fix HTC's buggy app for them and include it in a custom ROM. I really like the HTC mail app otherwise.
-Randy
zesta said:
I am the mail administrator
Additional research shows that it is a problem specifically with HTC devices. They are not properly implementing the protocol.
The app is setting the "Content-Transfer-Encoding" to "utf-8" which is invalid.
My mail server is Zimbra 6.x, which uses the Exchange 2003 protocols. My guess is that the true Microsoft servers either have specific support for the non-compliant HTC devices, or just happen to work because Microsoft isn't closely following their own standards (which happens more than one would think).
Looks like there is an unofficial patch to work around this specific issue.
Maybe some enterprising person can fix HTC's buggy app for them and include it in a custom ROM. I really like the HTC mail app otherwise.
-Randy
Click to expand...
Click to collapse
do you have access to this unofficial patch. I'd like to try it out.
From what I've learned, this isn't specific to HTC, it's an Android thing. There was only partial support for security policies in 1.5 and now more complete support in 2.1. I've been successfully sending/receiving Exchange emails, contacts, and calendar items (sending and accepting) in both 1.5 and 2.1.
In 1.5 I had to have the Exchange admin change the mobile device support setting to allow all devices. In 2.1 he was able to change it back and my Hero then enforced a security policy that made me enter a PIN every time I unlocked my phone.
There were some general Android-specific issues before, but this is specific to HTC's broken mail application.
djorijun said:
do you have access to this unofficial patch. I'd like to try it out.
Click to expand...
Click to collapse
http://bugzilla.zimbra.com/show_bug.cgi?id=41145
All of the info and the patched file is there.
I am the Exchange 2007 admin here and I've never had an issue with my phone, on 1.5 or on 2.1 now. Both Damage's and the Fresh roms work fine to sync mail, contacts, and calendar items. I can send and receive just fine.
The global address list will not show up as a list, you will always have to search. That's the way it is implemented in OWA.
I would think that if you are not using Exchange Server, but someone else's implementation, it's not HTC that's at fault... It's more than likely the faulty implementation of the exchange clone.
CodeMonk said:
I am the Exchange 2007 admin here and I've never had an issue with my phone, on 1.5 or on 2.1 now. Both Damage's and the Fresh roms work fine to sync mail, contacts, and calendar items. I can send and receive just fine.
The global address list will not show up as a list, you will always have to search. That's the way it is implemented in OWA.
I would think that if you are not using Exchange Server, but someone else's implementation, it's not HTC that's at fault... It's more than likely the faulty implementation of the exchange clone.
Click to expand...
Click to collapse
I am using an Exchange Server that patch above isn't something I can use. I can receive emails, reply and forward but here's the zinger. when I compose it sends and the program known as mail marshal see's the email and stops it from sending. But when I go to my computer look in the sent folder the email shows up immediately. We've set Mail marshal to low and apparently the issue is with the Mail Format, and since I'm on 2003 the mail app doesn't let me change this option. I used Touchdown to see if this was the case, and BINGO I was able to compose without issue. Now I don't like the functionality of touchdown very much so I refuse to use it. Do you guys know of a workaround to change the mail format that's grayed out in the settings?
HTC's implementation is obviously wrong, as indicated by the details that have already been listed.
It looks like Exchange Server is either not checking for valid message headers (which doesn't surprise me), or is specifically allowing the invalid Content-Transfer-Encoding header.
zesta said:
HTC's implementation is obviously wrong, as indicated by the details that have already been listed.
It looks like Exchange Server is either not checking for valid message headers (which doesn't surprise me), or is specifically allowing the invalid Content-Transfer-Encoding header.
Click to expand...
Click to collapse
I see a different error, but my error is with MailMarshal. Does anyone deal with MailMarshal?
I ran into this issue at work with MailMarshal. You need to add an exception into MailMarshal to allow incorrect types through.
I did this a few months ago so I don't remember off the top of my head exactly where the change was made. (Not at work right now)
I'll let you know if I remember.
djorijun said:
I see a different error, but my error is with MailMarshal. Does anyone deal with MailMarshal?
Click to expand...
Click to collapse
This is what I had to do to get it working.
sorry...can't post links yet.
Go to mailmarshal site: m86security dot com
click on support and search for Q10166.
Read that article, it should help if you want to implement it.
yadnom said:
This is what I had to do to get it working.
sorry...can't post links yet.
Go to mailmarshal site: m86security dot com
click on support and search for Q10166.
Read that article, it should help if you want to implement it.
Click to expand...
Click to collapse
Thanks I'll do this when I get to work tomorrow.
In the Keynote, there was discussion of "over 20 new Enterprise features." From the Keynote, we know some of them were:
1. Auto discovery
2. Security Policies
3. GAL Lookup
4. Device Admin API's
5. Exchange Calendar support
From the Froyo test release I've see exchange signatures activated.
Does anyone know the rest? Any other discoveries that I missed? I'm really hoping that they enable folder push and the ability to transfer messages between folders in the final build.
Is there a list anywhere that you guys have seen?
gibosn6594 said:
In the Keynote, there was discussion of "over 20 new Enterprise features." From the Keynote, we know some of them were:
1. Auto discovery
2. Security Policies
3. GAL Lookup
4. Device Admin API's
5. Exchange Calendar support
From the Froyo test release I've see exchange signatures activated.
Does anyone know the rest? Any other discoveries that I missed? I'm really hoping that they enable folder push and the ability to transfer messages between folders in the final build.
Is there a list anywhere that you guys have seen?
Click to expand...
Click to collapse
For the GAL, if you compose an email and type the person's last name (provided that your GAL is "last, first") it'll autosearch the GAL. For the exchange calendar, this is supported out of the box and works well. It doesn't folder push unfortunately. I personally use rules that only work on my laptop (i.e. not server side rules) so that everything's in my inbox until I log in. Looks like the ability to move items into folders is also a no show.
Mi|enko said:
For the GAL, if you compose an email and type the person's last name (provided that your GAL is "last, first") it'll autosearch the GAL. For the exchange calendar, this is supported out of the box and works well. It doesn't folder push unfortunately. I personally use rules that only work on my laptop (i.e. not server side rules) so that everything's in my inbox until I log in. Looks like the ability to move items into folders is also a no show.
Click to expand...
Click to collapse
No, I know that those features are supported. I'm asking if anyone knows about the rest that don't seem to be so obvious. Perhaps they are something we will see in the final build?
Remote wipe
Devastatin said:
Remote wipe
Click to expand...
Click to collapse
Yea, that's another. That's puts us at about 7 out of 20. Any others?
yea i'll be honest i think folder pushing is a bit of an annoying oversight!
that's only other feature I could really do with!
Devastatin said:
Remote wipe
Click to expand...
Click to collapse
I haven't been able to get remote wipe to work on FroYo yet. Has anyone else?
http://www.zdnet.co.uk/news/mobile-...googles-android-into-the-enterprise-40089007/
http://phandroid.com/2010/05/20/and...-announced-with-ground-breaking-new-features/
We’ve added Exchange capabilities such as account auto-discovery and calendar sync. Device policy management APIs allow developers to write applications that can control security features of the device such as the remote wipe, minimum password, lockscreen timeout etc.
Click to expand...
Click to collapse
Looks like its there and no interface to use, or its not there and you have to wait for 'official'
Within Exchange, I can choose to Remote Wipe the device, the same way I can remote wipe an iPhone or WinMo phone. It just didn't do anything.
PIN enforcement is another. Because of our Exchange security policy, I get asked to set a Password or PIN while setting up activesync.
Another enhancement over 2.1 is Office 2007 files are supported (pptx,docx,xlsx) and quick office pinch-zoom works, so more consistent with rest of OS
I haven't been able to get my N1 set up for our Exchange environment. I'm coming off a 3GS and didn't have any issues. Our policy isn't set particularly stringent - don't allow non-provisionable devices, enforce simple passwords, password recovery and no encryption. Keep getting the "your device doesn't support the policies pushed by the server" message, or whatever it is.
I was wondering if certain elements of the EAS policy aren't supported yet? No clue.
satchmo_d said:
I haven't been able to get my N1 set up for our Exchange environment. I'm coming off a 3GS and didn't have any issues. Our policy isn't set particularly stringent - don't allow non-provisionable devices, enforce simple passwords, password recovery and no encryption. Keep getting the "your device doesn't support the policies pushed by the server" message, or whatever it is.
I was wondering if certain elements of the EAS policy aren't supported yet? No clue.
Click to expand...
Click to collapse
I had similar issues with 2.1. I had to purchase roadsync (trial is possible)
froyo addressed all that! Did you upgrade yet?
satchmo_d said:
I haven't been able to get my N1 set up for our Exchange environment. I'm coming off a 3GS and didn't have any issues. Our policy isn't set particularly stringent - don't allow non-provisionable devices, enforce simple passwords, password recovery and no encryption. Keep getting the "your device doesn't support the policies pushed by the server" message, or whatever it is.
I was wondering if certain elements of the EAS policy aren't supported yet? No clue.
Click to expand...
Click to collapse
I got that when my company switched over to 2007 exchange, until I let the IT department know that they needed to flip the switch for Android devices (they had done BB, WM, et al)...
In the short term I used TouchDown, it has a free trial period that you can use as many times as you want, you just have to set your account back up once a week.
pjcforpres said:
they needed to flip the switch for Android devices (they had done BB, WM, et al)...
Click to expand...
Click to collapse
Can you expand on that? I'm not familiar with changes that need to be made to allow Android via EAS. Am I missing something? Would rock if I could get it to work.
BTW, I did upgrade to Froyo.
satchmo_d said:
Can you expand on that? I'm not familiar with changes that need to be made to allow Android via EAS. Am I missing something? Would rock if I could get it to work.
BTW, I did upgrade to Froyo.
Click to expand...
Click to collapse
On my companies exchange 2007 server, they have the option to block or support mobile devices. Out of the box, it had no devices allowed to sync, so they had to turn on sync for different mobile devices. They had done Windows Mobile and BlackBerry, but forgot to do Android until I reminded them that some of use use Android devices, and would like to use our native exchange support.
I got the same error you do until they changed the security settings to allow Android devices to sync as well. I would assume this is your case as well, given that Android, even 2.1, supports more security protocol than iPhone's regarding exchange, and our exchange server is set up with high levels of security (uses SSL, etc).
Anyways, just email your IT department and ask them to enable Android devices for mobile sync... if they say it is already allowed, then ask them what the settings are supposed to be for your phone... I would bet $5 they just never turned on mobile sync for Android devices.
When I first recieved the Evo, everything synchronized just fine. Contacts both ways, emails, and calendar, but after about 5 hours, I started getting a notification that there were Exchange sync issues.
Whenever I would open up the accounts page under settings, I would see the sync symbol next to Contacts, repeatedly trying, over and over again. Finally, after a while, it stops, and a sync symbol with an exclamation point appears in the notification bar, as well as next to Contacts, and at the bottom of the accounts page, the same symbol with "An I/O error has occurred," explanation.
I don't understand what is going on here... as the original sync worked great. I can remove my Exchange account and re-add, and it works great for a few hours. Same thing if I wipe the phone completely, (factory reset.) The only solution I have had so far is to un-tick the Contact sync, and it seems to work okay, but obviously I need this service to work properly.
I have tried searching for a few days now and couldn't find anything really related to this. Some have had issues with reboots, and I had it BAD two days ago, and I finally wiped my phone. I do believe that there are some serious core Exchange integration problems on the Evo..
Does anyone have any insight on the matter, or should I just email HTC? Would a cooked ROM perhaps be any better?
Thanks guys
Same issue here. Very frustrating.
theadlee said:
Same issue here. Very frustrating.
Click to expand...
Click to collapse
Also, this DESTROYS my battery. If I actually let it attempt to keep syncing, it's completely dead within an hour.
Also have the same issues and was searching for answers to no avail. Another problem I have is that sometimes random emails just stop showing up on the phone. I can open once and view but later they are gone even though they haven't been deleted. I obviously see them on my outlook on my computer but never see them again on the phone. I hoping an update in the future will fix these issues as I never had a problem with my Touch Pro so I'm thinking it's not the server at work.
njward75 said:
Also have the same issues and was searching for answers to no avail. Another problem I have is that sometimes random emails just stop showing up on the phone. I can open once and view but later they are gone even though they haven't been deleted. I obviously see them on my outlook on my computer but never see them again on the phone. I hoping an update in the future will fix these issues as I never had a problem with my Touch Pro so I'm thinking it's not the server at work.
Click to expand...
Click to collapse
No problem on my Pre either, and I really don't want to have to buy 3rd-party software to fix something that is supposedly integrated into the phone...
Fellas, talk to your IT dept and have them check the Exchange logs. Different versions of Exchange have different levels of administration over mobile synchronization.
I have an EAS on my EVO with no issue whatsoever.
Bear in mind, Exchange 2003 doesn't seem to like Android synching with a mailbox that was previously synched with another device. I have seen synchs crash consistently until the synch relationship is deleted on the server side.
i have zero issues with exchange on the android.
you guy can try touchdown form the market. its the best exchange app out. dataviz has road sync which is another idea. i have not used road sync but have used touchdown on the hero. it works well.. bullet proof.
i would check with your respective IT Admins and make sure they allow Android handsets to access the server. some companies do not OR recommend you use a 3rd party app (such as touchdown)
Strange, I had my phone replaced yesterday, and it worked from about 5pm to 9:45am today, perfectly... then out of nowhere, it failed, and is now in an infinite loop to sync contacts.
Something to do with Facebook
I think it has something to do with contacts that are linked to Facebook. Very Very frustrating.
theadlee said:
I think it has something to do with contacts that are linked to Facebook. Very Very frustrating.
Click to expand...
Click to collapse
I just created a ticket with my IT department to investigate the logs to see what is going on. Something tells me it's related to Sense, and not my Exchange server at all... considering that multiple Windows Mobile phones, and my Palm Pre have all worked fine... even some of my old Sprint dumbphones worked okay, when I used Sprint Email.
I would root my phone and try a standard version of Android, but isn't it Sense that does the Exchange sync? or is that built into Android at this point?
ScrapMaker said:
I just created a ticket with my IT department to investigate the logs to see what is going on. Something tells me it's related to Sense, and not my Exchange server at all... considering that multiple Windows Mobile phones, and my Palm Pre have all worked fine... even some of my old Sprint dumbphones worked okay, when I used Sprint Email.
I would root my phone and try a standard version of Android, but isn't it Sense that does the Exchange sync? or is that built into Android at this point?
Click to expand...
Click to collapse
I've tried touchdown and can't even get it to create an account. I think it maybe something with my work server that these programs don't like. I know that my employer was too cheap to get an exchange server so they use some sort of activesync client that runs on the standard server. Not an IT guy so I don't know how this affects things but I do know that I had no issues like this with the windows mobile email. On top of my contacts not syncing, I still have emails that randomly disappear or no longer have a body to the email after viewing once. Very strange and very frustrating that I have no work around.
Well we are definitely using Exchange 2007, and I had to bypass our whole "ticketing system," and contact our Exchange/Outlook department secretly. I am hoping for a response in the next day or so. I bet you anything it has to do with the policy-push that happens once or twice a day... basically re-affirms your device is compliant. IE, if you went through and manually disabled your password protection, this is SUPPOSED to push out the requirement again.
One thing I should probably try, is re-wiping my phone and NEVER installing lockpicker... even though the phone is nearly non-functional without that handy utility, perhaps that can be causing issues?
Been running HTC Sense, and Exchange on my EVO without any issues for three weeks.
I have not made any changes to the original setup, other than adding about ten apps from Market Place.
Holy crap, I just got a call from two highest-level managers (with attitude, I might add,) that no one from the company is _ALLOWED_ to help me get this to work. It's an unsupported device. So are iPhones and all WM phones... so this is bizarre.
Basically, this ActiveSync service is a back-door offering, with zero support, and everyone is real hush-hush about it. My asking to investigate the logs seems to have REALLY irritated people in my company, and this is a big place. I hope I didn't create waves... damnit Android, you are ruining my life!!
What assholes. I hate these arrogant ass IT guys. They need to recognize that they are a cost center which only exist to make you a more effecient employee. If your effeciency is enhanced by using android vs a crappy blackberry, they need to make reasonable efforts to accomodate you.
I would send an email to THEIR boss, and ask him what the mission of an IT organization should be. And if he gives you crap, ask the CIO.
You don't understand... the top-dogs just made their call... the next higher up is the VP of our IT group... basically, if I bring it up again, I can consider myself terminated. I didn't realize this was such a sore subject, but apparently it is.
Apparently it has a lot to do with export control, policies, all sorts of random BS that I don't really know about. The ActiveSync service is mainly provided as a back-door 'friendly' service to help those who don't get corporate blackberries.
So it's totally unsupported, and I don't know anyone I can buy a few drinks for in order to get this fixed. I guess I'll have to work the other angle with HTC, but damnit, I already know nothing will help there. Even if they were to offer to help, my IT department would be less than willing to lend a helping hand.
Also, most of our stuff is out-sourced... but I know there are DEFINITELY people in my own building that can help me---I just don't know who, and I also don't want them getting in trouble.
It just bothers me that when the iPhone came out, there were enough 'important' people around, so that even though it's "not supported," our environment was definitely modified to work with the phone...
Le Sigh.
Man, this problem is killing me... I have delete my exchange account twice a day.
man, I wish there was a solution to this... no one else is having this issue?
You could root and get Cyans new Froyo build, it has native exchange support. There is definitely differences between HTC sense exchange and Android exchange.
fragchild said:
You could root and get Cyans new Froyo build, it has native exchange support. There is definitely differences between HTC sense exchange and Android exchange.
Click to expand...
Click to collapse
Does this build support Camera and 4G? I keep hearing about these new ROMs and all their problems.
I just installed TouchDown and figured I'd give it a whirl. If the new Froyo build works on all aspects, I'd obviously rather have that. I like the integration of the stock solution. I don't like that I will have to use TouchDown for everything... calendar alerts, and everything, but we'll see. I also hate that I might have to pay $20 for something that should work out of the box...