<p>Hi Martin and Troy, </p>
<p>I finally got the AndBible source built; I needed to get the jsword source and also raise the memory limit for Eclipse--it thrashed and eventually crashed in the linker/dex step. There's still a dex warning that floods the Console, but it works on my Droid X. I made a few minor modifications to ensure I could, but nothing serious yet. </p>
<p>Major things I'd like to work on as a user are navigation, continuous scrolling, and verse number sync. Also, do you think we should replace the backend with native libsword? That might help formatting and speed, but I don't know how deeply it's woven into the code. The Bishop code could be a useful example if we decide to go that way. </p>
<p>Should we continue discussion on this list? </p>
<p>-Ken (mobile)</p>
<p><blockquote type="cite">On Aug 26, 2010 1:39 AM, "Troy A. Griffitts" <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>> wrote:<br><br>Dear Ken,<br>
<br>
Thank you for the debug. I also have had trouble with the installer and<br>
haven't had time to look into it.<br>
<br>
The history is that I build Bishop as a sort of proof of concept for the<br>
java-jni bindings for Android. I mostly work in the engine code. The<br>
jni binding code I kept in SWORD SVN and the Bishop code I just backed<br>
up occasionally to our server. Last year my drive crashed and I lost<br>
some work but might have pieced it all back together. Here is an email<br>
I sent to Gary with links to all my stuff.<br>
<br>
______________________<br>
<br>
After last year when I started the work I had a harddrive die on my<br>
laptop. I had been backing up the work regularly, but lost about 2<br>
weeks of work in the crash. I used a recovery tool to salvage many of<br>
the files from the bishop project and think I may have close to what is<br>
in the apk. Here are my resources if you want to try to piece things<br>
together:<br>
<br>
Lastest binary when I stopped, dated 11-18-2009:<br>
<p><font color="#500050"><a href="http://crosswire.org/~scribe/bishop.apk">http://crosswire.org/~scribe/bishop.apk</a><br></font></p>Latest backup of source, dated 10-31-2009:<br>
<a href="http://crosswire.org/~scribe/bishop-20091031.tar.gz" target="_blank">http://crosswire.org/~scribe/bishop-20091031.tar.gz</a><br>
<br>
Latest binary after reconstructing source and I think some small new<br>
work (I think this is built with debug symbols in the native library so<br>
it's a little bigger):<br>
<p><font color="#500050"><a href="http://crosswire.org/~scribe/bishop2.apk">http://crosswire.org/~scribe/bishop2.apk</a><br></font></p>Current backup of source which built the above:<br>
<a href="http://crosswire.org/~scribe/bishop-20100804.tar.gz" target="_blank">http://crosswire.org/~scribe/bishop-20100804.tar.gz</a><br>
<br>
Please excuse my ignorance of Android programming. I am fumbling<br>
through it all.<br>
<br>
I remember having trouble with the InstallMgr. It sometimes connects<br>
and downloads and other times it does not. I thought it might be the<br>
limited memory on my G1 or some trouble with the timing of the FTP code<br>
in the native library. I've found serious bugs in Android's system<br>
calls, (e.g. memccpy) and reported it to them, but they still haven't<br>
fixed it. I use my own version in the ftp lib to avoid the bug. That<br>
is where I stopped-- thinking I needed to debug this ftp intermittent<br>
issue. I didn't compare how well the older .apk works versus the newer<br>
.apk. Maybe the older version worked better? Or maybe a newer version<br>
of Android or new phone works better?<br>
<br>
Let me know what you find.<br>
<font color="#888888"><br>
Troy<br>
</font><p><font color="#500050"><br><br><br>On 08/24/2010 09:01 PM, Kenneth Arnold wrote:<br>> I just got an Android phone, and after seeing the...</font></p></blockquote></p>