It worked for me without having to re-enter the settings (WPA2-Personal and WPA2-Enterprise).
But there are a few problems:
Sometimes I loose connection. This is probably a combination of the building I’m in, using 2.4 GHz and the other people who use it, too. This happens with other devices, too.
After a few hours of having connection, loosing it, reconnecting and so on, my phone won’t reconnect. It simple stays on mobile (which mostly isn’t available in the building). The wifi settings say “Disconnected.”. I guess that it gives up after a few times loosing connection. I would count being connected for more than 5 minutes as successful.
Sometimes when using memory intensive apps (e.g. Firefox), I’m loosing wifi. The connection goes away and there are no available networks listed in settings, only the known ones. This goes away when I disable and re-enable wifi. I guess that wpa_supplicant is killed when the system runs out of memory.
Anybody here, who has the Bose Quietcomfort 35 headphones and can test the microphone quality during calls? We are trying to figure out what’s the problem here.
It works for me in an Android emulator (at boot and when run with bootanimation).
On my FP1 it only works when I execute bootanimation after bootup. It won’t show during boot.
Were is this “android” bootanimation.zip stores at?
And how can I get the Fairphone updater for #kitkat without gapps?
The rest works fine, I’m about to use my FP1 as my main phone again.
OK, something weird just happened regarding the call lag:
I searched around because it bugged me (pun not intended!) and found this Stackexchange post. One suggestion was to install an alternative dialer app. I went to F-Droid and installed Dialer2 from 2012. When I then placed a call through my launcher KISS it was as fast as it gets! The effect stayed after I had uninstalled Dialer2.
My hypothesis: Dialer2 managed to load the required information (caller list? Contacts?) into the RAM and the call manager could make use of it, bypassing the stock dialer. The first time you try to call someone it takes some time until the telephony app is loaded into RAM and the following times it’s there already and calling is faster.
PS: I’d like to split this topic, but I’m undecided whether it is #kitkat specific or happens on Kola Nut too…
Edit: An hour later, I press on that contact in KISS launcher again and the call starts as slow as always (~5 seconds). The second try is “rocket”-fast again though (in comparison).
I deleted my call history now (and uninstalled Dialer2 again, but I no longer think it’s relevant) and will report back in an hour or so.
Edit2: It’s not the call history. An hour later, the first (and this time the second a very short time after the first) placed call takes about 5 seconds until the call window appears.
Edit3: Ok, the call goes through and it can be embarrassing, if you are testing this and can’t hang up because the call screen doesn’t come up. Luckily I was testing this by calling my mother, so no harm done!
Edit4: Nope, Deleting data of “telephone /sms storage” with Titanium Backup doesn’t solve the issue.
But I don’t think you can ever solve this problem.
The dialer app has been opening slow on all Android devices I’ve ever owned (on one device it was even so bad that I couldn’t accept any calls).
Android is not that optimized as the firmware on dumb phones. It will never be that responsive.
You can try to solve this issue by throwing RAM and / or processing power against the problem but as the FP1 is not easily upgradable, that won’t be possible. (And this won’t happen, either, I guess.)
You could try to remove all apps and data from your phone. But what’s the point in having a smartphone then?
(It may be a good idea to prioritize some apps regarding RAM, but I don’t think that it possible on Android. It may be possible for the dialer app to display a steady notification.)
Yes, this is annoying.
However, I found a workaround:
You can turn off the screen while talking by pressing the power button.
The call will continue but your face can’t hang up the call anymore.
Hello! I’ve finally installed pre3. So far so good, except the updater app still doesn’t work for me since pre2 for some reason… It crashes instantly when I try to launch it. I have already contacted @jftr by email to explain the problem, but we could not figure it out.
The following things are nice to have and not bugs:
Increase the amount of zram. Currently, the device uses one zram with 512MB. On desktop Linux it’s quite common to create a zram per CPU (core). That would be 4 in our case. So perhaps 4x256MB? (This will need some fine tuning.)
Include a build of busybox. It is a bit tedious to reinstall Busybox after each firmware upgrade. And it would be better to use a recent build made by the people who build the ROM than an old build from F-Droid (or some unknown build from the Play Store).
Do something about the kernel ring buffer. It isn’t possible to get old messages with only three days uptime. My laptop has those logs even after more than a week.
