CN115113946A - A method and device for optimizing camera startup - Google Patents

Abstract

The invention belongs to the field of intelligent devices, and discloses a method and device for optimizing camera startup. The method includes: defining a process killing service of a target background service process in an init.rc file; and triggering the killing process service when a camera starts a connection , to close the target background service process. The invention can accurately kill the background process that does not affect the system running when the camera is turned on, release the memory of the killed background process, increase the available memory of the system for the camera operation, and reduce the jamming of the camera operation.

Description

A method and device for optimizing camera startup

technical field

The present invention relates to the field of smart devices, in particular to an optimized camera startup method and device.

Background technique

As users' diverse demands for smart terminal products increase, terminal functions such as mobile phones, tablet circuits (PADs), and smart wearable devices continue to innovate, and their application scope continues to expand.

At present, on Android devices with low memory, since the use of a higher-pixel camera requires a large amount of memory, and the remaining available memory of the system itself is relatively small, the operation after turning on the camera will be very laggy, affecting the user experience.

SUMMARY OF THE INVENTION

The purpose of the present invention is to provide an optimized camera startup method and device to solve the above problems.

The technical scheme provided by the present invention is as follows:

In one aspect, a method for optimizing camera startup is provided, including:

Define the killing process service of the target background service process in the init.rc file;

When the camera starts to connect, the process killing service is triggered to close the target background service process.

Further preferred, also includes:

Marking a target background service process, the target background service process includes a closeable background service process;

When it is detected that the target background service process is started, the process ID of the target background service process is saved.

Further preferably, when the camera initiates the connection, triggering the killing process service to execute and close the corresponding target background service process, including:

Based on the process ID of the target background service process, a corresponding process killing service is triggered to close the target background service process.

Further preferred, also includes:

Get the properties of the camera;

When the attribute of the camera is the enable attribute, the automatic restart path of the target background service process is closed.

Further preferably, when the attribute of the camera is the enable attribute, closing the automatic restart path of the target background service process, including:

Based on the preset shutdown identifier, the automatic restart path of the target background service process is closed.

Further preferably, before triggering the killing process service to close the target background service process when the camera starts to connect, the process includes:

When the camera initiates the connection, the enabled property of the camera is set to the enabled property.

Further preferred, including:

When the camera is turned off, the enabled property of the camera is set to the enabled shutdown property.

An optimized camera activation device, comprising:

Define the module, which is used to define the killing process service of the target background service process in the init.rc file;

The triggering module is used for triggering the killing process service to close the target background service process when the camera starts to connect.

Further preferred, also includes:

a marking module, used to mark a target background service process, the target background service process includes a closeable background service process;

The saving module is configured to save the process ID of the target background service process when it is monitored that the target background service process is started.

Further preferably, the trigger module is also used for:

Based on the process ID of the target background service process, a corresponding process killing service is triggered to close the target background service process.

An optimized camera startup method and device provided by the present invention have at least the following technical effects:

Through the optimized camera startup method of the present invention, the memory can be effectively managed, and the camera can be started quickly.

Description of drawings

The present invention is described in further detail below in conjunction with the accompanying drawings and specific embodiments:

FIG. 1 is a schematic diagram of an embodiment of an optimized camera startup method of the present invention;

FIG. 2 is a schematic diagram of an embodiment of an optimized camera activation device of the present invention.

Detailed ways

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained according to these drawings without creative efforts.

In order to keep the drawings concise, the drawings only schematically show the parts related to the present invention, and they do not represent its actual structure as a product. In addition, in order to make the drawings concise and easy to understand, in some drawings, only one of the components having the same structure or function is schematically shown, or only one of them is marked. As used herein, "one" not only means "only one", but also "more than one".

It should also be further understood that, as used in this specification and the appended claims, the term "and/or" refers to and including any and all possible combinations of one or more of the associated listed items .

In this article, it should be noted that, unless otherwise expressly specified and limited, the terms "installed", "connected" and "connected" should be understood in a broad sense, for example, it may be a fixed connection or a detachable connection, or It can be connected in one piece; it can be a mechanical connection or an electrical connection; it can be directly connected or indirectly connected through an intermediate medium, and it can be internal communication between two components. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood in specific situations.

In addition, in the description of the present application, the terms "first", "second" and the like are only used to distinguish the description, and cannot be understood as indicating or implying relative importance.

In order to more clearly describe the embodiments of the present invention or the technical solutions in the prior art, the specific embodiments of the present invention will be described below with reference to the accompanying drawings. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative efforts, and obtain other implementations.

Example 1

The present invention provides an embodiment of an optimized camera startup method, as shown in FIG. 1 , including:

S100 defines the killing process service of the target background service process in the init.rc file.

Specifically, a kill_pid service is defined in the init.rc file, which is specially used to kill the process corresponding to the pid stored in sys.update.pid.

Exemplarily, a startup file, that is, an init.rc file, is stored in the linux system, which is generally a script file that is automatically executed before an application is started.

Specifically, the pid of the background service process to be killed is stored in the system attribute, such as sys.killed.pid, and the service process obtains the corresponding pid by reading the system attribute sys.killed.pid.

Among them, Init.rc can directly define service, similar to the following way:

service prd_pid/system/bin/prod_cmd

user root

disabled

oneshot

seclabel u:r:xtc_init:s0

Because the operation of opening the camera itself is a performance bottleneck, in this embodiment, the process is directly killed by saving the pid, which is faster than the query used by other manufacturers which process pids need to be killed, and at the same time consumes less CPU resources.

S200 , when the camera starts to connect, the process killing service is triggered to close the target background service process.

Specifically, when the camera hardware executes CameraService::connect, set the property sys.camera.enable=true, and trigger the service kill_pid, kill the corresponding background process, and set sys.camera.enable=false when the camera exits .

Exemplarily, the defined service can be started by setting property monitoring in Init.rc. For example, the following code will start the service on property named prd_pid when sys.camera.enable becomes true: sys.camera.enable = true start prd_pid. Among them, the way to kill the process is to kill the corresponding pid process one by one.

Through the optimized camera startup method of the present invention, the memory can be effectively managed, and the camera can be started quickly.

Embodiment 2

Based on the above-mentioned embodiments, the same parts as those in the above-mentioned embodiments will not be repeated in this embodiment. This embodiment provides an optimized camera startup method, which preferably further includes:

A target background service process is marked, and the target background service process includes a closeable background service process.

When it is detected that the target background service process is started, the process ID of the target background service process is saved.

Preferably, when the camera initiates a connection, triggering the killing process service to execute and close the corresponding target background service process, including:

Based on the process ID of the target background service process, a corresponding process killing service is triggered to close the target background service process.

Specifically, in the init.rc file, before defining the killing process service of the target background service process, it is necessary to mark the background service process that can be killed, including: finding a type that often runs in the background of the system, but can be used at any time For the killed processes, these processes are regarded as the target background service process, and the pid (full name progress id) of the target background service process is saved when this type of target background service process is started.

Exemplarily, such as saving the pid of the update process in sys.update.pid.

In this embodiment, since the camera needs to take up a lot of CPU resources to open, for example, because the camera has too many pixels, the CPU processing burden is heavy, so when the camera is opened normally and when taking pictures, it will freeze.

In order to minimize the use of CPU and improve the overall performance of the system, by recording the corresponding process ID when the relevant process that needs to be killed, that is, the target background service process is started, the system does not need to repeatedly query the target background service process through the CPU. Reduce the burden on the cpu and further improve the efficiency of the cpu.

In this embodiment, the method further includes: when the attribute of the camera is the enable attribute, closing the automatic restart path of the target background service process.

Preferably, when the attribute of the camera is the enable attribute, closing the automatic restart path of the target background service process, including:

Based on the preset shutdown flag, close the automatic restart path of the target background service process.

Specifically, under normal circumstances, the android service process will restart within 5s after it is killed, which affects the performance of the camera. Compared with other manufacturers, the process will automatically restart repeatedly after killing the service process.

Because restarting the service requires system resources, when it is detected that the camera is in use, it is not allowed to restart if it is stopped by the CPU, so as to reduce the burden on the CPU and optimize the performance of the camera.

In this embodiment, by setting the shutdown flag, the killed service process is not allowed to be restarted during the use of the camera, which avoids the background service process from restarting repeatedly.

Preferably, before the automatic restart path of the target background service process is closed when the attribute of the camera is the enable attribute, the method includes:

Set the enable property of the camera to enable on property.

Specifically, it is judged that if sys.camera.enable is true, the system does not allow the killed background service process to restart automatically.

Preferred include:

When the camera is turned off, the enable property is set to the enable off property to turn off the camera.

In this embodiment, when the camera is turned on, the background processes that do not affect the running of the system are precisely killed, the memory of this part of the background processes is released, the available memory of the system is increased for the camera operation, and the camera operation lag is reduced. At the same time, directly specify the pid to kill the process, and the CPU usage is smaller.

Starting the service defined in init.rc by setting the property sys.camera.enable is an asynchronous process operation and does not affect the performance of the main thread opening the camera.

Embodiment 3

On the other hand, the present invention also provides an embodiment of an optimized camera activation device, as shown in FIG. 2 , including:

The definition module 100 is used to define the killing process service of the target background service process in the init.rc file.

The triggering module 200 is configured to trigger the killing process service to close the target background service process when the camera starts to connect.

Preferably, it also includes:

The marking module is used for marking a target background service process, where the target background service process includes a closeable background service process.

The saving module is configured to save the process ID of the target background service process when it is monitored that the target background service process is started.

Preferably, the trigger module is also used for:

Based on the process ID of the target background service process, a corresponding process killing service is triggered to close the target background service process.

In this embodiment, when the camera is turned on, the background processes that do not affect the running of the system are precisely killed, the memory of this part of the background processes is released, the available memory of the system is increased for the camera operation, and the camera operation freeze is reduced. At the same time, directly specify the pid to kill the process, and the CPU usage is smaller.

Starting the service defined in init.rc by setting the property sys.camera.enable is an asynchronous process operation and does not affect the performance of the main thread opening the camera.

In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

In the embodiments provided in this application, it should be understood that the disclosed apparatus/electronic device and method may be implemented in other manners. Exemplarily, the above-described embodiments of the apparatus/electronic device are only illustrative, and the division of the modules or units is merely a logical function division, and there may be other division methods in actual implementation, Illustratively, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, which may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

It should be noted that the above embodiments can be freely combined as required. The above are only the preferred embodiments of the present invention. It should be pointed out that for those skilled in the art, without departing from the principles of the present invention, several improvements and modifications can be made. It should be regarded as the protection scope of the present invention.

Claims (10)

1. A method for optimizing camera startup, comprising:

rc file defines the killing process service of the target background service process;

and when the camera starts connection, triggering the progress killing service to close the target background service progress.

2. The method for optimizing camera startup of claim 1, further comprising:

marking a target background service process, wherein the target background service process comprises a closable background service process;

and when the starting of the target background service process is monitored, saving the process ID of the target background service process.

3. The method for optimizing camera startup according to claim 2, wherein the triggering the progress killing service to execute the closing of the corresponding target background service process when the camera starts the connection comprises:

and triggering the corresponding killing process service based on the process ID of the target background service process so as to close the target background service process.

4. The method for optimizing camera startup of claim 1, further comprising:

acquiring attributes of the camera;

and when the attribute of the camera is the enable-to-start attribute, closing the automatic restart path of the target background service process.

5. The method for optimizing camera booting according to claim 4, wherein the closing the automatic restart path of the target background service process when the attribute of the camera is an enable attribute comprises:

and closing the automatic restarting path of the target background service process based on a preset closing identifier.

6. The optimized camera startup method according to claim 1, wherein before the triggering the progress killing service to close the target background service process when the camera starts connecting, the method comprises:

when the camera starts to connect, setting the enabling attribute of the camera as an enabling opening attribute.

7. The method for optimizing the startup of the camera according to any one of claims 1 to 6, comprising:

setting an enable attribute of the camera to an enable-off attribute when the camera is off.

8. An optimized camera activation device, comprising:

the definition module is used for defining the killing process service of the target background service process in the init.rc file;

and the triggering module is used for triggering the progress killing service when the camera starts connection so as to execute the process of closing the target background service.

9. The optimized camera launching device of claim 8, further comprising:

the system comprises a marking module, a sending module and a receiving module, wherein the marking module is used for marking a target background service process, and the target background service process comprises a closable background service process;

and the storage module is used for storing the process ID of the target background service process when the starting of the target background service process is monitored.

10. The optimized camera launching device of claim 9, wherein the triggering module is further configured to:

and triggering the corresponding killing process service based on the saved process ID of the target background service process so as to close the target background service process.

Images