So, all of you encourage me to act against sustainability one of the foremost values of Fairphone!
Thank you for this! (very ironic)
I don’t believe this was the demand Fairphone started with, when it raised it Crowd-Funding. Please note that I was very, very patient when I received my Fairphone 6 month AFTER I was promised it to be delivered (with a horrible update policy on delivery schedule!).
Now I am waiting again 6 month only to get a reliable update plan for an update that seems crucible to me to do a educated decision.
Regarding the “promised” I used: Please have a look at
I disagree!
Please read the title!
And this title alone demands a clear update schedule in this (more or less official threat) of Fairphone!
All of you refuse to give a clear clear schedule!
Don’t you see that this schedule is important to make an educated decision?
All love to the Fairphone!
You try to steal out of responsibility!
You are not giving me the info I need to do my decisions!
The topic you linked to doesn’t contain a single post by a Fairphone employee and the title was chosen by the person who asked the question.
We are the community. This is a community forum. We don’t work for Fairphone, so we don’t have the official schedule.
Also please try to make up your mind: Do you want Fairphone not break promises or do you want them to give you a promise about when the update will be released. Because those are the only two options.
You can either expect them to make promises they can’t keep or expect them to keep promises they didn’t make. You can’t have both.
This is the only statement they can make that is reliable. If they were to tell you any timeframe then that would only be guesswork. When they said “September” that was a guess - not a promise - and it wasn’t far fetched as guessing how long you’ll need to port an OS may not be too difficult. They were actually done in June and obviously didn’t expect that beta testing would take longer than July.
Then they encountered severe issues with bluetooth and battery and are trying to fix them. But guessing how long you’ll take to fix bugs is obviously not that easy.
So once again: You can either hear what you want (an exact schedule) or something reliable. Both is simply not possible.
FairPhone is a product, not a charity or a one time project I don’t need to align to any of the expectations you raised. Commitments that made need to bo fulfill, and defects such security holes and reliability bugs need to be fixed in timely manner as long it’s a supported product. I couldn’t care less that the dev can’t fix it in the year passed since the base os provided to fp - hire another dev, reach to the soc vendor or the open source community.
For 4 months now my employer not allowing to sync this os to the company email systm due to all the security issue in the product. The industry standard for security fixes going as around 3 months expected from bug disclosure to a fix for available to users, fair phkne is well behind, and currently I’m holding two phones because of this (very sustainable).
With all given respect, but you knew that you bought a telephone from a startup company that is completely dependant from its suppliers. Furthermore you knew that the Android update situation is less than optimal with all manufacturers.
For such a small company Fairphone did extraordinarily well in supplying security patches. They even got hold of the source code for the totally blobbed Mediatek Android - something different manufacturers wouldn’t even waste a thought about.
Really, get to your senses. Different Android phones don’t do any better.
This is just talking. The truth is that the phones are dying in our hands and nothing concrete seems to happen to FP1 owners. More and more users are switching. Phones are freezing, crashing, and rebooting like there was no tomorrow. Soon these talks will end because there will be no one left complaining. Hence, no tomorrow for FP!
Yes, the phones are slowly dying. But the things you mentioned (a broken power button) and the issues I have (my second battery seems to be in bad shape) are hardware defects of a already very old phone and nothing Fairphone can do about now. (It looks like they have learnt from it and corrected some of the issues in the FP2.)
They won’t be fixed by installing new software.
And BTW: You make it sound like this affects a majority of the phones. I’m using my power button probably more often than I should, my phone is now more than three years old and I don’t have an issue with my power button. It’s not that dramatic as your comment suggests.
No, it is not the power button and I am already on my third battery. It happens when the phone is lying on a table in front of me, or when I arrive home when it connects to my WiFi. The reboot sometimes takes up to 10 minutes. These are not hardware issues for sure.
IMHO, the bottom of this issue is that FP’s sustainable business model was always broken. They tried to make it work inside a planned obsolescence ecosystem (Android) and that starts by being very hard to eventually becoming impossible. We are watching it! live!
It’s not always the software’s fault. Sometimes it’s just bad luck or a mobile operator that doesn’t care for backwards compatibility, for example in this case:
@Luis_Quental_Pereira If you are looking for a solution to your problem, please go to that other thread or search the forum for alternative ways to solve the problem.
It doesn’t help anybody, if you post here. Nobody knows if the #kitkat update will solve any issues that people have reported.
To everybody who wants to know exactly how #kitkat is coming along here is the up-to-date list of (critical) issues.
If you don’t mind those you can help testing.
What’s kind of nagging me is that it’s March 2017 now and we’re still waiting for Kitkat without any substantial news on progress or even bug fix patches for 4.2.2. It’s not just that we’re not getting a Kitkat update, we’re also not getting security updates for the OS any more. What stings even more is that FairPhone 2 is continually getting software updates and is currently beta testing an Android 6.0 update. Of course it was to be expected that updating FP2 would be a lot easier than FP1, but it’s getting a bit awkward now.
So what’s the hold up? In this thread I’m seeing 6 unfixed issues. Is that all that remains? Have they been working on just these 6 issues for the past 6 months? It sounds harsh, but if you can’t fix an issue in the past 6 months, why would you be able to fix it in the next 6?