I'm not sure what the issue is with xposed but whenever the screen turns off sometimes the phone will completely reboot. It'll vibrate twice and then completely reboot. I have a log cat running in the background and after it reboots I check the log and before the reboot occurs it says system error and then XposedMainBridge. It doesn't just happpen with Firekat, it's happening with other TW Roms too. Does anyone else have the same issue. aswell? The modules I'm running are App Settings, Keepchat, No Lock Home, Snapshare, Wanam Xposed, and Xposed Torch
alfadog77 said:
I'm not sure what the issue is with xposed but whenever the screen turns off sometimes the phone will completely reboot. It'll vibrate twice and then completely reboot. I have a log cat running in the background and after it reboots I check the log and before the reboot occurs it says system error and then XposedMainBridge. It doesn't just happpen with Firekat, it's happening with other TW Roms too. Does anyone else have the same issue. aswell? The modules I'm running are App Settings, Keepchat, No Lock Home, Snapshare, Wanam Xposed, and Xposed Torch
Click to expand...
Click to collapse
Your correct i had the same issue i jst uninstalled all xposed modules and my phone never had another reboot again. Its still buggy thus causing all of the random issues throughout the rom.
I also have Xposed installed on Fire Kat V8 and I haven't had any random reboots.
It depends on the module really. Xposed isn't buggy lol! It's the "app" per se. I've had this issue with my Note 2 and it was that particular module. The only way to figure it out is trial and error. Uncheck one and reboot. Wait for the random reboot. If it happens... Check it back and just go down the list. It's pretty simple really. Just a bit time consuming. Fixed the issue without losing xposed. I mean with xposed... you can do anything! You can the customization of what most aosp roms offer without the broken crap that may not ever work on our phone model and enjoy a stable touchwiz based rom. Also you can't beat Dynamic Kat rom. Most other roms (not all) I've seen have just removed a few stock apps, deodexed, added a few init.d scripts, and call it a custom rom. Many claim custom kernels cause issues as well which is total bs. Problem was the user setting frequencies that were too low. It's all subjective but has just been my experience being in IT for many years and here as well. Good luck and enjoy the phone! It's pretty badass either way you go
I have 11 modules, those included are:
App Settings
Autoinstall
Bootmanager
Customshare
GravityBox
WanamXposed
Xposed Torch
Youtube Adaway
I would recommend intalling echoAEL kernel.
I suffer no reboots as mentioned in this post.
Ok it seems to be Wanam xposed causing the reboots for me when using power saving mode. Once i disabled wanam xposed module, no more reboots! Not sure which setting in wanam caused the issue, so will keep testing until I can figure it out. Don't want to have to choose between wanam and power saving mode lol. It's likely just a single setting in wanam causing the issue.
---------- Post added at 11:59 AM ---------- Previous post was at 11:23 AM ----------
sefrcoko said:
Ok it seems to be Wanam xposed causing the reboots for me when using power saving mode. Once i disabled wanam xposed module, no more reboots! Not sure which setting in wanam caused the issue, so will keep testing until I can figure it out. Don't want to have to choose between wanam and power saving mode lol. It's likely just a single setting in wanam causing the issue.
Click to expand...
Click to collapse
Ok i found the issue! It's DVFS in Wanam xposed. If it is disabled then when i turn on power saving mode the phone reboots. If you enable DVFS in Wanam though and reboot to activate it of course, then you wont have any more reboots when you turn on power saving mode! I posted in the Wanam thread to see if this is a bug or if 5here is any way to disable DVFS without causing Power Saving mode reboots. Will post back here if I get any positive news.
Related
Of course it depend on the hack the module trying inject to the apps, but how its impact on performance if I change nothing of the code, just implement an exactly same method by XPosed module in theory?
yup...xposed kinda slows down my nexus 4 and my note 10.1 too much...
I have a Moto G and Xposed does not slowdown my phone not one bit.
randommmm said:
Of course it depend on the hack the module trying inject to the apps, but how its impact on performance if I change nothing of the code, just implement an exactly same method by XPosed module in theory?
Click to expand...
Click to collapse
Xposed slows your phone down an immeasurable amount...
The modules however... Can slow your phone to a crawl...
For me... Anything systemUI related makes my phone unusable...
Sent from my HTC Vivid 4G using Tapatalk
Running a S5 and have not seen any slow down.
No hit in speed normally, but have when 30+ modules were active. Lol
Sent from my SM-N900A using Tapatalk
Yes it solws down my wiko pulp fab 4g but mostly for the boot. The boot got sooooo loooong so i rather unistalled xposed and now i feel fresh i can turn down my phone or reboot fast. I regret all that time spent to customize the phone lol. But was a good experience.
After this long boot the phone speed was almost good. If you don't switch your phone off or reboot often it is okay.
My Zenfone GO ZV00D slowed down alot!
And I had only xblast tools, root cloak and mock location hide..
Several years passed, many devices changed. Xposed by itself does not affect to phone performance or battery usage at all. Maybe it because of specific module settings.
have been using it for a while now and there's nothing i love more but I just uninstalled xposed off my s7 edge on MM . was slowing down the phone a bit. had about 7 modules active. the benefits were worth the slowdown previously.
Okay so I'm really confused. I just had to get a refurb replacement for my Sprint HTC One because I accidentally bricked it and couldn't get it backed, took it to Sprint, they said it was water damage, blah blah blah. Whatever. So I get the new one in the mail, use it for a couple of days to make sure it's not broken, then root it.
All of that goes fine, with a couple of hiccups like flashing an outdated SuperSU. I use the TitaniumBackup from my previous phone to get all of my apps back. That goes fine. Note that I keep it a stock ROM.
Now here's the kicker.
I go to Xposed installer to install it. Normal install method won't work (it used to, but won't on this phone, probably because my old phone had a GPE ROM), so I switch to automatic install via recovery. So it installs, and- all of my mods work! Great! I disable Gravitybox since my phone is no longer on GPE and I come to a sudden realization. My multitasking won't work. I double tap the home button and it takes me back to the homescreen. It's like multitasking doesn't even exist. So I go through Xposed and disable all but the first mod, thinking I'll go through on by one to find the culprit. So I reboot with only the first mod active, and multitasking still doesn't work. Wha? This mod barely even does anything, much less to do with multitasking. So I think "Hey, maybe I should reinstall Xposed, that should fix it." So I uninstall Xposed and reboot, and viola, multitasking works. So now I wonder if it's Xposed itself that's screwing with it. So I reinstall Xposed, but don't activate any mods. I reboot, and sure enough, there's no multitasking. So it's 100% Xposed that's causing the issue, not a GPE mod conflicting with Sense.
What do I do?
Also note that the phone runs fine with Xposed enabled aside from multitasking not existing.
Thanks!
Specs:
Rom: ARHD 91.1
Kernel: Elemental X 20.2
Xposed 3.0 A4, FrameWork v67
So recently I have been using Netflix to watch shows on my phone, and maybe after around 15-20 minutes into a show, the phone will freeze up. A small percentage of the time it will unfreeze and I can go to homescreen, but otherwise I would have to do a hard reboot.
It was a crazy guess, but when I disable all Xposed Mods, Netflix would work without a problem.
I tried going through each of my modules to figure out the problem one, but it would literally take hours....
If I took the Xposed Log from the framework would that potentially tell me which module is causing the error even after the reboot? or how would i go about this?
If I can provide logs would anyone be able to see quickly which mod causes the crash?
Thanks.
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
SpGG said:
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
Click to expand...
Click to collapse
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
optimumpro said:
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
Click to expand...
Click to collapse
I didn't change anything. Same thing when I went for a new nightly of cm12.1 I did nothing out of the ordinary. Since I did not have new problems since the above mentioned, I didn't delve any further. Today I had another, interesting issue. No one was able to call the phone and I wasn't able to call out, even though the network showed up as fine with full bars. This lasted for several hours. I went into flight mode and back out of flight mode and the issue was fixed. Several SMS arrived about calls missed. And again, I have no idea if this was caused by the hardware, an issue with the software or even the network.
And that is the frustrating thing: How can I find out who the culprit is? Are there good system crash diagnostic tools? Because so far I haven't seen anything.
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