CN110362355B - Application interface display method and device - Google Patents

Application interface display method and device Download PDF

Info

Publication number
CN110362355B
CN110362355B CN201810285018.9A CN201810285018A CN110362355B CN 110362355 B CN110362355 B CN 110362355B CN 201810285018 A CN201810285018 A CN 201810285018A CN 110362355 B CN110362355 B CN 110362355B
Authority
CN
China
Prior art keywords
application
target application
window container
container control
carrier
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.)
Active
Application number
CN201810285018.9A
Other languages
Chinese (zh)
Other versions
CN110362355A (en
Inventor
吴锦
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hisense Mobile Communications Technology Co Ltd
Original Assignee
Hisense Mobile Communications Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hisense Mobile Communications Technology Co Ltd filed Critical Hisense Mobile Communications Technology Co Ltd
Priority to CN201810285018.9A priority Critical patent/CN110362355B/en
Publication of CN110362355A publication Critical patent/CN110362355A/en
Application granted granted Critical
Publication of CN110362355B publication Critical patent/CN110362355B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44568Immediately runnable code
    • G06F9/44578Preparing or optimising for loading
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces

Abstract

The invention discloses an application interface display method and device, and belongs to the technical field of mobile terminals. The method comprises the following steps: when the target application is detected to be cleared, detecting whether a window container control used for displaying the target application in the carrier application is available, wherein the target application refers to an application which is currently embedded in the carrier application for displaying an application interface, and the carrier application is displayed on a main screen; and if the window container control is detected to be available, restarting the target application through the window container control, and embedding the application interface of the target application into the carrier application through the window container control for displaying. That is, in the embodiment of the present invention, even if the mobile terminal performs memory recovery, which causes the application interface of the target application embedded in the carrier application to be cleared, the target application may be automatically restarted through the window container control, so that the application interface of the target application may still be displayed in the carrier application after the mobile terminal performs memory recovery.

Description

Application interface display method and device
Technical Field
The invention relates to the technical field of mobile terminals, in particular to an application interface display method and device and a mobile terminal.
Background
Currently, the mobile terminal may embed the application interface of the target application into the carrier application for display, that is, the application interface of the target application may be displayed in the carrier application as an interface in the carrier application for a long time. The target application may be a third party application or a built-in application installed in the mobile terminal, the carrier application may be another third party application or a built-in application installed in the mobile terminal except the target application, and the carrier application is currently displayed on a home screen of the mobile terminal.
In the related art, in the process that the mobile terminal embeds the application interface of the target application into the carrier application for display, if the mobile terminal needs to recycle the memory due to the fact that the memory usage is too large, the target application may be cleared due to the fact that the memory usage is too large or the memory is continuously increased.
However, if the target application is cleared, the application interface of the target application embedded and displayed in the carrier application is also cleared, and therefore, it is desirable to provide an application interface display method, so that the application interface of the target application can still be displayed in the carrier application after the mobile terminal performs memory recovery.
Disclosure of Invention
In order to solve the problem that an application interface of a target application embedded in a carrier application and displayed cannot be continuously displayed after a mobile terminal performs memory recovery in the related art, embodiments of the present invention provide an application interface display method and apparatus. The technical scheme is as follows:
in a first aspect, a method for displaying an application interface is provided, where the method includes:
when the target application is detected to be cleared, detecting whether a window container control used for displaying the target application in a carrier application is available, wherein the target application refers to an application which is currently embedded in the carrier application for application interface display, and the carrier application is displayed on a main screen;
if the window container control is detected to be available, restarting the target application through the window container control;
and embedding the application interface of the target application in the carrier application for displaying through the window container control.
Optionally, before detecting whether a window container control for displaying the target application in the carrier application is available, the method further includes:
monitoring whether an application task of the target application is removed;
and if the application task of the target application is removed, determining that the target application is cleared.
Optionally, the method further comprises:
if the window container control is detected to be unavailable, rebuilding the window container control used for displaying the target application in the carrier application;
restarting the target application through the reconstructed window container control, and embedding an application interface of the target application in the carrier application for displaying through the reconstructed window container control.
Optionally, the window container control comprises a window container corresponding to the virtual screen, and a TextureView and a Surface object created in the window container;
wherein the TextureView is used to draw and display an application interface of the target application, and the Surface object includes window information indicating a width, a height, and a screen resolution.
Optionally, the embedding, by the window container control, the application interface of the target application in the carrier application for display includes:
capturing drawing information of the target application through a Surface object in the window container control;
based on the drawing information, drawing an application interface of the target application through TextureView in the window container control;
Displaying the application interface of the target application as a parallel page of the application interface of the carrier application on the home screen through TextureView in the window container control based on the window information.
Optionally, the restarting the target application through the window container control includes:
and taking the virtual screen identifier as a display screen parameter in a StartActivity function, and calling the StartActivity function through the window container control, wherein the StartActivity function is used for triggering the operation of restarting the target application in the virtual screen.
Optionally, the method further comprises:
determining a mapping relationship between the coordinates on the virtual screen and the coordinates on the main screen;
when a touch operation of an application interface for the target application is detected on the home screen, determining coordinates of the touch operation;
and responding to the touch operation through the virtual screen based on the coordinate of the touch operation and the mapping relation.
In a second aspect, an application interface display apparatus is provided, the apparatus comprising:
the device comprises a detection module, a display module and a display module, wherein the detection module is used for detecting whether a window container control used for displaying a target application in a carrier application is available or not when the target application is detected to be cleared, the target application refers to an application which is currently embedded in the carrier application for displaying an application interface, and the carrier application is displayed on a main screen;
The starting module is used for restarting the target application through the window container control if the window container control is detected to be available;
and the display module is used for embedding the application interface of the target application into the carrier application through the window container control for displaying.
Optionally, the apparatus further comprises:
the monitoring module is used for monitoring whether the application task of the target application is removed;
a determining module, configured to determine that the target application is cleared if the application task of the target application is removed.
Optionally, the apparatus is further configured to:
if the window container control is detected to be unavailable, rebuilding the window container control used for displaying the target application in the carrier application;
restarting the target application through the reconstructed window container control, and embedding an application interface of the target application in the carrier application for displaying through the reconstructed window container control.
Optionally, the window container control comprises a window container corresponding to the virtual screen, and a TextureView and a Surface object created in the window container;
wherein the TextureView is used to draw and display an application interface of the target application, and the Surface object includes window information indicating a width, a height, and a screen resolution.
Optionally, the display module includes:
the grabbing submodule is used for grabbing the drawing information of the target application through the Surface object in the window container control;
the drawing sub-module is used for drawing an application interface of the target application through TextureView in the window container control based on the drawing information;
and the display sub-module is used for displaying the application interface of the target application on the main screen as a parallel page of the application interface of the carrier application through the TextureView in the window container control based on the window information.
Optionally, the starting module is specifically configured to:
and taking the virtual screen identifier as a display screen parameter in a StartActivity function, and calling the StartActivity function through the window container control, wherein the StartActivity function is used for triggering the operation of restarting the target application in the virtual screen.
Optionally, the apparatus is further configured to:
determining a mapping relationship between the coordinates on the virtual screen and the coordinates on the main screen;
when a touch operation of an application interface for the target application is detected on the home screen, determining coordinates of the touch operation;
And responding to the touch operation through the virtual screen based on the coordinate of the touch operation and the mapping relation.
In a third aspect, a mobile terminal is provided, which includes:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to perform the steps of any one of the methods of the first aspect.
In a fourth aspect, a computer-readable storage medium is provided, having instructions stored thereon, which when executed by a processor, implement the steps of any of the methods of the first aspect described above.
In a fifth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the application interface display method of the first aspect.
The technical scheme provided by the embodiment of the invention has the following beneficial effects: when the target application is detected to be cleared, detecting whether a window container control used for displaying the target application in the carrier application is available, if the window container control is detected to be available, restarting the target application through the window container control, and embedding an application interface of the target application in the carrier application through the window container control for displaying. That is, in the embodiment of the present invention, even if the mobile terminal performs memory recovery, which causes the application interface of the target application embedded in the carrier application to be cleared, the target application may be automatically restarted through the window container control, so that the application interface of the target application may still be displayed in the carrier application after the mobile terminal performs memory recovery.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1A is a diagram illustrating a related art embedding of a target application into a carrier application for display;
fig. 1B is a flowchart of an application interface display method according to an embodiment of the present invention;
FIG. 2 is a flowchart of an application interface display method according to an embodiment of the present invention;
fig. 3A is a block diagram of an application interface display apparatus according to an embodiment of the present invention;
fig. 3B is a block diagram of an application interface display apparatus according to an embodiment of the present invention;
FIG. 3C is a block diagram of a display module according to an embodiment of the invention;
fig. 4 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
Before explaining the embodiments of the present invention in detail, an application scenario related to the embodiments of the present invention will be described.
Currently, the mobile terminal may embed the application interface of the target application into the carrier application for display according to user settings, that is, the application interface of the target application may be displayed as a parallel page of the application interface of the carrier application. Since the carrier application is currently displayed on the mobile terminal, after the application interface of the target application is embedded into the carrier application, the user can switch to the application interface of the target application by performing a page switching operation in the carrier application without switching to the application interface of the target application by exiting the carrier application.
For example, referring to fig. 1A, a schematic diagram of a related art method for embedding a target application into a carrier application for display is provided. As shown in fig. 1A, the carrier application includes four interfaces, and different interfaces can be switched to be displayed by sliding left and right. Wherein, the left diagram in fig. 1A is a fourth application interface of the carrier application. The target application is embedded into the carrier application, and thus, the carrier application further includes a fifth application interface, that is, an application interface of the target application, as shown in the right diagram of fig. 1A. In this way, if the currently displayed fourth application interface is the fourth application interface, and the sliding operation of sliding to the left is performed on the fourth application interface, the application interface of the target application can be switched to. In this way, the user can switch to the application interface of the target application by performing a switching operation in the application interface of the carrier application without exiting the carrier application.
However, in practical applications, the mobile terminal may need to clean the memory due to operating jamming and the like. And the mobile terminal may remove the target application when cleaning the memory, so that the application interface of the target application embedded and displayed in the carrier application is also removed, and at this time, the page originally displaying the application interface of the target application is changed into a blank page. However, since the mobile terminal displays the application interface of the target application in the carrier application according to the user setting, embedding the application interface displaying the target application corresponds to becoming a function of the carrier application, and if the application interface of the target application is cleared due to the mobile terminal clearing the memory, it corresponds to the carrier application losing a part of the function, which is not suitable for the user. In this scenario, the mobile terminal may automatically redisplay the removed application interface of the target application in the carrier application through the application interface display method provided in the embodiment of the present invention.
Next, a method for displaying an application interface according to an embodiment of the present invention will be described.
Fig. 1B is a flowchart of an application interface display method according to an embodiment of the present invention, where the method may be used in a mobile terminal, and as shown in fig. 1B, the method includes the following steps:
step 101: when the target application is detected to be cleared, whether a window container control used for displaying the target application in the carrier application is available is detected.
The target application refers to an application that is currently embedded in a carrier application for application interface display, the carrier application is currently displayed on a home screen, and the carrier application may be a built-in application of the mobile terminal or a third-party application installed in the mobile terminal.
In addition, it should be further noted that, for a mobile terminal installed with an android system, the mobile terminal may launch an installed application onto a screen. The mobile terminal generally supports three screen displays, one of which is a main screen, that is, a physical screen of the mobile terminal, and generally, when the mobile terminal starts an application, the application is started on the main screen, so that a user can see an application interface of the application on the main screen. Also, the desktop of the mobile terminal is displayed on the main screen. The other is a virtual screen, where the displayed interface is not visible to the user. That is, if an application is launched onto a virtual screen, the user cannot see the application interface of the application on the virtual screen. Also known as peripheral screens, are commonly used to extend displays. Since the peripheral screen is not referred to in the present application, the peripheral screen will not be described in detail here.
Step 102: and if the window container control is detected to be available, restarting the target application through the window container control.
Step 103: and embedding the application interface of the target application in the carrier application for displaying through the window container control.
In the embodiment of the invention, when the target application is detected to be removed, whether a window container control used for displaying the target application in the carrier application is available is detected, if the window container control is detected to be available, the target application is restarted through the window container control, and an application interface of the target application is embedded in the carrier application through the window container control for displaying. That is, in the embodiment of the present invention, even if the mobile terminal performs memory recovery, which causes the application interface of the target application embedded in the carrier application to be cleared, the target application may be automatically restarted through the window container control, so that the application interface of the target application may still be displayed in the carrier application after the mobile terminal performs memory recovery.
Fig. 2 is a flowchart of an application interface display method according to an embodiment of the present invention, where the method may be used in a mobile terminal, and as shown in fig. 2, the method includes the following steps:
Step 201: when the target application is detected to be cleared, whether a window container control used for displaying the target application in the carrier application is available is detected.
Generally, an application running in a mobile terminal has a corresponding process and an application task for recording related information of the application. And if the mobile terminal recovers the memory to cause that the application is cleared, removing the application task corresponding to the application. Based on this, in the embodiment of the present invention, the operating system of the mobile terminal may monitor whether the application task of the target application is removed in real time, and if the application task of the target application is removed, it may be determined that the target application has been cleared.
Specifically, in the embodiment of the present invention, after monitoring that the application task of the target application is removed, the operating system of the mobile terminal may send a notification message to the bearer application to notify the bearer application that the target application has been cleared.
When detecting that the target application is cleared, the mobile terminal may further detect whether a window container control for displaying an application interface of the target application in the carrier application is also removed or damaged, that is, the mobile terminal may detect whether the window container control for displaying the application interface of the target application is still available.
Based on the foregoing description, it can be known that the operating system of the mobile terminal may send a notification message to the carrier application, and after the carrier application receives the notification message, may call back the window container control to detect whether the window container control is still available after the target application is cleared. If the carrier application successfully calls back the window container control, it may be determined that the window container control is available, and if the call back fails, it may be determined that the window container control is unavailable.
It should be noted that the window container control is a control created in advance by the mobile terminal for displaying an application interface of the target application. The window container control comprises a window container corresponding to the virtual screen, and a TextureView and a Surface object which are created in the window container. TextureView is used to draw and display an application interface of a target application, and Surface objects include window information indicating a width, a height, and a screen resolution. The window information in effect specifies the width, height and screen resolution of the application interface of the target application displayed in the carrier application.
If the mobile terminal detects that the window container control for displaying the application interface of the target application is still available, the mobile terminal may perform step 202-.
Step 202: and if the window container control is detected to be available, restarting the target application through the window container control.
When detecting that the window container control is available through step 201, the mobile terminal may restart the target application through the window container control.
It should be noted that, in which screen the mobile terminal launches the target application, which screen displays the application interface of the target application accordingly. In the related art, when an application is started, a mobile terminal generally starts the application directly on a main screen. However, in the embodiment of the present invention, since a plurality of target applications may be embedded and displayed in one carrier application, if the target applications are directly launched onto the main screen when the target applications are launched, several target applications are embedded and displayed in the carrier application, and several target applications are launched on the main screen, which may result in poor user experience and may affect application stack management of the main screen, thereby bringing a large burden to the main screen. Based on this, in the embodiment of the present invention, the mobile terminal may launch the target application onto a virtual screen invisible to the user, and create a separate external stack for recording application information of the application launched onto the virtual screen for the virtual screen.
Specifically, in the embodiment of the present invention, the mobile terminal may use the virtual screen identifier as a display screen parameter in a StartActivity function, and call the StartActivity function through the window container control, where the StartActivity function is used to trigger an operation of starting the target application in the virtual screen.
The mobile terminal can call the StartActivity function through the window container control and transmit the virtual screen identifier to the StartActivity function as the display screen parameter, so that the StartActivity function can start the target application on the virtual screen indicated by the display screen parameter through the window container control.
Step 203: and embedding the application interface of the target application in the carrier application for displaying through the window container control.
After launching the target application onto the virtual screen, the mobile terminal can redraw and display the application interface of the target application through the window container control.
The mobile terminal can capture drawing information of a target application through a Surface object in a window container control; and drawing an application interface of the target application through the TextureView based on the drawing information. Specifically, the drawing information includes drawing data for drawing an application interface of the target application, and the TextureView can draw the application interface of the target application according to the drawing information. The width of the application interface of the drawn target application may be smaller than, greater than, or equal to the width indicated by the window information, and the height of the application interface of the drawn target application may also be smaller than, greater than, or equal to the height indicated by the window information.
After drawing the application interface of the target application through the window container control, the mobile terminal may display the application interface of the target application in the carrier application through TextureView in the window container control based on window information included in the Surface object.
It should be noted that, if the width of the application interface of the drawn target application is greater than the width indicated by the window information and/or the height of the application interface of the drawn target application is greater than the height indicated by the window information, the mobile terminal may reduce the application interface of the target application so that the size of the application interface of the reduced target application is less than or equal to the size indicated by the window information, or, if the size of the application interface of the target application is less than the size indicated by the window information, the mobile terminal may appropriately enlarge the size of the application interface of the target application so that the size of the application interface of the target application may be adapted to the size indicated by the window information. That is, in the embodiment of the present invention, the application interface of the drawn target application may perform adaptation processing according to the size indicated by the window information, so that the application interface may be displayed in the area of the size indicated by the window information.
Optionally, in the embodiment of the present invention, the mobile terminal simply draws the application interface of the target application through the window container control and displays the application interface on the main screen, but the target application is launched on the virtual screen instead of the main screen. In this case, what is displayed in the carrier application of the main screen is actually only the application interface of the target application, and what can respond to the target application is the virtual screen. Based on this, the mobile terminal may determine a mapping relationship between the coordinates on the virtual screen and the coordinates on the main screen, that is, the mobile terminal may correspond the coordinates on the virtual screen and the coordinates on the main screen one to one, so that when the mobile terminal detects a touch operation on the main screen for the application interface of the target application, the coordinates of the touch operation may be determined and sent to the virtual screen. After the virtual screen receives the coordinates of the touch operation, the corresponding position of the coordinates of the touch operation in the virtual screen can be determined according to the mapping relation between the virtual screen and the main screen, and if a control capable of responding to the touch operation exists at the determined position, the virtual screen can respond to the touch operation through the control.
In the process that the mobile terminal displays the application interface of the target application through the window container control, if the user performs touch operation on the target application and the virtual screen responds according to the touch operation and then updates the application interface of the target application, the mobile terminal can inform the Surface object in the window container control to capture the drawing information of the target application again, and redraw and display the application interface through the TextureView. In this way, the application interface of the target application displayed on the main screen will be updated synchronously with the update of the application interface of the target application on the virtual screen.
Step 204: and if the window container control is detected to be unavailable, rebuilding the window container control for displaying the target application in the carrier application.
The above step 202-. In a possible case, after the mobile terminal clears the target application, the window container control may also be affected to become unavailable, and at this time, the mobile terminal may rebuild the window container control for displaying the application interface of the target application in the carrier application.
Specifically, the mobile terminal may create a window container corresponding to the virtual screen in the Activity component of the carrier application, and create a TextureView and a Surface object in the window container, so as to complete creation of the window container control. The embedding of the application interface of the target application into the desktop for display refers to displaying the application interface of the target application as a parallel page of the interface of the desktop, that is, the application interface of the target application can be displayed on the home screen as one interface of the desktop.
The Activity component is one of four main components in an android system and is mainly used for interacting with a user. In an android application, an Activity component may provide a separate screen on which controls may be displayed and in which user operational events may be monitored and processed in response. In an embodiment of the present invention, the mobile terminal may create a window container in the Activity component of the carrier application. Since the target application needs to be launched onto the virtual screen in order to reduce the burden of the main screen in consideration of the subsequent launching of the target application, the mobile terminal can associate the window container with the virtual screen.
In addition, in the embodiment of the invention, after the mobile terminal creates the window container, the TextureView can be created in the window container. When rendering, drawing and displaying an interface to be displayed, the mobile terminal needs a displayed canvas and controls the position size and the like of picture content. In the related art, when an application interface of an application is displayed, a mobile terminal can start packaged surfaceView for an Activity component of the application, and realize the function of a canvas by creating a Windows object.
After creating the TextureView, the mobile terminal may create a listening event for the TextureView, where the listening event may be used to listen whether a creation opportunity of a Surface object is reached, and if so, the mobile terminal may create the Surface object in a window container, where the Surface object may include window information indicating a width, a height, and a screen resolution, that is, the created Surface object specifies a size of an area of an application interface for displaying a target application.
The reconstruction of the window container control is realized by creating the window container, the TextureView and the Surface object in the carrier application Activity component, and then the mobile terminal can start the target application together with the reconstructed window container control and display the application interface of the target application.
Step 205: and restarting the target application through the reconstructed window container control, and embedding the application interface of the target application into the carrier application for displaying through the reconstructed window container control.
The specific implementation process of this step may refer to the specific implementation manner of the foregoing steps 202-203, and details are not described herein in this embodiment of the present invention.
In the embodiment of the invention, when the target application is detected to be removed, the mobile terminal can detect whether a window container control used for displaying the target application in the carrier application is available, and if the window container control is detected to be available, the target application is restarted through the window container control, and the application interface of the target application is embedded in the carrier application through the window container control for displaying. That is, in the embodiment of the present invention, even if the mobile terminal performs memory recovery, which causes the application interface of the target application embedded in the carrier application to be cleared, the target application may be automatically restarted through the window container control, so that the application interface of the target application may still be displayed in the carrier application after the mobile terminal performs memory recovery.
Next, an application interface display apparatus provided in an embodiment of the present invention is described.
Fig. 3A is a block diagram of an application interface display apparatus 300 according to an embodiment of the present invention, and referring to fig. 3A, the apparatus 300 includes:
the detection module 301 is configured to detect whether a window container control for displaying a target application in a carrier application is available when it is detected that the target application is cleared, where the target application is an application currently embedded in the carrier application for displaying an application interface, and the carrier application is displayed on a home screen;
a starting module 302, configured to restart the target application through the window container control if it is detected that the window container control is available;
and the display module 303 is configured to embed the application interface of the target application in the carrier application through the window container control for displaying.
Optionally, referring to fig. 3B, the apparatus 300 further comprises:
a monitoring module 304, configured to monitor whether an application task of a target application is removed;
a determining module 305, configured to determine that the target application is cleared if the application task of the target application is removed.
Optionally, the apparatus 300 is further configured to:
if the window container control is detected to be unavailable, rebuilding the window container control used for displaying the target application in the carrier application;
And restarting the target application through the reconstructed window container control, and embedding the application interface of the target application into the carrier application for displaying through the reconstructed window container control.
Optionally, the window container control comprises a window container corresponding to the virtual screen, and a textview and a Surface object created in the window container;
wherein the TextureView is used to draw and display an application interface of the target application, and the Surface object includes window information indicating a width, a height, and a screen resolution.
Optionally, referring to fig. 3C, the display module 303 includes:
the grabbing submodule 3031 is used for grabbing drawing information of the target application through a Surface object in the window container control;
the drawing submodule 3032 is used for drawing an application interface of the target application through TextureView in the window container control based on the drawing information;
the display sub-module 3033 is configured to display the application interface of the target application as a parallel page of the application interface of the carrier application on the main screen through the TextureView in the window container control based on the window information.
Optionally, the starting module 302 is specifically configured to:
and taking the virtual screen identifier as a display screen parameter in the StartActivity function, and calling the StartActivity function through a window container control, wherein the StartActivity function is used for triggering the operation of restarting the target application in the virtual screen.
Optionally, the apparatus 300 is further configured to:
determining a mapping relation between the coordinates on the virtual screen and the coordinates on the main screen;
when a touch operation of an application interface for a target application is detected on a home screen, determining coordinates of the touch operation;
and responding to the touch operation through the virtual screen based on the coordinate and the mapping relation of the touch operation.
In the embodiment of the invention, when the target application is detected to be removed, whether a window container control used for displaying the target application in the carrier application is available is detected, if the window container control is detected to be available, the target application is restarted through the window container control, and an application interface of the target application is embedded in the carrier application through the window container control for displaying. That is, in the embodiment of the present invention, even if the mobile terminal performs memory recovery, which causes the application interface of the target application embedded in the carrier application to be cleared, the target application may be automatically restarted through the window container control, so that the application interface of the target application may still be displayed in the carrier application after the mobile terminal performs memory recovery.
It should be noted that: in the application interface display apparatus provided in the foregoing embodiment, when displaying an application interface, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the functions described above. In addition, the application interface display apparatus and the application interface display method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.
Fig. 4 shows a block diagram of a mobile terminal 400 according to an exemplary embodiment of the present invention. Among them, the mobile terminal 400 may be: industrial computers, industrial personal computers, notebook computers, desktop computers, smart phones or tablet computers, and the like. The mobile terminal 400 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, and the like.
Generally, the mobile terminal 400 includes: a processor 401 and a memory 402.
Processor 401 may include one or more processing cores, such as a 4-core processor, an 8-core processor, or the like. The processor 401 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 401 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 401 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed by the display screen. In some embodiments, the processor 401 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.
Memory 402 may include one or more computer-readable storage media, which may be non-transitory. Memory 402 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 402 is used to store at least one instruction for execution by processor 401 to implement the application interface display method provided by method embodiments herein.
In some embodiments, the mobile terminal 400 may further optionally include: a peripheral interface 403 and at least one peripheral. The processor 401, memory 402 and peripheral interface 403 may be connected by bus or signal lines. Each peripheral may be connected to the peripheral interface 403 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 404, touch screen display 405, camera 406, audio circuitry 407, positioning components 408, and power supply 409.
The peripheral interface 403 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 401 and the memory 402. In some embodiments, processor 401, memory 402, and peripheral interface 403 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 401, the memory 402 and the peripheral interface 403 may be implemented on a separate chip or circuit board, which is not limited by this embodiment.
The Radio Frequency circuit 404 is used to receive and transmit RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 404 communicates with a communication network and other communication devices via electromagnetic signals. The rf circuit 404 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 404 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuitry 404 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: the world wide web, metropolitan area networks, intranets, generations of mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the rf circuit 404 may further include NFC (Near Field Communication) related circuits, which are not limited in this application.
The display screen 405 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 405 is a touch display screen, the display screen 405 also has the ability to capture touch signals on or over the surface of the display screen 405. The touch signal may be input to the processor 401 as a control signal for processing. At this point, the display screen 405 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display screen 405 may be one, providing the front panel of the mobile terminal 400; in other embodiments, the number of the display screens 405 may be at least two, and the two display screens are respectively disposed on different surfaces of the mobile terminal 400 or in a folding design; in still other embodiments, the display 405 may be a flexible display disposed on a curved surface or on a folded surface of the mobile terminal 400. Even further, the display screen 405 may be arranged in a non-rectangular irregular pattern, i.e. a shaped screen. The Display screen 405 may be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), and other materials.
The camera assembly 406 is used to capture images or video. Optionally, camera assembly 406 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 406 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.
The audio circuit 407 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 401 for processing, or inputting the electric signals to the radio frequency circuit 404 for realizing voice communication. The microphones may be provided in a plurality for stereo sound collection or noise reduction, and are respectively disposed at different portions of the mobile terminal 400. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 401 or the radio frequency circuit 404 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, audio circuitry 407 may also include a headphone jack.
The positioning component 408 is used to locate the current geographic Location of the mobile terminal 400 for navigation or LBS (Location Based Service). The Positioning component 408 may be a Positioning component based on the GPS (Global Positioning System) of the united states, the beidou System of china, or the galileo System of the european union.
The power supply 409 is used to supply power to various components in the mobile terminal 400. The power source 409 may be alternating current, direct current, disposable or rechargeable. When the power source 409 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.
In some embodiments, the mobile terminal 400 also includes one or more sensors 410. The one or more sensors 410 include, but are not limited to: acceleration sensor 411, gyro sensor 412, pressure sensor 413, fingerprint sensor 414, optical sensor 415, and proximity sensor 416.
The acceleration sensor 411 may detect the magnitude of acceleration in three coordinate axes of a coordinate system established with the mobile terminal 400. For example, the acceleration sensor 411 may be used to detect components of the gravitational acceleration in three coordinate axes. The processor 401 may control the touch display screen 405 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 411. The acceleration sensor 411 may also be used for acquisition of motion data of a game or a user.
The gyro sensor 412 may detect a body direction and a rotation angle of the mobile terminal 400, and the gyro sensor 412 may collect a 3D motion of the user on the mobile terminal 400 in cooperation with the acceleration sensor 411. From the data collected by the gyro sensor 412, the processor 401 may implement the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization while shooting, game control, and inertial navigation.
The pressure sensor 413 may be disposed at a side bezel of the mobile terminal 400 and/or a lower layer of the touch display screen 405. When the pressure sensor 413 is disposed at a side frame of the mobile terminal 400, a holding signal of the user to the mobile terminal 400 may be detected, and the processor 401 performs left-right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 413. When the pressure sensor 413 is disposed at the lower layer of the touch display screen 405, the processor 401 controls the operability control on the UI interface according to the pressure operation of the user on the touch display screen 405. The operability control comprises at least one of a button control, a scroll bar control, an icon control, and a menu control.
The fingerprint sensor 414 is used for collecting a fingerprint of the user, and the processor 401 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 414, or the fingerprint sensor 414 identifies the identity of the user according to the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, processor 401 authorizes the user to perform relevant sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying, and changing settings, etc. The fingerprint sensor 414 may be disposed on the front, back, or side of the mobile terminal 400. When a physical key or vendor Logo is provided on the mobile terminal 400, the fingerprint sensor 414 may be integrated with the physical key or vendor Logo.
The optical sensor 415 is used to collect the ambient light intensity. In one embodiment, the processor 401 may control the display brightness of the touch screen display 405 according to the ambient light intensity collected by the optical sensor 415. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 405 is increased; when the ambient light intensity is low, the display brightness of the touch display screen 405 is turned down. In another embodiment, the processor 401 may also dynamically adjust the shooting parameters of the camera assembly 406 according to the ambient light intensity collected by the optical sensor 415.
A proximity sensor 416, also known as a distance sensor, is typically disposed on the front panel of the mobile terminal 400. The proximity sensor 416 is used to collect a distance between the user and the front surface of the mobile terminal 400. In one embodiment, when the proximity sensor 416 detects that the distance between the user and the front surface of the mobile terminal 400 gradually decreases, the processor 401 controls the touch display screen 405 to switch from the bright screen state to the dark screen state; when the proximity sensor 416 detects that the distance between the user and the front surface of the mobile terminal 400 becomes gradually larger, the processor 401 controls the touch display screen 405 to switch from the screen-on state to the screen-on state.
That is, not only is an application interface display apparatus provided in the embodiment of the present invention, which can be applied to the mobile terminal 400, and includes a processor and a memory for storing executable instructions of the processor, where the processor is configured to execute the application interface display method provided in the foregoing embodiment, but also a computer-readable storage medium is provided, in which a computer program is stored, and when the computer program is executed by the processor, the application interface display method in the foregoing embodiment can be implemented.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.

Claims (9)

1. An application interface display method, characterized in that the method comprises:
when the target application is detected to be cleared, detecting whether a window container control used for displaying the target application in a carrier application is available, wherein the target application refers to an application which is currently embedded in the carrier application for application interface display, the carrier application is displayed on a main screen, and the window container control comprises a window container corresponding to a virtual screen and a TextureView and a Surface object which are created in the window container;
if the window container control is detected to be available, restarting the target application through the window container control;
embedding an application interface of the target application in the carrier application through the window container control for displaying;
the restarting the target application through the window container control comprises:
and transmitting the virtual screen identifier to a StartActivity function as a display screen parameter, and calling the StartActivity function through the window container control, wherein the StartActivity function is used for triggering the operation of restarting the target application in the virtual screen.
2. The method of claim 1, wherein before detecting whether a window container control in the carrier application for displaying the target application is available, further comprising:
Monitoring whether an application task of the target application is removed;
and if the application task of the target application is removed, determining that the target application is cleared.
3. The method of claim 1, further comprising:
if the window container control is detected to be unavailable, rebuilding the window container control used for displaying the target application in the carrier application;
restarting the target application through the reconstructed window container control, and embedding an application interface of the target application in the carrier application for displaying through the reconstructed window container control.
4. The method of claim 1, wherein the TextureView is used for drawing and displaying an application interface of the target application, and wherein the Surface object includes window information indicating a width, a height, and a screen resolution.
5. The method of claim 4, wherein the embedding and displaying an application interface of the target application in the carrier application through the window container control comprises:
capturing drawing information of the target application through a Surface object in the window container control;
Based on the drawing information, drawing an application interface of the target application through TextureView in the window container control;
and based on the window information, displaying the application interface of the target application on the main screen as a parallel page of the application interface of the carrier application through TextureView in the window container control.
6. The method of claim 1, further comprising:
determining a mapping relationship between the coordinates on the virtual screen and the coordinates on the main screen;
when a touch operation of an application interface for the target application is detected on the home screen, determining coordinates of the touch operation;
and responding to the touch operation through the virtual screen based on the coordinate of the touch operation and the mapping relation.
7. An application interface display apparatus, the apparatus comprising:
the device comprises a detection module, a display module and a display module, wherein the detection module is used for detecting whether a window container control used for displaying a target application in a carrier application is available or not when the target application is detected to be cleared, the target application refers to an application which is currently embedded in the carrier application for application interface display, the carrier application is displayed on a main screen, and the window container control comprises a window container corresponding to a virtual screen and a TextureView and a Surface object which are created in the window container;
The starting module is used for restarting the target application through the window container control if the window container control is detected to be available;
the display module is used for embedding the application interface of the target application into the carrier application through the window container control for displaying;
the start module is further configured to:
and transmitting the virtual screen identifier to a StartActivity function as a display screen parameter, and calling the StartActivity function through the window container control, wherein the StartActivity function is used for triggering the operation of restarting the target application in the virtual screen.
8. The apparatus of claim 7, further comprising:
the monitoring module is used for monitoring whether the application task of the target application is removed;
a determining module, configured to determine that the target application is cleared if the application task of the target application is removed.
9. The apparatus of claim 7, wherein the apparatus is further configured to:
if the window container control is detected to be unavailable, rebuilding the window container control used for displaying the target application in the carrier application;
restarting the target application through the reconstructed window container control, and embedding an application interface of the target application in the carrier application for displaying through the reconstructed window container control.
CN201810285018.9A 2018-04-02 2018-04-02 Application interface display method and device Active CN110362355B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810285018.9A CN110362355B (en) 2018-04-02 2018-04-02 Application interface display method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810285018.9A CN110362355B (en) 2018-04-02 2018-04-02 Application interface display method and device

Publications (2)

Publication Number Publication Date
CN110362355A CN110362355A (en) 2019-10-22
CN110362355B true CN110362355B (en) 2022-06-28

Family

ID=68213524

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810285018.9A Active CN110362355B (en) 2018-04-02 2018-04-02 Application interface display method and device

Country Status (1)

Country Link
CN (1) CN110362355B (en)

Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102799385A (en) * 2012-07-19 2012-11-28 腾讯科技(深圳)有限公司 Desktop control method and device
CN103064724A (en) * 2012-12-14 2013-04-24 北京伸得纬科技有限公司 Virtual mechanism constructing method and device
CN104798355A (en) * 2012-09-18 2015-07-22 思杰系统有限公司 Mobile device management and security
CN104965718A (en) * 2014-06-20 2015-10-07 腾讯科技(深圳)有限公司 Method and apparatus for desktop loading
CN104995601A (en) * 2013-03-15 2015-10-21 谷歌公司 Switching to and from native web applications
CN105005519A (en) * 2014-04-17 2015-10-28 腾讯科技(深圳)有限公司 Method and device for clearing client cache
CN105630461A (en) * 2014-10-27 2016-06-01 航天信息股份有限公司 Managing method of android application interface
CN106020930A (en) * 2016-05-13 2016-10-12 深圳市中润四方信息技术有限公司 Application container based application management method and system
CN106126236A (en) * 2016-06-24 2016-11-16 北京奇虎科技有限公司 The multi-screen display method of terminal screen, device and terminal
CN106528224A (en) * 2016-11-03 2017-03-22 腾讯科技(深圳)有限公司 Content updating method and system for Docker container, and server
CN106598656A (en) * 2016-12-07 2017-04-26 北京奇虎科技有限公司 Mobile terminal and starting method and apparatus for banned application therefor
CN106598783A (en) * 2016-12-06 2017-04-26 广东欧珀移动通信有限公司 Intelligent terminal display control method and device and intelligent terminal
CN106648869A (en) * 2016-12-26 2017-05-10 竞技世界(北京)网络技术有限公司 Intelligent terminal application switch method
CN106815041A (en) * 2016-11-24 2017-06-09 北京奇虎科技有限公司 The loading method and device of application program entry information in task manager
CN107391199A (en) * 2017-07-27 2017-11-24 珠海市魅族科技有限公司 Using startup method and device, terminal and computer-readable recording medium
CN107545188A (en) * 2016-06-27 2018-01-05 南京中兴软件有限责任公司 The management method of application, apparatus and system
CN107783803A (en) * 2017-11-21 2018-03-09 广东欧珀移动通信有限公司 System optimization method, device, storage medium and the intelligent terminal of intelligent terminal

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7274304B2 (en) * 2004-07-27 2007-09-25 Intelliserv, Inc. System for loading executable code into volatile memory in a downhole tool
US20070074156A1 (en) * 2005-09-01 2007-03-29 Microsoft Corporation Componentization of software computer programs
EP2497547B1 (en) * 2011-03-08 2018-06-27 Nintendo Co., Ltd. Information processing program, information processing apparatus, information processing system, and information processing method

Patent Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102799385A (en) * 2012-07-19 2012-11-28 腾讯科技(深圳)有限公司 Desktop control method and device
CN104798355A (en) * 2012-09-18 2015-07-22 思杰系统有限公司 Mobile device management and security
CN103064724A (en) * 2012-12-14 2013-04-24 北京伸得纬科技有限公司 Virtual mechanism constructing method and device
CN104995601A (en) * 2013-03-15 2015-10-21 谷歌公司 Switching to and from native web applications
CN105005519A (en) * 2014-04-17 2015-10-28 腾讯科技(深圳)有限公司 Method and device for clearing client cache
CN104965718A (en) * 2014-06-20 2015-10-07 腾讯科技(深圳)有限公司 Method and apparatus for desktop loading
CN105630461A (en) * 2014-10-27 2016-06-01 航天信息股份有限公司 Managing method of android application interface
CN106020930A (en) * 2016-05-13 2016-10-12 深圳市中润四方信息技术有限公司 Application container based application management method and system
CN106126236A (en) * 2016-06-24 2016-11-16 北京奇虎科技有限公司 The multi-screen display method of terminal screen, device and terminal
CN107545188A (en) * 2016-06-27 2018-01-05 南京中兴软件有限责任公司 The management method of application, apparatus and system
CN106528224A (en) * 2016-11-03 2017-03-22 腾讯科技(深圳)有限公司 Content updating method and system for Docker container, and server
CN106815041A (en) * 2016-11-24 2017-06-09 北京奇虎科技有限公司 The loading method and device of application program entry information in task manager
CN106598783A (en) * 2016-12-06 2017-04-26 广东欧珀移动通信有限公司 Intelligent terminal display control method and device and intelligent terminal
CN106598656A (en) * 2016-12-07 2017-04-26 北京奇虎科技有限公司 Mobile terminal and starting method and apparatus for banned application therefor
CN106648869A (en) * 2016-12-26 2017-05-10 竞技世界(北京)网络技术有限公司 Intelligent terminal application switch method
CN107391199A (en) * 2017-07-27 2017-11-24 珠海市魅族科技有限公司 Using startup method and device, terminal and computer-readable recording medium
CN107783803A (en) * 2017-11-21 2018-03-09 广东欧珀移动通信有限公司 System optimization method, device, storage medium and the intelligent terminal of intelligent terminal

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
5大战役 兄弟连夺""保卫战――全面掌控Windows多用户;Cornel等;《电脑爱好者》;20080515(第10期);第20-27页 *

Also Published As

Publication number Publication date
CN110362355A (en) 2019-10-22

Similar Documents

Publication Publication Date Title
CN110308956B (en) Application interface display method and device and mobile terminal
CN110602321B (en) Application program switching method and device, electronic device and storage medium
CN108449641B (en) Method, device, computer equipment and storage medium for playing media stream
CN110362366B (en) Application interface display method and device
CN110288689B (en) Method and device for rendering electronic map
CN110007981B (en) Method and device for starting application program, electronic equipment and medium
CN110839174A (en) Image processing method and device, computer equipment and storage medium
CN110677713B (en) Video image processing method and device and storage medium
CN109783176B (en) Page switching method and device
CN110769120A (en) Method, device, equipment and storage medium for message reminding
CN111191227A (en) Method and device for preventing malicious code from executing
CN111897465B (en) Popup display method, device, equipment and storage medium
CN107943484B (en) Method and device for executing business function
CN110868642B (en) Video playing method, device and storage medium
CN111857938A (en) Management method and device of popup view, terminal and storage medium
CN111275607A (en) Interface display method and device, computer equipment and storage medium
CN112181915A (en) Method, device, terminal and storage medium for executing service
CN111464829B (en) Method, device and equipment for switching media data and storage medium
CN112015612B (en) Method and device for acquiring stuck information
CN110362355B (en) Application interface display method and device
CN112202966B (en) Communication information notification method and device and computer readable storage medium
CN113843814A (en) Control system, method, device and storage medium for mechanical arm equipment
CN110471613B (en) Data storage method, data reading method, device and system
CN111930438A (en) Method, device and equipment for determining page loading duration and storage medium
CN110941458A (en) Method, device and equipment for starting application program and storage 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
CP01 Change in the name or title of a patent holder
CP01 Change in the name or title of a patent holder

Address after: 266071 Shandong city of Qingdao province Jiangxi City Road No. 11

Patentee after: Qingdao Hisense Mobile Communication Technology Co.,Ltd.

Address before: 266071 Shandong city of Qingdao province Jiangxi City Road No. 11

Patentee before: HISENSE MOBILE COMMUNICATIONS TECHNOLOGY Co.,Ltd.