I´m glad to find this thread and the possibility update my Fairphone to Android 4.4.4…
Unfortunately I haven´t read the whole topic…my Fitbit Tracker doesn´t work (as someone of you describes). The only reason why I want to update my phone.
Is there someone, who find I way to fix this? (Tracker was identified in Bluetooth but cannot connected)
I have a Garmin Vivoactive which uses Bluetooth LE and I cannot get it to connect reliably. I’m not sure whether the problem is in the Garmin or the phones Bluetooth stack. I suspect the former. I keep trying as new new versions appear.
This was originally the only reason I updated my phone, but I’m glad I did as, apart from the Bluetooth problem, I think it is great software.
I’m sorry I can’t give you better news.
I guess you will have to provide a bit more info. I assume the game is “Frozen Bubble”? Can you log into the phone while you play the the game and have a look at the log files? Can you find out what keeps the phone busy?
There is no guide for that yet, I’m sorry. Mostly it will help if you setup the phone so that you can access it using adb. With that you can run some commands on the phone (adb shell) to check how its resources are being used and also have a look at the logs (adb logcat). But so far nobody has written a guide for this yet.
However, I think that the App-Switcher is much slower than with the official Fairphone OS. I searched a bit in the internet and found that it could be the Swap. The original Fairphone OS has no Swap but this rom has 500 MB Swap (You can see that with the app “OS Monitor”).
Is this true?
If yes: any idea how to disable the Swap?
Did anybody succeed in using the Estimote BT LE beacons with the 4.4.4 ROM? I experience the same problems as with Fitbit activity tracker: the device is visible in the list of Bluetooth devices, but the app does not recognize/ find them.
Apart from connecting to Bluetooth LE devices, the ROM works very well for me. Unfortunately, the BT LE functionality is one of the main reasons for me to use Android 4.4.4.
Sadly I think this is a problem with the BT LE stack in the ROM. I have experienced similar problems with my Garmin VivoActive which also uses BT LE to connect to the phone. Sometimes it will connect, but not reliably, and, if it does manage to connect, the connection gets dropped after only a few minutes, and automatic reconnections don’t work.
I’ve kept the ROM as the other stuff makes it very much worth having IMHO, and I can sync with my Garmin via a laptop rather than the phone.
Yes, I also have the feeling that the “hardware” is somehow around, but that there is a problem with the software layer. According to the info I found, BT LE should work “somehow” with both phones. But maybe I’m reading it the wrong way. I’m sure there is a way to debug this somehow, if you have the right tools. I think MTK/Android is not using the standard stack anymore. So I guess all we can do is wait for the last MTK FP1 release from FP.
Just installed the ROM two days ago, thanks @chrmhoffmann.
Thanks @fp1_wo_sw_updates for the HOWTO. Eventually I can add a section on how to do it WITHOUT a working USB port (dead on my FP1), using adb over wi-fi.
Overall the ROM sounds good but I have two minor problems:
a) I use the two SIM cards (private/pro) and need to be able to send SMS with both of them. The stock messaging app before the 4.4.4 ROM was dealing it correctly asking with SIM card to use before sending an SMS. And I was using Textra, more fun, for my private SMS. Here comes my problem: the 4.4.4 ROM’s stock messaging app (1) needs to be the default messaging app exclusively, and (2) doesn’t bother with dual SIM. Any hint?
b) I was using Gmail with multiples accounts, among them my pro emails directly in gmail through the Google add-on “Exchange services”. It does not work anymore : (1) the 4.4.4 ROM comes with an older version of Exchanges services which is not detected by the current gmail version, (2) I can’t succeed to connect to my pro email account with a newer “Exchange services” add-on. I fixed the matter by installing the Outlook app, which works fine, but it was not (at all) my first intent!