Hmm, well live wallpapers do have icons and other UI stuff draw on top
of them. That could slow things down, or the way they are used could
have been written to intentionally limit their speed to preserve extra
capacity for the foreground, etc.. I wonder how easy it is to debug/
traceview them to find out what's going on. It's easy to do for your
own app's process, which you can set to debuggable and not have to be
on an emulator or rooted phone. Live wallpapers probably run in the
home process or something, though.

On Oct 15, 2:27 pm, Robert Green <[email protected]> wrote:
> The code I posted is mostly just a refactored GLSurfaceView from 2.1
> Master.  It shouldn't perform differently unless something deeper down
> is limiting.
>
> On Oct 15, 10:15 am, "mr.winky" <[email protected]> wrote:
>
> > Yes, I have verified with an opengl app under GLSurfaceView that I can
> > get 60 fps. I havent been able to successfully adapt, beyond what
> > Robert Green has posted, the GLSurfaceView to work forlivewallpaper
> > without the 30fps barrier.
>
> > Is there someone out there that has solved this?
>
> > On Oct 15, 6:54 am, Lance Nanek <[email protected]> wrote:
>
> > > Did you lookup the usual refresh rate, which is indeed 60FPS, or did
> > > you check the specific number for your phone? I know from my own
> > > testing that the HTC Evo 4G cannot go above 30FPS in OpenGL, for
> > > example. Chris Pruett mentioned one of the XPeria devices doing
> > > similar, running at 30FPS, even when he draws a scene with nothing in
> > > it 
> > > (http://code.google.com/events/io/2010/sessions/writing-real-time-game...
> > > ). I'm just pointing out that you may actually have one of these rarer
> > > crippled phone models rather than a software issue.
>
> > > On Oct 13, 1:56 am, "mr.winky" <[email protected]> wrote:
>
> > > > I've been using theGLWallpaperServiceas posted by Robert Green
> > > > (http://www.rbgrn.net/content/354-glsurfaceview-adapted-3d-live-
> > > > wallpapers), which has worked so far for thelivewallpapers but I'm
> > > > hitting a wall when it comes to performance. The GL code is executing
> > > > at the expected speed when swapping (about 14ms after the swap
> > > > occurs), but there seems to be an extreme overhead with thewallpaper
> > > > code of 33ms.
>
> > > > For example, if I was to implement a basiclivewallpaperthat only
> > > > called gl.glClearColor and nothing else, the maximum framerate I can
> > > > achieve is 30fps (33ms), which is far lower than it should be. Now the
> > > > phone refresh rate is 16ms, from what I have read, so I could
> > > > understand hitting a wall at 60 fps.
>
> > > > The question is if there is an alternative way out there? I tried
> > > > naively using the GLSurfaceView with no luck and am looking for
> > > > suggestions from those who may have encountered this issue or know of
> > > > a solution. I have been googling but all posts send me back to the
> > > > above site from Robert Green as the "only" way to do this, and I have
> > > > had no luck finding alivewallpaper"sample" from the SDK that uses
> > > > OpenGL while they state that you have access to OpenGL from here:
>
> > > >http://developer.android.com/resources/articles/live-wallpapers.html
>
> > > > I tried searching for the code for the bundledlivewallpapers with no
> > > > luck, if anyone could throw me a link to one of the wallpapers that
> > > > uses OpenGL that would more than enough for me to figure it out (if a
> > > > different method is used ;)).- Hide quoted text -
>
> > > - Show quoted text -

-- 
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

Reply via email to