Related
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.
Hey,
Ever since the OTA update my phone reboots randomly about once every two days [I'm on Verizon].
Is anyone else experiencing this?
Screen just goes black, vibrates once quickly, then its back on that LG G2/Verizon screen and then boots. Then everything is fine.
Vexorg said:
Hey,
Ever since the OTA update my phone reboots randomly about once every two days.
Is anyone else experiencing this?
Screen just goes black, vibrates once quickly, then its back on that LG G2/Verizon screen and then boots. Then everything is fine.
Click to expand...
Click to collapse
Nope... Have you done a FDR yet? It is highly recommended to do one after taking this OTA if you have ANY kind of trouble at all.
acejavelin said:
Nope... Have you done a FDR yet? It is highly recommended to do one after taking this OTA if you have ANY kind of trouble at all.
Click to expand...
Click to collapse
Fdr is a full factory reset?
Sent from my VS980 4G using Tapatalk
Vexorg said:
Fdr is a full factory reset?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Yes, FDR = Factory Data Reset, basically a factory default, not reflashing the original factory images.
acejavelin said:
Yes, FDR = Factory Data Reset, basically a factory default, not reflashing the original factory images.
Click to expand...
Click to collapse
Sorry for all the questions but you're just referring to go going to settings > backup and reset > factory data reset?
Sent from my VS980 4G using Tapatalk
Vexorg said:
Sorry for all the questions but you're just referring to go going to settings > backup and reset > factory data reset?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Yes
Sent from my Nexus 4 using Tapatalk
acejavelin said:
Yes
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Cool thanks
Sent from my VS980 4G using Tapatalk
Problem still persists, I'm surprised I'm the only person getting this issue.
Vexorg said:
Problem still persists, I'm surprised I'm the only person getting this issue.
Click to expand...
Click to collapse
Your not the only one, but this is a very rare occurrence... Across all the major forums only 3 or 4 users have reported this issue.
Sent from my Nexus 4 using Tapatalk
Fairly common on custom builds
Vexorg said:
Problem still persists, I'm surprised I'm the only person getting this issue.
Click to expand...
Click to collapse
It's a fairly common occurrence for people on custom builds. I've noticed it when trying to do too many things at once.
There also apparently appears to be a link between SwiftKey and this problem from what I've read, or maybe that's an entirely different problem.
Mine have stopped after I disabled Google Services Sound Search.
hardheart1 said:
It's a fairly common occurrence for people on custom builds. I've noticed it when trying to do too many things at once.
There also apparently appears to be a link between SwiftKey and this problem from what I've read, or maybe that's an entirely different problem.
Mine have stopped after I disabled Google Services Sound Search.
Click to expand...
Click to collapse
I just rooted my phone about a week ago, I'm still on the 4.4.2 KK ROM and have Swiftkey and Google Services enabled. I also am using the Complete Keyguard Disabler.
A few things I've noticed are:
1)Random reboots/Phone overheating
2)Sluggish/unresponsive phone performance coming out of 'sleep' using double tap
3)Speaker/headphone Viper4 mod not working properly
Is a factory reset something I should consider if I didn't root the device until after the 4.4.2 update or is there something else causing these issues? I'm sure there is some user error in #3 as I'm going through the learning curve, but the most concerning is by far the #1 and 2, as I rooted it for the main purpose of increasing performance speed.
Any insights?
substitutesam said:
I just rooted my phone about a week ago, I'm still on the 4.4.2 KK ROM and have Swiftkey and Google Services enabled. I also am using the Complete Keyguard Disabler.
A few things I've noticed are:
1)Random reboots/Phone overheating
2)Sluggish/unresponsive phone performance coming out of 'sleep' using double tap
3)Speaker/headphone Viper4 mod not working properly
Is a factory reset something I should consider if I didn't root the device until after the 4.4.2 update or is there something else causing these issues? I'm sure there is some user error in #3 as I'm going through the learning curve, but the most concerning is by far the #1 and 2, as I rooted it for the main purpose of increasing performance speed.
Any insights?
Click to expand...
Click to collapse
I haven't looked at any logs or anything on a remotely technical level. I noticed the google sound search was eating battery so I disabled it. Reboots are gone.
substitutesam said:
I just rooted my phone about a week ago, I'm still on the 4.4.2 KK ROM and have Swiftkey and Google Services enabled. I also am using the Complete Keyguard Disabler.
A few things I've noticed are:
1)Random reboots/Phone overheating
2)Sluggish/unresponsive phone performance coming out of 'sleep' using double tap
3)Speaker/headphone Viper4 mod not working properly
Is a factory reset something I should consider if I didn't root the device until after the 4.4.2 update or is there something else causing these issues? I'm sure there is some user error in #3 as I'm going through the learning curve, but the most concerning is by far the #1 and 2, as I rooted it for the main purpose of increasing performance speed.
Any insights?
Click to expand...
Click to collapse
hardheart1 said:
I haven't looked at any logs or anything on a remotely technical level. I noticed the google sound search was eating battery so I disabled it. Reboots are gone.
Click to expand...
Click to collapse
First and foremost, I was not rooted or using anything customer. I never tried rooting this phone because I figured there would be updates in the near future (I was optimistic).
I am also receiving:
Random Reboots
Overheating
Random Apps Crash frequently (Kindle, Search, Home, etc)
I am also using swiftkey.
Vexorg said:
First and foremost, I was not rooted or using anything customer. I never tried rooting this phone because I figured there would be updates in the near future (I was optimistic).
I am also receiving:
Random Reboots
Overheating
Random Apps Crash frequently (Kindle, Search, Home, etc)
I am also using swiftkey.
Click to expand...
Click to collapse
I believe there are known issues with the G2 and Swiftkey on stock roms (rooted, custom, or otherwise).
What language are you using on Swiftkey. I'm on Swiftkey and Carbon and I'm not having any problems.
Using English (US)
Sent from my VS980 4G using Tapatalk
Vexorg said:
Using English (US)
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I'm also on Swiftkey and am experiencing very similar issues, using English as well.
On a side note, I also work in a building that has no cell service and continuously cycles through wifi connections because the 3 networks I have entered vary greatly in strength based on a 10 ft radius of where I walk.. could this be a cause as well and is there a way to stop it from happening?
I've tried removing all of the connections except 1 wifi signal but then I'm really only connected when I'm at my desk and if I standup to walk somewhere it's disconnected...
#1stWorldProblems
These issues are still persisting... anyone think taking it to Verizon would do anything?
My phone is completely stock. I am wondering if I should just flash a new ROM or something.
Vexorg said:
These issues are still persisting... anyone think taking it to Verizon would do anything?
My phone is completely stock. I am wondering if I should just flash a new ROM or something.
Click to expand...
Click to collapse
I second this, still having random reboots and running completely stock. I'm getting close to just removing Swiftkey all together?
I stopped using swiftkey and I'm still getting random reboots
So prior to update i'm pretty sure i was not having this issue.
Now, i'm updated and have not been getting my notifications.
What i have done to see if the issue can be fixed
-reset my phone
-reset the watch
-factory reset watch
-re-install app
After i do some of the steps above it will work but then eventually goes back to the same ole crap of not working. I'm getting a little irritated....
Thoughts?
Nobody?
Sent from my LG-D800 using XDA Free mobile app
Try to uninstall any non Wear app, reset and see what it does "clean". I had similar problems any time I used none Wear stuff. It works OK now with only Instaweather and Battery Wear installed. Mini Wear Launcher seems particularly difficult [emoji19]
So are you saying that the mini wear launcher causes issues?
Possibly... Mine works fine without and other threads also mention that they have problems with it. With all the respect for the developers, everything before the 5.0.1 update were more or less hacks because Google never published a developer kit until a few days ago. They all have to update their apps now this kit is available.
Tonio78370 said:
Possibly... Mine works fine without and other threads also mention that they have problems with it. With all the respect for the developers, everything before the 5.0.1 update were more or less hacks because Google never published a developer kit until a few days ago. They all have to update their apps now this kit is available.
Click to expand...
Click to collapse
Well, i think its a software issue so i am going to do process of elimination by starting to delete apps to see if one makes it stop.
Deleted:
-Rain Alarm: Still drops notifications
-Facer: Pending.......
I would proceed the other way around. Start clean to see if it's really a buggy apps that causes the fault. If yes then install one after the other to find the culprit...
I am now, nothing on it now. Gonna add something every 24 hours to see what happens.
Sent from my LG-D800 using XDA Free mobile app
Fingers crossed [emoji6]
Here should be the fix to this:
Go to your phone's settings, on my Nexus 6 there is a notification tab, you go to whatever your's is called, and find the checkbox to enable notifications to your android wear app. Hope this helps! Feel free to give me thanks.
Does anyone know how to fix an issue where the screen never locks? It just shows the last app when the phone wakes up about half the time.
I have a Galaxy S5 unrooted and stock.
Haven't run into that but I'm having issues with random sleep of death and random reboots. Stock unrooted here as well. I've already done a cache clear and that seemed to work for about 24 hours but I just had another SOD.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
lathamc said:
Does anyone know how to fix an issue where the screen never locks? It just shows the last app when the phone wakes up about half the time.
I have a Galaxy S5 unrooted and stock.
Click to expand...
Click to collapse
I been having the same problem
lathamc said:
Does anyone know how to fix an issue where the screen never locks? It just shows the last app when the phone wakes up about half the time.
I have a Galaxy S5 unrooted and stock.
Click to expand...
Click to collapse
mcnaught82 said:
I been having the same problem
Click to expand...
Click to collapse
In settings, go to lockscreen > Secured Lock Time > Instantly. Thats how I fixed it.
amazingasian said:
In settings, go to lockscreen > Secured Lock Time > Instantly. Thats how I fixed it.
Click to expand...
Click to collapse
That doesn't fix the problem. I adjusted that setting as soon as I did the upgrade. It's a lollipop issue.
mcnaught82 said:
That doesn't fix the problem. I adjusted that setting as soon as I did the upgrade. It's a lollipop issue.
Click to expand...
Click to collapse
Was this listed under 'Lock screen'? I checked where the amazingasian stated, and couldn't find the option. That being said, it doesn't seem to be consistent enough to be a setting.
lathamc said:
Was this listed under 'Lock screen'? I checked where the amazingasian stated, and couldn't find the option. That being said, it doesn't seem to be consistent enough to be a setting.
Click to expand...
Click to collapse
Yes it's under lockscreen. To be able to see the setting, 1st u must select a lock screen type, not the regular swype screen. Then go back to the lock screen setting and the option will be available. But lime I said, doing that doesn't fix this issue. Yesterday I turned my screen on and off 3 times just to get it to lock.
mcnaught82 said:
Yes it's under lockscreen. To be able to see the setting, 1st u must select a lock screen type, not the regular swype screen. Then go back to the lock screen setting and the option will be available. But lime I said, doing that doesn't fix this issue. Yesterday I turned my screen on and off 3 times just to get it to lock.
Click to expand...
Click to collapse
Have you tried a lock screen from Play Store? That might solve the problem. I'm using Hi Locker currently, with no problems at all.
cmerlyn said:
Have you tried a lock screen from Play Store? That might solve the problem. I'm using Hi Locker currently, with no problems at all.
Click to expand...
Click to collapse
I haven't tried it, mostly because I actually like the look of the lock screen and its integration with the rest of the OS. I think it is more of a problem with the OS not recognizing that the screen has been turned off. Therefore, I think it is a problem that would affect all lock screens.
Could it be an issue with Smart Lock? I do have a smart device set up (the Sync system in my car), but the locking isn't being consistent in my car.
I am having an issue where the Samsung Keyboard crashes when used with some apps. Notably Facebook messenger. Anyone else notice this? Also, on occasion when opening the stock SMS app after unlocking the device, it automatically opens the bottom most conversation. I've cleared both data and caches for the apps. I am fresh install rooted lollipop the day it came out.
CAG-man said:
I am having an issue where the Samsung Keyboard crashes when used with some apps. Notably Facebook messenger. Anyone else notice this? Also, on occasion when opening the stock SMS app after unlocking the device, it automatically opens the bottom most conversation. I've cleared both data and caches for the apps. I am fresh install rooted lollipop the day it came out.
Click to expand...
Click to collapse
Try my new revised rooted 5.0 process which uses FlashFire. Much more accurate in regard to permissions and contexts.
muniz_ri said:
Try my new revised rooted 5.0 process which uses FlashFire. Much more accurate in regard to permissions and contexts.
Click to expand...
Click to collapse
Will do, I have been so busy lately, I did not even notice. Thank you.
my lollipop problems
Stock s5 with lollipop AT&T. Since update and even after cache clearing, I am suffering from extremely slow charging, too fast battery drain. Occasional sluggishness, and occasionally notifications don't work until phone unlocked.
I used muniz_ri's flash fire method keeping root which installs fresh and lollipop works flawlessly with no bugs, nothing broken. After install, google reinstalls your apps which many rediscover their stored settings on the internal sd. Most lollipop issues seem to be related to the stock update method or manual tibu restore... muniz fresh install lollipop is solid.
SoCalHTCFuze said:
I used muniz_ri's flash fire method keeping root which installs fresh and lollipop works flawlessly with no bugs, nothing broken. After install, google reinstalls your apps which many rediscover their stored settings on the internal sd. Most lollipop issues seem to be related to the stock update method or manual tibu restore... muniz fresh install lollipop is solid.
Click to expand...
Click to collapse
This makes me wonder then, because I was a fresh install with the original method Muniz had up. I only TiBu restored a few apps (none affected by my keyboard issue) and let everything else stay fresh. I am going to try the new method for the reasons Muniz pointed out to my prior post that listed the issues I had.
SoCalHTCFuze said:
I used muniz_ri's flash fire method keeping root which installs fresh and lollipop works flawlessly with no bugs, nothing broken. After install, google reinstalls your apps which many rediscover their stored settings on the internal sd. Most lollipop issues seem to be related to the stock update method or manual tibu restore... muniz fresh install lollipop is solid.
Click to expand...
Click to collapse
Totally agree. I also used the FF method and I have no problems what so ever with my phone. @muniz_ri came through again. Thanks.
Sent from my SAMSUNG-SM-G900A
I noticed a bug in the YouTube app on my device (note 8 SM-N950F).
while a video is playing if I minimized the movie and then maximized it (quickly few times in a row) the phone crash to boot.
I didn't face any kind of crash in the month I have it except this scenario in the youtube app .
the app version 12.44.53
as you can see :
https://youtu.be/OPA2KdPunsA
anyone else can try and report ?
thanks
I have had the same thing. It would just randomly crash out and reboot my phone when minimising/maximising videos from the little preview window when scrolling.
xMadMike said:
I have had the same thing. It would just randomly crash out and reboot my phone when minimising/maximising videos from the little preview window when scrolling.
Click to expand...
Click to collapse
I manage to find more info by trying diffrent things. I think maybe it's memory management bug. If the device is fresh from boot with nothing else running then it won't crash. But with some apps open in the background then it always happens. not randomly at all.
Did you solved it?
Sent from my SM-N950F using Tapatalk
It happens so rarely that I haven't really done anything about it. It will happen out of the blue one day and won't show up for weeks. I have gone on the Samsung Members app and it detected an unexpected reboot which it reported to Samsung so maybe they will fix it eventually.
Same thing for me. Happened already 3 times. While resizing the window or passing from portrait to landscape.
nafroman said:
I manage to find more info by trying diffrent things. I think maybe it's memory management bug. If the device is fresh from boot with nothing else running then it won't crash. But with some apps open in the background then it always happens. not randomly at all.
Did you solved it?
Click to expand...
Click to collapse
I have same problem like you. Whenever there is an apps running in the background, it will crash. I happen rarely for me but this week, youtube and instagram crash 4 times already each. Yea most likely its Ram management.
any update on how to fix it? Thanks
Zz'Rot said:
any update on how to fix it? Thanks
Click to expand...
Click to collapse
I've checked now and it won't crash. I don't know if it's related but Yesterday I've installed the latest OTA update (which was the first since I've got my unit). Any way it's seems fixed as far as i can see. Didn't do anything except updating all my apps and the unit itself to the latest version available. If it will happen again I'll keep you update.
Sent from my SM-N950F using Tapatalk
nafroman said:
I've checked now and it won't crash. I don't know if it's related but Yesterday I've installed the latest OTA update (which was the first since I've got my unit). Any way it's seems fixed as far as i can see. Didn't do anything except updating all my apps and the unit itself to the latest version available. If it will happen again I'll keep you update.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Same, i also got the first update on my Note8 yesterday too.