[Desire General] justanewuser:
Might not be flickr

Hi, I am not a developer, just a new fan of the Desire. I apologise for the length of my first post here, but I hope this will shed some further light on this problem.

I have had my Desire for a few weeks, and since day one I have had my google (with calendar) and flickr accounts registered on the phone, and it has been working just fine (battery-wise). Then yesterday I did 4 things:

1) Accepted the update to googlemaps I was offered, and installed it.

2) Replaced the supplied sd card with a Samsung 8gb class 6 to see if it resolved the one problem I have had on the phone, namely the intermittent loss of access to the card, as described exactly here (this is a url but as a new unverified user I am not allowed to post it as such yet)

androidforums.com/htc-desire/61925-cant-take-pictures-due-permission-errror-sd-card.html

3) Having not bothered up to now, copied a load of music on to the new card (rips from windows media player, so including album art)

4) Having never used twitter before, decided that as my phone supported it, I would register and give it a go, using it via Peep.

Then last night I noticed that my battery was dying REALLY fast, and after a few hours trying to track down which of these changes might be responsible (and pointing the finger at the sd card for quite a while) I eventually figured out using juiceplotter and the battery app that the phone was not sleeping when I turned it off. I then started looking at Peep, and soon found that even though it wasn't running after a boot, if I started it and then killed it, the phone started sleeping properly. Even if I then started Peep again, the phone continued to sleep properly. So killing it once seems to fix the problem until a reboot. So I then tried deleting my twitter account from the phone, but that did not cure the problem, the phone stayed awake after a boot. But starting then killing Peep without signing in still "fixed" it. Then I found that starting and killing Friendstream would also fix it. I also found that having both wifi and 3g OFF when I turned the phone off so that they were off when it rebooted also meant that the phone went to sleep. But when I then turned wifi on, it would then fail to sleep, until I started/killed something. So it is definitely network/background-update related.

After more searching, I found this thread. I have deleted my flickr account now, and sure enough, this does seem to have permanently fixed the problem for me (I currently have neither flickr or twitter accounts on the phone, I haven't tried putting them back yet).

But, the fact that I had flickr running for weeks until last night with no problem, and the fact that starting and then killing one of these other "background update" apps, such as Peep or Friendstream, also seems to fix the problem (until the next reboot that is) would indicate to me that the problem is not quite so simple as "it's flickr, get rid of it", it seems to be a much more complex combination of apps all together.

Hope this helps someone else figure out what is really going on here. I will be experimenting today with putting accounts back and messing about with the sd card and seeing what happens. Some silly theories bouncing around in my brain now include:

Is flickr trying to do something with the sudden huge number of JPGs (album art) on the card?

Is the new large number of files on the card slowing something else down that never completes?

Did googlemaps update do something?

Is there something strange about the new sd card?

EDIT:

Put flickr account back, problem came back.

Booted without sd card in, problem still there.

Removed flickr account again, problem cured.

Put twitter account back, problem does not return.

This is crap. Up until yesterday I could use flickr. Now I can't unless I bugger about killing something when I reboot.

My theory is that setting up twitter acount for the first time has configured something else that it needed which has caused this problem with flickr. Getting rid of twitter account does not "unconfigure" it.

I am really not keen on doing a reset, but might have to try it.

Does all this help anyone figure out what is happening?