CN108845840A - Management method, device, storage medium and the intelligent terminal of application program sound - Google Patents

Management method, device, storage medium and the intelligent terminal of application program sound Download PDF

Info

Publication number
CN108845840A
CN108845840A CN201810578119.5A CN201810578119A CN108845840A CN 108845840 A CN108845840 A CN 108845840A CN 201810578119 A CN201810578119 A CN 201810578119A CN 108845840 A CN108845840 A CN 108845840A
Authority
CN
China
Prior art keywords
audio
application program
sound
application
preloaded
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201810578119.5A
Other languages
Chinese (zh)
Inventor
韩世广
陈岩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to CN201810578119.5A priority Critical patent/CN108845840A/en
Publication of CN108845840A publication Critical patent/CN108845840A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44521Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/16Sound input; Sound output

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Computer Interaction (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the present application discloses management method, device, storage medium and the intelligent terminal of a kind of application program sound.This method includes the audio broadcast event for detecting application program, obtains the corresponding audio file of the audio broadcast event;Obtain the preset audio attribute of the application program;Whether allow to play the sound of the audio file based on the audio broadcast message class being pre-created according to the preset audio determined property.By using above-mentioned technical proposal, in the audio broadcast event for detecting application program, the audio broadcast message class being pre-created wouldn't be written in decoded audio file;When the preset audio attribute of the application program, which is, to be allowed to be written, audio file is just written to the audio broadcast message class being pre-created, effectively sound play operation can be managed, backstage preloaded applications program is avoided to play the case where sound impacts the application program that foreground is shown.

Description

Application sound management method and device, storage medium and intelligent terminal
Technical Field
The embodiment of the application relates to an application program loading technology, in particular to a method and a device for managing application program sound, a storage medium and an intelligent terminal.
Background
At present, terminals such as smart phones, tablet computers, notebook computers, and smart appliances have become essential electronic devices in people's daily life. With the continuous intellectualization of the terminal equipment, the operating system is loaded in most terminal equipment, so that the terminal equipment can install abundant and various application programs and meet different requirements of users.
With the continuous improvement of the configuration of the terminal device, dozens or even hundreds of application programs can be installed in most terminal devices, and with the increasing abundance of the functions of the application programs, more and more resources are needed to be loaded when the application programs run. In order to improve user experience and reduce the starting time delay of some applications, the applications are preloaded in some scenes. However, in preloading applications, there is a possibility that some hardware is used to affect the current application displayed in the display screen
Disclosure of Invention
The embodiment of the application provides a method and a device for managing application program sound, a storage medium and an intelligent terminal, and can optimize a loading scheme of an application program.
In a first aspect, an embodiment of the present application provides a method for managing application sound, including:
detecting an audio playing event of an application program, and acquiring an audio file corresponding to the audio playing event;
acquiring a preset audio attribute of the application program;
and judging whether to allow the sound of the audio file to be played based on a pre-established audio playing class or not according to the preset audio attribute.
In a second aspect, an embodiment of the present application further provides an apparatus for managing application sound, where the apparatus includes:
the file acquisition module is used for detecting an audio playing event of an application program and acquiring an audio file corresponding to the audio playing event;
the attribute acquisition module is used for acquiring the preset audio attribute of the application program;
and the sound playing management module is used for judging whether the sound of the audio file is allowed to be played based on the pre-established audio playing class or not according to the preset audio attribute.
In a third aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a management method for application sound according to an embodiment of the present application.
In a fourth aspect, an embodiment of the present application provides an intelligent terminal, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the method for managing application sound according to the embodiment of the present application.
The embodiment of the application provides a management scheme of application program sound, which is characterized in that an audio playing event of an application program is detected, and an audio file corresponding to the audio playing event is decoded; acquiring a preset audio attribute of the application program; judging whether to allow the decoded audio file to be written into a pre-established audio playing class or not according to the preset audio attribute; and if so, writing the audio file into a pre-established audio playing class so as to play the sound of the audio file. By adopting the technical scheme, when the audio playing event of the application program is detected, the decoded audio file is temporarily not written into the pre-established audio playing class; when the preset audio attribute of the application program is allowed to be written, the audio file is written into the pre-established audio playing class, so that the sound playing operation can be effectively managed, and the condition that the playing sound of the application program is preloaded in the background to influence the application program displayed in the foreground is avoided.
Drawings
Fig. 1 is a flowchart of a method for managing application sound according to an embodiment of the present application;
FIG. 2 is a diagram illustrating a relative position relationship between a preloaded active window stack and a display area of a display screen according to an embodiment of the present disclosure;
FIG. 3 is a diagram illustrating a relative position relationship between a preloaded active window stack and a display area of a display screen according to an embodiment of the present application;
fig. 4 is a schematic diagram of application interface migration according to an embodiment of the present application;
fig. 5 is a flowchart of another management method for application sound according to an embodiment of the present application;
fig. 6 is a block diagram illustrating an apparatus for managing application sound according to an embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of an intelligent terminal according to an embodiment of the present application;
fig. 8 is a block diagram of a structure of a smart phone according to an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some of the structures related to the present application are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the steps as a sequential process, many of the steps can be performed in parallel, concurrently or simultaneously. In addition, the order of the steps may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
It should be noted that AudioTrack is a music playing class that manages and plays a single audio resource. It is used for playback of PCM (Pulse Code Modulation) audio streams. This is accomplished by pushing data to the AudioTrack object through write (byte [ ], int, int), write (short [ ], int, int), write (float [ ], int, int, int). The initiator that disables or reopens the audio playback function is the system server process and the responder is the AudioTrack. Since an AudioTrack corresponding to each application is created separately, the AudioTrack exists in the process of different applications. If an application program is inquired whether to prohibit writing audio data into the corresponding AudioTrack object, cross-process communication is involved. In the related art, the query of cross-process communication may be in the form of a file, a content provider, or the like. However, since the rights of the respective applications are not consistent, there may be a case where there is no right to read the file, and further, the AudioTrack class may not know whether or not to allow the audio data to be written to the AudioTrack object. In addition, the contentprovider mode is adopted, and the requirement of declaration in android manifest is needed in advance, so that the implementation is complicated. In addition, if the AudioTrack is prohibited from being created, the purpose of prohibiting the background preloaded application program from playing the sound can be achieved, but this way may cause the sound playing abnormality when the application program is switched to the foreground operation.
Fig. 1 is a flowchart of a management method for application sound according to an embodiment of the present disclosure, where the method may be performed by an application sound management apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an intelligent terminal. As shown in fig. 1, the method includes:
step 110, detecting an audio playing event of an application program, and acquiring an audio file corresponding to the audio playing event.
It should be noted that the intelligent terminal in the embodiment of the present application may include terminal devices such as a smart phone, a tablet computer, a notebook computer, a handheld game console, and an intelligent household appliance. The terminal is loaded with an operating system. The operating system may be Android, iOS, BlackBerry OS, windows mobile, or the like.
For example, the triggering condition of the audio playing event may be set according to an actual situation, and the embodiment of the present application is not particularly limited. For example, an audio play event may be triggered upon detection of insertion of a headphone jack into a headphone; or when the intelligent terminal is detected to be connected with external playing equipment (such as a Bluetooth headset, a wireless headset and an on-vehicle player), triggering an audio playing event; or, in the application program loading process, when the starting advertisement is played or the animation is started, the audio playing event is triggered; or, in the execution process of the preloaded application program operation, triggering an audio playing event when a starting advertisement or a starting animation is played in the background; or when an operation instruction of the target application program is detected, triggering an audio playing event; or, when the preloaded application program is detected to be migrated to the display screen for displaying, an audio playing event is triggered, and the like. When the audio playing event is triggered, the system may detect that the audio playing event is triggered by reading the flag bit or receiving a trigger instruction, and the like, and the specific detection method is not specifically limited in this embodiment of the application.
Illustratively, an audio playback class is created upon detection of an audio playback event of an application. The audio playing class may be AudioTrack, that is, when an audio playing event of an application program is detected, AudioTrack is created, and after the AudioTrack is created, an AudioTrack object is initialized and the size of an audio buffer related to the AudioTrack object is specified in detail in a construction method, so that the time length of audio data that can be played by the AudioTrack is determined. The AudioTrack is suitable for playing the decoded audio data, and can also acquire an audio file corresponding to the audio playing event, and create a decoder to decode the audio file to obtain the decoded audio data. In Android, MediaCodec can be used to access the underlying media codec, and media can be coded/decoded. In the embodiment of the present application, the MediaCodec processes data in an asynchronous manner, and uses a set of input/output buffers (bytebuffers). By requesting an empty input buffer (ByteBuffer), it is filled with data and passed to the decoder for processing. The decoder processes the data and outputs the processed result to an empty output buffer (ByteBuffer). After the output buffered data is used, it is released back to the codec.
It should be noted that the audio playback class is not limited to the AudioTrack listed above, and may be selected according to actual situations, and the embodiment of the present application is not particularly limited. For example, the audio play class may also be MediaPlayer, and the like.
And step 120, acquiring the preset audio attribute of the application program.
It should be noted that the preset audio attribute may be an attribute configured for each application in advance, and is used for representing a scene in which the application is allowed to play sound and a scene in which the application is prohibited from playing sound. For example, while application a is being displayed on the display screen, provision may be made for allowing application a to play sound using an audio device; if the pre-loading operation on the application D, the application F and the application X is executed in the background at this time, the application D, the application F and the application X need to be prohibited from playing the sound by using the audio device, and the permission can be realized by setting the audio attribute for the application program in advance.
Illustratively, the preset audio attributes of the application program may be obtained based on a pre-created audio playback class. For example, the audio playing attribute corresponding to the user identifier of the application program may be obtained through a get instruction in the AudioTrack class. It should be noted that the user identifier of the application program and the preset audio attribute may be stored in association with each other in the form of a key-value pair. For example, for an android system, the property mechanism may be employed to set the audio properties of each application. Each application can obtain a common android property, wherein the common property refers to a mechanism that a header file is not a character string such as a persistence ro. The advantage of adopting the property mechanism is that the single query time of the property mechanism is in the level of several milliseconds, the query speed is high, the code amount is small, the implementation is simple, and the running speed is high.
For example, the audio property may be set by using the property mechanism, such as the following code sys. For example, if sys.audio.disable < uid > is set to 1, it indicates that the application program corresponding to the user identifier is prohibited from playing sound; set sys.audio.disable < uid > to 0, it indicates that the user is allowed to identify the corresponding application program to play sound. The audio attribute is preset for the application program in the same way, when the system is started, the audio attribute is loaded to a shared memory, and each application process in the system can map the shared memory to the memory space of the application process, so that the attribute content can be directly read. For example, if an application program whose uid is 10030 is to be prohibited from playing sound, system. For another example, if an application program whose uid is 10030 is to be allowed to play a sound, sys.
Optionally, before detecting the audio playing event of the application program, determining whether the application program is a preloaded application program, if so, setting an audio attribute of the preloaded application program when a preloading operation is performed on the preloaded application program, otherwise, setting the audio attribute of the application program as a sound allowing to be played. For example, when an audio playing event of an application program is detected to be triggered, whether the application program is a preloaded application program which is being preloaded is judged, and if yes, the audio attribute of the preloaded application program is set to be a sound which is forbidden to be played; if the application program is a preloaded application program and an operation instruction for the preloaded application program is detected, the audio attribute of the preloaded application program can be set to allow sound to be played. In addition, if the application program is not preloaded, when detecting that the audio playing event of the application program is triggered, setting the audio attribute of the application program as allowing the sound to be played.
The preloaded application may be understood as an application that a user may open soon, and may be a fixed application that is set in advance, or may be an application that is predicted in a certain manner. The preloaded applications may include one or more. Alternatively, a prediction model may be used to predict the application to be preloaded. The prediction model may be a machine learning model, and the algorithm used may include a Recurrent Neural Network (RNN), a Long Short-Term Memory (LSTM) network, a threshold cycle unit, a simple cycle unit, an auto-encoder, a decision tree, a random forest, a feature mean classification, a classification regression tree, a hidden markov, a K-nearest neighbor (KNN) algorithm, a logistic regression model, a bayesian model, a gaussian model, and a KL divergence (Kullback-Leibler) or the like.
Optionally, in the process that the user uses the terminal, a training sample may be collected, the training sample is adopted to train the preset initial model, and finally, a prediction model for predicting the application program to be preloaded is obtained. For example, the elements contained in the training sample may include a time sequence or an order sequence in which the application was opened; can include the time, place, frequency, etc. that the application was opened; the method can include the running state of the terminal, such as the on-off state of a mobile data network, the connection state of a wireless hotspot, the identity information of the connected wireless hotspot, the currently running application program, the previous foreground application program, the stay time of the current application program in the background, the last time the current application program is switched to the background, the plugging state of an earphone jack, the charging state, the battery power information, the screen display time and the like; and the data collected by sensors integrated in the terminal can be included, such as a motion sensor, a light sensor, a temperature sensor, a humidity sensor and the like.
Step 130, judging whether to allow the sound of the audio file to be played based on the pre-established audio playing class according to the preset audio attribute.
Illustratively, if the preset audio attribute is that sound is allowed to be played, the audio file is allowed to be played based on a pre-created audio playing class. And if the preset audio attribute is that the sound is prohibited to be played, prohibiting the audio file from being played based on the pre-established audio playing class. For example, an Audio play event of an application is detected, an AudioTrack is created, the AudioTrack is initialized, and an Audio device is started (Audio device information is packaged in an AudioSystem class). And acquiring an audio file corresponding to the audio playing event, and decoding the audio file to obtain decoded audio data. Before writing audio data into the AudioTrack object, inquiring the memory space of an application process according to the uid of the application program, and acquiring the preset audio attribute of the application program. And judging whether to allow the decoded audio data to be written into the AudioTrack according to the value of the preset audio attribute so as to play the audio file. For example, if the value of the preset audio attribute is 1, the decoded audio data is prohibited from being written into the AudioTrack. Because the sound of the audio file corresponding to the audio data can only be played by writing the decoded audio data into the object of the AudioTrack, if the audio data is prohibited from being written into the AudioTrack, the sound of the audio file corresponding to the audio data cannot be played, and the application program is prohibited from playing the sound. If the value of the preset audio attribute is 0, the decoded audio data is allowed to be written into the AudioTrack, so that the sound of an audio file corresponding to the audio data is played, and the sound is allowed to be played by the application program.
According to the technical scheme of the embodiment of the application, when an audio playing event of an application program is detected, an audio file corresponding to the audio playing event is decoded; acquiring a preset audio attribute of the application program; judging whether to allow the decoded audio file to be written into a pre-established audio playing class or not according to the preset audio attribute; and if so, writing the audio file into a pre-established audio playing class so as to play the sound of the audio file. By adopting the technical scheme, when the audio playing event of the application program is detected, the decoded audio file is temporarily not written into the pre-established audio playing class; when the preset audio attribute of the application program is allowed to be written, the audio file is written into the pre-established audio playing class, so that the sound playing operation can be effectively managed, and the condition that the playing sound of the application program is preloaded in the background to influence the application program displayed in the foreground is avoided.
In some embodiments, when preloading the preloaded application program, setting the audio attribute of the preloaded application program as a sound playing prohibition includes: preloading an application interface corresponding to the preloaded application program based on a pre-created preloaded active window stack, possibly needing to play sound of the preloaded application program in the preloading process, and setting the audio attribute of the preloaded application program to be sound prohibited before playing the sound, wherein the boundary coordinate corresponding to the preloaded active window stack is located outside the coordinate range of the display screen.
It should be noted that, an active window Stack (preloaded Stack) is preloaded to indicate a Stack displayed by the preloaded application, and the boundary coordinates of the preloaded Stack are set to be outside the coordinate range of the display screen, where the preloaded application can be displayed. The boundary coordinates corresponding to the preloaded active window stack are outside the coordinate range of the display screen.
In the embodiment of the present application, the active window may be understood as a separate interface directly providing interaction and operation for a user, and different names may be used in different operating systems to name the interface. For ease of understanding, the following description will be made taking an Android (Android) operating system as an example.
In the Android system, the active window is called Activity. Activity is a component responsible for interacting with a user that provides a screen (which may be understood as a screen interface, rather than a display screen of an entity) for the user to interact to accomplish a task. In an android application, an Activity is usually a separate screen on which controls can be displayed and events of the user can be monitored and processed. In managing Activity, there are two concepts: task Stack and Stack. The Task corresponds to an application program, the Task is used for storing activities, one Task can store one or more activities, and the activities follow the principle of first-in first-out and last-in first-out. And the Stack is used for managing the Task, generally, one Stack manages the Task to which each Activity required to be shown by one screen belongs, and one Stack can manage one or more tasks, and of course, the Stack also follows the basic management principle of the Stack. The screens described herein are not necessarily completely separate display screens, and in the case of "two screens", the two screens may be only two regions of a complete display screen that independently display respective display contents. Of course, if the terminal has two or even more separate display screens, the "two screens" may also be two separate display screens.
In the Android system, multi-window modes are supported, which may include split screen mode, picture-in-picture mode, and free mode (FreeForm). In the multi-window mode, the Stack in which the application is located may have its own size (size), and may include upper, lower, left, and right coordinates in a coordinate system with the upper left corner of the terminal screen as the origin. For example, (a, b, c, d), which generally describes the boundary of a rectangle, the coordinates of the upper left corner and the coordinates of the lower right corner of the rectangle can be used for representation, i.e. the coordinates of the upper left corner of the rectangle are (a, b), and the coordinates of the lower right corner are (c, d), and such a rectangular area corresponds to the size of Stack. The in-application layout in the Stack is based on the size of the Stack, that is, the application interface corresponding to Activity is displayed within the boundary range of the size.
In the multi-window mode, multiple applications may be allowed to be visible, including both system and user visibility and system-only visibility. The system and the user can see the display on the display screen, and the user can see the display; system-only-visible means that the operating system is visible, but not the user, and may be obscured by foreground applications or displayed outside the display screen as the application is intended to implement.
In the embodiment of the application, the application interface of the application to be loaded is preloaded outside the display screen, which can be realized based on a multi-window mechanism of an operating system, and the size corresponding to the application is set outside the display screen through the multi-window mechanism, so that the purpose of being invisible to a user is achieved, and the display of the display content of the foreground application on the display screen is not affected.
Generally, in the multi-window mode, there may be multiple types of stacks, for example, Home Stack represents a Stack displayed by a desktop application, App Stack represents a Stack displayed by a third-party application, and there may be other split-screen stacks, and contents contained in the three types of stacks may be displayed on a display screen, which are collectively referred to as application active window stacks in this embodiment.
Illustratively, the preloading of the application interface corresponding to the application program to be loaded based on the pre-created preloading active window stack includes: creating a target process corresponding to the application program to be loaded; creating a task stack corresponding to the application program to be loaded in a pre-created preloading active window stack; starting an active window corresponding to the application program to be loaded in the task stack based on the target process; and drawing and displaying an application interface corresponding to the application program to be loaded based on the started active window. The method has the advantages that the boundary coordinates corresponding to the preloaded active window stack are located outside the coordinate range of the display screen, so that the application interface of the application program to be loaded can be drawn and displayed based on the preloaded active window stack outside the screen coordinate range, the running and the display of the foreground application program cannot be interfered, the system stability is ensured, and the starting speed of the target application program is effectively improved. While creating the target process, an initialization process of the target process may also be included. In the execution process of the above steps, preloading of other resources may also be involved, such as application service starting, memory allocation, file content reading, network data acquisition, and the like.
In some embodiments, further comprising: and sending a fake focus notification to the application program to be loaded, and keeping continuous drawing and display updating of the application interface corresponding to the application program to be loaded within a preset time period based on the fake focus notification. The method has the advantages that the drawing and the display of the application interface can be completed under the condition that the application program to be loaded obtains the focus and is visible to the system, the completion degree of preloading is improved, and the focus of foreground application is not influenced. The focus in the embodiment of the present application is also referred to as an input focus, and the fake focus is independent from the focus corresponding to the foreground application. Generally, for the current Android system, a focus is unique, for example, input operations such as touch and the like only take effect on the focus, the system end and the application end are consistent for inputting focus information, and once the system end modifies the input focus information, the system end sends information that the input focus information changes to the application, so that the method ensures that the input focus information of the system end and the application end is consistent. In the embodiment of the application, the purpose that the application end can forge the focus is achieved by separating the mode that the system end and the application end input the focus information. Specifically, in the embodiment of the application, the focus information is forged for the preloaded application, so that the preloaded application has the focus information, and the focus information of the system end is still correct, so that the preloaded application can be drawn normally, and the purpose of full loading is achieved. The focus exists in the system end and the application end, which can be regarded as a server end (server) and a client end (client), the system end records the application with the focus, and the application end stores a flag bit (flag) to identify whether the application has the focus. The time for forging the input focus can be that when a new window of the Android window system is added and the focus needs to be updated, a forged focus notification is generated and sent. The method for forging the focus may be a method for changing the focus of the window by calling the client end of the window, so that the window acquires the focus. Specifically, the forged focus notification can be sent based on a Binder mechanism, which is the most common mode of interprocess communication of the Android system and adopts a c/s architecture, i.e., a client/service architecture.
For some terminals, especially for intelligent terminals such as mobile phones and tablet computers, in order to facilitate the use of users, the display modes of the display screen generally include vertical screen display and horizontal screen display, many applications display by default in the vertical screen mode, some applications display by default in the horizontal screen mode (such as some online games), and some applications switch the horizontal and vertical screen display along with the direction in which the user holds the terminal during the use of the terminal. In some embodiments of the present application, a boundary coordinate corresponding to the preloaded active window stack is (H, 0, 2H, H), a coordinate system corresponding to the boundary coordinate is a system coordinate, an origin of the system coordinate is an upper left corner of the display screen, and H is a length of a long side of a display area of the display screen. That is, the side corresponding to H is the maximum side of the display area of the display screen, and is the height of the display screen in the vertical screen display and the width of the display screen in the horizontal screen display. This is done to allow for the display of a landscape screen, pre-loaded application landscape displays, and the normal display of some applications. Fig. 2 is a schematic diagram illustrating a relative position relationship between a preloaded active window stack and a display area of a display screen according to an embodiment of the present disclosure. As shown in fig. 2, at this time, the display screen is in a vertical screen mode, the origin of the terminal system coordinates is the left vertex (0,0) of the display screen 201, the width direction of the display screen 201 is the X axis, the height direction is the Y axis, the boundary coordinates corresponding to the preloaded Stack202 are (H, 0, 2H, H), H is the screen height, that is, the area in the left solid line rectangular range is the main screen display area, and the area in the right dotted line rectangular range is the preloaded display area. Fig. 3 is a schematic diagram illustrating a relative position relationship between a preloaded active window stack and a display area of a display screen according to an embodiment of the present application. As shown in fig. 3, at this time, the display screen is in a landscape mode, the origin of the terminal system coordinates is the left vertex (0,0) of the display screen 301, the height direction of the display screen 301 is the X axis, the width direction is the Y axis, the boundary coordinates corresponding to the preloaded Stack202 are (H, 0, 2H, H), H is the screen height, that is, the area in the left solid line rectangular range is the main screen display area, and the area in the right dotted line rectangular range is the preloaded display area.
The reason why the pre-loaded Stack boundaries are so set is that:
the abscissa of the upper left corner is H, which is an interface for preventing the display screen (also referred to as a main screen) from displaying the preloaded application during the landscape screen, and since the main screen has a landscape mode in addition to the portrait mode, the abscissa of the upper left corner of the rectangular area corresponding to the preloaded Stack is set to the screen height in order to prevent the main screen display area from displaying the local part of the preloaded application during the landscape screen of the main screen.
The ordinate in the upper left corner is 0 in order for the preload application to be able to calculate the status bar height correctly. In order to better design a User Interface (UI), the Android application can customize the top status bar, and if the vertical coordinate corresponding to the upper edge is not equal to 0, the height of the status bar may be wrong.
The abscissa of the lower right corner is 2H (2 times the screen height), that is, the width of the rectangle corresponding to the preloaded Stack is equal to the screen height, so that the size of the preloaded Stack can contain the landscape application at the time of preloading (that is, the application interface is an application program in a landscape display mode).
The ordinate of the lower right corner is H, i.e. the height of the rectangle corresponding to the preloaded Stack is equal to the screen height, so as to preload the size of the Stack and be able to contain the vertical screen application at the time of preloading.
For the reasons described above, the inventors set the size of the preload Stack to (H, 0, 2H, H).
In addition, fig. 4 is a schematic application interface migration diagram provided in the embodiment of the present application, as shown in fig. 4, when an operation instruction of a target application program is received, an application interface 401 corresponding to the target application program included in a preloaded active window Stack is migrated to a display screen 201 to be displayed, specifically, a task to which the preloaded application interface belongs is migrated to the top of an application active window Stack, and size information, configuration information, and visibility of the task are updated, so that the application interface can be normally displayed on the display screen.
In some embodiments, after preloading an application interface corresponding to the preloaded application program based on a pre-created preloaded active window stack, the method further includes: when an operation instruction of a target application program is received, modifying the audio attribute of the target application program into sound which is allowed to be played; and migrating an application interface corresponding to the target application program contained in the preloading activity window stack to a display screen for displaying. It should be noted that the target application is an application corresponding to the detected application opening operation, that is, an application actually opened by the user. The method includes that the target application program can be an object of an operation instruction, namely when the operation instruction aiming at the target application program is received, the audio attribute of the target application program is modified to allow sound to be played, and a task stack corresponding to the target application program contained in a pre-loading active window stack is migrated to the top of the application active window stack; and updating the size information, the configuration information and the visibility of the task stack to realize that the application interface corresponding to the target application program is displayed on the display screen. The advantage that sets up like this lies in, can guarantee the stability of interface migration process, guarantees that the card screen can not appear in the recovery process, the black screen or the migration speed is slow scheduling problem.
Fig. 5 is a flowchart of another method for managing application sound according to an embodiment of the present application, where the method includes:
step 501, detecting an application preloading event.
The intelligent terminal judges whether a preset triggering condition of the application preloading event is met, and if yes, the application preloading event is triggered.
Step 502, determining an application program to be preloaded, recording the application program as a preloaded application program, and setting the audio attribute of the preloaded application program as a sound playing prohibition.
It should be noted that, for the non-preloaded application, the audio attribute is to allow playing of sound.
Illustratively, an application interface corresponding to the preloaded application program is preloaded based on a pre-created preloaded active window stack, and the audio attribute of the preloaded application program is set as a sound prohibited to be played, wherein the boundary coordinate corresponding to the preloaded active window stack is located outside the coordinate range of the display screen. It should be noted that before preloading an application interface corresponding to the preloaded application program based on a pre-created preloaded active window stack, determining whether the pre-created preloaded active window stack exists, if not, creating the preloaded active window stack according to a preset rule, otherwise, creating a target process corresponding to the preloaded application program, and initializing the target process. And creating a task stack corresponding to the application program in the preloading active window stack. And starting an active window corresponding to the preloaded application program in the task stack based on the target process, and sending a fake focus notification to the target application program. And updating the focus zone bit corresponding to the application program according to the fake focus notification, and continuously drawing and updating the application interface corresponding to the application program based on the started active window in a preset time period. Before the active window corresponding to the preloaded application program is started, the audio attribute of the preloaded application program is set as a sound for prohibiting playing, so as to prohibit playing of a start advertisement or a sound for starting a picture.
In the embodiment of the application, the creation time of the preloaded active window Stack (namely, the preloaded Stack) is not limited, and the preloaded Stack can be set to be in a resident state by default before the terminal leaves a factory, namely, the preloaded Stack exists all the time; the method can also be established when the terminal is started or after the terminal is successfully unlocked; it may also be created after an application preload event is triggered (which may be before the target application is determined), and so on.
In the embodiment of the application, if the pre-established preloading activity window stack does not exist, the pre-established preloading activity window stack is established according to the preset rule; and preloading an application interface corresponding to the target application program based on the created preloading active window stack. The method has the advantages that after the application program to be preloaded is determined, whether the preloaded Stack exists or not is judged, if yes, new construction is not needed, and if not, creation is conducted, so that system resources can be saved. It can be understood that, when there are multiple preloaded applications, that is, when multiple applications need to be continuously preloaded in a short time, the preloaded Stack is already created before the first preloaded application starts to load, and then the preloaded Stack exists before the second preloaded application starts to load, which may not be necessary to perform the above determination.
Step 503, detecting an audio playing event of the application program.
The application programs include preloaded application programs and non-preloaded application programs. The intelligent terminal judges whether a preset triggering condition of the audio playing event is met, and if yes, the audio playing event is triggered.
Step 504, when an audio playing event of the application program is detected, an audio playing class is created.
It should be noted that, for the same application program, if the audio playing class already exists, when the audio playing event of the application program is detected, it is not necessary to create the audio playing class again, that is, for the application program with the existing audio playing class, this step may be omitted.
And 505, acquiring an audio file corresponding to the audio playing event, and decoding the audio file to obtain decoded audio data.
Step 506, acquiring the preset audio attribute of the application program based on the audio playing class.
Step 507, judging whether the preset audio attribute is that sound is allowed to be played, if so, executing step 508, otherwise, executing step 509.
Step 508, allowing the audio data to be written into the audio playing class to play the sound of the audio file.
Step 509, forbidding to write the audio data into the audio playing class, so as to forbid to play the sound of the audio file.
Because the audio attribute of the application program running in the foreground is that sound is allowed to be played, the sound can be played normally. If the system is detected to execute the application preloading operation, the relevant operation of the preloaded application program runs in the background, and the preset audio attribute is that the playing of sound is forbidden, so that the influence on the normal running of the application program running in the foreground can be avoided.
Step 510, when receiving an operation instruction of a target application program, modifying an audio attribute of the target application program to allow sound to be played.
Step 511, migrating the application interface corresponding to the target application program contained in the preloaded active window stack to a display screen for displaying, triggering an audio playing event, and executing step 503.
Specifically, taking an application active window as an App Stack as an example, moving the task to the App Stack may include: this task is removed from the list in the original Stack (i.e., the preloaded Stack) and added at the top in the new Stack (App Stack). Each stack has a list for recording all the tasks contained in the stack; correspondingly, each task will record the stack information of the task at the same time. Since a stack contains attributes such as size, configuration, visibility, and zorder, which may be different from other stacks, the attributes such as zorder of the task may be changed simply by adding the task to the list of the new stack. The top added in the new stack is to make the task visible.
And step 512, updating the size information, the configuration information and the visibility of the task stack to display the current application interface corresponding to the target application program on a display screen.
It can be understood that, in the preloading process, the application interface corresponding to the target application program is in the continuous drawing and display updating process, and the timing when the user really starts the target application program is uncertain, and may receive an operation instruction in the preloading process, so that the application interface currently displayed in the preloading Stack may be migrated to the display screen for display. If the user opens the target application program after the preloading is completed, the last application interface when the preloading is completed can be migrated to the display screen to be displayed.
Specifically, the updating of the size information and the configuration information of the task stack is to change the boundary of the application, and may specifically include: actively updating the size and configuration information. The size and configuration of the task cannot be changed immediately only by using the above task migration operation, so that the method for modifying the size and configuration of the task can be actively called, the application state is ensured to be correct, and the application can normally work in the foreground.
Specifically, the update task is visible because, after the size and configuration are updated, the target application may not be visible at this time, a method of updating the visibility of the new stack is invoked, the visible applications are searched from top to bottom, set to visible, and the corresponding window surface is updated to visible. The visible application judgment method may include: is not occluded by other applications on the zorder; is not shielded by the lock screen; the state of the top activity of the application is a non-initializing or non-exiting state.
According to the application program sound management method provided by the embodiment of the application program, in the process of executing the preloading operation on the preloaded application program, writing of audio data into the audio playing class corresponding to the preloaded application program is forbidden, so that the application program is forbidden to use sound, the influence of the preloaded application program on the application program running in the foreground can be reduced, the preparation work before application starting is completed to a large extent, when the target application program is really started, the preloaded application interface is directly migrated to the display screen to be displayed, and the starting speed is effectively increased.
Fig. 6 is a block diagram of an application sound management apparatus according to an embodiment of the present disclosure, where the apparatus may be implemented by software and/or hardware, and is generally integrated in an intelligent terminal, and the application sound management apparatus may perform playback management of an application sound by executing an application sound management method. As shown in fig. 6, the apparatus includes:
the file obtaining module 610 detects an audio playing event of an application program, and obtains an audio file corresponding to the audio playing event;
an attribute obtaining module 620, configured to obtain a preset audio attribute of the application program;
and a sound playing management module 630, configured to determine whether to allow the sound of the audio file to be played based on a pre-created audio playing class according to the preset audio attribute.
According to the management device for the application program sound, when an audio playing event of the application program is detected, the decoded audio file is temporarily not written into a pre-established audio playing class; when the preset audio attribute of the application program is allowed to be written, the audio file is written into the pre-established audio playing class, so that the sound playing operation can be effectively managed, and the condition that the playing sound of the application program is preloaded in the background to influence the application program displayed in the foreground is avoided.
Optionally, the file obtaining module 610 is specifically configured to:
when an audio playing event of an application program is detected, creating an audio playing class;
and acquiring an audio file corresponding to the audio playing event, and decoding the audio file to obtain decoded audio data.
Optionally, the attribute obtaining module 620 is specifically configured to:
and acquiring the preset audio attribute of the application program based on the audio playing class.
Optionally, the sound playing management module 630 is specifically configured to:
when the preset audio attribute is that sound is allowed to be played, allowing the audio data to be written into the audio playing class so as to play the sound of the audio file;
or,
and when the preset audio attribute is the playing-prohibited sound, prohibiting the audio data from being written into the audio playing class so as to prohibit the sound of the audio file from being played.
Optionally, the method further includes:
the attribute setting module is used for judging whether the application program is a preloaded application program or not before detecting an audio playing event of the application program; if so, setting the audio attribute of the preloaded application program as a sound forbidden to be played when the preloaded application program is preloaded; otherwise, setting the audio attribute of the application program as allowing the sound to be played.
Optionally, the attribute setting module is specifically configured to:
and preloading an application interface corresponding to the preloaded application program based on a pre-created preloaded active window stack, and setting the audio attribute of the preloaded application program as a sound prohibited to be played, wherein the boundary coordinate corresponding to the preloaded active window stack is positioned outside the coordinate range of the display screen.
Optionally, the method further includes:
the attribute updating module is used for modifying the audio attribute of the target application program into sound which is allowed to be played when receiving an operation instruction of the target application program after an application interface corresponding to the preloading application program is preloaded based on a preloading activity window stack which is created in advance;
and the application display module is used for transferring the application interface corresponding to the target application program contained in the preloading activity window stack to a display screen for displaying.
Embodiments of the present application also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a method for managing sound of an application, the method including:
detecting an audio playing event of an application program, and acquiring an audio file corresponding to the audio playing event;
acquiring a preset audio attribute of the application program;
and judging whether to allow the sound of the audio file to be played based on a pre-established audio playing class or not according to the preset audio attribute.
Storage medium-any of various types of memory devices or storage devices. The term "storage medium" is intended to include: mounting media such as CD-ROM, floppy disk, or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Lanbas (Rambus) RAM, etc.; non-volatile memory such as flash memory, magnetic media (e.g., hard disk or optical storage); registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in a first computer system in which the program is executed, or may be located in a different second computer system connected to the first computer system through a network (such as the internet). The second computer system may provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations, such as in different computer systems that are connected by a network. The storage medium may store program instructions (e.g., embodied as a computer program) that are executable by one or more processors.
Of course, the storage medium provided in the embodiments of the present application contains computer-executable instructions, and the computer-executable instructions are not limited to the management operation of the application sound described above, and may also perform related operations in the management method of the application sound provided in any embodiments of the present application.
The embodiment of the application provides an intelligent terminal, an operating system is arranged in the intelligent terminal, and a management device of application program sound provided by the embodiment of the application can be integrated in the intelligent terminal. The intelligent terminal can be a terminal device such as a smart phone, a tablet computer, a notebook computer, a handheld game console and an intelligent household appliance. Fig. 7 is a schematic structural diagram of an intelligent terminal provided in an embodiment of the present application. As shown in fig. 7, the intelligent terminal includes a memory 710 and a processor 720. The memory 710 is used for storing computer programs and the like; the processor 720 reads and executes the computer programs stored in the memory 710. The processor 720, when executing the computer program, performs the steps of: detecting an audio playing event of an application program, and acquiring an audio file corresponding to the audio playing event; acquiring a preset audio attribute of the application program; and judging whether to allow the sound of the audio file to be played based on a pre-established audio playing class or not according to the preset audio attribute.
The memory and the processor listed in the above examples are all part of components of the intelligent terminal, and the intelligent terminal may further include other components. Taking a smart phone as an example, a possible structure of the smart terminal is described. Fig. 8 is a block diagram of a structure of a smart phone according to an embodiment of the present application. As shown in fig. 8, the smart phone may include: memory 801, a Central Processing Unit (CPU) 802 (also known as a processor, hereinafter CPU), a peripheral interface 803, a Radio Frequency (RF) circuit 805, an audio circuit 806, a speaker 811, a touch screen 812, a power management chip 808, an input/output (I/O) subsystem 809, other input/control devices 810, and an external port 804, which communicate via one or more communication buses or signal lines 807.
It should be understood that the illustrated smartphone 800 is merely one example of a smart terminal, and that the smartphone 800 may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration of components. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.
The following describes in detail a smartphone integrated with an application sound management apparatus according to this embodiment.
A memory 801, the memory 801 being accessible by the CPU802, the peripheral interface 803, and the like, the memory 801 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other volatile solid state storage devices. The memory 801 stores a computer program, and may store audio attributes of an application program, an audio file, audio data obtained by decoding the audio file, and the like.
A peripheral interface 803, said peripheral interface 803 allowing input and output peripherals of the device to be connected to the CPU802 and the memory 801.
I/O subsystem 809, which I/O subsystem 809 may connect input and output peripherals on the device, such as touch screen 812 and other input/control devices 810, to peripheral interface 803. The I/O subsystem 809 may include a display controller 8091 and one or more input controllers 8092 for controlling other input/control devices 810. Where one or more input controllers 8092 receive electrical signals from or transmit electrical signals to other input/control devices 810, other input/control devices 810 may include physical buttons (push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels. It is worth noting that the input controller 8092 may be connected to any of the following: a keyboard, an infrared port, a USB interface, and a pointing device such as a mouse.
A touch screen 812, which touch screen 812 is an input interface and an output interface between the user terminal and the user, displays visual output to the user, which may include graphics, text, icons, video, and the like.
The display controller 8091 in the I/O subsystem 809 receives electrical signals from the touch screen 812 or sends electrical signals to the touch screen 812. The touch screen 812 detects a contact on the touch screen, and the display controller 8091 converts the detected contact into an interaction with a user interface object displayed on the touch screen 812, that is, implements a human-computer interaction, and the user interface object displayed on the touch screen 812 may be an icon for running a game, an icon networked to a corresponding network, or the like. It is worth mentioning that the device may also comprise a light mouse, which is a touch sensitive surface that does not show visual output, or an extension of the touch sensitive surface formed by the touch screen.
The RF circuit 805 is mainly used to establish communication between the mobile phone and the wireless network (i.e., the network side), and implement data reception and transmission between the mobile phone and the wireless network. Such as sending and receiving short messages, e-mails, etc. In particular, the RF circuitry 805 receives and transmits RF signals, also referred to as electromagnetic signals, which the RF circuitry 805 converts to or from electrical signals, and communicates with communication networks and other devices over. RF circuitry 805 may include known circuitry for performing these functions including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC (CODEC) chipset, a Subscriber Identity Module (SIM), and so forth.
The audio circuit 806 is mainly used to receive audio data from the peripheral interface 803, convert the audio data into an electric signal, and transmit the electric signal to the speaker 811. The system writes the decoded Audio data into the AudioTrack, transmits the Audio data into the Audio Service through the Binder IPC, and calls the Audio hardware abstraction layer Audio HAL through the AudioFlinger to output the Audio data to the Audio circuit 806 of the corresponding Audio device.
The speaker 811 is used to convert the voice signal received by the handset from the wireless network through the RF circuit 805 into sound and play the sound to the user.
And the power management chip 808 is used for supplying power and managing power to the hardware connected with the CPU802, the I/O subsystem and the peripheral interface.
The intelligent terminal provided by the embodiment of the application can temporarily not write the decoded audio file into the pre-established audio playing class when detecting the audio playing event of the application program; when the preset audio attribute of the application program is allowed to be written, the audio file is written into the pre-established audio playing class, so that the sound playing operation can be effectively managed, and the condition that the playing sound of the application program is preloaded in the background to influence the application program displayed in the foreground is avoided.
The management device, the storage medium and the intelligent terminal for the application sound provided in the above embodiments can execute the management method for the application sound provided in any embodiment of the present application, and have corresponding functional modules and beneficial effects for executing the method. For technical details that are not described in detail in the above embodiments, reference may be made to a method for managing application sound provided in any embodiment of the present application.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present application and the technical principles employed. It will be understood by those skilled in the art that the present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the appended claims.

Claims (10)

1. A method for managing application sound, comprising:
detecting an audio playing event of an application program, and acquiring an audio file corresponding to the audio playing event;
acquiring a preset audio attribute of the application program;
and judging whether to allow the sound of the audio file to be played based on a pre-established audio playing class or not according to the preset audio attribute.
2. The method according to claim 1, wherein detecting an audio playing event of an application program, and acquiring an audio file corresponding to the audio playing event comprises:
when an audio playing event of an application program is detected, creating an audio playing class;
and acquiring an audio file corresponding to the audio playing event, and decoding the audio file to obtain decoded audio data.
3. The method of claim 2, wherein obtaining the preset audio property of the application program comprises:
and acquiring the preset audio attribute of the application program based on the audio playing class.
4. The method of claim 2, wherein determining whether to allow the sound of the audio file to be played based on a pre-created audio playback class according to the preset audio attributes comprises:
when the preset audio attribute is that sound is allowed to be played, allowing the audio data to be written into the audio playing class so as to play the sound of the audio file;
or,
and when the preset audio attribute is the playing-prohibited sound, prohibiting the audio data from being written into the audio playing class so as to prohibit the sound of the audio file from being played.
5. The method of any one of claims 1 to 4, further comprising, prior to detecting an audio play event of an application:
judging whether the application program is a preloaded application program;
if so, setting the audio attribute of the preloaded application program as a sound forbidden to be played when the preloaded application program is preloaded;
otherwise, setting the audio attribute of the application program as allowing the sound to be played.
6. The method of claim 5, wherein setting the audio attribute of the preloaded application program to be a play-prohibited sound when preloading the preloaded application program comprises:
and preloading an application interface corresponding to the preloaded application program based on a pre-created preloaded active window stack, and setting the audio attribute of the preloaded application program as a sound prohibited to be played, wherein the boundary coordinate corresponding to the preloaded active window stack is positioned outside the coordinate range of the display screen.
7. The method of claim 6, further comprising, after preloading an application interface corresponding to the preloaded application based on a pre-created preloaded active window stack:
when an operation instruction of a target application program is received, modifying the audio attribute of the target application program into sound which is allowed to be played;
and migrating an application interface corresponding to the target application program contained in the preloading activity window stack to a display screen for displaying.
8. An apparatus for managing application sound, comprising:
the file acquisition module is used for detecting an audio playing event of an application program and acquiring an audio file corresponding to the audio playing event;
the attribute acquisition module is used for acquiring the preset audio attribute of the application program;
and the sound playing management module is used for judging whether the sound of the audio file is allowed to be played based on the pre-established audio playing class or not according to the preset audio attribute.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a method of managing sound of an application program according to any one of claims 1 to 7.
10. An intelligent terminal, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method for managing sound of an application program according to any one of claims 1 to 7 when executing the computer program.
CN201810578119.5A 2018-06-05 2018-06-05 Management method, device, storage medium and the intelligent terminal of application program sound Pending CN108845840A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810578119.5A CN108845840A (en) 2018-06-05 2018-06-05 Management method, device, storage medium and the intelligent terminal of application program sound

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810578119.5A CN108845840A (en) 2018-06-05 2018-06-05 Management method, device, storage medium and the intelligent terminal of application program sound

Publications (1)

Publication Number Publication Date
CN108845840A true CN108845840A (en) 2018-11-20

Family

ID=64210489

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810578119.5A Pending CN108845840A (en) 2018-06-05 2018-06-05 Management method, device, storage medium and the intelligent terminal of application program sound

Country Status (1)

Country Link
CN (1) CN108845840A (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109614252A (en) * 2018-12-10 2019-04-12 苏州思必驰信息科技有限公司 Audio playout schedule method and system for Intelligent story device
CN110225386A (en) * 2019-05-09 2019-09-10 青岛海信电器股份有限公司 A kind of display control method, display equipment
CN112615853A (en) * 2020-12-16 2021-04-06 瑞芯微电子股份有限公司 Android device audio data access method
CN113849241A (en) * 2020-06-10 2021-12-28 Oppo(重庆)智能科技有限公司 Audio playing control method, intelligent watch and device with storage function
CN114201226A (en) * 2020-08-26 2022-03-18 北京小米移动软件有限公司 Application starting method and device, electronic equipment and storage medium
CN116679900A (en) * 2022-12-23 2023-09-01 荣耀终端有限公司 Audio service processing method, firmware loading method and related devices

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103596641A (en) * 2012-10-18 2014-02-19 华为终端有限公司 Audio frequency managing method and device
CN103714837A (en) * 2013-12-18 2014-04-09 福州瑞芯微电子有限公司 Electronic device and method for playing audio files
CN105959466A (en) * 2016-04-22 2016-09-21 青岛海信移动通信技术股份有限公司 Method and device for processing audio data
CN106155828A (en) * 2016-07-13 2016-11-23 微鲸科技有限公司 For play-back application resource control method and equipment
CN107040815A (en) * 2017-05-09 2017-08-11 微鲸科技有限公司 Multimedia method and its device are played in a kind of many applications jointly
US20170353705A1 (en) * 2016-06-06 2017-12-07 Samsung Electronics Co., Ltd. Method for processing signals with operating state-dependent handling of multimedia attributes and electronic device thereof

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103596641A (en) * 2012-10-18 2014-02-19 华为终端有限公司 Audio frequency managing method and device
CN103714837A (en) * 2013-12-18 2014-04-09 福州瑞芯微电子有限公司 Electronic device and method for playing audio files
CN105959466A (en) * 2016-04-22 2016-09-21 青岛海信移动通信技术股份有限公司 Method and device for processing audio data
US20170353705A1 (en) * 2016-06-06 2017-12-07 Samsung Electronics Co., Ltd. Method for processing signals with operating state-dependent handling of multimedia attributes and electronic device thereof
CN106155828A (en) * 2016-07-13 2016-11-23 微鲸科技有限公司 For play-back application resource control method and equipment
CN107040815A (en) * 2017-05-09 2017-08-11 微鲸科技有限公司 Multimedia method and its device are played in a kind of many applications jointly

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109614252A (en) * 2018-12-10 2019-04-12 苏州思必驰信息科技有限公司 Audio playout schedule method and system for Intelligent story device
CN110225386A (en) * 2019-05-09 2019-09-10 青岛海信电器股份有限公司 A kind of display control method, display equipment
CN110225386B (en) * 2019-05-09 2021-09-14 海信视像科技股份有限公司 Display control method and display device
CN113849241A (en) * 2020-06-10 2021-12-28 Oppo(重庆)智能科技有限公司 Audio playing control method, intelligent watch and device with storage function
CN114201226A (en) * 2020-08-26 2022-03-18 北京小米移动软件有限公司 Application starting method and device, electronic equipment and storage medium
CN112615853A (en) * 2020-12-16 2021-04-06 瑞芯微电子股份有限公司 Android device audio data access method
CN116679900A (en) * 2022-12-23 2023-09-01 荣耀终端有限公司 Audio service processing method, firmware loading method and related devices
CN116679900B (en) * 2022-12-23 2024-04-09 荣耀终端有限公司 Audio service processing method, firmware loading method and related devices

Similar Documents

Publication Publication Date Title
CN108614722B (en) Application program preloading method and device, storage medium and terminal
CN108762843B (en) Application program preloading method and device, storage medium and intelligent terminal
US11467855B2 (en) Application preloading method and device, storage medium and terminal
CN108647055B (en) Application program preloading method and device, storage medium and terminal
CN108595231B (en) Application program preloading method and device, storage medium and intelligent terminal
CN108958830B (en) Application program starting method and device, storage medium and terminal
CN108681475B (en) Application program preloading method and device, storage medium and mobile terminal
CN108595230B (en) Application program preloading method and device, storage medium and terminal
CN108710513B (en) Application program starting method and device, storage medium and terminal
CN108845840A (en) Management method, device, storage medium and the intelligent terminal of application program sound
CN108920202B (en) Application preloading management method and device, storage medium and intelligent terminal
CN108762831B (en) Application program preloading method and device, storage medium and terminal
CN108776599B (en) Management method and device for preloaded application, storage medium and intelligent terminal
CN108804153B (en) Application program preloading method and device, storage medium and terminal
CN108595224B (en) Application program prompting method and device, storage medium and terminal
US20190370657A1 (en) Method and apparatus for updating application prediction model, storage medium, and terminal
CN108647056B (en) Application program preloading method and device, storage medium and terminal
CN108958828B (en) Application program preloading method and device, storage medium and terminal
CN108647057B (en) Screen direction setting method and device, storage medium and terminal
CN108762836B (en) Management method and device for preloaded application, storage medium and intelligent terminal
CN108710512B (en) Application program preloading method and device, storage medium and intelligent terminal
CN108762844B (en) Application program preloading method and device, storage medium and terminal
US11138956B2 (en) Method for controlling display of terminal, storage medium, and electronic device
WO2019228149A1 (en) Collection method and apparatus for prediction sample, and storage medium and smart terminal
CN108845838B (en) Application program preloading method and device, storage medium and terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20181120

RJ01 Rejection of invention patent application after publication