CN113535113A - Audio sharing method, system and storage medium - Google Patents
Audio sharing method, system and storage medium Download PDFInfo
- Publication number
- CN113535113A CN113535113A CN202110815811.7A CN202110815811A CN113535113A CN 113535113 A CN113535113 A CN 113535113A CN 202110815811 A CN202110815811 A CN 202110815811A CN 113535113 A CN113535113 A CN 113535113A
- Authority
- CN
- China
- Prior art keywords
- audio
- applications
- application
- capture
- common
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 28
- 230000004048 modification Effects 0.000 claims description 11
- 238000012986 modification Methods 0.000 claims description 11
- 238000007781 pre-processing Methods 0.000 claims description 10
- 238000012545 processing Methods 0.000 claims description 9
- 230000008569 process Effects 0.000 claims description 8
- 230000008859 change Effects 0.000 claims description 7
- 230000035945 sensitivity Effects 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 230000004888 barrier function Effects 0.000 claims description 4
- 239000003999 initiator Substances 0.000 claims description 3
- 230000030279 gene silencing Effects 0.000 claims description 2
- 230000005236 sound signal Effects 0.000 abstract description 7
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000005457 optimization Methods 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 21
- 230000006872 improvement Effects 0.000 description 8
- 230000000694 effects Effects 0.000 description 4
- 230000006399 behavior Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000005070 sampling Methods 0.000 description 2
- 238000012952 Resampling Methods 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000005465 channeling Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000011800 void material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input 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/16—Sound input; Sound output
- G06F3/162—Interface to dedicated audio devices, e.g. audio drivers, interface to CODECs
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Multimedia (AREA)
- Health & Medical Sciences (AREA)
- Audiology, Speech & Language Pathology (AREA)
- General Health & Medical Sciences (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephone Function (AREA)
Abstract
The invention provides an audio sharing method, an audio sharing system and a storage medium, wherein when a plurality of applications capture audio in an Android system, a priority strategy is adopted to switch input audio streams among running applications, the applications comprise common applications and privileged applications, and the priority strategy is as follows: privileged applications have higher priority than normal applications; applications with visible foreground interfaces have higher priority than background applications; applications that capture audio from privacy-sensitive sources have a higher priority than applications that capture audio from non-privacy-sensitive sources; two common applications cannot capture audio simultaneously; if two background applications of the same priority are both capturing audio, the later applications are prioritized higher. The invention has the beneficial effects that: the user can open a plurality of different software applications simultaneously in use, and audio signal input signal output simultaneously realizes a tractor serves several purposes, effectively promotes the product practicality, easy operation, a tractor serves several purposes, resource optimization and hommization.
Description
Technical Field
The present invention relates to the field of audio data processing technologies, and in particular, to an audio sharing method, system, and storage medium.
Background
One digital device can only open one audio device signal input or audio signal output, and if different devices are used simultaneously, a user cannot use audio on the same device simultaneously.
Disclosure of Invention
The invention provides an audio sharing method, in an Android system, when a plurality of applications capture audio, a priority policy is adopted to switch input audio streams among running applications, the applications comprise common applications and privileged applications, and the priority policy for using and sharing audio input is as follows:
privileged applications have higher priority than normal applications;
applications with visible foreground interfaces have higher priority than background applications;
applications that capture audio from privacy-sensitive sources have a higher priority than applications that capture audio from non-privacy-sensitive sources;
two common applications cannot capture audio simultaneously;
if two background applications of the same priority are both capturing audio, the later applications are prioritized higher.
As a further improvement of the present invention, when the Google assistant and the common application capture audio, the Google assistant belongs to privileged applications, and Android shares input audio according to the following rules:
the Google assistant receives audio unless another application using a privacy sensitive audio source is already capturing the audio;
unless the Google assistant has a visible interface component on top of the screen, the application will receive the audio.
As a further improvement of the present invention, when the barrier-free service and the common application capture audio, the barrier-free service belongs to privileged application, and the Android shares input audio according to the following rules:
if the barrier free service interface is at the top, both barrier free service and normal applications will receive audio input;
if the barrier-free service is not on top, only one application receives audio, and the other application is subjected to silence.
As a further improvement of the present invention, when two common applications capture audio, Android shares input audio according to the following rules:
if neither of the two common applications has privacy sensitivity, receiving audio by the common application with the interface at the top; if neither of the two common applications has an interface, the later initiator receives audio;
if one of the common applications has privacy sensitivity, receiving audio by the common application, and subjecting the other common application to a silencing process;
if both of the normal applications have privacy sensitivity, the audio is received by the normal application that started capturing at the latest, and the other normal application is subjected to the mute processing.
As a further improvement of the present invention, when capturing audio for voice calls and common applications, Android shares input audio according to the following rules:
the voice call always receives audio;
if the service belongs to the barrier-free service, the application captures audio;
if the application is a privileged application with CAPTURE _ AUDIO _ OUTPUT authority, the application CAPTUREs a voice call;
if an UPLINK and/or DOWNLINK of a voice call is to be captured, the application must specify the audio source mediarecorder.
As a further improvement of the present invention, when multiple applications capture audio simultaneously, only one or two applications are active and the other applications are silent, and when the active application changes, the audio framework reconfigures the audio path according to the following rules:
the audio input device of each active application will change;
the preprocessing associated with the highest priority active application is enabled and the other preprocessing is ignored.
As a further improvement of the present invention, when an application with higher priority is in an active state, the active application is quiesced, and an audiomanager.
As a further improvement of the invention, the modification comprises that the capture is subjected to silence processing or silence release processing, equipment modification, preprocessing modification, audio stream attribute modification.
The invention also provides an audio sharing system, comprising: a memory, a processor and a computer program stored on the memory, the computer program being configured to implement the steps of the audio sharing method of the invention when invoked by the processor.
The invention also provides a computer-readable storage medium having stored thereon a computer program configured to, when invoked by a processor, perform the steps of the audio sharing method of the invention.
The invention has the beneficial effects that: the user can open a plurality of different software applications simultaneously in use, and audio signal input signal output simultaneously realizes a tractor serves several purposes, effectively promotes the product practicality, easy operation, a tractor serves several purposes, resource optimization and hommization.
Drawings
FIG. 1 is a schematic block diagram of the system of the present invention.
Detailed Description
The invention discloses an audio sharing method, which is used for sharing multiple platforms of audio of the same machine and realizing audio sharing of multiple applications APP.
The invention introduces the audio sharing device, a user can open a plurality of different software applications simultaneously in use, and simultaneously the audio signal input signal is output, thus realizing multiple purposes of one machine and effectively improving the practicability of products.
The audio input is typically from a built-in microphone, an external microphone, or an audio interface connected to the device. The audio input may also come from a telephone conversation. Sometimes, two or more applications may all want to "capture" the same audio input. These applications may be performing different tasks. For example, some applications receiving audio may be "recording" like a simple voice recorder, while other applications may be "listening" like a Google assistant or barrier-free service responding to voice commands.
In either case, these applications desire to receive audio input. In the present invention, the term "capture" is used in the present invention regardless of whether the application is recording or listening.
Transmitting audio signals from the same source to all applications can be problematic if two or more applications wish to capture audio simultaneously. The present invention introduces how the Android system shares audio input among multiple applications that capture audio.
Early versions of Android: in the early Android, the input audio stream could only be captured by one application at a time. If an application already records or listens to audio, your application may create an AudioRecord object, but the system will return an error when you call AudioRecord.
An exception to this rule is that privileged applications (e.g., Google assistants or barrier-free services) possess android. In this case, another application may start recording. When this occurs, the privileged application terminates and the new application captures the input.
An alteration is also added to the Android 9: only the application running in the foreground (or foreground service) can capture the audio input. When an application without a foreground service or foreground interface component begins capturing, the application will continue to run, but will be subject to quiesce processing, even though it is the only application that captures audio at the time.
The technical improvement of the invention is as follows: the previous behavior is "first come first get". After an application starts capturing audio, all other applications cannot access the audio input until the capturing application stops. The invention adopts a priority task scheduling scheme, and can switch input audio streams between running applications. In most cases, if the new application acquires audio input, the previous capture application will continue to run, but will be subjected to a muting process. In some cases, the system may continue to deliver audio to both applications. This sharing scheme will be described below.
This approach is similar to the way audio focus handles multiple applications contending for audio output usage. However, audio focus acquisition and focus release are governed by programming requests; the input switching scheme described herein is based on a priority policy that is automatically applied when a new application begins capturing audio.
To capture audio, Android distinguishes two types of applications:
user installed "normal" applications.
A pre-installed "privileged" application on a device. Including Google assistants and all barrier-free services.
Furthermore, if an application uses a "privacy-sensitive" audio source (CAMCORDER or VOICE _ COMMUNICATION), it is treated differently.
The priority rules for using and sharing audio input are as follows:
1. privileged applications have a higher priority than normal applications.
2. Applications with visible foreground interfaces have a higher priority than background applications.
3. Applications that capture audio from privacy-sensitive sources have a higher priority than applications that capture audio from non-privacy-sensitive sources.
4. Two common applications can never capture audio at the same time.
5. In some cases, a privileged application may share audio input with other applications.
6. If two background applications of the same priority are both capturing audio, the priority starting later is higher.
The audio sharing scheme comprises the following steps: when both applications attempt to capture audio, they may both receive the input signal, or one of them may be subjected to silence processing.
The four main schemes are as follows:
google assistant + general application.
2. Barrier-free service + general application.
3. Two general applications.
4. Voice call + normal application.
Google assistant + general application: the Google assistant belongs to a privileged application because it is pre-installed on the device and possesses the role of rolemanager. roll _ ASSISTANT. Any other pre-installed application that owns this role will be similarly processed. Android shares input audio according to the following rules:
1. the Google assistant may receive audio (whether in the foreground or the background) unless another application that uses a privacy sensitive audio source is already capturing the audio.
2. Unless the Google assistant has a visible interface component on top of the screen, the application will receive the audio.
Note that both applications receive audio only when the Google assistant is in the background and the other application is not capturing from a privacy sensitive audio source.
Barrier-free service + general application: an accessitivyservice requires a strict declaration. Android shares input audio according to the following rules:
1. if the interface of the service is at the top, both the service and the application will receive audio input. This behavior provides the ability to control voice calls or video capture using voice commands.
2. If the service is not at the top, this case is handled in the same way as the case of the two general applications described below.
Two general applications: when two applications are capturing at the same time, only one application receives audio and the other application is subjected to silence processing.
Android shares input audio according to the following rules:
1. if neither application has privacy sensitivity, audio is received by the application with the interface at the top. If neither application has an interface, the initiator receives audio later.
2. If one of the applications is privacy sensitive, the audio is received by it, and the other application is muted, even if the latter is at the top by the interface or starts capturing later.
3. If both applications are privacy sensitive, the audio is received by the application that started capturing at the latest, and the other application is subjected to the muting process.
Voice call + general application: getmode () returns the audio MODE as MODE _ IN _ CALL or MODE _ IN _ COMMUNICATION, and the voice CALL is active. Android shares input audio according to the following rules:
1. the call always receives audio.
2. If it is a barrier-free service, the application may capture audio.
3. If it is a privileged (pre-installed) application that has the capability _ AUDIO _ OUTPUT right, the application may CAPTURE the voice call.
If the UPLINK (TX), DOWNLINK (RX), or both, of a voice call are to be captured, the application must specify the audio sources mediaregister, audio, voice _ UPLINK, or mediaregister, audio, voice _ DOWNLINK, and/or device audiodeviceinfo, type _ telephy.
Configuration change:
when multiple applications capture audio simultaneously, only one or two applications are in an "active" state (receiving audio) and the other applications are in a mute state (receiving mute). When the active application changes, the audio framework may reconfigure the audio path according to the following rules:
1. the audio input device for each active application may be changed (e.g., from a built-in microphone to a connected bluetooth headset).
2. The preprocessing associated with the highest priority active application is enabled. Other pre-processing will be ignored.
Active applications may be quiesced when higher priority applications are active, so you can register an audiomanager. audiorecordingcallback on the AudioRecord or MediaRecorder object to be notified when a configuration change occurs. Possible modifications are as follows:
1. acquisition is muted or unmuted
2. Device modification
3. Preprocessing changes
4. Audio stream attribute modification (sampling rate, channel mask, sampling format)
You must call audiorecord. register audiorecord calling () before starting capture. The callback is only executed when the application is receiving audio and a change occurs.
The onRecordingConfigChanged () method returns an AudioRecordingConfiguration containing the current audio capture state. The following methods were used to understand the changes:
isClientSilenced()
true is returned if the audio returned to the client is currently subject to silent processing due to the capture policy.
getAudioDevice()
Returning to the active audio device.
getEffects()
And returning to the activity preprocessing effect. Note that if the client is not the highest priority active application, the active effect may be different from the effect returned by getClientEffects ().
getFormat()
The audio stream attributes are returned. Note that the actual audio data received by the client always follows the required format returned by getClientFormat (). The framework automatically performs the necessary resampling, channeling, and format conversion, i.e., from the format used on the hardware interface to the client-specified format.
AudioRecord.getActiveRecordingConfiguration()
By calling audiomanager, getactiverecordingconfigurations (), general paths of all active recordings on the device can be obtained, so that a plurality of audio signals are realized, a plurality of APPs can share the same audio signal source, and audio sharing is realized.
Analyzing a code flow: we know by the api that the application needs to register audiomanager. audiorecordingcallback, notified when a configuration change occurs, so we need to analyze this function.
This is an abstract class, implemented by the application itself, so it needs to find out who called onRecordingConfigChanged, and the tracking code finds out that it received MSSG _ RECORDING _ CONFIG _ CHANGE message, then it finds out where the message was sent, and then finds out the following code:
from the above code we find that we need to find where to call the dispatchRecodingConfigChange function, then go to the dispatchCallbacks function of RecodingActityMonitor. java (no code is pasted next to each other, only the key is pasted), then to the onRecodingConfigurtConfigurationChanged function, then to the recordingCallbackFromNative function of AudioSystem. java, here the setRecordingCallback function of AudioSystem. cpp comes from jni calls (the jni calls are simpler, no more analysis is done).
The calling process of the java layer is completed, the following key points are used for analyzing native calling, and the main realization is also realized here
First, see AudioSystem:setRecordConfigCallback
/*static*/void AudioSystem::setRecordConfigCallback(record_config_callback cb)
{
Mutex::Autolock_l(gLock)；
gRecordConfigCallback＝cb；
}
This results in a callback of callback, associated with gRecordConfigCallback, finding AudioSerystem:: AudioPolicyServiceClient:: onRecordConsortionRegistrationUpdate function through gRecordConfigCallback, then finding this function called by AudioPolicyService:: Notification Client:: onRecordingConfigurationUpdate function, proceeding to AudioPolicyService:: DoOnRecordConfigurationUpdate, then proceeding to reverse lookup, the tracking code determines that AudioPolicyServiceUpdate:: RecordRecordedConfiguringConfigurationUpdate function is followed by feedback to track AudioPolicyServiceService:: AudioTractyServiceReservice:: RecordedModityServiceReservice function, and then proceeding to the feedback function, if AudioPolicyServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceUpdate function is found by FItPolityServiceReservice:: feedback:: AudioConfigurationServiceReservice function, and then proceeding to feedback function, if AudioTracordPolityServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceUpdate function is found is to feedback is function, and if AudioTracedPolityServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceUpdate function is, and to feedback is function is to feedback is function is, if feedback is to feedback is, and to feedback is found to feedback, and to feedback function, if AucordingPolitsAudioTracordPolitsAudioTracedPolityServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceServiceService.
The foregoing is a more detailed description of the invention in connection with specific preferred embodiments and it is not intended that the invention be limited to these specific details. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (10)
1. An audio sharing method is characterized in that in an Android system, when a plurality of applications capture audio, a priority policy is adopted to switch input audio streams among running applications, the applications comprise common applications and privileged applications, and the priority policy for using and sharing audio input is as follows:
privileged applications have higher priority than normal applications;
applications with visible foreground interfaces have higher priority than background applications;
applications that capture audio from privacy-sensitive sources have a higher priority than applications that capture audio from non-privacy-sensitive sources;
two common applications cannot capture audio simultaneously;
if two background applications of the same priority are both capturing audio, the later applications are prioritized higher.
2. The audio sharing method of claim 1, wherein when the Google assistant and the general application capture audio, the Google assistant belongs to a privileged application, and the Android shares the input audio according to the following rules:
the Google assistant receives audio unless another application using a privacy sensitive audio source is already capturing the audio;
unless the Google assistant has a visible interface component on top of the screen, the application will receive the audio.
3. The audio sharing method according to claim 1, wherein the barrier-free service and the common application capture audio, the barrier-free service belongs to privileged applications, and the Android shares input audio according to the following rules:
if the barrier free service interface is at the top, both barrier free service and normal applications will receive audio input;
if the barrier-free service is not on top, only one application receives audio, and the other application is subjected to silence.
4. The audio sharing method according to claim 1, wherein when two common applications capture audio, Android shares input audio according to the following rules:
if neither of the two common applications has privacy sensitivity, receiving audio by the common application with the interface at the top; if neither of the two common applications has an interface, the later initiator receives audio;
if one of the common applications has privacy sensitivity, receiving audio by the common application, and subjecting the other common application to a silencing process;
if both of the normal applications have privacy sensitivity, the audio is received by the normal application that started capturing at the latest, and the other normal application is subjected to the mute processing.
5. The audio sharing method according to claim 1, wherein when the voice call and the common application capture audio, Android shares the input audio according to the following rules:
the voice call always receives audio;
if the service belongs to the barrier-free service, the application captures audio;
if the application is a privileged application with CAPTURE _ AUDIO _ OUTPUT authority, the application CAPTUREs a voice call;
if an UPLINK and/or DOWNLINK of a voice call is to be captured, the application must specify the audio source mediarecorder.
6. The audio sharing method of any one of claims 1 to 5, wherein when multiple applications capture audio simultaneously, only one or two applications are active, and the other applications are silent, and when the active application changes, the audio framework reconfigures the audio path according to the following rules:
the audio input device of each active application will change;
the preprocessing associated with the highest priority active application is enabled and the other preprocessing is ignored.
7. The audio sharing method of claim 6, wherein when the higher priority application is in an active state, the active application is subjected to a mute process, and an audiomanager.
8. The audio sharing method of claim 7, wherein the modification comprises a capture subject to a mute process or an un-mute process, a device modification, a pre-processing modification, an audio stream property modification.
9. An audio sharing system, comprising: memory, a processor and a computer program stored on the memory, the computer program being configured to carry out the steps of the audio sharing method of any of claims 1-8 when invoked by the processor.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program configured to, when invoked by a processor, implement the steps of the audio sharing method of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110815811.7A CN113535113A (en) | 2021-07-19 | 2021-07-19 | Audio sharing method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110815811.7A CN113535113A (en) | 2021-07-19 | 2021-07-19 | Audio sharing method, system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113535113A true CN113535113A (en) | 2021-10-22 |
Family
ID=78128787
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110815811.7A Pending CN113535113A (en) | 2021-07-19 | 2021-07-19 | Audio sharing method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113535113A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103617803A (en) * | 2013-11-08 | 2014-03-05 | 中标软件有限公司 | Multi-sound-source automatic switching method and system on vehicle-mounted system |
| US20160342384A1 (en) * | 2012-09-28 | 2016-11-24 | Pantech Co., Ltd. | Mobile terminal and method for controlling sound output |
| US10147426B1 (en) * | 2017-08-01 | 2018-12-04 | Lenovo (Singapore) Pte. Ltd. | Method and device to select an audio output circuit based on priority attributes |
| CN109032559A (en) * | 2018-07-25 | 2018-12-18 | 南京创维信息技术研究院有限公司 | A kind of configuration method and system of the same sound pick-up outfit of more Application shares |
| CN112805988A (en) * | 2018-11-16 | 2021-05-14 | 深圳市欢太科技有限公司 | Call control method and device, computer readable storage medium and electronic equipment |
-
2021
- 2021-07-19 CN CN202110815811.7A patent/CN113535113A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160342384A1 (en) * | 2012-09-28 | 2016-11-24 | Pantech Co., Ltd. | Mobile terminal and method for controlling sound output |
| CN103617803A (en) * | 2013-11-08 | 2014-03-05 | 中标软件有限公司 | Multi-sound-source automatic switching method and system on vehicle-mounted system |
| US10147426B1 (en) * | 2017-08-01 | 2018-12-04 | Lenovo (Singapore) Pte. Ltd. | Method and device to select an audio output circuit based on priority attributes |
| CN109032559A (en) * | 2018-07-25 | 2018-12-18 | 南京创维信息技术研究院有限公司 | A kind of configuration method and system of the same sound pick-up outfit of more Application shares |
| CN112805988A (en) * | 2018-11-16 | 2021-05-14 | 深圳市欢太科技有限公司 | Call control method and device, computer readable storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20060168114A1 (en) | Audio processing system | |
| US10949162B2 (en) | Method for multi-channel recording based on android system and audio system | |
| US11604674B2 (en) | Systems and methods for detecting and filtering function calls within processes for malware behavior | |
| CN102508702B (en) | Method for processing common service logic by performing interception based on AOP (aspect-oriented programming) technology | |
| US20050021876A1 (en) | Terminal device | |
| US20090109961A1 (en) | Multiple simultaneous call management using voice over internet protocol | |
| JP7020630B2 (en) | Methods and equipment for managing hardware resource access in electronic devices | |
| CN110933075B (en) | Service calling method and device, electronic equipment and storage medium | |
| WO2013189263A1 (en) | Method and device for monitoring api function scheduling in mobile terminal | |
| US9432954B2 (en) | Determination of device body location | |
| CN112331202B (en) | Voice screen projection method and device, electronic equipment and computer readable storage medium | |
| CN112333282B (en) | Service providing method and device based on hybrid cloud, medium and electronic equipment | |
| TWI400650B (en) | Audio stream notification and processing | |
| CN113535113A (en) | Audio sharing method, system and storage medium | |
| CN112395242A (en) | Multi-chip control method, device, electronic equipment and computer readable storage medium | |
| WO2023130938A1 (en) | Method and apparatus for transmitting call audio data | |
| CN113765939B (en) | Calling method, device, equipment and storage medium | |
| CN106790006B (en) | Device management method and system | |
| CN115242972A (en) | Method and device for calling camera by application, electronic equipment and storage medium | |
| CN115022770A (en) | Audio playing control method, terminal device and computer readable storage medium | |
| CN114448553B (en) | Anti-eavesdropping method, device, equipment and storage medium | |
| CN109213467B (en) | Method for acquiring sound of audio equipment, storage medium, electronic equipment and system | |
| US20220365808A1 (en) | Method and system for controlling an application feature based on system metrics | |
| KR100593843B1 (en) | An application program management system for a mobile telecommunication terminal | |
| CN116662024B (en) | Inter-process communication monitoring method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |