The phenomenon the place a music utility on the Android working system unexpectedly terminates shortly after being launched represents a major consumer expertise problem. For instance, a consumer makes an attempt to play a track, the appliance opens, and inside seconds, it shuts down with out enjoying any music or displaying an error message. This conduct disrupts the consumer’s meant exercise and signifies an issue with the appliance or the system it runs on.
Addressing the untimely termination of music gamers is essential for sustaining consumer satisfaction and confidence within the Android platform. Traditionally, such points have been traced to a wide range of components, together with inadequate system assets, software program bugs, conflicts with different functions, and incompatibility with the machine’s {hardware} or Android model. Resolving these issues is helpful for app builders aiming to enhance their merchandise and for machine producers making certain a steady and dependable consumer setting.
Subsequent sections will delve into the potential causes behind this irritating situation, exploring troubleshooting steps customers can take, inspecting debugging methods for builders, and contemplating preventative measures for making certain music utility stability on Android units.
1. Useful resource Rivalry
Useful resource rivalry, within the context of Android working techniques, refers back to the competitors amongst varied functions for restricted system assets, comparable to CPU processing time, reminiscence (RAM), and community bandwidth. When the Android system experiences excessive demand for these assets, notably reminiscence, it might forcibly terminate background processes to unencumber assets for foreground functions. A music participant utility, particularly if not optimized for minimal useful resource utilization, can turn into a first-rate candidate for termination in such situations. The direct consequence of that is the abrupt closure of the music participant, interrupting the consumer’s audio playback. For instance, a consumer concurrently operating a memory-intensive recreation, a video streaming service, and a music participant could discover the music participant persistently shutting down because of inadequate accessible RAM.
The significance of understanding useful resource rivalry lies within the sensible implications for utility improvement and consumer conduct. Builders should implement methods for environment friendly useful resource administration, together with reminiscence optimization, background activity limitation, and adaptive useful resource allocation. Customers, however, can mitigate the issue by closing pointless functions, monitoring useful resource utilization by system instruments, and adjusting application-specific settings associated to background exercise. The effectiveness of those measures relies on the severity of the useful resource rivalry and the design of the person functions concerned. Functions consuming extreme assets with out demonstrable profit could set off system-level interventions, additional exacerbating the instability.
In abstract, useful resource rivalry represents a crucial issue contributing to the difficulty of Android music gamers closing instantly. Addressing this drawback requires a twin method: builders optimizing functions for minimal useful resource footprint and customers managing their machine utilization to stop extreme pressure on system assets. Failure to mitigate useful resource rivalry can result in a degraded consumer expertise and decreased general system stability. This understanding is essential for making certain a seamless and uninterrupted audio playback expertise on Android units.
2. Software program Malfunction
Software program malfunctions inside an Android music participant utility symbolize a major explanation for its abrupt and sudden termination. These malfunctions embody a variety of points that compromise the appliance’s stability and performance, in the end resulting in its closure.
-
Coding Errors and Bugs
Coding errors, inherent within the software program improvement course of, can manifest as bugs inside the music participant utility. These bugs, starting from easy logical errors to extra advanced reminiscence leaks or null pointer exceptions, can set off a crash. For example, a poorly written perform that makes an attempt to entry a non-existent reminiscence location will lead to instant utility termination. Untested code paths or ignored edge instances usually harbor these errors, resulting in unpredictable conduct and eventual crashes. The implications embrace a degraded consumer expertise and potential information loss, particularly if the appliance doesn’t correctly save its state.
-
API Misuse and Integration Issues
Android functions depend on a large number of APIs (Utility Programming Interfaces) supplied by the Android working system. Incorrect utilization or improper integration of those APIs can result in sudden conduct and utility crashes. For instance, an try and entry a protected useful resource with out the mandatory permissions, or a failure to deal with asynchronous operations accurately, can set off a system-level exception, forcing the music participant to shut. Incompatibility between totally different variations of APIs or the appliance’s failure to adapt to platform updates are widespread sources of such issues. This manifests as unpredictable closures following working system updates.
-
Reminiscence Leaks and Useful resource Administration Points
Reminiscence leaks, the place the appliance fails to launch allotted reminiscence, can regularly eat accessible system assets. Over time, this results in a crucial depletion of reminiscence, forcing the working system to terminate the appliance to stop system-wide instability. Equally, inefficient useful resource administration, comparable to holding onto file handles or community connections longer than vital, can contribute to useful resource exhaustion and utility closure. The problem usually turns into evident throughout extended utilization, with the music participant exhibiting sluggish efficiency earlier than in the end crashing. The results may be extra pronounced on units with restricted RAM.
-
Exception Dealing with Deficiencies
Strong exception dealing with is essential for stopping utility crashes. If the music participant utility fails to anticipate and correctly deal with distinctive conditions, comparable to community errors, file corruption, or invalid consumer enter, it might encounter unrecoverable errors resulting in termination. An uncaught exception, as an illustration, will propagate up the decision stack till it reaches the system degree, triggering a crash report and utility closure. Insufficient error dealing with can render the appliance fragile and vulnerable to sudden closures even below regular working circumstances. Correctly applied try-catch blocks and error logging mechanisms are important for mitigating these points.
In abstract, software program malfunctions, whether or not stemming from coding errors, API misuse, useful resource mismanagement, or exception dealing with deficiencies, symbolize a major driver behind the abrupt closure of Android music participant functions. Addressing these underlying points requires diligent code overview, rigorous testing, adherence to finest practices in software program improvement, and a proactive method to figuring out and resolving potential vulnerabilities. Failure to take action can lead to a poor consumer expertise, unfavourable app rankings, and in the end, a lack of consumer belief.
3. Battery Optimization
Battery optimization, a function applied within the Android working system to increase machine battery life, can inadvertently trigger music participant functions to terminate prematurely. The system employs methods to restrict background exercise, doubtlessly affecting functions engaged in long-running processes like audio playback.
-
Aggressive App Standby
Android incorporates an “App Standby” function that locations apps in a restricted state if they aren’t actively used. This limits their capacity to run background duties and eat battery assets. If a music participant is relegated to standby, the system could interrupt its playback course of, resulting in sudden closure. For instance, a consumer listening to music whereas multitasking could discover the music participant shutting down if it has been within the background for an prolonged interval. The influence is a disruption in audio playback and a necessity for the consumer to restart the appliance.
-
Doze Mode Interference
Doze mode, designed to cut back battery consumption when the machine is idle, restricts background community entry and defers scheduled duties. Whereas efficient in conserving energy, it will possibly intervene with music gamers counting on community streams or background processes to keep up steady playback. Think about a state of affairs the place a consumer is listening to a web-based radio station; if the machine enters Doze mode, the community connection could also be severed, inflicting the music participant to terminate playback. The consequence is an interrupted listening expertise.
-
Background Course of Limitations
Android imposes strict limitations on background processes to preserve battery energy. These limitations prohibit the flexibility of functions to carry out duties within the background, together with audio playback. If a music participant’s background processes are deemed extreme or pointless, the system could terminate them, ensuing within the utility’s closure. An instance is a music participant trying to obtain album artwork or lyrics within the background; the system could prioritize battery conservation and terminate the obtain course of together with the appliance itself. The result’s interrupted service.
-
Exemptions and Whitelisting
To mitigate the influence of battery optimization on important functions, Android offers mechanisms for builders to request exemptions or for customers to whitelist functions. By whitelisting a music participant, customers can forestall the system from making use of aggressive battery-saving measures that would trigger it to shut prematurely. This includes navigating to the machine’s battery settings and excluding the appliance from optimizations. The influence is that, whereas battery life could also be barely decreased, the music playback expertise stays steady.
The interaction between battery optimization and music participant performance highlights a trade-off between energy conservation and steady utility operation. Whereas battery optimization is important for prolonging machine utilization, its aggressive implementations can result in undesirable penalties for functions requiring uninterrupted background exercise. Understanding the mechanics of battery optimization and using whitelisting choices are essential steps in stopping sudden music participant closures.
4. Permissions denied
The state of affairs the place an Android music participant utility terminates shortly after launching can usually be straight linked to denied permissions. Android’s permission mannequin requires functions to explicitly request entry to particular machine options and information, comparable to storage, microphone, or community connectivity. If a music participant lacks the mandatory permissions, notably storage permission to entry audio recordsdata, it might encounter a deadly error upon trying to load or play music. This results in instant utility closure. For example, if an utility requests storage entry, and the consumer denies this request, the appliance can be unable to enumerate and play audio recordsdata saved on the machine, triggering an error and subsequent termination. The absence of vital permissions successfully prevents the appliance from functioning as meant, leading to an abrupt shutdown.
The significance of understanding the permissions mannequin lies in its direct affect on utility performance and stability. Builders should implement strong error dealing with to gracefully handle conditions the place permissions are denied. This includes displaying informative messages to the consumer, guiding them to grant the mandatory permissions, or providing different performance that doesn’t require the restricted entry. Customers, in flip, should concentrate on the permissions they grant to functions and the potential penalties of denying important entry. An uninformed consumer would possibly inadvertently deny storage permission to a music participant, resulting in persistent utility closures and a unfavourable consumer expertise. Moreover, the denial of community permissions can forestall the appliance from streaming music or accessing on-line databases, leading to related termination conduct.
In abstract, denied permissions symbolize a crucial issue contributing to the difficulty of Android music gamers closing instantly. This drawback necessitates a collaborative method involving builders implementing applicable error dealing with and consumer schooling relating to permission administration. Understanding and addressing permission-related points are important for making certain a steady and purposeful music playback expertise on Android units, thereby stopping sudden utility closures and enhancing general consumer satisfaction.
5. Codec incompatibility
Codec incompatibility represents a major trigger for the sudden termination of Android music participant functions. Audio codecs are algorithms that encode and decode audio information, permitting music recordsdata to be saved effectively and performed again on varied units. When a music participant encounters a file encoded with a codec it doesn’t assist, the appliance could try and course of the information, leading to a crash or instant closure. For instance, a consumer trying to play an audio file encoded with a much less widespread codec, comparable to a proprietary lossless format, on a music participant designed primarily for MP3 or AAC recordsdata would possibly expertise the appliance closing abruptly. The basis trigger lies within the utility’s incapacity to accurately interpret and course of the audio information, resulting in a crucial error.
Addressing codec incompatibility requires a multifaceted method. Music participant builders should guarantee their functions assist a variety of widespread audio codecs and implement strong error dealing with for unsupported codecs. This will contain integrating libraries that deal with a wide range of codecs or offering customers with choices to put in further codec packs. Moreover, informing customers concerning the particular codecs supported by the appliance is essential. For example, an utility would possibly show an error message indicating {that a} particular file sort will not be supported, quite than merely closing with out clarification. Customers can then both convert the file to a suitable format or search out a music participant that helps the mandatory codec. Failure to handle codec incompatibility successfully leads to a poor consumer expertise, characterised by unpredictable utility conduct and the lack to play sure audio recordsdata.
In abstract, codec incompatibility is a key issue contributing to the abrupt termination of Android music participant functions. Resolving this situation includes a mix of complete codec assist inside the utility, efficient error dealing with, and clear communication with the consumer. By addressing these elements, builders can considerably enhance the steadiness and usefulness of their music gamers, making certain a seamless audio playback expertise throughout a various vary of audio file codecs. Understanding the position of codecs and their influence on utility stability is subsequently important for each builders and end-users.
6. Background Limits
Background limits, imposed by the Android working system to handle useful resource consumption, straight contribute to cases the place a music participant utility terminates unexpectedly. The Android system actively restricts the flexibility of functions to run indefinitely within the background, primarily to preserve battery life and forestall extreme useful resource utilization. When a music participant exceeds these pre-defined limits, the working system could forcibly terminate the appliance course of. This manifests because the consumer experiencing an abrupt cessation of music playback, usually with out warning. For instance, if a consumer switches to a unique utility and the music participant is relegated to the background, the system could terminate the participant if it deems the background exercise too resource-intensive. The period earlier than termination varies relying on components comparable to machine reminiscence, system configuration, and the presence of different operating functions. Understanding background limits is essential, as they’re a core factor of the Android system’s useful resource administration technique and considerably influence the conduct of functions designed for steady background operation.
The particular actions triggered by exceeding background limits embrace the cessation of audio playback, the elimination of the appliance course of from reminiscence, and the potential lack of playback state. This situation is exacerbated when the music participant depends on community connections for streaming audio, because the background limitations can interrupt the information stream and set off termination. Builders should implement methods to mitigate the consequences of background limits, comparable to using foreground companies with applicable notifications to sign ongoing background exercise, optimizing useful resource utilization to attenuate the appliance’s footprint, and gracefully dealing with interruptions by saving playback progress. A music participant that inadequately manages background exercise is liable to frequent and unpredictable terminations, negatively affecting the consumer expertise and doubtlessly resulting in uninstalls. Moreover, the introduction of battery-saving options by machine producers usually intensifies the influence of background limitations, making strong background administration much more crucial.
In conclusion, background limits symbolize a key constraint on the operation of Android music participant functions. Understanding the mechanisms by which these limits are enforced and implementing applicable countermeasures is important for builders to make sure a steady and dependable consumer expertise. By rigorously managing background exercise, leveraging foreground companies responsibly, and optimizing useful resource consumption, builders can decrease the danger of sudden utility terminations and keep steady audio playback even when the appliance is within the background. This understanding varieties an important facet of creating strong and user-friendly music participant functions for the Android platform.
7. Cache Corruption
Cache corruption, the unintended alteration or injury of knowledge saved in a music participant utility’s cache reminiscence, serves as a possible catalyst for the instant closure of such functions on Android units. This corruption can come up from varied sources, together with abrupt system shutdowns, software program bugs, or file system errors. When the appliance makes an attempt to entry or course of corrupted information from its cache, it might encounter sudden values or inconsistencies, resulting in a crucial error situation. For example, metadata associated to audio recordsdata, comparable to track titles, album artwork, or playback positions, is perhaps saved within the cache. If this metadata turns into corrupted, the appliance could crash when trying to show details about a selected track or resume playback from a saved place. Cache corruption undermines the appliance’s capacity to perform accurately and can lead to instant termination to stop additional system instability. The integrity of the cache reminiscence is subsequently a crucial element of the music participant’s general stability.
The sensible implications of cache corruption lengthen to each utility builders and end-users. Builders should implement mechanisms to detect and deal with cache corruption gracefully. This will contain frequently verifying the integrity of cached information, using error-correcting codes, or implementing fallback mechanisms that bypass the cache when errors are detected. For customers, clearing the appliance’s cache by the Android system settings usually serves as a troubleshooting step for resolving sudden conduct. This successfully resets the cache to a clear state, forcing the appliance to rebuild its cached information from scratch. It’s also essential to notice that the danger of cache corruption may be influenced by the standard of storage media and the steadiness of the working system. Units with defective storage or working techniques liable to instability are extra vulnerable to cache-related points. A broken storage drive or an incomplete app replace would possibly corrupt the cache.
In abstract, cache corruption represents a notable issue contributing to the issue of Android music participant functions closing instantly. Addressing this situation necessitates a proactive method by builders in implementing strong error dealing with and information validation mechanisms. For customers, understanding the position of the cache and understanding how you can clear it offers a beneficial troubleshooting instrument. The flexibility to mitigate the consequences of cache corruption is important for sustaining a steady and satisfying music playback expertise on Android units, in the end stopping sudden utility terminations and preserving consumer information integrity.
8. App updates
Utility updates, whereas meant to boost performance and enhance stability, can paradoxically induce the instant closure of Android music gamers. This phenomenon arises when an replace introduces unexpected software program bugs, incompatibilities with present machine configurations, or conflicts with different put in functions. For example, a current replace would possibly incorporate modifications to the appliance’s inside code or dependencies, leading to a reminiscence leak that triggers termination when the appliance makes an attempt to carry out a particular perform. Alternatively, the replace might not be absolutely suitable with the machine’s Android model or {hardware}, resulting in runtime errors and subsequent closure. The replace course of itself, if interrupted or incomplete, can even lead to a corrupted utility set up, making the music participant unusable. An actual-world instance is a music participant replace that introduces a brand new audio processing library however fails to correctly deal with sure audio file codecs, inflicting the appliance to crash when trying to play these recordsdata. Consequently, the consumer experiences an abrupt and sudden termination of the music participant, straight attributable to the supposedly helpful replace. Such occurrences underscore the crucial significance of rigorous testing and high quality assurance procedures in the course of the utility replace improvement cycle.
Moreover, the frequency of updates can even contribute to this situation. Functions that launch updates too often, with out enough testing, enhance the probability of introducing new bugs or incompatibilities. The fast iteration cycle could prioritize new options over stability, resulting in a compromised consumer expertise. It’s not unusual for customers to report stability points instantly following an utility replace, solely to have these points resolved in subsequent patches. This cycle of instability and correction highlights the inherent challenges of sustaining a posh software program utility throughout a various vary of Android units and configurations. Moreover, the replace mechanism itself may be problematic. An incomplete or corrupted obtain of the replace bundle can result in an improperly put in utility, leading to instant closure or different unpredictable conduct. The system needs to be engineered to detect such conditions and carry out integrity checks.
In conclusion, utility updates symbolize a double-edged sword: whereas they maintain the promise of enhancements and new options, additionally they carry the danger of introducing instability and inflicting the instant closure of Android music gamers. Rigorous testing, thorough high quality assurance, and cautious consideration of machine compatibility are important to mitigating this threat. Moreover, builders ought to prioritize stability and tackle reported points promptly to keep up consumer belief and guarantee a constructive consumer expertise. The replace course of itself should be strong and dependable to stop corrupted installations, contributing to the general stability of the music participant utility.
9. System instability
System instability, encompassing a variety of underlying points affecting the Android working system’s core performance, presents a major contributing issue to the abrupt termination of music participant functions. Instability undermines the reliability of system companies and assets, impacting utility conduct and resulting in sudden closures.
-
Kernel Panics and Crashes
Kernel panics, crucial errors inside the working system’s kernel, can halt system operations abruptly. These panics could stem from {hardware} faults, driver incompatibilities, or software program defects inside the kernel code. When a kernel panic happens, the whole system, together with operating functions such because the music participant, is pressured to close down with out warning. An instance features a defective reminiscence module triggering a kernel panic throughout audio playback, leading to instant closure of the music participant. This disruption straight hinders the music participant’s capacity to perform.
-
Useful resource Administration Deficiencies
Inefficient useful resource administration, together with reminiscence leaks or CPU overutilization, can destabilize the system. When system assets turn into scarce, the Android working system could aggressively terminate background processes to keep up responsiveness. If a music participant is operating within the background or consuming a disproportionate share of assets, it turns into a first-rate goal for termination. An instance can be a runaway course of consuming reminiscence, inflicting the system to kill the music participant to get well reminiscence. This illustrates how unstable useful resource allocation results in utility failure.
-
Driver Incompatibilities and Errors
Driver incompatibilities, notably these associated to audio {hardware} or codecs, can set off system-level errors. When a music participant makes an attempt to work together with incompatible or defective drivers, it might encounter exceptions that propagate to the working system, inflicting instability. For instance, an outdated or corrupt audio driver would possibly result in errors throughout audio decoding, inflicting the music participant and doubtlessly the whole system to crash. Driver-related points straight have an effect on the music participant’s capacity to perform accurately.
-
Working System Corruption
Corruption inside the working system’s recordsdata or configurations can result in unpredictable conduct and system instability. This corruption can come up from incomplete updates, malicious software program, or file system errors. If the working system’s core parts are compromised, functions counting on these parts, such because the music participant, could encounter errors and terminate unexpectedly. For example, a corrupted system library required for audio playback would possibly trigger the music participant to crash upon startup. The integrity of the working system is paramount for utility stability.
In abstract, system instability, stemming from kernel panics, useful resource administration deficiencies, driver incompatibilities, or working system corruption, straight contributes to the frequent and sudden closure of Android music participant functions. Addressing system-level points is subsequently important for making certain a steady and dependable music playback expertise, underscoring the interdependence between utility conduct and the underlying working system’s integrity.
Continuously Requested Questions
This part addresses widespread queries and issues associated to the difficulty of music participant functions closing unexpectedly on Android units, offering detailed and technical insights.
Query 1: What are probably the most prevalent causes for a music participant utility to terminate with out warning on Android?
The instant closure of an Android music participant usually stems from useful resource rivalry, software program malfunction, aggressive battery optimization, permission denials, codec incompatibilities, or limitations imposed on background processes. System-level points comparable to kernel panics or driver incompatibilities can even contribute.
Query 2: How does Android’s battery optimization influence music participant stability?
Android’s battery optimization options, together with Doze mode and App Standby, can prohibit background exercise and community entry, doubtlessly interrupting audio playback and inflicting the music participant to terminate. Aggressive battery-saving measures could prioritize energy conservation over uninterrupted utility operation.
Query 3: What position do utility permissions play within the untimely termination of music gamers?
Denied permissions, notably storage permission, forestall the music participant from accessing audio recordsdata. If an utility lacks the mandatory permissions, it might encounter errors when trying to load or play music, resulting in termination.
Query 4: How can codec incompatibility result in utility closure?
If a music participant encounters an audio file encoded with a codec it doesn’t assist, the appliance could try and course of the information, leading to a crash or instant closure. The appliance’s incapacity to accurately interpret the audio information triggers the error.
Query 5: What measures can builders take to stop background limitations from inflicting utility termination?
Builders can make the most of foreground companies with applicable notifications, optimize useful resource utilization to attenuate the appliance’s footprint, and implement swish dealing with of interruptions by saving playback progress. These methods mitigate the consequences of Android’s background course of limitations.
Query 6: How does cache corruption contribute to this drawback, and what steps may be taken to deal with it?
Cache corruption, the unintended alteration or injury of knowledge saved within the utility’s cache reminiscence, can result in sudden values and inconsistencies, leading to utility termination. Clearing the appliance’s cache by the Android system settings can usually resolve this situation.
Understanding the interaction of things comparable to useful resource administration, permissions, codecs, background limitations, and system stability is important for troubleshooting and stopping sudden music participant closures on Android units.
Subsequent, the article will transition to troubleshooting steps to resolve the issue, and debugging methods for builders.
Troubleshooting Surprising Music Participant Closures on Android
The next steerage provides sensible steps to mitigate the difficulty of music participant functions terminating unexpectedly on Android units. These suggestions are meant for each end-users and technical assist personnel.
Tip 1: Confirm Utility Permissions. Entry the Android system settings, find the music participant utility, and make sure that it possesses the mandatory permissions, notably storage entry for native audio recordsdata and community entry for streaming companies. Insufficient permissions impede the appliance’s capacity to perform accurately.
Tip 2: Clear Utility Cache and Knowledge. Navigate to the appliance settings inside Android and clear each the cache and information for the music participant. This removes non permanent recordsdata and settings that will have turn into corrupted, doubtlessly resolving stability points. Word: Clearing information will reset the appliance to its default state.
Tip 3: Disable Battery Optimization. Look at battery optimization settings for the music participant utility. Exclude the appliance from battery-saving measures to stop the system from aggressively limiting background exercise, which may interrupt audio playback.
Tip 4: Shut Pointless Background Functions. Cut back useful resource rivalry by closing functions that aren’t actively in use. Extreme background exercise can pressure system assets, resulting in the termination of lower-priority functions like music gamers.
Tip 5: Guarantee Enough System Sources. Affirm that the Android machine possesses adequate accessible RAM and cupboard space. Inadequate assets can contribute to system instability and utility closures. Think about releasing up cupboard space and restarting the machine.
Tip 6: Examine for Utility Updates. Confirm that the music participant utility is operating the newest accessible model. Utility updates usually embrace bug fixes and stability enhancements that may tackle identified points. Guarantee auto-update is enabled or manually test for updates by way of the Google Play Retailer.
Tip 7: Affirm Codec Compatibility. Confirm that the music participant helps the audio file codecs getting used. Incompatibility with sure codecs could cause playback errors and utility termination. Convert incompatible recordsdata to broadly supported codecs comparable to MP3 or AAC.
Implementing these measures can improve the steadiness of music participant functions on Android units. Systematic troubleshooting and useful resource administration contribute to a extra dependable audio playback expertise.
The following part will discover debugging methods to resolve the issue.
Addressing Untimely Termination of Android Music Gamers
This text has comprehensively explored the multifaceted situation of “android music participant that closes instantly.” Elements recognized vary from useful resource rivalry and software program malfunctions to battery optimizations, permission restrictions, codec incompatibilities, background limitations, cache corruption, problematic app updates, and system instability. A scientific understanding of those potential causes is crucial for each customers and builders searching for to resolve this disruptive situation.
Continued diligence in software program improvement, rigorous testing protocols, and knowledgeable consumer consciousness stay important in combating this drawback. Addressing the complexities detailed inside this evaluation serves as a basis for making certain a persistently steady and passable audio playback expertise on the Android platform. Prioritizing utility stability and consumer expertise is paramount to sustaining the long-term viability and constructive notion of Android-based music functions.
