Search: Often only half of the screen used

Fairphone 3 with Android 10 stock build 8901.3.A.0136

"often but not always" - that's unfortunately a problem because it is impossible to simulate issues that occur random only - therefore, it's impossible to fix them.

🙁

As it's not the first time I read "shall not happen but we can't fix it", adding a debug log function seems like a reasonable idea. After all, Locus 4 was boldly announced as a big step in UX compared to Locus 3, but in my practical usage experience, it does not feel as UX improvement – which is sad, as you invested a lot of energy in improved concepts etc. and also seem to invest quite some time to reproduce the many bugs but often can't, so it's a lose-lose-situation 🙁

Georg, sorry for the inconvenience and I understand your frustration but programming an app for Android isn't that simple. Each phone has its own "glitches", its own solutions, add-ons to the original operating system. And there are thousands of them. And not everything is written in system log... You are the only one to report this kind of bug. Nevertheless, we finally managed to find a possible cause of it and fixed it. So please wait for the next app version.

Thank you 🙂 I'll try after updating.

Exactly because as a programmer I can estimate how challenging it is to cope with so many side effects creating huge amount of variances, I wanted to give as brain food something like debug log, flight recorder or the like so that you can better understand the situation on a user's device – and thus have higher chances to quickly reproduce/simulate or narrow down to an analyzable piece of source code. I hoped it may be a vehicle to make life easier on both sides, you developers and us users 🙂