DOCSLIB.ORG

The Neo900 Open Smartphone a Platform with New Security Features Neo900.Org

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

The Neo900 Open Smartphone A platform with new security features neo900.org Werner Almesberger [email protected], J¨orgReisenweber [email protected] The Neo900 project Tired of closed mobile platforms ? Openmoko veterans, still hungry Open hardware Designed for Free Software New security features Inspired by Nokia N900 Linux-friendly platform Active community Has a real keyboard Making a smartphone in three easy steps Electronics (lots of them) Mechanical design (case) User-visible software Smartphone user interface The Openmoko experience: 2007.1: Gaudy, obese, unmaintainable, confusing 2007.2: Lighter, cryptic Let's try something new: Qtopia Let's try something else, too: Android 2008: Enlightenment Post-Openmoko: QtMoko, SHR Lession learned. Let's not do this again. Software evolution (simplified) Nokia Intel Linux Foundation Samsung Maemo Moblin LiMo Bada Nokia+Intel MeeGo Hildon Community Maemo 5 Mer (Fremantle) Intel+Samsung+LF Tizen Community Jolla Nemo Mobile Sailfish OS Software choices Neo900 is a Linux platform. Maemo (Fremantle) Hardware compatibility goal Debian / Devuan Board Support Package Replicant (Android) MeeGo ::: whatever you choose to install or port Hardware evolution Openmoko Golden Delicious Neo900 Nokia Linux Symbian 2006 2007 GTA01 (Neo1973) N800−810 (Tablet) N95 Case, LCD 2008 GTA02 (Freerunner) N96 Case, Maemo 2009 GTA03 N900 (Phone) N97 (Keyboard) 2010 2011 GTA04A3 N9 (no keyboard) 2012 GTA04A4 Know−how 2013 Neo900v0 Influence R&D 2014 Neo900v1 Product Prototype design 2015 GTA04A5 Neo900v2 Reusing the case N900 case is nice Making own would be too expensive N900 case is still available Problem: We need more space Original component heights Modem (PLS8) Top 2.3 mm max. 2.0 mm PCB 0.8 mm max. 1.5−2.0 mm Bottom Solution: Add another board Top max. 2.0 mm UPPER 0.8 mm Modem Board−to−board 2.5 mm +3.3 mm (PLS8) connector LOWER 0.8 mm max. 1.5−2.0 mm Bottom Original mechanical stacking Case bottom Case bottom Display PCB Display opening Keyboard frame Keyboard Dome sheet Keyboard frame Key mat The Spacer Frame Case bottom Spacer frame Display PCBs Display opening Keyboard Spacer frame Key mat Drawing not to scale Your smartphone, in theory Modem Application (GSM, ...) Environment (Linux) Closed Open In practice Modem Application (GSM, ...) Environment (Linux) Closed Open Keep them separated Application Modem Environment (GSM, ...) (Linux) Data Power Closed Open However, ::: Radio Application Modem Environment (GSM, ...) (Linux) Audio Data Power Closed Open Oops ! Radio Application Modem Environment (GSM, ...) (Linux) Audio Data ? Power Closed Open Oops ! Radio ROGUEApplication MODEM Modem NOT DETECTEDEnvironment (GSM, ...) (Linux) Audio Data ? Power Closed Open Sensory deprivation Radio Application Modem Environment (GSM, ...) (Linux) Audio Data STOP Power Closed Open ::: and monitor Radio Application Modem Environment (GSM, ...) (Linux) Audio Data Power Closed Open Just in case ::: Radio Application Modem Environment (GSM, ...) (Linux) Audio Data Power Closed Open Prototype V0/V1 Modem, some switches No CPU Goal: Test mechanical compatibility and modem Produced early in the project Prototype V2 Most components present External CPU (BeagleBoard) Refined mechanical design Goal: Test subsystems Working on this now Prototype V3 Complete system, with CPU Goal: Certification Goal: Finalize design before production Expected around end of 2015 CPU, Neo900 Block Diagram (Work in progress) power (3x) Comp. Modem TX (a) = EMERG_OFF, RING, Modem monitor monitor Connection through PCB contact(s) I2C#2 pcm[4] Modem+Navigation cell PWR_IND, LC_IND, CPU STATUS, 3G_WOE, Junction with branch 2 3 x INA231, TPS22963 PHS8/PLS8−E,US/PXS8 1 CPU MODEM_IGT eMMC (64 GB) GPS/GLONASS Crossing of separate connections VGNSS (b) = rst, clk, io, cd, power, MMC2_{CLK,CMD,DAT[8]} 2 LNA swp (a) 5 3 D+, D−, VBUS N signals on connection/branch ??? uart[4] gps BGM 1034N7 SIM switch N 5 GPS kill blue: I2C bus 10 44 USB PHY PE4259 ALERT, EN (b) 6 ULPI[12], RESETB USB3322 SIM #1 RAM_{CTRL[17],DA[32],AD[19]} 68 MMC#2 13 rst, io, clk, cd, power RAM (1 GB), SF7W006S4E BSP#4 3 int, en, strobe antenna (b) UART#1 USB#1 8 NAND (512 MB) NAND_{CTRL[9],ADDA[16]} 25 Flash LED driver CPU 3 cd 6 2 Flash LEDs SIM #2 I2C#2 data,ctrl CPU 1 KCE00E00CA I2C#2 ADP1653 2 x L130−5780002011001 NFC swp,control 101−00271−82 rst,int I2C#2 TRF7970A, KL16 uSD card MMC1_{CLK, 7 2 I2C#3 Audio, BTFM CPU 2 I2C#3 MMC#1 I2C#3 ST1W008S4B CMD,DAT[4]}, CD B2B UPPER−LOWER 2 cam_d3, CAM_XCLKA 2 x DF40HC(2.5)−60DS−0.4V, 2 x DF40C−60DP−0.4V 1 CAM_B_EN Batt. lid mag. BAT_LID 1 CPU CMOS camera (rear) B2B LOWER−BOB MLX90248ESE 4 CSI_A_B[4] 4 DF9−21P−1V, DF9−21S−1V 5 GHz Cam switch Main cam conn N97 cam, DF37NB−20DS−0.4V conn. 2.4 GHz ??? sdio[6] MMC#3 CAM_CLKB WLAN_{EN,IRQ} 1 WLAN/BT 2 x TS3DS26227 Baro, CSI_B[4] Accel BMX055 BME280 9−Axis CMOS camera (front) LIS302DL Tap uart[4] humidity RF UART#2 RGB.R 4 VS6555AC pcm[4] 1 INT1 (c) INT2/4/5 Diplexer 0R BSP#3 I2C#3 1 ??? BT_EN 1 INT2 (to cam, proxy, ambient) TBD WL1837MODGI (c) INT1/3, DRDY 1 PROXY Reflective switch (proximity) M50−3151042 DPX2012LL85R2455A Hackerbus 1 ALS_INT FM_nINT Ambient light sensor FM TX/RX TSL2563 FM TX I2C#2 LCD_LEDS Backlight LED driver SETCURR1, LCDLEDS_{1,2}, CABC 4 Si4721 CPU Compan Speakers 2 1 TPS61041 17 LCD_{RST,CDP[8],SPI[4]} 17 LCD SPI#3 ACX565AKM−7 FM_ANT FM_AUDIO[4] B2B 2 audio 2 1 4 Main flex connector Resistive Speaker 2 TSC_RST, PEN_INT I2C#2 Touch scrn ctrl X/Y 4 CRTOUCHB10 touch screen amplifier I2S 4 3 audio 2 Stereo NRST[2], RGB_INT, RGB_CTRL_EN audio BSP#2 18 Kbd LEDs RGB TPA2012 1 4 audio codec CODEC_RST 1 6 x MSL0201RGB 2 1 Basic RGB Earpiece 2 x TINY control(s) IR LED LED drivers 3 Privacy EAR 2 RX DM3730CBP IR Logic VSMB2948SL ? SMLP36RGB2W3 Flex IR ? 2 x LP55281 3 1 UART[4] EAR 5000246471 From GTA04A4 3 bias, clk, data 3 UART#3 1 IR sense Mod LEDs 4 LTST−C190KRKT, audio PMIC_INT, I2C#4USB#0 I2C#1 RX VEMD10940F I2C#3 LTST−C190TBKT, Codec From GTA04b7v2 Digital microphones nRESPWRON, Codec 3 LTST−C190KFKT 2 x SPK0415HM4H 4 TLV320AIC34 2 2 1 NCX2200, UART[4] Fancy RGB 6 (pre−reorg) NSLEEP1, Fuel TBD LED driver Aux LEDs ... 1 NX3V1G66 4 3 2 x MSL0201RGB 3 I2C_SR[2] ULPI I2C_CNTL[2] Other origin Mic Itf. 3 line[2], bias I2C#2 12 LP55231 CPU 2 4 VBUS, D+, D−, ID VBUS, D+, D− 3 EMIF02−MIC07F3 Headphone amplifer 5 CHRG_IND Companion 4 Privacy.B Being discussed 2 1 HEADPH_EN LCD_LEDS Batt charger 1 CPU BL Battery (contact) I2C#2 1 USB AB 47590−0001 BQ24297 CPU BSI_HDQ Keep/same TPA6130 2 BKBAT CPU, Compan ECI Mic/TV Backup 1 BTEMP 2 1 ??? TLV1702 TS5A22366 ? battery Add / change Ring switch 1 present "TWL4030" 1 POWERON Fuel gauge CPU GPO 3 1 TVOUT, 2 I2C#2 PAS3225P 3R3113 TPS65950 IR BQ27200 Future development CPU 1 TVOUT_EN TS3A225 2 2 I2C#2 Kbd scan ECI[3] VIBRA_{P,M} CPU Batt. CPU CPU CPU CPU I2C#2CPU I2C#3 CPU 2 TCA8418 mic temp. 1 SCREEN_LCK 1 SLIDE_SW 2 CAM_CAP[2] 1 cam_d11 1 stylus ECI_AD Vibra motor KEYIRQ, RESET 2 2 CPU 18 Compan Slide mag. 3.5 mm 3 Power Lock Capture Cam cover 2 Stylus 2 HEADPH_IND ROW[8], COL[10] 18 sensor CPU CPU Vol +/− EVQ−P42B3M ESE16 MLX90248ESE EVQQ0G03K TMD26713 TMD26713 1 5469246 304−106 2 x EVQ−P42B3M ??? 2016−04−25 20:47:19 −0300 Feature comparison (1/2) N900 ! Neo900 CPU TI OMAP3xxx, 600 MHz ! 1 GHz RAM 256 MB ! 1 GB eMMC 32 GB ! 64 GB Modem GSM, UMTS ! Various options Touch Resistive + Dual-touch Sensors Accel, light + Add compass, gyro, baro Infrared Consumer IR (TX only) ! CIR (TX/RX), IrDA Positioning GPS + GLONASS Modem Bands PHS8 4×GSM, 5×UMTS PLS8-E 2×GSM, 3×UMTS, 5×LTE PLS8-US 4×GSM, 3×UMTS, 4×LTE PXS8 4×GSM, 5×UMTS, 3×CDMA2000 Feature comparison (2/2) New features: Neo900 NFC TRF7970A Expansion Hackerbus What we keep: Neo900 Screen 3.5", 800 x 480, Transflective Front camera VGA Main camera 5.0 MP Products NeoN: Upgrade kit (boards, parts) Bring your own N900 No soldering required Neo900: Complete device Built from N900 still in the market More information Web: neo900.org Village: see us at the Neo village.
Recommended publications
  • Enabling Musical Applications on a Linux Phone

    Enabling Musical Applications on a Linux Phone

    University of Wollongong Research Online Faculty of Creative Arts - Papers (Archive) Faculty of Arts, Social Sciences & Humanities 2009 Enabling Musical Applications On A Linux Phone Greg Schiemer University of Wollongong, [email protected] E. Chen Royal Melbourne Institute of Technology Follow this and additional works at: https://ro.uow.edu.au/creartspapers Part of the Arts and Humanities Commons, and the Social and Behavioral Sciences Commons Recommended Citation Schiemer, Greg and Chen, E.: Enabling Musical Applications On A Linux Phone 2009. https://ro.uow.edu.au/creartspapers/36 Research Online is the open access institutional repository for the University of Wollongong. For further information contact the UOW Library: [email protected] ENABLING MUSICAL APPLICATIONS ON A LINUX PHONE Greg Schiemer Eva Cheng Sonic Arts Research Network School of Electrical and Computer Faculty of Creative Arts Engineering University of Wollongong RMIT Melbourne 2522 3000 The prospect of using compiled Arm9 native code of- fers a way to synthesise music using generic music soft- ABSTRACT ware such as Pure data and Csound rather than interpre- tive languages like java and python which have been Over the past decade the mobile phone has evolved to used in mobile devices [1, 2]. A similar approach to mo- become a hardware platform for musical interaction and bile synthesis has been adopted using the Symbian oper- is increasingly being taken seriously by composers and ating system [3]. instrument designers alike. Its gradual evolution has seen The Linux environment is more suited to the devel- improvements in hardware architecture that require al- opment of new applications in embedded hardware than ternative methods of programming.
  • Lamadrid Android

    Lamadrid Android

    ANDROID FGSDFG FDDFGDF ANTITRUST Android antitrust investigation DOMINANT POSITION mokmdokamsdfkmasodmkfosakdmfosdkmf okmsadf IT MARKET ANDROID FGSDFG FDDFGDF ANTITRUST Android antitrust investigation DOMINANT POSITION mokmdokamsdfkmasodmkfosakdmfosdkmf okmsadf IT MARKET ANDROID FGSDFG FDDFGDF ANTITRUST Android antitrust investigation DOMINANT POSITION mokmdokamsdfkmasodmkfosakdmfosdkmf okmsadf IT MARKET ANDROID THOUGHTS IN BRIEF: FGSDFG FDDFGDF(i) A quick overview of the facts (ii) Business considerations and ANTITRUSTbackground DOMINANT(iii)The POSITION Law : (I) Dominance mokmdokamsdfkmasodmkfosakdmfosdkmf(iv)The Law: (II) Predatory okmsadf allegations IT MARKET(v) The Law: (III) Bundling allegations ANDROID FGSDFG THE FACTS FDDFGDF ANTITRUST DOMINANT POSITION mokmdokamsdfkmasodmkfosakdmfosdkmf okmsadf IT MARKET • AndroidANDROID is an open source OS licensed on a royalty-free basis. Licensees remain free to do whatever they wish with the code (e.g. downloading,FGSDFG distributing or modifying –forking- it). • OEMs remain free to use Android with or without Google Apps (e.g. NokiaFDDFGDF X). • WhenANTITRUST OEMs wish to offer certain Google apps on top of Android they can enter into a MADA which requires them to (i) preload a minimum set ofDOMINANT apps (GMS); POSITION (ii) place Search widget and GooglePlay icons in a certain way; and (iii) use Google Search as default engine for the searchmokmdokamsdfkmasodmkfosakdmfosdkmf intent. okmsadf • OEMs (and users) remain at all times free to pre-install at any time any nonIT MARKET-Google app (including a non-Google App Store) = no Google walled garden (room for intra-ecosystem competition) ANDROID A MATTER OF DIFFERENT FGSDFG FDDFGDFBUSINESS MODELS ANTITRUST DOMINANT POSITION mokmdokamsdfkmasodmkfosakdmfosdkmf okmsadf IT MARKET EssentiallyANDROID 3 different business models for mobile operating systems (OSs): i. Apple’s vertically integrated model - Monetization via sales of devices.
  • Meego Smartphones and Operating System Find a New Life in Jolla Ltd

    Meego Smartphones and Operating System Find a New Life in Jolla Ltd

    Jolla Ltd. Press Release July 7, 2012 Helsinki, Finland FOR IMMEDIATE RELEASE MeeGo Smartphones and Operating System Find a New Life in Jolla Ltd. Jolla Ltd. is an independent Finland based smartphone product company which continues the excellent work that Nokia started with MeeGo. The Jolla team is formed by directors and core professionals from Nokia's MeeGo N9 organisation, together with some of the best minds working on MeeGo in the communities. Jussi Hurmola, CEO Jolla Ltd.: "Nokia created something wonderful - the world's best smartphone product. It deserves to be continued, and we will do that together with all the bright and gifted people contributing to the MeeGo success story." Jolla Ltd. will design, develop and sell new MeeGo based smartphones. Together with international private investors and partners, a new smartphone using this MeeGo based OS will be revealed later this year. Jolla Ltd. has been developing a new smartphone product and the OS since the end of 2011. The OS has evolved from MeeGo OS using Mer Core and Qt with Jolla technology including its own brand new UI. The Jolla team consists of a substantial number of MeeGo's core engineers and directors, and is aggressively hiring the top MeeGo and Linux talent to contribute to the next generation smartphone production. Company is headquartered in Helsinki, Finland and has an R&D office in Tampere, Finland. Sincerely, Jolla Ltd. Dr. Antti Saarnio - Chairman & Finance Mr. Jussi Hurmola - CEO Mr. Sami Pienimäki - VP, Sales & Business Development Mr. Stefano Mosconi - CIO Mr. Marc Dillon - COO Further inquiries: [email protected] Jolla Ltd.
  • Overall Features Performance Price

    Overall Features Performance Price

    Scan this code for more info. To download a barcode app, SMS <f2k> to 56677 from a mobile phone with Internet access and camera. SMARTPHONE JOLLA Experience a different way of operating a smartphone without any home or back button — Ashok Pandey to operate, but those who are upgrading to taste the new flavor may struggle a little. At the start, it asks to setup your account and then, it guides you how to use the phone. The first screen reminded us of BB 10 OS. Since there is no Home button, you’ll have to learn a lot of gestures, shortcuts and cues. Sailfish OS sup- ports Android apps and games, and most apps run smoothly. Although there is no issue with Android apps and games on Jolla, but with third party apps like facebook you will find some functionality and notification differences, as Price: `15,490 they are not integrated with the system. Feels good and runs smooth: Jolla has 4.5-inch qHD (960x450p) display, though we were expecting a 720p display, yet screen has good viewing angles. The display is average to use in direct sunlight. It is backed by a 1.4GHz dual-core processor, 1GB RAM and 16 GB internal memory (13.7 GB available to the user) expandable via microSD card. Navigating the phone was quite easy, and launching and switching between apps was smooth. It is equipped with 8 MP rear camera with LED flash that captures quality images in day- light with decent color reproduction. The cam- here are many smartphone manufacturers era comes with several settings for the flash, and OS platforms available in the market.
  • Android Operating System

    Android Operating System

    Software Engineering ISSN: 2229-4007 & ISSN: 2229-4015, Volume 3, Issue 1, 2012, pp.-10-13. Available online at http://www.bioinfo.in/contents.php?id=76 ANDROID OPERATING SYSTEM NIMODIA C. AND DESHMUKH H.R. Babasaheb Naik College of Engineering, Pusad, MS, India. *Corresponding Author: Email- [email protected], [email protected] Received: February 21, 2012; Accepted: March 15, 2012 Abstract- Android is a software stack for mobile devices that includes an operating system, middleware and key applications. Android, an open source mobile device platform based on the Linux operating system. It has application Framework,enhanced graphics, integrated web browser, relational database, media support, LibWebCore web browser, wide variety of connectivity and much more applications. Android relies on Linux version 2.6 for core system services such as security, memory management, process management, network stack, and driver model. Architecture of Android consist of Applications. Linux kernel, libraries, application framework, Android Runtime. All applications are written using the Java programming language. Android mobile phone platform is going to be more secure than Apple’s iPhone or any other device in the long run. Keywords- 3G, Dalvik Virtual Machine, EGPRS, LiMo, Open Handset Alliance, SQLite, WCDMA/HSUPA Citation: Nimodia C. and Deshmukh H.R. (2012) Android Operating System. Software Engineering, ISSN: 2229-4007 & ISSN: 2229-4015, Volume 3, Issue 1, pp.-10-13. Copyright: Copyright©2012 Nimodia C. and Deshmukh H.R. This is an open-access article distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.
  • Openmoko Is Dead. Long Live Openphoenux!

    Openmoko Is Dead. Long Live Openphoenux!

    Openmoko is dead. Long live OpenPhoenux! Nikolaus Schaller, Lukas Märdian LinuxTag, Berlin, May 26th, 2012 Agenda Part one: some history Part two: a long way home Part three: rising from the ashes Part four: flying higher Part five: use it as daily phone – software Q&A Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 2 Some history – Past iterations • FIC GTA01 – Neo 1973 – Roughly 3.000 units sold – Production discontinued • Openmoko GTA02 – Neo Freerunner – Roughly 15.000 units sold – Hardware revision v7 – Production discontinued Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 3 Some history – The End (of part I) • FIC and Openmoko got out • Strong community continues development • Golden Delicious taking the lead – Excellent support for existing devices – Shipping spare parts and add-ons – Tuned GTA02v7++ • Deep sleep fix (aka bug #1024) -> Improved standby time • Bass rework -> Improved sound quality Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 4 Agenda Part one: some history Part two: a long way home Part three: rising from the ashes Part four: flying higher Part five: use it as daily phone – software Q&A Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 5 A long way home How do we get to a new open mobile phone? – open kernel for big ${BRAND} – reverse eng. – order from some ${MANUFACTURER} – hope for openness – DIY, “Use the source, Luke!” Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 6 Using the source: Beagleboard Beagleboard – Full Linux support – Open schematics – Open layout – Expansion connectors – Lots of documentation – Components available Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 7 In theory it could fit (Aug.
  • An Analysis of Power Consumption in a Smartphone

    An Analysis of Power Consumption in a Smartphone

    An Analysis of Power Consumption in a Smartphone Josh Hildebrand Introduction l Mobile devices derive the energy required to operate from batteries that are limited by the size of the device. l The ability to manage energy usage requires a good understanding of where and how the energy is being used. l The advancing functionality of modern smartphones is increasing the pressure on battery lifetime, and increases the need for effective energy management. l Goal is to break down a modern smartphone and measure the power consumption of the devices major subsystems, under a range of usage scenarios. l Results from the breakdown of energy consumption will be validated against two additional mobile devices. l Finally, an analysis of the energy consumption will be performed, and an energy model will be created to allow us to model usage patterns. Methodology / Device Under Test l The approach is to take physical power measurements at the component level on a piece of real hardware. l Three elements to the experimental setup, the device under test, a hardware data acquisition (DAQ) system, and a host computer. l Device under test is the Openmoko Neo Freerunner 2.5G smartphone. Experimental Setup l To measure power to each component, supply voltage and current must be measured. l Current is measured by placing sense resistors on the power supply rails of each component. Resistors were selected such that the voltage drop did not exceed 10mV, less than 1% of the supply voltage. l Voltages were measured using a National Instruments PCI-6229 DAQ. Software l The device was running the Freerunner port of Android 1.5, using the Linux v2.6.29 kernel.
  • A Survey Onmobile Operating System and Mobile Networks

    A Survey Onmobile Operating System and Mobile Networks

    A SURVEY ONMOBILE OPERATING SYSTEM AND MOBILE NETWORKS Vignesh Kumar K1, Nagarajan R2 (1Departmen of Computer Science, PhD Research Scholar, Sri Ramakrishna College of Arts And Science, India) (2Department of Computer Science, Assistant Professor, Sri Ramakrishna College Of Arts And Science, India) ABSTRACT The use of smartphones is growing at an unprecedented rate and is projected to soon passlaptops as consumers’ mobile platform of choice. The proliferation of these devices hascreated new opportunities for mobile researchers; however, when faced with hundreds ofdevices across nearly a dozen development platforms, selecting the ideal platform is often met with unanswered questions. This paper considers desirable characteristics of mobileplatforms necessary for mobile networks research. Key words:smart phones,platforms, mobile networks,mobileplatforms. I.INTRODUCTION In a mobile network, position of MNs has been changing due todynamic nature. The dynamic movements of MNs are tracked regularlyby MM. To meet the QoS in mobile networks, the various issuesconsidered such as MM, handoff methods, call dropping, call blockingmethods, network throughput, routing overhead and PDR are discussed. In this paper I analyse the five most popular smartphone platforms: Android (Linux), BlackBerry, IPhone, Symbian, and Windows Mobile. Each has its own set of strengths and weaknesses; some platforms trade off security for openness, code portability for stability, and limit APIs for robustness. This analysis focuses on the APIs that platforms expose to applications; however in practice, smartphones are manufactured with different physical functionality. Therefore certain platform APIs may not be available on all smartphones. II.MOBILITY MANAGEMENT IP mobility management protocols proposed by Alnasouri et al (2007), Dell'Uomo and Scarrone (2002) and He and Cheng (2011) are compared in terms of handoff latency and packet loss during HM.
  • Mer: Core OS Mobile & Devices

    Mer: Core OS Mobile & Devices

    Mer: Core OS mobile & devices Qt Developer Days - Silicon Valley 2012 Carl Symons Introduction Plasma Active chooses Mer Not just another Linux distribution Focus - device providers Where's Mer? SDKs - apps & platform Get Mer Resources Carl Symons Large company Mktg/BusDev Start-ups } Slightly geeky Grassroots LinuxFest organizer KDE News editor/promo KDE Plasma Active Mer upstream and downstream First LinuxCon September 2009 Portland Moblin is a hot topic Moblin 2.1 for phones introduced MeeGo Announced February 201 0 Moblin & Maemo merger Support for Intel Atom Desktop Summit August 11 , 2011 Berlin; Free Desktop meeting Developer orientation; ExoPCs MeeGo AppStore A real Linux OS LinuxCon - Vancouver August 1 8, 2011 Intel AppUp Developer orientation; ExoPCs MeeGo AppStore show real Linux OS; possibilities Intel AppUp Elements September 28, 2011 National developer conference Tizen announced (led by Intel and Samsung) MeeGo and Qt abandoned HTML5/CSS3 Maemo Reconstructed October 3, 2011 Mer announced The spirit of MeeGo lives on Plasma Active chooses Mer October 5, 2011 No viable alternative Lightweight Mer talent and community Performant Boot time - more than a minute to about 1 5 seconds on Atom tablet Not just another Linux MeeGo - large company dominated; closed governance Mer - Core OS only Packages Focus - Device Providers Complete world class platform for building commercial products Modern, clean Linux Easy to try; easy to port Systems, structures, processes, code to serve device providers Where's Mer? X86, ARM, MIPS NemoMobile
  • Download Android Os for Phone Open Source Mobile OS Alternatives to Android

    Download Android Os for Phone Open Source Mobile OS Alternatives to Android

    download android os for phone Open Source Mobile OS Alternatives To Android. It’s no exaggeration to say that open source operating systems rule the world of mobile devices. Android is still an open-source project, after all. But, due to the bundle of proprietary software that comes along with Android on consumer devices, many people don’t consider it an open source operating system. So, what are the alternatives to Android? iOS? Maybe, but I am primarily interested in open-source alternatives to Android. I am going to list not one, not two, but several alternatives, Linux-based mobile OSes . Top Open Source alternatives to Android (and iOS) Let’s see what open source mobile operating systems are available. Just to mention, the list is not in any hierarchical or chronological order . 1. Plasma Mobile. A few years back, KDE announced its open source mobile OS, Plasma Mobile. Plasma Mobile is the mobile version of the desktop Plasma user interface, and aims to provide convergence for KDE users. It is being actively developed, and you can even find PinePhone running on Manjaro ARM while using KDE Plasma Mobile UI if you want to get your hands on a smartphone. 2. postmarketOS. PostmarketOS (pmOS for short) is a touch-optimized, pre-configured Alpine Linux with its own packages, which can be installed on smartphones. The idea is to enable a 10-year life cycle for smartphones. You probably already know that, after a few years, Android and iOS stop providing updates for older smartphones. At the same time, you can run Linux on older computers easily.
  • Call Your Netbsd

    Call Your Netbsd

    Call your NetBSD BSDCan 2013 Ottawa, Canada Pierre Pronchery ([email protected]) May 17th 2013 Let's get this over with ● Pierre Pronchery ● French, based in Berlin, Germany ● Freelance IT-Security Consultant ● OSDev hobbyist ● NetBSD developer since May 2012 (khorben@) Agenda 1.Why am I doing this? 2.Target hardware: Nokia N900 3.A bit of ARM architecture 4.NetBSD on ARM 5.Challenges of the port 6.Current status 7.DeforaOS embedded desktop 8.Future plans 1. A long chain of events ● $friend0 gives me Linux CD ● Computer not happy with Linux ● Get FreeBSD CD shipped ● Stick with Linux for a while ● Play with OpenBSD on Soekris hardware ● $friend1 gets Zaurus PDA ● Switch desktop and laptop to NetBSD ● I buy a Zaurus PDA ● I try OpenBSD on Zaurus PDA 1. Chain of events, continued ● $gf gets invited to $barcamp ● I play with my Zaurus during her presentation ● $barcamp_attender sees me doing this ● Begin to work on the DeforaOS desktop ● Get some of it to run on the Zaurus ● Attend CCC Camp near Berlin during my bday ● $gf offers me an Openmoko Neo1973 ● Adapt the DeforaOS desktop to Openmoko 1. Chain of events, unchained ● $barcamp_attender was at the CCC Camp, too ● We begin to sell the Openmoko Freerunner ● Create a Linux distribution to support it ● Openmoko is EOL'd and we split ways ● $friend2 gives me sparc64 boxes ● Get more involved with NetBSD ● Nokia gives me a N900 during a developer event ● $barcamp_attender points me to a contest ● Contest is about creating an OSS tablet 1. Chain of events (out of breath) ● Run DeforaOS on NetBSD on the WeTab tablet ● Co-win the contest this way ● $friend3 boots NetBSD on Nokia N900 ● Give a talk about the WeTab tablet ● Promise to work on the Nokia N900 next thing ● Apply to BSDCan 2013 ● Taste maple syrup for the first time in Canada ● Here I am in front of you Pictures: Sharp Zaurus Pictures: Openmoko Freerunner Pictures: WeTab Pictures: DeforaOS 2.
  • Hildon 2.2: the Hildon Toolkit for Fremantle

    Hildon 2.2: the Hildon Toolkit for Fremantle

    Hildon 2.2: the Hildon toolkit for Fremantle Maemo Summit 2009 – Westergasfabriek Amsterdam Alberto Garcia [email protected] Claudio Saavedra [email protected] Introduction Hildon widgets library ● Set of widgets built on top of GTK+ ● Created for Nokia devices based on the Maemo platform: – Nokia 770 – Nokia N800 – Nokia N810 – Nokia N900 ● Released under the GNU LGPL ● Used also in other projects (e.g Ubuntu Mobile) Maemo 5 - Fremantle ● Maemo release for the Nokia N900 ● Modern, usable and finger-friendly UI ● Completely revamped user interface, very different from all previous versions ● Hildon 2.2.0 released on 24 September 2009 Hildon 2.0: Modest http://www.flickr.com/photos/yerga/ / CC BY-NC 2.0 Hildon 2.0: Modest http://www.flickr.com/photos/yerga/ / CC BY-NC 2.0 Hildon 2.2: Modest Hildon 2.2: Modest Hildon source lines of code ● Hildon 1.0 (16 Apr 2007): 23,026 ● Hildon 2.0 (10 Oct 2007): 23,690 ● Hildon 2.2.0 (24 Sep 2009): 36,291 Hildon 2.2: the Fremantle release ● Applications as window stacked views ● Buttons as central UI part ● Scrollable widgets are touchable-friendly ● Kinetic scrolling (HildonPannableArea) Other goals ● New and old-style applications can coexist ● Maintain backward compatibility – No API breakage – UI style preserved (where possible) MathJinni in Fremantle New UI concepts Window stacks ● Hierarchical organization of windows ● Applications have a main view from which different subviews can be opened ● Views: implemented with HildonStackableWindow ● Stacks: implemented with HildonWindowStack Demo HildonButton: