CN112732365A - Method and device for starting pre-installed application program, electronic equipment and storage medium - Google Patents
Method and device for starting pre-installed application program, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112732365A CN112732365A CN202110119657.XA CN202110119657A CN112732365A CN 112732365 A CN112732365 A CN 112732365A CN 202110119657 A CN202110119657 A CN 202110119657A CN 112732365 A CN112732365 A CN 112732365A
- Authority
- CN
- China
- Prior art keywords
- library file
- application program
- dynamic link
- file
- compressed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 105
- 230000003068 static effect Effects 0.000 claims abstract description 43
- 230000006870 function Effects 0.000 claims description 39
- 230000001419 dependent effect Effects 0.000 claims description 32
- 230000006837 decompression Effects 0.000 claims description 25
- 238000007906 compression Methods 0.000 claims description 10
- 230000006835 compression Effects 0.000 claims description 10
- 208000003443 Unconsciousness Diseases 0.000 abstract description 3
- 239000012141 concentrate Substances 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 20
- 238000004590 computer program Methods 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000009434 installation Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000008447 perception Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013144 data compression Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the disclosure provides a method and a device for starting a pre-installed application program, an electronic device and a storage medium. The process of decompressing and loading the pre-installed application program is set in the process of displaying the preset static information, so that the time window for displaying the static information is fully utilized, the program starting time is shortened, and meanwhile, the user is enabled to concentrate on the static information by displaying the static information to the user, thereby avoiding the situation that the user perceives the unconscious time consumption caused by decompressing and loading the application program and improving the user experience.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of computers, and in particular relates to a method and a device for starting a pre-installed application program, an electronic device and a storage medium.
Background
In order to facilitate the use of the user, a terminal device manufacturer generally pre-installs a plurality of commonly used Applications (APPs) in the terminal device for sale, so that the user can directly use the pre-installed APPs without special downloading after purchasing the terminal device.
At present, in order to reduce the volume of a pre-installed APP and reduce the memory occupation of a terminal device, the pre-installed APP is compressed to a certain extent, and when the terminal device runs the pre-installed APP for the first time, database files are decompressed and loaded.
However, since the APP cannot be started before the decompression and loading process is completed, the problem that the user experience is affected due to long APP start time and time consumption is caused.
Disclosure of Invention
The embodiment of the disclosure provides a method and a device for starting a pre-installed application program, electronic equipment and a storage medium, so as to solve the problems that the APP is long in starting time and time consuming and affects the user experience.
In a first aspect, an embodiment of the present disclosure provides a method for starting a pre-installed application, including:
running an application program; and in the process of displaying preset static information, decompressing the compressed library file of the application program, generating a dynamic link library file, and loading the dynamic link library file to start the application program.
In a second aspect, an embodiment of the present disclosure provides a preinstalled application starting apparatus, including:
an execution unit configured to execute an application;
and the decompression unit is used for decompressing the compressed library file of the application program in the process of displaying preset static information, generating a dynamic link library file and loading the dynamic link library file so as to start the application program.
In a third aspect, an embodiment of the present disclosure provides an electronic device, including: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the pre-installed application launching method as described above in the first aspect and in various possible designs of the first aspect.
In a fourth aspect, the embodiments of the present disclosure provide a computer-readable storage medium, where computer-executable instructions are stored, and when a processor executes the computer-executable instructions, the method for starting a pre-installed application program according to the first aspect and various possible designs of the first aspect is implemented.
According to the method and the device for starting the pre-installed application program, the electronic device and the storage medium provided by the embodiment, by running the application program, in the process of displaying preset static information, a compressed library file of the application program is decompressed, a dynamic link library file is generated, and the dynamic link library file is loaded to start the application program. The process of decompressing and loading the pre-installed application program is set in the process of displaying the preset static information, so that the time window for displaying the static information is fully utilized, the program starting time is shortened, and meanwhile, the user is enabled to concentrate on the static information by displaying the static information to the user, thereby avoiding the situation that the user perceives the unconscious time consumption caused by decompressing and loading the application program and improving the user experience.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present disclosure, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise.
FIG. 1 is a diagram illustrating a process for starting a pre-installed application in the prior art;
fig. 2 is a first flowchart illustrating a method for starting a preinstalled application according to an embodiment of the present disclosure;
fig. 3 is a schematic diagram of a privacy statement page provided by an embodiment of the present disclosure;
fig. 4A is a schematic diagram of a process of starting a preinstalled application according to an embodiment of the present disclosure;
fig. 4B is a schematic diagram illustrating a display of static information according to an embodiment of the disclosure;
fig. 5 is a schematic diagram of a dynamic link library file loading process according to an embodiment of the present disclosure;
fig. 6 is a flowchart illustrating a second method for starting a preinstalled application according to an embodiment of the present disclosure;
FIG. 7 is a timing diagram illustrating a method for starting an application according to an embodiment of the present disclosure;
fig. 8 is a block diagram illustrating a structure of a preinstalled application starting apparatus according to an embodiment of the present disclosure;
fig. 9 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present disclosure.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be described clearly and completely with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are some, but not all embodiments of the present disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
The nouns to which this disclosure relates will be explained first:
pre-installing an application program: the pre-installed Application is an Application (APP) that is pre-installed in the terminal device when the terminal device leaves the factory. In order to facilitate the use of the user, a terminal equipment manufacturer generally pre-installs a plurality of commonly used APPs in the terminal equipment for sale, so that the user can directly use the pre-installed APPs after purchasing the terminal equipment without additional downloading, thereby achieving the purpose of 'ready-to-use-by-hand' of the terminal equipment, reducing the configuration time of the terminal equipment and improving the usability. In order to prevent the preinstalled APP from occupying the storage space of the terminal device too much, the difference between the actual storage space of the terminal device purchased by a user and the nominal device storage space is large, and a terminal device manufacturer can limit the installation volume of the preinstalled APP preinstalled to the terminal device, so that in order to meet the limitation requirement of the installation volume, the preinstalled APP with more functions and large volume is obtained, part of files are in a compression state, decompression is needed when the preinstalled APP is operated for the first time, and the decompressed data files are loaded, so that the normal start of the preinstalled APP can be realized.
Fig. 1 is an exemplary diagram of a starting process of a pre-installed application in the prior art, and referring to fig. 1, a target application is pre-installed on a terminal device, for example, a smart phone. As shown in fig. 1, in the prior art, when a pre-installed application is started for the first time, after a user clicks a pre-installed application (pre-installed APP) in a system interface of a smart phone, the smart phone displays a decompression interface, decompresses a compressed file inside the pre-installed application, loads a decompressed data file, and after all the decompressed data files are loaded, the pre-installed application can be normally started to display a main function interface of a target application. However, since the target application cannot be started before the decompression and loading process is completed, and the user needs to wait until the process is finished, the time consumption of the user is meaningless, and the use experience of the user is affected. How to avoid the perception of the data file decompression and loading process of the preinstalled application program when the preinstalled application program is started for the first time by a user and realize the noninductive starting of the preinstalled application program is a problem which needs to be solved urgently at present.
The embodiment of the disclosure provides a method for starting a pre-installed application program to solve the above problem.
Fig. 2 is a first flowchart illustrating a method for starting a pre-installed application according to an embodiment of the present disclosure, and referring to fig. 2, the method of this embodiment may be applied to a terminal device, and the method for starting the pre-installed application includes:
step S101, the application is run.
The application program is a pre-installed application program pre-installed in the terminal device, and more specifically, the terminal device takes a smart phone as an example, and the pre-installed application program includes a system self-contained application program installed and displayed on a desktop of the smart phone, or a third party application program. The implementation manner of running the application program is various, for example, if an operation instruction input by a user is received and the corresponding application program is run, the operation instruction is, for example, to click an application program icon on a desktop of a smartphone; or, a call-up instruction initiated by the system or other application program is received to run the corresponding application program, and the detailed implementation of running the application program is not described herein.
Further, optionally, after the application program is run, it is determined whether the application program needs to decompress and load the data file, and more specifically, it is determined whether the application program is a preinstalled application program that is started for the first time, if so, the subsequent step of S102 is performed, and if not, the application program is directly started.
And S102, in the process of displaying the preset static information, decompressing the compressed library file of the application program, generating a dynamic link library file, and loading the dynamic link library file to start the application program.
The process of decompressing the compressed library file of the application program, generating the dynamic link library file, loading the dynamic link library file and displaying the preset static information are at least partially carried out in parallel, and the duration intervals of the two processes are at least partially overlapped. Illustratively, after the application program is run, the static information is displayed through a display unit, such as a display screen, of the terminal device, where the static information refers to data information that can be displayed without calling a dynamic link library file of the application program, and the static information may be preset information preset in the application program, such as description information, contract clause information, declaration information, and the like of the application program, or may be information such as pictures, videos, and the like that do not need to be decompressed.
More specifically, in one possible implementation, the static information is a privacy statement page. Fig. 3 is a schematic diagram of a privacy statement page provided by an embodiment of the present disclosure, and referring to fig. 3, the privacy statement page is a compliance requirement of the department of industry and credit for collecting and using user privacy information of an application, and for a pre-installed application, the privacy statement page must be displayed at the first startup, and after reading the privacy statement page, a user chooses to agree or disagree, and the privacy statement page can be closed. In the process of displaying the privacy statement page, the compressed library file is decompressed to generate a dynamic link library file, and the dynamic link library file is loaded. Meanwhile, compared with the display of other static pictures, videos and other information, the privacy statement page is a compliance requirement specified by the Ministry of industry and communications and belongs to an un-ignorable necessary link, so that the decompression of the compressed library file and the loading of the dynamic link library file are simultaneously carried out in the process of displaying the privacy statement page to a user, which is equivalent to simultaneously carrying out two necessary links in the process of starting the pre-installed application program for the first time, and the purpose of shortening the starting time of the pre-installed application program can be realized.
Further, while the static information is displayed, the system background decompresses the compressed library file of the application program to generate a dynamic link library file. Illustratively, decompressing a compressed library file of an application to generate a dynamically linked library file comprises: suspending a main thread of an application; and decompressing the compressed library file of the application program through the sub-thread of the application program to generate a dynamic link library file. The compressed library file refers to a file generated by compressing a dynamic link library file, and the compressed library file may be generated by compressing the dynamic link library file by a publisher of an application program. Further, the dynamic link library file is a data file which supports the starting and running of the application program and completes the corresponding function. Specifically, taking the android system as an example, the dynamically linked library file is, for example, a shared object (so) file. The so file is a binary file and can be used as a dynamic link library of the unix system, and specific principles of the so file are not repeated here.
In one possible implementation, the compressed library file is a file generated by compressing the so file in an xz compression format. The xz compression format is a lossless data compression file format using an LZMA (Lempel-Ziv-Markovchain-Algorithm) compression Algorithm, has a high compression rate, can well reduce the volume of a pre-installed application program in a compression scene of the pre-installed application program, and compared with the existing scheme, realizes the extreme compression of a pre-installed package.
Further, after the compressed library file is decompressed, the corresponding dynamic link library file generated by decompression needs to be loaded, specifically, taking the android system as an example, the dynamic link library file is loaded into the system by calling a system. Fig. 4A is a schematic diagram of a process of starting a preinstalled application according to an embodiment of the present disclosure, and referring to fig. 4A, the foregoing processes of decompressing and loading and the process of displaying static information are synchronized in time, in a possible implementation manner, as shown in fig. 4A, the duration of the process of displaying static information is greater than or equal to the time of decompressing a compressed library file and loading a dynamic link library file, in which case, a user may not feel the time-consuming process of decompressing a compressed library file and loading a dynamic link library file. Fig. 4B is a schematic diagram of displaying static information according to an embodiment of the disclosure, as shown in fig. 4B, specifically, this implementation may be implemented by setting a shortest display time for the static information, and when the duration is less than the shortest display time, the user may not close the static information, i.e., click "agree" as shown in fig. 4B. The shortest display time is determined by the time required to decompress and load the file, and in particular, by calculating the time required to decompress and load the file according to the computing power of different terminal devices. In another possible implementation manner, the duration of the process of displaying the static information is less than the time for decompressing the compressed library file and loading the dynamic link library file, at this time, the user can feel a part of the time-consuming process for decompressing the compressed library file and loading the dynamic link library file, but compared with the prior art, the meaningless time consumption is still effectively shortened, and the user experience is improved.
Illustratively, the decompression process of the compressed library file and the loading process of the dynamic link library file may be performed simultaneously through a plurality of threads, or may be performed after the compressed library file is completely decompressed, and then the loading process of the dynamic link library file is performed, where the processes may be set as needed, and are not specifically limited herein.
In a possible implementation manner, the implementation method for loading the dynamic link library file in step S102 includes the following specific steps:
step S1021, determining the storage position corresponding to the dynamic link library file.
In step S1022, the preset loading path is modified to a storage location.
In step S1023, the dynamic link library file is loaded through the modified loading path.
Specifically, after the compressed library file is decompressed, the dynamic link library file generated by the decompression is placed in a preset storage location, where the storage location may be flexibly set by a publisher of the application according to specific needs, and a default loading path of the system, that is, the preset loading path, is not necessarily matched with the storage location, so that an error (unscathed fiedlink) that the dynamic link library file cannot be found occurs in the process of starting the application. Therefore, after the decompression of the compressed library file is completed, the loading path of the system needs to be modified into a decompressed directory, i.e. a storage location corresponding to the dynamic link library file, so that the dynamic link library can be correctly loaded by the system.
Specifically, the method for modifying the preset loading path into the storage position includes: the method can be realized by a Proxy (Proxy) system.
In the embodiment, the position of the system for loading the dynamic link library is matched with the position of the dynamic link library generated by decompression by repositioning the loading path, so that the file of the dynamic link library can be correctly loaded, and the problem that the file of the dynamic link library cannot be found in the starting process of a pre-installed application program is solved.
Optionally, before step S1023, the method further includes:
step S1022A, determining the dependent file of each dynamic link library file, where the dependent file is a dynamic link library file that needs to be loaded before loading the dynamic link library file, determining whether the dependent file is loaded, and if the dependent file is not loaded, loading the dependent file.
Illustratively, in the process of loading the dynamic link library files, because of the dependency characteristics among the dynamic link library files, the dynamic link library files must be loaded in a specific loading sequence to realize the correct loading of all the dynamic link libraries. Illustratively, a.so and b.so are dynamic link library files to be loaded, where b.so includes a dependent dynamic link library file c.so, i.e. c.so is a dependent file of b.so, and in the sequential loading process, if c.so is not loaded, loading b.so may cause a system error. Therefore, fig. 5 is a schematic diagram of a dynamic link library file loading process provided in the embodiment of the present disclosure, referring to fig. 5, before loading a.so and b.so, determining respective dependent files, and determining whether the dependent files are loaded, and if the dependent files of the dynamic link library file are loaded, normally loading the dynamic link library file (for example, b.so in fig. 5); if the dependent file of the dynamic link library file is not loaded, the corresponding dependent file is loaded first (e.g., c.so in fig. 5), and then the dynamic link library file is loaded (e.g., b.so in fig. 5).
In the embodiment, before the dynamic link library file is loaded, whether the dynamic link library file has an unloaded dependent file or not is judged, if the unloaded dependent file exists, the dependent file is loaded preferentially, and then the dynamic link library file is loaded, so that system error reporting caused by loading sequence errors is avoided, and the stability of the starting process of the application program is improved.
In this embodiment, by running the application program, in the process of displaying the preset static information, the compressed library file of the application program is decompressed, the dynamic link library file is generated, and the dynamic link library file is loaded to start the application program. The process of decompressing and loading the pre-installed application program is set in the process of displaying the preset static information, so that the time window for displaying the static information is fully utilized, the program starting time is shortened, and meanwhile, the user is enabled to concentrate on the static information by displaying the static information to the user, thereby avoiding the situation that the user perceives the unconscious time consumption caused by decompressing and loading the application program and improving the user experience.
Referring to fig. 6, fig. 6 is a schematic flowchart illustrating a second method for starting a preinstalled application according to an embodiment of the present disclosure. In this embodiment, the implementation process of step 102 in the foregoing embodiment is described in detail, and the method for starting the preinstalled application program includes:
in step S201, an application is executed.
And step S202, displaying preset static information to a user through the sub-thread, and suspending the main thread of the application program.
Specifically, after the application program starts to run, the main thread of the application program is started, a basic application program file is loaded, then, static information such as a privacy statement page is loaded and displayed through a sub-thread, and since the compressed library file cannot be loaded with a dynamic link library file in the compressed library file before the decompression is not completed, the application program cannot be completely started, the main thread of the application program is suspended, the main thread is enabled to enter a 'suspended' state, the computing resources of the CPU are released, and the computing resources of the CPU can be enabled to perform subsequent file decompression and loading.
Step S203, obtaining a type identifier of the compressed library file, where the type identifier is used to indicate a function of an application program supported by a dynamic link library generated after the compressed library file is decompressed.
Illustratively, the compressed library file is a compressed file generated by compressing a dynamic link library file, the compressed file may include a plurality of files, the type identifier of the compressed library file is used for indicating the purpose of the dynamic link library composing the compressed library file, more specifically, for example, the compressed library file a is compressed by 5 so files named #01 to #05, and the 5 so files named #01 to #05 are used for realizing the a function of the application program, that is, after the system loads the 5 so files #01 to #05, the a function may be started. Thus, the type identification of the compressed library file a corresponds to the a function. Further, the type identifier may be implemented in a variety of ways, for example, by compressing the name of the library file, or compressing a specific attribute of the library file, so as to implement the type identifier, which is not described herein again.
And step S204, determining necessary compressed library files in the plurality of compressed library files according to the type identification.
In step S205, the necessary compressed library file is decompressed by the sub-thread of the application program, and a necessary library file is generated.
And step S206, loading necessary library files through the sub-thread of the application program so as to start the main function interface of the application program through the main thread of the application program.
Specifically, the dynamic link library file includes a necessary library file and an unnecessary library file, the necessary library file is used for supporting the application program to start the main function interface, the unnecessary library file is a library file which is not required to be loaded in the process of starting the main function interface by the application program, and the unnecessary library file can be loaded after the application program starts the main function interface, so as to implement other functions of the application program. The compressed library files comprise necessary compressed library files and unnecessary compressed library files, correspondingly, the necessary compressed library files refer to the compressed library files containing the necessary library files, and the unnecessary compressed library files refer to the compressed library files containing the unnecessary library files.
And according to the type identifier and a preset identifier analysis table, determining a necessary compressed library file from the plurality of compressed library files, decompressing the necessary compressed library file through a sub-thread of the application program to obtain the necessary library file, and awakening a main process of the application program after the necessary library file is loaded to enable the application program to start the main function interface because the necessary library file is used for realizing the function of starting the main function interface of the application program.
In step S207, the unnecessary compressed library file of the application is decompressed by the child thread of the application, and an unnecessary library file is generated.
And step S208, loading the unnecessary library file through the sub thread of the application program so as to completely start the application program.
Specifically, in the process of running the main function interface of the application program, the sub-thread of the application program decompresses the unnecessary compressed library file of the application program to generate the unnecessary library file. Specifically, after the application program is started and runs the main function interface, when the user does not perform operation, the application program is relatively in a static state, and the consumption of the computing resources of the CPU is low. Therefore, in the time window, the residual unnecessary compressed library files are decompressed through the sub-thread of the application program to generate unnecessary library files, and the unnecessary library files are loaded, so that the user finishes loading all the dynamic link library files under the condition of no perception, and the application program is completely started.
Fig. 7 is a timing diagram of starting an application according to an embodiment of the present disclosure, as shown in fig. 7, in this embodiment, for a preinstalled application, because a compressed library file and a corresponding dynamic link library file are decompressed and loaded in a segmented manner, only a part of the dynamic link library file is decompressed and loaded when a main function interface of the application is started, which is shorter in time consumption compared to a scheme of starting the application after all the compressed library files are decompressed and loaded; meanwhile, for the preinstalled application program, after the main function interface is generally started for the first time, a user can further select the corresponding sub-function after browsing the content of the main function interface, so that a part of time can be consumed, the terminal device decompresses the unnecessary compressed library file through the sub-program of the application program by using the idle time window, and loads the generated unnecessary library file, so that the user cannot feel the decompression and loading process, the starting time of the application program is shortened, and the purpose of reducing the time consumed by the user in an meaningless manner is realized.
In this embodiment, step S201 and step S101 in the above embodiments are implemented in the same manner, and for a detailed discussion, reference is made to the discussion of step S101, which is not described herein again.
Fig. 8 is a block diagram of a preinstalled application starting device according to an embodiment of the present disclosure. For ease of illustration, only portions that are relevant to embodiments of the present disclosure are shown. Referring to fig. 8, the preinstalled application startup device 3 includes:
and an execution unit 31 for executing the application program.
And the decompressing unit 32 is configured to decompress the compressed library file of the application program in the process of displaying the preset static information, generate a dynamic link library file, and load the dynamic link library file to start the application program.
In an embodiment of the present disclosure, when decompressing the compressed library file of the application and generating the dynamic link library file, the decompressing unit 32 is specifically configured to: suspending a main thread of an application; and decompressing the compressed library file of the application program through the sub-thread of the application program to generate a dynamic link library file.
In one embodiment of the present disclosure, the static information is a privacy statement page.
In an embodiment of the present disclosure, the dynamic link library includes an essential library file, where the essential library file is used to support the application program to start the main function interface, and the decompressing unit 32 is specifically used to: acquiring a type identifier of the compressed library file, wherein the type identifier is used for indicating the function of an application program supported by a dynamic link library generated after the compressed library file is decompressed; determining necessary compressed library files in the plurality of compressed library files according to the type identifiers; and decompressing the necessary compressed library file through the sub-thread of the application program to generate a necessary library file.
In an embodiment of the present disclosure, when the dynamic link library file is loaded to start the application, the decompressing unit 32 is specifically configured to: and loading necessary library files through the sub-thread of the application program so as to start the main functional interface of the application program through the main thread of the application program.
In one embodiment of the present disclosure, decompression unit 32 is further configured to: and decompressing the unnecessary compressed library file of the application program through the sub-thread of the application program to generate an unnecessary library file.
In an embodiment of the present disclosure, the decompressing unit 32, when decompressing the unnecessary compressed library file of the application program through the sub-thread of the application program, is specifically configured to: in the process of operating the main functional interface of the application program, decompressing unnecessary compressed library files of the application program through the sub-thread of the application program to generate unnecessary library files; after generating the optional library file, decompression unit 32 is further configured to: the unnecessary library files are loaded by the child thread of the application.
In an embodiment of the present disclosure, when the dynamic link library file is loaded, the decompressing unit 32 is specifically configured to: determining a storage position corresponding to the dynamic link library file; and modifying the preset loading path into a storage position, and loading the dynamic link library file through the modified loading path.
In an embodiment of the present disclosure, the dynamic link library file includes a plurality of files, and the decompressing unit 32 is further configured to, before loading each dynamic link library file: determining a dependent file of each dynamic link library file, wherein the dependent file is a dynamic link library file which needs to be loaded before the dynamic link library file is loaded; and judging whether the dependent file is loaded or not, and if the dependent file is not loaded, loading the dependent file.
The apparatus provided in this embodiment may be used to implement the technical solutions of the above method embodiments, and the implementation principles and technical effects are similar, which are not described herein again.
Referring to fig. 9, a schematic structural diagram of an electronic device 900 suitable for implementing the embodiment of the present disclosure is shown, where the electronic device 900 may be a terminal device or a server. Among them, the terminal Device may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a Digital broadcast receiver, a Personal Digital Assistant (PDA), a tablet computer (PAD), a Portable Multimedia Player (PMP), a car terminal (e.g., car navigation terminal), etc., and a fixed terminal such as a Digital TV, a desktop computer, etc. The electronic device shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 9, the electronic device 900 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 901, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage means 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the electronic apparatus 900 are also stored. The processing apparatus 901, the ROM902, and the RAM 903 are connected to each other through a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.
Generally, the following devices may be connected to the I/O interface 905: input devices 906 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 907 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 908 including, for example, magnetic tape, hard disk, etc.; and a communication device 909. The communication device 909 may allow the electronic apparatus 900 to perform wireless or wired communication with other apparatuses to exchange data. While fig. 9 illustrates an electronic device 900 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication device 909, or installed from the storage device 908, or installed from the ROM 902. The computer program performs the above-described functions defined in the methods of the embodiments of the present disclosure when executed by the processing apparatus 901.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of Network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, the first retrieving unit may also be described as a "unit for retrieving at least two internet protocol addresses".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
In a first aspect, according to one or more embodiments of the present disclosure, there is provided a method for starting a pre-installed application, including: running an application program; and in the process of displaying preset static information, decompressing the compressed library file of the application program, generating a dynamic link library file, and loading the dynamic link library file to start the application program.
According to one or more embodiments of the present disclosure, decompressing a compressed library file of the application program, and generating a dynamic link library file, includes: suspending a main thread of the application; and decompressing the compressed library file of the application program through the sub-thread of the application program to generate the dynamic link library file.
According to one or more embodiments of the present disclosure, the static information is a privacy statement page.
According to one or more embodiments of the present disclosure, the dynamic link library includes a necessary library file, where the necessary library file is used to support the application program to start a main function interface, decompress a compressed library file of the application program, and generate a dynamic link library file, and the method includes: acquiring a type identifier of the compressed library file, wherein the type identifier is used for indicating the functions of the application program supported by a dynamic link library generated after the compressed library file is decompressed; determining necessary compressed library files in the compressed library files according to the type identifiers; and decompressing the necessary compressed library file through the sub-thread of the application program to generate the necessary library file.
According to one or more embodiments of the present disclosure, loading the dynamic link library file to start the application program includes: and loading the necessary library file through the sub thread of the application program so as to start the main function interface of the application program through the main thread of the application program.
According to one or more embodiments of the present disclosure, the method further comprises: and decompressing the unnecessary compressed library file of the application program through the sub-thread of the application program to generate an unnecessary library file.
According to one or more embodiments of the present disclosure, decompressing, by a child thread of the application, a non-essential compressed library file of the application, and generating the non-essential library file, includes: in the process of operating the main functional interface of the application program, decompressing the unnecessary compressed library file of the application program through the sub-thread of the application program to generate an unnecessary library file; after generating the unnecessary library file, the method further comprises: loading the unnecessary library file through a child thread of the application program.
According to one or more embodiments of the present disclosure, loading the dynamic link library file includes: determining a storage position corresponding to the dynamic link library file; and modifying the preset loading path into the storage position, and loading the dynamic link library file through the modified loading path.
According to one or more embodiments of the present disclosure, the dynamic link library file includes a plurality of files, and before loading each of the dynamic link library files, the method further includes: determining a dependent file of each dynamic link library file, wherein the dependent file is a dynamic link library file which needs to be loaded before the dynamic link library file is loaded; and judging whether the dependent file is loaded or not, and if not, loading the dependent file.
According to one or more embodiments of the present disclosure, the dynamic link library file is a shared object file; the compressed library file is generated by compressing the shared object file in an xz compression format.
In a second aspect, according to one or more embodiments of the present disclosure, there is provided an application starting apparatus including:
and the running unit is used for running the application program.
And the decompression unit is used for decompressing the compressed library file of the application program in the process of displaying preset static information, generating a dynamic link library file and loading the dynamic link library file so as to start the application program.
In one or more embodiments of the present disclosure, when decompressing the compressed library file of the application program and generating the dynamic link library file, the decompressing unit is specifically configured to: suspending a main thread of the application; and decompressing the compressed library file of the application program through the sub-thread of the application program to generate the dynamic link library file.
In one or more embodiments of the present disclosure, the static information is a privacy statement page.
In one or more embodiments of the present disclosure, the dynamic link library includes a necessary library file, where the necessary library file is used to support the application program to start a main function interface, and the decompression unit is specifically configured to, when decompressing the compressed library file of the application program and generating the dynamic link library file: acquiring a type identifier of the compressed library file, wherein the type identifier is used for indicating the functions of the application program supported by a dynamic link library generated after the compressed library file is decompressed; determining necessary compressed library files in the compressed library files according to the type identifiers; and decompressing the necessary compressed library file through the sub-thread of the application program to generate the necessary library file.
In one or more embodiments of the present disclosure, when the decompression unit loads the dynamic link library file to start the application, the decompression unit is specifically configured to: and loading the necessary library file through the sub thread of the application program so as to start the main function interface of the application program through the main thread of the application program.
In one or more embodiments of the present disclosure, the decompression unit is further configured to: and decompressing the unnecessary compressed library file of the application program through the sub-thread of the application program to generate an unnecessary library file.
In one or more embodiments of the present disclosure, the decompression unit, when decompressing the unnecessary compressed library file of the application program by the sub-thread of the application program, is specifically configured to: in the process of operating the main functional interface of the application program, decompressing the unnecessary compressed library file of the application program through the sub-thread of the application program to generate an unnecessary library file; after generating the unnecessary library file, the decompression unit is further configured to: loading the unnecessary library file through a child thread of the application program.
In one or more embodiments of the present disclosure, when the dynamic link library file is loaded, the decompressing unit is specifically configured to: determining a storage position corresponding to the dynamic link library file; and modifying the preset loading path into the storage position, and loading the dynamic link library file through the modified loading path.
In one or more embodiments of the present disclosure, the dynamic link library file includes a plurality of files, and the decompressing unit is further configured to, before loading each of the dynamic link library files: determining a dependent file of each dynamic link library file, wherein the dependent file is a dynamic link library file which needs to be loaded before the dynamic link library file is loaded; and judging whether the dependent file is loaded or not, and if not, loading the dependent file.
According to one or more embodiments of the present disclosure, the dynamic link library file is a shared object file; the compressed library file is generated by compressing the shared object file in an xz compression format.
In a third aspect, according to one or more embodiments of the present disclosure, there is provided an electronic device including: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the pre-installed application launching method as described above in the first aspect and in various possible designs of the first aspect.
In a fourth aspect, according to one or more embodiments of the present disclosure, a computer-readable storage medium is provided, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, the method for starting a pre-installed application is implemented as described in the first aspect and various possible designs of the first aspect.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (13)
1. A method for starting a pre-installed application program, comprising:
running an application program;
decompressing a compressed library file of the application program in the process of displaying preset static information; and generating a dynamic link library file, and loading the dynamic link library file to start the application program.
2. The method of claim 1, wherein decompressing the compressed library file of the application to generate a dynamically linked library file comprises:
suspending a main thread of the application;
and decompressing the compressed library file of the application program through the sub-thread of the application program to generate the dynamic link library file.
3. The method of claim 2, wherein the static information is a privacy statement page.
4. The method of claim 2, wherein the dynamic link library file comprises a required library file, and wherein the required library file is used for supporting the application program to launch a main function interface;
decompressing the compressed library file of the application program to generate a dynamic link library file, including:
acquiring a type identifier of the compressed library file, wherein the type identifier is used for indicating the function of the application program supported by a dynamic link library file generated after the compressed library file is decompressed;
determining necessary compressed library files in the compressed library files according to the type identifiers;
and decompressing the necessary compressed library file through the sub-thread of the application program to generate the necessary library file.
5. The method of claim 4, wherein loading the dynamic link library file to launch the application comprises:
and loading the necessary library file through the sub thread of the application program so as to start the main function interface of the application program through the main thread of the application program.
6. The method of claim 5, further comprising:
and decompressing the unnecessary compressed library file of the application program through the sub-thread of the application program to generate an unnecessary library file.
7. The method of claim 6, wherein decompressing the unnecessary compressed library file of the application by the sub-thread of the application to generate an unnecessary library file comprises:
in the process of running the main function interface of the application program through the main thread of the application program, decompressing the unnecessary compressed library file of the application program through the sub-thread of the application program to generate an unnecessary library file;
after generating the unnecessary library file, the method further comprises:
loading the unnecessary library file through a child thread of the application program.
8. The method of any of claims 1-7, wherein loading the dynamically linked library file comprises:
determining the storage position of the dynamic link library file;
and modifying the preset loading path into the storage position, and loading the dynamic link library file through the modified loading path.
9. The method according to claim 8, wherein the dynamic link library file comprises a plurality of dynamic link library files, and before loading each of the dynamic link library files, the method further comprises:
determining a dependent file of each dynamic link library file, wherein the dependent file is a dynamic link library file which needs to be loaded before the dynamic link library file is loaded;
and judging whether the dependent file is loaded or not, and if not, loading the dependent file.
10. The method according to any one of claims 1 to 7, wherein the dynamic link library file is a shared object file;
the compressed library file is generated by compressing the shared object file in an xz compression format.
11. An application startup device, comprising:
an execution unit configured to execute an application;
and the decompression unit is used for decompressing the compressed library file of the application program in the process of displaying preset static information, generating a dynamic link library file and loading the dynamic link library file so as to start the application program.
12. An electronic device, comprising: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the application launching method of any of claims 1 to 10.
13. A computer-readable storage medium having stored thereon computer-executable instructions which, when executed by a processor, implement the application launching method as claimed in any one of claims 1 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110119657.XA CN112732365B (en) | 2021-01-28 | 2021-01-28 | Preassembled application program starting method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110119657.XA CN112732365B (en) | 2021-01-28 | 2021-01-28 | Preassembled application program starting method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112732365A true CN112732365A (en) | 2021-04-30 |
| CN112732365B CN112732365B (en) | 2024-07-12 |
Family
ID=75594399
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110119657.XA Active CN112732365B (en) | 2021-01-28 | 2021-01-28 | Preassembled application program starting method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112732365B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114138288A (en) * | 2021-11-29 | 2022-03-04 | 广东明创软件科技有限公司 | Installation package processing method, installation package sending device and electronic equipment |
| CN114217870A (en) * | 2021-12-10 | 2022-03-22 | 北京欧珀通信有限公司 | Loading method and device of installation package, electronic equipment and storage medium |
Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2003050719A (en) * | 2001-08-03 | 2003-02-21 | Katsuyoshi Nagashima | Device for monitoring utilization state of application software, and its software program |
| CN103955375A (en) * | 2014-05-21 | 2014-07-30 | 北京安兔兔科技有限公司 | Generation method for application installation file and starting method and device for application |
| US20140359262A1 (en) * | 2012-02-16 | 2014-12-04 | Huawei Device Co., Ltd. | Wireless handheld device startup method and wireless handheld device |
| CN105204890A (en) * | 2015-08-24 | 2015-12-30 | 小米科技有限责任公司 | Preassembly application modifying method and device |
| CN106406923A (en) * | 2015-07-30 | 2017-02-15 | 腾讯科技（深圳）有限公司 | Processing method and device of dynamic library file |
| US20170371595A1 (en) * | 2016-06-23 | 2017-12-28 | Qualcomm Incorporated | Preemptive decompression scheduling for a nand storage device |
| CN107562499A (en) * | 2017-08-23 | 2018-01-09 | 青岛海信移动通信技术股份有限公司 | Using the method, apparatus and computer-readable recording medium of loading |
| CN108132814A (en) * | 2017-12-22 | 2018-06-08 | 平安养老保险股份有限公司 | Page loading method, device, computer equipment and the storage medium of application program |
| CN108536481A (en) * | 2018-02-28 | 2018-09-14 | 努比亚技术有限公司 | A kind of application program launching method, mobile terminal and computer storage media |
| CN108595226A (en) * | 2018-05-09 | 2018-09-28 | 腾讯科技（深圳）有限公司 | Dynamic loading method, device and computer readable storage medium |
| CN109814930A (en) * | 2018-12-27 | 2019-05-28 | 维沃移动通信有限公司 | A kind of application loading method, device and mobile terminal |
| CN109885355A (en) * | 2019-02-21 | 2019-06-14 | 珠海市魅族科技有限公司 | A kind of application starting method and relevant apparatus |
| CN109947317A (en) * | 2019-03-11 | 2019-06-28 | 北京字节跳动网络技术有限公司 | Application program page display method and device |
| CN111240766A (en) * | 2020-01-22 | 2020-06-05 | 北京字节跳动网络技术有限公司 | Application starting method and device, electronic equipment and computer readable storage medium |
| CN111309391A (en) * | 2020-01-20 | 2020-06-19 | 北京无限光场科技有限公司 | Application program starting method, device, equipment and medium |
| CN111552517A (en) * | 2019-01-23 | 2020-08-18 | 阿里巴巴集团控股有限公司 | Application program starting method and device, electronic equipment and computer storage medium |
| CN111625289A (en) * | 2020-05-06 | 2020-09-04 | 小船出海教育科技（北京）有限公司 | Method and device for quickly starting application program and electronic equipment |
| CN111666564A (en) * | 2020-05-14 | 2020-09-15 | 平安科技（深圳）有限公司 | Application program safe starting method and device, computer equipment and storage medium |
| CN112119378A (en) * | 2018-08-22 | 2020-12-22 | 华为技术有限公司 | Application installation method and terminal |
| CN112256286A (en) * | 2020-10-21 | 2021-01-22 | 北京字节跳动网络技术有限公司 | Application running method and device and computer storage medium |
-
2021
- 2021-01-28 CN CN202110119657.XA patent/CN112732365B/en active Active
Patent Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2003050719A (en) * | 2001-08-03 | 2003-02-21 | Katsuyoshi Nagashima | Device for monitoring utilization state of application software, and its software program |
| US20140359262A1 (en) * | 2012-02-16 | 2014-12-04 | Huawei Device Co., Ltd. | Wireless handheld device startup method and wireless handheld device |
| CN103955375A (en) * | 2014-05-21 | 2014-07-30 | 北京安兔兔科技有限公司 | Generation method for application installation file and starting method and device for application |
| CN106406923A (en) * | 2015-07-30 | 2017-02-15 | 腾讯科技（深圳）有限公司 | Processing method and device of dynamic library file |
| CN105204890A (en) * | 2015-08-24 | 2015-12-30 | 小米科技有限责任公司 | Preassembly application modifying method and device |
| US20170371595A1 (en) * | 2016-06-23 | 2017-12-28 | Qualcomm Incorporated | Preemptive decompression scheduling for a nand storage device |
| CN107562499A (en) * | 2017-08-23 | 2018-01-09 | 青岛海信移动通信技术股份有限公司 | Using the method, apparatus and computer-readable recording medium of loading |
| CN108132814A (en) * | 2017-12-22 | 2018-06-08 | 平安养老保险股份有限公司 | Page loading method, device, computer equipment and the storage medium of application program |
| CN108536481A (en) * | 2018-02-28 | 2018-09-14 | 努比亚技术有限公司 | A kind of application program launching method, mobile terminal and computer storage media |
| CN108595226A (en) * | 2018-05-09 | 2018-09-28 | 腾讯科技（深圳）有限公司 | Dynamic loading method, device and computer readable storage medium |
| CN112119378A (en) * | 2018-08-22 | 2020-12-22 | 华为技术有限公司 | Application installation method and terminal |
| CN109814930A (en) * | 2018-12-27 | 2019-05-28 | 维沃移动通信有限公司 | A kind of application loading method, device and mobile terminal |
| CN111552517A (en) * | 2019-01-23 | 2020-08-18 | 阿里巴巴集团控股有限公司 | Application program starting method and device, electronic equipment and computer storage medium |
| CN109885355A (en) * | 2019-02-21 | 2019-06-14 | 珠海市魅族科技有限公司 | A kind of application starting method and relevant apparatus |
| CN109947317A (en) * | 2019-03-11 | 2019-06-28 | 北京字节跳动网络技术有限公司 | Application program page display method and device |
| CN111309391A (en) * | 2020-01-20 | 2020-06-19 | 北京无限光场科技有限公司 | Application program starting method, device, equipment and medium |
| CN111240766A (en) * | 2020-01-22 | 2020-06-05 | 北京字节跳动网络技术有限公司 | Application starting method and device, electronic equipment and computer readable storage medium |
| CN111625289A (en) * | 2020-05-06 | 2020-09-04 | 小船出海教育科技（北京）有限公司 | Method and device for quickly starting application program and electronic equipment |
| CN111666564A (en) * | 2020-05-14 | 2020-09-15 | 平安科技（深圳）有限公司 | Application program safe starting method and device, computer equipment and storage medium |
| CN112256286A (en) * | 2020-10-21 | 2021-01-22 | 北京字节跳动网络技术有限公司 | Application running method and device and computer storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114138288A (en) * | 2021-11-29 | 2022-03-04 | 广东明创软件科技有限公司 | Installation package processing method, installation package sending device and electronic equipment |
| CN114217870A (en) * | 2021-12-10 | 2022-03-22 | 北京欧珀通信有限公司 | Loading method and device of installation package, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112732365B (en) | 2024-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110275723A (en) | Obtain method, apparatus, electronic equipment and the readable medium of resource | |
| CN110851204B (en) | Application starting method and device and application packaging method and device | |
| CN112965761B (en) | Data processing method, system, electronic equipment and storage medium | |
| CN111309391A (en) | Application program starting method, device, equipment and medium | |
| CN111198999B (en) | Picture loading method and device for webpage end, medium and electronic equipment | |
| CN111240766B (en) | Application starting method and device, electronic equipment and computer readable storage medium | |
| CN111309304B (en) | Method, device, medium and electronic equipment for generating IDL file | |
| CN112732365B (en) | Preassembled application program starting method and device, electronic equipment and storage medium | |
| CN110704833A (en) | Data permission configuration method, device, electronic device and storage medium | |
| CN110727869A (en) | Page construction method and device | |
| CN112596720A (en) | Service operation method and device, electronic equipment and computer storage medium | |
| CN111079125A (en) | Method and device for calling third-party library dynamic lifting authority by application program | |
| CN110489162B (en) | Method, device, medium and equipment for simplifying installation package SO (storage and retrieval) file | |
| CN114035879A (en) | Page theme color changing method and device, electronic equipment and computer readable medium | |
| US20240095022A1 (en) | Hotfix method, apparatus, device and storage medium | |
| CN112416303B (en) | Software development kit hot repair method and device and electronic equipment | |
| CN110442419B (en) | Interface layout method and device for Android application | |
| CN112835671A (en) | Application page scene switching method, device and equipment | |
| US20240120991A1 (en) | Method and apparatus for synchronizing time by parsing satellite navigation data | |
| US12010356B2 (en) | Method and apparatus for sending information in live broadcast room, and electronic device | |
| CN112422648B (en) | Data synchronization method and system | |
| CN114090070A (en) | Application program installation package file processing method and electronic equipment | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN113032046A (en) | Method, device and equipment for repairing so file and storage medium | |
| CN113296771A (en) | Page display method, device, equipment and computer readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |