Live Wallpaper not Showing up on Market for Moto Droid w/ OTA 2.1

by Yakloin » Thu, 22 Apr 2010 05:27:07 GMT

Sponsored Links
 I am pulling out my hair trying to figure out what to do to get my
Live Wallpaper to show up on the Android Market for a Moto Droid with
the 2.1 OTA update.  It shows up and downloads just fine on Nexus One.

I can only think that it has something to do with the
AndroidManifest.xml file contents.  I tried all combinations for
<supports-screens> including not having it at all.  I tried including/
excluding the <uses-feature
android:name="" />.

I don't like releasing my app over and over trying to debug this.
Please help out if you can.

Here is the file for reference (in it's current state):
<?xml version="1.0" encoding="utf-8"?>
    xmlns:android="" ;


            <intent-filter android:priority="1">
android:name="android.service.wallpaper.WallpaperService" />
                android:resource="@xml/main" />

            android:exported="true" />


    <uses-sdk android:minSdkVersion="7" />
    <uses-permission android:name="android.permission.VIBRATE" />



Other Threads

1. Help, HH ga bisa di root

Bro, sampeyan pake rom eclair built terbaru (2.0.2.A.0.24) ya?
Rom built ini memang belum bisa di root dengan semua metode rooting yg
berhasil di rom built sebelumnya.
Untuk bisa root di built ini, mesti downgrade ke built sebelumnya (rooted)
trus install xrecovery dan flash pre rooted rom built 2.0.2.A.0.24.
Tutorial lengkapnya ada di

2011/1/18 Ichtiardo Wanto <>


2. Proper Exception Handling

Coming over from other languages/platforms, and just trying to get my
head around the proper way to handle Exceptions in Android (or at a
minimum, some advice/links on this topic).

Have an app that in various activities handles any number of types of
Exceptions, such as IOException, FileNotFoundException, SAXException,
etc. In some cases, I want an exception to terminate the called
Activity and alert the user of an error, in others, I can handle the
Exception more gracefully, if appropriate. So I guess the question is,
is it a good strategy to create a custom app-specific Exception class
that I can then re-throw specific Exceptions from, such that I only
have to listen for that specific exception in try/catch blocks further
up the chain, rather than listening for a bunch of different ones?

A very basic question, but want to make sure I get off on the right



3. [WTA] saran pengen beli hape android

4. glHint implementation and openGL antialiasing

5. change color of Button

6. Setting up development environment on windows 7

7. XL unlimited