I've been getting these weird "flashes". Sometimes the screen actually flashes white and sometimes not, but when it happens (once every few minutes or sometimes even several times a minute), if I'm in Chrome, the bar will appear, if I'm in an IM app the keyboard will disappear and reappear and then if I continue typing, it moves the cursor to a random spot in my typed passage and replaces a word with the last word I typed, if I'm in the YouTube app, the video will restart, if I'm watching a video in the normal video player, the video will pause, etc. This has happened on two Moto Xs after rooting. I tried disabling every customization I instaled (a few Xposed modules) and I still had the problem. The PwnMyMoto root has to be the cause, unless I'm missing something. Any ideas on how to get these to go away?
Slusho,
That is not normal, nor is it happening to my rooted+SS Moto X.
I recommend flashing back to stock and starting over. The problem could be hardware related, but based on your description it sounds like software.
I am not experiencing this issue either. I'm on stock and rooted with PwnMyMoto. I would go with what Ctrl-Freak said. Try going back to stock.
Because I've experienced this on every device I root, how would going back to stock and rerooting fix it? It's certain to happen again.
Slusho said:
Because I've experienced this on every device I root, how would going back to stock and rerooting fix it? It's certain to happen again.
Click to expand...
Click to collapse
You should go back to stock and not reroot to see if it is truly root that is causing the problem.
Dark9781 said:
You should go back to stock and not reroot to see if it is truly root that is causing the problem.
Click to expand...
Click to collapse
Okay I'm trying it. I have to back everything up, unroot, check if it's still happening, root, check if it's still happening, and restore everything. It'll take a while. I don't think I can just back up in one fell swoop like on custom recoveries, right?
Okay I've confirmed it doesn't happen when not rooted (as it didn't before). Moving to root...
...and it isn't happening. Strange. I'll enable the Xposed modules now, but I already troubleshot that, so it shouldn't cause it.
And that didn't cause it to happen either. I don't know what's changed, and this mystery will haunt me for the rest of my days...
Thanks though.
I went to bed and it was fine, but I wake up and my phone's back to doing the flashes. Another thing is that I freeze Updater but the update dialog still pops up. I doubt they're related but I guess I should mention it.
Sounds to me like a faulty digitizer. Had similar issue with previous device. Sometimes wouldn't happen for months. Some ROMs seemed to provoke it more as well. When it happens again, go into dev options and select show touches or grab a painting/drawing app off play. Run the app when its acting up and you may see it drawing by itself. That or your phones haunted, it is almost Halloween.
Tried it, and it didn't register any touches. These things that happen can't happen due to touches anyway. And this has happened on every Moto X I've rooted. Perhaps it won't happen if I use the old root method?
The problem is present with the old root too. Guess I just can't have root on my Moto X.
Slusho said:
The problem is present with the old root too. Guess I just can't have root on my Moto X.
Click to expand...
Click to collapse
I'm sure you are tired of troubleshooting but, no one else is reporting having this problem. So its either something you are setting up on your phone, or you should return your phone. It may have something to do with what you are restoring after you root.
jayboyyyy said:
I'm sure you are tired of troubleshooting but, no one else is reporting having this problem. So its either something you are setting up on your phone, or you should return your phone. It may have something to do with what you are restoring after you root.
Click to expand...
Click to collapse
I'm only restoring normal Play Store apps that I doubt are doing this, Xposed, MotoXposed, Gravity Box, and Advanced Power Menu. I tried disabling those and it didn't stop the flashing, so I didn't think it was the Xposed modules, but I'll try wiping and rerooting my phone without those. If that doesn't work, I'll just use it unrooted. Does anyone know of some diagnostic software that could detect what's doing this? Also, this has happened on multiple devices and only after rooting so I don't see how it could be a hardware problem.
Slusho said:
I'm only restoring normal Play Store apps that I doubt are doing this, Xposed, MotoXposed, Gravity Box, and Advanced Power Menu. I tried disabling those and it didn't stop the flashing, so I didn't think it was the Xposed modules, but I'll try wiping and rerooting my phone without those. If that doesn't work, I'll just use it unrooted. Does anyone know of some diagnostic software that could detect what's doing this? Also, this has happened on multiple devices and only after rooting so I don't see how it could be a hardware problem.
Click to expand...
Click to collapse
perhaps you are using the wrong root exploit?
jayboyyyy said:
perhaps you are using the wrong root exploit?
Click to expand...
Click to collapse
I've used both of jcase's Moto X root exploits.
jayboyyyy said:
perhaps you are using the wrong root exploit?
Click to expand...
Click to collapse
Slusho said:
I've used both of jcase's Moto X root exploits.
Click to expand...
Click to collapse
I think jayboyyyy meant was did you grab the right one for your carrier?
Sent from my Moto X
Slusho said:
. Does anyone know of some diagnostic software that could detect what's doing this? Also, this has happened on multiple devices and only after rooting so I don't see how it could be a hardware problem.
Click to expand...
Click to collapse
Terminal emulator and logcat
Dark9781 said:
I think jayboyyyy meant was did you grab the right one for your carrier?
Sent from my Moto X
Click to expand...
Click to collapse
Oh. Yes, I did.
xxxo said:
Terminal emulator and logcat
Click to expand...
Click to collapse
I tried logcat with adb. I take it anytime it says "E/" there's an error. I tested it when Chrome makes the top bar appear randomly, and got a ton of
Code:
E/ActivityThread ]
Failed to find provider info for com.motorola.blur.setupprovider
I tried it while playing a video in the default video player and got a lot of
Code:
E/AwesomePlayer ]
LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec
as well as
Code:
E/OMX-VDEC-1080P
I got that a lot while playing YouTube as well.
These errors come up dozens of times a second. This is getting too low level for me to understand. I can't find the specific moment/problem since there are hundreds of lines generated for just a minute of logging.
Slusho said:
I tried logcat with adb. I take it anytime it says "E/" there's an error. I tested it when Chrome makes the top bar appear randomly, and got a ton of
Code:
E/ActivityThread ]
Failed to find provider info for com.motorola.blur.setupprovider
I tried it while playing a video in the default video player and got a lot of
Code:
E/AwesomePlayer ]
LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec
as well as
Code:
E/OMX-VDEC-1080P
I got that a lot while playing YouTube as well.
These errors come up dozens of times a second. This is getting too low level for me to understand. I can't find the specific moment/problem since there are hundreds of lines generated for just a minute of logging.
Click to expand...
Click to collapse
just to clarify, you did try rooting the device without running tibu to set your apps back up and you still ran into the issue? If it failed to find motorola blur stuff it seems that you may have restored some stuff with tibu accidentally that is screwing up some system apk's. I'm not sure this is the case, but again, you are the only one reporting this so in the end I still really feel it is something you are doing. The errors you are reporting should not be affected when rooting your phone unless you are altering something post root that you are unaware you are altering or that you think you aren't altering but in fact you are.
hi guys,
I'm working on CM-11-20140606-NIGHTLY.
currently I'm facing two problems:
1- when i plug my headset, if anyone calls ringing be in the headset it self, so if i'm not beside my note i'll never hear it.
i didn't face this issue in stock rom as ringing works with both mobile itself and headset at the same time.
so, is there any way i can follow to make it act as stock rom??
2- some times when i press home button to use it, soft buttons lightened but screen still black and no way to make mobile works again unless i restart it.
3- on stock rom i used to install xposed installer and apply "enable call recording" and was working flawlessly by replacing add button by record, now it doesn't work and need it sometimes.
any suggestions?
NaAZoOR said:
hi guys,
I'm working on CM-11-20140606-NIGHTLY.
currently I'm facing two problems:
1- when i plug my headset, if anyone calls ringing be in the headset it self, so if i'm not beside my note i'll never hear it.
i didn't face this issue in stock rom as ringing works with both mobile itself and headset at the same time.
so, is there any way i can follow to make it act as stock rom??
2- some times when i press home button to use it, soft buttons lightened but screen still black and no way to make mobile works again unless i restart it.
3- on stock rom i used to install xposed installer and apply "enable call recording" and was working flawlessly by replacing add button by record, now it doesn't work and need it sometimes.
any suggestions?
Click to expand...
Click to collapse
Hey there! Let's see:
1. I really have no idea what could be happening...try asking on the CM11-Nightlies Discussion forum or the devs at the Development thread.
2. Are you sure the screen STAYS black?? On my phone, I get the black screen with softkeys lighting up, but display turns on after a good 10 second lag...
3. What exactly is the problem here? Is the record button not displaying? Does the module support KitKat?
Try disabling the module>reboot>re-enable>reboot. If that doesn't help, uninstall and re-install the entire Xposed Framework.
Xposed-related problems don't usually get support but you can ask at the discussion thread linked above.
The Dork Knight Rises said:
Hey there! Let's see:
1. I really have no idea what could be happening...try asking on the CM11-Nightlies Discussion forum or the devs at the Development thread.
2. Are you sure the screen STAYS black?? On my phone, I get the black screen with softkeys lighting up, but display turns on after a good 10 second lag...
3. What exactly is the problem here? Is the record button not displaying? Does the module support KitKat?
Try disabling the module>reboot>re-enable>reboot. If that doesn't help, uninstall and re-install the entire Xposed Framework.
Xposed-related problems don't usually get support but you can ask at the discussion thread linked above.
Click to expand...
Click to collapse
1- I'll check above links, thanks.
2- may be i didn't wait for a whole 10 seconds, usually i restart it after a press or two.
will wait and check.
3- probably module isn't compatible as it was updated 25-7-2013.
I've tried uninstall and reinstall both module and Xposed framework.
many thanks for your interest.
NaAZoOR said:
1- I'll check above links, thanks.
2- may be i didn't wait for a whole 10 seconds, usually i restart it after a press or two.
will wait and check.
3- probably module isn't compatible as it was updated 25-7-2013.
I've tried uninstall and reinstall both module and Xposed framework.
many thanks for your interest.
Click to expand...
Click to collapse
You're welcome(though you COULD just hit the Thanks button next time, yknow )
And yeah, try waiting for a few seconds for the black screen problem...I'm pretty sure we're having the same problem...
Background - switched from xposed to Edxposed to get Google Pay to work. It does now work but caused buggy side effects.
1. System soft reboots directly after a manual boot completed but is then okay usually if left to settle.
2. Screen says always on, will not respond to display settings options set to 'off' after 1 min. It will off by power key, just not auto off.
3. One xposed module does't work at all (Niwatori One Handed Mode). Xposed Edge and Gravity work fine so far.
I have 2 devices, an LG V20, LG G5 both on Oreo and both exhibiting exact same problems. 1 device uses Edexposed Manager, the other Edxposed Installer. Is installer now obsolete?
So the One handed Mode is the biggest problem. Is there a way to look under the hood to fix a non working module? If I could fix the other problems maybe I could find an alternative app for one handed mode.
Okay well "HiddenCore module" (xposed module) was causing the screen to stay on. As I said I just installed it cause I saw it thinking maybe it was necessary for Gpay. Turns out I uninstalled it, the screen will now auto off, and Gpay still works.
Only issue now is the soft reboot after boot completed. Not a huge deal, maybe it will be resolved in an edxposed update, although I am now using the latest Canary alpha, alas no change.
Okay well "HiddenCore module" (xposed module) was causing the screen to stay on. As I said I just installed it cause I saw it thinking maybe it was necessary for Gpay. Turns out I uninstalled it, the screen will now auto off, and Gpay still works.
Only issue now is the soft reboot after boot completed. Not a huge deal, maybe it will be resolved in an edxposed update, although I am now using the latest Canary alpha, alas no change.
ezzony said:
Only issue now is the soft reboot after boot completed. Not a huge deal, maybe it will be resolved in an edxposed update, although I am now using the latest Canary alpha, alas no change.
Click to expand...
Click to collapse
I experience the same and already reported it to devs.
https://github.com/ElderDrivers/EdXposed/issues/373
C3C076 said:
I experience the same and already reported it to devs.
https://github.com/ElderDrivers/EdXposed/issues/373
Click to expand...
Click to collapse
That thread is saying something about using a modified build of magisk. Did you try that and do you know where to get it?
edit: I'm using latest magisk 20 version.
The Edxposed Manager Canary release fixes this for me
Hi, I've rooted my Galaxy S8 Plus using TWRP and all that jazz. To make it clear I am a complete noob to this whole thing and probably jumped way higher than my belly button by now,
but I'm pretty close to reaching my goal. I am trying to download modules from within Magisk but all I get is a visual confirmation that a button was pressed ( it turning blue, basically ),
and the app freezes, the only way to interact with it is to shut it down. It happened to me when I tried to download/install Magisk from the in-app button, but it got resolved on its own
and now it's happening again when I'm trying to download, for instance, Systemizer.
Any steps or experience to avoid it?
UPDATE -
Managed to import it from this forum, installed through TWRP recovery, see no way to access the terminal itself.. is it a physical app on my phone, or do I need to access it through somewhere? I know it's probably trivial, but I'm clueless..
Should probably elaborate - it's a Samsung Galaxy S8 Plus SM-G955FD
Hello my nerdy pals!
I bought a new Pixel 5a yesterday and set it up normally... no bootloader unlocking or rooting or whatnot.
Everything works as expected except for these features:
1) Wake screen for notification (the one I actually care about)
2) Tap to check phone
3) Lift to check phone
I googled this issue and read a post that suggested I boot the phone in Safe Mode to see if the features still don't work. I did that, and in safe mode they work. The post further said that if it works in safe mode and not normally then I have an app installed that is causing the problem. I should then uninstall apps that are possibly interfering, reboot, and then try the feature again.
I have around 100 apps (nothing crazy, this includes all the system/stock apps). Rather than try to uninstall/reboot/test/reinstall each one, I'm wondering if anyone here has any suggestions for solving this issue.
UPDATE: I ended up the process of uninstalling all my apps to find the culprit, and I did find it.
The app causing the problem was, strangely, a radio app for Canadian stations.