a) I would like to second Paul’s first suggestion to include module disassembly in the CALLS section before users are advised to request a replacement module. Disassembly should follow this screen if the chosen answer is “No”:
So it says that if the proximity sensor is reporting the correct values, then the proximity sensor is not working correctly. If that’s the right conclusion, then I guess I am not the only person who felt confused. It might still be the right conclusion.
a) disassembly instructions added;
b) mention of the pictures corrected;
b1) when you confirm that the proximity sensor is reporting the correct values the next step is to recalibrate it again. It’s done so that you go back to that step, however the instructions become contradictory. I’ll adjust this.
The troubleshooting tool is now finished!
We’ve listed the most common symptoms with which users come to us asking for support.
We invite you to have a look at the new symptoms and troubleshooting instructions. Please, give us any feedback you consider useful (typos, incongruences, anything missing or redundant…).
Note: we are still working on the possibility to have some details automatically filled in the contact form, when the user submits a support request.
Is replacing reboot-causing slim cases without mentioning the button-switch-fix that afaik works every time really a good idea?
Why is there no option for Linux computers in Connectivity > Connecting to a computer?
Q: What problem do you have? A: Buttons Q: Does removing the back cover solve it? A: No -> Core module will be replaced. That sounds like a quick shot to me. At least I’d ask for a more detailed description in the support request than “Troubleshooting instructions diagnosed the buttons of the core module to be defective.” to avoid replacing working core modules out of misunderstandings e.g. menu/back/home softbutton-issues or “install” button not clickable while screen overlay is active.
In general I think a short problem description instead or additionally to the standard “Let’s see step-by-step how we can help you troubleshooting this problem.” would help to make sure you are at the right place within the tool and to avoid misunderstandings.
Is replacing reboot-causing slim cases without mentioning the button-switch-fix that afaik works every time really a good idea?
Maybe Fairphone is still looking for samples of cases that trigger the reboots?
And well, I think while the button-switch-fix is a reliable help, it’s not an ideal solution. I think there is a reason why the power button and the camera button have completely different surfaces. Apart from that, I seem to remember that some folks reported the power button did not work reliably as a camera button.
I noticed the troubleshooting pages on the proximity sensor don’t show any images. Since these pages are meant to help people solve their problems step-by-step, this could be somewhat disturbing for those who are not used to open their phone or use sensor-testing apps…
The pictures seem to be available in other troubleshooting guides, so I don’t really understand what the problem could be.
Display -> screen scrolls or opens apps by itself -> No (removing screen didn’t help) -> No (updating didn’t help) ->
Now it ends with the touch and hold workaround and only the options to go back or restart. What if the workaround also didn’t help? I’m especially thinking about a screen failure (my water damaged screen has an extreme version this issue) and a static/battery issue.
In many places, the Troubleshooting Tool includes this video on module replacement that still includes the removal of an old regular case. I think this is a problem given that many FP2 users keep asking how to remove their slim case. This video might mislead them into applying a lot of force into a wrong method.
Thanks for spotting. For now we’ll need to leave it. We don’t have another similar video where we use a Slim cover.
However I’ll raise this internally to have a new video made featuring a Slim cover. In the mean time, I’ll also add a video with instructions on how to swap a regular case with the slim one. Hopefully users will find this when needed.
Please add the required photo here (maybe it’s just a broken link):
Calls -> My display stays black … -> No -> Clean your display photo not displayed here
I think the photo is really indispensable here because to me it is not completely clear whether to clean the actual sensor itself or just the inside of the protective glass cover (in the display module).
I also don’t see it. I see a small framed square and when I right click it I can choose “reload image”, but nothing happens. If I choose “show image” or “copy image location” I get: https://fairphone.zendesk.com/hc/en-us/article_attachments/203706656/Exploded_view.jpg, but that just redirects to the main support page.
Clearing the cache didn’t help.
I’m on Ubuntu with Firefox 59.0.2.
I just tried it with Firefox, Safari, Chrome and Opera on my Mac (desktop) and with Firefox on Windows 10 (tablet PC). The picture does not show in any of these.
Maybe the picture is set to be shown just in your Fairphone intranet?
Anyway, I know now that it’s the glass that is meant to be cleaned, not the sensor itself.
Judging by the “signing?” part of that URL it seems to require to be logged in, thus confirming the assumption by @urs_lesse that it’s accessibility is limited to the “intranet” only.
