wzhwawhxmmj / frozenbubbleplus

Automatically exported from code.google.com/p/frozenbubbleplus
0 stars 0 forks source link

Issue with Kyocera Hydro (Android 4.0) - current level is reset/lost #54

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Multiple people have reported that they have had the current level index reset 
on them.

This is either due to an issue with bundle saving/restoring (when 
onSaveInstanceState() is called, which ultimately calls 
LevelManager.saveState()), or is as a result of an issue saving the current 
level index to the game preferences in FrozenBubble.pause(), or restoring the 
current level index from the game preferences.

Original issue reported on code.google.com by forter...@gmail.com on 28 Oct 2013 at 6:35

GoogleCodeExporter commented 8 years ago
From Robert Leslie:

Eric,

Ok, here's the rundown on 3 complete 1 to 100 games, but don't forget this is 
the old one..see my previous gmail..because your new trial version wouldn't 
stick in my phone. This is distilled from 2 pages of notes:

Stopping w/flag "Unfortunately..." :

From level 1, made it to 29, at "Winner" board, touched return, got flag. For 
the first time I touched "report", and got   :-) "Unfortunately Google Play 
Store has stopped." LMFAO! So..touched the GPS icon, and got same flag. Touched 
the FB icon in recent apps (RAI) and it came up on 29! at start of game as if 
paused. Played, 30 came up ok. I played it, and at the end ad came up..but 
while still at the start I hit recent apps, the GPSI again, still stuck. So I 
offed it. Back to the game..and this is google for you, take any cue, even bad 
ones..suddenly a pulldown, "8 GPS updates" await my pleasure. I updated U-Tube 
(probably yours  :-) the only one, but FB is on the "Up to date" list. At this 
point I got tired and left FB with the ad up using return and home, and offed 
the RAI.

Next, FB came up fine using the bookmark icon (BMI), no ad there, and played 
through from 30 fine, to (I Think) 67. I was going very fast, through 
everything, these 37 levels in just a few minutes..touched Winner and it 
crashed.   This is always at a change point! Never IN a level 
playing..sometimes leaving, like then, a few, but most often coming in or out 
of the game at the menu, and once in a while at the first page. ...ok, so at 
the flag I left the RAI, used BMI, & it came up fine at the first page & 
self-activated to menu, But, I'm on level 34 now.

So..went fine again thru 40, where I offed the ad, and on to 54, where it 
crashed at the scoreboard when touched. I used return twice, offed the RAI, 
used DMI & all went well to 73. There (different & fairly common prob) the 
"Next" button was sticky & took 5-6 hits to activate. At 75 same, but only 3 
taps, and 89 same. The "stickyness" varies from 1 or 2, to 6 or 8 taps needed, 
and in CPU there are times, Most, when it refuses to change, period! No matter 
What you do. Yet there are times it functions off & on to mostly. Worse, I 
think, with rotate on. I notice also this seems to happen more toward the end 
of levels, and toward the higher levels. The rest thru 100 then went fine, and 
that's the first run through.

Next run-CPU:  Turned on rotate, and you were right about the difference, but 
not quite what I expected. On horiz. the balls are so small using your finger 
to aim is hopelessly wide. Not for me I'm afraid. Worse, the sticky Next prob 
is severe here. It changes sometimes, but seldom on first touch. It was better, 
I think, with rotate off, if that means anything. Mostly it's Very sticky, many 
times refusing to change at all..I've tried soft, hard, fast, slow, press, 
Swype, etc., and when it's stuck it's stuck! It also seemed a little better set 
on easy than moderate (haven't tried hard). This seems to fit my thinking that 
this prob manifests itself more toward game ends and higher levels, if faster 
has anything to do with it.

Then on level 2; when the win/lose board was up, touched, it didn't go to the 
next level or repeat, there was a word (this is on vertical) half in the void.. 
Turned horiz. then it read, so tiny even near sighted me could hardly read it, 
"High score for moderate." Thing was..with it off the side like that, virtually 
all the way out of the field, there was no touching it; no way to advance or go 
back, and return bought me back to the main menu. This was also one of the 
times Next refused to activate at all. The too small thing seems to affect this 
as well, as horiz Next works 2 or 3 times less often than in vert, where sticky 
on every ? Tenth to fifteenth ball is the norm. This held thru 13, 14 levels. 
Then I turned rotate back off and ran thru another 10 or 15 levels with the 
above results.

3rd run thru had the worst confused levels prob yet. Level 1 thru 27 played out 
fine as usual. At end of 27 I used return twice to exit, offed the RAI, used 
the BMI, and "Unfortunately." Offed everything again and it started fine. End 
of 28 I left from winner board with a double return, offed the RAI, and the 
game started fine, but still on 28. So... same routine again, game didn't 
start. I checked just to be thorough, and the RAI was back..this even tho the 
game hadn't started, flag still up. Clue? Then I ran thru every permutation of 
starting and stopping combinations: home only, return + home, etc., and it came 
up every time, but always on 28. I also did all this, trying to shake it loose, 
both playing and not playing with same results.

Synopsis this paragraph:  27 to 28, no start. Third time 28 played thru but 
returning to 28 started. 4th time, no start. 8 more times, play and not, all 
back to 28. Shut rotate off, same. "Full Screen" back on, same.

I started over..new game from sub-menu..it played right thru to 100 with only 
"sticky" (tho 99 is a Bitch..love it!).

That's the score, hope it helps, & remember I still don't have the new version 
due to prob ie previous gmail.

Yours, 
BeOhBe--<[;{>*

Original comment by forter...@gmail.com on 5 Nov 2013 at 4:31

GoogleCodeExporter commented 8 years ago
Based on the information from Robert Leslie, it appears a latent crash occurs 
when transitioning to the high score screen after the completion of a level.

Original comment by forter...@gmail.com on 5 Nov 2013 at 4:32

GoogleCodeExporter commented 8 years ago
This has been traced to the music player causing the application to crash upon 
memory SIGSEV (segmentation fault) errors, and unhandled OutOfMemoryException 
throws when allocating a module file storage buffer.

Fixed in V2.1.

Original comment by forter...@gmail.com on 12 May 2014 at 1:22