yashsingh1/xdaforums huggingface dataset:
[Fairphone 1] 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 [MENTION=4636351]Quallenauge[/MENTION] 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
[Fairphone 1] jogri:
Thank's a lot for the updates, why don't you get a "mini-job" at Fairphones , so these kitkat updates would be official updates, it would be worth it. Anyway - you do a great job - thank you very much!!!
[Fairphone 1] Quallenauge:
Many thanks for solving this issue! My test cases performing successfully, atm. no problems with the lock screen anymore.
[Fairphone 1] chrmhoffmann:
Full CTS results for 0.7:

https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml

Doesn't look too bad actually...

Chris
[Fairphone 1] Nihal @A-JAX:
I ported v0.5 of this rom for my MMX Canvas 4 and here are the bugs I found:

1) Port related (never mind)

- no phone storage [data partition is shown as phone storage]( I found you're using repartitioned phone)

- no sound (I just replaced modem and boot so may be )

2) Rom related

- Recent menu and lock screen doesn't work after sometime

- Screen timeout issue

- USSD code doesn't work (phone app force closes)

- no internet access to only play store.

Have to try your 0.7 version. Please build the same for wiko stairway so that we can enjoy 4.4.4 too. And sorry for porting. I have limited data.
[Fairphone 1] chrmhoffmann:
When I find some time, yes, I will do the Wiko Stairway, too. Those are my 6589 phones. :)

Chris
[Fairphone 1] manu_26:
Thanks for the development.

Quick question: I'm currently using device encryption on the original FP ROM. Do I have to consider any additional steps to install this version or is the process the same?
[Fairphone 1] chrmhoffmann:
Nothing special. You will lose your current data as an upgrade is not supported. It means that you have to wipe your device from the recovery. But this is the same on non-encrypted devices.

You can then reencrypt - hopefully. Haven't tried this yet.

Chris
[Fairphone 1] manu_26:
Thanks. I guess I'll try the ROM over the holidays when I've got more time. Of course, I'll post my feedback right here.

One more question concerning the Authenticator App: how about the version on f-droid? Does that version work or is it the same as on the play store?
[Fairphone 1] chrmhoffmann:
Did you restore nova through titanium? I installed it from scratch and can't really see any lag. But haven't checked logcat either...

Chris
[Fairphone 1] chrmhoffmann:
No idea, but the one from github (OSS) works fine with google two-factor authentication.

Chris
[Fairphone 1] ralf_xda:
First I restored it through titanium, but than I uninstalled and re-installed it, just to be sure.

But this issue is less important as I found a simple solution: just changed the drawer style to vertical. Vertical scrolling in the drawer shows no lag.
[Fairphone 1] chrmhoffmann:
Just encrypted the phone. Seems to work just fine....

Chris
[Fairphone 1] manu_26:
Awesome. As soon as I find the time, I'll check out the ROM and will give feedback.
[Fairphone 1] manu_26:
OK,

I just installed the latest version.

I also had some trouble with a boot loop due to the device encryption. The password prompt popped up on boot, so some traces of the encryption must have survived. After formatting all partitions in the recovery tool it worked.

Now I still have problems with the xposed-framework.

I downloaded the original xposed-installer apk and installed it. Then I rebooted into recovery and applied Quallenauge's zip:

xposed-v58-sdk19-arm-custom-build-by-Quallenauge-20151125.zip

But I still get these messages in the xposed-installer:
[Fairphone 1] manu_26:
There is another weird thing I found (at least on my phone). Location services only work for me if I turn on GPS. Without GPS (only network location) I can only see my position on Google Maps. Other apps seem to fail grabbing the current location (for example: Chronus widget (weather location), Öffi Haltestellen, OsmAnd~). But then again the App "DB Navigator" works just fine.

Another thing I noticed: The wifi symbol is always grey (never blue). Didn't that mean that Google Play Services has no connection?
[Fairphone 1] chrmhoffmann:
Apparently in KitKat the status icons are all white (http://www.androidpolice.com/2013/1...nd-only-shows-connectivity-in-quick-settings/). I guess that MTK didn't follow the policy and painted the 3G GSM icons blue...

Chris
[Fairphone 1] chrmhoffmann:
Hi,

I guess it is mainly due to the problem that on the FP1 modem, http://developer.android.com/reference/android/telephony/TelephonyManager.html#getAllCellInfo() does not return anything (maybe because it's a JB modem).

Location providers are then supposed to use http://developer.android.com/refere...TelephonyManager.html#getNeighboringCellInfo()

But maybe not all apps (or location providers?) don't use this properly. It also seems that all location providers are closed source :(

Chris
[Fairphone 1] chrmhoffmann:
Well, above might be true, but in fact, it's simpler than that. The google apps package name has changed, so in the overlay, we need to change:

<string-array name="config_locationProviderPackageNames" translatable="false">

<!-- The standard AOSP fused location provider -->

<item>com.android.location.fused</item>

- <item>com.google.android.location</item>

+	<item>com.google.android.gms</item>

</string-array>

I will release 0.8.

Thanks for reporting this issue!

Chris
[Fairphone 1] chrmhoffmann:
0.8 released which fixes google location providers.

Chris
[Fairphone 1] manu_26:
I can confirm that location services work as expected now. So thanks a lot.

Concerning the play services I think that everything is fine. I checked the play services monitor and there's a connection and push seems to work. So I was just confused by the white/grey wifi symbol.
[Fairphone 1] ralf_xda:
Please check if you have the following files in place:

0aa4905d5141ceab53945008e7252b93 /system/bin/app_process
c0cb7f0482cb9522b75a74b33b3a42de /system/framework/XposedBridge.jar
ead195c2d888a26d13a98319ee140f77 /system/xposed.prop
[Fairphone 1] manu_26:
Thanks for your answer.

Yes, all those files with the exact MD5-sum are in place.
[Fairphone 1] manu_26:
Ok, I found a solution that works for me.

I used the modified xposed installer in this post: http://xdaforums.com/showpost.php?p=64063168&postcount=62

I hope that file is trustworthy. Maybe someone with a bit more experience can check out this apk (I used the first one) and tell me if it's safe to use.
[Fairphone 1] joergschulz:
This made me install .8 as well. Congratulations. While with .4 I had problems getting a GPS fix at all, now location services are working as good as never with FP1U; in flight mode (GPS only), it took 5 minutes to get a fix, with networks enabled, I had a fix almost instantly. Still testing this one.
[Fairphone 1] manu_26:
I witnessed another change compared to the official FP firmware.

Before running this custom ROM my battery went normally down to ~20% charge and then within minutes to 0.

Now my battery first seems to last very long, but then makes a huge jump down from 40-50% to ~15% and then I have a few minutes to go.

Is that a calibration problem or do I need a new battery anyway?

View attachment 3569609
[Fairphone 1] chrmhoffmann:
0.9

0.9 fixes android security bulletin from: https://source.android.com/security/bulletin/2015-12-01.html

Please update ASAP.

Note:

- There's one kernel security update that is not publicly know but fixed in Nexus kernels. Still trying to find which one.

- MTK sources esp. in the stagefright area are very different from AOSP. I apply security patches the best I can, but there's no guarantee that this is 100%. Anyway it's better than nothing.

- There are also new gapps from: http://opengapps.org/?api=4.4&variant=nano - maybe worth updating them, too. Who knows, maybe there are also security related fixes.

Chris

PS: You realize that you get security updates now even faster than certain Nexus devices get OTAs?
[Fairphone 1] chrmhoffmann:
Dirty flash update reboots

Hi,

I noticed that a dirty flash update shows the "Android is upgrading" with decreasing counters, but then it reboots.

It doesn't seem to cause any issues apart from booting again and to continue "Optimizing..."

Maybe it's also because I use device encryption now and it's just, err, slower and thus some watchdogs time out?

Chris
[Fairphone 1] manu_26:
Installed both. No issues. Only one reboot. Thanks a lot once again.
[Fairphone 1] ralf_xda:
Chris, what you are doing is amazing! Very nice.

The patch for CVE-2015-6617 (skia) seems to break some apps here. The F-Droid app crashes shortly after startup, every time. Same for the Simple Dilbert app.

Logcat gave me the hint to libskia, so I replaced /system/lib/libskia.so with the one from your 0.8 build. This fixes the crashes.

The questions now is:

May this be a caused by the differences between the mediatek sources and AOSP?
[Fairphone 1] joergschulz:
Cannot confirm - my FP1 seemed to update fine to 0.9 (no encrypted storage). Rest of tests not yet done.

---------- Post added at 10:28 AM ---------- Previous post was at 10:05 AM ----------

confirmed. Firefox crashes here as well.
[Fairphone 1] manu_26:
OK, now that I read your posts, I can confirm f-droid crashing. Furthermore the e-mail app crashes when opening some specific emails.
[Fairphone 1] chrmhoffmann:
Can you please always post logcat?

Fdroid and Firefox work fine for me :(

Chris
[Fairphone 1] joergschulz:
what I'm seeing in the log

Will this be enough?

V/WindowManager( 649): Changing focus from Window{42141478 u0 Application Error: org.fdroid.fdroid EXITING} to Window{425cc2d0 u0 com.android.launcher3/com.android.launcher3.Launcher} Callers=com.android.server.wm.WindowManagerService.removeWindowLocked:2781 com.android.server.wm.WindowManagerService.removeWindowLocked:2720 com.android.server.wm.WindowManagerService.removeWindow:2715 com.android.server.wm.Session.remove:182
D/PhoneStatusBar( 728): setSystemUiVisibility vis=40000700 mask=ffffffff oldVal=40000000 newVal=40000700 diff=700
I/WindowManager( 649): Gaining focus: Window{425cc2d0 u0 com.android.launcher3/com.android.launcher3.Launcher}
I/WindowManager( 649): Losing focus: Window{42141478 u0 Application Error: org.fdroid.fdroid EXITING}

or, while trying to set a background image:

V/WindowManager( 649): Changing focus from Window{423330f0 u0 Application Error: com.android.launcher3 EXITING} to Window{425cc2d0 u0 com.android.launcher3/com.android.launcher3.Launcher} Callers=com.android.server.wm.WindowManagerService.removeWindowLocked:2781 com.android.server.wm.WindowManagerService.removeWindowLocked:2720 com.android.server.wm.WindowManagerService.removeWindow:2715 com.android.server.wm.Session.remove:182
D/PhoneStatusBar( 728): setSystemUiVisibility vis=40000700 mask=ffffffff oldVal=40000000 newVal=40000700 diff=700
I/WindowManager( 649): Gaining focus: Window{425cc2d0 u0 com.android.launcher3/com.android.launcher3.Launcher}
I/WindowManager( 649): Losing focus: Window{423330f0 u0 Application Error: com.android.launcher3 EXITING}
D/dalvikvm( 649): threadid=80: exiting
[Fairphone 1] chrmhoffmann:
OK. I can reproduce the crash now...

Hrmmmm....

Update: won't be able to fix this right away, you can take old libskia.so and push it to /system/lib

adb root

adb remount

adb push libskia.so /system/lib

Chris
[Fairphone 1] chrmhoffmann:
Indeed I can reproduce this. There is a security fix in skia. Looks like it breaks something. I can't see any mtk specifics here. So maybe Google made a mistake...

Hrmmmm....

Chris
[Fairphone 1] ralf_xda:
Ok, good to know. I was just going to disable Xposed to see if it may be related to it. But I asume you do not have Xposed installed, have you? So I can save the time and just revert to libskia.so (0.8) again.
[Fairphone 1] chrmhoffmann:
I don't have exposed installed. I already have enough problems ;)

Chris
[Fairphone 1] ralf_xda:
I'm sure I know what you mean. ;)

Something completely different:

I wrote recently that the gallery app is slow in deleting photos when there are a lot of photos in the camera folder. This is only the case when you are in picture view mode, then it takes up to several seconds until the photo is deleted. Now I discovered by accident that the gallery performs very poor in displaying animated png, too. Under 4.2.2 the gallery app was fast in all cases. Yesterday I thought I should give some other stock gallery apps from other roms a try.

First I tested the one from your wiko-stairway-kk-0.7 build but it performs exactly the same. Then I tested the one from your cm_acclaim-UNOFFICIAL-cm11-2015-11-19 build (camera and gallery are splitted into Camera2.apk and Gallery2.apk). The camera does not work (too device specific I assume), but the gallery works like a charm! The deleting of photos is as fast as in 4.2.2 and playing of animated png is faster than light. :) It feels snappier in other places, too, e.g. when scrolling through albums etc.

So my question: Would it be possible to merge the Gallery2.apk from cm_acclaim-UNOFFICIAL-cm11-2015-11-19 into our Gallery2.apk to get both a working camera and a fast gallery?

I know, there are many other things to do with higher priority but may be it could be put on the to-do list.
[Fairphone 1] 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
[Fairphone 1] jogri:
Thanks a lot, great, everything is working fine so far
[Fairphone 1] ralf_xda:
:laugh:

Seems like basketbuild.com has problems since hours ("An unexpected error has occurred.")

Any chance for an alternative download?
[Fairphone 1] chrmhoffmann:
Basketbuild is back. Just when I am at 85% upload to androidfilehost.com !!!

Anyway: here's a mirror: https://www.androidfilehost.com/?fid=24269982087016133
[Fairphone 1] chrmhoffmann:
- How many photos do you have?

- Do you have an example animated gif (or png) that is slow?

- Logcat?

Anyway, there are plenty of gallyery apps on the playstore (e.g. also the one from cyanogenmod), until we figure out what goes wrong here in MTK land.

Chris
[Fairphone 1] joergschulz:
first view: everything looks fine

Been there, installed it (clear cache, sideload .zip, reactivate XPosed) everything looks fine now.

By the way, I currently enjoy better GPS/location performance than ever with the fairphone.

Not yet tested: Bluetooth.

When I use the FairPhone launcher, (./adb install ~/Downloads/FP1-Fairphone_OS_v1_8_7_OTA_2015081400/system/app/FairphoneHome.apk) I can even set a background image what I can't with the stock launchers under 0.8 and 0.9.

This release would earn the name: 0.10 where the previous would have been 0.09 but release numbers aren't decimal.

Great works, Chris!
[Fairphone 1] z3ntu:
[MENTION=361777]chrmhoffmann[/MENTION] should I upgrade from the first KK version 4.4.2 to the newest now?
[Fairphone 1] joergschulz:
IMHO, yes, definitevely. Just scroll through this thread for possible errors - not too many left, I'd say.

Jörg
[Fairphone 1] chrmhoffmann:
0.9.2

Released to fix:

- dial funny numbers (like *143#)

- creation of sim card contacts was crashing

Chris

PS: very likely last release this year :) Happy holidays!
[Fairphone 1] manu_26:
Happy holidays and thanks for this awesome present.

---------- Post added at 08:32 PM ---------- Previous post was at 08:30 PM ----------

Btw. The download link throws a 404...still uploading?
[Fairphone 1] chrmhoffmann:
Should be there now...

Chris
[Fairphone 1] cbrunos:
Just installed it on my FP1 and it works like a charm! At first I was stuck on a boot loop but then I wiped the data and the cache from recovery, and reflashed the rom. Then it booted normally. Thanks for this!

Edit: I just noticed that my Fairphone is not rooted anymore. After installing supersu I was prompted to install the su binary via recovery, but the installation failed. What do?

EDIT2: Well, I've just flashed supersu using recovery, so it's ok now.

Thanks again for your hard work!
[Fairphone 1] chrmhoffmann:
It is rooted. You need to enable developer options and then enable root (like in cyanogen - from who I copied the code for this).

No need to install anything.

Chris
[Fairphone 1] Dede525:
wow, I just came to xda to see if someone wrote something new about the FP1 and you actually did it! That's amazing, a cm11 rom for the FP1 is kind of incredible!

I am considering to flash this rom, but have a question that I couldn't find on the topic:

Is the dual sim working or is just one sim working?
[Fairphone 1] chrmhoffmann:
Dual sim should be OK.

Chris
[Fairphone 1] joergschulz:
Definitely works. My setup: 1st sim data-only, 2nd sim voice, SMS.

I am using the most current version, FP launcher, XPosed, Google apps (most recent open GAPPS), just like written above
[Fairphone 1] chrmhoffmann:
It is BTW not CM11.

Chris
[Fairphone 1] Donat.Callens:
How did you get xposed framework to install correctly? I get an error that xposed is not yet compatible with sdk version 19.
[Fairphone 1] manu_26:
Go back a few pages in this thread to find out.
[Fairphone 1] Donat.Callens:
So you are saying we need to use this http://xdaforums.com/showpost.php?p=64198697&postcount=67
[Fairphone 1] manu_26:
At least it works for me. Use at your own risk.
[Fairphone 1] Donat.Callens:
Thank you for this 4.4 ROM chrmhoffmann. I like it

Only two things have been found to be not working:

- ART instead of Dalvik (no error message, it just does nothing)

- Face Unlock (on the configuration screen, it seems it cannot use the front face camera as there is no image)

PS: used manu_26 solution for Xposed successfully
[Fairphone 1] joergschulz:
Thanks again for the 9.2 release. For me, the best software my FP1 ever had.

- Now I can even pair with my car radio using bluetooth successfully which wasn't possible with FP original software.

- GPS fix faster than previously, and more accurate as well. Without knowing, even without Google services (forgot to reinstall the gapps after installing 9.2).

Chris, you saved my FP1 from being sold 2nd hand!
[Fairphone 1] chrmhoffmann:
093 released

Changelog fp1-kk444-CH-0.9.3 - also you might want to check if there are new gapps here and flash at same time: http://opengapps.org/?api=4.4&variant=nano

- 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

Chris
[Fairphone 1] manu_26:
Damn, drop those releases like they're hot. Awesome. If you update faster, you'll invent time travel.
[Fairphone 1] jogri:
Thanks a lot. Great!!!, everything is working fine
[Fairphone 1] Donat.Callens:
I personally tested the Aroma installer for the Open GAPPs 4.4 on this ROM and it works flawlessly. I now get to remove all the Stock applications and can replace the default Browser, Calendar, Camera, Clock, Keyboard and Messenger apps with the latest versions from Google. And there is still space left on /system for XPosed and some... Awesome.

The only downside is the big download size for the small amount of apps i am going to use from it. But it is worth it nevertheless.

Edit: The Aroma version from 2015-12-19 works fine. The latest from 2016-01-08 does not.

Edit2: The Aroma from 2016-01-09 does work fine. Make sure you check the Version Information file and have

ok

in the

Sig.

column for (almost) all the applications
[Fairphone 1] Donat.Callens:
Can we do anything about the device name that is set to ahong89_wet_jb2? Should we just manually edit the build.prop file ourselves? Is ther e a risk in doing so that the wrong apps versions will be installed from the play store?
[Fairphone 1] ralf_xda:
Has anyone managed to install certificates? I tried to install the CAcert root certificate (and others) without success.

Neither "/Settings/Security/Install from phone storage" nor install via file manager does work.

First gives this logcat output:

D/CredentialHelper(17564): # extras: 1
D/CredentialHelper(17564): CERT: 36
W/CredentialHelper(17564): parseCert(): java.security.cert.CertificateException: com.android.org.conscrypt.OpenSSLX509CertificateFactory$ParsingException: com.android.org.conscrypt.OpenSSLX509CertificateFactory$ParsingException: java.lang.RuntimeException: error:0D06B08E:asn1 encoding routines:ASN1_D2I_READ_BIO:not enough data

Install via file manager / Certificate Installer gives this:

E/CertInstaller(22443): Failed to read certificate: java.io.FileNotFoundException: /storage/emulated/0/root.crt: open failed: EACCES (Permission denied)

[MENTION=361777]chrmhoffmann[/MENTION]

Could this be related to https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml#android.core.tests.libcore.package.conscrypt?
[Fairphone 1] chrmhoffmann:
Was the certificate imported successfully on some other KitKat device? Did you try it with another format?

I will try to reproduce. Don't you need to install root certificates some where yourself with the file manager?

Chris
[Fairphone 1] ralf_xda:
Problem solved, no need to reproduce.

I just downloaded the certificate files with the stock browser so the files are stored under "Downloads" (/sdcard/MyFavorite). Then (and only then) they are installable via /Settings/Security/Install from phone storage

Under 4.2.2 it was possible to install the certs when the files were simply copied to /sdcard.

Seems these are some security restrictions introduced with 4.4.x

Sorry for the noise.
[Fairphone 1] Donat.Callens:
Use this to be able to access the SD card as in versions prior to 4.4 https://play.google.com/store/apps/details?id=nextapp.sdfix
[Fairphone 1] ralf_xda:
/sdcard refers to the internal storage, not the external sdcard.

Edit: to be clear, the files are accessible but the certificate system refuses to parse them until they are copied to /sdcard/MyFavorites (aka Downloads).
[Fairphone 1] derhannes:
Success on FP1

fp1-kk444-CH-0.9.3 on an FP1.

Installation took many attempts because of an encrypted /data partition.

In the end, I had to first flash "Kola Nut 1.8.7" for "FP1U and FP1 with upgraded partition layout" (cf. fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions-) to get a "clean" FP1 OS without encryption.

Then I installed the v0.9.3 from this thread and did a factory reset (this is where the installation failed before - it told me it could not access /data).

Thanks to the developer!
[Fairphone 1] manu_26:
I had a similar problem that I could resolve by formatting all partitions in the recovery tool.
[Fairphone 1] joergschulz:
Using the current rom for weeks now in my (albeit limited) daily tasks, the ROM seems to be stable and mature. I can take photos, connect to bluetooth, sync with owncloud, use some google apps (playstore), have xprivacy, navigate using OSMAnd (does not find locations when Nokia here is active and vice versa, interesting) .

If turned off, the phone powers on for stored alarms. Battery life seems to be good, but my poor usage might not be representative. I never use more than 50% of battery per day.

It's amazing, pretty good work.
[Fairphone 1] ralf_xda:
Yep, it runs very stable. I use these builds since November without significant issues. And I am very happy that we get security updates virtually as fast as the Nexus users (thanks again, Chris!).
[Fairphone 1] chrmhoffmann:
0.9.4 released. Changelog: See OP
[Fairphone 1] chrmhoffmann:
FP1 does not seem to be affected by this: https://twitter.com/jcase/status/687592592662466560

Not sure if the screenshot is the only test case though.