Display device, application resolution mode switching method, computer readable storage medium, and program product

CN122845863APending Publication Date: 2026-09-29HISENSE VISUAL TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610796261.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-06-03
Publication Date
2026-09-29

AI Technical Summary

Technical Problem

[0003]智能电视的操作系统往往可以支持输出多种分辨率模式,然而,相关技术中的智能电视往往只能支持分辨率模式的全局切换

Benefits of technology

[0026]本实施例具有如下有益效果:通过响应于操作系统的初始化满足预设条件,调用操作系统中的XML文件解析器,对分辨率映射配置文件进行解析,以实现构建应用包名为键、组件分辨率配置列表为值的哈希映射索引,实现在后续响应分辨率切换事件时,可以快速地基于分辨率配置查询对象这一配置数据载体快速地查询出目标应用的目标应用组件的分辨率配置,有效地提升了分辨率切换的决策效率,缩短了切换命令的响应延迟。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122845863A_ABST
    Figure CN122845863A_ABST
Patent Text Reader

Abstract

The application relates to a display device, an application resolution mode switching method, a computer readable storage medium and a program product. The method comprises the following steps: parsing a resolution mapping configuration file and constructing a resolution configuration query object; in response to a resolution switching event, obtaining an application package name of a target application; the target application is one of each preset application; according to the application package name of the target application, determining a target resolution mode of a target application component corresponding to the target application from the resolution configuration query object, and recording component state description data of the target application component; the target application component is a running application component; according to the target resolution mode of the target application component, switching the display resolution of the target application component on a corresponding layer of a user graphical interface, and according to the component state description data of the target application component, re-establishing the component state of the target application component. The method can improve the control accuracy of the resolution mode of the display device.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of display technology, and in particular to a display device, a method for switching application resolution modes, a computer-readable storage medium, and a computer program product. Background Technology

[0002] A smart TV is a display device equipped with an operating system. Users can install various applications on the smart TV's operating system, enabling it to not only watch live broadcasts but also enjoy various functions such as audio-visual entertainment and games.

[0003] Smart TV operating systems often support multiple resolution modes; however, smart TVs using this technology typically only support global switching of resolution modes. For example, when a user switches a smart TV from 4K mode to 1080p mode, the operating system often needs to restart to achieve the overall resolution switch, forcing all background applications to be rebuilt.

[0004] Therefore, the related technologies suffer from the problem of low precision in controlling the resolution mode of display devices. Summary of the Invention

[0005] Therefore, it is necessary to address the aforementioned technical problems by providing a display device, a resolution mode switching method, a computer-readable storage medium, and a computer program product that can improve the control accuracy of the resolution mode of the display device.

[0006] In a first aspect, this application provides a display device, comprising:

[0007] The monitor is configured to display a user graphical interface;

[0008] The memory is configured to store an operating system, the target partition of which stores a resolution mapping configuration file; the resolution mapping configuration file is used to record the resolution control policies configured for application components of a preset application; the resolution mapping configuration file uses multi-level application identifiers to represent the application components;

[0009] The controller, connected to the display and the memory, is configured to:

[0010] The resolution mapping configuration file is parsed to construct a resolution configuration query object; the resolution configuration query object is indexed by the application package name and records the target resolution mode of at least one application component corresponding to each preset application.

[0011] In response to a resolution switching event, the application package name of the target application is obtained; the target application is one of the preset applications.

[0012] Based on the application package name of the target application, determine the target resolution mode of the target application component corresponding to the target application from the resolution configuration query object, and record the component status description data of the target application component; the target application component is a running application component;

[0013] According to the target resolution mode of the target application component, switch the display resolution of the corresponding layer of the target application component in the user graphical interface, and restore the component state of the target application component according to the component state description data of the target application component.

[0014] This embodiment has the following beneficial effects: By deploying a resolution mapping configuration file in the target partition of the operating system of the display device, the resolution mapping configuration file is used to record the resolution control strategy matching the application components of the preset application. By parsing the resolution mapping configuration file, an indexed resolution configuration query object is constructed, which enables the target resolution mode of the specific application component of the target application to be quickly matched according to the application package name of the target application when a resolution switching event occurs. Before the resolution mode switch, the component status description data of the specific application component is recorded. After the resolution mode switch, the working state of the target component is restored according to the component status description data of the specific application component. This allows the display device to achieve fine-grained dynamic resolution switching for a single application or a specific application component within an application without the need for a global interruption or restart of the operating system. This effectively avoids the problem of interruption of other application operation or data loss caused by resolution switching, improves the stability of the system in multi-resolution scenarios, and effectively improves the control accuracy of the resolution mode of the display device.

[0015] In one embodiment, in the step of recording the component state description data of the target application component, the controller is configured to:

[0016] Obtain a snapshot of the currently running tasks of the operating system;

[0017] If the target application component is determined to be a running application component based on the current running task snapshot, the component status description data of the target application component is obtained;

[0018] The component status description data includes at least one of the following: current task record, current interface status, service connection status, and service frontend status.

[0019] This embodiment has the following beneficial effects: by acquiring a snapshot of the currently running task, and determining that the target application component is a running application component based on the snapshot of the currently running task, the complete running status record of the target application component is collected at once, including task records, interface status, service connection status, etc., which provides sufficient and accurate data support for the subsequent seamless recovery of the target application component, ensuring that the resolution switching process is zero-perceptible to the user and optimizing the continuity of resolution mode switching.

[0020] In one embodiment, the multi-level application identifier includes at least two of the following: application package name, component type, and process name; the application component includes at least one of the following: front-end interface component or back-end service component.

[0021] This embodiment has the following beneficial effects: by setting the multi-level application identifier to include at least two of the following: application package name, component type and process name, the resolution control granularity can be refined to a specific process or a specific type of component, avoiding misoperation or performance overhead caused by overall matching.

[0022] In one embodiment, the resolution mapping configuration file is in XML format. In the step of parsing the resolution mapping configuration file and constructing a resolution configuration query object, the controller is configured to:

[0023] In response to the operating system initialization meeting preset conditions, the XML file parser in the operating system is invoked;

[0024] The resolution mapping configuration file is parsed by the XML file parser, and a hash mapping index is constructed with the application package name as the key and the component resolution configuration list as the value to obtain the resolution configuration query object.

[0025] The component resolution configuration list includes at least the target resolution mode, application component type, application component identifier, running status marker, and visibility marker of the application component corresponding to the preset application.

[0026] This embodiment has the following beneficial effects: by responding to the initialization of the operating system and meeting the preset conditions, the XML file parser in the operating system is called to parse the resolution mapping configuration file, so as to build a hash mapping index with the application package name as the key and the component resolution configuration list as the value. This enables the resolution configuration of the target application component to be quickly queried based on the resolution configuration query object as the configuration data carrier when responding to the resolution switching event in the future, which effectively improves the decision efficiency of resolution switching and shortens the response delay of the switching command.

[0027] In one embodiment, the controller is further configured to:

[0028] Based on the application package name of the target application, query whether the target application is a whitelisted application; the whitelisted application is an application that the operating system needs to run continuously.

[0029] If the target application is not a whitelisted application, the step of recording the component state description data of the target application components is executed;

[0030] If the target application is a whitelisted application, the canvas size of the window corresponding to the target application component is updated through the window manager of the operating system to switch the target application component to the target resolution mode.

[0031] This embodiment has the following beneficial effects: By introducing a whitelist protection mechanism, for critical system applications (such as live streaming applications and system settings), the controller only adjusts the canvas size of the target application component through the window manager, without performing a stop-and-restart process on the target application component. This ensures that when users are watching live streams or performing critical operations such as system settings, service interruption or interface flickering will not occur due to application restart.

[0032] In one embodiment, the controller is further configured to:

[0033] In response to receiving an OTA upgrade package from the operating system, extract resolution configuration update data from the OTA upgrade package;

[0034] Update the resolution mapping configuration file stored in the target partition of the operating system according to the resolution configuration update data.

[0035] This embodiment has the following beneficial effects: by responding to the received OTA upgrade package of the operating system, extracting the resolution configuration update data from the OTA upgrade package, and updating the resolution mapping configuration file stored in the target partition of the operating system, it is possible to dynamically update the resolution mapping configuration file through OTA upgrade, quickly adjust the resolution switching strategy of preset applications, and eliminate the need to push a complete system firmware version.

[0036] In one embodiment, in the step of switching the display resolution of the target application component on the corresponding layer of the user graphical interface according to the target resolution mode of the target application component, the controller is configured to:

[0037] Traverse all layers of the operating system and match the layer corresponding to the target application component in the user graphical interface to obtain the target application layer;

[0038] According to the target resolution mode of the target application component, the target display resolution of the target application layer is set, and a resolution conversion flag is added to the target application layer; the resolution conversion flag is used to instruct the hardware compositor of the operating system to convert the current display resolution of the target application layer;

[0039] The hardware synthesizer switches the current display resolution of the target application layer to the target display resolution.

[0040] This embodiment has the following beneficial effects: by setting a resolution conversion mark on the target application layer corresponding to the user's graphical interface in the target application component, and having the hardware synthesizer (HWC) directly perform the buffer resolution conversion at the hardware level, the complex software scaling of the GPU is avoided, effectively reducing the GPU load and system power consumption.

[0041] Secondly, this application also provides an application resolution mode switching method applied to a display device, wherein the target partition of the operating system of the display device stores a resolution mapping configuration file, the resolution mapping configuration file being used to record the resolution control strategy configured for application components of a preset application; the resolution mapping configuration file uses multi-level application identifiers to represent the application components, and the method includes:

[0042] The resolution mapping configuration file is parsed to construct a resolution configuration query object; the resolution configuration query object is indexed by the application package name and records the target resolution mode of at least one application component corresponding to each preset application.

[0043] In response to a resolution switching event, the application package name of the target application is obtained; the target application is one of the preset applications.

[0044] Based on the application package name of the target application, determine the target resolution mode of the target application component corresponding to the target application from the resolution configuration query object, and record the component status description data of the target application component; the target application component is a running application component;

[0045] According to the target resolution mode of the target application component, switch the display resolution of the corresponding layer of the target application component in the user graphical interface, and restore the component state of the target application component according to the component state description data of the target application component.

[0046] Thirdly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the second aspect.

[0047] Fourthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in the second aspect.

[0048] The aforementioned display device, application resolution mode switching method, computer-readable storage medium, and computer program product deploy a resolution mapping configuration file in the target partition of the operating system of the display device. This configuration file records the resolution control strategies that match the application components of a preset application. By parsing the resolution mapping configuration file, an indexed resolution configuration query object is constructed. This allows the target resolution mode of a specific application component of the target application to be quickly matched based on the application package name of the target application when a resolution switching event occurs. Before the resolution mode switch, the component state description data of the specific application component is recorded. After the resolution mode switch, the working state of the target component is restored based on the component state description data of the specific application component. This enables the display device to achieve fine-grained dynamic resolution switching for a single application or a specific application component within an application without the need for a global interruption or restart of the operating system. This effectively avoids the problem of interruption of other application operation or data loss caused by resolution switching, improves the stability of the system in multi-resolution scenarios, and effectively improves the control accuracy of the display device's resolution mode. Attached Figure Description

[0049] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device provided in some embodiments of this application;

[0051] Figure 2 This is a schematic diagram of the hardware configuration of a display device provided in some embodiments of this application;

[0052] Figure 3 This is a schematic diagram of the hardware configuration of the control device provided in some embodiments of this application;

[0053] Figure 4 This is a schematic diagram of the software configuration of a display device provided in some embodiments of this application;

[0054] Figure 5 A flowchart illustrating an application resolution switching method provided in some embodiments of this application;

[0055] Figure 6 A flowchart illustrating another application resolution switching method provided in some embodiments of this application;

[0056] Figure 7 A structural block diagram of an application resolution switching device provided in some embodiments of this application;

[0057] Figure 8 A schematic diagram of the structure of a resolution mode switching system provided in some embodiments of this application;

[0058] Figure 9 A resolution switching timing flowchart is provided for some embodiments of this application;

[0059] Figure 10 This application provides an internal structural diagram of a computer device according to some embodiments. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0061] The embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described below do not represent all embodiments consistent with this application. They are merely examples of systems and methods consistent with some aspects of this application as detailed in the claims.

[0062] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0063] In this application, the terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence, unless otherwise specified. It should be understood that such terms can be used interchangeably where appropriate. In the embodiments of this application, "display device 200" generally refers to a device with screen display and data processing capabilities. For example, display device 200 includes, but is not limited to, smart TVs, mobile terminals, computers, monitors, advertising screens, wearable devices, virtual reality devices, augmented reality devices, etc.

[0064] Figure 1This is a schematic diagram illustrating an operational scenario between a display device and a control device provided in some embodiments of this application. For example... Figure 1 As shown, a user can operate the display device 200 via touch operation, a mobile terminal 300, and a control device 100. For example, the control device 100 can be a remote control, a stylus, a gamepad, etc. The mobile terminal 300 can serve as a control device for human-computer interaction between the user and the display device 200. The mobile terminal 300 can also serve as a communication device for establishing a communication connection with the display device 200 and exchanging data. In some embodiments, the mobile terminal 300 can have software applications installed on it and connect to the display device 200 via network communication protocols to achieve one-to-one control operation and data communication. Audio and video content displayed on the mobile terminal 300 can also be transmitted to the display device 200 to achieve synchronous display. Figure 1 The diagram also shows that the display device 200 communicates with the server 400 via various communication methods. The display device 200 can communicate via a local area network (LAN), a wireless local area network (WLAN), and other networks. The display device 200 can provide broadcast television reception functionality and can also be additionally equipped with intelligent network television functionality that provides computer support, including but not limited to, internet television, smart television, and Internet Protocol television (IPTV).

[0065] Figure 2 Provided for some embodiments of this application Figure 1The diagram shows the hardware configuration of the display device 200. In some embodiments, the display device 200 may include at least one of a tuner / demodulator 210, a communication device 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output device 270, a memory, a power supply, and a user input interface. In some embodiments, the detector 230 is used to collect signals from the external environment or to interact with the external environment. For example, the detector 230 includes a light receiver, a sensor for collecting ambient light intensity; or, the detector 230 includes an image acquisition device, such as a camera, which can be used to collect external environmental scenes, user attributes, or user interaction gestures; or, the detector 230 includes a sound acquisition device, such as a microphone, for receiving external sounds. In some embodiments, the display 260 includes display function components for presenting images and driving components for driving image display. The display 260 is used to receive and display image signals output from the controller 250. For example, the display 260 can be used to display video content, image content, menu control interface components, and user control UI interfaces, etc. In some embodiments, a touch component connected to the display 260 is further included. The touch component is used to receive touch operations from the user, and the display 260 is also used to display the display effect corresponding to the user's touch operation. In some embodiments, the communication device 220 is a component used to communicate with external devices or the server 400 according to various communication protocol types. The display device 200 may be equipped with multiple communication devices 220 depending on the supported communication methods. For example, when the display device 200 supports wireless network communication, it may be equipped with a communication device 220 that includes WiFi functionality. When the display device 200 supports Bluetooth connection communication, it needs to be equipped with a communication device 220 that includes Bluetooth functionality. The communication device 220 can enable the display device 200 to communicate with external devices or the server 400 through wireless or wired connections. Wired connections can connect the display device 200 to external devices through components such as data cables and interfaces. Wireless connections can connect the display device 200 to external devices through wireless signals or wireless networks. The display device 200 can directly establish a connection with external devices, or it can indirectly establish a connection through gateways, routers, connection devices, etc. In some embodiments, the controller 250 may include at least one of a central processing unit, a video processor, an audio processor, a graphics processor, and a power processor, and provide a first to an nth interface for input / output. The controller 250 controls the operation of the display device and responds to user operations through various software control programs stored in memory. The controller 250 controls the overall operation of the display device 200. In some embodiments, the controller 250 and the tuner / demodulator 210 may be located in different separate devices; that is, the tuner / demodulator 210 may also be located in an external device of the main device where the controller 250 is located, such as an external set-top box.

[0066] In some embodiments, a user can input user commands through a graphical user interface (GUI) displayed on a display 260, and the user input interface receives user input commands through the graphical user interface (GUI).

[0067] In some embodiments, the audio output device 270 can be a built-in speaker of the display device 200 or an external audio output device connected to the display device 200. For the external audio output device connected to the display device 200, the display device 200 may also be provided with an external audio output terminal, through which the audio output device can be connected to the display device 200 to output sound from the display device 200.

[0068] In some embodiments, the user input interface 280 can be used to receive instructions from user input.

[0069] Figure 3 Provided for some embodiments of this application Figure 1 Hardware configuration block diagram of the central control device. (Example) Figure 3 As shown, the control device 100 may include: a controller 110, a communication interface 130, a user input / output interface, a memory, and a power supply.

[0070] The control device 100 is configured to control the display device 200, and to receive user input operation commands and convert the operation commands into commands that the display device 200 can recognize and respond to, thus acting as an intermediary for interaction between the user and the display device 200.

[0071] In some embodiments, the control device 100 may be an intelligent device. For example, the control device 100 may be equipped with various applications for controlling the display device 200 according to user needs.

[0072] In some embodiments, such as Figure 1 As shown, the mobile terminal 300 or other smart electronic devices can perform similar functions to the control device 100 after installing the application of the control display device 200.

[0073] The controller 110 includes a processor 112, RAM 113, ROM 114, a communication interface 130, and a communication bus. The controller 110 is used to control the operation of the control device 100, as well as the communication and cooperation between internal components and the external and internal data processing functions.

[0074] Under the control of the controller 110, the communication interface 130 enables communication of control signals and data signals with the display device 200. The communication interface 130 may include at least one of other near-field communication modules such as WiFi chip 131, Bluetooth module 132, and NFC module 133.

[0075] User input / output interface 140, wherein the input interface includes at least one of other input interfaces such as microphone 141, touchpad 142, sensor 143, and button 144.

[0076] In some embodiments, the buttons 144 configured on the control device 100 may include basic buttons, such as a power button, number keys, arrow keys, volume keys, home button, and back button. Users can control the display device 200 to perform corresponding functions using these basic buttons. The buttons 144 configured on the control device 100 may also include special buttons, such as color keys, allowing users to control the display device 200 to perform specific functions in different scenarios using these special buttons.

[0077] In some embodiments, the control device 100 includes at least one of a communication interface 130 and an input / output interface 140. The control device 100 is configured with the communication interface 130, such as a WiFi, Bluetooth, or NFC module, which can encode user input commands via WiFi, Bluetooth, or NFC protocols and send them to the display device 200.

[0078] The memory 190 is used to store various operating programs, data, and applications for driving and controlling the control device 100 under the control of the controller. The memory 190 can also store various control signal instructions input by the user.

[0079] The power supply 180 is used to provide operating power support for the various components of the control device 100 under the control of the controller.

[0080] In some embodiments, the display device 200 may run an operating system to enable user interaction. An operating system is a computer program that manages and controls the hardware and software resources of the display device 200. The operating system can (control the display device) provide a user interface, allowing users to interact with the display device 200 and supporting the running of various applications.

[0081] It should be noted that the operating system can be a native operating system based on a specific operating platform, a third-party operating system that is deeply customized based on a specific operating platform, or an independent operating system specifically developed for display devices.

[0082] An operating system can be divided into different modules or levels based on the functions it implements, for example... Figure 4 As shown, in some embodiments, the system is divided into four layers, from top to bottom: the Applications layer (referred to as the "Application Layer"), the Application Framework layer (referred to as the "Framework Layer"), the System Library layer, and the Kernel layer.

[0083] In some embodiments, the application layer provides services and interfaces for applications, enabling the display device 200 to run applications and interact with the user based on the applications. The application layer may contain at least one application, which may be a built-in Windows program, system settings program, or clock program of the operating system; or it may be an application developed by a third-party developer. In specific implementations, the application packages in the application layer are not limited to the examples above.

[0084] The framework layer provides application programming interfaces (APIs) and a programming framework for applications. The application framework layer includes predefined functions. It acts as a central processing unit, determining the actions taken by applications within the application layer. Through the API, applications can access system resources and obtain system services during execution.

[0085] like Figure 4 As shown, the application framework layer in this embodiment includes a view system, managers, and content providers. The view system designs and implements the application's interface and interactions, and includes lists, grids, text boxes, and buttons. The managers include at least one of the following modules: an activity manager for interacting with all running activities in the system; a location manager for providing system services or applications with access to system location services; a package manager for retrieving various information related to application packages currently installed on the device; a notification manager for controlling the display and clearing of notification messages; and a window manager for managing icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0086] In some embodiments, the Activity Manager manages the lifecycle of individual applications and common navigation and back functions, such as controlling application exit, opening, and back actions. The Window Manager manages all window programs, such as obtaining the screen size, determining if a status bar is present, locking the screen, capturing the screen, and controlling changes to the display window, such as shrinking the display window, shaking the display, or distorting the display.

[0087] In some embodiments, the system runtime library layer can provide support for the framework layer. When the framework layer is used, the operating system runs the instruction library contained in the system runtime library layer, such as the C / C++ instruction library, to implement the functions to be performed by the framework layer.

[0088] In some embodiments, the kernel layer is a functional layer between the hardware and software of the display device 200, and can implement functions such as hardware abstraction, multitasking, and memory management. For example, Figure 4 As shown, hardware drivers can be configured in the kernel layer. The kernel layer can contain at least one of the following drivers: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver, etc.

[0089] It should be noted that the above examples are merely a simple division of operating system functions and do not limit the specific form of the operating system of the display device 200 in this application embodiment. Depending on the function of the display device, the type of operating system, and other factors, the number of levels and the specific level type of the operating system may be expressed in other forms.

[0090] In one exemplary embodiment, a resolution mapping profile can be deployed in the target partition of the operating system of the display device 200.

[0091] The target partition can refer to the system partition.

[0092] The resolution mapping configuration file is used to record the resolution control strategy that matches the application rendering object of the preset application, based on the multi-level application identifier.

[0093] The application rendering object can include at least one of the following: application components (components of type Activity / Service, i.e., front-end interface components or back-end service components) or application processes.

[0094] In practical applications, multi-level application identifiers can include at least two of the following: application package name, component type (Activity / Service), and process name (ProcessName), enabling multi-dimensional matching. This allows for querying the resolution control strategy, such as the target resolution mode, that matches the application rendering object based on its multi-level application identifiers. In other words, the resolution mapping configuration file records the mapping relationship between the multi-level application identifiers corresponding to the application rendering object of a preset application and the resolution control strategy.

[0095] In practice, the resolution mapping configuration file can be deployed in the system partition / system / etc / or / vendor / etc / of the operating system of the display device 200. This resolution mapping configuration file can be named "ui_resolution_packages.xml". Specifically, the resolution mapping configuration file can use multi-level application identifiers as matching conditions to record the resolution control policies or resolution rules that match the application rendering objects of preset applications.

[0096] For ease of understanding by those skilled in the art, a portion of the resolution mapping configuration file content is shown below:

[0097] “

[0098] <package mode="4k" item="应用包名1">

[0099] <activity processname="进程A"> Activity component 1< / activity>

[0100] <activity processname="进程B >Activity component 2< / activity>

[0101] ​< / activity> < / package>

[0102] "

[0103] The aforementioned portion of the file content indicates that two Activity components (i.e., application rendering objects) of a preset application with the application package name "Application Package Name 1" are configured for 4K resolution mode; these two Activity components include:

[0104] 1: Activity component 1, running in process A;

[0105] 2: Activity component 2, running in process B.

[0106] The contents of the resolution mapping configuration file can also be shown below:

[0107] “

[0108] <package mode="4k" item="应用包名2>

[0109] <service class="class name 1"

[0110] action="action 1" / >

[0111] "

[0112] Wherein, the above partial file content means that the Service component of the preset application with the corresponding application package name "application package name 2" is configured to the 4K resolution mode, wherein the class name identifier (Service Class) of the Service component is "class name 1", and the action identifier (service Action) of the Service component is "action 1".

[0113] Wherein, the Mode attribute in the resolution mapping configuration file is used to define the target resolution mode (4k / 2k / 1080p / 720p); the Item attribute is used to match the application package name and supports partial matching; the ProcessName attribute is used for separate resolution configuration of multiple processes of a multi-process application, avoiding the performance overhead of the main process being affected; the class name identifier (Service Class) and the action identifier (service Action) of the Service component are used to accurately match background services, solving the ambiguity problem of implicit Intent parsing.

[0114] As Figure 5 shown, an application resolution mode switching method is provided. Taking the application of this method to the controller of a display device in Figure 1 as an example for description, the controller is configured to execute the following steps S502 to S508. Wherein:

[0115] Step S502: parsing a resolution mapping configuration file to construct a resolution configuration query object; the resolution configuration query object uses an application package name as an index, and records a target resolution mode of at least one application component corresponding to each preset application.

[0116] In specific implementation, when the initialization of the operating system satisfies a preset condition, the controller may invoke an XML file parser at the bottom layer of the operating system (such as XmlPullParser) to parse the aforementioned resolution mapping configuration file and construct the resolution configuration query object.

[0117] The resolution configuration query object uses an application package name as an index and records the target resolution mode of at least one application component corresponding to each preset application, thereby realizing that the resolution configuration query object is used as a data carrier for runtime configuration. In this way, the controller can quickly query the resolution configuration information of the application corresponding to the application package name from the resolution configuration query object based on the application package name.

[0118] Step S504: In response to the resolution switching event, obtain the application package name of the target application; the target application is one of the preset applications.

[0119] The resolution switching event can refer to an event that triggers the controller to perform a resolution switching operation. For example, it may be triggered by the detection of application startup, application switching, hardware status changes (such as HDMI hot-plugging, resolution refresh rate timing changes, HDR mode switching) or system load changes (such as CPU / GPU utilization exceeding a preset utilization triggering resolution switching, temperature sensor temperature value exceeding a preset temperature value triggering resolution switching).

[0120] In the specific implementation, the controller can respond to the resolution switching event and obtain the event-triggered application of the resolution mode to be adjusted; then, it can determine whether the event-triggered application is a preset application configured in the resolution mapping configuration file; specifically, the controller can obtain the application package name of the event-triggered application; then, it can determine whether the application package name of the event-triggered application is in the application package name list; where the application package name list is a list of package names of each preset application.

[0121] If the application package name of the application that triggered the event is in the above application package name list, the application that triggered the event is determined to be the target application, and the application package name of the target application is obtained.

[0122] Step S506: Based on the application package name of the target application, determine the target resolution mode of the target application component corresponding to the target application from the resolution configuration query object, and record the component status description data of the target application component.

[0123] The target application component is the application component that is currently running.

[0124] In practice, the controller determines the target resolution mode of the running application component (i.e., the target application component) based on the obtained application package name of the target application from the previously constructed resolution configuration query object. For example, if the target application is com.example.window and its WinService is running, then the resolution of the WinService is determined to be "4k".

[0125] Simultaneously, the controller records the current component state description data of the target application component. Specifically, the controller can obtain all currently running Tasks in the application system through the RootWindowContainer, and obtain a Task stack snapshot. Based on the Task stack snapshot, the controller determines the application component currently running in the target application, i.e., the target application component.

[0126] Step S508: According to the target resolution mode of the target application component, switch the display resolution of the corresponding layer of the target application component in the user graphical interface, and restore the component state of the target application component according to the component state description data of the target application component.

[0127] In practice, the controller switches the display resolution of the corresponding layer of the target application component in the user's graphical interface according to the target resolution mode of the target application component. Specifically, the controller can pause the operation of the target application component and save its component state description data. Then, the controller switches the display resolution of the corresponding layer of the target application component in the user's graphical interface according to the target resolution mode of the target application component.

[0128] After the switch is complete, the controller restores the running state of the target application component based on the previously recorded component state description data. For example, it restores the Activity component to the foreground and displays the interface previously saved by the Activity component, or restores the Service component to the running state and rebinds the Service component's Surface.

[0129] Activity restart: Build a new Intent, inject FLAG_ACTIVITY_NEW_TAS and FLAG_RESUME_WHILE_PAUSING, and start it through ActivityStartController; if the original Activity is visible, add avoidMoveToFront=false to ensure it returns to the foreground; if it is a background Activity, add avoidMoveToFront=true to keep it in the background.

[0130] Service restart: Construct an explicit Intent containing componentClassName and serviceAction, and call ActiveServices.startServiceLocked() to ensure that the Service is initialized in the new resolution process environment.

[0131] The aforementioned display device deploys a resolution mapping configuration file in the target partition of its operating system. This configuration file records the resolution control strategies that match the application components of a preset application. By parsing this configuration file, an indexed resolution configuration query object is constructed. This allows the device to quickly match the target resolution mode of a specific application component of the target application based on the application package name when a resolution switching event occurs. Before the resolution mode switch, the device records the component status description data of the specific application component. After the resolution mode switch, the device restores the working state of the target component based on the component status description data. This enables the display device to achieve fine-grained dynamic resolution switching for a single application or a specific application component within an application without requiring a global interruption or restart of the operating system. This effectively avoids the problem of interruption of other application operations or data loss caused by resolution switching, improves the stability of the system in multi-resolution scenarios, and effectively improves the control accuracy of the display device's resolution mode.

[0132] In an exemplary embodiment, in the step of recording component state description data of the target application component, the controller is configured to:

[0133] Get a snapshot of the operating system's currently running tasks;

[0134] Based on the current running task snapshot, obtain the component state description data of the target application component;

[0135] The component status description data includes at least one of the following: current task record, current interface status, service connection status, and service frontend status.

[0136] In practice, the controller can obtain all running tasks of the operating system through the operating system's RootWindowContainer, and obtain a snapshot of the currently running tasks. Then, based on the snapshot of the currently running tasks, it can determine whether the target application component is a running application component; if the target application component is a running application component, the controller can obtain and save the component state description data of the target application component.

[0137] Then, the controller can iterate through the Task stack in the snapshot of currently running tasks, constructing a hash map index (HashMap, Task map) with the application package name as the key and the Task as the value. Simultaneously, the controller can check if the target application's application package name is in the aforementioned Task map. If the target application's application package name is in the aforementioned Task map, a running flag can be set for the target application to indicate that the target application is running.

[0138] Simultaneously, the controller can mark the running and visible states of target application components based on their component types, and record the component state description data of the target application components. Specifically:

[0139] For components of the target application that are of type Activity: the controller can check if the application package name is in the Task mapping. If it exists, it sets runningFlag=true and visibleFlag=true according to task.isVisible().

[0140] For components of the target application that are of type Service: the controller can obtain the list of services through ActivityManager.getRunningServices(), match packageName and serviceClass, and if the match is successful, set runningFlag=true and VisibleFlag=true.

[0141] When the target application component's runningFlag is true (i.e., the target application component is a running application component), the controller obtains and saves the component state description data of the target application component. Specifically:

[0142] For a target application component of type Activity: the controller can call ActivityStack.finishActivityLocked(), but set the DONT_FINISH_TASK_ON_EXIT flag to retain the target application component's Task record (i.e., the current task record).

[0143] Save the current UI state (Intent Extras, SavedInstanceState) using ActivityRecord;

[0144] Set the avoidMoveToFront flag to prevent automatic pop-up to the foreground from interfering with the switching process.

[0145] The component type for the target application component is Service.

[0146] For bound services, the server can notify the client to unbind, but does not destroy the service connection (i.e., retain the service connection state).

[0147] For Foreground Services, keep their notification bar state (keep the service in the foreground state) and only pause Surface updates.

[0148] The technical solution of this embodiment obtains a snapshot of the currently running task. If the target application component is determined to be a running application component based on the snapshot of the currently running task, the complete running status record of the target application component is collected at once, including task records, interface status, service connection status, etc. This provides sufficient and accurate data support for the subsequent seamless restoration of the target application component, ensuring that the resolution switching process is imperceptible to the user and optimizing the continuity of resolution mode switching.

[0149] In an exemplary embodiment, the resolution mapping configuration file is in XML format. In the step of parsing the resolution mapping configuration file and constructing a resolution configuration query object, the controller is configured to: in response to the operating system initialization meeting preset conditions, call the XML file parser in the operating system; parse the resolution mapping configuration file through the XML file parser, construct a hash mapping index with the application package name as the key and the component resolution configuration list as the value, and obtain the resolution configuration query object.

[0150] The component resolution configuration list includes at least the target resolution mode, application component type, application component identifier, running status marker, and visibility marker for the application component corresponding to the preset application.

[0151] In the specific implementation, the resolution mapping configuration file is in XML format. During the process of the controller parsing the resolution mapping configuration file and constructing the resolution configuration query object, the controller is configured to: respond to the operating system initialization meeting preset conditions (e.g., reaching the systemReady stage), call the operating system's built-in XML file parser, such as XmlPullParser. This XML file parser then parses the aforementioned resolution mapping configuration file ui_resolution_packages.xml node by node, extracting each... <package>The `item` attribute (package name), `mode` attribute (resolution mode), and internal attributes of the node. <activity>or <service>Attributes of child nodes.

[0152] The parsing logic includes:

[0153] The default is componentType="activity" (for backward compatibility).

[0154] Validate the validity of the class identifier and action identifier for the Service type (to prevent null pointer exceptions).

[0155] After parsing the resolution mapping configuration file, the controller constructs a hash map (PackageName→List) with the application package name as the key and the component resolution configuration list as the value. <uipackageconfig>This hash map is the resolution configuration query object.

[0156] Each UIPackageConfig object in the component resolution configuration list encapsulates at least the following information: application package name (String packageName), target resolution mode (String mode), application component type (String componentType), application component identifier (String processName (Activity-specific), String serviceClass (Service-specific), String serviceAction (Service-specific)), running status flag (boolean isRunning, indicating whether the component is running), and visibility flag (boolean isVisible, indicating whether the component is currently visible to the user).

[0157] The technical solution of this embodiment, in response to the initialization of the operating system meeting preset conditions, calls the XML file parser in the operating system to parse the resolution mapping configuration file, so as to build a hash mapping index with the application package name as the key and the component resolution configuration list as the value. This enables the target application component's resolution configuration to be quickly queried based on the resolution configuration query object as the configuration data carrier when responding to subsequent resolution switching events, effectively improving the decision efficiency of resolution switching and shortening the response delay of the switching command.

[0158] In an exemplary embodiment, the controller is further configured to: query whether the target application is a whitelisted application based on the application package name of the target application; whitelisted applications are applications that the operating system needs to run continuously; if the target application is not a whitelisted application, perform the step of recording the component state description data of the target application component; if the target application is a whitelisted application, update the canvas size of the window corresponding to the target application component through the window manager of the operating system to switch the target application component to the target resolution mode.

[0159] In practice, after the controller determines the target application, it can query a predefined whitelist based on the application package name of the target application. This predefined whitelist records applications that the operating system needs to run continuously and should not be forcibly stopped, i.e., whitelisted applications, such as the live streaming application LiveTV and the system settings application.

[0160] If the target application is a whitelisted application within a predefined whitelist, to avoid interrupting the user experience, the controller will not execute the target application's shutdown process. Instead, it will use the operating system's WindowManager to call methods such as ActivityRecord.setBounds() to update the surface size of the window corresponding to the target application component, adapting its displayed content to the new target resolution mode. This allows the user to continue watching the live stream or performing system settings without any noticeable disruption.

[0161] If the target application is not a whitelisted application in the predefined whitelist, the controller will execute the step of recording the component state description data of the target application components, that is, continue to execute the aforementioned target application stop, state preservation and restart process.

[0162] The technical solution of this embodiment introduces a whitelist protection mechanism. For critical system applications (such as live streaming applications and system settings), the controller only adjusts the canvas size of the target application component through the window manager, without performing a stop-and-restart process on the target application component. This ensures that when users are watching live streams or performing critical operations such as system settings, service interruption or interface flickering will not occur due to application restart.

[0163] In one exemplary embodiment, the controller is further configured to: extract resolution configuration update data from the OTA upgrade package in response to receiving an OTA upgrade package from the operating system; and update the resolution mapping configuration file stored in the target partition of the operating system based on the resolution configuration update data.

[0164] In practice, the display device also supports upgrading the resolution mapping configuration file via OTA (Over-The-Air). The controller can respond to receiving an OTA upgrade package from the operating system and extract the resolution configuration update data (e.g., a new or modified ui_resolution_packages.xml file) from the OTA upgrade package. Then, the controller can update the resolution mapping configuration file stored in the target partition of the operating system based on the resolution configuration update data.

[0165] The technical solution of this embodiment, by responding to the received OTA upgrade package of the operating system, extracting resolution configuration update data from the OTA upgrade package, and updating the resolution mapping configuration file stored in the target partition of the operating system, can realize the dynamic updating of the resolution mapping configuration file through OTA upgrade, and quickly adjust the resolution switching strategy of preset applications without pushing a complete system firmware version.

[0166] In an exemplary embodiment, in the step of switching the display resolution of the target application component on the corresponding layer of the user graphical interface according to the target resolution mode of the target application component, the controller is configured to: traverse all layers of the operating system, match the layer corresponding to the target application component on the user graphical interface, and obtain the target application layer; set the target display resolution of the target application layer according to the target resolution mode of the target application component, and add a resolution conversion flag to the target application layer; the resolution conversion flag is used to instruct the hardware compositor of the operating system to convert the current display resolution of the target application layer; and the hardware compositor switches the current display resolution of the target application layer to the target display resolution.

[0167] In practice, the controller can traverse all layers of the operating system through the operating system's image compositing service (SurfaceFlinger). By matching the layer's owner user ID (ownerUid) or associated application package name, it determines the layer corresponding to the target application component and uses it as the target application layer.

[0168] Next, set the target display resolution for the target application layer and add a resolution conversion flag to the target application layer. This resolution conversion flag is used to instruct the operating system's hardware compositor (HWC) to convert the current display resolution of the target application layer.

[0169] Upon receiving the resolution update command and the resolution conversion flag, the hardware synthesizer (HWC) performs resolution conversion at the hardware level (e.g., the DE module of the TV main control chip). This involves upscaling or downscaling the layer content in the source buffer to the target display resolution. Specifically, it can upscale the layer content from 1080p to 4K, or downscale the layer content from 4K to 1080p.

[0170] The hardware compositor releases the Overlay Plane (a separate hardware display channel) at the original resolution occupied by the current layer and reallocates the video memory (buffer) to match the target resolution (4K).

[0171] When the next vertical sync (VSync) signal arrives, the hardware compositor (HWC) can atomically switch the display output, displaying the scaled layer content on the screen, completing a seamless switch from 1080p to 4K and avoiding screen tearing.

[0172] In this embodiment, the controller sets a resolution conversion marker on the target application layer corresponding to the user's graphical interface by the target application component, and then lets the hardware synthesizer (HWC) directly perform the resolution conversion of the buffer at the hardware level. This avoids complex software scaling by the GPU and effectively reduces the GPU load and system power consumption.

[0173] In another embodiment, such as Figure 5 As shown, an application resolution switching method is provided, which is applied to... Figure 1 Taking a display device as an example, the target partition of the operating system of the display device stores a resolution mapping configuration file. The resolution mapping configuration file is used to record the resolution control strategy configured for the application components of a preset application, including the following steps:

[0174] Step S502: Parse the resolution mapping configuration file and construct a resolution configuration query object; the resolution configuration query object is indexed by the application package name and records the target resolution mode of at least one application component corresponding to each preset application;

[0175] Step S504: In response to the resolution switching event, obtain the application package name of the target application; the target application is one of the preset applications.

[0176] Step S506: Based on the application package name of the target application, determine the target resolution mode of the target application component corresponding to the target application from the resolution configuration query object, and record the component status description data of the target application component; the target application component is a running application component;

[0177] Step S508: According to the target resolution mode of the target application component, switch the display resolution of the corresponding layer of the target application component in the user graphical interface, and restore the component state of the target application component according to the component state description data of the target application component.

[0178] It should be noted that the specific limitations of the above steps can be found in the specific limitations of a display device described above. The above application resolution switching method deploys a resolution mapping configuration file in the target partition of the display device's operating system. This configuration file records the resolution control strategies that match the application components of a preset application. By parsing this configuration file, an indexed resolution configuration query object is constructed. This allows for rapid matching of the target resolution mode of a specific application component of the target application based on the application package name when a resolution switching event occurs. Before the resolution mode switch, the component state description data of the specific application component is recorded. After the resolution mode switch, the working state of the target component is restored based on the component state description data. This enables the display device to achieve fine-grained dynamic resolution switching for a single application or a specific application component within an application without requiring a global interruption or operating system restart. This effectively avoids the interruption of other applications or data loss caused by resolution switching, improves system stability in multi-resolution scenarios, and effectively enhances the control precision of the display device's resolution mode.

[0179] It should be noted that the specific limitations of the above steps can be found in the specific limitations of a display device mentioned above, and will not be repeated here.

[0180] In another embodiment, such as Figure 6 As shown, another method for application resolution switching is provided, which can be applied to... Figure 1 Taking a display device as an example, the target partition of the operating system of the display device stores a resolution mapping configuration file. The resolution mapping configuration file is used to record the resolution control strategy configured for the application components of a preset application, including the following steps:

[0181] Step S602: In response to the operating system initialization meeting the preset conditions, the XML file parser in the operating system is invoked.

[0182] Step S604: Parse the resolution mapping configuration file using an XML file parser, construct a hash mapping index with the application package name as the key and the component resolution configuration list as the value, and obtain the resolution configuration query object.

[0183] Step S606: In response to the resolution switching event, obtain the application package name of the target application; the target application is one of the preset applications.

[0184] Step S608: Based on the application package name of the target application, query whether the target application is a whitelisted application; whitelisted applications are applications that the operating system needs to run continuously.

[0185] Step S610: If the target application is not a whitelisted application, obtain a snapshot of the operating system's currently running tasks.

[0186] Step S612: Obtain component state description data of the target application component based on the snapshot of the currently running task.

[0187] Step S614: According to the target resolution mode of the target application component, switch the display resolution of the corresponding layer of the target application component in the user graphical interface.

[0188] Step S616: Restore the component state of the target application component based on the component state description data of the target application component.

[0189] It should be noted that the specific limitations of the above steps can be found in the specific limitations of a display device mentioned above, and will not be repeated here.

[0190] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0191] Based on the same inventive concept, this application also provides an application resolution mode switching device for implementing the application resolution mode switching method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more application resolution mode switching device embodiments provided below can be found in the limitations of the application resolution mode switching method described above, and will not be repeated here.

[0192] In one exemplary embodiment, such as Figure 7 As shown, an application resolution switching device is provided, applied to a display device. The target partition of the operating system of the display device stores a resolution mapping configuration file. The resolution mapping configuration file is used to record the resolution control strategy configured for application components of a preset application. The device includes:

[0193] The parsing unit 710 is used to parse the resolution mapping configuration file and construct a resolution configuration query object; the resolution configuration query object is indexed by the application package name and records the target resolution mode of at least one application component corresponding to each preset application.

[0194] The response unit 720 is configured to, in response to a resolution switching event, obtain the application package name of the target application; the target application is one of the preset applications.

[0195] The query unit 720 is configured to determine the target resolution mode of the target application component corresponding to the target application from the resolution configuration query object based on the application package name of the target application, and to record the component status description data of the target application component; the target application component is a running application component;

[0196] The switching unit 720 is used to switch the display resolution of the target application component in the corresponding layer of the user graphical interface according to the target resolution mode of the target application component, and restore the component state of the target application component according to the component state description data of the target application component.

[0197] Each module in the aforementioned application resolution switching device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0198] For the convenience of those skilled in the art, Figure 9 An exemplary structural diagram of a resolution mode switching system (UI resolution dynamic configuration system) is provided; wherein, the application resolution mode switching system includes a configuration layer, a listening layer, a decision layer, an execution layer, and a rendering layer.

[0199] The configuration layer is used to define, parse, and update resolution control policies; specifically:

[0200] The configuration layer is used to parse the resolution mapping configuration file (ui_resolution_packages.xml, XML configuration file) into a resolution configuration query object, namely UIPackageConfig (data carrier class). In addition, the configuration layer is also configured with an OTA upgrade interface, which supports extracting incremental resolution configuration data from the system OTA package, silently updating the XML configuration file and rebuilding UIPackageConfig without restarting the operating system.

[0201] The listening layer is used to listen for system events that trigger resolution switching, including: application startup listening (ActivityStarter callback), hardware status listening (HDMI / HDR changes), system load listening (CPU / GPU / temperature), and the listening hub (UIManagerService). The listening hub is used to receive and distribute system events that trigger resolution switching and pass the event information to the decision layer for processing.

[0202] The decision layer determines the resolution mode of the target application component based on configuration and event information. This includes a package name matching detection function (HashMap index lookup), which retrieves the corresponding resolution configuration list from the hash map index of UIPackageConfig based on the target application's package name; and a component type identification (Activity / Service) function, which identifies the component type of the target application component, distinguishing between front-end UI components (Activity) and back-end service components (Service), and matching the corresponding resolution switching strategy.

[0203] The execution layer is used to perform resolution switching operations. It can obtain Task stack snapshots and determine the state description data of the target application component (including task records, UI state, service state, etc.) based on these snapshots. The execution layer also includes a whitelist filtering function. After identifying the target application, the controller can query a predefined whitelist based on the target application's package name. If the target application is a whitelisted application, the controller will not execute the target application's shutdown process. Instead, it will update the canvas size of the window corresponding to the target application component through the operating system's window manager, preventing application interruption and ensuring a better user experience.

[0204] If the target application is not a whitelisted application in the predefined whitelist, the controller can save the target application component's interface state, Intent attached data, running state and other information for restoration after resolution switching. It can also inject a system flag through the targeted restart function, and use the flag to target restart the target application component of the target application and apply the new resolution mode.

[0205] The rendering layer is used to switch resolutions and output image signals through system services and hardware capabilities. Specifically, the rendering layer includes the SurfaceFlinger image compositing service (Layer parameter configuration), the HWC hardware compositor, and VSync synchronization functionality. The controller can use the SurfaceFlinger image compositing service to traverse all layers of the operating system. By matching the layer's owner user ID (ownerUid) or associated application package name, the layer corresponding to the target application component is determined as the target application layer. Then, the target display resolution of the target application layer is set, and a resolution conversion flag is added to the target application layer. This resolution conversion flag instructs the operating system's hardware compositor (HWC) to convert the current display resolution of the target application layer.

[0206] Upon receiving the resolution update command and the resolution conversion flag, the Hardware Composer (HWC) performs resolution conversion at the hardware level (e.g., the DE module of the TV's main control chip). This involves upscaling or downscaling the layer content in the source buffer to the target display resolution. The hardware composer then releases the overlay plane occupied by the current layer at the original resolution and reallocates video memory (buffer) that matches the target resolution (4K).

[0207] When the next vertical sync (VSync) signal arrives, the hardware compositor (HWC) can atomically switch the display output, displaying the scaled layer content on the screen, completing a seamless switch from 1080p to 4K and avoiding screen tearing.

[0208] For the convenience of those skilled in the art, Figure 9 A resolution switching timing flowchart is provided, such as Figure 9 As shown, the application resolution mode switching system can listen for resolution switching events (such as application startup or application switching) to determine if they are triggered. When a resolution switching event is triggered, the controller determines the application that triggered the event based on the event information. The controller then determines whether the application that triggered the event is a preset application configured in the resolution mapping configuration file. Specifically, it can obtain the application package name of the application that triggered the event and check whether the application package name is in the application list configured in the resolution mapping configuration file. If the application package name of the application that triggered the event is not in the application list configured in the resolution mapping configuration file, it is determined that the application that triggered the event is not configured. The application that triggered the event is then started normally without performing resolution switching, maintaining the native experience of the unconfigured application.

[0209] If the application package name of the event-triggered application is in the application list configured in the resolution mapping configuration file, the event-triggered application is determined to be a configured application (i.e., the target application), and the controller enters the following resolution switching process;

[0210] Get a snapshot of the Task stack. Obtain a snapshot of the currently running task stack through the system's RootWindowContainer.getTasks() interface to extract the running status information of the target application component.

[0211] Whitelist application determination: Determine whether the target application is a whitelist application (an application that the operating system needs to run continuously and cannot be interrupted).

[0212] If the target application is a whitelisted application, the controller updates the canvas size of the window corresponding to the target application component through the operating system's window manager to prevent the target application from being interrupted and affecting the user experience.

[0213] If the target application is not a whitelisted application, the controller can associate the application package name of the target application with the currently running Task stack, and set the runningFlag (running status flag) and visibleFlag (visibility flag) to provide a basis for subsequent component processing.

[0214] In addition, the controller executes differentiated state preservation strategies based on the component type of the target application component, specifically:

[0215] For a target application component of type Activity, the controller calls the system's finishActivityLocked() interface to safely terminate the current Activity instance.

[0216] If the component type of the target application component is Service, the controller will unbind or suspend the Surface corresponding to the Service to avoid service interruption.

[0217] Additionally, the controller can cache the UI state, Intent appended data, runtime parameters, and other component state description data of the target application components through SavedInstanceState, in order to control the target application components to restore to the state before the resolution switch.

[0218] Then, the controller performs the resolution switching, which is accomplished in collaboration with the system surface compositing service (SurfaceFlinger) and the hardware compositing module (HWC). See above for details.

[0219] After completing the resolution switch, the targeted restart component of the application resolution mode switching system restarts the target application component by injecting a system flag, applies the new resolution mode, and restores the component state of the target application component using the previously saved component state description data.

[0220] In one exemplary embodiment, a computer device is provided, which may be a smart TV, and its internal structure diagram may be as follows: Figure 10 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements an application resolution mode switching method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0221] Those skilled in the art will understand that Figure 10 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0222] In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of the application resolution mode switching method described above. The steps of the application resolution mode switching method described here may be steps from one of the application resolution mode switching methods in the various embodiments described above.

[0223] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, causes the processor to perform the steps of the application resolution mode switching method described above. The steps of the application resolution mode switching method described here may be steps from one of the application resolution mode switching methods in the various embodiments described above.

[0224] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, causes the processor to perform the steps of the application resolution mode switching method described above. The steps of the application resolution mode switching method described here may be steps from one of the application resolution mode switching methods in the various embodiments described above.

[0225] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0226] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0227] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0228] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.< / uipackageconfig> < / service> < / activity> < / package> < / package>

Claims

1. A display device, characterized in that, The display device includes: The monitor is configured to display a user graphical interface; The memory is configured to store an operating system, the target partition of which stores a resolution mapping configuration file; the resolution mapping configuration file is used to record the resolution control policies configured for application components of a preset application; the resolution mapping configuration file uses multi-level application identifiers to represent the application components; The controller, connected to the display and the memory, is configured to: The resolution mapping configuration file is parsed to construct a resolution configuration query object; the resolution configuration query object is indexed by the application package name and records the target resolution mode of at least one application component corresponding to each preset application. In response to a resolution switching event, the application package name of the target application is obtained; the target application is one of the preset applications. Based on the application package name of the target application, determine the target resolution mode of the target application component corresponding to the target application from the resolution configuration query object, and record the component status description data of the target application component; the target application component is a running application component; According to the target resolution mode of the target application component, switch the display resolution of the corresponding layer of the target application component in the user graphical interface, and restore the component state of the target application component according to the component state description data of the target application component.

2. The display device according to claim 1, characterized in that, In the step of recording the component state description data of the target application component, the controller is configured to: Obtain a snapshot of the currently running tasks of the operating system; If the target application component is determined to be a running application component based on the current running task snapshot, the component status description data of the target application component is obtained; The component status description data includes at least one of the following: current task record, current interface status, service connection status, and service frontend status.

3. The display device according to claim 1, characterized in that, The multi-level application identifier includes at least two of the following: application package name, component type, and process name; the application component includes at least one of the following: front-end interface component or back-end service component.

4. The display device according to claim 1, characterized in that, The resolution mapping configuration file is in XML format. In the step of parsing the resolution mapping configuration file and constructing the resolution configuration query object, the controller is configured as follows: In response to the operating system initialization meeting preset conditions, the XML file parser in the operating system is invoked; The resolution mapping configuration file is parsed by the XML file parser, and a hash mapping index is constructed with the application package name as the key and the component resolution configuration list as the value to obtain the resolution configuration query object. The component resolution configuration list includes at least the target resolution mode, application component type, application component identifier, running status marker, and visibility marker of the application component corresponding to the preset application.

5. The display device according to claim 1, characterized in that, The controller is also configured to: Based on the application package name of the target application, query whether the target application is a whitelisted application; the whitelisted application is an application that the operating system needs to run continuously. If the target application is not a whitelisted application, the step of recording the component state description data of the target application components is executed; If the target application is a whitelisted application, the canvas size of the window corresponding to the target application component is updated through the window manager of the operating system to switch the target application component to the target resolution mode.

6. The display device according to any one of claims 1 to 5, characterized in that, The controller is also configured to: In response to receiving an OTA upgrade package for the operating system, resolution configuration update data is extracted from the OTA upgrade package; Update the resolution mapping configuration file stored in the target partition of the operating system according to the resolution configuration update data.

7. The display device according to any one of claims 1 to 5, characterized in that, In the step of switching the display resolution of the target application component on the corresponding layer of the user graphical interface according to the target resolution mode of the target application component, the controller is configured to: Traverse all layers of the operating system and match the layer corresponding to the target application component in the user graphical interface to obtain the target application layer; According to the target resolution mode of the target application component, set the target display resolution of the target application layer, and add a resolution conversion mark to the target application layer; The resolution conversion flag is used to instruct the hardware synthesizer of the operating system to convert the current display resolution of the target application layer; The hardware synthesizer switches the current display resolution of the target application layer to the target display resolution.

8. A method for switching application resolution modes, characterized in that, Applied to a display device, the target partition of the operating system of the display device stores a resolution mapping configuration file, which is used to record the resolution control strategy configured for the application components of a preset application; The resolution mapping configuration file uses multi-level application identifiers to represent the application components, and the method includes: The resolution mapping configuration file is parsed to construct a resolution configuration query object; the resolution configuration query object is indexed by the application package name and records the target resolution mode of at least one application component corresponding to each preset application. In response to a resolution switching event, the application package name of the target application is obtained; the target application is one of the preset applications. Based on the application package name of the target application, determine the target resolution mode of the target application component corresponding to the target application from the resolution configuration query object, and record the component status description data of the target application component; the target application component is a running application component; According to the target resolution mode of the target application component, switch the display resolution of the corresponding layer of the target application component in the user graphical interface, and restore the component state of the target application component according to the component state description data of the target application component.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the method of claim 8.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the method of claim 8.