So I've gone through a total of 6 Palm Pre's & Sprint allowed me to choose a different device, so I just picked up a Hero...
The problem is, of course, lack of simple pin & remote wipe support for ActiveSync, so I am unable to use my corporate email on the device. I have tried using TouchDown & that doesn't even work. It seems that my work may have a filter I was told by support for TouchDown(I work for a large technology company, so IT policies are very strict).
My question, is there any way, by rooting or whatnot, to get my device to support ActiveSync fully? Or a way of somehow fooling EAS into thinking I have a simple pin setup & remote wipe available?
I really wanted to start using an Android device, but shoot, if i can't even get my work email on it, its pretty pointless...
Thanks alll!
So I've gone through a total of 6 Palm Pre's & Sprint allowed me to choose a different device, so I just picked up a Hero...
The problem is, of course, lack of simple pin & remote wipe support for ActiveSync, so I am unable to use my corporate email on the device. I have tried using TouchDown & that doesn't even work. It seems that my work may have a filter I was told by support for TouchDown(I work for a large technology company, so IT policies are very strict).
My question, is there any way, by rooting or whatnot, to get my device to support ActiveSync fully? Or a way of somehow fooling EAS into thinking I have a simple pin setup & remote wipe available?
I really wanted to start using an Android device, but shoot, if i can't even get my work email on it, its pretty pointless...
Thanks alll!
Click to expand...
Click to collapse
Thought 2.1 took care of those security issues. Only other option is touchdown in the market, it works with complex security options.
-------------------------------------
Sent via the XDA Tapatalk App
Hello,
i am running Froyo on my nexus one.
When configuring a new Exchange support, i get:
""SETUP COULD NOT FINISH.
This server requires security features your phone does not support""
Touchdown is working fine and reports the following securities features:
Allow simple password
Password/PIN required
Failed attempts 10
Min length 5
Min Complex 3
Timeout 1800 sec.
Password recovery
So the question are:
1) Which of this securities is not yet implemented natively in froyo?
2) Will it make it in the final froyo release?
If any of you has some inputs, it would be nice to share.
Thanks in advance!
Best
dico
Sorry I cannot help with your problem other than to say that I have exactly the same issue. I am really shocked that Google have not got this fully working. We are hardly talking about a new protocol here!
Whilst I have Touchdown and have done since moving to Android last year, this single problem has stopped my company giving everyone Android phones. Come on Google, get it sorted!
Maybe because the foryo we got is not final? Ever thought of a unfinisched product that you use, is not finisched?
jaapschaap said:
Maybe because the foryo we got is not final? Ever thought of a unfinisched product that you use, is not finisched?
Click to expand...
Click to collapse
I think the point is that proper exchange support should really have been there from day one.
You just don't build a serious, high end smart phone with out proper integration to corporate mail (read exchange ).
Unless you're Google apparently.
badomen said:
I think the point is that proper exchange support should really have been there from day one.
You just don't build a serious, high end smart phone with out proper integration to corporate mail (read exchange ).
Unless you're Google apparently.
Click to expand...
Click to collapse
Well, I work and live in the corporate world and use my phone as such a device. I guess I sort of agree with you there about the exchange support, I can't really legitimize why they didn't incorporate this almost-brainless sync method.
Does the security policy of your works exchange server require to have a screen lock pin, specifically mobile device security policies? I noticed, after wiping from Froyo(with screen lock pin prior to EX acct) to CM and then back to Froyo(no screen lock when configuring), that I received an error that setup could not finish, I assume this is because without having a screen lock policy set up on the phone the exchange server will not authenticate to my device. Check that out. Also, this is not a finalized product.
Mine works fine...and I manage the Exchange system here...no problems.
My biggest issue is that Google has provided half-ass support for Exchange, and this version is no different.
You can't even move an item to another folder from the inbox with the stock Froyo.
The Desire Rom has the functionality and ability, best interface and options compared to the stock Android.
The stock Rom sucks honestly...if it weren't for Desire...I would still have my iPhone, even they figured out, licensed and got working properly the Exchange support 18 months ago. Windows mobile devices have had this for 3-4yrs.
My first post! May as well make it contributory.
It is interested to note that one may need a PIN lock set up first *before* adding an exchange account that requires one... I know I haven't been able to get our 2.2 Nexus One's to connect to our corporate Exchange Server for my girlfriend and I.
Let me go change to a PIN lock and see what happens when I try to add the exchange account...
Yep, no go still. "Unable to open connection to server."
They really need to add a Verbose button to these error messages.
still not working
Hello,
I tried setting up a PIN code before starting up the email application.
Does someone knows where to find the email app log file to see what is not good?
Thanks in advance!
best
CJ
To be honest, I tried using touchdown (which as great as it is, still lacks a lot of features), then tried using the Froyo Email/Calendar apps... Nothing has ever worked smoothly with Exchange + Android. I ended up migrating my email server (luckly it is only a personal email server) to Google Apps, and I have never been so happy with the performance and stability.
It is a tough cookie to swallow, but gmail is much better then Exchange on Android...
So, this sounds simple; but I guarantee you it is not.
I just got my Note5 about 2 weeks ago; and despite some missing key features, I really like it. Until today.
Carrier: Sprint (who apparently doesn't have 24/7 customer service)
My fingers were a little dirty (which they have been before) and my scanner wouldn't unlock the phone. Cleaned them and now it's already locked and seems to not really check the prints anymore?
First attempted fix: backup password, I know I set it up...but it doesn't work. None of the passwords I might use will work.
Second attempted fix: Google signin, I have a free google apps account and apparently using my whole email address as username doesn't work on this; also tried just using the plain username just in case. I know the password is correct. I'm the domain administrator.
Third attempted fix: Android device manager, tried setting a new password on the lock screen and was greeted by the infuriating message "Since google has verified that your screen is already locked, the password you set won't be needed"
Fourth attempted fix: chat with samsung support, which was utterly useless. Although I did find out that samsung has their own unlock utility...except that it has to be setup beforehand.
Fifth attempted fix: bang head on cement...hasn't shown any signs of working yet. Although I feel less frustrated.......and less conscious.
Theories: free version of Google Apps, sucks (the apps themselves are great)...I've had tons of trouble getting signed into certain google features over the years. Also I have no option for a support PIN to use to contact google support.
I think that my latest OTA update may have somehow changed or reset my backup password.
The last theory is whomever changed Android device manager to not reset lockscreen passwords whenever you want to...basically made that tool half as useful as it should be and completely useless to me.
Anyone have any other ideas, that don't involve a full wipe?
I was finally able to gain access to my phone. I had to disable two-step verification in order to sign into my google apps account from the lock screen.
I am having the same issues and tried ALL of the fixes you tried except I didn't get the notification to login with google. When does that happen?
I had the problem, too. I ended up having to factory reset. REALLY irritated by this.
8-31-21: My report on the death of this app for the NST is a little premature. See post #5, etc., for a "fix". It worked for the poster and it worked for me. It might work for you.
Don't shoot the messenger...
Sometime in late 2020 or early 2021 it became impossible to negotiate an initial login with the Kindle app (yes, even with the OTP they email you). I've checked the security certificates and they are fine. I've tried installing the app on newer devices, going all the way to Oreo. Same behavior. A logcat on the NST shows a failed SSL negotiation so it looks like the server just won't talk to the old app any longer--at least for an initial authorization. That's the very bad news.
There is a tiny bit of good news for those who already have the Kindle app installed and authorized. At least on my three devices it continues to function completely. You can still check out Overdrive Kindle books and send them to your device and the same book on different devices appears to sync. You can also sideload .mobi books and read those. The clock is, however, probably ticking.
I mention this as a warning for anyone who has a legacy Kindle installation and is thinking of doing major work on their device. If you uninstall or wipe out the Kindle app, it's gone for good. It may be possible to use something like Titanium Backup to restore the app. I was able to find all this out after a reset and then restore my NookManager backup and the app worked fine.
Edit: I have done a little experimenting and the app authorization token appears to include a lot about the device and system. So it's not possible to use Titanium Backup. I tried this on a FW 1.2.1 installation with a working copy of Kindle. Then I updated and rooted FW 1.2.2, installed the Kindle app and then restored a Titanium backup from the same device (but with FW 1.2.1). It failed to initialize, asking to register again. I've had success only in restoring a NookManager backup from the same device with the same FW, etc., and in cloning a device from a NookManager backup. This is not something I would necessarily recommend, but you might have your reasons. However, when I tried to correct the MAC address, this threw off the Kindle app token and it reverted to asking for registration again. So there's very little wiggle room for preserving a working installation if you have to do any significant changing.
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
If the SSL layer is somewhere in Android oh boy that might be harder cookie to bake from my point of view.
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
I
Click to expand...
Click to collapse
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
Click to expand...
Click to collapse
My understanding of the issues is very limited. I once happened into a discussion where it was stated that apps which need to communicate with external servers contain their own SSL certificate which has an expiration date. If so, apps like that just die a "natural" death.
It's actually amazing that there are some apps requiring logins that still work on the NST. Two that come to mind are ancient versions of Pandora and TuneIn Radio. I use both and they still perform flawlessly. For now.
Until today I didn't know what Pandora is but I am familiar with TuneIn radio app. Good to know that some of those apps is still working. Well it just had to be complicated with SSL/TLS hidden somewhere in Android layer. I totally understand why people like Android user friendly UI and apps availability. Still gamble with Java seems that didn't paid of regarding promised platform crossing ability.
So either porting to a new Android version which probably will not be very new (low RAM) or making custom Linux which is anything but user friendly?
Edit: Scratch that question about Linux and the app OP mentioned! I just realize that there is no Linux Kindle app. It could be used through Wine and such witchcraft but that is stupid way of doing things on this device. Better option is to use it on PC and then pass it on to NST using Calibre IMHO. SSL/TLS although remains as weak spot for the time being. Oh well... If that issue with certificates get somehow fixed maybe Kindle cloud reader from browser could reclaim at least part of functions of dedicated Kindle app.
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
wrexroad said:
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
Click to expand...
Click to collapse
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
nmyshkin said:
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
Click to expand...
Click to collapse
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
wrexroad said:
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
Click to expand...
Click to collapse
Excellent. As I expected based on legacy installs continuing to work, once the credentials are on the device, you're good to go whether you use single or two factor login after.
I had a password issue with Amazon awhile back and I'll bet that's where the problem originated. When I changed my password, authentication must have gone to two-factor. I need to check that, but I'm pretty sure that's it. What great news! Back to seamless library book checkout and download, all on the device!
BTW, the version of the app you mention is the only one that works (again!) on the NST.
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
wrexroad said:
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
Click to expand...
Click to collapse
Mmm... I'm glad you posted this before I started testing. I have two NSTs with working Kindle apps right now and I don't want to trash those while tracking down the "solution". I need to think about how I'm going to approach this.
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
wrexroad said:
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
OK, that's what I had hoped for and expected since my two working installs were made before my auth. got changed to two-factor. With really old apps you never quite know how server negotiation is going to evolve.
I hope to give it a try later today.
wrexroad said:
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
When I went to my Amazon account it seemed like 2SV was not enabled, by which I mean that clicking on "edit" for the settings generated an email which contained a link that took me to a page with a button that said "Get Started".
I didn't pursue this. I didn't see anything about turning it off--or should I have gone farther along?
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
wrexroad said:
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
Click to expand...
Click to collapse
Yeah, this is not working for me. I looked at the 2SV stuff again this morning and thought, "well, I'll just set it up and then disable it". Except I don't own a mobile phone (no, truly, just an emergency ancient (non-text message) device I keep in my glove compartment), and the QR thingy woud do me no good with the NST. So I'm cooked.
Despite apparently not having 2SV set up, now I can't even generate an OTP email when I try to login with the Kindle app. But my two working installations continue to function. Puzzlement.
Edit: I had a friend with a mobile phone help me out. So I finally got to where I could "disable" 2SV. But it made no difference. Still can't log in or even generate an OTP email by trying to log in. I'm glad this worked for you and I'd like to think it might work for others, but alas my account appears to be "special".
Edit-Edit: Yeehaw! It took a lot of fumbling for me with the unwieldy password I had to recreate in the near past, but by clearing the dalvik cache and making sure that 2SV was actually listed as "disabled" at Amazon, I was finally able to log in a new installation!!! Now I don't have to run a "clone" of another device on this particular NST. Thank you, @wrexroad, for taking the time to look into this and communicate your findings. One big step back from the brink for the Kindle app
That's awesome, I'm glad you got it running! In the future, if you need to get a password via text, you can use a temporary number here: https://sms24.me/en/countries/us/
Hey folks,
I just stumbled into this NST world and want to share my experience with the Kindle app. I'm on FW 1.2.2, and used NookManager to root. I replaced the certs file as recommended in another thread. Once I was ready to login, I enabled 2fa on my Amazon account in a browser. The instructions there clarified that I would need to use PASSWORD+OTP when registering my device. Previously I had tried only the OTP, or only my normal passwrord, but those failed. Appending the OTP to my password, I was able to login.
Hope that helps anyone else who has reached this point.
Are there any other users experiencing (solved?) issues with the Volkswagen remote access app? This app had been working well up until march of this year. Then the app just started throwing an error stating "unable to log in at this time" when I attempt to log in, but before I even enter any data.
I have tried all the usual steps including factory reset of my S21-Ultra to no avail. VW tech support has not responded to my requests for assistance. I had given up hope. Then, during July I had to switch handsets for a short time. On a moto stylus 5G, the app worked correctly with my existing account data. When switching back to my S21 I have the same error message.
Thanks in advance for any suggestions.
For the record - issue solved by pure focus, commitment, and sheer f*cking will.
It seems the car net app REQUIRES chrome to perform the initial connection setup. It does not utilize the default internet application. I prefer the samsung internet beta and promptly disable chrome after resetting to avoid downloading any updates for it. While I was on the temporary phone (knowing it was temporary) i did not go through my usual customizing / disabling. Once set up I check the "keep me logged in" option and I can disable chrome again.
Wow, talk about browser monopoly. Really dumb implementation, thanks sharing the cure