This is great! Can’t wait to receive my Fairphone 4. This gives me more confidence in the QA you’re doing. Also thanks for providing the background, with that it makes the long wait for users justified. And good to know you’re working on an improved method to manage these roll outs.
Thank you for clarifying, but can I ask why it took the company more than a month to take the time to give us these clarifications? You certainly lost me as a future customer, and I am probably not the only one… and I am more sad than mad about this, belive me.
Well, i am not that disappointed and do think that my fp3 is the best phone i had so far considering all aspects, but i would rather like to see a quick and easy solution to revert back to the last release next time.
@rae Could you maybe in future releases implement an easy way to switch back to the last version via another slot if the update is somehow broken? Something like “reset device” which is already there?
There would be no problem if there was a detailed changelog.
But even lacking detailed info, I still imagine users would know what to expect with the OS version used before on their phones, as they used the former version for a while afterall.
Since it’s a user’s decision to update or not to update, it should be a possible user decision to roll back an update, too.
The procedure to roll back is there anyway, it just has to be made sure that it works for a start.
Sorry if I have misunderstood, the lowest setting now is not something useful for you? On my side I use it only at night but it is such an improvement for me. But I agree that adaptative brightness is broken. I disabled it.
Honestly if updating my FP3 means having the minimum brightness to be as it was before this update, I think I will simply not update my phone. And I am pretty obsessive about installing updates! It is that important for me
when will the Update happen? We have already initiated legal steps
against Vodafone here in Germany, as they say it’s a technical problem
on their side, but haven’t given any details on how fast they will
resolve the Caller ID issue. It’s more then a pain in the back - I use
the GMS for home office, so without the Caller ID the CTI software
You understood me correctly I never had an issue with the lowest brightness setting.
So what happened for me was that the adaptive brightness came in too soon. i.e. the sensor read zero when there was enough ambient light to read and then set the screen to minimum brightness. Then the so called AI function didn’t learn. So I’ve just disabled adaptive and the phone is more usable in that sense.
Hopefully if it’s only the adaptive part Fairphone are rolling back and not level then all should be OK
I suppose all you have to do is to watch this forum before you decide. I will definitely be updating on the changes.
Your question would be better directed to Vodafone, not that they may answer.
Fairphone update the A10
Fairphone do over 500,000 test to get an updated Android certificate
The update is send to the major Networks (Vodafone, EE, O2 etc)
Once each network confirms it’s OK it is released via the networks push notification
What doesn’t happen, which is quite often is that the networks don’t check with each of their carriers. If there’s protocol updated to Vodafone that hasn’t been passed to a carrier, something may break ~ like the caller ID. For me it was the carrier name ~ no big deal.
Fairphoners tell Faiphone
Fairphone collate and confirm there is a ‘ladybird’ in the works
Fairphone tell Vodaphone, maybe six weeks ago
Vodafone look at it and do tests
Vodafone confirm and tell Fairphone they have found the problem
Fairphone get the new info maybe 5 weeks ago
Fairphone prepare a new update
Two months later maybe we get the update.
That’s just my pennies worth.
Where’s the bovine manure you keep stepping in. It seems all vegan, kosher and halal from here
Thanks, as always, for the feedback and for proposing alternative solutions.
To answer @AnotherElk’s question about whether switching the A/B slot back to the OS state prior to the update could be made a part of internal testing. This is not a possible solution and is in fact, not recommended by Google because it might cause data loss. We also have Verified Boot installed which includes rollback protection. This is a protective measure that records the most recent version of the Android and refuses to boot Android if it’s lower than the recorded version.
Hope that clears it up a little! If there are further questions, of course feel free to give me a shout too.