http://iscoresports.com/

I used iSBb to score games on my Kindle Fire for the first time this weekend (I've used it on an iPod touch for 3 year, just upgraded to a larger screen Fire).

I experienced a display problem which occurs frequently. I used the Fire in landscape mode with the orientation locked (don't know if the issue happens in portrait, didn't try that). Between half-innings I put the fire to sleep by pressing the power button so that I could save battery. When the next half-inning started I woke it back up. Often, but not every time, when it came out of sleep the field graphic was incorrect with the base positions moved down such that the outfielders were at the edge of the infield dirt, shortstop was on third base, second baseman was on first base and the pitcher was where the catcher should be. The catcher was not visible.

I finally figured out that I could fix the problem by going back into sleep mode and then coming out but sometimes it took 2-3 tries to get that to work.

I also experienced another problem which I suspect is related. There was a situation where a player hit a single and then reached second on an error by the right fielder. When I was prompted to select the fielder which caused the error the fielders were shifted up this time such that only the very bottom of the catcher icon was visible at the top of the screen, no other fielders were visible. I was forced to assign the error to the catcher before I could progress.

Hopefully these errors can be easily reproduced by FTM. I was able to recreate the problem this morning by creating a test game and once I started the game with the PLAY button I put the Fire to sleep. When I woke it up the field was shifted.

-phil

We will check into these issues... thank you.

FTMSupport wrote:We will check into these issues... thank you.

FTM,
Has any progress been made on this issue? I ran in to the problems again this past weekend. I wonder if any other Fire owners have this issue, or is it just me?

Thanks,
-phil

We have not been able to reproduce this consistently. If you have exact steps from the time of going into the Play screen to cause this to happen, that would help us be able to resolve the issue.

FTMSupport wrote:We have not been able to reproduce this consistently. If you have exact steps from the time of going into the Play screen to cause this to happen, that would help us be able to resolve the issue.

FTM,

I have used the procedure below several times to create two test teams and a test game to display the failure. Please note that the corruption doesn't happen every time that the Fire comes out of sleep. Sometimes I have to repeat the sleep/wake cycle multiple times to see the failure. I have a screen grab from my Fire showing the failure but I can't seem to attach that to this post.

1) open iscore baseball
2) select Team Manager
3) at the Team Manager screen select Add
4) at the Team Info screen enter Team Name “Team1”
5) select Roster
6) at the Team Roster screen select Quick Roster
7) at the Quick Roster screen enter Number of Players “9”
8) select Create
9) at the Team Roster screen select Done
10) at the Team Info screen select Save
11) at the Team Manager screen select Add
12) at the Team Info screen enter Team Name “Team2”
13) select Roster
14) at the Team Roster screen select Quick Roster
15) at the Quick Roster screen enter Number of Players “9”
16) select Create
17) at the Team Roster screen select Done
18) at the Team Info screen select Save
19) at the Team Manager screen select the back arrow
20) select Game Manger
21) at the Game Manger screen select Add
22) at the New Game screen select Visitor Team of Team1 (from the Team List screen)
23) select Home Team of Team2 (from the Team List screen)
24) select Save
25) at the Game Manger screen select the new game you just created
26) at the Game Info screen select Play
27) at the Team2 screen select Done
28) at the scoring screen select Play!
29) press the Fire power/sleep button to put the Fire to sleep
30) press the Fire power/sleep button to wake the Fire up
31) drag finger across screen to open the Fire
32) repeat steps 29 – 31 until field display is corrupted

We will look into this. Thank you.

FTMSupport wrote:We will look into this. Thank you.

FTM,

Have you made any progress with this issue? Have you been able to recreate the display problem using the procedure I provided?

Regards,
-phil

The problem is Step 32:

32) repeat steps 29 – 31 until field display is corrupted


The intermittent aspect of the issue is what makes it hard to figure out. If it happened every time, it is an easy fix. But having it not happen every time makes it more of a challenge. We do not yet have a fix for this.

FTMSupport wrote:The intermittent aspect of the issue is what makes it hard to figure out. If it happened every time, it is an easy fix. But having it not happen every time makes it more of a challenge. We do not yet have a fix for this.

So it sounds like you are able to recreate the problem (at least intermittently), is that correct? If that's the case at least I know it's not an issue specific to my Fire and there is hope that it can be fixed.

Thanks,
-phil

Yes, we can also get it intermittently. We are working on a fix but it is much harder when things are not consistent.