Crashing on some Samsung devices.
-
iamthayse last edited by
@akkk now that you mentioned, I did start using the secure folder.. so it can be related.. well unfortunately I have zero intentions of unstalling my secure folder. I'll keep using another browser until they fix this problem with opera.. it's a pity though cause I really miss using opera on my phone
-
salimanilaslan last edited by
@iamthayse its definitely related with secure folder, i deleted it and opera works fine, yesterday i installed secure folder again and opera crashes again. Its obvious but opera does nothing about it. Maybe its time for using Brave.
-
akkk last edited by
@salimanilaslan
As far as we see at Opera they are just now getting the right feedback on the cause of the problem.
In reality it is a particular case and not too widespread (Samsung phone, Android 13, Secure Folder active, ...), even if it is spreading.
I was lucky to discover the cause because on the day it stopped working, the only change was the activation of the Secure Folder. A few weeks later I tried to activate again but Opera crashed again until I deactivated Secure Folder again. I searched the web with little success until I found this forum, where there was a description of the same problem but no one had yet associated it with the Secure Folder.
From now Opera should be able to replicate the problem and find a solution (assuming that the problem should not be solved by Samsung). -
miyukiwork Opera last edited by
Thanks for all the comments. We have checked the secure folder, but the crash is still not reproduced on our end. However, we have made a big progress now. It seems the crash is happening if your phone has "DT Ignite" or similar app installed.
This is what I want you to try now:
- Go to Phone's settings
- Go to Apps
- Find "DT Ignite" or similar
- Disable it
- Start Opera
-
akkk last edited by
@miyukiwork
I don't have "DT ignite" or similar apps on my phone (as far as I can tell).
Opera only works if I don't activate the Secure Folder, so there must still be some link (with Android 12 Opera and the Secure Folder worked together without problems). -
akkk last edited by
Considering that for someone the problem was solved by installing a different Launcher, the problem could be linked more precisely to One UI 5.0 than to Android 13. A problem that does not occur with One UI 4.1.
-
efolch last edited by
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":
- go to "settings"
- go to "apps"
- 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)
- 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 last edited by
@efolch
Very interesting.
I confirm that I also found "Mobile Services Manager" on my phone. Only later will I be able to do some tests by reinstalling the Secure Folder to see if Opera still works even with the active one.
I agree that I'm hoping for a fix from Opera so I don't have to keep a system app disabled (even if it doesn't seem to have any use for the user). -
-
-
duartes last edited by
@miyukiwork I don't have either DT ignite or Mobile Services Manager, and in my S21 the issue started around November when I was still on Android 12. I only upgrade to Android 13 last week. I have always had Secure Folder enabled as well a work profile (knox).
I also use opera on a Samsung S6 lite tablet (with secure folder and work profile) and I have had no issues there. The tablet is already on Android 13.
I have been using vivaldi since the issue on the S21
-
efolch last edited by
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 -
Referenced by
efolch
-
-
-
akkk last edited by
As announced for my phone, on which Opera only worked if Secure Folder was disabled, I proceeded to test the solution proposed by miyukiwork/efolch:
- reactivated Secure Folder;
- tested Opera, which started crashing again;
- deactivated the "Mobile Services Manager" system app;
- re-tested Opera which worked flawlessly.
I therefore confirm the effectiveness of the solution.
Thanks to all for the contributions. -
miyukiwork Opera last edited by
Hi again.
We have fixed the issue in the latest beta 73.0.3844.69682 (Google Play: Opera beta). If you could help us, please install and try if Opera beta starts.
-
speshul-flash last edited by speshul-flash
@miyukiwork Hello,
I have re-enabled mobile services manager and normal opera has once again stopped working although after installing the latest version of opera beta it seems to have no issues whatsoever! Would be happy if you let us know when it is patched on the normal version.
-
miyukiwork Opera last edited by
We have released OfA 73 now and it include the fix. This is currently rolling out gradually, so the availability might not be immediate.
If you still have the problem, please let me know and send in a log file.
-
duartes last edited by
@miyukiwork I can confirm that the new update works (so far) on my S21, Android 13, with secure folder and work profile activated. thank god/opera!
-
francescomapelli last edited by
@miyukiwork - fellow developer here - we're having a similar crash on our app and we can't reproduce it in any way - would you be so kind to help us understand what the issue was and how you fixed it?
how can we contact you?
Thank you so much
