The present invention relates to media rendering devices, and more particularly, is related to a user interface for controlling a media rendering device.
It has become commonplace for an individual to have access to one or more devices that render media, such as an mp3 player, a car stereo, a home entertainment system, a portable computer or tablet, a gaming console, and a smart phone, among others. The rendering devices may have access to a communication network and/or the internet, and may be configured to render digital media provided over the communication network and/or the internet, for example, a digital media streaming service.
Platform based applications hosted by portable controller devices, such as a smart phone or tablet, may control one or more rendering devices. However, controlling multiple rendering devices with a single controller device may be confusing and/or cumbersome.
For example,
As shown in the first column of
As shown in the second column of
As shown in the third column of
While the above described user interface provides access to many functions, it may not be simple or intuitive to coordinate activities/functions among the various screens. Therefore, there is a need in the industry to address one or more of the abovementioned shortcomings.
Embodiments of the present invention provide a combined tablet screen drag-and-drop interface. Briefly described, the present invention is directed to a media rendering system with a media rendering device and a controller device in communication via a network. The controller has a touch screen, presenting a portrait display mode when oriented in a first position, and a landscape display mode when oriented in a second position. The portrait mode displays either a first full screen presenting a first menu, or a second full screen presenting a second menu. The landscape mode displays a landscape full screen with two side-by-side tiles including a first tile presenting the first menu and a second tile presenting the second menu. Landscape mode provides drag-and-drop functionality for menu objects among the first and second, generating configuration commands to the media rendering device.
Other systems, methods and features of the present invention will be or become apparent to one having ordinary skill in the art upon examining the following drawings and detailed description. It is intended that all such additional systems, methods, and features be included in this description, be within the scope of the present invention and protected by the accompanying claims.
The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. The drawings illustrate embodiments of the invention and, together with the description, serve to explain the principals of the invention.
The following definitions are useful for interpreting terms applied to features of the embodiments disclosed herein, and are meant only to define elements within the disclosure.
As used within this disclosure, “media” refers to audio and/or video content either stored on a storage medium, such as a disk drive or digital disk, or streamed from a media server. Media may refer to analog and/or digitally formatted data. A specific recorded performance is referred to as a media recording.
As used within this disclosure, an originating provider of media, either streamed or locally stored, is referred to as a “media source.” Examples of a media source include a music and/or video server, an internet radio station, a streaming service, or a cache of media files.
As used within this disclosure, “rendering” refers to playback of a media recording by a media player, also referred to herein as a “rendering device.” Examples of rendering devices include, but are not limited to, an mp3 player, a tablet computer, a portable stereo, a home entertainment system, a portable video player, a smart phone, a laptop or desktop computer, and a mobile entertainment system. A rendering device generally has at least one audio transducer (speaker) used to render the media audio portion.
As used within this disclosure, a “controller” refers to a hand held device or an application running on a hand held device configured to interact with a media rendering device. The controller may interact with the media rendering device by issuing commands to adjust one or more operating parameters on the media rendering device, and/or to display operational status of the media rendering device. Examples of a hand held device include a smart phone or tablet computer.
As used within this disclosure, a “user” refers to a person consuming media from a media rendering device, and/or a person operating a controller for the media rendering device.
As used within this disclosure, “cue point” refers a playback time location in a rendered media recording.
As used within this disclosure, “portrait mode” refers to an operation configuration of a controller device corresponding to orientation of a display screen where the top and bottom edges of the display screen are shorter than the side edges.
As used within this disclosure, “landscape mode” refers to an operation configuration of a controller device corresponding to orientation of a display screen where the top and bottom edges of the display screen are longer than the side edges. In both portrait and landscape mode, text on the display is generally arranged to be oriented with respect to the top edge of the screen.
As used within this disclosure, a local device, such as a server, refers to a network element directly connected to a local area network (LAN), while a remote device refers to an item that may be in communication with local network elements, for example, via the internet, but is not directly connected to the LAN. Examples of a LAN include a wireless (WiFi) LAN or a wired LAN, for example, connected via Ethernet cables.
As used within this disclosure, a “playlist” is a modifiable data structure containing an ordered list of media, or an ordered list of references to media. A playlist may be stored, for example, on a rendering device or a server, or within a storage medium, such as a hard drive, thumb drive, or optical disc. A playlist may be modified to add, remove, and/or re-order media or media references. Since playlists containing media references do not contain audio or video content, they are generally small in size and therefore readily transportable. A display playlist is a text listing of media in a playlist, and may include a subset of identifying parameters of a media, such as title, artist, duration, and date, among others. A play queue refers to a playlist that is currently being rendered by a rendering device. The head of the play queue refers to the next media file to be rendered after the currently rendered media recording, while the tail of the play queue refers to the location of the play queue indicating the final media in the play queue to be rendered.
As used within this disclosure, “streaming” refers to a process of real-time transmitting of a media recording by a source to a rendering device. The rendering device may begin rendering the media before the entire recording has been transmitted. Streaming is generally transitory, such that the streamed data is not retained after it has been rendered. Portions of a received stream may be buffered for rendering, for example, to ensure rendering is uninterrupted during short interruptions of the streamed transmission. In contrast, a downloaded digital multimedia file is generally received in its entirety before it may be rendered. A downloaded digital multimedia file is generally retained in a memory for subsequent rendering, while a streamed file is generally re-streamed for subsequent renderings. “Streaming a song” is shorthand for streaming audio media.
As used within this disclosure, “GUI” is a graphical user interface, and in particular, may be a touch-screen interface. A graphical user interface or GUI, sometimes pronounced /'gu:i/ (“gooey”) is a type of interface that allows users to interact with electronic devices through graphical icons and visual indicators such as secondary notation, referred to herein as “objects,” as opposed to text-based interfaces, typed command labels or text navigation. An ordered list of objects in a GUI may be referred to as a “menu.” Menus may be stationary, may drop down from top of the display (a “drop-down menu”), or may pop up to fill the screen or a portion of the screen when an object is selected (a “pop-up menu”). The actions in a GUI are usually performed through direct manipulation of the objects. As used herein, “selecting” refers to touching an object, for example with a finger or stylus. A “drag-and-drop” operation refers to selecting a first object with a touch of the touchscreen, and moving the finger/stylus from the first object to another location (often with a ghost or outline of the object tracking the movement) corresponding to a second object. The second object may become highlighted when the ghost is dragged over it, indicating the second object is able to “receive” the first object. The drag-and-drop operation may be thought of providing the dragged object as an input to the second object. The operation resulting from the drag-and-drop operation is generally generation of a command to a media rendering device controlled by the controller, the scope of which may depend upon context or the mode of the display during the operation.
An object refers to an item represented by a graphical icon or visual indicator, for example, a media source, a media file, or a media rendering device.
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the description to refer to the same or like parts.
Each of the five media rendering devices 111-115 may be in communication with one or more controllers (not shown) via the LAN 160. Alternatively, a control panel on one or more of the media rendering devices 111-115 may serve as a controller for all of the media rendering devices 111-115. The media rendering devices 111-115 may be individually controlled, or two or more rendering devices 111-115 may be linked so that they may operate under common control.
As described above, navigating multiple control screens in a controller application may be cumbersome. There are advantages provided by combining the content of two or more of these screens. For example, while a single screen may be displayed in portrait orientation, two or more screens may be displayed as side-by-side tiles 250, 260, 270 in landscape orientation, as shown in
As shown in
The very top of the interface 200 generally includes a system bar 202. The system bar is displayed in both landscape orientation and portrait orientation. In general, the system bar 202 may be configured by an operating system of the controller, and may include text and/or icons indicating the network and/or cell signal strength, time of day, and battery level, among others. Hereinafter, references to the top of the screen refer to the top of the display interface 200 below the system bar 202. Further, since the user interface for the controller includes a touch sensitive display screen, the interface 200 may be interchangeably referred to as the interface, display screen, touch screen, display, or screen.
In portrait orientation, the interface 200 may be configured substantially according to the earlier description of the interface of a prior art controller as shown in
A second tab in portrait orientation may select a second view, for example, a menu listing media sources, such as a playlist stored on the device, a broadcast playlist, or a streamed or broadcast media. Other media sources may include playlists stored on other devices available to the network 160 (
A third tab in portrait orientation brings up a third view, for example, a “now playing” view, indicating media currently playing in the target room. The now playing view may show an image associated with the playing media, such as an album cover. The now playing view may also display media rendering (playback) controls, such as a volume control, and transport controls, such as play, pause, replay, and skip backward/forward. Other rendering controls may include tone controls (bass, mid, treble) and/or balance. The user may display the current play queue, for example, by selecting the image or swiping downward on the now playing view display. The play queue may be edited from the now play queue screen, for example, deleting media from the play queue or adding media to the play queue.
In the landscape orientation, as shown by
In general, the second tile 260 presents similar information to the information presented in the music tab of portrait orientation, and may therefore be referred to herein as the music tile 260. Since the music tile 260 occupies approximately one third of the screen area in landscape orientation as the music tab in the portrait orientation, the information presented in the music tile 260 may be reduced in comparison with the portrait orientation music tab, for example, by reducing the number of sources listed. Like the music tab, the music tile 260 may be switched, for example by swiping the screen or selecting a media source, between a top level menu displaying a list of music sources, and a track level browsing view, displaying a list of tracks in the playlist of the selected media source.
In general, the third tile 270 presents similar information to the information presented in the now playing tab of portrait orientation, and may therefore be referred to herein as the now playing tile 270. Since the now playing tile 270 occupies approximately one third or less of the screen area in landscape orientation as the now playing tab in the portrait orientation, the information presented in the now playing tile 270 may be reduced in comparison with the portrait orientation now playing tab, for example, by reducing the number of sources listed. Like the now playing tab, the now playing tile 260 may be switched, for example by swiping or selecting a track, between a top level menu displaying information of the track corresponding to the media currently being rendered, to a play queue, displaying an ordered list of tracks in a queue for rendering. Each of the first tile 250, second tile 260, and the third tile 270 may be scrollable, to facilitate display of lists longer than may be feasible to be shown in their entirety in the available space.
Unlike the first tile 250 and second tile 260, the third tile 270 may not extend fully from the bottom of the screen to the system bar 202. Instead, the top portion of the third tile 270 may be displaced somewhat by a sub-menu, here a tool pallet 280. The tool pallet 280 may display one or more objects to assist the user in manipulating one or more of the tiles 250, 260, 270. For example, the tool pallet 280 may include an edit icon 281, a delete icon 282, and a favorites icon 283, among other icons. The edit icon 281 allows the user to mark and reorder one or more items. The delete icon 282 allows the user to clear only the marked items or delete the whole list at once (without having to mark many items). The form of an icon in the tool pallet 280 may change according to a context of the action. For example, the appearance of the edit icon 281 may change from a pencil to a check mark to allow the user to save edits that have been made.
The delete icon 282 may be used to remove an item from one of the tiles, for example, by dragging an object over the delete icon 282. The favorites icon 283 may act as a “Save as a Play list” button that lets the user save the contents of a list into a playlist for later recall. This saves the user from having to manually recreate the order of songs currently in the list. In alternative embodiments, the tool pallet 280 may be in the first tile 250 or second tile 260, or may be available as a pop-up menu. The tiles 250, 260, 270 may also contain other sub-menus.
In the first embodiment, the tiles 250, 260, 270 may be arranged to be hierarchical, where the first tile 250 represents a high level of objects, the second tile 260 represents a middle level of objects, and the third tile 270 represents a low level of objects, such that the high level objects may be considered to include the middle level objects, and the middle level object may be considered to include the low level objects. For example, a media player in a room may be represented by an object in the first tile 250, and be considered to include a playlist represented by an object in the second tile 260. While it may be desirable in some embodiments to arrange the tiles in a hierarchical fashion, alternative embodiments may adopt different arrangements.
In contrast to portrait mode, where the content of only one menu is presented at a time, in landscape mode the user may drag-and-drop objects from one menu to another by dragging an object from one tile to another. For example, as shown in
In another example, as shown in
As with the music tab in portrait mode, the music tile 260 may be switched between a top level menu and one or more lower level menus, for example, by selecting a media source in the top level menu, which will then populate the music tile 260 with the playlist for the media source.
Other drag-and-drop actions are also possible. For example, the play queue in the now playing tile 270 may be dragged to a room in the room tile 250, causing the media rendering device 111-115 (
A graphical user interface is provided on a display portion 200 of the touch screen, as shown by block 610. For example, the touch screen may be part of a tablet computer or smart mobile telephone or wearable computing device. The display portion 200 of the touch screen may be presented in a portrait mode, as shown by block 620. In portrait mode, a first menu, a second menu, or a third menu may be presented. A first full screen with a first menu of first objects is presented, as shown by block 630. A second menu with a second full screen of second objects is presented, as shown by block 632. A third menu with a third full screen of third objects is presented, as shown by block 634. When in portrait mode, the first menu, the second menu, and the third menu are not displayed concurrently. Instead, only the menu corresponding to the presently selected tab 205 is displayed. For example, in portrait mode a tab bar 205 may be displayed with which the user may select which of the first menu, the second menu, or the third menu to display.
The display portion 200 of the touch screen may be presented in a landscape mode, as shown by block 640. In the landscape mode, a fourth full screen is presented having three side-by-side tiles 250, 260, 270 substantially filling the fourth full screen, as shown by block 650. A first tile 250 is presented with the first menu of the first objects, as shown by block 652. A second tile 260 is presented with the second menu of the second objects, as shown by block 654. A third tile is presented with the third menu of the third objects, as shown by block 656. Drag-and-drop operation functionality is provided for the first, second, and third objects among the first, second, and third tiles, as shown by block 660. In particular, the landscape mode facilitates drag-and-drop functionality between the first, second, and third menus, which is not feasible in portrait mode, where the first, second, and third menus are not simultaneously displayed. A configuration command is generated to a media rendering device 111-115 as a result of a drag-and-drop operation, as shown by block 670. For example, dragging a track object to a room object may result in a media rendering device 111-115 located in a room 101-105 represented by the room object to render a media file represented by the track object.
The portrait mode is displayed when the touch screen is oriented in a first position, as shown by block 680. For example, the portrait mode is displayed when one of the two shorter edges of the touch-screen is oriented topmost. The landscape mode is displayed when the touch screen is oriented in a second position, as shown by block 690. For example, the landscape mode is displayed when one of the two longer edges of the touch-screen is oriented topmost.
As previously mentioned, the present system for executing the functionality described in detail above may be a computer, an example of which is shown in the schematic diagram of
The processor 502 is a hardware device for executing software, particularly that stored in the memory 506. The processor 502 can be any custom made or commercially available single core or multi-core processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the present system 500, a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, or generally any device for executing software instructions.
The memory 506 can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, the memory 506 may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory 506 can have a distributed architecture, where various components are situated remotely from one another, but can be accessed by the processor 502.
The software 508 defines functionality performed by the system 500, in accordance with the present invention. The software 508 in the memory 506 may include one or more separate programs, each of which contains an ordered listing of executable instructions for implementing logical functions of the system 500, as described below. The memory 506 may contain an operating system (O/S) 520. The operating system essentially controls the execution of programs within the system 500 and provides scheduling, input-output control, file and data management, memory management, and communication control and related services.
The I/O devices 510 may include input devices, for example but not limited to, a touchscreen surface, a keyboard, mouse, scanner, microphone, etc. Furthermore, the I/O devices 510 may also include output devices, for example but not limited to, a printer, a touchscreen display, etc. Finally, the I/O devices 510 may further include devices that communicate via both inputs and outputs, for instance but not limited to, a modulator/demodulator (modem; for accessing another device, system, or network), a WiFi or other transceiver, a telephonic interface, a bridge, a router, or other device.
When the system 500 is in operation, the processor 502 is configured to execute the software 508 stored within the memory 506, to communicate data to and from the memory 506, and to generally control operations of the system 500 pursuant to the software 508, as explained above.
When the functionality of the system 500 is in operation, the processor 502 is configured to execute the software 508 stored within the memory 506, to communicate data to and from the memory 506, and to generally control operations of the system 500 pursuant to the software 508. The operating system 520 is read by the processor 502, perhaps buffered within the processor 502, and then executed.
When the system 500 is implemented in software 508, it should be noted that instructions for implementing the system 500 can be stored on any computer-readable medium for use by or in connection with any computer-related device, system, or method. Such a computer-readable medium may, in some embodiments, correspond to either or both the memory 506 or the storage device 504. In the context of this document, a computer-readable medium is an electronic, magnetic, optical, or other physical device or means that can contain or store a computer program for use by or in connection with a computer-related device, system, or method. Instructions for implementing the system can be embodied in any computer-readable medium for use by or in connection with the processor or other such instruction execution system, apparatus, or device. Although the processor 502 has been mentioned by way of example, such instruction execution system, apparatus, or device may, in some embodiments, be any computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can store, communicate, propagate, or transport the program for use by or in connection with the processor or other such instruction execution system, apparatus, or device.
Such a computer-readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a nonexhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM, EEPROM, or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). Note that the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
In an alternative embodiment, where the system 500 is implemented in hardware, the system 500 can be implemented with any or a combination of the following technologies, which are each well known in the art: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.
While the embodiments above have described a landscape mode with three side-by-side tiles, in alternative embodiments the landscape mode may include two, four or more side-by-side tiles.
It will be apparent to those skilled in the art that various modifications and variations can be made to the structure of the present invention without departing from the scope or spirit of the invention. In view of the foregoing, it is intended that the present invention cover modifications and variations of this invention provided they fall within the scope of the following claims and their equivalents.
Number | Name | Date | Kind |
---|---|---|---|
5487143 | Southgate | Jan 1996 | A |
5838384 | Schindler et al. | Nov 1998 | A |
6359656 | Huckins | Mar 2002 | B1 |
6650963 | DiLorenzo | Nov 2003 | B2 |
6934740 | Lawande | Aug 2005 | B1 |
6976062 | Ostermann | Dec 2005 | B1 |
7119266 | Bittner | Oct 2006 | B1 |
7130608 | Hollstrom | Oct 2006 | B2 |
7130616 | Janik | Oct 2006 | B2 |
7149549 | Ortiz et al. | Dec 2006 | B1 |
7313540 | Hueler | Dec 2007 | B1 |
7337409 | Doblmayr | Feb 2008 | B2 |
7373414 | Evron et al. | May 2008 | B2 |
7412060 | Fukuda | Aug 2008 | B2 |
7571014 | Lamboume | Aug 2009 | B1 |
7574691 | Freitas et al. | Aug 2009 | B2 |
7630501 | Blank et al. | Dec 2009 | B2 |
7689510 | Lamkin et al. | Mar 2010 | B2 |
7791594 | Bunko | Sep 2010 | B2 |
7792311 | Holmgren et al. | Sep 2010 | B1 |
7978176 | Forstall et al. | Jul 2011 | B2 |
8095191 | Gorsica | Jan 2012 | B2 |
8111132 | Allen et al. | Feb 2012 | B2 |
8116476 | Inohara | Feb 2012 | B2 |
8131389 | Hardwick et al. | Mar 2012 | B1 |
8214447 | Deslippe et al. | Jul 2012 | B2 |
8239910 | Anderson, Jr. et al. | Aug 2012 | B2 |
8243949 | Bhow et al. | Aug 2012 | B2 |
8245143 | Yach et al. | Aug 2012 | B2 |
8266550 | Cleron | Sep 2012 | B1 |
8290172 | Langelle | Oct 2012 | B2 |
8290603 | Lambourne | Oct 2012 | B1 |
8368723 | Gossweiler, III | Feb 2013 | B1 |
8724600 | Ramsey | May 2014 | B2 |
8769431 | Prasad | Jul 2014 | B1 |
8788080 | Kallai et al. | Jul 2014 | B1 |
8812051 | Jouin | Aug 2014 | B2 |
8832823 | Boss et al. | Sep 2014 | B2 |
8887071 | Yang | Nov 2014 | B2 |
9001047 | Forstall | Apr 2015 | B2 |
9104301 | Kim | Aug 2015 | B2 |
9239662 | Matas | Jan 2016 | B2 |
9288596 | Gossain | Mar 2016 | B2 |
9311426 | Stovicek | Apr 2016 | B2 |
9342234 | Kobayashi | May 2016 | B2 |
9395871 | Marra | Jul 2016 | B2 |
9504076 | El-Hoiydi | Nov 2016 | B2 |
9640158 | Baker | May 2017 | B1 |
9654073 | Apodaca | May 2017 | B2 |
9671997 | Triplet | Jun 2017 | B2 |
9703471 | Wachter | Jul 2017 | B2 |
9996161 | Le Grand | Jun 2018 | B2 |
9999091 | Wachter | Jun 2018 | B2 |
10051103 | Gordon | Aug 2018 | B1 |
10055108 | Bates | Aug 2018 | B2 |
20020003548 | Krusche et al. | Jan 2002 | A1 |
20020055788 | Petrie et al. | May 2002 | A1 |
20020101997 | Curtis et al. | Aug 2002 | A1 |
20020133327 | McGrath | Sep 2002 | A1 |
20020170061 | DiLorenzo | Nov 2002 | A1 |
20030020763 | Mayer et al. | Jan 2003 | A1 |
20030029918 | Leanheart et al. | Feb 2003 | A1 |
20030161292 | Silvester | Aug 2003 | A1 |
20030208300 | DiLorenzo | Nov 2003 | A1 |
20040066414 | Czerwinski | Apr 2004 | A1 |
20040162025 | Plummer | Aug 2004 | A1 |
20050094610 | De Clerq et al. | May 2005 | A1 |
20050111672 | Chen | May 2005 | A1 |
20050195986 | McCarty et al. | Sep 2005 | A1 |
20050262201 | Rudolph et al. | Nov 2005 | A1 |
20060258419 | Winkler | Nov 2006 | A1 |
20060281477 | Downes | Dec 2006 | A1 |
20070022207 | Millington | Jan 2007 | A1 |
20070162953 | Bolliger | Jul 2007 | A1 |
20070223398 | Luo et al. | Sep 2007 | A1 |
20070297459 | Cucos et al. | Dec 2007 | A1 |
20080010648 | Ando et al. | Jan 2008 | A1 |
20080092204 | Bryce et al. | Apr 2008 | A1 |
20080165153 | Platzer | Jul 2008 | A1 |
20080215959 | Lection | Sep 2008 | A1 |
20080222295 | Robinson et al. | Sep 2008 | A1 |
20080271080 | Gossweiler | Oct 2008 | A1 |
20080282158 | Aaltonen | Nov 2008 | A1 |
20080313568 | Park et al. | Dec 2008 | A1 |
20090002335 | Chaudhri | Jan 2009 | A1 |
20090094317 | Venkitaraman | Apr 2009 | A1 |
20090169030 | Inohara | Jul 2009 | A1 |
20090171487 | Wilhelm | Jul 2009 | A1 |
20090172542 | Girish et al. | Jul 2009 | A1 |
20090187842 | Collins et al. | Jul 2009 | A1 |
20090191854 | Beason | Jul 2009 | A1 |
20090228919 | Zott et al. | Sep 2009 | A1 |
20090254861 | Seetharamakrishnan | Oct 2009 | A1 |
20090258598 | Shin et al. | Oct 2009 | A1 |
20100058168 | Shah et al. | Mar 2010 | A1 |
20100088590 | Bajohr | Apr 2010 | A1 |
20100088639 | Yach | Apr 2010 | A1 |
20100121919 | Hepworth et al. | May 2010 | A1 |
20100131869 | Adachi | May 2010 | A1 |
20100138782 | Rainisto | Jun 2010 | A1 |
20100216515 | White | Aug 2010 | A1 |
20100240390 | Russ | Sep 2010 | A1 |
20100259547 | de Aguiar | Oct 2010 | A1 |
20100260348 | Bhow et al. | Oct 2010 | A1 |
20100272270 | Chaikin | Oct 2010 | A1 |
20100284389 | Ramsay et al. | Nov 2010 | A1 |
20100299639 | Ramsay | Nov 2010 | A1 |
20100318917 | Holladay et al. | Dec 2010 | A1 |
20100325211 | Ylinen | Dec 2010 | A1 |
20110004517 | Soto | Jan 2011 | A1 |
20110028083 | Soitis | Feb 2011 | A1 |
20110041086 | Kim | Feb 2011 | A1 |
20110074710 | Weeldreyer | Mar 2011 | A1 |
20110211219 | Bradley et al. | Sep 2011 | A1 |
20110225539 | Lee | Sep 2011 | A1 |
20120032981 | Hackwell | Feb 2012 | A1 |
20120051560 | Sanders | Mar 2012 | A1 |
20120054143 | Doig | Mar 2012 | A1 |
20120057725 | Nakamura | Mar 2012 | A1 |
20120072853 | Krigstrom | Mar 2012 | A1 |
20120084712 | Gimpl | Apr 2012 | A1 |
20120099594 | Lau et al. | Apr 2012 | A1 |
20120113224 | Nguyen et al. | May 2012 | A1 |
20120117598 | Pons et al. | May 2012 | A1 |
20120190386 | Anderson | Jul 2012 | A1 |
20120192070 | De Faria et al. | Jul 2012 | A1 |
20120240055 | Webber | Sep 2012 | A1 |
20120262489 | Caliendo, Jr. | Oct 2012 | A1 |
20120263318 | Millington | Oct 2012 | A1 |
20120269361 | Bhow et al. | Oct 2012 | A1 |
20120290965 | Ignor | Nov 2012 | A1 |
20120310703 | Cavalcanti et al. | Dec 2012 | A1 |
20130002568 | Selim | Jan 2013 | A1 |
20130030892 | Liu | Jan 2013 | A1 |
20130073932 | Migos | Mar 2013 | A1 |
20130076651 | Reimann et al. | Mar 2013 | A1 |
20130080955 | Reimann | Mar 2013 | A1 |
20130080966 | Kikin-Gil | Mar 2013 | A1 |
20130089026 | Piper et al. | Apr 2013 | A1 |
20130109928 | Menzel | May 2013 | A1 |
20130154950 | Kvasnica | Jun 2013 | A1 |
20130159928 | Joynes | Jun 2013 | A1 |
20130173794 | Agerbak et al. | Jul 2013 | A1 |
20130187861 | Lavallee | Jul 2013 | A1 |
20130231044 | Wang | Sep 2013 | A1 |
20130238724 | Cunningham | Sep 2013 | A1 |
20130246916 | Reimann | Sep 2013 | A1 |
20130265235 | Cai | Oct 2013 | A1 |
20130275901 | Saas et al. | Oct 2013 | A1 |
20130290888 | Reimann et al. | Oct 2013 | A1 |
20130305152 | Griffiths et al. | Nov 2013 | A1 |
20130311912 | Aso | Nov 2013 | A1 |
20130321340 | Seo | Dec 2013 | A1 |
20130334300 | Evans | Dec 2013 | A1 |
20130339907 | Matas | Dec 2013 | A1 |
20130340003 | Davis et al. | Dec 2013 | A1 |
20140009676 | Cannistraro | Jan 2014 | A1 |
20140013254 | Hosein | Jan 2014 | A1 |
20140022285 | Stovicek | Jan 2014 | A1 |
20140026088 | Monte | Jan 2014 | A1 |
20140047487 | Guedalia et al. | Feb 2014 | A1 |
20140057569 | Toivanen et al. | Feb 2014 | A1 |
20140064492 | Lakkundi | Mar 2014 | A1 |
20140068475 | Li | Mar 2014 | A1 |
20140072270 | Goldberg | Mar 2014 | A1 |
20140075394 | Nawle | Mar 2014 | A1 |
20140078178 | Li | Mar 2014 | A1 |
20140089832 | Kim | Mar 2014 | A1 |
20140096002 | Dey | Apr 2014 | A1 |
20140154983 | Schultz et al. | Jun 2014 | A1 |
20140157166 | Choi | Jun 2014 | A1 |
20140169569 | Toivanen et al. | Jun 2014 | A1 |
20140181654 | Kumar et al. | Jun 2014 | A1 |
20140193047 | Grosz | Jul 2014 | A1 |
20140195921 | Grosz | Jul 2014 | A1 |
20140195953 | Sakai | Jul 2014 | A1 |
20140201635 | Kumar | Jul 2014 | A1 |
20140210860 | Caissy | Jul 2014 | A1 |
20140213372 | Liang | Jul 2014 | A1 |
20140219483 | Hong | Aug 2014 | A1 |
20140229959 | Beckhardt et al. | Aug 2014 | A1 |
20140242913 | Pang | Aug 2014 | A1 |
20140270235 | Shin et al. | Sep 2014 | A1 |
20140270306 | Luna et al. | Sep 2014 | A1 |
20140274185 | Luna et al. | Sep 2014 | A1 |
20140279889 | Luna | Sep 2014 | A1 |
20140283136 | Dougherty et al. | Sep 2014 | A1 |
20140289597 | Kim | Sep 2014 | A1 |
20140289642 | Prasad | Sep 2014 | A1 |
20140310597 | Triplett et al. | Oct 2014 | A1 |
20140334644 | Selig et al. | Nov 2014 | A1 |
20140359496 | Cammarata | Dec 2014 | A1 |
20140368441 | Touloumlzis | Dec 2014 | A1 |
20140368547 | Elings | Dec 2014 | A1 |
20140370817 | Luna | Dec 2014 | A1 |
20140380159 | Reilly et al. | Dec 2014 | A1 |
20140380219 | Cartan | Dec 2014 | A1 |
26140356389 | Reunamaki | Dec 2014 | |
20150022558 | Li | Jan 2015 | A1 |
20150025661 | Vega-Zayas et al. | Jan 2015 | A1 |
20150045000 | Kim | Feb 2015 | A1 |
20150086045 | Millington et al. | Mar 2015 | A1 |
20150091708 | Tan et al. | Apr 2015 | A1 |
20150094120 | Suh | Apr 2015 | A1 |
20150116218 | Yang | Apr 2015 | A1 |
20150161141 | Evans | Jun 2015 | A1 |
20150181010 | Bran | Jun 2015 | A1 |
20150192940 | Silva et al. | Jul 2015 | A1 |
20150193135 | Kim | Jul 2015 | A1 |
20150195649 | Vogt | Jul 2015 | A1 |
20150256957 | Kim et al. | Sep 2015 | A1 |
20150262396 | Devarajan | Sep 2015 | A1 |
20150286360 | Wachter | Oct 2015 | A1 |
20150293655 | Tan | Oct 2015 | A1 |
20160026371 | Lu | Jan 2016 | A1 |
20160026428 | Morganstern et al. | Jan 2016 | A1 |
20160103586 | Greenberg | Apr 2016 | A1 |
20160117072 | Sharifi | Apr 2016 | A1 |
20160124635 | Covington | May 2016 | A1 |
20160162127 | Sepulveda | Jun 2016 | A1 |
20160328789 | Grosz | Nov 2016 | A1 |
20160335041 | Wachter | Nov 2016 | A1 |
20170060374 | Murrells et al. | Mar 2017 | A1 |
20170272860 | Ludovic | Sep 2017 | A1 |
20170351900 | Lee | Dec 2017 | A1 |
20170357317 | Chaudhri | Dec 2017 | A1 |
20170357437 | Peterson | Dec 2017 | A1 |
20170357477 | Im et al. | Dec 2017 | A1 |
20180032997 | Gordon | Feb 2018 | A1 |
20180136898 | Shi et al. | May 2018 | A1 |
20180255398 | Fischer et al. | Sep 2018 | A1 |
20190163339 | Zhu | May 2019 | A1 |
20200242298 | Allen | Jul 2020 | A1 |
Number | Date | Country |
---|---|---|
2014074089 | May 2014 | WO |
2014094877 | Jun 2014 | WO |
Entry |
---|
D. Raneburger, R. Popp, D. Alonso-Ríos, H. Kaind and J. Falb, “A User Study with GUIs Tailored for Smartphones and Tablet PCs,” 2013 IEEE International Conference on Systems, Man, and Cybernetics, Manchester, 2013, pp. 3727-3732, doi: 10.1109/SMC.2013.635. (Year: 2013). |
Megan Yen et al., “Portable Music Player User Interface Concepts: A Synaptics White Paper”, IP.com Prior Art Database Technical Disclosure, Jun. 2, 2005, pp. 1-32 (Year: 2005). |
Disclosed Anonymously, “Layout Profile Manager for multi-orientation screen devices”, IP.com Prior Art Database Technical Disclosure, Nov. 1, 2006, pp. 1-4 (Year: 2006). |
International Search Report and Written Opinion for PCT/US16/32092 dated Oct. 14, 2016. |
International Search Report and Written Opinion for PCT/US16/49425 dated Oct. 28, 2016. |
Cheng, et al, IrotateGrasp: automatic screen rotation based on grasp of mobile devices. Proceedings of the SIGCHI conference on Human Factors in computing Systems; 3051-3054; 2013. |
Kim et al; Huffman user interface for fill touch screen based mobile phones. Proceedings of the 12th International Conference on Advanced Communication Technology; 1021-1026; 2010. |
International Search Report for PCT/US16/31964 dated Aug. 18, 2016. |
European Search Report for application 16793488.4 dated Sep. 12, 2018. |
European Search Report for application 16793522.0 dated Sep. 12, 2018. |
Number | Date | Country | |
---|---|---|---|
20170060374 A1 | Mar 2017 | US |