Ok, the can be seen here: http://pastebin.com/f3757c38c
A package is here: http://www.file-pasta.com/file/0/TouchPerfTest.apk The results with this Java program on the N1: 01-28 10:58:04.109: INFO/TouchPerfTest(25423): FPS: 55.82622451910052 01-28 10:58:05.129: INFO/TouchPerfTest(25423): FPS: 56.88378072014953 01-28 10:58:06.139: INFO/TouchPerfTest(25423): FPS: 59.639628676872945 01-28 10:58:07.149: INFO/TouchPerfTest(25423): FPS: 56.210906460963045 01-28 10:58:08.159: INFO/TouchPerfTest(25423): FPS: 56.412939087859826 01-28 10:58:09.159: INFO/TouchPerfTest(25423): FPS: 57.80594930119449 01-28 10:58:10.179: INFO/TouchPerfTest(25423): FPS: 57.8454909425594 01-28 10:58:11.199: INFO/TouchPerfTest(25423): FPS: 35.48240387526278 # Touch 01-28 10:58:12.199: INFO/TouchPerfTest(25423): FPS: 36.79227991210169 01-28 10:58:13.219: INFO/TouchPerfTest(25423): FPS: 38.45430745895421 01-28 10:58:14.219: INFO/TouchPerfTest(25423): FPS: 38.9714564479255 01-28 10:58:15.229: INFO/TouchPerfTest(25423): FPS: 39.72239898193239 01-28 10:58:16.239: INFO/TouchPerfTest(25423): FPS: 46.47522481312174 01-28 10:58:17.239: INFO/TouchPerfTest(25423): FPS: 39.771816995265795 01-28 10:58:18.239: INFO/TouchPerfTest(25423): FPS: 40.95750257724087 # Release 01-28 10:58:19.249: INFO/TouchPerfTest(25423): FPS: 57.94518125100339 01-28 10:58:20.249: INFO/TouchPerfTest(25423): FPS: 56.74715928648654 01-28 10:58:21.249: INFO/TouchPerfTest(25423): FPS: 55.70928078397315 01-28 10:58:22.259: INFO/TouchPerfTest(25423): FPS: 57.890466028132835 01-28 10:58:23.259: INFO/TouchPerfTest(25423): FPS: 58.569238711555535 01-28 10:58:24.289: INFO/TouchPerfTest(25423): FPS: 57.74528074344163 01-28 10:58:25.289: INFO/TouchPerfTest(25423): FPS: 57.777831814439644 01-28 10:58:26.289: INFO/TouchPerfTest(25423): FPS: 58.800815120020864 01-28 10:58:27.299: INFO/TouchPerfTest(25423): FPS: 54.51421656579143 01-28 10:58:28.319: INFO/TouchPerfTest(25423): FPS: 58.10802198951738 01-28 10:58:29.329: INFO/TouchPerfTest(25423): FPS: 56.43850846127753 01-28 10:58:30.329: INFO/TouchPerfTest(25423): FPS: 55.9658411928621 01-28 10:58:31.329: INFO/TouchPerfTest(25423): FPS: 58.66699038117603 01-28 10:58:32.339: INFO/TouchPerfTest(25423): FPS: 58.45059862497602 01-28 10:58:33.359: INFO/TouchPerfTest(25423): FPS: 59.1053390907831 For some unknown reason I can not reach 60 FPS as in the C++ Version. I killed all tasks, but this didn't help. Anyway the effect is clearly visible with the pure Java version, too. Regards, Ralf 2010/1/28 Mario Zechner <badlogicga...@gmail.com> > @Ralf you can find the base activity for my tutorial code at > > http://code.google.com/p/android-gamedev/source/browse/trunk/src/com/badlogic/gamedev/tools/GameActivity.java > . > Inserting fps timing should be easy. > > @Lance that sounds like an interesting idea. However, i suspect the > flood arises at a deeper abstraction level not accesible via the java > framework. > > On Jan 28, 1:16 am, Lance Nanek <lna...@gmail.com> wrote: > > Someone in one of the past threads on this issue mentioned that > > overriding dispatchTouchEvent on Activity performs better than > > onTouchEvent on a View. It might be worth testing that if you guys are > > writing benchmarks anyway. > > > > On Jan 27, 5:56 pm, Ralf Schneider <li...@gestaltgeber.com> wrote: > > > > > Robert, > > > > > yes, there is really nothing more! > > > > > I have already tested with a Thread.sleep(18). This does not change the > > > behaviour. > > > Actually it makes other things worse. Events don't get handled in time: > > > If you don't touch the screen for a while it's get dimmed. If I put in > the > > > Thread.sleep(...) and touch a (dimmed) screen it can take up to 3 and > more > > > seconds until it gets bright again. Without the sleep() it is reacting > > > instantly. > > > > > So I have abonomed Thread.sleep(...) and event.recycle(). I think we > have to > > > live with this behaviour. > > > > > But it would be good if another one can confirm this. Especially if it > is a > > > problem with the Nexus One or Android 2.1. > > > > > Can someone post its Java "Framerate meassurement code" and post it? > Mine is > > > in a "Game-Framework" (which I can not share) written in C++. > > > > > With this I can prepare a simple testcase. But as I told the test is > really > > > simple: Take the code from: > http://android-developers.blogspot.com/2009/04/introducing-glsurfacev... > > > add the log output of the frame rate. > > > > > Regards, > > > Ralf > > > > > 2010/1/27 Robert Green <rbgrn....@gmail.com> > > > > > > So Ralf, > > > > > > Is that really what you have for your touch handling? Nothing - and > > > > you get that slowdown? Can you test with a Thread.sleep(16) in > there? > > > > > > On Jan 27, 3:01 pm, Mario Zechner <badlogicga...@gmail.com> wrote: > > > > > @Ralf > > > > > > > that doesn't look suspicious at all. I guess we'll have to wait for > > > > > Robert to chim in. > > > > > > > On Jan 27, 7:45 pm, Mario Zechner <badlogicga...@gmail.com> wrote: > > > > > > > > Nice, there goes another myth. I read about recycling the > MotionEvent > > > > > > at a couple of places on the net. Thanks for clearing that up! > > > > > > > > I wonder however why it is exposed as a public method. > Additionally, > > > > > > the semantics of onTouch allow me to return a boolean indicating > that > > > > > > i consumed the event (or not). So my reasoning was that in case i > > > > > > return true from onTouch and recycle the event, everything should > work > > > > > > out fine. Maybe add to the documentation that it should never > ever be > > > > > > called by an application? > > > > > > > > Anyways, thanks again! > > > > > > (if you have the time, seeing as you are obviously responsible > for > > > > > > this part of the framework, could you have a look at the other > > > > > > discussion on multi-touch over herehttp:// > > > > groups.google.com/group/android-developers/browse_thread/threa... > > > > > > :) > > > > > > > > On Jan 27, 7:17 pm, Dianne Hackborn <hack...@android.com> wrote: > > > > > > > > > On Tue, Jan 26, 2010 at 4:20 PM, Mario Zechner < > > > > badlogicga...@gmail.com>wrote: > > > > > > > > > > That being said, there shouldn't be any problems with touch > events > > > > on > > > > > > > > devices running android >= 2.0 as they fixed the event flood > > > > problem > > > > > > > > in that version. I couldn't see any problem in my projects > that > > > > make > > > > > > > > heavy use of the touch screen on my droid. There seems to be > a > > > > small > > > > > > > > memory leak in the onTouch method if you don't call > event.recycle > > > > > > > > before exiting the onTouch method. > > > > > > > > > Oh my ghod... are you saying you are calling recycle() on the > > > > MotionEvent > > > > > > > that is -given- to you in onMotionEvent()? Please please > please do > > > > not do > > > > > > > that, you do not own the event, and you are going to cause > nasty > > > > problems if > > > > > > > you recycle it from the caller that does own it. > > > > > > > > > -- > > > > > > > Dianne Hackborn > > > > > > > Android framework engineer > > > > > > > hack...@android.com > > > > > > > > > Note: please don't send private questions to me, as I don't > have time > > > > to > > > > > > > provide private support, and so won't reply to such e-mails. > All > > > > such > > > > > > > questions should be posted on public forums, where I and others > can > > > > see and > > > > > > > answer them. > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "Android Developers" group. > > > > To post to this group, send email to > android-developers@googlegroups.com > > > > To unsubscribe from this group, send email to > > > > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > <android-developers%2bunsubscr...@googlegroups.com<android-developers%252bunsubscr...@googlegroups.com> > > > > > > For more options, visit this group at > > > >http://groups.google.com/group/android-developers?hl=en > > > > > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
