Android - Bug Android VER 1.0.7 Bugs

Please post your Android version 1.0.7 Bugs here, Thanks.

I believe this update was mainly used to address performance issues so the usual suspects are still present.

Grand Canyon between the flippers in MM, 10 Billion light in BoP, backwards side art, blah, blah, blah.

Black Hole works again though so the 4 or 5 of you who play it should be happy! Just joking......... sort of.....

Android version 1.0.7 is definitely faster, too fast for my Samsung Galaxy 10.1. The ball zips around like it just had 10 shots of espresso.

I was only experiencing minor slowdown with 1.0.6 such as during Funhouse multiball and with Ripley's (never had to turn off the HUD) so for me 1.0.7 is a bit of a step backwards (bug fixes aside). Android phone users will probably experience a marked improvement though.

I notice an improvement, but I still get slowdown every so often on BoP and Funhouse. Sometimes in BoP it's bad enough where I guess the game is dropping frames, as the ball is traversing down the path but not fluidly.

Hi

I uninstall the previous version and install this new one. But it cannot remember I've paid before, it keeps asking me the purchase and I can only play the demo version. Even if I click buy, it then show I've purchased. How can I get out of this loop ????

Hey Songor, that's a hard loop to get out of. Eventually your phone/account will remember. Uninstall, install...turn off the phone. Very annoying but it seems to work itself out.

In regards to the update...i'm not very happy...I've had flickering before, usually just got out of game and started again and the flickering would be gone. But now the flickering seems to build up during the game. That never happened before. I will uninstall, reinstall etc...Google will probably not recognise me again!?!? I sure hope it fixes it...otherwise I can't play MM with flicker...I can't even see the ball (just a fuzz) on the Joust loop.

Kudos to Pinball Arcade for doing updates...but I sure hope this hasn't ruined MM for me; i play it most days.

On my HTC sensation, Pinball Arcade only works from a reboot. If I launch it after running some other apps, I get:

05-25 12:58:55.516: W/dalvikvm(13615): JNI WARNING: 0x405252b0 is not a valid JNI reference
05-25 12:58:55.516: W/dalvikvm(13615): in Lcom/farsight/AndroidPinball/javaProject/AndroidPinballLib;.Step (IIZZ)V (GetStaticMethodID)
05-25 12:58:55.526: I/dalvikvm(13615): "Game thread (CPU)" prio=5 tid=24 RUNNABLE
05-25 12:58:55.526: I/dalvikvm(13615): | group="main" sCount=0 dsCount=0 obj=0x40562358 self=0x438530
05-25 12:58:55.526: I/dalvikvm(13615): | sysTid=13647 nice=0 sched=0/0 cgrp=default handle=3799032
05-25 12:58:55.526: I/dalvikvm(13615): | schedstat=( 264373687 275145579 173 )
05-25 12:58:55.526: I/dalvikvm(13615): at com.farsight.AndroidPinball.javaProject.AndroidPinballLib.Step(Native Method)
05-25 12:58:55.526: I/dalvikvm(13615): at com.farsight.AndroidPinball.javaProject.AndroidPinballGameThread.run(AndroidPinballGameThread.java:121)
05-25 12:58:55.526: E/dalvikvm(13615): VM aborting
05-25 12:58:55.577: D/AudioHardwareMSM8660(132): ACDB -> send_audio_cal, acdb_id = 15, path = 0
05-25 12:58:55.577: D/AudioHardwareMSM8660(132): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
05-25 12:58:55.577: D/AudioHardwareMSM8660(132): ACDB -> AUDIO_SET_AUDPROC_CAL
05-25 12:58:55.577: D/AudioHardwareMSM8660(132): ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_VOLTBL_STEP_COPP
05-25 12:58:55.577: D/AudioHardwareMSM8660(132): ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
05-25 12:58:55.587: W/AudioFlinger(132): write blocked for 87 msecs, 30 delayed writes, thread 0x1d6f0
05-25 12:58:55.627: I/DEBUG(3139): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-25 12:58:55.627: I/DEBUG(3139): Build fingerprint: 'htc_europe/htc_pyramid/pyramid:2.3.4/GRJ22/125597.1:user/release-keys'
05-25 12:58:55.627: I/DEBUG(3139): pid: 13615, tid: 13647 >>> com.farsight.AndroidPinball.javaProject <<<
05-25 12:58:55.627: I/DEBUG(3139): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00d
05-25 12:58:55.627: I/DEBUG(3139): r0 fffffe78 r1 deadd00d r2 00000026 r3 00000000
05-25 12:58:55.627: I/DEBUG(3139): r4 800a869c r5 405252b0 r6 80089c78 r7 00000000
05-25 12:58:55.627: I/DEBUG(3139): r8 822c929c r9 462529f0 10 00000000 fp 00000000
05-25 12:58:55.627: I/DEBUG(3139): ip 800a87ac sp 462528f8 lr afd197e9 pc 80046cfc cpsr 20000030
05-25 12:58:55.627: I/DEBUG(3139): d0 74726f6261204d69 d1 6a2e64616572686e
05-25 12:58:55.627: I/DEBUG(3139): d2 7463656a6f725067 d3 64696f72646e410a
05-25 12:58:55.627: I/DEBUG(3139): d4 0062006e00690050 d5 002e006c006c0061
05-25 12:58:55.627: I/DEBUG(3139): d6 006100760061006a d7 006a006f00720050
05-25 12:58:55.627: I/DEBUG(3139): d8 0000000000000000 d9 0000000000000000
05-25 12:58:55.627: I/DEBUG(3139): d10 0000000000000000 d11 0000000000000000
05-25 12:58:55.627: I/DEBUG(3139): d12 0000000000000000 d13 0000000000000000
05-25 12:58:55.627: I/DEBUG(3139): d14 0000000000000000 d15 0000000000000000
05-25 12:58:55.627: I/DEBUG(3139): d16 0000000040028e28 d17 bfd0000000000000
05-25 12:58:55.627: I/DEBUG(3139): d18 3fd0000000000000 d19 0000000000000000
05-25 12:58:55.627: I/DEBUG(3139): d20 0000000000000000 d21 c021800000000000
05-25 12:58:55.627: I/DEBUG(3139): d22 3fd0000000000000 d23 0000000000000000
05-25 12:58:55.627: I/DEBUG(3139): d24 3ff0000000000000 d25 0000000000000000
05-25 12:58:55.627: I/DEBUG(3139): d26 c041800000000000 d27 0000000000000000
05-25 12:58:55.627: I/DEBUG(3139): d28 0000000000000000 d29 0000000000000000
05-25 12:58:55.627: I/DEBUG(3139): d30 0000000000000000 d31 0000000000000000
05-25 12:58:55.627: I/DEBUG(3139): scr 20000012
05-25 12:58:55.677: I/DEBUG(3139): #00 pc 00046cfc /system/lib/libdvm.so
05-25 12:58:55.677: I/DEBUG(3139): #01 pc 00037f6c /system/lib/libdvm.so
05-25 12:58:55.677: I/DEBUG(3139): #02 pc 00038ef6 /system/lib/libdvm.so
05-25 12:58:55.677: I/DEBUG(3139): #03 pc 00038f26 /system/lib/libdvm.so
05-25 12:58:55.677: I/DEBUG(3139): #04 pc 0003af8e /system/lib/libdvm.so
05-25 12:58:55.677: I/DEBUG(3139): #05 pc 0003b846 /system/lib/libdvm.so
05-25 12:58:55.677: I/DEBUG(3139): #06 pc 001ee750 /mnt/asec/com.farsight.AndroidPinball.javaProject-1/lib/libAndroidPinball.so
05-25 12:58:55.677: I/DEBUG(3139): #07 pc 001fe324 /mnt/asec/com.farsight.AndroidPinball.javaProject-1/lib/libAndroidPinball.so
05-25 12:58:55.677: I/DEBUG(3139): #08 pc 001e027c /mnt/asec/com.farsight.AndroidPinball.javaProject-1/lib/libAndroidPinball.so
05-25 12:58:55.687: I/DEBUG(3139): #09 pc 0009fd24 /mnt/asec/com.farsight.AndroidPinball.javaProject-1/lib/libAndroidPinball.so
05-25 12:58:55.687: I/DEBUG(3139): #10 pc 00160cb4 /mnt/asec/com.farsight.AndroidPinball.javaProject-1/lib/libAndroidPinball.so
05-25 12:58:55.687: I/DEBUG(3139): #11 pc 0009e6c4 /mnt/asec/com.farsight.AndroidPinball.javaProject-1/lib/libAndroidPinball.so
05-25 12:58:55.687: I/DEBUG(3139): #12 pc 00018234 /system/lib/libdvm.so
05-25 12:58:55.687: I/DEBUG(3139): code around pc:
05-25 12:58:55.687: I/DEBUG(3139): 80046cdc 447a4479 f7d04c0b 2000ee20 ef2af7d0
05-25 12:58:55.687: I/DEBUG(3139): 80046cec 447c4809 6bdb5823 4798b103 22264902
05-25 12:58:55.687: I/DEBUG(3139): 80046cfc f7d0700a bf00ef9e deadd00d 00044e23
05-25 12:58:55.687: I/DEBUG(3139): 80046d0c 00046a48 000619aa fffffe78 4b09b40e
05-25 12:58:55.687: I/DEBUG(3139): 80046d1c 4c09b517 aa05447b f852591b 6b5b1b04
05-25 12:58:55.687: I/DEBUG(3139): code around lr:
05-25 12:58:55.687: I/DEBUG(3139): afd197c8 4a0e4b0d e92d447b 589c41f0 26004680
05-25 12:58:55.687: I/DEBUG(3139): afd197d8 686768a5 f9b5e006 b113300c 47c04628
05-25 12:58:55.687: I/DEBUG(3139): afd197e8 35544306 37fff117 6824d5f5 d1ef2c00
05-25 12:58:55.687: I/DEBUG(3139): afd197f8 e8bd4630 bf0081f0 00028c58 ffffff64
05-25 12:58:55.687: I/DEBUG(3139): afd19808 b086b570 f602fb01 9004460c a804a901
05-25 12:58:55.687: I/DEBUG(3139): stack:
05-25 12:58:55.687: I/DEBUG(3139): 462528b8 afd43584
05-25 12:58:55.687: I/DEBUG(3139): 462528bc 000cb558
05-25 12:58:55.687: I/DEBUG(3139): 462528c0 00000015
05-25 12:58:55.687: I/DEBUG(3139): 462528c4 afd188b1 /system/lib/libc.so
05-25 12:58:55.687: I/DEBUG(3139): 462528c8 afd4362c
05-25 12:58:55.687: I/DEBUG(3139): 462528cc afd435d8
05-25 12:58:55.687: I/DEBUG(3139): 462528d0 00000000
05-25 12:58:55.687: I/DEBUG(3139): 462528d4 afd197e9 /system/lib/libc.so
05-25 12:58:55.687: I/DEBUG(3139): 462528d8 000619aa
05-25 12:58:55.687: I/DEBUG(3139): 462528dc 405252b0
05-25 12:58:55.687: I/DEBUG(3139): 462528e0 80089c78 /system/lib/libdvm.so
05-25 12:58:55.687: I/DEBUG(3139): 462528e4 00000000
05-25 12:58:55.687: I/DEBUG(3139): 462528e8 822c929c /mnt/asec/com.farsight.AndroidPinball.javaProject-1/lib/libAndroidPinball.so
05-25 12:58:55.687: I/DEBUG(3139): 462528ec afd188e1 /system/lib/libc.so
05-25 12:58:55.687: I/DEBUG(3139): 462528f0 df002777
05-25 12:58:55.687: I/DEBUG(3139): 462528f4 e3a070ad
05-25 12:58:55.687: I/DEBUG(3139): #00 462528f8 80089c78 /system/lib/libdvm.so
05-25 12:58:55.687: I/DEBUG(3139): 462528fc 80037f71 /system/lib/libdvm.so
05-25 12:58:55.687: I/DEBUG(3139): #01 46252900 80089c78 /system/lib/libdvm.so
05-25 12:58:55.687: I/DEBUG(3139): 46252904 80038efb /system/lib/libdvm.so

This update worked out great on my Galaxy S2, the lag is almost completely gone and no more hud trick required, yay!!! All the tables seem to run smooth from the start, now I can finally dig in to Funhouse in a more serious way

thanks for the feedback, we have a galaxy tab here that I will test out.

Playing Funhouse on my Samsung Galaxy 10.1 tablet I experienced a lot of music overlap with different tunes playing at the same time.

Thanks for switching the HUD to default to off on CV btw!

Hi,

Nice update for my galaxy note. CV plays now perfectly. However I still experience slowdowns and dropped frames on Funhouse and BoP.

Many thanks for your work!

EVO 3D

much improved! Funhouse still plays bit slow but a lot better than the last version and is playable now. BOP is almost smooth but still playable. CV is smooth as butter!

I'm still having to switch the HUD off on Bride of Pinbot and Funhouse to get them to play right. Short of installing a more customizable ICS ROM on my phone to tinker with the settings, I don't know what else to do.

McGuirk said:

I'm still having to switch the HUD off on Bride of Pinbot and Funhouse to get them to play right. Short of installing a more customizable ICS ROM on my phone to tinker with the settings, I don't know what else to do.

Click to expand...

Try dropping an email to support@pinballarcade.com if you haven't already.
I've never known them not respond.

I would make the custom rom a last resort personally!

Overall pretty pleased with this version. It's not perfect, but at least everything is playable.

Performance is about the same as 1.0.5 on my 1gHz snapdragon (1.0.6 was crazy slow).

BoP and Funhouse are the slowest tables with the HUD on, but are playable. HUD off they're smooth as silk.

MM and CV run great, really smooth! TotAN, Ripley's, BH, and ToM fall somewhere in between.

The camera views are still mislabeled in the options menu, at least for portrait mode (see 1.0.6 bugs).

EVO 3D

In CV I went up the highwire ramp halfway and came back down and it caused a lock ball when it should not have.

On my Kindle Fire, even after turning off sound both on the device and in-game, I get flipper sounds.

Tabe

Ryan Routon said:

thanks for the feedback, we have a galaxy tab here that I will test out.

Click to expand...

Is there a changelog that you could provide to ND3G to append to his post (or add it to his post manually?). If it details all the performance fixes we *should* be seeing, it might help filter the noise.

I generally report bugs against the table, appropriately flagged in the subject, to keep everything together. Is that harder for your team, or easier?

Might help us all hone our reporting for you, and limit our findings to newly-discovered issues.



Just some thoughts that might make it easier to track things in a forum, rather than a bug tracker.

The next update via Amazon should fix this Tabe.

Really the only performance fixes that were put in the last update was a tweaking of the threading. The gpu thread is given a decently high thread priority, while the cpu thread priority is handled by Android's os (before I tried bumping that up manually and it was causing thread starvation on single core older devices).

Nik Barbour said:

Try dropping an email to support@pinballarcade.com if you haven't already.
I've never known them not respond.

I would make the custom rom a last resort personally!

Click to expand...

The custom ROM thing didn't work out so well, so I may just send in an e-mail. But the problem seems to be better for a number of users here, some even with Galaxy S2 devices, so I'm not sure what else can be done besides modding the OS some more.

McGuirk said:

The custom ROM thing didn't work out so well, so I may just send in an e-mail. But the problem seems to be better for a number of users here, some even with Galaxy S2 devices, so I'm not sure what else can be done besides modding the OS some more.

Click to expand...

Sorry to hear you've still got problems.
Like you say, don't know why other SGS2 owners have seen improvement with 1.0.7 and you haven't.
I know it's frustrating when things won't work.
Try dropping Farsight an email - sounds like an unusual case, who knows you may even get some beta test out of it! (may take a few days for response - I suspect they get a lot of email)

Last resort - try a simpler custom rom, without a custom kernel. (noticed you were trying the full monty in another thread).
Maybe CyanogenMod or MIUI but someone with an SGS2 who's tried a few different roms could steer you better. Forget the more extreme experimental dev roms. Stick to stable releases.
Use 'rom manager' (makes life easier - never a bad thing) do a full backup of your current rom, and when putting a rom on you haven't used before, always clear both dalvik and other app caches to avoid problems with old roms data. (apologies if you already know, or do this - just covering the bases).

Hope this gets sorted for you!