Database Info

Google News & Weather Widget Problems?

Wondering if any developer folks have noticed a problem with the Google News & Weather widget yesterday and today? I installed this on my EVO (GenieWidget.apk) because I love its simplicity and elegance, but it has been telling me "Sorry, unable to connect. Please try later" with a "Retry now" button.
I've discovered it's not just me, but other Android phone users too, so it could be an issue with the Google servers, but the thing that I'm trying to work out is who to contact about the problem. Is this a Google-developed widget or is there someone else who can be asked? Has this happened before and is there a fix?
I'm guessing there isn't much that can be done, but I thought I'd ask anyway.

I have the same problem. Can't find any info on who to go to on this.

Same problem here, it's got to be at Google's end (it's part of 2.x). I expect they're aware of it by now though.

same (UK), it's just not giving new content at all, last one is around 23-24h ago

Interesting. On another forum, I saw mention of a company called PalmarySoft who are apparently the provider of the backend of the widget (though I can't confirm that). They have had some kind of DDoS attack. Not sure if that'd be enough to kill the widget entirely, but who knows. Miss it already, one of my favorites, let's hope it gets fixed soon.

same thing here in tampa
it worked once this morning around 8:00 am for a few minutes, then couldnt connect again
and just when i got shawn1224's transparent version (no background)
http://www.4shared.com/file/IrjCMniv/GenieWidget.html

The server that supplies the News and weather is under a Ddos attack. Google Places is down too.

violent23 said:
The server that supplies the News and weather is under a Ddos attack. Google Places is down too.
Click to expand...
Click to collapse
how did you find that out?
a search turns up nothing for me

tnpapadakos said:
same thing here in tampa
it worked once this morning around 8:00 am for a few minutes, then couldnt connect again
and just when i got shawn1224's transparent version (no background)
http://www.4shared.com/file/IrjCMniv/GenieWidget.html
Click to expand...
Click to collapse
I'm also in tampa and yep having the same problem..

Hi all.
I was having the same problem as above but it seems to be fixed this morning ( in the UK ).
Cheers

tnpapadakos said:
how did you find that out?
a search turns up nothing for me
Click to expand...
Click to collapse
This is who provides the back end that the widget uses.
http://www.palmarysoft.com/all_news.php

Happy to say it's now back!
There was an update for Google Places in the Android Market this morning coincidentally.

violent23 said:
This is who provides the back end that the widget uses.
http://www.palmarysoft.com/all_news.php
Click to expand...
Click to collapse
thanks for the info, its up here now, too

[Q] Readers Hub

I got my tab in Norway yesterday and i noticed that the news and magazine section is not activated yet. Does anyone know when "Service will be available soon" is? Like 1 week, month, half a year?
Update: News and Magazines seems to be available to most people now, just open Readers Hub and click on Install. Personally i only got the update for Zinio.
If you don't get the install option try to go into "Manage applications" find the Readers Hub app and clear data, then start the app again.

Been trying to google an answer myself. Wished Samsung would come out with an official statement. It's one of the most anticipated things on my list.

paradox82 said:
Been trying to google an answer myself. Wished Samsung would come out with an official statement. It's one of the most anticipated things on my list.
Click to expand...
Click to collapse
from what i can tell they dont work anywhere yet (mines italian)

Not working for me in Malaysia yet as well.

Same here in Dubai. Firmware JPJJ1. Does anyone see them active using any other firmware?

Zinio isn't even available if you go to their homepage.
It was supposed to be relased this summer.

It appears to be available, as per some reviews. See PC World hands on with the Galaxy Tab.
So the question is, has it been pulled back due to some reason... or if it is to be made available in only select markets?
Either way, it's quite unfortunate, as Zinio was one of the features I was looking forward to in the Galaxy Tab.

German tab in the netherlands not activated either
Sent from my GT-P1000 using XDA App

UK: only Kobo e-books available, out of the 3 options in the reader "hub".

I found the reader hub apps, taken from the Tab, and I loaded them on Desire HD.
Zinio is working, and I was able to download the magazines that I purchased (I have a subscription from the time I owed an iPad). News papers are working too.
Why it is not working on the Tab ?
Zinio launch says Zinio beta - it is the same on Tab ?
I am waiting for my Tab to arrive soon, and I was looking forward to read my magazines from Zinio.
Could you guys upload those files and see if it is working ?

This worked! - showthread.php?t=827566 (I can't post links here yet)...
Perhaps it's the limited catalogue for Android/Tab formatted content that has prompted Samsung to hold back until later...

starhash said:
This worked! - showthread.php?t=827566 (I can't post links here yet)...
Perhaps it's the limited catalogue for Android/Tab formatted content that has prompted Samsung to hold back until later...
Click to expand...
Click to collapse
I've tried, this and it works.
If you install the zinio and press reader only, only the press reader app is available in readers hub.
If you install the readers hub as well, you'll end up with two applications "readers hub" and "ReadingHub", and in the later one. Zinio is available.
Downloading my Zinio subscriptions right now, unfortunately it crashed..
Update: Was able to download an issue now but the internal pdf-viewer doesn't seem to work so it is pretty much back to square one.

Hi there
can u please explain how you managed to fix this? im still not able to use this service :-(
Sent from my GT-P1000 using Tapatalk

It seems to be a problem with Zinio on the new magazines.
When I try to download the new issue on iPhone, the app crashes. The old magazines (October or November) are working fine - download and read.
Same thing happens on Desire HD.

Where can I get the apps? Any idea?

Link to apk:s are in the first post on this page.

I just bought a subscription and downloaded it... it seemed like the magazine would not load but zooming in a tiny bit opened the page?? It seems like the preview won't open/render properly.
I don't understand why this would happen. As I don't have any old subscriptions to try, I can't comment on the ability to load past issues. I wish Zino would fix this.... I can't be that hard to rectify!

According to the Norwegian newspaper Aftenposten, readers hub will be ready «in a week or two».
Sent from my GT-P1000 using XDA App

eskasi said:
I just bought a subscription and downloaded it... it seemed like the magazine would not load but zooming in a tiny bit opened the page?? It seems like the preview won't open/render properly.
I don't understand why this would happen. As I don't have any old subscriptions to try, I can't comment on the ability to load past issues. I wish Zino would fix this.... I can't be that hard to rectify!
Click to expand...
Click to collapse
Same here. On Macworld from August there is no need to zoom - I think they change the format from that time.
Let's hope they will come soon with a proper release app.

RaduOv said:
Same here. On Macworld from August there is no need to zoom - I think they change the format from that time.
Let's hope they will come soon with a proper release app.
Click to expand...
Click to collapse
My problem was with the current issue of Popular Photography.... I really hope they can fix it soon... I love the idea of using Zinio on my Tab

HTC Peep Login Problems

This thread is to track my dealing with HTC and their service department over the current Twitter Tab (HTC Peep) outage. Please don't PM me about it, I'll just make fun of you for not reading and searching.
The current outage has NOTHING AT ALL to do with the Peep security updates published back in February. For information on the past update, please refer to this post.
I am reaching out to everyone who uses this application to bug the crap out of HTC until they fix this problem. Please read this post all the way through so you can contact them with a bit of information. I originally tried to ask about it as simply as possible, but only got an idiotic response. The communication log will be posted in the next post.
Basically, for anyone experiencing issues with Peep, simply read the post I linked to and the following post. This will give you enough information to be able to contact HTC and make some noise. If you do contact them, please use proper grammar and be respectful. Typing like a pissed off high school girl (no offense to pissed off high school girls) will get us no where.
A brief history of Peep outages​Since the very beginning of HTC Sense, most experienced users have known about Peep's security flaws and have either decided to live with it, figuring that it wasn't very important to them, or simply used another client for Twitter. The problem is that Peep was accessing the Twitter API through use of unencrypted HTTP headers which exposed your username and password to anyone who might be eavesdropping on the connection via cellular data IP or WiFi.
Twitter experienced some headlines last summer where several celebrity and high profile accounts were compromised due to lax security features. This caused them to begin shifting their API towards a more secure end. In doing this, they notified the developers of Twitter clients of this shift and to update their applications accordingly. HTC was one of the few who did not update their applications.
Late last year, HTC's Peep application experienced some outages. HTC, instead of repairing the problem, petitioned Twitter about the outage and, after several weeks, the functionality of Peep was restored through an exception made in Twitter's API. This was the easiest solution for HTC, but the worst solution for the customers, since it still left the user's data exposed to risk and was only a temporary solution.
Then, sometime in late January/early February, the members of Tadong blog released their security information to the general public after trying for months to get HTC to fix the security flaw in Peep as outlined above. Subsequent to the release of the information, HTC finally release the security updates for Peep that corrected half of the problem. The initial log in attempt now used OAuth to establish a secure connection over HTTPS on TCP port 443. This fixed the update Twitter rolled out shortly after where some users got the "Forbidden" errors when trying to use the tab. It did not fix the remainder of the session where Peep would request data from Twitter. The rest of the time, Peep requested data over unencrypted HTTP basic headers just as it always had. This, as most of you know, caused problems with the most recent update to Twitter's API.
Twitter rolled out an update again at the end of April that broke the Peep client again. The problem wasn't really Twitter, though. Twitter has now disallowed any new requests to access it through unencrypted channels. This, of course, blocks Peep again. The sad thing now is that this would not be a problem if HTC had simply fixed the problem last year during the first outage or even produced a secure client in the first place.
This brings us to the present. I have contacted HTC with all the information I could gather about this problem. The conversation is listed in the next post. I encourage everyone reading this to learn a bit here and contact HTC via their support page. Any serial number should work as long in the contact form as it matches the correct device. The only Rhodiums to receive the Sense update were the Euro and AT&T ones, as far as I know. Leos ship with it, and I'm sure there were other devices that got Sense updates as well, such as the Photon and Topaz. I'm not up to speed on the models of those devices that got Sense, though. If you contact them, please post in here your conversations. If you need help crafting a proper response to the HTC support techs, please PM me. I will try to assist as best I can.

Communication log
Log between myself and HTC reps, Douglas and Danielle.
Me said:
I have both a Tilt2 and a HD2. Both are using HTC Sense as the primary GUI. On both of them, the Twitter Tab (HTC Peep) no longer works. I put in the right username and password and it always tells me that it is the wrong username or password. I have done this multiple times, and am absolutely certain that I am typing it in correctly.
After searching around for a while, it appears that I am not the only one to have this problem. I also have the HTC Peep security update installed on both of the devices, but it does not work with or without that fix.
Is HTC planning to roll out an update to fix this problem?
Click to expand...
Click to collapse
HTC Douglas said:
understand you are unable to log in to Twitter even with the Peep security update. The link you need to download the update for is different for your two devices.
Use this first link for your Touch Pro 2:
http://www.htc.com/www/SupportViewNews.aspx?dl_id=1085&news_id=874
And this link for your HD2:
http://www.htc.com/www/SupportViewNews.aspx?dl_id=1086&news_id=865
If this does not work you may need to restore your devices to factory settings and re-apply the appropriate hotfix after backing up your information, for example with ActiveSync or the Windows Mobile Device Center to sync your information with Outlook.
Sync software is available at: http://www.microsoft.com/windowsphone/en-us/apps/65-downloads.aspx
You can back up your information using ActiveSync or the Windows Mobile Device Center located at the following URL:
http://www.microsoft.com/windowsphone/en-us/apps/65-downloads.aspx
Essentially, plug your phone into the PC after installing the software and select Activesync as your connection type. Your computer will walk you through backing up your data.
A factory data reset will clear all data from the phone's internal memory and restore the device to manufacturer defaults. Information on your storage card will be kept. To reset the phone press start>settings>(menu>all settings)>system>clear data and confirm.
Click to expand...
Click to collapse
Me said:
I just mentioned that I installed the security update already, and the response I got was to install the security update? What kind of answer is that? Even if the line of thinking was that I perhaps installed the wrong update, how would that even be possible considering the updates require the installation to pass software version checks before installing? I was trying to make this as simple as possible, but considering the response I received, it is apparent I will be unable to do this.
The problem is that the Peep Security Update did not fix the problem all the way. Originally, the Twitter account information was sent via unencrypted http headers upon login which reveal both the username and password to anyone who happens to be eavesdropping on the connection, whether it is by cellular data or wifi. Also, when sending tweets or receiving them, their is a continuous authenticate request sent which exposes the username and password again in the same manner.
The security update is not a 100% fix. After installing the update, it seems that while the initial session is now being sent over https using TCP port 443 (sending against the api.twitter.com domain), during the rest of the session, Peep switches back to HTTP basic. This still leaves the whole session after the initial login vulnerable to hijacking based on the Twitter's session ID through cookies. Because this was not fixed properly in the first place, Twitter has blocked the application from accessing its api. Twitter has increased its security measures and disallowed new authenticate requests from unsecured clients. So any device that is currently authenticated in Peep will not be affected, but once the user logs out of Twitter, does a hard reset, or a ROM upgrade, the Oauth token will be invalidated or removed and will not allow Peep to log back in.
This is the position I am currently in, along with hundreds other users. It affects every user on HTC Sense as it will break the Peep client as soon as they log out. Since these devices are still being sold as brand new, HTC should still be providing support for them, since it is the HTC software that is not functioning as intended. Now, what is HTC prepared to do for every single Sense user? All that needs to be done is to FINALLY secure the Peep client and force it to use HTTPS instead of basic HTTP. The Twitter api will refuse all new auth requests that are unencrypted.
I have attached an eavesdrop of the timeline update request that is sent when the client refreshes. Notice that the username and password are UNENCRYPTED and shown in plain text. One more time I will ask what HTC is prepared to do to solve this problem. Please don't give me a cookie cutter response again. Thank you for your time.
Click to expand...
Click to collapse
The previously mentioned log is attached to this post.
HTC Douglas said:
Thank you for your reply. If you have performed the security update after performing a factory data reset please let me know and I can escalate this issue within HTC.
These are standard troubleshooting steps required to identify an issue and would be required before Escalations can review the case. I appreciate the additional data and log you included, as well.
Also so that I can escalate this issue, please reply with the following information:
Mobile device number:
Alternate contact number
Time zone:
Preferred contact time:
Current ROM version: (Start>Settings>about phone>software information on the HD2)
Click to expand...
Click to collapse
Me said:
As I mentioned, this is problem is persistent through hard resets and ROM updates. Anytime you log out or clear the Peep auth token in any way, it will not allow any further logins due to the (lack of) security of Peep. The only way around this currently is to back up the registry data associated with the Peep client in [HKLM\Software\HTC\HTCAccountManager] as well as the entire folder [\Temp\TwitEng]. If these are imported into a new flash of a ROM update or after a hard reset, the client will function again, as no new initial auth request will be needed. This still does not fix the problem of the client exposing usernames and passwords during EVERY update attempt. Nor does it allow less savvy users to use the Tab after having to hard reset or update the ROM.
The Tilt 2 is running ROM version 2.10.502.4.
The HD2 is running ROM version 3.14.531.1.
You may contact me via e-mail (email removed). I prefer not to be called.
Click to expand...
Click to collapse
HTC Douglas said:
Thank you for your reply. I have escalated the issue for further review. An escalations agent will reach out to you soon. Escalations contacts are performed in the order they are received so it may take a few days for us to review this information and get in touch with you.
Thank you for the detailed information about your analysis.
Click to expand...
Click to collapse
HTC Danielle said:
The previous agent has forwarded your email request to the next level for further review. The escalations team will be getting back with you as soon as they have any information for you. I hope you have a safe holiday weekend.
If you need any further assistance, you are welcome to send another inquiry through the HTC website by going through the Support page (http://www.htc.com/us/support) then tapping ‘send us an email’. You should input all the necessary information requested on the page.
Click to expand...
Click to collapse
Me said:
I will be awaiting further reply. Thank you for your attention to this matter.
Click to expand...
Click to collapse
HTC Travis said:
Thank you for provding us information about the shortcomings of our PEEP security update. I have verified that you are correct and have alerted our corporate office of this fact. They are researching the root cause in terms of the programming and will look into providing an update.
Click to expand...
Click to collapse
Me said:
This is great news. I'm having trouble seeing that I'm the first person to bring this to HTC's attention, though, seeing as this has been an issue for right about a month now. I figured someone else would have reported the problem before me. Please do keep me informed as this progresses. It should be as simple as forcing Peep to use secure HTTPS over TCP port 443 during the session as it does during the login procedure that was updated in February. Currently, it uses OAuth over HTTPS to establish the initial login, but switches back to HTTP basic for the remainder of the session. This allows the username and password to be seen in plain text every time the application requests an update from the Twitter API. Using this method also has another side effect. Twitter updated its security measures to disallow unencrypted requests. This means that Peep is no longer able to establish a connection since it moves from OAuth over HTTPS to HTTP basic during the initial session. If I can be of any other assistance, please let me know. I look forward to updates in this matter.
Click to expand...
Click to collapse
HTC Travis said:
You are not the first person to tell us they are having a problem with Twitter. You are the first person to provide us with this level of information and we thank you for that. Please reply to this email in a few days and someone should be able to give you more information.
Click to expand...
Click to collapse
Me said:
I see. I'm just doing what I can to benefit the dwindling Windows Mobile community. I will check back later this week. Thank you for the updated information.
Click to expand...
Click to collapse

Retain Twitter Tab/Peep functionality through a flash or hard reset
Before you ask, I don't have first hand experience with this. This is based on successful attempts by other members of the community.
This only works if the Twitter Tab/Peep currently still work for you. If it doesn't, then you are out of luck, and this will not work for you.​
To retain the functionality of the Peep client through a flash of a new ROM or a hard reset, you will need to follow the steps listed below.
1. Stop Sense and soft reset to make sure that Sense doesn't continue altering information while you are backing up data.
2. Back up the entire key of "HKLM\Software\HTC\HTCAccountManager." You really only need the Twitter strings, but it's easier to just back up the whole thing.
3. Backup the entire folder of \Temp\TwitEng. This is where the Twitter authentication token is stored.
4. Flash the new ROM or hard reset, whichever you need to do.
5. Once the new ROM is stable and working, stop Sense and soft reset.
6. Restore the registry key and backed up directory.
7. Soft reset and then enable Sense. The Twitter tab should now continue working for you without any trouble.
EDIT: JVH3 made a pair of posts about this HERE and HERE. The second one talks about authenticating another device with the backed up data.

Great initiative ! I'm very curious to hear about HTC's reception of the issue, and see if they will take the initiative to fix it...or imagine a way to justify how not doing it

majorasshole said:
Great initiative ! I'm very curious to hear about HTC's reception of the issue, and see if they will take the initiative to fix it...or imagine a way to justify how not doing it
Click to expand...
Click to collapse
Please use this thread to contact HTC about the problem. Please don't link them to this thread, though. I started this with the intention that others would use the information I have gathered on the issue to contact HTC in an informed manner to get it resolved.
Basically, the more noise is made on this issue, the better chance there will be to have it fixed.

HOLY $ |-| 1 +, it worked!
Ok, so I received official word that Peep is being looked into by HTC. I would still encourage anyone reading this to contact them with the information I have provided here. The squeaky wheel gets the grease, as they say.
HTC Travis said:
Thank you for provding us information about the shortcomings of our PEEP security update. I have verified that you are correct and have alerted our corporate office of this fact. They are researching the root cause in terms of the programming and will look into providing an update.
Click to expand...
Click to collapse
Me said:
This is great news. I'm having trouble seeing that I'm the first person to bring this to HTC's attention, though, seeing as this has been an issue for right about a month now. I figured someone else would have reported the problem before me. Please do keep me informed as this progresses. It should be as simple as forcing Peep to use secure HTTPS over TCP port 443 during the session as it does during the login procedure that was updated in February. Currently, it uses OAuth over HTTPS to establish the initial login, but switches back to HTTP basic for the remainder of the session. This allows the username and password to be seen in plain text every time the application requests an update from the Twitter API. Using this method also has another side effect. Twitter updated its security measures to disallow unencrypted requests. This means that Peep is no longer able to establish a connection since it moves from OAuth over HTTPS to HTTP basic during the initial session. If I can be of any other assistance, please let me know. I look forward to updates in this matter.
Click to expand...
Click to collapse
HTC Travis said:
You are not the first person to tell us they are having a problem with Twitter. You are the first person to provide us with this level of information and we thank you for that. Please reply to this email in a few days and someone should be able to give you more information.
Click to expand...
Click to collapse
Me said:
I see. I'm just doing what I can to benefit the dwindling Windows Mobile community. I will check back later this week. Thank you for the updated information.
Click to expand...
Click to collapse

cajunflavoredbob said:
Before you ask, I don't have first hand experience with this. This is based on successful attempts by other members of the community.
This only works if the Twitter Tab/Peep currently still work for you. If it doesn't, then you are out of luck, and this will not work for you.​
To retain the functionality of the Peep client through a flash of a new ROM or a hard reset, you will need to follow the steps listed below.
1. Stop Sense and soft reset to make sure that Sense doesn't continue altering information while you are backing up data.
2. Back up the entire key of "HKLM\Software\HTC\HTCAccountManager." You really only need the Twitter strings, but it's easier to just back up the whole thing.
3. Backup the entire folder of \Temp\TwitEng. This is where the Twitter authentication token is stored.
4. Flash the new ROM or hard reset, whichever you need to do.
5. Once the new ROM is stable and working, stop Sense and soft reset.
6. Restore the registry key and backed up directory.
7. Soft reset and then enable Sense. The Twitter tab should now continue working for you without any trouble.
Click to expand...
Click to collapse
Looks alot like what I posted here: http://forum.xda-developers.com/showpost.php?p=13790743&postcount=34951
Your thread is a better place for it though.
I also posted this: http://forum.xda-developers.com/showpost.php?p=13520319&postcount=34836
Which is helpful if you have another device that still is authenticated with the Twitter tab and transfering the info to another device.
Real glad you got things going with HTC to finally work on this.

JVH3 said:
Looks alot like what I posted here: http://forum.xda-developers.com/showpost.php?p=13790743&postcount=34951
Your thread is a better place for it though.
I also posted this: http://forum.xda-developers.com/showpost.php?p=13520319&postcount=34836
Which is helpful if you have another device that still is authenticated with the Twitter tab and transfering the info to another device.
Real glad you got things going with HTC to finally work on this.
Click to expand...
Click to collapse
Well, I already knew the key and file that needed to back up, but I forgot where I saw the bit about turning on and off Sense. Thanks. I'll add some credit for you.
Yea, there's a bit more that I can't post due to personal or sensitive information, but it's looking good so far. I'll keep updating this as more info rolls in. I'm hoping that other people contact them about it as well.

Very good afford cajunflavoredbob .
Lets hope Peep developer team in HTC are getting ready with new client
Thanks.

prabhat said:
Very good afford cajunflavoredbob .
Lets hope Peep developer team in HTC are getting ready with new client
Thanks.
Click to expand...
Click to collapse
I have a bit more to update tonight. They have sent the information onward and are working on a fix right now. No ETA was given, however.

Ive just suffered this problem today - logged out of peep and now i cant get back in again. As i didnt know about this issue, obviously dont have any backup! Thanks for pursuing this!

This has been my ongoing encounter with HTC Support for the Touch HD / Blackstone
Simon Lee Reply
Ok, could you keep me notifed if the touch HD will get the update or not ?
Thanks 2011/06/08 18:04:45
Bjorn [EU team] Close Pending I'm not saying it won't happen, I'm just saying that at this point I can not guarantee taht the touch HD will get such an update as it is an older device. I'm not saying it won't happen, I'm just saying that at this point I can not guarantee taht the touch HD will get such an update as it is an older device. 2011/06/08 16:15:10
--
Simon Lee Reply How come thou ? If theres no fix then that might meen i will have to buy a new phone, and am quite happy with the Touch HD ?
--
2011/06/08 10:57:55 Bjorn
[EU team] Close Pending I can not guarantee That a fix will be released for the Touch HD when te issue is resolved. I can not guarantee That a fix will be released for the Touch HD when te issue is resolved.
--
2011/06/08 07:59:10 Simon Lee Reply
Yeah, i realise its an Unoffical ROM, but thats beside the point, When tyou fix the HTC peep, will the Touch HD get a Upgrade for 6.1 with the HTC Peep fix?
--
2011/06/07 17:15:23 Bjorn [EU team]
Close Pending As your device is runnig an unaproved ROM we are unable to support it and can not guarantee that any applications will work properly. We have how ever had reports regarding this and are looking in to it on our approved ROM's, As your device is runnig an unaproved ROM we are unable to support it and can not guarantee that any applications will work properly. We have how ever had reports regarding this and are looking in to it on our approved ROM's,
--
2011/06/07 16:14:50

spikeyl said:
Ive just suffered this problem today - logged out of peep and now i cant get back in again. As i didnt know about this issue, obviously dont have any backup! Thanks for pursuing this!
Click to expand...
Click to collapse
Theres some kind of solution floating around here somewere
- Edit -
you could try this: http://forum.xda-developers.com/showthread.php?t=708770

Thanks - i found this earlier and tried all these but none of them work! Having read through the thread above I can see why though - it is related to the security authentication issue, so currently no fix.

spikeyl said:
Thanks - i found this earlier and tried all these but none of them work! Having read through the thread above I can see why though - it is related to the security authentication issue, so currently no fix.
Click to expand...
Click to collapse
Yeah, and HTC are planning on bring out a fix, but wont say which devices, will get the supported fix,

Simon_WM said:
Yeah, and HTC are planning on bring out a fix, but wont say which devices, will get the supported fix,
Click to expand...
Click to collapse
The only devices that will get the fix are the ones that have official Sense 2.5 ROMs. There are only four of them.
1. Leo
2. Rhodium
3. Photon
4. Topaz
My recent communications with HTC contain personal information regarding the fix. It is being worked on, but there is no current ETA that they have provided. I am keeping in touch with them and working with HTC to resolve the problem. I'll update this thread as more information is provided to me.
EDIT: Please don't post here about possible fixes. There is no fix for this error. The problem is with Peep and has nothing to do with Twitter. Logging in and out of Twitter on the desktop will have no bearing on the Peep application. No applications are allowed to access Twitter's API though unsecured connections, thus Peep is excluded.

My Twitter also stopped working sometime last week, but I don't ever remember logging out. However when I scrolled past the peep tab on my HD2 this morning it read "no tweets" instead of the click to login screen (or whatever it said). I clicked the screen and now have tweets going back to sometime yesterday. Is this any way connected?

jools5431 said:
My Twitter also stopped working sometime last week, but I don't ever remember logging out. However when I scrolled past the peep tab on my HD2 this morning it read "no tweets" instead of the click to login screen (or whatever it said). I clicked the screen and now have tweets going back to sometime yesterday. Is this any way connected?
Click to expand...
Click to collapse
This is unrelated if you did not log out, as far as we know. Twitter isn't yet blocking anyone from their API who already has a connection. They are only refusing new attempts.

HTC knows the problem, is working on it, but still no ETA
Just to add my story:
Originally Posted by Me
After flashing a new row to my HTC HD Mini, HTC Peep cannot sync with Twitter anymore.
I have flashed this rom: http://www.htc.com/europe/SupportDownload.aspx?p_id=314&cat=2&dl_id=980
And updated it with this update: http://www.htc.com/europe/SupportDownload.aspx?p_id=314&cat=0&dl_id=1085
When I enter my account and password, HTC Peep tells me: "You entered an incorrect username or password".
The account and password are OK, since I can use them via the web and other Twitter-applications.
I tried revoking HTC Peep as a Twitter-application and then re-adding HTC Peep.
But the message is still "You entered an incorrect username or password".
From an old backup I have retrieved registry settings at HKLM\Software\HTC\HTCAccountManager and the directory at \Temp\TwitEng.
After putting these settings back into the new rom I get a message: "The account was forbidden to access the twitter server!"
This is logically because I revoked HTC Peep as a Twitter-application at the Twitter website.
So, the HTC Peep client does not recreate the connection to Twitter.
Please provide a solution or update so that the HTC Peep client will work again.
Click to expand...
Click to collapse
Originally Posted by HTC
Thank you for contacting HTC Support.
The problems you are experiencing is because of a change in the Twitter API's that Peep has not yet adapted to.
Unfortunately I have no ETA for when this might be.
Until then I can only recommend using another Twitter client.
I hope this helps.
Click to expand...
Click to collapse
Originally Posted by Me
Thank you for the answer.
I am already using another Twitter client, but miss Peep...
I sincerely hope that Peep will be adapted soon.
Is this problem (already) sent to the development department?
Click to expand...
Click to collapse
Originally Posted by HTC Thank you for your email.
Yes, HTC is working on solving this issue as soon as possible.
If you have any further queries please don't hesitate to contact HTC again.
Have a nice weekend.
Click to expand...
Click to collapse
So, HTC knows the problem, is working on it. But still no ETA.....

wensing said:
Just to add my story:
So, HTC knows the problem, is working on it. But still no ETA.....
Click to expand...
Click to collapse
It's good to hear someone else's experience. I will ry to get back in touch with the HTC rep I've been communicating with this evening or tomorrow to see if there are any updates.

stock email client crashing

Is anyone using or having issues with the stock email application? I am using it for exchange and i cannot download attachments, reply, forward, or compose emails. I am stock and never installed the update.
After trying to do any of the above, the program locks up then a popup comes up that says "unfortunately, Email has stopped"
any ideas?

greenzkool said:
Is anyone using or having issues with the stock email application? I am using it for exchange and i cannot download attachments, reply, forward, or compose emails. I am stock and never installed the update.
After trying to do any of the above, the program locks up then a popup comes up that says "unfortunately, Email has stopped"
any ideas?
Click to expand...
Click to collapse
Same here. Works for a few hours after full wipe, then suddenly stops. I am also not able to send any mails.

My phone I never stock e-mail application, so I work very convenient that I do not like to use his

greenzkool said:
Is anyone using or having issues with the stock email application? I am using it for exchange and i cannot download attachments, reply, forward, or compose emails. I am stock and never installed the update.
After trying to do any of the above, the program locks up then a popup comes up that says "unfortunately, Email has stopped"
any ideas?
Click to expand...
Click to collapse
I'm using the stock client with Exchange Server 2010 and don't have any issues. During setup did you answer "yes" to all the security and permissions pop-ups? It might be something on the server side. Does your IT department require a client certificate?

Hi,
I am not the creator of this thread, but I am facing the same issues with an Exchange 2007. I dont believe it is server-related. Everything is working fine on my GTab 8.9, my Galaxy Nexus and my Note (the phone). Only the Note 10.1 is having issues. It is also working fine four a few hours after a tull wipe and stops working later. Tried this three times, always the same result. Also noted down all the steps I was doing before it stopped b7t could not find anything. Last time it just stopped working after a longer time of inactivity.
It is always the same thing with this Samsung stuff... Changing anything with there TouchWiz, leaving a perfectly working system (stock Android) unstable and buggy. Had those exchange issues on nearly every new Samsung device, it always took two or three firmware updates after it was fully working.
Update: To give you some more information. Everything is syncing fine... mails, tasks, appointments, contacts. I am also perfectly able to create and edit contacts, appointments and tasks. But whenever the mail application is trying to open the editor window (so on new, reply and forward) the whole mail app simply quits.

ranzassel said:
Hi,
I am not the creator of this thread, but I am facing the same issues with an Exchange 2007. I dont believe it is server-related. Everything is working fine on my GTab 8.9, my Galaxy Nexus and my Note (the phone). Only the Note 10.1 is having issues. It is also working fine four a few hours after a tull wipe and stops working later. Tried this three times, always the same result. Also noted down all the steps I was doing before it stopped b7t could not find anything. Last time it just stopped working after a longer time of inactivity.
It is always the same thing with this Samsung stuff... Changing anything with there TouchWiz, leaving a perfectly working system (stock Android) unstable and buggy. Had those exchange issues on nearly every new Samsung device, it always took two or three firmware updates after it was fully working.
Update: To give you some more information. Everything is syncing fine... mails, tasks, appointments, contacts. I am also perfectly able to create and edit contacts, appointments and tasks. But whenever the mail application is trying to open the editor window (so on new, reply and forward) the whole mail app simply quits.
Click to expand...
Click to collapse
I agree with this, also i cant open attachments. I set up my gmail account on the stock email program (i use gmail app) just to see if it was exchange or the program in general. It did the same thing with gmail. It is the program that is crashing.

Not trying to throw salt in the wounds but i also have 4 emails running thru the stock email- including my exchange which works perfect- everything syncs and no issues like you are exeriencing. I also had this same setup without issues on the 16g GTnote before i just exchanged it for my current 32g. no issues on either.
Let us know if you figure it out- good luck.

tonyz3 said:
Not trying to throw salt in the wounds but i also have 4 emails running thru the stock email- including my exchange which works perfect- everything syncs and no issues like you are exeriencing. I also had this same setup without issues on the 16g GTnote before i just exchanged it for my current 32g. no issues on either.
Let us know if you figure it out- good luck.
Click to expand...
Click to collapse
question to all with working or not working email. did you install the update or not? I do not have the update installed and my email isnt working. I just deleted everything, wiped email data and reset it and still isnt leting me send emails or open attachments

I found the solution! It's working for me and it is reproducible: Disable "force 2d gpu rendering" in the developers settings (sorry, don't know how it is named inthe english version, I am German ).

I dont think it was the update- because on my 16g i had the update and email worked, On the new 32g no update and it works.
Also, i can confirm as posted in the other - i do not have the force gpu 2d or whatever it is -checked... so maybe thats the deal.

tonyz3 said:
I dont think it was the update- because on my 16g i had the update and email worked, On the new 32g no update and it works.
Also, i can confirm as posted in the other - i do not have the force gpu 2d or whatever it is -checked... so maybe thats the deal.
Click to expand...
Click to collapse
Hey!!!!i took gpu2d off and it started working! Thanks!

ranzassel said:
I found the solution! It's working for me and it is reproducible: Disable "force 2d gpu rendering" in the developers settings (sorry, don't know how it is named inthe english version, I am German ).
Click to expand...
Click to collapse
Thanks Ranz!

ranzassel said:
I found the solution! It's working for me and it is reproducible: Disable "force 2d gpu rendering" in the developers settings (sorry, don't know how it is named inthe english version, I am German ).
Click to expand...
Click to collapse
Why would you enable "force 2d gnu rendering"?

Thanks
ranzassel said:
I found the solution! It's working for me and it is reproducible: Disable "force 2d gpu rendering" in the developers settings (sorry, don't know how it is named inthe english version, I am German ).
Click to expand...
Click to collapse
Faced same problem. Disabling force gpu rendering worked for me.

had similer problems you could try this http://forum.xda-developers.com/showthread.php?t=1842226 :angel::silly::highfive::laugh:

ranzassel said:
I found the solution! It's working for me and it is reproducible: Disable "force 2d gpu rendering" in the developers settings (sorry, don't know how it is named inthe english version, I am German ).
Click to expand...
Click to collapse
Thank you so much. It works. Good fix. :good:

Problem remains...
Hi! I'm having the same problem... However, I already the force gpu rendering disabled and it crashes anyway. I turned it on and it's the same. Already cleaned all data, deactivated and activated, etc and nothing. It always crashes... Any idea?
Ah! The same happened with YouTube after installing the update...
And it's my second tablet, the first one did the same and I was hoping it could be some hardware malfunction... I guess not...
Thanks!

Ricarditu said:
Hi! I'm having the same problem... However, I already the force gpu rendering disabled and it crashes anyway. I turned it on and it's the same. Already cleaned all data, deactivated and activated, etc and nothing. It always crashes... Any idea?
Ah! The same happened with YouTube after installing the update...
And it's my second tablet, the first one did the same and I was hoping it could be some hardware malfunction... I guess not...
Thanks!
Click to expand...
Click to collapse
I think I got it!
I did a factory format and reboot and tried the email client. It worked all ok, no crash until here. When I installed Flash from Adobe, the latest version, it started working oddly... Crashed and even the touch was not accurate as before.
So I rebooted it once again and didn't install Flash anymore. Until now it's ok, maybe there is some conflict... The truth is that Samsung and Adobe don't include N8000 in their list of devices to run flash. 4.0.X up won't anymore.
Thanks!

ranzassel said:
I found the solution! It's working for me and it is reproducible: Disable "force 2d gpu rendering" in the developers settings (sorry, don't know how it is named inthe english version, I am German ).
Click to expand...
Click to collapse
Thank you! This solved my issue!

thanks
greenzkool said:
Thanks Ranz!
Click to expand...
Click to collapse
dude..that's it...i never would have thought that this is the problem...mega thanks...you will be astonished to now that all of this was due to the animation effect in the stock app...that is my third samsung tablet always had problems with these things...

Desperate gig worker seeking help with terrible app

Hey everyone,
I know this is probably a long shot but I'm not sure where else to go for advice.
I have the KB2007, up to date. I do gig work and doordash is one of my major sources of income. The Dasher app does not work on this phone. When I try to login, it just redirects me back to the login page without any error message.
Last week, I uninstalled the latest version of the app and grabbed an old apk. This actually ended up working and I was even able to update the app to the latest version and continue as usual. But last Sunday it suddenly stopped working. And the trick of using an old apk no longer works.
I've contacted doordash technical support but they basically didn't help and closed the case. I will keep pestering them since it seems like a bug on development side but I was wondering if anyone here has any idea what's going on and any suggestions for me to fix it.
All the usual stuff like clear cache and data doesn't work.
Thank you.

tretinh said:
Hey everyone,
I know this is probably a long shot but I'm not sure where else to go for advice.
I have the KB2007, up to date. I do gig work and doordash is one of my major sources of income. The Dasher app does not work on this phone. When I try to login, it just redirects me back to the login page without any error message.
Last week, I uninstalled the latest version of the app and grabbed an old apk. This actually ended up working and I was even able to update the app to the latest version and continue as usual. But last Sunday it suddenly stopped working. And the trick of using an old apk no longer works.
I've contacted doordash technical support but they basically didn't help and closed the case. I will keep pestering them since it seems like a bug on development side but I was wondering if anyone here has any idea what's going on and any suggestions for me to fix it.
All the usual stuff like clear cache and data doesn't work.
Thank you.
Click to expand...
Click to collapse
Seems like an incompability of OOS and this app.
There are plenty of versions there. I hope, you'll find one that works.