[ROM][MTK][STOCK] fairphone FP1 kitkat 4.4.4

Search This thread
By:
Advanced…
C

chrmhoffmann

Inactive Recognized Developer
Nov 11, 2006
1,007
3,205
This is Android 4.4.4 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).

It includes various security fixes on top of 4.4.4 - but most likely not all. Major security hole detectors are green now (VTS, Bluebox, Zimperium).

NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!

Without much ado...

To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/filedl/devs...mhoffmann/fp1-kk-stock/fp1-kk444-CH-0.9.7.zip MD5sum: 9140c93ff8f2b8327fdd330d2448c16f
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711

Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
- CTS is complaining about some issues. https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
- As this is a merge of 4.4.4 into the MTK stuff, watch out for more bugs than the previous release. Not merged: the new 4.4.4 dialer screen (we stick with 4.4.2 dialer as the modifications are too heavy), chromium does not support wml anymore (who cares?).
- You most likely need to wipe to install this when coming from the previous KK version to 4.4.4. Email app e.g. seems to crash without.
- Playstore version of Google Authenticator does not work (see https://github.com/google/google-authenticator-android/pull/4). Use the OSS version https://github.com/google/google-authenticator-android/releases - this is not specific to FP1 but seems an MTK issue.
- A dirty update (without wipe) from 0.8 on an encrypted device seems to reboot once during the "Android is upgrading" dialog
- Sometimes the lower part of the homescreen launcher seems to lose transparency.

Changelog fp1-kk444-CH-0.9.7 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAY-2016 (https://source.android.com/security/bulletin/2016-05-01.html)
- Kernel CVEs including the mediatek wifi ones from https://source.android.com/security/advisory/2016-03-18.html, CVE-2016-2549, CVE-2016-2847, CVE-2016-2547, CVE-2016-2546, CVE-2016-2545, CVE-2016-2384

Changelog fp1-kk444-CH-0.9.6 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 2-APR-2016 (https://source.android.com/security/bulletin/2016-04-02.html)
- Kernel CVEs including the one from https://source.android.com/security/advisory/2016-03-18.html, CVE-2015-7550, CVE-2016-0774, CVE-2016-0821, CVE-2016-0723.

Changelog fp1-kk444-CH-0.9.5 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAR-2016 (https://source.android.com/security/bulletin/2016-03-01.html)
(incl. the kernel fixes that Google only publishes for Google One / Sprout - ported to MT6589)

Changelog fp1-kk444-CH-0.9.4 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-FEB-2016 (http://source.android.com/security/b...016-02-01.html)
- Kernel CVE CVE-2015-8785

Changelog fp1-kk444-CH-0.9.3:
- Android Security Updates from Google bulletin 1-JAN-2015 (http://source.android.com/security/bulletin/2016-01-01.html)
- Some kernel CVEs (CVE2015-8543, CVE2015-8575, CVE2015-7509)
- Attempt to fix German's E-PLUS on O2 roaming

Changelog fp1-kk444-CH-0.9.2:
- Fix that you can now call funny numbers like *143# without phone application crash
- Fix to be able to add contacts to SIM card

Changelog fp1-kk444-CH-0.9.1:
- several kernel CVEs (CVE-2015-5697, CVE-2015-8539, CVE-2015-8215, and a few more without CVE yet)
- the december 1st security advisory bulletin skia issue introduced in 0.9.0 - aka as the dilbert bug - is fixed now

Changelog fp1-kk444-CH-0.9:
- android security bulletin https://source.android.com/security/bulletin/2015-12-01.html
- also update gapps if you install them: http://opengapps.org/?api=4.4&variant=nano

Changelog fp1-kk444-CH-0.8:
- google location providers are used now, which should enable network location provider (in case you installed google apps).

Changelog fp1-kk444-CH-0.7:
- National roaming should be fixed (at least as good as CM). If you still have issue with national roaming, send me your mmc/mmn data.
- Use original FP1 lens parameters for fm50af lens - does this improve the auto/manual focus issues that some people reported compared to stock FP jellybean?
- Attempt to fix the problem where sometimes the scrollbar and recents screen stopped working and screen locked despite having higher screen timeouts.
- Full CTS result: https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml

Changelog fp1-kk444-CH-0.5:
- SELinux enforcing
- Camera app now shows all resolutions
- adb now requires acceptance of adb key

Changelog fp1-kk444-CH-0.4:
- ro.adb.secure set
- browser default pages revisited (removed wrong thumbnail).
- removed MTK root CAs that are not in AOSP
- fixed remaining security false-positives in VTS and Bluebox Trustable - all green now
- USB default setting should be MTP now

Changelog fp1-kk444-CH-0.3:
- More CVE fixes (e.g CVE-2015-3845). VTS and Bluebox Trustable are almost green. For some reasons they still think "Stagefright" is not fixed. Zimperium nevertheless shows all stagefright OK. Edit: found out why. It's false positive as MTK reports errors in MPEG4Extractor differently than stock.

Changelog fp1-kk444-CH-0.2:
- Netflix issue fixed with new blob from E3
- Some CTS issues fixed
- More security fixes CVE-2014-7911

Changelog fp1-kk444-CH-0.1:
- Upgraded to 4.4.4_r2.0.1: Yay! That was an insane amount of work. The following "shortcuts" were taken:
-- Chromium sources taken from AOSP - MTK added wml but it was too much work to merge this back in
-- Email app sources taken from aosp - MTK customized something there esp. exchange sync, is that really giving someone problems?
-- Dialer app taken from MTK without 4.4.4 updates - that stuff is too heavily customized also for dual sim, and 4.4.4 revamped the UI, so this was just too much work for now.
- Latest security fixes up to November 2015. Security fixes also for wpa_supplicant_8 (thanks to Michael Bestas for collecting them for CM)
- Kernel sec fixes
- FP1 power profile xml (does this actually change anything)

As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes

Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
 

Attachments

  • Screenshot_fp1_444.png
    Screenshot_fp1_444.png
    101.8 KB · Views: 2,345
Last edited:
  • Like
Reactions: raunz, linux26.android, kossaflo and 24 others
J

jogri

Member
May 14, 2015
28
5
54
chrmhoffmann said:
This is Android 4.4.2 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).

It includes various security fixes on top of 4.4.2 - but most likely not all.

NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!

Without much ado...

To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/devs/chrmhoffmann/fp1-kk-stock
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711

Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?

As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes

Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
Click to expand...
Click to collapse
so far it works on my fp1 (without U), no Problems with my IMEI-Numbers. Thank you very very much, great!
 
Z

z3ntu

Member
May 2, 2015
26
5
Just flashed it and it works! Thank you so much! :) (although instructions how to create such a rom would be nice for me ;) )
EDIT: some answers to your question:

I am using the FP1u.
No problems with my IMEI.
Other major issues: none noticed, and this actually fixed the transparency bug in the Play Store :D
Missing security patches: Stagefright CVE-2015-6602 is not fixed.

Thank you very much!
 
Last edited:
  • Like
Reactions: chrmhoffmann
F

fredflegel

Member
Apr 15, 2013
27
30
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
 
C

ccxxx

Senior Member
Mar 4, 2013
89
33
fredflegel said:
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
Click to expand...
Click to collapse
There's an old thread about it: http://xdaforums.com/showthread.php?t=2615613
So in this case:
Code: 
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/recovery
And because I can never remember if it's volume up or down when powering on: "Hold the Volume Up button, while at the same time press and hold the Power button. Hold these two buttons at the same time for about 10 seconds until the screen changes."
Then install from sideload, etc. and
Code: 
adb sideload fp1-kk-stock-0.1.zip
Takes quite a while to update. I did NOT disable rom recovery, I don't think this one reverts the recovery, right?

aaaand
UN4nseP.png

Sound and bluetooth seem to work fine, didn't test more so far.

Edit: By the way, are you going to do a Lollipop rom? That would be even more awesome than this. Meanwhile: Good job for raising the FP1 software to the minimum requirements for today. :)
 
Last edited:
  • Like
Reactions: derhannes and fredflegel
F

fredflegel

Member
Apr 15, 2013
27
30
Great Work! Thanks alot!

I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
 
Z

z3ntu

Member
May 2, 2015
26
5
fredflegel said:
Great Work! Thanks alot!

I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
Click to expand...
Click to collapse

You can enable "National data roaming" with GravityBox, which you can install via the Xposed installer. Helped in Austria with bob (and A1)
 
  • Like
Reactions: fredflegel
C

ccxxx

Senior Member
Mar 4, 2013
89
33
You forgot to mount the "external" storage:
Code: 
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0

Workaround for getting the correct one for now:
Code: 
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8  /storage/emulated
But there are still symlinks to /storage/emulated/legacy.

So that needs some kind of fix up.
 
Last edited:
C

chrmhoffmann

Inactive Recognized Developer
Nov 11, 2006
1,007
3,205
ccxxx said:
You forgot to mount the "external" storage:
Code: 
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0

Workaround for getting the correct one for now:
Code: 
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8  /storage/emulated
But there are still symlinks to /storage/emulated/legacy.

So that needs some kind of fix up.
Click to expand...
Click to collapse

I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.

Chris
 
  • Like
Reactions: ccxxx
C

chrmhoffmann

Inactive Recognized Developer
Nov 11, 2006
1,007
3,205
Upgrade to 4.4.4. available

See OP. Please test this. It's an update to android 4.4.4 and lots of additional security fixes.

Oh, and yeah, I recommend to wipe. Email (e.g. and maybe others) will crash without.

Chris
 
Last edited:
  • Like
Reactions: Quallenauge
C

ccxxx

Senior Member
Mar 4, 2013
89
33
It wasn't obvious, how to do that, so I downloaded the "Storage Upgrader 1.8.7 * (~200MB)" from https://fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions-
It doesn't update the partitions when flashing, it does so on the first boot. It also overwrites the recovery.

After that I installed the 4.4.4 image and it boot loops: https://gist.github.com/ChristophHaag/64da8b31533d2c562c92

edit: And so does the 4.4.2 image that has worked before.

*sigh*

edit 2: Formatted a few partitions and tried again - now 4.4.4 works.
 
Last edited:
  • Like
Reactions: chrmhoffmann
C

chrmhoffmann

Inactive Recognized Developer
Nov 11, 2006
1,007
3,205
0.2 released.

It should fix Netflix (will confirm when all apps are installed after wipe) and should also squash a security problem that bluebox reported (CVE-2014-7911).

It should also make less CTS tests fails.

Still uploading... Edit: Uploaded.

Chris
 
Last edited:
J

jogri

Member
May 14, 2015
28
5
54
Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work
 
Last edited:
  • Like
Reactions: chrmhoffmann
C

chrmhoffmann

Inactive Recognized Developer
Nov 11, 2006
1,007
3,205
C

chrmhoffmann

Inactive Recognized Developer
Nov 11, 2006
1,007
3,205
z3ntu said:
btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.
Click to expand...
Click to collapse

This is most likely related to this issue: https://github.com/google/google-authenticator-android/pull/4
It is most likely an MTK issue with problematic math library (or something like that).

Anyway, it works for me when I use the open source version of the google authenticator: https://github.com/google/google-authenticator-android/releases

Chris
 
Last edited:
Z

z3ntu

Member
May 2, 2015
26
5
Jeah, I used the Play Store version, but this is also mentionable in "known bugs" (and that they should use the open-source version)
 
  • Like
Reactions: chrmhoffmann
You must log in or register to reply here.

Similar threads

benkxda
  • Poll
Fairphone - Technical details, links and Q&A interaction with Fairphone [26 Jul 2014]
Replies
757
Views
183K
K
_keesj
C
[ROM][UNOFFICIAL][WIP] Cyanogenmod 11 (4.4.4 - kitkat) for fairphone FP1
Replies
27
Views
39K
C
chrmhoffmann
C
[RECOVERY] fairphone FP1 (1st edition, repartitioned) CWM 6.0.5.0
Replies
23
Views
26K
C
chrmhoffmann
Deedend
And Fairphone?
Replies
65
Views
19K
A
azureskies
mudar1771
  • Poll
[APP] Peace of Mind+, Fairphone fork
Replies
46
Views
16K
P
Phant19

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 27
    C
    chrmhoffmann
    This is Android 4.4.4 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).

    It includes various security fixes on top of 4.4.4 - but most likely not all. Major security hole detectors are green now (VTS, Bluebox, Zimperium).

    NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!

    Without much ado...

    To install...
    - Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
    - Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/filedl/devs...mhoffmann/fp1-kk-stock/fp1-kk444-CH-0.9.7.zip MD5sum: 9140c93ff8f2b8327fdd330d2448c16f
    - I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
    - You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711

    Bugs:
    - IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
    - CTS is complaining about some issues. https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
    - As this is a merge of 4.4.4 into the MTK stuff, watch out for more bugs than the previous release. Not merged: the new 4.4.4 dialer screen (we stick with 4.4.2 dialer as the modifications are too heavy), chromium does not support wml anymore (who cares?).
    - You most likely need to wipe to install this when coming from the previous KK version to 4.4.4. Email app e.g. seems to crash without.
    - Playstore version of Google Authenticator does not work (see https://github.com/google/google-authenticator-android/pull/4). Use the OSS version https://github.com/google/google-authenticator-android/releases - this is not specific to FP1 but seems an MTK issue.
    - A dirty update (without wipe) from 0.8 on an encrypted device seems to reboot once during the "Android is upgrading" dialog
    - Sometimes the lower part of the homescreen launcher seems to lose transparency.

    Changelog fp1-kk444-CH-0.9.7 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
    - Android Security Updates from Google bulletin 1-MAY-2016 (https://source.android.com/security/bulletin/2016-05-01.html)
    - Kernel CVEs including the mediatek wifi ones from https://source.android.com/security/advisory/2016-03-18.html, CVE-2016-2549, CVE-2016-2847, CVE-2016-2547, CVE-2016-2546, CVE-2016-2545, CVE-2016-2384

    Changelog fp1-kk444-CH-0.9.6 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
    - Android Security Updates from Google bulletin 2-APR-2016 (https://source.android.com/security/bulletin/2016-04-02.html)
    - Kernel CVEs including the one from https://source.android.com/security/advisory/2016-03-18.html, CVE-2015-7550, CVE-2016-0774, CVE-2016-0821, CVE-2016-0723.

    Changelog fp1-kk444-CH-0.9.5 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
    - Android Security Updates from Google bulletin 1-MAR-2016 (https://source.android.com/security/bulletin/2016-03-01.html)
    (incl. the kernel fixes that Google only publishes for Google One / Sprout - ported to MT6589)

    Changelog fp1-kk444-CH-0.9.4 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
    - Android Security Updates from Google bulletin 1-FEB-2016 (http://source.android.com/security/b...016-02-01.html)
    - Kernel CVE CVE-2015-8785

    Changelog fp1-kk444-CH-0.9.3:
    - Android Security Updates from Google bulletin 1-JAN-2015 (http://source.android.com/security/bulletin/2016-01-01.html)
    - Some kernel CVEs (CVE2015-8543, CVE2015-8575, CVE2015-7509)
    - Attempt to fix German's E-PLUS on O2 roaming

    Changelog fp1-kk444-CH-0.9.2:
    - Fix that you can now call funny numbers like *143# without phone application crash
    - Fix to be able to add contacts to SIM card

    Changelog fp1-kk444-CH-0.9.1:
    - several kernel CVEs (CVE-2015-5697, CVE-2015-8539, CVE-2015-8215, and a few more without CVE yet)
    - the december 1st security advisory bulletin skia issue introduced in 0.9.0 - aka as the dilbert bug - is fixed now

    Changelog fp1-kk444-CH-0.9:
    - android security bulletin https://source.android.com/security/bulletin/2015-12-01.html
    - also update gapps if you install them: http://opengapps.org/?api=4.4&variant=nano

    Changelog fp1-kk444-CH-0.8:
    - google location providers are used now, which should enable network location provider (in case you installed google apps).

    Changelog fp1-kk444-CH-0.7:
    - National roaming should be fixed (at least as good as CM). If you still have issue with national roaming, send me your mmc/mmn data.
    - Use original FP1 lens parameters for fm50af lens - does this improve the auto/manual focus issues that some people reported compared to stock FP jellybean?
    - Attempt to fix the problem where sometimes the scrollbar and recents screen stopped working and screen locked despite having higher screen timeouts.
    - Full CTS result: https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml

    Changelog fp1-kk444-CH-0.5:
    - SELinux enforcing
    - Camera app now shows all resolutions
    - adb now requires acceptance of adb key

    Changelog fp1-kk444-CH-0.4:
    - ro.adb.secure set
    - browser default pages revisited (removed wrong thumbnail).
    - removed MTK root CAs that are not in AOSP
    - fixed remaining security false-positives in VTS and Bluebox Trustable - all green now
    - USB default setting should be MTP now

    Changelog fp1-kk444-CH-0.3:
    - More CVE fixes (e.g CVE-2015-3845). VTS and Bluebox Trustable are almost green. For some reasons they still think "Stagefright" is not fixed. Zimperium nevertheless shows all stagefright OK. Edit: found out why. It's false positive as MTK reports errors in MPEG4Extractor differently than stock.

    Changelog fp1-kk444-CH-0.2:
    - Netflix issue fixed with new blob from E3
    - Some CTS issues fixed
    - More security fixes CVE-2014-7911

    Changelog fp1-kk444-CH-0.1:
    - Upgraded to 4.4.4_r2.0.1: Yay! That was an insane amount of work. The following "shortcuts" were taken:
    -- Chromium sources taken from AOSP - MTK added wml but it was too much work to merge this back in
    -- Email app sources taken from aosp - MTK customized something there esp. exchange sync, is that really giving someone problems?
    -- Dialer app taken from MTK without 4.4.4 updates - that stuff is too heavily customized also for dual sim, and 4.4.4 revamped the UI, so this was just too much work for now.
    - Latest security fixes up to November 2015. Security fixes also for wpa_supplicant_8 (thanks to Michael Bestas for collecting them for CM)
    - Kernel sec fixes
    - FP1 power profile xml (does this actually change anything)

    As usual some credits:
    - @Santhosh M : for some advice on the modem/baseband
    - @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
    - @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
    - @CyanogenMod for the stagefright fixes

    Let me know if
    - it works also on older FP1 (without U).
    - you have problems with your IMEI, too
    - if you find other major issues
    - if you think I am missing some security updates
    - i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
    View
    8
    C
    chrmhoffmann
    0.7

    0.7 changelog:
    - fix the R - oaming symbol for some virtual operators (like Free in France)
    - Use fm50AF lens params from original FP - does this make auto focus better?
    - Fix lock screen issue (thx @Quallenauge for the reproducible test case from Google Maps navigation). This fixes at least one pattern that broke the slider and recents screen. I am not sure if this fixes all those issues, but I hope so :)

    Give it a go!
    Chris
    View
    7
    C
    chrmhoffmann
    0.9.6 released. Changelog see OP.

    Chris
    View
    6
    C
    chrmhoffmann
    0.9.1 released...

    It fixes:
    - several kernel CVEs
    - the december 1st security advisory bulletin skia issue introduced in 0.9.0 - aka as the dilbert bug
    View
    6
    C
    chrmhoffmann
    0.9.4 released. Changelog: See OP
    View

New posts