[UNOFFICIAL] Stock ROM Android 4.4.2/4.4.4 Kitkat for FP1 & FP1U

Help Fairphone 1
,
131

Thanks for the offer to fix issues. I’ve encountered one:
I’m a blau.de customer which uses the E-Plus (and now also O2) network in Germany. The roaming issues was fixed by Fairphone as discussed in this thread.

Unfortunately I can’t give you mmc/mmn data since I don’t know what that is (and googling didn’t help). My only guess is that this is a typo and you mean MCC/MNC. These seem to be the following for my provider blau.de (second source):

MCC: 262
MNC: 03

I don’t know whether this is the correct information to make usage of both O2 and E-Plus network work, though.

I’d be happy to hunt for more information if necessary.

1 Like
132

That is probably an option. How can we arrange this?

133

I haven’t read about other people experiencing problems with automatically connecting to wifi networks. Am I the only one having this problem?

Best regards, Michel

134

I have version 0.9.2 and haven’t had any problems yet.

135

Had some really weird things happen with my phone this week after installing the custom ROM. After a few hours switched off my phone booted into android 4.4, but a load of stuff no longer worked. No amount of resets, taking battery out, changing settings seemed to make any difference. Ended up having to wipe user data and start fresh. Next day the same thing happened! Have returned to the standard fairphone OS for now as I need to use the phone but I’ll be continuing to lurk and will probably give it another go soon.

Full(ish) list of symptoms:
Lock screen not appearing
Home button inactive, both long and short press - vibrates but does nothing
Buttons in swipe down menu (e.g. wifi on/off) cannot be reached
All settings returned to default values (e.g. wifi turned off, input methods back to defaults)
Off button long press no longer shows sound profiles - just option to shutdown

1 Like
136

You can try [this thread][1]. Read carefully and do the same
[1]: [FP1(U)] Baseband software unknown)

137

I once installed the Cyanogenmod for FP1 and suddenly started having lots of random issues, some similar, some different from yours. After lots of hard resets I found that the problem was a large useless .zip file using all of the cache partition. I erased it and it returned to normal. Take a look if there’s such a file in your phone.

138

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

Enjoy

6 Likes
139

Everything runs well, thank’s a lot for your excellent work

140

I would like to install this on my FP1 but I’m a bit scared… not being a programmer and all. What do I need to know?

Thanks

141

Look in this first post and follow the link to the xda-developers forum.

1 Like
142

Thanks for the quick fix. Unfortunately I’m not in Germany anymore and can’t test it myself. Is anyone else here with E-Plus as a provider?

143

There is a very detailed guide by @fp1_wo_sw_updates

1 Like
144

Solved: the solution is to install version 20160106 rather than 20160108 of GApps
Different Gapps releases can be acessed from Tags · opengapps/arm · GitHub
I also wiped wiped cache and dalvik-cache first, though I don’t know whether that was necessary
Thanks joagri!

Thanks for the updated ROM. The updated ROM is fine, but when I try to install the latest GApps, with

adb sideload open_gapps-arm-4.4-nano-20160108.zip

the install fails with the following

...
- Installing updated GApps
E:Error in /tmp/update.zip
(Status 2)
Installation aborted

I can install the previous version open_gapps-arm-4.4-nano-20151225.zip with no problems.
I’ve Googled the error but not come across an obvious fixes. Any clues or suggestions?

Regards

Pete

145

Hello Pete, reboot into recovery and install gapps this way (from sdcard) . Worked without any problems with me.

146

How does that work with GApps? I often see people suggesting installing newer GApps but doesn’t Android update the GApps to the latest version through the Play Store itself?

148

I downloaded open_gapps-arm-4.4-nano-20160106.zip not open_gapps-arm-4.4-nano-20160108.zip. Maybe thats important???

149

… and also wiped cache and dalvik-cache first…

150

I just tried with a jawbone up2 and I was able to pair and connect and use the jawbone up software from the playstore.

So I think that BT LE seems to work at least to some extend.

Chris

PS: I also have a fitbit somewhere but can’t find the charger.

151

My experience is that it works to some extent, but is still a bit flakey :slight_smile: . A particular problem I have noticed is automatic re-connections, which often just do not happen. This is not confined to BLE: I have problems with the following devices, only the first of which is BLE:

  1. [Garmin VivoActive GPS Smartwatch with Sports Apps:][1] this is BLE, and I think its own BT implementation is a bit flakey. Works OK immediately after both devices are powered on, but re-connects fail after subsequent disconnections. This did not work with the old FP Stock ROM as that did not have BLE

  2. [IOPlay 2 Bluetooth handsfree car kit][2] (Not BLE) Connections are sometimes incomplete: the IOPLay shows the phone as being connected, but the phone does not respond to music controls, and music playing on the phone is not play through the handsfree. This mostly worked OK with the old FP stock ROM

  3. [BoomBar Portable Rechargeable Bluetooth Speaker][3] Agin re-connections sometimes fail. To play music through the Boombar I often have to initiate the connect manually from the BT Settings page on the phone

I know this stuff is tricky, and it’s hard to reproduce the problems deterministically. Let me know if I can help, by providing log files or anything else.

Thanks again for all you work on this ROM!

Pete
[1]: http://explore.garmin.com/en-GB/vivo-fitness/
[2]: http://www.my-io.com/products/io-play2-overview/
[3]: http://www.mobilefun.co.uk/kitsound-boombar-portable-rechargeable-bluetooth-speaker-black-p40120.htm

2 Likes