Continuous Crashing

[jmiller42]

Our team owns 2 kindle fires that run iscore. Both devices have been crashing multiple times per game. One of my scorekeepers have noticed that, right before a crash is about to occur, there are no names shown by the fielding positions on the field. It just reads first base, second base etc. Any move he makes after that, the program issues a force close and he needs to restart the program. This has been happening multiple times an inning. I haven't confirmed with our other scorekeeper if the same scenario happens on the other device, but he has been having a lot of force close problems as well.

Both devices were purchased for the sole use of running iscore and they are not loaded down with apps and other data. I have done a hard reset on both devices, as well as the data maintenance tuneup, to no avail. Please help, as this is a major distraction in trying to keep score. I love the product otherwise.

[FTMSupport]

We use Kindle Fire regularly to score games, and have not seen this issue. If you can give us steps to reproduce the crash here, we can debug what is going on. But if it is just random crashes as opposed to a certain set of steps, that is usually more indicative of memory issues on the device.

[akalostangel]

I, too, use iScore with Kindle Fire. At least twice per game, I get the force close message. Usually about the 4th inning every time. Other than that there is no pattern to the force close. Sometimes it happens when I mark a ball or strike, sometimes it happens when I mark a hit, sometimes when I make a change to the lineup (lineup change, enter batter number that I didn't have before they hit, substitution, etc.) There's no one thing that appears to cause it.

I restart the app and it usually does it again within a minute. I restart the app again and it may run fine the rest of the game, but it may do it again later in the game.

I have scored 7 games with the iScore/Kindle combination and it has done it with every game. Luckily, I don't lose anything I entered prior to shut down and when it restarts I am at the same place I was when it forced close.

I'm not convinced it's a memory issue. My Kindle is new and I only about 5 apps and 10 books on it. I always shut down any running apps completely, after I've hit the back button to get out of them. I don't have internet access where we play most games, and I usually have the WiFi set to "off" so it's not that I'm using memory that way, either.

[FTMSupport]

We actually did find an issue with "rotating" the device. If you are quickly rotating from portrait to landscape and back (can happen if you just turn in your chair for example), it can cause a crash. Version 3.49 fixes this issue. Version 3.49 is already available on Google Play, but Amazon has an approval process that takes longer for apps to become available there. Watch for v3.49 in a future update and it will address the force close issues we have been able to reproduce.

[akalostangel]

Thanks. I have a rooted Kindle Fire and got my app from Google Apps. I'll be sure to update it and let you know if that fixes the issue.

It could well be that, because in my excitement over the game, I probably did not hold my kindle very steady at times.