Anroid 分析：proxy模式理解Manager和Service

最新推荐文章于 2023-01-13 16:46:59 发布
原创 最新推荐文章于 2023-01-13 16:46:59 发布 · 974 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍了Android系统中Context提供的getSystemService接口如何通过ContextImpl加载一系列服务代理对象，并将这些对象存放在HashMap表中。详细解释了当用户调用服务方法时，代理对象如何将请求传递给实际的服务组件。


Android 通过 Context提供getSystemService的接口， 而是实现类是 ContextImp




ContextImpl.java 的Load时(Static)，会创建一堆 service proxy 对象，而后将其放入HashMap表中， 比如StatusBarManager


当用户调用 Service 方法的时候， Proxy 对象会将其传给真正在 ServiceManager 中注册的 Service. 表面上看就是 Manager是 Proxy对象， Service 是真正的对象.

这样的好处：
当 Service 不存在时，用户依然可以调用 Manger的接口，只是传不到Service, 基本没有任何动作而已

span76
关注
Framework层ServiceManager类的详细介绍
lvyaer_1122的博客
04-23 806
SystemManager是/frameworks/base/core/java/android/os/ServiceManager.java。该类主要与native层的SystemManager.cpp通信交互。
Android9 HWbinder使用-获取service流程解析
Deep Lee的专栏
12-30 2575
前言 接上篇Android9 HWbinder使用-注册service流程解析讲了hidl service的注册流程，这篇文章接着解析hidl service的获取流程 HwBinder框架 流程解析 废话不多说，继续以USB HAL 1.0为例，解析一下获取的流程 以vts为参考获取的代码 获取流程 1. hardware/interfaces/usb/1.0/vts/functional/VtsHalUsbV1_0TargetTest.cpp 改一下代码，以常见的不带参数为例 usb = IUsb::
红茶一杯话Binder（ServiceManager篇）
weixin_33989780的博客
08-02 326
2019独角兽企业重金招聘Python工程师标准>>> ...
ServiceManager 小结
weixin_34049948的博客
10-20 194
  1 ServiceManger 根据name优先从Map中获取IBinder，例如AMS、WMS、PMS；如果Map中没有对应的IBinder，我们获取Serviceanager的代理ServiceManagerNative.asInterface(BinderInternal.getContextObject());　　android_os_BinderInternal_getContex...
[Android]ServiceManager的客户端proxy本质是BpBinder(0)
aaajj的专栏
05-09 864
在客户端，我们通常都是使用ServiceManager的getService或者checkService方法去获取相应服务的proxy，比如dumpsys.cpp中有    sp<IServiceManager> sm =defaultServiceManager();sp<IBinder>service = sm->checkService(String16("po...
ServiceManager
iffy
03-06 198
java层 BinderProxy---ServiceManagerProxy为ServiceManagerNative的内部类 java层 Binder-----ServiceManagerNative Native层--bpBinder BpServiceManager Navtive层 bnServicemanager ...
Android AMS: New_Task流程解析与ActivityManagerService关键点
当flag设置为New_Task时，涉及到的是Android应用程序管理和生命周期控制的核心组件——ActivityManagerService (AMS)。在Android系统中，AMS是一个关键的服务，它负责整个系统的活动管理，包括Activity、Service、...
11-21 20:49:50.147 4762 30319 E AndroidRuntime: FATAL EXCEPTION: IpClient.wlan0 11-21 20:49:50.147 4762 30319 E AndroidRuntime: Process: com.android.networkstack.process, PID: 4762 11-21 20:49:50.147 4762 30319 E AndroidRuntime: java.lang.IllegalArgumentException: Wakelock.mLock is already dead. 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:3374) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:3354) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3337) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3279) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.IPowerManager$Stub$Proxy.acquireWakeLock(IPowerManager.java:1471) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.PowerManager$WakeLock.acquireLocked(PowerManager.java:4194) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.PowerManager$WakeLock.acquire(PowerManager.java:4175) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.android.net.ip.IpReachabilityMonitor$Dependencies$1.acquireWakeLock(IpReachabilityMonitor.java:198) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.android.net.ip.IpReachabilityMonitor.probeAll(IpReachabilityMonitor.java:572) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.android.net.ip.IpClient.handleUpdateL2Information(IpClient.java:2845) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.android.net.ip.IpClient.-$$Nest$mhandleUpdateL2Information(IpClient.java:0) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.android.net.ip.IpClient$StartedState.processMessage(IpClient.java:3388) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:1002) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.networkstack.com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:820) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:115) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:298) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.Looper.loop(Looper.java:408) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:85) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace: 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.server.power.PowerManagerService$WakeLock.linkToDeath(PowerManagerService.java:6302) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.server.power.PowerManagerService$WakeLock.<init>(PowerManagerService.java:6289) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.server.power.PowerManagerService.acquireWakeLockInternal(PowerManagerService.java:1890) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.server.power.PowerManagerService.-$$Nest$macquireWakeLockInternal(Unknown Source:0) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: at com.android.server.power.PowerManagerService$BinderService.acquireWakeLock(PowerManagerService.java:6785) 11-21 20:49:50.147 4762 30319 E AndroidRuntime: 11-21 20:49:50.663 1715 1715 D AndroidRuntime: Shutting down VM 11-21 20:49:50.664 1715 1715 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main 11-21 20:49:50.664 1715 1715 E AndroidRuntime: java.lang.IllegalStateException: Lost network stack. This is not the root cause of any issue, it is a side effect of a crash that happened earlier. Earlier logs should point to the actual issue. 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.net.ConnectivityModuleConnector.maybeCrashWithTerribleFailure(ConnectivityModuleConnector.java:336) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.net.ConnectivityModuleConnector.-$$Nest$mmaybeCrashWithTerribleFailure(Unknown Source:0) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.net.ConnectivityModuleConnector$ModuleServiceConnection.onServiceDisconnected(ConnectivityModuleConnector.java:279) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.app.LoadedApk$ServiceDispatcher.doDeath(LoadedApk.java:2473) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:2488) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:1027) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:108) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:298) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at android.os.Looper.loop(Looper.java:408) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:1139) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:709) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:613) 11-21 20:49:50.664 1715 1715 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1052)
最新发布
11-25
首先，用户的问题是：查找解决Android系统中出现的java.lang.IllegalArgumentException: Wakelock.mLock is already dead和java.lang.IllegalStateException: Lost network stack错误的方法。 我需要基于提供的引用...
06-05 06:24:05.669 5900 5900 D AndroidRuntime: Shutting down VM 06-05 06:24:05.672 5900 5900 E AndroidRuntime: FATAL EXCEPTION: main 06-05 06:24:05.672 5900 5900 E AndroidRuntime: Process: com.avatr.cockpit.settings, PID: 5900 06-05 06:24:05.672 5900 5900 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.avatr.cockpit.settings.CockpitSettingsApplication: java.lang.SecurityException: Permission Denial: Component com.avatr.cockpit.settings/.service.SettingsService requests FLAG_SINGLE_USER, but app does not hold android.permission.INTERACT_ACROSS_USERS 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7107) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2305) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:218) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.os.Looper.loop(Looper.java:307) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8309) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:573) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1049) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: Caused by: java.lang.SecurityException: Permission Denial: Component com.avatr.cockpit.settings/.service.SettingsService requests FLAG_SINGLE_USER, but app does not hold android.permission.INTERACT_ACROSS_USERS 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:3079) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:3063) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3046) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2988) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.app.IActivityManager$Stub$Proxy.startService(IActivityManager.java:6047) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1931) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.app.ContextImpl.startService(ContextImpl.java:1900) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.content.ContextWrapper.startService(ContextWrapper.java:825) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at com.avatr.cockpit.settings.CockpitSettingsApplication.onCreate(CockpitSettingsApplication.java:20) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1316) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7102) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: ... 9 more 06-05 06:24:05.672 5900 5900 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace: 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at com.android.server.am.ActivityManagerService.isSingleton(ActivityManagerService.java:13546) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at com.android.server.am.ActiveServices.retrieveServiceLocked(ActiveServices.java:4394) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at com.android.server.am.ActiveServices.startServiceLocked(ActiveServices.java:833) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at com.android.server.am.ActiveServices.startServiceLocked(ActiveServices.java:794) 06-05 06:24:05.672 5900 5900 E AndroidRuntime: at com.android.server.am.ActivityManagerService.startService(ActivityManagerService.java:13415) 06-05 06:24:05.672 5900 5900 E AndroidRuntime:
06-07
2.什么是Android的多用户（Multi-User）模式？3.如何正确使用自定义Application类？4.Android系统权限和普通权限有何区别？5.如何解决方法重名导致的冲突问题？ ### 解决 Android 应用因缺少 INTERACT_ACROSS_USERS ...
08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: FATAL EXCEPTION: main 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: Process: com.android.nfc, PID: 3025 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.android.nfc.NfcApplication: java.lang.SecurityException: com.android.nfc: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:8381) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2700) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:249) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.os.Looper.loop(Looper.java:337) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:9626) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:648) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1005) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: Caused by: java.lang.SecurityException: com.android.nfc: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:3256) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:3240) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3223) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3165) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.IActivityManager$Stub$Proxy.registerReceiverWithFeature(IActivityManager.java:6559) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1915) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.ContextImpl.registerReceiverAsUser(ContextImpl.java:1883) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.content.ContextWrapper.registerReceiverAsUser(ContextWrapper.java:843) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at com.android.nfc.NfcService$PollConfig.<init>(NfcService.java:8431) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at com.android.nfc.NfcService.<init>(NfcService.java:1342) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at com.android.nfc.NfcApplication.onCreate(NfcApplication.java:63) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1392) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:8373) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: ... 9 more 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace: 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at com.android.server.am.ActivityManagerService.registerReceiverWithFeatureTraced(ActivityManagerService.java:15970) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at com.android.server.am.ActivityManagerService.registerReceiverWithFeature(ActivityManagerService.java:15766) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.IActivityManager$Stub.onTransact$registerReceiverWithFeature$(IActivityManager.java:13187) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:3426) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime: at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3113) 08-16 13:46:41.971 nfc 3025 3025 E AndroidRuntime:
08-17
注意：`Context.RECEIVER_EXPORTED`和`Context.RECEIVER_NOT_EXPORTED`是在Android 13（API 33）中引入的，但强制要求是在Android 14（API 34）中。因此，在Android 13中，你可以设置这些标志，但在13以下会忽略。在...
ServiceManager远程代理的获取
启程
10-21 762
ServiceManager管理着系统中所有的服务，无论是service 还是client只要跟系统中的服务打交道，必先获取ServiceManager的代理，才能获取ServiceManager提供的各项服务。在安卓系统中Service Manager远程代理是一个特殊的Binder引用，它的引用句柄一定是0。获取远程代理的方法defaultServiceManager()的实现在framewor
ServiceManage分析
d_o_n_g2的博客
09-16 316
我们注册系统初始化的时候，会注册service到ServiceManager，那么我们从源码的角度分析addService和getService到底发生了什么？ServiceManager 本身的方法并不多，代码行数也简单。 /** @hide */ public final class ServiceManager { private static final String TAG = "ServiceManager"; private static IServiceManager sS
ServiceManager分析
kaixinbingju的专栏
04-24 4149
Service Manager 的工作就是登记功能。服务通过add_service方法将自己的名字和Binder 标识handle 登记在svclist 中。而服务请求者，通过check_service方法，通过服务名字在service list 中获取到service 相关联的Binder 的标识handle,通过这个Handle 作为请求包的目标地址发起请求。 通讯：IPC。Andr
Binder学习[3]: ServiceManger.getService 实现
大将军王虎剩的专栏
12-04 2446
本文主要从分析 Java层 getService是怎么实现的，getService最终的返回值是什么，以及怎么使用的。 1.ServiceManager.getService 从Am.java的 onRun函数开始： @Override public void onRun() throws Exception { mAm = ActivityManager....
Android笔记 - Binder之servicemanager代理对象
yansha的专栏
01-30 1238
1. 前言上一篇文章解答了关于 servicemanager 的三个问题，其中讲到 servicemanager 作为一个特殊的 Service 组件，既负责为系统中其他的 Service 组件提供注册服务，同时又负责为 Client 组件提供获取 Service 组件代理对象的服务。那么 Service 组件和 Client 组件如何才能使用到 servicemanager 提供的服务呢？
ServiceManagerProxy中mRemote变量指的什么？
转载和创作优秀的博客
12-02 246
首先标红的代码Binder.allowBlocking(BinderInternal.getContextObject())，实际上返回的是BinderProxy对象实例 sServiceManager = ServiceManagerNative .asInterface(Binder.allowBlocking(BinderInternal.getContextObject())); static public IServiceManager asInterfa...
图解ServiceManager的获取服务过程(上)
handy周
02-01 3324
网上有很多关于ServiceManager和Binder的文章，但是老感觉理解起来不是那么顺畅，笔者基于Android 8.1系统源代码，从最简单的获取服务开始了解Binder进程间通信，由于篇幅原因，这里分开两部分来了解，上部分主要集中在Java层，下部分主要集中在Native层。
（五）Binder分析·下篇
qq_33427070的博客
01-13 285
通过一个BinderDemo例子，学习binder在java层的使用。
【Service】ServiceManager.getService流程总结
明朗晨光的专栏
09-14 8769
参考《深入理解Android内核设计思想》（第2版），对ServiceManager.getService流程分析过程中的一些总结进行记录备忘： ServiceManagerProxy 当某个Binder Server在启动时，会把自己的名称name与对应的Binder句柄值保存在ServiceManager中。调用者通常只知道Binder Server的名称，所以必须先向Se...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值