Search Unity

Unable to run Development builds on Android in 5.2.1(/p)

Discussion in 'Editor & General Support' started by AngryMuppet, Oct 6, 2015.

  1. AngryMuppet

    AngryMuppet

    Joined:
    Mar 28, 2014
    Posts:
    34
    Anyone else having issues? When my development build starts up I just have a black screen that crashes out to desktop after a while (works fine in non-dev builds)

    logcat is showing GL issues?

    I/AEE/AED (18472): backtrace:

    I/AEE/AED (18472): #00 pc 000136a4 /system/lib/libc.so (__memcpy_base+108)

    I/AEE/AED (18472): #01 pc 00007c9f /system/vendor/lib/libusc.so (PVRUniflexReadHWBinary+166)

    I/AEE/AED (18472): #02 pc 0006cd2f /system/vendor/lib/egl/libGLESv2_mtk.so

    I/AEE/AED (18472): #03 pc 0006d1fd /system/vendor/lib/egl/libGLESv2_mtk.so

    I/AEE/AED (18472): #04 pc 00039ca7 /system/vendor/lib/egl/libGLESv2_mtk.so (glProgramBinary+418)

    I/AEE/AED (18472): #05 pc 004a136c /data/app/xxxxxxxxxxxxxxxxxxxxx/lib/arm/libunity.so (GlslGpuProgramGLES::CompileProgram(std::string const&, std::string const&, std::string const&, std::string const&, std::string const&, ChannelAssigns&)+656)

    I/AEE/AED (18472): #06 pc 004a07d8 /data/app/xxxxxxxxxxxxxxxxxxxxx/lib/arm/libunity.so (GlslGpuProgramGLES::Create(std::string const&, ChannelAssigns&)+1244)

    I/AEE/AED (18472): #07 pc 004a01e8 /data/app/xxxxxxxxxxxxxxxxxxxxx/lib/arm/libunity.so (GlslGpuProgramGLES::GlslGpuProgramGLES(std::string const&, CreateGpuProgramOutput&)+148)

    I/AEE/AED (18472): #08 pc 002a8278 /data/app/xxxxxxxxxxxxxxxxxxxxx/lib/arm/libunity.so (CreateGpuProgram(std::string const&, CreateGpuProgramOutput&)+2284)

    I/AEE/AED (18472): #09 pc 002a7984 /data/app/xxxxxxxxxxxxxxxxxxxxx/lib/arm/libunity.so (GfxDevice::CreateGpuProgram(std::string const&, CreateGpuProgramOutput&)+12)

    I/AEE/AED (18472): #10 pc 004807dc /data/app/xxxxxxxxxxxxxxxxxxxxx/lib/arm/libunity.so (GfxDeviceWorker::RunCommand(ThreadedStreamBuffer&)+3472)

    I/AEE/AED (18472): #11 pc 0048548c /data/app/xxxxxxxxxxxxxxxxxxxxx/lib/arm/libunity.so (GfxDeviceWorker::Run()+20)

    I/AEE/AED (18472): #12 pc 0047fa34 /data/app/xxxxxxxxxxxxxxxxxxxxx/lib/arm/libunity.so (GfxDeviceWorker::RunGfxDeviceWorker(void*)+80)

    I/AEE/AED (18472): #13 pc 004018c8 /data/app/xxxxxxxxxxxxxxxxxxxxx/lib/arm/libunity.so (Thread::RunThreadWrapper(void*)+84)

    I/AEE/AED (18472): #14 pc 00016f83 /system/lib/libc.so (__pthread_start(void*)+30)

    I/AEE/AED (18472): #15 pc 00014fef /system/lib/libc.so (__start_thread+6)

    Issue is the same in 5.2.1f1 and 5.2.1p2.

    Any ideas/suggestions?

    Ta,
     
  2. joe.davis

    joe.davis

    Joined:
    Apr 17, 2012
    Posts:
    14
    From the logcat, it looks like the shader compilation has failed and the PowerVR driver has been unable to read the compiled shader binary from memory. Do you know if the shaders in the debug build are different from the release ones?

    If you can capture the shader source that's causing the crash and share it with us on the PowerVR forum, we can investigate. Better still, if your Android device is rooted you can install PVRHub to capture a PVRTrace OpenGL ES recording. With this, we can see the entire API call stream as well as the shader source code uploaded to the GL driver. If you do capture a PVRTrace recording and do not want to share it publicly, you can attach it to a ticket in the PowerVR support system.

    Hope this helps,
    Joe
     
    AngryMuppet likes this.
  3. AngryMuppet

    AngryMuppet

    Joined:
    Mar 28, 2014
    Posts:
    34
    Thanks Joe - will do some digging around the shaders - didn't about them being different in the debug build tbh!

    I think I need more coffee!
     
  4. AngryMuppet

    AngryMuppet

    Joined:
    Mar 28, 2014
    Posts:
    34
    Hmm... think it must be something more sinister Unity related - I've deleted all custom shaders from the project so only the standard Unity mobile shaders are in use now and still the same issue (and same logcat)
     
  5. AngryMuppet

    AngryMuppet

    Joined:
    Mar 28, 2014
    Posts:
    34
    I've filed a ticket in the support system - the backtrace doesn't look to hold any useful info so hopefully there is more joy elsewhere in the logcat!