I sent a Help Ticket directly to FP and despite my offering a Phone ID and everything all they said is I must prove I bought this Phone.
Which ist irrelevant since this is an Update Error. Even if I demand an exchange of phones at Vodafone the new Phone has the same Software so this is of no value.
As of now I can use my other Card. However I do expect a timely Bug fix since either having 4g deactivated or No Caller ID, which ist clearly a malfunction of my Phone, makes it useless for me.
Fairphone don’t know that and you may have noticed on this topic it seems to be a Vodafone issue. Mind you if you exchange the phone at Vodafone you may get one without the new update ~ that may work for you.
Yes timely is of the essence but when is more of issue.
So have you only just bought the phone? Still this is not a hardware issue.
From my understanding Vodafone had to OK the update before they sent it out, so the it seems better to ask Vodafone why they released it. But I also note from above, somewhere it’s not all Vodafone but may be related to a specific provider that uses Vodafone.
For example after an update I had the incorrect network name popping up T-Mobile not EE as I would have expected. EE and T-mobile sorted out the issue not Fairphone. I imagine the networks just didn’t account for naming issues when they checked the update. It may just have gone to the main Vodafone check in and they said, yes it seems to work, pass it on the downstream carriers for the users.
Did anybody who knows how to do it and with confidence in their data backup already try to switch the OS slot back to the state before the update?
Being with Vodafone Germany wouldn’t be required.
(I’m not using Fairphone OS currently, so I can’t check whether the prior OS version would boot successfully. )
I have the same problem, I reset my fairphone several times and tried first with restore, then without, the error “unknown” persists.
I lost some important datas because of this.
When I insert my cards into an other phone everything works fine, so I suggest it is not a vodafone problem, but a fairphone one.
It’s the combination of sending an update to Vodafone to verify all is OK and then Vodafone releasing it without enough checks.
Other phones will have other updates which either may be older or suited Vodafone better.
It’s more to do with actual provider than either Fairphone or Vodafone. However if Vodafone don’t provide enough details to Faiphone on the providers ID then the phone cannot recall the callers details from the provider ~ sort of ???
Well maybe they do maybe they don’t. I didn’t say they didn’t and I can’t imagine how you would know they did.
Information provided for a particular algorithm isn’t necessarily compatible with all adaptations of an update.
As I mentioned I had similar misrepresentation of the carrier name, but it was resolved. The coding was for T-Mobile but had been changed between updates, so my EE read T-Mobile which held the carrier ID.
It would appear Fairphone were not told this prior to the update and T-Mobile didn’t check the update and passed it on to EE. So EE pushed an update designed for T-Mobile.
No big deal but annoying to look at and did get me wondering what was going on.
Hardly surprising that big companies don’t communicate with Fairphone in the same way they may with Samsung, and Fairphone don’t have the weight to push the big companies to check their updates thoroughly else it would have been spotted.
All total speculation, imagination and such from me obviously, but not without reason.
However you will see there that my concern is that the Ambient Light Sensor doesn’t record the LUX properly.
If the sensor isn’t calibrated correctly then the Adaptive brightness will cut in at high levels of LUX irrespective of the settings referred to.
Here’s hoping I’m wrong
Still as Rae has acknowledged the topic dedicated to this ‘light’ issue it would seem more convenient, for Fiarphone’s support team ~ maybe to have all extra info on this issue in that topic.
To those affected by the brightness issue, myself included, I wanted to share what I hope is common knowledge: you can adjust brightness quickly by swiping down twice from the top of the screen. Personally this is an OK workaround for me, but I understand it may not work for everyone.
Yes that’s what I was doing but then I was out in bright light and couldn’t see anything on the screen until I had removed the battery to force a reset, I couldn’t even turn the phone on and off by the buttons, though the later may be a separate issue unrelated to the update anomalies.
Sounds to me as though the algorithm for adjusting according to ambient light was originally designed to take into account the fact that (at that time) the minimum brightness (lowest value of the scale) was still quite visible. Now that the lowest value has, it seems, been lowered to almost zero, the algorithm needs to be corrected to take that into account, by no longer bringing the brightness down quite so much.
I would class this as a regression bug, since the relationship between the algorithm and the brightness scale should have been checked, when changing the scale in this patch.
The issue I have discovered is that the Ambient light sensor does not respond to low light, so the algorithm thinks there is no light.
I.e it looks more like a sensor calibration issue that’s feeding poor data to the algorithm.
But please add to the specific topic on this as Fairphone are following that for this specific issue and this topic is more general notes of the update.
Hey,
Since the last update, I can no longer use my Garmin GPS as an external storage linked to my FP3+…
I also tried with a simple USB key, and it does not work either.
Has anyone experienced the same ?
Same in my case since the last update (……805):
I have the same issue concerning the brightness, which goes to zero unexpectedly, especially during the evening. Now I have turned off the automatic brightness. My provider is O2.
Last week I had contacted the FP-Support, and they recommended sending my FP3 to the centre in France for analysis. For now, I have rejected this option as I need the FP3 for work.
I hope these problems with the new update will be solved soon.
. Anyway, until not it’s not even sure, that the fault is on Fairphones side, as so far only one provider in Germany is affected.