Hi guys,
My girlfriend has a galaxy s6 running marshmallow. The soft keys are constantly flashing/blinking whenever the screen is turned on. This also causes the device to lag, draining the battery.
I've tried factory resetting the device, and running it in safe mode suggesting it's not software related.
I also installed the the app "Galaxy button lights" that allows the control of the lights, this does stop them flashing, but the device still seems to be running slowly.
Thanks for any advice in advance.
Hi did you find a solution to this as I am having the same problem. Power mode on stops the constant flashing but the phone still lags and it flashes when I charge my phone. My power button also phantom presses :/
I have the same problem. Did you find a solution?
Me too. Turning off the buttons seems to help... it drives me less crazy... but it still feels like there is screen lag. I think this started after I installed the last system update.
One of my co-workers suggested that it may be caused by moisture inside the phone. I set it in the sun for a while, and the problem seems to have gone away.
nhusby said:
One of my co-workers suggested that it may be caused by moisture inside the phone. I set it in the sun for a while, and the problem seems to have gone away.
Click to expand...
Click to collapse
This happened to me like 4 months ago, it hasn't "dried" till now However if i press hard on the lower left bezel - next to the app switcher button my phone works. I have a theory that the contact has become loose under the phone or so?
Hi, I have the same problem for a long time I installed a couple of firmware and the same thing on the factory software always happens, now I use custom rom and it works without problems, it means only on the factory versions I have a problem
Related
Hi dear community!
Got a problem with the power button of my a510. Sometimes when the device is in standby and I want to switch it on by pressing the power button nothing happens and rest totally unresponsive. I have to push it like 10-20 times and even connect the charger to get reaction. Once the device is switched on the power button works normal. I suppose its some kind of freezing of the device in standby mode that blocks the power button. Is it a common problem and what can I do? Thanks in advance for advise!
First thing I would try is to reboot it (press power button for a few second and let it shut down, then restart it). If this is not helping I would hardreset it (reset hole left to power/usb-connector).
And if not this is making it better make a factory reset (from the settings). Keep in mind that you will loose all data and have to start from scratch with your tablet.
Thanks! One question though, do the hardreset from the hole left to power/usb-connector do the same thing as factory reset from the settings - loosing all the data?
ozonbg said:
Thanks! One question though, do the hardreset from the hole left to power/usb-connector do the same thing as factory reset from the settings - loosing all the data?
Click to expand...
Click to collapse
Nope. The pinhole reset thingee is similar to the reset button on a CPU. It simply hard reboots the system (supposedly used when the device freezes, since we can't "pull the battery" like what we do with phones).
Reading through your OP though, I actually recommend sending the tablet back to the shop. I don't have that, nor have I heard of that issue.
I don't have this problem, you'd better send it to service.
I think I found the problem wnen seeing the log from the device. It's a freezing situation. The device become unresponsive and that's why the power button doesnt work when pressed. After second long press it reboots the device. So the button works.
In one of those freezings console says: Unsafe JavaScript attenmp to access frame with URL.. So I disabled java in the stock browser and will keep reading log for further freezes.
hi i was getting that issue.
a factory reset stopped it but recently it came back.
im overseas for 2 months asking acer the immeditaely said to return device for repair.
have to wait now.
Also jist the other day i got three freezes screen went pink completely.
once it went yellow.
i would sugest talk to acer as i know mine now is def faulty after the screen issue.
Hi,
so I realized that a couple of days after buying the thing I disabled some of the apps that comes with it in order to save some RAM, but maybe disabling them causes other apps to misbehave. And thats why sometimes device freezes compleatly. Now I'm checking this theory. Sorry for my English.
What did you use to disable them?
From settings - > apps, then choose a system app and there is a option to disable it.
Another thing. So I'm playing a lot and when some game suddenly stop responding I force closing it. Even this game is already closed after like 10-15min. the device freezes and only rebooting it saves the situation.
ozonbg said:
Hi,
so I realized that a couple of days after buying the thing I disabled some of the apps that comes with it in order to save some RAM, but maybe disabling them causes other apps to misbehave. And thats why sometimes device freezes compleatly. Now I'm checking this theory. Sorry for my English.
Click to expand...
Click to collapse
I disabled alot of stock apps as well. My tab is running fine though. You can maybe list down what you've disabled and I'll confirm if they're disabled on mine too?
Couple of days observation lead me to the conclusion that the freezing is due to unresponding processes left in the memory most likely a high demanding 3d games such Dead trigger, Asphalt 7 or Dark knight.
Edit:
It might be a bad freezing flash player mostly used through stock browser.
i tried this way too..but it freezes also when it's fresh from a hard reset
i don't know if it's an app issue...or whatever.
but i just got a new a510 as replacement of my old one that kept freezing...and also this replacement keeps freezing
i didn0t disable any native app...nor installed any new app. just got it...and freezes the same.
When watching flash video in stock browser and when exit watching, the browser sometimes freezes and needs to be force closed to function again. When left whitout force closing it eventually after some time causes general freeze. That's happening also when a game crashes and left in memory that way. Needs to force close everything that crashes. For example when watching HD Cams in Earthcam.com often browser crashes when closing it or when I play Tower Defense game crashes a lot. Afterwards the whole system freezes.
That's my assumption as above all monitoring I've done.
Let's hope Acer will have fix in Jelly Bean update.
in the newer firmwares are freezes still found? i noticed that all my italian friends stuck with 1044 experience them...maybe later ones solve it?
There is no new firmware, but will be most likely.
there are lots of ota after 1.044 ww.
germany is at 1.099 stock....
i'd like to hear something from who uses it ...
Hey guys,
I have a really strange display issue with my Galaxy R.
I'm on CM10.1 nightly and already tried different nightlies with factory reset and wipe data/cache.
If the phone is not used for a while (sometimes even after 30 minutes), meaning it is on and screen is off, the display won't turn on anymore.
So I press the power button and the capacitive buttons light up, but the screen stays completely black.
Today I noticed that I can even use the touch screen and I could hear all sounds, I even managed to open the dialer and start typing blindly and it would make the dial sounds.
But whatever I try, the screen won't turn on.
Also, it seems when I'm connected to a charger and/or connected to wifi, this problem doesn't seem to occur.
Then I have no choice but to remove the battery, but then often I can't even start the phone.
Sometimes it takes some minutes, sometimes a really long time until I can start it again.
Usually the battery isn't drained, this only happened once.
This occurs after I dropped the phone twice, so it might be related to that.
(Though before I've also dropped it and this never happened.)
Any ideas?
flash stock ics and see if problem persists.
once i flashed a custom rom and faced this issue, reverted to stock and now my device is running with zero issues.
Nikhil said:
flash stock ics and see if problem persists.
once i flashed a custom rom and faced this issue, reverted to stock and now my device is running with zero issues.
Click to expand...
Click to collapse
I tried to find the stock rom online, but all links seem to be down.
Do you know where I can get it?
wasabah said:
I tried to find the stock rom online, but all links seem to be down.
Do you know where I can get it?
Click to expand...
Click to collapse
You need to register and then download from here.
Thanks for that, I installed newest stock rom.
Could boot fine, set up the phone, put it to the side.
One hour later I checked it - same problem again.
Capacitive buttons flaring up, screen not.
Thanks for that, I installed newest stock rom.
Could boot fine, set up the phone, put it to the side.
One hour later I checked it - same problem again.
Capacitive buttons flaring up, screen not.
Then you should visit SSC. They can only repair your device.
Hi, I've been using ViperS 5.1.2 for some time now on my Sensation XE, and it used to work great for me. But since a few days I've got this really annoying freezing problem and I just cannot find a solution.
The touch screen just freezes without any reason, sometimes after using the phone for half an hour, but most of the time within a few seconds after unlocking the screen. When it freezes, the screen won't respond to anything, also not on the back or home button. If I use the on/off button though, the screen will respond again for one or more seconds. This happens randomly; a lot of times I can't even unlock the screen properly, and the rest of the time I only get the screen working normal for a at most 10 seconds. This way it can take a few minutes just getting to the settings menu, for example. The phone does not report any error; after using the on/off button it just goes on where it froze. Also the phone reacts to tilting the screen. Or when playing a video, this just keeps playing normally. So it seems to be purely the screen itself...
I tried a lot to figure out what could be the cause of this problem: uninstalled a lot of recently installed or updated apps, checked the amount of free space/RAM, cleared cache, Dalvik, used nandroid backups to return to a previous (in the past good working) state, tried if removing the sd card would make any difference and finally flashed the rom again. All to no avail; the problem keeps occurring. At first, after trying out a possible solution like the ones I've mentioned, it looks like this did the trick. Sometimes the phone appears to work normal for at most half an hour. But then the problem occurs again, and will at that point occur at a high frequency.
I am out of idea's right now and am getting quite desperate. I need this phone to work properly badly, as I will go on my vacation in a few days and really need to be able to use some of my apps then. So I do hope somebody can help me out here? Any help would be greatly appreciated!
Does it do this while connected to the charger or usb.??
sent by v.konvict
v.konvict said:
Does it do this while connected to the charger or usb.??
sent by v.konvict
Click to expand...
Click to collapse
Yes, does not make any difference. I found today that the phone is now also acting strange in clockworkmod recovery touch, that's for the first time. Can't properly use the touch screen there either any more, only with hardware buttons. So now I guess this should really be a hardware issue. Maybe the phone is just dying...
Yess its a common thing for our phone to act that way while charging.... It has somtheing to do with its poor grounding. You can find threads to help u with how to solve it.
sent by v.konvict
Hello! I have a stock Android Lollipop 5.0.1 Nexus 5 and for the past week or so I have been experiencing a weird issue.
The device randomly crashes. By "crashes" I mean the screen goes black, but the backlight is still on (it's a lighted black). I can push the power button and it will turn completely black (locked) and if I push it once more it turns lighted black again.
To get the device back into usable state I have to keep the power button pressed until the phone resets. Sometimes I keep it pushed for a full minute and nothing happens, sometimes 10 seconds are enough. Sometimes it will go through the "Google" logo and then stay in the lighted black state until I finally manage to reboot it again. Sometimes it crashes again right after it boots up.
It's weird because a lot of the times it's ok throughout the day and then when I go out in the evening, I take it out of the pocket and I see it crashed. Sometimes it crashes while I actually use it.
Last night it started doing something else: instead of lighted black, the screen is filled with static noise. It doesn't move or anything, it's a still image. Today, when a crash like that occurred, the screen glitched first (random lines on the screen, some parts got moved, really weird). I will get some photos if it happens again.
The problem is that I can't identify what's causing it. There is no particular app or action that I do / use that triggers this. It also doesn't seem to be movement-based, as it sometimes happens while it's sitting still on a table.
I updated to 5.0.1 about a day before this started happening, but I'm still not sure if it's software or hardware-based.
I tried a factory reset and booting into safe mode, none of these helped. I will only consider flashing a custom ROM as a final resort, because I'm not sure if it voids the warranty.
PS: the device is still under warranty, but I'm away for the holidays and will be until the beginning of the next year. And I'd like to have a usable device, especially while I'll be on the road.
Smith_S9 said:
Hello! I have a stock Android Lollipop 5.0.1 Nexus 5 and for the past week or so I have been experiencing a weird issue.
The device randomly crashes. By "crashes" I mean the screen goes black, but the backlight is still on (it's a lighted black). I can push the power button and it will turn completely black (locked) and if I push it once more it turns lighted black again.
To get the device back into usable state I have to keep the power button pressed until the phone resets. Sometimes I keep it pushed for a full minute and nothing happens, sometimes 10 seconds are enough. Sometimes it will go through the "Google" logo and then stay in the lighted black state until I finally manage to reboot it again. Sometimes it crashes again right after it boots up.
It's weird because a lot of the times it's ok throughout the day and then when I go out in the evening, I take it out of the pocket and I see it crashed. Sometimes it crashes while I actually use it.
Last night it started doing something else: instead of lighted black, the screen is filled with static noise. It doesn't move or anything, it's a still image. Today, when a crash like that occurred, the screen glitched first (random lines on the screen, some parts got moved, really weird). I will get some photos if it happens again.
The problem is that I can't identify what's causing it. There is no particular app or action that I do / use that triggers this. It also doesn't seem to be movement-based, as it sometimes happens while it's sitting still on a table.
I updated to 5.0.1 about a day before this started happening, but I'm still not sure if it's software or hardware-based.
I tried a factory reset and booting into safe mode, none of these helped. I will only consider flashing a custom ROM as a final resort, because I'm not sure if it voids the warranty.
PS: the device is still under warranty, but I'm away for the holidays and will be until the beginning of the next year. And I'd like to have a usable device, especially while I'll be on the road.
Click to expand...
Click to collapse
I have none of your issues, try booting the device in safe mode and see if the problems still occure. It must be a or multiple downloaded apps that are causing your issues. Or try a data factory reset and restore/download your apps one by one amd try to identify the culpritt.
gee2012 said:
I have none of your issues, try booting the device in safe mode and see if the problems still occure. It must be a or multiple downloaded apps that are causing your issues. Or try a data factory reset and restore/download your apps one by one amd try to identify the culpritt.
Click to expand...
Click to collapse
I said in the post that I tried both of those things. The crash occurred seconds after booting in safe mode and factory reset did not help either.
Smith_S9 said:
I said in the post that I tried both of those things. The crash occurred seconds after booting in safe mode and factory reset did not help either.
Click to expand...
Click to collapse
Flashing the 5.0.1 factory image in fastboot should fix your issues. Or try flashing system.img first, maybe thats enough.
Same issues with my Nexus 5
gee2012 said:
Flashing the 5.0.1 factory image in fastboot should fix your issues. Or try flashing system.img first, maybe thats enough.
Click to expand...
Click to collapse
I am experiencing SAME exactly issues in my N5 with 5.01 and 5.1 . EXACTLY... you are not alone
Seems a software problem (third party app ?) , started in 5.01 and now is in 5.1 , of course system and boot images where flashed with fastboot, so no solution using
Stock, Rooted, using Nova Launcher - Smartwatch 2 - Google Cardboard - Chromecast and many apps.
But started ..if memory helps .. after installing Cardboard 3D apps.
reimer1 said:
I am experiencing SAME exactly issues in my N5 with 5.01 and 5.1 . EXACTLY... you are not alone
Seems a software problem (third party app ?) , started in 5.01 and now is in 5.1 , of course system and boot images where flashed with fastboot, so no solution using
Stock, Rooted, using Nova Launcher - Smartwatch 2 - Google Cardboard - Chromecast and many apps.
But started ..if memory helps .. after installing Cardboard 3D apps.
Click to expand...
Click to collapse
My phone had an issue with the screen. I went to the LG service and they replaced the screen entirely, so that's that.
again and again...
i'm in the same case... I don't have any clues or solutions, i'm just wainting like a dumb... I don't know what to do, i always have to make the thing with the power button and the lower sound button to make it show the boot screen, but it glitch after few seconds... PLS HALP
Hi guys,
I am experiencing the wierdest thing on my brother's Xperia Z3.
2 days ago, the phone randomly stopped showing images on the screen, but the backlight would still switch on and off as normal when pressing the power button. If the phone is restarted in this state by using key combos, the Sony logo won't even show up. This problem started intermittently, but now it does this for a much longer period. The issue would usually occur after the phone being locked, or if it were being used, the screen would show horrible distortion on the bottom half and become non-responsive until the screen switched off and any attempt to switch it on would be make the phone behave as described earlier.
I used to be able to make the image work by plugging in the USB cable, but this method seems to have stopped working, or at the very least has a really low success rate. I have tried all the soft reset methods: Power+VolUp, yellow button in the sim tray, none of those work for me.
I have just stopped short of reflashing the phone with Flash Tools.
Has anyone had this problem before? It is really confusing me as to whether this is a software or hardware issue.
Any suggestions?
I reflashed the phone using Flash Tools and the phone is still behaving the same way; just the backlight is turning on. Besides that, the phone seems to be making the correct noises and responding to the USB cable. Anyone have any ideas? Could it be the screen itself? I'm worried that it may be the motherboard.
Ok, I found something that works. If I hit the device with my hand on the back or the screen a few times, it seems to bring the phone back. My suspicion is either a loose screen connector or something on the motherboard. I'm not really comfortable with opening the phone up, so this is going to be my go-to solution. Hope this is able to help someone.