Amy Williams
CEP 812
Project Description:
Using Offline Weblinks and Mobile
Technology in Education
Note to readers:
In the interest of readability, offline weblinks will be referred to as “tags,” “codes,”
“weblinks,” “physical hyperlinks,” “Semacodes,” and “ShotCodes,” and used
interchangeably.
Educational Need/Opportunity:
The major educational need falls under the realm of community and continuing
education. All learning does not take place within the four walls of a classroom.
Learning is and should be continuous. One of my goals as a teacher is to instill a love
of life-long learning within my students. In order to achieve this goal, I must show how
learning translates from the classroom and into the real world.
The use of offline weblinks and mobile technology allows education to be
accessible to the masses at any time. Podcasting is the beginning of the time/space
shift; offline weblinks are a continuance of this convenience.
In addition to providing easy access to educational materials, offline weblinks and
mobile technology allow for educators to continue their teaching beyond the school day.
According to Donna Walker Tileston in her book What Every Teacher Should Know
about Media and Technology, “students are no longer limited by the walls of a
classroom or the knowledge of a single textbook (1). She goes on to say that,
“technology is more in tune with the way our students learn today [and] is so much a
part of the real world that to limit is use in the classroom is to limit our students’ ability to
compete in the world (2).”
Teachable moments are a best practice. The real world is full of these moments.
Even if we are not physically with our students, educators can still guide them towards
learning. Tileston shows support of teachable moments when she states, “contextual
learning is stored in the episodic memory system, which is much better at
remembering...the more context you can provide, the stronger the recall. Using media
in the form of auditory or visual stimulus can help you do this (4).”
Introduction to Offline Weblinks:
Offline weblinks are an emerging technology that translates a URL behind a two-
dimensional code into a website. Individuals use the camera function on their mobile
phones to take digital pictures of these codes using the programs they’ve downloaded
from the code providers. The most common forms are Semacode, ShotCode, and QR
Code. These weblinks currently exhibit the most usage in Asia followed by Europe. At
the moment, offline weblinks in the forms of Semacodes, ShotCodes, and QR Codes
are rare in the United States; however, as interest continues to increase, these codes
will become more readily available.
Today, marketing of specific companies and products seems to be the most
popular use of tags. Coca-cola has put them on their cans, musicians have included
them on concert posters, and United Parcel Service uses them to assure that the
correct package arrives at its intended destination. Still, there is plenty of room to
incorporate codes into the field of education.
Implementation Plan:
The implementation of this technology-integrated strategy is three-fold. The first
step requires gathering the appropriate technology. Creating the websites and offline
weblinks is next. Finally, posting the codes and encouraging use is last.
Both hardware and software are necessary to use these codes. The hardware is
common across the globe. A cellular phone with a camera function is needed to
capture photos of the weblinks, while a computer is needed to create them and the
websites they point to. A list of compatible phones is provided in Appendix A. In order
for the user to bring up the websites on his or her phone, he or she will need to have
subscribed to internet access through his or her cellular provider.
Semacode, ShotCode, and QR Code offer free code readers. These can be
downloaded directly from their websites and onto a cellular phone. All three of the
aforementioned providers offer the ability to create tags for free as long as they are
being used by private or non-profit individuals or companies. Qode is also involved in
the creation of offline weblinks, however, there is a fee associated with producing the
tag.
Since I would be using these codes as part of instruction within a public school,
the district would incur few expenses. The codes would be made using the computers,
printer, and paper that is already supplied with my classroom. As I would most likely tag
less than fifty items per school year, the school would need to budget for fifty pieces of
paper, less than one black ink cartridge, internet access, and the use of one computer
and printer. The students and community members who choose to utilize the tags
would absorb the fees associated with their mobile phones and mobile internet access.
To create the websites, there are several choices available in terms of software.
NVU is a free open-source website-creation software program. Other products to
consider are Dreamweaver and Microsoft FrontPage. It should be noted that the
individual generating the codes, does not necessarily need to be the one creating the
website. For example, an educator could create an offline weblink that points to a site
owned and managed by a textbook company.
Posting the code is simple. It can be printed as a sticker, poster, or common
paper document. The person creating the weblink identifies what it is he or she wants
to tag, prints the code, and adheres it to the object. Once the weblink is posted, he or
she should encourage its use. This can be done through word of mouth, incentives for
use, or other advertising strategies.
In my classroom, I would choose to incorporate the use of Semacodes or
ShotCodes as those appear to be the most user-friendly and readily accessible. These
codes would fit nicely into my unit on the nature of matter. Common themes of this unit
include the properties of matter, the Periodic Table of Elements, and physical and
chemical changes. These themes are easily observed and identified outside my fifty-
three minute science class.
In an ideal situation, cell phone service would work within my school. Although
mobile phones are an infringement upon our student handbook, students still carry and
use them during the school day. To make use of the technology they already have at
an arms length, I would post Semacodes throughout my classroom, school, and
community.
A ShotCode scavenger hunt would be a model homework assignment. For
example, to demonstrate the prevalence of the elements of the Periodic Table, I could
tag different examples of the elements and compounds found throughout our school.
The weblinks might direct them to a site explaining how the properties of the elements
make them best suited for specific uses. A code that links to a website on the chemical
reactions needed to break the bonds between the molecules of gasoline and transform
that energy into mechanical energy could be posted at the local gas station. In addition,
a tag placed on the shelves of local grocery stores (with their permission, of course)
could lead students to sites describing the arrangement of molecules within solutions
(soft drinks), colloids (whipped cream), and suspensions (salad dressing.)
Once the unit is over, the codes could be taken down. On the other hand, if they
are left up this would serve as a way to spiral the curriculum. The use of offline
weblinks lends itself to continued implementation as they can be adapted to almost any
educational need.
Connection to the four common places:
Someone teaching plays a supporting role in the use of offline weblinks and
mobile technology. The person teaching would be the individual who seeks out objects
to tag and the websites they were point to. For example, if a teacher was taking his or
her class on a field trip to a museum, he or she would be the one to decide upon which
objects should exhibit a code, find or create the websites that the codes will link to,
create the codes, and post them for student use. The person should possess basic
technological skills if simply directing students to a preexisting website. A more
advanced knowledge of technology would be required if the educator were to participate
in the creation of the websites he or she would like the students to visit.
Someone learning plays the most significant role in this plan. The person who is
learning could be anyone, students or otherwise. It is my belief that if it is only my
actual students who are learning, this plan is minimally successful. I would anticipate
that “someone learning” would consist of my own students, other students at my school,
their family members, and in the broadest and most successful spectrum, the local
community as a whole.
The subject matter and setting are filled with many options. Any subject matter
could be used. For example, physical education could be introduced by posting codes
at the community ball park directing its visitors to learn more about the training required
to perform well during competitions. Biology and chemistry come into play as
explanations of the life processes that take place within the body during exercise.
Mathematics and engineering take part in the creation of the ball park. Often, parks are
named after a person who has been influential in the community. Social studies would
fit seamlessly here. Reading informational text is an essential skill that can be practiced
when visiting these various websites.
The setting in which tags can be used is unbounded. Most educators would
choose to post the codes around their school and community. It should be noted that
the opportunity exists for teachers to provide tags worldwide. The physical setting for
which the teaching is taking place is within the screen of a cellular phone and extends
onto the Internet.
Alternate options:
Instead of using this emerging technology, individuals could continue the
common practices that they carry out at the present moment. The phrase “Google it,”
comes to mind. Today, when someone sees or hears something they are curious
about, they make either a mental or physical note and then research that topic when
they have the time and resources. Many people will return home and search for
information about the topic on www.google.com. The problem with this method is that
once the curious individual has the time available to do the research or is within reach of
an internet connection, they have already forgotten what it was they were curious about.
The teachable moment is lost.
Using weblinks and mobile technology solves this problem by allowing immediate
results. The “digital natives” that are presently walking the halls of our school buildings
are used to receiving information on-demand. Marc Prensky clarifies in his work titled
Digital Natives, Digital Immigrants,
Digital Natives are used to receiving information really fast. They like to parallel process
and multi-task. They prefer their graphics before their text rather than the opposite. They
prefer random access (like hypertext). They function best when networked. They thrive
on instant gratification and frequent rewards (1).
The strategy that I have proposed nurtures these characteristics. Once the student or
community member captures the tag, he or she will immediately learn more about the
topic that originally peaked his or her curiosity.
Potential drawbacks:
Moderate use of tags is recommended. The two-dimensional codes themselves
cannot be described as aesthetically pleasing. It would be a shame to see these codes
plastered on every surface imaginable. Over-posting of these codes might lead to a
feeling of displeasure within the environment, which may cause people to avoid them.
The largest drawback at this time is the lack of compatible hardware in the United
States and the cost of use. Verizon Wireless, one of the largest cellular phone
providers in the country, does not allow the Semacode reader to be used on their
phones. In addition, internet access on a mobile phone can be very costly to its owner.
This would significantly hinder utilization of tags. Nonetheless, I anticipate that due to
the growing popularity of offline weblinks and mobile technology in the East, its use will
spread throughout the West within the next three to five years. Cellular phones that can
make use of this technology will become more prevalent and the cost of mobile internet
access will decrease.
Resources
Tileston, Donna Walker. What Every Teacher Should Know about Media and
Technology
Prensky, Marc. Digital Natives, Digital Immigrants
http://www.shotcode.com/
http://www.nytimes.com/2007/04/01/business/01code.html?ex=1176868800&en=d7e18
b99ef27eb3a&ei=5070
http://www.prnewswire.com/cgi-bin/stories.pl?ACCT=109&STORY=/www/story/03-11-
2005/0003164282&EDATE=
http://www.tectonic.co.za/view.php?action=view&id=965&topic=
http://semacode.org/
http://www.aspisdrift.com/2007/03/clicking-real-world-objects.html
http://www.qode.com/en/qodeReader.jsp
http://www.qrcode.com/
Appendix A
List of cellular phones currently capable of handling Semacode readers as provided by
http://semacode.org/about/hardware/
Hardware Support
Semacode SDK supports a large number of mobile phones, some of which are listed below, with
the recommended version to use.
Your phone is made by: Motorola ... Nokia ... Samsung ... Sony Ericsson ... Alcatel ... BenQ-
Siemens ... Blackberry ... HTC ... LG ... Mitac ... Palm ... Panasonic ... Sagem ... Sanyo ... Sendo
... Sharp
There are 157 supported devices listed.
Motorola
You may need to activate the "Java App Loader", either by obtaining a "Motorola developer
enabled" phone or using a program like PST or p2kman. See for example this MIDway guide.
Motorola A780 (use Reader for Java Phones 1.6)
Motorola A1200 (use Reader for Java Phones 1.6)
Motorola C975 (use Reader for Java Phones 1.6)
Motorola E77v (use Reader for Java Phones 1.6)
Motorola E1000 (use Reader for Java Phones 1.6)
Motorola E680 (use Reader for Java Phones 1.6)
Motorola MPx220 (use Reader for Java Phones 1.6)
Motorola V980 (use Reader for Java Phones 1.6)
Motorola V975 (use Reader for Java Phones 1.6)
Motorola V1050 (use Reader for Java Phones 1.6)
Motorola RAZR V3x (aka V1150) (use Reader for Java Phones 1.6)
Motorola RAZR V3xx (use Reader for Java Phones 1.6)
Motorola ROKR E2 (use Reader for Java Phones 1.6)
Motorola ROKR E6 (use Reader for Java Phones 1.6)
Motorola i275 (test Reader for Java Phones 1.6 and tell us!)
Motorola i850 (test Reader for Java Phones 1.6 and tell us!)
Motorola i870 (test Reader for Java Phones 1.6 and tell us!)
Motorola A920 (no camera access provided by manufacturer)
Motorola A1000 (no camera access provided by manufacturer)
Motorola M1000 (no camera access provided by manufacturer)
Motorola PEBL U6 (no camera access provided by manufacturer)
Motorola SLVR L6 (no camera access provided by manufacturer)
Motorola SLVR L7 (no camera access provided by manufacturer)
Motorola V3 (no camera access provided by manufacturer)
Motorola V3i (no camera access provided by manufacturer)
Motorola V360 (no camera access provided by manufacturer)
Motorola V635 (no camera access provided by manufacturer)
Motorola V8 (no camera access provided by manufacturer)
Nokia
Generally speaking: phones starting with 1 and 2 are "entry level"; 3 is "youth"; 5 is "active"; 6
is "classic"; 7 is "fashion"; 8 is "premium"; and 9 is "communicator". In addition, E is for
business, N is high-end multimedia.
Nokia 5200 (use Reader for Java Phones 1.6)
Nokia 5300 (use Reader for Java Phones 1.6)
Nokia 6085 (use Reader for Java Phones 1.6)
Nokia 6086 (use Reader for Java Phones 1.6)
Nokia 6131 (use Reader for Java Phones 1.6)
Nokia 6133 (use Reader for Java Phones 1.6)
Nokia 6280 (use Reader for Java Phones 1.6)
Nokia 6288 (use Reader for Java Phones 1.6)
Nokia 7373 (use Reader for Java Phones 1.6)
Nokia 7390 (use Reader for Java Phones 1.6)
Nokia 3250 (use Reader for Java Phones 1.6)
Nokia 5500 (use Reader for Java Phones 1.6)
Nokia 6290 (use Reader for Java Phones 1.6)
Nokia 6630 (use Reader for Java Phones 1.6)
Nokia 6638 (use Reader for Java Phones 1.6)
Nokia 6680 (use Reader for Java Phones 1.6)
Nokia 6681 (use Reader for Java Phones 1.6)
Nokia 6682 (use Reader for Java Phones 1.6)
Nokia E50 (use Reader for Java Phones 1.6)
Nokia E62 (use Reader for Java Phones 1.6)
Nokia E70 (use Reader for Java Phones 1.6)
Nokia N70 (use Reader for Java Phones 1.6)
Nokia N71 (use Reader for Java Phones 1.6)
Nokia N72 (use Reader for Java Phones 1.6)
Nokia N73 (use Reader for Java Phones 1.6)
Nokia N75 (use Reader for Java Phones 1.6)
Nokia N80 (use Reader for Java Phones 1.6)
Nokia N90 (use Reader for Java Phones 1.6)
Nokia N91 (use Reader for Java Phones 1.6)
Nokia N92 (use Reader for Java Phones 1.6)
Nokia N93 (use Reader for Java Phones 1.6)
Nokia N95 (use Reader for Java Phones 1.6)
Nokia 7710 (use Reader for Java Phones 1.6)
Nokia 9300 (use Reader for Java Phones 1.6)
Nokia 9500 (use Reader for Java Phones 1.6)
Nokia 3230 (use Reader for S60 1.5)
Nokia 6260 (use Reader for S60 1.5)
Nokia 6600 (use Reader for S60 1.5)
Nokia 6620 (use Reader for S60 1.5)
Nokia 6670 (use Reader for S60 1.5)
Nokia 7610 (use Reader for S60 1.5)
Nokia 3600 (use Reader for S60 1.1)
Nokia 3620 (use Reader for S60 1.1)
Nokia 3650 (use Reader for S60 1.1)
Nokia 3660 (use Reader for S60 1.1)
Nokia 7650 (use Reader for S60 1.1)
Nokia 6265 (test Reader for Java Phones 1.6 and tell us!)
Nokia 6230 (no camera access provided by manufacturer)
Nokia 6111 (no camera access provided by manufacturer)
Nokia 8800 (no camera access provided by manufacturer)
Nokia 8801 (no camera access provided by manufacturer)
Samsung
Samsung SGH-Z140 (use Reader for Java Phones 1.6)
Samsung SGH-Z300 (use Reader for Java Phones 1.6)
Samsung SGH-Z308 (use Reader for Java Phones 1.6)
Samsung SGH-Z500 (use Reader for Java Phones 1.6)
Samsung SGH-Z510 (use Reader for Java Phones 1.6)
Samsung SGH-Z540 (use Reader for Java Phones 1.6)
Samsung SGH-ZM60 (use Reader for Java Phones 1.6)
Samsung SGH-ZV10 (use Reader for Java Phones 1.6)
Samsung SGH-ZX20 (use Reader for Java Phones 1.6)
Samsung A700 (test Reader for Java Phones 1.6 and tell us!)
Samsung A880 (test Reader for Java Phones 1.6 and tell us!)
Samsung A900 (test Reader for Java Phones 1.6 and tell us!)
Samsung A920 (test Reader for Java Phones 1.6 and tell us!)
Samsung A940 (test Reader for Java Phones 1.6 and tell us!)
Samsung SGH-D500 (no camera access provided by manufacturer)
Samsung SGH-E720 (no camera access provided by manufacturer)
Samsung SPH-A700 (no camera access provided by manufacturer)
Samsung SPH-A790 (no camera access provided by manufacturer)
Samsung SPH-I700 (no camera access provided by manufacturer)
Sony Ericsson
"a" models are for the Americas, "c" models are for China, "i" models are for everywhere else.
For purposes of running Semacode they are the same.
Sony Ericsson D750 (use Reader for Java Phones 1.6)
Sony Ericsson F500 (use Reader for Java Phones 1.6)
Sony Ericsson J300 (use Reader for Java Phones 1.6)
Sony Ericsson K300 (use Reader for Java Phones 1.6)
Sony Ericsson K310 (use Reader for Java Phones 1.6)
Sony Ericsson K320 (use Reader for Java Phones 1.6)
Sony Ericsson K506 (use Reader for Java Phones 1.6)
Sony Ericsson K508 (use Reader for Java Phones 1.6)
Sony Ericsson K510 (use Reader for Java Phones 1.6)
Sony Ericsson K610 (use Reader for Java Phones 1.6)
Sony Ericsson K618 (use Reader for Java Phones 1.6)
Sony Ericsson K700 (use Reader for Java Phones 1.6)
Sony Ericsson K750 (use Reader for Java Phones 1.6)
Sony Ericsson K758 (use Reader for Java Phones 1.6)
Sony Ericsson K790 (use Reader for Java Phones 1.6)
Sony Ericsson K800 (use Reader for Java Phones 1.6)
Sony Ericsson S700 (use Reader for Java Phones 1.6)
Sony Ericsson S710 (use Reader for Java Phones 1.6)
Sony Ericsson V1020 (aka Vodafone 802SE) (use Reader for Java Phones 1.6)
Sony Ericsson W300 (use Reader for Java Phones 1.6)
Sony Ericsson W550 (use Reader for Java Phones 1.6)
Sony Ericsson W600 (use Reader for Java Phones 1.6)
Sony Ericsson W700 (use Reader for Java Phones 1.6)
Sony Ericsson W710 (use Reader for Java Phones 1.6)
Sony Ericsson W800 (use Reader for Java Phones 1.6)
Sony Ericsson W810 (use Reader for Java Phones 1.6)
Sony Ericsson W850 (use Reader for Java Phones 1.6)
Sony Ericsson W880 (use Reader for Java Phones 1.6)
Sony Ericsson W900 (use Reader for Java Phones 1.6)
Sony Ericsson V630 (use Reader for Java Phones 1.6)
Sony Ericsson V800 (use Reader for Java Phones 1.6)
Sony Ericsson Z310 (use Reader for Java Phones 1.6)
Sony Ericsson Z500 (use Reader for Java Phones 1.6)
Sony Ericsson Z520 (use Reader for Java Phones 1.6)
Sony Ericsson Z530 (use Reader for Java Phones 1.6)
Sony Ericsson Z550 (use Reader for Java Phones 1.6)
Sony Ericsson Z558 (use Reader for Java Phones 1.6)
Sony Ericsson Z610 (use Reader for Java Phones 1.6)
Sony Ericsson Z710 (use Reader for Java Phones 1.6)
Sony Ericsson Z800 (use Reader for Java Phones 1.6)
Sony Ericsson Z1010 (use Reader for Java Phones 1.6)
Sony Ericsson P900 (use Reader for UIQ 1.1)
Sony Ericsson K500 (test Reader for Java Phones 1.6 and tell us!)
Sony Ericsson K600 (test Reader for Java Phones 1.6 and tell us!)
Sony Ericsson M600 (test Reader for Java Phones 1.6 and tell us!)
Sony Ericsson J100 (device has no camera)
Sony Ericsson J200 (device has no camera)
Sony Ericsson J210 (device has no camera)
Sony Ericsson J220 (device has no camera)
Sony Ericsson J230 (device has no camera)
Sony Ericsson T290 (device has no camera)
Sony Ericsson K600 (only user-facing camera access provided by manufacturer)
Sony Ericsson K608 (only user-facing camera access provided by manufacturer)
Sony Ericsson V600 (only user-facing camera access provided by manufacturer)
Alcatel
Alcatel OT 756 (test Reader for Java Phones 1.6 and tell us!)
Alcatel TH3 (test Reader for Java Phones 1.6 and tell us!)
Alcatel TH4 (test Reader for Java Phones 1.6 and tell us!)
BenQ-Siemens
BenQ-Siemens SX1 (use Reader for S60 1.1)
BenQ-Siemens C65 (use Reader for Java Phones 1.6)
BenQ-Siemens C6V (use Reader for Java Phones 1.6)
BenQ-Siemens C75 (use Reader for Java Phones 1.6)
BenQ-Siemens C81 (use Reader for Java Phones 1.6)
BenQ-Siemens CF61 (use Reader for Java Phones 1.6)
BenQ-Siemens CF75 (use Reader for Java Phones 1.6)
BenQ-Siemens CFX65 (use Reader for Java Phones 1.6)
BenQ-Siemens CL71 (use Reader for Java Phones 1.6)
BenQ-Siemens CL75 (use Reader for Java Phones 1.6)
BenQ-Siemens CV65 (use Reader for Java Phones 1.6)
BenQ-Siemens CX65 (use Reader for Java Phones 1.6)
BenQ-Siemens CX6c (use Reader for Java Phones 1.6)
BenQ-Siemens CX70 (use Reader for Java Phones 1.6)
BenQ-Siemens CX75 (use Reader for Java Phones 1.6)
BenQ-Siemens CXT65 (use Reader for Java Phones 1.6)
BenQ-Siemens E61 (use Reader for Java Phones 1.6)
BenQ-Siemens E71 (use Reader for Java Phones 1.6)
BenQ-Siemens E81 (use Reader for Java Phones 1.6)
BenQ-Siemens EF51 (use Reader for Java Phones 1.6)
BenQ-Siemens EF81 (use Reader for Java Phones 1.6)
BenQ-Siemens EF91 (use Reader for Java Phones 1.6)
BenQ-Siemens EL71 (use Reader for Java Phones 1.6)
BenQ-Siemens M65 (use Reader for Java Phones 1.6)
BenQ-Siemens M75 (use Reader for Java Phones 1.6)
BenQ-Siemens ME75 (use Reader for Java Phones 1.6)
BenQ-Siemens S65 (use Reader for Java Phones 1.6)
BenQ-Siemens S66 (use Reader for Java Phones 1.6)
BenQ-Siemens S68 (use Reader for Java Phones 1.6)
BenQ-Siemens S6V (use Reader for Java Phones 1.6)
BenQ-Siemens S75 (use Reader for Java Phones 1.6)
BenQ-Siemens S81 (use Reader for Java Phones 1.6)
BenQ-Siemens S88 (use Reader for Java Phones 1.6)
BenQ-Siemens S6C (use Reader for Java Phones 1.6)
BenQ-Siemens SF65 (use Reader for Java Phones 1.6)
BenQ-Siemens SFG75 (use Reader for Java Phones 1.6)
BenQ-Siemens SK65 (use Reader for Java Phones 1.6)
BenQ-Siemens SL65 (use Reader for Java Phones 1.6)
BenQ-Siemens SL75 (use Reader for Java Phones 1.6)
BenQ-Siemens SL91 (use Reader for Java Phones 1.6)
BenQ-Siemens SP65 (use Reader for Java Phones 1.6)
BenQ-Siemens SXG75 (use Reader for Java Phones 1.6)
Blackberry
Blackberry 8100 (Pearl) (test Reader for Java Phones 1.6 and tell us!)
HTC
HTC makes phones sold under a variety of labels. They are identical.
HTC Blue Angel (aka Qtek 9090, MDA III, O2 XDA III, Orange SPV M2000) (no
camera access provided by manufacturer)
HTC Magician (aka Qtek S100, T-Mobile MDA Compact, i-mate JAM, O2 XDA II mini,
Orange SPV M500, Vodafone VPA compact) (no camera access provided by
manufacturer)
HTC Prophet (aka Qtek S200, i-mate Jamin, T-Mobile MDA Vario II, Orange SPV
M600, O2 XDA Neo, Dopod 818 Pro, Vodafone VPA compact S) (no camera access
provided by manufacturer)
HTC Tornado (no camera access provided by manufacturer)
HTC Typhoon (aka Qtek 8010, i-mate SP3, Orange SPV C500/C500S, Audiovox STM
5600, Dopod 565) (no camera access provided by manufacturer)
HTC Universal (aka Qtek 9000, i-mate Jasjar, T-mobile MDA Pro, Orange SPV M5000,
O2 XDA Exec, Dopod 900, Vodafone VPA IV) (no camera access provided by
manufacturer)
HTC Wizard (aka Qtek 9100, i-mate K-Jam, T-mobile MDA Vario, Orange SPV M6000,
O2 XDA Mini Pro/S, Dopod 838, Vodafone VPA compact II) (no camera access
provided by manufacturer)
LG
LG CU500 (use Reader for Java Phones 1.6)
LG U880 (use Reader for Java Phones 1.6)
LG 535 (unknown manufacturer incompatibility)
LG 8130 (unknown manufacturer incompatibility)
LG VX6000 (unknown manufacturer incompatibility)
Mitac
Mitac 8390 (test Reader for Java Phones 1.6 and tell us!)
Palm
Palm Treo 600 (no camera access provided by manufacturer)
Palm Treo 650 (no camera access provided by manufacturer)
Panasonic
Panasonic X701 (test Reader for Java Phones 1.6 and tell us!)
Panasonic VS3 (no camera access provided by manufacturer)
Sagem
Sagem myX6-2 (test Reader for Java Phones 1.6 and tell us!)
Sagem myV-76 (test Reader for Java Phones 1.6 and tell us!)
Sagem myS-7 (no camera access provided by manufacturer)
Sanyo
Sanyo Katana (use Reader for Java Phones 1.6)
Sanyo 5600 (test Reader for Java Phones 1.6 and tell us!)
Sanyo 7400 (test Reader for Java Phones 1.6 and tell us!)
Sanyo 7500 (test Reader for Java Phones 1.6 and tell us!)
Sanyo 8300 (test Reader for Java Phones 1.6 and tell us!)
Sanyo 9000 (test Reader for Java Phones 1.6 and tell us!)
Sanyo S750 (no camera access provided by manufacturer)
Sendo
Sendo X (use Reader for S60 1.1)
Sharp
Sharp SX813 (test Reader for Java Phones 1.6 and tell us!)
Sharp V902sh (test Reader for Java Phones 1.6 and tell us!)