android lib so library file porting

http://tieba.baidu.com/p/2545670265

For friends who want to learn porting, I will tell you some of the libs I know about here.
These library files are mainly related to some stuck screens during transplantation!
You can find other library files in Baidu.
Something else you must know!
Mainly because I have learned from some problems encountered in the transplantation, and the conclusions I have drawn from various materials may be different from some of the materials on the Internet.

 

1. libgui.so is related to libsurfaceflinger.so, and libsurfaceflinger.so is responsible for the framework layer data: 
2. libhardware_legacy.so is mainly related to wifi
3. liblog.so is mainly related to generating system dynamic data log
4. libmdnssd.so is mainly Some header files are linked to the library file, which may involve framework layer
5, liboemcamera.so camera driver file
6, libOmx----.so mainly for kernel multimedia support (when porting, libOmxCore.so is Can not move, others can)
7. libreference-ril.so is related to communication
8. libskia.so is the engine of the graphics system, and is a low-level graphics library of Google for graphics, images, animations, SVG, text and other aspects.
9. libstagefright.so is related to media, mainly audio and video
10, libwebcore.so seems to be related to browsers
11, libandroid_servers.so system library files, system service components, framework-related
12, libandroid_runtime.so runtime library, application layer calls
13, libandroid.so provides Android function access
14, libsuspend.so seems to be related to the system instruction set

 

 

Anzhi's 13-step forward porting:
Many friends are interested in porting, but they all feel that porting is very profound and difficult to start, and there is no breakthrough point at all. In fact, you can easily port porting
here using MIUI and CM packages.
Note: In fact, the problem of resolution is not very serious. When WVGA is transplanted to HVGA model, MS has an adaptive resolution
tutorial to start:
1. You need to have a CM package, for example: HTC G11 CM package
2. You need to have A MIUI package, for example: HTC G14 MIUI package
3. To port MIUI to CM, the first step is to unpack it, you can use the kitchen to unpack it, which is simple and quick
4. Delete the app under system in the ROM of CM , framework , media folder
5. Move the folder in MIUI into the CM package
6. Download Beyond Compare (file comparison tool) to compare the files in the bin directory of the two ROMs,
except for files such as wlan and wl, the rest Everything missing in the CM package must be added
. 7. Compared with the etc folder, the internal folders cannot be touched! Add MIUI redundant folders, add redundant files
8. Compare the so driver files in the lib folder, put the redundant files in the MIUI package into the CM lib
9. Compare the xbin files, the redundant and decisive ones in the CM ROM delete
10.build.prop,主要修改设备信息,没什么大问题
11.两个ROM的boot.img解包,替换MIUI的kernel文件进CM的,之后打包内核
12.打包出来的新内核替换进CM的ROM
13.打包ROM,签名,试刷,刷入则成功,刷不入,则失败

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326604536&siteId=291194637