Related
I would like to start this out by saying that I have had my Bravo since January 16, and have loved every minute of it. This has been my first Android (Came over from my iPhone 3G). I was extremely excited to finally get the upgrade to 2.2, even though I decided to wait to officially download it OTA.
Since I got my phone, I had no more than three to five apps force close on my using the stock launcher. I rarely noticed much of any lag while working with my phone, and I never once had any issues with the phone rebooting itself on me.
Since I updated my phone on Saturday I've been plagued with all of these issues. Immediately after updating, I noticed my phone was running very hot, and my battery drained to 50% within an hour or two without me even running anything stressful on it. I restarted it twice and since then I haven't noticed any significant issues with my battery, or the phone seeming to run it's processor excessively.
But, I have constant lag, making tasks that were extremely quick and easy before the weekend be significantly more difficult and frustrating. Today I've even noticed that the lag is so bad that I am not even able to use Swype because the phone takes so long to register any touch's it doesn't register anything other than the first and last letter I swyped across. In addition, my phone has rebooted itself 3 times within the last three days I've been using it, an issue that has not happened once in the three months before this weekend.
I will regularly be trying to do things on my phone and it will lag, causing the phone to freeze for 20-30 seconds at a time, and then trying to perform every touch it received in those 20-30 seconds in a scant second after it recovers.
I have noticed some issues not regarding lag, but sometimes it has been difficult for my phone to initiate calls. I have tried to call my wife, and it took 5 times before the call would finally go through, it was immediately ending the call right after I pressed the call button.
I love my phone and the capabilities of the Android system. Until now I haven't had any problems at all with it. Can you help me try to figure out what's happening, and if there are any ways to fix my phone? I haven't gotten around to rooting my phone since I've gotten it, but have been planning on it.
roadkizzle said:
I would like to start this out by saying that I have had my Bravo since January 16, and have loved every minute of it. This has been my first Android (Came over from my iPhone 3G). I was extremely excited to finally get the upgrade to 2.2, even though I decided to wait to officially download it OTA.
Since I got my phone, I had no more than three to five apps force close on my using the stock launcher. I rarely noticed much of any lag while working with my phone, and I never once had any issues with the phone rebooting itself on me.
Since I updated my phone on Saturday I've been plagued with all of these issues. Immediately after updating, I noticed my phone was running very hot, and my battery drained to 50% within an hour or two without me even running anything stressful on it. I restarted it twice and since then I haven't noticed any significant issues with my battery, or the phone seeming to run it's processor excessively.
But, I have constant lag, making tasks that were extremely quick and easy before the weekend be significantly more difficult and frustrating. Today I've even noticed that the lag is so bad that I am not even able to use Swype because the phone takes so long to register any touch's it doesn't register anything other than the first and last letter I swyped across. In addition, my phone has rebooted itself 3 times within the last three days I've been using it, an issue that has not happened once in the three months before this weekend.
I will regularly be trying to do things on my phone and it will lag, causing the phone to freeze for 20-30 seconds at a time, and then trying to perform every touch it received in those 20-30 seconds in a scant second after it recovers.
I have noticed some issues not regarding lag, but sometimes it has been difficult for my phone to initiate calls. I have tried to call my wife, and it took 5 times before the call would finally go through, it was immediately ending the call right after I pressed the call button.
I love my phone and the capabilities of the Android system. Until now I haven't had any problems at all with it. Can you help me try to figure out what's happening, and if there are any ways to fix my phone? I haven't gotten around to rooting my phone since I've gotten it, but have been planning on it.
Click to expand...
Click to collapse
Something probably is messed up in the upgrade process.
Simple solution, flash the 2.2 sbf and you should be good.
roadkizzle, Something doesn't sound right at all with your update. I would try to remove the battery for a minute and reboot. If you still have issues I would try a factory data reset. If that doesn't cure your ills then flashing the 2.2sbf as bandroidx suggested may be in order.
Alright, I flashed the SBF file to the phone through RSDLite, and from what I can see it went through correctly. My only question now is do you think I'll need to try to re-install the full update? Or is that similar to what I did?
roadkizzle said:
Alright, I flashed the SBF file to the phone through RSDLite, and from what I can see it went through correctly. My only question now is do you think I'll need to try to re-install the full update? Or is that similar to what I did?
Click to expand...
Click to collapse
flashing the sbf already updated your phone to 2.2. You don't need to do anything else
I hope reflashing did the trick for you. That experience sounds nasty...
Sent from my MB520 using XDA App
Well, after a couple of hours of playing with my phone it's seeming better. I have been playing a few games of Worms, and my normal surfing the internet and so far I haven't noticed any real lag. The test will be my day through tomorrow.
I was just really confused because I was following the instructions from the Flashing SPRecovery SBF to a Motorola Droid youtube video, and his SBF file really seemed to only change the recovery screen. It looked like he still had to go through the actual update.zip process to make the actual updates to his phone.
Alright it's official, flashing the sbf did not fix the lag issues. My phone hasn't had a critical malfunction and reboot itself yet today, but the lag is unbearable.
roadkizzle, It sounds like you are still having issues. If you look at the system version in "about phone" in settings menu does it say version 37.4.0.MB520??
Yes, it says Version.37.4.0.MB520.ATT.en.US
roadkizzle said:
Alright it's official, flashing the sbf did not fix the lag issues. My phone hasn't had a critical malfunction and reboot itself yet today, but the lag is unbearable.
Click to expand...
Click to collapse
what apps do you have installed?
look in task master and get rid of any auto-ends and reboot and see if that makes a difference
Well, immediately after removing the AT&T apps from the auto-end list and rebooting, I thought I noticed some lag initially, but I've let it run for a few days now doing everything I was before and I've not been having any of those issues recently.
I'm not sure what it was. I wasn't very aggressive adding apps to my auto-end list, really just Maps and the AT&T apps. I added maps after a while because when I would use it once it would stay open and I'd notice later on that it would have been a major consumer of my battery, and I couldn't figure out how to close it fully.
Glad to hear things are going better. I had some issues totally unrelated to the apps I had in auto-end but pulling all of them off of auto-end got rid of the issues. Froyo is supposed to minimise the need for having to add apps to auto-end in task manager. Regards
(SIA for the long post)
roadkizzle - my situation sounds very similar to yours and I wanted see if you are also seeing a couple of other symptoms I've seen beyond what you have indicated. This has been an issue from early on for me. At first it seemed to be associated to when the battery was low, but it is now ever increasingly interrupting my use of the phone. I was hoping 2.2 might resolve some of this, but it hasn't.
Background: Purchased/activated phone early Jan 2011; recently upgraded to the 2.2 sys and used the official channels; all apps I've added are lightweight stuff (ex: notepad-type stuff, weather widget) and I have pushed most unused stuff to the auto-end list.
Similar symptoms: I see the same power drain and high CPU usage when using maps/navigator (really evident on a recent trip). Still monitoring if some of that can be attributed to use of the GPS.
I'm getting a similar lag though I wish it was only for the short period you are seeing. I've only rarely been able to just put the phone down and have it responsive when I get back to it. Maps/Navigator were especially susceptible to this problem, and it seemed consistent with the 90%+ CPU usage often seen when they are running.
I don't use swipe, but the keypad is most often what is being used when the lag kicks in... the entire phone just goes completely unresponsive, including any and all other input such as the hardware home/back keys, etc.
In addition: Better than half the time that the qwerty touchpad becomes unresponsive, I see sporadically entered random keystrokes to my messages... everything from initiating the voice input to entering several dozen spaces or just simple random characters. This happens at a random, often changing rate and I see the keys lighting up and the haptic responses happen as if I were touching the keys, but they are not from any delay in the input. Once ruling out an exorcism, this has started me thinking I might have a hardware issue with the touchpad. The phone has not been dropped or roughed up in any way, so if it is HDWR, it's a manuf issue.
Luckily.... in 99% of the cases where this happens, using the HDWR power button to cycle the screen through a sleep and back resolves the issue. Not a big deal unless you have to do it 3 times to send one text/mail. This has me constantly thinking about items on the auto-end list but I have not unearthed anything to support that.
The other 1% of the time I have had to reboot the phone, but in those cases I can't rule out 'user issues' due to just pure frustration. Task Manager has become my most freq used app, but often I see everything at 0% CPU and/or not running.
I'm wondering if any of these additional symptoms sound familiar...
thx.
humanque said:
(SIA for the long post)
roadkizzle - my situation sounds very similar to yours and I wanted see if you are also seeing a couple of other symptoms I've seen beyond what you have indicated. This has been an issue from early on for me. At first it seemed to be associated to when the battery was low, but it is now ever increasingly interrupting my use of the phone. I was hoping 2.2 might resolve some of this, but it hasn't.
Background: Purchased/activated phone early Jan 2011; recently upgraded to the 2.2 sys and used the official channels; all apps I've added are lightweight stuff (ex: notepad-type stuff, weather widget) and I have pushed most unused stuff to the auto-end list.
Similar symptoms: I see the same power drain and high CPU usage when using maps/navigator (really evident on a recent trip). Still monitoring if some of that can be attributed to use of the GPS.
I'm getting a similar lag though I wish it was only for the short period you are seeing. I've only rarely been able to just put the phone down and have it responsive when I get back to it. Maps/Navigator were especially susceptible to this problem, and it seemed consistent with the 90%+ CPU usage often seen when they are running.
I don't use swipe, but the keypad is most often what is being used when the lag kicks in... the entire phone just goes completely unresponsive, including any and all other input such as the hardware home/back keys, etc.
In addition: Better than half the time that the qwerty touchpad becomes unresponsive, I see sporadically entered random keystrokes to my messages... everything from initiating the voice input to entering several dozen spaces or just simple random characters. This happens at a random, often changing rate and I see the keys lighting up and the haptic responses happen as if I were touching the keys, but they are not from any delay in the input. Once ruling out an exorcism, this has started me thinking I might have a hardware issue with the touchpad. The phone has not been dropped or roughed up in any way, so if it is HDWR, it's a manuf issue.
Luckily.... in 99% of the cases where this happens, using the HDWR power button to cycle the screen through a sleep and back resolves the issue. Not a big deal unless you have to do it 3 times to send one text/mail. This has me constantly thinking about items on the auto-end list but I have not unearthed anything to support that.
The other 1% of the time I have had to reboot the phone, but in those cases I can't rule out 'user issues' due to just pure frustration. Task Manager has become my most freq used app, but often I see everything at 0% CPU and/or not running.
I'm wondering if any of these additional symptoms sound familiar...
thx.
Click to expand...
Click to collapse
Try taking things off of the auto-end list. You shouldn't need the task killer because android manages apps on its own (it's supposed to manage apps better in froyo than in 2.1)
I've also had lag, especially when opening maps (the first time I open maps it often force closes).
Can anyone get the "lock pattern" screen without the slide to unlock? It seems like a common "Motorola 2.2" issue, but I can't figure out if it gets resolved through an update or not
kyngnothing said:
I've also had lag, especially when opening maps (the first time I open maps it often force closes).
Can anyone get the "lock pattern" screen without the slide to unlock? It seems like a common "Motorola 2.2" issue, but I can't figure out if it gets resolved through an update or not
Click to expand...
Click to collapse
it can be fixed through the settings.db in the com.android.providers.settings, but i dont remember what to edit inside.
or you can download No Lock from the Market
https://market.android.com/details?id=org.jraf.android.nolock
jorgonv said:
it can be fixed through the settings.db in the com.android.providers.settings, but i dont remember what to edit inside.
or you can download No Lock from the Market
Click to expand...
Click to collapse
NoLlock just seems to turn the lock screen on and off altogether?
I can get the screen lock on and off, I just can't get the pattern lock without the side-to-side swipe lock at the same time
This is messing with
PS . If you can't get your screen to stop locking all the time with froyo 2.2.1dissable it in the same location ID # 61 screen_lock set to 0. ),
Click to expand...
Click to collapse
and the settings menus.
There are several other seemingly lock-related database settings, but I'm worried about locking myself out
kyngnothing said:
NoLlock just seems to turn the lock screen on and off altogether?
I can get the screen lock on and off, I just can't get the pattern lock without the side-to-side swipe lock at the same time
This is messing with
and the settings menus.
There are several other seemingly lock-related database settings, but I'm worried about locking myself out
Click to expand...
Click to collapse
You can always sbf if you get locked out. your data will also be kept
I've been having an issue where my phone will get the sleep of death (SOD), generally from trying to turn the screen on too quickly after turning it off, or if the device gets too hot in general. Occasionally the SOD is accompanied with some data loss, my wallpaper will reset to stock, and old sms messages will be will pop up in notifications as if they are new (and it is a stock messaging notification, not my default messaging app). This has happened on both CM based custom roms and stock roms. It generally become more common the longer I stay on the rom setup, so I haven't been able to pin it to one modification (although I have many). Now on C-rom there has been another problem, when I reboot the LG screen comes on normally but slowly loses contrast and greys out, which kind of worries me given some of the screen issues I've heard about.
Has anybody had issues like this? Any tips would be appreciated
Hello,
I have been having issues with the opendelta for past couple of times i decided to update. It goes till a certain stage, which varies every time, like verifying file, downloading, etc and then suddenly says that it's up to date. I have tried many times and the problem persists.
I have updated manually couple of times so wanted to know if this is a known issue or can i do something about it.
Sent from my GT-N7000 using Tapatalk
I'd been having similar problems. I could always make it update in the end with enough attempts, but it was a nuisance. Then I switched to using CyanDelta from the Play Store, I think it's the same method, maybe even the same developer involved. It's been very reliable.
opendelta is broken.
Most of the time, my Note 7 is instantly responsive no matter how heavily loaded it is.
Every few hours, though, it gets into a mode with serious UI-feedback lag. In this mode, when I tap any key or icon, the corresponding click-and-vibration feedback is delayed by up to one or two seconds. Often I can type several characters with no feedback, followed a second later by a rapid-fire sequence of the delayed clicks and vibrations.
When the phone is in lag mode, the lag occurs in all apps and with both keyboards I've tried (Samsung and Google). And it's not just during typing; tapping on any icon produces the same lag. Lag mode is not fixed by closing all apps, turning on Airplane mode, clearing the clipboard, switching to a different keyboard app, or clearing the keyboard cache or data. (Clearing the clipboard did seem to fix the problem on one occasion, but not subsequently.)
Rebooting the phone does fix the problem--until it comes back again a few hours later. I've tried booting into recovery and clearing the system cache, but the problem still comes back in a few hours. I have not had time to try a factory reset. But the phone is completely stock (APH1), no power-saving turned on, no debloating or esoteric settings or apps.
As I said above, most of the time the phone doesn't have this problem, no matter how many apps are running. And when the lag occurs, the phone is not hot and is not draining the battery. So it's not a matter of the phone being overloaded; rather, it's a specific bug in the UI feedback.
The problem arises at seemingly random times. I have not noticed any pattern as to what triggers it.
Here's a video demonstrating the problem, both for typing and for icon-tapping:
https://vid.me/iYya
And just for contrast, here's a video of the phone when it's working properly, with no UI-feedback delay:
https://vid.me/GF82
Again, when the phone is in lag-mode, it lags in all apps, for typing and for all icon-taps, etc. The videos show only one particular app for illustration.
Gary02468 said:
Most of the time, my Note 7 is instantly responsive no matter how heavily loaded it is.
Every few hours, though, it gets into a mode with serious UI-feedback lag. In this mode, when I tap any key or icon, the corresponding click-and-vibration feedback is delayed by up to one or two seconds. Often I can type several characters with no feedback, followed a second later by a rapid-fire sequence of the delayed clicks and vibrations.
When the phone is in lag mode, the lag occurs in all apps and with both keyboards I've tried (Samsung and Google). And it's not just during typing; tapping on any icon produces the same lag. Lag mode is not fixed by closing all apps, turning on Airplane mode, clearing the clipboard, switching to a different keyboard app, or clearing the keyboard cache or data. (Clearing the clipboard did seem to fix the problem on one occasion, but not subsequently.)
Rebooting the phone does fix the problem--until it comes back again a few hours later. I've tried booting into recovery and clearing the system cache, but the problem still comes back in a few hours. I have not had time to try a factory reset. But the phone is completely stock (APH1), no power-saving turned on, no debloating or esoteric settings or apps.
As I said above, most of the time the phone doesn't have this problem, no matter how many apps are running. And when the lag occurs, the phone is not hot and is not draining the battery. So it's not a matter of the phone being overloaded; rather, it's a specific bug in the UI feedback.
The problem arises at seemingly random times. I have not noticed any pattern as to what triggers it.
Here's a video demonstrating the problem, both for typing and for icon-tapping:
https://vid.me/iYya
And just for contrast, here's a video of the phone when it's working properly, with no UI-feedback delay:
https://vid.me/GF82
Again, when the phone is in lag-mode, it lags in all apps, for typing and for all icon-taps, etc. The videos show only one particular app for illustration.
Click to expand...
Click to collapse
Yes this pretty much seems to be happening across Note7...hope Samsung fixes this
Sent from my SAMSUNG-SM-N930A using Tapatalk
I exactly have the same issue u clearly described above. My phone lags intermittently and no matter what I do, it doesn't go away. After some time, magically it comes back to normal.
Not sure how to fix this.. very frustrating!
Sent from my SAMSUNG-SM-N930A using Tapatalk
Same thing for me as well. I've heard whispers it's an AT&T thing. Been trying to fix by turning off Battery Optimizer for certain apps and using package disabled. I've noticed it's most consistently caused by locking and unlocking again within a specific time window. Like if you're using the phone, then you put it to sleep, and come back within about 10 min, it does it's lag mode.
If anyone who's having this specific UI-lag problem tries a factory reset, please report whether or not the problem comes back after that.
I did the factory reset multiple times but it didn't solve the lag issue..
Sent from my SM-N930P using Tapatalk
Sameer3.b said:
I did the factory reset multiple times but it didn't solve the lag issue..
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
After the factory reset, did you restore using backups (e.g., smart switch, directly transferring SD card) or did you set up as a new phone. I was having very bad lag. I used Smart Switch the first time. After a factory reset and rebuilding from scratch (without Smart Switch) my lag problem is gone. There is some discussion of this over at Android Central.
GeorgeP said:
After the factory reset, did you restore using backups (e.g., smart switch, directly transferring SD card) or did you set up as a new phone. I was having very bad lag. I used Smart Switch the first time. After a factory reset and rebuilding from scratch (without Smart Switch) my lag problem is gone. There is some discussion of this over at Android Central.
Click to expand...
Click to collapse
I set it up as a new phone and didnt use smart switch.
Sent from my SAMSUNG-SM-N930A using Tapatalk
This lag seems to be AT&T specific
Sent from my SAMSUNG-SM-N930A using Tapatalk
Sameer3.b said:
I did the factory reset multiple times but it didn't solve the lag issue.
Click to expand...
Click to collapse
Sameer3.b said:
I set it up as a new phone and didnt use smart switch.
Click to expand...
Click to collapse
Thanks. That's disappointing but important to know, both diagnostically and also to save everyone else the effort of duplicating the attempt.
I'd be very curious to see if an unlocked (no AT&T bloat) N7 has the same issue on AT&T. If I get a N7, I'm hoping to wait until unlocked versions become available.
I have the same problem. It's the only thing I don't like about the phone. Hopefully they will update it soon.
All samsung phones has that. A new custom rom will fix it.
Same problem, sprint... Stock, TouchWiz. Switched to nova and it doesn't seem to have helped much.
I'm finding the problem may be gone. It hasn't shown up in the last 48 hours (compared to several times a day up until then).
There's nothing I'm aware of doing differently now, other than having turned off Report Diagnostic Info in Settings|General Management. I'm skeptical that that has anything to do with the reversal (but not quite skeptical enough to try turning it back on just yet).
Perhaps the improvement is due to an app update, or perhaps it's a delayed effect of clearing the system cache (though the problem did crop up once or twice after the cache-clearing, before it stopped occurring). Has anyone else seen the problem go away?
UPDATE: The feedback-lag returned after about 60 hours. Again, no obvious trigger. Very annoying.
Hi guys,
I am having similar issues. Most of the times the UI is pretty smooth, but intermittently it starts lagging, opening apps takes 1-2 secs and scrolling the pages isnt smooth, its very annoying esp considering the device is barely few days old. Need some fix to this, or its a dead investment!
pranavsukh said:
I am having similar issues. Most of the times the UI is pretty smooth, but intermittently it starts lagging, opening apps takes 1-2 secs and scrolling the pages isnt smooth
Click to expand...
Click to collapse
Wait, are you talking about the same feedback problem that this thread is about? Taking a second to load an app isn't necessarily unreasonable. But a one-second lag for haptic feedback defeats the whole purpose of the feedback and is clearly a bug.
Gary02468 said:
Wait, are you talking about the same feedback problem that this thread is about? Taking a second to load an app isn't necessarily unreasonable. But a one-second lag for haptic feedback defeats the whole purpose of the feedback and is clearly a bug.
Click to expand...
Click to collapse
What i mean is that the lag isnt just restricted to feedback, the phone seems to stutter overall, scrolling on pages and apps is jittery. And this is noticeable since when it doesn't occur the phone is buttery smooth! I tried the google now launcher and it still persists. Turning the animations to 0.5x didnt help either.
Oh ok. Yeah, I'm using the Google Now launcher too. For me, the lag problem disappeared about 58 hours ago though. Just out of curiosity, do you have Report Diagnostic Info enabled in Settings|General Management?
UPDATE: The lag came back after about 60 hours.
Just for completeness, I should mention that after the phone went into lag mode, I also tried turning haptic/audio feedback off and then back on. But the lag did not stop.
6P - Rooted, Stock, Xposed w/Amplify, Greenify, & Gravity Box.
Android v. 6.0.1 w/ 8/5/16 Security Patch.
Build number MTC20F.
Kernel version 3.10.7.-g909746b.
I'm getting 2 or 3 Sleep of Death (SOD) occurrences a day. Fingerprint scanner, nor power button press wakes it. I have to do a hard reset to turn it back on. I did a factory wipe about two weeks ago when it was getting to be that every time it slept it wouldn't wake up and it was better for a short while, but it's popping up again.
My research has shown that apps can cause it, but I have no way of narrowing down what's causing it at all. It's getting super frustrating at this point.
So my questions are:
1) Is there a way to figure out what's causing the SOD? I can't seem to find a pattern or figure out what's triggering it, so it's not like I can turn a logger on to figure it out before it happens.
2) Once I figure it out, what can I do about it? Or is there something I can do to prevent it without figuring out what directly is causing it?
Hopefully there's a solution that's obvious that I'm missing here. I'd rather not go through the factory reset process again, as it happened again after I reset the last time.
Help is sorely needed.
I use gravity box but not greenify. I use Recently instead of greenify with no problems. Not sure what Amplify is but I use the XML hack to raise headphone volume. Hope this helps.
RRuszczyk said:
6P - Rooted, Stock, Xposed w/Amplify, Greenify, & Gravity Box.
Android v. 6.0.1 w/ 8/5/16 Security Patch.
Build number MTC20F.
Kernel version 3.10.7.-g909746b.
I'm getting 2 or 3 Sleep of Death (SOD) occurrences a day. Fingerprint scanner, nor power button press wakes it. I have to do a hard reset to turn it back on. I did a factory wipe about two weeks ago when it was getting to be that every time it slept it wouldn't wake up and it was better for a short while, but it's popping up again.
My research has shown that apps can cause it, but I have no way of narrowing down what's causing it at all. It's getting super frustrating at this point.
So my questions are:
1) Is there a way to figure out what's causing the SOD? I can't seem to find a pattern or figure out what's triggering it, so it's not like I can turn a logger on to figure it out before it happens.
2) Once I figure it out, what can I do about it? Or is there something I can do to prevent it without figuring out what directly is causing it?
Hopefully there's a solution that's obvious that I'm missing here. I'd rather not go through the factory reset process again, as it happened again after I reset the last time.
Help is sorely needed.
Click to expand...
Click to collapse
I think the best way to diagnose and pinpoint the issue would be by obtaining logs. Haven't used xposed in a while though I think it has a log mechanism you can refer to. If you check the logs for keywords such as "error", "reboot", or "restart, etc. that may narrow down the processes causing the issue.
blitzkriegger said:
I think the best way to diagnose and pinpoint the issue would be by obtaining logs. Haven't used xposed in a while though I think it has a log mechanism you can refer to. If you check the logs for keywords such as "error", "reboot", or "restart, etc. that may narrow down the processes causing the issue.
Click to expand...
Click to collapse
Just checked. The logs are automatically cleared when the phone reboots or resets, so no way I can tell to get the logs before the SOD occurs.
RRuszczyk said:
Just checked. The logs are automatically cleared when the phone reboots or resets, so no way I can tell to get the logs before the SOD occurs.
Click to expand...
Click to collapse
Then try to capture a system-wide log instead. This article may help. Do the logcat after you have experienced the bug. I'm sure it will point out what's causing the issue.
Other than taking the logcat approach you can try eliminating possible culprits. If you suspect it may either be amplify or gb then temporarily disable each module within xposed then observe if the problem persists.