Hey,
I have a Bell SGS, totally stock. It's suddenly become incredibly slow.
I haven't installed any new apps recently, or changed any settings.
When I press an icon, any icon here is what happens:
- I put my finger on the icon and let go, nothing happens for 2 seconds.
- The icon goes 'dark' like it is being depressed, stays that way for about 3 seconds
- The icon finally gets 'clicked' and I get the 'ding' sound
- The screen goes black with only status bar for about 5 seconds
- finally the app will show up, but if I press anything, it is unresponsive
- the app will become responsive after about 5 more seconds
- If I click a text box (like in stock messaging app), it freezes for another 4-5 seconds, the keyboard doesn't come up
- Finally the keyboard will come up.
ALSO:
- The phone app takes ages to launch.
- Anytime there is a screen to scroll, the scrolling is unresponsive for the first few seconds, its painful
- pressing the home button takes ages to bring me to home screen
- Often the phone just locks up and I can't turn the screen on, have to do a battery pull (once a day or so), I can't figure out what is causing it.
There are no apps running while this is happening, I looked at all running processes and everything seems normal, nothing hogging CPU.
Reboots don't fix it, it comes back just as slow
All the haptic feedback is way late, sometimes the little buzzes get queued up, so it wont do anything, then all of a sudden it will buzz 10 times in a row as it catches up with the button presses
Samsung email (which I use because I like how it handles multiple accounts) is the slowest program in the phone. When it loads up, I click on one of my accounts, it takes literally 30 seconds to load the messages. Then I still can't scroll for another 10 seconds, its agonizing. Switch to the other account? Another 30 seconds. Both accounts are set to keep emails from the last 14 days (not that much).
So, what the hell is going on? I took it to the Bell store, and even with the stupid warranty, they said "well, its still working, so theres nothing we can do"
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
apollohay said:
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
Click to expand...
Click to collapse
it was at ten percent brightness and the screen was completely unresponsive as far as i could tell. doing the power + volume up press made it reboot and return to normal.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
kingwaffle said:
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
Click to expand...
Click to collapse
exactly the same here. felt like i had dropped a baby on it's head haha. i wish i knew a way to figure out what caused it.
My wife and I have been having the same issue, and I'm surprised that there's not more reports of this behavior The worst part is that I use my phone as an alarm, and the alarm won't go off if this happens in the night.
It has happened to me 3 times now, and 2 times in one day for my wife. Holding down the power button for ~20 seconds will cause the reboot, which is the good news. This morning after holding down the power button I noticed the notification light flashing red.
The phone appears to be still on, because if it happens overnight I will still see the white notification light flashing even though the screen won't turn on.
I had this problem on faux123 kernel on the second day after I got my Nexus 4.
Doesn't encounter it on franco.Kernel...
Sleep of death brozillas! Happens to all android phones. Happened to all my phones listed in my signature. You can reboot the device and you should be good. For the dude that's missing his alarm you should do a factory reset if you are stock or if you have root do not set your min cpu values to less than 3xx MHz.
Sent from my Nexus 4 using xda app-developers app
Same thing happened to me on my N4. Did a hard reboot and it came back on. Has happened at least twice since then, usually after being plugged in.
Sent from my Nexus 10 using XDA Premium HD app
Change chargers, cables. Make sure the charger is 5v 1.2a. Factory reset to stock.
If all that fails, RMA if you can.
Sent from my Nexus 4 using xda
I observed the same issue (going to standby, then cannot switch on within an hour) with my [just bought] Nexus 4 (latest 4.2.2 firmware OTA updated, nothing special in setup, second day of use).
Certainly must be difficult to say if it's hardware of software (that is, JB/drivers, since I cannot see how such issue can be caused by any virtual machine application) and when/if the latter will be fixed. I have another such great device already -- ASUS TF700 transformer, with similar "everything works, just reboots occasionally", which I think is enough for me
As with the ASUS Transformer case, I have trouble understanding: if it's the issue with all devices/firmware, although not too frequent -- then why everybody does not complain/return the units massively: the phone is pretty unusable if it cannot be relied upon. If it's just some isolated cases with particular units -- then what happened to QA/testing at LG...
So I guess I am going to return it while I can.
Too bad, good model otherwise, will have to see other phones or wait/observe.
My point is, I understand: fairly new device, can have quite a few faults to be fixed later -- now everybody seem to work that way, for better or worse.
It can have more or less beautiful (or ugly) designs, more or less features, larger or smaller batteries/working time; it can have problems with data connectivity, it can have better or worse browser (or the lack thereof completely). I'm fine with the lack of text reflow in Chrome although that was surprising.
One thing a phone/communicator/PDA absolutely cannot do, provided its battery is not empty, is going into "sleep of death"-like states -- it just cannot serve its purpose then, I cannot see how people sell it at all...
I have had a similar issue before, but i have experienced it when my phone has been through one of 2 sets of scenarios.
1 - It gets really warm and the screen becomes unresponsive, dead if you will. The hard reboot fixes this.
2 - When the signal to my phone is sporadic. An example of this would be my recent trip to London. I was on the underground quite a lot, and I'd lose signal quite often whilst travelling. On a couple of occasions i had to reboot my phone the hard way to get it going again.
Hope this helps?
In my case the device was lying near me on the sofa, the time between its going to standby and my attempt to switch it on was something within 1 hour. Nothing especially intensive had been done before.
BTW, while the phone was in that state, trying to call it resulted in long tones, i.e., apparently the radio/cell was online.
Hope this will help somebody, I returned mine.
Good evening. First post but long time lurker. My N4 is unrooted and on 4.2.2. I'm troubled with this as well especially so when the alarm doesn't ring in the morning after it's crashed overnight and I'm late for work!
Not sure if this is relevant though. I don't listen to music frequently on my N4 but the 3 times it had crashed overnight I had been listening to music before going to bed. Twice using Google music being streamed via my home wifi and once using poweramp with music on internal memory. I remember on 2 occasions the phone feeling rather hot as I was plugging the charger in as I was about to turn in.
I suspect there's a process that's causing the the phone to overload/ overheat and then switch off as a result. Because it's plugged in, it'll just continue to charge overnight and present you with a 100% battery in the morning once you've got it to reset again.
I have also found that doing a soft reset before going to bed prevents this from happening.
Just my observations.
Hi all, I got my Nexus 4 a week ago to replace a broken HTC One X (The cost of repairs was almost equal to the cost of a new Nexus 4). Since I got it, SoD happened twice, both times when I left it to charge overnight. The weird thing is that I have this LED application that blinks the notification light when charging with screen off. When I unplugged the phone, the LED was still blinking as if charging, so the phone is definitely not dead. I will try to set it to day-dream while charging and see if it helps. If it does, it might be considered a way of Google encouraging developers (like myself) to create more daydream apps .
Good morning from beyond the pond,
had the same thing happening as described in the first post solution (pressing POWER+VOL UP) helped to reboot my device.
Only thing that was showing was the led, flashing a blueish white light.
Now runs again on rasbeanjelly. Thanks to OP.
EDIT: since this happened the first time, I thought about what I had altered in my setup.
Only thing that was new was "Greenify". Maybe it sent the APEX launcher into standby?!
Having same problem on my 1 week older n4, my friend having the same problem . only thing in commune we have is the WHATSAPP app that once the phone restart it give a notification that the phone date is wrong,once I look at the date settings yes it is wrong, it says 1970 ,so I have to reset it. It does it every time the problem happens ,can this be a clue???
Sent from my Nexus 7 using xda app-developers app
guinnes.s said:
it says 1970
Click to expand...
Click to collapse
UNIX equivalent of Pol Pot's year zero
I'm having similar problems.
The first time I believe it was just an issue of slight overheating. I turned off the screen but left Google Maps running & put it in my bag. It didn't actually turn off, but the screen didn't want to come on when I took it out later. I did notice it was hot, and after it cooled for a couple mins, it worked fine again. I haven't done this again, and so far, so good.
However, now, on occasion the phone won't respond to the power button. I've never had to actually do a reset - it will eventually decide to work after a couple of presses.. but when it does, it will be slow to come on. The screen will be backlit (but black) for a few seconds, then it will load and respond as normal.
Since the light comes on prior to the screen, it seems like a software rather than hardware issue to me. If the screen was damaged, I don't think it would act that way. I don't know phones, but that's my intuition. I'm going to try and remember to turn it off on occasion and see if that helps. I don't think it's been reset since the last push update.
(I'm rooted, but stock)
Hi all,
My Galaxy S5 has been a real bear lately. At least once every single day, the phone completely locks up. Usually it's with the screen on, but other times has been while the screen is off and I can't get it to turn on. The weird part is that if there's an animation on the screen (like the battery charging animation), the animation still plays but everything else is just stuck. The only way to fix it is to battery pull or hold down the volume down + home + power buttons and force it to reboot.
This happening every day, at least once if not more. I've flashed different ROMs hoping that it was just a ROM that was the issue, but it doesn't fix it. When I flash the ROMs, I make sure to wipe everything except the SD card so it's a very clean install, but alas no bueno.
I'm about at my wits end and ready to go to the AT&T store today to turn in my phone and get a Nexus 6 or Galaxy S6, but thought maybe someone here may have ran into the same issue and was able to resolve it.
any help appreciated - thanks!
My GF was making a call with my Note5 and it popped up Process System isn't responding - OK, Wait - neither of which did anything. also it was vibrating every second or so, probably while trying to bring the system process back up and it crashing again.
Holding power didn't seem to turn it off but eventually it restarted to SAMSUNG screen, where it CONTINUES to vibrate every second and never progress.
Holding power does not shut it down.
What the heck do I do now!?
This is a relatively new phone but I bought it from some guy who I can't get back in contact with. It had been working fine for a week, rooted, running Dr Ketan rom.
edit: OK, after about 5 minutes of it vibrating at the SAMSUNG screen I tried holding power AND vol down, this (perhaps coincidentally) then rebooted it and it seemed to come up fine this time. It's a real pain not having a removable battery when something like this happens.
I have a Note 8 that i have never dropped, had this phone since release haven't rooted. However it is running one of the early Oreo Beta builds CQLB the phone is on Sprint. This has happened once before about 2 months ago and i can almost guarantee it happened in the same fashion as the most recent time a few days ago. It seems while receiving a call i go to reach in my pocket and hit several buttons pulling it out (because of the bulky case) then my screen goes completely black.
(This is where it starts to sound like the normal black screen issue that there are a thousand YouTube videos for)
The phone still makes noises for notifications, rings when calling and other noises like emails and low battery alarm. The screen however doesn't display anything whatsoever and has a blue led blinking.
(This is where it differs)
I've done every button combination i can think of with no avail.
-The regular restart button combination Vol Up + Power and hold for 7-10 secs,
-I've tried to boot into Recovery mode by guessing at what time the Samsung logo should be on the screen and pressing the vol button down several times
-I've tried to boot into safe mode by pressing the Bixby button, power and Vol Up and without the screen displaying anything i can of course not see if i was in Recovery or not.
The screen doesn't display a Samsung Logo, No sprint splash screen NOTHING. The last time this only lasted for about 3 hours and it suddenly came back up when being on the charger and restarted several times. This is now day 3 and after dozens of restarts nothing has worked, on or off the charger. I mentioned the Oreo build because maybe it's linked to that? i haven't had this issue on regular Nougat. ANY help is appreciated and thanks in advance
Try turning off Always on Display. It worked for me..
Actually your problem seems different, so doubt it will work
..
WizP said:
Try turning off Always on Display. It worked for me..
Actually your problem seems different, so doubt it will work
Click to expand...
Click to collapse
nope, i cant get anything to show on the screen at all
winol said:
How did you get an Oreo firmware?
Click to expand...
Click to collapse
By flashing the Oreo beta builds via Odin etc..
go back to a stable build.
bober10113 said:
go back to a stable build.
Click to expand...
Click to collapse
Kinda hard to do without anything displaying on the screen whatsoever, anyway i mailed it off yesterday for repair from Samsung. It was either that or a 2 hour drive to 12 Mile (Detroit) to bring it to the Ubreakifix store.
Unfortunately Sprint doesn't offer loner phones and can't activate any phone that is non sprint outside of some iPhones which sound a bit strange but now I'm out a phone for 9-11 days :silly:
Have you solved this issue? I have the same issue with my phone. It started happening to me even when I was on Nougat. Happens to me several times already. It goes black screen for about an hour to 3 hours then randomly get back to normal (get notification sounds, can receive call, etc). I am now on Oreo. Everything is stock. Never rooted my device as well.
Tried to bring to Samsung but all they did is 'Software Update' the device which is basically reinstalling the firmware and wipe everything. Service Center sucks and doesn't want to claim it is a defective unit.
My note 8 began experiencing this yesterday and after some frustrations and work around, I managed to pinpoint the issue.
Work around was go unlock phone and drag down taskbar, then click on systems and the system interface would open, after which I could press buttons on lower part of phone and clearscfeen to get back to homepage.
Problem was with Google. In my case I realised when I opened Google maps, the screen went black, so I went into applications and cleared the Google cache and Google maps cache. No 0roblems since.
Is it something with Snapdragon?