Does anyone else have problems with their screen just randomly turning off? I will be using the phone with my finger on the screen and the screen will go off. When this happens the phone doesn't lock, I can hit the volume button to turn it back on. I haven't been able to narrow the behavior down to an app. I have done a full wipe of system data and cache and only flashed a rom with gapps and it will still happen before I even restore anything other than Google login.
My phone hasn't been dropped or suffered any damage other than a small scratch on the screen. The buttons don't stick and seem to function perfectly. Never spilled anything on the phone either.
Anyone have any ideas about how to diagnose or someone that may have had the same issue?
Sent from my Galaxy Nexus
Happened to me when running a xylon ROM a week or so ago. I did a full wipe, sdcard and all, went back to stock then flashed a different ROM.
Which roms did it happen to you on?
Scent from my bud
I'm worried that it is possibly a hardware issue because it seems to happen on any rom that I flash. I just bought a mako yesterday and am looking to sell this phone soon and really hope their is nothing wrong with this phone. It might also be kernel related also because the dual boot kernels don't seem to be very stable yet.
Sent from my Galaxy Nexus
Don't seem to be encountering the issue on latest cm stable rom with latest lean kernel 6.4. Not sure what was causing the problem before, but it seems to have resolved.
Sent from my Galaxy Nexus
eqjunkie829 said:
Don't seem to be encountering the issue on latest cm stable rom with latest lean kernel 6.4. Not sure what was causing the problem before, but it seems to have resolved.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
It was probably the kernel!
I also use LK but when I used AK I had that issue and it was just me, other people didn't have it
The phone should be fine
Related
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Restore your previous ROM save
graymonkey44 said:
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Click to expand...
Click to collapse
Are you using a custom kernel. If so are you under / overclocking or over / undervolting?
Nope. I'm running whatever kernel comes with the ROM and no undervolting or overclocking either.
Anyone....?
Have you done a restore?
I would try wiping dalvik-cache and the cache partition. If that dosent work i would wipe everything and do a fresh install of a different rom to determine weather it is rom related or hardware related.
I'm not sure if this has happened to anyone else..
However, this seems to be an ongoing issue with me and Android.
I've had the X10a and Nexus One .. both after only rooting it and using a different rom. While making phone calls and charging.. my phone would reboot..
Or playing a game on the phone.. it would reboot. I basically couldn't do anything without the phone rebooting. Which was sad.
Now with the Galaxy S2X.. This very same issue just happened to me moments ago.
Should I have never rooted it or changed the rom in the first place?
It was running very well before I decided to do so.. even while charging and talking on the phone.
Its funny because it just happened while charging.... I'm not even on the phone myself.
Does anyone seem to have any problem with this when using custom ROMs?
Because if this is true.. then I guess I'll flash the stock kernel and stuff back on the phone just to HOPE it doesn't occur then. :/
I've only experienced this after trying different roms and kernels. I flashed the stock kernel and the deodex rooted stock rom back at the same time and have had no such things happen again.
Imo, stock always runs better than any other rom. I always get better battery too.
My sensation was/is the same way, reboots, dropped signals and all until I put it back to stock rooted. Now it's fine.
——————————
Deebo took your bike too?
Yes I have had it more often on this phone though but it has been fixed by wiping the proper things first then flashing. If not then you might need to redownload the file.
If that doesnt work then you need to make sure that the kernel you are using is compatible with the rom
Also make sure that you are using the proper cpu software for the kernel.. Setcpu seems to work good for most but on Juggernauts new kernel they highly recommend Fauxclock .
I've run roms and kernels since we got root. Never had a random reboot or any other problem for that matter.
Sent from my SGH-T989 using Tapatalk
no6969el said:
Yes I have had it more often on this phone though but it has been fixed by wiping the proper things first then flashing. If not then you might need to redownload the file.
If that doesnt work then you need to make sure that the kernel you are using is compatible with the rom
Also make sure that you are using the proper cpu software for the kernel.. Setcpu seems to work good for most but on Juggernauts new kernel they highly recommend Fauxclock .
Click to expand...
Click to collapse
The only thing I'm worried about is if I continue to wipe and reinstall these customs ROM's that this issue could worsen, but you said that Fauxclock was highly recommended for Jug's Rom? I should try that out myself.
I've always done exactly what was written on the Instructions themselves.
But as for now. . I did a full wipe.. including my SD and the USB data and did a practice call for roughly an hour with me playing games and surfing. So far, there has been any problems. I hope this is perm!
I'd hate to waste another $500 phone D:
As far as the problem kernel with rom etc..
I am running Jug's rom straight. No different kernel's nothing.
I just had it happen to me last night. First time on this phone it has happened. It its stock, rooted. Happened while I was paying music in the car. My other phones with custom roms used to do it all the time.
I wonder if this has happened to anyone without ANY mods on their phone? =X
Fix Permissions
What exactly does that do?
jangst123 said:
Fix Permissions
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
none, with Juggernaut, they did an excellent job
yes, with stock ROM
Sighx said:
I'm not sure if this has happened to anyone else..
However, this seems to be an ongoing issue with me and Android.
I've had the X10a and Nexus One .. both after only rooting it and using a different rom. While making phone calls and charging.. my phone would reboot..
Or playing a game on the phone.. it would reboot. I basically couldn't do anything without the phone rebooting. Which was sad.
Now with the Galaxy S2X.. This very same issue just happened to me moments ago.
Should I have never rooted it or changed the rom in the first place?
It was running very well before I decided to do so.. even while charging and talking on the phone.
Its funny because it just happened while charging.... I'm not even on the phone myself.
Does anyone seem to have any problem with this when using custom ROMs?
Because if this is true.. then I guess I'll flash the stock kernel and stuff back on the phone just to HOPE it doesn't occur then. :/
Click to expand...
Click to collapse
Are you overclocking?
I am running jugs rom. Before I cleaned everything I did move a lot of apps to SD. Maybe that cause it but as for now I have no.problem. definitely report in the future should there be anymore.
AllGamer said:
none, with Juggernaut, they did an excellent job
yes, with stock ROM
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
Reviving old thread... I have a completely stock S2X running 4.0.3 and it randomly reboots or shuts itself off.
I'm trying to figure out if it's a wayward app or a hardware problem. Thinking of rooting and removing the bloatware.
I also saw that it could be a faulty power button, but it also happens by itself, sitting on a desk.
jabela said:
Reviving old thread... I have a completely stock S2X running 4.0.3 and it randomly reboots or shuts itself off.
I'm trying to figure out if it's a wayward app or a hardware problem. Thinking of rooting and removing the bloatware.
I also saw that it could be a faulty power button, but it also happens by itself, sitting on a desk.
Click to expand...
Click to collapse
Root try new rom and kernel see if that fixes it.
Did anyone find any solution? everything in this thread failed for me ..
Have you tried updating to jellybean? Mu phone used to randomly reboot on 4.0.4 probably once a day, and hasn't done it since I did. I am on stock rom.
Sent from my SGH-T989D using Tapatalk 4 Beta
I have a problem. Yesterday, my phone started rebooting randomly. It's been happening almost every time I use the phone. I rooted and flashed the Calk E4GT 2 4.0.4 ROM about a month or so ago and have had no issues to speak of with it at all. I disabled the facial unlock because I noticed that the reboot would routinely happen with either I was trying to unlock or put the phone in standby or while I was trying to use it in some way.
In the past I had noticed similar behaviors randomly, but never became a persistent issue. Anyone have any ideas as to what the culprit could be?
If I need to reload...how do I go about doing that? Just pick a new ROM and flash from CM to start from scratch? If so, what's a good ROM that is 4.0.4 based to run with....Cyanogenmod?
willjr0k5 said:
I have a problem. Yesterday, my phone started rebooting randomly. It's been happening almost every time I use the phone. I rooted and flashed the Calk E4GT 2 4.0.4 ROM about a month or so ago and have had no issues to speak of with it at all. I disabled the facial unlock because I noticed that the reboot would routinely happen with either I was trying to unlock or put the phone in standby or while I was trying to use it in some way.
In the past I had noticed similar behaviors randomly, but never became a persistent issue. Anyone have any ideas as to what the culprit could be?
If I need to reload...how do I go about doing that? Just pick a new ROM and flash from CM to start from scratch? If so, what's a good ROM that is 4.0.4 based to run with....Cyanogenmod?
Click to expand...
Click to collapse
I'm having the same problem with the stock ff18 rooted...started out of the clear blue, can't place my finger on a consistent pattern. I'm gonna try installing a new kernel and see if that helps. If it works I'll let you know.
I disabled facial recognition security and cleared dalvik and normal cache with clockworkmod. My phone hasn't rebooted basically all day so far.
Something must have been stuck in the cache possibly that was causing issues.
Sent from my SPH-D710 using xda app-developers app
So here's what I've discovered.
As of now, on stock 4.1.1, the phone runs smooth when audio is screwed up. The moment touch sounds work again (or the moment I install SoundAbout to fix it) it starts lagging like crazy. Is this a hardware thing? After switching roms, kernels, versions of Android, flashing stock and locking the bootloader nothing has worked.
_________________________________________________________________________________________________________
So I'm having this strange issue that I don't really see mentioned previously (based on my multiple searches)
My phone was running fine until I flashed Paranoid Android (The last Jellybean 4.1 Release). On this ROM i was getting some insane lag, sluggish performance. I'd swipe on the home screen and get a huge delay or the phone would read it as a long touch and bring up the wallpapers option. Opening folders and the app drawer had some serious slow downs. It was a real mess.
I assumed the phone just didn't play well with the ROM so I flashed over to Bugless Beast. The odd thing is that the problems persisted. I would get just as horrible performance and the same sluggish visual effects and stuff. Specifically I remember even the audio slowing down and being choppy (touch sounds) until they automatically disabled themselves and the ROM ran smooth for a bit but returned to the sluggishness again.
So last night I restored to stock flashing the stock image and relocking the bootloader. Rooted, unlocked, flashed recovery again and loaded up Bugless Beast and the issue is still happening. Even got my first random reboot on Bugless Beast today after it slowed down really bad. Now I've noticed that when touch sounds disable themselves so does media audio (while the ringer and notification sounds still work). This is pretty much why I'm convinced it's a software problem and not a hardware one.
Basically I just wanted to know if anyone's experienced something similar and found a way to fix it? Probably going to reflash to stock tonight
EDIT: Well it seems like the audio thing might be a hardware issue. SoundAbout fixed that but I don't see how my audio jack could have been damaged in between flashes.
EDIT 2: Current State:
- I tried flashing just the system img (multiple times) and the lag returned
- I just flashed a 4.2.1 ROM just to see what happened. Touch sounds are back which means my headphone jack fixed itself. Still EXTREMELY slow.
- And just like that headphone jack screwed AGAIN but no more lag? Any reason for these two things to be related?
Bump. Any help? Still happening, though not as common, when I flashed stock
Could it be a hardware problem? Though it would be odd for a hardware issue to show up after flashing a rom. How long have you had the phone before the issues started?
Have you tried the official 4.1.1 image?
If so, do problems go away?
If you are using ports you have to expect bugs.
Let us know
Sent from my Galaxy Nexus using xda premium
Try flashing just the system.img a few times in fast boot with a reboot boot loader between. I was having slow boot up and random performance issues on full stock until I flashed that partition with the stock image (3 Times to be precise). I no longer have the 5 minute wait for the Google logo to disappear, and overall much snappier. Apparently something was leftover from previous restores/downloaded OTA updates.
Sent from my Galaxy Nexus using xda premium
I'd suggest you stop messing around with multiple ROMs and start trying different kernels. Kernels will impact performance much more than any specific ROM will. Try either an updated version of leanKernel (assuming your sig is accurate) or a different kernel all together. Others have had luck with franco, trinity, etc, etc.
Had the same problem on my GSM GNex yesterday. Flashed a ROM combination (Xylon 4.2.1 + Lean Kernel 5.0) and had this lag.. everything would lag and FC.. tried a full wipe as well but didnt work..
Changed to another AOSP Rom (UDK 4.2.1 with linaro kernel) and its fine now..
Oh and i also changed recovery from 6.0.1.5 non-touch(that i flashed yesterday) to CWM 6.0.1.9 touch..
Not sure if this helps but thats what worked for me.. I suggest going back to a ROM that worked for you in the past.. and also try formatting your SD card and run the phone without putting back your data for a while..
@rlb81 - Starting to think it might be a hardware one but at this point I'm not sure of anything. Only had the device 3 months.
@tincbtrar - Yeah I flashed the official 4.1.1 image and the problems are still there. Ridiculously sluggish and the audio problems. In fact, on stock 4.1.1 I just had this issue where I'd turn the screen off, the animation would be really slow, and then I'd get a black screen and wouldn't be able to wake it up. Did a battery pull to boot it again and the same exact issue the second time it turned on.
@Winesnob - I'll be sure to give this a try. Thanks so much! This is a really odd issue and I've never experienced it on any of my previous android devices (Fascinate, Incredible, Thunderbolt, even the old HTC Vogue)
@Cilraaz - Currently just trying to get stock running properly so everything is locked right now. Can't remember but I'm pretty sure I tried the newer lean kernel when I flashed back to bugless.
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
Thanks so much to all of you guys. If you have any other input it'd be greatly appreciated.
+1 on try different kernels, my phone seems to love lean kernel. I switched to tiny kernel for a few days and every so often, a simple task like opening tapatalk would take up to 30 seconds, and everything would become unresponsive. Nothing but smoothness on lean, give some different kernels a try.
Sent from my Galaxy Nexus using Tapatalk 2
I tried Winesnob's method and I THOUGHT it worked. Was running smooth for a good amount of time and just now back to the really choppy mess it was before. In fact it just got frozen on the lock screen and went to a black screen again.
This is killing me. The headphone jack thing seems to be a hardware issue anyway so I emailed Wirefly about getting a replacement. I feel like they'll avoid that though and I'll be left with this.
Gonna try some other things tonight. Wish me luck
EDIT: The thing gets so choppy that notification sound get choppy and crackle. This is insane. I'm fully stock minus the unlocked bootloader right now
EDIT2: Flashed stock image and touch sounds came back. This is getting really weird. Lag is still here though. Really bad lag
Bumping again now that I've sort of pinpointed the issue. Lags with touch sounds enabled and headphone jack works / soundabout installed with touch sounds on.
Currently the phone's headphone jack is screwed up, I installed soundabout, disabled touch sound and no lag.
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Ahh thanks for the heads up
Would it be wise for me to try going back to the ROM that started the problem? Maybe that'll do *something?
Again, from what I saw, everyone had some luck going back to the rom that caused the problem.
There's a tool in the developer thread called "super duper wipe" that seems to have fixed the lag for ones having the issue. I'm not sure how it works, but If you can take it apart and look at the zip, it may point someone in the right direction.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
The dev thread in the DROID incredible 2 forums.
Sent from my Incredible 2 using xda app-developers app
SkinnyT said:
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I took a look at that super duper wipe script...looks interesting but not necessary on our phone.
Im starting to think you may have a hardware issue if you cant flash stock images and get everything back to normal. Maybe a relock and then unlock?
i just did this cause I had a SIM card issue...and naturally it wiped my data completely.
solarpolitiks said:
...
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
...
Click to expand...
Click to collapse
turns out my lag problems weren't gone completely until i wiped /System before flash.. Alot of ROM's out there have a /system wipe script, but the one causing my FC's and lag didn't, so it was installing the new system files on top of the old ones and possibly causing a conflict.
it could the same for you
Yeah I've recently tried unlocking again, formatting system before a ROM flash and I still get lag. Now it's more that it will last a day without the lag and just magically come back the next day. Headphone/speaker issues still exist. Wirefly completely ignored my first email so I sent them another one. Hoping for the best.
Completely lost on what this could be
anyone see this thread?
http://forum.xda-developers.com/showthread.php?t=2029246
I have random lag on my vzw nexus and i think its io related and nothing to do with the kernel.
Sent from my Galaxy Nexus using Tapatalk 2
I'll check out that app but like I've mentioned. Lag seems to be coming from sound. After installing soundabout to get the speaker working again I get some nasty lag. Disable touch sounds and I have no lag. Disable the sound effects on twitter - no issues with the app. WireFly said I'm still under manufacturer warranty through my carrier and it sounds like I should be covered. If Verizon tries anything to get around that they'll be willing to do a three way call to make sure I get the replacement. I'll probably end up with a refurb but hopefully it'll beat this stupid issue.
Just stopping in to say thanks to everyone that tried to fix the issue but Verizon is sending out my replacement device today and I'll be sending this one with the faulty headphone jack back.
Problem solved!
Hey all!
This is happening to me for 2 months now, I was running official 12.1CM and now official 13CM
I tried to also use some stock based rom but im pretty sure it happened there too.
Whats happening to me is that randomly throughout the day my phone's screen turns black and I cant reboot it by any home button combination, only by getting out the battery.
When this happens the phone just totally freezes and I cant get it to respond or make a sound.
I don't think that the phone dies because sometimes when its freezes I can still see the notification led blinking.
Does anyone know why this might happen? or where can i copy some logs that might help you guys figure it out?
Thanks in advance!
sounds like you have the sleep of death issue? Personally I haven't been on CM roms much on my G3 so I haven't really encountered this issue but on my previous phone I've encountered this a few times on CM.
EDIT: Though it shouldn't happen on stock are you sure it happens on stock as well?
I have this issue as well using the Exodus rom. I never had it while using a stock rom, so I think this is a cyanogenmod issue (Exodus is a CM based rom in 5.1).
I have the exact same issue with my vs985. Seems to happen the most when viewing any sort of video, but I have had it happen at other times as well. Pretty dang annoying, probably 3-4 times a day. Using CM 13.0-20151217-nightly-vs985 but it started when I first flashed CM. Never had the issue on stock rooted rom.