I have been having a persisting force close issue that I initially thought was linked to Greenify. "Unfortunately, Context Service has stopped" after every call I made or received, and upon booting the phone. Trial and error have caused me to find the only thing that allows me to run Xposed without any issue is having 7 or less modules enabled. I can switch between modules. For instance, I had Xposed Torch enabled and things were fine with 7 modules. I installed Xtoast, rebooted, and instant error/FC. Repeats no matter how many times I reboot. I uninstall Xposed Torch, which was just working perfectly fine, and leave XToast installed. Reboot and no error. Rebooted over and over to ensure, no error. Switched a few modules around to ensure, and it seems to not matter what modules I have installed. I have no issues whatsoever running Xposed as long as I only have seven modules installed, but if I go to install an 8th, no matter what it is, I immediately get Context Service force closes. I have not found anything on here about a definitive amount of modules you can install, so I can only hope someone has a clue what could be going on. Normally I'd look to the Logcat, but it doesn't seem to be a specific module causing this. I'd really appreciate any help any of you might have. Xposed has a lot more to offer for me than you can cram in seven modules.
Logcat? The Xposed log may not show you anything but an unfiltered logcat will.
GermainZ said:
Logcat? The Xposed log may not show you anything but an unfiltered logcat will.
Click to expand...
Click to collapse
You mean the full logcat I create through adb? If so, do i need to produce the issue while the phone is one and then take the logcat? Phone has been rebooted since the last time i got the FC, just don't want to waste time learning to upload and uploading a logcat now while phone is working if I need to re-create the problem first in order for it to be useful. Definitely will take the time to upload a logcat because I would really like to fix this issue, I just wanna make sure I do it correctly.
wrongway213 said:
You mean the full logcat I create through adb? If so, do i need to produce the issue while the phone is one and then take the logcat? Phone has been rebooted since the last time i got the FC, just don't want to waste time learning to upload and uploading a logcat now while phone is working if I need to re-create the problem first in order for it to be useful. Definitely will take the time to upload a logcat because I would really like to fix this issue, I just wanna make sure I do it correctly.
Click to expand...
Click to collapse
Enable 7+ modules so that the issue will be reproduced on next boot.
Reboot and start the logcat while the device is booting.
Wait till you see the FC and stop the logcat.
Upload the logcat.
Thanks for your reply. I just figured out the problem, thankfully.. I was preparing to do what you said, and I for some reason thought to reinstall Busybox before installing an eighth module and rebooting. My Busybox install must have been faulty. After reinstalling it said I had just reinstalled the same version as previously installed, but now I am back to nine modules and no problems.
scratch that, problem keeps getting weirder. Installed Wanam Xposed again and the issue came right back, uninstalled and the issue came back until I went back down to 7 modules and now no issue. I'm so confused..
wrongway213 said:
scratch that, problem keeps getting weirder. Installed Wanam Xposed again and the issue came right back, uninstalled and the issue came back until I went back down to 7 modules and now no issue. I'm so confused..
Click to expand...
Click to collapse
Honestly can't say anything without a logcat, please grab one.
You should also be able to use an app to do it (e.g. CatLog) since your device is booting. Just start the app as soon as your device boots.
GermainZ said:
Honestly can't say anything without a logcat, please grab one.
You should also be able to use an app to do it (e.g. CatLog) since your device is booting. Just start the app as soon as your device boots.
Click to expand...
Click to collapse
FC is not currently happening, but I just downloaded Catlog and I am still getting a lot of errors in my logcat.. makes me curious as to whether my issue can be pinpointed without messing things up yet again. I attached my logcat filtered for "error", if you are able to discern anything from it, please do let me know what you find. If not I'll be sure to load Catlog at boot and grab one if the error does occur again. Thank you for recommending Catlog, by the way, SO much easier for a new guy like me than terminal emulator/ADB.
Edit: I see you mentioned an unfiltered logcat earlier, but honestly I do not know what I am doing with logcats at all, and as the error is not occuring right now I thought it might be a little unnecessary to look through a million lines of text.. I figure this is short enough that if something sticks out I can fix it, if not I can run Catlog again if the problem persists.
F/C All devices
All of my androids device using Xpose are force closing, well apps that are associated with it. Only fix I could find is older download..it seems the update had issues..
wrongway213 said:
FC is not currently happening, but I just downloaded Catlog and I am still getting a lot of errors in my logcat.. makes me curious as to whether my issue can be pinpointed without messing things up yet again. I attached my logcat filtered for "error", if you are able to discern anything from it, please do let me know what you find. If not I'll be sure to load Catlog at boot and grab one if the error does occur again. Thank you for recommending Catlog, by the way, SO much easier for a new guy like me than terminal emulator/ADB.
Edit: I see you mentioned an unfiltered logcat earlier, but honestly I do not know what I am doing with logcats at all, and as the error is not occuring right now I thought it might be a little unnecessary to look through a million lines of text.. I figure this is short enough that if something sticks out I can fix it, if not I can run Catlog again if the problem persists.
Click to expand...
Click to collapse
I'm asking for an unfiltered logcat because not all useful lines will contain "error". Filtering for " AndroidRuntime" is usually enough, but it's safer to just upload the whole thing.
Anyway, please upload one when you can reproduce the issue. I see some errors related to secure storage in your log but I don't think that's related to anything.
jon3640 said:
All of my androids device using Xpose are force closing, well apps that are associated with it. Only fix I could find is older download..it seems the update had issues..
Click to expand...
Click to collapse
Well, if it is a problem with the framework, it won't be fixed unless you help out by posting a logcat.
GermainZ said:
I'm asking for an unfiltered logcat because not all useful lines will contain "error". Filtering for " AndroidRuntime" is usually enough, but it's safer to just upload the whole thing.
Anyway, please upload one when you can reproduce the issue. I see some errors related to secure storage in your log but I don't think that's related to anything.
Well, if it is a problem with the framework, it won't be fixed unless you help out by posting a logcat.
Click to expand...
Click to collapse
problem came back again for no reason, only 6 mods enabled and all have been stable for days... restart phone because i was getting a crazy mms wakelock in bbs. here's the logcat with the "unfortunately, context service has stopped" both from just automatically happening and i triggered it by having my girlfriend call me. i then disabled xposed, restarted and no problems, so i took a logcat of that to show how my phone runs normally in case you need it. let me know if you do and i will upload that as well.. if you can find anything in here i will greatly appreciate it. i can't even use xposed at this point, i'm worried i'm either damaging my phone or possibly missing calls/texts/notifications. thanks for your time in advance.
It's an ANR (Application Not Responding) error, so I'm guessing your phone kinda hangs for a bit before showing you the dialog?
It doesn't seem to be related to Xposed at all, though. It's Samsung's "Context service" (com.samsung.android.providers.context), so I'd personally try checking for a system update before anything else. You're likely to get more help in the S5 section (since the problem isn't related to Xposed), through it looks like no one else has this problem.
It hangs for a second, but those errors don't stop things I can see, just errors. I have to admit, I don't quite understand, if it's not related to Xposed, why would it only happen with certain modules enabled? That's why I assumed it was xpoaed related to begin with. Do I need to Odin back to stock? I don't want to damage my phone but I don't know anything about that error or if it could he damaging.. Sorry for the text wall. Thanks for being so helpful.
Sent from my SM-G900V using XDA Free mobile app
wrongway213 said:
It hangs for a second, but those errors don't stop things I can see, just errors. I have to admit, I don't quite understand, if it's not related to Xposed, why would it only happen with certain modules enabled?
Click to expand...
Click to collapse
Coincidence, I'd say. You'd probably get the same thing without Xposed, but as you've noticed it seems to happen semi-randomly, so chances are you weren't "lucky" enough.
wrongway213 said:
Do I need to Odin back to stock?
Click to expand...
Click to collapse
If you're using a custom ROM, you could also report this problem to the ROM dev with the logcat and ask him if his base is up to date or if there's anything he can do about it.
wrongway213 said:
I don't want to damage my phone but I don't know anything about that error or if it could he damaging..
Click to expand...
Click to collapse
It's mostly just annoying, there should be no permanent damage of any kind.
GermainZ said:
Coincidence, I'd say. You'd probably get the same thing without Xposed, but as you've noticed it seems to happen semi-randomly, so chances are you weren't "lucky" enough.
If you're using a custom ROM, you could also report this problem to the ROM dev with the logcat and ask him if his base is up to date or if there's anything he can do about it.
It's mostly just annoying, there should be no permanent damage of any kind.
Click to expand...
Click to collapse
could it be related to s health? i know this isn't the s5 forum, but i see under app info on s health there is a "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY".. i have heard people talk about having issues with s health and xposed. could that permission be the context service error i am getting, based on what you have seen in my logcat?
wrongway213 said:
could it be related to s health? i know this isn't the s5 forum, but i see under app info on s health there is a "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY".. i have heard people talk about having issues with s health and xposed. could that permission be the context service error i am getting, based on what you have seen in my logcat?
Click to expand...
Click to collapse
I didn't see anything related to S Health, but it might've related to the secure storage (though I'm not sure if that's a stock Samsung thing or if it's activated by the user).
Related
I just rooted and downloaded xposed. I've done this like 20 times now so I know it's not coincidence, but every time I install xposed, SMS sending (not receivingnevermind) is crippled. 99% of messages I try to send either hang forever or fail, every now and then one goes through (10 minutes later or something). Oddly MMS sending is not affected (receiving now seems to be). What the heck is going on‽‽‽‽‽‽‽‽
sum1 plz halp?
P.S. there may or may not be a problem with screen timeouts too. I'll post about that once I get more concrete data.
EDIT:
Some clarifications. No modules, nada. The ONLY variable is whether or not xposed is installed.
jooniloh said:
I just rooted and downloaded xposed. I've done this like 20 times now so I know it's not coincidence, but every time I install xposed, SMS sending (not receivingnevermind) is crippled. 99% of messages I try to send either hang forever or fail, every now and then one goes through (10 minutes later or something). Oddly MMS sending is not affected (receiving now seems to be). What the heck is going on‽‽‽‽‽‽‽‽
sum1 plz halp?
P.S. there may or may not be a problem with screen timeouts too. I'll post about that once I get more concrete data.
EDIT:
Some clarifications. No modules, nada. The ONLY variable is whether or not xposed is installed.
Click to expand...
Click to collapse
I can confirm that for the t-mobile variant n915t this is also an issue. For me causes eras with the settings on the edge menu, in addition to many laggy installations and random errors everywhere. I'm not using xposed until this gets resolved. I installed last stable but I am Not sure if the unreleased most recent one might be better compatible but I'm not interested in trying till someone confirms there is a working version because I am tired of playing with my phone like this I want to enjoy it lol
Eras=errors
zz1049 said:
I can confirm that for the t-mobile variant n915t this is also an issue. For me causes eras with the settings on the edge menu, in addition to many laggy installations and random errors everywhere. I'm not using xposed until this gets resolved. I installed last stable but I am Not sure if the unreleased most recent one might be better compatible but I'm not interested in trying till someone confirms there is a working version because I am tired of playing with my phone like this I want to enjoy it lol
Eras=errors
Click to expand...
Click to collapse
YES! YES! I never thought the laggy installs were related too! I didn't even get around to testing that because the SMS issue was frustrating me so much. The experimental version of xposed installer doesn't fix anything. I've just stuck my SIM in my note 3 for now until a fix is released.
Interesting thing. The guy on this thread has the same issue on as s5, but he says a kernel update fixed it . . .
EDIT:
The following threads all document similar, if not the same issues:
http://forum.xda-developers.com/xposed/xposed-touchwiz-stock-messaging-app-t2795905
http://forum.xda-developers.com/xposed/issues-xposed-n915p-sprint-galaxy-note-t2947850
http://forum.xda-developers.com/note-edge/help/n915p-cf-auto-root-fails-t2944539
http://forum.xda-developers.com/xposed/xposed-note-4-t2928864
Find a fix yet zz1049?
jooniloh said:
Find a fix yet zz1049?
Click to expand...
Click to collapse
Not yet until then I'm just finding replacement rooted apps to fill the gaps in till then..
http://forum.xda-developers.com/note-edge/help/q-successfully-rooted-note-edge-n915t-t2940554/page6
Member pieces of cake stated he resolved it it was simple, don't know what that really means but you could ask him. I checked there has not been any new uploaded versions of Xposed. I'm just going to wait for a patch to Xposed unless we hear of any fixes.
zz1049 said:
Not yet until then I'm just finding replacement rooted apps to fill the gaps in till then..
http://forum.xda-developers.com/note-edge/help/q-successfully-rooted-note-edge-n915t-t2940554/page6
Member pieces of cake stated he resolved it it was simple, don't know what that really means but you could ask him. I checked there has not been any new uploaded versions of Xposed. I'm just going to wait for a patch to Xposed unless we hear of any fixes.
Click to expand...
Click to collapse
ugh. well I guess whatever works. I was rather dependent on greenify's xposed features and wanam. I hope someone figures out a fix soon.
try this guys
Just disable secure storage in Wanam this fixes the lag as others mentioned
Its Wanam Xposed, under "Security" tab and checkbox "Disable Secure storage" and/ or used XSecureStorage module.
http://besttopics.net/link/189924_fix-how-to-fix-xposed-framework-lag-on-note-4
Several months ago, I started experiencing an annoying issue on my Nexus 6 running LOS 14.1 where the silent mode setting would get disabled on its own even when the "Until you turn this off" option was chosen. I had posted on the LOS subreddit as well as here on XDA about it multiple times and someone had stated that the maintainer for shamu was likely ignoring it because they were busy working on 15.1. So naturally, I was disappointed to find out after upgrading to the first LOS 15.1 release that the issue still persists.
What do I do? My phone's been doing this since January and I tried everything I could think of to fix it, including wiping the phone and reinstalling everything and even that did not work.
Here are some important things to note about my installation:
Running LOS 15.1 (upgraded from LOS 14.1)
Using the stock Open GApps package
Rooted with Magisk 16.0 (latest version at the time of this post)
(I'm going to tag @Elektroschmock since as far as I am aware, he's the person we have to thank for keeping our shamus alive and well and would therefore be most likely to able to help me out.)
I wasn't ignoring it, I just wasn't able to reproduce it.
If this really is a common problem then it is not specific to Nexus 6.
Elektroschmock said:
I wasn't ignoring it, I just wasn't able to reproduce it.
If this really is a common problem then it is not specific to Nexus 6.
Click to expand...
Click to collapse
Ah, alright. That's unfortunate. The thing that's frustrating about this is that I cannot find any reports from anyone else having this issue. Not just the Nexus 6, but for any phone.
David B. said:
Ah, alright. That's unfortunate. The thing that's frustrating about this is that I cannot find any reports from anyone else having this issue. Not just the Nexus 6, but for any phone.
Click to expand...
Click to collapse
In cases where you seem to be the only one affected, make a backup and try to do a clean install.
Elektroschmock said:
In cases where you seem to be the only one affected, make a backup and try to do a clean install.
Click to expand...
Click to collapse
I already tried that though. In fact I tried it multiple times. It keeps happening though.
David B. said:
I already tried that though. In fact I tried it multiple times. It keeps happening though.
Click to expand...
Click to collapse
I guess you are aware of the fact, that alarms may override the endtime of DND.
Did you check your automatic rules?
Elektroschmock said:
I guess you are aware of the fact, that alarms may override the endtime of DND.
Did you check your automatic rules?
Click to expand...
Click to collapse
Yes I have, and I am afraid that I did not find anything useful there. Even though you could not reproduce the issue, did the catlog that I posted on the LOS Jira help? (https://jira.lineageos.org/browse/BUGBASH-1373)
Even though that post applies to LOS 14.1, the issue is occurring in the same way in LOS 15.1.
It's also worth noting that I tried installing a fresh copy of LOS 14.1 to fix it, but when I upgraded to 15.1, I did not do a fresh install. Do you think it would be worth the effort to try it?
Elektroschmock said:
I guess you are aware of the fact, that alarms may override the endtime of DND.
Did you check your automatic rules?
Click to expand...
Click to collapse
I had some time last night, so without waiting for a reply, I decided to do a fresh install and I am so glad I did. So far, silent mode has not disabled itself, and I am hoping this stays that way. Additionally, my phone's performance in general seems a lot better. I am not sure if it's in my head or not, but either way, I am satisfied. If the issue pops up again, I'll be sure to let you know so that we can keep looking for alternative solutions.
Elektroschmock said:
I guess you are aware of the fact, that alarms may override the endtime of DND.
Did you check your automatic rules?
Click to expand...
Click to collapse
Last night I had some time, so I decided to do a full wipe and reinstall without waiting for a response. I am so glad I did. The issue appears to finally be resolved, as it has not happened yet, and on top of that, my phone feels like it's running faster. I am not sure if it actually is or if it's just a placebo, but either way, I am satisfied.
If the issue does end up returning, I will let you know so that we may continue looking for a way to stop it from happening.
David B. said:
Last night I had some time, so I decided to do a full wipe and reinstall without waiting for a response. I am so glad I did. The issue appears to finally be resolved, as it has not happened yet, and on top of that, my phone feels like it's running faster. I am not sure if it actually is or if it's just a placebo, but either way, I am satisfied.
If the issue does end up returning, I will let you know so that we may continue looking for a way to stop it from happening.
Click to expand...
Click to collapse
Thanks for the feedback.
If you have time can you provide feedback on jira when you think it has been solved?
Elektroschmock said:
Thanks for the feedback.
If you have time can you provide feedback on jira when you think it has been solved?
Click to expand...
Click to collapse
You're welcome! I posted this on the Jira submission. Is that good?
David B. said:
You're welcome! I posted this on the Jira submission. Is that good?
Click to expand...
Click to collapse
Yes thanks! I'll leave the ticked open a few more days and close it then.
We can reopen it anytime.
Elektroschmock said:
Yes thanks! I'll leave the ticked open a few more days and close it then.
We can reopen it anytime.
Click to expand...
Click to collapse
Alright, sounds good. Thank you for working so hard to keep my Nexus 6 up to date.
Hi. I rooted my S6 with magisk, but there is an issue where root randomly disappears. It happens within 2 minutes of the phone booting or whenever I launch and close the app. What could be the issue?
Possible culprits:
Aggressive battery optimisation.
MagiskHide fails to remount files after hiding.
Something completely different.
Didgeridoohan said:
Possible culprits:
Aggressive battery optimisation.
MagiskHide fails to remount files after hiding.
Something completely different.
Click to expand...
Click to collapse
Check response below. Don't know how to delete.
Flashed custom kernel, thought it helped. Wrote a long reply. It showed that it's uninstalled 10/10. Trying to disable the samsung useless battery manager. Where can I find the logs for MagiskHide?
TheHurtmaster said:
Flashed custom kernel, thought it helped. Wrote a long reply. It showed that it's uninstalled 10/10. Trying to disable the samsung useless battery manager. Where can I find the logs for MagiskHide?
Click to expand...
Click to collapse
The logs that might show something would be Magisk log, but preferably the magisk_debug.log, and possibly a logcat.
Didgeridoohan said:
The logs that might show something would be Magisk log, but preferably the magisk_debug.log, and possibly a logcat.
Click to expand...
Click to collapse
In your signature I saw that there's a troubleshooting guide. One of the solutions is to see if there's a faulty module. It seems that Pixel Experience doesn't like my phone that much. I left the phone alone for 4 hours so far and Magisk is still there. I found the culprit!
I'm just going to stop saying that it worked because I keep jinxing it. Here's the log. From what I see, it could be a battery optimization problem.
Edit: Debug log added too.
Disabled Samsung's battery optimization and android battery optimization that google implemented. Didn't help.
Did you ever figure this out? Keeps happening to me. Would the EX Kernel Manager's powersave cause this? Switching between performance and powersave is when I typically notice this... Will be pretty bummed if that feature won't work.
Running Pixel Dust on Pixel XL
Hello,
I'd like to have some help with diagnosing what hiccup my device recently has.
For a few days I'm on EUA4 Android 11, BL unlocked, Magisk patched, fresh install. Before that I was running some months old Android 10 also magisk rooted, some modules etc. and had uptimes of several weeks without reboot.
Now I get random reboots a few times per day. System shows samsung logo for a while, brings up warning messges "your devide... not official... security" etc., shows SIM pin, Device pin and crashes right again before launcher is fully up. Sometimes multiple times until system stays on. (Can interrupt this ofc with Power+bix+VolDown and boot Power+bix+VolUp into magisk)
Can someone help me figure out why? Some app, magisk module, frozen app idk...
I tried reading through last_kmsg and bugreport files but I'm not that savvy to actually understand why watchdog is killing system and what extra information I should fetch from the device.
I don't know where to look for the reason why this happens so I can fix it or avoid it after the next flash.
Thanks for your help.
you are not alone. its happening to me on S10+ aswell.
Thanks, always nice to know
I went back to Android 10 (DTK9). Device running for 68h without even an app force closing. Same setup otherwise, same apps/ magisk modules/ magisk canary/ disabeled samsung apps etc...
Really don't know why I couldn't get 11 to run acceptable. I'm clearly missing some diagnostic capability like "your device rebooted cause app x did something funny that produced a 0 somwhere else and that caused something in the kernel to **** it's pants..."
Propably android somehow could point me there, but obviously I'm too much of a noob to understand it.
Thats why I asked for help if someone can teach me to understand what my poor system tries to tell me.
If you can - or at least show me where I can learn about that - I'm still interested, but for the next few months I'll skip firmware updates
emanrov said:
Thanks, always nice to know
I went back to Android 10 (DTK9). Device running for 68h without even an app force closing. Same setup otherwise, same apps/ magisk modules/ magisk canary/ disabeled samsung apps etc...
Really don't know why I couldn't get 11 to run acceptable. I'm clearly missing some diagnostic capability like "your device rebooted cause app x did something funny that produced a 0 somwhere else and that caused something in the kernel to **** it's pants..."
Propably android somehow could point me there, but obviously I'm too much of a noob to understand it.
Thats why I asked for help if someone can teach me to understand what my poor system tries to tell me.
If you can - or at least show me where I can learn about that - I'm still interested, but for the next few months I'll skip firmware updates
Click to expand...
Click to collapse
im am sorry, but i cant help you with your issue. I just wanted to let you know that we all struggle and i am planning on switching back to A10 aswell, since Samsung pay still doesnt work in my country... hope someone can help you tho!
I've held off on asking for advice about this for a while because I didn't know where to ask, but I guess since there are threads for other games with similar issues, it's okay to ask here.
Basically, Pokémon Masters EX has been failing to load properly for some time. I get to the main screen only for it to give me a 'error 10102' and restart. I've looked it up and it seems it means the game has detected that my device is rooted. Problem is, I already have MagiskHide activated for it. In fact, if I disable it, the game actually crashes immediately, so at least I know it's doing something.
I'm just a novice when it comes to root-related problems, so I hope some of you have some ideas or maybe even have faced this problem with this game before. My phone is a Samsung Galaxy SM-M315F running Android 10. If there's any other information that might help, I'll be happy to tell you all.
Thanks in advance.
I tested and it seems like the 10102 error is connected to something else than Magisk. Once the game was added to the Hide list I could play it without issue.
You don't mention if you've repackaged the Magisk app with a random package name, so if you haven't done that yet, do so
Could also be that it's detecting other root apps or files on your device. Got some tips on other detection methods here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Or maybe that error is about something else entirely.
Sorry, wrong thread. Please ignore this post, my apologies.