I'm thinking about learning to skin, mostly because it seems impossible for me to find exactly what I want to do so I have to do it myself. I can't get too crazy with live wallpapers and such though, as theres limited resources such as processing power and battery use. So my questions are:
How much processing and battery does it take to draw shapes, as opposed to displaying an image (from file)?
How much processing and battery does it take to slide images around, such as for switching screens?
Would I be using less resources if I used a small image and tiled it over the whole screen, as opposed to having a large picture?
Do images get drawn in layers? If I keep stacking images on top of each other, is it going to be a huge hog?
I don't mean exact amounts, just relative amounts on whats efficient for Android (for which I know very little of). I'm guessing it would perform like a browser would?
Pencil Box Free v. 1.2
Pencil Box Free can help you to create simple and complex multilayer pictures, larger than a screen of your Android device. You have a great opportunity to draw your own picture or create it from image JPEG or BMP file. It`s also possible to add extra layers, color them and save your results in JPEG image file.
The main features of Version 1.0 include:
- To create a blank picture with the resolution you need. A limit of width and height is no more than 10000 pixels. The limit of the pixels in one layer is no more than 1000000;
- To add extra layers to a picture. Their limit depends on memory capabilities of Android device and resolution of picture;
- To set and reset a visibility of each layer;
- To set an active layer. The active layer is a layer where you are drawing your picture;
- To delete a layers which you do not need anymore;
- To draw with a finger or a stylus on an active layer;
- To erase previous images from the active layer;
- To select a color of virtual pen;
- To select a color of background;
- To select a width of virtual pen;
- To move a picture inside device display in case of picture is larger than display;
- To show the whole image in case of picture is larger than display;
- To save all your work in file at memory card;
- To open saved picture from file;
- To create a blank picture and to put an image from JPEG or BMP file into one of the pictures` layer;
- To transfer all layers of your picture to separate JPEG image files;
- To transfer all visible layers of your picture to one JPEG file.
Ver. 1.1. An user interface is improved. Toolbars, seekbar and color palette are added. The sequence of drawing of the layers is set by the order of drawing now, which can be adjust by user.
Ver. 1.2. A Zoom toolbar is added. Now you can draw, erase, shift your picture with x2,x4 or x8 zoom. It's a good opportunity to draw the fine details of the picture!
Available in Android Market!
Nice app, thanks. Would be great if it could "smooth" freehand-traced lines. Scribbling with your finger on a capacitative screen is quite inprecise.
Ernesto de Bernardis
N900 - Galaxy Tab 7"
Thank you for response! I will think about this feature.
Here are some screenshots from the application
Version 1.3
Undo and Redo actions for drawing and erasing, multitouch support for zoom and move actions are available.
Saw this one on google+ and I think it's a nice read and very informative
How about some Android graphics true facts?
I get tired of seeing so much misinformation posted and repeated all over the place about how graphics rendering works on Android. Here is some truth:
• Android has always used some hardware accelerated drawing. Since before 1.0 all window compositing to the display has been done with hardware.
• This means that many of the animations you see have always been hardware accelerated: menus being shown, sliding the notification shade, transitions between activities, pop-ups and dialogs showing and hiding, etc.
• Android did historically use software to render the contents of each window. For example in a UI like http://www.simplemobilereview.com/wp-content/uploads/2010/12/2-home-menu.png there are four windows: the status bar, the wallpaper, the launcher on top of the wallpaper, and the menu. If one of the windows updates its contents, such as highlighting a menu item, then (prior to 3.0) software is used to draw the new contents of that window; however none of the other windows are redrawn at all, and the re-composition of the windows is done in hardware. Likewise, any movement of the windows such as the menu going up and down is all hardware rendering.
• Looking at drawing inside of a window, you don’t necessarily need to do this in hardware to achieve full 60fps rendering. This depends very much on the number of pixels in your display and the speed of your CPU. For example, Nexus S has no trouble doing 60fps rendering of all the normal stuff you see in the Android UI like scrolling lists on its 800x480 screen. The original Droid however struggled with a similar screen resolution.
• "Full" hardware accelerated drawing within a window was added in Android 3.0. The implementation in Android 4.0 is not any more full than in 3.0. Starting with 3.0, if you set the flag in your app saying that hardware accelerated drawing is allowed, then all drawing to the application’s windows will be done with the GPU. The main change in this regard in Android 4.0 is that now apps that are explicitly targeting 4.0 or higher will have acceleration enabled by default rather than having to put android:handwareAccelerated="true" in their manifest. (And the reason this isn’t just turned on for all existing applications is that some types of drawing operations can’t be supported well in hardware and it also impacts the behavior when an application asks to have a part of its UI updated. Forcing hardware accelerated drawing upon existing apps will break a significant number of them, from subtly to significantly.)
• Hardware accelerated drawing is not all full of win. For example on the PVR drivers of devices like the Nexus S and Galaxy Nexus, simply starting to use OpenGL in a process eats about 8MB of RAM. Given that our process overhead is about 2MB, this is pretty huge. That RAM takes away from other things, such as the number of background processes that can be kept running, potentially slowing down things like app switching.
• Because of the overhead of OpenGL, one may very well not want to use it for drawing. For example some of the work we are doing to make Android 4.0 run well on the Nexus S has involved turning off hardware accelerated drawing in parts of the UI so we don’t lose 8MB of RAM in the system process, another 8MB in the phone process, another 8MB in the system UI process, etc. Trust me, you won’t notice -- there is just no benefit on that device in using OpenGL to draw something like the status bar, even with fancy animations going on in there.
• Hardware accelerated drawing is not a magical silver bullet to butter-smooth UI. There are many different efforts that have been going on towards this, such as improved scheduling of foreground vs. background threads in 1.6, rewriting the input system in 2.3, strict mode, concurrent garbage collection, loaders, etc. If you want to achieve 60fps, you have 20 milliseconds to handle each frame. This is not a lot of time. Just touching the flash storage system in the thread that is running the UI can in some cases introduce a delay that puts you out of that timing window, especially if you are writing to storage.
• A recent example of the kinds of interesting things that impact UI smoothness: we noticed that ICS on Nexus S was actually less smooth when scrolling through lists than it was on Gingerbread. It turned out that the reason for this was due to subtle changes in timing, so that sometimes in ICS as the app was retrieving touch events and drawing the screen, it would go to get the next event slightly before it was ready, causing it to visibly miss a frame while tracking the finger even though it was drawing the screen at a solid 60fps.
• When people have historically compared web browser scrolling between Android and iOS, most of the differences they are seeing are not due to hardware accelerated drawing. Originally Android went a different route for its web page rendering and made different compromises: the web page is turned in to a display list, which is continually rendered to the screen, instead of using tiles. This has the benefit that scrolling and zooming never have artifacts of tiles that haven’t yet been drawn. Its downside is that as the graphics on the web page get more complicated to draw the frame rate goes down. As of Android 3.0, the browser now uses tiles, so it can maintain a consistent frame rate as you scroll or zoom, with the negative of having artifacts when newly needed tiles can’t be rendered quickly enough. The tiles themselves are rendered in software, which I believe is the case for iOS as well. (And this tile-based approach could be used prior to 3.0 without hardware accelerated drawing; as mentioned previously, the Nexus S CPU can easily draw the tiles to the window at 60fps.)
• Hardware accleration does not magically make drawing performance problems disappear. There is still a limit to how much the GPU can do. A recent interesting example of this is tablets built with Tegra 2 -- that GPU can touch every pixel of a 1280x800 screen about 2.5 times at 60fps. Now consider the Android 3.0 tablet home screen where you are switching to the all apps list: you need to draw the background (1x all pixels), then the layer of shortcuts and widgets (let’s be nice and say this is .5x all pixels), then the black background of all apps (1x all pixels), and the icons and labels of all apps (.5x all pixels). We’ve already blown our per-pixel budget, and we haven’t even composited the separate windows to the final display yet. To get 60fps animation, Android 3.0 and later use a number of tricks. A big one is that it tries to put all windows into overlays instead of having to copy them to the framebuffer with the GPU. In the case here even with that we are still over-budget, but we have another trick: because the wallpaper on Android is in a separate window, we can make this window larger than the screen to hold the entire bitmap. Now, as you scroll, the movement of the background doesn’t require any drawing, just moving its window... and because this window is in an overlay, it doesn’t even need to be composited to the screen with the GPU.
• As device screen resolution goes up, achieving a 60fps UI is closely related to GPU speed and especially the GPU’s memory bus bandwidth. In fact, if you want to get an idea of the performance of a piece of hardware, always pay close attention to the memory bus bandwidth. There are plenty of times where the CPU (especially with those wonderful NEON instructions) can go a lot faster than the memory bus.
All credit goes to Dianne Hackborn. Thanks for sharing this!
HAHAHAHA good facts, and very interesting!
Great post
yup, Nice Post!
Interesting observation!
Updates:
Version 13 28.10.2012:
-Many new features added on htc evo 3d version
-neverending road, drag to drive
-big 3d analog clock
-timeshift-displacement lava-like shader material
-Sterescopic suport, red-green, s3d and normal mode
-...
Version 9 10.10.2012:
-Faster Rendering for all Objects
-Changed to old fluid colors
Version 8 07.10.2012:
loading custom obj files!
Load any 3D-Mesh to your 3D live wallpaper!
Just place "beammeup.obj" on sd root and activate loading from settings.
Try with attached exampes.
News: New HTC-evo-3D stereoscopic Version in new thread...
obj-import will work for both versions soon:
http://forum.xda-developers.com/showthread.php?t=1904203
Version 7 25.09.2012:
saved some cpu-power, reworked internal framerate-and sensordelay, re-balanced Color Fluid Surface-Particles, fixed a bug of previous Versions not showing 3D-Andoid if active alone.
Version 6 25.09.2012:
HTC-Evo-3D Stereoscopic Flying Particle added in landscape and portrait
Version 5 25.09.2012:
-HTC-Evo-3D Stereoscopic 3D Mode supported in landscape and portrait with auto switchig orientation. Use with "Jmz 3D Switcher". 3D-Mode can be used with other Objects. It has one build-in Image yet and can load custom, pre-interlaced in devices resolution. Will add sterescopic support for 3D-Objects like the Android and loading custom obj´s. Also particles flying into your head...
-Optimized color fluid and beta-particles a little and rebalanced the connection between both so activate both and test.
-I forgot to disable multisampling on Version 4 so it is the only version with multisampling. It will not run on devices without ms. Also it looks a little better and runs a little slower. This is was only Version 4, "fixed" on Version 5...
Fix Version 4 24.09.2012: Path to not-cropped Image will be saved since this version, so selected Image will come up after reboot or resetting wallpaper. If image is not avilible because sdcard is not mounted yet after reboot, backup tex will be used until sdcard is mounted. If Image is renamed or deleted, also backup tex will be used until you set another image or restore missing file. So all Settings should work fine now.
Note: Framerate and Sensorspeed are tweaked to 100% to give you a very smooth first run, until you touch the framerate slider first time.
I can't stop touching my phone!
BIG UPDATE Liquid Version 3 23.09.2012:
So much new stuff: New Objects, New Features, New artworks, New Settings, many Fixes and Changes, improved stability.
New Objects:
-The amazing Color Fluid Surface(including; Liquid Colors, Anti-Color, Particles, a swimming Object, Connections to other Objects, own new sub-section in Settings)
-Full Screen Image(just shifting a little with homescreen)
-New Liquid Beta-Particles (linked to the Fluid Surface to make 2 fluid physics engines connected driving each other!)
-The amazing Color Fluid Surface:
Get a realy liquid screen.
Make fine colorfull swhirls with each finger or mix the whole fluid witch all touch points.
Continuously auto-selecting the "next most-amazing color" for each touch point.
See the colors mixing transparent on any background.
Finger 4 will dropp Anti-Color, the mathematical opposite of Color. Anti-Color and Color will be colorfull neutralized against each other. Naturally Anti-Color is invisible but I found a way to show it. It´s enabled on default and will change to it´s naturally invisibility if switching to "Inverse Fluid Colors".
The Engine has it´s "own" swimming Particles and a swimming customizable Object.
Some Objects are connected to the fluid and will swimm in fluid and/or add forces to it.
The Fluid Particles are very fine and have some options, you can select an independent build-in texture to keep them look Particle-like while using any Picture on other Objects.
Fluid Surface code is great but calculated on cpu and needs power at higher fluid resolution. This needs some optimizations, I will try to move some expensive calculations to faster scripts or buffer-array-operations to make it run faster at higher resolutions. Rendering fluid is already fast.
-Static Background Picture. It´s just shifting a little with homescreen. If you select a not-transparent Picture, background will hide the 3D-Android and the 3D-Background Particles, so don't forget to disable hidden Objects to safe power.
-New Liquid Beta-Particles.
Interesting dynamic physics. Connected to Fluid Surface, if active together, engines will move each other, result will move very dynamic or chaotic.
Beta because unoptimized, slow, cpu draining, laggy touch and unstable physics could force close somtimes because moving out of bounds. But It can blast the Fluid
-New Image Artworks all supporting Transparency:
If you want to use old removed Images, you can extract the Images from old apk file.
-New Settings. Added icons to most options. Select Picture direct from Image-Buttons.
As simple and friendly as possible.
Linked gravity-sensor-delay to framerate slider to make it fast or power-saving together.
Added info and contact button linked to this thread(nothing else online yet).
Wallpaper runs fine without sdcard now. Just Cropping Image is not possible without sdcard reasonable.
- Build on Android 4.1.-, minimum required Android 2.2.
Runs Best on 4.1 with "additional features" and best stability. Settings Icons will not be visible on older Androids than 2.3.3 if I am right.
Runs on every phone and virtual device I tested. Also it runs on my TegravII Tablet on Android x86 4.0 R2 but only the 3D-Android is shown and changing Picture works but everything else not. So I will try to get it running complete on not fully compatible Android x86 later.
-Bugs: Nothing is realy broken for me. For left bugs seems just trying again makes it fine.
Loading or Cropping Pictures could still fail on bigger images or incompatible formats. I will rework the image handling a little softer to make this stable. Unfortunately Wallpaper can force close on first start in some cases.
This was next step to get everything ready for more interesting stuff.
Please send some feedback after testing.
______________________________________________________
______________________________________________________
Version 2 28.08.2012:
-New Version Build on Android 4.1.(V1 was build on Android 2.2)
-Fixed a Cropping Bug(should run more stable on most devices)
-Added Settings and Wallpaper Picker Icon, Picker can be launched after Setup
-Some Changes on loading Settings, Settings can be used before setting Wallpaper now
-This Update should fix most bugs and enable new UI in Settings!
Wallpaper Description:
Highly customizable by loading Images to interacitve Objects on fast GLES2 (OpenGL ES 2.X) Engine.
MainFeatures:
-Load any Image from Gallery to any interactive object! (supporting jpg and png with transparency)
-Load any Image cropped from Gallery to any interactive object! (supporting jpg and png without transparency)
-Fast GLES2 Engine! -Multitouch -Gravity-Sensor
-Transparency on all objects (if transparent png used)
-5 included Example Images with transparency
-Many Settings
Objects:
-Big multitouch Layer in foreground supporting G-Sensor
-Background 3D-Particles floating and rotating on Home-Screen-Shift
-High-Quality Particle System, dropping Particles from all touch-points to Gravity-Direction. Particles are rotating and random glittering when dying.
-The Bouncing Object. Elastic, downfalling, touchable, could be anything depending on the picture you select. This can get knot, you can unknot by throwing around or resetting by hiding Wallpaper(opening an app or turning display off and on will reset physics)
-The 3D-Android. Mustsee! Smooth, high Quality 3D Object with fine Mapping your Image. Rotating on Homescreen Shift and Gravity-Sensor.
Engine/App Features:
-required Android 2.2. <-> 4.1 compatible.
-Superfast GLES2 Engine on low CPU Power. Everything is displayed via optimized Shaderscripts on the GPU Buffer.
-Adjustable Framerate. Depending on Device Speed and selected Objects you can save Power by slowing down Framerate. Best result shold be about 90% with a little delay. At 100 % it will run without delay, should be no problem but not required.
-Low CPU-Power at all. Worst case with all Objects active and 100% Framerate(no delay) it consumes only about 30% CPU Power on my Evo 3D.
-Wallpaper only needs Power if visible. Propper freeing all recources and unregistering sensors if invisible.
-Settings Launcher in Notification Bar.(could be toggled in settings)
-Can be moved to sdcard in app menu
-I will implement much more (ai talking to you, more Physics, 3D-Wallpaper-Designer-App, obj-Importer,Kinect-Scan-Importer...)
Premissions:
Change/Delete External Storage. Neede to save the cropped Image.
Loading From Galery Info:
Without cropping only a link will made to load the original Image. Loading linked Image can fail! Chance to fail is higher on larger images. Also re-initialising after sucsessfull load can fail. Also speed will slow down if using big images. No Problems on smaller images, great for loading png icons with transparency. Ideal size is 512x512 Pixels (Image will be used direct as gl texture without resizing). After rebooting Device link to Image could get lost and backup tex will be loaded. Please select Image again.
By Cropping a resized 512x512 Version is saved on sdcard/jbGLESIIwallpaper/curbg.png. You can replace this Image with a transparent png for example and it should come up if you select cropped from Gallery without finishing cropping(that would overwrite the replaced)
This should work without Problems. Cropping Pictures could fail. Try again, this should bring up any jpg or png.
BUGS!!!
-Please set Wallpaper before launching Settings!!! Launching Settings before setting Wallpaper can drive you into strange Behaviours*.
-Wallpaper needs SD-Card! Wallpaper should run without sd but needs sd to start, to launch setting and to bring up custom images. If custom image is selected, wp should use backup Image and load your selected if sd is mounted again.
-Selecting Images from Gallery can fail. Please try again or try cropped.
-Selecting Images from Gallery can crash the Wallpaper or get into strange Behaviours*.
-It is only tested on my Evo [email protected], a Xperia [email protected] and some emulator images. It works on the SDK-Emulators GPU-Emulation (faster as suspected). Loading the Image as GLESII Texture needs the GPU to support the pixels format, this may fail on some devices or drivers.
-Wallpaper will start on default settings after rebooting device, setting another Wallpaper, crashing or re-installing, but your Settings are saved and will be restored if launching Settings Menu.
*strange Behaviours: waiting, staying black, force close, not opening settings, text in settings broken, asking for superuser premissions.
If you get into strange Behaviours please kill the app from app menu and try again. Everything will work fine!
a bug-free version would have not all the features yet. I am very sorry for any Problem and except everyone will be able to get it running fine.
I hope someone will have fun with it! I like it. I coded this using many open sources. It is just the beginning, to get the engine perfect with all features I want. This will be much more soon.
Downloads:
looks pretty sweet. Nice job. Will report any bugs I find.
Update Version 2 28.08.2012: Must Bugs fixed, 4.1 build
Updates:
Version 2 28.08.2012:
-New Version Build on Android 4.1.(V1 was build on Android 2.2)
-Fixed a Cropping Bug(should run more stable on most devices)
-Added Settings and Wallpaper Picker Icon, Picker can be launched after Setup
-Some Changes on loading Settings, Settings can be used before setting Wallpaper now
-This Update should fix most bugs and enable new UI in Settings!
Looks cool, gonna try
Sent from my SGH-T989 with Cyanogenmod 10 Alpha Power.
Great wallpaper! I loved it!
Sent from my PC36100 using xda premium
Da_Rock_1119 said:
Great wallpaper! I loved it!
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Happy to hear that after all that work(continued)!
Thanks for first feedback!
@All: I have an urgent project and hollydays next week so updates will be small or after that (I can edit and build project on phone, so maybe I find some time at the beach
Version 3: Can't stop touching my phone!
Updates:
Can't stop touching my phone!
BIG UPDATE Liquid Version 3 22.09.2012:
So much new stuff: New Objects, New Features, New artworks, New Settings, many Fixes and Changes, improved stability.
New Objects:
-The amazing Color Fluid Surface(including; Liquid Colors, Anti-Color, Particles, a swimming Object, Connections to other Objects, own new sub-section in Settings)
-Full Screen Image(just shifting a little with homescreen)
-New Liquid Beta-Particles (linked to the Fluid Surface to make 2 fluid physics engines connected driving each other!)
-The amazing Color Fluid Surface:
Get a realy liquid screen.
Make fine colorfull swhirls with each finger or mix the whole fluid witch all touch points.
Continuously auto-selecting the "next most-amazing color" for each touch point.
See the colors mixing transparent on any background.
Finger 4 will dropp Anti-Color, the mathematical opposite of Color. Anti-Color and Color will be colorfull neutralized against each other. Naturally Anti-Color is invisible but I found a way to show it. It´s enabled on default and will change to it´s naturally invisibility if switching to "Inverse Fluid Colors".
The Engine has it´s "own" swimming Particles and a swimming customizable Object.
Some Objects are connected to the fluid and will swimm in fluid and/or add forces to it.
The Fluid Particles are very fine and have some options, you can select an independent build-in texture to keep them look Particle-like while using any Picture on other Objects.
Fluid Surface code is great but calculated on cpu and needs power at higher fluid resolution. This needs some optimizations, I will try to move some expensive calculations to faster scripts or buffer-array-operations to make it run faster at higher resolutions. Rendering fluid is already fast.
-Static Background Picture. It´s just shifting a little with homescreen. If you select a not-transparent Picture, background will hide the 3D-Android and the 3D-Background Particles, so don't forget to disable hidden Objects to safe power.
-New Liquid Beta-Particles.
Interesting dynamic physics. Connected to Fluid Surface, if active together, engines will move each other, result will move very dynamic or chaotic.
Beta because unoptimized, slow, cpu draining, laggy touch and unstable physics could force close somtimes because moving out of bounds. But It can blast the Fluid
-New Image Artworks all supporting Transparency:
If you want to use old removed Images, you can extract the Images from old apk file.
-New Settings. Added icons to most options. Select Picture direct from Image-Buttons.
As simple and friendly as possible.
Linked gravity-sensor-delay to framerate slider to make it fast or power-saving together.
Added info and contact button linked to this thread(nothing else online yet).
Wallpaper runs fine without sdcard now. Just Cropping Image is not possible without sdcard reasonable.
- Build on Android 4.1.-, minimum required Android 2.2.
Runs Best on 4.1 with "additional features" and best stability. Settings Icons will not be visible on older Androids than 2.3.3 if I am right.
Runs on every phone and virtual device I tested. Also it runs on my TegravII Tablet on Android x86 4.0 R2 but only the 3D-Android is shown and changing Picture works but everything else not. So I will try to get it running complete on not fully compatible Android x86 later.
-Bugs: Nothing is realy broken for me. For left bugs seems just trying again makes it fine.
Loading or Cropping Pictures could still fail on bigger images or incompatible formats. I will rework the image handling a little softer to make this stable. Unfortunately Wallpaper can force close on first start in some cases.
This was next step to get everything ready for more interesting stuff.
Please send some feedback after testing.
Fix Version 4 24.09.2012: Path to not-cropped Image will be saved
Updates:
Fix Version 4 24.09.2012: Path to not-cropped Image will be saved since this version, so selected Image will come up after reboot or resetting wallpaper. If image is not avilible because sdcard is not mounted yet after reboot, backup tex will be used until sdcard is mounted. If Image is renamed or deleted, also backup tex will be used until you set another image or restore missing file.
So all Settings should work fine now.
Note: Framerate and Sensorspeed are tweaked to 100% to give you a very smooth first run, until you touch the framerate slider first time.
Version 5: HTC-Evo-3D Stereoscopic 3D Mode supported and some fixes
Version 5 25.09.2012:
-HTC-Evo-3D Stereoscopic 3D Mode supported in landscape and portrait with auto switchig orientation. Use with "Jmz 3D Switcher". 3D-Mode can be used with other Objects. It has one build-in Image yet and can load custom, pre-interlaced in devices resolution. Will add sterescopic support for 3D-Objects like the Android and loading custom obj´s. Also particles flying into your head...
-Optimized color fluid and beta-particles a little and rebalanced the connection between both so activate both and test.
-I forgot to disable multisampling on Version 4 so it is the only version with multisampling. It will not run on devices without ms. Also it looks a little better and runs a little slower. This is was only Version 4, "fixed" on Version 5...
very nice, thank so much
Update:
Version 6 25.09.2012:
HTC-Evo-3D Stereoscopic Flying Particle added in landscape and portrait
Update:
Version 7 25.09.2012:
saved some cpu-power, reworked internal framerate-and sensordelay, balanced Color Fluid Surface-Particles, fixed a bug of previous Versions not showing 3D-Andoid if active alone.
News: New HTC-evo-3D stereoscopic Version in new thread...
obj-import will work for both versions soon:
http://forum.xda-developers.com/showthread.php?t=1904203
Update: obj-import: Load any 3D mesh to wallpaper.
Update:
Version 8 07.10.2012:
loading custom obj files!
Load any 3D-Mesh to your 3D live wallpaper!
Just place "beammeup.obj" on sd root and activate loading from settings.
Try with attached exampes.
Update: V9: Performance
-Faster Rendering for all Objects
-Changed back to old fluid colors
Update: Version 13 28.10.2012: many new features
-Many new features added on htc evo 3d version
-neverending road, drag to drive
-big 3d analog clock
-timeshift-displacement lava-like shader material
-Sterescopic suport, red-green, s3d and normal mode
-...