Right. Could come any month now…
Yes, I was in the process of figuring out if I could get a refund and after a couple of emails back and forward they replied that they found the root cause and that it will be fixed within 1-2 months!
How can the option to use the thermal-engine.conf be set up?
Actually I don’t know the specific values because it depends on how it has been configured in the ROM or by the vendor (Qualcomm probably).
This is an example but it’s for a Xiaomi device, so I don’t know if it works.
thresholds 36000 37000 38000 39000 40000 41000 42000 43000
thresholds_clr 35000 36000 37000 38000 39000 40000 41000 42000
actions battery battery battery battery battery battery battery battery
action_info 1 2 3 4 5 6 8 9
Probably it’s the LCD_MONITOR_STATE that here has a treshold of 60.0C° and actions could be what it does when the treshold it’s reached.
But again, I don’t know what it does with actions lcd and action_info 3685.
Neither did I get an answer. I’m on holiday at the beach now. Fph4 is useless in this bright sunshine. I regret every day to have bought this awful brik.
I’m hoping for the patch to hit beta next week. Hopefully it will fix this.
Luckily I live in a country where Summer is 1 month long and that has now passed so this is no longer an issue for me.
I also didn’t get the answer that it will be resolved soon. If we have to wait 1 or 2 months, summer will be over. Good timing Fairphone support (NOT).
the day I bought the pf4 I read their ads. that you can fix your smartphone yourself. just need to buy a screwdriver.
niedz., 13 sie 2023, 21:41 użytkownik IT Hero via Fairphone Community Forum <firstname.lastname@example.org> napisał:
In fairness, if you want to fix this software issue yourself, you can: fairphone lets you unlock your bootloader, and you can root the phone and have a crack at it. It’s not for the faint hearted or the uninitiated, and you’ll have to reapply your fix after each official OTA update, so it’s a real uphill battle. But at least it’s doable. That sure beats other manufacturers that plain lock you out of the bootloader completely.
I’ve been using the fairphone in light mode (not dark) and it helps somewhat, you can guess/read some of the information more easily than in dark mode.
Just wanted to share while we frustratingly wait for the fix.
A new beta update just dropped. This issue isn’t mentioned at all.
I just asked FP, using my support ticket thread why I have not gotten any update like someone reported having gotten.
And why there is no mention of this fix in the recently published beta.
I so want to believe FP is actually ethical. Not only on paper
There are vague rumors (that’s the best we can call them) that Fairphone might have, eventually, perhaps, found a solution to the problem.
According to the same rumors, a fix is forthcoming “soon”, and here the rumors diverge: One says “in the next patch”, and another says “in a 1-2 months”.
(Obviously in “1-2 months” the problem should more or less fix itself, since temperatures will (most likely) drop, and people will spend less time in bright sunshine (where still available).)
So it could very well turn out the same way as the proximity sensor issue. It will be considered “fixed” because it’s not happening anymore, and we’ll deal with it again next summer. That’s just great. I’m seriously considering selling the phone and finally buying something that actually works. Even at a loss.
Hi guys, I’m over with this problem. Especially cause I use my phone also for working. Do you know if they give you a refund? I bought it more than one year ago
They won’t refund you after a year. Your best bet is to sell it.
If you make a new thread on this forum, you might have a potential buyer on here. Otherwise, there’s always Facebook Marketplace.
I don’t buy the ethical socio-green-washing myself. I bought my Fairphone half for the repairability and half for the unlockable bootloader.
Seeing as though Fairphone might turn out to be rather flaky and/or possibly on the brink of tanking (I’ve been around long enough in this industry to know the signs… Sorry guys but it donẗ smell good) I’ve stocked up on parts that are likely to break in my almost-new Fairphone 4. And I’ve preemptively unlocked my bootloader again in case Fairphone’s website goes silent.
With my little war chest and the modular design of the phone, and the unlocked bootloader, I should be good to go for a few years to come even if Fairphone goes belly up tomorrow. And since I live in a generally frigid country, the screen dimming bug doesn’t affect me too badly.
So I’m a happy camper personally. But that’s just me.
Hey all, I just want to clear up the question about when this will be fixed. We had some final kinks to iron out, and unfortunately we didn’t meet the cutoff for the next update (after the one that will come out later today).
The good news is that the fix is confirmed and will be included in the October update. I know that timeline is a bit disappointing. We have to finalize the software before it goes out for approval by Google and numerous partners so we’re limited in how quickly we can make changes.
I’ll update the tickets as soon as I can.
I just got a support ticket response from Lesley (official FP employee) stating that FP has not found a root cause yet. Yet here I read something else entirely.
Can you please clarify this discrepancy and also make sure that support tickets use the same data you are using to inform customers?
Thanks for flagging this. The details from my previous comment are correct and the same will be shared in any future ticket replies. Existing tickets will receive an update/clarification shortly.