The utilization of a virtualized Android surroundings on Chrome OS {hardware} permits customers to execute Android purposes inside the Chrome OS ecosystem. This performance offers entry to a variety of cell software program instantly on Chromebook units. An instance of it is a person working a resource-intensive sport from the Google Play Retailer on their Chromebook, leveraging the system’s processing energy with out instantly putting in the Android working system.
This functionality enhances the flexibility of Chromebooks, extending their utility past internet looking and cloud-based purposes. It offers entry to instructional apps, productiveness instruments, and leisure choices not natively obtainable on Chrome OS. Traditionally, working Android purposes on non-Android units required advanced workarounds or devoted software program. This integration streamlines the method, providing a extra seamless person expertise.
The following sections will delve into the technical elements of implementation, efficiency issues, and potential use circumstances associated to working Android purposes on this method on Chrome OS units. These subjects will present a extra thorough understanding of the capabilities and limitations inherent on this performance.
1. Compatibility Layer
The compatibility layer varieties the foundational bridge enabling Android purposes to operate inside the Chrome OS surroundings. Its effectiveness instantly determines the vary and efficiency of Android software program able to working on a Chromebook. This layer handles the required translation and adaptation between the Android utility’s necessities and the underlying Chrome OS system.
-
System Name Translation
Android purposes depend on system calls particular to the Linux kernel inside Android. The compatibility layer interprets these calls into equal calls that Chrome OS can perceive and execute. With out correct translation, purposes could crash or exhibit sudden habits. For instance, an utility requesting entry to a selected {hardware} element by way of an Android system name should have that request accurately translated to a corresponding operation in Chrome OS.
-
{Hardware} Abstraction
Android and Chrome OS may make the most of completely different drivers or {hardware} interfaces for a similar bodily system. The compatibility layer offers an abstraction that permits Android purposes to work together with {hardware} (such because the digicam, microphone, or GPS) with no need to pay attention to the particular Chrome OS drivers. This abstraction ensures that purposes developed for a variety of Android units can nonetheless operate accurately on Chromebooks, no matter {hardware} variations.
-
Runtime Atmosphere Emulation
The compatibility layer typically consists of emulation of the Android runtime surroundings, together with Dalvik or ART (Android Runtime). This emulation permits the Chromebook to execute Android bytecode. Appropriate emulation is essential for utility efficiency and stability. For example, failure to precisely emulate the Android Runtime’s reminiscence administration can result in reminiscence leaks or utility crashes.
-
Library and Framework Adaptation
Android purposes rely upon quite a lot of libraries and frameworks supplied by the Android working system. The compatibility layer both offers suitable variations of those libraries or interprets calls to the Android frameworks into equal operations inside Chrome OS. This ensures that purposes using options reminiscent of location companies, push notifications, or Google Play Companies operate accurately. Incorrect adaptation may end up in options failing to work or producing inaccurate outcomes.
The efficacy of this compatibility layer is central to person expertise on a Chromebook. A well-implemented layer facilitates a easy integration, enabling a big selection of purposes to run seamlessly. Conversely, a poorly carried out layer limits the variety of useful purposes and degrades the general efficiency of people who do operate, undermining the utility of this Android integration. Cautious consideration should be given to safety implications as effectively, making certain the compatibility layer would not introduce vulnerabilities inside the Chrome OS surroundings.
2. Useful resource Allocation
Efficient useful resource allocation is paramount for a seamless person expertise with Android purposes on Chrome OS. The underlying Chrome OS should intelligently distribute computing sources to each its core features and the virtualized Android surroundings to keep away from efficiency degradation or system instability. Correct allocation instantly influences the responsiveness, stability, and general utility.
-
CPU Core Administration
The project of CPU cores between Chrome OS and the virtualized Android surroundings determines processing energy obtainable to every. Inadequate allocation to the Android surroundings leads to sluggish utility efficiency, whereas extreme allocation may impair Chrome OS system responsiveness. A dynamic allocation technique, which adjusts sources based mostly on present workload, proves important. For example, throughout energetic use of a demanding Android sport, extra CPU cores needs to be allotted to the virtualized surroundings, whereas background processes ought to obtain fewer sources. Improper administration leads to stuttering, utility freezes, or general system unresponsiveness.
-
Reminiscence Partitioning
RAM allocation dictates the quantity of working reminiscence obtainable to each working methods. The Android surroundings necessitates ample reminiscence to run purposes and retailer knowledge. Inadequate allocation triggers efficiency bottlenecks and utility crashes. Chrome OS additionally requires sufficient reminiscence for its processes. Reminiscence partitioning needs to be dynamic, increasing or contracting in line with the present calls for. Take into account working a number of Android purposes concurrently, every requiring a selected reminiscence footprint. Insufficient partitioning results in fixed swapping, elevated latency, and a compromised person expertise.
-
Storage I/O Prioritization
Environment friendly entry to storage is significant for utility loading instances, knowledge storage, and general responsiveness. Chrome OS should prioritize I/O operations between its storage system and the virtualized Android surroundings. A system that permits the Android surroundings to monopolize storage entry leads to delayed Chrome OS operations. Conversely, fixed interruption of Android I/O leads to sluggish utility efficiency. For instance, contemplate an Android utility downloading a big file. Environment friendly I/O prioritization ensures Chrome OS stays responsive even throughout this course of. A good allocation technique offers optimum expertise.
-
Graphics Processing Unit (GPU) Sharing
Android purposes typically make the most of the GPU for rendering graphical parts and performing computations. Sharing the GPU between Chrome OS and the virtualized Android surroundings should be rigorously managed to forestall rivalry and guarantee each obtain ample rendering sources. Improper allocation may end up in graphical glitches, lowered body charges, or system instability. For example, a graphically intense Android sport ought to obtain precedence GPU entry, whereas background Chrome OS processes obtain decrease precedence. Correct GPU useful resource allocation ensures easy operation and optimum visible expertise.
The advanced interaction between these parts necessitates a classy useful resource administration system. Inadequate or improperly managed useful resource allocation finally undermines the feasibility and utility of working Android purposes. Efficient administration ensures easy operation, stability, and optimum utilization of Chrome OS system capabilities.
3. Efficiency Optimization
Efficiency optimization is a vital determinant of the viability and person expertise of working Android purposes on Chrome OS units. The act of emulation or virtualization introduces overhead, doubtlessly resulting in lowered efficiency in comparison with working the identical purposes natively on Android {hardware}. Due to this fact, methods to mitigate this efficiency influence are important for making certain usability. With out efficient optimization, the advantages of expanded utility availability are offset by unacceptable sluggishness, rendering the combination largely impractical.
Optimization efforts should deal with varied sides, together with environment friendly code translation from Android’s runtime surroundings (ART/Dalvik) to Chrome OS’s underlying system structure. This entails streamlining the instruction units utilized by the Android utility to execute effectively on the {hardware}. Moreover, reminiscence administration performs a major position. Optimizing reminiscence allocation and minimizing reminiscence leaks inside the emulated surroundings prevents efficiency bottlenecks and ensures the steadiness of the Android purposes. One particular instance can be a picture enhancing utility. With out optimization, making use of even fundamental filters could end in noticeable delays or system freezes. With optimization, these operations turn out to be fluid and responsive, mirroring the expertise on a local Android system. The mixing with Chrome OS’s graphics drivers requires meticulous optimization as effectively. Environment friendly utilization of the GPU avoids rendering bottlenecks, leading to easy animations and responsive person interfaces. Correct threading and concurrency administration is vital, permitting the purposes to leverage the multi-core processors of Chromebooks successfully.
In abstract, efficiency optimization just isn’t merely an non-compulsory enhancement, however a elementary requirement for a passable expertise when working Android purposes on Chrome OS. The trouble instantly influences utility responsiveness, battery life, and general system stability. Ongoing developments in emulation expertise, mixed with clever useful resource allocation, present the pathway for enhancing the usability of Android purposes on Chromebooks. Failing to prioritize this results in a degraded person expertise, thereby negating a lot of some great benefits of this utility integration functionality.
4. Software Help
The extent of utility help defines the performance and value of the Android emulation on Chrome OS. It instantly determines which Android purposes will be executed and the way reliably they function inside the Chrome OS surroundings. A complete and strong utility help ecosystem enhances the worth proposition of Chrome OS units, enabling customers to entry a wider vary of software program past web-based purposes. It is a essential element of the general person expertise. Restricted utility help restricts the performance and attractiveness of the system, lowering its attraction for customers requiring entry to particular Android purposes. A direct cause-and-effect relationship exists: expanded utility help drives elevated person satisfaction and productiveness. For instance, if vital productiveness purposes or instructional sources designed for Android are unsupported, the usefulness of the emulator diminishes considerably.
Software help just isn’t merely a binary (supported/unsupported) attribute. Completely different purposes may exhibit various levels of performance and efficiency. Some could function flawlessly, whereas others could expertise efficiency points, graphical glitches, or full failure. This variability underscores the complexity of making certain complete utility help. The sensible significance of that is evident when contemplating specialised purposes, reminiscent of these associated to scientific computing or engineering design. These usually depend on particular {hardware} options or libraries, which could not be absolutely emulated or supported. Due to this fact, understanding the restrictions of utility help is crucial for customers to make knowledgeable selections concerning the suitability of a Chromebook for his or her particular wants. The flexibility to run a desired utility is commonly a pivotal buy consideration.
In abstract, utility help is a vital issue that determines the success or failure of Android emulation on Chrome OS. A restricted utility library severely restricts the worth of the system to potential customers. Overcoming challenges related to making certain broad and steady utility help necessitates steady effort in compatibility testing, efficiency optimization, and the incorporation of latest Android runtime options. The target stays clear: to supply a seamless and dependable expertise when executing Android purposes on Chrome OS, increasing the general performance and growing the attraction of Chromebooks.
5. Safety Issues
The implementation of a virtualized Android surroundings on Chrome OS introduces distinct safety issues. The Android working system, designed for cell units, operates inside a sandboxed surroundings on Chrome OS. This sandboxing is meant to isolate the Android runtime from the core Chrome OS system, stopping malicious purposes inside the virtualized surroundings from instantly compromising the host working system. Nonetheless, the effectiveness of this isolation is contingent upon the robustness of the virtualization layer and the safety insurance policies enforced by Chrome OS.
Potential assault vectors embrace vulnerabilities inside the virtualization software program itself, which might permit an attacker to flee the sandboxed surroundings and achieve management over the Chrome OS system. Moreover, shared sources, such because the file system or community interfaces, characterize potential factors of vulnerability if not correctly managed. Take into account a state of affairs the place an Android utility, contaminated with malware, makes an attempt to entry delicate knowledge saved inside the Chrome OS file system. A poorly configured or exploited digital surroundings might inadvertently grant this entry, resulting in knowledge theft or system compromise. Efficient safety protocols should deal with these potential vulnerabilities. Routine safety audits, immediate patching of identified vulnerabilities, and strong enter validation are essential to mitigate these dangers. Examples of such safety insurance policies embrace limiting the flexibility of Android purposes to entry particular system sources, imposing strict permissions for file entry, and monitoring community visitors for suspicious exercise. These measures purpose to attenuate the assault floor and make sure that the virtualized Android surroundings doesn’t turn out to be a gateway for malicious exercise.
In abstract, safety issues are paramount within the integration of a virtualized Android surroundings inside Chrome OS. Whereas sandboxing offers a foundational layer of safety, it isn’t a panacea. Addressing potential vulnerabilities inside the virtualization layer, managing shared sources securely, and implementing strong safety insurance policies are important to keep up the integrity of the Chrome OS system. Neglecting these issues might expose the system to vital safety dangers, undermining the general safety posture of the Chromebook.
6. Debugging Capabilities
Debugging capabilities are important for builders using the Android emulator on Chromebooks, facilitating the identification and determination of software program defects. The flexibility to effectively debug purposes instantly impacts growth cycles and the standard of the ultimate product.
-
Logcat Integration
Logcat offers a system for amassing and viewing utility logs, very important for diagnosing runtime errors and tracing utility habits. Within the context of the Android emulator on Chromebooks, Logcat integration permits builders to watch the output of their purposes, determine exceptions, and pinpoint the supply of crashes. An instance can be observing error messages associated to file entry permissions, aiding within the correction of permission settings inside the utility manifest.
-
Breakpoint Help
Breakpoint help allows builders to pause utility execution at particular factors within the code. This function facilitates step-by-step examination of variables and program state, essential for understanding advanced code flows and figuring out logic errors. For instance, a developer can set a breakpoint inside a operate that handles community requests to examine the information being transmitted and obtained, verifying its correctness and diagnosing potential network-related points.
-
Distant Debugging
Distant debugging permits builders to attach a debugging device working on the Chromebook to the emulated Android surroundings. This functionality offers entry to superior debugging options, reminiscent of reminiscence inspection and thread evaluation. An instance entails utilizing Android Debug Bridge (ADB) to attach Android Studio on the Chromebook to the emulator, permitting builders to make the most of the total suite of debugging instruments supplied by the IDE.
-
Efficiency Profiling
Efficiency profiling instruments allow builders to determine efficiency bottlenecks inside their purposes. These instruments present insights into CPU utilization, reminiscence allocation, and different efficiency metrics, aiding builders in optimizing their code for improved effectivity. An instance can be utilizing the Android Profiler to determine sections of code that eat extreme CPU sources, enabling builders to optimize algorithms or knowledge buildings to cut back processing time.
These debugging capabilities are integral to the event course of on Chrome OS. Efficient utilization of Logcat, breakpoint help, distant debugging, and efficiency profiling ensures that purposes working inside the Android emulator are steady, performant, and freed from vital defects. With out these instruments, builders face vital challenges in diagnosing and resolving points, prolonging growth cycles and doubtlessly compromising the standard of the software program.
7. Growth Atmosphere
The event surroundings represents a vital facet of using the Android emulator on Chromebooks, offering the instruments and infrastructure mandatory for constructing, testing, and debugging Android purposes. A well-configured growth surroundings streamlines the applying growth course of, enhancing developer productiveness and software program high quality.
-
Built-in Growth Atmosphere (IDE) Help
Help for industry-standard IDEs, reminiscent of Android Studio, is crucial for environment friendly utility growth. The IDE offers options like code completion, syntax highlighting, and debugging instruments. When creating for the Android emulator on Chromebooks, the IDE allows builders to put in writing code, construct purposes, and deploy them on to the emulator for testing. For instance, Android Studio’s emulator integration permits builders to run and debug purposes on the Chromebook’s virtualized Android surroundings with no need a bodily Android system. This integration reduces the complexity of the event workflow and accelerates the testing course of.
-
Software program Growth Equipment (SDK) Integration
The Android SDK offers the required libraries, instruments, and documentation for constructing Android purposes. Correct SDK integration ensures that builders have entry to the most recent APIs and options obtainable for the Android platform. When focusing on the Android emulator on Chromebooks, the SDK should be accurately configured to match the Android model supported by the emulator. For example, if the emulator is working Android 11, the SDK should be configured to incorporate the Android 11 API degree. Mismatched SDK configurations can result in compatibility points and utility errors.
-
Command-Line Instruments
Command-line instruments, such because the Android Debug Bridge (ADB), provide highly effective capabilities for interacting with the Android emulator. ADB permits builders to put in purposes, switch information, and execute shell instructions on the emulated system. When debugging purposes on the Android emulator on Chromebooks, ADB offers a method to hook up with the emulator, examine its state, and troubleshoot points. A sensible instance is utilizing ADB to put in an utility’s APK file instantly onto the emulator with out utilizing the IDE’s deployment options. These instruments improve developer management and allow superior debugging situations.
-
Model Management System (VCS) Integration
Integration with model management methods, reminiscent of Git, is vital for collaborative growth and code administration. Model management methods permit builders to trace modifications to their code, collaborate with different builders, and revert to earlier variations if mandatory. When creating for the Android emulator on Chromebooks, VCS integration allows builders to handle their code successfully, making certain that modifications are correctly tracked and synchronized throughout the event staff. An instance is utilizing Git to create branches for various options or bug fixes, permitting builders to work independently with out interfering with one another’s progress. The flexibility to revert to prior steady variations is essential.
These sides of the event surroundings are inextricably linked to the efficacy of utilizing the Android emulator on Chromebooks. A well-integrated growth surroundings streamlines the applying growth course of, enabling builders to construct, check, and debug Android purposes with ease. Conversely, a poorly configured or incomplete growth surroundings can hinder developer productiveness and result in elevated growth prices. Environment friendly integration of those parts is essential for realizing the total potential of Android utility growth.
8. Testing Platform
A complete testing platform is integral to the profitable utilization of Android emulators on Chromebooks. The emulator offers a managed surroundings for assessing utility performance, efficiency, and compatibility throughout completely different Android variations and {hardware} configurations. With out rigorous testing inside the emulated surroundings, undetected bugs or efficiency bottlenecks might compromise the person expertise when the applying is deployed on precise Chromebooks. For example, an utility may exhibit sudden habits because of variations in {hardware} acceleration or variations within the Android runtime implementation between the emulator and a bodily system. Such inconsistencies spotlight the necessity for systematic testing to determine and deal with potential points earlier than launch.
The testing platform encompasses varied testing methodologies, together with unit exams, integration exams, and person interface (UI) exams. Unit exams confirm the correctness of particular person code parts, whereas integration exams make sure that completely different modules work collectively seamlessly. UI exams validate the applying’s person interface and make sure that it responds accurately to person enter. For instance, UI exams can simulate person interactions, reminiscent of tapping buttons or coming into textual content, to confirm that the applying behaves as anticipated. The emulator’s functionality to simulate completely different display screen sizes and resolutions permits builders to check the applying’s responsiveness throughout a spread of Chromebook fashions. Moreover, automated testing frameworks will be built-in with the emulator to streamline the testing course of and enhance the reliability of the check outcomes. These frameworks allow builders to put in writing check scripts that mechanically execute check circumstances and report any failures.
The efficient use of the Android emulator as a testing platform presents sure challenges. Sustaining consistency between the emulated surroundings and real-world Chromebook units is crucial for making certain the accuracy of check outcomes. Builders should rigorously configure the emulator to match the goal system’s {hardware} specs and software program configuration. Moreover, the emulator’s efficiency may not at all times precisely mirror the efficiency of the applying on a bodily system, notably for computationally intensive duties. Regardless of these challenges, the Android emulator stays an indispensable device for testing Android purposes on Chromebooks, enabling builders to determine and deal with potential points earlier than deployment. This contributes to the creation of strong, dependable, and user-friendly Android purposes for the Chrome OS ecosystem.
9. Digital Gadget Configuration
Digital system configuration inside the context of Android emulation on Chromebooks represents a vital determinant of efficiency and utility compatibility. The emulator’s performance relies upon the institution of a digital Android surroundings. The attributes of this digital system, specified throughout its configuration, exert a direct affect on the emulator’s capability to precisely mimic the habits of a bodily Android system. Incorrect or insufficient configuration can result in utility instability, efficiency degradation, and even full incompatibility. For instance, allocating inadequate reminiscence to the digital system leads to slower utility loading instances and potential crashes, notably when working memory-intensive purposes. Equally, specifying an incorrect Android model for the digital system renders purposes designed for a special API degree unusable.
The sensible significance of digital system configuration extends to utility testing and growth. Builders make the most of the emulator to check their purposes throughout a spectrum of Android variations and {hardware} configurations, enabling them to determine and deal with potential compatibility points earlier than deployment. The digital system configuration course of permits builders to simulate various {hardware} traits, reminiscent of display screen decision, CPU structure, and GPU capabilities. This ensures that the applying features accurately on completely different Chromebook fashions. Take into account a state of affairs the place a developer wants to make sure that their utility features optimally on each low-end and high-end Chromebooks. By way of cautious digital system configuration, the developer can emulate the efficiency traits of those units, permitting them to optimize the applying’s code accordingly. The aptitude to customise digital system properties is essential for utility refinement.
In abstract, digital system configuration constitutes a core component of Android emulation on Chromebooks. The accuracy and completeness of the configuration instantly influence utility compatibility and efficiency. Furthermore, digital system configuration performs an instrumental position in utility testing and growth, enabling builders to determine and resolve compatibility points earlier than deploying their purposes on Chromebooks. Challenges exist in sustaining parity between the emulated surroundings and bodily units. This course of should be meticulously executed to comprehend the total potential of Android utility execution on Chrome OS.
Steadily Requested Questions
This part addresses frequent inquiries and offers clarification concerning the usage of an Android emulator on Chromebook units.
Query 1: What constitutes an Android emulator on Chromebook {hardware}?
An Android emulator on a Chromebook is a software program surroundings that simulates the Android working system, permitting customers to run Android purposes inside the Chrome OS surroundings. This performance is usually achieved by way of a containerization or virtualization approach.
Query 2: What degree of efficiency will be anticipated when working Android purposes on this method?
Efficiency varies relying on the Chromebook’s {hardware} specs and the complexity of the Android utility. Useful resource-intensive purposes could expertise efficiency degradation in comparison with working natively on Android units.
Query 3: Which Android purposes are suitable with this emulation surroundings?
Compatibility varies. Whereas a major variety of Android purposes are useful, some purposes could exhibit compatibility points or be fully unsupported because of reliance on particular {hardware} options or system libraries.
Query 4: What are the safety issues related to working an Android emulator on Chrome OS?
Safety is paramount. The Android surroundings is usually sandboxed to forestall malicious purposes from compromising the Chrome OS system. Common safety updates are important to mitigate potential vulnerabilities.
Query 5: How is the Android emulator configured and managed on a Chromebook?
The Android emulator is usually built-in inside Chrome OS and managed by way of system settings. Configuration choices could embrace specifying the Android model, allocating sources, and setting permissions.
Query 6: Does the provision of this performance rely upon the Chromebook mannequin?
Availability varies. Older Chromebook fashions could lack the required {hardware} capabilities or software program help to run an Android emulator successfully. Newer fashions are usually extra prone to provide this function.
The knowledge supplied herein goals to make clear frequent factors of confusion concerning Android emulation on Chromebooks. The performance provides comfort, however consciousness of inherent limitations is essential.
The following part will delve into sensible use circumstances and deployment methods.
Android Emulator on Chromebook
The next ideas purpose to optimize the expertise of using an Android emulator on a Chromebook, making certain stability, efficiency, and safety.
Tip 1: Often Replace Chrome OS.
Chrome OS updates typically embrace enhancements to the Android emulation surroundings. Common updates guarantee entry to the most recent efficiency optimizations, bug fixes, and safety patches, mitigating potential compatibility points.
Tip 2: Handle Software Permissions.
Rigorously evaluation and handle the permissions granted to Android purposes. Limiting pointless permissions enhances system safety and protects delicate knowledge from unauthorized entry.
Tip 3: Monitor Useful resource Utilization.
Monitor CPU, reminiscence, and storage utilization. Terminate unused purposes to release sources, optimizing efficiency for actively used Android purposes. The Chrome OS process supervisor offers useful resource monitoring capabilities.
Tip 4: Make the most of Light-weight Purposes.
Prioritize light-weight Android purposes when doable. Much less resource-intensive purposes usually exhibit higher efficiency inside the emulated surroundings, minimizing pressure on the Chromebook’s sources.
Tip 5: Disable Pointless Companies.
Deactivate location companies, background knowledge synchronization, and different non-essential companies inside the Android surroundings. Disabling these options conserves sources and improves battery life.
Tip 6: Periodically Clear Cache and Knowledge.
Clear cached knowledge and utility knowledge repeatedly to forestall efficiency degradation brought on by collected non permanent information. This motion can enhance utility responsiveness and release cupboard space.
Tip 7: Optimize Digital Gadget Configuration.
Modify digital system settings, reminiscent of allotted reminiscence and CPU cores, to match the Chromebook’s {hardware} capabilities. Keep away from over-allocating sources, as this could negatively influence Chrome OS efficiency.
The following pointers, when carried out carefully, contribute to a extra steady, safe, and performant expertise when using Android emulation capabilities on a Chromebook. Adherence to those pointers optimizes system usability.
The following part will present a concluding abstract of the Android emulator performance on Chrome OS.
Android Emulator on Chromebook
This exploration has underscored the multifaceted nature of the Android emulator on Chromebooks. Performance ranges from increasing utility accessibility to presenting challenges in efficiency optimization and safety administration. The compatibility layer, useful resource allocation, debugging capabilities, and digital system configuration are all intrinsically linked. An efficient deployment of the virtualized surroundings necessitates a complete understanding of every element. Safety issues are notably essential, demanding diligence in mitigating potential vulnerabilities. Rigorous testing platforms are equally very important to ensure utility reliability.
The utility of the Android emulator on Chromebooks lies in its potential to bridge the hole between cell utility ecosystems and Chrome OS. Realizing this potential mandates that builders and end-users undertake a method grounded in knowledgeable consciousness and meticulous execution. The continued evolution of virtualization expertise will invariably form the long run panorama. A dedication to steady analysis and adaptation is the requisite path ahead for optimizing the usage of Android purposes on Chrome OS.
