I mean… just how? HOW?
And did you already reboot? Such things can happen. And if its no 1 time occurrence contact Fairphone.
It’s a second time occourance. But the first time it happened, I was near a charger, and plugging in and unplugging fixed it. This time I fixed it with a reboot.
1 Like
On a complete side note …
… highly artistic photography, chapeau ! 
6 Likes
Thank you thank you <3
Per FP5 considered itself to be charging with no device connected, reported to https://support.fairphone.com/hc/en-us/requests/1205151. Have you made a ticket, @Nabalazs? If not, it’s worth doing, since they consider the amount of tickets to indicate the prevalence of the issue.
1 Like
Allright, update time.
Not from support. But just the consequences of this bug.
Months ago I reported that the touch screen sensitivity and general touch response turns weird sometimes, when the phone is plugged in to charge.
I just experienced the same sort of weirdness, while I wasn’t even charging. Except the phone thinks it is charging!
So this just helps confirm my theory that this has nothing to do with faulty contacts or grounding issues. There’s just some dumb software error that changes the touch behaviour when the phone THINKS it’s charging.
Oh also, this time I had to reboot to fix it, because unplugging the cable did not make the phone stop thinking it’s charging.
Did you capture logs, I guess thats the best way to see whats going as like with this bug , there seem to be very few people facing this…
While I see the BT bug as well and this behaviour ,
so far I did not see the phone stuck in charging mode while not charging
2 Likes
I’ve seen this today for the first time. In the battery settings it showed something like “until 20:12” (I’m making up the exact time), there it didn’t tell me it was charging, but the icon on top definitely showed that. Will keep an eye on it.
1 Like
I do have the same issue. More frequently recently.
Also, when I plug it in “while it thinks it’s charging” it does not charge in reality.
It is really annoying.
@Nabalazs have you contacted Fairphone for this?
I did not. It happens so randomly and rarely. I don’t wanna open a ticket unless I can at least nail down a consistent cause for the issue.
I just had my ticket closed due to that.
Case and point, then. Quite a terrible situation to be in.
At this point I’m wondering if we’d have more luck reporting these rare anomalies in the AOSP developer spaces. Or to Qualcomm.
How do you even approach this as an average joe user?
1 Like
@Nabalazs, I’ve tried shoehorning such things into other issues a few times, but the Google developers aren’t stupid, so they usually close or ignore it if it’s not an issue with AOSP. Unless it’s egregious, they shan’t even bother contacting the device vendor most of the time. As much as it’s frustrating that Fairphone has closed their GitLab instance(s), I don’t think misusing Google’s shall do us any good. The sole method of contact appears to be FP’s ZenDesk instance.
As with most proprietary software, it’s infeasible for all except the technically competent.
1 Like