Note that there are some explanatory texts on larger screens.

plurals
  1. POAny way to respond to Android users' force close messages?
    text
    copied!<p>I've published an Android live wallpaper for which I have recently started to get this strange force close error:</p> <pre><code>java.lang.RuntimeException: Failed to register input channel. Check logs for details. at android.view.InputQueue.nativeRegisterInputChannel(Native Method) at android.view.InputQueue.registerInputChannel(InputQueue.java:92) at android.service.wallpaper.WallpaperService$Engine.updateSurface(WallpaperService.java:521) at android.service.wallpaper.WallpaperService$Engine.attach(WallpaperService.java:651) at android.service.wallpaper.WallpaperService$IWallpaperEngineWrapper.executeMessage(WallpaperService.java:875) at com.android.internal.os.HandlerCaller$MyHandler.handleMessage(HandlerCaller.java:61) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:130) at android.app.ActivityThread.main(ActivityThread.java:3683) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:507) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597) at dalvik.system.NativeStart.main(Native Method) </code></pre> <p>According to this StackOverflow <a href="https://stackoverflow.com/questions/5768857/weird-exception-when-livewallpaper-is-set-in-android">page</a> the issue might be with Launcher Pro.</p> <p>I want to avoid getting bad ratings for this. Is there any way to communicate with the users who send me this error report that it is not the fault of my program, and that they should run the wallpaper through their normal home screen?</p> <p>I could post a note on the app's Android Market page, but that would seem to be a major distraction for an infrequent error.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload