Fairphone - Technical details, links and Q&A interaction with Fairphone [26 Jul 2014]

What do you think about the Fairphone?

  • Fair? Nothing in life is fair.

    Votes: 0 0.0%

  • Total voters
    53
  • Poll closed .
Search This thread

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
Last edited:

paalsteek

Senior Member
Jul 7, 2010
55
18
My guess would be

GND TXD4
VCC RXD4
TXD1 RXD1

But it's hard to tell from the pictures and use a voltmeter to check at least vcc and gnd
 

chrmhoffmann

Inactive Recognized Developer
Nov 11, 2006
941
3,154
After the teaser, now the ROM. Head over to the fairphone original android development forum and get some kitkat love.

Beware that not all is working (no Bluetooth,video recording, hw video decoding and lots of bugs).

Be sure to make an entire backup first and know how to restore it.

Chris
 

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
Last edited:
  • Like
Reactions: MoreThanADev

_keesj

Senior Member
Mar 4, 2014
62
137
Amsterdam
It seems the kernel source is the same for both FP1 and FP1U (not sure about this)

The kernel *is* the same but it is good to keep in mind that different kernels are needed for the different partition layouts.


FYI: Setting of ro.product.model at runtime is not functional yet. The init.rc does not allow using such sh syntax commands and the replacement that uses a oneshot service also doesn't. After boot cat /proc/gpufreq/gpufreq_var_dump | grep "clk_cfg_0 = 1" does reliably discriminates between the model but not at that point in the boot process.
 

_keesj

Senior Member
Mar 4, 2014
62
137
Amsterdam
different kernels or different ramdisks ?

I described how the MTK partition layout works here https://github.com/keesj/alps-fairphone-gpl/wiki/MTKPartitionLayout . What it boils down to is that a based on an xls file many files are generated that end up in the kernel, bootloader, recovery and flasher. Between the old partition layout and the new one we use less partitions and EBR2 is no longer used but we have ensures=d that the /system partition remains on the same place.

The result of that is that pre and post unified partition the kernels are "mostly" compatible but not in all situation. I expect problems the when swapping the binaries in place like the flasher.

The normal recovery also for example checks for a scatter file inside OTA and compare thems againts a binary version of the partition table.

The differences between 1.6 1G13G and 1.6 FUSE are caused by this change and not different hardware. We use the same kernel and ramdisk for both the models. To keep things simple I would suggest to only support the new unified partition scheme (that will work on both the FP1 and FP1U).
 
  • Like
Reactions: simsalonaut

simsalonaut

Member
Oct 19, 2013
45
64
Heidelberg
Feedback on AOSP 4.2.2 (v2014-08-05)

AOSP user reporting in, thanks for not forgetting about Stock Android!
  • Red camera tint removed, though might have gone a bit too far, as there is a blue halo visible around the center now
  • Battery no longer stuck at 14%. Instead, it now drops instantly from ~12% to zero, and glitches when recharging. Doesn't happen everytime though; is it possible that the system needs a few cycles to recalibrate?
  • EPO: I noticed a few small changes in settings (Update period setting), but with the servers at Mediatek being so unstable, that doesn't really help. This solution by @BlaY0 seems to be the best, but since I am a noob regarding baksmaling, I'd appreciate it if this could be implemented into the next update. How about it, @_keesj? :)
Organizational issue: This thread is getting too long to read - I think it's time to start separate threads for issues like GPS accuracy and so on. What do you guys think?

And last but not least: Over a year since the first post, this subforum is finally dealing with the topics it's meant to deal with: Not just feedback on bugs, but actual ROM development - and that is awesome.
 
Last edited:

_keesj

Senior Member
Mar 4, 2014
62
137
Amsterdam
AOSP user reporting in, thanks for not forgetting about Stock Android!
  • EPO: I noticed a few small changes in settings (Update period setting), but with the servers at Mediatek being so unstable, that doesn't really help. This solution by @BlaY0 seems to be the best, but since I am a noob regarding baksmaling, I'd appreciate it if this could be implemented into the next update. How about it, @_keesj? :)

And last but not least: Over a year since the first post, this subforum is finally dealing with the topics it's meant to deal with: Not just feedback on bugs, but actual ROM development - and that is awesome.

We have confused a few people who accidentally installed AOSP and contacted us because the edge swipe no longer worked. Are many people using Stock Android?
The EPO download will be fixed to the next release but this will be as good as it gets. We are very happy to see ROM development picking up!
 

madde-

Member
Sep 2, 2014
23
3
AOSP user reporting in, thanks for not forgetting about Stock Android!
  • Red camera tint removed, though might have gone a bit too far, as there is a blue halo visible around the center now
  • Battery no longer stuck at 14%. Instead, it now drops instantly from ~12% to zero, and glitches when recharging. Doesn't happen everytime though; is it possible that the system needs a few cycles to recalibrate?
  • EPO: I noticed a few small changes in settings (Update period setting), but with the servers at Mediatek being so unstable, that doesn't really help. This solution by @BlaY0 seems to be the best, but since I am a noob regarding baksmaling, I'd appreciate it if this could be implemented into the next update. How about it, @_keesj? :)
Organizational issue: This thread is getting too long to read - I think it's time to start separate threads for issues like GPS accuracy and so on. What do you guys think?

And last but not least: Over a year since the first post, this subforum is finally dealing with the topics it's meant to deal with: Not just feedback on bugs, but actual ROM development - and that is awesome.

Problem with the battery suddenly dropping from 1X % to zero also occurs with FPOS after update to 1.6 and repartitioning.
 

benkxda

Senior Member
Jan 28, 2012
1,157
3,604
True! Maybe we should move bug reports etc to another thread?

I appreciate to bring up other threads, like bug reporting. And for developing threads it's always better to start a DevDB thread, where you can assign a Q&A thread and you have options to display, like feature requests and bug reports.

Yes, that's what they are for. Also to have a nice overview over everything and being able to help each other (usually the OP must include everything in their post) use the wiki! :) http://forum.xda-developers.com/wiki/Fairphone_Fairphone

The wiki needs some work I think. For example there is another Fairphone out there, means, for the Fairphone 2014 you can remove the "M" from the SoC. Maybe we can push it a bit more? Can you place it in your signature? I included it in the (still very unknown) Fairphone index.
 

Dominik K

New member
Sep 7, 2014
2
1
xda:devcon -> Mediatek contact

Hi,

We will be joining the xda devcon this year. I hope we can get in touch with some of you. I personally hope to get a better understanding of the XDA eco system and I am also looking forwards to talk to some MediaTek people.

See you there!

Good to hear you want to get in contact with Mediatek. Maybe you can get a hint why they're disclosing information about their GSM baseband processor that much. Harald Welte gives in chapter 7 of his phone "anatomy" paper [1] reasonable arguments why there's no need for it.

I wish all of you a good conference and best wishes getting in contact with the Mediatek guys. :)


[1] laforge.gnumonks.org/papers/gsm_phone-anatomy-latest.pdf
 

joemier

Member
Aug 6, 2013
38
214
Amsterdam
www.fairphone.com
Hackathon/think tank next week in The Hague - win a ticket!

Hi,

To those based around the Netherlands (and not going to xda:devcon), there's an exciting event on the beach near The Hague next week: WTHX. It's a 2-day hackathon/think tank on 25 & 26 Sept. More here:
http://wthx.org

"WTHX is part hackathon and part think-tank, bringing together a diverse group of thinkers and makers to address the themes of Peace, Justice and Security"

And for those in the area who can attend - we have a ticket to give away! Reply with a line about why you want to go, and we'll put you in a random drawing for a free ticket. Hope you can attend!


[hopefully this kind of giveaway is in accordance with XDA guidelines?]
 
Last edited:
  • Like
Reactions: _keesj and benkxda

benkxda

Senior Member
Jan 28, 2012
1,157
3,604
Hi,

To those based around the Netherlands (and not going to xda:devcon), there's an exciting event on the beach near The Hague next week: WTHX. It's a 2-day hackathon/think tank on 25 & 26 Sept. More here:
http://wthx.org1

"WTHX is part hackathon and part think-tank, bringing together a diverse group of thinkers and makers to address the themes of Peace, Justice and Security"

And for those in the area who can attend - we have a ticket to give away! Reply with a line about why you want to go, and we'll put you in a random drawing for a free ticket. Hope you can attend!


[hopefully this kind of giveaway is in accordance with XDA guidelines?]

No problems with XDA rules here. :good:
But fix your link, remove the "1". Well, probably all of us know how tho reach the website anyway ;)
 

haiag

Senior Member
Sep 23, 2013
55
32
Is the Fairphone vulnerable though the AOSP browser bug?

Are there plans for a security patch?

Regards
 

Top Liked Posts

  • There are no posts matching your filters.
  • 37
    Fairphone - Technical details, links and Q&A interaction with Fairphone [26 Jul 2014]

    Thread link
    Announcement
    21 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
    Older announcements


    Fairphone - The Technical Details And Links
    The Fairphone - technical details, weblinks and other stuff
    fairphonepics9oedz.png


    First of all - read the story behind the Fairphone to know, why it's fair and what it is all about.



    Official Fairphone website
    Fairphone 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
    Technical specifications
    The FAQs
    Download the Fairphone Press Kit (30-10)
    The Fairphone shop




    More weblinks
    iFixit: 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, software
    Fairphone 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




    Known issues
    1. Serial number: It seems that the serial number is not a valid serial number, but the standard number 0123456789ABCDEF (solution below)

    2. 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)

    3. 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.

    4. 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 Link2SD[/URL. Learn more on the [URL="https://fairphone.zendesk.com/hc/en-us/articles/201154666-How-can-I-see-all-the-different-places-where-information-is-stored-on-my-phone-SD-Card-Internal-Storage-and-Phone-Storage-"]official support page (thanks to haiag)




    Mods, hacks, solutions
    Please keep in mind, that you are using this at your own risk and may void your warranty.

    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*

    This is the place of the sound settings for musics, movies and apps.

    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:

    6)
    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 :p
    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.
    Done :)



    Xposed solutions
    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"
    Reboot
    Done!

    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
    Reboot
    Done!



    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.
    [EDIT: You first need the XPosed framework to install XPrivacy afterwards.]


    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:

    https://github.com/bgcngm/mtk-tools

    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.
    [EDIT: Made link clickable]


    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:
    /etc/permissions/com.google.android.maps.xml
    /system/etc/permissions/com.google.android.maps.xml
    /system/framework/com.google.android.maps.jar
    (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 replies
    First 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 replies
    OSB-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.




    Technical specifications
    SoC: MediaTek MT6589 MT6589m
    CPU: Cortex A7 (ARMv7) 1.2 GHz quad-core
    GPU PowerVR SGX544 @ 286 MHz PowerVR SGX544 @ 156 MHz
    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: MPEG4/H.264:[email protected] MPEG4/H.264:[email protected]
    Video Encode Format: MPEG4/H.263:[email protected] MPEG4/H.263:[email protected] H.264:[email protected]
    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
    External memory: microSDHC up to 32 microSD (compatible SD, SDHC and SDXC types) (up to 64Gb)
    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, downlink cat24 up to 42.2Mbps HSPA downlink cat 14 up to 21.1 Mbps
    LTE -
    NFC -

    FM radio: yes
    Light sensor: yes
    G sensor: yes
    E compass: yes
    Proximity sensor: yes
    GPS: yes
    Glonass -
    Gyroscope: yes

    SAR rating (indication): 0.318 W/Kg 0.329 W/Kg (CE)
    Dimensions & Weight: 123 x 64.5 x 10 mm 126 x 63.5 x 10 mm, 170 g
    Android version: 4.2
    Connector: Micro-USB
    Earphone Jack ¢3.5

    Release date: expected in 3th quarter 2013 December 2013 December 2013 / January 2014




    Screenshots


    Teardown - Cleaning the backside of the camera lens cover

    Opening metal backsided lid.
    img_0318e0skbt.jpg


    Removed battery, SIM card and micro SD card.
    img_0320ek8y47.jpg


    Close-up of the dusty camera lens cover.
    img_0323eefyb2.jpg


    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.

    img_0329eofby6.jpg


    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

    img_0335eiujes.jpg




    Benchmarks

    AnTuTu Benchmark 4.1.4, result: 13179
    shot_2013-12-31_21-314mz73.png
    shot_2013-12-31_21-31cmsj7.png
    shot_2013-12-31_21-316jxzu.png
    shot_2013-12-31_21-3131sid.png


    CF-Bench 1.3, result: 12960 (sorry for the volume slider)
    shot_2013-12-31_21-3656sud.png
    shot_2013-12-31_21-37g7suu.png
    shot_2013-12-31_21-37umx5a.png


    Quadrant Standard Edition 2.1.1, result: 4824
    shot_2013-12-31_21-391jx2i.png




    Fairphone OS Screenshots

    Beginning with a journey through some system setting screens.
    shot_2013-12-31_21-12npsbp.png
    shot_2013-12-31_21-12ctsjt.png
    shot_2013-12-31_21-13adsve.png
    shot_2013-12-31_21-13duspc.png
    shot_2013-12-31_21-135db8v.png
    shot_2013-12-31_21-16x1s9i.png


    Next up some memory screenshots an a switch on/off timer, I think for the automatic on/off scheduler.
    shot_2013-12-31_21-18m4szr.png
    shot_2013-12-31_21-185blxk.png
    shot_2013-12-31_21-19oasak.png
    shot_2013-12-31_21-223ts5h.png





    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.
    shot_2013-12-31_21-408mlyv.png
    shot_2013-12-31_21-4050s8z.png
    shot_2013-12-31_21-50k2ssb.png




    Battery consumption

    screenshot_2014-01-02r2sjc.png
    screenshot_2014-01-029luj7.png





    Videos


    FAIRPHONE UNBOXING HD

    Alternative OS on Fairphone


    Fair Lifestyle - Technology | Euromaxx


    Dragontrail glass

    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
    16
    Hi,

    I am Kees and I have started working for Fairphone at the first of June. As
    Embedded software developer and Open Source addict I spent most of my career
    doing what I like most: writing software and playing with hardware.

    I joined the Fairphone team because I believe that a Fairphone phone deserves
    to be running Open Source software. I will do what I can, certainly in the
    future, to make this happen.

    Currently? Currently I am working on getting the software for the second batch
    ready for production. The new phones are to come with an slightly updated
    software stack and will be using the new unified partition scheme (Using fuse
    to emulate external storage)

    At the same time I am looking at the technical possibilities of upgrading the
    current phones to the new partition scheme (this is where I hope to get some
    technical input form XDA members).

    the xrteamer forum has a nice write-up on the layout changes (I might post the
    link once I have permission to post links on the forum). and their current solution
    (that involves wiping the data). I am currently basing my work on theirs.

    One of the biggest (annoying) changes to user is that the phone will no longer
    provide mass storage functionality unless an external SD-card is inserted. This
    has impact on how a proper backup and recovery can be done (backup using mass
    storage and recovery using MTP?). For the typical Fairphone user I estimate
    that this will be to much hassle and we need to find an alternative solution.

    I was thinking of perhaps requesting the user to temporarily insert an SD-card
    for the update. But for now I am still simply looking at the upgrade (not the
    backup/restore yet) and this involves changing the partition layout while
    upgrading.

    I am not used to using forum's much as I tend to prefer using irc and mailing
    list but I will try to keep you posted and use your minds as much a possible.
    16
    Fairphone OS Linux kernel source code package

    Here's our next step in providing developer resources. Happy to present to XDA: Fairphone OS Linux kernel source code package. Please let us know issues, problems, questions!

    We've put together this package with all our downloads of Fairphone OS and stock Android 4.2.2.

    We're eager to see what you all can do with it. Thanks for your patience as we got it up. Enjoy!
    15
    Hi all,

    There are a lot of different questions and issues building up here on XDA for the Fairphone team. Thanks for bearing with us. I've talked with @benkxda so that he can help me collect all relevant issues for the Fairphone tech team and Kwame software developers. Soon, it seems XDA will have Fairphone sub-forums to make this easier for all of us, too.

    Also, news for you all: We're still planning the software release of Fairphone OS 1.1 over the air very soon. It was expected around today/tomorrow, but still needs some time.



    Best,
    Joe
    FP Community Manager