Quote:
Originally Posted by Purple Lady
I just had this same problem again. One thing this time is that I noticed that if I have an external IP address for the content server it won't connect to the content server if I am at home with wifi on - is this new? If I turn wifi off it connects fine. I'll send the debug log again.
|
First, are you editing the log, or is what you are sending me all there is?
From what I can see, the root cause of what is happening is that a connection to some IP address is timing out, coupled with (I think) the connection being cancelled while waiting for this timeout. That timeout is several seconds (5, I think). Android requires that network connections be done in a background thread. We chose what is called an AsyncTask, which is easy to use but carries the baggage that there can be only one of them running at once. Painting covers and text in the booklist is also done by AsyncTasks. Thus, until that timeout happens, no covers will paint. Why they *never* paint is a mystery. I would expect that if you went to settings and back, or if you scrolled some distance up or down then they would start painting again.
As for why that timeout on connect is occurring, I can't say. There isn't enough of the log to know what IP address is being used, whether it is a DNS name that is being mistranslated, or whether some other CC option is getting in the way. My suspicion is that the connection wants to loop back through the external IP address of your router to some machine on your local net, and that your router doesn't support loop backs (most do not). If this is the case then you can use the second address section of CC's content server connection box to specify the internal IP address. Or invert them, specifying the internal address in the first section, which might avoid the timeout.