DOCSLIB.ORG

Pining for Data

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pining for Data Pining for data Acquiring and Analysing a PinePhone (Manjaro) Kathryn Hedley @4enzikat0r Why am I here? • To learn about PinePhones • How to acquire data from a device • What data is stored on a PinePhone • Where some data of interest is stored Wait, what’s a PinePhone? PinePhone 101 • Open source smartphone • Intended to deliver functional Linux phone to users & create a market for Linux-based smartphones • Supports existing Linux phone projects (https://wiki.pine64.org/wiki/PinePhone_Software_Releases): • Ubuntu Touch • Manjaro • Mobian • Fedora • Many more! • https://www.pine64.org/pinephone/ Meet my PinePhone – Piney McPinephone Purchased directly from https://pine64.com/ Cracking passwords for fun • root user password: root • manjaro user password: 123456 • (both users have admin rights & can sudo) …or just Google it! https://wiki.pine64.org/wiki/PinePhone What happens when you connect the device via USB? Hard route – UART - flick a switch & buy a cable Default state: UART enabled: UART cable: https://pine64.com/product/pinebook-pinephone-pinetab-serial-console Easy route – Terminal, dd & SD card • Open Terminal • Default pin code: 123456 • Can’t change in Settings • (Can change in Terminal with passwd) • Mount SD card • sudo mkdir /mnt/sdcard • sudo mount /dev/mmcblk0p1 /mnt/sdcard • Image device • sudo dd if=/dev/mmcblk2 of=/mnt/sdcard/mmcblk2.dd • Unmount SD card • sudo umount /mnt/sdcard Data commonly found on Linux systems • Operating system information • Device identifiers • Device suspend & reboot events • USB cable connection events not found • Bash history • Recent activity • Network connections OS version information • \etc\lsb-release Device ID • \etc\machine-id Device suspend events • \var\log\pp-suspend.log • NOT updated during testing Device boot, reboot, login events • \var\log\wtmp (btmp & lastlog are empty) • Timestamps are empty & not properly parsed by last command Bash history • \home\manjaro\.bash_history NOTE: only updated on device shutdown/reboot Recent activity • \home\manjaro\.local\share\rece ntly-used.xbel • SOME recent events: • Image file viewed: IMG20210405202000.jpg (double click) – 5 April 2021 19:22 UTC+2 • Photo added to contact – 5 April 2021 21:00 UTC+1 • Text file created using gedit application – 5 April 2021 22:22 UTC+1 • Timestamps appear to be in device local time (very few examples to base this on!) • Not consistently updated WiFi connections • \etc\NetworkManager\system-connections\ • One file per remembered SSID - <SSID>.nmconnection • Contains: SSID, UUID, security info, password • ‘Forgotten’ network nmconnection files deleted (can be carved using ‘[connection]’ header) Phone-specific data • Software - Installed applications • Calls - Call logs • Chatty - SMS messages (MMS not possible on my PinePhone) • Telegram Messenger • Contacts • Megapixels – Photographs taken with the camera • Calendar entries • To Do - Task lists • Text Editor - Documents • Firefox - Browser history • Map data Installed applications (Software) • \var\log\pacman.log • Includes prerequisites, so quite noisy! Call Log (calls) • \home\manjaro\.local\share\calls\records.db • Inbound field: 0 = outgoing call, 1 = incoming call SMS Messages (chatty) – SQLite database • \home\manjaro\.purple\chatty\db\chatty-history.db • Timestamps are Unix numeric values • Direction: -1 = outgoing (sent), 1 = incoming (received) SMS Messages (chatty) – HTML files • \home\manjaro\.purple\logs\mm-sms\sms • One subfolder per sender/recipient phone number, one HTML file per date • Includes sent or received SMS message SMS Messages (chatty) – XML list of SMS contacts • \home\manjaro\.purple\blist.xml • Lists all senders/recipients for which you have communicated via SMS • ‘name’ matches that shown to the user i.e. phone number or organization name • ‘alias’ only present for device contacts • 'chatty-unknown-contact’ only present for contacts not in device contacts Telegram • \home\manjaro\.local\share\TelegramDesktop Contacts • \home\manjaro\.local\share\evolution\addressbook\system\contacts.db • folder_id table • uid = unique ID – links to folder_id_phone_list table (phone number) & folder_id_email_list (email address) • Rev = last modified date Contact photos • \home\manjaro\.local\share\evolution\addressbook\system\photos\ • PNG files named for contact’s UID - <UID>_photo-file0.image%2Fpng Photographs taken with the camera (Megapixels) • \home\manjaro\Pictures\ Photograph thumbnails… maybe! • \home\manjaro\.cache\thumbnails\ • Only one thumbnail created here during testing Calendar entries • \home\manjaro\.local\share\evolution\calendar\ system\calendar.ics • vCalendar file, starts ‘BEGIN:VCALENDAR’ • Each event starts BEGIN: VEVENT • Each event ends END: VEVENT • UID = unique event ID • DTSTAMP = CREATED = event creation date/time • (so far!) • DTSTART = event start • DTEND = event end • SUMMARY = event name • LAST-MODIFIED – event last modified date/time Tasklists (To Do) • \home\manjaro\.config\evolution\sources\<40-char hex string>.source • One per ‘List’, includes list name (DisplayName) but not individual tasks Tasklist tasks (To Do) • \home\manjaro\.local\share\evolution\tasks\<same 40-char hex string>\tasks.ics • vCalendar file, starts ‘BEGIN:VCALENDAR’ Tasklist tasks (To Do) Each individual task in this file has the structure: • Date/time values appear to be in local time BEGIN:VTODO to the device (UTC+2 in this case) UID:618e6a9d87ba9708889751c729490e705f440d6c • (again, only a small amount of testing done DTSTAMP:20210405T191820Z so far) SUMMARY:tasky mctaskface 1 CREATED:20210405T191821Z • Summary is the task name within the LAST-MODIFIED:20210405T191821Z tasklist END:VTODO Documents created using Text Editor • \home\manjaro\Documents\ Firefox (desktop version) history • \home\manjaro\.mozilla\firefox\firefox.default\places.sqlite • \home\manjaro\.mozilla\firefox\tk0topo4.default-release\places.sqlite Firefox cookies • \home\manjaro\.mozilla\firefox\firefox.default\cookies.sqlite • \home\manjaro\.mozilla\firefox\tk0topo4.default-release\cookies.sqlite Firefox cache • \home\manjaro\.mozilla\firefox\firefox.default\cache2\ • No cache2 folder in \home\manjaro\.mozilla\firefox\tk0topo4.default-release\ Firefox search history • \home\manjaro\.mozilla\firefox\firefox.default\formhistory.sqlite • \home\manjaro\.mozilla\firefox\tk0topo4.default-release\formhistory.sqlite Map searches • \home\manjaro\.local\share\maps-places.json • “name” – search term • GPS co-ordinates, altitude, date/time search conducted (UNIX numeric) Map tiles • \home\manjaro\.cache\champlain\mapbox.streets-v11\ Future stuff to think about • Geary (email app) wouldn’t open during testing • Suspect data would be stored in \home\manjaro\.local\share\evolution\mail • Unconfirmed • Other Linux variants – look at re-flashing device & doing the same evaluation process Cheatsheet https://www.khyrenz.com/blog/pinephone-forensics/ …so you don’t actually need to remember anything I just said! .
Load more

Recommended publications
  • Plasma on Mobile Devices
    Plasma on Mobile devices Application Ecosystem MC Bhushan Shah KDE Developer Agenda ● Initial development of the Plasma Mobile ● Basic architecture details ● Advantages to KDE community ● Application ecosystem and development ● Future for Plasma Mobile ● Challenges Introduction ● KDE developer and sysadmin ● Plasma Mobile maintainer and lead developer ● Employed by Bluesystems GmbH ● From Vadodara, India KDE ● Previously known as the K Desktop Environment ● Now community, which creates free software for end users ● Several products including Plasma, KDE Frameworks, KDE applications. Plasma Mobile ● Announced in the July 2015 ● Vision of providing completely free and open-source mobile platform which respects user’s privacy and freedom. ● Initial prototype on the LG Nexus 5. Initial Development ● LGE Nexus 5 as reference device ● Ubuntu Touch 15.04 (vivid) as base system ● Makes use of the Android binary blobs / drivers ● Can also run on the desktop system for development Basic architecture details ● KWin wayland as compositor ● DRM/GBM or hwcomposer backends ● plasmashell and mobile shell package ● QtQuickControls2 and Kirigami for application development Advantages to KDE community ● Several performance improvements ● Better touch input support in applications and shell ● Improvements in Wayland support ● More modular and re-usable user interfaces Application ecosystem and development ● QtQuickControls2 and Kirigami as toolkit ● CMake/QMake as a buildsystem ● Various bundle formats as well as native distribution packaging for the distribution
    [Show full text]
  • Building a Distribution: Openharmony and Openmandriva
    Two different approaches to building a distribution: OpenHarmony and OpenMandriva Bernhard "bero" Rosenkränzer <[email protected]> FOSDEM 2021 -- February 6, 2021 1 MY CONTACT: [email protected], [email protected] Way more important than that, he also feeds LINKEDIN: dogs. https://www.linkedin.com/in/berolinux/ Bernhard "bero" Rosenkränzer I don't usually do "About Me", but since it may be relevant to the topic: Principal Technologist at Open Source Technology Center since November 2020 President of the OpenMandriva Association, Contributor since 2012 - also a contributor to Mandrake back in 1998/1999 2 What is OpenHarmony? ● More than an operating system: Can use multiple different kernels (Linux, Zephyr, ...) ● Key goal: autonomous, cooperative devices -- multiple devices form a distributed virtual bus and can share resources ● Initial target devices: Avenger 96 (32-bit ARMv7 Cortex-A7+-M4), Nitrogen 96 (Cortex-M4) ● Built with OpenEmbedded/Yocto - one command builds the entire OS ● Fully open, developed as an Open Source project instead of an inhouse product from the start. ● For more information, visit Stefan Schmidt's talk in the Embedded devroom, 17.30 and/or talk to us at the Huawei OSTC stand. 3 What is OpenMandriva? ● A more traditional Linux distribution - controlled by the community, continuing where Mandriva left off after the company behind it went out of business in 2012. Its roots go back to the first Mandrake Linux release in 1998. ● Originally targeting only x86 PCs - Support for additional architectures (aarch64, armv7hnl, RISC-V) added later ● Repositiories contain 17618 packages, built and updated individually, assembled into an installable product with omdv-build-iso or os-image-builder.
    [Show full text]
  • Pinephone User Manual - Quick Start Guide (En)
    PINEPHONE USER MANUAL - QUICK START GUIDE (EN) 1 Package contents ● User Manual - Quick Start Guide (x1)​ ​ ● PinePhone (x1)​ ​ ● USB-C power cable (x1)​ ​ 2 Safety precautions and recycling 2.1 Cautions Before using the device please read this manual carefully. Notes for safe operation: ● The PinePhone should be charged using a 15W (5V 3A) USB-PD power adapter. Charging at a higher voltage may result in damage to the device. ● The PinePhone will only operate when its internal temperature is between 5°C and 65°C. It should never be operated with an external temperature lower than -20°C or higher than 40°C. ● Do not puncture, disassemble, strike or squeeze the battery. Old batteries need to be disposed of ​ ​ in accordance with local regulations (see ​section 2.2)​. ​ ​ ● Do not expose the device to direct sunlight, water or high levels of humidity. ● In the event of overheating, power off the PinePhone and let it cool for 15 minutes. ● Comply with local regulation pertaining to using mobile devices. This extends to and includes use of the device in public spaces, when operating motor vehicles and heavy machinery. 2.2 Recycling of components and batteries Recycling any PinePhone components should be done according to local regulation. This may require you to dispose of the phone or its parts at a local recycling centre or at a designated container. Please consult local legislation for details. Batteries should never, under any circumstances, be disposed of with general household waste. The end user is legally obliged to return used batteries. Batteries can be returned to us to be disposed of.
    [Show full text]
  • 最近の事と来年の目標 in 2020 1 Recently My Activity and the Next Year’S Goal in 2020
    最近の事と来年の目標 in 2020 1 Recently my activity and the next year’s goal in 2020 FZ-G1+Lubuntu20.04 in128GB USB memory １、 自己紹介 Self introduction ２、Recently my activities ３、Non eMMC Windows Tablet? ４、Install Linux in The third Mobile OSs 5、Install Linux in UMPC ６、Install Linux in Macbook,PowerbookG4 ７、USB Wifi and USB HDMI capture 8、Recently my activity 詳しい話はSlideshareで公開中 This Presentation: @kapper1224 Slideshare & PDF files publication of my HP http://kapper1224.sakura.ne.jp 鹿児島らぐ 2020年12月 Gadget Hacking 2020 年12月26日 14:00~ User Group Place: Online Speaker：Kapper 自己紹介 Self Introduction 2 ● My name: Kapper ● Twitter account：＠kapper1224 ● HP：http://kapper1224.sakura.ne.jp ● Slideshare: http://www.slideshare.net/kapper1224 ● Mastodon:https://pawoo.net/@kapper1224/ ● Facebook：https://www.facebook.com/kapper1224/ ● My Hobby：Linux、*BSD、and Mobile Devices ● My favorite words：The records are the more important than the experiment. ● Test Model：Netwalker(PC-Z1,T1)、Nokia N900、DynabookAZ、RaspberryPi Nexus7(2012、2013)、Nexus5、Chromebook、Fx0（FirefoxOS）、 無敵CD-920、CD-928,GPD-WIN、GPD-Pocket、Macbook NANOTE、Windows Tablet、SailfishOS、UBPorts、postmarketOS ● Recent my Activity： Hacking Linux on Windows10 Tablet (Intel Atom) and Android Smartphone. Hacking NetBSD and OpenBSD on UEFI and Windows Tablet. I have been exhibiting in NT Nagoya, NT Kanazawa, Oogaki Mini MakerFaire. I have over 200 Windows Tablet and 120 ARM Android, and test it now. 後、最近小説家になろうで異世界で製造業と産業革命の小説書いていますなう。 Recently my activities 3 NetBSD、OpenBSD、FreeBSD SailfishOS on UBPorts on Nexus5 MaruOS Some Linux on Windows Tablet Nexus5 Nexus7 2013 on Nexus5X postmarketOS on Install Linux and *BSD Nexus5, Nexus7 2012 In USB memory Activities on NT, MakerFaire,Taiwan 異世界転生小説を書いています。 4 This is my novels 「The otherworldy 」 ● 中世〜近世で製造業で産業革命するネタ。 It is 「Industrial Revolutions」 in ｔhe early modern period in my novels.
    [Show full text]
  • Genode Operating System Framework Platforms
    GENODE Operating System Framework 21.05 Platforms Norman Feske Contents Contents 1 Introduction3 2 Porting Genode to a new SoC4 2.1 Preparatory steps................................9 2.1.1 Licensing considerations........................9 2.1.2 Selecting a suitable SoC........................ 10 2.1.3 Start by taking the known-good path................ 11 2.1.4 Setting up an efficient development workflow........... 12 2.2 Getting acquainted with the target platform................. 14 2.2.1 Getting a first impression....................... 15 2.2.2 The U-Boot boot loader........................ 19 2.3 Bare-metal serial output............................ 24 2.4 Kernel skeleton................................. 34 2.4.1 A tour through the code base..................... 34 2.4.2 A new home for the board support.................. 41 2.4.3 Getting to grips using meaningful numbers............. 48 2.4.4 A first life sign of the kernel...................... 55 2.5 Low-level debugging.............................. 57 2.5.1 Option 1: Walking the source code.................. 58 2.5.2 Option 2: One step of ground truth at a time............ 60 2.5.3 Option 3: Backtraces.......................... 62 2.6 Excursion to the user land........................... 64 2.7 Device access from the user level....................... 73 2.7.1 Using a GPIO pin for sensing a digital signal............ 74 2.7.2 Driving an LED via a GPIO pin.................... 81 2.7.3 Responding to device interrupts................... 84 2.8 One Platform driver to rule them all..................... 90 2.8.1 Platform driver............................. 90 2.8.2 Session interfaces for accessing pins................. 95 2.8.3 PIO device driver............................ 96 2.8.4 Dynamic configuration testing...................
    [Show full text]
  • Digital Forensics Analysis of Ubuntu Touch on Pinephone
    electronics Article Digital Forensics Analysis of Ubuntu Touch on PinePhone Yansi Keim *,† , Yung Han Yoon *,† and Umit Karabiyik * Department of Computer and Information Technology, Purdue University, West Lafayette, IN 47907, USA * Correspondence: [email protected] (Y.K.); [email protected] (Y.H.Y.); [email protected] (U.K.) † These authors contributed equally to this work. Abstract: New smartphones made by small companies enter the technology market everyday. These new devices introduce new challenges for mobile forensic investigators as these devices end up becoming pertinent evidence during an investigation. One such device is the PinePhone from Pine Microsystems (Pine64). These new devices are sometimes also shipped with OSes that are developed by open source communities and are otherwise never seen by investigators. Ubuntu Touch is one of these OSes and is currently being developed for deployment on the PinePhone. There is little research behind both the device and OS on what methodology an investigator should follow to reliably and accurately extract data. This results in potentially flawed methodologies being used before any testing can occur and contributes to the backlog of devices that need to be processed. Therefore, in this paper, the first forensic analysis of the PinePhone device with Ubuntu Touch OS is performed using Autopsy, an open source tool, to establish a framework that can be used to examine and analyze devices running the Ubuntu Touch OS. The findings include analysis of artifacts that could impact user privacy and data security, organization structure of file storage, app storage, OS, etc. Moreover, locations within the device that stores call logs, SMS messages, images, and videos are reported.
    [Show full text]
  • Pinephone User Manual - Quick Start Guide
    PINEPHONE USER MANUAL - QUICK START GUIDE 1 Packaging contents 2 2 Safety cautions and recycling 2 2.1 Cautions 2 2.2 Recycling of components and batteries 2 3 Getting started 3 3.1 Back case removal 3 3.2 Initial setup 3 3.2 Privacy switches and pogo pins 3 3.3 Operating the PinePhone 4 4 Operating systems 4 5 Hardware 4 5.1 External component description 4 5.2 Device hardware specifications 5 5.3 Troubleshooting common issues 5 6 Regulatory compliance 5 7 Documentation and contact information 5 2 1 Packaging contents ● User Manual - Quick Start Guide (x1) ​ ​ ● PinePhone (x1) ​ ​ ● USB-C power cable (x1) ​ ​ 2 Safety cautions and recycling 2.1 Cautions Before using the device please read this manual carefully. Operational variables and cautions: ● The PinePhone should be charged using a 15W (5V 3A) USB-PD power adapter. Charging at a higher voltage may result in damage to the device. ● The PinePhone will only operate when its internal temperature is between 5*C and 65*C. It should never be operated with an external temperature lower than -20*C or higher than 40*C. ● Do not puncture, disassemble, strike or squeeze the battery. Old batteries need to be disposed of ​ ​ in accordance with local regulations (see section 2.2). ​ ​ ​ ​ ● Do not expose the device to direct sunlight, water or high density moisture. ● In the event of overheating, power off the PinePhone and let it cool for 15 minutes. ● Comply with local regulation pertaining to using mobile devices. This extends to and includes use of the device in public spaces, when operating motor vehicles and heavy machinery.
    [Show full text]
  • Christopher Obbard Email: [email protected] Twitter: @Obbardc
    Creating Debian-Based Embedded Systems in the Cloud using Debos Christopher Obbard email: [email protected] twitter: @obbardc Open First ● Engineer at Collabora About ● Working on... me – Custom distros for cloud, embedded and PC – Continuous integration – Packaging – OTA upgrades – Tooling to make life easier – Learning Rust! 2 Overview ● Why use Debian as a base? ● Internal design decisions ● How to use Debos (warning: YAML) ● Future plans ● Q&A 3 What is a GNU/Linux distro? ● A collection of software packages ● But also a collection of like-minded developers ● Each distribution has different common goals ● Some goals may be financial, others social ● Debian/Ubuntu uses dpkg/apt ● Red Hat/Fedora uses rpm/yum ● ...everyone has their own preference 4 Why create your own distro? ● Hardware dev kits are supplied with general- purpose distro for evaluatation ● Cloud images ● Lots of bloat, outdated/insecure packages, incompatibilities ● Your own distro would be nice ● A distro is a lot of work to maintain! ● No need to reinvent the wheel: base on a proven technology... 5 Yocto & Buildroot ● Usually for only embedded platforms ● Creates totally custom distribution, can become a maintainance nightmare ● All packages are compiled on your machine ● High learning curve ● Why make things hard... 6 Why use Debian as a base? ● Traditionally seen as a desktop OS... recent years effort has gone into enabling embedded targets ● Released in 1993, widely used (DistroWatch top 10) ● 1,000s of volunteers shape Debian, all following the DFSG & social
    [Show full text]
  • Xinxinli Blue Curves
    Pine64: Synapse on a SBC Cluster Matthew Petry @fire219:matrix.org (or @fire219:pine64.org) Agenda ● The Two Sides of Pine64 ● The RockPro64 Cluster ● Synapse on the Cluster? The Two Sides of Pine64 (how to make FOSS-friendly devices) Pine64 ● So what is it? ● According to Wikipedia: ● I guess that’s not really wrong, but there’s a bit more to it... Pine64 Hardware ● Do one thing and do it well: Make FOSS-friendly ARM hardware at lowest possible cost Pine A64 Pinebook Pro PinePhone Pine64, a bit more in depth ● Rather unusual: zero employees! ● Everyone within the organization is either a contractor, or volunteer. Two distinct entities: ● Business: Pine Store Ltd. (Manufacturing, Logistics, Sales, Official Support) ● Community: Pine64 (Main website, forum, wiki, chat rooms, social media) It takes two to tango ● Hardware is nice and all, but it’s not much good without the software to run on it! ● Most people watching this probably agree: Hardware businesses and FOSS usually don’t mix well – Official firmware often full of blobs, undecipherable without access to NDA-gated documentation Separation of Responsibilities ● The solution is rather simple: have the community handle software development! ● In short: – Business → Pine Store Ltd. → Hardware – Community → Pine64 → Software ● The two sides run independently, but work together to make a complete experience. Here’s a couple more benefits... Community Software is Diverse Software ● As an example, the PinePhone has firmware images available spanning several Linux distributions (PostmarketOS,
    [Show full text]
  • Ubports Documentation Marius Gripsgard
    UBports Documentation Marius Gripsgard 23 Eyl 2021 Hakkında 1 Başlangıç 3 2 Süreçler 5 3 Install Ubuntu Touch 11 4 Daily use 15 5 Advanced use 27 6 Contributing to UBports 35 7 Uyguluma geliştime 47 8 Human interface guidelines 89 9 System software development 125 10 Introduction 145 11 Building and booting 153 12 Configuring, testing and fixing 169 13 Finalizing the port 181 i ii UBports Documentation UBports projesinin resmi dökümanlarına hoş geldiniz! UBports cep telefonu işletim sistemi olan Ubuntu Touch’u geliştiriyor. Ubuntu Touch, kullanım kolaylığı, mahremiyet ve yakınsama üzerine odaklanmış bir mobil işletim sistemidir. On this website you find guides to install Ubuntu Touch on your mobile phone, use Ubuntu Touch, develop Ubuntu Touch apps, port Ubuntu Touch to an Android handset and learn more about system components. If this is your first time here, please consider reading our introduction. Bu belgelerin geliştirilmesine yardımcı olmak istiyorsanız, Dokümantasyon katkı sayfası iyi bir başlangıç olacaktır. Bu dokümanları aşağıdaki dillerde görüntüleyebilirsiniz: • English • Català • Français • Deutsch • Italiano • Română • • Türkçe • Español • Simplified Chinese Hakkında 1 UBports Documentation 2 Hakkında BÖLÜM 1 Başlangıç Our goal is to create a copylefted libre mobile operating system. One you can use, study, change and share; with all. 1.1 UBports Hakkında The project was founded by Marius Gripsgard in 2015 and in its infancy a place where developers could share ideas and educate each other in hopes of bringing the Ubuntu Touch platform to more mobile devices. After Canonical suddenly announced plans to terminate support for Ubuntu Touch in April of 2017, UBports and its sister projects began work on the source code; maintaining and expanding its possibilities for the future.
    [Show full text]
  • 2021 Year of the Linux Phone? by Aaron Grothe & Raul Ochoa
    2021 Year of the Linux Phone? By Aaron Grothe & Raul Ochoa August 03, 2021 2021 Year of the Linux Phone? A common joke amongst Linux people is that XXXX is the year of the Linux Desktop. So we’ve decided to lift that for our presentation. Options There are 3 major Linux phones currently available Pine Phone Purism Librem5 F(x)tec Pro1-X smartphone Aquarius BQ (discontinued) Ubuntu Touch can also run on a bunch of phones as well: Nexus, Oneplus, Meizu, Pixel 3a - check their website We both own Pine Phones as we’re poor :-( Quick Pine Phone overview There are two major versions of the Pinephone available Base version 2gb ram/16gb storage - $149 Convergence edition 3gb ram/32gb storage/usb-c hub - $199 They are now up to the Beta edition. They have had previous editions: Braveheart, bunch of community editions (UBports, PostmarketOS, Manjaro, KDE, Mobian) - my phone is from the Manjaro edition Used to be only be available in batches, can order now but you might be waiting a while :-( Quick Pine Phone overview Spare parts may be purchased You can upgrade your 2gb/16gb mainboard to a 3gb/32gb mainboard for $105.00 Replacement batteries are $10 LCD panel with touch screen is $35 Other pieces are available (back cover, usb-c side boards, etc..) Quick Pine Phone overview Can turn off hardware via DIP Switches - 6th switch converts headphone into UART serial port Hardware Switches (Quick Aside) If you ever see Snowden in an interview on his phone he will always be wearing his earphones.
    [Show full text]
  • Ubports Documentation
    UBports Documentation Marius Gripsgard Sep 23, 2021 ABOUT 1 Introduction 3 2 Processes 5 3 Install Ubuntu Touch 11 4 Daily use 15 5 Advanced use 27 6 Contributing to UBports 35 7 App development 47 8 Human interface guidelines 87 9 System software development 123 10 Introduction 143 11 Building and booting 149 12 Configuring, testing and fixing 165 13 Finalizing the port 177 i ii UBports Documentation Welcome to the official documentation of the UBports project! UBports develops the mobile phone operating system Ubuntu Touch. Ubuntu Touch is a mobile operating system focused on ease of use, privacy, and convergence. On this website you find guides to install Ubuntu Touch on your mobile phone, use Ubuntu Touch, develop Ubuntu Touch apps, port Ubuntu Touch to an Android handset and learn more about system components. If this is your first time here, please consider reading our introduction. If you want to help improving this documentation, the Documentation contribute page will get you started. You may view this documentation in the following languages: • English • Català • Français • Deutsch • Italiano • Română • • Türkçe • Español • Simplified Chinese ABOUT 1 UBports Documentation 2 ABOUT CHAPTER ONE INTRODUCTION Our goal is to create a copylefted libre mobile operating system. One you can use, study, change and share; with all. 1.1 About UBports The project was founded by Marius Gripsgard in 2015 and in its infancy a place where developers could share ideas and educate each other in hopes of bringing the Ubuntu Touch platform to more mobile devices. After Canonical suddenly announced plans to terminate support for Ubuntu Touch in April of 2017, UBports and its sister projects began work on the source code; maintaining and expanding its possibilities for the future.
    [Show full text]