What value are you using for sleep? About 16ms is good for apps that can do 60fps, 32ms for apps doing 30fps etc.
Also check you have no other blocking code on the UI thread and all your application code is on the background thread. -- RichardC On Oct 27, 10:14 pm, Eric <[email protected]> wrote: > Thanks, I've tried this way before, but still not good enough. Before > using sleep(), the FPS reduced from 35 to 15 while pressing the > screen. By now, with the sleep() it reduced from 35 to 25, which I > think not enough for me. > > Anybody got better solution? Or in other words, I should stop trying > to improve it and accept the 35fps to 25fps is almost the best result > for me? :-( > > On Oct 20, 11:50 am, Nightwolf <[email protected]> wrote: > > > Try this solution > > > public boolean onTouchEvent(final MotionEvent event) { > > try { > > Thread.sleep(50); > > } catch (final InterruptedException e) { > > } > > return super.onTouchEvent(event); > > } > > > On Oct 19, 7:00 am, Eric Wang <[email protected]> wrote: > > > > Hi all, > > > > I found that if Ikeeppressingthe touch screen, the app will slow > > > down very much. Both happened in my code and the sample app. > > > > The same issue happened to me on Windows Mobile, but not happened on > > > Symbian. Anybody have some clew to fix it? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
