带有WallpaperService子类的IPC

发布于 2024-12-21 01:06:56 字数 843 浏览 2 评论 0原文

我正在尝试在 Android 上制作动态壁纸。我有一个类

public class MyWallpaperService extends WallpaperService {
}

和另一个类：

public class SettingsActivity extends Activity {
}

我需要使 SettingsActivity 与 MyWallpaperService 通信，以便在动态壁纸上设置值。我之前使用过aidl，并尝试将其应用于这种情况。然而，WallpaperService 似乎具有以下方法：

/**
 * Implement to return the implementation of the internal accessibility
 * service interface.  Subclasses should not override.
 */
@Override
public final IBinder onBind(Intent intent) {
    return new IWallpaperServiceWrapper(this);
}

因此，由于超类（WallpaperService）的 onBind 方法的最终声明，我无法在服务的 onBind 方法中返回我自己的自定义 aidl 定义的绑定器。在我看来，这似乎是 Android 平台开发团队的疏忽。这是否有效地消除了任何动态壁纸中所有可能的进程间通信能力？

我在这里有什么选择？我知道我可以将活动和服务放在同一个进程中，并让活动在服务上设置全局变量，但这似乎会很快变得混乱，我想正确执行此操作。在服务中添加广播接收器是正确的做法吗？

原文

I am trying to make a live wallpaper on Android. I have one class

public class MyWallpaperService extends WallpaperService {
}

And annother class:

public class SettingsActivity extends Activity {
}

I need to make the SettingsActivity communicate with MyWallpaperService in order to set values on the live wallpaper. I have used aidl before and have tried to apply it to this situation. However it seems like WallpaperService has the following method:

/**
 * Implement to return the implementation of the internal accessibility
 * service interface.  Subclasses should not override.
 */
@Override
public final IBinder onBind(Intent intent) {
    return new IWallpaperServiceWrapper(this);
}

Therefore I cannot return my own custom aidl defined binder in the onBind method of my service due to the final declaration on the superclass, WallpaperService's, onBind method. To me this seems like an oversight by the Android platform development team. Does this effectively removes all possible inter process communication abilities from any live wallpaper?

What are my options here? I know I can put the Activity and the Service in the same process and have the Activity set global variables on the Service, but that seems like it could get messy fast and I want to do this right. Is adding a Broadcast Receiver in the Service the right move here?

分享到QQ

分享到微博