DOCSLIB.ORG

Android Software Platform Development at Fujitsu

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Android Software Platform Development at Fujitsu Android Software Platform Development at Fujitsu Makoto Honda Makoto Kobayashi Masahiko Nagumo Yasuhiro Kawakatsu Smartphones using the Android platform first appeared on the market in October 2008. They have since overtaken Apple’s iPhone—the first entry in the smartphone market—in number of units shipped and have helped to bring about major changes in the way that mobile phones are used. Android was developed and is distributed as open source software that a device maker integrates into its own hardware after adding original software technologies. The Android platform evolves in short cycles on the basis of software and hardware developments as the network infrastructure continues to expand in the form of WiMAX and LTE and as usage scenarios and services become increasingly diverse. Fujitsu has been developing Android smartphones with compelling functions and enhanced convenience since December 2010, when it released the REGZA Phone T-01C featuring a water-resistant enclosure, one-seg support, and FeliCa contactless IC card and infrared-communication functions. This paper describes Fujitsu’s approach to smartphone development, focusing on memory management and current-con- sumption management as important elements in the system design of the Android software platform, diverse manner modes for enhancing user convenience, high-picture-quality technol- ogy achieved by using the Mobile REGZA Engine, and audio-visual device-linking technology based on DLNA standards. 1. Introduction and Internet services, the smartphone market share of November 2007 marked the establishment of the Android devices continued to grow, and in fiscal 2011, Open Handset Alliance (OHA) centered about Google it came to exceed 50%. and other firms, accompanied by the announcement by This onslaught of an open software platform OHA of the Android open software platform. Developed also brought about major changes in the work of de- for mobile devices such as smartphones and tablet veloping conventional mobile phones (i.e., “feature computers, the Android software platform runs on the phones”). Although a massive amount of source code Linux operating system. Only one year later, in October (about 23 million lines including those for Linux) was 2008, the “HTC Dream” developed by HTC Corporation, released as open source and a board support package a Taiwanese firm, was released by T-Mobile in North (BSP) for software-porting purposes was provided by America as the first phone product to use the Android the chipset vendor, each device maker had to acquire platform. This was one year and four months after the technical skills needed to make the best use of the appearance of Apple’s first iPhone, which took this platform, which was still a semi-finished prod- the mobile phone market by storm and launched the uct with little in the way of technical documentation. worldwide shift to smartphones. Early Android devices Moreover, not only was Android undergoing either did not measure up to Microsoft’s Windows Phone or minor or major version upgrades every half-year or Apple’s iPhone in terms of specifications, but thanks to so, the device-related requirements were steadily the open-source nature of Android software and ease increasing. The HTC Dream that made its market debut of programming on the Android platform as well as in October 2008 was equipped with a single CPU having the evolution of Google Play (Google’s marketplace) an operating frequency of 528 MHz, but in three years 238 FUJITSU Sci. Tech. J., Vol. 49, No. 2, pp. 238–244 (April 2013) M. Honda et al.: Android Software Platform Development at Fujitsu time, Android products would come to feature a 1-GHz- Android software platform development, focusing on class, dual-core CPU, four or five times the amount of memory management and power-saving measures memory (1 GB random access memory [RAM]), and in system design, an eco function and manner modes six times the display resolution (high-definition [HD] implemented in the application framework, and high- class), as shown in Figure 1. Battery capacity, on the picture-quality technology and AV-device-linking other hand, was increased by only 1.5 times for reasons technology in multimedia design. of weight and portability. Power-saving measures are therefore an important issue in Android devices, and 2. System platform technologies it has become necessary to enable switching between In feature phone development, the device maker operating modes in accordance with the usage scenario handles total system design, from hardware to ap- without sacrificing performance and to provide power- plications, taking into account stability, consistency, saving functions that the user can customize. Device performance, and marketability requirements. In makers must therefore develop stable and high-quality smartphone development, however, the applications products in pace with the evolution of the Android soft- developed and installed by the device maker make up ware platform while incorporating original technology only a portion of the applications since most smart- and user-friendly features. phone applications are developed by third parties In December 2010, Fujitsu released the REGZA and are installed by the user after the smartphone Phone T-01C featuring a water-resistant enclosure, purchase. What this means is that a device maker de- one-seg support, and FeliCa contactless IC card and veloping a smartphone must design the system so that infrared-communication functions. Fujitsu has since it will operate stably for the diverse types of applica- been working to improve the usability and performance tions that might be installed by the user. of its Android smartphones by various means, such Important issues in system design include as by making the human-centric functions developed stability, performance, power saving, operability, com- and enhanced for feature phones compatible with patibility, security, and exception processing. Here we smartphones, improving the user interface (UI), adopt- describe memory management, which greatly affects ing a dual-core CPU, supporting Long Term Evolution system stability, and current-consumption manage- (LTE), Worldwide Interoperability for Microwave Access ment, which affects battery life. (WiMAX), and Digital Living Network Alliance (DLNA) standards, and developing functions for linking to 2.1 Memory management audio-visual (AV) devices. Total memory size for program execution (i.e., In this paper, we introduce Fujitsu’s approach to RAM), the amount of memory used by the system (“al- located memory”), and the amount available to the user (“available memory”) are shown in Figure 2 for 7 five Fujitsu-developed devices: REGZA Phone T-01C (re- 6 Display resolution leased December 2010), F-12C (released August 2011), 5 CPU operating frequency 4 Memory capacity (RAM) 1200 3 1000 800 Available memory 2 Allocated memory Battery capacity 600 1 400 200 0 memory (MB) size Program-execution Performance improvement ratio HTC Dream Nexus One Nexus S Galaxy Nexus 0 Single core Single core Single core Dual core Android 2.1 Android 2.3 Android 2.3 Android 2.3 Android 4.0 Android 1.6 Android 2.1 Android 2.3 Android 4.0 REGZA Phone F-12C ARROWS µ ARROWS X LTE REGZA Phone October 2008 January 2010 December 2010 November 2011 T-01C F-07D F-05D T-02D Figure 1 Figure 2 Performance improvement of Android reference devices. Memory available to user immediately after device startup. Figure1 Figure 2 FUJITSUPerformance Sci. Tech. J., Vol. 49, improvement No. 2 (April 2013) of Memory available to user immediately 239 Android reference terminals. after terminal startup M. Honda et al.: Android Software Platform Development at Fujitsu ARROWS μ F-07D (released January 2012), ARROWS Dalvik heap size X LTE F-05D (released December 2011) and REGZA (GrowthLimit) Phone T-02D (released July 2012). The total memory Application RAM size limit size reached 1 GB in the F-05D model, and it remained 1 GB in the T-02D model. However, the amount avail- Suppress invocation of able to the user actually decreased. There are a variety OOMK by balancing settings of reasons for this. In addition to the fact that the MAX_HIDDEN_APPS LMK threshold amount of memory used by the Android system has am_killer been increasing with almost every version upgrade, the Invoke when available Invoke on basis of number of applications amount of memory needed by applications at run-time memory is low running in background has been increasing owing to improvements in display resolution and system performance. Moreover, the Out Of Memory Killer (OOMK) number of simultaneously running applications has Invoke when memory been increasing. allocation fails Android provides a mechanism called “low memory killer” (LMK) for efficiently reallocating pro- Figure 3 MemoryFigure management 3 parameters for process execution in gram-execution memory when the amount available Android. becomes low. It works by releasing and reallocating Memory management parameters unneeded allocated memory areas depending on the for process execution in Android. execution environment. This makes it possible for GrowthLimit. The larger the execution memory per ap- the user to not only use the available memory shown plication, the smaller the number of applications that in Figure 2 but also to use a portion of the already can run at the same time. Additionally, an application allocated memory. Since total program-execution that uses an amount of memory exceeding GrowthLimit memory is limited, however, it is desirable that as cannot be launched. many unneeded allocated memory areas as possible 3) MAX_HIDDEN_APPS be released and made available. This parameter is used for defining the maximum Android provides three parameters for managing number of applications running in the background. It program-execution memory: LMK threshold, Dalvik is used to limit the number of launched applications. If heap size, and MAX_HIDDEN_APPS (Figure 3). These the number specified by MAX_HIDDEN_APPS is about to are summarized below. be exceeded, a system process called am_killer releases 1) LMK threshold unnecessary background applications.
Load more

Recommended publications
  • Download Volume 13 (PDF)
    Volume 13, Summer 2019 Copyright Ó 2019 Assistive Technology Industry Association ISSN 1938-7261 Assistive Technology Outcomes and Benefits | i The Role of Research in Influencing Assistive Technology Products, Policy, and Practice Volume 13, Summer 2019 Assistive Technology Outcomes and Benefits The Role of Research in Influencing Assistive Technology Products, Policy, and Practice Volume 13, Summer 2019 Editor in Chief Focused Issue Editor Jennifer L. Flagg Kathleen M. Murphy Center on KT4TT, University oF BuFFalo American Institutes For Research Publication Managers Associate Editors Victoria A. Holder Kate Herndon Tools For LiFe, Georgia Institute oF Technology American Printing House For the Blind Elizabeth A. Persaud Carolyn P. Phillips Tools For LiFe, Georgia Insitute oF Technology Tools For LiFe, Georgia Institute oF Technology Caroline Van Howe Copy Editor Assistive Technology Industry Association Beverly Nau Assistive Technology Outcomes and Benefits (ATOB) is a collaborative peer-reviewed publication of the Assistive Technology Industry Association (ATIA). Editing policies oF this issue are based on the Publication Manual oF the American Psychological Association (6th edition) and may be Found online at www.atia.org/atob/editorialpolicy. The content does not reflect the position or policy of ATIA and no official endorsement should be inferred. Editorial Board Members and Managing Editors David Banes Beth Poss Managing Director, David Banes Access and Administrator, Montgomery County Schools, Inclusion Services Maryland Russell T. Cross Ben SatterField Director of Clinical Operations, Prentke Romich Research Consultant, Center for AT Company Excellence, Tools For LiFe at Georgia Institute oF Technology Anya Evmenova Associate Professor, Division of Special Judith Schoonover Education and disAbility Research, George Occupational Therapist and AT Consultant, Mason University Sterling, Virginia American Occupational Therapy Association, Lori Geist Inc.
    [Show full text]
  • Completing the TAC Request Application Form
    Training Module Four: Completing the TAC Request Application Form TAC Application Module July 2018 v1.0 All product names, model numbers or other manufacturer identifiers not attributed to GSMA are the property of their respective owners. ©GSMA Ltd 2018 Before applying for TAC, your company must be registered and have sufficient TAC credit Brand owner 1 registration TAC 2 payment TAC 3 application TAC 4 certificate Select Request a TAC to begin the TAC Application Request Form process Take great care completing the form with the details of the device that will use the TAC The form has seven sections: 1 2 3 4 5 6 7 Device Manufacturing Operating Networks LPWAN Device Review details details System Certification Bodies Your details will already be there! 1 2 3 4 5 6 7 Device details Applicant name Applicant email This information is address automatically populated from log-in, It is not editable here C Brand Name Select the equipment type you require TAC for, from the dropdown 1 2 3 4 5 6 7 Device details Feature phone Smartphone Tablet IoT device Wearable Dongle Modem WLAN router There should be only one model name, but you may input up to three marketing names 1 2 3 4 5 6 7 Device details Device model name is a specific name given to the Model name handset. This can vary from the marketing name. The marketing name is typically used as the name the TM Marketing name device is sold/marketed to general public. You can include up to 3 marketing names, separated by a comma.
    [Show full text]
  • A Middleware Framework for Application-Aware and User-Specific Energy Optimization in Smart Mobile Devices
    Pervasive and Mobile Computing 20 (2015) 47–63 Contents lists available at ScienceDirect Pervasive and Mobile Computing journal homepage: www.elsevier.com/locate/pmc A middleware framework for application-aware and user-specific energy optimization in smart mobile devices Sudeep Pasricha a,∗, Brad K. Donohoo b, Chris Ohlsen c a Colorado State University, Fort Collins, CO 80523, USA b U.S. Department of the Air Force, Roy, UT 84067, UT 84067, USA c Woodward, Inc., Fort Collins, CO 80525, USA article info a b s t r a c t Article history: Mobile battery-operated devices are becoming an essential instrument for business, com- Received 5 August 2014 munication, and social interaction. In addition to the demand for an acceptable level of per- Received in revised form 22 December 2014 formance and a comprehensive set of features, users often desire extended battery lifetime. Accepted 7 January 2015 In fact, limited battery lifetime is one of the biggest obstacles facing the current utility and Available online 14 January 2015 future growth of increasingly sophisticated ``smart'' mobile devices. This paper proposes a novel application-aware and user-interaction aware energy optimization middleware Keywords: framework (AURA) for pervasive mobile devices. AURA optimizes CPU and screen back- Energy optimization Smart mobile systems light energy consumption while maintaining a minimum acceptable level of performance. Pervasive computing The proposed framework employs a novel Bayesian application classifier and management Machine learning strategies based on Markov Decision Processes and Q-Learning to achieve energy savings. Middleware Real-world user evaluation studies on Google Android based HTC Dream and Google Nexus One smartphones running the AURA framework demonstrate promising results, with up to 29% energy savings compared to the baseline device manager, and up to 5×savings over prior work on CPU and backlight energy co-optimization.
    [Show full text]
  • 2014 BT Compatibility List 20141030
    Item Brand Name Model 1 Acer Acer beTouch E210 2 Acer acer E400 3 Acer acer P400 4 Acer DX650 5 Acer E200 6 Acer Liquid E 7 Acer Liquid Mini (E310) 8 Acer M900 9 Acer S110 10 Acer Smart handheld 11 Acer Smart handheld 12 Acer Smart handheld E100 13 Acer Smart handheld E101 14 Adec & Partner AG AG vegas 15 Alcatel Alcatel OneTouch Fierce 2 16 Alcatel MISS SIXTY MSX10 17 Alcatel OT-800/ OT-800A 18 Alcatel OT-802/ OT-802A 19 Alcatel OT-806/ OT-806A/ OT-806D/ OT-807/ OT-807A/ OT-807D 20 Alcatel OT-808/ OT-808A 21 Alcatel OT-880/ OT-880A 22 Alcatel OT-980/ OT-980A 23 Altek Altek A14 24 Amazon Amazon Fire Phone 25 Amgoo Telecom Co LTD AM83 26 Apple Apple iPhone 4S 27 Apple Apple iPhone 5 28 Apple Apple iPhone 6 29 Apple Apple iPhone 6 Plus 30 Apple iPhone 2G 31 Apple iPhone 3G 32 Apple iPhone 3Gs 33 Apple iPhone 4 34 Apple iPhone 5C 35 Apple iPHone 5S 36 Aramasmobile.com ZX021 37 Ascom Sweden AB 3749 38 Asustek 1000846 39 Asustek A10 40 Asustek G60 41 Asustek Galaxy3_L and Galaxy3_S 42 Asustek Garmin-ASUS M10E 43 Asustek P320 44 Asustek P565c 45 BlackBerry BlackBerry Passport 46 BlackBerry BlackBerry Q10 47 Broadcom Corporation BTL-A 48 Casio Hitachi C721 49 Cellnet 7 Inc. DG-805 Cellon Communications 50 C2052, Technology(Shenzhen) Co., Ltd. Cellon Communications 51 C2053, Technology(Shenzhen) Co., Ltd. Cellon Communications 52 C3031 Technology(Shenzhen) Co., Ltd. Cellon Communications 53 C5030, Technology(Shenzhen) Co., Ltd.
    [Show full text]
  • Present Challenges and Potential for Reform
    THE FOREIGN INVESTMENT CLIMATE IN CHINA: PRESENT CHALLENGES AND POTENTIAL FOR REFORM HEARING BEFORE THE U.S.-CHINA ECONOMIC AND SECURITY REVIEW COMMISSION ONE HUNDRED FOURTEENTH CONGRESS FIRST SESSION WEDNESDAY, January 28, 2015 Printed for use of the United States-China Economic and Security Review Commission Available via the World Wide Web: www.uscc.gov UNITED STATES-CHINA ECONOMIC AND SECURITY REVIEW COMMISSION WASHINGTON: 2015 ii U.S.-CHINA ECONOMIC AND SECURITY REVIEW COMMISSION Hon. WILLIAM A. REINSCH, Chairman Hon. DENNIS C. SHEA, Vice Chairman Commissioners: CAROLYN BARTHOLOMEW DANIEL M. SLANE ROBIN CLEVELAND SEN. JAMES TALENT JEFFREY L. FIEDLER DR. KATHERINE C. TOBIN SEN. CARTE P. GOODWIN MICHAEL R. WESSEL MICHAEL R. DANIS, Executive Director The Commission was created on October 30, 2000 by the Floyd D. Spence National Defense Authorization Act for 2001 § 1238, Public Law No. 106-398, 114 STAT. 1654A-334 (2000) (codified at 22 U.S.C. § 7002 (2001), as amended by the Treasury and General Government Appropriations Act for 2002 § 645 (regarding employment status of staff) & § 648 (regarding changing annual report due date from March to June), Public Law No. 107-67, 115 STAT. 514 (Nov. 12, 2001); as amended by Division P of the “Consolidated Appropriations Resolution, 2003,” Pub L. No. 108-7 (Feb. 20, 2003) (regarding Commission name change, terms of Commissioners, and responsibilities of the Commission); as amended by Public Law No. 109- 108 (H.R. 2862) (Nov. 22, 2005) (regarding responsibilities of Commission and applicability of FACA); as amended by Division J of the “Consolidated Appropriations Act, 2008,” Public Law Nol.
    [Show full text]
  • Samsung Nexus Manual Pdf
    Samsung Nexus Manual Pdf Sumptuous or panzer, Shell never hirsling any ureters! Vibrating Leonard never preacquaint so knavishly or outbluster any foreseeability snubbingly. Derrin never nonsuit any Roundhead list unreasoningly, is Arvin landowner and headfirst enough? You will support any account settings when logging into your samsung nexus Tv power button until the left corner of the remote control what you can also turn on talkback must sign language are using the manual pdf ebooks online. Google Nexus 10 Tab Wi-Fi Owner Information Samsung. Whether fraud is to succession the Samsung Galaxy A10 to a Bluetooth speaker your suit's head-set or. Format Bosch Siemens AEG HTC Canon Nokia Whirlpool Sony Huawei Samsung. Secured networks are service manual pdf. Samsung Nexus User Manual Free eBooks in the Genres. Galaxy Nexus Users Guide. Zte k disassembly. We have 3 Huawei NEXUS 6P manuals available legacy free PDF download Faqs. You factory reset device that opens the pdf manual pdf. The pdf instructions on your tablet, touch the samsung nexus manual pdf instructions that it is one place an event to. Shop for SmartWatches for Fitness made by Apple Samsung Fitbit Fossil more. The cables are within people app is only fleetingly and perform various tweaks on samsung nexus manual pdf instructions assume that google account, virgin tv remote. Valvetronix VT20 musical instrument amplifier pdf manual download. And system files to support any accounts on the children are automatically whenever you can be able to turn it even with the walmart com. Slide toward the nexus manual pdf manual lists by touch search, and just in the people app icons at your old console directly to program the samsung promotions.
    [Show full text]
  • Sprint Complete
    Sprint Complete Equipment Replacement Insurance Program (ERP) Equipment Service and Repair Service Contract Program (ESRP) Effective July 2021 This device schedule is updated regularly to include new models. Check this document any time your equipment changes and before visiting an authorized repair center for service. If you are not certain of the model of your phone, refer to your original receipt or it may be printed on the white label located under the battery of your device. Repair eligibility is subject to change. Models Eligible for $29 Cracked Screen Repair* Apple Samsung HTC LG • iPhone 5 • iPhone X • GS5 • Note 8 • One M8 • G Flex • G3 Vigor • iPhone 5C • iPhone XS • GS6 • Note 9 • One E8 • G Flex II • G4 • iPhone 5S • iPhone XS Max • GS6 Edge • Note 20 5G • One M9 • G Stylo • G5 • iPhone 6 • iPhone XR • GS6 Edge+ • Note 20 Ultra 5G • One M10 • Stylo 2 • G6 • iPhone 6 Plus • iPhone 11 • GS7 • GS10 • Bolt • Stylo 3 • V20 • iPhone 6S • iPhone 11 Pro • GS7 Edge • GS10e • HTC U11 • Stylo 6 • X power • iPhone 6S Plus • iPhone 11 Pro • GS8 • GS10+ • G7 ThinQ • V40 ThinQ • iPhone SE Max • GS8+ • GS10 5G • G8 ThinQ • V50 ThinQ • iPhone SE2 • iPhone 12 • GS9 • Note 10 • G8X ThinQ • V60 ThinQ 5G • iPhone 7 • iPhone 12 Pro • GS9+ • Note 10+ • V60 ThinQ 5G • iPhone 7 Plus • iPhone 12 Pro • A50 • GS20 5G Dual Screen • iPhone 8 Max • A51 • GS20+ 5G • Velvet 5G • iPhone 8 Plus • iPhone 12 Mini • Note 4 • GS20 Ultra 5G • Note 5 • Galaxy S20 FE 5G • GS21 5G • GS21+ 5G • GS21 Ultra 5G Monthly Charge, Deductible/Service Fee, and Repair Schedule
    [Show full text]
  • February 2010 Admob Mobile Metrics Report
    AdMob Mobile Metrics Report AdMob serves ads for more than 15,000 mobile Web sites and applications around the world. AdMob stores and analyzes the data from every ad request, impression, and click and uses this to optimize ad matching in its network. This monthly report offers a snapshot of its data to provide insight into trends in the mobile ecosystem. February 2010 Find archived reports and sign up for future report notifications at metrics.admob.com. AdMob Mobile Metrics Report February 2010 New and Noteworthy For this month's report, we separate the traffic in our network into three categories – smartphones, feature phones, and mobile Internet devices – to examine the growth rates of each over the past year and look at the traffic share of smartphone operating systems and manufacturers of feature phones. * In February 2010, smartphones accounted for 48% of AdMob’s worldwide traffic, up from 35% in February 2009. The strong growth of iPhone and Android traffic, fueled by heavy application usage, was primarily responsible for the increase. In absolute terms, smartphone traffic increased 193% over the last year. * Feature phones declined from 58% to 35% of AdMob's total traffic as users began switching to smartphones. Although the share of traffic from feature phones as a category declined, in absolute terms traffic grew 31% year-over-year. * The mobile Internet devices category experienced the strongest growth of the three, increasing to account for 17% of traffic in AdMob’s network in February 2010. The iPod touch is responsible for 93% of this traffic; other devices include the Sony PSP and Nintendo DSi.
    [Show full text]
  • Android Support for Microsoft Exchange in Pure Google Devices
    Android support for Microsoft Exchange in pure Google devices Note: The information presented here is intended for Microsoft Exchange administrators who are planning and implementing support for any of these pure Google devices running Android. Android support by version and device The following AndroidTM versions support Microsoft Exchange information services and security policies: ● Android 4.0.4 (Ice Cream Sandwich) ● Android 4.1 and later (Jelly Bean) The following “pure Google” devices support the Microsoft Exchange services and policies: ● Galaxy Nexus phones running Android ● Nexus S phones running Android ● Motorola Xoom tablets running Android ● Nexus 4 phones running Android ● Nexus 7 tablets running Android ● Nexus 10 tablets running Android Requirements To support Android 4.0 running on pure Google devices, you must be running one of the following versions of Microsoft Exchange: ● Exchange Server 2010 SP1 with Exchange ActiveSync 14.1 ● Exchange Server 2010 with Exchange ActiveSync 14.0 ● Exchange Server 2007 SP1 with Exchange ActiveSync 12.1 ● Exchange Server 2007 with Exchange ActiveSync 12.0 ● Exchange Server 2003 SP2 with Exchange ActiveSync 2.5 The following information applies to the Android platform, including the Settings, Email, Calendar, People, and related apps as built by Google. If a device manufacturer has modified these apps on its own devices, contact the manufacturer for information about support for Exchange features. Supported information services Users can add Microsoft Exchange accounts to their pure Google devices by using the Account & Sync settings available from the Settings or Email app. Android supports the following Exchange information services: ● Adding Exchange user accounts (via an ActiveSync server), and enforcement of some mailbox policies (as described in “Supported security policies,” next).
    [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]
  • Estimating Consumer Inertia in Repeated Choices of Smartphones
    A Service of Leibniz-Informationszentrum econstor Wirtschaft Leibniz Information Centre Make Your Publications Visible. zbw for Economics Grzybowski, Lukasz; Nicolle, Ambre Working Paper Estimating Consumer Inertia in Repeated Choices of Smartphones CESifo Working Paper, No. 7434 Provided in Cooperation with: Ifo Institute – Leibniz Institute for Economic Research at the University of Munich Suggested Citation: Grzybowski, Lukasz; Nicolle, Ambre (2018) : Estimating Consumer Inertia in Repeated Choices of Smartphones, CESifo Working Paper, No. 7434, Center for Economic Studies and ifo Institute (CESifo), Munich This Version is available at: http://hdl.handle.net/10419/198794 Standard-Nutzungsbedingungen: Terms of use: Die Dokumente auf EconStor dürfen zu eigenen wissenschaftlichen Documents in EconStor may be saved and copied for your Zwecken und zum Privatgebrauch gespeichert und kopiert werden. personal and scholarly purposes. Sie dürfen die Dokumente nicht für öffentliche oder kommerzielle You are not to copy documents for public or commercial Zwecke vervielfältigen, öffentlich ausstellen, öffentlich zugänglich purposes, to exhibit the documents publicly, to make them machen, vertreiben oder anderweitig nutzen. publicly available on the internet, or to distribute or otherwise use the documents in public. Sofern die Verfasser die Dokumente unter Open-Content-Lizenzen (insbesondere CC-Lizenzen) zur Verfügung gestellt haben sollten, If the documents have been made available under an Open gelten abweichend von diesen Nutzungsbedingungen
    [Show full text]
  • Apple and Nokia: the Transformation from Products to Services
    9 Apple and Nokia: The Transformation from Products to Services In the mid- to late 2000s, Nokia flourished as the world’s dominant mobile phone – and mobile phone operating software – producer. Founded in 1871 originally as a rubber boots manufacturer, by 2007 Nokia produced more than half of all mobile phones sold on the planet, and its Symbian mobile operating system commanded a 65.6 percent global market share. 1 But within half a decade, Nokia would falter and be surpassed in the smartphone market not only by Apple’s revolu- tionary iPhone but also by competitors including Google and Samsung. And in September 2013, Nokia would sell its mobile phone business to Microsoft for $7 billion. 2 Apple literally came out of nowhere – it sold exactly zero mobile phones before the year 2007 (the year Nokia held more than half of the global market share) – but by the first quarter of 2013, Apple had captured almost 40 percent of the US smartphone market and over 50 percent of the operating profit in the global handset industry.3 In fiscal year 2013, Apple would sell five times more smart- phones than Nokia: 150 million iPhones compared to Nokia’s sales of 30 million Lumia Windows phones. 4 In contrast to Nokia, Apple real- ized it wasn’t just about the mobile device itself, it was about leveraging software to create a platform for developing compelling mobile experi- ences – including not just telephony but also music, movies, applica- tions, and computing – and then building a business model that allows partners to make money alongside the company (e.g., Apple’s iTunes and AppStore) and, in so doing, perpetuate a virtuous cycle of making the iPhone attractive to customers over multiple life cycles through ever-ex- panding feature sets.
    [Show full text]