Android下SF合成流程重学习之Refresh流程

2024-02-19 06:36
文章标签 android 流程 学习 合成 sf refresh

本文主要是介绍Android下SF合成流程重学习之Refresh流程，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

        Android下SF合成流程重学习之Refresh流程



引言

在前面初步分析完成了Android下SF合成流程重学习之Invalidate流程，我们接下来继续下面的分析。当有事务的更新或者有Buffer的更新便会触发后面刷新的流程,即Refresh流程！



一. onMessageRefresh

文件：frameworks/native/services/surfaceflinger/Surfaceflinger.cpp
void SurfaceFlinger::onMessageRefresh() {ATRACE_CALL();mRefreshPending = false;//这里的主要逻辑是搜集需要送显的layer的情况，封装成compositionengine::CompositionRefreshArgs参数传递//给CompositionEngine做进一步操作compositionengine::CompositionRefreshArgs refreshArgs;const auto& displays = ON_MAIN_THREAD(mDisplays);// display 的数量，把当前displaydevice 记录下来refreshArgs.outputs.reserve(displays.size());for (const auto& [_, display] : displays) {refreshArgs.outputs.push_back(display->getCompositionDisplay());}// 把当前layer记录下来mDrawingState.traverseInZOrder([&refreshArgs](Layer* layer) {if (auto layerFE = layer->getCompositionEngineLayerFE())refreshArgs.layers.push_back(layerFE);});// 把当前有queueframe的layer记录下来, 有Buffer的layerrefreshArgs.layersWithQueuedFrames.reserve(mLayersWithQueuedFrames.size());for (sp<Layer> layer : mLayersWithQueuedFrames) {if (auto layerFE = layer->getCompositionEngineLayerFE())refreshArgs.layersWithQueuedFrames.push_back(layerFE);}...// 主要逻辑在present里面mCompositionEngine->present(refreshArgs);}

前面主要搜集需要送显的layer的情况，封装成compositionengine::CompositionRefreshArgs参数传递给CompositionEngine做进一步操作。并且最最主要合成及调用Hal composer送显的逻辑都在在present里面了。



二. CompositionEngine::present

文件：frameworks/native/services/surfaceflinger/CompositionEngine/src/CompositionEngine.cppvoid CompositionEngine::present(CompositionRefreshArgs& args) {ATRACE_CALL();ALOGV(__FUNCTION__);// 根据是否还有layer没有消费掉，判断再调起一次刷新preComposition(args);{// latchedLayers is used to track the set of front-end layer state that// has been latched across all outputs for the prepare step, and is not// needed for anything else.LayerFESet latchedLayers;for (const auto& output : args.outputs) {// 计算各个区域大小以及创建hwc layeroutput->prepare(args, latchedLayers);}}// 更新layerCompositionStateupdateLayerStateFromFE(args);for (const auto& output : args.outputs) {// 逻辑在output.cpp的present里面output->present(args);}
}

2.1 preComposition

在这里插入图片描述

void CompositionEngine::preComposition(CompositionRefreshArgs& args) {ATRACE_CALL();ALOGV(__FUNCTION__);bool needsAnotherUpdate = false;mRefreshStartTime = systemTime(SYSTEM_TIME_MONOTONIC);//调用了layer->onPreComposition做composition前的准备。进去看没做啥实际操作for (auto& layer : args.layers) {if (layer->onPreComposition(mRefreshStartTime)) {needsAnotherUpdate = true;}}mNeedsAnotherUpdate = needsAnotherUpdate;
}

其主要逻辑就是调用了layer->onPreComposition做composition前的准备。进去看没做啥实际操作。


2.2 Output::prepare

在这里插入图片描述

prepare主要的作用是收集可见的Layers并计算各个区域大小以及创建hwc layer！

//frameworks/native/services/surfaceflinger/CompositionEngine/src/Output.cpp
void Output::prepare(const compositionengine::CompositionRefreshArgs& refreshArgs,LayerFESet& geomSnapshots) {...rebuildLayerStacks(refreshArgs, geomSnapshots);
}void Output::rebuildLayerStacks(const compositionengine::CompositionRefreshArgs& refreshArgs,LayerFESet& layerFESet) {...// Process the layers to determine visibility and coveragecompositionengine::Output::CoverageState coverage{layerFESet};collectVisibleLayers(refreshArgs, coverage);...
}void Output::collectVisibleLayers(const compositionengine::CompositionRefreshArgs& refreshArgs,compositionengine::Output::CoverageState& coverage) {...for (auto layer : reversed(refreshArgs.layers)) {// Incrementally process the coverage for each layerensureOutputLayerIfVisible(layer, coverage);// TODO(b/121291683): Stop early if the output is completely covered and// no more layers could even be visible underneath the ones on top.}...
}

其主要逻辑在ensureOutputLayerIfVisible里面。

2.3 ensureOutputLayerIfVisible

文件：frameworks/native/services/surfaceflinger/CompositionEngine/src/Output.cppvoid Output::ensureOutputLayerIfVisible(sp<compositionengine::LayerFE>& layerFE,compositionengine::Output::CoverageState& coverage) {....// 创建OutputLayerauto result = ensureOutputLayer(prevOutputLayerIndex, layerFE);...}

各个layer区域的计算结果可以通过adb shell dumpsys SurfaceFlinger看到，通过区域的计算把区域为空的layer过滤掉.

区域

ensureOutputLayer将创建Output layer，这些layer最后是要显示到屏幕上的

文件: frameworks/native/services/surfaceflinger/CompositionEngine/include/compositionengine/impl/Output.hOutputLayer* ensureOutputLayer(std::optional<size_t> prevIndex,const sp<LayerFE>& layerFE) {// 判断当前的outputlayer 集合里面有没有当前的layer，如果没有则新创建一个auto outputLayer = (prevIndex && *prevIndex <= mCurrentOutputLayersOrderedByZ.size())? std::move(mCurrentOutputLayersOrderedByZ[*prevIndex]): BaseOutput::createOutputLayer(layerFE);auto result = outputLayer.get();mPendingOutputLayersOrderedByZ.emplace_back(std::move(outputLayer));return result;}文件：frameworks/native/services/surfaceflinger/CompositionEngine/src/Display.cppstd::unique_ptr<compositionengine::OutputLayer> Display::createOutputLayer(const sp<compositionengine::LayerFE>& layerFE) const {auto result = impl::createOutputLayer(*this, layerFE);if (result && mId) {auto& hwc = getCompositionEngine().getHwComposer();auto displayId = *mId;// 创建hwclayerauto hwcLayer = std::shared_ptr<HWC2::Layer>(hwc.createLayer(displayId),[&hwc, displayId](HWC2::Layer* layer) {hwc.destroyLayer(displayId, layer);});ALOGE_IF(!hwcLayer, "Failed to create a HWC layer for a HWC supported display %s",getName().c_str());// 更新state.hwcresult->setHwcLayer(std::move(hwcLayer));}return result;
}

可以看到prepare主要的作用是遍历layer计算各个区域大小，过滤掉空区域的layer以及创建hwc layer。


2.4 updateLayerStateFromFE

在这里插入图片描述

它的核心逻辑是跟新更新OutputlayerState的参数，即layer的状态信息


文件：frameworks/native/services/surfaceflinger/Layer.cppvoid Layer::prepareCompositionState(compositionengine::LayerFE::StateSubset subset) {using StateSubset = compositionengine::LayerFE::StateSubset;switch (subset) {case StateSubset::BasicGeometry:prepareBasicGeometryCompositionState();break;case StateSubset::GeometryAndContent:prepareBasicGeometryCompositionState();prepareGeometryCompositionState();preparePerFrameCompositionState();break;case StateSubset::Content:preparePerFrameCompositionState();break;case StateSubset::Cursor:prepareCursorCompositionState();break;}
}C++
文件：frameworks/native/services/surfaceflinger/Layer.cppvoid Layer::prepareCompositionState(compositionengine::LayerFE::StateSubset subset) {using StateSubset = compositionengine::LayerFE::StateSubset;switch (subset) {case StateSubset::BasicGeometry:prepareBasicGeometryCompositionState();break;case StateSubset::GeometryAndContent:prepareBasicGeometryCompositionState();prepareGeometryCompositionState();preparePerFrameCompositionState();break;case StateSubset::Content:preparePerFrameCompositionState();break;case StateSubset::Cursor:prepareCursorCompositionState();break;}
}

这部分也可以通过adb shell dumpsys SurfaceFlinger看出来有哪些属性。

image



三. Output::present

如果说前面的都是洒洒水，开胃菜。那么从这里开始就是大餐了。

文件：frameworks/native/services/surfaceflinger/CompositionEngine/src/Output.cppvoid Output::present(const compositionengine::CompositionRefreshArgs& refreshArgs) {ATRACE_CALL();ALOGV(__FUNCTION__);//设置 Display的dataspace, colormodeupdateColorProfile(refreshArgs);// 设置outputlayer的dispFrame和sourceCrop等以及将outputlayer属性设给hwcupdateAndWriteCompositionState(refreshArgs);// 设置display的颜色矩阵，对全屏有效setColorTransform(refreshArgs);// FrameBuffer里面没做啥操作beginFrame();// 选择合成策略，判断是device还是GPU合成，如果是device合成，直接present，如果要走GPU合成则需要validateprepareFrame();// 一般不走devOptRepaintFlash(refreshArgs);// GPU合成主要逻辑在此，device合成没做啥finishFrame(refreshArgs);// device合成设置release fence，GPU合成需要present给hwcpostFramebuffer();
}

先关注device合成，涉及GPU部分单独分析(简单带过)！


3.1 updateAndWriteCompositionState


文件：frameworks/native/services/surfaceflinger/CompositionEngine/src/Output.cppvoid Output::updateAndWriteCompositionState(const compositionengine::CompositionRefreshArgs& refreshArgs) {ATRACE_CALL();ALOGV(__FUNCTION__);if (!getState().isEnabled) {return;}mLayerRequestingBackgroundBlur = findLayerRequestingBackgroundComposition();// 如果是有背景模糊的layer则强制使用GPU合成bool forceClientComposition = mLayerRequestingBackgroundBlur != nullptr;for (auto* layer : getOutputLayersOrderedByZ()) {// 遍历outputlayer，计算DisplayFrame， SourceCrop 等参数layer->updateCompositionState(refreshArgs.updatingGeometryThisFrame,refreshArgs.devOptForceClientComposition ||forceClientComposition,refreshArgs.internalDisplayRotationFlags);if (mLayerRequestingBackgroundBlur == layer) {forceClientComposition = false;}// 将layer属性设给hwclayer->writeStateToHWC(refreshArgs.updatingGeometryThisFrame);}

这部分参数也可以通过adb shell dumpsys SurfaceFlinger看到：

屏幕显示区域.png



3.2 setColorTransform

文件：frameworks/native/services/surfaceflinger/CompositionEngine/src/Display.cppvoid Display::setColorTransform(const compositionengine::CompositionRefreshArgs& args) {Output::setColorTransform(args);if (!mId || CC_LIKELY(!args.colorTransformMatrix)) {return;}auto& hwc = getCompositionEngine().getHwComposer();// 将上层设的colorTransformMatrix 设给hwc，这个效果作用于全屏，比如护眼模式下，改变的就是这个colorTransformMatrixstatus_t result = hwc.setColorTransform(*mId, *args.colorTransformMatrix);ALOGE_IF(result != NO_ERROR, "Failed to set color transform on display \"%s\": %d",mId ? to_string(*mId).c_str() : "", result);
}

setColorTransform 设置颜色矩阵给屏幕，作用于屏幕显示，所有的layer都受影响，护眼效果就是改变的这个值。


3.3 beginFrame

在这里插入图片描述

最终调用到FramebufferSurface，并没有执行具体的逻辑:

//frameworks/native/services/surfaceflinger/DisplayHardware/FramebufferSurface.cpp
status_t FramebufferSurface::beginFrame(bool /*mustRecompose*/) {return NO_ERROR;
}

3.4 prepareFrame

在这里插入图片描述

它的核心逻辑是选择合成策略，判断是device还是GPU合成，如果是device合成，直接present，如果要走GPU合成则需要validate。让我们通过代码具体分析:

文件：frameworks/native/services/surfaceflinger/CompositionEngine/src/Output.cppvoid Output::prepareFrame() {...const auto& outputState = getState();if (!outputState.isEnabled) {return;}// 选择合成类型，如果是device合成，则跳过validate，直接present送显chooseCompositionStrategy();// 把合成类型送到frameBufferSurface，没啥逻辑mRenderSurface->prepareFrame(outputState.usesClientComposition,outputState.usesDeviceComposition);
}void Output::chooseCompositionStrategy() {// The base output implementation can only do client composition// 默认使用GPU合成,针对没有hwc的设备auto& outputState = editState();outputState.usesClientComposition = true;outputState.usesDeviceComposition = false;outputState.reusedClientComposition = false;
}文件：frameworks/native/services/surfaceflinger/CompositionEngine/src/Display.cppvoid Display::chooseCompositionStrategy() {...// Default to the base settings -- client composition only.Output::chooseCompositionStrategy();...// Get any composition changes requested by the HWC device, and apply them.std::optional<android::HWComposer::DeviceRequestedChanges> changes;auto& hwc = getCompositionEngine().getHwComposer();// 从HWC device获得合成类型的改变，这个根据hwc能力来选择device还是GPU合成if (status_t result = hwc.getDeviceCompositionChanges(*mId, anyLayersRequireClientComposition(),&changes);result != NO_ERROR) {ALOGE("chooseCompositionStrategy failed for %s: %d (%s)", getName().c_str(), result,strerror(-result));return;}//如果有变化则设置给对应的layerif (changes) {applyChangedTypesToLayers(changes->changedTypes);applyDisplayRequests(changes->displayRequests);applyLayerRequestsToLayers(changes->layerRequests);applyClientTargetRequests(changes->clientTargetProperty);}// Determine what type of composition we are doing from the final state// 决定最后的合成类型auto& state = editState();state.usesClientComposition = anyLayersRequireClientComposition();state.usesDeviceComposition = !allLayersRequireClientComposition();
}文件：frameworks/native/services/surfaceflinger/DisplayHardware/HWComposer.cppstatus_t HWComposer::getDeviceCompositionChanges(DisplayId displayId, bool frameUsesClientComposition,std::optional<android::HWComposer::DeviceRequestedChanges>* outChanges) {...if (!frameUsesClientComposition) {sp<Fence> outPresentFence;uint32_t state = UINT32_MAX;// 如果所有的layer都能走device合成，则在hwc里面直接present，若有不支持device合成的情况，则走GPU合成，会走validate逻辑error = hwcDisplay->presentOrValidate(&numTypes, &numRequests, &outPresentFence , &state);if (!hasChangesError(error)) {RETURN_IF_HWC_ERROR_FOR("presentOrValidate", error, displayId, UNKNOWN_ERROR);}if (state == 1) { //Present Succeeded.// present成功，数据直接提交给了hwcstd::unordered_map<HWC2::Layer*, sp<Fence>> releaseFences;error = hwcDisplay->getReleaseFences(&releaseFences);displayData.releaseFences = std::move(releaseFences);displayData.lastPresentFence = outPresentFence;displayData.validateWasSkipped = true;displayData.presentError = error;return NO_ERROR;}// Present failed but Validate ran.} else {// 这个分支走不到error = hwcDisplay->validate(&numTypes, &numRequests);}// 接收hwc过来的change，对于device合成不走，GPU合成走的逻辑，这个后续GPU合成专门分析...

prepareFrame 的作用是根据hwc的能力选择合成方式，如果是device合成则直接走hwc present上屏，如果是GPU合成后面则走hwc validate，然后根据hwc过来的变化改变layer的合成方式。用另外一种方式表达就是首先将合成策略给HWC看是否接受，然后如果有变化就将变化应用于layer


3. 5 Output::finishFrame

文件： frameworks/native/services/surfaceflinger/CompositionEngine/src/Output.cppvoid Output::finishFrame(const compositionengine::CompositionRefreshArgs& refreshArgs) {ATRACE_CALL();ALOGV(__FUNCTION__);if (!getState().isEnabled) {return;}// Repaint the framebuffer (if needed), getting the optional fence for when// the composition completes.// 主要针对GPU合成的逻辑auto optReadyFence = composeSurfaces(Region::INVALID_REGION, refreshArgs);// device合成直接returnif (!optReadyFence) {return;}// swap buffers (presentation)mRenderSurface->queueBuffer(std::move(*optReadyFence));
}

composeSurface的主要核心逻辑是针对GPU合成，对于device合成，则直接return了。


3.6 Output::postFramebuffer

在这里插入图片描述

这块的核心逻辑主要是对于device合成设置release fence，GPU合成需要present给hwc。我们通过代码来看下:

文件：frameworks/native/services/surfaceflinger/CompositionEngine/src/Output.cppvoid Output::postFramebuffer() {...// device合成获取release fenceauto frame = presentAndGetFrameFences();mRenderSurface->onPresentDisplayCompleted();for (auto* layer : getOutputLayersOrderedByZ()) {sp<Fence> releaseFence = Fence::NO_FENCE;if (auto hwcLayer = layer->getHwcLayer()) {if (auto f = frame.layerFences.find(hwcLayer); f != frame.layerFences.end()) {releaseFence = f->second;}}if (outputState.usesClientComposition) {releaseFence =Fence::merge("LayerRelease", releaseFence, frame.clientTargetAcquireFence);}// 将releasefence放到mslot里面，这个是dequeueBuffer等的fencelayer->getLayerFE().onLayerDisplayed(releaseFence);}
...
}文件：frameworks/native/services/surfaceflinger/DisplayHardware/HWComposer.cppstatus_t HWComposer::presentAndGetReleaseFences(DisplayId displayId) {ATRACE_CALL();RETURN_IF_INVALID_DISPLAY(displayId, BAD_INDEX);auto& displayData = mDisplayData[displayId];auto& hwcDisplay = displayData.hwcDisplay;// device合成直接returnif (displayData.validateWasSkipped) {// explicitly flush all pending commandsauto error = static_cast<hal::Error>(mComposer->executeCommands()); RETURN_IF_HWC_ERROR_FOR("executeCommands", error, displayId, UNKNOWN_ERROR);RETURN_IF_HWC_ERROR_FOR("present", displayData.presentError, displayId, UNKNOWN_ERROR);return NO_ERROR;}//GPU 合成走presentauto error = hwcDisplay->present(&displayData.lastPresentFence);RETURN_IF_HWC_ERROR_FOR("present", error, displayId, UNKNOWN_ERROR);std::unordered_map<HWC2::Layer*, sp<Fence>> releaseFences;error = hwcDisplay->getReleaseFences(&releaseFences);RETURN_IF_HWC_ERROR_FOR("getReleaseFences", error, displayId, UNKNOWN_ERROR);displayData.releaseFences = std::move(releaseFences);return NO_ERROR;
}

3.6 postComposition

文件： frameworks/native/services/surfaceflinger/SurfaceFlinger.cppvoid SurfaceFlinger::postComposition()
{ATRACE_CALL();ALOGV("postComposition");nsecs_t dequeueReadyTime = systemTime();// release Bufferqueuelayerfor (auto& layer : mLayersWithQueuedFrames) {layer->releasePendingBuffer(dequeueReadyTime);}...// mPreviousPresentFences[0]是这一帧的present fence，mPreviousPresentFences[1]是上一帧的present fencemPreviousPresentFences[1] = mPreviousPresentFences[0];mPreviousPresentFences[0] =display ? getHwComposer().getPresentFence(*display->getId()) : Fence::NO_FENCE;...// 这个有关vsync，是校验presentfence释放的时间戳if (display && display->isPrimary() && display->getPowerMode() == hal::PowerMode::ON &&presentFenceTime->isValid()) {mScheduler->addPresentFence(presentFenceTime);}....
}

postComposition的作用就是释放上一帧显示的Buffer，然后重新设置当前帧的present fence，以及根据presentfence时间戳判断是否重新打开HW Vsync和软件Vsync进行校准。至此，SurfaceFlinger刷新的主体函数分析完了，可以看出来，如果是走device合成，SurfaceFlinger是直接把layer信息提交给hwc，由hwc去合成.



写在最后

好了今天的博客Android下SF合成流程重学习之Refresh流程就到这里了。总之，青山不改绿水长流先到这里了。如果本博客对你有所帮助，麻烦关注或者点个赞，如果觉得很烂也可以踩一脚！谢谢各位了！！

这篇关于Android下SF合成流程重学习之Refresh流程的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！


http://www.chinasem.cn/article/723799。

相关文章

SpringBoot整合Flowable实现工作流的详细流程

SpringBoot整合Flowable实现工作流的详细流程

《SpringBoot整合Flowable实现工作流的详细流程》Flowable是一个使用Java编写的轻量级业务流程引擎,Flowable流程引擎可用于部署BPMN2.0流程定义,创建这些流程定义的... 目录1、流程引擎介绍2、创建项目3、画流程图4、开发接口4.1 Java 类梳理4.2 查看流程图4
阅读更多...
java Long 与long之间的转换流程

java Long 与long之间的转换流程

《javaLong与long之间的转换流程》Long类提供了一些方法,用于在long和其他数据类型（如String）之间进行转换,本文将详细介绍如何在Java中实现Long和long之间的转换,感... 目录概述流程步骤1：将long转换为Long对象步骤2：将Longhttp://www.cppcns.c
阅读更多...
Go学习记录之runtime包深入解析

Go学习记录之runtime包深入解析

《Go学习记录之runtime包深入解析》Go语言runtime包管理运行时环境,涵盖goroutine调度、内存分配、垃圾回收、类型信息等核心功能,：本文主要介绍Go学习记录之runtime包的... 目录前言：一、runtime包内容学习1、作用：① Goroutine和并发控制：② 垃圾回收：③ 栈和
阅读更多...
Android学习总结之Java和kotlin区别超详细分析

Android学习总结之Java和kotlin区别超详细分析

《Android学习总结之Java和kotlin区别超详细分析》Java和Kotlin都是用于Android开发的编程语言,它们各自具有独特的特点和优势,：本文主要介绍Android学习总结之Ja... 目录一、空安全机制真题 1：Kotlin 如何解决 Java 的 NullPointerExceptio
阅读更多...
spring-gateway filters添加自定义过滤器实现流程分析(可插拔)

spring-gateway filters添加自定义过滤器实现流程分析(可插拔)

《spring-gatewayfilters添加自定义过滤器实现流程分析(可插拔)》：本文主要介绍spring-gatewayfilters添加自定义过滤器实现流程分析(可插拔),本文通过实例图... 目录需求背景需求拆解设计流程及作用域逻辑处理代码逻辑需求背景公司要求，通过公司网络代理访问的请求需要做请
阅读更多...
使用JavaConfig配置Spring的流程步骤

使用JavaConfig配置Spring的流程步骤

《使用JavaConfig配置Spring的流程步骤》JavaConfig是Spring框架提供的一种基于Java的配置方式,它通过使用@Configuration注解标记的类来替代传统的XML配置文... 目录一、什么是 JavaConfig？1. 核心注解2. 与 XML 配置的对比二、JavaConf
阅读更多...
重新对Java的类加载器的学习方式

重新对Java的类加载器的学习方式

《重新对Java的类加载器的学习方式》：本文主要介绍重新对Java的类加载器的学习方式,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录1、介绍1.1、简介1.2、符号引用和直接引用1、符号引用2、直接引用3、符号转直接的过程2、加载流程3、类加载的分类3.1、显示
阅读更多...
Android NDK版本迭代与FFmpeg交叉编译完全指南

Android NDK版本迭代与FFmpeg交叉编译完全指南

《AndroidNDK版本迭代与FFmpeg交叉编译完全指南》在Android开发中,使用NDK进行原生代码开发是一项常见需求,特别是当我们需要集成FFmpeg这样的多媒体处理库时,本文将深入分析A... 目录一、android NDK版本迭代分界线二、FFmpeg交叉编译关键注意事项三、完整编译脚本示例四
阅读更多...
Java对接Dify API接口的完整流程

Java对接Dify API接口的完整流程

《Java对接DifyAPI接口的完整流程》Dify是一款AI应用开发平台,提供多种自然语言处理能力,通过调用Dify开放API,开发者可以快速集成智能对话、文本生成等功能到自己的Java应用中,本... 目录Java对接Dify API接口完整指南一、Dify API简介二、准备工作三、基础对接实现1.
阅读更多...
Android与iOS设备MAC地址生成原理及Java实现详解

Android与iOS设备MAC地址生成原理及Java实现详解

《Android与iOS设备MAC地址生成原理及Java实现详解》在无线网络通信中,MAC（MediaAccessControl）地址是设备的唯一网络标识符,本文主要介绍了Android与iOS设备M... 目录引言1. MAC地址基础1.1 MAC地址的组成1.2 MAC地址的分类2. android与I
阅读更多...

Copyright China编程 23002807@qq.com

沪ICP备2023033072号-2