US20130024778A1 - Dynamic cross-environment application configuration/orientation - Google Patents
Dynamic cross-environment application configuration/orientation Download PDFInfo
- Publication number
- US20130024778A1 US20130024778A1 US13/399,929 US201213399929A US2013024778A1 US 20130024778 A1 US20130024778 A1 US 20130024778A1 US 201213399929 A US201213399929 A US 201213399929A US 2013024778 A1 US2013024778 A1 US 2013024778A1
- Authority
- US
- United States
- Prior art keywords
- application
- active
- display
- environment
- mobile
- 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.)
- Abandoned
Links
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/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
- G06F3/1423—Digital output to display device ; Cooperation and interconnection of the display device with other functional units controlling a plurality of local displays, e.g. CRT and flat panel display
-
- 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/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
-
- 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/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
-
- 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/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
- G06F3/1454—Digital output to display device ; Cooperation and interconnection of the display device with other functional units involving copying of the display data of a local workstation or window to a remote workstation or window so that an actual copy of the data is displayed simultaneously on two or more displays, e.g. teledisplay
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
- G09G5/00—Control arrangements or circuits for visual indicators common to cathode-ray tube indicators and other visual indicators
- G09G5/14—Display of multiple viewports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/75—Indicating network or usage conditions on the user display
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
- G09G2340/00—Aspects of display data processing
- G09G2340/04—Changes in size, position or resolution of an image
- G09G2340/0492—Change of orientation of the displayed image, e.g. upside-down, mirrored
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
- G09G2354/00—Aspects of interface with display user
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
- G09G2370/00—Aspects of data communication
- G09G2370/04—Exchange of auxiliary data, i.e. other than image data, between monitor and graphics controller
- G09G2370/045—Exchange of auxiliary data, i.e. other than image data, between monitor and graphics controller using multiple communication channels, e.g. parallel and serial
- G09G2370/047—Exchange of auxiliary data, i.e. other than image data, between monitor and graphics controller using multiple communication channels, e.g. parallel and serial using display data channel standard [DDC] communication
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
- G09G2370/00—Aspects of data communication
- G09G2370/12—Use of DVI or HDMI protocol in interfaces along the display data pipeline
Definitions
- This Application relates generally to the field of mobile computing environments, and more particularly to dynamically configuration applications in a computing environment with multiple active user environments.
- Mobile communications devices are becoming ubiquitous in today's society. For example, as of the end of 2008, 90 percent of Americans had a mobile wireless device.
- smartphones that is, mobile phones built on top of a mobile computing platform.
- Mobile providers have launched hundreds of new smartphones in the last three years based upon several different computing platforms (e.g., Apple iPhone, Android, BlackBerry, Palm, Windows Mobile, and the like).
- smartphone penetration reached almost 23% by the middle of 2010, and over 35% in some age-groups.
- the smartphone market grew by 41% from 2009 to 2010, with over 60 million smartphone subscribers as of July 2010 in the five largest European countries alone.
- Smartphone computing platforms typically include a mobile operating system (“OS”) running on a mobile processor. While mobile processors and mobile OSs have increased the capabilities of these devices, smartphones have not tended to replace personal computer (“PC”) environments (i.e., Windows, Mac OS X, Linux, and the like) such as desktop or notebook computers at least because of the limited user experience provided. In particular, smartphones typically have different processing resources, user interface device(s), peripheral devices, and applications. For example, mobile processors may have a different processor architecture than PC processors that emphasizes features like low-power operation and communications capabilities over raw processing and/or graphics performance.
- OS mobile operating system
- PC personal computer
- smartphones tend to have smaller amounts of other hardware resources such as memory (e.g., SRAM, DRAM, etc.) and storage (e.g., hard disk, SSD, etc.) resources.
- Other considerations typically include a smaller display size that limits the amount of information that can be presented through a mobile OS graphical user interface (“GUI”) and different user input devices.
- GUI graphical user interface
- Use interface input device(s) for smartphones typically include a small thumb-style QWERTY keyboard, touch-screen display, click-wheel, and/or scroll-wheel.
- laptop, notebook, and desktop computers that use a desktop OS typically have a full-size keyboard, pointing device(s), and/or a larger screen area.
- mobile OSs typically have a different architecture where some capabilities and features such as communications, lower power consumption, touch-screen capability, and the like, are emphasized over traditionally emphasized PC capabilities such as processing speed, graphics processing, and application multi-tasking
- Android runs only applications that are specifically developed to run within a Java-based virtual machine runtime environment.
- Android is based on a modified Linux kernel, it uses different standard C libraries, system managers, and services than Linux. Accordingly, applications written for Linux do not run on Android without modification or porting.
- Apple's iPhone uses the iOS mobile operating system. Again, while iOS is derived from Mac OS X, applications developed for OS X do not run on iOS. Therefore, while many applications are available for mobile OSs such as Android and iOS, many other common applications for desktop operating systems such as Linux and Mac OS X are either not available on the mobile platforms or have limited funcitonality. As such, these mobile OSs provide
- smartphones are typically suited for a limited set of user experiences and provide applications designed primarily for the mobile environment.
- smartphones do not provide a suitable desktop user experience, nor do they run most common desktop applications.
- the user interface components typically found on a smartphones tend to be more difficult to use than a full-size keyboard and large display that may be typically found on a PC platform.
- each device has its own CPU, memory, file storage, and operating system.
- Connectivity and file sharing between smartphones and other computing devices involves linking one device (e.g., smartphone, running a mobile OS) to a second, wholly disparate device (e.g., notebook, desktop, or tablet running a desktop OS), through a wireless or wired connection.
- Information is shared across devices by synchronizing data between applications running separately on each device. This process, typically called “synching,” is cumbersome and generally requires active management by the user.
- FIG. 1 illustrates a computing environment that provides multiple user computing experiences, according to various embodiments.
- FIG. 2 illustrates an exemplary system architecture for a mobile computing device, according to various embodiments.
- FIG. 3 illustrates an operating system architecture for a computing environment, according to various embodiments.
- FIG. 4 illustrates an exemplary computing environment employing various aspects of embodiments.
- FIG. 5 illustrates aspects of an operating system architecture for a computing environment, according to various embodiments.
- FIG. 6 illustrates an exemplary boot procedure that may be used to configure an operating system architecture of a mobile computing device in more detail, according to various embodiments.
- FIG. 7 illustrates an operating system architecture configuration for providing cross-environment rendering of applications and/or user interaction spaces, according to various embodiments.
- FIG. 8 illustrates a computing environment with multiple user environments, according to various embodiments.
- FIG. 9 illustrates aspects of cross-environment remote rendering, according to various embodiments.
- FIG. 10 shows a flow diagram of an illustrative method for cross-environment remote rendering in a non-extended rendering context, according to various embodiments.
- FIG. 11 illustrates a registration and drawing process flow for cross-environment remote rendering, according to various embodiments.
- FIG. 12 shows a flow diagram of another illustrative method for cross-environment rendering in a non-extended rendering context, according to various embodiments.
- FIG. 13 illustrates operating system architecture configuration 300 b for providing user interaction support to cross-environment applications, according to various embodiments.
- FIG. 14 illustrates aspects of user interaction support for cross-environment applications rendered using a non-extended graphics context, according to various embodiments.
- FIG. 15 illustrates aspects of concurrent user interface support across multiple OSs using extended rendering contexts, according to various embodiments.
- the present disclosure is generally directed to dynamically managing configuration of applications for display of application screens across multiple active user environments. More particularly, applications or “Apps” may be running on a first operating system (“OS”) of a mobile computing device that generally defines a first active user environment.
- the first active user environment may include one or more display devices and other user input devices.
- An application screen of an App running within the first OS may be displayed within a second active user environment connected to the first active user environment.
- the second active user environment may be associated with the first OS or a second OS also running on the mobile computing device. Further, the application screen may be presented in various ways on the second display of the second active user environment.
- user interface components of the application screen may be dynamically configured according to a current configuration of the second active user environment to provide the optimal user experience across the multiple user environments and presentation variations.
- Dynamic configuration includes dynamic selection of application resources based on the current display characteristics including parameters associated with the second active user environment and application screen presentation within the second active user environment.
- Dynamic configuration may also include dynamically managing application screen orientation across multiple active user environments for various use cases. While the dynamic application configuration techniques presented in the disclosure are discussed with reference to a mobile computing device and various docked terminal environments, the disclosure may, in various embodiments, be applied to other computing devices (e.g., laptop computers, tablet computers, desktop computers, etc.) and is not intended to be limited to handheld mobile computing devices unless otherwise explicitly specified.
- FIG. 1 illustrates a computing environment 100 that provides multiple user computing experiences through multiple active user environments, according to various embodiments.
- a first active user environment 115 of computing environment 100 is defined by display(s) 116 , touch screen sensor(s) 117 , and/or I/O devices 118 of mobile computing device 110 .
- the display(s) 116 may be operative to display a displayed image or “screen.”
- the term display is intended to connote device hardware, whereas screen is intended to connote the displayed image produced on the display.
- a display is physical hardware that is operable to render screen.
- a screen may encompass a majority of one or more displays. For instance, a screen may occupy substantially all of the display area of one or more displays except for areas dedicated to other functions (e.g.
- a screen may be associated with an application and/or an operating system executing on the mobile computing device 110 .
- application screens or desktop screens may be displayed and an application may have various kinds of application screens that are capable of being manipulated as will be described further below.
- mobile computing device 110 When mobile computing device 110 is operated as a stand-alone mobile device, active user environment 115 presents a typical mobile computing user experience.
- mobile computing device 110 typically includes mobile telephony capabilities and user interaction features suited to a mobile computing use model.
- mobile computing device 110 may present a graphical user interface (“GUI”) suited to active user environment 115 including display(s) 116 , touch-screen sensor(s) 117 , and/or I/O device(s) 118 .
- GUI graphical user interface
- the user may interact with Apps running on mobile computing device 110 through an application screen including various interactive features (e.g., buttons, text fields, toggle fields, etc.) presented on display(s) 116 .
- the user interacts with these interactive features by way of I/O device(s) 118 .
- the user interacts with these features by way of touch-screen sensor(s) 117 using gestures and symbols that are input to touch screen sensor(s) 117 using the user's fingers or a stylus.
- the user interacts with these features using a combination of I/O device(s) 118 and touch-screen sensor(s) 117 .
- FIG. 2 illustrates an exemplary hardware system architecture for mobile computing device 110 , according to various embodiments.
- Mobile computing device 110 includes mobile processor 114 with one or more CPU core(s) 204 and external display interface 220 .
- mobile computing device 110 may also include memory 206 , storage devices 208 , touch-screen display controller 212 connected to touch-screen display(s) 116 and/or touch-screen sensor(s) 117 , I/O devices 118 , power management IC 214 connected to battery 216 , cellular modem 218 , communication devices 222 , and/or other devices 224 that are connected to processor 114 through various communication signals and interfaces.
- I/O devices 118 generally includes buttons and other user interface components that may be employed in mobile computing device 110 .
- I/O devices 118 may include a set of buttons, (e.g., back, menu, home, search, etc.), off-screen gesture area, click-wheel, scroll-wheel, QWERTY keyboard, etc.
- Other devices 224 may include, for example, GPS devices, LAN connectivity, microphones, speakers, cameras, accelerometers, gyroscopes, magnetometers, and/or MS/MMC/SD/SDIO card interfaces.
- External display interface 220 may be any suitable display interface (e.g., VGA, DVI, HDMI, wireless, etc.).
- One or more sensor devices of the mobile computing device 110 may be able to monitor the orientation of the mobile computing device with respect to gravity. For example, using an accelerometer, gyroscope, inclinometer, or magnetometer, or some combination of these sensors, mobile computing device 110 may be able to determine whether it is substantially in a portrait orientation (meaning that a long axis of the display(s) 116 is oriented vertically) or substantially in a landscape orientation (long axis oriented horizontally) with respect to gravity. These devices may further provide other control functionality by monitoring the orientation and/or movement of the mobile computing device 110 .
- a portrait orientation meaning that a long axis of the display(s) 116 is oriented vertically
- a landscape orientation long axis oriented horizontally
- orientation sensor is intended to mean some combination of sensors (e.g., accelerometer, gyroscope, inclinometer, magnetometer, etc.) that may be used to determine orientation of a device with respect to gravity and is not intended to be limited to any particular sensor type or technology.
- sensors e.g., accelerometer, gyroscope, inclinometer, magnetometer, etc.
- Processor 114 may be an ARM-based mobile processor.
- mobile processor 114 is a mobile ARM-based processor such as Texas Instruments OMAP3430, Marvell PXA320, Freescale iMX51, or Qualcomm QSD8650/8250.
- mobile processor 114 may be another suitable ARM-based mobile processor or processor based on other processor architectures such as, for example, x86-based processor architectures or other RISC-based processor architectures.
- FIG. 2 illustrates one exemplary hardware implementation 112 for mobile computing device 110
- other architectures are contemplated as within the scope of the invention.
- various components illustrated in FIG. 2 as external to mobile processor 114 may be integrated into mobile processor 114 .
- external display interface 220 shown in FIG. 2 as integrated into mobile processor 114 , may be external to mobile processor 114 .
- other computer architectures employing a system bus, discrete graphics processor, and/or other architectural variations are suitable for employing aspects of the present invention.
- Secondary terminal environment 140 may be some combination of visual rendering devices (e.g., monitor or display) 140 , I/O devices (e.g., mouse, touch pad, touch-screen, keyboard, etc.) 146 , and other computing peripherals (e.g., HDD, optical disc drive, memory stick, camera, printer, GPS, accelerometer, etc.) 148 connected to mobile computing device 110 by connecting port 142 on secondary terminal environment 140 with port 120 on mobile computing device 110 through interface 122 .
- visual rendering devices e.g., monitor or display
- I/O devices e.g., mouse, touch pad, touch-screen, keyboard, etc.
- other computing peripherals e.g., HDD, optical disc drive, memory stick, camera, printer, GPS, accelerometer, etc.
- Interface 122 may be some combination of wired (e.g., USB, Firewire, Thunderbolt, HDMI, VGA, etc.) or wireless (e.g., Bluetooth, WiFi, Wireless HDMI, etc.) interfaces. While secondary terminal environments may have some processing or logic elements such as microcontrollers or other application specific integrated circuits (“ASICs”), they typically do not have a processor that runs a separate instance of an operating system.
- wired e.g., USB, Firewire, Thunderbolt, HDMI, VGA, etc.
- wireless e.g., Bluetooth, WiFi, Wireless HDMI, etc.
- secondary terminal environments may have some processing or logic elements such as microcontrollers or other application specific integrated circuits (“ASICs”), they typically do not have a processor that runs a separate instance of an operating system.
- ASICs application specific integrated circuits
- Secondary terminal environments that define a second active user environment may be suited for one or more of various use models, depending on the components that make up the secondary terminal environment.
- Some secondary terminal environments may be associated with a user computing experience that is similar to the user computing experience of the mobile computing device 110 , while others may provide a user computing experience more traditionally associated with desktop computing.
- secondary terminal environment 140 may be a device that includes a display 144 with a corresponding touch-screen sensor 146 that serves as the primary user input for the device.
- This type of secondary terminal environment may be called a tablet-style secondary terminal environment. While a tablet-style secondary terminal environment may have a larger touch-screen display than mobile computing device 110 , the user experience of this type of secondary terminal environment may be similar in some ways to the user experience of mobile computing device 110 .
- a tablet-style secondary terminal environment includes a 10.1-inch diagonal (1280 ⁇ 800 resolution) touch-enabled display, standard set of buttons (e.g., back, menu, home, search, etc.), one or more cameras, and an off-screen gesture area.
- a tablet-style secondary terminal environment may include other peripheral devices that may be used to influence the configuration of applications presented to the user on the tablet-style secondary terminal environment.
- a tablet-style secondary terminal environment may include a GPS receiver, accelerometer, gyroscope, magnetometer, and/or other sensors for determining its location and/or orientation. Using these sensors, the tablet-style secondary terminal environment may be able to determine whether it is substantially in a portrait orientation or substantially in a landscape orientation.
- a notebook-style secondary terminal environment generally includes a display screen 144 , keyboard and pointing device(s) 146 , and/or other peripheral devices 148 in a clam-shell type enclosure.
- a laptop or notebook-style secondary terminal environment may be known as a “Smart Display” or “LapDock.” Because this type of secondary terminal environment includes a larger display, full-size keyboard, and pointing device(s), it typically has a user computing experience associated with a desktop computing experience. In this regard, this type of secondary terminal environment may not have a similar user experience profile to mobile computing device 110 .
- a notebook-style secondary terminal environment may include other peripheral devices that may be used to influence the configuration of applications presented to the user on the secondary terminal environment.
- a notebook-style secondary terminal environment may include a GPS receiver, accelerometer, gyroscope, magnetometer, and/or other sensors for determining its location and/or orientation. Using these sensors, the tablet-style secondary terminal environment may be able to determine whether it is substantially in a portrait orientation or substantially in a landscape orientation.
- the various secondary terminal environments may also include a variety of generic input/output device peripherals that make up a typical desktop computing environment.
- the I/O devices may be connected through a docking hub (or “dock cradle”) that includes port 142 and one or more device I/O ports for connecting various commercially available display monitors 144 , I/O devices 146 , and/or other peripheral devices 148 .
- a docking hub may include a display port (e.g., VGA, DVI, HDMI, Wireless HDMI, etc.), and generic device ports (e.g., USB, Firewire, etc.).
- a user may connect a commercially available display, keyboard, and pointing device(s) to the docking hub.
- this secondary terminal environment will be suited to a desktop computing experience.
- this type of secondary terminal environment may be suited to a computing experience designed around the use of a pointing device(s) and physical keyboard to interact with a user interface on the display.
- mobile computing device 110 includes multiple operating systems running concurrently on a shared kernel. Concurrent execution of a mobile OS and a desktop OS on a shared kernel is described in more detail in U.S. patent application Ser. No. 13/217,108, filed Aug. 24, 2011, entitled “MULTI-OPERATING SYSTEM,” herein incorporated by reference. In this way, a single mobile computing device can provide a mobile computing experience through a first user interaction space and a desktop computing experience through a second user interaction space.
- FIG. 3 illustrates OS architecture 300 that may be employed to run mobile OS 130 and desktop OS 160 concurrently on mobile computing device 110 , according to various embodiments.
- mobile OS 130 and desktop OS 160 are independent operating systems.
- mobile OS 130 and desktop OS 160 may have independent and incompatible user libraries, graphics systems, and/or framework layers.
- Functions and instructions for OS architecture 300 may be stored as computer program code on a tangible computer readable medium of mobile computing device 110 .
- instructions for OS architecture 300 may be stored in storage device(s) 208 of mobile computing device 110 .
- mobile OS 130 and desktop OS 160 run concurrently on shared kernel 320 .
- mobile OS 130 and desktop OS 160 both interface to shared kernel 320 through the same kernel interface 322 , for example, by making system calls to shared kernel 320 .
- Shared kernel 320 manages task scheduling for processes of both mobile OS 130 and desktop OS 160 .
- mobile OS 130 and desktop OS 160 are running independently and concurrently on shared kernel 320 .
- shared kernel 320 runs directly on mobile processor 114 of mobile computing device 110 , as illustrated in FIG. 3 .
- shared kernel 320 directly manages the computing resources of processor 114 such as CPU scheduling, memory access, and I/O.
- hardware resources are not virtualized, meaning that mobile OS 130 and desktop OS 160 make system calls through kernel interface 322 without virtualized memory or I/O access.
- mobile OS 130 has libraries layer 330 , application framework layer 340 , and application layer 350 .
- applications 352 and 354 run in application layer 350 supported by application framework layer 340 of mobile OS 130 .
- Application framework layer 340 includes manager(s) 342 and service(s) 344 that are used by applications running on mobile OS 130 .
- application framework layer 340 may include a window manager, activity manager, package manager, resource manager, telephony manager, gesture controller, and/or other managers and services for the mobile environment.
- Application framework layer 340 may include a mobile application runtime environment that executes applications developed for mobile OS 130 .
- the mobile application runtime environment may be optimized for mobile computing resources such as lower processing power and/or limited memory space.
- the mobile application runtime environment may rely on the kernel for process isolation, memory management, and threading support.
- Libraries layer 330 includes user libraries 332 that implement common functions such as I/O and string manipulation, graphics functions, database capabilities, communication capabilities, and/or other functions and capabilities.
- desktop OS 160 has libraries layer 360 , framework layer 370 , and application layer 380 .
- applications 382 and 384 run in application layer 380 supported by application framework layer 370 of desktop OS 160 .
- Application framework layer 370 includes manager(s) 372 and service(s) 374 that are used by applications running on desktop OS 160 .
- application framework layer 370 may include a window manager, activity manager, package manager, resource manager, and/or other managers and services common to a desktop environment.
- Libraries layer 360 may include user libraries 362 that implement common functions such as I/O and string manipulation, graphics functions, database capabilities, communication capabilities, and/or other functions and capabilities.
- desktop OS 160 runs in a separate execution environment from mobile OS 130 .
- mobile OS 130 may run in a root execution environment and desktop OS 160 may run in a secondary execution environment established under the root execution environment.
- Processes and applications running on mobile OS 130 access user libraries 332 , manager(s) 342 and service(s) 344 in the root execution environment.
- Processes and applications running on desktop OS 160 access user libraries 362 , manager(s) 372 and service(s) 374 in the secondary execution environment.
- mobile OS 130 and desktop 160 are independent operating systems with incompatible user libraries, graphics systems, and/or application frameworks. Therefore, applications developed for mobile OS 130 may not run directly on desktop OS 160 , and applications developed for desktop OS 160 may not run directly on mobile OS 130 .
- application 352 running in application layer 350 of mobile OS 130 , may be incompatible with desktop OS 160 , meaning that application 352 could not run on desktop OS 160 .
- application 352 may depend on manager(s) 342 , service(s) 344 , and/or libraries 332 of mobile OS 130 that are either not available or not compatible with manager(s) 372 , service(s) 374 , and/or libraries 362 of desktop OS 160 .
- mobile OS 130 and desktop OS 160 may have different sets of available applications.
- mobile OS 130 and desktop OS 160 of OS architecture 300 provide separate user experiences through separate sets of applications accessible through separate user interaction spaces. The user may access the applications available on (i.e., compiled for and loaded within the execution environment of) mobile OS 130 through a first user interaction space associated with mobile OS 130 , and the applications available on desktop OS 160 through a second user interaction space associated with desktop OS 160 .
- graphics environments for desktop OSs were designed for flexibility and high performance.
- the X-window system used by some desktop OSs, provides platform and network independence at the expense of greater processing and system resources.
- graphics environments for mobile OSs are designed more for efficiency and the specific user input devices of a mobile computing environment and less for flexibility. Because the graphics environments of mobile and desktop OSs are often different, an application running on a mobile OS may not be re-directed to display within a user space of a desktop OS by re-directing the graphics information from the graphics server of the mobile OS to the graphics server of the desktop OS.
- the most widely adopted mobile OS is Google's Android. While Android is based on Linux, it includes modifications to the kernel and other OS layers for the mobile environment and mobile processors. In particular, while the Linux kernel is designed for a PC (i.e., x86) CPU architecture, the Android kernel is modified for ARM-based mobile processors. Android device drivers are also particularly tailored for devices typically present in a mobile hardware architecture including touch-screens, mobile connectivity (GSM/EDGE, CDMA, Wi-Fi, etc.), battery management, GPS, accelerometers, and camera modules, among other devices. In addition, Android does not have a native X Window System nor does it support the full set of standard GNU libraries, and this makes it difficult to port existing GNU/Linux applications or libraries to Android.
- Android does not have a native X Window System nor does it support the full set of standard GNU libraries, and this makes it difficult to port existing GNU/Linux applications or libraries to Android.
- Apple's iOS operating system (run on the iPhone) and Microsoft's Windows Phone 7 are similarly modified for the mobile environment and mobile hardware architecture.
- iOS is derived from the Mac OS X desktop OS
- common Mac OS X applications do not run natively on iOS.
- iOS applications are developed through a standard developer's kit (“SDK”) to run within the “Cocoa Touch” runtime environment of iOS, which provides basic application infrastructure and support for key iOS features such as touch-based input, push notifications, and system services. Therefore, applications written for Mac OS X do not run on iOS without porting.
- SDK developer's kit
- an Android mobile OS and a full Linux OS run independently and concurrently on a modified Android kernel.
- the Android OS may be a modified Android distribution while the Linux OS (“Hydroid”) may be a modified Debian Linux desktop OS.
- FIGS. 4-6 illustrate Android mobile OS 430 , Android kernel 520 , and Hydroid OS 660 that may be employed in OS architecture 300 in more detail, according to various embodiments.
- Android OS 430 includes a set of C/C++ libraries in libraries layer 432 that are accessed through application framework layer 440 .
- Libraries layer 432 includes the “bionic” system C library 439 that was developed specifically for Android to be smaller and faster than the “glibc” Linux C-library.
- Libraries layer 432 also includes inter-process communication (“IPC”) library 436 , which includes the base classes for the “Binder” IPC mechanism of the Android OS. Binder was developed specifically for Android to allow communication between processes and services.
- IPC inter-process communication
- libraries 435 that support recording and playback of media formats
- surface manager 434 that manages access to the display subsystem and composites graphic layers from multiple applications
- 2D and 3D graphics engines 438 and lightweight relational database engine 437 .
- Other libraries that may be included in libraries layer 432 but are not pictured in FIG. 4 include bitmap and vector font rendering libraries, utilities libraries, browser tools (i.e., WebKit, etc.), and/or secure communication libraries (i.e., SSL, etc.).
- Application framework layer 440 of Android OS 430 provides a development platform that allows developers to use components of the device hardware, access location information, run background services, set alarms, add notifications to the status bar, etc. Framework layer 440 also allows applications to publish their capabilities and make use of the published capabilities of other applications.
- Components of application framework layer 440 of Android mobile OS 430 include activity manager 441 , resource manager 442 , window manager 443 , dock manager 444 , hardware and system services 445 , desktop monitor service 446 , multi-display manager 447 , and remote communication service 448 .
- Other components that may be included in framework layer 440 of Android mobile OS 430 include a view system, telephony manager, package manager, location manager, and/or notification manager, among other managers and services.
- Applications running on Android OS 430 run within the Dalvik virtual machine 431 in the Android runtime environment 433 on top of the Android object-oriented application framework.
- Dalvik virtual machine 431 is a register-based virtual machine, and runs a compact executable format that is designed to reduce memory usage and processing requirements.
- Applications running on Android OS 430 include home screen 451 , email application 452 , phone application 453 , browser application 454 , and/or other application(s) (“App(s)”) 455 .
- Each application may include one or more application screens through which the user interfaces with the application.
- the Android OS graphics system uses a client/server model.
- a surface manager (“SurfaceFlinger”) is the graphics server and applications are the clients. SurfaceFlinger maintains a list of display ID's and keeps track of assigning applications to display ID's.
- mobile computing device 110 has multiple touch screen displays 116 .
- display ID 0 is associated with one of the touch screen displays 116 and display ID 1 is associated with the other touch screen display 116 .
- Display ID 2 is associated with both touch screen displays 116 (i.e., the application is displayed on both displays at the same time).
- Graphics information for Android applications and/or activities includes windows, views, and canvasses. Each window, view, and/or canvas is implemented with an underlying surface object.
- Surface objects are double-buffered (front and back buffers) and synchronized across processes for drawing.
- SurfaceFlinger maintains all surfaces in a shared memory pool which allows all processes within Android to access and draw into them without expensive copy operations and without using a server-side drawing protocol such as X-Windows.
- Applications always draw into the back buffer while SurfaceFlinger reads from the front buffer.
- SurfaceFlinger creates each surface object, maintains all surface objects, and also maintains a list of surface objects for each application. When the application finishes drawing in the back buffer, it posts an event to SurfaceFlinger, which swaps the back buffer to the front and queues the task of rendering the surface information to the frame buffer.
- SurfaceFlinger monitors all window change events. When one or more window change events occur, SurfaceFlinger renders the surface information to the frame buffer for one or more displays.
- Rendering includes compositing the surfaces, i.e., composing the final image frame based on dimensions, transparency, z-order, and visibility of the surfaces. Rendering may also include hardware acceleration (e.g., OpenGL 2D and/or 3D interface for graphics processing hardware). SurfaceFlinger loops over all surface objects and renders their front buffers to the frame buffer in their Z order.
- FIG. 5 illustrates modified Android kernel 520 in more detail, according to various embodiments.
- Modified Android kernel 520 includes touch-screen display driver 521 , camera driver(s) 522 , Bluetooth driver(s) 523 , shared memory allocator 524 , IPC driver(s) 525 , USB driver(s) 526 , WiFi driver(s) 527 , I/O device driver(s) 528 , and/or power management module 530 .
- I/O device driver(s) 528 includes device drivers for external I/O devices, including devices that may be connected to mobile computing device 110 through port 120 .
- Modified Android kernel 520 may include other drivers and functional blocks including a low memory killer, kernel debugger, logging capability, and/or other hardware device drivers.
- FIG. 6 illustrates Hydroid OS 660 in more detail, according to various embodiments.
- Hydroid is a full Linux OS that is capable of running almost any application developed for standard Linux distributions.
- libraries layer 662 of Hydroid OS 660 includes Linux libraries that support networking, graphics processing, database management, and other common program functions.
- user libraries 662 may include the “glibc” Linux C library 664 , Linux graphics libraries 662 (e.g., GTK, OpenGL, etc.), Linux utilities libraries 661 , Linux database libraries, and/or other Linux user libraries.
- Applications run on Hydroid within an X-Windows Linux graphical environment using X-Server 674 , window manager 673 , and/or desktop environment 672 .
- Illustrated applications include word processor 681 , email application 682 , spreadsheet application 683 , browser 684 , and other application(s) 685 .
- the Linux OS graphics system is based on the X-windows (or “X11”) graphics system.
- X-windows is a platform-independent, networked graphics framework.
- X-windows uses a client/server model where the X-server is the graphics server and applications are the clients.
- the X-server controls input/output hardware associated with the Linux OS such as displays, touch-screen displays, keyboards, pointing device(s), etc.
- X-windows provides a server-side drawing graphics architecture, i.e., the X-server maintains the content for drawables including windows and pixmaps.
- X-clients communicate with the X-server by exchanging data packets that describe drawing operations over a communication channel.
- X-clients access the X communication protocol through a library of standard routines (the “Xlib”). For example, an X-client may send a request to the X-server to draw a rectangle in the client window.
- the X-server sends input events to the X-clients, for example, keyboard or pointing device input, and/or window movement or resizing. Input events are relative to client windows. For example, if the user clicks when the pointer is within a window, the X-server sends a packet that includes the input event to the X-client associated with the window that includes the action and positioning of the event relative to the window.
- Hydroid OS 660 includes components of a cross-environment communication framework that facilitates communication with Android OS 430 through shared kernel 520 . These components include IPC library 663 that includes the base classes for the Binder IPC mechanism of the Android OS and remote communications service 671 .
- Hydroid OS 660 is run within a chrooted (created with the ‘chroot’ command) secondary execution environment created within the Android root environment. Processes and applications within Hydroid OS 660 are run within the secondary execution environment such that the apparent root directory seen by these processes and applications is the root directory of the secondary execution environment. In this way, Hydroid OS 660 can run programs written for standard Linux distributions without modification because Linux user libraries 662 are available to processes running on Hydroid OS 660 in the chrooted secondary execution environment.
- mobile computing device 110 typically defines a single active user environment through which the user interacts with mobile OS 130 and/or applications running on the mobile OS. Accordingly, mobile OS 130 typically maintains a single active device configuration that includes configuration qualifiers associated with various parameters of the mobile computing device.
- Device configuration qualifiers may include display properties such as resolution, display pixel density (i.e., dots per inch or “dpi”), display orientation, and/or display aspect ratio.
- Device configuration qualifiers may also include input device properties such as touch-screen type, navigation method (e.g., touch-screen, trackball, scroll-wheel, etc.), keyboard availability, and the like. Display properties such as display resolution, display orientation, and/or display aspect ratio may correspond to various combinations of device configuration qualifiers.
- mobile computing device 110 defines configuration qualifiers for display size (e.g., small, medium, large, xlarge, etc.), display orientation (e.g., portrait, landscape), display pixel density (e.g., low, medium, high, extra-high, etc.), and display aspect ratio (e.g., normal, wide, etc.) that are associated with the display(s) 116 of the mobile computing device.
- display size e.g., small, medium, large, xlarge, etc.
- display orientation e.g., portrait, landscape
- display pixel density e.g., low, medium, high, extra-high, etc.
- display aspect ratio e.g., normal, wide, etc.
- applications for mobile OS 130 may be designed to run on multiple physical device configurations.
- applications may externalize application resources to provide compatibility with multiple different computing device hardware configurations without requiring the application to be recompiled.
- application resources may be maintained in separate files and/or locations from application program code.
- Application resources include images, strings, and/or other components used to create application screens associated with the application.
- application resources may include graphical resources such as drawable resources (e.g., bitmap files, state lists, shapes, re-sizeable bitmaps, nine-patches, etc.), animation drawables, and/or other drawable or graphical elements used by an application to build an application screen.
- mobile OS 130 may be designed to build application screens associated with applications by selecting application screen resources upon startup of the application or modification of an application screen by the application.
- Resources may be grouped into sets of resources which may be indexed using a resource configuration list or hierarchy. Each set of resources may provide application resources appropriate for a particular range of device configurations. Generally, when an application is launched, mobile OS 130 selects resources based on the device configuration for an application screen associated with the application. Mobile OS 130 may follow a predetermined procedure for selecting resources based on device configuration qualifiers. For example, mobile OS 130 may traverse a qualifier table to locate an appropriate set of resources for the current device configuration. The qualifier table may define the precedence of configuration qualifiers for selecting an appropriate resource set from the available resource sets for the application.
- certain device configuration qualifiers may be statically defined for the OS build. These device configuration qualifiers may correspond with physical parameters of the specific mobile computing device. In this regard, these configuration qualifiers are hard-coded into the OS build such that the mobile OS will use these configuration qualifiers to create all application screens for applications run on the mobile OS.
- configuration qualifiers such as display resolution, display pixel density, and display aspect ratio may be statically defined in a mobile OS build.
- Mobile OS 130 may have a mechanism through which it manages device configuration changes during runtime of applications. In particular, mobile OS 130 may tear down an application screen established with a first set of resources for a running application and rebuild the application screen with a second set of resources based on certain configuration changes. Commonly, mobile OS 130 may dynamically rebuild application screens based on an orientation change of the mobile computing device 110 .
- mobile computing device 110 may be docked with secondary terminal environment 140 by connecting port 120 of mobile computing device 110 to port 142 of secondary terminal environment 140 to create a computing environment 100 that includes multiple active user environments.
- the multiple active user environments of computing environment 100 may be configured to be used in different ways for various use models.
- mobile computing device 110 may associate the secondary terminal environment 140 with mobile OS 130 .
- user environment 140 may present a second active user environment to user environment 115 , or, user environment 140 may replace user environment 115 as a single active user environment for mobile computing device 110 . Accordingly, this configuration may have a single active user environment or more than one active user environment associated with mobile OS 130 .
- This configuration of computing environment 100 may be referred to as a single OS, extended active user environment configuration.
- Apps running on mobile OS 130 may be displayed in various configurations on the displays 116 associated with the first user environment 115 and one or more display(s) 144 of the second active user environment 140 .
- an App running on mobile OS 130 could have an application screen displayed on display 144 of the second active user environment 140 .
- mobile computing device 110 has a second operating system (e.g., desktop OS, etc.) in active concurrent execution with the mobile OS on a shared kernel.
- mobile computing device 110 may associate secondary terminal environment 140 with desktop OS 160 .
- computing environment 100 presents a first computing experience through a first active user environment 115 associated with mobile OS 130 , and, concurrently, a second computing experience through second active user environment 140 associated with desktop OS 160 .
- These configurations may generally be referred to as multiple-OS, multiple active user environment configurations.
- applications running on mobile OS 130 may be displayed (i.e., via an application screen) across one or more active user environments. For example, a user may begin interacting with an App running on mobile OS 130 through an application screen displayed within the first user environment 115 , subsequently dock the mobile computing device 110 with a secondary user environment 140 and continue to interact with the same App through an application screen displayed on a display of the secondary user environment 140 . Alternatively, a user may launch an App on mobile OS 130 from within a secondary user environment 140 such that an application screen associated with the App is displayed within the secondary user environment 140 .
- An application screen displayed across environments may be displayed in a number of configurations within the second active user environment.
- the application screen may take up all or substantially all of a display associated with the second active user environment.
- the application screen may be displayed within a window on a display associated with the second active user environment.
- the window may be reconfigured dynamically by the user according to current user preferences related to interacting with the App.
- the second active user environment 140 may be associated with the mobile OS 130 , or, in some instances, the second active user environment 140 may be associated with the desktop OS 160 .
- Embodiments provide various novel techniques for dynamically configuring application screens for various device configurations that include extended user environments and/or multiple user environments.
- Dynamic configuration of application screens includes dynamically maintaining multiple active device configurations (i.e., multiple sets of configuration qualifiers associated with separate active user environments) and dynamic resource selection based on the multiple active device configurations. Dynamic configuration of application screens takes into account characteristics of the multiple active user environments.
- Embodiments also support dynamic configuration of applications displayed across user environments in a multiple operating system computing environment. These embodiments support dynamic configuration of applications running in a first operating system and displayed within console windows of a second operating system on a per console window and/or per application basis.
- these embodiments include determining and maintaining an active device configuration in a first OS associated with a console window of a second OS used to display an application running in the first OS through cross-environment display techniques.
- Application screens of applications running in the first OS are generated using dynamic resource selection based on configuration qualifiers of the active device configuration associated with the console window of the second OS.
- configuration qualifiers associated with a virtual display may be translated from indicators and/or parameters coming from multiple sources. That is, some configuration qualifiers may be determined from parameters associated with the first user environment 115 , while other configuration qualifiers (e.g., orientation qualifier) may be determined from parameters associated with a secondary terminal environment. In yet other embodiments, a single configuration qualifier may be translated from multiple display and/or device parameters, where some display and/or device parameters are associated with the first active user environment 115 and some display and/or device parameters are associated with the secondary terminal environment.
- the mobile computing device may have a fixed mechanical relationship to a secondary terminal environment that determines an orientation relationship or offset.
- the secondary terminal environment may or may not have an independent orientation sensor for determining the orientation of the secondary terminal environment independently of the mobile computing device.
- Embodiments may also use orientation and/or aspect ratio of an application screen within a second active user environment for application configuration, including dynamically selecting resources for the application screen.
- the active device configuration for an application screen may be disassociated from the orientation sensor of the mobile device.
- the orientation qualifier of the active device configuration may be determined according to device characteristics of the second active user environment, a default orientation, and/or a user-selectable orientation.
- FIG. 7 illustrates a computing environment 700 a that includes mobile computing device 110 .
- mobile computing device 110 generally includes one or more display device(s) 116 and one or more input device(s) (e.g., touch screen sensor(s) 117 and/or I/O device(s) 118 , etc.) that make up a first user environment 115 .
- Mobile computing device 110 includes a first operating system (e.g., mobile OS 130 , etc.).
- Mobile computing device 110 may have a second operating system (e.g., desktop OS 160 , etc.) running concurrently with the first OS on a shared kernel.
- the first operating system provides a mobile computing experience through the first active user environment.
- the second OS if present, may be in a suspended state.
- application 752 runs on mobile OS 130 .
- Application 752 includes multiple resource sets including resource set A 742 , resource set B 744 , resource set C 746 , and/or resource set D 748 .
- Resource sets A, B, C, and D may include corresponding resources that may be used to build applications screens that are appropriate for various device configurations.
- application screen 762 is displayed on display(s) 116 of mobile computing device 110 using resource set A 742 .
- Resource set A 742 may have a target device configuration range that includes a display having display properties similar or substantially similar to display device(s) 116 of mobile computing device 110 .
- resource set A may include drawable resources and layout resources that define a particular application screen appearance that is suited to a display having display properties (e.g., height, width, dpi, etc.) within a range that includes display(s) 116 .
- display properties e.g., height, width, dpi, etc.
- FIG. 8 illustrates a computing environment 700 b in which mobile computing device 110 has been docked or connected with a tablet-style secondary terminal environment 840 through interface 122 .
- computing environment 700 b includes a first user environment 115 and a second user environment 840 .
- mobile computing device 110 may determine a user experience profile associated with the secondary terminal environment.
- the mobile computing device 110 may determine that secondary terminal environment has a user experience profile associated with a tablet-style secondary terminal environment.
- mobile computing device 110 may associate tablet-style secondary terminal environment 840 with mobile OS 130 , according to a user or device setting.
- a second OS (e.g., desktop OS 160 ) may be running concurrently with mobile OS 130 on shared kernel 320 .
- the second OS may be in a suspended state when mobile computing device 110 is undocked. If mobile computing device 110 associates a docked tablet-style secondary terminal environment 840 with mobile OS 130 , the second OS may remain suspended.
- Tablet-style secondary terminal environment 840 may have a physical dock connector to which mobile computing device 110 may be attached.
- the physical dock connector may provide electrical coupling (e.g., interface 122 , etc.) and optionally mechanical fixturing of the mobile computing device 110 to the tablet-style secondary terminal environment 840 . That is, the dock connector may establish a predetermined physical relationship between display 116 of the first user environment 115 and display 844 of secondary terminal environment 840 .
- the predetermined physical relationship may define a fixed orientation offset.
- display 844 when display 116 is in a portrait orientation display 844 may also be in a portrait orientation (i.e., the fixed offset may be zero degrees), or when display 116 is in a portrait orientation, display 844 may be in a landscape orientation (i.e., a fixed offset of 90 degrees).
- tablet-style secondary terminal environment 840 may be connected to mobile computing device 110 through a wired or wireless interface that does not constrain the physical relationship between mobile computing device 110 and tablet-style secondary terminal environment 840 .
- tablet-style secondary terminal environment 840 may be connected to mobile computing device 110 through a wireless-HDMI interface.
- relative positioning of tablet-style secondary terminal environment 840 to mobile computing device 110 including orientation with respect to gravity, may be arbitrary.
- tablet-style secondary terminal environment 840 includes an orientation sensor.
- tablet-style secondary terminal environment 804 may indicate an orientation of display 844 with respect to gravity to mobile computing device 110 through interface 122 .
- Mobile computing device 110 may query tablet-style secondary terminal environment 840 to determine various parameters associated with the docked secondary terminal environment 840 .
- mobile computing device may query terminal environment 840 for parameters such as display dimensions (e.g., width, height, etc.), display pixel density (e.g., dpi, etc.), display orientation (e.g., arbitrary, offset, on-board sensing, etc.).
- Mobile computing device 110 may receive these parameters through interface 122 .
- interface 122 may include an extended display identification data (EDID) interface that provides a data structure indicating the display properties and/or I/O device capabilities of the secondary terminal environment 840 .
- EDID extended display identification data
- Various user interface properties for the second user environment 840 may be different than for the first user environment 115 .
- display properties for display 844 of the second user environment 840 may be different than display properties of one or more display(s) 116 of the first user environment 115 .
- display 844 may have a larger screen area (i.e., larger physical display dimensions), higher display resolution, different display aspect ratio, different display pixel density, and/or other differences from display(s) 116 .
- mobile computing device 110 determines that a user experience profile of secondary terminal environment 840 corresponds to a tablet-style secondary terminal environment, and that a device setting or user setting of mobile computing device 110 indicates that this type of secondary terminal environment is to be associated with mobile OS 130 .
- Mobile OS 130 establishes a virtual display (i.e., generates a virtual display ID and corresponding graphics context for building graphics information from application screen content and/or surface data) associated with display 844 of the tablet-style secondary terminal environment 840 .
- mobile computing device 110 may maintain operation of user environment 115 when mobile computing device 110 is docked to a tablet-style secondary terminal environment 840 .
- display 844 of secondary terminal environment 840 acts as an alternative display to display 116 through which the user interfaces with mobile OS 130 .
- mobile computing device 110 may disable user environment 115 when mobile computing device 110 is docked to secondary terminal environment 840 .
- secondary terminal environment 840 replaces user environment 115 as the single active user environment.
- mobile computing device 110 and secondary terminal environment 840 are connected through interface 122 and mobile OS 130 is associated with secondary terminal environment 840 , the user may display one or more active application screens on the second active user environment. For example, the user may have indicated through a gesture or menu selection that application 752 is to be displayed in secondary terminal environment 840 .
- mobile OS 130 Upon detection of an event indicating that the application screen associated with application 752 is to be displayed on display 844 of tablet-style secondary terminal environment 840 , mobile OS 130 builds application screen 864 on display 844 using resources that are appropriate for application screen 864 .
- Dynamically selecting resources for application screen 864 includes determining properties associated with the display and I/O devices associated with tablet-style secondary terminal environment 840 , selecting qualifiers that define the graphics context of the virtual display associated with tablet-style secondary terminal environment 840 , and selecting qualifiers that determine I/O properties of tablet-style secondary terminal environment 840 . That is, mobile OS 130 maintains a separate active device configuration associated with secondary terminal environment 840 (e.g., via the virtual display ID associated with secondary terminal environment 840 ). Configuration qualifiers associated with the secondary terminal environment may be determined in part from device parameters of the mobile computing device (e.g., dock mode, etc) and in part from device parameters of the secondary terminal environment (e.g., aspect ratio, dpi, display size, etc.).
- device parameters of the mobile computing device e.g., dock mode, etc
- device parameters of the secondary terminal environment e.g., aspect ratio, dpi, display size, etc.
- Determining configuration properties of tablet-style secondary terminal environment 840 includes determining an orientation configuration of tablet-style secondary terminal environment 840 .
- Several configuration qualifiers associated with the secondary terminal environment 840 may be dynamically updated as the tablet-style secondary terminal environment 840 is interacted with by the user.
- tablet-style secondary terminal environment 840 has a fixed orientation offset to mobile computing device 110 .
- mobile computing device 110 may physically dock with tablet-style secondary terminal environment 840 such that the docking arrangement defines a fixed orientation relationship between display 116 and display 844 .
- mobile OS 130 establishes a graphics context for the virtual display associated with tablet-style secondary terminal environment 840 according to the orientation of the mobile computing device 110 and the fixed orientation offset.
- mobile computing device 110 may dock with a tablet-style secondary terminal environment 840 such that a long axis of one or more of the display(s) 116 of mobile computing device is orthogonal to the long axis of a display 844 of the tablet-style secondary terminal environment 840 .
- mobile computing device 110 may dock with tablet-style secondary terminal environment 840 such that display(s) 116 of mobile computing device and display 844 have a different orientation offset.
- mobile computing device 110 generates qualifiers for resource selection for application 752 based on an orientation of the mobile computing device 110 and the fixed offset. For example, if mobile computing device 110 has a portrait orientation, mobile OS 130 may define an orientation qualifier for the virtual display associated with display 844 as having a landscape orientation.
- mobile computing device 110 and tablet-style secondary terminal environment 840 may be connected such that they do not have a constrained physical relationship.
- mobile computing device 110 and tablet-style secondary terminal environment 840 may be connected through a wired or wireless interface.
- tablet-style secondary terminal environment 840 may have an on-board orientation sensor to determine the orientation of display 844 with respect to gravity.
- mobile OS 130 associates an orientation qualifier of the virtual display with the orientation of tablet-style secondary terminal environment 840 through an orientation indicator received from the tablet-style secondary terminal environment 840 .
- the secondary terminal environment orientation qualifier is used to determine dynamic resource selection for application screen 864 .
- tablet-style secondary terminal environment 840 may indicate that display 844 is in a portrait orientation.
- application screen 864 may be built using resource set B 744 .
- resource set B 744 may be appropriate for the display properties of display 844 and the current orientation of tablet-style secondary terminal environment 840 .
- mobile OS 130 may maintain the mobile computing device orientation qualifier associated with display of application screens on display 116 of the mobile computing device 110 .
- mobile OS 130 maintains multiple orientation qualifier feeds associated with multiple active user environments.
- Mobile OS 130 may associate orientation qualifiers with particular display IDs such that application screens displayed through the particular displays update according the orientation of the associated displays.
- FIG. 9 illustrates a computing environment 700 c in which the tablet-style secondary terminal environment 840 is operated by the user in a first position 972 generally providing a portrait orientation for display 844 .
- application screen 864 of application 752 has been established using resource set B 744 .
- the user rotates the tablet-style secondary terminal environment 840 from a first position 972 having generally a portrait orientation to a second position 974 having generally a landscape orientation.
- mobile OS 130 updates the orientation qualifier associated with the tablet-style secondary terminal environment based on the change in orientation of mobile computing device 110 and the fixed orientation offset. For example, consider that the fixed orientation offset between mobile computing device 110 and tablet-style secondary terminal environment 840 is 90 degrees. In this instance, when the user rotates the tablet-style secondary terminal environment 840 from the first position 972 to the second position 974 , mobile computing device 110 will indicate that it has been rotated from a landscape to a portrait orientation. In this instance, mobile OS 130 applies the orientation offset and determines that tablet-style secondary terminal environment 840 has been rotated from a portrait orientation to a landscape orientation. Mobile OS 130 tears down the application screen 864 and performs dynamic resource selection to select the appropriate resources for the new orientation. For example, the application screen 964 may be built with resource set C 746 as illustrated in FIG. 9 .
- mobile OS 130 may receive an indicator message from the tablet-style secondary terminal environment 840 indicating that the orientation of display 844 has changed.
- Mobile OS 130 updates the orientation qualifier associated with display 844 to the new orientation of the second position 974 .
- mobile OS 130 tears down application screen 864 and establishes application screen 964 on display 844 using resource set C 746 of application 752 .
- tablet-style secondary terminal environment 840 may not include an independent orientation sensor.
- mobile OS 130 may disassociate resource selection for applications displayed on the second user environment with the orientation qualifier associated with mobile computing device 110 .
- mobile OS 130 may determine the orientation qualifier associated with the second active user environment based on device properties such as a standard use-mode orientation.
- a default orientation setting, user setting, or resource preference parameter may determine the orientation qualifier associated with display 844 of tablet-style secondary terminal environment 840 . For example, a certain application may default to a resource set associated with a portrait orientation of display 844 for an application screen displayed on display 844 .
- the first OS (e.g., mobile OS 130 , etc.) may be running concurrently with a second OS (e.g., desktop OS 160 , etc.) on shared kernel 320 .
- a second OS e.g., desktop OS 160 , etc.
- mobile OS 130 is associated with the first active user environment 115 defined by the mobile computing device 110 .
- desktop OS 160 may be in a suspended state.
- FIG. 10 illustrates a computing environment 700 d where mobile computing device 110 is docked to a secondary terminal environment 1040 .
- Secondary terminal environment 1040 may be a notebook-type secondary terminal environment, a desktop-type secondary terminal environment, and/or another type of secondary terminal environment.
- mobile computing device 110 may associate desktop OS 160 with secondary terminal environment 1040 .
- desktop OS 160 presents an independent desktop computing experience through the second user environment defined by the I/O devices associated with secondary terminal environment 1040 (e.g., display 1044 , a keyboard, pointing device(s), etc.).
- applications running on mobile OS 130 may be accessed and have application screens displayed within a console window of secondary user environment 1040 associated with desktop OS 160 .
- These techniques are described in more detail in U.S. patent application Ser. No. 13/246,665, filed Sep. 27, 2011, entitled “INSTANT REMOTE RENDERING,” the entire contents of which are incorporated herein for all purposes.
- Dynamically configuring applications displayed across user environments associated with different operating systems raises a number of issues.
- mobile OS's typically display one application screen at a time and maintain a single active device configuration associated with the mobile computing device. Accordingly, application screens for mobile OS's are not designed to be dynamically resized.
- a cross-environment application screen may be displayed within a window of a GUI of a separate OS (e.g., desktop OS 160 , etc.).
- a desktop OS may display multiple application screens concurrently within windows of the desktop OS GUI. These windows may be dynamically stretched or otherwise resized in various ways.
- other device configuration parameters associated with a secondary terminal environment may affect how a cross-environment application screen appears and is interacted with by the user.
- input devices associated with secondary terminal environments may determine the way that the user interacts with application screens.
- a secondary terminal environment may also include other attributes that can dynamically affect device configuration.
- the secondary terminal environment may have an orientation sensor that can sense the orientation of a display of the secondary terminal environment with respect to gravity. In these instances, the orientation of the cross-environment application screen may be affected by the orientation of the secondary terminal environment.
- dynamically configuring cross-environment application screens includes maintaining multiple active device configurations based on device configuration parameters that come from a variety of sources.
- sources include devices associated with the secondary terminal environment 1040 (e.g., EDID data from display 1044 , availability and/or type of input devices, sensor information, etc.), console windows displayed on the display of the second user environment, and/or information from sensors on mobile computing device 110 (e.g., ambient light level, etc.).
- Mobile OS 130 determines the appropriate configuration qualifier for each active device configuration and selects resources for applications based on the active device configuration associated with the application (e.g., through a display identifier, etc.).
- computing environment 700 d represents mobile computing device 110 docked with a notebook-style secondary terminal environment 1040 .
- a first application 1052 runs on mobile OS 130 and is associated with application screen 1062 displayed on display 116 of mobile computing device 110 .
- a second application 1054 is also running on mobile OS 130 .
- Application 1054 is associated with application screen 1064 displayed on display 1044 of secondary terminal environment 1040 .
- application screen 1064 may be displayed through a console window 1084 associated with a console application 1080 running on desktop OS 160 .
- mobile OS 130 may define a virtual display associated with console application 1080 . That is, to mobile OS 130 , console application 1080 may be considered an independent display device through which mobile OS 130 may display applications screens and/or other graphics information in console window 1084 .
- mobile OS 130 maintains multiple active device configurations. For example, mobile OS 130 may maintain an active device configuration for the first user environment 115 and a separate active device configuration associated with the console application 1080 through which application screen 1064 is displayed. Further, additional applications may be running on mobile OS 130 and displayed through separate console applications running on desktop OS 160 . Mobile OS 130 may maintain additional separate active device configurations for each application running on mobile OS 130 and displayed remotely (i.e., within a user environment external to mobile computing device 110 ). As described above, application 1054 may include resources 1040 for various different device configurations. For example, application 1054 may include resource sets E 1072 , F 1074 , and G 1076 that define corresponding application screen components appropriate for different device configurations.
- the active device configuration for console window 1084 includes a variety of device configuration qualifiers that may come from several different sources that define properties of the secondary terminal environment 1040 , console window 1084 , and/or mobile computing device 110 .
- the active device configuration for console window 1084 may include configuration qualifiers for the active display size (e.g., small, medium, large, etc.), active display orientation (e.g., portrait, landscape, etc.), active display pixel density (e.g., dpi, etc.), and/or input device configuration (e.g., touch-based, pointing device(s), hardware keyboard present, etc.).
- the active pixel density configuration qualifier may come from a hardware parameter associated with the display 1044 (e.g., EDID data and the like) of the secondary terminal environment.
- the configuration qualifiers for the active device configuration associated with application 1054 may be generated by mobile OS 130 by determining the various hardware components of secondary terminal environment 1040 , various parameters associated with console application 1080 , and/or other information provided by secondary terminal environment 1040 (e.g., sensor data, etc.).
- resources of application 1054 are selected for application screen 1064 based on the configuration qualifiers according to a predefined process for matching resources to various device configurations based on the configuration qualifiers.
- application screen 1064 is built using resource set E 1072 .
- resource set E 1072 may be the best matching resource set according to the configuration qualifiers associated with secondary terminal environment 1040 (e.g., pointing device style interface, display dpi, and the like) and/or a particular size of console window 1084 on display 1044 , as discussed above.
- Some device configuration parameters for the active device configuration associated with application 1054 may change dynamically during runtime of application 1054 .
- a mobile OS typically displays an application screen for a particular application across the entire or substantially the entire display 116 of the mobile computing device.
- console window 1084 may be resize according to how the user wishes to interact with the application. Re-sizing the console window 1084 has the effect of dynamically changing the display device configuration.
- mobile OS dynamically selects one or more resources sets for building a new application screen in response to console window change events.
- FIG. 11 shows computing environment 700 e that illustrates aspects of dynamic cross-environment application configuration based on console window resizing, according to various embodiments.
- a user resizes console window 1084 from a first display area indicated by position 1182 to a second, larger display area indicated by position 1186 .
- the user may resize the window using a drag motion on the corner of the console window as indicated by drag arrow 1184 .
- console application 1080 Upon detection by console application 1080 of the window resize event, console application 1080 notifies mobile OS 130 that parameters associated with the active display size of console window 1084 have changed.
- Mobile OS 130 updates the display configuration qualifiers associated with console application 1080 (e.g., associated with a display identifier through which mobile OS 130 displays application 1054 ). Mobile OS 130 then selects resources for the application screen associated with application 1054 according to the updated display configuration qualifiers. As illustrated in FIG. 11 , application screen 1166 may be built for the modified console window 1084 using resource set F 1074 . For example, resource set F 1074 may be appropriate for the modified console window 1084 on display 1044 of the second user environment 1040 associated with desktop OS 160 .
- FIG. 12 shows computing environment 700 f that illustrates other aspects of dynamic cross-environment application configuration based on console window resizing, according to various embodiments.
- a user resizes console window 1084 from a first display area indicated by position 1282 to a second, display area indicated by position 1286 .
- the user may resize the window using a drag motion on the corner of the console window as indicated by drag arrow 1284 .
- the resizing of the console window 1084 may have the effect of changing the aspect ratio of console window 1084 .
- the window re-sizing event indicated by arrow 1284 may transition console window 1084 from a generally portrait orientation in position 1282 to a generally landscape orientation indicated by position 1286 .
- Mobile OS 130 updates the display configuration qualifiers associated with console application 1080 . For example, mobile OS may update the orientation qualifier and/or the display size qualifiers. Mobile OS 130 then selects resources for the application screen associated with application 1054 according to the updated display configuration qualifiers. As illustrated in FIG. 12 , application screen 1266 may be built for the modified console window 1084 using resource set G 1076 . For example, resource set G 1076 may be appropriate for the modified console window 1084 as shown by position 1286 on display 1044 of the second user environment 1040 associated with desktop OS 160 .
- the orientation configuration qualifier associated with virtual display 1082 takes into account the orientation of the secondary terminal environment and/or the orientation of the mobile computing device 110 .
- the orientation qualifier may take into account the aspect ratio of the console window 1084 as well as an orientation of the display 1044 .
- the orientation qualifier may take into account the aspect ratio of the console window 1084 as well as the orientation of mobile computing device 110 and a fixed orientation offset between the display 1044 and the mobile computing device 110 .
- applications may be designed to implement multiple concurrent application screens.
- a mobile computing device may have more than one built-in display device.
- mobile computing device 110 includes two display devices 116 .
- Applications may take advantage of the presence of multiple display devices by presenting multiple application screens concurrently for various activities of the application. For example, an application may have a list view of items on one application screen and a detail view of a selected item on the second application screen.
- FIG. 13 shows computing environment 700 g that illustrates aspects of dynamic cross-environment application configuration that may take advantage of multiple concurrent application screens, according to various embodiments.
- a user resizes console window 1084 from a first display area indicated by position 1382 to a second, display area indicated by position 1386 .
- the user may resize the window using a drag motion on the corner of the console window as indicated by drag arrow 1384 .
- the application 1054 may have a user setting that indicates that the application should switch to a multiple-screen mode when sufficient screen area is available.
- the user setting could indicate that when a display area associated with the application has more than a certain display area and is in generally a landscape orientation, the application will enter the multiple-screen mode.
- the screen area indicated by position 1386 of console window 1084 may be sufficient for the multiple-screen mode of application 1054 .
- application 1054 may build a first application screen 1366 using a first resource set 1374 , and a second application screen 1368 using a second resource set 1376 .
- FIG. 14 illustrates a process flow 1400 for dynamically configuring a cross-environment application according to aspects of dynamic application configuration described above.
- Process flow 1400 begins at block 1402 where a first application is executed in a first operating system of a mobile computing device.
- the mobile computing device defines a first active user environment.
- the mobile computing device may be docked with a second user environment and may provide graphics information (e.g., application screens and/or desktop screens and the like) to the second user environment through a graphics interface.
- the second user environment may replace the first user environment as the single active user environment, or, it may represent a second active user environment which may be interacted with concurrently with the first active user environment.
- the mobile computing device receives a device configuration change message related to the second active user environment.
- the device configuration change message may be related to properties of the second active user environment and/or application presentation (e.g., application windows, etc.) within the second active user environment.
- the mobile computing device receives a display parameter associated with an active display of the second active user environment.
- the display parameter may indicate the resolution, pixel density (e.g., dpi, etc.), and/or aspect ratio of the active display.
- the mobile OS determines a display qualifier associated with the active display of the second active user environment based on the display parameter.
- the mobile OS may determine a display size qualifier (e.g., medium, large, xlarge, etc.) from display resolution parameters (e.g., width, height in pixels, etc.).
- the mobile OS selects an active resource set from the available resource sets based at least in part on the display qualifier.
- the mobile OS then disestablishes a first application screen associate with the first application at block 1412 .
- the mobile OS uses the active resource set selected at block 1410 , the mobile OS then builds and displays a second application screen at block 1414 on the active display of the second active user environment.
- FIG. 15 illustrates a process flow 1500 for dynamically configuring orientation of a cross-environment application according to aspects of dynamic application configuration described above.
- a first application and a second application are in active concurrent execution in a first OS (e.g., mobile OS) of a mobile computing device associated with a first active user environment, as indicated by block 1502 .
- the first OS receives a first orientation indicator from a first orientation sensor associated with the first active user environment.
- the mobile computing device may include the first orientation sensor.
- the first OS determines a first orientation qualifier associated with an active display of the first active user environment based on the first orientation indicator.
- the first OS uses the first orientation qualifier at block 1508 to select a first resource set for the first application from the available resource sets of the first application based on the orientation qualifier.
- the first OS then displays a first application screen established with the first resource set on a first display of the first active user environment.
- the first OS associates a second orientation qualifier with a second active display of a second active user environment.
- orientation configuration of applications displayed on the second active display of the second active user environment is disassociated from the first orientation qualifier.
- the second orientation qualifier may be determined from parameters received from a second orientation sensor associated with the second active user environment, or from default settings associated with the second active user environment, or from parameters associated with application windows displayed within the second display.
- the first OS selects a second resource set for the second application from the available resource sets of the second application based on the second orientation qualifier.
- a second application screen associated with the second application is established using the second resource set and displayed on the second display at block 1516 . Using this process flow, dynamic orientation of multiple applications is maintained across multiple active user environments to provide a more seamless computing experience.
- the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
- the means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor.
- ASIC application specific integrated circuit
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA field programmable gate array signal
- PLD programmable logic device
- a general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine.
- a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
- a software module may reside in any form of tangible storage medium.
- storage media include random access memory (RAM), read only memory (ROM), flash memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM and so forth.
- RAM random access memory
- ROM read only memory
- flash memory EPROM memory
- EEPROM memory EEPROM memory
- registers a hard disk, a removable disk, a CD-ROM and so forth.
- a storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
- a software module may be a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media.
- the methods disclosed herein comprise one or more actions for achieving the described method.
- the method and/or actions may be interchanged with one another without departing from the scope of the claims.
- the order and/or use of specific actions may be modified without departing from the scope of the claims.
- a storage medium may be any available tangible medium that can be accessed by a computer.
- such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or any other tangible medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
- Disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
- a computer program product may perform operations presented herein.
- a computer program product may be a computer readable tangible medium having instructions tangibly stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein.
- the computer program product may include packaging material.
- Software or instructions may also be transmitted over a transmission medium.
- software may be transmitted from a website, server, or other remote source using a transmission medium such as a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology such as infrared, radio, or microwave.
- a transmission medium such as a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology such as infrared, radio, or microwave.
- modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable.
- a user terminal and/or base station can be coupled to a server to facilitate the transfer of means for performing the methods described herein.
- various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a CD or floppy disk, etc.), such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device.
- storage means e.g., RAM, ROM, a physical storage medium such as a CD or floppy disk, etc.
- any other suitable technique for providing the methods and techniques described herein to a device can be utilized.
Priority Applications (19)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/399,929 US20130024778A1 (en) | 2011-07-13 | 2012-02-17 | Dynamic cross-environment application configuration/orientation |
US13/410,983 US9003311B2 (en) | 2011-08-24 | 2012-03-02 | Activating applications in unified desktop |
US13/410,958 US9122441B2 (en) | 2011-08-24 | 2012-03-02 | Opening applications in unified desktop |
US13/436,823 US9213516B2 (en) | 2011-08-24 | 2012-03-30 | Displaying a unified desktop across devices |
CN201280003868.6A CN103415834B (zh) | 2011-07-13 | 2012-07-13 | 动态跨环境应用配置 |
PCT/US2012/046800 WO2013010144A2 (fr) | 2011-07-13 | 2012-07-13 | Configuration d'application inter-environnement dynamique |
US13/566,336 US9405459B2 (en) | 2011-08-24 | 2012-08-03 | Unified desktop laptop dock software operation |
US13/566,168 US9715252B2 (en) | 2011-08-24 | 2012-08-03 | Unified desktop docking behavior for window stickiness |
US13/604,384 US8990712B2 (en) | 2011-08-24 | 2012-09-05 | Unified desktop triad control user interface for file manager |
US13/836,792 US9152404B2 (en) | 2011-07-13 | 2013-03-15 | Remote device filter |
US13/837,340 US20130268559A1 (en) | 2011-07-13 | 2013-03-15 | Virtual file system remote search |
US14/858,867 US9665333B2 (en) | 2011-08-24 | 2015-09-18 | Unified desktop docking behavior for visible-to-visible extension |
US14/876,588 US10198450B2 (en) | 2011-07-13 | 2015-10-06 | Virtual file system remote search |
US14/887,074 US10678411B2 (en) | 2001-08-24 | 2015-10-19 | Unified desktop input segregation in an application manager |
US14/927,517 US20160117139A1 (en) | 2011-08-24 | 2015-10-30 | Handling applications on a unified desktop |
US14/930,092 US20160124698A1 (en) | 2011-08-24 | 2015-11-02 | Unified desktop triad control user interface for an application launcher |
US14/931,670 US10558414B2 (en) | 2011-08-24 | 2015-11-03 | Unified desktop big brother application pools |
US14/950,632 US10503344B2 (en) | 2011-07-13 | 2015-11-24 | Dynamic cross-environment application configuration/orientation |
US14/965,638 US20160196007A1 (en) | 2011-08-24 | 2015-12-10 | Displaying a unified desktop across connected devices |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161507209P | 2011-07-13 | 2011-07-13 | |
US201161507203P | 2011-07-13 | 2011-07-13 | |
US201161507201P | 2011-07-13 | 2011-07-13 | |
US201161507199P | 2011-07-13 | 2011-07-13 | |
US201161507206P | 2011-07-13 | 2011-07-13 | |
US13/399,929 US20130024778A1 (en) | 2011-07-13 | 2012-02-17 | Dynamic cross-environment application configuration/orientation |
Related Child Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/836,792 Continuation-In-Part US9152404B2 (en) | 2011-07-13 | 2013-03-15 | Remote device filter |
US13/837,340 Continuation-In-Part US20130268559A1 (en) | 2011-07-13 | 2013-03-15 | Virtual file system remote search |
US14/950,632 Continuation US10503344B2 (en) | 2011-07-13 | 2015-11-24 | Dynamic cross-environment application configuration/orientation |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130024778A1 true US20130024778A1 (en) | 2013-01-24 |
Family
ID=47506967
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/399,929 Abandoned US20130024778A1 (en) | 2001-08-24 | 2012-02-17 | Dynamic cross-environment application configuration/orientation |
US14/950,632 Active 2033-04-25 US10503344B2 (en) | 2011-07-13 | 2015-11-24 | Dynamic cross-environment application configuration/orientation |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/950,632 Active 2033-04-25 US10503344B2 (en) | 2011-07-13 | 2015-11-24 | Dynamic cross-environment application configuration/orientation |
Country Status (3)
Country | Link |
---|---|
US (2) | US20130024778A1 (fr) |
CN (1) | CN103415834B (fr) |
WO (1) | WO2013010144A2 (fr) |
Cited By (74)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130050074A1 (en) * | 2011-08-31 | 2013-02-28 | Ryouhei YASUDA | Information processing apparatus, information processing method, and program |
US20130139076A1 (en) * | 2011-11-28 | 2013-05-30 | Sony Computer Entertainment Inc. | Screen setting file generator, generation method thereof, and information processing apparatus and method for displaying screen using screen setting file |
US20130252597A1 (en) * | 2012-03-20 | 2013-09-26 | Qualcomm Incorporated | Controlling applications in mobile device based on environmental context |
US20140002328A1 (en) * | 2012-06-29 | 2014-01-02 | Canon Kabushiki Kaisha | Information processing apparatus, screen display method, and non-transitory computer-readable medium |
US8683496B2 (en) | 2010-10-01 | 2014-03-25 | Z124 | Cross-environment redirection |
US8726294B2 (en) | 2010-10-01 | 2014-05-13 | Z124 | Cross-environment communication using application space API |
US8761831B2 (en) | 2010-10-15 | 2014-06-24 | Z124 | Mirrored remote peripheral interface |
US8819705B2 (en) | 2010-10-01 | 2014-08-26 | Z124 | User interaction support across cross-environment applications |
CN104021021A (zh) * | 2014-06-19 | 2014-09-03 | 深圳市中兴移动通信有限公司 | 移动终端及其通过压力检测实现快捷启动的方法和装置 |
US8842080B2 (en) | 2010-10-01 | 2014-09-23 | Z124 | User interface with screen spanning icon morphing |
US20140289635A1 (en) * | 2013-03-22 | 2014-09-25 | Canon Kabushiki Kaisha | Information processing apparatus and method therefor |
US8868135B2 (en) | 2011-09-27 | 2014-10-21 | Z124 | Orientation arbitration |
US8898443B2 (en) | 2010-10-01 | 2014-11-25 | Z124 | Multi-operating system |
US8924958B1 (en) | 2011-05-24 | 2014-12-30 | BlueStack Systems, Inc. | Application player |
US8933949B2 (en) | 2010-10-01 | 2015-01-13 | Z124 | User interaction across cross-environment applications through an extended graphics context |
US8966379B2 (en) | 2010-10-01 | 2015-02-24 | Z124 | Dynamic cross-environment application configuration/orientation in an active user environment |
US8990712B2 (en) | 2011-08-24 | 2015-03-24 | Z124 | Unified desktop triad control user interface for file manager |
US8990713B2 (en) | 2011-09-27 | 2015-03-24 | Z124 | Unified desktop triad control user interface for an application manager |
US9047102B2 (en) | 2010-10-01 | 2015-06-02 | Z124 | Instant remote rendering |
US9152404B2 (en) | 2011-07-13 | 2015-10-06 | Z124 | Remote device filter |
US9164544B2 (en) | 2011-12-09 | 2015-10-20 | Z124 | Unified desktop: laptop dock, hardware configuration |
US9244668B1 (en) * | 2013-02-11 | 2016-01-26 | Symantec Corporation | Systems and methods for synchronizing mobile computing platforms |
US9268518B2 (en) | 2011-09-27 | 2016-02-23 | Z124 | Unified desktop docking rules |
US9380456B1 (en) | 2013-01-22 | 2016-06-28 | Hypori, Inc. | System, method and computer program product for dynamically switching operating systems in a virtual mobile device platform |
US9380562B1 (en) | 2013-01-22 | 2016-06-28 | Hypori, Inc. | System, method and computer program product for providing notifications from a virtual device to a disconnected physical device |
US9380523B1 (en) | 2013-01-22 | 2016-06-28 | Hypori, Inc. | System, method and computer program product for connecting roaming mobile devices to a virtual device platform |
US9405459B2 (en) | 2011-08-24 | 2016-08-02 | Z124 | Unified desktop laptop dock software operation |
US20160259653A1 (en) * | 2015-03-03 | 2016-09-08 | Software Robotics Corporation Limited | Software robots for programmatically controlling computer programs to perform tasks |
US9445392B1 (en) | 2011-10-07 | 2016-09-13 | BlueStack Systems, Inc. | Method of providing non-native notifications and system thereof |
US20160349931A1 (en) * | 2015-05-28 | 2016-12-01 | Rockwell Automation Technologies, Inc. | Responsive user interface for an industrial environment |
US9529494B2 (en) | 2011-09-27 | 2016-12-27 | Z124 | Unified desktop triad control user interface for a browser |
US9619673B1 (en) | 2013-01-22 | 2017-04-11 | Hypori, Inc. | System, method and computer program product for capturing touch events for a virtual mobile device platform |
US9667703B1 (en) | 2013-01-22 | 2017-05-30 | Hypori, Inc. | System, method and computer program product for generating remote views in a virtual mobile device platform |
US9665333B2 (en) | 2011-08-24 | 2017-05-30 | Z124 | Unified desktop docking behavior for visible-to-visible extension |
CN106814961A (zh) * | 2015-12-02 | 2017-06-09 | 西安中兴新软件有限责任公司 | 一种操作方法和终端 |
US9678624B2 (en) | 2011-09-27 | 2017-06-13 | Z124 | Unified desktop triad control user interface for a phone manager |
US9678640B2 (en) | 2014-09-24 | 2017-06-13 | Microsoft Technology Licensing, Llc | View management architecture |
US9697629B1 (en) * | 2013-01-22 | 2017-07-04 | Hypori, Inc. | System, method and computer product for user performance and device resolution settings |
US9703468B2 (en) | 2011-09-27 | 2017-07-11 | Z124 | Unified desktop independent focus in an application manager |
US9715252B2 (en) | 2011-08-24 | 2017-07-25 | Z124 | Unified desktop docking behavior for window stickiness |
US9769227B2 (en) | 2014-09-24 | 2017-09-19 | Microsoft Technology Licensing, Llc | Presentation of computing environment on multiple devices |
US9778938B2 (en) | 2013-09-30 | 2017-10-03 | Hewlett-Packard Development Company, L.P. | Selecting operating systems based on a computing device mode |
US9819593B1 (en) | 2013-01-22 | 2017-11-14 | Hypori, Inc. | System, method and computer program product providing bypass mechanisms for a virtual mobile device platform |
US9860306B2 (en) | 2014-09-24 | 2018-01-02 | Microsoft Technology Licensing, Llc | Component-specific application presentation histories |
US10025684B2 (en) | 2014-09-24 | 2018-07-17 | Microsoft Technology Licensing, Llc | Lending target device resources to host device computing environment |
US10089093B1 (en) * | 2011-05-24 | 2018-10-02 | BlueStack Systems, Inc. | Apparatuses, systems and methods of switching operating systems |
US10198450B2 (en) | 2011-07-13 | 2019-02-05 | Z124 | Virtual file system remote search |
US10250521B2 (en) | 2013-11-29 | 2019-04-02 | Huawei Technologies Co., Ltd. | Data stream identifying method and device |
US10254950B2 (en) | 2014-05-30 | 2019-04-09 | Huawei Technologies Co., Ltd. | Display method of terminal device and terminal device |
US10360010B1 (en) * | 2017-07-21 | 2019-07-23 | Jpmorgan Chase Bank, N.A. | Method and system for implementing an ATM management and software policy tool |
US10409438B2 (en) | 2011-09-27 | 2019-09-10 | Z124 | Unified desktop big brother applications |
US10409582B1 (en) * | 2017-07-21 | 2019-09-10 | Jpmorgan Chase Bank, N.A. | Method and system for implementing a retail event management tool |
US10448111B2 (en) | 2014-09-24 | 2019-10-15 | Microsoft Technology Licensing, Llc | Content projection |
US10503344B2 (en) | 2011-07-13 | 2019-12-10 | Z124 | Dynamic cross-environment application configuration/orientation |
US10528210B2 (en) | 2010-10-01 | 2020-01-07 | Z124 | Foreground/background assortment of hidden windows |
US10558414B2 (en) | 2011-08-24 | 2020-02-11 | Z124 | Unified desktop big brother application pools |
US10579362B1 (en) * | 2017-07-21 | 2020-03-03 | Jpmorgan Chase Bank, N.A. | Method and system for implementing an ATM phone home and scrapper mapping tool |
US10635296B2 (en) | 2014-09-24 | 2020-04-28 | Microsoft Technology Licensing, Llc | Partitioned application presentation across devices |
US10678411B2 (en) | 2001-08-24 | 2020-06-09 | Z124 | Unified desktop input segregation in an application manager |
US10684813B2 (en) | 2015-08-21 | 2020-06-16 | Samsung Electronics Co., Ltd. | Display device and method for controlling same |
US10685331B2 (en) * | 2015-12-08 | 2020-06-16 | TCL Research America Inc. | Personalized FUNC sequence scheduling method and system |
US10791538B1 (en) | 2011-07-06 | 2020-09-29 | BlueStack Systems, Inc. | Cloud-based data synchronization |
US10915214B2 (en) | 2010-10-01 | 2021-02-09 | Z124 | Annunciator drawer |
US10949075B2 (en) * | 2014-11-06 | 2021-03-16 | Microsoft Technology Licensing, Llc | Application command control for small screen display |
US10983559B2 (en) | 2011-09-27 | 2021-04-20 | Z124 | Unified desktop docking flow |
US11079995B1 (en) * | 2017-09-30 | 2021-08-03 | Apple Inc. | User interfaces for devices with multiple displays |
US11086494B2 (en) | 2017-02-28 | 2021-08-10 | Samsung Electronics Co., Ltd. | Electronic device and method for managing window |
US11093200B2 (en) | 2011-09-27 | 2021-08-17 | Z124 | Unified desktop triad control user interface for an application launcher |
US11126329B2 (en) | 2014-11-06 | 2021-09-21 | Microsoft Technology Licensing, Llc | Application command control for smaller screen display |
US11144190B2 (en) | 2019-08-06 | 2021-10-12 | Samsung Electronics Co., Ltd. | Electronic device and method for sharing data thereof |
US11416131B2 (en) | 2011-09-27 | 2022-08-16 | Z124 | Unified desktop input segregation in an application manager |
US11422765B2 (en) | 2018-07-10 | 2022-08-23 | Apple Inc. | Cross device interactions |
US11423050B2 (en) | 2011-09-27 | 2022-08-23 | Z124 | Rules based hierarchical data virtualization |
US11972164B2 (en) | 2021-07-29 | 2024-04-30 | Apple Inc. | User interfaces for devices with multiple displays |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104035689A (zh) * | 2014-06-24 | 2014-09-10 | 中科创达软件股份有限公司 | 一种按键功能切换方式及装置 |
CN104915144A (zh) * | 2015-06-29 | 2015-09-16 | 惠州华阳通用电子有限公司 | 双屏互动用户界面投射方法 |
US10582011B2 (en) * | 2015-08-06 | 2020-03-03 | Samsung Electronics Co., Ltd. | Application cards based on contextual data |
US10136247B2 (en) * | 2015-10-20 | 2018-11-20 | Microsoft Technology Licensing, Llc | Physical and virtual phone mobility |
DE112016006178T5 (de) * | 2016-01-08 | 2018-09-20 | Hewlett-Packard Development Company, L.P. | Startvorgangsmodifikation |
CN110058649A (zh) * | 2019-03-28 | 2019-07-26 | 维沃移动通信有限公司 | 一种界面显示方法及终端设备 |
WO2020247657A1 (fr) * | 2019-06-04 | 2020-12-10 | Stefan Richard Schacht | Systèmes et procédés permettant de distribuer des articles stériles |
CN111142968A (zh) * | 2019-12-26 | 2020-05-12 | 联想(北京)有限公司 | 电子设备配置推荐处理方法、装置及存储介质 |
CN111796898A (zh) * | 2020-07-03 | 2020-10-20 | 北京三快在线科技有限公司 | 布局调整方法、装置、计算机设备及存储介质 |
CN113840295B (zh) * | 2021-09-26 | 2022-08-09 | 北京字节跳动网络技术有限公司 | 移动数据网络建立方法、装置、电子设备及存储介质 |
WO2023075791A1 (fr) * | 2021-10-29 | 2023-05-04 | Hewlett-Packard Development Company, L.P. | Port d'affichage à commutation connecté à un afficheur externe entre des processeurs graphiques distinct et intégré |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090119580A1 (en) * | 2000-06-12 | 2009-05-07 | Gary B. Rohrabaugh | Scalable Display of Internet Content on Mobile Devices |
US20100064228A1 (en) * | 2008-09-11 | 2010-03-11 | Ely Tsern | Expandable system architecture comprising a handheld computer device that dynamically generates different user environments with secondary devices with displays of various form factors |
US20100097386A1 (en) * | 2008-10-20 | 2010-04-22 | Samsung Electronics Co. Ltd. | Apparatus and method for operating multiple operating systems in multi-modem mobile communication terminal |
US20110093836A1 (en) * | 2009-07-20 | 2011-04-21 | Galicia Joshua D | Multi-environment operating system |
Family Cites Families (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5673403A (en) | 1992-11-13 | 1997-09-30 | International Business Machines Corporation | Method and system for displaying applications of different operating systems on a single system using the user interface of the different operating systems |
JPH06301555A (ja) | 1993-02-26 | 1994-10-28 | Internatl Business Mach Corp <Ibm> | マイクロカーネル上の複数の共存オペレーティング・システム・パーソナリティ用のシステム |
US7284203B1 (en) | 1999-07-27 | 2007-10-16 | Verizon Laboratories Inc. | Method and apparatus for application sharing interface |
JP4395223B2 (ja) | 1999-09-24 | 2010-01-06 | 株式会社日立製作所 | 表示装置、表示方法、および、ナビゲーション装置 |
US20100005396A1 (en) | 2000-02-18 | 2010-01-07 | Nason D David | Method and system for controlling a comlementary user interface on a display surface |
US7478341B2 (en) | 2000-04-19 | 2009-01-13 | Broadcom Corporation | Apparatus and method for persistent display interface |
US9047102B2 (en) | 2010-10-01 | 2015-06-02 | Z124 | Instant remote rendering |
US8819705B2 (en) | 2010-10-01 | 2014-08-26 | Z124 | User interaction support across cross-environment applications |
US8933949B2 (en) | 2010-10-01 | 2015-01-13 | Z124 | User interaction across cross-environment applications through an extended graphics context |
US8726294B2 (en) | 2010-10-01 | 2014-05-13 | Z124 | Cross-environment communication using application space API |
US20130024812A1 (en) | 2011-07-13 | 2013-01-24 | Z124 | Foreground/background assortment of hidden windows |
US20130024778A1 (en) | 2011-07-13 | 2013-01-24 | Z124 | Dynamic cross-environment application configuration/orientation |
US9098437B2 (en) | 2010-10-01 | 2015-08-04 | Z124 | Cross-environment communication framework |
US8966379B2 (en) | 2010-10-01 | 2015-02-24 | Z124 | Dynamic cross-environment application configuration/orientation in an active user environment |
US7013464B2 (en) | 2001-10-17 | 2006-03-14 | Beptech, Inc. | Method of communicating across an operating system |
US20030079205A1 (en) | 2001-10-22 | 2003-04-24 | Takeshi Miyao | System and method for managing operating systems |
US20030115443A1 (en) | 2001-12-18 | 2003-06-19 | Cepulis Darren J. | Multi-O/S system and pre-O/S boot technique for partitioning resources and loading multiple operating systems thereon |
US8943434B2 (en) | 2010-10-01 | 2015-01-27 | Z124 | Method and apparatus for showing stored window display |
EP1503286B1 (fr) | 2003-07-30 | 2014-09-03 | Jaluna SA | Réseau de plusieurs systèmes d'exploitation |
US7478204B2 (en) | 2004-04-29 | 2009-01-13 | International Business Machines Corporation | Efficient sharing of memory between applications running under different operating systems on a shared hardware system |
US20060082581A1 (en) | 2004-10-14 | 2006-04-20 | Microsoft Corporation | Encoding for remoting graphics to decoder device |
US7565535B2 (en) | 2005-05-06 | 2009-07-21 | Microsoft Corporation | Systems and methods for demonstrating authenticity of a virtual machine using a security image |
US8195624B2 (en) | 2005-06-30 | 2012-06-05 | Phoenix Technologies Ltd. | Shared file system management between independent operating systems |
US7950008B2 (en) * | 2005-07-06 | 2011-05-24 | International Business Machines Corporation | Software installation in multiple operating systems |
US20070067769A1 (en) | 2005-08-30 | 2007-03-22 | Geisinger Nile J | Method and apparatus for providing cross-platform hardware support for computer platforms |
US8140997B2 (en) | 2005-12-26 | 2012-03-20 | International Business Machines Corporation | Manipulating display of multiple display objects |
KR20070082691A (ko) | 2006-02-17 | 2007-08-22 | 삼성전자주식회사 | 디지털 멀티미디어 장치 |
US20090278806A1 (en) | 2008-05-06 | 2009-11-12 | Matias Gonzalo Duarte | Extended touch-sensitive control area for electronic device |
KR100772875B1 (ko) * | 2006-05-22 | 2007-11-02 | 삼성전자주식회사 | 사용자 선호도에 따른 사용자 인터페이스를 설정하는 장치및 그 방법 |
US9201703B2 (en) | 2006-06-07 | 2015-12-01 | International Business Machines Corporation | Sharing kernel services among kernels |
US7880728B2 (en) * | 2006-06-29 | 2011-02-01 | Microsoft Corporation | Application switching via a touch screen interface |
KR100811794B1 (ko) | 2006-10-12 | 2008-03-10 | 삼성전자주식회사 | 휴대단말기의 블루투스 기능을 이용하여 프린터를 제어하는방법 |
US20080119731A1 (en) | 2006-11-20 | 2008-05-22 | North American Medical Corporation | Portable ultrasound with touch screen interface |
US8839105B2 (en) | 2006-12-01 | 2014-09-16 | International Business Machines Corporation | Multi-display system and method supporting differing accesibility feature selection |
KR20080085780A (ko) | 2007-03-20 | 2008-09-24 | 이상규 | 운영체제의 가상화 방법 |
US8789063B2 (en) * | 2007-03-30 | 2014-07-22 | Microsoft Corporation | Master and subordinate operating system kernels for heterogeneous multiprocessor systems |
CN101520745B (zh) | 2008-02-27 | 2012-03-28 | 联想(北京)有限公司 | 数据处理设备及其状态切换方法 |
US7930328B2 (en) | 2008-03-31 | 2011-04-19 | Lenovo (Singapore) Pte. Ltd. | Apparatus, system, and method for file system sharing |
US20100046026A1 (en) | 2008-08-21 | 2010-02-25 | Samsung Electronics Co., Ltd. | Image forming apparatus and image forming method |
US8165558B2 (en) | 2008-09-08 | 2012-04-24 | Celio Technology Corporation | Client device for cellular telephone as server |
US8803816B2 (en) | 2008-09-08 | 2014-08-12 | Qualcomm Incorporated | Multi-fold mobile device with configurable interface |
US9009984B2 (en) | 2008-09-08 | 2015-04-21 | Qualcomm Incorporated | Multi-panel electronic device |
US8194001B2 (en) | 2009-03-27 | 2012-06-05 | Microsoft Corporation | Mobile computer device display postures |
US8868899B2 (en) * | 2009-07-20 | 2014-10-21 | Motorola Mobility Llc | System and method for switching between environments in a multi-environment operating system |
US9052800B2 (en) | 2010-10-01 | 2015-06-09 | Z124 | User interface with stacked application management |
CN107122168A (zh) | 2010-10-01 | 2017-09-01 | Z124 | 多操作系统 |
US9430122B2 (en) | 2010-10-01 | 2016-08-30 | Z124 | Secondary single screen mode activation through off-screen gesture area activation |
US20130312106A1 (en) | 2010-10-01 | 2013-11-21 | Z124 | Selective Remote Wipe |
US8761831B2 (en) | 2010-10-15 | 2014-06-24 | Z124 | Mirrored remote peripheral interface |
US8810533B2 (en) | 2011-07-20 | 2014-08-19 | Z124 | Systems and methods for receiving gesture inputs spanning multiple input devices |
US9182935B2 (en) | 2011-09-27 | 2015-11-10 | Z124 | Secondary single screen mode activation through menu option |
-
2012
- 2012-02-17 US US13/399,929 patent/US20130024778A1/en not_active Abandoned
- 2012-07-13 CN CN201280003868.6A patent/CN103415834B/zh active Active
- 2012-07-13 WO PCT/US2012/046800 patent/WO2013010144A2/fr active Application Filing
-
2015
- 2015-11-24 US US14/950,632 patent/US10503344B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090119580A1 (en) * | 2000-06-12 | 2009-05-07 | Gary B. Rohrabaugh | Scalable Display of Internet Content on Mobile Devices |
US20100064228A1 (en) * | 2008-09-11 | 2010-03-11 | Ely Tsern | Expandable system architecture comprising a handheld computer device that dynamically generates different user environments with secondary devices with displays of various form factors |
US20100097386A1 (en) * | 2008-10-20 | 2010-04-22 | Samsung Electronics Co. Ltd. | Apparatus and method for operating multiple operating systems in multi-modem mobile communication terminal |
US20110093836A1 (en) * | 2009-07-20 | 2011-04-21 | Galicia Joshua D | Multi-environment operating system |
Cited By (130)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10678411B2 (en) | 2001-08-24 | 2020-06-09 | Z124 | Unified desktop input segregation in an application manager |
US9063798B2 (en) | 2010-10-01 | 2015-06-23 | Z124 | Cross-environment communication using application space API |
US8726294B2 (en) | 2010-10-01 | 2014-05-13 | Z124 | Cross-environment communication using application space API |
US9152582B2 (en) | 2010-10-01 | 2015-10-06 | Z124 | Auto-configuration of a docked system in a multi-OS environment |
US8683496B2 (en) | 2010-10-01 | 2014-03-25 | Z124 | Cross-environment redirection |
US9098437B2 (en) | 2010-10-01 | 2015-08-04 | Z124 | Cross-environment communication framework |
US9047102B2 (en) | 2010-10-01 | 2015-06-02 | Z124 | Instant remote rendering |
US8819705B2 (en) | 2010-10-01 | 2014-08-26 | Z124 | User interaction support across cross-environment applications |
US8898443B2 (en) | 2010-10-01 | 2014-11-25 | Z124 | Multi-operating system |
US8842080B2 (en) | 2010-10-01 | 2014-09-23 | Z124 | User interface with screen spanning icon morphing |
US10915214B2 (en) | 2010-10-01 | 2021-02-09 | Z124 | Annunciator drawer |
US9405444B2 (en) | 2010-10-01 | 2016-08-02 | Z124 | User interface with independent drawer control |
US9160796B2 (en) | 2010-10-01 | 2015-10-13 | Z124 | Cross-environment application compatibility for single mobile computing device |
US9727205B2 (en) | 2010-10-01 | 2017-08-08 | Z124 | User interface with screen spanning icon morphing |
US10528210B2 (en) | 2010-10-01 | 2020-01-07 | Z124 | Foreground/background assortment of hidden windows |
US11573674B2 (en) | 2010-10-01 | 2023-02-07 | Z124 | Annunciator drawer |
US9077731B2 (en) | 2010-10-01 | 2015-07-07 | Z124 | Extended graphics context with common compositing |
US9071625B2 (en) | 2010-10-01 | 2015-06-30 | Z124 | Cross-environment event notification |
US9026709B2 (en) | 2010-10-01 | 2015-05-05 | Z124 | Auto-waking of a suspended OS in a dockable system |
US8933949B2 (en) | 2010-10-01 | 2015-01-13 | Z124 | User interaction across cross-environment applications through an extended graphics context |
US8957905B2 (en) | 2010-10-01 | 2015-02-17 | Z124 | Cross-environment user interface mirroring |
US8966379B2 (en) | 2010-10-01 | 2015-02-24 | Z124 | Dynamic cross-environment application configuration/orientation in an active user environment |
US8963939B2 (en) | 2010-10-01 | 2015-02-24 | Z124 | Extended graphics context with divided compositing |
US9060006B2 (en) | 2010-10-01 | 2015-06-16 | Z124 | Application mirroring using multiple graphics contexts |
US9049213B2 (en) | 2010-10-01 | 2015-06-02 | Z124 | Cross-environment user interface mirroring using remote rendering |
US8761831B2 (en) | 2010-10-15 | 2014-06-24 | Z124 | Mirrored remote peripheral interface |
US8924958B1 (en) | 2011-05-24 | 2014-12-30 | BlueStack Systems, Inc. | Application player |
US10310892B1 (en) | 2011-05-24 | 2019-06-04 | BlueStack Systems, Inc. | Apparatuses, systems and methods of switching operating systems |
US10089093B1 (en) * | 2011-05-24 | 2018-10-02 | BlueStack Systems, Inc. | Apparatuses, systems and methods of switching operating systems |
US10791538B1 (en) | 2011-07-06 | 2020-09-29 | BlueStack Systems, Inc. | Cloud-based data synchronization |
US9152404B2 (en) | 2011-07-13 | 2015-10-06 | Z124 | Remote device filter |
US10198450B2 (en) | 2011-07-13 | 2019-02-05 | Z124 | Virtual file system remote search |
US10503344B2 (en) | 2011-07-13 | 2019-12-10 | Z124 | Dynamic cross-environment application configuration/orientation |
US10558414B2 (en) | 2011-08-24 | 2020-02-11 | Z124 | Unified desktop big brother application pools |
US8910061B2 (en) | 2011-08-24 | 2014-12-09 | Z124 | Application manager in a unified desktop |
US9715252B2 (en) | 2011-08-24 | 2017-07-25 | Z124 | Unified desktop docking behavior for window stickiness |
US8990712B2 (en) | 2011-08-24 | 2015-03-24 | Z124 | Unified desktop triad control user interface for file manager |
US9665333B2 (en) | 2011-08-24 | 2017-05-30 | Z124 | Unified desktop docking behavior for visible-to-visible extension |
US9122441B2 (en) | 2011-08-24 | 2015-09-01 | Z124 | Opening applications in unified desktop |
US9003311B2 (en) | 2011-08-24 | 2015-04-07 | Z124 | Activating applications in unified desktop |
US9405459B2 (en) | 2011-08-24 | 2016-08-02 | Z124 | Unified desktop laptop dock software operation |
US9213516B2 (en) | 2011-08-24 | 2015-12-15 | Z124 | Displaying a unified desktop across devices |
US8854300B2 (en) * | 2011-08-31 | 2014-10-07 | Sony Corporation | Information processing apparatus, information processing method, and program |
US20130050074A1 (en) * | 2011-08-31 | 2013-02-28 | Ryouhei YASUDA | Information processing apparatus, information processing method, and program |
US9069518B2 (en) | 2011-09-27 | 2015-06-30 | Z124 | Unified desktop freeform window mode |
US10409438B2 (en) | 2011-09-27 | 2019-09-10 | Z124 | Unified desktop big brother applications |
US9529494B2 (en) | 2011-09-27 | 2016-12-27 | Z124 | Unified desktop triad control user interface for a browser |
US8874894B2 (en) | 2011-09-27 | 2014-10-28 | Z124 | Unified desktop wake and unlock |
US11423050B2 (en) | 2011-09-27 | 2022-08-23 | Z124 | Rules based hierarchical data virtualization |
US9268518B2 (en) | 2011-09-27 | 2016-02-23 | Z124 | Unified desktop docking rules |
US11416131B2 (en) | 2011-09-27 | 2022-08-16 | Z124 | Unified desktop input segregation in an application manager |
US11093200B2 (en) | 2011-09-27 | 2021-08-17 | Z124 | Unified desktop triad control user interface for an application launcher |
US10983559B2 (en) | 2011-09-27 | 2021-04-20 | Z124 | Unified desktop docking flow |
US9128660B2 (en) | 2011-09-27 | 2015-09-08 | Z124 | Dual display pinyin touch input |
US8904165B2 (en) | 2011-09-27 | 2014-12-02 | Z124 | Unified desktop wake and unlock |
US11573597B2 (en) | 2011-09-27 | 2023-02-07 | Z124 | Displaying a unified desktop across connected devices |
US8996073B2 (en) | 2011-09-27 | 2015-03-31 | Z124 | Orientation arbitration |
US9152179B2 (en) | 2011-09-27 | 2015-10-06 | Z124 | Portrait dual display and landscape dual display |
US8872727B2 (en) | 2011-09-27 | 2014-10-28 | Z124 | Activating applications in portions of unified desktop |
US9703468B2 (en) | 2011-09-27 | 2017-07-11 | Z124 | Unified desktop independent focus in an application manager |
US9128659B2 (en) | 2011-09-27 | 2015-09-08 | Z124 | Dual display cursive touch input |
US8990713B2 (en) | 2011-09-27 | 2015-03-24 | Z124 | Unified desktop triad control user interface for an application manager |
US9104366B2 (en) | 2011-09-27 | 2015-08-11 | Z124 | Separation of screen usage for complex language input |
US8868135B2 (en) | 2011-09-27 | 2014-10-21 | Z124 | Orientation arbitration |
US9678624B2 (en) | 2011-09-27 | 2017-06-13 | Z124 | Unified desktop triad control user interface for a phone manager |
US9804864B1 (en) | 2011-10-07 | 2017-10-31 | BlueStack Systems, Inc. | Method of mapping inputs and system thereof |
US10255080B2 (en) | 2011-10-07 | 2019-04-09 | BlueStack Systems, Inc. | Method of providing non-native notifications and system thereof |
US9445392B1 (en) | 2011-10-07 | 2016-09-13 | BlueStack Systems, Inc. | Method of providing non-native notifications and system thereof |
US20130139076A1 (en) * | 2011-11-28 | 2013-05-30 | Sony Computer Entertainment Inc. | Screen setting file generator, generation method thereof, and information processing apparatus and method for displaying screen using screen setting file |
US9164544B2 (en) | 2011-12-09 | 2015-10-20 | Z124 | Unified desktop: laptop dock, hardware configuration |
US20130252597A1 (en) * | 2012-03-20 | 2013-09-26 | Qualcomm Incorporated | Controlling applications in mobile device based on environmental context |
US9167520B2 (en) * | 2012-03-20 | 2015-10-20 | Qualcomm Incorporated | Controlling applications in a mobile device based on environmental context |
US9099022B2 (en) * | 2012-06-29 | 2015-08-04 | Canon Kabushiki Kaisha | Information processing apparatus, screen display method, and non-transitory computer-readable medium |
US20140002328A1 (en) * | 2012-06-29 | 2014-01-02 | Canon Kabushiki Kaisha | Information processing apparatus, screen display method, and non-transitory computer-readable medium |
US9674171B2 (en) | 2013-01-22 | 2017-06-06 | Hypori, Inc. | System, method and computer program product for providing notifications from a virtual device to a disconnected physical device |
US9380456B1 (en) | 2013-01-22 | 2016-06-28 | Hypori, Inc. | System, method and computer program product for dynamically switching operating systems in a virtual mobile device platform |
US10958756B2 (en) | 2013-01-22 | 2021-03-23 | Hypori, LLC | System, method and computer program product for capturing touch events for a virtual mobile device platform |
US9667703B1 (en) | 2013-01-22 | 2017-05-30 | Hypori, Inc. | System, method and computer program product for generating remote views in a virtual mobile device platform |
US9622068B2 (en) | 2013-01-22 | 2017-04-11 | Hypori, Inc. | System, method and computer program product for connecting roaming mobile devices to a virtual device platform |
US9819593B1 (en) | 2013-01-22 | 2017-11-14 | Hypori, Inc. | System, method and computer program product providing bypass mechanisms for a virtual mobile device platform |
US10459772B2 (en) | 2013-01-22 | 2019-10-29 | Intelligent Waves Llc | System, method and computer program product for capturing touch events for a virtual mobile device platform |
US9619673B1 (en) | 2013-01-22 | 2017-04-11 | Hypori, Inc. | System, method and computer program product for capturing touch events for a virtual mobile device platform |
US9380523B1 (en) | 2013-01-22 | 2016-06-28 | Hypori, Inc. | System, method and computer program product for connecting roaming mobile devices to a virtual device platform |
US9380562B1 (en) | 2013-01-22 | 2016-06-28 | Hypori, Inc. | System, method and computer program product for providing notifications from a virtual device to a disconnected physical device |
US9697629B1 (en) * | 2013-01-22 | 2017-07-04 | Hypori, Inc. | System, method and computer product for user performance and device resolution settings |
US9244668B1 (en) * | 2013-02-11 | 2016-01-26 | Symantec Corporation | Systems and methods for synchronizing mobile computing platforms |
US20140289635A1 (en) * | 2013-03-22 | 2014-09-25 | Canon Kabushiki Kaisha | Information processing apparatus and method therefor |
US9954741B2 (en) * | 2013-03-22 | 2018-04-24 | Canon Kabushiki Kaisha | Information processing apparatus and method including display control of messages during printing |
US10606607B2 (en) | 2013-09-30 | 2020-03-31 | Hewlett-Packard Development Company, L.P. | Selecting operating systems based on a computing device mode |
US9778938B2 (en) | 2013-09-30 | 2017-10-03 | Hewlett-Packard Development Company, L.P. | Selecting operating systems based on a computing device mode |
US10250521B2 (en) | 2013-11-29 | 2019-04-02 | Huawei Technologies Co., Ltd. | Data stream identifying method and device |
US10254950B2 (en) | 2014-05-30 | 2019-04-09 | Huawei Technologies Co., Ltd. | Display method of terminal device and terminal device |
CN104021021A (zh) * | 2014-06-19 | 2014-09-03 | 深圳市中兴移动通信有限公司 | 移动终端及其通过压力检测实现快捷启动的方法和装置 |
US9769227B2 (en) | 2014-09-24 | 2017-09-19 | Microsoft Technology Licensing, Llc | Presentation of computing environment on multiple devices |
US10448111B2 (en) | 2014-09-24 | 2019-10-15 | Microsoft Technology Licensing, Llc | Content projection |
US9678640B2 (en) | 2014-09-24 | 2017-06-13 | Microsoft Technology Licensing, Llc | View management architecture |
US10277649B2 (en) | 2014-09-24 | 2019-04-30 | Microsoft Technology Licensing, Llc | Presentation of computing environment on multiple devices |
US10635296B2 (en) | 2014-09-24 | 2020-04-28 | Microsoft Technology Licensing, Llc | Partitioned application presentation across devices |
US9860306B2 (en) | 2014-09-24 | 2018-01-02 | Microsoft Technology Licensing, Llc | Component-specific application presentation histories |
US10824531B2 (en) | 2014-09-24 | 2020-11-03 | Microsoft Technology Licensing, Llc | Lending target device resources to host device computing environment |
US10025684B2 (en) | 2014-09-24 | 2018-07-17 | Microsoft Technology Licensing, Llc | Lending target device resources to host device computing environment |
US20180007104A1 (en) | 2014-09-24 | 2018-01-04 | Microsoft Corporation | Presentation of computing environment on multiple devices |
US11422681B2 (en) | 2014-11-06 | 2022-08-23 | Microsoft Technology Licensing, Llc | User interface for application command control |
US11126329B2 (en) | 2014-11-06 | 2021-09-21 | Microsoft Technology Licensing, Llc | Application command control for smaller screen display |
US10949075B2 (en) * | 2014-11-06 | 2021-03-16 | Microsoft Technology Licensing, Llc | Application command control for small screen display |
US10990238B2 (en) | 2015-03-03 | 2021-04-27 | Soroco Private Limited | Software robots for programmatically controlling computer programs to perform tasks |
US10585548B2 (en) | 2015-03-03 | 2020-03-10 | Soroco Private Limited | Software robots for programmatically controlling computer programs to perform tasks |
US10802662B2 (en) | 2015-03-03 | 2020-10-13 | Soroco Private Limited | Software robots for programmatically controlling computer programs to perform tasks |
US10754493B2 (en) | 2015-03-03 | 2020-08-25 | Soroco Private Limited | Software robots for programmatically controlling computer programs to perform tasks |
US20160259653A1 (en) * | 2015-03-03 | 2016-09-08 | Software Robotics Corporation Limited | Software robots for programmatically controlling computer programs to perform tasks |
US11157128B2 (en) | 2015-03-03 | 2021-10-26 | Soroco Private Limited | Software robots for programmatically controlling computer programs to perform tasks |
US10310701B2 (en) | 2015-03-03 | 2019-06-04 | Soroco Private Limited | Software robots for programmatically controlling computer programs to perform tasks |
US10671235B2 (en) * | 2015-03-03 | 2020-06-02 | Soroco Private Limited | Software robots for programmatically controlling computer programs to perform tasks |
US10983660B2 (en) | 2015-03-03 | 2021-04-20 | Soroco Private Limited | Software robots for programmatically controlling computer programs to perform tasks |
US10642442B2 (en) | 2015-03-03 | 2020-05-05 | Soroco Private Limited | Software robots for programmatically controlling computer programs to perform tasks |
US10474313B2 (en) | 2015-03-03 | 2019-11-12 | Soroco Private Limited | Software robots for programmatically controlling computer programs to perform tasks |
US20160349931A1 (en) * | 2015-05-28 | 2016-12-01 | Rockwell Automation Technologies, Inc. | Responsive user interface for an industrial environment |
US10684813B2 (en) | 2015-08-21 | 2020-06-16 | Samsung Electronics Co., Ltd. | Display device and method for controlling same |
US11372612B2 (en) | 2015-08-21 | 2022-06-28 | Samsung Electronics Co., Ltd. | Display device and method for controlling same |
CN106814961A (zh) * | 2015-12-02 | 2017-06-09 | 西安中兴新软件有限责任公司 | 一种操作方法和终端 |
US10685331B2 (en) * | 2015-12-08 | 2020-06-16 | TCL Research America Inc. | Personalized FUNC sequence scheduling method and system |
US11086494B2 (en) | 2017-02-28 | 2021-08-10 | Samsung Electronics Co., Ltd. | Electronic device and method for managing window |
US11650722B2 (en) | 2017-02-28 | 2023-05-16 | Samsung Electronics Co., Ltd. | Electronic device and method for managing window |
US10579362B1 (en) * | 2017-07-21 | 2020-03-03 | Jpmorgan Chase Bank, N.A. | Method and system for implementing an ATM phone home and scrapper mapping tool |
US10409582B1 (en) * | 2017-07-21 | 2019-09-10 | Jpmorgan Chase Bank, N.A. | Method and system for implementing a retail event management tool |
US10360010B1 (en) * | 2017-07-21 | 2019-07-23 | Jpmorgan Chase Bank, N.A. | Method and system for implementing an ATM management and software policy tool |
US11079995B1 (en) * | 2017-09-30 | 2021-08-03 | Apple Inc. | User interfaces for devices with multiple displays |
US11422765B2 (en) | 2018-07-10 | 2022-08-23 | Apple Inc. | Cross device interactions |
US11144190B2 (en) | 2019-08-06 | 2021-10-12 | Samsung Electronics Co., Ltd. | Electronic device and method for sharing data thereof |
US11972164B2 (en) | 2021-07-29 | 2024-04-30 | Apple Inc. | User interfaces for devices with multiple displays |
Also Published As
Publication number | Publication date |
---|---|
US20160077682A1 (en) | 2016-03-17 |
CN103415834B (zh) | 2018-06-05 |
CN103415834A (zh) | 2013-11-27 |
WO2013010144A2 (fr) | 2013-01-17 |
WO2013010144A3 (fr) | 2013-04-25 |
US10503344B2 (en) | 2019-12-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10503344B2 (en) | Dynamic cross-environment application configuration/orientation | |
US8966379B2 (en) | Dynamic cross-environment application configuration/orientation in an active user environment | |
US10528210B2 (en) | Foreground/background assortment of hidden windows | |
US9047102B2 (en) | Instant remote rendering | |
US9049213B2 (en) | Cross-environment user interface mirroring using remote rendering | |
US8933949B2 (en) | User interaction across cross-environment applications through an extended graphics context | |
US8819705B2 (en) | User interaction support across cross-environment applications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: Z124, CAYMAN ISLANDS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:REEVES, BRIAN;REEVES, PAUL E.;LIU, WUKE;SIGNING DATES FROM 20120920 TO 20121001;REEL/FRAME:029061/0621 |
|
AS | Assignment |
Owner name: Z124, CAYMAN ISLANDS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SUSHCHEV, BORYS;REEL/FRAME:029899/0970 Effective date: 20130117 Owner name: Z124, CAYMAN ISLANDS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SUSHCHEV, BORYS;REEL/FRAME:029899/0968 Effective date: 20130117 Owner name: Z124, CAYMAN ISLANDS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SUSHCHEV, BORYS;REEL/FRAME:029900/0077 Effective date: 20130117 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |