Related
So since installing CM12, I've been running into both "Unfortunately camera has stopped", and "Cannot connect to camera" errors. It's strange because when I flash a fresh install after wiping cache/dalvik/data/system...everything, then boot up, the camera works fine. It's not until a day or two later that I realize it just breaks itself and stops working.
This has happened multiple times now, and what I have to do to temporarily fix is wipe everything (including internal storage and sd card...yes on purpose), and then sideload CM12 and GApps back onto the phone. Once I do this and boot up, again, the camera is working fine...but sure enough a day or two later *poof*, it commits suicide...
This is the runtime exception that is being thrown:
Code:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performLaunchActivity(A ctivityThread.java:2329)
at android.app.ActivityThread.handleLaunchActivity(Ac tivityThread.java:2391)
at android.app.ActivityThread.access$900(ActivityThre ad.java:147)
at android.app.ActivityThread$H.handleMessage(Activit yThread.java:1296)
at android.os.Handler.dispatchMessage(Handler.java:10 2)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.jav a:5256)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:693)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.camera.one.OneCameraManager.isCamera2S upported(OneCameraManager.java:107)
at com.android.camera.one.OneCameraManager.create(One CameraManager.java:84)
at com.android.camera.one.OneCameraManager.get(OneCam eraManager.java:71)
at com.android.camera.CameraActivity.onCreate(CameraA ctivity.java:1352)
at android.app.Activity.performCreate(Activity.java:5 933)
at android.app.Instrumentation.callActivityOnCreate(I nstrumentation.java:1105)
at android.app.ActivityThread.performLaunchActivity(A ctivityThread.java:2282)
... 10 more
I seem to be the only one facing this issue, and google is no help whatsoever. It can't possibly be hardware related, because each time I wipe internal storage and adb sideload the rom back on, the camera works great...EVERY TIME...and I've done it about 5 times now, but it's getting old, tedious, and inconvenient... Can anyone offer any insight at all, or does anyone have *any* idea what could be causing this?? Thanks in advance, and I appreciate all help...
Are you on the latest TWRP and the latest firmware? People have had that issue and that was the culprit. Read the first few pages of the CM12 thread santod made in the development section.
Sent from my HTC6500LVW using XDA Free mobile app
Here's the stock rooted YNG1TAS17L ROM. Includes root(enable in Developer options) and the rest is untouched, so it's OTA update safe
Stock Rooted YNG1TAS17L ROM
md5 - b98a809b18ab26679cffda230ab09f68
YNG1TAS17L Radio, etc - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
F2FS users - Attached zip includes a modified updater-script that needs to be added to the ROM(overwrite updater-script in META-INF\com\google\android folder), which will format the system partition as F2FS. You will also need to overwrite the boot.img with a F2FS compatible one or you can flash it after flashing the ROM
Downloading... I'll make a try on multirom.
Thanks..I like your works!
Thank you for your regular work and effort calkulin !
Sent from my A0001 using XDA Free mobile app
Great job! Thanks
changelog?
what bugs have been fixed
Flypants101010 said:
what bugs have been fixed
Click to expand...
Click to collapse
They fixed the SystemUpdateService wakelock
Added Voice Wakeup
And I imagine a few more things
Thanks @Calkulin..
Looking for email and exchange email apks if anyone has them or has a link thanks.
The radio link seems to be offline mate.
Edit: Its up again.
Thank you for all the hard work mate! Awesome!
Sent from my A0001 using Tapatalk
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Calkulin are you going to work your magic on this release soon?
I dirty flashed today's update over Calkulin's stock, rooted CM12s from the original roll-out and now, when I try to open developer's options in settings I get the "Unfortunately settings have stopped" message. I did install SuperSU when TWRP prompted me and root is working. I tried clearing data in Settings and re-enabled developer's options and it still crashes. Everything else seems to work fine. Fixing permissions didn't help either. Anyone else having this issue? Is there a fix?
Here is the log that appears when I click report:
java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NumberFormatException: Invalid int: "3
"
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2980)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3011)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2394)
at android.app.ActivityThread.access$900(ActivityThread.java:147)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1296)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
Caused by: java.lang.NumberFormatException: Invalid int: "3
"
at java.lang.Integer.invalidInt(Integer.java:138)
at java.lang.Integer.parse(Integer.java:410)
at java.lang.Integer.parseInt(Integer.java:367)
at java.lang.Integer.parseInt(Integer.java:334)
at java.lang.Integer.valueOf(Integer.java:525)
at com.android.settings.DevelopmentSettings.updateRootAccessOptions(DevelopmentSettings.java:733)
at com.android.settings.DevelopmentSettings.updateAllOptions(DevelopmentSettings.java:637)
at com.android.settings.DevelopmentSettings.setPrefsEnabledState(DevelopmentSettings.java:512)
at com.android.settings.DevelopmentSettings.onResume(DevelopmentSettings.java:543)
at android.app.Fragment.performResume(Fragment.java:2096)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:928)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1049)
at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:1879)
at android.app.Activity.performResume(Activity.java:6029)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2969)
... 11 more
ynnek63 said:
I dirty flashed today's update over Calkulin's stock, rooted CM12s from the original roll-out and now, when I try to open developer's options in settings I get the "Unfortunately settings have stopped" message. I did install SuperSU when TWRP prompted me and root is working. I tried clearing data in Settings and re-enabled developer's options and it still crashes. Everything else seems to work fine. Fixing permissions didn't help either. Anyone else having this issue? Is there a fix?
Here is the log that appears when I click report:
java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NumberFormatException: Invalid int: "3
"
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2980)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3011)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2394)
at android.app.ActivityThread.access$900(ActivityThread.java:147)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1296)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
Caused by: java.lang.NumberFormatException: Invalid int: "3
"
at java.lang.Integer.invalidInt(Integer.java:138)
at java.lang.Integer.parse(Integer.java:410)
at java.lang.Integer.parseInt(Integer.java:367)
at java.lang.Integer.parseInt(Integer.java:334)
at java.lang.Integer.valueOf(Integer.java:525)
at com.android.settings.DevelopmentSettings.updateRootAccessOptions(DevelopmentSettings.java:733)
at com.android.settings.DevelopmentSettings.updateAllOptions(DevelopmentSettings.java:637)
at com.android.settings.DevelopmentSettings.setPrefsEnabledState(DevelopmentSettings.java:512)
at com.android.settings.DevelopmentSettings.onResume(DevelopmentSettings.java:543)
at android.app.Fragment.performResume(Fragment.java:2096)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:928)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1049)
at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:1879)
at android.app.Activity.performResume(Activity.java:6029)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2969)
... 11 more
Click to expand...
Click to collapse
why not try a clean instalation? full wipe
ynnek63 said:
I dirty flashed today's update over Calkulin's stock, rooted CM12s from the original roll-out and now, when I try to open developer's options in settings I get the "Unfortunately settings have stopped" message. I did install SuperSU when TWRP prompted me and root is working. I tried clearing data in Settings and re-enabled developer's options and it still crashes. Everything else seems to work fine. Fixing permissions didn't help either. Anyone else having this issue? Is there a fix?
Here is the log that appears when I click report:
java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NumberFormatException: Invalid int: "3
"
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2980)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3011)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2394)
at android.app.ActivityThread.access$900(ActivityThread.java:147)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1296)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
Caused by: java.lang.NumberFormatException: Invalid int: "3
"
at java.lang.Integer.invalidInt(Integer.java:138)
at java.lang.Integer.parse(Integer.java:410)
at java.lang.Integer.parseInt(Integer.java:367)
at java.lang.Integer.parseInt(Integer.java:334)
at java.lang.Integer.valueOf(Integer.java:525)
at com.android.settings.DevelopmentSettings.updateRootAccessOptions(DevelopmentSettings.java:733)
at com.android.settings.DevelopmentSettings.updateAllOptions(DevelopmentSettings.java:637)
at com.android.settings.DevelopmentSettings.setPrefsEnabledState(DevelopmentSettings.java:512)
at com.android.settings.DevelopmentSettings.onResume(DevelopmentSettings.java:543)
at android.app.Fragment.performResume(Fragment.java:2096)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:928)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1049)
at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:1879)
at android.app.Activity.performResume(Activity.java:6029)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2969)
... 11 more
Click to expand...
Click to collapse
I experienced this too, when dirty flashed, root permissions were not found by any app and trying to get into developer options caused a force close. After full wipe and reinstall, root permissions were still not working right out of the box,which was the case on previous release of yours if i remeber right, but i could get into developer options and enable it myself. I was able to hide developer options again without losing root access by cleaning data of settings app.
Th3DaRk_Vampire said:
why not try a clean instalation? full wipe
Click to expand...
Click to collapse
Well, this was a clean install when I flashed COS12 from the original release. Prefer not to have to do that again. But it is an option. Thanks!
RADIO
Hi, thanks for the update i just got it in my phone but i did not try it...
Can i have some informations for the radio thing, cause i don't know what can i do with it ?
Thanks
The radio file link posted here is for the previous version. Kould you note it down in the OP that they are the the same in case there is actually no difference between the two versions.
Or maybe this is a mistake to fix.
ynnek63 said:
Well, this was a clean install when I flashed COS12 from the original release. Prefer not to have to do that again. But it is an option. Thanks!
Click to expand...
Click to collapse
Mine was working fine for couple of days in the previous version before it started doing this FC on Dev ops and then I OTAed to YNG1TAS17L but the issue was still there. Funny thing is that I made a nandroid afterwards did a clean flash of this ROM but the problem didn't go away.
So I tried replacing the boot.img from the signed zip file and removing the SU binary. Rebooted flashed SuperSU but the problem didn't go away. I was thinking isn't there anyway we can completely revert the built-in root? even though what I did above was more or less the same thing
I'm going to try removing the SU binary again and before flashing SuperSU check whether I can access Dev ops or not.
From the error code posted above shouldn't the integer be without quotes .
3 instead of "3"?
Sent from my A0001 using XDA Free mobile app
ynnek63 said:
I dirty flashed today's update over Calkulin's stock, rooted CM12s from the original roll-out and now, when I try to open developer's options in settings I get the "Unfortunately settings have stopped" message. I did install SuperSU when TWRP prompted me and root is working. I tried clearing data in Settings and re-enabled developer's options and it still crashes. Everything else seems to work fine. Fixing permissions didn't help either. Anyone else having this issue? Is there a fix?
Click to expand...
Click to collapse
Flash this and then you'll have to re-enable root in developer options
Am trying to make this rom F2FS in one zip, but cant find boot.img from another LP 5..0.2 F2FS rom, any suggestion? Perhaps anyone has it done already and willing share it? (Which I`d do when I make it)
EDIT: is it enough to flash any F2FS compatible kernel to change the boot.img?
Hello,
after flashing the new CM13 snapshot cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J2-i9300 I keep receiving the following error over and over again:
"[CRASH] com.google.android.gms threw java.lang.securityException
java.lang.SecurityException: "gps" location provider requires ACCESS_FINE_LOCATION permission.
at android.os.Parcel.readException(Parcel.java:1620)
at android.os.Parcel.readException(Parcel.java:1573)
at android.location.ILocationManager$Stub$Proxy.addGpsStatusListener(ILocationManager.java:741)
at android.location.LocationManager.addGpsStatusListener(LocationManager.java:1537)
at aepg.acom.google.android.gms:1045)
at aelu.bcom.google.android.gms:7362)
at aelu.handleMessagecom.google.android.gms:262)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.os.HandlerThread.run(HandlerThread.java:61)"
Most of the apps doesn't work either. Most of the Gapps don't work, too, reffering to this error.
I granted the permission for Location but this does't help either.
I don't know what to do. Help would be much appriciated!
Thanks.
Mike
Same problem here....
I tried a clean flash and also tried to install gapps directly after installing cm13. But no success. I keep getting this error message...
I have the same problem with S4.
flash newest/oldest gapps ?
exe98123q said:
flash newest/oldest gapps ?
Click to expand...
Click to collapse
directly downloaded from open gapps:
open_gapps-arm-6.0-nano-20160821
try old or dont use, you can download apk from mirrors (google is yours uncle )
the newest have some bug or high demand on resurences imo
edit.
try pico only, you no need nothing else
exe98123q said:
try old or dont use, you can download apk from mirrors (google is yours uncle )
the newest have some bug or high demand on resurences imo
edit.
try pico only, you no need nothing else
Click to expand...
Click to collapse
Tried pico - same problem.
Tried whiping cash, fresh install CM13, fresh install GApps - same problem.
I did however find apk mirrors, but installing them didn't work ("Parsingfehler")...? How do I install the APK other then uploading it to the phone? Did I choose the wrong apk? Which one do I use for my S3 i9300? I tried this one:
http://www.apkmirror.com/apk/google...es-9-4-52-438-127739847-android-apk-download/
Does this problem maybe have anything to do with this patch?!
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0
Sorry, but I'm not an expert so I'd need support what to do with it.
Please help. I'm starting to get sick of this problem and thinking about switching back to CM11 if this is even possible (tried to do so once after CM13 - phone went to bootloop) ...
Thanks.
that apk you can install normal, only gaps
exe98123q said:
that apk you can install normal, only gaps
Click to expand...
Click to collapse
???
i mean cant, gapps include files .jar, not only gsm core
Does anyone have a solution for the problem? Still not working. As soon as I start any gapp the message appears again.
Please help.
Thanks
Meanwhyle I managed to solve the problem. This gapps seem to work fine in combination with the CM13 snapshot:
http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
1) whype system partition & cash
2) flash room (I used cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J2-i9300.zip (296.87 MB)
3) install gapps (see above)
4) reboot
At first it seemed to cause further FC, but somehow they disappeared (maybe after updating the apps) and now everything works fine (except GPS location in Google Maps, but this is my least problem).
I also foudn another provider of gapps, but didn't test it.
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Apps
I had the same problem I gave up in the end and I downloaded aptoide has the same apps that you get from the play store
http://forum.xda-developers.com/showthread.php?t=3276606
Try this.
Sent from my GT-I9300 using XDA-Developers mobile app
hello,
been having this weird bug/problem with com.miui.security center with every miui 9 release for poco(miui 10/pie security app runs fine but i didnt like miui10!)
the strange thing is that xiaomi is sending updates to all its apps on miui 9 exept security center!!(am talking about the app update not about the antivirus defs update etc).
the question is : can i remove the security app?and how?( am on miui 9.6.14 global stable ....rooted).
Install Titanuim Backup and uninstall from there.
P.S you can run into problems and force close issues along with other unbearable ****. so backup Security App on Titanium Backup and then uninstall it
Don't even think of uninstalling the Security app. I tried it twice and ended up in bootloop. I spoke to a miui dev and he said Security app is an essential part of miui rom and messing with it means messing with the ROM.
Right
Same here
com.miui.securitycenter
Need a mod for this can someone help.
How do i mod this so that all undesirable tracking & spyware components can be removed. It is obvious that this of a tracker agent making it unsafe for the user only makes it safer for XIamoi & its partners.
So I opened up the the app components-
Broadcast receivers activities services etc. And here is what I found .....
In something that supposedly claims to be a for security component for the phone
- Dunno if they will let me stick in a screenshot here . There are adware and spyware components down to the core.
Code:
AdsProcessPriorityService
com.facebook.ads.internal.ipc.AdsProcess
PriorityService
AdsMessengerService
com.facebook.ads.internal.ipc.AdsMessen
gerService
That is to name a few
- any attempt to disable this component is futile because even if you run pm disable the component is force enabled
- the other singers if I am rooted and I am ' magiskcally ' I hide magisk from all these redmi components. ..... even Here it forces need to unhide magisk could you see the extent of spyware organisation down to the core
I would like to continue this thread with an invitation to vah word wants to give me an approach and work with me so that a magisk module that will grab his component from the current phone and mod it -let the original spyware component load during boot time and post boot do a swap with the mod
Is it possible to do this kind of modification & unspy MIUI
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Vipxpert said:
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Click to expand...
Click to collapse
i can confirm this , i on miui 13.0.11 , redmi note 10(mojito) . uninstalled com.miui.securitycenter , rebooted . no bootloop. i will let other know if i encounter some bug later
Edit1: cant open battery setting, manage apps show nothing
Vipxpert said:
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Click to expand...
Click to collapse
can i delete miui cleaner ?
Apih95 said:
can i delete miui cleaner ?
Click to expand...
Click to collapse
Well.... Isnt that intergrated into Security Center app as well lol
ron_hyatt said:
hello,
been having this weird bug/problem with com.miui.security center with every miui 9 release for poco(miui 10/pie security app runs fine but i didnt like miui10!)
the strange thing is that xiaomi is sending updates to all its apps on miui 9 exept security center!!(am talking about the app update not about the antivirus defs update etc).
the question is : can i remove the security app?and how?( am on miui 9.6.14 global stable ....rooted).
Click to expand...
Click to collapse
Lucky patcher (slightly sketchy) and De-Bloater appear to work to remove apps on rooted devices
Obviously
Code:
adb shell pm uninstall --user 0 com.miui.securitycenter
will not remove it but if all you need is it to be disabled you can try that
Hello, this probably won't be seen, but to the very few travelers who discover this message on google or something:
As of January 19th 2023, the "Security Center" application on MIUI 13 is extremely sketchy.
I'm planning on trying to decompile it if possible.
Currently (According to the AOSP part of the settings) The app has permissions that are very worrying. Downloading files without permission, proprietary MIUI perms, full network access, etc.
Not only that, the built-in package manager utility (PM), refuses to disable com.miui.securitycenter due to being unable to "disable core miui packages..." and spitting out an exception dump.
This is clearly a protected app, that has too many permissions, for no apparent reasson.
Setting SELinux to permissive dosen't help either.
There are 2 options that people have currently - Either leaving a piece of a PUP (Potentially unwanted program) on their phone, or risking bricking it by uninstalling it.
According to the posts on this thread some people have had success, some got a soft-brick.
Doing so shouldn't result in a hard brick, so if you have backups, a userdata format should solve the issue.
TheMagnificent_Y said:
Hello, this probably won't be seen, but to the very few travelers who discover this message on google or something:
As of January 19th 2023, the "Security Center" application on MIUI 13 is extremely sketchy.
I'm planning on trying to decompile it if possible.
Currently (According to the AOSP part of the settings) The app has permissions that are very worrying. Downloading files without permission, proprietary MIUI perms, full network access, etc.
Not only that, the built-in package manager utility (PM), refuses to disable com.miui.securitycenter due to being unable to "disable core miui packages..." and spitting out an exception dump.
This is clearly a protected app, that has too many permissions, for no apparent reasson.
Setting SELinux to permissive dosen't help either.
There are 2 options that people have currently - Either leaving a piece of a PUP (Potentially unwanted program) on their phone, or risking bricking it by uninstalling it.
According to the posts on this thread some people have had success, some got a soft-brick.
Doing so shouldn't result in a hard brick, so if you have backups, a userdata format should solve the issue.
Click to expand...
Click to collapse
i recommend lineageos rom instead of miui but make backups
Hi I'm struggling with the same problem trying to stop de SecCenter. Maybe there is a way to stop the app to run. I tried on my Note 10 Pro with MIUI12.0.6 Global (Android 11) and it works.
You need root on the phone. You should change the owner of the folder "/data/user/0/com.miui.securitycenter" to a user the is not System. In my case a run the command "chown -R root:root /data/user/0/com.miui.securitycenter". After that you need to kill the process of the "com.miui.securitycenter". So at the end the process doesn't start anymore. In the next boot you need do the process again because the boot change the permission of the folder to the system again.
I'm trying to create a Magisk Module to do that but i don't know how until now.
My solution: I just flashed a new kernel and it seems like it fixed my problem with the newest Messenger. The kernel I flashed is Thunderstorm. Now I don't have to use the old version anymore
OG POST:
Hello!
First post here, so hoping this is the right place to post.
On to the problem:
I rooted and installed a custom os for my Samsung S7 flat and everything seems to be working fine except for Facebook Messenger. The app won't open and just crashes before even actually opening without any clear error message (Messenger has stopped). Funny thing is that Facebook Messenger Lite works without any problem. I've Googled around a bit and seen that people have the same issue but none of the fixes have worked for me..
I am currently running Black Diamond os (Pie) but I have tried two other os' with the same result.. I have also tried to flash back to stock and then again to custom but that didn't work either.
Other things I've tried:
- Core only mode in Magisk
- Hide messenger in Magisk
- Delete .odex file in data/facebook.ocra folder
- Wipe dalvik, cache etc.
- Uninstall / reinstall messenger
I even tried to debug the log with adb. One thing caught my eye in the log which might explain the crash (I'm not an Android dev tho):
HTML:
AndroidRuntime: java.lang.RuntimeException: Unable to instantiate application com.facebook.messenger.app.MessengerApplication: java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.String.length()' on a null object reference
Anyone have any idea how to fix this? Thanks!
Happens to me as well on the Pixel XL Pie semi-GSI on the Redmi Note 5 Global (whyred).
It's actually a problem in the latest versions of the app, you can revert to an older version from APKMirror and it works just fine...
I haven't been able to figure out the problem either.
xezrunner said:
Happens to me as well on the Pixel XL Pie semi-GSI on the Redmi Note 5 Global (whyred).
It's actually a problem in the latest versions of the app, you can revert to an older version from APKMirror and it works just fine...
I haven't been able to figure out the problem either.
Click to expand...
Click to collapse
Ok thanks! Hopefully they'll fix it soon. I'm gonna try an older version for now and see if it'll work.
Edit: and it indeed did work. Disabled autoupdates so I'll be rolling with this for now!