I didn’t suggest that, but it might be necessary. It might not even be a solution. I advise to sit tight and wait for news.
Personally I’m hoping for a fix, like you
In any case you should always back up your phone.
I didn’t suggest that, but it might be necessary. It might not even be a solution. I advise to sit tight and wait for news.
Personally I’m hoping for a fix, like you
In any case you should always back up your phone.
Same issue here. No big problems but it’s quite annoying.
Did you reboot phone after installing fossify launcher (edit : and making it default launcher) ?
For me it’s been necessary for good working state.
If you rebooted and still have issues, maybe consider installing another launcher (on f-droid there is also ion launcher for instance) or indeed reset device in last resort.
Yes, I’ve restarted after changing the default launcher, but still got the same behaviour.
For now I’m trying other launchers, waiting for an update.
Same issue here.
Did report to fairphone but did not hear from them yet.
In addition, on start or restart the it start on the Android verbose screen (like when flashing ROM).
Very inconvenient
Welcome to the forum
Could you post a screenshot photo?
Same problem. Seems harmless but annoying nonetheless.
Having the same issue here since the Android 15 update
hello,
In my FP5 a window began to appear with the message: “Quickstep still does not work”
I don’t know what importance I can have this and I don’t know how to solve it.
Any idea?
Thanks and greetings
Hi,
Quite a few people have encountered problems with Quickstep and many have worked around it by installing a different launcher such as Nova, Lawnchair or Fossify Launcher Beta (available from F-Droid).
You can also Factory reset device if you can save it easily.
You mean make a backup before a factory reset. Because you will loose everything.
Yes.
“Easily” meaning if he does backup using Google account.
I don’t have one on my FP5 so backup is way less easy.
I meant “fastboot” screen. Could not find the right word when writing.
Same here … Quicksteps reboots very often.
On my phone, it seems to be related to Orange-related checks or UI overrides …
”isOrangeApp” fires null object exception …
Fairphone developpers out there ?
Could you tell us what’s happening in this method, and if it can be fixed ?
— logs —
08-13 08:56:19.945 24611 24611 E AndroidRuntime: FATAL EXCEPTION: main
08-13 08:56:19.945 24611 24611 E AndroidRuntime: Process: com.android.launcher3, PID: 24611
08-13 08:56:19.945 24611 24611 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method ‘boolean java.lang.String.contains(java.lang.CharSequence)’ on a null object reference
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.uioverrides.QuickstepLauncher.isOrangeApp(QuickstepLauncher.java:1049)
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.uioverrides.QuickstepLauncher.onStateSetEnd(QuickstepLauncher.java:621)
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.uioverrides.QuickstepLauncher.onStateSetEnd(QuickstepLauncher.java:222)
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.statemanager.StateManager.onStateTransitionEnd(StateManager.java:426)
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.statemanager.StateManager.-$$Nest$monStateTransitionEnd(Unknown Source:0)
08-13 08:56:19.945 24611 24611 E AndroidRuntime: at com.android.launcher3.statemanager.StateManager$1.onAnimationSuccess(StateManager.java:402)
Absolutely not…
You should make a support ticket.
Hello everyone - especially anyone else who, since the Android 15 update is having a problem with the ‘square button’, and ghost apps that you are told are not available when you click on them:
Using another launcher instead of Quickstep - I’m using Lawnchair - has fixed the problem for me.
Maybe this is related to all the other Android 15/Quickstep issues I’ve just read about
Hello and welcome
as you mentioned, it looks similar to the other posts in this topic (and my own experience as well - only I switched to Nova), so I moved your post here
I could confirm the problem comes from Orange customisation layer on my phone.
This may not be the same situation for you, but you can always have a look on this page for the details .
Hope that helps
So we need an update from Orange right ?
Maybe we should all try to let them know via support channels.