You need to perform the battery reset as described in the #batteryguide and then let it charge until the LED turns at least yellow (better wait for green).
It will take a long time from blinking red to solid red and then to yellow, but don’t try to boot until then.
If it continues to go back to blinking red on it’s own then your charger, cable, battery, bottom module or core module is defect or you have a connection issue between the modules.
Take them apart, clean the connectors and put everything back in order. If you can move the battery around in it’s place then fill the gaps with folded paper strips, so it sits tightly.
Then try the batteryreset again.
@wytzeschouten if after you charged the battery you get into a bootloop (the app optimization process restarts again and again) then please read this and continue there.
(not sure whether or not i am expected to make a new topic, my excuses if i am thrasing the OP)
I’ve already done the suggested methods over and over again. Except for disassembling the module, will try that this evening but i dont expect much of it.
As said, i dont have a choice too boot my phone or not. The phone boots up without my consent which causes it to go in to deep discharge modus. If i am lucky it does not, i try to turn it off but during the turn off period (with circling circle) it goes in that case back to deep discharge mode.
Looking at the amount of post regarding charging and views on those topics, it is not a cable or charger issue but a Fairphone hard/software issue.
Hi Paul, thanks for your quick answer. Turns out it was enough to have let the device rest (disconnected and terribly empty) for a night.
When I connected the device to the powerbank, it gently started the sequence of (1) blinking red light, (2) Fairphone logo, (3) blue battery recharging screen and then (4) dark screen with permanent red light, then (5) permanent yellow light. After an hour I powered it on and it went into the app update process. Which it merrily finished in half an hour. Then all was back to normal.
I do wonder how my phone got into this state. Two days ago when this began, it wasn’t just a matter of me letting the battery drain: even when the device was on, the battery refused to recharge. I could see the battery level drop, and no matter what power source I connected it to, it just did not recharge (it didn’t show the lightning symbol in the battery icon either). Powering the device off and on did not help either, I did that two or three times in the hours during which the battery just went down.
Could it be related to another problem my FP2 has been having on and off?
In the last two months, I’ve had moments where the device just suddenly shut down. Often during or after calls, or while taking photos or videos. But also while browsing or merely flicking through the screens of the Android/FP2 launcher itself. This happens about once a week, though sometimes it can be in quick succession.
From support: "According to the repair report, the core module, bottom module and the battery of your phone have been replaced with brand new ones. "
If that’s true then it could be software. -
When I received the phone back from being repaired it immediately did a a software update. Is it it possible that the phone worked in the Fairphone lab on one software version and then broke after I updated it?
Here is the current state of my phone: I removed the battery from the phone for several hours. I put the battery back in and I see the blinking light. According to the #batteryguide the light should turn solid red after “some minutes”. On my phone the light goes dark after 30 seconds and stays dark.
If I press the on button then the light starts blinking again. After a minute the light goes dark, I see the battery charging icon followed by the Fairphone logo. After about 30 seconds the screen goes dark and the red light starts blinking again.
Sometimes it gets to the “Android is starting…” message box. It counts up to a number before turning off again.
"Optimising app 20 of 128"
"Optimising app 28 of 86"
“Optimising app 24 of 128”
That means either your brand new bottom module is having issues too or your charger or cable is not working right.
With the right hardware the LED should stay on while charging and the phone shouldn’t try to start booting on it’s own. So you shouldn’t get to the app optimization bootloop without pressing a button - which by the way is a separate issue described here.
You can try going to #dic:recoverymode.
Just try and stay there for a while and see if the phone charges there (it’s definitely more battery-friendly then the app optimization process).
Okay, my sister is having the same issues on her Fairphone 2.
It doesn’t boot up and neither does it properly charge. We’ve tried a number of different cables, too.
We can’t be sure whether it is the battery or the bottom module since don’t know any other FP2 owner to check. My sister now considers returning the phone, but would like to recover the data from it. Is there any way we can do this?
Thank you!
Another report to same kind of issue:
My Fairphone is now 18 month old and looks like the bottom connector is the culprit.
It switches on but charging stops before 100% and sometimes there is quick charging/not charging state switching.
Tried several chargers, cables, a new battery from the shop, dissambling and cleaning the bottom module. No change. And fiddling with the connector finally allows the charge to start again, but I think it also breaks it more.
My last trial would be to change completely the bottom connector but the shop indicates it as ‘out of stock’ which might be a hint that many other fairphoners ordered this spare part or that the repair team are replacing this module often on returned pieces.
So I’ll wait until this part is available again, hoping that my connector will not die before
Indeed, the bottom connector is dying:
today dyring a call, the distant party did not hear me.
I checked with the Settings > Maintenance > Hardware diagnostic tool: the bottom mike was producing noise and not transmitting voice.
Again by fiddling and tapping on the bottom connector, it started to work again.
Seems that the connections are loose but I don’t know how to tighten them more, looks more difficult than the battery that I now keeps into place with a piece of paper…
Finally I opened a ticket to support describing exactly the issue and the tests I have performed and they sent me a bottom module.
Everything is OK now.
Yo, just wanted to give an update: I met @explit in Berlin and he helped me solve the problem. The issue was in fact a broken bottom module, which we then replaced. Thank you @explit!
You are always welcome! There is not much possibilities to make a fast diagnostics and troubleshooting on FP1 and FP2 devices. I try to fill this hole in Berlin / Brandenburg Area.
