Hi, I used to use the HTC twitter app in Sense. But from one day to another I cannot access anymore. I get the message "You entered an incorrect username or password". I tried with different twitter accounts but I get always the same error. I also tried to access with email and username.
Any idea what could be the problem?
Thx.
Little information that I bookmarked myself but not conclusive, just know we're done with Twitter apparently. Some help for you maybe is here (won't fix it but explains why you can't access like the rest of us).
Read CFB's explaination on this (Cudos to him again), concise explaination that is apparent throughout the web and Google search:
http://forum.xda-developers.com/showthread.php?t=562773&highlight=twitter,+peeps&page=34960
This is just a site I saved (I read here often):
http://phandroid.com/2010/09/01/htc-peep-or-friendstream-not-working-its-oauths-fault/
Have you tried out moTweet, many have gone this way and it is ok comparitively.
Thanks for this information. I was fearing something like this.
Actually I am using motweet since Peep is not working anymore.
Regards.
Not sure how deep your interest is in this but heres CFB's full write up, if you look at his last tweet at the bottom you get good news on recent developments.
http://forum.xda-developers.com/showthread.php?t=1101151
Peep is working again. Log out via Settings Tab > Data Services > Log out of Twitter. Then log in the same way. Keep in mind (if you read my posts about it) that this does not resolve the security issues with the application. It still leaves your session open to hijacking, but it does work again.
If HTC does not fix the problem, it will only go out again in the future.
hello friends,
maybe someone of you is able to help, or at least enlighten me about the cause of this:
since i use ICS on my note (about for 2 weeks, starting with stunner) i have REALLY BIG problems with one of my exchange accounts, the one which is running on a hosted exchange 2007 (second account with my corporate exchange 2010 is fine)! so until today i hoped that the "official ICS" for the note won't show this behavior, but now with a total clean install of the today released LPY and therefore OFFICIAL SAMSUNG ICS rom, the problem persists!
description:
95 out of 100 trys to connect to my exchange account fails with a message telling me that there is a security error (if needed i can provide some screenshots) telling me that either my username and/or password is incorrect! this makes it almost impossible even to simply add the account. and, on the rare occasions (which SOMETIMES can be triggered through a connection change between wifi and 3g) when the phone is able to connect (and sync), it stops after a few minutes again with the same error.
i re-added the account numerous times, tried everything which came through my mind (change password, enabled and disabled sec features) and trust me, i know what i'm doing here. i configure exchange accounts since almost 10 years from now!
clues:
there are a few tickets existing on http://code.google.com/p/android regarding this issue, but with different "flavours":
http://code.google.com/p/android/issues/detail?id=16992
http://code.google.com/p/android/issues/detail?id=19366
http://code.google.com/p/android/issues/detail?id=25315
to sum it up:
google developers are recognizing the problem (it seems to exist since android 3+ to some extent) but are unable to provide a solution until now. it seems to be a problem with an EAS policy refresh, which fails and therefore closes (or does not even open) the connection! a guy suggested to disable these policy refresh in the EX2007 config, but this would only be possible if you are the admin of this server (and i doubt that it would make sense, security-wise, too)!
another theory says this mess is due to implementation errors in the connection layer, which directly affects wifi and 3g connection behavior...
i guess that this problem would now get's more imminent, as this security error wasn't occurring at gingerbread. and now more and more people with smartphones will migrate to ICS!
what do you think?
does anybody else experience this? or am i one of the few unlucky bastards?
regards,
markus
so, is exchange 2007 working for everyone?
this would be important to know for me, because in this case i would have
to blame my exchange provider for wrong EAS settings!
can a few people with an exchange 2007 account confirm that their sync work flawlessly? anyone please?
Just realized my exchange account is not syncing unless I open the client.
My work is running exchange 2003
Never had this issue with imilka ROM weird
Sent from my GT-N7000 using xda premium
mardos said:
Just realized my exchange account is not syncing unless I open the client.
My work is running exchange 2003
Never had this issue with imilka ROM weird
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
This seems to be the case on all TW based roms, no matter if GB or ICS at least for me. It syncs fine with Hotmail service but not with my company's 2003 server so there has to be some incompatibility there. When disabling all syncs and re-enabling them it started syncing. Just had to wait for about 30 minutes to get all info synced.
E: On AOSP based (CM9, AOKP) everything works as it should right from the beginning without the extra hassle.
I'm working properly in Galaxy Note, from KKA to LPY, with Exchange 2007 SP3.
Syncing is correct in my case.
Samsungs version of ICS (or Gingerbread) doesn't communicate with Lotus Notes traveler active sync. Cyanogen 9 (ICS) is working out of the box. In Gingerbread the Traveler App is working but in Samsungs version of ICS the widgets dont work.
after fiddling around this WE i think there would be no other solution as reverting back to GB (which would suck, and therefore is no real option), or to change to a hoster with exchange 2010!
every client i tried shows the same behavior, if i'm able to establish a connection it won't last long till the security error reappears! this renders my account almost useless...
i will update this post if something changes!
Just upgraded my device to OTA 4.4 and Exchange services crashed every time I opened Email (I kept getting a message "Unfortunately Exchange Services stopped" repeatedly).
After deleting both the email account and the user certificate (we use certificate-based email authentication), I am unable to re-add the Exchange account back (after defining all credentials and parameters, I get a popup that says "Couldn't finish. Can't connect to server."). Additionally, I see a white triangle with an exclamation point inside in the notification bar. When I pull the bar down, the exclamation bar has a caption of "Network may be monitored by an unknown third party". When I click on that caption, I get a new pop-up saying "Network monitoring. A third party is capable of monitoring your network activity, including emails, apps and secure web sites. A trusted credential installed on your device is making this possible". There is a button underneath called "Check trusted credentials" and clicking on that takes me to a "user" portion of the trusted credentials store, where I see my corporate CA certificates.
In general, the issue of certificates issued by a non-public CA generating a "Network may be monitored" message has already been documented in several forums and there is an issue #62076 created for it. However, I suspect that "security features" introduced in KitKat are somehow preventing my device from using my certificate for email authentication (because device does not trust it). I knew I could count on Google to break the most used feature of my phone (email) and thus render it useless. Another win for the history books.
had the same issue after updating to 4.4. in short, i had to re-push both OA and CA certificates to re-establish the authentication system for work
aldouse said:
had the same issue after updating to 4.4. in short, i had to re-push both OA and CA certificates to re-establish the authentication system for work
Click to expand...
Click to collapse
I already tried that twice. No joy.
The most annoying part is that I also have a Nexus 10 tablet and it had ZERO problems after upgrading to KitKat (aside from the annoying "your network is being monitored" notification). This means Motorola yet again mucked with the stock Android install and broke it.
Any other ideas? I'd hate to go through a pain of reverting back to 4.3.
It'll work if you keep deleting, rebooting, then reinstalling the apk for email. At least it did for me. My company issues these certs, and I got it to work eventually.
Sent from my XT1060 using Tapatalk
So....here is what the issue is: https://code.google.com/p/android/issues/detail?id=61785
Looks like quite a lot of people are affected by this. I cant believe how sloppy Google's QA is if something as major as this was pushed out of the door.
Now I need to wait for Motorola to incorporate this fix into their build of Android, then for Verizon to "test" it and roll it out via another OTA update. In the mean time, my Moto X is as good as a brick because I cant get my corporate email/contacts/calendar on it.
Ridiculous!
Use another client
Touchdown is my client of choice and it works great with kit Kat
Sent from my XT1058 using Tapatalk
mj0528 said:
Use another client
Touchdown is my client of choice and it works great with kit Kat
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
+1 for touchdown... Worth the money if you rely on exchange email.
Sent from my XT1053 using Tapatalk
Network security warning cleared also
1ManWolfePack said:
It'll work if you keep deleting, rebooting, then reinstalling the apk for email. At least it did for me. My company issues these certs, and I got it to work eventually.
Click to expand...
Click to collapse
Can you clarify 'work' - I assume this means it is sync'ing - do you still have the security warning about the certificate, or did this get cleared in your reboot/re-install cycles ?
Thanks
Just wanted to update everyone - Google has stated that the issue is fixed "in a future release". One "minor" problem - there is zero information as to which release, as well as when it is going to be rolled out.
So....as of now thousands of people using private certs on Kitkat devices are still screwed and this number is growing by the day. In order to make it more convenient to pretend like the issue is minor and insignificant, Google has blocked further comments on issue 61785 after 260 people starred it, so now users that have an issue cannot even report it.
ek001 said:
In order to make it more convenient to pretend like the issue is minor and insignificant, Google has blocked further comments on issue 61785 after 260 people starred it, so now users that have an issue cannot even report it.
Click to expand...
Click to collapse
If the issue is resolved and Google has a rollout plan for the fix, what use is there for further bug reports or reporting? It just becomes noise in their bug tracking system. Is there a purpose for yet more people to say, "hey, yeah, I have this issue too"?
Strange, I have Exchange email set up on my Moto X 4.4 and synching without issues.
After the pop-up, I accepted or ok'd. We're running a 2010 Exchange Server.
SYNSYNACKACK said:
Strange, I have Exchange email set up on my Moto X 4.4 and synching without issues.
After the pop-up, I accepted or ok'd. We're running a 2010 Exchange Server.
Click to expand...
Click to collapse
Are you using a certificate issued by a private CA for ActiveSync authentication?
ek001 said:
Are you using a certificate issued by a private CA for ActiveSync authentication?
Click to expand...
Click to collapse
Under Exchange settings, Port is 443, Security type is SSL/TLS, client certificate is None.
Strange, I thought it pushed a CA though when I completed the set up.
SYNSYNACKACK said:
Under Exchange settings, Port is 443, Security type is SSL/TLS, client certificate is None.
Strange, I thought it pushed a CA though when I completed the set up.
Click to expand...
Click to collapse
That's the point. This issue only affects users that are using certificates issued by private CAs for ActiveSync authentication. If you are not using certificates, you would not be affected.
ek001 said:
That's the point. This issue only affects users that are using certificates issued by private CAs for ActiveSync authentication. If you are not using certificates, you would not be affected.
Click to expand...
Click to collapse
Not necessarily true. I use exchange email for work and although I can set up my account I cannot receive emails. I can send sometimes. But never receive.
via my slapped KIT KAT moto X
lowvolt1 said:
Not necessarily true. I use exchange email for work and although I can set up my account I cannot receive emails. I can send sometimes. But never receive.
via my slapped KIT KAT moto X
Click to expand...
Click to collapse
What you are experiencing is a separate issue, so please open a separate thread for it.
The issue being discussed here is a situation where an attempt to use private certificates for authentication while adding an Exchange Activesync account to a device running 4.4 results in a bogus "Couldn't finish. Can't connect to server." error message (while the device does not even attempt to go out and establish a connection).
binary visions said:
If the issue is resolved and Google has a rollout plan for the fix, what use is there for further bug reports or reporting? It just becomes noise in their bug tracking system. Is there a purpose for yet more people to say, "hey, yeah, I have this issue too"?
Click to expand...
Click to collapse
There are several reasons the thread should have remained open:
1. While Google is taking their sweet time to roll out a fix, someone may find a workaround for the issue. A workaround is certainly better than a phone with no email/contains/calendar (and no, nobody wants to pay for and use those crappy 3rd party email clients).
2. Having 10,000+ people star a thread gives a great indication of how widespread the issue is, hopefully giving Google developers a hint that it needs to be prioritized and rolled out ASAP (as opposed to incorporating it into the next general patch release).
3. Since most handset vendors customize their Android build, the issue may not exist on every handset made by every manufacturer. Someone may report that a particular device is not suffering from this issue, thus making it safe to buy.
4. If and when the fixed version of Android is finally rolled out and the "fix" does not work, users have no way to report it, other than opening a brand new thread and wasting more resources.
Ever since the KitKat upgrade, my stock email fails, with the message box: "Unfortunately, email has stopped", and an option to report it. I had read that there are some difficulties with exchange servers, so I deleted my exchange account, but the email program still fails in the same way. Thanks for any advice that you can give me.
EDIT: I fixed this by a full reset of the tablet. I think that the security features of exchange email got in the way and I just needed to start from scratch.
Nexus 4 Update, I got Lollipop with my device OTA.
I set up my Exchange account with Gmail application.
During the setup phase "Server Connection Can not Open" I get a warning.
However, the same user can set up my exchange account information to another android device.
Lollipop Before the current could use my Exchange account seamlessly.
Although I am not able to return to their factory settings repeatedly solve the problem.
Am I the only living such a problem?
You can tell where I went wrong?
This post was written by Google Translate. I was able to fully explain my problem.
Thank you.
Yunus YILDIZ said:
Nexus 4 Update, I got Lollipop with my device OTA.
I set up my Exchange account with Gmail application.
During the setup phase "Server Connection Can not Open" I get a warning.
However, the same user can set up my exchange account information to another android device.
Lollipop Before the current could use my Exchange account seamlessly.
Although I am not able to return to their factory settings repeatedly solve the problem.
Am I the only living such a problem?
You can tell where I went wrong?
This post was written by Google Translate. I was able to fully explain my problem.
Thank you.
Click to expand...
Click to collapse
Help Me :crying: