Android (HTC MAGIC)

Subforum for discussion and help with ScummVM's Android port

Moderator: ScummVM Team

Post Reply
rackham
Posts: 2
Joined: Thu Feb 11, 2010 2:42 pm

Android (HTC MAGIC)

Post by rackham » Thu Feb 11, 2010 2:46 pm

Hello all, two qeustions,

I just downloaded both versions of Beneath a steel sky (cd and floppy) to my htc magic (1.6), included the extra scumm vm package for BASS support for the installed scumm vm. All works fine apart from two issues.

1) I cannot load my saved games, the saved game game starts to load and i hear the music kick in, the exits (and shuts down the vm). Any one else have this problem?

2) The trackball is verrrry slow moving, any way to speed this up?

Thanks for any help, would love to get this working

User avatar
sev
ScummVM Lead
Posts: 1967
Joined: Wed Sep 21, 2005 1:06 pm
Contact:

Post by sev » Thu Feb 11, 2010 7:18 pm

Do not hold your breath for quick answer since Android port is not yet official. gus seem to be busy with real life.


Eugene

gus
ScummVM Porter
Posts: 77
Joined: Fri Feb 13, 2009 5:44 pm

Re: Android (HTC MAGIC)

Post by gus » Fri Feb 12, 2010 5:35 am

rackham wrote:I just downloaded both versions of Beneath a steel sky (cd and floppy) to my htc magic (1.6), included the extra scumm vm package for BASS support for the installed scumm vm. All works fine apart from two issues.

1) I cannot load my saved games, the saved game game starts to load and i hear the music kick in, the exits (and shuts down the vm). Any one else have this problem?
Nope, never heard of this one... Perhaps one of the files got corrupted during the copy to SD card (or there's a bug somewhere)? I would suggest checking the Android logs to see if ScummVM printed any error messages on its way down - get the Android SDK and run "adb logcat"
rackham wrote:2) The trackball is verrrry slow moving, any way to speed this up?
When I tried to implement some mouse acceleration, I found that Android only delivers trackball motion events at a fixed rate, and drops everything faster than that - so it was impossible to track fast "bursts" of movement accurately. I think this may have changed on the Nexus1 (don't know if it is due to software improvements or the CPU is just faster), so there is some hope. In the end I just went with a fixed 2 ScummVM pixels for every trackball motion unit, which lets you click on small things but is annoying for crossing from one side of the screen to the other.

So: I might be able to find some ways to speed this up, but it will take further experimentation and may vary by platform.

rackham
Posts: 2
Joined: Thu Feb 11, 2010 2:42 pm

Post by rackham » Fri Feb 12, 2010 10:43 am

Hello, thanks for your replys.

Here is a bit of debug output for the time where the app dies (and a little before) from ddms.

The last line states it received a remoteException...

Any ideas?

Dori

02-12 10:38:17.373: INFO/DEBUG(4763): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-12 10:38:17.373: INFO/DEBUG(4763): Build fingerprint: 'vodafone/vfpioneer/sapphire/sapphire:1.6/DRC92/15632:user/ota-rel-keys,release-keys'
02-12 10:38:17.383: INFO/DEBUG(4763): pid: 4787, tid: 4803 >>> org.inodes.gus.scummvm <<<
02-12 10:38:17.383: INFO/DEBUG(4763): signal 11 (SIGSEGV), fault addr 003f402a
02-12 10:38:17.383: INFO/DEBUG(4763): r0 002a1c30 r1 003f402a r2 000001e2 r3 00000002
02-12 10:38:17.383: INFO/DEBUG(4763): r4 002a1c08 r5 000001e4 r6 8054588c r7 00000000
02-12 10:38:17.383: INFO/DEBUG(4763): r8 00000000 r9 00000001 10 00000000 fp 00000016
02-12 10:38:17.383: INFO/DEBUG(4763): ip 00000000 sp 450e6c90 lr 80496d5c pc afe0da14 cpsr 60000010
02-12 10:38:17.643: INFO/DEBUG(4763): #00 pc 0000da14 /system/lib/libc.so
02-12 10:38:17.643: INFO/DEBUG(4763): #01 lr 80496d5c /data/data/org.inodes.gus.scummvm/cache/libscummvm.so
02-12 10:38:17.643: INFO/DEBUG(4763): stack:
02-12 10:38:17.643: INFO/DEBUG(4763): 450e6c50 3f800000
02-12 10:38:17.643: INFO/DEBUG(4763): 450e6c54 00000000
02-12 10:38:17.643: INFO/DEBUG(4763): 450e6c58 00000000
02-12 10:38:17.643: INFO/DEBUG(4763): 450e6c5c 00000000
02-12 10:38:17.643: INFO/DEBUG(4763): 450e6c60 3f800000
02-12 10:38:17.643: INFO/DEBUG(4763): 450e6c64 00000000
02-12 10:38:17.653: INFO/DEBUG(4763): 450e6c68 00000000
02-12 10:38:17.653: INFO/DEBUG(4763): 450e6c6c 00000000
02-12 10:38:17.653: INFO/DEBUG(4763): 450e6c70 3f800000
02-12 10:38:17.663: INFO/DEBUG(4763): 450e6c74 00000110
02-12 10:38:17.663: INFO/DEBUG(4763): 450e6c78 00000000
02-12 10:38:17.663: INFO/DEBUG(4763): 450e6c7c 00000000
02-12 10:38:17.663: INFO/DEBUG(4763): 450e6c80 000001e0
02-12 10:38:17.663: INFO/DEBUG(4763): 450e6c84 00000140
02-12 10:38:17.663: INFO/DEBUG(4763): 450e6c88 df002777
02-12 10:38:17.663: INFO/DEBUG(4763): 450e6c8c e3a070ad
02-12 10:38:17.663: INFO/DEBUG(4763): #00 450e6c90 450e6cd4
02-12 10:38:17.663: INFO/DEBUG(4763): 450e6c94 ace091d8 /system/lib/libcorecg.so
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6c98 00000001
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6c9c 00000140
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6ca0 450e6cd4
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6ca4 00000000
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6ca8 00000001
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6cac 002a1c30 [heap]
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6cb0 002a1c08 [heap]
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6cb4 80496d5c /data/data/org.inodes.gus.scummvm/cache/libscummvm.so
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6cb8 00000002
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6cbc 80731e01 /data/data/org.inodes.gus.scummvm/cache/libsky.so
02-12 10:38:17.673: INFO/DEBUG(4763): 450e6cc0 00000000
02-12 10:38:17.683: INFO/DEBUG(4763): 450e6cc4 00000000
02-12 10:38:17.683: INFO/DEBUG(4763): 450e6cc8 00000016
02-12 10:38:17.683: INFO/DEBUG(4763): 450e6ccc 003f402a
02-12 10:38:17.683: INFO/DEBUG(4763): 450e6cd0 00000000
02-12 10:38:17.683: INFO/DEBUG(4763): 450e6cd4 00000016
02-12 10:38:20.523: INFO/ActivityManager(74): Process org.inodes.gus.scummvm (pid 4787) has died.
02-12 10:38:20.533: INFO/WindowManager(74): WIN DEATH: Window{4347ed38 org.inodes.gus.scummvm/org.inodes.gus.scummvm.ScummVMActivity paused=false}
02-12 10:38:20.533: INFO/WindowManager(74): WIN DEATH: Window{435b0780 SurfaceView paused=false}
02-12 10:38:20.573: DEBUG/Zygote(50): Process 4787 terminated by signal (11)
02-12 10:38:20.593: INFO/WindowManager(74): Setting rotation to 0, animFlags=0
02-12 10:38:20.593: INFO/WindowManager(74): Config changed: { scale=1.0 imsi=0/0 loc=en_GB touch=3 keys=1/1/2 nav=3 orien=1 layout=18}
02-12 10:38:20.603: WARN/WindowManager(74): performLayoutAndPlaceSurfacesLocked called while in layout
02-12 10:38:20.753: WARN/UsageStats(74): Unexpected resume of com.android.launcher while already resumed in org.inodes.gus.scummvm
02-12 10:38:20.823: DEBUG/StatusBar(74): updateResources
02-12 10:38:21.093: WARN/InputManagerService(74): Got RemoteException sending setActive(false) notification to pid 4787 uid 10063

gus
ScummVM Porter
Posts: 77
Joined: Fri Feb 13, 2009 5:44 pm

Post by gus » Fri Feb 19, 2010 2:55 am

rackham wrote:Here is a bit of debug output for the time where the app dies (and a little before) from ddms.

The last line states it received a remoteException...

Any ideas?

Dori

02-12 10:38:17.373: INFO/DEBUG(4763): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-12 10:38:17.373: INFO/DEBUG(4763): Build fingerprint: 'vodafone/vfpioneer/sapphire/sapphire:1.6/DRC92/15632:user/ota-rel-keys,release-keys'
02-12 10:38:17.383: INFO/DEBUG(4763): pid: 4787, tid: 4803 >>> org.inodes.gus.scummvm <<<
02-12 10:38:17.383: INFO/DEBUG(4763): signal 11 (SIGSEGV), fault addr 003f402a
...
Unfortunately, this is from the crash onwards. What we really want is the (ScummVM) messages before this - hoping to see ScummVM printing some sort of error message right before it crashed.

Post Reply