WO2022183856A1 - Procédé et dispositif d'identification d'un fil de dessin de système android, et terminal mobile et support d'enregistrement - Google Patents

Procédé et dispositif d'identification d'un fil de dessin de système android, et terminal mobile et support d'enregistrement Download PDF

Info

Publication number
WO2022183856A1
WO2022183856A1 PCT/CN2022/072611 CN2022072611W WO2022183856A1 WO 2022183856 A1 WO2022183856 A1 WO 2022183856A1 CN 2022072611 W CN2022072611 W CN 2022072611W WO 2022183856 A1 WO2022183856 A1 WO 2022183856A1
Authority
WO
WIPO (PCT)
Prior art keywords
thread
state
threads
current running
android system
Prior art date
Application number
PCT/CN2022/072611
Other languages
English (en)
Chinese (zh)
Inventor
丁唐
王斌宏
Original Assignee
惠州Tcl移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 惠州Tcl移动通信有限公司 filed Critical 惠州Tcl移动通信有限公司
Priority to US18/548,904 priority Critical patent/US20240143395A1/en
Priority to EP22762325.3A priority patent/EP4303725A1/fr
Publication of WO2022183856A1 publication Critical patent/WO2022183856A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
    • G06F9/526—Mutual exclusion algorithms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/544—Buffers; Shared memory; Pipes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/545—Gui
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/548—Queue
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • the present application relates to the technical field of Android operating system terminals, in particular to a method, device, mobile terminal and storage medium for identifying Android system drawing threads.
  • Thread is the smallest unit of program execution flow, an entity in the process, and the basic unit independently scheduled and dispatched by the system. Threads include three basic states: ready, stuck (blocked), and running.
  • the ready state means that the thread has all the conditions for running, it can run logically, and is waiting for the processor;
  • the running state means that the thread occupies the processor and is running;
  • the stuck state means that the thread is waiting for an event (such as a semaphore), Logically not executable.
  • a thread in a stuck state will directly affect the running effect of the entire program. Therefore, how to identify the drawing-related threads on the mobile terminal and maximize resource utilization has become a technical problem that needs to be solved.
  • the present application provides a method, device, mobile terminal and storage medium for identifying Android system drawing threads, and aims to solve the technical problem that: when software runs on the mobile terminal, there may be a number of auxiliary software remaining on the mobile terminal. Processes, processes used to collect data to formulate user policies, processes used to pop up pop-up windows, etc. Residual processes occupy the resources of the mobile terminal, causing the mobile terminal to freeze or run slowly, and the thread is stuck. The state will directly affect the running effect of the whole program.
  • the present application provides a method for identifying Android system drawing threads, the method applies to a client based on the Android operating system, and the method includes:
  • the threads include one or more threads among the main thread of the application process, the hardware rendering thread of the Android system and the custom thread;
  • Identify the thread task according to the state when the process state is switched identify the current running thread, mark the current task_struct of the thread as ui_thread, and obtain the drawing thread state;
  • the step of identifying the thread task according to the state of the process state switching includes:
  • the drawing thread state is set according to whether it is the foreground state. If it is the foreground state, it is marked as the drawing thread and enters the drawing process; otherwise, the drawing thread state is reset or the default priority is used to enter the process;
  • the drawing state is set for the drawing thread during initialization, and is set to the thread table maintained by the kernel.
  • the drawing process is entered, otherwise the default priority is used to enter the process;
  • the current running thread is a custom thread
  • identify and set the state of the drawing thread in the drawing interface queueBuffer When a client fills the graphics buffer through this interface, the calling end is marked as the drawing thread, and when it is identified as setting the drawing flag Then enter the drawing process, otherwise the default priority is used to enter the process.
  • the step of identifying the thread task according to the state when the process state is switched includes: when the current running thread is the main thread, the identification of the main thread is performed by updating the process state, and then judging whether it is the foreground state. Settings for drawing thread state.
  • the graphics buffer is GraphicBuffer.
  • the steps of the method for identifying the Android system drawing thread further include: the current running thread sends a drawing request, and calls an interface control ioctl function, and the ioctl function parses the service request.
  • the steps of the method for identifying the Android system drawing thread further include: the current process calls the server and draws the application, and in the drawing application, the SurfaceFlinger is used to control the composition of the windows and perform the drawing.
  • the SurfaceFlinger in the step of controlling window composition and drawing through SurfaceFlinger, is connected to the HWComposer, and the synthesized frame buffer is sent to the HWComposer to be used as the target buffer.
  • the present application also provides a device for identifying Android system drawing threads, including:
  • a thread creation module is used to create multiple threads, and the threads include one or more threads in the main thread of the application process, the hardware rendering thread of the Android system and the custom thread;
  • the cache acquisition module is used to communicate across processes through threads and apply for a graphics buffer area, and call the QueueBuffer function of BufferQueue to submit the graphics content drawn by the client to the system graphics buffer;
  • the thread drawing module is used to identify the thread task according to the state when the process state is switched, identify the current running thread, mark the current task_struct of the thread as ui_thread, and obtain the drawing thread state;
  • the thread drawing control module is used to identify the thread task according to the state when the process state is switched, and if it is not the current running thread, reset the state of the drawing thread.
  • the present application provides a mobile terminal, which includes a memory, a processor, and a program for identifying Android system drawing threads that is stored on the memory and can run on the processor, and the processor executes the identification When the Android system draws the thread program, the processor is configured to execute the above method.
  • the present application provides a storage medium storing a computer program for electronic data exchange, wherein the computer program causes a computer to execute the method as described above.
  • the method for identifying Android system drawing threads identifies thread tasks and current running threads according to the state of the process state switching, especially the main thread, hardware rendering thread and custom thread are marked in different ways. Whether the main thread is in the foreground state and then decide whether to enter the drawing process, identify whether the hardware rendering state is set to the drawing state during initialization and then decide whether to enter the drawing process, and identify whether the custom thread sets the drawing state in the drawing interface queueBuffer. Then decide whether to enter the drawing process.
  • This method helps to identify the status of each thread and identify the status of each task, so that no matter which thread applies for GraphicBuffer for cross-process communication, it can identify the status of each task identified by the identification. , so that the identified tasks can be given more resource avoidance in subsequent processing; furthermore, the drawing-related processes on the mobile terminal can be identified and the maximum resource utilization can be given, which can improve the utilization rate of the mobile system.
  • Fig. 1 is the step flow chart of the method for identifying Android system drawing thread provided by the application
  • Fig. 2 is the frame diagram of drawing thread data flow provided by the application
  • Fig. 3 is the concrete flow chart of drawing thread identification provided by the application.
  • FIG. 4 is a schematic block diagram of an apparatus for identifying a drawing thread of an Android system provided by the present application.
  • Fig. 1 is a flow chart of steps of a method for identifying Android system drawing threads provided by the application
  • Fig. 2 is a frame diagram of a drawing thread data flow provided by the application
  • Fig. 3 is the application Provides a specific flowchart for drawing thread identification.
  • the present application provides a method for identifying Android system drawing threads for a client based on Android operating system, which includes the following steps:
  • the threads include one or more threads in the main thread of the application process, the hardware rendering thread of the Android system and the self-defined thread;
  • S02 perform cross-process communication through threads and apply for a graphics buffer area, and call the QueueBuffer function of BufferQueue to submit the graphics content drawn by the client to the system graphics buffer;
  • the current running process calls the server and draws the application, and in the drawing application, the SurfaceFlinger is used to control the composition of the window and draw it.
  • the present application provides an embodiment to describe the above steps in detail.
  • the Android system provides a graphics drawing system.
  • An application program can be invoked through a certain interface, and transmit its own drawing instructions to SurfaceFlinger through a given interface for drawing and display.
  • the specific steps of the method for identifying Android system drawing threads provided by the present application And the principle is as follows:
  • Thread is the smallest unit of program execution flow, an entity in the process, and the basic unit independently scheduled and dispatched by the system.
  • An Android program has only one process (Process) by default, and multiple threads (Thread) can be set under one Process.
  • a thread is an execution scenario in a process, and a process can start multiple threads. Threads include three basic states: ready, stuck (blocked), and running.
  • the ready state means that the thread has all the conditions for running, it can run logically, and is waiting for the processor;
  • the running state means that the thread occupies the processor and is running;
  • the stuck state means that the thread is waiting for an event (such as a semaphore), Logically not executable.
  • the method provided by this application is to identify the running state of the thread.
  • Threads in Android are mainly divided into two categories: UIThread, that is, the main thread, also known as UI thread; the other is WorkerThread, that is, custom thread, or worker thread.
  • UIThread is the main thread of application execution and is where most of the application code runs. All application components, including Activities, Services, Content Providers, BroadCastReceivers, etc., are created in this thread, and any system calls to the application components are executed in this thread.
  • the jvm Java Virtual Machine
  • Accessing the network generally takes a long time, and accessing the network in the main thread will cause the program to freeze or even freeze.
  • UIThread threads and one or more WorkerThreads can exist in the program at the same time.
  • HardwareRenderer is the entry point of the entire hardware accelerated rendering.
  • the implementation is a ThreadedRenderer object. ThreadedRenderer should be closely related to a Render thread, and ThreadedRenderer is created in the UI thread. The role is to be responsible for communicating with the rendering thread.
  • S02 perform cross-process communication through the drawing thread and apply for a graphics buffer area, and call the dequeueBuffer function of the BufferQueue to submit the graphics content drawn by the client to the system graphics buffer.
  • the graphics buffer area is GraphicBuffer.
  • the graphics buffer area is GraphicBuffer.
  • the drawing principle of the Android system graphics system whether it is a built-in application of the system or a third-party application, it is necessary to apply for a graphics buffer from the BufferQueue to prepare the content of the drawing application. Apply for the corresponding GraphicBuffer to the SurfaceFlinger in the display system of the local operating system based on the image data applied for display by the current application thread; then, draw the image data applied for and display by the current application process to the GraphicBuffer; draw the SurfaceFlinger through the SurfaceFlinger The GraphicBuffer after the image data synthesizes the final image content as the current screen information for display.
  • thread A When the current running thread is thread A (main thread), thread A first updates the process state (updateProcessState), and then sets the drawing thread state according to whether it is the foreground state. If it is judged that thread A is in the foreground state, mark the current task_struct of thread A as ui_thread, obtain the drawing thread state, and call the IOCTL function through the system.
  • IOCTL is a function in the device driver to manage the I/O channel of the device. The so-called management of the I/O channel is to control some characteristics of the device, such as the transmission baud rate of the serial port, the speed of the motor, and so on. In this embodiment, the drawing request sent by the current running thread is parsed.
  • the drawing state is set for thread B during initialization, and is set to the thread table maintained by the kernel.
  • the current task_struct of the thread is marked as ui_thread, the drawing thread state is obtained, and the IOCTL function is called through the system.
  • the current running thread is thread N (unknown custom thread)
  • identify and set the state of the drawing thread in the drawing interface QueueBuffer When a client fills the graphics buffer through the drawing interface QueueBuffer, mark the current thread of the calling end.
  • the task_struct is ui_thread, which gets the drawing thread state.
  • the drawing process is entered, and the IOCTL function is called through the system.
  • thread A When the current running thread is thread A (main thread), thread A first updates the process state (updateProcessState), and then sets the drawing thread state according to whether it is the foreground state. If it is judged that thread A is not in the foreground state, reset the drawing thread state and call the IOCTL function through the system.
  • process state updateProcessState
  • the drawing state is set for thread B during initialization, and is set to the thread table maintained by the kernel.
  • the default priority is used to enter the process.
  • the current running thread is thread N (unknown custom thread) (unknown custom thread)
  • thread N unknown custom thread
  • the drawing thread state is set.
  • the default priority is used to enter the process. .
  • the current running process calls the server and draws the application, and in the drawing application, the SurfaceFlinger is used to control the composition of the window and draw it.
  • the SurfaceFlinger is connected to the HWComposer, and the synthesized frame buffer is sent to the HWComposer to be used as the target buffer.
  • Each application App includes multiple threads (Thread), and the application App can create multiple sub-threads Thread, and it is not certain which thread executes the drawing task.
  • Thread multiple threads
  • the child thread needs to perform the drawing task, it will apply for a graphics buffer from the BufferQueue to prepare the content of the drawing application, and finally pass it to the BufferQueue through the queueBuffer, and hand it over to SurfaceFlinger for drawing.
  • a window is described by a Surface. If multiple windows need to be displayed at the same time, multiple windows need to be merged. This requires the service Surfaceflinger in the display system to control the composition of windows, combine multiple windows into one, and then send it to the LCD. Among them, Surfaceflinger adopts the concept of layers, namely Layer. SurfaceFlinger synthesis is based on Display The implementation of HAL combines multiple layers. SurfaceFlinger is to synthesize the content of multiple Surfaces, and finally submit it to the back buffer area of the screen, wait for the next vertical synchronization signal of the screen to arrive, and then display it on the screen.
  • the Surface is a further encapsulation of the Buffer, which means that the Surface has multiple Buffers for the upper layer to use.
  • the graphics buffer allocated in the system frame buffer is used in the SurfaceFlinger service, and the graphics buffer allocated in memory can be used in the SurfaceFlinger service or in other applications.
  • the graphics buffer allocated in memory can be used in the SurfaceFlinger service or in other applications.
  • other applications need to use the graphics buffer, they will request the SurfaceFlinger service to allocate them. Therefore, for other applications, they only need to map the graphics buffer returned by the SurfaceFlinger service to their own process. address space to use it.
  • SurfaceFlinger is the management core of the entire Android display system, controlling the overlay of each window, and calling the GPU or 2D accelerator for synthesis.
  • the interface first call the dequeueBuffer function of BufferQueue to obtain a frame buffer, then start the GPU to synthesize the contents of each window into this frame buffer, and then call the queueBuffer function of BufferQueue.
  • BufferQueue will call the fbPost function of HWComposer, and hand over the synthesized frame buffer to HWComposer as the target buffer of the 2D accelerator.
  • HWComposer will call the interface fb_post of framebuffer_device_t, and hand over the target buffer area to framebuffer_device_t and send it to the screen for display.
  • Thread A represents the main program of the application, and each application will create a main thread by default when it is created for life cycle management. Thread A first updates the process state (updateProcessState), and then sets the drawing thread state according to whether it is the foreground state. If it is judged that thread A is in the foreground state, mark the current task_struct of the thread as ui_thread, get the drawing thread state, and call the IOCTL function through the system; if it is judged that thread A is not in the foreground state, reset the drawing thread state, and call the IOCTL function through the system .
  • process state updateProcessState
  • Thread B is a hardware rendering thread HardwareRenderer that exists by default in the Android system.
  • the drawing state is set during initialization and is set to the thread table maintained by the kernel.
  • the current task_struct of the thread is marked as ui_thread
  • the drawing thread state is obtained, and the IOCTL function is called through the system.
  • the process is entered with a default priority.
  • Thread N is an undefined thread, and it has no specific flag bit to identify it. Therefore, in this application, it is identified through the QueueBuffer formed by multiple buffer areas inside the Surface. Specifically, when a client fills the graphics buffer through the drawing interface QueueBuffer, the current task_struct of the calling thread is marked as ui_thread, and the drawing thread state is obtained. The subsequent identification steps are consistent with thread B. When it is identified that the thread N is in the setting drawing state, the current task_struct of the thread is marked as ui_thread, the drawing thread state is obtained, and the IOCTL function is called through the system. When it is recognized that the thread N is in the unset drawing state, the process B is entered with the default priority.
  • a mobile terminal comprising a processor and a memory, the memory stores a program, and the processor is configured to perform the following operations:
  • the threads include one or more threads among the main thread of the application process, the hardware rendering thread of the Android system and the custom thread;
  • Identify the thread task according to the state when the process state is switched identify the current running thread, mark the current task_struct of the thread as ui_thread, and obtain the drawing thread state;
  • the current running process calls the server and draws the application.
  • SurfaceFlinger controls the composition of the window and draws it.
  • the processor of the mobile terminal is used to provide computing and control capabilities.
  • the memory of the mobile terminal includes a non-volatile storage medium and an internal memory.
  • the nonvolatile storage medium stores an operating system and a computer program.
  • the internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium.
  • the network interface of the mobile terminal is used for communicating with external terminals through a network connection.
  • the computer program is executed by a processor to implement a method for identifying a drawing thread of an Android system.
  • an embodiment of the present application further provides a device for identifying Android system drawing threads, which is used for a client based on the Android operating system, and the device includes:
  • the thread creation module 10 is used to create a plurality of threads, and the threads include one or more threads among the main thread of the application process, the hardware rendering thread of the Android system and the custom thread;
  • the cache acquisition module 20 is used to perform cross-process communication through threads and apply for a graphics buffer area, and call the QueueBuffer function of BufferQueue to submit the graphics content drawn by the client to the system graphics buffer;
  • the thread drawing module 30 is used to identify the thread task according to the state when the process state is switched, identify the current running thread, mark the current task_struct of the thread as ui_thread, and obtain the drawing thread state;
  • the thread drawing control module 40 is configured to identify the thread task according to the state when the process state is switched, and reset the drawing thread state if it is not the current running thread.
  • the present application provides a storage medium storing a computer program for electronic data exchange, wherein the computer program causes a computer to perform the method as described above.
  • Nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory may include random access memory (RAM) or external cache memory.
  • RAM is available in various forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Road (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM) and so on.
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDRSDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchronous chain Road (Synchlink) DRAM
  • SLDRAM synchronous chain Road (Synchlink) DRAM
  • Rambus direct RAM
  • DRAM direct memory bus dynamic RAM
  • RDRAM memory bus dynamic RAM
  • the method for identifying Android system drawing threads identifies thread tasks and current running threads by identifying thread tasks according to the state of process state switching, especially for main threads, hardware rendering threads and custom threads to be marked in different ways. , specifically identify whether the main thread is in the foreground state and then decide whether to enter the drawing process, identify whether the hardware rendering state sets the drawing state during initialization to determine whether to enter the drawing process, and identify whether the custom thread is in the drawing interface.
  • the drawing state is set in the queueBuffer to determine whether to enter the drawing process.
  • This method helps to identify the state of each thread and identify the state of each task, so that no matter which thread applies for GraphicBuffer for cross-process communication, it can pass the identification mark.
  • the status of each task enables the identified tasks to be given more resource avoidance in subsequent processing; furthermore, it can identify the process related to drawing on the mobile terminal and give maximum resource utilization, which can improve the utilization rate of the mobile system.
  • a part of the present application can be applied as a computer program product, such as computer program instructions, which when executed by a computer, through the operation of the computer, can invoke or provide methods and/or technical solutions according to the present application.
  • the program instructions for invoking the methods of the present application may be stored in fixed or removable recording media, and/or transmitted via data streams in broadcast or other signal-bearing media, and/or stored in accordance with the in the working memory of the computer device on which the program instructions are executed.
  • an embodiment according to the present application includes an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein, when the computer program instructions are executed by the processor, a trigger is
  • the apparatus operates based on the aforementioned methods and/or technical solutions according to various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Image Generation (AREA)

Abstract

La présente demande divulgue un procédé et un dispositif d'identification d'un fil de dessin de système Android, et un terminal mobile et un support d'enregistrement. Le procédé comprend : la création d'une pluralité de fils, les fils comprenant un ou plusieurs parmi un fil principal d'un processus d'application, un fil de rendu matériel d'un système Android, et un fil personnalisé ; la réalisation d'une communication inter-processus au moyen d'un fil, l'application d'une région de mémoire cache graphique, et l'appel d'une fonction de mise du tampon en file d'attente de la file d'attente de tampon pour soumettre un contenu graphique dessiné par un client à une région de mémoire cache graphique système ; l'identification d'un fil d'exécution actuel selon une tâche de fil d'identification d'état pendant la commutation d'état de processus, et le marquage de la structure de tâche actuelle du fil comme fil d'interface utilisateur pour obtenir un état de fil de dessin ; l'identification de la tâche de fil selon l'état pendant la commutation d'état de processus, et la réinitialisation de l'état de fil de dessin si le fil n'est pas le fil d'exécution actuel. Selon la présente demande, un fil lié à un dessin sur le terminal mobile peut être identifié, l'utilisation maximale des ressources est fournie, et le taux d'utilisation d'un système mobile peut être amélioré.
PCT/CN2022/072611 2021-03-03 2022-01-18 Procédé et dispositif d'identification d'un fil de dessin de système android, et terminal mobile et support d'enregistrement WO2022183856A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US18/548,904 US20240143395A1 (en) 2021-03-03 2022-01-18 Method and device for identifying android system drawing thread, and mobile terminal and storage medium
EP22762325.3A EP4303725A1 (fr) 2021-03-03 2022-01-18 Procédé et dispositif d'identification d'un fil de dessin de système android, et terminal mobile et support d'enregistrement

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110239090.XA CN113051047B (zh) 2021-03-03 2021-03-03 识别安卓系统绘制线程的方法、装置、移动终端及存储介质
CN202110239090.X 2021-03-03

Publications (1)

Publication Number Publication Date
WO2022183856A1 true WO2022183856A1 (fr) 2022-09-09

Family

ID=76510086

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/072611 WO2022183856A1 (fr) 2021-03-03 2022-01-18 Procédé et dispositif d'identification d'un fil de dessin de système android, et terminal mobile et support d'enregistrement

Country Status (4)

Country Link
US (1) US20240143395A1 (fr)
EP (1) EP4303725A1 (fr)
CN (1) CN113051047B (fr)
WO (1) WO2022183856A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113051047B (zh) * 2021-03-03 2023-06-27 驭新智行科技(宁波)有限公司 识别安卓系统绘制线程的方法、装置、移动终端及存储介质
CN113918249B (zh) * 2021-09-14 2023-11-21 北京房江湖科技有限公司 一种背景模糊控件的实现方法及装置
CN117687771A (zh) * 2023-07-24 2024-03-12 荣耀终端有限公司 一种缓冲区分配方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110050712A1 (en) * 2009-08-26 2011-03-03 Red Hat, Inc. Extension To A Hypervisor That Utilizes Graphics Hardware On A Host
CN111367741A (zh) * 2020-02-28 2020-07-03 Oppo广东移动通信有限公司 用户界面卡顿检测方法与装置、电子设备
CN111831462A (zh) * 2020-07-01 2020-10-27 Oppo广东移动通信有限公司 Io请求的处理方法、装置、存储介质及电子设备
CN113051047A (zh) * 2021-03-03 2021-06-29 惠州Tcl移动通信有限公司 识别安卓系统绘制线程的方法、装置、移动终端及存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108509260B (zh) * 2018-01-31 2021-08-13 深圳市万普拉斯科技有限公司 线程识别处理方法、装置、计算机设备和存储介质
CN110109528B (zh) * 2019-03-29 2021-10-22 努比亚技术有限公司 应用程序的管控方法、移动终端及计算机可读存储介质
CN110489228B (zh) * 2019-07-16 2022-05-17 华为技术有限公司 一种资源调度的方法和电子设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110050712A1 (en) * 2009-08-26 2011-03-03 Red Hat, Inc. Extension To A Hypervisor That Utilizes Graphics Hardware On A Host
CN111367741A (zh) * 2020-02-28 2020-07-03 Oppo广东移动通信有限公司 用户界面卡顿检测方法与装置、电子设备
CN111831462A (zh) * 2020-07-01 2020-10-27 Oppo广东移动通信有限公司 Io请求的处理方法、装置、存储介质及电子设备
CN113051047A (zh) * 2021-03-03 2021-06-29 惠州Tcl移动通信有限公司 识别安卓系统绘制线程的方法、装置、移动终端及存储介质

Also Published As

Publication number Publication date
CN113051047B (zh) 2023-06-27
US20240143395A1 (en) 2024-05-02
EP4303725A1 (fr) 2024-01-10
CN113051047A (zh) 2021-06-29

Similar Documents

Publication Publication Date Title
WO2022183856A1 (fr) Procédé et dispositif d'identification d'un fil de dessin de système android, et terminal mobile et support d'enregistrement
US10127628B2 (en) Method and system to virtualize graphic processing services
US9049213B2 (en) Cross-environment user interface mirroring using remote rendering
EP2479666B1 (fr) Procédés et systèmes pour afficher les graphiques de plateforme au cours de l'initialisation du système d'exploitation
WO2018161813A1 (fr) Procédé et dispositif de chargement de ressources
US20100115510A1 (en) Virtual graphics device and methods thereof
WO2018223075A1 (fr) Procédé et appareil d'implémentation de processeur graphique virtuel et système
CN109324903B (zh) 用于嵌入式系统的显示资源调度方法及装置
CN111597042A (zh) 业务线程运行方法、装置、存储介质及电子设备
WO2021013019A1 (fr) Procédé et appareil de traitement d'image
JP2000330806A (ja) 計算機システム
JP7100154B6 (ja) プロセッサコアのスケジューリング方法、装置、端末及び記憶媒体
US20190080017A1 (en) Method, system, and device that invokes a web engine
US20110066836A1 (en) Operating system booting method, computer, and computer program product
CN113419845A (zh) 计算加速方法和装置、计算系统、电子设备及计算机可读存储介质
US20130067502A1 (en) Atlasing and Virtual Surfaces
WO2023138020A1 (fr) Procédé et appareil de génération d'image, dispositif électronique et support de stockage
WO2015154226A1 (fr) Procédé, dispositif et processeur de communication de données dans un environnement virtualisé
WO2023044877A1 (fr) Procédé et appareil de traitement de passage de rendu, dispositif électronique, et support d'enregistrement
CN114924837A (zh) 数据处理方法、电子设备和可读存储介质
CN114116227A (zh) 一种无GPU支持的基于Wayland协议的显示方法、装置及设备
WO2023173896A1 (fr) Procédé de communication, dispositif électronique et support d'enregistrement lisible
WO2019079940A1 (fr) Procédé de traitement graphique et appareil et dispositif associés
EP4345622A1 (fr) Procédé d'appel de processus de service et dispositif associé
WO2023061014A1 (fr) Procédé et appareil de gestion de tâche

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22762325

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18548904

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2022762325

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022762325

Country of ref document: EP

Effective date: 20231004