FP4 Quickstep keeps stopping after A15 upgrade

It’s still blinking whithout the SIM card.

1 Like

Moved your post here. Kindly confirm if you use Orange? As you seem to can access your phone you can try another launcher App, e.g. from Fossify

Else see above

2 Likes

No way to go back on this update?

What a mistake to have made…

I’m with Free, but I still have an Orange app that installs with every Android update.

I just tried without a SIM card → Same problem.

Moi aussi, le mien a une sous couche orange. Il clignote dès l’allumage.

Me too, mine has an orange underlayer. It flashes as soon as the ignition.

I can access an application from the home screen, if I manage to press the icon at the right moment. Then, the screen no longer flashes. On the other hand, as soon as closing, the blinking resumes.

1 Like

I’m no longer with Orange, but I used to be with this phone.
I can’t download another app to test a different launcher.

Try to get into the Playstore to download another launcher, e.g. the Fossify Launcher

1 Like

No, there is no way without doing a factory reset unless your bootloader is already unlocked?

1 Like

I can’t access to the playstore. Only few app on my home screen, with luck…

The phone’s status bar is accessible.
So, we can go to the Settings menu (Network, Applications, Display, System, etc.).
Can’t we find a solution there?

so you can access the settings and Apps list? Try to go from there to the Playstore using the little icon at the top right and download another launcher, open it, you will be asked which one to use by default, select the other launcher

2 Likes

Yes, I did it. Go to Settings | Apps | Playstore, small square in the top right corner.
Now, I’m downloading Fossify Launcher.

I’m setting it as the default.
It works!

2 Likes

I managed to install the fossify launcher and make it the default. The screen no longer blink but the look is very different.

2 Likes

Summary workaround:
Go to settings via the quick settings menu (pull down from top and select the gear icon-select apps-select Playstore-open it using the small square at the top right-download another launcher (e.g. Fossify)-open it and select it as default

I like the look more actually… however the important thing at the moment is, you can use your phone.

Now def back up all important data when you are not doing this on a regular basis and report to support as long as Fairphone didnt confim to have logged the bug internally…

Edit: there is a second woraround, requiring a PC and adb

I know its no solution ,still I will mark this post with the a workaround as solution for this topic so that people can easily find it.

17 Likes

Can we expect an update from Fairphone? The last time I asked a question on the customer service, I had my awnser 6 months later…

1 Like

well support still has a backlog, while they are working on improving it. Overall yes I would expect they work on this and provide an update to fix it…In the beta group was 1 report from someone who used Orange during roaming/travel a few days before this update, however it was not that drastic as your reports here, i.e. the phone was still usable, For the FP5 as linked above there were reports as well (still phones were usable) and a fix was applied by Fairphone.

While I tagged FP above, as long as they dont confirm the bug without everyone contacting support, support is the official way to report bugs. Def link to this topic here when doing so.

4 Likes

Wow! Awesome work! :clap:

4 Likes

has been flagged, thanks for your efforts! @yvmuell :folded_hands:t2:

8 Likes

Thanks @Fairphone_CM , can you confirm if customer need to report to support or not?

3 Likes

Thank you very much ! It also works for me and my Fairphone 4 is easily usable now :-). But as Fabian3 said, I thonk it would be better to have an update from Fairphone, or to extend the community of “beta-testors” in order to cover a wide range of possible bugs.

The only remaining strange thing is that when I swipe down on my screen, the “Wallet” icon is now always on and I can’t turn it off. This wasn’t the case before the Android 15 update. I hope this won’t be a source of future problems…