Android 2.3.4

A place to submit bugs to the Andor's Trail Development Team.
Post Reply
Nero
Posts: 20
Joined: Sat Aug 27, 2011 9:57 pm
android_version: 2.3 - Gingerbread

Android 2.3.4

Post by Nero »

Hey guys!

Since there was a new update for my Galaxy S2 I obviously installed it right away.
After the update there has occured several bugs in Andors Trail. Like:

Lag, Character skips "blocks" on movement and sometimes gets a freeze for a couple a seconds
Character Disappear, until you move
Quite often Force Close.. mostly when entering the smallest room with Trainers in the gargoyle cave.
Duplicate Monsters, until death. Also the character auto move when monster is killed..
Sometimes the game get a black screen, only showing the character and occationally the monsters.

Probably there is a few more things going on.. but ive been only in the Gargoyle Cave for the last couple of weeks.
So I dont know if anything elese happens outside.

I dont know if anyone else is having the same problem with the Android 2.3.4
Or if it is just my phone.. :(
User avatar
nyktos
VIP
Posts: 3463
Joined: Wed Sep 14, 2011 5:38 pm
android_version: 7.1 - Nougat
Location: Nor City, Dhayavar

Re: Android 2.3.4

Post by nyktos »

im having similar issues, but less frequent on my LG optimus S... it started when i updated from 2.2.2 to 2.3.3. but i think its the updates problem - not andors, because the phone wont sync (to a PC / laptop) either.

my dealer suggested i revert back to 2.2.2 until the update is reissued.
so i went back to 2.2.2, then a week later it updated again.
fixing the andors problem, but still not syncing.

*shrug*
they'll get it right eventually (?)
:roll:
"Embrace the Shadow"

Image

[Lv: 60] [HP: 175] [AC: 361] [AD: 25-39] [BC: 75]
[Dual Wielding Swords] [Unarmored Fighting]
oskarwiksten
Captain Awesome
Posts: 368
Joined: Sat Jan 29, 2011 8:51 am
android_version: 2.3 - Gingerbread
Location: Stockholm, Sweden

Re: Android 2.3.4

Post by oskarwiksten »

I am interested in getting in touch with someone that wants to verify a potential fix for this. I have a compiled testversion that might have fixed this issue, but would like to verify it on a device where this behaviour can be reproduced.

If you are comfortable with installing debug-versions of the game and would like to help verify a fix for this, contact me and I'll email you a link for an APK to verify.

Thanks in advance
/Oskar
/Oskar
Post Reply