It’s not an issue on my phone for example, the algorithm learnt quite quickly.
If you are Google or Apple with more employees than Fairphone has customers.
It’s not an issue on my phone for example, the algorithm learnt quite quickly.
If you are Google or Apple with more employees than Fairphone has customers.
That has absolutely nothing to do with it. It is not that one single developer removes line by line of a code snippet carefully. And you do not need dozens of developers to maintain a ROM…
OFF Topic
My view of business is a contract, but ‘having to’ or ‘should’ are not a part of that, well not in the UK.
The idea is that the vendor will do their best to fulfil their part of the contract, and can be held accountable if they do not.
What contract do you have with Fairphone that they have not fulfilled would be more to the point?
There is often an expressed notion that one person should tell another what to do, that’s not business that an attempt to apply authoritarian pressure.
You want authority then the courts will weight what is reasonable, they may then use the word ‘should’ though I doubt it, but the courts do have the authority to enforce their will
I’m not so sure about that… Apple certainly does a good job supporting their devices for a long period. But even Google didn’t want to try that, until now since they have their own SoC now. Fairphone is doing the impossible already. Let’s appreciate that and focus on solutions. Like e.g. advocate for the beta tester community, so that we can make sure issues like these won’t happen that easily anymore.
Just to be clear, we are discussing hotfixes…
But I am also affected by both problems:
This update really has some bad problems!
@formerFP.Com.Manager Please release a fix for both problems!
Is any date for an update assessable. These issuses are nerve-racking day by day -.-
No real date, but it is supposed to be in the next regular update, which normally should appear in the next days.
unknown caller + zero brightness +
Cant answer Phonecalls when Keylocked
Welcome to the Fairphone community.
Could you please explain in detail, when and how the problem occurs? With my FP3 it works, when the phone is locked.
Phone rings, display stays dark
Side buttons=reject
Swiping=no effect
Works perfectly with my phone. You are swiping up?
If you have zero brightness in the day then yes you can’t react with the screen. I had a similar issue and had to remove the battery as i couldn’t tell if I could even switch the phone off.
But zero brightness doesn’t mean the screen is switched off, so it should react.
It was so dark, maybe my sunglasses didn’t help
@formerFP.Com.Manager Please forward to the appropriate person(s) that customers are unsatisfied with this testing and have the impression that fairphone either detectes issues but does fail to communicate them effectively to customers, or that these tests are not sufficient to detect even widespread & considerable issues like unexpected loss of all local contacts or dysfunctional display of calling number (this forum thread). Please also add customers’ solution suggestions, e.g.
You’re asking a lot, but you never know some of it may even happen
Personally, I am not asking much - just to forward a summary consolidating complaints, dissatisfaction reports and suggestions expressed by several users in forum threads I did read in around 2-3 hours. Of course, this is at the one hand a service / support for the fairphone staff, at the other hand, bringing that topic again onto the responsible’s mind makes improvements more likely than not reminding about it - and I’d clearly benefit of improvements, just like all other FP3 + FP4 users.
Also the solution ideas do - after the one-time organisational change - not cause much additional ongoing workload: Adding a link and copy & pasting the DEV’s changelog shall not take more than 5 minutes per update, so once per 3 months. Fairphone staff would use their mobiles as usual - just with the update earlier than customers, and in case that causes too much productivily loss for fairphone, it clearly means same productivily loss for customers in the current process Beta testers do receive an update just earlier - like the carriers already do, so the process does exist and considering the sheer amount of carriers the process shall already be massively automated so extending it by beta testers shall only cause minimal additional workload.
As a side note, the measurements are not unusual: An easily accessible changelog, not only naming 2-3 highlighs but more detailed what was touched and naming possibly breaking changes / incompatibilities, as well as internal testing and tests on external/customers explicit test systems (often in context of “early access”) are good practice in software industry, e.g. for “big” software like operating systems or integration engines, but also small software teams, see release notes of e.g. Locus maps or KeePass, and also hardware-bound software like Fritz!OS updates. All of these examples are not that much different from Android for Fairphones.
Sounds like you could have an involved chat with support@fairphone dot com