<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Peter,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Maybe the code that Soot generated for the new APK is wrong. As you have already identified the rendering loop of the game, can you have a look into how the code of the original app is different from the one of the app generated by Soot with respect to this rendering loop? If we have a method that gets corrupted by Soot, it should not be too hard for us to figure out why this happens and fix it.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>In general, such reports which are clearly or most likely issues in Soot should rather be reported in our issue tracker on Github and not on the mailing list where they can easily get lost if no-one immediately has the time to look into it.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> Steven<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> soot-list-bounces@CS.McGill.CA [mailto:soot-list-bounces@CS.McGill.CA] <b>Im Auftrag von </b>Peter Kim<br><b>Gesendet:</b> Donnerstag, 5. März 2015 21:50<br><b>An:</b> soot-list@cs.mcgill.ca<br><b>Betreff:</b> [Soot-list] output as APK failing<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Hi,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>After I instrument a game app, the game is not displaying the graphics anymore on the mobile device (Galaxy S5), but the graphics render loop is still running. What is odd is that even when the code is unchanged and is merely output by Soot, the same problem occurs. Unfortunately, I cannot find any useful error/debug information to pinpoint the problem. The transformation passed validation and was signed and aligned.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The app is downloadable from here, <a href="https://github.com/siondream/freegemas-gdx">https://github.com/siondream/freegemas-gdx</a>. The APK file will be generated after you run it and will be located in freegemas-android/bin.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I'm using the following statements to get the output:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>Options.v().set_src_prec(Options.src_prec_apk);<o:p></o:p></p></div><div><p class=MsoNormal>Options.v().set_output_format(Options.output_format_dex); <o:p></o:p></p></div><div><p class=MsoNormal>soot.options.Options.v().set_force_android_jar("C:/android-19/android.jar");<o:p></o:p></p></div><div><p class=MsoNormal>Options.v().set_allow_phantom_refs(true);<o:p></o:p></p></div><div><p class=MsoNormal>ArrayList<String> procDir = new ArrayList<String>();<o:p></o:p></p></div><div><p class=MsoNormal>procDir.add("C:/freegemas.apk"); <o:p></o:p></p></div><div><p class=MsoNormal>Options.v().set_process_dir(procDir);<o:p></o:p></p></div><div><p class=MsoNormal>Options.v().set_output_dir("C:/sootoutput"); <o:p></o:p></p></div><div><p class=MsoNormal>Options.v().set_whole_program(true);<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I found someone posted a similar issue a while ago (<a href="http://marc.info/?l=soot-list&m=141925896127089&w=2">http://marc.info/?l=soot-list&m=141925896127089&w=2</a>) but could not find responses to it.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thank you.<o:p></o:p></p></div></div></div></body></html>