Results 1 to 13 of 13

Thread: Android 5.0 Crash

  1. #1
    Iron Member Contributor Level 2
    Join Date
    Sep 2014
    Location
    Bucharest
    Posts
    15
    Rep Power
    6

    Exclamation Android 5.0 Crash

    Hi,

    I've noticed consistent crashes while trying to fight in the crusade, all of them since my very recent upgrade to Android 5.0.
    Out of 4 tries, only the first one worked. The other 3 (for the next level), with the same or different team comps, resulted in crashes.

    Please, look into this matter asap, since it's a game-breaking bug.

    Thanks,
    OmegWar

  2. #2
    Bronze Member Contributor Level 4
    Join Date
    Oct 2014
    Location
    Bulgaria
    Posts
    53
    Rep Power
    7

    guild: Ba Dao, server 12 Vengeance

    Quote Originally Posted by OmegWar View Post
    Hi,

    I've noticed consistent crashes while trying to fight in the crusade, all of them since my very recent upgrade to Android 5.0.
    Out of 4 tries, only the first one worked. The other 3 (for the next level), with the same or different team comps, resulted in crashes.

    Please, look into this matter asap, since it's a game-breaking bug.

    Thanks,
    OmegWar
    Hi I am having this same issue in Crusade, Arena, Raiding and Booty Cave

    I select my team > press fight > the game force closes

    When I get back in I have wasted the resource for the particular fight - bread, arena try or stamina BUT the fight has not taken place.

    This sucks I hope you can fix it soon.

    The device I`m using is LG Nexus 5, updated to the official OTA version of Android Lollipop 5.0 (Build number LRX210)

  3. #3
    Administrator Contributor Level 12 Betty's Avatar
    Join Date
    Sep 2014
    Posts
    24,245
    Rep Power
    10
    Quote Originally Posted by OmegWar View Post
    Hi,

    I've noticed consistent crashes while trying to fight in the crusade, all of them since my very recent upgrade to Android 5.0.
    Out of 4 tries, only the first one worked. The other 3 (for the next level), with the same or different team comps, resulted in crashes.

    Please, look into this matter asap, since it's a game-breaking bug.

    Thanks,
    OmegWar

    Dear Leader
    We have assigned a developer to look into the Android 5.0 crash problem. Thanks.

    Best Regards
    Betty

  4. #4
    Iron Member Contributor Level 2
    Join Date
    Sep 2014
    Location
    Bucharest
    Posts
    15
    Rep Power
    6
    Quote Originally Posted by Betty View Post

    We have assigned a developer to look into the Android 5.0 crash problem.
    I seem to have been able to reproduce [part of] the bug:
    In both Crusade and Caves, it crashed if both Sapper and Rifleman were in the team. Replacing any one of them with another DPS hero (Leaves Shadow, in my case) worked well.

  5. #5

    Join Date
    Nov 2014
    Posts
    2
    Rep Power
    6
    Quote Originally Posted by kurnavilica View Post
    Hi I am having this same issue in Crusade, Arena, Raiding and Booty Cave

    I select my team > press fight > the game force closes

    When I get back in I have wasted the resource for the particular fight - bread, arena try or stamina BUT the fight has not taken place.

    This sucks I hope you can fix it soon.

    The device I`m using is LG Nexus 5, updated to the official OTA version of Android Lollipop 5.0 (Build number LRX210)
    Same problem here..

    Code:
    11-20 14:42:01.010      781-879/? E/WifiStateMachine﹕ WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=3,75 rxSuccessRate=4,29 targetRoamBSSID=00:24:89:93:46:74 RSSI=-62
    11-20 14:42:01.020      895-895/? I/wpa_supplicant﹕ wlan0: CTRL-EVENT-SCAN-STARTED
    11-20 14:42:04.402      182-871/? D/audio_hw_primary﹕ disable_audio_route: reset and update mixer path: low-latency-playback
    11-20 14:42:04.402      182-871/? D/audio_hw_primary﹕ disable_snd_device: snd_device(2: speaker)
    11-20 14:42:21.009      781-879/? E/WifiStateMachine﹕ WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0,06 rxSuccessRate=0,50 targetRoamBSSID=00:24:89:93:46:74 RSSI=-66
    11-20 14:42:21.009      781-879/? E/WifiStateMachine﹕ WifiStateMachine starting scan for "Vodafone-27808281"WPA_PSK with 2437
    11-20 14:42:21.022      895-895/? I/wpa_supplicant﹕ wlan0: CTRL-EVENT-SCAN-STARTED
    11-20 14:42:41.009      781-879/? E/WifiStateMachine﹕ WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0,00 rxSuccessRate=0,41 targetRoamBSSID=00:24:89:93:46:74 RSSI=-66
    11-20 14:42:41.009      781-879/? E/WifiStateMachine﹕ WifiStateMachine starting scan for "Vodafone-27808281"WPA_PSK with 2437
    11-20 14:42:41.017      895-895/? I/wpa_supplicant﹕ wlan0: CTRL-EVENT-SCAN-STARTED
    11-20 14:43:01.009      781-879/? E/WifiStateMachine﹕ WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0,00 rxSuccessRate=0,19 targetRoamBSSID=00:24:89:93:46:74 RSSI=-68
    11-20 14:43:01.009      781-879/? E/WifiStateMachine﹕ WifiStateMachine starting scan for "Vodafone-27808281"WPA_PSK with 2437
    11-20 14:43:01.020      895-895/? I/wpa_supplicant﹕ wlan0: CTRL-EVENT-SCAN-STARTED
    11-20 14:43:02.005    9219-9249/? A/libc﹕ Fatal signal 11 (SIGSEGV), code 2, fault addr 0x4665737d in tid 9249 (GLThread 491)
    11-20 14:43:02.005    9219-9249/? I/libc﹕ Suppressing debuggerd output because prctl(PR_GET_DUMPABLE)==0
    11-20 14:43:02.043     781-1322/? I/WindowState﹕ WIN DEATH: Window{ef76256 u0 com.ucool.hero/com.ucool.hero.Main}
    11-20 14:43:02.044     781-1322/? W/WindowManager﹕ Force-removing child win Window{2e7986d8 u0 SurfaceView} from container Window{ef76256 u0 com.ucool.hero/com.ucool.hero.Main}
    11-20 14:43:02.047      182-878/? E/IMemory﹕ binder=0xb3c19380 transaction failed fd=-2147483647, size=0, err=-32 (Broken pipe)
    11-20 14:43:02.047      182-878/? E/IMemory﹕ cannot dup fd=-2147483647, size=0, err=-32 (Bad file number)
    11-20 14:43:02.047      182-878/? E/IMemory﹕ cannot map BpMemoryHeap (binder=0xb3c19380), size=0, fd=-1 (Bad file number)
    11-20 14:43:02.053     781-1084/? W/WindowManager﹕ Failed looking up window
        java.lang.IllegalArgumentException: Requested window android.os.BinderProxy@2c3230a9 does not exist
                at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:8412)
                at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:8403)
                at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:1113)
                at android.os.BinderProxy.sendDeathNotice(Binder.java:551)
    11-20 14:43:02.053     781-1084/? I/WindowState﹕ WIN DEATH: null
    11-20 14:43:02.142      193-193/? I/Zygote﹕ Process 9219 exited due to signal (11)
    11-20 14:43:02.152     781-1361/? I/ActivityManager﹕ Process com.ucool.hero (pid 9219) has died
    11-20 14:43:02.155     781-1361/? W/ActivityManager﹕ Force removing ActivityRecord{2e7ffcf7 u0 com.ucool.hero/.Main t305}: app died, no saved state
    11-20 14:43:02.173      781-781/? V/ActivityManager﹕ Display changed displayId=0
    11-20 14:43:02.180     781-1361/? I/ActivityManager﹕ Config changes=480 {1.0 222mcc1mnc it_IT ldltr sw360dp w360dp h567dp 480dpi nrml port finger -keyb/v/h -nav/h s.14}
    11-20 14:43:02.184      781-863/? I/InputReader﹕ Reconfiguring input devices.  changes=0x00000004
    11-20 14:43:02.184      781-863/? I/InputReader﹕ Device reconfigured: id=4, name='touch_dev', size 1080x1920, orientation 0, mode 1, display id 0
    11-20 14:43:02.218      781-850/? I/WindowManager﹕ Screen frozen for +60ms due to Window{3b2d7193 u0 Starting com.ucool.hero}
    11-20 14:43:02.284     781-2407/? W/InputMethodManagerService﹕ Got RemoteException sending setActive(false) notification to pid 9219 uid 10114
    11-20 14:43:02.409      781-797/? I/art﹕ Explicit concurrent mark sweep GC freed 72473(3MB) AllocSpace objects, 1(16KB) LOS objects, 33% free, 31MB/46MB, paused 858us total 82.378ms
    11-20 14:43:02.456    1590-1625/? I/Icing﹕ Usage reports 1 indexed 0 rejected 0 denied 0 imm upload true
    11-20 14:43:02.811    1242-1565/? W/OpenGLRenderer﹕ Incorrectly called buildLayer on View: adg, destroying layer...
    11-20 14:43:04.300      781-850/? I/art﹕ Explicit concurrent mark sweep GC freed 4035(202KB) AllocSpace objects, 0(0B) LOS objects, 33% free, 31MB/46MB, paused 1.085ms total 70.229ms
    nexus 5 Lollipop

  6. #6
    Administrator Contributor Level 12 Betty's Avatar
    Join Date
    Sep 2014
    Posts
    24,245
    Rep Power
    10
    Dear Leader
    Please try mute the game before our fix comes out. It can help avoid the crash. Thanks.

    Best Regards
    Betty

  7. #7

    crashed

    i never play with sound on.. but still crashed and when i play campaign n arena n crusade always force close

  8. #8
    Administrator Contributor Level 3
    Join Date
    Nov 2013
    Posts
    37
    Rep Power
    10
    Please download Version 1.4.5 from Google Play and let us know if the crash has been fixed. Thanks.

  9. #9

    Join Date
    Nov 2014
    Posts
    2
    Rep Power
    6
    Crash fixed with 1.4.6
    I have looooong freeze but 0 crash.
    25-30 sec freeze when i click on start battles (always on first battle, campaing and arena) and something else

  10. #10
    Quote Originally Posted by Betty View Post
    Dear Leader
    Please try mute the game before our fix comes out. It can help avoid the crash. Thanks.

    Best Regards
    Betty
    Hi Betty,

    The crash issue fix,
    but the lagging issue is still there.
    once i off my volume, it will stop lagging.
    but is it want us playing the game like deaf?

    Hope to get your update as soon as possible.

    IT IS SUPER LAGGING

  11. #11
    Iron Member Contributor Level 1
    Join Date
    Oct 2014
    Posts
    11
    Rep Power
    6

    here too

    Crashes all the time.... Some heroes make it more frequent like succubus and keepers.

  12. #12
    Administrator Contributor Level 12 Betty's Avatar
    Join Date
    Sep 2014
    Posts
    24,245
    Rep Power
    10
    Quote Originally Posted by wakakaeddie View Post
    Hi Betty,

    The crash issue fix,
    but the lagging issue is still there.
    once i off my volume, it will stop lagging.
    but is it want us playing the game like deaf?

    Hope to get your update as soon as possible.

    IT IS SUPER LAGGING

    Dear Leader
    We are still working on it. Sorry for the inconvenience.

    Best Regards
    Betty

  13. #13
    Quote Originally Posted by Betty View Post

    Dear Leader
    We are still working on it. Sorry for the inconvenience.

    Best Regards
    Betty
    Hi Betty,

    Good day to you,
    hope to hear good news from you soon.

    Thanks for you reply.

    Regards,
    Eddie

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •