Closed GoogleCodeExporter closed 8 years ago
OK, thanks for reporting that. I wonder if the CPU in that phone is different
enough
that I would have to cross-compile the native code for another target. Then
again,
people have also informally reported crashes on startup on HTC Magic, etc, which
should have the same CPU as the G1, so perhaps there is something else going
on. Will
try to debug, though it's obviously a bit tricky without having the hardware
available... If anybody has the Android SDK set up, you can try running "adb
logcat"
and perhaps the log could tell me something more about why it couldn't start.
Original comment by farnst...@gmail.com
on 8 Nov 2009 at 7:45
just gave this a poke on the android 2.0 emulator, got the same error.
Here's the adb trace:
D/dalvikvm( 198): Trying to load lib /data/data/com.nethackff/lib/libnethack.so
0x44b34ff8
D/dalvikvm( 198): Added shared lib /data/data/com.nethackff/lib/libnethack.so 0
x44b34ff8
D/dalvikvm( 198): No JNI_OnLoad found in /data/data/com.nethackff/lib/libnethac
k.so 0x44b34ff8
W/dalvikvm( 198): threadid=15: thread exiting with uncaught exception (group=0x
4001b188)
E/AndroidRuntime( 198): Uncaught handler: thread Thread-8 exiting due to uncaug
ht exception
E/AndroidRuntime( 198): java.lang.RuntimeException: android.os.Exec
E/AndroidRuntime( 198): at com.nethackff.NetHackApp.doCommand(NetHackApp
.java:1365)
E/AndroidRuntime( 198): at com.nethackff.NetHackApp.run(NetHackApp.java:
1251)
E/AndroidRuntime( 198): at java.lang.Thread.run(Thread.java:1096)
I/Process ( 53): Sending signal. PID: 198 SIG: 3
I/dalvikvm( 198): threadid=7: reacting to signal 3
E/dalvikvm( 198): Unable to open stack trace file '/data/anr/traces.txt': Permi
ssion denied
I/ARMAssembler( 53): generated scanline__00000077:03515104_00000000_00000000 [
33 ipp] (47 ins) at [0x4644b8:0x464574] in 424495 ns
I/ARMAssembler( 53): generated scanline__00000177:03515104_00001001_00000000 [
91 ipp] (114 ins) at [0x464578:0x464740] in 484488 ns
I/ActivityManager( 53): Displayed activity com.nethackff/.NetHackApp: 1811 ms
(total 1811 ms)
I/ARMAssembler( 53): generated scanline__00000077:03545404_00000A04_00000000 [
29 ipp] (51 ins) at [0x464748:0x464814] in 393626 ns
I/Process ( 198): Sending signal. PID: 198 SIG: 9
I/ActivityManager( 53): Process com.nethackff (pid 198) has died.
I/WindowManager( 53): WIN DEATH: Window{44cdf3d0 com.nethackff/com.nethackff.N
etHackApp paused=false}
W/UsageStats( 53): Unexpected resume of com.android.launcher while already res
umed in com.nethackff
E/gralloc ( 53): [unregister] handle 0x4e96a8 still locked (state=40000001)
W/InputManagerService( 53): Got RemoteException sending setActive(false) notif
ication to pid 198 uid 10023
Hope that helps.
Original comment by PatrickS...@gmail.com
on 11 Nov 2009 at 10:46
I have looked into this now and I think I have a fix. At least, it runs in the
Android 2.0 emulator for me now. I have uploaded this potentially fixed version
as
NetHack-1.1.3-beta.apk, available in the Downloads section. I would much
appreciate
if somebody with a Motorola Droid could download and install this, and report
back to
me whether it works or not. There are no new features in this version (I have
plenty
in the works, but not ready for release), so if it doesn't run on Droid there
is not
much point in releasing it on the Android Market. Aside from not crashing on
startup,
please also verify that the text shows up readable (not half the size or
something
from the increased resolution). I would also be interested in hearing back from
HTC
Magic or Hero users, as I believe some crashes on startup were reported there
too in
the past (though it probably won't be really playable on those until I finish
the
rest of my improvements, with a better virtual keyboard and stuff). Thanks!
Original comment by farnst...@gmail.com
on 12 Nov 2009 at 10:14
As far as I can tell, it works on my droid.
Original comment by Bright.N...@gmail.com
on 12 Nov 2009 at 1:03
Yup, that fixed it. Font/display etc all looks good so far.
Original comment by davidkwood@gmail.com
on 12 Nov 2009 at 2:31
Works for me, too!
Original comment by PatrickS...@gmail.com
on 13 Nov 2009 at 12:38
Closing this, version 1.1.3 with the fix has been released on Android Market
now.
Thanks to everybody who helped to get this resolved.
Original comment by farnst...@gmail.com
on 14 Nov 2009 at 5:24
Original issue reported on code.google.com by
davidkwood@gmail.com
on 7 Nov 2009 at 3:31