Announcement21 Jun 2014: Added a 60 days poll. Just for your information, your vote and choice is public.
03 Apr 2014: iFixit released one of their famous teardowns for the Fairphone and Fairphone sells spare parts. BAM!!! Greets and thanks to Miro from iFixit.
23 Mar 2014: Added pictures from opening the device to clean the dusty back side of the photo camera lens.
31 Jan 2014: We have our own Fairphone Forum. That's really grand.
25 Jan 2013: Added two links. First, the unoffical FairPhone Users Forum and Fairphone at XDA Developers Wiki.
19 Jan 2014: Added a lot of links recently. Today I want to point you to a petition to get AOSP Support for MediaTek Devices (thanks to @Donat.Callens)
09 Jan 2014: Hid some larger content to get a better structure in the OP. By clicking the buttons you can recover the content. Added a link to the download section on the official Fairphone website for the "FP1" (indicates that there will be a FP2?).
05 Jan 2014: Added a new section "Apps" due to a new app coming up, Fairphone Launcher by LuLeBe
The Fairphone - technical details, weblinks and other stuff
First of all - read the story behind the Fairphone to know, why it's fair and what it is all about.
Official Fairphone websiteFairphone Spare Parts
Fairphone accessories - Case (black)
Fairphone Tutorial - Getting you started with your Fairphone (video tutorials)
Downloads for the FP1: Repair form, Fariphone OS, Stock Android, source code packages, 3D files (CAD), Graphic Design and user guide
The story behind the Fairphone
Download the Fairphone Press Kit (30-10)
The Fairphone shop
More weblinksiFixit: Fairphone
Requests to Fairphone
Fairphone at XDA Developers Wiki
unoffical FairPhone Users Forum (English forum)
Fairphone Freunde (German forum)
Petition: AOSP Support for MediaTek Devices[/B]
Loco Toys Blog
Fairphone OS on GitHub (incl. FairPhoneHome and FairPhonePeaceOfMind)
Kwamecorp, the company who creates the Fairphone OS
AOSP Support for MediaTek Devices (Petition)
Fairphone on Google+
WeAreFairphone FairPhone Fans Users & Enthusiasts (G+ community)
Fairphone on Vimeo
Fairphone on Twitter
Fairphone on Facebook
Fairphone on Flickr
Articles, reviews, videos, images...[08 Jan 2014] Glückliches Smartphone aus fairem Anbau (golem.de, German)
[03 Jan 2014] Fairphone im Praxis-Test: Smartphone fürs gute Gewissen (Computer Bild, German)
[03 Jan 2014] Kommentar: Das Fairphone ist gut genug (heise online, German)
[Update 3.1.2014; 02 Jan 2014] Fairphone im Kurztest (c't, German)
[03 Jan 2014] Fairphone: Öko-Handy im ersten Eindruck (Computer Bild, German)
Apps, widgets, themes, softwareFairphone Launcher on Google Play by LuLeBe
Peace of Mind+, A fork of Fairphone's app by mudar1488. Find out more on Google Play, GitHub, development website, XDA portal
- Serial number: It seems that the serial number is not a valid serial number, but the standard number 0123456789ABCDEF (solution below)
- Google Maps API: Apps which take advantage of the Google Maps API are currently incompatible with the Fairphone (e.g. DB Navigator, Öffi - Fahrplanauskunft) (solution below)
- Device wiggles: If you touch the device if its laying on a flat surface, it wiggles unacceptably. The reason is the popping out speaker grill on the bottom right and the camera and LED module at the top left, both on the backside.
- 1 GB limit for apps: There is a limit of 1 GB for app installation. Of course, you can move installations to the SD card or use managing apps like [URL="https://play.google.com/store/apps/details?id=com.buak.Link2SD"]Link2SD[/URL. Learn more on the official support page (thanks to haiag)
Mods, hacks, solutions
Power measurements by globuli (original post)
I finally got around to do more extensive power measurements (video with more detailed info to follow).
Everything is done with the display (when on) on lowest brightness, I have not looked into the effect of brightness on the consumption, hopefully next week. Also: the measuring equipment is self-built, so don't bet your money on my findings. The current was measured in 10 ms steps, then send through a rolling average. In theory anything could happen in between the 10 ms, and the consumption pattern suggests very short bursts of current. In brackets the time to live, if the battery delivers exactly 2000mAh
Display off, nothing to do in the background: basically below our precision, somewhere at 2mA (1000h), but I mean nothing to do
Display on, nothing to do: 85 mA (23.5h)
Video playback: ~160mA (12.5h)
Incoming call 3G (with MP3 ringtone, vibrator, the works): > 410 mA (<4.8h), sorry, the measurement equipment clipped at 430mA
Talking on 3G: 230 mA (8.7h)
Incoming call 2G: (MP3, vibrator): >370 mA (5.4h), again, clipping involved, but clearly less than 3G
Talking on 2G: 140 mA (14.3h)
With Z-Device-Test I tried other components as well, one interesting thing was that the flashlight apparently can only be switched on when the main camera module is active as well. BTW: the changing of the advertisement on the bottom of Z-Device Test costs ~30mA.
Main camera on (with picture in the display): 235mA (8.5h)
Front camera on (with picture in the display): 195mA (10.2h)
Vibrator: ~60 mA
Flashlight: ~50 mA
GPS costs next to nothing, when trying different applications, GPS on or off seemingly made a difference of ~10mA, all power measurements here mainly showed costs for drawing pictures. Bluetooth similar, as long as the component is only on, but no pairing or other activity happens, next to nothing.
Heise wrote in their short test that in their measurements they assumed 7.1 hours of video playback, which would result to 281 mA. But at least with XVID and MP4 I could not make the Fairphone take more then 180 mA peak. No idea what the reason for that is, but as they explained, they emptied the battery to half it's capacity, but who knows how they deemed this "half". And our equipment surely is not off by 100 mA.
Lowering the volume by MoreThanADev (original post)
I agree with you the speaker is too loud by default.
Here is the way to configure it without installing apps.
1) Enter Mediateck EngineerMode by calling *#*#3646633#*#* /!\ you can mess up your conf, be carefull not to randomly click on every button
2) Swipe to the right to Hardware Testing
3) Enter submenu Audio
4) Select LoudSpeaker Mode
5) in Type list, change Ring with Media
*Here i try to explain (with my poor english, and my poor explaining skills) how to adjust the sounds setting that best fits you, skip to 6) for a no brain guide*
On the page you have a field Level which enables you to pick levels from 0 to 6
and a field Value where you can put a number.
Levels corresponds to a fillness of the sound bar, so with default configuration, almost empty sound barre correspond to the level 0 and to the lowest sound of your phone.
If you want to change the sound volume for the almost empty sound bar, select Level 0 and change number in the field value (lower number => lower sound)
If you want to change the sound volume for bar filled at 1/6th change the value for Level 1 etc
The value I putted there were:
a)Select Level 0 and put 80 in Value field then press the Set button on the Value field line.
b)Select Level 1 and put 110 in Value field then press the Set button on the Value field line.
c)Select Level 2 and put 130 in Value field then press the Set button on the Value field line.
d)Select Level 3 and put 150 in Value field then press the Set button on the Value field line.
e)Select Level 4 and put 170 in Value field then press the Set button on the Value field line.
f)Select Level 5 and put 200 in Value field then press the Set button on the Value field line.
g)Select Level 6 and put 240 in Value field then press the Set button on the Value field line.
7) Test your sound, if it fits you, go to 8, else read the text you skipped after 5
8) Restart (might not be necessary but, who knows ), or if you don't restart makes sur to close the EngineerMode so you won't mess up with your conf by accident.
That seemed to work whithout breaking anythings with my phone, and hopefully it will with yours
Gesture typing - Official Google Keyboard for the Fairphone
Gesture typing aka swipe is not available on your Fairphone keyboard? No problem!
As we figured out, the Google Keyboard from Google Play is not compatible with the Fairphone. But you can install the apk directly from the thread [APK] Official Google Keyboard.
After the download, follow following instruction:
1. Go to Settings -> Security -> activate Unknown sources
2. Scroll down the notification drawer and tap on the icon of the downloaded Google Keyboard apk
3. Go to Settings -> Language & input -> activate the Google Keyboard.
The Xposed framework is known for its very good customization abilities.
One of the famous modules is GravityBox. With it we were able to solve some issues.
Volume slider interrupts system
Sometimes changing the volume interrupts the system, because the volume slider won't disappear. The system is inoperable. Switching display on/off can help as well as a system reboot. Use the extended volume sliders from GravityBox.
Unused SIM slot notification
If you have only inserted one SIM, you get an icon in the status bar. You can hide this notification with GravityBox.
How to install GravityBox
First you have to download and install Xposed. In this app you can download GravityBox.
First: Download the Xposed Installer APK and install it
Launch the Xposed Installer, go to the "Framework" section and click on "Install/Update"
Second: Download and install GravityBox, therefore open Xposed, go to download section and select GravityBox.
After that, enable the module by checking the checkbox in the modules section
Serial number by fjxda (original post)
I saw that XPrivacy can fake the serial number for the apps you select (and you can even select that ONLY the serial is faked by Xprivacy, and ONLY for one app, so it has no side effects. And you can input your real serial number into XPrivacy if you want!).
With the correct serial number faked by Xprivacy, my favourite navigation app does now work fine.
The open(ed) bootloader by fjxda (original post)
The bootloader is open.
I downloaded, modified an uploaded the boot.img and the phone did still boot, so it doesn't verify any signature of the boot image.
Hint: boot-image starts at /dev/bootimg
/dev/bootimg seems to point to a start address of internal memory but you can access the whole memory through it. So if you write something into, you can brick your whole phone and delete everything - probably.
The boot image is probably at most 0x600000 bytes large, afterwards recovery partition starts.
Command to retrieve the boot img:
dd if=/dev/boot of=/sdcard/boot.img bs=6291456 count=1
Tools to modifiy:
After repacking, the boot.img will be smaller (verify!).
Then you can copy with dd if=/sdcard/boot1.img of=/dev/boot.img - on your own risk, better wait till official firmware image becomes available.
DON'T use cat on /dev/bootimg! Use dd.
Don't write more than 6291456 bytes or your recovery will be lost.
May be good Idea to backup recovery with
dd if=/dev/recovery of=/sdcard/recovery.img bs=6291456 count=1
If using mtk-tools - use a unix filesystem to extract into so that executed-rights within the initramfs of the boot-img don't get lost.
Google Maps API issues by MrJekyll (original post, this solution was verified as working by several XDA members)
0. (install terminal emulator)
EDIT: as imparted by Nicholas Evans in the Fairphone support forum, BusyBox is not necessary for this as the used programs are provided by Android itself.
1. get superuser rights (Start terminal emulator, type "su" and press enter, grant root priveledges if asked for)
2. remount your system-partition with write access (type "mount -o rw,remount /system" and enter)
3. change the permissions for the following files to rw-r-r:
(to do so, type "chmod 644 $file" and enter, replace $file with the filename and path as written above, do this for all three files)
4. remount system-partition read only (type "mount -o ro,remount /system" and enter)
5. close terminalemulator, delete appdata and updates for Google playstore and reboot. For me that was all.
Please have these instructions rewied by an experienced user/developer before using them, I will/can not guarantee for anything
Q&A discussion - You ask, Kwamecorp repliesFirst Fairphone OS version is based on Android 4.2.2
The widgets of Fairphone OS will be released as open source, they will be uninstallable and the system comes without bloatware. (I am really impressed!)
Q&A discussion - You ask, Fairphone repliesOSB-OTG is working with the Fairphone
Fairphone firmware updates possibly available OTA, updates will be available as long as possible, also stock Android available on launch. No tablet planned right now, currently focusing on the smartphone only. First prototypes not to be expected before October.
Front side Dragontrail Glass, backside cover to reveal the battery/SIM cards is silver steel, the rest made of plastic.
The navigation bar ("navbar") has capacitive buttons.
CPU: Cortex A7 (ARMv7) 1.2 GHz quad-core
Radios: 3G, HSPA+, TD-SCDMA, GSM850/900/1800/1900MHZ, WCDMA 900/2100MHz, no CDMA
WLAN: WIFI 2.4GHz 802.11b/g/n
Bluetooth: v2.1 + EDR / v3.0 + HS (802.11 AMP) / v4.0 LE
GPRS Class GPRS Class 12
EDGE Class Multi-Slot Class 12
Display: 960 × 540 pixel, 4,3" (qHD) LCD, 24 bit 16 Mio. colors, 256 ppi, capacitive protected by Dragontrail Glass
Camera: 8 megapixels, AF (stabilization + image sensor) 3264 × 2448 pixel, photo LED, multishot
Front facing camera: 1,3 megapixels
Video: 1280 x 720 pixel
Video Decode Format:
Video Encode Format:
Audio Decode Format: WAV,MP3,MP2,AAC,AMR-NB,AMR-WB,MIDI,Vorbis,APE,AAC-plus v1,Aac-plus v2,FLAC,WMA
Audio Encode Format: AMR-NB,AMR-WB,AAC,OGG
Dual-SIM: yes, (Mini-SIM) Dual Stand-by SIM1: 2G SIM2: 3G, Standard format SIM (ID-000 format)
Internal memory 16 GByte
RAM: 1 GByte
Battery: Li-Ion 2000 mAh, replaceable
HSDPA: 7,2 MBit/s
HSUPA: 5,7 MBit/s
UMTS: HSPA uplink cat 7 up to 11.5Mbps,
FM radio: yes
Light sensor: yes
G sensor: yes
E compass: yes
Proximity sensor: yes
SAR rating (indication):
Dimensions & Weight:
Android version: 4.2
Earphone Jack ￠3.5
Release date: expected in
Teardown - Cleaning the backside of the camera lens cover
Opening metal backsided lid.
Removed battery, SIM card and micro SD card.
Close-up of the dusty camera lens cover.
After removing five screws, you can remove the frame which covers the circuit boards.
Removing the frame was a difficult and hard work, as it is clipped very tough and tight. If you have the right tools, don't be afraid, but still be careful.
Picture from inside after cleaning. The square black rubber around the lens cover does not protect well. It probably is just too thin.
Other than that, the whole circuit boards and all electronic components where dusty on the top of the device. Possible reasons: USB port, earphone jack, power button
AnTuTu Benchmark 4.1.4, result: 13179
CF-Bench 1.3, result: 12960 (sorry for the volume slider)
Quadrant Standard Edition 2.1.1, result: 4824
Fairphone OS Screenshots
Beginning with a journey through some system setting screens.
Next up some memory screenshots an a switch on/off timer, I think for the automatic on/off scheduler.
System tool and Google Maps API
CPU-Z and an app for public transportation like DB Navigator. I did not find DB Navigator in the Store, but Öffi - Fahrplanauskunft was found on the Fairphone. As this app is similar to DB Navigator, it's not compatible due to recent mentioned problems with the Google Maps API. There is already a detailed solution for the Google Maps API issues by @MrJekyll.
FAIRPHONE UNBOXING HD
Alternative OS on Fairphone
Fair Lifestyle - Technology | Euromaxx
Manufacturer: Asahi Glass Co.
Dragontrail details (PDF)
Information on Wikipedia
Incredible aMazing Dragontrail glass screen test for xiaomi m2 smartphone from ibuygou
Dragontrail VS the All-Stars