CN110543329A - method for managing application version and mobile terminal - Google Patents
method for managing application version and mobile terminal Download PDFInfo
- Publication number
- CN110543329A CN110543329A CN201910797595.0A CN201910797595A CN110543329A CN 110543329 A CN110543329 A CN 110543329A CN 201910797595 A CN201910797595 A CN 201910797595A CN 110543329 A CN110543329 A CN 110543329A
- Authority
- CN
- China
- Prior art keywords
- version
- target
- identification
- user
- mobile terminal
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method for managing application versions and a mobile terminal, wherein the method comprises the following steps: receiving a first operation; displaying version identifications of the multiple versions of the target application in response to a first operation, wherein the first operation comprises one of the following operations: the method comprises the steps that a user executes a first preset operation on a version management control corresponding to a target application and a second preset operation executed by the user in the foreground running process of the target application; receiving a second operation aiming at a target version identification in the version identifications; in response to the second operation, a version management operation corresponding to the second operation is performed. According to the method, the user can enable the mobile terminal to display the version identifications corresponding to the multiple versions of the target application through simple and convenient operation, and the mobile terminal can receive and respond to the operation of the user on the target version identification in the multiple version identifications and execute the corresponding version management operation, so that the user can manage the multiple versions of the target application more conveniently and flexibly, and the user experience is improved.
Description
Technical Field
The present invention relates to the field of terminals, and in particular, to a method for managing an application version and a mobile terminal.
background
with the popularization of mobile terminals, various applications of the mobile terminals are increasing, and users need to manage the various applications. For example, the number of upgrading various applications is increasing, but the upgraded version may have poor stability, low compatibility, and large changes in user interface and function, which causes some users, especially middle-aged and old users, to be unaccustomed to use and to return to the version before upgrading.
in the existing rollback method, when an application is upgraded, a difference package is generated based on the difference between a new version application and an old version application, the old version application and the difference package are used as a temporary application which is used as the new version application, and after a rollback instruction is received, the difference package is deleted, and then the application is rolled back to the old version application. At present, the mainstream operation is that a user searches for a corresponding application and each version of the corresponding application from all applications in a setting, and based on the current rollback method, the rollback operation is executed on the corresponding version of the application to realize the rollback of the application version, but the operation mode is not convenient enough, and the user experience is influenced.
disclosure of Invention
The embodiment of the invention provides a method for managing application versions and a mobile terminal, and aims to solve the problems that the operation mode of the prior art is not convenient enough and influences user experience.
In order to solve the technical problem, the invention is realized as follows:
In a first aspect, a method for managing application versions is provided, the method comprising:
Receiving a first operation;
Displaying version identifications of multiple versions of a target application in response to the first operation, wherein the first operation comprises one of the following operations: executing a first preset operation on a version management control corresponding to the target application by a user and executing a second preset operation executed by the user in the foreground running process of the target application by the user;
Receiving a second operation aiming at a target version identification in the version identifications;
And responding to the second operation, and executing a version management operation corresponding to the second operation.
In a second aspect, a mobile terminal is provided, which includes:
the first receiving module is used for receiving a first operation;
A display module, configured to display version identifications of multiple versions of a target application in response to the first operation, where the first operation includes one of: executing a first preset operation on a version management control corresponding to the target application by a user and executing a second preset operation executed by the user in the foreground running process of the target application by the user;
A second receiving module, configured to receive a second operation for a target one of the version identifiers;
And the execution module is used for responding to the second operation and executing the version management operation corresponding to the second operation.
in a third aspect, a mobile terminal is provided, comprising a processor, a memory and a computer program stored on the memory and being executable on the processor, the computer program, when executed by the processor, implementing the steps of the method according to the first aspect.
in a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, realizes the steps of the method according to the first aspect.
In the embodiment of the invention, the user can enable the mobile terminal to display the version identifications of the multiple versions of the target application through a simple and convenient operation mode, and the mobile terminal can receive and respond to the second operation of the user aiming at the target version identification in the multiple version identifications to execute the corresponding version management operation, so that the user can manage the multiple versions of the target application more conveniently and flexibly, and the user experience is improved.
drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and not to limit the invention. In the drawings:
FIG. 1 is a flow diagram of a method of managing application versions of an embodiment of the present invention;
2(a) -2 (c) are diagrams of a method of displaying a version management control of one embodiment of the present invention;
3(a) -3 (c) are schematic diagrams of a method of selecting a target version identification of one embodiment of the present invention;
4(a) -4 (c) are diagrams of a method of deleting a target version identification according to an embodiment of the present invention;
5(a) -5 (b) are schematic diagrams of a method of modifying target version identification of one embodiment of the present invention;
FIG. 6 is a flow diagram illustrating a method of managing application versions in accordance with another embodiment of the present invention;
FIG. 7 is a flowchart illustrating a method of managing application versions according to yet another embodiment of the present invention;
8(a) -8 (c) are schematic diagrams of a method of selecting a target version identification of another embodiment of the present invention;
fig. 9 is a schematic structural diagram of a mobile terminal of an embodiment of the present invention;
Fig. 10 is a schematic structural diagram of a mobile terminal according to another embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
fig. 1 is a flowchart illustrating a method for managing application versions according to an embodiment of the present invention, where the method shown in fig. 1 may be performed by a mobile terminal, and the method includes:
s110, receiving a first operation.
S120, responding to the first operation, displaying the version identification of the multiple versions of the target application, wherein the first operation comprises one of the following operations: and the user executes a first preset operation on the version management control corresponding to the target application and a second preset operation executed by the user in the foreground running process of the target application.
in some embodiments, when the current interface is a desktop, that is, in a process that a target application is not running in the foreground, each application has a corresponding version management control, a first operation is a first preset operation performed on the version management control corresponding to the target application by a user, the first preset operation may be an operation in which the user clicks the version management control corresponding to the target application, and the mobile terminal receives and responds to the first preset operation to display version identifiers of multiple versions of the target application. And under the condition that the current interface is the interface of the target application, namely the target application runs in the foreground, the first operation is a second preset operation executed by the user in the process of the running of the target application in the foreground, the second preset operation can be an operation of shaking the mobile terminal, and the mobile terminal receives and responds to the second preset operation to display the version identifications of the multiple versions of the target application. The user can execute the first preset operation or the second preset operation based on the running state of the target application, so that the mobile terminal can display the multiple versions of the target application to the user in a short time, that is, the user can quickly find the multiple versions of the target application through a simple and convenient operation mode, the time for finding the multiple versions of the target application is reduced, and the user experience is improved.
optionally, in other embodiments, when the first preset operation is an operation of clicking a version management control corresponding to the target application by a user, the method shown in fig. 1 further includes:
Hiding the version management control in response to a sliding operation of a user sliding the version management control in a first direction; or the like, or, alternatively,
And responding to a sliding operation of a user in a preset area along a second direction, and displaying the version management control, wherein the second direction is opposite to the first direction.
in general, the version management control is not displayed by default, the version management control corresponding to the target application is displayed after the version of the target application is upgraded or in response to a sliding operation of a user in a preset area along a second direction, and in order to improve the operability of the version management control, the version management control is hidden in response to the sliding operation of the user sliding the version management control along a first direction, so that the desktop display is simpler, wherein the first direction is opposite to the second direction. And otherwise, responding to the sliding operation of the user in the second direction in the preset area, and displaying the version management control.
for example, the version management control is in the lower left corner of the application, and the version management control is represented in the form of a hinting point. As shown in fig. 2(a), by default, the lower left corner area of the WeChat, calendar, novel, and map does not display a cue point. As shown in fig. 2(b), the user performs a slide operation in the right direction in the area below the WeChat. As shown in fig. 2(c), the mobile terminal displays a cue point in response to a sliding operation by the user in the right direction. Otherwise, in response to the sliding operation of the user sliding the prompt point in the left direction, the prompt point disappears from the interface.
s130, receiving a second operation aiming at the target version identification in the version identifications.
and S140, responding to the second operation, and executing the version management operation corresponding to the second operation.
In some embodiments, in the case of displaying the version identifiers of the multiple versions of the target application, the user may manage the multiple versions of the target application according to the usage habit of the user. The mobile terminal receives and responds to the operation of the user aiming at the target version identification of the plurality of version identifications, and executes the corresponding version management operation. Therefore, the user can manage the multiple versions of the target application more conveniently, conveniently and flexibly, and the user experience is improved.
for example, when the target version is lower than the current version, if the target version is rolled back, the rolling back operation of the target version is executed in response to a second operation that the user selects the target version identifier corresponding to the target version. And if the target version is deleted, responding to a second operation that the user deletes the target version identification corresponding to the target version, and executing the deletion operation of the target version.
Optionally, in some embodiments, the second operation is an operation of selecting the target version identifier, where a version corresponding to the target version identifier is lower than a current version of the target application;
Wherein the version management operations comprise:
acquiring an installation package corresponding to the target version identification;
and installing the installation package.
specifically, in some embodiments, in response to the operation of selecting the target version identifier, if the target version corresponding to the target version identifier is the lowest version, the installation package corresponding to the target version identifier is directly obtained and installed. And if the target version corresponding to the target version identification is not the lowest version, namely the target version is the upgraded version, determining the installation package corresponding to the target version identification based on the difference package between the lowest version and the target version and the installation package of the lowest version, and acquiring and installing the installation package. The method and the device provide a quick interaction mode for returning the low version for the user, the user can conveniently degrade the upgraded version, the operation mode is simple, the efficiency is high, and the user experience is improved.
it should be understood that the difference package of the target version is formed of code that is added, changed, or reduced on the basis of the installation package of the last version of the target version. That is, the difference between the target version of the installation package and the previous version of the installation package.
for example, the target application has four versions, which are respectively an a version, a B version, a C version, and a D version in sequence from the lowest version to the highest version, wherein the a version is the lowest version, the a version only has an installation package, the B version, the C version, and the D version are upgraded versions, and the installation package and the difference package of the corresponding versions are generated once per liter of the versions. However, in order to save the storage space of the mobile terminal, after the installation package of the corresponding version is installed, the installation package is automatically deleted, so that the version B, the version C and the version D only have difference packages.
and under the condition that the current version of the target application is the D version, if the target application is returned to the A version, responding to the operation of clicking the version identification corresponding to the A version, and directly acquiring and installing the installation package of the A version. And if the version C is returned, responding to the operation of clicking the version identifier corresponding to the version C, synthesizing the installation package of the version C based on the installation package of the version A, the difference package of the version B and the difference package of the version C, acquiring the installation package of the version C, and installing the installation package of the version C.
alternatively, the target application is WeChat, and the version management control is represented in the form of a cue point. As shown in fig. 3(a), in response to the user clicking on the cue point of the lower area of the WeChat. As shown in fig. 3(b), the desktop background becomes translucent, and a version switching box is displayed at the same time, the content of the version switching box includes a box name, version identifiers corresponding to multiple versions of the target application, and check boxes corresponding to the identifier identifiers, where the box name is version switching, the version identifiers corresponding to the highest version to the lowest version are respectively v7.1.0, V7.2.2, V7.3.1, and V8.0.0, the current version of the target application is the version identifier V8.0.0, and the check box corresponding to V8.0.0 displays gray and is in a non-check state; and the check boxes corresponding to the V7.1.0, V7.2.2 and V7.3.1 are displayed in black and in a check-able state. That is to say, when the target application is in a certain version, the check box corresponding to the version identifier of the version displays gray and is in a non-check state; otherwise, the check box displays black and is in a check-able state. As shown in fig. 3(c), if the version is rolled back to the version with the version identification of V7.3.1, in response to the operation of clicking the version identification of V7.3.1, the installation package corresponding to the version identification is obtained and installed.
optionally, in other embodiments, the version management operation is one of:
if the target version corresponding to the target version identification is the lowest version, deleting the installation package corresponding to the target version identification and the difference package corresponding to the version identification of the next lower version, and determining the target installation package of the next lower version based on the installation package corresponding to the target version identification and the difference package corresponding to the version identification of the next lower version;
if the target version corresponding to the target version identification is the highest version, deleting the difference packet corresponding to the target version identification; and the number of the first and second groups,
If the target version corresponding to the target version identification is not the lowest version and not the highest version, deleting the difference packet corresponding to the target version identification and the initial difference packet corresponding to the version identification of the next version with the higher target version, and taking the target difference packet as the final difference packet corresponding to the version identification of the next version, wherein the target difference packet is determined based on the difference packet corresponding to the target version identification and the initial difference packet corresponding to the version identification of the next version.
for example, the target application has eight versions, the lowest version only has an installation package, other versions only have a difference package, if the lowest version is deleted, the installation package of the lowest version and the difference package of the next-lower version are deleted, and the target installation package synthesized by the installation package of the lowest version and the difference package of the next-lower version is determined as the final installation package of the next-lower version, that is, the next-lower version is changed into the lowest version. And if the highest version, namely the eighth version, is deleted, deleting the difference packet of the highest version. And if the third version is deleted, deleting the difference packet of the third version and the initial difference packet of the fourth version, and determining a target difference packet synthesized by the difference packet of the third version and the initial difference packet of the fourth version as a final difference packet of the fourth version. On one hand, the storage space of the mobile terminal can be saved; on the other hand, the version which is not liked or used by the user can be deleted, the user is prevented from selecting the version which is not liked or used by the user, and user experience is improved.
Alternatively, if the version identified as V7.2.2 is deleted, as shown in fig. 4(a), in response to the operation of sliding the version identification V7.2.2 in the left direction. As shown in fig. 4(b), a delete button is displayed. As shown in fig. 4(c), the version is identified as V7.2.2 version delete. The specific process of deletion is as follows: the difference packet corresponding to V7.2.2 and the initial difference packet corresponding to V7.3.1 are deleted, a target difference packet is formed based on the difference packet corresponding to V7.2.2 and the primary difference packet corresponding to V7.3.1, and the target difference packet is determined to be the final difference packet of V7.3.1.
Optionally, in some embodiments, the version management operation includes:
Displaying an edit box;
and in response to the input operation of the user for the edit box, modifying the target version identification into the identification input by the user.
In order to facilitate the user to better manage and distinguish the versions of the target application according to the understanding of the user, the user can modify the version identification corresponding to each version into the identification which is easy to identify. For example, the target application has three versions, and the version identifiers corresponding to the three versions are A, B, C, respectively, if the user feels that the version identifier B is good, and wants to modify the version identifier B into good. And in response to the pressing operation on the B, displaying the edit box, and in response to the input operation of the user on the edit box, modifying the version identifier B into good use. And then the user can quickly identify the version identification as a good version, thereby improving the user experience.
alternatively, if the target version is identified as V7.2.2 modified to be a proper version, as shown in fig. 5(a), the mobile terminal displays an edit box in response to a pressing operation to V7.2.2, and the pressing duration of the pressing operation is greater than a preset duration. As shown in fig. 5(b), the mobile terminal modifies the version identification V7.2.2 to a proper version in response to an input operation of the user with respect to the edit box.
Optionally, in other embodiments, the method further comprises:
hiding version identifications of multiple versions of a target application in response to an operation of clicking on a desktop or an interface of the target application.
Specifically, under the condition that the current interface is the desktop, if the target version identifier of the target application is not selected, the desktop is clicked to hide the target version identifier of the target application, and under the condition that the current interface is the interface of the target application, if the target version identifier of the target application is not selected, the interface of the target application is clicked to hide the target version identifier of the target application.
for example, the existing cue point is used as a version management entry, so that the use habit and the thinking habit of the user can be delayed. As shown in FIG. 6, by default, the cue point in the lower left corner of the target application is not displayed. And after the target application is upgraded or in response to the sliding operation of the user in the right direction in the lower area of the target application, displaying a prompt point at the lower left corner of the target application. And responding to the operation of clicking the prompt point by the user, and popping up a version switching bullet box, wherein the version switching bullet box comprises version identifications of a plurality of versions of the target application. And under the condition that the target version is lower than the current version of the target application, if the target version of the target application is returned, responding to the operation that the user clicks the target version identification corresponding to the target version, closing the version switching popup box, and acquiring and installing the installation package corresponding to the target version identification in the background. And if the target version is deleted, displaying a delete button to delete the target version in response to the operation of sliding the target version identifier corresponding to the target version in the left direction. And if the target version identification is renamed, responding to the pressing operation of the target version identification, wherein the pressing time of the pressing operation is longer than the preset time, displaying an edit box for renaming the target version identification, and responding to the input operation of a user aiming at the edit box to modify the identification input by the user with the target version identification. If the target version identification of the target application is not selected, clicking the desktop, closing the version switching popup box, namely hiding the target version identification of the target application. And hiding the cue point in response to a sliding operation in the left direction in the lower area of the target application.
Or, the prompt point is not needed to be used as an entry for upgrading and returning the target application, and the version switching bullet box is only needed to be opened in the target application in a shaking mode, so that the entry is shallower, the interactivity is stronger, and each version of the target application can be switched at any time in the target application. As shown in fig. 7, in response to an operation of opening a target application, the target application is made to run in the foreground, in response to an operation of shaking the mobile terminal, a version switching popup frame is popped up, where the version switching popup frame includes multiple versions of the target application, and in a case where the target version is lower than a current version of the target application, if the target version is backed to, in response to an operation of a user clicking a target version identifier corresponding to the target version, the version switching popup frame is closed, and an installation package corresponding to the target version identifier is obtained in the background and installed. And if the target version is deleted, displaying a delete button to delete the target version in response to the operation of sliding the target version identifier corresponding to the target version in the left direction. And if the target version identification is renamed, responding to the pressing operation of the target version identification, displaying an edit box when the pressing time of the pressing operation is longer than the preset time, and renaming the target version identification in response to the input operation of a user for the edit box. And if the target version identification of the target application is not selected, clicking the interface of the target application, and closing the target version identification of the version hiding target application.
Specifically, in the case that the target version is lower than the current version of the target application, the specific operation procedure of rolling back the current version to the target version is as follows: after the target application is opened, as shown in fig. 8(a), the interface of the target application is a current version UI interface, and in the use process of the target application, if the user is not used to the current version, the user wants to return to the previous version, i.e., the target version, as shown in fig. 8(b), in response to the operation of shaking the mobile terminal, a version switching popup box pops up, and the interface of the target application becomes semi-transparent.
And responding to the operation of clicking the target version identification corresponding to the target version by the user, closing the version switching popup frame, exiting the foreground by the target application, and acquiring and installing the installation package corresponding to the target version identification in the background. As shown in fig. 8(c), after the installation is completed, the interface of the target application is a target version UI interface.
in the embodiment of the invention, the user can enable the mobile terminal to display the version identifications of the multiple versions of the target application through a simple and convenient operation mode, and the mobile terminal can respond to the second operation of the user aiming at the version identifications of the multiple versions to execute the corresponding version management operation, so that the user can manage the multiple versions of the target application more conveniently and flexibly, and the user experience is improved.
The method for managing application versions according to the embodiment of the present invention is described in detail above with reference to fig. 1 to 8, and the mobile terminal according to the embodiment of the present invention will be described in detail below with reference to fig. 9. The mobile terminal 90 shown in fig. 9 includes:
a first receiving module 91, configured to receive a first operation;
a display module 92, configured to display version identifications of multiple versions of the target application in response to the first operation, where the first operation includes one of the following operations: executing a first preset operation on a version management control corresponding to the target application by a user and executing a second preset operation executed by the user in the foreground running process of the target application by the user;
A second receiving module 93, configured to receive a second operation for a target one of the version identifiers;
an executing module 94, configured to, in response to the second operation, execute a version management operation corresponding to the second operation.
in the embodiment of the invention, the user can enable the mobile terminal to display the version identifications of the multiple versions of the target application through a simple and convenient operation mode, and the mobile terminal can receive and respond to the second operation of the user aiming at the target version identification in the multiple version identifications to execute the corresponding version management operation, so that the user can manage the multiple versions of the target application more conveniently and flexibly, and the user experience is improved.
Optionally, as an embodiment, the second operation is an operation of selecting the target version identifier, where a version corresponding to the target version identifier is lower than a current version of the target application;
wherein the execution module 94 comprises:
The rollback submodule is used for acquiring the installation package corresponding to the target version identification;
The rollback submodule is also used for installing the installation package.
Optionally, as an embodiment, the executing module 94 includes:
a deleting submodule, configured to delete the installation package corresponding to the target version identifier and the difference package corresponding to the version identifier of the next lower version if the target version corresponding to the target version identifier is the lowest version, and determine the target installation package of the secondary version based on the installation package corresponding to the target version identifier and the difference package corresponding to the version identifier of the next lower version;
if the target version corresponding to the target version identification is the highest version, deleting the difference packet corresponding to the target version identification; and the number of the first and second groups,
If the target version corresponding to the target version identification is not the lowest version and not the highest version, deleting the difference packet corresponding to the target version identification and the initial difference packet corresponding to the version identification of the next version with the higher target version, and taking the target difference packet as the final difference packet corresponding to the version identification of the next version, wherein the target difference packet is determined based on the difference packet corresponding to the target version identification and the initial difference packet corresponding to the version identification of the next version.
Optionally, as an embodiment, the executing module 94 includes:
The display submodule is used for displaying the edit box;
And the modification sub-module is used for modifying the target version identification into the identification input by the user in response to the input operation of the user for the edit box.
Optionally, as an embodiment, the display module is further configured to:
hiding the version management control in response to a sliding operation of a user sliding the version management control in a first direction; or the like, or, alternatively,
And responding to a sliding operation of a user in a preset area along a second direction, and displaying the version management control, wherein the second direction is opposite to the first direction.
The mobile terminal provided in the embodiment of the present invention can implement each process implemented by the mobile terminal in the method embodiments of fig. 1 to fig. 8, and is not described herein again to avoid repetition.
fig. 10 is a schematic diagram of a hardware structure of a mobile terminal for implementing various embodiments of the present invention, where the mobile terminal 100 includes, but is not limited to: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the mobile terminal architecture illustrated in fig. 10 is not intended to be limiting of mobile terminals, and that a mobile terminal may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the mobile terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.
Wherein, the processor 110 is configured to control the user input unit 107 to receive a first operation; controlling the display unit 106 to display the version identification of the plurality of versions of the target application in response to the first operation, the first operation comprising one of: executing a first preset operation on a version management control corresponding to the target application by a user and executing a second preset operation executed by the user in the foreground running process of the target application by the user; controlling the user input unit 107 to receive a second operation for a target one of the version identifications; and responding to the second operation, and executing a version management operation corresponding to the second operation.
in the embodiment of the invention, the user can enable the mobile terminal to display the version identifications of the multiple versions of the target application through a simple and convenient operation mode, and the mobile terminal can receive and respond to the second operation of the user aiming at the target version identification in the multiple version identifications to execute the corresponding version management operation, so that the user can manage the multiple versions of the target application more conveniently and flexibly, and the user experience is improved.
it should be understood that, in the embodiment of the present invention, the radio frequency unit 101 may be used for receiving and sending signals during a message transmission or call process, and specifically, after receiving downlink data from a base station, the downlink data is processed by the processor 110; in addition, the uplink data is transmitted to the base station. Typically, radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with a network and other devices through a wireless communication system.
The mobile terminal provides wireless broadband internet access to the user through the network module 102, such as helping the user send and receive e-mails, browse webpages, access streaming media, and the like.
the audio output unit 103 may convert audio data received by the radio frequency unit 101 or the network module 102 or stored in the memory 109 into an audio signal and output as sound. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 includes a speaker, a buzzer, a receiver, and the like.
The input unit 104 is used to receive an audio or video signal. The input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, and the Graphics processor 1041 processes image data of a still picture or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the network module 102. The microphone 1042 may receive sound and may be capable of processing such sound into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone call mode.
the mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 1061 and/or a backlight when the mobile terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the posture of the mobile terminal (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), and vibration identification related functions (such as pedometer, tapping); the sensors 105 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.
the display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, the user input unit 107 includes a touch panel 1071 and other input devices 1072. Touch panel 1071, also referred to as a touch screen, may collect touch operations by a user on or near the touch panel 1071 (e.g., operations by a user on or near touch panel 1071 using a finger, stylus, or any suitable object or attachment). The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and receives and executes commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. Specifically, other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.
further, the touch panel 1071 may be overlaid on the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although in fig. 10, the touch panel 1071 and the display panel 1061 are two independent components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.
The interface unit 108 is an interface through which an external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and external devices.
The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 109 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
the processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The mobile terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system.
In addition, the mobile terminal 100 includes some functional modules that are not shown, and thus, the detailed description thereof is omitted.
preferably, an embodiment of the present invention further provides a mobile terminal, which includes a processor 110, a memory 109, and a computer program stored in the memory 109 and capable of running on the processor 110, where the computer program, when executed by the processor 110, implements the processes of the method embodiments shown in fig. 1 to 8, and can achieve the same technical effects, and in order to avoid repetition, the details are not repeated here.
an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the method embodiments shown in fig. 1 to 8, and can achieve the same technical effect, and is not described herein again to avoid repetition. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (12)
1. A method of managing application versions, the method comprising:
Receiving a first operation;
displaying version identifications of multiple versions of a target application in response to the first operation, wherein the first operation comprises one of the following operations: executing a first preset operation on a version management control corresponding to the target application by a user and executing a second preset operation executed by the user in the foreground running process of the target application by the user;
Receiving a second operation aiming at a target version identification in the version identifications;
and responding to the second operation, and executing a version management operation corresponding to the second operation.
2. the method of claim 1, wherein the second operation is an operation of selecting the target version identification, the target version identification corresponding to a version lower than a current version of the target application;
wherein the version management operations comprise:
Acquiring an installation package corresponding to the target version identification;
and installing the installation package.
3. the method of claim 1, wherein the version management operation is one of:
If the target version corresponding to the target version identification is the lowest version, deleting the installation package corresponding to the target version identification and the difference package corresponding to the version identification of the next lower version, and determining the target installation package of the next lower version based on the installation package corresponding to the target version identification and the difference package corresponding to the version identification of the next lower version;
If the target version corresponding to the target version identification is the highest version, deleting the difference packet corresponding to the target version identification; and the number of the first and second groups,
if the target version corresponding to the target version identification is not the lowest version and not the highest version, deleting the difference packet corresponding to the target version identification and the initial difference packet corresponding to the version identification of the next version with the higher target version, and taking the target difference packet as the final difference packet corresponding to the version identification of the next version, wherein the target difference packet is determined based on the difference packet corresponding to the target version identification and the initial difference packet corresponding to the version identification of the next version.
4. The method of claim 1, wherein the version management operation comprises:
displaying an edit box;
And in response to the input operation of the user for the edit box, modifying the target version identification into the identification input by the user.
5. the method of any one of claims 1-4, further comprising:
Hiding the version management control in response to a sliding operation of a user sliding the version management control in a first direction; or the like, or, alternatively,
and responding to a sliding operation of a user in a preset area along a second direction, and displaying the version management control, wherein the second direction is opposite to the first direction.
6. a mobile terminal, characterized in that the mobile terminal comprises:
The first receiving module is used for receiving a first operation;
A display module, configured to display version identifications of multiple versions of a target application in response to the first operation, where the first operation includes one of: executing a first preset operation on a version management control corresponding to the target application by a user and executing a second preset operation executed by the user in the foreground running process of the target application by the user;
A second receiving module, configured to receive a second operation for a target one of the version identifiers;
And the execution module is used for responding to the second operation and executing the version management operation corresponding to the second operation.
7. The mobile terminal according to claim 6, wherein the second operation is an operation of selecting the target version identifier, and a version corresponding to the target version identifier is lower than a current version of the target application;
Wherein the execution module comprises:
The rollback submodule is used for acquiring the installation package corresponding to the target version identification;
the rollback submodule is also used for installing the installation package.
8. The mobile terminal of claim 6, wherein the execution module comprises:
A deleting submodule, configured to delete the installation package corresponding to the target version identifier and the difference package corresponding to the version identifier of the next lower version if the target version corresponding to the target version identifier is the lowest version, and determine the target installation package of the secondary version based on the installation package corresponding to the target version identifier and the difference package corresponding to the version identifier of the next lower version;
If the target version corresponding to the target version identification is the highest version, deleting the difference packet corresponding to the target version identification; and the number of the first and second groups,
if the target version corresponding to the target version identification is not the lowest version and not the highest version, deleting the difference packet corresponding to the target version identification and the initial difference packet corresponding to the version identification of the next version with the higher target version, and taking the target difference packet as the final difference packet corresponding to the version identification of the next version, wherein the target difference packet is determined based on the difference packet corresponding to the target version identification and the initial difference packet corresponding to the version identification of the next version.
9. The mobile terminal of claim 6, wherein the execution module comprises:
The display submodule is used for displaying the edit box;
and the modification sub-module is used for modifying the target version identification into the identification input by the user in response to the input operation of the user for the edit box.
10. the mobile terminal of any of claims 8-9, wherein the display module is further configured to:
Hiding the version management control in response to a sliding operation of a user sliding the version management control in a first direction; or the like, or, alternatively,
and responding to a sliding operation of a user in a preset area along a second direction, and displaying the version management control, wherein the second direction is opposite to the first direction.
11. A mobile terminal, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps of the method according to any one of claims 1 to 5.
12. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910797595.0A CN110543329B (en) | 2019-08-27 | 2019-08-27 | Method for managing application version and mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910797595.0A CN110543329B (en) | 2019-08-27 | 2019-08-27 | Method for managing application version and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110543329A true CN110543329A (en) | 2019-12-06 |
| CN110543329B CN110543329B (en) | 2023-05-05 |
Family
ID=68710680
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910797595.0A Active CN110543329B (en) | 2019-08-27 | 2019-08-27 | Method for managing application version and mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110543329B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116679872A (en) * | 2022-11-15 | 2023-09-01 | 荣耀终端有限公司 | Redundant installation package cleaning method |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5732275A (en) * | 1996-01-11 | 1998-03-24 | Apple Computer, Inc. | Method and apparatus for managing and automatically updating software programs |
| CN105893080A (en) * | 2016-03-28 | 2016-08-24 | 努比亚技术有限公司 | Application management method and device |
| US20170220814A1 (en) * | 2016-01-29 | 2017-08-03 | Konica Minolta Laboratory U.S.A., Inc. | Digital rights management system implementing version control |
| CN107967153A (en) * | 2017-12-13 | 2018-04-27 | 维沃移动通信有限公司 | The management method and mobile terminal of a kind of application program |
| CN108563378A (en) * | 2018-04-25 | 2018-09-21 | 维沃移动通信有限公司 | A kind of information management method and terminal |
| CN109725805A (en) * | 2018-12-28 | 2019-05-07 | 维沃移动通信有限公司 | A kind of alarm clock setting method and terminal |
-
2019
- 2019-08-27 CN CN201910797595.0A patent/CN110543329B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5732275A (en) * | 1996-01-11 | 1998-03-24 | Apple Computer, Inc. | Method and apparatus for managing and automatically updating software programs |
| US20170220814A1 (en) * | 2016-01-29 | 2017-08-03 | Konica Minolta Laboratory U.S.A., Inc. | Digital rights management system implementing version control |
| CN105893080A (en) * | 2016-03-28 | 2016-08-24 | 努比亚技术有限公司 | Application management method and device |
| CN107967153A (en) * | 2017-12-13 | 2018-04-27 | 维沃移动通信有限公司 | The management method and mobile terminal of a kind of application program |
| CN108563378A (en) * | 2018-04-25 | 2018-09-21 | 维沃移动通信有限公司 | A kind of information management method and terminal |
| CN109725805A (en) * | 2018-12-28 | 2019-05-07 | 维沃移动通信有限公司 | A kind of alarm clock setting method and terminal |
Non-Patent Citations (1)
| Title |
|---|
| 张向军: "ANDROID智能手机开发软件版本管理系统设计与实现", 《知网》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116679872A (en) * | 2022-11-15 | 2023-09-01 | 荣耀终端有限公司 | Redundant installation package cleaning method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110543329B (en) | 2023-05-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111049979B (en) | Application sharing method, electronic equipment and computer readable storage medium | |
| CN108536365B (en) | Image sharing method and terminal | |
| CN111459355B (en) | Content sharing method and electronic equipment | |
| CN110995923A (en) | Screen projection control method and electronic equipment | |
| CN110502163B (en) | Terminal device control method and terminal device | |
| CN110062105B (en) | Interface display method and terminal equipment | |
| CN110837327B (en) | Message viewing method and terminal | |
| CN109814786B (en) | Image storage method and terminal equipment | |
| CN109525710B (en) | Method and device for accessing application program | |
| CN111026484A (en) | Application sharing method, first electronic device and computer-readable storage medium | |
| CN111142723B (en) | Icon moving method and electronic equipment | |
| CN110752981B (en) | Information control method and electronic equipment | |
| CN109407948B (en) | Interface display method and mobile terminal | |
| CN110096203B (en) | Screenshot method and mobile terminal | |
| CN110703972B (en) | File control method and electronic equipment | |
| CN109101327B (en) | Switching of light application and mobile terminal | |
| CN110928619B (en) | Wallpaper setting method and device, electronic equipment and medium | |
| CN110167006B (en) | Method for controlling application program to use SIM card and terminal equipment | |
| CN110012152B (en) | Interface display method and terminal equipment | |
| CN109284146B (en) | Light application starting method and mobile terminal | |
| CN111190515A (en) | Shortcut panel operation method, device and readable storage medium | |
| CN109067975B (en) | Contact person information management method and terminal equipment | |
| CN108491125B (en) | Operation control method of application store and mobile terminal | |
| CN107704159B (en) | Application icon management method and mobile terminal | |
| CN111399715B (en) | Interface display method and electronic equipment |
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 |