[chaley]

Originally Posted by DiapDealer

Just a heads-up on the "empty shelf syndrome":
I just downloaded the official 3.0.4 update from Google Play and the syndrome rears its head under very reproduceable circumstances on my Kindle Fire HD 7".

First question: how are you running CC on a kindle fire? It requires access to the google play license service, which AFIK doesn't exist on the fire without rooting. It would be so nice to be wrong ...

Unfortunately we don't have a fire of any kind and we don't know anyone with one, so this will be hard to trace.

If I open the app (grid or list) with the device oriented landscape, I get the empty shelf (and I see the >>> drawer >>> indicator even though I have it disabled in the settings). When I turn the device back to portrait, everything goes back to normal. Going back to landscape after that works fine, too. Only the initial opening in landscape seems trigger it.

To be clear, because there might be an important clue here. Do these steps reproduce the problem?

1) You have CC open in list mode in either portrait or landscape. All is well.
2) You shut down CC by "back"ing out until it quits.
3) You change orientation to landscape. Things settle.
4) You start CC. You see the wood background with no books.

Right?

The interesting thing about this scenario is the change from list to grid. That should not happen, and if it does then I might be able to trace paths in the startup sequence that would allow it.

EDIT:Having looked at the code, I can't see any way for the above to happen. The very first thing CC does on startup is to set up the correct view (grid or list). As such, step 4 is probably "You start CC. You see the same background you were looking at before, but with no books". Is this right?

Still love the new look! The bug doesn't really "bug" me at all, but I thought someone might like to know (unless the Fire's flavor of Android isn't intended to be supported at all).

Thanks!

And yes, we do want to know.

We don't intend or not intend to support the Fire, but defacto is has not been supported. Our problem has always been Amazon, who really don't want CC on the fire. It that restriction has become relatively easy to avoid, then we will need to get access to one for testing.