Which I did NOT YET install
because (a) I was not willing to let my Fon get fucked up while I was on a festival tour, and (b) I wanted to wait and see which problems actually show up after release, e.g. here;
By now I would trust the “4.A.0013.4”.
Now there is already an update “4.A.0016.6”
When I go to settings>system>advanced>Systemupdate
however, I am only offered the “4.A.0016.6” - and not both, nor the “4.A.0013.4” anymore.
(1) how to solve this one case?
(2) make it better (clearer, choosable, …) please, in the future.
No, the last update is not fine. It breaks Bluetooth and NFC capabilities, it breaks something with the camera (no slow-mode anymore). The last update is a simple team event of how not to develope and do quality control.
There is a topic that includes a download link for 4.A.0013.4, but that would be a fastboot installation from a computer to your FP3, and frankly I am out of the loop right now how that exactly works and how it affects existing data on your phone. The file can not be just downloaded to the phone and be installed from there – that will just not work.
There is no way to install a version other than the most recent one OTA.
P.S.: I’m just noticing Fairphone also currently offers the penultimate update 4.A.0013.4 for manual installation (fastboot):
It’s not even technically correct, because it’s potentially misleading. I’d prefer to stay with the version, the Opener has over the new version every time, since that new version is simply buggy. No way of putting it nice. At least a warning would be appropriate before telling someone that updating to the newest version is safe. Simply, because the update-process might work, the consequences of that update are nevertheless shit. Why not giving that hint in your answer?
However, thank you @urs_lesse, for the link. It would be now of interest if updating to 13.4 has the same issues as downgrading from 16 to 13.4, especially losing all data.
Well apart from you rude tone and words, the reason is I’ve never had a serious issue with an update so I am not in a possion to sya what will have to another.
However out of the maybe 200,000 users this forum does record well less than 1% who have a problem. Maybe you are one of those and you are free to explain your problems but that is not a warning just your experience.
There’s always some small inconvenience for most I image, like ambient display brightness but that all the issues I have and it seems to come and go with various undates. It gets a mention from me when it happens but that’s it.
On updating, it has been explained above. That is if you do a manual install. An OTA is safe.
(How sure (in percent) are you, @amoun, that you are right with your answers?)
The 0016 says “Update size: 98.46 MB”.
The older one, 0013, had an “Update size: 303.62 MB”.
So naively, I would assume that 0016 changes less than the 0013 did. Right?
After then having done the 0016, would the new system notice, that 0013 still has NOT been done yet? Probably THIS is the most important question here, and a possible implicit feature request for a better future solution to issues like this?
Why no good reason?
The 0016 updates much less (in MB) than the 0013 would have updated - right?
For now, I will refuse to install ANY update, until there is a SIMPLE way to first install 0013.
BUT: The person who is going to inherit my FP3 is NOT a technical person, and if the first thing she encounters is a broken update system where she always has to say “NO PLEASE NO UPDATES” whenever an (increasingly escalating) update demand pops up …
… she will likely have a very bad first impression of FAIRPHONE in general.
So, please find a quick solution, even if it is a quick’n’dirty solution.
This forum here exists for a reason though, and I am always / often checking first whether other users have had issues with the latest update - before I let that update overwrite my ususally perfectly working previous state.
If my phone had been working just fine before, then upgrading the basic system software is always a risk. Right?
The issue that this thread here points to is a different one though:
How to still install an older update when already there is a newer update?
A better, future Fairphone needs a solution for that simple problem.
No option for me. Not gonna unlock the bootloader, just to fix a problem in the basic update delivery process.
Please find a different GOOD solution, for example:
a >300 MB new update 4.A.0017 (which makes all prior updates obsolete) ASAP
not gonna pass on a phone with an unlocked bootloader, no.
That is so untrue, and it’s such a malicious distortion of what I had really said … that I am actually wondering what YOUR agenda is in all of this.
Why are you spending much time here, to fight against us users who have reasonable demands, real problems, and most of all: Their valid point of view? Your whole act pretends that your view is superior. It is not. You even misunderstood the very basics of my request here.
Get a life, do something useful, be constructive. Because: You are actually hurting my issue here - because you think you can devalue and contradict my view point.
Instead of wasting my time with you, I would like HELP and IMPROVEMENTS - and not someone unimportant telling me “YOU DO NOT NEED HELP” and “ALL YOUR SUGGESTIONS ARE USELESS”.
I politely ask you to leave this thread, and never come back. Harm other threads please.
To reiterate, and show you how wrong your assessment can sometimes be … I wrote this:
That means … I first check … wait a few days or weeks … and then I do the update.
I never “declined” the update, just postponed it, until I had enough data.
I do now - but now the suboptimal fairphone updating procedure … blocks me from updating to 0013 (simply because 0016 is in the way). Not my choice, but a bad design of the updating procedure.
I am sending an email to support@ now, for them to have a look at this REAL ISSUE.
You unlock to install a clean 0013.4 if that is what you want, then update to the more recent OS then you can relock the bootloader before you pass it on. ??
It is not a huge problem, you just have to want to do it.
I’m sure you said you chose not to install 0013.4 I’ll re-read to see if I mistaken.
My agenda is to respond to your comments
It seems it was a decisiion you knowing made as it was available. There was no reason to assume it would &^(&^(&^ you up. Not doubt some people found an errant issue, but not critical to the extent you want to swear/sweat about, which is rude given you hadn’t tried and most people don’t seem to have complained. It seems you’ve taken a extremly risk averse view not to update based on a few topics whilst you waited for others to take the risk.
Don’t forget the OS updates also contain security updates which arguable are more likey to cause serious damage to your mental health than maybe an adaptive brightness issue which occured in 0016 not 0013
To be honest: Even if that’s true, with the different descriptions of the issues with the 16-version a warning would still be appropriate. The words you used are not suitable for stating a purely private experience. If it had been your goal to share only your own experience, there would have been words for it, i.e.: “Though throughout the forum some users describe one or more issues with the update, I did not experience one. So, from my perspective, the update might well be save.”
That’s technically an untrue conclusion. You have no statistics on users who experience the mentioned issues but simply not writing those down here. And yes, I experience the massive lack of quality control shown in this update – and I’m not alone. Though there is indeed a hotfix for the NFC-issue, there is no thouroughly tested update available. And yes, that is an issue in itself, too.
That bt-issues is a lot more than an inconvience for me, because I have bound several functions around a working bt-capability. So, you conclude something from your limited private perspective on user behaviour and extrapolate that as general opinion on the significance of the issues with the update. Normally, I’d say, that’s ignorant. And because you set me on that track, alone the fact that issues with the software had been patched and are coming back with a later update, is again a telltale on how quality control at fairphone works.
Not if the updates would be tested thouroughly… it simply makes no sense to install an older version with all the security issues which are patched in an available newer software version.
How can there be a warning when no one has a problem, and when a few do it’s too late for a warning. For example: There was/is an issue with some users connecting to a diabetes ‘monitor’ via NFC.
The devs are not able to test how every device will work with each update and if they had noticed that I’m sure there would be a warning.
Users have discovered
NFC issue with some devices
The Bluetooth with soem devices
The ambient light issue.
I do some of the testing but don’t have a diabetes monitor and the Bluetooth works fine for me. Only issue as mentioned was the ambient light. All of which I have read are fixed with the next release along with security patch Oct 11.
A few people can make a lot of noise especially when everyone else is quiet.
200,000 users is the number sold.
1% is 2000 complaints ~ I don’t think I’ve see 20 so if you think it is untrue then I think you have read wrong. The forum clearly doesn’t have 2000 complainants on this update
Where do you see a conclusion other than I am saying that I note there is always/often some inconvenience.
Regarding the unlocking. That wasn’t directed at you as I have no idea what you want to do.
Although there are errors in many updates, they are only huge to those people you have specific expectations, and as for testing thoroughly that’s a personal value.
This topic is about installing thr 0013 which has been answered.
This, your last post and others are just perifieral to how upset some people get and offer no help in regards to the features and faults therein of the phone. It has become more a hand hold for those who seem very upset and I don’t see I can offer you any more support.
You’re kidding me… I suppose, you look at the timeline, like: When has that topic been opened and when came the first topics regarding issues with the new update. Likely, you find the reports on the issues came first. And then, yes, a warning would have been the correct way. There simply as not been no-one without a problem at the time this topic had been opened.