I get your reasoning about the issue.
But support are suggesting a path forward, and you decide not to take it, and support isn’t really helpful? Good going .
Software issues are not always about logic and reason. Software development is a mess which makes early prototypes into market-ready products by declaring them as such and later rather puts multiple layers of plaster on cracks in the foundations (software developers will rightfully argue that mostly not software developers will do this, but marketing departments and decision makers).
It’s not an industry producing predictable results based on sound principles and techniques. The principles and techniques are there, but they are not followed and used to ultimately meaningful effect, because there’s no reason to. The quick-and-dirty approach saves time and money, the products sell nonetheless and nobody’s getting held accountable for conceptual inadequacy, so the system is broken and will not get better any time soon.
Just my two cents.
Long story short: There can be unpredictable, erratic and plain illogical behaviour in software, even more probably so in a conglomerate of multiple complex components forming an OS.
You will not get far operating on the requirement that it all has to make sense .
If no App immediately turns out to be the culprit, a factory reset will be a sound way forward.
I’m a software developer myself for more than 12 years. I’ve done embedded software as well so I’m aware of those things.
A software reset might help me (but also cause a lot of work to restore all the settings etc) but it would not help fairphone to find the actual cause of the problem which more people seem to have.
It’s typical first level support like “try turning it on or off”. I would prefer to have the actual bug solved, not a workaround that causes me a lot of work.
So I’m not going to bother with the support any more unless I have a hardware issue. Maybe when they have a large enough amount of customer complaints they will actually investigate and fix the bug.
I can live with the issue, it’s just an annoyance. Until then I just hope that either I myself or someone here on the forum stumbles upon a solution or that fairphone comes up with a software update that fixes the issue.
Hej, I’ve been getting the same problem for some month now.
It was at start not too painful, from 1 to 2 seconds to open up and it didn’t occur all the time. Recently it’s been getting worse to the point that i needed to wait up to 10seconds to light the screen up, and if the phone was fully turned off, it once took almost 1 HOUR to turn on… I’m not exagering the number.
BUT, I’ve manage (I think) to fix it. I’ve tried to press the screen at the junction where the screen is linked to the rest of the phone and it seriously just magicaly turned on.
So after screwing at full capacity every screws of the phone, it works as it did before. Not a second of waiting time.
So if anyone is having this problem today, feel free to try. Tho I don’t know how good it is to screw that hard the screws in the phone. Maybe it has to be like that, maybe not, but it worked for me.
However apart from the aforementioned factory reset, which is a last resort before sending a phone to ‘support’ there is an option to start in safe mode rather than a factory reset. This keeps all personal data and app data from the default apps.
question to everyone who had this issue: did you have an SD card installed?
I’m having the same issue, and just found an FP2 issue that was solved by removing the SD card. I did that and for the last 10 minutes it didn’t show this issue yet. now I’m wondering whether all this delay issues might be caused by broken/misconfigured SD cards… or whether some users had this issue without an SD card installed, so my theory is proven wrong.
btw, it has to be a driver/firmware issue or a mainboard malfunction in my case:
installing a custom rom (/e/ in my case) didn’t help.
and when switching the mainboard from my FP3 to my sister’s FP3 , the issue goes with it. (I always also switched the sd card)