Issue #1910


Unfortunately, Shattered Pixel Dungeon has stopped.

Added by G S over 5 years ago. Updated over 3 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Type of work:
C programming, Unknown


Unable to launch latest version of Shattered Pixel Dungeon from F-Droid - get the subject error message.

Shattered Pixel Dungeon is version 0.7.1d (323) - Added on 2019-01-27

Replicant is 6.0 0003 Android running on two tablets: Galaxy Tab 2 7.0 and Galaxy Tab 2 10.0

Sent crash logs to Shattered Pixel Dungeon developer - he thinks it's problem on Replicant side:

Actions #1

Updated by Fil Bergamo over 5 years ago

Hi, thank you for reporting this issue.

Quoting 00-Evan on the Shattered Pixel Dungeon tracker:

so it's likely that shattered is doing something specific which is exposing an error in Replicant's EGL behavior.

This is probably related to the EGL implementation used by Replicant being incomplete (see Issue #705).
Replicant cannot make use of hardware acceleration, because of the lack of readily available free implementations for the supported devices (there is some progress going on in this field, though)

You could try Enabling llvmpipe as software renderer to see if the app works. This would only help debugging the cause. It would be uselessly slow to play games while using LLVMPipe rendering, but at least it can help us understand if the cause of the crash is in the graphics.

You can follow instructions, and find general information on the wiki page about graphics

Actions #2

Updated by G S over 5 years ago

After applying the llvmpipe softeare rendering command and re-booting my tablet is no longer boots.
Factory reset does not help.
I shall report more when/if I re-install the whole system and applications.

Actions #3

Updated by Joonas Kylmälä over 5 years ago

You could try running the software renderer command again ( if you can connect to the device with adb. That should get you back to the default software renderer.

Actions #4

Updated by G S over 5 years ago

Device was not booting after the

adb shell "grep -q "ro.libagl=1" /system/build.prop && sed "s/ro.libagl=1/ro.libagl=0/" -i /system/build.prop || sed "s/ro.libagl=0/ro.libagl=1/" -i /system/build.prop" 

so no ADB or whatever.

Now re-installed vanilla empty Replicant and somehow not immediately willing to re-try.

Actions #5

Updated by Denis 'GNUtoo' Carikli over 4 years ago

  • Target version changed from Replicant 6.0 to Replicant 6.0 0005
Actions #6

Updated by _I3^ RELATIVISM over 3 years ago

  • Type of work C programming, Unknown added

Also available in: Atom PDF