Sorry, but this comment is absolutely unneccessary.
As suggested, a public bug tracker similar to the one which existed for the FP 2 would be nice, so one can always check there before submitting an issue. This would also make the process more transparent. One coould see what is already being worked on or what may take more time or even what will be treated as “won’t fix” including an explanation why certain things have to be as they are (for example why the supplied camera app of Fairphone 4 is hardcoded to use Google Photos and won’t work with any other gallery app - maybe this is a requirement by Google if the camera is based on code provided by Google, but I don’t know and the support can’t tell me either).
Yes, I am aware that maintaining such a thing needs time - but just using a public repository on Gitlab or Github to collect user reports about bugs and feature requests would change a lot.
And yes, I am also aware that this topic was already discussued many times. But telling people they are “spoilt children” because they like to know what is going on, does not really help either.
I was going to edit after your critique but wanted to understand better before I do.
Is it
a) I should not criticise the frequent and general demand that users want Fairphone to communicate more
b) That I shouldn’t emphasise it by comparing to ‘children’ or
c) You think that is an unfair observation of children
I understand how you can see it is not helpful but this is a topic about communicating with users, not a [Help] topic. Also this topic is not not directed to Fairphone but but a peer to peer opinion.
I’m sure also that I fall into that category of people that expect a lot of or to some, too much attention, so I speak for and about myself too.
and the referred to comment I made in that topic
This forum deals mostly with functions of the Fairphone, but a lot is just complaining about Fairphone and some is for for emotional support to users. The later is difficult to judge as to whether indulge or cut off.
Either way I’m happy to cut out. I’ll wait to see if there’s a response that seems to warrant a reply and then I’ll mute this topic.
It is, that you are insulting people by calling them ‘spoiled children’.
For a native english speaker it might possibly sound different, but for me, that is nasty. It implies, that the request for a more explicit communication about bugs that are addressed or not addressed is an inappropriate wish.
When I ran a support team, we supported big customers with different support level contracts. Some had premium contracts that required us to respond within 1 hour and come up with a fix in 6 hours. We literally updated them every 30 minutes, even just to say “we’re on it”.
The lowest level contract required a reply within 3 hours and a fix within 3 days. We updated them every day.
It’s human psychology: people like to know their stuff is being worked on. It’s supremely important for customer satisfaction. The one thing that’s guaranteed to hurt customer satisfaction is lack of communication: people hate companies that don’t talk to them, or talk to them only when asked. Even if the talking is done by a cron job sending an automated email at a fixed time, that’s enough for people to think “Nice! These guys aren’t forgetting me,”
In this case, Fairphone is dealing with issues that affect everybody (bugs) not individual cases. What I would do is simply maintain a list of open bugs and have someone update the status every week. You know, a simple text file with entries like “This-or-that bug: under investigation, likely cause Acme driver - Jul 10, 2023”.
Every week, I’d go around in the Monday meeting and update the text file (with an actual update, not just changing the dates, else people will notice and get mad ). It really shouldn’t take more than a minute per line, and probably less than that.
Lol why are you constantly defending their inability?
It’s really a shame how Fairphone treats their customers, but there are still people who defend them for whatever reason.
I’m willing to cut a lot of slack to any company, all too rare these days, that goes against the anti-right-to-repair tidalwave and the fascist Google surveillance society. I personally believe both fights have long been lost already, but the few who still resist get a free pass from me.
And this specific topic is about “Communicating with the users”. If you don’t want to discuss this, then just ignore this topic. And yes, one can also discuss how Fairphone may improve communication with their customers. If you believe it makes no sense to discuss that here because Fairphone will not have a look into discussion here anway than all discussions here are completeley useless since users will not build new devices and mobile device manufacturers will likely never read the discussions here anyway.
Where was this documented? I only found speculations in the forum that overheating may be a reason for the screen getting dimmed to cool down the device - but no definitive statetment by Fairphone. Or did I miss anything?
Again a good reason to have a kind of public bugtracker where this could be found easily and not by searching the whole user forum.
just a bit unrealistic if not in business-business context. There is always a big difference in support to normal privat 1 man customer compared to business customer. Not saying this is how I would whish it to be, still its how it is.
Well - this would be perfect example for a bugtracker to let people know that Fairphone is aware of this issue and what possible solutions may be implemented in the future.
What ever they come up with, its never enough, there is always “yes, but I want…”
Be it an explanation of the job description of the community moderator or a way to try to be more transparent (and yes there I also put some critics) or whatever. so somehow a game you can never win.
I haven’t tried it, but I assume Google Pay doesn’t work in anything but the full blown Google spyware stack, and certainly not with MicroG, right?
I pay with an NFC implant, so I never need a cellphone (or a wallet). But infrequently I use iCard pay, which works pretty much exactly like Google pay, only it’s not Google, and the iCard client works fine in CalyxOS.
