Related
Has anyone else experienced this?
Sometimes (5-6 times in the last 24 hours) when the phone is sleeping, it will not wake when I hit power/unlock. I have tried installing no lock, hoping it was a glitch in the lock screen, but it still happens. The only way to fix it is to pull the battery.
Any advice?
Web sites are over-rated, when you have apps like these
bryon13 said:
Has anyone else experienced this?
Sometimes (5-6 times in the last 24 hours) when the phone is sleeping, it will not wake when I hit power/unlock. I have tried installing no lock, hoping it was a glitch in the lock screen, but it still happens. The only way to fix it is to pull the battery.
Any advice?
Web sites are over-rated, when you have apps like these
Click to expand...
Click to collapse
Are you running setcpu? Mine was doing this when I would lower the speed with a screen off profile. I just uninstalled setcpu for now. I don't think the kernel supports it anyway.
Sent from my SGH-T959 using XDA App
No, I had it, but since I can't overclock yet, there was no need to keep it installed. I did a factory reset, so we'll see if this fixes things.
Sent from my SGH-T959 using XDA App
bryon13 said:
No, I had it, but since I can't overclock yet, there was no need to keep it installed. I did a factory reset, so we'll see if this fixes things.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
let us know how it goes... If you experienced any unable to wakes after the reset...
Seems to be working fine. I'm not sure what the problem WAS, but the reset seems to have fixed it.
Root and busybox were still intact. Had to re-do the lag fix. (Method 1)
I'll update if I get the issue again.
My phone is just so...VIBRANT
Samething happened to me yesterday morning. Woke up found my phone wouldn't go back up. I thought it was dead, until I pulled the battery. I haven't Root hack it or installed SetCPU.
Sorry to throw this issue in this topic, but anyone have any problem with the phone rotating sideway for WEB and Messaging? I thought when I first got it, it worked.. now it doesnt..
There is probably a common app here or something causing this because I don't ever recall hearing this type of issue with the Vibrant before this thread.
I had the same thing happen to me and found after much trial and error that when I pulled my SD card out I was then able to wake the phone up. Apparently there was some problem with my SD (I was using it with my previous phone..MT3G) that was causing the Media scanning process to get stuck.
I ended up backing up what I needed from the SD and reformatting it. Since then I haven't had any issues. We may or amy not have the same root cause but hopefully this does help.
I'm thinking the problem HAS to be software related. After the reset, I've reinstalled everything I had before, and it's working like a charm! I've even used Titanium Backup to remove a lot of the bloatware, and still ruining great!
I just wish we could get a logcat, but when it happens, the phone is dead until you pull the battery.
My phone is just so...VIBRANT
bryon13 said:
I'm thinking the problem HAS to be software related. After the reset, I've reinstalled everything I had before, and it's working like a charm! I've even used Titanium Backup to remove a lot of the bloatware, and still ruining great!
I just wish we could get a logcat, but when it happens, the phone is dead until you pull the battery.
My phone is just so...VIBRANT
Click to expand...
Click to collapse
I am almost 100% SETCPU is the problem..
My phone would not come out of sleep.. I had to pull the battery and when I turned it on it would say "auto update of time and date".. That made me think the phone lost its internal battery and the phone was bad..
It started doing it right after I configured SETCPU... I installed the program last Thursday but never clicked on it.. I set it for on demand and that is when it started not coming out of sleep..
So I removed SETCPU and it still would not come out of sleep..
So I did a wipe all user data and it started working fine.. I installed SETCPU and it was still working fine.. I setup SETCPU for performance and it started messing up again and not coming out of sleep..
So, I wiped all user data again last night and it has been working perfectly since.. So I do not plan on reinstalling SETCPU...
It seems to happen after the phone has been on for an extended amount of time. I don't have lag, and I'm not using the gps when it happens. In fact, it usually happens when I sleep. Has anyone else experienced this? My phone is not modified. I'm even running plain touch whiz. I'm considering returning if I can't resolve with a hard reset. No third party apps are running when this occurs. I routinely close processes before I stop using the phone. I love this phone, I'm just worried I have a bad unit.
i'm having a similar issue, but with a rooted vibrant. the problem has spanned across two different handsets. the first one i rooted almost out of the box. but after a few days it started locking up after sitting for a while and i would have to pull the battery to get it to come back on. so i returned it, got a new one and held off rooting it to see if this one would do the same thing. the non rooted one had no problems at all, so i bit the bullet and rooted this one too, and sure enough later that same day it started doing the same freezes when trying to unlock it.
as soon as i rooted the second phone i downloaded rom manager and made a nandroid backup. after the backup i proceeded to remove some of the bloat, like dual clock, the startup/shutdown sounds, and some of the other crap that the vibrant comes with. i also installed and started up setcpu. it seemed that after i did all of this is when the freezes started up again. so i did a restore to before i removed all that stuff and now the phone is fine again. what is it about my process that is making this phone lock up like this?
EDIT: nevermind...i found some other people with the same problem in a setcpu thread...seems setting the sleep profile too low will cause the phone to not wake up after sitting too long
Uh, I'm not getting any freezing, but I know there is an issue with SetCPU. A certain setting will causes problems on the Vibrant. My issue is just unexpected reboots after the phone has been on for approximately 170 hours.
I had many random restarts and general craziness from my non rooted stock vibrant. A factory restore fixed all problems.
Sent from my SGH-T959 using XDA App
Yeah, if it happens again I'm going to try a factory reset.
Sent from my SGH-T959 using XDA App
Hi guys,
Not exactly the most positive of first posts but here we go. There's a problem with my phone that I can't find the solution for...
Essentially my phone randomly turns itself off (no power down sequence, almost as though the battery's being taken out if you know what I mean) and then it has difficulty in fully booting again. For some reason it also likes to revert my wallpaper back to the original as stock.
The first thing that I thought of was malware, with the wallpaper - so I tried a couple of anti-malware apps to no avail. As my device was rooted, I then flashed back to stock, locked and unrooted it and checked the behaviour. Again to no avail (then again I've never rooted/unrooted so this may have been done incorrectly). By the looks of it, the worst case scenario is a problem with battery connections/hardware...
So the question is have you guys come across this before? Is there a solution to this or is Google/LG going to have to give me a replacement?
Many Thanks.
Weird, I just had this happen couple hours ago, I was watching a video and close the app. I press the power button to put it to sleep. Just like 20 second later, I press the power to wake it and it don't do anything. I had to hold the power button to turn it on. I check the battery status afterward and it looks like it drop between 5-10 percent in the chart after it turn on. The battery must have failed or something. This also happen to my wife phone couple weeks back, although she had to do a hard reset(power+volume up and down) it have not happen again though.
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
maintains
kyokeun1234 said:
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
Click to expand...
Click to collapse
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Thrice87 said:
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Click to expand...
Click to collapse
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
kyokeun1234 said:
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
Click to expand...
Click to collapse
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Thrice87 said:
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Click to expand...
Click to collapse
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
kyokeun1234 said:
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
Click to expand...
Click to collapse
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Thrice87 said:
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Click to expand...
Click to collapse
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
kyokeun1234 said:
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, after completely reverting the phone back to its stock version and pretty much everything else, it's still doing it - which surely points to a problem with the chip (or something). So, I've contacted google about a replacement and so far so good - got through in 5 minutes and sorted out the RMA and everything, should be delivered in the next few days.
Thanks for the help anyway. I'm going to avoid rooting this one for the time being to see how it behaves.
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
hfuizo said:
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
Click to expand...
Click to collapse
Yeah that's not my problem at all Lol. Glad you've figured it out and I bet that magnet caused the issue IMO
Sent from my Nexus 4 using xda app-developers app
Funny I had the same thing happen to me last night. I was using the phone put it down for a minute or two and then could not wake the phone. What was interesting was when I couldn't get it to turn on I plugged in into the charger and let it sit for a few hours. When I was finally able to restart it using the the power, vol button the battery was at the same level before the incident. In other words whatever happened prevented the battery from being charged. I am stock and rooted and haven't loaded any new apps in over 2 weeks
Sent from my Nexus 4 using xda app-developers app
I have almost the same problem as the op but I do have a shut down sequence. It does randomly shut down itself. The first thing I got the phone I rooted it and it was fine working on modaco for 2 weeks then one day it kept shutting down upon boot until like 10 tries later I successfully got back in but lasted only a few mins and sometimes hours. Im gonna rma this pos and I hope I can get it replaced soon. I try it with stock rom and kernel then modaco with stock kernel then modaco with faux kernel. Same problem.
I had these problems earlier ... I just gave HARD RESET by pressing power key for more than 5 sec.
Then i figured, it was due to Undervolting ! and Processor going to a DEEP SLEEP all together !
So i removed UVing and it was cool since then ! ... Although my signature says the rest !
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
The same happens several times a week with my nexus 4 running latest cyanogenmod. I will revert it to clean stock in a few days to see how it goes. I don't think that is a hardware problem but time will tell.
MildewMan said:
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
Click to expand...
Click to collapse
Don't know if anyone is keeping up or cares, but I wanted to update and say that this did not fix the problem. 4.2.2 also did not fix the problem. I guess I could try getting a new one from Google.
My wife and I are both having this problem. Hers is completely stock, I'm unlocked and rooted. I was hoping it would be fixed with 4.2.2, but if it hasn't then it maybe time to get replacement N4s
I can't imagine this issue is very widespread, since there have only been a few threads about it. Its a big nuisance especially because it usually happens at night when I'm expecting my alarm to go off at night.
I hadn't wanted to send for replacements since it seems like a software issue but I'm getting fed up.
Sent from my Nexus 4 using xda app-developers app
Just had this problem occur with my N4 last night..... Phone is 2 weeks old.
Went to bed, plugged in the phone to charge [it was at about 50% or so, so not exactly low].
Woke up at 8.30 wondering why my alarm didn't go off at 7.30.... looked over and the phone was off.
It also didn't want to turn back on either. Took about a minute of holding in the power button for various amounts of time before it finally kicked to life [at 100% charge too].
This is going to be a real problem if this problem reoccurs. At home I have a clock radio but I travel a lot and rely on my phone to wake me up!
Here's hoping we can start to identify what is causing this issue. All I can add is that it is not low-battery related.
As stated in the sig. Phone is unlocked/rooted with stock rom.
Over the past week or so, I've noticed a couple of really concerning problems with my T-mo Galaxy S7 edge:
The home button stops responding while the rest of the phone functions normally. (https://youtu.be/CEj1CrRbdkI)
The phone entirely hangs up for a significant period of time (1 min - 5 mins) and doesn't respond to any buttons or input, sometimes leading to a restart (https://youtu.be/wuo1Ngc9bqE, https://youtu.be/UXwIPle5rHw)
These problems happen completely randomly - whether I'm at home, work, on a train, it doesn't matter. The app or screen that I'm on doesn't matter as well. The videos I captured were just examples from today, after a fresh factory reset. I'm not sure what else to do at this point. Any suggestions?
Edit: I should also add that I recently sent in my phone to Samsung for a screen replacement (which involves swapping out the entire front plate). I wonder if they messed something up on the hardware side ...
That defenetly looks like it could be a hardware defect my friend. Sorry but your home button looks gone. Anything sticky you had on your hands? Children?
Sent from my SM-G935T using Tapatalk
nano303 said:
That defenetly looks like it could be a hardware defect my friend. Sorry but your home button looks gone. Anything sticky you had on your hands? Children?
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Nothing sticky, no, but you're right that it could be a hardware thing. Since Samsung replaced the entire front plate (including the home button, soft buttons, volume and power buttons) it could be that. It doesn't explain the complete hangups either though ... I clocked the latest one at EIGHT MINUTES. That's how long the phone was hung up before deciding to restart on its own. Really strange. I might just get it replaced through T-mobile instead of engaging Samsung again.
An update: I took it to the T-mobile store for a check, and the rep there discovered that there was something like 1.5GB of data sitting in my cache (which somehow escaped clearing from two factory resets - access it by Settings > Storage > Internal Storage > Cache data). I also refrained from disabling any of the stock apps. It's been less than a day but so far the problems haven't resurfaced.
I proceed with cautious optimism.
Thank you very much for the info! I am having the same issue, I hope this helps me out. Currently I have 1.38 g of cached data. fingers crossed.
fatannasty said:
Thank you very much for the info! I am having the same issue, I hope this helps me out. Currently I have 1.38 g of cached data. fingers crossed.
Click to expand...
Click to collapse
No problem! Please keep us updated here if clearing the cache worked for you too. I want to make sure that the cache is the actual cause of the hang-ups. I still don't understand how it was unaffected even after two factory resets
Used to have reboot issues
I was wondering if you have the Samsung Good Lock installed?? I had it enabled for about 2 weeks and would get random reboots and the phone would become unresponsive. I tried everything to get rid of the problem but couldn't figure it out. Make a long story short, I unistalled Good Lock and no more reboots or issues. Worth a shot at least.
Also did you have saved fingerprints? I know on my Note 4 if you reset your phone when you had fingerprints setup that would cause issues because of how they are saved.
Sent from my SM-G935T using XDA-Developers mobile app
sevengroove said:
An update: I took it to the T-mobile store for a check, and the rep there discovered that there was something like 1.5GB of data sitting in my cache (which somehow escaped clearing from two factory resets - access it by Settings > Storage > Internal Storage > Cache data). I also refrained from disabling any of the stock apps. It's been less than a day but so far the problems haven't resurfaced.
I proceed with cautious optimism.
Click to expand...
Click to collapse
Bahaha! I had 4.3 GB. I was wondering why things seemed slow!
I do not have Good Lock installed, but I'll make sure to watch out for that one in the future.
I did have saved fingerprints, but they always got cleared after the factory reset. Besides, the problems existed before I decided to do the factory resets so maybe that isn't the issue.
4.3GB is high! But again I've been using the phone for just 3+ months (and only 1 month since I received it back from Samsung). We've all used phones for far longer than that without hte need to actively clear any cache. So I don't know, it still seems weird.
After 2 days since clearing the cache, the hang-ups seem to have stopped but I still noticed the home button being unresponsive a couple of times. It seems like they are separate issues, and I may still put in for a warranty replacement with T-mo for the home button issue if it persists.
Gah I don't know how to work multi-quote here sorry lol.
Final update: both problems are back in full swing. I even tried a 'hard reset' through recovery mode a couple of times and set my phone up as a new device (as opposed to restoring all my apps during setup). Stuck with stock everything, and did not disable any bloatware. Only apps I installed were Whatsapp, Inbox, and google Keyboard. Removed my SD card just in case. Still, both the problems highlighted in the first post continue to happen.
Based on the evidence I cannot see how this can be a software problem alone. Called in for a warranty replacement through T-mobile, which I should be receiving early next week.
Definitely a hardware problem.
Sent from my SM-G935T using XDA-Developers mobile app
joe1blue said:
Definitely a hardware problem.
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
Yea - kind of f*cked up that Samsung created a new problem for my phone while fixing the original issue (cracked screen). I specifically chose to send it to them and not a local store or even Staples (yup, they do repairs now lol) because I wanted to avoid complications ... smh.
sevengroove said:
No problem! Please keep us updated here if clearing the cache worked for you too. I want to make sure that the cache is the actual cause of the hang-ups. I still don't understand how it was unaffected even after two factory resets
Click to expand...
Click to collapse
So far my phone is still running great!
fatannasty said:
So far my phone is still running great!
Click to expand...
Click to collapse
I just got my replacement unit yesterday and it's been performing like a champ. I set it up as a new device to play it safe, but since then I've installed most of the apps that I use and have been able to disable all the bloatware without problems.
Pretty much confirms that there was a f*ck up with the screen repair on my original unit that ruined the home button functionality (and more, probably).
A note about those looking to do a warranty replacement through T-mobile: If you do not have insurance on the phone through them, they charge a $20 warranty service replacement fee AND a $20 shipping fee. Neither of these fees were revealed to me when I processed the replacement over the phone. Very under-handed on their part, especially because in that conversation with the T-mo rep I actually talked about how sending it back to Samsung was one of my options (for free, but they take 7-9 days to 'process' the replacement). Shameful on that rep's part.
sevengroove said:
I do not have Good Lock installed, but I'll make sure to watch out for that one in the future.
I did have saved fingerprints, but they always got cleared after the factory reset. Besides, the problems existed before I decided to do the factory resets so maybe that isn't the issue.
4.3GB is high! But again I've been using the phone for just 3+ months (and only 1 month since I received it back from Samsung). We've all used phones for far longer than that without hte need to actively clear any cache. So I don't know, it still seems weird.
After 2 days since clearing the cache, the hang-ups seem to have stopped but I still noticed the home button being unresponsive a couple of times. It seems like they are separate issues, and I may still put in for a warranty replacement with T-mo for the home button issue if it persists.
Gah I don't know how to work multi-quote here sorry lol.
Click to expand...
Click to collapse
The fingerprints are stored in a weird way. A factory reset does make it look like they are cleared, but for some reason if you don't manually clear them before you factory reset the phone develops a lag. I have no idea why, I just know it was an issue on the Note 4/5 so I am not surprised it is an issue on this device as well.
ShrekOpher said:
The fingerprints are stored in a weird way. A factory reset does make it look like they are cleared, but for some reason if you don't manually clear them before you factory reset the phone develops a lag. I have no idea why, I just know it was an issue on the Note 4/5 so I am not surprised it is an issue on this device as well.
Click to expand...
Click to collapse
Oh that's really interesting - it's really a shame that Samsung doesn't sort these issues out. It's actually concerning to know that my fingerprint profile could be residually passed on with my device to a new owner because it didn't clear out with a factory reset like it was supposed to.
So I got the latest beta 10, and decided I wanted to start fresh cause it has been a minute. When it's all said and done Youtubes skip overlay does NOT go away on its own. Usually you can just tap the screen once and she's gravy but I have to manually hit the X and I hit the damn travel bar 90 percent of the time and it is driving. Me. NUTS.
I have factory reset the phone, factory reset the app, deleted the app entirely with SD Maid...I am at a loss. I cannot figure it out.
Anyone else have this problem before and know of a fix? Any halp would be fantastic. Lmao
Here is a screen recording of my problem with taps enabled
https://youtu.be/Yn_VpQvRLww
I put OB10 on my phone last night and mine doesn't do that...Only difference is mine wasn't a fresh install. Also I'm not rooted and bootloader is locked.
Jeffro64 said:
I put OB10 on my phone last night and mine doesn't do that...Only difference is mine wasn't a fresh install. Also I'm not rooted and bootloader is locked.
Click to expand...
Click to collapse
Yeah I have never had this problem until now. It is hilariously weird. Not world ending but confusingly obnoxious.
Gytole said:
So I got the latest beta 10, and decided I wanted to start fresh cause it has been a minute. When it's all said and done Youtubes skip overlay does NOT go away on its own. Usually you can just tap the screen once and she's gravy but I have to manually hit the X and I hit the damn travel bar 90 percent of the time and it is driving. Me. NUTS.
I have factory reset the phone, factory reset the app, deleted the app entirely with SD Maid...I am at a loss. I cannot figure it out.
Anyone else have this problem before and know of a fix? Any halp would be fantastic. Lmao
Here is a screen recording of my problem with taps enabled
https://youtu.be/Yn_VpQvRLww
Click to expand...
Click to collapse
Is it the stock YT app or Vanced?
ebproject said:
Is it the stock YT app or Vanced?
Click to expand...
Click to collapse
Stock. I couldn't fix it. I had to Qdownload the latest beta 10 to get everything to work. the phone started freaking out out of nowhere and got the red bootloader message. Idk WHAT happened. I don't do any mods, just updates, magisk and a kernel. lol
All is well again.