|
|
Post by Cory Trese on Jan 20, 2014 13:18:43 GMT -5
|
|
|
|
Post by Jacob on Jan 20, 2014 14:14:26 GMT -5
Stop liking your own posts, thanks for the Update! ... HOW was the last one messed up, BTW?  Sent from my broken HTC Desire C using proboards. Anyone's got a fan? |
|
|
|
Post by fallen on Jan 20, 2014 14:15:45 GMT -5
Jacob - just update, thanks! It's bad enough that it can cause saved game corruption. End of story.
|
|
|
|
Post by contributor on Jan 20, 2014 14:26:55 GMT -5
Jacob - just update, thanks! It's bad enough that it can cause saved game corruption. End of story. nuff said, updating... Would that be games that were opened and played on 1.1.33 or any saved games that we might have had? |
|
|
|
Post by Cory Trese on Jan 20, 2014 14:44:41 GMT -5
Jacob - just update, thanks! It's bad enough that it can cause saved game corruption. End of story. nuff said, updating... Would that be games that were opened and played on 1.1.33 or any saved games that we might have had? There were things in 1.1.33 that you could do that would corrupt your saved game. Only games you opened and ran into one of those. |
|
|
|
Post by Cory Trese on Jan 20, 2014 15:00:41 GMT -5
+1 to user "rearick" who discovered this bug the hard way, and reported it to us directly.
Saved us some heart ache, hopefully v1.1.35 gets to enough people that the bug doesn't hit anyone too bad.
|
|
|
|
Post by Jacob on Jan 20, 2014 17:17:46 GMT -5
Jacob - just update, thanks! It's bad enough that it can cause saved game corruption. End of story. Thanks for the info, fallen. Agreed, that is pretty bad... ... Sent from my broken HTC Desire C using proboards. Anyone's got a fan? |
|
|
|
Post by algesan on Jan 21, 2014 0:44:47 GMT -5
Ouch. 1.1.33 just went live on Amazon, guess no play for a couple days until this one hits.
|
|
|
|
Post by fallen on Jan 21, 2014 1:19:51 GMT -5
algesan - v1.1.35 is now approved on Amazon and is cycling into the store. Should be available soon.
|
|
|
|
Post by algesan on Jan 21, 2014 7:51:33 GMT -5
algesan - v1.1.35 is now approved on Amazon and is cycling into the store. Should be available soon. Yep, it is just a fairly consistent 36-48 hours from the announcement here & it hitting auto update. No big deal & not a TB issue. |
|
|
|
Post by tenbsmith on Jan 21, 2014 10:44:34 GMT -5
I just checked and the Amazon HoS page has version 1.1.35. I seem to see the update on the Amazon HoS page within around 24 hours. It can take a bit longer to propagate to my Fire. My Fire has to be connected to WIFI for a while in order for the update to propagate.
|
|
|
|
Post by algesan on Jan 21, 2014 13:15:16 GMT -5
A delete & reinstall would get the newer version quicker, but at the cost of losing saved parties.
|
|
|
|
Post by tenbsmith on Jan 21, 2014 14:44:40 GMT -5
I've found that if I connect to WIFI and then hit the Sync button in the Kindle settings menu, I get updated within 20-30 minutes. I have to stay connected to WIFI so the update can download.
|
|
|
|
Post by algesan on Jan 21, 2014 22:48:18 GMT -5
I'm almost always on wi-fi, like now, but sync doesn't work faster for me. OTOH, this is a poor little 1st gen Fire.
|
|
|
|
Post by Cory Trese on Jan 22, 2014 1:35:46 GMT -5
I'm almost always on wi-fi, like now, but sync doesn't work faster for me. OTOH, this is a poor little 1st gen Fire. My 1st gen Fire takes a little more than twice as long as the HDX. Your milage may vary. |
|
