Uni2Lwp is an Unity extension that allows you to create Android 3D live wallpapers with Unity 3.4.2 and 3.5.7 and 4.0/4.0.1!
Support:
If you are having any issues please check the FAQ and Tutorials page.
Haven’t found your answer ? Then contact here or use the site’s Contact form.
->Extract GoogleAdMobAdsSdk-x.x.x.jar into your Live Wallpaper libs folder;*
OR Locate AdMob Jar file directly from Uni2LwP create live wallpaper window;[/COLOR]
Deprecated*. On August 1, 2014, Google Play will stop accepting new or updated apps that use the old standalone Google Mobile Ads SDK v6.4.1 or lower.
Tutorial: “How to upgrade from the old Admob ads to the new Google Play Ads”. Please contact me to get the tutorial.*
Change live wallpaper name and description inside Uni2LwP window;
Player Settings icons are automatically copied to the live wallpaper drawable folders;
Uni2LwP works with OpenGL ES 1.x and 2.0;
App2SD (Option);
Option to create a Toast message that hides the “Settings” and “Set Live Wallpaper” buttons when the LWP is loading (although hidden the user can still press the buttons);
Media volume is now disabled for Unity 3.4.2, 3.5.7 and 4.0.1; If you want to use sounds on your live wallpapers just comment this line renderer.PauseMediaVolume(“unity version″); that’s inside the onVisibilityChanged method.
Minimum requirements:*
Works with Unity 3.4.2/3.5.7/4.0/4.0.1 Free and Pro;
Minimum API level is Android 2.2 ‘Froyo’;
Known issues:*
Doesn’t work with Unity 4.1+ / 4.2+ / 4.3+ / 5+ (Only works with Unity 4.0 and 4.0.1)
Live wallpaper restarts if you try to set it twice or access the settings menu after the lwp is already set. This means that after the live wallpaper is set (running in your home screen) you must access the settings menu using the double tap feature or else it will restart.
Updated info: Google changed this with Android 4.4.2 and it no longer restarts. The user will have to manually set the live wallpaper again.*
As you have said, there would be a lot of people using Unity 3.5 /4 who would ask for it. For $30 - $40 I would happily shell out the cash if Unity 4 were supported but I couldn’t justify the price tag on a chance that it might work. The wallpaper would also need to be able to interface with scripts (like moving the camera when the user slides to a new screen).
It already supports everything that a normal Android live wallpaper needs. I will include a demo live wallpaper that demonstrates how to interface with scripts (like home switch and saving/loading user settings inside android LWP settings activity).
I think the price can be lower to let people have more review first. 20 dollars would be reasonable to me. I use another plugin call unity2eclipse. However, after I edited the setting I created in the LWP. The phone’s screen turns black. If I change to another LWP and go back to my own LWP. The LWP works on my phone’s background again. Is there any guaranteed your plugin would not have this issue? If this is solved, I would buy one.
I have read that unity2eclipse uses partially developed classes by Unity and that is why everyone that builds live wallpapers with it has some problems (the developed does say it’s experimental).
My plugin does not rely on any developed class by Unity. It’s build from scratch and as far as I have tested it doesn’t have that particularly issue.
Maybe I’ll need to get 3.4 specifically for publishing live wallpapers. If your library can be updated to support newer versions of Unity, you should do it, though. It’s an untapped resource, since the closest alternative is Unity2Eclipse and I hear that it’s a bit sketchy.
As far as I know, the closest Unity has come to officially supporting live wallpapers is a statement that they might consider it in the future. But that was two years ago.
3.4 included a specific library in the jar file or something like that, which allows unity to run as a live wallpaper, but is only compatible with that version of unity (and is really buggy). That’s how the unity2eclipse works is by building off of that jar file’s library, or something to that effect.
If it’s not using this specific jar library/class then I don’t see why it should be locked to a specific version of unity. If it is a custom wrote class, there is no reason why it should only work for 3.4
As it is (only working with Unity 3.4.x) I could release it tomorrow. However, I’m not going to release it just yet. Why? Well, because in the last 3 days I have been working on it and I have some good news
My plugin now works with Unity 3.5 but only using developed build and disabling Dynamic Batching.
So, please be patient. I’m now convinced that Uni2LWP WILL work on Unity3.5 and probably on Unity4.0 (Haven’t tested it though).
