101 moving smileys => 60 frames per second

[Erel]

Starting with Android 3.0 it is possible to use hardware acceleration with the standard views. Hardware acceleration is about 5-10 times faster than the software based drawings.

As you can see in the above image all 101 smileys are redrawn on every "tick". The frame rate is between 55 to 65 frames per second.

This will be the base of a new library and framework...

 

[derez]

What have we done to earn all this ?

Thank you Erel :icon_clap:

 

[Jim Brown]

Great stuff. This has been one of the drawbacks with software drawing - slow rendering. It prompted me to create an OpenGL based 2D libray. Looking forward to the next update

 

[Erel]

This solution will only be able to use hardware acceleration with Android 3.0 or above. So solutions based on OpenGL do have an advantage if you target Android 2.x devices as well.

 

[Jost aus Soest]

Only 101?

102 would have been great!

Just kidding...
:sign0098:

 

[Erel]

For 300 moving smileys the fps rate is between 35 to 60 (still looks smooth). Without hardware acceleration it is about 14 fps (looks bad).

Tested on Galaxy Nexus 4.1.

Note that these are just very simple tests.

 

[NJDude]

Cool!.

Also, I would suggest you make that example an app and post it on the market and charge 99 cents, it will go viral you'll be a millionaire in no time, people seem to buy this kind of silly apps

 

[Roger Garstang]

Awesome, so this new library will make use of it like a per application usage (Application is hardware acceleration capable) and not need the hardware acceleration override turned on in the device's options?

 

[Erel]

The library will allow you to use hardware acceleration if that is available.

The standard canvas object cannot use hardware acceleration. This library uses a different method to draw the graphics.

 

[Jim Brown]

This solution will only be able to use hardware acceleration with Android 3.0 or above. So solutions based on OpenGL do have an advantage if you target Android 2.x devices as well

Yes. Good point.
Could you post the source and smiley Erel? It would be interesting to see how OpenGL stands up. I am assuming it is equally capable.

 

[WAZUMBi]

Where do you find the FPS when testing apps?

 

[Erel]

It is done by checking the actual time passed between two timer ticks.

 

[Informatix]

Did you see that library ?
NineOldAndroids

 

[Erel]

Yes. This library is for a different task.

 

[Jim Brown]

Where do you find the FPS when testing apps?

I do mine FPS timing like this:

'snippet of FPS code
Sub Process_Globals
   Dim time As Timer
End Sub

Sub Globals
   'fps variables
   Dim frameCount As Int
   Dim oldTime,FPS As Long
End Sub

Sub Activity_Create(FirstTime As Boolean)
   time.Initialize("Timer1",10)
End Sub

Sub Activity_Resume
   time.Enabled=True
End Sub

Sub Activity_Pause (UserClosed As Boolean)
   time.Enabled=False
End Sub

Sub Timer1_Tick
   '
   ' DO DRAWING STUFF
   '
   ' FPS monitor
   If DateTime.Now>oldTime Then
      oldTime=DateTime.now+1000
      FPS=frameCount :  frameCount=0
   Else
      frameCount=frameCount+1
   End If
   somelabel.Text="FPS:" & FPS
End Sub

 

[Erel]

Some progress...

 

[monki]

Hi Erel,
this looks very good.
When will be available this Lib?

Monki

 

[Erel]

It will probably take a week or two due to other constraints.

The library itself doesn't do match. It is only responsible for drawing a list of bitmaps.