Can someone with the technical know-how post a link to some of the gingerbread apps.
In particular, I am interested in the email app.
thanks,
bob
At least the 2.3 email.apk is (ALSO) missing the > Next and < Previous buttons!
like many other email.apk 's.
If you install the Android SDK you can install Gingerbread (2.3) yourself very easy and start an Android Virtual Device, a full graphical emulation of an Android device running the latest software. Very nice to see and test, and functionality is excellent.
Bump
Sent from my PC36100 using XDA App
I also would like the new email.apk but for a more specific reason... it includes EAS (exchange activesync) functionalities that allow 2.3 gingerbread to connect to an exchange 2010 server that has applied the SP1 service pack.
as of yet, the email.apk included up to 2.2 has not worked with the new EAS features. I loaded up an emulator and have verified that gingerbread email.apk DOES in fact work with our exchange server, but I don't know how to pull this specific email.apk
I used to use ES file explorer to pull apks but on gingerbread ES file explorer FC's.
someone link it and you'll be my hee-row
infotechsailor said:
I also would like the new email.apk but for a more specific reason... it includes EAS (exchange activesync) functionalities that allow 2.3 gingerbread to connect to an exchange 2010 server that has applied the SP1 service pack.
as of yet, the email.apk included up to 2.2 has not worked with the new EAS features. I loaded up an emulator and have verified that gingerbread email.apk DOES in fact work with our exchange server, but I don't know how to pull this specific email.apk
I used to use ES file explorer to pull apks but on gingerbread ES file explorer FC's.
someone link it and you'll be my hee-row
Click to expand...
Click to collapse
I haven't had a chance to test this in any other Exchange environments, but I did manage to get my Droid on 2.2 (no, not 2.2.1, so the Exchange fixes had not yet gone into place) our Exchange 2010 (SP1) without having to modify or replace my email.apk. I simply had to go to Settings > Location & Security > Set up screen lock > PIN and enforce a 7-digit pin to unlock my Droid. I was then able to setup my mail profile. Once it was setup, I disabled the PIN requirement, and everything still worked fine.
I work in IT, and I know our sysadmins pretty well. They were actively working on getting Android devices on Exchange 2010 at the time, so they may have put in a fix that made my own fix a pure coincidence. Still, the problem with older email.apk apps not working seems to be directly related to policy requirements on Exchange 2010 that didn't exist in previous versions of Exchange. My theory is that the new policy checks for certain security settings and that enforcing a PIN to unlock the phone somehow satisfies this policy requirement.
As I said, this may not work for you, and it may be a coincidence on my part. I'm quite curious if this fix works for you so I can advertise this to our end users when we migrate the rest of our faculty and staff (I work at a university) to Exchange 2010.
pekka91166 said:
At least the 2.3 email.apk is (ALSO) missing the > Next and < Previous buttons!
like many other email.apk 's.
If you install the Android SDK you can install Gingerbread (2.3) yourself very easy and start an Android Virtual Device, a full graphical emulation of an Android device running the latest software. Very nice to see and test, and functionality is excellent.
Click to expand...
Click to collapse
I have also noticed that Email 2.3 also breaks my ability to use the camera as a video recorder... can anyone else confirm this?
Related
Firstly I take no responsibility for issues caused by this "fix". A nandroid backup is always recommended. It has been tested with MCR r4 WIP and Exchange 2010, no other roms have been tested.
Since FRF91 2.2 has been released a number of people have had difficulty connecting HTC Mail/Stock Email to Exchange Active-Sync. Like a number of organisations using Exchange we have the security options set to "accept client certificates". It seems since FRF91 has been released this setting stops phones without certificates from connecting with a username & password.
The fix is a new libnativehelper.so installed in /system/lib I personally have no idea what the file does or doesn't do, it appears that its been built from source in order to fix this problem!
All credits to grennis. If you wish to read further into the fixes technical details, see here.
How to install attached zip (this is not an update zip):
1. Extract the zip someplace handy
2. Boot your phone into your preferred recovery
3. Run 'adb shell' (this gives you a shell on the phone)
4. Run 'mount /system' (allows writes to the system volume)
5. Run 'cd /system/lib' (enter the system lib directory)
6. Run 'cp libnativehelper.so libnativehelper.so.orig' (make a backup of the original file)
7. Close the ADB shell
8. On your PC, run 'adb push libnativehelper.so /system/lib' (copies the patched file to the phone). This should return a message similar to '1138 KB/s (202976 bytes in 0.174s)'.
9. Reboot the phone
Finally if someone wishes to provide an update zip I will be more than happy to add it to the original post. I however don't have the tools here right now.
Great job! Does this fix also sorts the "This server requires security features your phone does not have" issue? (that enables the pin code for exchange policy)
masi0 said:
Great job! Does this fix also sorts the "This server requires security features your phone does not have" issue? (that enables the pin code for exchange policy)
Click to expand...
Click to collapse
I would like to know this as well.
I only get it to work with HTC Sence ROMs, but they are not stable enough. DJ Droid has performance hickups. I want to go with OpenDesire1.6b and test this fix.
When I do, I'll let you know.
xf0rz said:
I would like to know this as well.
I only get it to work with HTC Sence ROMs, but they are not stable enough. DJ Droid has performance hickups. I want to go with OpenDesire1.6b and test this fix.
When I do, I'll let you know.
Click to expand...
Click to collapse
Thanks mate!
Well I hope this helps in some way, it was just research on my part not the actual fix. I was specifically looking for a fix for my above issue.
xf0rz said:
I would like to know this as well.
I only get it to work with HTC Sence ROMs, but they are not stable enough. DJ Droid has performance hickups. I want to go with OpenDesire1.6b and test this fix.
When I do, I'll let you know.
Click to expand...
Click to collapse
Tested it with OpenDesire 2.0, didn't change it.
Too bad....have to go HTC Sence ROM.
This fix only disables part of the SSL code so it can connect to servers with optional client certificates. It won't effect any of the policy options.
ritdaw said:
This fix only disables part of the SSL code so it can connect to servers with optional client certificates. It won't effect any of the policy options.
Click to expand...
Click to collapse
So this does not enable the pin?
I hate the interface of touchdown (and having to pay for exchange functionality )
tested this fix with a few roms and none of them works.. been not able to connect to my company exchange since hero and legend with htc stock mail..
im using moxier mail now .. and thats the only app i can use to connect to my company exchange mail..
There is a simple workaround on rooted phones for the Exchange security policy without having to replace the original mail app. I also posted this in the Android 2.2 Email.apk - Bypassing Exchange security policy - APK Attached thread in the Evo forum and am making a new thread here in case people have missed this very simple workaround. I am using it on an account on a Exchange 2007 server and I believe Exchange 2003 works as well. I heard from one person who did not have good results with Exchange 2010. All exchange functions work fine without any issues. I am using the stock email app so this only applies to the stock email app that forces a password security policy.
I am using an app called Autostarts found in the market (less than a dollar - I am not the developer) that allows disabling the exchange policy on restart. The setting can be found under Device Admin Enabled. Make sure you are in USB Debugging Mode before disabling the policy.
If you already have an Exchange account set up yet:
Install Autostarts from the Android Market and run. Find and click the Device Admin Enabled entry and press Mail (Exchange security policies) and select Disable (acknowledge the warning about disabling a system component). Close Autostarts and reboot the phone. After restart, change your screen lock under security to whatever you want (None, Pattern, or PIN).
If you don't have an Exchange account set up yet:
Install Autostarts from the Android Market then set up your Exchange account and let Exchange force the password policy. After the exchange setup is completed, run Autostarts and find and click the Device Admin Enabled entry and press Mail (Exchange security policies) and select Disable (acknowledge the warning about disabling a system component). Close Autostarts and reboot the phone. After restart, change your screen lock under security to whatever you want (None, Pattern, or PIN).
Is there any freeware tools?
Hi,
Thanks for posting. Is there any freeware tools available for this purpose??
Thanks
I just installed the program and then realized you need to have your phone rooted. How would I do that and what are the effects of rooting the phone? This is the easiest option I have seen so far depending on what has to be done to the phone to make it work.
It would also be nice to shut down all those horrible programs that keep restarting that I never use.
Thanks
Works on 3.70 kernel Fresh ROM 3.5.0.1
I am running fresh 3.5.0.1 on my HTC Evo and this method worked for removing the Exchange security pin requirement. My company uses Exchange 2007.
UPDATE:
My phone started prompting me that my server requires the security profile. It won't refresh the email account unless I turn it back on.
thanks for the awesome work!!
forceOnature said:
I am running fresh 3.5.0.1 on my HTC Evo and this method worked for removing the Exchange security pin requirement. My company uses Exchange 2007.
UPDATE:
My phone started prompting me that my server requires the security profile. It won't refresh the email account unless I turn it back on.
Click to expand...
Click to collapse
I also started getting the warning after upgrading to roms based on 3.70. The workaround still works for those on the earlier roms. I'll see if there is any other graceful way around it.
Sent from my EVO using XDA App
I don't see the Device Admin Enabled entry in AutoStarts. Am I missing something? I've enabled the USB debugging and I'm running a rooted Captivate/Galaxy S.
Thanks,
Landon
I don't know if it's part of the HTC sense or android framework.
Sent from my Evo using XDA App
This isn't a good solution...although you can disable the remote admin, the corporate exchange account alerts you that "security policy needs to be updated"...thus you can't check emails...
So after posting I got off the stock ATT rom and installed the Cognition 2.3 rom. Everything was great after that and worked like a champ. I just tried upgrading to Cognition 3.0 and the fix here broke again. I'd rather stay archaic and not have that dang password than run the latest and greatest and have to deal with it. When you guys are saying your running 3.5 and 3.7 what are you referring to?
Thanks,
Landon.
I knew I should have waited before posting...
I reinstalled Cognition 3.0 on my Captivate and tried the email.apk here.
http://forum.xda-developers.com/showthread.php?t=729753
Worked great again and didn't need autostarts. Woohoo!
Landon.
Loophole closed?
It would *appear* that Google closed this loophole, perhaps in Gingerbread? I just tried the latest MIUI and WarmZ ROMs (both of which are GB based, AFAIK). While this still enables the option to change from PIN to pattern or none under security, as soon as the next sync I am re-prompted about the policy, and if I accept it re-enables the setting in autostarts. I switched back to IncROM which is 2.2 and this procedure still works. If this loophole was indeed closed I am so bummed. I'd rather forgo using Exchange entirely than put up with a freaking 8-digit PIN every 15 minutes. And I can't seem to find a Mail.apk for Sense that has been modded to bypass this stringent policy. Blackberry users on the same Exchange server don't have to unlock their phone all day long, so why does Android's default behavior require this?
(I'm on an HTC Incredible)
+1. Agree with Stretch2m.
Really annoying have to enter pin code every 5 minutes or so. Especially when I'm in a hurry to access e-mail or other stuff...
Anyone out there who can assist with GB 2.3.3
Please help!
I am on an Epic with Syndicate frozen 1.1.0.... i enabled corporate exchange sync and it made me install the pin lock - which i want to disable...
Please can you post - NOOB version of the directions and also if anyone knows if this works on Epic with this custom ROM.
THANKS!
Since I have a lot of passwords I needed a password manager which will fit my needs. I did not want a manager that keeps my passwords safe on their servers but I want to export my db so I can have a backup! That's why I created PassLock password manager and I release it to the market for everyone.
PassLock keeps your passwords safe using AES-256bit and is free.
- You can group your passwords
- You can change/edit your records and also transfer them to an other group
- You can change your master pass
- You can import/export your database
Anyone that will give it a shot please leave feedback.
Since v1.0 I have changed some things that you can find below.
Changes in v1.5.1
Disabled auto-complete/auto-suggest words in passwords fields.(This might not work for all devices and all android versions.Trying to improve)
Changes in v1.5
-Show/Hide option when you type your master pass
-Lock database only and not exit
-Highly configurable password generator added
Devices Support
Unfortunately google does not release yet any documentation about 2.3.5 and also I can not create an AVD with this version for testing the app.
I have test it on 2.3.3(API 10) which is also has the same API with 2.3.4(API 10). If google changed the API level in 2.3.5 it might not work and I will fix it when released.
As far for the SGS2 I am not sure why is not working for some of you...Maybe it's the rom you are using?!As I can see 15 SGS2 has the app working fine!
For any other devices I have to search more so please post your device with the rom you are using and if it is working or not.
Thanks!
Note: The 3 permissions that required are just for the import/export of the database and for the ads!
Download from here
thanks, id much rather have a local manager then a cloud manager.
Showing as incompatible with my Thunderbolt. Running A05PTh30RY 1.3X which is Android 2.3.5
So why does the app need internet access?
If it's supposed to be a local pw manager i don't see the need for any network access at all, specially not internet.
Ads supported maybe
Wraios file Maybe you could add froyo support too? Very nice app.
None of my device supported, neither NI Adam nor Galaxy sII
Works great on Galaxy S XXJVP 2.3.4, Speedmod T5.
seems to work, but can I access it while on the browser to fill fields or is it strictly a look up your info in this program then go to the browser and enter it manually? (or copy paste)
Would be nice if there was an option to autofill
I just installed on my Atrix. Seems to be working okay. I will do some more testing with it later. Seems to work as advertised--good and simple. Thanks for the dev work.
Will not install to my Tmo Hd2 running Android
The app doesnt work on many phones I think you need to fix it to gain wide popularity.
But anyways Thanks
And after going to my blog, I think you will Thank me also.
See here http://www.techofweb.com/google/android-passwords-manager.html
But again I dint like its non-working on many Android devices.
Hope you will fix it soon.
@jwgizmo maybe you do not have a 2.3+ version?!
Thanks vostdev
I've been seeing a lot of requests recently on StackOverflow and the android-developers group for help with building and extending the Launcher2 from stock AOSP.
I've tried building the ICS launcher myself a while back (June 2012) and succeeded fairly well.
I open sourced my efforts here:
https://github.com/RaghavSood/CompilingLauncher2
What doesn't work:
Adding a widget to the homescreen crashes the app as it uses a system level permission. Installing via root into the same place as other system apps may fix this, but I haven't tried.
The app list is strangely magnified. I had this working correctly at some point of time, but then I changed something and it got all zoomed in. Widget list is normal sized though. I don't remember what I changed though, as it was back in June.
If someone is able to fix it, I'd welcome patches and bugfixes. If not, I'll be getting back to it after march, as I have exams right now. Just dropped in to share a mostly working and compiling version.
EDIT1
After a request from a friend earlier today, I've also modified the JB 4.1 Stock AOSP 4.1 Email client to compile with the public SDK and published it here:
https://github.com/RaghavSood/CompilingAndroidMail
Gmail IDs currently login and sync and work fine, but hotmail IDs seem to result in server errors.
Reserved for future use.
Hi all, Updated to CM10.1 AOSP 4.2.1 Jellybean on my HTC Sensation. All works excellently other than I can no longer connect to Exchange, getting the "this server requires security features that your android..." error. I've Google it and looked on this forum but can't seem to find any definitive answer. My Sensation is running the above ROM, rooted, and, Android 4.2.2 and the Exchange server is 2003. Firmware is 3.3 which I had to update prior to this ROM. Nothing has been changed on the Exchange server and indeed until I flashed this new rom it sync'd no problem. My previous rom was on ICS and I though I had heard that there were problems with ICS and active sync but can't find any details on it.
I tried this hack too http://forum.xda-developers.com/showthread.php?t=1117452 but it doesn't seem to make any difference. Interestingly enough, when I look at exchange via OWA and remove all mobile devices and then try to connect the phone again it shows up.
Is this problem because CM10.1 AOSP doesn't support EAS?
Thanks for any help.
Derf66 said:
Hi all, Updated to CM10.1 AOSP 4.2.1 Jellybean on my HTC Sensation. All works excellently other than I can no longer connect to Exchange, getting the "this server requires security features that your android..." error. I've Google it and looked on this forum but can't seem to find any definitive answer. My Sensation is running the above ROM, rooted, and, Android 4.2.2 and the Exchange server is 2003. Firmware is 3.3 which I had to update prior to this ROM. Nothing has been changed on the Exchange server and indeed until I flashed this new rom it sync'd no problem. My previous rom was on ICS and I though I had heard that there were problems with ICS and active sync but can't find any details on it.
I tried this hack too http://forum.xda-developers.com/showthread.php?t=1117452 but it doesn't seem to make any difference. Interestingly enough, when I look at exchange via OWA and remove all mobile devices and then try to connect the phone again it shows up.
Is this problem because CM10.1 AOSP doesn't support EAS?
Thanks for any help.
Click to expand...
Click to collapse
I am not any help, but I see the exact same issue with my EVO LTE on CM10.1. Shows up in the OWA devices log and everything. I have googled the heck out of it to no avail. I am able to gain access using the Touchdown app, but that is not a very good solution (and it costs $20 when the stock app is perfectly fine). I have not tried the custom apps that remove security like the one you link to. I do not mind the security features as much as I just want to connect to my work email. My company has an "iPhone only" policy, but If I revert back to a 4.1 ROM, I am able to connect. As far as I know, there is no way to restrict the type of device from the server side; it just checks to see if the correct sercurity is in place.