@riccardomineo Kinda same thing here: Opera doesn't start (opens and closes inmediately) in my Samsung S22. I tried deleting cache, deleting all data, reinstalling... nothing works.
However, Opera Mini works just fine, but it lacks some features of the full Opera browser.

@miyukiwork

I don't have DT Ignite either, nor ever heard about it.

However, I searched about it and found this:
https://cellularnews.com/mobile-apps/what-is-dt-ignite-why-you-should-delete-it/

TL;DR: It's either called "DT Ignite" or "Mobile Services Manager", and actually, "Mobile Services Manager" was installed in my phone. Once I disabled it (can't uninstall), Opera is working!

How to find and disable "Mobile Services Manager":

1. go to "settings"
2. go to "apps"
3. enable listing system apps by clicking on the sorting icon next to "Your apps", and turning on the slider "Show system apps" (I'm translating from my phone language, might differ a little in your particular case)
4. search for "Mobile Services Manager", select it, and disable it at the bottom of the app settings.

And voilà! Opera works again!

However, as that links states: "With DT Ignite, you only have to deal with one app and have it disabled as soon as the initial phone setup is done. After that, you can forget about it until the next system update provided by the manufacturer or data carrier comes in, or when the time you decide to reset the phone.". So it would be great if Opera would work even if DT Ignite/Mobile Services Manager is running.

Tried with an older Samsung device, S5lite tablet, and Opera works just fine there, though the firmware is old. Maybe there's something between latest Samsung firmwares, or phone form-factor vs. tablet, that makes Opera go nuts. BTW, Opera Beta behaves exactly the same, so there's no fix there (yet?).

Is there any moderator around here? It looks like this is a pervasive issue among Samsung phones. Would love to have an status update.

@speshul-flash I opened a bug report to Opera (ANDEX-105266). I also attached a video capture of the whole behavior.
However I believe there's no way to track its status or add more users as affected.

I also tried with Opera beta hoping it was fixed there but the behavior is the same.

@leocg Looks like you're a moderator for the Opera/Android forum.

Reading through this post there seems to be a common problem with latest Android/Opera/Samsung combo.

Couple of Q's:

• Should we change the title to something to refer specifically to Samsung? (if so, I don't think I can do it, maybe you can?)
• Do you have any insights about what might be going on? Or a way to track the referred support case? Or a contact within Opera devels?

Thanks

@miyukiwork Hi Miyuki,

First of all, thank you for paying attention to this bug.

Now, to your suggested tests, none of them worked for me

Test 1:
I use "Nova Launcher" as the default app launcher, instead of "One UI". Nevertheless, before creating the bug report, I tried switching to the vanilla One UI from Samsung and the behavior was the same. Now, I deleted cache and data for One UI and the behavior is still the same, whether I'm using One UI or Nova Launcher: Opera screen opens and closes inmediately.

Test 2:
Android Webview version 108.0.5359.128, last update: 13-dec-2022. Uninstalled/reinstalled, still same behavior. Attaching screenshot (catalan language):

Let me know if there're more test you want me to try or more info about detailed version numbers for OS/models/Operas, etc.

Thanks again,
Enric

@miyukiwork

I just sent a log of launching Opera with no filters to that email address and the one for the opened bug.

Let me know if that was what you needed.

@nyoh

You should give more details about what kind of help you expect

@duartes

Just to double check: have you checked within systems apps, not just the lists of apps in your phone?

Explained in step 3 here:
https://forums.opera.com/topic/58951/crashing-on-some-samsung-devices/42

@miyukiwork

I don't have DT Ignite either, nor ever heard about it.

However, I searched about it and found this:
https://cellularnews.com/mobile-apps/what-is-dt-ignite-why-you-should-delete-it/

TL;DR: It's either called "DT Ignite" or "Mobile Services Manager", and actually, "Mobile Services Manager" was installed in my phone. Once I disabled it (can't uninstall), Opera is working!

How to find and disable "Mobile Services Manager":

1. go to "settings"
2. go to "apps"
3. enable listing system apps by clicking on the sorting icon next to "Your apps", and turning on the slider "Show system apps" (I'm translating from my phone language, might differ a little in your particular case)
4. search for "Mobile Services Manager", select it, and disable it at the bottom of the app settings.

And voilà! Opera works again!

However, as that links states: "With DT Ignite, you only have to deal with one app and have it disabled as soon as the initial phone setup is done. After that, you can forget about it until the next system update provided by the manufacturer or data carrier comes in, or when the time you decide to reset the phone.". So it would be great if Opera would work even if DT Ignite/Mobile Services Manager is running.

@akkk yes, I did all that. When uninstalling it asked to copy the files from Secure Folder to the standard partition (though I didn't have anything as I don't use Secure Folder)

@guidoglx

Same here.
I actually uninstalled Secure Folder following the instructions in the link but opera still crashing, so it doesn't seem to be (exclusively) an issue related to Secure Folder.
However I have a work partition (that works under Knox, same tech used for Secure Folder). Maybe there's some interaction with Samsung Knox that makes Opera go nuts?

Do other users with the same problem also have Secure Folder or Work Profiles/Partitions?

@miyukiwork

I just sent a log of launching Opera with no filters to that email address and the one for the opened bug.

Let me know if that was what you needed.

@miyukiwork

I have adb connected and adb logcat spits out a lot of log lines, but I don't think you need them all.

What filter/command line do you need there?

@miyukiwork Hi Miyuki,

First of all, thank you for paying attention to this bug.

Now, to your suggested tests, none of them worked for me

Test 1:
I use "Nova Launcher" as the default app launcher, instead of "One UI". Nevertheless, before creating the bug report, I tried switching to the vanilla One UI from Samsung and the behavior was the same. Now, I deleted cache and data for One UI and the behavior is still the same, whether I'm using One UI or Nova Launcher: Opera screen opens and closes inmediately.

Test 2:
Android Webview version 108.0.5359.128, last update: 13-dec-2022. Uninstalled/reinstalled, still same behavior. Attaching screenshot (catalan language):

Let me know if there're more test you want me to try or more info about detailed version numbers for OS/models/Operas, etc.

Thanks again,
Enric

@leocg Looks like you're a moderator for the Opera/Android forum.

Reading through this post there seems to be a common problem with latest Android/Opera/Samsung combo.

Couple of Q's:

• Should we change the title to something to refer specifically to Samsung? (if so, I don't think I can do it, maybe you can?)
• Do you have any insights about what might be going on? Or a way to track the referred support case? Or a contact within Opera devels?

Thanks

Tried with an older Samsung device, S5lite tablet, and Opera works just fine there, though the firmware is old. Maybe there's something between latest Samsung firmwares, or phone form-factor vs. tablet, that makes Opera go nuts. BTW, Opera Beta behaves exactly the same, so there's no fix there (yet?).

Is there any moderator around here? It looks like this is a pervasive issue among Samsung phones. Would love to have an status update.