I have installed Xposed Framework on my wife's Acer Liquid E3 (E380). In fact, Xposed was the main reason for me to root it. But it seems, that Xposed causes problems. The thing is, that after I have it installed and activated, when the phone boots, the laucher starts, then some services that run in background (Llama for instance) and for several seconds I can try and do something, but at the end of the boot process the phone freezes. It does not respond to the keys nor screen touching. Furthermore, it does not respond to plugging the power cable nor unplugging it. Well... in fact it seems, that it is not completly hanged, becouse after something like few minutes it can perform certain actions, like dim the screen, but then it does not respond again. It looks like something is consuming all available computing resources and even the system core is not responding. I have tried to uninstall background services, but it changes nothing. Lucky for me, I managed to deactivate Xposed Framework before the phone "hung", which fixed all the problems.
Since I'd like to have ability to use Xposed Framework, I'd like to have the situation fixed. Is there a way to safely debug Xposed Framework startup? I have just several seconds after the launcher starts, before I get a system frozen.
Thanks in advance for any wise advice.
Related
I wish I could explain better what I did, but I can't figure out what it might be.
I am running Captivate rooted, mostly stock 2.2 with a modded camera app, and sideloaded apps allowed (for the Amazon market). The behavior is this:
Phone takes about 5 minutes to boot, was previously booting in maybe 1-2 minutes before launcher comes up. Launcher loads and i have a slow but usable phone for 30 seconds then phone freezes, and maybe a few minutes later, launcher will restart. this whole time, i am getting double vibrate every few seconds, like something is freezing/crashing in the background (that's my best guess). I disabled all Widgets in both launchers and it does not hookup via USB once it freezes, but will charge.
This is happening with Samsung TWlauncher and with LauncherPro. Thinking this was a LauncherPro issue, I switched default launcher to TW, but same behavior occurred. I also uninstalled LauncherPro, but still no change in behavior for default launcher. I would like to try to get back to a usable phone, or if worse comes to worse, get my data off the phone before reinstalling either stock, CM7, etc. I do not have a phone recovery as I could never seem to get the clockwordmod recovery to install, so I only have reset user settings as an option from default recovery mode.
The only thing I can remember doing when this started was changing LauncherPro memory presets to see if it would stop restarting often, so I thought maybe LauncherPro was the issue, but it does not appear to be.
I reinstalled LP during a few hour period of usability, but then it occurred again and it took all day to have the right moment of unlocking my phone and getting to be able to uninstall LP before it froze again. If I wait too long to unlock, it is frozen until I restart or pull battery and try again at first bootup before the launcher goes crazy.
My main question is this:
Is there a way to determine which app is causing the problem, pull logs, etc. when the phone is off, and does not connect on USB (when it's frozen)?
If not, is there a way to pull data under same circumstances? (I'm guessing this is tied into the first answer)
If these all fail, I guess I will probably go to CM7 and try that out, but I have a hard time finding out what known issues there are as it still appears in unofficial status, since there's no downloads from the Cyanogenmod site.
Any help or advice is greatly appreciated. This has been a hard one to search for, so if anyone knows of other instances of situations like this, I would be glad to see what else was encountered. If I have this in the wrong forum, please forgive me.
Came home from dinner tonight and set my phone down on the nightstand, went downstairs. Came back up, phone is dead...plugged in, but now I can't do anything. Every time it boots (even in safe mode) I get process system not responding and the phone is stuck. I can't do anything from this point.
No issues at all up to this point...it's like the phone just randomly self destructed. What do I do? I'm still on 5.1, no recent backup because like I said I had been having no issues at all....I am rooted with xposed, amplify and greenify, if that makes a difference. Stock 5.1 otherwise...
I did try booting to recovery and wiping cache...no dice. Did the android is starting with upgrading apps thing, but then back to this nonsense again...
HELP PLEASE!
Install a ROM or flash factory image with fastboot.
Assuming you left USB Debugging and OEM Unlock enabled in Developer Options, your best bet is to flash a new ROM.
EDIT: @scryan beat me to it.
interestingly, i was able to get it to boot long enough this morning to (slowly, between all the 'not responding' messages) get it to disable everything in xposed and reboot again...now it seems to be working. seems something in one of the xposed modules completely borked the system. any idea how that could happen after running smoothly forever really?
also strange, it seems most of my settings have gone back to factory...for example, i use chomp for sms, but on the reboot it's bringing up both chomp and messenger notifications (even though i had chomp set as the default SMS client).
edit: it was amplify causing the issues, it seems. there must be something in the new version that fubar'd my phone. i turned every module back on except amplify, and the phone is good again...
crackers8199 said:
interestingly, i was able to get it to boot long enough this morning to (slowly, between all the 'not responding' messages) get it to disable everything in xposed and reboot again...now it seems to be working. seems something in one of the xposed modules completely borked the system. any idea how that could happen after running smoothly forever really?
also strange, it seems most of my settings have gone back to factory...for example, i use chomp for sms, but on the reboot it's bringing up both chomp and messenger notifications (even though i had chomp set as the default SMS client).
edit: it was amplify causing the issues, it seems. there must be something in the new version that fubar'd my phone. i turned every module back on except amplify, and the phone is good again...
Click to expand...
Click to collapse
Perfect chance to update to 6.0
I seem to have been bitten by whatever it is that's causing Note 8s to freeze. In my case, it seems to freeze when idle - case closed, always-on display showing a clock. Sometimes the digital clock - just stopped; the last time, the analog clock with the second hand ticking, but an otherwise unresponsive phone.
It seems like this is happening to other people, in a variety of other applications - and the only advice anybody is giving is to see what happens in safe mode, then uninstall applications one-by-one. All of which seems rather time-consuming, and counter-intuitive -- if a single App is freezing the system, that suggests on o/s or hardware issue -- the o/s should be isolating the rest of the system from app misbehavior.
Which leads me to wonder how one might track down what's actually going on. If this were one of our servers, I'd crank up logging and look at crash logs. But... those options don't seem to be available without rooting the phone. (Why does Google insist on making syslogs unreadable by normal users - that puts a big crimp in the ability to do any kind of real trouble diagnosis.)
Any suggestions on how to do crash analysis? Any tools that someone can recommend?
Any insight on the matter?
I have not had this problem, so I would not know how to tackle all down to pinpoint the exact culprit, but I would start by controling what apps I dont want to run in background, in maintenance>battery>always sleeping, I put all the apps I dont need to be in always running state, I would also try to unistall or freeze apps I installed just before the problem began, if you have bk disabler this is a rather easy process, as you can batch-disable/enable apps, in the end it is a trial-error exercise
You can use logcat extreme, Catlog or somthing similiar from playstore. But you need some knowless to see wat happend and root. Perhaps you can pull the log file without root to your computer with ADB.
Sounds like impending motherboard failure. My wife's S7 Edge started doing the same thing then one day it just wouldn't start up at all.
Common thing for Samsung phones unfortunately .... and if you're out of warranty they won't repair without a charge.
Ever since Android 11, of which I am running Magisk, I have lately been getting these strange occurrences where my device will stop loading apps and slowly things will start breaking down in the system UI. If I try opening an app that is not already opened, it will simply keep me on the screen I was on, such as the lock screen or the notification shade, and tapping on the screen does nothing. I can swipe up to go to home then, and when I open recants it shows me the app with a transparent or black window. Then things such as screenshotting, screen recording, and the settings app will stop working, so I cannot try to force close an app. Because of this, its somewhat difficult to demonstrate and record. If I close an app that was open before the lockup and try to reopen it, that app meets the same fate.
The only way to revert these changes is with a reboot, and I haven't seen it occur when I have Magisk disabled. But it does take a few days of the device not being rebooted (which I have a habit of doing) to occur.
I've seen the same things on occasion... though I also had EdXposed installed, so I blamed it on that.
Eventually all the issues started stacking up and I decided to do my first ever factory reset and install fewer things. Hasn't been set up long enough to decide what's fixed. Though the factory reset caused a bunch of other issues, which annoys me.
Ever figure this one out?
Hello everyone, I'm just curious to know if anyone knows how to fix this issue: when I unplug my phone and shut the screen off right after, my phone simply freezes in the state that its in. I know its frozen because if I have my flashlight on it stays on and nothing responds (touches, buttons, fingerpring sensor, etc), but it will not freeze if I have music playing for some reason and the only way to get access to my phone again is to forcefully restarting it (by holding down power for about 10s, which is really annoying). If anyone can help me with this I would really apreciate it. Ps: my phone is a Moto G6 (ali). I know that doing a factory reset fixes it, but right after I re root it and install my apps it starts doing it again. Below is a screenshot with all my root apps.
IuriP said:
Hello everyone, I'm just curious to know if anyone knows how to fix this issue: when I unplug my phone and shut the screen off right after, my phone simply freezes in the state that its in. I know its frozen because if I have my flashlight on it stays on and nothing responds (touches, buttons, fingerpring sensor, etc), but it will not freeze if I have music playing for some reason and the only way to get access to my phone again is to forcefully restarting it (by holding down power for about 10s, which is really annoying). If anyone can help me with this I would really apreciate it. Ps: my phone is a Moto G6 (ali). I know that doing a factory reset fixes it, but right after I re root it and install my apps it starts doing it again. Below is a screenshot with all my root apps.
Click to expand...
Click to collapse
I have this exact same problem. I have 2 moto's. It occurs on both of them. Never happened till I rooted.
You should disable all of those apps ( especially substratum) and see if the problem still happens. Then if it doesn't, activate one by one till it happens again. Then with the culprit found, look in internet if it has any conflicts to another app you have installed. If you find maybe they have like a patch to download or a modified version. If not you'll have to let one of them go. Or maybe there's no conflict with any other app and it's just that one misbehaving. Disable all other apps and let only the culprit activated. Does it still bug? you can try reinstalling the app or uninstalling it.