Related
After rooting with Damagecontrol, anytime I go from an application back to the home screen, a White HTC shows up, then after 3 seconds goes away, a loading box comes up for about 3 seconds, and the home screen appears. Never happened before root. did I do something wrong? Did I change a setting by accident?
I hate this screen, slows everything down. Anyone have any ideas?
Thanks in advance
That white HTC screen is just the loading screen for Sense. Sounds like something is killing Sense while it's in the background so it has to reload when you go back to the home screen. Are you using any kind of app killer w/ auto kill turned on?
Nope, I had task manager installed, but I uninstalled it and it is still happening.
I'm bumping this to get a reply. I've searched the boards and having found much of anything besides this thread.
After I used rEVOked to root, I started getting this issue. I thought if I updated to the latest firmware, the problem would go away. I was wrong. Still getting this issue about 3-4 times a day which is pretty annoying.
I usually get this whenever I unlock my phone or going to a different home screen. Any help would be greatly appreciated.
jhawk2002 said:
I'm bumping this to get a reply. I've searched the boards and having found much of anything besides this thread.
After I used rEVOked to root, I started getting this issue. I thought if I updated to the latest firmware, the problem would go away. I was wrong. Still getting this issue about 3-4 times a day which is pretty annoying.
I usually get this whenever I unlock my phone or going to a different home screen. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Unrevoked does not unlock NAND. More than likely, not being fully rooted has something to do with your problem.
Well, I've "cleared storage" and I am still getting the same problem... Any other possible solutions?
You said, "not being fully rooted has something to do with your problem", so should I fully root my EVO and see if that works?
You should see that screen when coming from a different home screen. You know how when you start some PC applications there is a splash screen that comes up for a few seconds while it loads? That is exactly what that white HTC screen is.
The HTC launcher is a bit more resource hungry than some of the others, so it has to load some stuff into memory every time it starts. However it is supposed to stay in memory so you can open a music app/game/browser/etc. and then go back to home without waiting for it to load.
If you are seeing that screen something has killed the HTC Sense process since you were last on the homescreen. If you are not running something like a task killer, it is probably that whatever ROM you are running has settings that kill apps quickly, this is often done for performance or battery life, but yours is too aggressive.
Only other possibility I can think of would be if sense is crashing and has to restart every time.
I'm having this same issue. I'm running a stock EVO, and HTC Sense will reloading sometimes when unlocking/tapping home.
I have a feeling it might be related to WidgetLocker, as the only "task killer" app I have is System Panel which doesn't auto-kill.
Anybody else using WidgetLocker and having this issue?
Bump. Still having this issue regularly.... anybody else have this with or without WidgetLocker?
I've done a search for this problem, but haven't found a solution to this yet.
I'm running the stock rom w/root. It didn't do this when I first got it, but it's doing it more and more as time goes by. It's starting to drive me nuts, especially at night since my phone is my alarm as well. Doesn't seem to matter if the phone is charging or not.
The screen will flicker on and off a few times in a row, then stay dark for awhile then resume the on/off behavior out of nowhere. I'm not receiving texts or emails when this happens.
I have checked my account syncs, and nothing is set to automatic. Never had this behavior on my SGII LTE running ICS.
blanchardc said:
I've done a search for this problem, but haven't found a solution to this yet.
I'm running the stock rom w/root. It didn't do this when I first got it, but it's doing it more and more as time goes by. It's starting to drive me nuts, especially at night since my phone is my alarm as well. Doesn't seem to matter if the phone is charging or not.
The screen will flicker on and off a few times in a row, then stay dark for awhile then resume the on/off behavior out of nowhere. I'm not receiving texts or emails when this happens.
I have checked my account syncs, and nothing is set to automatic. Never had this behavior on my SGII LTE running ICS.
Click to expand...
Click to collapse
Your title made me chuckle.
I did experience some random screen wake ups while on stock that sort of just resolved themselves. Try rebooting, and then try to uninstall any new apps you've installed to see if one is causing this.
TheFiveDots said:
Your title made me chuckle.
I did experience some random screen wake ups while on stock that sort of just resolved themselves. Try rebooting, and then try to uninstall any new apps you've installed to see if one is causing this.
Click to expand...
Click to collapse
Thanks for the suggestion. Rebooting was obvious as I've done that many times. I did go through a bunch of apps and removed them, then reinstalled one by one. So far the problem has gone away, I've yet to identify which app might have caused it though.
If you're having reboot problems please post here - if there are problem apps or bad devices out there it would be good to know!
Got a new Nexus 5X yesterday for my partner. Plugged it in and charged all day (oh what patience). 10pm started setup and added account to it. Phone immediately did an update which succeeded. Then it started to install the saved apps from the Google account, about 50 in all. After all the apps were installed I handed it over to her to play and log into all those apps with logins. Tedious.
Within about 30 minutes she tried to take a photo and it rebooted. Then a bit later she was using it and it rebooted again. Before going to be it rebooted a few more times. Then again this morning. There wasn't one particular app or other that was in use when these crashes happened. During the day she saw a message about "Google needs to restart". Also the camera often comes up with an all black screen and can't be used.
I called Google tech support and they wanted to do a factory reset and maybe a cache partition wipe. They would also like to investigate if a rogue app is causing the crashes by using it without any apps installed. Because reinstalling apps is so tedious I decided to have her do a cache partition reset I'm awaiting news. I'm hoping we don't have to do the other... I can't imagine how a bad app could be causing such repeated crashes (well I can, but it just shouldn't happen). That's lame...
It would really help if it was easy to get a crash log and find out the cause - unfortunately unless you're rooted this doesn't seem to be easy, and may well be impossible.
I've been having a lot of similar-sounding issues with my 5X. It's never rebooted while I was using it, but once or twice a day I'll pull it out of my pocket and it will be off, awaiting the unlock pattern to boot up.
The camera has been atrocious as well. I've seen the black screen you describe, tons of rotation lag, hanging, etc. Not just in Camera, but in other apps using the camera (such as when attaching a photo to a Hangout). Hoping this is something software-related and not a hardware problem.
I've had mine spontaneously reboot twice so far, both times I've pulled it out of my pocket and it required the PIN to unlock, then it booted up. I'm a bit concerned, as I have no idea when this happened, and, since it's encrypted a reboot essentially puts me offline until I notice it.
I just now had mine reboot during active use for the first time. I was long-pressing a wifi network in order to forget it (which is another 5x problem I keep having—wifi turns itself off or connects to the wrong networks).
My 5x was working fine and the crashing started happening yesterday...
they only app that i recently installed before the crashes started was firefox... are you guys using firefox by any chance???
Mine is still working fine, I do not have Firefox.
Same problem for me when using Firefox. The phone seems to crash and reboot when loading news websites containing photos and videos.
Not seen the issue when not using Firefox.
I've had my nexus 5x since mid/late November 2015. I've had the problem described below happen prior to today, and more than once.
Today, I cant turn my phone off - it seems to be in the middle of a reboot... the four coloured circles (google logo?) with colours going round and round. I powered it off cos it had started going slow... thought a reboot might fix the problem... but now its not starting and I cant even turn it off or do anything with it.. I've tried pressing the power button, I've tried holding the power button down, and I've tried different combinations... nothing seems to make a difference... (has been in that state of un-useablity for at least 30 mins now)
Anyone else also having wi-fi issues where facebook has an error and "cant connect" ?
I had the same thing happen and returned the phone, it's the only solution I found. I factory reset multiple times, called up Google and they told me to safe boot. Right.. I was completely stock and it rebooted multiple times / day and I know what I'm doing too, for the most part anyway. Got a replacement device and it has not once rebooted no matter what I do. Camera, Chrome random apps caused a reboot, it's not that. It's a defective device and you need to get it replaced period.
I have the same thing and can't sent it back to google because I live outside the US.
I believe it is a manufacture defect as I tried everything with no success really annoying.
Stuck with a brick...
Sent from my Nexus 5X using Tapatalk
I used my phone completely stock for weeks and had zero issues, whereas I have a friend who ordered and received the phone at the exact same time (likely same mfg batch) and had issues. Difference between us two is that I'm a minimalist and only have about 50 apps installed, and he has a ton that he rarely uses and restores them every time.
I know it seems ridiculous, but having an android phone gives you more customization and your apps more power of the phone, so it's completely feasible for ONE rogue app to destroy performance and/or battery.
You guys might all want to try uninstalling apps one by one and figuring out which apps are killing performance. In particular, check out the running services (developer options -> running services) and see which apps are constantly running, since those are more likely to be the ones causing issues.
For example, I've used firefox (for adblocked browsing) for weeks recently, and can definitely say it's a pretty slow app, so if you're having issues on it, you may want to just use chrome or lightning browser.
I just ordered a replacement as well. Mine would reboot about 1 to 2 times a week right after the fingerprint unlock. Annoying as hell today because I was in the middle of a conf call.
Sent from my Nexus 5X using Tapatalk
Hello, I have had my Note 4 for quite some time now and have not had any issues with it up until the last month or so.
At first it started out as just a hiccup every now and then, an example would be when I play music via bluetooth to my Jeep CD Player, I would sometimes have to turn bluetooth off then back on to get it to connect or reconnect.
Now things are getting out of hand. Here is a list of problems I have on a daily/hourly basis and seemingly at random times. I cannot reproduce any of these problems (except the NFC problem) on demand.
I have noticed that rebooting the phone will clear up these issues (except NFC) for a short time, SOMETIMES. Other times a reboot does nothing to help the situation.
Keyboard Lag
Sometimes when I press the keys the phone vibrates indicating a key press and magnifies the key that is being pressed, but fails to enter anything in the text box/input field. For the record I am using Swiftkey. I have noticed that this happens most often when I open an app via "popup notification." For example, if I were to receive an IM or SMS I would tap on the notification that pops up, which then switches to/opens the corresponding app. It is then I will more often than not have this issue. To remedy this I have to close and re-open the app, sometimes several times causing the keyboard to open and close, several times... Sometimes when I TAP a key, the phone will behave as though I have held the key down or performed a "long press." This issue is not exclusive to the keyboard, it often happens anywhere on the screen and with any app, usually indicating that I have been "long pressing" for about 1-2sec at a time.
NFC Does Not Work
One day while I was at work I attempted to add the office printer via NFC. To my surprise I was unable to turn on NFC via the "quick settings" drawer. In the quick settings panel the NFC icon would light up, as if it were turning on, and then just turn right back off again, this happens consistently. I went into setting to enable NFC that way and I am stuck with a slider that is actually in the "on" position but greyed out, I am unable to interact with it.
Bluetooth Connectivity
I have a JVC CD player in my Jeep, I often use YouTube or Google Play Music when I drive. Usually I do not have any problems connecting to the CD player at first, but after about 30-60sec of playback the audio goes blank. The app says that it is still playing however no audio can be heard. Then it will suddenly come back on after about 5-10sec, and here is where it gets strange. After the audio comes back on after this "hiccup" the playback is fast, as in it is playing at 2X's it's normal speed, makes the vocals sound like chipmunks. This will continue indefinitely until I turn on the screen, unlock the phone, then shut the screen off. Then the audio goes on playing fine. This happens with both YouTube and Play Music, while using YouTube the video gets sped up as well. I also experience issues with connectivity where sometimes at random the phone will just disconnect from the CD player, and refuse to reconnect until I have rebooted the phone, or if it does reconnect I get no audio until the phone is rebooted. I notice that this ONLY happens when connected via bluetooth. If I turn bluetooth off while this is happening music will play over the phone's speaker perfectly normal. My CD player has a hands free feature, and I do not seem to have any issues with phone calls, it's only with music playback do I have problems.
Originally I thought it was my CD player acting up, however in light of the other problems, and the fact that I tested it with my tablet and two of my friend's phones without issue, I don't think the CD player is the problem.
Sluggish/Glitchy UI
Sometimes when the phone really freaks out, the UI behaves very strangely. Sometimes notification Icons will hover above the running app, other times the whole screen will lock in place for a few seconds. Sometimes if the screen is locked up, I will shut it off, then turn it on, shut it off, turn it on. However as I press the power button to turn the screen on and off, nothing is happening, the screen just stays black while the "back" and "recent apps" buttons light up at the bottom. Then when the screen does finally come back in it will flash on and off quickly in accordance with how many times I pressed the power button. While all this is happening, if I hold the power button to turn the phone off, the power/reboot menu will appear without incident. Sometimes when I am swiping to unlock the phone, it does not register the full swipe. Basically it acts/appears as though I lightly touched the screen and moved my finger a half inch even though I have drug my finger all the way across the screen. To remedy that issue I have to SLOWLY drag my finger across the screen and then it unlocks without incident. I have also noticed that when I go to "swipe away" a notification, especially one that has "information" in it, it will swipe off the information but leave the notification there and display the app name the notification was from. An example would be, if I just installed an app (for example YouTube) from the Play Store, the notification will say "YouTube has been successfully installed." When I swipe either left or right to remove that notification, a "white ghost box" or "overlaying top layer" with the "successfully installed" text in it will slide away. However it leaves behind a green box/notification that says "Google Play Store" and that remains until I shut the screen off and turn it back on.
NFC Will Not Turn On
I simply cannot get NFC to turn on, the slider is in the ON position but is greyed out as I mentioned earlier. I would post a picture but I guess there is a 10post rule before I can do that. I have given up on NFC, mostly because I rarely use it, so it's really not that big of a deal.
Initializing the Camera
I use an app called "Telegram" instead of SMS messaging, thus I use Telegram to share pictures with friends. Sometimes, again I am not able to reproduce this problem on demand, the problem comes and goes seemingly at random. The camera will take more than 30-60sec to initialize, while I am waiting for it I am stuck with a black screen. If the camera doesn't initialize, shutting the screen on then off will take me back to the telegram app. I never get an error message or anything. Other times when I try to use the camera it pops on instantly and works flawlessly. Originally I thought this was a problem specific to telegram, however in the name of science I tested it with the default camera app and get the same results.
USB File Transfers
I'm not really sure this is specific to my phone, but whenever I transfer files from my PC to the phone or from the phone to PC, it is PAINFULLY slow. It's even painfully slow when the PC just displays what is in the folder. However I can't say for sure this is related because I never attempted to transfer files until I started having these issues, at which point I thought it would be a good idea to start backing things up.
Gets Stuck in 3G Mode
This happens rarely, not even sure that it's related but I felt that it was worth mention.
What have I done to try to remedy this problem you ask?
So far I have performed a non-root ADB nandroid backup, just in case factory resetting the phone didn't work.
I have factory reset the phone 2 times, I see no improvements.
I have cleared out my SD card/removed SD card
I removed and/or shut off bloatware apps (Yes I tested the phone without removing/disabling bloatware, still having the same issues)
Wiped cache via Recovery
I am not sure what else I can really do to fix the phone, I am starting to think that this is a hardware issue. I should mention that there was no significant event that I feel would cause these malfunctions. System update installed and worked perfectly up until this last month, I have not dropped the phone from significant height, the phone has an otterbox anyway. I have not gotten the phone wet, it has not been left outside, this phone has not seen any abuse what-so-ever. I just started having these problems out of the blue and they seem to be getting progressively more frequent and longer lasting. If I don't get any ideas from here I am going to try to get Verizon to replace the phone via insurance, however I don't have high hopes for that because I have grandfathered unlimited data and this is not the "original" phone that I had when I added the insurance option, so I am not sure it's covered.
Does anyone have any ideas on what could be causing this or anything I can do to correct it or try to troubleshoot it?
Any help is greatly appreciated!
Phone Information is as follows:
Samsung Galaxy Note4
Model: SM-N910V
Android Ver: 5.0.1
Baseband Ver: N910VVRU2BOG5
Build#: LRX22C.N910VVRU2BOG5
HW Ver: N910V.05
Verizon Wireless
Non-Root, Default Launcher, Not modified in any way.
I realize that this is a long post but whenever I ask for help I like to be detailed. If I left out any information that might be helpful please let me know.
Unfortunately, it looks very much like components on your logic board are going bad. Sometimes a few specific things will go bad that don't actually make the phone unusable, but make it act similar to what you are explaining. It wouldn't be worth the money you'd have to pay someone to track down the bad components and replace them. If you really like the note 4, I would just make a full backup with kies while you can, buy a new phone and restore your backup.
All of Kies backups do NOT restore to a new phone! Only contacts, messages and call logs will restore on a new phone. Use Samsung Smart Switch or Helium. Good luck
Sent from my SM-N910V using Tapatalk
outcasted2003 said:
All of Kies backups do NOT restore to a new phone! Only contacts, messages and call logs will restore on a new phone. Use Samsung Smart Switch or Helium. Good luck
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I see. I didn't know that because I've always restored my backups to the same phone. Thanks for the info.
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
It seems the problem is more severe than just Android.
Because even in TWRP, I noticed the display need to wait ~1 minute from the last time I turn off the display (push the power button) to reactivating it.
If I try to turn it on, the display will give black color, but I still can actually interact with the system.
ArcOnFire said:
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
Click to expand...
Click to collapse
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Shimizux said:
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Click to expand...
Click to collapse
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
ArcOnFire said:
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
Click to expand...
Click to collapse
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Shimizux said:
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Click to expand...
Click to collapse
I don't think it's a battery problem. I see that I can play game for 1hr+ fine. A game that require exact timing of 2 touches on top of that. So that ghost touch really doesn't appear.
But yeah, it's really 2 contrasting sign
- In one hand, it seems an OS problem because I can simulate an environment where the screen definitely won't be frozen for hours, while on specific other environment, the screen freeze can happen very quickly between release and re-occurence.
- On the other hand, the problem seem doesn't stop on OS level because it can be found in TWRP.
If I read an answer on Quora that shows GIF image on the section I read, the screen freeze 100% won't happen. I tried the same thing on imgur too, the screen freeze won't happen.
So it seems that as long as the screen is showing dynamic content, it won't freeze (that's why game and YouTube doesn't show this kind of problem, but reading a web full of text/static images can)
A bit of update : I have left my phone in off state for 4-5 days. And I have been using it again, albeit, less extensively since my main phone has changed to K20 Pro.
Long story short : I haven't encountered screen freeze again. But this is just after 2 days playing with less intensity.
I wonder what really went wrong.