Ambient Networks Mobile Phone Integration

Total Page:16

File Type:pdf, Size:1020Kb

Ambient Networks Mobile Phone Integration Ambient Networks Mobile phone integration Carlos Rocha, Rui Botelho PSTFC FEUP – DEEC 2004 Ambient network - Mobile phone integration Supervisor professor: Prof. Manuel Alberto Pereira Ricardo Project supervisor: Prof. Mário Jorge Moreira Leitão Department: Department of Electrical and Computer Engineering Institutions: Faculty of Engineering at University of Oporto Institute of Engineering and Computer Systems of Oporto i About the authors Carlos Rocha Carlos is a student at FEUP since 1999. Carlos first experience on Symbian came with the acknowledgment of the project in the end of 2003. The work on this subject continues at the time of this writing. Student number: 990503145 E-mail: [email protected] Telephone: 961818010 Rui Botelho Rui is also student at FEUP since 1999. As with Carlos, Rui Botelho heard about Symbian in late 2003 as it was a project proposal of Prof. Manuel Ricardo. Since then, this area has been one of his main interests. Student number: 990503146 E-mail: [email protected] Telephone: 963379295 ii We would like to thank Professor Manuel Pereira Ricardo for believing in this work and helping us to overcome the problems that we met along the semester. We also would like to thank our colleagues, Filipe Abrantes, Ricardo Duarte and António Madureira for all the work done in the integration of our projects. A special thank you note goes to Filipe Sousa from INESC for all the help and support given. iii Contents 1. Introduction 1.1 Overview....................................................................................................1 1.2 Objectives ..................................................................................................2 1.3 Results .......................................................................................................3 1.4 Report structure .......................................................................................4 2. Symbian OS 2.1 Introduction to Symbian OS....................................................................6 2.1.1 Symbian History ..........................................................................6 2.1.2 Symbian OS Structure .................................................................7 2.1.3 Networking infrastructure............................................................10 2.2 Java programming for Symbian .............................................................12 2.2.1 Introduction..................................................................................12 2.2.2 Java and Symbian ........................................................................12 2.2.3 Programming essentials ...............................................................14 2.3 Symbian C++ programming....................................................................16 2.3.1 Getting started..............................................................................16 2.3.2 Development basics .....................................................................17 2.3.3 Applications structure..................................................................18 2.3.4 Implementation Details................................................................21 2.4 Summary ...................................................................................................23 3. PC connectivity 3.1 Introduction ..............................................................................................24 3.2 Linux notes ................................................................................................25 3.3 Bluetooth connectivity under Linux .......................................................26 3.4 Summary ...................................................................................................27 4. Project description 4.1 Overview....................................................................................................28 4.2 Fundamentals............................................................................................30 4.3 Application structure ...............................................................................33 4.4 Networking................................................................................................45 4.5 Results........................................................................................................50 4.6 Summary ...................................................................................................51 iv 5. Project evaluation 5.1 Testing procedure.....................................................................................52 5.2 Test validation...........................................................................................54 6. Conclusion 6.1 Review of objectives and results..............................................................55 6.2 Main conclusions.......................................................................................55 6.3 Future work...............................................................................................56 Appendix A – Symbian’s History............................................................ 57 Appendix B – How to create a Java application ...................................... 61 Appendix C – First approach to Symbian C++ programming................. 64 Appendix D – How to create a C++ application...................................... 65 Appendix E – Building an application..................................................... 66 Appendix F – How to create a simple installation file ............................ 69 Appendix G – The Communications Database classes ........................... 70 Appendix H – Using active objects ......................................................... 76 Appendix I – Sockets API ....................................................................... 79 Appendix J – Using Bluez tools .............................................................. 96 References .............................................................................................101 v Acronym list ACL – Asynchronous Connectionless packet AVKON Series 60 extensions and modifications to Symbian’s Uikon and other parts of the Symbian OS Application Framework. CBA - Command Button Area, i.e. toolbar CDC – Connected Device Configuration Defines a Java runtime environment for “high end” consumer devices with constrained hardware resources such as set top boxes, PDAs and Communicators. Falls under the J2ME umbrella. CLDC – Connected Limited Device Configuration Defines a Java runtime environment for devices with highly constrained hardware resources. CommDb Communications database offered by Symbian. It provides access to extensible database which holds information about internet access, GPRS connections, WAP settings, proxy servers DBMS – Database Management System Defines a general relational database access API, and allows different database implementations to be provided. DUN – Dial-Up Networking profile FTP – File Transfer Profile GAP – Generic Access Profile GOEP – Generic Object Exchange (OBEX) Profile GPRS – General Packet Radio Service vi GSM – Global System for Mobile Communications. GSM is the world’s most widely-used digital mobile phone system. HCI – Host Controller Interface HTTP – HyperText Transfer Protocol IDE – Integrated Development Environment JABWT - Java API for Bluetooth Wireless Technology An optional API that allows J2ME applications to access Bluetooth functionality. JAD – Java Application Descriptor (file) JAR – Java Archive (file). Java Industry standard object-oriented language and virtual machine, invented by Sun Microsystems and formally released in 1996. Java is an ideal language for network applications and applets. Sun's Java specifications include many Java APIs and platforms, including the JavaPhone API and PersonalJava platform, which are included in Symbian OS. J2ME – Java 2 Platform, Micro Edition. The edition of the Java platform that is targeted at small, standalone or connectable consumer, and embedded devices. The J2ME technology consists of a virtual machine and a set of APIs suitable for tailored runtime environments for these devices. The J2ME technology has two primary kinds of components – configurations and profiles. JavaPhone A Java API specification controlling contacts, power management, call control, and phonebook management, intended specifically for the programmability requirements of mobile phones. JCP – Java Community Process An open organisation of Java developers and licensees whose charter is to develop and revise Java technology specifications, reference implementations, and technology compatibility kits. vii JSR – Java Specification Request The process by which new Java specifications are defined. Part of the Java Community Process. JTAPI – Java Telephony API The Java Telephony API is an extensible API that offers an interface to all call control services (from those needed in a consumer device up to those of call centers). JTAPI is part of the JavaPhone API. JTWI – Java Technology Wireless Initiative An initiative to provide a roadmap of mobile phone related JSRs, indicating their availability in different markets around the world a specification describing the essential client components of an end-to-end wireless environment also to provide a Reference Implementation of the technology and a Technology Compatibility Kit. JVM – Java Virtual Machine. Kernel Core of an operating system, a kernel manages the machine’s hardware resources (including the processor and the memory), and
Recommended publications
  • WORKABOUT PRO™ 3 Works As Hard As You Do
    WORKABOUT PRO™ 3 Works as hard as you do The needs of businesses are changing almost daily, creating a demand for a fleet of handheld computers that can keep up. Introducing the latest innovation from Psion Teklogix – The WORKABOUT PRO 3. Intelligent, rugged and most importantly flexible, the Psion WORKABOUT PRO 3 is a new breed of handheld computer that delivers the choice of numerous hardware add-ons, software applications and upgrades, making it work as hard as you do. WORKABOUT PRO™ 3 The Flexible, Expandable, Rugged Handheld Computer Makes the Most of Mobility Created for the mobile worker, the WORKABOUT PRO 3 is ideal for employees across a range of industries, including mobile field services, logistics, warehousing, transportation, manufacturing and more. Its impressive flexibility enables you to supply one device to meet many requirements; the WORKABOUT PRO 3 is built to be a key member of your IT infrastructure. The leading product in its category, the WORKABOUT PRO 3 allows you to get exactly the device that you need. In addition, you have the opportunity to get the add-ons you need today and the ability to add more features at any point, as business needs change. The number of add-ons and software applications you can attach is endless, so whether it’s a camera for a traffic officer or a GPS module used to track and trace delivery locations – there is a solution for every application. Features & Benefits As Adaptable As You Are It Builds on Mobility The hardware expansion slots of the The WORKABOUT PRO 3’s Natural CASE STUDY WORKABOUT PRO 3 make adding Task Support™ means mobile workers new modules fast and easy – saving get the job done faster and more significant time and money.
    [Show full text]
  • Palm Security WP.Qxd
    Palm® Mobility Series: Security Smartphone and handheld security for mobile business. Mobile computing: Opportunities and risk By providing professionals with convenient mobile access to email, business applications, customer information and critical corporate data, businesses can become more productive, streamline business processes and enable better decision making. With the new ease of access to information comes a responsibility to protect the organization's data as well as the investment in mobile devices. In many ways, security risks for mobile computing are similar to those for other computing platforms. There are the usual concerns of protecting data, authenticating users, and shielding against viruses and other malicious Contents code. But because of their mobility and compact size, smartphones and handhelds present some additional challenges: Mobile computing: Opportunities and risk...................................................... 1 Know thy enemy: Security risks...................................................................... 2 • Smartphones and handhelds are more easily lost or stolen than Theft and loss ............................................................................................ 2 laptop or desktop computers. Password cracking .................................................................................... 2 Data interception ...................................................................................... 2 • Users often treat smartphones and handhelds as personal devices Malicious code
    [Show full text]
  • Mobile Commerce Business Models and Technologies Towards Success
    Rochester Institute of Technology RIT Scholar Works Theses 2003 Mobile commerce business models and technologies towards success Pinar Acar Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Acar, Pinar, "Mobile commerce business models and technologies towards success" (2003). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. MS in Information Technology Capstone Thesis Pinar Nilgul1 Acar 5/15/2003 Mobile Commerce Business Models and Technologies Towards Success By Pinar Nilgun Acar Thesis submitted in partial fulfillment of the requirements for the degree ofMaster of Science in Information Technology Rochester Institute of Technology B. Thomas Golisano College of Computing and Information Sciences 5/15/2003 1 Rochester Institute of Technology B. Thomas Golisano College of Computing and Information Sciences Master of Science in Information Technology Thesis Approval Form Student Name: Pinar Nilgun Acar Project Title: Mobile Commerce Business Models and Technologies Towards Success Thesis Committee Name Signature Date Michael Floeser Chair Ed Holden Committee Member Jack Cook Committee Member Thesis Reproduction Permission Form Rochester Institute of Technology B. Thomas Golisano College of Computing and Information Sciences I Master of Science in Information Technology Title I, Pinar Acar. hereby grant permission to the Wallace Library of the Rochester Institute of Technology to reproduce my thesis in whole or in part. Any reproduction must not be for commercial use Dr profit.
    [Show full text]
  • WORKABOUT PRO the Flexible, Expandable Workhorse Psionteklogix.Com
    WORKABOUT PRO The Flexible, Expandable Workhorse psionteklogix.com Something’s very wrong if you have to throw out your fleet of handheld computers just because your needs change. At Psion Teklogix, we take a different approach. The WORKABOUT PRO has hardware expansion slots that make adding new modules fast and easy – there’s a whole range of add-ons already available – everything from fingerprint scanners to the largest selection of RFID readers on any handheld device. Period. It just might be the most flexible, intelligent, rugged handheld computer ever made... www.psionteklogix.com WORKABOUT PRO The Flexible, Expandable Rugged Handheld Computer THE MobILE workHorSE Let’s face it: you have no idea what tomorrow will bring. The rugged handheld computer you choose today may not be right when your needs change. Unless you choose the legendary WORKABOUT PRO. It’s built on the Modulus™ platform, so it’s easily Meter Reading extended using a wide range of hardware modules – anything from passport readers and fingerprint scanners to WAN radios, laser scanners, imagers and Bluetooth® printers. Plus a growing range of connectivity peripherals (RS232, USB...) that mean you’ll never regret your decision. Our many partners are always developing new modules. Choose one to meet your unique needs, change one when your needs evolve or use the Hardware Development Kit to make your own. Shipping and Warehousing FEaturES & BENEFITS The mobile workhorse The mobile worker is our focus CASE STUDY The WORKABOUT PRO is relied on every WORKABOUT PRO’s Natural Task day in mobile-intensive applications Support™ means mobile workers get the such as asset tracking, meter reading, job done faster and more comfortably, and mobile ticketing across a variety of even over the longest shifts.
    [Show full text]
  • Nokia 6630 User's Guide
    Nokia 6630 User’s Guide 1 DECLARATION OF CONFORMITY We, NOKIA CORPORATION declare under our sole responsibility that the product RM-1 is in conformity with the provisions of the following Council Directive: 1999/5/EC. A copy of the Declaration of Conformity can be found at http://www.nokia.com/phones/declaration_of_conformity/ Copyright © 2005 Nokia. All rights reserved. Reproduction, transfer, distribution or storage of part or all of the contents in this document in any form without the prior written permission of Nokia is prohibited. Nokia, Nokia Connecting People, and Pop-Port are trademarks or registered trademarks of Nokia Corporation. Other product and company names mentioned herein may be trademarks or tradenames of their respective owners. Nokia tune is a sound mark of Nokia Corporation. This product includes software licensed from Symbian Software Ltd © 1998-200(4). Symbian and Symbian OS are trademarks of Symbian Ltd. Java™ and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. Bluetooth is a registered trademark of Bluetooth SIG, Inc. Stac ®, LZS ®, © 1996, Stac, Inc., © 1994-1996 Microsoft Corporation. Includes one or more U.S. Patents: No. 4701745, 5016009, 5126739, 5146221, and 5414425. Other patents pending. Hi/fn ®, LZS ®,© 1988-98, Hi/fn. Includes one or more U.S. Patents: No. 4701745, 5016009, 5126739, 5146221, and 5414425. Other patents pending. Part of the software in this product is © Copyright ANT Ltd. 1998. All rights reserved. US Patent No 5818437 and other pending patents. T9 text input software Copyright © 1997-2004. Tegic Communications, Inc. All rights reserved. Copyright © 2005 Nokia.
    [Show full text]
  • Nokia Phones: from a Total Success to a Total Fiasco
    Portland State University PDXScholar Engineering and Technology Management Faculty Publications and Presentations Engineering and Technology Management 10-8-2018 Nokia Phones: From a Total Success to a Total Fiasco Ahmed Alibage Portland State University Charles Weber Portland State University, [email protected] Follow this and additional works at: https://pdxscholar.library.pdx.edu/etm_fac Part of the Engineering Commons Let us know how access to this document benefits ou.y Citation Details A. Alibage and C. Weber, "Nokia Phones: From a Total Success to a Total Fiasco: A Study on Why Nokia Eventually Failed to Connect People, and an Analysis of What the New Home of Nokia Phones Must Do to Succeed," 2018 Portland International Conference on Management of Engineering and Technology (PICMET), Honolulu, HI, 2018, pp. 1-15. This Article is brought to you for free and open access. It has been accepted for inclusion in Engineering and Technology Management Faculty Publications and Presentations by an authorized administrator of PDXScholar. Please contact us if we can make this document more accessible: [email protected]. 2018 Proceedings of PICMET '18: Technology Management for Interconnected World Nokia Phones: From a Total Success to a Total Fiasco A Study on Why Nokia Eventually Failed to Connect People, and an Analysis of What the New Home of Nokia Phones Must Do to Succeed Ahmed Alibage, Charles Weber Dept. of Engineering and Technology Management, Portland State University, Portland, Oregon, USA Abstract—This research intensively reviews and analyzes the management made various strategic changes to take the strategic management of technology at Nokia Corporation. Using company back into its leading position, or at least into a traditional narrative literature review and secondary sources, we position that compensates or reduces the losses incurred since reviewed and analyzed the historical transformation of Nokia’s then.
    [Show full text]
  • 1 Smartphones and Symbian OS
    1 Smartphones and Symbian OS Symbian OS is a full-featured, open, mobile operating system that powers many of today’s smartphones. As these smartphones become more pow- erful and popular, the demand for smartphone software has grown. Symbian smartphones are shipped with a variety of useful pre-loaded and targeted applications, which are selected by each phone’s manu- facturer. Today, the average Symbian smartphone ships with over 30 pieces of third-party software pre-installed. However, the exciting aspect of Symbian smartphones is that they are ‘open’, meaning that users can further customize their phone experience by downloading, installing, and uninstalling applications written by third-party developers (or by the users themselves). Users can download applications from a PC to the smartphone through a link such as USB, or Bluetooth technology, or over-the-air via the Internet. With the largest installed base of smartphones worldwide, Symbian OS offers a great opportunity for software developers to establish them- selves in the mobile market by creating novel and exciting software for the growing mass of smartphone users around the world. There is a growing list of Symbian applications available as freeware or as paid downloads on numerous Internet sites (http://www.handango.com and http://www.epocware.com are good examples). They range from pro- ductivity, entertainment, navigation, multimedia, and communications software to programs that can count fast food calories, improve your golfCOPYRIGHTED swing, keep diaries, and calculate MATERIAL foreign currency exchange. And business opportunities aside, sometimes it’s just plain fun writing your own code to run on your own smartphone.
    [Show full text]
  • Using the Psion Series 3 Serial Link with the PC Emulator
    10th March 1993 Support Group Application Note Number: 227 Issue: 1.0 (10-3-93) Author: Russell Scott Using the Psion Series 3 Serial Link with the PC Emulator This application note describes how to connect your Pocket Book/Psion Series 3 to your RISC OS computer via the PC Emulator and the Psion Series 3 PC Serial Link interface and software. This is especially useful for users who already possess a Psion 3 Link but not the Acorn A-Link product. Applicable Related Hardware : RISC OS based machine Application Acorn Pocket Book Notes: None Psion Series 3 Copyright © Acorn Computers Limited 1993 Every effort has been made to ensure that the information in this leaflet is true and correct at the time of printing. However, the products described in this leaflet are subject to continuous Support Group development and improvements and Acorn Computers Limited reserves the right to change its specifications at any time. Acorn Computers Limited cannot accept liability for any loss Acorn Computers Limited or damage arising from the use of any information or particulars in this leaflet. ACORN, Acorn House ECONET and ARCHIMEDES are trademarks of Acorn Computers Limited. Vision Park Histon Cambridge CB4 4AE Support Group Application Note No. 227, Issue 1.0 10th March 1993 Introduction This application note describes how you can transfer files between an Acorn Pocket Book/Psion Series 3 and your RISC OS computer if you already possess the Psion Series 3 Serial Link interface and software. The PC software that comes with the 3 Link does run under the emulator but is unable to communicate with the Pocket Book/Series 3 using the Serial Link lead, unless the lead is modified.
    [Show full text]
  • The Symbian OS Architecture Sourcebook
    The Symbian OS Architecture Sourcebook The Symbian OS Architecture Sourcebook Design and Evolution of a Mobile Phone OS By Ben Morris Reviewed by Chris Davies, Warren Day, Martin de Jode, Roy Hayun, Simon Higginson, Mark Jacobs, Andrew Langstaff, David Mery, Matthew O’Donnell, Kal Patel, Dominic Pinkman, Alan Robinson, Matthew Reynolds, Mark Shackman, Jo Stichbury, Jan van Bergen Symbian Press Head of Symbian Press Freddie Gjertsen Managing Editor Satu McNabb Copyright 2007 Symbian Software, Ltd John Wiley & Sons, Ltd The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England Telephone (+44) 1243 779777 Email (for orders and customer service enquiries): [email protected] Visit our Home Page on www.wileyeurope.com or www.wiley.com All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except under the terms of the Copyright, Designs and Patents Act 1988 or under the terms of a licence issued by the Copyright Licensing Agency Ltd, 90 Tottenham Court Road, London W1T 4LP, UK, without the permission in writing of the Publisher. Requests to the Publisher should be addressed to the Permissions Department, John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England, or emailed to [email protected], or faxed to (+44) 1243 770620. Designations used by companies to distinguish their products are often claimed as trademarks. All brand names and product names used in this book are trade names, service marks, trademarks or registered trademarks of their respective owners.
    [Show full text]
  • Symbian Phone Security
    Symbian phone Security Job de Haas ITSX Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Overview • Symbian OS. • Security Risks and Features. • Taking it apart. • Conclusions. Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian History • Psion owner of EPOC OS, originally from 1989, released EPOC32 in 1996 • EPOC32 was designed with OO in C++ • 1998: Symbian Ltd. formed by Ericsson, Nokia, Motorola and Psion. • EPOC renamed to Symbian OS • Currently ~30 phones with Symbian and 15 licensees. Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian Organization • Symbian licenses the main OS • Two GUI’s on top of Symbian: – Series 60, led by Nokia – UIQ, subsidiary of Symbian • Ownership: – Nokia 47.5% Panasonic 10.5% – Ericsson 15.6% Siemens 8.4% – SonyEricsson 13.1% Samsung 4.5% Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian Versions • EPOC32 • EPOC R5 • Symbian v6.0 • Symbian v7.0 • Symbian v8.0 • Symbian v9.0 announced for Q3 ‘05 Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Series60 versions • 1st edition • 2nd edition • 3rd edition, announced feb. 2005 Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 UIQ versions • UIQ 1.0 • UIQ 2.1 • UIQ 3.0 released feb 2005 Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian OS Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian OS • Multitasking, preemptive kernel. • MMU protection of kernel and process spaces. • Strong Client – Server architecture • Plug-in patterns • Filesystem in ROM, Flash, RAM and on SD-card Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian development • Symbian v6 and v7 are compiled with a modified GCC.
    [Show full text]
  • Using Codewarrior for Macintosh
    CS106B Handout #5M Winter 04-05 January 7, 2005 Using CodeWarrior for Macintosh In CS106, you have the option of writing your programs on the Mac or PC. For the Macintosh environment, you will write your programs using the C++ compiler by Metrowerks called CodeWarrior Professional. The current version of CodeWarrior, Pro 8, has been site-licensed to Stanford and can be downloaded from the Software page on the course web site. CodeWarrior provides a very nice editing environment and debugger, and it is the state-of-the-art C++ compiler for the Mac. One of the consequences of using a state-of-the-art compiler is that the system requirements for CodeWarrior Pro 8 are somewhat high – it requires Mac OS 9.2.2 or later, 700MB of hard drive space, and at least 64 MB of RAM. You also have to have CarbonLib 1.5, since Pro 8 is written for Mac OS X as well. If you have OS X, then you need 128MB of RAM to run CodeWarrior Pro 8, and you don’t need CarbonLib as this is already part of OS X. You can download CarbonLib from Apple—more on this later. Using CodeWarrior at a cluster CodeWarrior is available for use in the Lair (the Tresidder Macintosh cluster), on the Macs in Meyer library, and in the residential computer clusters. Often it will already be in the Applications folder on the machine’s hard disk. If there is a folder there named something like Metrowerks CodeWarrior 8, then the application can be found within that folder.
    [Show full text]
  • Linux on Cellphones
    Linux on cellphones Pavel Machek Phones are everywhere ● everyone has their cellphone ● and carries it whereever they go ● cellphones are not just phones any more ● they browse web ● can read mail ● play mp3s and videos ● play radio ● they show maps, and you can use them for navigation Phones are sensitive ● They contain your contacts ● ...your passwords ● ...your emails ● ...can eavesdrop on you ● ...can steal your money and transfer them to attacker ● Backups are important because they break down ● non-smart phones do not have adequate ways to backup more than contacts Phones are working against their owner ● Cellphone operators have „interesting“ requirements before they'll sell a cellphone ● Branded phones are actively evil here ● right button takes you right into provider's portal, and you pay for it ● without confirmation ● without chance to change that ● branding is non-removable, so you are stuck with looking at red wallpaper ● you can't use it with other operator ● MMS / push to talk are designed to be expensive ● Voice-over-IP is a big no-no for a phone Phones are working against their owner ● You can only transfer pictures out of a phone using MMS ● You can only download applications using GPRS ● You can't transfer pictures/apps/songs between phones ● Have to confirm actions even of your own apps Phones are limited ● (but maybe that's a good thing?) ● Java applications work everywhere ● but they can't do interresting stuff ● usually can't access microphone, camera ● can't go background ● can't interact with one another ● Symbian
    [Show full text]