U.S. patent application number 17/026574 was filed with the patent office on 2021-03-04 for mobile device cover for use with a host mobile device.
The applicant listed for this patent is STAR CO Scientific Technologies Advanced Research Co, LLC d/b/a STAR CO, STAR CO Scientific Technologies Advanced Research Co, LLC d/b/a STAR CO. Invention is credited to Thomas E. Coverstone.
Application Number | 20210067190 17/026574 |
Document ID | / |
Family ID | 1000005222151 |
Filed Date | 2021-03-04 |
View All Diagrams
United States Patent
Application |
20210067190 |
Kind Code |
A1 |
Coverstone; Thomas E. |
March 4, 2021 |
MOBILE DEVICE COVER FOR USE WITH A HOST MOBILE DEVICE
Abstract
A mobile device cover for use with a host mobile device includes
a front frame, a middle frame, and a back frame. The back frame
includes a plate or portion that can be removed and interchanged
with a second plate or portion. The second plate or portion can be
designed to look different and to provide different functionality.
For example, the plate or portion of the back frame can be replaced
with the second interchangeable plate or portion to provide a
screen that can be used by one or both of the mobile device cover
and the host mobile device.
Inventors: |
Coverstone; Thomas E.;
(Longview, TX) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
STAR CO Scientific Technologies Advanced Research Co, LLC d/b/a
STAR CO |
Longview |
TX |
US |
|
|
Family ID: |
1000005222151 |
Appl. No.: |
17/026574 |
Filed: |
September 21, 2020 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
15972970 |
May 7, 2018 |
10784916 |
|
|
17026574 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04B 1/3888 20130101;
H04M 1/0249 20130101 |
International
Class: |
H04B 1/3888 20060101
H04B001/3888; H04M 1/02 20060101 H04M001/02 |
Claims
1-20. (canceled)
21. A mobile phone cover for use with a mobile phone, comprising: a
housing configured to enclose the mobile phone, wherein a front
side of the housing comprises an opening through which a screen of
the mobile phone can be viewed; and a removable portion operably
coupled to a backside of the housing.
22. The mobile phone cover according to claim 21, wherein the
removable portion is interchangeable with a different removable
portion.
23. The mobile phone cover according to claim 21, wherein the
removable portion is configured to house circuitry to support
functionality.
24. The mobile phone cover according to claim 21, wherein the
mobile phone cover comprises circuitry, and wherein the removable
portion comprises electrical contacts configured to electrically
connect to the circuitry of the mobile phone cover.
25. The mobile phone cover according to claim 21, wherein the
mobile phone cover comprises wireless transceiver circuitry, and
wherein the removable portion is configured to wirelessly connect
to the mobile phone cover.
26. The mobile phone cover according to claim 21, wherein the
removable portion comprises a plate.
27. The mobile phone cover according to claim 26, wherein the
removable portion is interchangeable with a different removable
portion comprising a different plate with a different
appearance.
28. The mobile phone cover according to claim 21, wherein the
removable portion is interchangeable with a different removable
portion with a different physical shape or size.
29. The mobile phone cover according to claim 21, wherein the
removable portion forms part of an external side of the
housing.
30. The mobile phone cover according to claim 21, wherein the
removable portion is magnetically secured to the housing.
31. The mobile phone cover according to claim 21, wherein the
removable portion comprises an output device that can be used by
one or both of the mobile phone cover and the mobile device.
32. The mobile phone cover according to claim 21, wherein the
removable portion comprises a screen.
33. The mobile phone cover according to claim 21, wherein the
removable portion comprises a projector.
34. The mobile phone cover according to claim 21, wherein the
housing comprises a plurality of connected frames.
35. A mobile device comprising: a mobile phone; a mobile phone
cover configured to enclose the mobile phone, wherein a front side
of the housing comprises an opening through which a screen of the
mobile phone can be viewed; and a removable portion operably
coupled to a backside of the mobile phone cover, wherein the
removable portion comprises circuitry operably coupled to the
mobile phone.
36. The mobile device according to claim 35, wherein the removable
portion is wirelessly coupled to the mobile phone.
37. The mobile device according to claim 35, wherein the removable
portion comprises a display.
38. The mobile device according to claim 35, wherein the removable
portion comprises a projector.
39. The mobile device according to claim 35, wherein the removable
portion is configured to be magnetically coupled to the mobile
phone cover.
40. The mobile device according to claim 35, wherein the mobile
phone cover comprises a plurality of connected frames.
Description
FIELD OF THE DISCLOSURE
[0001] Certain embodiments of the disclosure relate to systems and
methods for controlling a mobile device cover for use with a mobile
device.
BACKGROUND OF THE DISCLOSURE
[0002] Conventional mobile phone covers are passive accessories to
mobile phones. They can have static designs and can offer some
measure of protection for the mobile phone.
[0003] Further limitations and disadvantages of conventional and
traditional approaches will become apparent to one of skill in the
art, through comparison of such systems with the present disclosure
as set forth in the remainder of the present application with
reference to the drawings.
BRIEF SUMMARY OF THE DISCLOSURE
[0004] Some embodiments according to the present disclosure relate
to, for example, an active cover for an electronic device or
equipment as illustrated by and/or described in connection with at
least one of the figures, as set forth more completely in the
claims.
[0005] Various advantages, aspects and novel features of the
present disclosure, as well as details of an illustrated embodiment
thereof, will be more fully understood from the following
description and drawings.
BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS
[0006] FIG. 1A shows an exemplary mobile device cover according to
an embodiment of the present disclosure.
[0007] FIG. 1B shows a top view of an exemplary mobile device cover
according to an embodiment of the present disclosure.
[0008] FIG. 1C shows a partially exploded side perspective view of
an exemplary mobile device cover according to an embodiment of the
present disclosure.
[0009] FIG. 1D shows an exploded side perspective view of an
exemplary mobile device cover according to an embodiment of the
present disclosure.
[0010] FIG. 1E shows an exemplary mobile device cover according to
an embodiment of the present disclosure.
[0011] FIG. 1F shows a front side of a front portion of an
exemplary mobile device cover according to an embodiment of the
present disclosure.
[0012] FIG. 1G shows a front side of a middle portion of an
exemplary mobile device cover according to an embodiment of the
present disclosure.
[0013] FIG. 2 shows an exemplary circuit arrangement according to
an embodiment of the present disclosure.
[0014] FIG. 3 shows an exemplary launch screen page of a mobile
application according to an embodiment of the present
disclosure.
[0015] FIG. 4 shows an exemplary front page of a mobile application
according to an embodiment of the present disclosure.
[0016] FIG. 5 shows an exemplary connection page of a mobile
application according to an embodiment of the present
disclosure.
[0017] FIG. 6 shows an exemplary instructions page of a mobile
application according to an embodiment of the present
disclosure.
[0018] FIG. 7 shows an exemplary home page of a mobile application
according to an embodiment of the present disclosure.
[0019] FIG. 8 shows an exemplary lightshows page of a mobile
application according to an embodiment of the present
disclosure.
[0020] FIG. 9 shows an exemplary assigned contacts page of a mobile
application according to an embodiment of the present
disclosure.
[0021] FIG. 10 shows an exemplary icons page of a mobile
application according to an embodiment of the present
disclosure.
[0022] FIG. 11A shows an exemplary scrolling text page of a mobile
application according to an embodiment of the present
disclosure.
[0023] FIG. 11B shows another exemplary scrolling text page of a
mobile application according to an embodiment of the present
disclosure.
[0024] FIG. 12 shows an exemplary add item page of a mobile
application according to an embodiment of the present
disclosure.
[0025] FIG. 13 shows an exemplary notifications-for-applications
page of a mobile application according to an embodiment of the
present disclosure.
[0026] FIG. 14 shows an exemplary lighting-for-contacts page of a
mobile application according to an embodiment of the present
disclosure.
[0027] FIG. 15 shows an exemplary lightshows-for-contacts page of a
mobile application according to an embodiment of the present
disclosure.
[0028] FIG. 16 shows an exemplary icons-for-contacts page of a
mobile application according to an embodiment of the present
disclosure.
[0029] FIG. 17 shows an exemplary battery page of a mobile
application according to an embodiment of the present
disclosure.
[0030] FIG. 18 shows an exemplary lighting page of a mobile
application according to an embodiment of the present
disclosure.
[0031] FIG. 19 shows an exemplary clock page of a mobile
application according to an embodiment of the present
disclosure.
[0032] FIG. 20 shows an exemplary back design page of a mobile
application according to an embodiment of the present
disclosure.
[0033] FIG. 21 shows an exemplary settings page of a mobile
application according to an embodiment of the present
disclosure.
[0034] FIG. 22 shows an exemplary notifications-for-applications
settings page of a mobile application according to an embodiment of
the present disclosure.
[0035] FIG. 23 shows an exemplary lightshows-for-contacts settings
page of a mobile application according to an embodiment of the
present disclosure.
[0036] FIG. 24 shows an exemplary synchronization/reset page of a
mobile application according to an embodiment of the present
disclosure.
[0037] FIG. 25A shows an exemplary preview as a portion of an
exemplary page of a mobile application according to an embodiment
of the present disclosure.
[0038] FIG. 25B shows an exemplary preview page of a mobile
application according to an embodiment of the present
disclosure.
[0039] FIG. 25C shows an exemplary preview on a mobile device cover
according to an embodiment of the present disclosure.
[0040] FIG. 25D shows an exemplary preview on a mobile device cover
according to an embodiment of the present disclosure.
[0041] FIG. 25E shows an exemplary preview on a mobile device cover
according to an embodiment of the present disclosure.
[0042] FIG. 26 shows a front view of an exemplary middle frame of a
mobile device cover according to an embodiment of the present
disclosure.
[0043] FIG. 27 shows a back view of an exemplary middle frame of a
mobile device cover according to an embodiment of the present
disclosure.
[0044] FIG. 28 shows a side view of an exemplary middle frame of a
mobile device cover according to an embodiment of the present
disclosure.
[0045] FIG. 29 shows a perspective view of an exemplary middle
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0046] FIG. 30 shows a front view of an exemplary front frame of a
mobile device cover according to an embodiment of the present
disclosure.
[0047] FIG. 31 shows a back view of an exemplary front frame of a
mobile device cover according to an embodiment of the present
disclosure.
[0048] FIG. 32 shows a side view of an exemplary front frame of a
mobile device cover according to an embodiment of the present
disclosure.
[0049] FIG. 33 shows a perspective view of an exemplary front frame
of a mobile device cover according to an embodiment of the present
disclosure.
[0050] FIG. 34 shows a front view of an exemplary back frame of a
mobile device cover according to an embodiment of the present
disclosure.
[0051] FIG. 35 shows a back view of an exemplary back frame of a
mobile device cover according to an embodiment of the present
disclosure.
[0052] FIG. 36 shows a side view of an exemplary back frame of a
mobile device cover according to an embodiment of the present
disclosure.
[0053] FIG. 37 shows a perspective view of an exemplary back frame
of a mobile device cover according to an embodiment of the present
disclosure.
[0054] FIG. 38 shows a front view of an exemplary button structure
of a mobile device cover according to an embodiment of the present
disclosure.
[0055] FIG. 39 shows a back view of an exemplary button structure
of a mobile device cover according to an embodiment of the present
disclosure.
[0056] FIG. 40 shows a side view of an exemplary button structure
of a mobile device cover according to an embodiment of the present
disclosure.
[0057] FIG. 41 shows a perspective view of an exemplary button
structure of a mobile device cover according to an embodiment of
the present disclosure.
[0058] FIG. 42 shows a perspective view of an exemplary middle
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0059] FIG. 43 shows an exemplary cushion disposed in an exemplary
middle frame of a mobile device cover according to an embodiment of
the present disclosure.
[0060] FIG. 44 shows an exemplary host mobile device disposed in an
exemplary middle frame of a mobile device cover according to an
embodiment of the present disclosure.
[0061] FIG. 45 shows an exemplary front frame mounted on an
exemplary middle frame of a mobile device cover according to an
embodiment of the present disclosure.
[0062] FIG. 46 shows an exemplary port connector disposed in an
exemplary middle frame of a mobile device cover according to an
embodiment of the present disclosure.
[0063] FIG. 47 shows an exemplary first screw screwed in an
exemplary middle frame of a mobile device cover according to an
embodiment of the present disclosure.
[0064] FIG. 48 shows an exemplary second screw screwed in an
exemplary middle frame of a mobile device cover according to an
embodiment of the present disclosure.
[0065] FIG. 49 shows an exemplary battery disposed in an exemplary
middle frame of a mobile device cover according to an embodiment of
the present disclosure.
[0066] FIG. 50 shows exemplary wires of an exemplary battery
disposed in an exemplary middle frame of a mobile device cover
according to an embodiment of the present disclosure.
[0067] FIG. 51 shows exemplary wires of an exemplary port connector
disposed in an exemplary middle frame of a mobile device cover
according to an embodiment of the present disclosure.
[0068] FIG. 52 shows an exemplary printed circuit board mounted
over the exemplary battery in an exemplary middle frame of a mobile
device cover according to an embodiment of the present
disclosure.
[0069] FIG. 53 shows an exemplary printed circuit board mounted
over the exemplary battery by an exemplary first screw in an
exemplary middle frame of a mobile device cover according to an
embodiment of the present disclosure.
[0070] FIG. 54 shows an exemplary printed circuit board mounted
over the exemplary battery by an exemplary second screw in an
exemplary middle frame of a mobile device cover according to an
embodiment of the present disclosure.
[0071] FIG. 55 shows an exemplary button structure disposed in an
exemplary middle frame of a mobile device cover according to an
embodiment of the present disclosure.
[0072] FIG. 56 shows an exemplary back frame mounted on an
exemplary middle frame of a mobile device cover according to an
embodiment of the present disclosure.
[0073] FIG. 57 shows an exploded view of an exemplary mobile device
cover according to an embodiment of the present disclosure.
[0074] FIG. 58 shows an exploded view of an exemplary mobile device
cover according to an embodiment of the present disclosure.
[0075] FIG. 59 shows an exemplary USB-to-connector circuit of a
mobile device cover according to an embodiment of the present
disclosure.
[0076] FIG. 60 shows an exemplary push button circuit of a mobile
device cover according to an embodiment of the present
disclosure.
[0077] FIG. 61 shows an exemplary battery charge indicator circuit
of a mobile device cover according to an embodiment of the present
disclosure.
[0078] FIG. 62 shows an exemplary memory circuit of a mobile device
cover according to an embodiment of the present disclosure.
[0079] FIG. 63 shows an exemplary processor circuit of a mobile
device cover according to an embodiment of the present
disclosure.
[0080] FIG. 64 shows an exemplary battery management circuit of a
mobile device cover according to an embodiment of the present
disclosure.
[0081] FIG. 65 shows an exemplary power management circuit of a
mobile device cover according to an embodiment of the present
disclosure.
[0082] FIG. 66 shows an exemplary off/on and/or reset circuit of a
mobile device cover according to an embodiment of the present
disclosure.
[0083] FIG. 67 shows an exemplary clock circuit of a mobile device
cover according to an embodiment of the present disclosure.
[0084] FIG. 68 shows an exemplary Bluetooth circuit of a mobile
device cover according to an embodiment of the present
disclosure.
[0085] FIG. 69 shows an exemplary LED driver circuit of a mobile
device cover according to an embodiment of the present
disclosure.
[0086] FIG. 70A shows an exemplary LED array of a mobile device
cover according to an embodiment of the present disclosure.
[0087] FIG. 70B shows an exemplary LED array of a mobile device
cover according to an embodiment of the present disclosure.
[0088] FIG. 70C shows an exemplary LED array of a mobile device
cover according to an embodiment of the present disclosure.
[0089] FIG. 70D shows an exemplary LED array of a mobile device
cover according to an embodiment of the present disclosure.
[0090] FIG. 71 shows an exemplary multi-layer printed circuit board
of a mobile device cover according to an embodiment of the present
disclosure.
[0091] FIG. 72 shows an exemplary top layer of a multi-layer
printed circuit board of a mobile device cover according to an
embodiment of the present disclosure.
[0092] FIG. 73 shows an exemplary second layer of a multi-layer
printed circuit board of a mobile device cover according to an
embodiment of the present disclosure.
[0093] FIG. 74 shows an exemplary third layer of a multi-layer
printed circuit board of a mobile device cover according to an
embodiment of the present disclosure.
[0094] FIG. 75 shows an exemplary bottom layer of a multi-layer
printed circuit board of a mobile device cover according to an
embodiment of the present disclosure.
[0095] FIG. 76 shows an exemplary removable portion of a back frame
of a mobile device cover according to an embodiment of the present
disclosure.
[0096] FIG. 77A shows an exemplary removable portion of a back
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0097] FIG. 77B shows an exemplary removable portion of a back
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0098] FIG. 78A shows an exemplary removable portion of a back
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0099] FIG. 78B shows an exemplary removable portion of a back
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0100] FIG. 79A shows an exemplary removable portion of a back
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0101] FIG. 79B shows an exemplary removable portion of a back
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0102] FIG. 79C shows an exemplary removable portion of a back
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0103] FIG. 79D shows an exemplary removable portion of a back
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0104] FIG. 79E shows an exemplary removable portion of a back
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0105] FIG. 79F shows an exemplary removable portion of a back
frame of a mobile device cover according to an embodiment of the
present disclosure.
[0106] FIG. 80A shows an exemplary removable back frame of a mobile
device cover according to an embodiment of the present
disclosure.
[0107] FIG. 80B shows an exemplary removable back frame of a mobile
device cover according to an embodiment of the present
disclosure.
[0108] FIG. 81 shows an exemplary removable back cover of a host
mobile device according to an embodiment of the present
disclosure.
DETAILED DESCRIPTION OF THE DISCLOSURE
[0109] As utilized herein the terms "circuit" and "circuitry" refer
to physical electronic components (i.e., hardware) and any software
and/or firmware ("code") which may configure the hardware, be
executed by the hardware, and/or otherwise be associated with the
hardware. As utilized herein, "and/or" means any one or more of the
items in the list joined by "and/or". As an example, "x and/or y"
means any element of the three-element set {(x), (y), (x, y)}. As
another example, "x, y, and/or z" means any element of the
seven-element set {(x), (y), (z), (x, y), (x, z), (y, z), (x, y,
z)}. As utilized herein, the term "exemplary" means serving as a
non-limiting example, instance, or illustration. As utilized
herein, the terms "e.g.," and "for example" set off lists of one or
more non-limiting examples, instances, or illustrations.
[0110] As utilized herein the terms "circuits" and "circuitry"
refer to physical electronic components (i.e., hardware) and any
software and/or firmware ("code") that may configure the hardware,
be executed by the hardware, and or otherwise be associated with
the hardware. As used herein, for example, a particular processor
and memory (e.g., a volatile or non-volatile memory device, a
general computer-readable medium, etc.) may comprise a first
"circuit" when executing a first one or more lines of code and may
comprise a second "circuit" when executing a second one or more
lines of code. Additionally, a circuit may comprise analog and/or
digital circuitry. Such circuitry may, for example, operate on
analog and/or digital signals. It should be understood that a
circuit may be in a single device or chip, on a single motherboard,
in a single chassis, in a plurality of enclosures at a single
geographical location, in a plurality of enclosures distributed
over a plurality of geographical locations, etc. Similarly, the
term "module" may, for example, refer to a physical electronic
components (i.e., hardware) and any software and/or firmware
("code") that may configure the hardware, be executed by the
hardware, and or otherwise be associated with the hardware.
[0111] As utilized herein, circuitry is "operable" to perform a
function whenever the circuitry comprises the necessary hardware
and code (if any is necessary) to perform the function, regardless
of whether performance of the function is disabled, or not enabled
(e.g., by a user-configurable setting, factory setting or trim,
etc.).
[0112] As utilized herein, "and/or" means any one or more of the
items in the list joined by "and/or". As an example, "x and/or y"
means any element of the three-element set {(x), (y), (x, y)}. That
is, "x and/or y" means "one or both of x and y." As another
example, "x, y, and/or z" means any element of the seven-element
set {(x), (y), (z), (x, y), (x, z), (y, z), (x, y, z)}. That is,
"x, y, and/or x" means "one or more of x, y, and z." As utilized
herein, the terms "e.g.," and "for example," "exemplary," and the
like set off lists of or provide one or more non-limiting examples,
instances, or illustrations.
[0113] The terminology used herein is for the purpose of describing
particular examples only and is not intended to be limiting of the
disclosure. As used herein, the singular forms are intended to
include the plural forms as well, unless the context clearly
indicates otherwise. It will be further understood that the terms
"comprises," "includes," "comprising," "including," "has," "have,"
"having," and the like when used in this specification, specify the
presence of stated features, integers, steps, operations, elements,
and/or components, but do not preclude the presence or addition of
one or more other features, integers, steps, operations, elements,
components, and/or groups thereof.
[0114] It will be understood that, although the terms first,
second, etc. may be used herein to describe various elements, these
elements should not be limited by these terms. These terms are only
used to distinguish one element from another element. Thus, for
example, a first element, a first component or a first section
discussed below could be termed a second element, a second
component or a second section without departing from the teachings
of the present disclosure. Similarly, various spatial terms, such
as "upper," "lower," "side," and the like, may be used in
distinguishing one element from another element in a relative
manner. It should be understood, however, that components may be
oriented in different manners, for example an electronic device may
be turned sideways so that its "top" surface is facing horizontally
and its "side" surface is facing vertically, without departing from
the teachings of the present disclosure.
[0115] The drawings are of illustrative embodiments. They do not
illustrate all embodiments. Other embodiments may be used in
addition to or instead of the illustrative embodiments. Details
that may be apparent or unnecessary may be omitted to save space or
for more effective illustration. Some embodiments may be practiced
with additional components or steps and/or without all of the
components or steps that are illustrated.
[0116] Some embodiments according to the present disclosure
provide, for example, suitable logic, circuitry, code, and/or
combinations thereof that may be adapted to perform the functions
or acts described herein.
[0117] Some embodiments according to the present disclosure may
relate to, for example, systems and methods that provide an active
cover for an electronic device or equipment. Some embodiments
contemplate that the active cover and the electronic device or
equipment can communicate (e.g., digitally communicate) with each
other. Some embodiments contemplate that the active cover and the
electronic device or equipment can power themselves, for example,
via direct current (DC) power supplies (e.g., rechargeable
batteries) and/or via alternating current (AC) power supplies
(e.g., wall outlets). Some embodiments further contemplate that one
or both of the active cover and the electronic device or equipment
can power and/or recharge the other.
[0118] Some embodiments according to the present disclosure provide
that the active cover can sense when the electronic device is
generating an alert or receiving a message, a notification, a call,
an email, and/or an indication, and can provide an enhanced alert
or indication (e.g., audible and/or visual alert or indication)
instead of or in addition to the generated alert or indication of
the electronic device. The active cover can provide a visual
display (e.g., patterns of lights, animated icons, animated emojis,
lightshows, scrolling text, video, etc.), display information
(e.g., a message, a notification, and/or an indication) received
from the electronic device on a graphical user interface (e.g., a
touch-sensitive screen), generate a sound (e.g., voice, musical
note, audible tone, etc.), and/or vibrate.
[0119] Some embodiments according to the present disclosure
contemplate that the active cover includes a mobile device cover
for use with, for example, a host mobile device (e.g., a cellular
handset, a cellular device, a smartphone, a wireless phone, a
wireless device, a wireless handset, a multimode phone, a mobile
phone compliant with multiple wireless communication standards, a
mobile phone equipped with a global positioning system, a
multiple-input-multiple-output phone, a wireless communication
device, a two-way radio, a communication device with one or more
antennas, etc.). The systems and methods disclosed herein can also
be used with, for example, tablets, tablet computers, laptops,
computers, computing devices, and other devices as well. The
systems and methods can be used with stationary devices such as,
for example, desktop computers and stationary monitors and/or
displays as well. Some embodiments according to the present
disclosure that the functionality of the active cover can be
directly implemented into the host mobile device, for example, as
part of the housing of the host mobile device.
[0120] Some embodiments according to the present disclosure
contemplate that, during a host mobile device alert or event, an
active mobile device cover can provide its own alert or indication
according to signals (e.g., alert signals, indication signals,
data, digital signals, etc.) received from the host mobile device.
The active mobile device cover may also light in a distinct or
random pattern such as, for example, any arrangement, sequence,
etc. using one or more lights (e.g., illuminating devices, display
devices, lighting devices, light emitting diodes (LEDs), liquid
crystal displays (LCDs), etc.) in which different colors,
brightness, intensities, etc. form shapes, images, icons, emojis,
text, alphanumeric text, video, messages, notifications, etc. that
are either static or moving (e.g., animated), for example. The
lights may be individual or distinct lighting devices or may be
part of or form at least a portion of a screen or a display of the
active mobile device cover. In some embodiments, the distinct or
random patterns can be illuminated according to the sound, sound
signal, alert data, digital signal, caller, contact, notification,
etc., and/or other information generated by the host mobile device,
and received by the active mobile device cover, for example. In
some embodiments, a distinct pattern can be assigned (e.g.,
manually by a user or automatically) to an associated sound, sound
signal, alert, alert signal, digital signal, and/or other
information. For example, a distinct pattern can be assigned to a
particular ring tone, ring tone signal, contact information (e.g.,
telephone number, email address, etc.), etc. A random pattern can
be assigned to and/or associated with particular sounds, sound
signals, alerts, alert signals, digital signals, callers, contacts,
notifications, etc., and/or other information. For example, a
random pattern or selected pattern can be assigned to a particular
ring tone or ring tone signal of the host mobile device, or to a
particular source (e.g., telephone number, caller ID, email
address, IP address, etc.) of a message, email, call, etc. The
random pattern can also be assigned to unassigned identifiers
(e.g., telephone numbers, email addresses, IP addresses, source
identifiers, etc.) or unrecognized and/or unknown identifiers. In
addition to enhancing the look and feel of the outside of the host
mobile device, the active mobile device cover provides the user
with superior sensory input over the host mobile device alone,
and/or protect the host mobile device from drops, scratches,
etc.
[0121] Some embodiments according to the present disclosure provide
a mobile device cover with lights such as light emitting diodes
(LEDs) which can be part of and/or form different types of displays
(e.g., organic LED (OLED) screens, RGB LED screens, LCD displays,
LED indicator lights, touch-sensitive displays, screens, etc.), or
other light sources or displays.
[0122] Some embodiments according to the present disclosure provide
a mobile application that runs on a host mobile device. The mobile
application provides a graphical user interface including one or
more graphical elements that are used to control the mobile device
cover and the host mobile device.
[0123] FIG. 1A shows an exemplary mobile device cover 100 according
to an embodiment of the present disclosure. As shown in FIG. 1A,
the mobile device cover 100 (e.g., a cover, a case, a shell, a
protector, etc.) is physically and/or electrically connected to a
host mobile device 110. In some embodiments, the mobile device
cover 100 is wirelessly connected to the host mobile device 110. In
some embodiments according to the present disclosure, the host
mobile device 110 (not shown in FIG. 1A except for a camera 125 and
a sensor 135 on a back side 185 of the host mobile device 110) may
be slipped inside or inserted into the mobile device cover 100, or
the mobile device cover 100 can be snapped on or stretched around,
at least in part, or otherwise can be fit around, at least in part,
the host mobile device 110. FIGS. 1F and 1G show front sides of a
front portion 145 and a middle portion 153 of the mobile device
cover 100 according to some embodiments of the present disclosure.
Referring to FIGS. 1F and 1G, the host mobile device 110 (not
shown) can be inserted or locked in between the guides 165 of the
middle portion 153. Although some embodiments contemplate a via in
the mobile device cover 100 through which a female connector (e.g.,
a female USB-type connector) of the host mobile device can be
accessed, other embodiments contemplate the mobile device cover 100
with a connector 175 (e.g., a lightning connector, a USB-type
connector, a data connector, a recharging connector, multi-pin
connector, etc.) that mates with the female connector of the host
mobile device 110 to provide a connection (e.g., a power
connection, a physical connection, an electrical connection, a
signal connection, a synchronization connection, etc.). In some
embodiments, the connector 175 provides a connection (e.g.,
electrical connection, data connection, etc.) between circuits in
the host mobile device 110 and the mobile device cover 100. For
example, the batteries in the host mobile device 110 and the mobile
device cover 100 can charge each other via the connector 175 and/or
other ports, for example. In some embodiments, the connector 175 is
part of a connector assembly that includes a connector element 148,
a coupler 149, and a port 147. In addition to or instead of the
connector 175, the host mobile device 110 and the mobile device
cover 100 can communicate wirelessly (e.g., Bluetooth
communication, near field communication (NFC), other radio
frequency (RF) communication (e.g., Wi-Fi), infrared communication,
etc.) with each other, as mentioned below. In some embodiments, the
front side 145 of the mobile device cover 100 can be interlocked
with the middle portion 153 of the mobile device cover 100 with the
host mobile device 110 there between. As noted before, the main
display of the host mobile device 110 may or may not be covered by
a transparent material of the mobile device cover 100. In some
embodiments, a window 195 is provided in the front portion 145 of
the mobile device cover 100 so that the user can directly touch the
display (e.g., touch-sensitive screen) of the host mobile device
110.
[0124] In some embodiments, the mobile device cover 100 can be an
accessory to the host mobile device 110. In some embodiments, the
mobile device cover 100 can be an accessory that is operable while
separate from the host mobile device 110. The accessory can be in
wireless communication with the host mobile device 110. In some
embodiments, the mobile device cover 100 and the host mobile device
110 can be controlled via inputs (e.g., buttons, touch-sensitive
screens, capacitive touch, sliders, graphical elements on graphical
user interfaces, etc.) located on the mobile device cover 100, the
host mobile device 110, a mobile application running on the host
mobile device 110, a mobile application running on the mobile
device case 100, a wired and/or wireless signal sent to the host
mobile device 110, a wired and/or wireless signal sent to the
mobile device cover 100, etc. The wireless signal can include, for
example, Bluetooth signals, IEEE 802.11 signals, wireless local
area network (WLAN) signals, wireless personal area network (PAN)
signals, Zigbee signals, infrared signals, RF signals, etc. sent to
the mobile device cover 100, the host mobile device 110, etc.
Accordingly, the mobile device cover 100 and/or the host mobile
device 110 include, for example, antennas and circuits (e.g.,
processors, wireless hardware, transceivers, transmitters,
receivers, etc.) to support wireless communication between them
100, 110, and/or between the mobile device cover 100, the host
mobile device 110, and/or other wireless devices (e.g., wireless
speakers, wireless microphones, wireless headphones, wireless
earbuds, wireless displays, base stations, access points, wireless
networks, etc.).
[0125] Referring to FIG. 1A, a back side 158 of the back portion
155 (e.g., back cover) of an exemplary mobile device cover 100
according to an embodiment of the present disclosure is shown. The
back portion 155 of the mobile device cover 100 has lights 160. The
lights 160 can form, be a part of, and/or illuminate a screen
(e.g., a main screen or display, indicator lights, light patterns,
etc.) and can emit different colors with different intensities at
different times. The lights 160 can also form, be a part of, and/or
illuminate another screen 132 or an extension of the main screen
along an edge 130 (e.g., a beveled edge, a chamfered edge, a side,
a lateral side, a border of the screen 162, etc.) of the mobile
device cover 100. Further, the lights 160 can illuminate beads 180
with different colors as indicator lights, for example. The beads
180 can be colored or not, and can be at least partially
transparent, for example. In some instances, the beads 180 can take
the configuration of letters, numbers, and/or shapes and can be
flat or raised in structure. The beads 180 can be used as part of a
Braille reader system, for example. In some instances, the beads
180 can include, for example, LED or light covers. In some
examples, the beads 180 can be flat transparent plastic windows
that can be positioned over lights 160. In such an instance, the
beads 180 can be colored, and/or the lights 160 can provide color
through colorless, transparent beads 180. In some embodiments, the
beads 180 can be disposed throughout the back cover 155 of the
mobile device cover 100 so that the beads 180 can be illuminated in
particular colors, patterns, and/or intensities at particular times
and/or in response to certain alerts or other information (e.g.,
digital signals, digital data, analog signals, etc.) received from
the host mobile device 110.
[0126] In some embodiments, when the host mobile device 110 and the
mobile device cover 100 are operatively coupled, the mobile device
cover 100 can provide indicators and/or data (e.g., digital data,
video data, streaming data, etc.) from the host mobile device 110
to the user via output interfaces (e.g., lights, screens, speakers,
etc.) of the mobile device cover 100. In some embodiments, when the
host mobile device 110 and the mobile device cover 100 are
operatively coupled, the mobile device cover 100 and the host
mobile device 110 are in one- or two-way digital and/or analog data
communication. The mobile device cover 100 can display information,
data, and/or content (e.g., multimedia content, video content,
streaming content, social media content, scrolling text, etc.)
received from the host mobile device 110. Further, the host mobile
device 110 can display information, data, and/or content received
from the mobile device cover 100. The host mobile device 110 and/or
the mobile device cover 100 can cause information, data, and/or
content to be displayed on the host mobile device 110. Further, the
host mobile device 110 and/or the mobile device cover 100 can cause
information, data, and/or content to be displayed on the mobile
device cover 100. The information, data, and/or content can be
received from the host mobile device 110, the mobile device cover
100, another device, and/or a third party, such as a mobile
application, a website, etc. FIG. 1E shows an embodiment of the
mobile device cover 100 in which the back cover 1030 includes the
lights 160 forming a touch-screen display 162 that can be similar
or the same as the display that can be shown on the main display of
the host mobile device 110. Thus, for example, the touch-screen
display 162 of the mobile device cover 100 can operate in a same or
similar manner (e.g., same or similar graphical user interface,
graphical elements, touch-and-feel, etc.) as the main display of
the host mobile device 110. The touch-screen display 162 of the
mobile device cover 100 can provide the same or similar array of
icons 164 as the main display of the host mobile device 110, for
example, or can be completely different. This can be useful, for
example, if the display of the host mobile device 110 is being used
for another purpose (e.g., playing a video, taking a call, work
use, personal use, etc.), but the user wants to access other mobile
applications. For example, the host mobile device 110 can be used
to operate a GPS navigation application, while the mobile device
cover 100 is being used to watch a movie or to stream video.
Further, since the host mobile device 110 and the mobile device
cover 100 can be in wireless communication, the mobile device cover
100 can be detached from the host mobile device 110 while watching
the movie or streaming video, for example.
[0127] Referring to FIG. 1A, when the host mobile device 110 is
receiving an incoming call, for example, beads 180 that form the
word "CALL" on the back cover 155 of the mobile device cover 100
can be illuminated, caused to flicker, flash, etc. If a calendar
event notification is activated or received by the host mobile
device 110, for example, the beads 180 that form the word "ALERT"
can be illuminated, caused to flicker, flash, etc. If a text
message is received by the host mobile device 110, for example, the
beads 180 that form the word "TEXT" can be illuminated, caused to
flicker, flash, etc. These events and others (e.g., social media
postings or messages, changes in sports scores, news items, emails,
SMS messages, etc.) can also be displayed on the touch-screen
display 162. The beads 180 can also be illuminated different colors
and with different intensities to indicate different degrees of
urgency. For example, if the alert is urgent (e.g., an email sent
with "high importance"), the beads 180 that form the word "ALERT"
can flash red and/or with increased intensity to indicate urgency.
In another example, if the incoming call or text message is not
from an important person, which can be designated via programming,
user settings, user configurations, user preferences, etc., the
corresponding beads 180 can be illuminated a dim blue. In some
embodiments, the mobile device cover 100 can determine the identity
of the caller or the message sender via electrical signals, sound
signals, acoustic signals, wireless signals, digital signals, etc.
received from the host mobile device 110. In some embodiments, the
host mobile device 110 can determine the identity of the caller or
the message sender and send a data signal corresponding to and/or
identifying the caller or the message sender to the mobile device
cover 100 as well as other information (e.g., voice mail, text
message, indications of importance, etc.). Further, the user may be
notified as to the name, number, email address, etc. of the sender
or source of the alert, text, email, or other notification via the
lights 160, beads 180, or other output devices (e.g., speakers,
screens, vibration, etc.) of the mobile device cover 100.
[0128] In some embodiments, the mobile device cover 100 can be
configured to provide video (e.g., live streaming video, streaming
video, stored video, etc.) and/or other information (e.g., digital
data, messages, news, alerts, etc.) on one or more screens. The
video can be provided via the host mobile device 110, for example,
or some other source to which the mobile device cover 100 and/or
the host mobile device 110 is operatively coupled. For example, the
mobile device cover 100 can have its own wireless link with an
access point (e.g., an IEEE 802.11-compliant access point) or a
base station (e.g., a cellular base station, a portable base
station, etc.) from which to download media content. The mobile
device cover 100 can also include memory storage (e.g.,
non-transitory memory storage, solid state memory storage,
removable memory sticks, disks, cards, etc.) on which resides media
content for playing or displaying on the screen of the mobile
device cover 100 and/or the host mobile device 110. The video can
be, for example, stored on the host mobile device 110 or can be
streamed via a wireless link (e.g., cellular link, WIFI link, IEEE
802.11 link, wireless local area network (WLAN) link, Bluetooth
link, RF link, etc.) with a content provider or a third party
application. In some embodiments, closed captioning or subtitles
can scroll along the main screen 162 which can include and/or be
supplemented with one or more screens 132 on one or more edges 130
of the mobile device cover 100. In some embodiments, the mobile
device cover 100 can be configured to provide an alert of a
received video message and to play the video message on the screen
162 of the mobile device cover 100. The screen 162 of the mobile
device cover 100 can be substantially independent or can
substantially mirror the screen of the host mobile device 110. The
screens 162, 132 can be incorporated into the housing of the
electronic device. Further, the screen 162 of the mobile device
cover 100 can be touch-sensitive and employ graphical elements of a
graphical user interface. Thus, for example, a user input via the
touch-sensitive screen 162 of the mobile device cover 100 can
provide a user input to the host mobile device 110 and/or the
mobile device cover 100. The screen of the mobile device cover 100
can be set up to substantially mirror the screen of the host mobile
device 110 or to operate independently of the screen of the host
mobile device 110. Content or material can also be displayed on the
mobile device cover 100 and/or the host mobile device 110 that is
from an application on the host mobile device 110, for example. For
example, if the user has access to a sports application running on
the host mobile device 110 that shows sports videos, television
channels, movie channels, or live events on the host mobile device
110, the video may be displayed on the host mobile device 110
and/or the mobile device cover 100.
[0129] Some embodiments provide that digital signals can be
received or provided by the host mobile device 110 and forwarded to
the mobile device cover 100 for storage, processing, and/or output
(e.g., on a display, lights, a speaker, a vibrating mechanism,
etc.). For example, in addition to multimedia data, some
embodiments provide that data (e.g., alphanumeric data, indicators,
control data, source information, etc.) can be received or provided
by the host mobile device 110 and forwarded to the mobile device
cover 100 for storage, processing, and/or output. For example, the
edge screen 132 (or any other screen or display comprising lights
160 on the mobile device cover 100) can be configured to scroll
information relating to news, sports, live or recorded events or
movies, stocks, weather, calendar events, text messages, alerts,
email, social media messages (e.g., messages or posts from mobile
applications or websites such as Facebook, Twitter, Snapchat,
Instagram, etc.), etc. In some embodiments, the information can
scroll around one or more edge screens 132 around the mobile device
cover 100. In some embodiments, the host mobile device 110 can be
set to periodically receive or retrieve sports data (e.g., scores,
news items, etc.) or other types of data. The data can be from, for
example, websites, mobile applications, other host mobile devices,
etc. The host mobile device 110 can send sports data, for example,
to the mobile device cover 100; and the mobile device cover 100 can
display or scroll the data across the edge screen 132 of the mobile
device cover 100 or display or scroll on the screen 162. In some
embodiments, the edge screen 132 can be touch-sensitive, thereby
allowing the user to tap or swipe an email notification and read a
scrolling email on the edge screen 132 or on another display (e.g.,
the main display 162 on the back cover 155) of the mobile device
cover 100. In some embodiments, the data can flow across the edge
screen 132 in response to a finger sweeping motion along the edge
touch-sensitive screen 132. In one embodiment, an incoming text
message can be indicated by the beads 180 forming the word "TEXT"
being illuminated by lights 160, the sender of the incoming text
can be displayed on the edge screen 132, and the text of the text
message can be displayed on the main screen 162 on the back cover
155 of the mobile device cover 100. In one embodiment, alphanumeric
letters are displayed on the screen on the back cover 155 and the
edge 130, either simultaneously or independently, indicating that a
text message has been received and possibly displaying the sender's
name, the sender's associated icon (e.g., icon, emoji, animated
icon, animated emoji, etc.), the sender's associated image (e.g.,
sender's picture), the sender's subject, the sender's header, the
sender's body text, the sender's partial or full text, etc. A text
or email icon can be displayed instead of the words TEXT, for
example. The display can also be a series of LEDs forming a grid to
accommodate lights show, scrolling text, etc.
[0130] The edge screen 132 can be configured to scroll completely
or partially around the mobile device cover 100 and/or along one or
more of its edges 130. In some embodiments, the edge 130 can be
segmented or partitioned so that the right edge portion is reserved
for a first subject (e.g., stocks), the left edge portion is
reserved for a second subject (e.g., sports), the bottom edge
portion is reserved for a third subject (e.g., email), and the top
edge portion is reserved for a fourth subject (e.g., calendar
items, alerts, etc.), for example. Within each segment, the edge
screen 132 can scroll the data. In some embodiments, the user can
program and/or select which subject is displayed on each individual
segment on the mobile device cover 100. In some embodiments, the
user can program the mobile device cover 100 so that it decides on
which segment to display a particular subject (e.g., incoming call,
incoming text, incoming email, incoming message, mobile device
notification, mobile device accessory notifications, music or other
audio notifications, social media notifications, etc.).
[0131] FIG. 1B shows a top view of an exemplary mobile device cover
100 according to an embodiment of the present disclosure. FIG. 1C
shows a partially exploded side perspective view of an exemplary
mobile device cover 100 according to an embodiment of the present
disclosure.
[0132] Referring to FIGS. 1B and 1C, the mobile device cover 100
can be adapted, for example, to provide physical vias (e.g., access
openings and windows) through which various input interfaces and
output interfaces of the host mobile device 110 can be accessed
without detaching the mobile device cover 100 from the host mobile
device 110. In some embodiments, the mobile device cover 100 may
provide a physical opening to access a display, a camera, a button,
a control, other input/output (I/O) interfaces, etc. of the host
mobile device 110. In some embodiments, the mobile device cover 100
does not cover the main display of the host mobile device 110 when
the mobile device cover 110 is attached to the host mobile device
110. In some embodiments, the mobile device cover 100 may provide a
transparent or partially transparent cover portion, for example,
over a display or other portions of the host mobile device 110. The
transparent cover portion can be made of materials that, for
example, do not interfere with the operation of any of the touch
screens, speakers, and/or buttons of the host mobile device 110. In
some embodiments, the materials can be substantially transparent to
wireless communication links used by the host mobile device 110
and/or the mobile device cover 100. The transparent cover portion
may also protect areas of the host mobile device 110 such as touch
screens from scratches or other damage.
[0133] Some embodiments according to the present disclosure may
provide that the mobile device cover 100 is made of one or more of
the following materials: silicone, rubber, metal, plastic,
polymers, polycarbonate, composites, cloth, metal, wood, acrylic,
glass, plexiglass, and/or other materials. The cover material may
be, at least in part, opaque or transparent. The cover material may
assist a user in gripping the host mobile device 110 and may
protect the host mobile device 110. The cover material may be, for
example, one or more of the following: shock resistant, shock
proof, shatter proof, shatter resistant, dust resistant, dust
proof, water resistant, water proof, etc. In some embodiments, the
mobile device cover 100 may be made up of multiple pieces (e.g.,
portions 100a, 100b, 100c, one or more printed circuit boards,
housings, etc.), as shown in FIGS. 1B and 1C. In some embodiments,
the multiple pieces of the mobile device cover 100 interlock
together to house, become the back panel of the host mobile device
110, and/or to connect (e.g., physically and/or electrically
connect, snap, interlock, etc.) to the host mobile device 110.
[0134] Referring to FIGS. 1B and 1C, the mobile device cover 100
can include, for example, circuitry 150 and lights 160 disposed on
one or more printed circuit boards. In some embodiments, the
circuitry 150 can include one or more of the following: one or more
processors, one or more non-transitory memories, signal processors,
light control circuitry, light drive circuitry, battery recharging
circuitry, battery control circuitry, display control circuitry,
sensors, input interface circuitry, output interface circuitry,
digital-to-analog converters, analog-to-digital converters, wired
transceivers, wireless transceivers, input/output ports,
input/output interfaces, and antennas. The one or more
non-transitory memories can be configured to store, for example,
data (e.g., input data, data received from the host mobile device
110, stored reference data, stored configuration data, stored
personal data, etc.) and processor-executable instructions or code
for use with the one or more processors. The circuitry 150 can be
connected, for example, to and/or can include the lights 160. Some
embodiments provide that the lights can include one or more of the
following: LEDs, flexible active-matrix OLEDs (AMOLEDs), OLEDs,
phosphor-based LEDs, white LEDs (WLEDs), multi-color WLEDs,
semiconductor LEDs, other types of LEDs, LCDs, LCD touch screens,
electroluminescence, pixel displays, etc., and can be arranged or
used in a specific pattern, array, sequence, etc. Some embodiments
provide that the lights can be raised or provide bumpy surfaces
suitable for use in a Braille system. Various components and/or
elements of the circuitry 150 can be connected to each other
through one or more buses, for example.
[0135] The mobile device cover 100 can also include, for example, a
battery 170 (e.g., a rechargeable battery) that can be used to
power, for example, the circuitry 150, the lights 160, and any
other circuitry or components in the mobile device cover 100 and/or
the host mobile device 110. The battery 170 can also be used to
power the host mobile device 110 and/or to recharge a battery in
the host mobile device 110. In some embodiments, the mobile device
cover 100 does not have a battery and instead can be powered by the
host mobile device 110. Some embodiments according to the present
disclosure provide that the battery 170 can be rechargeable or not
rechargeable. If not rechargeable, the battery 170 can be replaced.
Some embodiments of the battery 170 include, for example, a lithium
battery, an alkaline battery, a silver-oxide battery, nickel
cadmium battery, nickel metal hydride battery, lithium ion battery,
lithium ion polymer battery, etc. If rechargeable, then the battery
170 can be recharged, for example, by drawing energy from one or
more interfaces of the host mobile device 110 (e.g., an audio port,
an earphone jack, a docking port (e.g., a USB-type port, a
lightning connector port, a power and signaling connection port,
etc.), a wireless charging pad, etc.). The battery 170 can also be
recharged by drawing energy separate from or independent of the
host mobile device 110. Similarly, a rechargeable battery of the
host mobile device 110 can be charged through one or more
interfaces of the host mobile device 110 that are electrically or
wirelessly connected to the mobile device cover 100. The
rechargeable battery of the host mobile device 110 can also be
recharged by drawing energy separate from or independent of the
host mobile device 110.
[0136] For example, independent of whether the mobile device cover
100 is connected to the host mobile device 110, the mobile device
cover 100 can be separately plugged into a wall outlet or
wirelessly charged at a wireless charging station. The mobile
device cover 100 can also be charged by plugging it into a
computer, a charger bank, a generator, etc. via a USB-type
connection, for example. The battery 170 of the mobile device cover
100 can be charged by a piezoelectric battery charger, for example.
In some embodiments, the piezoelectric battery charger can convert
force (e.g., caused by pressure, movements, mechanical forces,
etc.) into electrical energy for use by the battery 170. Some
embodiments contemplate converting other types of energy (e.g.,
sound energy, light energy, electromagnetic energy, magnetic
energy, thermal energy, moving air, wireless energy, etc.) into
electrical energy to charge the battery 170. In some embodiments,
the mobile device cover 100 can utilize charging methods such as
conductive and inductive charging.
[0137] In some embodiments, the battery 170 of the mobile device
cover 100 can also be recharged when the host mobile device 110 is
wirelessly or wiredly connected to a power source (e.g., AC and/or
DC power source). For example, the battery 170 of the mobile device
cover 100 can be recharged when the host mobile device 110 is
connected to a wall outlet, for example, such as when a docking
port of the host mobile device 110 is connected to a wall outlet.
The battery 170 may receive energy directly from the wall outlet
(e.g., via connecting the mobile device cover 100 directly to the
wall outlet) or indirectly from the wall outlet through the host
mobile device 110. In addition, the battery 170 may receive energy
when a docking port or some other interface of the host mobile
device 110 is connected to a computer while electrically or
wirelessly connected to the mobile device cover 100. Some
embodiments according to the present disclosure contemplate that
the circuitry 150 receives power from the host mobile device 110
without using the battery 170 or in combination with the battery
170. Thus, some embodiments according to the present disclosure
might not have a dedicated battery as part of the mobile device
cover 100, or might use the battery 170 as a back-up power
source.
[0138] In some embodiments, just as the battery 170 of the mobile
device cover 100 can draw on energy from the host mobile device
110, the battery of the host mobile device 110 can draw on energy
from the mobile device cover 100 to recharge the battery of the
host mobile device 110 or to supplement power to the host mobile
device 110. For example, as rechargeable batteries age, they are
less capable of fully powering the main processor on the host
mobile device 110. The aging batteries have reduced full charge
capacity and provide less power, voltage, and/or current during
normal operation. As a result, some processors (e.g., central
processor, graphics processor, general processor, dedicate
processor, etc.) will enter a power-save mode in which processor
speed (e.g., clock speed) and/or load capacity (e.g., peak load)
are reduced to conserve power and/or energy which is detrimental to
performance and/or inconvenient to the user. In such a situation,
the host mobile device 110 can supplement the power and capacity of
its own battery with the battery 170 of the mobile device cover
100, thereby avoiding the power-save mode of the processor of the
host mobile device 110 or vice versa. Accordingly, the processors
in the host mobile device 110 can continue to operate at normal
operation speeds and load capacities. Further, by supplementing
power and capacity of the host mobile device 100, the battery 170
of the mobile device cover and the battery of the host mobile
device 110 can be used to power a turbo mode in the processor of
the host mobile device 110 or vice versa. For example, in turbo
mode, the processor (e.g., a central processor, a graphics
processor, a general processor, a dedicated processor, etc.) of the
host mobile device 110 can operate at one or more of the following:
a higher voltage, a higher current, a higher power, a higher load
capacity, and/or a higher clock speed than during normal operation.
During turbo mode, the host mobile device 110 and/or the mobile
device cover 100 can operate with greater performance and can
perform more processor-intensive applications.
[0139] In some embodiments, when the host mobile device 110 is
electrically connected to the mobile device cover 100 (e.g., when
the host mobile device 110 has been inserted into the mobile device
cover 110) and the mobile device cover 100 is plugged into a wall
outlet, for example, the battery 170 of the mobile device cover 100
and the battery of the host mobile device 110 charge at the same
time. In some embodiments, the battery of the host mobile device
110 charges without a decrease in charge speed even when the host
mobile device 110 and the mobile device cover 100 are charged at
the same time via the electrical connection (e.g., via a port 147)
of the mobile device cover 100 to the wall plug, for example.
[0140] FIG. 1D shows an exploded side perspective view of an
exemplary mobile device cover 100 according to an embodiment of the
present disclosure. In some embodiments, the circuitry 150 can be
embedded in the mobile device cover 100. In some embodiments, the
circuitry 150 may include, for example, one or more circuit boards
150a including, for example, one or more of the following: one or
more processors, circuit elements or components, an integrated
circuit, an integrated circuit chip, a system on a chip, etc. The
circuitry 150 may also include, for example, one or more sensors
150b (e.g., an audio sensor, a signal sensor, an optical sensor, a
wireless signal sensor, a wireless receiver, a wireless
transceiver, an electrical sensor, a power sensor, a battery
sensor, an electromagnetic sensor, a vibration sensor, gyroscope
sensor, iris scanner, fingerprint sensor, accelerometer, proximity
sensor, barometer, hear rate sensor, a biometric sensor, etc.).
Components 150a and 150b can be part of the same circuit board or
can be part of separate circuit boards, for example, that are
connected to form, in part, the mobile device cover 100. A sensor
can be part of components 150a, 150b, or both. In some embodiments,
the mobile device cover 100 can include multiple circuit boards or
multiple-layered circuit boards.
[0141] FIG. 2 illustrates an exemplary circuit arrangement
according to an embodiment of the present disclosure. Referring to
FIG. 2, a simplified block diagram is shown of the circuitry 150.
The circuitry 150 may include one or more of the following: a
processor 200, a memory 210, an I/O device 220, a bus 230, driver
circuitry 240, and lights 160. The processor 200, the memory 210,
the I/O device 220, the driver circuitry 240, and the lights 160
can be coupled to each other via one or more buses 230. The
circuitry 150 can include more or less than one processor 200, one
memory 210, one I/O device 220, one bus 230, one driver circuit
240, and two lights 160 as illustrated in FIG. 2. Thus, some
embodiments contemplate employing different numbers of various
elements of the circuitry 150.
[0142] The driver circuitry 240 can include, for example, one or
more of the following: light drivers, LED drivers, shift registers,
constant current supply, constant voltage supply, switching supply,
FET amplifier, BJT amplifier, etc. In addition, some embodiments
according to the present disclosure contemplate using a plurality
of sensors, processors, memories, and/or driver circuits. Some
embodiments provide that the driver circuitry 240 can be part of
the processor 200 and, in some embodiments, can take the place of
the processor 200. Some embodiments provide that the driver
circuitry 240 and other circuitry can be incorporated into a system
on a chip (SOC). In some embodiments, the driver circuitry 240 can
be configured to control any amount or arrangement of similar or
different lights 160, including a full display (e.g., a
touch-sensitive screen, LED screen, etc.). In some embodiments, the
driver circuitry 240 can be configured to power any number or
arrangement of similar or different lights 160.
[0143] The I/O device 220 can include, for example, one or more of
the following: an input device (e.g., a button), a touch-screen
display, a wired and/or wireless transceiver (e.g., cellular
transceiver, Bluetooth transceiver, WLAN transceiver, etc.), a
wired and/or wireless transmitter, a wired and/or wireless
receiver, an antenna, a speaker, a microphone, an I/O port (e.g.,
earbud port, earphone port, microphone port, speaker port, etc.),
an I/O interface, data connector port, power connector port, wired
and/or wireless communication device, GPS receiver, a network
interface, etc.
[0144] The processor 200 can include, for example, one or more of
the following: a general processor, a central processing unit, a
digital filter, a microprocessor, a digital processor, a digital
signal processor, a microcontroller, a programmable array logic
device, a complex programmable logic device, a field-programmable
gate array and an application specific integrated circuit (ASIC),
and a memory (e.g., a cache). Code, instructions, software,
firmware, and/or data including, for example, a mobile application
may be processed and/or executed by the processor 200 to perform
any of the operations, functions, and/or features described in the
present disclosure. Further, the code, instructions, software,
firmware, and/or data including, for example, the mobile
application may be stored in the processor 200 and/or the memory
210. The code, instructions, software, firmware, and/or data can be
automatically or manually updated, upgraded, modified, replaced,
overwritten, supplemented, etc. via a wireless or wired
connection.
[0145] The memory 210 can include, for example, one or more of the
following: a non-transitory memory, a non-transitory processor
readable medium, a non-transitory computer readable medium, a read
only memory (ROM), a random access memory (RAM), DRAM, EPROM,
EEPROM, F-RAM, FIFO, NVRAM, SRAM, a cache, a semiconductor memory,
a magnetic memory, an optical memory, a flash memory, a flash card,
a compact flash card, memory cards, secure digital memory cards, a
microcard, a minicard, an expansion card, a smart card, a memory
stick, a multimedia card, a picture card, flash storage, a
subscriber identity module (SIM) card, a hard drive (HDD), a solid
state drive (SSD), etc. The memory 210 may be configured to store
code, instructions, software, firmware, and data for use by the
processor 200 and may be external, internal, or both with respect
to the processor 200. In some embodiments, the memory 210 also
stores a mobile application, settings, parameters, values,
lightshows, icons (e.g., icons, emojis, graphical elements, etc.),
animations, scrolling text, etc. Further, the code, instructions,
software, firmware, and/or data can be automatically or manually
updated, upgraded, modified, replaced, overwritten, supplemented,
etc. via a wireless or wired connection.
[0146] FIGS. 26-41 show exemplary parts of an exemplary mobile
device cover 100 according to some embodiments of the present
disclosure.
[0147] FIGS. 26-29 show different views of an exemplary middle
frame 2600 of the mobile device cover 100 according to an
embodiment of the present disclosure. For example, FIGS. 26-29 show
a front view 2630, a back view 2700, a side view 2800, and a
perspective view 2900, respectively, of the middle frame 2600 of
the mobile device cover 100 according to the present disclosure.
The middle frame 2600 and other components of the mobile device
cover 100 can be made of, for example, one or more of the
following: plastic, metal, composite materials, alloys, wood,
cloth, fibers, glass, plexiglass, resin, rubber, etc., and/or one
or more other materials. Referring to FIGS. 26-29, the front of
middle frame 2600 can include, for example, guides 2620 configured
to receive the host mobile device 110 into a space 2640, and an
opening 2630 configured to accommodate the camera 125 and sensor
135 of the host mobile device 110 when the host mobile device 110
is placed in the space 2640 provided by the middle frame 2600. The
back of the middle frame 2600 can also provide a space 2710 to
accommodate a rechargeable battery 170 in which the space is
delineated by guides 2730. The guides 2730 can include, for
example, screw posts 2740 for receiving screws that are used to
mount one or more printed screen boards. In addition, the middle
frame 2600 provides a space 2720 to receive connector or port
components and/or circuitry (e.g., connector element 148, coupler
149, port 147, wires, and other circuitry). The middle frame 2600
can also include, for example, a locking mechanism 2910 that can be
integral with the guides 2620 and configured to lock with a locking
mechanism 3310 of a front frame 3000 when the middle frame 2600 and
the front frame 3000 are assembled. The locking mechanism 2910 of
the middle frame 2600 can also be configured to lock with a locking
mechanism of a back frame 3400. Some embodiments also contemplate
that one or more of the front frame 3000, the middle frame 2600,
and/or the back frame 3400 can be integral with or incorporated
into the host mobile device 110.
[0148] FIGS. 30-33 show different views of an exemplary front frame
3000 of the mobile device cover 100 according to an embodiment of
the present disclosure. For example, FIGS. 30-33 show a front view
3010, a back view 3100, a side view 3200, and a perspective view
3300, respectively, of the front frame 3000 according to the
present disclosure. The front frame 3000 and other components of
the mobile device cover 100 can be made of, for example, one or
more of the following: plastic, metal, composite materials, alloys,
wood, cloth, fibers, glass, plexiglass, resin, rubber, etc., and/or
one or more other materials. In one embodiment, the front frame 300
is made up of rubber to provide shock absorption and/or vibration
resistance. Further, a front frame 300 made up of rubber is also
flexible for securely and easily attaching and removing the front
frame 3000 to the middle frame 2600. In some instances, the front
frame 300 can be stretched around the middle frame 2600 with the
host mobile device 110 to attach or remove the front frame 300 to
or from the middle frame 2600. Referring to FIGS. 30-33, the front
frame 3000 can include, for example, an opening 3020 configured to
provide access to the main screen of the host mobile device 110,
and button elements 3030. The button elements 3030 are configured
to receive the buttons of the host mobile device 110 and to provide
buttons 3040 as part of the mobile device cover 100 that, when
pressed down by the user, press down the buttons of the host mobile
device 110. The front frame 3000 can also include, for example, a
via 3110 that is configured to provide access to a port and/or I/O
device (e.g., a headphone port, an earphone port, a headset port,
an I/O port, a speaker, a microphone, a dock connector, a connector
port, a USB-type port, etc.) of the host mobile device 110. In some
embodiments, the middle frame 2600 can also include, for example, a
via that is configured to provide access to a port and/or I/O
device (e.g., a headphone port, an earphone port, a headset port,
an I/O port, a speaker, a microphone, a dock connector, a connector
port, a USB-type port, etc.) of the host mobile device 110. The
front frame 3000 can include, for example, a via 3210 that is
configured to provide access to a switch 3210 (or some other user
input or output) of the host mobile device 110. The front frame
3000 also provides a locking mechanism 3310 that is configured to
lock with the locking mechanism 2910 of the middle frame 2600 when
the front frame 3000 and the middle frame 2600 are assembled.
[0149] The front frame 3000 can also include, for example, a via
3110 or another via that is configured to provide access to a port
and/or I/O device (e.g., a headphone port, an earphone port, a
headset port, an I/O port, a speaker, a microphone, a dock
connector, a connector port, a USB-type port, etc.) of the mobile
device cover 100. The earphone port (or headset port, headphone
port, etc.) provided by the mobile device cover 100 can be used by
the host mobile device 110 when, for example, the host mobile
device 110 no longer provides a dedicated earphone port or when its
multi-purpose port is being used for some other purpose (e.g.,
charging the host mobile device 110). The host mobile device 110
can use the ports of the mobile device cover 100, and the mobile
device cover 100 can use the ports of the host mobile device 110.
Further, I/O devices integrated with (or a part of) or connected to
the host mobile device 110 can be used by the mobile device cover
100, and I/O devices integrated with (or a part of) or connected to
the mobile device cover 100 can be used by the host mobile device
110.
[0150] FIGS. 34-37 show different views of an exemplary back frame
3400 of the mobile device cover 100 according to an embodiment of
the present disclosure. For example, FIGS. 34-37 show a front view
3410, a back view 3500, a side view 3600, and a perspective view
3700, respectively, of the back frame 3400 according to the present
disclosure. The back frame 3400 and other components of the mobile
device cover 100 can be made of, for example, one or more of the
following: plastic, metal, composite materials, alloys, wood,
cloth, fibers, glass, plexiglass, resin, rubber, etc., and/or one
or more other materials. Referring to FIGS. 34-37, the back frame
3400 can include, for example, an opening 3420 configured to
accommodate the camera 125 and sensor 135 of the host mobile device
110 when the host mobile device 110 is placed in the space 2650
provided by the middle frame 2600 and the back frame 3400 is
secured or locked onto the middle frame 2600. In some embodiments,
the back frame 3400 can be unlocked, removed, and replaced with
another back frames 3400 with the same or different appearance
and/or functionality, for example. The back frame 3400 also
includes, for example, a via 3430 configured to receive a button
structure 3800, and a via 3440 configured to provide access to the
port 147 of the mobile device cover 100 and/or the host mobile
device 110. The back frame 3400 is also structured to provide a
space 3510 to accommodate one or more printed circuit boards that
can include, for example, one or more lights 160. In some
embodiments, the back frame 3400 can be an integral part of a
housing of the host mobile device 110.
[0151] FIGS. 38-41 show different views of an exemplary button
structure 3800 of the mobile device cover 100 according to an
embodiment of the present disclosure. For example, FIGS. 38-41 show
a front view 3810, a back view 3900, a side view 4000, and a
perspective view 4100, respectively, of the button structure 3800
according to the present disclosure. The button structure 3800 and
other components of the mobile device cover 100 can be made of, for
example, one or more of plastic, metal, composite materials,
alloys, wood, cloth, fibers, glass, plexiglass, resin, rubber, etc.
Referring to FIGS. 38-41, a front of the button structure 3800
includes a push button 3820 that is in mechanical communication
with a spring return 3920. The sprint return 3920 includes a disc
3920 that comes nearer to and/or in contact with circuitry (e.g., a
magnetic sensor, a mechanical sensor, an electrical sensor, a
switch, a relay, etc.) of a printed circuit board when the push
button 3820 is pressed. The printed circuit can sense when the push
button 3820 is pressed and/or released, and can determine the
duration of the press, for example. The push button 3820 can be
used to turn the mobile device cover 100 on or off, and can be used
as a single button control for the mobile device cover 100 to turn
on or off or modify notifications, operations, and modes (e.g.,
silent mode, flashlight mode, panic mode, etc.). The button
structure 3800 is configured so that the button can be inserted
through the via 3430 of the back frame 3400.
[0152] FIGS. 42-58 show an embodiment of an exemplary process for
assembling a mobile device cover 100 according to the present
disclosure. FIG. 42 shows a perspective view of a front side of the
middle frame 2600. In FIG. 43, a cushion 4310 (e.g., a foam
cushion, a rubber cushion, etc.) is secured (e.g., glued, fastened,
etc.) in the space 2640 of the middle frame 2600 for receiving the
host mobile device 110. The cushion 4310 provides additional shock
and/or vibration resistance or isolation and helps to secure the
host mobile device 110 in place. In FIG. 44, an exemplary host
mobile device 110 is placed (e.g., inserted, slid, etc.) facing
forward in the space 2640 of the middle frame 2600 such that the
back of host mobile device 110 is disposed against the cushion 4310
and guided into place by guides 2630. In FIG. 45, the front frame
3000 is mounted on the middle frame 2600 over the host mobile
device 110. If made of rubber or other flexible material, the front
frame 3000 is stretched over the middle frame 2600 and the host
mobile 110. The front frame 3000 and the middle frame 2600 are
locked together by the stretched front frame 3000 and/or the mating
of the locking mechanisms 2910, 3310 of the front frame 3000 and
the middle frame 2600.
[0153] The back view of the middle frame 2600 is shown in FIGS.
46-55 with the host mobile device 110 already installed between the
front frame 3000 and the middle frame 2600. In FIGS. 46-48, a port
connector 4610 (e.g., a USB-type connector, a lighting connector, a
serial connector, a parallel connector, etc.) is mounted on the
middle frame 2600. The port connector 4610 can provide, for
example, a connection to the circuitry (including the battery 170)
of the mobile device cover 100, a connection to the host mobile
device 110 (including its circuitry and battery), and/or a
connection to an external device or power supply, for example. The
port connector 4610 can be configured for male and/or female
connectors and includes port circuitry 4620. One or more screws
4710, 4810 or another fastening mechanism (e.g., glue, fasteners,
stakes, nails, etc.) is used to secure the port connector 4610 to
the middle frame 2600 as shown in FIGS. 47 and 48.
[0154] In FIG. 49, the battery 170 (e.g., rechargeable battery) of
the mobile device cover 100 is installed in the space 2710 of the
middle frame 2600. The battery 170 fits within guides 2730, some of
which are also screw posts 2740. In FIG. 50, battery wires 5010 are
added for connecting the battery 170 to the circuitry of the mobile
device cover 100. In FIG. 51, the port connector wires 5110 are
added for connecting the port connector 4610 including its
circuitry 4620 to the rest of the circuitry of the mobile device
cover 100.
[0155] An exemplary printed circuit board 5210 is installed on the
middle frame 2600 of the mobile device cover 100. Referring to
FIGS. 52-54, the printed circuit board 5210 is mounted on the screw
posts 2740 of the middle frame 2600. The printed circuit board 5210
can include a plurality of printed circuit boards that are stacked
and communicate with each other via wires and other circuitry. Both
sides of the printed circuit boards can have circuitry. For
example, the printed circuit board 5210 shows an array of lights
160 that are can be controlled by circuitry on the other side of
the printed circuit board or by another printed circuit board
underneath the printed circuit board 5210, for example. One or more
screws 5310, 5410 or another fastening mechanism (e.g., glue,
fasteners, stakes, nails, etc.) is used to secure the printed
circuit board 5210 to the middle frame 2600 as shown in FIGS. 53
and 54. In FIG. 55, the button structure 3800 is installed such
that the disk 3920 of the spring return 3910 is over a sensor 5420
of the printed circuit board 5210. The sensor 5420 is configured to
sense when the button 3820 of the button structure 3800 is being
pressed, held down, and/or released.
[0156] The back frame 3400 is mounted over the middle frame 2600
and covers the printed circuit board 5210 as shown in FIG. 56. The
back frame 3400 can be clear, transparent, translucent, or
semi-transparent. In some embodiments, the back frame 3400 is
configured so that the array of lights 160 can shine through the
back frame 3400. The back frame 3400 is disposed so that the button
3820 of the button structure 3800 passes through the via 3430, and
the opening 3420 accommodates the camera 125 and sensor 135 of the
host mobile device 110. Referring to FIG. 56, the back frame 3400
is secured to the middle frame 2600 via a locking mechanism 5610
(e.g., ridges molded into the four sides of the middle frame 2600).
The locking mechanism 5610 can be configured to permanently or
removably secure, without damage, the back frame 3400 to the middle
frame 2600. Other types of locking mechanisms 5610 (e.g., screws,
fasteners, etc.) are within the scope of the present disclosure and
can provide easy removal of the back frame 3400 from the middle
frame 2600.
[0157] FIGS. 57 and 58 show the assembly of the mobile device cover
100 in two exploded views according to an embodiment of the present
disclosure. The printed circuit board 5210 is shown in a simplified
fashion and does not show all of the circuitry on the one or more
boards that make up the printed circuit board 5210.
[0158] FIG. 76 shows an exemplary back frame 3400 that provides an
exemplary removable plate (or removable portion) 3450 according to
an embodiment of the present disclosure. Although shown as a plate,
the removable portion of the back frame 3400 can be any shape,
size, and/or material, and can include, for example, almost all of
the backside 7610 of the back frame 3400. The plate 3450 can be
removed and replaced with other plates with different appearances
(e.g., designs, prints, level of transparency, colors, etc.), form
factors (e.g., plate with disk extending from plate, shapes
conducive for easy and secure handling, other shapes with or
without the plate as a platform, etc.), and/or materials (e.g.,
metal, plastic, rubber, cloth, composite materials, alloys, etc.).
The plate 3450 replacing the previous plate 3450 need not be of the
same shape, size, and/or material as illustrated by the
interchangeable removable plates (or removable portions) 3450 shown
in FIGS. 77A-B.
[0159] FIGS. 79A-F show exemplary removable plates 3450 that are
interchangeable on the back frame 3400 of the mobile device cover
100 and can enhance the design or appearance of the back frame 3400
according to the present disclosure. FIGS. 79A-B show exemplary
removable plates 3450 of different colors (e.g., blue color in FIG.
79A and red color in FIG. 79B), or different levels of transparency
(e.g., 25% transparency in FIG. 79A and 75% transparency in FIG.
79B). FIG. 79C shows an exemplary removable plate 3450 with a
college logo, for example. FIG. 79D shows an exemplary removable
plate 3450 with a sports team logo, for example. FIG. 79E-F show
exemplary removable plates 3450 with a customized message and/or a
customized design. The plates can be slid or inserted into and/or
mounted onto the back frame 3400. Further, the mobile application
that runs on the host mobile device 110, for example, that is used
to configure the mobile device cover 100 can also be used to select
different removable plates 3450 for purchase. In addition, a web
site can be provided to select different removable plates 3450 for
purchase. The mobile application and/or the web site can be used to
design removable plates 3450 with personalized text (e.g., names,
phrases, etc.) and/or graphics (e.g., icons, emojis, etc.) as shown
in FIGS. 79E-F, for example. Once selected and/or designed, a user
can order (e.g., purchase) the removable plate 3450 for delivery or
pick up. Some embodiments also provide for programming the mobile
device cover 100 to display the selected and/or customized designs
through a transparent or semi-transparent back plate 3450 using
lights 160 and/or a screen of the mobile device cover 100.
[0160] The plate 3450 can be removed and replaced with other plates
that provide functionality and/or different functionality (e.g., a
particular display resolution, screen, speaker, microphone,
projector, camera, flashlight, laser light, additional memory,
additional processing power, etc.). The functionality, which can be
accessed by the mobile device cover 100 and/or the host mobile
device 110, can be a new function or can provided enhanced
functionality over existing functionality of the mobile device
cover 100 and/or the host mobile device 110. For example, FIGS.
77A-B show side views of two exemplary removable plates (or
removable portions) 3450 of the back frame 3400 of the mobile
device cover 100 according to an embodiment of the present
disclosure. The removable portion 3450 in FIG. 77A may be an
existing plate 3450 of the back frame 3400, while the removable
portion 3450 in FIG. 77B, which is interchangeable with the
existing plate 3450, can have a different look, design, color, and
functionality. For example, the removable portion 3450 in FIG. 77B
can replace the plate 3450 in FIG. 77A on the back frame 3400 and
can be used as a speaker and/or a microphone for use by the mobile
device cover 100 and/or the host mobile device 110. The removable
portion 3450 need not be in physical contact with the back frame
3400 to function and may wireless communicate with the back frame
3400. Thus, the removable portion 3450 can be separated from the
back frame 3400 and operate as a wireless speaker.
[0161] The plate (or removable portion) 3450 can include, for
example, circuitry 7710 within the plate housing 7720 as shown in
FIG. 77B. The circuitry 7710 can be electrically connected and/or
in wired and/or wireless communication with the rest of the
circuitry of the mobile device cover 100. FIG. 78A shows an
exemplary plate 3450 that houses circuitry 7710 and provides
electrical contacts 7720 for connecting with the rest of the
circuitry of the mobile device cover 100 when the plate 3450 is
inserted into the back frame 3400. The edge of the plate 3450 may
be inserted into a female electrical connector of the back frame
3400 which secures the plate 3450 in place. FIG. 78B shows another
exemplary plate 3450 that houses circuitry 7710 and provides
electrical contacts 7720 for connecting with the rest of the
circuitry of the mobile device cover 100 when the plate 3450 is
inserted into the back frame 3400. Contact can be made
automatically when the plate 3450 is inserted into the back frame
3400. The electrical contacts 7720 can also include, for example, a
magnet for securing the plate 3450 to the back plate 3400 and
maintaining contact between the electrical contact 7720 and a
corresponding electrical contact of the back frame 3400.
[0162] FIGS. 80A-B show two exemplary embodiments of
interchangeable back frames 3400 of the mobile device cover 100
according to the present disclosure. Instead of or in addition to
replacing a removable plate 3450, some embodiments provide for
interchangeable back frames 3400. Thus, similar to the discussion
with respect to interchangeable back plates 3450, a back frame 3400
can be removed and replaced by another back frame 3400 that
provides a different size, shape, material, and/or functionality,
for example. The back frame 3400 in FIG. 80A can be removed from
the mobile device cover 100 and replaced with the back frame 3400
in FIG. 80B to provide, among other things, one or more touch
screens 8010. The back frame 3400 can house circuitry to support
the functionality of the interchangeable back frame and to
facilitate electrically connecting and/or communicating wiredly
and/or wirelessly with the rest of the circuitry of the mobile
device cover 100. Just as with the back plates 3450, back frames
3400 can be selected, designed, and/or ordered using a mobile
application and/or a website for pickup or delivery to the
customer.
[0163] FIG. 81 shows an exemplary embodiment of a host mobile
device 110 with an interchangeable back cover 8110 according to the
present disclosure. Referring to FIG. 81, the back cover 8110 of
the host mobile device 110 can be replaced with another back cover
8110. Similar to discussions with respect to the removable plate
3450 and the interchangeable back frames 3400 of the mobile device
cover 100, a back cover 8110 of the host mobile device 110 can be
removed and replaced by another back cover 8110 that provides a
different size, shape, material, and/or functionality, for example.
The back cover 8110 of the host mobile device 110 in FIG. 81 can be
removed from the host mobile device 110 and replaced with another
back cover 8110 to provide, among other things, the functionality
of one or more touch screens 8120 for the back of the host mobile
device 110 (in addition to the main screen on the front of the host
mobile device 110). The back cover 8110 can house circuitry to
support the functionality of the interchangeable back cover 8110
and to facilitate electrically connecting and/or communicating
wiredly and/or wirelessly with the rest of the circuitry of the
host mobile device 110. Just as with the back plates 3450 and back
frames 3400 of the mobile device cover 100, the back cover 8110 of
the host mobile device 110 can be selected, designed, and/or
ordered using a mobile application and/or a website for pickup or
delivery to the customer.
[0164] FIGS. 59-70 show some exemplary circuits that are part of
the printed circuit board 5210 and other circuitry of the mobile
device cover 100 according to the present disclosure.
[0165] FIG. 59 shows an exemplary USB-to-lightning-connector
circuit 5900 of the mobile device cover 100 according to an
embodiment of the present disclosure. The circuit 5900 includes a
male lightning connector 5910, a switch 5930, and a USB-type
receptacle 5920. The male lightning connector 5910 is inserted into
a female lightning connector of the host mobile device 110 when the
host mobile device 110 is placed into the middle frame 2600. The
USB-type receptacle 5920 includes, for example, a female micro-USB
connector that is part of the mobile device cover 100. An
embodiment of the female micro-USB connector is shown, for example,
as port 147 in FIG. 1C. The USB-type receptacle 5920 can be used,
for example, to connect to a wall plug to charge the host mobile
device 110 and/or the mobile device cover 100, or to connect to
another USB-type compatible device. In addition, the circuit 5900
also enables power transfer and synchronization between the host
mobile device 110 and the mobile device cover 100.
[0166] FIG. 60 shows an exemplary battery charge indicator circuit
6000 of the mobile device cover 100 according to an embodiment of
the present disclosure. The exemplary battery indicator circuit 600
is operatively coupled to one or more processors of the mobile
device cover 100. The one or more processors send signals that
cause the light driver circuitry 6010 to light up 0 to 4 lights 160
as an indication of battery charge of the battery 170 of the mobile
device cover 100. For example, 0 lights indicates no or little
charge; 1 light indicates approximately 25% battery charge; 2
lights indicate approximately 50% battery charge; 3 lights indicate
approximately 75% battery charge; and 4 lights indicate full or
almost full charge.
[0167] FIG. 61 shows an exemplary push button circuit 6100
according to an embodiment of the present disclosure. The pushing
or releasing of a button (e.g., button 3820) causes a switch 6110
to open or close, thereby allowing the one or more processors of
the mobile device cover 600 to sense when the button has been
pressed or released, as well as determine a duration of time that
the button is held down. In some embodiments, the button comprises
any type of input device and/or sensor (e.g., capacitive sensor,
proximity sensor, heat sensor, touch sensor, pressure sensor,
electromagnetic sensor, motion sensor, gesture sensor, etc.).
[0168] FIG. 62 shows an exemplary memory circuit 6200 according to
an embodiment of the present disclosure. The memory circuit 6200
can be in communication with the one or more processors of the
mobile device cover 100. Referring to FIG. 62, one or more flash
memories 6210 can be used to store instructions (e.g.,
processor-executable instructions), software, code, commands,
parameters, data, etc. The flash memories 6210 can be used to
store, for example, icons, light shows, contact information,
settings, notifications, notification parameters, etc. in the
mobile device cover 100.
[0169] FIG. 63 shows an exemplary processor circuit 6300 according
to an embodiment of the present disclosure. The processor circuit
6300 can include one or more processors 6310. For example,
processor 6310 is shown as a digital signal processor with internal
memory (e.g., cache, RAM, ROM, etc.). The processor 6310 can be
operatively coupled with and controls the other circuits shown in
FIGS. 59-70 in addition to other circuitry of the mobile device
cover 100 and/or the host mobile device 110. Processor 6310 is the
main processor of the mobile device cover 100.
[0170] FIG. 64 shows an exemplary battery management circuit 6400
according to an embodiment of the present disclosure. Referring to
FIG. 64, the battery management circuit 6400 is operatively coupled
to the battery 170 of the mobile device cover 100 and/or the
battery of the host mobile device 110. The battery management
circuit 6400 includes a battery charger 6410 that is operatively
coupled to the battery 170 of the mobile device cover 100 and/or
the battery of the host mobile device 110. When the mobile device
cover 100 is plugged into a wall outlet, for example, the battery
charger 6410 charges one or both of the batteries of the mobile
device cover 100 and the battery of the host mobile device 110 as
well as powers the mobile device cover 100 and/or the host mobile
device 110. The battery charger 6410 is also configured to charge
the battery of the host mobile device 110 from the battery 170 of
the mobile device cover 100, or vice versa, and/or to power the
mobile device cover 100 and/or the host mobile device 110. The
charging direction and other start- or stop-charging parameters can
be set by the one or more processors of the mobile device cover
100. The battery charger 6410 in combination with the one or more
processors of the mobile device cover 100 is also configured to
sense the amount of battery charge in one or both of the batteries
of the mobile device cover 100 and the battery of the host mobile
device 110.
[0171] FIG. 65 shows an exemplary power management circuit 6500
according to an embodiment of the present disclosure. Referring to
FIG. 65, the power management circuit 6500 provides a power
distribution auto-switching power multiplexer 6510, regulator 6520,
and a load switch 6530 (e.g., power rail switch) to smoothly
transition between multiple power sources, such as DC power (e.g.,
battery operated power) and AC power (e.g., wall plug power) to
power the mobile device cover 100 and/or the host mobile device
110. The regulator 6520 provides a regulated 3V output for use by
system power of the mobile device cover 100.
[0172] FIG. 66 shows an exemplary off/on and/or reset circuit 6600
according to an embodiment of the present disclosure. Referring to
FIG. 66, the circuit 6600 includes a microcontroller 6610 that
causes the mobile device cover 100 to turn off and then on. For
example, if the button 3820 is pressed and held down or otherwise
actuated for at least a particular duration, the mobile device
cover 100 is powered off and then powered on. In some embodiments,
this is a power reset or power on/off of the mobile device cover
100.
[0173] FIG. 67 shows an exemplary clock circuit 6700 according to
an embodiment of the present disclosure. Referring to FIG. 67, the
clock circuit 6700 includes, for example, a clock 6710 and a
crystal 6720 to provide a real-time clock for the mobile device
cover 100 and/or the host mobile device 110. The clock 6710 can be
set and can keep time and calendar data, and/or set an alarm. The
clock 6710 can be used, for example, to display time and calendar
information on the mobile device cover 100 and for synchronization
purposes. Other wireless communications can used instead of or in
combination with Bluetooth wireless signals including, for example,
IEEE 802.11 wireless signals, WLAN signals, wireless PAN signals,
Zigbee signals, infrared signals, RF signals, near-field wireless
signals, etc.
[0174] FIG. 68 shows an exemplary Bluetooth circuit 6800 according
to an embodiment of the present disclosure. Referring to FIG. 68,
the Bluetooth circuit 6800 includes a Bluetooth module 6810. The
Bluetooth module 6810 supports the Bluetooth standard by providing
secure wireless connections. In some embodiments, the Bluetooth
module 6810 includes one or more internal antennas for Bluetooth
communications. However, one or more external Bluetooth antennas
operatively coupled to the Bluetooth module 6810 are also within
the scope of the present disclosure. The Bluetooth module 6810 of
the mobile device cover 100 can be used, for example, to wirelessly
communicate with the host mobile device 110 and/or with other
Bluetooth-enabled wireless devices.
[0175] FIG. 69 shows an exemplary LED driver circuit 6800 according
to an embodiment of the present disclosure. Referring to FIG. 69,
the LED driver circuit 6900 includes, for example, LED drivers
6910, 6920. Each exemplary LED driver 6910, 6920 can drive up to
144 LEDs and can be programmed via an I2C compatible interface, for
example. LED drivers that drive more or less than 144 LEDs are also
within the scope of the present disclosure. FIGS. 70A-D show
exemplary arrays of LEDs driven by the LED drivers 6910, 6920. For
example, the 144 LEDs in FIGS. 70A-B can be driven by LED driver
6910, and the remaining LEDs in FIGS. 70C-D can be driven by LED
drive 6920. An exemplary array of LEDs is formed from an
11.times.21 grid of LEDs, for example. Additional or fewer LED
drivers and LEDs can be added to or removed from the mobile device
cover 100 without departing from the scope of the present
disclosure. In addition, screens or other types of displays with
accompanying screen or display driver circuits are also within the
scope of the present disclosure.
[0176] FIGS. 71-75 show exemplary printed circuit boards (or
layers) that make up a printed circuit board (or multi-layer
printed circuit board) 7100 as shown in FIG. 71 according to an
embodiment of the present disclosure. FIG. 71 shows the printed
circuit board 7100 when the four printed circuit boards (or layers
of a multi-layer printed circuit board) 7200, 7300, 7400, 7500 are
stacked and put together. FIG. 72 shows an exemplary top printed
circuit board (or top layer of a multi-layer printed circuit board)
7200 according to an embodiment of the present disclosure. FIG. 73
shows an exemplary second printed circuit board (or second layer of
a multi-layer printed circuit board) 7300 according to an
embodiment of the present disclosure. The second printed circuit
board 7300 is disposed beneath the top printed circuit board 7200.
FIG. 74 shows an exemplary third printed circuit board (or third
layer of a multi-layer printed circuit board) 7400 according to an
embodiment of the present disclosure. The third printed circuit
board 7400 is disposed beneath the second printed circuit board
7300. FIG. 75 shows an exemplary bottom printed circuit board (or
bottom layer of a multi-layer printed circuit board) 7500 according
to an embodiment of the present disclosure. The bottom printed
circuit board 7500 is disposed beneath the third printed circuit
board 7400.
[0177] Some embodiments provide that a mobile application can be
downloaded onto the host mobile device 110 to provide a graphical
user interface that can be used, for example, to control the mobile
device cover 100. The mobile application can run on the host mobile
device 110 and/or the mobile device cover 100. The graphical user
interface can be on the host mobile device 110 and/or the mobile
device cover 100. Further, the mobile application can be
automatically or manually updated, upgraded, modified, replaced,
overwritten, supplemented, etc. via a wireless or wired
connection.
[0178] FIGS. 3 and 4 show an exemplary launch screen page 300 and
an exemplary front page 400 according to an embodiment of the
present disclosure. The mobile application can be represented as an
icon (e.g., a graphical element of a graphical user interface) on
the display (e.g., screen) of the host mobile device 110 and/or the
mobile device cover 100. When the icon is selected, the mobile
application runs on the host mobile device 110 (and/or the mobile
device cover 100) and a launch page 300 as shown in FIG. 3 is
displayed by the host mobile device 110 (and/or the mobile device
cover 100). Subsequently, a front page 400 as shown in FIG. 4 is
displayed. While the front page 400 is being displayed, the mobile
application attempts to wirelessly and/or wiredly connect the host
mobile device 110 and the mobile device cover 100 according to an
embodiment of the present disclosure. In one embodiment, the mobile
application attempts to wirelessly pair the mobile device cover 100
and the host mobile device 110, which are both Bluetooth-enabled.
If the mobile application is not successful in making a connection
(e.g., a connection between previously paired devices 100, 110),
then a connection page 500 is opened as shown in FIG. 5, or an
alternative connection method can be established via, for example,
a USB-type connection, WiFi connection, Bluetooth connection,
Zigbee connection, etc. If a successful connection is made, then an
exemplary home page 700 is opened as shown in FIG. 7. If the
connection is lost, then the mobile application opens the front
page 400 or the connection page 500.
[0179] By selecting the pair icon 410 (e.g., graphical button)
shown in FIG. 4, an exemplary connection page 500 according to an
embodiment of the present disclosure as shown in FIG. 5 is opened
that allows for configuring wireless and/or network connections.
The connection page 500 enables the user to select a device for
pairing (e.g., a mobile device cover 100) and/or a network for
connection. The list 520 of devices can be refreshed by a user
gesture such as a swipe, for example, otherwise, the list is
refreshed periodically. In some embodiments, selecting a particular
device such as a mobile device cover 100, for example, initiates a
verification process such as a pin verification process, for
example. After a prompt from the mobile application, entry of the
correct pin (e.g., supplied by the mobile device cover 100) within
a particular time limit or by a particular number of attempts
causes the mobile application to open the home page 700 shown in
FIG. 7. Configuring of the mobile application and/or the mobile
device cover 100 can occur based on a selection or an input of a
particular model number or particular type of mobile device cover
100. Incorrect entry of the pin number within the particular time
limit or after a particular number of failed attempts causes the
mobile application to open the front page 400 or the connection
page 500. By selecting a back icon 510, for example, the mobile
application navigates to the front page 400, the connection page
500, or a previous page.
[0180] By selecting the information icon 420 (e.g., an "i" icon) in
FIG. 4, an exemplary instructions page 600 according to an
embodiment of the present disclosure as shown in FIG. 6 is opened
which provides descriptions and helpful information about various
items being displayed, for example, on a push button or element
selectable menu. By tapping or toggling the back icon 610 (e.g.,
back graphical button), for example, by making a gesture on the
screen (e.g., swiping left to right on the screen), or by moving
the mobile device cover 100 and/or host mobile device 110 in a
particular way, the home page 700 as shown in FIG. 7 or a previous
page can be opened.
[0181] FIG. 7 shows an exemplary home page 700 according to an
embodiment of the present disclosure. In some embodiments, upon
successful connection and pairing, the mobile application displays
a home page 700 as shown in FIG. 7. The home page 700 provides a
graphical user interface by which the user can further navigate the
mobile application. Referring to FIG. 7, the home page 700 includes
icons or hyperlinks to open, for example, a phone page, a messages
page, an email page, a notifications-for-applications page, a
lighting-for-contacts page, a battery page, a lighting page, a back
design page, and a settings page. In addition, the home page 700
provides for controlling a brightness (e.g., via a brightness
slider 710) of a display and/or a volume for a speaker for the
mobile device cover 100 and/or the host mobile device 110. In some
embodiments, the home page 700 provides an icon 720 (e.g., a
graphical element) that can be toggled on or off as to whether to
display incoming notifications on the mobile device cover 100, for
example.
[0182] In some embodiments, the mobile application enables the user
with the ability to set up a particular lightshow, a particular
icon (e.g., an icon, an emoji, a custom-designed graphical
element), and/or a particular text (e.g., scrolling text) to be
displayed for a particular type of communication (e.g., phone,
message, email. etc.), a particular contact, and/or a particular
type of communication (e.g., phone, message, email, etc.) for that
particular contact on a contact list stored in the host mobile
device 110 and/or the mobile device cover 100. The mobile
application also enables the user to customize the selected
lightshow, icon, text, etc.
[0183] By selecting the phone icon 730 on the home page 700, a
phone page 800 according to an embodiment of the present disclosure
is opened as shown in FIG. 8. In some embodiments, a messages page
and an email page are opened by selecting the message icon 735 and
the email icon 745, respectively, of the home page 700 and operate
in a similar manner as the phone page 800. In some embodiments,
after the phone icon 730 is selected, a lightshows page 810 (e.g.,
for phone notifications) is first shown for the phone page 800 as
in FIG. 8; however, other selectable options including an icons
page and a scrolling text page can also be opened by selecting the
corresponding icons 820, 830 (e.g., graphical buttons or tabs).
Referring to FIG. 8, the lightshows page 810 provides one or more
graphical elements on a graphical user interface that enable the
user to select a particular lightshow (e.g., flare) from a list of
lightshows that can be assigned, for example, to a particular
contact. Parameters for the lightshows are also selected. For
example, a speed and a duration are set (e.g., via graphical
sliders 840, 850 as shown in FIG. 8) for the selected lightshow,
which includes animation, for example. Other adjustable or
selectable parameters can include light intensity, colors, size,
pulsing, bursting, etc. The selected lightshow with any selected
particular lightshow parameters is assigned to a particular contact
(e.g., phone contact, phone number, etc.), and this information is
sent to the mobile device cover 100, for example. The assignments
are stored in the mobile device cover 100, the host mobile device
110, and/or the mobile application. The lightshows page 810
provides an icon 860 (e.g., a preview-on-case icon) that, when
selected, causes the mobile device cover 100 to demonstrate the
currently selected lightshow according to the selected lightshow
parameters on the LEDs (or other lights or lighting devices) and/or
on one or more screens of the mobile device cover 100. In some
embodiments, the lightshows page 810 can provide an icon (e.g., a
preview-in-the-mobile application icon) or can automatically
display in a portion 870 of the lightshows page 810 or in a
separate page of the mobile application, a preview of the selected
lightshow according to the set lightshow parameters. For example,
the mobile application can provide a separate preview page or
preview section 870 as shown in FIG. 8 of the lightshows page 810
that shows the selected lightshow according to the selected
settings (e.g., with any selected animation at a particular speed
for a particular duration) on an image of the mobile device cover
100 according to the selected model and/or other characteristics
(e.g., a blue back design or color). The preview in the mobile
application can provide the user with a preview of the selected
lightshow and lightshow options (e.g., on the host mobile device
110) without necessarily demonstrating the lightshow on the LEDs
and/or screen of the mobile device cover 100. However, the preview
in the mobile application (e.g., on the host mobile device 110) can
also be played concurrently or separately from with a preview on
the case (e.g., a preview using the LEDs and/or screen of the
mobile device cover 100). In some embodiments, the lightshows page
810 provides an icon that, when selected, enables a user to
download or purchase (e.g., as part of an in-application purchases
page) additional lightshows or features. In some embodiments,
clicking on a share icon enables the user to share the particular
lightshow, icon, and/or scrolling text with others (e.g., friends,
selected individuals, contacts, etc.). The sharing can be
facilitated via a wired and/or wireless communication or transfer,
a text, an email, a social media post or communication, etc. as
text, a file, a graphics interchange format (GIF) file, an image, a
video, a picture, a file stored in camera roll, etc. Selecting the
back button 880 (or other actions such as backwards swipes) brings
back the home page 700 or a previous page. Selecting (e.g., tapping
or some other user input) on the assigned contacts button or link
890 causes an assigned contacts page 900 to open as shown in FIG.
9.
[0184] FIG. 9 shows an exemplary assigned contacts page 900
according to an embodiment of the present disclosure. The assigned
contacts page 900 enables the user to view and select a particular
lightshow (e.g., light pattern, lightshow, animation, etc.) for
assignment (e.g., assignment or re-assignment). In some
embodiments, a lightshow includes a series of images that are
displayed on the mobile device cover 100 and/or the mobile
application. The assigned contacts page 900 also enables the user
to view the currently assigned lightshow for a particular
notification category (e.g., email, message, phone, etc.). Further,
the assigned contacts page 900 can also identify duplicate
lightshow assignments. Colors or other indicators enable the user
to easily see duplicate assignments. Referring to FIG. 9, the Halo
lightshow, which is shown as a red button 910, is assigned both to
contacts Adam Fee and Abc Xyz. The particular colors used are
merely exemplary. The Star lightshow, which is shown as a blue
button 920, is uniquely assigned to Amanda Bee. The email icon, the
message icon, the phone icon, and the Happy icon, which are shown
as green buttons 930, indicate uniquely assigned icons for emails
generally, messages, phone calls generally, and Ally Arm. Selecting
the back button 940 (or other actions such as backwards swipes)
brings back a previous page (e.g., the lightshows page 810).
[0185] Selecting the icons button 820 (e.g., graphical tab) at the
top of the phone page 800 shown in FIG. 8 opens an exemplary icons
page 1000 according to an embodiment of the present disclosure as
shown in FIG. 10. The icons page 800 of the mobile application
enables the user to select a particular icon, icon parameters,
and/or animation for assignment (e.g., assignment or
re-assignment). Selecting a particular icon such as, for example,
the phone icon 1010 as shown in FIG. 10, causes the mobile
application to display the phone icon as it would look when
displayed on the mobile device cover 100 on a portion 1020 of the
page 1000 or on a separate page. Information relating to the
selection of the phone icon 1010 including any icon parameters and
assignments is sent to the mobile device cover 100. By selecting
the animations button 1030, different types of animations are
listed for application to the phone icon, for example. In some
embodiments, the list includes only those animations that are
applicable for the selected icon. In some embodiments, the
animations can include moving across the screen, pulsating,
bursting, dynamically changing colors, rotating, dynamically
changing in size, etc. Selecting an icon parameter such as, for
example, an animation, causes the mobile application to display the
selected icon on a portion 1020 of the display according to the
selected animations and/or icon parameters, and to send the
icon-related information to the mobile device cover 100. Icon
parameters such as a speed and a duration are set (e.g., via
graphical sliders 1040, 1050 as shown in FIG. 10) for the selected
icon and the applied animation. In some embodiments, the icons page
1000 provides an icon 1060 (e.g., a preview-on-case icon) that,
when selected, causes the mobile device cover 100 to demonstrate
the currently selected icon according to the selected parameters
and/or animations on the mobile device cover 100 as shown in FIG.
25C, for example. For example, the lights 160 (e.g., LEDs, screens,
etc.) of the mobile device cover 100 light up according to the
selected icon, animations, and/or parameters to preview the
response of the mobile device cover 100 for the particular
assignment (e.g., a particular contact, type of communication, type
of notification, alert, etc.). In some embodiments, the icons page
1000 can provide an icon (e.g., a preview-in-the-mobile application
icon) or can automatically display in a portion 1020 of the icons
page 1000 as in FIG. 10 or 25A, or in a separate page 2500 of the
mobile application as in FIG. 25B, a preview of the selected
lightshow according to the set lightshow parameters. The preview
changes as the user makes changes. The mobile application can also
provide a separate preview page 2500 as shown in FIG. 25B or
preview section 1020 as shown in FIG. 10 (or FIG. 25A) of the icons
page 1000 that shows the selected icon according to the selected
settings (e.g., with any selected animation at a particular speed
for a particular duration) on an image of the mobile device cover
100 according to the selected model and/or other characteristics
(e.g., a blue back design or color). The preview in the mobile
application can provide the user with a preview of the selected
icon and icon options (e.g., on the host mobile device 110) without
necessarily demonstrating the icon on the LEDs and/or screen of the
mobile device cover 100. However, the preview in the mobile
application (e.g., on the host mobile device 110) can also be
played concurrently with a preview on the case (e.g., a preview
using the LEDs and/or screen of the mobile device cover 100) as
shown in FIG. 25C. In some embodiments, clicking on a share icon
enables the user to share the particular lightshow, icon, and/or
scrolling text with others (e.g., friends, selected individuals,
contacts, etc.). The sharing can be facilitated via a wired and/or
wireless communication or transfer, a text, an email, a social
media post or communication, etc. as text, a file, a graphics
interchange format (GIF) file, an image, a video, a picture, a file
stored in camera roll, etc. Selecting the back button 880 (or other
actions such as backwards swipes) brings back the home page 700 or
a previous page.
[0186] In some embodiments, the icons page 1000 provides an icon
that, when selected, enables a user to download or purchase (e.g.,
as part of an in-application purchases page) additional icons or
features. Selecting the back button 1070 (or other actions such as
backwards swipes) brings back the home page 700 or a previous
page.
[0187] Selecting the scrolling text button 830 (e.g., graphical
tab, graphical element, etc.) at the top of the phone page 800
shown in FIG. 8 or the scrolling text button 1080 at the top the
icons page 1000 shown in FIG. 10 opens an exemplary scrolling text
page 1100 according to an embodiment of the present disclosure as
shown in FIG. 11A. The scrolling text page 1100 enables the user to
select a text and/or a scrolling text and/or scrolling text
parameters for assignment (e.g., assignment or re-assignment).
Selecting text, scrolling text, and/or scrolling text parameters
causes the mobile application to send the selected text, scrolling
text, and/or scrolling text parameters to the mobile device cover
100. Referring to FIG. 11B, an exemplary scrolling text page 1105
is shown with a preview pane 1115 that enables the viewing of the
scrolling text (e.g., customized scrolling text, preset scrolling
text, etc.). The speed and text can be changed using the scrolling
text page 1105. Further, as will be explained below with respect to
FIGS. 25D-E, for example, the font and the orientation of the
scrolling text can be changed and previewed. The preview changes as
the user makes changes to the scrolling text. The preview pane 1115
can also be a pop-up window or a separate page. The previewed pane
1115 can also illustrate various changes in the scrolling text on a
representation of a selected model of the mobile device cover 100.
Further, the previewed display can also be actually displayed on
the mobile device cover 100 to view the display (e.g., scrolling
text display) in view of any scrolling text changes, for example.
In some embodiments, clicking on a share icon 1125 enables the user
to share the scrolling text (and/or particular lightshow, icon,
etc.,) with others (e.g., friends, selected individuals, contacts,
etc.). The sharing can be facilitated via a wired and/or wireless
communication or transfer, a text, an email, a social media post or
communication, etc. as text, a file, a graphics interchange format
(GIF) file, an image, a video, a picture, a file stored in camera
roll, etc.
[0188] By selecting an icon 1110 (e.g., a plus icon), an exemplary
add item page 1200 according to an embodiment of the present
disclosure is opened as shown in FIG. 12. The add item page enables
a user to select text options for scrolling on the mobile device
cover 100. Referring to FIG. 12, a user can add words, symbols,
names, a phone type, and/or a phone character for scrolling. A user
can cause the word "Call" to scroll across the mobile device cover
100 as part of a phone call notification or as part of a calendar
alert, for example. In addition, different options for scrolling
the name of the caller are available such as the full name, first
name, first name and remaining name in initials, all initials, etc.
Furthermore, the user can add a phone type, a phone character, or
some other customized graphics for scrolling across the mobile
device cover 100 as part of a notification, for example. Selecting
the back button 1210 (or other actions such as backwards swipes)
brings back the scrolling text page 1100.
[0189] Referring back to FIG. 11, further options for scrolling
include changing the order and appearance of words, names, phone
type, phone character, and/or icon for scrolling. The order of
these options can be changed, for example, by moving the particular
category of information being scrolled into a different position in
the display order 1120 by selecting and moving the three lined icon
1130. The scrolling text page 1100 enables, via one or more
graphical elements 1140, a user to display the icon before or after
the scrolling text, or not at all. The scrolling text page 1100
further enables the user to select a type of separator, via a
selection menu 1150, between different categories (e.g., name,
phone character, phone type, etc.) for scrolling. For example, the
separator can be one or more lines or spaces between different
categories (e.g., phone character, name, phone type, icon, etc.).
In addition, the scrolling text page 1100 provides for the user to
determine, via selection menus 1160, 1170, the number of display
repetitions (e.g., one, two, three, etc.) of the scrolling message
and a scroll speed. In some embodiments, the scrolling text page
1100 provides an icon 1180 (e.g., a preview-on-case icon) that,
when selected, causes the mobile device cover 100 to demonstrate
the currently selected scrolling text and/or icon according to the
selected scrolling text parameters and/or animations on the mobile
device cover 100. In some embodiments, the mobile application can
preview the scrolling text on the host mobile device 110, for
example, as part of the lightshows page 810, the icons page 1000,
the scrolling text page 1100, or a separate page, the selected
scrolling text with or without accompanying icons or lightshows
according to the scrolling text parameters and/or other parameters
as it would appear on the mobile device cover 100. For example, the
mobile application can provide a preview page that includes an
image of the mobile device cover 100 (e.g., the selected model
including color and other characteristics of that model of the
mobile device cover 100) with the scrolling text as it would appear
on the mobile device cover 100 during a notification or other
display, for example. Selecting the back button 1190 (or other
actions such as backwards swipes) brings back the home page 700 or
a previous page.
[0190] In some embodiments, by selecting a
notifications-for-applications button or link 740 (e.g., graphical
element in a graphical user interface, the text "Notifications for
App," etc.) on the home page 700 as shown in FIG. 7, an exemplary
notifications-for-applications page 1300 is opened as shown in FIG.
13. The notifications-for-applications page 1300 enables users to
view and change settings for applications for which the mobile
application and the mobile device cover 100 support custom
notifications. Referring to FIG. 13, a list of applications 1310 is
shown for which the mobile application and the mobile device cover
100 support notifications. Some embodiments provide that the list
of mobile applications include the mobile application installed on
the host mobile device 110, any of the user's other host mobile
devices or mobile devices, the mobile device cover 100, etc. For
each listed application, the user can select (e.g., tap, toggle,
etc.) various options. In some embodiments, a button or icon (e.g.,
a graphical element of a graphical user interface) is provided to
turn on or off a particular notification parameter. Referring to
FIG. 13, for each listed application, a graphical button 1320 is
provided to turn on or off the displaying of notifications from the
calendar application on the mobile device cover 100, for example. A
graphical button 1330 is also provided for each listed application
to turn on or off the displaying of the respective application name
(e.g., Amazon, Calendar, etc.) on the mobile device cover 100 when
the mobile application receives a notification for the respective
application. A graphical button 1340 is provided for each listed
application to turn on or off the displaying of a particular icon
(e.g., application icon, customized icon, emoji, etc.)
corresponding to the respective application when the mobile
application receives a notification for the respective application.
In addition, a graphic button 1350 is provided for each listed
application to turn on or off the displaying of the contents of a
notification (e.g., scrolling the contents of a notification on the
mobile device cover 100, text or media from an email, a message, a
textual alert, a sound, a transcription of a voicemail, etc.) when
the mobile application receives the notification for the respective
application. The notifications-for-applications page also provides
a search bar 1360 for searching for applications by name, for
example. Selecting the back button 1370 (or other actions such as
backwards swipes) brings back the home page 700 or a previous
page.
[0191] In some embodiments, by selecting a lighting-for-contacts
button or link 750 (e.g., graphical element in a graphical user
interface, the text "Lighting for Contacts," etc.) on the home page
700 as shown in FIG. 7, an exemplary lighting-for-contacts page
1400 is opened as shown in FIG. 14. The lighting-for-contacts page
1400 enables users to view and assign lightshows, icons, scrolling
text, etc. for display on the mobile device cover 100, for example.
Referring to FIG. 14, by selecting (e.g., tapping or some other
user input) a contact name 1410 or a graphical button 1420
indicating an assigned lightshow, icon, etc., a
lightshows-for-contacts page 1500 or an icon-for-contacts page 1600
is opened as shown in FIG. 15 or 16, respectively. In some
embodiments, swiping left to right or right to left on the contact
name 1410 or the graphical button 1420 indicating an assigned
lightshow or icon, for example, causes the removal of the
particular contact and/or the lightshow or icon assignment for a
particular contact. The screen including the data displayed on the
screen can be refreshed continuously, periodically, or
aperiodically by a gesture (e.g., a swipe up or down, selecting a
graphical element, etc.) on the screen. Selecting the back button
1430 (or other actions such as backwards swipes) brings back the
home page 700 or a previous page.
[0192] FIG. 15 shows an exemplary lightshows-for-contacts page 1500
according to an embodiment of the present disclosure. In
particular, by selecting the contact name, e.g., Hank Williams, or
a graphical button indicating a lightshow assigned to Hank Williams
on the lighting-for-contacts page 1400, the exemplary
lightshows-for-Hank-Williams page 1510 opens as shown in FIG. 15.
The lightshows-for-contacts page 1500 enables a user to change the
lightshow and lightshow parameters assigned to a particular
contact. The current lightshow for Hank Williams is listed as the
Star lightshow 1520; however, other lightshows can be selected
(e.g., by tapping or toggling on the lightshow name such as "Nova")
from the lightshows list 1530 for assignment to Hank Williams.
Parameters for the selected lightshow such as a speed (e.g., speed
of an animation of the lightshow) and a duration of the lightshow
care are controlled by sliding controls 1540, 1550 (e.g., graphical
sliders). Data relating to the selected lightshow and lightshow
parameters is sent to the mobile device cover 100. The selected
lightshow is shown or previewed on a portion 1560 of the
lighting-for-contacts page 1500 including any selected animations
in accordance with any selected lightshow parameters. The preview
also reflects the selected model including color or other
characteristics (e.g., arrangement of LEDs or screens, resolution,
etc.) of the selected model of the mobile device cover 100 so that
the user can see how the lightshow looks on the selected model of
the mobile device cover 100. The lightshows-for-contacts page 1500
also provides an icon 1570 (e.g., a preview-on-case icon) that,
when selected, causes the mobile device cover 100 to demonstrate
(e.g., actually display on the mobile device cover 100, cause LEDs
of the mobile device cover 100 to light according to the lightshow,
animations, and parameters, cause screens of the mobile device
cover 100 to display according to the lightshow, animations, and
parameters, etc.) the currently selected lightshow including any
selected animations according to any selected lightshow parameters.
Selecting (e.g., tapping or some other user input) on the assigned
contacts button or link 1580 causes the assigned contacts page 900
to open. In some embodiments, the lightshows-for-contact page 1500
provides an icon that, when selected, enables a user to download or
purchase (e.g., as part of an in-application purchases page)
additional lightshows or features. Selecting the back button 1590
(or other actions such as backwards swipes) brings back the home
page 700 or a previous page.
[0193] FIG. 16 shows an exemplary icons-for-contacts page 1600
according to an embodiment of the present disclosure. In
particular, by selecting the contact name, e.g., Hank Williams, or
a graphical button indicating an icon assigned to Hank Williams on
the lighting-for-contacts page 1400, the icons-for-Hank-Williams
page 1610 opens as shown in FIG. 16. Alternatively, if the
lightshows-for-Hank-Williams page 1510 is already opened as shown
in FIG. 15, then selecting the icons button 1595 (e.g., graphical
tab) also opens the icons-for-Hank-Williams page 1610. The
icons-for-contacts page 1600 enables a user to change the icon
(e.g., an icon, an emoji, a graphical element, a custom-designed
graphical element, a downloaded graphical element, a stored
graphical element, etc.) and icon parameters assigned to a
particular contact and/or for a particular type of notification for
the particular contact. For example, in addition to speed and
duration parameters, the icons-for-contacts page 1600 can also add
animation to the icon. Other parameters that can be changed
include, for example, parameters that change the color, size,
intensity, pulsating, bursting, etc. of the icon. The information
indicating the selected icon and icon parameters is sent to the
mobile device cover 100. The selected icon is shown or previewed on
a portion 1620 of the icons-for-contacts page 1600 (or on a
separate page) including any selected animations in accordance with
any selected icon parameters. The preview also reflects the
selected model including color or other characteristics (e.g.,
arrangement of LEDs or screens, resolution, etc.) of the selected
model of the mobile device cover 100 so that the user can see how
the displayed icon looks on the selected model of the mobile device
cover 100. The icons-for-contacts page 1600 also provides an icon
1630 (e.g., a preview-on-case icon) that, when selected, causes the
mobile device cover 100 to demonstrate (e.g., actually display on
the mobile device cover 100, cause LEDs of the mobile device cover
100 to light according to the icon, animations, and parameters,
cause screens of the mobile device cover 100 to display according
to the icon, animations, and parameters, etc.) the currently
selected icon with any selected animations according to any
selected icon parameters. Selecting (e.g., tapping or some other
user input) on the assigned contacts button or link 1640 causes the
assigned contacts page 900 to open. In some embodiments, the
lightshows-for-contact page provides an icon that, when selected,
enables a user to download or purchase (e.g., as part of an
in-application purchases page) additional icons or features.
Selecting the back button (or other actions such as backwards
swipes) brings back the home page 700 or a previous page (e.g., the
lightshows-for-contacts page).
[0194] FIG. 17 shows an exemplary battery page 1700 according to an
embodiment of the present disclosure that is opened, for example,
when the battery icon or link 760 on the home page 700 is selected.
The battery page 1700 enables a user to view and change the battery
settings of mobile device cover 100 and/or the host mobile device
110. For example, the battery page 1700 enables a user to turn on
an autocharging feature of the mobile application. The user can set
a start automatic charging parameter and a stop automatic charging
parameter. The parameters can be, for example, battery charge
percentages of the mobile device cover 100 battery or the host
mobile device 110 battery. In an exemplary embodiment, a full
battery charge is 100% and an exhausted battery charge is 0%, for
example. In addition to battery charge percentages, the parameters
can be in units of energy, charge, power, capacity, etc. Each
parameter is set by selecting (e.g., tapping, toggling, or some
other user input) the increase ("+") or decrease ("-") graphical
buttons 1710 which incrementally increases or decreases the
respective parameter accordingly. In some embodiments, when the
mobile application senses that the battery charge percentage of the
host mobile device 110 battery has dropped to or below the start
automatic charging parameter, then the mobile application causes
the mobile device cover 100 battery to charge the host mobile
device 100 battery until the stop automatic charging parameter is
reached. In some embodiments, similar automatic charging parameters
are used by the mobile application to also cause the host mobile
device 110 battery to charge the mobile device cover 100 battery.
The parameters and information relating to whether the automatic
charging feature enabled is sent by the mobile application to the
mobile device cover 100 and/or the host mobile device 110. By
selecting the manual tab 1770, the battery page 1700 also enables
to user to initiate manual battery charging by selecting one
battery (e.g., the mobile device cover 100 battery) to charge
another battery (e.g., the host mobile device 110 battery)
according to a selectable condition (e.g., battery charge,
duration, etc.). The battery page 1700 also displays the battery
charge or battery charge percentages 1720, 1730 of the batteries of
the mobile device cover 100 and the host mobile device 110,
respectively. When either battery is being charged, a charging icon
1740 is displayed over the battery FIG. 1750 or over the portion
1760 of the battery FIG. 1750 representing the battery that is
being charged. Selecting the back button 1780 (or other actions
such as backwards swipes) brings back the home page 700 or a
previous page.
[0195] FIG. 18 shows an exemplary lighting page 1800 according to
an embodiment of the present disclosure that is opened, for
example, when the lighting icon or link 770 on the home page 700 is
selected. The lighting page 1800 enables a user to set lighting
settings for the mobile application and the mobile device cover
100. The lighting page lists a number of lighting options 1810
(e.g., flashlight, softlight, reading light, strobe light, panic
light, etc.), the order of which can be changed by dragging the
respective three lines icon 1820 corresponding to the lighting
option to the appropriate place in the list. By selecting one of
the lighting options (e.g., flashlight, softlight, panic light,
etc.), the respective light parameters 1830 (e.g., brightness via
slider 1840, duration via incremental adjustment buttons 1850,
1855, etc.) of the selected lighting option is viewed and can be
modified. The mobile device cover 100 and/or the mobile application
can operate according to one or more light options for a select
time and/or duration, the one or more light options provided by the
mobile device cover 100 including: a flashlight; a soft light; a
panic light (e.g., a bright bursting light that may accompany a
piercing sound); a selfie light (e.g., a soft ring of light to
naturally illuminate a face during a selfie and used in
conjunction, for example, with a camera of the host mobile device
110 or an external camera); a reading light (e.g., an adjustable
light for reading); a strobe light; icons (e.g., static or animated
icons including emojis displayed by one or more LEDs or on one or
more screens); light shows; light patterns; scrolling text (e.g.,
favorite proverb or saying); and a clock. By selecting a respective
icon (e.g., an "i" icon 1860), a corresponding page (e.g., clock
page, lightshows page, icons page, etc.) opens. Referring to FIG.
18, when the flashlight option is selected, the mobile device cover
100 operates as a flashlight by one or both of turning on selected
LEDs or turning on one or more screens to a particular brightness
and/or hue, for example. The "on" and "off" tabs 1870, 1875 (e.g.,
icons, graphical elements, etc.) turn the flashlight on or off,
respectively. The brightness and duration of the flashlight option
can be set by a graphical slider 1840 or incremental adjustment
icons (e.g., "+" icon 1850 and "-" icon 1855). The various options
of the lighting page 1800 can be previewed in the mobile
application (e.g., a portion of the lighting page 1800 or a
separate page) and/or on the mobile device cover 100 (and host
mobile device 110). As with all features described in the present
disclosure, the mobile device cover 100 operates whether physically
connected to host mobile device 110 or physically separated from
the host mobile device 110. Selecting the back button 1880 (or
other actions such as backwards swipes) brings back the home page
700 or a previous page.
[0196] In some embodiments, the lighting page 1800 provides the
setup of a panic light, panic alert, hazards, blinkers, etc. For
example, for use in an emergency situation, a user can enable the
lighting page to set up a panic alert. The panic alert can be
activated by a graphical button on the lighting page 1800 or on a
home screen of the host mobile device 110, or a physical button on
the host mobile device 110. The panic alert can also be activated
by a graphical button on a screen or a physical button on the
mobile device cover 100. The panic alert can include, for example,
a panic light that is a light pattern at the highest intensities in
a pattern (e.g., bursting light pattern, full LED on/off blue or
other light pattern) configured to draw the most attention to the
user and/or to disorient an attacker of the user, for example.
Further, the panic alert can be accompanied with a loud sound or
voice that is broadcast over the speakers of the mobile device
cover 100 and/or the host mobile device 110. The sound or voice is
configured to draw the most attention to the user and/or to
disorient an attacker of the user, for example. The panic alert can
also include, with or without a prompt, the dialing of an emergency
phone number (e.g., police department, security system, emergency
contact, etc.) and other configurations such as turning on the
speaker phone. Other options of the panic alert can include, for
example, the sending of text messages to various contacts notifying
the various contacts of the emergency situation. The messages
and/or phone call can include location information (e.g., via a
satellite-based location determining system such as GPS and/or a
ground-based location determining system) or other data to direct
responders to the user location. The camera on the host mobile
device 110 can be activated during a panic alert to take pictures
at selected intervals and/or to take one or more movies, which can
be sent automatically and/or stored. These options can be set up
for the panic light link on the lighting page 1800 that can open up
a menu or a separate page for these panic alert settings and/or
parameters.
[0197] FIG. 19 shows an exemplary clock page 1900 according to an
embodiment of the present disclosure that is opened, for example,
when the clock icon or link 1885 (e.g., the "Clock" link) on the
lighting page 1800 is selected. The clock page 1900 enables a user
to set clock settings for display by the mobile device cover 100.
Referring to FIG. 19, different clock faces 1910 can be selected,
for example, by swiping the clock face menu options (e.g., vertical
view, horizontal view, portrait view, landscape view, stop watch
view, etc.). Different parameters 1920 can be set by corresponding
icons (e.g., graphical toggle switches 1930). For example, the
following parameters can be set to affect the clock display on the
mobile device cover 100: 12-hour time format, 24-hour time format,
displaying leading zeroes, blinking colon, etc. Further, custom
fields can be selected and/or set. For example, custom fields can
be used to further display and/or set calendar information, time
zone information, additional time zone information times,
highlighted world time zone map, etc. In some embodiments, the
clock page provides an icon 1940 (e.g., a preview-on-case icon)
that, when selected, causes the mobile device cover 100 to
demonstrate the currently selected clock according to the selected
clock face and other clock parameters on the mobile device cover
100. Selecting the back button 1950 (or other actions such as
backwards swipes) brings back the home page 700 or a previous page
(e.g., the lighting page 1800).
[0198] FIG. 20 shows an exemplary back design page 2000 according
to an embodiment of the present disclosure that is opened, for
example, when the back design icon or link 780 (e.g., icon and/or
"Lighting" link) on the home page 700 is selected. The back design
page 2000 enables a user to select a particular back design and/or
mobile device cover 100 model. Referring to FIG. 20, a listing 2010
of back designs can be viewed by swiping up or down, for example,
on a touch-sensitive screen of the host mobile device 110.
Selection of a particular back design occurs by selecting (e.g.,
tapping, toggling, or some other user input) the particular back
design graphic 2020 or the back design description 2030 (e.g., the
"Blue" link). The selection of the particular back design and/or
mobile device cover 100 model affects the available lightshows,
icons, animations, etc. that are adjustable for the selected back
design and/or mobile device cover 100 model. For example, each
mobile device cover 100 model and/or particular back design can
have its own arrangement of lights (e.g., LEDs, indicators, etc.),
screens, and/or features. Accordingly, the available lightshows,
icons, animations, etc. available for display on the light
arrangements and/or screens of the selected mobile device cover 100
model and/or back design vary according to the selected mobile
device cover 100 model and/or back design. Further, the mobile
application uses the selected mobile device cover 100 model
and/back design when displaying selected lightshows, icons,
animations, etc. during a preview, for example. For example, when
the mobile application is running on the host mobile device 110,
the host mobile device 110 can preview the selected lightshow,
icons, animations, etc. using a page (e.g., lightshows page,
lightshows-for-contacts page, icons page, a preview page, etc.) of
the mobile application. The graphical preview provided by a page of
the mobile application incorporates the selected mobile device
cover 100 model and/or back design (e.g., structural features,
colors, etc.). Selecting the back button 2040 (or other actions
such as backwards swipes) brings back the home page 700 or a
previous page.
[0199] FIG. 21 shows an exemplary settings page 2100 that is
opened, for example, when the settings icon or link 790 (e.g.,
settings icon or "Settings" link") on the home page 700 is
selected. The settings page 2100 enables a user to view and change
general settings and other settings. For example, the settings page
2100 can be used to change fonts, languages, display orientation,
etc. via its graphical user interface. Referring to FIG. 25D, an
exemplary scrolling text fonts page 2530 is shown with a preview
pane 2535 that enables the viewing and/or selection of different
fonts such as, for example, rounded, condensed, boxed, and other
font choices that are not shown. By a swipe or other gesture on a
screen, for example, other font choices can be viewed. Further, the
option of all text being in capitals is provided. The preview pane
2535 can also be a pop-up window or a separate page. The previewed
pane 2535 can also illustrate various changes in fonts on a
representation of a selected model of the mobile device cover 100.
Further, the previewed display can also be actually displayed on
the mobile device cover 100 to view the display (e.g., scrolling
text display) in view of any font changes, for example. Referring
to FIG. 25E, an exemplary scrolling orientation page 2550 is shown
with a preview pane 2555 that enables the viewing and/or selection
of different orientations (e.g., whether the text scrolls up, down,
left, right, whether the text is in landscape or portrait format,
etc.) for the scrolling text. The preview pane 2555 can also be a
pop-up window or a separate page. The previewed pane 2555 can also
illustrate various changes in orientation on a representation of a
selected model of the mobile device cover 100. Further, the
previewed display can also be actually displayed on the mobile
device cover 100 to view the display (e.g., scrolling text display)
in view of any orientation changes, for example. Some embodiments
provide that the host mobile device 110 and/or the mobile device
cover 100 can determine, for example, whether the host mobile
device 110 and/or the mobile device cover 100 is upside down or
some other orientation, for example, via an internal gyroscope
and/or accelerometer, for example, and automatically re-orient the
displayed information accordingly so that the displayed information
is easily read by a user.
[0200] Referring back to FIG. 21, respective icons 2110 (e.g.,
graphical switches or graphical elements that can be selected or
toggled) are selected to turn on or off corresponding categories of
notifications. For example, phone notifications, message
notifications, email notifications, alerts, application
notifications, or other notifications supported and displayed on
the mobile device cover 100 and/or the host mobile device 110 can
be turned on or off. Further, by selecting an icon or link 2120,
2130, 2140 on the settings page 2100, a
notifications-for-applications page 2200, a lightshows-for-contacts
page 2300, a synchronization/reset page 2400, etc. can be opened.
The settings page 2100 also provides icons or links 2150, 2160 that
open an about page, a test functions page, and other settings
pages. The about page enables the user to view model or version
details of the mobile application and/or the mobile device cover
100. In addition, an icon or link 2170 is provided to facilitate
the update of the mobile application on the host mobile device 110
and/or the mobile device cover 100, and the software and/or
circuitry on the mobile device cover 100. Selecting the back button
2180 (or other actions such as backwards swipes) brings back the
home page 700 or a previous page.
[0201] FIG. 22 shows an exemplary notifications-for-applications
settings page 2200 according to an embodiment of the present
disclosure that is opened, for example, when the
notifications-for-applications icon or link 2120 on the settings
page 2100 is selected. The notifications-for-applications settings
page 2200 enables a user to view and make changes (e.g., generally
or specifically) to parameters governing the display of application
notifications on the mobile device cover 100. Referring to FIG. 22,
various parameters can be set by the user. For example, the user
can generally (or specifically) enable or disable, via a graphical
switch 2210, the application notifications being shown on the
mobile device cover 100 for phone notifications, message
notifications, email notifications, application notifications, etc.
When enabled, the user can then set other general or specific
parameters for the application notifications. The
notifications-for-applications settings page 2200 provides the user
with an icon 2220 (e.g., graphical switch or graphical element that
can be tapped or toggled) that causes icons (e.g., icons, emojis,
graphical designs, animations, lightshows, light icons, scrolling
text, etc.) to be included or not included during an application
notification displayed on the mobile device cover 100. Other
parameters for general or specific application notifications that a
user can view and modify include turning on/off animations 2230
and/or text scrolling, and setting a scroll speed 2240, a type of
separator 2250 between text and/or icons, a number of repeat times
2260, etc. Selecting the back button 2270 (or other actions such as
backwards swipes) brings back the home page 700 or a previous page
(e.g., the settings page 2100).
[0202] FIG. 23 shows an exemplary lightshows-for-contacts settings
page 2300 according to an embodiment of the present disclosure that
is opened, for example, when the lightshows-for-contacts icon or
link 2130 on the settings page 2100 is selected. The
lightshows-for-contacts settings page 2300 enables a user to view
and make changes (e.g., generally or specifically) to parameters
governing the display of contact lightshows on the mobile device
cover 100. Referring to FIG. 23, various parameters can be set by
the user. For example, the lightshows-for-contacts settings page
2300 provides a sort order icon or link 2310 (e.g., that provides a
pop up menu) that is selected to set a sorting parameter for
contacts (e.g., a list of contacts) in the mobile application, and
a display order icon or link 2320 that is selected to set a display
parameter for contacts (e.g., first name before last name when a
contact is displayed on the mobile device cover 100). Further, the
lightshows, icons (e.g., light icons), scrolling text, etc. for the
phone, message, email, etc. are enabled or disabled by icons 2330
(e.g., graphical switches or graphical elements that can be
selected or toggled). In addition, content can be displayed on the
mobile device cover 100 including, for example, phone numbers,
email addresses, transcriptions of voice mails, the body of emails,
the body of texts, attachments to the emails or texts, etc.
Different parameters can be generally be set for the different
types of communication, for example, to distinguish them from each
other. For example, once a particular category of application
notification has been enabled, animations can be turned on or off
(e.g., via graphical switch 2340), particular animations can be
chosen, and other animation characteristics (e.g., blink, fade,
etc.) of the animations can be set (e.g., via menus links 2450,
2460) for the general categories such as notifications for phone,
messages, emails, etc. or for specific phone numbers,
messages/emails from specific senders, etc. In some embodiments,
animations and animation parameters can be set for groups (e.g.,
subsets) of contacts depending upon the type of communication.
Selecting the back button 2470 (or other actions such as backwards
swipes) brings back the home page 700 or a previous page (e.g., the
settings page 2100).
[0203] FIG. 24 shows an exemplary synchronization/reset page 2400
that is opened, for example, when the synchronization/reset icon or
link 2140 on the settings page 2100 is selected. By selecting the
reset-to-default icon or link 2410, the synchronization/reset page
2400 enables the user to reset the mobile application settings to
original default values and clear contact lists and other
information in the mobile application. The default values and other
information are sent to and/or stored in the mobile device cover
100 and/or the host mobile device 110. By selecting the
sync-settings-with-case icon or link 2420, the
synchronization/reset page 2400 enables the user to synchronize the
mobile application with the mobile device cover 100, for example,
by sending present values/settings and other present information
(e.g., present settings, contact lists, selected animations, icons,
parameters, etc.) to the mobile device cover 100 or vice versa.
Further, by selecting the repair-LED-grid icon or link 2430, the
synchronization/reset page enables a rewrite of all sectors for the
mobile device cover 100, including sectors that store light
patterns, light shows, fonts, icons, animations, clock faces,
graphical elements, graphical designs, etc. The
synchronization/reset page 2400 also provides an icon or link 2440
for backing up settings and/or other information to a cloud
network. The mobile application also provides an icon 2450 for
restoring settings and/or other information of the mobile
application and/or mobile device cover 100 from settings and/or
other information stored on the cloud network. In some embodiments,
selections made on the synchronization/reset page 2400 include
warnings about the information being lost if the user proceeds with
the synchronization, reset, repair, and/or restore. For example,
resetting or synchronizing the mobile application and/or the mobile
device cover 100 can cause the settings and lookup tables (or other
types of memory or storage) in the mobile device cover 100 to be
overwritten. Selecting the back button 2460 (or other actions such
as backwards swipes) brings back the home page 700 or a previous
page (e.g., the settings page 2100).
[0204] Other embodiments of the present disclosure may provide a
non-transitory computer readable medium and/or storage medium,
and/or a non-transitory machine readable medium and/or storage
medium, having stored thereon, a machine code and/or a computer
program having at least one code section executable by a machine
and/or a computer, thereby causing the machine and/or computer to
perform the steps as described herein.
[0205] Accordingly, aspects of the present disclosure may be
realized in hardware, software, or a combination of hardware and
software. The present disclosure may be realized in a centralized
fashion in at least one computer system or in a distributed fashion
where different elements are spread across several interconnected
computer systems. Any kind of computer system or other apparatus
adapted for carrying out the methods described herein is suited. A
typical combination of hardware and software may be a
general-purpose computer system with a computer program that, when
being loaded and executed, controls the computer system such that
it carries out the methods described herein.
[0206] Aspects of the present disclosure may also be embedded in a
computer program product, which comprises all the features enabling
the implementation of the methods described herein, and which when
loaded in a computer system is able to carry out these methods.
Computer program in the present context means any expression, in
any language, code or notation, of a set of instructions intended
to cause a system having an information processing capability to
perform a particular function either directly or after either or
both of the following: a) conversion to another language, code or
notation; b) reproduction in a different material form.
[0207] While the present disclosure has been described with
reference to certain embodiments, it will be understood by those
skilled in the art that various changes may be made and equivalents
may be substituted without departing from the scope of the present
disclosure. In addition, many modifications may be made to adapt a
particular situation or material to the teachings of the present
disclosure without departing from its scope. Therefore, it is
intended that the present disclosure not be limited to the
particular embodiment disclosed, but that the present disclosure
will include all embodiments falling within the scope of the
appended claims.
* * * * *