[Fairphone 1] Fisher_AZ:
[MENTION=1656095]benxda[/MENTION]: Yes, it has been amazingly quiet here since the Chestnut update has been released, hasn't it ?

But usually no news is good news, no ?

My experiences with the update process: it went fine, but only after I managed to get it started in the first place. When I first hit the "Install the new version" button, nothing happened. At first I thought the battery wasn't charged enough, but even with a full charge it did nothing. I then read that this is known to happen with the Fairphone Updater (cfr. https://fairphone.zendesk.com/hc/co...run-the-update-whereas-all-conditions-seem-OK). Taking the best advice from that thread, I repeatedly kept hitting the button and after some 20 or 30 times the update finally started. After that things went smooth. So the update worked, but it wasn't the ideal user experience. It is impossible to guess whether this problem is within the Updater software or rather some server-side problem, but it seems like the Updater could still use some improvements. If at least to give some meaningful error messages, because now the user is left clueless.

I can't say much about my experience with Chestnut itself, because at the moment I'm not using my Fairphone very much yet (for personal reasons unrelated to the Fairphone itself) - I'm hoping to making the Fairphone my main phone really soon now. But from the limited things I have done with it so far, Chestnut seems to work just fine.

It's good to hear you are working on this. I will be very patient and not ask any additional questions until you have published the Q&A ;)

But I would like to offer 2 points for your consideration:

1. I would propose that whatever solution you come up with, you allow for a considerable amount of time for users to give feedback, prior to a final release. This feedback could be based on theory (a detailed description of how the unification/re-partitioning will work) or practice (some kind of beta release). I think this "beta period" is essential to make sure that whatever solution you come up with corresponds with actual user needs and/or expectations. I will already give mine in point 2.

2. For me, it is paramount that the unification/repartitioning is optional. Even if you find a way to do this without any data loss (and if so, big kudos to Fairphone/Kwame/Guohong, because that ain't technically simple), I'm not inclined to use it myself. As I explained in a previous post, I (and as [MENTION=1656095]benxda[/MENTION] has pointed out, many others) have already solved this matter earlier, so have no reason to run even the slightest risk of things going wrong with your solution. For the repartitioning to be optional, the Updater needs to include some kind of dialog screen ("Do you want to unify/repartition your storage at this moment" ?) or - even better - to make it a separate download altogether. If on the other hand the repartitioning tool will be included automatically and without opt-out in a future update, those of us who really don't want/need to unify/repartion may be forced to decline all or some future software updates.

On a final note, I just would like to state that I hope this post (and all my previous) will be read in the spirit of constructive criticism they were meant in. I am still a big supporter of the Fairphone project, hoping it will get better still. The past few weeks have certainly seen a lot of good things coming from Fairphone, which makes me really optimistic. Among which: I really like how the website is evolving: cleaner with better structure, and better use of screen space by removing the big fixed header & other improvements. The planned replacement of ZenDesk with more powerful forum software is also a really good idea. Keep up the good work !!

Also: best of luck with the sale of the 2nd batch !!

"4,773 of 35,000 Fairphones sold" Not bad after just 2 days ;)